Problem installing pidgin because it propagates gtk+@2

  • Open
  • quality assurance status badge
Details
One participant
  • Christopher Baines
Owner
unassigned
Submitted by
Christopher Baines
Severity
normal
C
C
Christopher Baines wrote on 4 Jan 2021 21:40
(address . bug-guix@gnu.org)
87mtxojv0j.fsf@cbaines.net
As reported by sss2 on IRC [1]. I can see this has changed recently, I
don't know why [2].

guix package -i pidgin spice-gtk --no-substitutes
The following package will be upgraded:
spice-gtk (dependencies or package changed)
The following package will be installed:
pidgin 2.14.1
The following derivations will be built:
/gnu/store/a4n2ankaiqv857dbaqj82bmmk6bmd6ha-spice-gtk-0.37.drv
/gnu/store/jh9z9mn9jz6744fyb3g3q5cn2nhhi65z-spice-gtk-0.37.tar.bz2.drv
building /gnu/store/jh9z9mn9jz6744fyb3g3q5cn2nhhi65z-spice-gtk-0.37.tar.bz2.drv...
building /gnu/store/a4n2ankaiqv857dbaqj82bmmk6bmd6ha-spice-gtk-0.37.drv...
guix package: error: profile contains conflicting entries for gtk+
guix package: error: first entry: gtk+@3.24.23 /gnu/store/1biqkwwsx20rbg8xm1y66qdj41h2jp4h-gtk+-3.24.23
guix package: error: ... propagated from spice-gtk@0.37
guix package: error: second entry: gtk+@2.24.32 /gnu/store/19av64kqzb9y9d9lfhqfy6bb4xl8z0zh-gtk+-2.24.32
guix package: error: ... propagated from pidgin@2.14.1
hint: Try upgrading both `spice-gtk' and `pidgin', or remove one of them from the profile.


-----BEGIN PGP SIGNATURE-----

iQKlBAEBCgCPFiEEPonu50WOcg2XVOCyXiijOwuE9XcFAl/zfTxfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF
ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcRHG1haWxAY2Jh
aW5lcy5uZXQACgkQXiijOwuE9XcJYw/+MxgFqCz6E0cfM1fOftnw5d8lisB/SVT3
9uXBgGmyQeq4DcWrUGz3ORrlBdrxNIGZJO5eJ+PxLA6By47V2NIUw/9T73XoOfa1
R0sIprmXP6by5MLgLfqKvNB7qbOnsNeycRHUG0/VhLQy4mfsr9eqzTpXfpwk9LqH
o7Q+Eo7uXS4EsSqeInSdEgK1FyZKID3NPPBYya3K9eUBQksrvYEQzOozK09gvbG0
dux+l/WgF3D8eX7oRjDFEsesTnU8uFxMkgZlS4XeJLF/NiNyS+o73cb5fMx4KK1H
Vz4k419Cb2YoyzUh9xdjPebYyNS2vXQdaHeYvzEHxkOmuD5qU8U5zYewQSseJrWJ
VlKStaYMOPJrUUtsB7cWe2u47zXrNYC5A/V1o7WN1Pbsk1VFT8gBN1sBbAFEC6R9
9wQp1+OuhKYM+2fAXTep1l7r5BRzAAZUv05YneMWvZ5LTFQHP2gyvpQv+8cz6Z4B
ptYmyLlsmggR/qanJnSiLc8niBS6IDwY2m2oyMvUGIUWTAkF46ShS9uLltFekiOE
CiOREHfLwP2U2gSI1xfDXkxrgDkwg0mARS1qfmQ/lqe3q42rd+Sh2Qwe8rhqK7SC
ZdW9B+Rr66OEzZ1xNuRpaRN1H2hA2+gRezQRCMPXCMpLchaaNBtPXOZLzVLVBMXG
+t6Jnkpu+cs=
=f48I
-----END PGP SIGNATURE-----

?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 45663@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 45663
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch