GNU bug report logs - #72851
[PATCH] gnu: pidgin: Update to 2.14.13 [security fixes].

Previous Next

Full log

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

From: Dariqq <dariqq <at> posteo.net>
To: Liliana Marie Prikler <liliana.prikler <at> gmail.com>, 72851 <at> debbugs.gnu.org
Cc: me <at> tobias.gr
Subject: Re: [PATCH] gnu: pidgin: Update to 2.14.13 [security fixes].
Date: Wed, 28 Aug 2024 20:01:15 +0000

Hi Liliana,

On 28.08.24 20:35, Liliana Marie Prikler wrote:
> Am Mittwoch, dem 28.08.2024 um 07:41 +0000 schrieb Dariqq:
>> The 2.14.9 update fixes CVE-2022-26491.
>>
>> Cleanup leftovers from 89f4f0baa9ff956ba0efe9ec20e1805f01230a54.
>>
>> * gnu/packages/messaging.scm (pidgin): Update to 2.14.13.
>> [source]: Switch to bz2 compression.
>> [snippet]: Remove.
> Why?
>> [native-inputs]: Remove autoconf, automake and libtool.
> Again, why?
> 
bz2 change: Default for the source download on the pidgin website and is 
what guix refresh fetched for me.


THe snippet was needed for an older patch (touching configure.ac) which 
got removed in commit 89f4f0baa9ff956ba0efe9ec20e1805f01230a54.
There was a comment "Remove the snippet and bootstrapping native inputs 
together with this patch" resp. "Remove stale generated file after 
applying pidgin-libnm.patch.".

Should configure scripts always be regenerated when building from tarballs?

> As a follow-up commit, you might want to drop the input labels.
> 
ALso noticed some other things later today:
- no status icon : --enable-trayicon-compat
-  nss-certs:  --with-system-ssl-certs=<dir>
- finch.pc requires libgnt. Should that also be propagated?
- Propagating gtk2 (required by pidgin.pc) conflicts in my home 
environments with nm-applet propagating gtk3.
- python2

> Cheers

Previous Next

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