Your message dated Tue, 1 Mar 2016 22:31:42 +0100
with message-id <20160301213142.GA26956@esfahan>
and subject line transient bug while waiting binNMU for ruby-sqlite3
has caused the Debian Bug report #816120,
regarding ruby-default-value-for: FTBFS: Specified 'sqlite3' for database
adapter, but the gem is not loaded
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.)
--
816120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-default-value-for
Version: 3.0.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
ruby-default-value-for fails to build from source in unstable/amd64:
[..]
RUBYLIB=/home/lamby/temp/cdt.20160227182753.jixeRidhmm/ruby-default-value-for-3.0.1/debian/ruby-default-value-for/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-default-value-for/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 test.rb
/usr/lib/ruby/vendor_ruby/active_record/connection_adapters/connection_specification.rb:177:in
`rescue in spec': Specified 'sqlite3' for database adapter, but the gem is not
loaded. Add `gem 'sqlite3'` to your Gemfile (and ensure its version is at the
minimum required by ActiveRecord). (Gem::LoadError)
from
/usr/lib/ruby/vendor_ruby/active_record/connection_adapters/connection_specification.rb:174:in
`spec'
from
/usr/lib/ruby/vendor_ruby/active_record/connection_handling.rb:50:in
`establish_connection'
from test.rb:43:in `<main>'
Testing with Active Record version 4.2.5.1
rake aborted!
Command failed with status (1): [/usr/bin/ruby2.3 test.rb...]
/home/lamby/temp/cdt.20160227182753.jixeRidhmm/ruby-default-value-for-3.0.1/debian/ruby-tests.rake:5:in
`block in <top (required)>'
Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install
/home/lamby/temp/cdt.20160227182753.jixeRidhmm/ruby-default-value-for-3.0.1/debian/ruby-default-value-for
returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
[..]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
ruby-default-value-for.3.0.1-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Control: notfound -1 3.0.1-1
Hi,
The bug occured during the short period between activation of build/test
runs for ruby2.3 and binNMUs for packages with native extensions.
ruby-sqlite3 has now an extension for ruby2.3, and the package builds
fine in a clean chroot.
I am thus closing this bug.
Cheers,
Cédric
signature.asc
Description: PGP signature
--- End Message ---
