On Tue, May 28, 2013 at 02:13:48PM +0100, Julian Gilbey wrote: > ** byte-compile and prepare package for lazy loading > Error : package ‘mgcv’ was built before R 3.0.0: please re-install it > > And sure enough: > > polya:~ $ rmadison r-cran-mgcv > r-cran-mgcv | 1.6-2-1 | squeeze | amd64, armel, i386, ia64, kfreebsd-amd64, > kfreebsd-i386, mips, mipsel, powerpc, s390, sparc > r-cran-mgcv | 1.7-13-1 | wheezy | amd64, armel, armhf, i386, ia64, > kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc > r-cran-mgcv | 1.7-13-1 | jessie | amd64, armel, armhf, i386, ia64, > kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc > r-cran-mgcv | 1.7-22-1 | sid | ia64 > r-cran-mgcv | 1.7-22-2 | sid | kfreebsd-amd64, kfreebsd-i386 > r-cran-mgcv | 1.7-23-1 | sid | amd64, armel, armhf, hurd-i386, i386, > mips, mipsel, powerpc, s390, s390x, sparc > > So because of the new version in sid, which didn't wait for the R > 3.0.0 migration to testing, the jessie version is still an R 2.7 > version :-( Had there been a "Provides: r-api-3.0" in r-base-core and > "Depends: r-api-2.7" in r-cran-mgcv, the transition would either have > been delayed or knowingly pushed though in spite of this, but the > breakage would have been caught at the time. (Then again, this might > have been the case anyway.)
(Sorry, I meant R 2.14 version or whatever the last binary incompatible version was.) <grumble> And I just tried backporting r-cran-mgcv to jessie, only to discover that the Build-Depends are overly strict; the package itself only requires R (>= 2.14.0). So it wouldn't build on jessie directly. Having this API thingy would remove the need for overly strict build-time dependencies and make back-porting simpler. </grumble> Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
