Hi, On 09-07-2023 16:20, Andreas Tille wrote:
I'm working my through the list and the ppc64el ci workers have a bit of backlog; we're getting somewhere, but I'm think I'm still also seeing different failure modes than the graphics engine, tibble and dplyr.I admit the only chance I personally see to clarify this question is to open an issue at the tibble git repository[1]. May be we also need something like an r-cran-tibble-api?
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]. In unstable r-cran-xopen works. If I take r-cran-ps, r-cran-xopen and r-base from unstable and test in testing, r-cran-xopen works. If I only take r-base and r-cran-ps from unstable and test in testing, r-cran-xopen works. Can somebody with R understanding confirm?
33s Error in `not_null(.Call("psll_connections", p))`: DLL requires the use of native symbols
33s Backtrace: 33s 1. testthat::test_that(...) 33s at test.R:4:033s 2. testthat:::test_code(desc, code, env = parent.frame(), reporter = reporter)
33s 3. reporter$start_test(context = reporter$.context, test = test)
33s 4. testthat:::o_apply(self$reporters, "start_test", context, test)
33s 5. base::lapply(objects, f)
33s 6. testthat (local) FUN(X[[i]], ...)
33s 7. x$start_test(...)
33s 8. ps::ps_connections(ps_handle())
33s 9. ps:::psl_connections(p)
33s 10. ps:::not_null(.Call("psll_connections", p))
Same for r-cran-fnn, which impacts r-cran-uwof [2].
I think what we should do is add a versioned Breaks in r-base on
<packages-involved-in:r-graphics-engine>, r-cran-ps, r-cran-tibble,
r-cran-dplyr, r-cran-fnn. I think that's the right thing to do for
bookworm to trixie upgrades (and current trixie to trixie with the new
r-base). Has anyone see other packages throwing that "DLL requires the
use of native symbols" error? I spotted the ones below [3, 4, 5, 6], but
I haven't identified which package brings in the issue. I first thought
it would be from the package itself, but for some (r-cran-spacetime and
r-cran-stars) their versions in unstable fail their own testsuite in
testing. Would it hint at the same problem for the packages, or just for
their tests? I suspect the former, then they should also need to be
added to the Breaks list.
Paul[1] https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-xopen/35575366/log.gz [2] https://ci.debian.net/data/autopkgtest/testing/i386/r/r-cran-uwot/35590669/log.gz [3] https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-intervals/35575046/log.gz [4] https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-maldiquant/35575320/log.gz [5] https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-spacetime/35575371/log.gz [6] https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-stars/35583884/log.gz
OpenPGP_signature
Description: OpenPGP digital signature
