Brilliant!
On Mon, Apr 14, 2025 at 22:49 谭显英 wrote:
> Thanks. I confirmed the issue has been resolved by following the
> instructions in your link.
>
> Regards,
>
> Xianying Tan (shrektan)
>
>
> Replied Message
> From Josiah Parry
> Date 04/15/20
Please update your Makevars template using the development version of
rextendr.
Please see:
https://github.com/extendr/extendr/releases/tag/extendr-api-v0.8.0
On Mon, Apr 14, 2025 at 18:59 谭显英 wrote:
> Dear R-devel list,
>
>
> I maintain two packages that use Rust code through the "extendr" lib
n log for
"Downloading crates." This could be easily circumvented on CRAN and locally
by suppressing stdout/err. But that would be adversarial and I would like
to adhere to the intent of the check.
On Mon, Mar 31, 2025 at 9:23 AM Duncan Murdoch
wrote:
> On 2025-03-31 11:50 a.m.,
t;
> > All the existing check-regulating env variables ...
> >
> > cd src/library/tools/R
> > grep 'Sys.getenv("_R_CHECK' * | sed -e 's/^.*Sys.getenv(//' | sed -e
> > 's/[,)].*//' | sort | uniq | wc
> >
> >
> > * should CRAN all
Well this has surely veered off course!
As the one who filed the BugZilla report, I'd like to redirect the
conversation and provide further context.
The question should be *"how do we get a dialogue started on this bugzilla
issue before the next minor *
*release of R?"*
The current check for Rus
Other people may be like me where R is the first programming language I
learned.
It took probably ~5/6 years or more to learn what “MD5” is and even longer
to understand what a checksum is and why they’re useful.
I think saying it _explicitly_ is helpful. Maybe saying that 1) the package
was ins
I’ve been guilty of this myself. I think a check would be good.
In my case I was using the new sort_by() function (I think also 4.1) and a
user was failing to install on R 4.0.
On Fri, Dec 13, 2024 at 11:30 Jan Netík wrote:
> Hello,
>
> I have a server with R 3.6.3 installed and I struggled a
Thank you, Tomas, for the clarification!
On Sun, Oct 13, 2024 at 14:59 Tomas Kalibera
wrote:
> On 10/13/24 19:30, Josiah Parry wrote:
> > Hi all,
> >
> > I'm new to contributing to r-devel. The trunk of r-devel right now
> includes
> > a `check_rust()` functi
Hi all,
I'm new to contributing to r-devel. The trunk of r-devel right now includes
a `check_rust()` function for adherence to CRAN's evolving rust policy (see
commit
https://github.com/r-devel/r-svn/commit/6114d4126434c056b476cbc5db2657536c153d9a
).
As it stands R 4.4.2 will codify CRAN policy o
I wouldn't go so far as to call people who don't want to wholesale attach
namespaces as "nuts."
{survival} is provided via the {censored} R package to integrate into the
{tidymodels} ecosystem.
And the reverse imports of the package is massive! Assuming that each and
every one of them
should attac
have been stabilized and begin working towards
remedying them? These WARNs come from R-devel which is, as its name
suggests,
a development version which is vacillating daily.
On Tue, Jun 25, 2024 at 12:10 PM wrote:
> On Tue, 25 Jun 2024, Josiah Parry wrote:
>
> > Hey folks,
> &g
Hey folks,
I'm sure many of you all woke to the same message I did: "Please correct
before 2024-07-09 to safely retain your package on CRAN" caused by Non-API
changes to CRAN.
This is quite unexpected as Luke Tierney's June 6th email writes (emphasis
mine):
"An *experimental* *effort* is underw
It looks like to me the class is being removed explicitly due to the use of
as.numeric()
On Sun, Jun 9, 2024 at 12:04 PM Spencer Graves
wrote:
> Hello, All:
>
>
> The 'head' and 'tail' functions strip the time from a 'ts'
> object.
> Example:
>
>
> > head(presidents)
> [1] NA 87 82 75
Hey Doug,
R is not a product that is provided by a company or any vendor that can be
procured through a vendor e.g. something on a GSA schedule.
Seems like you're caught in the bureaucracy hell hole. I used to help the
USAF, and other DoD members use R when I was at RStudio (now Posit).
I recomm
14 matches
Mail list logo
