Hi,

src:aegisub in unstable can't migrate to testing because the QA
infrastructure couldn't reproduce some binary packages in
unstable while it could reproduce the version in testing [1, 2].

From the diff it looks like some randomness is compiled in, maybe due to
some auto generated source code? Based on the diff to -4 it could also
be in one of the build dependencies.

Feel free to reach out if you need help debugging the problem but I
assume it will not be easy. Alternatively you can ask the release team
for an exception [3].

Cheers Jochen


[1] https://qa.debian.org/excuses.php?package=aegisub
[2] https://lists.debian.org/debian-devel-announce/2026/05/msg00001.html
[3] https://lists.debian.org/debian-devel/2026/05/msg00383.html

Hi Jochen,

Thanks for the report! I tried to find the reproducibility report.
However it looks like on reproduce.d.n[1] it shows that it passed on
most archs, and for other archs, ppc64el and riscv64 failed when
downloading buildinfo file, for example the log for ppc64el says:

,----
| rebuilderd: unexpected error while rebuilding package: Failed to download build input from "https://buildinfos.debian.net/buildinfo-pool/a/aegisub/aegisub_3.4.2+ds-5_ppc64el.buildinfo": error sending request for url (https://buildinfos.debian.net/buildinfo-pool/a/aegisub/aegisub_3.4.2+ds-5_ppc64el.buildinfo): client error (Connect): tcp connect error: Connection refused (os error 111)
`----

And no log is available for loong64.

So it looks like a toolchain issue, or maybe I'm missing something? If
you have the failure log for reproducibility that would be great for
debugging.

Thanks!

[1] https://reproduce.debian.net/excuses.html?source_name=aegisub

Hi Jochen,

Xiyue Deng <manphiz@gmail.com> writes:

I haven't heard back from you. Maybe because the previous email didn't
put you in CC, that was on me.

As I cannot find any reproducibility error (as mentioned in the last
email), I intend to lower the severity of this bug in a few days to let
aegisub migrate, while keeping the bug open to wait for your comment. I
hope this is fine.

Thanks!

* Xiyue Deng <manphiz@gmail.com> [2026-08-30 01:22]:

You can ignore ppc64el, riscv64 and loong64 as they are not stable and
not used by briteny.

Seems like the new version is reproducible so we can simply close this.
Thanks for your work!

Cheers Jochen