Red Hat Bugzilla – Bug 1187741
dnf should state if packages explicitly requested for update aren't installed
Last modified: 2015-06-24 12:58:32 EDT
Description of problem:
I was trying to update my version of the `zip` software from the updates-testing repo to test the new update and I kept getting a "Nothing to do" message from dnf. Turns out the package I was trying to update wasn't even installed. dnf should either prompt the user to install these packages or at least notify the user that the package wasn't installed so updating won't occur.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run `sudo dnf update PACKAGE_THATS_NOT_INSTALLED -y`
"Dependencies resolved.\nNothing to do." is output
A notice or warning that the package isn't installed so updating can't be done. It could even prompt the user to install the requested package in this case. Since this is an explicit request from the user, I don't see how that would be a bad thing.
Thanks for the report. Fixed. PR: https://github.com/rpm-software-management/dnf/pull/220
Excellent, looked at the PR and it looks good (I know Python but not familiar with DNF's internals).
Did you decide that adding a prompt to install the software that was requested isn't worth the code complexity? I think it'd be very nice from a UX perspective though I could see how it could be a lot of extra code.
See also Bug #1195106. I'd like more information than a confirmation of "nope, couldn't do it". I'd like to know *why*. Especially since it's being held back to a Fedora 20 version...
dnf-1.0.1-2.fc22 has been submitted as an update for Fedora 22.
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnf-1.0.1-2.fc22'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dnf-1.0.1-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Yep, this fixed it now. Thanks!