Hello,
swedebugia skribis:
> This whole update to guix pull was somewhat a breaking change, but
> unfortunately it was very hard to imagine the repercussions (horrible
> bugs) down the line...
>
> Could it have been completely avoided by introducing it as such and
> forced people to reinstall/up
Hi
On 2018-10-17 11:17, Konrad Hinsen wrote:
Lesson learned: avoid messing around with mutable state. How about
creating a functional package manager? ;-)
LOL
This whole update to guix pull was somewhat a breaking change, but
unfortunately it was very hard to imagine the repercussions (horr
Konrad Hinsen skribis:
>> To work around it, you can pull from an older generation, along these
>> lines:
>>
>> ~/.config/guix/current-42-link/bin/guix pull
>>
>> (This will work because this older guix won’t attempt to move your
>> generations to /var/guix/profiles, so it allows you to “jump o
Hi Ludo,
> To work around it, you can pull from an older generation, along these
> lines:
>
> ~/.config/guix/current-42-link/bin/guix pull
>
> (This will work because this older guix won’t attempt to move your
> generations to /var/guix/profiles, so it allows you to “jump over” the
> bug.)
>
> L
Hello Konrad,
Konrad Hinsen skribis:
> But there still seems to be some collateral damage, since I could not
> use "guix pull" any more on my standard user account:
>
> $ guix pull
> Migrating profile generations to '/var/guix/profiles/per-user/hinsen'...
> guix pull: error: rename-file: I
Hi Ludo,
> If you’re familiar with Dired in Emacs, I’d suggest opening
> /var/guix/profiles/per-user/root and fixing the symlink targets from
> there (with C-c C-q).
Done. And after rebooting, guix seems to work fine for root, including
the download phase. Meaning that I consider this bug fixed.
Hi Konrad,
Konrad Hinsen skribis:
> This looks like an error in an error-raising procedure, something
> like a meta-error ;-)
The horror bug department worked hard to deliver this one. :-)
> Looking at
>
> ~# ls -l /var/guix/profiles/per-user/root/current-guix
> lrwxrwxrwx 1 root root 1
Hi Ludo,
Hmm you might need to run, say, ‘guix pull -l’, to make this script
magically appear. :-)
Concretely, the new ‘guix pull’ migrates things from ~/.config/guix to
/var/guix/profiles the first time you run it, but it may be that you
haven’t yet run the *new* ‘guix pull’.
That looks lik
On Thu, Oct 11, 2018 at 06:32:20PM +0200, Ludovic Courtès wrote:
> Hi there!
>
> I believe commit ed9d7cb4d95f8f4776e6fee2778ab52bc2852969 fixes it.
>
> That is, if you run ‘guix pull’ as root and then start
> ~/.config/guix/current/bin/guix-daemon, everything should be fine.
It works on one pro
Hello,
Konrad Hinsen skribis:
>> I believe commit ed9d7cb4d95f8f4776e6fee2778ab52bc2852969 fixes it.
>>
>> That is, if you run ‘guix pull’ as root and then start
>> ~/.config/guix/current/bin/guix-daemon, everything should be fine.
> Let's say the bug seems to be elsewhere now ;-)
>
> When I try
Hi Ludo,
I believe commit ed9d7cb4d95f8f4776e6fee2778ab52bc2852969 fixes it.
That is, if you run ‘guix pull’ as root and then start
~/.config/guix/current/bin/guix-daemon, everything should be fine.
Let's say the bug seems to be elsewhere now ;-)
When I try to build something after following y
Hi there!
I believe commit ed9d7cb4d95f8f4776e6fee2778ab52bc2852969 fixes it.
That is, if you run ‘guix pull’ as root and then start
~/.config/guix/current/bin/guix-daemon, everything should be fine.
Thanks,
Ludo’.
Pjotr Prins skribis:
> On Tue, Sep 11, 2018 at 03:23:13PM +0200, Pjotr Prins wrote:
>> On Tue, Sep 11, 2018 at 12:12:15PM +0200, Ludovic Courtès wrote:
>> > The download process is running as a build user, not as root, hence the
>> > permission issue (silly me!).
>> >
>> > Now we need to find a
Pjotr Prins skribis:
> On Tue, Sep 11, 2018 at 12:12:15PM +0200, Ludovic Courtès wrote:
>> The download process is running as a build user, not as root, hence the
>> permission issue (silly me!).
>>
>> Now we need to find a way to use ‘guix’ from root’s
>> ~/.config/guix/current. A solution may
On Tue, Sep 11, 2018 at 03:23:13PM +0200, Pjotr Prins wrote:
> On Tue, Sep 11, 2018 at 12:12:15PM +0200, Ludovic Courtès wrote:
> > The download process is running as a build user, not as root, hence the
> > permission issue (silly me!).
> >
> > Now we need to find a way to use ‘guix’ from root’s
On Tue, Sep 11, 2018 at 12:12:15PM +0200, Ludovic Courtès wrote:
> The download process is running as a build user, not as root, hence the
> permission issue (silly me!).
>
> Now we need to find a way to use ‘guix’ from root’s
> ~/.config/guix/current. A solution may be to expose that profile und
Hi Konrad,
Konrad Hinsen skribis:
>> Specifically, you’d have to run something along these lines as root:
>>
>> strace -f -p $(pidof guix-daemon) -o log
>>
>> and then, as root or non-root (it doesn’t matter), run, say:
>>
>> guix build curl -S --no-substitutes
>
> The log file (compressed)
Hi Ludo,
> I don’t think you’re doing anything wrong. Could anyone of you who
> experience this problem strace guix-daemon? I’ve thought about this and
> don’t understand where that EACCES (“Permission denied”) comes from.
>
> Specifically, you’d have to run something along these lines as root:
Hello,
Pjotr Prins skribis:
> guix pull
>
> Updating channel 'guix' from Git repository at
> 'https://git.savannah.gnu.org/git/guix.git'...
> Building from this channel:
> guix https://git.savannah.gnu.org/git/guix.git 91cc2a3
> guile: warning: failed to
It is working now. After a guix pull I did a guix package -i guix in a
new profile. Restarting the daemon from there it stopped complaining!
I don't know why the deamon from guix pull straight was not working,
but at least guix is building again.
Pj.
Dear Ludo,
If I understand 'guix pull' correctly below should simply not be
possible, right? I mean, once you do a guix pull you have the latest
and the greatest and there should be no interference? Intriguingly
this does not happen on all my systems, just on 2 - notably my laptop
I am using in So
On Sun, Sep 02, 2018 at 10:04:32PM +0200, Ludovic Courtès wrote:
> OK. Do reopen it if it shows up again.
Just to report that I did a successful install on one of those
machines. Starting with a 0.14 guix as root
guix pull
restarted daemon using the new one in /root/.config/current/bin/
swit
Hi,
Pjotr Prins skribis:
> On Sun, Sep 02, 2018 at 03:55:06PM +0200, Ludovic Courtès wrote:
>> Hi Pjotr,
>>
>> What was the outcome of this bug?
>>
>> https://bugs.gnu.org/32183
>>
>> If it wasn’t resolved, could you answer the questions below?
>
> I still face this problem on one or two ma
On Sun, Sep 02, 2018 at 03:55:06PM +0200, Ludovic Courtès wrote:
> Hi Pjotr,
>
> What was the outcome of this bug?
>
> https://bugs.gnu.org/32183
>
> If it wasn’t resolved, could you answer the questions below?
I still face this problem on one or two machines. I am running a
standard setup. N
Hi Pjotr,
What was the outcome of this bug?
https://bugs.gnu.org/32183
If it wasn’t resolved, could you answer the questions below?
Thanks in advance!
Ludo’.
l...@gnu.org (Ludovic Courtès) skribis:
> Hi Pjotr,
>
> Pjotr Prins skribis:
>
>> Not completely sorted. Not sure what is going wro
Hi Pjotr,
Pjotr Prins skribis:
> Not completely sorted. Not sure what is going wrong but now starting
> with guix 0.14 daemon and client and running guix pull a few times
> successfully, running guix-daemon from $HOME/.config/guix/current/bin
> and guix from a fresh git checkout using ./pre-inst
Not completely sorted. Not sure what is going wrong but now starting
with guix 0.14 daemon and client and running guix pull a few times
successfully, running guix-daemon from $HOME/.config/guix/current/bin
and guix from a fresh git checkout using ./pre-inst-env guix I get
substitute:
/gnu/store/x
Leo Famulari skribis:
> On Tue, Jul 17, 2018 at 10:55:41AM +0200, Pjotr Prins wrote:
>> > > Fails to build with below
>> > > /gnu/store/8ahlc84zaj0iw9jpsdpa9wx4ms0s9cma-guix-daemon-0.15.0-1.4876bc8/libexec/guix/download:
>> > > line 8: /root/.config/current/bin/guix: Permission denied
>
> There
28 matches
Mail list logo
