Bug 1219886 - Adapt package python to build with OpenSSL 3
Summary: Adapt package python to build with OpenSSL 3
Status: RESOLVED DUPLICATE of bug 1219306
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Python maintainers (group account)
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 1219879
  Show dependency tree / graph
 
Reported: 2024-02-13 14:28 UTC by Otto Hollmann
Modified: 2024-02-14 13:45 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Otto Hollmann 2024-02-13 14:28:00 UTC 
Package python requires openssl 1.1.1 that is EOL and we would like to remove it from Factory.
> %if 0%{?suse_version} >= 1500
> BuildRequires:  libopenssl-1_1-devel
> %else
> BuildRequires:  libopenssl-devel
> %endif

> https://build.opensuse.org/package/view_file/openSUSE:Factory/python/python.spec?expand=1


Please check tracker bug 1219879 for more details.
Comment 1 Otto Hollmann 2024-02-13 14:35:32 UTC 
@Matej, this sounds very similar to what you did in bug 1217782.
Is there any chance for such a change or is it impossible?

And if it is impossible, do we have any estimate when we will drop python 2 from Factory?
Comment 2 Matej Cepl 2024-02-14 13:19:35 UTC 
(In reply to Otto Hollmann from comment #1)
> @Matej, this sounds very similar to what you did in bug 1217782.
> Is there any chance for such a change or is it impossible?
> 
> And if it is impossible, do we have any estimate when we will drop python 2
> from Factory?

See bug 1219306, the latest will be probably Gimp (i.e., sometime in May).
Comment 3 Otto Hollmann 2024-02-14 13:45:57 UTC 
Great, thank you
So let's mark this bug as duplicate of bug 1219306

*** This bug has been marked as a duplicate of bug 1219306 ***