mirror of
https://github.com/overcuriousity/autopsy-flatpak.git
synced 2025-07-06 12:50:22 +00:00
updates
This commit is contained in:
parent
0f7affa6a0
commit
8230fda797
@ -16,7 +16,7 @@ sudo apt update && \
|
||||
build-essential autoconf libtool automake git zip wget ant \
|
||||
libde265-dev libheif-dev \
|
||||
libpq-dev \
|
||||
testdisk libafflib-dev libewf-dev libvhdi-dev libvmdk-dev \
|
||||
testdisk libafflib-dev libewf-dev libvhdi-dev libvmdk-dev libvslvm-dev \
|
||||
libgstreamer1.0-0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad \
|
||||
gstreamer1.0-plugins-ugly gstreamer1.0-libav gstreamer1.0-tools gstreamer1.0-x \
|
||||
gstreamer1.0-alsa gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-qt5 gstreamer1.0-pulseaudio
|
||||
|
@ -24,4 +24,8 @@ An error like "Local Solr Server did not respond to status request" or something
|
||||
|
||||
### There are no local disks for processing
|
||||
|
||||
Autopsy looks at the block devices in the `/dev` directory for local disks to process. If autopsy can't read block devices in that directory, it won't show the local disk. In most instances, starting autopsy with a command like `sudo -g disk autopsy` should give autopsy the right permissions to view local disks. This assumes that the `disk` group has read rights to local disks (i.e. `/dev/sda1`). Appropriate permissions can be determined by running something like `ls -l /dev` looking for the permissions required for the local disks. Then autopsy should be started in such a way that the `$USER` and `$HOME` are preserved (i.e. running as root may be problematic), but the user account and, consequently, autopsy, has sufficient permissions to access local disk block devices.
|
||||
Autopsy looks at the block devices in the `/dev` directory for local disks to process. If autopsy can't read block devices in that directory, it won't show the local disk. In most instances, starting autopsy with a command like `sudo -g disk autopsy` should give autopsy the right permissions to view local disks. This assumes that the `disk` group has read rights to local disks (i.e. `/dev/sda1`). Appropriate permissions can be determined by running something like `ls -l /dev` looking for the permissions required for the local disks. Then autopsy should be started in such a way that the `$USER` and `$HOME` are preserved (i.e. running as root may be problematic), but the user account and, consequently, autopsy, has sufficient permissions to access local disk block devices.
|
||||
|
||||
### Out of space error when building snap
|
||||
|
||||
It might be worth reinitializing lxd for building the image. This can be done by running `sudo snap remove --purge lxd` removing lxd and cached data. Run `sudo snap install lxd` and then `sudo snap lxd init` with defaults to reinitialize.
|
@ -121,10 +121,11 @@ apps:
|
||||
parts:
|
||||
sleuthkit:
|
||||
# more information on plugins here: https://snapcraft.io/docs/supported-plugins
|
||||
plugin: autotools
|
||||
plugin: nil
|
||||
source: https://github.com/sleuthkit/sleuthkit.git
|
||||
source-tag: sleuthkit-4.13.0
|
||||
build-environment: [JAVA_HOME: /usr/lib/jvm/java-17-openjdk-amd64]
|
||||
build-environment:
|
||||
- JAVA_HOME: /usr/lib/jvm/java-17-openjdk-amd64
|
||||
# information on packages here: https://snapcraft.io/docs/package-repositories
|
||||
build-packages:
|
||||
- build-essential
|
||||
@ -139,17 +140,25 @@ parts:
|
||||
- ant-optional
|
||||
- libpq-dev
|
||||
- testdisk
|
||||
- libvslvm-dev
|
||||
- libafflib-dev
|
||||
- libewf-dev
|
||||
- libvhdi-dev
|
||||
- libvmdk-dev
|
||||
- libstdc++6
|
||||
stage-packages:
|
||||
- libpq-dev
|
||||
- testdisk
|
||||
- libvslvm-dev
|
||||
- libafflib-dev
|
||||
- libewf-dev
|
||||
- libvhdi-dev
|
||||
- libvmdk-dev
|
||||
override-build: |
|
||||
./bootstrap
|
||||
./configure --enable-java
|
||||
make
|
||||
make install
|
||||
autopsy:
|
||||
after: [sleuthkit]
|
||||
# information on packages here: https://snapcraft.io/docs/package-repositories
|
||||
@ -235,9 +244,9 @@ parts:
|
||||
for snap in "core22" "gnome-42-2204"; do
|
||||
cd "/snap/$snap/current/usr/lib"
|
||||
for filename in [ *.so* ]; do
|
||||
rm -f "$CRAFT_PRIME/usr/lib/$CRAFT_ARCH_TRIPLET/$filename"
|
||||
rm -f "$CRAFT_PRIME/usr/lib/$CRAFT_ARCH_TRIPLET_BUILD_FOR/$filename"
|
||||
done
|
||||
cd "/snap/$snap/current/usr/lib/$CRAFT_ARCH_TRIPLET"
|
||||
cd "/snap/$snap/current/usr/lib/$CRAFT_ARCH_TRIPLET_BUILD_FOR"
|
||||
for filename in [ *.so* ]; do
|
||||
rm -f "$CRAFT_PRIME/usr/lib/$filename"
|
||||
done
|
||||
|
Loading…
x
Reference in New Issue
Block a user