On 9 September 2017 at 14:12, Sébastien Villemot wrote: | On Sat, Sep 09, 2017 at 06:48:12AM -0500, Dirk Eddelbuettel wrote: | > | > On 9 September 2017 at 06:44, Niels Thykier wrote: | > | Thanks to Sébastien and Andreas for explaining the issue. | > | > Well, was it "explained" ? They both raised and stressed a hypothetical | > issue: That "there might be siutations where a partial upgrade breaks" | > | > We don't actually know whether this holds. This R 3.4.* change was not a | > full-fledged ABI change. | | I made the following experiment: | | - started from a minimal stretch chroot | - installed r-base and r-cran-spatial | - upgraded r-base to the version from sid (but not r-cran-spatial)
Come one. That's the situation of EVERY known bug in testing fixed in unstable. You explicitly chose to NOT get the fix, to then state it wasn't fixed. I am waiting for you to also enforce use of 'rm -i' over 'rm'. I am done. This way too dogmatic for my taste. I feel sorry about the users who will not get access to current, updated and bug free version of R because of this. A wrong decision. Dirk | - ran the example described in #861333: | | $ R -e "library(spatial); example(surf.gls)" | | then I get a crash with the error message "object 'VR_frset' not found". | | So this confirms that partial upgrades are indeed broken. | | Best, | | -- | ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot | ⣾⠁⢠⠒⠀⣿⡁ Debian Developer | ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name | ⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org | [DELETED ATTACHMENT signature.asc, application/pgp-signature] -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
