Dear Release Team, While preparing uploads of the BioConductor 3.20 r-bioc-* packages to the experimental distribution, I accidentally uploaded a newer version of r-bioc-biocstyle (2.34.0+dfsg-1) to unstable. Shall I fix this by rolling back the change with an upload of a r-bioc-biocstyle source package version "2.34.0+really2.32.1+dfsg-1" to unstable (and corresponding "2.34.0+really2.34.0+dfsg-1" version to experimental)? Or shall I wait for the bioc-3.20 transition's [0] blockers [1][2] to be fixed and permission for the new r-bioc-* packages to be uploaded to unstable? Sorry about the mess I made! Thanks, [0] https://bugs.debian.org/1088701 [1] https://bugs.debian.org/1086904 RM: r-bioc-alabaster.base, r-bioc-alabaster.matrix [s390x] [2] https://bugs.debian.org/1088299 ITP: r-bioc-assorthead -- Assorted Header-Only C++ Libraries (in NEW)
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature