Arch Linux

vindicator

Member

Registered: 2016-02-25

Posts: 39

Dracut v111 Broken And Flagged Out Of Date

If there is a bug with the package, please create an issue on the gitlab instance.

Closing, for deletion.

WorMzy, the issue is that dracut is broken AND an update is available AND the package was flagged, but hasn't been updated.

My prior post stands and is valid here:

https://github.com/dracut-ng/dracut/issues/2780
In short, active/needed modules are not being installed.

I cloned https://github.com/dracut-ng/dracut/com … 2b5cba07b3 (the latest main), and found it correctly built the initramfs (haven't tested the built initramfs yet, but `lsinitrd` showed what was missing before).
Just for shiggles, I downloaded and built v112, and that worked as well.

The issue was related to `dracut-install` "Ignoring" drivers: `$ /usr/lib/dracut/dracut-install --debug -D /tmp/dracut/ -m "=crypto"`

This was never about reporting the bug, which I DID by the way if you actually read the linked github issue.
***Again, this is to push getting the dracut packaged updated to v112 because v111 is broken.***

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,507

Re: Dracut v111 Broken And Flagged Out Of Date

For clarity here's a link to the previous thread : https://bbs.archlinux.org/viewtopic.php?id=315197

You reported the bug to upstream, but not on the archlinux gitlab .
Very few arch devs follow the forum, please file a bug on https://gitlab.archlinux.org/archlinux/ … work_items .

In case you don't have a arch gitlab account, try emailing the maintainer directly.

Moderator Note
for now this thread can stay open and in this board.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

vindicator

Member

Registered: 2016-02-25

Posts: 39

Re: Dracut v111 Broken And Flagged Out Of Date

Lone_Wolf, you, and I see WorMzy were both correct about `gitlab`. 
My eye/brain may have just assumed the dracut-ng repo was being referred to. 
I see there was another (different) issue posted in the gitlab, and that wasn't enough to sway them, so I'm not sure my post will either. 
Hopefully they'll see it is a legit issue and push it out.