On Mon, Aug 06, 2012 at 08:43:57AM +0200, Raphael Hertzog wrote: > Hello, > > On Sun, 05 Aug 2012, Robert Luberda wrote: > > > Processing triggers for doc-base ... > > > /usr/bin/perl: symbol lookup error: /usr/lib/perl5/auto/UUID/UUID.so: > > > undefined symbol: Perl_xs_apiversion_bootcheck > > > dpkg: error processing doc-base (--unpack): > > > subprocess installed post-installation script returned error exit status > > > 127 > > > > This has been already reported as #673913. But to be honest I have no > > idea what to do with this bug. From doc-base point of view it has been > > fixed in doc-base 0.10.3, but you are still running 0.9.5. > > > > I believe the doc-base trigger was activated because some package > > providing /usr/share/doc-base file was upgraded during the dpkg run, > > and the doc-base trigger failed because system was not in consistent > > state. I've just learn about `interest-noawait' flag. Would using the > > flag in doc-base's triggers file help? Probably not, because still the > > flag won't be available in doc-base 0.9.5. > > It won't help for this upgrade. But it might help for the next one > between wheezy and jessie. So it might still be a good idea to switch > to interest-noawait for packages like doc-base and man-db which trigger > for many packages. > > > So maybe making libuuuid-perl to conflict with doc-base << 0.10.3 as > > suggested in #652638 will be a better idea? Honestly, I don't know. > > That would be a klumsy work-around. > > Another thing that we should be considering is changing APT's default > to avoid running the triggers so often. I filed > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626599 some time ago > but it's not been activated yet :-( > > I did a test-upgrade this weekend on my laptop's wife and I enabled > those APT's options: > DPkg::NoTriggers "true"; > PackageManager::Configure "smart"; > DPkg::ConfigurePending "true"; > DPkg::TriggersPending "true"; > > And the upgrade went fine. I clearly saw the part of the upgrade where > libuuid-perl was unpacked before perl-base but no doc-base trigger was > activated in between IIRC.
I just tested several time following Raphael's advice on APT configuration, and I'm afraid it doesn't close this #680626 bug I reported. :/ However, when I ldd /usr/bin/python, it seems to be linked against libssl, so I'm wondering if this bug isn't related to the python package missing a dependency against libssl. It also seem to be linked against libcrypto, which is also missing when the dist-upgrade fails. I can test another time and send more informations if you tell me what output you might want to see included. bert. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
