Efraim Flashner schreef op di 11-01-2022 om 15:46 [+0200]:
> guix package: error:   first entry:
> gnupg@2.2.30 /gnu/store/0snfzd41n430ddpq316j9v2z5fn2y62m-gnupg-2.2.30
> guix package: error:    ... propagated from emacs-shroud@1.105
> guix package: error:   second entry:
> gnupg@2.2.32 /gnu/store/75122spwjdkxxgd32gkkil3n7ifax8i5-gnupg-2.2.32
> guix package: error:    ... propagated from
> emacs-pinentry@0.1-1.dcc9ba0
> hint: Try upgrading both `emacs-shroud' and `emacs-pinentry', or
> remove one of them from the profile.
> ```
> 
> Note, that while the above error message is complaining about
> emacs-pinentry, it still barfs even if I remove emacs-pinentry and
> just
> install gnupg directly since the current gnupg is 2.2.32.
> 
> Can whoever is maintaining the emacs-shroud package please update it
> to
> gnupg@2.2.32, so it can be installed again?

Instead of working around the limitations of propagation, why not
unpropagate?

I took a look at emacs-shroud's source code, and I don't see it calling
gnupg anywhere, so maybe propagating gnupg from emacs-shroud isn't
necessary?  The dependency 'shroud' hardcodes the GPG binary location,
so I don't see why 'gpg' was included in 'propagated-inputs'. 

I made the following change in emacs-shroud

    (propagated-inputs
     (list emacs-bui
           emacs-dash
           emacs-f
           emacs-s
           #;gnupg ;; <--- changed line
           shroud)),

set ~/.shroud according to https://dthompson.us/projects/shroud.html

ran "./pre-inst-env guix shell --pure emacs shroud emacs-shroud -- emacs"
and evaluated the following S-exps:
(require 'shroud) ;; why is this required? e.g. emacs-magit
(shroud--init)    ;; require things like this.

Then did "M-x shroud-bui" but nothing happened (a bug?),
so I couldn't test the change.