You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In RTFACT-17392, Artifactory has a bug dealing with how CRAN archives. While that is indeed a bug, I have found in 3.5.1 install.packages, varying implementation of REMOTES, and/or versions of packrat, each package attempt to solve these varying implementations differently. Some need to reference a "archive.rds". Others must have a package.rds while others sufficiently use a PACKAGE file.
The ask and the associated PR is allowing the loosening of these restrictions to be backwards compatible. Remotes has a similar bug and PR
The text was updated successfully, but these errors were encountered:
The recent version of Connect which bundles a newer version of packrat exposed us to this issue as well. It would be great to either adapt the code from the linked PR or the linked renv solution to support this.
In the short term I have patched the vendored version of packrat for our use, but it would be great to avoid this workaround and use the one bundled with Connect.
In RTFACT-17392, Artifactory has a bug dealing with how CRAN archives. While that is indeed a bug, I have found in 3.5.1 install.packages, varying implementation of REMOTES, and/or versions of packrat, each package attempt to solve these varying implementations differently. Some need to reference a "archive.rds". Others must have a package.rds while others sufficiently use a PACKAGE file.
The ask and the associated PR is allowing the loosening of these restrictions to be backwards compatible. Remotes has a similar bug and PR
The text was updated successfully, but these errors were encountered: