[DRE-maint] ruby-omniauth-ldap 2.2.0-1 MIGRATED to testing

FYI: The status of the ruby-omniauth-ldap source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 2.2.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a

[DRE-maint] ruby-mechanize 2.7.7-3 MIGRATED to testing

FYI: The status of the ruby-mechanize source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 2.7.7-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day

[DRE-maint] ruby-sham-rack 1.4.1-3 MIGRATED to testing

FYI: The status of the ruby-sham-rack source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1.4.1-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day

[DRE-maint] ruby-ntlm 0.6.3-2 MIGRATED to testing

FYI: The status of the ruby-ntlm source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0.6.3-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you w

[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

[DRE-maint] Bug#1019644: ruby-omniauth-openid-connect: 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': cove

Source: ruby-omniauth-openid-connect Version: 0.10.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-omniauth-openid-connect with rub

[DRE-maint] Bug#1019643: ruby-omniauth-oauth2-generic: FTBFS with ruby3.1: ERROR: Test "ruby3.0" failed: Failure/Error: expect(last_response.headers["Location"]).to match(%r{redirect_uri=https%3A%2F%2

Source: ruby-omniauth-oauth2-generic Version: 0.2.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-omniauth-oauth2-generic with ru

[DRE-maint] Bug#1019640: ruby-mono-logger: 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 measure

Source: ruby-mono-logger Version: 1.1.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-mono-logger with ruby3.1 enabled, the build f

[DRE-maint] Bug#1019641: ruby-omniauth-auth0: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: expect(last_response.status).to eq(302)

Source: ruby-omniauth-auth0 Version: 2.0.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-omniauth-auth0 with ruby3.1 enabled, the b

[DRE-maint] Bug#1019642: ruby-omniauth-kerberos: FTBFS with ruby3.1: ERROR: Test "ruby3.0" failed: NoMethodError:

Source: ruby-omniauth-kerberos Version: 0.3.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-omniauth-kerberos with ruby3.1 enable

[DRE-maint] Bug#1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is memoized')

Source: ruby-memoizable Version: 0.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-memoizable with ruby3.1 enabled, the build fai

[DRE-maint] Bug#1019639: ruby-minitest-hooks: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-minitest-hooks Version: 1.5.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-minitest-hooks with ruby3.1 enabled, the b

[DRE-maint] Bug#1019638: ruby-memory-profiler: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-memory-profiler Version: 0.9.14-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-memory-profiler with ruby3.1 enabled, th

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

Source: ruby-mechanize Version: 2.7.7-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-mechanize with ruby3.1 enabled, the build faile

[DRE-maint] Bug#1019635: ruby-mail: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Can not decode an entire message, try calling #decoded on the various fields and body

Source: ruby-mail Version: 2.7.1+dfsg1-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-mail with ruby3.1 enabled, the build failed.

[DRE-maint] Bug#1019634: ruby-jekyll-remote-theme: FTBFS: ERROR: Test "ruby3.0" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could no

Source: ruby-jekyll-remote-theme Version: 0.4.3-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-jekyll-remote-theme with ruby3.1 enab

[DRE-maint] Bug#1019633: ruby-invisible-captcha: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp

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, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-invisible-captcha with ruby3.1 enabled,

[DRE-maint] Bug#1019632: ruby-ice-cube: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(YAML.load(symbol_yaml)).to eq(YAML.load(string_yaml))

Source: ruby-ice-cube Version: 0.16.4-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-ice-cube with ruby3.1 enabled, the build failed

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

Source: ruby-hoe Version: 3.22.1+dfsg1-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-hoe with ruby3.1 enabled, the build failed. R

[DRE-maint] Bug#1019631: ruby-httparty: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

Source: ruby-httparty Version: 0.20.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-httparty with ruby3.1 enabled, the build failed

[DRE-maint] Bug#1019629: ruby-heapy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

Source: ruby-heapy Version: 0.2.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-heapy with ruby3.1 enabled, the build failed. Rele

[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 #

Source: ruby-hashie Version: 3.5.5-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-hashie with ruby3.1 enabled, the build failed. Re

[DRE-maint] Bug#1019626: ruby-grape-entity: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

Source: ruby-grape-entity Version: 0.10.1-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-grape-entity with ruby3.1 enabled, the buil

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

Source: ruby-graphviz Version: 1.2.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-graphviz with ruby3.1 enabled, the build failed.

[DRE-maint] Bug#1019623: ruby-fog-core: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-fog-core Version: 2.1.0-3.1 Severity: serious 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-fog-core with ruby3.1 enabled, the build failed.

[DRE-maint] Bug#1019622: ruby-factory-bot: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "undefined method 'static_attributes_are_gone' in 'broken' factory\nDid you mea

Source: ruby-factory-bot Version: 6.2.0-2 Severity: serious 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-factory-bot with ruby3.1 enabled, the build fai

[DRE-maint] Bug#1019621: ruby-excon: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

Source: ruby-excon Version: 0.88.0-1 Severity: serious 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-excon with ruby3.1 enabled, the build failed. Relev

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

Source: ruby-enumerize Version: 2.4.0-1 Severity: serious 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-enumerize with ruby3.1 enabled, the build failed.

[DRE-maint] Bug#1019618: ruby-delayed-job: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error:

Source: ruby-delayed-job Version: 4.1.9-1 Severity: serious 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-delayed-job with ruby3.1 enabled, the build fai

[DRE-maint] Bug#1019619: ruby-did-you-mean: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-did-you-mean Version: 1.2.1-1 Severity: serious 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-did-you-mean with ruby3.1 enabled, the build f

[DRE-maint] Bug#1019617: ruby-delayed-job-active-record: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error:

Source: ruby-delayed-job-active-record Version: 4.1.6-3 Severity: serious 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-delayed-job-active-record with ru

[DRE-maint] Bug#1019616: ruby-dalli: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: adduser: Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory

Source: ruby-dalli Version: 3.0.6-1 Severity: serious 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-dalli with ruby3.1 enabled, the build failed. Releva

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

Source: ruby-crack Version: 0.4.4-2 Severity: serious 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-crack with ruby3.1 enabled, the build failed. Releva

[DRE-maint] Bug#1019614: ruby-celluloid: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected Timeout::Error, got #

Source: ruby-celluloid Version: 0.17.3-1 Severity: serious 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-celluloid with ruby3.1 enabled, the build failed

[DRE-maint] Bug#1019613: ruby-capybara: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: raise LoadError, 'Capybara is unable to load `puma` for its server, please add `puma` to your p

Source: ruby-capybara Version: 3.36.0+ds-2 Severity: serious 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-capybara with ruby3.1 enabled, the build faile

[DRE-maint] Bug#1019611: ruby-asset-sync: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: @yml ||= ::YAML.load(::ERB.new(IO.read(yml_path)).result)[::Rails.env] || {}

Source: ruby-asset-sync Version: 2.11.0-1 Severity: serious 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-asset-sync with ruby3.1 enabled, the build fail

[DRE-maint] Processed: severity of 1016541 is serious

Processing commands for cont...@bugs.debian.org: > severity 1016541 serious Bug #1016541 [src:ruby-aruba] ruby-aruba: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assist

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

Source: ruby-ahoy-email Version: 1.1.1-2 Severity: serious 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-ahoy-email with ruby3.1 enabled, the build faile

[DRE-maint] Bug#1019609: ruby-activerecord-import: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.

Source: ruby-activerecord-import Version: 1.2.0-1 Severity: serious 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-activerecord-import with ruby3.1 enable

[DRE-maint] Bug#1019607: redmine: FTBFS with ruby3.1: Could not find gem 'rails (~> 6.1.4.6)' in cached gems or installed locally.

Source: redmine Version: 5.0.0-1 Severity: serious 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 redmine with ruby3.1 enabled, the build failed. Relevant par

[DRE-maint] Bug#1019608: rubocop: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 40.2) Failure/Error: expect($stderr.string).to eq('')

Source: rubocop Version: 0.89.1+dfsg-3 Severity: serious 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 rubocop with ruby3.1 enabled, the build failed. Releva

[DRE-maint] Bug#1019606: roodi: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: YAML.load_file config_file

Source: roodi Version: 5.0.0-4 Severity: serious 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 roodi with ruby3.1 enabled, the build failed. Relevant part of

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

Source: feed2imap Version: 1.3.1-1 Severity: serious 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 feed2imap with ruby3.1 enabled, the build failed. Relevant

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

Source: bsfilter Version: 1:1.0.19-3 Severity: serious 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 bsfilter with ruby3.1 enabled, the build failed. Relevan

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

Source: asciidoctor Version: 2.0.16-2 Severity: serious 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 asciidoctor with ruby3.1 enabled, the build failed. Rel

[DRE-maint] Processed: Starting ruby3.1 transition: important bugs now marked as serious

Processing commands for cont...@bugs.debian.org: > severity 1015305 serious Bug #1015305 [src:puma] puma: FTBFS: ERROR: Test "ruby3.1" failed. Severity set to 'serious' from 'important' > severity 1015309 serious Bug #1015309 [src:ruby-bson] ruby-bson: FTBFS: ERROR: Test "ruby3.1" failed: Failure

[DRE-maint] Bug#1015305: Starting ruby3.1 transition: important bugs now marked as serious

severity 1015305 serious severity 1015309 serious severity 1015310 serious severity 1015322 serious severity 1015327 serious severity 1015328 serious severity 1015329 serious severity 1015334 serious thanks Hi, We are about to start the ruby3.1 transition. I will coordinate this with the release

[DRE-maint] ruby-rack-oauth2_1.21.2-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Sep 2022 12:26:19 + Source: ruby-rack-oauth2 Architecture: source Version: 1.21.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Ravi Dwivedi Changes: ruby-rack-oauth2

[DRE-maint] rails_6.1.7+dfsg-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 Sep 2022 22:40:02 +0530 Source: rails Architecture: source Version: 2:6.1.7+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Utkarsh Gupta Changes: rails (2:6.1.7+dfsg-

[DRE-maint] Processing of rails_6.1.7+dfsg-1_source.changes

rails_6.1.7+dfsg-1_source.changes uploaded successfully to localhost along with the files: rails_6.1.7+dfsg-1.dsc rails_6.1.7+dfsg.orig.tar.xz rails_6.1.7+dfsg-1.debian.tar.xz rails_6.1.7+dfsg-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org

[DRE-maint] Processing of ruby-rack-oauth2_1.21.2-1_source.changes

ruby-rack-oauth2_1.21.2-1_source.changes uploaded successfully to localhost along with the files: ruby-rack-oauth2_1.21.2-1.dsc ruby-rack-oauth2_1.21.2.orig.tar.gz ruby-rack-oauth2_1.21.2-1.debian.tar.xz ruby-rack-oauth2_1.21.2-1_amd64.buildinfo Greetings, Your Debian queue daemon

[DRE-maint] Bug#1019238: redmine: confirmation of the problem

Package: redmine Version: 4.0.7-1~bpo10+1 Followup-For: Bug #1019238 Dear Maintainer, Hello, i can confirm the presence of this problem, it renders redmine unusable hth, Wim -- System Information: Debian Release: 10.13 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (