Bug#891517: marked as done (ros-ros-comm FTBFS: error: 'logError' was not declared in this scope)

Wed Feb 28 21:00:11 UTC 2018

Your message dated Wed, 28 Feb 2018 20:56:48 +0000
with message-id <E1er8mO-0006pT-7n at fasolo.debian.org>
and subject line Bug#891517: fixed in ros-ros-comm 1.13.5+ds1-2
has caused the Debian Bug report #891517,
regarding ros-ros-comm FTBFS: error: 'logError' was not declared in this scope
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.)

-- 
891517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891517
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Adrian Bunk <bunk at debian.org>
Subject: ros-ros-comm FTBFS: error: 'logError' was not declared in this scope
Date: Mon, 26 Feb 2018 13:34:29 +0200
Size: 2472
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20180228/a979b5ef/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Jochen Sprickerhof <jspricke at debian.org>
Subject: Bug#891517: fixed in ros-ros-comm 1.13.5+ds1-2
Date: Wed, 28 Feb 2018 20:56:48 +0000
Size: 8582
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20180228/a979b5ef/attachment-0001.mht>