Your message dated Fri, 22 Apr 2016 11:52:38 +0200
with message-id <[email protected]>
and subject line Re: Bug#789911: python-gear: Obsolete ‘daemon.pidlockfile’ API
migrated to ‘python-lockfile’ library
has caused the Debian Bug report #789911,
regarding python-gear: Obsolete ‘daemon.pidlockfile’ API migrated to
‘python-lockfile’ library
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
789911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789911
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-gear
Version: 0.5.5-2
Severity: important
Howdy,
The ‘python-daemon’ library has in the past included an internal
‘daemon.pidlockfile’ module for its own use.
That functionality has migrated to the ‘lockfile’ distribution
(packaged in Debian as ‘python-lockfile’ or ‘python3-lockfile’)
version 0.9 and later.
In ‘python-daemon’ version 2 and later, the ‘daemon.pidlockfile’
module does not exist. Code which attempts to import it will fail.
A simple inspection (using ‘grep’) of the Python source for this
package shows it is using the obsolete ‘daemon.pidlockfile’ API, and
will fail with an ImportError.
If the package is unusable without that API, then this bug report
should be upgraded to “Severity: serious”.
You can fix this bug by:
* Work with upstream to remove references to ‘daemon.pidlockfile’, and
to migrate to the ‘lockfile.pidlockfile’ API.
* Package the new upstream version of this package.
* Add to this package a “Depends: python-lockfile (>= 0.9)” and/or
“Depends: python3-lockfile (>= 0.9)”.
* Release that package to Debian Sid.
If you've already done this, great! Please let me know so that I can
keep track of which packages are affected.
--
\ “My doctor told me to stop having intimate dinners for four. |
`\ Unless there are three other people.” —Orson Welles |
_o__) |
Ben Finney <[email protected]>
--- End Message ---
--- Begin Message ---
On Fri, Apr 22, 2016 at 06:11:16 +1000, Ben Finney wrote:
> On 21-Apr-2016, Julien Cristau wrote:
> > On Thu, Jun 25, 2015 at 18:02:54 +1000, Ben Finney wrote:
> > > In ‘python-daemon’ version 2 and later, the ‘daemon.pidlockfile’
> > > module does not exist. Code which attempts to import it will fail.
> > >
> > > A simple inspection (using ‘grep’) of the Python source for this
> > > package shows it is using the obsolete ‘daemon.pidlockfile’ API,
> > > and will fail with an ImportError.
> > >
> > python-gear uses daemon.pidfile.TimeoutPIDLockFile, is that API
> > safe? If yes, this bug can be closed afaict.
>
> Yes, ‘daemon.pidfile’ remains supported for current code.
>
> Please close this bug using a message that also sets the “fixed”
> version, with the value of “python-gear/FOO” where “FOO” is the
> version that uses the ‘daemon.pidfile’ API.
>
As far as I can tell this was always the case, the code was apparently
added in
https://github.com/openstack-infra/gear/commit/3ca44afc2cb040bdc4cd2f090ae0b9f364b8e6c4
and already had a fallback from daemon.pidlockfile to daemon.pidfile.
Cheers,
Julien
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
