Closed rscm closed 1 year ago
This is ultimately the same issue as #475. Composes have been failing for several days, apparently due to a samba update. The fix for that is in the compose running now, so hopefully this one will succeed:
thanks for the info
looks like that was it, because I had a ton of packages upgraded
well ostree is upgraded now so this issue is closed
thanks again
Describe the bug The package ostree doesn't get updated to the latest version even though is present in the servers and available.
I've tried rpm-ostree refresh-md and nothing. I also tried rpm-ostree refresh-md --force.
I checked using toolbox and the latest version of the package for dnf is 2023.4-2
the lastest upgrade was (you can see that ostree gets upgraded to 2023.4-1 not the latest version)
this is the output of dnf info inside a pod (toolbox), there you can see the latest is version 2023.4-2
To Reproduce Please describe the steps needed to reproduce the bug:
Expected behavior Upgrade ostree from ostree-2023.4-1.fc38.x86_64 to ostree-2023.4-2.fc38.x86_64 and being able to use flatpak
OS version:
Additional context The package was marked in stable yesterday https://bodhi.fedoraproject.org/updates/FEDORA-2023-464fae1680
and is present in the mirrors the system direct me to use through the metalink (https://mirrors.fedoraproject.org/metalink?repo=updates-released-f38&arch=x86_64)
this is the first mirror (100 score) http://fedora.c3sl.ufpr.br/linux/updates/38/Everything/x86_64/Packages/o/ostree-2023.4-2.fc38.x86_64.rpm this is the second mirror (99 score) https://edgeuno-bog2.mm.fcix.net/fedora/linux/updates/38/Everything/x86_64/Packages/o/ostree-2023.4-2.fc38.x86_64.rpm