Your message dated Thu, 10 Apr 2014 21:22:29 +0200
with message-id <20140410192227.GA21056@spin>
and subject line fixed in ruby-dataobjects-mysql/0.10.14-1
has caused the Debian Bug report #743980,
regarding FTBFS: DataObjects::Mysql::Connection it should behave like a 
Connection with authentication support ...
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.)


-- 
743980: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-dataobjects-mysql
Version: 0.10.13-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

In a test rebuild your package failed to build from source, with this output:

Failures:

  1) DataObjects::Mysql::Connection it should behave like a Connection with 
authentication support with an invalid URI should raise an error with a 
meaningless URI
     Failure/Error: connecting_with("#{@driver}://peekaboo$2!@#4543").should 
raise_error(Addressable::URI::InvalidURIError)
       expected Addressable::URI::InvalidURIError, got 
#<DataObjects::ConnectionError: Access denied for user 
'peekaboo$2!'@'localhost' (using password: NO) (code: 1045, sql state: 28000, 
query: , uri: )> with backtrace:
         # /usr/lib/ruby/vendor_ruby/data_objects/connection.rb:79:in 
`initialize'
         # /usr/lib/ruby/vendor_ruby/data_objects/connection.rb:79:in `new'
         # /usr/lib/ruby/vendor_ruby/data_objects/pooling.rb:181:in `block in 
new'
         # /usr/lib/ruby/vendor_ruby/data_objects/pooling.rb:176:in 
`synchronize'
         # /usr/lib/ruby/vendor_ruby/data_objects/pooling.rb:176:in `new'
         # /usr/lib/ruby/vendor_ruby/data_objects/pooling.rb:121:in `new'
         # /usr/lib/ruby/vendor_ruby/data_objects/connection.rb:68:in `new'
         # 
/usr/lib/ruby/vendor_ruby/data_objects/spec/shared/connection_spec.rb:113:in 
`block in connecting_with'
         # 
/usr/lib/ruby/vendor_ruby/rspec/matchers/built_in/raise_error.rb:36:in `call'
         # 
/usr/lib/ruby/vendor_ruby/rspec/matchers/built_in/raise_error.rb:36:in 
`matches?'
         # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:24:in 
`handle_matcher'
         # /usr/lib/ruby/vendor_ruby/rspec/expectations/syntax.rb:53:in `should'
         # 
/usr/lib/ruby/vendor_ruby/data_objects/spec/shared/connection_spec.rb:133:in 
`block (3 levels) in <top (required)>'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:114:in 
`instance_eval'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:114:in `block in run'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in 
`with_around_each_hooks'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:111:in `run'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:390:in `block 
in run_examples'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:386:in `map'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:386:in 
`run_examples'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:371:in `run'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `block 
in run'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `map'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `run'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `block 
in run'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `map'
         # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:372:in `run'
         # /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:28:in `block (2 
levels) in run'
         # /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:28:in `map'
         # /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:28:in `block in 
run'
         # /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:58:in `report'
         # /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:25:in `run'
         # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:80:in `run'
         # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:17:in `block in 
autorun'
     Shared Example Group: "a Connection with authentication support" called 
from ./spec/connection_spec.rb:20

Finished in 0.39874 seconds
77 examples, 1 failure, 1 pending

Failed examples:

rspec /usr/lib/ruby/vendor_ruby/data_objects/spec/shared/connection_spec.rb:132 
# DataObjects::Mysql::Connection it should behave like a Connection with 
authentication support with an invalid URI should raise an error with a 
meaningless URI
/usr/bin/ruby2.0 -S rspec ./spec/command_spec.rb ./spec/connection_spec.rb 
./spec/encoding_spec.rb ./spec/reader_spec.rb ./spec/result_spec.rb failed
ERROR: Test "ruby2.0" failed. Exiting.

--- End Message ---
--- Begin Message ---
fixed 743980 ruby-dataobjects-mysql/0.10.14-1
thanks

Hi!

This bug was fixed by the upload of 0.10.14-1 (more precisely, that of
ruby-dataobjects, which does not ship the failing test anymore).
I forgot to close the bug in the changelog. Doing it now.

Cheers,

Cédric

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to