Description of problem:
I run `$ dnf --cacheonly upgrade` quite frequently. Every time the cache expires it updates the cache from network. This is not what the man page says:
Run entirely from system cache, don't update the cache and use it even in case it is expired.
DNF uses a separate cache for each user under which it executes. The cache for the root user is called the system cache. This switch allows a regular user read-only access to the system cache which usually is more fresh then the user's and thus he does not have to wait for metadata sync.
Version-Release number of selected component (if applicable):
dnf 0.6.2-1.fc21 from F21 Alpha
There was a similar bug: https://bugzilla.redhat.com/show_bug.cgi?id=1048468 so this seems to be a regression.
Unfortunately, I am not able to reproduce this bug in dnf 0.6.2-1. Is there any difference between your system and fresh F21 alpha installation?
Yes. I have set root's umask to 077 and have installed all available updates.
dnf-0.6.3-2.fc21,dnf-plugins-core-0.1.4-1.fc21,hawkey-0.5.2-1.fc21 has been submitted as an update for Fedora 21.
Package dnf-0.6.3-2.fc21, hawkey-0.5.2-1.fc21, dnf-plugins-core-0.1.4-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnf-0.6.3-2.fc21 hawkey-0.5.2-1.fc21 dnf-plugins-core-0.1.4-1.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dnf-0.6.3-2.fc21, hawkey-0.5.2-1.fc21, dnf-plugins-core-0.1.4-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.