Tough luck: It has already been declined two months ago without meaningful comment. https://build.opensuse.org/request/show/1130702 https://build.opensuse.org/request/show/1130712 https://build.opensuse.org/request/show/1130713 Am 29.01.24 um 18:58 schrieb Ben Greiner:

Hi Christian,

Am 29.01.24 um 18:27 schrieb Keil:

...

Hi,

currently python311-kombu does not build in the devel project because it misses python311-boto3, which is only built for plain python3. This makes python311-celery in turn uninstallable in 15.5 or 15.6 as this directly translates to devel:languages:python or :backports respectively. All build fine in Factory.

I'm happy to raise this anywhere else, it just wasn't obvious to me where this fits best.

Boto3 and all of its dependencies need %{?sle15_python_module_pythons} added like this: https://build.opensuse.org/request/show/1142617 When you have completed the full dependency chain, try to get the attention of the package or project maintainer (Adrian in CC).

...

Best regards,

Christian

- Ben

Hi all, since all of the missing dependencies (botocore, s3transfer) build for 311 in Factory, I was hoping for this to be rather simple ,o). Thanks for the heads up Robert, I'll keep my fingers crossed. Cheers, Christian

Hi Robert, On Fri, 2 Feb 2024 15:17:18 -0500 Robert Schweikert wrote:

Finally got around to work on this. Packages are up as SRs and I have asked a couple of people to take a look since reviewing my own work is somewhat pointless.

I expect some movement next week on this and everything to land in Factory soonish and then in SLE/Leap in 4-6 weeks.

can you share a status on this? I just checked and python-azure-identity is not yet building for Python 3.11 in turn blocking python311-kombu. Best regards, Christian -- Dr.-Ing. Christian Keil (Principal Researcher) Phone:+49 40 808077-648 Fax:+49 40 808077-556 Mail: keil@dfn-cert.de DFN-CERT Services GmbH, https://www.dfn-cert.de/, Fax: +49 40 808077-556 Sitz / Register: Hamburg, AG Hamburg, HRB 88805, Ust-IdNr.: DE 232129737 Nagelsweg 41, 20097 Hamburg, Germany. CEO: Dr. Klaus-Peter Kossakowski

Hi, On 4/3/24 05:58, Ben Greiner wrote:

Am 03.04.24 um 11:27 schrieb Christian Keil:

...

Hi Robert,

On Fri, 2 Feb 2024 15:17:18 -0500 Robert Schweikert wrote:

...

Finally got around to work on this. Packages are up as SRs and I have asked a couple of people to take a look since reviewing my own work is somewhat pointless.

I expect some movement next week on this and everything to land in Factory soonish and then in SLE/Leap in 4-6 weeks. can you share a status on this? I just checked and python-azure-identity is not yet building for Python 3.11 in turn blocking python311-kombu.

Expected this week. We have one more thing to iron out w.r.t. the few packages that have the older versioning for bets packages, i.e. using 'b' instead of '~b'. Once that is sorted out the packages will all be sent to the 15 SP4 stream. Also see [1] as reference.

You will have to ask @glaubitz directly. He's the maintainer of devel:languages:python:azure, doesn't like outside contributions

Comments like this are not really helpful. Later, Robert

and doesn't always read the mailing lists.

Note that the checkin deadline for SLE15SP6 Beta already has expired.

...

[1] https://www.suse.com/c/incompatible-changes-ahead-for-public-cloud-sdks/ -- Robert Schweikert MAY THE SOURCE BE WITH YOU Distinguished Engineer LINUX rjschwei@suse.com IRC: robjo

Am 03.04.24 um 13:15 schrieb Robert Schweikert:

Hi,

...

You will have to ask @glaubitz directly. He's the maintainer of devel:languages:python:azure, doesn't like outside contributions

Comments like this are not really helpful.

But they are true. Quote from https://build.opensuse.org/project/show/devel:languages:python:azure :

Please don't make any submit requests before talking to @glaubitz. Please avoid updating individual packages only as this can break the Azure SDK which needs the package versions to be in sync.

* // I vividly remember the last time I tried to submit a fix and was shot down by you and glaubitz despite doing exactly as requested above. Plus the frequent non-exuse "too many e-mails on the list, I didn't see them" . If you and him would be more cooperating with submissions to the development projects, this would have been resolved months ago. Instead you chose to be clandestine, rejected submissions out of the blue if not ignoring them for months, and did not provide any meaningful explanation until very recently. In addition, I despise your focus on commercial SLE15 and disregard of openSUSE Tumbleweed in your devel projects. Every time you update boto3 and botocore, it breaks moto because you "forget". For several updates I submitted fixes, but it always took weeks or months to react. Hence, and because of your reactions documented in this thread, I have decided to stop contributing in that area despite seeing it in the failing packages for openSUSE:Factory all the time and some of my own packages depending on it.

[1] https://www.suse.com/c/incompatible-changes-ahead-for-public-cloud-sdks/

On Wed, 2024-04-03 at 11:58 +0200, Ben Greiner wrote:

You will have to ask @glaubitz directly. He's the maintainer of devel:languages:python:azure, doesn't like outside contributions and doesn't always read the mailing lists.

I do read mailing lists, but I am subscribed to a large number of lists, so I naturally cannot read every message posted here, especially when the topic is not obviously relevant to me. As for the submissions: The reason why I don't prefer outside submissions to the Azure SDK is because that has caused trouble in the past and makes scripted changes to the packages more difficult. I had to revert some changes in the past in order to get my scripts for the current conversion to Python 3.11 working. It's also important to note that you cannot just pick single packages from the SDK and switch them to Python 3.11, it has to be done for all packages. And if that happens, the CLI has to be switched as well. So, while I can understand that someone might be waiting for some dependencies to become available as a Python 3.11 version, it's important to make these changes in an orchestrated manner to make sure the SDK and CLI still works afterwards. I have already successfully converted the SDK to 3.11 and while at it, I also cleaned up all packages and removed some cruft and also fixed some mistakes. I have asked the maintenance team for a pre-submission review now and if they're fine with the changes, I'm going to submit everything to Factory and SLE-15-SP4. Adrian