Re: [R-pkg-devel] DESCRIPTION file question

On 22 July 2023 at 16:07, Dirk Eddelbuettel wrote: | | Taylor, | | I believe we have been over this at StackOverflow but you may by now have | deleted the question/ | | On 21 July 2023 at 20:51, taylor brown via R-package-devel wrote: | | I have a question about the DESCRIPTION file of an R

Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386

On 22 July 2023 at 21:45, Paul Gevers wrote: | Source: lme4 | Version: 1.1-31-1 | Severity: serious | Control: close -1 1.1-34-1 | X-Debbugs-CC: debia...@lists.debian.org | Tags: sid trixie | User: release.debian@packages.debian.org | Usertags: out-of-sync | | Dear maintainer(s), | | The

Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386

On 22 July 2023 at 21:45, Paul Gevers wrote: | Source: lme4 | Version: 1.1-31-1 | Severity: serious | Control: close -1 1.1-34-1 | X-Debbugs-CC: debia...@lists.debian.org | Tags: sid trixie | User: release.debian@packages.debian.org | Usertags: out-of-sync | | Dear maintainer(s), | | The

Re: [R-pkg-devel] DESCRIPTION file question

Taylor, I believe we have been over this at StackOverflow but you may by now have deleted the question/ On 21 July 2023 at 20:51, taylor brown via R-package-devel wrote: | I have a question about the DESCRIPTION file of an R package that has some c++ dependencies. | | This package of mine

Re: [R-pkg-devel] macOS results not mirrored/updated at CRAN

Simon, This still persists. As Murray reported, it happened for a while now, it is still happening eg package tiledb has been rebuilt everywhere [1] since the upload a few days ago -- yet the results page still reports builds two uploads ago [2] for both arm64 variants of your macOS setup. Can

Re: [R-pkg-devel] macOS results not mirrored/updated at CRAN

On 16 July 2023 at 14:31, Simon Urbanek wrote: | I looked into it and there was no issue on the build machine or staging server, so it will require some more digging in the international waters .. hopefully sometime next week… Thanks for checking, sometimes one-offs happen. Dirk --

Re: [R-pkg-devel] macOS results not mirrored/updated at CRAN

Simon, On 12 July 2023 at 19:02, Dirk Eddelbuettel wrote: | | Simon, | | It looks like some result mirroring / pushing from your machines to CRAN fell | over. One of my packages, digest 0.6.33, arrived on CRAN about a week ago, | is built almost everywhere (apart from macOS_release_x86_64

Re: [R-pkg-devel] Feedback on "Using Rust in CRAN packages"

The concerns over github going away (!!) (or altering references, tags, releases, ...) may be somewhat alleviated by Software Heritage [1] covering and 'preserving' it. FWIW I briefly spoke about that iniative and a possible CRAN connection at useR! in Toulouse four years ago [2]. I think I

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Graham, On 13 July 2023 at 18:59, Graham Inggs wrote: | I believe the attached patch should do the trick. It's basically | Paul's list from message #210, plus r-cran-interval and | r-cran-maldiquant. I've also used a << relationship against the | versions in unstable, and appended a tilde at

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Graham, On 13 July 2023 at 18:59, Graham Inggs wrote: | I believe the attached patch should do the trick. It's basically | Paul's list from message #210, plus r-cran-interval and | r-cran-maldiquant. I've also used a << relationship against the | versions in unstable, and appended a tilde at

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Hi Graham, On 13 July 2023 at 11:14, Graham Inggs wrote: | On Wed, 12 Jul 2023 at 19:07, Dirk Eddelbuettel wrote: | > On 12 July 2023 at 19:47, Paul Gevers wrote: | > | Yes, you only need to carry the Breaks until in the next release. So | > | every Breaks that's present in the r-bas

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Hi Graham, On 13 July 2023 at 11:14, Graham Inggs wrote: | On Wed, 12 Jul 2023 at 19:07, Dirk Eddelbuettel wrote: | > On 12 July 2023 at 19:47, Paul Gevers wrote: | > | Yes, you only need to carry the Breaks until in the next release. So | > | every Breaks that's present in the r-bas

[R-pkg-devel] macOS results not mirrored/updated at CRAN

Simon, It looks like some result mirroring / pushing from your machines to CRAN fell over. One of my packages, digest 0.6.33, arrived on CRAN about a week ago, is built almost everywhere (apart from macOS_release_x86_64 stuck at 0.6.32) but the result page still has nags from the 0.6.31 build

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Hi Paul, On 12 July 2023 at 19:47, Paul Gevers wrote: | On 12-07-2023 16:02, Dirk Eddelbuettel wrote: | > I can add the Breaks as a 'best of the worse alternative'. And, I presume, I | > can remove the existing four-year breaks? [1] | | Yes, you only need to carry the Breaks until in th

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Hi Paul, On 12 July 2023 at 19:47, Paul Gevers wrote: | On 12-07-2023 16:02, Dirk Eddelbuettel wrote: | > I can add the Breaks as a 'best of the worse alternative'. And, I presume, I | > can remove the existing four-year breaks? [1] | | Yes, you only need to carry the Breaks until in th

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Hi Paul, On 11 July 2023 at 20:36, Paul Gevers wrote: | On 11-07-2023 02:43, Dirk Eddelbuettel wrote: | I'm totally on board for technical excellence, although I think we have | different things in mind when we say that. | | In Debian, with more QA than we ever had before, we're finding

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Hi Paul, On 11 July 2023 at 20:36, Paul Gevers wrote: | On 11-07-2023 02:43, Dirk Eddelbuettel wrote: | I'm totally on board for technical excellence, although I think we have | different things in mind when we say that. | | In Debian, with more QA than we ever had before, we're finding

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

On 10 July 2023 at 19:43, Dirk Eddelbuettel wrote: | Someone simply didn't update our Debian package, so it lacks this change and | fingers point at r-base when the fault, if there is one, is to let our | package slip behind a compilation and code standard established at CRAN for | the R 4.3.0

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

On 10 July 2023 at 19:43, Dirk Eddelbuettel wrote: | Someone simply didn't update our Debian package, so it lacks this change and | fingers point at r-base when the fault, if there is one, is to let our | package slip behind a compilation and code standard established at CRAN for | the R 4.3.0

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Paul, Here is a case in point from looking at the current excluses list (which is by now indeed a little shorter). One package that jumps out is r-cran-maldiquant. We are at version 1.22, with Debian build 1.22-1. But one second at the CRAN site and the page for the package shows that it is

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Paul, Here is a case in point from looking at the current excluses list (which is by now indeed a little shorter). One package that jumps out is r-cran-maldiquant. We are at version 1.22, with Debian build 1.22-1. But one second at the CRAN site and the page for the package shows that it is

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Hi Paul, On 9 July 2023 at 20:11, Paul Gevers wrote: | On 09-07-2023 18:41, Dirk Eddelbuettel wrote: | > On 9 July 2023 at 17:40, Paul Gevers wrote: | > | Did we already discuss that r-cran-ps also seems to be impacted by the | > | r-base change of the symbols thingy, as can be seen

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Hi Paul, On 9 July 2023 at 20:11, Paul Gevers wrote: | On 09-07-2023 18:41, Dirk Eddelbuettel wrote: | > On 9 July 2023 at 17:40, Paul Gevers wrote: | > | Did we already discuss that r-cran-ps also seems to be impacted by the | > | r-base change of the symbols thingy, as can be seen

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

On 9 July 2023 at 11:41, Dirk Eddelbuettel wrote: | For spacetime and stars I suspect (based on past experience) possible | interaction from the underlying graphics libraries. Absent-minded typing error: "geospatial", of course. Not "graphics". Dirk -- dirk.eddelbuettel

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

On 9 July 2023 at 11:41, Dirk Eddelbuettel wrote: | For spacetime and stars I suspect (based on past experience) possible | interaction from the underlying graphics libraries. Absent-minded typing error: "geospatial", of course. Not "graphics". Dirk -- dirk.eddelbuettel

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Paul, On 9 July 2023 at 17:40, Paul Gevers wrote: | Did we already discuss that r-cran-ps also seems to be impacted by the | r-base change of the symbols thingy, as can be seen in r-cran-xopen [1]. Correct me if I am wrong but the "symbols thingy" was not a change in R 4.2.* to R 4.3.*. It

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

Paul, On 9 July 2023 at 17:40, Paul Gevers wrote: | Did we already discuss that r-cran-ps also seems to be impacted by the | r-base change of the symbols thingy, as can be seen in r-cran-xopen [1]. Correct me if I am wrong but the "symbols thingy" was not a change in R 4.2.* to R 4.3.*. It

Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

Thanks for closing it. I think in due course as you will see there a) new tag does not help today (we already took care of the six packages needing a rebuild because of the graphics engine constant changing) and b) what is likely being the exact same sets of packages having issue

Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing (Was: Bug#1040001: transition: r-base)

On 7 July 2023 at 00:33, Nilesh Patra wrote: | I think we are hitting this issue here: https://github.com/tidyverse/dplyr/issues/6793 | The comment says "Looks like some package in the stack sets R_forceSymbols(dll, TRUE)" and that package is tibble | | | $ grep -rnw R_forceSymbols | |

Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing (Was: Bug#1040001: transition: r-base)

On 7 July 2023 at 00:33, Nilesh Patra wrote: | I think we are hitting this issue here: https://github.com/tidyverse/dplyr/issues/6793 | The comment says "Looks like some package in the stack sets R_forceSymbols(dll, TRUE)" and that package is tibble | | | $ grep -rnw R_forceSymbols | |

Re: [R-pkg-devel] Warning 'as.data.frame.POSIXct()' is deprecated

On 6 July 2023 at 08:14, Dirk Eddelbuettel wrote: | | On 6 July 2023 at 14:31, Vincent van Hees wrote: | | Thanks, in that case the REPLEX for the issue may need to be: | | | | > remember = Sys.getenv("_R_CHECK_AS_DATA_FRAME_EXPLICIT_METHOD_") | |

Re: [R-pkg-devel] Warning 'as.data.frame.POSIXct()' is deprecated

On 6 July 2023 at 14:31, Vincent van Hees wrote: | Thanks, in that case the REPLEX for the issue may need to be: | | > remember = Sys.getenv("_R_CHECK_AS_DATA_FRAME_EXPLICIT_METHOD_") | > Sys.setenv("_R_CHECK_AS_DATA_FRAME_EXPLICIT_METHOD_" = TRUE) | > data.frame(time = Sys.time()) |

Bug#1040001: transition: r-base

Paul, Graham, r-base 4.3.1-2 is now on its way. You will have to update / tweak the ben file as there is no 'r-api-4.3' tag as there is no such thing API change upstream in R itself. Filing the bug reports against the handful of packages testing the graphics engine version was the right thing

Bug#1040001: transition: r-base

Paul, Graham, r-base 4.3.1-2 is now on its way. You will have to update / tweak the ben file as there is no 'r-api-4.3' tag as there is no such thing API change upstream in R itself. Filing the bug reports against the handful of packages testing the graphics engine version was the right thing

Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

Control: severity -1 normal I am changing this back because a) there is no general bug in R 4.3.1, and there newer was there were a few packages requiring an update to the new graphics engine version (as the packages choose to call R_GE_checkVersionOrDie, it is coming from

Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

Control: severity -1 normal I am changing this back because a) there is no general bug in R 4.3.1, and there newer was there were a few packages requiring an update to the new graphics engine version (as the packages choose to call R_GE_checkVersionOrDie, it is coming from

Bug#1040341: r-base: please drop libpcre3-dev dependencies

On 4 July 2023 at 16:00, Graham Inggs wrote: | Source: r-base | Version: 4.3.1-1 | Tags: patch | | Hi Maintainer | | r-base has a build-dependency, and r-base-dev has a dependency, on the | ancient libpcre3-dev package. I believe these are no longer required | since the dependencies on the

Bug#1040038: r-base-core: Please provide r-graphics-api-*

On 1 July 2023 at 15:26, Graham Inggs wrote: | Your patch has 'rgraphicsapiversion' and 'r-graphics-api-4.3'. | | Upstream [1] refer to it as follows: | | The graphics engine version, R_GE_version, has been bumped to 16 | and so packages that provide graphics devices should be |

Bug#1040001: transition: r-base

This is not a bug in r-base, and does not warrant a transition. I have written at some length about it, and (if I find some time) will expand on it in blog post. I will also try to coordinate with upstream. In short, R header GraphicsEngine.h [1] defines an integer constant declaring the

Bug#1040001: transition: r-base

This is not a bug in r-base, and does not warrant a transition. I have written at some length about it, and (if I find some time) will expand on it in blog post. I will also try to coordinate with upstream. In short, R header GraphicsEngine.h [1] defines an integer constant declaring the

Bug#1039926: svglite requires rebuild under R 4.3.*

On 29 June 2023 at 10:22, Dirk Eddelbuettel wrote: | | Package: r-cran-svglite | Version: 2.1.1-1 | Severity: normal | | R 4.3.0 brought (once again) a new graphics API which requires a rebuild for | functionality that involves creating graphics device. Once rebuilt the | following will again

Bug#1039953: tikzDevice requires rebuild under R 4.3.*

Package: r-cran-tikzdevice Version: 0.12.4-1 Severity: normal R 4.3.0 brought (once again) a new graphics API which requires a rebuild for functionality that involves creating graphics device. Once rebuilt the following will again work: > getRversion() [1] ‘4.3.1’ >

Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

On 28 June 2023 at 17:39, Jeremy Bícha wrote: | Control: severity -1 serious | | On Wed, Jun 28, 2023 at 5:29 PM Dirk Eddelbuettel wrote: | > Feel free to change the severity back if you truly think it is that serious. | | Done. | | Feel free to close the bug once r-base is ready to migr

Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

On 28 June 2023 at 17:39, Jeremy Bícha wrote: | Control: severity -1 serious | | On Wed, Jun 28, 2023 at 5:29 PM Dirk Eddelbuettel wrote: | > Feel free to change the severity back if you truly think it is that serious. | | Done. | | Feel free to close the bug once r-base is ready to migr

Bug#1039925: ragg requires rebuild under R 4.3.*

Package: r-cran-ragg Version: 1.2.5-1 Severity: normal R 4.3.0 brought (once again) a new graphics API which requires a rebuild for functionality that involves creating graphics device. Once rebuilt the following will again work: > getRversion() [1] ‘4.3.1’ >

Bug#1039926: svglite requires rebuild under R 4.3.*

Package: r-cran-svglite Version: 2.1.1-1 Severity: normal R 4.3.0 brought (once again) a new graphics API which requires a rebuild for functionality that involves creating graphics device. Once rebuilt the following will again work: > getRversion() [1] ‘4.3.1’ >

Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

Feel free to change the severity back if you truly think it is that serious. Some of the autopkgtests may be stumbling about the graphics API change and may need a rebuild of packages interfacing it: svglite, ggplot2, ragg, tikzdevice. As some of these are widely used the rest may be

Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

severity 1039721 normal thanks Hi Jeremy, That is a false positive (more below) and a duplicate of #1039510; the discussion of the latter now continues on the debian-r list. On 28 June 2023 at 12:31, Jeremy Bícha wrote: | Source: r-base | Version: 4.3.1-1 | Severity: serious | | I'm copying

Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

severity 1039721 normal thanks Hi Jeremy, That is a false positive (more below) and a duplicate of #1039510; the discussion of the latter now continues on the debian-r list. On 28 June 2023 at 12:31, Jeremy Bícha wrote: | Source: r-base | Version: 4.3.1-1 | Severity: serious | | I'm copying

Bug#1039645: Seems we need a transition for r-base instead of lots of single bugs against single packages (Was: Bug#1039645: r-cran-epi: autopkgtest failure with r-base (4.3.1-1))

On 28 June 2023 at 14:03, Andreas Tille wrote: | Am Wed, Jun 28, 2023 at 08:11:05AM +0200 schrieb Bas Couwenberg: | > 189s DLL requires the use of native symbols | | I wonder, whether all those bugs against single r-* packages are | sensible. Yes they are. Those are bugs in the packages

Bug#1039645: Seems we need a transition for r-base instead of lots of single bugs against single packages (Was: Bug#1039645: r-cran-epi: autopkgtest failure with r-base (4.3.1-1))

On 28 June 2023 at 14:03, Andreas Tille wrote: | Am Wed, Jun 28, 2023 at 08:11:05AM +0200 schrieb Bas Couwenberg: | > 189s DLL requires the use of native symbols | | I wonder, whether all those bugs against single r-* packages are | sensible. Yes they are. Those are bugs in the packages

Re: [ESS] Working with Roxygen2

nce _forever_. Invoking it adds this header above ##' .. content for \description{} (no empty lines) .. ##' ##' .. content for \details{} .. ##' @title ##' @param x ##' @param y ##' @return ##' @author Dirk Eddelbuettel pyth <- function(x, y) { sq

Re: [Rd] Correct use of tools::R_user_dir() in packages?

On 27 June 2023 at 15:36, Carl Boettiger wrote: | tools::R_user_dir() provides configurable directories for R packages | to write persistent information consistent with standard best | practices relative to each supported operating systems for | applications to store data, config, and cache

Bug#1039105: I can confirm this bug, fix works for me

Hi Thomas, On 27 June 2023 at 22:05, Thomas Lange wrote: | Hi Dirk, | | I'm a vm user for reading my mail. So there's two of us! :-) | Thanks a lot for this bug report and fix. It also works for me. | Patching /etc/emacs/site-start.d/50vm-init.el still compiles vm-vars | and vm-version, but

Bug#1039510: mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or versioned (test) Depends?

Hi Paul, On 27 June 2023 at 20:08, Paul Gevers wrote: | Hi Dirk, | | On 26-06-2023 22:21, Dirk Eddelbuettel wrote: | > I really appreciate the diligence and detail you put into this. | > | > But I would like to offer a simple shortcut. I am also CCing debian-r again | > as this

Bug#1039510: mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or versioned (test) Depends?

Hi Paul, On 27 June 2023 at 20:08, Paul Gevers wrote: | Hi Dirk, | | On 26-06-2023 22:21, Dirk Eddelbuettel wrote: | > I really appreciate the diligence and detail you put into this. | > | > But I would like to offer a simple shortcut. I am also CCing debian-r again | > as this

Bug#1039510: mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or versioned (test) Depends?

Hi Paul, I really appreciate the diligence and detail you put into this. But I would like to offer a simple shortcut. I am also CCing debian-r again as this has come up time and time again, is guaranteed to come up again for as long as combine autopkgtests with letting packages go stake.

Bug#1039510: mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or versioned (test) Depends?

Hi Paul, I really appreciate the diligence and detail you put into this. But I would like to offer a simple shortcut. I am also CCing debian-r again as this has come up time and time again, is guaranteed to come up again for as long as combine autopkgtests with letting packages go stake.

Re: [R-pkg-devel] Questions regarding a new (seperated package) and how to submit them to cran

On 26 June 2023 at 21:03, Uwe Ligges wrote: | On 26.06.2023 02:52, Bernd.Gruber wrote: | > Thanks, just to make sure: | > | > In the policy I find the entry: | > | > Additional_repositories: | | You can use this for CRAN-style repositories. Not for other inds of | storage. In that case you

Re: [Rd] restoring LANGUAGE env variable within an R session

Ben, POSIX level / glibc level variables are set at process start and AGAIK cannot really be altered after start. They clearly work when set _before_ calling sqrt(-1): $ LANGUAGE=es Rscript -e 'sqrt(-1)' [1] NaN Warning message: In sqrt(-1) : Se han producido NaNs $

Bug#1039105: Fails to start with Emacs 28

Package: vm Version: 8.2.0b-8 Severity: normal Ian, After updating my main machine (and the only one running vm along and exim4, dovecot, spamassassin and whatnot) to Ubuntu 23.04 with its Emacs 28.2 (in an upgrade from 22.10 with Emacs 27.*), I found that vm (which I have been using all

Re: [Vm] [Question #707095]: Emacs 28.2 does not start vm 8.2.0b-8

Question #707095 on VM changed: https://answers.launchpad.net/vm/+question/707095 Dirk Eddelbuettel gave more information on the question: Uninstalling and re-installing the package worked. That should of course have been doing the upgrade -- somehow it didn't remake the .elc fine. So still

[Vm] [Question #707095]: Emacs 28.2 does not start vm 8.2.0b-8

New question #707095 on VM: https://answers.launchpad.net/vm/+question/707095 After upgrading from Ubuntu 22.10 to 23.04, I cannot launch `vm`. It results in an error Wrong number of arguments: #, 0 from either the `(require 'vm)` or a simple `M-x vm`. The emacs version is

Re: [R-pkg-devel] Convention or standards for using header library (e.g. Eigen)

On 24 June 2023 at 21:35, Stephen Wade wrote: | Doesnt seem like the system package is worth it. Should the convention | simply be to bundle the headers in the package then? What about package | size - is there some limit to the size of included libraries/headers to | consider for CRAN? Here is

Bug#1037439: Opinions about removal of 32bit architecture for r-cran-rstan (Was: Bug#1037439: r-cran-rstan/armhf FTBFS with r-cran-bh 1.74)

Nilesh, But nobody suggested to turn 32bit builds for R off so it was not a question that needed adressing. Or did I miss something here? We do have _a_ package failing. My first suggestion always is to talk to upstream (and I did so on June 13 in my first post on this bug report). Has

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

Hi Philip, On 21 June 2023 at 20:15, Philip Rinn wrote: | Hi, | | could we please close this bug? We released bookworm some days ago and | propagating to testing should be fine now. [It blocks R packages to propagate to | testing currently.] Thanks for the reminder. I think we had informal

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

Hi Philip, On 21 June 2023 at 20:15, Philip Rinn wrote: | Hi, | | could we please close this bug? We released bookworm some days ago and | propagating to testing should be fine now. [It blocks R packages to propagate to | testing currently.] Thanks for the reminder. I think we had informal

Re: [R-sig-Debian] R 4.3.1 on Debian bullseye-cran40 repository

On 21 June 2023 at 07:48, Iago Giné Vázquez wrote: | Although R 4.3.1 has been released some days ago, and in http://cloud.r-project.org/bin/linux/debian/ it is claimed that | | | Debian bullseye has been released with R 4.0.4. If you want to upgrade to R 4.3.1 on bullseye, you can use the

Re: [R-pkg-devel] Change package name

Hi William, On 20 June 2023 at 16:06, William Becker wrote: | I am the maintainer of a package which is unfortunately involved in a complicated dispute regarding its intellectual property (since the package was partly built under a contract with an organisation), but also the "branding" of

Bug#1037439: r-cran-rstan/armhf FTBFS with r-cran-bh 1.74

On 19 June 2023 at 16:37, Adrian Bunk wrote: | On Tue, Jun 13, 2023 at 03:30:18PM -0500, Dirk Eddelbuettel wrote: | > | > On 13 June 2023 at 13:15, Steve Langasek wrote: | > | Control: reassign -1 r-cran-rstan r-cran-bh | > | Control: found -1 r-cran-rstan/2.21.8-1 | > | | &g

Bug#1037439: r-cran-rstan/armhf FTBFS with r-cran-bh 1.74

On 13 June 2023 at 13:15, Steve Langasek wrote: | Control: reassign -1 r-cran-rstan r-cran-bh | Control: found -1 r-cran-rstan/2.21.8-1 | | Unfortunately, at least in Ubuntu it appears the r-cran-rstan build still | exhausts the 32-bit memory space even with boost 1.81. | |

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

On 13 June 2023 at 00:46, Josh Triplett wrote: | On Mon, Jun 12, 2023 at 05:03:01PM -0500, Dirk Eddelbuettel wrote: | > | > reassign 1037113 screen-message | > thanks | > | > Binary package 'sm' is from source package 'screen-message' | > | > Binary package 'r-cran-sm' i

Bug#1037439: r-cran-rstan/armhf FTBFS with r-cran-bh 1.74, works with boost 1.81

On 12 June 2023 at 16:08, Steve Langasek wrote: | On Mon, Jun 12, 2023 at 05:22:39PM -0500, Dirk Eddelbuettel wrote: | > edd@rob:~$ cat deb/bh/debian/control | > Source: r-cran-bh | > Section: gnu-r | > Priority: optional | > Maintainer: Dirk Eddelbuettel | &g

Bug#1037439: r-cran-rstan/armhf FTBFS with r-cran-bh 1.74, works with boost 1.81

th discussing.) So for the last few years _Debian's_ r-cran-bh was an empty virtual package dependending on what Debian has as libboost* (particularly the headers only): edd@rob:~$ cat deb/bh/debian/control Source: r-cran-bh Section: gnu-r Priority: optional Maintainer: Dirk Eddelbuett

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

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