IRC channel logs


back to list of logs

<orbea>huh, test_concurrent_futures has taken hours so far...
<orbea>ACTION tries again
<orbea>strange, freezes on test 389 out of 390...first time it was test_concurrent_features, now its test_lib2to3
<orbea>and now test_multiprocessing_forkserver, test 389 again...
<orbea>0.11.0 is doing it too, I guess this is a problem in the repo...
<OriansJ>rekado: How much work would it be to convert the yale haskell on CLISP to one that can bootstrap GHC or something we have source code to which could bootstrap GHC?
<guix>mkfs.ext4 -L my-root /dev/sda1 doesn't work because it contains the gnu-disk image, I can used /dev/sda2 buts it's only 8mb so i run out of space,what do i do?
<guix>I've tried resizing my virtual disk but I couldn't get it right
<guix>join #vbox
<albertoefg>sneek help
<albertoefg>sneek later tell lfam that I think he is hiding to not play hedgewars
<sneek>Will do.
<bldtg>I'm still having trouble understanding things about testing and submitting packages
<jmd>bldtg: What kind of trouble.
<bldtg>like, what are the steps required, for one thing. What I've gathered, and I'm not sure it's correct, is that 1. I need to git clone 2. modify or add a package module 3. test it (don't know exactly how) 4. submit the patch
<bldtg>there's so much stuff and I don't understand all of it so I feel like I'm underqualified to submit patches.
<vtomole>How do i get rid of this error?: "guix system: error open-file: No such file or directory:"/gnu/store/…-guile-bootstrap-2.0.drv"
<Apteryx>bldtg: So far my flow looks like that: 1) I setup my git clone of guix to me my main guix (covered in the manual). 2) Fix a package definition directly in the source (if already exist). 3) In a guix environment (guix environment guix), I rebuild the package sources (not sure if this is really necessary; make -j3) 4) Build my modified package: guix build my-modified-package 5) Install it using "guix package -i
<Apteryx>my-modified-package", replace "i" by "u" if it's already installed to update it instead. 6) It's installed... test it like you'd test any installed software.
<fredmanglis>bldtg, from my experience, just work on the errors and submit the patches. The people here are really helpful
<Apteryx>1) is not necessary per see.
<fredmanglis>I still don't understand a lot of guix and I have one patch accepted - working on a more challenging package now
<Apteryx>But if you want to work with the latest and greatest, and test with the latest and greatest, it simplifies things a bit.
<vtomole>I've been trying to install it all day and i don't even know anymore :(
<Apteryx>vtomole: Installing what exactly?
<jmd>bldtg: Submit a patch. If there is anything wrong about it, then somebody will tell you.
<Apteryx>(sorry just joined)
<vtomole>I'm trying to install it with guix init
<vtomole>on a vm
<Apteryx>vtomole: And you are using GuixSD 0.12.0?
<bldtg>Apteryx: I don't think I fully understand guix enviroment
<bldtg>Apteryx: I just don't have a hold on the whole process you described.
<vtomole>bldtg: Have you used nixos?
<bldtg>vtomole: No, I haven't.
<bldtg>vtomole: I'm very new to all this. guix, packaging
<Apteryx>bldtg: I can elaborate on any of those points if you'd like. FWIU the environment is a temporary profile where only specific outputs (programs, libraries) get installed. When you do "guix environment guix" it installs all the dependencies required to build guix I believe.
<jmd>bldtg: I would recommend starting off by looking at an existing package and using that as a pattern.
<vtomole>Aptery: Installing guix shouldn't be this hard.. idk what's wrong with my image. I downloaded it from here:, and then i converted that raw image to a vdi which i am now running on virtualbox'
<bldtg>jmd: I have modifying the package down; I'm starting off just updating the version of a package.
<vtomole>I'm also connected to the network
<bldtg>Apteryx: Maybe I should start from the beginning. You said it's in the manual. do you mean section 8.1?
<Apteryx>vtomole: So you basically followed the instructions from the manual?
<rekado_>OriansJ: I wouldn’t use Yale Haskell for that. I’d like to try to see if Hugs can be used to run an older version of GHC, if there is a GHC version that is written in only Haskell98.
<vtomole>Apteryx: Yes
<Apteryx>bldtg: Yes the whole 8 section is useful to get started.
<Apteryx>The bit I was refering to about using guix from git as your main guix is detailed in a note under section 8.2
<Apteryx>vtomole: OK. That's strange. If you can reproduce it I think you should file a bug on
<Apteryx>If you don't mind experimenting you could also try a "guix pull" to refresh guix content.
<Apteryx>It might get you pass the problem, although that you can't install the provided image would still be a bug.
<Apteryx>I don't have more ideas at the moment. I hope you can sort it out :)
<bldtg>Apteryx: so I git clone, then... run guix enviroment guix?
<vtomole>guix pull doesn't work either :(
<vtomole>"failed to download up to date source exiting"
<vtomole>Apteryx: Any interesting things I can do without installing? Or am i just a sitting duck now?
<vtomole>I know I could run the scheme REPL..
<jmi2k_>Is there any way of dumping system configuration? I *accidentally* lost config.scm...
<jmi2k_>Nevermind, solved. dd + strings + grep + some patience came to the rescue.
<jmi2k_>I can't start X with xinit (xf86OpenConsole: Cannot open virtual console 7 (Permission denied)). It works if I set its suid bit, but it's a good idea?
<ZombieChicken>X needs to be suid to run w/o systemd (specifically, logind). I think there is an elogind package that pulled logind from systemd for GuixSD, but I'm not sure and I'm not sure if that does what needs to be done to run X w/o root perms
<davexunit>never set the suid bit for any file in /gnu/store
<jmi2k_>davexunit: now I'm carefully doing that for debug purposes, but I think I can do it using setuid-programs in my config.
<davexunit>jmi2k_: yes, that's the correct way. just making sure that was known. :)
<jmi2k_>ZombieChicken: I have the elogind-service, but I don't know what to do after that. I don't even know if I'm supposed to do anything more.
<jmi2k_>davexunit: just something more... How can I do that :D I have this: (setuid-programs (cons #~(string-append #$xorg-server "/bin/X") %setuid-programs)) . I copy-pasted it from somewhere, but it causes kernel panic at boot.
<davexunit>jmi2k_: hmm, not sure why it would cause a panic
<davexunit>your code looks fine
<ZombieChicken>I don't have GuixSD installed anywhere atm, so I can't comment further tbh
<jmi2k_>Ok, GuixSD boot fails because chown can't find the file. Then, it tries to enter a guile prompt, and finally kernel panic. Can anyone test it please?
<civodul>Hello Guix!
<jmd>civodul: Hi
<paroneayea>there should be a podcast episode hitting Hacker Public Radio interviewing me about Guix
<paroneayea>it's an old interview, but it'll finally go up :)
<civodul>paroneayea: woohoo, cool!
<civodul>when will it be available?
<paroneayea>civodul: Wednesday!
<paroneayea>I'll post it to the list when it is.
<roptat>one of the packages I would like to add to the distro has a reproducibility issue
<roptat>I found that it recorded the build date and fixed that, and that it records temporary files paths
<roptat>for instance /tmp/guix-build-omake-0.10.1.drv-0/camlstartup8412d8.o
<roptat>or /tmp/guix-build-omake-0.10.1.drv-0/camlstartupe2f129.o in another build (same binary)
<roptat>who could be the culprit here?
<davidl>I just tried to install with btrfs but then I get a boot error saying it can't find fsck.btrfs and then Im brought to rescue prompt. I guess I can put "check? #t" in the system conf file but I wonder if there's a way to fix it? I have btrfs-progs in the packages definition list and btrfs in the initrd modules definition and thought that would be enough but I guess not.
<davidl>*"check? #f"
<jmd>davidl: I think we would need to include the btrfs-progs in the installation-os
<davidl>jmd: ok, so maybe in GuixSD 0.13 if Im lucky then.
<jonsger>okay. I don't think guix is ready to run on a Nokia N900 with Mameo :P
<civodul>roptat: presumably OCaml generates file names based on a random seed
<roptat>civodul, yes I just found a patch in debian for that, I'm trying it
<roptat>civodul, unexpectedly, it removed all differences between the two versions *except* for the random filename ^^'
<Apteryx>vtomole: I think if you are confident you followed carefully what's in the installation section of the manual and are hitting these problems they are worth being discussed at "".
<Apteryx>Why doesn't the restart button of IceCat following a crash, well, restarts IceCat?
<civodul>roptat: good first step anyway ;-)
<buenouanq>nginx and letsencrpyt with the certbot
<buenouanq>I wanted to install the certbot under the nginx user, but it not loginable.
<buenouanq>Making it such is something I prolly shouldn't do, but maybe temporarily just to install this is ok?
<buenouanq>Otherwise should I do it as root? That also doesn't seem the wisest...
<Acou_Bass>eey folks... ive got a bit of an issue, ive just reinstalled my guixSD laptop, and it kernel panics on boot with no real way to avoid... XD any advice i can take?
<ng0>for a quick fix, try a previous kernel version
<rekado_>emacs-devel talks about an official Emacs Docker image.
<rekado_>I was going to suggest building it with Guix.
<rekado_>i.e. “guix environment --ad-hoc emacs”, then “tar cf emacs-closure.tar $(guix gc --requisites $GUIX_ENVIRONMENT)”
<rekado_>then in the dockerfile “ADD emacs-closure.tar /” and exposing “$GUIX_ENVIRONMENT/bin/emacs” as the default command.
<rekado_>this worked for me earlier with another application.
<rekado_>our Emacs closure is pretty fat, though: 582M
<rekado_>AIUI a graphical Emacs really doesn’t need to be built with Gtk because it’s not a proper Gtk application anyway.
<buenouanq>letsencrypt tutorial wants me to make /etc/ssl/certs/dhparam.pem but it's a read only file system
<buenouanq>what is the guix way of doing this?
<rekado_>or maybe there’s a way to reduce the size of the Gtk closure?
<rekado_>buenouanq: what is this file used for?
<ng0>i don't know what LE needs it for, but "openssl dhparam"
<ng0>but I think you know that, i'Äm just confused why LE wnats it
<ng0>oh, tutorial
<buenouanq>I just run random commands I find online for fun.
<buenouanq>and when they don't work I come and bug you guys
<geemili>How do I get the DESTDIR? The software I'm packaging doesn't have a configure stage, but the Makefile takes a `DESTDIR`.
<geemili>That is, a `DESTDIR` environment variable
<rekado_>geemili: you can get the store directory by evaluating “(assoc-ref %output "out")”
<ng0>for example: put this in the (arguments) phases: (setenv "DESTDIR" (assoc-ref %output "out"))
<ng0>what rekado_ said
<rekado_>to override a Makefile variable just do (arguments `(#:make-flags (string-append "DESTDIR=" (assoc-ref %outputs "out"))))
<rekado_>using setenv is not necessary in most cases.
<rekado_>setenv sets an environment variable and that’s ugly when a make-flag is sufficient.
<geemili>I was planning on using `#:make-flags`
<geemili>Also, is there a way to install packages from a file?
<geemili>Something like `guix package -L /path/to/dir -i package`?
<ng0>the most basic (and not so inteligent example) can be seen at gnunet HEAD and in gnurl atm
<ng0>where it's like guix package -f file.scm
<geemili>I've been using that for building the package, but I wanted to move away from it
<geemili>Since it means ending the file with the package
<rekado_>geemili: as long as your file is on the Guile load path (or better: GUIX_PACKAGE_PATH) you can use any packages that are defined in it.
<bldtg>I don't understand section 8.2 of the manual
<bldtg>it says: "the pre-inst-env script lives in the top build tree of Guix". I can't find the script.
<rekado_>I don’t see any 8.2 section.
<rekado_>section 8 is “Acknowledgements”
<rekado_>bldtg: have you run “./configure” yet?
<bldtg>section 8 is contributing
<rekado_>it’s section 7 in my manual
<bldtg>rekado_: no... I guess I don't understand any of section 8
<rekado_>7.2 assumes that you have at least built Guix already
<rekado_>you don’t need to install it but you still have to build it
<rekado_>so the usual steps are still needed: ./bootstrap; ./configure --localstatedir=/var; make
<bldtg>I must be getting ahead of myself. I don't know anything about ./bootstrap or --localstatedir
<bldtg>this is probably more general knowledge stuff than guix stuff, isn't it?
<buenouanq>well, y'all'll be happy to know that I got LE working with an A+ score from ssllabs
<geemili>Running `guix package -L ./ -s vimb` gives me errors:
<geemili>`guix package: warning: failed to load '(vimb)':`
<geemili>`ERROR: no code for module (vimb)`
<rekado_>what about the vimb module? What does it look like?
<ng0>bldtg: yes, this is very general
<rekado_>bldtg: it’s specific to guix. “--localstatedir” has to be set during configuration with “configure” to ensure that the built Guix uses the same database that your running instance of Guix uses.
<rekado_>bldtg: ./bootstrap is a script that creates the “configure” script and does a few things more. Other projects might do without a script like that and just request running “autoreconf -vif” or similar.
<Acou_Bass>ng0: i havent got any previous kernels installed, its a fresh install :( XD
<rekado_>geemili: your module is called (gnu packages vimb-browser)
<rekado_>so it must be in a file $GUIX_PACKAGE_PATH/gnu/packages/vimb-browser.scm
<geemili>I see
<rekado_>module names and file paths must match
<geemili>Now everything makes sense. Thanks!
<ng0>Acou_Bass: not like this. you can specify the kernel being used