From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: Helmut Grohne <helmut@subdivi.de>
Cc: linux-xfs@vger.kernel.org
Subject: Processed: xfsprogs FTCBFS: [TEST] CRC32 fails to compile
Date: Thu, 18 Nov 2021 05:24:04 +0000 [thread overview]
Message-ID: <handler.s.B.16372129108764.transcript@bugs.debian.org> (raw)
In-Reply-To: YZPJDbOH7tDyK5sb@alf.mars
Processing control commands:
> block -1 by 999743
Bug #999879 [src:xfsprogs] xfsprogs FTCBFS: [TEST] CRC32 fails to compile
999879 was not blocked by any bugs.
999879 was not blocking any bugs.
Added blocking bug(s) of 999879: 999743
--
999879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999879
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
next prev parent reply other threads:[~2021-11-18 5:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b14e2072-5556-41b9-dfab-035b35f3d395@debian.org>
[not found] ` <163700840784.4520.2954754823827344140.reportbug@localhost>
2021-11-19 17:36 ` Bug#999743: marked as done (xfsprogs FTBFS: .gitcensus: No such file or directory) Debian Bug Tracking System
[not found] ` <YZPJDbOH7tDyK5sb@alf.mars>
2021-11-18 5:24 ` Debian Bug Tracking System [this message]
2021-11-19 17:36 ` Bug#999879: marked as done (xfsprogs FTCBFS: [TEST] CRC32 fails to compile) Debian Bug Tracking System
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=handler.s.B.16372129108764.transcript@bugs.debian.org \
--to=owner@bugs.debian.org \
--cc=helmut@subdivi.de \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.