new buildd dependency resolution breaks self depends?
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 . 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 :
mlton/alpha dependency installability problem:
mlton (= 20100608-3) build-depends on one of:... 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.
- mlton (= 20100608-3)
Thanks for any help understanding why the buildd system will no longer attempt to build my package!