Re: Bug#1023731: BioC Transition blocked by new dependencies
On Mon, Nov 21, 2022 at 04:39:26PM +0100, Andreas Tille wrote:
>...
> Am Mon, Nov 21, 2022 at 03:05:26PM +0100 schrieb Sebastian Ramacher:
> > On 2022-11-21 15:02:16 +0100, Andreas Tille wrote:
> > > Control: block -1 by 1024563
> > > Control: block -1 by 1024565
> > > Control: block -1 by 1024567
> > >
> > > Some of the BioConductor packages need new dependencies.
> > > I have pushed these to new queue and set the ITP bugs as
> > > blocker.
> >
> > As this is happening every r-bioc transition, could this be handled
> > before starting the transition the next time?
>
> This is really hard to do, thought. The new packages are needing those
> packages from the transition. I actually injected two packages from
> higher levels manually to be able to build one of the new packages. So
> we really need to upload the start of the transition and I do not see
> any sense in not documenting what we are doing without the transition
> tracker.
>...
Your transition is special because you are manually uploading every
single package involved in the transition.
You could upload everything to experimental, run a local ben tracker
against experimental, and when the transition is complete in
experimental contact the release team for the transition in unstable.
The actual transition is then a batch of "Upload to unstable".
> Kind regards
> Andreas.
cu
Adrian
Example for the status of the ongoing python3.11-add transition in experimental:
$ cat tracker/python3.11-add.ben
title = "Add Python 3.11 as supported version";
is_affected = .build-depends ~ /python3-all-dev|python3-all-dbg/ | .build-depends-arch ~ /python3-all-dev|python3-all-dbg/;
is_good = .depends ~ /python3 \(<< 3\.12\)|python3.11|python3-dbg \(<< 3\.12\)|python3.11-dbg/;
is_bad = .depends ~ /python3 \(<< 3\.11\)|python3-dbg \(<< 3\.11\)/ | .breaks ~ /python \(>= 3\.11\)|python-dbg \(>= 3\.11\)/;
notes = "#1021984";
$ ben download --suite experimental --preferred-compression-format xz
Downloading /home/bunk/Sources...
Downloading /home/bunk/Packages_armhf...
Downloading /home/bunk/Packages_amd64...
Downloading /home/bunk/Packages_mips64el...
Downloading /home/bunk/Packages_armel...
Downloading /home/bunk/Packages_i386...
Downloading /home/bunk/Packages_arm64...
Downloading /home/bunk/Packages_mipsel...
Downloading /home/bunk/Packages_ppc64el...
Downloading /home/bunk/Packages_s390x...
$ ben tracker -cd tracker
Parsing /home/bunk/Sources...
Parsing /home/bunk/Packages_amd64...
Parsing /home/bunk/Packages_arm64...
Parsing /home/bunk/Packages_armel...
Parsing /home/bunk/Packages_armhf...
Parsing /home/bunk/Packages_i386...
Parsing /home/bunk/Packages_mips64el...
Parsing /home/bunk/Packages_mipsel...
Parsing /home/bunk/Packages_ppc64el...
Parsing /home/bunk/Packages_s390x...
Computing data for (unknown) python3.11-add
Generating html/python3.11-add.html
Generating ./export/packages.yaml
Cleaning up...
Generating index...
$ cp -a /usr/share/ben/media html/
$
html/python3.11-add.html can then be viewed with any web broswer
(or html/ copied to a public webserver like people.d.o).
Different from the release team tracker, "ben download" above will get
updated data only every 6 hours after dinstall.
Reply to: