Heya folks, due to an update issue that was not caught before sync that can result in a broken package manager, we're temporarily blocking updates from being downloaded. While this issue is being addressed, updates will not be able to be downloaded, nor will new packages be able to be installed.

We apologize for the inconvenience, and will update you as soon as we have more information.

    EbonJaeger What about this week's update that's done already? Is anything broken as a result?

      As an update, we're still working on safely rolling back the problematic update. After that, we have to come up with a safer way to perform the "usr-merge" for the /bin and /sbin directories.

      Thank you for your patience.

      We are currently testing a solution to reverting the /bin and /sbin merge. Initial results are promising, but additional testing is needed, and the situation will be re-evaluated tomorrow morning.

      If you are on the Unstable repository, please head on over to our Packaging Matrix channel if you would like to help test.

      Thanks!

      It does look like eopkg situation is a show stopper for package maintenance too. Keep us updated. Thanks.

      Hi ... I have this output :

      home@linux ~ $ sudo eopkg up
      Depots are actualized
      Depot is actualized: Solus

      Failed to fetch file, retrying 1 out of 5 "https://cdn.getsol.us/repo/shannon/eopkg-index.xml.xz.sha1sum": HTTP
      Error 403: Forbidden

      Failed to fetch file, retrying 2 out of 5 "https://cdn.getsol.us/repo/shannon/eopkg-index.xml.xz.sha1sum": HTTP
      Error 403: Forbidden

      Failed to fetch file, retrying 3 out of 5 "https://cdn.getsol.us/repo/shannon/eopkg-index.xml.xz.sha1sum": HTTP
      Error 403: Forbidden

      Failed to fetch file, retrying 4 out of 5 "https://cdn.getsol.us/repo/shannon/eopkg-index.xml.xz.sha1sum": HTTP
      Error 403: Forbidden

      Failed to fetch file, retrying 5 out of 5 "https://cdn.getsol.us/repo/shannon/eopkg-index.xml.xz.sha1sum": HTTP
      Error 403: Forbidden
      Program ended.
      Hit max retry count when downloading: "https://cdn.getsol.us/repo/shannon/eopkg-index.xml.xz.sha1sum"

      I have retried with same results. Do not hurry, we are patient.

        DirtyAngel Yes, that is the expected output for the time being, until the problem with the packages has been fixed and the repository is activated again.

          presianbg In the worst case scenario pretty much the whole system is affected, and then even eopkg4-bin won't work correctly (PAM permission issues) without workarounds. That's why the repository was disabled completely as a safety measure, so the updates that can cause this issue for certain configurations won't be applied to more users' systems. To be fair that case should be pretty rare and only affect systems that haven't been updated for a number of weeks, but it's not fun when it happens.

            Affirmative! Good to know that the issue is severe yet rare.

            Breaking news! Access to the stable repository has been restored! Steps have been taken to ensure that upgrading is once again safe.

            If you updated previously, and now your system is broken, you will have to follow the steps here to chroot into your system from a live USB session and fix it manually. Depending on where in the upgrade it failed, doing the chroot step may fail because executables are not where they are expected to be. To fix this, add links to them from the live session, for example with Bash:

            sudo ln -srvf /target/usr/bin/bash /target/bin/bash
sudo ln -srvf /target/usr/bin/bash /target/bin/sh

            It may be necessary to repeat this for multiple files before chrooting will succeed. Hop into Solus Support Matrix or post in this thread if it still doesn't work after this for more personalized instructions.

            Once you have successfully chrooted into your system, running sudo eopkg upgrade should upgrade and fix your system.

            A more detailed explanation of what happened will be posted at a later time, once everything has settled. Thank you for your patience and understanding during this event.

              EbonJaeger What is the newest software update my Solus just alerted me to? What is it for? Is it for everyone? My previous update this week was uneventful.

                  elfprince It safely reverts the attempt at a /usr merge until we implement a way to make it safe for everyone, no matter how long ago you last updated. It also ensures that systems won't break, and/or will be fixed, during the update.

                      EbonJaeger [✓] Syncing filesystems success
                      [✓] Updating clr-boot-manager success
                      [✓] Updating hwdb success
                      [✓] Updating system users success
                      [✓] Updating systemd tmpfiles success
                      [✓] Reloading systemd configuration success
                      [✓] Re-starting vendor-enabled .socket units success
                      [✓] Re-executing systemd success
                      [✓] Compiling and Reloading AppArmor profiles success
                      [✓] Compiling glib-schemas success
                      [✓] Updating mimetype database success
                      [✓] Updating icon theme cache: hicolor success
                      [✓] Updating icon theme cache: Papirus success
                      [✓] Updating icon theme cache: Papirus-Adapta-Nokto success
                      [✓] Updating icon theme cache: Papirus-Light success
                      [✓] Updating icon theme cache: solus-sc success
                      [✓] Updating icon theme cache: Papirus-Dark success
                      [✓] Updating icon theme cache: Papirus-Adapta success
                      [✓] Updating desktop database success
                      [✓] Updating manpages database success
                      [✓] Ensuring usr-merge consistency success
                      [✓] Reloading udev rules success
                      [✓] Applying udev rules success
                      System error. Program terminated.
                      [Errno 21] Is a directory: 'usr/share/bash-completion/completions/onefetch'
                      Please use 'eopkg help' for general help.
                      Use --debug to see a traceback.                      Is this normal?

                        My newest update after above resulted in $ sudo eopkg up
                        bash: /bin/sudo: No such file or directory                        WHAT NOW?

                        elfprince Not exactly the definitive answer but I have just run the latest updates on two previously successfully updated machines without any ill effects. Everything downloaded and installed without issue and the system still seems to be working well after a reboot.
                        I am guessing that they are for us too, if we don't install them now they will still be waiting for us on next week's update.
                        Congratulations to all team members on your swift fix. I'm sure it has been a very long day for you. The dedication and support to Solus is very much appreciated 👍

                          Oh, perhaps I should reboot first, before applying the latest batch of updates. lol