[R-pkg-devel] State of stringi and stringr
Thanks for clearing that up so quickly. Murray
From: Uwe Ligges <ligges at statistik.tu-dortmund.de>
Sent: 14 May 2021 13:12
To: Murray Efford; r-package-devel at r-project.org
Subject: Re: [R-pkg-devel] State of stringi and stringr
Sent: 14 May 2021 13:12
To: Murray Efford; r-package-devel at r-project.org
Subject: Re: [R-pkg-devel] State of stringi and stringr
On 14.05.2021 02:32, Murray Efford wrote: > CRAN checks of 'secr' 4.4.1 (https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcran.r-project.org%2Fpackage%3Dsecr&data=04%7C01%7Cmurray.efford%40otago.ac.nz%7C09a27360247948b3b76c08d916755da4%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637565515645165196%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fCVHjLUvJe%2FNFyERnO2S3onBe3skleZhgzsKS1NYNdk%3D&reserved=0) show an error on r-oldrel-windows-ix86+x86_64 : > > ** byte-compile and prepare package for lazy loading > Error in loadNamespace(i, c(lib.loc, .libPaths()), versionCheck = vI[[i]]) : > there is no package called 'stringi' > > 'secr' imports from 'stringr' that imports 'stringi', that was updated 10 May. 'secr' does not use 'stringi' directly. The error also appears on current CRAN tests of 'openCR' 2.0.1 with r-devel-windows-ix86+x86_64. > > Can I assume this is a transient problem and advise CRAN accordingly when I update my own package? Yes. Best, Uwe Ligges > > > > > ______________________________________________ > R-package-devel at r-project.org mailing list > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fr-package-devel&data=04%7C01%7Cmurray.efford%40otago.ac.nz%7C09a27360247948b3b76c08d916755da4%7C0225efc578fe4928b1579ef24809e9ba%7C1%7C0%7C637565515645165196%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=U5Mu4ZnlvZS%2FkKVrWrR02t9SU8mfy935qUcsJruf9fo%3D&reserved=0 >