Package: scalpel Version: 1.60-10 Severity: grave Tags: patch Justification: renders package unusable X-Debbugs-Cc: goldenrich...@gmail.com
Dear Maintainer, * What led up to the situation? I am the author of Scalpel. Execution of Scalpel 1.60 (the version that is currently in the scalpel package on Debian et al) fails completely on VMs hosted on Apple Silicon because of some long-standing memory corruption bugs. It may also work incorrectly on other platforms. * What exactly did you do (or not do) that was effective (or ineffective)? I have placed updated source distros for Scalpel 1.60 as well as the newer (and more powerful) Scalpel 2.02 on GitHub via https://github.com/nolaforensix/scalpel-1.60 and https://github.com/nolaforensix/scalpel-2.02. My recommendation is to rebuild the 1.60 package from the updated source and also consdering adding 2.02. * What was the outcome of this action? Scalpel is broken and I fixed it :) * What outcome did you expect instead? N/A? -- System Information: Distributor ID: Kali Description: Kali GNU/Linux Rolling Release: 2023.4 Codename: kali-rolling Architecture: x86_64 Kernel: Linux 6.5.0-kali3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages scalpel depends on: ii libc6 2.37-12 scalpel recommends no packages. scalpel suggests no packages. -- no debconf information