How Reproducible: Steps to Reproduce: 1. Go to http://webapp.rwc-colo.redhat.com/network/channel/download_isos.pxt and login as tommyreynolds 2. 3. Actual Results: Expected Results: Additional Information: When attempting to download an ISO, it is not clear from the working whether this is going to be a pristine as-released ISO, or whether it is a "virtual" ISO containing the current snapshot including the errata RPM's. I'd prefer a "virtual" ISO that would be today's versions of all my configured packages.
Would be lovely, but I don't see this happening anytime soon. Making this happen would mean that we were rebuilding anaconda with every ISO, and we just don't have that kind of time to push the results through QA.
But isn't this effectively what we have with RHN and "up2date"? Just because it's delivered in a single file instead of tons'o downloaded RPM changes our support policy?
You are simplifying the process way too much. RHN and up2date allow the user to download updated packages for their already installed system. Putting together installable ISOs on the fly which include the latest and greatest is quite a bit different. First and foremost, the installer itself (anaconda) has to feed an updated package listing (with the new versions) and the header list has to be regenerated. Then the resulting ISO image would have to undergo testing to verify that it works as it should. We might be able to start thinking about doing stuff like this with the next major version switch, but definitely not at this point.
I believe you; never claimed to know anything about the gory details ;-) I'll happliy accept a "we'll consider this for a future enhancement" note. If we can wordsmith the RHN web page about ISO's to clarify that it is the pristine original ISO's that are downloaded, I'll be satisfied for the nonce.
This is more of a longterm goal on our roadmap than a bugzilla at this point.