From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15703] New: Resolve sgdisk UUID warning in gptfdisk package
Date: Tue, 18 Jul 2023 16:23:00 +0000 [thread overview]
Message-ID: <bug-15703-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15703
Bug ID: 15703
Summary: Resolve sgdisk UUID warning in gptfdisk package
Product: buildroot
Version: 2023.02.3
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Outdated package
Assignee: unassigned@buildroot.uclibc.org
Reporter: jkoch@outrider.ai
CC: buildroot@uclibc.org
Target Milestone: ---
When using any option that generates a random UUID using sgdisk (e.g. sgdisk -G
/dev/sda) you are presented with the warning:
Warning! Unable to generate a proper UUID! Creating an improper one as a last
resort! Windows 7 may crash if you save this partition table!
This appears to stem from a change in libuuid where a #define was changed:
https://github.com/util-linux/util-linux/commit/10f5f79485964ab52272ebe79c3b0047b1f84d82
Upstream gptfdisk has resolved this issue on 2022-04-16 (and a few others
since) but these patches haven't yet made it into the buildroot package.
Upstream commit:
https://sourceforge.net/p/gptfdisk/code/ci/6a8416cbd12d55f882bb751993b94f72d338d96f/
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-07-18 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 16:23 bugzilla [this message]
2024-06-15 15:11 ` [Buildroot] [Bug 15703] Resolve sgdisk UUID warning in gptfdisk package bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-15703-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox