Bug#1143226: src:libheif: fails to migrate to testing for too long
Paul Gevers <[email protected]> Sat, 01 Aug 2026 08:33:36 +0200
| Newsgroups | gmane.linux.debian.devel.multimedia |
|---|---|
| Message-ID | <178556607597.122469.7559402905144118410__36903.382784088$1785566251$gmane$org@debian.org> |
Source: libheif Version: 1.21.2-4 Severity: serious Control: close -1 1.23.1-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:libheif has been trying to migrate for 31 days [2], hence= this bug report. The current output of the migration software for this packa= ge 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 u= nstable. Blocked packages can have impact on other packages, which makes prep= aring for the release more difficult. The situation that caused this bug repo= rt might even be the result of such an issue. We expect maintainers to fix is= sues that hamper the migration of their package in a timely manner. If your p= ackage in this situation due to another package, consider helping out. This bug will trigger auto-removal when appropriate. As with all new bugs, th= ere 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 affec= t 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 bey= ond your control, don't hesitate to contact the Release Team. This bug report has been automatically generated. If you have any comments wi= th 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=3Dlibheif Current text from [2]: Migration status for libheif (1.21.2-4 to 1.23.1-1): BLOCKED: Rejected/violat= es migration policy/introduces a regression Issues preventing migration: =E2=88=99 =E2=88=99 Autopkgtest for cimg/3.5.2+dfsg-2: amd64: Pass, arm64: Pa= ss, armhf: Pass, i386: Pass, loong64: Pass, ppc64el: Pass, riscv64: Test trig= gered (failure will be ignored), s390x: Pass =E2=88=99 =E2=88=99 Autopkgtest for libheif/1.23.1-1: amd64: Pass, arm64: Pas= s, armhf: Pass, i386: Pass, loong64: Pass, ppc64el: Pass, riscv64: Pass, s390= x: Pass =E2=88=99 =E2=88=99 Autopkgtest for rust-libheif-sys/5.2.0-1: amd64: Regressi= on =E2=99=BB (reference =E2=99=BB), arm64: Regression =E2=99=BB (reference = =E2=99=BB), armhf: Regression =E2=99=BB (reference =E2=99=BB), i386: Regressi= on =E2=99=BB (reference =E2=99=BB), loong64: Regression =E2=99=BB (reference = =E2=99=BB), ppc64el: Regression =E2=99=BB (reference =E2=99=BB), riscv64: Reg= ression =E2=99=BB (reference =E2=99=BB), s390x: Regression =E2=99=BB (referen= ce =E2=99=BB) Additional info (not blocking): =E2=88=99 =E2=88=99 Updating libheif will fix bugs in testing: #1140223 =E2=88=99 =E2=88=99 Piuparts tested OK - https://piuparts.debian.org/sid/sour= ce/libh/libheif.html =E2=88=99 =E2=88=99 Reproduced on amd64 - info =E2=88=99 =E2=88=99 Reproduced on arm64 - info =E2=88=99 =E2=88=99 Reproduced on armhf - info =E2=88=99 =E2=88=99 Reproduced on i386 - info =E2=88=99 =E2=88=99 31 days old (needed 5 days)