Another R 4.5.0 and BioConductor 3.21 idea
There is another possibly bullet point for the list Charles assembled in what
became a long-ish thread. We could simply update the (tiny) BiocVersion (aka
r-bioc-biocversion) package to its new 3.21 release. (And, for the next few
weeks, knowingly leave the other r-bioc-* packages at 3.20.) If and when a
user invokes BiocManager::install() they will at least be able to install (or
upgrade) packages.
It removes a hard conflict between 3.20 and R 4.5.0 and allows continued
operations.
Of course, it is not ideal as a bunch of packages remain in 'need an update'
state but that happens to other r-cran-* packages too at times.
But it removes the hard(er) conflict we currently have. Just a thought.
Cheers, Dirk
PS I just 'organically' upgraded about 500 r-bioc-* packages three times each
for Ubuntu 20.04, 22.04, and 24.04 over at my r2u project, and had no issues
(besides racking up cpu cycles at GitHub Actions). I ran this from the
'inside out' ordering all packages by the number of BioC depenendencies,
starting with the no-depends packages and working up. That way dependee
packages were tested during the build.
--
dirk.eddelbuettel.com | @eddelbuettel | edd@debian.org
Reply to: