[Git][debian-gis-team/debian-gis-team.pages.debian.net][master] Configure pbuilder hooks in ~/.pbuilderrc.

Bas Couwenberg (@sebastic) gitlab at salsa.debian.org
Wed Jan 19 07:08:02 GMT 2022



Bas Couwenberg pushed to branch master at Debian GIS Project / debian-gis-team.pages.debian.net


Commits:
1b38bade by Bas Couwenberg at 2022-01-19T08:03:59+01:00
Configure pbuilder hooks in ~/.pbuilderrc.

- - - - -


2 changed files:

- policy.xml
- public/policy/packaging.html


Changes:

=====================================
policy.xml
=====================================
@@ -848,20 +848,10 @@ DIST=<replaceable><distribution></replaceable> ARCH=<replaceable><archi
 </programlisting>
             </para>
             <para>
-              Specify the <command>pbuilder</command> hook directory when
-              creating the chroot to run the hook scripts contained therein.
+              Configure the hook directory in
+              <filename>~/.pbuilderrc</filename> to have it used by default.
 <programlisting>
-<command>sudo cowbuilder</command> <option>--create</option> \
-                <option>--distribution=<replaceable>sid</replaceable></option> \
-                <option>--basepath=/var/cache/pbuilder/base-<replaceable>sid</replaceable>.cow</option> \
-                <option>--hookdir=/var/cache/pbuilder/hook.d/</option>
-</programlisting>
-              If you have already created the chroot, then you will need to do an update and override the configuration to ensure the hook is found:
-<programlisting>
-<command>sudo cowbuilder</command> <option>--update</option> \
-                <option>--override-config</option> \
-                <option>--basepath=/var/cache/pbuilder/base-<replaceable><distribution></replaceable>-<replaceable><architecture></replaceable>.cow</option> \
-                <option>--hookdir=/var/cache/pbuilder/hook.d/</option>
+HOOKDIR="/var/cache/pbuilder/hooks.d/"
 </programlisting>
             </para>
           </sect5>


=====================================
public/policy/packaging.html
=====================================
@@ -206,20 +206,10 @@ DIST=<em class="replaceable"><code><distribution></code></em> ARCH=<em cla
 <span class="command"><strong>sed</strong></span> <code class="option">-i</code> <code class="literal">'s/lintian -I --show-overrides/& --pedantic -E/; s/^su /##&/; s/^#su /su /'</code> <code class="filename">/var/cache/pbuilder/hook.d/B90lintian</code>
 </pre><p>
             </p><p>
-              Specify the <span class="command"><strong>pbuilder</strong></span> hook directory when
-              creating the chroot to run the hook scripts contained therein.
+              Configure the hook directory in
+              <code class="filename">~/.pbuilderrc</code> to have it used by default.
 </p><pre class="programlisting">
-<span class="command"><strong>sudo cowbuilder</strong></span> <code class="option">--create</code> \
-                <code class="option">--distribution=<em class="replaceable"><code>sid</code></em></code> \
-                <code class="option">--basepath=/var/cache/pbuilder/base-<em class="replaceable"><code>sid</code></em>.cow</code> \
-                <code class="option">--hookdir=/var/cache/pbuilder/hook.d/</code>
-</pre><p>
-              If you have already created the chroot, then you will need to do an update and override the configuration to ensure the hook is found:
-</p><pre class="programlisting">
-<span class="command"><strong>sudo cowbuilder</strong></span> <code class="option">--update</code> \
-                <code class="option">--override-config</code> \
-                <code class="option">--basepath=/var/cache/pbuilder/base-<em class="replaceable"><code><distribution></code></em>-<em class="replaceable"><code><architecture></code></em>.cow</code> \
-                <code class="option">--hookdir=/var/cache/pbuilder/hook.d/</code>
+HOOKDIR="/var/cache/pbuilder/hooks.d/"
 </pre><p>
             </p></div><div class="sect5"><div class="titlepage"><div><div><h6 class="title"><a id="git-pbuilder-update"></a>Updating cowbuilder chroots</h6></div></div></div><p>
               Remember to update the chroots for
@@ -1225,7 +1215,7 @@ allowed_distributions = .*
           <span class="command"><strong>gbp-pq</strong></span> can be used for treating the patches as a
           series of commits, see:
           <a class="ulink" href="https://honk.sigxcpu.org/piki/development/debian_packages_in_git/" target="_top">Keeping debian/patches on a patch-queue branch</a>
-        </p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a id="git-commit-policy"></a>Commit policy</h4></div></div></div><p></p><div class="sect4"><div class="titlepage"><div><div><h5 class="title"><a id="idm1442"></a>Single change per commit</h5></div></div></div><p>
+        </p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a id="git-commit-policy"></a>Commit policy</h4></div></div></div><p></p><div class="sect4"><div class="titlepage"><div><div><h5 class="title"><a id="idm1427"></a>Single change per commit</h5></div></div></div><p>
             This is true for any VCS, but it won't hurt saying it again:
             please include only one change in each commit.
           </p><p>
@@ -1233,7 +1223,7 @@ allowed_distributions = .*
             <span class="command"><strong>git add</strong></span> <code class="option">-p</code>'s
             ability to stage single lines (or hunks) is a huge help
             if you have done several unrelated changes in the sources.
-          </p></div><div class="sect4"><div class="titlepage"><div><div><h5 class="title"><a id="idm1449"></a>Changelog maintenance</h5></div></div></div><p>
+          </p></div><div class="sect4"><div class="titlepage"><div><div><h5 class="title"><a id="idm1434"></a>Changelog maintenance</h5></div></div></div><p>
             Some prefer to update <code class="filename">debian/changelog</code>
             with each commit, while others prefer to do that only at release time
             by using <span class="command"><strong>gbp dch</strong></span>.



View it on GitLab: https://salsa.debian.org/debian-gis-team/debian-gis-team.pages.debian.net/-/commit/1b38bade25a3e29b83b978b66abfb4124cf354bb

-- 
View it on GitLab: https://salsa.debian.org/debian-gis-team/debian-gis-team.pages.debian.net/-/commit/1b38bade25a3e29b83b978b66abfb4124cf354bb
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-grass-devel/attachments/20220119/25cf141a/attachment-0001.htm>


More information about the Pkg-grass-devel mailing list