From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: nvidia390: fix libGL dependency conflict
Date: Sat, 12 Oct 2019 10:59:04 +0200 [thread overview]
Message-ID: <20191012085904.uwEsbm3tEJnpc6Smh65Vc-pKWdKvGGfxBnbj6fdVTKc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15337@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
There's a merged pull request on the void-packages repository
nvidia390: fix libGL dependency conflict
https://github.com/void-linux/void-packages/pull/15337
Description:
Trying to include the package `nvidia390` in a live image:
`sudo ./mklive.sh -a x86_64 -r https://alpha.de.repo.voidlinux.org/current/nonfree -p nvidia390`
Failed with:
> nvidia390-libs-390.129_1: collecting files...
ERROR: nvidia390-libs-390.129_1: file `/usr/lib/libEGL.so.1' already installed by package libEGL-19.1.7_3.
ERROR: nvidia390-libs-390.129_1: file `/usr/lib/libGL.so.1' already installed by package libGL-19.1.7_3.
ERROR: nvidia390-libs-390.129_1: file `/usr/lib/xorg/modules/extensions/libglx.so' already installed by package libGL-19.1.7_3.
Transaction failed! see above for errors.
ERROR: Failed to install base-system nvidia390
The reason is that `nvidia390-gtklibs` pulls in `cairo` which in turn installs the Mesa implementation of `libGL` (ignoring the `libGL` provided by Nvidia). I fixed this looking at how the `nvidia` template deals with it, I don't know if it's the optimal solution.
prev parent reply other threads:[~2019-10-12 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 15:20 [PR PATCH] " voidlinux-github
2019-10-12 8:35 ` voidlinux-github
2019-10-12 8:56 ` voidlinux-github
2019-10-12 8:57 ` voidlinux-github
2019-10-12 8:59 ` voidlinux-github [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191012085904.uwEsbm3tEJnpc6Smh65Vc-pKWdKvGGfxBnbj6fdVTKc@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).