'CRAN package Rcpp' notice about rcpp

[eddelbuettel]

Rcpp 1.0.12 arrived at CRAN on Jan 9 as planned so this can be closed.

[kurthornik]

>>>> Dirk Eddelbuettel writes:

Thanks: yes I know, I had forgotten to tag my issue db accordingly. Best -k

…

CRAN / @kurthornik emails: Dear maintainer, Please see the problems shown on https://cran.r-project.org/web/checks/check_results_Rcpp.html. Please correct before 2024-01-10 to safely retain your package on CRAN. Note that this will be the final reminder. Best, -k which is of course redundant as we had been in contact ever since the -Wformat -Wformat-security wave broke. 'They know' we have a fixed 1.0.11.3 here, in the drat and at R-universe. Which, given no other currently known needs for change, I plan to relabel as 1.0.12 and ship once our regular bi-annual window opens in January. So January 8 it is per their winter break notice. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.*Message ID: <RcppCore/Rcpp ***@***.***>

[eddelbuettel]

@kurthornik No worries, it looked very much like the automated script and it was in fact timely -- I had promised 'early Jan' and it is now officially on the map.

[hadley]

FYI I'm seeing this in problem causing a check failure in odbc: https://www.stats.ox.ac.uk/pub/bdr/clang18/odbc.log so I'd appreciate it if you have time to get a fix to CRAN in the not too distant future.

[eddelbuettel]

Sure. First off the release happened yesterday a few days ago and second as you can see in the extended comments in #1287 (which i am sure you consulted) a number of packages made use of the provided pre-releases that have been available since November.