Followup-For: Bug #1036828
X-Debbugs-Cc: k...@debian.org
On Sat, 24 Feb 2024 11:01:31 +, I wrote:
> Should this bug be closed? (the logic to skip the experimental/sid firmware
> image build during non-testing builds is in place for both bookworm and
> trixie)
Nope, it looks like I've
Followup-For: Bug #1036828
X-Debbugs-Cc: k...@debian.org
Hi Cyril,
Should this bug be closed? (the logic to skip the experimental/sid firmware
image build during non-testing builds is in place for both bookworm and trixie)
Regards,
James
Followup-For: Bug #994274
X-Debbugs-Cc: lu...@schwaighofer.name, pk...@debian.org, timo.lindf...@iki.fi
Hi Lukas, Philipp, Timo,
Does reverting the removal[1] of 'efisetjmp.h' from 'efi.h' in src:gnu-efi
produce successful results?
That occurred between gnu-efi versions 3.0.9 and 3.0.13 if I
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
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
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 in
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
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
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
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
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
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
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
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
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
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,
Followup-For: Bug #1005886
Control: reassign -1 debian-cd
Control: retitle -1 debian-cd: bookworm net-install CD hangs on "Detecting
Network Hardware"
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:
18 matches
Mail list logo