*Confirm This Information.*
*It is totally against the ethics and civil service code of conduct in
accordance with oath of secrecy for me to do this but I wish to do this on
personal capacity believing you will not betray me but will surely come
back to reward me for my sincerity, honesty and for
Hi,
Chris Bainbridge:
I still can't create a partition, which was the original aim. Is it
supposed to work?
I succeeded with gdisk on my oldstable test machine (help texts and
clueless actions of mine not shown):
--
$ dd
On 8 April 2014 18:14, Steve McIntyre st...@einval.com wrote:
Other folks: could you please test the output of the next daily builds
and verify these work better for you?
I still can't create a partition, which was the original aim. Is it
supposed to work? If it is not possible to produce an
Hi,
the GPT header CRC of
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
looks ok now for me and for gdisk of oldstable (which formerly
complained about amd64 ISOs). Now it says:
GPT fdisk (gdisk) version 0.8.1
Partition
Hi,
my newest bug about gdisk hating an ISO with GPT and MBR is
not affecting debian-cd. (Further it is not GRUB2 specific.)
I can reproduce the user's symptoms with gdisk 0.8.1 and can work
around them by explicitely disabling multi-session emulation when
producing the ISO. This disabling is
On Mon, Apr 07, 2014 at 03:55:44PM +0200, Thomas Schmitt wrote:
Hi,
the bug in question is supposed to have existed in upstream until 1.3.4?
No.
It was introduced by 1.2.4 and fixed by 1.3.0.
So the version in Debian testing should be ok.
It's just that xorriso-1.3.6.pl01 is the newest upstream
Correct me if I got this wrong, but the bug in question is supposed to
have existed in upstream until 1.3.4?
I built several ISOs of our Ubuntu Privacy Remix live project using
upstream xorriso 1.3.0 and 1.3.1 So far I have not seen any UEFI test
machine which failed booting from USB drive
Hi,
the bug in question is supposed to have existed in upstream until 1.3.4?
No.
It was introduced by 1.2.4 and fixed by 1.3.0.
So the version in Debian testing should be ok.
It's just that xorriso-1.3.6.pl01 is the newest upstream release,
which i would of course like to see in Debian testing.
I am also a bit curious to know how the information regarding which
versions of software were used to create the .ISO . It seems this
info. is embedded in the .iso generated but there doesn't seem to be
any answers.
Mount the iso image, the file /.disk/mkisofs has the exact xorriso
command
Mount the iso image, the file /.disk/mkisofs has the exact xorriso
command line used to generate the image.
Apologies for the dupe info, I now see that Thomas already posted this detail.
btw the Ubuntu images have the same issue - Launchpad bug
https://bugs.launchpad.net/debian/+bug/1298912
Hi,
it is embarrassing to see the own bugs mummified since a
full year. You should rather enjoy the fresh and juicy bugs
of version 1.3.6.pl01.
Funnily nobody complains that the wrong GPT header checksum
would prevent booting from USB stick via EFI.
Doesn't (U)EFI check ? Do all tested machines
Hi,
because debian-cd also records the arguments of its xorriso run,
it should be not too hard to repack it with a newer xorriso,
which produces better GPT. E.g. xorriso-1.3.2 from Debian Sid.
You will need to copy the MBR from the original ISO
dd if=debian-7.3.0-amd64-netinst.iso bs=512
Hi all,
Just saw this bug. I am supposed to get a few desktop machines which
would have the newer GPT (GUID Partition Table) rather than MBR.
I am also a bit curious to know how the information regarding which
versions of software were used to create the .ISO . It seems this
info. is embedded in
Hi,
I am also a bit curious to know how the information regarding which
versions of software were used to create the .ISO . It seems this
info. is embedded in the .iso generated
xorriso by default writes its version info into the Preparer Id
field of the ISO Primary Volume Descriptor
Package: cdimage.debian.org
Severity: important
Dear Maintainer,
The GPT checksum of debian-7.4.0-amd64-netinst.iso (and other
wheezy and testing images) is incorrect due to a bug in the Xorriso build
tool used on the build system (confirmed by author of build tool). Reported on
mailing list but
15 matches
Mail list logo
