unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Zheng Junjie <zhengjunjie@iscas.ac.cn>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 75180@debbugs.gnu.org
Subject: [bug#75180] Request for merging "libgcrypt-gpg-update" branch
Date: Mon, 30 Dec 2024 16:48:18 +0800	[thread overview]
Message-ID: <87h66lsgj1.fsf@iscas.ac.cn> (raw)
In-Reply-To: <871pxqr002.fsf@inria.fr> ("Ludovic Courtès"'s message of "Sun, 29 Dec 2024 16:18:21 +0100")

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

Ludovic Courtès <ludo@gnu.org> writes:

> Hello,
>
> (This time sent to guix-patches…)
>
> I’d like to merge the ‘libgcrypt-gpg-update’ branch.
>
> It is partially built at
> <https://ci.guix.gnu.org/jobset/security-updates> for x86_64-linux and
> i686-linux (partially only because that’s via the “-full-upgrade”
> jobs,
> which include additional upgrades).
>
> It’s fairly trivial and safe but expensive (‘cmake-minimal’ depends on
> libgcrypt).
>
>   04673f8d50 gnu: gpgme: Update to 1.24.1.

I include gpgme-1.23 qgpgme-qt6-1.23 for kde-pim, which we need to
delete them now. And add qgpgme-qt6@1.24.1 for kde-pim.

>   458b9b649b gnu: gnupg: Update to 2.5.2.
>   469bac1546 gnu: npth: Update to 1.8.
>   d51e56f7e4 gnu: libksba: Update to 1.6.7.
>   22dc97b670 gnu: libassuan: Update to 3.0.1.

see https://dev.gnupg.org/T5911, libassuan remove Pth support. so we
should also remove pth from propagated-inputs.

>   7e989b4ca8 gnu: libgcrypt: Update to 1.11.0.
>   74c937a7f3 gnu: libgpg-error: Update to 1.51.
>
> Ludo’.

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

      reply	other threads:[~2024-12-30  8:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-29 15:18 [bug#75180] Request for merging "libgcrypt-gpg-update" branch Ludovic Courtès
2024-12-30  8:48 ` Zheng Junjie [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=87h66lsgj1.fsf@iscas.ac.cn \
    --to=zhengjunjie@iscas.ac.cn \
    --cc=75180@debbugs.gnu.org \
    --cc=ludo@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.
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).