On Fri, 10 Jan 2025 11:08:07 +0100 Emilio Pozuelo Monfort
<po...@debian.org> wrote:
> Control: tags -1 confirmed
>
> On 09/01/2025 20:05, Lucas Kanashiro wrote:
> > Hi Emilio,
> >
> > On 09/01/2025 12:36, Emilio Pozuelo Monfort wrote:
> >> On 30/12/2024 21:38, Lucas Kanashiro wrote:
> >>> We filed bugs for the packages that are failing to build with
ruby 3.3 and
> >>> are not in the removal request list above:
> >>>
> >>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-
> >>> r...@lists.debian.org&tag=ruby3.3
> >>
> >> What's the plan for those? I.e. what would happen if we started this
> >> transition now? Would those block it? I don't see any activity in
them
> >> (haven't checked them all). Looks like most of them are not key
packages, but
> >> these two are, so they should be addressed or there should be a
plan for them
> >> before we go ahead.
> >>
> >> ruby-amq-protocol
> >> ruby-excon
> >
> > I just addressed those 2 bugs, they should be closed at this point.
For ruby-
> > excon, it was a problem in the rebuild we did, I closed the bug and
added an
> > explanation and a link to the successful build log. For
ruby-amq-protocol, it
> > was a problem in the upstream code, I patched it and uploaded
version 2.3.2-2
> > fixing it.
> >
> > I hope this helps with the beginning of the ruby 3.3 transition.
>
> Ack. Go ahead with the transition.
Thanks! I just uploaded ruby-defaults/3.1+support3.3 to unstable, it
should be available in the archive soon.
Cheers!
--
Lucas Kanashiro
