similar to: https://cran.r-project.org/src/base-prerelease/ is not updating

Displaying 20 results from an estimated 20000 matches similar to: "https://cran.r-project.org/src/base-prerelease/ is not updating"

2024 Aug 09
1
R-patched on CRAN is R-4.3.3
Thanks! So, to make sure I got this right, when the time of beta, alpha, RC comes, they'll also have a link called R-patched.tar.gz? Thanks again! Gabor On Fri, Aug 9, 2024 at 10:41?AM peter dalgaard <pdalgd at gmail.com> wrote: > > Exactly. I was in the process of getting the CRAN texts to point at base-prerelease, rather than Martin's versions i Zurich and decided that his
2024 Aug 09
1
R-patched on CRAN is R-4.3.3
Exactly. I was in the process of getting the CRAN texts to point at base-prerelease, rather than Martin's versions i Zurich and decided that his names were better than mine. "R-latest" makes better sense for the actual releases over in src/base. -pd > On 9 Aug 2024, at 10:33 , Ivan Krylov via R-devel <r-devel at r-project.org> wrote: > > ? Fri, 9 Aug 2024 10:28:19
2024 Aug 09
1
R-patched on CRAN is R-4.3.3
? Fri, 9 Aug 2024 10:28:19 +0200 G?bor Cs?rdi <csardi.gabor at gmail.com> ?????: > Possibly related to this, it seems that > https://cran.r-project.org/src/base-prerelease/R-latest.tar.gz > is not available any more. I think it's now R-patched.tar.?z: https://github.com/r-devel/r-dev-web/commit/8e146a769206924ec60ae08e2841910ac8e23083 -- Best regards, Ivan
2024 Aug 09
1
R-patched on CRAN is R-4.3.3
Possibly related to this, it seems that https://cran.r-project.org/src/base-prerelease/R-latest.tar.gz is not available any more. This file was very convenient, because it pointed to R-RC, R-beta, R-alpha or R-patched, as appropriate. Our nightly "next version of R" builds [1] depend on it. Do you think you can still create this file or link? Thank you, Gabor [1]
2023 Mar 19
0
CRAN 'R Sources' page: Provide link to https://svn.r-project.org/R/
Not sure who is the webadmin for https://cran.r-project.org/sources.html, so posting it here: I just noticed it's not straightforward to find the Subversion URL for the R source code. A natural search would be to go to https://cran.r-project.org/, then click 'Source code' to get to https://cran.r-project.org/sources.html. That page does mention "Subversion tree", but it
2020 Jun 09
0
r-project.org SSL certificate issues
To be clear, this not an issue in the libraries nor R, the certificates on the server were simply wrong. So, no, this has nothing to do with R. Cheers, Simon > On Jun 10, 2020, at 10:45 AM, Henrik Bengtsson <henrik.bengtsson at gmail.com> wrote: > > Was this resolved upstream or is this something that R should/could > fix? If the latter, could this also go into the
2020 May 31
0
r-project.org SSL certificate issues
Btw. it would be also possible to create a macOS R installer that embeds a static or dynamic libcurl with Secure Transport, instead of the Apple default LibreSSL. This might be too late for R 4.0.1, I don't know. Gabor On Sun, May 31, 2020 at 4:09 PM G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > > On Sat, May 30, 2020 at 11:32 PM G?bor Cs?rdi <csardi.gabor at
2020 Jun 09
2
r-project.org SSL certificate issues
Was this resolved upstream or is this something that R should/could fix? If the latter, could this also go into the "emergency release" R 4.0.2 that is scheduled for 2020-06-22? My $.02 /Henrik On Sun, May 31, 2020 at 8:13 AM G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > > Btw. it would be also possible to create a macOS R installer that > embeds a static or
2020 Jun 09
0
r-project.org SSL certificate issues
You are making a very strong assumption that finding an alternative chain of trust is safe. I'd argue it's not - it means that an adversary could manipulate the chain in a way to trust it instead of the declared chain and thus subverting it. In fact switching to OpenSSL would create a serious security hole here - in particular since it installs a separate trust store which it is far more
2020 May 31
2
r-project.org SSL certificate issues
On Sat, May 30, 2020 at 11:32 PM G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: [...] > Btw. why does this affect openssl? That root cert was published in > 2010, surely openssl should know about it? Maybe libcurl / openssl > only uses the chain provided by the server? Without trying to use an > alternate chain? Yes, indeed it seems that old OpenSSL versions cannot handle
2020 Jun 10
0
r-project.org SSL certificate issues
My (also not expert) understanding is that there is nothing insecure about alternative certificate chains at all. All browsers and macOS's built in SSL library (secure transport) support them properly. OpenSSL and LibreSSL were/are simply broken. This was not such a big issue so far, but now that some old long lived certificates are expiring, it is increasingly an issue. FWIW it is possible
2020 Aug 19
1
r-project.org SSL certificate issues
Hi win-builder certificate expired on Aug 15. My student on the other side of the world is also seeing this problem so I think it needs to be fixed... > download.file("https://win-builder.r-project.org", "/tmp/wb.html") trying URL 'https://win-builder.r-project.org' Error in download.file("https://win-builder.r-project.org", "/tmp/wb.html") :
2003 Sep 14
2
4.9-20030914-PRERELEASE hangs during boot
I just noticed the 4.9-20030914-PRERELEASE and made a set of installation boot floppies from it to see which of the devices in my new PC the PRERELEASE would support. It wedged hard during the boot autoconfiguration monologue, just after typing these lines on the console: atapci0: <Intel ICH5 ATA100 controller> port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0 ata0:
2020 May 30
0
r-project.org SSL certificate issues
Odd. Safari has no problem and says certificate expires August 16 2020, but I also see the download.file issue with 4.0.1 beta: > download.file("https://www.r-project.org", tempfile()) trying URL 'https://www.r-project.org' Error in download.file("https://www.r-project.org", tempfile()) : cannot open URL 'https://www.r-project.org' In addition: Warning
2008 Jan 26
0
[LLVMdev] 2.2 Prerelease available for testing
My test results for the LLVM 2.2 prerelease. === Q. Target === * Mac OS X 10.4.11 * 2 GHz Intel Core 2 Duo * MacBook % uname -a Darwin macbook.local 8.11.1 Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386 === Q. How you built the release === * objDir != srcDir * Release build * llvm-gcc-4.2 from source
2020 Jun 09
3
r-project.org SSL certificate issues
Yes and no... At least as I understand it (Disclaimer: There are things I am pretty sure that I don't understand properly, somewhere in the Bermuda triangle beween CA bundles, TLS protocols, and Server-side settings), there are two sided to this: One is that various *.r-project.org servers got hit by a fumble where a higher-up certificate in the chain of trust expired before the
2020 May 30
0
r-project.org SSL certificate issues
# A tibble: 13 x 1 site <chr> 1 beta.r-project.org 2 bugs.r-project.org 3 cran-archive.r-project.org 4 cran.r-project.org 5 developer.r-project.org 6 ess.r-project.org 7 ftp.cran.r-project.org 8 journal.r-project.org 9 r-project.org 10 svn.r-project.org 11 user2011.r-project.org 12 www.cran.r-project.org 13 www.r-project.org is the whole list b/c of the wildcard cert. On
2006 May 25
2
mongrel_cluster 0.1.3 prerelease
Hi y''all, A prerelease of mongrel_cluster 0.1.3 is available for testing with the Mongrel 0.3.13 prerelease. This release contains bug fixes and adds a Ruby script for managing all applications on a server with a single command. To install: gem install mongrel_cluster --source=http:// railsmachine.rubyforge.org/releases/ Changes: * Suppress output from mongrel_rails. * Added a
2006 Mar 22
0
6.1 Prerelease, USB-to-IDE problem
Hello! FreeBSD tarkhil.titl.ru 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #5: Tue Mar 14 14:58:53 MSK 2006 root@tarkhil.titl.ru:/usr/obj/usr/src/sys/ARMADA i386 encountered problems with USB-to-IDE box and NEC CD-RW/DVD drive. Controller /dev/usb3: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), NEC(0x0000), rev 1.00 port 1 powered port 2 addr 2: high speed, self powered,
2008 Jan 31
0
[LLVMdev] 2.2 Prerelease available for testing
Dear Tanya: > You also have a few CBE failures that I am not seeing. What version > of xcode do you have installed? Xcode 2.4.1 > Can you send me the following files? > SingleSource/Regression/C/Output/2008-01-07-LongDouble.* > SingleSource/Regression/C/Output/PR1386.* OK, I attached those files (llvm-2.2-test-output.tar.gz) Best regards, 2008/1/30, Tanya Lattner <tonic at