Re: R 4.4.0 coming April 24

2024-04-21 Thread Dirk Eddelbuettel
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

2024-04-21 Thread Dirk Eddelbuettel
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

2024-04-18 Thread Dirk Eddelbuettel
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

2024-04-17 Thread Dirk Eddelbuettel
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: CRAN Package Matrix update and a possible transition or not

2024-03-23 Thread Dirk Eddelbuettel
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

2024-03-23 Thread Dirk Eddelbuettel
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

2024-03-22 Thread Dirk Eddelbuettel
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

CRAN Package Matrix update and a possible transition or not

2024-02-27 Thread Dirk Eddelbuettel
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_

Bug#1054657: Transition seems to be blocked (Was: Bug#1054657: transition: r-bioc-biocgenerics)

2023-12-08 Thread Dirk Eddelbuettel
On 9 December 2023 at 01:06, Charles Plessy wrote: | I do not know for r-bioc-netsam, but for r-bioc-org.hs.eg.db and similar | packages, it is because it is an "annotation package" made of data and | therefore not managed the same way as the other Bioconductor packages. | | This is why it

Re: Matrix update triggering need for four rebuilds

2023-11-17 Thread Dirk Eddelbuettel
On 17 November 2023 at 23:50, Nilesh Patra wrote: | | | On 17 November 2023 11:34:21 pm IST, Dirk Eddelbuettel wrote: | > | >On 17 November 2023 at 18:43, Andreas Tille wrote: | >| Am Fri, Nov 17, 2023 at 10:12:02AM -0600 schrieb Dirk Eddelbuettel: | >| > Leaving | >| &

Re: Matrix update triggering need for four rebuilds

2023-11-17 Thread Dirk Eddelbuettel
On 17 November 2023 at 18:43, Andreas Tille wrote: | Am Fri, Nov 17, 2023 at 10:12:02AM -0600 schrieb Dirk Eddelbuettel: | > Leaving | > | >r-cran-irlba | >r-cran-openmx | > | > for you (unless you got to it already). | | To make it pretty clear: I will

Re: Matrix update triggering need for four rebuilds

2023-11-17 Thread Dirk Eddelbuettel
On 15 November 2023 at 05:23, Dirk Eddelbuettel wrote: | | On 15 November 2023 at 07:00, Andreas Tille wrote: | | Am Tue, Nov 14, 2023 at 04:49:01PM -0600 schrieb Dirk Eddelbuettel: | | > | | > On 14 November 2023 at 16:17, Dirk Eddelbuettel wrote: | | > | | | > | On 14 November 2

Re: Matrix update triggering need for four rebuilds

2023-11-15 Thread Dirk Eddelbuettel
On 15 November 2023 at 07:00, Andreas Tille wrote: | Am Tue, Nov 14, 2023 at 04:49:01PM -0600 schrieb Dirk Eddelbuettel: | > | > On 14 November 2023 at 16:17, Dirk Eddelbuettel wrote: | > | | > | On 14 November 2023 at 11:06, Andreas Tille wrote: | > | | Am Mon, Nov 13, 202

Re: Matrix update triggering need for four rebuilds

2023-11-14 Thread Dirk Eddelbuettel
On 14 November 2023 at 16:17, Dirk Eddelbuettel wrote: | | On 14 November 2023 at 11:06, Andreas Tille wrote: | | Am Mon, Nov 13, 2023 at 07:23:06AM -0600 schrieb Dirk Eddelbuettel: | | > Most of these are not in Debian but I think we need binary rebuilds of | | > | | >

Re: Matrix update triggering need for four rebuilds

2023-11-14 Thread Dirk Eddelbuettel
On 14 November 2023 at 11:06, Andreas Tille wrote: | Am Mon, Nov 13, 2023 at 07:23:06AM -0600 schrieb Dirk Eddelbuettel: | > Most of these are not in Debian but I think we need binary rebuilds of | > | >irlbabecause of headers | >OpenMx becaus

Bug#1054657: transition: r-bioc-biocgenerics

2023-11-07 Thread Dirk Eddelbuettel
On 7 November 2023 at 14:58, Andreas Tille wrote: | Do you see any way to answer the question that is discussed in this | thread by r2u how to know whether new Bioconductor packages might have | new dependencies not yet packaged for Debian? "Kinda. Sorta. Not fully." I have written related code

Bug#1054657: transition: r-bioc-biocgenerics

2023-11-07 Thread Dirk Eddelbuettel
On 7 November 2023 at 22:01, Charles Plessy wrote: | One possible direction would be to leverage the work done by Dirk and | others in r2u, where the Bioc transition is over, and for each package | in Debian, look if the r2u equivalent has a dependency not in Debian. | |

Bug#1054657: transition: r-bioc-biocgenerics

2023-10-27 Thread Dirk Eddelbuettel
On 27 October 2023 at 16:43, Andreas Tille wrote: | Am Fri, Oct 27, 2023 at 09:19:22AM -0500 schrieb Dirk Eddelbuettel: | > | > | BioConductor has just released version 3.17. Since the next r-base | > | > Typo: 3.18 | | Yes. Thanks for pointing this out. | | > | release is

Bug#1054657: transition: r-bioc-biocgenerics

2023-10-27 Thread Dirk Eddelbuettel
On 27 October 2023 at 16:00, Andreas Tille wrote: | Package: release.debian.org | Severity: normal | User: release.debian@packages.debian.org | Usertags: transition | X-Debbugs-Cc: r-bioc-biocgener...@packages.debian.org, debia...@lists.debian.org | Control: affects -1 +

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

2023-07-13 Thread Dirk Eddelbuettel
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)

2023-07-13 Thread Dirk Eddelbuettel
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)

2023-07-12 Thread Dirk Eddelbuettel
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)

2023-07-12 Thread Dirk Eddelbuettel
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)

2023-07-10 Thread Dirk Eddelbuettel
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)

2023-07-10 Thread Dirk Eddelbuettel
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)

2023-07-09 Thread Dirk Eddelbuettel
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)

2023-07-09 Thread Dirk Eddelbuettel
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)

2023-07-09 Thread Dirk Eddelbuettel
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: Seeking advise how to proceed with the transition / move R stack to testing (Was: Bug#1040001: transition: r-base)

2023-07-06 Thread Dirk Eddelbuettel
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: transition: r-base

2023-07-05 Thread Dirk Eddelbuettel
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

2023-07-01 Thread Dirk Eddelbuettel
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

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

2023-05-16 Thread Dirk Eddelbuettel
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: ...)

2023-05-16 Thread Dirk Eddelbuettel
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: ...)

2023-05-16 Thread Dirk Eddelbuettel
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: ...)

2023-05-16 Thread Dirk Eddelbuettel
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#1023731: BioC Transition blocked by new dependencies

2022-11-21 Thread Dirk Eddelbuettel
On 21 November 2022 at 16:39, Andreas Tille wrote: | Am Mon, Nov 21, 2022 at 03:05:26PM +0100 schrieb Sebastian Ramacher: | > On 2022-11-21 15:02:16 +0100, Andreas Tille wrote: | > > Some of the BioConductor packages need new dependencies. | > > I have pushed these to new queue and set the ITP

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-12-08 Thread Dirk Eddelbuettel
On 8 December 2021 at 12:16, Sebastian Ramacher wrote: | gsl now migrated and libgsl25 got removed from testing. Fantastic! Thanks to you and to Patrick (CC'ed again) and we're back to where we once were (GSL updates upstream, I can update without fuss or formal transitions) but now we are

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-12-06 Thread Dirk Eddelbuettel
Hi Mattia and Sebastian, On 6 December 2021 at 22:44, Mattia Rizzolo wrote: | Yes! See https://wiki.debian.org/BuildProfileSpec for the | documentation. | | Unfortunately there have been a few troubles getting a formal and good | specifical text that was "good enough" for the Debian Policy.

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-12-06 Thread Dirk Eddelbuettel
Hi Sebastian, On 6 December 2021 at 21:58, Sebastian Ramacher wrote: | gsl needs another upload. It currently lists libgsl-prof as package that | should be built, but it isn't. I've been told that in the past this has | been worked around by manually changing the .dsc before uploading. It has

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-12-02 Thread Dirk Eddelbuettel
On 2 December 2021 at 15:57, Dirk Eddelbuettel wrote: | Yep. It's in the queue by now. I sometimes forget if an experimental -> | unstable passage does or does not need an orig.tar.gz to go along or not but | the bots will tell me if so :) And by now in unstable. Thanks so much for look

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-12-02 Thread Dirk Eddelbuettel
On 2 December 2021 at 22:39, Sebastian Ramacher wrote: | On 2021-12-02 15:11:20, Dirk Eddelbuettel wrote: | > | > On 2 December 2021 at 20:55, Sebastian Ramacher wrote: | > | gsl cleared NEW thanks to ta. So this should be good to go. | > | | > | Please go ahead with the upl

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-12-02 Thread Dirk Eddelbuettel
On 2 December 2021 at 20:55, Sebastian Ramacher wrote: | gsl cleared NEW thanks to ta. So this should be good to go. | | Please go ahead with the upload to unstable. Will do. Without any other requirements, correct? I.e. standard upload which thanks to Patrick's work will be around a new

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-12-02 Thread Dirk Eddelbuettel
On 1 December 2021 at 21:47, Patrick Alken wrote: | Ok please send along the patches. Sure thing. They are actually 'in the open' as we (== Debian devs) these days have most / all work in git(-lab via our instance at salsa.debian.org). See this directory and note that the 'series' file governs

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-12-01 Thread Dirk Eddelbuettel
On 1 December 2021 at 21:41, Sebastian Ramacher wrote: | Indeed, it will need a trip through NEW. So going via experimental would | be appreciated. But, once it passed NEW, you can then immediatly follow | up with the upload to unstable. I will take care of the binNMUs of the | reverse

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-12-01 Thread Dirk Eddelbuettel
On 1 December 2021 at 09:45, Sebastian Ramacher wrote: | On 2021-11-30 22:43:11 -0700, Patrick Alken wrote: | > All, I have uploaded a new GSL release (2.7.1) which I hope fixes the | > libtool version numbers Patrick, Big big thank you! (And I missed this email yesterday) | Thank you! | |

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-11-23 Thread Dirk Eddelbuettel
On 22 November 2021 at 09:08, Patrick Alken wrote: | Hi all, sorry for all this trouble. I will try to make a new GSL release | with the correct numbers. Much appreciate it! Sebastian, we'll then run a new transition with gsl 2.8 (or whichever version number it will be) and its new somajor.

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-11-21 Thread Dirk Eddelbuettel
Hi Patrick, Can you please chime in (as you did in the earlier exchanges when Sebastian explained to us how to set valus triplet for libtool via configure.ac) ? On 21 November 2021 at 23:00, Sebastian Ramacher wrote: | On 2021-11-09 12:54:44 -0600, Dirk Eddelbuettel wrote: | > | >

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-11-09 Thread Dirk Eddelbuettel
On 8 November 2021 at 22:14, Sebastian Ramacher wrote: | Control: tags -1 moreinfo | Control: forwarded -1 https://release.debian.org/transitions/html/auto-gsl.html | | On 2021-10-31 14:29:40 -0500, Dirk Eddelbuettel wrote: | > | > Package: release.debian.org | > Severity: normal

Bug#998192: release.debian.org: Transition for gsl-2.7 / libgsl26

2021-10-31 Thread Dirk Eddelbuettel
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition GNU GSL 2.7 was release a few months ago, and we now realised (in the discussion of #993324 which also included upstream) that the upstream libtool instruction were in error by _not_

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-10-31 Thread Dirk Eddelbuettel
On 31 October 2020 at 18:46, Sebastian Ramacher wrote: | On 2020-05-28 11:58:09 -0500, Dirk Eddelbuettel wrote: | > | > Thanks everybody for the help with the transition: 4.0.0-3 is now in testing. | | So let's close this one. Indeed. Thanks for catching that! Dirk |

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-05-29 Thread Dirk Eddelbuettel
On 29 May 2020 at 07:51, Dylan Aïssi wrote: | Hi, | | Le jeu. 28 mai 2020 à 18:58, Dirk Eddelbuettel a écrit : | > | > Thanks everybody for the help with the transition: 4.0.0-3 is now in testing. | > | | \o/ | | Both transition trackers (r-api-4.0 and r-api-bioc-3.11) were

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-05-28 Thread Dirk Eddelbuettel
Thanks everybody for the help with the transition: 4.0.0-3 is now in testing. Which is lovely as upstream is already at work with 4.0.1 which will drop on June 6 [1]. I'll likely make an rc upload. Special thanks to Graham for calmly pulling a few strings here and there. Cheers, Dirk [1]

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-05-26 Thread Dirk Eddelbuettel
On 25 May 2020 at 09:32, Graham Inggs wrote: | Hi All | | Thanks everyone for doing all the hundreds of uploads that were needed | for this combined transition. | All rebuilds for r-api-bioc3.11 are done [1] and there's one | outstanding FTBFS on a release architecture for r-api-4.0 [2]. The

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-05-14 Thread Dirk Eddelbuettel
On 4 April 2020 at 13:40, Dirk Eddelbuettel wrote: | | On 4 April 2020 at 10:15, Sebastiaan Couwenberg wrote: | | On 4/3/20 8:27 PM, Dirk Eddelbuettel wrote: | | > Can the tracker sort by | | > - maintainer | | > - binary type | | > to help ? | | | | With the attached script yo

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-05-13 Thread Dirk Eddelbuettel
On 13 May 2020 at 10:15, Graham Inggs wrote: | Control: tags -1 + confirmed | | Hi Dirk | | On Fri, 1 May 2020 at 14:51, Dirk Eddelbuettel wrote: | > Please schedule a transition for r-base. | > | > I will then upload 4.0.0-3 to unstable as soon as I get your green light. | | Please

Bug#959133: release.debian.org: Transition for gsl

2020-05-04 Thread Dirk Eddelbuettel
On 4 May 2020 at 09:27, Graham Inggs wrote: | Control: tags -1 + confirmed | | Hi Dirk | | On Wed, 29 Apr 2020 at 21:33, Dirk Eddelbuettel wrote: | > GNU GSL 2.6 was release last fall; the package is stable and does not move | > too much upstream. It has been in 'auto transition' for a

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-05-01 Thread Dirk Eddelbuettel
On 29 April 2020 at 13:23, Dirk Eddelbuettel wrote: | R 4.0.0 was released as scheduled on Friday, source packages have been in | experimental since Friday too. | | There is one build failure on ppc64el but we now know what causes it so a bug | fix from upstream should be forthcoming shortly

Bug#959133: release.debian.org: Transition for gsl

2020-04-29 Thread Dirk Eddelbuettel
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition GNU GSL 2.6 was release last fall; the package is stable and does not move too much upstream. It has been in 'auto transition' for a while following my initial upload to experimental.

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-04-29 Thread Dirk Eddelbuettel
All, R 4.0.0 was released as scheduled on Friday, source packages have been in experimental since Friday too. There is one build failure on ppc64el but we now know what causes it so a bug fix from upstream should be forthcoming shortly. The bug can also be circumvented by (on that platform

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-04-04 Thread Dirk Eddelbuettel
On 4 April 2020 at 10:15, Sebastiaan Couwenberg wrote: | On 4/3/20 8:27 PM, Dirk Eddelbuettel wrote: | > Can the tracker sort by | > - maintainer | > - binary type | > to help ? | | With the attached script you can create a dd-list from the tracker. | | transition-dd-list.p

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-04-03 Thread Dirk Eddelbuettel
Hi Graham, On 3 April 2020 at 21:32, Graham Inggs wrote: | Hi Dirk | | On Fri, 3 Apr 2020 at 20:27, Dirk Eddelbuettel wrote: | > I am still (as always) lost by the process. Does that mean an upload to | > unstable is now ok? Or not? I am unsure what "hand shake" from the f

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-04-03 Thread Dirk Eddelbuettel
Hi Graham, On 3 April 2020 at 20:07, Graham Inggs wrote: | Hi Dirk | | On Sat, 28 Mar 2020 at 15:57, Dirk Eddelbuettel wrote: | > R does change internals every now and then with the annual releases; this is | > a major one which will require rebuilds of all packages. | | I've

Bug#955211: release.debian.org: Transition r-base for 4.0.0

2020-03-28 Thread Dirk Eddelbuettel
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: debia...@lists.debian.org R 4.0.0 will be released on April 24. The upstream team always follows a well-publicised scheduled which started yesterday with the first

Bug#920804: release.debian.org: security upload for r-cran-readxl

2019-01-30 Thread Dirk Eddelbuettel
On 30 January 2019 at 13:59, Adam D. Barratt wrote: | On 2019-01-30 13:39, Dirk Eddelbuettel wrote: | > On 30 January 2019 at 13:11, Adam D. Barratt wrote: | > | On 2019-01-29 11:53, Dirk Eddelbuettel wrote: | > ... | > | > Happy to upload once you give a green light. (Sys

Bug#920804: release.debian.org: security upload for r-cran-readxl

2019-01-30 Thread Dirk Eddelbuettel
On 30 January 2019 at 13:11, Adam D. Barratt wrote: | On 2019-01-29 11:53, Dirk Eddelbuettel wrote: | > This is a follow-up to the discussion in #919324 and subsequent emails | > with | > Moritz and Salvatore. The two CVEs are genuine and fixed, the issue | > however | > is

Bug#920804: release.debian.org: security upload for r-cran-readxl

2019-01-29 Thread Dirk Eddelbuettel
: #919324) + * libxls/xlstool.h: Idem + * ole.c: Idem + * xls.c: Idem + * xlstool.c: Idem + + * This addresses +CVE-2018-20450 +CVE-2018-20452 +with corresponding upstream patch in libxls and readxl + + -- Dirk Eddelbuettel Sun, 27 Jan 2019 09:29:50 -0600 + r-cran-readxl (0.1.1-1

Bug#896667: It is safe to assume that source only uploads will build against the r-api-3.5? (Was: Bug#896667: transition: r-base-3.5)

2018-06-02 Thread Dirk Eddelbuettel
On 1 June 2018 at 18:35, Graham Inggs wrote: | On 01/06/2018 17:19, Dirk Eddelbuettel wrote: | > This is now taken care of: dbi_1.0.0-2 was just uploaded | | Thanks Dirk! | | Another weirdness I have come across in Ubuntu today is rebuilds of | r-cran-expm and r-cran-mlmrev f

Bug#896667: It is safe to assume that source only uploads will build against the r-api-3.5? (Was: Bug#896667: transition: r-base-3.5)

2018-06-01 Thread Dirk Eddelbuettel
On 1 June 2018 at 06:32, Dirk Eddelbuettel wrote: | | On 1 June 2018 at 12:41, Graham Inggs wrote: | | A warning: src:dbi has a hard-coded dependency on r-api-3.4 in | | debian/control, and src:wkward has the same in debian/rules. | | That was from when dh-r was borked and could not cope

Bug#896667: It is safe to assume that source only uploads will build against the r-api-3.5? (Was: Bug#896667: transition: r-base-3.5)

2018-06-01 Thread Dirk Eddelbuettel
On 1 June 2018 at 13:37, Emilio Pozuelo Monfort wrote: | On 01/06/18 13:32, Dirk Eddelbuettel wrote: | > | > On 1 June 2018 at 11:54, Emilio Pozuelo Monfort wrote: | > | Scheduled for cluster foreign rmpi nlme rmatrix robustbase lmtest survival lme4 | > | tseries. | > | >

Bug#896667: It is safe to assume that source only uploads will build against the r-api-3.5? (Was: Bug#896667: transition: r-base-3.5)

2018-06-01 Thread Dirk Eddelbuettel
On 1 June 2018 at 12:41, Graham Inggs wrote: | A warning: src:dbi has a hard-coded dependency on r-api-3.4 in | debian/control, and src:wkward has the same in debian/rules. That was from when dh-r was borked and could not cope with srcname != pkgname. I can look into fixing it this morning

Bug#896667: It is safe to assume that source only uploads will build against the r-api-3.5? (Was: Bug#896667: transition: r-base-3.5)

2018-06-01 Thread Dirk Eddelbuettel
On 1 June 2018 at 11:54, Emilio Pozuelo Monfort wrote: | Scheduled for cluster foreign rmpi nlme rmatrix robustbase lmtest survival lme4 | tseries. Why is that needed? Aren't ALL binary packages auto-rebuilt? Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#896667: transition: r-base-3.5

2018-05-31 Thread Dirk Eddelbuettel
On 31 May 2018 at 16:17, Emilio Pozuelo Monfort wrote: | > (Out of nerdy curiousity because we sometimes drive rebuilds of [generally | > much smaller] subsets, where is the code that "walks" the dependency graph? | > Is that in libapt by chance [as I happen to have a package getting from R to |

Bug#896667: transition: r-base-3.5

2018-05-31 Thread Dirk Eddelbuettel
On 31 May 2018 at 16:15, Emilio Pozuelo Monfort wrote: | Hi, | | On 31/05/18 15:45, Emilio Pozuelo Monfort wrote: | > On 31/05/18 15:09, Dirk Eddelbuettel wrote: | >> | >> Emilio, Seb, | >> | >> Can you confirm that now that we have | >> a) "green light&q

Bug#896667: transition: r-base-3.5

2018-05-31 Thread Dirk Eddelbuettel
On 31 May 2018 at 15:45, Emilio Pozuelo Monfort wrote: | On 31/05/18 15:09, Dirk Eddelbuettel wrote: | > | > Emilio, Seb, | > | > Can you confirm that now that we have | > a) "green light" on the transition, and | > b) the r-base package is in unstable |

Bug#896667: transition: r-base-3.5

2018-05-31 Thread Dirk Eddelbuettel
Emilio, Seb, Can you confirm that now that we have a) "green light" on the transition, and b) the r-base package is in unstable we should see binary: any packages being rebuilt -- which I do not yet see. When will this start? On 31 May 2018 at 05:37, Dirk Eddelbuettel wrote: | |

Bug#896667: transition: r-base-3.5

2018-05-31 Thread Dirk Eddelbuettel
On 31 May 2018 at 09:25, Emilio Pozuelo Monfort wrote: | On 31/05/18 00:13, Dirk Eddelbuettel wrote: | > | > On 30 May 2018 at 23:40, Emilio Pozuelo Monfort wrote: | > | curl migrated to testing today. Please go ahead with R 3.5. | > | > Yay!! Thank you -- and r-base_3.5.0-3 is

Bug#896667: transition: r-base-3.5

2018-05-30 Thread Dirk Eddelbuettel
On 30 May 2018 at 23:40, Emilio Pozuelo Monfort wrote: | Control: tags -1 confirmed | | On 28/05/18 15:00, Emilio Pozuelo Monfort wrote: | > On 28/05/18 14:32, Dirk Eddelbuettel wrote: | >> | >> On 28 May 2018 at 14:08, Emilio Pozuelo Monfort wrote: | >> | Control

Bug#896667: transition: r-base-3.5

2018-05-28 Thread Dirk Eddelbuettel
al. | >> | >> Due to changes in R internals, all R extension packages must be recompiled, | >> that is 573 packages (of which 260 are arch:all, and will therefore need | >> sourceful uploads). | >> | >> The transition will be managed jointly by Dirk Eddelbuettel

Re: [BUMP] r-cran-readstata13 had five weeks in NEW queue for two uploads

2017-10-14 Thread Dirk Eddelbuettel
On 14 October 2017 at 22:00, Adam D. Barratt wrote: | On Sat, 2017-10-14 at 12:59 -0500, Dirk Eddelbuettel wrote: | > Bumping this as my mail to ftpmaster went unanswered. | > | > Could someone please remind me who to ask about the NEW Queue?  It is | > causing | > me a

Re: [BUMP] r-cran-readstata13 had five weeks in NEW queue for two uploads

2017-10-14 Thread Dirk Eddelbuettel
On 14 October 2017 at 21:59, Chris Lamb wrote: | Dirk Eddelbuettel wrote: | | > The passive-aggressive "we won't work on your package, and won't tell you | > why" is a wee bit annoying. | | This is an uncharitable interpretation of the situation. There is no | delib

[BUMP] r-cran-readstata13 had five weeks in NEW queue for two uploads

2017-10-14 Thread Dirk Eddelbuettel
at 06:39, Dirk Eddelbuettel wrote: | | Hi guys, | | Package r-cran-readstata13 is now a required build-dependency of another | package we had in Debian for a decade. So I prepared r-cran-readstata13 five | weeks ago, and followed up with a revision a week ago (adding README.source). | | Could

Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Dirk Eddelbuettel
On 12 October 2017 at 22:32, Johannes Ranke wrote: | Am Donnerstag, 12. Oktober 2017, 12:01:14 CEST schrieb Dirk Eddelbuettel: | | > So we did this 71 times, but stopped 4+ years ago. Not sure what got the | > toolchain coughing, but I guess we could try again. | | texi2dvi used to tri

Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Dirk Eddelbuettel
On 12 October 2017 at 17:45, Graham Inggs wrote: | Hi Dirk | | On 12/10/2017 16:37, Dirk Eddelbuettel wrote: | > And yes, the hint re 3.5 being shaky leads itself to uploading to experimental. | | Would you please consider versioning such uploads as 3.5~something | instead of 3.4.someth

Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Dirk Eddelbuettel
On 12 October 2017 at 16:18, Sébastien Villemot wrote: | On Thu, Oct 12, 2017 at 09:13:54AM -0500, Dirk Eddelbuettel wrote: | > | > On 12 October 2017 at 15:58, Sébastien Villemot wrote: | > | Thanks Charles for explaining this. | > | | > | Actually the migration has already h

Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Dirk Eddelbuettel
On 12 October 2017 at 15:58, Sébastien Villemot wrote: | Thanks Charles for explaining this. | | Actually the migration has already happened, thanks to the Release Team that | took appropriate action to mitigate the impact of the most recent uploads. | | This will soon be reflected in the

Re: Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Dirk Eddelbuettel
On 12 October 2017 at 14:38, Gianfranco Costamagna wrote: | Hello, | | >s/you/Seb/ to make it correct. Not my transition at all. | | who-uploads r-base | Uploads for r-base: | 3.4.2-1 to unstable: Dirk Eddelbuettel <e...@debian.org> | 3.4.1.20170921-1 to unstable: Dirk Eddelb

Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Dirk Eddelbuettel
On 12 October 2017 at 14:26, Andreas Tille wrote: | On Thu, Oct 12, 2017 at 07:06:33AM -0500, Dirk Eddelbuettel wrote: | > | > On 12 October 2017 at 11:36, Andreas Tille wrote: | > | yesterday you uploaded | > | | > | r-cran-rcpparmadillo 0.8.100.1.0-1 | > | | &

Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Dirk Eddelbuettel
transition at all. Dirk | it would be helpful if you would not upload r-* packages as long as the | testing migration has not happened. | | Thank you | | Andreas. | | On Sat, Sep 23, 2017 at 11:58:20AM -0500, Dirk Eddelbuettel wrote: | > | > See below for upcoming R 3.4.2 "pre-rele

Bug#868558: transition: r-api-3.4 [was Re: Bug#868558: nmu: multiple r-* packages]

2017-09-29 Thread Dirk Eddelbuettel
On 29 September 2017 at 16:23, Andreas Tille wrote: | On Fri, Sep 29, 2017 at 09:11:41AM -0500, Dirk Eddelbuettel wrote: | > | > | rebuild against r-api-3.4 to upload r-cran-dplyr. | > | > It so happens that I (as upstream) got Rcpp 0.12.13 onto CRAN yesterday too, | > so I owe

Bug#868558: transition: r-api-3.4 [was Re: Bug#868558: nmu: multiple r-* packages]

2017-09-29 Thread Dirk Eddelbuettel
On 29 September 2017 at 15:24, Andreas Tille wrote: | On Fri, Sep 29, 2017 at 02:37:19PM +0200, Andreas Tille wrote: | > On Fri, Sep 29, 2017 at 05:59:54AM -0500, Dirk Eddelbuettel wrote: | > > | > > dplyr just had a new upstream CRAN release 0.7.4 yesterday. Don't know about |

Bug#868558: transition: r-api-3.4 [was Re: Bug#868558: nmu: multiple r-* packages]

2017-09-29 Thread Dirk Eddelbuettel
On 29 September 2017 at 15:11, Graham Inggs wrote: | On 29 September 2017 at 12:59, Dirk Eddelbuettel <e...@debian.org> wrote: | > On 29 September 2017 at 07:36, Graham Inggs wrote: | > | rgtk2 and rggobi now FTBFS on s390x, they also fail in a Buster chroot | > | on zelenka.debian

Bug#868558: transition: r-api-3.4 [was Re: Bug#868558: nmu: multiple r-* packages]

2017-09-29 Thread Dirk Eddelbuettel
On 29 September 2017 at 07:36, Graham Inggs wrote: | I've been working on this transition in Ubuntu and here are some of my notes: | | rgtk2 and rggobi now FTBFS on s390x, they also fail in a Buster chroot | on zelenka.debian.org so I don't believe it is a regression in R, but | the binaries

Bug#868558: transition: r-api-3.4 [was Re: Bug#868558: nmu: multiple r-* packages]

2017-09-28 Thread Dirk Eddelbuettel
On 28 September 2017 at 22:22, Andreas Tille wrote: | I wonder if we could teach dh-r to make sure that is added to arch:all | packages. I'm converting all packages I'm touching to dh-r anyway. | | At least a lintian warning might help. | | Kind regards | | Andreas (after having

Bug#868558: transition: r-api-3.4 [was Re: Bug#868558: nmu: multiple r-* packages]

2017-09-28 Thread Dirk Eddelbuettel
On 28 September 2017 at 18:53, Sébastien Villemot wrote: | On Thu, Sep 28, 2017 at 07:04:51AM -0500, Dirk Eddelbuettel wrote: | > | > On 28 September 2017 at 13:20, Sébastien Villemot wrote: | > | On Thu, Sep 28, 2017 at 12:53:10PM +0200, Graham Inggs wrote: | > | > On 2

Bug#868558: transition: r-api-3.4 [was Re: Bug#868558: nmu: multiple r-* packages]

2017-09-28 Thread Dirk Eddelbuettel
On 28 September 2017 at 13:20, Sébastien Villemot wrote: | On Thu, Sep 28, 2017 at 12:53:10PM +0200, Graham Inggs wrote: | > On 28/09/2017 12:28, Sébastien Villemot wrote: | > > Note that there are many arch:all R packages that will need sourceful upload | > > (they are easy to identify on the

Bug#868558: transition: r-api-3.4 [was Re: Bug#868558: nmu: multiple r-* packages]

2017-09-24 Thread Dirk Eddelbuettel
On 24 September 2017 at 15:36, Sébastien Villemot wrote: | Control: reopen -1 | Control: retitle -1 transition: r-api-3.4 | Control: user release.debian@packages.debian.org | Control: usertags -1 = transition | | On Sun, Sep 10, 2017 at 04:15:00PM +, Niels Thykier wrote: | | > To be

Re: Bug#868558: nmu: multiple r-* packages

2017-09-11 Thread Dirk Eddelbuettel
On 11 September 2017 at 18:00, Andreas Tille wrote: | On Mon, Sep 11, 2017 at 08:55:58AM -0500, Dirk Eddelbuettel wrote: | > | > On 11 September 2017 at 15:36, Andreas Tille wrote: | > | IMHO the best way to deal with this would have been by doing a mass bug | > | filing against th

Re: Bug#868558: nmu: multiple r-* packages

2017-09-11 Thread Dirk Eddelbuettel
On 11 September 2017 at 15:36, Andreas Tille wrote: | IMHO the best way to deal with this would have been by doing a mass bug | filing against those packages which were in need of an upgrade. This | would have attracted the attention of the according maintainers directly | and would have led to

Re: Bug#868558: nmu: multiple r-* packages

2017-09-10 Thread Dirk Eddelbuettel
On 10 September 2017 at 16:15, Niels Thykier wrote: | To be perfectly, honest, I would prefer if you did a proper ABI-like | transition over the Breaks. At this scale, Breaks seems too fragile and | too likely for people to get wrong. I *am* -- all packages (currently) get have r-api-3:

Re: Bug#868558: nmu: multiple r-* packages

2017-09-10 Thread Dirk Eddelbuettel
On 10 September 2017 at 11:20, Emilio Pozuelo Monfort wrote: | On 09/09/17 13:48, Dirk Eddelbuettel wrote: | > | > On 9 September 2017 at 06:44, Niels Thykier wrote: | > | Thanks to Sébastien and Andreas for explaining the issue. | > | > Well, was it "explained" ? They

  1   2   3   >