-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
R release builds failing (3.3.0 "corrupted and unreadable") #68
Comments
looks like this is the same error as #62 |
That's probably me not updating rversions.r-pkg.org. I'll try to get to it today. |
https://github.com/krlmlr/r-appveyor/blob/master/scripts/appveyor-tool.ps1#L68-L74 for appveyor builds using https://cran.rstudio.com/bin/windows/base/release.htm of course you can use a different CRAN mirror if desired. |
@achubaty: I find parsing r-pkg.org easier than parsing the persistent CRAN link, I guess the latter requires some web scraping. I'd review a PR, though. |
@krlmlr sorry I should have been more clear. I meant to use the persistent link for the download. I'll take a closer look and see if a PR will make it clearer/cleaner. The goal is to ensure that release (and devel) always work, with fewer manual updates required. |
hmm I can't get this to work...I don't know PowerShell enough to know whether it is able to correctly resolve the redirect URL to get the .exe. |
@krlmlr Looks like you don't need to parse HTML, that link just redirects to the installer. |
I see it's using |
Contents of <html>
<head>
<META HTTP-EQUIV="Refresh" CONTENT="0; URL=R-3.3.1-win.exe">
<body></body> Doesn't seem like CURL can do it (but then I didn't really look into it): http://stackoverflow.com/a/32939779/946850 |
@gaborcsardi does r-pkg.org use a cronjob or similar to update the json for r-release and r-oldrel? something along these lines would reduce the manual updating you otherwise have to do. library(jsonlite)
library(rversions)
cat(toJSON(r_oldrel()), file = "r-oldrel.json")
cat(toJSON(r_release()), file = "r-release.json") |
Should be OK now, just updated it to 3.3.1. The reason for the manual update is that https://github.com/metacran/r-builder relies on it, so I have to make the new version available there. This will solve it: r-hub/rversions.app#2 I just need to remember implementing it before the next R release time..... |
Awesome, thanks! |
I guess this can be closed. Please comment or add a new issue if the problem persists. |
@krlmlr OK, so now we have the opposite problem. I am implementing r-hub/rversions.app#2 right now, FYI. |
OK, so I guess you can query http://rversions.r-pkg.org/r-release-win now. |
Thanks. Does it make sense to have http://rversions.r-pkg.org/r-oldrel-win, too? |
I think oldrel is fine. Older binaries are always available AFAICT. |
I am getting the same error. What should I do? Is my R directory corrupt or something?
|
@IndrajeetPatil: This problem looks like a duplicate of #112. |
I'm assuming this is a transient issue caused by the release of R 3.3.1 but I figure I should report it here anyway, in case an update is required on your end.
Thank you.
The text was updated successfully, but these errors were encountered: