On Tue, Apr 23, 2024 at 11:00 AM Colin Watson wrote:
> I've been attempting to debug this on an AWS instance provided by
> Santiago. So far I'm afraid I can only report some partial progress,
> but I might as well write down what I've got so far.
Colin, thanks for looking into this issue. It
On Tue, Mar 12, 2024 at 03:48:24PM -0400, Jeremy Bícha wrote:
> 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
On Tue, Mar 12, 2024 at 3:32 PM Santiago Vila 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
El 3/3/24 a las 17:38, Jeremy Bícha escribió:
Control: severity -1 important
Control: affects -1 src:gcr
On Fri, Mar 1, 2024 at 6:36 AM Santiago Vila wrote:
Ignore build test failures on s390x (Closes: #1057562)
This is wrong for several reasons.
- The bug report did not say anything about
Control: severity -1 important
Control: affects -1 src:gcr
On Fri, Mar 1, 2024 at 6:36 AM Santiago Vila wrote:
> > Ignore build test failures on s390x (Closes: #1057562)
>
> This is wrong for several reasons.
>
> - The bug report did not say anything about s390x.
s390x is the only architecture
reopen 1057562
found 1057562 4.2.0-3
thanks
Ignore build test failures on s390x (Closes: #1057562)
This is wrong for several reasons.
- The bug report did not say anything about s390x.
- This is still happening on version 4.2.0-3. I can still reproduce
it 100% of the time here, and I'm
6 matches
Mail list logo
