Ubuntu
update-manager package

problem with gutsy distribution upgrade

Bug #150404 reported by alex4a
2
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Michael Vogt

Bug Description

Binary package hint: update-manager

This is the second time i try to upgrade to Gustsy.
The first time was from feisty and I got an error message saying : Could not install the upgrades. This happened during the download stage.
I then downloaded the Live CD and installed it from scratch, ran the update manager and I got the same error message.

ProblemType: Package
Architecture: i386
Date: Sun Oct 7 20:24:49 2007
DistroRelease: Ubuntu 7.10
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:I wasn't able to locate file for the libc6 package. This might mean you need to manually fix this package.

NonfreeKernelModules: ath_hal
Package: update-manager 1:0.76
PackageArchitecture: all
SourcePackage: update-manager
Title: package update-manager 1:0.76 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:I wasn't able to locate file for the libc6 package. This might mean you need to manually fix this package.
Uname: Linux 4a-3 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux

Revision history for this message
alex4a (alex-4a) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bugreport as attachments to your bug report? Thanks in advance.

Changed in update-manager:
assignee: nobody → mvo
status: New → Incomplete
Revision history for this message
alex4a (alex-4a) wrote :

Sorry for the delay, here is the attached file

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for this addtional information.

Was "'apt.log" the only file in /var/log/dist-upgrade/ ? There should be more, especially main.log and term.log.

Thanks,
 michael

Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in update-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.