Your message dated Sat, 05 Nov 2016 22:37:41 +0000
with message-id <e1c39an-000erd...@fasolo.debian.org>
and subject line Bug#841564: fixed in ruby-hipchat 1.5.2-3
has caused the Debian Bug report #841564,
regarding ruby-hipchat: FTBFS: ERROR: Test "ruby2.3" failed: NoMethodError:
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.)
--
841564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-hipchat
Version: 1.5.2-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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 `mock' for
> #<RSpec::ExampleGroups::HipChatAPIV2::SendFileUser:0x0000000333d788>
> # ./spec/hipchat_api_v2_spec.rb:368:in `block (3 levels) in <top
> (required)>'
>
> Finished in 0.10501 seconds (files took 0.71396 seconds to load)
> 72 examples, 28 failures
>
> Failed examples:
>
> rspec ./spec/hipchat_api_v1_spec.rb:30 # HipChat (API V1) #history fails when
> the room doen't exist
> rspec ./spec/hipchat_api_v1_spec.rb:38 # HipChat (API V1) #history fails when
> we're not allowed to do so
> rspec ./spec/hipchat_api_v1_spec.rb:46 # HipChat (API V1) #history fails if
> we get an unknown response code
> rspec ./spec/hipchat_api_v1_spec.rb:69 # HipChat (API V1) #topic fails when
> the room doesn't exist
> rspec ./spec/hipchat_api_v1_spec.rb:77 # HipChat (API V1) #topic fails when
> we're not allowed to do so
> rspec ./spec/hipchat_api_v1_spec.rb:85 # HipChat (API V1) #topic fails if we
> get an unknown response code
> rspec ./spec/hipchat_api_v1_spec.rb:120 # HipChat (API V1) #send but fails
> when the room doesn't exist
> rspec ./spec/hipchat_api_v1_spec.rb:128 # HipChat (API V1) #send but fails
> when we're not allowed to do so
> rspec ./spec/hipchat_api_v1_spec.rb:140 # HipChat (API V1) #send but fails if
> we get an unknown response code
> rspec ./spec/hipchat_api_v2_spec.rb:31 # HipChat (API V2) #history fails when
> the room doen't exist
> rspec ./spec/hipchat_api_v2_spec.rb:39 # HipChat (API V2) #history fails when
> we're not allowed to do so
> rspec ./spec/hipchat_api_v2_spec.rb:47 # HipChat (API V2) #history fails if
> we get an unknown response code
> rspec ./spec/hipchat_api_v2_spec.rb:72 # HipChat (API V2) #statistics fails
> when the room doen't exist
> rspec ./spec/hipchat_api_v2_spec.rb:80 # HipChat (API V2) #statistics fails
> when we're not allowed to do so
> rspec ./spec/hipchat_api_v2_spec.rb:88 # HipChat (API V2) #statistics fails
> if we get an unknown response code
> rspec ./spec/hipchat_api_v2_spec.rb:111 # HipChat (API V2) #topic fails when
> the room doesn't exist
> rspec ./spec/hipchat_api_v2_spec.rb:119 # HipChat (API V2) #topic fails when
> we're not allowed to do so
> rspec ./spec/hipchat_api_v2_spec.rb:127 # HipChat (API V2) #topic fails if we
> get an unknown response code
> rspec ./spec/hipchat_api_v2_spec.rb:162 # HipChat (API V2) #send but fails
> when the room doesn't exist
> rspec ./spec/hipchat_api_v2_spec.rb:170 # HipChat (API V2) #send but fails
> when we're not allowed to do so
> rspec ./spec/hipchat_api_v2_spec.rb:182 # HipChat (API V2) #send but fails if
> we get an unknown response code
> rspec ./spec/hipchat_api_v2_spec.rb:209 # HipChat (API V2) #send_file but
> fails when the room doesn't exist
> rspec ./spec/hipchat_api_v2_spec.rb:217 # HipChat (API V2) #send_file but
> fails when we're not allowed to do so
> rspec ./spec/hipchat_api_v2_spec.rb:229 # HipChat (API V2) #send_file but
> fails if we get an unknown response code
> rspec ./spec/hipchat_api_v2_spec.rb:313 # HipChat (API V2) #send user message
> but fails when the user doesn't exist
> rspec ./spec/hipchat_api_v2_spec.rb:321 # HipChat (API V2) #send user message
> but fails when we're not allowed to do so
> rspec ./spec/hipchat_api_v2_spec.rb:359 # HipChat (API V2) #send_file user
> but fails when the user doesn't exist
> rspec ./spec/hipchat_api_v2_spec.rb:367 # HipChat (API V2) #send_file user
> but fails when we're not allowed to do so
>
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.3" failed:
If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185
If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.
The full build log is available from:
http://aws-logs.debian.net/2016/10/21/ruby-hipchat_1.5.2-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 ---
Source: ruby-hipchat
Source-Version: 1.5.2-3
We believe that the bug you reported is fixed in the latest version of
ruby-hipchat, 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 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pirate Praveen <prav...@debian.org> (supplier of updated ruby-hipchat 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: Sun, 06 Nov 2016 03:45:46 +0530
Source: ruby-hipchat
Binary: ruby-hipchat
Architecture: source
Version: 1.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Pirate Praveen <prav...@debian.org>
Description:
ruby-hipchat - Ruby library to interact with HipChat
Closes: 841564
Changes:
ruby-hipchat (1.5.2-3) unstable; urgency=medium
.
* Team upload
* Disable tests (incompatible with newer rspec) (Closes: #841564)
Checksums-Sha1:
ae971e5ed32d813564e3449a656de75a53cc916a 2141 ruby-hipchat_1.5.2-3.dsc
52da89a540e5ee0ec4a068f8295352632ad9f8d4 3624
ruby-hipchat_1.5.2-3.debian.tar.xz
Checksums-Sha256:
75e6fbfbee873cd2f4d8b36d3959c00f28708bfac175253c4c0d5053062abb38 2141
ruby-hipchat_1.5.2-3.dsc
14a361db5c4e544e1d01a3ceb8d8bfdd9ef033d3d61b885b8b42c68a8b5a50dc 3624
ruby-hipchat_1.5.2-3.debian.tar.xz
Files:
12ad9dbf182679f24011b56b26da79dc 2141 ruby optional ruby-hipchat_1.5.2-3.dsc
a0ed7e806e882844a2f3d167bb5a1825 3624 ruby optional
ruby-hipchat_1.5.2-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCAAGBQJYHlrtAAoJEM4fnGdFEsIqDUMP/1xbmpIaAB/KW6VhrdyYl0a6
RQg+8cspNKDbCfvENPiZzvlnPCaV772tpVQclr1orFg+nGgy9/kf6L+msYHc5aVU
VRSPTUWqIQ66Z5rTu1pOWzrpXDZ1+4kR3vGcrGWBjVpgl2L+EzwVrbGzSfZ7Pf8Z
1C7ZdClFgKvWTP5nrzgYJs2vqD2HUwC4sCuEVB0O8Lkg2/qmKrUbJObhzI4R2FZl
qoFw9mWy/StRNuQhvT6g71cjPvxbhlGLkz4A5NBphfSmbXlprFb7Id/r0EPeuiiZ
44LMu3Rg1ynAFiaxFSVGEyEkiRYH1PqdjDRs4OMdSGenT7DPU6K/6EQdYhhGyv5q
2rtg2Ium3vZmG5wub9GrY9Ung6WR7kf/Lv522jgfBQEbzVQaRLOiKmGWBa2mwVq6
vJpARGT6ls9ZmjWXYj9bMyydxUVBsWvA7crLOVrKgZw8kOjKn4bwQnnpU3Wb61qa
JMts+EZw+94anp2mK/l9TWFFeVgtAMLdSlSfldIEKM7LRbzx/iMR8uubq/Ch7sB2
Dy20EyuGaIaCk+IHcfoJMfUmAAOX6Ozb4JkGg9323xpzKd0AfO0r7PeqYQTW674y
a5n39uV2dZMbG4eRCgQeFRtyjh9vQ1CBMp3O3lhBPfriEGHyLIVAROf20lRO1ajA
mMrQEJ3uOr6nPdF3E/e5
=utwG
-----END PGP SIGNATURE-----
--- End Message ---
