From: Saku Laesvuori <saku@laesvuori.fi>
To: Michael Dahlberg <dahlberg@recursoft.org>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Guix custom channel and gnupg update
Date: Thu, 21 Nov 2024 19:41:07 +0200 [thread overview]
Message-ID: <hjykgwv5it44hcbcs6jmaxeuqe3p6hpgg627vehkylt5mbjyyi@4unk6ydjf75a> (raw)
In-Reply-To: <167kvJ0arG3-j8uSR1zdERM9PdiCYofOhKn5CuuYMO2oJWHqVulSFfOfWQ3hZGT3iQwTJ1B4-Sv4JQ1E2htjYIyVpVU-Jy3rc9036d7Cc20=@recursoft.org>
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
> I decided to create a custom channel that includes the latest version
> of gnupg and its dependent libraries. To do this I used the gnupg.scm
> file from Guix as a template but modified the versions and hashes of
> the relevant package definitions. I then used my gnupg.scm file and
> did a test build and was able to successfully build the latest version
> of gnupg, and its libraries.
Have you renamed the module defined in your copy of gnupg.scm? If it is
still (gnu packages gnupg) it will probably be shadowed by the module in
base guix.
> I then created a signed git repo with the custom channel and included
> it in my ~/.config/guix/channels.scm. A guix pull recognizes my
> channel and apparently everything is signed as it should be since it
> seems to be pulled in without errors. However, when I then run
>
> guix show gnupg
> or
> guix package --list-available | grep gnupg
Have you checked that the guix command you are using is not the system
default (/run/current-system/profile/bin/guix)? Normally it isn't, but
it could have kept it if you were using it before the pull. If this is
the case, it should get fixed just by logging out and back in.
If these don't help you could try running
guix shell -e '(@ (your channel gnupg module) gnupg-variable-name)'
replacing the module and variable name with correct values. This should
either bring the updated gnupg package into a temporary shell session or
give an error that we can use to debug further.
- Saku
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-11-21 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 17:39 Guix custom channel and gnupg update Michael Dahlberg
2024-11-21 17:41 ` Saku Laesvuori [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=hjykgwv5it44hcbcs6jmaxeuqe3p6hpgg627vehkylt5mbjyyi@4unk6ydjf75a \
--to=saku@laesvuori.fi \
--cc=dahlberg@recursoft.org \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).