Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dnf5 CLI: Redownload update for --offline switch #1655

Open
mcrha opened this issue Aug 26, 2024 · 1 comment
Open

dnf5 CLI: Redownload update for --offline switch #1655

mcrha opened this issue Aug 26, 2024 · 1 comment
Labels
Priority: MEDIUM Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take

Comments

@mcrha
Copy link
Contributor

mcrha commented Aug 26, 2024

This is with dnf5-5.2.4.0-20240715005730.21.g9c2e2150.fc41.x86_64

Steps, commands run as root:

  1. dnf update and let it download the packages; then cancel the update
  2. run again dnf update and notice the packages are not downloaded, they are recognized as being locally stored; cancel the update
  3. run dnf update --offline - this time the packages are downloaded again, even they are stored locally, as verified in the previous step

I had a Fedora rawhide update, which meant to download 3GB of the data (according to the dnf message). Downloading it twice is a waste of bandwidth, time and the disk space (I fight with the disk space constantly, because this virtual machine has only ~20GB disk, thus I cannot even store those 3GB twice locally). The package cache should be shared for the --offline and not --offline variant of the update.

@jan-kolarik
Copy link
Member

The data from dnf update and dnf update --offline are stored at different locations. But you're right that it would be a good optimization.

@jan-kolarik jan-kolarik added Priority: MEDIUM Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take labels Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: MEDIUM Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take
Projects
Status: Backlog
Development

No branches or pull requests

2 participants