Bug#1005886: debian-cd: bookworm net-install CD hangs on "Detecting Network Hardware"

Followup-For: Bug #1005886 X-Debbugs-Cc: powe...@gmail.com Control: reassign -1 cdimage.debian.org Control: retitle -1 cdimage.debian.org: bookworm net-install CD hangs on "Detecting Network Hardware" Sorry (both to you Tony, and also the Debian CD team) for confusion and wasting time - I

Processed: reassign 1032238 to src:linux, reassign 1033209 to apt, reassign 1033208 to apt, tagging 1032551 ...

Processing commands for cont...@bugs.debian.org: > reassign 1032238 src:linux Bug #1032238 {Done: Salvatore Bonaccorso } [linux-image-6.1.0-5-amd64] linux-image-6.1.0-5-amd64: cryptsetup 2:2.6.1-1 password not recognized Warning: Unknown package 'linux-image-6.1.0-5-amd64' Bug reassigned from

Re: Starting the weekly live images for Bookworm building again

On Sun, Mar 19, 2023 at 03:13:47PM +, Steve McIntyre wrote: > So, after some delay from me and some further delays from various > Debian machines committing suicide [1], I've got bookworm live builds > running again. \o/ this is great news! thanks and kudos to everyone involved! -- cheers,

Re: Starting the weekly live images for Bookworm building again

My last cross-post. Follow-up please on debian-live Hello Steve and lists, On 19/03/2023 16:13, Steve McIntyre wrote: So, after some delay from me and some further delays from various Debian machines committing suicide, I've got bookworm live builds running again. \o/ Thanks for merging the

Installation report - Debian-live standard failed (WAS Re: Starting the weekly live images for Bookworm building again)

On Sun, Mar 19, 2023 at 03:13:47PM +, Steve McIntyre wrote: > Hey again, > > On Tue, Jan 31, 2023 at 03:36:53PM +, Steve McIntyre wrote: > >> > >>As you can see, this affects many teams: > >>* live-setup: a MR to generate all live images for Bookworm [A2] > > So, *builds* work fine but

Testing of LXDE live image

Hi, Steve McIntyre wrote (Sun, 19 Mar 2023 15:13:47 +): > So, *builds* work fine but I've not *yet* tested actually > booting/using one of these images in any way. I've just triggered a > full build of "testing" live images now, please help test if you can > once they're in place at [2] in a

Re: Starting the weekly live images for Bookworm building again

Hi, Steve McIntyre (2023-03-19): > So, after some delay from me and some further delays from various > Debian machines committing suicide [1], I've got bookworm live builds > running again. \o/ Great news. > I don't yet know how close we are to having full non-free-firmware > integration with

Re: Starting the weekly live images for Bookworm building again

Hey again, On Tue, Jan 31, 2023 at 03:36:53PM +, Steve McIntyre wrote: >> >>As you can see, this affects many teams: >>* live-setup: a MR to generate all live images for Bookworm [A2] So, after some delay from me and some further delays from various Debian machines committing suicide [1],

Re: 11.7 planning

Will help out the 29th April :) On 3/18/23, Jonathan Wiltshire wrote: > On Wed, Mar 15, 2023 at 08:33:47PM +, Jonathan Wiltshire wrote: >> We're overdue for 11.7 and need it done with a keyring update included >> before bookworm can be released. The wheels are turning on the keyring so >>

Re: How Do You Create ISOs?

Hi, Ricardo Romanach wrote: > I am currently attempting to create an ISO file from an existing > Debian 11 installation. Google found me https://github.com/pieroproietti/penguins-eggs "penguins-eggs is a console utility, under continuous development, that allows you to remaster your

Upcoming stable point release (11.7)

Hi, The next point release for "bullseye" (11.7) is scheduled for Saturday, April 29th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam

Re: 11.7 planning

On Wed, Mar 15, 2023 at 08:33:47PM +, Jonathan Wiltshire wrote: > We're overdue for 11.7 and need it done with a keyring update included > before bookworm can be released. The wheels are turning on the keyring so > how do dates in April look for everybody? Saturdays are 1st (probably too >

Re: How Do You Create ISOs?

I believe debian-u...@lists.debian.org would be more fruitful for your underlying goal(s). Ricardo Romanach wrote: To whom it may concern in the Debian team, I have a question about creating ISOs. I am currently attempting to create an ISO file from an existing Debian 11 installation. I want

How Do You Create ISOs?

To whom it may concern in the Debian team, I have a question about creating ISOs. I am currently attempting to create an ISO file from an existing Debian 11 installation. I want to do this in order to more easily share this customized copy with a few friends. However, I have not found a tool

Re: 11.7 planning + bookworm planning

On Thu, Mar 16, 2023 at 11:26:00AM +0100, Paul Gevers wrote: > >From where I'm looking, bookworm is looking pretty good. Obviously we'll have >to follow through on the flurry of unblock requests that came in after the >hard freeze, but that should be manageable in a couple of weeks. kibi just

Re: 11.7 planning

On Wed, Mar 15, 2023 at 08:33:47PM +, Jonathan Wiltshire wrote: >Hi, > >We're overdue for 11.7 and need it done with a keyring update included >before bookworm can be released. The wheels are turning on the keyring so >how do dates in April look for everybody? Saturdays are 1st (probably too

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi, Pete Batard wrote: > Debian does not use an efi.img. Oh it does with ISOs for i386 and amd64. There is a data file in the ISO filesystem named /boot/grub/efi.img advertised as MBR partition of type 0xEF and as El Torito boot image for EFI: $ xorriso -indev

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi, Just going to report that I have tested media creation from the 2023-03-13 version of debian-testing-amd64-netinst.iso, using only the Windows native utilities (i.e. formatting a USB drive to FAT32 using Windows Disk manager and mounting the ISO and copying the files using Windows File

Re: 11.7 planning

Hello El 16 de marzo de 2023 13:21:52 CET, Donald Norwood escribió: >29th is workable. > I can the 15th and 22nd of April. For now I cannot say anything about my availability for May (bookworm release). Kind regards >On 3/15/23 18:36, Andy wrote: >> On 15 March 2023 20:33:47 GMT, Jonathan

Re: 11.7 planning

29th is workable. On 3/15/23 18:36, Andy wrote: On 15 March 2023 20:33:47 GMT, Jonathan Wiltshire wrote: Hi, We're overdue for 11.7 and need it done with a keyring update included before bookworm can be released. The wheels are turning on the keyring so how do dates in April look for

Re: 11.7 planning + bookworm planning

Hi, Paul Gevers (2023-03-16): > From where I'm looking, bookworm is looking pretty good. Obviously > we'll have to follow through on the flurry of unblock requests that > came in after the hard freeze, but that should be manageable in a > couple of weeks. kibi just told me on IRC that asking

Re: 11.7 planning + bookworm planning

Can the 6th and 20th in May On Thu, Mar 16, 2023 at 11:26 AM Paul Gevers wrote: > > Dear all, > > On 15-03-2023 21:33, Jonathan Wiltshire wrote: > > We're overdue for 11.7 and need it done with a keyring update included > > before bookworm can be released. The wheels are turning on the keyring

Re: 11.7 planning + bookworm planning

Dear all, On 15-03-2023 21:33, Jonathan Wiltshire wrote: We're overdue for 11.7 and need it done with a keyring update included before bookworm can be released. The wheels are turning on the keyring so how do dates in April look for everybody? Saturdays are 1st (probably too soon), 8th, 15th,

Re: 11.7 planning

If you want my help with testing i can do the later April dates 15th, 22nd and 29th On 3/15/23, Jonathan Wiltshire wrote: > Hi, > > We're overdue for 11.7 and need it done with a keyring update included > before bookworm can be released. The wheels are turning on the keyring so > how do dates in

Re: 11.7 planning

On 15 March 2023 20:33:47 GMT, Jonathan Wiltshire wrote: >Hi, > >We're overdue for 11.7 and need it done with a keyring update included >before bookworm can be released. The wheels are turning on the keyring so >how do dates in April look for everybody? Saturdays are 1st (probably too >soon),

11.7 planning

Hi, We're overdue for 11.7 and need it done with a keyring update included before bookworm can be released. The wheels are turning on the keyring so how do dates in April look for everybody? Saturdays are 1st (probably too soon), 8th, 15th, 22nd and 29th. Thanks, -- Jonathan Wiltshire

Re: 11.7 planning

Jonathan Wiltshire (2023-03-15): > We're overdue for 11.7 and need it done with a keyring update included > before bookworm can be released. The wheels are turning on the keyring so > how do dates in April look for everybody? Saturdays are 1st (probably too > soon), 8th, 15th, 22nd and 29th. I

Re: 11.7 planning

On Wed, 2023-03-15 at 20:33 +, Jonathan Wiltshire wrote: > We're overdue for 11.7 and need it done with a keyring update > included > before bookworm can be released. The wheels are turning on the > keyring so > how do dates in April look for everybody? Saturdays are 1st (probably > too >

Re: Starting the weekly live images for Bookworm building again

Alright should remember that for the future but then i know, did it broke hardware or software wise, is a new box gonna be there to replace it to get updated images or what is the plan? On 3/15/23, Cyril Brulebois wrote: > Luna Jernberg (2023-03-15): >> And now they have not built for 2 days

Re: Starting the weekly live images for Bookworm building again

Luna Jernberg (2023-03-15): > And now they have not built for 2 days any specific reason? casulana broke; please refrain from hijacking threads and cross-posting to so many lists. debian-cd would have done just fine… Cheers, -- Cyril Brulebois (k...@debian.org)

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi, James Addison wrote: > The problem, in both cases, was that I hadn't copied the '.disk' dotfile > directory from the install media ISO filesystem(s) in each case. Besides such user pitfalls with the produced ISO and the problem of symbolic links there are other constraints which an ISO has

Re: Starting the weekly live images for Bookworm building again

And now they have not built for 2 days any specific reason? On 3/15/23, Holger Wansing wrote: > Hi, > > Steve McIntyre wrote (Tue, 31 Jan 2023 15:36:53 +): >> On Mon, Jan 16, 2023 at 05:35:50PM +0100, Roland Clobus wrote: >> >* localechooser: A minor fix [A3] >> >> No idea about that,

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi James On 2023.03.15 00:47, James Addison wrote: The problem, in both cases, was that I hadn't copied the '.disk' dotfile directory from the install media ISO filesystem(s) in each case. Ah, yes, the infamous '.disk/' directory. If it's any consolation, you're not the first person to

Re: Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Please disregard my previous message to this list, that was a bug specific reply sent to the wrong e-mail. /Pete

Re: Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi James, On 2023.03.15 00:47, James Addison wrote: The problem, in both cases, was that I hadn't copied the '.disk' dotfile directory from the install media ISO filesystem(s) in each case. Ah, yes, the infamous '.disk/' directory. If it's any consolation, you're not the first person to

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Package: debian-cd Followup-For: Bug #1031696 On Wed, 15 Mar 2023 00:04:28 +, James Addison wrote: > I haven't (have not) been able to install Debian from FAT32-based media > created > using file-copy from either of these two approaches. > In both cases d-i integrity checks of the FAT32

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Followup-For: Bug #1031696 On Mon, 13 Mar 2023 01:04:26 +, James Addison wrote: > I've been able to build local NETINST ISO images successfully using the merged > changes (thanks, Steve), and was also able to file-copy them to a FAT32 > filesystem and successfully boot from that into Debian

Re: Starting the weekly live images for Bookworm building again

Hi, Steve McIntyre wrote (Tue, 31 Jan 2023 15:36:53 +): > On Mon, Jan 16, 2023 at 05:35:50PM +0100, Roland Clobus wrote: > >* localechooser: A minor fix [A3] > > No idea about that, leaving for somebody else. A (small) change, that we want, I guess, to add Curaçao to Carribean region,

Bug#1032941: Additional use of Rock Ridge symbolic links in bookwork ISO images

Hi, the use of xorrisofs/genisoimage option -f would convert those links into shared content data files, too. Side note: Differing from my statement in bug #1031696, the current xorriso version does not complain about dangling symbolic links when -f is given. It silently includes them as

Re: Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

On 2023.03.13 01:04, James Addison wrote: Pete: perhaps it'd be worth filing a separate bug for the documentation-copy issue? It'd be good to understand what the practical implications of that are. I have now created https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032941. Personally, I

Bug#1032941: Additional use of Rock Ridge symbolic links in bookwork ISO images

Package: debian-cd Version: debian-testing-amd64-DVD.iso (2023.03.08) This is a requested follow up to #1031696 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031696). Besides essential installation packages using symlinks, the upcoming bookworm also uses symlinks for non essential

Bug#1031696: Also affects bookworm

On 2023.03.13 12:16, Holger Levsen wrote: what's FST? https://en.wikipedia.org/wiki/FST is not helpful. File System Transposition. It's in the title of this very bug report and after repeating it all over the place for a while, I hope that using a shorthand for the term is fine. /Pete

Bug#1031696: Also affects bookworm

On Sun, Mar 12, 2023 at 06:11:51PM +, Pete Batard wrote: > I will venture that this is because, and this is not criticism per se, most > distributions currently make that process quite difficult or fraught with so > many hurdles that people who would want to use FST will not yet bother >

Processed: Re: Use of symbolic links in non-free ISO images breaks file system transposition support

Processing control commands: > tags -1 - moreinfo Bug #1031696 [debian-cd] Use of symbolic links in non-free ISO images breaks file system transposition support Removed tag(s) moreinfo. -- 1031696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031696 Debian Bug Tracking System Contact

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Followup-For: Bug #1031696 Control: tags -1 - moreinfo I've been able to build local NETINST ISO images successfully using the merged changes (thanks, Steve), and was also able to file-copy them to a FAT32 filesystem and successfully boot from that into Debian Installer using QEMU. Building

Bug#1017555: marked as done (Let's drop win32-loader from amd64/i386 and multiarch CDs)

Your message dated Sun, 12 Mar 2023 21:08:09 + with message-id <20230312210809.ga261...@tack.einval.com> and subject line Re: Bug#1017555: Let's drop win32-loader from amd64/i386 and multiarch CDs has caused the Debian Bug report #1017555, regarding Let's drop win32-loader from amd64/i386 and

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Package: debian-cd Followup-For: Bug #1031696 > >Thinking aloud: as an alternative, would adding the '-f' flag to MKISOFS > >achieve the desired result for both documentation and firmware files, without > >requiring any other changes? > No, then I expect we'll simply end up with duplicate copies

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi, James Addison wrote: > Thinking aloud: as an alternative, would adding the '-f' flag to MKISOFS > achieve the desired result for both documentation and firmware files, > without requiring any other changes? Let's pack up some symbolic links with -f: $ sudo mount

Bug#1031696: Also affects bookworm

Hi Steve, On 2023.03.12 14:53, Steve McIntyre wrote: It looks like James (with some help from Thomas) has worked out a quick way to change things to make things better for you, which is good! (Thanks, guys! I'm about to test the change locally.) Yes, I'm happy to see this development as well.

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

On Sun, Mar 12, 2023 at 05:43:24PM +, James Addison wrote: >Followup-For: Bug #1031696 > >Thinking aloud: as an alternative, would adding the '-f' flag to MKISOFS >achieve the desired result for both documentation and firmware files, without >requiring any other changes? No, then I expect

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Followup-For: Bug #1031696 Thinking aloud: as an alternative, would adding the '-f' flag to MKISOFS achieve the desired result for both documentation and firmware files, without requiring any other changes? (I'll mention as context that there are symlinks in the debian-faq tarball that is used

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi, James Addison wrote: > Please find below a proposed update to the commit message under discussion: Only one nitpick: > multiple filenames ("records"). The ISO9660 generation tools > genisoimage and xorriso can use this to de-duplicate multiple linked > files from their input,

Bug#1031696: Also affects bookworm

Hi Pete, On Thu, Mar 09, 2023 at 08:24:08PM +, Pete Batard wrote: >Please note that, since bookworm has started to include firmware files, this >issue is also starting to affect bookworm users [1] and I can only advise >Debian maintainers to raise its priority, rather than dismiss it as

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Package: debian-cd Followup-For: Bug #1031696 X-Debbugs-Cc: scdbac...@gmx.net Please find below a proposed update to the commit message under discussion: nonfree-firmware: when creating on-disc firmware links, use the same link creation logic as archive-area links This changeset

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi, James Addison wrote: > I've opened a merge request at > https://salsa.debian.org/images-team/debian-cd/-/merge_requests/30 > [...] > The commit message contains an effort to explain what's going on; please > consider that message as reviewable and open to feedback too. I'm clumsy with web

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Package: debian-cd Followup-For: Bug #1031696 Thank you again Thomas. I've opened a merge request at https://salsa.debian.org/images-team/debian-cd/-/merge_requests/30 My Debian mirror is still under construction, hence the 'draft' status for the merge request (to indicate that I'm not certain

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi, James Addison wrote: > My interpretation of the commands and output in your comment is that both > genisoimage and xorriso can translate hardlinks from a source filesystem > into deduplicated file references in a written ISO filesystem With genisoimage we only know empirically. With libisofs

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Followup-For: Bug #1031696 On Sat, 11 Mar 2023 18:10:22 +0100, Thomas Schmitt wrote: > ifneq (,$(filter i386 amd64 arm64 hppa,$(ARCHES))) > Surely i386, amd64, and arm64 get their published Debian ISOs made > by xorriso. I think your expectation is correct there, yes: looking further into the

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi, James Addison wrote: > it looks like the selection of CD image > creation tool is configured per-architecture here: > https://salsa.debian.org/images-team/debian-cd/-/blob/5aebb6794a3b8b2393663fb643e35eb8e510c9a4/Makefile#L24 I wish i would understand the clause ifneq (,$(filter i386 amd64

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Followup-For: Bug #1031696 On Sat, 11 Mar 2023 12:16:47 +0100, Thomas Schmitt wrote: > This could be achieved by a bunch of hard links instead of the symbolic > links. In /firmware of firmware-bookworm-DI-alpha1-amd64-netinst.iso > i see only symbolic links to data files. So replacing symlinks by

Bug#1031696: Also affects bookworm

On 2023.03.11 13:37, Cyril Brulebois wrote: >> I am also concerned about your view that nobody outside of a few >> users would want to create Debian installation media using their >> native OS utilities, which is very reductive in my opinion (...) > You seem to be putting words in my mouth I

Bug#1031696: Also affects bookworm

Pete Batard (2023-03-11): > In other words, the minute you add a package to the standard ISO, that > may be required for installation, it is my opinion that that package > should be accessible for both 'dd' and FST modes of creating Debian > installation media. If this isn't the case, then I will

Bug#1031696: Also affects bookworm

On 2023.03.11 13:06, Cyril Brulebois wrote: That. is. not. a. change. from. Bullseye. It is when you consider from a standpoint that an image created with 'dd' should perform the same in terms of being able to retrieve .deb packages as one that is created through file system transposition.

Bug#1031696: Also affects bookworm

Hi, Pete Batard (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

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi James, > so the regression: > > * IS NOT that non-free firmware becomes unavailable when UEFI > file transposition is used to create bootable drives > -- because that firmware was not available previously > > * IS that bootable drives created using UEFI file transposition >

Bug#1031696: Also affects bookworm

Hi Cyril, 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. Whereas one could use file

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Hi, James Addison wrote: > Something that symlinks can do is to allow image creators to save space by > by de-duplicating files. [...] This could be achieved by a bunch of hard links instead of the symbolic links. In /firmware of firmware-bookworm-DI-alpha1-amd64-netinst.iso i see only symbolic

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Package: debian-cd Followup-For: Bug #1031696 Hi Pete - could you check my understanding of your paragraph: > In short, if this issue is left unaddressed, bookworm will be > introducing a *regression* compared to bullseye, in that it will no > longer be possible to perform a Debian

Bug#1031696: Also affects bookworm

Pete Batard (2023-03-09): > In short, if this issue is left unaddressed, bookworm will be introducing a > *regression* compared to bullseye, in that it will no longer be possible to > perform a Debian installation on a UEFI system through file system > transposition, and everyone will be forced

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Package: debian-cd Followup-For: Bug #1031696 On Sat, 11 Mar 2023 03:31:50 +, Pete wrote: > Just going to add, in case you wonder why it shouldn't be up to the > software that is mounting the ISO to sort out symbolic links and just > duplicate content, that neither Windows File Explorer

Processed: Re: Use of symbolic links in non-free ISO images breaks file system transposition support

Processing control commands: > reassign -1 debian-cd Bug #1031696 [cdimage.debian.org] Use of symbolic links in non-free ISO images breaks file system transposition support Bug reassigned from package 'cdimage.debian.org' to 'debian-cd'. Ignoring request to alter found versions of bug #1031696

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Followup-For: Bug #1031696 X-Debbugs-Cc: p...@akeo.ie Control: reassign -1 debian-cd Control: tags -1 moreinfo I forgot to mention: thanks, Pete, for testing this UEFI file transposition support with bookworm's d-i alpha 2. We're all volunteers and I'm no expert with the CD image build process,

Processed: Re: cdimage.debian.org: bookworm net-install CD hangs on "Detecting Network Hardware"

Processing control commands: > reassign -1 debian-cd Bug #1005886 [cdimage.debian.org] cdimage.debian.org: bookworm net-install CD hangs on "Detecting Network Hardware" Bug reassigned from package 'cdimage.debian.org' to 'debian-cd'. Ignoring request to alter found versions of bug #1005886 to

Bug#1005886: cdimage.debian.org: bookworm net-install CD hangs on "Detecting Network Hardware"

Followup-For: Bug #1005886 Control: reassign -1 debian-cd Control: retitle -1 debian-cd: bookworm net-install CD hangs on "Detecting Network Hardware"

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Thanks for looking into this. Just going to add, in case you wonder why it shouldn't be up to the software that is mounting the ISO to sort out symbolic links and just duplicate content, that neither Windows File Explorer nor 7-zip (both of which can mount/extract ISO content) will list

Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support

Package: cdimage.debian.org Followup-For: Bug #1031696 X-Debbugs-Cc: p...@akeo.ie My best guess at the moment is that the relevant section of the CD image preparation scripts is:

Bug#1031696: Also affects bookworm

Please note that, since bookworm has started to include firmware files, this issue is also starting to affect bookworm users [1] and I can only advise Debian maintainers to raise its priority, rather than dismiss it as something that will only affect folks who don't use DD mode to write the

Re: "up to 300 mb in size"

On Wed, Mar 08, 2023 at 05:23:29AM -0500, nick black wrote: >Steve McIntyre left as an exercise for the reader: >> Yup, we know. Things are growing over time. >> In fact, the bookworm release will be bigger again due to including >> firmware too. > >my sincere apologies if this came off as a

Re: "up to 300 mb in size"

Steve McIntyre left as an exercise for the reader: > Yup, we know. Things are growing over time. > In fact, the bookworm release will be bigger again due to including > firmware too. my sincere apologies if this came off as a complaint about the size or anything else; i just wanted to bring it to

Re: "up to 300 mb in size"

Right should be right ;) Maybe update that website for the 11.7 or 12 release :p On 3/8/23, Steve McIntyre wrote: > On Wed, Mar 08, 2023 at 02:53:43AM -0500, nick black wrote: >>the netinst page claims: >> >> Up to 300 MB in size, this image contains the installer and a >> small set of packages

Re: "up to 300 mb in size"

On Wed, Mar 08, 2023 at 02:53:43AM -0500, nick black wrote: >the netinst page claims: > > Up to 300 MB in size, this image contains the installer and a > small set of packages which allows the installation of a (very) > basic system. > > netinst CD image (generally 150-300 MB, varies by

"up to 300 mb in size"

the netinst page claims: Up to 300 MB in size, this image contains the installer and a small set of packages which allows the installation of a (very) basic system. netinst CD image (generally 150-300 MB, varies by architecture) but we're now at 400MB on amd64: [schwarzgerat](0) $ ls -l

Re: Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

Why am I getting these bug reports? I think I've been accidentally added to your team mailing list. On March 1, 2023 1:32:13 AM CST, Cyril Brulebois wrote: >Cyril Brulebois (2023-02-27): >> Unfortunately, I wasn't aware of those instructions, and that looks utterly >> buggy. How can we claim

Re: Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

Cyril Brulebois (2023-02-27): > Unfortunately, I wasn't aware of those instructions, and that looks utterly > buggy. How can we claim to publish “official images” that are snapshots, built > using debian-installer daily builds, that can be broken by random packages in > unstable, and left unfixed

Re: Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

Hi, Cesar Enrique Garcia Dabo (2023-02-27): > Thank you for the answer. Good to know that it is a known issue and is being > taken care of. > > Regarding why I took that image. I just followed the official Debian > webpages: > > https://www.debian.org/CD/http-ftp/index.en.html Many thanks for

Bug#1032071: ARM firmware packages included in amd64 installation images

Package: debian-cd Version: 3.2.0 Severity: minor debian-bookworm-DI-alpha2-amd64-netinst.iso includes firmware packages for ARM platforms: firmware-qcom-soc firmware-samsung firmware-ti-connectivity raspi-firmware These packages add 34 MB to the ISO image, which is not negligible.

Re: Bug#1031622: d-i regression in weekly builds: FEATURE_C12 unsupported by the installed e2fsck

Control: reassign -1 src:e2fsprogs 1.47.0-1 Control: retitle -1 mke2fs: should not enable orphan_file by default until trixie Control: affects -1 installation-reports On Fri, 24 Feb 2023 at 18:43:05 +0100, Cyril Brulebois wrote: > Simon McVittie (2023-02-24): > > caused by the mke2fs in

Re: Bug#1031622: d-i regression in weekly builds: FEATURE_C12 unsupported by the installed e2fsck

Simon McVittie (2023-02-24): > If I understand the situation correctly, that means the regression here is > indeed caused by the mke2fs in e2fsprogs/unstable defaulting to creating > a filesystem that cannot be fsck'd by the e2fsck in e2fsprogs/testing, > because orphan_file is a "compat" feature

Re: Bug#1031622: d-i regression in weekly builds: FEATURE_C12 unsupported by the installed e2fsck

On Fri, 24 Feb 2023 at 16:56:23 +0100, Cyril Brulebois wrote: > Cyril Brulebois (2023-02-19): > > Simon McVittie (2023-02-19): > > > Are d-i alphas and weekly builds built differently? Is it perhaps the > > > case that alphas are built from testing udebs, while weeklies are built > > > from

debian-cd_3.2.0_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 24 Feb 2023 17:04:14 +0100 Source: debian-cd Architecture: source Version: 3.2.0 Distribution: unstable Urgency: medium Maintainer: Debian CD Group Changed-By: Cyril

Bug#1031424: marked as done (add config option to control mixed-mode EFI on x86)

Your message dated Fri, 24 Feb 2023 16:49:01 + with message-id and subject line Bug#1031424: fixed in debian-cd 3.2.0 has caused the Debian Bug report #1031424, regarding add config option to control mixed-mode EFI on x86 to be marked as done. This means that you claim that the problem has

Processing of debian-cd_3.2.0_source.changes

debian-cd_3.2.0_source.changes uploaded successfully to localhost along with the files: debian-cd_3.2.0.dsc debian-cd_3.2.0.tar.xz debian-cd_3.2.0_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Re: Bug#1031622: d-i regression in weekly builds: FEATURE_C12 unsupported by the installed e2fsck

Hi Simon, Cyril Brulebois (2023-02-19): > Simon McVittie (2023-02-19): > > Are d-i alphas and weekly builds built differently? Is it perhaps the > > case that alphas are built from testing udebs, while weeklies are built > > from unstable udebs? > > Let's quote

Processed: reassign 1031696 to cdimage.debian.org, severity of 1008654 is normal, tagging 1008654 ...

Processing commands for cont...@bugs.debian.org: > reassign 1031696 cdimage.debian.org Bug #1031696 [non-free] Use of symbolic links in non-free ISO images breaks file system transposition support Warning: Unknown package 'non-free' Bug reassigned from package 'non-free' to 'cdimage.debian.org'.

Re: Bug#1031622: d-i regression in weekly builds: FEATURE_C12 unsupported by the installed e2fsck

Simon McVittie (2023-02-19): > Are d-i alphas and weekly builds built differently? Is it perhaps the > case that alphas are built from testing udebs, while weeklies are built > from unstable udebs? Let's quote : - Or install the current

Bug#1031598: marked as done (debian-cd: missing Contents-firmware in firmware archives (tar, zip, cpio))

Your message dated Sun, 19 Feb 2023 08:36:43 + with message-id <20230219083643.gd20...@tack.einval.com> and subject line Re: Bug#1031598: debian-cd: missing Contents-firmware in firmware archives (tar, zip, cpio) has caused the Debian Bug report #1031598, regarding debian-cd: missing

Processed: Re: Bug#1031598: debian-cd: missing Contents-firmware in firmware archives (tar, zip, cpio)

Processing control commands: > tag -1 patch pending Bug #1031598 [debian-cd] debian-cd: missing Contents-firmware in firmware archives (tar, zip, cpio) Added tag(s) pending and patch. -- 1031598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031598 Debian Bug Tracking System Contact

Bug#1031598: debian-cd: missing Contents-firmware in firmware archives (tar, zip, cpio)

Control: tag -1 patch pending Cyril Brulebois (2023-02-19): > As mentioned earlier on #debian-cd: the firmware archives generated by > make-firmare-image contain the dep11/ directory but are missing the > Contents-firmware index that was added to make hw-detect's easier (and > slightly faster).

Bug#1031598: debian-cd: missing Contents-firmware in firmware archives (tar, zip, cpio)

Package: debian-cd Severity: normal As mentioned earlier on #debian-cd: the firmware archives generated by make-firmare-image contain the dep11/ directory but are missing the Contents-firmware index that was added to make hw-detect's easier (and slightly faster). Cheers, -- Cyril Brulebois --

Bug#1031424: add config option to control mixed-mode EFI on x86

Package: debian-cd Version: 3.1.36 Severity: normal [ Reminder for me ] I've added support for mixed-mode EFI stuff on amd64 builds. Add an option to enable/disable it, so that local hack builds don't need both amd64 and i386 d-i builds to function. -- System Information: Debian Release: 11.6

<    1   2   3   4   5   6   7   8   9   10   >