8 Oct
2012
8 Oct
'12
1:51 p.m.
I'm attempting to upgrade my VPS from Etch to Lenny and then onto Squeeze.
For some reason it is failing at the first step. What is happening is shown below. What is
the solution?
Thanks
Neil
myserver:~# aptitude update
Ign http://apt-cacher.lon.bitfolk.com lenny Release.gpg
Ign http://apt-cacher.lon.bitfolk.com lenny/updates Release.gpg
Ign http://apt-cacher.lon.bitfolk.com lenny Release
Ign http://apt-cacher.lon.bitfolk.com lenny/updates Release
Err http://apt-cacher.lon.bitfolk.com lenny/main Packages
404 Not Found [IP: 85.119.80.211 80]
Err http://apt-cacher.lon.bitfolk.com lenny/contrib Packages
404 Not Found [IP: 85.119.80.211 80]
Err http://apt-cacher.lon.bitfolk.com lenny/main Sources
404 Not Found [IP: 85.119.80.211 80]
Err http://apt-cacher.lon.bitfolk.com lenny/contrib Sources
404 Not Found [IP: 85.119.80.211 80]
Err http://apt-cacher.lon.bitfolk.com lenny/updates/main Packages
404 Not Found [IP: 85.119.80.211 80]
Err http://apt-cacher.lon.bitfolk.com lenny/updates/contrib Packages
404 Not Found [IP: 85.119.80.211 80]
Reading package lists... Done
W: Couldn't stat source package list http://apt-cacher.lon.bitfolk.com
lenny/main Packages
(/var/lib/apt/lists/apt-cacher.lon.bitfolk.com_debian_ftp.uk.debian.org_debian_dists_lenny_main_binary-i386_Packages)
- stat (2 No such file or directory)
W: Couldn't stat source package list http://apt-cacher.lon.bitfolk.com
lenny/contrib Packages
(/var/lib/apt/lists/apt-cacher.lon.bitfolk.com_debian_ftp.uk.debian.org_debian_dists_lenny_contrib_binary-i386_Packages)
- stat (2 No such file or directory)
W: Couldn't stat source package list http://apt-cacher.lon.bitfolk.com
lenny/updates/main Packages
(/var/lib/apt/lists/apt-cacher.lon.bitfolk.com_debian_security.debian.org_dists_lenny_updates_main_binary-i386_Packages)
- stat (2 No such file or directory)
W: Couldn't stat source package list http://apt-cacher.lon.bitfolk.com
lenny/updates/contrib Packages
(/var/lib/apt/lists/apt-cacher.lon.bitfolk.com_debian_security.debian.org_dists_lenny_updates_contrib_binary-i386_Packages)
- stat (2 No such file or directory)
W: Couldn't stat source package list http://apt-cacher.lon.bitfolk.com
lenny/main Packages
(/var/lib/apt/lists/apt-cacher.lon.bitfolk.com_debian_ftp.uk.debian.org_debian_dists_lenny_main_binary-i386_Packages)
- stat (2 No such file or directory)
W: Couldn't stat source package list http://apt-cacher.lon.bitfolk.com
lenny/contrib Packages
(/var/lib/apt/lists/apt-cacher.lon.bitfolk.com_debian_ftp.uk.debian.org_debian_dists_lenny_contrib_binary-i386_Packages)
- stat (2 No such file or directory)
W: Couldn't stat source package list http://apt-cacher.lon.bitfolk.com
lenny/updates/main Packages
(/var/lib/apt/lists/apt-cacher.lon.bitfolk.com_debian_security.debian.org_dists_lenny_updates_main_binary-i386_Packages)
- stat (2 No such file or directory)
W: Couldn't stat source package list http://apt-cacher.lon.bitfolk.com
lenny/updates/contrib Packages
(/var/lib/apt/lists/apt-cacher.lon.bitfolk.com_debian_security.debian.org_dists_lenny_updates_contrib_binary-i386_Packages)
- stat (2 No such file or directory)
W: You may want to run apt-get update to correct these problems
myserver:~#
8 Oct
8 Oct
2:17 p.m.
Hello Neil,
On 2012-10-08 14:51, Neil Morris wrote:
I'm attempting to upgrade my VPS from Etch to
Lenny and then onto
Squeeze.
For some reason it is failing at the first step. What is happening is
shown below. What is the solution?
Thanks
Neil
myserver:~# aptitude update
Ign http://apt-cacher.lon.bitfolk.com [1] lenny Release.gpg
Ign http://apt-cacher.lon.bitfolk.com [1] lenny/updates Release.gpg
Ign http://apt-cacher.lon.bitfolk.com [1] lenny Release
Ign http://apt-cacher.lon.bitfolk.com [1] lenny/updates Release
Err http://apt-cacher.lon.bitfolk.com [1] lenny/main Packages
404 Not Found [IP: 85.119.80.211 80]
This is because the Lenny repos does not exist any more upstream (I
fell into this trap myself). There are basically two different workflows
you can follow:
1.1 Ask Bitfolk to do a snapshot of your VPS, so that you have
something to fall back onto in case the next step does not work.
1.2 Once you have a snapshot, dist-upgrade directly to Squeeze. This
should work with some minor hassles (such as different formatting in
config files etc), but nothing especially serious.
Failing that:
2.1 Ask Bitfolk to arrange for a migration VPS
2.2 Migrate all your software and settings
2.3 Decommission the old VPS
Regards,
Jan Henkins
2:25 p.m.
Hi Neil, Jan,
On Mon, Oct 08, 2012 at 03:17:40PM +0100, jan(a)henkins.za.net wrote:
This is because the Lenny repos does not exist any
more upstream (I
fell into this trap myself). There are basically two different
workflows you can follow:
I think there is a third option which may have a greater chance of
success: archive.debian.org.
End of life releases such as lenny still exist on
archive.debian.org. I've used it in order to achieve normal package
installs on older machines I've had to work on. I've never done a
dist-upgrade against it, but I can't think of any particular reason
why that shouldn't work.
sources.lst for that would be:
deb http://apt-cacher.lon.bitfolk.com/debian/archive.debian.org/debian/ lenny main
(note no updates or volatile lines for this one)
So I would have thought that would allow a dist-upgrade to lenny and
then from there follow release notes to dist-upgrade to squeeze.
Disk snapshots are always a good idea before any major upgrade of
course..
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
2:36 p.m.
Hi,
I think there is a third option which may have a
greater chance of
success: archive.debian.org.
End of life releases such as lenny still exist on
archive.debian.org. I've used it in order to achieve normal package
installs on older machines I've had to work on. I've never done a
dist-upgrade against it, but I can't think of any particular reason
why that shouldn't work.
This works: I recommend it. I used it to update to the latest Etch when
I did my Etch -> Lenny -> Squeeze migration at the point that Squeeze
was released. Note: I used to to upgrade to the latest Etch as that was
no longer in the main archive. At the time Lenny was in the main archive.
Regards,
@ndy
--
andyjpb(a)ashurst.eu.org
http://www.ashurst.eu.org/
0x7EBA75FF
2:45 p.m.
On 2012-10-08 15:25, Andy Smith wrote:
Hi Neil, Jan,
On Mon, Oct 08, 2012 at 03:17:40PM +0100, jan(a)henkins.za.net wrote:
This is something I did not know, thanks for the good news! :-D
This is because the Lenny repos does not exist
any more upstream (I
fell into this trap myself). There are basically two different
workflows you can follow:
I think there is a third option which may have a greater chance of
success: archive.debian.org. End of life releases such as lenny still exist on
archive.debian.org. I've used it in order to achieve normal package
installs on older machines I've had to work on. I've never done a
dist-upgrade against it, but I can't think of any particular reason
why that shouldn't work.
From the README on the site:
---start---
The following releases are archived on this site:
Archive Releases Directory
Debian buzz, rex, bo, hamm,
slink, potato, woody,
sarge, etch, lenny debian/
Debian Security slink, potato, woody,
sarge, etch, lenny debian-security/
Debian Non-US slink, potato, woody debian-non-US/
AMD64 sarge debian-amd64/
Debian Volatile sarge, etch, lenny debian-volatile/
Debian Backports sarge, etch, lenny backports.org/
Look at the individual directories README file for more information.
---end---
Awesome!
sources.lst for that would be:
deb
http://apt-cacher.lon.bitfolk.com/debian/archive.debian.org/debian/
lenny main
(note no updates or volatile lines for this one)
It seems that whatever was in volatile up to the point of archiving is
all there.
So I would have thought that would allow a
dist-upgrade to lenny and
then from there follow release notes to dist-upgrade to squeeze.
I have to pip in here to say that I have always had a relatively good
result whenever I had to bunny-hop over an intermediate version with
Debian. Still, if you don't have the time to sit down and fix what will
inevitably be broken, then using Andy's suggestion is the way to go. I
guess I like living dangerously! :-)
Regards,
Jan Henkins
3:02 p.m.
Thanks Jan, Andy and Andy
I shall try the Andy and Andy recommended approaches.
However before I do this I read the following message from the archives:
Notes for those moving to a pvops kernel (Debian lenny, Gentoo?, upstream)
http://lists.bitfolk.com/lurker/message/20080820.163101.70ccaa59.en.html
Is this still an issue with the Xen code that I need to be aware of?
cheers
Neil
5:49 p.m.
Hi Neil,
On Mon, Oct 08, 2012 at 05:02:57PM +0200, Neil Morris wrote:
Notes for those moving to a pvops kernel (Debian
lenny, Gentoo?, upstream)
http://lists.bitfolk.com/lurker/message/20080820.163101.70ccaa59.en.html
Is this still an issue with the Xen code that I need to be aware of?
Not really an issue as such.. Yes it is the case that from Debian
lenny onwards the best kernel to use is the normal
linux-image-686-bigmem one. As a Xen user under etch you will have
linux-image-xen-686, so all the upgrade will do is upgrade that. It
will take a manual install of linux-image-686-bigmem to switch
between them.
It is not crucial, as both will work.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
4240
days inactive
4240
days old
6 comments
4 participants
participants (4)
-
Andy Bennett -
Andy Smith -
jan＠henkins.za.net -
Neil Morris