On Sun, Jan 02, 2022 at 07:12:31AM +0500, Gleb Gorshkov wrote:
> Snippet from documentation
> https://guix.gnu.org/manual/en/html_node/X-Window.html#slim-service-type
> produce an error
> guix system: error: service 'xorg-server' provided more than once
Hm, it's similar to
On Sun, Jan 02, 2022 at 10:11:01AM -0900, Christopher Howard wrote:
> Package "freedroidrpg" fails to build:
[...]
> ld: addon_crafting_ui.o:(.bss+0x0): multiple definition of `tux_rendering';
> action.o:(.bss+0x0): first defined here
I think we need to build the package with -fcommon. This is a
Snippet from documentation
https://guix.gnu.org/manual/en/html_node/X-Window.html#slim-service-type
produce an error
guix system: error: service 'xorg-server' provided more than once
-- Gleb Gorshkov
Package "freedroidrpg" fails to build:
```
gcc -I/gnu/store/l4k60q5jm9g2f3jslnhjsldls0l4vf9q-sdl-1.2.15/include/SDL
-D_GNU_SOURCE=1 -D_REENTRANT -pipe -Wall -Wno-format-zero-length -ffast-math
-I/gnu/store/2qfzwl2k819cdp57xwikhp0i3sl27hma-sdl-gfx-2.0.26/include/SDL
Hey Maxime,
The let form was mostly included because, if possible, we should pull
the value of `beets-python-version` from the version of python used for
beets (because this implementation currently relies on a hardcoded and
versioned library path in `lib/python3.9/site-packages`, it will
Liliana Marie Prikler skribis:
> @Guillaume: From what I can gather from the build error, it appears as
> though the calling convention changed to require an additional
> parameter. I've tracked down the relevant commit [1] and bug [2].
>
> Now obviously doing such a thing violates SemVer, so
Hi Guix,
today I got the attached traceback while trying to reconfigure Guix.
It turns out that 145:12 tries to check which services are currently
running and ignores that (eval exp) might return #f.
I'm not sure which point would be the correct one to guard against this
case, but a naïve
Hello again,
> Good morning Josselin, and Happy New Year!
>
> Many thanks for taking the time to explain this in detail for us. If I
> have properly understood your explanation, it suggests I am running
> network-manager from outside of the dbus session. If I look at the
> processes running on
