#1

I am using silverblue 30 beta and I dont want to reinstall the ISO from scratch is there a possible way to upgrade from Silverblue 30 Beta to new released Silverblue 30 or am I already updated?

This is my current rpm-ostree status output commit ID:

ostree://fedora-workstation:fedora/30/x86_64/silverblue
Version: 30.20190427.n.0 (2019-04-27T08:57:18Z)
BaseCommit: a602958b1097d0790361a8b907f6f6ecbb62b7bbf826b086401eafb4ffcb845d

#2

You won’t need to do anything. The fedora/30/x86_64/silverblue ref (branch) is the one you should follow for updates and you are already doing that so you look good!

3 Likes
#3

One thing I have observed is that the remote name is fedora instead of fedora-workstation, if we do a clean install of Fedora 30 Silverblue. Will there be difference between the two remotes?

rpm-ostree status output:

Deployments:
● ostree://fedora:fedora/30/x86_64/silverblue
Version: 30.20190427.n.0 (2019-04-27T08:57:18Z)
Commit: a602958b1097d0790361a8b907f6f6ecbb62b7bbf826b086401eafb4ffcb845d
GPGSignature: Valid signature by F1D8EC98F241AAF20DF69420EF3C111FCFC659B9
ostree://fedora:fedora/30/x86_64/silverblue
Version: 30.1.2 (2019-04-25T23:13:10Z)
Commit: 982faf58087c9d020780b829d5f24b4e78bd40399b4e4769fc8bc2df9890e301
GPGSignature: Valid signature by F1D8EC98F241AAF20DF69420EF3C111FCFC659B9

#4

The fedora remote is now delivered via the fedora-ostree-repos package, which allows the Fedora/Silverblue teams to deliver configuration changes via the RPM (and subsequent Silverblue composes).

Previously, the fedora-workstation remote was not delivered via an RPM and was configured as part of the post-compose process. This made it difficult to deploy changes to all Silverblue users.

The main difference between the two is the configuration. The fedora remote points at a new set of infrastructure that improves the download speeds of ostree content.

$ cat /etc/ostree/remotes.d/fedora.conf 
[remote "fedora"]
url=https://ostree.fedoraproject.org
gpg-verify=true
gpgkeypath=/etc/pki/rpm-gpg/
contenturl=mirrorlist=https://ostree.fedoraproject.org/mirrorlist

The fedora-workstation remote references the legacy infrastructure that was previously used. This config is still usable (for now), but it will likely result in slower download speeds.

$ cat /etc/ostree/remotes.d/fedora-workstation.conf 
[remote "fedora-workstation"]
url=https://kojipkgs.fedoraproject.org/atomic/repo/
gpg-verify=true
gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-primary
3 Likes
#5

I guess your fedora-workstation.conf is different than mine

$ cat /etc/ostree/remotes.d/fedora-workstation.conf
[remote "fedora-workstation"]
url=https://ostree.fedoraproject.org
gpg-verify=true
gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-30-primary
contenturl=mirrorlist=https://ostree.fedoraproject.org/mirrorlist

This is default I haven’t made any changes.

#6

That’s interesting. I took that config file from a fresh SB29 install that I did in a VM. I upgraded to the latest release (29.20190506.0) and the config was the same.

$ rpm-ostree status
State: idle
AutomaticUpdates: disabled
Deployments:
● ostree://fedora-workstation:fedora/29/x86_64/silverblue
                   Version: 29.20190506.0 (2019-05-06T00:44:20Z)
                    Commit: a17456870198452d66f2943a8d2d73365c7e20499d9507f40910af32f99a2ec7
              GPGSignature: Valid signature by 5A03B4DD8254ECA02FDA1637A20AA56B429476B4

  ostree://fedora-workstation:fedora/29/x86_64/silverblue
                   Version: 29.1.2 (2018-10-24T23:20:30Z)
                    Commit: f17b670fa8cf69144be5ae0c968dc2ee7eb6999a5f7a54f1ee71eec7783e434a
              GPGSignature: Valid signature by 5A03B4DD8254ECA02FDA1637A20AA56B429476B4
[miabbott@localhost ~]$ cat /etc/ostree/remotes.d/fedora-workstation.conf 
[remote "fedora-workstation"]
url=https://kojipkgs.fedoraproject.org/atomic/repo/
gpg-verify=true
gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-primary

Even after rebasing to SB30, the config file remained the same for me:

 rpm-ostree status
State: busy
AutomaticUpdates: disabled
Transaction: refresh-md
Deployments:
● ostree://fedora:fedora/30/x86_64/silverblue
                   Version: 30.20190427.n.0 (2019-04-27T08:57:18Z)
                    Commit: a602958b1097d0790361a8b907f6f6ecbb62b7bbf826b086401eafb4ffcb845d
              GPGSignature: Valid signature by F1D8EC98F241AAF20DF69420EF3C111FCFC659B9

  ostree://fedora-workstation:fedora/29/x86_64/silverblue
                   Version: 29.20190506.0 (2019-05-06T00:44:20Z)
                    Commit: a17456870198452d66f2943a8d2d73365c7e20499d9507f40910af32f99a2ec7
              GPGSignature: Valid signature by 5A03B4DD8254ECA02FDA1637A20AA56B429476B4
[miabbott@localhost ~]$ cat /etc/ostree/remotes.d/fedora-workstation.conf 
[remote "fedora-workstation"]
url=https://kojipkgs.fedoraproject.org/atomic/repo/
gpg-verify=true
gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-primary

However, if your fedora and fedora-workstation remotes are the same, you could use both. But, the plan is to make changes to the fedora remote via the fedora-ostree-repos package as I stated earlier. So there is a possibility you might get out of sync if you continue to use the fedora-workstation remote.

#7

Yes, you are right both fedora.conf & fedora-workstation.conf are identical.
I installed Silverblue 30 beta ISO and I am using it since then, maybe they changed it to the new one in ISO and I think you can’t get that by doing a rebase because it does not modify /etc & /var right?

#8

Thanks a lot. Switched to fedora remote.
rpm-ostree rebase --remote=fedora

#9

Probably you have followed this post before:
https://discussion.fedoraproject.org/t/improved-upgrade-speeds-now-possible/1060