Hi Maxime,
Maxime Devos skribis:
> Grigory Shepelev schreef op zo 30-01-2022 om 22:45 [+0300]:
>> Seems like the problem was in my .gitconfig file where "autocrlf =
>> true". I set it to "false", and cleared the cache. Then the "guix
>> pull" started to work as expected.
>
> According to
>
Grigory Shepelev schreef op ma 31-01-2022 om 15:48 [+0300]:
> The issue can be closed I guess. Thanks for your assistance.
> пн, 31 янв. 2022 г. в 00:06, Maxime Devos :
> > Grigory Shepelev schreef op zo 30-01-2022 om 22:45 [+0300]:
> > > Seems like the problem was in my .gitconfig file where
The issue can be closed I guess. Thanks for your assistance.
пн, 31 янв. 2022 г. в 00:06, Maxime Devos :
> Grigory Shepelev schreef op zo 30-01-2022 om 22:45 [+0300]:
> > Seems like the problem was in my .gitconfig file where "autocrlf =
> > true". I set it to "false", and cleared the cache.
Grigory Shepelev schreef op zo 30-01-2022 om 22:45 [+0300]:
> Seems like the problem was in my .gitconfig file where "autocrlf =
> true". I set it to "false", and cleared the cache. Then the "guix
> pull" started to work as expected.
According to
Seems like the problem was in my .gitconfig file where "autocrlf = true". I
set it to "false", and cleared the cache. Then the "guix pull" started to
work as expected.
I don't even remember why I had to get into "git's guts". Something like:
had some problem with some exact project where my
That explains why the problem was raised on my desktop PC as well. It uses
the same .gitconfig file.
вс, 30 янв. 2022 г. в 22:45, Grigory Shepelev :
> Seems like the problem was in my .gitconfig file where "autocrlf = true".
> I set it to "false", and cleared the cache. Then the "guix pull"
Hi,
Grigory Shepelev skribis:
> shegeley@zone51 ~$ guix pull
> Updating channel 'nonguix' from Git repository at
> 'https://gitlab.com/nonguix/nonguix'...
> Updating channel 'guix' from Git repository at
> 'https://git.savannah.gnu.org/git/guix.git'...
> Building from these channels:
> guix
