Re: Recovering from broken Guix due to GC'd derivations
On Mon, Jun 11, 2018 at 13:08:52 +0200, Ludovic Courtès wrote: > Hmm weird. Did you try running ‘guix gc --verify’? I don’t see how one > could end up in such a state, unless there’s some hard disk corruption > or something. That did it. It removed 83 packages, and pulling now works. Thank you! I'm sorry that I can't provide more information. -- Mike Gerwitz Free Software Hacker+Activist | GNU Maintainer & Volunteer GPG: D6E9 B930 028A 6C38 F43B 2388 FEF6 3574 5E6F 6D05 https://mikegerwitz.com signature.asc Description: PGP signature
Re: root certificate
On 06/11/2018 at 12:59 Joshua Branson writes: > Divan Santana writes: > >> Hi Guix :) >> >> How does one import a root certificate for GuixSD? > > This probably isn't helpful, but what is a root certificate? > >> >> I didn't see it in the manual. >> >> (Hopefully I didn't miss it. I need to read up on using info within Emacs >> better.) >> -- >> Divan Hello Divan, If you want to a bundle of standard CA certificates install "nss-certs". It is probably already be installed as a system package since most of the example GuixSd configs include it. But I have encountered at least one situation where I needed to also install in as a user package, e.g. 'guix package -i nss-certs'. For details please see ... (guix) Application Setup ... or ... https://www.gnu.org/software/guix/manual/guix.html HTH - George
Re: root certificate
Divan Santana writes: > Hi Guix :) > > How does one import a root certificate for GuixSD? This probably isn't helpful, but what is a root certificate? > > I didn't see it in the manual. > > (Hopefully I didn't miss it. I need to read up on using info within Emacs > better.) > -- > Divan
root certificate
Hi Guix :) How does one import a root certificate for GuixSD? I didn't see it in the manual. (Hopefully I didn't miss it. I need to read up on using info within Emacs better.) -- Divan
Re: Confusion around the new `guix pull'
> > One way to look at it is that ‘guix pull’ provides an up-to-date Guix > (sans guix-daemon). Conversely, the package in ~root/.guix-profile is a > fixed snapshot of Guix. We update the ‘guix’ package in Guix from time > to time, and you can upgrade it that way, but basically normal users > should only care about ~/.config/guix/current. > > HTH! > > Ludo’. Thanks for the explanation, that clears things up. :)
Re: Confusion around the new `guix pull'
Hello, Fis Trivial skribis: > * Is it ok to remove /usr/local/bin/guix ? It’s OK to remove this symlink *if* all your users have already populated ~/.config/guix/current. > Now the new guix command is resided in ~/.config/guix/current, is the > old one (linked from /root/.guix-profile/bin/guix manually) still > needed? I don't have any other users other than root and my current user > needs to use it. The old one is still needed for root because it provides ‘guix-daemon’, which ‘guix pull’ doesn’t build currently. (In the future ‘guix pull’ will provide ~/.config/guix/current/bin/guix-daemon, and at that point the old one can be removed altogether.) Regardless, ~/.config/guix/current/bin should come first in $PATH so that you get to run the latest ‘guix’ command. > Or, as a normal user(non-root), is there any different between using the > one linked at installation time (the one from root's profile) and the > one from $HOME/.config/guix/bin? Users should use ~/.config/guix/current/bin/guix because it’s going to be up-to-date, whereas /usr/local/bin/guix may remain old. > * What's the different for ~/.guix-profile/bin/guix and > ~/.config/guix/current/bin/guix for root user account. The latter can be upgraded anytime by running ‘guix pull’; the former cannot be upgraded. > As a root user, there are two guix command now, as shown in the question > title. > > Which one should I use? > > What are the differences? > > Is there a right way to remove the duplication? > > > Or is there a section of documentation that explains the relationship > between the `guix' in /root/.guix-profile/bin and one in > /root/.config/guix/current/bin? I didn't found it, but if there is one, > please point me to it. One way to look at it is that ‘guix pull’ provides an up-to-date Guix (sans guix-daemon). Conversely, the package in ~root/.guix-profile is a fixed snapshot of Guix. We update the ‘guix’ package in Guix from time to time, and you can upgrade it that way, but basically normal users should only care about ~/.config/guix/current. HTH! Ludo’.
Re: Recovering from broken Guix due to GC'd derivations
Hi Mike, Mike Gerwitz skribis: > On Sun, Jun 10, 2018 at 18:45:19 +0200, Ludovic Courtès wrote: >> Hello Mike, >> >> Mike Gerwitz skribis: >> >>> Any pull or package install operations that I attempt give me an error >>> like this (the exact derivation varies between my user and root, but >>> they're both Perl): >>> >>> guix pull: error: open-file: No such file or directory: >>> "/gnu/store/fq9583a3w3is0r1yrjxg1znfz2qkvg78-perl-5.26.2.tar.xz.drv" >> >> This cannot happen under normal circumstances, as we say. Could it be >> that you run a Guix configured with a different ‘localstatedir’ than the >> original one that populated /gnu/store? > > I've never done anything other than a normal `guix pull`. When I was > working on the `guix environment` changes for containers months ago, I > was using `pre-inst-env', but nothing other than that. I didn't provide > any options to `configure' or anything change any other env vars. > > Since before March, I've just been using a vanilla guix (rather than my > local git checkout). Hmm weird. Did you try running ‘guix gc --verify’? I don’t see how one could end up in such a state, unless there’s some hard disk corruption or something. Ludo’.
