From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 52519-done@debbugs.gnu.org
Subject: bug#52519: glibmm-2.64 propagates two different versions of libsigc++
Date: Mon, 17 Jan 2022 12:10:58 -0500 [thread overview]
Message-ID: <87y23ei8yl.fsf@gmail.com> (raw)
In-Reply-To: <87v8zm4jqk.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 17 Dec 2021 23:31:15 -0500")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Hi Leo,
>
> Leo Famulari <leo@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@2.64 | grep libsigc
>> dependencies: doxygen@1.9.1 glib@2.70.0 graphviz@2.49.0 libsigc++@2.9.3
>> + libsigc++@3.0.6 libxslt@1.1.34 m4@1.4.18 mm-common@1.0.3 perl@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
prev parent reply other threads:[~2022-01-17 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 18:40 bug#52519: glibmm-2.64 propagates two different versions of libsigc++ Leo Famulari
2021-12-18 4:31 ` Maxim Cournoyer
2022-01-17 17:10 ` Maxim Cournoyer [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=87y23ei8yl.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=52519-done@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).