[med-svn] [Git][med-team/policy][master] pbuilder-options=--source-only-changes
Andreas Tille
gitlab at salsa.debian.org
Thu Sep 5 09:47:38 BST 2019
Andreas Tille pushed to branch master at Debian Med / policy
Commits:
7cff1613 by Andreas Tille at 2019-09-05T08:47:21Z
pbuilder-options=--source-only-changes
- - - - -
2 changed files:
- policy.html
- policy.rst
Changes:
=====================================
policy.html
=====================================
@@ -3,7 +3,7 @@
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="generator" content="Docutils 0.14: http://docutils.sourceforge.net/" />
+<meta name="generator" content="Docutils 0.15.2: http://docutils.sourceforge.net/" />
<title>policy.rst</title>
<style type="text/css">
@@ -367,91 +367,92 @@ ul.auto-toc {
<div class="contents topic" id="table-of-contents">
<p class="topic-title first">Table of Contents</p>
<ul class="simple">
-<li><a class="reference internal" href="#introduction" id="id9">Introduction</a></li>
-<li><a class="reference internal" href="#how-to-contribute" id="id10">How to Contribute</a><ul>
-<li><a class="reference internal" href="#membership" id="id11">Membership</a></li>
-<li><a class="reference internal" href="#essential-readings" id="id12">Essential readings</a></li>
-<li><a class="reference internal" href="#contributing-to-this-policy" id="id13">Contributing to this Policy</a></li>
+<li><a class="reference internal" href="#introduction" id="id10">Introduction</a></li>
+<li><a class="reference internal" href="#how-to-contribute" id="id11">How to Contribute</a><ul>
+<li><a class="reference internal" href="#membership" id="id12">Membership</a></li>
+<li><a class="reference internal" href="#essential-readings" id="id13">Essential readings</a></li>
+<li><a class="reference internal" href="#contributing-to-this-policy" id="id14">Contributing to this Policy</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#repositories" id="id14">Repositories</a><ul>
-<li><a class="reference internal" href="#give-me-the-source" id="id15">Give me the source!</a></li>
-<li><a class="reference internal" href="#common-git-repository-structures" id="id16">Common Git repository structures</a><ul>
-<li><a class="reference internal" href="#gbp-buildpackage" id="id17"><tt class="docutils literal">gbp buildpackage</tt></a></li>
-<li><a class="reference internal" href="#social-git" id="id18">Social Git</a></li>
-<li><a class="reference internal" href="#other-branches" id="id19">Other branches</a></li>
+<li><a class="reference internal" href="#repositories" id="id15">Repositories</a><ul>
+<li><a class="reference internal" href="#give-me-the-source" id="id16">Give me the source!</a></li>
+<li><a class="reference internal" href="#common-git-repository-structures" id="id17">Common Git repository structures</a><ul>
+<li><a class="reference internal" href="#gbp-buildpackage" id="id18"><tt class="docutils literal">gbp buildpackage</tt></a></li>
+<li><a class="reference internal" href="#social-git" id="id19">Social Git</a></li>
+<li><a class="reference internal" href="#other-branches" id="id20">Other branches</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#git-tips" id="id20">Git tips</a><ul>
-<li><a class="reference internal" href="#set-the-devscripts-variables-debemail-and-debfullname" id="id21">Set the devscripts variables <tt class="docutils literal">DEBEMAIL</tt> and <tt class="docutils literal">DEBFULLNAME</tt></a></li>
-<li><a class="reference internal" href="#configure-git-to-commit-using-your-packager-name-and-address" id="id22">Configure Git to commit using your packager name and address.</a></li>
-<li><a class="reference internal" href="#to-create-a-new-local-git-repository" id="id23">To create a new local git repository</a></li>
-<li><a class="reference internal" href="#to-clone-and-follow-every-branch-of-a-git-repository" id="id24">To clone and follow every branch of a git repository.</a></li>
-<li><a class="reference internal" href="#to-track-extra-upstream-branches-simply-check-them-out" id="id25">To track extra upstream branches, simply check them out.</a></li>
-<li><a class="reference internal" href="#to-create-a-pristine-tar-branch-when-it-is-missing" id="id26">To create a pristine-tar branch when it is missing.</a></li>
-<li><a class="reference internal" href="#creating-a-new-repository-on-salsa" id="id27">Creating a new repository on Salsa</a></li>
-<li><a class="reference internal" href="#to-change-the-default-branch" id="id28">To change the default branch.</a></li>
-<li><a class="reference internal" href="#to-push-the-package" id="id29">To push the package.</a></li>
-<li><a class="reference internal" href="#to-push-all-your-work" id="id30">To push all your work</a></li>
-<li><a class="reference internal" href="#to-tag-a-release" id="id31">To tag a release</a></li>
-<li><a class="reference internal" href="#if-upstream-manages-his-sources-with-git" id="id32">If upstream manages his sources with Git.</a></li>
-<li><a class="reference internal" href="#to-make-gbp-buildpackage-build-the-package-with-pdebuild" id="id33">To make <tt class="docutils literal">gbp buildpackage</tt> build the package with <tt class="docutils literal">pdebuild</tt>.</a></li>
+<li><a class="reference internal" href="#git-tips" id="id21">Git tips</a><ul>
+<li><a class="reference internal" href="#set-the-devscripts-variables-debemail-and-debfullname" id="id22">Set the devscripts variables <tt class="docutils literal">DEBEMAIL</tt> and <tt class="docutils literal">DEBFULLNAME</tt></a></li>
+<li><a class="reference internal" href="#configure-git-to-commit-using-your-packager-name-and-address" id="id23">Configure Git to commit using your packager name and address.</a></li>
+<li><a class="reference internal" href="#to-create-a-new-local-git-repository" id="id24">To create a new local git repository</a></li>
+<li><a class="reference internal" href="#to-clone-and-follow-every-branch-of-a-git-repository" id="id25">To clone and follow every branch of a git repository.</a></li>
+<li><a class="reference internal" href="#to-track-extra-upstream-branches-simply-check-them-out" id="id26">To track extra upstream branches, simply check them out.</a></li>
+<li><a class="reference internal" href="#to-create-a-pristine-tar-branch-when-it-is-missing" id="id27">To create a pristine-tar branch when it is missing.</a></li>
+<li><a class="reference internal" href="#creating-a-new-repository-on-salsa" id="id28">Creating a new repository on Salsa</a></li>
+<li><a class="reference internal" href="#to-change-the-default-branch" id="id29">To change the default branch.</a></li>
+<li><a class="reference internal" href="#to-push-the-package" id="id30">To push the package.</a></li>
+<li><a class="reference internal" href="#to-push-all-your-work" id="id31">To push all your work</a></li>
+<li><a class="reference internal" href="#to-tag-a-release" id="id32">To tag a release</a></li>
+<li><a class="reference internal" href="#if-upstream-manages-his-sources-with-git" id="id33">If upstream manages his sources with Git.</a></li>
+<li><a class="reference internal" href="#to-make-gbp-buildpackage-build-the-package-with-pdebuild" id="id34">To make <tt class="docutils literal">gbp buildpackage</tt> build the package with <tt class="docutils literal">pdebuild</tt>.</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#updating-a-source-package-managed-with-git" id="id34">Updating a source package managed with Git</a></li>
+<li><a class="reference internal" href="#updating-a-source-package-managed-with-git" id="id35">Updating a source package managed with Git</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#packaging" id="id35">Packaging</a><ul>
-<li><a class="reference internal" href="#newcomer-guidelines-for-building-proper-debian-packages" id="id36">Newcomer guidelines for building proper Debian packages</a></li>
-<li><a class="reference internal" href="#announcing-intent-to-package" id="id37">Announcing intent to package</a></li>
-<li><a class="reference internal" href="#backports" id="id38">Backports</a></li>
-<li><a class="reference internal" href="#ppa-for-ubuntu" id="id39">PPA for Ubuntu</a></li>
-<li><a class="reference internal" href="#debian-unstable-chroot-on-ubuntu" id="id40">Debian unstable chroot on Ubuntu</a></li>
-<li><a class="reference internal" href="#derivatives-working-together-with-debian-med" id="id41">Derivatives working together with Debian Med</a></li>
-<li><a class="reference internal" href="#r-packages" id="id42">R packages</a></li>
+<li><a class="reference internal" href="#packaging" id="id36">Packaging</a><ul>
+<li><a class="reference internal" href="#newcomer-guidelines-for-building-proper-debian-packages" id="id37">Newcomer guidelines for building proper Debian packages</a></li>
+<li><a class="reference internal" href="#announcing-intent-to-package" id="id38">Announcing intent to package</a></li>
+<li><a class="reference internal" href="#backports" id="id39">Backports</a></li>
+<li><a class="reference internal" href="#ppa-for-ubuntu" id="id40">PPA for Ubuntu</a></li>
+<li><a class="reference internal" href="#debian-unstable-chroot-on-ubuntu" id="id41">Debian unstable chroot on Ubuntu</a></li>
+<li><a class="reference internal" href="#derivatives-working-together-with-debian-med" id="id42">Derivatives working together with Debian Med</a></li>
+<li><a class="reference internal" href="#r-packages" id="id43">R packages</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#tasks" id="id43">Tasks</a></li>
-<li><a class="reference internal" href="#policy" id="id44">Policy</a><ul>
-<li><a class="reference internal" href="#id1" id="id45"><tt class="docutils literal">debian/control</tt></a></li>
-<li><a class="reference internal" href="#id2" id="id46"><tt class="docutils literal">debian/copyright</tt></a></li>
-<li><a class="reference internal" href="#id3" id="id47"><tt class="docutils literal">debian/changelog</tt></a></li>
-<li><a class="reference internal" href="#id4" id="id48"><tt class="docutils literal">debian/upstream</tt></a></li>
-<li><a class="reference internal" href="#id5" id="id49"><tt class="docutils literal">debian/gbp.conf</tt></a></li>
-<li><a class="reference internal" href="#id6" id="id50"><tt class="docutils literal">debian/README.source</tt></a></li>
-<li><a class="reference internal" href="#id7" id="id51"><tt class="docutils literal">debian/README.test</tt></a></li>
-<li><a class="reference internal" href="#id8" id="id52"><tt class="docutils literal">debian/source/format</tt></a></li>
-<li><a class="reference internal" href="#debian-source-options" id="id53"><tt class="docutils literal">debian/source/options</tt></a></li>
-<li><a class="reference internal" href="#debhelper" id="id54">Debhelper</a></li>
-<li><a class="reference internal" href="#version-control-systems" id="id55">Version control systems</a><ul>
-<li><a class="reference internal" href="#source-package-stored-in-a-git-repository-on-salsa" id="id56">Source package stored in a Git repository on Salsa</a></li>
-<li><a class="reference internal" href="#tags" id="id57">Tags</a></li>
+<li><a class="reference internal" href="#tasks" id="id44">Tasks</a></li>
+<li><a class="reference internal" href="#policy" id="id45">Policy</a><ul>
+<li><a class="reference internal" href="#id1" id="id46"><tt class="docutils literal">debian/control</tt></a></li>
+<li><a class="reference internal" href="#id2" id="id47"><tt class="docutils literal">debian/copyright</tt></a></li>
+<li><a class="reference internal" href="#id3" id="id48"><tt class="docutils literal">debian/changelog</tt></a></li>
+<li><a class="reference internal" href="#id4" id="id49"><tt class="docutils literal">debian/upstream</tt></a></li>
+<li><a class="reference internal" href="#id5" id="id50"><tt class="docutils literal">debian/gbp.conf</tt></a></li>
+<li><a class="reference internal" href="#id6" id="id51"><tt class="docutils literal">debian/README.source</tt></a></li>
+<li><a class="reference internal" href="#id7" id="id52"><tt class="docutils literal">debian/README.test</tt></a></li>
+<li><a class="reference internal" href="#id8" id="id53"><tt class="docutils literal">debian/source/format</tt></a></li>
+<li><a class="reference internal" href="#debian-source-options" id="id54"><tt class="docutils literal">debian/source/options</tt></a></li>
+<li><a class="reference internal" href="#id9" id="id55"><tt class="docutils literal"><span class="pre">debian/gitlab-ci.yml</span></tt></a></li>
+<li><a class="reference internal" href="#debhelper" id="id56">Debhelper</a></li>
+<li><a class="reference internal" href="#version-control-systems" id="id57">Version control systems</a><ul>
+<li><a class="reference internal" href="#source-package-stored-in-a-git-repository-on-salsa" id="id58">Source package stored in a Git repository on Salsa</a></li>
+<li><a class="reference internal" href="#tags" id="id59">Tags</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#new-package" id="id58">New package</a></li>
-<li><a class="reference internal" href="#the-debian-med-blend-tasks" id="id59">The Debian Med Blend tasks</a></li>
-<li><a class="reference internal" href="#building-and-tagging-the-packages" id="id60">Building and tagging the packages</a></li>
-<li><a class="reference internal" href="#handling-patches" id="id61">Handling patches</a><ul>
-<li><a class="reference internal" href="#using-quilt" id="id62">Using <tt class="docutils literal">quilt</tt></a><ul>
-<li><a class="reference internal" href="#creating-a-patch" id="id63">Creating a patch</a></li>
-<li><a class="reference internal" href="#applying-and-unapplying-patches" id="id64">Applying and unapplying patches</a></li>
-<li><a class="reference internal" href="#editing-patches" id="id65">Editing patches</a></li>
-<li><a class="reference internal" href="#renaming-patches" id="id66">Renaming patches</a></li>
-<li><a class="reference internal" href="#other-commands" id="id67">Other commands</a></li>
+<li><a class="reference internal" href="#new-package" id="id60">New package</a></li>
+<li><a class="reference internal" href="#the-debian-med-blend-tasks" id="id61">The Debian Med Blend tasks</a></li>
+<li><a class="reference internal" href="#building-and-tagging-the-packages" id="id62">Building and tagging the packages</a></li>
+<li><a class="reference internal" href="#handling-patches" id="id63">Handling patches</a><ul>
+<li><a class="reference internal" href="#using-quilt" id="id64">Using <tt class="docutils literal">quilt</tt></a><ul>
+<li><a class="reference internal" href="#creating-a-patch" id="id65">Creating a patch</a></li>
+<li><a class="reference internal" href="#applying-and-unapplying-patches" id="id66">Applying and unapplying patches</a></li>
+<li><a class="reference internal" href="#editing-patches" id="id67">Editing patches</a></li>
+<li><a class="reference internal" href="#renaming-patches" id="id68">Renaming patches</a></li>
+<li><a class="reference internal" href="#other-commands" id="id69">Other commands</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
-<li><a class="reference internal" href="#faq" id="id68">FAQ</a><ul>
-<li><a class="reference internal" href="#what-to-do-if-a-large-package-does-not-build-on-a-specific-autobuilder-architecture" id="id69">What to do if a large package does not build on a specific autobuilder architecture?</a></li>
+<li><a class="reference internal" href="#faq" id="id70">FAQ</a><ul>
+<li><a class="reference internal" href="#what-to-do-if-a-large-package-does-not-build-on-a-specific-autobuilder-architecture" id="id71">What to do if a large package does not build on a specific autobuilder architecture?</a></li>
</ul>
</li>
</ul>
</div>
<div class="section" id="introduction">
-<h1><a class="toc-backref" href="#id9">Introduction</a></h1>
+<h1><a class="toc-backref" href="#id10">Introduction</a></h1>
<p>Debian Med is a “<a class="reference external" href="https://blends.debian.org/blends">Debian Pure
Blend</a>” with the aim to develop
Debian into an operating system that is particularly well tailored for
@@ -466,7 +467,7 @@ is not a competition to these efforts but a platform to present the
packages to the community as a Debian Pure Blend.</p>
</div>
<div class="section" id="how-to-contribute">
-<span id="contribute"></span><h1><a class="toc-backref" href="#id10">How to Contribute</a></h1>
+<span id="contribute"></span><h1><a class="toc-backref" href="#id11">How to Contribute</a></h1>
<p>From the developer to the user, there is a long chain of tasks in which
we always welcome participation. First we must keep ourselves informed
about the software landscape in biology and medicine. Software to be
@@ -491,7 +492,7 @@ tutorials that guide Debian users towards the use of packages to their
immediate benefit. You may also consider to write respective articles
for Magazines, be they online or in print.</p>
<div class="section" id="membership">
-<h2><a class="toc-backref" href="#id11">Membership</a></h2>
+<h2><a class="toc-backref" href="#id12">Membership</a></h2>
<p>To request membership to this group, please go on our <a class="reference external" href="https://salsa.debian.org/med-team/">page on
Salsa</a>, or directly follow this
<a class="reference external" href="https://salsa.debian.org/groups/med-team/-/group_members/request_access">link</a>.
@@ -501,7 +502,7 @@ requesting membership (see
on Salsa.debian.org).</p>
</div>
<div class="section" id="essential-readings">
-<span id="readings"></span><h2><a class="toc-backref" href="#id12">Essential readings</a></h2>
+<span id="readings"></span><h2><a class="toc-backref" href="#id13">Essential readings</a></h2>
<ul class="simple">
<li>The <a class="reference external" href="https://www.debian.org/doc/debian-policy/">Debian Policy</a>:
packages must conform to it.</li>
@@ -517,7 +518,7 @@ document): explains how the work is organised in our team.</li>
</ul>
</div>
<div class="section" id="contributing-to-this-policy">
-<span id="meta"></span><h2><a class="toc-backref" href="#id13">Contributing to this Policy</a></h2>
+<span id="meta"></span><h2><a class="toc-backref" href="#id14">Contributing to this Policy</a></h2>
<p>This policy is itself maintained in Git and all team members have write
access to its repository.</p>
<pre class="literal-block">
@@ -529,12 +530,12 @@ make publish
</div>
</div>
<div class="section" id="repositories">
-<h1><a class="toc-backref" href="#id14">Repositories</a></h1>
+<h1><a class="toc-backref" href="#id15">Repositories</a></h1>
<p>We use Git repositories, hosted by Debian. You can have a look at each
repository through <a class="reference external" href="https://salsa.debian.org/groups/med-team/">Salsa's web
interfaces</a>.</p>
<div class="section" id="give-me-the-source">
-<span id="source"></span><h2><a class="toc-backref" href="#id15">Give me the source!</a></h2>
+<span id="source"></span><h2><a class="toc-backref" href="#id16">Give me the source!</a></h2>
<p>To check the sources of a package (referred as <em><package></em> below) in our
repositories, use the <tt class="docutils literal">debcheckout</tt> command, from the
<a class="reference external" href="https://packages.debian.org/devscripts">devscripts</a> package.</p>
@@ -567,9 +568,9 @@ gbp clone https://salsa.debian.org/med-team/<package>.git
</ul>
</div>
<div class="section" id="common-git-repository-structures">
-<span id="git-repository-structures"></span><h2><a class="toc-backref" href="#id16">Common Git repository structures</a></h2>
+<span id="git-repository-structures"></span><h2><a class="toc-backref" href="#id17">Common Git repository structures</a></h2>
<div class="section" id="gbp-buildpackage">
-<span id="git-buildpackage"></span><h3><a class="toc-backref" href="#id17"><tt class="docutils literal">gbp buildpackage</tt></a></h3>
+<span id="git-buildpackage"></span><h3><a class="toc-backref" href="#id18"><tt class="docutils literal">gbp buildpackage</tt></a></h3>
<p>Most of our packages using Git and stored on Salsa are managed following
the standard layout of the <tt class="docutils literal">gbp buildpackage</tt> helper. The <tt class="docutils literal">master</tt>
branch contains the full source package. The <tt class="docutils literal">upstream</tt> branch
@@ -582,7 +583,7 @@ upstream releases are tagged with names like
<tt class="docutils literal">upstream/upstreamversion</tt>.</p>
</div>
<div class="section" id="social-git">
-<span id="git-without-tarball"></span><h3><a class="toc-backref" href="#id18">Social Git</a></h3>
+<span id="git-without-tarball"></span><h3><a class="toc-backref" href="#id19">Social Git</a></h3>
<p>For some projects, like the ones hosted on
<a class="reference external" href="https://www.github.com">GitHub</a> or
<a class="reference external" href="https://www.gitlab.com">GitLab</a>, it may be easier to forward changes
@@ -597,20 +598,20 @@ URL</a> with the <tt class="docutils literal"><span class="pre">-b</span></tt> o
the repository.</p>
</div>
<div class="section" id="other-branches">
-<span id="git-branches"></span><h3><a class="toc-backref" href="#id19">Other branches</a></h3>
+<span id="git-branches"></span><h3><a class="toc-backref" href="#id20">Other branches</a></h3>
<p>Changes uploaded to other distributions than <tt class="docutils literal">unstable</tt> can be stored
in other branches, named for instance <tt class="docutils literal">experimental</tt>, <tt class="docutils literal">stable</tt>, etc.</p>
</div>
</div>
<div class="section" id="git-tips">
-<h2><a class="toc-backref" href="#id20">Git tips</a></h2>
+<h2><a class="toc-backref" href="#id21">Git tips</a></h2>
<div class="section" id="set-the-devscripts-variables-debemail-and-debfullname">
-<span id="git-options-devscripts"></span><h3><a class="toc-backref" href="#id21">Set the devscripts variables <tt class="docutils literal">DEBEMAIL</tt> and <tt class="docutils literal">DEBFULLNAME</tt></a></h3>
+<span id="git-options-devscripts"></span><h3><a class="toc-backref" href="#id22">Set the devscripts variables <tt class="docutils literal">DEBEMAIL</tt> and <tt class="docutils literal">DEBFULLNAME</tt></a></h3>
<p><tt class="docutils literal">debcheckout</tt> will then set <tt class="docutils literal">git</tt>'s options <tt class="docutils literal">user.email</tt> and
<tt class="docutils literal">user.name</tt> accordingly.</p>
</div>
<div class="section" id="configure-git-to-commit-using-your-packager-name-and-address">
-<span id="debcheckout-sets-git-options"></span><h3><a class="toc-backref" href="#id22">Configure Git to commit using your packager name and address.</a></h3>
+<span id="debcheckout-sets-git-options"></span><h3><a class="toc-backref" href="#id23">Configure Git to commit using your packager name and address.</a></h3>
<p>The <tt class="docutils literal"><span class="pre">--global</span></tt> option is to say Git these are the default parameters
for every Git repository you commit to, without it the settings will be
per-repository only:</p>
@@ -620,7 +621,7 @@ git config --global user.email "$DEBEMAIL"
</pre>
</div>
<div class="section" id="to-create-a-new-local-git-repository">
-<span id="new-repository-with-gbp"></span><h3><a class="toc-backref" href="#id23">To create a new local git repository</a></h3>
+<span id="new-repository-with-gbp"></span><h3><a class="toc-backref" href="#id24">To create a new local git repository</a></h3>
<p>Before you create a new git repository you probably want to check
whether your target project just exists. In the Gitlab interface of
<a class="reference external" href="https://salsa.debian.org/med-team/">Salsa</a> you can seek for software
@@ -650,14 +651,14 @@ upstream
.. _debcheckout-git-track:</p>
</div>
<div class="section" id="to-clone-and-follow-every-branch-of-a-git-repository">
-<h3><a class="toc-backref" href="#id24">To clone and follow every branch of a git repository.</a></h3>
+<h3><a class="toc-backref" href="#id25">To clone and follow every branch of a git repository.</a></h3>
<p>When the package is already in the Debian archive, you can use the
<tt class="docutils literal">debcheckout</tt> command with its <tt class="docutils literal"><span class="pre">--git-track='*'</span></tt> option.</p>
<p>To update the <tt class="docutils literal">upstream</tt>, <tt class="docutils literal">master</tt> and <tt class="docutils literal"><span class="pre">pristine-tar</span></tt> branches at
once, use the <tt class="docutils literal">gbp pull</tt>.</p>
</div>
<div class="section" id="to-track-extra-upstream-branches-simply-check-them-out">
-<span id="git-track-new-branches"></span><h3><a class="toc-backref" href="#id25">To track extra upstream branches, simply check them out.</a></h3>
+<span id="git-track-new-branches"></span><h3><a class="toc-backref" href="#id26">To track extra upstream branches, simply check them out.</a></h3>
<p>With recent versions of git, the remote branch will be automatically
tracked when running <tt class="docutils literal">git</tt> checkout. For example, when a
<tt class="docutils literal"><span class="pre">pristine-tar</span></tt> branch is available upstream and not yet tracked
@@ -665,7 +666,7 @@ locally, the command <tt class="docutils literal">git checkout</tt> <tt class="d
run the command <tt class="docutils literal">git branch</tt> <tt class="docutils literal"><span class="pre">-t</span> <span class="pre">pristine-tar</span> <span class="pre">origin/pristine-tar</span></tt>.</p>
</div>
<div class="section" id="to-create-a-pristine-tar-branch-when-it-is-missing">
-<span id="git-missing-pristine-tar"></span><h3><a class="toc-backref" href="#id26">To create a pristine-tar branch when it is missing.</a></h3>
+<span id="git-missing-pristine-tar"></span><h3><a class="toc-backref" href="#id27">To create a pristine-tar branch when it is missing.</a></h3>
<p>See the <a class="reference external" href="https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html">documentation of
git-buildpackage</a>
for details. Use a similar command for any other missing branch.</p>
@@ -677,7 +678,7 @@ git checkout -f master
</pre>
</div>
<div class="section" id="creating-a-new-repository-on-salsa">
-<span id="create-git-repository-on-salsa"></span><h3><a class="toc-backref" href="#id27">Creating a new repository on Salsa</a></h3>
+<span id="create-git-repository-on-salsa"></span><h3><a class="toc-backref" href="#id28">Creating a new repository on Salsa</a></h3>
<p>Before pushing to salsa.debian.org for the first time, an empty
repository needs to be created there in the Gitlab interface.</p>
<p>Each package is kept in its own Git repository. Now, on your local
@@ -687,7 +688,7 @@ git remote add origin git@salsa.debian.org:med-team/<pkg>.git
</pre>
</div>
<div class="section" id="to-change-the-default-branch">
-<span id="git-change-default-branch"></span><h3><a class="toc-backref" href="#id28">To change the default branch.</a></h3>
+<span id="git-change-default-branch"></span><h3><a class="toc-backref" href="#id29">To change the default branch.</a></h3>
<p>If the Debian work is not on the <tt class="docutils literal">master</tt> branch, change the default
branch by editing the <tt class="docutils literal">HEAD</tt> file in the bare repository on Salsa, and
replace <tt class="docutils literal">master</tt> by the name of the new default branch. For a branch
@@ -695,7 +696,7 @@ called <tt class="docutils literal">debian/unstable</tt> the contents of the fil
<tt class="docutils literal">refs/heads/debian/unstable</tt>.</p>
</div>
<div class="section" id="to-push-the-package">
-<span id="push-package-to-salsa"></span><h3><a class="toc-backref" href="#id29">To push the package.</a></h3>
+<span id="push-package-to-salsa"></span><h3><a class="toc-backref" href="#id30">To push the package.</a></h3>
<p>(make sure you've added the salsa remote!), do the following:
<tt class="docutils literal">git push origin master</tt>. For the first push, it's necessary to specify
<tt class="docutils literal">origin master</tt>. The next time you will push, a <tt class="docutils literal">git push</tt> will
@@ -706,7 +707,7 @@ git push --set-upstream
</pre>
</div>
<div class="section" id="to-push-all-your-work">
-<span id="git-push-all-tags"></span><h3><a class="toc-backref" href="#id30">To push all your work</a></h3>
+<span id="git-push-all-tags"></span><h3><a class="toc-backref" href="#id31">To push all your work</a></h3>
<p>Be sure to also do a run <tt class="docutils literal">git push</tt> with <tt class="docutils literal"><span class="pre">--all</span></tt>, and one with
<tt class="docutils literal"><span class="pre">--tags</span></tt> if you created new tags.</p>
<pre class="literal-block">
@@ -715,12 +716,12 @@ git push --tags
</pre>
</div>
<div class="section" id="to-tag-a-release">
-<span id="git-tag-release"></span><h3><a class="toc-backref" href="#id31">To tag a release</a></h3>
+<span id="git-tag-release"></span><h3><a class="toc-backref" href="#id32">To tag a release</a></h3>
<p><tt class="docutils literal">git tag <span class="pre">debian/x.y-z</span></tt>. You can also easily retroactively make tags:
<tt class="docutils literal">git tag <span class="pre">debian/x.y-z</span> <commit hash></tt>. Remember to <tt class="docutils literal">git push <span class="pre">--tags</span></tt>.</p>
</div>
<div class="section" id="if-upstream-manages-his-sources-with-git">
-<span id="git-debian-version-from-commit"></span><h3><a class="toc-backref" href="#id32">If upstream manages his sources with Git.</a></h3>
+<span id="git-debian-version-from-commit"></span><h3><a class="toc-backref" href="#id33">If upstream manages his sources with Git.</a></h3>
<p>The following makefile script can help producing a version number when
no Git tag is available:</p>
<pre class="literal-block">
@@ -737,7 +738,7 @@ get-orig-source:
</pre>
</div>
<div class="section" id="to-make-gbp-buildpackage-build-the-package-with-pdebuild">
-<span id="git-pbuilder"></span><h3><a class="toc-backref" href="#id33">To make <tt class="docutils literal">gbp buildpackage</tt> build the package with <tt class="docutils literal">pdebuild</tt>.</a></h3>
+<span id="git-pbuilder"></span><h3><a class="toc-backref" href="#id34">To make <tt class="docutils literal">gbp buildpackage</tt> build the package with <tt class="docutils literal">pdebuild</tt>.</a></h3>
<p>Add the following to the configuration file <tt class="docutils literal"><span class="pre">~/.gbp.conf</span></tt> or
<tt class="docutils literal">debian/gbp.conf</tt>:</p>
<pre class="literal-block">
@@ -745,6 +746,7 @@ get-orig-source:
builder = ~/bin/git-pbuilder
pristine-tar = True
+pbuilder-options=--source-only-changes
</pre>
<p>With this configuration file you're specifying that <tt class="docutils literal">gbp buildpackage</tt>
will use <tt class="docutils literal"><span class="pre">~/bin/git-pbuilder</span></tt> as the builder script. This is an
@@ -758,10 +760,19 @@ rm ../*_source.changes
</pre>
<p>This will build the package inside the default cowbuilder chroot, while
passing any more parameters directly do <tt class="docutils literal"><span class="pre">dpkg-buildpackage</span></tt>.</p>
+<p>Other options in <tt class="docutils literal"><span class="pre">~/.gbp.conf</span></tt>:</p>
+<ul class="simple">
+<li><tt class="docutils literal"><span class="pre">pristine-tar</span> = True</tt>: specifies that we are using
+the pristine-tar branch to store the necessary information about the
+original source tarball in pristine-tar</li>
+<li><tt class="docutils literal"><span class="pre">pbuilder-options=--source-only-changes</span></tt>: Creates a source changes
+file to do source only uploads. That's extremely important since
+for Debian 11 only source uploads are allowed.</li>
+</ul>
</div>
</div>
<div class="section" id="updating-a-source-package-managed-with-git">
-<span id="updating-git-package"></span><h2><a class="toc-backref" href="#id34">Updating a source package managed with Git</a></h2>
+<span id="updating-git-package"></span><h2><a class="toc-backref" href="#id35">Updating a source package managed with Git</a></h2>
<p>Most source packages maintained as Git repositories in Debian Med are
using the <tt class="docutils literal">gbp buildpackage</tt> helper toolkit. In doubt, try this one
first.</p>
@@ -792,9 +803,9 @@ default is 500…</p>
</div>
</div>
<div class="section" id="packaging">
-<h1><a class="toc-backref" href="#id35">Packaging</a></h1>
+<h1><a class="toc-backref" href="#id36">Packaging</a></h1>
<div class="section" id="newcomer-guidelines-for-building-proper-debian-packages">
-<span id="packagingguidelines"></span><h2><a class="toc-backref" href="#id36">Newcomer guidelines for building proper Debian packages</a></h2>
+<span id="packagingguidelines"></span><h2><a class="toc-backref" href="#id37">Newcomer guidelines for building proper Debian packages</a></h2>
<p>Some newcomers tend to go the create DEBIAN dir, move files around and
`dpkg-deb -b` way to create Debian packages. Short answer: Forget
about this. The only way to the official Debian mirror leads via proper
@@ -809,7 +820,7 @@ Month</a> as student to get a
personal training how to start working inside the Debian Med team.</p>
</div>
<div class="section" id="announcing-intent-to-package">
-<span id="itp"></span><h2><a class="toc-backref" href="#id37">Announcing intent to package</a></h2>
+<span id="itp"></span><h2><a class="toc-backref" href="#id38">Announcing intent to package</a></h2>
<p>If you intent to work on a Debian package you should follow the <a class="reference external" href="https://www.debian.org/devel/wnpp/#l1">normal
Debian rules</a> and file a WNPP
bug report.</p>
@@ -822,7 +833,7 @@ we notice if for some reason the package has not been uploaded.</p>
best, and document your ITP number using the <tt class="docutils literal">WNPP</tt> field name.</p>
</div>
<div class="section" id="backports">
-<h2><a class="toc-backref" href="#id38">Backports</a></h2>
+<h2><a class="toc-backref" href="#id39">Backports</a></h2>
<p>Debian offers <a class="reference external" href="https://backports.debian.org">backports</a> to provide
up-to-date software for users of the official stable releases. Backports
of Debian Med packages should be kept as branches in our
@@ -858,7 +869,7 @@ dch --bpo
<p>Now, you can try building against a Stable chroot.</p>
</div>
<div class="section" id="ppa-for-ubuntu">
-<span id="ppa"></span><h2><a class="toc-backref" href="#id39">PPA for Ubuntu</a></h2>
+<span id="ppa"></span><h2><a class="toc-backref" href="#id40">PPA for Ubuntu</a></h2>
<p>Debian Med operates a <a class="reference external" href="https://launchpad.net/~debian-med/+archive/ppa">Personal Package
Archive</a> (PPA) on
Launchpad, where packages are backported for Ubuntu. There is currently
@@ -883,11 +894,11 @@ for versioning packages in PPA.</p>
follows: <tt class="docutils literal">LINTIAN_PROFILE=ubuntu</tt>.</p>
</div>
<div class="section" id="debian-unstable-chroot-on-ubuntu">
-<span id="sidonubuntu"></span><h2><a class="toc-backref" href="#id40">Debian unstable chroot on Ubuntu</a></h2>
+<span id="sidonubuntu"></span><h2><a class="toc-backref" href="#id41">Debian unstable chroot on Ubuntu</a></h2>
<p>cowbuilder-dist sid create cowbuilder-dist sid login</p>
</div>
<div class="section" id="derivatives-working-together-with-debian-med">
-<span id="derivatives"></span><h2><a class="toc-backref" href="#id41">Derivatives working together with Debian Med</a></h2>
+<span id="derivatives"></span><h2><a class="toc-backref" href="#id42">Derivatives working together with Debian Med</a></h2>
<p>Debian Med is proud that derivatives (like for instance
<a class="reference external" href="http://environmentalomics.org/bio-linux/">Bio-Linux</a>) are profiting
from our work inside Debian and we try to establish strong connections
@@ -902,7 +913,7 @@ it should get the version
the versioning scheme usually used by Ubuntu).</p>
</div>
<div class="section" id="r-packages">
-<h2><a class="toc-backref" href="#id42">R packages</a></h2>
+<h2><a class="toc-backref" href="#id43">R packages</a></h2>
<p>Debian R packages should be maintained within the <a class="reference external" href="https://wiki.debian.org/Teams/r-pkg-team">Debian R Packages
Team</a>.</p>
<p><a class="reference external" href="https://packages.debian.org/r-base-core">GNU R</a> sometimes introduces
@@ -914,7 +925,7 @@ binary package.</p>
</div>
</div>
<div class="section" id="tasks">
-<h1><a class="toc-backref" href="#id43">Tasks</a></h1>
+<h1><a class="toc-backref" href="#id44">Tasks</a></h1>
<p>The Debian Med <a class="reference external" href="https://blends.debian.org/blends">Debian Pure Blend</a>
is organised by <a class="reference external" href="https://blends.debian.org/med/tasks">tasks</a>, that
group packages around broad themes such as <a class="reference external" href="https://blends.debian.org/med/tasks/imaging">medical
@@ -931,9 +942,9 @@ and described in the <a class="reference external" href="https://blends.debian.o
website</a>.</p>
</div>
<div class="section" id="policy">
-<h1><a class="toc-backref" href="#id44">Policy</a></h1>
+<h1><a class="toc-backref" href="#id45">Policy</a></h1>
<div class="section" id="id1">
-<span id="debian-control"></span><h2><a class="toc-backref" href="#id45"><tt class="docutils literal">debian/control</tt></a></h2>
+<span id="debian-control"></span><h2><a class="toc-backref" href="#id46"><tt class="docutils literal">debian/control</tt></a></h2>
<ol class="arabic">
<li><p class="first"><strong>Section.</strong></p>
<p>Should be “science” for the source package.</p>
@@ -998,7 +1009,7 @@ you want to use the cme GUI you also need to</p>
<p><tt class="docutils literal">cme</tt> <tt class="docutils literal">edit dpkg</tt></p>
</div>
<div class="section" id="id2">
-<span id="debian-copyright"></span><h2><a class="toc-backref" href="#id46"><tt class="docutils literal">debian/copyright</tt></a></h2>
+<span id="debian-copyright"></span><h2><a class="toc-backref" href="#id47"><tt class="docutils literal">debian/copyright</tt></a></h2>
<p>We use the <a class="reference external" href="https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/">machine-readable
format</a>
for the <tt class="docutils literal">debian/copyright</tt> file. The <tt class="docutils literal">Source</tt> field does not need to
@@ -1029,7 +1040,7 @@ cme check|fix|edit dpkg-copyright
<p>from package <tt class="docutils literal"><span class="pre">libconfig-model-dpkg-perl</span></tt> (see above).</p>
</div>
<div class="section" id="id3">
-<span id="debian-changelog"></span><h2><a class="toc-backref" href="#id47"><tt class="docutils literal">debian/changelog</tt></a></h2>
+<span id="debian-changelog"></span><h2><a class="toc-backref" href="#id48"><tt class="docutils literal">debian/changelog</tt></a></h2>
<p>Packages hosted in our Git repository, that have been modified but not
uploaded must use <tt class="docutils literal">UNRELEASED</tt> as a distribution name. This can be
done automatically by declaring
@@ -1037,7 +1048,7 @@ done automatically by declaring
<tt class="docutils literal">dch</tt>.</p>
</div>
<div class="section" id="id4">
-<span id="debian-upstream"></span><h2><a class="toc-backref" href="#id48"><tt class="docutils literal">debian/upstream</tt></a></h2>
+<span id="debian-upstream"></span><h2><a class="toc-backref" href="#id49"><tt class="docutils literal">debian/upstream</tt></a></h2>
<p>We use the <a class="reference external" href="https://wiki.debian.org/UpstreamMetadata#Fields">bibliographic
information</a> which
should be stored in the file <tt class="docutils literal">debian/upstream</tt>. The purpose of
@@ -1050,7 +1061,7 @@ RRID, bio.tools, OMICtools). The metadata allows for references to
publications and entries in these registries alike.</p>
</div>
<div class="section" id="id5">
-<span id="debian-gbp-conf"></span><h2><a class="toc-backref" href="#id49"><tt class="docutils literal">debian/gbp.conf</tt></a></h2>
+<span id="debian-gbp-conf"></span><h2><a class="toc-backref" href="#id50"><tt class="docutils literal">debian/gbp.conf</tt></a></h2>
<p>Include this file to document the layout of the repository. Packages
managed with <tt class="docutils literal">gbp buildpackage</tt> may omit default values.</p>
<pre class="literal-block">
@@ -1069,7 +1080,7 @@ pristine-tar = True
</pre>
</div>
<div class="section" id="id6">
-<span id="debian-readme-source"></span><h2><a class="toc-backref" href="#id50"><tt class="docutils literal">debian/README.source</tt></a></h2>
+<span id="debian-readme-source"></span><h2><a class="toc-backref" href="#id51"><tt class="docutils literal">debian/README.source</tt></a></h2>
<p>This file is recommended by the Policy
(<a class="reference external" href="https://www.debian.org/doc/debian-policy/#source-package-handling-debian-readme-source">§ 4.14</a>)
from version 3.8.0 for documenting source package handling. Please
@@ -1078,20 +1089,20 @@ a patch system, when the upstream sources are in another format than
gzipped tar archive, when we repack the sources,…</p>
</div>
<div class="section" id="id7">
-<span id="debian-readme-test"></span><h2><a class="toc-backref" href="#id51"><tt class="docutils literal">debian/README.test</tt></a></h2>
+<span id="debian-readme-test"></span><h2><a class="toc-backref" href="#id52"><tt class="docutils literal">debian/README.test</tt></a></h2>
<p>This file was (<a class="reference external" href="https://lists.debian.org/debian-devel-announce/2011/01/msg00006.html">recommended by the Security
team</a>)
for describing to others than the regular maintainer how the package's
functionality can properly be tested.</p>
</div>
<div class="section" id="id8">
-<span id="debian-source-format"></span><h2><a class="toc-backref" href="#id52"><tt class="docutils literal">debian/source/format</tt></a></h2>
+<span id="debian-source-format"></span><h2><a class="toc-backref" href="#id53"><tt class="docutils literal">debian/source/format</tt></a></h2>
<p>This file sould contain “<tt class="docutils literal">3.0 (quilt)</tt>” in order to use this source
format. Other formats should be avoided unless they bring a specific
advantage.</p>
</div>
<div class="section" id="debian-source-options">
-<span id="debian-source-option"></span><h2><a class="toc-backref" href="#id53"><tt class="docutils literal">debian/source/options</tt></a></h2>
+<span id="debian-source-option"></span><h2><a class="toc-backref" href="#id54"><tt class="docutils literal">debian/source/options</tt></a></h2>
<p>For packages not using <a class="reference external" href="#quilt">quilt</a> patches, for example when
committing changes directly to the Debian branch, this file should
contain “<tt class="docutils literal"><span class="pre">single-debian-patch</span></tt>” in order to emulate the <tt class="docutils literal">1.0</tt>
@@ -1099,8 +1110,17 @@ format. This is better than using the <tt class="docutils literal">1.0</tt> form
the <tt class="docutils literal">3.0 (quilt)</tt> format brings other advantages, in particular
the conservation of file permissions in the <tt class="docutils literal">debian</tt> directory.</p>
</div>
+<div class="section" id="id9">
+<span id="debian-gitlab-ci-yml"></span><h2><a class="toc-backref" href="#id55"><tt class="docutils literal"><span class="pre">debian/gitlab-ci.yml</span></tt></a></h2>
+<p>To run continuous integration tests at each push in our Salsa forge, the Salsa
+CI team provides a pipeline that can be activated by including
+some template files available from their <a class="reference external" href="https://salsa.debian.org/salsa-ci-team/pipeline">repository</a>. The simplest and
+recommended way is to put the include statements in a <tt class="docutils literal"><span class="pre">debian/gitlab-ci.yml</span></tt>
+file, and configure the repository to recognise that file, as documented
+in the <tt class="docutils literal"><span class="pre">`salsa-ci-team/pipeline</span></tt> repository's <a class="reference external" href="https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md">README</a> file.</p>
+</div>
<div class="section" id="debhelper">
-<h2><a class="toc-backref" href="#id54">Debhelper</a></h2>
+<h2><a class="toc-backref" href="#id56">Debhelper</a></h2>
<p>Debhelper uses compatibility levels to control the behaviour of its
commands. We currently recommend to use the level <em>10</em> which is
available in current <em>Stable</em> and backported to <em>Oldstable</em>. However,
@@ -1112,26 +1132,26 @@ easy to understand the packaging for other members of the team. Even
complex packaging becomes quite transparent this way.</p>
</div>
<div class="section" id="version-control-systems">
-<span id="vcs"></span><h2><a class="toc-backref" href="#id55">Version control systems</a></h2>
+<span id="vcs"></span><h2><a class="toc-backref" href="#id57">Version control systems</a></h2>
<div class="section" id="source-package-stored-in-a-git-repository-on-salsa">
-<span id="vcs-git"></span><h3><a class="toc-backref" href="#id56">Source package stored in a Git repository on Salsa</a></h3>
+<span id="vcs-git"></span><h3><a class="toc-backref" href="#id58">Source package stored in a Git repository on Salsa</a></h3>
<p>Git repositories should be stored on
<a class="reference external" href="https://salsa.debian.org/med-team/">Salsa</a>.</p>
</div>
<div class="section" id="tags">
-<span id="vcs-tags"></span><h3><a class="toc-backref" href="#id57">Tags</a></h3>
+<span id="vcs-tags"></span><h3><a class="toc-backref" href="#id59">Tags</a></h3>
<p>Tags indicate the revision corresponding to uploaded packages. For a
released package <tt class="docutils literal">debian/</tt> is added before the package version number.</p>
</div>
</div>
<div class="section" id="new-package">
-<h2><a class="toc-backref" href="#id58">New package</a></h2>
+<h2><a class="toc-backref" href="#id60">New package</a></h2>
<p>Try to inject a new package only after successfully building it with
<tt class="docutils literal"><span class="pre">dpkg-buildpackage</span></tt> (or any wrapper around it). Use a file like
<tt class="docutils literal">debian/DRAFT</tt> to mention when the package is a draft.</p>
</div>
<div class="section" id="the-debian-med-blend-tasks">
-<span id="new-packages-in-tasks"></span><h2><a class="toc-backref" href="#id59">The Debian Med Blend tasks</a></h2>
+<span id="new-packages-in-tasks"></span><h2><a class="toc-backref" href="#id61">The Debian Med Blend tasks</a></h2>
<p>Once you injected a new package please make sure that it is mentioned in
the appropriate <a class="reference external" href="#tasks">tasks</a> file in the Git source of the
debian-med Blend package. Some team members watch the changes in the
@@ -1139,13 +1159,13 @@ Debian Med packaging pool but it helps if the maintainer of a new
package verifies that everything is in the right place.</p>
</div>
<div class="section" id="building-and-tagging-the-packages">
-<span id="building-and-tagging"></span><h2><a class="toc-backref" href="#id60">Building and tagging the packages</a></h2>
+<span id="building-and-tagging"></span><h2><a class="toc-backref" href="#id62">Building and tagging the packages</a></h2>
<p>We prefer that uploaded packages are built in a chroot, to provide
similar build environment to the whole team. After upload, please
<a class="reference external" href="#vcs-tags">tag</a> the <a class="reference external" href="#git-tag-release">Git</a> repository.</p>
</div>
<div class="section" id="handling-patches">
-<span id="patches"></span><h2><a class="toc-backref" href="#id61">Handling patches</a></h2>
+<span id="patches"></span><h2><a class="toc-backref" href="#id63">Handling patches</a></h2>
<p>Often happens that the upstream code doesn't fit well into the Debian
distribution: be this wrong paths, missing features, anything that
implies editing the source files. When you directly edit upstream's
@@ -1157,7 +1177,7 @@ the <tt class="docutils literal">debian/patches</tt> directory.</p>
<p>The <tt class="docutils literal">3.0 (quilt)</tt> Dpkg source format provides its own patch system.
You can use it with the <tt class="docutils literal">quilt</tt> command.</p>
<div class="section" id="using-quilt">
-<span id="quilt"></span><h3><a class="toc-backref" href="#id62">Using <tt class="docutils literal">quilt</tt></a></h3>
+<span id="quilt"></span><h3><a class="toc-backref" href="#id64">Using <tt class="docutils literal">quilt</tt></a></h3>
<p>Using quilt is rather easy.</p>
<p>First, make sure you have correctly setup quilt: open <tt class="docutils literal">.quiltrc</tt> in
your home directory (create it if you don't have one), and make sure it
@@ -1173,7 +1193,7 @@ QUILT_PATCHES="debian/patches"
instructions in the <a class="reference external" href="https://www.debian.org/doc/manuals/maint-guide/modify.en.html#quiltrc">New Maintainer's
Guide</a>.</p>
<div class="section" id="creating-a-patch">
-<span id="quilt-create"></span><h4><a class="toc-backref" href="#id63">Creating a patch</a></h4>
+<span id="quilt-create"></span><h4><a class="toc-backref" href="#id65">Creating a patch</a></h4>
<p>To create a patch, use the <tt class="docutils literal">new</tt> command. Run:</p>
<blockquote>
<tt class="docutils literal">quilt new <span class="pre"><patch_name>.patch</span></tt></blockquote>
@@ -1196,7 +1216,7 @@ format</a>:</p>
<tt class="docutils literal">quilt header <span class="pre">-e</span> <span class="pre">--dep3</span></tt></blockquote>
</div>
<div class="section" id="applying-and-unapplying-patches">
-<span id="quilt-apply"></span><h4><a class="toc-backref" href="#id64">Applying and unapplying patches</a></h4>
+<span id="quilt-apply"></span><h4><a class="toc-backref" href="#id66">Applying and unapplying patches</a></h4>
<p>Just two easy commands to do the job:</p>
<ul class="simple">
<li><tt class="docutils literal">quilt pop</tt> will unapply the topmost patch.</li>
@@ -1211,7 +1231,7 @@ apply/unapply all patches in the series.</p>
</blockquote>
</div>
<div class="section" id="editing-patches">
-<span id="quilt-edit"></span><h4><a class="toc-backref" href="#id65">Editing patches</a></h4>
+<span id="quilt-edit"></span><h4><a class="toc-backref" href="#id67">Editing patches</a></h4>
<p>To edit a patch, first make it the topmost:</p>
<blockquote>
<tt class="docutils literal">quilt push <patch_name></tt></blockquote>
@@ -1221,22 +1241,22 @@ apply/unapply all patches in the series.</p>
when you're done, <tt class="docutils literal">quilt refresh</tt>.</p>
</div>
<div class="section" id="renaming-patches">
-<span id="quilt-rename"></span><h4><a class="toc-backref" href="#id66">Renaming patches</a></h4>
+<span id="quilt-rename"></span><h4><a class="toc-backref" href="#id68">Renaming patches</a></h4>
<p>Sometimes it's useful to rename a patch. Without any hassle, do:</p>
<blockquote>
<tt class="docutils literal">quilt rename <span class="pre">-P</span> <span class="pre"><old_name>.patch</span> <span class="pre"><new_name>.patch</span></tt></blockquote>
</div>
<div class="section" id="other-commands">
-<span id="quilt-other"></span><h4><a class="toc-backref" href="#id67">Other commands</a></h4>
+<span id="quilt-other"></span><h4><a class="toc-backref" href="#id69">Other commands</a></h4>
<p>Please see <tt class="docutils literal">man 1 quilt</tt> to have a comprehensive list of commands.</p>
</div>
</div>
</div>
</div>
<div class="section" id="faq">
-<h1><a class="toc-backref" href="#id68">FAQ</a></h1>
+<h1><a class="toc-backref" href="#id70">FAQ</a></h1>
<div class="section" id="what-to-do-if-a-large-package-does-not-build-on-a-specific-autobuilder-architecture">
-<span id="autobuilder"></span><h2><a class="toc-backref" href="#id69">What to do if a large package does not build on a specific autobuilder architecture?</a></h2>
+<span id="autobuilder"></span><h2><a class="toc-backref" href="#id71">What to do if a large package does not build on a specific autobuilder architecture?</a></h2>
<p>Some of our target packages are large regarding memory consumption or
requiring more computing power to build on not so powerful
architectures. Since the Debian autobuilder infrastructure consists of
=====================================
policy.rst
=====================================
@@ -392,6 +392,7 @@ Add the following to the configuration file ``~/.gbp.conf`` or
builder = ~/bin/git-pbuilder
pristine-tar = True
+ pbuilder-options=--source-only-changes
With this configuration file you're specifying that ``gbp buildpackage``
will use ``~/bin/git-pbuilder`` as the builder script. This is an
@@ -408,6 +409,16 @@ example script you can use:
This will build the package inside the default cowbuilder chroot, while
passing any more parameters directly do ``dpkg-buildpackage``.
+Other options in ``~/.gbp.conf``:
+
+- ``pristine-tar = True``: specifies that we are using
+ the pristine-tar branch to store the necessary information about the
+ original source tarball in pristine-tar
+
+- ``pbuilder-options=--source-only-changes``: Creates a source changes
+ file to do source only uploads. That's extremely important since
+ for Debian 11 only source uploads are allowed.
+
.. _updating-git-package:
Updating a source package managed with Git
View it on GitLab: https://salsa.debian.org/med-team/policy/commit/7cff1613553bb269221d19ee0edc07e449cccce6
--
View it on GitLab: https://salsa.debian.org/med-team/policy/commit/7cff1613553bb269221d19ee0edc07e449cccce6
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/debian-med-commit/attachments/20190905/04396eb2/attachment-0001.html>
More information about the debian-med-commit
mailing list