Fixed 'duplicate label' Sphinx warnings.

Author: torsava

applications.rst

@@ -29,8 +29,6 @@ Change ``BuildRequires`` from ``python-devel`` to ``python3-devel`` and adjust a
 **It is very important that you don't use any Python 2 dependencies as that would make your package depend both on Python version 2 and version 3, which would render your porting efforts useless.**
 
 
-.. _build-section:
-
 %build
 ^^^^^^
 
@@ -52,7 +50,7 @@ In rare cases, you might encounter some non-Python build script such as a Makefi
 
 The ``%install`` section will oftentimes contain the ``%py_install`` and ``%py2_install`` macros; you can replace these with the new Python 3 macro ``%py3_install``.
 
-Furthermore, as in the preceding `build-section`_ section, you will frequently find custom scripts or commands prefixed by either the ``%{__python}`` or ``%{__python2}`` macros or simply preceded by an invocation of the Python interpreter without the use of macros at all.
+Furthermore, as in the preceding `%build`_ section, you will frequently find custom scripts or commands prefixed by either the ``%{__python}`` or ``%{__python2}`` macros or simply preceded by an invocation of the Python interpreter without the use of macros at all.
 
 In the install section, try substituting it with the new ``%py3_install`` macro, which should figure out what to do automatically. If that doesn't work, or if you're porting the ``%check`` section, just make sure that any custom scripts or commands are invoked by the new ``%{__python3}`` macro.
 

snippets/install_non-python-script.inc

@@ -1 +1 @@
-Again as in the `build-section`_ section, in the rare cases where you encounter a non-Python install script such as a Makefile, consult documentation for the specific install method and make adjustments on your own.
+Again as in the `%build`_ section, in the rare cases where you encounter a non-Python install script such as a Makefile, consult documentation for the specific install method and make adjustments on your own.

subsections/h2-modifications.inc

@@ -1,5 +1,3 @@
-.. _modifications:
-
 Modifications
 -------------
 

subsections/h3-build.inc

@@ -1,5 +1,3 @@
-.. _build-section:
-
 %build
 ^^^^^^
 

subsections/h3-install.inc

@@ -1,7 +1,7 @@
 %install
 ^^^^^^^^
 
-First, in the same manner as in the preceding `build-section`_ section, it is advisable to upgrade the current Python 2 install command to use the new ``%py2_install`` macro, however, if that doesn't work for you, you can stick with the current install command, just make sure it's invoked by the ``%{__python2}`` macro.
+First, in the same manner as in the preceding `%build`_ section, it is advisable to upgrade the current Python 2 install command to use the new ``%py2_install`` macro, however, if that doesn't work for you, you can stick with the current install command, just make sure it's invoked by the ``%{__python2}`` macro.
 
 After that, add the corresponding Python 3 install command, which will be either be the custom command prefixed by ``%{__python3}`` or the new ``%py3_install`` macro.
 

subsections/h4-description.inc

@@ -1,5 +1,3 @@
-.. _description-subsection:
-
 %description
 ************
 

tools.rst

@@ -39,7 +39,7 @@ Let's take an example spec file and port it to illustrate the process. We start
 
 The ``%install`` section is perhaps the most crucial one, because we have to be very mindful of which executable goes where and what symlinks should be created.
 
-First, in the same manner as in the preceding `build-section`_ section, it is advisable to upgrade the current Python 2 install command to use the new ``%py2_install`` macro, however, if that doesn't work for you, you can stick with the current install command, just make sure it's invoked by the ``%{__python2}`` macro. The corresponding Python 3 install command will then either be the custom command prefixed by ``%{__python3}`` or the new ``%py3_install`` macro, which I'll be using in this example.
+First, in the same manner as in the preceding `%build`_ section, it is advisable to upgrade the current Python 2 install command to use the new ``%py2_install`` macro, however, if that doesn't work for you, you can stick with the current install command, just make sure it's invoked by the ``%{__python2}`` macro. The corresponding Python 3 install command will then either be the custom command prefixed by ``%{__python3}`` or the new ``%py3_install`` macro, which I'll be using in this example.
 
 .. include:: snippets/install_non-python-script.inc