I have changed the title to "Anaconda Installer Using GPT on all architectures by Default" and updated the description as well. I'll be happy to work with Neil to extend the scope to image creation as well, but my original idea was to cover only the installer defaults the same way the F37 change did, so the change should reflect that as well. On Sat, Dec 21, 2024 at 4:59 PM Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote: > > On Sat, Dec 21, 2024 at 05:44:02AM -0700, Neal Gompa wrote: > > On Sat, Dec 21, 2024 at 2:13 AM Zbigniew Jędrzejewski-Szmek > > <zbyszek@xxxxxxxxx> wrote: > > > > > > On Thu, Dec 12, 2024 at 07:59:28PM +0100, Simon de Vlieger wrote: > > > > On 12/12/24 5:04 PM, Vojtech Trefny wrote: > > > > > The default we have in blivet actually applies only to systems > > > > > installed with Anaconda so this would not be true for many ARM > > > > > systems. The images used with arm-image-installer are different. > > > > > > > > While it is mentioned under scope the title of the change proposal reads as > > > > if it's targeting all images and architectures. > > > > > > Yeah, the Change page needs to be updated to describe the scope of the > > > change more precisely. In fact, the word "Anaconda" does not appear in > > > the title, Summary, or Detailed Description at all. One needs to read > > > until the very end to understand that this would only apply to images > > > created with Anaconda. > > > > > > > Well, I'd rather we actually did the same thing elsewhere too. > > Consistency here is valuable wherever we can achieve it. > > > > I was surprised to learn we can use GPT on IBM Z, so it's being > > explored to support it in kiwi: > > https://github.com/OSInside/kiwi/issues/2694 > > > > We already use GPT for x86_64 and Power systems. ARM is the fiddly one > > because ARM systems kind of suck in terms of platform coherence. > > > > I'm also thinking ahead a bit with RISC-V to figure out if we're going > > to have problems here too. I don't think we will, but who knows...? > > Sure, but let's not let aspirations get in the way of an accurate > description. If the proposal is extended to cover additional > areas — great. But in any case, we need to know what is and what > isn't in the scope. > > Zbyszek > -- > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
