Package: developers-reference Version: 3.3.3 Severity: wishlist Hello,
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 using $(Source-Version). 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 5.10.2.1: ... 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. Despite ... (Don't hesitate to fix my grammar/spelling in this paragraph, English is not my native language). Cheers, Aurelien -- System Information: Debian Release: testing/unstable Architecture: i386 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 [EMAIL PROTECTED]) -- no debconf information
