On 14 November 2023 at 11:06, Andreas Tille wrote:
| Am Mon, Nov 13, 2023 at 07:23:06AM -0600 schrieb Dirk Eddelbuettel:
| > Most of these are not in Debian but I think we need binary rebuilds of
| >
| >irlbabecause of headers
| >OpenMx becaus
On 14 November 2023 at 12:03, Deepayan Sarkar wrote:
| Are you suggesting that we should not be getting that by default? I
As I wrote in my message starting the thread:
Casual searching at the rlang repo doesn't reveal anything so pardon me for
asking here but what is a simple way to
On 14 November 2023 at 17:22, Lionel Henry wrote:
| Worth noting I'm using `xterm-color` instead of `ansi-color` in my
| comint buffers. IIRC the latter (which is builtin) didn't support some
| features. Not sure if that could explain the bad behaviour you've
| observed.
I was also thinking cli
si-colors-and-styles-
if (Sys.getenv("INSIDE_EMACS") != "")
Sys.setenv(NO_COLOR="TRUE")
See next message. Part of me still thinks rlang and cli do this wrong by
ignoring available env vars.
Thanks for the help, Dirk
| Best,
| Lionel
|
|
On 14 November 2023 at 12:26, Graham Inggs wrote:
| Hi Dirk
|
| On Tue, 14 Nov 2023 at 12:01, Dirk Eddelbuettel wrote:
| > Well that seems to be a) the wrong severity and b) the wrong package.
|
| Both are correct. We do not want rmatrix to migrate and break
| packages in testing.
Does
On 14 November 2023 at 12:26, Graham Inggs wrote:
| Hi Dirk
|
| On Tue, 14 Nov 2023 at 12:01, Dirk Eddelbuettel wrote:
| > Well that seems to be a) the wrong severity and b) the wrong package.
|
| Both are correct. We do not want rmatrix to migrate and break
| packages in testing.
Does
On 14 November 2023 at 12:30, Christoph Brinkhaus wrote:
| Source: rodbc
| Version: 1.3-21-1
| Severity: wishlist
|
| Dear Maintainer,
|
| please find attached the po file with the german translation.
| It is an update to the current po template.
| Please consider to apply it to the package.
On 14 November 2023 at 09:15, Graham Inggs wrote:
| Source: rmatrix
| Version: 1.6-2-1
| Severity: serious
| X-Debbugs-Cc: debia...@lists.debian.org
|
| Hi Dirk
|
| I'm opening this bug as a place for discussion and to track the
| affected packages. It can be closed once rmatrix and its
|
On 14 November 2023 at 09:15, Graham Inggs wrote:
| Source: rmatrix
| Version: 1.6-2-1
| Severity: serious
| X-Debbugs-Cc: debia...@lists.debian.org
|
| Hi Dirk
|
| I'm opening this bug as a place for discussion and to track the
| affected packages. It can be closed once rmatrix and its
|
nord8 ; blue
| nord15; magenta
| nord7 ; cyan
| nord5 ; white
| )))
| (setq xterm-color-names ansi-colours)
| (custom-theme-set-vari
Casual searching at the rlang repo doesn't reveal anything so pardon me for
asking here but what is a simple way to tell rlang to NOT do fancy pants
color error backtraces? At least under the theme I use ("nord", for Emacs)
it basically nixes readability by leaving a 'dark on dark' default.
On 13 November 2023 at 16:46, Ivan Krylov wrote:
| Hello Christiaan and welcome to R-package-devel!
Seconded but PLEASE do not send large attachments to the list and all its
subscriber. Point us to your code repository, you will like get a kind
response from a volunteer or two peeking at it.
Avi,
Might be toolchain-dependent, might be options-dependent--it built fine here.
Easier for you to vary option two so maybe try that?
Dirk
--
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
__
R-devel@r-project.org mailing list
On 10 November 2023 at 14:19, Martin Maechler wrote:
| >> 2. In the installed R in /where/you/want/R/to/go, there is no even
etc folder, there are only the folders bin, lib and share.
That would appear to be an error in the locally installed R.
What the package does has been discussed
On 10 November 2023 at 14:19, Martin Maechler wrote:
| >> 2. In the installed R in /where/you/want/R/to/go, there is no even
etc folder, there are only the folders bin, lib and share.
That would appear to be an error in the locally installed R.
What the package does has been discussed
On 7 November 2023 at 14:58, Andreas Tille wrote:
| Do you see any way to answer the question that is discussed in this
| thread by r2u how to know whether new Bioconductor packages might have
| new dependencies not yet packaged for Debian?
"Kinda. Sorta. Not fully." I have written related code
On 7 November 2023 at 14:58, Andreas Tille wrote:
| Do you see any way to answer the question that is discussed in this
| thread by r2u how to know whether new Bioconductor packages might have
| new dependencies not yet packaged for Debian?
"Kinda. Sorta. Not fully." I have written related code
On 7 November 2023 at 22:01, Charles Plessy wrote:
| One possible direction would be to leverage the work done by Dirk and
| others in r2u, where the Bioc transition is over, and for each package
| in Debian, look if the r2u equivalent has a dependency not in Debian.
|
|
On 7 November 2023 at 22:01, Charles Plessy wrote:
| One possible direction would be to leverage the work done by Dirk and
| others in r2u, where the Bioc transition is over, and for each package
| in Debian, look if the r2u equivalent has a dependency not in Debian.
|
|
On 31 October 2023 at 19:58, Ivan Krylov wrote:
| [...] The computers that helped launch the first
| people into space had 2 kWords of memory, but nowadays you need more
| than 256 MBytes of RAM to launch a bird into a pig and 10 GBytes of
| storage in order to compile a compiler. This is what
I have some better news. While we established that 'in theory' setting the
environment variable OMP_NUM_THREADS would help (and I maintain that it is a
great PITA that CRAN does not do so as a general fix for this issue) it does
*not help* once R is started. OpenMP only considers the variable
On 30 October 2023 at 13:17, Willem Ligtenberg via R-devel wrote:
| I just tried it on Ubuntu 23.10. It seems to just work.
| See screenshot here: https://nextcloud.wligtenberg.nl/s/jnbDT4ZiHw2JQ8H
| I should be using wayland, and as far as I know I haven't done anything
| special to make this
On 30 October 2023 at 12:23, Luigi Ballabio wrote:
| Hello Dirk, unfortunately I have no idea what can cause this — do you think it
| possible that the size of the wrappers crossed some threshold and relocations
| started to occur that weren't there before?
Adrian (CC'ed) supplied a merge
On 30 October 2023 at 12:23, Luigi Ballabio wrote:
| Hello Dirk, unfortunately I have no idea what can cause this — do you think it
| possible that the size of the wrappers crossed some threshold and relocations
| started to occur that weren't there before?
Adrian (CC'ed) supplied a merge
On 30 October 2023 at 09:20, Simon Urbanek wrote:
| > On 30/10/2023, at 8:38 AM, Dirk Eddelbuettel wrote:
| > On 30 October 2023 at 07:54, Paul Murrell wrote:
| > | I am unaware of any Wayland display support.
| > |
| > | One useful way forward would be an R package that provide
On 30 October 2023 at 07:54, Paul Murrell wrote:
| I am unaware of any Wayland display support.
|
| One useful way forward would be an R package that provides such a device
| (along the lines of 'Cairo', 'tikzDevice', et al)
As I understand it, it is a protocol, and not a device.
Several
The Debian package fails to build now on mipsel, a log is at [1]. The gist
seems to be a relocation error:
g++ -shared -Wl,-O1 -Wl,-Bsymbolic-functions -O0 -g0 -mxgot --param
ggc-min-expand=20 -DBOOST_NO_AUTO_PTR
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o
The Debian package fails to build now on mipsel, a log is at [1]. The gist
seems to be a relocation error:
g++ -shared -Wl,-O1 -Wl,-Bsymbolic-functions -O0 -g0 -mxgot --param
ggc-min-expand=20 -DBOOST_NO_AUTO_PTR
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o
On 28 October 2023 at 22:53, Sebastian Ramacher wrote:
| Source: quantlib-swig
| Version: 1.32-1
| Severity: serious
| Tags: ftbfs
| Justification: fails to build from source (but built successfully in the past)
| X-Debbugs-Cc: sramac...@debian.org
|
|
On 28 October 2023 at 22:53, Sebastian Ramacher wrote:
| Source: quantlib-swig
| Version: 1.32-1
| Severity: serious
| Tags: ftbfs
| Justification: fails to build from source (but built successfully in the past)
| X-Debbugs-Cc: sramac...@debian.org
|
|
On 27 October 2023 at 16:43, Andreas Tille wrote:
| Am Fri, Oct 27, 2023 at 09:19:22AM -0500 schrieb Dirk Eddelbuettel:
| >
| > | BioConductor has just released version 3.17. Since the next r-base
| >
| > Typo: 3.18
|
| Yes. Thanks for pointing this out.
|
| > | release is
On 27 October 2023 at 16:43, Andreas Tille wrote:
| Am Fri, Oct 27, 2023 at 09:19:22AM -0500 schrieb Dirk Eddelbuettel:
| >
| > | BioConductor has just released version 3.17. Since the next r-base
| >
| > Typo: 3.18
|
| Yes. Thanks for pointing this out.
|
| > | release is
On 27 October 2023 at 16:00, Andreas Tille wrote:
| Package: release.debian.org
| Severity: normal
| User: release.debian@packages.debian.org
| Usertags: transition
| X-Debbugs-Cc: r-bioc-biocgener...@packages.debian.org,
debia...@lists.debian.org
| Control: affects -1 +
On 27 October 2023 at 16:00, Andreas Tille wrote:
| Package: release.debian.org
| Severity: normal
| User: release.debian@packages.debian.org
| Usertags: transition
| X-Debbugs-Cc: r-bioc-biocgener...@packages.debian.org,
debia...@lists.debian.org
| Control: affects -1 +
Hi Jouni,
On 27 October 2023 at 13:02, Helske, Jouni wrote:
| Actually, the OMP_NUM_THREADS worked for vignettes and testthat tests, but
| didn't help with the examples. However, I just wrapped the problematic example
Now I am confused.
What is your understanding of why it helps in one place
Jouni,
My CRANberriesFeed reports a new bssm package at CRAN, congratulations for
sorting this out. [1,2] The OMP_NUM_THREADS setting is indeed all it takes,
and it _does_ seem to be read even from a running session: i.e. you can set
this inside an R session and the OpenMP code considers it in
On 27 October 2023 at 13:00, Johan Andresen wrote:
| I am sorry yet delighted to announce that the problem has been resolved.
| ragg didn't install successfully in the first place. When it was, there was
| no graphics API mismatch. Apologies for the spam; this entry may be
| deleted. Johan
Yes.
On 26 October 2023 at 11:14, Cole Johanson wrote:
| My package https://github.com/cole-johanson/smartsheetr requires an
| environment variable, the API access token, to run most of the functions.
| The steps for setting this are documented in the README, but my package is
| being auto-rejected
On 24 October 2023 at 08:15, Dirk Eddelbuettel wrote:
|
| On 24 October 2023 at 15:55, Ivan Krylov wrote:
| | В Tue, 24 Oct 2023 10:37:48 +
| | "Helske, Jouni" пишет:
| |
| | > Examples with CPU time > 2.5 times elapsed time
| | > user system elapsed ratio
|
On 24 October 2023 at 15:55, Ivan Krylov wrote:
| В Tue, 24 Oct 2023 10:37:48 +
| "Helske, Jouni" пишет:
|
| > Examples with CPU time > 2.5 times elapsed time
| > user system elapsed ratio
| > exchange 1.196 0.04 0.159 7.774
|
| I've downloaded the archived copy of the
On 19 October 2023 at 05:57, Helske, Jouni wrote:
| I am having difficulties in getting the latest version of the bssm
(https://github.com/helske/bssm) package to CRAN, as the pretest issues a NOTE
that the package uses too many cores in some of the examples ("Examples with
CPU time > 2.5
else,
specifically using R.rsp.
| >
| > Best,
| > John
| >
| > On 2023-10-17 4:02 a.m., Dirk Eddelbuettel wrote:
| >> Caution: External email.
| >> On 16 October 2023 at 10:42, Kevin R Coombes wrote:
| >> | Produce a PDF file yourself, then use the "as.is" feat
is not
accessible. Loading a precomputed set is similar. I may be doing that in the
much older never quite finished gcbd package and its vignette.
Hope this helps, maybe more once I am back home.
Cheers, Dirk
| Best,
| John
|
| On 2023-10-17 4:02 a.m., Dirk Eddelbuettel wrote:
| > Caution: Exter
On 16 October 2023 at 10:42, Kevin R Coombes wrote:
| Produce a PDF file yourself, then use the "as.is" feature of the R.rsp
| package.
For completeness, that approach also works directly with Sweave. Described in
a blog post by Mark van der Loo in 2019, and used in a number of packages
On 16 October 2023 at 11:41, Andreas Beckmann wrote:
| On 05/10/2023 17.05, Dirk Eddelbuettel wrote:
| >
| > Andreas,
| >
| > This looks like an error:
| >
| > > reassign 1037439 src:r-base
| > Bug #1037439 {Done: Dirk Eddelbuettel }
[r-cran-rstan] r-cran-
Andreas,
This looks like an error:
> reassign 1037439 src:r-base
Bug #1037439 {Done: Dirk Eddelbuettel } [r-cran-rstan]
r-cran-rstan/armhf FTBFS with r-cran-bh 1.74, works with boost 1.81
Bug reassigned from package 'r-cran-rstan' to 'src:r-base'.
No longer marked as fo
On 3 October 2023 at 18:52, Manuel Teodoro via ESS-help wrote:
| Is there a way to run R code upon starting each ESS session?
|
| Something like Rprofile but I'd like to make it more dependent to emacs.
|
| What I want is to have a few options settings in my R sessions by default.
| Since I
Hi Salvatore,
Looks like we emailed concurrently :) (or concurrently enough for my batched
mail setup).
On 26 September 2023 at 14:19, Salvatore Bonaccorso wrote:
| Hi Dirk,
|
| On Tue, Sep 26, 2023 at 06:54:31AM -0500, Dirk Eddelbuettel wrote:
| >
| > On 25 September 2023 at
Fix made, built, uploaded and committed to the package's salsa repo.
Dirk
--
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
On 25 September 2023 at 20:58, Salvatore Bonaccorso wrote:
| Source: gsl
| Version: 2.7.1+dfsg-5
| Severity: important
| Tags: security upstream
| Forwarded: https://savannah.gnu.org/bugs/?59624
| X-Debbugs-Cc: car...@debian.org, Debian Security Team
| Control: found -1
On 22 September 2023 at 07:04, Stephen J. Eglen via ESS-help wrote:
| 2. A non-answer to the original question, but I prefer writing Makefiles
| to build my documents, rather than using Emacs functionality. Emacs has
| a good interface to running make (e.g. through M-x compile). Use
| whatever
PS There is another neat use case where a shared_ptr is allocated. Now we
cannot wrap a shared_ptr in an XPtr but ... we can stick the shared_ptr into
a struct, and allocate that with new and then make_xptr. You are then back
to well-understood C++ semantics.
Dirk
--
dirk.eddelbuettel.com |
Hi Ralf,
On 23 September 2023 at 08:28, Ralf Stubner wrote:
| I have a question concerning the file-cycle of Rcpp::XPtr: Consider a
| XPtr with the default delete finalizer wrapping some pointer. If I use
| the copy constructor to create another XPtr, this is pointing at the
| same underlying
Package: wnpp
Owner: Dirk Eddelbuettel
Severity: wishlist
* Package name: r-cran-writexl
Version : 1.4.2
Upstream Author : Jeroen Ooms
* URL or Web page : https://cran.r-project.org/package=writexl
* License : BSD-2
Description : GNU R package to write xlsx file
Package: wnpp
Owner: Dirk Eddelbuettel
Severity: wishlist
* Package name: r-cran-writexl
Version : 1.4.2
Upstream Author : Jeroen Ooms
* URL or Web page : https://cran.r-project.org/package=writexl
* License : BSD-2
Description : GNU R package to write xlsx file
Package: wnpp
Owner: Dirk Eddelbuettel
Severity: wishlist
* Package name: r-cran-writexl
Version : 1.4.2
Upstream Author : Jeroen Ooms
* URL or Web page : https://cran.r-project.org/package=writexl
* License : BSD-2
Description : GNU R package to write xlsx file
Simon,
A new package of mine [1] appeared on CRAN on Sep 5. Respecting the one week
gap,
I made a small update on Sep 12.
Today is Sep 14. There are still no builds for
macOS r-release (arm64)
macOS r-oldrel (arm64)
macOS r-release (x86_64)
but we do have two oldrel releases. Weirder
On 31 August 2023 at 11:37, Chris Lamb wrote:
| Source: rpy2
| Version: 3.5.13-5
| Severity: normal
| Tags: patch
| User: reproducible-bui...@lists.alioth.debian.org
| Usertags: timestamps
| X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
|
| Hi,
|
| Whilst working on the Reproducible
On 31 August 2023 at 07:32, SHIMA Tatsuya wrote:
| I submitted prqlr 0.5.1 yesterday, which is almost identical to prqlr
| 0.5.0, and prqlr is now available again on CRAN.
| Thanks to the CRAN reviewers for their quick reaction.
And it is gone again (per CRANberries). Never a dull moment with
On 27 August 2023 at 18:44, YunQiang Su wrote:
| Maybe there is something wrong with ffi. (In fact the complex support of mips
| was added by me. ;)
Hah.
| I am looking for a way to use debug to debug the extensions.
| If you have any documents, can you point it to me.
I can help you with R,
On 27 August 2023 at 18:44, YunQiang Su wrote:
| Maybe there is something wrong with ffi. (In fact the complex support of mips
| was added by me. ;)
Hah.
| I am looking for a way to use debug to debug the extensions.
| If you have any documents, can you point it to me.
I can help you with R,
On 27 August 2023 at 18:44, YunQiang Su wrote:
| Maybe there is something wrong with ffi. (In fact the complex support of mips
| was added by me. ;)
Hah.
| I am looking for a way to use debug to debug the extensions.
| If you have any documents, can you point it to me.
I can help you with R,
On 27 August 2023 at 14:09, YunQiang Su wrote:
| Dirk Eddelbuettel 于2023年8月27日周日 00:15写道：
| >
| >
| > Hi all,
| >
| > As the test failures for complex valued variables appeared to be systemic on
| > the 'mips64el' platform, I buckled down, taught myself some Python ==:-) a
On 27 August 2023 at 14:09, YunQiang Su wrote:
| Dirk Eddelbuettel 于2023年8月27日周日 00:15写道：
| >
| >
| > Hi all,
| >
| > As the test failures for complex valued variables appeared to be systemic on
| > the 'mips64el' platform, I buckled down, taught myself some Python ==:-) a
On 27 August 2023 at 14:09, YunQiang Su wrote:
| Dirk Eddelbuettel 于2023年8月27日周日 00:15写道：
| >
| >
| > Hi all,
| >
| > As the test failures for complex valued variables appeared to be systemic on
| > the 'mips64el' platform, I buckled down, taught myself some Python ==:-) a
Hi all,
As the test failures for complex valued variables appeared to be systemic on
the 'mips64el' platform, I buckled down, taught myself some Python ==:-) and
conditioned the number of failing tests away via
@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder ==
Hi all,
As the test failures for complex valued variables appeared to be systemic on
the 'mips64el' platform, I buckled down, taught myself some Python ==:-) and
conditioned the number of failing tests away via
@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder ==
Hi all,
As the test failures for complex valued variables appeared to be systemic on
the 'mips64el' platform, I buckled down, taught myself some Python ==:-) and
conditioned the number of failing tests away via
@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder ==
On 25 August 2023 at 18:48, Jeff Newmiller wrote:
| You have a really bizarre way of twisting what others are saying, Dirk. I
have seen no-one here saying 'limit R to 2 threads' except for you, as a way to
paint opposing views to be absurd.
That's too cute.
Nobody needs to repeat it, and
On 26 August 2023 at 12:05, Simon Urbanek wrote:
| In reality it's more people running R on their laptops vs the rest of the
world.
My point was that we also have 'single user on really Yuge workstation'.
Plus we all know that those users are often not sysadmins, and do not have
our levels
On 25 August 2023 at 18:45, Duncan Murdoch wrote:
| The real problem is that there are two stubborn groups opposing each
| other: the data.table developers and the CRAN maintainers. The former
| think users should by default dedicate their whole machine to
| data.table. The latter think
On 25 August 2023 at 15:37, Uwe Ligges wrote:
|
|
| On 23.08.2023 16:00, Scott Ritchie wrote:
| > Hi Uwe,
| >
| > I agree and have also been burnt myself by programs occupying the
| > maximum number of cores available.
| >
| > My understanding is that in the absence of explicit
On 24 August 2023 at 07:42, Fred Viole wrote:
| Hi, I am receiving a NOTE upon submission regarding the re-building of
| vignettes for CPU time for the Debian check.
|
| I am unable to find any documented instances or solutions to this issue.
| The vignettes currently build in 1m 54.3s locally
Paul,
Thanks for the hint. I was aware and had been meaning to bring this up with
Laurent (upstream, now CCed).
Laurent: I should have access to a 'porterbox' running mips64el if you have
an idea about what may be going on here / have a branch to test.
Paul: While I have you here, and as all
Paul,
Thanks for the hint. I was aware and had been meaning to bring this up with
Laurent (upstream, now CCed).
Laurent: I should have access to a 'porterbox' running mips64el if you have
an idea about what may be going on here / have a branch to test.
Paul: While I have you here, and as all
My thanks to Ivan for catching that it was of course a legit Ubuntu mirror,
which I had missed.
Can we (ever so briefly, no need for long posts) get back to the issue at
hand: was there a package you wanted to install from r2u, but could not
because of another repo or build infelicity. If so,
Chris,
This got a little long so I'll chop a few things down.
On 22 August 2023 at 19:38, Chris Evans wrote:
| On 16/08/2023 00:06, Dirk Eddelbuettel wrote:
| >
| > That can happen, and pinning can help. I would suggest to look at 'apt-cache
| > polict nameofthepackagehere'. (
On 23 August 2023 at 16:49, Duncan Murdoch wrote:
| On 23/08/2023 2:54 p.m., Dirk Eddelbuettel wrote:
| >
| > When I invoke valgrind via
| > R -d valgrind -e '...'
| > the options in the file ~/.valgrindrc are being picked up. Good.
| >
| > When I invok valgrind via
|
When I invoke valgrind via
R -d valgrind -e '...'
the options in the file ~/.valgrindrc are being picked up. Good.
When I invok valgrind via
R CMD check --use-valgrind ...
the options in the file ~/.valgrindrc are NOT being picked up. Bad.
And valgrind complains. How can I add the
' @param ncores A numeric or character variable with the desired
##' count of threads to use
##' @param verbose A logical value with a default of \sQuote{FALSE} to
##' operate more verbosely
##' @return The return value of the \pkg{data.table} function
##' \code{setDTthreads} which is called as a side
On 21 August 2023 at 15:16, Ivan Krylov wrote:
| On Mon, 21 Aug 2023 12:02:55 +0100
| Scott Ritchie wrote:
|
| > remotes::install_github("sritchie73/ukbnmr")
| > library(ukbnmr)
| > system.time({ remove_technical_variation(test_data) })
|
| data.tables, you say? Can you show us the NOTE
On 20 August 2023 at 09:22, Duncan Murdoch wrote:
| That seems like a bug that should be reported to the Roxygen authors.
Seb did so in June:
https://github.com/r-lib/roxygen2/issues/1491
There has not been a response (but given the CRAN email to many maintainers
it has now been referenced
On 18 August 2023 at 13:58, Andreas Tille wrote:
| Control: tags -1 upstream
| Control: forwarded -1 Roger Bivand
|
| Hi Roger,
|
| the CI tests in Debian uncovered some conflict between recent rgdal and
| version 2.0 of sp. As you either can see in the bug report that was
| filed[1] or in a
On 18 August 2023 at 13:58, Andreas Tille wrote:
| Control: tags -1 upstream
| Control: forwarded -1 Roger Bivand
|
| Hi Roger,
|
| the CI tests in Debian uncovered some conflict between recent rgdal and
| version 2.0 of sp. As you either can see in the bug report that was
| filed[1] or in a
On 17 August 2023 at 07:24, Graham Inggs wrote:
| On Thu, 17 Aug 2023 at 05:52, Andreas Tille wrote:
| > I tried to skip two tests in r-cran-checkmate with this patch[1]
| > which is based on
| >
| > arch <- R.version$arch
| > identical(arch, "i386") || identical(arch, "i686") ||
On 17 August 2023 at 07:24, Graham Inggs wrote:
| On Thu, 17 Aug 2023 at 05:52, Andreas Tille wrote:
| > I tried to skip two tests in r-cran-checkmate with this patch[1]
| > which is based on
| >
| > arch <- R.version$arch
| > identical(arch, "i386") || identical(arch, "i686") ||
Chris,
I edited the README.md for r2u (also the main page at
https://eddelbuettel.github.io/r2u) in a few places, that should hopefully
address a few of the snafus you found.
As for your question 'is r2u running R version x.y.z' there are few way to
find out
- if you have docker: docker run
Hi Chris,
Thanks for posting here, and sorry I missed it for two days due to sorting
mailing list traffic into folders and clearly not glancing at all of them.
On 13 August 2023 at 09:12, Chris Evans wrote:
| I am putting this here as it may be of general and not just my own
| interest. I am
On 14 August 2023 at 11:51, Mark Padgham wrote:
| An update of a package of mine got immediately kicked off CRAN because
| an externally-bundled file which had not been changed for years, and
| which included "pragma clang system_header" to suppress warnings. The
| concern is fair enough.
e distribution unstable
| > dpkg-buildpackage: info: source changed by Dirk Eddelbuettel
| > dpkg-source --before-build .
| > fakeroot debian/rules clean
| > dh_testdir
| > dh_testroot
| > dh_autoreconf_clean
| > rm -f build-stamp configure-stamp install-stamp
| > [ ! -f Mak
The 'bug fix' applied to the _previous_ version of CRAN package clock, namely
a somewhat 'wild' sed patching of a single ie
# Ignore single test for i386 architecture. This is a workaround for bug
#1024828 of r-cran-igraph
if [ "$hostarch" = "i386" -o "$hostarch" = "armel" -o "$hostarch" =
The 'bug fix' applied to the _previous_ version of CRAN package clock, namely
a somewhat 'wild' sed patching of a single ie
# Ignore single test for i386 architecture. This is a workaround for bug
#1024828 of r-cran-igraph
if [ "$hostarch" = "i386" -o "$hostarch" = "armel" -o "$hostarch" =
On 12 August 2023 at 18:12, Uwe Ligges wrote:
| On 12.08.2023 15:10, Jamie Lentin wrote:
| > The system call in question is done by the TMB package[2], and not ours
| > to tinker with:
| >
| > cmd <- paste("R --vanilla < ",file," -d gdb --debugger-args=\"-x",
| >
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 "
On 9 August 2023 at 21:59, Thomas Petzoldt wrote:
| On 09.08.2023 at 19:18 Dirk Eddelbuettel wrote:
| > There is a fifth option I just realized.
| >
| > I use a variant of that to keep for example an old version of roxygen2 I
| > prefer available. Recall that R packages a
ronemnt".
On 9 August 2023 at 18:58, Thomas Petzoldt wrote:
| Am 09.08.2023 um 18:17 schrieb Dirk Eddelbuettel:
| > Yes. If and when that happens, it is a bug!
|
| Not necessarily. Breaking code can also be due to an incompatible
| feature update. We know that R has both, conservative a
Hi Thomas,
Thanks a lot for bringing this over from r-package-devel!
As for your question, "there is a lot of meat on these bones" and I really
think we should discuss this here.
Quick comments inline, more recap at the bottom.
On 9 August 2023 at 17:29, Thomas Petzoldt wrote:
| Hi,
|
| I
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,
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
Hi Hadley,
On 8 August 2023 at 08:34, Hadley Wickham wrote:
| Do you think it's worth also/instead considering a fix to S4 to avoid
| this caching issue in future R versions?
That is somewhat orthogonal to my point of "'some uses' of the 20 year old S4
system (which as we know is fairly widely
201 - 300 of 15988 matches
Mail list logo
