Package: libcv-dev Version: 2.4.9.1+dfsg-1+b1 Followup-For: Bug #675542 I have also been bitten by this and could not follow the rationale you gave in reply to the original bug report. Could you please elaborate where and how a dependency loop would occur by making libcv-dev depend on libopencv-dev? Also, a transitional package should help for an easy transition. If you need to point people to a README.Debian document instead (which you should, honestly, have someone read over), that transitional package is rather pointless.
Thank you! - Fabian -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libcv-dev depends on: ii libopencv-calib3d-dev 2.4.9.1+dfsg-1+b1 ii libopencv-core-dev 2.4.9.1+dfsg-1+b1 ii libopencv-features2d-dev 2.4.9.1+dfsg-1+b1 ii libopencv-flann-dev 2.4.9.1+dfsg-1+b1 ii libopencv-imgproc-dev 2.4.9.1+dfsg-1+b1 ii libopencv-legacy-dev 2.4.9.1+dfsg-1+b1 ii libopencv-ml-dev 2.4.9.1+dfsg-1+b1 ii libopencv-objdetect-dev 2.4.9.1+dfsg-1+b1 ii libopencv-video-dev 2.4.9.1+dfsg-1+b1 ii pkg-config 0.28-1 libcv-dev recommends no packages. libcv-dev suggests no packages. -- no debconf information -- debian-science-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
