I've changed /usr/sbin/update-python-modules to get more information out of the warning:
for package in public_packages:
if srcfile in public_packages[package]:
if py not in public_packages[package].pyversions: debug("remove "+abspath) os.remove(abspath) removed = True
break
else: warning("WARNING: %s is linked (from %s) but does not belong to any package." % (srcfile, abspath))
And it now shows
WARNING: WARNING: /usr/share/pyshared/lsb_release.py is linked (from /usr/lib/pymodules/python2.6/lsb_release.py) but does not belong to any package.
I don't know how to fix this, but for the people who know about packaging python modules, creating a python-support module description file should be an easy fix?
Hope this comment helps to speed this fix up (a.k.a. my 2 cents).
I've changed /usr/sbin/ update- python- modules to get more information out of the warning: packages[ package] : packages[ package] .pyversions:
debug(" remove "+abspath)
os.remove( abspath)
removed = True
warning( "WARNING: %s is linked (from %s) but does not belong to any package." % (srcfile, abspath))
for package in public_packages:
if srcfile in public_
if py not in public_
break
else:
And it now shows pyshared/ lsb_release. py is linked (from /usr/lib/ pymodules/ python2. 6/lsb_release. py) but does not belong to any package.
WARNING: WARNING: /usr/share/
I think the problem is that the lsb_release.py is not mentioned in a .private or .public file described in http:// svn.debian. org/viewsvn/ collab- maint/deb- maint/python- support/ trunk/README
I don't know how to fix this, but for the people who know about packaging python modules, creating a python-support module description file should be an easy fix?
Hope this comment helps to speed this fix up (a.k.a. my 2 cents).