issues trying to upgrade to gutsy

Asked by cardinals_fan on 2007-07-21

I want to upgrade to Gutsy from Feisty. I have update-manager 1:0.59.23, but when I run update-manager -d, nothing happens. Is there any other way to upgrade to Gutsy (without downloading 700 megabytes and installing)? Below is what I get when I update/upgrade, prior to running update-manager -d:

jesse@jesse-desktop:~$ sudo apt-get update
Get:1 http://security.ubuntu.com feisty-security Release.gpg [191B]
Ign http://security.ubuntu.com feisty-security/main Translation-en_US
Ign http://security.ubuntu.com feisty-security/restricted Translation-en_US
Get:2 http://us.archive.ubuntu.com feisty Release.gpg [191B]
Ign http://us.archive.ubuntu.com feisty/main Translation-en_US
Ign http://us.archive.ubuntu.com feisty/restricted Translation-en_US
Get:3 http://archive.ubuntu.com feisty-proposed Release.gpg [191B]
Ign http://archive.ubuntu.com feisty-proposed/restricted Translation-en_US
Ign http://archive.ubuntu.com feisty-proposed/main Translation-en_US
Ign http://security.ubuntu.com feisty-security/universe Translation-en_US
Ign http://security.ubuntu.com feisty-security/multiverse Translation-en_US
Hit http://security.ubuntu.com feisty-security Release
Ign http://us.archive.ubuntu.com feisty/universe Translation-en_US
Ign http://us.archive.ubuntu.com feisty/multiverse Translation-en_US
Get:4 http://us.archive.ubuntu.com feisty-updates Release.gpg [191B]
Ign http://us.archive.ubuntu.com feisty-updates/main Translation-en_US
Ign http://us.archive.ubuntu.com feisty-updates/restricted Translation-en_US
Ign http://us.archive.ubuntu.com feisty-updates/universe Translation-en_US
Ign http://us.archive.ubuntu.com feisty-updates/multiverse Translation-en_US
Ign http://archive.ubuntu.com feisty-proposed/multiverse Translation-en_US
Ign http://archive.ubuntu.com feisty-proposed/universe Translation-en_US
Hit http://archive.ubuntu.com feisty-proposed Release
Hit http://us.archive.ubuntu.com feisty Release
Hit http://security.ubuntu.com feisty-security/main Packages
Hit http://us.archive.ubuntu.com feisty-updates Release
Hit http://archive.ubuntu.com feisty-proposed/restricted Packages
Hit http://security.ubuntu.com feisty-security/restricted Packages
Hit http://security.ubuntu.com feisty-security/restricted Sources
Hit http://security.ubuntu.com feisty-security/main Sources
Hit http://us.archive.ubuntu.com feisty/main Packages
Hit http://us.archive.ubuntu.com feisty/restricted Packages
Hit http://us.archive.ubuntu.com feisty/restricted Sources
Hit http://us.archive.ubuntu.com feisty/main Sources
Hit http://archive.ubuntu.com feisty-proposed/main Packages
Hit http://archive.ubuntu.com feisty-proposed/multiverse Packages
Hit http://archive.ubuntu.com feisty-proposed/universe Packages
Hit http://security.ubuntu.com feisty-security/multiverse Sources
Hit http://security.ubuntu.com feisty-security/universe Sources
Hit http://security.ubuntu.com feisty-security/universe Packages
Hit http://security.ubuntu.com feisty-security/multiverse Packages
Hit http://us.archive.ubuntu.com feisty/multiverse Sources
Hit http://us.archive.ubuntu.com feisty/universe Sources
Hit http://us.archive.ubuntu.com feisty/universe Packages
Hit http://us.archive.ubuntu.com feisty/multiverse Packages
Hit http://us.archive.ubuntu.com feisty-updates/main Packages
Hit http://us.archive.ubuntu.com feisty-updates/restricted Packages
Hit http://us.archive.ubuntu.com feisty-updates/restricted Sources
Hit http://archive.ubuntu.com feisty-proposed/restricted Sources
Hit http://archive.ubuntu.com feisty-proposed/main Sources
Hit http://archive.ubuntu.com feisty-proposed/multiverse Sources
Hit http://archive.ubuntu.com feisty-proposed/universe Sources
Hit http://us.archive.ubuntu.com feisty-updates/main Sources
Hit http://us.archive.ubuntu.com feisty-updates/multiverse Sources
Hit http://us.archive.ubuntu.com feisty-updates/universe Sources
Hit http://us.archive.ubuntu.com feisty-updates/universe Packages
Hit http://us.archive.ubuntu.com feisty-updates/multiverse Packages
Fetched 4B in 1s (3B/s)
Reading package lists... Done
jesse@jesse-desktop:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
jesse@jesse-desktop:~$

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
cardinals_fan
Solved:
2007-07-23
Last query:
2007-07-23
Last reply:
2007-07-22
Cesare Tirabassi (norsetto) said : #1

You have to add the gutsy repositories if you want to upgrade.
Two words of caution also:

1 - Gutsy Tribe 3 is ALPHA software. It should not be used for production but only for debugging. Do expect to have a number of problems which you must be prepared to solve, perhaps manually.

2 - It is NOT recommended to attempt a manual upgrade, unless you know what you are doing and are prepared to solve problems manually.

I would heartily advise you to wait until gutsy is officially released.

open a terminal and run...

sudo update-manager -d

update manager should appear, but a little 'upgrade to 7.10' button should be near the top.

on the 'no 700mb' thing, you could always have a friend download for you and give you a disc or something. Or do something cheeky, and go to a library or someplace similar, and download it there.

cardinals_fan (jesseblehman) said : #4

This is what I get when I run sudo update-manager -d

jesse@jesse-desktop:~$ sudo update-manager -d
Password:
warning: could not initiate dbus
current dist not found in meta-release file
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
jesse@jesse-desktop:~$

cardinals_fan (jesseblehman) said : #5

I've done more looking, and have found that the meta-release file for development releases is at http://changelogs.ubuntu.com/meta-release-development. The update manager is clearly just reading the http://changelogs.ubuntu.com/meta-release file, which doesn't include gutsy. Any ideas on how to make it view the development file?

cardinals_fan (jesseblehman) said : #6

Yet more information:

jesse@jesse-desktop:~$ update-manager --dist-upgrade
ERROR:root:not handled expection:
Traceback (most recent call last):

  File "/usr/bin/update-manager", line 78, in <module>
    controler = DistUpgradeControler(view, datadir=data_dir)

  File "/usr/lib/python2.5/site-packages/DistUpgrade/DistUpgradeControler.py", line 150, in __init__
    os.O_RDWR|os.O_CREAT|os.O_APPEND|os.O_SYNC, 0644)

OSError: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt.log'

ERROR:root:failed to import apport python module, can't report bug: No module named python_hook

cardinals_fan (jesseblehman) said : #7

All i had to do was paste the information at http://changelogs.ubuntu.com/meta-release-development into the meta-release file. After that, everything has worked and I now have gutsy.

Tyler Rick (tyler.rick) said : #8

Hmm, that didn't work for me...

Even *after* I added the gutsy section from http://changelogs.ubuntu.com/meta-release-development into my ~/.update-manager-core/meta-release, it still didn't want to detect that there were new packages available...

> sudo update-manager -d
warning: could not initiate dbus
current dist not found in meta-release file

When I click "Check", it displays this on the command line:
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

And in the GUI it says: Your system is up-to-date.

Any ideas what I'm doing wrong?

Tyler Rick (tyler.rick) said : #9

(I too have update-manager version 1:0.59.23)

Tyler Rick (tyler.rick) said : #10

Odd! I haven't done anything except add this line to my /etc/apt/sources.list:

deb http://archive.ubuntu.com/ubuntu/dists/ feisty-proposed main restricted universe multiverse

and just a second ago it popped up with a message saying there were new updates to install. I clicked on that and sure enough, it had 17 updates to install AND it said "New distribution release '7.10' is available". How exciting!

Not sure if adding feisty-proposed is what enabled me to see the option to upgrade to 7.10 or not, but for whatever reason, it's there now.

Tyler Rick (tyler.rick) said : #11

Ack, I spoke too soon!

After installing all the updates provided by feisty-proposed, it told me I needed to restart, so I let it. When it booted back up, I tried doing sudo update-manager -d but this time it reverted to its old behavior, and it didn't show the option to upgrade to 7.10 anymore.

I decided to downgrade dbus since I remember that was one of the packages I just upgraded. I figure if I downgrade it, it may pop up again to tell me that I have new updates to install.

Synaptic -> Package -> Force version ->
Selected 1.0.2-1ubuntu3 (feisty) instead of 1.0.2-1ubuntu4 (feisty-proposed)

It said "System restart required" but this time I cancelled it.

It said "Software updates available" almost immediately afterwards. I clicked on that icon, let it update its list, and sure enough, it listed dbus as a proposed update again and also said "New distribution release '7.10' is available.

I cannot explain this behavior, but I'm glad I was able to find a workaround...

cardinals_fan (jesseblehman) said : #12

I guess that that solved your problem, but I just added http://changelogs.ubuntu.com/meta-release-development into /usr/lib/python2.5/site-packages/UpdateManager/Core/MetaRelease.py

wtgee (wtgee) said : #13

I'm having this problem too on fiesty amd64. I have tried all of the above and so far nadda...

wtgee (wtgee) said : #14

Sorry, I spoke too soon as well...

Adding the section to the ~/.update-manager-core/meta-release did work for me.

Joey Stanford (joey) said : #15

me too. I had to paste into ~/.update-manager-core/meta-release

Erik Lander (erik-lander) said : #16

"rm -rf ~/.update-manager-core" worked for me

Wait, so what's the work around?

Copying http://changelogs.ubuntu.com/meta-release-development into ~/.update-manager-core/meta-release doesn't work.

`rm -rf ~/.update-manager-core` doesn't work.

`sudo update-manager -d` doesn't work.
I get this exact same error:
"jesse@jesse-desktop:~$ sudo update-manager -d
Password:
warning: could not initiate dbus
current dist not found in meta-release file
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
jesse@jesse-desktop:~$"

**Also**

`sudo update-manager --dist-upgrade` only installs ubuntu-desktop and therefore all the programs I removed that's included in it.

I run it again and it can't find any packages to install.

Any advice?

moschops (simon-waddington) said : #19

I did the

Copying http://changelogs.ubuntu.com/meta-release-development into ~/.update-manager-core/meta-release

trick and it made no difference

I also copied it to /root/.update-manager/meta-release

also no difference (but I guess update manager when run with sudo looks at your home directory from before so ~/.update-manager-core is right)

Then I tried the downgrade of dbus trick without rebooting - after that update-manager -c -d offered an upgrade and from there things have started downloading okay - I have not completed the update process yet.