From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>,
Rutger Helling <rhelling@mykolab.com>
Subject: Re: Conflict resolution (gtk, wayland)
Date: Mon, 14 May 2018 11:23:41 +0200 [thread overview]
Message-ID: <87efiea8v6.fsf@gnu.org> (raw)
In-Reply-To: <87efijhj5q.fsf@gmail.com> (Pierre Neidhardt's message of "Thu, 10 May 2018 12:58:09 +0200")
Hello,
Pierre Neidhardt <ambrevar@gmail.com> skribis:
> Sometimes when updating or install packages, guix encounters conflicts.
> It's usually smart enough to fix it by itself.
>
> That said, conflicts seems to be a telltale sign of bad packaging
> (e.g. duplicate files in a package and its inputs).
>
> Presently guix reports 3 conflicts on my install:
>
> warning: collision encountered:
> /gnu/store/9hddxnv7q3q819axyw0yngzppmrgmjfi-mesa-17.3.8/lib/pkgconfig/wayland-egl.pc
> /gnu/store/2w8lhl8hyvciy3hb0h2r0mbhx7pmniy1-wayland-1.15.0/lib/pkgconfig/wayland-egl.pc
> warning: choosing /gnu/store/9hddxnv7q3q819axyw0yngzppmrgmjfi-mesa-17.3.8/lib/pkgconfig/wayland-egl.pc
>
> warning: collision encountered:
> /gnu/store/9hddxnv7q3q819axyw0yngzppmrgmjfi-mesa-17.3.8/lib/libwayland-egl.la
> /gnu/store/2w8lhl8hyvciy3hb0h2r0mbhx7pmniy1-wayland-1.15.0/lib/libwayland-egl.la
> warning: choosing /gnu/store/9hddxnv7q3q819axyw0yngzppmrgmjfi-mesa-17.3.8/lib/libwayland-egl.la
>
> warning: collision encountered:
> /gnu/store/nf6py3ddvk8nsqxg7jlg0kmiqjigiqgw-gtk-icon-themes/share/icons/hicolor/icon-theme.cache
> /gnu/store/mg1ilfq7ajcsk12kanzsbb8jhgv7g5vm-gtk+-3.22.29/share/icons/hicolor/icon-theme.cache
> warning: choosing /gnu/store/nf6py3ddvk8nsqxg7jlg0kmiqjigiqgw-gtk-icon-themes/share/icons/hicolor/icon-theme.cache
[...]
> So if I get it right, gtk-icon-themes is an automatically generated
> store items for each profile and it duplicates a file found in
> gtk+-3.22.29.
> Is this a packaging mistake?
No, “icon-theme.cache” collisions can be ignored. In fact, I think we
should not warn about them in the first place.
> Now to wayland:
>
>> guix gc -R /gnu/store/9hddxnv7q3q819axyw0yngzppmrgmjfi-mesa-17.3.8 | grep wayland
> /gnu/store/2w8lhl8hyvciy3hb0h2r0mbhx7pmniy1-wayland-1.15.0
>
>> guix gc --referrers /gnu/store/2w8lhl8hyvciy3hb0h2r0mbhx7pmniy1-wayland-1.15.0 | grep mesa
> /gnu/store/9hddxnv7q3q819axyw0yngzppmrgmjfi-mesa-17.3.8
>
> So mesa depends on wayland and wayland is properly referred to by mesa.
> So far so good. Same question: is this a packaging mistake?
It could be.
Actually, the .so files are identical, but the .la files differ
trivially:
--8<---------------cut here---------------start------------->8---
$ cmp $(guix build mesa)/lib/libwayland-egl.so $(guix build wayland)/lib/libwayland-egl.so
$ diff -u $(guix build mesa)/lib/libwayland-egl.la $(guix build wayland)/lib/libwayland-egl.la
--- /gnu/store/9hddxnv7q3q819axyw0yngzppmrgmjfi-mesa-17.3.8/lib/libwayland-egl.la 1970-01-01 01:00:01.000000000 +0100
+++ /gnu/store/2w8lhl8hyvciy3hb0h2r0mbhx7pmniy1-wayland-1.15.0/lib/libwayland-egl.la 1970-01-01 01:00:01.000000000 +0100
@@ -1,5 +1,5 @@
# libwayland-egl.la - a libtool library file
-# Generated by libtool (GNU libtool) 2.4.6 Debian-2.4.6-2
+# Generated by libtool (GNU libtool) 2.4.6
#
# Please DO NOT delete this file!
# It is necessary for linking the library.
@@ -38,4 +38,4 @@
dlpreopen=''
# Directory that this library needs to be installed in:
-libdir='/gnu/store/9hddxnv7q3q819axyw0yngzppmrgmjfi-mesa-17.3.8/lib'
+libdir='/gnu/store/2w8lhl8hyvciy3hb0h2r0mbhx7pmniy1-wayland-1.15.0/lib'
--8<---------------cut here---------------end--------------->8---
I’m not familiar enough with these packages, and I’m not sure why they
both provide this library.
Ideas? Rutger maybe?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-05-14 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 10:58 Conflict resolution (gtk, wayland) Pierre Neidhardt
2018-05-14 9:23 ` Ludovic Courtès [this message]
2018-05-14 10:40 ` Rutger Helling
2018-05-17 14:13 ` Ludovic Courtès
2018-05-22 7:42 ` Rutger Helling
2018-05-22 15:55 ` Marius Bakke
2018-05-22 16:22 ` Rutger Helling
2018-06-01 11:30 ` Rutger Helling
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=87efiea8v6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
--cc=rhelling@mykolab.com \
/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).