Bug 5030 - Package 'libxcb-util-wm-devel' conflicts with xcb (bad header file)
Summary: Package 'libxcb-util-wm-devel' conflicts with xcb (bad header file)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Junior_job, PATCH
Depends on:
Blocks:
 
Reported: 2012-03-19 18:43 CET by Rick Stockton
Modified: 2012-10-07 20:06 CEST (History)
2 users (show)

See Also:
Source RPM: xcb-util-wm
CVE:
Status comment:


Attachments

Description Rick Stockton 2012-03-19 18:43:28 CET
We need to rebuild this package; a current pull from Git works correctly. The header file "xcb/util-wm/icccm/xcb_icccm.h" contains some new data, and this newer version (larger) runs correctly when compiling an xcb interface against our other RPMs.

The current header provided in the RPM does not work with xcb 3.8.
Size of the good, new one is 40454 bytes.
Size of the older, bad one is 40439 bytes.

Problem occurs, for example, when compiling the xcb platform plugin of Qt5.0 (which is alpha code, but widely used and tested on other platforms. Mageia-2, beta 2, is broken.
Comment 1 Manuel Hiebel 2012-03-19 19:11:12 CET
no maintainer and commiter for now

Keywords: (none) => Junior_job, PATCH
Source RPM: (none) => xcb-util-wm

Comment 2 Rick Stockton 2012-04-02 09:09:29 CEST
I'm not smart enough to do this, but KDE Devs are already working on migration to Qt5 ... and aren't we a "KDE-oriented Distro"?

There is no xlib support left in qt5: You MUST use xcb (now) or Wayland (future) in order to see a graphics DE. 

Unfortunately, my workaround no longer works -- and I'm not able to figure out things which the build scripts want (the xcb "core" library builds, but the  utils and wm-utils break during "autogen.sh" and /or "configure".)

- - - - -
No one will be able to attempt anything like a KDE 5 backport, or begin learning teh "new" qt, unless we can Display a graphical window. Both Widgets and QML die on the command line wher you try to run a program, saying "libxcb.so: undefined symbol: xcb_size_hints_set_position".

Here's the header for Qt change, which is already Merged in Git:
    "2     Author: Robin Burchell <robin+qt@viroteck.net>
3	AuthorDate: 2012-03-15 10:39:47 +0100
			4	Commit: Robin Burchell <robin+qt@viroteck.net>
			5	CommitDate: 2012-03-21 15:17:58 +0100
			6	
			7	Remove xlib plugin.
			8	
			9	There's not much point having this with the xcb plugin being present, and xlib
			10	is pretty much unmaintained / broken anyway.
			11	
			12	Task-number: QTBUG-24913
			13	Change-Id: I090a9a0e6d2f893c030574e23f1d59f610282bd3
Comment 3 Rick Stockton 2012-04-02 09:11:12 CEST
Sorry about the edit.
Anyway, I was the last holdout, and I stopped whining when I had the problem bypassed (temporarily) and blamed on Mageia. No other Distro has the problem.
Comment 4 Marja Van Waes 2012-05-26 13:10:34 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 5 Rick Stockton 2012-05-27 01:30:15 CEST
marja, I have needed Qt5 (for Dev work within that product). Given the lack of a maintainer/packager here, combined with my inability to even solve the problem (much less build packages for it) - I migrated to Fedora 17.

So I cannot that the problem is still present, and I also cannot verify that the problem is resolved.

If it isn't resolved, you will receive numerous future complaints by people attempting to build Qt5 from source (including your own Maintainer).
- - - -
perhaps change the status from 'New' to 'Unconfirmed' ? Sorry that I can't help.
Manuel Hiebel 2012-05-27 01:38:44 CEST

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Sander Lepik 2012-05-27 09:36:16 CEST

Keywords: NEEDINFO => (none)
CC: (none) => sander.lepik

Comment 6 Thierry Vignaud 2012-10-07 20:06:49 CEST
Cauldron has been updated to 0.3.9 a long time ago

Status: UNCONFIRMED => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.