Bug#1088573: src:apt-setup: fails to migrate to testing for too long: kcov not available on mips64el and s390x

[Philip Hands]

Cyril Brulebois  writes:

> Cyril Brulebois  (2024-11-28):
>> kcov got binNMU'd, doesn't build on mips64el and s390x, and has no bug
>> reports filed against it… So, sure, apt-setup is RC-buggy by your
>> standards, but maybe filing something on the kcov side would be best
>> (esp. given the bug title, the *actual* problem seems to have been
>> spotted)?
>
> Also looping in Philip who introduce a build-dependency that's not
> available on all architectures.

Thanks for nudging me :-)

> Regardless of what happens (or doesn't) on the kcov side, we need to
> get apt-setup buildable everywhere.

Oh, sorry about that -- it's only really useful on salsa anyway, so I'll just
get rid of the dependancy.

If kcov is unavailable then the coverage job will fail, but that can
only happen if we get gitlab runners on mips64el or s390x, and even then
it wouldn't be even slightly important.

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil


signature.asc
Description: PGP signature

Bug#1088573: src:apt-setup: fails to migrate to testing for too long: kcov not available on mips64el and s390x

[Cyril Brulebois]

Cyril Brulebois  (2024-11-28):
> kcov got binNMU'd, doesn't build on mips64el and s390x, and has no bug
> reports filed against it… So, sure, apt-setup is RC-buggy by your
> standards, but maybe filing something on the kcov side would be best
> (esp. given the bug title, the *actual* problem seems to have been
> spotted)?

Also looping in Philip who introduce a build-dependency that's not
available on all architectures. Regardless of what happens (or doesn't)
on the kcov side, we need to get apt-setup buildable everywhere.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1088573: src:apt-setup: fails to migrate to testing for too long: kcov not available on mips64el and s390x

[Cyril Brulebois]

Paul Gevers  (2024-11-28):
> 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.

kcov got binNMU'd, doesn't build on mips64el and s390x, and has no bug
reports filed against it… So, sure, apt-setup is RC-buggy by your
standards, but maybe filing something on the kcov side would be best
(esp. given the bug title, the *actual* problem seems to have been
spotted)?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1088573: src:apt-setup: fails to migrate to testing for too long: kcov not available on mips64el and s390x

[Paul Gevers]

Source: apt-setup
Version: 1:0.187
Severity: serious
Control: close -1 1:0.189
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:apt-setup has been trying to migrate for 
40 days [2]. Hence, I am filing this bug.


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=apt-setup