Processed: transition: r-bioc-biocgenerics (r-api-bioc-3.20)

[Debian Bug Tracking System]

affects -1 + src:r-bioc-biocgenerics

Bug #1088701 [release.debian.org] transition: r-bioc-biocgenerics (r-api-bioc-3.20)
Added indication that 1088701 affects src:r-bioc-biocgenerics

block -1 by 1086904

Bug #1088701 [release.debian.org] transition: r-bioc-biocgenerics (r-api-bioc-3.20)
1088701 was not blocked by any bugs.
1088701 was not blocking any bugs.
Added blocking bug(s) of 1088701: 1086904

block -1 by 1088299

Bug #1088701 [release.debian.org] transition: r-bioc-biocgenerics (r-api-bioc-3.20)
1088701 was blocked by: 1086904
1088701 was not blocking any bugs.
Added blocking bug(s) of 1088701: 1088299

[Graham Inggs]

Hi Michael

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?

I don't think this is worth reverting. It cannot migrate to testing
as it is, and even if it would, we could just add a block hint.

Sorry about the mess I made!

No problem!

Regards
Graham

[Debian Bug Tracking System]

tags -1 + moreinfo

Bug #1088701 [release.debian.org] transition: r-bioc-biocgenerics (r-api-bioc-3.20)
Added tag(s) moreinfo.

[Graham Inggs]

Control: tags -1 + moreinfo

Hi MIchael

I would like a transition slot for Bioconductor 3.20.
We only need one new package, r-bioc-assorthead, and it is in the NEW queue. We are also still waiting on the removal of two r-bioc binary s390x packages. I've set both of those bugs to block this bug.

Please remove the moreinfo tag once these are done.

title = "r-api-bioc-3.20";
is_affected = .depends ~ /r-api-bioc/ | .source ~ /r-bioc-/;
is_good = .depends ~ "r-api-bioc-3.20";
is_bad = .depends ~ "r-api-bioc-3.19";

The tracker is set up [1].

Regards
Graham


[1] https://release.debian.org/transitions/html/r-api-bioc-3.20.html

[Michael R. Crusoe]

Control: tags -1 - moreinfo

Post by Graham Inggs
Control: tags -1 + moreinfo
Hi MIchael

I would like a transition slot for Bioconductor 3.20.
We only need one new package, r-bioc-assorthead, and it is in the NEW queue. We are also still waiting on the removal of two r-bioc binary s390x packages. I've set both of those bugs to block this bug.

Please remove the moreinfo tag once these are done.

The removals are done, but we are still waiting for r-bioc-assorthead to pass the NEW queue.

I would like to start the transition without waiting for r-bioc-assorthead, would that be okay?

Post by Graham Inggs

title = "r-api-bioc-3.20";
is_affected = .depends ~ /r-api-bioc/ | .source ~ /r-bioc-/;
is_good = .depends ~ "r-api-bioc-3.20";
is_bad = .depends ~ "r-api-bioc-3.19";

The tracker is set up [1].
Regards
Graham
[1] https://release.debian.org/transitions/html/r-api-bioc-3.20.html

[Debian Bug Tracking System]

tags -1 - moreinfo

Bug #1088701 [release.debian.org] transition: r-bioc-biocgenerics (r-api-bioc-3.20)
Removed tag(s) moreinfo.

[Debian Bug Tracking System]

tags -1 confirmed

Bug #1088701 [release.debian.org] transition: r-bioc-biocgenerics (r-api-bioc-3.20)
Added tag(s) confirmed.

[Debian Bug Tracking System]

Your message dated Tue, 21 Jan 2025 13:17:40 +0100
with message-id <9fb08e0d-3c9a-4e5a-af54-***@debian.org>
and subject line Re: Bug#1088701: transition: r-bioc-biocgenerics (r-api-bioc-3.20)
has caused the Debian Bug report #1088701,
regarding transition: r-bioc-biocgenerics (r-api-bioc-3.20)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)