Your message dated Sun, 26 Oct 2025 13:51:37 +0000
with message-id <[email protected]>
and subject line remaining bugs fixed, thus closing
has caused the Debian Bug report #1116598,
regarding debian-repro-status misses some GOOD results
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1116598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116598
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debian-repro-status
Version: 0.3.1-2
Severity: grave
X-Debbugs-Cc: [email protected]
Dear Maintainer,
debian-repro-status doesn't work on Debian Trixie but gives out an 404
error. I first reported this to upstream after consulting with the
#debian-reproducible matrix chat. jochensp recommended filing a bug here
too so the bug can be fixed in Trixie too.
I'm not sure about the severity since right now debian-repro-status
doesn't work at all (quite serious or grave in my book) but of course
won't cause dataloss or have any security implicatins.
So feel free to change the severity.
I will now copy-paste my upstream bug report from
https://github.com/kpcyrd/debian-repro-status/issues/19
How to reproduce
Install debian-repro-status on a current Debian Trixie System (I used a
cloudinit image from cdimage.debian.org on a ProxmoxVE 9 qemu10 VM ) with
apt install debian-repro-status
Verify the version:
apt-cache policy debian-repro-status`de
debian-repro-status:
Installed: 0.3.1-2
Candidate: 0.3.1-2
Version table:
*** 0.3.1-2 500
500 mirror+file:/etc/apt/mirrors/debian.list trixie/main amd64
Packages
100 /var/lib/dpkg/status
Run it:
debian-repro-status
Error: Failed to complete http request: "
https://reproduce.debian.net/amd64/api/v0/pkgs/list";
Caused by:
HTTP status client error (404 Not Found) for url (
https://reproduce.debian.net/amd64/api/v0/pkgs/list)
Alternatively build and run it from the github repo:
git clone https://github.com/kpcyrd/debian-repro-status
cargo build
cargo run
Finished dev profile [unoptimized + debuginfo] target(s) in 0.49s
Running target/debug/debian-repro-status
Error: Failed to complete http request: "
https://reproduce.debian.net/amd64/api/v0/pkgs/list";
Caused by:
HTTP status client error (404 Not Found) for url (
https://reproduce.debian.net/amd64/api/v0/pkgs/list)
- ```
git describe --tags
v0.3.1
Possible causes
Since the error is an 404 on the api url my first guess was that the api
changed ad some point in rebuilderd, but a grep -R api/
--exclude-dir=target rebuilderd on my local copy of the rebuilderd
repository didn't confirmed this. So my guess is that reproduce.debian.net
changed something in their setup which is not reflected in
debian-repro-status yet. On the other hand rdn mentions a api/v1 and even
has some examples for these "api/v1" so maybe I missed something in the
rebuilderd source code.
-- System Information:
Debian Release: 13.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.48+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages debian-repro-status depends on:
ii ca-certificates 20250419
ii libc6 2.41-12
ii libgcc-s1 14.2.0-19
ii libssl3t64 3.5.1-1
debian-repro-status recommends no packages.
debian-repro-status suggests no packages.
-- no debconf information
Regards, Johannes.
--- End Message ---
--- Begin Message ---
hi,
jarl fixed the remaining issues in https://github.com/kpcyrd/rebuilderd/pull/184
which is whats running on reproduce.debian.net and now:
<h01ger> \o/
<h01ger> INFO debian-repro-status > 137/3019 packages could not be reproduced.
<h01ger> INFO debian-repro-status > Your system has 95.46% been reproduced.
<h01ger> compared to 309/3012 and 89.74% yesterday.
<h01ger> yay!
<h01ger> jarl: thank you!
<h01ger> which also means that debian-repro-status now for the first time can
report accurate results for unstable and forky too! \o/
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
Bananas are berries.
signature.asc
Description: PGP signature
--- End Message ---
