<OriansJ>Swedneck: how detailed of a guide are you looking for? <reepca>it seems that wget works because it has a timeout for how much silence to allow from the data transfer connection before giving up. But once it does give up, it automatically retries using the REST command to restart wherever it gave up, which apparently works okay. Also, in this particular case, despite our progress reporter saying "100.0%", it actually still has 204 bytes to transfer, apparently. <apteryx>it seems that starting shepherd in my ~/.xsession or ~/.bash_profile, and then logging out, the shepherd process is still alive. I'm surprised by that. <apteryx>(the user shepherd process, that is) <apteryx>the problem is that its dangling socket file prevent it from restarting fully upon relogin <apteryx>I'd need to add a rm command on it myself in xsession it seems... inconvenient for novices <kammd[m]>Hi guys does guix use signing for packages or just hashes? <atw`>kammd[m]: do you mean, when a package is downloaded for installation, is a signature on the downloaded thing checked? <atw`>I believe the answer is no, only a hash check is performed. <kammd[m]>Ok.. so similar to Nix or linuxbrew(homebrew). <atw`>from what I know of homebrew, yes <eubarbosa>hey, installing shellcheck this error is issued: <eubarbosa>cannot build derivation `/gnu/store/zzp6rdfbq2rkh8806haz6rplri5m39b8-shellcheck-0.5.0.drv': 1 dependencies couldn't be built <eubarbosa>guix package: error: build failed: build of `/gnu/store/zzp6rdfbq2rkh8806haz6rplri5m39b8-shellcheck-0.5.0.drv' failed ***rekado_ is now known as rekado
<rekado>what’s the dependency that couldn’t be built? <eubarbosa>I might need some help to know which one, lol <eubarbosa>"attoparsec-iso8601/Data/Attoparsec/Time.hs:79:33: error:" <eubarbosa>Throw to key `srfi-34' with args `(#<condition &invoke-error [program: "runhaskell" arguments: ("Setup.lhs" "build") exit-status: 1 term-signal: #f stop-signal: #f] 56dd40>)'. <rekado>eubarbosa: that’s really bug 33922, I think. <rekado>there’s a fix for it, which I’ll push today. <eubarbosa>rekado: is the process of upgrading package difficult, I rather like to learn and help <eubarbosa>hey, installing icecat and it is taking its time with: building...-icecat-60-3..drv... <g_bor>eubarbosa: I guess you can just ctrl+c it... <eubarbosa>g_bor:yep, but as I 'guix package -i icecat' again, it just returns from where it stop <g_bor>what are you trying to achieve? <g_bor>I guess there is no substitute for icecat, that's why it can't download, but must build it from source. <g_bor>Building icecat can take a lot of time. <eubarbosa>g_bor: I think I still did not "enable" substitute... <eubarbosa>I recall doing it back there. Must to learn how to do it agian <g_bor>you could check what are the command line parameters of your daemon, to learn you substitute urls, and check /etc/guix/acl for the list of authorized substitute server public keys. ***ayerhart_ is now known as ayerhart
<eubarbosa>guix pacakge "building" would help us more if there is a percentage progress bar/number <civodul>eubarbosa: we've thought about it but it's the best we could do is make an estimate based on past builds of the same package <civodul>rekado: could you restart a couple of build machines so we have more aarch64/armv7 builders? <g_bor>civodul: I got a message from my mailer daemon, that my email could not be delivered to ludo@gnu.org <g_bor>host fencepost.gnu.org [2001:470:142:3::e]: 550 relay not permitted <civodul>g_bor: that happened to rekado as well a couple of weeks ago, but i don't understand what that means <g_bor>civodul:ok, I will check it later. The mail was not that important, just a quick response to lsl88. I just wanted you to know that this happened. <ebrasca>Guixsd don't install because of locale don't compile. <ebrasca>I get this error "build of /gnu/store/x96jqkjd7jagszan8srmqblhgx1g6qmc-sed-4.5.drv failed" <roptat>g_bor, the memory issue I have seems to be related to the fact that antlr remembers decisions it took, thus growing memory usage <roptat>the usual way to solve that issue is to optimize the grammar to prevent antlr from having to do too much lookahead <roptat>ebrasca, guix should tell you where to find the build log, you can read it with bzless for instance <roptat>it should have more info about why it failed <ebrasca>Why do you don't include emacs to GuixSD install image? <roptat>is that error from the installation image? what architecture is it? <rk4>i was impressed with zile in the install image, didn't feel it lacking for the task compared to emacs at all [which is just writing one config.scm] <ebrasca>roptat: That one is from gentoo guix. <ebrasca>roptat: I have try with guixsd image but it don't have emacs. <roptat>I mean, what version of guix are you using? <ebrasca>roptat: I have : sys-apps/guix-0.16.0 <roptat>what does "guix --version" have to say? <roptat>weird, it has no version info... <jonsger>roptat: that's on opensuse always the case, if it's build from a commit and not from a release tarball... <roptat>ebrasca, did you allow substitutes? <ebrasca>roptat: What do you mean with "substitutes" ? <roptat>we have build farms that build the packages. you can allow receiving substitutes (binary packages) from them if you want to <roptat>substitutes are allowed outside of this config <ebrasca>roptat: Binary sound someting unsecure. <roptat>mh... sure, you don't need substitutes if don't feel safe <roptat>you can always "challenge" build farms though, which makes it a bit better (comparing local builds with builds from build farms) <roptat>I think there's a page on "binary transparency" in the manual <pkill9>you have to authorize substitutes before guix will use them if they're specified, so thye're pretty safe <ebrasca>How to change "sudo guix system init -c 8 -M 4 /mnt/etc/config.scm /mnt" to allow substitutes? <pkill9>and the default substitute servers are no more dangerous than default mirrors in other distros <roptat>that's a global setting for guix <roptat>basically, "guix archive --authorize < prefix/share/guix/ci.guix.info.pub" <roptat>but let's not use substitutes if you don't want to <roptat>that build failure could be transient (have tried multiple times?), because the release must have relied on that, so it should have been built correctly <roptat>or we could update guix with "guix pull" and try to use a newer version (we have sed-4.7 now) <ebrasca>Do I need to make some script to run it 100 times , 1000 times? <ebrasca>I like to ask why scheme and not cl? <jonsger>ebrasca: because Guile is the official extension language for GNU and Guix is a GNU project <ebrasca>jonsger: Why Guile is official GNU extension language? <rain1>elisp was made with emacs long ago <rain1>guile is a bit newer and evolved from tinyscheme as the script language for GIMP <kmicu>DamienCassou: that post is very opinionated and can too easily backfire. <rekado>g_bor, civodul I got the same mailer daemon error for an email sent to another gnu.org address today. <rekado>civodul: sure, I’ll restart some nodes. Do I need to disable them first on the head node and make sure that no builds are running on them? <rekado>(maybe we can add a zabbix check for number of running builds) <DamienCassou>ebrasca: I"m currently installing GuixSD as well in VirtualBox. I will let you know if I can reproduce *kmicu recommends sticking to the manual and its defaults. Tweaking during the installation process makes things non-trivial for the user and folks trying to help with or diagnose issues. <DamienCassou>the manual says to execute "guix system reconfigure" but I get "wrong number of arguments for action 'reconfigure'` <cnmne>you want `guix system reconfigure my-config.scm` <DamienCassou>I want to reconfigure the whole system, so should it be prefixed with sudo and the filename should be /etc/config.scm? <cnmne>i think the manual has this (?) <cnmne>i see, you do have to follow the '(see Invoking guix system)' <DamienCassou>the end of this page could mention `sudo` and `/etc/config.scm`. Updating the system the first time should not require reading another page IMO. What do you think? <cnmne>i admit on my first install it wasn't clear that the sudo mentioned with the `guix pull` also applied to the reconfigure, and i agree that the installation manual could be more explicit about the update process, and maybe even give a workflow example for updating/reconfiguring the system <civodul>rekado: i think you don't need to disable them, that should be fine <civodul>DamienCassou: where did you see "guix system reconfigure" without arguments in the manual? <civodul>DamienCassou: oh nevermind, found it, and will fix! <DamienCassou>civodul: I wrote a patch already. Can I send it to the mailing list? <DamienCassou>that would be my first contribution to guix and it matters to me :-) <DamienCassou>civodul: i just did. Please give me feedback if I did something wrong. Also, I disabled reception of emails from this mailing list so I hope people CC the senders <roptat>same issue on my side sending to a gnu.org address <civodul>roptat: could you forward the reply you got to sysadmin@gnu.org? <civodul>i don't mind getting less mail but it could become a problem ;-) <kmicu>Necomers are in the best position to catch such things and necomers sending patches are worth their weight in gold. Thank you! *kmicu bashes ‘w’ key multiple times cuz it didn’t register twice in ‘newcomers’ <DamienCassou>I hope my patch will get merged or at least that I will get feedback :-) <civodul>DamienCassou: sometimes we're not as fast as we'd like but i'm sure you'll get feedback <civodul>well it was easy to be fast in this case ;-) <rekado>DamienCassou: try reading civodul backwards… ;) <civodul>i'm always surprised it works this well <civodul>rot13 should be more than enough for everyone ;-) <jonsger>oh, didn't get that. And I'm hanging around here quite for some time :P <roptat>or openjdk:jdk for newer versions <bgardner>I'm going in circles here trying to get my config.scm modified to provide "make", is there some obvious syntax I am missing? <bgardner>I've added many other packages (i3-wm, emacs and so on) using the same pattern, but make is being balky <reepca>bgardner: you could use specification->package. The name of the package is "make", but the name of the variable containing the package is gnu-make, presumably to prevent name collisions. <reepca>it's in (gnu packages base) by the way <bgardner>Thanks reepca, how did you determine that? <reepca>M-x guix-edit make in emacs, looked at which file I was in and which variable the package was bound to. But the more proper way of finding the package is probably to "guix package -A make", which gives the package and line / column numbers as well. <mbakke>A recent email to "ludo@gnu.org" bounced, was this a known problem? <civodul>mbakke: a few people reported it on this channel, perhaps you can email sysadmin@gnu.org to find out what's going on if roptat hasn't done it yet <civodul>that's worrisome but i have no idea what it means <bavier`>just finished building out icecat on core-updates <rekado>civodul: I’ve also mailed sysadmin@gnu.org earlier. <apteryx>hello; is there a way to have M-x shell in Emacs source my ~/.bashrc? I'm surprised it doesn't. <apteryx>DamienCassou: you're right, I should probably have asked in #emacs. The value returned is /gnu/store/qn1ax1fkj16x280m1rv7mcimfmn9l2pf-bash-4.4.23/bin/bash <apteryx>DamienCassou: you are right. it must be something special about a function defined in my ~/.bashrc that only works after explicitly sourcing it when used from *shell* in Emacs. <apteryx>(it works without having to do this in xterm) <tune>agreed, I only learned of it from a post on hackernews <tune>despite used guixsd for around a year <eubarbosa>Are there any minimal graphical browser as I gave up on icecat(building is taking too long) <apteryx>eubarbosa: you should get substitutes I believe. Have you enabled mirror.hydra.gnu.org as well as ci.guix.info (authorized + substitute-urls) <efraim>i use 'links -g' often for one-off things <eubarbosa>apteryx: what is the PREFIX on this command? guix archive --authorize < PREFIX/share/guix/ci.guix.info.pub <jlicht>eubarbosa: you could try sbcl-next, although you should probably double check to make sure you are safe online using it :) <mbakke>Does the groff patch not cause thousands of rebuilds? <eubarbosa>I did, both icecat and next has webkitgtk2 as dependency, that one is exactly why its taking so loging building <mbakke>civodul: The one efraim reverted recently :) <efraim>I thought it was just me and then I saw berlin also picked it up as world-changing <civodul>efraim: could you tell me which commits should be canceled on berlin? <efraim>96733e9 is the one where I reverted it <mbakke>Hopefully those who accidentally pulled that commit realize that they should roll back to an older Guix before pulling again :/ <eubarbosa>Guix package manual says the substutive are enabled by default in GuixSD, but now that I "enable" it, icecat is just downloading binaries instead of building from source... <kmicu>What is unexpected about it? <rekado>they should be enabled by default without requiring user action. <pkill9>eubarbosa: it's supposed to download binaries, that's what the substitutes are <eubarbosa>pkill9: So we can install in both way, I get! <eubarbosa>Can Guix generate a scm file with all installed user package? <eubarbosa>So I just version that file and next GuixSD fresh install I just guix package early-installed-packs.scm ***Elon_Satoshi is now known as Copenhagen_Bram
<pkill9>that article that was posted to hackernews has a guile snippet that does that i think <pkill9>you can also get a list of installed packages with `guix package -I` and put that list into the example manifest file given in the guix manual <bgardner>chsh throws a pam error, is there a different, guix-y way to select a user shell? <civodul>bgardner: you'd rather do it in the global config file, under 'user-account' <bgardner>civodul: I was just realizing that, should have looked first before I asked. Thank you! <sykloid>Is there some kind of "empty" package I can inherit from while testing things out? I don't want to have to specify version/source/build-system, etc when trying to create an environment for my project. <pkill9>'hello' is a basic useless package <pkill9>all it does is print 'Hello, world!' <sykloid>Yeah, that looks like the best idea. <sykloid>I'm getting grand mal build errors when trying to do `guix environment --ad-hoc ghc cabal-install`, is there a way I can set the package definitions to some "stable" set that works? `guix pull -l` currently shows that I'm using the master branch, which may be too bleeding-edge. <ebrasca>DamienCassou: How is going your install of guixsd? <DamienCassou>ebrasca: It was working fine but I had to stop because I had work to do <ebrasca>I get similar error with GuixSD image installer. <kmicu>ebrasca: do you really want ‘ea_ES’ and not es_ES? <ebrasca>Yea "Installation finished. No error reported." <g_bor>istm the find files call misses a parameter. <g_bor>It goes like: (find-files dir regexp) <vagrantc>ok, added a directory, and now it doesn't get a syntax error, but it doesn't actually do the substitution :/ <g_bor>How does the call look like now? <g_bor>I guess simply "." should work for the directory... <g_bor>I'm trying to do something similar now...