Jan Wielkiewicz writes:
> I made a patch already.
> https://lists.gnu.org/archive/html/guix-patches/2020-07/msg00283.html
> It seems opendht is just buggy there, as using one of its features
> causes compilation error, so I think it is okay to patch the bug.
> What's the point of keeping
Hello,
Dnia 2020-07-11, o godz. 14:49:58
Pierre Neidhardt napisał(a):
> In this case the common procedure is to add a (non-public)
> opendht-jami package at the right commit.
>
> This package can then safely be deleted when the next version of
> opendht comes out.
>
> Cheers!
>
I made a
Hello,
Jami devs helped me - it turns out opendht 2.1.4 contains a bug, which
was fixed on master. I can either wait for the next version where it
works or add the commit fixing the bug as a patch. Opendht in Jami was
bumped though, I can't downgrade in my wip.
What do you think?
Jan
Hello,
Seems opendht is fine, but Jami just fails during compilation.
Reported the issue here:
https://git.jami.net/savoirfairelinux/ring-daemon/issues/261
It seems they build their package with meson now, but libring requires
meson 0.54 or higher. Tried upgrading it quickly and dirty but glib or
Jan Wielkiewicz writes:
> I need someone to push this commit:
> https://lists.gnu.org/archive/html/guix-patches/2020-07/msg00226.html
>
> From this version, my toaster can't build opendht anymore and I'm stuck
> on Fedora on my newer now, where I have no Guix available.
> Can someone check if
Hello,
I need someone to push this commit:
https://lists.gnu.org/archive/html/guix-patches/2020-07/msg00226.html
From this version, my toaster can't build opendht anymore and I'm stuck
on Fedora on my newer now, where I have no Guix available.
Can someone check if it compiles and push, so I can
