| |
@@ -11,7 +11,7 @@
|
| |
|
| |
Name: python-%{srcname}
|
| |
Version: 2.0.2
|
| |
- Release: 1%{?dist}
|
| |
+ Release: 2%{?dist}
|
| |
Summary: %{sum}
|
| |
|
| |
License: BSD
|
| |
@@ -21,13 +21,13 @@
|
| |
BuildArch: noarch
|
| |
BuildRequires: python2-devel
|
| |
BuildRequires: python3-devel
|
| |
- BuildRequires: python-setuptools
|
| |
+ BuildRequires: python2-setuptools
|
| |
BuildRequires: python3-setuptools
|
| |
- BuildRequires: numpy
|
| |
+ BuildRequires: python2-numpy
|
| |
BuildRequires: python3-numpy
|
| |
- BuildRequires: python-sphinx
|
| |
+ BuildRequires: python2-sphinx
|
| |
BuildRequires: python3-sphinx
|
| |
- BuildRequires: pytest
|
| |
+ BuildRequires: python2-pytest
|
| |
BuildRequires: python3-pytest
|
| |
|
| |
%description
|
| |
@@ -36,9 +36,9 @@
|
| |
%package -n python2-%{srcname}
|
| |
Summary: %{sum}
|
| |
%{?python_provide:%python_provide python2-%{srcname}}
|
| |
- Requires: numpy
|
| |
- Requires: python-setuptools
|
| |
- Requires: python-sphinx
|
| |
+ Requires: python2-numpy
|
| |
+ Requires: python2-setuptools
|
| |
+ Requires: python2-sphinx
|
| |
|
| |
%description -n python2-%{srcname}
|
| |
%{common_description}
|
| |
@@ -83,6 +83,10 @@
|
| |
%{python3_sitelib}/*
|
| |
|
| |
%changelog
|
| |
+ * Mon Jan 15 2018 Iryna Shcherbina <ishcherb@redhat.com> - 2.0.2-2
|
| |
+ - Update Python 2 dependency declarations to new packaging standards
|
| |
+ (See https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3)
|
| |
+
|
| |
* Thu Oct 19 2017 Christian Dersch <lupinix@mailbox.org> - 2.0.2-1
|
| |
- new version
|
| |
|
| |
ishcherb
commented 6 years ago
This package uses names with ambiguous
python-prefix in requirements.According to Fedora Packaging guidelines for Python, packages must use names with either
python2-orpython3-prefix in requirements where available.We are aiming to rename
python-*dependencies topython2-*, so we can later switch thepython-*namespace to Python 3.This PR is part of Fedora's Switch to Python 3 effort.
Note that, although this PR was created automatically, we will respond to any comments or issues which you might find with it. We will keep the PR open for review for a week, and if there's no feedback we'll merge it. There is no need to build the package right after merge, this change can wait for the next package rebuild.
The local mock build passed, for Koji scratch build please see simple-koji-ci result.
This PR was opened automatically, for source code see here