On Mon, Jul 28, 2008, Luk Claes wrote: > > Hmm I don't know; this support for ~ versions feels backward to me: > > casically all build-deps in the archive would need it, so it seems > > wrong to add a ~ only to the ones I touch. It would seem more > > appropriate to e.g. append ~ to all versions numbers in build-deps > > before building backported packages for instance. > > > > If you have a pointer on recommended practice or rationale, I'm happy > > to learn why and in which case to do this though. > > The lintian warning tells to not use versioned build-deps that include > Debian revisions if possible to not make backporting harder. There are > two options to not do it: either strip the Debian revision (what > happened in the previous upload and should work fine unless there are > versions in between the upstream version and the revision) or to add ~ > to the revision which works in all cases.
Sure, I understand why it makes it easier to backport the package with the ~ (see my previous remark), I just wonder why backporters don't use a centralized approach of changing all Debian revs programatically instead of relying on maintainers to have backports knowledge. (Thanks for the pointer to the lintian tag; I see the text was updated since last time I read it.) Anyway, pushing another NMU with ~, thanks. -- Loïc Minier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
