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!

                        I run updates on all my computers/OS's Mondays so I missed out on the fun. I think I'm going to wait on this a bit longer.

                        Now on to see what fiasco Windows has come up with this week.

                        I was able to update and reboot without issue on my laptop that was previously not working. No pickle problems this time around either.

                        Solus Budgie-Desk:
                        i had done fridays updates: no issues
                        now i did the new updates: no issues, system seems to work normal.

                        BUT during boot there was always a box where you can choose if you want to boot into:
                        -SOLUS
                        -SOLUS - Advanced options

                        with this latest update the box only gives the option for SOLUS.
                        the SOLUS-Advanced options seem to got lost.
                        is this meant to be?
                        i re-booted twice to check.

                          BTO It is fine. It just means you don't have previous version of kernel anymore. It gets cleaned up automatically once in a while. If you install LTS kernel/linux-lts, or there is new kernel update, it will show up again and will show you options to boot to other kernel.

                          • BTO replied to this.

                              alfisya OK, big thanks for the explanation!
                              Then everything should be fine :-)

                                The new update bricks itself at the point of trying to install baselayout package, it doesn't end up finding sbin (not 100% sure anymore, might've been bin) from that point on it doesn't continue the update and I can't open up any programs like FireFox or the Terminal.
                                Tried it on a complete fresh install and it still happens, from my limit understanding I'd make an educated guess and assume that it is due to the new systemd standard.

                                  Updated yesterday. Rebooted today and updated again. Rebooted. All is normal on Solus Budgie, so far.

                                  Terry1031 I'd make an educated guess and assume that it is due to the new systemd standard.

                                  It's a Solus baselayout package problem. This package puts in place the basic "skeleton" of the system (including directories) that forms the foundation of how Solus is organised on disk.

                                  Ironically, the change was made in preparation for upcoming systemd updates that require /bin and /sbin to be merged into /usr/bin and /usr/sbin respectively. It's a good idea in principle, but the unfortunate reality is that we missed certain outcomes in our internal testing coverage.

                                  The team is working on sussing out a good solution.