On 27 October 2023 at 16:00, Andreas Tille wrote: | Package: release.debian.org | Severity: normal | User: release.debian....@packages.debian.org | Usertags: transition | X-Debbugs-Cc: r-bioc-biocgener...@packages.debian.org, debia...@lists.debian.org | Control: affects -1 + src:r-bioc-biocgenerics | | Hi, | | BioConductor has just released version 3.17. Since the next r-base
Typo: 3.18 | release is pending on 2023-10-31 we do not think it is a good idea to | start the transition before but it might make sense to open this bug These two events are basically unrelated. (BioC releases twice a year, and the April release comes usually right after an R release. Those may warrant staging. October releases do not. It uses R 4.3.*. Note the wildcard.) | right now. (No idea whether we will see a proper r-api transition but R does not change APIs on _minor_ releases such as 4.3.2 next week. Dirk | building everything against the new r-base sounds like less hassle | than doing r-api-bioc transition right now.) | The BioConductor transition will bump the virtual package | r-api-bioc-3.17 to r-api-bioc-3.18. | | BTW, I'm aware that a couple of r-bioc-* packages did not yet migrated | to testing due to some autopkgtest issues on some architectures. We | decided that it makes sense to do the transition first and approach | upstream about their latest release in case those issues might remain. | | Kind regards and thanks a lot for your work as release team | Andreas. | | Ben file: | | title = "r-bioc-biocgenerics"; | is_affected = .depends ~ "r-api-bioc-3.17" | .depends ~ "r-api-bioc-3.18"; | is_good = .depends ~ "r-api-bioc-3.18"; | is_bad = .depends ~ "r-api-bioc-3.17"; | -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
