brent The packages are not broken, the package check itself is not handling them correctly. This was mentioned above as eopkg check showing errors, and is expected.

Basically eopkg sucks as a package manager (which is why we're replacing it) and due to it's constraints we found that satisfying all of the following was impossible:

  • Allowing people who didn't upgrade to the Friday sync to update and have working systems
  • Allowing people who did upgrade to the Friday sync to update and have working systems
  • Having a "clean" eopkg check that succeeds for all packages.

Given these constraints we chose the solution that satisfied the first two requirements. That means that eopkg check will show that certain packages (between 20 and 30 depending on what you have installed) are "broken" which is just because it can't handle how the symlinks on the system are setup, not because those packages are actually broken.

      Also, I edited your post but please don't paste walls of text without enclosing them in triple backticks please. See here for how.

      ReillyBrogan That means that eopkg check will show that certain packages (between 20 and 30 depending on what you have installed) are "broken" which is just because it can't handle how the symlinks on the system are setup, not because those packages are actually broken.

      that's exactly what is going on. forgive me if I missed the fine print, apparently I did. A third check shows all the same stuff "broken".
      what threw me:
      1) when the eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall command just showed complete success and nothing broken
      2) when sudo eopkg check shows 20 packages broken

      these 2 contradictions exist in the output but if it's all good I'll go about my business. appreciate the clarity. I am calm🙂

          • [deleted]

          • Post #65

          everything just works 👍️

          brent command just showed complete success and nothing broken

          eopkg check without sudo can't access some directories and might show the package status as "Invalid".
          Example:

          Checking integrity of shim-signed                                      Unknown
Access denied: /usr/lib64/shim/BOOTX64.CSV
Access denied: /usr/lib64/shim/fbx64.efi
Access denied: /usr/lib64/shim/mmx64.efi
Access denied: /usr/lib64/shim/shimx64.efi

          Also depends on what you mean by "complete success". That command will reinstall all packages that are detected as broken. Success in that case just means that everything has been reinstalled, it doesn't mean there are necessarily no more broken packages in situations such as this, when the check isn't adequate.
          Anyway, if that command does any sort of package installation then it has detected broken packages indeed. In fact it will only fail if there are NO broken packages (using xargs -r fixes that, which is also reflected in the Help Center documentation now)

              Staudey when I sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall this morning the result was:

              Installing 24 / 24
iproute2-6.8.0-24-1-x86_64.eopkg [cached]
Installing iproute2, version 6.8.0, release 24
Extracting the files of iproute2
Installed iproute2
 [✓] Syncing filesystems                                                success
 [✓] Updating dynamic library cache                                     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
 [✓] Compiling and Reloading AppArmor profiles                          success
 [✓] Updating mimetype database                                         success
 [✓] Updating manpages database                                         success
 [✓] Reloading udev rules                                               success
 [✓] Applying udev rules                                                success

              that why I used the 'success' word but you are right there is a lot unconsidered by me after reading you.

              Staudey Success in that case just means that everything has been reinstalled, it doesn't mean there are necessarily no more broken packages in situations such as this, when the check isn't adequate.

              but that command implicitly looks for broken (..grep Broken..) so I assumed repair would be a consequence of the command.

              Staudey In fact it will only fail if there are NO broken packages (using xargs -r fixes that, which is also reflected in the Help Center documentation now)

              now that says it all. gotcha. thanks for deciphering my inability to decipher!

                    Are we now good to go with updating as normal (with just the temporary caveat that eopkg check isn't working 100%)?

                      Terry1031 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,

                      The latest update to baselayout should improve this situation.

                      Updating from a fresh 4.5 ISO install or potentially from an install that has not been updated in several weeks may still fail. But you should be able to just update again sudo eopkg up -y and have it complete successfully (Reboot once it is completed). At least that was the case for me on a fresh 4.5 install.

                      I recommend anyone seeing an error similar to this:

                      Installing 47 / 699
baselayout-1.9.0-81-1-x86_64.eopkg [cached]
Installing baselayout, version 1.9.0, release 81
Upgrading to new distribution release
Extracting the files of baselayout
System error. Program terminated.
[Errno 2] No such file or directory: 'bin'
Please use 'eopkg help' for general help.
Use --debug to see a traceback.

                      To not reboot and simply try updating again.

                      Unfortunately it may be impossible to support updating from every possible system state without some clunkiness like this.

                      Apologies for the inconvenience.

                          Harvey I can confirm rerunning the update fixed this issue for me on a laptop that hadn't been updated in a while, thanks!

                            Harvey
                            for those who have sync'ed to Week 18 but not to Week 19, should they install baselayout first, prior to sync'ing to Week 19?

                                snowee
                                You shouldn't need to, worst case scenario you have to run sudo eopkg up -y twice.

                                  Harvey Thank you sir. I appreciate all the work you guys have done on this!

                                    Here I had no attempt with update on last Friday.
                                    I made update yesterday evening and it went smooth.
                                    Here is Solus Gnome with Gnome 46.1
                                    Thank you !!
                                    (Last update was one week ago.)

                                    Hi there.
                                    After my heart surgery i was on rehab for 3 weeks.
                                    So no updates for about 4 weeks are installed.
                                    Is it safe to update now or should i wait a few more days ?

                                      Would this show up as a problem with extracting base-layout? After a clean install and attempting to update..it hangs at that point. while installing updates. Initial install and reboot is fine.. (Budgie DE) After a restart it crashes.

                                        PC-TECH so 2 different things are happening at the same time? A crash on restart? and before that the updates hung up?
                                        use the terminal for updates (sudo eopkg up) then try to reboot. if its crashed then one of the ctrl+alt+someFkey will get you a terminal

                                            MikeK61 Is it safe to update now or should i wait a few more days ?

                                            hope your heart is on the road to happy! 💗
                                            should you update after missing 4 cycles of updates?
                                            kinda safe answer: no guts, no glory
                                            safer answer: wait til Friday. I think the crew is trying to iron out one more issue
                                            2 cents to be sure, as I'm not answering as a Dev

                                              brent Not at the same time. After the initial install which works fine , reboots & logins correctly . Then when you do system updates it downloaded about 400 packages, then proceeds to installing updates..it hangs at extracting base-layout...If you shutdown from that point and restart it crashed after login. ...with a frowning computer no less. Perhaps I did wait long enough for that package to extract?? I waiting for 20 ish minutes...observing no activity on the HDD indicator in the time. I can certainly repeat this using the CLI.
                                              Back ground info. I'm doing a virgin install on a computer that was running Solus Budgie from the original version. I decided to "de-kluge" the system So I know it capable of running Solus. Thanks for any help.

                                                  PC-TECH baselayout was a package rolled out last night to address a couple wrinkles. maybe it conflicts with ISO?
                                                  I wish I could help but it's brand new and I am going to defer to a DEV or Maintainer on this one.