Seth Vidal wrote:
On Mon, 15 Dec 2008, Jeroen van Meeuwen wrote:
Now that in anaconda, during package selection, you can enable the
"Updates" repository for a given release, has anyone thought of the
- You select/enable the "Updates" repository
- Included in your selection of packages is package foo, available in
both the "Fedora/" repository as well as the "Updates" repository
- Package foo (from "Updates") now requires package bar, which is in
"Everything/" (not in "Fedora/"), but hasn't been updated since GA
(e.g, is not available in the "Updates" repository)
This would cause failed dependencies if the "Updates" repository is
enabled during installation, also enable the "Everything" repository.
Let me know if this doesn't make any sense.
You mean it is possible for someone to add repos to Anaconda which don't
satisfy all the deps? I think that's been known for a long time.
It's not that, it's the package selection dialog with the "Office and
Productivity" / "Software Development" / "Web-server" screen that allows
enabling the "Fedora 10" repository (also known as "Everything/"), and
the "Fedora 10 - Updates" repository.
So, again, adding your own / third party repositories == go die in a
fire, NOTABUG, WONTFIX, WORKSFORME, insert-your-favorite-here.
Enabling the repositories offered in the GUI *as we offer it* however
could lead to errors it shouldn't -> forcibly enabling the "Everything/"
repository when "Updates" has been enabled is the solution, IMO.
Jeroen van Meeuwen
Anaconda-devel-list mailing list