[DRE-maint] Bug#1019611: marked as done (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] || {})

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2022 15:20:24 +0000
with message-id <E1ooR9k-007szO-I2 at 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 owner at bugs.debian.org
immediately.)


-- 
1019611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019611
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Antonio Terceiro <terceiro at debian.org>
Subject: 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] || {}
Date: Mon, 12 Sep 2022 20:49:05 -0300
Size: 9699
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20221028/572e5481/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Debian FTP Masters <ftpmaster at ftp-master.debian.org>
Subject: Bug#1019611: fixed in ruby-asset-sync 2.11.0-1.1
Date: Fri, 28 Oct 2022 15:20:24 +0000
Size: 6149
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20221028/572e5481/attachment-0001.eml>