strange warning on python-support

Missing system information:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu karmic (development branch)
Release: 9.10
Codename: karmic

uname -a
Linux monstermord 2.6.31-6-generic #26-Ubuntu SMP Fri Aug 21 17:55:00 UTC 2009 x86_64 GNU/Linux

LANG=C apt-cache policy lsb-release
lsb-release:
  Installed: 4.0-0ubuntu3
  Candidate: 4.0-0ubuntu3

LANG=C apt-cache policy python-support
python-support:
  Installed: 1.0.3ubuntu1
  Candidate: 1.0.3ubuntu1

LANG=C apt-cache policy python-central
python-central:
  Installed: 0.6.11ubuntu7
  Candidate: 0.6.11ubuntu7

 LANG=C apt-cache policy python
python:
  Installed: 2.6.2-0ubuntu1
  Candidate: 2.6.2-0ubuntu1

Processing triggers for python-support ...
WARNING: WARNING: /usr/share/pyshared/lsb_release.py is linked but does not belong to any package.

$ apt-cache policy python-support
python-support:
  Installed: 1.0.3ubuntu1
  Candidate: 1.0.3ubuntu1
  Version table:
 *** 1.0.3ubuntu1 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

im having the same issue too .. waiting for update to fix it :)

So far updates did not fix it for me

Exactly the same error quoted in #3

After apt-get update finishes: "/usr/share/pyshared/lsb_release.py is linked but does not belong to any package"
===
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu karmic (development branch)
Release: 9.10
Codename: karmic
===
$ uname -a
Linux vmc-desktop 2.6.31-7-generic #27-Ubuntu SMP Mon Aug 24 17:33:49 UTC 2009 i686 GNU/Linux
===

same problem here :
Verarbeite Trigger für python-support ...
WARNING: WARNING: /usr/share/pyshared/lsb_release.py is linked but does not belong to any package.
________
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu karmic (development branch)
Release: 9.10
Codename: karmic
________
uname -a
Linux 2.6.31-6-generic #26-Ubuntu SMP Fri Aug 21 17:55:00 UTC 2009 x86_64 GNU/Linux

<OT>This ticket is already in 'confirmed' state. At this moment in time, we don't need further confirmative comments. To the contrary, they clutter up this ticket and make it harder to find the really important information. Please use the link "This bug doesn't affect me (Change)" to indicate that you are affected by this bug. You should also subscribe yourself to get progress updates, etc. This "rule" generally applies to all bugs in Launchpad. Thank you and sorry for being off-topic.</OT>

Removing the file does the trick.
sudo rm /usr/share/pyshared/lsb_release.py

Does deleting this break anything????

Deleting the files removes the messages, but as soon as you reinstall lsb-release package it comes back. It doesn't hurt to remove it, but keeping it doesn't hurt either.

I also get this error, not that is has any effect (but visual/aesthetic). The error says that it is not part of an existing package but it seems that it is part of the lsb-release package.

$ dpkg -S /usr/share/pyshared/lsb_release.py
lsb-release: /usr/share/pyshared/lsb_release.py

||/ Name Version Description
ii lsb-release 4.0-0ubuntu5 Linux Standard Base version reporting utility

I wanted to also compare the two lsb_release:

$ which lsb_release
/usr/bin/lsb_release

$ diff /usr/bin/lsb_release /usr/share/pyshared/lsb_release.py
(Output attached: lsb_release.diff)

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 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).

I'm still having this problem.

The lsb package calls pycentral as follows:
DH_PYCENTRAL=include-links dh_pycentral

I suspect the include-links bit triggers the python-support warning: python-support expects to find this file in a corresponding .public/.private list, but doesn't. You can safely ignore this warning which is just a consistency check in python-support not handling this python-central case.

I'm keeping this report open to either drop "include-links" from the lsb package if it's not needed, or to fix the python-support check/warning.

Loïc, any news on this one?

This is just a harmless warning; I don't know whether it can easily be avoided, but we have hopes to change the way we package core python packages substantially in the future, which would make this warning obsolete.

Hmm I first thought all include-links packages would cause similar warnings for some files, but it's not the case; the problem appeared on my system after 4.0-0ubuntu2 and does not appear on new installs (the timestamp of the file is the date of installation of 4.0-0ubuntu2 which is the last version using python-support). In 4.0-0ubuntu3, it was converted to python-central + include-links; I guess this needs a manual cleanup call to python-support's update-python-modules.

The lsb package was already using python-central in jaunty, so I think this only affected users of intermediate karmic versions; I did a jaunty -> karmic upgrade (debootstrap jaunty + apt-get install update-manager-core (pulls python-support for some reason) + do-release-upgrade) and there's no /usr/lib/pymodules/python2.6/lsb-release.py and update-python-modules --post-install doesn't trigger the warning.

This bug was fixed in the package lsb - 4.0-0ubuntu7

---------------
lsb (4.0-0ubuntu7) lucid; urgency=low

  * Remove /usr/lib/pymodules/python2.6/lsb_release.py on upgrades; this might
    have stayed behind due to using python-support in intermediate karmic
    development versions; LP: #418017.
 -- Loic Minier <email address hidden> Fri, 18 Dec 2009 15:34:25 +0100

this bug is back in lucid beta 1