Bug 339731 - wrong libxklavier buildreq
Summary: wrong libxklavier buildreq
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-19 14:02 UTC by Kirill Kolyshkin
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 16:01:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kirill Kolyshkin 2007-10-19 14:02:36 UTC
Apparently version of libxklavier specified as BuildReq in control-center.spec
should be bumped.

I'm trying to rebuild control-center from devel on F7 box:

$ rpmbuild --rebuild control-center-2.20.1-1.fc8.src.rpm
Installing control-center-2.20.1-1.fc8.src.rpm
......
checking for LIBGNOMEKBD... configure: error: Package requirements (libgnomekbd
>= 0.1 libxklavier >= 3.2) were not met:

Requested 'libxklavier >= 3.2' but version of libxklavier is 3.1
$ rpm -qp --requires control-center-2.20.1-1.fc8.src.rpm | grep libxk
libxklavier-devel >= 1.14

Should be

BuildReq: libxklavier-devel >= 3.2


Version-Release number of selected component (if applicable):
control-center-2.20.1-1


Finally -- is there a way to auotmate the generations those BuildReqs from the
configure.ac of the package itself? I heard that AltLinux guys are doing just
that for their spec files...

Comment 1 Ray Strode [halfline] 2007-10-19 15:47:18 UTC
there's a patch laying around to pull buildreqs for pkg-config files, but I
don't think it's on the radar to get applied anytime soon.

I'll commit the BuildReq change, but probably won't do a build until there's a
more pressing reason.

Comment 2 Kirill Kolyshkin 2007-10-19 15:55:02 UTC
Sure, doesn't make sense to rebuild per se, just fix the spec. Thanks!


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