Thanks for the report! I'll fix it soon. Best Regards, Chen-Tse
2011/1/4 Yaroslav Halchenko <deb...@onerussian.com> > Package: libsvm-dev > Version: 3.0-1 > Severity: normal > > > Since there is no libsvm3.0-dev, and multiple versions (e.g. 2.91 and 3.0) > of > libsvm-dev could not be co-installed on the system, it really makes little > to > no sense to carry additional versioned directory such as > /usr/include/libsvm-3.0 on top of libsvm includes directory. Or am I > missing > something? > > Such include directories migration from one location to another might for > no > good reason ruin builds of dependent packages which might remain > compatible with multiple versions of libsvm while not foreseeing a variety > of > versioned directories coming with new major releases of libsvm. Partially > it > accounts for FTBFS of pymvpa (#608844, CCed). > > -- System Information: > Debian Release: squeeze/sid > APT prefers testing > APT policy: (900, 'testing'), (800, 'unstable'), (300, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages libsvm-dev depends on: > ii libsvm3 3.0-1 library implementing support > vecto > > libsvm-dev recommends no packages. > > libsvm-dev suggests no packages. > > -- no debconf information > > >
