On Thu, Sep 14, 2006 at 12:55:47PM +0200, Goswin von Brederlow wrote: > Steve Langasek <[EMAIL PROTECTED]> writes:
> > If you want to declare a strict versioned dependency from an arch: all > > package to an arch: any package... don't do that, because it will break > > under binNMUs. :) > I only know of one simple way to handle this: > arch:any provides any-package-1.2-3 > arch:all depends any-package-1.2-3 > Some people try to use > arch:all depends any-package (>= version), any-package (<< next-version) > The BIG problem is how to get the next-version. Say you have version > 1.2-3. A binNMU would be 1.2-3+b1, a security release would be > 1.2-3etch1 (unless there was a binNMU). In the Great Scheme, these were supposed to become 1.2-3+etch1 instead of 1.2-3etch1 so that security NMUs would sort higher than binNMUs... -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
