Charles Plessy <plessy@debian.org> (28/01/2009): > The advantage is normalisation. I prefer to use the latest Debhelper > version if possible. We have more than 100 packages in our repository, > and if some carry on some legacy versions from upgrade to upgrade, > each time one will work on the packate, he will have to figure out why > the latest is not used. With the latest upload of BioFOX, I took the > opportunity to verify that it was compatible with Debhelper 7. That also means that release managers have to check that, too. If you didn't observe it during the last months, even “meant to be trivial” changes led to RC bugs. The same could happen with an apparently trivial debhelper compatibility level bump, even if the maintainer took extra care. Example: in debhelper(7), look at v7's 1st item. I guess one could obtain the wanted output when (p|cow)building, but not on the buildds, where -B is used (do you have any idea how many maintainers try a build with -B?). Tricky, yeah, but shit happens, and release managers want to lower the risks. That's why the freeze is there. That's why guidelines exist. > I hope next time we trust each other and we are not asked to upload > identical packages with cosmetical changes. Anyway, as we say in > France, "sans rancune" (no offense). Next time, abide by the guidelines, and stop wasting everyone's time. Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature