On 02.05.23 at 13:11 Daniel Garcia wrote:
On mar, 2023-05-02 at 12:48 +0200, Johannes Kastl wrote:
1. Currently I set those lines in the prjconf in the SLES15+Python3 projects: ``` %define pythons python310 Macros: %pythons python310 :Macros ```
IIUC I can just remove this, once the macro was added to each package?
That's exactly what the macro does (but with python311), so you'll be able to remove it from your prconf and just use the macro when it's available.
Hm, as this is set in the package, it seems it overwrites what I have in the project's prjconf. So my whole build chain using python3.10 is now switched to 3.11... :-( But as I wanted to rebuild this properly in systemsmanagement:ansible:SLE15 anyway, I'll start there using the new 3.11 stack.
This should be adapted, but in this case you'll need to continue modifying the pythons for tumbleweed to build just for the primary python, and setting the corresponding so at the end I don't see any difference if using the new macro or not, because this package doesn't use %python_subpackages
Will the new python3.11 stack for SLE15 stay with 3.11? Or will it switch to something else (perhaps regularly)? Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537