From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: Chris Hofstaedtler <zeha@debian.org>
Cc: linux-xfs@vger.kernel.org
Subject: Processed: xfsprogs: diff for NMU version 6.8.0-2.2
Date: Wed, 19 Jun 2024 22:09:04 +0000 [thread overview]
Message-ID: <handler.s.B1073831.17188347522843853.transcript@bugs.debian.org> (raw)
In-Reply-To: 20240619112859.26ekvlxkt4sb5jt2@debian
Processing control commands:
> tags 1073831 + patch
Bug #1073831 [xfslibs-dev] xfsdump:FATAL ERROR: could not find a current XFS handle library
Added tag(s) patch.
> tags 1073831 + pending
Bug #1073831 [xfslibs-dev] xfsdump:FATAL ERROR: could not find a current XFS handle library
Added tag(s) pending.
> affects -1 + src:partclone
Bug #1073831 [xfslibs-dev] xfsdump:FATAL ERROR: could not find a current XFS handle library
Added indication that 1073831 affects src:partclone
--
1073831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073831
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
prev parent reply other threads:[~2024-06-19 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZnNOJtgGQ2M4DciV@per>
[not found] ` <20240619112859.26ekvlxkt4sb5jt2@debian>
2024-06-19 21:33 ` Processed: Re: Bug#1073831: xfsdump:FATAL ERROR: could not find a current XFS handle library Debian Bug Tracking System
2024-06-19 22:09 ` Debian Bug Tracking System [this message]
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.B1073831.17188347522843853.transcript@bugs.debian.org \
--to=owner@bugs.debian.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zeha@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox