<cbaines>I'm pretty sure that your user profile should survive doing guix system reconfigure, but I'm not sure why it doesn't, perhaps when it's empty again, try and do some debugging or ask in IRC
<cbaines>with the new guix, you might get a better error message, so you might want to try with bash still in your profile
<happy_gnu[m]>Yeah I installed searx on parabola, and then I said, I should look for it on guix, and it wasn't so I started installing a virtual machine
<ng0>I have an idea how it could look like, it's not a functional package because of socks['#:blafoo'] or something.. the idea is to have a service afterwards, so that one can run searx locally, not necessarily on a headless server
<happy_gnu[m]>I am learning scheme and dustyweb suggested me to package things for guix
<ng0>I'm not really sure wether I can link my git here or not as one repository contains non-free instructions for guix.. but the indirect way, if you have much time on your hands and are impatient, go to https://www.krosos.org and you'll find a link to my git. I have to leave soon
<efraim>i had to fix my build script, `./pre-inst-env guix package -A | cut -f1,2 | sed -e 's/\\t/@/' | shuf | parallel --jobs 1 ./pre-guix-env guix build`, changed cut from 'cut -f1', took out 'sort -u' for sed
<jherrlin>cbaines thanks for the tips, will look at geiser!
<pmikkelsen>What do we usually do when packages become deprecated upstream? If I remove them, I will have to remove some other packages that depend on them too, but if I don't, then we will have to have and old version of a library around?
<civodul>pmikkelsen: i would raise the issue on guix-devel
<civodul>we rarely remove packages, but we've done so a couple of times in the past i think
<pmikkelsen>civodul: allright, I will figure out how many 'old' libraries we will have to keep around, and if it is just a single or two, then I think it is ok to keep it
<ng0>would anyone know if it's by design or by grave mistake that you can get anything into https://mate-desktop.org/ without even merging the Pull Request?
<ng0>read the website, section Linux-Systems or something
<Apteryx>dustyweb: not surprised a bit by it. PyPI doesn't exerce any filtering or control on the packages it hosts. It contains lots of fake packages that were uploaded once just to see how it'd goes.
<Apteryx>In Guix we have systems tests. Do we also have unit tests?
<happy_gnu[m]>You would normally leave this field to #f, initialize user passwords as rootwith the passwd command, and then let users change it with passwd. Passwords set with passwd are of course preserved across reboot and reconfiguration.
<nextos>civodul: thanks. One last question, I should guix pull often to be able to get binaries right? If my package definitions are old, i won't be able to pull matching binaries from hydra?
***Piece_Maker is now known as Acou_Bass
<civodul>nextos: the main reason to run "guix pull" frequently is to get security updates
<civodul>so once per week you'd run "guix pull && guix package -u"
<nextos>civodul: but was my reasoning right? I mean if i dont guix pull after my initial guix install, hydra wont contain matching binaries? It's just for me to understand how guix works. I know I should update often.
<civodul>nextos: mirror.hydra.gnu.org keeps binaries for a couple of months at least
<civodul>so normally you won't have this kind of problem
<Apteryx>it's a bug that the docs don't get updated when we do 'guix pull'; so for now you don't have much choice but to git clone guix somewhere and build it. the docs will appear under guix/doc. You can then info -f guix/doc/guix.info or C-u h i in emacs
<Apteryx>alternatively add something like: INFOPATH=/home/$USER/src/guix/doc to your ~/.bash_profile
<Apteryx>I remember someone having an issue because their label name started by "guix" or something. This was supposedly fixed but just to stay on the safe side you might want to rename your label to something else.
<buenouanq>wow, that's a silly/awful bug that would seem to indicate potentially much worse problems if true
<bavier`>CompanionCube: is your profile directory included in PERL5LIB?
<CompanionCube>I haven't explicitly added it, but it doesn't look like Guix sets it automagically in the profile's etc/profile
<cbaines>You might need to also install perl in your profile for the search path to be setup
<CompanionCube>(the reason i'm using guix for this is most likely something you've heard a million times)
<marusich>CompanionCube, it would be better if the ikiwiki package "just worked" without requiring you to install a perl module into your profile. Ideally, software deployed via Guix (or Nix) should not require "extra steps" like installing a second package; although it is a common practice with other package managers, it runs against the spirit of functional package managers like Guix and Nix.
<marusich>Because the software will not work if you do not also install the extra thing you need, the deployment of the software is "incomplete". That is one of the problems that Guix and Nix specifically aim to solve.
<marusich>Unless there's a good reason to do otherwise, either the module should be a propagated input of the pacakge (not so great because it introduces the possibility of conflicts with other packages installed in your profile), or (better) the package definition should be changed so that the software which is failing to find the module will find it. Foe example, if a script or program is being run which expected the module to be available, one solution
<marusich>might be to wrap it in a launcher script that correctly sets up the PERL5LIB environment variable so that perl will find the module.
<marusich>There are helper procedures to accomplish that; look for existing package definitions which use "wrap-program" if you are curious.
<cbaines>the ikiwiki package is already setup to wrap the scripts with the PERL5LIB to include the inputs, if there is indeed a missing input, just adding it to the list of inputs should be sufficient
<bavier`>is that letter only for EU citizens? why are there non-EU countries listed in the dropdown menu?
<civodul>it's possible for non-EU citizens to sign, but i guess FSFE will not go lobby at parlamients outside of EU :-)
<civodul>it's great to show support from everywhere anyway!
<joshuaBPMan>hello, does guix provide an easy way to specify an alternate keyboard layout at the login manager? ie: dvorak? Perferably this would be an easy way to make X provide the same layout as well.
<sneek>Welcome back joshuaBPMan, you have 1 message.
<sneek>joshuaBPMan, efraim says: there's a meson-build-system work in progress so we should be ready soon for the GNOME switch