[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 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 Wed, Jun 28, 2023 at 05:07:14PM +0200, Sébastien Villemot wrote:
> The question to answer to determine whether a transition is needed is
> the following: are CRAN packages compiled against R 4.2 binary-
> compatible with R 4.3? Or do they need a rebuild to work with 4.3?

Looking at the NEWS section of R release here[1] gives me the impression
that a bunch of things have changed between 4.2->4.3 so most definitely,
a few CRAN packages need recompilation. To pick out one instance of it,
the doc says:

| GRAPHICS:
| • The graphics engine version, R_GE_version, has been bumped to 16 and so packages
| that provide graphics devices should be reinstalled.

This is a good indication that packages in debian that use graphics API
(like cairo or ggplot) which are compiled against 4.2 would not work
with the new 4.3, which is also confirmed from the autopkgtest failures
for the same.

> If a rebuild is needed, then this means that we have to go through a
> proper transition (involving the Release Team).

I agree that doing binNMU for arch:any packages that need re-building
makes sense. However, in a few cases these packages also have a new
upstream release, which is compatible with a new r-base release.
Hence, we have to go ahead and update then anyway.

That said, I don't have a clear answer about the specific cases since I
never really did a proper binNMU-esque analysis (i.e. re-build older
versions and see if rest things work) for the packages in
question.

Best,
Nilesh

Attachment: signature.asc
Description: PGP signature


Reply to: