Silverblue F39 - automatic updating? How to disable?

Ask Fedora
, , , ,
1

I rebased my Silverblue from F38 to F39 last week.

And I discovered that I will have a new deployment waiting for me from time to time, like below:

I did not reboot, and over the night & day, I find there is a new deployment 39.20230817 waiting for me.

Is this a new update behaviour? How can I disable this?

rpm-ostree status
State: idle
Deployments:
  fedora:fedora/39/x86_64/silverblue
                  Version: 39.20230817.n.0 (2023-08-17T07:51:17Z)
               BaseCommit: cef807158a7ddeb23c53cd5390cd6f8b724eb01dbc03b866a5da0e1371153e7b
             GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C
                     Diff: 119 upgraded, 1 removed, 1 added
          LayeredPackages: ibus-cangjie-engine-cangjie virt-manager
            LocalPackages: google-chrome-beta-116.0.5845.82-1.x86_64 google-chrome-stable-115.0.5790.170-1.x86_64

● fedora:fedora/39/x86_64/silverblue
                  Version: 39.20230814.n.0 (2023-08-14T07:53:21Z)
               BaseCommit: 204eb7615fd250bec9c404a1080314e3a18878f0bed2301648ea554f7ee125d9
             GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C
          LayeredPackages: ibus-cangjie-engine-cangjie virt-manager
            LocalPackages: google-chrome-beta-116.0.5845.82-1.x86_64 google-chrome-stable-115.0.5790.170-1.x86_64

  fedora:fedora/39/x86_64/silverblue
                  Version: 39.20230814.n.0 (2023-08-14T07:53:21Z)
               BaseCommit: 204eb7615fd250bec9c404a1080314e3a18878f0bed2301648ea554f7ee125d9
             GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C
          LayeredPackages: ibus-cangjie-engine-cangjie virt-manager
            LocalPackages: google-chrome-beta-116.0.5845.82-1.x86_64 google-chrome-stable-115.0.5790.170-1.x86_64

  fedora:fedora/39/x86_64/silverblue
                  Version: 39.20230811.n.0 (2023-08-11T07:53:56Z)
                   Commit: 97fa93f46d0394ec590caabbdc5013ee0da6e7d8bbc0003bd645709ab67ec3af
             GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C
                   Pinned: yes

  fedora:fedora/38/x86_64/silverblue
                  Version: 38.20230808.0 (2023-08-08T00:44:53Z)
                   Commit: 0d709914c6296f56068b76024ddc35c0210a9731025b18f55f85b96b191235f7
             GPGSignature: Valid signature by 6A51BBABBA3D5467B6171221809A8D7CEB10B464
                   Pinned: yes
2

/etc/rpm-ostreed.conf is the first place I’d look!

2 Likes
3

My /etc/rpm-ostreed.conf is exactly with defaults.

With the manpage, it said “none” should be the default, but the behaviour I got sounds like “stage”.

4

This is the auto update from GNOME Software. See GNOME Software should automatically update Silverblue · Issue #87 · fedora-silverblue/issue-tracker · GitHub and rpm-ostree: Install pending updates when automatic updates are on (54da3af6) · Commits · GNOME / gnome-software · GitLab.

1 Like