brent I updated my system on Friday without any issues. Today's "hot" update borked it and I had to chroot. Interesting that my other Solus PC wasn't affected.

      Solarmass I updated my system on Friday without any issues. Today's "hot" update borked it and I had to chroot. Interesting that my other Solus PC wasn't affected.

      trippy. thanks for clarifying

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

        Solarmass, thanks this helped me get up and running again.

        Friday week 19 updated with no issues, but the fix for that update broke the system, on reboot with

        [FAILED] Failed to start apparmor.service - Load AppArmor profiles., etc

          Somehow, without announcement, the updates are blocked again.
          Which is good since I can avoid the 'hot' fix. I hope.

          Was going to face the music and update but:

          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 terminated.
Hit max retry count when downloading: "https://cdn.getsol.us/repo/shannon/eopkg-index.xml.xz.sha1sum"
Please use 'eopkg help' for general help.

          it's late afternoon/night in the USA.
          Feels like I dodged a bullet?

          Solarmass So all of this worked for me, except the clr-boot-manager update step. That gives an error of "Cannot determine the currently running kernel" and I'm not quite sure why. Should I attempt to exit chroot anyway, reboot and see if the system is fixed?

            The staffs are still working on this (again), hence the shannon repo is blocked again. If you want to see the process, feel free to join the packaging room on matrix. Reilly, Evan, and many other staffs are discussing(working) the best move forward. Also as noted before if steps explained here doesn't solve your current problem, please go to support room on matrix for more personalized troubleshooting. Clearly, this is critical problem as we don't want anymore users end up in borked system. Thank you all for your patience. Cheers !

            Thanks for posting this, I'd forgotten to hit the update button and was wondering why it was sitting on the Discombobulation step just now.

            Okay, the stable repository is once again unblocked; we believe we now have a path forward.

            If you still experience issues while updating, such as if an earlier update broke your system, please follow the steps in this Help Center article to chroot into your system from a live session, and run the following commands:

            sudo ln -srvf /target/usr/bin /target/bin
sudo ln -srvf /target/usr/sbin /target/sbin

            This will perform the "usr-merge" manually, creating symbolic links for /bin and /sbin. After that, exit the chroot and reboot your system.

            Note: As a result of the fixes, eopkg check will fail on a bunch of packages. This is because of the symbolic links for /bin, /sbin, and /lib, and does not actually indicate a problem. This will be addressed at a later time.

            EbonJaeger changed the title to Temporary blocking of updates, now unblocked .

            My update script I threw together checks for broken packages each time after a system update, and at the moment it is listing the following packages as broken and reinstalling them every time I run it:
            acl apparmor attr audit bash bzip2 coreutils cpio dash e2fsprogs fuse2 glibc golang grep iproute2 iptables kmod mdadm ntfs-3g sed shadow systemd tar util-linux wpa_supplicant zsh

            I am also experiencing major lag spikes during most every operation, but I'm unsure how related to the current update that is as I just installed a new gpu (gtx 4060ti) & updated the bios version.

            EDIT: I'm sorry! Missed the part where you said eopkg check will fail. Major system stuttering/freezing is due to the new GPU, so I'll make a new thread for that.

              Kuuchuu If your system is working, it is harmless. As noted on previous post

              Note: As a result of the fixes, eopkg check will fail on a bunch of packages. This is because of the symbolic links for /bin, /sbin, and /lib, and does not actually indicate a problem. This will be addressed at a later time

              Also please try update it normally using sudo eopkg upgrade, then reboot. Reinstalling all those "broken" packages over and over will not solve the issue until it is addressed on later date.

                EbonJaeger If you updated previously, and now your system is broken

                Do people who ran the initial update without experiencing any obvious issues need to take any action?

                    EbonJaeger

                    I just updated Solus (36 packages, 63.24 MIB).

                    I was able to use Solus normally after reboot:

                    • gedit is again in my native language (French),
                    • Firefox just asked me if I wanted to make it my default internet browser.

                    But when I typed the terminal command sudo eopkg check, I got a lot of anomalies:
                    https://0.0g.gg/?d657e6008a0ce8ab#5HpsHDSjDgMQJnDGwA3R9KnmE8depAPSSaYeC2TYiV7b

                    Should I also use the commands you recommend above to fix them?

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

                    Waiting for your feedback, I remain at your disposal.

                        Sebastian
                        Assuming you have updated again and rebooted, no there is nothing more you need to do.

                          penny-farthing But when I typed the terminal command sudo eopkg check, I got a lot of anomalies:

                          From this post: https://discuss.getsol.us/d/10599-temporary-blocking-of-updates-now-unblocked/36

                          Note: As a result of the fixes, eopkg check will fail on a bunch of packages. This is because of the symbolic links for /bin, /sbin, and /lib, and does not actually indicate a problem. This will be addressed at a later time.

                          So no, if you have updated, rebooted and your system is working ignore the errors, its fine.

                              no issues with the new update here, didnt have any with the original one either though
                              also, thanks for the new papirus!

                              I'm closely monitoring this situation.

                              I have yet to sync Week 19 updates.
                              I also have not installed Week 19 hotfix

                              I have previously updated to Week 18.

                              Is it safe for me to sync now?
                              Or should I wait for Week 20 Friday sync?

                                snowee It should be safe now. As always if problem arise, please check over help center on how to recover your system. Also feel free to ask support on support room on matrix. Cheers!