Bug#1031696: Also affects bookworm

Cyril Brulebois <[email protected]> Sat, 11 Mar 2023 14:06:50 +0100

Newsgroups	gmane.linux.debian.devel.cd
Organization	Debian
Message-ID	<20230311130650.3foytrtvfrbfur7l__36225.7787071698$1678540178$gmane$org@mraw.org>

Hi,

Pete Batard <[email protected]> (2023-03-11):
> The regression, in my opinion, is that the standard release of bullseye
> made sure that all the packages that may be required for a successful
> installation would be available for users who did not create their media
> using 'dd', whereas bookworm doesn't.

The standard release of Bullseye doesn't include all the packages that may
be required for a successful installation!

That's exactly why we've had this vote on non-free-firmware and all those
changes!

> Whereas one could use file system transposition with bullseyes to create a
> working installation media for a UEFI system, the same is not true for
> bookworm, as we now have .deb packages that are symbolically linked and that
> will not be found unless the user takes care of manually duplicating those,
> or copies the ISO through a utility that does.

As far as I can tell, there are no functional changes here.

> Again, I will point out that the goal is for users of any OS to be able to
> bypass the need to use any external utility (and I'll remind everyone that
> Windows does not come with a native 'dd' equivalent for instance) and just
> use the native tools that come with the OS to create a Debian installation
> UEFI bootable media .

This appears to be *your* goal.

> With bullseye, and to continue with the example of Windows, this was
> possible by simply formatting a USB drive to FAT32 (which can be easily
> achieved by right clicking on the drive or through the native disk utility)
> then mounting the ISO in File Explorer (again right click, for any version
> of Windows starting with Windows 8 included) and copying the files to the
> USB drive.

You've been repeating that a lot. But those Bullseye images are nowhere
more usable!

> With bookworm, doing the above no longer guarantees that the media will
> result in an installable Debian, because if the user happens to require a
> firmware, the relevant .deb package will be missing from /firmware due to
> the use of symbolic links.

That. is. not. a. change. from. Bullseye.

Example: My laptop requires iwlwifi firmware. Please explain to me how
it gets installed during the Bullseye installation process.

> I hope that clarifies it.

Not at all.


Cheers,
-- 
Cyril Brulebois ([email protected])            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

signature.asc (application/pgp-signature, 833 B)