On 11 August 2023 at 07:54, Thomas Petzoldt wrote:
| After moving this discussion to R-SIG-Debian
| (https://stat.ethz.ch/pipermail/r-sig-debian/2023-August/thread.html),
| Dirk Eddelbuettel suggested five different approaches.
|
| I made indeed a snapshot (a local copy) of the complete "
Hi Thomas,
On 9 August 2023 at 17:00, Thomas Petzoldt wrote:
| thank you very much dirk for the quick response. I was aware that
| r-package-devel may not be the optimal place ;-) but hoped to address
| the right audience between r-devel and r-help.
|
| Many thanks also for the suggestions, e
On 9 August 2023 at 16:26, Thomas Petzoldt wrote:
| I am running a couple of shiny servers with several apps that are based
| around own CRAN packages. It worked stable for years, but due to the
| growing number of packages, the compile time for regular manual package
| installation and updat
Simon,
This is still an issue for arm64. Uploaded tiledb and RQuantLib yesterday,
both already built binaries for macOS (thank you!) but on the x86_64 ones are
on the results page. Can you take another peek at this?
Thanks so much, Dirk
--
dirk.eddelbuettel.com | @eddelbuettel | e...@debia
On 7 August 2023 at 13:55, Grose, Daniel wrote:
| As I say - I cannot reproduce the error myself. I will try asking Uwe Ligges
| for more information.
Methinks you are doing it wrong. We created the r-package-devel list years
ago to take load away from the overworked CRAN maintainers who are "on
On 7 August 2023 at 13:38, Grose, Daniel wrote:
| No - unfortunately not. I cannot reproduce the error locally so I posted the
| snippet that Uwe Ligges sent me regarding the failed CRAN submission. That is
| all of the information I have.
|
| For now I will follow Dirk's advice and see if the C
Daniel,
This is not new, and not related to clang.
On 7 August 2023 at 12:58, Grose, Daniel wrote:
| Any ideas ?
Add a line
#define R_NO_REMAP 1
before _any_ inclusion of R headers. See Section 6 of Writing R Extensions.
If you use eg Rcpp it is done for you when you include Rcpp headers
On 22 July 2023 at 16:07, Dirk Eddelbuettel wrote:
|
| Taylor,
|
| I believe we have been over this at StackOverflow but you may by now have
| deleted the question/
|
| On 21 July 2023 at 20:51, taylor brown via R-package-devel wrote:
| | I have a question about the DESCRIPTION file of an R
Taylor,
I believe we have been over this at StackOverflow but you may by now have
deleted the question/
On 21 July 2023 at 20:51, taylor brown via R-package-devel wrote:
| I have a question about the DESCRIPTION file of an R package that has some
c++ dependencies.
|
| This package of mine bu
Simon,
This still persists. As Murray reported, it happened for a while now, it is
still happening eg package tiledb has been rebuilt everywhere [1] since the
upload a few days ago -- yet the results page still reports builds two
uploads ago [2] for both arm64 variants of your macOS setup.
Can
On 16 July 2023 at 14:31, Simon Urbanek wrote:
| I looked into it and there was no issue on the build machine or staging
server, so it will require some more digging in the international waters ..
hopefully sometime next week…
Thanks for checking, sometimes one-offs happen.
Dirk
--
dirk.edd
Simon,
On 12 July 2023 at 19:02, Dirk Eddelbuettel wrote:
|
| Simon,
|
| It looks like some result mirroring / pushing from your machines to CRAN fell
| over. One of my packages, digest 0.6.33, arrived on CRAN about a week ago,
| is built almost everywhere (apart from macOS_release_x86_64
The concerns over github going away (!!) (or altering references, tags,
releases, ...) may be somewhat alleviated by Software Heritage [1] covering
and 'preserving' it. FWIW I briefly spoke about that iniative and a possible
CRAN connection at useR! in Toulouse four years ago [2].
I think I und
Simon,
It looks like some result mirroring / pushing from your machines to CRAN fell
over. One of my packages, digest 0.6.33, arrived on CRAN about a week ago,
is built almost everywhere (apart from macOS_release_x86_64 stuck at 0.6.32)
but the result page still has nags from the 0.6.31 build f
On 6 July 2023 at 08:14, Dirk Eddelbuettel wrote:
|
| On 6 July 2023 at 14:31, Vincent van Hees wrote:
| | Thanks, in that case the REPLEX for the issue may need to be:
| |
| | > remember = Sys.getenv("_R_CHECK_AS_DATA_FRAME_EXPLICIT_METHOD_")
| |
On 6 July 2023 at 14:31, Vincent van Hees wrote:
| Thanks, in that case the REPLEX for the issue may need to be:
|
| > remember = Sys.getenv("_R_CHECK_AS_DATA_FRAME_EXPLICIT_METHOD_")
| > Sys.setenv("_R_CHECK_AS_DATA_FRAME_EXPLICIT_METHOD_" = TRUE)
| > data.frame(time = Sys.time())
|
On 26 June 2023 at 21:03, Uwe Ligges wrote:
| On 26.06.2023 02:52, Bernd.Gruber wrote:
| > Thanks, just to make sure:
| >
| > In the policy I find the entry:
| >
| > Additional_repositories:
|
| You can use this for CRAN-style repositories. Not for other inds of
| storage. In that case you ne
On 24 June 2023 at 21:35, Stephen Wade wrote:
| Doesnt seem like the system package is worth it. Should the convention
| simply be to bundle the headers in the package then? What about package
| size - is there some limit to the size of included libraries/headers to
| consider for CRAN?
Here is
Hi William,
On 20 June 2023 at 16:06, William Becker wrote:
| I am the maintainer of a package which is unfortunately involved in a
complicated dispute regarding its intellectual property (since the package was
partly built under a contract with an organisation), but also the "branding" of
th
Non-Maintainer Update (NMU) is a well-defined term in the Debian Developer's
Reference and packaging practice (see [1]) but not something that exists in
the CRAN Repository Policy [2] so "requesting" a NMU is a tricky. As Duncan
kindly explained there are some words in [2] about transfering / ta
Hi Jarrett
On 16 May 2023 at 19:06, Jarrett Phillips wrote:
| I wonder if my problem is related to the question you posed about the CRAN
| macOS builders being down. If it is, then according to @Simon Urbanek, this
| should be resolved in a few hours.
|
| Can you confirm?
Oh, maybe -- were yo
builds so they should catch up in a few hours.
Thanks but as I noted _all other non-arm64 macOS machines are also lagging_
and now for about five days -- which is why wrote the email.
But good to know you are on it now!
Dirk
|
| Thanks,
| Simon
|
|
| > On 17/05/2023, at 8:39 AM, Dirk Eddelbuet
, two
linux builds and all macOS missing
https://cran.r-project.org/web/checks/check_results_RcppSimdJson.html
So no builds on macOS for either of my uploads to CRAN. Can you comment?
Dirk
| Cheers,
| Simon
|
|
| > On 17/05/2023, at 4:27 AM, Dirk Eddelbuettel wrote:
| >
| >
| > S
On 16 May 2023 at 18:32, Serguei Sokol wrote:
| Try to add in /src/Makevars:
|
| PKG_LIBS=$(FLIBS)
Good catch. For every RcppArmadillo package we recommend (and inject if you
use the RcppArmadillo.package.skeleton() helper) (and omit the earlier
comment lines)
PKG_CXXFLAGS = $(SHLIB_OPENMP_C
Simon,
As a follow-up to the cmake questions (and me now knowing I have to tell R
where cmake is on macOS), I uploaded a new package last Thursday. It has long
built everywhere on CRAN, but not on macOS. Ditto for another package update
from Sunday (RcppSimdJson) which also has not been touched
Hi Reed,
On 11 May 2023 at 11:15, Reed A. Cartwright wrote:
| I'm curious why you chose to call cmake from make instead of from configure.
| I've always seen cmake as part of the configure step of package building.
Great question! Couple of small answers: i) This started as a 'proof of
concept'
On 11 May 2023 at 09:02, Martin Maechler wrote:
| I've been told in private that the above "be happy if"
| may *not* be a good idea,
| or rather even close to impossible as cmake seems to not fit
| well, at all, with the quite sophisticated
| autoconf -> configure -> make
| setup we have w
On 10 May 2023 at 16:02, Dirk Eddelbuettel wrote:
|
| On 10 May 2023 at 13:45, Reed A. Cartwright wrote:
| | I use the following logic in my configure script to detect cmake on the
MacOS
| | builders:
| |
| | https://github.com/reedacartwright/rbedrock/blob/master/configure#L39-L49
|
| Nice
On 10 May 2023 at 13:45, Reed A. Cartwright wrote:
| I use the following logic in my configure script to detect cmake on the MacOS
| builders:
|
| https://github.com/reedacartwright/rbedrock/blob/master/configure#L39-L49
Nice. That was entirely undocumented. What a dance. It should help.
|
Simon,
On 11 May 2023 at 08:35, Simon Urbanek wrote:
| Dirk,
|
| can you be more specific, please? I suspect that it may be rather an issue in
your package. All build machines have the official cmake releases installed and
there are many packages that use it successfully. Here is the report o
Simon,
Explicitly declaring
SystemRequirements: cmake
appears to be insufficient to get a build on the (otherwise lovely to have)
'macOS builder', and leads to failure on (at least) 'r-oldrel-macos-x86_64'.
Would it be possible to actually have cmake installed?
These daus cmake is for be
On 4 May 2023 at 09:00, Simon Urbanek wrote:
| > On May 4, 2023, at 3:36 AM, Martin Morgan wrote:
| > CRAN is fine with Bioconductor Depends: and Imports: dependencies, as
previously mentioned. This is because the CRAN maintainers explicitly configure
their system to know about Bioconductor pa
Sergej,
Please consider:
- there are nearly 20k CRAN packages
- all of them are mirrored at https://github.com/cran so you can browse
- pick any one 'heavy' package you like, Seurat is a good example; there
are other examples in geospatial or bioinformatics etc
- you can browse
Simon,
On 24 April 2023 at 18:28, Simon Urbanek wrote:
| thanks - the problem is that there is not a single installer package (for
several years now), so that URL is ambiguous. Whether the missing link is a
good or bad depends on how it is used. I would argue that any link to that URL
is inhe
On 25 April 2023 at 11:39, Viechtbauer, Wolfgang (NP) wrote:
| I ran into the same issue (on Ubuntu 20.04).
|
| I just copied everything from /usr/share/R/doc to /usr/lib/R:
|
| A bit of a hack but then everything works fine.
That is rather bad as you create lots of 'orphan' files your package
On 25 April 2023 at 11:02, Ivan Krylov wrote:
| On Mon, 24 Apr 2023 18:17:22 +0200
| Göran Broström wrote:
|
| >cannot open file '/usr/lib/R/doc/html/katex/katex.js': No such
| > file or directory
|
| > I still get the error with R CMD check --as-cran. What am I
| > missing? Obviously /usr
The URL ${CRAN}/bin/macosx/R-latest.pkg is in fairlt widespread use. A quick
Google query [1] reveals about 1.1k hits. And it happens to be used too in a
CI job a colleague noticed failing yesterday.
The bin/macosx/ page now prominently displays both leading flavours
R-4.3.0-arm64.pkg
R-4.3.
On 22 April 2023 at 14:43, D Z wrote:
| Thank you Dirk and Joshua,
| Using Valgrind, I have found several memory leaks in the program that required
| some smaller rewrites.
| Valgrind (with Makevars flags -O0 and --ggdb) now reports no "definitely" and
| no "indirectly" lost bytes so that's a sma
Hi David,
On 21 April 2023 at 19:17, D Z wrote:
| Hi all,
| I wanted to publish my RITCH package (https://github.com/DavZim/RITCH) to
CRAN, which has Rcpp code.
That would be great!
| It has, in it�s CICD Pipeline, Tests for Macos, Windows, and Ubuntu (devel,
release,, and oldrel-1), which al
On 17 April 2023 at 20:37, Socorro Dominguez wrote:
| Thank you for all the help.
|
| Here is the GitHub link:
| https://github.com/NeotomaDB/neotoma2
Thanks for posting a link to the repo. That should really be a standard.
You currently have (and I indent by two spaces for clarity here)
De
On 4 April 2023 at 10:04, Duncan Murdoch wrote:
| I'd suggest this: build the tarball, and check the tarball.
Strong second. The _Writing R Extensions_ manual does not mention devtools.
As Uwe often reminds everybody here the package is not used by CRAN either.
This may sound harsh but one of
Hi Rodrigo,
This came up recently again on social media where I illustrated how the
tiledb package deals with it. So a quick recap:
First off, let's make the goals clear.
We want to _simultaneously_
- abide by CRAN Policy rules and cap ourselves to two cores there
- do not impose any limits
On 25 March 2023 at 13:01, Shawn Way wrote:
| Sorry to kind of repeat this but I really didn't understand the issues with
the prior thread and how it relates to my issue.
|
| I'm getting the error message in
|
| B_T <- BT(Temp)
| Error in BT(Temp) : DLL requires the use of native symbo
checks and balances.
(One micro nit for something else I noticed: you have a nice pkgdown site,
but not linked to it anywhere.)
Cheers, Dirk
|
| On 3/20/23 17:56, Dirk Eddelbuettel wrote:
| > On 20 March 2023 at 12:43, Duncan Murdoch wrote:
| > | It appears that you have some uses of .Call
On 20 March 2023 at 12:43, Duncan Murdoch wrote:
| It appears that you have some uses of .Call() where you are passing a
| character variable as the first argument, instead of registering the
| entry point and passing the variable containing the registration
| information.
Correct. And to mak
On 27 February 2023 at 14:32, Duncan Murdoch wrote:
| I am in the process of updating rgl to use the glad loader
| (https://github.com/Dav1dde/glad). This replaces system standard gl.h
| and glext.h files with new ones that include function pointers to be
| filled in at run-time, so that rgl
On 20 February 2023 at 22:37, Vasileios Nikolaidis wrote:
| Thanks for taking the time to check it. The hint about the virtual
| 'layer' class is valuable.
| I will look into it.
Sounds good, glad to have been of assistance. On a lark, I also tried your
most recent CRAN release, and it install
On 20 February 2023 at 21:41, Vasileios Nikolaidis wrote:
| Oh yes thank you. I just realized I did not mention the repo on my
| previous reply. It is
| https://github.com/VNNikolaidis/nnlib2Rcpp
Thanks for that -- I can confirm the error.
The packages compiles all source files without issue o
Can you share the repo URL? It may be a a fairly simple and standard issue
some of us can spot easily.
Hth, Dirk
--
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/
On 21 January 2023 at 05:27, Duncan Murdoch wrote:
| On 21/01/2023 5:15 a.m., Holger Hoefling wrote:
| > Is there a simple replacement that I can use?
|
| You should use snprintf() which has an extra argument to state the size
| of the buffer receiving the string. For example,
|
| char text
As the error is common against your _all three_ of your Ubuntu runs, you
could consider the possibility that the events are correlated. Most often it
simply means a (temporary, usually) network or server outage. I would wait,
and then relaunch (which these days you can do just for the failed jo
On 27 December 2022 at 13:27, Duncan Murdoch wrote:
| On 15/12/2022 10:25 a.m., Spencer Graves wrote:
| > I know that some on this list do not like this construct, but it has
| > helped me manage this problem for several years. NOTE: This CRAN
| > function is NOT maintained by anyone on C
On 16 December 2022 at 20:30, EcoC2S - Irucka Embry wrote:
| While running R CMD check on my iemisc package, I receive the following
| warning:
|
| * checking sizes of PDF files under ‘inst/doc’ ... WARNING
|‘gs+qpdf’ made some significant size reductions:
| compacted ‘Comparing_Manni
raction. If CRAN reports this to you,
they see it. You should have access to `tempdir()` and friends to make things
per-session, or else you need to ask the user (once) and then store in
user-supplied location. I think that was discussed here recently.
Good luck, Dirk
[1] Also commonly ca
On 10 December 2022 at 14:00, Roy Mendelssohn - NOAA Federal via
R-package-devel wrote:
| CRAN has sent me a notice about the following:
|
| https://www.stats.ox.ac.uk/pub/bdr/donttest/rerddapXtracto.out
|
| I can not reproduce it. I test on my Mac, the cache space is properly
handled (by
Simon,
On 9 December 2022 at 10:00, Simon Urbanek wrote:
| the minimum required version for the high-sierra build is 10.13 and for
big-sur build is 11.0 (as the names imply). Although it is not unrealistic to
move Intel to macOS 10.14, it would be more problematic to move to 10.15 since
it is
One package I stand behind as maintainer does
## Take care of 10.14 requirement for Intel macOS
if test x"${uname}" = x"Darwin" -a x"${machine}" = x"x86_64"; then
AC_MSG_CHECKING([for Darwin x86_64 use minimum version override])
CXX17_MACOS="-mmacosx-version-min=10.14"
AC_M
On 28 November 2022 at 12:15, Peter Carbonetto wrote:
| I maintain the mashr R package (https://cran.r-project.org/package=mashr),
| which has been on CRAN a little over 2 years. The mashr package depends on
| another package, flashr, which is available from an external repository
| (via *Additio
On 22 November 2022 at 14:15, Jaihee Choi wrote:
| I was trying to resubmit a package but was notified that it did not pass
| the initial checks due to the following error message regarding compiling
| my vignette:
|
| Error: .onLoad failed in loadNamespace() for 'rje', details:
| call: getEng
On 16 November 2022 at 06:36, Duncan Murdoch wrote:
| On 15/11/2022 11:59 p.m., Hugh Parsonage wrote:
| > I think you've misunderstood that excerpt. By "temporary development
| > state", it means _between_ CRAN releases; packages in a development
| > state are not suitable for CRAN, as the polic
On 14 November 2022 at 16:34, Elysée Aristide wrote:
| I was convinced that the issue is local. The warning message only appears
| on MAC.
| I did not try with another computer. I used CRAN macbuilder service and got
| the warning message. I guess this is also the computer CRAN uses.
Some furthe
Ivan,
Thanks for following-up but I think this issue is local to the OP as R is
already setup exactly that way to skip `assert()` in builds (in perfect
congruence with the CRAN Repository Policy)
edd@rob:~$ grep NDEBUG /etc/R/Makeconf
R_XTRA_CPPFLAGS = -I"$(R_INCLUDE_DIR)" -DNDEBUG
ALL_
On 13 November 2022 at 08:15, Simon Urbanek wrote:
| sorry, I think you misunderstood: CRAN machines have the compilers, but the
packages were not detecting it properly and/or were violating the CRAN policies
as noted, so that's why I was saying that it would make sense to have a unified
appro
On 12 November 2022 at 19:27, Jeroen Ooms wrote:
| On Sat, Nov 12, 2022 at 12:49 AM Simon Urbanek
| wrote:
| >
| > this does not directly address your question, but I think it would make a
lot of sense to standardize the process, given how many issues there were with
packages using Rust (mainl
On 11 November 2022 at 16:06, Ivan Krylov wrote:
| В Fri, 11 Nov 2022 12:54:52 +
| "Grose, Daniel" пишет:
|
| > * checking sizes of PDF files under 'inst/doc' ... WARNING
| > 'gs+qpdf' made some significant size reductions:
| > compacted 'cpop.pdf' from 805Kb to 547Kb
| > consider
On 5 November 2022 at 19:32, David Hugh-Jones wrote:
| I'm considering submitting the package onetime (
| https://github.com/hughjonesd/onetime/) to CRAN.
|
| Onetime has functions for showing a message or warning only once (ever per
| user). It does this by writing to a file in the user's confi
On 3 November 2022 at 21:09, Andrew Simmons wrote:
| I had some R code for dealing with connections, and I was using
| summary.connection(). I rewrote it in C, so I was doing something more
| like:
|
| #include
|
| Rconnection Rcon = R_GetConnection(file);
| Rcon->description or Rcon->class
|
On 20 October 2022 at 13:16, Elysée Aristide wrote:
| Thank you very much for your answers.
|
| I finally noticed that the issue comes from the numerical optimization, in
which I use the class MFuncGrad of the package RcppNumerical. Is there any
problem in using this class? This is the only wa
On 20 October 2022 at 14:46, Ivan Krylov wrote:
| В Thu, 20 Oct 2022 12:43:30 +0200
| Elysée Aristide пишет:
|
| > What I understood is that it is better to use Rcpp functions. So I
| > used:
| >
| > Rcpp::Rcout << "beta: \n";
| > Rcpp::print(betacpp);
| > Rcpp::Rcout << "log-likelihood: " <<
On 17 October 2022 at 13:20, Göran Broström wrote:
| Thanks Ivan,
|
| I found two simple ways to convert this old file to UTF-8:
|
| (i) In emacs, C-x f (default is utf-8)
That's a good ti[. I had actually hand-edited two lines down to 'seven bits'
instead of this. Umlaute, accents and spec
On 7 September 2022 at 11:58, Ivan Krylov wrote:
| there at all. On the other hand, my package that uses the
| R_InitOutPStream and R_Serialize entry points seems to have passed the
| CRAN review. A table of all public entry points including short
| descriptions and whether they allocate could be
Based on further (off-list) follow-ups with Simon and Uwe, the situation can
now be summarized as follows:
- there appears to be no word about non-leak errors reported by valgrind in
the official documentation; I will have to plead that those with the power
to amend these documents maybe
Dear CRAN Team,
On 18 August 2022 at 06:55, Dirk Eddelbuettel wrote:
|
| [ Five days ago, I sent (most) of the message below to a CRAN team member. I
| have not had a reply, and it now appears that we are asked to email here so I
| am resending. ]
An answer would be much appreciated after the
On 8 July 2022 at 14:23, Plamen Mirazchiyski wrote:
| to what actual the problem is. Unfortunately, the r-svn repository on
| GitHub does not have the possibility to report this as an issue.
Please see https://bugs.r-project.org/but also see old mailing list (and
elsewhere) posts on how to
On 11 May 2022 at 19:07, Daniel Kelley wrote:
| Today I tried to update the CRAN oce package to version 1.7-3, to address a
problem with 1.7-2 on one of the CRAN build platforms. I used
devtools::release() to submit it. I just received the text I've pasted at the
bottom of this email. I've
On 23 April 2022 at 18:05, Greg Hunt wrote:
| I want to incorporate a static PDF (created from LaTeX source separately
| from the R package) into an R package as a vignette.
I do that in several vignettes via a zero-depends approach described by Mark
in this blog post:
https://www.markvanderloo
Two (related) questions:
1. Could pandoc be installed on the macoOS machines CRAN uses? If not, could
R Core devise a way to have a registered vignette builder fail gracefully?
2. Could CRAN define and publish a minimal set of external applications
available on each build + test machine?
On 16 March 2022 at 14:01, Henrik Bengtsson wrote:
| Related to this, there's also been discussion (here or on R-devel), of
| having `R CMD build` produce identical tarballs when the input doesn't
| change, but the injection of `Packaged: ; ` to the
| `DESCRIPTION` file prevents this. If I recall
On 8 March 2022 at 18:01, Sebastian Meyer wrote:
| Not an expert here, but that does seem to be possible, according to WRE
| (Section 4.3.2):
|
| > It is possible to run all the examples, tests and vignettes covered by R
CMD check under valgrind by using the option --use-valgrind. If you do th
On 27 January 2022 at 11:18, Ben Bolker wrote:
|I have spent hours trying to understand the scoping behaviour of
| testthat, mostly without success.
It may bear repeating that use of a test runner package is NOT required by
CRAN Repo Policy, Writing R Extensions, or any other official text
On 11 January 2022 at 18:44, riccardo wrote:
| Hallo,
|
| I wish to submit the following error rising running an example in a rcpp
| function *only *in Debian check:
|
| > ### Name: least_square_plane_rcpp
| > ### Title: returns the coefficients of the least square plane and the
| > ### rela
Ezra,
[ A gentle plea: Can you please turn the encryption signing off when you
reply? Thank you, it really confuses one of the email programs I use. ]
What you state in passing is somewhere between misleading and just wrong,
likely due to a misunderstanding. Quoting from your email:
a stu
On 23 December 2021 at 11:07, Tomas Kalibera wrote:
| You can have a look at CRAN package Rblpapi which is using an external DLL.
Yes with one big caveat: You have to make sure the library follows what is
the "hour-glass pattern": it needs to have an internal (the "narrow" part) C
library coveri
On 17 December 2021 at 09:51, Simon Urbanek wrote:
| Sure, installed pandoc 2.16.2.
Perfect, thank you!
Dirk
| Cheers,
| Simon
|
|
| > On Dec 17, 2021, at 9:21 AM, Dirk Eddelbuettel wrote:
| >
| >
| > CRAN results flag NOTEs on the two platforms
| > r-release-macos
CRAN results flag NOTEs on the two platforms
r-release-macos-x86_64
r-oldrel-macos-x86_64
because `pandoc` is apparently missing. These platforms being somewhat
common, could pandoc be installed? Or are they running such a jurassic
version that no premade pandoc is available _anywhere_ ?
On 5 December 2021 at 17:23, Travers Ching wrote:
| I see that there doesn't exist a Solaris flavor on any CRAN check page.
| However, I'm certain that Solaris was being checked up until very recently.
|
| Is this just temporary?
|
| Is there any information for the future of Solaris on CRAN?
Agreed. I have used `.pkgenv` in a few packages (digest, rpushbullet, ...),
and usually added a comment that it is package-global.
And so have a few others:
https://github.com/search?l=R&q=org%3Acran+pkgenv&type=Code
Dirk
--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
_
On 9 October 2021 at 12:08, Ben Bolker wrote:
|FWIW there is some machinery in the glmmTMB package for querying,
| setting, etc. the number of OpenMP threads.
|
| https://github.com/glmmTMB/glmmTMB/search?q=omp
https://cloud.r-project.org/package=RhpcBLASctl
Dirk
--
https://dirk.eddelbu
While we generally get an email about these things, CRAN appears to have
closed shop for a week to take a well deserved break until September 1.
Or so the message says---the hourly CRANberriesFeed cron job saw packages
being processed, but that too is not uncommon when the queues get cleared.
T
If look closely enough at _Writing R Extensions_ you notice that it mentions
'configure.win' over half a dozen times. A powerful trick is to then use the
fact that there are other packages on CRAN, in fact almost 18k of them.
And e.g. this search
https://github.com/search?q=org%3Acran+config
Section 2.7.3 'C++ Support' of the R Admin manual says, "C++ is not used by R
itself, but support is provided ...". This is all stored from when R itself
is configure (prior to compiling) and override-able in package configuration
(Section 2.7.3 covers that) but as that in other places _it all d
Russell,
On 24 July 2021 at 12:04, Russell Almond wrote:
| I'm working on a package called RNetica which links to a 3rd party
| library: Netica. Netica is available in both static (libnetica.a) and
| shared (libnetica.so) version (also Netica.dll for windows, but that is
| a separate topic)
On 8 July 2021 at 10:41, Uwe Ligges wrote:
| It was likely an interim version of Rcpp (which never made it to CRAN)
| that was causing trouble.
Yup, our bad.
While we test against 2300+ reverse depends, we only test against them _under
the most recent versions we have seen_ which affects the R
On 1 July 2021 at 20:00, Lluís Revilla wrote:
| I have a question related to changing maintainers.
| What happens when the old/current maintainer does not respond to
| emails or other methods of contact?
| Would the new maintainer need to wait until the package is removed
| from CRAN to submit it
On 24 June 2021 at 16:31, Duncan Murdoch wrote:
| This does the full compile again, so it's slow.
ccache fixes that (as it has its own cache). It also works on macOS.
Dirk
--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
__
R-pack
Hi Greg,
On 24 June 2021 at 12:15, Greg Minshall wrote:
| when developing packages, my current work flow is to change the code,
| (re-)build the package, detach/load the package, test (to find the
| N+1'st bug, sigh).
|
| the building step takes tens of seconds.
You may benefit from looking in
On 10 June 2021 at 09:22, J C Nash wrote:
| Thanks to help from Duncan Murdoch, we have extracted the nls() functionality
to a package nlspkg and are building
| an nlsalt package. We can then run nlspkg::AFunction() and
nlsalt::AFunction() in a single script to compare.
| This works great in Li
On 4 June 2021 at 16:21, Balasubramanian Narasimhan wrote:
| Suggests" would trigger an attempt to install gurobi, which is not on CRAN.
To my understanding that is not the case. It would only do so if and when
install.packages() is asked to also install packages in Suggests:. And point
of Sugge
Danielle,
On 26 May 2021 at 21:23, Danielle Maeser wrote:
| Please excuse the very simple question, but I received the following
| message from a CRAN maintainer, and I am not sure what code to include
| inside of the \donttest{}. This is meant to enclose code that typically
| should be run, but
On 12 May 2021 at 11:03, Eric Dunipace wrote:
| I did some searching and wasn’t able to find a good answer to my question, so
I hope that someone here has knowledge of how to fix the problem.
|
| I’m currently trying to create an R package that bundles the CGAL header
files (http://www.cgal.or
101 - 200 of 707 matches
Mail list logo
