From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: Julian Andres Klode <julian.klode@canonical.com>
Cc: pkg-grub-devel@alioth-lists.debian.net, linux-xfs@vger.kernel.org
Subject: Processed: Re: Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices
Date: Mon, 25 Dec 2023 08:18:06 +0000 [thread overview]
Message-ID: <handler.s.B1054644.1703492168204060.transcript@bugs.debian.org> (raw)
In-Reply-To: 169839498168.1174073.11485737048739628391.reportbug@nimble.hk.hands.com
Processing control commands:
> clone -1 -2
Bug #1054644 [grub2] xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices
Bug 1054644 cloned as bug 1059424
> reassign -2 xfsprogs
Bug #1059424 [grub2] xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices
Bug reassigned from package 'grub2' to 'xfsprogs'.
Ignoring request to alter found versions of bug #1059424 to the same values previously set
Ignoring request to alter fixed versions of bug #1059424 to the same values previously set
--
1054644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054644
1059424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059424
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
next prev parent reply other threads:[~2023-12-25 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871qdgccs5.fsf@nimble.hk.hands.com>
[not found] ` <20231027154505.GL3195650@frogsfrogsfrogs>
2023-10-27 19:18 ` Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices Philip Hands
[not found] ` <169839498168.1174073.11485737048739628391.reportbug@nimble.hk.hands.com>
[not found] ` <ZTvjFZPn7KH6euyT@technoir>
2023-10-27 16:25 ` Darrick J. Wong
2023-10-27 22:27 ` Philip Hands
2023-10-27 22:38 ` Bastian Germann
2023-10-27 22:42 ` Processed: " Debian Bug Tracking System
2023-12-25 8:18 ` Debian Bug Tracking System [this message]
2023-12-25 8:54 ` 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.B1054644.1703492168204060.transcript@bugs.debian.org \
--to=owner@bugs.debian.org \
--cc=julian.klode@canonical.com \
--cc=linux-xfs@vger.kernel.org \
--cc=pkg-grub-devel@alioth-lists.debian.net \
/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.