GNU bug report logs - #52519
glibmm-2.64 propagates two different versions of libsigc++

Previous Next

Full log

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

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Leo Famulari <leo <at> famulari.name>
Cc: 52519-done <at> debbugs.gnu.org
Subject: Re: bug#52519: glibmm-2.64 propagates two different versions of
 libsigc++
Date: Mon, 17 Jan 2022 12:10:58 -0500

Hi,

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> Hi Leo,
>
> Leo Famulari <leo <at> famulari.name> writes:
>
>> glibmm-2.64 has this:
>>
>> ------
>>      (propagated-inputs
>>       (modify-inputs (package-propagated-inputs glibmm)
>>         (prepend libsigc++-2)))))
>> ------
>>
>> And, the glibmm package also propagates libsigc++.
>>
>> So:
>>
>> ------
>> $ guix show glibmm <at> 2.64 | grep libsigc
>> dependencies: doxygen <at> 1.9.1 glib <at> 2.70.0 graphviz <at> 2.49.0 libsigc++@2.9.3
>> + libsigc++@3.0.6 libxslt <at> 1.1.34 m4 <at> 1.4.18 mm-common <at> 1.0.3 perl <at> 5.34.0
>> ------
>>
>> It propagates both versions of libsigc++, and thus cannot be installed
>> into a profile. 1785 packages depend on glibmm-2.64.
>>
>> This breaks synfig, which propagates glibmm, as requested in its 'synfig.pc'
>> pkg-config file.
>
> I've fixed this with;
>
> modified   gnu/packages/glib.scm
> @@ -814,7 +814,7 @@ (define-public glibmm-2.64
>          (base32 "11m37sbx0i18cl17d0fkq0bik4bbzlb5n8kcl651jhci5ipci3sh"))))
>       (propagated-inputs
>        (modify-inputs (package-propagated-inputs glibmm)
> -        (prepend libsigc++-2)))))
> +        (replace "libsigc++" libsigc++-2)))))
>  
>  (define-public python2-pygobject-2
>
> It will have to be built on the version-1.4.0 branch first.

Which has now been merged back into master.

Closing!

Maxim

Previous Next

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