Wheezy updates failing

[David Taylor]

Yes, I know wheezy is out of date, but....

sudo apt-get update fails with:

Err http://mirrordirector.raspbian.org wheezy/main armhf Packages
404 Not Found
Err http://mirrordirector.raspbian.org wheezy/contrib armhf Packages
404 Not Found
Err http://mirrordirector.raspbian.org wheezy/non-free armhf Packages
404 Not Found
Err http://mirrordirector.raspbian.org wheezy/rpi armhf Packages
404 Not Found

What should I add the /etc/apt/source.list ? I really don't want to
have to upgrade the RPi to Stretch.

--
Cheers,
David
Web: http://www.satsignal.eu

[Richard Kettlewell]

http://archive.raspberrypi.org/ has wheezy.

--
https://www.greenend.org.uk/rjk/

[The Natural Philosopher]

https://www.raspberrypi.org/forums/viewtopic.php?t=237469

...replace 'mirrordirector' with 'legacy'

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


--
To ban Christmas, simply give turkeys the vote.

[The Natural Philosopher]

Not any more I think



--
There’s a mighty big difference between good, sound reasons and reasons
that sound good.

Burton Hillis (William Vaughn, American columnist)

[The Natural Philosopher]

On 11/07/2019 12:13, Roger Bell_West wrote:

> On 2019-07-11, David Taylor wrote:
>> Yes, I know wheezy is out of date, but....
>

> 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.
>
He wants a new image

[David Taylor]

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

[David Taylor]

On 11/07/2019 12:18, The Natural Philosopher wrote:
> On 11/07/2019 12:13, Roger Bell_West wrote:
>> On 2019-07-11, David Taylor wrote:
>>> Yes, I know wheezy is out of date, but....
>>
>> 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.
>>
> He wants  a new image

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.

[David Taylor]

On 11/07/2019 12:13, Roger Bell_West wrote:
> On 2019-07-11, David Taylor wrote:

>> Yes, I know wheezy is out of date, but....
>

> 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.

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

[Pete]

In article <qg7b4c$pdr$1...@dont-email.me>,

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 http://legacy.raspbian.org/raspbian/ wheezy main contrib non-free rpi
deb-src http://legacy.raspbian.org/raspbian/ wheezy main contrib non-free rpi

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 --

[David Taylor]

On 11/07/2019 18:59, Pete wrote:
> 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:
>

> debhttp://legacy.raspbian.org/raspbian/ wheezy main contrib non-free rpi
> deb-srchttp://legacy.raspbian.org/raspbian/ wheezy main contrib non-free rpi

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

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

[Big Bad Bob]

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)



--
(aka 'Bombastic Bob' in case you wondered)

'Feeling with my fingers, and thinking with my brain' - me

'your story is so touching, but it sounds just like a lie'
"Straighten up and fly right"

[David Taylor]

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

> 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)

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.

[Martin Gregorie]

On Mon, 26 Aug 2019 16:43:22 +0100, David Taylor wrote:

> On 26/08/2019 08:08, Big Bad Bob wrote:
> []
>> 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)
>
> 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.


--
Martin | martin at
Gregorie | gregorie dot org

[druck]

On 26/08/2019 17:25, Martin Gregorie wrote:
> 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

[Martin Gregorie]

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.

[Richard Kettlewell]

Martin Gregorie <mar...@mydomain.invalid> writes:
> On Mon, 26 Aug 2019 20:37:53 +0100, druck wrote:
>> On 26/08/2019 17:25, Martin Gregorie wrote:
>>> 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.

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-)

> 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.

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

--
https://www.greenend.org.uk/rjk/

[Martin Gregorie]

On Tue, 27 Aug 2019 10:45:43 +0100, Richard Kettlewell wrote:

>
> 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.

[druck]

On 26/08/2019 20:57, Martin Gregorie wrote:
> On Mon, 26 Aug 2019 20:37:53 +0100, druck wrote:
>
>> On 26/08/2019 17:25, Martin Gregorie wrote:
>>> 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.
>>
> 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.

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

[Martin Gregorie]

I did exactly what it said in this page:

https://www.raspberrypi.org/blog/buster-the-new-version-of-raspbian/

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.

[druck]

On 28/08/2019 19:41, Martin Gregorie wrote:
> I did exactly what it said in this page:
>
> https://www.raspberrypi.org/blog/buster-the-new-version-of-raspbian/
>
> 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.

That's the way every Debian based distro does it! All packages are
download first on any upgrade, during installation some may ask
questions when altering config files. A reboot is performed to ensure
all the new packages are now being run

You can get away without rebooting after minor upgrades, but you will
have to restart anything application or service that has been upgraded,
as otherwise the old versions will carry on running.

> 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.

I don't recall Wheezy, Jessie and Stretch doing anything different than
the above!

---druck

[Richard Kettlewell]

druck <ne...@druck.org.uk> writes:
> On 28/08/2019 19:41, Martin Gregorie wrote:
>> I did exactly what it said in this page:
>>
>> https://www.raspberrypi.org/blog/buster-the-new-version-of-raspbian/
>>
>> 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.
>
> That's the way every Debian based distro does it! All packages are
> download first on any upgrade, during installation some may ask
> questions when altering config files. A reboot is performed to ensure
> all the new packages are now being run
>
> You can get away without rebooting after minor upgrades, but you will
> have to restart anything application or service that has been
> upgraded, as otherwise the old versions will carry on running.

In particular you won’t get a new kernel without 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.
>
> I don't recall Wheezy, Jessie and Stretch doing anything different
> than the above!

Indeed. It’s worked like that for decades.

--
https://www.greenend.org.uk/rjk/

[Martin Gregorie]

OK. Seems like my punkin been baking way too long.