Your message dated Wed, 28 Dec 2022 01:50:26 +0000
with message-id <e1palam-00d0m9...@fasolo.debian.org>
and subject line Bug#1027083: fixed in ruby-notiffany 0.1.3-4
has caused the Debian Bug report #1027083,
regarding ruby-notiffany: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1"
failed: Failure/Error: expect(foo_object).to
receive(:notify).with("Hello", foo: "bar")
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.)
--
1027083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-notiffany
Version: 0.1.3-3
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-notiffany failed to build.
Relevant part of the build log (hopefully):
> Failure/Error: expect(foo_object).to receive(:notify).with("Hello",
> foo: "bar")
>
> #<InstanceDouble(Notiffany::Notifier::Tmux) (anonymous)> received
> :notify with unexpected arguments
> expected: ("Hello", {:foo=>"bar"}) (keyword arguments)
> got: ("Hello", {:foo=>"bar"}) (options hash)
> # ./spec/lib/notiffany/notifier_spec.rb:336:in `block (6 levels) in
> <module:Notiffany>'
>
> Finished in 0.25327 seconds (files took 0.16632 seconds to load)
> 183 examples, 17 failures, 2 pending
>
> Failed examples:
>
> rspec ./spec/lib/notiffany/notifier/terminal_notifier_spec.rb:67 #
> Notiffany::Notifier::TerminalNotifier#notify should allow the title to be
> customized
> rspec ./spec/lib/notiffany/notifier/terminal_notifier_spec.rb:57 #
> Notiffany::Notifier::TerminalNotifier#notify should call the notifier.
> rspec ./spec/lib/notiffany/notifier/terminal_notifier_spec.rb:78 #
> Notiffany::Notifier::TerminalNotifier#notify without a title set should show
> the app name in the title
> rspec ./spec/lib/notiffany/notifier/terminal_notifier_spec.rb:45 #
> Notiffany::Notifier::TerminalNotifier#notify with options passed at
> initialization overwrites object options with passed options
> rspec ./spec/lib/notiffany/notifier/terminal_notifier_spec.rb:38 #
> Notiffany::Notifier::TerminalNotifier#notify with options passed at
> initialization uses these options by default
> rspec ./spec/lib/notiffany/notifier/rb_notifu_spec.rb:80 #
> Notiffany::Notifier::Notifu#notify without additional options shows the
> notification with the default options
> rspec ./spec/lib/notiffany/notifier/rb_notifu_spec.rb:101 #
> Notiffany::Notifier::Notifu#notify with additional options can override the
> default options
> rspec ./spec/lib/notiffany/notifier/rb_notifu_spec.rb:40 #
> Notiffany::Notifier::Notifu#notify with options passed at initialization uses
> these options by default
> rspec ./spec/lib/notiffany/notifier/detected_spec.rb:112 #
> Notiffany::Notifier::Detected#add with manually configured notifiers when not
> available shows a warning
> rspec ./spec/lib/notiffany/notifier/detected_spec.rb:103 #
> Notiffany::Notifier::Detected#add with manually configured notifiers when not
> available does not add the library
> rspec ./spec/lib/notiffany/notifier/detected_spec.rb:108 #
> Notiffany::Notifier::Detected#add with manually configured notifiers when not
> available does not raise an error
> rspec ./spec/lib/notiffany/notifier/growl_spec.rb:144 #
> Notiffany::Notifier::Growl#notify with options Growl cannot handle passes
> options only Growl can handle
> rspec ./spec/lib/notiffany/notifier_spec.rb:182 #
> Notiffany::Notifier#initialize with custom notifier config when connected
> when enabled when supported when available adds the notifier to the
> notifications
> rspec ./spec/lib/notiffany/notifier_spec.rb:145 #
> Notiffany::Notifier#initialize with custom notifier config when not connected
> when enabled when supported when available adds the notifier to the
> notifications
> rspec ./spec/lib/notiffany/notifier_spec.rb:360 # Notiffany::Notifier.notify
> with multiple notifiers when connected when enabled sends notifications
> rspec ./spec/lib/notiffany/notifier_spec.rb:368 # Notiffany::Notifier.notify
> with multiple notifiers when connected when enabled when a child process
> sends notifications
> rspec ./spec/lib/notiffany/notifier_spec.rb:335 # Notiffany::Notifier.notify
> with multiple notifiers when not connected when a child process sends
> notifications
>
> Randomized with seed 32791
>
> /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
> --pattern ./spec/\*\*/\*_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
ruby-notiffany.log.gz
Description: application/gzip
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-notiffany
Source-Version: 0.1.3-4
Done: HIGUCHI Daisuke (VDR dai) <d...@debian.org>
We believe that the bug you reported is fixed in the latest version of
ruby-notiffany, 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 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai) <d...@debian.org> (supplier of updated ruby-notiffany
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: Wed, 28 Dec 2022 10:14:36 +0900
Source: ruby-notiffany
Architecture: source
Version: 0.1.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: HIGUCHI Daisuke (VDR dai) <d...@debian.org>
Closes: 1027083
Changes:
ruby-notiffany (0.1.3-4) unstable; urgency=medium
.
* fix FTBFS with ruby-rspec 3.12 and ruby3.1 (Closes: #1027083).
* Drop XS-Ruby-Version and XB-Ruby-Version.
Checksums-Sha1:
9d1c585469229ed61fe340e7df5fbdd985d43707 2113 ruby-notiffany_0.1.3-4.dsc
140fe5e8045a97960d74fc2e77a396146593e7e5 6012
ruby-notiffany_0.1.3-4.debian.tar.xz
Checksums-Sha256:
fdf6cd038218bfe69762f6cd1a4a9ce2b4228ae6424c34e314600ca99c9bb36e 2113
ruby-notiffany_0.1.3-4.dsc
3aaea9b7271330e9decb39e65e728c8dd92299c0c44ed3c864e4376cba516b2e 6012
ruby-notiffany_0.1.3-4.debian.tar.xz
Files:
51b3d07e0c30f205e47fa1b83cdf66e0 2113 ruby optional ruby-notiffany_0.1.3-4.dsc
4d6265a36c5b92f20e71b5f2f3be973d 6012 ruby optional
ruby-notiffany_0.1.3-4.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECynYjkLmt2W42OpQeDlhndQ5Zo4FAmOrm1UACgkQeDlhndQ5
Zo7bqRAAqG78CnlPpBxeAyuG8Ij37hPD7+wWHo9oJRpoRXSD1v9l0snRHMug3wXE
UBY0adp3W3TRB4HGCh9t5ykbUAFvWUYr+gdD4APE81ELMSt3PD8b+xsdjCOu+pKB
6i+qHDHXg7aQBVIn1ABIIUqRD93A5loqQNE1kSF1l60/j9Zpcl571DJZksRYLfrI
fWl59sRvbhEOePIqqIrYmwG+exh7enqpUidIVlonGEn2RHGEZ8/bQiai0UMzQZy0
zk1e+ezrUj5Wgl7YKkRWeOgx6PQGz4W3nkOvI19hdl6je3TRyaEQJZjV01ioG8e6
gO3j44u1FYKaS42uzwNL3qQBA96p3o2o5Q8eGP7hpQpBRkAGxLDuELRC1hfqMlvo
WRstp3El4kjYtfHOqSaKR91gdzy7NUQ+1vr3pLOFoD/eRctH7mLPzPTyfEHXFP1U
5KnkFrZH2pKcm3Bos14lyEiotGhFAYofqu0Lgzo/eBS9BqrgK4UVJ5Z2sqMdfgi3
Z3ILu/PPPTsx/4he3FDtqSFLv8sC6K87EPt5G1+o/dyv5OY6oFdFz52Z8L/IV0qf
nLvl2JqV4WIaR9M5gUADKDa57JR3Dm21K4B2TvnCu+dloKHe+dM3FRYCd0EOV2xY
S6LZbueVCk9hBkM/2QFhAmN824yuRrMZsleZ4SnL5dGyLviw+Sc=
=s++K
-----END PGP SIGNATURE-----
--- End Message ---
