Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#75409 - [ostree] don't inject ostree module into dracut initramfs
Attached to Project:
Arch Linux
Opened by tinywrkb (tinywrkb) - Sunday, 24 July 2022, 16:01 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 09 August 2022, 05:53 GMT
Opened by tinywrkb (tinywrkb) - Sunday, 24 July 2022, 16:01 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 09 August 2022, 05:53 GMT
|
DetailsI don't think it's acceptable to force the ostree module by installing /etc/dracut.conf.d/ostree.conf, this should be opt-in.
Does it ill effects? Probably not, but I think it's still a bad practice. See this ostree module complains while debugging initrd issue today, and thought it had no place there. Remove (or relocating) /etc/dracut.conf.d/ostree.conf from the package is possibly a breaking change, but no one sane should be using ostree-admin with Arch Linux, as Arch Linux packaging practices are a bad fit for /usr system delivery (or whatever you want to call it), e.g. packaging ucode in /boot instead of deploying from /usr/lib/fw. Oh! And I know that the obvious answer is to omit the module. I'm already doing that, but this still shouldn't be forced on other users. |
This task depends upon
This is how upstream seems to envision this to work. Have you opened an upstream ticket for this?
But seeing your reply here, I guess you don't agree, so I open one now @ https://github.com/ostreedev/ostree/issues/2723.