Jeroen van Meeuwen wrote:
Jeremy Katz wrote:
Do these actually need to be excluded now? I think that with recent
yum (which we end up depending on anyway), if you have a package set
which includes
fedora-release
generic-release
and then you explicitly specify to install 'generic-release', provides
which generic-release can do will get used "first" and then we'd only
fall back to fedora-release if there was a provide which couldn't be
satisfied.
Well, upd-instroot selects "system-release" and "system-logos", and
let's YUM figure out whatever is the best match. The user (or
application triggering buildinstall) is not able to select the brand
packages.
The same goes for mk-images(.efi), where repoquery whatprovides
system-logos spits out a list (grep -v generic-logos), which using only
the Fedora repositories will give you "fedora-logos". If, however, I
include a repository for orangesombrero-logos -which I'm going to want
to use, it'll still select fedora-logos (head -1).
I should add that (using this patch) when using orangesombrero as a
brand, the packages must be available or the build will fail. It cannot
fall back to generic-* packages since those have been excluded.
Kind regards,
Jeroen van Meeuwen
-kanarip
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
