Description: Fix build errors
 Backported from upstream git
Author: Carsten Leonhardt <leo@debian.org>
Last-Update: 2024-11-23
Forwarded: not-needed

--- a/latex/license.tex
+++ b/latex/license.tex
@@ -15,7 +15,7 @@
 \section{CC-BY-SA}
 \index[general]{CC-BY-SA}
 
-The \ilink{Creative Commons Attribution-ShareAlike 4.0 International
+The \bilink{Creative Commons Attribution-ShareAlike 4.0 International
 License (CC-BY-SA)}{CCbySAChapter} is used for this manual,
 which is a free and open license. Though there are certain
 restrictions that come with this license you may in general freely
@@ -30,7 +30,7 @@
 \index[general]{GPL }
 
 The vast bulk of the source code is released under the 
-\ilink{Affero GNU General Public License version 3.}{GplChapter}.
+\bilink{Affero GNU General Public License version 3.}{GplChapter}.
 
 Most of this code is copyrighted: Copyright \copyright 2000-2016,
 Kern Sibbald.
@@ -42,7 +42,7 @@
 \index[general]{LGPL }
 
 Some of the Bacula library source code is released under the 
-\ilink{GNU Lesser General Public License.}{LesserChapter} This
+\bilink{GNU Lesser General Public License.}{LesserChapter} This
 permits third parties to use these parts of our code in their proprietary
 programs to interface to Bacula. 
 
--- a/manuals/en/problems/rpm-faq.tex
+++ b/manuals/en/problems/rpm-faq.tex
@@ -176,7 +176,7 @@
 \end{bVerbatim}
 
 Further, if you are using File storage volumes rather than tapes those
-files will also need to have ownership set to user \textt{bacula} and group \textt{bacula}.
+files will also need to have ownership set to user \texttt{bacula} and group \texttt{bacula}.
 
 \item \label{blb:faq9}
    \textbf{There are a lot of rpm packages.  Which packages do I need for
@@ -314,7 +314,7 @@
 \begin{bitemize}
 \item [Wrong /var/bacula Permissions]
   By default, the Director and Storage daemon do not run with
-  root permission. If the \bdirectoryname{/var/bacula} is owned by \textt{root}, then it
+  root permission. If the \bdirectoryname{/var/bacula} is owned by \texttt{root}, then it
   is possible that the Director and the Storage daemon will not
   be able to access this directory, which is used as the Working
   Directory. To fix this, the easiest thing to do is:
--- a/manuals/en/main/dirdconf.tex
+++ b/manuals/en/main/dirdconf.tex
@@ -4214,7 +4214,7 @@
    point and \texttt{<filter>} is a standard LDAP search object filter which support dynamic string
    substitution: \texttt{\%u} will be replaced by credential's username and \texttt{\%p} by credential's
    password, i.e. \texttt{query=dc=bacula,dc=com/(cn=\%u)}.
- \item  [starttls] - instruct BPAM LDAP Plugin to use **StartTLS** extension if LDAP Directory service
+ \item  [starttls] - instruct BPAM LDAP Plugin to use \texttt{StartTLS} extension if LDAP Directory service
    will support it and follback to no TLS if this extension is not available.
 \item [starttlsforce] - does the same what `starttls` but resport error on fallback.
 \end{itemize}
--- a/manuals/en/main/newfeatures.tex
+++ b/manuals/en/main/newfeatures.tex
@@ -165,7 +165,7 @@
    point and \texttt{<filter>} is a standard LDAP search object filter which support dynamic string
    substitution: \texttt{\%u} will be replaced by credential's username and \texttt{\%p} by credential's
    password, i.e. \texttt{query=dc=bacula,dc=com/(cn=\%u)}.
- \item  [starttls] - Instruct the BPAM LDAP Plugin to use the **StartTLS** extension if the LDAP Directory service
+ \item  [starttls] - Instruct the BPAM LDAP Plugin to use the \texttt{StartTLS} extension if the LDAP Directory service
    supports it and fallback to no TLS if this extension is not available.
 \item [starttlsforce] - Does the same as the `starttls` setting does but reports error on fallback.
 \end{itemize}
@@ -7362,7 +7362,7 @@
  db_address=
  db_port=0
  db_socket=
-\end{verbatim} %$
+\end{verbatim}
 
 You can now specify the database connection port in the command line.
 
