Andreas Tille pushed to branch master at Debian Med / policy
Commits: 60c6093b by Andreas Tille at 2024-02-22T10:50:25+01:00 Explain gbp import-orig and mention routine-update - - - - - 2 changed files: - policy.html - policy.rst Changes: ===================================== policy.html ===================================== @@ -1,9 +1,9 @@ -<?xml version="1.0" encoding="utf-8" ?> +<?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <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.19: https://docutils.sourceforge.io/" /> +<meta name="generator" content="Docutils 0.20.1: https://docutils.sourceforge.io/" /> <title>policy.rst</title> <style type="text/css"> @@ -799,6 +799,11 @@ the repository alone (not doing so results in archive rejection of package updates). With recent versions of <tt class="docutils literal">gbp buildpackage</tt>, it is often unnecessary to rename the freshly downloaded original upstream archive.</p> +<p>Assuming you use <tt class="docutils literal">gbp buildpackage</tt> which is strongly recommended in +the Debian Med team you want to import the new upstream source by using</p> +<pre class="literal-block"> +gbp import-orig --pristine-tar --no-interactive PACKAGE_VERSION.orig.tar.gz +</pre> <p>If you do not use <tt class="docutils literal">gbp buildpackage</tt>, please use <tt class="docutils literal"><span class="pre">pristine-tar</span></tt> anyway to register the compressed archives that you upload to Debian as original upstream sources (the <tt class="docutils literal"><span class="pre">orig.tar.{gz|bz2|xz}</span></tt> file), with a @@ -814,6 +819,9 @@ pristine-tar commit tarball tag avoid sending too many messages, consider setting the option <tt class="docutils literal">multimailhook.maxCommitEmails</tt> to a low value, for instance 20; the default is 500…</p> +<p>There is also a more or less automated workflow using the <tt class="docutils literal"><span class="pre">routine-update</span></tt> +package. It provides a shell script which usually does what you want +to upgrade some package to the latest upstream version.</p> </div> </div> <div class="section" id="packaging"> ===================================== policy.rst ===================================== @@ -454,6 +454,13 @@ package updates). With recent versions of ``gbp buildpackage``, it is often unnecessary to rename the freshly downloaded original upstream archive. +Assuming you use ``gbp buildpackage`` which is strongly recommended in +the Debian Med team you want to import the new upstream source by using + +:: + + gbp import-orig --pristine-tar --no-interactive PACKAGE_VERSION.orig.tar.gz + If you do not use ``gbp buildpackage``, please use ``pristine-tar`` anyway to register the compressed archives that you upload to Debian as original upstream sources (the ``orig.tar.{gz|bz2|xz}`` file), with a @@ -472,6 +479,11 @@ avoid sending too many messages, consider setting the option ``multimailhook.maxCommitEmails`` to a low value, for instance 20; the default is 500… +There is also a more or less automated workflow using the ``routine-update`` +package. It provides a shell script which usually does what you want +to upgrade some package to the latest upstream version. + + Packaging ========= View it on GitLab: https://salsa.debian.org/med-team/policy/-/commit/60c6093b14e51b11f421a916ba7c53b5aeba5afd -- View it on GitLab: https://salsa.debian.org/med-team/policy/-/commit/60c6093b14e51b11f421a916ba7c53b5aeba5afd You're receiving this email because of your account on salsa.debian.org.
_______________________________________________ debian-med-commit mailing list debian-med-com...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-commit