--- Begin Message ---
Apologies, this is a cross post from 'R-devel', where I sent this message a few
months ago when I did not realize there was an 'r-package-devel' list. So here
it is again in the correct list:
I'm working on a package that implements a REPL. A typical interaction with
the
--- Begin Message ---
I too am seeing the same failure in my package. It does not contain any
#pragma directives, and it doesn't have any dependencies to other compiled
packages.
Poking around through the CRAN checks I've found other packages with C compiled
code displaying the same error on th
An all.equal method? This might not work with 3rd edition though
(untested), and I'm not sure what method registration requirements
would exist for the user.
Best,
B.
On Friday, April 16, 2021, 6:09:24 AM EDT, Duncan Murdoch
wrote:
I'm updating the rgl package, and have come across the
At the risk of only being mildly (if at all) helpful, I was able
to reproduce your warnings on Rhub, which has the same compiler,
with:
rhub::check('cubature_2.0.4.1.tar.gz', platform='windows-x86_64-release')
Absent feedback from CRAN you could try tweaking your code so that
it does not prod
> On Tuesday, July 6, 2021, 8:09:18 AM EDT, dbosa...@gmail.com
> wrote:
>
> Martin:
>
> What I suggested was he remove the LazyData entry from the description file
> if he was NOT lazy loading data. If someone is lazy loading data, then that
> is a different situation, and they obviously need
There was a recent changed made to R to remove that option.
There is documentation visible in the patch that explains it:
https://github.com/r-devel/r-svn/commit/795fb3fe60d35734750afbc34cc7d36b19290b9c
Presumably you would have to remove any uses of the now
unsupported functions. After the patc
Or you might need to make their use conditional on the R
version. It is possible that the call is still needed if your
package is run on older versions of R. I am not familiar with
the general use of this though. I only noticed the change
in R-devel and linked it to your question.
Best,
B.
O
Fabio,
Judging from prior versions of your package, the function `tile_read`
makes many assumptions as to what paths will look like, and also
modifies paths. In this case, it appears to be thrown off by either
the lower case drive name, or the forward slashes in the path. Presumably
winbuilder i
I would just increment the version. This is the from the CRAN
re-submission policy[1]:
> Updates to previously-published packages must have an increased version.
> Increasing the version number at each submission reduces confusion so is
> preferred even when a previous submission was not accept
--- Begin Message ---
My package unitizer has recently gained a new set of errors that look like:
[[alternative HTML version deleted]]
--- End Message ---
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-pack
--- Begin Message ---
Sorry, previous e-mail got pre-maturely sent due to fat finger...
My package unitizer[1] has recently gained the following type of error:
Warning in install.packages(pkg, repos = NULL, type = "src") : 'lib =
"/home/hornik/tmp/R.check/r-devel-clang/Work/build/Packages
the library is writeable. It is not in many
network installations.
Best,
Uwe Ligges
On 18.03.2019 16:48, brodie gaslam via R-package-devel wrote:
>
> Subject:
> Installing "Additional" Packages During Tests
> From:
> brodie gaslam
> Date:
> 18.03.2019, 16:48
&
At the risk of getting laughed out of the room I wanted to share with you some
interesting findings that arose from trying to figure out why my package vetr
is segfaulting on the gcc-10 test machine:
https://www.stats.ox.ac.uk/pub/bdr/gcc10/vetr.out
Thanks to Dirk Eddelbuettel who pointed me to
You can also just paste the ftp link into your browser.
On Thursday, March 5, 2020, 6:31:03 PM EST, Rolf Turner
wrote:
On 6/03/20 11:41 am, Henrik Bengtsson wrote:
> 1. I'd guess it helps Uwe a bit you clarify exactly which queue you
> think is stuck - otherwise he has to check the
I don't know if this will work in your case (or even if it is a good
or bad thing to do), but backports conditionally exports the function
in question, e.g.:
https://github.com/r-lib/backports/blob/master/R/lengths.R
So in that example their implementation of a function not available
in R < 3.2.0
15 matches
Mail list logo
