SBo scripts not building on current (read 1st post, pls)

SpacePlod · 12-07-2021, 08:20 AM

Zathura won't build on current right now. Girara (its only dep) needs a version bump 0.3.0 > 0.3.6 in order for Zathura to compile.

I'd send a patch, but I can't get the dang git tag to download correctly.

pghvlaans · 12-07-2021, 08:45 AM

Code:

wget https://github.com/pwmt/girara/archive/0.3.6/girara-0.3.6.tar.gz

worked for me. Everything compiled fine after that.

SpacePlod · 12-07-2021, 09:05 AM

Quote:

Originally Posted by pghvlaans

Code:

wget https://github.com/pwmt/girara/archive/0.3.6/girara-0.3.6.tar.gz

worked for me. Everything compiled fine after that.

Thanks. I could swear I tried that (just editing the version in .info). I need more coffee.

camerabambai · 12-08-2021, 04:54 PM

chrootkit 404

Code:

chkrootkit not found in /var/cache/sbopkg.
--2021-12-08 23:53:18--  ftp://ftp.pangeia.com.br/pub/seg/pac/chkrootkit-0.54.tar.gz
           => «chkrootkit-0.54.tar.gz»
Risoluzione di ftp.pangeia.com.br (ftp.pangeia.com.br)... 187.33.4.179
Connessione a ftp.pangeia.com.br (ftp.pangeia.com.br)|187.33.4.179|:21... non riuscito: Connessione rifiutata.

marav · 12-08-2021, 05:15 PM

Quote:

Originally Posted by camerabambai

chrootkit 404

Code:

chkrootkit not found in /var/cache/sbopkg.
--2021-12-08 23:53:18--  ftp://ftp.pangeia.com.br/pub/seg/pac/chkrootkit-0.54.tar.gz
           => «chkrootkit-0.54.tar.gz»
Risoluzione di ftp.pangeia.com.br (ftp.pangeia.com.br)... 187.33.4.179
Connessione a ftp.pangeia.com.br (ftp.pangeia.com.br)|187.33.4.179|:21... non riuscito: Connessione rifiutata.

doesn't work for me either

Code:

blackstar :: ~ » telnet ftp.pangeia.com.br 21
Trying 187.33.4.179...
telnet: connect to address 187.33.4.179: Connection refused

chrisretusn · 12-09-2021, 02:27 AM

checkrookit is available on https://launchpad.net/chkrootkit, latest version is 0.55

http://www.chkrootkit.org/ is also down.

Mechanikx · 12-10-2021, 03:16 PM

i3lock-2.10 doesn't build on -current.

I've updated the i3-lock slackbuild, i3lock.info, slack-desc, and README for version 2.13. Here are the diffs.

i3lock.SlackBuild:

Quote:

--- i3lock.SlackBuild 2021-12-10 12:43:37.442873696 -0800
+++ i3lock.SlackBuild.new 2021-12-10 13:18:07.889678848 -0800
@@ -25,7 +25,7 @@
cd $(dirname $0) ; CWD=$(pwd)

PRGNAM=i3lock
-VERSION=${VERSION:-2.10}
+VERSION=${VERSION:-2.13}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}
PKGTYPE=${PKGTYPE:-tgz}
@@ -79,21 +79,19 @@
$ -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
-o -perm 440 -o -perm 400 $ -exec chmod 644 {} \;

-# This patch removes all the PAM-related code,
-# and checks the password against shadow instead.
-patch -p0 -i $CWD/i3lock-2.10-no-pam.patch
+autoreconf --force --install

-make install DESTDIR=$PKG
+rm -rf build/
+mkdir -p build && cd build/
+
+../configure \
+ --prefix=/usr \
+ --sysconfdir=/etc \
+ --disable-sanitizers \
+ --mandir=/usr/man

-# i3lock needs setuid to make sure it isn't killed by the kernel and to read shadow.
-# Don't worry, the privileges are dropped really soon after starting
-# and everything else runs without privileges.
-chown 0.0 $PKG/usr/bin/i3lock
-chmod 4751 $PKG/usr/bin/i3lock
-# We need setuid to set the out of memory score, and drop permissions once done.
-# This makes the program's init slightly more insecure, since we'd only need
-# setgid to change the group to shadow to read the password, otherwise.
-# In fact, both Slackware's xlock and xscreensaver use (root.shadow 2751) as permissions.
+make install DESTDIR=$PKG
+cd $TMP/$PRGNAM-$VERSION

find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \
| cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
@@ -105,7 +103,7 @@
for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done

mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
-cp -a CHANGELOG LICENSE LICENSE-slock README.md $PKG/usr/doc/$PRGNAM-$VERSION
+cp -a CHANGELOG LICENSE README.md $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild

mkdir -p $PKG/install

i3lock.info:

Quote:

--- i3lock.info 2021-12-10 12:43:46.922872804 -0800
+++ i3lock.info.new 2021-12-10 12:39:21.144897816 -0800
@@ -1,8 +1,8 @@
PRGNAM="i3lock"
-VERSION="2.10"
+VERSION="2.13"
HOMEPAGE="https://i3wm.org/i3lock/"
-DOWNLOAD="https://i3wm.org/i3lock/i3lock-2.10.tar.bz2"
-MD5SUM="a496ec274c2f75bbefaa088c4d18ec85"
+DOWNLOAD="https://i3wm.org/i3lock/i3lock-2.13.tar.bz2"
+MD5SUM="a10993d6cd409d980f78a4a376885f1b"
DOWNLOAD_x86_64=""
MD5SUM_x86_64=""
REQUIRES="libev"

slack-desc:

Quote:

--- slack-desc 2021-12-10 12:45:15.506864467 -0800
+++ slack-desc.new 2021-12-10 12:21:08.385000655 -0800
@@ -13,7 +13,6 @@
i3lock: (you can configure the color/an image).
i3lock: You can return to your screen by entering your password.
i3lock:
-i3lock: This version is patched to not to use PAM.
i3lock:
i3lock: Homepage: https://i3wm.org/i3lock/
i3lock:

README:

Quote:

--- README 2021-12-10 12:49:37.994839765 -0800
+++ README.new 2021-12-10 12:49:26.305840865 -0800
@@ -1,7 +1 @@
i3lock is a simple screen locker like slock.
-
-This SlackBuild patches i3lock to not to use PAM, and is as such
-usable in Slackware. For verifying the password it uses shadow
-instead. Because of that, it needs suid permissions, but those
-privileges are dropped as soon as possible. The code for this was
-taken from slock. See the patch and LICENSE-slock.

Since Slackware now includes pam there is no need for the no-pam patch.

It builds and works fine on my system but this is my first time updating a package so I hope I've done everything correctly.

Mechanikx · 12-10-2021, 06:59 PM

Just a small correction to the ufw README.

README:

Quote:

Add the following code to /etc/rc.local to start Ufw at boot time:

I believe should be changed to:

Quote:

Add the following code to /etc/rc.d/rc.local to start Ufw at boot time:

Quote:

--- README 2021-12-10 16:45:58.959968598 -0800
+++ README.new 2021-12-10 16:51:05.854946594 -0800
@@ -2,7 +2,7 @@
It provides a command line interface and aims to be uncomplicated and easy
to use.

-Add the following code to /etc/rc.local to start Ufw at boot time:
+Add the following code to /etc/rc.d/rc.local to start Ufw at boot time:

if [ -x /lib/ufw/ufw-init ]; then
/lib/ufw/ufw-init start

willysr · 12-10-2021, 09:14 PM

Fixed, thanks

willysr · 12-10-2021, 09:26 PM

Quote:

Originally Posted by Mechanikx

i3lock-2.10 doesn't build on -current.

I've updated the i3-lock slackbuild, i3lock.info, slack-desc, and README for version 2.13. Here are the diffs.

i3lock.SlackBuild:

i3lock.info:

slack-desc:

README:

Since Slackware now includes pam there is no need for the no-pam patch.

It builds and works fine on my system but this is my first time updating a package so I hope I've done everything correctly.

Thanks, i pushed it to my branch with some modifications

willysr · 12-10-2021, 09:35 PM

Quote:

Originally Posted by chrisretusn

checkrookit is available on https://launchpad.net/chkrootkit, latest version is 0.55

http://www.chkrootkit.org/ is also down.

Fixed now in my branch

camerabambai · 12-11-2021, 01:43 AM

Some advice about linphone.
Compile fine, but enable only zrtp encryption(not supported by Asterisk as I know), to enable dtls and srtp I add to slackbuild this line(libsrtp and mbedtls must be installed first)

Code:

  --enable-dtls \
  --with-srtp=/usr \

. The package linphone doesn't search libsrtp.a in /usr/lib64 but search it in /usr/lib, i have "solved" making a symlink(sic!) compiling linphone and then remove the symlink
At least linphone works with srtp.

USUARIONUEVO · 12-17-2021, 04:27 PM

Hi , i buy new notebook , with ryzen 7 5700u , when try build libtorrent-rasterbar , system freezes.

Solution for me is

Quote:

make -j1
make -j1 install-strip

Im not test if some new release builds fine , only provide solution for actual version from SBo.

Thanks for all work.

Ilgar · 12-24-2021, 11:37 AM

Hi all,

Today (Dec 24th) I upgraded my -current system and SBo-git repo to their most recent versions. While trying to build zulu-openjdk8 I get the following error:

Code:

Processing zulu-openjdk8

zulu-openjdk8:
Found zulu8.58.0.13-ca-jdk8.0.312-linux_x64.tar.gz in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for zulu8.58.0.13-ca-jdk8.0.312-linux_x64.tar.gz ... OK
Building package for zulu-openjdk8...
Architecture x86_64 is not supported.

I also tried zulu-openjdk11, it was the same. Some inspection revealed that it is this bit causing the error:

Code:

if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i686 ;;
    x86_64) ARCH=x64 ;;
  esac
fi

It turns out that ARCH is NOT a null string right before this code runs (it's x86_64 in my case), therefore the block inside the "if" never executes, causing this later check to fail:

Code:

if [ "$ARCH" = "i686" ]; then
  LIB_ARCH=i686
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "x64" ]; then
  LIB_ARCH=amd64
  LIBDIRSUFFIX="64"
else
  echo "Architecture ${ARCH} is not supported."
  exit 1
fi

Eliminating the first if check above and running the inner code unconditionally solves the problem.

Ilgar · 12-24-2021, 01:43 PM

Another one that does not build is golang-googlecode-gotools. Here is the error:

Code:

Processing golang-googlecode-gotools

golang-googlecode-gotools:
Found go.tools-588451.tar.gz in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for go.tools-588451.tar.gz ... OK
Building package for golang-googlecode-gotools...
WORK=/tmp/go-build304747255
go: go.mod file not found in current directory or any parent directory; see 'go help modules'

From what I found on Google, some module initialization should be made. I tried adding

Code:

go mod init ${IMPORT_PATH}

and a similar "go mod tidy" line right before the main build stage, but other erros got in the way and I gave up. I am not familiar with the Go build system so I am not the least bit sure if I was trying something sensible, but in any case, the script does not build as-is.