Skip to content
Prev 21313 / 21319 Next

[Bioc-devel] rworkflows temporary CRAN removal and next steps

Thank you for the suggestion, Ivan. I will use that function going forward.

At the time, the maintainer was away on leave. As I was not listed as a maintainer, I did not receive any notifications about this.

I wish it were possible to have more than one maintainer!

Kind regards,
Hiru

From: Ivan Krylov <ikrylov at disroot.org>
Date: Friday, 20 March 2026 at 6:40?pm
To: Hiranyamaya Dash (Hiru) <hdash.work at gmail.com>
Cc: Skene, Nathan G <n.skene at imperial.ac.uk>, bioc-devel at r-project.org <bioc-devel at r-project.org>
Subject: Re: [Bioc-devel] rworkflows temporary CRAN removal and next steps

? Fri, 20 Mar 2026 14:21:29 +0000
"Hiranyamaya Dash (Hiru)" <hdash.work at gmail.com> ?????:
That must have been the case:

tools:::CRAN_package_issues() |> subset(Package == 'rworkflows') |>
tail(1)
#               ID    Package                Date From     Before
# 22099 2026.15520 rworkflows 2026-02-16 10:20:07  BDR 2026-03-02
#                   Title Label Info
# 22099 Additional_issues  <NA> <NA>

Did an e-mail from around 16th of February land in the spam folder?

In the future, it may help to set up a periodic check to warn in case
subset(tools::CRAN_package_db(), Package == 'rworkflows', 'Deadline')
stops being NA.

--
Best regards,
Ivan