age_db(), Deadline[Package %in% c('parzer',
'flightsbr')]) should have been returning non-NA values) in the month
that passed. Having a number of packages archived due to a silent
problem with mail delivery is very unfortunate.
--
Best regards,
Ivan
_
On Fri, 11 Jul 2025 18:50:44 +
Daniel Kelley wrote:
> My concern is with the last test, i.e. on system
>
> R version 4.4.3 (2025-02-28 ucrt)
>
> It produces one NOTE. Looking into this, I see the following in the
> 00check.log file:
>
> * checking DESCRIPTION m
to the package for the resubmission, put the
explanation about the R scripts under tools/ being required by the
configure script to operate on the current directory in the submission
comment.
If you want to be extra sure, you can try experimenting with a
container or a virtual machine:
find
>>> Dear All,
>>>
>>> I submitted a new package ("ironseed") [1] to CRAN. I am not sure how
>>> to address one feedback message or even what is causing it. It might
>>> be related to Kevin Ushey's R scripts that I am using to configure t
l 5, 2025, at 2:12 PM, Reed A. Cartwright wrote:
>
> Dear All,
>
> I submitted a new package ("ironseed") [1] to CRAN. I am not sure how
> to address one feedback message or even what is causing it. It might
> be related to Kevin Ushey's R scripts that I am usi
r use with
.Call() (see the info in ape::seq_root2tip). So you can import it and
use is as seq_root2tip or use it as ape::seq_root2tip.
Best,
luke
From: Duncan Murdoch
Date: Thursday, July 3, 2025 at 4:13 PM
To: Sharon Bewick , r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Two e
rt it and
use is as seq_root2tip or use it as ape::seq_root2tip.
Best,
luke
From: Duncan Murdoch
Date: Thursday, July 3, 2025 at 4:13 PM
To: Sharon Bewick , r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Two errors
This Message Is From An External Sender: Use caution when opening
В Sun, 29 Jun 2025 13:56:36 +0800
Shu Fai Cheung пишет:
> An R-CMD-check action on an old release of R, conducted by GitHub
> action, failed, because Package C depends on R 4.5.0. However, I found
> that several other packages that import Package C, including Package
> B, do not req
s,
Ivan
[1]
https://win-builder.r-project.org/incoming_pretest/Mega2R_1.2.0_20250620_214524/specialChecks/gcc-san/summary.txt
[2]
https://sqlite.org/forum/forumpost/311dbf9a1cadfae6
______
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
re.R and so should have
the same PATH, it should be safe to tell CMake only the name of the
compiler, without Sys.which() or normalizePath().
--
Best regards,
Ivan
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
e our primary identifier?
> >
> >2.
> > If updating multiple packages with a new maintainer email account, is
> there a "best way" to do this to avoid sending CRAN 20-something unique
> emails and wasting their time each time?
> >
> > For what it
В Sun, 8 Jun 2025 22:24:11 +
Wayne Oldford пишет:
> As I understand it, the problem appears to be that package testing
> under Unix uses an R built with Tcl/Tk version 9.0.1
<...>
> I think I have excised the version number 8.6 everywhere in the
> package and am only askin
igible.
--
Best regards,
Ivan
______
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
From: Dirk Eddelbuettel
Sent: Wednesday, 4 June 2025 02:33
To: Greg Hunt
Cc: Dirk Eddelbuettel ; Murray Efford
; R Package Development
Subject: Re: [R-pkg-devel] Check time > 10min
Greg,
On 4 June 2025 at 00:19, Greg Hunt wrote:
| In the original email, there was t
ng about finding the exact problem before.
Generally, R CMD check will produce a NOTE if it sees you disabling a
compiler warning, but the compiler is in the wrong here, and a NOTE is
better than a WARNING. Still, it's best to have a package pass R CMD
check without even NOTEs because those don&#
Yes, that run is the problem. There is an attachment from CRAN-pretest with
this NOTE that I take to be the issue:
Flavor: r-devel-windows-x86_64
Check: *, Result: NA
Flavor: r-devel-windows-x86_64
Check: Overall checktime, Result: NOTE
Overall checktime 13 min > 10 min
Flavor: r-devel-li
ay, 3 June 2025 12:54
To: Murray Efford
Cc: R Package Development
Subject: Re: [R-pkg-devel] Check time > 10min
On 3 June 2025 at 00:12, Murray Efford via R-package-devel wrote:
| My revision of package 'secr' fails CRAN pre-test on Windows (R 4.5.0)
because total check time exceed
My revision of package 'secr' fails CRAN pre-test on Windows (R 4.5.0) because
total check time exceeds 10 min (it's 760 seconds or 13 min). I can't see how
to fix this as none of the times listed in the log
https://win-builder.r-project.org/incoming_pretest/secr_5.2.2_202
If this were the case I don't think that I'd be having problems replicating it.
From: Serguei Sokol
Sent: Wednesday, May 21, 2025 9:21 AM
To: and...@robbinsa.me ; R Package Development
Subject: Re: [R-pkg-devel] gcc-asan replication for
both my shared object and the Rcpp binding
library-which seems like something that shouldn't be raising any issues.
Dirk, you wouldn't happen to have seen this before?
-Andrew Robbins
__
R-package-devel@r-project.org mailing list
https
increased coverage as an additional argument when resubmitting. After
all, tests are code and thus may also contain bugs, and sometimes it's
the right choice to remove the buggy code.
--
Best regards,
Ivan
__
R-package-devel@r-project.org mailing li
On Sat, 10 May 2025 16:48:16 +0200
Lorenzo Sostero wrote:
> Flavor: r-devel-windows-x86_64
> Check: tests, Result: ERROR
> Running 'testthat.R'
> Running the tests in 'tests/testthat.R' failed.
> Complete output:
> > library(testthat)
>
s and pass them through. Such
"impossible" errors could be signs of a protection error. (Well, any
memory corruption, but arbitrary memory corruption is harder to
diagnose, so let's hope it's something to do with the garbage
collector.) Let's run the test suite check using a bu
m on your end by making
sure that all values in your adjacency matrices are finite before
calling igraph::graph.adjacency().
To see the problem for yourself, you'll need a "sanitized" build of R:
https://cran.r-project.org/doc/manuals/R-exts.html#Using-Undefined-Behaviour-Sanitizer
San
В Wed, 7 May 2025 20:10:50 + (UTC)
Mat Fok via R-package-devel пишет:
> I want to be able to click "Run Examples" in my Help documentation
> but I get the error /Example/olr not found.
> I have searched online for this but the most relevant thing I have
> found w
hould have a folder called
Example, but ChatGPT said no. I have searched online for this but the most
relevant thing I have found was
stackoverflow.com/questions/76365640/r-roxygen-examples-example-foo-bar-not-found,
but no one answered and it is over a year old.
|
|
|
| | |
|
|
ry and link it into the package
shared library. Otherwise you'll need to arrange for the gecode
shared libraries to be installed together with the R package and
properly loaded before your package shared library.
- Provide a 'clean' target so that R CMD build doesn't include
> don't want to modify base::letters.
The situation is more dangerous than that. When 'x' references the same
object as base::letters (which is a locked binding), you can still
modify this object from C code, given its SEXP address, and see the
changes from either binding; R won&#
В Sun, 13 Apr 2025 21:54:03 -0700 (PDT)
adi...@pdx.edu пишет:
> Package has help file(s) containing install/render-stage \Sexpr{}
> expressions but no prebuilt PDF manual.
This is a relatively recent change (r85348, October 2023). Previously,
R CMD build detected non-build-time dynamic c
CRAN checks.
Nowadays, R CMD check --as-cran does run \donttest{} examples. (But not
without --as-cran or --run-donttest, and no automatic checks enable
--run-dontrun.)
> Examples with CPU (user + system) or elapsed time > 5s
>
В Mon, 14 Apr 2025 08:57:49 +0200
Emanuele Cordano пишет:
> R CMD check --as-cran on my machine did not help.
Strange, it should be doing the same thing as 'urlchecker'. I've tried
it with an old version of 'RMAWGEN' and saw the messages:
>> * checking CRAN
В Fri, 11 Apr 2025 16:00:16 +
"Killick, Rebecca" пишет:
> All of the \link uses within my package are anchored except for the
> \linkS4class{cpt} call so I think this is what it is referring to.
> I've checked the writing R extensions "Cross-references"
В Thu, 10 Apr 2025 11:24:31 +0200
Emanuele Cordano пишет:
> Is there an option in R CMD check that I can use on
> my server to directly verify all URLs
Does R CMD check --as-cran help?
--
Best regards,
Ivan
__
R-package-devel@r-project.org m
going to have a significantly longer stable lifetime than the NCBI URL.
So, for now at least, I think I will leave them both.
Best,
Kevin
On 4/7/2025 11:35 AM, Ivan Krylov wrote:
В Mon, 7 Apr 2025 11:10:21 -0400
"Kevin R. Coombes" пишет:
But version R 4.5.0 RC comes back with;
В Mon, 7 Apr 2025 11:10:21 -0400
"Kevin R. Coombes" пишет:
> But version R 4.5.0 RC comes back with;
> (possibly) invalid URL. Status: 403 Message: Forbidden
> I copied the URL as reported in the error message, pasted it into my
> browser, and it worked just fine.
Hi,
I am systematically going through the packages that I maintain on CRAN
to clean up some administrative details. Specifically, I am (1) changing
all DESCRIPTION files to use Authirs@R, (2) updating the links in man
files to include package anchors, and (3) making sure that the output of
; DOIs, though i did not get it on any previous check:
>
> Checking URLs failed with message:
> there is no package called 'curl'
>
> Checking DOIs failed with message:
> there is no package called 'curl'
Looks like Win-Builder for R-devel is having transient p
uding checks for repository content) or
_R_CHECK_CRAN_INCOMING_SKIP_URL_CHECKS_IF_REMOTE_=TRUE to only skip the
URL checks.
--
Best regards,
Ivan
[*]
https://cran.r-project.org/doc/manuals/r-devel/R-ints.html#index-_005fR_005fCHECK_005fCRAN_005fINCOMING
If it is *only *in sysdata.Rda, then it is accessible to your package
code but is not available to users. (They can't, for example, use the
"data" function to load it themselves.) So, there is no reason to
document it. Just like there is no reason to document functions in your
Did you seriously look for instructions and not find [1]? And why do you think
the answer should not involve Rd files? Documentation in R packages is what Rd
files are for.
If you don't want to mess with Rd files then you have no choice but to use
something like the Roxygen package to
[[alternative HTML version deleted]]
______
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
gt;
> Best,>
> Uwe Ligges
Thanks Uwe, I'll reduce further -- looks like there's a test runtime variance
of a few minutes I need to account for.Best Regards,Mark
[[alternative HTML version deleted]]
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
В Mon, 17 Mar 2025 13:38:50 + (UTC)
Mark Webster пишет:
> > Flavor: r-devel-windows-x86_64
> > Check: Overall checktime, Result: NOTE
> > Overall checktime 12 min > 10 min
I think you'll have to reduce the test datasets further:
https://win-builder.r-pr
Hi Michael and Ivan,
> Could you please share a link to the check results? If it's>
<https://win-builder.r-project.org/incoming_pretest/autodb_2.3.0_20250316_203825/>,
> it seems to have passed the R CMD check. As Michael says, the NOTE
> about the package being a new
В Sun, 16 Mar 2025 22:06:16 + (UTC)
Mark Webster via R-package-devel пишет:
> I'm getting a NOTE on winbuilder, which doesn't come with much
> information:
> Build log:
> * using log directory
> 'd:/RCompile/CRANguest/R-devel/autodb.Rcheck'
> >
Hello,
I'm getting a NOTE on winbuilder, which doesn't come with much information:
Build log:> * using log directory 'd:/RCompile/CRANguest/R-devel/autodb.Rcheck'
> * using R version 4.5.0 alpha (2025-03-15 r87978 ucrt)
> * using platform: x86_64-w64-mingw32
> *
: 3AD40 | Email:
mccrowey.clin...@epa.gov | Phone: 215-814-2157 | Fax: 215-814-2124
-Original Message-
From: R-package-devel On Behalf Of Ivan
Krylov via R-package-devel
Sent: Wednesday, February 26, 2025 6:50 AM
Cc: r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] How do you make
lp to use if (reticulate::py_module_available(...)) { ... }
instead of \donttest{...} in your examples?
https://cran.r-project.org/web/packages/reticulate/vignettes/package.html#checking-and-testing-on-cran
--
Best regards,
Ivan
______
R-package-devel@r-project
(As they shouldn't. If there was still a match, it would be much harder
to explain as a checksum collision.)
--
Best regards,
Ivan
______
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
ne match:
https://www.virustotal.com/gui/url/f8d4551cce926dbe1ca4ade853038e9b358a65ce06e448f83825247df0c9f375
> Can you translate that tip into an actionable `sed` (or, of course
> `Rscript` or `r`) expression I could add to the Makefile?
It's probably doable with `sed`, but her
or finding a
comment that can be changed. For example, (La)TeX-produced vignettes
sometimes contain a comment that says charToRaw('PTEX') |> as.integer()
|> bitwXor(0x80) |> as.raw(), and these four bytes can be replaced by
four spaces.
--
Best regards,
Ivan
[*] https://stat.
Dear Han Zhang,
Welcome to R-package-devel!
В Mon, 17 Feb 2025 23:28:24 -0500
Han Zhang пишет:
> Found the following
> HTML validation problems: GraphicalTesting.html:114:1
> (GraphicalTesting.Rd:170): Warning: attribute "id" has invalid
> value "method-Graphical Te
fgang
From: Ivan Krylov
Sent: Monday, February 17, 2025 8:05 AM
To: Wolfgang Rolke via R-package-devel
Cc: Wolfgang Rolke
Subject: Re: [R-pkg-devel] GPU programming in R packages
� Sun, 16 Feb 2025 13:00:55 +
Wolfgang Rolke via R-package-devel
�:
> I am c
В Sun, 16 Feb 2025 13:00:55 +
Wolfgang Rolke via R-package-devel
пишет:
> I am currently working on a project that requires calculations on
> large matrices, for example calculating pairwise distances of points
> in higher dimensions.
How large are the matrices? Are CPU-side cal
nline and found
that a number of R packages such as rput are no longer available on CRAN, so I
suppose I shouldn't use those. So my question is, how should I implement a GPU
based calculation in a package that will eventually be acceptable for CRAN?
Any hints are appreciated!
Dear Stephen Abrams,
Welcome to R-package-devel!
В Thu, 13 Feb 2025 22:20:50 -0500
Stephen Abrams пишет:
> A secondary worry is that even if I resolve this, there might be
> something else causing threads to spin up.
Instead of using detectCores() [*] and creating cluster objects
yo
ackage = new(MyPackage)
>>
>> Then, if necessary, the user could change the dataset used with something
>> like:
>> mypackage.dataset("2.1.0") which would retrieve new csv files if they
>> haven't already been downloaded and update the data_folder path inte
Browse[1]> BaseSet::tidy
function (object)
{
UseMethod("tidy")
}
...and the method is registered for the BaseSet::tidy generic, not the
generics::tidy generic:
Browse[1]> 'tidy.GeneSet' %in% ls(BaseSet:::.__S3MethodsTable__.)
[1] TRUE
Browse[1]> 'ti
В Fri, 7 Feb 2025 06:51:27 +
KABILAN S пишет:
> > result <- TRANSFORMER(df = S_P_500_Close_data, study_variable =
> > "Price")
> Error: Valid installation of TensorFlow not found.
>
> Python environments searched for 'tensorflow' packag
to be called by their full names.
Removing these lines and re-generating NAMESPACE should help:
https://github.com/thibautjombart/adegenet/blob/e4874e73f0d39ebdddeca05b7eb1359fab771aaf/R/basicMethods.R#L546
https://github.com/thibautjombart/adegenet/blob/e4874e73f0d39ebdddeca05b7eb1359fab77
That was clear to me, and changes nothing about my comments.
On February 4, 2025 3:27:34 PM PST, Josiah Parry wrote:
>The file was written using writeLines() but it is just a normal R script
>with normal function definitions and is included in the R/ directory. The
>source cod
code from generated
files, then maybe you should use textConnection to run from internal RAM.
On February 4, 2025 1:11:10 PM PST, Josiah Parry wrote:
>I'm running R CMD check for my package {calcite} (source:
>https://github.com/r-arcGIS/calcite) which is failing due to what *looks* l
lements [1]. Every byte must be unpacked into 8 bits, and
199 is less than 26*8 = 208. Where did the values come from?
The C function GLsumFreq() stores them unchanged from its arguments
[2], and those come from the SNPbin objects passed by R code [3] from
nLoc(x) and length(x$gen[[1]]@snp[[1]]).
Thanks for the quick (detailed) response.
On 1/31/2025 12:23 PM, Martin Maechler wrote:
Kevin R Coombes
on Fri, 31 Jan 2025 11:48:33 -0500 writes:
> Hi,
> I have a package that has been in CRAN for years and is now failing
> checks because some of the output
uot;summary" to
hide the differences). the only one that remains yields this R CMD check
report:
Comparing ‘testDiff.Rout’ to ‘testDiff.Rout.save’ ...52c52
< 2.600e-06 1.328e-01 4.666e-01 1.060e+00 1.369e+00 1.091e+01
---
> 0.03 0.132800 0.466600 1.06 1.369000 10.91000
not being able
to find this function. For details see
https://github.com/r-hub2/productive-joking-manatee-Rgof/actions
[https://opengraph.githubassets.com/b40e189207ca774a60d2c41f7b3410850dddf9a6816238d771e042279edbac03/r-hub2/productive-joking-manatee-Rgof]<https://github.com/r-hub2/product
Dear Zahra Heidari Ghahfarrokhi,
Welcome to R-package-devel!
В Tue, 28 Jan 2025 18:17:06 +0330
zahra heidari gh пишет:
>- Additional details:
> - The package FD is used during package building.
> - In a previous post on the r-h...@r-project.org mailing list,
> I
tions(numThreads = 1)
> }
This is not a good idea. First of all, the OpenMP standard requires
the changes done by Sys.setenv(OMP_NUM_THREADS=...) calls after the R
process is started to be ignored; they will only take effect for newly
created child processes (e.g. system() calls). Secondly, if a u
kages uploaded
later (and then regularly deleted). Perhaps last time 'survival' was
uploaded on Win-Builder, something went wrong with the package.
If the problem doesn't go away by itself, it may be worth asking Dr.
Uwe Ligges for advice.
--
Best regards,
Ivan
В Tue, 28 Jan 2025 14:25:23 +0100
John Clarke пишет:
> I'm wondering if there is a way to point an R package installer to a
> pre-compiled release on Github rather than rely on CRAN.
>From the point of view of install.packages(), a repository is a
collection of package files plus
Dear Guillermo,
Welcome to R-package-devel!
В Mon, 27 Jan 2025 19:26:10 +0100
Guillermo Vinue пишет:
> I am writing to you because I am getting this NOTE from the CRAN
> Debian machine that is not allowing CRAN acceptance: "Installation
> took CPU time 2.9 times elapsed time&quo
В Sat, 25 Jan 2025 08:54:45 -0800
Balasubramanian Narasimhan пишет:
> (https://github.com/blas-lapack-rs/r-src/blob/966266425b1a21a1e979f767c6023e6bf00616fc/build.rs#L160).
>
Thank you for providing the link to the code!
> The only thing I can think of is that FLIBS is being se
Yes, that fixed it. My package was quickly re-tested and is now on CRAN. Thanks
to all.
Murray
From: Kevin Ushey
Sent: Friday, 24 January 2025 15:10
To: Murray Efford
Cc: R-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Pre-test failure with
alled ... ERROR Installation
failed. See 'd:/RCompile/CRANincoming/R-devel/secr.Rcheck/00install.out' for
details.
which includes
undefined reference to `RcppParallel::tbbParallelFor(unsigned long long,
unsigned long long, RcppParallel::Worker&, unsigned long long, int)'
Winbuild
es this API for saving and checking ABI versions be useful to
anyone?
Best,
Pavel
On Sun, 2025-01-19 at 05:31 +, Pavel Krivitsky via R-package-devel
wrote:
> Thanks, Ivan! Replies below.
>
> On Fri, 2025-01-17 at 16:50
further updates to the tracked commit pointer must be applied with git
submodule update. If the referenced repository becomes unavailable, it
will be impossible to build the package.
--
Best regards,
Ivan
______
R-package-devel@r-project.org mailing lis
, but got swamped. If the
compiler flags are right, $CXX -c conftest.cpp will succeed the same way
that the individual object files currently successfully compile on
Fedora-clang [1]:
>> /usr/local/clang19/bin/clang++ -stdlib=libc++ -std=gnu++17
>> -I"/data/gannet/ripley/R/R-clang/includ
В Sun, 19 Jan 2025 17:07:51 +
Pepijn de Vries пишет:
> He also mentioned that I "need to check in your configure script that
> the external library you need is available *and* usable with the
> compilers used to compile R and packages."
The Fedora-clang test fails with a
Thanks, Ivan! Replies below.
On Fri, 2025-01-17 at 16:50 +0300, Ivan Krylov wrote:
> В Fri, 17 Jan 2025 10:21:27 +
> Pavel Krivitsky via R-package-devel
> пишет:
>
> > 1. What is the best way to save this information? I have a
> > rudimentary implementatio
В Fri, 17 Jan 2025 10:21:27 +
Pavel Krivitsky via R-package-devel
пишет:
>1. What is the best way to save this information? I have a
> rudimentary implementation [1]
For now, this is the best way we have. Export the ABI version as an
include-time constant and as a regi
#x27; precisely
in order to test the exported C API. As
https://cloud.r-project.org/doc/manuals/r-devel/R-exts.html#Linking-to-native-routines-in-other-packages
suggests, LinkingTo packages should either depend on an exact version
(which is impractical) or test whether the version matches at runt
nt: Wednesday, January 15, 2025 12:34 PM
To: Iris Simmons
Cc: Merlise Clyde, Ph.D. ; List r-package-devel
Subject: Re: [External] Re: [R-pkg-devel] Replacement for SETLENGTH
On Wed, 15 Jan 2025, Iris Simmons wrote:
I don't think memcpy works well for VECSXP. The elements being overwr
ckage too being approved if
you reply-all and explain the situation.
--
Best regards,
Ivan
__________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
ALTREP [1]. It's a lot of typing because the code will need to
register an ALTREP class for every vector type that needs to be
shrinkable. Moreover, since some of those vectors are of type VECSXP
and "altlist" classes only appeared in R-4.3.0, you will probably
prefer to leave
GTH. There's an example here:
https://github.com/wch/r-source/blob/744b5d34e1b8eb839e5d49d91ab21c1fe6800856/src/main/subassign.c#L257
The example uses SET_STDVEC_LENGTH which shouldn't be used, just replace it
with SETLENGTH.
So in your code, I'd replace:
SETLENGTH(modelspace, nUn
lready in place (see the AC_SEARCH_LIBS paragraph
> above). But my explanation gets ignored.
I'm sorry for asking this admittedly thick question, but are you sure
it's not just R CMD check --as-cran repeating the X-CRAN-Comment: field
(which includes the phrase about not testing for single
В Fri, 10 Jan 2025 07:45:00 -0700
Kent Riemondy пишет:
> cleancall.c:110:46: runtime error: call to function cb_progress_done
> through pointer to incorrect function type 'void (*)(void *)'
This is a (mostly harmless) error in the purrr package:
https://stat.ethz.ch/pipermail
the
similarly named component of the blood instead.
Is there any simple way (that won't burden or confuse the CRAN
maintainers excessively) to make this change?
Thanks,
Kevin
__________
R-package-devel@r-project.org mailing list
https://stat.ethz.c
В Fri, 20 Dec 2024 11:30:04 +0300
Ivan Krylov via R-package-devel пишет:
> Unfortunately, it's still a puzzle why the function
> tesseract::TessBaseAPI::GetVariableAsString(char const*, std::string*)
> const fails to load from libtesseract.
That's because libtesserac
String(char const*, std::string*)
const fails to load from libtesseract.
--
Best regards,
Ivan
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
Hi All:
r-hub has changed the way that it works. Now you need Github, plus it writes
things to your Github repo. I do not understand what it writes, I am always
loath to add anything to a repo I don't understand, and I wonder if it
conflicts in any way with existing Github actions
В Tue, 17 Dec 2024 20:26:01 +0100
David Cortes пишет:
> I am seeing a curious error in an ASAN package check which is not
> reproducible in the r-debug containers
> (https://github.com/wch/r-debug), and which I'm suspecting might be a
> compiler bug.
r-debug differs from the
Dear Aixiang,
Welcome to R-package-devel!
В Tue, 17 Dec 2024 09:47:26 +
Aixiang Jiang пишет:
> I am really confused by the error, which did not happen in the
> previous versions.
>
> Since I have not changed my code at all, the possible reason is that
> the external func
ring incoming checks with ASan?
--
Best regards,
Ivan
[1]
https://developers.redhat.com/blog/2019/03/13/understanding-gcc-warnings-part-2
[2]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117881
[3]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108939
_______
and GCC stops being
able to prove that truncation occurs. It looks like you will either
need to find a container with R pre-built with sanitizers enabled (are
there Rocker containers for aarch64?) or build R yourself [*].
--
Best regards,
Ivan
[*]
https://cran.r-project.org/doc/manuals/R-e
ing the string:
https://gcc.gnu.org/onlinedocs/gcc-14.2.0/gcc/Warning-Options.html#index-Wstringop-truncation
strncpy(trunc_s1, s1, sizeof trunc_s1 - 1);
trunc_s1[sizeof trunc_s1 - 1] = '\0';
--
Best regards,
Ivan
______
R-package-devel@r
It is clear. Thank you very much.
Thang
-Original Message-
From: R-package-devel On Behalf Of
r-package-devel-requ...@r-project.org
Sent: Wednesday, November 27, 2024 12:00 PM
To: r-package-devel@r-project.org
Subject: R-package-devel Digest, Vol 115, Issue 19
Send R-package-devel
e libarrow look like?
Thank you & best regards,
Thang
__
AmsterdamUMC disclaimer : www.amsterdamumc.org/nl/disclaimers.htm
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mail
seems this could be ignored. Is it so?
Yes. It's for the CRAN maintainers to perform a manual review of the
new package. Good luck!
--
Best regards,
Ivan
______
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
, 'xx', 'nmxx'? What is your
sessionInfo()?
--
Best regards,
Ivan
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
1 - 100 of 552 matches
Mail list logo
