t; Maybe there's a way to make the new packages compatible with the old
> one, so there would be no excuse for the downstream packages not to
> update right away.
>
> Duncan Murdoch
>
>
> On 11/03/2021 7:39 p.m., Ege Rubak wrote:
> > Dear Duncan,
> >
> > T
This way it
> could
> be done with no breaking changes. Reverse dependencies could change
> to
> depend on spatstat. at their leisure.
>
> Duncan Murdoch
>
> On 11/03/2021 10:18 a.m., Ege Rubak wrote:
> > Dear all,
> >
> > I'm seeking advice on how to sub
0-1 is available from this repository they may pass
the incoming checks on CRAN, but my hopes are not too high.
If this was successful the reverse dependencies would be compatible
with spatstat 2.0 and on CRAN and so spatstat 2.0 would break nothing
and we could resubmit.
Best regards,
Ege
Hi all,
My two cents are below Marc's summary here:
On Thu, 2020-10-22 at 20:33 -0400, Marc Schwartz wrote:
> Right now, the interpretation, without further clarification from
> CRAN, would be, it is ok for a package to be on CRAN with license
> based usage restrictions included (e.g. for
On 27/11/2019 00.22, Fernando Roa wrote:
- I used a guest debian 10 in vmware in my system, and couldn't replicate
the error installing with R CMD INSTALL
I guess you should rather run "R CMD check ..." on the tar.gz file to
reproduce the error.
Hope that helps.
/Ege
This in not well thought through, but what about using `sink` to capture
any messages from the call? Then you might be able to remove the
expected warning and output any remaining warnings if they are there...
However, note this part of `help(sink)`:
Sink-ing the messages stream should be
The obvious place to look for pointers of how to detect and link
correctly to fftw would be in the current CRAN package `fftwtools` that
does it without any Rcpp:
https://github.com/krahim/fftwtools
Cheers,
Ege
On 11/28/2017 02:47 AM, Dirk Eddelbuettel wrote:
On 27 November 2017 at 21:24,
Hi Rolf,
Another place to look for macros in Rd files would be in the spatstat
package which I know you are quite familiary with ;-)
However, I think our macros are plain LaTeX without calls to \Sexpr so
it may behave differently than the case at hand.
Cheers,
Ege
On 11/10/2017 02:00 AM, Rolf
do this in the Makevars file
if the strip tool is available (typically the case on Linux). Does
anybody know what CRAN's take is on this?
Cheers,
Ege
[1]:
http://dirk.eddelbuettel.com/blog/2017/08/14/#009_compact_shared_libraries
--
Ege Rubak, Associate Professor,
Department of Mathematical
Hello,
Maybe you could start by writing a polite email to Paul Murrell (the
maintainer of `gridGraphics` according to
https://cran.r-project.org/package=gridGraphics) and ask if he is aware
that his package fails on OSX on CRAN.
If you are lucky he might be able to quickly fix the issue and
Hi,
We had this issue with `median.im` in spatstat. I wasn't involved in
fixing it, but maintainer Adrian Baddeley changed the documentation
according to CRAN instructions. You can see it here:
https://github.com/spatstat/spatstat/blob/master/man/mean.im.Rd
Maybe you can use that for
On 08/10/2016 04:05 PM, Dirk Eddelbuettel wrote:
On 10 August 2016 at 08:39, Charles Determan wrote:
| I have seen this previous discussion (
| https://stat.ethz.ch/pipermail/r-package-devel/2015q2/000115.html) on this
| question but I didn't find a clear answer. I am looking at integrating
Thanks for the good specific suggestions Kevin and Max. It is amazing
that great help is available from the R community in such a short time.
Clearly everybody thinks that these issues should be fixed before I even
try to submit to CRAN (and I fully agree that they shouldn't lower their
I am using #pragma omp statements all over the place and this is the only
type causing crashes. I'm guessing it has something to do with travis
building on a 12.04 ubuntu VM with a rather old gcc (4.6.3).
2. Is there a workaround, or should I just go for another build service
(which one)?
14 matches
Mail list logo
