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

Bug#1093944: marked as done (transition: ruby3.3-default)

Your message dated Sun, 9 Feb 2025 22:25:26 +0100
with message-id <e125b404-a9f8-4d1b-ada5-35de69479328@debian.org>
and subject line Re: Bug#1093944: transition: ruby3.3-default
has caused the Debian Bug report #1093944,
regarding transition: ruby3.3-default
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.)


-- 
1093944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093944
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,

As discussed with Emilio, we are going to start the transition to switch the default ruby to version 3.3, while keeping version 3.1 as an alternative interpreter. He allowed me, on IRC, to already upload a new ruby-defaults to unstable. I am going to upload ruby-defaults/1:3.3~3.1 switching the default.

I am not providing a ben file, since I saw Emilio already updated the transition tracker:

https://release.debian.org/transitions/html/ruby3.3-default.html

So once ruby-defaults/1:3.3~3.1 lands in archive we can start the rebuilds.

TIA!

    

    
-- 
Lucas Kanashiro

  


--- End Message ---


--- Begin Message ---


On 05/02/2025 06:21, Soren Stoutner wrote:

On Tuesday, February 4, 2025 2:41:57 PM MST Soren Stoutner wrote:

Regarding redmine, #1094049 was fixed in 5.1.3+ds-6, but now there's
#1095148 (related to the nokogiri update). So it would still be better
to remove redmine from testing for now (together with its reverse
dependencies) to let ruby-defaults in.


Let me take a look at #1095148 and see how easy it is to fix.


#1095148 is not an easy fix.  Ananthu made an attempt to bump a few gem versions, but
they ended up causing massive test failures.

https://salsa.debian.org/ruby-team/redmine/-/commit/
467eb9df226cfdf021b226abc8c38ddbdb69dd60

I agree that the best way forward is to temporarily remove redmine from testing.

I have started work on packaging redmine 6.0.3, but it will take a bit of work.

https://salsa.debian.org/ruby-team/redmine

1.  Redmine 6.x introduces a new dependency on ruby-rails-propshaft, which I have
started working on packaging.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095198


2.  Redmine transitions to Rails 7.  Currently, not all the packages I need to test it are
available in experimental.  It is possible that everything builds cleanly, but it is also
possible there are complexities.

soren@soren-desktop:~$ sudo apt install -t experimental rails ruby-actionpack-xml-parser
ruby-roadie-rails ruby-actionview ruby-activesupport ruby-actionpack
ruby-actionpack-xml-parser is already the newest version (2.0.1-4).
ruby-roadie-rails is already the newest version (3.0.0-1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
  ruby-actionpack-xml-parser : Depends: ruby-actionpack (< 2:7) but 2:7.2.2.1+dfsg-1~exp4
is to be installed
                               Depends: ruby-railties (< 2:7) but 2:7.2.2.1+dfsg-1~exp4 is to be installed
  ruby-roadie-rails : Depends: ruby-railties (< 2:7.1) but 2:7.2.2.1+dfsg-1~exp4 is to be
installed
Error: Unable to correct problems, you have held broken packages.


3. Redmine 6.0.3 still targets nokogiri ~> 1.16.0 and sanitize ~> 6.0.  It is likely that when
points 1 and 2 above are address, there will still be issues with nokogiri 1.18 and sanitize
7.0.  The upcoming Redmine 6.1.0 supports nokogiri 1.18, so it might not be too difficult to
backport it to 6.0.3.

https://www.redmine.org/issues/41964


Some packages had to be removed, but ruby-defaults finally migrated.

Cheers,
Emilio

--- End Message ---







Reply to: