On 10/28/2011 10:33 PM, Dirk Eddelbuettel wrote: > > The "Depends: r-base-core (>= minVersion), r-base-core (<< nextVersion) had > been tried in the past and rejected a few years ago: > > > rpy (1.0.0-1) unstable; urgency=low > > * New upstream release announced today > > * debian/control: Update Depends: on r-base-core to (>= 2.6.0) but remove > the (<< 2.7.0) so that rpy should not prevent R from entering testing > > -- Dirk Eddelbuettel <e...@debian.org> Mon, 19 Nov 2007 16:51:59 -0600 > > > What else can we do? > > Dirk > > breaking rpy is probably a valid reason to deny R to migrate to testing or for rpy to be removed from testing. But I think you will have to get in contact with the release team to hint the packages into testing together when ready each time.
How does rpy2 handle this? can't you just relax the version requirements in rpy and match up migrations with when rpy2 needs them? Or does the coupling go beyond api/abi compatibility?
signature.asc
Description: OpenPGP digital signature
