Hi,
> https://launchpad.net/ubuntu/+source/cd-boot-images-amd64/7
Oh. This explains why there is still an invalid GPT in
http://cdimage.ubuntu.com/daily-live/current/groovy-desktop-amd64.iso
which i downloaded 2 days ago.
Above change has at its end:
+ echo 'xorriso -as mkisofs [...]
Thanks! I keep discovering new ones :P
I'm marking this bug as Fix Released, as LP: #1886148 is.
** Changed in: casper (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Tue, 6 Oct 2020 at 22:20, Paride Legovini <1895...@bugs.launchpad.net>
wrote:
> I can't spot what change caused the /efi directory to be included again
> in the ISO filesystem. Does anybody have a pointer?
It was this upload I think:
I can confirm the /efi directory is back, although with different
capitalization than before:
Focal:
/EFI
/EFI/BOOT
/EFI/BOOT/BOOTx64.EFI
/EFI/BOOT/grubx64.efi
/EFI/BOOT/mmx64.efi
Groovy:
/efi/
/efi/boot
/efi/boot/bootx64.efi
/efi/boot/grubx64.efi
/efi/boot/mmx64.efi
This is a bit annoying
@sudodus, you're right. I just tested the 2020.10.04 daily build and, as
opposed to the beta, it does contain a /efi/ directory at root level
with all the relevant files.
If this is carried out into the release, then, as far as I am concerned,
this bug can be closed.
--
You received this bug
@ Akeo,
If I understand correctly, this bug is fixed in the current daily Groovy
iso files. These files are newer than the Groovy beta iso files.
http://iso.qa.ubuntu.com/qatracker/milestones/413/builds
I can extract the content of an iso file to a FAT32 partition and get a
USB boot drive, that
Any update on this?
As a reminder, ALL that is being asked from this bug is to duplicate the
files and directories currently found in /boot/grub/efi.img to the root
level of the ISO. That's it.
It's a very straightforward fix, and, with the beta now being out, the
need to fix this becomes
** Merge proposal linked:
https://code.launchpad.net/~utah/utah/+git/utah/+merge/390895
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895131
Title:
Groovy Desktop *BREAKS* the most common
Hi,
This bug is affecting the automated ISO testing of the Desktop and
Server images, as UTAH (the test framework) validates the EFI files
contained in the main iso9660 filesystem as part of the ISO static
validation stage. An actual install with UEFI boot is also performed as
part of the test
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1895131
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi,
Steve Langasek wrote:
> Reading https://lists.debian.org/debian-cd/2019/07/msg7.html was very
> helpful in clarifyingthe options needed to get the image structure we
> are looking for.
At least the ISO would comply to the specs, although this is in no way
mandatory for boot success. :))
Thomas, thanks for weighing in. Reading https://lists.debian.org
/debian-cd/2019/07/msg7.html was very helpful in clarifying the
options needed to get the image structure we are looking for. I think
we may now have the xorriso options sorted out (though, this does not
address the /EFI/BOOT
Hi,
> avoiding characters like '*', '?', '<', '>', ':', '|'... That's all.
Except ':' the others have a meaning to the shell and thus would be a
controversial choice.i
In case of Debian it is nearly defined what characters are allowed in a
package name.
Just going to point out that I was NOT talking about limiting file names
to 8.3.
FAT32/vfat does has LFN support, and the UEFI FAT driver supports LFN as
well, so, NO, what I was talking about was not about suddenly asking
distro maintainers to use 8.3 names.
It's only about case sensitivity
Hi,
> the EDK2/UEFI folks are more inclined to have the existing EDK2 code
> drive the specs, especially for boot, than the opposite.
It really was supposed to be the other way round this time. :))
But well, firmware is as firmware is.
As said, having a copy of the ESP tree in the ISO should be
Hi Thomas. Glad to see you onboard here as well. ;)
First of all, I guess I should point out that UEFI bootloader boot from
non ESP partitions is hardly a "trick". It is de-facto. That behaviour
comes from the EDK2 source itself and, as my recent dealings with EDK2
indicate (in [1]) that the
@ Thomas Schmitt (scdbackup),
Thanks for chipping in and offering help :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895131
Title:
Groovy Desktop *BREAKS* the most common method of creating
Hi,
i am the developer of xorriso. If there are problems after changing
the xorriso arguments i am ready to help identifying the cause.
My own opinion about how Debain (and Ubuntu) ISOs for BIOS|EFI from CD|HDD
should look like is to see in
@ Michael Hudson-Doyle (mwhudson),
Please let us know, when this change will be available for iso testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895131
Title:
Groovy Desktop *BREAKS* the
I think this change https://code.launchpad.net/~mwhudson/debian-cd/half-
the-grubs/+merge/387085 will make things more like they were.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895131
Title:
@Akeo,
I have seen the problem that you address in this bug report, and I was
afraid that it may cause problems for you[r tool] and others who use
extracting methods. Thanks for speaking out load about it.
There is an additional problem too, that some computers do not even boot
from cloned
I have been trying to boot the latest Groovy daily by loop mounting the
ISO file. It works in BIOS mode but not in UEFI mode. This is worse than
the problems with GRUB 2.04.
I am wondering if this is related to Bug
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892754
--
You received
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: casper (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895131
Title:
23 matches
Mail list logo
