[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1090913: marked as done (transition: ruby3.3-add)

Your message dated Thu, 23 Jan 2025 09:52:54 +0100
with message-id <[🔎] fc31664d-1949-4efc-a463-c7491314e127@debian.org>
and subject line Re: Bug#1090913: transition: ruby3.3
has caused the Debian Bug report #1090913,
regarding transition: ruby3.3-add
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 owner@bugs.debian.org
immediately.)


-- 
1090913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090913
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Hi,

I would like to start the transition to ruby 3.3 in unstable. General
information about Ruby transitions can be found in:
https://wiki.debian.org/Teams/Ruby/InterpreterTransitions

ruby3.3 has been in testing for a while. Building against ruby3.3 has
been enabled in experimental, and we already did a test rebuild against
it, with satisfiable results:
https://ruby-builds.debian.net/ruby3.3/

We also requested a bunch of removals to help with this transition here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090911

So I would like to enable building against ruby3.3 in unstable, and to
effectively start the transition.

Ben file:

title = "ruby3.3-add";
architectures = [ "amd64" ];
is_affected = (.depends ~ /ruby3.1/ | .depends ~ /ruby3.3/) & !.source ~ /^(ruby3.1|ruby3.2|ruby3.3|ruby-defaults|dislocker|epic5|graphviz|hivex|kamailio|klayout|kross-interpreters|libprelude|marisa|ngraph-gtk|notmuch|obexftp|redland-bindings|rubyluabridge|ruby-standalone|subtle|subversion|uwsgi|vim-command-t|weechat|robot-testing-framework|treil|vim|nbdkit|spglib|ignition-math)$/;
is_good = .depends ~ /ruby3.3/;
is_bad = .depends ~ /ruby3.1/ & !.depends ~ /ruby3.3/;

TIA!


-- 
Lucas Kanashiro

--- End Message ---
--- Begin Message --- 
Control: retitle -1 transition: ruby3.3-add

On 23/01/2025 09:11, Emilio Pozuelo Monfort wrote:

On 23/01/2025 02:18, Lucas Kanashiro wrote:
ruby-defaults/1:3.3~0 was uploaded to experimental with ruby3.3 as the default and removing ruby3.1. 

I generated a list of package to rebuild using the following ben file:

title = "ruby3.3-default";
is_affected = (.depends ~ /ruby3.1/ | .depends ~ /ruby3.3/) & !.source ~ / ^(ruby3.1|ruby3.3|ruby-defaults)$/; 
is_good = ! .depends ~ /ruby3.1/ & .depends ~ /ruby3.3/;
is_bad = .depends ~ /ruby3.1/;
I rebuilt all of them using ruby-defaults from experimental. You can see the results here as usual: 

https://ruby-builds.debian.net/ruby3.3/
 From the build 20 onward, all builds are related to this new round of rebuilds. The summary is: 

- 20 build failures
   + 2 bug reports with patches (uwsgi and vim-command-t)
   + 2  packages with fixes uploaded to the archive already (puma and ruby-mpi)
   + libse{linux,manage} are FTBFSing but unrelated to the ruby transition. A problem with SWIG and python    + All the other packages were already removed from testing, so not blocking the migration
With that in mind, I'd like to request the permission to start this second part of the transition in unstable. 

Ack, go ahead.
Actually, it'd be best to switch the default without removing support for 3.1 in one transition. Then after that, we can drop 3.1 as a supported version. So doing this in two steps instead of one, like we used to do in the past (see e.g. #1015207, #1023495, #1026890). Also, let's better track it in a separate transition request. 

Cheers,
Emilio

--- End Message ---
Reply to: