Differences between revisions 2 and 3
Revision 2 as of 2006-09-25 22:44:02
Size: 1097
Comment: Adding some bits of information (still not more than a short list).
Revision 3 as of 2006-09-26 02:25:39
Size: 1316
Editor: KevinMcCarty
Comment: fix typo, add another example, mention deprecation of ${Source-Version}
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
A further example: NonMaintainerUpload See also: NonMaintainerUpload
Line 8: Line 8:
A '''binNMU''' is a binary-only non-maintainer upload. In this case the {{{arch: any}}} packages are rebuild, but the {{{arch: all}}} packages are not. This is necessary for cases, where a simple rebuild (without any changes to the package) will fix a serious error (an [http://lists.debian.org/debian-release/2006/09/msg00003.html example]). A '''binNMU''' is a binary-only non-maintainer upload. In this case the {{{arch: any}}} packages are rebuild, but the {{{arch: all}}} packages are not. This is necessary for cases, where a simple rebuild (without any changes to the package) will fix a serious error, such as a library transition ([http://lists.debian.org/debian-release/2006/09/msg00003.html example]) or a misconfiguration on the maintainer's machine ([http://lists.debian.org/debian-release/2006/09/msg00297.html example]).
Line 12: Line 12:
 * do ''not'' use the ${Source-Version} variable; this has been deprecated!
Line 14: Line 15:
 * declaring dependency between an {{{arch: any}}} to an {{{arch: all}}} package: {{{${souce:Version}}}}  * declaring dependency between an {{{arch: any}}} to an {{{arch: all}}} package: {{{${source:Version}}}}

The info in this thread could be the starting point for this page: http://lists.debian.org/debian-mentors/2006/09/msg00223.html

See also: NonMaintainerUpload

What are binNMUs?

A binNMU is a binary-only non-maintainer upload. In this case the arch: any packages are rebuild, but the arch: all packages are not. This is necessary for cases, where a simple rebuild (without any changes to the package) will fix a serious error, such as a library transition ([http://lists.debian.org/debian-release/2006/09/msg00003.html example]) or a misconfiguration on the maintainer's machine ([http://lists.debian.org/debian-release/2006/09/msg00297.html example]).

How to make packages binNMU safe?

  • do not use the ${Source-Version} variable; this has been deprecated!

  • versioned dependency on dpkg-dev (>= 1.13.19)

  • declaring dependency between 2 arch: any packages: ${binary:Version}

  • declaring dependency between an arch: any to an arch: all package: ${source:Version}

  • no way for a safe dependency between an arch: all to an arch: any package using these variables

Where to request a binNMU?

To request a binNMU ask for it on the [http://lists.debian.org/debian-release/ debian-release mailing list].