[DRE-maint] Bug#921703: marked as done (gem2deb is failing to refresh vagrant-libvirt -found character that cannot start any token while scanning for the next token at line 10432 column 16 (Psych::SyntaxError))

[Debian Bug Tracking System]

Your message dated Fri, 08 Feb 2019 13:34:05 +0000
with message-id <E1gs6I9-000Bpi-Fz at fasolo.debian.org>
and subject line Bug#921703: fixed in gem2deb 0.42
has caused the Debian Bug report #921703,
regarding gem2deb is failing to refresh vagrant-libvirt -found character that cannot start any token while scanning for the next token at line 10432 column 16 (Psych::SyntaxError)
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.)


-- 
921703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921703
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Pirate Praveen <praveen at onenetbeyond.org>
Subject: gem2deb is failing to refresh vagrant-libvirt -found character that cannot start any token while scanning for the next token at line 10432 column 16 (Psych::SyntaxError)
Date: Fri, 08 Feb 2019 11:21:47 +0500
Size: 3201
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20190208/3a9a9700/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Antonio Terceiro <terceiro at debian.org>
Subject: Bug#921703: fixed in gem2deb 0.42
Date: Fri, 08 Feb 2019 13:34:05 +0000
Size: 5053
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20190208/3a9a9700/attachment-0001.mht>