I understand the others but I dont know about updates/silverblue and how this is different from just /silverblue? I assume updates are normally applied to the normal silverblue remote because we all receive updates?
Are testing/silverblue silverblue with the testing repositories enabled?
I don’t have a complete answer to this question yet. I will take a look soon but in the meantime you can try to fetch those refs or rebase to them and compare the packages included with rpm-ostree db diff/list.
I have wanted to post on the fedora remote for a while but was afraid of coming across as a malcontent. But I do wish it
a) was updated with a little more frequency and
b) had any sort of music and video player to fill out the default applications (I’d honestly just like Rhythmbox and Totem like the default Fedora comes with)
It doesn’t seem like much but I hate the idea of at least my browser not being up to date. Is the packaging particularly difficult and could I contribute in any way to help keep the applications updated?
Ah apologies, I see I posted on the wrong type of remote, but if anyone will allow for the tangent it is all just software packaging at the end of the day (if it is too much of a tangent I can make my own thread).
This is expected as the Flatpaks are not made the same way:
Flathub Flatpaks are directly built from upstream sources at the version the maintainer decides to use.
Fedora Flatpaks are built from sources too but from the versions used in RPMs.
In both cases, anyone can contributes update via pull requests. If you want fresher software in the Fedora Flatpak repo, you can try to help with Fedora packaging updates.
In Fedora, the sources and specfiles used to build RPM packages are also re-used to build Flatpaks. There is only a small Flatpak specific configuration needed on top.
Same deals with Evolution and eog. Looking at Commits - flatpaks/firefox - src.fedoraproject.org it seems like Kalev Lember has built 92.0 for Flatpak. It just hasn’t found its way into the Fedora remote yet?
From QA:Updates Testing - Fedora Project Wiki, the testing refs should be images built with the testing repos enabled. I don’t know what the updates ones are.
Was curious too so I tested it and updates vs normal silverblue seems the same thing except naming of the branch even the commit hashes are same and no diff.
[me@fedora ~]$ rpm-ostree rebase fedora:fedora/35/x86_64/updates/silverblue
â ‹ Scanning metadata: 7989
Scanning metadata: 7989... done
Staging deployment... done
Freed: 626.0 MB (pkgcache branches: 0)
Changes queued for next boot. Run "systemctl reboot" to start a reboot
[me@fedora ~]$ rpm-ostree status
State: idle
Deployments:
fedora:fedora/35/x86_64/updates/silverblue
Version: 35.20211102.0 (2021-11-02T00:40:44Z)
Commit: 1f1bc444c98105e29a2a7ac828818f947001c39af6e20cc9be5e2d1328453782
GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
â—Ź fedora:fedora/35/x86_64/silverblue
Version: 35.20211102.0 (2021-11-02T00:40:44Z)
Commit: 1f1bc444c98105e29a2a7ac828818f947001c39af6e20cc9be5e2d1328453782
GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
fedora:fedora/35/x86_64/silverblue
Version: 35.20211029.1 (2021-10-29T22:13:42Z)
Commit: 1e3c0b9ec5dac32ad3c369e22eb235b3ff94f4b8d9f698b64ff56511fb434c3d
GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
[me@fedora ~]$ rpm-ostree db diff
ostree diff commit from: booted deployment (1f1bc444c98105e29a2a7ac828818f947001c39af6e20cc9be5e2d1328453782)
ostree diff commit to: pending deployment (1f1bc444c98105e29a2a7ac828818f947001c39af6e20cc9be5e2d1328453782)
@computersavvy I know this is an old post but there is not a clear answer. I was wondering about this as I was thinking about enabling the testing repository.
Someone discovered the difference between testing and updates remote refs?
Essentially, the named and updates refs are the same once a given Fedora release is go. The testing one is built with the testing repo enabled and thus has all the pending packages in testing included.
but there is not a clear answer. I was wondering about this as I was thinking about enabling the testing repository.