Wheezy updates failing

If you're sticking with wheezy, which has now been removed from the primary archives as it's no longer even old-old-stable... why are you looking for updates? There probably won't be any.

...replace 'mirrordirector' with 'legacy'

The point of breaking the system, is that the pacakges no longer have updates

Not any more I think

He wants a new image

Thanks, I'll try that. First part looks successful.

No, I am chasing an issue which appears to affect only older OS versions, and these won't have been updated in the last couple of years. As these RPi cards are in use, rather than for playing, I prefer to see whether simply updating the OS to its latest patch level might affect the issue.

I'm investigating an issue, and would like ensure that the OS in question is at least its latest version.

Just as confirmation, I went through this a few days ago. (see the 'Trouble with apt-get" thread, which I appropriated...)

My sources.list is:

deb

and seems to work fine. (I haven't tried to update the lists in sources.list.d as I don't really need them.)

-- Pete --

Thanks! I missed that thread, since at the time I had no intention of, or reason to, update!

if systemd is your reason for not wanting stretch, perhaps you can dist-upgrade to a newer devuan distro... ?

(I know _I_ dislike systemd, so I can totally understand)

On 26/08/2019 08:08, Big Bad Bob wrote: []

It was just to be sure that I did have, as far as possible, a fully patched version without the well-documented nausea associated with any RPi Linux version upgrade.

I thought my recent in-situ upgrade (Stretch -> Buster) went surprisingly well seeing that it was the first Raspbian attempt at in-situ upgrades. By and large it 'just worked' even though it took its time (but then so do Fedora in-situ upgrades and they've been doing them for the last 10 distro versions). But, you MUST have Stretch fully updated before attempting it.

Over the years I've in-situ upgraded from squeeze > wheezy > jessie > stretch > buster, plus upgraded the Pi its running on from B (256M) > B (512MB) > 2B > 3B > 3B+ > 4B. Just make sure its up to date on the current version and fully backed up before you begin.

---druck

Yep, agreed, but the Stretch->Buster upgrade was rather different to simply editing a few files and running the standard update again like we did previously. Indeed, it has noticeable similarities to the Fedora version upgrade.

Ditto. On the x86 side I have had a system which has been in-situ upgraded repeatedly since 1995 and is still working fine. Most recently was an i386->amd64 crossgrade, which I don?t recommend in general but I really didn?t want to capture and reproduce a quarter century of local configuration (or lose the mtime on /etc/hostname l-)

I don?t recall it being particularly involved...

I didn't say whether it was more or less involved - just different.

It had a glitch or two, all easily overcome, so I expect/hope its next iteration will be better.

I didn't think it was any different than previous ones. Update the apt sources, and do a full upgrade. There were a few obsolete packages that could be removed afterwards, but that's common.

My main problem was some of images were getting low on space for storing all the package upgrades, fixed by removing the swap file temporarily. But I will need to re-jiggle partitions before the next upgrade.

I upgraded my dozen Pis to Buster just before getting a new Pi 4, then moved the image from the Pi 3B+ to the Pi 4. The only thing needed before the move was to do a rpi-update to get the new Pi 4 specific files in to /boot. That's been necessary when moving up each Pi generation.

---druck

I did exactly what it said in this page:

and thought that running "sudo apt dist-upgrade" worked somewhat differently to the Jessie -> Stretch upgrade - in particular because dist- upgrade promptly pulled down a large selection of packages before installing them (with periodic questions about how I wanted deal with several specific packages), before completing the process with a reboot. This is similar to the in-situ version upgrade that Fedora has used for the last five years, i.e. not like the Wheezy->Jessie and Jessie->Stretch upgrades, which IIRC were just a rather larger update and without an immediate reboot being required.