[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#680626: marked as done (Squeeze->Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0)

Your message dated Wed, 27 Mar 2019 19:58:00 +0000
with message-id <051e9bca-acfc-01c9-c30c-da9926fafe15@thykier.net>
and subject line Re: Squeeze->Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
has caused the Debian Bug report #680626,
regarding Squeeze->Wheezy: dist-upgrade fails, /usr/bin/python unable to load libssl.so.1.0.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
680626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680626
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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.

--- End Message ---
--- Begin Message --- 
On Sat, 7 Jul 2012 14:51:32 +0200 bertagaz <bertagaz@ptitcanardnoir.org>
wrote:
> 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.
> 
> 
> 

Hi,

I am closing this bug caused by dpkg triggers (long overdue).

 * It was worked around in Wheezy.
 * We have begun using -noawait triggers much more aggressively (along
   with CI jobs to check for trigger cycles).
 * The buster version of dpkg will fix a few remaining issues with
   triggers (these are tracked as #901127 and #910819).

Thanks,
~Niels

--- End Message ---
Reply to: