Bug#431814: Source field of .changes files may contain a version number
Russ Allbery <rra@debian.org> writes:
> Package: debian-policy
> Version: 3.7.2.2
> Severity: wishlist
>
> Per recent mail from Guillem Jover, the version number is also added
> to the Source field of .changes files for binNMUs. This change was
> made in dpkg 1.13.22 and is therefore currently in stable. dak also
> now supports it.
>
> This diff attempts to bring Policy back in line with current practice.
> Comments?
I believe this change is obviously correct, so since I've gotten no
replies to this message, I'm committing it.
> --- orig/policy.sgml
> +++ mod/policy.sgml
> @@ -2336,14 +2336,14 @@
> </p>
>
> <p>
> - In a main source control information, a <file>.changes</file>
> - or a <file>.dsc</file> file this may contain only the name
> - of the source package.
> + In <file>debian/control</file> or a <file>.dsc</file> file,
> + this field must contain only the name of the source package.
> </p>
>
> <p>
> - In the control file of a binary package it may be followed
> - by a version number in parentheses<footnote>
> + In a binary package control file or a <file>.changes</file>
> + file, the source package name may be followed by a version
> + number in parentheses<footnote>
> It is customary to leave a space after the package name
> if a version number is specified.
> </footnote>.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: