Your message dated Mon, 27 Sep 2021 12:58:57 -0400
with message-id <87sfxq0xbi....@transcendence.maguirefamily.org>
and subject line Re: src:fricas: fails to migrate to testing for too long:
maintainer built arch:all binaries
has caused the Debian Bug report #993478,
regarding src:fricas: fails to migrate to testing for too long: maintainer
built arch:all binaries
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
993478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fricas
Version: 1.3.6-6
Severity: serious
Control: close -1 1.3.7-1
Tags: sid bookworm pending
User: release.debian....@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As announced [1] last year, the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:fricas has
been trying to migrate for 62 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 bookworm, so
it doesn't affect (old-)stable.
Your package is only really blocked because the arch:all binary
package(s) aren't built on a buildd. Unfortunately the Debian
infrastructure doesn't allow arch:all packages to be properly binNMU'ed.
Hence, I will shortly do a no-changes source-only upload to DELAYED/15,
closing this bug. Please let me know if I should delay or cancel that
upload.
Paul
[1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html
[2] https://qa.debian.org/excuses.php?package=fricas
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 1.3.6-6
Greetings, and thank you so much for your report!
I have uploaded several identical versions of the package. The build
only fails on one host, arm-conova-02, whether building armhf or armel,
and when exercising orthogonal sections of linker code. The failure is
unreproducible on Debian porterboxes. All other autobuilders in either
architecture correctly build the package. The armel and armhf
autobuilders have successfully built 1.3.7-3 at the moment so migration
is imminent. I will follow up with debian admin and request access to
the offending machine to investigate further, but this is a problem with
the machine, not the package, as far as can be discerned at present.
Take care,
--
Camm Maguire c...@maguirefamily.org
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
--- End Message ---
