Package: libogre-dev Version: 1.7.4-5 Severity: important Dear Maintainer,
Rather than using default versions, I believe the package should depend on whichever specific version of the libboost-date-time-dev and libboost-thread-dev packages were used to build the Ogre binary libs. By not having the specific version as a dependency it becomes very easy for the libboost-*-dev packages to be upgraded or held-back and thus become out of sync with the version used to build the binary Ogre libraries - this can result in issues when running code built against Ogre on a system where such a mis-match of boost versions has occurred. The issues can occur because Ogre exposes its use of boost to client code, so a situation can arise where client code compiles in one version of boost template code whereas the binary Ogre contains different and possibly incompatible code. Given this situation, when the binary ogre and client code have affected objects passed between them, bad things happen. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libogre-dev depends on: ii libboost-date-time-dev 1.49.0.1 ii libboost-thread-dev 1.49.0.1 ii libfreeimage-dev 3.15.1-1+b1 ii libfreetype6-dev 2.4.9-1 ii libogre-1.7.4 1.7.4-5 ii libxaw7-dev 2:1.0.10-2 ii libzzip-dev 0.13.56-1.1 libogre-dev recommends no packages. Versions of packages libogre-dev suggests: pn ogre-doc <none> -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
