Half-Baked 2024Q4 repo cooked my system

pfr

basically this:
https://mail-index.netbsd.org/pkgsrc-bugs/2024/12/28/msg073527.html

This exact scenario happened to me. For me, it was more than just firefox that I lost. I lost my entire LXQt desktop environment. I acknowledge the "may be reasonably described as user error" however, the fact remains that a broken build was released to the public. This shouldn't happen. I moved back to stable because I did not want the hassle of things breaking on Current or HEAD. How ironic. 😆

However, I didn't come here just to complain, although I was extremely annoyed when it happened and I probably wont tolerate something like this happening again. If I have to rebuild my system or perform a clean install I'll likely move back to Void Linux. I came here to shed light on this situation, and also for advice. @pin has already advised me to wait until a new build is released. 🥱 Let wait and see hey...

Anyone else in this boat besides me and the user referenced in this bug report?

kc9udx

pfr to be fair you didn't lose your desktop environment. You lost the ability to use it. It'll be back exactly how you had it when you get the packages straightened out. How do I know? I have to build KDE4 on 3 ports every time I change to a different pkgsrc release. I just today finished doing that for 2024Q3 on i386. It took a month.

BTW, pkgin autoremove will never cause missing dependencies; upgrading a package that has inconsistent dependency requirements will cause that.

Since you mentioned me ...

In case you didn't do anything else to the system, waiting for a new build and running update and upgrade, should fix your system. Provided that, this new build contains all the packages which are currently broken.

In case you did try further actions in an attempt to fix the system, you might need to remove broken packages before running the new update and reinstall them from the new build.

In any case, make sure this new build contains everything you want.

pfr

pin Thanks. As I mentioned over matrix, I did do a silly thing and ran pkgin autoremove which did remove about 8 packages (before I realised what was happening and aborted), I now have unresolved dependencies.

Will post exactly which ones in a bit..

bsduck

Couldn't you just point pkgin back to 2024Q3 and force a reinstall of all packages?

@pfr this looks much better.

Do check if everything is available, https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/10.0_2024Q4/All/

pfr

Ok, I've updated from the new branch, and it's still quite broken.

I'm not really sure what to make of this, but it doesn't look good.

Xorg.0.log

Edit
Like like my entire desktop was gone... Well, LXQt was nowhere to be found.

Reinstalled LXQt and we're back.

pfr I've updated from the new branch, and it's still quite broken.

I'm not really sure what to make of this, but it doesn't look good.

What does this have to do with pkgsrc packages?

... nothing.

pfr

pin 😅 well, this is clear to me now. But startx failed and the error message said to check xorg log so I just figured...
Nevermind.

kc9udx

The times they are a-changing! I am overjoyed to be getting rid of Debian on an important machine which has an inbuilt video card that did not work with NetBSD. I had been meaning to try it with 10.0, but yesterday I found out I only have until March 15 to update Debian. So I installed NetBSD 10.0 and it works!!

I immediately upgraded to 10.1, and installed pkgsrc 2024Q4. Then I noticed kde-20240828 in the binary repository! I think the last time I didn't have to build KDE from source, I was running NetBSD 8.x

So I wonder if you've considered 10.1 or if you are using 10.0 stable?

kc9udx

Since it worked so good on that machine, I decided to upgrade my main server from 10.0 STABLE and 2024Q3 to 10.1 and 2024Q4. And what you experienced happened to me; which has happened to me in the past when doing an upgrade.
My solution is just to pkgin export > pkglist and pkgin uninstall all but the most simple packages, and then pkgin autoremove. Then I reinstall all packages based on the list in the file pkglist. It's not the most ideal way to have to deal with this but it works well every time. I'm pretty sure this is just normal for pkgsrc and again isn't ideal but it's just not the end of the world.

Something else I do, is I wrote a script to export all installed packages as binary packages; and I do that in case something is missing in the new pkgsrc branch that I really need. Such missing package problems have always been resolved in future branches, and I haven't encountered any such problems going to the last two most recent branches.