Bug#213348: developers-reference: Binary-only NMU and dependencies
I remarked that some binary-only NMU are breaking packages by making
them uninstallable. The problem occurs when a source package generate
more than one binary package, a few architecture dependant and a few
architecture independant, with strict dependenciess between them, ie
If a binary-only NMU is done, the architecture dependant packages have
a different version than the architecture independant one. In that case,
binary-only NMU should be avoided, instead, the maintainer should be
asked to upload a new version.
Thus I propose the add the following paragraph to the Debian Developer's
Reference, section 18.104.22.168:
... available one).
You have to make sure that doing a binary-only NMU won't render the
package uninstallable. It could occur when a source package generates
both architecture dependant and independant packages that depend on
each other through $(Source-Version). In the later case, you may
consider doing a source NMU.
(Don't hesitate to fix my grammar/spelling in this paragraph, English
is not my native language).
-- System Information:
Debian Release: testing/unstable
Kernel: Linux pc.aurel32 2.4.22 #1 mer sep 17 20:55:21 CEST 2003 i686
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (ignored: LC_ALL set to fr_FR@euro)
-- no debconf information