Bug#695097: Prepared sleuthkit 4.1.0

2013-09-01 Thread Andreas Moog
Hello Michael, as far as I understand it, package names for libraries should follow so-names where possible. Wouldn't it make sense then to name the library package libtsk10 and keep the libtsk-dev name for the header/development files? Since upstream decided to drop the major version from the lib

Bug#695097: Prepared sleuthkit 4.1.0

2013-07-01 Thread Derrick Karpo
Hello. Since upstream renamed all the include paths from 'tsk3' to 'tsk since v4.1.0, would it work to rename libtsk-dev to libtsk3-3-dev so that it remains with the other libtsk3-3 libraries, and libtsk-dev becomes the new standard following the v4.x upstream? libtsk3-3-dev can continue to provi

Bug#695097: Prepared sleuthkit 4.1.0

2013-06-26 Thread Michael Prokop
* Henri Salo [Wed Jun 26, 2013 at 10:10:32AM +0300]: > On Tue, Jun 18, 2013 at 01:07:23PM +0200, Michael Prokop wrote: > > we're lagging quite some versions behind with our sleuthkit > > packaging in Debian. I tried to take care of it and just pushed > > upstream and pristine-tar branches for new u

Bug#695097: Prepared sleuthkit 4.1.0

2013-06-26 Thread Henri Salo
On Tue, Jun 18, 2013 at 01:07:23PM +0200, Michael Prokop wrote: > we're lagging quite some versions behind with our sleuthkit > packaging in Debian. I tried to take care of it and just pushed > upstream and pristine-tar branches for new upstream version 4.1.0 of > sleuthkit to our git repos (I hope