Re: src:dnspython: fails to migrate to testing for too long: autopkgtest regression on s390x

Paul Gevers <[email protected]> Wed, 5 Feb 2025 07:50:55 +0100
Newsgroups	gmane.linux.debian.ports.s390
Message-ID	<[email protected]>
user: [email protected]
usertags: s390x
thanks

Hi,

Maybe the s390x porters can help? I have the suspicion that there is 
endianess involved in the autopkgtest failure of dnspython. dnspython is 
key package.

Original message for context in full below.

Paul

On Thu, 2 Jan 2025 21:37:33 +0100 Paul Gevers <[email protected]> wrote:
> Source: dnspython
> Version: 2.6.1-1
> Severity: serious
> Control: close -1 2.7.0-1
> Tags: sid trixie
> 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:dnspython 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=dnspython
> 
> Current text from [2]:
> Migration status for dnspython (2.6.1-1 to 2.7.0-1): BLOCKED: 
> Rejected/violates migration policy/introduces a regression
> Issues preventing migration:
> ∙ ∙ autopkgtest for dnspython/2.7.0-1: amd64: Pass, arm64: Pass, armel: 
> Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a 
> regression), s390x: Regression or new test ♻ (reference ♻)
> Additional info:
> ∙ ∙ Piuparts tested OK - 
> https://piuparts.debian.org/sid/source/d/dnspython.html
> ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ 
> ∙ Reproducible on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 
> 32 days old (needed 5 days)
>
OpenPGP_signature.asc (application/pgp-signature, 495 B)