upgrade-manager install failed

Bug #197305 reported by Chris Vaisvil
8
Affects Status Importance Assigned to Milestone
python-central (Ubuntu)
Fix Released
High
Matthias Klose

Bug Description

I am upgrading from a clean install of Gutsy to Hardy on a 4-gig USB flash drive.
Twice during install I received a popup box stating that the upgrade manager
could not be installed and that it may be in an unusable state consider
filling a bug report.

It is still upgrading some 10 hours later so I can't get to the system to drag out anymore information yet.

I used the command "sudo update-manager -d" in a Gutsy terminal to start this install

Chris

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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

Changed in update-manager:
status: New → Incomplete
Revision history for this message
Chris Vaisvil (chrisvaisvil) wrote :

Hi, these are the files you wanted in a zip.

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

Thanks for your bugreport.

The error is in the python-central package, I will reassign:

Preparing to replace update-manager 1:0.81 (using .../update-manager_1%3a0.87.9_all.deb) ...
86.deb) ...
Traceback (most recent call last):
  File "/usr/bin/pycentral", line 1685, in <module>
    main()
  File "/usr/bin/pycentral", line 1679, in main
    rv = action.run(global_options)
  File "/usr/bin/pycentral", line 1180, in run
    pkg.prepare(used_runtimes, old_used_runtimes, old_pkg)
  File "/usr/bin/pycentral", line 803, in prepare
    rt.remove_byte_code(removed_fs)
AttributeError: 'NoneType' object has no attribute 'remove_byte_code'
dpkg: error processing /var/cache/apt/archives/update-manager_1%3a0.87.9_all.deb (--unpack):
 subprocess pre-installation script returned error exit status 1

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

This bug might be fixed already, but I would like to have confirmation on this.

Changed in update-manager:
importance: Undecided → High
milestone: none → ubuntu-8.04
status: Incomplete → Confirmed
Colin Watson (cjwatson)
Changed in python-central:
assignee: nobody → doko
Revision history for this message
James Westby (james-w) wrote :

Hi,

This looks a lot like bug #197160 (and also bug #196335),
which was fixed in python-central 0.5.61ubuntu1.

Thanks,

James

Revision history for this message
Matthias Klose (doko) wrote :

this was fixed in 0.5.62ubuntu1:

  * pkgprepare, pkginstall: Always use the default runtime as a last resort.

Changed in python-central:
status: Confirmed → Fix Released
Revision history for this message
Chris Vaisvil (chrisvaisvil) wrote : Re: [Bug 197305] Re: upgrade-manager install failed
  • unnamed Edit (1.7 KiB, text/html; charset=ISO-8859-1)

I don't get it....
"Always use the default runtime as a last
resort"

I tried to upgrade and lost the ability to communicate to the internet and
had no way to fix it.

On Fri, Apr 4, 2008 at 2:21 PM, Matthias Klose <email address hidden> wrote:

> this was fixed in 0.5.62ubuntu1:
>
> * pkgprepare, pkginstall: Always use the default runtime as a last
> resort.
>
>
> ** Changed in: python-central (Ubuntu)
> Status: Confirmed => Fix Released
>
> --
> upgrade-manager install failed
> https://bugs.launchpad.net/bugs/197305
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "python-central" in Ubuntu: Fix Released
>
> Bug description:
> I am upgrading from a clean install of Gutsy to Hardy on a 4-gig USB
> flash drive.
> Twice during install I received a popup box stating that the upgrade
> manager
> could not be installed and that it may be in an unusable state consider
> filling a bug report.
>
> It is still upgrading some 10 hours later so I can't get to the system to
> drag out anymore information yet.
>
> I used the command "sudo update-manager -d" in a Gutsy terminal to start
> this install
>
> Chris
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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