[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))



Thanks Dirk for the clarification.

Le mercredi 28 juin 2023 à 10:24 -0500, Dirk Eddelbuettel a écrit :
> On 28 June 2023 at 17:07, 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?
> 
> They are. There is no binary API transition, just as there wasn't from R 4.0
> to 4.1, or from 4.1 to 4.2.  (And as before they cheated _a little_ and
> changes the graphics API so the likes of agg, ggplot2, ... need a rebuild.)

Well, so there is some ABI change, and some rebuilds needed.

Since we currently have no way to distinguish between the graphics
packages and the other ones (until we implement the r-graphics-api-*
tag that you suggest), I’m sorry to say that this implies that a proper
transition is needed from Debian’s point of view.

The Release Team will not accept to just binNMU the graphics packages,
because partial upgrades will be broken (i.e. it will still be possible
to install r-base 4.3 and a non-rebuilt graphics CRAN package, a
combination which is broken but not forbidden by the dependency
system).

Of course we could cheat and do source uploads of the affected CRAN
packages, but that would go against good practices and our quality
standards.

Cheers,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  https://www.debian.org

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: