[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#219010: On the cooperation between sleuthkit and tct



* Justin Pryzby <justinpryzby at users.sourceforge.net> [20090929 22:15]:

> sleuthkit and tct no longer conflict.  Sleuthkit includes an
> alternatives mechanism for those files which used to exist in both
> packages.  But, alternatives are only useful when there are multiple
> cooperating packages; right now, there is only one.  Also, the current
> state of things allows debsums to needlessly report false positives:

> $ aptitude remove tct sleuthkit
> $ aptitude install tct
> $ aptitude install sleuthkit
> $ debsums tct |grep mact
> $ debsums tct |grep -vw OK$
> /usr/bin/mactime                                                          FAILED
> /usr/bin/ils                                                              FAILED
> /usr/share/man/man1/ils.1.gz                                              FAILED
> /usr/share/man/man1/mactime.1.gz                                          FAILED

> Not only that, but the previous "alternatives" configuration is
> effectively ignored (although changes are not permanently lost..).

I can't reproduce the debsum missmatch:

# dpkg --list tct sleuthkit
[...]
ii  sleuthkit      3.0.1-5        collection of tools for forensics analysis on volume and file system data
ii  tct            1.18-4+b1      collection of forensics related utilities

# debsums -a tct | grep -v 'OK$'
# debsums -a sleuthkit | grep -v 'OK$'
#

Though I support your suggestion regarding the use of the
update-alternatives mechanism within tct.

Christophe: there's a patch by Martin Godisch available within
#219010 which provides the according update-alternatives mechanism.
Any objections against including it?

regards,
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/forensics-devel/attachments/20090930/7dc7bccc/attachment-0001.pgp>


Reply to: