Re: Curl Errors During DNF Repository Refresh

[Will McDonald <wmcdonald@xxxxxxxxx>]

On Sun, 24 Nov 2024 at 23:13, Barry <barry@xxxxxxxxxxxxxxxx> wrote:

> On 24 Nov 2024, at 21:54, Stephen Morris <steve.morris.au@xxxxxxxxx> wrote:
> I've been in the situation where running a dnf check-upgrade has refreshed the two Fedora Updates repositories and then issued dnf upgrade immediately after and had it refresh the two updates repositories again. I've been told from this mail list that for the Updates repositories that is normal as they are being updated all the time.

Did you do both dnf commands with sudo?

If dnf check-update was not run under sudo then the metadata is
saved somewhere is you user’s $HOME.
Then when you run sudo dnf update it will not have access to the user’s copy of the meta data.

And, just for the record because I still had the Vagrant box running:

[vagrant@localhost ~]$ id
uid=1000(vagrant) gid=1000(vagrant) groups=1000(vagrant) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

[vagrant@localhost ~]$ dnf check-upgrade > /dev/null 2>&1
[vagrant@localhost ~]$ find . -mmin -1
.
./.local/state/dnf5.log
./.cache
./.cache/libdnf5
./.cache/libdnf5/updates-e19adde8fd271134
./.cache/libdnf5/updates-e19adde8fd271134/repodata
./.cache/libdnf5/updates-e19adde8fd271134/repodata/repomd.xml
./.cache/libdnf5/updates-e19adde8fd271134/repodata/010f603e88da3adf72fbdc14876833963399f814ce1795698cffa6d529bf9cc8-primary.xml.zck
./.cache/libdnf5/updates-e19adde8fd271134/repodata/c885cb31c9bc9b0f810cbffcefca8d74d49ae5b34e7a5d89fa64b618379e123b-comps-Everything.x86_64.xml.zst
./.cache/libdnf5/updates-e19adde8fd271134/repodata/493151ccb8d844a2243c7940877cfe990b00784d3d1b51a45048f9d24652be0f-updateinfo.xml.zck
./.cache/libdnf5/updates-e19adde8fd271134/solv
./.cache/libdnf5/updates-e19adde8fd271134/solv/updates-updateinfo.solvx
./.cache/libdnf5/updates-e19adde8fd271134/solv/updates-group.solvx
./.cache/libdnf5/updates-e19adde8fd271134/solv/updates.solv
./.cache/libdnf5/fedora-7efbab3c1dbcd0d4
./.cache/libdnf5/fedora-7efbab3c1dbcd0d4/repodata
./.cache/libdnf5/fedora-7efbab3c1dbcd0d4/repodata/repomd.xml
./.cache/libdnf5/fedora-7efbab3c1dbcd0d4/repodata/3973367e3877b70900ae12d5074f025c99015ab5bc829d2cfbf6fa5d7a0cd0e2-primary.xml.zck
./.cache/libdnf5/fedora-7efbab3c1dbcd0d4/repodata/e0139f84a99188422fc0b0ce898b3eea06ee4b9702158c5a24adc70047c5a760-comps-Everything.x86_64.xml.gz
./.cache/libdnf5/fedora-7efbab3c1dbcd0d4/solv
./.cache/libdnf5/fedora-7efbab3c1dbcd0d4/solv/fedora-group.solvx
./.cache/libdnf5/fedora-7efbab3c1dbcd0d4/solv/fedora.solv
./.cache/libdnf5/fedora-cisco-openh264-1e5e9f1be3093a1f
./.cache/libdnf5/fedora-cisco-openh264-1e5e9f1be3093a1f/repodata
./.cache/libdnf5/fedora-cisco-openh264-1e5e9f1be3093a1f/repodata/repomd.xml
./.cache/libdnf5/fedora-cisco-openh264-1e5e9f1be3093a1f/repodata/a15963f895f0869850dc7805b79794c1913c9492d24214d2712a21ae3c97f578-primary.xml.gz
./.cache/libdnf5/fedora-cisco-openh264-1e5e9f1be3093a1f/repodata/3d50825fb25440abc9579f078205d6ba3590b1d146187af8179eb43214c8b40e-comps-Temporary.x86_64.xml.gz
./.cache/libdnf5/fedora-cisco-openh264-1e5e9f1be3093a1f/solv
./.cache/libdnf5/fedora-cisco-openh264-1e5e9f1be3093a1f/solv/fedora-cisco-openh264-group.solvx
./.cache/libdnf5/fedora-cisco-openh264-1e5e9f1be3093a1f/solv/fedora-cisco-openh264.solv

The root-owned cache files are in /var/cache/libdnf5/ from man 8 dnf5

FILES
       Cache Files
              /var/cache/libdnf5/

 

-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue