Red Hat Bugzilla – Bug 169245
yum.repos.d files should turn on development repos not others
Last modified: 2013-01-09 20:19:42 EST
Description of problem:
When one installs rawhide, yum is configured to pull packages from
fc4 repos not devel repos. It is annoying to have to correct this each
time after installing.
Steps to Reproduce:
1. Install rawhide.
2. Look at which repos are enabled in /etc/yum.repos.d/
Core, Updates and Extras repos for fc4 are enabled.
Core and Extras Devel repos only to be enabled.
This would have to be changed in fedora-release. I'll try to remember to change
this in FC5Test3. However I do feel that until we have a test release, the
previous release should remain enabled. Rawhide isn't self sustaining at first.
Perhaps the change should be flipped at test1 timeframe. I want to discuss
this w/ the engineers.
There is no reason why a FC5test install should be pointing at FC4 repos. I
made sure it was pointing at devel for test1 but didn't check it before test2,
sorry about the inconvenience. =(
Sorry, why is rawhide not "self-sustaining"? Doesn't it pull from
FC updates from the last release?
FC5 earlier in its development pulled in FC4 + updates if packages were not
rebuilt in FC5. By this point we *should* have rebuilt everything at least once
and FC5 should be self-hosting. However parent collections and yum.repos.d are
actually different things.
This bug is really about forgetting to enable the development repo and disable
FC4 in test2.
To be clear, I mean that rawhide and test installs should always enable
development by default in yum.repos.d.
It looks like development is enabled, but the base is still enabled. So not
only is it pulling from the development repo, its also pulling from whatever yum
figures is the $release, in this case FC4. I agree that base should be disabled
in test releases, I'm just not sure about rawhide itself. Prior to Test1,
rawhide could be just a bunch of FCX + updates packages, including
fedora-release. At that point, rawhide is just a set of updates to a given FC
release, not a release in itself.
Am I totally off base?
Rawhide may contain packages that are exactly the same as those in FC4 (it still
does today), however rawhide has a copy of the latest-pkg for the entire
collection within its own yum repo. This is due to collection inheritance.
Right, but is it worth it to respin redhat-release each time the rawhide tree
moves on from a release? Is the cost worth the effort?
I'm still confused: is there any good reason why rawhide yum shouldn't
always pull just from FC/FE devel repos by default?
The FC/FE Devel should be. I suppose that fedora-release would have to be
touched in order ot make this happen anway, so at the same time we're touching
that, we could turn off the base repo.
I'll look into this for the FC6 development. It is too late in FC5 development
to make any changes.
Did we release FC5test3 with this same problem?
(Yes, too late now, but just curious.)
INVESTIGATE state has been obsoleted. Moving bugs to ASSIGNED.
Fixed in rawhide.