Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 772697 - libvirt-devel grew a dependency on systemtap, preventing installs on ppc
libvirt-devel grew a dependency on systemtap, preventing installs on ppc
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt (Show other bugs)
6.3
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Martin Kletzander
Virtualization Bugs
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-09 12:12 EST by Daniel Berrange
Modified: 2012-06-20 02:46 EDT (History)
6 users (show)

See Also:
Fixed In Version: libvirt-0.9.10-1.el6
Doc Type: Bug Fix
Doc Text:
No Documentation needed
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 02:46:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0748 normal SHIPPED_LIVE Low: libvirt security, bug fix, and enhancement update 2012-06-19 15:31:38 EDT

  None (edit)
Description Daniel Berrange 2012-01-09 12:12:51 EST
Description of problem:
Attempting to build the latest perl-Sys-Virt RPM, I encountered an unresolvable
dependency in Systemtap on PPC architectures:

http://download.devel.redhat.com/brewroot/work/tasks/7361/3927361/root.log

DEBUG util.py:256:  Error: Missing Dependency: kernel-devel is needed by
package systemtap-1.6-4.el6.ppc (build)


The problem is that 'kernel-devel' is not built on PPC architecture in RHEL-6.
So AFAICT, there is no way that the 'systemtap' RPM can ever be installed on
the PPC archictecture, despite it being built.


NB, the root cause here is technically a systemtap (see bughttps://bugzilla.redhat.com/show_bug.cgi?id=772693) , but I don't think we should have a dep on systemtap in libvirt-devel in the first place.

This appears to be coming because we copy the examples/systemtap scripts in %doc. IIUC, if we remove the 'execute' bit from the *.stp files, then the RPM auto-dep extractor should not add this bogus dep.


Version-Release number of selected component (if applicable):
libvirt-0.9.9-1.el6

How reproducible:
Always (on ppc arch)

Steps to Reproduce:
1. yum install libvirt
2.
3.
  
Actual results:
DEBUG util.py:256:  Error: Missing Dependency: kernel-devel is needed by
package systemtap-1.6-4.el6.ppc (build)

Expected results:
libvirt can be installed without pulling in systemtap


Additional info:
Comment 4 Martin Kletzander 2012-01-17 13:20:34 EST
Fixed in commit 34364f43e9ddd02f5996aa44b58d52e0753e8064
Author: Martin Kletzander <mkletzan@redhat.com>
Date:   Fri Jan 13 13:40:56 2012 +0100

Permission change for systemtap examples.

Execute bit on *.stp files in examples/systemtap/ caused dependency when building RPM packages. Disabling execute permission should help the auto dependency resolver to see that systemtap is not needed.
Comment 7 yanbing du 2012-02-15 06:20:35 EST
Since we have no ppc machine to install libvirt and verify this bug, so just check the dependency of libvirt-devel-0.9.10-1.el6.ppc64.rpm

# rpm -qpR libvirt-devel-0.9.10-1.el6.ppc64.rpm
/usr/bin/pkg-config  
libvirt-client = 0.9.10-1.el6
libvirt-qemu.so.0()(64bit)  
libvirt.so.0()(64bit)  
pkgconfig  
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(VersionedDependencies) <= 3.0.3-1
rpmlib(PayloadIsXz) <= 5.2-1

There no dependency about  /usr/bin/stap, so move to VERIFIED.
Comment 8 Martin Kletzander 2012-05-03 09:13:01 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No Documentation needed
Comment 10 errata-xmlrpc 2012-06-20 02:46:12 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0748.html

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