<digash>email@example.com depends on the following 23 packages: firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org ld-wrapper@0 email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com
<bandali>brettgilio, hehe. more seriously though, i'd love to find other fellow formal methods people in the guix community. it may not be a bad idea to email guix-devel, cc'ing/naming me if you wish, and see if there are any others? :-)
<digash>looks like info-reader depends on perl, but also disallowed?
<Blackbeard[m]>And lisp is easier to understand for non programmers than other languages
<leoprikler>Well, I certainly disagree on the "Emacs is for programmers" thing if it is meant exclusively. (That said, Emacs is also for programmers and we should not forget support for the various tools they need.)
<leoprikler>As far as programming Emacs itself is concerned, I wouldn't trade Lisp for another language family, but I would trade Emacs Lisp for another Lisp.
<peanutbutterandc>It seems the maintainers (I know atleast nckx does) prefer anything to propagated-inputs because of the 'conflicts' and it seems it goes against the idea of functional package management
<alextee[m]>anyone else get this? `- 'compress-documentation' phaseoutput (`/gnu/store/6rnhfi8zrdajbahbq9ii8bpj7mwfcjba-info-reader-6.6') is not allowed to refer to path `/gnu/store/ziinjmbnq004866mwjrczsk12wf35qb8-perl-5.30.0'`
<alextee[m]>happens with `guix install info-reader` after the install phase
<nixo_>Ehy guix, anybody knows what SOURCE_DATE_EPOCH should override? I'm following civodul suggestion to patch julia to use it, instead of using libfaketime. So far so good, matched jl_gettimeofday. Julia compiles, tests run successfuly.. but it never ends. Looking at the source, it's calling a function that does this: while (time() - start) < waitfor. Since time is always the same, this won't end
<nixo_>but IMHO is their bug. They should use a monotonic clock there
<leoprikler>As for why it is spammed to stdout like this: substitutes are always updated first when considering a package to build and since this step is done for multiple packages it is the only output you will see before things start actually building.
<leoprikler>as snape said, your ~/.guix-profile is already added for you
<raghav-gururajan>I have a patch in ".diff" format. I was told to do `git am --3way --directory=~/patchfile.diff`. But the process is still going on and does not seem like anything is progressing. What should I do?
<nixo__>Hi civodul! I was working ont he julia SOURCE_DATE_EPOCH thing. But the more I play with the time, the more bugs in julia I find .-. (see https://github.com/JuliaLang/julia/issues/34115). I'm pausing this for a couple of days (also beacuase for some reason, even if time() now returns values according to SOURCE_DATE_EPOCH, mtime of cahce files is still correct, and I don't know how that's possible. But since faketime was
<nixo__>working, probably there's another function used to get the time? or maybe libfaketime does something more. I'll try to figure this out)
<rekado>I’m trying to use guile-next with mumi, but I’m stuck on gnutls.
<rekado>1) gnutls somehow doesn’t benefit from the 2.2 -> 3.0 rewrite, so I had to add it to the inputs of mumi; 2) it fails trying to connect to debbugs over HTTPS: “Unbound variable: set-session-server-name!”
<str1ngs>emacsy is a guile library to create emacs like applications
<str1ngs>it provides things like keybindings, buffers, windows. it has a nice abstraction. in that it's not dependent on any GUI toolkit either.
<janneke>str1ngs: yes, i feel that way too -- but i don't like to think that i'm letting you down
<str1ngs>janneke: nope not at all. the only think we might need immediately is static html docs for emacys. maybe later when re visit documentation introspection. or I'll probably run any major API change by you.
<Parra>I want to try emacs, but it's so vi like, I'm more used to nano
<bavier>fortunately nano has decent scheme syntax highlighting
<Parra>I mean, I just like that style, I come from Visual Studio C++ which is very different, I moved to Linux many years ago but I only use vi like mode if I only have that option, and emacs seems similar to vi, maybe it's time to start learning it in deep
<valignatev>I'm not sure what do you mean, but emacs is very different from vi in a sense of having a modal editing workflow
<valignatev>e.g. you don't have to enter an "insert mode" to write text
<valignatev>raingloom: I couldn't figure out nix import yesterday as well. I tried to import it from the local copy of nixpkgs though, didn't want to spin a whole nix stack for it. Ended up "importing" the package by hand as well :)
<raingloom>hmm, which package has the manpages for stuff like calloc?
<lispmacs>hi, I've got a HP LaserJet Professional P1102w USB printer, which worked for me under Debian 9 (free system) but in Guix, cups Web administration tool does not see it. Do you have any ideas for me?
<lispmacs>I was just wondering if somebody was working on (or planning to work on) some kind of package install queue interface? I have this frequent problem where I'll start a 10 minute package install, and then two minutes into that decide I want to install another package as well.
<lispmacs>but by the time the first installs are done, I forget to install the other thing I wanted
<leoprikler>you can start the second installation right away
<leoprikler>it will build things in parallel rather than sequential, but it's super duper safe to do so in guix
<vagrantc>really was happy to see "configuration file" listed with "guix system list-generations" !
<nckx>leoprikler: Have you tried that recently? Guix locks profiles during building now (I understand why, but it broke that common operation for me).