Bug#569486: edos-distcheck: doesn't handle multiple versions of same packages in Packages nicely

[Ralf Treinen <treinen@free.fr>]

Bonsoir,

On Thu, Feb 11, 2010 at 10:09:30PM +0100, Lucas Nussbaum wrote:

> Apparently, edos-builddebcheck (at least) doesn't handle having several
> versions of the same package in the same Packages or Sources file (that
> change was introduced at the end of 2009 by ftpmasters).
> 
> Example:
> prelude-manager (= 1.0.0~rc1-1): FAILED
>   prelude-manager (= 1.0.0~rc1-1) build-depends on one of:
>   - libpreludedb-dev (= 1.0.0~rc1-1)
>   libpreludedb-dev (= 1.0.0~rc1-1) depends on one of:
>   - libpreludedb0 (= 1.0.0~rc1-1)
> prelude-manager (= 0.9.15-4): FAILED
>   prelude-manager (= 0.9.15-4) build-depends on one of:
>   - libpreludedb-dev (= 1.0.0~rc1-1)
>   libpreludedb-dev (= 1.0.0~rc1-1) depends on one of:
>   - libpreludedb0 (= 1.0.0~rc1-1)

In my understanding that shows exactly that edos-(build)debcheck does handle
multiple versions of the same package, since it analyses each of them. For us
(mancoosi/edos), all packages and versions are born with an equal right
to be analysed ;-)

> You probably only want to list the newer version.

Two answers:
- no, we do not want to do that by default (see above)
- yes, that might be useful for some application scenarios. I'm putting this
  on the wishlist, but it certainly won't be integrated before we move on
  to the new edos-distcheck that will be based on the dose3 library.

BTW, for build-dependencies you can achieve that by filtering out old
versions from the Sources file. I mention this since it does *not* hold for 
edos-debcheck. The reason is that the semantics of binary dependencies are
transitive, while this is not the case for build-dependencies. IOW, 
removing an old version of source package can never impede the
build-dependencies of other packages/versions.

-Ralf