Solus Unstable in a VM, bricked after updating

dotWayton

Howdy folks i run Solus on two pc's one of which i run it as a VM that i use for working on packages, I definitely could just delete the VM and spin up another (but i have already setup all the packaging tools so if i can save the time from resetting those back up) that would be ideeal.

any tips?

alfisya

You can try following these rescue steps.

A little tips on working in VM: You can set up a snapshot on VM, so you can restore to that point if anything goes wrong.

pomon

I had this image appear a few times after an update. In my case, reinstalling Mesa helped:
sudo eopkg it --reinstall mesalib mesalib-32bit

dotWayton

Cheers for the reply folks,
after some troubleshooting it seems like the best method is to just suck it up and rebuild my build enviroment and then setup a snapshot later on 🙂

Thankfully the package i was working on (Zafiro Icons - KDE style icon theme)
https://github.com/getsolus/packages/pull/7658

Had the most recent progress and fixs required for merging committed and off the machine and onto the internet.

Harvey

If you are not aware. People on unstable need to be in our packaging matrix channel and paying attention to the topic before updating. If it says do not update and you update, you could break things.

Yesterday this was the case for a llvm update.

I wouldn't advise installing anything / building packages during this sort of thing either unless you know when it would impact you or not.