#10 F32: The ultimate Python 2 release. Long live Python 3
Merged 4 years ago by churchyard. Opened 4 years ago by churchyard.
rpms/ churchyard/python27 f32-ultimate_release  into  f32

file added
+11542
The added file is too large to be shown here, see it at: pubkeys.txt
file modified
+16 -5
@@ -51,11 +51,13 @@ 

  # ==================

  Summary: Version %{pybasever} of the Python interpreter

  Name: python%{pyshortver}

- %global general_version %{pybasever}.17

+ URL: https://www.python.org/

+ 

+ %global general_version %{pybasever}.18

  #global prerel ...

  %global upstream_version %{general_version}%{?prerel}

  Version: %{general_version}%{?prerel:~%{prerel}}

- Release: 2%{?dist}

+ Release: 1%{?dist}

  License: Python

  

  # Python 2 is deprecated in Fedora 30+, see:
@@ -113,6 +115,7 @@ 

  BuildRequires: tix-devel

  BuildRequires: tk-devel

  BuildRequires: zlib-devel

+ BuildRequires: gnupg2

  

  %if %{with_gdbm}

  # ABI change without soname bump, reverted
@@ -172,7 +175,9 @@ 

  # Source code and patches

  # =======================

  

- Source: https://www.python.org/ftp/python/%{general_version}/Python-%{upstream_version}.tar.xz

+ Source0: %{url}ftp/python/%{general_version}/Python-%{upstream_version}.tar.xz

+ Source1: %{url}ftp/python/%{general_version}/Python-%{upstream_version}.tar.xz.asc

+ Source2: %{url}static/files/pubkeys.txt

  

  # Systemtap tapset to make it easier to use the systemtap static probes

  # (actually a template; LIBRARY_PATH will get fixed up during install)
@@ -681,8 +686,6 @@ 

  # Additional metadata

  # ======================================================

  

- URL: https://www.python.org/

- 

  %description

  Python 2 is an old version of the language that is incompatible with the 3.x

  line of releases. The language is mostly the same, but many details, especially
@@ -700,6 +703,7 @@ 

  # ======================================================

  

  %prep

+ %gpgverify -k2 -s1 -d0

  %setup -q -n Python-%{upstream_version}

  

  %if 0%{?with_systemtap}
@@ -1489,6 +1493,13 @@ 

  # ======================================================

  

  %changelog

+ * Mon Apr 20 2020 Miro Hrončok <mhroncok@redhat.com> - 2.7.18-1

+ - Update to 2.7.18

+ - This is is the last Python 2.7 release and therefore the last Python 2 release

+ 

+ * Thu Apr 09 2020 Marcel Plch <mplch@redhat.com> - 2.7.18~rc1-1

+ - Update to 2.7.18rc1

+ 

  * Thu Jan 30 2020 Fedora Release Engineering <releng@fedoraproject.org> - 2.7.17-2

  - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild

  

file modified
+2 -1
@@ -1,1 +1,2 @@ 

- SHA512 (Python-2.7.17.tar.xz) = 2dc19a0b0d818c71429dae94783e58b2aac0fa31f5faa1e840cac06245a59932ecc4658d913515736601bcf70a78c9ec60367aed75f4567d1e41ff3bb104da9a

+ SHA512 (Python-2.7.18.tar.xz) = a7bb62b51f48ff0b6df0b18f5b0312a523e3110f49c3237936bfe56ed0e26838c0274ff5401bda6fc21bf24337477ccac49e8026c5d651e4b4cafb5eb5086f6c

+ SHA512 (Python-2.7.18.tar.xz.asc) = c2a5f5a52f47dec52460ad3275758d4e5de6e7075c3def4353c988d74d563a39b42cae2d5eb24e2a23a6247cef69100f91620b11a49c2359fbf99b203c9cbda8

no initial comment

Build failed.

and the Fedora CI hasn't even started. [citest]

Build failed.

The diff and the build log look good. RPM is installable and works as usual.

Pull-Request has been merged by churchyard

4 years ago

@fbo the zuul job was run on rawhide, according to https://fedora.softwarefactory-project.io/zuul/build/0073c12a40f4458aaa919f4f286bd118/log/artifacts/installed-packages.list

Yes, we don't have yet the image f32 on softwarefactory-project.io (https://softwarefactory-project.io/zuul/t/local/labels). I'll manage to enable it (we are close to the release, so I guess that's fine). The definition of the job still use rawhide yes: https://pagure.io/fedora-zuul-jobs/blob/master/f/zuul.d/jobs.yaml#_32

Glad to hear it is known.

we are close to the release, so I guess that's fine

That part is what I don't understand. How is this related to the release? The tests being run on f32 is beneficial the very moment rawhide and f32 diverge -- that is almost immediately after branching. See also https://pagure.io/fedora-ci/general/issue/97

Glad to hear it is known.

we are close to the release, so I guess that's fine

That part is what I don't understand. How is this related to the release? The tests being run on f32 is beneficial the very moment rawhide and f32 diverge -- that is almost immediately after branching. See also https://pagure.io/fedora-ci/general/issue/97

Well, you are right. It was a bad statement. So yes as long as we have a working cloud image for the next release stable release we can expose it in Nodepool and make it available for Zuul jobs to run on.

@churchyard : The cloud-fedora-32 image is now ready. I merged that patch 1 to add the new nodeset and set rpm-test job for f32 branch to use that new nodeset. I've validated the change with this PR 2

Let me know if you see any issue.