Is pureos crimson 11 base on debian testing?
Crimson is based on Debian 12 âBookwormâ.
You said crimson is rolling so why is it base on debian which is stable?
PureOS releases are behind Debian by one codename release:
- PureOS 10.3 âByzantiumâ (stable) â Debian 11 âBullseyeâ (oldstable)
- PureOS 11 âCrimsonâ (rolling) â Debian 12 âBookwormâ (stable)
There is currently no PureOS equivalent for Debian 13 âTrixieâ (testing).
AHH i think i get it pureos 11 crimson is stable but it merge packages from the debian testing. Example: keepassxc unstable version is 2.7.7 after that testing in unstable to move to testing version 2.7.7 and after that testing it become stable so the pureos 11 application will get updated stable applications unlike that debian pure stable which is staying in 2.7.4 which is old.
Am i correct with this?
No, Crimson is rolling and does not receive real-world testing by design.
Personally i find calling the active development branch a ârollingâ release to be disingenuous and to create confusion.
Just call it the testing/development branch since itâs not a rolling release if you plan to have it eventually stablize.
Exactly - If Iâm not wrong, Crimson is based on Debian Bookworm - which is the âstableâ version of Debian, which only gets security fixes, and (very seldom) new stuff. Even the two development repositories of Debian isnât really rolling, because they are working to release a new version of Debian, and get frozen when getting close to the new release, and then they donât get new versions of packages, but only fixes for release-critical bugs. And if a release isnât rolling always, it canât really be called rolling, can it?
BUT, with that said, Crimson does get updates from Purism in addition to the security fixes from Bookworm with fixes for their parts (fixes for the librem 5 and stuff like that). But I would very much doubt that their fixes are enough to classify the release as ârollingâ. And this is good, we want a stable operating system for our phone or computers, right?
It depends on your use case.