Github messages for voidlinux
 help / color / mirror / Atom feed
From: Hoshpak <Hoshpak@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] evieext conflicts with xorgproto
Date: Sat, 23 May 2020 10:30:48 +0200	[thread overview]
Message-ID: <20200523083048.sNOiSQFuceQZES10hPTlW5ZwOrZuWAgh_YXyfaPvJdE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22172@inbox.vuxu.org>

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

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





      parent reply	other threads:[~2020-05-23  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 17:46 [ISSUE] " 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 ` Hoshpak [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=20200523083048.sNOiSQFuceQZES10hPTlW5ZwOrZuWAgh_YXyfaPvJdE@z \
    --to=hoshpak@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).