GNU bug report logs - #75180
Request for merging "libgcrypt-gpg-update" branch

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 75180 in the body.
You can then email your comments to 75180 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: guix-patches <at> gnu.org
Subject: Request for merging "libgcrypt-gpg-update" branch
Date: Sun, 29 Dec 2024 16:18:21 +0100

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.
  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.
  7e989b4ca8 gnu: libgcrypt: Update to 1.11.0.
  74c937a7f3 gnu: libgpg-error: Update to 1.51.

Ludo’.

Message #8 received at 75180 <at> debbugs.gnu.org (full text, mbox):

From: Zheng Junjie <zhengjunjie <at> iscas.ac.cn>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 75180 <at> debbugs.gnu.org
Subject: Re: [bug#75180] Request for merging "libgcrypt-gpg-update" branch
Date: Mon, 30 Dec 2024 16:48:18 +0800

[Message part 1 (text/plain, inline)]

Ludovic Courtès <ludo <at> 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 <at> 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’.

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 75180 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Zheng Junjie <zhengjunjie <at> iscas.ac.cn>
Cc: 75180 <at> debbugs.gnu.org
Subject: Re: [bug#75180] Request for merging "libgcrypt-gpg-update" branch
Date: Sat, 04 Jan 2025 18:57:26 +0100

Hello,

Zheng Junjie <zhengjunjie <at> iscas.ac.cn> skribis:

>>   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 <at> 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.

Good points.  I’ve pushed an update that incorporates those suggestions.

Thanks!

Ludo’.

Message #14 received at 75180 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Zheng Junjie <zhengjunjie <at> iscas.ac.cn>
Cc: Dariqq <dariqq <at> posteo.net>, 75180 <at> debbugs.gnu.org
Subject: Re: bug#75180: Request for merging "libgcrypt-gpg-update" branch
Date: Fri, 10 Jan 2025 22:57:03 +0100

Hello,

I have rebased the branch and it is now about to be built:

  https://ci.guix.gnu.org/jobset/libgcrypt-gpg-update

I also took the liberty to push <https://issues.guix.gnu.org/72751>:
these are safe patches and everything depending on ‘cmake-minimal’ was
going to be rebuilt anyway.

Ludo’.

Message #17 received at 75180 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Zheng Junjie <zhengjunjie <at> iscas.ac.cn>
Cc: Dariqq <dariqq <at> posteo.net>, 75180 <at> debbugs.gnu.org
Subject: Re: bug#75180: Request for merging "libgcrypt-gpg-update" branch
Date: Mon, 13 Jan 2025 09:39:43 +0100

Hi,

Ludovic Courtès <ludo <at> gnu.org> skribis:

> I have rebased the branch and it is now about to be built:
>
>   https://ci.guix.gnu.org/jobset/libgcrypt-gpg-update

I had erroneously upgraded gnupg to 2.5.x, which is the development
version.  Retrying with 2.4.7.

Ludo’.

Message #22 received at 75180-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Zheng Junjie <zhengjunjie <at> iscas.ac.cn>
Cc: Dariqq <dariqq <at> posteo.net>, 75180-done <at> debbugs.gnu.org
Subject: Re: bug#75180: Request for merging "libgcrypt-gpg-update" branch
Date: Tue, 14 Jan 2025 14:16:01 +0100

Pushed:

  d804997897 * gnu: ath9k-firmware: Remove CMAKE_SYSTEM_NAME override.
  ad672d80d7 * build-system: cmake: Rework cross compilation.
  f5fa65b3e9 * gnu: gpgme: Remove 1.23 and update KDE users.
  4593303db7 * gnu: gpgme: Update to 1.24.1.
  64d95c78e3 * gnu: gnupg: Update to 2.4.7.
  f4abe0fc61 * gnu: npth: Update to 1.8.
  0859d612f5 * gnu: libksba: Update to 1.6.7.
  34b8b8febe * gnu: libassuan: Update to 3.0.1.
  0bf3142acb * gnu: libgcrypt: Update to 1.11.0.
  eec2c5d6a7 * gnu: libgpg-error: Update to 1.51.

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.