#17 Use PEP 503 names for BuildRequires
Merged 2 years ago by eclipseo. Opened 2 years ago by churchyard.
rpms/ churchyard/python-twisted pep503  into  rawhide

file modified
+1 -1
@@ -53,7 +53,7 @@ 

  BuildRequires:  python3dist(sphinx) >= 1.3.1

  BuildRequires:  python3dist(sphinx-rtd-theme)

  BuildRequires:  python3dist(typing-extensions) >= 3.6.5

- BuildRequires:  python3dist(zope.interface) >= 4.4.2

+ BuildRequires:  python3dist(zope-interface) >= 4.4.2

  

  %{?python_extras_subpkg:Recommends:  python3-%{pypi_name}+tls}

  %{!?python_extras_subpkg:Recommends: python3dist(service-identity) >= 18.1}

Since Fedora 33, we generate both python3dist(foo.bar) and python3dist(foo-bar)
provides, but we'd like to follow PEP 503 and use only the names with dash.

By using the dashes, this is not compatible with the provides generated in EPEL 8,
compatibility can be achieved with the %py3_dist macro.

The EPEL 8 compatible way is in my pep503-compatible branch and can be used
instead if you prefer that.

I don't plan on bumping the EPEL8 package. Should I do it? I thought policy was pretty strict about bumping version in a stable branch.

I don't think you should. I've just included that disclaimer in all such PRs, for packagers who do care about such compatibility.

Pull-Request has been merged by eclipseo

2 years ago
Metadata