Bug 339731
| Summary: | wrong libxklavier buildreq | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kirill Kolyshkin <kolyshkin> |
| Component: | control-center | Assignee: | Control Center Maintainer <control-center-maint> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | rstrode |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-10-19 16:01:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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. Sure, doesn't make sense to rebuild per se, just fix the spec. Thanks! |
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...