Your message dated Mon, 11 Jan 2016 18:20:39 +0000
with message-id <e1aih55-0005uq...@franck.debian.org>
and subject line Bug#798538: fixed in ruby-rest-client 1.8.0-2
has caused the Debian Bug report #798538,
regarding ruby-rest-client fails the tests in unstable
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.)


-- 
798538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-rest-client
Version: 1.8.0-1
Severity: serious
Tags: sid stretch

fails the tests in unstable with:

Failures:

  1) RestClient::Request closes payload if not nil
     Failure/Error: test_file.closed?.should be_true
       expected true to respond to `true?` or perhaps you meant `be true` or
`be_truthy`
     # ./spec/unit/request2_spec.rb:29:in `block (2 levels) in <top (required)>'

  2) RestClient::Request proxy creates a non-proxy class if a proxy url is not 
given
     Failure/Error: @request.net_http_class.proxy_class?.should be_false
       expected false to respond to `false?` or perhaps you meant `be false` or
`be_falsey`
     # ./spec/unit/request_spec.rb:364:in `block (3 levels) in <top (required)>'

  3) RestClient::Request proxy creates a proxy class if a proxy url is given
     Failure/Error: @request.net_http_class.proxy_class?.should be_true
       expected true to respond to `true?` or perhaps you meant `be true` or
`be_truthy`
     # ./spec/unit/request_spec.rb:360:in `block (3 levels) in <top (required)>'

Deprecation Warnings:

Using `should` from rspec-expectations' old `:should` syntax without explicitly
enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly
enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }`
instead. Called from
/home/packages/tmp/ruby-rest-client-1.8.0/spec/unit/response_spec.rb:22:in
`block (2 levels) in <top (required)>'.

Using `stub` from rspec-mocks' old `:should` syntax without explicitly enabling
the syntax is deprecated. Use the new `:expect` syntax or explicitly enable
`:should` instead. Called from
/home/packages/tmp/ruby-rest-client-1.8.0/spec/unit/request_spec.rb:8:in `block
(2 levels) in <top (required)>'.


If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.

2 deprecation warnings total

Finished in 11.1 seconds (files took 0.80213 seconds to load)

--- End Message ---
--- Begin Message ---
Source: ruby-rest-client
Source-Version: 1.8.0-2

We believe that the bug you reported is fixed in the latest version of
ruby-rest-client, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 798...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Balasankar C <balasank...@autistici.org> (supplier of updated ruby-rest-client 
package)

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


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 11 Jan 2016 23:02:23 +0530
Source: ruby-rest-client
Binary: ruby-rest-client
Architecture: source all
Version: 1.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Balasankar C <balasank...@autistici.org>
Description:
 ruby-rest-client - simple REST client for Ruby
Closes: 798538
Changes:
 ruby-rest-client (1.8.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Port tests to support RSpec3 syntax (Closes: #798538)
     - Add port-tests-rspec3.patch
   * Bump debhelper compatibility
Checksums-Sha1:
 91476c6a3f251bc44c4d134c3084bf83ab59faa9 2248 ruby-rest-client_1.8.0-2.dsc
 78c84ff679d509fea39ccd56b02f42c3369f7a1f 16276 
ruby-rest-client_1.8.0-2.debian.tar.xz
 2efdf790e757d6740ae5fb4527a505a8cd950798 29556 ruby-rest-client_1.8.0-2_all.deb
Checksums-Sha256:
 e3e400e97db552b5a6b6754e397df8c0e2b72f9da3d0377fdada80684a39944b 2248 
ruby-rest-client_1.8.0-2.dsc
 4b29c8c65a95142a74024354517f02c4782e25caeba0855c9abd31857b92581a 16276 
ruby-rest-client_1.8.0-2.debian.tar.xz
 9e6ba8446fbd3ed0c793874b0a9177c6b800c788eacc2374005460002d5b0010 29556 
ruby-rest-client_1.8.0-2_all.deb
Files:
 c4a80eab7843dd4f3fc155714ca74dae 2248 ruby optional 
ruby-rest-client_1.8.0-2.dsc
 f9c2970628360c4b6d7ce8e74d75c99c 16276 ruby optional 
ruby-rest-client_1.8.0-2.debian.tar.xz
 b2d8ae08695fbf6757ca611cb4ce1d43 29556 ruby optional 
ruby-rest-client_1.8.0-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJWk+sDAAoJEM4fnGdFEsIqJW0QAJv/LdhXeeVMV8/84VoEWa4X
kaP8MWZB7mZx6LCrpeahZImeEyb+D3EANIhgaM60XSmsOlngHxtzm3buYaKYWOaT
s4VbU0g+uYvnwdLrH6/6NOGVM+9AvKjj6sVTsQaIiW05iF5DPqMEG5/WMehpqQRd
rQMADaPn0CSuTkiQeJ9nReJQbU8om3wBY3aCSefYNzRbQltTfahQHGs8n/htlxCp
g8zjQcCI2rurSrB2ntj2bxaJKohDXs8ysWYxvYQewv1o/gD5+9Z+dQegsTdBPKd8
sbM40EARYqBM8he/6ounClblftx7bSO8xY6YIM4iI6hcDvIXZ0vgTQxDL115ZtXj
j5ERZVh+uG1XG1MSdZ7oDAYaI99CdIgJR2pzODlxDbz/Dokn/8qO/ob8KShw1Rf5
PGWromxHcXLROg3eeGU0v7Ifdx995ZElFQCtRzZ5MowmutwoviUyUONk6s1SgdEF
SyHjdNsIt60IoFrNcUY1TE1Y/89aU0NM5gcrVHvpBPWrN2q91qDyigKAfuvpzjHv
t2KC3aHZaBRivZDzLPs02Z442TxD5sGUumqVNNbg0iQ/dQa0vMlMOpX3DY9EZPn8
3t95ojzJJHXnnjYXZguxT8/b49ILQHa3iEStWybRhxcX2tm2APEtjv/zc6cYdagZ
Xj5GMWdITPyPrLossLva
=IV9L
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to