It used to show on my workstation:

Devuan GNU/Linux 4 (daedalus/ceres) x86_64
Instead of
Devuan GNU/Linux 5 (daedalus/ceres) x86_64

After the last change it appears properly version 5 for testing.
I had made changes myself aswell early, but i am happy that it took official form properly.

Thank you!

"Daedalus it is one version advance than Chimaera/Ceres."

There is no Chimaera/Ceres. Ceres is always unstable. Packages go from Ceres to testing. Although Chimaera has not been officially released as 'stable' yet, Daedalus appears to be the new testing. But it is not one version more advance[d] than Ceres.

My mistake in mentioning "Ceres" above, I have correct it. Thank you for point out sgage.

That's true, i mean Daedalus it's one advance over Chimaera, but not ceres aka sid.

Although this topic was used for SID packages too, let it remain so as we're on OFFtopic, or move to a more favorable thread if you find it right.

Thanks!

So far, from Daedalus-testing (Devuan 5) aka Bookworm-testing (Debian 12) got updates for apps that i daily use.

Nautilus 40.2
Geany 1.37.1 
Disks 40.2
ntfs-3g 1:2021.8.22-2
gtk+3.0 3.24.30-3
mediainfo 21.03-1

Awaiting to upgraded very soon 2/5 days.

mpv to 0.33.1-1
alsa-mixer 1.2.5.1-1

Also i hope Debian maintainer pass to sid soon those two-below packages, i had a few concern with them so i can't wait to check it if they've been fixed.

feh 3.7.1
conky 1.12.2

Many other packages have been updated since this topic was opened. That's why i like testing or better sid, but i'll stick on testing for some reasons that requires less attention than sid.

Guys, Do not be confused, this topic is Devuan 5 (testing/sid) aka Daedalus.
See the thread name.
Leave alone Chimaera here.
Daedalus it is one version advance than Chimaera/Ceres.
This thread serve to test (next testing/after chimaera releases).
For people who like to play in advance with testing/sid packages

I open this topic asking about next-testing as there was no repo for Daedalus, and edited it as soon as it was set. Personally, I have taken all the risks and responsibility on my testing jurney.

More here about releases names.
https://www.devuan.org/os/releases

We know versions and names are a bit confusing at first on the early releases, as some walk faster with repos than with official releases names.

I hope i have somewhat clarified my position and forgive me if i have created a bit confusion if i did.

BR!

"Daedalus it is one version advance than Chimaera/Ceres."

There is no Chimaera/Ceres. Ceres is always unstable. Packages go from Ceres to testing. Although Chimaera has not been officially released as 'stable' yet, Daedalus appears to be the new testing. But it is not one version more advance[d] than Ceres.

@zapper . . . we are in the home stretch . . .

Wait I thought, Devuan Ascii was based on that...

Okay but seriously, its coming sooner than that?

Also, I have wanted to make a joke like that for a long time...

zapper wrote:

Wow, you guys were mega fast in getting Devuan chimaera out...

The subject of this thread is misleading.  Chimaera has not been "officially" released yet.  Will be soon though . . .

Still would be surprising considering when debian 11 was released...

August 14th 2021 was when it was released... so there's that.

Even if it came out in september, or early october.

Best wishes though on such a goal though if that's what you intend!

I don't think you need to use negative numbers. I generally use a priority of 10 or 50 or sometimes 1 for things I want to use selectively.

You can use codenames with 'n=<codename>' as in my example. This is from my beowulf (my main computer.)

Package: *
Pin: release n=chimaera
Pin-Priority: 50

Package: *
Pin: release n=ceres
Pin-Priority: 50

If you have nothing pinned, running apt-policy will show you the default priorities of all the repos you have enabled. I think backports is 100 by default and experimental is 1.

See man apt_preferences for all the details.

A good compromise between testing and unstable is to have both in your sources and pin ceres to a lower priority. Then you will just get packages from the testing suite unless you specify that you want something from ceres.

@FSR, Well since you mentioned it, here is a good example.  Virtualbox was removed from the debian?/chimaera release, I think it was.  If using only that release name in sources.list, then virtualbox would not be found.  Virtualbox was put back in the unstable/sid/ceres repository so I installed with "apt -t ceres install virtualbox".  I wanted to have virtualbox updated automatically from the ceres repo so I left the ceres line present in sources.list. 

This apt pinning seems to work okay.  At least it correctly updated virtualbox recently.  This is a working example that I use to make sure that other packages do not get updated with a dist-upgrade from either chimaera or daedalus.  I found this example on the www, and since it has not broken anything, I continue to use it.

This is what I have in /etc/preferences.d/40sid-virtualbox

I ask this to verify that it is safe for future use.  Do you or anyone else see anything wrong that would cause a problem in the future?  I hope I have not strayed too far from the forum topic, but if running a testing release, this example may come in handy.  I do understand that chimaera/testing, daedalus/(future) testing, and ceres/unstable are very prone to break and are not for production work.  But, when they do break, one can learn quite a bit in order to fix them.

A good compromise between testing and unstable is to have both in your sources and pin ceres to a lower priority. Then you will just get packages from the testing suite unless you specify that you want something from ceres. This can be helpful when something breaks and the fix gets put into ceres. You don't have to wait for it to move to the testing suite.

Beowulf to Chimara: yes, change sources, update, upgrade/dist-upgrade. There has been some problem with upgrading eudev in some cases. I'm not sure what the exact circumstances are to create that problem, but there's a fix coming to chimaera very soon.

Nautilus 40.2
Geany 1.37.1 
Disks 40.2
ntfs-3g 1:2021.8.22-2
gtk+3.0 3.24.30-3
mediainfo 21.03-1

Awaiting to upgraded very soon 2/5 days.

mpv to 0.33.1-1
alsa-mixer 1.2.5.1-1

Also i hope Debian maintainer pass to sid soon those two-below packages, i had a few concern with them so i can't wait to check it if they've been fixed.

feh 3.7.1
conky 1.12.2

Many other packages have been updated since this topic was opened. That's why i like testing or better sid, but i'll stick on testing for some reasons that requires less attention than sid.

Guys, Do not be confused, this topic is Devuan 5 (testing) aka Daedalus.
See the thread name.
Leave alone Chimaera here.
Daedalus it is one version advance than Chimaera (not released yet).
This thread serve to test (next testing/after chimaera releases).
For people who like to play in advance with next testing

I open this topic asking about Daedalus, and edited it as soon as it was set.
Personally, I have taken all the risks and responsibility on my testing jurney.

More here about releases names.
https://www.devuan.org/os/releases

We know versions and names are a bit confusing at first (even to me) on the early releases, as some walk faster with repos than with official releases names.

I hope i have somewhat clarified my position and forgive me if i have created a bit confusion if i did.

BR!

Wow, you guys were mega fast in getting Devuan chimaera out...

The subject of this thread is misleading.  Chimaera has not been "officially" released yet.  Will be soon though . . .

nixer wrote:

If my ceres install was not working so well, I would be in daedalus right now, (-;

Ceres and daedelus should be almost identical right now. I don't think we have added any packages to daedelus, and debian has probably only added a few to whatever B is after bullseye. (Buckthorn? Bumble? Busted? I can't keep them straight anymore.)

It's "bookworm".

So what's the current procedure for upgrading Beowulf to Chimaera? Can we just change repo names, or are we looking at breakage if we go that route?

If my ceres install was not working so well, I would be in daedalus right now, (-;

Ceres and daedelus should be almost identical right now. I don't think we have added any packages to daedelus, and debian has probably only added a few to whatever B is after bullseye. (Buckthorn? Bumble? Busted? I can't keep them straight anymore.)