On Fri, Jun 18, 2021 at 09:02:08AM -0500, Michael Catanzaro wrote:
> On Fri, Jun 18 2021 at 08:02:05 AM +1000, Peter Hutterer
> wrote:
> > Right now pipewire gets around this by hardcoding pipewire-media-session
> > and
> > starting it directly (instead of the systemd service) but that makes it
>
On Sun, Jun 20, 2021 at 10:17 AM Michael Catanzaro wrote:
>
> On Fri, Jun 18 2021 at 08:02:05 AM +1000, Peter Hutterer
> wrote:
> > Right now pipewire gets around this by hardcoding
> > pipewire-media-session and
> > starting it directly (instead of the systemd service) but that makes
> > it hard
On Fri, Jun 18 2021 at 08:02:05 AM +1000, Peter Hutterer
wrote:
Right now pipewire gets around this by hardcoding
pipewire-media-session and
starting it directly (instead of the systemd service) but that makes
it hard
to replace.
Anyway, sounds like I'd need to get the FESCo approval for both
On Thu, Jun 17, 2021 at 07:48:24AM -0500, Michael Catanzaro wrote:
> On Thu, Jun 17 2021 at 11:52:44 AM +1000, Peter Hutterer
> wrote:
> > What I need is manager.service being auto-enabled at install time. How
> > do I
> > get this done?
>
> Hi, you're missing a systemd preset. You generally need
On Thu, Jun 17 2021 at 11:52:44 AM +1000, Peter Hutterer
wrote:
What I need is manager.service being auto-enabled at install time.
How do I
get this done?
Hi, you're missing a systemd preset. You generally need FESCo approval
to add a preset. See:
* https://src.fedoraproject.org/rpms/fedor
I'm running around in circles here not getting anywhere, so maybe someone
on this list has the answer :)
I have three packages [1], lets call them
- server
- manager (Conflicts: alternative-manager)
- alternative-manager (Conflicts: manager)
The server on its own is relatively dumb, it needs a ma
