Your message dated Fri, 23 Dec 2022 14:36:05 +0530
with message-id <20221223090605.5ykiaiq7seqol...@nileshpatra.info>
and subject line Re: Bug#1019610: ruby-ahoy-email: FTBFS with ruby3.1: ERROR: 
Test "ruby3.1" failed: cannot load such file -- net/smtp (LoadError)
has caused the Debian Bug report #1019610,
regarding ruby-ahoy-email: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 
cannot load such file -- net/smtp (LoadError)
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.)


-- 
1019610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 failed.

Relevant part of the build log (hopefully):
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `require': cannot load such file -- net/smtp (LoadError)
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `block in require'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in
>  `load_dependency'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `require'
>       from /usr/lib/ruby/vendor_ruby/mail.rb:9:in `<module:Mail>'
>       from /usr/lib/ruby/vendor_ruby/mail.rb:3:in `<top (required)>'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `require'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `block in require'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in
>  `load_dependency'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `require'
>       from 
> /usr/share/rubygems-integration/all/gems/actionmailer-6.1.6.1/lib/action_mailer/mail_with_error_handling.rb:4:in
>  `<top (required)>'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `require'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `block in require'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in
>  `load_dependency'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `require'
>       from 
> /usr/share/rubygems-integration/all/gems/actionmailer-6.1.6.1/lib/action_mailer/base.rb:3:in
>  `<top (required)>'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `require'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `block in require'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:299:in
>  `load_dependency'
>       from 
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/dependencies.rb:332:in
>  `require'
>       from /<<PKGBUILDDIR>>/test/test_helper.rb:21:in `<top (required)>'
>       from /<<PKGBUILDDIR>>/test/click_test.rb:1:in `require_relative'
>       from /<<PKGBUILDDIR>>/test/click_test.rb:1:in `<top (required)>'
>       from 
> <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:85:in
>  `require'
>       from 
> <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:85:in
>  `require'
>       from 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in 
> `block in <main>'
>       from 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in 
> `select'
>       from 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in 
> `<main>'
> rake aborted!
> Command failed with status (1)
> 
> Tasks: TOP => default => test
> (See full trace by running task with --trace)
> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-ahoy-email/ruby-ahoy-email_1.1.1-2+rebuild1663007340_amd64-2022-09-12T18:29:01Z.build

To reproduce this, you need ruby-all-dev >= 1:3.0+2.  Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or ir the
transition has alraedy started in unstable, a normal build on unstable should
do it.  If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Version: 2:6.1.7+dfsg-3

This is fixed after rails update, clsoing.

On Sun, 20 Nov 2022 00:19:44 +0200 Adrian Bunk <b...@debian.org> wrote:
> I am reassigning this to rails since it is likely that the problem is there.

-- 
Best,
Nilesh

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to