hey there! I was wondering if there was a technical issue preventing github.com/omniosorg/lx-images from releasing a Debian 13 image for LX branded zones?

I think it's a resource availability issue. In Edgecast-cloud (home of the Triton, SmartOS, and Manta devs & admins of MNX), we're a combination of coming back from winter break, or deep in some projects that need review & testing.

If the OmniOS folks are building images, maybe they can help. I also ping my peers who may have better insight into the situation.

Sorry I don't have an immediate answer for you from SmartOS-land, but thank you for moving it over here.

veg: I think you can try to build a trixie image yourself using this : github.com/TritonDataCenter/debian-lx-brand-image-builder and upload it to datasets.at

thanks a bunch for the info, danmcd & szilard

I tried upgrading to Debian 13 from within the OmniOS Debian 12 image, but it failed; is this expected behaviour, and should one migrate data to a new image instead of upgrading using native Linux tools, or would this be abnormal behaviour related to some recently introduced systemd witchcraft?

I have no experiences with dist-upgrading debian lx zone from n to n+1, so i dont know what to expect, but upgrading to trixie failed on my side aswell (some important systemd services failed to start properly , afair journaling stuff). Other than that the system used to work.