Arch Linux

Please read this before reporting a bug:

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
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


I 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

Comment by David Runge (dvzrv) - Friday, 30 September 2022, 07:54 GMT
@tinywrkb: Thanks for the ticket.

This is how upstream seems to envision this to work. Have you opened an upstream ticket for this?
Comment by tinywrkb (tinywrkb) - Friday, 30 September 2022, 15:21 GMT
@dvzrv, no, I haven't filed an upstream ticket, as it seemed like a packaging decision.
But seeing your reply here, I guess you don't agree, so I open one now @
Comment by David Runge (dvzrv) - Friday, 30 September 2022, 15:36 GMT
Well, it's an upstream decision, but I'm also not actively preventing it from happening I guess (see