Bug 955668

Summary:	A collection can get twice-enabled
Product:	Red Hat Enterprise Linux 5	Reporter:	Jan Zeleny <jzeleny>
Component:	scl-utils	Assignee:	Jan Zeleny <jzeleny>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Zachar <lzachar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.9	CC:	drieden
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	scl-utils-20120927-4.el5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	955669 955670 (view as bug list)		Environment:
Last Closed:	2013-09-30 22:05:06 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:	955669, 955670

Description Jan Zeleny 2013-04-23 13:45:22 UTC

When running scl enable <collection> bash, a variable $X_SCLS should be filled with a list of collections that are enabled. When calling scl enable for the second time, content of $x_scls is read instead of $X_SCLS. In case of enabling the same collection again, it would lead to running collection's enable scriptlet twice.

In some specific cases, this can lead to malformed environment, as one of the basic assumptions of scl-utils is that once collection is enabled, it won't be enabled for the second time.

Comment 1 RHEL Program Management 2013-04-23 13:57:21 UTC

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 3 Jan Zeleny 2013-04-25 08:39:01 UTC

This has been fixed in the lates build scl-utils-20120927-4.el5

Comment 10 errata-xmlrpc 2013-09-30 22:05:06 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-2013-1303.html