PDA

View Full Version : [SOLVED] Lucid update issues



sports fan Matt
November 11th, 2009, 01:58 AM
I did a clean reinstall of Karmic Via CD and when that was all finished I planned to upgrade to lucid. It didn't go well:confused:

update-manager -d: does not notify me of an upgrade. Any advice?

alphacrucis2
November 11th, 2009, 02:14 AM
I did a clean reinstall of Karmic Via CD and when that was all finished I planned to upgrade to lucid. It didn't go well:confused:

update-manager -d: does not notify me of an upgrade. Any advice?


Edit your /etc/apt/sources.list file. Change all occurrences of karmic -> lucid. Then

sudo apt-get update
sudo apt-get dist-upgrade

sports fan Matt
November 11th, 2009, 02:18 AM
Apparently I switched everything over in my sources list but still have karmic entries even after updating..hmm.

Fetched 10.5MB in 13s (762kB/s)
W: GPG error: http://deb.opera.com etch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9A2F76A9D1A0061
W: GPG error: http://ppa.launchpad.net karmic Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EF4186FE247510BE
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/restricted/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]

W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/universe/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]

W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/multiverse/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]

whoop
November 11th, 2009, 02:21 AM
Apparently I switched everything over in my sources list but still have karmic entries even after updating..hmm.

Fetched 10.5MB in 13s (762kB/s)
W: GPG error: http://deb.opera.com etch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9A2F76A9D1A0061
W: GPG error: http://ppa.launchpad.net karmic Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EF4186FE247510BE
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/restricted/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]

W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/universe/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]

W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/multiverse/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]

These look like specific karmic entries, they just have been changed to lucid (but they don't exist). You can comment them out in sources.

alphacrucis2
November 11th, 2009, 02:23 AM
Apparently I switched everything over in my sources list but still have karmic entries even after updating..hmm.

Fetched 10.5MB in 13s (762kB/s)
W: GPG error: http://deb.opera.com etch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F9A2F76A9D1A0061
W: GPG error: http://ppa.launchpad.net karmic Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EF4186FE247510BE
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/restricted/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]

W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/universe/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]

W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/multiverse/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]

1. Remove all PPA's
2. Change to use the main server. Looks like your us.archive.ubuntu.com doesn't have the lucid packages on it yet.

ranch hand
November 11th, 2009, 02:46 AM
Mine works fine on the "us" setting.

sports fan Matt
November 11th, 2009, 02:49 AM
I'll get there..latest round of not founds:

Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/restricted/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]
Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/universe/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]
Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/multiverse/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]
Some index files failed to download, they have been ignored, or old ones used instead.

xebian
November 11th, 2009, 02:53 AM
I'll get there..latest round of not founds:

Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/restricted/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]
Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/universe/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]
Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/multiverse/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]
Some index files failed to download, they have been ignored, or old ones used instead.

Comment out these. Think for a moment. There is no such thing as lucid-backports yet. This makes relevance only when master..monkeys is released.

LKjell
November 11th, 2009, 02:57 AM
I'll get there..latest round of not founds:

Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/restricted/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]
Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/universe/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]
Failed to fetch http://us.archive.ubuntu.com/ubuntu/lucid-backports/dists/main/multiverse/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.134 80]
Some index files failed to download, they have been ignored, or old ones used instead.


# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.

deb http://archive.ubuntu.com/ubuntu/ lucid main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://archive.ubuntu.com/ubuntu/ lucid-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu/ lucid universe
deb http://archive.ubuntu.com/ubuntu/ lucid-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://archive.ubuntu.com/ubuntu/ lucid multiverse
deb http://archive.ubuntu.com/ubuntu/ lucid-updates multiverse

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu lucid partner
# deb-src http://archive.canonical.com/ubuntu lucid partner

deb http://archive.ubuntu.com/ubuntu/ lucid-security main restricted
deb http://archive.ubuntu.com/ubuntu/ lucid-security universe
deb http://archive.ubuntu.com/ubuntu/ lucid-security multiverse

sports fan Matt
November 11th, 2009, 03:12 AM
I now copied, saved the above list: sudo do-release-upgrade -d
Checking for a new ubuntu release
No new release found


and update-manager -d does not show the upgrade..perhaps checking for lts since it is 10.04 under release upgrade would help?

LKjell
November 11th, 2009, 03:24 AM
Do to check what you have.

lsb_release -a

alphacrucis2
November 11th, 2009, 03:30 AM
I now copied, saved the above list: sudo do-release-upgrade -d
Checking for a new ubuntu release
No new release found


and update-manager -d does not show the upgrade..perhaps checking for lts since it is 10.04 under release upgrade would help?

Just do

sudo apt-get dist-upgrade

That should be enough to get you onto Lucid now you have manually changed your sources and run sudo apt-get update. Nothing more should be needed.

sports fan Matt
November 11th, 2009, 03:30 AM
Heh...I am running lucid. I wonder why there wasn't a prompt to restart my system. Distributor ID: Ubuntu
Description: Ubuntu lucid (development branch)
Release: 10.04
Codename: lucid

alphacrucis2
November 11th, 2009, 03:33 AM
Heh...I am running lucid. I wonder why there wasn't a prompt to restart my system. Distributor ID: Ubuntu
Description: Ubuntu lucid (development branch)
Release: 10.04
Codename: lucid

It should have installed kernel 2.6.32-2 unless you were already running that under karmic I would have expected it to want to reboot.

ranch hand
November 11th, 2009, 03:34 AM
Update Manager knows nothing about this yet. It would be great to forget Update mangler for the rest of testing.

To get this thing going though, is easy;


sudo apt-get update
and
[code]
sudo apt-get dist-upgrade
[code]
EDIT
A Little late I see. Good we have another victim.

sports fan Matt
November 11th, 2009, 03:35 AM
one thing im wondering though...About ubuntu says: im using 9.10. Weird

LKjell
November 11th, 2009, 03:38 AM
That is because nobody has written a new documentation.

If it bother you much you can edit the /etc/lsb-release file to karmic...

Which makes me think that lucid and karmic is the same at this state.

alphacrucis2
November 11th, 2009, 03:40 AM
That is because nobody have written a new documentation.

Yep. We are not even at alpha yet.

VMC
November 11th, 2009, 03:43 AM
one thing im wondering though...About ubuntu says: im using 9.10. Weird

sox fan, Read this link (http://ubuntuforums.org/showthread.php?t=1308574). There is one more file to edit. Especially this post (http://ubuntuforums.org/showpost.php?p=8215796&postcount=6).

LKjell
November 11th, 2009, 03:48 AM
sox fan, Read this link (http://ubuntuforums.org/showthread.php?t=1308574). There is one more file to edit. Especially this post (http://ubuntuforums.org/showpost.php?p=8215796&postcount=6).
He is one of the lucky that does not need to edit that file. It was fixed last Thursday.

papangul
November 11th, 2009, 03:53 AM
Isn't dist-upgrade supposed to be used in a "stable release to stable release" scenario only?

Think of it, if you are running lucid and the state of archive at certain point of time is such that dist-upgrade will create problems(like the problem with the pulseaudio package that occured recently) then dist upgrading from karmic to lucid at that point of time is bound to create the exactly same problem.

23meg
November 11th, 2009, 03:58 AM
Isn't dist-upgrade supposed to be used in a "stable release to stable release" scenario only?

Think of it, if you are running lucid and the state of archive at certain point of time is such that dist-upgrade will create problems(like the problem with the pulseaudio package that occured recently) then dist upgrading from karmic to lucid at that point of time is bound to create the exactly same problem.

Which is why it's generally a better idea, especially for less experienced testers, to begin testing with a milestone release.

LKjell
November 11th, 2009, 04:02 AM
You need a strong gut feeling or read through the change logs to be certain when to do dist-upgrade, partial-upgrade..

alphacrucis2
November 11th, 2009, 04:08 AM
Isn't dist-upgrade supposed to be used in a "stable release to stable release" scenario only?

Think of it, if you are running lucid and the state of archive at certain point of time is such that dist-upgrade will create problems(like the problem with the pulseaudio package that occured recently) then dist upgrading from karmic to lucid at that point of time is bound to create the exactly same problem.

Yeah but you just read what is says it is going to do and if you don't like it you say no and do an aptitude safe-upgrade first. Then check the changes log for whatever a dist-upgrade wanted to trash to see if it is legit.

papangul
November 11th, 2009, 04:23 AM
Which is why it's generally a better idea, especially for less experienced testers, to begin testing with a milestone release.
It would be nice if there was a freeze on the repos for a period of 12 hours or so during the release of milestone releases.

ranch hand
November 11th, 2009, 04:24 AM
It would be nice if there was a freeze on the repos for a period of 12 hours or so during the release of milestone releases.
You are no FUN at ALL.

papangul
November 11th, 2009, 04:38 AM
You are no FUN at ALL.
I need a break from all the fun I am having with karmic.

ranch hand
November 11th, 2009, 04:44 AM
Ah, that could be it. Your own problems or forum problems?

My Kinky Kitten install is just purring along very nicely.

VMC
November 11th, 2009, 04:39 PM
It would be nice if there was a freeze on the repos for a period of 12 hours or so during the release of milestone releases.

Why stop there. Just freeze until first alpha.

23meg
November 11th, 2009, 06:19 PM
It would be nice if there was a freeze on the repos for a period of 12 hours or so during the release of milestone releases.

There's a soft freeze lasting more than four days before milestone releases, during which only very high priority uploads go through.

VMC
November 11th, 2009, 11:56 PM
There's a soft freeze lasting more than four days before milestone releases, during which only very high priority uploads go through.

Ok, I see now what he meant by that freeze statement, My bad.

papangul
November 12th, 2009, 02:29 AM
There's a soft freeze lasting more than four days before milestone releases, during which only very high priority uploads go through.
Strange, I came across many milestone releases of karmic but the daily updates never seemed to slow down, even for a single day. Thats how I gathered the idea that milestone releases are non event for the repos!