So, having read the news on my stable system this morning, I'm thinking I should probably migrate to the new gui-libs/display-manager-init sooner rather than later. However, following the instructions in the news item I get:
Code: Select all
# emerge -vuDU gui-libs/display-manager-init
These are the packages that would be merged, in order:
Calculating dependencies... done!
!!! All ebuilds that could satisfy "gui-libs/display-manager-init" have been masked.
!!! One of the following masked packages is required to complete your request:
- gui-libs/display-manager-init-1.0::gentoo (masked by: ~amd64 keyword)
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
Sure, I could simply unmask it, but on my stable system I learned a long time ago to go read Bugzilla before I do something like that to a fairly important service. Having done so, now I'm not convinced this is an actionable item for stable users at the present time. Depending on system configuration I may or may not end up back in my display manager (sddm) after reboot. Yes, I could fix that as well, but now I'm wondering why I should pay any attention to this news item. For one, it currently seems to apply only to the users who are running unstable (OK unmasked) systems by default. Secondly, as my profile is default/linux/amd64/17.1/desktop/plasma (stable), I'm wondering why this isn't simply part of a profile upgrade. Why do I need to add gui-libs/display-manager-init to my world file? Seems to me the news item is missing some useful information. How should stable users proceed here?
