Bug 339731 - wrong libxklavier buildreq
wrong libxklavier buildreq
Product: Fedora
Classification: Fedora
Component: control-center (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Control Center Maintainer
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-10-19 10:02 EDT by Kir Kolyshkin
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 12:01:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kir Kolyshkin 2007-10-19 10:02:36 EDT
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):

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 11:47:18 EDT
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 Kir Kolyshkin 2007-10-19 11:55:02 EDT
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.