From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] libglvnd-devel conflicts with rpi-userland-devel
Date: Tue, 14 Jan 2020 05:20:46 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18299@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
New issue by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/18299
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
*output of ``xuname`` (part of xtools)*
* package:
*affected package(s) including the version*
### Expected behavior
No conflicts
### Actual behavior
```
libdrm-devel-2.4.100_1: coERROR: libglvnd-devel-1.3.0_1: file `/usr/lib/pkgconfig/egl.pc' already installed by package rpi-userland-devel-20190501_2.
ERROR: libglvnd-devel-1.3.0_1: file `/usr/lib/pkgconfig/glesv2.pc' already installed by package rpi-userland-devel-20190501_2.
```
### Steps to reproduce the behavior
`./xbps-src pkg EmulationStation-rpi -a armv7l`
`rpi-userland-devel` keeps everything in `/opt/vc/lib` but moves the pkgconfig to `/usr/lib` so they conflict with `libgvlnd` and most likely also always did, nobody just noticed/cared about it.
https://github.com/void-linux/void-packages/blob/e58027461027de6c2b123791fee3f2b2ed8b3c4a/srcpkgs/rpi-userland/template#L57
next reply other threads:[~2020-01-14 4:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 4:20 voidlinux-github [this message]
2020-01-24 15:04 ` [ISSUE] [CLOSED] " voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18299@inbox.vuxu.org \
--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).