From: zimoun <zimon.toutoune@gmail.com>
To: Christopher Baines <mail@cbaines.net>, 58775@debbugs.gnu.org
Subject: [bug#58775] [PATCH] WIP build python-gpg from gpgme
Date: Sat, 26 Nov 2022 14:08:21 +0100 [thread overview]
Message-ID: <86r0xpc18a.fsf@gmail.com> (raw)
In-Reply-To: <20221025121439.18746-1-mail@cbaines.net>
Hi Chris,
On Tue, 25 Oct 2022 at 13:14, Christopher Baines <mail@cbaines.net> wrote:
> The python-gpg package using PyPI source code seems out of date, and doesn't
> build on 32bit systems like i686-linux and armhf-linux. Maybe we should use
> the source from gpgme?
You mean, instead of ’inherit’ from ’gpgme’, right?
Well, the current version on PyPI is 1.10.0 and the ’gpgme’ is 1.15.1.
> ---
> gnu/packages/gnupg.scm | 48 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
>
> diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm
> index ce9ef48796..3a8be9a544 100644
> --- a/gnu/packages/gnupg.scm
> +++ b/gnu/packages/gnupg.scm
> @@ -431,6 +431,54 @@ (define-public gpgme
> (properties '((ftp-server . "ftp.gnupg.org")
> (ftp-directory . "/gcrypt/gpgme")))))
>
> +(define-public python-gpg-latest
Why the symbol is ’-latest’?
> + (package
> + (inherit gpgme)
> + (name "python-gpg")
when the name is not? And ’gpgme’ neither.
Well, I propose to use this updated version using ’gpgme’ and drop the
old package from PyPI if all the dependencies,
--8<---------------cut here---------------start------------->8---
$ guix refresh -l python-gpg
Building the following 9 packages would ensure 14 dependent packages are rebuilt: alot@0.10 gajim-openpgp@1.4.9 assword@0.11 linuxdcpp@1.1.0 ikiwiki@3.20200202.3 xandikos@0.2.3 python-oslosphinx@4.18.0 websockify@0.8.0 breezy@3.2.2
--8<---------------cut here---------------end--------------->8---
build fine. WDYT?
Cheers,
simon
prev parent reply other threads:[~2022-11-26 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 12:14 [bug#58775] [PATCH] WIP build python-gpg from gpgme Christopher Baines
2022-11-26 13:08 ` zimoun [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=86r0xpc18a.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=58775@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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.
Code repositories for project(s) associated with this public 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).