MichaIng

Thanks for your report. That is true, if the package has been removed, but not purged, and config files were left in place. One solution would be `dpkg-query -s "$i"...

Since there is no `https://download.webmin.com/download/repository/dists/sarge/contrib/binary-riscv64/Packages` (and it is not listed in `https://download.webmin.com/download/repository/dists/sarge/Release`), a system with `dpkg --print-architecture` == `riscv64` is not able to use the repo with APT. The packages...

Yeah it is a little contradicting. The header show `Architecture: all i386 amd64`, but does not list/have a `binary-all/Packages`. APT seems to internally fall back to `binary-/Packages`, which works if...

Ah thanks for the hint, fount it: https://download.webmin.com/download/newkey/repository/dists/stable/Release Compared to the old one, it is a little more consistent, as it contains all individual architectures in the header. But the...

Jep, something like this should do: ```sh cp -a contrib/binary-{arm64,all} ``` and adding the hashes to the `Release` file (+ regenerating the `Release.gpg`), which is also just copy&pasting the lines...

@jcameron I see you added this to the old repository, not the new one? Tested with: ```console root@visionfive2:~# cat /etc/apt/sources.list.d/webmin.list deb https://download.webmin.com/download/repository/ sarge contrib ``` Interestingly, `apt update` shows the...

As I could not find any info about APT repositories in general in the [Debian policies](https://www.debian.org/doc/debian-policy/), I just asked in the developer mailing list: https://lists.debian.org/debian-devel/2023/12/msg00023.html

Cycling back to this: TL;DR: It is indeed intended that a repo should declare itself compatible with each architecture explicitly, providing a `binary-/Packages` for each of them, even if only...

@dependabot rebase

@dependabot recreate