[med-svn] [Git][med-team/policy][master] Rebuild the HTML file.

Tue Sep 8 19:40:14 BST 2020


Charles Plessy pushed to branch master at Debian Med / policy


Commits:
c17bfa89 by Charles Plessy at 2020-09-09T03:39:58+09:00
Rebuild the HTML file.

- - - - -


1 changed file:

- policy.html


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.16: http://docutils.sourceforge.net/" />
+<meta name="generator" content="Docutils 0.14: http://docutils.sourceforge.net/" />
 <title>policy.rst</title>
 <style type="text/css">
 
@@ -365,7 +365,7 @@ ul.auto-toc {
 
 <p><img alt="debian-med-logo" src="https://people.debian.org/~tille/debian-med/logos/med-06.jpg" /></p>
 <div class="contents topic" id="table-of-contents">
-<p class="topic-title">Table of Contents</p>
+<p class="topic-title first">Table of Contents</p>
 <ul class="simple">
 <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>
@@ -439,15 +439,16 @@ ul.auto-toc {
 <li><a class="reference internal" href="#applying-and-unapplying-patches" id="id67">Applying and unapplying patches</a></li>
 <li><a class="reference internal" href="#editing-patches" id="id68">Editing patches</a></li>
 <li><a class="reference internal" href="#renaming-patches" id="id69">Renaming patches</a></li>
-<li><a class="reference internal" href="#other-commands" id="id70">Other commands</a></li>
+<li><a class="reference internal" href="#updating-patches" id="id70">Updating patches</a></li>
+<li><a class="reference internal" href="#other-commands" id="id71">Other commands</a></li>
 </ul>
 </li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a class="reference internal" href="#faq" id="id71">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="id72">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="id72">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="id73">What to do if a large package does not build on a specific autobuilder architecture?</a></li>
 </ul>
 </li>
 </ul>
@@ -490,7 +491,7 @@ make medical and biological software available to Debian users. Read the
 <a class="reference external" href="#membership">Membership</a> section if you're interested in joining us.</p>
 <p>If you speak a language other than English, you can contribute rightaway
 with translations of package descriptions at
-<a class="reference external" href="https://ddtp.debian.net">ddtp.debian.net</a>.</p>
+<a class="reference external" href="https://ddtp.debian.org">ddtp.debian.org</a>.</p>
 <p>When working on these, you will find immediate targets for improvements
 of the original English versions, too. For these, though, you need
 access to Debian Med's source code repository. Very welcome are
@@ -518,7 +519,7 @@ details best packaging practices.</li>
 <li>The <a class="reference external" href="https://www.debian.org/doc/maint-guide/">New Maintainer's
 Guide</a>: puts a bit of the
 two above in practice.</li>
-<li>The <a class="reference external" href="https://med-team.pages.debian.net/policy.html">Debian Med
+<li>The <a class="reference external" href="https://med-team.pages.debian.net/policy/">Debian Med
 Policy</a> (this
 document): explains how the work is organised in our team.</li>
 </ul>
@@ -1268,17 +1269,36 @@ when you're done, <tt class="docutils literal">quilt refresh</tt>.</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="#id70">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>
+<p>When there was any fuzzing, do <tt class="docutils literal">quilt refresh</tt> before the next
+<tt class="docutils literal">quilt push</tt>.</p>
+<p>If a patch does apply cleanly because it is not needed anymore
+(applied upstream, etc.), it can be removed with
+<tt class="docutils literal">quilt delete <span class="pre"><patchname>.patch</span> && git rm debian/patches/patchname</tt>
+(assming the source package is managed with Git, which is the case in
+our team).</p>
+<p>If the patch is still needed, force its application with
+<tt class="docutils literal">quilt push <span class="pre">-f</span></tt>, editing the files indicated while reviewing the
+corresponding <tt class="docutils literal">*.rej</tt> files, and then update the patch with
+<tt class="docutils literal">quilt refresh</tt>.</p>
+</div>
 <div class="section" id="other-commands">
-<span id="quilt-other"></span><h4><a class="toc-backref" href="#id70">Other commands</a></h4>
-<p>Please see <tt class="docutils literal">man 1 quilt</tt> to have a comprehensive list of commands.</p>
+<h4><a class="toc-backref" href="#id71">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>
 </div>
 </div>
 </div>
 </div>
 <div class="section" id="faq">
-<h1><a class="toc-backref" href="#id71">FAQ</a></h1>
+<h1><a class="toc-backref" href="#id72">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="#id72">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="#id73">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



View it on GitLab: https://salsa.debian.org/med-team/policy/-/commit/c17bfa8959ac9180cae9701ca93e3896e2b2332f

-- 
View it on GitLab: https://salsa.debian.org/med-team/policy/-/commit/c17bfa8959ac9180cae9701ca93e3896e2b2332f
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/20200908/404471f0/attachment-0001.html>
