Bug 1212618 - Packaging of SELinux toolchain for additional python versions
Summary: Packaging of SELinux toolchain for additional python versions
Status: RESOLVED FIXED
: 1209654 (view as bug list)
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Python (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Johannes Segitz
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-22 09:51 UTC by Johannes Segitz
Modified: 2023-12-01 00:40 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Segitz 2023-06-22 09:51:18 UTC
I accepted https://build.opensuse.org/package/rdiff/security:SELinux/libselinux?linkrev=base&rev=154
to build the python subpackage, which was probably an error.

Previsusly the package was named python3-libselinux. No I get on e.g. SLE 15.5 a package called python311-libselinux.

My understanding is that I should build python3-libselinux and python311-libselinux to satisfy the old dependencies and still allow users to install python311 and work with this.
Comment 1 Matej Cepl 2023-06-23 17:07:07 UTC
*** Bug 1209654 has been marked as a duplicate of this bug. ***
Comment 2 Johannes Segitz 2023-07-04 14:28:58 UTC
I think the current state in security:SELinux is good now. Thanks for the help Matej!
Comment 3 Johannes Segitz 2023-07-12 06:32:43 UTC
we need to go back to the old split spec file since this in ring0 and otherwise causes issues for the staging of the initial build system
Comment 4 Matej Cepl 2023-07-19 11:47:15 UTC
??? What doesn’t work in ring0? To the best of my knowledge we have all python-rpm-macros present?
Comment 5 Johannes Segitz 2023-07-19 13:58:36 UTC
See the slack thread, adding here for archival:
https://build.opensuse.org/request/show/1096710
It's not about the macros, it's about keeping the build strapping system as small as possible. I'm not involved in that, Ana can probably explain in more detail
Comment 6 Johannes Segitz 2023-08-14 07:24:51 UTC
should be solved now, thanks Matej