Hi Paul, Thanks, I'm in contact with upstream about this.
Hi Stef, суб 19 20:17 <@joostvb> @ #klutshnik: >> stf: opaque_CreateRegistrationResponse Segmentation fault >> @ >> https://buildd.debian.org/status/fetch.php?pkg=libopaque&arch=ppc64el&ver=0.99.7-2&stamp=1726766202&raw=0 >> it's that weird ppc64el arch >> bugs.debian.org/1085466 >> could be that the fix is not ours to make, but some problem elsewhere... Stef: any thoughts? Bye, Joost On Sat, Oct 19, 2024 at 08:01:01PM +0200, Paul Gevers wrote: > Source: libopaque > Version: 0.99.3-1 > Severity: serious > Control: close -1 0.99.7-2 > Tags: sid trixie > User: release.debian....@packages.debian.org > 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:libopaque 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 trixie, 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=libopaque > > Current text from [2]: > Migration status for libopaque (0.99.3-1 to 0.99.7-2): BLOCKED: Maybe > temporary, maybe blocked but Britney is missing information (check below) > Issues preventing migration: > ∙ ∙ missing build on ppc64el > ∙ ∙ arch:ppc64el not built yet, autopkgtest delayed there > Additional info: > ∙ ∙ Piuparts tested OK - > https://piuparts.debian.org/sid/source/libo/libopaque.html > ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ > Reproducible on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 29 days > old (needed 10 days) >
