Pureos rolling release


#1

I see a repo called byzantium with recent files on your repo lists. Is this the new rolling release and is it ready to install? I miss my rolling release ;-).

TIA


#2

Hes this is the repo for the equivalent of Debian Testing. As for it’s status @jeremiah would be the best person to reply to that question.


#3

I think it might be ready for experimental testing, yes. Please note, I’ve only done cursory testing but once I added ‘byzantium’ to my /etc/apt/sources.list I had well over 1,000 updates. I don’t know how well these updates work with my current amber based system. Caveat emptor!


#4

I added byzantium too and will update in batches as long as it works.


#5

I’m thinking that this is not a generic Debian Testing repo, but modified by pureos. Is it also security maintained and is there any attempt to make it at least as usable as the prior rolling releases. I found the rolling release to be very stable.


#6

Because it is based on Debian Testing, it get’s Debian Security support. We do add some PureOS specific things, but we try to keep that to a minimum.


#7

I just upgraded successfully to byzantium. I used synaptic and upgraded the packages in batches between 20 to 100. Only phonon-backend made problems.


#8

Did you see any change in your encryption setup (if you’re using LUKS)?


#9

I do not use LUKS. When there is an ISO byzanitum, I will setup my laptop again with disk-encryption, When I set up my Laptop for the first time, I did not succeed in encrypting my hard-disk. I do not know the reason why.


#10

also from : https://www.debian.org/releases/bullseye/

Please note that security updates for “testing” distribution are not yet managed by the security team. Hence, “testing” does not get security updates in a timely manner. You are encouraged to switch your sources.list entries from testing to buster for the time being if you need security support. See also the entry in the Security Team’s FAQ for the “testing” distribution.


#11

Note that this is for Byzantium we’re talking about which is still unofficial.

Here’s more complete information on Debian Testing;

Q: How is security handled for testing?

A: Security for testing benefits from the security efforts of the entire project for unstable. However, there is a minimum two-day migration delay, and sometimes security fixes can be held up by transitions. The Security Team helps to move along those transitions holding back important security uploads, but this is not always possible and delays may occur. Especially in the months after a new stable release, when many new versions are uploaded to unstable, security fixes for testing may lag behind. If you want to have a secure (and stable) server you are strongly encouraged to stay with stable.

To make it clear, Byzantium gets the same security support as testing which receives support for Debian unstable. When Debian releases, testing gets less support because there is so much new work with the new packages. But there is a time delay on unstable packages and we add an additional delay and additional testing.


#12

I guess I should rephrase my original question, although I think I can infer the answer from the discussion so far.

There are several distros that claim to have a rolling release model. My understanding of this model is that packages are updated as they are released by upstream with very little testing. In the case of system packages, they are released as needed to maintain a working system. The maintainers just keep it rolling along ;-).

So, I’m wondering if purism is using debian testing, once it’s become usable, as a rolling release. That’s not a bad thing, but it would necessitate waiting while the debian devs get testing back on track. After all, the task of packaging a new stable release (around a two year cycle) will continue as the dust settles and they prepare for the .1 update. Wikipedia lists 79 distros that depend on debian including pureos, all with good reason. I’ve used debian testing before as a daily driver and it can be a wild ride. I think it would take substantial effort to mold debian testing into a dependable desktop and maintain it day after day.

If the above is correct then I should wait until pureos officially ‘releases’ a rolling release before I make it my everyday os (even if it takes 6-12 months).


#13

from what i understand debian testing (Bullseye) is the middle ground between stable 10 (Buster) and unstable (Sid - likes to cause damage). gotta love the naming convention :wink:


#14

In debian real rolling is SID because sid is always sid. Testing is a ‘pre-prod stable’ and is just a staging ground before it’s getting frozen. Rolling release is a mentality, you usually don’t have version-locked dependencies unless you deliver/maintain several versions of the same software (eg python2/3, perl5/6, gtk2/3, etc). So you never have dependency nightmare in the package manager but you may hit some instability during run time instead.


#15

I used debian unstable with siduction and testing for years. A i cannot remember, when I had problems with testing. I updated on a nearly daily manner but always look, if there are conflicts.


#16

with debian testing the most painful are the first couple months after a stable has been released in the wild. after that i think it’s pretty ok for people that want the almost bleeding edge to hop in. the recommended way is to upgrade from stable to testing … i haven’t been able to do a clean install of testing so far …


#17

I haven’t tested them, but install ISOs are available for download.

There are also weekly builds and daily builds image available that allow you to install Debian Testing directly. Some of these are netinstall iso images that require internet connection during installation.

Daily looks as though it’s updated throughout the day and they provide a current directory for your convenience. The current current is missing some architectures, like amd64, so I guess that hasn’t been updated yet today.


#18

There are currently problems with their cdbuilder. The first problem is a kernel mismatch issue thats been ongoing for 2-3 weeks that prevents a clean install and the second is a problem in that it hasn’t been installing cryptsetup-initramfs by default for luks-encrypted systems, but this could be worked around.

I believe that they have a new point release for debian stable in the next week or so and thse problems should be sorted out by then.