Bug#1096238: marked as done (ros-image-pipeline: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 17 Feb 2025 17:49:09 +0100
with message-id <Z7NohWWQWixN53ah at vis>
and subject line Re: Bug#1096238: ros-image-pipeline: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory
has caused the Debian Bug report #1096238,
regarding ros-image-pipeline: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory
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.)


-- 
1096238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096238
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Lucas Nussbaum <lucas at debian.org>
Subject: ros-image-pipeline: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory
Date: Mon, 17 Feb 2025 17:40:26 +0100
Size: 9658
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20250217/b26c3bb7/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Jochen Sprickerhof <jspricke at debian.org>
Subject: Re: Bug#1096238: ros-image-pipeline: FTBFS: ld: cannot find -lopencv_barcode: No such file or directory
Date: Mon, 17 Feb 2025 17:49:09 +0100
Size: 11310
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20250217/b26c3bb7/attachment-0001.eml>