Package: debian-policy
Version: 4.7.4.1
Severity: minor

I noticed that a number of cross-references related to build profiles 
are broken.  The attached patch should fix this.  I believe it contains 
no normative policy changes.

Thanks,

-- 
Colin Watson (he/him)                              [[email protected]]
>From 0cb842bf311cda2e063069fbc3cc8cb8dfb2efc4 Mon Sep 17 00:00:00 2001
From: Colin Watson <[email protected]>
Date: Wed, 27 May 2026 09:48:16 +0100
Subject: [PATCH] Fix broken links related to build profiles

Several labels were malformed, and the `s-f-Build-Profiles` label was
referenced but not defined.

Fixing this caused the `s-restrictions` label to be defined in two
places with entirely different contents, so I renamed the newer one to
`s-dep-restrictions`.
---
 policy/ch-controlfields.rst | 4 +++-
 policy/ch-relationships.rst | 6 +++---
 policy/ch-source.rst        | 2 +-
 3 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 69467c4..9ba3c98 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -1532,13 +1532,15 @@ Since removing this value tends to break reverse dependencies that
 employ ``:any``, uses of it should be discussed with
 *[email protected]* first.
 
+.. _s-f-Build-Profiles:
+
 ``Build-Profiles``
 ~~~~~~~~~~~~~~~~~~
 
 This field occurs in the binary package sections of a source template control
 file. It expresses whether the binary package is to be produced, given a set
 of enabled build profiles.  The condition uses the same `restriction formula
-syntax <s-restrictions>` as the ``Build-Depends`` field. In the following
+syntax <s-dep-restrictions>` as the ``Build-Depends`` field. In the following
 example, ``libglib2.0-tests`` is only built if both the ``noinsttest`` and
 ``nogir`` build profiles are not enabled:
 
diff --git a/policy/ch-relationships.rst b/policy/ch-relationships.rst
index d2e0f53..9afd29c 100644
--- a/policy/ch-relationships.rst
+++ b/policy/ch-relationships.rst
@@ -50,7 +50,7 @@ For example, a list of dependencies might appear as:
     Version: 1.3.17-1
     Depends: libc6 (>= 2.2.1), default-mta | mail-transport-agent
 
-.. _s-restrictions
+.. _s-dep-restrictions:
 
 Restrictions
 ~~~~~~~~~~~~
@@ -103,7 +103,7 @@ package template control file ``debian/control``.  The dependency is
 ignored, in the sense that it will not appear in the corresponding
 binary package control file, if the restriction does not match.
 
-.. _s-architecture-restrictions
+.. _s-architecture-restrictions:
 
 Architecture restrictions
 ^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -188,7 +188,7 @@ is equivalent to ``foo`` on architectures using the Linux kernel and any
 cpu, ``bar`` on architectures using any kernel and an i386 cpu, and
 ``baz`` on any architecture using a kernel other than Linux.
 
-.. _s-profile-restrictions
+.. _s-profile-restrictions:
 
 Build profile restriction formulas
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
diff --git a/policy/ch-source.rst b/policy/ch-source.rst
index f31f56a..5228e0b 100644
--- a/policy/ch-source.rst
+++ b/policy/ch-source.rst
@@ -621,7 +621,7 @@ order to make it work for your package.
             # Code to run the package test suite.
     endif
 
-.. _s-rules-build-profiles
+.. _s-rules-build-profiles:
 
 ``debian/rules`` and ``DEB_BUILD_PROFILES``
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
2.53.0

Reply via email to