Bug#451459: update-manager: Leaving stray files after purging the package
Sam Morris
sam at robots.org.uk
Sun Feb 17 13:21:23 UTC 2008
forcemerge 434025 451459 447641
thanks
It seems that the presence of these files breaks update-manager
completely:
# update-manager
/usr/lib/python2.4/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
warnings.warn("apt API not stable yet", FutureWarning)
Traceback (most recent call last):
File "/usr/sbin/update-manager", line 76, in ?
app = UpdateManager(data_dir)
File "/usr/lib/python2.4/site-packages/UpdateManager/UpdateManager.py", line 254, in __init__
File "/usr/lib/python2.4/site-packages/UpdateManager/Common/DistInfo.py", line 58, in __init__
IOError: [Errno 2] No such file or directory: '/usr/share/update-manager/channels//Debian.info'
After I removed the leftover UpdateManager and SoftwareProperties
directories from /usr/lib/python2.4/site-packages, the copies
in /var/lib/python-support/python2.4 were then used, and the package
started to work again.
--
Sam Morris
http://robots.org.uk/
PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20080217/aa4f5e66/attachment-0004.pgp
More information about the pkg-gnome-maintainers
mailing list