<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.
<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
<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.
<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.
<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?