You are not logged in.
https://archive.debian.org/debian-secur … -security/
bullseye-security is in archive now... now we need chimaera-security here https://archive.devuan.org/merged/dists/
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
Recalling the experience with moving Chimaera backports to the archive, I think we need to wait for a decision from the Debian side and then spend some time persuading the Devuan team to fix their "unique" repositories ![]()
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.
I need Tomcat 9 and Java 8. Tomcat 9 is available in the standard repositories, while I get Java 8 from Temurin. I also have ELTS from Freexian.
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.
https://lists.debian.org/debian-mirrors … m%2F#00001 - last two posts
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/
There is no "security" in debian archive for Bullseye. Security becomes a part of updates.
https://gist.github.com/ishad0w/7665cde … 13802e61e4
https://lists.debian.org/debian-user/20 … 00415.html
> Did this mean that everything that was in
> bullseye-security was rolled into the main
> archiveYes, pretty much
That might be the reason.
Debian repo is in archive now. Devuan merged repo points not to archive but to main updates pool - http://deb.debian.org/debian-security/pool/updates/main
BUG is on the devuan side. It’s really sad that the developers can’t even properly move a release to the archive.
I’m not demanding anything, and I realize that no one owes me anything, but I’ve been pointing out the problem and its causes for some time now. It would be great if someone responded.
https://dev1galaxy.org/viewtopic.php?id=7317 - Last time, it took some time to acknowledge the problem.
No changes. I think, it is not a "mirrors not being in sync" problem. All debian packages are in archive repository but devuan source is trying to merge them from deb.debian.org.
I can make apt-get update but not apt-get upgrade
http://deb.debian.org/debian-security/pool/updates/main/a/apr-util/libaprutil1_1.6.1-5+deb11u2_amd64.deb 404 Not Found [IP: 146.75.118.132 80]
http://deb.debian.org/debian-security/pool/updates/main/libd/libdbi-perl/libdbi-perl_1.643-3+deb11u2_amd64.deb 404 Not Found [IP: 146.75.118.132 80]
http://deb.debian.org/debian-security/pool/updates/main/l/linux-signed-amd64/linux-image-amd64_5.10.262-1_amd64.deb 404 Not Found [IP: 146.75.118.132 80]
http://deb.debian.org/debian-security/pool/updates/main/p/python-httplib2/python3-httplib2_0.18.1-3+deb11u1_all.deb 404 Not Found [IP: 146.75.118.132 80]
http://deb.debian.org/debian-security/pool/updates/main/u/unzip/unzip_6.0-26+deb11u2_amd64.deb 404 Not Found [IP: 146.75.118.132 80]All this files are in Debian 11 (Bullseye) archive.
I use virtualization and understand how to gain experience independently. I asked the question because I wanted to learn from the community's experience.
kernel 5.10 is also very interesting, does anybody tried kernel from Freexian?
I have a service that depends on Tomсat 9 and Java 8. I'm currently using Devuan 4 and Java from Temurin.
Debian 11 support ends in September, and Devuan 4 support will end soon as well.
My service is fairly stable and won't be updated. It's not exactly a legacy service, more like a "mature enterprise solution"
.
I'd like to connect the Freexian repository, but I'm worried about potential issues.
Are there any good practices for using Freexian? Perhaps a whitelist of packages (tzdata, dns-root-data, and other system packages), or a blacklist?
Basically, I'd like to receive updates for Java (which will come from Temurin), Apache 2 (hopefully via ELTS), and the system/OS in general. Apache Tomchat 9 obviously won't update automatically, and even if it does, it won't have the scripts for Sysvinit.
So, has anyone tried Devian + ELTS Freexian and what happened?
Does this mean opening the first vhost on port 443 is normal behavior when opening https://deb.devuan.org?
In my opinion, the mirror is configured incorrectly.
I expect to see deb.devuan.org, a redirect to http://deb.devuan.org, or nothing when opening https://deb.devuan.org, but I see the first website I come across on the same hosting.
In my opinion, this isn't normal.
https://pkginfo.devuan.org/cgi-bin/poli … 9&x=submit
May be it is siolved.... i need to check
Thank you. I tried to make a report and send a copy to maintainer.
Unfortunately, my major packages, for example tomcat and nodejs are broken, outdated and/or misconfigured in Devuan.
9.0.107 - https://packages.debian.org/bullseye/tomcat9 (bullseye - 9.0.43-2~deb11u10, bullseye security - 9.0.107-0+deb11u1)
9.0.43 - https://pkginfo.devuan.org/cgi-bin/pack … 3+devuan10
why? Is it in chimaera-security?
There is no devuan archive mirrors and current morror (hosting provider?) blocks some networks (not all) in my country. I have no access to mirror from Universiry network and have no problems in home network.
ralph.ronnquist
(I assume "freer" is a misspelling)
No, I copied one more additional symbol from next line
Does the "same thing" happen every time?
Unfortunatelly yes.
Now I am using this mirror http://mirror.mephi.ru/devuan/devuan/di … backports/ - it is actually ru.devuan.org and have no problems.
rolfie
not
deb http://deb.devuan.org/merged backports
but
deb http://archive.devuan.org/merged chimaera-backports main contrib non-free
user@host:~# cat /etc/apt/sources.list
deb http://deb.devuan.org/merged chimaera main contrib non-free
deb http://deb.devuan.org/merged chimaera-security main contrib non-free
deb http://deb.devuan.org/merged chimaera-updates main contrib non-free
deb http://archive.devuan.org/merged chimaera-backports main contrib non-freerThere are no problems with adoptium java repo:
user@host:~# ls -l /etc/apt/sources.list.d/
-rw-r--r-- 1 root root 64 мая 29 14:57 adoptium.listThere was no any changes here:
user@host:~# ls -l /etc/apt/apt.conf.d/
-rw-r--r-- 1 root root 82 мая 29 14:34 00CDMountPoint
-rw-r--r-- 1 root root 40 мая 29 14:34 00trustcdrom
-rw-r--r-- 1 root root 630 июн 21 2021 01autoremove
-r--r--r-- 1 root root 122 мая 29 14:36 01autoremove-kernels
-rw-r--r-- 1 root root 307 мар 28 2021 20listchanges
-rw-r--r-- 1 root root 182 июн 10 2021 70debconfI tried something like
apt-get -o Acquire::CompressionTypes::Order::=bz2 update
but it does not work
Unfortunately yes.
This message was translated:
Reading package lists… Done
E: Failed to fetch http://archive.devuan.org/merged/dists/chimaera-backports/main/i18n/Translation-en Connection timed out finally [IP: 116.202.138.216 80]
E: Some index files could not be downloaded. They were ignored or older versions were used instead.
root@ojs:~#I can not update apt sources ![]()
bullseye-backports was allways avaliable. There was no removal. bullseye-backports was avaliable in debian archive with no delay.
And now we have no http://archive.devuan.org/merged/dists/ … slation-en in devuan archive... problem is NOT SOLVED. chimaera-backports does not working now.
Sorry, you seem to have a silly idea how Devuan works
Ok... I seem to have a silly idea.... but - https://archive.devuan.org/merged/dists … backports/