Your message dated Thu, 22 Sep 2011 20:08:48 +0200
with message-id <[email protected]>
and subject line Re: Bug#373465: python-nautilus: needs a tight dependency on
python
has caused the Debian Bug report #373465,
regarding python-nautilus: needs a tight dependency on python
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.)
--
373465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373465
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nautilus-python
Version: 0.3.0-3
Severity: important
Hi, your package has been detected as generating a python
module/extension that may need an upgrade to the new Python Policy[1].
A wiki page [2] explains what has to be done to upgrade your packages
to the new Policy. This bug may be a false positive, in that case,
please just close the bug.
This bug is part of a mass bug filling, and its severity will be
raised to serious when python will default to python2.4. Please note
that this bug (even not being RC) falls under the 0-day NMU policy.
[1] http://lists.debian.org/debian-devel-announce/2006/06/msg00009.html
[2] http://wiki.debian.org/DebianPython/NewPolicy
--- End Message ---
--- Begin Message ---
* Jakub Wilk <[email protected]>, 2010-06-25, 01:03:
nautilus-python builds private Python extensions. Such extensions are
normally not binary compatible across different Python versions, so
the package must declare tight dependency on the version for which the
extensions were built (i.e.: "python (>= X.Y), python (<< X.{Y+1})").
Uhh, now I see that python-nautilus apparently access the private
module via libpythonX.Y.so, so the above is nonsense.
I believe that the (originally reported) bug can be closed.
Doing it now.
--
Jakub Wilk
--- End Message ---
