[R-pkg-devel] CRAN incoming services and winbuilder down Mar 9-10

2018-03-08 Thread Uwe Ligges

Dear list,

due to a full power shutdown in the relevant building at TU Dortmund 
University we have to shut down winbuilder and the CRAN incoming check 
service from

Mar 9, 5pm CET
to
Mar 10, 5pm CET

Best,
Uwe Ligges
(CRAN team)

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


[R-pkg-devel] CRAN stable download url?

2018-03-08 Thread Jonathon Love

hi,

i'm bundling some R packages to go into a flatpak/flathub application. 
for that it is necessary to provide the download URLs for all the 
required dependencies in advance - including R packages. this works, 
*except* when an R package version transitions from being the current 
version, to being archived.


the current version will be, say:

https://cran.r-project.org/src/contrib/yaml_2.1.16.tar.gz

then when yaml 2.1.17 comes out (which it just has), that url will 
return a 404, and has become:


https://cran.r-project.org/src/contrib/Archive/yaml/yaml_2.1.16.tar.gz

this means everything breaks when a new version of an R package comes out.

does anyone know if a stable url exists for R packages?

with thanks

jonathon

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


Re: [R-pkg-devel] CRAN stable download url?

2018-03-08 Thread Zhian Kamvar
You might try using MRAN snapshots: 
https://mran.revolutionanalytics.com/documents/rro/reproducibility#standard 


For example:
https://cran.microsoft.com/snapshot/2018-01-01/src/contrib/yaml_2.1.16.tar.gz 


-
Zhian N. Kamvar, Ph. D.
Postdoctoral Researcher (Everhart Lab)
Department of Plant Pathology
University of Nebraska-Lincoln
ORCID: -0003-1458-7108




> On Mar 8, 2018, at 14:39 , Jonathon Love  wrote:
> 
> hi,
> 
> i'm bundling some R packages to go into a flatpak/flathub application. for 
> that it is necessary to provide the download URLs for all the required 
> dependencies in advance - including R packages. this works, *except* when an 
> R package version transitions from being the current version, to being 
> archived.
> 
> the current version will be, say:
> 
> https://cran.r-project.org/src/contrib/yaml_2.1.16.tar.gz
> 
> then when yaml 2.1.17 comes out (which it just has), that url will return a 
> 404, and has become:
> 
> https://cran.r-project.org/src/contrib/Archive/yaml/yaml_2.1.16.tar.gz
> 
> this means everything breaks when a new version of an R package comes out.
> 
> does anyone know if a stable url exists for R packages?
> 
> with thanks
> 
> jonathon
> 
> __
> R-package-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel



signature.asc
Description: Message signed with OpenPGP
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


Re: [R-pkg-devel] CRAN stable download url?

2018-03-08 Thread Henrik Bengtsson
On Thu, Mar 8, 2018 at 12:39 PM, Jonathon Love  wrote:
> hi,
>
> i'm bundling some R packages to go into a flatpak/flathub application. for
> that it is necessary to provide the download URLs for all the required
> dependencies in advance - including R packages. this works, *except* when an
> R package version transitions from being the current version, to being
> archived.
>
> the current version will be, say:
>
> https://cran.r-project.org/src/contrib/yaml_2.1.16.tar.gz
>
> then when yaml 2.1.17 comes out (which it just has), that url will return a
> 404, and has become:
>
> https://cran.r-project.org/src/contrib/Archive/yaml/yaml_2.1.16.tar.gz
>
> this means everything breaks when a new version of an R package comes out.
>

[Rd] CRAN indices out of whack (for at least macOS)


[Rd] CRAN indices out of whack (for at least macOS)

> does anyone know if a stable url exists for R packages?

Somewhat related: Winston Chang made the following argument in R-devel
thread 'CRAN indices out of whack (for at least macOS)' on 2018-02-03
(https://stat.ethz.ch/pipermail/r-devel/2018-February/075532.html):

> [...]
> One reason that package installations fail in these cases is that the
> current version of a package is in one directory, and the old
> (archived) versions of a package are in another directory. If current
> and old versions were in the same directory, then package installation
> would not fail.

An obvious, quick solution would be to also put the current version
under https://cran.r-project.org/src/contrib/Archive/ and link to it
but not sure how well that works with the CRAN mirroring setup.

/Henrik

>
> with thanks
>
> jonathon
>
> __
> R-package-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel