Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1196957

Bug#1070813: src:camelot-py: fails to migrate to testing for too long: autopkgtest failure on ppc64el

From Paul Gevers <elbrus@debian.org>
Newsgroups linux.debian.bugs.dist
Subject Bug#1070813: src:camelot-py: fails to migrate to testing for too long: autopkgtest failure on ppc64el
Date 2024-05-09 19:30 +0200
Message-ID <ICfKF-ccRd-5@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Source: camelot-py
Version: 0.11.0-3
Severity: serious
Control: close -1 0.11.0-4
Tags: sid trixie
User: release.debian.org@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1063891

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:camelot-py has been trying to migrate for 
86 days [2]. Hence, I am filing this bug. As you noticed yourself (in 
bug 1063891) the autopkgtest fails on ppc64el. If you can't easily fix 
it, I suggest you make the test failure on ppc64el not blocking. You can 
do that by either using the Architecture field in d/t/control 
("!ppc64el" works), but I don't recommend that because changes to the 
results would go unnoticed and it would be harder to get a log. 
Alternatively you can annotate the test with the flaky restriction, but 
that would cause failure on !ppc64el to go unnoticed. So, I would 
recommend using the skippable restriction and "exit 77" when the test 
fails on ppc64el (but that's a bit more work to embed in the test).

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.

I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug 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.

Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=camelot-py

Back to linux.debian.bugs.dist | Previous | Next | Find similar | Unroll thread


Thread

Bug#1070813: src:camelot-py: fails to migrate to testing for too long: autopkgtest failure on ppc64el Paul Gevers <elbrus@debian.org> - 2024-05-09 19:30 +0200

csiph-web