Bug#1037113: Should not be in /usr/games

reassign 1037113 screen-message thanks Binary package 'sm' is from source package 'screen-message' Binary package 'r-cran-sm' is from source package 'sm', which I maintain, and something totally different :-) Not the first crossed bug report so no worries, the reassign should work. Cheers,

Re: [R-sig-Debian] Fwd: package interflex

On 7 June 2023 at 08:37, Johan Andresen wrote: | I can understand why it changes the game. | | | It would be sweet if we could do something like r2u for Debian, but for now | we can't.  Switching between Debian and Ubuntu is not that onerous though. | | | Do you mind clarifying what

Re: [R-sig-Debian] Fwd: package interflex

On 7 June 2023 at 11:55, Johan Andresen wrote: | Btw Dirk, can I help package interflex for apt? Please be welcome to refer me | to guidelines/a manual for doing so if you can imagine it happening. Well I already replied to you saying that for me Rscript -e 'install.packages("interflex")'

Re: [R-sig-Debian] Fwd: package interflex

On 6 June 2023 at 17:53, Richard Careaga wrote: | I was delighted I with how fast (faster than a tickled toddler giggles) r2u scarfed packages I. up my Pop!_OS (Ubuntu in party attire tuned for System76). But, despite 40 years as my own sys admin (classic fool for a client?), I bolluxed up,

Re: [R-sig-Debian] Fwd: package interflex

ething like r2u for Debian, but for now we can't. Switching between Debian and Ubuntu is not that onerous though. Cheers, Dirk | Johan | | | | | Den tirs. 6. jun. 2023 kl. 19.58 skrev Dirk Eddelbuettel : | | | On 6 June 2023 at 19:37, Johan Andresen wrote: | | I'd like input on how to in

Re: [R-sig-Debian] why is KEYWORDS.db not in '/usr/lib/R/doc/' but in '/usr/share/R/doc/'?

On 6 June 2023 at 22:29, Johan Andresen wrote: | Thanks, Dirk and Ivan | | Now I better understand what is going on. Sweet this help is already in the | github issue. It's an issue somewhere between Laurent (for rpy2) and me (for the R package and his rpy2 on Debian) and we should be able to

Re: [R-sig-Debian] package interflex

On 6 June 2023 at 19:37, Johan Andresen wrote: | I'd like input on how to install interflex | (note the instructions on its | github). It says install.packages("interflex") -- did you try that? | The installation failed on stable/bullseye, also when

Re: [R-sig-Debian] why is KEYWORDS.db not in '/usr/lib/R/doc/' but in '/usr/share/R/doc/'?

Hi Johan, On 6 June 2023 at 18:55, Johan Andresen wrote: | Hi r-sig-debian, | | I feel lucky to have found out that `/doc/KEYWORDS.db` is in `/usr/share/R/`, | not in `usr/lib/R/` where rpy2 in python apparently looks for it when | trying to search help in R from the python environment. it

Re: [R-pkg-devel] How to request for an Non Maintainer update - NMU

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 /

Bug#1036071: fixed in gsl 2.7.1+dfsg-4

On 2 June 2023 at 20:57, Paul Gevers wrote: | Hi Dirk, | | On 02-06-2023 20:38, Dirk Eddelbuettel wrote: | > | Are you sure? I just diffed the source to see if I should unblock and | > | got this: | > | > I would appear I did NOT add that one line to debian/control !! Doh !! | &g

Bug#1036071: fixed in gsl 2.7.1+dfsg-4

On 2 June 2023 at 20:57, Paul Gevers wrote: | Hi Dirk, | | On 02-06-2023 20:38, Dirk Eddelbuettel wrote: | > | Are you sure? I just diffed the source to see if I should unblock and | > | got this: | > | > I would appear I did NOT add that one line to debian/control !! Doh !! | &g

Bug#1036071: fixed in gsl 2.7.1+dfsg-4

(with thanks to | +Andreas Beckmann for the suggestion) (Closes: #1036071) | + | + * debian/control: Set Standards-Version: to current version | + | + -- Dirk Eddelbuettel Sun, 14 May 2023 21:25:16 -0500 | + | gsl (2.7.1+dfsg-3) unstable; urgency=medium | | * debian/cont

Bug#1036071: fixed in gsl 2.7.1+dfsg-4

(with thanks to | +Andreas Beckmann for the suggestion) (Closes: #1036071) | + | + * debian/control: Set Standards-Version: to current version | + | + -- Dirk Eddelbuettel Sun, 14 May 2023 21:25:16 -0500 | + | gsl (2.7.1+dfsg-3) unstable; urgency=medium | | * debian/cont

Bug#1037001: r-cran-htmltable: Homepage link doesn't work because it is case-sensitive

On 31 May 2023 at 15:18, David Fifield wrote: | Package: r-cran-htmltable | Severity: minor | X-Debbugs-Cc: da...@bamsoftware.com | | The package homepage https://cran.r-project.org/package=htmltable | leads to a 404 error page. The link | https://cran.r-project.org/package=htmlTable works

Re: [Rcpp-devel] Rcpp::sourceCpp Problem with R 4.3 update

On 30 May 2023 at 14:27, Dominick Samperi wrote: | Looks like the recent update to R 4.3 broke Rcpp::sourceCpp. | | Here is a simple example... | | library(Rcpp) | Rcpp::sourceCpp(code=' |   #include |   using namespace Rcpp; |   // [[Rcpp::export()]] |   SEXP cpptest(NumericVector v) { |    

Bug#1036868: mlpack 4.1.0 available

Severity: normal Package: mlpack mlpack 4.1.0 came out (relatively quietly) a month ago. I think it should be a fairly simple upgrade over 4.0.1. It would be nice if you could update it. I stuck your 4.0.1 it my launchpad PPA for use on Ubuntu 22.04 which worked fine as usual. It needed

Bug#1036868: mlpack 4.1.0 available

Severity: normal Package: mlpack mlpack 4.1.0 came out (relatively quietly) a month ago. I think it should be a fairly simple upgrade over 4.0.1. It would be nice if you could update it. I stuck your 4.0.1 it my launchpad PPA for use on Ubuntu 22.04 which worked fine as usual. It needed

Re: [Rd] Heap access across multiple calls from R to C++

On 24 May 2023 at 09:09, Ivan Krylov wrote: | On Wed, 24 May 2023 02:08:25 +0200 | wrote: | > Is there a better way to do this? | | The .Call() interface (where functions take an arbitrary number of | native R objects and return a native R object) combined with external | pointers is likely to

Bug#1036608: gretl: broken syminks: /usr/share/gretl/{doc,examples} -> ../doc/gretl-doc/*

On 23 May 2023 at 10:32, Andreas Beckmann wrote: | Package: gretl | Version: 2022c-1 | Severity: normal | User: debian...@lists.debian.org | Usertags: piuparts | | Hi, | | during a test with piuparts I noticed your package ships (or creates) | broken symlinks: | | 0m54.7s ERROR: FAIL: Broken

Bug#1036308: r-base: R CMD check --as-cran fails for packages with math in help files

On 19 May 2023 at 07:08, Johannes Ranke wrote: | Package: r-base | Version: 4.3.0-1 | Severity: normal | | Dirk, | | as recently discussed on the r-pkg-devel list[1], checking a package with | using the --as-cran option fails when using R 4.3.0-1 currently sitting | in unstable. | | Please

Re: [R-pkg-devel] Problems with devtools::build() in R

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

Re: [R-pkg-devel] Are the CRAN macOS builders down?

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

Re: [R-pkg-devel] Are the CRAN macOS builders down?

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: | > | >

Bug#1035428: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

On 16 May 2023 at 20:13, Nilesh Patra wrote: | Uh, no. Maybe you misunderstood my suggestion. The t-p-u way was for Indeed! | r-base can continue to stay where it already is at the moment :) Yep. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1035428: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

On 16 May 2023 at 20:13, Nilesh Patra wrote: | Uh, no. Maybe you misunderstood my suggestion. The t-p-u way was for Indeed! | r-base can continue to stay where it already is at the moment :) Yep. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Re: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

On 16 May 2023 at 20:13, Nilesh Patra wrote: | Uh, no. Maybe you misunderstood my suggestion. The t-p-u way was for Indeed! | r-base can continue to stay where it already is at the moment :) Yep. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Re: [R-pkg-devel] Problems with devtools::build() in R

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 =

[R-pkg-devel] Are the CRAN macOS builders down?

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

Bug#1035428: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

On 16 May 2023 at 19:49, Nilesh Patra wrote: | On Tue, May 16, 2023 at 07:25:15PM +0530, Nilesh Patra wrote: | > I personally prefer "1" over 2 as it is less noise (and effort). | | On second thoughts, I think sending it via testing-proposed-updates | would be a better thing to do, as this case

Bug#1035428: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

On 16 May 2023 at 19:49, Nilesh Patra wrote: | On Tue, May 16, 2023 at 07:25:15PM +0530, Nilesh Patra wrote: | > I personally prefer "1" over 2 as it is less noise (and effort). | | On second thoughts, I think sending it via testing-proposed-updates | would be a better thing to do, as this case

Re: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

On 16 May 2023 at 19:49, Nilesh Patra wrote: | On Tue, May 16, 2023 at 07:25:15PM +0530, Nilesh Patra wrote: | > I personally prefer "1" over 2 as it is less noise (and effort). | | On second thoughts, I think sending it via testing-proposed-updates | would be a better thing to do, as this case

Bug#1035428: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

d to some better | regular expression. Nice catch and suggestion! On 16 May 2023 at 19:27, Nilesh Patra wrote: | On Tue, May 16, 2023 at 08:26:21AM -0500, Dirk Eddelbuettel wrote: | > Note that none of this affects the release. My recommendation is temporarily | > suspend the autopkgtest in

Bug#1035428: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

d to some better | regular expression. Nice catch and suggestion! On 16 May 2023 at 19:27, Nilesh Patra wrote: | On Tue, May 16, 2023 at 08:26:21AM -0500, Dirk Eddelbuettel wrote: | > Note that none of this affects the release. My recommendation is temporarily | > suspend the autopkgtest in

Re: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

d to some better | regular expression. Nice catch and suggestion! On 16 May 2023 at 19:27, Nilesh Patra wrote: | On Tue, May 16, 2023 at 08:26:21AM -0500, Dirk Eddelbuettel wrote: | > Note that none of this affects the release. My recommendation is temporarily | > suspend the autopkgtest in

Bug#1035428: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

On 16 May 2023 at 15:01, Andreas Tille wrote: | Hi, | | when fixing bug #1035428 I realised test suite issues with | | r-cran-thematic [1] |-> Error in `svglite_(filename, bg, width, height, pointsize, standalone, | always_valid)`: Graphics API version mismatch | |

Bug#1035428: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

On 16 May 2023 at 15:01, Andreas Tille wrote: | Hi, | | when fixing bug #1035428 I realised test suite issues with | | r-cran-thematic [1] |-> Error in `svglite_(filename, bg, width, height, pointsize, standalone, | always_valid)`: Graphics API version mismatch | |

Re: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

On 16 May 2023 at 15:01, Andreas Tille wrote: | Hi, | | when fixing bug #1035428 I realised test suite issues with | | r-cran-thematic [1] |-> Error in `svglite_(filename, bg, width, height, pointsize, standalone, | always_valid)`: Graphics API version mismatch | |

Bug#1036071: libgsl27: please add Breaks: libgsl25 for smoother opgrades from bullseye

On 15 May 2023 at 03:15, Andreas Beckmann wrote: | On 15/05/2023 02.58, Dirk Eddelbuettel wrote: | > | Yes thank you -- that sounds sensible. And we would then nag the release | > | team to get this out in the release? | | yes | | > Oh, and to be extra plain: upload to unstable as a

Bug#1036071: libgsl27: please add Breaks: libgsl25 for smoother opgrades from bullseye

On 15 May 2023 at 03:15, Andreas Beckmann wrote: | On 15/05/2023 02.58, Dirk Eddelbuettel wrote: | > | Yes thank you -- that sounds sensible. And we would then nag the release | > | team to get this out in the release? | | yes | | > Oh, and to be extra plain: upload to unstable as a

Bug#1036071: libgsl27: please add Breaks: libgsl25 for smoother opgrades from bullseye

On 14 May 2023 at 19:50, Dirk Eddelbuettel wrote: | | On 15 May 2023 at 02:21, Andreas Beckmann wrote: | | Package: libgsl27 | | Version: 2.7.1+dfsg-3 | | Severity: serious | | Tags: patch | | User: debian...@lists.debian.org | | Usertags: piuparts | | | | Hi, | | | | libgsl25 from bullseye

Bug#1036071: libgsl27: please add Breaks: libgsl25 for smoother opgrades from bullseye

On 14 May 2023 at 19:50, Dirk Eddelbuettel wrote: | | On 15 May 2023 at 02:21, Andreas Beckmann wrote: | | Package: libgsl27 | | Version: 2.7.1+dfsg-3 | | Severity: serious | | Tags: patch | | User: debian...@lists.debian.org | | Usertags: piuparts | | | | Hi, | | | | libgsl25 from bullseye

Bug#1036071: libgsl27: please add Breaks: libgsl25 for smoother opgrades from bullseye

On 15 May 2023 at 02:21, Andreas Beckmann wrote: | Package: libgsl27 | Version: 2.7.1+dfsg-3 | Severity: serious | Tags: patch | User: debian...@lists.debian.org | Usertags: piuparts | | Hi, | | libgsl25 from bullseye and libgsl27 from bookworm are not co-installable | due to their strict

Bug#1036071: libgsl27: please add Breaks: libgsl25 for smoother opgrades from bullseye

On 15 May 2023 at 02:21, Andreas Beckmann wrote: | Package: libgsl27 | Version: 2.7.1+dfsg-3 | Severity: serious | Tags: patch | User: debian...@lists.debian.org | Usertags: piuparts | | Hi, | | libgsl25 from bullseye and libgsl27 from bookworm are not co-installable | due to their strict

Re: [R-pkg-devel] Please install cmake on macOS builders

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

Re: [R-pkg-devel] Please install cmake on macOS builders

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

Re: [R-pkg-devel] Please install cmake on macOS builders

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

Re: [R-pkg-devel] Please install cmake on macOS builders

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. |

Re: [R-pkg-devel] Please install cmake on macOS builders

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

[R-pkg-devel] Please install cmake on macOS builders

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

Re: [R-pkg-devel] How to declare Bioconductor Dependencies in the Description File of my R Package

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

Re: [R-pkg-devel] How to declare Bioconductor Dependencies in the Description File of my R Package

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

Re: [R-SIG-Mac] 'Default' macos (x86) download URL now gone?

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

Re: [R-pkg-devel] 'Default' macos (x86) download URL now gone?

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

Re: [R-pkg-devel] katex

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

Re: [R-pkg-devel] katex

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

[R-pkg-devel] 'Default' macos (x86) download URL now gone?

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

Re: [R-pkg-devel] Segmentation Fault cause 'memory not mapped' on Debian only

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

Bug#1034683: r-base: new upstream release unintentionally uploaded to unstable

Hi Simon, Thanks for the long and thoughtful and detailed reply. Just 'sitting back' will do just fine then. R releases annually in April, the 4.2.* series was just fine. We had an usual event in that R Core upstream asked (a first in ~25 years) to patch 4.2.2, hence the somewhat unusual

Bug#1034683: r-base: new upstream release unintentionally uploaded to unstable

Hi Simon, Thanks for the long and thoughtful and detailed reply. Just 'sitting back' will do just fine then. R releases annually in April, the 4.2.* series was just fine. We had an usual event in that R Core upstream asked (a first in ~25 years) to patch 4.2.2, hence the somewhat unusual

Re: [R-pkg-devel] Segmentation Fault cause 'memory not mapped' on Debian only

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

Bug#1034683: r-base: new upstream release unintentionally uploaded to unstable

On 21 April 2023 at 10:51, Dirk Eddelbuettel wrote: | | On 21 April 2023 at 16:23, Simon McVittie wrote: | | Source: r-base | | Version: 4.3.0-1 | | Severity: serious | | Justification: maintainer presumably considers this version to be unsuitable for bookworm | | | | > r-base (4.3.

Bug#1034683: r-base: new upstream release unintentionally uploaded to unstable

On 21 April 2023 at 10:51, Dirk Eddelbuettel wrote: | | On 21 April 2023 at 16:23, Simon McVittie wrote: | | Source: r-base | | Version: 4.3.0-1 | | Severity: serious | | Justification: maintainer presumably considers this version to be unsuitable for bookworm | | | | > r-base (4.3.

Bug#1034683: r-base: new upstream release unintentionally uploaded to unstable

On 21 April 2023 at 16:23, Simon McVittie wrote: | Source: r-base | Version: 4.3.0-1 | Severity: serious | Justification: maintainer presumably considers this version to be unsuitable for bookworm | | > r-base (4.3.0-1) unstable; urgency=medium | > . | > * New upstream release (into

Bug#1034683: r-base: new upstream release unintentionally uploaded to unstable

On 21 April 2023 at 16:23, Simon McVittie wrote: | Source: r-base | Version: 4.3.0-1 | Severity: serious | Justification: maintainer presumably considers this version to be unsuitable for bookworm | | > r-base (4.3.0-1) unstable; urgency=medium | > . | > * New upstream release (into

Re: [R-pkg-devel] (no subject)

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)

Re: [ESS] Emacs, ESS and Rmarkdown: Is this the way compile is supposed to work?

On 15 April 2023 at 19:21, Kevin Zembower via ESS-help wrote: | I'm trying to get Emacs, ESS and Rmarkdown to work together for the | first time. Therefore, the problem might be me, and not the software. | | I have this program as Prob_11.Rmd: |

Re: [R] converting to date object...

That is what I wrote the anytime package for: effortless automatic parsing. Also works for dates: > library(anytime) > anydate("12 APR 2023") [1] "2023-04-12" > Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org __

Bug#1034024: RM: tiledb -- ROM remove remaining experimental upload too

Package: ftp.debian.org Severity: normal In #1033410 we suggested that package tiledb may not be a perfect fit for Debian and suggested its removal. Reverse dependencies have been taken care of, and the package is now removed from testing and unstable. However, a one-off upload to

Re: [R-pkg-devel] correcting errors in an existing package

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

Re: [R-pkg-devel] OpenMP and CRAN checks

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

Re: [Rd] Let R compile for libcurl8 ?

On 3 April 2023 at 15:07, Detlef Steuer wrote: | The same Inar reported for rawhide | (https://stat.ethz.ch/pipermail/r-devel/2023-March/082482.html) | is true for SuSE's distros. | | Right now R does not compile with libcurl8, but SuSE Tumbleweed/Factory | switched to 8 a week ago. | | Would

Re: [Rcpp-devel] Locating an Instance of a Reference Class in the Environment

inappropriate | to | >> me. | >> | >> On March 24, 2023 10:43:34 AM PDT, Dirk Eddelbuettel | >> wrote: | >> > | >> >On 24 March 2023 at 13:08, Matthew Supernaw - NOAA Federal wrote: | >> >| I'm sure it's possible to

Re: [R-sig-Debian] Announcing r2u: 20k CRAN binaries for Ubuntu 22.04 + 20.04

On 26 March 2023 at 18:53, Dirk Eddelbuettel wrote: | | On 26 March 2023 at 18:30, Dirk Eddelbuettel wrote: | | Over the last few months I have provided multiple 'demos' as animated gifs | | showing how for example `system.time(install.package("tinyverse"))` installs | | all thes

Re: [R-sig-Debian] Announcing r2u: 20k CRAN binaries for Ubuntu 22.04 + 20.04

On 26 March 2023 at 18:30, Dirk Eddelbuettel wrote: | Over the last few months I have provided multiple 'demos' as animated gifs | showing how for example `system.time(install.package("tinyverse"))` installs | all these packages and all their dependencies in under twenty seconds (!!)

[R-sig-Debian] Announcing r2u: 20k CRAN binaries for Ubuntu 22.04 + 20.04

The r2u repository [1] has been providing CRAN packages as Ubuntu binaries (with *full* and *complete* dependency resolution) since last May. It is being served from a well-connect Internet2 mirror thanks to the University of Illinois making it *fast*. By relying on the bspm package [2], it

Re: [R-pkg-devel] Another DLL requires the use of native symbols thread

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

Bug#1033456: genomicsdb may need build adjustment

Package: genomicsdb Severity: normal I recently filed #1033410 and requested to have tiledb removed from Debian as the build has always severely constrained by both a lack of 'cloud' support, a mismatch with pinned dependencies at different versions of required libraries, an upcoming change to

Bug#1033453: RM: tiledb-py -- ROM,NPOASR as build-depends tiledb should RM

Package: ftp.debian.org Severity: normal As argued in #1033410, tiledb is not really a good fit for Debian and should RM. As such, tiledb-py cannot build and needs to RM as well. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1033454: RM: tiledb-r -- ROM,NPOASR as build-depends tiledb should RM

Package: ftp.debian.org Severity: normal As argued in #1033410, tiledb is not really a good fit for Debian and should RM. As such, tiledb-r cannot build and needs to RM as well. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Re: [Rcpp-devel] Locating an Instance of a Reference Class in the Environment

On 24 March 2023 at 13:08, Matthew Supernaw - NOAA Federal wrote: | I'm sure it's possible to do from the R side, however, the requirement is to | hide this from the end user and set the reference objects name to the declared | name from the R environment. If I view the environment in RStudio,

Bug#1033410: RM: tiledb -- ROM as full builds not possible within Debian

Package: ftp.debian.org Severity: normal The TileDB source package uses cmake and find_package for external resources; the upstream team maintaining the core library is going to switch to vcpkg soon. A full featured TileDB really needs the AWS SDK which we still do not have, would benefit from

Re: [Rcpp-devel] Locating an Instance of a Reference Class in the Environment

On 22 March 2023 at 13:31, Matthew Supernaw - NOAA Federal wrote: | I'm trying to get an instance of a reference class (vonBertalanffyInterface) | from the R environment with the following code: | | void SetName(vonBertalanffyInterface& v) { | |     Rcpp::Environment env =

Re: [R-pkg-devel] DLL requires the use of native symbols

d 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() where

Re: [R-pkg-devel] DLL requires the use of native symbols

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

Re: [Rd] Request: better default R_LIBS_USER

On 16 March 2023 at 17:15, Henrik Bengtsson wrote: | We're all starting out with a fresh R_LIBS_USER once a year when a new | minor version of R is released, Maybe not "we all". I don't, and I know other Linux users who don't force a rebuild unless needed (as with R 3.6.* -> R 4.0.0). R

Re: [Rd] Request: better default R_LIBS_USER

On 16 March 2023 at 13:39, Felipe Contreras wrote: | I see R by default installs packages in ~/R. I know I can change the | default directory with R_LIBS_USER, but software shouldn't be | polluting the home directory. | | For example both python and node install packages to ~/.local/lib, | ruby

Bug#1032120: Upload of new upstream version before fix has migrated to testing (Was: Re: Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic)

Why not wait a week on 2.15.0-1 which now 'Too young, only 4 of 10 days old'? Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1032120: Upload of new upstream version before fix has migrated to testing (Was: Re: Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic)

Why not wait a week on 2.15.0-1 which now 'Too young, only 4 of 10 days old'? Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic

Hi Graham, On 28 February 2023 at 19:36, Graham Inggs wrote: | Hi Dirk | | Thanks for the quick upload! | Already got a successful build of tiledb-py on riscv64[1]. | | On Tue, 28 Feb 2023 at 17:14, Dirk Eddelbuettel wrote: | > TileDB upstream does everything in CMake (which I do not fu

Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic

Hi Graham, On 28 February 2023 at 19:36, Graham Inggs wrote: | Hi Dirk | | Thanks for the quick upload! | Already got a successful build of tiledb-py on riscv64[1]. | | On Tue, 28 Feb 2023 at 17:14, Dirk Eddelbuettel wrote: | > TileDB upstream does everything in CMake (which I do not fu

Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic

(Whoops typed this hours ago but apparently did not send from Emacs. --D.) Hi Graham, On 28 February 2023 at 10:49, Graham Inggs wrote: | Source: tiledb | Version: 2.14.1-1 | Severity: serious | Tags: ftbfs patch | Control: affects -1 src:tiledb-py | | Hi Dirk | | TileDB uses atomic

Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic

(Whoops typed this hours ago but apparently did not send from Emacs. --D.) Hi Graham, On 28 February 2023 at 10:49, Graham Inggs wrote: | Source: tiledb | Version: 2.14.1-1 | Severity: serious | Tags: ftbfs patch | Control: affects -1 src:tiledb-py | | Hi Dirk | | TileDB uses atomic

Re: [R-pkg-devel] Ignoring a compiler warning?

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

Re: [Rcpp-devel] Problem with RCPP Paralell

Hi Roberto, Very briefly: 1) We spell it Rcpp. Capital R, lowercase cpp. 2) The package you inquire about is called RcppParallel. 3) You didn't list the repo making it harder for us to help you. As a little bit of GitHub searching reveals, it is here

Re: [R-pkg-devel] Package submission rejected as it fails checks on Debian

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

Re: [R-pkg-devel] Package submission rejected as it fails checks on Debian

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

Re: [R-pkg-devel] Package submission rejected as it fails checks on Debian

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

Re: [Rcpp-devel] CRAN note about std::cout in shared library

Hi Kassel, On 7 February 2023 at 02:57, Kassel Hingee wrote: | I'm running into CRAN check notes about std::cout being present in the Cpp code of a library I'm using. | | Found ‘_ZSt4cout’, possibly from ‘std::cout’ (C++) | | It looks like Rcpp is automatically redirecting the std::cout

Re: [ESS] build problem

On 5 February 2023 at 15:01, Sparapani, Rodney via ESS-help wrote: | I don�t have 28 on this machine. I am using 26 since there is not much | benefit upgrading. I am really sorry but I cannot let this stand. It is too close to FUD. As a general rule, newer *is* better. Features get added, bugs

Re: [Rcpp-devel] RInline::repl() issues

Dominick, On 3 February 2023 at 20:02, Dominick Samperi wrote: | I'm sorry to say that the RInline::repl() issues are not resolved, and to | resolve them would likely require help from R core. | | Here's the test case: | library(sphereplot) | rgl.sphgrid(longtype="D") | | Under Linux there is

<    1   2   3   4   5   6   7   8   9   10   >