Your message dated Thu, 17 Nov 2022 00:27:58 +0000
with message-id <[email protected]>
and subject line Bug#1019632: fixed in ruby-ice-cube 0.16.4-3
has caused the Debian Bug report #1019632,
regarding ruby-ice-cube: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:      
 Failure/Error: expect(YAML.load(symbol_yaml)).to eq(YAML.load(string_yaml))
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.)


-- 
1019632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019632
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-ice-cube
Version: 0.16.4-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: [email protected]
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-ice-cube with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>       Failure/Error: expect(YAML.load(symbol_yaml)).to 
> eq(YAML.load(string_yaml))
> 
>       Psych::DisallowedClass:
>         Tried to load unspecified class: Time
>       # ./spec/examples/to_yaml_spec.rb:315:in `block (2 levels) in 
> <module:IceCube>'
>       # ./spec/spec_helper.rb:68:in `block (3 levels) in <top (required)>'
>       # ./spec/spec_helper.rb:67:in `block (2 levels) in <top (required)>'
> 
> Finished in 1.01 seconds (files took 0.36923 seconds to load)
> 1076 examples, 48 failures
> 
> Failed examples:
> 
> rspec ./spec/examples/active_support_spec.rb:48 # IceCube::Schedule using 
> ActiveSupport can round trip TimeWithZone to YAML
> rspec ./spec/examples/hourly_rule_spec.rb:61 # IceCube::HourlyRule should 
> produce the correct days for @interval = 3
> rspec ./spec/examples/ice_cube_spec.rb:449 # IceCube::Schedule should be able 
> to specify an end date and go to/from yaml
> rspec ./spec/examples/minutely_rule_spec.rb:58 # IceCube::MinutelyRule should 
> produce the correct days for @interval = 3
> rspec './spec/examples/regression_spec.rb[1:1:5]' # IceCube::Schedule in 
> America/Anchorage should not choke on parsing [#26]
> rspec './spec/examples/regression_spec.rb[1:1:6]' # IceCube::Schedule in 
> America/Anchorage should parse an old schedule properly
> rspec './spec/examples/regression_spec.rb[1:1:13]' # IceCube::Schedule in 
> America/Anchorage should not hang next_time on DST boundary [#98]
> rspec './spec/examples/regression_spec.rb[1:1:14]' # IceCube::Schedule in 
> America/Anchorage should still include date over DST boundary [#98]
> rspec './spec/examples/regression_spec.rb[1:2:5]' # IceCube::Schedule in 
> Europe/London should not choke on parsing [#26]
> rspec './spec/examples/regression_spec.rb[1:2:6]' # IceCube::Schedule in 
> Europe/London should parse an old schedule properly
> rspec './spec/examples/regression_spec.rb[1:2:13]' # IceCube::Schedule in 
> Europe/London should not hang next_time on DST boundary [#98]
> rspec './spec/examples/regression_spec.rb[1:2:14]' # IceCube::Schedule in 
> Europe/London should still include date over DST boundary [#98]
> rspec './spec/examples/regression_spec.rb[1:3:5]' # IceCube::Schedule in 
> Pacific/Auckland should not choke on parsing [#26]
> rspec './spec/examples/regression_spec.rb[1:3:6]' # IceCube::Schedule in 
> Pacific/Auckland should parse an old schedule properly
> rspec './spec/examples/regression_spec.rb[1:3:13]' # IceCube::Schedule in 
> Pacific/Auckland should not hang next_time on DST boundary [#98]
> rspec './spec/examples/regression_spec.rb[1:3:14]' # IceCube::Schedule in 
> Pacific/Auckland should still include date over DST boundary [#98]
> rspec ./spec/examples/serialization_spec.rb:19 # 
> IceCube::Schedule::dump(schedule) with ActiveSupport::TimeWithZone serializes 
> time as a Hash
> rspec ./spec/examples/serialization_spec.rb:41 # 
> IceCube::Schedule::load(yaml) creates a new object from a YAML string
> rspec ./spec/examples/serialization_spec.rb:48 # 
> IceCube::Schedule::load(yaml) with ActiveSupport::TimeWithZone deserializes 
> time from Hash
> rspec './spec/examples/to_yaml_spec.rb[1:1]' # IceCube::Schedule to_yaml 
> should make a yearly round trip with to_yaml [#47]
> rspec './spec/examples/to_yaml_spec.rb[1:2]' # IceCube::Schedule to_yaml 
> should make a monthly round trip with to_yaml [#47]
> rspec './spec/examples/to_yaml_spec.rb[1:3]' # IceCube::Schedule to_yaml 
> should make a weekly round trip with to_yaml [#47]
> rspec './spec/examples/to_yaml_spec.rb[1:4]' # IceCube::Schedule to_yaml 
> should make a daily round trip with to_yaml [#47]
> rspec './spec/examples/to_yaml_spec.rb[1:5]' # IceCube::Schedule to_yaml 
> should make a hourly round trip with to_yaml [#47]
> rspec './spec/examples/to_yaml_spec.rb[1:6]' # IceCube::Schedule to_yaml 
> should make a minutely round trip with to_yaml [#47]
> rspec './spec/examples/to_yaml_spec.rb[1:7]' # IceCube::Schedule to_yaml 
> should make a secondly round trip with to_yaml [#47]
> rspec ./spec/examples/to_yaml_spec.rb:19 # IceCube::Schedule to_yaml should 
> be able to let rules take round trips to yaml
> rspec ./spec/examples/to_yaml_spec.rb:34 # IceCube::Schedule to_yaml should 
> be able to make a round-trip to YAML
> rspec ./spec/examples/to_yaml_spec.rb:48 # IceCube::Schedule to_yaml should 
> be able to make a round-trip to YAML with .day
> rspec ./spec/examples/to_yaml_spec.rb:59 # IceCube::Schedule to_yaml should 
> be able to make a round-trip to YAML with .day_of_month
> rspec ./spec/examples/to_yaml_spec.rb:70 # IceCube::Schedule to_yaml should 
> be able to make a round-trip to YAML with .day_of_week
> rspec ./spec/examples/to_yaml_spec.rb:81 # IceCube::Schedule to_yaml should 
> be able to make a round-trip to YAML with .day_of_year
> rspec ./spec/examples/to_yaml_spec.rb:92 # IceCube::Schedule to_yaml should 
> be able to make a round-trip to YAML with .hour_of_day
> rspec ./spec/examples/to_yaml_spec.rb:103 # IceCube::Schedule to_yaml should 
> be able to make a round-trip to YAML with .minute_of_hour
> rspec ./spec/examples/to_yaml_spec.rb:114 # IceCube::Schedule to_yaml should 
> be able to make a round-trip to YAML with .month_of_year
> rspec ./spec/examples/to_yaml_spec.rb:125 # IceCube::Schedule to_yaml should 
> be able to make a round-trip to YAML with .second_of_minute
> rspec ./spec/examples/to_yaml_spec.rb:149 # IceCube::Schedule to_yaml should 
> be able to roll forward times and get back times in an array - TimeWithZone
> rspec ./spec/examples/to_yaml_spec.rb:159 # IceCube::Schedule to_yaml should 
> be able to roll forward times and get back times in an array - Time
> rspec ./spec/examples/to_yaml_spec.rb:169 # IceCube::Schedule to_yaml should 
> be able to go back and forth to yaml and then call occurrences
> rspec ./spec/examples/to_yaml_spec.rb:179 # IceCube::Schedule to_yaml should 
> be able to make a round trip with an exception time
> rspec ./spec/examples/to_yaml_spec.rb:186 # IceCube::Schedule to_yaml crazy 
> shit
> rspec ./spec/examples/to_yaml_spec.rb:212 # IceCube::Schedule to_yaml should 
> be able to roll forward and back in time
> rspec ./spec/examples/to_yaml_spec.rb:218 # IceCube::Schedule to_yaml should 
> be backward compatible with old yaml Time format
> rspec ./spec/examples/to_yaml_spec.rb:260 # IceCube::Schedule to_yaml should 
> be able to bring a Rule to_yaml and back with a timezone
> rspec ./spec/examples/to_yaml_spec.rb:275 # IceCube::Schedule to_yaml should 
> be able to bring a Rule to_yaml and back with an until Date
> rspec ./spec/examples/to_yaml_spec.rb:281 # IceCube::Schedule to_yaml should 
> be able to bring a Rule to_yaml and back with an until Time
> rspec ./spec/examples/to_yaml_spec.rb:288 # IceCube::Schedule to_yaml should 
> be able to bring a Rule to_yaml and back with an until TimeWithZone
> rspec ./spec/examples/to_yaml_spec.rb:308 # IceCube::Schedule to_yaml should 
> be able to bring in a schedule with a rule from hash with symbols or strings
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-ice-cube/ruby-ice-cube_0.16.4-1+rebuild1663007724_amd64-2022-09-12T18:35:25Z.build

To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on
when you try this, it might mean installing ruby-all-dev from experimental, or
if the transition has already started, a normal build on unstable will be
enough.  If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.

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!

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: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: ruby-ice-cube
Source-Version: 0.16.4-3
Done: Cédric Boutillier <[email protected]>

We believe that the bug you reported is fixed in the latest version of
ruby-ice-cube, 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.
Cédric Boutillier <[email protected]> (supplier of updated ruby-ice-cube 
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: SHA512

Format: 1.8
Date: Thu, 17 Nov 2022 00:05:35 +0100
Source: ruby-ice-cube
Architecture: source
Version: 0.16.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<[email protected]>
Changed-By: Cédric Boutillier <[email protected]>
Closes: 1019632
Changes:
 ruby-ice-cube (0.16.4-3) unstable; urgency=medium
 .
   * Team upload
   * Add upstream to support Psych 4 shipped with ruby3.1 (Closes: #1019632)
   * Fix some round trip test failures in autopkgtest
   * Bump Standards-Version to 4.6.1 (no changes needed)
   * Skipping -2 to recover from broken upload
Checksums-Sha1:
 1cf377b1f277d9a51efe8050dc1dbba117deca61 1476 ruby-ice-cube_0.16.4-3.dsc
 2b2036766738803943a89b975e885da28a689310 75006 ruby-ice-cube_0.16.4.orig.tar.gz
 36641ba32ecbfc01ad38cfaf70198481fa960e13 4644 
ruby-ice-cube_0.16.4-3.debian.tar.xz
 b86fe1ef9ad77116f7f11491a183322d0ed44110 9882 
ruby-ice-cube_0.16.4-3_amd64.buildinfo
Checksums-Sha256:
 64f3e2419625ec63d2ab09b9739d01fdcd462fdd41e2091450c6c162e9905517 1476 
ruby-ice-cube_0.16.4-3.dsc
 f76b8e42a494e981821ef71cf3f2df479a2e74a2ecc503229e2636734d4d4d7c 75006 
ruby-ice-cube_0.16.4.orig.tar.gz
 0fd4ab4aad4bedc3cd387bf742f38dd7ac1859ee32781a44e80be268e9d7a908 4644 
ruby-ice-cube_0.16.4-3.debian.tar.xz
 0000fe997efdbcba1306bfce0f42a9b40eb4da59111c4b71f8d2d318971c9c09 9882 
ruby-ice-cube_0.16.4-3_amd64.buildinfo
Files:
 77e6e7e1e13502794ef339cfc164aaa1 1476 ruby optional ruby-ice-cube_0.16.4-3.dsc
 2fcfcf24e5e4ef671347d049e927e937 75006 ruby optional 
ruby-ice-cube_0.16.4.orig.tar.gz
 b07da1c6808c601bd68b9d704b09a1e9 4644 ruby optional 
ruby-ice-cube_0.16.4-3.debian.tar.xz
 a58037814ae157f4f5454160d33a2b20 9882 ruby optional 
ruby-ice-cube_0.16.4-3_amd64.buildinfo

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

iHUEARYKAB0WIQSEz/3CFSD4gwbsKdFSaZq2P58rwwUCY3VuAAAKCRBSaZq2P58r
w3nnAQDz96N0eGmC2GovXdL0BtdM7xaampqsjcKnJPOprruwMgEAkhjQH1aHxZik
+G3Xo/nHgpGhb+3m0zs7xxHbG83KsAA=
=ZlmT
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to