Your message dated Tue, 18 Feb 2025 10:40:16 +0100
with message-id <bf5c9505-c257-407d-aadb-33cbdd9d2...@debian.org>
and subject line Re: Bug#1095713: transition: ruby3.1-rm
has caused the Debian Bug report #1095713,
regarding transition: ruby3.1-rm
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 ow...@bugs.debian.org
immediately.)
--
1095713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
Hi release team,
Now that ruby3.3 is already the default in testing, I'd like to start
removing support for ruby3.1.
Our plan is to start this transition once ruby-rack 3 migrates to
testing and before starting the rails 7 transition, to avoid further
entanglement.
I already uploaded ruby-defaults/1:3.3~3.3 to experimental removing
ruby3.1 support.
The following Ben file can be used to create the tracker page:
is_affected = (.depends ~ /ruby3.1/ | .depends ~ /ruby3.3/) & !.source ~
/^(ruby3.1|ruby3.3|ruby-defaults)$/; is_good = ! .depends ~ /ruby3.1/;
is_bad = .depends ~ /ruby3.1/;
TIA!
--
Lucas Kanashiro
--- End Message ---
--- Begin Message ---
On 11/02/2025 21:33, Lucas Kanashiro wrote:
Hi,
On 11/02/2025 16:22, Emilio Pozuelo Monfort wrote:
Control: tags -1 confirmed
On 11/02/2025 04:49, Lucas Kanashiro wrote:
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
Hi release team,
Now that ruby3.3 is already the default in testing, I'd like to start
removing support for ruby3.1.
Our plan is to start this transition once ruby-rack 3 migrates to testing and
before starting the rails 7 transition, to avoid further entanglement.
I already uploaded ruby-defaults/1:3.3~3.3 to experimental removing ruby3.1
support.
The following Ben file can be used to create the tracker page:
is_affected = (.depends ~ /ruby3.1/ | .depends ~ /ruby3.3/) & !.source ~ /
^(ruby3.1|ruby3.3|ruby-defaults)$/; is_good = ! .depends ~ /ruby3.1/;
is_bad = .depends ~ /ruby3.1/;
Go ahead.
ruby-defaults/1:3.3 was uploaded to unstable, once it is properly published in
the archive we can proceed with binNMUs.
I hinted the removal of ruby3.1 yesterday, and it is gone from testing.
Cheers,
Emilio
--- End Message ---
