<goglosh>what is the package I need to connect wpa? <goglosh>tried guix package -i wpa_supplicant <goglosh>okay now I do have trouble. installed wpa-supplicant but 'command not found' <goglosh>I managed (don't ask me how) to connect wireless <goglosh>but this thing won't resolve addresses <goglosh>oh god I made it. feels good. sorry about asking prematurely, leaving, and then just, figuring it out <Steap>AndChat404481: people usually idle here, so don't ask to ask <AndChat404481>hi rekado hi steap and other, sorry I havent changed my hostname yet. So is there any guix developer online here now ? <rekado>AndChat404481: I guess you could call me a Guix developer. Do you have questions about the projects? <alezost>AndChat404481: just ask, if you have a question <rekado>(or are you just checking if people are online...? ;)) <AndChat404481>I have many question to ask. Just wait a 5 minute more, I must go to toilet. <AndChat|404481>So there, Im just a intermediate linux user but Im are big fan of fsf. So I heard there is guixhurd under development, is that true ? <rekado>AndChat|404481: yes, Guix is being ported to the Hurd. <rekado>eventually, you will be able to run a GuixSD system using the Hurd instead of Linux. ***yang_ is now known as yang
<rekado>AndChat|404481: do you mean a GUI for the package manager? <rekado>we already have an Emacs interface in addition to the command line interface. <rekado>there also is a minimal web interface, but it provides access to only a tiny subset of all the features of the package manager. <mkletzan>Yaay! \\o/ I managed to install guix ;-)emacs <mkletzan>and also type "emacs" in ERC window instead the terminal apparently <taylanub>ACTION can't wait to use GNU Guix/Hurd with GNU Guile/Emacs running on it :P <mkletzan>unfortunately it starts into window maker only and I have no idea where the configs are so I can debug why it doesn't start into ratpoison <rekado>mkletzan: there's an odd bug that changes the session to windowmaker when you mistype the password at the login screen. <mkletzan>rekado: oh, that might've happened, I forgot to set my passwords the first time <iyzsong>WindowMaker is used by the 'slim-service' as fallback session, you can override it in the system config or write a ~/.xsession script. <rekado>iyzsong: can it be removed completely? I find it odd that I have WindowMaker even though I didn't ask for it in my operating-system expression. <iyzsong>rekado: well, it's also (mainly) the auto-login command, slim don't choose a default session for auto login, so we have to provide one. <efraim>gnunet doesn't build because gnurl doesn't build <efraim>currently gnurl is at 7.37.0 (?), and 7.40.0 fails on the same reason (test 46) <efraim>gnurl 7.43.0 is missing something so it doesn't compile to begin with <efraim>gnurl inherits from curl the ability to skip the one test, but I haven't gotten it to work right for me, and disabling all the tests just seems wrong <efraim>i guess i could leave in the logic and a note for it to be fixed later <mark_weaver>after a recent upgrade of something else, curl 7.43.0 failed to build but curl 7.44.0 succeeded. I've forgotten the details. <efraim>7.43.0 complained about a missing install.sh/install-sh file <efraim>so that seemed more like a whoops error <mark_weaver>I have to go now, but I can help with this within a few hours <mark_weaver>efraim: It should be (zero? (system* ...)) instead of just (system* ...), otherwise errors won't be detected. <mark_weaver>also, since 'outputs' is not used in the new check phase, you can change "lambda* (#:key ...)" to just "lambda _" <mark_weaver>efraim: but also, we really need 7.43.0, because 7.40.0 has security flaws <efraim>so i guess i could take a diff of curl 7.43.0 to 7.44.0 and check the gnurl 7.43.0 diff provided and try to meld them <mark_weaver>efraim: there's a new tarball for gnurl 7.43.0, isn't there? <mark_weaver>okay. taking the curl-7.44.0 diff and trying to apply it to gnurl-7.43.0 sounds good to me <civodul>GNUnet doesn't build i'll talk to grothoff since he's around :-) ***francis7 is now known as francis7-fsf30
***francis7-fsf30 is now known as francis7
<paroneayea>I must rectify this, I can't give a demo without showing nethack <goglosh>I'm going to run `guix system reconfigure` but I badly need wpa-supplicant to come in there, how should I declare it in the system file? <lfam>I see the dmd manual was last updated 2014-07-08. Have there been changes to dmd since then? I'm planning to install GuixSD soon and I'd like to read the docs in advance. <lfam>I know that GuixSD is "alpha" but how much pain am I really in for? <lfam>on a scale of Ubuntu to LFS <davexunit>I wish we had GNOME, but things work reliably. <lfam>That would be good for getting users but I won't miss it (never used it) <taylanub>given how much pain I've had with the Ubuntu installation on a family laptop, your scale is pretty narrow :P <lfam>Haha, fair enough. You know what I meant ;) <lfam>On the right hardware everything works out of the box ***Gonbe is now known as _`_
<efraim>i see that graphviz can be updated from 2.28.0 to 2.38.0 but a lot of stuff depends on it, including guix <civodul>efraim: yes but it has to be updated someday anyway :-) <civodul>110 packages depend on it apparently <civodul>it would be great if at the same time you prepared a second patch that moves its doc to a separate "doc" output <civodul>since the doc represents more than half of its size <efraim>a bit more work than "find stuff I have installed so I can update it" but sure <efraim>hmm, just finished building, it looks like /bin is 60MB and /share is 6.1MB <civodul>i had noted 10MB for all of Graphviz <efraim>20M on /bin/cluster, 20M on /bin/edgepaint <efraim>its almost 11pm here, i'll take another look at it tomorrow <paroneayea>I think I also included the most boiled down intro to functional programing in here, since I know many people in the audience aren't familiar, and use that to guide towards "so how to we apply this to packaging?" <davexunit>paroneayea: are we going to get a sneak preview? :) <paroneayea>also, I decided to throw out "proper presentation" and I'm just going to unfold an orgmode document as I go :) <paroneayea>I was beating my head against trying to do a nice presentation and I decided, screw it, this is a moderately technical talk, people can survive me unfolding an orgmode tree as a presentation format :) <paroneayea>but I finally am in the right groove of writing this thing out <civodul>i guess you can probably demo the command-line stuff <civodul>or M-x guix if you have the appropriate audience ;-) <paroneayea>civodul: I will probably do a demo of M-x guix-all-available-packages and M-x guix-generations <paroneayea>but I will probably not do M-x guix because I just tried it today and I don't get how to use it yet <civodul>i was thinking more of what you suggests actually <civodul>did you know you can diff generations in M-x guix-generations? <paroneayea>I wonder if the "git-like" part of my talk is a bit too much detail <paroneayea>I'm going to give a test demonstration of the talk to my brother tonight so we'\\ll see <paroneayea>I think it's an easy idea for many audience members to catch on to though <paroneayea>most devs know git now, and it makes the hashes seem familiar <paroneayea>plus rolling back in git is an easy thing to understand as "whoa cool" <civodul>though the store is not content-addressed <civodul>often i talk of the "Corresponding Source" as the GPL defines it <civodul>just to say that here, we really have it all :-) <paroneayea> - We refer to commits by their hashes... we'll see more hashes in <paroneayea>maybe a bit closer to making the hashes familiar without explaining why <davexunit>civodul: hmm, I always considered the store to be content addressed <davexunit>where that "content" was the full dependency graph of the derivation <civodul>davexunit: it's not content-addressed in the sense that the hashes are not hashes of the contents <civodul>if you look at Eelco's thesis, he did try content-addressing too <paroneayea>they aren't hashes of the actual files being revisioned (though they are of the "objects") <paroneayea>so, similarly vaguely "nearly but not really CAS" :) <davexunit>paroneayea: "I've fallen and I can't get out!" hahahahaha <davexunit>I distinguish memoization from the traditional notion of a cache. <davexunit>and I see that paroneayea mentions this point in his draft <davexunit>"Memoization means caching with no cache invalidation challenges" <civodul>mark_weaver: do you have a patch for gnurl? <mark_weaver>I'd been hoping that gnurl-7.44.0 would be released, but I guess we'll have to figure something else out in the meantime. <mark_weaver>lfam: btw, civodul recently added the ability to clear entries from the failed builds cache. <civodul>mark_weaver: i'll see if we can get gnurl released ;-) <mark_weaver>lfam: if you run "guix pull", then hopefully "guix gc --list-failures" and "guix gc --clear-failures" subcommands will be available <civodul>alezost: C-c . b is awesome, as usual! <alezost>here I also use "C-c . s" to perform "guix-download" on the current package (to see its hash), I'll send a patch for it soon <alezost>I mean the hash of the package source <civodul>excellent, i was about to propose it :-)