<ngz>Hello. I'm packaging a Python module that tries to locate and load the "libsodium" library in the system, with the following command: ctypes.util.find_library('libsodium'). "libsodium" is a propagated input from the package, yet it is unable to find it. Is there a proper way to fix this? Or should I simply replace the command above with the hard-coded library file name in the store?
<sneek>jlicht, Guest2732 says: I'm trying to get ansible-playbook going at the moment. The only way I can get it to work is:
<jlicht>Guest2732: AFAICS, your workaround seems to make sure that the ansible scripts has access to $0 being set as "ansible-playbook" (or ".ansible-playbook-real") instead of ".ansible-real", thereby fixing the issue. I am not really sure what we can do to actually fix this right now within guix proper.
<zybell>jlicht:you can add at build a symlink "ansible-playbook" to ansible and a possibly a *wrapper script* that is ansible in another dir and calls ansible-playbook. The PATH will decide.
<jlicht>zybell: that is already the case in the sources for ansible, I am not sure if adding it again will help much. What do you mean with the wrapper-script?
<Guest2732>jlicht: thanks for working out what's going on and writing up the bug report!
<Guest2732>jlicht: this might be a silly suggestion, but could there be some way you can call a program and override what it sees as $0? I don't know how to this, but it seems like it should exist. :)
<jlicht>Guest54768: `exec -a <desired-name> <the actual program>' should do this, but it seems this does not work icw with interpreters and the way we wrap scripts. See one of the links in the bug report I opened :-)
<jlicht>so you are 100% correct in your assumption, btw
<Guest2732>jlicht: thanks for the info, I'll have a look
<zybell>jlicht:I meant a script named like the real executable,that calls the executable *through the symlink*(setting $0) with all params preserved,and because being in another dir,can be ordered before the real exec in PATH. Therefore setting $0 indirectly over PATH.
<jlicht>zybell: Our wrapper already does this, or should be, at least
<jlicht>ah wow, that makes a lot of sense. I'm a bit slow with these things, sorry Guest2732 and zybell :-).
<jlicht>btw, Guest2732, what did you use to make that diagram? It looks quite crisp.
<Guest2732>jlicht: just used libreoffice draw - little bit fiddly, but works well enough
***Guest2732 is now known as sturm
<zybell>sturm:I thought more s;/bin/ansible-playbook;/bin/automatic/ansible; because I thought it was the remote that called the wrong program,but if that works, what you did draw, it were the wrapper scripts themselves.(A readlink too many I assume)
<divansantana_>can one configure guixsd with luks for sda1. And then root is in encrypted vol. Boot is on the same /. Would grub work like that? Or does grub and boot need to be on an unencrpted vol?
<divansantana_>civodul: I was thinking that. Its getting interesting. Its a lenovo t560. In the "bios" ive set it on to both(legacy+uefi). Though I've noticed if I set it to just legacy, then it fails to boot the guixsd usb disk.
<divansantana_>civodul: Then after that error, I ran guix pull on install media and reran the guix system init /mnt/etc/config.scm which strangely worked. Or finished without errors. In then boots and sees grub. But fails to decrypt of find crypt drive.
<lfam>I'm working on upgrading GIMP but I'm stuck. For some reason it fails to find the babl headers while building GIMP, whether it uses pkg-config or I set BABL_CFLAGS and BABL_LIBS manually
<buenouanq>I've found the manual can be quite confusing - It makes perfect sense if you already know what it's talking about, but some things are downright cryptic are way too glossed over if you're not there yet.
<buenouanq>That's the sort of thing that really hard to improve because once you figure it out, looking back it doesn't seem unclear anymore so you don't know how to change it.
<buenouanq>We need someone new to take really detailed notes of confusions as they do everything the first time.