On 2 April 2014 at 14:17, Julian Gilbey wrote: | On Tue, Apr 01, 2014 at 09:49:35PM -0500, Dirk Eddelbuettel wrote: | > | Actually, there's probably an even simpler solution: just have | > | fflags = $(shell dpkg-buildflags --get FFLAGS) | > | unconditionally. This result is no worse than the existing | > | debian/rules on wheezy, and will be better on jessie if the latest | > | dpkg-dev is used (which it will be on all of the autobuilders). | > | > I *finally* applied this yesterday. Thanks so much for prodding me to do this. | | Great, thanks!
Thank you. A big bunch. I used to be more responsive as a maintainer but I seen to more swamped these days... So thanks for your patience. | Now all that's left to do is the Provides: r-api-3.0 stuff ;-) I didn't like that discussion very much and still don't think it makes sense. Case in point: my littler package continues to work with R 3.0.* or R 3.1.*. There really is little breakage. But ... I just built the first r-cran-* package against the new setting and lintian still says: W: r-cran-slam: hardening-no-relro usr/lib/R/site-library/slam/libs/slam.so (Could be a side-effect on building in Debian chroot but running lintian 'outside' under <cough, cough> Ubuntu but I suspect it is legit.) Should we look into fixing the good old r-cran.mk so that hardening is on? (Part of me of course that R packages are probably not the common attack vector though...) Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
