<ile>Ok, I think I will just use the simplest way for now (homemade scripts to install software), and wait till I get the GuixSD installed natively. Either it will happen soon, or it won't happen at all, so this is the easiest way for now...
<ile>If it's possible to create a Vagrant box (Virtualbox) for GuixSD, it might help a lot of people for setting it up/learning how to do it. So, it would be nice to see such a box on vagrantcloud.com - a suggestion.
<vtomole>or should it be run on this download://www.gnu.org/software/guix/
<vtomole>lfam: booting from vm was not hard, it's just installing it that's been a pain most recent error has been "can't install GRUB"
<lfam>If you just want to get GuixSD running in QEMU, `guix system vm-image` will generate a new QEMU image with GuixSD in it for you
<lfam>It's probably easier than installing GuixSD in QEMU "by hand", although that does work too
<foobar123>I'm considering guixsd as a nix user, and after going through the manual, i have a few questions. First, the regular channel that guix uses to serve packages is a rolling release or moves with releases only?
<Apteryx>I'm trying to understand where the setuptools v20 is "bundled" or "input" to the python build system, if anyone has a clue.
<lfam>vtomole: I'm not familiar with pacman. Apt / dpkg work by changing the contents of the /usr directory, destroying what was there before. Also, they are binary package managers. Guix and Nix, on the other hand, and build-from-source package managers. And, they put all packages in unique immutable directories and then use symlinks to make a subset of them available to users. These unique directories are named for all their inputs:
<lfam>dependencies, build scripts, etc. This allows the system to transparently substitute pre-built binaries instead of building from source.
<lfam>Apteryx: My understanding is that Setuptools is bundled with Python itself, but I'm not sure
<vtomole>lfam: For the vm, you had to make a config.scm first right? I did this "guix system vm my-config.scm \\ --expose=$HOME --share=$HOME/tmp=/exchange"
<lfam>vtomole: Right, you have supply a configuration file on the command line. I also recommend setting --image-size to some large value. The image file uses a "balloon" so it won't take up that much space until you use it.
<lfam>Oh, perhaps that's only necessary for vm-image.
<lfam>No, it seems that `guix system vm` does take that option. I use 100G
<vtomole>I'm new to linux so sorry for the stupid questions, how do you change permissions? do you use chown?
<lfam>You'll want to use chmod, and just change the permission bits, rather than changing ownership with chown. I've been using `sudo chmod 666 /dev/kvm` but, like I said, no promises that this is a good idea! The permissions are reset after reboot
<Apteryx>lfam: Just saw your answer, thanks. Yes it is bundled with Python. I'm trying to test a newer setuptools (required to run pip's tests). I've extracted pip's sources and tried to use the environment: "guix environment guix python-pip --ad-hoc python-setuptools". However a "pip list" in that environment shows that I'm still using setuptools 20 rather than 31. Am I creating the environment wrong?
<lfam>Apteryx: You probably can remove the 'guix', unless you need Guix's dependencies in the environment. I would also use, at least, --pure, if not --container
<lfam>Beyond that, Hartmut is the expert on guix-devel
<Apteryx>lfam: Right, the guix is only so that I can rebuild the package files I'm editing.
<lfam>If you are making your changes in the package files, then the python-pip and python-setuptools won't have an impact when you rebuild the packages in the package files
<lfam>You have to make all your changes in the package definitions. Sorry if I misunderstand your approach
<lfam>I meant to say that Hartmut is the expert on Pip and Python on guix-devel. He recently revamped the python-build-system
<Apteryx>lfam: I guess my flow is a bit confusing, I kind of doing two things in parallel (adapting the package definition and testing manually (independent of the package definition) in an environment).
<lfam>The last line is a shell script. Just run that script
<lfam>You might also want to protect the script from being garbage collected by symlinking it into /var/guix/gcroots: `ln -s /gnu/store/dl2xk2qnqaai3703hgmas0hbc76q542q-run-vm.sh /var/guix/gcroots/my-vm`
<lfam>Otherwise it will disappear when you run `guix gc` to free up space
<vtomole>lfam: hmm "./gnu/store/dl2xk2qnqaai3703hgmas0hbc76q542q-run-vm.sh bash: ./gnu/store/dl2xk2qnqaai3703hgmas0hbc76q542q-run-vm.sh: No such file or directory"
<lfam>The leading '.' means "the current directory". Try leaving it off, so the command starts with the '/'
<vtomole>"qemu-system-x86_64: -virtfs local,path=/home/vtomole/tmp,security_model=none,mount_tag=TAG_home_vtomole_tmp: 9pfs Failed to initialize fs-driver with id:TAG_home_vtomole_tmp and export path:/home/vtomole/tmp"
<lfam>Hm... I've actually never tried those --expose and --share options in this context
<lfam>vtomole: If you want to set a user password, you should really follow the instructions in the section Running GuixSD in a VM. The method you used created an immutable (unchangeable) VM image. Maybe that's what you want, I'm not sure
<lfam>I usually make changes in the package definition of the failing package itself, because that way I don't have to worry about isolating the test builds from the rest of my system, but others do it with `guix environment`
<lfam>I wonder if they turned deprecation warnings into fatal errors
<vtomole>lfam, you said you've gotten this error too, have you ever fixed it? I mean you just don't use guixsd on vm without being connected to the internet, do you?
<lfam>vtomole: I mean, in general, I've seen dhclient fail. It usually means that the network interface was not actually activated, or there is some problem with the dhcp server I'm querying
<lfam>vtomole: Did you start the VM with '-net user' like the manual suggests?
<lfam>I bet the problem has to do with the ffmpeg update that happened between the last good build and new failures
<lfam>We still have the old ffmpeg-2.8 package in our tree
<Apteryx>Where is all the information for a package DAG kept? In a database?
<Apteryx>Just looking at the graph of Python; it's really interesting to be able to visualize the dependencies so easily :)
<enoeht>Hi, I've downloaded the source to a guix package that was broken, now I want to test to see if it works, I'm thinking I just run guix environment kodi --pure -- make install... is this correct
<enoeht>or is there a link to where I can read how to make changes to existing packages?
<Apteryx>enoeht: Not really yet... I like to be working directly in guix from git with "guix environment guix --ad-hoc your_package", then I can edit the package definition in-place. In emacs I then run "C-c C-z" to fire Geiser, then 'M-x guix RET e "your_package"'
<Apteryx>the emacs guix command will bring you to your package definition.
<Apteryx>From there there is a Guix mode in emacs which allows you to lint & build your package definition using C-c . l and C-c . b
<Apteryx>To set your system so that you can use the flow described above you'll want to refer to the manual at chapter 8, it gives useful directions to work directly from Git.
<enoeht>I accidentally deleted the source archive, now I'm getting guix environment: error: build failed: getting attributes of path `/gnu/store/p142amjzp1zplf6c659fmgrilhzdl86n-kodi-16.0.tar.xz': No such file or directory... is there any way to fix this
<Apteryx>enoeht: Oh, did you delete it directly from its store location?
<enoeht>I accidentally deleted an archive from /gnu/store and now I am getting this error "guix package: error: build failed: getting attributes of path `/gnu/store/p142amjzp1zplf6c659fmgrilhzdl86n-kodi-16.0.tar.xz': No such file or directory", is there any way to get this file back? I've tried removing the package and calling gc with no luck
<rekado>enoeht: deleting items from /gnu/store is very bad
<jmi2k_>Help, please! Xorg doesn't detect any input: keyboard or mouse. I read that it should be related with xserver.conf, but I don't have that file. I'm not using a login manager, just installed xorg-server, xinit and some drivers.
<rekado>and it includes the annoying step of linking /gnu/store/.../bin to /bin
<ng0>I've packaged some more dependencies for libextractor, but it's difficult to get more replies (mainly: I need a maintainer to reply) from upstream libmp4v2, where it went etc... as code.google.com will disapear soon, is there a place where I can propose to GNU to fork it to continue development, or if I comment it enough will a fork at gnunet.org be enough? the situation out there of the forks is wild chaos..
<ng0>those are the two last options I would want to decide on if I get no reply this month
<adfeno>About recipe for abbaye (that is currently depending on Google Code): I received an email from nevat, and according to him, the text font which is bundled is no longer used because they decided to write the game text using images.
<enoeht>guix package: error: build failed: some substitutes for the outputs of derivation `/gnu/store/s14xmy0liyr93cgybf16a40mlkyqlrb9-kodi-16.0.tar.xz.drv' failed (usually happens due to networking issues); try `--fallback' to build derivation from source
<roelj>enoeht: Have you tried gc'ing the derivation? `guix gc -d /gnu/store/s14xmy0liyr93cgybf16a40mlkyqlrb9-kodi-16.0.tar.xz.drv'?
<cbaines>So, I'm trying to use substitute* from (guix build utils) in a service start script, but it doesn't seem to work (I get an error that looks like its not using that special syntax), I imagine this is a Guile thing, but I'm wondering if there is a way to make it work?
<rekado>download the substitute with wget, then: bzcat p142amjzp1zplf6c659fmgrilhzdl86n-kodi-16.0.tar.xz | guix archive -x /tmp/p142amjzp1zplf6c659fmgrilhzdl86n-kodi-16.0.tar.xz; then sudo mv the file back into the store.
<Apteryx>Looking at our Python-2.7 package, I was wondering: do the patches need to reference the exact filename to be patched or is there some fuzzy matchig mechanism? I see we are still patching 2.7.10 but we're now using 2.7.12.
<civodul>i just pushed zile-on-guile, you folks should give it a try, it's pretty cool :-)
<Apteryx>civodul: Cool! A precursor to a fully working emacs-on-guile? ;)
<Apteryx>I'd be tempted to say that the first thing that must happen is to provide the story of what happened and any available evidence. Have you read submitted such a claim at email@example.com?
<Apteryx>The CODE-OF-CONDUCT says: Instances of abusive, harassing, or otherwise unacceptable behavior may
<Apteryx>be reported by contacting a project maintainer at firstname.lastname@example.org.
<Apteryx>All complaints will be reviewed and investigated and will
<Apteryx>result in a response that is deemed necessary and appropriate to the
<Apteryx>circumstances. Maintainers are obligated to maintain confidentiality
<Apteryx>with regard to the reporter of an incident.
<rain1>okay thanks, thought it might be easier to just discuss but yeah
<Apteryx>No problem! I hope that your conflict can be resolved and that you can start contributing in high spirits again! :)
<alezost>jmi2k_2: hm, do you have "/run/current-system/profile/lib/xorg/modules/input/evdev_drv.so" file?
<jmi2k_2>alezost: to see if I could notice any differences, I enabled the slim service and it worked perfect. Then, I saw the Xorg.0.log (this one was generated at ~/.local/share/xorg/Xorg.0.log) and the last lines were pretty much the same.
<adfeno>Please report to the project's bug mailing list (the project: Guix).
<adfeno>It's an error in the recipe (which tells Guix how to provide php-fpm to you).
<adfeno>Because the php-fpm recipe should not write "/etc/" to the Guix store ("/gnu/store").
<buenouanq>do you know who packaged it? I don't feel I should report anything because I have no idea how this is supposed to work. Someone has obviously used php here before (therefor it's packaged), but everything written about it assumes a normal file system hierarchy.
<buenouanq>I think I'm probably approching it wrong. Should I be making it into a service or what, I don't know.
<vtomole>Im on qemu, I added the -net user tag like lfam said "qemu-system-x86_64 -m 1024 -smp 1 -net user -net nic,model=virtio -boot menu=on -drive file=guixsd.img -drive file=guixsd-usb-install-0.12.0.x86_64-linux"