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

2023-05-17 Thread Andreas Tille
Am Wed, May 17, 2023 at 02:07:22PM +0530 schrieb Nilesh Patra: > On Wed, May 17, 2023 at 08:58:58AM +0200, Andreas Tille wrote: > > I hope I was following developers reference about t-p-u[6] correctly > > and pushed > > I've choosen the version 1.7.4+dfsg-3~deb12u1 to match > > the requirement

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

2023-05-17 Thread Nilesh Patra
On Wed, May 17, 2023 at 08:58:58AM +0200, Andreas Tille wrote: > Am Tue, May 16, 2023 at 07:49:55PM +0530 schrieb Nilesh Patra: > > 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

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

2023-05-17 Thread Andreas Tille
Hi again, Am Tue, May 16, 2023 at 07:49:55PM +0530 schrieb Nilesh Patra: > 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

Bug#1035428: 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

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

2023-05-16 Thread Nilesh Patra
On Tue, May 16, 2023 at 09:31:20AM -0500, Dirk Eddelbuettel wrote: > > 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

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

2023-05-16 Thread Andreas Tille
Am Tue, May 16, 2023 at 07:49:55PM +0530 schrieb Nilesh Patra: > 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

Bug#1035428: 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

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

2023-05-16 Thread Nilesh Patra
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 perfectly fits the problem. It's be same effort in both

Bug#1035428: 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:25, Nilesh Patra wrote: | On Tue, May 16, 2023 at 03:01:10PM +0200, Andreas Tille wrote: | > when fixing bug #1035428 I realised test suite issues with | > | > r-cran-thematic [1] | >-> Error in `svglite_(filename, bg, width, height, pointsize, standalone, | >

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

2023-05-16 Thread Nilesh Patra
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 those affected packages. No, don't do that as they indicate a new r-base being pulled as one of the dependencies (which

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

2023-05-16 Thread Nilesh Patra
Hi On Tue, May 16, 2023 at 03:01:10PM +0200, Andreas Tille wrote: > 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: ...)

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#1035428: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)

2023-05-16 Thread Andreas Tille
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 r-cran-treescape [2] r-cran-treespace [3] -> error is given if lambda is