Dev1 Galaxy Forum / Sudden change in repositories

Re: Sudden change in repositories

dummy@example.com (fsmithred) — Wed, 15 Jul 2026 17:01:52 +0000

daedalus-security is fixed.

Components: main contrib non-free non-free-firmware

Re: Sudden change in repositories

dummy@example.com (chris2be8) — Wed, 15 Jul 2026 16:09:08 +0000

I would point a web browser at http://ch.deb.devuan.org/ and start looking around for a name or address to contact. Or any other clue.

Re: Sudden change in repositories

dummy@example.com (Andre4freedom) — Wed, 15 Jul 2026 07:45:11 +0000

Here comes another "inconsistency" of another package- and patch-mirror:

The repository ch.deb.devuan.org is no longer working, since a few days ago - at all.
Before that, a re-issuing the apt update / apt upgrade command solved the thing momentarily.

I did switch to de.deb.devuan.org and this works well.

andre@sapporo:~$ sudo apt update
[sudo] password for andre:
Ign:1 http://ch.deb.devuan.org/merged excalibur InRelease
Ign:2 http://ch.deb.devuan.org/merged excalibur-security InRelease
Ign:3 http://ch.deb.devuan.org/merged excalibur-updates InRelease
Err:4 http://ch.deb.devuan.org/merged excalibur Release
404 Not Found [IP: 147.78.194.22 80]
Err:5 http://ch.deb.devuan.org/merged excalibur-security Release
404 Not Found [IP: 147.78.194.22 80]
Err:6 http://ch.deb.devuan.org/merged excalibur-updates Release
404 Not Found [IP: 147.78.194.22 80]
Error: The repository 'http://ch.deb.devuan.org/merged excalibur Release' no longer has a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
Error: The repository 'http://ch.deb.devuan.org/merged excalibur-security Release' no longer has a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
Error: The repository 'http://ch.deb.devuan.org/merged excalibur-updates Release' no longer has a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.

Whom must I send this message to?
Have a good day,
André

Re: Sudden change in repositories

dummy@example.com (fsmithred) — Tue, 14 Jul 2026 23:57:15 +0000

Maintenance of bookworm-security got moved to the LTS team. They'll probably hear about it soon and fix it. FWIW, you can still do upgrades, and the nonfree firmware doesn't change often, so you're probably not missing anything.
https://lists.debian.org/debian-announc … 00007.html

Re: Sudden change in repositories

dummy@example.com (Micronaut) — Tue, 14 Jul 2026 21:55:20 +0000

But up till yesterday it was on that line in sources.list and DID NOT cause any error messages. What changed and why?

Re: Sudden change in repositories

dummy@example.com (fsmithred) — Tue, 14 Jul 2026 18:56:09 +0000

It's not listed here for daedalus-security like it is for the other daedalus repos.
https://pkgmaster.devuan.org/merged/dis … /InRelease

Origin: Devuan
Label: Devuan-Security
Suite: oldstable-security
Version: 5.0
Codename: daedalus-security
Date: Tue, 14 Jul 2026 18:50:06 UTC
Valid-Until: Tue, 21 Jul 2026 18:15:06 UTC
Architectures: amd64 arm64 armel armhf i386 ppc64el
Components: main contrib non-free          <---- missing "non-free-firmware"

I'm guessing it got left out by mistake. You didn't spell it wrong.

Sudden change in repositories

dummy@example.com (Micronaut) — Tue, 14 Jul 2026 17:30:50 +0000

Just today, as I check every time I boot my system, which is daily, I got a series of errors from APT.

Skipping acquire of configured file 'non-free-firmware/dep11/icons-48x48.tar' as repository 'http://deb.devuan.org/merged daedalus-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)

Now, simply plugging this into Google, I got an "AI" response that I needed to edit my source.list and remove the reference to firmware. Not hard to do, but WHY was there this sudden change? Is there some technical reason? It seems like change for its own sake.