On 30 March 2021 at 15:19, Florian Rupprecht wrote:
| I am trying to add an optional system/C++ library to my package and was
| wondering if anyone could point me in the right direction on how to do this
| in the R package ecosystem.
|
| To be concrete, I want my graphics device package httpgd
On 29 March 2021 at 23:29, Rasmus Liland wrote:
| can someone please guide me a little in
| installing RODBC[1] on FreeBSD 13?
|
| I believe it depends on unixodbc[2], but
| the compilation stops with at not
| finding unixodbc (I think):
|
| rasmus@iselin ~ % mkdir ~/src/RODBC
|
Hi Ivan,
On 27 March 2021 at 19:11, Ivan Krylov wrote:
| Dirk, thank you a prompt reply!
|
| I see the issue you took part in solving:
| https://github.com/x13org/x13binary/issues/49
Yes. Temporary files are now written to a temporary directory which I make
sure to remove at end of examples
On 27 March 2021 at 17:26, Ivan Krylov wrote:
| Dear R-package-devel,
|
| My package "albatross" doesn't contain any compiled code and has been
| checked on both a POSIX-compatible system and on Windows, so I wasn't
| expecting any problems after seeing it pass CRAN "pretest" checks.
| Imagine
Sorry for the noise. I was (clearly) unaware of one more message in the queue
for this folder. My apologies. Looking forward to a refreshed and
strengthened check farm for CRAN.
Dirk
--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Dear Uwe,
CRAN processing appears to have halted completely, with packages stuck in
incoming. I do not recall seeing an announcement, or a note on the site so I
am assuming this was unplanned. Is there an expected resolution time?
Many thanks as always for keeping the CRAN machine humming,
On 16 March 2021 at 06:48, Duncan Murdoch wrote:
| On 16/03/2021 5:58 a.m., Chris Evans wrote:
| You have 5 workflows, and their current content doesn't appear to match
| the results on your actions page. Pick one, run it, and I'll see if I
| can spot the reason for a failure.
More
On 7 March 2021 at 12:54, Rolf Turner wrote:
| Dirk Eddelbuettel wrote:
| By "in base R" do you mean that one can do this *without* invoking
| the R.rsp package?
Exactly. Zero added dependencies.
| What I understand you to be saying is that you can add four or five
| lines to a
On 5 March 2021 at 21:07, Ben Bolker wrote:
|Thanks! Now I see this is in Writing R Extensions, should have
| looked more carefully ...
There is also a very good (and frequently linked-to) post by Kevin on SO
which lists the different ways in the C API of R, and the Rcpp wrapper which
On 5 March 2021 at 15:41, Duncan Murdoch wrote:
| On 05/03/2021 2:40 p.m., Henrik Bengtsson wrote:
| > Thank you. Glad to hear it's useful.
| >
| > This plain TeX/LaTeX vignette engine is implemented using base R. If
| > someone is willing to drive the efforts, I think it's not too much
| >
Martin,
Both questions are FAQs. Searches at e.g. StackOverflow might have lead you
to a solution (and you can search there, key is to add the tag i.e. make [r]
or [data.table] part of the search term).
The first one is a generic package programming question. You can use Imports:
in
On 21 February 2021 at 19:52, Karim Rahim wrote:
| I'm in the process of incorporating some improvements that I pulled from
| github.
| I am getting a warning and a note. These occur when I run
|
| R CMD check --as-cran fftwtools_0.9-10.tar.gz
|
| 1.
| * checking whether package ‘fftwtools’
On 11 February 2021 at 11:30, Balasubramanian Narasimhan wrote:
| If GNU make is acceptable as a system requirement, you can get any R
| configuration/runtime variable in Makevars, e.g.
|
| R_ARCH=$(shell $(R_HOME)/bin/Rscript -e 'cat(.Platform$r_arch)')
You can switch to backticks to not
On 1 February 2021 at 20:21, Jose Barrera wrote:
| Many thanks for your help Thierry but unfortunately I can't see the link
| between your first reply and my issue (of course, that's my fault).
Thierry very gently (yet correctly) suggested to have the "cached" results as
"precomputed"
On 28 January 2021 at 16:50, Duncan Murdoch wrote:
| Thanks Dirk, Neal and Nathan. I ended up going with Dirk's suggestion.
|
| So far I haven't got it to work in 3.2.0; I probably won't put much
| effort into supporting that old version. But it's fine in 3.4.0 and
| 3.5.0, and I'm trying
The Rocker Project provides both rocker/r-ver (with package snapshotting) as
well as the (much smaller, just R) rocker/r-base images which are then passed
on to the Docker team to become the official r-base image.
These go back to 3.1.3 with (almost if not all) interim releases, see
Hi James,
On 22 January 2021 at 15:42, James Pustejovsky wrote:
| Thanks very much for your input! By "patch it out" do you mean modify my
| package description for the Debian distribution only? Would it work to
And code / content! Can't just alter the DESCRIPTION if the Rd still call
Hi James,
On 22 January 2021 at 14:29, James Pustejovsky wrote:
| I'm writing to see if anyone has suggestions for how to handle an issue I'm
| facing with the clubSandwich package (
| https://CRAN.R-project.org/package=clubSandwich; Github repo:
| https://github.com/jepusto/clubSandwich). The
On 19 January 2021 at 21:51, Frantisek Bartos wrote:
| I wanted to submit a new version of my package and I encountered issues
| with boost when compiling it on R devel version for windows. (Please excuse
| my stupidity, but I'm a complete noob in regards to compilers and C++)
|
| A full error
On 19 January 2021 at 17:45, Florian Rupprecht wrote:
| Hello,
|
| the CRAN checks show an error for my newly released package 'httpgd' with
| 'r-patched-solaris-x86':
|
| Error: C++17 standard requested but CXX17 is not defined
|
| It seems like 'rcppsimdjson' had the same problem (
|
On 14 January 2021 at 15:32, Rampal Etienne wrote:
| I have a package with FORTRAN code using REAL(16) for accurate
| computations. This package has been on CRAN for several years, but now
| it suddenly fails on M1 Macs, apparently due to the use of REAL(16) - it
| cannot handle higher
On 8 January 2021 at 11:32, Henrik Bengtsson wrote:
| R CMD check --as-cran will give an ERROR if not all Suggest:ed
| packages are installed and available when it runs.
This can be overridden with R_CHECK_FORCE_SUGGESTS_=false which may be
helpful if Suggests: has a long tail of dependencies,
On 12 December 2020 at 16:24, Michael L Friendly wrote:
| I got the email below concerning 3 of my packages but wonder if they are
false alarms or
| if not, how to locate & fix the problem.
|
| This concerns packages: ...
|
| Suggested packages should be used conditionally: see
On 30 November 2020 at 11:54, Duncan Murdoch wrote:
| On 30/11/2020 11:31 a.m., Dirk Eddelbuettel wrote:
| >
| > On 30 November 2020 at 11:27, Duncan Murdoch wrote:
| > | I think that C++11 isn't a requirement of RcppArmadillo, it's an option
| >
| > It is as of the 10.* seri
On 30 November 2020 at 11:27, Duncan Murdoch wrote:
| I think that C++11 isn't a requirement of RcppArmadillo, it's an option
It is as of the 10.* series of Armadillo and hence RcppArmadillo 0.10.*
Dirk
--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
On 30 November 2020 at 17:06, Mark Clements wrote:
| [Apologies for cross-posting]
|
| A colleague uses a package I maintain (rstpm2) as a dependency in their
| package (rsimsum) with testing using GitHub Actions. They found that
| testing failed against R versions 3.3, 3.4 and 3.5 because
On 27 November 2020 at 11:18, jérémy Gelb wrote:
| I plan to submit a package I created called spNetwork. The package
| uses both Rcpp and parallelization to ensure reasonable calculation
| time. However, it is currently not possible to pass a compiled
| function to a child process. The
On 27 November 2020 at 12:05, Benjamin Becker wrote:
| I want to add 'Rglpk' as a dependency to a package. On windows and MacOS
| everything works fine, but there seem to be installation issues with the
| underlying optimization software 'GLPK' on Linux systems. The problem
| occurs when
Jon,
On 16 November 2020 at 12:27, Jon Davidson wrote:
| I am trying to build an R package with a manually compiled .so file. To do
| so, I have included a call to useDynLib() in my NAMESPACE file.
In general you would not need to do that, or do that:
- A package knows how to turn files in
On 27 October 2020 at 12:21, Helmut Schütz wrote:
| is there somewhere an official statement about the maximum run-times of
| examples in vignettes?
Seven minutes is excessive. I have (long) gone by the rule of "about one
minute" each for tests and examples. Rcpp is slightly above [1],
On 25 October 2020 at 11:54, Michael Dewey wrote:
| I think the protocol is to always bump the version number for a
| re-submission even when the first one did not get onto CRAN.
No, as Hong wrote two days ago here in another thread:
My personal opinion is that as long as a package
On 18 October 2020 at 20:56, Rafael H. M. Pereira wrote:
| The CRAN incoming Dashboard indicates that the status of my package (r5r)
| is "pending", which means 'the CRAN maintainers are waiting for an action
| on your side. You should check your emails!'.
AFAICT the text there is wrong: it
Hugh,
The different SAN/ASAB/UBSAN/... analysers depend critically on _exactly how_
the instrumentation is setup. That make the whole setup analysis a little
brittle, and it is a real shame that neither CRAN nor some of the entities
supposedly here in order to support R users and developers
On 15 October 2020 at 10:36, Joseph Park wrote:
| Apologies for the mis-directed reply, and, imprecise syntax/context re
| environment variable.
|
| Just to close the loop, it seems that using a -D macro assignment inside
| the make command (macro?) is interpreted as a make option:
(I think
On 14 October 2020 at 15:56, Joseph Park wrote:
| Dear R-devel,
|
| The Writing R Extensions manual states:
|
| 6.14 Platform and version information
| The header files define USING_R, which can be used to test if the code
| is indeed being used with R.
|
| I suppose this only applies to
On 13 October 2020 at 17:54, Helmut Schütz wrote:
| in one of my packages I import from package xlsx, which itself imports
In case you were unaware there is also openxlsx which may be sufficient for
your import/export needs, and which is does not need a Java toolchain.
Dirk
--
On 3 October 2020 at 09:54, Hadley Wickham wrote:
| I think this is a bit of an oversimplification, especially given that
| "compatibility" is not symmetric. For example, you can include MIT license
| code in a GPL licensed package; you can not include GPL licensed code
| inside an MIT licensed
On 2 October 2020 at 14:44, Jeff Newmiller wrote:
| if you want clarity in the minds of _users_ I would beg you to split the code
into two packages. People will likely either be afraid of the GPL bogey man and
refrain from utilizing your MIT code as permitted or fail to honor the GPL
terms
On 1 October 2020 at 19:13, Max Turgeon wrote:
| Hi Nicholas,
|
| I see two potential solutions, maybe other people will suggest different ones:
|
| 1. You can make the evaluation of the whole vignette dependent on the data
packages being available. Here's an example from one of my packages:
On 26 September 2020 at 14:42, Dirk Eddelbuettel wrote:
|
| On 26 September 2020 at 14:20, Duncan Murdoch wrote:
| | On 26/09/2020 12:54 p.m., Dirk Eddelbuettel wrote:
| | Hmmm, that's strange. From what I can see you only get the --lua-filter
| | if pandoc 2.0 is available:
| |
| |
https
On 28 September 2020 at 17:17, Georgi Boshnakov wrote:
| I am using package 'revdepcheck' to check reverse dependencies of a package
and it works great. But now I have a scenario such that I wish it to use a
local version of one of the dependencies of the checked package and am not able
to
On 26 September 2020 at 14:20, Duncan Murdoch wrote:
| On 26/09/2020 12:54 p.m., Dirk Eddelbuettel wrote:
| Hmmm, that's strange. From what I can see you only get the --lua-filter
| if pandoc 2.0 is available:
|
|
https://github.com/rstudio/rmarkdown/blob
On 26 September 2020 at 11:50, Duncan Murdoch wrote:
| On 26/09/2020 9:14 a.m., Dirk Eddelbuettel wrote:
| >
| > I had a submission fail and bomb with this error on Windows:
| >
| >Flavor: r-devel-windows-ix86+x86_64
| >Check: re-building of vignette outputs,
I had a submission fail and bomb with this error on Windows:
Flavor: r-devel-windows-ix86+x86_64
Check: re-building of vignette outputs, Result: WARNING
Error(s) in re-building vignettes:
--- re-building 'vignettefilename.Rmd' using rmarkdown
pandoc.exe: unrecognized option
On 18 September 2020 at 18:38, Nuria Perez-Zanon wrote:
| I am maintaining a package call CSTools which is aimed for
| post-processing climate simulations.
[...]
| library(CSTools)
| library(qmap)
You never use library() in a package. Rather, you declare dependency
relationsships via
On 15 September 2020 at 10:27, Cesko Voeten wrote:
| the language provides an obvious way to do this, why write a semantic kludge
As already said, Occam's Razor give the answer: keep it simple(r) and don't
write the kludge. Stick it all into a package, load the package on every node
and use
Hi Jens,
On 11 September 2020 at 21:00, Dr. Jens Oehlschlägel wrote:
| I can compile a package under clang++ with -stdlib=libstdc++, but with
-stdlib=libc++ I get
|
| "
| In file included from
/home/jo/R/x86_64-pc-linux-gnu-library/4.0/Rcpp/include/Rcpp/r/headers.h:67:
|
e I emailed
earlier and do something like
fftw3 development package: libfftw3-dev (deb), . (rpm)
Maybe someone can help with the rpm package name.
Cheers, Dirk
|
| Kind Regards,
| Karim
|
|
|
|
|
| On Fri, Sep 11, 2020 at 11:20 AM Dirk Eddelbuettel wrote:
| >
| >
| > On 10 Se
> Thanks,
| >
| > That may be it. It is a missing dependency.
| >
| > It's been a while and I'm not sure which package exposes fftw3.h ...
| >
| > Karim
| >
| > On Thu, Sep 10, 2020 at 8:16 AM Dirk Eddelbuettel wrote:
| >
| >>
| >> On 9 September 202
On 9 September 2020 at 23:45, Karim Rahim wrote:
| sudo apt-get install -y fftw3
Or maybe rather
sudo apt-get install libfftw3-dev
to get the development headers?
Dirk
| Then try again.
|
| Let me know if it doesn't work.
|
| Cheers!
| Karim
|
| On Wed, Sep 9, 2020 at 10:27 PM Max
On 9 September 2020 at 10:33, Tomas Kalibera wrote:
| Spending much more time for optimizing of the 32-bit builds may not be
| worth the effort (and neither on the R/CRAN side).
As we are in conditional mode: maybe that could be recognized by adding an
explicit flag allowing us to disable
On 2 September 2020 at 23:59, Emmanuel Blondel (GMAIL) wrote:
| Dear all,
|
| I've received a notification of errors from CRAN on some package (zen4R)
| recently updated, being asked to fix within the 2 weeks before archiving.
|
| The error deals with 'keyring' package import at test time, on
On 26 August 2020 at 08:46, Dirk Eddelbuettel wrote:
| One way to ensure the last point is to have a file
|
| ~/.R/check.Renviron-Rdevel
|
| which I had (but where I had commented out 'incoming' as it can take a
| moment). Current values below, with thanks to Uwe for the reminder.
And I
Ok, Uwe was kind enough to take me to task off-list and I can now confirm
that I _can_ replicate the URL issue locally by ensuring all three of
- recent enough r-devel build (that was true, I may add that the
rocker/r-devel and rocker/drd containers I look after can help)
- built with
On 26 August 2020 at 14:34, Vincent van Hees wrote:
| Addressing the errors is not the problem. I want to be able to detect these
| problems when I do: R CMD check --as-cran.
You cannot :-/. I pointed that out to CRAN maintainers a few times myself.
| At the moment, I can only detect the
On 19 August 2020 at 13:01, Gábor Csárdi wrote:
| >From https://cran.r-project.org/doc/manuals/R-exts.html:
|
| > The script is run in a separate R environment containing the following
| variables: R_PACKAGE_NAME (the name of the package), R_PACKAGE_SOURCE (the
| path to the source directory of
On 5 August 2020 at 16:25, William Dunlap wrote:
| You might make a second package that depends only on nimble and your
| main package can then suggest that second package and JAGS.
Nice. "We can solve any problem by introducing an extra level of indirection."
See
On 3 August 2020 at 10:07, Dirk Eddelbuettel wrote:
| Tracing it:
|
| edd@rob:~$ locate libnode.so.64
| /usr/lib/x86_64-linux-gnu/libnode.so.64
| edd@rob:~$ dpkg -S $(locate libnode.so.64)
| libnode64:amd64: /usr/lib/x86_64-linux-gnu/libnode.so.64
| edd@rob:~$
|
| Looks like
On 3 August 2020 at 16:42, Paul Buerkner wrote:
| Dear R community,
|
| in an effort to re-submit one of my packages (thurstonianIRT) to CRAN
| because of some test failures after updates of other packages, I get the
| following error from the CRAN debian installation, which I don't know how
|
Hi Adelchi,
On 28 July 2020 at 11:46, Adelchi Azzalini wrote:
| When I updated package mnormt to version 2.0.0 in June (now at 2.0.1),
| at the stage of --as-cran checking, there was a compilation error,
| which was overcome by setting the
|
| Depends: R (≥ 4.0.0)
|
| With this
Helmut,
For previous uploads you affirmed that you read the CRAN Repository Policy
which states
* The code and examples provided in a package should never do anything
which might be regarded as malicious or anti-social. The following are
illustrative examples from past
On 17 July 2020 at 14:58, Benjamin Christoffersen wrote:
| Quick guess. After changing
| > SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11 -pthread -O3 -Wextra
-Wall -Wno-unknown-pragmas -Wno-return-type -Wno-ignored-attributes
-Wno-cast-function-type -Wno-error=cast-function-type")
|
| to
Hi Lisa,
On 28 June 2020 at 20:32, Lisa GM wrote:
| Thank you so much for your quick reply. I'm not particularly set on the
| 'inline' package especially if it's becoming outdated. I looked into using
Please report bugs or shortcomings in an issue ticket at GitHub. I am also
its maintainer and
Lisa,
Sorry, I misread your code. There is a possible array overrun, so we need
argument n and p, apparently. A likely better version, and demo running the
right code are below. The rest of the reasoning likely stands, methinks.
Code
Lisa,
One can do what you do, but it is fraught with some difficulties (as you
experienced) and even more so once you try to do this portably. Helper
packages exists: the `inline` package is the oldest of this class and still
supports the .C() interface you used here. And which for a few years
On 26 June 2020 at 19:16, Zehao Xu wrote:
| Package suggested but not available for checking: 'actigraphy'
|
| ```
|
| This stackoverflow
https://stackoverflow.com/questions/51453717/issue-with-r-package-check-on-windows-package-suggested-but-not-available-str
can solve you problem
No,
On 25 June 2020 at 18:59, Uwe Ligges wrote:
| On 25.06.2020 18:26, Guo, Wei (NIH/NIMH) [C] via R-package-devel wrote:
| > Dear all,
| > I have an error about R dependencies as shown above.
| > Strong dependencies not in mainstream repositories:
| >actigraphy, r.jive, SpatioTemporal
| >
Hi Daniel,
On 4 June 2020 at 08:19, Daniel Lüdecke wrote:
| the package in question is "insight"
| (https://cran.r-project.org/package=insight). Since a few days, the test for
| the panelr-package fails, because panelr itself fails on many systems
|
On 2 June 2020 at 18:32, R. Mark Sharp wrote:
| I apologize for my obvious (in hindsight) error in bringing up the topic. I
will bring up one example, because of your request. Google has listed GPL-1, 2,
and 3 as one of several licenses that are restricted and cannot be used by a
Google
On 2 June 2020 at 10:06, R. Mark Sharp wrote:
| The GPL-2 and GPL-3 licenses are apparently sufficiently ambiguous in the
legal community that some companies avoid them.
Wittgenstein: 'That whereof we cannot speak, thereof we must remain silent'
This is a mailing list of the R project. R is
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
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):
|
|
Hi Chris,
On 12 May 2020 at 18:00, Chris Paciorek wrote:
| 1) Does anyone happen to know why this problem with Eigen is occurring
| with clang11?
Compilers change. Languages changes. Requirements change.
Many of us have been there (e.g. witness the "excitement" about gcc-10 last
December
On 11 May 2020 at 13:13, Joris Meys wrote:
| To add to the suggestion of Gabor and Duncan, it might be a good idea to add
a packageStartupMessage that warns the user about the problem when running on a
32bit system. You can easily extract that info from R.Version()$arch . That
might help
Jim,
This is not the list for Rcpp discussions, as the package and its
documentation have been saying for a decade you should subscribe
to the rcpp-devel list.
Allow me to add one item:
On 5 May 2020 at 19:58, James Owen Ramsay, Dr. wrote:
| I’m working on max OS-X 10.15.3, using R 4.0.0, and
On 30 April 2020 at 17:43, Hugh Parsonage wrote:
| For reference, the file mode was not set as executable; however,
| `file` was reporting a particular file (only one of several .fst
| files) as a DOS executable (COM, 0x8C-variant), which according to
| comments in the code of "file" appears to
Hugh,
On 27 April 2020 at 16:02, Hugh Parsonage wrote:
| I would like to include some fst files (produced by fst::write_fst) in
| inst/extdata so that (a) users can update them between releases and
| (b) to take advantage of fst's benefits. However, when I do this and
Good idea, it is a very
Stuart,
As a follow-up, the errors are of the '*** caught illegal operation ***'
variety which is frequently seen when different compiled components (and
particularly C++ ones) are out of sync with respect to their toolchains.
So I would suggest a clean rebuild, but given that it is at CRAN
On 23 April 2020 at 19:06, Stuart Lacy via R-package-devel wrote:
| I've been told to fix the problems that my package 'multistateutils' has on
| OSX:
| https://cran.r-project.org/web/checks/check_results_multistateutils.html
|
| This is seemingly something to do with my Rcpp code, but I can't
On 6 April 2020 at 08:38, Ben Bolker wrote:
| Just reply to the CRAN maintainers and explain this situation. It¨s
| slightly buried, but the e-mail you received does say:
|
| > If you are fairly certain the rejection is a false positive, please
reply-all to this
| > message and explain.
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
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
On 13 March 2020 at 14:17, Dirk Eddelbuettel wrote:
|
| On 13 March 2020 at 11:53, Zack McCaw wrote:
| | Hello all,
| |
| | I am attempting to submit a package (https://github.com/zrmacc/Temporal)
| | that uses RcppArmadillo. The package builds successfully locally (on Mac)
| | and on Windows
On 13 March 2020 at 11:53, Zack McCaw wrote:
| Hello all,
|
| I am attempting to submit a package (https://github.com/zrmacc/Temporal)
| that uses RcppArmadillo. The package builds successfully locally (on Mac)
| and on Windows. However, when submitting to CRAN, it fails to build on
| Debian
On 12 March 2020 at 20:14, Ivan Krylov wrote:
| On Thu, 12 Mar 2020 15:16:13 +
| Carsten Croonenbroeck wrote:
| >> Where a large amount of data is required (even after compression),
| >> consideration should be given to a separate data-only package which
| >> can be updated only rarely
On 23 February 2020 at 08:45, Daniel Sjoberg wrote:
| I have a few continuous integration sites set up (e.g. Travis CI) to check
| packages I've written. To install packages I've used `install.packages(...,
| repo = "http://cran.us.r-project.org;). All the CI checks began failing
| last week
Hi Joseph,
On 19 February 2020 at 21:59, Joseph Wood wrote:
| As the subject says, what is the best way to specify a minimum
| compiler version in the DESCRIPTION file.
In short: you can't. Read on.
| I only found 2 packages on CRAN that have a minimum requirement for
| GCC, however they
On 5 February 2020 at 08:39, Brian G. Peterson wrote:
| We've noticed over the past week that Winbuilder/R-Hub's 'experimental'
Are you refering to winbuilder, or to rhub?
| Rtools4 toolchain images for Windows are approximately 4-5x slower than
| all other containers to build and check
On 5 February 2020 at 11:47, Ralf Stubner wrote:
| On Tue, Feb 4, 2020 at 5:51 PM Guido Kraemer wrote:
| > I have also set `~/.R/Makevars.win` as suggested in the manual "Writing
| > R extensions", Section 1.2.5 "Using C++14 code".
|
| What exactly do you have in src/Makevars.win? Just the
On 4 February 2020 at 17:51, Guido Kraemer wrote:
| I am testing building a package on Windows. The package requires C++14.
You will have to wait.
The current Rtools is at g++ 4.9.3 which (barely) supports C++11. We all
keep our fingers crossed as the replacement Rtools would bring g++ 8.*.
On 4 February 2020 at 08:15, Marcelo Araya Salas wrote:
| I found it here:
|
| ftp://cran.r-project.org/incoming/archive/
|
| not sure what that's suppose to mean
"It's dead."
It generally means you will have gotten an email with the reasoning. But
whatever is in archive/ is no longer
On 4 February 2020 at 15:04, GD wrote:
| I have a very specific question regarding the licensing of my R package.
|
| Here is the details: I have an R package under the MIT license so the
| DESCRIPTION file contains the field `License: MIT + file LICENSE` and
| the LICENSE file contains the
On 4 February 2020 at 10:28, Helmut Schütz wrote:
| Possibly it went unnoticed.
A follow-up email may be a good idea.
| My first new package took two days from submission to acceptance
| including answering questions in July last year.
It is _much_ more clogged now as you can tell via a
On 3 February 2020 at 23:58, Ivan Krylov wrote:
| On Mon, 3 Feb 2020 13:30:11 -0600
| Spencer Graves wrote:
|
| > logo.jpg <- paste(R.home(), "doc", "html", "logo.jpg", sep
| > = .Platform$file.sep)
|
| I wonder whether file.path(R.home('doc'), 'html', 'logo.jpg') would be
| more portable.
On 3 February 2020 at 09:03, profjohn wrote:
| While there are huge benefits to upgrading, there is pain. It's that
We have a dedicated mailing list r-sig-debian for use of R on operating
systems that are .deb based. It is low volume, and has high signal / noise.
So I would cordially invite
On 2 February 2020 at 21:47, Ben Bolker wrote:
| Maybe an Rhub glitch. I just ran R CMD check with a recent r-devel
| (2019-12-03 r77509) on Ubuntu 16.04 with no problems.
Is there a reason that keeps _both_ of you on Ubuntu 16.04 which has been
replaced _nearly two years ago_ by the
On 31 January 2020 at 09:11, Borini, Stefano wrote:
| Thanks. What is the recommended strategy in this case? Keep submitting and
patching until it passes?
Standard debugging, and (as Uwe already said) win-builder for that OS, rhub
for others, and asking here, ... Imperfect, but doable.
It
On 30 January 2020 at 21:40, Borini, Stefano wrote:
| I am currently trying to submit a package to CRAN, and I see no problems in
running the test on my package on Linux ubuntu 18.04 and the latest compiled R.
| Is there a docker image of the CRAN automatic build system so that one can
try to
Guido,
On 29 January 2020 at 15:11, Guido Kraemer wrote:
| I am developing an R package that can make (optional, but strongly
| recommended) use of a number of external compression algorithms. What is
| the best strategy if I want to distribute this as an R package? Because
It's actually a
On 28 January 2020 at 19:47, EcoC2S - Irucka Embry wrote:
| Hi everyone, I am receiving the following NOTE when checking my package
| 'iemisc':
|
| * checking top-level files ... NOTE
| Non-standard file/directory found at top level:
|'cran-comments.md'
|
| Will someone please tell me the
201 - 300 of 579 matches
Mail list logo
