Package Details: scalpel-git r31.35e1367-1

Git Clone URL: https://aur.archlinux.org/scalpel-git.git (read-only, click to copy)
Package Base: scalpel-git
Description: Recover files based on their headers, footers and internal data structures. This program is based on Foremost.
Upstream URL: https://github.com/sleuthkit/scalpel
Licenses: Apache
Conflicts: scalpel
Provides: scalpel
Submitter: m3tamantra
Maintainer: willemw
Last Packager: willemw
Votes: 80
Popularity: 0.000072
First Submitted: 2014-05-24 13:25 (UTC)
Last Updated: 2021-06-25 13:21 (UTC)

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

1 2 3 4 5 Next › Last »

willemw commented on 2021-10-08 05:41 (UTC) (edited on 2021-10-08 15:15 (UTC) by willemw)

@Kaiya: Clear your build cache:

rm -rf /home/<redacted>/.cache/yay/scalpel-git

C0rn3j commented on 2021-10-07 11:42 (UTC) (edited on 2021-10-07 11:45 (UTC) by C0rn3j)

Compiles just fine. Build the package manually without relying on AUR helpers.

This package is not out-of-date, tagging it so is not helpful.

https://wiki.archlinux.org/title/Arch_User_Repository#Installing_and_upgrading_packages

Kaiya commented on 2021-10-07 11:32 (UTC)

Currently aborts with.

==> Retrieving sources...
==> ERROR: /home/<redacted>/.cache/yay/scalpel-git/scalpel-git is not a clone of https://github.com/sleuthkit/scalpel.git
    Aborting...

When installing via git clone and manually following instructions, I can't compile. For specifying -std=c++14, I tried to add that to the lines referring to gcc in the Makefile, but did not manage to compile. How to do this?

willemw commented on 2021-06-12 11:23 (UTC)

@C0rn3j: Thanks. Your suggestion worked.

C0rn3j commented on 2021-06-12 10:10 (UTC)

Does not build with gcc 11 which seems to default to C++17, specifying --std=c++14 would probably help, didn't test.

willemw commented on 2016-04-18 09:14 (UTC)

The pkgver is already according to the wiki. It is maybe nice to have, but why change/improve it beyond the guidelines? The project hasn't been updated since 3 years ago, so the version is unlikely going to change. Even then, increasing the epoch would also not really be necessary, since nothing really changed (in PKGBUILD), only the version. A downgrade in pkgver in a VCS package is not an issue (if nothing changed in PKGBUILD), because it is normally you, the user, who decides when to upgrade VCS packages.

dreieck commented on 2016-04-18 07:53 (UTC) (edited on 2016-04-18 07:54 (UTC) by dreieck)

Can you please change "pkgver()" such, that it includes the version number, i.e. that what "scalpel -V" would output? It should be present in some source file, so you can parse it within "pkgver()". The format of the output of "pkgver()" should then be ${version}.r${release}, see Right now, only the r${release} is there. See http://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver.28.29_function, http://wiki.archlinux.org/index.php/PKGBUILD#Version. Since you would be updating the format of pkgver, you als need to increase epoch by 1 (i.e. set "epoch=1" if not specified yet).

LucasHenderson commented on 2015-11-22 17:44 (UTC)

No longer compiles for me, full of errors like /usr/include/libio.h:306:3: error: ‘size_t’ does not name a type size_t __pad5; ^ /usr/include/libio.h:310:67: error: ‘size_t’ was not declared in this scope char _unused2[15 * sizeof (int) - 4 * sizeof (void *) - sizeof (size_t)]; ^ In file included from /usr/include/stdio.h:74:0, from /usr/include/jni.h:48, from libscalpel_jni.h:2, from libscalpel_jni.cpp:75: /usr/include/libio.h:338:62: error: ‘size_t’ has not been declared typedef __ssize_t __io_read_fn (void *__cookie, char *__buf, size_t __nbytes); ^ /usr/include/libio.h:347:6: error: ‘size_t’ has not been declared size_t __n);

m3tamantra commented on 2014-10-22 16:27 (UTC)

Ok thank you for the info. I changed it in the PKGBUILD file. The package is also under the right license now (GPL -> Apache2.0).

willemw commented on 2014-10-22 15:06 (UTC)

Yes, PKGBUILD file misses: makedepends=('git')

1 2 3 4 5 Next › Last »