vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 323cbacdc0841fed0ac871a6fb881613e237da57
Author: Thomas Goirand <zigo@debian.org>
Date: Thu Jul 2 14:03:05 2026 +0200
Also install manila and magnum db on messaging nodes if installing the service.
commit 72952f232e1512144af615875671f24d2a6caca3
Author: Thomas Goirand <zigo@debian.org>
Date: Thu Jul 2 13:33:21 2026 +0200
Fix cloudkitty scheduler hint, if cloudkitty is on messaging nodes.
commit 1cf8a1fbf4062dcfa4853dc445e77dc0d05749ae
Author: Theo Gindre <theo.gindre@infomaniak.com>
Date: Thu Jul 2 10:15:45 2026 +0200
feat(ceilometer): Ignore disabled projects
commit 90702aad8f8fbad7006c93e30d550657c86b8134
Author: Thomas Goirand <zigo@debian.org>
Date: Thu Jul 2 11:57:55 2026 +0200
Manila: - With >= epoxy, remove email_v2, auth_name_v2, password_v2 when setting-up Manila.
- not setting-up v1 endpoints starting with >= Gazpacho.
- starting with zed, service_instance has changed path.
commit cf94c657c91172d476e3ae13fa80db14608ece46
Author: Evan Bebi <evan.bebi@infomaniak.com>
Date: Mon Jun 22 14:33:01 2026 +0200
feat: add default backup
feat: add default
feat: default
commit 9e3c62e7a10e065619d00dcc594fb7e3b58330db
Author: Thomas Goirand <zigo@debian.org>
Date: Thu Jun 25 10:53:40 2026 +0200
Do not install cloudkitty on controllers if there's messaging nodes.