Processed: Re: md5deep: sudo md5deep -rel /* leads to system crash

Processing control commands: > tags 841447 moreinfo Bug #841447 [md5deep] md5deep: sudo md5deep -rel /* leads to system crash Added tag(s) moreinfo. -- 841447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#848881: [gpart] Floating point exception when scanning

Am 20.12.2016 um 18:24 schrieb Baruch Even : > Can you please run it under gdb and capture the output of the command: > bt > bt full Reading symbols from /usr/sbin/gpart...(no debugging symbols found)...done. (gdb) r Starting program: /usr/sbin/gpart -f /dev/lv/Elite3 Program

Bug#848881: [gpart] Floating point exception when scanning

Can you please run it under gdb and capture the output of the command: bt bt full Baruch On Tue, Dec 20, 2016, 18:32 Eriberto Mota wrote: > Control: severity 848881 important > > Hi, > > Adding Baruch (upstream) in Cc. > > I downgraded the severity to important because

volatility 2.5+git20161121.ecd8a54-1 MIGRATED to testing

FYI: The status of the volatility source package in Debian's testing distribution has changed. Previous version: 2.5+git20161026.75fb034-1 Current version: 2.5+git20161121.ecd8a54-1 -- This email is automatically generated once a day. As the installation of new packages into testing

Bug#848881: [gpart] Floating point exception when scanning

Control: severity 848881 important Hi, Adding Baruch (upstream) in Cc. I downgraded the severity to important because this bug is not grave (maybe it could be normal). Baruch, any idea? Regards, Eriberto 2016-12-20 11:33 GMT-02:00 Ingo Juergensmann : > Package:

Bug#848881: [gpart] Floating point exception when scanning

Package: gpart Version: 1:0.3-3 Severity: grave --- Please enter the report below this line. --- Hi! When trying to examine a volume on LVM, I get a floating point exception quite instantly: # strace -f gpart -f /dev/lv/Elite3 execve("/usr/sbin/gpart", ["gpart", "-f", "/dev/lv/Elite3"], [/* 59

Bug#848666: rkhunter: should recommend s-nail instead of heirloom-mailx - or not at all

* Jonas Smedegaard [Mon Dec 19, 2016 at 12:11:22PM +0100]: > heirloom-mailx is now a transitional package depending on s-nail. > S-nail does not offer same ABI as mailx (see bug#846062). > If s-nail ABI is really supported, then rkhunter should recommend > s-nail instead of heirloom-mailx, or

Processed: severity of 848666 is important

Processing commands for cont...@bugs.debian.org: > severity 848666 important Bug #848666 [rkhunter] rkhunter: should recommend s-nail instead of heirloom-mailx - or not at all Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance.