I am trying to update from Silverblue 41 to 42 (fully updated) but run into issues when attempting to update from both the software app and from CLI.

The problem using the software app is the same as what is described by this other user, who is using Fedora Workstation not Silverblue like I am:

https://discussion.fedoraproject.org/t/update-to-fedora-42-fails-in-gnome-software/148885

When I click the download button, it looks like it’s downloading multiple files since the progress bar goes from 0 to 100 several times, and then it gets up to 95% then suddenly returns to the download button. This happens in about 30 seconds.

Using the CLI method, I run the following command:

rpm-ostree rebase fedora:fedora/42/x86_64/silverblue

and get the following errors:

 Problem: conflicting requests
  - package dnf5-plugin-automatic-5.2.12.0-2.fc42.x86_64 from updates requires libcurl-full(x86-64), but none of the providers can be installed
  - package dnf5-plugin-automatic-5.2.12.0-1.fc42.x86_64 from fedora requires libcurl-full(x86-64), but none of the providers can be installed
  - package dnf5-plugin-automatic-5.2.12.0-2.fc42.x86_64 from updates-archive requires libcurl-full(x86-64), but none of the providers can be installed
  - package libcurl-minimal-8.11.1-4.fc42.x86_64 from @System conflicts with libcurl(x86-64) provided by libcurl-8.11.1-4.fc42.x86_64 from fedora

SOLUTION: Uninstalled layered packages in dnf-automatic, libreoffice, and rpmfusion and then restarted. Rebase command successfully completed thereafter.

  • Telorand@reddthat.com
    4·
    1 day ago

    For the “none of the providers can be installed” errors, there’s likely been a package name change or removal in 42. I ran into a similar issue with Bazzite. I uninstalled the offending package, then reinstalled after the update.

    The last one says there’s a package conflict. You’ll need to remove the one you have in order to proceed.

    • milon@lemm.eeOP
      1·
      1 day ago

      Problem is I don’t know what the packages are or what they were for even. I don’t recall installing them.

        • milon@lemm.eeOP
          2·
          13 hours ago

          Yes, I did. I was warned about doing so before but now I understand 😆

          • Telorand@reddthat.com
            1·
            11 hours ago

            Layering isn’t bad, but what happens is with each update, the system tries to re-layer each of those packages. If some are missing from the next deployment’s rpm database or have been superceded by another package, you’ll run into these kinds of issues.

            In my case, for example, my next deployment was missing java-17-openjdk, because it had been superceded by other metapackages.