<jlicht>sneek: later tell civodul: it seems that if I want to include the (json) module in e.g. (guix build node-build-system), it will be part of the module-import derivation either way because of the modules that are imported by default via build-expression->derivation
<lfam>Or, does `guix gc --references` just refer to store metadata, which was created by scanning the store item earlier?
<lfam>I'm reading every search engine result for 'gc references' in the IRC logs :p
<dpg23>So does 'guix package -i emacs' compile all dependences, and emacs itself, from source?
<lfam>dpg23: If you have authorized the use of binary substitutes from hydra.gnu.org, and substitutes are available for the derivations you are trying to build, then you will download the binary substitutes instead of building. Otherwise, you will build from source.
<lfam>It's not "all or nothing" if you've authorized substitutes. You might build some parts of the dependency graph that aren't available, and use substitutes for the rest
<lfam>We try to make substitutes available for recent commits to our Git repository, but if your version of Guix is too old, we will have probably garbage collected them. We should try to make that tail as long as possible.
<lfam>Yes, I think it's pretty cool, too. The binary substitutes are "referentially transparent" to building from source.
<lfam>The UI typically first tells you what will be built and what will be substituted, but if there are grafts involved, the UI suffers a bit :(
<lfam>And of course, there could be other substitute providers with their own signing key that you would have to authorize. I sometimes use this mechanism to transfer substitutes of private packages from my fast computer to my slow computer.
<dpg23>That would be useful. Ideally I'd like my server to build for my laptop.
<sneek>civodul, dsmith says: Are there any continuous integration servers for guile? For guix?
<sneek>civodul, jlicht says: it seems that if I want to include the (json) module in e.g. (guix build node-build-system), it will be part of the module-import derivation either way because of the modules that are imported by default via build-expression->derivation
<anthk_>gnome shell extension plugin is missing in both icecat and epiphany (Gnome Web)
<lfam>If you can use that key to connect to other servers, then it should be possible to make it work. I think that our project admins have to manually approve that key for access to the repo. I'm not sure who that is, but I'd guess it's the names that are underlined here: http://savannah.gnu.org/project/memberlist.php?group=guix
<lfam>By the way, my personal method is to use a separate SSH key for Savannah, and to keep a strong passphrase on it. Since other people run code from the repo, I feel a strong responsibility to protect access to it.
<kyamashita>I'll see about it a bit later. For now I have to go, but I'll be back later.
<mark_weaver_alt>well, I wanted to verify that grafting worked properly before pushing it, but I found that there were problems. and then I found that the same problems seem to exist without my patch too, but anyway that's why I got stuck.
<lfam>Ah, that's always a discouraging turn of events