On 27 April 2017 at 12:49, Don Armstrong wrote: | Control: severity -1 serious | | Do we know if this issue may also mean that any packages built with this | new version are incompatible with older R versions? [I'm thinking so, | but my ABI-fu is not super strong.]
I don't know, and I tend not to run dated r-base-core packages. | If so, we'll need to make sure that they depend on at least this R | version. Is that what debian/control ensures? Ie from one of my most recent uploads: edd@max:~$ dpkg -f /var/cache/pbuilder/result/r-cran-foreign_0.8.68-1_amd64.deb | grep Depends Depends: libc6 (>= 2.14), r-base-core (>= 3.4.0-1), r-api-3 edd@max:~$ Pretty much ensure you cannot use this with R 3.3.* or older. | We also may need to populate a breaks with all of those packages which | have the older version. | | As a side note, it's really important not to start transitions like this | when we're in a freeze; this upload of R 3.4 should have been made to | experimental, not unstable. [Not that I can really point too many | fingers; I accidentally uploaded a new release of scowl to unstable | which I meant to target at experimental the other day...] I uploaded one beta build to experimental. Approximately nobody uses those. The 'blocking' mechanism really works. R 3.4.0 will not seep into testing. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
