Bug 77394
Summary: | up2date does not list all package/channel combinations | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Nick Strugnell <nstrug> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED NOTABUG | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 8.0 | CC: | djenkins, gafton, mihai.ibanescu |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-04-05 21:11:28 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
Nick Strugnell
2002-11-06 10:17:13 UTC
whats `up2date --show-channels` report? up2date --show-channels correctly lists all the available channels. I think that up2date is simply unaware that a package can reside in multiple channels, and only ever reports the first hit for a given package. You have the exact same package in multiple channels? I didn't even think that was supposed to work at all. And the machine is subscibed to all these channels? This is kind of unusual useage, so I'm not exactly sure what to expect it to do. Never sure how exactly the expected behaviour differed from the actual behaviour, so closing. |