Our (pi-apps) automation frequently discovers broken raspbian mirrors
https://github.com/Botspot/pi-apps/acti ... step:7:874
https://github.com/Botspot/pi-apps/acti ... step:7:865
https://github.com/Botspot/pi-apps/acti ... step:7:868

This mirror currently 404's from the automation (github actions servers) and my home location (USA) both at the time of posting.
Why is http://raspbian.raspberrypi.org/ mirrorbrain resolving to this address?

Additionally, what is the root repository that http://raspbian.raspberrypi.org/ mirrorbrain is mirroring? Is it https://archive.raspbian.org/ directly or is there another public raspberypi.org/com domain that does not use mirrorbrain?

It seems to me that mirrorbrain is flawed by design (when it comes to robustness) allowing up to 24 hours of failures before removal. You should instead be using mirrorcache. A writeup of the benefits can be seen here https://opensuse.github.io/MirrorCache/mb_compare/ . Additionally, it seems VERY bad to me to be reliant on 11+ year old abandoned software (mirrorbrain hasn't had a release since 2014 and hasn't had a commit since 2015) while mirrorcache is actively maintained (by openSUSE nonetheless!).

made other moderators aware, but next time just use this link. https://www.raspberrypi.com/contact/

Thanks.

Still getting errors as recently as 30 minutes ago https://github.com/Botspot/pi-apps/acti ... step:7:866

Errors still occurring. Please have this removed with urgency.

(I assume that what you are talking about is when you try to do an "apt update" or "apt upgrade" and it figures out what the nearest mirror is, but that mirror is down, so it just errors out instead of trying another mirror. Is that right?)

Assuming so, yes, I've had a similar situation. I think I fixed it by adding a line in my /etc/hosts file like this:

w.x.y.z badmachine.com

where w.x.y.z is the IP address of a known good mirror (goodmachine). Then, when the apt system tries to access badmachine, it goes to goodmachine.

This works, but is obviously a kludge.

There should be a way to just tell it "Don't use badmachine".

My posts may be "controversial" and/or out-of-sync with the party line.

Nothing I write should in any way be taken as an official statement by any organization connected with (any branch of) RPi and/or any of its funding sources.

BigRedMailbox wrote: ↑

Tue Aug 20, 2024 5:58 pm

(I assume that what you are talking about is when you try to do an "apt update" or "apt upgrade" and it figures out what the nearest mirror is, but that mirror is down, so it just errors out instead of trying another mirror. Is that right?)

I don't need a workaround. I am fully aware of how the system works and could workaround the issue if I wanted to. I am posting this for the broader community and highlight that the (default) mirrorbrain system is fundamentally broken. It should NOT be redirecting to known broken (404) webpages for multiple weeks.

I have already provided the solution but it is up to https://archive.raspbian.org/ (Raspberry Pi LTD) maintainers to implement it.
I do not require any further community member contact.

Well, good. Sounds like you're all set, then.

My posts may be "controversial" and/or out-of-sync with the party line.

Nothing I write should in any way be taken as an official statement by any organization connected with (any branch of) RPi and/or any of its funding sources.

theofficialgman wrote: ↑

Sat Aug 24, 2024 4:55 pm

but it is up to https://archive.raspbian.org/ (Raspberry Pi LTD) maintainers to implement it.

From what I understand, Raspberry Pi Ltd do not maintain Raspbian. It is an independent project (that may receive funding and support from RPi). Pi should be able to pass a message on to the right people though.

Unreadable squiggle

theofficialgman wrote: ↑

Sat Aug 24, 2024 4:55 pm

[I do not require any further community member contact.

Then why are you here, this forum is exclusively for community member contact,
Instead contact per e-mail.

From what I understand, Raspberry Pi Ltd do not maintain Raspbian.

Of course, technically, nobody maintains "Raspbian" anymore, since it no longer exists.

That was the point of renaming it to "Raspi OS" - because (for reasons I never fully understood, but am willing to accept at face value) it is no longer Raspbian. I.e., the implication here is that the term "Raspbian" actually means something (i.e., it isn't just a brand name, like Kleenex) and that that meaning is no longer valid.

Or something like that...

My posts may be "controversial" and/or out-of-sync with the party line.

Nothing I write should in any way be taken as an official statement by any organization connected with (any branch of) RPi and/or any of its funding sources.

BigRedMailbox wrote: ↑

Sun Aug 25, 2024 10:09 am

From what I understand, Raspberry Pi Ltd do not maintain Raspbian.

Of course, technically, nobody maintains "Raspbian" anymore, since it no longer exists.

That was the point of renaming it to "Raspi OS" - because (for reasons I never fully understood, but am willing to accept at face value) it is no longer Raspbian. I.e., the implication here is that the term "Raspbian" actually means something (i.e., it isn't just a brand name, like Kleenex) and that that meaning is no longer valid.

Of course Raspbian exists. Where else would the 32-bit version of Raspberry Pi OS get its packages from?

The name was also (incorrectly) used for the OS. The OS was renamed to avoid confusion between the OS and the repository project.

Unreadable squiggle

BigRedMailbox wrote: ↑

Sun Aug 25, 2024 10:09 am

From what I understand, Raspberry Pi Ltd do not maintain Raspbian.

Of course, technically, nobody maintains "Raspbian" anymore, since it no longer exists.

That was the point of renaming it to "Raspi OS" - because (for reasons I never fully understood, but am willing to accept at face value) it is no longer Raspbian. I.e., the implication here is that the term "Raspbian" actually means something (i.e., it isn't just a brand name, like Kleenex) and that that meaning is no longer valid.

Or something like that...

You may want to read here
https://www.raspbian.org/

And it was renamed because he, Raspbian maintained, didn't want the name to be used for a none Raspbian based OS etc.