Re: binNMU safe and ${binary:Version} or ${source:Version}

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Steve Langasek <vorlon@debian.org> 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).

Now, next-version must allow 1.2-3+b1 to be installed but not
1.2-3etch1. But 1.2-3etch1 is << 1.2-3+b1 making this somewhat
impossible.

% dpkg --compare-versions "1.2-3etch1" "<<" "1.2-3+b1" && echo yes
yes

Maybe this would work:

any-package (= ${source:version}) | any-package (>= ${source:version}+b1), any-package (= ${source:version}) | any-package (<< ${source:version}+c)

MfG
        Goswin