From fc74aa26134ef89c62c8b6888a142aeb6d4cb4f5 Mon Sep 17 00:00:00 2001
From: Guido Günther <agx@sigxcpu.org>
Date: Sun, 30 Jun 2013 23:37:43 +0200
Subject: Fix broken xrefs

---
 docs/chapters/building.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'docs/chapters/building.sgml')

diff --git a/docs/chapters/building.sgml b/docs/chapters/building.sgml
index 3029672..495b585 100644
--- a/docs/chapters/building.sgml
+++ b/docs/chapters/building.sgml
@@ -87,7 +87,7 @@ export-dir=../build-area
     <title>Running lintian</title>
 	<para>&gbp-buildpackage; exports several variables into the
 	<option>posttag</option>'s environment (for details see the <xref
-	linkend="man.git.buildpackage">).
+	linkend="man.gbp.buildpackage">).
 	To invoke &lintian; we need to tell it where to find the changes file:
 <programlisting>
 <command>git-buildpackage</command> <option>--git-postbuild</option>=<replaceable>'lintian $GBP_CHANGES_FILE'</replaceable>
@@ -155,7 +155,7 @@ echo "done."
     <title>Running postexport hook</title>
     <para>&gbp-buildpackage; exports several variables into the
 	<option>postexport</option>'s environment (for details see
-	the <xref linkend="man.git.buildpackage">). The motivation
+	the <xref linkend="man.gbp.buildpackage">). The motivation
 	for the postexport action is to allow further adjustment of
 	the sources prior to building the package. A typical use case
 	scenario is to allow creating multiple source and binary
-- 
cgit v1.2.3