[Pkg-auth-maintainers] Incompatible API coming, in “python-daemon >= 2”

[Ben Finney]

Howdy,

You are maintaining a package with a dependency on ‘python-daemon’. In
turn, this brings a dependency on ‘python-lockfile’.

Debian's package ‘python-lockfile’ has recently updated to one with a
backward-incompatible API. (In summary: exported names in the API have
changed, and dependent code must change accordingly. See its changelog
for more detail.)

The ‘python-daemon’ code has changed in many ways since the version
1.5.x series. The 2.x series now depends on the current
‘python-lockfile’ API, and it is that version of ‘python-daemon’ which
will be soon uploaded to Debian.

Please check the package you maintain to see whether it is compatible
with upstream ‘python-daemon’ version 2 or later.

If the package is compatible only with earlier ‘python-daemon’
versions, I recommend declaring this in the package metadata. A field
“Depends: python-daemon (<= 1.6)” would be good.

If there is an upstream version of your package that is compatible
*only* with ‘python-daemon’ version 2 or later, please package that
version with “Depends: python-daemon (>= 2)”.

The backward-incompatible ‘python-daemon’ will likely be uploaded into
Debian within a few weeks.

Please let me wknow if you need assistance with this issue.

-- 
 \       “To have the choice between proprietary software packages, is |
  `\      being able to choose your master. Freedom means not having a |
_o__)                        master.” —Richard M. Stallman, 2007-05-16 |
Ben Finney <ben at benfinney.id.au>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-auth-maintainers/attachments/20150605/703e60a1/attachment-0001.sig>