Bug#948435: gdisk: cgdisk claims that attribute flags are all set to 0

2022-04-10 Thread Rod Smith
I believe I've fixed this bug. It's in the following commit to the GPT fdisk git repository: https://sourceforge.net/p/gptfdisk/code/ci/b056f3860ad587c01ed9e2a0bae6cc3ba8d41535/ I expect to make a new 1.0.9 release of GPT fdisk sometime in the next few days, including this bug fix. -- Rod

Bug#994676: gdisk FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]

2022-04-10 Thread Rod Smith
Thanks for the bug report and patch. I've added the patch referenced in this bug report to the GPT fdisk git repository. I expect to make a new 1.0.9 release with this fix in the next few days. https://sourceforge.net/p/gptfdisk/code/ci/4be26d7228a5dadfd04488618f08a29f0c67dd8c/ -- Rod Smith

Bug#876393: gdisk: valgrind reports conditional evaluation depends on unitialized variable

2022-04-10 Thread Rod Smith
Thanks for the patch! I've just added it to the GPT fdisk git repository: https://sourceforge.net/p/gptfdisk/code/ci/8ff360f49eda175142e01d46edbb494cfebe309d/ (I expect to do a new release soon, FWIW.) -- Rod Smith rodsm...@rodsbooks.com http://www.rodsbooks.com

Bug#873452: gdisk reports "Total free space is 18446744073709551581 sectors (16.0 EiB)"

2022-04-10 Thread Rod Smith
I've just added a fix for this; see: https://sourceforge.net/p/gptfdisk/code/ci/6b7486db9927a1b3f6dd9cc84dff54c33a8aef8c/tree/gpt.cc?diff=4be26d7228a5dadfd04488618f08a29f0c67dd8c -- Rod Smith rodsm...@rodsbooks.com http://www.rodsbooks.com

Bug#995623: refind FTBFS: error: conflicting types for ‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’

2021-10-23 Thread Rod Smith
86: gnuefi] Error 2 >>> | make[2]: Leaving directory '/<>' >>> | dh_auto_build: error: make -j1 gnuefi ARCH=x86_64 returned exit code 2 >>> | make[1]: *** [debian/rules:33: override_dh_auto_build] Error 25 >>> | make[1]: Leaving directory '/<>' >>> | make: *** [debian/rules:26: build] Error 2 >>> | dpkg-buildpackage: error: debian/rules build subprocess returned exit >>> status 2 >>> >>> Also seen by crossqa: >>> http://crossqa.debian.net >>> >>> Reproduced natively on arm64 by reproducible builds: >>> https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/refind_0.12.0-1.rbuild.log.gz >>> >>> Helmut >>> -- Rod Smith rodsm...@rodsbooks.com http://www.rodsbooks.com

Bug#995623: refind FTBFS: error: conflicting types for ‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’

2021-10-21 Thread Rod Smith
[1]: Leaving directory '/<>' >> | make: *** [debian/rules:26: build] Error 2 >> | dpkg-buildpackage: error: debian/rules build subprocess returned exit >> status 2 >> >> Also seen by crossqa: >> http://crossqa.debian.net >> >> Reproduced natively on arm64 by reproducible builds: >> https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/refind_0.12.0-1.rbuild.log.gz >> >> Helmut >> -- Rod Smith rodsm...@rodsbooks.com http://www.rodsbooks.com

Bug#843000: refind: fails to install on NVMe

2020-02-17 Thread Rod Smith
d 0.11.5 a few days ago, and this commit is the first since then. As to efibootmgr requiring "/dev/nvme0n1p1", rather than the as-expected "/dev/nvme0n1", as an option to "-d", that sounds like an efibootmgr bug, and on my main test system (running Linux Mint 19, using efibootmgr 15-1), it takes "/dev/nvme0n1" and works correctly. -- Rod Smith rodsm...@rodsbooks.com http://www.rodsbooks.com

Bug#949130: refind-install fails to determine the ESP partition

2020-01-23 Thread Rod Smith
this context. OTOH, presenting a disseration on the differences between the Linux vfat and msdos drivers in this warning would be overkill. Probably changing "...it must be VFAT!" to "...it must be VFAT (not msdos)!" would help. I've just pushed that change to the rEFInd git repository. -- Rod Smith rodsm...@rodsbooks.com http://www.rodsbooks.com

Bug#843000: refind: fails to install on NVMe

2016-11-03 Thread Rod Smith
On 11/03/2016 02:16 PM, Tianon Gravi wrote: > On 3 November 2016 at 11:03, Rod Smith <rodsm...@rodsbooks.com> wrote: >> Good question. I guess it depends on what efibootmgr wants, since that's >> where the variable is used. The efibootmgr man page implies it wants a >>

Bug#843000: refind: fails to install on NVMe

2016-11-03 Thread Rod Smith
On 11/03/2016 01:29 PM, Tianon Gravi wrote: > On 3 November 2016 at 10:28, Tianon Gravi <tia...@debian.org> wrote: >> On 3 November 2016 at 10:19, Rod Smith <rodsm...@rodsbooks.com> wrote: >>> Note, however, that I have no NVMe or similar devices on which to test. &

Bug#843000: refind: fails to install on NVMe

2016-11-03 Thread Rod Smith
devices. -- Rod Smith rodsm...@rodsbooks.com http://www.rodsbooks.com

Bug#715426: Version 0.10.1

2015-12-12 Thread Rod Smith
elease with Debian packaging tweaks and we can base the first Debian release off of it. I think that's about it. Unless there are other outstanding issues. I'm ready to push this version for inclusion in Debian! Tianon, if you can advise me on the next step, I'd appreciate it. Thanks! -- Rod Smith

Bug#715426: Bug # 715426: Interested in getting this done

2015-11-29 Thread Rod Smith
n the main rEFInd package since 0.10.0 that I hope to push out a 0.10.1 version soon -- probably in a week or two. My intent is to get the debian/copyright and other major packaging files in order by that time so as to smooth the way to getting 0.10.1 included in the Debian repos, assuming no major unforseen hangup. -- Rod Smith rodsm...@rodsbooks.com http://www.rodsbooks.com

Bug#739824: partman-efi: The term EFI boot partition is non-standard and adds to community confusion

2014-02-22 Thread Rod Smith
Package: partman-efi Severity: normal Dear Maintainer, The partman-efi package refers to the EFI System Partition (ESP) as an EFI boot partition. The latter name is non-standard; AFAIK, it's used *only* in partman-efi and tools derived from it, such as Ubuntu's ubiquity. It's therefore

Bug#723669: gptsync: Doesn't understand linux filesystem gpt partition type

2013-11-07 Thread Rod Smith
Note that the parent package (rEFIt) is no longer maintained. I've forked rEFIt into rEFInd (http://www.rodsbooks.com/refind) and I've updated the gptsync program in rEFInd in such a way that this problem is fixed; however, at present, gptsync compiles only into an EFI binary. Patches to

Bug#637276: Version 3.0p is now available

2012-04-22 Thread Rod Smith
the required features were added, but GNU-EFI 3.0p is sufficient. -- Rod Smith rodsm...@rodsbooks.com http://www.rodsbooks.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#637572: [Gptfdisk-general] Bug#637572: gdisk: fails to write protective MBR

2011-08-25 Thread Rod Smith
of them. With any luck that'll enable me to reproduce and fix the bug. In the meantime, the workaround for you is obvious: Use your locally-compiled (with GCC 4.4.5) version of gdisk! -- Rod Smith rodsm...@rodsbooks.com http://www.rodsbooks.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ

Bug#637572: [Gptfdisk-general] Bug#637572: gdisk: fails to write protective MBR

2011-08-15 Thread Rod Smith
might turn up a set of options that would work. (Search the gcc man page for ARM Options to turn up a list of options.) Unfortunately, I don't have any ARM hardware myself. I'll look into setting up a virtual ARM machine using QEMU, but it may be a few days before I can get to that -- Rod