On Sat, 23 Feb 2019 19:55:14 +0200 Adrian Sevcenco <Adrian.Sevcenco@xxxxxxx> wrote: > On 2/23/19 6:49 PM, stan via users wrote: > > Otherwise, you could just do the basic netinstall, then boot into > > it and do the dnf install of other packages as normal. Then it > > would just be a package conflict, and skip-broken would skip it. > well, i commented out the fedora-update repo and the install worked .. > so, i would say that it is a bug as i would expect that the update > repository to be compatible with the install image The update repo changes with time while the install image doesn't. > > If it is a broken install image, you should bugzilla it at > > https://bugzilla.redhat.com/ > yup, i submitted trough the included mechanism from anaconda Probably going to be closed as notabug because they can't fix it. It is just the way fedora works. > > I think the images are checked as part of the release process so > > this shouldn't be true, but that is done by volunteers so it might > > not have been checked. > well, i would say that always a net install should be checked with > update repository enabled... It might have at freeze time, but the update repo changes constantly. The fedora repo is frozen when the release is frozen, so that it works with the released image, as you discovered. The inconsistency you ran into is not uncommon with regular dnf updates. Glad you got it worked out. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
