Le mercredi 27 janvier 2010 à 16:25 -0500, Joey Hess a écrit :
> > It doesn’t make much sense to me since it would mean that
> > update-python-modules failed silently for all of these packages; no
> > symlinks set, and no dpkg-trigger called.
>
> Or that dpkg-trigger failed to record the trigger somehow.
At least this was not the case for python-dbus, since dpkg-trigger is
called after the symlinks are created.
> > It would be interesting, if you manage to reproduce the issue, to see
> > whether there have been any output, and to see whether the contents of
> > the files in /usr/share/python-support is correct. I’d also like to know
> > whether some other symlinks, especially some from this last batch of
> > updates, are still missing.
>
> Does the attached output of find /var/lib/python-support/ -type l
> and find /usr/share/python-support/ suffice, or is there an easy way
> I can search for missing symlinks?
The easy way is to regenerate all symlinks from scratch, making them as
they should be, and look for differences:
find /usr/lib/pymodules | sort > foo
cp -a /usr/lib/pymodules /var/tmp/pymodules.backup
update-python-modules -f
find /usr/lib/pymodules | sort > bar
diff -u foo bar
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “A handshake with whitnesses is the same
`- as a signed contact.” -- Jörg Schilling
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
