continuing error upgrading Sarge to Etch

This is a continuation of the Sarge to Etch via Knoppix post. But, I've been able to gather considerable info since then:

I've got 2 errors that if I can get fixed I'm betting will solve my problem.

Running apt-get -f upgrade results in the following 2 errors:

Couldn't stat source package list file: stable/main Packages
(/var/lib/apt/lists/_cdrom_dists_stable_main_binary-i386_Packages)
- stat (2 no such file or directory)

AND

Couldn't stat source package list file: stable/contrib Packages
(/var/lib/apt/lists/_cdrom_dists_stable_contrib_binary-i386_Packages)
- stat (2 no such file or directory)

apt-get update no matter how many time I run it, doesn't fix this issue. How do I create that file and/or directory?!?!?!!?

Thanks in advance for your help!!!!

0

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

continuing error upgrading

You can give apt-get and dpkg a lobotomy:

1. check your /etc/apt/sources.list file and comment out any references to the Sarge install CDs and repositories.

2. dpkg --forget-avail

3. cd /var/lib/apt/lists && rm *

Then rebuild your source database:

4. dselect update

Continuing error upgrading

dpkg --forget-avail didn't work but dpkg --clear-avail seemed to. But I'm still getting the same error after following the rest of it.

When I do an apt-get update I get a new error (so there's progress at least) that that glibc6_yadda_yadda.gz cannot be sourced (or something like that, it flies by too quickly to read).

Could I just copy a glibc.gz file somewhere and call it good?

Continuing error upgrading

What's in your sources.list file? I've never seen that message about libc6...gz can't be sourced.

continuing error upgrading

and again thank you for your help!!!!

Now we're talking

OK that cleared up everything... Almost. So here's the deal. My kernel is 2.2 upgrade won't work till I'm kernel 2.4 or better. I've tried apt-get install kernel-2.4.2.27 or something like that, but the package doesn't exist anymore. When I look at the list of availible kernels they're all 2.6.

If I try to install kernel 2.6 I hit that glibc dependancy and can't find a way around it. So I'm figuring I need a 2.4 kernel. Without compiling my own kernel (make menuconfig and make xconfig both crap out when I try starting them) how can I just go nicely and easily from 2.2 to 2.4?

Is there a fancy apt-get install kernel2.4 statement that will look for all the availible 2.4 kernels around in the world or am I hosed and need to build my own kernel from scrtch?

Thank you thank you thank you! My apt-sources soooooooooooooooo needed a labotomy!!!!

Now we're talking

An upgrade from kernel 2.2 will be very painful because so many packages would have changed so much that they will not upgrade correctly either.

The easiest way, if the machine is not acting as a server for database, web, etc, is to backup all your user's files and reinstall from scratch. To get a list of what you have currently installed (so that you can install it on the new system):
dpkg --get-selections > mylist
Then save the file 'mylist' somewhere else.
Also copy and save your /etc/{passwd, group, shadow} files.
After doing a minimal install, do:
dpkg --set-selections < mylist
apt-get dselect-upgrade
Then restore your users and their passwords, restore your user files, and restore the configuration of your services.

The other way is tricky; make sure you back up everything or the system and date may be lost; also make a list of your installed packages as described above. Anyway, you can use "debootstrap" to do the install. I can't remember the details of debootstrap since it's been a few years since I used it, but it might erase the 'target' directory before proceeding with the installation.

I can think of other methods, but they all take many many hours - you can easily spend 20 hours upgrading manually.

bummer

The only thing I'm really worried about losing is the content of our database, and even then it's not a huge deal. This server is our internal web server hosting our Intranet site. So if it goes down for good and I have to recreate the data in it, oh well.

I was afraid that was going to be the path I'd have to take. Thank you for all your help, your instructions have been very useful!!!

bummer

In that case, I'd say make a copy of configuration files in /etc for reference later, save your database somewhere else (another HD, DVD, another computer), then do a complete reinstall. Since you're running such an old system, even using "dpkg --get/set-selections" may not work; many package names have changed, packages have been split, etc. It is probably far better to install from scratch and add what you need. Any database should still be accessible by current software. Keep in mind that PHP scripts may break and there may be other similar nuisances. This is just the sort of thing that happens if a system is not upgraded more frequently. On the other hand, I would guess that the system had been working very well and no one saw a reason to upgrade anything.

Syndicate content