[MASTER] Upgrade fails if it runs for more than 2 days (race with in the cleanup code)

[alex]

Binary package hint: update-manager

Installed: Ubuntu 6.10 amd 64 version with latest all updates exept 4:
 - libx11-6, libx11-data, libx11-dev, tzdata

Install those updates, afterwards press "upgrade" button to upgrade distribution from 6.10 to 7.04

[Michael Vogt (mvo)]

Thanks for your bugreport.

From the logs, it looks like the upgrade was runing for three days, is that correct?

[..]
2007-04-20 19:58:29,738 WARNING no activity on terminal for 240 seconds (Configuring libssl0.9.8)
2007-04-23 11:53:08,132 ERROR SystemError from cache.commit(): installArchives() failed

Thanks,
 Michael

[alex (alex27a)]

Hello!

I run the update on friday and I left. I don't know what happened since
then. I've checked it today and I got this message...

On 4/23/07, Michael Vogt <email address hidden> wrote:
>
> Thanks for your bugreport.
>
> >From the logs, it looks like the upgrade was runing for three days, is
> that correct?
>
> [..]
> 2007-04-20 19:58:29,738 WARNING no activity on terminal for 240 seconds
> (Configuring libssl0.9.8)
> 2007-04-23 11:53:08,132 ERROR SystemError from cache.commit():
> installArchives() failed
>
> Thanks,
> Michael
>
> ** Changed in: update-manager (Ubuntu)
> Status: Unconfirmed => Needs Info
>
> --
> Ubuntu distribution upgrade from 6.10 to 7.04 failed
> https://bugs.launchpad.net/bugs/109195
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Launchpad Janitor (janitor)]

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

[Gregor Müllegger (gregor-muellegger)]

This bug is still not fixed. I run the upgrade over 2 days.

[Michael Vogt (mvo)]

Hello Gregor,

here is the error:
2009-11-10 03:50:40,117 ERROR got an error from dpkg for pkg: '/var/cache/apt/archives/sun-java6-jre_6-15-1_all.deb': 'Unterprozess neues pre-installation-Skript gab den Fehlerwert 2 zurück

this error is unreleated to the original bug that was discussed here, I close it again, please check bug #378802 for a similar report