How works OMV Upgrades ?

Sorry for this stupid question, but I don't understand how OMV updates are handled.

For example, my main NAS is currently running version 7.0.5-1 (Sandworm).

I perform all updates every week.

Yet I installed a new OMV alongside it, and I noticed that this OMV fresh install is running version 7.7.17-1 (Sandworm)!!

Why didn't my first OMV NAS, running 7.0.5, follow this update thread until it reached 7.7.17?

Quote from macom

Post the output of sudo omv-update from the one running 7.0.5

root@nas:~# omv-update

-bash: omv-update : commande introuvable

root@nas:~# omv-upgrade

Hit:14 http://security.debian.org/debian-security bookworm-security InRelease

Hit:15 https://download.docker.com/linux/debian bookworm InRelease

Hit:16 http://ftp.debian.org/debian bookworm-updates InRelease

Get:17 https://openmediavault.github.io/packages shaitan-proposed InRelease [5448 B]

Fetched 18.2 kB in 1s (26.3 kB/s)

Reading package lists... Done

W: http://packages.azlux.fr/debian/dists/bullseye/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

Calculating upgrade... Done

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

i understood

i had "Shaitan" repository in my openmediavault.list !!!

i have change source.list to Sandworm.

After an omv-upgrade

I passed to sandworm but always old version4

Version
7.0.5-1 (Sandworm)

The following packages have been kept back:
  openmediavault openmediavault-clamav openmediavault-diskstats openmediavault-lvm2 openmediavault-nut openmediavault-shairport openmediavault-snmp
  openmediavault-tftp openmediavault-usbbackup
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.

root@nas:/etc/apt/sources.list.d# apt list openmediavault -a

En train de lister... Fait

openmediavault/sandworm,sandworm 7.7.17-1 all [pouvant être mis à jour depuis : 7.0.5-1]

openmediavault/now 7.0.5-1 all [installé, pouvant être mis à jour vers : 7.7.17-1]

root@nas:/etc/apt/sources.list.d# apt-get install openmediavault

Lecture des listes de paquets... Fait

Construction de l'arbre des dépendances... Fait

Lecture des informations d'état... Fait

Certains paquets ne peuvent être installés. Ceci peut signifier

que vous avez demandé l'impossible, ou bien, si vous utilisez

la distribution unstable, que certains paquets n'ont pas encore

été créés ou ne sont pas sortis d'Incoming.

L'information suivante devrait vous aider à résoudre la situation :

Les paquets suivants contiennent des dépendances non satisfaites :

wsdd-server : Dépend: wsdd (= 2:0.8-5) mais 2:0.7.0-2.1 devra être installé

E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ».

unfortunatly same problem after apt-get update

root@nas:/BACKUP/DUPLICATI# LANG=C; apt-get install openmediavault
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 wsdd-server : Depends: wsdd (= 2:0.8-5) but 2:0.7.0-2.1 is to be installed
E: Unable to correct problems, you have held broken packages.

root@nas:/BACKUP/DUPLICATI# cat /etc/issue.net
Debian GNU/Linux 12