Bluefin Updaters all wonky

After the latest update, ujust update only checks rpm-ostree and homebrew (which it had stopped doing for a while) and topgrade is using dnf and failing with a SQL error.

[14/14] Total                                                                                                                                                                                                                                       100% |  11.1 MiB/s |  17.9 MiB |  00m02s
Running transaction
SQL statement evaluation failed: "
    INSERT INTO
        "trans" (
            "dt_begin",
            "dt_end",
            "rpmdb_version_begin",
            "rpmdb_version_end",
            "releasever",
            "user_id",
            "description",
            "comment",
            "state_id",
            "id"
        )
        VALUES
            (1738841843, 0, '3423ac401adc046575a6bcbc36112cee241d617438aa630ae21782eb7ba21897', '', '41', 1000, '/usr/bin/dnf upgrade', '', (SELECT "id" FROM "trans_state" WHERE "name" = 'Started'), NULL)
": (8) - attempt to write a readonly database
System update failed:
   0: Command failed: `/usr/bin/sudo /usr/bin/dnf upgrade`
   1: `/usr/bin/sudo` failed: exit status: 1

Location:
   src/steps/os/linux.rs:250
Retry? (y)es/(N)o/(s)hell/(q)uit⏎

ujust update now checks system, flatpak and homebrew updates. Distroboxes, fwupd were removed as topgrade was really wonky and was breaking updates.

The plan at some point is to switch to the new uupd updater, once it is deemed ready.

Same here, but I was able to get around it. @j0rge will likely point out where I went wrong, but I was curious. It did fix it, though. :laughing:

Was on Version: latest-41.20250204

Like you, got a:

All the stuff before this below....then this error.

Running transaction
SQL statement evaluation failed: "
    INSERT INTO
        "trans" (
            "dt_begin",
            "dt_end",
            "rpmdb_version_begin",
            "rpmdb_version_end",
            "releasever",
            "user_id",
            "description",
            "comment",
            "state_id",
            "id"
        )
        VALUES
            (1738845811, 0, 'ab7219bdb968f1b7c7547738457ba1e3cf1b75f050f9f321c72fa62d35d668f2', '', '41', 1000, '/usr/bin/dnf upgrade -y', '', (SELECT "id" FROM "trans_state" WHERE "name" = 'Started'), NULL)
": (8) - attempt to write a readonly database
System update failed: 
   0: Command failed: `/usr/bin/sudo /usr/bin/dnf upgrade -y`
   1: `/usr/bin/sudo` failed: exit status: 1

Location:
   src/steps/os/linux.rs:259
Retry? (y)es/(N)o/(s)hell/(q)uit

So just for giggles, I did one of these:

rpm-ostree reset

Then switched over to stable:

sudo bootc switch ghcr.io/ublue-os/bluefin:stable

Reboot.
Update there was smooth. So, being the daring sort, did this:

sudo bootc switch ghcr.io/ublue-os/bluefin:latest
Reboot.
This gave me the same errors again, but I allowed it to finish, rebooted.

Now on: latest-41.20250206

And now I am rocking:

ujust update
note: automatic updates (stage) are enabled
Pulling manifest: ostree-unverified-registry:ghcr.io/ublue-os/bluefin:latest
No upgrade available.
Looking for updates…

Info: runtime org.kde.Platform branch 6.6 is end-of-life, with reason:
   We strongly recommend moving to the latest stable version of the Platform and SDK
Info: applications using this runtime:
   com.obsproject.Studio

Info: (pinned) runtime org.gnome.Platform branch 45 is end-of-life, with reason:
   The GNOME 45 runtime is no longer supported as of September 18, 2024. Please ask your application developer to migrate to a supported platform.

Nothing to do.
==> Updating Homebrew...
Already up-to-date.

Where I live now, currently:

sudo bootc status

â—Ź Booted image: ghcr.io/ublue-os/bluefin:latest
        Digest: sha256:abbecbd26d0f47d1a85bdcfc8295fe543a0f02f18e9c5cc7650ef76c4d510014
       Version: latest-41.20250206 (2025-02-06 05:02:24 UTC)

  Rollback image: ghcr.io/ublue-os/bluefin:stable
          Digest: sha256:12fefae335b0ba23ca0380a589cbf1de8ca1042e2fe7782829f1e84c892bbdd4
         Version: 41.20250202.1 (2025-02-02 05:59:53 UTC)

I love that at no time, was my system non-bootable. It was a minor inconvenience, 5 minutes and resolved. Wild.

So it seems like my issue was with:

latest-41.20250204

and by jumping to stable, then back to latest, I was able to get to:

latest-41.20250206

My daily box lives on gts for a reason. I knew what I was doing by using latest.

1 Like

Again, I am sure there are better ways to do this. I just went all YOLO on it.

And had I slept last night, I would have realized I could have also just done

ujust rebase-helper

Choose:                     
> date                      
  latest                    
  stable                    
  stable-daily              
  gts                       
  cancel 

But I was not awake enough to brain that one.

Yeah, the manual updater went through a journey the past day or so as we moved Bluefin to dnf, but it only affected running the command by hand. People on the default weekly builds weren’t affected.

The automatic updates will pick up the update anyway, so if you’re still seeing this just wait and it’ll resolve itself.

1 Like

That’s odd. My sudo bootc status doesn’t return as much as yours.

sudo bootc status
[sudo] password for guru:
â—Ź Booted ostree
           Commit: 06f7c91ee8609b05581f4be3ca13485ec7150f70ac1730243a5e3e6d772a8339

  Rollback ostree
           Commit: cd33256e42a181c517258b6fb6b9f2d13e561e70cd613f05ae606d873fad1583

Also, I can’t upgrade using bootc as it doesn’t support layering apparently. I get the following:

sudo bootc update
ERROR Upgrading: Deployment contains local rpm-ostree modifications; cannot upgrade via bootc. You can run `rpm-ostree reset` to undo the modifications.

And what does happen if you use just the rpm-ostree upgrade command?

1 Like

That behaves as expected.

rpm-ostree update
note: automatic updates (stage) are enabled
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-nvidia:stable-daily
Checking out tree 59b445d... done
Enabled rpm-md repositories: google-chrome fedora updates rpmfusion-nonfree-nvidia-driver rpmfusion-nonfree-steam copr:copr.fedorainfracloud.org:phracek:PyCharm copr:copr.fedorainfracloud.org:pgdev:ghostty updates-archive
Updating metadata for 'updates'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'google-chrome' (cached); generated: 2025-02-05T21:19:17Z solvables: 4
rpm-md repo 'fedora' (cached); generated: 2024-10-24T13:55:59Z solvables: 76624
rpm-md repo 'updates'; generated: 2025-02-06T01:21:18Z solvables: 19354
rpm-md repo 'rpmfusion-nonfree-nvidia-driver' (cached); generated: 2024-12-17T11:02:42Z solvables: 17
rpm-md repo 'rpmfusion-nonfree-steam' (cached); generated: 2024-12-02T07:45:38Z solvables: 2
rpm-md repo 'copr:copr.fedorainfracloud.org:phracek:PyCharm' (cached); generated: 2024-12-16T12:28:59Z solvables: 10
rpm-md repo 'copr:copr.fedorainfracloud.org:pgdev:ghostty' (cached); generated: 2025-02-05T19:33:28Z solvables: 74
rpm-md repo 'updates-archive'; generated: 2025-02-06T02:14:55Z solvables: 28056
Resolving dependencies... done
No upgrade available.

My concern is the switch to bootc/dnf will kill the ability to overlay applications.

Kube-anything is meaningless gibberish to me.

Sorry.

How will we overlay apps in the coming cloud-topia? Please use the normie vocabulary. Videos are too slow for me (I read 1200 wpm). I use bluefin because I need a Linux that is sufficiently cutting-edge but won’t blow up on me catastrophically on a monthly basis. I am not a cloud dev. I was old-school IT for 38 years. I can only visualize containers as VM’s with an App Store.

1 Like

6 Likes

Thank you for tolerating a cantankerous old IT guy.

3 Likes

If at any reason an update doesn’t seem to be working… just run rpm-ostree upgrade

Topgrade on version 16.0.2 is broken on bootc images so we have downgraded to 15.0.0 (hopefully topgrade gets an update soon since the fix has already landed)

But everything in bluefin has gone back to older systemd service based updates.

We also have uupd currently cooking. It’s in use on bluefin-lts right now.