Update issue with flatpak org.fedoraproject.Platform

Ask Fedora
1

Update of the following component doesn’t work. Is there something missing?
How can I resolve this issue?

========================================
LANG=C flatpak update
Looking for updates?

    ID                                   Branch          Op          Remote          Download


1. org.fedoraproject.Platform           f43             u           fedora          1.0?kB / 496.7?MB

Error: Server returned status 404
Updates complete.
error: There were one or more errors

Best regards
Andreas

2

Error 404 usually means the server is down. Try again later or change servers.

1 Like
3

Hi David,

thank you for your reply. I’m just wondering because
LANG=C flatpak update -vv

shows me
F: Loading https://registry.fedoraproject.org/v2/f43/flatpak-runtime/manifests/sha256:6a23aec8feda246f116aa1ab13823450ecbbd5760a424bfda78d9164e6f00659 using curl
F: Received 557 bytes
F: Loading https://registry.fedoraproject.org/v2/f43/flatpak-runtime/blobs/sha256:890d8d3192763d632505f0f3a33aad0db1a6071ea06948560e0556179fdc21e3 using curl
F: Received 10226 bytes
F: Pulling OCI image sha256:6a23aec8feda246f116aa1ab13823450ecbbd5760a424bfda78d9164e6f00659
F: Loading https://cdn.registry.fedoraproject.org/deltas/6a/23aec8feda246f116aa1ab13823450ecbbd5760a424bfda78d9164e6f00659.json using curl
F: Received 3095 bytes
Updating? ?? 8%
F: Using OCI delta sha256:0e4623aea071181d0a594155aa1e68c4a863f3d3b68efb1388d1a3f878a6bc0f for layer sha256:8c5112b5cf6446c51542a1fc4445dad103ef5834435600b3661dda54d58fbbbf
F: Loading https://cdn.registry.fedoraproject.org/deltas/0e/4623aea071181d0a594155aa1e68c4a863f3d3b68efb1388d1a3f878a6bc0f.tardiff using curl
Updating? ?? 8%
Error: Server returned status 404
Updates complete.
error: There were one or more errors

And this looks like certain elements are missing while other download ressources seem to be there.

4

The comment by David above still applies. The different files required from the server seem not in sync and that is usually fixed by allowing time for the sync to complete.

1 Like
5

Hi David, hi Jeff,

you’ve been right. Just waiting another day solved the problem.
I wasn’t aware that a situation can come up where a mirrot site knows about an update and signalling it but not having all necessary parts to fulfill the update.

Thank you for the answers
Andreas

1 Like