I am looking for the correct way to rebase from SB F28 to SB F29. Via the command line, is it the following?
rebase fedora/29/x86_64/workstation
can you try
rpm-ostree rebase fedora/29/x86_64/silverblue
I see from the Silverblue cheatsheet (found here: https://docs.fedoraproject.org/en-US/fedora-silverblue/_attachments/silverblue-cheatsheet.pdf) that the correct command is:
rpm-ostree rebase <REMOTE>:<BRANCH>
I can see what my current remote & and branch are from the refspec given by running:
rpm-ostree status
Some of the output is as follows:
State: idle
AutomaticUpdates: disabled
Deployments:
â—Ź ostree://fedora-workstation:fedora/28/x86_64/workstation
Version: 28.20180902.0 (2018-09-02 04:34:23)
So I believe the correct command to rebase the system to SB29 is:
rpm-ostree rebase fedora-workstation:fedora/29/x86_64/workstation
Correct me if I am wrong please
1 Like
Yeah, that is the correct full command.
During a rebase operation, if the remote isn’t specified, rpm-ostree will try to find the branch specified on the currently active remote.
The command that @dustymabe provided is just a shorter way of using the command you derived.
1 Like
The problem is that we “re-branded” Atomic Workstation to Silverblue, which means you need to use the fedora/29/x86_64/silverblue branch now
2 Likes
Thank you both @dustymabe and @miabbott
Is there a list somewhere of all the Fedora-maintained branches one can rebase to?
which means you need to use the
fedora/29/x86_64/silverbluebranch now
Yes, though note that until there’s a new compose Commit - workstation-ostree-config - 87a4410d2f42485673dfbce27c1a0e0ce847d91c - Pagure.io will break everyone using LVM (which is the default).
Is there a list somewhere of all the Fedora-maintained branches one can rebase to?
I have fedora-atomic as the remote name here, it will vary currently.
# ostree remote refs fedora-atomic
fedora-atomic:fedora/27/aarch64/atomic-host
fedora-atomic:fedora/27/ppc64le/atomic-host
fedora-atomic:fedora/27/x86_64/atomic-host
fedora-atomic:fedora/27/x86_64/testing/workstation
fedora-atomic:fedora/27/x86_64/updates/workstation
fedora-atomic:fedora/27/x86_64/workstation
fedora-atomic:fedora/28/aarch64/atomic-host
fedora-atomic:fedora/28/aarch64/testing/atomic-host
fedora-atomic:fedora/28/aarch64/updates/atomic-host
fedora-atomic:fedora/28/ppc64le/atomic-host
fedora-atomic:fedora/28/ppc64le/testing/atomic-host
fedora-atomic:fedora/28/ppc64le/updates/atomic-host
fedora-atomic:fedora/28/x86_64/atomic-host
fedora-atomic:fedora/28/x86_64/testing/atomic-host
fedora-atomic:fedora/28/x86_64/testing/workstation
fedora-atomic:fedora/28/x86_64/updates/atomic-host
fedora-atomic:fedora/28/x86_64/updates/workstation
fedora-atomic:fedora/28/x86_64/workstation
fedora-atomic:fedora/29/aarch64/testing/atomic-host
fedora-atomic:fedora/29/ppc64le/testing/atomic-host
fedora-atomic:fedora/29/x86_64/silverblue
fedora-atomic:fedora/29/x86_64/testing/atomic-host
fedora-atomic:fedora/29/x86_64/testing/silverblue
fedora-atomic:fedora/29/x86_64/workstation
fedora-atomic:fedora/rawhide/aarch64/atomic-host
fedora-atomic:fedora/rawhide/ppc64le/atomic-host
fedora-atomic:fedora/rawhide/x86_64/atomic-host
fedora-atomic:fedora/rawhide/x86_64/silverblue
fedora-atomic:fedora/rawhide/x86_64/workstation
1 Like
@walters answer should be the same for most Silverblue users who have the fedora-workstation remote installed
Also worth noting, @walters has a ticket open with Fedora rel-eng to delete the workstation refs in favor of the silverblue refs
Thanks!! I guess I need to start reading rpm-ostree docs.
Hmmm …
rpm-ostree rebase fedora-workstation:fedora/29/x86_64/silverblue
error: Commit 7aab9c4071c544d6bac9e02a2a01d54cfbd41f42d6b3b8b055a160bf0afdcf0f: GPG signatures found, but none are in trusted keyring
rpm-ostree rebase fedora-workstation:fedora/29/x86_64/silverblue
Receiving metadata objects: 1/(estimating) 142 bytes/s 569 bytes
error: Commit 8781ad5a58f3a7dbedaad23391fa439dbb6bb3bcf9a7b267148e4fa3aad102c0: GPG signatures found, but none are in trusted keyring
Hi I am getting the above error
Sigh… see make gpgkeypath 🗝 support being a list 📓 · Issue #773 · ostreedev/ostree · GitHub. basically the gpgkey you currently have configured for the remote is the f28 gpg key. You’ll have to change it out for the f29 gpgkey. For example:
[root@vanilla-f29-atomic ~]# cat /etc/ostree/remotes.d/fedora-atomic.conf
[remote "fedora-atomic"]
url=https://kojipkgs.fedoraproject.org/atomic/repo/
gpg-verify=true
gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-primary
Find your file in the /etc/ostree/remotes.d/ directory and update it to say 29 instead of 28.
1 Like
I think the missing GPG signature in the keyring is a bug.
A workaround for me was to download https://getfedora.org/static/429476B4.txt and save it as “fedora-29-key.txt”, then run:
ostree remote gpg-import fedora-workstation -k fedora-29-key.txt
4 Likes
Thanks Garrett, that seems to have done the trick!
though note that until there’s a new compose
That happened now, it includes lvm2 again.
I got Silverblue 29 rebase to work:
sudo ostree remote gpg-import fedora-workstation -k /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-x86_64
sudo rpm-ostree rebase fedora-workstation:fedora/29/x86_64/silverblue
but the boot didn’t come all the way to to a login screen. gdm started but that’s as far as it got
It’s a bit blurry but if you zoom in you can read it -“Started GNOME Display Manager”.
ostree://fedora-workstation:fedora/29/x86_64/silverblue
Version: 29.20180905.n.0 (2018-09-06 02:15:39)
BaseCommit: 8781ad5a58f3a7dbedaad23391fa439dbb6bb3bcf9a7b267148e4fa3aad102c0
GPGSignature: Valid signature by 5A03B4DD8254ECA02FDA1637A20AA56B429476B4
LayeredPackages: chrome-gnome-shell chromium cockpit docker-compose f28-backgrounds-extras-gnome git git-lfs
gnome-shell-extension-dash-to-dock gnome-shell-extension-native-window-placement
gnome-shell-extension-openweather gnome-shell-extension-pomodoro
gnome-shell-extension-screenshot-window-sizer gnome-shell-extension-topicons-plus
gnome-shell-extension-user-theme gnome-tweaks kernel-tools powertop python3-speedtest-cli
vim-enhanced
I bet it’s your gnome-shell extensions that are stopping you from reaching the desktop. They probably aren’t compatible with gnome 3.30