Closed kontura closed 3 years ago
I confirm this patch fix the issue
Tested on Fedora 33 with librepo 1.14.0 + this patch and dnf 3.7.0 + mock 2.10.1
@kontura : this makes a lot of sense to me. Thanks for writing this!
This bug is affecting me on Fedora 34 with dnf-4.7.0-1.fc34 and librepo-1.14.0-1.fc34; is there likely to be an update at some point to fix it?
@pghmcfc there will definitely be an update to F34 but it might take a while.
@pghmcfc there is https://bodhi.fedoraproject.org/updates/FEDORA-2021-3b74285c43 which contains new librepo with the fix.
@pghmcfc there is https://bodhi.fedoraproject.org/updates/FEDORA-2021-3b74285c43 which contains new librepo with the fix.
Thanks, that works for me.
When
fsync
fails due to the file not supporting synchronization just log the problem instead of failing the whole dnf run. This happens for example with filesystems mounted read-only in which case there is no point tofsync
anyway.Currently we also ignore return values from
FSETXATTR
which also fails on read-only filesystem (so no checksum cache is set). This is fine however since the checksum is recomputed when needed, dnf is just a bit slower.https://bugzilla.redhat.com/show_bug.cgi?id=1956361
@malmond77 can you take a look at this please?