npm 'command not found' while node js is installed ?
Hi Guixers, I installed nodejs package. When i go 'npm' in the shell i'm getting a 'command not found' error message. how to get 'npm' working ? what am i missing ? thanks, thanks, thanks Fenix
python-pyarrow is missing dataset module
Hi list I wanted to use python.pyarrow with the module pyarrow.dataset, but a ModuleNotFound error is thrown. Checking the mailing lists [1] I see that an additional build variable need to be set: PYARROW_WITH_DATASET Cheers, Reza [1] https://yhetil.org/guix/CAOvsyQvEZHuDoaTnjWt8xDfOn2=2bd=XaLhKBGViv1JVeg3w=g...@mail.gmail.com/#t -- Reza Housseini This message is signed with my GnuPG key: C0F3 0812 9AF2 80F4 0830 C2C1 C375 C6AF 0512 5C52 OpenPGP_0xC375C6AF05125C52.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: EDOPro can't load libpthread.so.0
Am Dienstag, dem 11.10.2022 um 09:09 +0100 schrieb (: > (1) Make a Guix ``edopro'' package. I recommend you do this. > If you don't know how to make a package, I'll be happy to help > on #guix (I'm ``unmatched-paren'' there). Alternatively, you can try using one that's already packages in a channel (e.g. [1], though note that as of the time of writing this one seems a bit behind). [1] https://github.com/LordYuuma/guix-ygopro/blob/master/ygopro/packages/ignis.scm#L106
Re: Wayland Functionality for Jami
Bumping this, just in case. On Wednesday, October 5, 2022 at 03:52:49 PM CDT, Wamm K. D. wrote: The Jami available in the repo.s, currently, causes an error about the Wayland plugin for QT not being available. While some app.s don't require this to be bundled with the app. – apparently (I run into similar errors for Qutebrowser but installing QTWayland fixes the issue) –, Jami does. Building the package definition in the repo. exactly as is but with QTWayland added as an additional ~input~ causes Jami to be able to be used under Wayland perfectly. So my question is, what would be the best means of updating this package? Should QTWayland just get added to the ~inputs~, even for users who aren't running Wayland? Or would it make sense to just create a second Jami package definition (called =jami-wayland= or something) that ~inherit~s the original Jami package and just adds QTWayland to the ~inputs~? Or a third option?
