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.

    • milon@lemm.eeOP
      1·
      20 hours ago

      I have two entries each with a different BaseCommit. One has dnf-automatic, libreoffice, vpn app. The other has the same three plus rpmfusion-free-release and rpmfusion-nonfree-release.

      I just recently installed the rpmfusion packages but I didn’t know what I was doing. Just found something online suggesting an alternative update method for Silverblue.

      • pogodem0n@lemmy.world
        8·
        19 hours ago
        • dnf-automatic looks a like a package designed for non-Atomic versions of Fedora.
        • libreoffice is available as a flatpak. You should avoid layering packages as much as possible.
        • A VPN app makes sense to have layered. I assume it comes from a third-party repository added to /etc/yum.repos.d. It is possible this package does not support Fedora 42 yet. You can try removing it to see if the update succeeds.
        • rpmfusion is a repository providing packages that often cannot be pre-installed due to some legal reasons. Unless you need/installed a package from there, uninstall it.
        • milon@lemm.eeOP
          1·
          19 hours ago

          So basically it’s not allowing me to update because of these layered packages and every time I want to update, I have to uninstall them and reinstall after I update?

          • pogodem0n@lemmy.world
            6·
            19 hours ago

            Kind of. Atomic versions of Fedora are designed to be set it and forget it kind of distro. New releases can cause issues with third party packages.

            • milon@lemm.eeOP
              4·
              19 hours ago

              It worked! I uninstalled dnf-automatic, libreoffice, and rpmfusion and then restarted.

              Thanks for your help! Will keep your tips in mind for the future and try to avoid layering.

            • milon@lemm.eeOP
              1·
              19 hours ago

              Also, as I reinstall a flathub version of LibreOffice, should I choose the Fedora repo or Flathub repo?

              • pogodem0n@lemmy.world
                3·
                18 hours ago

                Fedora version has been packaged by Fedora Linux developers, while the other is published by LibreOffice developers themselves. The former may be only slightly out of date. Choose whichever one you feel comfortable with.

  • Telorand@reddthat.com
    4·
    21 hours 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·
      19 hours 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·
          6 hours ago

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

          • Telorand@reddthat.com
            1·
            4 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.

  • blobjim [he/him]@hexbear.netEnglish
    1·
    19 hours ago

    Do you have “dnf” installed specifically? What layered packages do you have? I ran rpm -qa on my system and didn’t find any packages containing “dnf”

    Also not sure if it’s useful but here’s my ostree remote list --show-urls output:

    fedora          https://ostree.fedoraproject.org/
fedora-compose  https://kojipkgs.fedoraproject.org/compose/ostree/repo/

    I also always have the same issue trying to use the UI. I had to use rpm-ostree rebase for the upgrade to 41 and 42, but it worked for me with no issues.

    • milon@lemm.eeOP
      2·
      19 hours ago

      Turns out the issue was with one or some of the layered packages I had. After uninstalling, the CLI method to upgrade worked. See the post below, but thanks for your reply.

  • Ulrich@feddit.orgEnglish
    12·
    21 hours ago

    I’m not an expert but it looks like you’re using the wrong command. You’re not trying to rebase, just update

    $ rpm-ostree update