Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
Package: upgrade-reports Followup-For: Bug #680626 Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
On Tue, Aug 7, 2012 at 14:37:10 +0200, berta...@ptitcanardnoir.org wrote: 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. python2.7-minimal in wheezy does depend on libssl1.0.0. However that's not enough to ensure unpack ordering. Cheers, Julien -- Julien Cristau julien.cris...@logilab.fr Logilab http://www.logilab.fr/ Informatique scientifique gestion de connaissances -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
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. Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
Julien Cristau wrote: As a variation on this theme (triggers being run when the triggered package is unconfigured in the middle of an upgrade from squeeze to wheezy), I just got the following: 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. 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. Regards, robert -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
On Wed, Aug 01, 2012 at 12:22:22AM +0200, Julien Cristau wrote: On Mon, Jul 16, 2012 at 14:19:03 +0200, Julien Cristau wrote: On Sun, Jul 15, 2012 at 18:26:50 +0200, Guillem Jover wrote: W/o having looked yet at the details I'd say this *seems* like #671711, which I'm not planning on fixing for wheezy as it would introduce regressions on other situations, and given that this behaviour has been around since the introduction of triggers, and while quite unfortunate it's something that will have to be worked around on the affected packages because older dpkg will not be able to handle this correctly anyway. Going to look now, to make sure the above is the case. That seems likely. What is the recommended workaround here? Should package postinsts just ignore failures when called with 'triggered', or is there a better way? Ping? Any ideas? The current behaviour of triggers is well documented. Packagers should not use triggers in situation when they need more than what the trigger interface offer. This is why menu do not use triggers (see #556104). Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
On Fri, Aug 3, 2012 at 11:04:25 +0200, Bill Allombert wrote: The current behaviour of triggers is well documented. triggers.txt.gz says Packages in t-awaited and t-pending demand satisfaction of their dependencies just like package in installed. The current behaviour doesn't seem to satisfy that at least for t-pending, unless I'm missing something. Either way, we need a fix for this in the squeeze to wheezy upgrade, which means not involving dpkg or squeeze packages, and probably not involving rewriting 10 packages to not use triggers (though I guess that would be an option if there's no better idea). Cheers, Julien signature.asc Description: Digital signature
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
On Sat, Jul 7, 2012 at 14:51:32 +0200, bertagaz wrote: In an attempt to test upgrading Squeeze to Wheezy now that the Big Wheezy Freeze has come, it failed at the dist-upgrade step. I installed a fresh Debian Squeeze and tested from it. I wanted first to see if it would be possible to upgrade with a simple and graphical method (using update-manager and synaptic), as it was quite complicated for the Lenny-Squeeze upgrade. Ended up with this result, so I also tested using plain apt-get upgrade and dist-upgrade. Same result, dist-upgrade fails on python-support postintallation script with the following error: Processing triggers for python-support ... /usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory dpkg: error processing python-support (--unpack): subprocess installed post-installation script returned error exit status 127 As a variation on this theme (triggers being run when the triggered package is unconfigured in the middle of an upgrade from squeeze to wheezy), I just got the following: 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 Processing triggers for install-info ... configured to not write apport reports Errors were encountered while processing: doc-base E: Sub-process /usr/bin/dpkg returned an error code (1) With: $ dpkg -l libuuid-perl perl-base perl doc-base Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== iF doc-base 0.9.5 utilities to manage online documentation iU libuuid-perl 0.02-4+b2 Perl extension for using UUID interfaces as defined in e2fsprogs ii perl 5.10.1-17squeeze2 Larry Wall's Practical Extraction and Report Language ii perl-base 5.10.1-17squeeze2 minimal Perl system i.e. new libuuid-perl is unpacked, while dpkg, perl and doc-base are still the squeeze version. Cheers, Julien -- Julien Cristau julien.cris...@logilab.fr Logilab http://www.logilab.fr/ Informatique scientifique gestion de connaissances -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
On Wed, Aug 01, 2012 at 12:22:22AM +0200, Julien Cristau wrote: On Mon, Jul 16, 2012 at 14:19:03 +0200, Julien Cristau wrote: On Sun, Jul 15, 2012 at 18:26:50 +0200, Guillem Jover wrote: W/o having looked yet at the details I'd say this *seems* like #671711, which I'm not planning on fixing for wheezy as it would introduce regressions on other situations, and given that this behaviour has been around since the introduction of triggers, and while quite unfortunate it's something that will have to be worked around on the affected packages because older dpkg will not be able to handle this correctly anyway. Going to look now, to make sure the above is the case. That seems likely. What is the recommended workaround here? Should package postinsts just ignore failures when called with 'triggered', or is there a better way? Ping? Any ideas? I can understand the reasons not to fix the trigger bug, sounds like something not that tricky. However, given how it actually break the upgrade process, and will like likely in the future, it would probably be a good idea to document somewhere for package maintainers how to work around it. I can commit to test further during the freeze if the upgrade process goes well, and having this kind of documentation to point maintainers at would help. If it already exists, please share the link. bert. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
Hi, berta...@ptitcanardnoir.org wrote: I can understand the reasons not to fix the trigger bug, sounds like something not that tricky. However, given how it actually break the upgrade process, and will like likely in the future, it would probably be a good idea to document somewhere for package maintainers how to work around it. I suspect the answer is some combination of use noawait where possible and do such-and-such in your postinst scripts, which after a careful analysis of different upgrade paths I can guarantee will cause the intended effect of the trigger to happen at some point in the upgrade. Unfortunately I have not done that careful analysis, so I can't give the appropriate advice, but hopefully someone else will be able to (using triggers.txt for reference and letting us know if they run into any questions). Thanks and sorry I have nothing better to offer, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
On Mon, Jul 16, 2012 at 14:19:03 +0200, Julien Cristau wrote: On Sun, Jul 15, 2012 at 18:26:50 +0200, Guillem Jover wrote: W/o having looked yet at the details I'd say this *seems* like #671711, which I'm not planning on fixing for wheezy as it would introduce regressions on other situations, and given that this behaviour has been around since the introduction of triggers, and while quite unfortunate it's something that will have to be worked around on the affected packages because older dpkg will not be able to handle this correctly anyway. Going to look now, to make sure the above is the case. That seems likely. What is the recommended workaround here? Should package postinsts just ignore failures when called with 'triggered', or is there a better way? Ping? Any ideas? Cheers, Julien signature.asc Description: Digital signature
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
On Sun, Jul 15, 2012 at 18:26:50 +0200, Guillem Jover wrote: W/o having looked yet at the details I'd say this *seems* like #671711, which I'm not planning on fixing for wheezy as it would introduce regressions on other situations, and given that this behaviour has been around since the introduction of triggers, and while quite unfortunate it's something that will have to be worked around on the affected packages because older dpkg will not be able to handle this correctly anyway. Going to look now, to make sure the above is the case. That seems likely. What is the recommended workaround here? Should package postinsts just ignore failures when called with 'triggered', or is there a better way? Thanks, Julien signature.asc Description: Digital signature
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
On Sat, Jul 7, 2012 at 14:51:32 +0200, bertagaz wrote: In an attempt to test upgrading Squeeze to Wheezy now that the Big Wheezy Freeze has come, it failed at the dist-upgrade step. I installed a fresh Debian Squeeze and tested from it. I wanted first to see if it would be possible to upgrade with a simple and graphical method (using update-manager and synaptic), as it was quite complicated for the Lenny-Squeeze upgrade. Ended up with this result, so I also tested using plain apt-get upgrade and dist-upgrade. Same result, dist-upgrade fails on python-support postintallation script with the following error: Processing triggers for python-support ... /usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory dpkg: error processing python-support (--unpack): subprocess installed post-installation script returned error exit status 127 Looks like dpkg is running triggers from packages that aren't configured. Can dpkg folks have a look at this? Bug#680626 has the details. Thanks, Julien signature.asc Description: Digital signature
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
On Sun, 2012-07-15 at 17:14:26 +0200, Julien Cristau wrote: On Sat, Jul 7, 2012 at 14:51:32 +0200, bertagaz wrote: In an attempt to test upgrading Squeeze to Wheezy now that the Big Wheezy Freeze has come, it failed at the dist-upgrade step. I installed a fresh Debian Squeeze and tested from it. I wanted first to see if it would be possible to upgrade with a simple and graphical method (using update-manager and synaptic), as it was quite complicated for the Lenny-Squeeze upgrade. Ended up with this result, so I also tested using plain apt-get upgrade and dist-upgrade. Same result, dist-upgrade fails on python-support postintallation script with the following error: Processing triggers for python-support ... /usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory dpkg: error processing python-support (--unpack): subprocess installed post-installation script returned error exit status 127 Looks like dpkg is running triggers from packages that aren't configured. Can dpkg folks have a look at this? Bug#680626 has the details. W/o having looked yet at the details I'd say this *seems* like #671711, which I'm not planning on fixing for wheezy as it would introduce regressions on other situations, and given that this behaviour has been around since the introduction of triggers, and while quite unfortunate it's something that will have to be worked around on the affected packages because older dpkg will not be able to handle this correctly anyway. Going to look now, to make sure the above is the case. regards, guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680626: Squeeze-Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
Package: upgrade-reports Severity: normal Hi, In an attempt to test upgrading Squeeze to Wheezy now that the Big Wheezy Freeze has come, it failed at the dist-upgrade step. I installed a fresh Debian Squeeze and tested from it. I wanted first to see if it would be possible to upgrade with a simple and graphical method (using update-manager and synaptic), as it was quite complicated for the Lenny-Squeeze upgrade. Ended up with this result, so I also tested using plain apt-get upgrade and dist-upgrade. Same result, dist-upgrade fails on python-support postintallation script with the following error: Processing triggers for python-support ... /usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory dpkg: error processing python-support (--unpack): subprocess installed post-installation script returned error exit status 127 I noticed that the python2.7 transition is supposed to be almost finished, might be related. Attached is the transcript of the full upgrade session, including several `dpkg -l` at different steps. bert. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
