Your message dated Mon, 02 Jan 2023 14:43:00 +0000
with message-id <[email protected]>
and subject line Bug#1027078: fixed in ruby-jira 2.1.5-4
has caused the Debian Bug report #1027078,
regarding ruby-jira: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed:  
    Failure/Error: result.push(client.Issue.build(issue))
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 [email protected]
immediately.)


-- 
1027078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027078
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-jira
Version: 2.1.5-3
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: [email protected]
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-jira failed to build.

Relevant part of the build log (hopefully):
>      Failure/Error: result.push(client.Issue.build(issue))
> 
>        #<Double (anonymous)> received :build with unexpected arguments
>          expected: ({"id"=>"1", "summary"=>"Bugs Everywhere"}) (keyword 
> arguments)
>               got: ({"id"=>"1", "summary"=>"Bugs Everywhere"}) (options hash)
>      # ./lib/jira/resource/issue.rb:59:in `block (2 levels) in all'
>      # ./lib/jira/resource/issue.rb:58:in `map'
>      # ./lib/jira/resource/issue.rb:58:in `block in all'
>      # ./lib/jira/resource/issue.rb:53:in `loop'
>      # ./lib/jira/resource/issue.rb:53:in `all'
>      # ./spec/jira/resource/issue_spec.rb:52:in `block (2 levels) in <top 
> (required)>'
> 
> Deprecation Warnings:
> 
> The implicit block expectation syntax is deprecated, you should pass a block 
> rather than an argument to `expect` to use the provided block expectation 
> matcher or the matcher must implement `supports_value_expectations?`. e.g  
> `expect { value }.to raise ArgumentError with "Required option :deadbeef 
> missing"` not `expect(value).to raise ArgumentError with "Required option 
> :deadbeef missing"`
> 
> The implicit block expectation syntax is deprecated, you should pass a block 
> rather than an argument to `expect` to use the provided block expectation 
> matcher or the matcher must implement `supports_value_expectations?`. e.g  
> `expect { value }.to raise JIRA::HTTPError` not `expect(value).to raise 
> JIRA::HTTPError`
> 
> 
> 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 0.14389 seconds (files took 0.80057 seconds to load)
> 221 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/jira/oauth_client_spec.rb:57 # JIRA::OauthClient authenticating 
> with oauth the access token initializes
> rspec ./spec/jira/resource/issue_spec.rb:37 # JIRA::Resource::Issue should 
> find all issues
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> ./spec/jira/base_factory_spec.rb ./spec/jira/base_spec.rb 
> ./spec/jira/has_many_proxy_spec.rb ./spec/jira/http_client_spec.rb 
> ./spec/jira/http_error_spec.rb ./spec/jira/jwt_uri_builder_spec.rb 
> ./spec/jira/oauth_client_spec.rb ./spec/jira/request_client_spec.rb 
> ./spec/jira/resource/agile_spec.rb ./spec/jira/resource/attachment_spec.rb 
> ./spec/jira/resource/board_spec.rb ./spec/jira/resource/createmeta_spec.rb 
> ./spec/jira/resource/field_spec.rb ./spec/jira/resource/filter_spec.rb 
> ./spec/jira/resource/issue_spec.rb ./spec/jira/resource/issuelink_spec.rb 
> ./spec/jira/resource/project_factory_spec.rb 
> ./spec/jira/resource/project_spec.rb ./spec/jira/resource/sprint_spec.rb 
> ./spec/jira/resource/user_factory_spec.rb 
> ./spec/jira/resource/worklog_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

Attachment: ruby-jira.log.gz
Description: application/gzip

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: ruby-jira
Source-Version: 2.1.5-4
Done: HIGUCHI Daisuke (VDR dai) <[email protected]>

We believe that the bug you reported is fixed in the latest version of
ruby-jira, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai) <[email protected]> (supplier of updated ruby-jira 
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 [email protected])


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

Format: 1.8
Date: Mon, 02 Jan 2023 22:45:54 +0900
Source: ruby-jira
Architecture: source
Version: 2.1.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<[email protected]>
Changed-By: HIGUCHI Daisuke (VDR dai) <[email protected]>
Closes: 1027078
Changes:
 ruby-jira (2.1.5-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Jonathan Dowland ]
   * remove Homepage: field: no longer relevant
 .
   [ Debian Janitor ]
   * Update standards version to 4.6.1, no changes needed.
 .
   [ HIGUCHI Daisuke (VDR dai) ]
   * fix FTBFS with ruby-rspec-3.12 (Closes: #1027078)
   * Drop XS-Ruby-Version and XB-Ruby-Version.
   * set Homepage field.
   * set Rules-Requires-Root as no.
   * eliminate lintian warning: ruby-interpreter-is-deprecated
   * eliminate lintian warning: patch-not-forwarded-upstream
   * eliminate lintian warning:
     override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS
Checksums-Sha1:
 d717503946230e2ec18543a53d98c5c6e8bba1e7 2089 ruby-jira_2.1.5-4.dsc
 4816321f81415c9b078f96852009a4675acc785e 4332 ruby-jira_2.1.5-4.debian.tar.xz
Checksums-Sha256:
 1514f4b96041da865f35acf0af2e8ebe94fc130f1f132b39bc4624e36ac02657 2089 
ruby-jira_2.1.5-4.dsc
 b1efc785ee0b54f38999c213010dc65bc8cd77e9309453c36a2a63af95fcacf9 4332 
ruby-jira_2.1.5-4.debian.tar.xz
Files:
 18166b1a90c845a1748b6d3119f2c1b5 2089 ruby optional ruby-jira_2.1.5-4.dsc
 394f078d9c6aa10fcb74aff7848dcdf5 4332 ruby optional 
ruby-jira_2.1.5-4.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEECynYjkLmt2W42OpQeDlhndQ5Zo4FAmOy4FcACgkQeDlhndQ5
Zo4Cuw/+NtyqTy0abzyJxb0Hg0v+LX+WC/VRRVXx+9bDDXXrGXaylw1UXQMAzZLV
aMhnhHc/vwWtxvR5PHxpIL6ZXVG+egwR/PqiRzXfQ9bEDEN4pn14FPkPV5gfyJqA
jj/09rIY7IksLnMNxaS47NWjqAVjvHlnKa5FUa20FMc2UPvDBGxFf5EXIPJIT4xQ
jcZ3lcqmUbELCyMDhHFPz85DjIIQjPh7oZtyCHVzwx/PqufkrM8sYLVfzBQk8YKe
IeAiobGpT3Tq4zojzLNljkobhGs0ryC72v4FU3CYpSDj+yjawM30KPlOP+Tp3W0v
g4sYL/kFR/1L4ujMfCDXXRE1WJMg1TQpvJr/KcSGM7KqZFj54r3HtlkPr7FzfRkV
9aLs/M/LM8Z8qfBw0Lk2/Dv/lJqtWD7KU1AjlEhuTjf+V5CoU88Y1wjgTXadcnWQ
gLJ2PZDyTg89rQW/DfXEQCdDXKPvb07zeD+94ptTFIDE9Jjlcb38ThWUWt9dcKKW
4SKymr6MGTsDLVvo4kNWTn7QGSSUcdABCBkGXaR+hunaEAotnA8elCnMsS3jMKpV
Ute+BlDmAWyQZBZy8MKtJV47H6BonX03TuvEa2ACi2caIj7RI+EZcO+jH1BprPL3
a2JGBh5Gu4j2KHPNHNwJQctfT2LFGrhnhXGlWnQS99XxDAz4zPc=
=/gV6
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to