I am trying to use lorax to build a test boot.iso with a newer anaconda build. When I point it to the F22 repository and my local repo with a newer anaconda DNF is not picking the package with the higher NVR. If I point it to the F22 and rawhide repos it picks the one from rawhide, so my guess is that with my local repo there are some deps still missing and it falls back to the one with the complete set of dependencies instead of stopping with an error. Attached is a script that can demonstrate the problem. Copy a newer version of anaconda (23.8 from rawhide is what I used in my test) into a side repo, run createrepo on it and run: test-dnf-transaction -r 22 -s http://dl.fedoraproject.org/pub/fedora/linux/releases/22/Everything/x86_64/os/ -s http://url-of-side-repo/ anaconda |& tee package-list.txt Is it possible to get DNF to choose the one I want, and if it won't work exit with an error?
Created attachment 1030844 [details] test-dnf-transaction script
*** This bug has been marked as a duplicate of bug 1225725 ***
(In reply to Brian Lane from comment #0) > Is it possible to get DNF to choose the one I want, and if it won't work > exit with an error? If the package has a unique version, specify the version (e.g. "anaconda-23.8"), if the package is in a unique repository, specify the repository (e.g. "dnf repository-packages REPO install anaconda"; using API, you need to query the package "base.sack.query().filter(reponame=REPO)" and install it "base.package_install(pkg)").
Well the point is to not have to specify the NVR. We give lorax a list of repos and DNF should pick the best packages or raise an error if the dependencies of the highest NVR packages cannot be met. As an update, I've added conf.best = True to my config setup in the attached script, expecting that it would at least raise an error that the deps for the newer anaconda version were unresolved, but it does not. It still picks the older version. I'm unduping this since I don't think it is the same issue. In those other bugs they are having dependency problems that can't be resolved at all. In this case there is a resolution, it's just the wrong one. I want to see it complain that anaconda-23.xxx can't be installed instead of it picking anaconda-22.xxx which has complete deps.
(In reply to Brian Lane from comment #4) > Well the point is to not have to specify the NVR. We give lorax a list of > repos and DNF should pick the best packages or raise an error if the > dependencies of the highest NVR packages cannot be met. > > As an update, I've added conf.best = True to my config setup in the attached > script, expecting that it would at least raise an error that the deps for > the newer anaconda version were unresolved, but it does not. It still picks > the older version. > > I'm unduping this since I don't think it is the same issue. In those other > bugs they are having dependency problems that can't be resolved at all. In > this case there is a resolution, it's just the wrong one. I want to see it > complain that anaconda-23.xxx can't be installed instead of it picking > anaconda-22.xxx which has complete deps. I'm sorry but I have hard time seeing how this is different than bug 1225725. If you re-read your last sentence, you will see that the problem is exactly the same. Or am I missing something? Reading back the second paragraph of your response, maybe that's what you want this bug report to be about? (the conf.best option behavior)
bug 1225725 is about it reporting an error. This bug is about it *not* reporting an error and choosing the package that isn't the higest NVR even when best=True is used.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.