Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] evieext conflicts with xorgproto
@ 2020-05-21 17:46 not-chicken
  2020-05-21 19:42 ` mnabid
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: not-chicken @ 2020-05-21 17:46 UTC (permalink / raw)
  To: ml

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

New issue by not-chicken on void-packages repository

https://github.com/void-linux/void-packages/issues/22172

Description:

### System

* package:  
  `evieext-1.1.1_2`, `xorgproto-2019.2_1` 

### Expected behavior
No conflicts
### Actual behavior
```
libffi-devel-3.3_2: ERROR: evieext-1.1.1_2: file `/usr/include/X11/extensions/Xeviestr.h' already installed by package xorgproto-2019.2_1.
ERROR: evieext-1.1.1_2: file `/usr/include/X11/extensions/evieproto.h' already installed by package xorgproto-2019.2_1.
```
### Steps to reproduce the behavior
`./xbps-src -aaarch64 pkg at-spi2-core`

### Possible Solution
Remove `evieext`( and the only package that depends on it `libXevie`) from the repos, it's been replaced by `xorgproto` [upstream](https://gitlab.freedesktop.org/xorg/proto/evieproto/-/commit/b834764e393cdc966fa3ac6ca0f004108fd5e4d6).

According to xbps-query only `at-spi2-core` needs `libXevie-devel` , but it isn't listed as a dep by [upstream](https://github.com/GNOME/at-spi2-core/blob/mainline/INSTALL) and I was able to build it without it so `libXevie` should be safe to remove as well.





^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2020-05-23  8:30 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-21 17:46 [ISSUE] evieext conflicts with xorgproto not-chicken
2020-05-21 19:42 ` mnabid
2020-05-21 19:46 ` ericonr
2020-05-21 23:54 ` not-chicken
2020-05-23  8:30 ` [ISSUE] [CLOSED] " Hoshpak

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).