Hello Thomas,
Am 11.03.25 um 12:08 schrieb Thomas Goirand:
Hi there!
Thanks for maintaining python3-ilorest.
ilorest (the shell command line utility), is using python3-ilorest (the
Python library that you maintain). They go together, and should be
uploaded together with the same version. Upstream releases them
together, at the same time. If we don't do the same, there are
incompatibility risks.
I believe I asked for this multiple times already (at least twice).
I count one time, but this doesn't matter in the end.
Could we *PLEASE* communicate and get to upload both at the same time?
So far, I've been communicating with you about this privately. This
time, I'm adding the release team list as recipient, to get the release
team attention, and to make sure the message is publicly seen and ACK
that I've made such a request. If the bad practice of rogue uploads
continue, I may escalate this further. You've been (politely) warned...
Yes, we've had a conversion in the past about some coordinated uploads
and there was no and never an intention from my side in the past to
block any other packages, why should I've an interest in such doings. If
this was happen I need to apologize about that.
It's more that I've really forgotten about we need to coordinate the work.
Also, would you be ok to move your package to the Python team, so I get
upload rights as well?
I don't mind, I also would not mind if you want to put yourself into the
Uploaders field and remove me there.
In the past I had an interest in the package as I was using this on may
day job, this isn't the case anymore.
I'll move the package to the DPT the next hours.
Version 6.0.0 has been released 6 hours ago, and is available. Should we
package these for Trixie? The library freeze is in 4 days... Once done,
IMO, no further upload should be done before Trixie is out. Your thoughts?
I'm totally fine if the new version 6.x goes into Trixie. If you want to
pick over the package feel free, otherwise I can try to have a look at
the weekend.
There is a ongoing hassle with python-redfish as both packages use the
same module path, it's not resolved yet and would need to get fixed by
HPE I think. But I'm very pessimistic HPE will move ever to get this
solved so bot Python libraries can live together.
--
Regards
Carsten
