Bug 26176 - Conflict: X11/extensions/XKBgeom.h provided by lib64x11-devel and x11-proto-devel
Summary: Conflict: X11/extensions/XKBgeom.h provided by lib64x11-devel and x11-proto-d...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-08 13:52 CET by papoteur
Modified: 2020-02-09 10:40 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description papoteur 2020-02-08 13:52:48 CET 
L'installation a échoué : le fichier /usr/include/X11/extensions/XKBgeom.h de l'installation de lib64x11-devel-1.6.9-1.mga8.x86_64 entre en conflit avec le fichier du paquet x11-proto-devel-2018.4-4.mga7.noarch
Comment 1 David GEIGER 2020-02-08 16:09:54 CET 
refer to https://gitlab.freedesktop.org/xorg/proto/xorgproto/issues/10

  # These headers refer to libX11 types and don't belong in this package.
  # libX11 and libXvMC have been updated to supply these headers themselves
  # now, so these are only useful for building older versions of those libraries.


So the header "include/X11/extensions/XKBgeom.h" is now provided in libx11 since release 1.6.9.

And the header "include/X11/extensions/XKBgeom.h" is now provided in libxvmc since release 1.0.12.



Now the problem is that we compile x11-proto-devel with "legacy" option turned on, this is why these 2 headers are also provided by it. So we have to drop them manually like:

http://svnweb.mageia.org/packages?view=revision&revision=1488058


Should be fixed with x11-proto-devel-2019.2-2.mga8!

CC: (none) => geiger.david68210

Comment 2 Lewis Smith 2020-02-09 10:40:49 CET 
@David: superfast work again!

@Papoteur : please confirm the result.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
CC: (none) => lewyssmith
Note You need to log in before you can comment on or make changes to this bug.