On 12 May 2025 at 16:45, Adam Loy wrote:
| Hi all,
|
| I am having trouble getting past the pre-checks for CRAN, but things check
| out in my testing localling in the cloud. I get this message on Debian:
|
| Error: package or namespace load failed for ‘HLMdiag’ in
| dyn.load(file, DLLpath = DLL
Hi Ivan,
thanks for your helpful response and for the background info! Much
appreciated!
I'll reply-all as you suggested.
Best regards,
Johann
On 16.01.25 21:30, Ivan Krylov wrote:
В Wed, 15 Jan 2025 22:13:36 +0100
Johann Pfitzinger пишет:
I have, so far, failed to reproduce this or to f
В Wed, 15 Jan 2025 22:13:36 +0100
Johann Pfitzinger пишет:
> I have, so far, failed to reproduce this or to find any useful
> information on how to fix it. My best guess based on the output.txt
> is that it originates in "purrr" (which I depend on).
This is, indeed, a purrr bug:
https://github.
В Thu, 10 Oct 2024 13:10:39 +
Jaime Salvador пишет:
> * The \dontrun in examples. To run the examples, we need a
> database, the package doesn't include a sample database, so the code
> can't be run. I remove \dontrun in functions that can run without a
> database (for example redatam_ver
mailto:jaime.salva...@ideasybits.com>>
Cc "r-package-devel@r-project.org"
mailto:r-package-devel@r-project.org>>
Fecha 10/10/2024 3:30:18
Asunto Re: [R-pkg-devel] Help with 2 NOTES
Dear Jaime Salvador,
Welcome to R-package-devel!
В Wed, 9 Oct 2024 20:42:24 +
Jaime Salvador
Dear Jaime Salvador,
Welcome to R-package-devel!
В Wed, 9 Oct 2024 20:42:24 +
Jaime Salvador пишет:
> New submission
This one is expected for new packages.
> Possibly misspelled words in DESCRIPTION:
> DICX (12:67)
> RXDB (12:59)
> Redatam (2:34, 12:40)
Wrap the abbreviations and s
May be a completely red herring, but I've recently had what might be a similar
issue with reference classes, which kept me pulling my hair for a few hours
(when method calls that used to work suddenly stopped doing so, unless called
manually first).
IIRC, the culprit was a method obj$basis() be
В Wed, 25 Sep 2024 16:57:55 -0400
Ben Bolker пишет:
> Next question, is this (in your opinion) worth escalating to
> r-devel ?
I think so, yes. Hopefully there will be a way to temporarily re-enable
the S4 dispatch for primitive operators in methods:::.requirePackage
(that lives in R/RClassUtil
Please let me know if I can be of any help. I kind of "caused" this issue
by submitting the new version of brms to CRAN.
Of course, the issue is not really in brms but somehow deeper as your
investigations shows. Would it help if brms
extracted variables names from rstan objects somehow differently
Yikes. Next question, is this (in your opinion) worth escalating to
r-devel ?
I can definitely implement something where I require() rstan up
front, (which should be harmless if it's really not available but will
fix issues that brms is having?) ... that might resolve the symptoms
cleanl
В Wed, 25 Sep 2024 12:28:25 -0400
Ben Bolker пишет:
>What is your current estimate of the probability that this is
> something that I've done wrong vs. exposing something wonky elsewhere
> (i.e. at the level of testthat, brms, rstan, Rcpp, R-devel, ...) ?
I didn't have a good answer (the m
On 9/25/24 12:21, Ivan Krylov wrote:
Hmm, so it's *not* a machine-specific problem after all [1,2] and can
now be reproduced on a regular R-devel build on Debian Sid. I'm sorry
for jumping to conclusions.
No need to apologize, you've gotten 1000x farther than I would have
on my own.
Hmm, so it's *not* a machine-specific problem after all [1,2] and can
now be reproduced on a regular R-devel build on Debian Sid. I'm sorry
for jumping to conclusions.
Why would Rcpp::loadModule() (called from rstan's .onLoad) end up trying
to apply a non-function, but only when being called from
Thanks both.
Josiah Parry says:
> Ben, the issue is that {rstan} is not available. Since it is a
suggested package it is not expected to always be there.
The thing is that the checks for rstan-based objects *are*
conditional. This is actually failing on the tests for brms-based
object
В Tue, 24 Sep 2024 10:27:34 -0400
Ben Bolker пишет:
>Weirdly, I can't get this to fail on my local system even if I
> remove rstan -- maybe rstan needs to be present for brms at install
> time but not at runtime ... ???
I'm noticing that despite broom.mixed having Suggests: rstan and it
bein
Ben, the issue is that {rstan} is not available. Since it is a suggested
package it is not expected to always be there.
This is referred to is the "hard" check.
Here is a GitHub CI workflow I use to perform this check:
https://github.com/JosiahParry/sfdep/blob/008a59b6009d01e5e1625319f6525c1e0ba
Dear Ivan,
Thank you so much for your help.
I followed your advices and I reduced the size of the example data, move one
package from Import to Suggest.
The type of the license is unfortunately not depending on me so I’ll try one
last time with the CC license and the new improvements.
Thank y
(I am adding the mailing list back in Cc: because package licensing is
a complicated topic.)
В Tue, 9 Jul 2024 09:25:14 +
Matei Teleman пишет:
> I’ve added “ … SuperCell uses
> [velocyto.R](https://github.com/velocyto-team/velocyto.R) for RNA
> velocity. ” in the Description field. Is that e
В Mon, 8 Jul 2024 15:12:24 +
Matei Teleman пишет:
> Non-FOSS package license (file LICENSE)
> The license we’re using is the standard CC BY-NC-ND 4.0 and is listed
> among the accepted licenses for CRAN
Instead of putting the license text in a file inside the package (that
would have to mat
Hello, Pedro et al.:
Your package is on GitHub with GitHub Actions.[1] If whoever manages
GitHub actions feels inclined to add macos-latest (oldrel-1), this would
be one argument for doing that, though this kind of problem may be too
rare to justify the expense. That's particularly true si
On 2024-06-30 5:17 a.m., Aphalo, Pedro J wrote:
Hello,
A few days ago I submitted to CRAN an updated version of package 'ggpp', it
passed checks during submission and version 0.5.8 is now on CRAN. However I see
errors for old-rel only for MacOS at
https://cran.r-project.org/web/checks/check_re
On 2024-05-30 7:43 a.m., Ivan Krylov via R-package-devel wrote:
В Thu, 30 May 2024 11:12:05 +0200
Héctor Meleiro Suárez пишет:
So why is this a problem? Is it that there are too many files aftes
examples and tests are run? or would this NOTE be an issue to CRAN
even if only one file was detect
В Thu, 30 May 2024 11:12:05 +0200
Héctor Meleiro Suárez пишет:
> So why is this a problem? Is it that there are too many files aftes
> examples and tests are run? or would this NOTE be an issue to CRAN
> even if only one file was detected at the end?
This problem has two sides.
The side that R
Dear Hector,
The tmp dir depends on the R session. Use tools::R_user_dir("your_package",
which = "cache") if you want a permanent cache of the files.
Best regards,
ir. Thierry Onkelinx
Statisticus / Statistician
Vlaamse Overheid / Government of Flanders
INSTITUUT VOOR NATUUR- EN BOSONDERZOEK /
On 18.03.2024 02:07, Ben Bolker wrote:
I think I may actually have figured this out.
The Matrix package is being updated to version 1.7.0 soon, with
expected ABI breakage. This version is **already installed on
win-builder/r-devel**, so the Matrix/TMB/glmmTMB binary stack fails
(digg
I think I may actually have figured this out.
The Matrix package is being updated to version 1.7.0 soon, with
expected ABI breakage. This version is **already installed on
win-builder/r-devel**, so the Matrix/TMB/glmmTMB binary stack fails
(digging into the logs a bit deeper showed that t
Hi,
This may need the help of Uwe Ligges to diagnose. I suspect this may be
related to the Windows machine having too much memory committed (as Uwe
has been able to pinpoint recently [*] about a package that failed to
compile some heavily templated C++), but there is not enough information
to give
Thanks. Although I have had Xtools for quite a while, it had not been
activated. Installing a new copy made all the difference
Bill
> On Sep 25, 2023, at 12:24 PM, Gábor Csárdi wrote:
>
> Seems like you are on macOS. You need to install XCode or the Command
> Line Tools to be able to compil
Seems like you are on macOS. You need to install XCode or the Command
Line Tools to be able to compile packages with C/C++/Fortran code.
Gabor
On Mon, Sep 25, 2023 at 7:02 PM William Revelle wrote:
>
> Dear friends,
> I am trying to release a new update to psych and psychTools and am having
> p
rom: R-package-devel on behalf of
Duncan Murdoch
Sent: Wednesday, July 5, 2023 10:03:11 AM
To: chrish...@psyctc.org ; r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Help with a github/Rstudio mess
I think this isn't the right place to ask for this sort of help. Maybe
stackoverflow ins
First, apologies for being off topic. I guess I can see that this was
pretty pure git/github/Rstudio with hindsight. I am very leary of
stackoverflow, probably wrongly, but I find such a mix of misinformation
and showboating there. By contrast this list is a haven for me
to learn. However, poi
On Wed, 5 Jul 2023 09:44:26 +0100
Chris Evans wrote:
> OK. So I try to pull thinking that made sense and that the change to
> pkgdown.yaml on github that I made yesterday is the offending change.
You are right about this.
> However, when I pull (in Rstudio again) I get this:
>
> >>> /usr/bi
I think this isn't the right place to ask for this sort of help. Maybe
stackoverflow instead?
What I'd do in this case is to rename the local dir holding the
repository, then clone a new copy from Github. Assuming that works,
compare all the files to make sure that you have all recent changes
On 5/22/23 2:38 PM, Duncan Murdoch wrote:
On 22/05/2023 3:07 p.m., Ivan Krylov wrote:
I fed your vignette to R CMD Sweave, and here's the relevant fragment
from the resulting *.tex file:
This returned a {\tt "findFn"} object identifying 405 help pages.
When this was run while preparing this
On 23/05/2023 6:53 a.m., Martin Maechler wrote:
Duncan Murdoch
on Mon, 22 May 2023 15:38:10 -0400 writes:
> On 22/05/2023 3:07 p.m., Ivan Krylov wrote:
>> I fed your vignette to R CMD Sweave, and here's the
>> relevant fragment from the resulting *.tex file:
>>
>>>
> Duncan Murdoch
> on Mon, 22 May 2023 15:38:10 -0400 writes:
> On 22/05/2023 3:07 p.m., Ivan Krylov wrote:
>> I fed your vignette to R CMD Sweave, and here's the
>> relevant fragment from the resulting *.tex file:
>>
>>> This returned a {\tt "findFn"} object iden
On 22/05/2023 3:07 p.m., Ivan Krylov wrote:
I fed your vignette to R CMD Sweave, and here's the relevant fragment
from the resulting *.tex file:
This returned a {\tt "findFn"} object identifying 405 help pages.
When this was run while preparing this manuscript, the sixth row was
{\tt pspline_ch
I fed your vignette to R CMD Sweave, and here's the relevant fragment
from the resulting *.tex file:
> This returned a {\tt "findFn"} object identifying 405 help pages.
> When this was run while preparing this manuscript, the sixth row was
> {\tt pspline_checker} in the \pkg{JOPS} package, which h
A simple fix might be to redefine findFn in the global environment of the
vignette, have it explicitly call sos::findFn, and return a result
sanitized for LaTeX output. According to this:
https://stackoverflow.com/questions/32865384/function-to-sanitize-strings-for-latex-compilation
it looks like t
Hi, Uwe et al.:
The sos vignette sos.Rnw now fails on GitHub, complaining of a LaTeX
error in "{\tt pspline_ checker}". I don't find it in the code for
sos.Rnw. It may be triggered by a response to an internet search that's
different from before.
https://github.com/sbgraves237/sos
Hi, Uwe et al.:
Uwe suggests I postprocess output with gsub("_", "_", output).
It's not clear to me where I should apply this. The "WARN" flags the
sos vignette sos.Rnw, but the offending code refers to pspline_checker,
which is not in the version of the vignette available on CRAN.[1]
On 16.05.2023 14:02, Spencer Graves wrote:
On 5/16/23 6:06 AM, Uwe Ligges wrote:
On 16.05.2023 01:46, Spencer Graves wrote:
Hello, All:
The sos package is failing some CRAN checks, complaining:[1]
LaTeX errors:
! Missing $ inserted.
$
l.303 {\tt pspline_
On 5/16/23 6:06 AM, Uwe Ligges wrote:
On 16.05.2023 01:46, Spencer Graves wrote:
Hello, All:
The sos package is failing some CRAN checks, complaining:[1]
LaTeX errors:
! Missing $ inserted.
$
l.303 {\tt pspline_
checker} in the
I can only
On 16.05.2023 01:46, Spencer Graves wrote:
Hello, All:
The sos package is failing some CRAN checks, complaining:[1]
LaTeX errors:
! Missing $ inserted.
$
l.303 {\tt pspline_
checker} in the
I can only guess this is part of the response you go
On Mon, 15 May 2023 18:46:00 -0500
Spencer Graves wrote:
> I can NOT replicate these locally nor with GitHub action, and I
> failed to find 'psp' in 'sos.Rnw'.[2] This raises two issue:
>
>
> OBVIOUS: What can I do to fix this error, or at least to understand
> it better?
How does the outpu
This was a temporary hicc up on the Windows machine, all check should
have been triggered again.
Best,
Uwe Ligges
On 31.01.2023 16:02, Mike Blazanin wrote:
Hi all, trying to troubleshoot my way through my first CRAN package
submission. I've addressed all the other issues so far (much thanks t
On 19.12.2022 22:45, Anna Carolina Resende wrote:
Hello,
I'm running test to check if my package is working properly, and for
Fedora, Windows and Ubuntu I get the following note:
* checking CRAN incoming feasibility ... [5s/25s] NOTE
Maintainer: ‘Anna Carolina Resende ’
I read online that i
В Tue, 20 Dec 2022 10:45:38 +1300
Anna Carolina Resende пишет:
> * checking CRAN incoming feasibility ... [5s/25s] NOTE
> Maintainer: ‘Anna Carolina Resende ’
>
> I read online that it's a note for CRAN so they can check that the
> maintainer made changes, could you confirm that that is the case
Thank you.
On Tue, Oct 18, 2022 at 4:28 PM Uwe Ligges
wrote:
> See my response to the list.
>
> Best,
> Uwe Ligges
>
>
> On 18.10.2022 14:11, Jahajeeah, Havisha wrote:
> > Hello,
> >
> > Grateful if you could please help with the following comments:
> >
> > Please add small executable examples i
See my response to the list.
Best,
Uwe Ligges
On 18.10.2022 14:11, Jahajeeah, Havisha wrote:
Hello,
Grateful if you could please help with the following comments:
Please add small executable examples in your Rd-files to illustrate the
use of the exported function but also enable automatic te
Hello,
Grateful if you could please help with the following comments:
Please add small executable examples in your Rd-files to illustrate the
use of the exported function but also enable automatic testing.
The greymodels package loads data from spreadsheets and each model accepts
a set of data a
Hello,
Thank you for the clarification.
Havisha
On Thu, 29 Sep 2022 at 01:24, Henrik Bengtsson
wrote:
> Hi,
>
> it's not just you; the win-builder server is down for all of us (e.g.
> https://downforeveryoneorjustme.com/win-builder.r-project.org?proto=https
> ).
> Uwe Ligges, who maintains thi
Hi,
it's not just you; the win-builder server is down for all of us (e.g.
https://downforeveryoneorjustme.com/win-builder.r-project.org?proto=https).
Uwe Ligges, who maintains this, mentioned (in another thread
somewhere) that there were networking issues at his university that
are being worked on
Dear team,
I am having trouble submitting my package to CRAN because the link
https://win-builder.r-project.org/ is not accessible.
Please advise.
Thank you
Havisha Jahajeeah
On Mon, Sep 26, 2022 at 11:17 PM Ivan Krylov wrote:
> It might be easier to help you if you show us your package by
>
It might be easier to help you if you show us your package by
publishing the source code somewhere.
On Mon, 26 Sep 2022 22:22:48 +0400
"Jahajeeah, Havisha" wrote:
> CIvalue2: no visible global function definition for 'qt'
> andgm11: no visible binding for global variable 'ParticleSwarm'
> andgm1
Hello,
are you aware of https://win-builder.r-project.org/? It'll allow you
to validate that your package passes all the requirements before
submitting it to CRAN.
My $.02
/Henrik
On Mon, Sep 26, 2022 at 11:23 AM Jahajeeah, Havisha
wrote:
>
> Dear team,
>
> My second attempt at submitting the
Dear team,
My second attempt at submitting the package GreymodelsPackage_1.0.tar.gz to
CRAN.
Grateful if you could please assist me with the following issues:
CIvalue2: no visible global function definition for 'qt'
andgm11: no visible binding for global variable 'ParticleSwarm'
andgm11: no visi
On 26.09.2022 17:14, Jahajeeah, Havisha wrote:
Dear team,
I have submitted the package GreymodelsPackage_1.0.tar.gz to CRAN and it's
a shiny app.
However, I received the following
* using log directory
'd:/RCompile/CRANincoming/R-devel/GreymodelsPackage.Rcheck'
* using R Under development
В Mon, 26 Sep 2022 19:14:04 +0400
"Jahajeeah, Havisha" пишет:
> * checking extension type ... ERROR
> Extensions with Type 'Shiny application' cannot be checked.
Since you're writing a package, you can either specify Type: Package in
the DESCRIPTION file, or omit the field entirely:
https://cran
Comments in-line:
> Date: Sat, 9 Jul 2022 16:29:57 -0400
> From: Ben Bolker
> To: R Package Development
> Subject: [R-pkg-devel] help/advice on debugging
> Message-ID:
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
>For some stupid reason I agreed to take over maintenance of
On 23.11.2020 04:13, Roy Mendelssohn - NOAA Federal wrote:
I have found win-builder timings come close, but only close. My experience is
that the CRAN timings were uniformly slower than those on win-builder. But I
also find that I can get quite significant differences between
win-builder
I have found win-builder timings come close, but only close. My experience is
that the CRAN timings were uniformly slower than those on win-builder. But I
also find that I can get quite significant differences between
win-builder-release and win-builder-devel. So I also take the slowest that
And one more (last for a while): presumably there is no way to check
CRAN windows timing without submitting to CRAN ... ? (I will obviously
do my best by doing arithmetic on the tests that I set to be skipped,
but it would be nice to be able to double-check without wasting
everyone's time ..
Thanks all for the help. The reward (as usual) is another dumb
question.
If I add up the elapsed times listed in
https://win-builder.r-project.org/incoming_pretest/lme4_1.1-26_20201122_184744/Windows/examples_and_tests/examples_x64/lme4-Ex.timings
I get 21.43 seconds. But the output in
Thanks Dirk. Yes, for lme4 the tests for each archiecture take longer
than 5 min, so the overall check time exceeds 10 min.
So one can follow Dirk's advise.
As a general remark for others who will read this in the future:
tests should test the software, but it is generally not important to
hav
On 22 November 2020 at 13:44, Ben Bolker wrote:
|My current guess is that the problem is with the too-long check time on
Windows (NOTE: "Overall checktime 18 min > 10 min")
Yes.
| I guess I have to get busy setting more tests and examples to skip-on-CRAN
(kind of a pain as there's no l
Just to close the loop on this: the drat suggestion for both packages
and also moving things to enhances worked. I could do this also for
Gurobi because it is LGPL'd. Thanks Toby and Dirk (for drat).
-Naras
On 9/9/20 5:16 PM, Balasubramanian Narasimhan wrote:
Thanks Toby, so there is hope. T
Thanks Toby, so there is hope. The drat suggestion for rcbc is worth a
try, gurobi is noted as you recommend.
-Naras
On 9/9/20 4:38 PM, Toby Hocking wrote:
> Hi Naras
> I had a similar issue recently with
> https://cloud.r-project.org/web/packages/nc/ --- it Suggests: re2r
> which is a packag
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
Thank you for the helpful replies! I got it now, I overlooked the return on
the ifelse() before.
Thanks a lot again!
- Anirban
On Thu, Sep 3, 2020, 11:18 AM Anirban wrote:
> Hi, I've one note in my package which I can't seem to resolve while
> submitting to CRAN:
>
> New submission
>
> Flavo
Hi Anirban,
I don't think the issue is coming from the return statement at the end of your
function. I think it's triggered by your "ifelse" statement, where you have
"return" as the expression to be run if the condition isn't met.
A more idiomatic way of achieving what you're trying to do woul
`return()` is a function in R, so `return` does nothing. You probably
want `return()`.
Here:
https://github.com/Anirban166/testComplexity/blob/c991c31e5250bcaf804c3ad781fbc126c6a17e57/R/asymptoticMemoryUsage.R#L22
https://github.com/Anirban166/testComplexity/blob/master/R/asymptoticTimings.R#L22
Is this reproducible on R-hub? Do you see it with the other R-devel
containers as well?
Some things to try:
Try running address sanitizer on your package to see if it can find
any memory errors. You can do this on R-hub as well, if you cannot do
it on your machine.
Try downloading the https://hu
Thanks for the tips. It appears the error is indeed related to the
matchingMarkets package, but specifically an issue with rJava
configuration. Now I get the following (see
https://artifacts.r-hub.io/PAutilities_1.0.0.tar.gz-54a555386e924de6a53385479a1e199f/PAutilities.Rcheck/00check.log
):
VALIDA
You don't need to move the files around, though, just use a more
verbose testthat reporter, e.g. in testthat.R use
test_check("PAutilities", reporter = "summary")
and then at least you'll know where it crashes. But to fix this,
you'll probably need to debug it locally. You can do that in Docker i
On Fri, 15 May 2020 03:50:12 -0400
Paul Hibbing wrote:
> Complete output:
> > library(testthat)
> > library(PAutilities)
> >
> > test_check("PAutilities")
It seems to me that the R process crashes while running your tests, but
since testthat::test_check captures everything to summarise
Removing the startup message did not resolve the issue. Now I have just:
* checking tests ...
Running ‘testthat.R’
ERROR
Running the tests in ‘tests/testthat.R’ failed.
Complete output:
> library(testthat)
> library(PAutilities)
>
> test_check("PAutilities")
See
https://artifacts.r-hu
On 15 May 2020 at 02:30, Gábor Csárdi wrote:
| It is unlikely that this is an R-hub issue because the first link is
| CRAN's machine, and the same error happens there.
My bad, sorry -- I read the original email(s) wrong.
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Ah, I hadn't considered that the startup message could be the problem
- I thought the point of startup messages was to be distinct from
errors and warnings, so I wouldn't have expected that to trip up R CMD
Check. I assumed the failure was occurring somewhere inside the actual
code for my unit test
Apparently, this is not a warning, but the package itself is printing
it as a startup message:
https://github.com/cran/PAutilities/blob/ada73d8d44177c12867cc385cdca0054885ddae3/R/zzz.R#L5
Gabor
On Fri, May 15, 2020 at 2:30 AM Gábor Csárdi wrote:
>
> It is unlikely that this is an R-hub issue bec
It is unlikely that this is an R-hub issue because the first link is
CRAN's machine, and the same error happens there.
I can reproduce it on macOS:
git clone https://github.com/paulhibbing/PAutilities
R CMD INSTALL PAutilities
R -q -e 'packageDescription("PAutilities")$Built'
#> > packageDescrip
On 14 May 2020 at 11:41, Paul Hibbing wrote:
| * Here is the CRAN check (devel version 2020-05-13):
|
|
https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-gcc/PAutilities-00check.html
|
| * Here is the successful R-hub check (devel version 2020-05-10):
|
|
https://artifacts.
* Here is the CRAN check (devel version 2020-05-13):
https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-gcc/PAutilities-00check.html
* Here is the successful R-hub check (devel version 2020-05-10):
https://artifacts.r-hub.io/PAutilities_1.0.0.tar.gz-43f919fd5595416799d74bfb312fd
On Mon, 2020-03-30 at 10:18 -0400, Kelsey Chetnik wrote:
> Hi,
>
> I am submitting a package to CRAN for the first time and I am not
> sure what
> the following error means and how to solve it:
> https://win-builder.r-project.org/incoming_pretest/MetaClean_0.1.0_20200330_150936/Windows/00install.o
Oohhh I didn't realize there was an RD. That simplifies things a lot!
And for the record, I'm not surprised that my setup suggests that I don't
know what I'm doing viz-a-viz docker. Everything was assembled by Google
search and spaghetti flinging, so I'm pleased to get some expert advice.
A grat
Steve,
On 25 March 2020 at 16:48, Dirk Eddelbuettel wrote:
| For ASAN/UBSAN to work you should use the same setting as the compiled
| 'host'. As you benefit from a pre-made Docker container, its settings are
|
| CC="clang -fsanitize=address,undefined -fno-sanitize=float-divide-by-zero
-fno-o
Steve,
Your message has me puzzled over a few things just like your previous message
from a few days ago.
On 25 March 2020 at 14:17, Steven Scott wrote:
| I'm trying to build an ASAN enabled version of my R library to help debug
| errors found by CRAN on my last submission. I'm tantalizingly c
> John Lawson
> on Thu, 5 Mar 2020 20:34:00 -0700 writes:
> I see this error on windows CRAN Check
> --- failure: the condition has length > 1 ---
> --- srcref ---
> :
> --- package (from environment) ---
> daewr
> --- call from context ---
> ihstep(y,
On 3/5/20 4:26 AM, John Lawson wrote:
> I see this error on the CRAN Check report
>
>> ### ** Examples
>>
>> #Definitive Screening Design
>> library(daewr)
>> set.seed(1234)
>> x <- DefScreen(m=5,c=0)
>> colnames(x) <- paste("x",1:5,sep="")
>> x$y <- 3*x$x1 + 2*x$x2 + 2*x$x4*x$x5 + x$x3^2 + 2*x$x1^
The first error said your package couldn't be installed, so look in
00install.out.
That file said it couldn't find your DESCRIPTION file. That file should
be in the top level directory of your package. I don't know if Roxygen2
can create it or not. I always write mine by editing the file pr
On Tue, 6 Aug 2019 at 14:40, Andy Stein wrote:
>
> Hi,
>
> I am submitting my first ever R package to CRAN! It's almost ready, but I
> have two notes below and I do not understand the best way to fix them and I
> was looking to get some feedback if anyone had time to help. I paste the
> notes at
On 5 August 2019 at 00:13, Iñaki Ucar wrote:
| On Mon, 5 Aug 2019 at 00:08, Ben Bolker wrote:
| >
| >
| > Yeah, I might try that, or I might try installing the downstream
| > packages that are causing problems from Rutter's repo.
|
| AFAICT from the build log, the packages that are causing pr
Thanks everyone! Passes now.
On 2019-08-04 7:05 p.m., Dirk Eddelbuettel wrote:
>
> On 5 August 2019 at 00:13, Iñaki Ucar wrote:
> | On Mon, 5 Aug 2019 at 00:08, Ben Bolker wrote:
> | >
> | >
> | > Yeah, I might try that, or I might try installing the downstream
> | > packages that are causi
On Mon, 5 Aug 2019 at 00:08, Ben Bolker wrote:
>
>
> Yeah, I might try that, or I might try installing the downstream
> packages that are causing problems from Rutter's repo.
AFAICT from the build log, the packages that are causing problems are
being installed precisely from Rutter's repo:
Get
On 2019-08-04 6:08 p.m., Joshua Ulrich wrote:
> On Sun, Aug 4, 2019 at 4:54 PM Ben Bolker wrote:
>>
>> On 2019-08-04 5:43 p.m., Iñaki Ucar wrote:
>>> On Sun, 4 Aug 2019 at 23:26, Ben Bolker wrote:
I'm having some trouble with travis builds of a package (local checks
work
On Sun, Aug 4, 2019 at 4:54 PM Ben Bolker wrote:
>
> On 2019-08-04 5:43 p.m., Iñaki Ucar wrote:
> > On Sun, 4 Aug 2019 at 23:26, Ben Bolker wrote:
> >>
> >>
> >> I'm having some trouble with travis builds of a package (local checks
> >> work fine) and hoping if I can get suggestions for diagnos
Yeah, I might try that, or I might try installing the downstream
packages that are causing problems from Rutter's repo. (Right now I'm
checking whether I can get it to build on travis without Rutter's repo,
and with rstan/rstanarm removed from the Suggests: list ...
thanks,
Ben Bolker
On Sun, 4 Aug 2019 at 23:45, Ben Bolker wrote:
>
> I tried that already, thanks.
Sorry, I should have read til the end of the email before posting.
> That's why I'm now suspecting it's some
> kind of mismatch between the Rutter PPAs and the default (?) repos that
> Travis uses. It would be a
On 2019-08-04 5:43 p.m., Iñaki Ucar wrote:
> On Sun, 4 Aug 2019 at 23:26, Ben Bolker wrote:
>>
>>
>> I'm having some trouble with travis builds of a package (local checks
>> work fine) and hoping if I can get suggestions for diagnosis &
>> troubleshooting ...
>>
>> The package is 'broom.mixed
On Sun, 4 Aug 2019 at 23:26, Ben Bolker wrote:
>
>
> I'm having some trouble with travis builds of a package (local checks
> work fine) and hoping if I can get suggestions for diagnosis &
> troubleshooting ...
>
> The package is 'broom.mixed'; I hadn't changed it in a while, but
> recently got a
1 - 100 of 148 matches
Mail list logo
