Hi,
Antoine Beaupré <anarcat@moszumanska.debian.org> (2016-10-03):
> anarcat pushed a commit to branch master
> in repository developers-reference.
>
> commit 6d8601bf8adb048e9239b56824e092b5528c76bb
> Author: Antoine Beaupré <anarcat@debian.org>
> Date: Mon Oct 3 10:11:53 2016 -0400
>
> clarify how the patch should be made for p-u
> ---
> pkgs.dbk | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/pkgs.dbk b/pkgs.dbk
> index 5391dd1..4d023d5 100644
> --- a/pkgs.dbk
> +++ b/pkgs.dbk
> @@ -314,9 +314,12 @@ To ensure that your upload will be accepted, you should discuss the changes
> with the stable release team before you upload. For that, file a bug against
> the <systemitem role="package">release.debian.org</systemitem> pseudo-package
> using <command>reportbug</command>, including the patch you want to
> -apply to the package version currently in <literal>stable</literal>. Always
> -be verbose and detailed in your changelog entries for uploads to the
> -<literal>stable</literal> distribution (e.g. `&codename-stable;').
> +apply to the package version currently in <literal>stable</literal>.
> +The patch should be a <command>debdiff</command> (see <xref
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Can we please make that “a source debdiff”? We've already seen
binary(-only) debdiffs…
Thanks.
> +linkend="debdiff"/>) against the current version in
> +<literal>stable</literal>. Always be verbose and detailed in your
> +changelog entries for uploads to the <literal>stable</literal>
> +distribution (e.g. `&codename-stable;').
> </para>
> <para>
> Extra care should be taken when uploading to <literal>stable</literal>.
KiBi.
Attachment:
signature.asc
Description: Digital signature