[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Guix custom channel and gnupg update
From: |
Michael Dahlberg |
Subject: |
Guix custom channel and gnupg update |
Date: |
Wed, 20 Nov 2024 17:39:45 +0000 |
Hello:
After spending a considerable amount of time researching Guix, I decided to
finally make the jump and install in on my main system. My first pain point
that I came across was when I needed access to my password-store and found out
after a few terrifying hours that my keys are from gpg ver. 2.4.x and Guix only
has available gnupg 2.2.39, which is unable to read these keys.
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.
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
the only version of gnupg that is available to me is the 2.2.39 from
%default-channels
My channel introduction is correct, although my commits are signed with my gpg
2.4.x key. The ascii-armor version of my public key is contained in the
origin/keyring branch.
So, I've run out of things to check as to why my package definitions are not
being built when I do a
guix pull
and why I'm not seeing them listed in the available list of packages.
I'm open to any troubleshooting suggestions or places to look for errors. Also,
if it would be of benefit to see any of my scheme files, I'm happy to provide
them.
Thanks VERY MUCH!
Mike
- Guix custom channel and gnupg update,
Michael Dahlberg <=