Your message dated Sat, 17 Dec 2016 00:32:09 +0100 with message-id <874m231mdi....@msgid.hilluzination.de> and subject line Not a problem with plaso 1.5.1 has caused the Debian Bug report #831446, regarding plaso: log2timeline.py fail cannot import name protobuf_serializer to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 831446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: plaso Version: 1.4.0+dfsg-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I try to use plaso * What exactly did you do (or not do) that was effective (or ineffective)? I want to use log2timeline.py * What was the outcome of this action? #log2timeline.py Traceback (most recent call last): File "/usr/bin/log2timeline.py", line 25, in <module> from plaso.frontend import log2timeline File "/usr/lib/python2.7/dist-packages/plaso/frontend/log2timeline.py", line 15, in <module> from plaso import output # pylint: disable=unused-import File "/usr/lib/python2.7/dist-packages/plaso/output/__init__.py", line 11, in <module> from plaso.output import pstorage File "/usr/lib/python2.7/dist-packages/plaso/output/pstorage.py", line 8, in <module> from plaso.storage import zip_file File "/usr/lib/python2.7/dist-packages/plaso/storage/zip_file.py", line 101, in <module> from plaso.serializer import protobuf_serializer File "/usr/lib/python2.7/dist- packages/plaso/serializer/protobuf_serializer.py", line 6, in <module> from dfvfs.serializer import protobuf_serializer as dfvfs_protobuf_serializer ImportError: cannot import name protobuf_serializer * What outcome did you expect instead? Working as expected :-) *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (104, 'stable-updates'), (104, 'proposed-updates'), (104, 'stable'), (103, 'experimental'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plaso depends on: ii ipython 2.4.1-1 ii python-binplist 0.1.5-1 ii python-bittorrent 3.4.2-12 ii python-construct 2.5.2-0.1 ii python-dateutil 2.4.2-1 ii python-dfvfs 20160510-1 ii python-dpkt 1.8.r98-0.1 ii python-hachoir-core 1.3.3-4 ii python-hachoir-metadata 1.3.3-2 ii python-hachoir-parser 1.3.4-2 ii python-libbde 20160418-2 ii python-libesedb 20151213-1 ii python-libevt 20160421-1 ii python-libevtx 20160421-1 ii python-libewf 20140608-6+b1 ii python-libfsntfs 20160418-1 ii python-libfwsi 20160110-1 ii python-liblnk 20160420-1 ii python-libmsiecf 20160421-1 ii python-libolecf 20160423-1 ii python-libqcow 20160123-2 ii python-libregf 20160424-1 ii python-libsigscan 20160312-1 ii python-libsmdev 20160320-1 ii python-libsmraw 20160424-1 ii python-libvhdi 20160424-1 ii python-libvmdk 20160119-3 ii python-libvshadow 20160110-2 ii python-pefile 2016.3.28-3 ii python-protobuf 2.6.1-2 ii python-psutil 4.2.0-1 ii python-pyparsing 2.1.5+dfsg1-1 ii python-requests 2.10.0-2 ii python-six 1.10.0-3 ii python-tsk 20160325-1 ii python-tz 2015.7+dfsg-0.1 ii python-xlsxwriter 0.7.3-1 ii python-yaml 3.11-3+b1 ii python-zmq 15.2.0-1 pn python:any <none> plaso recommends no packages. plaso suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---control: fixed -1 1.5.1+dfsg-3 The reason for this bug was that the module in question was removed from dfvfs at some point. Upgrading plaso to 1.5.1+dfsg-3 should make the problem go away -- I can no longer reproduce it in an otherwise clean unstable chroot. Cheers, -Hilko
--- End Message ---
_______________________________________________ forensics-devel mailing list forensics-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel
