Red Hat Bugzilla – Bug 470653
Packages from external repos not seen in package selection; mandatory packages don't get installed
Last modified: 2008-11-15 03:45:11 EST
Description of problem:
Enabling the RPM Fusion free repo during a standard Fedora rawhide install does not give the desired result:
- Packages from the RPM Fusion free repo are not selectable in the Package Selection within anaconda
- the rpmfusion-free-release package, which the comps.xml from RPM Fusion adds to the core group and marks as "mandatory" is not getting installed
Version-Release number of selected component (if applicable):
boot.iso from 20081107
Steps to Reproduce:
1. fire off a install using boot.iso
2. enable RPM Fusion free for rawhide as add-on repository when getting to the software selection screen in anaconda; repository name: foobar; repository URL [for ix86]: http://download1.rpmfusion.org/free/fedora/development/i386/os/
3. Select "Curtomize now"
-> no packages from RPM Fusion can be found in the package selection
4. Continue install
-> rpmfusion-free-release not installed
Note, maybe the comps.xml files from RPM Fusion are wrong and thus completely or partly the root case for the problem; but I designed them after advice from Jesse in
Comps.xml can be found here:
I build pirut from Fedora cvs for F8 on a up2date rawhide machine to check if it works well with the current compx.xml file from RPM Fusion. Is does; see
and the screenshots attached to it.
Also note that Jeremy tried to solve this problem (which creates trouble for some years now without getting properly fixed; this is the third bug about it iirc):
Can you grab the anaconda.log from the install? (/var/log/anaconda.log if you let it finish)
And then I'll take a look at it and see where I can get from there as I really think this *should* be working now.
Created attachment 322993 [details]
log from install with RPM Fusion Free enabled
(In reply to comment #1)
> Can you grab the anaconda.log from the install? (/var/log/anaconda.log if you
> let it finish)
> And then I'll take a look at it and see where I can get from there
> as I really think this *should* be working now.
As mentioned earlier, maybe it's the comps.xml format from RPM Fusion that's wrong.
Created attachment 322997 [details]
anaconda log with a different repo that has a different comps.xml
(In reply to comment #2)
> > as I really think this *should* be working now.
> As mentioned earlier, maybe it's the comps.xml format from RPM Fusion that's
I did one more test to check how the format of comps.xml influences the behavior: I used the latest boot.iso from rawhide and enabled the rpmfusion updates repo for Fedora 9 (http://download1.rpmfusion.org/free/fedora/updates/9/i386/) during install. Normally that is something one should never do, but its a nice way to test as a different comps.xml is used for the F9 repo.
For reference, here's the URI to RPM Fusion's comps.xml files from F9 and F10:
As you can see, the F10 comps.xml from RPM Fusion tries to extend the groups from Fedora. The one for F9 otoh defines RPM Fusion specific groups; their IDs and Names are different from the ones used by Fedora.
But the package selection doesn't work with the F9 comps as well. The problems are quite similar to the one in the initial bug report:
- Packages from the RPM Fusion free repo are not selectable in the "pirut-like" Package Selection screen from anaconda; none of the RPM Fusion specific groups is shown
- the rpmfusion-free-release package, which the comps.xml from RPM Fusion marks as "mandatory" in a default select group is not getting installed
I think I figured out what's going on and sent a patch for it to anaconda-devel-list. Will give a full test this evening and hopefully can get it into tomorrow's rawhide
Tested and cleaned up the stupid thinkos in the patch and resent it.
Many many thx for working on this jeremy. I saw it got added to the anaconda that was build for devel; is there still a chance/some way to get this integrated into anaconda for F-10?
Gah, that was the intent. It looks like Chris just did the build in the wrong place. Will get fixed up for tomorrow
I gave it a test and it seems to work now; thx jeremy!