"update-manager -d" in Feisty presents no option to upgrade to Gutsy

Bug #129392 reported by Bruce Miller
8
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

I am running Kubuntu 7.04 Feisty Fawn. I have masochistic tendencies and am prepared to try running a development version of Gutsy Gibbon. However, running "sudo update-manager -d" does not offer an option to upgrade to the new development release.

There are several complaints by other users on www.ubuntuforums.org who have run into the same problem. However, if anyone has already filed a bug on this problem, I have not been able to find it.

I have the latest version of update-manager recommended on help.ubuntu.com for updating from Feisty to Gutsy.

bruce@Herodotus:~$ uname -a
Linux Herodotus 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux
bruce@Herodotus:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 7.04
Release: 7.04
Codename: feisty
bruce@Herodotus:~$ apt-cache policy update-manager
update-manager:
  Installed: 1:0.59.23
  Candidate: 1:0.59.23
  Version table:
 *** 1:0.59.23 0
        500 http://ca.archive.ubuntu.com feisty-updates/main Packages
        500 http://archive.ubuntu.com feisty-updates/main Packages
        100 /var/lib/dpkg/status
     1:0.59.20 0
        500 http://ca.archive.ubuntu.com feisty/main Packages
        500 http://archive.ubuntu.com feisty/main Packages
bruce@Herodotus:~$

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

Thanks for your bugreport.

I can not reproduce this behaviour here, If I use 0.59.23 I get the upgrade button. Can you please attach ~/.update-manager-core/meta-release? Can you also please let me know if you are behind a proxy or if you use dialup?

Thanks,
 Michael

Changed in update-manager:
status: New → Incomplete
Revision history for this message
Jared (jared-alleyne) wrote :

I'm having the exact same problem except I'm running regular Ubuntu, not Kubuntu. That shouldn't make much of a difference though. I attached my ~/.update-manager-core/meta-release file, hope it helps!

Revision history for this message
Jared (jared-alleyne) wrote :

I forgot to add this into my comment, but when running apt-cache policy update-manager, I get

jared@jared-laptop:~$ apt-cache policy update-manager
update-manager:
  Installed: 1:0.59.23
  Candidate: 1:0.59.23
  Version table:
 *** 1:0.59.23 0
        100 /var/lib/dpkg/status

which is much less than the person who posted the bug report had.

Revision history for this message
Jared (jared-alleyne) wrote :

Found this somewhere else:

To fix this, replace your ~/.update-manager-core/meta-release file with the text found here:

http://changelogs.ubuntu.com/meta-release-development

Revision history for this message
Tommaso R. Donnarumma (tawmas) wrote :

It looks like the workaround found by Jared offers you a one-time only opportunity to upgrade.

For me, it worked the first time I tried, but I didn't have the time to do the upgrade at once. But when I came back to do the upgrade, the button was gone, no matter that my ~/.update-manager-core/meta-release file is up-to-date with the text from http://changelogs.ubuntu.com/meta-release-development

I also tried to update my ~/.update-manager-core/meta-release file again from the given url, although the text appeared unmodified at eye inspection, but of course it just didn't work because the "new" text was indeed unmodified...

Revision history for this message
Mário Vrablanský (vrablansky) wrote :

Same for me .I`ve full updated Feisty and i`m not behind proxy. Let me know if more info is needed

mario@server:~$ apt-cache policy update-manager
update-manager:
  Installed: 1:0.59.23
  Candidate: 1:0.59.23
  Version table:
 *** 1:0.59.23 0
        500 http://sk.archive.ubuntu.com feisty-updates/main Packages
        100 /var/lib/dpkg/status
     1:0.59.20 0
        500 http://sk.archive.ubuntu.com feisty/main Packages

Revision history for this message
Mário Vrablanský (vrablansky) wrote :

Same for me .I`ve full updated Feisty and i`m not behind proxy. Let me know if more info is needed

mario@server:~$ apt-cache policy update-manager
update-manager:
  Installed: 1:0.59.23
  Candidate: 1:0.59.23
  Version table:
 *** 1:0.59.23 0
        500 http://sk.archive.ubuntu.com feisty-updates/main Packages
        100 /var/lib/dpkg/status
     1:0.59.20 0
        500 http://sk.archive.ubuntu.com feisty/main Packages

Revision history for this message
Jørgen Tellnes (jorgis) wrote :

Confirmed in a fresh Feisty install. Jared`s fix does not give me the ability to upgrade, it still says my system is up-to-date.

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

Thanks for this additional information.

Can you please try to run it without "sudo" ? Just as your regular user? Does that help? You will need a installed gksu for later.

Thanks,
 Michael

Changed in update-manager:
status: Incomplete → Confirmed
Revision history for this message
Michael Vogt (mvo) wrote :

I suspect this is a duplicate of #127263 but I would like to confirm that it works when you start it as a user.

Changed in update-manager:
status: Confirmed → Incomplete
Revision history for this message
Bruce Miller (brm0423) wrote :

I am the original reporter of this bug. I regret that other >18hr/day commitments delayed my returning to this thread.

@Michael Vogt: running update-manager -d as a user resolved my problem. BTW, I do not have a proxy but do have a fairly fast (8Mbps) cable connection.

Thank you for your help.

Revision history for this message
Ryan Zeigler (rzeigler) wrote :

I had a similar problem, with a different cause. It turns out was, I connected to a wireless internet ap that redirected me to a website for me to agree to the terms of use. My meta-release file was actually replaced with the contents of this redirection page. Perhaps some kind of sanity checks should be performed on the meta-release file before a new one is written.

Revision history for this message
Jnik (grjohnis) wrote :

Had the same problem.
Starting update manager as user or with sudo/gksudo didn't provide me with the upgrade button.

Adding

Dist: gutsy
Name: Gutsy Gibbon
Version: 7.10
Date: Thu, 18 Oct 2007 12:00:00 UTC
Supported: 0
Description: This is the 7.10 release
Release-File: http://archive.ubuntu.com/ubuntu/dists/gutsy/Release
ReleaseNotes: http://archive.ubuntu.com/ubuntu/dists/gutsy/main/dist-upgrader-all/current/ReleaseAnnouncement
UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/gutsy/main/dist-upgrader-all/current/gutsy.tar.gz
UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/gutsy/main/dist-upgrader-all/current/gutsy.tar.gz.gpg

to the ~/.update-manager-core/meta-release as jared proposed did the trick.

Revision history for this message
Michael R. Head (burner) wrote :

I've found a workaround that works for me.

$ rm -rf $HOME/.update-manager-core
$ update-manager -d # "upgrade" button should appear

What's more, I can reliably reproduce this bug by doing this:
$ rm -rf $HOME/.update-manager-core
$ update-manager
$ update-manager -d # and now it won't be possible to get the "upgrade" button to appear

Revision history for this message
Michael R. Head (burner) wrote :

By the way, I'm using the us.archive.ubuntu.com mirror...

Revision history for this message
Kristoffer Lundén (kristoffer-lunden) wrote :

Got the same issue. Looking at my ~/.update-manager-core/meta-release it appears sane and whole, it has got entries for everything since warty, just not one for gutsy. Got all repositories enabled, including proposed and updates etc, am fully updated and have the correct version of update-manager. Just FYI. :)

Revision history for this message
Geoffrey Pursell (geoffp) wrote :

"@Michael Vogt: running update-manager -d as a user resolved my problem. BTW, I do not have a proxy but do have a fairly fast (8Mbps) cable connection."

Me too! Although: I did also delete the .update-manager* dirs from my home folder. At least it works!

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Revision history for this message
Trance (emilien-girault) wrote :

I experiment the same problem ; I want to update to Gutsy and update-manager doesn't show me the update button.
I deleted my ~/.update-manager-core/meta-release but it didn't fix anything. Moreover, I'm behind a proxy.

Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

Please don't comment on duplicate bugs, comment on the main bug.

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.