Bug 1078210

Summary: [python33] tbb doesn't depend on %{scl}-runtime
Product: Red Hat Software Collections Reporter: Bohuslav "Slavek" Kabrda <bkabrda>
Component: tbbAssignee: Tomas Tomecek <ttomecek>
Status: CLOSED ERRATA QA Contact: Jan Kepler <jkejda>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: python33CC: jkejda, python-maint
Target Milestone: beta   
Target Release: 1.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python33-tbb-4.1-7.20130314.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1078207 Environment:
Last Closed: 2014-06-04 07:28:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1072281    

Description Bohuslav "Slavek" Kabrda 2014-03-19 12:00:41 UTC 
+++ This bug was initially created as a clone of Bug #1078207 +++

python27-suitesparse doesn't require python27-runtime, which means that it can get installed/uninstalled without python27-runtime package. That can result in leftovers after uninstallation as mentioned in bug 1076159, e.g. "/opt/rh/python27/root/usr/share/doc".
The problem is that Yum can uninstall python27-suitesparse packages *after* the python27-runtime package is uninstalled, e.g.:

1) user types "yum remove python27*"
2) yum makes a transaction, in which it wants to remove python27-runtime prior to python27-suitesparse
3) directories owned by python27-runtime, that contain files from python27-suitesparse can't be removed when python27-runtime is uninstalled (suitesparse is still installed)
4) when python27-suitesparse is uninstalled, no package owns the directories like "/opt/rh/python27/root/usr/share/doc" => after python27-suitesparse uninstallation (and after the whole yum transaction), these directories are left on the system


The same applies to python33-tbb
Comment 4 errata-xmlrpc 2014-06-04 07:28:17 UTC 
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/RHBA-2014-0609.html