Re: How to Rescue GuixSD when guile and guix arebroken?

[znavko]

Hello, Ricardo Wurmus!
>
> Oh, you have “guix” installed with Guix…? Could you please show me the
> output of “which guix”? You should be using
> ~/.config/guix/current/bin/guix — that directory should be first on
> PATH, and you probably shouldn’t install the “guix” package itself,
> because it will necessarily be older than the version of Guix you used
> to install it.
>



# which guix
/root/.config/guix/current/bin/guix
# echo $PATH
/root/.config/guix/current/bin:/root/.guix-profile/bin:/root/.guix-profile/sbin:/root/.guix-profile/bin:/run/setuid-programs:/run/current-system/profile/bin:/run/current-system/profile/sbin

So, I can run `guix pull` ?
One more question. Often I have troubles that installed by root packages are 
not visible for root. I think this is because of PATH. So I have added this to 
/root/.bashrc , as these instructions appeared while I run `guix package -i 
ATOM` :

# tail -n 6 /root/.bashrc

# my
export PATH="/root/.guix-profile/bin${PATH:+:}$PATH"
export PATH="/root/.guix-profile/bin:/root/.guix-profile/sbin${PATH:+:}$PATH"
export PATH="/root/.config/guix/current/bin${PATH:+:}$PATH"

Is it right way? Does it work, when I run `su`?


PS. Hope my mail will not appear in Maillist archive.

Re: How to Rescue GuixSD when guile and guix arebroken?

[Ricardo Wurmus]

znavko  writes:

>> If you don’t have this you are likely upgrading from an old version of
>> Guix before that change was made. In that case you need to upgrade to a
>> version of Guix that has a guile-gcrypt package, then install it, and
>> only then run “guix pull”.
>
> I have that bin directory:
>
> # cd ~/.config/guix/current/bin/
> ~/.config/guix/current/bin# ls
> guix  guix-daemon
>
> And I have no upgrades for guix. As I thought before upgrading process is 
> `guix pull && guix package -u ATOM`
>
> # guix package -u guix

Oh, you have “guix” installed with Guix…?  Could you please show me the
output of “which guix”?  You should be using
~/.config/guix/current/bin/guix — that directory should be first on
PATH, and you probably shouldn’t install the “guix” package itself,
because it will necessarily be older than the version of Guix you used
to install it.

--
Ricardo

Re: How to Rescue GuixSD when guile and guix arebroken?

[znavko]

Thank you, Ricardo Wurmus, for these exact instructions.

> If you don’t have this you are likely upgrading from an old version of
> Guix before that change was made. In that case you need to upgrade to a
> version of Guix that has a guile-gcrypt package, then install it, and
> only then run “guix pull”.

I have that bin directory:

# cd ~/.config/guix/current/bin/
~/.config/guix/current/bin# ls
guix  guix-daemon

And I have no upgrades for guix. As I thought before upgrading process is `guix 
pull && guix package -u ATOM`

# guix package -u guix
# guix --version
guix (GNU Guix) e67ad5532f76b53e955149da2f1e237696ff0893
Copyright (C) 2018 the Guix authors
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.


Did you mean Guix version  67ad5532f76b53e955149da2f1e237696ff0893 that provide 
gcrypt?
Can I run `guix pull` now?


‐‐‐ Original Message ‐‐‐
пятница, сентябрь 21, 2018 4:17 дня, Ricardo Wurmus  пишет:

> Hello,
>
> > Both times, as I think, it happened this way. I run `guix pull`,
> > switch off notebook while it is running (just a mistake) and then I
> > run again `guix pull`, it works, but gives the errors.
>
> The mechanism used by “guix pull” has changed. These errors no longer
> happen with the new mechanism.
>
> > guix gc -R $(readlink -f ~/.config/guix/latest)
> >
> > 
>
> ~/.config/guix/latest is no longer used. Instead “guix pull” installs a
> full self-contained Guix to ~/.config/guix/current/bin/.
>
> If you don’t have this you are likely upgrading from an old version of
> Guix before that change was made. In that case you need to upgrade to a
> version of Guix that has a guile-gcrypt package, then install it, and
> only then run “guix pull”.
>
> With the new mechanism you can simply use any of the older variants of
> Guix you have in ~/.config/guix/current-n-link/bin.
>
> Hope this helps!
>
> --
>
> Ricardo

Re: How to Rescue GuixSD when guile and guix arebroken?

[Ricardo Wurmus]

Hello,

> Both times, as I think, it happened this way. I run `guix pull`,
> switch off notebook while it is running (just a mistake) and then I
> run again `guix pull`, it works, but gives the errors.

The mechanism used by “guix pull” has changed.  These errors no longer
happen with the new mechanism.

> # guix gc -R $(readlink -f ~/.config/guix/latest)

~/.config/guix/latest is no longer used.  Instead “guix pull” installs a
full self-contained Guix to ~/.config/guix/current/bin/.

If you don’t have this you are likely upgrading from an old version of
Guix before that change was made.  In that case you need to upgrade to a
version of Guix that has a guile-gcrypt package, then install it, and
only then run “guix pull”.

With the new mechanism you can simply use any of the older variants of
Guix you have in ~/.config/guix/current-n-link/bin.

Hope this helps!

--
Ricardo

How to Rescue GuixSD when guile and guix arebroken?

[znavko]

Hello! I want to ask novice's question, cause the first I want, having trouble, 
is to re-install GuixSD, but rescue with USB-stick is faster.
I have for second time a bug described here: 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31162
Both times, as I think, it happened this way. I run `guix pull`, switch off 
notebook while it is running (just a mistake) and then I run again `guix pull`, 
it works, but gives the errors.
Here it is log I copied from terminal: https://pastebin.com/7c06ER7v
Guix is not working at all.

# guix gc -R $(readlink -f ~/.config/guix/latest)
Backtrace:
In ice-9/boot-9.scm:
   222:17 19 (map1 (((guix store)) ((guix monads)) ((guix #)) ((…)) …))
  2788:17 18 (resolve-interface (guix store) #:select _ #:hide _ # _ …)
  2714:10 17 (_ (guix store) _ _ #:ensure _)
  2982:16 16 (try-module-autoload _ _)
   2312:4 15 (save-module-excursion _)
  3002:22 14 (_)
In unknown file:
  13 (primitive-load-path "guix/store" #)
In guix/store.scm:
 20:0 12 (_)
In ice-9/boot-9.scm:
   2862:4 11 (define-module* _ #:filename _ #:pure _ #:version _ # _ …)
  2875:24 10 (_)
   222:29  9 (map1 (((guix utils)) ((guix config)) ((guix #)) ((…)) …))
   222:29  8 (map1 (((guix config)) ((guix memoization)) ((guix …)) …))
   222:29  7 (map1 (((guix memoization)) ((guix serialization)) (#) …))
   222:29  6 (map1 (((guix serialization)) ((guix monads)) ((# #)) …))
   222:29  5 (map1 (((guix monads)) ((guix base16)) ((guix #)) (#) …))
   222:29  4 (map1 (((guix base16)) ((guix base32)) ((gcrypt #)) # …))
   222:29  3 (map1 (((guix base32)) ((gcrypt hash)) ((guix #)) (#) …))
   222:17  2 (map1 (((gcrypt hash)) ((guix profiling)) ((rnrs #)) # …))
   2791:6  1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ …)
In unknown file:
   0 (scm-error misc-error #f "~A ~S" ("no code for modu…" …) …)

ERROR: In procedure scm-error:
no code for module (gcrypt hash)

I reported this bug to Bugs Maillist. But for future want to ask how can I 
rescue broken system booting with GuixSD USB-stick?

Re: Trying to package GIMP Resynthesizer

[Thorsten Wilms]

On 20.09.2018 22:14, Thorsten Wilms wrote:

---
Calling error for procedure 'gimp-procedural-db-proc-info':
Procedure 'plug-in-resynthesizer' not found
---
Traceback (most recent call last):
   File 
"/gnu/store/2l3zsn1fliq5yw6g2wqpivqwkv602c10-gimp-2.10.6/lib/gimp/2.0/python/gimpfu.py", 
line 740, in response

     dialog.res = run_script(params)
   File 
"/gnu/store/2l3zsn1fliq5yw6g2wqpivqwkv602c10-gimp-2.10.6/lib/gimp/2.0/python/gimpfu.py", 
line 361, in run_script

     return apply(function, params)
   File 
"/home/thorwil/.guix-profile/lib/gimp/2.0/plug-ins/plugin-heal-selection.py", 
line 148, in heal_selection
     pdb.plug_in_resynthesizer(timg, tdrawable, 0,0, useBorder, 
work_drawable.ID, -1, -1, 0.0, 0.117, 16, 500)

error: procedure not found
---


I somehow managed to end up with parts in
~/.guix-profile/lib/gimp/2.0/plug-ins
and the rest in
~/.guix-profile/lib/gimp/2.0/plug-ins/plug-ins

After removing, collecting garbage and installing again with "/plug-ins" 
removed from the string manipulation, things work as they should.



--
Thorsten Wilms

thorwil's design for free software:
http://thorwil.wordpress.com/