We're currenlty working on the premise that an upload of pygobject triggered this [1,2]
[1] https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/4772#note_3234705 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120929 On Sat, 13 Dec 2025 at 13:47, Paul Gevers <[email protected]> wrote: > > Source: gst-python1.0 > Version: 1.26.7-1 > Severity: serious > Control: close -1 1.26.8-1 > Tags: sid forky > User: [email protected] > Usertags: out-of-sync > > Dear maintainer(s), > > The Release Team considers packages that are out-of-sync between testing > and unstable for more than 30 days as having a Release Critical bug in > testing [1]. Your package src:gst-python1.0 has been trying to migrate > for 31 days [2], hence this bug report. The current output of the > migration software for this package is copied to the bottom of this > report and should list the reason why the package is blocked. > > If a package is out of sync between unstable and testing for a longer > period, this usually means that bugs in the package in testing cannot be > fixed via unstable. Additionally, blocked packages can have impact on > other packages, which makes preparing for the release more difficult. > Finally, it often exposes issues with the package and/or its > (reverse-)dependencies. We expect maintainers to fix issues that hamper > the migration of their package in a timely manner. > > This bug will trigger auto-removal when appropriate. As with all new > bugs, there will be at least 30 days before the package is auto-removed. > > This bug submission immediately closes the bug with the version in > unstable, so if that version or a later version migrates, this bug will > no longer affect testing. This bug is also tagged to only affect sid and > forky, so it doesn't affect (old-)stable. > > If you believe your package is unable to migrate to testing due to > issues beyond your control, don't hesitate to contact the Release Team. > > This bug report has been automatically generated and has only been sent > manually. If you have any comments with regards to the content or the > process, please reach out to me. > > Paul > > [1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html > [2] https://qa.debian.org/excuses.php?package=gst-python1.0 > > Current text from [2]: > Migration status for gst-python1.0 (1.26.7-1 to 1.26.8-1): BLOCKED: > Maybe temporary, maybe blocked but Britney is missing information (check > below) > Issues preventing migration: > ∙ ∙ Missing build on amd64 > ∙ ∙ Missing build on arm64 > ∙ ∙ Missing build on armhf > ∙ ∙ Missing build on i386 > ∙ ∙ Missing build on ppc64el > ∙ ∙ Missing build on riscv64 > ∙ ∙ Missing build on s390x > ∙ ∙ Autopkgtest deferred on amd64: missing arch:amd64 build > ∙ ∙ Autopkgtest deferred on arm64: missing arch:arm64 build > ∙ ∙ Autopkgtest deferred on i386: missing arch:i386 build > ∙ ∙ Autopkgtest deferred on ppc64el: missing arch:ppc64el build > ∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build > ∙ ∙ Autopkgtest deferred on s390x: missing arch:s390x build > ∙ ∙ Lintian check waiting for test results on riscv64, armhf, amd64, > arm64, i386, ppc64el, s390x - info > Additional info (not blocking): > ∙ ∙ Piuparts tested OK - > https://piuparts.debian.org/sid/source/g/gst-python1.0.html > ∙ ∙ 31 days old (needed 5 days) -- g. Marc GPG: 827C FD74 BA46 8152 A041 F3A0 7A6A 4F17 5995 A65B
