[website] 04/10: Add copyright update subsection.

[Sebastiaan Couwenberg]

This is an automated email from the git hooks/post-receive script.

sebastic pushed a commit to branch master
in repository website.

commit c9362a4e156cc5e3431a8f6a3bc19f52f60bc940
Author: Bas Couwenberg <sebas...@xs4all.nl>
Date:   Fri Apr 24 19:33:31 2015 +0200

    Add copyright update subsection.
---
 policy.xml | 46 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 46 insertions(+)

diff --git a/policy.xml b/policy.xml
index 9451ad6..318e74f 100644
--- a/policy.xml
+++ b/policy.xml
@@ -826,6 +826,11 @@ pkg-grass/
                     <link linkend="git-update-patches">Update patches for new 
upstream release</link>
                   </para>
                 </listitem>
+                <listitem>
+                  <para>
+                    <link linkend="git-update-copyright">Update copyright 
file</link>
+                  </para>
+                </listitem>
               </itemizedlist>
             </para>
           </listitem>
@@ -1208,6 +1213,47 @@ Cmnd_Alias PBUILDERS=/usr/sbin/pbuilder, 
/usr/sbin/cowbuilder
 </programlisting>
             </para>
           </sect5>
+          <sect5 id="git-update-copyright">
+            <title>Update copyright file</title>
+            <para>
+              New upstream releases are likely to include copyright changes
+              that need to be reflected in the
+              <link 
linkend="debian-copyright"><filename>debian/copyright</filename></link>
+              file.
+            </para>
+            <para>
+              Review the changes in the upstream sources since the previous
+              release by inspecting the diff between the upstream branch
+              commits.
+<programlisting>
+<command>git diff</command> <literal>upstream~1</literal> 
<literal>upstream</literal>
+</programlisting>
+              Or by tag:
+<programlisting>
+<command>git diff</command> 
<literal>upstream/</literal><replaceable>&lt;old-version&gt;</replaceable> 
<literal>upstream/</literal><replaceable>&lt;new-version&gt;</replaceable>
+</programlisting>
+              Look for removed files which may need to be removed from the
+              <filename>debian/copyright</filename> file too, new files whose
+              copyright statements need to be included in the
+              <filename>debian/copyright</filename> file, and changes in
+              existing files.
+            </para>
+            <para>
+              It may also be helpfull to review the copyright file generated
+              by <command>licensecheck2dep5</command> for the new upstream
+              release, and compared it to the existing
+              <filename>debian/copyright</filename> file.
+<programlisting>
+<command>licensecheck</command> <option>--copyright</option> 
<option>-r</option> <literal>*</literal> | 
<command>/usr/lib/cdbs/licensecheck2dep5</command> &gt; 
<filename>debian/copyright.new</filename>
+<command>diff</command> <option>-u</option> 
<filename>debian/copyright</filename> <filename>debian/copyright.new</filename>
+</programlisting>
+            </para>
+            <para>
+              Finally tools such as
+              <ulink 
url="https://tracker.debian.org/pkg/license-reconcile";>license-reconcile</ulink>
+              can be useful for copyright review too.
+            </para>
+          </sect5>
         </sect4>
         <sect4 id="git-build-package">
           <title>Building the package</title>

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/pkg-grass/website.git

_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel