@mistersixt Wow. Is everything working? How is the stability?
@janvlug Yes, it is... to be honest I expected some serious issues, but the upgrade itself was flawless, and everything still works as expected. So... thumbs up!
@mistersixt @janvlug Crimson isn't even ready for developers yet, let alone users. There are many regressions over byzantium, many broken dependencies and many non-installable packages there. It was just barely cleaned up enough for images to build last week, and plenty of work is still needed to put it into shape. You can run it if you want, sure, but expect problems and don't expect any support.
@nanook @janvlug @mistersixt https://master.pureos.net/depcheck/pureos/crimson/binary/arm64/1
And there was some cheating too - several vital packages got their patches dropped instead of rebased to get the images into buildable and testable state faster.
It's just not ready yet. If you use it regardless, you're 100% on your own.
@nanook @janvlug @mistersixt You must have a pretty low threshold of "flawless" then. Even hiding the splashscreen on app launch is broken right now, it always waits for the timeout to pass. Epiphany crashes on launch. No way to copy things from terminal. File diaglos aren't adaptive. Typing with OSK is broken whenever GTK4 shows a completion popup. And those are just the immediately visible ones, there are many more under the hood.
@nanook @janvlug @mistersixt We're talking about crimson, not bookworm.
@nanook @janvlug @mistersixt crimson is based on bookworm, but all the PureOS-specific changes need to be updated too and we're not done yet, so things remain broken meanwhile.
@dos @nanook @janvlug thanks for clarifying things, I was not aware of that current situation.
I was simply expecting a completely broken system to be honest, and the way I currently use it (not as a daily driver) it just works fine. I am aware of possible flaws and errors.