From 7541df9cd0de42093197fad8d91f802d2e3c40d4 Mon Sep 17 00:00:00 2001
From: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Date: Aug 19 2017 13:42:41 +0000
Subject: Python 2 binary package renamed to python2-sanction


---

diff --git a/python-sanction.spec b/python-sanction.spec
index 4161eea..fcc59b1 100644
--- a/python-sanction.spec
+++ b/python-sanction.spec
@@ -6,7 +6,7 @@
 
 Name:               python-sanction
 Version:            0.3.1
-Release:            10%{?dist}
+Release:            11%{?dist}
 Summary:            A simple, lightweight OAuth2 client
 Group:              Development/Libraries
 License:            MIT
@@ -24,35 +24,43 @@ BuildRequires:      python3-nose
 %endif
 
 
-%description
-python-sanction is a lightweight, dead simple client implementation of
-the OAuth2 protocol.
+%global _description\
+python-sanction is a lightweight, dead simple client implementation of\
+the OAuth2 protocol.\
+\
+- Variations on OAuth2 client implementation range from a few hundred LOC\
+  to thousands. In a Pythonic world, there's absolutely no need for this when\
+  simply dealing with the client side of the spec. Currently, sanction sits\
+  at a whopping 65 LOC, one class. This makes the library tremendously easy\
+  to grok.\
+\
+- Most providers have varying levels of diversion from the official spec.\
+  The goal with this library is to either handle these diversions natively,\
+  or expose a method to allow client code to deal with it efficiently and\
+  effectively.\
+\
+- Three of the four OAuth2 flows should be supported by this library.\
+  Currently, only authorization code and client credential flows have been\
+  tested due to lack of other (known) implementations.\
+\
+sanction has been tested with the following OAuth2 providers:\
+\
+* Facebook (include the test API)\
+* Google\
+* Foursquare\
+* bitly\
+* GitHub\
+* StackExchange\
+* Instagram\
+* DeviantArt
 
-- Variations on OAuth2 client implementation range from a few hundred LOC
-  to thousands. In a Pythonic world, there's absolutely no need for this when
-  simply dealing with the client side of the spec. Currently, sanction sits
-  at a whopping 65 LOC, one class. This makes the library tremendously easy
-  to grok.
+%description %_description
 
-- Most providers have varying levels of diversion from the official spec.
-  The goal with this library is to either handle these diversions natively,
-  or expose a method to allow client code to deal with it efficiently and
-  effectively.
+%package -n python2-sanction
+Summary: %summary
+%{?python_provide:%python_provide python2-sanction}
 
-- Three of the four OAuth2 flows should be supported by this library.
-  Currently, only authorization code and client credential flows have been
-  tested due to lack of other (known) implementations.
-
-sanction has been tested with the following OAuth2 providers:
-
-* Facebook (include the test API)
-* Google
-* Foursquare
-* bitly
-* GitHub
-* StackExchange
-* Instagram
-* DeviantArt
+%description -n python2-sanction %_description
 
 %if 0%{?with_python3}
 %package -n python3-sanction
@@ -129,7 +137,7 @@ popd
 
 PYTHONPATH=$(pwd) nosetests
 
-%files
+%files -n python2-sanction
 %doc README.rst LICENSE.txt
 %{python_sitelib}/%{modname}/
 %{python_sitelib}/%{modname}-%{version}*
@@ -142,6 +150,10 @@ PYTHONPATH=$(pwd) nosetests
 %endif
 
 %changelog
+* Sat Aug 19 2017 Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> - 0.3.1-11
+- Python 2 binary package renamed to python2-sanction
+  See https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3
+
 * Thu Jul 27 2017 Fedora Release Engineering <releng@fedoraproject.org> - 0.3.1-10
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild