unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
* bug#53187: emacs-shroud propagates the wrong gnupg
@ 2022-01-11 13:46 Efraim Flashner
  2022-01-11 15:15 ` Maxime Devos
  0 siblings, 1 reply; 2+ messages in thread
From: Efraim Flashner @ 2022-01-11 13:46 UTC (permalink / raw)
  To: 53187


[-- Attachment #1.1: Type: text/plain, Size: 213 bytes --]


-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #1.2: Type: message/rfc822, Size: 5289 bytes --]

From: Gary Johnson <lambdatronic@disroot.org>
To: help-guix@gnu.org
Subject: emacs-shroud package appears to be out of date
Date: Thu, 06 Jan 2022 11:46:02 -0500
Message-ID: <87ee5kq05e.fsf@disroot.org>

Hi Guix,

During my recent `guix pull` + `guix package -u` adventure, the
emacs-shroud package barfed due to what looks like a hard-coded
reference to an older version of gnupg. I uninstalled it in order to
complete my upgrade. Of course, when I try to reinstall it now, I
continue to get the same version conflict error due to gnupg.

```
gjohnson@euclid ~ $ guix package -i emacs-shroud
The following package will be installed:
   emacs-shroud 1.105

guix package: error: profile contains conflicting entries for gnupg
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?

Thanks,
  Gary

-- 
GPG Key ID: 7BC158ED
Use `gpg --search-keys lambdatronic' to find me
Protect yourself from surveillance: https://emailselfdefense.fsf.org
=======================================================================
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Why is HTML email a security nightmare? See https://useplaintext.email/

Please avoid sending me MS-Office attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#53187: emacs-shroud propagates the wrong gnupg
  2022-01-11 13:46 bug#53187: emacs-shroud propagates the wrong gnupg Efraim Flashner
@ 2022-01-11 15:15 ` Maxime Devos
  0 siblings, 0 replies; 2+ messages in thread
From: Maxime Devos @ 2022-01-11 15:15 UTC (permalink / raw)
  To: Efraim Flashner, 53187

[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]

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.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-01-11 15:18 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-11 13:46 bug#53187: emacs-shroud propagates the wrong gnupg Efraim Flashner
2022-01-11 15:15 ` Maxime Devos

Code repositories for project(s) associated with this inbox:

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).