Description of problem:
When issuing "dnf upgrade" command the first response is:
"Setting up Update Process"...
If "update" is deprecated, why would we be using that term? It's just reinforcing it's use and makes it harder for the user to get it out of their mind.
If the decision was made to one term versus the other, we should be consistent.
Now it's just confusing, counter-intuitive and doesn't reinforce desired command syntax. We're telling people we don't want them to use "update" to do an "upgrade" - but instead when they enter "upgrade" we're telling them they are doing an "update".
Yes, in the grand scheme of problems it is a nit - but it should be extremely easy to correct.
Version-Release number of selected component (if applicable):
Issue "dnf upgrade" command from terminal
Steps to Reproduce:
1. Open terminal or kconsole
2. Issue "dnf upgrade" command
"Setting up Update Process"
"Setting up Upgrade Process"
This also applies throughout the transaction...
Updating : package_name
Upgrading : package_name
I didn't occur to me before but you are right, all those will have to be changed.
Also, until now I was careful not to change too many text outputs since DNF doesn't have its own translation project yet so no translations would work.
Fixed by 44c4a41, will be included in dnf-0.3.3.
dnf-0.3.3-3.git91ba5e0.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnf-0.3.3-3.git91ba5e0.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dnf-0.3.9-1.giteff4c49.fc19 has been submitted as an update for Fedora 19.
dnf-0.3.9-1.giteff4c49.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.