Roadmap for the update to last stable Debian 13 "trixie"

Feature Requests
,
1

Based on the Torizon OS naming convention, I know that Torizon OS 7 is (and it will be) a Yocto LTS 5.0 “scarthgap” build.

At the moment this Yocto build uses Debian 12 “bookworm”.

But on last August, the new Debian stable 13 “trixie” has been released.

Is there any roadmap to use Debian “trixie” in Torizon OS 7?

Or is this an upgrade planned for Torizon OS 8?

2

Greetings @vix,

Just to clarify, are you specifically asking about Debian Trixe based containers for Torizon OS 7? Or are you referring to something else?

If you are talking about the containers, then our current stance is that we have no plans to provide Debian Trixie based containers for Torizon OS 7. This is not a final decision, and we may adjust this based on new information, or customer input.

That said, is there a specific reason you are inquiring about Debian Trixie? Or do you just want to generally be on the latest version of things?

Best Regards,
Jeremias

3

As far as I understand (but I can be wrong), the containers for Torizon OS 7 are “bookworm based” because Torizon OS 7 itself it’s a kind of Debian Bookworm Yocto recipe. And the containers match the “base OS”.

So I’m asking about a “Trixie” base OS + “Trixie” containers.

No particular need at the moment.

It’s only curiosity. In the past I’ve already asked about this, but I’ve never understood the answer:

  • the number of Torizon OS increases with Yocto LTS release (7=kirkstone; 7=scarthgap; 8=wrynose?) - That’s fine. Yocto is the way I write the recipe
  • but there is also what I put inside the recipe. And here comes Debian (if I’m right)

How Torizon OS numbering takes into account Debian major releases?

We can’t be sure they’re aligned with Yocto LTS.

Correct me if I’m wrong.

4

because Torizon OS 7 itself it’s a kind of Debian Bookworm Yocto recipe.

No that’s not really the case. There’s nothing in Yocto that ties the OS that is built to a specific version of Debian. It’s simply the case that when we first released Torizon OS 7, the latest LTS version of Debian at the time was Bookworm.

How Torizon OS numbering takes into account Debian major releases?

The only correlation is that so far for every major version release of Torizon OS, we tend to stick with whatever the current LTS version of Debian is at the time the major was first released. Of course this is not a hard rule. But, unless we are given good reason to switch to another version of Debian in our containers, we want to avoid such a drastic change.

Best Regards,
Jeremias

5

Hi,

One good reason to move to trixie is that it has PySide6 packages so that Torizon could move from old/unsupported PySide2/Qt5 to the current PySide6/Qt6.

BR.

6

This has been discussed on github Bump PySide2 to PySide6 · Issue #60 · torizon/vscode-torizon-templates · GitHub

It was in Debian sid, but now it’s in Trixie.

7

Pyside as a topic is already in discussion internally. Our product team still needs to weigh the pros and cons of moving to Trixie and this isn’t the only consideration for us. That said our resources are fairly heavily tied up in other priorities at the moment so it’s not likely this topic is handled any time soon.

Best Regards,
Jeremias