[SLE-21167] Upgrade key packages in SLE-15 #586

New Issue

mcepl · 2025-12-29T01:24:56+01:00

mcepl commented

2025-12-29 01:24:56 +01:00

The theme of SP4 would be diminishing the discrepancy between SLE-15 and Tumbleweed. Which packages you think are too old in SLE-15?

Checklist: Packages to be rebased

python-rpm-macros I would like whole multiple version build system be present (even though not perhaps used), so that we can use the same macros without fear in SLE-15 and TW.
python-setuptools This one is probably the most questionable, but the idea is to avoid patching recent packages to use ancient setuptools we have there, and when a large update is allowed, this is the one I guess. Probably stop at <= 51.3.3 (see zc.buildout), or if Python 2 support is still required, 44.0.0 // When you look at https://is.gd/LiPJ9s we have either 44.1.0 (r215) or 57.0.0 (r217). Stick with 44.1.0? https://build.suse.de/request/show/256043
python-Sphinx it seems to me that being two major versions behind is too much. However, I am willing to be persuaded otherwise. I am also afraid of the situation when we will have to patch other packages to work with that archeological excavation of Sphinx. Sphinx should go to 2.3.1 (NOT 2.4.*, because of memory leaks). r61 of openSUSE:Factory/python-Sphinx https://build.suse.de/request/show/256084
python-pytest 6.x is probably too new, and the whole API/ABI break thing means we may be stuck with 4.x for yield tests; we can upgrade from package python-pytest5; we cannot, because it has changed names of files / generated RPMs. https://build.suse.de/request/show/256083
python-Twisted, we need to upgrade python-Autobahn (and python-cbor2, python-hyperlink) otherwise we break Django. https://build.suse.de/request/show/256627
python-pexpect, we need a patch from Factory. ssr#255875
python-urlgrabber ssr#255833

The theme of SP4 would be diminishing the discrepancy between SLE-15 and Tumbleweed. Which packages you think are too old in SLE-15? --- ### Checklist: Packages to be rebased - [x] python-rpm-macros I would like whole multiple version build system be present (even though not perhaps used), so that we can use the same macros without fear in SLE-15 and TW. - [x] python-setuptools This one is probably the most questionable, but the idea is to avoid patching recent packages to use ancient setuptools we have there, and when a large update is allowed, this is the one I guess. Probably stop at <= 51.3.3 (see zc.buildout), or if Python 2 support is still required, 44.0.0 // When you look at https://is.gd/LiPJ9s we have either 44.1.0 (r215) or 57.0.0 (r217). Stick with 44.1.0? https://build.suse.de/request/show/256043 - [x] python-Sphinx it seems to me that being two major versions behind is too much. However, I am willing to be persuaded otherwise. I am also afraid of the situation when we will have to patch other packages to work with that archeological excavation of Sphinx. Sphinx should go to 2.3.1 (NOT 2.4.\*, because of memory leaks). r61 of openSUSE:Factory/python-Sphinx https://build.suse.de/request/show/256084 - [x] python-pytest 6.x is probably too new, and the whole API/ABI break thing means we may be stuck with 4.x for yield tests; we can upgrade from package python-pytest5; we cannot, because it has changed names of files / generated RPMs. https://build.suse.de/request/show/256083 - [x] python-Twisted, we need to upgrade python-Autobahn (and python-cbor2, python-hyperlink) otherwise we break Django. https://build.suse.de/request/show/256627 - [x] python-pexpect, we need a patch from Factory. ssr#255875 - [x] python-urlgrabber ssr#255833

mcepl added the SLE label 2025-12-29 01:24:56 +01:00

mcepl closed this issue

2025-12-29 01:24:56 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: python/_ObsPrj#586