Displaying 2 results from an estimated 2 matches for "r71799".
Did you mean:
371799
2016 Dec 16
2
Upgrading a package to which other packages are LinkingTo
...r.
I've stumbled over this recently for A = Rcpp 0.12.8 and B = dplyr 0.5.0
[1], with a bug fix available in Rcpp 0.12.8.2. Simply upgrading Rcpp to
0.12.8.2 wasn't enough to propagate the bug fix to dplyr; we need to
reinstall dplyr 0.5.0 too.
I've prepared an example with R-devel r71799. The initial configuration
[2] is Rcpp 0.12.8 and dplyr 0.5.0. There is no warning from R after
upgrading Rcpp to 0.12.8.2 [3], and no warning when loading the (now
"broken") dplyr 0.5.0 linked against Rcpp 0.12.8 but importing Rcpp
0.12.8.2 [4].
As a remedy, I'd like to suggest...
2016 Dec 16
0
Upgrading a package to which other packages are LinkingTo
...over this recently for A = Rcpp 0.12.8 and B = dplyr 0.5.0
> [1], with a bug fix available in Rcpp 0.12.8.2. Simply upgrading Rcpp to
> 0.12.8.2 wasn't enough to propagate the bug fix to dplyr; we need to
> reinstall dplyr 0.5.0 too.
>
> I've prepared an example with R-devel r71799. The initial configuration
> [2] is Rcpp 0.12.8 and dplyr 0.5.0. There is no warning from R after
> upgrading Rcpp to 0.12.8.2 [3], and no warning when loading the (now
> "broken") dplyr 0.5.0 linked against Rcpp 0.12.8 but importing Rcpp
> 0.12.8.2 [4].
>
> As a remedy,...