"guix pull" fails on Trisquel

  • Open
  • quality assurance status badge
Details
2 participants
  • Caleb Herbert
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Caleb Herbert
Severity
normal
C
C
Caleb Herbert wrote on 30 Apr 21:08 +0200
(address . bug-guix@gnu.org)
236db2ef-749f-4322-97c2-9553b50922f3@bluehome.net
Hi Guix,
Should the docs recommend against using packaged versions of Guix on
foreign distros?
I installed Guix with the Trisquel package. When I ran "guix pull", it
failed and told me to post the output here. I've attached the
transcript of my terminal session with "guix pull" on Trisquel.
I tried doing "apt purge guix" and installing Guix using the installer
script, but the script "detected" an already-existing Guix installation.
I guess "apt purge" didn't really "purge" enough.
I'm now unable to install Guix in a way that will let me pull.
--
Caleb S. Herbert
M
M
Maxim Cournoyer wrote on 1 May 18:34 +0200
(name . Caleb Herbert)(address . csh@bluehome.net)(address . 70681@debbugs.gnu.org)
87y18t7apl.fsf@gmail.com
Hi Caleb,

Caleb Herbert <csh@bluehome.net> writes:

Toggle quote (15 lines)
> Hi Guix,
>
> Should the docs recommend against using packaged versions of Guix on
> foreign distros?
>
> I installed Guix with the Trisquel package. When I ran "guix pull",
> it failed and told me to post the output here. I've attached the
> transcript of my terminal session with "guix pull" on Trisquel.
>
> I tried doing "apt purge guix" and installing Guix using the installer
> script, but the script "detected" an already-existing Guix
> installation. I guess "apt purge" didn't really "purge" enough.
>
> I'm now unable to install Guix in a way that will let me pull.

A workaround would look like:

# rm -rf /var/guix /gnu

Then try the guix-install script again. There's also an undocumented
variable to "overwrite" the current installation; consult the script if
you want to use that.

--
Thanks,
Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 70681@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 70681
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch