Hide Forgot
Description of problem: yumex-dnf allows the user to configure expiration of cache after 1-240 hours. There should also be an option to disable yumex-dnf control of the cache, such as by allowing the user to enter -1. dnf allows for more fine-grained control of cache expiration (e.g. different expiration settings per repository -- particularly relevant since the fedora non-updates repo never changes), and some users would prefer to leave the cache control to dnf. Use case: I have things set up outside of yumex-dnf so that dnf always keeps its cache up-to-date, yet with the default yumex-dnf settings, virtually every time I open yumex-dnf, it redownloads the repo data. This is a big deal for me because on my connection it takes 5-10 minutes to download the repo data. I have finally set yumex-dnf to only expire the cache every 10 days (the maximum value allowed), but this is still sub-optimal because yumex-dnf should never need to expire the cache with my setup. Version-Release number of selected component (if applicable): 4.1.2-1
Agree Added upstream issue to track development https://github.com/timlau/yumex-dnf/issues/76
Fixed upstream https://github.com/timlau/yumex-dnf/commit/1191a0825bcb86ac0c6fb795180879048009ca3b
dnfdaemon-0.3.15-1.fc24 yumex-dnf-4.3.3-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-aa868f02e4
dnfdaemon-0.3.15-1.fc24, yumex-dnf-4.3.3-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-aa868f02e4
dnfdaemon-0.3.15-1.fc24, yumex-dnf-4.3.3-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.