All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: Chris Hofstaedtler <zeha@debian.org>
Cc: linux-xfs@vger.kernel.org, nathans@debian.org
Subject: Processed: Re: Bug#1073831: xfsdump:FATAL ERROR: could not find a current XFS handle library
Date: Wed, 19 Jun 2024 21:33:08 +0000	[thread overview]
Message-ID: <handler.s.B1073831.17188327152826728.transcript@bugs.debian.org> (raw)
In-Reply-To: 20240619112859.26ekvlxkt4sb5jt2@debian

Processing control commands:

> reassign -1 xfslibs-dev
Bug #1073831 [src:xfsdump] xfsdump:FATAL ERROR: could not find a current XFS handle library
Bug reassigned from package 'src:xfsdump' to 'xfslibs-dev'.
No longer marked as found in versions xfsdump/3.1.11-0.2.
Ignoring request to alter fixed versions of bug #1073831 to the same values previously set
> found -1 xfslibs-dev/6.8.0-2.1
Bug #1073831 [xfslibs-dev] xfsdump:FATAL ERROR: could not find a current XFS handle library
The source xfslibs-dev and version 6.8.0-2.1 do not appear to match any binary packages
Marked as found in versions xfslibs-dev/6.8.0-2.1.
> affects -1 src:xfsdump
Bug #1073831 [xfslibs-dev] xfsdump:FATAL ERROR: could not find a current XFS handle library
Added indication that 1073831 affects src:xfsdump

-- 
1073831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073831
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

       reply	other threads:[~2024-06-19 21:33 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   ` Debian Bug Tracking System [this message]
2024-06-19 22:09   ` Processed: xfsprogs: diff for NMU version 6.8.0-2.2 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.B1073831.17188327152826728.transcript@bugs.debian.org \
    --to=owner@bugs.debian.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nathans@debian.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 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.