[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Can we ship sources of a PDF file in the Debian diff?



Le Tue, Apr 28, 2009 at 02:22:14PM +0200, Stefano Zacchiroli a écrit :
> Given that, in response to your upload, you will get an email
> precisely mentioning the "NEW" status of your package, the most
> natural place to provide such comments is by replying to that email.

Le Tue, Apr 28, 2009 at 09:33:46PM +0300, Andrei Popescu a écrit :
> I seem to recall that replying to the REJECT mail would be best and that 
> the template for that mail would be adjusted accordingly. Don't recall 
> where and when though.

Le Tue, Apr 28, 2009 at 10:18:36PM +0200, Joerg Jaspert a écrit :
> The best is usual the latest changelog entry (well, one of the changelog
> entries the highest-versioned .changes will include) as that is shown in
> NEW processing.
> 
> Though i should probably also extract README.source, but i dislike the
> idea of another control file.
> 
> And yes, email is also supposed to work.

Le Tue, Apr 28, 2009 at 10:19:38PM +0200, Joerg Jaspert a écrit :
> Reply to the rejection mail *or* have a changelog entry "fixed lalala as
> mentioned by ftpmaster".

Hi all,

shall I send the following patch on the Developers Reference as a whishlist
bug?

Index: pkgs.dbk
===================================================================
--- pkgs.dbk	(revision 6678)
+++ pkgs.dbk	(working copy)
@@ -48,6 +48,13 @@
 package is installed in the archive (see <xref linkend="upload-bugfix"/> ).
 </para>
 <para>
+If you think your package needs some explanations for the administrators of the
+new package queue, include them in your changelog, reply to the email you
+receive as a maintainer after your upload, or reply to the rejection email in
+case you are already re-uploading. Note that some files like
+debian/README.source may not be read.
+</para>
+<para>
 When closing security bugs include CVE numbers as well as the Closes: #nnnnn.
 This is useful for the security team to track vulnerabilities.  If an upload is
 made to fix the bug before the advisory ID is known, it is encouraged to modify

Have a nice day,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


Reply to: