Bug 462132 – sys-apps/systemd-198 use wrong path to udevadm in some units

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Egor Y. Egorov 2013-03-18 02:47:20 UTC]

sys-fs/udev install udevadm into /bin, but in some units of sys-apps/systemd-198 used /usr/bin/systemd

Reproducible: Always

[Comment 1 Egor Y. Egorov 2013-03-18 02:48:16 UTC]

Created attachment 342450 [details, diff]
198-0004-udevadm_is_not_in_usr.patch

[Comment 2 Egor Y. Egorov 2013-03-18 02:49:03 UTC]

(In reply to comment #0)
> sys-fs/udev install udevadm into /bin, but in some units of
> sys-apps/systemd-198 used /usr/bin/systemd
> 
> Reproducible: Always

*used /usr/bin/udevadm

[Comment 3 Michał Górny 2013-03-20 19:14:53 UTC]

Could we move 'initrd-udevadm-cleanup-db.service' to udev? That should solve this one.

[Comment 4 William Hubbs 2013-03-20 21:38:44 UTC]

@mgorny:
Sure, we can look into doing that.

I would also though like to volunteer my time to look into fixing the
systemd installation as upstream recommends it should be installed.

I'm willing to do the work myself, but I would want you and floppym to
look over the changes and make sure that we don't break anything.

What do you think?

William

[Comment 5 Michał Górny 2013-03-20 21:48:37 UTC]

(In reply to comment #4)
> @mgorny:
> Sure, we can look into doing that.

Thanks.

> I would also though like to volunteer my time to look into fixing the
> systemd installation as upstream recommends it should be installed.
> 
> I'm willing to do the work myself, but I would want you and floppym to
> look over the changes and make sure that we don't break anything.
> 
> What do you think?

No.

[Comment 6 William Hubbs 2013-03-23 01:07:26 UTC]

Udev-198-r4 takes ownership of this unit, so now you will need to bump
systemd.

Thanks,

William

[Comment 7 Egor Y. Egorov 2013-03-23 03:52:05 UTC]

Ok. But wat about systemd-udev-settle.service and systemd-udev-trigger.service ?

[Comment 8 Egor Y. Egorov 2013-03-23 03:52:39 UTC]

*what

[Comment 9 Samuli Suominen (RETIRED) 2013-03-23 07:17:04 UTC]

(In reply to comment #7)
> Ok. But wat about systemd-udev-settle.service and
> systemd-udev-trigger.service ?

Looks like everything is now in order with udev-198-r5 and 9999:

$ qlist udev |grep "\.service"
/usr/lib/systemd/system/systemd-udev-settle.service
/usr/lib/systemd/system/systemd-udev-trigger.service
/usr/lib/systemd/system/systemd-udevd.service
/usr/lib/systemd/system/initrd-udevadm-cleanup-db.service

$ grep Exec.*udev /usr/lib/systemd/system/*udev*
/usr/lib/systemd/system/initrd-udevadm-cleanup-db.service:ExecStart=-/bin/udevadm info --cleanup-db
/usr/lib/systemd/system/systemd-udevd.service:ExecStart=/usr/lib/systemd/systemd-udevd
/usr/lib/systemd/system/systemd-udev-settle.service:ExecStart=/bin/udevadm settle
/usr/lib/systemd/system/systemd-udev-trigger.service:ExecStart=/bin/udevadm trigger --type=subsystems --action=add ; /bin/udevadm trigger --type=devices --action=add

[Comment 10 Michał Górny 2013-03-23 07:47:54 UTC]

Updated systemd committed as well.