Your message dated Mon, 23 Nov 2020 17:03:50 -0300
with message-id <[email protected]>
and subject line Re: Bug#975088: ruby-defaults breaks rails autopkgtest: Could
not find gem 'bootsnap (>= 1.4.2)'
has caused the Debian Bug report #975088,
regarding ruby-defaults breaks rails autopkgtest: Could not find gem 'bootsnap
(>= 1.4.2)'
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 [email protected]
immediately.)
--
975088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975088
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-defaults, rails
Control: found -1 ruby-defaults/1:2.7+2
Control: found -1 rails/2:6.0.3.4+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: [email protected]
User: [email protected]
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of ruby-defaults the autopkgtest of rails fails in
testing when that autopkgtest is run with the binary packages of
ruby-defaults from unstable. It passes when run with only packages from
testing. In tabular form:
pass fail
ruby-defaults from testing 1:2.7+2
rails from testing 2:6.0.3.4+dfsg-1
all others from testing from testing
I copied some of the output at the bottom of this report. Is this a
(test-)dependency that used to be pulled in?
Currently this regression is blocking the migration of ruby-defaults to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=ruby-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rails/8252966/log.gz
+ rails runner puts "Empty Rails %s app booted correctly" % Rails.version
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:313:in
`block in verify_gemfile_dependencies_are_found!': Could not find gem
'bootsnap (>= 1.4.2)' in any of the gem sources listed in your Gemfile.
(Bundler::GemNotFound)
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:281:in
`each'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:281:in
`verify_gemfile_dependencies_are_found!'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:49:in
`start'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:22:in
`resolve'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:264:in
`resolve'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:175:in
`specs'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:243:in
`specs_for'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:231:in
`requested_specs'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:91:in
`block in definition_method'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:20:in
`setup'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler.rb:149:in
`setup'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/setup.rb:20:in
`block in <top (required)>'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.rb:136:in
`with_level'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.rb:88:in
`silence'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/setup.rb:20:in
`<top (required)>'
from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:83:in
`require'
from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:83:in
`require'
from
/tmp/autopkgtest-lxc.nyo0q9u_/downtmp/autopkgtest_tmp/foo/config/boot.rb:3:in
`<top (required)>'
from bin/rails:3:in `require_relative'
from bin/rails:3:in `<main>'
autopkgtest [12:12:20]: test newapp: -----------------------]
autopkgtest [12:12:21]: test newapp: - - - - - - - - - - results - - -
- - - - - - -
newapp FAIL non-zero exit status 1
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Wed, Nov 18, 2020 at 09:28:55PM +0100, Paul Gevers wrote:
> Source: ruby-defaults, rails
> Control: found -1 ruby-defaults/1:2.7+2
> Control: found -1 rails/2:6.0.3.4+dfsg-1
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: [email protected]
> User: [email protected]
> Usertags: breaks needs-update
>
> Dear maintainer(s),
>
> With a recent upload of ruby-defaults the autopkgtest of rails fails in
> testing when that autopkgtest is run with the binary packages of
> ruby-defaults from unstable. It passes when run with only packages from
> testing. In tabular form:
>
> pass fail
> ruby-defaults from testing 1:2.7+2
> rails from testing 2:6.0.3.4+dfsg-1
> all others from testing from testing
>
> I copied some of the output at the bottom of this report. Is this a
> (test-)dependency that used to be pulled in?
>
> Currently this regression is blocking the migration of ruby-defaults to
> testing [1]. Due to the nature of this issue, I filed this bug report
> against both packages. Can you please investigate the situation and
> reassign the bug to the right package?
>
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
>
> Paul
>
> [1] https://qa.debian.org/excuses.php?package=ruby-defaults
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/r/rails/8252966/log.gz
>
> + rails runner puts "Empty Rails %s app booted correctly" % Rails.version
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:313:in
> `block in verify_gemfile_dependencies_are_found!': Could not find gem
> 'bootsnap (>= 1.4.2)' in any of the gem sources listed in your Gemfile.
> (Bundler::GemNotFound)
This was due to the first ruby-bootsnap binNMU (requested in #973444)
failing on the buildd because another package needed to be binNMU first.
I have back that binNMU, and now with ruby-bootsnap 1.4.6-1+b2, this no
longer fails.
signature.asc
Description: PGP signature
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
