Your message dated Wed, 23 Aug 2023 15:19:39 +0000
with message-id <e1qypdz-0011zx...@fasolo.debian.org>
and subject line Bug#1043574: Removed package(s) from unstable
has caused the Debian Bug report #1019665,
regarding ruby-safe-yaml: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
ArgumentError:
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.)
--
1019665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-safe-yaml
Version: 1.0.5-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-safe-yaml with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> ArgumentError:
> wrong number of arguments (given 2, expected 1)
> # ./lib/safe_yaml/load.rb:149:in `load'
> # ./lib/safe_yaml.rb:29:in `safe_load'
> # ./spec/safe_yaml_spec.rb:7:in `safe_load_round_trip'
> # ./spec/safe_yaml_spec.rb:745:in `block (4 levels) in <top (required)>'
>
> Finished in 0.08109 seconds (files took 0.12613 seconds to load)
> 134 examples, 20 failures
>
> Failed examples:
>
> rspec ./spec/safe_yaml_spec.rb:29 # Psych unsafe_load allows exploits through
> objects defined in YAML w/ !ruby/hash via custom :[]= methods
> rspec ./spec/safe_yaml_spec.rb:34 # Psych unsafe_load allows exploits through
> objects defined in YAML w/ !ruby/object via the :init_with method
> rspec ./spec/safe_yaml_spec.rb:40 # Psych unsafe_load allows exploits through
> objects w/ sensitive instance variables defined in YAML w/ !ruby/object
> rspec ./spec/safe_yaml_spec.rb:50 # Psych unsafe_load with special
> whitelisted tags defined effectively ignores the whitelist (since everything
> is whitelisted)
> rspec ./spec/safe_yaml_spec.rb:318 # Psych safe_load with special whitelisted
> tags defined will allow objects to be deserialized for whitelisted tags
> rspec ./spec/safe_yaml_spec.rb:330 # Psych safe_load with special whitelisted
> tags defined will not deserialize objects without whitelisted tags
> rspec ./spec/safe_yaml_spec.rb:336 # Psych safe_load with special whitelisted
> tags defined will not allow non-whitelisted objects to be embedded within
> objects with whitelisted tags
> rspec ./spec/safe_yaml_spec.rb:378 # Psych safe_load with special whitelisted
> tags defined with the :raise_on_unknown_tag option enabled does not raise an
> exception as long as all tags are whitelisted
> rspec ./spec/safe_yaml_spec.rb:404 # Psych safe_load with special whitelisted
> tags defined with the :raise_on_unknown_tag option enabled does not raise an
> exception on the non-specific '!' tag
> rspec ./spec/safe_yaml_spec.rb:421 # Psych safe_load with special whitelisted
> tags defined with the :raise_on_unknown_tag option enabled with whitelisted
> custom class does not raise an exception on the non-specific '!' tag
> rspec ./spec/safe_yaml_spec.rb:464 # Psych safe_load when options are passed
> direclty to #load which differ from the defaults (or, for example, when
> certain tags are whitelisted) goes with the default option when it is not
> overridden
> rspec ./spec/safe_yaml_spec.rb:497 # Psych unsafe_load_file allows exploits
> through objects defined in YAML w/ !ruby/hash via custom :[]= methods
> rspec ./spec/safe_yaml_spec.rb:504 # Psych unsafe_load_file allows exploits
> through objects defined in YAML w/ !ruby/object via the :init_with method
> rspec ./spec/safe_yaml_spec.rb:510 # Psych unsafe_load_file allows exploits
> through objects w/ sensitive instance variables defined in YAML w/
> !ruby/object
> rspec ./spec/safe_yaml_spec.rb:550 # Psych load as long as a :default_mode
> has been specified doesn't issue a warning for unsafe mode, since an explicit
> mode has been set
> rspec ./spec/safe_yaml_spec.rb:708 # Psych whitelist! with a Class as its
> argument successfully deserializes the specified class
> rspec ./spec/safe_yaml_spec.rb:719 # Psych whitelist! with a Class as its
> argument works for ranges
> rspec ./spec/safe_yaml_spec.rb:724 # Psych whitelist! with a Class as its
> argument works for regular expressions
> rspec ./spec/safe_yaml_spec.rb:729 # Psych whitelist! with a Class as its
> argument works for multiple classes
> rspec ./spec/safe_yaml_spec.rb:734 # Psych whitelist! with a Class as its
> argument works for arbitrary Exception subclasses
>
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-safe-yaml/ruby-safe-yaml_1.0.5-2+rebuild1663008186_amd64-2022-09-12T18:43:07Z.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
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.0.5-2+rm
Dear submitter,
as the package ruby-safe-yaml has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1043574
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
