commit:     0cd23b216690abcefacab37b5c4c36a50e713c42
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Thu Jan  9 21:03:23 2020 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Thu Jan  9 21:24:38 2020 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=0cd23b21

Fix broken internal links.

Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 appendices/common-problems/text.xml     | 2 +-
 ebuild-writing/common-mistakes/text.xml | 9 +++++----
 ebuild-writing/user-submitted/text.xml  | 6 +++---
 profiles/use.desc/text.xml              | 2 +-
 4 files changed, 10 insertions(+), 9 deletions(-)

diff --git a/appendices/common-problems/text.xml 
b/appendices/common-problems/text.xml
index 430e74b..c16608b 100644
--- a/appendices/common-problems/text.xml
+++ b/appendices/common-problems/text.xml
@@ -102,7 +102,7 @@ for security reasons. If this message is shown, you have a 
couple of options:
   </li>
   <li>
     Use <c>append-ldflags</c> (see <uri
-    link="ebuild-writing/functions/src_compile/build-environment/#Adding 
Additional Flags"/>)
+    link="::ebuild-writing/functions/src_compile/build-environment#Adding 
Additional Flags"/>)
     to add <c>-Wl,-z,now</c>. This will affect <e>all</e> binaries installed, 
not just the setXid ones.
   </li>
 </ul>

diff --git a/ebuild-writing/common-mistakes/text.xml 
b/ebuild-writing/common-mistakes/text.xml
index b0f841a..9cd998c 100644
--- a/ebuild-writing/common-mistakes/text.xml
+++ b/ebuild-writing/common-mistakes/text.xml
@@ -367,8 +367,8 @@ Please check if the HOMEPAGE variable is right and leads 
users to the right
 page if they want to find out more about the package. And make sure the
 DESCRIPTION is not overly long. Good descriptions will describe the main
 function of the package in a sentence. Set HOMEPAGE to
-<uri link="::ebuild-maintenance#Homepage unavailable">No_homepage wiki 
page</uri>,
-if there is none.
+<uri link="::ebuild-maintenance/maintenance-tasks#Homepage unavailable">
+No_homepage wiki page</uri>, if there is none.
 </p>
 
 </body>
@@ -450,8 +450,9 @@ at least when the ebuild hits the stable branch.
 <body>
 
 <p>
-Please submit ebuilds properly by following the <uri
-link="::ebuild-maintenance#adding-a-new-ebuild">Adding new Ebuild</uri> 
tutorial.
+Please submit ebuilds properly by following the
+<uri link="::ebuild-maintenance/maintenance-tasks#Adding a new ebuild">
+Adding new Ebuild</uri> tutorial.
 </p>
 
 </body>

diff --git a/ebuild-writing/user-submitted/text.xml 
b/ebuild-writing/user-submitted/text.xml
index 2f384ca..b97af10 100644
--- a/ebuild-writing/user-submitted/text.xml
+++ b/ebuild-writing/user-submitted/text.xml
@@ -22,10 +22,10 @@ The user-submitted ebuild must not contain custom headers 
like this:
 
 <p>
 Such information should be included in the git commit message instead.
-The use of tags such as <c>Suggested-By:</c> or <c>Reported-By:</c>in
+The use of tags such as <c>Suggested-By:</c> or <c>Reported-By:</c> in
 the commit message, as explained in the
-<uri link="::ebuild-maintenance#git-commit-message-format">commit
-message format section</uri>, is highly encouraged.
+<uri link="::ebuild-maintenance/git#Git Commit Message Format">
+commit message format section</uri>, is highly encouraged.
 Note that ebuilds received in the form of git patches or pull requests
 will have the user as the commit author by default, in which case
 including the user information in the commit message explicitly

diff --git a/profiles/use.desc/text.xml b/profiles/use.desc/text.xml
index ddb081a..87df40c 100644
--- a/profiles/use.desc/text.xml
+++ b/profiles/use.desc/text.xml
@@ -14,7 +14,7 @@ discussion on the <c>gentoo-dev</c> list.
 The <c>metadata.xml</c> file on each ebuild category contains a list of the 
local
 <c>USE</c> flags, together with short description for the package in the said 
category.
 More information about the <c>metadata.xml</c> file can be found
-<uri link="::ebuild-writing/misc-files/metadata/index.html">here.</uri>
+<uri link="::ebuild-writing/misc-files/metadata">here.</uri>
 </p>
 
 <note>

Reply via email to