Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 892826

Summary: >=media-video/pipewire-3.53_p20220704-r1: media-plugins/alsa-plugins[pulseaudio] will be uninstalled when migrating from pulseaudio
Product: Gentoo Linux Reporter: Pacho Ramos <pacho>
Component: Current packagesAssignee: Sam James <sam>
Status: CONFIRMED ---    
Severity: normal CC: arnaudv6, leio, silvio.gerli
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
See Also: https://bugs.gentoo.org/show_bug.cgi?id=327701
Whiteboard:
Package list:
Runtime testing required: ---

Description Pacho Ramos gentoo-dev 2023-02-01 13:49:39 UTC
After this change:
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=003c47c5b969885b16b7a34ad182c8419c3e4656

When migrating from pulseaudio following the instructions from the news item:
https://www.gentoo.org/support/news-items/2022-07-29-pipewire-sound-server.html

People will end-up without any alsa-plugins by default just after doing the depclean as suggested by the news item. This is because, at the time of the migration, media-plugins/alsa-plugins[pulseaudio] will be present at the time the elog message should be shown as it's still there pulled in by the pulseaudio. As a consequence, optfeature.eclass won't show the warning.

I noticed it just now when migrating one of my machines, as I was surprised of seen alsa-plugins in the (long) list of packages I needed to clean. I am not sure what option would be better:
- Enabling pipewire-alsa by default -> It looks the simplest and more future-proof, but it seems to not be enabled due to some runtime checks it should do (as I read from comments in the ebuild)
- Update the news item to remind people that they should ensure alsa-plugins[pulseaudio] is still there after depcleaning when pipewire-alsa is not enabled.

Thanks
Comment 1 Arnaud Vallette d'Osia 2023-05-17 08:14:05 UTC
Confirmed, it bited me.
Comment 2 Pacho Ramos gentoo-dev 2023-05-18 08:46:38 UTC
Other option could be to have something as FORCE_PRINT_ELOG from readme.gentoo.eclass in optfeature.eclass to, later, force the printing when updating (and needed) via has_version checks