Your message dated Wed, 17 May 2017 05:51:11 +0000
with message-id <e1darrb-000gtf...@fasolo.debian.org>
and subject line Bug#862539: Removed package(s) from unstable
has caused the Debian Bug report #822506,
regarding ruby-bluecloth: FTBFS: `split': invalid byte sequence in US-ASCII 
(ArgumentError)
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.)


-- 
822506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-bluecloth
Version: 2.2.0-6
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> /usr/lib/ruby/vendor_ruby/rspec/core/source.rb:23:in `split': invalid byte 
> sequence in US-ASCII (ArgumentError)
>       from /usr/lib/ruby/vendor_ruby/rspec/core/source.rb:23:in `lines'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/snippet_extractor.rb:50:in 
> `expression_lines'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/snippet_extractor.rb:33:in 
> `extract_expression_lines_at'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:209:in 
> `read_failed_lines'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:160:in 
> `failure_slash_error_lines'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:147:in 
> `block in failure_lines'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:146:in 
> `tap'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:146:in 
> `failure_lines'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:32:in 
> `colorized_message_lines'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:231:in 
> `formatted_message_and_backtrace'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:84:in 
> `fully_formatted_lines'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/exception_presenter.rb:76:in 
> `fully_formatted'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/notifications.rb:200:in 
> `fully_formatted'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/notifications.rb:114:in 
> `block in fully_formatted_failed_examples'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/notifications.rb:113:in `each'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/notifications.rb:113:in 
> `each_with_index'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/notifications.rb:113:in 
> `fully_formatted_failed_examples'
>       from 
> /usr/lib/ruby/vendor_ruby/rspec/core/formatters/base_text_formatter.rb:33:in 
> `dump_failures'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:189:in `block in 
> notify'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:188:in `each'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:188:in `notify'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:160:in `block in 
> finish'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:175:in 
> `close_after'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:156:in `finish'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:79:in `report'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:117:in `run_specs'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:93:in `run'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:78:in `run'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:38:in 
> `perform_at_exit'
>       from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:24:in `block in 
> autorun'
> ERROR: Test "ruby2.3" failed. Exiting.
> dh_auto_install: dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-bluecloth 
> returned exit code 1
> debian/rules:18: recipe for target 'binary' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

--- End Message ---
--- Begin Message ---
Version: 2.2.0-6+rm

Dear submitter,

as the package ruby-bluecloth has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/862539

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

Reply via email to