R CMD check issues this warning for #40 (see Travis CI log, but I doubt this has anything to do with the changes introduced in bcdf4ff.
Instead, I suspect a (package) update introduced a new conflict similar to the situtation in #36.
Another indication for this being introduced upstream is that the warning only comes up in the 'devel' R version test, not in the 'release' one.
R CMD checkissues this warning for #40 (see Travis CI log, but I doubt this has anything to do with the changes introduced in bcdf4ff.Instead, I suspect a (package) update introduced a new conflict similar to the situtation in #36.
Another indication for this being introduced upstream is that the warning only comes up in the 'devel' R version test, not in the 'release' one.