Done. 8^)

Best,

A.

Thanks for the heads up.

Best,

A.

bullseye-security is in archive now... now we need chimaera-security here https://archive.devuan.org/merged/dists/

Looking for the [*.deb] files I am needing I found two possible sources:

https://miroir.blueline.mg/debian-security/dists/
https://debian.sipwise.com/debian-security/dists/

Are these legitimate Debian mirrors?

Best,

A.

I seem to have the same problem with the headless [Chimaera] VM I run exclusively for [pihole]+[unbound], which I won't upgrade to [Daedalus]. Also for reasons, main one being that it works perfectly well.

An example, to be clear in case it is something else:
[unzip_6.0-26+deb11u2_amd64.deb] is not in http://deb.debian.org/debian-security/p … in/u/unzip.

Q: If I download the 13 packages, install them manually and (if*) this issue gets fixed, will the eventual upgrades (if any) be installed as usual? ie: no downloading the packages manually.

*I checked the link IdeaFix posted but those last two are it, from 07/09 and 08/09. ie: no activity from maintainers/packagers since then.

Best,

A.

debmirror --nosource \
          --host=snapshot.debian.org \
          --method=https \
          --root=archive/debian-security/20260903T220410Z \
          --dist=bullseye-security \
          --section=main,contrib,non-free \
          --arch=amd64 \
          --ignore-release-gpg \
          --progress \
          /opt/security/

I made a local mirror for x64 in /opt/security, next step I need to merge devuan packages and make a local repository

Right now, the Devuan package list is simply unreliable. Yes, one could blame Debian, but that doesn't solve the problem. "We don't guarantee anything to our users" and "We don't care about our users" are not the same thing.

Unfortunately, simply adding a snapshot isn't the solution. Before the move to the archive, PHP packages and several others were updated; these are rebuilt on the Devuan side. Just as with Tomcat, once the organizational issues are resolved, I might have to persuade the maintainer (via a bug report) to rebuild the package.

I have working deb11 server:

root@elar:~# apt update
Сущ:1 http://archive.debian.org/debian bullseye InRelease
Сущ:2 http://archive.debian.org/debian bullseye-updates InRelease
Сущ:3 http://archive.debian.org/debian bullseye-backports InRelease
Сущ:4 https://snapshot.debian.org/archive/debian-security/20260903T220410Z bullseye-security InRelease
Пол:5 https://packages.adoptium.net/artifactory/deb bullseye InRelease [7507 B]
Сущ:6 https://security.freexian.com/extended-lts bullseye InRelease
Сущ:7 https://repo.zabbix.com/zabbix-tools/debian-ubuntu bullseye InRelease
Сущ:8 https://repo.zabbix.com/zabbix/7.0/debian bullseye InRelease
Получено 7507 B за 2с (3918 B/s)
Чтение списков пакетов… Готово
Построение дерева зависимостей… Готово
Чтение информации о состоянии… Готово
Все пакеты имеют последние версии.
root@elar:~# uname -a
Linux elar 5.10.0-46-amd64 #1 SMP Debian 5.10.262-1 (2026-07-31) x86_64 GNU/Linux
root@elar:~# cat /etc/debian_version
11.11
root@elar:~#

However, neither the developers nor the user community have a solution for Devuan yet.

But you are right: one can manually build a repository from snapshots and rebuild specific packages. After all, that is precisely why we value the distribution.

E.g. https://snapshot.debian.org/archive/deb … u1_all.deb is one of them.

EDIT EDIT: I couldn't convince apt-get to use a sources.list line, so I have to stay with advicing you to download the deb file(s).

Upgrading to newer distribution versions would deprive me of the distribution's benefits if I had to install Tomcat 9 from a tarball.

I understand that Chimaera is currently EOL, but that doesn't mean it should be moved to the archive with errors.

And, if that snapshot has those debs, it'd be easy for you to add that to your sources list. Would be a way to fix the situation for yourself; your personal merge. if you like.

https://gist.github.com/ishad0w/7665cde … 13802e61e4

I understand that it is very difficult for devuan team to merge this repo https://snapshot.debian.org/archive/deb … 3T220410Z/

The transfer into archive does seem to be a gradual thing rather than instantaneous, so if you hold your breath for a week or so, it might have sorted itself.

https://gist.github.com/ishad0w/7665cde … 13802e61e4
https://lists.debian.org/debian-user/20 … 00415.html

That might be the reason.

It does look like Devuan's amprolla will need some logic to handle that. Perhaps you would want to assist with that... (how to merge debian packages that get dropped from deb.debian.org without turning up in archive.debian.org). Or you could perhaps get in touch with the debian developers on that issue. Afaict it would affect Debian 11 Bullseye in a similar way.

You can start here:
https://bugs.devuan.org/db/ix/full.html