Debian 13 Released!

An admin rule that's at least 40 years old states: Never update to even version numbers.

sandworm and bookworm are (old)stable candidates for the next years.

If you want, you can use new kernels with the kernel plugin and backports. It will take at least until version 13.2 for the Debian software ecosystem to catch up. And the benefit is likely to be minimal compared to the effort.

omv is more dependent on other packages than on Debian. Salt, for example. One of the things I'd prefer to see more horizontal expansion of omv, for example, toward cloud and cluster administration. That's 1,000 times more useful than Trixie will ever offer, compared to Bookworm.

Another old admin rule says that a system must be at least 50% faster than before you, as a user, even notice it in everyday use. I don't think Trixie has achieved that yet. so no rush!

oh
AIX 7 is on odd release states... not even 7.0.
https://www.ibm.com/docs/de/ai…0?topic=aix-release-notes

Software as a Service (SaaS) like Mail/Office/Diskspace and much other Services are growing Markets/Interest. Or you can rent dozens of servers for a few minutes and cancel them when the job is done. Ok this is not a typical omv-user Job... i agree.

Cloud and clusters are in my personal (professional) interest, but they are certainly not the goal of a system like omv. There are already options for extending omv with Docker and K3S.

Maybe someone could build an omv plugin with Ansible... but I know how it is with ideas like that... nothing happens if you don't push it yourself.
I know i know...

Quote from Rd65

Maybe someone could build an omv plugin with Ansible...

What do you want it to do?

Something like Semaphore UI?
Better integrated into OMV rather than as a standalone solution?
And maybe in Salt instead of Ansible?
But what ryecoaaron says is true. Salt and Ansible configs don't play well on the same host, and there's a significant risk of configs colliding. But even with Salt, OMV doesn't support cluster management because that's explicitly not OMV's goal. Otherwise, one could consider cluster management in Salt instead of Ansible. I only mentioned Ansible as an example because I can achieve things with it that I can't in Salt. But that's where I'm mentioned twice in the sentence, not ryecoaaron or anyone else! So, it's pointless to discuss it. I have nothing against Salt, nor anything against the decision to design OMV as a single-host application. To run Ansible via shell as a host controller for a cluster, you don't even need a VM, and for the UI, Docker with Semaphore UI is probably the better choice.

Quote from ryecoaaron

But it is irrelevant what the state of Debian 13 is since OMV 8 is not even close to being ready (barely started).

(emphasis mine) Understood, even if it's unfortunate. So for anyone that was holding out for OMV8 now that Debian 13.1 is out, sounds like it'll still be a while.

Quote from votdev

The Debian 13 based openmediavault will be released when it is done. This mostly happened with the first dot release, in this case 13.1.

Possible new features can be found in the GitHub issues.

(emphasis mine)

I guess I misunderstood. I read this as this time (unlike OMV7 you pointed out), it will be sooner and timed closer to the first point release. Seems it meant that work on OMV8 would simply start at Debian 13.1 release.

my expectation is, that OMV8 will be out shortly before the support for Debian 12 expires, which will be in June 2026. I would not expect a release before april. also it seems that since OMV 6 it moved to a kind of a "rolling release" model with new features delivered in minor versions, the major ones essentially "just" bumping the Debian release. given that no significant features seem to be around the corner i'd expect the same with OMV8

Quote from votdev

Is that bad? In my opinion, it makes no sense to hold back features for 1-2 years ONLY to then make them available as new features in a release. In addition, this model is more compatible with how I can balance my work at OMV with the rest of my life.

I agree. I think thats the way to go, I've liked the new features and plugins that have arrived since OMV7.

I'm all for developers and documentation maintainers having a private life that works for them. I've been impressed with the development since the release of OMV7. I like Sparkling new things as much as the next person, but not sure NAS software that does what it says on the tin, needs a new version just because the base OS has been updated, look at TrueNas, they seem to be making major changes every new release and some of them breaking changes at that.

Quote from votdev

Is that bad? In my opinion, it makes no sense to hold back features for 1-2 years ONLY to then make them available as new features in a release. In addition, this model is more compatible with how I can balance my work at OMV with the rest of my life.

No, this definitely preferred (in my opinion)! Otherwise you are right, a 1-2 year gap is much worse for artificially holding back features. Adoption would tank as well.

openmediavault 8 / Debian 13 by votdev · Pull Request #2019 · openmediavault/openmediavault

Do the basic migration to get OMV running. Signed-off-by: Volker Theile votdev@gmx.de

github.com

What’s this?! I haven’t seen anyone talking about it. Is this just the very beginning of OMV8 or it’s ready to try?

some progress to follow here https://github.com/openmediava…diavault/debian/changelog

Hey folks, my OMV box seems to have installed Debian 13 (I'm not sure how as I only use updates from the portal on the webGUI). But now I have issues that I cannot access the webgui anymore and copilot suggested I reinstalled OMV using

wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash

But got the error highlighting I was on Debian 13 (that's how I found out!)

Can anyone help me with what I need to do to get back to a working OMV Webgui? omv-firstaid isn't working for me either.

Happy to move to OMV 8 if I need to.