Your message dated Mon, 17 Mar 2014 00:30:17 +0100
with message-id <20140316233017.GB31371@spin>
and subject line fixed by the upload of ruby-fakeweb/1.3.0+dfsg1-3
has caused the Debian Bug report #741760,
regarding ruby-fakeweb: FTBFS: ERROR: Test "ruby1.9.1" failed: NoMethodError: 
undefined method `any_instance' for URI::Parser:Class
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.)


-- 
741760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-fakeweb
Version: 1.3.0+dfsg1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140315 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> NoMethodError: undefined method `any_instance' for URI::Parser:Class
>     /«BUILDDIR»/ruby-fakeweb-1.3.0+dfsg1/test/test_utility.rb:78:in 
> `test_uri_escape_delegates_to_uri_parser_when_available'
> 
> 187 tests, 295 assertions, 0 failures, 12 errors, 0 skips
> ERROR: Test "ruby1.9.1" failed: 

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/03/15/ruby-fakeweb_1.3.0+dfsg1-2_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
fixed 741760 ruby-fakeweb/1.3.0+dfsg1-3
thanks

Hi!

This bug was fixed by the upload of version 1.3.0+dfsg1-3 of
ruby-fakeweb. The bug number was wrong in the changelog entry though.
It will be corrected in the next upload.

Cheers,

Cédric

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to