Le mercredi 27 janvier 2010 à 11:21 -0500, Joey Hess a écrit : > I upgraded from 0.83.0-1 last night. This morning I rebooted > and noticed wicd was not working; python could not load the dbus > module. > > Seemed python-support had somehow not registered it: > > j...@gnu:/var/lib/python-support>find py* | grep -i dbus > python2.4/wicd/dbusmanager.py
> I purged, reinstalled, and dbus directories showed up there, problem solved. > > NB: This laptop was just converted to btrfs (via fresh format and copying > over the previous content), so it's possible btrfs is eating data. It seems > unlikely to me that it would choose to just eat all the python support files > for python-dbus, for both python 2.5 and python 2.6, and leave other files > that were modified at the same time alone, though. I don’t think this should matter - except if by an extraordinary coincidence it only ate up the python-dbus.public file. OTOH it’s not, as expected, trivially reproducible. Given how python-support works it either means the postinst could have failed silently (which should not happen) or something happened with the upgrade process that messed up the way scripts were run. The trigger would then have removed the old dangling symlinks, because the binNMU made python-dbus switch to the python-support 1.x directory layout. Do you have the dpkg.log snippet that corresponds to the python-dbus upgrade? I’d like to see what was upgraded with it that could have made it fail. Cheers, -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
