New upstream release with incorporated patches

As we are now becoming upstream for PyHesiodFS, which involves:
 - apply all our patches to pyHesiodFS.py
 - delete the patch files
 - punt the dependencies on quilt and patchutils in debian/control
 - punt the patchsys-quilt rule in debian/rules
 - instead of patching setup.py to change the script name, add some
   Python code to retain the old script name on OS X only
 - Add a debian/source/format file, since we didn't have one (force this
   to be source format 1.0 until we deal)
Move script name logic to setup.py

Rather than renaming the script in the rules file, move the logic
to setup.py itself, making use of custom distutils commands to
do the work for us.
Drop support for Python < 2.6

We want to require 2.6, because we're using Python 2.6 syntax in
exceptions.  This also means we can drop our own implementation of
defaultdict, since collections.defaultdict has been around since
Python 2.5.
Drop support for python-fuse < 0.2

- We no longer need to support ancient versions of python-fuse, which
  required Stats to be returned as tuples
- Also, remove the try/except around the constructor.  The code will no
  longer throw AttributeError because fuse.__version__ will always exist
Add config file, attachtab, and locker.py support

A large rewrite to add support for a configuration file, an "attachtab"
to present mount information to userspace tools, and using locker.py for
locker lookup and handling.

Changes as part of this commit:
- IOErrors are no longer raised during lookup, instead None is returned
  and errors are syslogged.
- Whether or not to syslog for ERR lockers, unmountable lockers, or
  successful mounts is configurable in the file.
- We override Fuse.parse() and store the mountpoint for later access
- Mount data is now stored in an attachtab object which stores both
  user-requested symlinks and Locker objects

N.B. The attachtab does not expose other users' mounts, as the old
liblocker did.  The decision to not expose other users' mounts in
pyhesiodfs was deliberate, and not simply a side-effect of
implementation.
Add a sample config file; update manpage

- Add a sample config.ini and install it with the docs.
- Mention sample config file in manpage (and clean up the
  man page while we're at it.)
Add dependency on $remote_fs in init script

Add a Required-Start and Required-Stop dependency on $remote_fs,
because it is apparently still 1992 with 40MB disks and /usr could
therefore be an NFS mount.

The irony of what is effectively a remote filesystem's init script
depending on $remote_fs is not lost on the authors.
Bump debian/compat and debian/pyversions

We now require Python 2.6 or higher in pyversions, and we're also
now compatibile with dh7.
Clean up control file

- Properly Provide/Conflict ${diverted-files} for c-p-d
- Use ${python:Versions} correctly
- Do not ${python:Provide} anything, because we don't.
- Do not depend on python-dev when we're not compiling modules.
Release version 1.1

Release version 1.1 in debian/changelog and setup.py