--- ChangeLog 11 Apr 2005 06:24:29 -0000 1.293

+++ ChangeLog	16 Apr 2005 04:39:27 -0000
@@ -1,3 +1,20 @@
+2005-04-16  Junichi Uekawa  <dancer@debian.org>
+
+	* pbuilder-modules: document signing-related options in pbuilder-options.
+
+	* pdebuild-user-mode-linux:
+	* pdebuild: implement keyid specification.
+
+	* Documentation/pbuilder-doc.xml: add document on using auto-debsign
+	and add a FAQ entry for source.changes file.
+
+	* pbuilder-checkparams: use --debsign-k option
+	to specify DEBSIGN_KEYID
+
+	* pdebuild.1: add --debsign-k option
+
+	* pdebuild-user-mode-linux.1: add --debsign-k option
+

1 files changed, 23 insertions, 0 deletions

diff --git a/Documentation/pbuilder-doc.xml b/Documentation/pbuilder-doc.xml
index 6b04918..a488583 100644
--- a/Documentation/pbuilder-doc.xml
+++ b/Documentation/pbuilder-doc.xml
@@ -981,6 +981,29 @@ $ sudo pbuilder update --hookdir ~/loginhooks/E10shell
 	inside your chroot.
       </para>
     </sect1>
+    <sect1 id="sponsor">
+      <title>Using pdebuild to sponsor package</title>
+      <para>
+	To sign a package marking for sponsorship, 
+	it is possible to use<command><option> --auto-debsign</option></command> and 
+	<command><option>--debsign-k</option></command> options of pdebuild.
+      </para>
+      <screen>
+	<command>pdebuild  <option>--auto-debsign </option> <option>--debsign-k </option><parameter>XXXXXXXX</parameter></command>
+      </screen>
+    </sect1>
+    <sect1 id="sourcechanges">
+      <title>Why is there a source.changes file in ../?</title>
+      <para>
+	When running pdebuild, pbuilder will run dpkg-buildpackage to create a 
+	Debian source package to pass it on to pbuilder.
+	File named XXXX_YYY_source.changes is what remains from that process.
+	It is harmless unless you try to upload it to the Debian archive.
+      </para>
+      <para>
+	This behavior is different when running through --use-pdebuild-internal
+      </para>
+    </sect1>
     <!-- end of FAQ -->
   </chapter>
   <chapter id="otheruse">