Re: Test suite issues due to new upstream version of r-core in unstable (Was: r-cran-shiny: broken symlink: ...)
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 do, as this case perfectly fits the problem.
Seems to be an appropriate solution - given we should stick to smallest
changes in packaging if possible.
> It's be same effort in both cases (one upload + filing a bug with release team).
Since I will not manage to do so in the next 16 hours I'd be happy if
someone might beat me in doing so. Otherwise I can catch up tomorrow.
Thanks a lot for your hint
Andreas.
> > Let me know what you think.
>
> > > [1] https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-thematic/33619891/log.gz
> > > [2] https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-treescape/33619892/log.gz
> > > [3] https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-treespace/33619893/log.gz
> > > [4] https://tracker.debian.org/news/1429562/accepted-r-base-430-1-source-into-unstable/
> > [5] https://wiki.debian.org/TestingProposedUpdates
>
> --
> Best,
> Nilesh
--
http://fam-tille.de
Reply to: