[DRE-maint] Bug#1069089: ruby-rubygems: Broken platform detection which lead to unability to install sass-embedded

te-3.3.15-behavior-on-Ruby-3.1.patch ───┼───── 1 │ From: Antonio Terceiro 2 │ Date: Fri, 13 Oct 2023 11:14:01 -0300 3 │ Subject: Gem::Platform: emulate 3.3.15 behavior on Ruby 3.1 4 │ 5 │ rubygems

Re: [DRE-maint] ruby-liquid-c is marked for autoremoval from testing

On Thu, Aug 22, 2024 at 11:44:03PM -0500, Piper McCorkle wrote: > On Thursday, 22 August 2024 23:39:07 CDT Debian testing autoremoval watch > wrote: > > ruby-liquid-c 4.1.0-2 is marked for autoremoval from testing on 2024-09-04 > > > > It is affected by these RC bugs: > > 1077072: ruby-liquid-c:

[DRE-maint] Bug#1054727: rails: FTBFS: build-dependency not installable: ruby-thin (>= 1.6.0)

Control: forcemerge 1054256 -1 Control affects 1054256 + src:rails On Fri, Oct 27, 2023 at 09:27:35PM +0200, Lucas Nussbaum wrote: > Source: rails > Version: 2:6.1.7.3+dfsg-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231027 ftb

[DRE-maint] Bug#1054256: ruby-blade: uninstallable in unstable (ruby-blade : Depends: ruby-thin (>= 1.6.0) but it is not installable)

Package: ruby-blade Version: 0.7.1-4 Severity: serious Justification: uninstallable After the last upload, ruby-blade ended up with a dependency on ruby-thin, which does not exist. 8<8<8<- $ LANG=C sudo apt install ruby-blade/unstabl

[DRE-maint] Bug#1050867: marked as pending in jekyll

On Fri, Sep 01, 2023 at 05:25:38PM +0200, Sébastien Villemot wrote: > Hi Antonio, > > Le mercredi 30 août 2023 à 15:33 +, Antonio Terceiro a écrit : > > Bug #1050867 in jekyll reported by you has been fixed in the > > Git repository and is awaiting an upload. Y

[DRE-maint] Bug#1051302: bookworm-pu: package jekyll/4.3.1+dfsg-3+deb12u1

/changelog b/debian/changelog index b91ea6e..7ba5630 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +jekyll (4.3.1+dfsg-3+deb12u1) bookworm; urgency=medium + + [ Sébastien Villemot ] + * Allow YAML aliases (Closes: #1050867) + + -- Antonio Terceiro Tue, 05 Sep 2023 19:37:14 -0300

[DRE-maint] Bug#1049999: vagrant: the future of packaging vagrant in Debian

On Thu, Aug 24, 2023 at 01:46:11AM +0200, Guillem Jover wrote: > Hi! > > On Fri, 2023-08-18 at 08:07:44 -0300, Antonio Terceiro wrote: > > FWIW, I have been maintaining vagrant in Debian for several years. > > BTW, thank you for having done that, it's been much appreci

[DRE-maint] Bug#1049999: vagrant: the future of packaging vagrant in Debian

On Sat, Aug 19, 2023 at 06:46:06AM +0200, Lucas Nussbaum wrote: > Hi, > > This license change is so disappointing... > > On 18/08/23 at 08:07 -0300, Antonio Terceiro wrote: > > > Plan B. > > > > > > - Drop vagrant because of that changed licence

[DRE-maint] Bug#1049999: vagrant: the future of packaging vagrant in Debian

Hi, FWIW, I have been maintaining vagrant in Debian for several years. Thank you for raising this as I have been too lazy to push this discussion. I am copying the Debian Ruby team plus all the people that I could find listed as maintainer or uploader of vagrant related packages (mostly plugins,

[DRE-maint] Bug#1034497: unblock: jekyll/4.3.1+dfsg-2

: #1034450) + + -- Antonio Terceiro Sun, 16 Apr 2023 18:35:56 -0300 + jekyll (4.3.1+dfsg-1) unstable; urgency=medium * Team upload diff --git a/debian/ruby-tests.rake b/debian/ruby-tests.rake index e926490..26eeaf2 100644 --- a/debian/ruby-tests.rake +++ b/debian/ruby-tests.rake @@ -8,6 +8,8

[DRE-maint] Bug#1019732: apt-listbugs: undefined method `default' for " # returns password\n":String

Control: reassign -1 apt-listbugs On Tue, Mar 28, 2023 at 06:39:35PM +0200, Francesco Poli wrote: > Control: reassign -1 ruby 1:3.0+1 > Control: affects -1 + apt-listbugs > > > On Fri, 24 Mar 2023 00:40:41 +0100 Francesco Poli wrote: > > [...] > > What you saw seems to be another case where som

[DRE-maint] Bug#1032070: fixed in ruby3.1 3.1.2-7~exp

On Fri, Mar 24, 2023 at 02:23:07PM +0530, Pirate Praveen wrote: > On Wed, 15 Mar 2023 01:05:14 +0530 Pirate Praveen > wrote: > > Are you planning to upload this to bookworm? We are starting to test > > gitlab on bookworm to be able to provide gitlab via bookworm-fasttrack > > when bookworm release

[DRE-maint] Bug#1033573: unblock: ruby3.1/3.1.2-7

0644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,15 @@ +ruby3.1 (3.1.2-7) unstable; urgency=medium + + * Upload to unstable + + -- Antonio Terceiro Sat, 25 Mar 2023 14:20:34 -0300 + +ruby3.1 (3.1.2-7~exp) experimental; urgency=medium + + * Update openssl extension to to 3.0.1 (Closes

[DRE-maint] Bug#1030987: bullseye-pu: package vagrant/2.2.14+dfsg-2

info ] n/a diff --git a/debian/changelog b/debian/changelog index fc3cfcf..a28263d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +vagrant (2.2.14+dfsg-2) bullseye; urgency=medium + + * Add support for VirtualBox 7.0 (Closes: #1026227) + + -- Antonio Terceiro Tue, 07 Feb 2023

[DRE-maint] Bug#1029728: bullseye-pu: package passenger/5.0.30-1.2+deb11u1

ebian/changelog index 729f9ae..2518772 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +passenger (5.0.30-1.2+deb11u1) bullseye; urgency=medium + + * Add patch to enable usage with newer NodeJS versions (Closes: #1025220) + + -- Antonio Terceiro Tue, 13 Dec 2022 19:48:20

[DRE-maint] Bug#1029632: unblock: ruby3.1/3.1.2-5

g +all Ruby packages to add ruby3.1 support, where ruby-augeas and +ruby-libvirt failed to build. + + -- Antonio Terceiro Wed, 25 Jan 2023 14:46:18 -0300 + ruby3.1 (3.1.2-4) unstable; urgency=medium * Replace cross pkg-config patch with patches applied upstream diff --git a/debian

[DRE-maint] Bug#1028221: RM: ruby3.0 -- ROM; obsolete

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby...@packages.debian.org Control: affects -1 + src:ruby3.0 Please remove ruby3.0 from unstable. It was an intermediate step between ruby2.7 (bullseye) and ruby3.1 (bookworm), and is

[DRE-maint] Bug#1027710: libruby3.0: drop Provides: ruby-dbm (now provided separately)

Control: reassign -1 dhelp Control: retitle -1 dhelp: dependency on ruby-dbm satisfied by (obsolete) libruby3.0 On Mon, Jan 02, 2023 at 11:28:54AM +0100, Drew Parsons wrote: > Package: libruby3.0 > Version: 3.0.4-8 > Severity: normal > > A new ruby-dbm package was recently created to resolve Bug

[DRE-maint] Bug#1027342: itamae: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'net-telnet

Control: reassign -1 src:ruby-specinfra Control: forcemerge #1027347 -1 Control: affects #1027347 src:itamae On Fri, Dec 30, 2022 at 05:20:58PM +0100, Lucas Nussbaum wrote: > Source: itamae > Version: 1.14.1-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debi

Re: [DRE-maint] ruby-dbm_1.1.0-1_amd64.changes is NEW

On Fri, Dec 30, 2022 at 11:04:46PM -0500, Paul Tagliamonte wrote: > I've marked this package for ACCEPT. > > However, there's one borderline issue that I'm going to allow through > NEW, because I don't believe it impacts our distributability, however > it's likely an RC bug IMHO. > > The debian/c

Re: [DRE-maint] ruby-dbm_1.1.0-1_amd64.changes is NEW

Hi, On Sat, Dec 31, 2022 at 01:09:44AM +, Debian FTP Masters wrote: > binary:ruby-dbm is NEW. > binary:ruby-dbm is NEW. > source:ruby-dbm is NEW. This package is needed ir order to fix dhelp: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027407 It's also a very simple package, so if po

[DRE-maint] Bug#1027407: ruby-rubygems: kernel_require.rb LoadError breaks dhelp

Control: reassign -1 dhelp Control: severity -1 serious Control: retitle: dhelp: depends on module removed from the Ruby stdlib (dbm) On Fri, Dec 30, 2022 at 06:09:03PM +0100, Drew Parsons wrote: > Package: ruby-rubygems > Version: 3.3.15-1 > Severity: important > > /usr/lib/ruby/vendor_ruby/ruby

[DRE-maint] Bug#1027098: vagrant: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: expect(env).to receive(:[]=).with(:machine_ssh_info, host: "ADDRESS") 

Source: vagrant Version: 2.2.19+dfsg-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, vagrant failed to build. Relevant part of the bu

[DRE-maint] Bug#1027096: ruby-webmock: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: @headers = Util::Headers.normalize_headers(@headers)

Source: ruby-webmock Version: 3.8.3-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-webmock failed to build. Relevant part of th

[DRE-maint] Bug#1027095: ruby-vcr: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: /<>/lib/vcr/library_hooks/webmock.rb:36:in `block in global_hook_disabled_requests': wrong num

Source: ruby-vcr Version: 6.0.0+really5.0.0-4 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-vcr failed to build. Relevant part o

[DRE-maint] Bug#1027093: ruby-thor: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: result = Thor::LineEditor.readline(message, options)

Source: ruby-thor Version: 1.2.1-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-thor failed to build. Relevant part of the buil

[DRE-maint] Bug#1027092: ruby-stomp: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error:

Source: ruby-stomp Version: 1.4.10-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-stomp failed to build. Relevant part of the b

[DRE-maint] Bug#1027091: ruby-slack-notifier: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: client.post endpoint, params

Source: ruby-slack-notifier Version: 1.5.1-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-slack-notifier failed to build. Relev

[DRE-maint] Bug#1027090: ruby-slack-messenger: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error:

Source: ruby-slack-messenger Version: 2.3.4-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-slack-messenger failed to build. Rel

[DRE-maint] Bug#1027089: ruby-simplecov: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: Coverage.start(start_arguments)

Source: ruby-simplecov Version: 0.21.2-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-simplecov failed to build. Relevant part

[DRE-maint] Bug#1027087: ruby-rubocop-performance: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: subject(:config) { RuboCop::ConfigLoader.load_file('config/default.yml') }

Source: ruby-rubocop-performance Version: 1.7.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-rubocop-performance failed to build

[DRE-maint] Bug#1027088: ruby-seamless-database-pool: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: master_connection = send("#{master_config[:adapter]}_connection".to_sym,

Source: ruby-seamless-database-pool Version: 1.0.20-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-seamless-database-pool failed

[DRE-maint] Bug#1027086: ruby-rest-client: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error:

Source: ruby-rest-client Version: 2.1.0-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-rest-client failed to build. Relevant pa

[DRE-maint] Bug#1027083: ruby-notiffany: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: expect(foo_object).to receive(:notify).with("Hello", foo: "bar")

Source: ruby-notiffany Version: 0.1.3-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-notiffany failed to build. Relevant part o

[DRE-maint] Bug#1027082: ruby-mysql2: FTBFS: ERROR: Test "ruby3.1" failed: mysqld crashes at startup

Source: ruby-mysql2 Version: 0.5.3-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-mysql2 failed to build. I retried it with the ve

[DRE-maint] Bug#1027081: ruby-multi-json: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: self.load_options = self.dump_options = value

Source: ruby-multi-json Version: 1.14.1-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-multi-json failed to build. Relevant par

[DRE-maint] Bug#1027080: ruby-localhost: FTBFS: tests fail randomly

Source: ruby-localhost Version: 1.1.9-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-localhost failed to build. I retried it with

[DRE-maint] Bug#1027079: ruby-listen: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: @snapshots[dir].invalidate(type, rel_path, options)

Source: ruby-listen Version: 3.7.0-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-listen failed to build. Relevant part of the

[DRE-maint] Bug#1027078: ruby-jira: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: result.push(client.Issue.build(issue))

Source: ruby-jira Version: 2.1.5-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-jira failed to build. Relevant part of the buil

[DRE-maint] Bug#1027077: ruby-invisible-captcha: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error:

Source: ruby-invisible-captcha Version: 1.1.0-5 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-invisible-captcha failed to build. Relevan

[DRE-maint] Bug#1027076: ruby-influxdb: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed.

Source: ruby-influxdb Version: 0.8.1-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-influxdb failed to build. Relevant part of

[DRE-maint] Bug#1027075: ruby-guard: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed.

Source: ruby-guard Version: 2.18.0-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-guard failed to build. Relevant part of the b

[DRE-maint] Bug#1027074: ruby-grape: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: namespace_inheritable(:version_options, options)

Source: ruby-grape Version: 1.6.2-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-grape failed to build. Relevant part of the bu

[DRE-maint] Bug#1027073: ruby-gh: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: expect { subject['/x'] }.to raise_error(GH::Error(:response_status => 500))

Source: ruby-gh Version: 0.18.0-4 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-gh failed to build. Relevant part of the build l

[DRE-maint] Bug#1027072: ruby-fission: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: Fission::Action::VM::Stopper.new(self).stop(options)

Source: ruby-fission Version: 0.5.0-2.1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-fission failed to build. Relevant part of

[DRE-maint] Bug#1027067: ruby-bunny: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: expect(ch).to receive(:exchange_bind).with(src1, dst, routing_key: "abc")

Source: ruby-bunny Version: 2.19.0-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, ruby-bunny failed to build. Relevant part of the b

[DRE-maint] Bug#1027066: atig: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: user = t.get("users/show", { screen_name: nick})

Source: atig Version: 0.6.1-7 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-rspec-3.12 Hi, I'm about to upload ruby-rspec 3.12. During a test rebuild with that version, atig failed to build. Relevant part of the build log (hop

Re: [DRE-maint] Most packages which did not build because of tzdata still FTBFS in bookworm

On Tue, Dec 27, 2022 at 11:58:26AM +0100, Santiago Vila wrote: > Hello. > > Thanks for fixing Bug #1026178 in ruby-tzinfo. > > Unfortunately, the following 20 packages still FTBFS in bookworm: > > ruby-active-model-serializers > ruby-ahoy-email > ruby-arbre > ruby-browser > ruby-coffee-rails > r

[DRE-maint] Bug#1027060: ruby-varia-model: FTBFS with ruby-hashie 5.0.0-1: unsatisfiable build-dependency: ruby-hashie (< 4.0.0) but 5.0.0-1 is to be installed

Source: ruby-varia-model Version: 0.6.0-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-hashie-5.0.0 Hi, After updating ruby-hashie to 5.0.0-1, ruby-varia-model fails to build. Relevant part of the build log (hopefully): > +--

[DRE-maint] Bug#1027059: ruby-rash-alt: FTBFS with ruby-hashie 5.0.0-1: ERROR: Test "ruby3.1" Could not find 'hashie' (~> 3.4) among 98 total gem(s) (Gem::MissingSpecError)

Source: ruby-rash-alt Version: 0.4.3-1.1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-hashie-5.0.0 Hi, After updating ruby-hashie to 5.0.0-1, ruby-rash-alt fails to build. Relevant part of the build log (hopefully): > /usr/li

[DRE-maint] Bug#1027058: ruby-github-api: FTBFS with ruby-hashie 5.0.0-1: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_depende

Source: ruby-github-api Version: 0.19.0-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-hashie-5.0.0 Hi, After updating ruby-hashie to 5.0.0-1, ruby-github-api fails to build. Relevant part of the build log (hopefully): > /usr

[DRE-maint] Bug#1019628: ruby-hashie: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "The property 'middle_name' is not defined for DashTest.", got #

Control: reassign -1 ruby-rspec-expectations Control: retitle -1 ruby-rspec-expectations: raise_error() matcher does not work with ruby3.1 Control: forwarded -1 https://github.com/rspec/rspec-expectations/issues/1338 Control: affects -1 src:ruby-hashie On Sat, Nov 19, 2022 at 03:29:31PM +0200, A

[DRE-maint] Bug#1026948: schleuder: FTBFS with ruby-sinatra >= 3.0: ERROR: Test "ruby3.1" failed: NoMethodError:

Control: tag -1 + patch Control: retitle -1 FTBFS with ruby-sinatra >= 3.0: gemspec has strict dependency on sinatra ~> 2 On Sat, Dec 24, 2022 at 12:50:51PM -0300, Antonio Terceiro wrote: > Source: schleuder > Version: 4.0.3-6 > Severity: important > Justification: FTBFS > T

[DRE-maint] Bug#1026948: schleuder: FTBFS with ruby-sinatra >= 3.0: ERROR: Test "ruby3.1" failed: NoMethodError:

Source: schleuder Version: 4.0.3-6 Severity: important Justification: FTBFS Tags: sid ftbfs User: debian-r...@lists.debian.org Usertags: sinatra-3 Hi, While trying rebuilds with src:ruby-sinatra 3.0.5-1, your package failed to build on amd64. Please try to support sinatra 3 as soon as possible, a

[DRE-maint] Bug#1026946: ruby-omniauth-auth0: FTBFS with ruby-sinatra >= 3.0: ERROR: Test "ruby3.1" failed: ArgumentError:

Source: ruby-omniauth-auth0 Version: 2.0.0-1 Severity: important Justification: FTBFS Tags: sid ftbfs User: debian-r...@lists.debian.org Usertags: sinatra-3 Hi, While trying rebuilds with src:ruby-sinatra 3.0.5-1, your package failed to build on amd64. Please try to support sinatra 3 as soon as p

[DRE-maint] Bug#1026897: ruby-tilt: FTBFS: ERROR: Test "ruby3.1" failed.

Source: ruby-tilt Version: 2.0.11-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, After updating ruby-haml to 6.1.1, ruby-tilt fails to build with a test failure. Relevant part (hopefully): > /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner > > ┌──

[DRE-maint] Bug#1026895: ruby-html2haml: FTBFS with ruby-haml 6.1.1: ERROR: Test "ruby3.1" failed: Could not find 'haml' (>= 4.0, < 6) among 102 total gem(s) (Gem::MissingSpecError)

Source: ruby-html2haml Version: 2.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block

[DRE-maint] Bug#1026894: ruby-haml-rails: FTBFS: unsatisfiable build-dependency: ruby-haml (< 6.0) but 6.1.1-1 is to be installed

Source: ruby-haml-rails Version: 2.0.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, After updating ruby-haml to 6.1.1, ruby-haml-rails has unsatisfiable build dependencies. Relevant part (hopefully): > +

[DRE-maint] Bug#1026893: ruby-haml-contrib: FTBFS: ERROR: Test "ruby3.1" failed: /<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filters/php.rb:8:in `': Filters is

Source: ruby-haml-contrib Version: 1.0.0.1-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, After updaring ruby-haml to 6.6.1, ruby-haml-contrib fails to build with a test failure. Relevant part (hopefully): > /<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filt

[DRE-maint] Bug#1026892: asciidoctor: FTBFS with haml 6.1.1: ERROR: Test "ruby3.1" failed.

Source: asciidoctor Version: 2.0.17-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, I'm working on updating ruby-haml to the new upstream versinon 6.1.1, and when trying asciidoctor against that the tests fail. Relevant part (hopefully): > /usr/bin/ruby3.1 /usr/bin/gem2deb

[DRE-maint] Bug#1026890: transition: ruby3.0-rm

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: ruby-defau...@packages.debian.org Control: affects -1 + src:ruby-defaults Please create a tracker for removing ruby3.0 as a supported version. Ben file (based on ruby2.7-rm

[DRE-maint] Bug#1026427: jekyll: depends on deprecated and broken ruby-safe-yaml

Package: jekyll Version: 3.9.0+dfsg-5 Severity: serious Tags: upstream Dear Maintainer, Working to get ruby3.1 as the default Ruby version it was noticed that ruby-safe-yaml is incompatible with ruby3.1 and thus deprecated. Most upstreams have dropped their dependencies on it; I checked and jekyl

[DRE-maint] Bug#1026227: vagrant: Uninstallable in sid with VirtualBox 7.0.x

On Fri, Dec 16, 2022 at 06:31:41PM +0100, Guillem Jover wrote: > Package: vagrant > Version: 2.2.19+dfsg-2 > Severity: serious > > Hi! > > Since virtualbox 7.0.4 got uploaded, vagrant is no longer installable > in Debian sid. I assume this will require packaging a new upstream > release to suppor

[DRE-maint] Bug#1025220: passenger: Passenger startup fails with nodejs applications using node versions later than 14.x

Control: tags -1 + patch On Tue, Dec 13, 2022 at 09:32:12PM +, Cool Fire wrote: > Hello, > > On Tue, 13 Dec 2022 09:54:05 -0300 Antonio Terceiro > wrote: > > Please note that supporting nodejs from outside of the debian archive is > > not a priority. > >

[DRE-maint] Bug#1025220: passenger: Passenger startup fails with nodejs applications using node versions later than 14.x

Hi, On Thu, Dec 01, 2022 at 06:59:05AM +, Cool Fire wrote: > Some additional digging findings; > > - Testing and Unstable packages are not affected as they are built from the > upstream passenger 6.x branch, which already includes this fix. > - Stable package is not affected when using the no

Re: [DRE-maint] Comments regarding ruby-oedipus-lex_2.6.0-1_amd64.changes

On Sat, Dec 10, 2022 at 12:28:56AM -0300, Lucas Kanashiro wrote: > Hi Scott, > > Em 09/12/2022 17:29, Scott Kitterman escreveu: > > I took a quick look at this package. > > > > One comment: > > > > You should put the exact copyright claim in debian/copyright: > > > > Ryan Davis, seattle.rb >

[DRE-maint] Bug#1024652: ruby3.0: Segmentation fault from irb when performing a simple multiplication

On Wed, Dec 07, 2022 at 09:36:26AM -0600, Gunnar Wolf wrote: > Bernhard Übelacker dijo [Wed, Dec 07, 2022 at 03:14:40PM +0100]: > > Dear Gunnar, > > I tried to collect some more information for the Maintainer. > > Thanks! > > > First I need to create a .irbrc with the USE_SINGLELINE > > set to tr

[DRE-maint] Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)

Hi, On Fri, Oct 07, 2022 at 01:50:56AM +0300, Adrian Bunk wrote: > On Mon, Sep 12, 2022 at 08:24:43PM -0300, Antonio Terceiro wrote: > > Source: ruby-ahoy-email > > Version: 1.1.1-2 > > Severity: serious > > Justification: FTBFS > > Tags: bookworm sid ftbfs >

[DRE-maint] Bug#1020435: ruby-prof: FTBFS on ppc64el

Control: tag -1 + unreproducible Control: severity -1 important Hi, On Wed, Sep 21, 2022 at 07:20:31PM +0200, Sebastian Ramacher wrote: > Source: ruby-prof > Version: 1.4.3-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Deb

[DRE-maint] Bug#1020580: FTBFS: ruby3.1 needs network/DNS during tests

On Fri, Sep 23, 2022 at 06:37:02PM +0200, Sven Mueller wrote: > Package: ruby3.1 > Version: 3.1.2-3 > > The package violates policy 4.9, namely: > > For packages in the main archive, required targets must not attempt > network access, except, via the loopback interface, to services on the > build

[DRE-maint] Bug#1019684: yard: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: require "gettext/mo"

Source: yard Version: 0.9.27-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild yard with ruby3.1 enabled, the build failed. Relevant part o

[DRE-maint] Bug#1019683: test-kitchen: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: "#".

Source: test-kitchen Version: 1.23.2-6 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild test-kitchen with ruby3.1 enabled, the build failed.

[DRE-maint] Bug#1019681: samizdat: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: samizdat Version: 0.7.1-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild samizdat with ruby3.1 enabled, the build failed. Relevant

[DRE-maint] Bug#1019682: schleuder: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(error).to be_empty

Source: schleuder Version: 4.0.3-4 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild schleuder with ruby3.1 enabled, the build failed. Releva

[DRE-maint] Bug#1019680: ruby-zeitwerk: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: LoadError: cannot load such file -- /<>/test/tmp/foo.rb

Source: ruby-zeitwerk Version: 2.4.2-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-zeitwerk with ruby3.1 enabled, the build failed.

[DRE-maint] Bug#1019679: ruby-yaml-db: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error:

Source: ruby-yaml-db Version: 0.7.0-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-yaml-db with ruby3.1 enabled, the build failed.

[DRE-maint] Bug#1019678: ruby-websocket: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(handshake.to_s).to eql(client_request)

Source: ruby-websocket Version: 1.2.9-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-websocket with ruby3.1 enabled, the build faile

[DRE-maint] Bug#1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Expected \"not a hash, really\" to respond to #to_hash", got #

Source: ruby-virtus Version: 1.0.5-3.1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-virtus with ruby3.1 enabled, the build failed.

[DRE-maint] Bug#1019677: ruby-webpacker: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-webpacker Version: 5.4.3-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-webpacker with ruby3.1 enabled, the build faile

[DRE-maint] Bug#1019675: ruby-versionomy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-versionomy Version: 0.5.0-2.1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-versionomy with ruby3.1 enabled, the build f

[DRE-maint] Bug#1019672: ruby-uglifier: FTBFS with ruby3.1: make[1]: *** [debian/rules:15: override_dh_auto_install] Error 25

Source: ruby-uglifier Version: 4.2.0+dfsg-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-uglifier with ruby3.1 enabled, the build fa

[DRE-maint] Bug#1019674: ruby-vcr: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: test failures

Source: ruby-vcr Version: 6.0.0+really5.0.0-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-vcr with ruby3.1 enabled, the build faile

[DRE-maint] Bug#1019673: ruby-uniform-notifier: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: require 'ruby-growl'

Source: ruby-uniform-notifier Version: 1.13.0-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-uniform-notifier with ruby3.1 enabled,

[DRE-maint] Bug#1019671: ruby-test-spec: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-test-spec Version: 0.10.0-3.1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-test-spec with ruby3.1 enabled, the build fa

[DRE-maint] Bug#1019670: ruby-sprite-factory: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: no image files found

Source: ruby-sprite-factory Version: 1.7.1-4 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-sprite-factory with ruby3.1 enabled, the b

[DRE-maint] Bug#1019668: ruby-sixarm-ruby-unaccent: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in `start': coverag

Source: ruby-sixarm-ruby-unaccent Version: 1.2.0-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-sixarm-ruby-unaccent with ruby3.1 en

[DRE-maint] Bug#1019667: ruby-sinatra: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- wlang: skipping wlang tests

Source: ruby-sinatra Version: 2.2.2-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-sinatra with ruby3.1 enabled, the build failed.

[DRE-maint] Bug#1019669: ruby-slim: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/testtask.rb:130:in `block (3 levels) in define': Command failed

Source: ruby-slim Version: 4.1.0-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-slim with ruby3.1 enabled, the build failed. Releva

[DRE-maint] Bug#1019666: ruby-simplecov: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(@stderr).to be_empty

Source: ruby-simplecov Version: 0.21.2-1.1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-simplecov with ruby3.1 enabled, the build fa

[DRE-maint] Bug#1019665: ruby-safe-yaml: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError:

Source: ruby-safe-yaml Version: 1.0.5-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-safe-yaml with ruby3.1 enabled, the build faile

[DRE-maint] Bug#1019663: ruby-ronn: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-ronn Version: 0.9.1-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-ronn with ruby3.1 enabled, the build failed. Releva

[DRE-maint] Bug#1019664: ruby-rspec: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise failure }

Source: ruby-rspec Version: 3.10.0c1e1m2s3-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-rspec with ruby3.1 enabled, the build fail

[DRE-maint] Bug#1019662: ruby-riddle: FTBFS: mysql server fails to start

Source: ruby-riddle Version: 2.4.2-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-riddle with ruby3.1 enabled, the build failed. Thi

[DRE-maint] Bug#1019652: ruby-regexp-parser: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(result[1]).to eq token

Source: ruby-regexp-parser Version: 2.1.1-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-regexp-parser with ruby3.1 enabled, the bui

[DRE-maint] Bug#1019650: ruby-rantly: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in `start': coverage measurement

Source: ruby-rantly Version: 2.0.0-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-rantly with ruby3.1 enabled, the build failed. Re

[DRE-maint] Bug#1019649: ruby-rabl: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: rm: cannot remove 'Gemfile.lock': No such file or directory

Source: ruby-rabl Version: 0.15.0-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-rabl with ruby3.1 enabled, the build failed. Relev

[DRE-maint] Bug#1019647: ruby-power-assert: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-power-assert Version: 1.1.7-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-power-assert with ruby3.1 enabled, the build

[DRE-maint] Bug#1019648: ruby-premailer-rails: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

Source: ruby-premailer-rails Version: 1.10.3-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-premailer-rails with ruby3.1 enabled, th

[DRE-maint] Bug#1019646: ruby-parallel: FTBFS: fails randomly

Source: ruby-parallel Version: 1.22.1-1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-parallel with ruby3.1 enabled, the build failed

[DRE-maint] Bug#1019645: ruby-otr-activerecord: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError:

Source: ruby-otr-activerecord Version: 2.0.3-3 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-otr-activerecord with ruby3.1 enabled, t

  1   2   3   4   5   >