Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory

reassign 1069842 r-base thanks On 25 April 2024 at 18:27, Santiago Vila wrote: | Package: src:rjava | Version: 1.0-11-1 | Severity: serious | Tags: ftbfs | | Dear maintainer: | | During a rebuild of all packages in unstable, your package failed to build: Thanks for this. It is caused by the

Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory

reassign 1069842 r-base thanks On 25 April 2024 at 18:27, Santiago Vila wrote: | Package: src:rjava | Version: 1.0-11-1 | Severity: serious | Tags: ftbfs | | Dear maintainer: | | During a rebuild of all packages in unstable, your package failed to build: Thanks for this. It is caused by the

Re: [Rd] Question regarding .make_numeric_version with non-character input

Hi Kurt, On 25 April 2024 at 08:07, Kurt Hornik wrote: | > Hervé Pagès writes: | | > Hi Kurt, | > Is it intended that numeric_version() returns an error by default on | > non-character input in R 4.4.0? | | Dear Herve, yes, that's the intention. | | > It seems that I can turn this into

Re: R 4.4.0 coming April 24

On 21 April 2024 at 15:25, Sebastiaan Couwenberg wrote: | On 4/21/24 3:04 PM, Dirk Eddelbuettel wrote: | > R upstream no longer releases or tests for 32 bits (and has not since the R | > 4.3.0 release a year ago) so 'expect trouble there'. I think you all in the | > release team

Re: R 4.4.0 coming April 24

Hi Graham, Hi Release Team, On 21 April 2024 at 13:37, Graham Inggs wrote: | On Thu, 18 Apr 2024 at 13:38, Dirk Eddelbuettel wrote: | > Right now it now only shows 'all reports (re-)running'. | | That was because of the new upload, but I see the results there now. | | The packa

Re: R 4.4.0 coming April 24

Hi Paul, On 18 April 2024 at 11:50, Paul Gevers wrote: | Hi Dirk, | | On 18-04-2024 4:41 a.m., Dirk Eddelbuettel wrote: | > I uploaded a first | > beta release r-base_4.3.3.20240409-1 to 'experimental' a week ago, I just | > followed up with a rc release r-base_4.3.3.20240416-1. |

R 4.4.0 coming April 24

R 4.4.0 will be released on April 24 (following the long established pattern of annual 'a.b.0' releases). As is common, nightlies (as alpha, betas, rc) have been made available for four weeks leading up to it. I uploaded a first beta release r-base_4.3.3.20240409-1 to 'experimental' a week ago,

R 4.4.0 coming April 24

R 4.4.0 will be released on April 24 (following the long established pattern of annual 'a.b.0' releases). As is common, nightlies (as alpha, betas, rc) have been made available for four weeks leading up to it. I uploaded a first beta release r-base_4.3.3.20240409-1 to 'experimental' a week ago,

Re: [Rd] read.csv

As an aside, the odd format does not seem to bother data.table::fread() which also happens to be my personally preferred workhorse for these tasks: > fname <- "/tmp/r/filename.csv" > read.csv(fname) Gene SNP prot log10p 1 YWHAE 13:62129097_C_T 1433 7.35 2 YWHAE 4:72617557_T_TA

Re: [Rd] read.csv

On 16 April 2024 at 10:46, jing hua zhao wrote: | Dear R-developers, | | I came to a somewhat unexpected behaviour of read.csv() which is trivial but worthwhile to note -- my data involves a protein named "1433E" but to save space I drop the quote so it becomes, | | Gene,SNP,prot,log10p |

Bug#970021: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

On 9 April 2024 at 18:45, Jose Manuel Abuin Mosquera wrote: | If possible, I would like to contribute. At work we use the Go and | Python implementations, also, in the short term, we will start using the | Rust one. Similar for us, and we have seen plenty of build headaches across pypi or

Bug#970021: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

On 9 April 2024 at 18:45, Jose Manuel Abuin Mosquera wrote: | If possible, I would like to contribute. At work we use the Go and | Python implementations, also, in the short term, we will start using the | Rust one. Similar for us, and we have seen plenty of build headaches across pypi or

Re: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

On 9 April 2024 at 18:45, Jose Manuel Abuin Mosquera wrote: | If possible, I would like to contribute. At work we use the Go and | Python implementations, also, in the short term, we will start using the | Rust one. Similar for us, and we have seen plenty of build headaches across pypi or

Bug#1068117: dieharder: dab_monobit2 crashes with ntuple > 17

On 8 April 2024 at 18:21, Lucas Thode wrote: | Apologies for the confusion, I didn't realize the patch in question was a new | addition.  Just confirmed that it errors out instead of segfaulting or hanging. Thanks for confirming! Dirk | On Sat, Apr 6, 2024 at 5:32 PM Dirk Eddelbuettel

Bug#1068117: dieharder: dab_monobit2 crashes with ntuple > 17

Hi Lucas, As Milan suggested, please sure you are current. If in doubt, park you current checkout and start from git checkout https://github.com/eddelbuettel/dieharder.git where you should see today's commit from merging PR 24. edd@rob:~/git/dieharder(master)$ git ls | head *

Bug#1068117: dieharder: dab_monobit2 crashes with ntuple > 17

Hi Lucas, On 30 March 2024 at 22:47, Lucas Thode wrote: | Package: dieharder | Version: 3.31.1.4-1.1 | Severity: normal | X-Debbugs-Cc: thode...@gmail.com | | Dear Maintainer, | | `dieharder -d 209 -n $nvalue` crashes for $nvalue>17: | | $ dieharder -d 209 |

Re: [Rd] RSS Feed of NEWS needs a hand

On 2 April 2024 at 09:41, Duncan Murdoch wrote: | On 02/04/2024 8:50 a.m., Dirk Eddelbuettel wrote: | > On 2 April 2024 at 07:37, Dirk Eddelbuettel wrote: | > blosxom, simple as it is, takes (IIRC) filesystem ctime as the posting | > timestamp so would be best if you had a backup wit

Re: [Rd] RSS Feed of NEWS needs a hand

On 2 April 2024 at 07:37, Dirk Eddelbuettel wrote: | | On 2 April 2024 at 08:21, Duncan Murdoch wrote: | | I have just added R-4-4-branch to the feeds. I think I've also fixed | | the \I issue, so today's news includes a long list of old changes. | | These feeds can fussy: looks like you

Re: [Rd] RSS Feed of NEWS needs a hand

On 2 April 2024 at 08:21, Duncan Murdoch wrote: | I have just added R-4-4-branch to the feeds. I think I've also fixed | the \I issue, so today's news includes a long list of old changes. These feeds can fussy: looks like you triggered many updates. Feedly currently greets me with 569 new

Re: [R-pkg-devel] Order of repo access from options("repos")

On 1 April 2024 at 17:44, Uwe Ligges wrote: | Untested: | | install.packages() calls available.packages() to find out which packages | are available - and passes a "filters" argument if supplied. | That can be a user defined filter. It should be possible to write a user | defined filter which

Re: [R-pkg-devel] Order of repo access from options("repos")

On 31 March 2024 at 11:43, Martin Morgan wrote: | So all repositories are consulted and then the result filtered to contain just | the most recent version of each. Does it matter then what order the | repositories are visited? Right. I fall for that too often, as I did here. The order matters

Bug#970021: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

Julian, Arrow is a complicated and large package. We use it at work (where there is a fair amount of Python, also to Conda etc) and do have issues with more complex builds especially because it is 'data infrastructure' and can come in from different parts. I would recommend against packaging at

Bug#970021: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

Julian, Arrow is a complicated and large package. We use it at work (where there is a fair amount of Python, also to Conda etc) and do have issues with more complex builds especially because it is 'data infrastructure' and can come in from different parts. I would recommend against packaging at

Re: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

Julian, Arrow is a complicated and large package. We use it at work (where there is a fair amount of Python, also to Conda etc) and do have issues with more complex builds especially because it is 'data infrastructure' and can come in from different parts. I would recommend against packaging at

Re: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

Julian, Arrow is a complicated and large package. We use it at work (where there is a fair amount of Python, also to Conda etc) and do have issues with more complex builds especially because it is 'data infrastructure' and can come in from different parts. I would recommend against packaging at

Re: Seeking a small group to package Apache Arrow (was: Bug#970021: RFP: apache-arrow -- cross-language development platform for in-memory analytics)

Julian, Arrow is a complicated and large package. We use it at work (where there is a fair amount of Python, also to Conda etc) and do have issues with more complex builds especially because it is 'data infrastructure' and can come in from different parts. I would recommend against packaging at

Re: [R-pkg-devel] Order of repo access from options("repos")

Greg, There are AFAICT two issues here: how R unrolls the named vector that is the 'repos' element in the list 'options', and how your computer resolves DNS for localhost vs 172.17.0.1. I would try something like options(repos = c(CRAN = "http://localhost:3001/proxy;,

Re: [Rd] Question regarding .make_numeric_version with non-character input

On 29 March 2024 at 17:56, Andrea Gilardi via R-devel wrote: | Dear all, | | I have a question regarding the R-devel version of .make_numeric_version() function. As far as I can understand, the current code

Re: [R-sig-Debian] Problem Installing R 4.3.3 on Vanilla based Jammy Ubuntu

Marco, It usually helps to be aware of one's hardware platform ;-) There is an option for Docker command to tell it to switch to x86_64, my colleagues who are on M1 and alike use that to access the generally richer eco-system of binaries for the Intel world. If on the other hand you prefer to

Re: [R-pkg-devel] using portable simd instructions

: https://github.com/google/highway docs: https://google.github.io/highway/en/master/ | | Op di 26 mrt 2024 om 15:41 schreef Dirk Eddelbuettel : | > | > | > On 26 March 2024 at 10:53, jesse koops wrote: | > | How can I make this portable and CRAN-acceptable? | > | > But wri

Re: [Rd] paths capability FALSE on devel?

On 27 March 2024 at 11:03, Prof Brian Ripley via R-devel wrote: | On 27/03/2024 10:28, Alexandre Courtiol wrote: | > Hi all, | > | > I don't know if it is a local issue on my hands or not, but after | > installing R-devel the output of grDevices::dev.capabilities()$paths is | > FALSE, while it

Re: [R-pkg-devel] Check results on r-devel-windows claiming error but tests seem to pass?

On 26 March 2024 at 09:37, Dirk Eddelbuettel wrote: | | Avi, | | That was a hickup and is now taken care of. When discussing this (off-line) | with Jeroen we (rightly) suggested that keeping an eye on Typo, as usual, "he (rightly) suggested". My bad. D. | |https://con

Re: [R-pkg-devel] using portable simd instructions

On 26 March 2024 at 10:53, jesse koops wrote: | How can I make this portable and CRAN-acceptable? But writing (or borrowing ?) some hardware detection via either configure / autoconf or cmake. This is no different than other tasks decided at install-time. Start with 'Writing R Extensions', as

Re: [R-pkg-devel] Check results on r-devel-windows claiming error but tests seem to pass?

Avi, That was a hickup and is now taken care of. When discussing this (off-line) with Jeroen we (rightly) suggested that keeping an eye on https://contributor.r-project.org/svn-dashboard/ is one possibility to keep track while we have no status alert system from CRAN. I too was quite

Re: [R-pkg-devel] How to store large data to be used in an R package?

On 25 March 2024 at 11:12, Jairo Hidalgo Migueles wrote: | I'm reaching out to seek some guidance regarding the storage of relatively | large data, ranging from 10-40 MB, intended for use within an R package. | Specifically, this data consists of regression and random forest models | crucial for

Re: CRAN Package Matrix update and a possible transition or not

On 23 March 2024 at 07:25, Dirk Eddelbuettel wrote: | | On 22 March 2024 at 11:12, Dirk Eddelbuettel wrote: | | | | On 27 February 2024 at 19:01, Dirk Eddelbuettel wrote: | | | A couple of days ago, the (effective) Maintainer and rather active developer | | | of the Matrix package Mikael

Re: CRAN Package Matrix update and a possible transition or not

On 23 March 2024 at 07:25, Dirk Eddelbuettel wrote: | | On 22 March 2024 at 11:12, Dirk Eddelbuettel wrote: | | | | On 27 February 2024 at 19:01, Dirk Eddelbuettel wrote: | | | A couple of days ago, the (effective) Maintainer and rather active developer | | | of the Matrix package Mikael

Re: CRAN Package Matrix update and a possible transition or not

On 22 March 2024 at 11:12, Dirk Eddelbuettel wrote: | | On 27 February 2024 at 19:01, Dirk Eddelbuettel wrote: | | A couple of days ago, the (effective) Maintainer and rather active developer | | of the Matrix package Mikael Jagan (CC'ed) posted on the r-package-devel list | | (the primary

Re: CRAN Package Matrix update and a possible transition or not

On 22 March 2024 at 11:12, Dirk Eddelbuettel wrote: | | On 27 February 2024 at 19:01, Dirk Eddelbuettel wrote: | | A couple of days ago, the (effective) Maintainer and rather active developer | | of the Matrix package Mikael Jagan (CC'ed) posted on the r-package-devel list | | (the primary

Re: CRAN Package Matrix update and a possible transition or not

On 27 February 2024 at 19:01, Dirk Eddelbuettel wrote: | A couple of days ago, the (effective) Maintainer and rather active developer | of the Matrix package Mikael Jagan (CC'ed) posted on the r-package-devel list | (the primary list for R package development) that the upcoming change

Re: CRAN Package Matrix update and a possible transition or not

On 27 February 2024 at 19:01, Dirk Eddelbuettel wrote: | A couple of days ago, the (effective) Maintainer and rather active developer | of the Matrix package Mikael Jagan (CC'ed) posted on the r-package-devel list | (the primary list for R package development) that the upcoming change

Re: [R-pkg-devel] Request for assistance: error in installing on Debian (undefined symbol: omp_get_num_procs) and note in checking the HTML versions (no command 'tidy' found, package 'V8' unavailable

Salut Annaig, On 21 March 2024 at 09:26, Annaig De-Walsche wrote: | Dear R-package-devel Community, | | I hope this email finds you well. I am reaching out to seek assistance regarding package development in R. | | Specifically, I am currently developing an R package for querying composite

Bug#1067218: gretl: please make the build reproducible

Hi Chris, On 20 March 2024 at 11:05, Chris Lamb wrote: | Source: gretl | Version: 2023c-2.1 | Severity: wishlist | 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

Re: [R-pkg-devel] new maintainer for CRAN package XML

Dear Uwe, Did CRAN ever reach a decision here with a suitable volunteer (or group of volunteers) ? The state of XML came up again recently on mastodon, and it might be helpful to share an update if there is one. Thanks, as always, for all you and the rest of the team do for CRAN. Cheers,

[Rd] RSS Feed of NEWS needs a hand

Years ago Duncan set up a nightly job to feed RSS based off changes to NEWS, borrowing some setup parts from CRANberries as for example the RSS 'compiler'. That job is currently showing the new \I{...} curly protection in an unfavourable light. Copying from the RSS reader I had pointed at this

Bug#1066403: R packages failing to build with missing -ltirpc are actually an issue in r-base

-Depends to fix build issue from side effects of t64 transition (Closes: #1065216) -- Dirk Eddelbuettel Mon, 04 Mar 2024 08:54:45 -0600 I will take care of it in -3. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1066403: R packages failing to build with missing -ltirpc are actually an issue in r-base

-Depends to fix build issue from side effects of t64 transition (Closes: #1065216) -- Dirk Eddelbuettel Mon, 04 Mar 2024 08:54:45 -0600 I will take care of it in -3. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Re: [R-pkg-devel] Suggesting an archived package in the DESCRIPTION file

On 5 March 2024 at 15:12, Duncan Murdoch wrote: | On 05/03/2024 2:26 p.m., Dirk Eddelbuettel wrote: | > The default behaviour is to build after every commit to the main branch. But | > there are options. On the repo I mentioned we use | > | > "branch": "*rele

Re: [R-pkg-devel] Suggesting an archived package in the DESCRIPTION file

On 5 March 2024 at 13:28, Duncan Murdoch wrote: | What I'm seeing is that the tags are ignored, and it is distributing the | HEAD of the main branch. I don't think most users should be using that | version: in my packages it won't have had full reverse dependency | checks, I only do that

Re: [R-pkg-devel] Suggesting an archived package in the DESCRIPTION file

On 5 March 2024 at 11:56, Duncan Murdoch wrote: | I have mixed feelings about r-universe. On the one hand, it is really | nicely put together, and it offers the service described above. On the | other, it's probably a bad idea to follow its advice and use | install.packages() with `repos`

Re: [R-pkg-devel] Suggesting an archived package in the DESCRIPTION file

On 5 March 2024 at 06:25, Duncan Murdoch wrote: | You could make a compatible version of `survivalmodels` available on a | non-CRAN website, and refer to that website in the | Additional_repositories field of DESCRIPTION. Every r-universe sub-site fits that requirement. For this package

Bug#1065216: r-base: recent libc6-dev change causes the xdr feature to be dropped

On 1 March 2024 at 23:36, Aurelien Jarno wrote: | Source: r-base | Version: 4.3.3-1 | Severity: serious | Tags: ftbfs | Justification: fails to build from source (but built successfully in the past) | User: debian-gl...@lists.debian.org | Usertags: libtirpc-dev | | Dear maintainer, | |

Bug#1065216: r-base: recent libc6-dev change causes the xdr feature to be dropped

On 1 March 2024 at 23:36, Aurelien Jarno wrote: | Source: r-base | Version: 4.3.3-1 | Severity: serious | Tags: ftbfs | Justification: fails to build from source (but built successfully in the past) | User: debian-gl...@lists.debian.org | Usertags: libtirpc-dev | | Dear maintainer, | |

Re: [Rcpp-devel] segfault on exit CRAN+Intel only

Hi Murray, On 4 March 2024 at 07:03, Murray Efford wrote: | Dirk | Thanks for a very helpful reply. I'll simplify my return values. | | I mentioned Intel with rhub2 in my earlier post here, but I'm sorry | that was somewhat buried. Debugging is somewhere between painful and | impossible when

Re: [Rcpp-devel] segfault on exit CRAN+Intel only

And "beauty" (ahem) of discussion scattered over two mailing lists: I now see you have a testbed via rhub2 (good) even though it does not reproduce (hm...). So you could still try the suggested simplication. Cheers, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Re: [Rcpp-devel] segfault on exit CRAN+Intel only

On 3 March 2024 at 20:47, Murray Efford wrote: | A couple of days ago I posted on R-package-devel about a mysterious | segfault from R CMD checks of my package secrdesign (see | https://CRAN.R-project.org/package=secrdesign, and | https://github.com/MurrayEfford/secrdesign) The issue rises only

Re: [Rcpp-devel] RcppArmadillo with -fopenmp: Not using all available cores

the following: | | > extSoftVersion()["BLAS"] Ah yes -- I keep forgetting about that one. Good reminder! | Thanks for your help! Always a pleasure. Glad you are all set. Dirk | On Sat, Feb 24, 2024 at 9:17 AM Dirk Eddelbuettel wrote: | | | On 24 February 2024 at 11:44, Ro

Re: [Rcpp-devel] Segfault in wrapping code in Rcpp

Hi Nikhil, Don't post images. I read in a text-based reader. The mailing list software also scrubs html (I think). I would simplify. Start with the simplest Rcpp Modules setup. Then add. Check checking. Eventually on your way towards what you are doing now you may spot the error. Hope this

Bug#1063320: gretl: NMU diff for 64-bit time_t transition

On 29 February 2024 at 00:20, Steve Langasek wrote: | Dear maintainer, | | Please find attached a final version of this patch for the time_t | transition. This patch is being uploaded to unstable. | | Note that this adds a versioned build-dependency on dpkg-dev, to guard | against accidental

Bug#1063320: gretl: NMU diff for 64-bit time_t transition

On 29 February 2024 at 00:20, Steve Langasek wrote: | Dear maintainer, | | Please find attached a final version of this patch for the time_t | transition. This patch is being uploaded to unstable. | | Note that this adds a versioned build-dependency on dpkg-dev, to guard | against accidental

Bug#1062364: dieharder: NMU diff for 64-bit time_t transition

On 28 February 2024 at 21:28, mwhud...@fastmail.fm wrote: | Dear maintainer, | | Please find attached a final version of this patch for the time_t | transition. This patch is being uploaded to unstable. | | Note that this adds a versioned build-dependency on dpkg-dev, to guard | against

Bug#1062364: dieharder: NMU diff for 64-bit time_t transition

On 28 February 2024 at 21:28, mwhud...@fastmail.fm wrote: | Dear maintainer, | | Please find attached a final version of this patch for the time_t | transition. This patch is being uploaded to unstable. | | Note that this adds a versioned build-dependency on dpkg-dev, to guard | against

Bug#1064388: ess: New version 24.1.1

On 28 February 2024 at 10:17, Sébastien Villemot wrote: | Salut Dirk, | | Le mercredi 21 février 2024 à 06:54 -0600, Dirk Eddelbuettel a écrit : | > Source: ess | > Version: 24.01.0-1 | > Severity: minor | > | > Salut Seb -- and thanks for packaging the recent 24.1.0 which in

Re: [R-pkg-devel] Unable to access log operator in C

On 28 February 2024 at 19:05, Avraham Adler wrote: | I am hoping the solution to this question is simple, but I have not | been able to find one. I am building a routine in C to be called from | R. I am including Rmath.h. However, when I have a call to "log", I get | the error "called object

CRAN Package Matrix update and a possible transition or not

A couple of days ago, the (effective) Maintainer and rather active developer of the Matrix package Mikael Jagan (CC'ed) posted on the r-package-devel list (the primary list for R package development) that the upcoming change of Matrix 1.7-0, planned for March 11, will be _very midly disruptive_

CRAN Package Matrix update and a possible transition or not

A couple of days ago, the (effective) Maintainer and rather active developer of the Matrix package Mikael Jagan (CC'ed) posted on the r-package-devel list (the primary list for R package development) that the upcoming change of Matrix 1.7-0, planned for March 11, will be _very midly disruptive_

Re: [R-pkg-devel] Package required but not available: ‘arrow’

On 26 February 2024 at 09:19, Simon Urbanek wrote: | [requiring increased is] best way [..] and certainly the only good practice. No, not really. Another viewpoint, which is implemented in another project I contribute to, is where a version + build_revision tuple exists if, and only if, the

Re: [Rcpp-devel] RcppArmadillo with -fopenmp: Not using all available cores

rn arma::eig_sym(M); | })" | | size <- 1 | m <- matrix(rnorm(size^2), size, size) | m <- m * t(m) | | # This line compiles the above code with the -fopenmp flag. | sourceCpp(code = src, verbose = TRUE, rebuild = TRUE) | result <- getEigenValues(m) | print(result[1:10]) | | On Fri, Feb 23,

Re: [Rcpp-devel] RcppArmadillo with -fopenmp: Not using all available cores

On 23 February 2024 at 09:35, Robin Liu wrote: | Hi all, | | Here is an R script that uses Armadillo to decompose a large matrix and print | the first 10 eigenvalues. | | library(RcppArmadillo) | library(Rcpp) | | src <- | r"(#include | | // [[Rcpp::depends(RcppArmadillo)]] | | //

Re: [R-pkg-devel] Package required but not available: ‘arrow’

On 23 February 2024 at 15:53, Leo Mada wrote: | Dear Dirk & R-Members, | | It seems that the version number is not incremented: | # Archived | arrow_14.0.2.1.tar.gz   2024-02-08 11:57  3.9M | # Pending | arrow_14.0.2.1.tar.gz   2024-02-08 18:24  3.9M | | Maybe this is the reason why it got

Re: [R-pkg-devel] Package required but not available:‘arrow’

On 22 February 2024 at 04:01, Duncan Murdoch wrote: | For you to deal with this, you should make arrow into a suggested | package, For what it is worth, that is exactly what package tiledb does. Yet the Suggests: still lead to a NOTE requiring a human to override which did not happen until I

Bug#1064388: ess: New version 24.1.1

Source: ess Version: 24.01.0-1 Severity: minor Salut Seb -- and thanks for packaging the recent 24.1.0 which installs fine. There is by now a follow-up 24.1.1 which would be nice to have too. Amities, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Re: [Rcpp-devel] Wrapping a c++ class with singleton using RCPP Module

On 21 February 2024 at 09:21, Iñaki Ucar wrote: | Could you please provide more details about what you tried so far and what are | the issues you found? A link to a public repo with a test case would be even | better. Seconded! I think I also did something like that 'way early' and 'way

Re: [Rd] Compiling libR as a standalone C library for java+jni (-fPIC)

Salut Pierre, On 20 February 2024 at 10:33, Pierre Lindenbaum wrote: | (cross-posted on SO: https://stackoverflow.com/questions/78022766) | | Hi all, | | I'm trying to compile R as a static library with the -fPIC flag so I can use it within java+JNI (is it only possible ?), but I cannot find

Re: [Rd] Tcl socket server (tcltk) does not work any more on R 4.3.2

On 20 February 2024 at 12:27, webmail.gandi.net wrote: | Dear list, | | It seems that something changed between R 4.2.3 and R 4.3 (tested with 4.3.2) that broke the Tcl socket server. Here is a reproducible example: | | - R process #1 (Tcl socket server): | | library(tcltk) | cmd <- r"( |

Re: [ESS] FW: [GNU ELPA] ESS version 24.1.1

On 18 February 2024 at 20:54, Brett Presnell via ESS-help wrote: | | Forgot to mention that you may need to uninstall and reinstall the ess | package after putting the :pin in place, but I'm not sure about that. | Restarting emacs is maybe needed too, but not sure about that either. The pin,

Re: [ESS] FW: [GNU ELPA] ESS version 24.1.1

Rodney et al, Thanks for the update(s)! Alas, I also seem to see ess20240131.1041 installed Emacs Speaks Statistics which seems to win over ess24.1.1 obsolete Emacs Speaks Statistics What is the

Re: [R-sig-Debian] Error building and installing with GCC ASAN in a Docker container

Hi Brent, On 15 February 2024 at 10:14, Brent G Ewing wrote: | Hi, | | I want to build a Docker container with R and various R packages built and | installed with the gcc address sanitizer enabled. I am working on a Debian | Bookworm system running on an x86_64 architecture. | | I start with

Re: [R-pkg-devel] CRAN uses an old version of clang

On 9 February 2024 at 08:59, Marcin Jurek wrote: | I recently submitted an update to my package. It previous version relied on | Boost for Bessel and gamma functions but a colleague pointed out to me that | they are included in the standard library beginning with the C++17 | standard. There is

Re: [R-pkg-devel] failing CRAN checks due to problems with dependencies

On 8 February 2024 at 13:28, Marcin Jurek wrote: | Ok, this makes sense! I saw that Rcpp was failing the checks too but I | wasn't sure if I should resubmit or wait. Thanks! For completeness, it was not caused by Rcpp but rather by a mix on new clang and gcc versions which somehow got into each

Bug#1063320: gretl: NMU diff for 64-bit time_t transition

On 6 February 2024 at 06:43, Steve Langasek wrote: | Source: gretl | Version: 2023c-2 | Severity: serious | Tags: patch pending sid trixie | Justification: library ABI skew on upgrade | User: debian-...@lists.debian.org | Usertags: time-t | | NOTICE: these changes must not be uploaded to

Bug#1063320: gretl: NMU diff for 64-bit time_t transition

On 6 February 2024 at 06:43, Steve Langasek wrote: | Source: gretl | Version: 2023c-2 | Severity: serious | Tags: patch pending sid trixie | Justification: library ABI skew on upgrade | User: debian-...@lists.debian.org | Usertags: time-t | | NOTICE: these changes must not be uploaded to

Bug#1062364: dieharder: NMU diff for 64-bit time_t transition

On 1 February 2024 at 07:21, mwhud...@debian.org wrote: | Source: dieharder | Version: 3.31.1.4-1 | Severity: serious | Tags: patch pending | Justification: library ABI skew on upgrade | User: debian-...@lists.debian.org | Usertags: time-t | | Dear maintainer, | | As part of the 64-bit time_t

Re: [R-pkg-devel] r-oldrel-linux- not in CRAN checks?

On 7 February 2024 at 09:15, Vincent van Hees wrote: | Thanks Ivan, In that case I will conclude that it is time to upgrade my | Ubuntu 18 machine. I just wasn't sure whether there is still a need for | keeping my own package Ubuntu 18 compatible, but if dependencies like Rfast | do not do it

Re: [Rd] Advice debugging M1Mac check errors

On 4 February 2024 at 20:41, Holger Hoefling wrote: | I wanted to ask if people have good advice on how to debug M1Mac package | check errors when you don´t have a Mac? Is a cloud machine the best option | or is there something else? a) Use the 'mac builder' CRAN offers:

Bug#1063047: Unable to run R CMD Rserve

Appears to work based on a quick check in Docker: root@8d41067e72ce:/work# dpkg -i r-cran-rserve_1.8-13-2_amd64.deb Selecting previously unselected package r-cran-rserve. (Reading database ... 17542 files and directories currently installed.) Preparing to unpack

Bug#1063047: Unable to run R CMD Rserve

On 4 February 2024 at 18:12, Jerome Charaoui wrote: | Package: r-cran-rserve | Version: 1.8-13-1 | Severity: important | | Hello, | | Running the command "R CMD Rserve" doesn't work because of missing | symlinks in the package. The error message shown is: | | /usr/lib/R/bin/Rcmd: 64: exec:

Re: [R-pkg-devel] Bioconductor reverse dependency checks for a CRAN package

Ivan, On 30 January 2024 at 18:56, Ivan Krylov via R-package-devel wrote: | Hello R-package-devel, | | What would you recommend in order to run reverse dependency checks for | a package with 182 direct strong dependencies from CRAN and 66 from | Bioconductor (plus 3 more from annotations and

Re: [R-pkg-devel] lost braces note on CRAN pretest related to \itemize

On 23 January 2024 at 19:39, Patrick Giraudoux wrote: | Has anyone an idea about what is going wrong ? \item has no braces following it. From a package I submitted today and for which I still have NEWS.Rd in the editor (indented here): \section{Changes in version 0.0.22 (2024-01-23)}{

Re: [R-pkg-devel] New Package Removal because Shared Library Too Large from Debugging Symbols

Johann, On 20 January 2024 at 14:38, Johann Gaebler wrote: | Hi everyone, | | I received the following message regarding `rar` , a package that I put up on CRAN two days ago: | | > Dear maintainer, | > | > Please see the problems shown on | >

Bug#1060101: Boost 1.81 removal

On 14 January 2024 at 06:49, Dirk Eddelbuettel wrote: | | FYI two days before you filed #1060101 I actually happened to have updated | r-cran-bh to 1.84.0 (upstream, which is me, went to the 1.84.0 version | released in December as Boost releases every four months) using 1.83: | |r-cran-bh

Bug#1060101: Boost 1.81 removal

On 14 January 2024 at 06:49, Dirk Eddelbuettel wrote: | | FYI two days before you filed #1060101 I actually happened to have updated | r-cran-bh to 1.84.0 (upstream, which is me, went to the 1.84.0 version | released in December as Boost releases every four months) using 1.83: | |r-cran-bh

Re: [R-pkg-devel] current docker image for ASAN

On 16 January 2024 at 15:54, Steven Scott wrote: | Greetings everyone, though I expect this message is mainly for Dirk. | | CRAN checks of my bsts/Boom package generate an ASAN error that the CRAN | maintainers have asked me to look into. I recall doing this before (this | error has been there

Re: [R-pkg-devel] checking CRAN incoming feasibility

On 17 January 2024 at 09:42, Simon Urbanek wrote: | that check always hangs for me (I don't think it likes NZ ;)), so I just use | | _R_CHECK_CRAN_INCOMING_REMOTE_=0 R CMD check --as-cran ... You can also set it in Renviron files consulted just for checks: $ grep INCOMING_=

Re: [R-pkg-devel] test failure: oldrel

done 4.3.2 2024-01-16 America/Chicago 4.2.2 2024-01-15 18:00:00 America/Chicago edd@rob:~$ Thanks to Seb for the cluebat wave. Dirk | | | On Tue, Jan 16, 2024 at 9:59 AM Dirk Eddelbuettel wrote: | | | Doesn't seem to be the case as it moderately easy to check (especially when | y

[R-pkg-devel] test failure: oldrel

Doesn't seem to be the case as it moderately easy to check (especially when you happen to have local images of r-base around anyway): edd@rob:~$ for v in 4.3.2 4.2.2 4.1.3 4.0.5 3.6.3 3.5.3 3.4.4 3.3.3; do echo -n "R ${v}: "; docker run --rm -ti r-base:${v} Rscript -e 'as.POSIXct(Sys.Date(),

Re: [R-sig-Debian] R

Hi, Can you please resend, but this time not in html format? The mailing list manager software swallows html; your email did not contain any plain text so there is nothing for us to read and (hopefully) help you with. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1060101: Boost 1.81 removal

+b2 * debian/control: Set Build-Depends: to current R version * debian/control: Switch to virtual debhelper-compat (= 13) -- Dirk Eddelbuettel Wed, 10 Jan 2024 07:20:09 -0600 So this should sort itself out by itself in a matter of days. r-cran-bh is healthy: https

Bug#1060101: Boost 1.81 removal

+b2 * debian/control: Set Build-Depends: to current R version * debian/control: Switch to virtual debhelper-compat (= 13) -- Dirk Eddelbuettel Wed, 10 Jan 2024 07:20:09 -0600 So this should sort itself out by itself in a matter of days. r-cran-bh is healthy: https

Bug#1059875: RM: rJava [i386] -- RoM: FTBFS as i386 builds no longer maintained upstream

( Resending to now correctly-typed package r-cran-rcdklibs -- Dirk ) On 11 January 2024 at 07:09, Dirk Eddelbuettel wrote: | | Package: ftp.debian.org | Severity: normal | | The rJava package (source package 'rjava', binary package r-cran-rjava) no | longer builds on i386 as most

  1   2   3   4   5   6   7   8   9   10   >