Github user HyukjinKwon commented on the issue:

    https://github.com/apache/spark/pull/18856
  
    Ah, I meant, the PR I linked actually describes a case when we were using 
3.3.1 but it was broken after 3.3.2 release. The reason was, 3.3.2 was released 
but 3.3.2 for Windows was not synced (but was synced after few hours).
    
    The script we are using checks if it is latest or not and adds `../old/..` 
part to build the download link correctly. So..
    
    - Check given version is latest via https://rversions.r-pkg.org/r-release
      - If so, don't add `../old/..`, e.g., 
https://cran.r-project.org/bin/windows/base/R-3.3.1-win.exe
      - if not, add `../old/..`,  e.g., 
https://cran.r-project.org/bin/windows/base/old/3.3.1/R-3.3.1-win.exe
    
    But, the issue was, https://rversions.r-pkg.org/r-release gives 3.3.2 after 
the release but 3.3.1 for WIndows was not in old repo as the latest.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to