Dependency Requirement: libsoup (also, Gnome & multimedia keys?)

[carakesa]

Building from source or installing from the Arch AUR will appear successful but fail with

╰─❯ slimpris2
Traceback (most recent call last):
  File "/usr/sbin/slimpris2", line 50, in <module>
    gi.require_version('Soup', '2.4')
  File "/usr/lib/python3.12/site-packages/gi/__init__.py", line 125, in require_version
    raise ValueError('Namespace %s not available for version %s' %
ValueError: Namespace Soup not available for version 2.4

Simply installing libsoup allows it to run and I can interact via Playerctl

Just for info in case someone else needs it:

Since I'm not using Gnome, I do get this message as well:

2024-09-08 18:38:57,561 slimpris2 ERROR: Failed to connect to GNOME Settings Daemon. Disabling multimedia key support

[mavit]

This is best handled in the AUR packaging.

@snakeroot: Do you want to take a look?

[carakesa]

To add: it appears to be a dependency across the board, so even building from source (and/or from the AUR) it will compile but can't run without libsoup

…

On Tue, Sep 10, 2024, 9:19 AM Peter Oliver ***@***.***> wrote: This is best handled in the AUR packaging. @snakeroot <https://github.com/snakeroot>: Do you want to take a look? — Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM3K3S7VYTKA6X4FYW7Y63DZV3WWZAVCNFSM6AAAAABN3L7SZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBQG42TKMZSGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mavit]

To add: it appears to be a dependency across the board, so even building from source (and/or from the AUR) it will compile but can't run without libsoup

Indeed. Soup is only required at run-time, not build time, which is why it isn't checked for at build time. When building a package, the build machine and the install machine aren't the same, so won't have the same things installed.

[snakeroot]

This is best handled in the AUR packaging.

@snakeroot: Do you want to take a look?

It seems I could either add it as a dependency or as a local dependency in the package( ) function. While the former may not be technically correct, it is straightforward and I doubt there are many people building the package on (libsoupless) machine A for installation on machine B.

https://gitlab.archlinux.org/pacman/pacman/-/issues/22

Let me know your thoughts, and I'll take care of it at the weekend.

[mavit]

@snakeroot: I don't know anything about Arch packages, but had naïvely assumed you could simply add libsoup to the depends= section that already contains the other runtime dependencies. I'll leave it to your judgment.

Thanks for packaging this, by the way!