You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm the debian maintainer of the spambayes package, and I received the following bug report (available online here).
Original bug report
Dear Maintainer,
The ‘python-lockfile’ package in Debian has released in Debian Sid an upstream version with an incompatible API to previous Debian releases.
This change was described in 2014-11, for example here. This bug report is part of a mass bug report announced 2015-06-05 here.
Packages using the API in ‘lockfile’ prior to version 0.9 will fail with the current ‘python-lockfile’ in Debian Sid.
Please do the following to resolve this bug:
Work with your package's upstream to have the code support ‘lockfile’'s current API, if it doesn't already. Encourage them to release a new version with that support.
Upload a new release of this package with a versioned dependency on “python-lockfile (>= 0.9)”.
A patch have been provided and seems to work. It would be nice to see it integrated in the next release.
Thanks for providing spambayes !
The text was updated successfully, but these errors were encountered:
Hi,
I'm the debian maintainer of the spambayes package, and I received the following bug report (available online here).
Original bug report
Dear Maintainer,
The ‘python-lockfile’ package in Debian has released in Debian Sid an upstream version with an incompatible API to previous Debian releases.
This change was described in 2014-11, for example here. This bug report is part of a mass bug report announced 2015-06-05 here.
Packages using the API in ‘lockfile’ prior to version 0.9 will fail with the current ‘python-lockfile’ in Debian Sid.
Please do the following to resolve this bug:
A patch have been provided and seems to work. It would be nice to see it integrated in the next release.
Thanks for providing spambayes !
The text was updated successfully, but these errors were encountered: