[Pkg-octave-devel] Bug#696377: octave3.2: 35 octave-* packages fail to upgrade from lenny to squeeze: octave3.0: error while loading shared libraries: liblapack.so.3gf: cannot open shared object file: No such file or directory
On 2012-12-26 10:38, Rafael Laboissiere wrote:
> * Thomas Weber <tweber@debian.org> [2012-12-23 18:09]:
>> On Thu, Dec 20, 2012 at 07:08:27AM +0100, Andreas Beckmann wrote:
>>> Package: octave3.2 Version: 3.2.4-8 Severity: serious Tags: squeeze
>>> User: debian-qa@lists.debian.org Usertags: piuparts Control: affects
>>> -1 + octave-ad octave-zenity
>>>
>>> during a test with piuparts I noticed many octave packages failing to
>>> upgrade from lenny to squeeze.
>>
>> To be honest, I don't quite see the value of checking for upgrades
>> from lenny to squeeze at this point of the release cycle - octave3.0
>> was removed in 2010. Putting it another way, how many users do we help
>> by fixing this issue now?
I'm currently doing lenny->squeeze->wheezy upgrade tests to find
packages that "did something wrong (but did not fail)" in lenny or
lenny->squeeze that makes the upgrade to wheezy fail (or makes
removing/purging in wheezy or some other checks in wheezy fail).
Upgrading long grown systems should work without problems ...
Of course this uncovers installability issues in lenny or lenny->squeeze
upgrade issues. I don't expect most of these to get fixed in squeeze -
but they should be documented anyway. I'll also implement workarounds
(if possible) in piuparts for non-leaf packages.
So, in case you have a suggestion how to work around this ... let me know.
> I am curious: why is this bug popping out only now? Why was it not
> discovered during the release cycle of squeeze?
without checking any logs ...: piuparts has seen a lot of improvements
since then and that probably increased the test coverage of the archive
(including old releases)
or maybe the problem was already discovered by earlier tests, but nobody
had the time to analyze the failed logfiles and therefore no bugs were filed
Andreas
PS: for wheezy I filed a few similar bugs w.r.t. octave3.2 removal that
were finally resolved by adding a few more Breaks (in lapack and related
packages, but not octave itself) to hint apt to use a better ordering of
the operations ... i.e. remove octave3.2 earlier
Reply to: