Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 59843

Summary:	RFE: up2date should support command line channel restrioctions
Product:	Red Hat Enterprise Linux 4	Reporter:	Chip Turner <cturner>
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jay Turner <jturner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	cturner, gafton, mihai.ibanescu, pjones, srevivo, taw
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-02-13 22:21:35 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:

Description Chip Turner 2002-02-13 20:24:49 UTC

up2date client should support a flag that lets you restrict -u to a given set of
channel(s):

[root@minbar rhn]# up2date --show-channels
redhat-linux-i386-7.2
skunkworks-i386-7.2
rhn-satellite-i386-7.2
[root@minbar rhn]# up2date -u -c skunkworks-i386-7.2 -c rhn-satellite-i386-7.2

This would only pull from skunkworks and satellite, and not the base (so it is
an inclusive operation with none defaulting to be included unless specified, if
any -c exists).  Or any other flag/scheme, the important functionality being
only upgrading packages in specific channels while allowing dependencies be
pulled all channels.

Comment 1 Adrian Likins 2002-02-13 22:21:29 UTC

I think we are going to need to always include the base channel,
but allow selected child channels to be included. It doesnt
really make since otherwise (use channel X at this point,
but channel B at that point, and both at this other point elsewhere...)
All the rules we tell child channel makers seem to blow up at
that point as well (basically, you can have deps on the base channel stuff)

The intent seems to be to allow all packages of a channel downloaded
at once, which is kind of a orthogonal problem and probabaly best
as a seperate RFE.