8 Oct
2012
8 Oct
'12
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