From: Philip Hands <phil@hands.com>
To: "Darrick J. Wong" <djwong@kernel.org>, 1054644@bugs.debian.org
Subject: Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices
Date: Fri, 27 Oct 2023 21:18:47 +0200 [thread overview]
Message-ID: <87y1fnc1rc.fsf@nimble.hk.hands.com> (raw)
In-Reply-To: <20231027154505.GL3195650@frogsfrogsfrogs>
"Darrick J. Wong" <djwong@kernel.org> writes:
...
> Curiously, this log says:
>
> Oct 24 05:35:32 in-target: Setting up xfsprogs (6.4.0-1) ...^M
>
> So ... is it running 6.4 and not 6.5?
The daily test versions of Debian-Installer draw components from
"unstable", which is where the 6.5 version is at present, which then
creates the file system with problematic flags.
However, the test images normally install "testing" onto the target, to
avoid pointless breakage caused by the potential for "unstable" to be,
well ... unstable, hence the 6.4 version that gets put in-target.
Having 6.4 in the target system doesn't help in this case, because the
damage has already been done while creating the file system, by the 6.5
version of the udeb.
One can confirm that this is the case by looking for xfsprogs in here:
https://openqa.debian.net/tests/198911/logfile?filename=complete_install-DI-installed-pkgs.txt
which lists the installed components (udebs) of the installer that's running:
xfsprogs-udeb 6.5.0-1
Cheers, Phil.
--
Philip Hands -- https://hands.com/~phil
next parent reply other threads:[~2023-10-27 19:23 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 ` Philip Hands [this message]
[not found] ` <169839498168.1174073.11485737048739628391.reportbug@nimble.hk.hands.com>
[not found] ` <ZTvjFZPn7KH6euyT@technoir>
2023-10-27 16:25 ` Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices 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
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=87y1fnc1rc.fsf@nimble.hk.hands.com \
--to=phil@hands.com \
--cc=1054644@bugs.debian.org \
--cc=djwong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox