Bug 1250843 - dnf cannot install updates while the cache is generated
Summary: dnf cannot install updates while the cache is generated
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-06 06:54 UTC by Sascha Zantis
Modified: 2015-08-11 15:31 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-11 15:31:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Sascha Zantis 2015-08-06 06:54:10 UTC
Description of problem:
I just started my system and wanted to install some updates via
sudo dnf update
It told me:
Waiting for process with pid 6904 to finish.
I looked for this process and it was:
/usr/bin/python -OO /usr/bin/dnf -v makecache timer
Well, I configured the system to create the cache via the systemd timer, but I somehow think creating the cache should not interfere with the update process. I am not familiar with dnf or package management details in general, but doesn't dnf update check the server on its own and not the cache?  

Version-Release number of selected component (if applicable):
dnf 1.0.1


How reproducible:
Always.

Steps to Reproduce:
1. Have dnf cache timer running
2. Start dnf update

Actual results:
You are forced to wait until the caching process is done.

Expected results:
dnf update ignores the caching process and just starts updating.

Comment 1 Honza Silhan 2015-08-11 15:31:08 UTC
This is a feature. DNF has makecache timer to sync the cache regularly. Without it you would still have to wait for the metadata downloads during "dnf update". If you wanna disable cron metadata refreshing you can turn it off by setting metadata_timer_sync=0 in /etc/dnf/dnf.conf. If you have waited forever for makecache timer then it's a bug -> reopen this, please.


Note You need to log in before you can comment on or make changes to this bug.