bug#52519: closed (glibmm-2.64 propagates two different versions of libsigc++)

[GNU bug Tracking System]

Your message dated Mon, 17 Jan 2022 12:10:58 -0500
with message-id <87y23ei8yl.fsf@gmail.com>
and subject line Re: bug#52519: glibmm-2.64 propagates two different versions 
of libsigc++
has caused the debbugs.gnu.org bug report #52519,
regarding glibmm-2.64 propagates two different versions of libsigc++
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
52519: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=52519
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> glibmm-2.64 propagates two different versions of libsigc++
>
>
>
>
> Date: 
>
> Wed, 15 Dec 2021 13:40:09 -0500
>
>
>
>
> 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.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#52519: glibmm-2.64 propagates two different versions of libsigc++
>
>
>
>
> Date: 
>
> Mon, 17 Jan 2022 12:10:58 -0500
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
>
>
>
>
> 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
>
>
> --- End Message ---