[Fwd: Bug#1001916: src:bart-view: fails to migrate to testing for too long: FTBFS on armel and s390x]
Hi all,
this is caused by some compiler bug in GCC 11. Any advice how
to proceed?
- use GCC 11
- exclude affected architectures?
- try to work around by patching? (would be easy
only with access to the affected architectures)
- talk to the release team?
Best,
Martin
-------- Weitergeleitete Nachricht --------
Von: Paul Gevers <elbrus@debian.org>
Antwort an: Paul Gevers <elbrus@debian.org>, 1001916@bugs.debian.org
An: submit@bugs.debian.org
Betreff: Bug#1001916: src:bart-view: fails to migrate to testing for too long: FTBFS on armel and
s390x
Datum: Sat, 18 Dec 2021 22:14:32 +0100
> Source: bart-view
> Version: 0.1.00-4
> Severity: serious
> Control: close -1 0.1.00-5
> Tags: sid bookworm ftbfs
> User: release.debian.org@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 60 days as having a Release Critical bug in
> testing [1]. Your package src:bart-view has been trying to migrate for
> 61 days [2]. Hence, I am filing this bug. Your package fails to build
> from source on armel and s390x where it built successfully in the past.
>
> 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 bookworm, 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/2020/02/msg00005.html
> [2] https://qa.debian.org/excuses.php?package=bart-view
>
> _______________________________________________
> Debian-med-packaging mailing list
> Debian-med-packaging@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
Reply to: