Bug#1059222: src:pv: fails to migrate to testing for too long: FTBFS on armhf

[Andrew Wood]

> This is a quick word to let you know that I've disabled valgrind tests
> on armhf in the Debian package. They were failing since the 1.8.5 upload
> [...]

Thank you, I agree with this approach.  The evidence I have seen so far
suggests that the failures are due to issues with the way valgrind itself
behaves on that architecture.

-- 
Andrew Wood

Bug#1059222: src:pv: fails to migrate to testing for too long: FTBFS on armhf

[Antoine Beaupré]

Hi Andrew!

This is a quick word to let you know that I've disabled valgrind tests
on armhf in the Debian package. They were failing since the 1.8.5 upload
(but possibly not in 1.8.0!), you can see a log here:

https://buildd.debian.org/status/fetch.php?pkg=pv=armhf=1.8.5-1=1700453788=0

Unfortunately, the failed build doesn't show the valgrind output, so
it's unclear exactly what's going on...

I might be able to get an armhf box to test this if you can't, let me
know how we should move ahead on this. For now, it seems better to
unblock the package so it trickles down to testing, considering how
slightly more flacky those tests are...

let me know!

a.

Bug#1059222: src:pv: fails to migrate to testing for too long: FTBFS on armhf

[Paul Gevers]

Source: pv
Version: 1.8.0-3
Severity: serious
Control: close -1 1.8.5-1
Tags: sid trixie ftbfs
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:pv has been trying to migrate for 31 days 
[2]. Hence, I am filing this bug. The version in unstable failed to 
build on armhf.


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/msg1.html
[2] https://qa.debian.org/excuses.php?package=pv



OpenPGP_signature.asc
Description: OpenPGP digital signature