diff --git python-larch/python-larch.spec python-larch/python-larch.spec.tmp
index fb51eac3e9..4b1837652b 100644
--- python-larch/python-larch.spec
+++ python-larch/python-larch.spec.tmp
@@ -2,7 +2,7 @@
 
 Name:           python-%{pkgname}
 Version:        1.20151025
-Release:        4%{?dist}
+Release:        5%{?dist}
 Summary:        Python B-tree library
 
 License:        GPLv3+
@@ -20,37 +20,45 @@ BuildRequires:  python-sphinx
 BuildRequires:  python-cliapp
 BuildRequires:  python-tracing
 BuildRequires:  python-ttystatus
+
+%global _description\
+This is an implementation of particular kind of B-tree, based on\
+research by Ohad Rodeh. See "B-trees, Shadowing, and Clones" (copied\
+here with permission of author) for details on the data\
+structure. This is the same data structure that btrfs uses. Note that\
+my implementation is independent from the btrfs one, and might differ\
+from what the paper describes.\
+\
+The distinctive feature of this B-tree is that a node is never\
+modified (sort-of). Instead, all updates are done by\
+copy-on-write. Among other things, this makes it easy to clone a tree,\
+and modify only the clone, while other processes access the original\
+tree. This is utterly wonderful for my backup application, and that's\
+the reason I wrote larch in the first place.\
+\
+I have tried to keep the implementation generic and flexible, so that\
+you may use it in a variety of situations. For example, the tree\
+itself does not decide where its nodes are stored: you provide a class\
+that does that for it. I have two implementations of the NodeStore\
+class, one for in-memory and one for on-disk storage.\
+\
+The tree attempts to guarantee this: all modifications you make will\
+be safely stored in the node store when the larch.Forest.commit method\
+is called. After that, unless you actually modify the committed tree\
+yourself, it will be safe from further modifications. (You need to\
+take care to create a new tree for further modifications, though.)\
+
+
+%description %_description
+
+%package -n python2-%{pkgname}
+Summary: %summary
 Requires:       python-cliapp
 Requires:       python-tracing
 Requires:       python-ttystatus
+%{?python_provide:%python_provide python2-%{pkgname}}
 
-%description
-This is an implementation of particular kind of B-tree, based on
-research by Ohad Rodeh. See "B-trees, Shadowing, and Clones" (copied
-here with permission of author) for details on the data
-structure. This is the same data structure that btrfs uses. Note that
-my implementation is independent from the btrfs one, and might differ
-from what the paper describes.
-
-The distinctive feature of this B-tree is that a node is never
-modified (sort-of). Instead, all updates are done by
-copy-on-write. Among other things, this makes it easy to clone a tree,
-and modify only the clone, while other processes access the original
-tree. This is utterly wonderful for my backup application, and that's
-the reason I wrote larch in the first place.
-
-I have tried to keep the implementation generic and flexible, so that
-you may use it in a variety of situations. For example, the tree
-itself does not decide where its nodes are stored: you provide a class
-that does that for it. I have two implementations of the NodeStore
-class, one for in-memory and one for on-disk storage.
-
-The tree attempts to guarantee this: all modifications you make will
-be safely stored in the node store when the larch.Forest.commit method
-is called. After that, unless you actually modify the committed tree
-yourself, it will be safe from further modifications. (You need to
-take care to create a new tree for further modifications, though.)
-
+%description -n python2-%{pkgname} %_description
 
 %package        doc
 Summary:        Documentation for %{pkgname}
@@ -85,7 +93,7 @@ rm -rf build
 make check
 
 
-%files
+%files -n python2-%{pkgname}
 %doc COPYING NEWS README
 %{_mandir}/man1/fsck-larch.1*
 %{_bindir}/fsck-larch
@@ -96,6 +104,10 @@ make check
 
 
 %changelog
+* Thu Aug 10 2017 Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> - 1.20151025-5
+- Python 2 binary package renamed to python2-larch
+  See https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3
+
 * Thu Jul 27 2017 Fedora Release Engineering <releng@fedoraproject.org> - 1.20151025-4
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild