Testing migration seems to have already been re-enabled after the trixie
release (thanks!) but packages in unstable don't seem to be candidates
for migration to testing, however trivial the package might be. For
example sound-theme-freedesktop:

    Migration status for sound-theme-freedesktop (0.8-4 to 0.8-6): Waiting for test results or another package, or too young (no action required now - check later)
    Issues preventing migration:
        No reproducible data available at all for amd64
        No reproducible data available at all for arm64
    Additional info:
        Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sound-theme-freedesktop.html
        11 days old (needed 5 days)

But
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sound-theme-freedesktop.html
reports that it is reproducible. This seems most likely to be a problem
with importing reproducibility data into the testing machinery?

    smcv

Hi Simon,

Thanks for the report.


This is because r-b.o isn't testing forky yet and
https://salsa.debian.org/release-team/britney2/-/blob/master/britney2/policies/policy.py?ref_type=heads#L2608.
I'm going to test commenting that line out and if I don't spot issues I
might use that as a containment.

On the other hand, my question on #debian-reproducible was replied with
"should happen today or tomorrow".

Paul

Hi,


Seems like this worked, things should move on the next real britney run.

Paul