[gentoo-user] Re: x11-base/xorg-x11 masked

2022-10-03 Thread Holger Hoffstätte

On 2022-10-04 08:40, w...@op.pl wrote:

Hello everyone!
Upon upgrade, portage told me that x11-base/xorg-x11 is masked and will
be removed from the repo on November 1st. I thought "ok, why not do it
now", so I have typed:
# emerge -W x11-base/xorg-x11
# emerge -cav
and there was a surprise (not a pleasant one). Since xorg-x11 is a
metapackage it pulled so many things I would like to have still here.
Is there any reasonable way to put all those packages to my world file,
so I can easily remove xorg-x11 without deleting half of my desktop
apps?


Please see discussions in:

https://bugs.gentoo.org/872119
https://bugs.gentoo.org/873973

cheers,
Holger



[gentoo-user] x11-base/xorg-x11 masked

2022-10-03 Thread w...@op.pl
Hello everyone!
Upon upgrade, portage told me that x11-base/xorg-x11 is masked and will
be removed from the repo on November 1st. I thought "ok, why not do it
now", so I have typed:
# emerge -W x11-base/xorg-x11
# emerge -cav
and there was a surprise (not a pleasant one). Since xorg-x11 is a
metapackage it pulled so many things I would like to have still here.
Is there any reasonable way to put all those packages to my world file,
so I can easily remove xorg-x11 without deleting half of my desktop
apps?

Thanks in advance, have a good day!

-- 
xWK


pgpfqN1k_yGiD.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Re: [SOLVED] Pipewire not a dependency?

2022-10-03 Thread Michael
On Monday, 3 October 2022 22:48:09 BST Håkon Alstadheim wrote:
> Den 02.10.2022 11:47, skrev Michael:
> > On Saturday, 1 October 2022 19:32:11 BST Daniel Sonck wrote:
> >> On zaterdag 1 oktober 2022 19:11:19 CEST Wol wrote:
> >>> On 01/10/2022 17:56, Michael wrote:
>  Anyway, I ventured into pipewire because I wanted to see if Skype would
>  work without pulseaudio and in this system it won't.  After I manually
>  installed pipewire Skype won't access the microphone.  🙁
> >>> 
> >>> I've got some vague feeling that pipewire is designed to happily sit
> >>> under pulseaudio. The design aim was to replace both Jack and pulseaudio
> >>> but it basically just presents a sound device to the layers above, so
> >>> just like you can stack block devices for disk access, you can stack
> >>> jack, pulseaudio and pipewire for sound.
> >> 
> >> Well, it is actually designed as a drop-in replacement and won't present
> >> audio devices in the sense pulseaudio wants to receive it. I guess it
> >> would
> >> theoretically be possible to use pulseaudio's jack sink to talk to
> >> pipewire, but pipewire has the full pulseaudio interface for pulseaudio
> >> applications.
> > 
> > At the moment only some applications support PipeWire's native API, but
> > most support PulseAudio's API.  When you come across an application like
> > Skype which expects PulseAudio, the solution is to enable
> > USE="sound-server pipewire-alsa" for PipeWire and in addition to PipeWire
> > also install media- libs/libpulse.  No other PulseAudio packages are
> > needed.
> 
> To get that, I seem to need media-sound/pulseaudio (meta package) with 
> USE="-daemon"

This USE flag setting would be required if you use pulseaudio (I don't have it 
installed) and need to avoid it fighting with pipewire over control
of audio devices.

At the present moment, because the migration to pipewire is work-in-progress, 
there are a number of options available to cover all use cases, depending on 
your system configuration and init system:

https://www.gentoo.org/support/news-items/2022-07-29-pipewire-sound-server.html



signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Re: [SOLVED] Pipewire not a dependency?

2022-10-03 Thread Håkon Alstadheim



Den 02.10.2022 11:47, skrev Michael:

On Saturday, 1 October 2022 19:32:11 BST Daniel Sonck wrote:

On zaterdag 1 oktober 2022 19:11:19 CEST Wol wrote:

On 01/10/2022 17:56, Michael wrote:

Anyway, I ventured into pipewire because I wanted to see if Skype would
work without pulseaudio and in this system it won't.  After I manually
installed pipewire Skype won't access the microphone.  🙁

I've got some vague feeling that pipewire is designed to happily sit
under pulseaudio. The design aim was to replace both Jack and pulseaudio
but it basically just presents a sound device to the layers above, so
just like you can stack block devices for disk access, you can stack
jack, pulseaudio and pipewire for sound.

Well, it is actually designed as a drop-in replacement and won't present
audio devices in the sense pulseaudio wants to receive it. I guess it would
theoretically be possible to use pulseaudio's jack sink to talk to
pipewire, but pipewire has the full pulseaudio interface for pulseaudio
applications.

At the moment only some applications support PipeWire's native API, but most
support PulseAudio's API.  When you come across an application like Skype
which expects PulseAudio, the solution is to enable USE="sound-server
pipewire-alsa" for PipeWire and in addition to PipeWire also install media-
libs/libpulse.  No other PulseAudio packages are needed.
To get that, I seem to need media-sound/pulseaudio (meta package) with  
USE="-daemon"


Thereafter an application requiring PulseAudio uses PipeWire, the latter
emulating PulseAudio's server by using PulseAudio's API via libpulse.

I applied the above and now the microphone in Skype works again.  I assume the
same applies to other PulseAudio friendly applications, which won't play
nicely with PipeWire only.  I suppose at some point PulseAudio will be
completely replaced by PipeWire and applications will update their code
accordingly.




[gentoo-user] Re: problem with emerge depclean after world update

2022-10-03 Thread Grant Edwards
On 2022-09-30, Wol  wrote:

> Does that mean an update typically cleans a replaced package 
> automagically?

Yes (except for slotted packages). A "normal" upgrade emerge removes
the old version.

> I thought that usually they got left behind and that was 
> why you needed depclean - to remove all the old versions?

Nope (except sometimes for slotted packages).

Depclean is for clearing out stuff that was installed automagically as
a dependancy but now doesn't need to be installed at all because

  1. Whataver pulled it in as dependency got manually removed.

  2. A package's dependencies got changed.

> Certainly that's what I remember of depclean of old - the list of stuff 
> being cleaned was mostly old versions of what was installed.

That happens for slotted packages and for things like kernel sources.

On my systems, the only things that typically get removed by depclean
are old versions of gentoo-sources and the occasional old slot of
binutils (or whatever).

--
Grant