$ rpm-ostree update
$ rpm-ostree rebase fedora:fedora/40/x86_64/silverblue
Receiving metadata objects: 0/(estimating) -/s 0 bytes... done
error: While pulling fedora/40/x86_64/silverblue: While fetching https://d2uk5hbyrobdzx.cloudfront.net/delta-indexes/NK/zRroGmpJGyBol0ksLZshGjGRCKuFQmJzolT948r3k.index: Server returned HTTP 504
If it’s relevant:
$ rpm-ostree status
State: idle
AutomaticUpdates: check; rpm-ostreed-automatic.timer: inactive
Deployments:
â—Ź fedora:fedora/41/x86_64/silverblue
Version: 41.20250228.0 (2025-02-28T01:04:58Z)
BaseCommit: f30505c93f2b6b5092f0c3ae69353c75556cee10538b67ba76a5e95124fdd7a9
GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
LocalOverrides: libxkbcommon-x11 libxkbcommon 1.7.0-4.fc41 -> 1.8.0-1.fc42
LayeredPackages: gnome-tweaks goldendict levien-inconsolata-fonts libavcodec-freeworld libva-intel-driver libva-utils lorax rpmfusion-free-release rpmfusion-nonfree-release smartmontools
systemd-boot-unsigned terminus-fonts translate-shell zsh
Probably relevant: Atomic Desktop Update Error: Server Returned HTTP 502
2 Likes
Might be, thanks.
Still I’m not seeing anyone reporting 504 error…
This is being tracked in Issue #12427: Server returns HTTP 502 when trying to rollback Fedora Silverblue - fedora-infrastructure - Pagure.io as well
1 Like
The infra issue has been fixed and the above issue has been closed.
Please file new issues about using the Atomic Desktops on the issue tracker - GitHub - fedora-silverblue/issue-tracker: Fedora Silverblue issue tracker
1 Like