Temporary blocking of updates, now unblocked

Axios Don't blame you. If they said 20 broken packages was normal I missed it
trying the old
sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall
then the old
sudo usysconf run -f
and will reboot and check again. thanks for responding.

Axios I'm going to hold off personally on the rest of my devices until this is completely sorted out. My laptop was one that got hit with the initial problem, it's working now, but I can't risk being down for work (or games!).

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

everything just works ️

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%)?

zmaint

If we did not believe so, we would have disabled access to the repository again.

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!

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