[med-svn] [Git][med-team/policy][official-coms] official communication channels and Code of Conduct
Michael R. Crusoe (@crusoe)
gitlab at salsa.debian.org
Sat Apr 6 13:43:33 BST 2024
Michael R. Crusoe pushed to branch official-coms at Debian Med / policy
Commits:
a4534e09 by Michael R. Crusoe at 2024-04-06T14:43:05+02:00
official communication channels and Code of Conduct
- - - - -
2 changed files:
- policy.html
- policy.rst
Changes:
=====================================
policy.html
=====================================
@@ -369,88 +369,89 @@ ul.auto-toc {
<ul class="simple">
<li><a class="reference internal" href="#introduction" id="toc-entry-1">Introduction</a></li>
<li><a class="reference internal" href="#how-to-contribute" id="toc-entry-2">How to Contribute</a><ul>
-<li><a class="reference internal" href="#membership" id="toc-entry-3">Membership</a></li>
-<li><a class="reference internal" href="#essential-readings" id="toc-entry-4">Essential readings</a></li>
-<li><a class="reference internal" href="#contributing-to-this-policy" id="toc-entry-5">Contributing to this Policy</a></li>
+<li><a class="reference internal" href="#communications" id="toc-entry-3">Communications</a></li>
+<li><a class="reference internal" href="#membership" id="toc-entry-4">Membership</a></li>
+<li><a class="reference internal" href="#essential-readings" id="toc-entry-5">Essential readings</a></li>
+<li><a class="reference internal" href="#contributing-to-this-policy" id="toc-entry-6">Contributing to this Policy</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#repositories" id="toc-entry-6">Repositories</a><ul>
-<li><a class="reference internal" href="#give-me-the-source" id="toc-entry-7">Give me the source!</a></li>
-<li><a class="reference internal" href="#common-git-repository-structures" id="toc-entry-8">Common Git repository structures</a><ul>
-<li><a class="reference internal" href="#gbp-buildpackage" id="toc-entry-9"><tt class="docutils literal">gbp buildpackage</tt></a></li>
-<li><a class="reference internal" href="#social-git" id="toc-entry-10">Social Git</a></li>
-<li><a class="reference internal" href="#other-branches" id="toc-entry-11">Other branches</a></li>
+<li><a class="reference internal" href="#repositories" id="toc-entry-7">Repositories</a><ul>
+<li><a class="reference internal" href="#give-me-the-source" id="toc-entry-8">Give me the source!</a></li>
+<li><a class="reference internal" href="#common-git-repository-structures" id="toc-entry-9">Common Git repository structures</a><ul>
+<li><a class="reference internal" href="#gbp-buildpackage" id="toc-entry-10"><tt class="docutils literal">gbp buildpackage</tt></a></li>
+<li><a class="reference internal" href="#social-git" id="toc-entry-11">Social Git</a></li>
+<li><a class="reference internal" href="#other-branches" id="toc-entry-12">Other branches</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#git-tips" id="toc-entry-12">Git tips</a><ul>
-<li><a class="reference internal" href="#set-the-devscripts-variables-debemail-and-debfullname" id="toc-entry-13">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="toc-entry-14">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="toc-entry-15">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="toc-entry-16">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="toc-entry-17">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="toc-entry-18">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="toc-entry-19">Creating a new repository on Salsa</a></li>
-<li><a class="reference internal" href="#to-change-the-default-branch" id="toc-entry-20">To change the default branch.</a></li>
-<li><a class="reference internal" href="#to-push-the-package" id="toc-entry-21">To push the package.</a></li>
-<li><a class="reference internal" href="#to-push-all-your-work" id="toc-entry-22">To push all your work</a></li>
-<li><a class="reference internal" href="#to-tag-a-release" id="toc-entry-23">To tag a release</a></li>
-<li><a class="reference internal" href="#if-upstream-manages-their-sources-with-git" id="toc-entry-24">If upstream manages their sources with Git.</a></li>
-<li><a class="reference internal" href="#to-make-gbp-buildpackage-build-the-package-with-pdebuild" id="toc-entry-25">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="toc-entry-13">Git tips</a><ul>
+<li><a class="reference internal" href="#set-the-devscripts-variables-debemail-and-debfullname" id="toc-entry-14">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="toc-entry-15">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="toc-entry-16">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="toc-entry-17">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="toc-entry-18">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="toc-entry-19">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="toc-entry-20">Creating a new repository on Salsa</a></li>
+<li><a class="reference internal" href="#to-change-the-default-branch" id="toc-entry-21">To change the default branch.</a></li>
+<li><a class="reference internal" href="#to-push-the-package" id="toc-entry-22">To push the package.</a></li>
+<li><a class="reference internal" href="#to-push-all-your-work" id="toc-entry-23">To push all your work</a></li>
+<li><a class="reference internal" href="#to-tag-a-release" id="toc-entry-24">To tag a release</a></li>
+<li><a class="reference internal" href="#if-upstream-manages-their-sources-with-git" id="toc-entry-25">If upstream manages their sources with Git.</a></li>
+<li><a class="reference internal" href="#to-make-gbp-buildpackage-build-the-package-with-pdebuild" id="toc-entry-26">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="toc-entry-26">Updating a source package managed with Git</a></li>
+<li><a class="reference internal" href="#updating-a-source-package-managed-with-git" id="toc-entry-27">Updating a source package managed with Git</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#packaging" id="toc-entry-27">Packaging</a><ul>
-<li><a class="reference internal" href="#newcomer-guidelines-for-building-proper-debian-packages" id="toc-entry-28">Newcomer guidelines for building proper Debian packages</a></li>
-<li><a class="reference internal" href="#announcing-intent-to-package" id="toc-entry-29">Announcing intent to package</a></li>
-<li><a class="reference internal" href="#backports" id="toc-entry-30">Backports</a></li>
-<li><a class="reference internal" href="#ppa-for-ubuntu" id="toc-entry-31">PPA for Ubuntu</a></li>
-<li><a class="reference internal" href="#debian-unstable-chroot-on-ubuntu" id="toc-entry-32">Debian unstable chroot on Ubuntu</a></li>
-<li><a class="reference internal" href="#derivatives-working-together-with-debian-med" id="toc-entry-33">Derivatives working together with Debian Med</a></li>
-<li><a class="reference internal" href="#r-packages" id="toc-entry-34">R packages</a></li>
+<li><a class="reference internal" href="#packaging" id="toc-entry-28">Packaging</a><ul>
+<li><a class="reference internal" href="#newcomer-guidelines-for-building-proper-debian-packages" id="toc-entry-29">Newcomer guidelines for building proper Debian packages</a></li>
+<li><a class="reference internal" href="#announcing-intent-to-package" id="toc-entry-30">Announcing intent to package</a></li>
+<li><a class="reference internal" href="#backports" id="toc-entry-31">Backports</a></li>
+<li><a class="reference internal" href="#ppa-for-ubuntu" id="toc-entry-32">PPA for Ubuntu</a></li>
+<li><a class="reference internal" href="#debian-unstable-chroot-on-ubuntu" id="toc-entry-33">Debian unstable chroot on Ubuntu</a></li>
+<li><a class="reference internal" href="#derivatives-working-together-with-debian-med" id="toc-entry-34">Derivatives working together with Debian Med</a></li>
+<li><a class="reference internal" href="#r-packages" id="toc-entry-35">R packages</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#tasks" id="toc-entry-35">Tasks</a></li>
-<li><a class="reference internal" href="#policy" id="toc-entry-36">Policy</a><ul>
-<li><a class="reference internal" href="#debian-control-1" id="toc-entry-37"><tt class="docutils literal">debian/control</tt></a></li>
-<li><a class="reference internal" href="#debian-copyright-1" id="toc-entry-38"><tt class="docutils literal">debian/copyright</tt></a></li>
-<li><a class="reference internal" href="#debian-changelog-1" id="toc-entry-39"><tt class="docutils literal">debian/changelog</tt></a></li>
-<li><a class="reference internal" href="#debian-upstream-1" id="toc-entry-40"><tt class="docutils literal">debian/upstream</tt></a></li>
-<li><a class="reference internal" href="#debian-gbp-conf-1" id="toc-entry-41"><tt class="docutils literal">debian/gbp.conf</tt></a></li>
-<li><a class="reference internal" href="#debian-readme-source-1" id="toc-entry-42"><tt class="docutils literal">debian/README.source</tt></a></li>
-<li><a class="reference internal" href="#debian-readme-test-1" id="toc-entry-43"><tt class="docutils literal">debian/README.test</tt></a></li>
-<li><a class="reference internal" href="#debian-source-format-1" id="toc-entry-44"><tt class="docutils literal">debian/source/format</tt></a></li>
-<li><a class="reference internal" href="#debian-source-options" id="toc-entry-45"><tt class="docutils literal">debian/source/options</tt></a></li>
-<li><a class="reference internal" href="#debian-salsa-ci-yml-1" id="toc-entry-46"><tt class="docutils literal"><span class="pre">debian/salsa-ci.yml</span></tt></a></li>
-<li><a class="reference internal" href="#debian-symbols" id="toc-entry-47"><tt class="docutils literal">debian/symbols</tt></a></li>
-<li><a class="reference internal" href="#debhelper" id="toc-entry-48">Debhelper</a></li>
-<li><a class="reference internal" href="#version-control-systems" id="toc-entry-49">Version control systems</a><ul>
-<li><a class="reference internal" href="#source-package-stored-in-a-git-repository-on-salsa" id="toc-entry-50">Source package stored in a Git repository on Salsa</a></li>
-<li><a class="reference internal" href="#tags" id="toc-entry-51">Tags</a></li>
+<li><a class="reference internal" href="#tasks" id="toc-entry-36">Tasks</a></li>
+<li><a class="reference internal" href="#policy" id="toc-entry-37">Policy</a><ul>
+<li><a class="reference internal" href="#debian-control-1" id="toc-entry-38"><tt class="docutils literal">debian/control</tt></a></li>
+<li><a class="reference internal" href="#debian-copyright-1" id="toc-entry-39"><tt class="docutils literal">debian/copyright</tt></a></li>
+<li><a class="reference internal" href="#debian-changelog-1" id="toc-entry-40"><tt class="docutils literal">debian/changelog</tt></a></li>
+<li><a class="reference internal" href="#debian-upstream-1" id="toc-entry-41"><tt class="docutils literal">debian/upstream</tt></a></li>
+<li><a class="reference internal" href="#debian-gbp-conf-1" id="toc-entry-42"><tt class="docutils literal">debian/gbp.conf</tt></a></li>
+<li><a class="reference internal" href="#debian-readme-source-1" id="toc-entry-43"><tt class="docutils literal">debian/README.source</tt></a></li>
+<li><a class="reference internal" href="#debian-readme-test-1" id="toc-entry-44"><tt class="docutils literal">debian/README.test</tt></a></li>
+<li><a class="reference internal" href="#debian-source-format-1" id="toc-entry-45"><tt class="docutils literal">debian/source/format</tt></a></li>
+<li><a class="reference internal" href="#debian-source-options" id="toc-entry-46"><tt class="docutils literal">debian/source/options</tt></a></li>
+<li><a class="reference internal" href="#debian-salsa-ci-yml-1" id="toc-entry-47"><tt class="docutils literal"><span class="pre">debian/salsa-ci.yml</span></tt></a></li>
+<li><a class="reference internal" href="#debian-symbols" id="toc-entry-48"><tt class="docutils literal">debian/symbols</tt></a></li>
+<li><a class="reference internal" href="#debhelper" id="toc-entry-49">Debhelper</a></li>
+<li><a class="reference internal" href="#version-control-systems" id="toc-entry-50">Version control systems</a><ul>
+<li><a class="reference internal" href="#source-package-stored-in-a-git-repository-on-salsa" id="toc-entry-51">Source package stored in a Git repository on Salsa</a></li>
+<li><a class="reference internal" href="#tags" id="toc-entry-52">Tags</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#new-package" id="toc-entry-52">New package</a></li>
-<li><a class="reference internal" href="#the-debian-med-blend-tasks" id="toc-entry-53">The Debian Med Blend tasks</a></li>
-<li><a class="reference internal" href="#building-and-tagging-the-packages" id="toc-entry-54">Building and tagging the packages</a></li>
-<li><a class="reference internal" href="#handling-patches" id="toc-entry-55">Handling patches</a><ul>
-<li><a class="reference internal" href="#using-quilt" id="toc-entry-56">Using <tt class="docutils literal">quilt</tt></a><ul>
-<li><a class="reference internal" href="#creating-a-patch" id="toc-entry-57">Creating a patch</a></li>
-<li><a class="reference internal" href="#applying-and-unapplying-patches" id="toc-entry-58">Applying and unapplying patches</a></li>
-<li><a class="reference internal" href="#editing-patches" id="toc-entry-59">Editing patches</a></li>
-<li><a class="reference internal" href="#renaming-patches" id="toc-entry-60">Renaming patches</a></li>
-<li><a class="reference internal" href="#updating-patches" id="toc-entry-61">Updating patches</a></li>
-<li><a class="reference internal" href="#other-commands" id="toc-entry-62">Other commands</a></li>
+<li><a class="reference internal" href="#new-package" id="toc-entry-53">New package</a></li>
+<li><a class="reference internal" href="#the-debian-med-blend-tasks" id="toc-entry-54">The Debian Med Blend tasks</a></li>
+<li><a class="reference internal" href="#building-and-tagging-the-packages" id="toc-entry-55">Building and tagging the packages</a></li>
+<li><a class="reference internal" href="#handling-patches" id="toc-entry-56">Handling patches</a><ul>
+<li><a class="reference internal" href="#using-quilt" id="toc-entry-57">Using <tt class="docutils literal">quilt</tt></a><ul>
+<li><a class="reference internal" href="#creating-a-patch" id="toc-entry-58">Creating a patch</a></li>
+<li><a class="reference internal" href="#applying-and-unapplying-patches" id="toc-entry-59">Applying and unapplying patches</a></li>
+<li><a class="reference internal" href="#editing-patches" id="toc-entry-60">Editing patches</a></li>
+<li><a class="reference internal" href="#renaming-patches" id="toc-entry-61">Renaming patches</a></li>
+<li><a class="reference internal" href="#updating-patches" id="toc-entry-62">Updating patches</a></li>
+<li><a class="reference internal" href="#other-commands" id="toc-entry-63">Other commands</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
-<li><a class="reference internal" href="#embedding-large-test-data" id="toc-entry-63">Embedding Large Test Data</a></li>
-<li><a class="reference internal" href="#faq" id="toc-entry-64">FAQ</a><ul>
-<li><a class="reference internal" href="#how-to-easily-help-upstream-exactly-reproduce-build-test-errors-that-may-be-specific-to-debian" id="toc-entry-65">How to easily help upstream exactly reproduce build/test errors that may be specific to Debian?</a></li>
-<li><a class="reference internal" href="#what-to-do-if-a-large-package-does-not-build-on-a-specific-autobuilder-architecture" id="toc-entry-66">What to do if a large package does not build on a specific autobuilder architecture?</a></li>
+<li><a class="reference internal" href="#embedding-large-test-data" id="toc-entry-64">Embedding Large Test Data</a></li>
+<li><a class="reference internal" href="#faq" id="toc-entry-65">FAQ</a><ul>
+<li><a class="reference internal" href="#how-to-easily-help-upstream-exactly-reproduce-build-test-errors-that-may-be-specific-to-debian" id="toc-entry-66">How to easily help upstream exactly reproduce build/test errors that may be specific to Debian?</a></li>
+<li><a class="reference internal" href="#what-to-do-if-a-large-package-does-not-build-on-a-specific-autobuilder-architecture" id="toc-entry-67">What to do if a large package does not build on a specific autobuilder architecture?</a></li>
</ul>
</li>
</ul>
@@ -502,8 +503,13 @@ immediate benefit. You may also consider to write respective articles
for Magazines, be they online or in print. Or just help point the developers
of a software to the Debian package and suggest respective link to their
home page, maybe supported by a badge from <a class="reference external" href="https://badges.debian.net/">https://badges.debian.net/</a>.</p>
+<div class="section" id="communications">
+<h2><a class="toc-backref" href="#toc-entry-3">Communications</a></h2>
+<p>The official mailing list of the Debian-Med team is <a class="reference external" href="mailto:debian-med@lists.debian.org">debian-med@lists.debian.org</a> ; you can read the archives of the list and subscribe at <a class="reference external" href="https://lists.debian.org/debian-med/">https://lists.debian.org/debian-med/</a>. The official chat room of the Debian-Med team is <a class="reference external" href="https://matrix.to">https://matrix.to</a>/#/#debian-med:matrix.org.</p>
+<p>Like all Debian spaces, the mailing list and the chat room of the Debian-Med team is subject to the <a class="reference external" href="https://www.debian.org/code_of_conduct">Debian Code of Conduct</a>.</p>
+</div>
<div class="section" id="membership">
-<h2><a class="toc-backref" href="#toc-entry-3">Membership</a></h2>
+<h2><a class="toc-backref" href="#toc-entry-4">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>.
@@ -513,7 +519,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="#toc-entry-4">Essential readings</a></h2>
+<span id="readings"></span><h2><a class="toc-backref" href="#toc-entry-5">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>
@@ -529,7 +535,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="#toc-entry-5">Contributing to this Policy</a></h2>
+<span id="meta"></span><h2><a class="toc-backref" href="#toc-entry-6">Contributing to this Policy</a></h2>
<p>This policy is itself <a class="reference external" href="https://salsa.debian.org/med-team/policy">maintained in Git</a>
and all team members have write access to its repository. Clone it with:</p>
<pre class="literal-block">
@@ -545,12 +551,12 @@ a small delay before the changes are visible.</p>
</div>
</div>
<div class="section" id="repositories">
-<h1><a class="toc-backref" href="#toc-entry-6">Repositories</a></h1>
+<h1><a class="toc-backref" href="#toc-entry-7">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="#toc-entry-7">Give me the source!</a></h2>
+<span id="source"></span><h2><a class="toc-backref" href="#toc-entry-8">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>
@@ -583,9 +589,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="#toc-entry-8">Common Git repository structures</a></h2>
+<span id="git-repository-structures"></span><h2><a class="toc-backref" href="#toc-entry-9">Common Git repository structures</a></h2>
<div class="section" id="gbp-buildpackage">
-<span id="git-buildpackage"></span><h3><a class="toc-backref" href="#toc-entry-9"><tt class="docutils literal">gbp buildpackage</tt></a></h3>
+<span id="git-buildpackage"></span><h3><a class="toc-backref" href="#toc-entry-10"><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
@@ -598,7 +604,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="#toc-entry-10">Social Git</a></h3>
+<span id="git-without-tarball"></span><h3><a class="toc-backref" href="#toc-entry-11">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
@@ -613,20 +619,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="#toc-entry-11">Other branches</a></h3>
+<span id="git-branches"></span><h3><a class="toc-backref" href="#toc-entry-12">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="#toc-entry-12">Git tips</a></h2>
+<h2><a class="toc-backref" href="#toc-entry-13">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="#toc-entry-13">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="#toc-entry-14">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="#toc-entry-14">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="#toc-entry-15">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>
@@ -636,7 +642,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="#toc-entry-15">To create a new local git repository</a></h3>
+<span id="new-repository-with-gbp"></span><h3><a class="toc-backref" href="#toc-entry-16">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
@@ -666,14 +672,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="#toc-entry-16">To clone and follow every branch of a git repository.</a></h3>
+<h3><a class="toc-backref" href="#toc-entry-17">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="#toc-entry-17">To track extra upstream branches, simply check them out.</a></h3>
+<span id="git-track-new-branches"></span><h3><a class="toc-backref" href="#toc-entry-18">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
@@ -681,7 +687,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="#toc-entry-18">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="#toc-entry-19">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>
@@ -693,7 +699,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="#toc-entry-19">Creating a new repository on Salsa</a></h3>
+<span id="create-git-repository-on-salsa"></span><h3><a class="toc-backref" href="#toc-entry-20">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
@@ -703,7 +709,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="#toc-entry-20">To change the default branch.</a></h3>
+<span id="git-change-default-branch"></span><h3><a class="toc-backref" href="#toc-entry-21">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
@@ -711,7 +717,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="#toc-entry-21">To push the package.</a></h3>
+<span id="push-package-to-salsa"></span><h3><a class="toc-backref" href="#toc-entry-22">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
@@ -722,7 +728,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="#toc-entry-22">To push all your work</a></h3>
+<span id="git-push-all-tags"></span><h3><a class="toc-backref" href="#toc-entry-23">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">
@@ -731,12 +737,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="#toc-entry-23">To tag a release</a></h3>
+<span id="git-tag-release"></span><h3><a class="toc-backref" href="#toc-entry-24">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-their-sources-with-git">
-<span id="git-debian-version-from-commit"></span><h3><a class="toc-backref" href="#toc-entry-24">If upstream manages their sources with Git.</a></h3>
+<span id="git-debian-version-from-commit"></span><h3><a class="toc-backref" href="#toc-entry-25">If upstream manages their 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">
@@ -753,7 +759,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="#toc-entry-25">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="#toc-entry-26">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">
@@ -787,7 +793,7 @@ for Debian 11 only source uploads are allowed.</li>
</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="#toc-entry-26">Updating a source package managed with Git</a></h2>
+<span id="updating-git-package"></span><h2><a class="toc-backref" href="#toc-entry-27">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>
@@ -826,9 +832,9 @@ to upgrade some package to the latest upstream version.</p>
</div>
</div>
<div class="section" id="packaging">
-<h1><a class="toc-backref" href="#toc-entry-27">Packaging</a></h1>
+<h1><a class="toc-backref" href="#toc-entry-28">Packaging</a></h1>
<div class="section" id="newcomer-guidelines-for-building-proper-debian-packages">
-<span id="packagingguidelines"></span><h2><a class="toc-backref" href="#toc-entry-28">Newcomer guidelines for building proper Debian packages</a></h2>
+<span id="packagingguidelines"></span><h2><a class="toc-backref" href="#toc-entry-29">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
@@ -844,7 +850,7 @@ 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="#toc-entry-29">Announcing intent to package</a></h2>
+<span id="itp"></span><h2><a class="toc-backref" href="#toc-entry-30">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>
@@ -857,7 +863,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="#toc-entry-30">Backports</a></h2>
+<h2><a class="toc-backref" href="#toc-entry-31">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
@@ -893,7 +899,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="#toc-entry-31">PPA for Ubuntu</a></h2>
+<span id="ppa"></span><h2><a class="toc-backref" href="#toc-entry-32">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
@@ -918,11 +924,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="#toc-entry-32">Debian unstable chroot on Ubuntu</a></h2>
+<span id="sidonubuntu"></span><h2><a class="toc-backref" href="#toc-entry-33">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="#toc-entry-33">Derivatives working together with Debian Med</a></h2>
+<span id="derivatives"></span><h2><a class="toc-backref" href="#toc-entry-34">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
@@ -937,7 +943,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="#toc-entry-34">R packages</a></h2>
+<h2><a class="toc-backref" href="#toc-entry-35">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
@@ -949,7 +955,7 @@ binary package.</p>
</div>
</div>
<div class="section" id="tasks">
-<h1><a class="toc-backref" href="#toc-entry-35">Tasks</a></h1>
+<h1><a class="toc-backref" href="#toc-entry-36">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
@@ -966,9 +972,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="#toc-entry-36">Policy</a></h1>
+<h1><a class="toc-backref" href="#toc-entry-37">Policy</a></h1>
<div class="section" id="debian-control-1">
-<span id="debian-control"></span><h2><a class="toc-backref" href="#toc-entry-37"><tt class="docutils literal">debian/control</tt></a></h2>
+<span id="debian-control"></span><h2><a class="toc-backref" href="#toc-entry-38"><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>
@@ -1032,7 +1038,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="debian-copyright-1">
-<span id="debian-copyright"></span><h2><a class="toc-backref" href="#toc-entry-38"><tt class="docutils literal">debian/copyright</tt></a></h2>
+<span id="debian-copyright"></span><h2><a class="toc-backref" href="#toc-entry-39"><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
@@ -1063,7 +1069,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="debian-changelog-1">
-<span id="debian-changelog"></span><h2><a class="toc-backref" href="#toc-entry-39"><tt class="docutils literal">debian/changelog</tt></a></h2>
+<span id="debian-changelog"></span><h2><a class="toc-backref" href="#toc-entry-40"><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
@@ -1071,7 +1077,7 @@ done automatically by declaring
<tt class="docutils literal">dch</tt>.</p>
</div>
<div class="section" id="debian-upstream-1">
-<span id="debian-upstream"></span><h2><a class="toc-backref" href="#toc-entry-40"><tt class="docutils literal">debian/upstream</tt></a></h2>
+<span id="debian-upstream"></span><h2><a class="toc-backref" href="#toc-entry-41"><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
@@ -1084,7 +1090,7 @@ RRID, bio.tools, OMICtools). The metadata allows for references to
publications and entries in these registries alike.</p>
</div>
<div class="section" id="debian-gbp-conf-1">
-<span id="debian-gbp-conf"></span><h2><a class="toc-backref" href="#toc-entry-41"><tt class="docutils literal">debian/gbp.conf</tt></a></h2>
+<span id="debian-gbp-conf"></span><h2><a class="toc-backref" href="#toc-entry-42"><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">
@@ -1103,7 +1109,7 @@ pristine-tar = True
</pre>
</div>
<div class="section" id="debian-readme-source-1">
-<span id="debian-readme-source"></span><h2><a class="toc-backref" href="#toc-entry-42"><tt class="docutils literal">debian/README.source</tt></a></h2>
+<span id="debian-readme-source"></span><h2><a class="toc-backref" href="#toc-entry-43"><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
@@ -1112,20 +1118,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="debian-readme-test-1">
-<span id="debian-readme-test"></span><h2><a class="toc-backref" href="#toc-entry-43"><tt class="docutils literal">debian/README.test</tt></a></h2>
+<span id="debian-readme-test"></span><h2><a class="toc-backref" href="#toc-entry-44"><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="debian-source-format-1">
-<span id="debian-source-format"></span><h2><a class="toc-backref" href="#toc-entry-44"><tt class="docutils literal">debian/source/format</tt></a></h2>
+<span id="debian-source-format"></span><h2><a class="toc-backref" href="#toc-entry-45"><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="#toc-entry-45"><tt class="docutils literal">debian/source/options</tt></a></h2>
+<span id="debian-source-option"></span><h2><a class="toc-backref" href="#toc-entry-46"><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>
@@ -1134,7 +1140,7 @@ the <tt class="docutils literal">3.0 (quilt)</tt> format brings other advantages
the conservation of file permissions in the <tt class="docutils literal">debian</tt> directory.</p>
</div>
<div class="section" id="debian-salsa-ci-yml-1">
-<span id="debian-salsa-ci-yml"></span><h2><a class="toc-backref" href="#toc-entry-46"><tt class="docutils literal"><span class="pre">debian/salsa-ci.yml</span></tt></a></h2>
+<span id="debian-salsa-ci-yml"></span><h2><a class="toc-backref" href="#toc-entry-47"><tt class="docutils literal"><span class="pre">debian/salsa-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
@@ -1167,7 +1173,7 @@ variables:
<p>Again, refer to the README provided by the Salsa CI team for more options.</p>
</div>
<div class="section" id="debian-symbols">
-<span id="symbols"></span><h2><a class="toc-backref" href="#toc-entry-47"><tt class="docutils literal">debian/symbols</tt></a></h2>
+<span id="symbols"></span><h2><a class="toc-backref" href="#toc-entry-48"><tt class="docutils literal">debian/symbols</tt></a></h2>
<p><a class="reference external" href="https://wiki.debian.org/UsingSymbolsFiles">Symbols files</a> in libraries
usually require more effort for maintenance.
However, these can be very important to detect ABI changes that are
@@ -1183,7 +1189,7 @@ could simplify the creation and maintenance of symbols files. The
is available online.</p>
</div>
<div class="section" id="debhelper">
-<h2><a class="toc-backref" href="#toc-entry-48">Debhelper</a></h2>
+<h2><a class="toc-backref" href="#toc-entry-49">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,
@@ -1195,26 +1201,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="#toc-entry-49">Version control systems</a></h2>
+<span id="vcs"></span><h2><a class="toc-backref" href="#toc-entry-50">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="#toc-entry-50">Source package stored in a Git repository on Salsa</a></h3>
+<span id="vcs-git"></span><h3><a class="toc-backref" href="#toc-entry-51">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="#toc-entry-51">Tags</a></h3>
+<span id="vcs-tags"></span><h3><a class="toc-backref" href="#toc-entry-52">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="#toc-entry-52">New package</a></h2>
+<h2><a class="toc-backref" href="#toc-entry-53">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="#toc-entry-53">The Debian Med Blend tasks</a></h2>
+<span id="new-packages-in-tasks"></span><h2><a class="toc-backref" href="#toc-entry-54">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
@@ -1222,13 +1228,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="#toc-entry-54">Building and tagging the packages</a></h2>
+<span id="building-and-tagging"></span><h2><a class="toc-backref" href="#toc-entry-55">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="#toc-entry-55">Handling patches</a></h2>
+<span id="patches"></span><h2><a class="toc-backref" href="#toc-entry-56">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
@@ -1240,7 +1246,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="#toc-entry-56">Using <tt class="docutils literal">quilt</tt></a></h3>
+<span id="quilt"></span><h3><a class="toc-backref" href="#toc-entry-57">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
@@ -1256,7 +1262,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="#toc-entry-57">Creating a patch</a></h4>
+<span id="quilt-create"></span><h4><a class="toc-backref" href="#toc-entry-58">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>
@@ -1279,7 +1285,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="#toc-entry-58">Applying and unapplying patches</a></h4>
+<span id="quilt-apply"></span><h4><a class="toc-backref" href="#toc-entry-59">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>
@@ -1294,7 +1300,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="#toc-entry-59">Editing patches</a></h4>
+<span id="quilt-edit"></span><h4><a class="toc-backref" href="#toc-entry-60">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>
@@ -1304,13 +1310,13 @@ 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="#toc-entry-60">Renaming patches</a></h4>
+<span id="quilt-rename"></span><h4><a class="toc-backref" href="#toc-entry-61">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="updating-patches">
-<span id="quilt-other"></span><h4><a class="toc-backref" href="#toc-entry-61">Updating patches</a></h4>
+<span id="quilt-other"></span><h4><a class="toc-backref" href="#toc-entry-62">Updating patches</a></h4>
<p>After updating a package to a new upstream version, it can happen
that the patches do not apply cleanly anymore. Try <tt class="docutils literal">quilt pop <span class="pre">-a</span></tt>,
to remove all patches, and then <tt class="docutils literal">quilt push</tt> one patch at a time.</p>
@@ -1327,7 +1333,7 @@ corresponding <tt class="docutils literal">*.rej</tt> files, and then update the
<tt class="docutils literal">quilt refresh</tt>.</p>
</div>
<div class="section" id="other-commands">
-<h4><a class="toc-backref" href="#toc-entry-62">Other commands</a></h4>
+<h4><a class="toc-backref" href="#toc-entry-63">Other commands</a></h4>
<p>Please see <tt class="docutils literal">man 1 quilt</tt> to have a comprehensive list of commands
and the <a class="reference external" href="https://wiki.debian.org/UsingQuilt">UsingQuilt</a> page on
the Debian Wiki.</p>
@@ -1336,7 +1342,7 @@ the Debian Wiki.</p>
</div>
</div>
<div class="section" id="embedding-large-test-data">
-<h1><a class="toc-backref" href="#toc-entry-63">Embedding Large Test Data</a></h1>
+<h1><a class="toc-backref" href="#toc-entry-64">Embedding Large Test Data</a></h1>
<p>Often a lot of times, there's a need to fetch external data for adding autopkgtests.
We choose to make a separate orig tarball for data if the size of data far exceeds the size of package.</p>
<p><tt class="docutils literal">Step - 1:</tt></p>
@@ -1363,9 +1369,9 @@ Simply use the <tt class="docutils literal"><span class="pre">debian-tests-data<
For further reading, check <a class="reference external" href="https://wiki.debian.org/Javascript/GroupSourcesTutorial#Manual_way">Javascript Team Embedding wiki</a></p>
</div>
<div class="section" id="faq">
-<h1><a class="toc-backref" href="#toc-entry-64">FAQ</a></h1>
+<h1><a class="toc-backref" href="#toc-entry-65">FAQ</a></h1>
<div class="section" id="how-to-easily-help-upstream-exactly-reproduce-build-test-errors-that-may-be-specific-to-debian">
-<span id="autobuilder"></span><h2><a class="toc-backref" href="#toc-entry-65">How to easily help upstream exactly reproduce build/test errors that may be specific to Debian?</a></h2>
+<span id="autobuilder"></span><h2><a class="toc-backref" href="#toc-entry-66">How to easily help upstream exactly reproduce build/test errors that may be specific to Debian?</a></h2>
<p>For packages already uploaded, you can adapt the Dockerfile below to <a class="reference external" href="https://github.com/sunpy/sunpy/issues/7550#issue-2225805770">share with
upstream</a> so
they can see the error and be able to inspect and troubleshoot with the exact
@@ -1389,7 +1395,7 @@ option to <tt class="docutils literal">docker build</tt> (or <tt class="docutils
architecture, and <tt class="docutils literal">linux/mips64le</tt> for mips64**el**.</p>
</div>
<div class="section" id="what-to-do-if-a-large-package-does-not-build-on-a-specific-autobuilder-architecture">
-<h2><a class="toc-backref" href="#toc-entry-66">What to do if a large package does not build on a specific autobuilder architecture?</a></h2>
+<h2><a class="toc-backref" href="#toc-entry-67">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
=====================================
@@ -62,6 +62,13 @@ for Magazines, be they online or in print. Or just help point the developers
of a software to the Debian package and suggest respective link to their
home page, maybe supported by a badge from https://badges.debian.net/.
+Communications
+--------------
+
+The official mailing list of the Debian-Med team is debian-med at lists.debian.org ; you can read the archives of the list and subscribe at https://lists.debian.org/debian-med/. The official chat room of the Debian-Med team is https://matrix.to/#/#debian-med:matrix.org.
+
+Like all Debian spaces, the mailing list and the chat room of the Debian-Med team is subject to the `Debian Code of Conduct <https://www.debian.org/code_of_conduct>`_.
+
Membership
----------
View it on GitLab: https://salsa.debian.org/med-team/policy/-/commit/a4534e0984e7d64dbaa6eb228eccc11b5e2527ee
--
View it on GitLab: https://salsa.debian.org/med-team/policy/-/commit/a4534e0984e7d64dbaa6eb228eccc11b5e2527ee
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/20240406/36eccf0b/attachment-0001.htm>
More information about the debian-med-commit
mailing list