package gcc-4.2-base 4.2.1-5ubuntu4 failed to install/upgrade:

[James Tait]

Binary package hint: gcc-4.2

Apport reported that the package failed to upgrade or install following reboot after upgrade to Gutsy beta using "upgrade-manager -c -d"

ProblemType: Package
Architecture: amd64
Date: Sat Sep 29 08:44:43 2007
Dependencies:

DistroRelease: Ubuntu 7.10
ErrorMessage:
 ErrorMessage: no package named `gcc-4.2-base' is installed, cannot configure
NonfreeKernelModules: video
Package: gcc-4.2-base 4.2.1-5ubuntu4
PackageArchitecture: amd64
SourcePackage: gcc-4.2
Title: package gcc-4.2-base 4.2.1-5ubuntu4 failed to install/upgrade:
Uname: Linux ferrari 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux

[James Tait (jamestait)]

This didn't get reported in quite the way I'd intended -- the AppPort report happened to come to my attention just after I'd done something else to cause something to crash and I initially thought this would be that crash report. Nonetheless, I feel this report still has some merit even if the description isn't quite right.

I ran "upgrade-manager -c -d" just before I went to bed, thinking it would take several hours to download all the new packages and I'd continue in the morning. I disabled the screensaver and so on, so no extra processes would be running during the upgrade. However, when I came to complete the upgrade the following morning, gcc-4.2 was one of many packages that apparently could not be installed. I didn't take a note of all the failed packages as there were so many, but I did have to spend a couple of hours cleaning things up in an interactive aptitude session for the apt caches to clear themselves up and the upgrade to complete.

The only thing that occurred to me was that I do have a cron job to automatically download updates each morning -- but I expect most if not all Ubuntu users also do, and I'd be surprised if I were the only person to leave the upgrade running overnight.

Now the upgrade has completed I'm very happy with the beta release, but something certainly went amiss with the upgrade process. Are there any logs I can provide that might help discover what?

[Matthias Klose (doko)]

I'm reassigning to apport. There is no reason why gcc-4.2-base or gcc-4.2 should fail to install. Any log is missing from this report.

There seems to be a problem with apport offering to submit very uncomplete bug reports. Reassigning for that reason to the apport package.

[Martin Pitt (pitti)]

Indeed this is another case of poor reports from apt. This one is probably just a followup failure from a failed dependency. Michael, do you agree that apt should not create reports which don't have a terminal log?

[Jean-Baptiste Lallement (jibel)]

Can we close this report ? The report issue has been fixed in apport I guess and it's unrelated with the reporter's issue ?

[James Tait (jamestait)]

I certainly didn't see any similar instances on the upgrade to Hardy. I won't pretend to understand what might have caused it, but any chance of getting logs has long since passed. I'm happy to close this.

[Martin Pitt (pitti)]

Closing then, thanks for your feedback!