no fancy html in commands pre

debomatic-webui/views/commands.ejs

@@ -26,8 +26,7 @@ rebuilding packages. These operations are handled by commands stored in
 <code>.commands</code> files, and uploaded into Deb-o-Matic <code>packagedir</code> by using
 <code>dcut</code> utility, or by hand.</p>
 <p>Using dcut is usually simpler, just launch the following command:</p>
-<pre>
-<div><em>dcut -U mydebomatic commandfile.commands</em></div></pre>
+<pre>dcut -U mydebomatic commandfile.commands</pre>
 <p>where <code>mydebomatic</code> is a dput host as described in dput.cf (5) man page, and
 <code>commandfile.commands</code> is the file containing the commands to be executed by
 Deb-o-Matic.</p>
@@ -41,8 +40,7 @@ usually safer to issue a single command per file.</p>
 <h3>Remove packages</h3>
 <p>It could happen some files are kept into Deb-o-Matic <code>packagedir</code> and you
 need to remove them. In order to do so, you must use the <code>rm</code> command:</p>
-<pre>
-<div><em>echo “rm foo*” &gt; foo.commands</em></div></pre>
+<pre>echo "rm foo*" &gt; foo.commands</pre>
 <p>where <code>foo*</code> is a regular expression matching the files you want to remove.</p>
 </div>
 <div class="tab-pane" id="rebuild-packages">
@@ -50,16 +48,14 @@ need to remove them. In order to do so, you must use the <code>rm</code> command
 <p>You could want to rebuild a package already in the mirrors to see whether it
 compiles with newer packages, to analyze its content, and so on. In order to do
 so, you must use the <code>rebuild</code> command:</p>
-<pre>
-<div><em>echo “rebuild foo_version dist” &gt; foo.commands</em></div></pre>
+<pre>echo "rebuild foo_version dist" &gt; foo.commands</pre>
 <p>where <code>foo</code> is the name of the source package you want to rebuild,
 <code>version</code> is the version of the package you want to rebuild, and <code>dist</code> is
 the distribution which rebuild the package for.</p>
 <p>Deb-o-Matic can also rebuild packages available in other distributions. The
 syntax is similar, you just have to indicate which distribution to pick
 packages from:</p>
-<pre>
-<div><em>echo “rebuild foo_version dist origin” &gt; foo.commands</em></div></pre>
+<pre>echo "rebuild foo_version dist origin" &gt; foo.commands</pre>
 <p>where <code>origin</code> is the distribution to pick packages from.</p>
 <div class="alert alert-warning">
 <b>Caution:</b> Make sure packages are available in the distribution mirrors, otherwise they
@@ -72,8 +68,7 @@ cannot be downloaded and processed by Deb-o-Matic.
 architecture dependent binaries only. Additional information can be found in
 <a class="reference external" href="http://www.debian.org/doc/manuals/developers-reference/pkgs.html#porter-guidelines">Debian Developer’s Reference</a>.</p>
 <p>In order to do so, you must use the <code>rebuild</code> command:</p>
-<pre>
-<div><em>echo “porter foo_version dist Joe Doe &lt;j.doe@acme.com&gt;” &gt; foo.commands</em></div></pre>
+<pre>echo "porter foo_version dist Joe Doe &lt;j.doe@acme.com&gt;" &gt; foo.commands</pre>
 <p>where foo is the name of the source package you want to rebuild, version is
 the version of the package you want to rebuild, dist is the distribution which
 rebuild package for, and the element between quotes is the address to be used
@@ -89,8 +84,7 @@ cannot be downloaded and processed by Deb-o-Matic.
 <p>You could want to rebuild a package already in the mirrors also adding a
 specific build-dependency to see whether it compiles with a newer library
 version. In order to do so, you must use the <code>builddep</code> command:</p>
-<pre>
-<div><em>echo “builddep foo_version dist extrapackage=packageversion” &gt; foo.commands</em></div></pre>
+<pre>echo "builddep foo_version dist extrapackage=packageversion" &gt; foo.commands</pre>
 <p>where <code>extrapackage</code> is the name of the package you want to install before
 the compilation takes place, and <code>packageversion</code> is the optional version of
 the package you want to install.</p>