sion numbers or results of spell check have a non neglible
> probability of false positives, hence get manually inspected once raised
> by the auto check system.
>
> In this case the jump 1 --> 11 was flagged, because many people actually
> mean 1.1 instead, but it got manually
> > I wouldn’t poopoo it so quickly!
> >
> > On Mon, Nov 4, 2024 at 15:32 Rolf Turner wrote:
> >
> >>
> >> On Mon, 4 Nov 2024 16:33:40 -0500
> >> Toby Hocking wrote:
> >>
> >>
> >>
> >>> Version jumps in minor (submitte
which do not pass auto checks.
Thanks for your consideration
* checking CRAN incoming feasibility ... [11s] NOTE
Maintainer: 'Toby Hocking '
Version jumps in minor (submitted: 2024.11.2, existing: 2024.1.24)
__
R-package-devel@r-project.org ma
I got this warning too, so I filed an issue to ask
https://github.com/r-lib/roxygen2/issues/1654
On Mon, Sep 2, 2024 at 2:58 PM John Fox wrote:
>
> As it turned out, I was able to avoid redefining coef.merMod(), etc., by
> making a simple modification to the cv package.
>
> I'm still curious abou
Thanks Dirk. I agree.
data.table is not in a situation to update very soon, so the easiest
solution for the R community would be for CRAN to set OMP_THREAD_LIMIT
to 2 on the Windows and Debian machines doing this test.
Otherwise the 1400+ packages with hard dependencies on data.table will
each have
Hi Tomas, these are really helpful suggestions, which are not at all
discussed in the current Writing R Extensions, nor in CRAN Repository
Policy. Would you please consider adding this information to one of these
official sources of documentation?
On Fri, May 14, 2021 at 3:59 AM Tomas Kalibera
wr
Hi Naras
I had a similar issue recently with
https://cloud.r-project.org/web/packages/nc/ --- it Suggests: re2r which is
a package that is no longer on CRAN, but available on github. To solve the
issue I just copied the re2r into a drat repo, which is a CRAN-like
repository hosted on github. More i
Hi all, I am getting an "invalid multibyte string" error from one of my
examples when it is run on solaris, which results in check FAILURE:
https://www.r-project.org/nosvn/R.check/r-patched-solaris-x86/nc-00check.html
To fix this I guess I could just delete this example, but is there any
easy/know
tdata", "file_with_unicode.txt",
package="yourPkg"))
On Wed, Sep 25, 2019 at 11:45 AM Tomas Kalibera
wrote:
> On 9/25/19 7:59 PM, Toby Hocking wrote:
>
> Hi Tomas thanks for the explanation. Does that mean that there is no known
> fix? i.e. it is OK to re-submit a new version of
Hi Tomas thanks for the explanation. Does that mean that there is no known
fix? i.e. it is OK to re-submit a new version of my package without fixing
these WARNINGS?
On Tue, Sep 24, 2019 at 1:38 AM Tomas Kalibera
wrote:
> On 9/24/19 1:57 AM, Toby Hocking wrote:
> > Hi all,
> >
Hi all,
is there a known fix for this WARNING which I am getting on solaris for my
newly submitted nc package?
https://www.r-project.org/nosvn/R.check/r-patched-solaris-x86/nc-00check.html
A quick google search for "it is not known that wchar_t is Unicode on this
platform cran" shows that many ot
Hi Dirk thanks for the helpful response.
On Wed, Oct 24, 2018 at 5:09 AM Dirk Eddelbuettel wrote:
>
> On 23 October 2018 at 14:02, Toby Hocking wrote:
> | I would like to put the https://github.com/tdhock/PeakSegDisk package on
> | CRAN. This package needs Berkeley DB C++ Stand
I would like to put the https://github.com/tdhock/PeakSegDisk package on
CRAN. This package needs Berkeley DB C++ Standard Template Library. What do
I need to do to get this package (with compiled mac/windows binaries) on
CRAN?
This C++ library is relatively easy to install
https://github.com/tdho
13 matches
Mail list logo
