Re: [Slackbuilds-users] maintainer status report
On 23/12/30 08:26AM, Willy Sudiarto Raharjo wrote: > the full report can be seen here > https://slackbuilds.org/maintainer_status.html > It looks like I need to make my email address in the info files a bit more consistent. This report has me maintaining 3 slackbuilds. That seems off by about 75 (or there about). > > -- > Willy Sudiarto Raharjo > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] rustup-1.26.0
On 23/08/13 07:48AM, John wrote: > Yes Eric > I discovered that, even though I had the shims installed my $PATH was not > set properly. Barry's response got me thinking about that and enabled me to > find my error and correct it. The $PATH had been properly set in the past. > I must have changed it for some reason. > Thank You > John Same here. Shims installed, user path set up, but not the system. Much appreciated. Barry > On Sat, Aug 12, 2023 at 10:55 PM Erich Ritz via SlackBuilds-users < > slackbuilds-users@slackbuilds.org> wrote: > > > --- Original Message --- > > On Saturday, August 12th, 2023 at 2:00 PM, Barry J. Grundy < > > bgru...@linuxleo.com> wrote: > > > > > > > > > > > > > On 23/08/12 12:35PM, John wrote: > > > > > > > Greetings List > > > > Rustup-1.26.0 fails to build for me with the following errors: > > > > > > > > --error: failed to get `anyhow` as a dependency of package `download > > v1.26.0 (/tmp/SBo/rustup-1.26.0/download)` > > > > Caused by: > > > > failed to load source for dependency `anyhow` > > > > Caused by: > > > > Unable to update registry `crates-io` > > > > Caused by: > > > > failed to update replaced source registry `crates-io` > > > > Caused by: > > > > failed to parse manifest at > > > > `/tmp/SBo/rustup-1.26.0/vendor/fs_at-0.1.3/Cargo.toml` > > > > Caused by: > > > > namespaced features with the `dep:` prefix are only allowed on the > > nightly > > > > channel and requires the `-Z namespaced-features` flag on the > > command-line > > > > > > > > Any help is greatly appreciated for my System76 also needs > > System76-power > > > > which requires rustup > > > > Thanks > > > > john > > > > > > > > > Interesting. Rustup installed fine for me, and after following the > > > README instructions, I tried to install system76-power and recieved a > > > very similar error to yours above: > > > > > > error: failed to get `clap` as a dependency of package `system76-power > > v1.1.25 (/tmp/SBo/system76-power-fc8eb49fae5222da56dcfa414ef2b190e9f870c7)` > > > > > > Caused by: > > > failed to load source for dependency `clap` > > > > > > Caused by: > > > Unable to update registry `crates-io` > > > > > > Caused by: > > > failed to update replaced source registry `crates-io` > > > > > > Caused by: > > > failed to parse manifest at > > `/tmp/SBo/system76-power-fc8eb49fae5222da56dcfa414ef2b190e9f870c7/vendor/anstream-0.3.2/Cargo.toml` > > > > > > Caused by: > > > namespaced features with the `dep:` prefix are only allowed on the > > nightly channel and requires the `-Z namespaced-features` flag on the > > command-line > > > make: *** [Makefile:62: target/release/system76-power] Error 101 > > > Failures: > > > system76-power: system76-power.SlackBuild return non-zero > > > > > > > I think you didn't configure your system to prefer rustup over system > > rust. See this user with the same error: > > > > > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2023-January/027714.html > > > > > > > > But again, rustup installed fine. > > > > > > Barry > > > ___ > > > SlackBuilds-users mailing list > > > SlackBuilds-users@slackbuilds.org > > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > > FAQ - https://slackbuilds.org/faq/ > > > > Erich > > ___ > > SlackBuilds-users mailing list > > SlackBuilds-users@slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > > > -- > Life expectancy in a firefight > Radio Man 3 seconds > Medic 7 seconds > Officer whenever they get around to it. > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] rustup-1.26.0
On 23/08/12 12:35PM, John wrote: > Greetings List > Rustup-1.26.0 fails to build for me with the following errors: > > --error: failed to get `anyhow` as a dependency of package `download > v1.26.0 (/tmp/SBo/rustup-1.26.0/download)` > Caused by: > failed to load source for dependency `anyhow` > Caused by: > Unable to update registry `crates-io` > Caused by: > failed to update replaced source registry `crates-io` > Caused by: > failed to parse manifest at > `/tmp/SBo/rustup-1.26.0/vendor/fs_at-0.1.3/Cargo.toml` > Caused by: > namespaced features with the `dep:` prefix are only allowed on the nightly > channel and requires the `-Z namespaced-features` flag on the command-line > > Any help is greatly appreciated for my System76 also needs System76-power > which requires rustup > Thanks > john Interesting. Rustup installed fine for me, and after following the README instructions, I tried to install system76-power and recieved a very similar error to yours above: error: failed to get `clap` as a dependency of package `system76-power v1.1.25 (/tmp/SBo/system76-power-fc8eb49fae5222da56dcfa414ef2b190e9f870c7)` Caused by: failed to load source for dependency `clap` Caused by: Unable to update registry `crates-io` Caused by: failed to update replaced source registry `crates-io` Caused by: failed to parse manifest at `/tmp/SBo/system76-power-fc8eb49fae5222da56dcfa414ef2b190e9f870c7/vendor/anstream-0.3.2/Cargo.toml` Caused by: namespaced features with the `dep:` prefix are only allowed on the nightly channel and requires the `-Z namespaced-features` flag on the command-line make: *** [Makefile:62: target/release/system76-power] Error 101 Failures: system76-power: system76-power.SlackBuild return non-zero But again, rustup installed fine. Barry ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] pytho2-config/python2-lz4
Good Day, I am in the process of trying to catch up with my builds this week. I maintain both the python 2 and 3 versions of python-lz4, which requires python-pkgconfig. I maintain these as dependancies of plaso. Plaso has moved on to the python3 version only, and I see no other builds that depend on python2-lz4 or python2-pkgconfig. Can these be removed, or does someone what to take them over? Thanks, Barry bgru...@linuxleo.com ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] python/pysqlite can be removed
python/pysqlite is largely unmaintained upstream (replaced by sqlite3 in the python standard library). As far as I can tell nothing depends on it anymore. Unless someone sees a reason to maintain it, can it be removed? Thanks, Barry ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] [PATCH] office/catdoc: Update for version 0.95
Good morning,
The version of office/catdoc on SBo is over 16 years old, and while it
builds, it segfaults at runtime. I contacted the maintainer and never
heard back.
The attached patch is an update to the latest version (still over 5
years old), which builds and runs without segfault. I doubt there will
be many updates to follow.
Note that there is no license in the original script as required by the
instructions at SBo for SlackBuilds. I would not know how to add one to
someone else's script. This is just a functional patch.
Thanks,
BarryFrom 79856c3eefe0023f507031929e96075e94d05550 Mon Sep 17 00:00:00 2001
From: "Barry J. Grundy"
Date: Fri, 20 May 2022 13:39:46 -0400
Subject: [PATCH] office/catdoc: Updated for version 0.95
Signed-off-by: Barry J. Grundy
---
office/catdoc/catdoc.SlackBuild | 12 ++--
office/catdoc/catdoc.info | 6 +++---
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/office/catdoc/catdoc.SlackBuild b/office/catdoc/catdoc.SlackBuild
index d679224a1b..d39065a826 100644
--- a/office/catdoc/catdoc.SlackBuild
+++ b/office/catdoc/catdoc.SlackBuild
@@ -8,14 +8,14 @@
cd $(dirname $0) ; CWD=$(pwd)
PRGNAM=catdoc
-VERSION=${VERSION:-0.94.2}
-BUILD=${BUILD:-2}
+VERSION=${VERSION:-0.95}
+BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}
PKGTYPE=${PKGTYPE:-tgz}
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
-i?86) ARCH=i486 ;;
+i?86) ARCH=i586 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
@@ -33,8 +33,8 @@ TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}
-if [ "$ARCH" = "i486" ]; then
- SLKCFLAGS="-O2 -march=i486 -mtune=i686"
+if [ "$ARCH" = "i586" ]; then
+ SLKCFLAGS="-O2 -march=i586 -mtune=i686"
LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
SLKCFLAGS="-O2 -march=i686 -mtune=i686"
@@ -103,7 +103,7 @@ find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \
mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a \
- CODING.STD COPYING CREDITS INSTALL INSTALL.dos NEWS README TODO \
+ CODING.STD COPYING NEWS README TODO \
$PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
diff --git a/office/catdoc/catdoc.info b/office/catdoc/catdoc.info
index 0f61762e32..b45f152e84 100644
--- a/office/catdoc/catdoc.info
+++ b/office/catdoc/catdoc.info
@@ -1,8 +1,8 @@
PRGNAM="catdoc"
-VERSION="0.94.2"
+VERSION="0.95"
HOMEPAGE="http://www.wagner.pp.ru/~vitus/software/catdoc/;
-DOWNLOAD="http://ftp.wagner.pp.ru/pub/catdoc/catdoc-0.94.2.tar.gz;
-MD5SUM="243e1680bb3e703616f5adecfee24491"
+DOWNLOAD="http://ftp.wagner.pp.ru/pub/catdoc/catdoc-0.95.tar.gz;
+MD5SUM="4ece2f43b140fab6a2c3a9d6436d7779"
DOWNLOAD_x86_64=""
MD5SUM_x86_64=""
REQUIRES=""
--
2.35.3
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Volatility/pythonX-yara
Good Afternoon, I'm trying to submit the following updates (via SBo form): python2-yara (update/rename/split) volatility(fix dependency name changes[python2-distorm and python2-yara]) python3-yara (update/rename/split) volatility3 (added-rewrite of volatility framework) I cannot get the pythonX-yara submissions to upload because it says they are already in pending (they are not). And there is already a package in pending for volatility that fixes only one of the dependency names (I did not submit that change). I may have screwed something up, but I had submitted all of the above last week and they were rejected because neither python-yara package would build against the older yara already in 15.0, even though the correct version of yara was submitted along side them (and was approved). Did I miss something? Thanks, Barry ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] udiskie builds but fails to run on 15.0
Hello all, system/udiskie requires "gi" to run (from pygobject3). It's currently built using python2 with docopt and python2-PyYAML as deps. The build completes without error, but will not run (module gi not found). Building for python3 fixes the issue. Pygobject3 and python(3)-PyYAML are included in 15.0. The docopt SB already includes py3 support. So the only dep is now docopt. Thanks, Barry ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Any help?
I have tested all my SlackBuilds as the currently sit in the master repo. They all compile without error. I have plenty of updates and new submissions to add once submissions are open again. In the meantime I'm wondering if there is a list of SlackBuilds we can test or that need some attention. Any other way the larger community can help with the workload? Thanks for all the hard work, Barry ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Orphans
In the process of updating my SlackBuilds, I came across several packages that I no longer need. If anyone would like to take them over, please do so. Otherwise I'll likely abandon them. As far as I can tell no other packages depend on these. python/backports.lzma python/binplist python/biplist python/construct python/dotty python/hachoir-core python/hachoir-metadata python/hachoir-parser python/pysqlite (no longer maintained upstream) Thanks, Barry ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Python (Again!)
On 4/20/21 7:05 PM, Robby Workman wrote: We are still in the "we don't know yet" phase of this. We will update everyone with a definitive answer once arrive at one :-) -RW Thanks Robby. I'll stop thinking about it now. :-) ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Python (Again!)
On 4/20/21 5:52 PM, Jeremy Hansen wrote: On Tue, Apr 20, 2021, 2:59 PM Barry J. Grundy <mailto:bgru...@gmail.com>> wrote: I know this has come up before and perhaps been answered and I've also read through the related threads on LQ, but I still have not seen a definitive answer (if there is one): Since python2 is EOL and -current/15 ships with python3, is it good practice now to build python packages with python3 by default? If so, then what's the best way to handle the multiple versions? This discussion was had on the list back in Feb of '19, but I don't see anything definitive. For example, I maintain dpkt. The version in the -current (ponce's) repo works, but I have an update ready to go when submissions open again. Right now dpkt builds for python2. Here's my question: My "ready to go" update switches to python3 by default and uses a "PYTHON2=yes" option to build python2 modules if the user wants. Would it be better to create python3-dpkt and leave the dpkt script at python2? I see it both ways in the 14.2 repo. Another probably better example is distorm, which is a requirement for volatility (which is python2 only). volatility3 is a separate re-write for python3 with different prerequisites (and I already have a slackbuild to submit for that when things open again). So for volatility it makes sense to leave distorm as is. I can submit a separate python3-distorm script when I submit volatility3. Perhaps with the submissions freeze it would be a good time to either separate the scripts or at least decide on a "best practice". My apologies if I'm simply kicking a dead horse here. Thanks, Barry In my opinion, I think SBo for 15.0 should default to python3 for any packages and python2 should be something that can be optional (for those packages that support both). If there's a need to have separate python2 and python3 packages, the python3 package should not need an identifier in front of it, where the python2 package should ($PRGNAM for python3 and python2-$PRGNAM for python2). I agree with defaulting to python3 for 15.0. But right now we'd have $PRGNAM changing to python2-$PRGNAM and python3-$PRGNAM changing to $PRGNAM. Then when python4 comes out it would be a repeat of the same issue (maybe). Perhaps "python$VER-$PRGNAM" would be appropriate for everything. And perhaps I'm just over thinking it. But thanks for the responses. Barry ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Python (Again!)
I know this has come up before and perhaps been answered and I've also read through the related threads on LQ, but I still have not seen a definitive answer (if there is one): Since python2 is EOL and -current/15 ships with python3, is it good practice now to build python packages with python3 by default? If so, then what's the best way to handle the multiple versions? This discussion was had on the list back in Feb of '19, but I don't see anything definitive. For example, I maintain dpkt. The version in the -current (ponce's) repo works, but I have an update ready to go when submissions open again. Right now dpkt builds for python2. Here's my question: My "ready to go" update switches to python3 by default and uses a "PYTHON2=yes" option to build python2 modules if the user wants. Would it be better to create python3-dpkt and leave the dpkt script at python2? I see it both ways in the 14.2 repo. Another probably better example is distorm, which is a requirement for volatility (which is python2 only). volatility3 is a separate re-write for python3 with different prerequisites (and I already have a slackbuild to submit for that when things open again). So for volatility it makes sense to leave distorm as is. I can submit a separate python3-distorm script when I submit volatility3. Perhaps with the submissions freeze it would be a good time to either separate the scripts or at least decide on a "best practice". My apologies if I'm simply kicking a dead horse here. Thanks, Barry ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Spotify Version mismatch
It looks like there is a version mis-match between the .info and the
.SlackBuild file (for the 64bit version):
$ cat spotify.info
PRGNAM="spotify"
VERSION="1.1.10"
HOMEPAGE="https://www.spotify.com;
DOWNLOAD="http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.72.117.g6bd7cc73-35_i386.deb;
MD5SUM="c8e54d60452bda40f6de23f11c909b2d"
DOWNLOAD_x86_64="http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb;
...
And the SlackBuild:
PRGNAM=spotify
SRCNAM=spotify-client
VERSION=${VERSION:-1.1.42}
VERSION32=${VERSION32:-1.0.72}
BUILD=${BUILD:-2}
TAG=${TAG:-_SBo}
Thanks,
Barry
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Spotify version mismatch
It looks like there is a version mis-match between the .info and the
.SlackBuild file (for the 64bit version):
$ cat spotify.info
PRGNAM="spotify"
VERSION="1.1.10"
HOMEPAGE="https://www.spotify.com;
DOWNLOAD="http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.72.117.g6bd7cc73-35_i386.deb;
MD5SUM="c8e54d60452bda40f6de23f11c909b2d"
DOWNLOAD_x86_64="http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb;
...
And the SlackBuild:
PRGNAM=spotify
SRCNAM=spotify-client
VERSION=${VERSION:-1.1.42}
VERSION32=${VERSION32:-1.0.72}
BUILD=${BUILD:-2}
TAG=${TAG:-_SBo}
Thanks,
Barry
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20201206.1
On 12/7/20 6:53 AM, Luiz Carlos Ramos wrote: Hello, Barry, just out of curiosity, in your system, if you type javac -version, what do you get? In my system, it gave me things like: javac 1.7.0_281 or for the java runtime: java version "1.7.0_281" OpenJDK Runtime Environment (IcedTea 2.6.24) (Slackware) OpenJDK 64-Bit Server VM (build 24.281-b01, mixed mode) I traced these packages and in fact they belong to an OpenJDK (from Alien's repository) which obviously is not in the stock Slackware install. Anyway, in the build process some Java code was processed and it has code constructions which are not supported in Java 1.7. Now I feel that if the system has no Java installed at all, maybe the build process skips all these Java thing. To verify this, I would take some time to do it; so I won't try. At the INSTALL.txt, it is stated that Java is needed only to build "Java bindings". This may give some support to my "feeling" stated above. A more simpler test would be setting a system with Java 1.7 compiler (this is easy to do, setting the PATH environment variable accordingly) and trying to rebuild the package. It hopefully would give errors such the ones I saw here. Many thanks! Luiz Hi Luiz, On a clean 14.2 system I get "command not found" for javac. Which of course makes sense. I think the easiest solution for the SlackBuild is just to add "--disable-java" to the config and allow people to add it if they need to. If there's no issues with that I'll go ahead and change it and re-submit (with a note in the README for the option to enable). Thanks, Barry ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20201206.1
On 12/6/20 9:39 AM, Luiz Carlos Ramos wrote: Hello again, I had also some problems when building sleuthkit. Surprisingly at least for me there were some Java components, one or two of them which failed in the compilation phase. Investigating the issue, it was found that they need JDK 1.8 to be built (with JDK 1.7 the compilation fails). Putting jdk1.8 binary path in the $PATH environment variable could solve the problem in my system. I would suggest adding a note in the README file about that. Alternatively, a Java 1.8 package can be put as an explicit dependency (but which specific package would be selected?). Many thanks, Luiz Ramos lramos dot prof at yahoo dot com dot br São Paulo - Brazil Hi Luiz, I've tested and built sleuthkit 4.10.1 on a clean 14.2 system with no additional packages. I had no issues with any Java components. Perhaps I'm missing something? Thanks, Barry ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
