The buidls fail because of: ``` gst-plugins-bad1.0-contrib build-depends on missing: - libfdk-aac-dev:amd64 ```
While these should be available. A re-trigger or re-upload should do the trick (e.g. with the next point release) https://packages.debian.org/search?keywords=libfdk-aac-dev On Thu, 21 Aug 2025 at 15:59, Paul Gevers <[email protected]> wrote: > > Source: gst-plugins-bad1.0-contrib > Version: 1.20.0-1.1 > Severity: serious > Control: close -1 1.26.5-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-plugins-bad1.0-contrib has been trying > to migrate for 85 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-plugins-bad1.0-contrib > > Current text from [2]: > Migration status for gst-plugins-bad1.0-contrib (1.20.0-1.1 to > 1.26.5-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 armel > ∙ ∙ missing build on armhf > ∙ ∙ missing build on i386 > ∙ ∙ missing build on ppc64el > ∙ ∙ missing build on s390x > ∙ ∙ arch:amd64 not built yet, autopkgtest delayed there > ∙ ∙ arch:arm64 not built yet, autopkgtest delayed there > ∙ ∙ arch:armel not built yet, autopkgtest delayed there > ∙ ∙ arch:armhf not built yet, autopkgtest delayed there > ∙ ∙ arch:i386 not built yet, autopkgtest delayed there > ∙ ∙ arch:ppc64el not built yet, autopkgtest delayed there > ∙ ∙ arch:s390x not built yet, autopkgtest delayed there > Additional info: > ∙ ∙ Cannot be tested by piuparts (not a blocker) - (no link yet) > ∙ ∙ 9 days old (needed 5 days) > -- g. Marc GPG: 827C FD74 BA46 8152 A041 F3A0 7A6A 4F17 5995 A65B
