Bug#1057562: closed by Debian FTP Masters <ftpmaster at ftp-master.debian.org> (reply to Jeremy Bícha <jbicha at ubuntu.com>) (Bug#1057562: fixed in gcr4 4.2.0-2)

[Jeremy Bícha]

On Tue, Mar 12, 2024 at 3:32 PM Santiago Vila <sanvila at debian.org> wrote:
> This is a violation of a *must* directive in Policy, because
> Debian policy says this:
>
> If build-time dependencies are specified, it must be possible to build the package and produce working binaries on a system with only essential and build-essential packages installed and also those required to satisfy the build-time relationships (including any implied relationships).

I disagree with your interpretation of Debian Policy. It is clearly
possible to build gcr and gcr4 on a system with only essential and
build-essential installed. See
https://buildd.debian.org/status/package.php?p=gcr4

Debian Policy does not say that it is a severity: serious bug because
you are unable to compile gcr4 on your particular AWS instance. I
understand that this bug appears serious to you. I also agree that
there is a real bug in gcr. Perhaps the bug is a race condition.
Fixing the issue that causes gcr build tests to fail 100% in your test
case may also fix the flakiness issue seen on the official buildds.

One problem with your insistence on declaring this bug serious was
that it put epiphany-browser on the auto-removal list. It was not that
critical. (That issue is obsolete since key packages are now using
gcr4.)

Unfortunately, the Debian GNOME team is too small for the amount of
work to be done and the number of open bugs. This bug is not so severe
that it requires my immediate attention compared to everything else
nor is it easy enough that I can fix it in a few minutes. Instead of
complaining about the severity the maintainer has assigned to the bug,
I guess you could try fixing it?

Thank you,
Jeremy Bícha