[buildd-tools-devel] new buildd dependency resolution breaks self depends?

[Julien Cristau]

On Tue, Mar 29, 2011 at 17:25:14 +0200, Wesley W. Terpstra wrote:

> I've read that there was a recent change made to the buildd resolution with
> regards to ensuring that consistent package versions are used on the builds
> [0]. Is it possible that this changed also messed up self-dependency
> resolution?
> 
> My package, mlton, has a versioned dependency on itself for version >=
> 20070826. As it is a compiler for SML written in SML, it needs a previous
> version of itself installed in order to compile the new version. Previously,
> this has presented no problems; the buildd installed the old version and
> compiled the new version. Now, the buildd demands that the same version be
> installed as is to be built [1]:
> 
> *mlton/alpha dependency installability problem:*
> 
>   mlton (= 20100608-3) build-depends on one of:
>   - mlton (= 20100608-3)
> 
> ... this is, of course, impossible. The buildd must install the old version
> in order to build the new. I have a suspicion that an overzealous 'use the
> same version' rule in the dependency resolver might be the cause of this
> bug.
> 
As far as I can tell the problem is that you switched the mlton binary
package to 'Architecture: all'.  Which means it's available on all
architectures already in the new version, even though it's not
installable.

Cheers,
Julien