sys-boot/plymouth masked for removal

[spijet]

Hello! First of all, thank you for your awesome overlay and brilliant EFI-install guide! It made me to try Gentoo yet again and explained a lot of stuff that I did wrong last time. ^_^

Now to the sad part: Today I was upgrading my system, when Portage gave me this message:

/var/portage/repos/gentoo/profiles/package.mask:
# Michał Górny <[email protected]> (04 Aug 2017)
# sys-boot/plymouth is unmaintained since Apr 2016. The current version
# has multiple bugs, including not supporting OpenRC. It really needs
# an active maintainer. Removal in 30 days. Bug #621470.
#
# The remaining packages are sys-boot/plymouth reverse dependencies.
# They have no use without it, so they are being removed as well.

- sys-boot/plymouth-0.9.2-r1::gentoo (masked by: package.mask)
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

Since buildkernel (and your EFI installation guide) uses Plymouth to provide a bootsplash, I thought that I had to open this issue ticket. I, myself, can just 'rip' current Plymouth ebuilds to my own overlay and continue to use it as usual, but this way I can't be sure that buildkernel (and other stuff) will still use it. :(

As far as I understand, Michal's point is that Plymouth didn't have a tagged release since April 2016. That's true, but git version is still (more or less) active, with latest commit happened in May. Maybe we should switch over to -9999?

[sakaki-]

Hi, thanks for your kind comments ^-^ and the heads up on plymouth - have been buried in arm64 RPi3 stuff and had missed the little "The following installed packages are masked..." line in my overnight genup run.

OK, for now I have cloned sys-boot/plymouth into sakaki-tools, and I'll modify the guide (and maybe put out a news item on the overlay) directing users to add a package.unmask. Not sure what will happen with genkernel-next though - presumably they'll have to drop the dep, which is sad since their plymouth support is pretty good...

[sakaki-]

Actually, belay that, I've just added the package.unmask entry to sakaki-tools directly. Should fix immediate breakage, but need to keep an eye on this over the next month.

Thanks for reporting! Closing this now but feel free to re-open if something breaks for you now or in the near future (due to genkernel-next etc)

[spijet]

Thanks for quick answer!

Just saw that you've cloned it (I did too :D), but Portage also gives me this:

WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:

sys-kernel/genkernel-next:0

  (sys-kernel/genkernel-next-65:0/0::gentoo, ebuild scheduled for merge) conflicts with
    >=sys-kernel/genkernel-next-58[cryptsetup,gpg,*plymouth*] required by (sys-kernel/buildkernel-1.0.25:0/0::sakaki-tools, installed)

That happened because Gentoo maintainers have also masked the plymouth flag:

# Michał Górny <[email protected]> (04 Aug 2017)
# sys-boot/plymouth is being treecleaned wrt #621470.
gnome-base/gdm plymouth
kde-plasma/plasma-meta plymouth
sys-kernel/genkernel-next plymouth

So you'll probably also need to unmask the USE flag.

[sakaki-]

OK I have just reverted the commits taking plymouth into the overlay, and have pushed a news item about this instead (the USE flag override can't be done directly in the overlay, there's no package.use.unmask, and a -plymouth in package.use.mask or use.mask gets trumped by the profile masks unfortunately, so the user has to do it). Will decide on a course of action and implement it before month end. In the meantime, please consider adding a stay-of-execution comment to bug 621470. Reopening for now. Will also update the guide on the wiki with a short-term workaround.

[cmosh]

Hello I'm not sure if it's related to this but I'm new to gentoo and decided to follow your awesome guide but I cannot emerge sys-kernel/buildkernel due to this error:
emerge: there are no ebuilds to satisfy ">=sys-kernel/genkernel-next-58[cryptsetup,gpg,plymouth?]"
Is this still part of the plymouth issue? I have done as the news item suggests and I'm still facing this issue

[sakaki-]

Hi, sorry to hear you are having problems with this.

If you run (as root) eix-sync -0 (hyphen zero) followed by eix genkernel-next, what output do you see? The problem you mention suggests that the plymouth USE flag is still masked for genkernel-next on your system, which the package.use.mask edit mentioned in the news item should have addressed.

[sakaki-]

Actually there is a problem with the news item instructions I think - package.use.mask cannot exist at the top level of /etc/portage, it has to go into /etc/portage/profile instead; so do (as root):

# mkdir -pv /etc/portage/profile
# mv /etc/portage/package.use.mask /etc/portage/profile/

Once you have done that you should be able to emerge buildkernel OK; please let me know if it fixes your issue, and I'll put out an erratum (problem is I use developer profiles on my own machines which makes it difficult to test this sort of stuff easily, I'll set up a baseline install VM to test against right now, so it doesn't happen again).

Thanks for reporting!

[Antony500]

Had the same issue, i can now emerge buildkernel. Thanks!

[sakaki-]

Thanks @Antony500; erratum news item pushed.

[cmosh]

Hello again, I've only just been able to continue my install and it now does work for me too. Thanks Sakaki your guide has been a great help

[ghost]

Hi everyone ! First of all, thanks a bunch for the guide and overlay sakaki you really managed to make things work and be convenient ! I'm posting this cause I have found a working solution concerning OpenRC and Plymouth which works for me (using plymouth-0.9.3-r1 and plymouth-openrc-plugin-0.1.2 ,although the plugin seems unrelated as it still worked when Plymouth didn't).
It seems adding a udev rule solved everything for me as discussed [here] (https://forums.gentoo.org/viewtopic-t-1061774-start-0.html) before re-running genkernel through buildkernel.
I hope this will help others in using Plymouth with OpenRC and again thanks for the guide

[sakaki-]

Thanks @naganori-san! As it happens, I am doing a refresh on the guide now (basis a fresh install on a Dell 5567 laptop) and am nearly complete with the systemd track; when I loop back through for the OpenRC pages, I'll check out your suggestion, and if it works merge it in.

[necrose99]

sabayon sabayon-distro live cd depends on plymouth... if that helps be forewarned you can get the sabayon themes if that's not what you want..

[necrose99]

think the plymouth been fixed/bumped , along with zulucypt ..

[sakaki-]

31 Oct 2020: sadly, due to legal obligations arising from a recent change in my 'real world' job, I must announce I am standing down as maintainer of this project with immediate effect. For the meantime, I will leave the repo up (for historical interest, and since the ebuilds etc. may be of use to others); however, I plan no further updates, nor will I be accepting / actioning further pull requests or bug reports from this point. Email requests for support will also have to be politely declined, so, please treat this as an effective EOL notice.

For further details, please see my post here.

If you have used my EFI Guide (and this repo) to install your PC-based Gentoo system, it should still continue to work for some time, but you should now take steps to migrate to a baseline Gentoo Handbook install (since the underlying tools, such as buildkernel, will also now no longer be supported and may eventually fail as more modern kernels etc. are released).

With sincere apologies, sakaki ><