Control: close -1
On Thu, Jan 11, 2018 at 03:33:30PM +0100, Simon Frei wrote:
> The digikam compiling issue was resolved on the spot back then.
Glad to hear you solved your issue!
> This report can be closed
ACK, doing so.
> thanks for your
> explanation and sorry for wasting your time.
no
Processing control commands:
> close -1
Bug #880438 [libopencv-core-dev] libopencv-core-dev: installs headers in
opencv2 directory
Marked Bug as done
--
880438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
I just stumbled upon these two different dir names when upgrading to
opencv3 and assumed this was controlled by debian packaging and has been
an oversight in the transition. The digikam compiling issue was resolved
on the spot back then. This report can be closed - thanks for your
explanation and
Control: tag -1 upstream moreinfo
Control: severity -1 minor
On Tue, Oct 31, 2017 at 03:28:14PM +0100, Simon Frei wrote:
> All the headers files are placed below
> /usr/include/opencv2/
> while libopencv-dev places its header files below
> /usr/include/opencv/
> Apart from this inconsistency, I
Processing control commands:
> tag -1 upstream moreinfo
Bug #880438 [libopencv-core-dev] libopencv-core-dev: installs headers in
opencv2 directory
Added tag(s) moreinfo and upstream.
> severity -1 minor
Bug #880438 [libopencv-core-dev] libopencv-core-dev: installs headers in
opencv2 directory
Package: libopencv-core-dev
Version: 3.2.0+dfsg-3
Severity: normal
All the headers files are placed below
/usr/include/opencv2/
while libopencv-dev places its header files below
/usr/include/opencv/
Apart from this inconsistency, I also don't see any reason for the
"reference" to version2 - I
