${Source-Version} was confusing (since it actually is replaced with the
binary package version in, for example, binNMUs) and has been deprecated
in dpkg. ${binary:Version} should be used instead. Update Policy's
recommendation accordingly.
git-archimport-id: rra@debian.org--lenny/debian-policy--devel--3.7--patch-5
Allombert (Closes: #361418).
* Bug fix: "typo: "must not be not world-writable"", thanks to Sam
Hocevar (Closes: #392594).
-
+ * Bug fix: "debian-policy: recommend binary:Version substvar instead",
+ thanks to Guillem Jover (Closes: #418444).
+
--
debian-policy (3.7.2.2) unstable; urgency=low
Typically the development version should have an exact
version dependency on the runtime library, to make sure that
compilation and linking happens correctly. The
- <tt>${Source-Version}</tt> substitution variable can be
+ <tt>${binary:Version}</tt> substitution variable can be
useful for this purpose.
+ <footnote>
+ Previously, <tt>${Source-Version}</tt> was used, but its name
+ was confusing and it has been deprecated since dpkg 1.13.19.
+ </footnote>
</p>
</sect>
* Scripts may assume that /bin/sh supports local (at a basic level)
and that its test builtin (if any) supports -a and -o binary
logical operators. [10.4]
+ * The substitution variable ${binary:Version} should be used in place
+ of ${Source-Version} for dependencies between packages of the same
+ library. [8.5]
* Substantial reorganization and renaming of sections in the Debian
menu structure. Packages with menu entries should be reviewed to
see if the menu section has been renamed or if one of the new