unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Martin Michel <martin@famic.de>, help-guix@gnu.org
Subject: Re: Conflicting entries for glibmm
Date: Wed, 11 May 2022 15:52:54 +0200	[thread overview]
Message-ID: <87czgkdvm1.fsf@gmail.com> (raw)
In-Reply-To: <20220427131122.egl4rwmjn62qu6yj@famic.de>

Hi,

On mer., 27 avril 2022 at 15:11, Martin Michel <martin@famic.de> wrote:

> ```
> $ guix install gtksourceviewmm
> The following package will be installed:
>    gtksourceviewmm 3.18.0
>
> guix install: error: profile contains conflicting entries for glibmm
> guix install: error:   first entry: glibmm@2.70.0 /gnu/store/fpfi5y405y04rpiz7zn75gmiilwkzb4x-glibmm-2.70.0
> guix install: error:    ... propagated from gtksourceviewmm@3.18.0
> guix install: error:   second entry: glibmm@2.64.5 /gnu/store/0sl7zf5bcr1qb7yfq2wqqly1w3x0spn8-glibmm-2.64.5
> guix install: error:    ... propagated from pangomm@2.46.0
> guix install: error:    ... propagated from gtkmm@3.24.5
> guix install: error:    ... propagated from gtksourceviewmm@3.18.0
> hint: You cannot have two different versions or variants of `gtksourceviewmm' in the same profile.
>
> $ guix remove glibmm
> guix remove: error: package 'glibmm' not found in profile
> ```

This issue is that ’gtksourceviewmm' propagates glibmm@2.70 when
pango@2.46 propagates glibmm@2.64.5 via gtkmm@3.24.5.  It reads,

--8<---------------cut here---------------start------------->8---
(define-public gtksourceviewmm
  (package
    (name "gtksourceviewmm")
    (version "3.18.0")
[...]
    (propagated-inputs
     ;; In 'Requires' of gtksourceviewmm-3.0.pc.
     (list glibmm gtkmm-3 gtksourceview-3))


(define glibmm
  (package
    (name "glibmm")
    (version "2.70.0")


(define-public gtkmm-3
  (package
    (inherit gtkmm)
    (name "gtkmm")
    (version "3.24.5")
[...]
    (propagated-inputs
     `(("atkmm-2.28" ,atkmm-2.28)
       ("cairomm-1.14" ,cairomm-1.14)
       ("glibmm" ,glibmm)
       ("gtk+" ,gtk+)
       ("pangomm-2.42" ,pangomm-2.46)))))


(define-public pangomm-2.46
  (package
    (inherit pangomm)
    (name "pangomm")
    (version "2.46.0")
[...]
     (list cairomm-1.14 glibmm-2.64 pango))))


 (define-public glibmm-2.64
   (package
    (inherit glibmm)
    (name "glibmm")
    (version "2.64.5")
--8<---------------cut here---------------end--------------->8---


The easiest workaround is to downgrade glibmm to glibmm-2.64 in
gtksourceviewmm.  This way, the conflict disappears but another appears:

--8<---------------cut here---------------start------------->8---
guix install: error: profile contains conflicting entries for libsigc++
guix install: error:   first entry: libsigc++@3.0.6 /gnu/store/ng4k2yl94d758p5vnashd4nvyb1aw8s1-libsigc++-3.0.6
guix install: error:    ... propagated from cairomm@1.14.2
guix install: error:    ... propagated from gtkmm@3.24.5
guix install: error:    ... propagated from gtksourceviewmm@3.18.0
guix install: error:   second entry: libsigc++@2.9.3 /gnu/store/iad8jg1fm7jsq0pqj547f3n5s2jn9rp0-libsigc++-2.9.3
guix install: error:    ... propagated from glibmm@2.64.5
guix install: error:    ... propagated from pangomm@2.46.0
guix install: error:    ... propagated from gtkmm@3.24.5
guix install: error:    ... propagated from gtksourceviewmm@3.18.0
--8<---------------cut here---------------end--------------->8---

Well, this package gtksourceviewmm seems old and I do not know what is
the best solution.  Maybe extract a complete stack without any conflict
(if such existed ;-))) and maintain this old package in a separated
channel.

Or update gtksourceviewmm to a more recent 4.x stack, if such wrapper
exists.

Or give a look if all these propagation are mandatory and maybe remove
the unnecessary ones.


Cheers,
simon


      reply	other threads:[~2022-05-11 13:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 13:11 Conflicting entries for glibmm Martin Michel
2022-05-11 13:52 ` zimoun [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=87czgkdvm1.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=martin@famic.de \
    /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.
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).