binNMU unsafe packages

In DebConf I’ve noticed a lintain error about some of my debian-hebrew packages. While fixing my own package, I’ve noticed a lot of other packages which have the same error.

During and after Debconf, I’ve started reporting these as bugs. The main reason for these bug are to provide the maintainer with patches to fix their debian/control.

While doing the patches and reports, I’ve stumbled on packages already binNMUed on some arches, which made them uninstallable. In a few cases I was able to provide a patch just before the package has been binNMUed.

Providing patches takes more time than just [mass-] reporting the bugs, but I believe it worth the trouble as it makes the maintainer’s life easier.

I’m following lintain.d.o for not-binnmuable-any-depends-any error and the not-binnmuable-any-depends-all / not-binnmuable-all-depends-any warnings to identify which packages are problematic. I’ve also asked to refine the not-binnmuable-any-depends-any check, to include check for binNMU unsafe packages with the old style dependency (“${Source-Version}”).

The change of the check will affect 1285 packages currently using the old style. These include some packages which are surely problematic (binary debug “-dbg” and development “-dev” packages).

So although this statement from the Release Team Meeting results is true:

* Automatic bin-NMUs have been of great use to shorten transitions. As most packages are now bin-NMUable, we will make further use of this tool for Lenny.

We still have some work to do to ease their life with the release work. Help will be appreciated.

1 Comment

Filed under Debian GNU/Linux, QA stuff

One response to “binNMU unsafe packages

  1. Pingback: Status of the binNMU unsafe packages « Free Software, the Universe and Everything

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s