Github messages for voidlinux
 help / color / mirror / Atom feed
From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: glfw-devel fails to install
Date: Sat, 21 Mar 2020 14:53:43 +0100	[thread overview]
Message-ID: <20200321135343.fPPrJltra0-QU4x0Ppt71tSz5Mfs0ANnniZb94Q1agg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20252@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

New comment by st3r4g on void-packages repository

https://github.com/void-linux/void-packages/issues/20252#issuecomment-602046028

Comment:
Can reproduce, `glfw-devel` is pulling `libglvnd-devel` which for some reason is trying to replace `nvidia340-libs` with `libglvnd`. Instead, you should be able to have `libglvnd-devel` and `nvidia340-libs` installed.
Trying to install `nvidia340` and `libglvnd-devel` in the same transaction seems to succeed... I did this:
```
xbps-remove nvidia340
xbps-install libglvnd
xbps-install nvidia340 libglvnd-devel
```
Now you should be able to install things that depend on `libglvnd-devel`, such as `glfw-devel`. I suspect this is a bug in the virtualpkg mechanism...
Please add 'when nvidia340 is installed' to the issue title.

  parent reply	other threads:[~2020-03-21 13:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21 11:04 [ISSUE] " BouncyMaster
2020-03-21 13:50 ` st3r4g
2020-03-21 13:53 ` st3r4g
2020-03-21 13:53 ` st3r4g [this message]
2020-03-21 13:54 ` st3r4g
2020-03-21 13:55 ` st3r4g
2020-03-21 14:02 ` xtraeme
2020-03-21 14:27 ` BouncyMaster
2020-05-23  9:43 ` libglvnd-devel fails to install when nvidia340 is installed st3r4g
2020-05-23 10:09 ` st3r4g
2020-07-03 11:57 ` st3r4g
2021-01-20 20:30 ` [ISSUE] [CLOSED] " ericonr
2021-01-20 20:30 ` ericonr

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=20200321135343.fPPrJltra0-QU4x0Ppt71tSz5Mfs0ANnniZb94Q1agg@z \
    --to=st3r4g@users.noreply.github.com \
    --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).