Bug 487800 – sys-kernel/genkernel-next-29 uses hardcoded /sbin/plymouth

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Pacho Ramos 2013-10-12 18:28:33 UTC]

This will break with sys-boot/plymouth-0.8.8-r2 that installs things in /usr/bin instead:
*   >> Installing plymouth [ using the spinner theme and plugin: "two-step" ]...
* ERROR: Binary /sbin/plymouthd could not be found

[Comment 1 Fabio Erculiani (RETIRED) 2013-10-12 20:06:12 UTC]

+*genkernel-next-30 (12 Oct 2013)
+
+  12 Oct 2013; Fabio Erculiani <[e-mail]> -genkernel-next-29.ebuild,
+  +genkernel-next-30.ebuild:
+  version bump to v30, fix bug #487800
+

[Comment 2 Michael Lange 2013-10-13 10:14:42 UTC]

sys-kernel/genkernel-next-30 uses wrong path

*   >> Installing plymouth [ using the spinner theme and plugin: "two-step" ]...
* ERROR: Binary /usr/bin/plymouthd could not be found

=> should be /usr/sbin/plymouthd

[Comment 3 Pacho Ramos 2013-10-13 10:35:43 UTC]

Bleh, I made a typo in bug report

[Comment 4 Fabio Erculiani (RETIRED) 2013-10-13 10:41:56 UTC]

Isn't this ok?
https://github.com/Sabayon/genkernel-next/commit/9aec1ae65e9efdc1531575927715328bc566195e

[Comment 5 Pacho Ramos 2013-10-13 10:45:57 UTC]

you need to change bin -> sbin there 

Why don't you use something like "type -P ..."?

[Comment 6 Fabio Erculiani (RETIRED) 2013-10-13 10:48:11 UTC]

I don't like using type -P.
Why don't you guys stop moving things around without providing symlinks for backward compatibility instead? Just saying...

[Comment 7 Fabio Erculiani (RETIRED) 2013-10-13 10:56:43 UTC]

+*genkernel-next-31 (13 Oct 2013)
+
+  13 Oct 2013; Fabio Erculiani <[e-mail]> -genkernel-next-30.ebuild,
+  +genkernel-next-31.ebuild:
+  version bump, fix bug #487800

[Comment 8 Fabio Erculiani (RETIRED) 2013-10-13 10:59:01 UTC]

But anyway, this is ridiculous, add compatibility symlinks to plymouth and keep them around for a bunch of months at least! Don't move things around like this, _please_!

[Comment 9 Michael Lange 2013-10-13 11:10:34 UTC]

sorry, i have just seen it ... plymouth from plymouth-0.8.8-r2 is now placed in /usr/bin/plymouth (before /bin/plymouth)
i have now errors when system boots "/bin/plymouth could not found"

[Comment 10 Pacho Ramos 2013-10-13 12:04:26 UTC]

How did you got comment#2 error? :O

There are different things:
# equery files plymouth|grep bin/plymo
/usr/bin/plymouth
/usr/sbin/plymouth-set-default-theme
/usr/sbin/plymouthd

The *d is in sbin, the other in /usr/bin

[Comment 11 Pacho Ramos 2013-10-13 12:05:35 UTC]

I guess last change moved all to bin instead of only plymouthD

[Comment 12 Michael Lange 2013-10-13 12:17:59 UTC]

(In reply to Pacho Ramos from comment #10)
> How did you got comment#2 error? :O
> 

plymouth-0.8.8-r2 + genkernel-next-30 (include this changes https://github.com/Sabayon/genkernel-next/commit/9aec1ae65e9efdc1531575927715328bc566195e)
your bugreport was right
new locations for plymouth and plymouthd are now fixed in genkernel-next-git

thx fabio

[Comment 13 Fabio Erculiani (RETIRED) 2013-10-14 15:25:10 UTC]

This is hopefully completely fixed in v34