Hi Diego,
Diego Nicola Barbato skribis:
>> Thanks for the heads-up. Commit
>> 3bbd6919bd84b76686d1aa626ba861faf3fc8ceb changes ‘guix pull’ to display
>> a hint in this case.
>>
>> Ludo’.
>
> I just tried to check if this worked. I installed GuixSD in a VM (with
> the 0.16.0 installer),
Hello Ludo,
Sorry to bother you with this again.
Ludovic Courtès writes:
[...]
>
> Thanks for the heads-up. Commit
> 3bbd6919bd84b76686d1aa626ba861faf3fc8ceb changes ‘guix pull’ to display
> a hint in this case.
>
> Ludo’.
I just tried to check if this worked. I installed GuixSD in a VM
Hi Diego,
Diego Nicola Barbato skribis:
> Ludovic Courtès writes:
>
>> Diego Nicola Barbato skribis:
>>
>>> Ludovic Courtès writes:
>>
>> [...]
>>
In addition, be aware that Bash maintains a cache of commands it looked
up in $PATH. Thus it may be that, say, it had cached that
On 2018-12-19 20:27, Tobias Geerinckx-Rice wrote:
swedebugia wrote:
egil@parabola:~$ time hash pacman
real 0m0,000s
user 0m0,000s
sys 0m0,000s
So it won't and any measuable overhead to just call this in the end of
guix package after updating the symlinks to the new profile
swedebugia wrote:
egil@parabola:~$ time hash pacman
real0m0,000s
user0m0,000s
sys 0m0,000s
So it won't and any measuable overhead to just call this in the
end of
guix package after updating the symlinks to the new profile
generation.
Do you mean to put something like
guix() {
On 2018-12-19 13:49, Diego Nicola Barbato wrote:
Hello,
Ludovic Courtès writes:
Diego Nicola Barbato skribis:
Ludovic Courtès writes:
[...]
In addition, be aware that Bash maintains a cache of commands it looked
up in $PATH. Thus it may be that, say, it had cached that ‘guix’ is
Hello,
Ludovic Courtès writes:
> Diego Nicola Barbato skribis:
>
>> Ludovic Courtès writes:
>
> [...]
>
>>> In addition, be aware that Bash maintains a cache of commands it looked
>>> up in $PATH. Thus it may be that, say, it had cached that ‘guix’ is
>>> really
Hi,
Diego Nicola Barbato skribis:
> Ludovic Courtès writes:
[...]
>> In addition, be aware that Bash maintains a cache of commands it looked
>> up in $PATH. Thus it may be that, say, it had cached that ‘guix’ is
>> really /run/current-system/profile/bin/guix. When you pulled, it didn’t
>>
On Fri, 07 Dec 2018 09:36:31 +0100
Diego Nicola Barbato wrote:
> I believe this is it. This also explains why ‘which guix’ returned
> the updated guix while ‘guix --version’ claimed it was still the older
> version, which I found rather confusing.
> I am afraid being unaware of this has led me
Hello,
Ludovic Courtès writes:
> Hello,
>
> Ricardo Wurmus skribis:
>
>>> Hello Guix,
>>>
>>> The first time a user runs ‘guix pull’ after a fresh install it does not
>>> seem to update guix. ‘guix --version’ reports that guix is still
>>> version 0.15.0 after running ‘guix pull’, instead of
Hello,
Ricardo Wurmus skribis:
>> Hello Guix,
>>
>> The first time a user runs ‘guix pull’ after a fresh install it does not
>> seem to update guix. ‘guix --version’ reports that guix is still
>> version 0.15.0 after running ‘guix pull’, instead of showing the hash of
>> the latest commit.
>
>
Hello Ricardo,
Thank you for the prompt reply.
Ricardo Wurmus writes:
> Hi Diego,
>
>> Hello Guix,
>>
>> The first time a user runs ‘guix pull’ after a fresh install it does not
>> seem to update guix. ‘guix --version’ reports that guix is still
>> version 0.15.0 after running ‘guix pull’,
Hello Guix,
The first time a user runs ‘guix pull’ after a fresh install it does not
seem to update guix. ‘guix --version’ reports that guix is still
version 0.15.0 after running ‘guix pull’, instead of showing the hash of
the latest commit.
This can be mitigated by logging out and back in,
13 matches
Mail list logo
