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

[Wesley W. Terpstra]

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.

Thanks for any help understanding why the buildd system will no longer
attempt to build my package!

[0] http://lists.debian.org/debian-policy/2011/03/msg00103.html
[1] https://buildd.debian.org/status/package.php?p=mlton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20110329/cc937635/attachment.htm>