Your message dated Fri, 28 Oct 2022 15:20:24 +0000
with message-id <e1oor9k-007szo...@fasolo.debian.org>
and subject line Bug#1019611: fixed in ruby-asset-sync 2.11.0-1.1
has caused the Debian Bug report #1019611,
regarding ruby-asset-sync: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:    
   Failure/Error: @yml ||= 
::YAML.load(::ERB.new(IO.read(yml_path)).result)[::Rails.env] || {}
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.)


-- 
1019611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-asset-sync
Version: 2.11.0-1
Severity: serious
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-asset-sync with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>       Failure/Error: @yml ||= 
> ::YAML.load(::ERB.new(IO.read(yml_path)).result)[::Rails.env] || {}
> 
>       Psych::BadAlias:
>         Unknown alias: defaults
>       # ./lib/asset_sync/config.rb:165:in `yml'
>       # ./lib/asset_sync/config.rb:195:in `load_yml!'
>       # ./lib/asset_sync/config.rb:95:in `initialize'
>       # ./spec/unit/rackspace_spec.rb:63:in `new'
>       # ./spec/unit/rackspace_spec.rb:63:in `block (3 levels) in <top 
> (required)>'
> 
> Finished in 1 second (files took 0.56587 seconds to load)
> 133 examples, 27 failures, 3 pending
> 
> Failed examples:
> 
> rspec ./spec/unit/asset_sync_spec.rb:105 # AssetSync from yml should default 
> AssetSync to enabled
> rspec ./spec/unit/asset_sync_spec.rb:110 # AssetSync from yml should 
> configure run_on_precompile
> rspec ./spec/unit/asset_sync_spec.rb:114 # AssetSync from yml should 
> configure aws_access_key_id
> rspec ./spec/unit/asset_sync_spec.rb:118 # AssetSync from yml should 
> configure aws_secret_access_key
> rspec ./spec/unit/asset_sync_spec.rb:122 # AssetSync from yml should 
> configure fog_directory
> rspec ./spec/unit/asset_sync_spec.rb:126 # AssetSync from yml should 
> configure fog_region
> rspec ./spec/unit/asset_sync_spec.rb:130 # AssetSync from yml should 
> configure path_style
> rspec ./spec/unit/asset_sync_spec.rb:134 # AssetSync from yml should 
> configure existing_remote_files
> rspec ./spec/unit/asset_sync_spec.rb:138 # AssetSync from yml should default 
> gzip_compression to false
> rspec ./spec/unit/asset_sync_spec.rb:142 # AssetSync from yml should default 
> manifest to false
> rspec ./spec/unit/asset_sync_spec.rb:146 # AssetSync from yml should default 
> asset_regexps to match regexps
> rspec ./spec/unit/asset_sync_spec.rb:158 # AssetSync from yml, exporting to a 
> mobile hybrid development directory should be disabled
> rspec ./spec/unit/google_spec.rb:111 # AssetSync from yml when using S3 
> interop API should configure google_storage_access_key_id
> rspec ./spec/unit/google_spec.rb:115 # AssetSync from yml when using S3 
> interop API should configure google_storage_secret_access_key
> rspec ./spec/unit/google_spec.rb:119 # AssetSync from yml when using S3 
> interop API should not configure google_json_key_location
> rspec ./spec/unit/google_spec.rb:123 # AssetSync from yml when using S3 
> interop API should configure fog_directory
> rspec ./spec/unit/google_spec.rb:127 # AssetSync from yml when using S3 
> interop API should configure existing_remote_files
> rspec ./spec/unit/google_spec.rb:131 # AssetSync from yml when using S3 
> interop API should default gzip_compression to false
> rspec ./spec/unit/google_spec.rb:135 # AssetSync from yml when using S3 
> interop API should default manifest to false
> rspec ./spec/unit/google_spec.rb:146 # AssetSync from yml when using service 
> account API should configure google_json_key_location
> rspec ./spec/unit/google_spec.rb:150 # AssetSync from yml when using service 
> account API should not configure google_storage_secret_access_key
> rspec ./spec/unit/rackspace_spec.rb:66 # AssetSync using Rackspace from yml 
> should keep existing remote files
> rspec ./spec/unit/rackspace_spec.rb:70 # AssetSync using Rackspace from yml 
> should configure rackspace_username
> rspec ./spec/unit/rackspace_spec.rb:74 # AssetSync using Rackspace from yml 
> should configure rackspace_api_key
> rspec ./spec/unit/rackspace_spec.rb:78 # AssetSync using Rackspace from yml 
> should configure fog_directory
> rspec ./spec/unit/rackspace_spec.rb:82 # AssetSync using Rackspace from yml 
> should configure fog_region
> rspec ./spec/unit/rackspace_spec.rb:86 # AssetSync using Rackspace from yml 
> should configure existing_remote_files
> 
> Coverage report generated for RSpec to /<<PKGBUILDDIR>>/coverage. 359 / 474 
> LOC (75.74%) covered.
> Stopped processing SimpleCov as a previous error not related to SimpleCov has 
> been detected
> /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 
> ./spec/integration/aws_integration_spec.rb ./spec/unit/asset_sync_spec.rb 
> ./spec/unit/google_spec.rb ./spec/unit/multi_mime_spec.rb 
> ./spec/unit/rackspace_spec.rb ./spec/unit/railsless_spec.rb 
> ./spec/unit/storage_spec.rb failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-asset-sync/ruby-asset-sync_2.11.0-1+rebuild1663007365_amd64-2022-09-12T18:29:26Z.build

To reproduce this, you need ruby-all-dev >= 1:3.0+2.  Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or ir the
transition has alraedy started in unstable, a normal build on unstable should
do it.  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-asset-sync
Source-Version: 2.11.0-1.1
Done: Adrian Bunk <b...@debian.org>

We believe that the bug you reported is fixed in the latest version of
ruby-asset-sync, 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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk <b...@debian.org> (supplier of updated ruby-asset-sync 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: SHA512

Format: 1.8
Date: Sat, 15 Oct 2022 11:32:32 +0300
Source: ruby-asset-sync
Architecture: source
Version: 2.11.0-1.1
Distribution: unstable
Urgency: low
Maintainer: Debian Ruby Team 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Adrian Bunk <b...@debian.org>
Closes: 1019611
Changes:
 ruby-asset-sync (2.11.0-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Add upstream fix to u se YAML.unsafe_load to support Psych v4.
     (Closes: #1019611)
Checksums-Sha1:
 29e3c1a0b6003512ca58b2d4910023e36c5c818c 2220 ruby-asset-sync_2.11.0-1.1.dsc
 1ce413e957ad8322621ea3efe68714b5eee4c95d 4828 
ruby-asset-sync_2.11.0-1.1.debian.tar.xz
Checksums-Sha256:
 fd2c3619ade050e777d1e8724952601745aa631e5d9f9135d2254e125e7b94b2 2220 
ruby-asset-sync_2.11.0-1.1.dsc
 6388e786aaba95988ca260586907f7eae5a3d0d629cd674819d7da88490af44a 4828 
ruby-asset-sync_2.11.0-1.1.debian.tar.xz
Files:
 c14fcfe5b9d5f69a644c0f365b4700bd 2220 ruby optional 
ruby-asset-sync_2.11.0-1.1.dsc
 2d8a9028602b38c566540c27a81f5883 4828 ruby optional 
ruby-asset-sync_2.11.0-1.1.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmNKcHwACgkQiNJCh6LY
mLHIKBAAzZ6fgXDDFxtItCOPgkL9dPBjnlA/9G3a7Y2xK/2Iuk7HHoUrU8MrWAOZ
bpFYEvhUeE9IEGOwPIJmmmlgYCdFm4aKgOulsiKtwfJRToNN4DDtc8gITX+CB7L+
6Mauke4/oXfwL5+7lyX87MjwpeDWxxcHlZ3C4RC+gwl+6Qx44dCne+p/h/5iJ5Zi
C5wLrFxzIY84uLOGYR8yDoWkw5N0nv/UnwY7MLojpgPHbS52Kdai/zq2BnbVVX/P
bGcXgOVOka9M+/bD2PHXJ7+VLX0zQGlrdiBBSUgVDLcecQlsHVX5s5oJ55x4z3u6
vu/6Bws+1hTx+BCF2JOTFXnF1lwM9dMODAxBkQhgNIDWYmJWYEvpgxfaFngCauNI
avX10UQW7nnJKMn9GVklwKkL1rbwu921GlbYi3WT5Y33/hdopMGAVKwZxugoxVXt
/w/bS22H5w1O6czY8B1AXoZ79O5TVVUmligj7qNDVt2te8hd8EDXGv1ZzMJv3on2
7jmvYBDFPtVCAzqtahP1JpI6VtkuJUxtHsxbwCNe4zkm+OqH1hVyLbZE+y16s9KX
wEn0i7qx2nxPZEJQZqvAdL//O5heuOsOwr84baGfxIzZOJxXyNomrWbLg/hXpsgC
8SV6KtYTv8+FyAIW1dsBW456pBhXKrqpuBRycydnQfEd8ltjf2A=
=ldC6
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to