Bug#824032: libsvm: Would it be possible to upgrade the package to the latest upstream release?

2016-05-11 Thread Christian Kastner
On 2016-05-11 21:51, Dominique Belhachemi wrote: > Thanks for the update Christian, it will leave all changes up to you guys. > > Two more comments: > > 1. Please compare the file size with/without binaries. > 828K libsvm-3.21.tar.gz > 137K libsvm_3.21+dfsg.orig.tar.gz Oh, it's definitely on

Bug#824032: libsvm: Would it be possible to upgrade the package to the latest upstream release?

2016-05-11 Thread Dominique Belhachemi
Thanks for the update Christian, it will leave all changes up to you guys. Two more comments: 1. Please compare the file size with/without binaries. 828K libsvm-3.21.tar.gz 137K libsvm_3.21+dfsg.orig.tar.gz 2. Please change this to 'all' . Package: python-libsvm Architecture: any

Bug#824032: libsvm: Would it be possible to upgrade the package to the latest upstream release?

2016-05-11 Thread Christian Kastner
On 2016-05-11 17:38, Dominique Belhachemi wrote: > I am preparing a NMU to fix #823880. Please don't, see my recent mail to #823880. > Your patch looks good Yes in general, but most changes are unacceptable within the context of an NMU. > and I can integrate it as well as a new python3-libsvm

Bug#824032: libsvm: Would it be possible to upgrade the package to the latest upstream release?

2016-05-11 Thread Dominique Belhachemi
I am preparing a NMU to fix #823880 . Your patch looks good, and I can integrate it as well as a new python3-libsvm package.

Bug#824032: libsvm: Would it be possible to upgrade the package to the latest upstream release?

2016-05-11 Thread Miriam Ruiz
Source: libsvm Version: 3.12-1.1 Severity: wishlist Hi, I would like to have libsvm 3.21 (released on December 14, 2015) if it was possible. I've already developed a patch to do this, fixing also some lintian warnings and upgrading the packaging to the latest policy on the way, that I'm