Successful dist-upgrade of my #Librem5 from byzantium (bullseye codebase) to crimson (bookworm):

purism@librem5:~$ lsb_release -c
Codename: crimson
purism@librem5:~$

πŸ’ͺ

#purism

@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!

Follow

@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.

Β· Web Β· 2 Β· 1 Β· 4

@primalmotion @mistersixt @janvlug Don't get me wrong, I'd probably install it myself too just to play with it early if I wasn't working on it :) I just need to make it clear that "everything still works as expected" isn't very close to truth when I can easily identify several annoying regressions just by using it for 5 minutes and I *know* that there are many more hidden a bit deeper because I've seen what was done there and even introduced some regressions myself :)

@dos @janvlug @mistersixt Hmm. 8192 packages and I did not encounter a single dependency issue.

@nanook @janvlug @mistersixt master.pureos.net/depcheck/pur

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.

@dos @janvlug @mistersixt So far it's been operating flawlessly for me for a couple of days now.

@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.

@dos @janvlug @mistersixt I am not experiencing any of these things, epiphany is working fine no crash on launch. Perhaps your platform has problems.
@dos @janvlug @mistersixt Ok well that explains things I guess. The title, "Successful dist-upgrade of my #Librem5 from byzantium (bullseye codebase) to crimson (bookworm):" is misleading.

@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.

Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml