On 11/1/25 5:35 PM, Adam D. Barratt wrote:
Control: tags -1 + moreinfo
On Fri, 2025-08-15 at 21:29 +0200, Thomas Goirand wrote:
[ Reason ]
I'd like to upload version 6.4.0-1 of puppet-module-rally which is
currently in Sid/Forky. I am aware that we shouldn't upload new
version in Stable,
however:
- I know that 5.4.0-2 doesn't work with the version of puppetserver
in Trixie, I simply forgot to upload 6.4.0-1.
I must admit that "I forgot to do
this upload" is not a great start for requesting an exception to the
norms for updates in stable.
Indeed ... :/
I have no excuse, and I'm not sure how to convince you it's still the
right thing to do, as the older version is kind of broken.
[...]
[ ] attach debdiff against the package in (old)stable
We can't approve anything without seeing what we're being asked to
approve.
[x] the issue is verified as fixed in unstable
Let me know if I should name the package version differently, for
example 6.4.0-1~deb13u1, to make it a different version than in
Forky, or if we don't care (IMO, we should not, it's going to be the
same binary anyways, but you know better...).
You've been a DD for more than long enough to know that version numbers
can't be reused. 6.4.0-1 already exists in the archive, there's no way
you can upload a different package with that version number.
Right. I'll come back (this week, hopefully) with a better versioning
scheme.
I am slightly confused as to whether the package is actually useful in
Debian or simply part of your own CI setup.
Well, my CI is ... part of Debian. If you install ikvswitch and
openstack-cluster-installer-poc in a server with enough RAM, and run
"oci-poc-ci", you end up with a fully virtuallized OpenStack. This is
how I make sure there's no regressions in the packaging I provide to Debian.
Also, rally is being setup in one of the nodes (ie: tempest node) of
openstack-cluster-installer, so users of that tool can also use Rally.
So here, I'm also trying to fix this setup.
Its highest popcon count
appears to have been 3, with frequent drops to 0.
The important point of all I'm doing with OpenStack in Debian, is so one
can setup OpenStack without internet access in one direction or another,
for security reasons. The only thing one needs is a Debian repository
that contains all the artifacts (including these puppet modules, and
which is why I package them in Debian). Only VMs running on the
deployment have internet access. So it is very much expected that popcon
is near zero under these conditions.
Anyways, thanks for your answer, and please give me a few days
(hopefully) to come back to this bug.
Cheers,
Thomas Goirand (zigo)
