From milgram at cgpp.com  Fri Apr  1 01:26:14 2022
From: milgram at cgpp.com (Judah Milgram)
Date: Thu, 31 Mar 2022 21:26:14 -0400
Subject: [Slackbuilds-users] GNU parallel
In-Reply-To: <CAC3J=Za-M_WqhmsBJ_x-dU0etW1yJohG+00g_A5RGLDTEBiCrw@mail.gmail.com>
References: <39459a21-589a-ebb6-910c-18e327e65df3@cgpp.com>
 <CAC3J=Za-M_WqhmsBJ_x-dU0etW1yJohG+00g_A5RGLDTEBiCrw@mail.gmail.com>
Message-ID: <e099413b-34b9-2ee8-10f8-17bb5162f819@cgpp.com>



I didn't know! Thanks, I'll check it out.


On 3/31/22 1:11 PM, Brandon Pribula wrote:

> 
> Just in case you didn't know and would like to see a real world example,
> the newest version of sbopkg specifically sqg uses gnu parallel. There's
> a big speed improvement.
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

-- 
Judah Milgram
milgram at cgpp.com
301-257-7069

From b.pribs11 at gmail.com  Fri Apr  1 01:59:01 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Thu, 31 Mar 2022 18:59:01 -0700
Subject: [Slackbuilds-users] GNU parallel
In-Reply-To: <e099413b-34b9-2ee8-10f8-17bb5162f819@cgpp.com>
References: <39459a21-589a-ebb6-910c-18e327e65df3@cgpp.com>
 <CAC3J=Za-M_WqhmsBJ_x-dU0etW1yJohG+00g_A5RGLDTEBiCrw@mail.gmail.com>
 <e099413b-34b9-2ee8-10f8-17bb5162f819@cgpp.com>
Message-ID: <CAC3J=ZYV=_=6tRrB+17c4Y9eGGtXgvOT=Uk4Z_8zbEONEoSVrQ@mail.gmail.com>

On Thu, Mar 31, 2022, 6:26 PM Judah Milgram, <milgram at cgpp.com> wrote:

>
>
> I didn't know! Thanks, I'll check it out.
>
>
> On 3/31/22 1:11 PM, Brandon Pribula wrote:
>
> >
> > Just in case you didn't know and would like to see a real world example,
> > the newest version of sbopkg specifically sqg uses gnu parallel. There's
> > a big speed improvement.
> >
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
>
> --
> Judah Milgram
> milgram at cgpp.com
> 301-257-7069
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/


No problem ;)

>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220331/9117567e/attachment.htm>

From arnaud.garcia-fernandez at laposte.net  Fri Apr  1 11:59:32 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Fri, 1 Apr 2022 13:59:32 +0200
Subject: [Slackbuilds-users] =?utf-8?q?Contacting_Audrius_Ka=C5=BEukauska?=
 =?utf-8?q?s?=
Message-ID: <20220401135932.0c6da4bfd3eae11373a50b72@laposte.net>

Hi!

	I've tried contacting Audrius Ka?ukauskas 3 weeks ago, about his
SlackBuilds, but received no answers.
His last contribution was more than a year ago.

Does anyone know if he's still active and well ?

Else I my need to upgrade some of his packages (redis and hg-git, probably some
containerd/runc related stuff too as I use them at work).

Thanks,

	- Yth.


From slackbuilds at schoepfer.info  Fri Apr  1 15:08:49 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 01 Apr 2022 17:08:49 +0200
Subject: [Slackbuilds-users] Slackbuild updates: aisleriot.patch
 herbstluftwm.patch lurch.patch mate-calc.patch musl.patch
Message-ID: <7726e91f243823ba8b823d149ee9f78a@schoepfer.info>

Hi,

as Willy wrote some time ago packages may be updated via git-patches on 
this list even now since submissions are open, here are some updates of 
my scripts.

Request to SBo admins:
Would it be possible to create a buildscript-submission at slackbuilds.org 
Mailaccount, accepting git-patches only?
Maybe with automatic tests if attachments apply to git cleanly etc..
That way the user-list wont't get annoyed by updates.

Another note, https://slackbuilds.org/faq/#su (point 22) isn't valid 
anymore about TeTex, also "Step 4" on https://slackbuilds.org/howto/#su 
should not mention "texmf/bin" anymore.

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aisleriot.patch
Type: text/x-diff
Size: 4519 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220401/db761f35/attachment-0005.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: herbstluftwm.patch
Type: text/x-diff
Size: 2672 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220401/db761f35/attachment-0006.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lurch.patch
Type: text/x-diff
Size: 1582 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220401/db761f35/attachment-0007.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mate-calc.patch
Type: text/x-diff
Size: 2158 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220401/db761f35/attachment-0008.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: musl.patch
Type: text/x-diff
Size: 1538 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220401/db761f35/attachment-0009.bin>

From didier at slint.fr  Fri Apr  1 16:18:19 2022
From: didier at slint.fr (Didier Spaier)
Date: Fri, 1 Apr 2022 18:18:19 +0200
Subject: [Slackbuilds-users] seahorse
Message-ID: <fd701a08-a4d0-c6d0-7f28-f2169175e870@slint.fr>

Is still at version 3.18 but builds fine for 41.0, SlackBuild adapted attached.

I write directly to the list as Andrew does not seem to have been active since
June 2020.

Cheers,
Didier
-------------- next part --------------
#!/bin/bash

# Slackware build script for seahorse

# Written by Andrew Rowland (weibullguy at gmail.com)
# Updated to version 3.8.1 by Andrew Rowland

cd $(dirname $0) ; CWD=$(pwd)

PRGNAM=seahorse
VERSION=${VERSION:-41.0}
BUILD=${BUILD:-1}
TAG=slint
PKGTYPE=${PKGTYPE:-txz}

if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i486 ;;
    arm*) ARCH=arm ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi

# If the variable PRINT_PACKAGE_NAME is set, then this script will report what
# the name of the created package would be, and then exit. This information
# could be useful to other scripts.
if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
  echo "$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE"
  exit 0
fi

TMP=$CWD
PKG=$TMP/package-$PRGNAM
OUTPUT=$CWD

if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
else
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
fi

set -e
rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$VERSION
tar xf $CWD/$PRGNAM-$VERSION.tar.?z
cd $PRGNAM-$VERSION
chown -R root:root .
find -L . \
 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 -o -perm 511 \) \
 -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
 -exec chmod 644 {} \;

mkdir build
cd build
  CFLAGS="$SLKCFLAGS" \
  CXXFLAGS="$SLKCFLAGS" \
  meson .. \
    --buildtype=release \
    --infodir=/usr/info \
    --libdir=/usr/lib${LIBDIRSUFFIX} \
    --localstatedir=/var \
    --mandir=/usr/man \
    --prefix=/usr \
    --sysconfdir=/etc \
    -Dstrip=true \
    -Dmanpage=true
  "${NINJA:=ninja}"
  DESTDIR=$PKG $NINJA install
cd ..

rm -f $PKG/usr/lib*/*.la
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

find $PKG/usr/man -type f -exec gzip -9 {} \;
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 \
  AUTHORS COPYING* NEWS README.md THANKS \
  $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild

mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cat $CWD/doinst.sh > $PKG/install/doinst.sh

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE

From phalange at komputermatrix.com  Fri Apr  1 16:52:30 2022
From: phalange at komputermatrix.com (Andrew Payne)
Date: Fri, 1 Apr 2022 12:52:30 -0400 (EDT)
Subject: [Slackbuilds-users] Do git updates get announced?
Message-ID: <f33b4deb-cad-5ac2-f9ea-8ab5e37354b@imap.fatcow.com>

Hi SBo folks, will updates pushed to git still be announced in the
weekly email?


From erich.public at protonmail.com  Fri Apr  1 18:16:01 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Fri, 01 Apr 2022 18:16:01 +0000
Subject: [Slackbuilds-users] Do git updates get announced?
In-Reply-To: <f33b4deb-cad-5ac2-f9ea-8ab5e37354b@imap.fatcow.com>
References: <f33b4deb-cad-5ac2-f9ea-8ab5e37354b@imap.fatcow.com>
Message-ID: <BebjUeA3O3cGb1d5KVkN52PXZ2E9BQSQgnZSqO3pvsAbqsL3tTgXmJ1iLxm__ITjlZtdhHsnR3NjMizYqNmWBmQyR0OsM74Ip0YQ_-M06Bc=@protonmail.com>

------- Original Message -------

On Friday, April 1st, 2022 at 11:52 AM, Andrew Payne <phalange at komputermatrix.com> wrote:

> Hi SBo folks, will updates pushed to git still be announced in the
> weekly email?

Yes.  The 15.0 (and master) branch incorporates changes from the various topic branches and the weekly email lists all the changes to the 15.0 branch.  Additionally the 15.0 branch is tagged.

Erich

From willysr at slackbuilds.org  Sat Apr  2 00:49:13 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 2 Apr 2022 07:49:13 +0700
Subject: [Slackbuilds-users] Slackbuild updates: aisleriot.patch
 herbstluftwm.patch lurch.patch mate-calc.patch musl.patch
In-Reply-To: <7726e91f243823ba8b823d149ee9f78a@schoepfer.info>
References: <7726e91f243823ba8b823d149ee9f78a@schoepfer.info>
Message-ID: <7bf5930c-99bd-b253-c324-d30add578f6b@slackbuilds.org>

> as Willy wrote some time ago packages may be updated via git-patches on
> this list even now since submissions are open, here are some updates of
> my scripts.

Please have a look on this article on how to send patches
https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220402/8054093e/attachment.asc>

From slackbuilds at schoepfer.info  Sat Apr  2 06:13:45 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 02 Apr 2022 08:13:45 +0200
Subject: [Slackbuilds-users] Slackbuild updates: aisleriot.patch
 herbstluftwm.patch lurch.patch mate-calc.patch musl.patch
In-Reply-To: <7bf5930c-99bd-b253-c324-d30add578f6b@slackbuilds.org>
References: <7726e91f243823ba8b823d149ee9f78a@schoepfer.info>
 <7bf5930c-99bd-b253-c324-d30add578f6b@slackbuilds.org>
Message-ID: <d40b3000b9701efc49a047226631977a@schoepfer.info>

On 2022-04-02 02:49, Willy Sudiarto Raharjo wrote:
>> as Willy wrote some time ago packages may be updated via git-patches 
>> on
>> this list even now since submissions are open, here are some updates 
>> of
>> my scripts.
> 
> Please have a look on this article on how to send patches
> https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html

Here you go, attached.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-desktop-herbstluftwm-Updated-for-version-0.9.4.patch
Type: text/x-diff
Size: 3143 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220402/093d20b8/attachment-0005.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-games-aisleriot-Updated-for-version-3.22.22.patch
Type: text/x-diff
Size: 5081 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220402/093d20b8/attachment-0006.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-network-lurch-Updated-for-version-0.7.0.patch
Type: text/x-diff
Size: 2003 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220402/093d20b8/attachment-0007.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0004-office-mate-calc-Updated-for-version-1.26.0.patch
Type: text/x-diff
Size: 2598 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220402/093d20b8/attachment-0008.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0005-system-musl-Updated-for-version-1.2.2.patch
Type: text/x-diff
Size: 1950 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220402/093d20b8/attachment-0009.bin>

From willysr at slackbuilds.org  Sat Apr  2 11:53:22 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 2 Apr 2022 18:53:22 +0700
Subject: [Slackbuilds-users] Updates - 20220402.1
Message-ID: <88a31724-fe87-9be2-a2e4-69bb433d599d@slackbuilds.org>

This week's update was few hours behind our normal schedule due to
massive submissions and updates for this week.

We have seen that some maintainers are still using their old local copy
of the SlackBuild script or using old templates for submission. We will
directly reject those submissions starting now.

Please note that if you want one of your submission to be removed and it
is a dependency for another script, all must be removed and resubmitted
again in the correct order.
Eg. A -> B -> C and A gets rejected, then you need to remove C, then B,
and lastly A.


Sat Apr  2 11:20:15 UTC 2022
academic/aeskulap: Added (medical image viewer)
academic/fet: Updated for versio 6.3.1.
academic/mathics: Updated for version 4.0.0.
academic/molequeue: Added (Desktop integration of hq resources)
academic/ngspice: Updated for version 36.
audio/fantasia: Removed (redundant; use JSampler instead).
audio/google-musicmanager: Handle 32 bit version.
audio/ncspot: Added (cross-platform ncurses Spotify client)
audio/pipewire-native-jack: Added (PipeWire JACK API).
audio/qmmp-plugin-pack-qt5: Updated for version 1.5.2.
audio/qmmp-qt5: Updated for version 1.5.3.
desktop/NsCDE: Added (CDE Desktop).
desktop/bashmount: Added (manage removeable media).
desktop/bemenu: Added (Dynamic Menu Library).
desktop/clearlooks-phenix-theme: Updated for version 7.0.1.
desktop/gromit-mpx: Added (On-screen Annotation tool).
desktop/herbstluftwm: Updated for version 0.9.4
desktop/i3-gaps: Updated for version 4.20.1.
desktop/mint-themes: Added (Linux Mint theme)
desktop/mint-x-icons: Added (Mint Linux default icon theme)
desktop/mint-y-icons: Added (Mint Linux default icon theme)
desktop/qtile: Update for 0.21.0
desktop/swaybg: Added (sway background setter)
desktop/ufetch: Added (displays system information)
desktop/weston: Updated for version 10.0.0.
desktop/zenity: Update for 3.42.0
development/CVSTools: Move cvslib.pl to private dir.
development/OpenJDK11: Added (open implementation of JDK 11).
development/OpenJDK17: Added (open implementation of JDK 17 LTS).
development/SQLAlchemy: Updated for version 1.4.34.
development/adms: Strip binaries/libraries.
development/dotnet-runtime-3.1: Updated for version 3.1.23.
development/dotnet-runtime-5.0: Added (Runtime for .NET 5.0).
development/dotnet-runtime-6.0: Added (Runtime for .NET 6.0).
development/dotnet-sdk-3.1: Updated for version 3.1.417.
development/dotnet-sdk-5.0: Added (Development Framework).
development/dotnet-sdk-6.0: Added (Development framework).
development/eclipse-cpp: Updated for version 4.23.
development/eclipse-java: Updated for version 4.23.
development/eclipse-jee: Updated for version 4.23.
development/eclipse-php: Updated for version 4.23.
development/flawfinder: Fix download URL, ARCH=noarch.
development/github-cli: Updated for version 2.7.0
development/jupyter-ipykernel: Updated for version 6.10.0.
development/jupyter-nbconvert: Updated for version 6.4.5.
development/jupyter-qtconsole: Updated for version 5.3.0.
development/latrace: Fix download URL.
development/lepton-eda: Updated for version 1.9.17.
development/mmtf-cpp: Added (pure C++ implementation of MMTF API)
development/mongodb-compass: Updated for version 1.31.0.
development/nodejs: Updated for version 17.8.0.
development/regina-rexx: Updated for version 3.9.4.
development/robotframework: Updated for version 5.0.
development/s51dude: Fix download URL.
development/sbt: Updated for version 1.6.2.
development/sdcc: Updated for version 4.2.0
development/terraform: Added (IaC Tool).
development/tiled: updated for version 1.8.3
development/vscode-bin: Updated for version 1.66.0.
development/vscodium: Updated for version 1.65.2.
development/vstudio: Updated for version 12.1.
development/zig: Added (toolchain).
games/FlightGear-data: Updated for version 2020.3.12.
games/FlightGear: Updated for version 2020.3.12.
games/SpaceZero: Strip binary, fix icon & .desktop.
games/advancemame: Add SlackBuild to doc dir.
games/aisleriot: Updated for version 3.22.22
games/angband: Updated for version 4.2.4.
games/beetle-psx-libretro: Added (libretro fork of Mednafen PSX).
games/crispy-doom: Updated for version 5.11.1.
games/darkplaces: Don't use precompiled binaries.
games/epsxe: Added (PSX Emulator)
games/fceux: Updated for version 2.6.3.
games/joy2key: Added (control applications with joystick/gamepad)
games/larn: Updated for version 14.1.5.
games/pychess: Updated for version 1.0.3.
games/rejoystick: Added (translates joystick movement/buttons)
games/rogue: Updated for version 5.4.5.
games/scid_vs_pc: Updated for version 4.23.
games/stone_soup: Updated for version 0.28.0.
games/tome-ah: Updated for version 20220224_d25bdae.
games/vkQuake: Updated for version 1.13.0.
gis/GMT: Updated for version 6.3.0.
gis/gdal: Updated for version 3.4.2
gis/google-earth-legacy: Added (Google Virtual Globe).
gis/google-earth: Updated for version 7.3.4.
gis/gpsbabel: Updated for version 1.8.0
gis/python3-basemap: Updated for version 1.3.2.
graphics/LDView: Fix .desktop, doinst.sh.
graphics/OpenVSP: Added (3D Aircraft Modeling Tool).
graphics/gscan2pdf: Updated for version 2.12.4
graphics/lilypond: Updated for version 2.22.2
graphics/mangohud: Added (Vulkan/OpenGL Overlay).
graphics/paraview: Updated for version 5.10.1
graphics/vuescan: Updated MD5SUMs.
ham/tucnak: Added (Ham Radio - VHF/HF contest logbook)
libraries/SimGear: Updated for version 2020.3.12.
libraries/VTK: Fix MPI option
libraries/aspnetcore-runtime-3.1: Updated for version 3.1.23.
libraries/aspnetcore-runtime-5.0: Added (Runtime for ASP.NET 5.0).
libraries/aspnetcore-runtime-6.0: Added (Runtime for ASP.NET 6.0).
libraries/cppzmq: Added (C++ binding for zmq)
libraries/geocode-glib: Added (library for geocoding)
libraries/hoel: updated for version 1.4.20
libraries/libEMF: Updated for version 1.0.13.
libraries/libaal: HOMEPAGE Updated.
libraries/libcoap: Updated for version 4.3.0.
libraries/liblxqt: Added (LXQT library).
libraries/libmseed: Updated for version 2.19.7.
libraries/libmsym: Added (molecular point group symmetry)
libraries/liboop Update to 1.0.1.
libraries/libopenshot-audio: Updated for version 0.2.2
libraries/libopenshot: Updated for version 0.2.7
libraries/libsoup3: Updated for version 3.0.6.
libraries/libvdpau-va-gl: New maintainer + cleanup
libraries/libxmlb: Updated for version 0.3.8.
libraries/libxmlbird: Added (XML parser written in Vala)
libraries/libxnvctrl: Updated for version 510.60.02.
libraries/libzia: Added (Support lib for tucnak4)
libraries/lxqt-notificationd: Added (LXQt notification daemon).
libraries/lxqt-sudo: Added (GUI frontend for sudo/su).
libraries/msgpack-c: Updated for version 3.3.0.
libraries/rhonabwy: updated for version 1.1.3
libraries/spglib: Added (ibrary for crystal symmetry search)
libraries/tree-sitter: Updated for version 0.20.6.
libraries/webkit2gtk4.1: Updated for version 2.36.0.
libraries/webkit2gtk: Updated for version 2.36.0.
misc/dex: Added (dex:)
multimedia/AtomicParsley: Fix ownership in doc dir.
multimedia/DivFix++: Fix doc dir, desktop, README, slack-desc.
multimedia/HandBrake: Strip ghb binary.
multimedia/JSampler: Add doinst, CLI launcher, fix jdk detection.
multimedia/JSampler: Fail if no jdk package installed.
multimedia/intel-gmmlib: Added (The Intel Graphics MML)
multimedia/intel-media-driver: Added (ntel Media Driver for VAAPI)
multimedia/intel-media-sdk: Added (Intel(R) Media SDK)
multimedia/jlscp: Fix jdk detection.
multimedia/lives: Update HOMEPAGE URL.
multimedia/openshot: Updated for version 2.6.1
multimedia/plexmediaserver: Updated for v 1.25.8.5663_e071c3d62.
network/2ping: Add SlackBuild to doc dir.
network/MEGAcmd: Added (MEGA CLI Interactive/Scriptable Application)
network/WhatWeb: Updated for version 0.5.5.
network/XD: Updated for version 0.4.2.
network/acme: Updated for version 3.0.2.
network/bitchx: Added (IRC client).
network/brave-browser: Updated for version 1.37.109
network/csync: Fix download URL.
network/dropbox: Updated for version 145.4.4921
network/glewlwyd: updated for version 2.6.2
network/i2pd: Updated for version 2.41.0.
network/keepalived: Enable nftables and libipset support.
network/linksys-tftp: Add more patches.
network/lurch: Updated for version 0.7.0
network/mod_auth_kerb: Fix download URL.
network/mod_geoip2: Fix download URL.
network/modsecurity-apache: remove gpg detection.
network/nbd: Updated for version 3.24
network/neomutt: Updated for version 20211029.
network/newsboat: Updated for version 2.27.
network/nextcloud-client: Removed (use nextcloud-desktop).
network/nextcloud-desktop: Added (Nextcloud Desktop Client).
network/nginx: Update nginx.logrotate.
network/pgbouncer: Fix download URL.
network/scapy: Updated for version 2.4.5.
network/signal-desktop: Updated for version 5.37.0.
network/sniffjoke: Fix download URL.
network/sslstrip: Fix download URL.
network/unicornscan: Fix DOWNLOAD url.
network/webalizer: Fix download URL, man page path.
network/wp-cli: Updated for version 2.6.0.
office/LibreOffice: Updated for version 7.3.2.2
office/adobe-reader: Fix .desktop, symlinks.
office/gnucash-docs: Updated for version 4.9.
office/gnucash: Updated for version 4.9.
office/hunspell-gr: Added (Greek hunspell dictionary).
office/keepassxc: Updated for version 2.7.0
office/libreoffice-helppack: Updated for version 7.3.2.
office/libreoffice-langpack: Updated for version 7.3.2.
office/libreoffice: Updated for version 7.3.2.
office/mate-calc: Updated for version 1.26.0
office/treesheets: Fixed MD5SUM.
office/xournalpp: Updated for version 1.1.1.
perl/MoarVM: Updated for version 2022.03.
perl/nqp: Updated for version 2022.03
perl/perl-Gtk3-ImageView: Added (Image viewer widget for Gtk3).
perl/perl-Gtk3-SimpleList: Added (interface to Gtk3's Widget).
perl/perl-gnome2-gconf: Updated for version 1.047.
perl/rakudo: Updated for version 2022.03
python/PyGreSQL: Updated for version 5.2.4
python/buildbot: updated for version 3.5.0, updated dependencies
python/cloudpickle: Added (Python Module).
python/debugpy: Updated for version 1.6.0.
python/doit: Added (task management tool).
python/ipython: Update for 8.2.0
python/pdfarranger: Added (Arrange PDF Pages).
python/pikepdf: Added (Python library).
python/pluggy: Updated for version 0.13.1.
python/py: Updated for version 1.11.0.
python/pybind11: Updated for version 2.9.2
python/pyfeed: Fix download URL.
python/python-colour: Added (python library).
python/python-daemonize: Added (python library).
python/python-evdev: Update for 1.5.0
python/python-mysql-replication: Updated for version 0.28.
python/python2-attrs: updated for version 21.4.0
python/python2-automat: removed unused python-m2r requirement
python/python3-alembic: updated for version 1.7.7
python/python3-amqp: updated for version 5.1.0
python/python3-autobahn: updated for version 22.3.2
python/python3-automat: removed unused python-m2r requirement
python/python3-characteristic: Added (Python module).
python/python3-dulwich: updated for version 0.20.35
python/python3-kombu: updated for version 5.2.4
python/python3-obspy: Updated for version 1.3.0.
python/python3-service-identity: Added (SIV for PyOpenSSL).
python/python3-tubes: Added (micro-framework for web services).
python/python3-twisted: updated for version 22.2.0, updated dependencies
python/python3-waitress: updated for version 2.1.1
python/python3-websockets: Added (WebSocket servers & clients)
python/xe: Fix download URL.
ruby/ruby-build: Updated for version 20220324.
system/CPU-X: Updated for version 4.3.0.
system/I-Nex: Fix symlimk, .desktop perms.
system/apache-tomcat: Updated for version 10.0.20.
system/bat: Updated for version 0.20.0.
system/chronograf: Updated for version 1.9.4
system/duperemove: Added (Find duplicate extents).
system/dust: Updated for version 0.8.0.
system/fcron: Updated for version 3.3.1.
system/fuse-zip: Added (FUSE filesystem).
system/kapacitor: Updated for version 1.6.4
system/libratbag: Added (daemon for gaming mice).
system/mkslack: Removed.
system/musl: Updated for version 1.2.2
system/noto-emoji: Updated for version 2.034.
system/nvidia-driver: Updated for version 510.60.02.
system/nvidia-kernel: Updated for version 510.60.02.
system/nvidia-legacy390-driver: Updated for version 390.147.
system/nvidia-legacy390-kernel: Updated for version 390.147.
system/nvidia-legacy470-driver: Added (Nvidia 470 driver).
system/nvidia-legacy470-kernel: Added (Nvidia 470 kernel module).
system/openrazer-daemon: Added (Razer Drivers for Linux).
system/openrazer-kernel: Added (kernel modules for openrazer).
system/pam-gnupg: Added (Unlock GnuPG keys on login).
system/passwordsafe: Updated for version 1.14.0.
system/pcem-roms: Added (rom files for the pcem emulator)
system/pcem: Added (low-level emulator for IBM compatibles)
system/piper: Added (configure gaming mice).
system/polychromatic: Added (GUI frontend for openrazer).
system/powershell: Updated for version 7.2.2.
system/pytrash: Updated for version 1.1.5.
system/razerCommander: Added (Razer device manager).
system/razergenie: Added (Razer device configuration tool).
system/reiser4progs: Updated for version 1.2.2.
system/restic: Updated for version 0.13.0
system/rmw: Update email.
system/sboui: Updated for version 2.2.
system/slpkg: Updated for version 3.9.4.
system/spman: Updated for version 2.2.3.
system/tagainijisho: Updated for version 1.1.94.
system/telegraf: Updated for version 1.22.0
system/ttf-charis-sil: Updated for version 6.101.
system/ttf-doulos-sil: Updated for version 6.101.
system/xen: Updated for version 4.15.2.
system/yelp-tools: Updated for version 42.0.
system/yelp-xsl: Updated for version 42.0.
system/yelp: Updated for version 42.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220402/0fa9465d/attachment.asc>

From slackalaxy at gmail.com  Sat Apr  2 15:28:02 2022
From: slackalaxy at gmail.com (Petar Petrov)
Date: Sat, 2 Apr 2022 18:28:02 +0300
Subject: [Slackbuilds-users] Slackware cited (again) in a scientific
 publication
Message-ID: <CAKXpWBddZyGZ4fGx7JvF8UvdaWPb=93KdeigYdd6t2yB+vceLA@mail.gmail.com>

dear All,

I am happy to let you know that Slackware was cited in the latest
paper from our group, published in the International Journal of
Molecular Sciences:

https://www.mdpi.com/1422-0067/23/6/3351

The paper describes a computational pipeline for the prediction of
inter-protein coevolution. In the center of the pipeline is program
CAPS, the static version of which you still have at SBo. Many of the
programs used are still present there, in fact. The showstopper for me
was Guidance, which required bioPerl, which in turn had a nightmarish
number of perl modules dependencies. This is when I had to change my
system and move away from Slackware (along with other reasons).
Slackware is credited in section 5. Materials and Methods -> 5.1.
Availability and Required Software.

I am very grateful for the help I have received from you as a
community through the years. Special thanks go to Urchlay, who
explained to me how to specify custom libs path at compile time.

kind regards,

Petar

From mjolnirdam at gmail.com  Sat Apr  2 16:21:07 2022
From: mjolnirdam at gmail.com (Damian Perticone)
Date: Sat, 2 Apr 2022 13:21:07 -0300
Subject: [Slackbuilds-users] can not delete my submission
Message-ID: <CAEW3CoH6iXwDbvAE9ywz-5tcV-PCvduTLg=8sX065cF2r7UAnA@mail.gmail.com>

hi i want to send my submission again but  It say The file libseat.tar.gz
does not exist in pending and when i try to submit again it say *File
exists;* a submission by the name 'libseat' is already pending approval.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220402/f6aa2849/attachment.htm>

From willysr at slackbuilds.org  Sat Apr  2 16:30:05 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 2 Apr 2022 23:30:05 +0700
Subject: [Slackbuilds-users] can not delete my submission
In-Reply-To: <CAEW3CoH6iXwDbvAE9ywz-5tcV-PCvduTLg=8sX065cF2r7UAnA@mail.gmail.com>
References: <CAEW3CoH6iXwDbvAE9ywz-5tcV-PCvduTLg=8sX065cF2r7UAnA@mail.gmail.com>
Message-ID: <5101fe47-f8b8-c25a-685b-012070db3b08@slackbuilds.org>

> hi i want to send my submission again but  It say The file libseat.tar.gz
> does not exist in pending and when i try to submit again it say *File
> exists;* a submission by the name 'libseat' is already pending approval.

it should be ok now


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220402/25634c4a/attachment.asc>

From andrzej at telszewski.com  Sun Apr  3 13:44:40 2022
From: andrzej at telszewski.com (Andrzej Telszewski)
Date: Sun, 3 Apr 2022 13:44:40 +0000 (UTC)
Subject: [Slackbuilds-users] Slackware cited (again) in a scientific
 publication
In-Reply-To: <CAKXpWBddZyGZ4fGx7JvF8UvdaWPb=93KdeigYdd6t2yB+vceLA@mail.gmail.com>
References: <CAKXpWBddZyGZ4fGx7JvF8UvdaWPb=93KdeigYdd6t2yB+vceLA@mail.gmail.com>
Message-ID: <719e5a65-a4ad-42a2-91df-384de8abde9e@telszewski.com>

Hi,

thank you for the heads up!

In addition, I am always happy to hear about people being involved in science. :-)

All the best to you, and of course to our beloved Slackware (and the **one** and the **others** behind it. :-))


-- 
Best regards,
Andrzej Telszewski

From sbo at linuxgalaxy.org  Sun Apr  3 18:16:52 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Sun, 03 Apr 2022 18:16:52 +0000
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
Message-ID: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>

Hello Admins,
I get it.  We want to ensure compatibility over a wide variety of
computer hardware and build systems.  However, IMHO this far into the
21st Century, we need to realize that most SBo users are on x86_64
architecture and will have multicore processors on any laptop or desktop
CPU.  My smallest, oldest 10+ year old laptop I have as 2 cores (2
threads/core; Intel? Core? i7-620M Processor).  The next oldest has 4
cores. On my "new" 3-year old processors

AMD Ryzen 7 3800X 8-core
AMD Ryzen 9 3900X 12-core (gemu gets 6 of these)

I sure as heck ain't gonna compile on one core and waste the rest when I
test, unless absolutely necessary.  I ain't got that kinda time given
that 70+ % of my expected lifespan is behind me.

Some SBo buildscripts can take a long time to compile when using only 1
core/thread.  Please note that nearly ALL core Slackware software sets
NUMJOBS based on the number of cores the CPU reports.  If it is good
enough for Pat, it's good enough for SBo.

Most modern build systems (ninja) are already parallel aware.
Autotools, can be problematic, especially with older sources, but is
generally parallel aware for newer projects.

It is easy enough to force 'make -j1' as needed for the few that need it.

Therefore, I will be adding back in to all the buildscripts under my
care, for those that can support it:

NUMJOBS=${NUMJOBS:-1}
make -j${NUMJOBS}

For compatibility, the default will be one core/thread.  Please do not
remove.  This is a feature and not a bug.

Thanks
-Ed





From willysr at slackbuilds.org  Sun Apr  3 18:22:47 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 4 Apr 2022 01:22:47 +0700
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
Message-ID: <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>

> For compatibility, the default will be one core/thread.  Please do not
> remove.  This is a feature and not a bug.

You can just export MAKEFLAGS in your machine to achive same results
Don't expect others to use same machine as yours and we often test those
scripts in a VM with only small specs.

We use -j1 explicitly only for those who failed to run on multiple
cores, but as for the rest, we want to keep it like what we have now.


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220404/6ae3b9fe/attachment.asc>

From urchlay at slackware.uk  Sun Apr  3 18:59:04 2022
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 3 Apr 2022 14:59:04 -0400 (EDT)
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
Message-ID: <cdc5af12-de2e-7af-dc3e-2de1b0547d6c@slackware.uk>



On Sun, 3 Apr 2022, Slackbuilds wrote:

> Therefore, I will be adding back in to all the buildscripts under my
> care, for those that can support it:
>
> NUMJOBS=${NUMJOBS:-1}
> make -j${NUMJOBS}

There's no need for this. You can just 'export MAKEFLAGS=-j8' or
whatever in your environment. A lot of users already do this... but
read on:

> For compatibility, the default will be one core/thread.

This is going to pose a problem for people who already use MAKEFLAGS
and never heard of your NUMJOBS variable. If I have MAKEFLAGS=-j8,
I expect everything to use it (unless it's forced to -j1). If I'm
running one of your builds that overrides that with NUMJOBS defaulting
to 1, I get a long slow build (which is what you and I are both trying
to avoid).

How about you do this instead?

if [ -z "$MAKEFLAGS" ]; then
   NUMJOBS="${NUMJOBS:-1}"
   export MAKEFLAGS="-j$NUMJOBS"
fi
make

...that way, your builds work the way you want: they respect NUMJOBS
if MAKEFLAGS isn't set... but they'll still work the way everyone else
wants: people who already use MAKEFLAGS will still get the expected
results.

> It is easy enough to force 'make -j1' as needed for the few that need it.

We already do this, when needed. Looks like we have 162 builds that
have "make -j1", which is around 2% of the total.

From sbo at linuxgalaxy.org  Sun Apr  3 18:59:16 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Sun, 03 Apr 2022 18:59:16 +0000
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>
Message-ID: <9c50f181-7144-e2ca-6f3a-69af397d524c@linuxgalaxy.org>

On 4/3/22 11:22, Willy Sudiarto Raharjo wrote:
>> For compatibility, the default will be one core/thread.  Please do not
>> remove.  This is a feature and not a bug.
>
> You can just export MAKEFLAGS in your machine to achive same results
> Don't expect others to use same machine as yours and we often test those
> scripts in a VM with only small specs.
>
> We use -j1 explicitly only for those who failed to run on multiple
> cores, but as for the rest, we want to keep it like what we have now.
>
>

Given that my 4 systems span over 10 yrs and both Intel and AMD (even
the newest is already 3 yrs old), it is a good guess that, yes, I may
have what most people are using.

Most of my testing for submission is in a VM (either 2, 4 or 6 cores,
depending on how many I fire up on the Ryzen 9).  Settings MAKEFLAGS
will hide NUMJOBS and is not appropriate since it obscures what was
used. My VMs may not have the expected cores. It's better to have this
available to explicitly set in the script as needed. Having
NUMJOBS=${NUMJOBS:-1} as the default provides a suitable fallback.

Also, most MakeFiles don't set the number of cores by default and expect
that to be passed with -j{n}, otherwise -j1 is used anyway.

I see no logical reason not to use -j${NUMJOBS} for those sources that
support it, and set -j1 as the default.  This is a decision that can be
left to the buildscript maintainer to determine from testing. It does
not need to be, IMHO, an arbitrary global rule.

There have been previous discussions on this topic. I have yet to be
convinced of the utility of not allowing NUMJOBS.  After all, Pat sprinkles

NUMJOBS=${NUMJOBS:-" -j$(expr $(nproc) + 1) "}

everywhere.  This seems to defeat your "Don't expect others to use same
machine as yours" argument.

Thanks,
-Ed


From netrixtardis at stealth3.com  Sun Apr  3 19:07:45 2022
From: netrixtardis at stealth3.com (netrixtardis)
Date: Sun, 3 Apr 2022 14:07:45 -0500
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>
Message-ID: <7a3471c9-63cc-d5f9-7e54-35b930d380e8@stealth3.com>

On 4/3/2022 1:22 PM, Willy Sudiarto Raharjo wrote:
>> For compatibility, the default will be one core/thread.  Please do not
>> remove.  This is a feature and not a bug.
> You can just export MAKEFLAGS in your machine to achive same results 
> Don't expect others to use same machine as yours and we often test 
> those scripts in a VM with only small specs. We use -j1 explicitly 
> only for those who failed to run on multiple cores, but as for the 
> rest, we want to keep it like what we have now. 
What about using "$(($(nproc) + 1))" or "$(($(nproc) -1))"?
 ? NUMJOBS=${NUMJOBS:$(($(nproc) + 1))}
or a safe default of
 ? NUMJOBS=${NUMJOBS:$(($(nproc) - 1))}

The 2nd option having the safety of saving 1 core or thread from being 
compiled on.

From willysr at slackbuilds.org  Sun Apr  3 19:09:27 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 4 Apr 2022 02:09:27 +0700
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <9c50f181-7144-e2ca-6f3a-69af397d524c@linuxgalaxy.org>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>
 <9c50f181-7144-e2ca-6f3a-69af397d524c@linuxgalaxy.org>
Message-ID: <1f66028b-0a22-a815-ac8c-006a9fa27c0f@slackbuilds.org>

> I see no logical reason not to use -j${NUMJOBS} for those sources that
> support it, and set -j1 as the default.  This is a decision that can be
> left to the buildscript maintainer to determine from testing. It does
> not need to be, IMHO, an arbitrary global rule.

It may not be a problem for those who only use small number of scripts
from SBo, but we have to deal with ALL of the scripts during development
cycle which is more than 8k.

if every maintainer do their job properly, we could have repo 15.0
released as same day as Slackware 15.0 gets released just like what we
had with 14.2. Unfortunately that's not the case.

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220404/e1ff2713/attachment.asc>

From ozan.turkyilmaz at gmail.com  Sun Apr  3 19:19:30 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Sun, 03 Apr 2022 22:19:30 +0300
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>
Message-ID: <1dbebfcd40dd92c44fbc6858e8714d5e7a93b6c4.camel@gmail.com>

Pzt, 2022-04-04 tarihinde 01:22 +0700 saatinde, Willy Sudiarto Raharjo
yazd?:
> 
> 
> You can just export MAKEFLAGS in your machine to achive same results
> Don't expect others to use same machine as yours and we often test
> those
> scripts in a VM with only small specs.
> 
Don't do that. MAKEFLAGS is for passing command line arguments to
submake processes [1]. I dont know if MAKEFLAGS="-j2" sh configure
would do any problem or even make would get it. 

Regards,
Ozan

[1] There's some long talk abut it
here:https://www.gnu.org/software/make/manual/html_node/Options_002fRecursion.html
Also here: https://stackoverflow.com/a/19622824/7247759

From matteo.bernardini at gmail.com  Sun Apr  3 19:26:37 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 3 Apr 2022 21:26:37 +0200
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <9c50f181-7144-e2ca-6f3a-69af397d524c@linuxgalaxy.org>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>
 <9c50f181-7144-e2ca-6f3a-69af397d524c@linuxgalaxy.org>
Message-ID: <CAPsDuS5hQ8NyzJd86uL3e72dxRmeb+AfdAOsL5KoF1-F8j9hQQ@mail.gmail.com>

Il giorno dom 3 apr 2022 alle ore 20:59 Slackbuilds <sbo at linuxgalaxy.org>
ha scritto:

> Most of my testing for submission is in a VM (either 2, 4 or 6 cores,
> depending on how many I fire up on the Ryzen 9).  Settings MAKEFLAGS
> will hide NUMJOBS and is not appropriate since it obscures what was
> used. My VMs may not have the expected cores. It's better to have this
> available to explicitly set in the script as needed. Having
> NUMJOBS=${NUMJOBS:-1} as the default provides a suitable fallback.
>

like netrixtrardis wrote you can use a dynamic setting also for MAKEFLAGS:
on my systems I have

export MAKEFLAGS=${MAKEFLAGS:--j$(expr $(nproc) + 1)}

this way you can use it on every machine regardless of their resources.
Il giorno dom 3 apr 2022 alle ore 21:19 Ozan T?rky?lmaz <
ozan.turkyilmaz at gmail.com> ha scritto:

> Don't do that. MAKEFLAGS is for passing command line arguments to
> submake processes [1]. I dont know if MAKEFLAGS="-j2" sh configure
> would do any problem or even make would get it.
>
> Regards,
> Ozan
>
> [1] There's some long talk abut it
> here:
> https://www.gnu.org/software/make/manual/html_node/Options_002fRecursion.html
> Also here: https://stackoverflow.com/a/19622824/7247759
>

Hi Ozan,

the first link you cite contains a couple of paragraphs that say that is
perfectly legit to use MAKEFLAGS to set parallel make jobs, the second
discussion on stackoverflow is only about the opportunity to set MAKEFLAGS
inside a Makefile.

Matteo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220403/316c778a/attachment-0001.htm>

From dave at slackbuilds.org  Sun Apr  3 19:34:17 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 3 Apr 2022 20:34:17 +0100
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <1dbebfcd40dd92c44fbc6858e8714d5e7a93b6c4.camel@gmail.com>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>
 <1dbebfcd40dd92c44fbc6858e8714d5e7a93b6c4.camel@gmail.com>
Message-ID: <Ykn2uTpcLn9JfTXa@localhost>

On 03/04/22 22:19,
Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com> put forth the proposition:
> Pzt, 2022-04-04 tarihinde 01:22 +0700 saatinde, Willy Sudiarto Raharjo
> yazd?:
> >
> >
> > You can just export MAKEFLAGS in your machine to achive same results
> > Don't expect others to use same machine as yours and we often test
> > those
> > scripts in a VM with only small specs.
> >
> Don't do that. MAKEFLAGS is for passing command line arguments to
> submake processes [1]. I dont know if MAKEFLAGS="-j2" sh configure
> would do any problem or even make would get it.
> Regards,
> Ozan
> [1] There's some long talk abut it
> here:https://www.gnu.org/software/make/manual/html_node/Options_002fRecursion.html
> Also here: https://stackoverflow.com/a/19622824/7247759

But also

The MAKEFLAGS variable can also be useful if you want to have certain
options, such as ?-k? (see Summary of Options), set each time you run
make. You simply put a value for MAKEFLAGS in your environment.

However:

If you do put MAKEFLAGS in your environment, you should be sure not to
include any options that will drastically affect the actions of make and
undermine the purpose of makefiles and of make itself. For instance, the
?-t?, ?-n?, and ?-q? options,

Same ref[1]

--
Dave

From sbo at linuxgalaxy.org  Sun Apr  3 23:26:01 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Sun, 03 Apr 2022 23:26:01 +0000
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <Ykn2uTpcLn9JfTXa@localhost>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>
 <1dbebfcd40dd92c44fbc6858e8714d5e7a93b6c4.camel@gmail.com>
 <Ykn2uTpcLn9JfTXa@localhost>
Message-ID: <0d3e9562-f220-265e-29a4-f007d75b5e72@linuxgalaxy.org>

On 4/3/22 12:34, Dave Woodfall wrote:
> On 03/04/22 22:19,
> Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com> put forth the proposition:
>> Pzt, 2022-04-04 tarihinde 01:22 +0700 saatinde, Willy Sudiarto Raharjo
>> yazd?:
>>>
>>>
>>> You can just export MAKEFLAGS in your machine to achive same results
>>> Don't expect others to use same machine as yours and we often test
>>> those
>>> scripts in a VM with only small specs.
>>>
>> Don't do that. MAKEFLAGS is for passing command line arguments to
>> submake processes [1]. I dont know if MAKEFLAGS="-j2" sh configure
>> would do any problem or even make would get it.
>> Regards,
>> Ozan
>> [1] There's some long talk abut it
>> here:https://www.gnu.org/software/make/manual/html_node/Options_002fRecursion.html
>> Also here: https://stackoverflow.com/a/19622824/7247759
>
> But also
>
> The MAKEFLAGS variable can also be useful if you want to have certain
> options, such as ?-k? (see Summary of Options), set each time you run
> make. You simply put a value for MAKEFLAGS in your environment.
>
> However:
>
> If you do put MAKEFLAGS in your environment, you should be sure not to
> include any options that will drastically affect the actions of make and
> undermine the purpose of makefiles and of make itself. For instance, the
> ?-t?, ?-n?, and ?-q? options,
>
> Same ref[1]
>

As I understand re[1] globally setting MAKEFLAGS in one's environment
could stomp on (or end up being ignored) since MAKEFLAGS might be
already set in the makefile internally to pass info to the sub-makes
(recursive make), but not tested to see if already set.  Unintended
consequences.  Especially given the age variety of makefiles.

-Ed






From sbo at linuxgalaxy.org  Sun Apr  3 23:44:20 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Sun, 03 Apr 2022 23:44:20 +0000
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <cdc5af12-de2e-7af-dc3e-2de1b0547d6c@slackware.uk>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <cdc5af12-de2e-7af-dc3e-2de1b0547d6c@slackware.uk>
Message-ID: <2b75ad06-404f-a6b1-5c34-8118061c1f5f@linuxgalaxy.org>

On 4/3/22 11:59, B. Watson wrote:
> How about you do this instead?
>
> if [ -z "$MAKEFLAGS" ]; then
>    NUMJOBS="${NUMJOBS:-1}"
>    export MAKEFLAGS="-j$NUMJOBS"
> fi
> make
>
> ...that way, your builds work the way you want: they respect NUMJOBS
> if MAKEFLAGS isn't set... but they'll still work the way everyone else
> wants: people who already use MAKEFLAGS will still get the expected
> results.

I'm still not convinced that globally setting MAKEFLAGS won't have
unintended consequences. I keep seeing in the make docs that the
toplevel make creates/sets MAKEFILE for sub-makes, but isn't clear in
what happens if MAKEFILES is already set, unless upstream source adds
that logic.

Setting 'make -j$NUMJOBS' seems a safer path, and is what Pat does in
Slackware source.

-Ed


From sbo at linuxgalaxy.org  Mon Apr  4 00:04:20 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Mon, 04 Apr 2022 00:04:20 +0000
Subject: [Slackbuilds-users] Libraries/miniupnpc (2.2.3) uses PYTHON3=yes by
 default
Message-ID: <4e458d1d-292b-ca1b-7b77-528277df72c7@linuxgalaxy.org>

The buildscript has

# For python 3.x support.
if [ "${PYTHON3:-yes}" == "yes" ]; then
  CFLAGS="$SLKCFLAGS" \
  python3 setup.py build
  python3 setup.py install --root=$PKG
fi

while the README stats

Note: To install python 3 bindings set PYTHON3=yes.
  # PYTHON3=yes ./miniupnpc.SlackBuild

Somewhere we need a PYTHON3=no, depending on intent.

CC: the listed maintainer.

-Ed


From willysr at slackbuilds.org  Mon Apr  4 01:21:13 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 4 Apr 2022 08:21:13 +0700
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <2b75ad06-404f-a6b1-5c34-8118061c1f5f@linuxgalaxy.org>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <cdc5af12-de2e-7af-dc3e-2de1b0547d6c@slackware.uk>
 <2b75ad06-404f-a6b1-5c34-8118061c1f5f@linuxgalaxy.org>
Message-ID: <0e2e2775-694a-ca24-7cb7-0d7ce8105b00@slackbuilds.org>

> Setting 'make -j$NUMJOBS' seems a safer path, and is what Pat does in
> Slackware source.

Because in most of the time, people use his binary packages, not
building from source (only some people do this, like nobodino who helped
him testing that slackware always build from source).

In case of SBo, we provide SlackBuild scripts, not binary packages

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220404/96c62098/attachment.asc>

From willysr at slackbuilds.org  Mon Apr  4 01:26:01 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 4 Apr 2022 08:26:01 +0700
Subject: [Slackbuilds-users] Libraries/miniupnpc (2.2.3) uses
 PYTHON3=yes by default
In-Reply-To: <4e458d1d-292b-ca1b-7b77-528277df72c7@linuxgalaxy.org>
References: <4e458d1d-292b-ca1b-7b77-528277df72c7@linuxgalaxy.org>
Message-ID: <09b95883-0123-79d4-8bd1-695c4ba9ce9a@slackbuilds.org>

> The buildscript has
> 
> # For python 3.x support.
> if [ "${PYTHON3:-yes}" == "yes" ]; then
>   CFLAGS="$SLKCFLAGS" \
>   python3 setup.py build
>   python3 setup.py install --root=$PKG
> fi
> 
> while the README stats
> 
> Note: To install python 3 bindings set PYTHON3=yes.
>   # PYTHON3=yes ./miniupnpc.SlackBuild
> 
> Somewhere we need a PYTHON3=no, depending on intent.

Fixed
thanks


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220404/e9ca9887/attachment.asc>

From marav8 at free.fr  Sat Apr  2 18:51:43 2022
From: marav8 at free.fr (marav)
Date: Sat, 2 Apr 2022 20:51:43 +0200
Subject: [Slackbuilds-users] Submissions: wireplumber
Message-ID: <cb673ddf-da72-9877-9609-d61682f96e4c@free.fr>

Hi,

I can't? re-upload my SB for wireplumber, it says : "File exists; a 
submission by the name 'wireplumber' is already pending approval."

And when I try to remove it: "The file wireplumber.tar.gz does not exist 
in pending"

Can you at this ?

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220402/0ee55024/attachment-0001.htm>

From mjolnirdam at gmail.com  Sat Apr  2 22:19:17 2022
From: mjolnirdam at gmail.com (Damian Perticone)
Date: Sat, 2 Apr 2022 19:19:17 -0300
Subject: [Slackbuilds-users] sorry to bother again
Message-ID: <CAEW3CoHo-C8JKWMTU0Hj73HvUPXrR1TZ2zV-Ss8dKR_jm2f7fA@mail.gmail.com>

i submit again libseat as seats, but i have the same problem as before with
wlroots
it say File exists a submission by the name 'libseat' is already pending
approval.
i want to submit wlroots and sway again. Thanks a lot and sorry to bother.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220402/cf99fb37/attachment-0001.htm>

From mjolnirdam at gmail.com  Sun Apr  3 20:51:08 2022
From: mjolnirdam at gmail.com (Damian Perticone)
Date: Sun, 3 Apr 2022 17:51:08 -0300
Subject: [Slackbuilds-users] another submission i can not delete
Message-ID: <CAEW3CoEujXFN0VQ_hRBhx-yOUO=X4MDJ50GM-Dwf3U82cAmejg@mail.gmail.com>

sorry to bother again i want to make a submission of wlroots again but it
say *File exists;* a submission by the name 'wlroots' is already pending
approval. it was already deleted before.
best regards!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220403/50f58194/attachment-0001.htm>

From willysr at slackbuilds.org  Mon Apr  4 01:28:31 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 4 Apr 2022 08:28:31 +0700
Subject: [Slackbuilds-users] another submission i can not delete
In-Reply-To: <CAEW3CoEujXFN0VQ_hRBhx-yOUO=X4MDJ50GM-Dwf3U82cAmejg@mail.gmail.com>
References: <CAEW3CoEujXFN0VQ_hRBhx-yOUO=X4MDJ50GM-Dwf3U82cAmejg@mail.gmail.com>
Message-ID: <b3dc2151-7861-5889-2e2b-2d9200d31326@slackbuilds.org>

> sorry to bother again i want to make a submission of wlroots again but it
> say *File exists;* a submission by the name 'wlroots' is already pending
> approval. it was already deleted before.

Done, you can resubmit
again, please read my note in last public update


Please note that if you want one of your submission to be removed and it
is a dependency for another script, all must be removed and resubmitted
again in the correct order.
Eg. A -> B -> C and A gets rejected, then you need to remove C, then B,
and lastly A.



-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220404/6278ab3b/attachment.asc>

From urchlay at slackware.uk  Mon Apr  4 07:50:14 2022
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 4 Apr 2022 03:50:14 -0400 (EDT)
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <7a3471c9-63cc-d5f9-7e54-35b930d380e8@stealth3.com>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <7696f685-cea2-9113-5404-3e64aebdb37f@slackbuilds.org>
 <7a3471c9-63cc-d5f9-7e54-35b930d380e8@stealth3.com>
Message-ID: <341beb1e-d7d4-87d6-955e-f07768f95c5@slackware.uk>



On Sun, 3 Apr 2022, netrixtardis wrote:

> or a safe default of
> ? NUMJOBS=${NUMJOBS:$(($(nproc) - 1))}

That's an *unsafe* default. What does make do when you run that on a
single-core machine? It gets a "-j0" argument, that's either an error,
or it means the same as "-j" by itself (meaning *infinite* jobs).

From jebrhansen+SBo at gmail.com  Mon Apr  4 08:41:38 2022
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Mon, 4 Apr 2022 02:41:38 -0600
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <2b75ad06-404f-a6b1-5c34-8118061c1f5f@linuxgalaxy.org>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <cdc5af12-de2e-7af-dc3e-2de1b0547d6c@slackware.uk>
 <2b75ad06-404f-a6b1-5c34-8118061c1f5f@linuxgalaxy.org>
Message-ID: <CANi9qSseQSO8PaNYrG4m9Fy-HcNY0SJ5anipWUaVy1Ep-tkpVg@mail.gmail.com>

On Sun, Apr 3, 2022, 5:44 PM Slackbuilds <sbo at linuxgalaxy.org> wrote:

> On 4/3/22 11:59, B. Watson wrote:
> > How about you do this instead?
> >
> > if [ -z "$MAKEFLAGS" ]; then
> >    NUMJOBS="${NUMJOBS:-1}"
> >    export MAKEFLAGS="-j$NUMJOBS"
> > fi
> > make
> >
> > ...that way, your builds work the way you want: they respect NUMJOBS
> > if MAKEFLAGS isn't set... but they'll still work the way everyone else
> > wants: people who already use MAKEFLAGS will still get the expected
> > results.
>
> I'm still not convinced that globally setting MAKEFLAGS won't have
> unintended consequences. I keep seeing in the make docs that the
> toplevel make creates/sets MAKEFILE for sub-makes, but isn't clear in
> what happens if MAKEFILES is already set, unless upstream source adds
> that logic.
>
> Setting 'make -j$NUMJOBS' seems a safer path, and is what Pat does in
> Slackware source.
>

This had been discussed on LQ and it was found that make is smart enough to
talk with its own sub-makes to ensure no more than the max number of jobs
can take place (specifically post #23, which is mine).

https://www.linuxquestions.org/questions/slackware-14/multi-thread-builds-via-sbopkg-slackbuilds-4175684827/

The only time it doesn't happen is if a makefile is poorly made as
demonstrated by pan64. However, I've had a global MAKEFLAGS set with only
what essentially sets -j17 in there since 2017 and I've never seen build
issues from it.

So, while theoretical, global MAKEFLAGS can cause issues with a poorly made
MAKEFILE, it seems they are extremely uncommon (if they exist at all).

NOTE: This is not to say we shouldn't have NUMJOBS in SlackBuilds (I don't
really have a preference), but just to say that setting -jXX in a global
MAKEFLAGS is unlikely to cause any issues in practice.

Here's the content of my /etc/profile.d/make-exports.sh. I have it do the
number of CPUs the kernel sees + 1 (this will include total threads, at
least on AMD systems).

export MAKEFLAGS="-j$(expr $(nproc) + 1)"

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220404/a5192f22/attachment.htm>

From gen-bch at useyouresp.org.uk  Mon Apr  4 13:10:31 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Mon, 4 Apr 2022 14:10:31 +0100 (BST)
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
Message-ID: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>

Hello everyone, good day

Slackware 15, clean, fully updated

The build either manually or via sbotools fails at the same place at the 
openjdk7 part.

(part of the buildlog is below up until it bails out).

Is it something I'm doing or something in the slackbuild and associate 
files and is there a quick 'fix' to try please ?

Regards
Habs



/tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf 
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar 
-C 
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/ 
.
/tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf 
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar 
-C /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes 
META-INF/services/com.sun.jdi.connect.Connector
java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but got 
0xc7a06d31)
         at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
         at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
         at java.io.FilterInputStream.read(FilterInputStream.java:107)
         at sun.tools.jar.Main.copy(Main.java:822)
         at sun.tools.jar.Main.update(Main.java:584)
         at sun.tools.jar.Main.run(Main.java:224)
         at sun.tools.jar.Main.main(Main.java:1231)
gmake[8]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86: 
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar] 
Error 1
gmake[8]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[7]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64: 
all] Error 2
gmake[7]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[6]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103: 
sa_stuff] Error 2
gmake[6]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[5]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323: 
product] Error 2
gmake[5]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'
gmake[4]: *** [Makefile:203: generic_build2] Error 2
gmake[4]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
gmake[3]: *** [Makefile:158: product] Error 2
gmake[3]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
gmake[2]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
gmake[1]: *** [Makefile:251: build_product_image] Error 2
gmake[1]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2



--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html


From lenardrspencer at gmail.com  Mon Apr  4 14:29:27 2022
From: lenardrspencer at gmail.com (Lenard Spencer)
Date: Mon, 4 Apr 2022 10:29:27 -0400
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
Message-ID: <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>

openjdk8 now also requires gcc5, and will build with zulu-openjdk7 with a
minor script edit (BOOT_JAVA to point to zulu-openjdk7).  If the maintainer
approves I can send the patch.

I also have an SBo script that builds OpenJDK8 without using icedtea, using
zulu-openjdk7 (a repackaged binary).  If there is interest I can submit it.


On Mon, Apr 4, 2022, 09:10 Habs <gen-bch at useyouresp.org.uk> wrote:

> Hello everyone, good day
>
> Slackware 15, clean, fully updated
>
> The build either manually or via sbotools fails at the same place at the
> openjdk7 part.
>
> (part of the buildlog is below up until it bails out).
>
> Is it something I'm doing or something in the slackbuild and associate
> files and is there a quick 'fix' to try please ?
>
> Regards
> Habs
>
>
>
> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf
> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>
> -C
> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
>
> .
> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf
> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>
> -C /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes
> META-INF/services/com.sun.jdi.connect.Connector
> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but got
> 0xc7a06d31)
>          at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
>          at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
>          at java.io.FilterInputStream.read(FilterInputStream.java:107)
>          at sun.tools.jar.Main.copy(Main.java:822)
>          at sun.tools.jar.Main.update(Main.java:584)
>          at sun.tools.jar.Main.run(Main.java:224)
>          at sun.tools.jar.Main.main(Main.java:1231)
> gmake[8]: ***
> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86:
>
> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar]
>
> Error 1
> gmake[8]: Leaving directory
>
> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
> gmake[7]: ***
> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64:
>
> all] Error 2
> gmake[7]: Leaving directory
>
> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
> gmake[6]: ***
> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103:
>
> sa_stuff] Error 2
> gmake[6]: Leaving directory
>
> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
> gmake[5]: ***
> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323:
> product] Error 2
> gmake[5]: Leaving directory
> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'
> gmake[4]: *** [Makefile:203: generic_build2] Error 2
> gmake[4]: Leaving directory
> '/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
> gmake[3]: *** [Makefile:158: product] Error 2
> gmake[3]: Leaving directory
> '/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
> gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
> gmake[2]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
> gmake[1]: *** [Makefile:251: build_product_image] Error 2
> gmake[1]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
> make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2
>
>
>
> --- Sent using Alpine/Pine, probably the best MUA ---
>
> My Tox Messaging Id:
>
> 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
> Get a client here: https://tox.chat/clients.html
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220404/aed75050/attachment-0001.htm>

From matteo.bernardini at gmail.com  Mon Apr  4 14:39:05 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 4 Apr 2022 16:39:05 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
Message-ID: <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>

Il giorno lun 4 apr 2022 alle ore 16:29 Lenard Spencer <
lenardrspencer at gmail.com> ha scritto:

> openjdk8 now also requires gcc5, and will build with zulu-openjdk7 with a
> minor script edit (BOOT_JAVA to point to zulu-openjdk7).  If the maintainer
> approves I can send the patch.
>
> I also have an SBo script that builds OpenJDK8 without using icedtea,
> using zulu-openjdk7 (a repackaged binary).  If there is interest I can
> submit it.
>
>
> On Mon, Apr 4, 2022, 09:10 Habs <gen-bch at useyouresp.org.uk> wrote:
>
>> Hello everyone, good day
>>
>> Slackware 15, clean, fully updated
>>
>> The build either manually or via sbotools fails at the same place at the
>> openjdk7 part.
>>
>> (part of the buildlog is below up until it bails out).
>>
>> Is it something I'm doing or something in the slackbuild and associate
>> files and is there a quick 'fix' to try please ?
>>
>> Regards
>> Habs
>>
>>
>>
>> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf
>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>>
>> -C
>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
>>
>> .
>> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf
>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>>
>> -C
>> /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes
>> META-INF/services/com.sun.jdi.connect.Connector
>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
>> got
>> 0xc7a06d31)
>>          at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
>>          at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
>>          at java.io.FilterInputStream.read(FilterInputStream.java:107)
>>          at sun.tools.jar.Main.copy(Main.java:822)
>>          at sun.tools.jar.Main.update(Main.java:584)
>>          at sun.tools.jar.Main.run(Main.java:224)
>>          at sun.tools.jar.Main.main(Main.java:1231)
>> gmake[8]: ***
>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86:
>>
>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar]
>>
>> Error 1
>> gmake[8]: Leaving directory
>>
>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>> gmake[7]: ***
>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64:
>>
>> all] Error 2
>> gmake[7]: Leaving directory
>>
>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>> gmake[6]: ***
>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103:
>>
>> sa_stuff] Error 2
>> gmake[6]: Leaving directory
>>
>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>> gmake[5]: ***
>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323:
>> product] Error 2
>> gmake[5]: Leaving directory
>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'
>> gmake[4]: *** [Makefile:203: generic_build2] Error 2
>> gmake[4]: Leaving directory
>> '/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
>> gmake[3]: *** [Makefile:158: product] Error 2
>> gmake[3]: Leaving directory
>> '/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
>> gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
>> gmake[2]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
>> gmake[1]: *** [Makefile:251: build_product_image] Error 2
>> gmake[1]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
>> make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2
>>
>
Hi Lenard,

yes, and please have a look at openjdk7 too because here, testing the build
locally, I got the same error as Habs:

cp
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes/sun/jvm/hotspot/ui/resources/*.png
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/sun/jvm/hotspot/ui/resources/
cp -r
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes/images/*
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
-C
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
.
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
-C
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes
META-INF/services/com.sun.jdi.connect.Connector
java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but got
0xc7a06d31)
        at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
        at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
        at java.io.FilterInputStream.read(FilterInputStream.java:107)
        at sun.tools.jar.Main.copy(Main.java:822)
        at sun.tools.jar.Main.update(Main.java:584)
        at sun.tools.jar.Main.run(Main.java:224)
        at sun.tools.jar.Main.main(Main.java:1231)
gmake[8]: ***
[/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86:
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar]
Error 1
gmake[8]: Leaving directory
'/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[7]: ***
[/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64:
all] Error 2
gmake[7]: Leaving directory
'/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[6]: ***
[/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103:
sa_stuff] Error 2
gmake[6]: Leaving directory
'/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[5]: ***
[/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323:
product] Error 2
gmake[5]: Leaving directory
'/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'
gmake[4]: *** [Makefile:203: generic_build2] Error 2
gmake[4]: Leaving directory
'/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make'
gmake[3]: *** [Makefile:158: product] Error 2
gmake[3]: Leaving directory
'/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make'
gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
gmake[2]: Leaving directory
'/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk'
gmake[1]: *** [Makefile:251: build_product_image] Error 2
gmake[1]: Leaving directory
'/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk'
make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2

Matteo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220404/52ea2154/attachment.htm>

From erich.public at protonmail.com  Mon Apr  4 16:45:15 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Mon, 04 Apr 2022 16:45:15 +0000
Subject: [Slackbuilds-users] OpenVSP download (content-disposition issue)
Message-ID: <auH-ibwj0QADdoeW2zABh87r7BWuWrOGMca2ZhVi4WSnu2oxYnlxGCHtR9p4mwO-1_cTngPK0oBkmjUdtoLYZ47mLo6VRY3C0qwnvMq7QcU=@protonmail.com>

Hi Lenard,

The OpenVSP.info file lists the download as:

https://github.com/OpenVSP/OpenVSP/archive/OpenVSP_3.27.1.tar.gz

but slackrepo downloads the file as

OpenVSP-OpenVSP_3.27.1.tar.gz

due to its use of the --content-disposition flag to wget, forcing OpenVSP.SlackBuild to fail.

Can you update the OpenVSP.info file to specify a download file name as OpenVSP-OpenVSP_3.27.1.tar.gz?  This will make it compatible with all download methods.

Erich



From willysr at slackbuilds.org  Mon Apr  4 17:48:27 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 5 Apr 2022 00:48:27 +0700
Subject: [Slackbuilds-users] Submissions: wireplumber
In-Reply-To: <cb673ddf-da72-9877-9609-d61682f96e4c@free.fr>
References: <cb673ddf-da72-9877-9609-d61682f96e4c@free.fr>
Message-ID: <79927013-9003-72ec-7b48-2b5748d98451@slackbuilds.org>

> I can't? re-upload my SB for wireplumber, it says : "File exists; a
> submission by the name 'wireplumber' is already pending approval."
> 
> And when I try to remove it: "The file wireplumber.tar.gz does not exist
> in pending"
> 
> Can you at this ?

Fixed now
you can submit


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220405/31fc648a/attachment.asc>

From lramos.prof at yahoo.com.br  Mon Apr  4 23:22:25 2022
From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos)
Date: Mon, 4 Apr 2022 20:22:25 -0300
Subject: [Slackbuilds-users] gdal tarball possibly changed layout
References: <Ykt9sYZ8Drz1nvmW.ref@giustizia.lan>
Message-ID: <Ykt9sYZ8Drz1nvmW@giustizia.lan>

Hello,

these days I tried to build some packages which changed the SlackBuild
script, among them, gdal.

In the first run, it failed.

Searching a little bit, it seemed that the tarball has a slightly
different layout. In fact, everything that was supposed to be in the
root level is actually in the "./gdal" subdirectory.

Also, the "configure" script was not there. It was rebuilt running
"autoreconf -fi" in the right time.

I managed to tweak the slackbuild script and could ultimately build the
package. A patch is provided below.

Anyway, it's wise to check whether these findings happen in other
environments before taking any measure. One other possible cause would
be the tarball URL be incorrect.

Many thanks,

Luiz Ramos
lramos dot prof at yahoo dot com dot br
S?o Paulo - Brazil


===
>From 031fd83c1fb76a855bc423c4b113829f5595fd4b Mon Sep 17 00:00:00 2001
From: Luiz Ramos <lramos.prof at yahoo.com.br>
Date: Sun, 3 Apr 2022 19:46:55 -0300
Subject: [PATCH] gis/gdal: fixed build

Appearently the tarball downloaded changed its layout and so the build directory
has to be changed. Also, there is no "configure" file: it has to be build using
"autoreconf -fi".
---
 gis/gdal/gdal.SlackBuild | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/gis/gdal/gdal.SlackBuild b/gis/gdal/gdal.SlackBuild
index 4f83453333..056874624f 100644
--- a/gis/gdal/gdal.SlackBuild
+++ b/gis/gdal/gdal.SlackBuild
@@ -119,6 +119,9 @@ else
    WITHLIST+=" --with-jpeg=yes"
 fi
 
+cd gdal
+autoreconf -fi
+
 # The CPPFLAGS are for the newer mariadb (thanks pprkut!)
 CPPFLAGS="-I/usr/include/mysql/server" \
 CFLAGS="$SLKCFLAGS" \
@@ -154,13 +157,17 @@ CXXFLAGS="$SLKCFLAGS" \
 make
 make install DESTDIR=$PKG
 
+cd ..
+
 find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \
   | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
 
 mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
+cd gdal && \
 cp -a \
   COMMITTERS HOWTO-RELEASE LICENSE.TXT MIGRATION_GUIDE.TXT NEWS.md PROVENANCE.TXT VERSION \
-  $PKG/usr/doc/$PRGNAM-$VERSION
+  $PKG/usr/doc/$PRGNAM-$VERSION && \
+cd ..
 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
 
 rm -f $PKG/usr/lib*/*.la
-- 
2.35.1


From artourter at gmail.com  Mon Apr  4 23:46:47 2022
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Tue, 5 Apr 2022 00:46:47 +0100
Subject: [Slackbuilds-users] gdal tarball possibly changed layout
In-Reply-To: <Ykt9sYZ8Drz1nvmW@giustizia.lan>
References: <Ykt9sYZ8Drz1nvmW.ref@giustizia.lan>
 <Ykt9sYZ8Drz1nvmW@giustizia.lan>
Message-ID: <CAK09-vkfy-XEbeyWAHrh=3hnUtqEDRSV2hJH3feH39wukBbQeA@mail.gmail.com>

Hi Luis,

I submitted a fix a few days ago for this. in the meantime use the source
url off the slackbuild website:
https://github.com/OSGeo/gdal/releases/download/v3.4.2/gdal-3.4.2.tar.gz
or look at the change in git:
https://git.slackbuilds.org/slackbuilds/commit/?h=willysr&id=bf9481b91e81851503e8ae54d41022eb8bbbd666

Then you do not need to change anything to the slackbuild script.

Hope this helps

Cheers

Greg

On Tue, 5 Apr 2022 at 00:20, Luiz Carlos Ramos <lramos.prof at yahoo.com.br>
wrote:

> Hello,
>
> these days I tried to build some packages which changed the SlackBuild
> script, among them, gdal.
>
> In the first run, it failed.
>
> Searching a little bit, it seemed that the tarball has a slightly
> different layout. In fact, everything that was supposed to be in the
> root level is actually in the "./gdal" subdirectory.
>
> Also, the "configure" script was not there. It was rebuilt running
> "autoreconf -fi" in the right time.
>
> I managed to tweak the slackbuild script and could ultimately build the
> package. A patch is provided below.
>
> Anyway, it's wise to check whether these findings happen in other
> environments before taking any measure. One other possible cause would
> be the tarball URL be incorrect.
>
> Many thanks,
>
> Luiz Ramos
> lramos dot prof at yahoo dot com dot br
> S?o Paulo - Brazil
>
>
> ===
> From 031fd83c1fb76a855bc423c4b113829f5595fd4b Mon Sep 17 00:00:00 2001
> From: Luiz Ramos <lramos.prof at yahoo.com.br>
> Date: Sun, 3 Apr 2022 19:46:55 -0300
> Subject: [PATCH] gis/gdal: fixed build
>
> Appearently the tarball downloaded changed its layout and so the build
> directory
> has to be changed. Also, there is no "configure" file: it has to be build
> using
> "autoreconf -fi".
> ---
>  gis/gdal/gdal.SlackBuild | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/gis/gdal/gdal.SlackBuild b/gis/gdal/gdal.SlackBuild
> index 4f83453333..056874624f 100644
> --- a/gis/gdal/gdal.SlackBuild
> +++ b/gis/gdal/gdal.SlackBuild
> @@ -119,6 +119,9 @@ else
>     WITHLIST+=" --with-jpeg=yes"
>  fi
>
> +cd gdal
> +autoreconf -fi
> +
>  # The CPPFLAGS are for the newer mariadb (thanks pprkut!)
>  CPPFLAGS="-I/usr/include/mysql/server" \
>  CFLAGS="$SLKCFLAGS" \
> @@ -154,13 +157,17 @@ CXXFLAGS="$SLKCFLAGS" \
>  make
>  make install DESTDIR=$PKG
>
> +cd ..
> +
>  find $PKG | xargs file | grep -e "executable" -e "shared object" | grep
> ELF \
>    | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
>
>  mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
> +cd gdal && \
>  cp -a \
>    COMMITTERS HOWTO-RELEASE LICENSE.TXT MIGRATION_GUIDE.TXT NEWS.md
> PROVENANCE.TXT VERSION \
> -  $PKG/usr/doc/$PRGNAM-$VERSION
> +  $PKG/usr/doc/$PRGNAM-$VERSION && \
> +cd ..
>  cat $CWD/$PRGNAM.SlackBuild >
> $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
>
>  rm -f $PKG/usr/lib*/*.la
> --
> 2.35.1
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220405/1954c4f4/attachment.htm>

From lenardrspencer at gmail.com  Tue Apr  5 04:20:20 2022
From: lenardrspencer at gmail.com (Lenard Spencer)
Date: Tue, 5 Apr 2022 00:20:20 -0400
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
Message-ID: <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>

I have submitted  OpenJDK8.tar.gz to SBo.  I am also attaching a patch here
for Strahil's openjdk8 script.
As for openjdk(6,7), my scripts share a common problem when building on
32-bit.  They both fail to link with gcc5 libstdc++.so.6, insisting instead
on trying to link with /usr/lib/libstdc++.so.6, which belongs to gcc11.
Building on 64-bit doesn't show this problem.


On Mon, Apr 4, 2022 at 10:39 AM Matteo Bernardini <
matteo.bernardini at gmail.com> wrote:

> Il giorno lun 4 apr 2022 alle ore 16:29 Lenard Spencer <
> lenardrspencer at gmail.com> ha scritto:
>
>> openjdk8 now also requires gcc5, and will build with zulu-openjdk7 with a
>> minor script edit (BOOT_JAVA to point to zulu-openjdk7).  If the maintainer
>> approves I can send the patch.
>>
>> I also have an SBo script that builds OpenJDK8 without using icedtea,
>> using zulu-openjdk7 (a repackaged binary).  If there is interest I can
>> submit it.
>>
>>
>> On Mon, Apr 4, 2022, 09:10 Habs <gen-bch at useyouresp.org.uk> wrote:
>>
>>> Hello everyone, good day
>>>
>>> Slackware 15, clean, fully updated
>>>
>>> The build either manually or via sbotools fails at the same place at the
>>> openjdk7 part.
>>>
>>> (part of the buildlog is below up until it bails out).
>>>
>>> Is it something I'm doing or something in the slackbuild and associate
>>> files and is there a quick 'fix' to try please ?
>>>
>>> Regards
>>> Habs
>>>
>>>
>>>
>>> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf
>>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>>>
>>> -C
>>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
>>>
>>> .
>>> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf
>>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>>>
>>> -C
>>> /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes
>>> META-INF/services/com.sun.jdi.connect.Connector
>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
>>> got
>>> 0xc7a06d31)
>>>          at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
>>>          at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
>>>          at java.io.FilterInputStream.read(FilterInputStream.java:107)
>>>          at sun.tools.jar.Main.copy(Main.java:822)
>>>          at sun.tools.jar.Main.update(Main.java:584)
>>>          at sun.tools.jar.Main.run(Main.java:224)
>>>          at sun.tools.jar.Main.main(Main.java:1231)
>>> gmake[8]: ***
>>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86:
>>>
>>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar]
>>>
>>> Error 1
>>> gmake[8]: Leaving directory
>>>
>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>>> gmake[7]: ***
>>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64:
>>>
>>> all] Error 2
>>> gmake[7]: Leaving directory
>>>
>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>>> gmake[6]: ***
>>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103:
>>>
>>> sa_stuff] Error 2
>>> gmake[6]: Leaving directory
>>>
>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>>> gmake[5]: ***
>>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323:
>>>
>>> product] Error 2
>>> gmake[5]: Leaving directory
>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'
>>> gmake[4]: *** [Makefile:203: generic_build2] Error 2
>>> gmake[4]: Leaving directory
>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
>>> gmake[3]: *** [Makefile:158: product] Error 2
>>> gmake[3]: Leaving directory
>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
>>> gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
>>> gmake[2]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
>>> gmake[1]: *** [Makefile:251: build_product_image] Error 2
>>> gmake[1]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
>>> make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2
>>>
>>
> Hi Lenard,
>
> yes, and please have a look at openjdk7 too because here, testing the
> build locally, I got the same error as Habs:
>
> cp
> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes/sun/jvm/hotspot/ui/resources/*.png
> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/sun/jvm/hotspot/ui/resources/
> cp -r
> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes/images/*
> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf
> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
> -C
> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
> .
> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf
> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
> -C
> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes
> META-INF/services/com.sun.jdi.connect.Connector
> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but got
> 0xc7a06d31)
>         at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
>         at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
>         at java.io.FilterInputStream.read(FilterInputStream.java:107)
>         at sun.tools.jar.Main.copy(Main.java:822)
>         at sun.tools.jar.Main.update(Main.java:584)
>         at sun.tools.jar.Main.run(Main.java:224)
>         at sun.tools.jar.Main.main(Main.java:1231)
> gmake[8]: ***
> [/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86:
> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar]
> Error 1
> gmake[8]: Leaving directory
> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
> gmake[7]: ***
> [/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64:
> all] Error 2
> gmake[7]: Leaving directory
> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
> gmake[6]: ***
> [/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103:
> sa_stuff] Error 2
> gmake[6]: Leaving directory
> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
> gmake[5]: ***
> [/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323:
> product] Error 2
> gmake[5]: Leaving directory
> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'
> gmake[4]: *** [Makefile:203: generic_build2] Error 2
> gmake[4]: Leaving directory
> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make'
> gmake[3]: *** [Makefile:158: product] Error 2
> gmake[3]: Leaving directory
> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make'
> gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
> gmake[2]: Leaving directory
> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk'
> gmake[1]: *** [Makefile:251: build_product_image] Error 2
> gmake[1]: Leaving directory
> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk'
> make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220405/1f51667d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openjdk8.diff
Type: text/x-patch
Size: 4393 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220405/1f51667d/attachment-0001.bin>

From matteo.bernardini at gmail.com  Tue Apr  5 04:56:50 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 5 Apr 2022 06:56:50 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
Message-ID: <CAPsDuS5H7Y74XKmxP1WSQHGs8nBr5rW==Lzb5Sv5HvdpqR267Q@mail.gmail.com>

Hi Lenard, please have a look at openjdk7 too: from my test it doesn't
build on 64bit.

Matteo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220405/5b879061/attachment.htm>

From willysr at slackbuilds.org  Tue Apr  5 06:13:02 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 5 Apr 2022 13:13:02 +0700
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CAPsDuS5H7Y74XKmxP1WSQHGs8nBr5rW==Lzb5Sv5HvdpqR267Q@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <CAPsDuS5H7Y74XKmxP1WSQHGs8nBr5rW==Lzb5Sv5HvdpqR267Q@mail.gmail.com>
Message-ID: <02f7db7a-3d6b-4da9-380a-cda7a09660bf@slackbuilds.org>

> Hi Lenard, please have a look at openjdk7 too: from my test it doesn't
> build on 64bit.

I tested here on VM and it build

Slackware package /tmp/openjdk7-7u321-x86_64-1_SBo.tgz created.


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220405/82f7121c/attachment.asc>

From gen-bch at useyouresp.org.uk  Tue Apr  5 07:31:30 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Tue, 5 Apr 2022 08:31:30 +0100 (BST)
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
Message-ID: <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>


Hello folks

Perhaps I should have mentioned in my OP, it is a clean Slackware 15 64bit 
machine, just freshly installed and fully updated on April 3rd, before 
starting the openjdk8 build (ie. installing gcc5, apache-ant openjdk7 and 
lastly openjdk8).  It baulks at openjdk7 with errors as detailed in the 
OP.

The build was tried manually  and using sbotools. Same result.

Regards
Habs



On Tue, 5 Apr 2022, Lenard Spencer wrote:

> I have submitted  OpenJDK8.tar.gz to SBo.  I am also attaching a patch here
> for Strahil's openjdk8 script.
> As for openjdk(6,7), my scripts share a common problem when building on
> 32-bit.  They both fail to link with gcc5 libstdc++.so.6, insisting instead
> on trying to link with /usr/lib/libstdc++.so.6, which belongs to gcc11.
> Building on 64-bit doesn't show this problem.
>
>
> On Mon, Apr 4, 2022 at 10:39 AM Matteo Bernardini <
> matteo.bernardini at gmail.com> wrote:
>
>> Il giorno lun 4 apr 2022 alle ore 16:29 Lenard Spencer <
>> lenardrspencer at gmail.com> ha scritto:
>>
>>> openjdk8 now also requires gcc5, and will build with zulu-openjdk7 with a
>>> minor script edit (BOOT_JAVA to point to zulu-openjdk7).  If the maintainer
>>> approves I can send the patch.
>>>
>>> I also have an SBo script that builds OpenJDK8 without using icedtea,
>>> using zulu-openjdk7 (a repackaged binary).  If there is interest I can
>>> submit it.
>>>
>>>
>>> On Mon, Apr 4, 2022, 09:10 Habs <gen-bch at useyouresp.org.uk> wrote:
>>>
>>>> Hello everyone, good day
>>>>
>>>> Slackware 15, clean, fully updated
>>>>
>>>> The build either manually or via sbotools fails at the same place at the
>>>> openjdk7 part.
>>>>
>>>> (part of the buildlog is below up until it bails out).
>>>>
>>>> Is it something I'm doing or something in the slackbuild and associate
>>>> files and is there a quick 'fix' to try please ?
>>>>
>>>> Regards
>>>> Habs
>>>>
>>>>
>>>>
>>>> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf
>>>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>>>>
>>>> -C
>>>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
>>>>
>>>> .
>>>> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf
>>>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>>>>
>>>> -C
>>>> /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes
>>>> META-INF/services/com.sun.jdi.connect.Connector
>>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
>>>> got
>>>> 0xc7a06d31)
>>>>          at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
>>>>          at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
>>>>          at java.io.FilterInputStream.read(FilterInputStream.java:107)
>>>>          at sun.tools.jar.Main.copy(Main.java:822)
>>>>          at sun.tools.jar.Main.update(Main.java:584)
>>>>          at sun.tools.jar.Main.run(Main.java:224)
>>>>          at sun.tools.jar.Main.main(Main.java:1231)
>>>> gmake[8]: ***
>>>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86:
>>>>
>>>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar]
>>>>
>>>> Error 1
>>>> gmake[8]: Leaving directory
>>>>
>>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>>>> gmake[7]: ***
>>>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64:
>>>>
>>>> all] Error 2
>>>> gmake[7]: Leaving directory
>>>>
>>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>>>> gmake[6]: ***
>>>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103:
>>>>
>>>> sa_stuff] Error 2
>>>> gmake[6]: Leaving directory
>>>>
>>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>>>> gmake[5]: ***
>>>> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323:
>>>>
>>>> product] Error 2
>>>> gmake[5]: Leaving directory
>>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'
>>>> gmake[4]: *** [Makefile:203: generic_build2] Error 2
>>>> gmake[4]: Leaving directory
>>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
>>>> gmake[3]: *** [Makefile:158: product] Error 2
>>>> gmake[3]: Leaving directory
>>>> '/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
>>>> gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
>>>> gmake[2]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
>>>> gmake[1]: *** [Makefile:251: build_product_image] Error 2
>>>> gmake[1]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
>>>> make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2
>>>>
>>>
>> Hi Lenard,
>>
>> yes, and please have a look at openjdk7 too because here, testing the
>> build locally, I got the same error as Habs:
>>
>> cp
>> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes/sun/jvm/hotspot/ui/resources/*.png
>> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/sun/jvm/hotspot/ui/resources/
>> cp -r
>> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes/images/*
>> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
>> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf
>> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>> -C
>> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
>> .
>> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf
>> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>> -C
>> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes
>> META-INF/services/com.sun.jdi.connect.Connector
>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but got
>> 0xc7a06d31)
>>         at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
>>         at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
>>         at java.io.FilterInputStream.read(FilterInputStream.java:107)
>>         at sun.tools.jar.Main.copy(Main.java:822)
>>         at sun.tools.jar.Main.update(Main.java:584)
>>         at sun.tools.jar.Main.run(Main.java:224)
>>         at sun.tools.jar.Main.main(Main.java:1231)
>> gmake[8]: ***
>> [/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86:
>> /tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar]
>> Error 1
>> gmake[8]: Leaving directory
>> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>> gmake[7]: ***
>> [/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64:
>> all] Error 2
>> gmake[7]: Leaving directory
>> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>> gmake[6]: ***
>> [/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103:
>> sa_stuff] Error 2
>> gmake[6]: Leaving directory
>> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
>> gmake[5]: ***
>> [/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323:
>> product] Error 2
>> gmake[5]: Leaving directory
>> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'
>> gmake[4]: *** [Makefile:203: generic_build2] Error 2
>> gmake[4]: Leaving directory
>> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make'
>> gmake[3]: *** [Makefile:158: product] Error 2
>> gmake[3]: Leaving directory
>> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/make'
>> gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
>> gmake[2]: Leaving directory
>> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk'
>> gmake[1]: *** [Makefile:251: build_product_image] Error 2
>> gmake[1]: Leaving directory
>> '/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk'
>> make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2
>>
>> Matteo
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>

--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html


From willysr at slackbuilds.org  Tue Apr  5 07:38:25 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 5 Apr 2022 14:38:25 +0700
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
Message-ID: <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>

> Perhaps I should have mentioned in my OP, it is a clean Slackware 15
> 64bit machine, just freshly installed and fully updated on April 3rd,
> before starting the openjdk8 build (ie. installing gcc5, apache-ant
> openjdk7 and lastly openjdk8).? It baulks at openjdk7 with errors as
> detailed in the OP.
> 
> The build was tried manually? and using sbotools. Same result.

I just tested openjdk8 on a clean VM and it built just fine using sbopkg

openjdk8:
  MD5SUM check for icedtea-3.20.0.tar.xz ... OK
  MD5SUM check for openjdk.tar.xz ... OK
  MD5SUM check for corba.tar.xz ... OK
  MD5SUM check for jaxp.tar.xz ... OK
  MD5SUM check for jaxws.tar.xz ... OK
  MD5SUM check for jdk.tar.xz ... OK
  MD5SUM check for langtools.tar.xz ... OK
  MD5SUM check for nashorn.tar.xz ... OK
  MD5SUM check for hotspot.tar.xz ... OK
  Building package openjdk8-8u292-x86_64-1_SBo.tgz ... OK
  Installing package openjdk8-8u292-x86_64-1_SBo.tgz ... OK

openjdk7 also built just fine as that's the requirement to build openjdk8


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220405/2295247d/attachment.asc>

From gen-bch at useyouresp.org.uk  Tue Apr  5 08:33:21 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Tue, 5 Apr 2022 09:33:21 +0100 (BST)
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
Message-ID: <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>

On Tue, 5 Apr 2022, Willy Sudiarto Raharjo wrote:

>> Perhaps I should have mentioned in my OP, it is a clean Slackware 15
>> 64bit machine, just freshly installed and fully updated on April 3rd,
>> before starting the openjdk8 build (ie. installing gcc5, apache-ant
>> openjdk7 and lastly openjdk8).? It baulks at openjdk7 with errors as
>> detailed in the OP.
>>
>> The build was tried manually? and using sbotools. Same result.
>
> I just tested openjdk8 on a clean VM and it built just fine using sbopkg
>
> openjdk8:
>  MD5SUM check for icedtea-3.20.0.tar.xz ... OK
>  MD5SUM check for openjdk.tar.xz ... OK
>  MD5SUM check for corba.tar.xz ... OK
>  MD5SUM check for jaxp.tar.xz ... OK
>  MD5SUM check for jaxws.tar.xz ... OK
>  MD5SUM check for jdk.tar.xz ... OK
>  MD5SUM check for langtools.tar.xz ... OK
>  MD5SUM check for nashorn.tar.xz ... OK
>  MD5SUM check for hotspot.tar.xz ... OK
>  Building package openjdk8-8u292-x86_64-1_SBo.tgz ... OK
>  Installing package openjdk8-8u292-x86_64-1_SBo.tgz ... OK
>
> openjdk7 also built just fine as that's the requirement to build openjdk8
>
>
> -- 
> Willy Sudiarto Raharjo
>

Yes I noted from your earlier message you had success in a VM.

The physical machine platform I used was not so.  Strange.

I will take the hit and strip it and have another go and see what happens.

Essentially just repeating earlier what I did earlier, repartition disk 
etc, Install Slackware 15 64, update it using 'update-all' (slackpkg) 
then install gcc5, apache-ant, openjdk7, openjdk8 using the packages on 
'slackbuilds'.

Regards
Habs


--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html

From gen-bch at useyouresp.org.uk  Tue Apr  5 11:09:27 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Tue, 5 Apr 2022 12:09:27 +0100 (BST)
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
Message-ID: <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>

On Tue, 5 Apr 2022, Habs wrote:

> On Tue, 5 Apr 2022, Willy Sudiarto Raharjo wrote:
>
>>> Perhaps I should have mentioned in my OP, it is a clean Slackware 15
>>> 64bit machine, just freshly installed and fully updated on April 3rd,
>>> before starting the openjdk8 build (ie. installing gcc5, apache-ant
>>> openjdk7 and lastly openjdk8).? It baulks at openjdk7 with errors as
>>> detailed in the OP.
>>> 
>>> The build was tried manually? and using sbotools. Same result.
>> 
>> I just tested openjdk8 on a clean VM and it built just fine using sbopkg
>> 
>> openjdk8:
>>  MD5SUM check for icedtea-3.20.0.tar.xz ... OK
>>  MD5SUM check for openjdk.tar.xz ... OK
>>  MD5SUM check for corba.tar.xz ... OK
>>  MD5SUM check for jaxp.tar.xz ... OK
>>  MD5SUM check for jaxws.tar.xz ... OK
>>  MD5SUM check for jdk.tar.xz ... OK
>>  MD5SUM check for langtools.tar.xz ... OK
>>  MD5SUM check for nashorn.tar.xz ... OK
>>  MD5SUM check for hotspot.tar.xz ... OK
>>  Building package openjdk8-8u292-x86_64-1_SBo.tgz ... OK
>>  Installing package openjdk8-8u292-x86_64-1_SBo.tgz ... OK
>> 
>> openjdk7 also built just fine as that's the requirement to build openjdk8
>> 
>> 
>> -- 
>> Willy Sudiarto Raharjo
>> 
>
> Yes I noted from your earlier message you had success in a VM.
>
> The physical machine platform I used was not so.  Strange.
>
> I will take the hit and strip it and have another go and see what happens.
>
> Essentially just repeating earlier what I did earlier, repartition disk etc, 
> Install Slackware 15 64, update it using 'update-all' (slackpkg) then install 
> gcc5, apache-ant, openjdk7, openjdk8 using the packages on 'slackbuilds'.
>



Starting afresh - clean [physical] machine Slackware 15 64 then update-all 
(slackpkg) - same 'result'; same error and drops out at the openjdk7 build 
just as before.


Regards
Habs


From willysr at slackbuilds.org  Tue Apr  5 13:25:39 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 5 Apr 2022 20:25:39 +0700
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
Message-ID: <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>

> Starting afresh - clean [physical] machine Slackware 15 64 then
> update-all (slackpkg) - same 'result'; same error and drops out at the
> openjdk7 build just as before.

Just to make sure
did you run "su -" instead of just "su" ?


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220405/32cb1a15/attachment.asc>

From kjhambrick at gmail.com  Tue Apr  5 15:53:13 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Tue, 5 Apr 2022 10:53:13 -0500
Subject: [Slackbuilds-users] gdal tarball possibly changed layout
In-Reply-To: <CAK09-vkfy-XEbeyWAHrh=3hnUtqEDRSV2hJH3feH39wukBbQeA@mail.gmail.com>
References: <Ykt9sYZ8Drz1nvmW.ref@giustizia.lan>
 <Ykt9sYZ8Drz1nvmW@giustizia.lan>
 <CAK09-vkfy-XEbeyWAHrh=3hnUtqEDRSV2hJH3feH39wukBbQeA@mail.gmail.com>
Message-ID: <CANBHt+MO5LwUV4_X6TV1WQ7CPf=PFw0Ro0E+VkdZ+9cH_2PjVw@mail.gmail.com>

Thanks Greg !

Building gdal 3.4.2 now :)

-- kjh

On Mon, Apr 4, 2022 at 6:47 PM Greg' Ar Tourter <artourter at gmail.com> wrote:

> Hi Luis,
>
> I submitted a fix a few days ago for this. in the meantime use the source
> url off the slackbuild website:
> https://github.com/OSGeo/gdal/releases/download/v3.4.2/gdal-3.4.2.tar.gz
> or look at the change in git:
>
> https://git.slackbuilds.org/slackbuilds/commit/?h=willysr&id=bf9481b91e81851503e8ae54d41022eb8bbbd666
>
> Then you do not need to change anything to the slackbuild script.
>
> Hope this helps
>
> Cheers
>
> Greg
>
> On Tue, 5 Apr 2022 at 00:20, Luiz Carlos Ramos <lramos.prof at yahoo.com.br>
> wrote:
>
>> Hello,
>>
>> these days I tried to build some packages which changed the SlackBuild
>> script, among them, gdal.
>>
>> In the first run, it failed.
>>
>> Searching a little bit, it seemed that the tarball has a slightly
>> different layout. In fact, everything that was supposed to be in the
>> root level is actually in the "./gdal" subdirectory.
>>
>> Also, the "configure" script was not there. It was rebuilt running
>> "autoreconf -fi" in the right time.
>>
>> I managed to tweak the slackbuild script and could ultimately build the
>> package. A patch is provided below.
>>
>> Anyway, it's wise to check whether these findings happen in other
>> environments before taking any measure. One other possible cause would
>> be the tarball URL be incorrect.
>>
>> Many thanks,
>>
>> Luiz Ramos
>> lramos dot prof at yahoo dot com dot br
>> S?o Paulo - Brazil
>>
>>
>> ===
>> From 031fd83c1fb76a855bc423c4b113829f5595fd4b Mon Sep 17 00:00:00 2001
>> From: Luiz Ramos <lramos.prof at yahoo.com.br>
>> Date: Sun, 3 Apr 2022 19:46:55 -0300
>> Subject: [PATCH] gis/gdal: fixed build
>>
>> Appearently the tarball downloaded changed its layout and so the build
>> directory
>> has to be changed. Also, there is no "configure" file: it has to be build
>> using
>> "autoreconf -fi".
>> ---
>>  gis/gdal/gdal.SlackBuild | 9 ++++++++-
>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/gis/gdal/gdal.SlackBuild b/gis/gdal/gdal.SlackBuild
>> index 4f83453333..056874624f 100644
>> --- a/gis/gdal/gdal.SlackBuild
>> +++ b/gis/gdal/gdal.SlackBuild
>> @@ -119,6 +119,9 @@ else
>>     WITHLIST+=" --with-jpeg=yes"
>>  fi
>>
>> +cd gdal
>> +autoreconf -fi
>> +
>>  # The CPPFLAGS are for the newer mariadb (thanks pprkut!)
>>  CPPFLAGS="-I/usr/include/mysql/server" \
>>  CFLAGS="$SLKCFLAGS" \
>> @@ -154,13 +157,17 @@ CXXFLAGS="$SLKCFLAGS" \
>>  make
>>  make install DESTDIR=$PKG
>>
>> +cd ..
>> +
>>  find $PKG | xargs file | grep -e "executable" -e "shared object" | grep
>> ELF \
>>    | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
>>
>>  mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
>> +cd gdal && \
>>  cp -a \
>>    COMMITTERS HOWTO-RELEASE LICENSE.TXT MIGRATION_GUIDE.TXT NEWS.md
>> PROVENANCE.TXT VERSION \
>> -  $PKG/usr/doc/$PRGNAM-$VERSION
>> +  $PKG/usr/doc/$PRGNAM-$VERSION && \
>> +cd ..
>>  cat $CWD/$PRGNAM.SlackBuild >
>> $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
>>
>>  rm -f $PKG/usr/lib*/*.la
>> --
>> 2.35.1
>>
>> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220405/3858e511/attachment.htm>

From kjhambrick at gmail.com  Tue Apr  5 16:23:07 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Tue, 5 Apr 2022 11:23:07 -0500
Subject: [Slackbuilds-users] gdal tarball possibly changed layout
In-Reply-To: <CANBHt+MO5LwUV4_X6TV1WQ7CPf=PFw0Ro0E+VkdZ+9cH_2PjVw@mail.gmail.com>
References: <Ykt9sYZ8Drz1nvmW.ref@giustizia.lan>
 <Ykt9sYZ8Drz1nvmW@giustizia.lan>
 <CAK09-vkfy-XEbeyWAHrh=3hnUtqEDRSV2hJH3feH39wukBbQeA@mail.gmail.com>
 <CANBHt+MO5LwUV4_X6TV1WQ7CPf=PFw0Ro0E+VkdZ+9cH_2PjVw@mail.gmail.com>
Message-ID: <CANBHt+PbdjCpCqzab5zZyWV0B4dMqaXUBXc0Gi=ngGrB_C9fOA@mail.gmail.com>

Thanks Greg.

Worked Great !

OTB ( montevideo ) is running as expected without a rebuild with gdal 3.4.2

-- kjh


On Tue, Apr 5, 2022 at 10:53 AM Konrad J Hambrick <kjhambrick at gmail.com>
wrote:

> Thanks Greg !
>
> Building gdal 3.4.2 now :)
>
> -- kjh
>
> On Mon, Apr 4, 2022 at 6:47 PM Greg' Ar Tourter <artourter at gmail.com>
> wrote:
>
>> Hi Luis,
>>
>> I submitted a fix a few days ago for this. in the meantime use the source
>> url off the slackbuild website:
>> https://github.com/OSGeo/gdal/releases/download/v3.4.2/gdal-3.4.2.tar.gz
>> or look at the change in git:
>>
>> https://git.slackbuilds.org/slackbuilds/commit/?h=willysr&id=bf9481b91e81851503e8ae54d41022eb8bbbd666
>>
>> Then you do not need to change anything to the slackbuild script.
>>
>> Hope this helps
>>
>> Cheers
>>
>> Greg
>>
>> On Tue, 5 Apr 2022 at 00:20, Luiz Carlos Ramos <lramos.prof at yahoo.com.br>
>> wrote:
>>
>>> Hello,
>>>
>>> these days I tried to build some packages which changed the SlackBuild
>>> script, among them, gdal.
>>>
>>> In the first run, it failed.
>>>
>>> Searching a little bit, it seemed that the tarball has a slightly
>>> different layout. In fact, everything that was supposed to be in the
>>> root level is actually in the "./gdal" subdirectory.
>>>
>>> Also, the "configure" script was not there. It was rebuilt running
>>> "autoreconf -fi" in the right time.
>>>
>>> I managed to tweak the slackbuild script and could ultimately build the
>>> package. A patch is provided below.
>>>
>>> Anyway, it's wise to check whether these findings happen in other
>>> environments before taking any measure. One other possible cause would
>>> be the tarball URL be incorrect.
>>>
>>> Many thanks,
>>>
>>> Luiz Ramos
>>> lramos dot prof at yahoo dot com dot br
>>> S?o Paulo - Brazil
>>>
>>>
>>> ===
>>> From 031fd83c1fb76a855bc423c4b113829f5595fd4b Mon Sep 17 00:00:00 2001
>>> From: Luiz Ramos <lramos.prof at yahoo.com.br>
>>> Date: Sun, 3 Apr 2022 19:46:55 -0300
>>> Subject: [PATCH] gis/gdal: fixed build
>>>
>>> Appearently the tarball downloaded changed its layout and so the build
>>> directory
>>> has to be changed. Also, there is no "configure" file: it has to be
>>> build using
>>> "autoreconf -fi".
>>> ---
>>>  gis/gdal/gdal.SlackBuild | 9 ++++++++-
>>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/gis/gdal/gdal.SlackBuild b/gis/gdal/gdal.SlackBuild
>>> index 4f83453333..056874624f 100644
>>> --- a/gis/gdal/gdal.SlackBuild
>>> +++ b/gis/gdal/gdal.SlackBuild
>>> @@ -119,6 +119,9 @@ else
>>>     WITHLIST+=" --with-jpeg=yes"
>>>  fi
>>>
>>> +cd gdal
>>> +autoreconf -fi
>>> +
>>>  # The CPPFLAGS are for the newer mariadb (thanks pprkut!)
>>>  CPPFLAGS="-I/usr/include/mysql/server" \
>>>  CFLAGS="$SLKCFLAGS" \
>>> @@ -154,13 +157,17 @@ CXXFLAGS="$SLKCFLAGS" \
>>>  make
>>>  make install DESTDIR=$PKG
>>>
>>> +cd ..
>>> +
>>>  find $PKG | xargs file | grep -e "executable" -e "shared object" | grep
>>> ELF \
>>>    | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
>>>
>>>  mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
>>> +cd gdal && \
>>>  cp -a \
>>>    COMMITTERS HOWTO-RELEASE LICENSE.TXT MIGRATION_GUIDE.TXT NEWS.md
>>> PROVENANCE.TXT VERSION \
>>> -  $PKG/usr/doc/$PRGNAM-$VERSION
>>> +  $PKG/usr/doc/$PRGNAM-$VERSION && \
>>> +cd ..
>>>  cat $CWD/$PRGNAM.SlackBuild >
>>> $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
>>>
>>>  rm -f $PKG/usr/lib*/*.la
>>> --
>>> 2.35.1
>>>
>>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220405/14b05df0/attachment-0001.htm>

From gen-bch at useyouresp.org.uk  Tue Apr  5 16:57:16 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Tue, 5 Apr 2022 17:57:16 +0100 (BST)
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
Message-ID: <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>

On Tue, 5 Apr 2022, Willy Sudiarto Raharjo wrote:

>> Starting afresh - clean [physical] machine Slackware 15 64 then
>> update-all (slackpkg) - same 'result'; same error and drops out at the
>> openjdk7 build just as before.
>
> Just to make sure
> did you run "su -" instead of just "su" ?

yes - in fact, with and without.

As an aside, I have run these openjdk's before (without '-') and had no 
problems.  I will rerun the whole chain again (with the '-') to make sure 
and clean out beforehand.

Having said that, the error has been the same and the machine rebuilt 
twice now to be 'clean' before starting. It's started happening fairly 
recently, as prior, all was well.

One wonders if the  recent slackpkg updates have introduced something.  It 
has never been this flaky previously for me.


Will post again when I've had another go.

Thank you
Habs

From roberto.puzzanghera at sagredo.eu  Tue Apr  5 19:08:29 2022
From: roberto.puzzanghera at sagredo.eu (Roberto Puzzanghera)
Date: Tue, 5 Apr 2022 21:08:29 +0200
Subject: [Slackbuilds-users] Viking slackbuild
Message-ID: <cd5c1e1c-1c83-3e12-db98-a562b9a33db9@sagredo.eu>

I contacted the maintainer of vikings, because the current version was 
published in 2015, and got no response.

I also browsed both the pending and ready queue and didn't find any 
update. It seems like it is not maintained anymore.

Can I take it over? I would be my first package

Roberto

From gen-bch at useyouresp.org.uk  Tue Apr  5 20:00:13 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Tue, 5 Apr 2022 21:00:13 +0100 (BST)
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
Message-ID: <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>

On Tue, 5 Apr 2022, Habs wrote:

> On Tue, 5 Apr 2022, Willy Sudiarto Raharjo wrote:
>
>>> Starting afresh - clean [physical] machine Slackware 15 64 then
>>> update-all (slackpkg) - same 'result'; same error and drops out at the
>>> openjdk7 build just as before.
>> 
>> Just to make sure
>> did you run "su -" instead of just "su" ?
>
> yes - in fact, with and without.
>
> As an aside, I have run these openjdk's before (without '-') and had no 
> problems.  I will rerun the whole chain again (with the '-') to make sure and 
> clean out beforehand.
>
> Having said that, the error has been the same and the machine rebuilt twice 
> now to be 'clean' before starting. It's started happening fairly recently, as 
> prior, all was well.
>
> One wonders if the  recent slackpkg updates have introduced something.  It 
> has never been this flaky previously for me.
>
>
> Will post again when I've had another go.
>


Right then.  I've had another do (and using 'su -') and its the same 
result.  openjdk7 fails as reported by Matteo and myself.

Perhaps there is a setting somewhere I'm missing. Perhaps a new 
incompatibility somewhere since the slackbuild was packaged.

I can't fathom why it's fine on a VM as has been reported, but on this 
[physical] machine, all I have tried (inc. two rebuilds for a clean 
machine) has not resulted in a successful build.

As I say, it has worked previously, but not now.

Here again is the last few bits of the openjdk7 build log until it bails.

/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar 
-C /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes 
META-INF/services/com.sun.jdi.connect.Connector
java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but got 
0xc7a06d31)
         at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
         at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
         at java.io.FilterInputStream.read(FilterInputStream.java:107)
         at sun.tools.jar.Main.copy(Main.java:822)
         at sun.tools.jar.Main.update(Main.java:584)
         at sun.tools.jar.Main.run(Main.java:224)
         at sun.tools.jar.Main.main(Main.java:1231)
gmake[8]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86: 
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar] 
Error 1
gmake[8]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[7]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64: 
all] Error 2
gmake[7]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[6]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103: 
sa_stuff] Error 2
gmake[6]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[5]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323: 
product] Error 2
gmake[5]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'
gmake[4]: *** [Makefile:203: generic_build2] Error 2
gmake[4]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
gmake[3]: *** [Makefile:158: product] Error 2
gmake[3]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
gmake[2]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
gmake[1]: *** [Makefile:251: build_product_image] Error 2
gmake[1]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2



Regards and thank you
Habs

From chris.willing at linux.com  Tue Apr  5 20:39:04 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Wed, 6 Apr 2022 06:39:04 +1000
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
Message-ID: <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>

On 6/4/22 06:00, Habs wrote:
> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
> got 0xc7a06d31)

This looks like you're inadvertently using the wrong set of source
files. Each new openjdk version has a new set of source files, many of
which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
your build system can easily pick up the wrong source file.

chris

From willysr at slackbuilds.org  Wed Apr  6 02:52:03 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 6 Apr 2022 09:52:03 +0700
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
Message-ID: <674dc46a-d6fc-b2a6-b35f-3cdec7c24faa@slackbuilds.org>

>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
>> got 0xc7a06d31)
> 
> This looks like you're inadvertently using the wrong set of source
> files. Each new openjdk version has a new set of source files, many of
> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
> your build system can easily pick up the wrong source file.

I think i had the same failures when building openjdk8 using sbopkg
because it has the same filename as openjdk7, so i tried to download it
manually and build it and it went fine


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220406/07b92ee9/attachment.asc>

From lenardrspencer at gmail.com  Wed Apr  6 04:56:54 2022
From: lenardrspencer at gmail.com (Lenard Spencer)
Date: Wed, 6 Apr 2022 00:56:54 -0400
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <674dc46a-d6fc-b2a6-b35f-3cdec7c24faa@slackbuilds.org>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <674dc46a-d6fc-b2a6-b35f-3cdec7c24faa@slackbuilds.org>
Message-ID: <CANSA5-uAoQQ5_SXYiA-fLJKw1_FvQ6Syu5mQN+7UA9NRU7-hbw@mail.gmail.com>

Matteo, I got it slightly wrong.  The openjdk8 script (don't forget the
patch I posted) does NOT need gcc5, and it builds u322b03 (a beta
version).  The OpenJDK8 script I submitted to SBo is u322-ga, and while it
doesn't use icedtea, it DOES require gcc5.  Both will require
zulu-openjdk7, since I have yet to solve the problem of the 32-bit build
linking against the default gcc11 libstd++.so.6 (in /usr/lib) instead of
the one in gcc5.  It worked back in early June, though.

On Tue, Apr 5, 2022 at 10:52 PM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> >> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
> >> got 0xc7a06d31)
> >
> > This looks like you're inadvertently using the wrong set of source
> > files. Each new openjdk version has a new set of source files, many of
> > which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
> > your build system can easily pick up the wrong source file.
>
> I think i had the same failures when building openjdk8 using sbopkg
> because it has the same filename as openjdk7, so i tried to download it
> manually and build it and it went fine
>
>
> --
> Willy Sudiarto Raharjo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220406/0090c4f7/attachment-0001.htm>

From matteo.bernardini at gmail.com  Wed Apr  6 05:25:49 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 6 Apr 2022 07:25:49 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
Message-ID: <CAPsDuS4O-FOysbmbrV0VHj4j81L3QSQNeT9Zb+6Zx11pdK0Q3A@mail.gmail.com>

Il giorno mar 5 apr 2022 alle ore 22:39 Christoph Willing <
chris.willing at linux.com> ha scritto:

> On 6/4/22 06:00, Habs wrote:
> > java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
> > got 0xc7a06d31)
>
> This looks like you're inadvertently using the wrong set of source
> files. Each new openjdk version has a new set of source files, many of
> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
> your build system can easily pick up the wrong source file.
>

could be we are still missing something but unfortunately I tried multiple
times manually to verify I hadn't got anything wrong (I also reinstalled a
vm from scratch) and redownloaded the sources too but still got the same
error.
Lenard, can you try building again openjdk7 (not openjdk8) from scratch
locally and verify that everything is building ok for you?

Matteo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220406/e6c7393a/attachment.htm>

From matteo.bernardini at gmail.com  Wed Apr  6 05:27:50 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 6 Apr 2022 07:27:50 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CAPsDuS4O-FOysbmbrV0VHj4j81L3QSQNeT9Zb+6Zx11pdK0Q3A@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <CAPsDuS4O-FOysbmbrV0VHj4j81L3QSQNeT9Zb+6Zx11pdK0Q3A@mail.gmail.com>
Message-ID: <CAPsDuS6HoDnMNtyJ7AxyU0RaY+5HurCq7heoVchDYbsKG=wq3w@mail.gmail.com>

Il giorno mer 6 apr 2022 alle ore 07:25 Matteo Bernardini <
matteo.bernardini at gmail.com> ha scritto:

> Il giorno mar 5 apr 2022 alle ore 22:39 Christoph Willing <
> chris.willing at linux.com> ha scritto:
>
>> On 6/4/22 06:00, Habs wrote:
>> > java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
>> > got 0xc7a06d31)
>>
>> This looks like you're inadvertently using the wrong set of source
>> files. Each new openjdk version has a new set of source files, many of
>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
>> your build system can easily pick up the wrong source file.
>>
>
> could be we are still missing something but unfortunately I tried multiple
> times manually to verify I hadn't got anything wrong (I also reinstalled a
> vm from scratch) and redownloaded the sources too but still got the same
> error.
> Lenard, can you try building again openjdk7 (not openjdk8) from scratch
> locally and verify that everything is building ok for you?
>

Note that the environment where you should try this *must* contain the
latest updates to slackware 15.0.

Matteo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220406/afae5506/attachment.htm>

From gen-bch at useyouresp.org.uk  Wed Apr  6 07:42:51 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Wed, 6 Apr 2022 08:42:51 +0100 (BST)
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
Message-ID: <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>

On Wed, 6 Apr 2022, Christoph Willing wrote:

> On 6/4/22 06:00, Habs wrote:
>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
>> got 0xc7a06d31)
>
> This looks like you're inadvertently using the wrong set of source
> files. Each new openjdk version has a new set of source files, many of
> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
> your build system can easily pick up the wrong source file.
>
> chris

Good morning all

I do not doubt the comment above, but in this case, how could it be unless 
the slackbuild source links are out of step/compromised/whatever.

As I mentioned, it is a clean physical machine freshly installed and then 
updated - no other [java related or other slackbuild addons etc] downloads 
prior - and simply the source files linked in the slackbuild info.  Each 
slackbuild individually run using 'su -' (rather than using sbotools or 
similar) as required.  I don't even get to try openjdk8 (or download 
anything for it) as apache-ant, gcc5 and openjdk7 are listed as required 
first.  It is openjdk7 that is failing in that chain as such.

That all said, I will go back and check the sources, though I think that 
has been done by Matteo.

Regards
Habs



From arnaud.garcia-fernandez at laposte.net  Wed Apr  6 08:09:56 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Wed, 6 Apr 2022 10:09:56 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
Message-ID: <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>

> >> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
> >> got 0xc7a06d31)
> >
> > This looks like you're inadvertently using the wrong set of source
> > files. Each new openjdk version has a new set of source files, many of
> > which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
> > your build system can easily pick up the wrong source file.
> >
> > chris
> 
> Good morning all
> 
> I do not doubt the comment above, but in this case, how could it be unless 
> the slackbuild source links are out of step/compromised/whatever.
> 
> As I mentioned, it is a clean physical machine freshly installed and then 
> updated - no other [java related or other slackbuild addons etc] downloads 
> prior - and simply the source files linked in the slackbuild info.  Each 
> slackbuild individually run using 'su -' (rather than using sbotools or 
> similar) as required.  I don't even get to try openjdk8 (or download 
> anything for it) as apache-ant, gcc5 and openjdk7 are listed as required 
> first.  It is openjdk7 that is failing in that chain as such.
> 
> That all said, I will go back and check the sources, though I think that 
> has been done by Matteo.
> 
> Regards
> Habs

My comment will not add much to the problem, but my several tries are all failing at the same place (ie: invalid entry CRC).
Be it on my master very unclean multilib box, a chroot, multilib or not, updated and clean, or some other cleaner boxes, VMs, not multilib, I can't make it build, and it always fails on the same place...

But unlike others here, I don't pretend doing it on perfectly clean installations (though always without any other java installed).
Although I am really sure my source packages are the right ones, MD5SUM checked and all.

-- 
Arnaud <arnaud.garcia-fernandez at laposte.net>

From artourter at gmail.com  Wed Apr  6 09:49:16 2022
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Wed, 6 Apr 2022 10:49:16 +0100
Subject: [Slackbuilds-users] gdal tarball possibly changed layout
In-Reply-To: <CANBHt+PbdjCpCqzab5zZyWV0B4dMqaXUBXc0Gi=ngGrB_C9fOA@mail.gmail.com>
References: <Ykt9sYZ8Drz1nvmW.ref@giustizia.lan>
 <Ykt9sYZ8Drz1nvmW@giustizia.lan>
 <CAK09-vkfy-XEbeyWAHrh=3hnUtqEDRSV2hJH3feH39wukBbQeA@mail.gmail.com>
 <CANBHt+MO5LwUV4_X6TV1WQ7CPf=PFw0Ro0E+VkdZ+9cH_2PjVw@mail.gmail.com>
 <CANBHt+PbdjCpCqzab5zZyWV0B4dMqaXUBXc0Gi=ngGrB_C9fOA@mail.gmail.com>
Message-ID: <CAK09-vnVkY1qhq_wO31gyA5osc5u0ozu1e9zPHnAobvxZxYE3g@mail.gmail.com>

Konrad,

note that if you are using OTB, the slackbuild is currently not maintained
as Benjamin unfortunately has stopped maintaining his builds. So if you
feel like taking it up, I suspect it is free.

Greg

On Tue, 5 Apr 2022 at 17:23, Konrad J Hambrick <kjhambrick at gmail.com> wrote:

> Thanks Greg.
>
> Worked Great !
>
> OTB ( montevideo ) is running as expected without a rebuild with gdal 3.4.2
>
> -- kjh
>
>
> On Tue, Apr 5, 2022 at 10:53 AM Konrad J Hambrick <kjhambrick at gmail.com>
> wrote:
>
>> Thanks Greg !
>>
>> Building gdal 3.4.2 now :)
>>
>> -- kjh
>>
>> On Mon, Apr 4, 2022 at 6:47 PM Greg' Ar Tourter <artourter at gmail.com>
>> wrote:
>>
>>> Hi Luis,
>>>
>>> I submitted a fix a few days ago for this. in the meantime use the
>>> source url off the slackbuild website:
>>> https://github.com/OSGeo/gdal/releases/download/v3.4.2/gdal-3.4.2.tar.gz
>>> or look at the change in git:
>>>
>>> https://git.slackbuilds.org/slackbuilds/commit/?h=willysr&id=bf9481b91e81851503e8ae54d41022eb8bbbd666
>>>
>>> Then you do not need to change anything to the slackbuild script.
>>>
>>> Hope this helps
>>>
>>> Cheers
>>>
>>> Greg
>>>
>>> On Tue, 5 Apr 2022 at 00:20, Luiz Carlos Ramos <lramos.prof at yahoo.com.br>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> these days I tried to build some packages which changed the SlackBuild
>>>> script, among them, gdal.
>>>>
>>>> In the first run, it failed.
>>>>
>>>> Searching a little bit, it seemed that the tarball has a slightly
>>>> different layout. In fact, everything that was supposed to be in the
>>>> root level is actually in the "./gdal" subdirectory.
>>>>
>>>> Also, the "configure" script was not there. It was rebuilt running
>>>> "autoreconf -fi" in the right time.
>>>>
>>>> I managed to tweak the slackbuild script and could ultimately build the
>>>> package. A patch is provided below.
>>>>
>>>> Anyway, it's wise to check whether these findings happen in other
>>>> environments before taking any measure. One other possible cause would
>>>> be the tarball URL be incorrect.
>>>>
>>>> Many thanks,
>>>>
>>>> Luiz Ramos
>>>> lramos dot prof at yahoo dot com dot br
>>>> S?o Paulo - Brazil
>>>>
>>>>
>>>> ===
>>>> From 031fd83c1fb76a855bc423c4b113829f5595fd4b Mon Sep 17 00:00:00 2001
>>>> From: Luiz Ramos <lramos.prof at yahoo.com.br>
>>>> Date: Sun, 3 Apr 2022 19:46:55 -0300
>>>> Subject: [PATCH] gis/gdal: fixed build
>>>>
>>>> Appearently the tarball downloaded changed its layout and so the build
>>>> directory
>>>> has to be changed. Also, there is no "configure" file: it has to be
>>>> build using
>>>> "autoreconf -fi".
>>>> ---
>>>>  gis/gdal/gdal.SlackBuild | 9 ++++++++-
>>>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/gis/gdal/gdal.SlackBuild b/gis/gdal/gdal.SlackBuild
>>>> index 4f83453333..056874624f 100644
>>>> --- a/gis/gdal/gdal.SlackBuild
>>>> +++ b/gis/gdal/gdal.SlackBuild
>>>> @@ -119,6 +119,9 @@ else
>>>>     WITHLIST+=" --with-jpeg=yes"
>>>>  fi
>>>>
>>>> +cd gdal
>>>> +autoreconf -fi
>>>> +
>>>>  # The CPPFLAGS are for the newer mariadb (thanks pprkut!)
>>>>  CPPFLAGS="-I/usr/include/mysql/server" \
>>>>  CFLAGS="$SLKCFLAGS" \
>>>> @@ -154,13 +157,17 @@ CXXFLAGS="$SLKCFLAGS" \
>>>>  make
>>>>  make install DESTDIR=$PKG
>>>>
>>>> +cd ..
>>>> +
>>>>  find $PKG | xargs file | grep -e "executable" -e "shared object" |
>>>> grep ELF \
>>>>    | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
>>>>
>>>>  mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
>>>> +cd gdal && \
>>>>  cp -a \
>>>>    COMMITTERS HOWTO-RELEASE LICENSE.TXT MIGRATION_GUIDE.TXT NEWS.md
>>>> PROVENANCE.TXT VERSION \
>>>> -  $PKG/usr/doc/$PRGNAM-$VERSION
>>>> +  $PKG/usr/doc/$PRGNAM-$VERSION && \
>>>> +cd ..
>>>>  cat $CWD/$PRGNAM.SlackBuild >
>>>> $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
>>>>
>>>>  rm -f $PKG/usr/lib*/*.la
>>>> --
>>>> 2.35.1
>>>>
>>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220406/05e1d5ad/attachment-0001.htm>

From luc.vanrompaey at gmail.com  Wed Apr  6 11:10:26 2022
From: luc.vanrompaey at gmail.com (Luc Van Rompaey)
Date: Wed, 6 Apr 2022 13:10:26 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
Message-ID: <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>

Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
slackbuilds-users at slackbuilds.org>:

> > >> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
> > >> got 0xc7a06d31)
> > >
> > > This looks like you're inadvertently using the wrong set of source
> > > files. Each new openjdk version has a new set of source files, many of
> > > which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
> > > your build system can easily pick up the wrong source file.
> > >
> > > chris
> >
> > Good morning all
> >
> > I do not doubt the comment above, but in this case, how could it be
> unless
> > the slackbuild source links are out of step/compromised/whatever.
> >
> > As I mentioned, it is a clean physical machine freshly installed and
> then
> > updated - no other [java related or other slackbuild addons etc]
> downloads
> > prior - and simply the source files linked in the slackbuild info.  Each
> > slackbuild individually run using 'su -' (rather than using sbotools or
> > similar) as required.  I don't even get to try openjdk8 (or download
> > anything for it) as apache-ant, gcc5 and openjdk7 are listed as required
> > first.  It is openjdk7 that is failing in that chain as such.
> >
> > That all said, I will go back and check the sources, though I think that
> > has been done by Matteo.
> >
> > Regards
> > Habs
>
> My comment will not add much to the problem, but my several tries are all
> failing at the same place (ie: invalid entry CRC).
> Be it on my master very unclean multilib box, a chroot, multilib or not,
> updated and clean, or some other cleaner boxes, VMs, not multilib, I can't
> make it build, and it always fails on the same place...
>
> But unlike others here, I don't pretend doing it on perfectly clean
> installations (though always without any other java installed).
> Although I am really sure my source packages are the right ones, MD5SUM
> checked and all.
>
> --
> Arnaud <arnaud.garcia-fernandez at laposte.net>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
> Let me first tell you all that I have been out of the Slackware loop for a
while and that I'm only just getting ready to install Slackware 15.0 on my
new computer.
Thus, for now, I cannot do any tests involving Slackware myself.

Anyway, I remember looking into the different Apache Ant releases just
before life interfered, and I was about to try and figure out how the Ant
releases and the (Open)JDK version did and did not go together. I hadn't
gotten far enough to draw any final conclusions, though, and I hadn't taken
any meaningful notes yet.

This ongoing discussion reminded me that I had sent in an update to the
apache-ant slackbuild when I took it over. According to the SlackBuilds
history, it had been at Ant version 1.9.9 until then, and I updated it to
1.9.14. Now, if I remember correctly, I had successfully compiled OpenJDK 7
(and subsequently 8) before I took over the apache-ant slackbuild, and I
don't believe that I have ever recompiled them since then.

Anyway, to cut a long story short, I'm now wondering if, perhaps, the
problem may have anything to do with the Apache Ant version. In other
words, the build fails with Ant 1.9.14, but it may still complete
successfully with Ant 1.9.9. May be worth a try. Then, if that works, I may
attempt a build with the latest Ant 1.9.x revision (currently 1.9.16) and
see what gives. In any case, there's no point in trying the build with Ant
1.10.x, since that cannot make sense of any Java run-time environment older
than, I think, Java version 8 (and, consequently, the Java environment
provided by gcc5).

If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 while
I'm getting ready for Slackware 15.0, the Ant versions can be downloaded
from https://archive.apache.org/dist/ant/binaries/

Let's hope we can work this issue out.

Regards,
Luc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220406/9675b700/attachment.htm>

From gen-bch at useyouresp.org.uk  Wed Apr  6 12:49:19 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Wed, 6 Apr 2022 13:49:19 +0100 (BST)
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
Message-ID: <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>

On Wed, 6 Apr 2022, Luc Van Rompaey wrote:

> Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
> slackbuilds-users at slackbuilds.org>:
>
>>>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
>>>>> got 0xc7a06d31)
>>>>
>>>> This looks like you're inadvertently using the wrong set of source
>>>> files. Each new openjdk version has a new set of source files, many of
>>>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
>>>> your build system can easily pick up the wrong source file.
>>>>
>>>> chris
>>>
>>> Good morning all
>>>
>>> I do not doubt the comment above, but in this case, how could it be
>> unless
>>> the slackbuild source links are out of step/compromised/whatever.
>>>
>>> As I mentioned, it is a clean physical machine freshly installed and
>> then
>>> updated - no other [java related or other slackbuild addons etc]
>> downloads
>>> prior - and simply the source files linked in the slackbuild info.  Each
>>> slackbuild individually run using 'su -' (rather than using sbotools or
>>> similar) as required.  I don't even get to try openjdk8 (or download
>>> anything for it) as apache-ant, gcc5 and openjdk7 are listed as required
>>> first.  It is openjdk7 that is failing in that chain as such.
>>>
>>> That all said, I will go back and check the sources, though I think that
>>> has been done by Matteo.
>>>
>>> Regards
>>> Habs
>>
>> My comment will not add much to the problem, but my several tries are all
>> failing at the same place (ie: invalid entry CRC).
>> Be it on my master very unclean multilib box, a chroot, multilib or not,
>> updated and clean, or some other cleaner boxes, VMs, not multilib, I can't
>> make it build, and it always fails on the same place...
>>
>> But unlike others here, I don't pretend doing it on perfectly clean
>> installations (though always without any other java installed).
>> Although I am really sure my source packages are the right ones, MD5SUM
>> checked and all.
>>
>> --
>> Arnaud <arnaud.garcia-fernandez at laposte.net>
>>
>> Let me first tell you all that I have been out of the Slackware loop for a
> while and that I'm only just getting ready to install Slackware 15.0 on my
> new computer.
> Thus, for now, I cannot do any tests involving Slackware myself.
>
> Anyway, I remember looking into the different Apache Ant releases just
> before life interfered, and I was about to try and figure out how the Ant
> releases and the (Open)JDK version did and did not go together. I hadn't
> gotten far enough to draw any final conclusions, though, and I hadn't taken
> any meaningful notes yet.
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>
> This ongoing discussion reminded me that I had sent in an update to the
> apache-ant slackbuild when I took it over. According to the SlackBuilds
> history, it had been at Ant version 1.9.9 until then, and I updated it to
> 1.9.14. Now, if I remember correctly, I had successfully compiled OpenJDK 7
> (and subsequently 8) before I took over the apache-ant slackbuild, and I
> don't believe that I have ever recompiled them since then.
>
> Anyway, to cut a long story short, I'm now wondering if, perhaps, the
> problem may have anything to do with the Apache Ant version. In other
> words, the build fails with Ant 1.9.14, but it may still complete
> successfully with Ant 1.9.9. May be worth a try. Then, if that works, I may
> attempt a build with the latest Ant 1.9.x revision (currently 1.9.16) and
> see what gives. In any case, there's no point in trying the build with Ant
> 1.10.x, since that cannot make sense of any Java run-time environment older
> than, I think, Java version 8 (and, consequently, the Java environment
> provided by gcc5).
>
> If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 while
> I'm getting ready for Slackware 15.0, the Ant versions can be downloaded
> from https://archive.apache.org/dist/ant/binaries/
>
> Let's hope we can work this issue out.
>
> Regards,
> Luc.
>
Good day all

I can confirm that using 1.9.9 does not resolve the issue from my attempt 
a short while ago.

Regards
Habs


--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html


From kjhambrick at gmail.com  Wed Apr  6 13:08:57 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Wed, 6 Apr 2022 08:08:57 -0500
Subject: [Slackbuilds-users] gdal tarball possibly changed layout
In-Reply-To: <CAK09-vnVkY1qhq_wO31gyA5osc5u0ozu1e9zPHnAobvxZxYE3g@mail.gmail.com>
References: <Ykt9sYZ8Drz1nvmW.ref@giustizia.lan>
 <Ykt9sYZ8Drz1nvmW@giustizia.lan>
 <CAK09-vkfy-XEbeyWAHrh=3hnUtqEDRSV2hJH3feH39wukBbQeA@mail.gmail.com>
 <CANBHt+MO5LwUV4_X6TV1WQ7CPf=PFw0Ro0E+VkdZ+9cH_2PjVw@mail.gmail.com>
 <CANBHt+PbdjCpCqzab5zZyWV0B4dMqaXUBXc0Gi=ngGrB_C9fOA@mail.gmail.com>
 <CAK09-vnVkY1qhq_wO31gyA5osc5u0ozu1e9zPHnAobvxZxYE3g@mail.gmail.com>
Message-ID: <CANBHt+PKfnCoontodxf20KgDBveT0CiZ1XrRoaqqF2fAd8xDMA@mail.gmail.com>

Let me think about Greg.

OTB works for me now when I need it.

And I would hate to take on an SB then abandon it immediately ...

-- kjh

-- kjh

On Wed, Apr 6, 2022 at 4:49 AM Greg' Ar Tourter <artourter at gmail.com> wrote:

> Konrad,
>
> note that if you are using OTB, the slackbuild is currently not maintained
> as Benjamin unfortunately has stopped maintaining his builds. So if you
> feel like taking it up, I suspect it is free.
>
> Greg
>
> On Tue, 5 Apr 2022 at 17:23, Konrad J Hambrick <kjhambrick at gmail.com>
> wrote:
>
>> Thanks Greg.
>>
>> Worked Great !
>>
>> OTB ( montevideo ) is running as expected without a rebuild with gdal
>> 3.4.2
>>
>> -- kjh
>>
>>
>> On Tue, Apr 5, 2022 at 10:53 AM Konrad J Hambrick <kjhambrick at gmail.com>
>> wrote:
>>
>>> Thanks Greg !
>>>
>>> Building gdal 3.4.2 now :)
>>>
>>> -- kjh
>>>
>>> On Mon, Apr 4, 2022 at 6:47 PM Greg' Ar Tourter <artourter at gmail.com>
>>> wrote:
>>>
>>>> Hi Luis,
>>>>
>>>> I submitted a fix a few days ago for this. in the meantime use the
>>>> source url off the slackbuild website:
>>>> https://github.com/OSGeo/gdal/releases/download/v3.4.2/gdal-3.4.2.tar.gz
>>>> or look at the change in git:
>>>>
>>>> https://git.slackbuilds.org/slackbuilds/commit/?h=willysr&id=bf9481b91e81851503e8ae54d41022eb8bbbd666
>>>>
>>>> Then you do not need to change anything to the slackbuild script.
>>>>
>>>> Hope this helps
>>>>
>>>> Cheers
>>>>
>>>> Greg
>>>>
>>>> On Tue, 5 Apr 2022 at 00:20, Luiz Carlos Ramos <
>>>> lramos.prof at yahoo.com.br> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> these days I tried to build some packages which changed the SlackBuild
>>>>> script, among them, gdal.
>>>>>
>>>>> In the first run, it failed.
>>>>>
>>>>> Searching a little bit, it seemed that the tarball has a slightly
>>>>> different layout. In fact, everything that was supposed to be in the
>>>>> root level is actually in the "./gdal" subdirectory.
>>>>>
>>>>> Also, the "configure" script was not there. It was rebuilt running
>>>>> "autoreconf -fi" in the right time.
>>>>>
>>>>> I managed to tweak the slackbuild script and could ultimately build the
>>>>> package. A patch is provided below.
>>>>>
>>>>> Anyway, it's wise to check whether these findings happen in other
>>>>> environments before taking any measure. One other possible cause would
>>>>> be the tarball URL be incorrect.
>>>>>
>>>>> Many thanks,
>>>>>
>>>>> Luiz Ramos
>>>>> lramos dot prof at yahoo dot com dot br
>>>>> S?o Paulo - Brazil
>>>>>
>>>>>
>>>>> ===
>>>>> From 031fd83c1fb76a855bc423c4b113829f5595fd4b Mon Sep 17 00:00:00 2001
>>>>> From: Luiz Ramos <lramos.prof at yahoo.com.br>
>>>>> Date: Sun, 3 Apr 2022 19:46:55 -0300
>>>>> Subject: [PATCH] gis/gdal: fixed build
>>>>>
>>>>> Appearently the tarball downloaded changed its layout and so the build
>>>>> directory
>>>>> has to be changed. Also, there is no "configure" file: it has to be
>>>>> build using
>>>>> "autoreconf -fi".
>>>>> ---
>>>>>  gis/gdal/gdal.SlackBuild | 9 ++++++++-
>>>>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/gis/gdal/gdal.SlackBuild b/gis/gdal/gdal.SlackBuild
>>>>> index 4f83453333..056874624f 100644
>>>>> --- a/gis/gdal/gdal.SlackBuild
>>>>> +++ b/gis/gdal/gdal.SlackBuild
>>>>> @@ -119,6 +119,9 @@ else
>>>>>     WITHLIST+=" --with-jpeg=yes"
>>>>>  fi
>>>>>
>>>>> +cd gdal
>>>>> +autoreconf -fi
>>>>> +
>>>>>  # The CPPFLAGS are for the newer mariadb (thanks pprkut!)
>>>>>  CPPFLAGS="-I/usr/include/mysql/server" \
>>>>>  CFLAGS="$SLKCFLAGS" \
>>>>> @@ -154,13 +157,17 @@ CXXFLAGS="$SLKCFLAGS" \
>>>>>  make
>>>>>  make install DESTDIR=$PKG
>>>>>
>>>>> +cd ..
>>>>> +
>>>>>  find $PKG | xargs file | grep -e "executable" -e "shared object" |
>>>>> grep ELF \
>>>>>    | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
>>>>>
>>>>>  mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
>>>>> +cd gdal && \
>>>>>  cp -a \
>>>>>    COMMITTERS HOWTO-RELEASE LICENSE.TXT MIGRATION_GUIDE.TXT NEWS.md
>>>>> PROVENANCE.TXT VERSION \
>>>>> -  $PKG/usr/doc/$PRGNAM-$VERSION
>>>>> +  $PKG/usr/doc/$PRGNAM-$VERSION && \
>>>>> +cd ..
>>>>>  cat $CWD/$PRGNAM.SlackBuild >
>>>>> $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
>>>>>
>>>>>  rm -f $PKG/usr/lib*/*.la
>>>>> --
>>>>> 2.35.1
>>>>>
>>>>> _______________________________________________
>>>> SlackBuilds-users mailing list
>>>> SlackBuilds-users at 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 at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220406/ee5b351a/attachment-0001.htm>

From chris.willing at linux.com  Wed Apr  6 13:14:43 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Wed, 6 Apr 2022 23:14:43 +1000
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
Message-ID: <3880232a-a219-c3cb-27ab-50f41f56806d@linux.com>

On 6/4/22 17:42, Habs wrote:
> On Wed, 6 Apr 2022, Christoph Willing wrote:
> 
>> On 6/4/22 06:00, Habs wrote:
>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
>>> got 0xc7a06d31)
>>
>> This looks like you're inadvertently using the wrong set of source
>> files. Each new openjdk version has a new set of source files, many of
>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
>> your build system can easily pick up the wrong source file.
>>
>> chris
> 
> Good morning all
> 
> I do not doubt the comment above, but in this case, how could it be
> unless the slackbuild source links are out of step/compromised/whatever.
> 
> As I mentioned, it is a clean physical machine freshly installed and
> then updated - no other [java related or other slackbuild addons etc]
> downloads prior - and simply the source files linked in the slackbuild
> info.? Each slackbuild individually run using 'su -' (rather than using
> sbotools or similar) as required.? I don't even get to try openjdk8 (or
> download anything for it) as apache-ant, gcc5 and openjdk7 are listed as
> required first.? It is openjdk7 that is failing in that chain as such.
> 
> That all said, I will go back and check the sources, though I think that
> has been done by Matteo.
> 

OK, good to know the sources are correct.

I thought I'd have a go at building it (I haven't used it for quite a
while now) and the first thing I noticed was that all the source
tarballs for the last version I'd built some time ago were still there.
Clearing out old source files was a task I always had to remember to do
back in the days when I used it a lot.

Anyway, the first build I did just now was in a VM and it built with no
problems. After that success I've started building it on my daily
machine. It has already progressed way beyond the point where the
infamous "invalid entry CRC (expected xxxxxx but got yyyyyy)" usually
appears. As far as I'm concerned it's done.

I'm sorry that news is no solution for you but at least we can say that
there's no difference in outcome whether building in a VM or on a
physical machine.


chris

From luc.vanrompaey at gmail.com  Wed Apr  6 14:54:32 2022
From: luc.vanrompaey at gmail.com (Luc Van Rompaey)
Date: Wed, 6 Apr 2022 16:54:32 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
Message-ID: <CACLujjwLQ93Dz4ALED9xg5g96iRKmq2qyFK1GUaxxEq0BywaVQ@mail.gmail.com>

Op wo 6 apr. 2022 14:49 schreef Habs <gen-bch at useyouresp.org.uk>:

> On Wed, 6 Apr 2022, Luc Van Rompaey wrote:
>
> > Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
> > slackbuilds-users at slackbuilds.org>:
> >
> >>>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7
> but
> >>>>> got 0xc7a06d31)
> >>>>
> >>>> This looks like you're inadvertently using the wrong set of source
> >>>> files. Each new openjdk version has a new set of source files, many of
> >>>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
> >>>> your build system can easily pick up the wrong source file.
> >>>>
> >>>> chris
> >>>
> >>> Good morning all
> >>>
> >>> I do not doubt the comment above, but in this case, how could it be
> >> unless
> >>> the slackbuild source links are out of step/compromised/whatever.
> >>>
> >>> As I mentioned, it is a clean physical machine freshly installed and
> >> then
> >>> updated - no other [java related or other slackbuild addons etc]
> >> downloads
> >>> prior - and simply the source files linked in the slackbuild info.
> Each
> >>> slackbuild individually run using 'su -' (rather than using sbotools or
> >>> similar) as required.  I don't even get to try openjdk8 (or download
> >>> anything for it) as apache-ant, gcc5 and openjdk7 are listed as
> required
> >>> first.  It is openjdk7 that is failing in that chain as such.
> >>>
> >>> That all said, I will go back and check the sources, though I think
> that
> >>> has been done by Matteo.
> >>>
> >>> Regards
> >>> Habs
> >>
> >> My comment will not add much to the problem, but my several tries are
> all
> >> failing at the same place (ie: invalid entry CRC).
> >> Be it on my master very unclean multilib box, a chroot, multilib or not,
> >> updated and clean, or some other cleaner boxes, VMs, not multilib, I
> can't
> >> make it build, and it always fails on the same place...
> >>
> >> But unlike others here, I don't pretend doing it on perfectly clean
> >> installations (though always without any other java installed).
> >> Although I am really sure my source packages are the right ones, MD5SUM
> >> checked and all.
> >>
> >> --
> >> Arnaud <arnaud.garcia-fernandez at laposte.net>
> >>
> >> Let me first tell you all that I have been out of the Slackware loop
> for a
> > while and that I'm only just getting ready to install Slackware 15.0 on
> my
> > new computer.
> > Thus, for now, I cannot do any tests involving Slackware myself.
> >
> > Anyway, I remember looking into the different Apache Ant releases just
> > before life interfered, and I was about to try and figure out how the Ant
> > releases and the (Open)JDK version did and did not go together. I hadn't
> > gotten far enough to draw any final conclusions, though, and I hadn't
> taken
> > any meaningful notes yet.
> >> _______________________________________________
> >> SlackBuilds-users mailing list
> >> SlackBuilds-users at slackbuilds.org
> >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >> FAQ - https://slackbuilds.org/faq/
> >
> > This ongoing discussion reminded me that I had sent in an update to the
> > apache-ant slackbuild when I took it over. According to the SlackBuilds
> > history, it had been at Ant version 1.9.9 until then, and I updated it to
> > 1.9.14. Now, if I remember correctly, I had successfully compiled
> OpenJDK 7
> > (and subsequently 8) before I took over the apache-ant slackbuild, and I
> > don't believe that I have ever recompiled them since then.
> >
> > Anyway, to cut a long story short, I'm now wondering if, perhaps, the
> > problem may have anything to do with the Apache Ant version. In other
> > words, the build fails with Ant 1.9.14, but it may still complete
> > successfully with Ant 1.9.9. May be worth a try. Then, if that works, I
> may
> > attempt a build with the latest Ant 1.9.x revision (currently 1.9.16) and
> > see what gives. In any case, there's no point in trying the build with
> Ant
> > 1.10.x, since that cannot make sense of any Java run-time environment
> older
> > than, I think, Java version 8 (and, consequently, the Java environment
> > provided by gcc5).
> >
> > If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 while
> > I'm getting ready for Slackware 15.0, the Ant versions can be downloaded
> > from https://archive.apache.org/dist/ant/binaries/
> >
> > Let's hope we can work this issue out.
> >
> > Regards,
> > Luc.
> >
> Good day all
>
> I can confirm that using 1.9.9 does not resolve the issue from my attempt
> a short while ago.
>
> Regards
> Habs
>
>
> --- Sent using Alpine/Pine, probably the best MUA ---
>
> My Tox Messaging Id:
>
> 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
> Get a client here: https://tox.chat/clients.html
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/


The only other issue that I can think of, would be jobs running in parallel
stepping on one another's toes.

Once I get going with Slackware 15.0, I'll try the build myself, and I'll
report my findings.

Regards,
Luc.

>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220406/ee68a320/attachment.htm>

From falsetti at clansco.org  Wed Apr  6 14:36:19 2022
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Wed, 6 Apr 2022 16:36:19 +0200
Subject: [Slackbuilds-users] Viking slackbuild
In-Reply-To: <cd5c1e1c-1c83-3e12-db98-a562b9a33db9@sagredo.eu>
References: <cd5c1e1c-1c83-3e12-db98-a562b9a33db9@sagredo.eu>
Message-ID: <20220406163619.172a73b145f0a9f7888edd99@clansco.org>

le Tue, 5 Apr 2022 21:08:29 +0200
Roberto Puzzanghera via SlackBuilds-users <slackbuilds-users at slackbuilds.org> a ?crit :

> I contacted the maintainer of vikings, because the current version was 
> published in 2015, and got no response.
> 
> I also browsed both the pending and ready queue and didn't find any 
> update. It seems like it is not maintained anymore.
> 
> Can I take it over? I would be my first package
> 
> Roberto
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
Hi Roberto,

I use 1.10 version, modifying the Slackbuild  :

  I only had to comment the patches lines :
    #patch -p1 < $CWD/remove-mapquest.patch
    #patch -p0 < $CWD/viking-1.6.2-gpsd-3.18-fix.patch

  and get 15.0 > Libraries > liboauth (1.0.3) 
  that is required.

I'm interested in using mapquest, but I haven't tested.

-- 
Fr?d?ric Falsetti




From mab974 at misouk.com  Wed Apr  6 17:58:40 2022
From: mab974 at misouk.com (Mab974)
Date: Wed, 6 Apr 2022 21:58:40 +0400
Subject: [Slackbuilds-users] perl-PDF-Builder build
Message-ID: <20220406215840.31d1b7fc56f9b1872ac55e14@misouk.com>

Hello everyone,

On a clean and updated Slackware 15, following perl-template,

I can't build current 'perl-PDF-Builder' with sbopkg but the slackbuild
works fine manually.

The problem is the different assignment of INSTALLDIRS in makefile.
('site' instead of 'vendor') 

Part of log is below ...

I can?t figure out what the problem is and how to fix it.
Any help will be welcome

Regards,

-*- 
Mab974 <mab974 at misouk.com>


PDF-Builder-3.021/lib/PDF/Builder/Resource/Glyphs.pm
PDF-Builder-3.021/lib/PDF/Builder/Resource/Pattern.pm
PDF-Builder-3.021/lib/PDF/Builder/Outline.pm
PDF-Builder-3.021/lib/PDF/Builder/UniWrap.pm
PDF-Builder-3.021/lib/PDF/Builder/Content.pm
PDF-Builder-3.021/.perl-version
PDF-Builder-3.021/META.yml
Attempt to install or update optional prereq libraries?
 a (default) = install all choices listed below
 n = do NOT install any of them
   or enter 1 to 3 of the following choices:
 t = install/update Graphics::TIFF (TIFF image support support)
 p = install/update Image::PNG::Libpng (PNG image support support)
 h = install/update HarfBuzz::Shaper (complex script support support) [A|
n|{t|p|h}] Can't open PREFIX=/usr: No such file or directory at Makefile.PL line 63. Can't open INSTALLDIRS=vendor: No such file or directory at Makefile.PL line 63.
Can't open INSTALLVENDORMAN1DIR=/usr/man/man1: No such file or directory
at Makefile.PL line 63. Can't open INSTALLVENDORMAN3DIR=/usr/man/man3: No
such file or directory at Makefile.PL line 63. Use of uninitialized value
$choice in substitution (s///) at Makefile.PL line 64. Use of
uninitialized value in numeric gt (>) at Makefile.PL line 65.
===========================================================================
The installation process will attempt to install or update several
OPTIONAL prerequisite packages. If one or more should fail to install,
Don't Panic
-- you will still be able to run PDF::Builder, but may not be able to use 
some advanced features. See the README file for more information.
===========================================================================
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for PDF::Builder

....................
...................

Installing /tmp/SBo/package-perl-PDF-Builder/usr/local/share/man/man3/PDF::Builder::Resource::Font::Postscript.
3
Installing /tmp/SBo/package-perl-PDF-Builder/usr/local/share/man/man3/PDF::Builder::Resource::Pattern.
3
Installing /tmp/SBo/package-perl-PDF-Builder/usr/local/share/man/man3/PDF::Builder::Resource::XObject::Form::Hybrid.
3 Appending installation info
to /tmp/SBo/package-perl-PDF-Builder/usr/lib64/perl5/perllocal.pod find:
?/tmp/SBo/package-perl-PDF-Builder/usr/man?: No such file or directory

From roberto.puzzanghera at sagredo.eu  Wed Apr  6 19:28:55 2022
From: roberto.puzzanghera at sagredo.eu (Roberto Puzzanghera)
Date: Wed, 6 Apr 2022 21:28:55 +0200
Subject: [Slackbuilds-users] Viking slackbuild
In-Reply-To: <20220406163619.172a73b145f0a9f7888edd99@clansco.org>
References: <cd5c1e1c-1c83-3e12-db98-a562b9a33db9@sagredo.eu>
 <20220406163619.172a73b145f0a9f7888edd99@clansco.org>
Message-ID: <7ab6f8d5-95c9-86ad-fdad-62be8a5ff651@sagredo.eu>

Hi Fr?d?ric,

> Hi Roberto,
> 
> I use 1.10 version, modifying the Slackbuild  :
> 
>    I only had to comment the patches lines :
>      #patch -p1 < $CWD/remove-mapquest.patch
>      #patch -p0 < $CWD/viking-1.6.2-gpsd-3.18-fix.patch
> 
>    and get 15.0 > Libraries > liboauth (1.0.3)
>    that is required.
> 
> I'm interested in using mapquest, but I haven't tested.

I'm compiling in the same way.
I see that mapquest support has been discontinued (I've never tried 
mapquest), while the gpsd patch has been added

Roberto

From bouboulov at mail.ru  Wed Apr  6 20:32:15 2022
From: bouboulov at mail.ru (Poligraf Poligrafovich Bouboulov)
Date: Wed, 6 Apr 2022 22:32:15 +0200
Subject: [Slackbuilds-users] Xerces-c source and hdf5
Message-ID: <3c396513-4544-a3f0-848a-59dabb54f015@mail.ru>

Hello, just to say that the address of the xerces-c source has changed : 
the tar.gz is now at :

https://dlcdn.apache.org//xerces/c/3/sources/xerces-c-3.2.3.tar.gz

Also I had some problems with the hdf5 package : i had to rewrite the 
slackbuild manually but i'm not so skilled at the moment. The archive 
seems corrupted but managed to compile it wit the .tar editing the 
.Slackbuild file.

Have a nice day, Bouboulov :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bouboulov.vcf
Type: text/vcard
Size: 305 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220406/6f886f53/attachment.vcard>

From artourter at gmail.com  Thu Apr  7 01:00:30 2022
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Thu, 7 Apr 2022 02:00:30 +0100
Subject: [Slackbuilds-users] Xerces-c source and hdf5
In-Reply-To: <3c396513-4544-a3f0-848a-59dabb54f015@mail.ru>
References: <3c396513-4544-a3f0-848a-59dabb54f015@mail.ru>
Message-ID: <CAK09-vnfK2Geqtke+4xWi6z_rWN9z4V06kE+S=LfYUdMghdVmA@mail.gmail.com>

I cannot see any issue with either the xerces-c source nor the hdf5 source.
They both download and build fine using the original source and scripts.

Can you give more details about the issues you are getting?

Cheers

Greg


On Thu, 7 Apr 2022 at 01:44, Poligraf Poligrafovich Bouboulov via
SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:

> Hello, just to say that the address of the xerces-c source has changed :
> the tar.gz is now at :
>
> https://dlcdn.apache.org//xerces/c/3/sources/xerces-c-3.2.3.tar.gz
>
> Also I had some problems with the hdf5 package : i had to rewrite the
> slackbuild manually but i'm not so skilled at the moment. The archive
> seems corrupted but managed to compile it wit the .tar editing the
> .Slackbuild file.
>
> Have a nice day, Bouboulov :)
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220407/e5a6430a/attachment.htm>

From lenardrspencer at gmail.com  Thu Apr  7 02:24:19 2022
From: lenardrspencer at gmail.com (Lenard Spencer)
Date: Wed, 6 Apr 2022 22:24:19 -0400
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CACLujjwLQ93Dz4ALED9xg5g96iRKmq2qyFK1GUaxxEq0BywaVQ@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwLQ93Dz4ALED9xg5g96iRKmq2qyFK1GUaxxEq0BywaVQ@mail.gmail.com>
Message-ID: <CANSA5-s-Kre=OeVYeXWmVZfQU4v2gY2Y=md27yZ96JoYEn6RWQ@mail.gmail.com>

Since openjdk6 and 7 can no longer be built at this time, I would have to
say drop them for now.  openjdk8 can be built if you have zulu-openjdk7
installed and adjust BOOT_JAVA to point to /usr/lib(64)/zulu-openjdk7 in
the script.


On Wed, Apr 6, 2022, 10:54 Luc Van Rompaey <luc.vanrompaey at gmail.com> wrote:

>
>
> Op wo 6 apr. 2022 14:49 schreef Habs <gen-bch at useyouresp.org.uk>:
>
>> On Wed, 6 Apr 2022, Luc Van Rompaey wrote:
>>
>> > Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
>> > slackbuilds-users at slackbuilds.org>:
>> >
>> >>>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7
>> but
>> >>>>> got 0xc7a06d31)
>> >>>>
>> >>>> This looks like you're inadvertently using the wrong set of source
>> >>>> files. Each new openjdk version has a new set of source files, many
>> of
>> >>>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
>> >>>> your build system can easily pick up the wrong source file.
>> >>>>
>> >>>> chris
>> >>>
>> >>> Good morning all
>> >>>
>> >>> I do not doubt the comment above, but in this case, how could it be
>> >> unless
>> >>> the slackbuild source links are out of step/compromised/whatever.
>> >>>
>> >>> As I mentioned, it is a clean physical machine freshly installed and
>> >> then
>> >>> updated - no other [java related or other slackbuild addons etc]
>> >> downloads
>> >>> prior - and simply the source files linked in the slackbuild info.
>> Each
>> >>> slackbuild individually run using 'su -' (rather than using sbotools
>> or
>> >>> similar) as required.  I don't even get to try openjdk8 (or download
>> >>> anything for it) as apache-ant, gcc5 and openjdk7 are listed as
>> required
>> >>> first.  It is openjdk7 that is failing in that chain as such.
>> >>>
>> >>> That all said, I will go back and check the sources, though I think
>> that
>> >>> has been done by Matteo.
>> >>>
>> >>> Regards
>> >>> Habs
>> >>
>> >> My comment will not add much to the problem, but my several tries are
>> all
>> >> failing at the same place (ie: invalid entry CRC).
>> >> Be it on my master very unclean multilib box, a chroot, multilib or
>> not,
>> >> updated and clean, or some other cleaner boxes, VMs, not multilib, I
>> can't
>> >> make it build, and it always fails on the same place...
>> >>
>> >> But unlike others here, I don't pretend doing it on perfectly clean
>> >> installations (though always without any other java installed).
>> >> Although I am really sure my source packages are the right ones, MD5SUM
>> >> checked and all.
>> >>
>> >> --
>> >> Arnaud <arnaud.garcia-fernandez at laposte.net>
>> >>
>> >> Let me first tell you all that I have been out of the Slackware loop
>> for a
>> > while and that I'm only just getting ready to install Slackware 15.0 on
>> my
>> > new computer.
>> > Thus, for now, I cannot do any tests involving Slackware myself.
>> >
>> > Anyway, I remember looking into the different Apache Ant releases just
>> > before life interfered, and I was about to try and figure out how the
>> Ant
>> > releases and the (Open)JDK version did and did not go together. I hadn't
>> > gotten far enough to draw any final conclusions, though, and I hadn't
>> taken
>> > any meaningful notes yet.
>> >> _______________________________________________
>> >> SlackBuilds-users mailing list
>> >> SlackBuilds-users at slackbuilds.org
>> >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> >> FAQ - https://slackbuilds.org/faq/
>> >
>> > This ongoing discussion reminded me that I had sent in an update to the
>> > apache-ant slackbuild when I took it over. According to the SlackBuilds
>> > history, it had been at Ant version 1.9.9 until then, and I updated it
>> to
>> > 1.9.14. Now, if I remember correctly, I had successfully compiled
>> OpenJDK 7
>> > (and subsequently 8) before I took over the apache-ant slackbuild, and I
>> > don't believe that I have ever recompiled them since then.
>> >
>> > Anyway, to cut a long story short, I'm now wondering if, perhaps, the
>> > problem may have anything to do with the Apache Ant version. In other
>> > words, the build fails with Ant 1.9.14, but it may still complete
>> > successfully with Ant 1.9.9. May be worth a try. Then, if that works, I
>> may
>> > attempt a build with the latest Ant 1.9.x revision (currently 1.9.16)
>> and
>> > see what gives. In any case, there's no point in trying the build with
>> Ant
>> > 1.10.x, since that cannot make sense of any Java run-time environment
>> older
>> > than, I think, Java version 8 (and, consequently, the Java environment
>> > provided by gcc5).
>> >
>> > If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 while
>> > I'm getting ready for Slackware 15.0, the Ant versions can be downloaded
>> > from https://archive.apache.org/dist/ant/binaries/
>> >
>> > Let's hope we can work this issue out.
>> >
>> > Regards,
>> > Luc.
>> >
>> Good day all
>>
>> I can confirm that using 1.9.9 does not resolve the issue from my attempt
>> a short while ago.
>>
>> Regards
>> Habs
>>
>>
>> --- Sent using Alpine/Pine, probably the best MUA ---
>>
>> My Tox Messaging Id:
>>
>> 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
>> Get a client here: https://tox.chat/clients.html
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>
>
> The only other issue that I can think of, would be jobs running in
> parallel stepping on one another's toes.
>
> Once I get going with Slackware 15.0, I'll try the build myself, and I'll
> report my findings.
>
> Regards,
> Luc.
>
>>
>> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220406/4f68745c/attachment-0001.htm>

From matteo.bernardini at gmail.com  Thu Apr  7 04:50:28 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 7 Apr 2022 06:50:28 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CANSA5-s-Kre=OeVYeXWmVZfQU4v2gY2Y=md27yZ96JoYEn6RWQ@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwLQ93Dz4ALED9xg5g96iRKmq2qyFK1GUaxxEq0BywaVQ@mail.gmail.com>
 <CANSA5-s-Kre=OeVYeXWmVZfQU4v2gY2Y=md27yZ96JoYEn6RWQ@mail.gmail.com>
Message-ID: <CAPsDuS5EAQz4+TVTrwWkh5cbrCHxS9sx4j5uxPrJmukjO294nA@mail.gmail.com>

can you send a patch for it so I can test it?

Il giorno gio 7 apr 2022 alle ore 04:25 Lenard Spencer <
lenardrspencer at gmail.com> ha scritto:

> Since openjdk6 and 7 can no longer be built at this time, I would have to
> say drop them for now.  openjdk8 can be built if you have zulu-openjdk7
> installed and adjust BOOT_JAVA to point to /usr/lib(64)/zulu-openjdk7 in
> the script.
>
>
> On Wed, Apr 6, 2022, 10:54 Luc Van Rompaey <luc.vanrompaey at gmail.com>
> wrote:
>
>>
>>
>> Op wo 6 apr. 2022 14:49 schreef Habs <gen-bch at useyouresp.org.uk>:
>>
>>> On Wed, 6 Apr 2022, Luc Van Rompaey wrote:
>>>
>>> > Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
>>> > slackbuilds-users at slackbuilds.org>:
>>> >
>>> >>>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7
>>> but
>>> >>>>> got 0xc7a06d31)
>>> >>>>
>>> >>>> This looks like you're inadvertently using the wrong set of source
>>> >>>> files. Each new openjdk version has a new set of source files, many
>>> of
>>> >>>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...)
>>> so
>>> >>>> your build system can easily pick up the wrong source file.
>>> >>>>
>>> >>>> chris
>>> >>>
>>> >>> Good morning all
>>> >>>
>>> >>> I do not doubt the comment above, but in this case, how could it be
>>> >> unless
>>> >>> the slackbuild source links are out of step/compromised/whatever.
>>> >>>
>>> >>> As I mentioned, it is a clean physical machine freshly installed and
>>> >> then
>>> >>> updated - no other [java related or other slackbuild addons etc]
>>> >> downloads
>>> >>> prior - and simply the source files linked in the slackbuild info.
>>> Each
>>> >>> slackbuild individually run using 'su -' (rather than using sbotools
>>> or
>>> >>> similar) as required.  I don't even get to try openjdk8 (or download
>>> >>> anything for it) as apache-ant, gcc5 and openjdk7 are listed as
>>> required
>>> >>> first.  It is openjdk7 that is failing in that chain as such.
>>> >>>
>>> >>> That all said, I will go back and check the sources, though I think
>>> that
>>> >>> has been done by Matteo.
>>> >>>
>>> >>> Regards
>>> >>> Habs
>>> >>
>>> >> My comment will not add much to the problem, but my several tries are
>>> all
>>> >> failing at the same place (ie: invalid entry CRC).
>>> >> Be it on my master very unclean multilib box, a chroot, multilib or
>>> not,
>>> >> updated and clean, or some other cleaner boxes, VMs, not multilib, I
>>> can't
>>> >> make it build, and it always fails on the same place...
>>> >>
>>> >> But unlike others here, I don't pretend doing it on perfectly clean
>>> >> installations (though always without any other java installed).
>>> >> Although I am really sure my source packages are the right ones,
>>> MD5SUM
>>> >> checked and all.
>>> >>
>>> >> --
>>> >> Arnaud <arnaud.garcia-fernandez at laposte.net>
>>> >>
>>> >> Let me first tell you all that I have been out of the Slackware loop
>>> for a
>>> > while and that I'm only just getting ready to install Slackware 15.0
>>> on my
>>> > new computer.
>>> > Thus, for now, I cannot do any tests involving Slackware myself.
>>> >
>>> > Anyway, I remember looking into the different Apache Ant releases just
>>> > before life interfered, and I was about to try and figure out how the
>>> Ant
>>> > releases and the (Open)JDK version did and did not go together. I
>>> hadn't
>>> > gotten far enough to draw any final conclusions, though, and I hadn't
>>> taken
>>> > any meaningful notes yet.
>>> >> _______________________________________________
>>> >> SlackBuilds-users mailing list
>>> >> SlackBuilds-users at slackbuilds.org
>>> >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> >> FAQ - https://slackbuilds.org/faq/
>>> >
>>> > This ongoing discussion reminded me that I had sent in an update to the
>>> > apache-ant slackbuild when I took it over. According to the SlackBuilds
>>> > history, it had been at Ant version 1.9.9 until then, and I updated it
>>> to
>>> > 1.9.14. Now, if I remember correctly, I had successfully compiled
>>> OpenJDK 7
>>> > (and subsequently 8) before I took over the apache-ant slackbuild, and
>>> I
>>> > don't believe that I have ever recompiled them since then.
>>> >
>>> > Anyway, to cut a long story short, I'm now wondering if, perhaps, the
>>> > problem may have anything to do with the Apache Ant version. In other
>>> > words, the build fails with Ant 1.9.14, but it may still complete
>>> > successfully with Ant 1.9.9. May be worth a try. Then, if that works,
>>> I may
>>> > attempt a build with the latest Ant 1.9.x revision (currently 1.9.16)
>>> and
>>> > see what gives. In any case, there's no point in trying the build with
>>> Ant
>>> > 1.10.x, since that cannot make sense of any Java run-time environment
>>> older
>>> > than, I think, Java version 8 (and, consequently, the Java environment
>>> > provided by gcc5).
>>> >
>>> > If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9
>>> while
>>> > I'm getting ready for Slackware 15.0, the Ant versions can be
>>> downloaded
>>> > from https://archive.apache.org/dist/ant/binaries/
>>> >
>>> > Let's hope we can work this issue out.
>>> >
>>> > Regards,
>>> > Luc.
>>> >
>>> Good day all
>>>
>>> I can confirm that using 1.9.9 does not resolve the issue from my
>>> attempt
>>> a short while ago.
>>>
>>> Regards
>>> Habs
>>>
>>>
>>> --- Sent using Alpine/Pine, probably the best MUA ---
>>>
>>> My Tox Messaging Id:
>>>
>>> 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
>>> Get a client here: https://tox.chat/clients.html
>>>
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>
>>
>> The only other issue that I can think of, would be jobs running in
>> parallel stepping on one another's toes.
>>
>> Once I get going with Slackware 15.0, I'll try the build myself, and I'll
>> report my findings.
>>
>> Regards,
>> Luc.
>>
>>>
>>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220407/9b2410b5/attachment.htm>

From arnaud.garcia-fernandez at laposte.net  Thu Apr  7 08:41:18 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Thu, 7 Apr 2022 10:41:18 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CANSA5-s-Kre=OeVYeXWmVZfQU4v2gY2Y=md27yZ96JoYEn6RWQ@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwLQ93Dz4ALED9xg5g96iRKmq2qyFK1GUaxxEq0BywaVQ@mail.gmail.com>
 <CANSA5-s-Kre=OeVYeXWmVZfQU4v2gY2Y=md27yZ96JoYEn6RWQ@mail.gmail.com>
Message-ID: <20220407104118.d07f29427978f2f1c8054d67@laposte.net>

On Wed, 6 Apr 2022 22:24:19 -0400
Lenard Spencer <lenardrspencer at gmail.com> wrote:

> Since openjdk6 and 7 can no longer be built at this time, I would have to
> say drop them for now.  openjdk8 can be built if you have zulu-openjdk7
> installed and adjust BOOT_JAVA to point to /usr/lib(64)/zulu-openjdk7 in
> the script.

Well, I wouldn't say it can no longer be built, because it can, but we still haven't figured out why it fails for some and not for others.

I *might* have a lead though.

I usually use a tmpfs for my builds.
I tried with a real drive, not tmpfs.
And, well, it worked, I've just build openjdk7.

May some other share if they are using tmpfs for TMP ?
And if so, does the build works if they don't just for this time ?

	- Yth / Arnaud

From gen-bch at useyouresp.org.uk  Thu Apr  7 10:23:12 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Thu, 7 Apr 2022 11:23:12 +0100 (BST)
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CANSA5-s-Kre=OeVYeXWmVZfQU4v2gY2Y=md27yZ96JoYEn6RWQ@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwLQ93Dz4ALED9xg5g96iRKmq2qyFK1GUaxxEq0BywaVQ@mail.gmail.com>
 <CANSA5-s-Kre=OeVYeXWmVZfQU4v2gY2Y=md27yZ96JoYEn6RWQ@mail.gmail.com>
Message-ID: <2n63o48p-381s-85r3-psrn-q46s9pqs8o2@hfrlbherfc.bet.hx>

On Wed, 6 Apr 2022, Lenard Spencer wrote:

> Since openjdk6 and 7 can no longer be built at this time, I would have to
> say drop them for now.  openjdk8 can be built if you have zulu-openjdk7
> installed and adjust BOOT_JAVA to point to /usr/lib(64)/zulu-openjdk7 in
> the script.
>
>
good day all

Just on the off-chance, I decided to have another go this morning.

Openjdk7  build completed.

So to clarify between previous and this successul attempt:

Previously, immediately after installing slackware 15, I ran 'slackpkg 
upgrade-all' to bring the release up to latest changes.

Then I left it running and moved onto a laptop I used and connected up to 
it remotely using ssh.

Then I tried the openjdk7 build.  Four attempts (inc reinstall Slack 15 
plus upgrade plus tweaks suggested on here for the build) failed.

For this mornings successful build of openjdk7 I reinstalled slackware 
just as previous, but I did *not* update it (slackpkg upgrade-all).

Nor did I use 'ssh' and just did the build at the console.

So the differences are 1) I was at a console on the machine and not via 
ssh and 2) I did not run 'slackpkg upgrade-all' (which installs a new 
kernel etc) following the install.

Perhap in these two differences is a/the reason.

- environment of ssh (which I doubt is an issue as it's never been a 
problem previously so why with Slack.15)

- 'slackpkg upgrade-all' is introducing an 'incompatibility' issue (eg. 
perhaps with gcc5 ?)


It's all I have at my level of competency  .

Regards
Habs

From chris.willing at linux.com  Thu Apr  7 12:17:56 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Thu, 7 Apr 2022 22:17:56 +1000
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <20220407104118.d07f29427978f2f1c8054d67@laposte.net>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwLQ93Dz4ALED9xg5g96iRKmq2qyFK1GUaxxEq0BywaVQ@mail.gmail.com>
 <CANSA5-s-Kre=OeVYeXWmVZfQU4v2gY2Y=md27yZ96JoYEn6RWQ@mail.gmail.com>
 <20220407104118.d07f29427978f2f1c8054d67@laposte.net>
Message-ID: <374e325a-7c54-2b5b-b80e-526f69dd55d7@linux.com>


On 7/4/22 18:41, Arnaud via SlackBuilds-users wrote:
> On Wed, 6 Apr 2022 22:24:19 -0400
> Lenard Spencer <lenardrspencer at gmail.com> wrote:
> 
>> Since openjdk6 and 7 can no longer be built at this time, I would have to
>> say drop them for now.  openjdk8 can be built if you have zulu-openjdk7
>> installed and adjust BOOT_JAVA to point to /usr/lib(64)/zulu-openjdk7 in
>> the script.
> 
> Well, I wouldn't say it can no longer be built, because it can, but we still haven't figured out why it fails for some and not for others.
> 
> I *might* have a lead though.
> 
> I usually use a tmpfs for my builds.
> I tried with a real drive, not tmpfs.
> And, well, it worked, I've just build openjdk7.
> 
> May some other share if they are using tmpfs for TMP ?
> And if so, does the build works if they don't just for this time ?
> 

I don't normally have /tmp as tmpfs and the build has consistently
worked OK.

I just tried with /tmp as tmpfs and had a few failures because of
insufficient "disk" space. The reason is quite explicitly explained when
it happens so I don't think that is OP's problem.

Eventually the build succeeded when I had 10G allocated (it used ~8.3G)
and the build was quite a bit faster (23mins vs 36mins).

chris

From evandrofisico at gmail.com  Thu Apr  7 19:06:05 2022
From: evandrofisico at gmail.com (evandrofisico)
Date: Thu, 7 Apr 2022 16:06:05 -0300
Subject: [Slackbuilds-users] building luarocks for different lua versions
Message-ID: <CAMjRrgRuu4VAXi9ueLzVzwmB266rAER2xbFiMbZmNsr3b0_PCw@mail.gmail.com>

Hello Everyone.

Just installed slack 15 and while testing my own slackbuild scripts, I saw
that now we have both lua 5.1, 5.2 and 5.3 in the repositories, and all of
them beautifully capable of being installed side by side. I heavily use
luarocks as my build system for lua, and it is usually configured with a
specific lua runtime/version, said configuration happening during build
time.

I believe I've seen this asked before, but in such cases, what is the best
option? to provide a flag on the building script, enabling the user to
select which version to build the package for, to provide multiple scripts,
or try to detect the installed versions?

-- 
Evandro Alves Rodrigues
Doutor em F?sica
Centro Internacional de F?sica da Mat?ria Condensada
Laborat?rio de Supercomputa??o para Sistemas Complexos
Instituto de F?sica
Universidade de Bras?lia
fone: 3307-2900 r 238
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220407/a3fdbc87/attachment.htm>

From arnaud.garcia-fernandez at laposte.net  Thu Apr  7 20:19:03 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Thu, 7 Apr 2022 22:19:03 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <374e325a-7c54-2b5b-b80e-526f69dd55d7@linux.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwLQ93Dz4ALED9xg5g96iRKmq2qyFK1GUaxxEq0BywaVQ@mail.gmail.com>
 <CANSA5-s-Kre=OeVYeXWmVZfQU4v2gY2Y=md27yZ96JoYEn6RWQ@mail.gmail.com>
 <20220407104118.d07f29427978f2f1c8054d67@laposte.net>
 <374e325a-7c54-2b5b-b80e-526f69dd55d7@linux.com>
Message-ID: <20220407221903.e425078b62188818c1857eda@laposte.net>

On Thu, 7 Apr 2022 22:17:56 +1000
Christoph Willing <chris.willing at linux.com> wrote:
> 
> I don't normally have /tmp as tmpfs and the build has consistently
> worked OK.
> 
> I just tried with /tmp as tmpfs and had a few failures because of
> insufficient "disk" space. The reason is quite explicitly explained when
> it happens so I don't think that is OP's problem.
> 
> Eventually the build succeeded when I had 10G allocated (it used ~8.3G)
> and the build was quite a bit faster (23mins vs 36mins).
> 
> chris

Well, you're right, I just rebuilt it on a tmpfs place.
It is faster, and doesn't wear SDD drives, and my box has 32G of RAM,
hence I'm pretty OK with a 24G tmpfs for building stuff.

So eliminating process shows :
 - tmpfs or SSD are both OK.
 - JOBS=1, JOBS=5 or JOBS=9 doesn't change the outcome.
 - setting LANG=C, LANG=en_US.UTF-8 or LANG=fr_FR.UTF-8 is the same (we
never know when unicode might break something old !)
 - sourcing /etc/profile.d/gcc5.sh matters not.
 - multilib chroot or normal chroot are both working. Today. Because
yesterday's multilib chroot wasn't working (it had fontforge,
webcore-fonts, and some python packages for Kallithea and buildbot, I
removepkg'ed all non-slackware and non-multilib stuff).


So I think I figured it out finally, and we should have these sentences
added to the README :
?
  This build may consistently fail.
  In case it happens, please do unrelated stuff, sleep it off, and retry
  another day.
  It might pretty well consistently work by that time.
 ?

	- Yth...

From kjhambrick at gmail.com  Thu Apr  7 20:27:08 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Thu, 7 Apr 2022 15:27:08 -0500
Subject: [Slackbuilds-users] gdal tarball possibly changed layout
In-Reply-To: <CANBHt+PKfnCoontodxf20KgDBveT0CiZ1XrRoaqqF2fAd8xDMA@mail.gmail.com>
References: <Ykt9sYZ8Drz1nvmW.ref@giustizia.lan>
 <Ykt9sYZ8Drz1nvmW@giustizia.lan>
 <CAK09-vkfy-XEbeyWAHrh=3hnUtqEDRSV2hJH3feH39wukBbQeA@mail.gmail.com>
 <CANBHt+MO5LwUV4_X6TV1WQ7CPf=PFw0Ro0E+VkdZ+9cH_2PjVw@mail.gmail.com>
 <CANBHt+PbdjCpCqzab5zZyWV0B4dMqaXUBXc0Gi=ngGrB_C9fOA@mail.gmail.com>
 <CAK09-vnVkY1qhq_wO31gyA5osc5u0ozu1e9zPHnAobvxZxYE3g@mail.gmail.com>
 <CANBHt+PKfnCoontodxf20KgDBveT0CiZ1XrRoaqqF2fAd8xDMA@mail.gmail.com>
Message-ID: <CANBHt+OXmkzHgzF8qZVtvLF4yUgc8nGi1mTknXw3Y7ozkHj-KQ@mail.gmail.com>

Greg --

I was able to download and build OTB 7.4.0 ( September 3, 2021 Release )
without any changes to Benjamin's OTB.SlackBuild Script.

I was also able to build OTB 8.0.0 ( March 24, 2022 Release ) with a few
'minor' changes to the 7.3.0 SlackBuild.

I feel good about Version 7.4.0

However, the 8.0.0 Version needs to be tested more than I am able to test.

I removed the sed edits from the 7.3.0 OTB/SlackBuild from Line 84 thru
Line 93 because the target files no longer exist in 8.0.0

OTB 8.0.0 compiled but  I don't use these features so I am reluctant to
bless and release the OTB 8.0.0 SlackBuild without further research.

I am running 8.0.0 now and I was able to use it to clean up a few simple
image files.

But if I was to adopt OTB I would want to do a proper job with all the OTB
Version 8.0.0 Requirements and CMake Options that have changed since 7.4.0

I'll drop a line on the Mailing List.

Maybe someone is interested in adopting OTB ?

-- kjh

On Wed, Apr 6, 2022 at 8:08 AM Konrad J Hambrick <kjhambrick at gmail.com>
wrote:

> Let me think about Greg.
>
> OTB works for me now when I need it.
>
> And I would hate to take on an SB then abandon it immediately ...
>
> -- kjh
>
> -- kjh
>
> On Wed, Apr 6, 2022 at 4:49 AM Greg' Ar Tourter <artourter at gmail.com>
> wrote:
>
>> Konrad,
>>
>> note that if you are using OTB, the slackbuild is currently not
>> maintained as Benjamin unfortunately has stopped maintaining his builds. So
>> if you feel like taking it up, I suspect it is free.
>>
>> Greg
>>
>> On Tue, 5 Apr 2022 at 17:23, Konrad J Hambrick <kjhambrick at gmail.com>
>> wrote:
>>
>>> Thanks Greg.
>>>
>>> Worked Great !
>>>
>>> OTB ( montevideo ) is running as expected without a rebuild with gdal
>>> 3.4.2
>>>
>>> -- kjh
>>>
>>>
>>> On Tue, Apr 5, 2022 at 10:53 AM Konrad J Hambrick <kjhambrick at gmail.com>
>>> wrote:
>>>
>>>> Thanks Greg !
>>>>
>>>> Building gdal 3.4.2 now :)
>>>>
>>>> -- kjh
>>>>
>>>> On Mon, Apr 4, 2022 at 6:47 PM Greg' Ar Tourter <artourter at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Luis,
>>>>>
>>>>> I submitted a fix a few days ago for this. in the meantime use the
>>>>> source url off the slackbuild website:
>>>>>
>>>>> https://github.com/OSGeo/gdal/releases/download/v3.4.2/gdal-3.4.2.tar.gz
>>>>> or look at the change in git:
>>>>>
>>>>> https://git.slackbuilds.org/slackbuilds/commit/?h=willysr&id=bf9481b91e81851503e8ae54d41022eb8bbbd666
>>>>>
>>>>> Then you do not need to change anything to the slackbuild script.
>>>>>
>>>>> Hope this helps
>>>>>
>>>>> Cheers
>>>>>
>>>>> Greg
>>>>>
>>>>> On Tue, 5 Apr 2022 at 00:20, Luiz Carlos Ramos <
>>>>> lramos.prof at yahoo.com.br> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> these days I tried to build some packages which changed the SlackBuild
>>>>>> script, among them, gdal.
>>>>>>
>>>>>> In the first run, it failed.
>>>>>>
>>>>>> Searching a little bit, it seemed that the tarball has a slightly
>>>>>> different layout. In fact, everything that was supposed to be in the
>>>>>> root level is actually in the "./gdal" subdirectory.
>>>>>>
>>>>>> Also, the "configure" script was not there. It was rebuilt running
>>>>>> "autoreconf -fi" in the right time.
>>>>>>
>>>>>> I managed to tweak the slackbuild script and could ultimately build
>>>>>> the
>>>>>> package. A patch is provided below.
>>>>>>
>>>>>> Anyway, it's wise to check whether these findings happen in other
>>>>>> environments before taking any measure. One other possible cause would
>>>>>> be the tarball URL be incorrect.
>>>>>>
>>>>>> Many thanks,
>>>>>>
>>>>>> Luiz Ramos
>>>>>> lramos dot prof at yahoo dot com dot br
>>>>>> S?o Paulo - Brazil
>>>>>>
>>>>>>
>>>>>> ===
>>>>>> From 031fd83c1fb76a855bc423c4b113829f5595fd4b Mon Sep 17 00:00:00 2001
>>>>>> From: Luiz Ramos <lramos.prof at yahoo.com.br>
>>>>>> Date: Sun, 3 Apr 2022 19:46:55 -0300
>>>>>> Subject: [PATCH] gis/gdal: fixed build
>>>>>>
>>>>>> Appearently the tarball downloaded changed its layout and so the
>>>>>> build directory
>>>>>> has to be changed. Also, there is no "configure" file: it has to be
>>>>>> build using
>>>>>> "autoreconf -fi".
>>>>>> ---
>>>>>>  gis/gdal/gdal.SlackBuild | 9 ++++++++-
>>>>>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>>>>>
>>>>>> diff --git a/gis/gdal/gdal.SlackBuild b/gis/gdal/gdal.SlackBuild
>>>>>> index 4f83453333..056874624f 100644
>>>>>> --- a/gis/gdal/gdal.SlackBuild
>>>>>> +++ b/gis/gdal/gdal.SlackBuild
>>>>>> @@ -119,6 +119,9 @@ else
>>>>>>     WITHLIST+=" --with-jpeg=yes"
>>>>>>  fi
>>>>>>
>>>>>> +cd gdal
>>>>>> +autoreconf -fi
>>>>>> +
>>>>>>  # The CPPFLAGS are for the newer mariadb (thanks pprkut!)
>>>>>>  CPPFLAGS="-I/usr/include/mysql/server" \
>>>>>>  CFLAGS="$SLKCFLAGS" \
>>>>>> @@ -154,13 +157,17 @@ CXXFLAGS="$SLKCFLAGS" \
>>>>>>  make
>>>>>>  make install DESTDIR=$PKG
>>>>>>
>>>>>> +cd ..
>>>>>> +
>>>>>>  find $PKG | xargs file | grep -e "executable" -e "shared object" |
>>>>>> grep ELF \
>>>>>>    | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
>>>>>>
>>>>>>  mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
>>>>>> +cd gdal && \
>>>>>>  cp -a \
>>>>>>    COMMITTERS HOWTO-RELEASE LICENSE.TXT MIGRATION_GUIDE.TXT NEWS.md
>>>>>> PROVENANCE.TXT VERSION \
>>>>>> -  $PKG/usr/doc/$PRGNAM-$VERSION
>>>>>> +  $PKG/usr/doc/$PRGNAM-$VERSION && \
>>>>>> +cd ..
>>>>>>  cat $CWD/$PRGNAM.SlackBuild >
>>>>>> $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
>>>>>>
>>>>>>  rm -f $PKG/usr/lib*/*.la
>>>>>> --
>>>>>> 2.35.1
>>>>>>
>>>>>> _______________________________________________
>>>>> SlackBuilds-users mailing list
>>>>> SlackBuilds-users at 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 at 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 at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220407/94c2a314/attachment-0001.htm>

From sb at rbn.im  Thu Apr  7 20:34:28 2022
From: sb at rbn.im (Ruben Schuller)
Date: Thu, 7 Apr 2022 22:34:28 +0200
Subject: [Slackbuilds-users] building luarocks for different lua versions
In-Reply-To: <CAMjRrgRuu4VAXi9ueLzVzwmB266rAER2xbFiMbZmNsr3b0_PCw@mail.gmail.com>
References: <CAMjRrgRuu4VAXi9ueLzVzwmB266rAER2xbFiMbZmNsr3b0_PCw@mail.gmail.com>
Message-ID: <20220407223428.3a4958d7@kiwi.kuchen>

Hi,

2022-04-07 evandrofisico <evandrofisico at gmail.com>:

> Just installed slack 15 and while testing my own slackbuild scripts,
> I saw that now we have both lua 5.1, 5.2 and 5.3 in the repositories,
> and all of them beautifully capable of being installed side by side.
> I heavily use luarocks as my build system for lua, and it is usually
> configured with a specific lua runtime/version, said configuration
> happening during build time.
> 
> I believe I've seen this asked before, but in such cases, what is the
> best option? to provide a flag on the building script, enabling the
> user to select which version to build the package for, to provide
> multiple scripts, or try to detect the installed versions?

I have modified lua-lpeg [1] to be build for every installed lua. As I
only use lua because some stuff requires it I'm no expert on it or if
this helps with luarocks.

Cheers
Ruben

[1]
https://git.slackbuilds.org/slackbuilds/tree/libraries/lua-lpeg/lua-lpeg.SlackBuild#n80


From kjhambrick at gmail.com  Thu Apr  7 20:46:20 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Thu, 7 Apr 2022 15:46:20 -0500
Subject: [Slackbuilds-users] Xerces-c source and hdf5
In-Reply-To: <CAK09-vnfK2Geqtke+4xWi6z_rWN9z4V06kE+S=LfYUdMghdVmA@mail.gmail.com>
References: <3c396513-4544-a3f0-848a-59dabb54f015@mail.ru>
 <CAK09-vnfK2Geqtke+4xWi6z_rWN9z4V06kE+S=LfYUdMghdVmA@mail.gmail.com>
Message-ID: <CANBHt+NkxrhWRMfaDGXPkvnoXCtjww52ExGDuvPb1my0bRc4UA@mail.gmail.com>

Bouboulov --

Just to add a me too ...

The original DOWNLOAD="
http://archive.apache.org/dist/xerces/c/3/sources/xerces-c-3.2.3.tar.gz"
and
MD5SUM="a5fa4d920fce31c9ca3bfef241644494"
both worked for me just now.

And for good measure, although I had already built and installed hdf5, I
checked the DOWNLOAD and MD5DUM as well.

DOWNLOAD="
https://support.hdfgroup.org/ftp/HDF5/releases/hdf5-1.10/hdf5-1.10.6/src/hdf5-1.10.6.tar.gz
"
and
MD5SUM="37f3089e7487daf0890baf3d3328e54a"
are both 'good' as well.

And the hdf5.SlackBuild worked too:

./hdf5.SlackBuild
<<snip>>
Slackware package /tmp/hdf5-1.10.6-x86_64-1_SBo.tgz created.

# ls -la  /tmp/hdf5-1.10.6-x86_64-1_SBo.tgz
-rw-r--r-- 1 root root 4234224 Apr  7 15:40
/tmp/hdf5-1.10.6-x86_64-1_SBo.tgz

One thing about the DOWNLOAD Targets is I always execute:

# wget -N "$DOWNLOAD"

rather than using a browser to download the file(s) because I have had
issues from time-to-time with browser(s)

hth

-- kjh

On Wed, Apr 6, 2022 at 8:01 PM Greg' Ar Tourter <artourter at gmail.com> wrote:

> I cannot see any issue with either the xerces-c source nor the hdf5
> source. They both download and build fine using the original source and
> scripts.
>
> Can you give more details about the issues you are getting?
>
> Cheers
>
> Greg
>
>
> On Thu, 7 Apr 2022 at 01:44, Poligraf Poligrafovich Bouboulov via
> SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:
>
>> Hello, just to say that the address of the xerces-c source has changed :
>> the tar.gz is now at :
>>
>> https://dlcdn.apache.org//xerces/c/3/sources/xerces-c-3.2.3.tar.gz
>>
>> Also I had some problems with the hdf5 package : i had to rewrite the
>> slackbuild manually but i'm not so skilled at the moment. The archive
>> seems corrupted but managed to compile it wit the .tar editing the
>> .Slackbuild file.
>>
>> Have a nice day, Bouboulov :)
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220407/9f1b42e2/attachment.htm>

From luc.vanrompaey at gmail.com  Fri Apr  8 12:18:37 2022
From: luc.vanrompaey at gmail.com (Luc Van Rompaey)
Date: Fri, 8 Apr 2022 14:18:37 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
Message-ID: <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>

Op wo 6 apr. 2022 om 14:49 schreef Habs <gen-bch at useyouresp.org.uk>:

> On Wed, 6 Apr 2022, Luc Van Rompaey wrote:
>
> > Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
> > slackbuilds-users at slackbuilds.org>:
> >
> >>>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7
> but
> >>>>> got 0xc7a06d31)
> >>>>
> >>>> This looks like you're inadvertently using the wrong set of source
> >>>> files. Each new openjdk version has a new set of source files, many of
> >>>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
> >>>> your build system can easily pick up the wrong source file.
> >>>>
> >>>> chris
> >>>
> >>> Good morning all
> >>>
> >>> I do not doubt the comment above, but in this case, how could it be
> >> unless
> >>> the slackbuild source links are out of step/compromised/whatever.
> >>>
> >>> As I mentioned, it is a clean physical machine freshly installed and
> >> then
> >>> updated - no other [java related or other slackbuild addons etc]
> >> downloads
> >>> prior - and simply the source files linked in the slackbuild info.
> Each
> >>> slackbuild individually run using 'su -' (rather than using sbotools or
> >>> similar) as required.  I don't even get to try openjdk8 (or download
> >>> anything for it) as apache-ant, gcc5 and openjdk7 are listed as
> required
> >>> first.  It is openjdk7 that is failing in that chain as such.
> >>>
> >>> That all said, I will go back and check the sources, though I think
> that
> >>> has been done by Matteo.
> >>>
> >>> Regards
> >>> Habs
> >>
> >> My comment will not add much to the problem, but my several tries are
> all
> >> failing at the same place (ie: invalid entry CRC).
> >> Be it on my master very unclean multilib box, a chroot, multilib or not,
> >> updated and clean, or some other cleaner boxes, VMs, not multilib, I
> can't
> >> make it build, and it always fails on the same place...
> >>
> >> But unlike others here, I don't pretend doing it on perfectly clean
> >> installations (though always without any other java installed).
> >> Although I am really sure my source packages are the right ones, MD5SUM
> >> checked and all.
> >>
> >> --
> >> Arnaud <arnaud.garcia-fernandez at laposte.net>
> >>
> >> Let me first tell you all that I have been out of the Slackware loop
> for a
> > while and that I'm only just getting ready to install Slackware 15.0 on
> my
> > new computer.
> > Thus, for now, I cannot do any tests involving Slackware myself.
> >
> > Anyway, I remember looking into the different Apache Ant releases just
> > before life interfered, and I was about to try and figure out how the Ant
> > releases and the (Open)JDK version did and did not go together. I hadn't
> > gotten far enough to draw any final conclusions, though, and I hadn't
> taken
> > any meaningful notes yet.
> >> _______________________________________________
> >> SlackBuilds-users mailing list
> >> SlackBuilds-users at slackbuilds.org
> >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >> FAQ - https://slackbuilds.org/faq/
> >
> > This ongoing discussion reminded me that I had sent in an update to the
> > apache-ant slackbuild when I took it over. According to the SlackBuilds
> > history, it had been at Ant version 1.9.9 until then, and I updated it to
> > 1.9.14. Now, if I remember correctly, I had successfully compiled
> OpenJDK 7
> > (and subsequently 8) before I took over the apache-ant slackbuild, and I
> > don't believe that I have ever recompiled them since then.
> >
> > Anyway, to cut a long story short, I'm now wondering if, perhaps, the
> > problem may have anything to do with the Apache Ant version. In other
> > words, the build fails with Ant 1.9.14, but it may still complete
> > successfully with Ant 1.9.9. May be worth a try. Then, if that works, I
> may
> > attempt a build with the latest Ant 1.9.x revision (currently 1.9.16) and
> > see what gives. In any case, there's no point in trying the build with
> Ant
> > 1.10.x, since that cannot make sense of any Java run-time environment
> older
> > than, I think, Java version 8 (and, consequently, the Java environment
> > provided by gcc5).
> >
> > If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 while
> > I'm getting ready for Slackware 15.0, the Ant versions can be downloaded
> > from https://archive.apache.org/dist/ant/binaries/
> >
> > Let's hope we can work this issue out.
> >
> > Regards,
> > Luc.
> >
> Good day all
>
> I can confirm that using 1.9.9 does not resolve the issue from my attempt
> a short while ago.
>
> Regards
> Habs
>
>
> --- Sent using Alpine/Pine, probably the best MUA ---
>
> My Tox Messaging Id:
>
> 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
> Get a client here: https://tox.chat/clients.html
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
I have just successfully built openjdk7 on a freshly installed Slackware64
15.0 system, with no system updates installed yet.
The apache-ant version is 1.9.14 (as currently provided by the slackbuild).
I'm using a 24-GB tmpfs for the "/tmp" location.

I will next update the Slackware64 system and retry the openjdk7 build.

Regards,
Luc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220408/da768149/attachment-0001.htm>

From luc.vanrompaey at gmail.com  Fri Apr  8 13:10:01 2022
From: luc.vanrompaey at gmail.com (Luc Van Rompaey)
Date: Fri, 8 Apr 2022 15:10:01 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-su2dr-3i3KVxY1971g-QwhRcuLEm9uE2srRst7q8K00g@mail.gmail.com>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
Message-ID: <CACLujjwMU1+GeaHUPOKz-zP+njssH6dNNf6SHLpD6dGtZnB08w@mail.gmail.com>

Op vr 8 apr. 2022 om 14:18 schreef Luc Van Rompaey <luc.vanrompaey at gmail.com
>:

>
>
> Op wo 6 apr. 2022 om 14:49 schreef Habs <gen-bch at useyouresp.org.uk>:
>
>> On Wed, 6 Apr 2022, Luc Van Rompaey wrote:
>>
>> > Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
>> > slackbuilds-users at slackbuilds.org>:
>> >
>> >>>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7
>> but
>> >>>>> got 0xc7a06d31)
>> >>>>
>> >>>> This looks like you're inadvertently using the wrong set of source
>> >>>> files. Each new openjdk version has a new set of source files, many
>> of
>> >>>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
>> >>>> your build system can easily pick up the wrong source file.
>> >>>>
>> >>>> chris
>> >>>
>> >>> Good morning all
>> >>>
>> >>> I do not doubt the comment above, but in this case, how could it be
>> >> unless
>> >>> the slackbuild source links are out of step/compromised/whatever.
>> >>>
>> >>> As I mentioned, it is a clean physical machine freshly installed and
>> >> then
>> >>> updated - no other [java related or other slackbuild addons etc]
>> >> downloads
>> >>> prior - and simply the source files linked in the slackbuild info.
>> Each
>> >>> slackbuild individually run using 'su -' (rather than using sbotools
>> or
>> >>> similar) as required.  I don't even get to try openjdk8 (or download
>> >>> anything for it) as apache-ant, gcc5 and openjdk7 are listed as
>> required
>> >>> first.  It is openjdk7 that is failing in that chain as such.
>> >>>
>> >>> That all said, I will go back and check the sources, though I think
>> that
>> >>> has been done by Matteo.
>> >>>
>> >>> Regards
>> >>> Habs
>> >>
>> >> My comment will not add much to the problem, but my several tries are
>> all
>> >> failing at the same place (ie: invalid entry CRC).
>> >> Be it on my master very unclean multilib box, a chroot, multilib or
>> not,
>> >> updated and clean, or some other cleaner boxes, VMs, not multilib, I
>> can't
>> >> make it build, and it always fails on the same place...
>> >>
>> >> But unlike others here, I don't pretend doing it on perfectly clean
>> >> installations (though always without any other java installed).
>> >> Although I am really sure my source packages are the right ones, MD5SUM
>> >> checked and all.
>> >>
>> >> --
>> >> Arnaud <arnaud.garcia-fernandez at laposte.net>
>> >>
>> >> Let me first tell you all that I have been out of the Slackware loop
>> for a
>> > while and that I'm only just getting ready to install Slackware 15.0 on
>> my
>> > new computer.
>> > Thus, for now, I cannot do any tests involving Slackware myself.
>> >
>> > Anyway, I remember looking into the different Apache Ant releases just
>> > before life interfered, and I was about to try and figure out how the
>> Ant
>> > releases and the (Open)JDK version did and did not go together. I hadn't
>> > gotten far enough to draw any final conclusions, though, and I hadn't
>> taken
>> > any meaningful notes yet.
>> >> _______________________________________________
>> >> SlackBuilds-users mailing list
>> >> SlackBuilds-users at slackbuilds.org
>> >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> >> FAQ - https://slackbuilds.org/faq/
>> >
>> > This ongoing discussion reminded me that I had sent in an update to the
>> > apache-ant slackbuild when I took it over. According to the SlackBuilds
>> > history, it had been at Ant version 1.9.9 until then, and I updated it
>> to
>> > 1.9.14. Now, if I remember correctly, I had successfully compiled
>> OpenJDK 7
>> > (and subsequently 8) before I took over the apache-ant slackbuild, and I
>> > don't believe that I have ever recompiled them since then.
>> >
>> > Anyway, to cut a long story short, I'm now wondering if, perhaps, the
>> > problem may have anything to do with the Apache Ant version. In other
>> > words, the build fails with Ant 1.9.14, but it may still complete
>> > successfully with Ant 1.9.9. May be worth a try. Then, if that works, I
>> may
>> > attempt a build with the latest Ant 1.9.x revision (currently 1.9.16)
>> and
>> > see what gives. In any case, there's no point in trying the build with
>> Ant
>> > 1.10.x, since that cannot make sense of any Java run-time environment
>> older
>> > than, I think, Java version 8 (and, consequently, the Java environment
>> > provided by gcc5).
>> >
>> > If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 while
>> > I'm getting ready for Slackware 15.0, the Ant versions can be downloaded
>> > from https://archive.apache.org/dist/ant/binaries/
>> >
>> > Let's hope we can work this issue out.
>> >
>> > Regards,
>> > Luc.
>> >
>> Good day all
>>
>> I can confirm that using 1.9.9 does not resolve the issue from my attempt
>> a short while ago.
>>
>> Regards
>> Habs
>>
>>
>> --- Sent using Alpine/Pine, probably the best MUA ---
>>
>> My Tox Messaging Id:
>>
>> 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
>> Get a client here: https://tox.chat/clients.html
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
> I have just successfully built openjdk7 on a freshly installed Slackware64
> 15.0 system, with no system updates installed yet.
> The apache-ant version is 1.9.14 (as currently provided by the slackbuild).
> I'm using a 24-GB tmpfs for the "/tmp" location.
>
> I will next update the Slackware64 system and retry the openjdk7 build.
>
> Regards,
> Luc.
>

After I updated the Slackware64 15.0 system, the openjdk7 build fails:

java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but got
0xc7a06d31)
at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
at java.io.FilterInputStream.read(FilterInputStream.java:107)
at sun.tools.jar.Main.copy(Main.java:822)
at sun.tools.jar.Main.update(Main.java:584)
at sun.tools.jar.Main.run(Main.java:224)
at sun.tools.jar.Main.main(Main.java:1231)
gmake[8]: ***
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86:
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar]
Error 1

This confirms earlier reports from others.

Regards,
Luc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220408/fbcca82a/attachment.htm>

From gen-bch at useyouresp.org.uk  Fri Apr  8 13:10:35 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Fri, 8 Apr 2022 14:10:35 +0100 (BST)
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CAPsDuS7Mu+Wr7bX+VM=kLomfTNztmG8dPP9i0Xrnef=A_=iibw@mail.gmail.com>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
Message-ID: <7oqs597o-p241-9s20-8o57-q45510rp47rr@hfrlbherfc.bet.hx>

On Fri, 8 Apr 2022, Luc Van Rompaey wrote:

> Op wo 6 apr. 2022 om 14:49 schreef Habs <gen-bch at useyouresp.org.uk>:
>
>> On Wed, 6 Apr 2022, Luc Van Rompaey wrote:
>>
>>> Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
>>> slackbuilds-users at slackbuilds.org>:
>>>
>>>>>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7
>> but
>>>>>>> got 0xc7a06d31)
>>>>>>
>>>>>> This looks like you're inadvertently using the wrong set of source
>>>>>> files. Each new openjdk version has a new set of source files, many of
>>>>>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
>>>>>> your build system can easily pick up the wrong source file.
>>>>>>
>>>>>> chris
>>>>>
>>>>> Good morning all
>>>>>
>>>>> I do not doubt the comment above, but in this case, how could it be
>>>> unless
>>>>> the slackbuild source links are out of step/compromised/whatever.
>>>>>
>>>>> As I mentioned, it is a clean physical machine freshly installed and
>>>> then
>>>>> updated - no other [java related or other slackbuild addons etc]
>>>> downloads
>>>>> prior - and simply the source files linked in the slackbuild info.
>> Each
>>>>> slackbuild individually run using 'su -' (rather than using sbotools or
>>>>> similar) as required.  I don't even get to try openjdk8 (or download
>>>>> anything for it) as apache-ant, gcc5 and openjdk7 are listed as
>> required
>>>>> first.  It is openjdk7 that is failing in that chain as such.
>>>>>
>>>>> That all said, I will go back and check the sources, though I think
>> that
>>>>> has been done by Matteo.
>>>>>
>>>>> Regards
>>>>> Habs
>>>>
>>>> My comment will not add much to the problem, but my several tries are
>> all
>>>> failing at the same place (ie: invalid entry CRC).
>>>> Be it on my master very unclean multilib box, a chroot, multilib or not,
>>>> updated and clean, or some other cleaner boxes, VMs, not multilib, I
>> can't
>>>> make it build, and it always fails on the same place...
>>>>
>>>> But unlike others here, I don't pretend doing it on perfectly clean
>>>> installations (though always without any other java installed).
>>>> Although I am really sure my source packages are the right ones, MD5SUM
>>>> checked and all.
>>>>
>>>> --
>>>> Arnaud <arnaud.garcia-fernandez at laposte.net>
>>>>
>>>> Let me first tell you all that I have been out of the Slackware loop
>> for a
>>> while and that I'm only just getting ready to install Slackware 15.0 on
>> my
>>> new computer.
>>> Thus, for now, I cannot do any tests involving Slackware myself.
>>>
>>> Anyway, I remember looking into the different Apache Ant releases just
>>> before life interfered, and I was about to try and figure out how the Ant
>>> releases and the (Open)JDK version did and did not go together. I hadn't
>>> gotten far enough to draw any final conclusions, though, and I hadn't
>> taken
>>> any meaningful notes yet.
>>>> _______________________________________________
>>>> SlackBuilds-users mailing list
>>>> SlackBuilds-users at slackbuilds.org
>>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>>> FAQ - https://slackbuilds.org/faq/
>>>
>>> This ongoing discussion reminded me that I had sent in an update to the
>>> apache-ant slackbuild when I took it over. According to the SlackBuilds
>>> history, it had been at Ant version 1.9.9 until then, and I updated it to
>>> 1.9.14. Now, if I remember correctly, I had successfully compiled
>> OpenJDK 7
>>> (and subsequently 8) before I took over the apache-ant slackbuild, and I
>>> don't believe that I have ever recompiled them since then.
>>>
>>> Anyway, to cut a long story short, I'm now wondering if, perhaps, the
>>> problem may have anything to do with the Apache Ant version. In other
>>> words, the build fails with Ant 1.9.14, but it may still complete
>>> successfully with Ant 1.9.9. May be worth a try. Then, if that works, I
>> may
>>> attempt a build with the latest Ant 1.9.x revision (currently 1.9.16) and
>>> see what gives. In any case, there's no point in trying the build with
>> Ant
>>> 1.10.x, since that cannot make sense of any Java run-time environment
>> older
>>> than, I think, Java version 8 (and, consequently, the Java environment
>>> provided by gcc5).
>>>
>>> If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 while
>>> I'm getting ready for Slackware 15.0, the Ant versions can be downloaded
>>> from https://archive.apache.org/dist/ant/binaries/
>>>
>>> Let's hope we can work this issue out.
>>>
>>> Regards,
>>> Luc.
>>>
>> Good day all
>>
>> I can confirm that using 1.9.9 does not resolve the issue from my attempt
>> a short while ago.
>>
>> Regards
>> Habs
>>
>>
>> --- Sent using Alpine/Pine, probably the best MUA ---
>>
>> My Tox Messaging Id:
>>
>> 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
>> Get a client here: https://tox.chat/clients.html
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
> I have just successfully built openjdk7 on a freshly installed Slackware64
> 15.0 system, with no system updates installed yet.
> The apache-ant version is 1.9.14 (as currently provided by the slackbuild).
> I'm using a 24-GB tmpfs for the "/tmp" location.
>
> I will next update the Slackware64 system and retry the openjdk7 build.
>
> Regards,
> Luc.
>

Hello Luc

Yes it does seem to work from a fresh install with no updates as I 
mentioned earlier.

It will be interesting to know how it goes for you once the updates are 
applied.

Might be a good idea to resinstall Slack again (clean machine) and then 
apply the updates and then try the build - that would match what I 
originally did when it failed.

Regards and thank you
Habs


--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html


From gen-bch at useyouresp.org.uk  Fri Apr  8 13:21:53 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Fri, 8 Apr 2022 14:21:53 +0100 (BST)
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CACLujjwMU1+GeaHUPOKz-zP+njssH6dNNf6SHLpD6dGtZnB08w@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
 <CACLujjwMU1+GeaHUPOKz-zP+njssH6dNNf6SHLpD6dGtZnB08w@mail.gmail.com>
Message-ID: <1ro945oq-q9q0-14nq-2524-996q129rpq@hfrlbherfc.bet.hx>

On Fri, 8 Apr 2022, Luc Van Rompaey wrote:

> Op vr 8 apr. 2022 om 14:18 schreef Luc Van Rompaey <luc.vanrompaey at gmail.com
>> :
>
>>
>>
>> Op wo 6 apr. 2022 om 14:49 schreef Habs <gen-bch at useyouresp.org.uk>:
>>
>>> On Wed, 6 Apr 2022, Luc Van Rompaey wrote:
>>>
>>>> Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
>>>> slackbuilds-users at slackbuilds.org>:
>>>>
>>>>>>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7
>>> but
>>>>>>>> got 0xc7a06d31)
>>>>>>>
>>>>>>> This looks like you're inadvertently using the wrong set of source
>>>>>>> files. Each new openjdk version has a new set of source files, many
>>> of
>>>>>>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
>>>>>>> your build system can easily pick up the wrong source file.
>>>>>>>
>>>>>>> chris
>>>>>>
>>>>>> Good morning all
>>>>>>
>>>>>> I do not doubt the comment above, but in this case, how could it be
>>>>> unless
>>>>>> the slackbuild source links are out of step/compromised/whatever.
>>>>>>
>>>>>> As I mentioned, it is a clean physical machine freshly installed and
>>>>> then
>>>>>> updated - no other [java related or other slackbuild addons etc]
>>>>> downloads
>>>>>> prior - and simply the source files linked in the slackbuild info.
>>> Each
>>>>>> slackbuild individually run using 'su -' (rather than using sbotools
>>> or
>>>>>> similar) as required.  I don't even get to try openjdk8 (or download
>>>>>> anything for it) as apache-ant, gcc5 and openjdk7 are listed as
>>> required
>>>>>> first.  It is openjdk7 that is failing in that chain as such.
>>>>>>
>>>>>> That all said, I will go back and check the sources, though I think
>>> that
>>>>>> has been done by Matteo.
>>>>>>
>>>>>> Regards
>>>>>> Habs
>>>>>
>>>>> My comment will not add much to the problem, but my several tries are
>>> all
>>>>> failing at the same place (ie: invalid entry CRC).
>>>>> Be it on my master very unclean multilib box, a chroot, multilib or
>>> not,
>>>>> updated and clean, or some other cleaner boxes, VMs, not multilib, I
>>> can't
>>>>> make it build, and it always fails on the same place...
>>>>>
>>>>> But unlike others here, I don't pretend doing it on perfectly clean
>>>>> installations (though always without any other java installed).
>>>>> Although I am really sure my source packages are the right ones, MD5SUM
>>>>> checked and all.
>>>>>
>>>>> --
>>>>> Arnaud <arnaud.garcia-fernandez at laposte.net>
>>>>>
>>>>> Let me first tell you all that I have been out of the Slackware loop
>>> for a
>>>> while and that I'm only just getting ready to install Slackware 15.0 on
>>> my
>>>> new computer.
>>>> Thus, for now, I cannot do any tests involving Slackware myself.
>>>>
>>>> Anyway, I remember looking into the different Apache Ant releases just
>>>> before life interfered, and I was about to try and figure out how the
>>> Ant
>>>> releases and the (Open)JDK version did and did not go together. I hadn't
>>>> gotten far enough to draw any final conclusions, though, and I hadn't
>>> taken
>>>> any meaningful notes yet.
>>>>> _______________________________________________
>>>>> SlackBuilds-users mailing list
>>>>> SlackBuilds-users at slackbuilds.org
>>>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>>>> FAQ - https://slackbuilds.org/faq/
>>>>
>>>> This ongoing discussion reminded me that I had sent in an update to the
>>>> apache-ant slackbuild when I took it over. According to the SlackBuilds
>>>> history, it had been at Ant version 1.9.9 until then, and I updated it
>>> to
>>>> 1.9.14. Now, if I remember correctly, I had successfully compiled
>>> OpenJDK 7
>>>> (and subsequently 8) before I took over the apache-ant slackbuild, and I
>>>> don't believe that I have ever recompiled them since then.
>>>>
>>>> Anyway, to cut a long story short, I'm now wondering if, perhaps, the
>>>> problem may have anything to do with the Apache Ant version. In other
>>>> words, the build fails with Ant 1.9.14, but it may still complete
>>>> successfully with Ant 1.9.9. May be worth a try. Then, if that works, I
>>> may
>>>> attempt a build with the latest Ant 1.9.x revision (currently 1.9.16)
>>> and
>>>> see what gives. In any case, there's no point in trying the build with
>>> Ant
>>>> 1.10.x, since that cannot make sense of any Java run-time environment
>>> older
>>>> than, I think, Java version 8 (and, consequently, the Java environment
>>>> provided by gcc5).
>>>>
>>>> If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 while
>>>> I'm getting ready for Slackware 15.0, the Ant versions can be downloaded
>>>> from https://archive.apache.org/dist/ant/binaries/
>>>>
>>>> Let's hope we can work this issue out.
>>>>
>>>> Regards,
>>>> Luc.
>>>>
>>> Good day all
>>>
>>> I can confirm that using 1.9.9 does not resolve the issue from my attempt
>>> a short while ago.
>>>
>>> Regards
>>> Habs
>>>
>>>
>>> --- Sent using Alpine/Pine, probably the best MUA ---
>>>
>>> My Tox Messaging Id:
>>>
>>> 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
>>> Get a client here: https://tox.chat/clients.html
>>>
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>>
>> I have just successfully built openjdk7 on a freshly installed Slackware64
>> 15.0 system, with no system updates installed yet.
>> The apache-ant version is 1.9.14 (as currently provided by the slackbuild).
>> I'm using a 24-GB tmpfs for the "/tmp" location.
>>
>> I will next update the Slackware64 system and retry the openjdk7 build.
>>
>> Regards,
>> Luc.
>>
>
> After I updated the Slackware64 15.0 system, the openjdk7 build fails:
>
> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but got
> 0xc7a06d31)
> at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
> at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
> at java.io.FilterInputStream.read(FilterInputStream.java:107)
> at sun.tools.jar.Main.copy(Main.java:822)
> at sun.tools.jar.Main.update(Main.java:584)
> at sun.tools.jar.Main.run(Main.java:224)
> at sun.tools.jar.Main.main(Main.java:1231)
> gmake[8]: ***
> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86:
> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar]
> Error 1
>
> This confirms earlier reports from others.
>
> Regards,
> Luc.
>

Noted. I will not try again on this as it does look like it is something 
in the 'slackware updates' affecting something in the openjdk7 build chain 
at some point.

Thank you Luc
Habs


--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html


From lenardrspencer at gmail.com  Fri Apr  8 13:52:50 2022
From: lenardrspencer at gmail.com (Lenard Spencer)
Date: Fri, 8 Apr 2022 09:52:50 -0400
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <1ro945oq-q9q0-14nq-2524-996q129rpq@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
 <CACLujjwMU1+GeaHUPOKz-zP+njssH6dNNf6SHLpD6dGtZnB08w@mail.gmail.com>
 <1ro945oq-q9q0-14nq-2524-996q129rpq@hfrlbherfc.bet.hx>
Message-ID: <CANSA5-s+1RgvLL3eDvYDYMZ8JFchW8KuishUqmRpc2E8nzB6=w@mail.gmail.com>

Here is what I have found.  The checksum error comes from the new zlib
1.2.12, which may have fixed the problem in 1.2.11 but I suspect badly
broke something else.  Adding --disable-system-zlib to the icedtea
configure parameters takes care of that.
As for the libstdc++ library linking issue on 32-bit, this looks like an
issue with the interaction between gcc11 and gcc5 and not in openjdk(6,7).
Installing an older -current in a test partition (actually 15.0-rc1), I'll
let you know what I find.

On Fri, Apr 8, 2022 at 9:22 AM Habs <gen-bch at useyouresp.org.uk> wrote:

> On Fri, 8 Apr 2022, Luc Van Rompaey wrote:
>
> > Op vr 8 apr. 2022 om 14:18 schreef Luc Van Rompaey <
> luc.vanrompaey at gmail.com
> >> :
> >
> >>
> >>
> >> Op wo 6 apr. 2022 om 14:49 schreef Habs <gen-bch at useyouresp.org.uk>:
> >>
> >>> On Wed, 6 Apr 2022, Luc Van Rompaey wrote:
> >>>
> >>>> Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
> >>>> slackbuilds-users at slackbuilds.org>:
> >>>>
> >>>>>>>> java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7
> >>> but
> >>>>>>>> got 0xc7a06d31)
> >>>>>>>
> >>>>>>> This looks like you're inadvertently using the wrong set of source
> >>>>>>> files. Each new openjdk version has a new set of source files, many
> >>> of
> >>>>>>> which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...)
> so
> >>>>>>> your build system can easily pick up the wrong source file.
> >>>>>>>
> >>>>>>> chris
> >>>>>>
> >>>>>> Good morning all
> >>>>>>
> >>>>>> I do not doubt the comment above, but in this case, how could it be
> >>>>> unless
> >>>>>> the slackbuild source links are out of step/compromised/whatever.
> >>>>>>
> >>>>>> As I mentioned, it is a clean physical machine freshly installed and
> >>>>> then
> >>>>>> updated - no other [java related or other slackbuild addons etc]
> >>>>> downloads
> >>>>>> prior - and simply the source files linked in the slackbuild info.
> >>> Each
> >>>>>> slackbuild individually run using 'su -' (rather than using sbotools
> >>> or
> >>>>>> similar) as required.  I don't even get to try openjdk8 (or download
> >>>>>> anything for it) as apache-ant, gcc5 and openjdk7 are listed as
> >>> required
> >>>>>> first.  It is openjdk7 that is failing in that chain as such.
> >>>>>>
> >>>>>> That all said, I will go back and check the sources, though I think
> >>> that
> >>>>>> has been done by Matteo.
> >>>>>>
> >>>>>> Regards
> >>>>>> Habs
> >>>>>
> >>>>> My comment will not add much to the problem, but my several tries are
> >>> all
> >>>>> failing at the same place (ie: invalid entry CRC).
> >>>>> Be it on my master very unclean multilib box, a chroot, multilib or
> >>> not,
> >>>>> updated and clean, or some other cleaner boxes, VMs, not multilib, I
> >>> can't
> >>>>> make it build, and it always fails on the same place...
> >>>>>
> >>>>> But unlike others here, I don't pretend doing it on perfectly clean
> >>>>> installations (though always without any other java installed).
> >>>>> Although I am really sure my source packages are the right ones,
> MD5SUM
> >>>>> checked and all.
> >>>>>
> >>>>> --
> >>>>> Arnaud <arnaud.garcia-fernandez at laposte.net>
> >>>>>
> >>>>> Let me first tell you all that I have been out of the Slackware loop
> >>> for a
> >>>> while and that I'm only just getting ready to install Slackware 15.0
> on
> >>> my
> >>>> new computer.
> >>>> Thus, for now, I cannot do any tests involving Slackware myself.
> >>>>
> >>>> Anyway, I remember looking into the different Apache Ant releases just
> >>>> before life interfered, and I was about to try and figure out how the
> >>> Ant
> >>>> releases and the (Open)JDK version did and did not go together. I
> hadn't
> >>>> gotten far enough to draw any final conclusions, though, and I hadn't
> >>> taken
> >>>> any meaningful notes yet.
> >>>>> _______________________________________________
> >>>>> SlackBuilds-users mailing list
> >>>>> SlackBuilds-users at slackbuilds.org
> >>>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >>>>> Archives -
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >>>>> FAQ - https://slackbuilds.org/faq/
> >>>>
> >>>> This ongoing discussion reminded me that I had sent in an update to
> the
> >>>> apache-ant slackbuild when I took it over. According to the
> SlackBuilds
> >>>> history, it had been at Ant version 1.9.9 until then, and I updated it
> >>> to
> >>>> 1.9.14. Now, if I remember correctly, I had successfully compiled
> >>> OpenJDK 7
> >>>> (and subsequently 8) before I took over the apache-ant slackbuild,
> and I
> >>>> don't believe that I have ever recompiled them since then.
> >>>>
> >>>> Anyway, to cut a long story short, I'm now wondering if, perhaps, the
> >>>> problem may have anything to do with the Apache Ant version. In other
> >>>> words, the build fails with Ant 1.9.14, but it may still complete
> >>>> successfully with Ant 1.9.9. May be worth a try. Then, if that works,
> I
> >>> may
> >>>> attempt a build with the latest Ant 1.9.x revision (currently 1.9.16)
> >>> and
> >>>> see what gives. In any case, there's no point in trying the build with
> >>> Ant
> >>>> 1.10.x, since that cannot make sense of any Java run-time environment
> >>> older
> >>>> than, I think, Java version 8 (and, consequently, the Java environment
> >>>> provided by gcc5).
> >>>>
> >>>> If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9
> while
> >>>> I'm getting ready for Slackware 15.0, the Ant versions can be
> downloaded
> >>>> from https://archive.apache.org/dist/ant/binaries/
> >>>>
> >>>> Let's hope we can work this issue out.
> >>>>
> >>>> Regards,
> >>>> Luc.
> >>>>
> >>> Good day all
> >>>
> >>> I can confirm that using 1.9.9 does not resolve the issue from my
> attempt
> >>> a short while ago.
> >>>
> >>> Regards
> >>> Habs
> >>>
> >>>
> >>> --- Sent using Alpine/Pine, probably the best MUA ---
> >>>
> >>> My Tox Messaging Id:
> >>>
> >>>
> 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
> >>> Get a client here: https://tox.chat/clients.html
> >>>
> >>> _______________________________________________
> >>> SlackBuilds-users mailing list
> >>> SlackBuilds-users at slackbuilds.org
> >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >>> FAQ - https://slackbuilds.org/faq/
> >>>
> >>>
> >> I have just successfully built openjdk7 on a freshly installed
> Slackware64
> >> 15.0 system, with no system updates installed yet.
> >> The apache-ant version is 1.9.14 (as currently provided by the
> slackbuild).
> >> I'm using a 24-GB tmpfs for the "/tmp" location.
> >>
> >> I will next update the Slackware64 system and retry the openjdk7 build.
> >>
> >> Regards,
> >> Luc.
> >>
> >
> > After I updated the Slackware64 15.0 system, the openjdk7 build fails:
> >
> > java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
> got
> > 0xc7a06d31)
> > at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
> > at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
> > at java.io.FilterInputStream.read(FilterInputStream.java:107)
> > at sun.tools.jar.Main.copy(Main.java:822)
> > at sun.tools.jar.Main.update(Main.java:584)
> > at sun.tools.jar.Main.run(Main.java:224)
> > at sun.tools.jar.Main.main(Main.java:1231)
> > gmake[8]: ***
> >
> [/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86:
> >
> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar]
> > Error 1
> >
> > This confirms earlier reports from others.
> >
> > Regards,
> > Luc.
> >
>
> Noted. I will not try again on this as it does look like it is something
> in the 'slackware updates' affecting something in the openjdk7 build chain
> at some point.
>
> Thank you Luc
> Habs
>
>
> --- Sent using Alpine/Pine, probably the best MUA ---
>
> My Tox Messaging Id:
>
> 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
> Get a client here: https://tox.chat/clients.html
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220408/f8cf0629/attachment-0001.htm>

From arnaud.garcia-fernandez at laposte.net  Fri Apr  8 13:59:29 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Fri, 8 Apr 2022 15:59:29 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <7oqs597o-p241-9s20-8o57-q45510rp47rr@hfrlbherfc.bet.hx>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <CANSA5-vhCCNK8fZcTwYNF3-s8+k436yzZaSyRaejOVoP-hA=Fw@mail.gmail.com>
 <r21252pq-4qr5-752-997-n2r4pr96970@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
 <7oqs597o-p241-9s20-8o57-q45510rp47rr@hfrlbherfc.bet.hx>
Message-ID: <20220408155929.c065edf1132d01edec352153@laposte.net>

> Hello Luc
> 
> Yes it does seem to work from a fresh install with no updates as I 
> mentioned earlier.
> 
> It will be interesting to know how it goes for you once the updates are 
> applied.
> 
> Might be a good idea to resinstall Slack again (clean machine) and then 
> apply the updates and then try the build - that would match what I 
> originally did when it failed.
> 
> Regards and thank you
> Habs

Well, my chroots (multilib or not) are not fully uptodate.

Here is the [patches applied] -> [patches not applied] list:
aaa_base-15.0-x86_64-4_slack15.0
at-3.2.3-x86_64-1_slack15.0
bind-9.18.1-x86_64-1_slack15.0 -> bind-9.16.27-x86_64-1_slack15.0
bluez-5.64-x86_64-1_slack15.0
boost-1.78.0-x86_64-2_slack15.0
ca-certificates-20220309-noarch-1_slack15.0 -> ca-certificates-20220403-noarch-1_slack15.0
cyrus-sasl-2.1.28-x86_64-1_slack15.0
expat-2.4.7-x86_64-1_slack15.0
flac-1.3.4-x86_64-1_slack15.0
httpd-2.4.53-x86_64-1_slack15.0
libxml2-2.9.13-x86_64-1_slack15.0
libxslt-1.1.35-x86_64-1_slack15.0
mariadb-10.5.15-x86_64-2_slack15.0
mozilla-firefox-91.7.1esr-x86_64-1_slack15.0
mozilla-thunderbird-91.7.0-x86_64-1_slack15.0
openssl-1.1.1n-x86_64-1_slack15.0
openssl-solibs-1.1.1n-x86_64-1_slack15.0
php-7.4.28-x86_64-1_slack15.0
polkit-0.120-x86_64-3_slack15.0
python3-3.9.11-x86_64-1_slack15.0 -> python3-3.9.12-x86_64-1_slack15.0
qt5-5.15.3_20220312_33a3f16f-x86_64-1_slack15.0 -> qt5-5.15.3_20220318_e507d3e5-x86_64-1_slack15.0
seamonkey-2.53.11-x86_64-1_slack15.0 -> seamonkey-2.53.11.1-x86_64-1_slack15.0
util-linux-2.37.4-x86_64-1_slack15.0
 -> glibc-zoneinfo-2022a-noarch-1_slack15.0
 -> vim-8.2.4649-x86_64-1_slack15.0
 -> vim-gvim-8.2.4649-x86_64-1_slack15.0
 -> whois-5.5.12-x86_64-1_slack15.0
 -> zlib-1.2.12-x86_64-1_slack15.0

I see two possible culprits :
 -> glibc-zoneinfo-2022a-noarch-1_slack15.0
 -> zlib-1.2.12-x86_64-1_slack15.0

I'd bet on zlib, but I've been known to be false ;)
Because the error is :
  > java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but got
0xc7a06d31)
So I downgraded zlib to the stock Slackware 15.0 on my main box (which is not clean, bloated, but uptodate as a few days ago).
And I'm rebuilding it there.
...
[ 46 minutes later ]
...
It worked !
So I guess there is something different with the new zlib, and it might probably be worth mentioning to Pat and Ze SlackTeam on Linuxquestions.
I should test with updating zlib on the chroot and see it fail, but I'm going away for the week-end, so see you all on monday.

	- Yth.

From arnaud.garcia-fernandez at laposte.net  Fri Apr  8 14:00:59 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Fri, 8 Apr 2022 16:00:59 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CANSA5-s+1RgvLL3eDvYDYMZ8JFchW8KuishUqmRpc2E8nzB6=w@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
 <CACLujjwMU1+GeaHUPOKz-zP+njssH6dNNf6SHLpD6dGtZnB08w@mail.gmail.com>
 <1ro945oq-q9q0-14nq-2524-996q129rpq@hfrlbherfc.bet.hx>
 <CANSA5-s+1RgvLL3eDvYDYMZ8JFchW8KuishUqmRpc2E8nzB6=w@mail.gmail.com>
Message-ID: <20220408160059.ebaeec238538734e6e7687b6@laposte.net>

> Here is what I have found.  The checksum error comes from the new zlib
> 1.2.12, which may have fixed the problem in 1.2.11 but I suspect badly
> broke something else.  Adding --disable-system-zlib to the icedtea
> configure parameters takes care of that.
> As for the libstdc++ library linking issue on 32-bit, this looks like an
> issue with the interaction between gcc11 and gcc5 and not in openjdk(6,7).
> Installing an older -current in a test partition (actually 15.0-rc1), I'll
> let you know what I find.

Well, our messages crossed path, but they lead to the same conclusion.

	- Yth.

From luc.vanrompaey at gmail.com  Fri Apr  8 16:27:14 2022
From: luc.vanrompaey at gmail.com (Luc Van Rompaey)
Date: Fri, 8 Apr 2022 18:27:14 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <20220408160059.ebaeec238538734e6e7687b6@laposte.net>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
 <CACLujjwMU1+GeaHUPOKz-zP+njssH6dNNf6SHLpD6dGtZnB08w@mail.gmail.com>
 <1ro945oq-q9q0-14nq-2524-996q129rpq@hfrlbherfc.bet.hx>
 <CANSA5-s+1RgvLL3eDvYDYMZ8JFchW8KuishUqmRpc2E8nzB6=w@mail.gmail.com>
 <20220408160059.ebaeec238538734e6e7687b6@laposte.net>
Message-ID: <CACLujjwqYSq2s0Z8RN3fa7z9MCM-=X3h_LHfXhq6g9q5Z9Lo4Q@mail.gmail.com>

Op vr 8 apr. 2022 om 16:01 schreef Arnaud via SlackBuilds-users <
slackbuilds-users at slackbuilds.org>:

> > Here is what I have found.  The checksum error comes from the new zlib
> > 1.2.12, which may have fixed the problem in 1.2.11 but I suspect badly
> > broke something else.  Adding --disable-system-zlib to the icedtea
> > configure parameters takes care of that.
> > As for the libstdc++ library linking issue on 32-bit, this looks like an
> > issue with the interaction between gcc11 and gcc5 and not in
> openjdk(6,7).
> > Installing an older -current in a test partition (actually 15.0-rc1),
> I'll
> > let you know what I find.
>
> Well, our messages crossed path, but they lead to the same conclusion.
>
>         - Yth.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
> I ran a few more tests, with the following results:

   - After the Slackware64 15.0 system updates got installed, rebuild the
   gcc5 package and install it.
   Then, try to rebuild openjdk7.
   The openjdk7 build keeps on failing.
   - Downgrade the zlib package to 1.2.11 (i.e., the version found on the
   Slackware64 15.0 ISO).
   Again, try to rebuild openjdk7.
   This completes successfully.

So, yes, the problem is with zlib 1.2.12.

Regards,
Luc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220408/f1d10be5/attachment.htm>

From ozan.turkyilmaz at gmail.com  Fri Apr  8 16:42:55 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Fri, 08 Apr 2022 19:42:55 +0300
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CACLujjwqYSq2s0Z8RN3fa7z9MCM-=X3h_LHfXhq6g9q5Z9Lo4Q@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
 <CACLujjwMU1+GeaHUPOKz-zP+njssH6dNNf6SHLpD6dGtZnB08w@mail.gmail.com>
 <1ro945oq-q9q0-14nq-2524-996q129rpq@hfrlbherfc.bet.hx>
 <CANSA5-s+1RgvLL3eDvYDYMZ8JFchW8KuishUqmRpc2E8nzB6=w@mail.gmail.com>
 <20220408160059.ebaeec238538734e6e7687b6@laposte.net>
 <CACLujjwqYSq2s0Z8RN3fa7z9MCM-=X3h_LHfXhq6g9q5Z9Lo4Q@mail.gmail.com>
Message-ID: <7b2207353f6bd8a396b832fde0769b83fb03d6f0.camel@gmail.com>

Cum, 2022-04-08 tarihinde 18:27 +0200 saatinde, Luc Van Rompaey yazd?:
> > I ran a few more tests, with the following results:
> * After the Slackware64 15.0 system updates got installed, rebuild
> the
> gcc5 package and install it.
> Then, try to rebuild openjdk7.
> The openjdk7 build keeps on failing.
> * Downgrade the zlib package to 1.2.11 (i.e., the version found on
> the
> Slackware64 15.0 ISO).
> Again, try to rebuild openjdk7.
> This completes successfully.
> So, yes, the problem is with zlib 1.2.12.
> 

I have quickly looked at the commit messages of the zlib. There has
been serious work on crc in zlib between 1.2.11 and 1.2.12.

REgards,
Ozan

From kjhambrick at gmail.com  Fri Apr  8 19:03:06 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Fri, 8 Apr 2022 14:03:06 -0500
Subject: [Slackbuilds-users] SBo 15.0 git kig
Message-ID: <CANBHt+PvATZdopaTGZmvs+cy2DyU95mbH4qNVVpKOfZOdfbCAQ@mail.gmail.com>

Willy --

Just a minor head's up ...

I post-process the output of `git log` to write a periodic SBo update
report.

I am seeing that multimedia is misspelled as multimedir on the pipe-viewer
entry.

But that could be my simplistic LC_ALL=C environment :)

Thanks for all the SlackBuilds !

-- kjh

$ git log

<<snip>>
commit f642c864952338c7b66a241142d003efb48e7b96
Author: B. Watson <yalhcru at gmail.com>
Date:   Sun Jan 30 15:17:01 2022 -0500

    multimedir/pipe-viewer: Added (youtube CLI/GUI).

    Signed-off-by: B. Watson <yalhcru at gmail.com>
    Signed-off-by: Willy Sudiarto Raharjo <willysr at slackbuilds.org>

<<snip>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220408/2fe1f79f/attachment-0001.htm>

From urchlay at slackware.uk  Fri Apr  8 20:38:03 2022
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 8 Apr 2022 16:38:03 -0400 (EDT)
Subject: [Slackbuilds-users] SBo 15.0 git kig
In-Reply-To: <CANBHt+PvATZdopaTGZmvs+cy2DyU95mbH4qNVVpKOfZOdfbCAQ@mail.gmail.com>
References: <CANBHt+PvATZdopaTGZmvs+cy2DyU95mbH4qNVVpKOfZOdfbCAQ@mail.gmail.com>
Message-ID: <4c89a081-c933-abfb-1fa4-c02539b2a1fd@slackware.uk>



On Fri, 8 Apr 2022, Konrad J Hambrick wrote:

> I am seeing that multimedia is misspelled as multimedir on the pipe-viewer
> entry.
> 
> But that could be my simplistic LC_ALL=C environment?:)?

No, that was a plain old typo, my fault. I normally have a script
that prefixes my commit message with the category and build name, the
"multimedia/pipe-viewer: " part should have been generated by that.

If I didn't have such a script, there would be *many* bad commit
messages from me...

However, pipe-viewer was a new submission (not an update to an
existing build), and at the time, the submission form on the site was
closed. So I submitted it via git (which is not normally allowed, even
for admins), and had to type the message manually because my script
wasn't smart enough to handle new submissions via git... and obviously
I fat-fingered it.

It happened a couple months ago. IMO, it's not really worth rebasing
everything to fix that one typo. Willy, what do you think?

From luc.vanrompaey at gmail.com  Fri Apr  8 20:57:20 2022
From: luc.vanrompaey at gmail.com (Luc Van Rompaey)
Date: Fri, 8 Apr 2022 22:57:20 +0200
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <7b2207353f6bd8a396b832fde0769b83fb03d6f0.camel@gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
 <CACLujjwMU1+GeaHUPOKz-zP+njssH6dNNf6SHLpD6dGtZnB08w@mail.gmail.com>
 <1ro945oq-q9q0-14nq-2524-996q129rpq@hfrlbherfc.bet.hx>
 <CANSA5-s+1RgvLL3eDvYDYMZ8JFchW8KuishUqmRpc2E8nzB6=w@mail.gmail.com>
 <20220408160059.ebaeec238538734e6e7687b6@laposte.net>
 <CACLujjwqYSq2s0Z8RN3fa7z9MCM-=X3h_LHfXhq6g9q5Z9Lo4Q@mail.gmail.com>
 <7b2207353f6bd8a396b832fde0769b83fb03d6f0.camel@gmail.com>
Message-ID: <CACLujjyFyXkLyWn8u75NTds8FOFw=pguu8+G1p6mMEdJxUiAOg@mail.gmail.com>

Op vr 8 apr. 2022 om 18:43 schreef Ozan T?rky?lmaz <
ozan.turkyilmaz at gmail.com>:

> Cum, 2022-04-08 tarihinde 18:27 +0200 saatinde, Luc Van Rompaey yazd?:
> > > I ran a few more tests, with the following results:
> > * After the Slackware64 15.0 system updates got installed, rebuild
> > the
> > gcc5 package and install it.
> > Then, try to rebuild openjdk7.
> > The openjdk7 build keeps on failing.
> > * Downgrade the zlib package to 1.2.11 (i.e., the version found on
> > the
> > Slackware64 15.0 ISO).
> > Again, try to rebuild openjdk7.
> > This completes successfully.
> > So, yes, the problem is with zlib 1.2.12.
> >
>
> I have quickly looked at the commit messages of the zlib. There has
> been serious work on crc in zlib between 1.2.11 and 1.2.12.
>
> REgards,
> Ozan
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
> A few more notes: At the point of failure, I can manually repeat the
failing command, which is:

/tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar \
   uf \

 /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
\
   -C
/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes \
   META-INF/services/com.sun.jdi.connect.Connector

(It's a jar 'update' command.)

If I then downgrade zlib back to 1.2.11, the update will keep failing.
However, if, at this point, I run the jar 'create' command first, then the
'update' command will complete successfully:

/tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar \
   cf \

 /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
\
   -C
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
\
   .
/tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar \
   uf \

 /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
\
   -C
/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes \
   META-INF/services/com.sun.jdi.connect.Connector

If I knew how to create a small test case that demonstrates the problem in
isolation, I would be happy to file a bug report about it, but I have no
idea where to start.

Regards,
Luc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220408/c462e87c/attachment.htm>

From kjhambrick at gmail.com  Fri Apr  8 22:23:45 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Fri, 8 Apr 2022 17:23:45 -0500
Subject: [Slackbuilds-users] SBo 15.0 git kig
In-Reply-To: <4c89a081-c933-abfb-1fa4-c02539b2a1fd@slackware.uk>
References: <CANBHt+PvATZdopaTGZmvs+cy2DyU95mbH4qNVVpKOfZOdfbCAQ@mail.gmail.com>
 <4c89a081-c933-abfb-1fa4-c02539b2a1fd@slackware.uk>
Message-ID: <CANBHt+MycHhibNFVcmNcQJn+R2_x6XQ=te7c5TdD0x5+MvyhMA@mail.gmail.com>

NP B. Watson !

I've mapped multimedir to multimedia in my report until it can be fixed :)

Thanks for all the hard work All'y'All !

-- kjh

On Fri, Apr 8, 2022 at 3:38 PM B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Fri, 8 Apr 2022, Konrad J Hambrick wrote:
>
> > I am seeing that multimedia is misspelled as multimedir on the
> pipe-viewer
> > entry.
> >
> > But that could be my simplistic LC_ALL=C environment :)
>
> No, that was a plain old typo, my fault. I normally have a script
> that prefixes my commit message with the category and build name, the
> "multimedia/pipe-viewer: " part should have been generated by that.
>
> If I didn't have such a script, there would be *many* bad commit
> messages from me...
>
> However, pipe-viewer was a new submission (not an update to an
> existing build), and at the time, the submission form on the site was
> closed. So I submitted it via git (which is not normally allowed, even
> for admins), and had to type the message manually because my script
> wasn't smart enough to handle new submissions via git... and obviously
> I fat-fingered it.
>
> It happened a couple months ago. IMO, it's not really worth rebasing
> everything to fix that one typo. Willy, what do you
> think?_______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220408/5bc65638/attachment.htm>

From chris.willing at linux.com  Fri Apr  8 22:58:43 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Sat, 9 Apr 2022 08:58:43 +1000
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <CACLujjyFyXkLyWn8u75NTds8FOFw=pguu8+G1p6mMEdJxUiAOg@mail.gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
 <CACLujjwMU1+GeaHUPOKz-zP+njssH6dNNf6SHLpD6dGtZnB08w@mail.gmail.com>
 <1ro945oq-q9q0-14nq-2524-996q129rpq@hfrlbherfc.bet.hx>
 <CANSA5-s+1RgvLL3eDvYDYMZ8JFchW8KuishUqmRpc2E8nzB6=w@mail.gmail.com>
 <20220408160059.ebaeec238538734e6e7687b6@laposte.net>
 <CACLujjwqYSq2s0Z8RN3fa7z9MCM-=X3h_LHfXhq6g9q5Z9Lo4Q@mail.gmail.com>
 <7b2207353f6bd8a396b832fde0769b83fb03d6f0.camel@gmail.com>
 <CACLujjyFyXkLyWn8u75NTds8FOFw=pguu8+G1p6mMEdJxUiAOg@mail.gmail.com>
Message-ID: <961a9a2a-eade-4247-ad7a-91cac814b0bc@linux.com>

On 9/4/22 06:57, Luc Van Rompaey wrote:
> 
> 
> Op vr 8 apr. 2022 om 18:43 schreef Ozan T?rky?lmaz
> <ozan.turkyilmaz at gmail.com <mailto:ozan.turkyilmaz at gmail.com>>:
> 
>     Cum, 2022-04-08 tarihinde 18:27 +0200 saatinde, Luc Van Rompaey yazd?:
>     > > I ran a few more tests, with the following results:
>     > * After the Slackware64 15.0 system updates got installed, rebuild
>     > the
>     > gcc5 package and install it.
>     > Then, try to rebuild openjdk7.
>     > The openjdk7 build keeps on failing.
>     > * Downgrade the zlib package to 1.2.11 (i.e., the version found on
>     > the
>     > Slackware64 15.0 ISO).
>     > Again, try to rebuild openjdk7.
>     > This completes successfully.
>     > So, yes, the problem is with zlib 1.2.12.
>     >
> 
>     I have quickly looked at the commit messages of the zlib. There has
>     been serious work on crc in zlib between 1.2.11 and 1.2.12.
> 
>     REgards,
>     Ozan
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>     Archives -
>     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>     FAQ - https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/>
> 
> A few more notes: At the point of failure, I can manually repeat the
> failing command, which is:
> 
> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar \
> ? ?uf \
> ?
> ?/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
> \
> ? ?-C
> /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes \
> ? ?META-INF/services/com.sun.jdi.connect.Connector
> 
> (It's a jar 'update' command.)
> 
> If I then downgrade zlib back to 1.2.11, the update will keep failing.
> However, if, at this point, I run the jar 'create' command first, then
> the 'update' command will complete successfully:
> 
> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar \
> ? ?cf \
> ?
> ?/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
> \
> ? ?-C
> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
> \
> ? ?.
> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar \
> ? ?uf \
> ?
> ?/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
> \
> ? ?-C
> /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes \
> ? ?META-INF/services/com.sun.jdi.connect.Connector
> 
> If I knew how to create a small test case that demonstrates the problem
> in isolation, I would be happy to file a bug report about it, but I have
> no idea where to start.
> 


This thread might have been a lot shorter if it had been made clear at
the beginning that the problem related to Slackware-current. Perhaps it
was mentioned somewhere along the line but I missed that and was under
the impression we were talking about Slackware-15.0.

Slackware-15.0 comes with zlib-1.2.11 (and the build works under any
conditions for me), whereas zlib-1.2.12 is part of Slackware-current.

My understanding has always been that this list is to discuss
SlackBuilds for stable Slackware i.e. Slackware-15.0, NOT Slackware-current.

chris

From chris.willing at linux.com  Fri Apr  8 23:21:24 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Sat, 9 Apr 2022 09:21:24 +1000
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <961a9a2a-eade-4247-ad7a-91cac814b0bc@linux.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
 <CACLujjwMU1+GeaHUPOKz-zP+njssH6dNNf6SHLpD6dGtZnB08w@mail.gmail.com>
 <1ro945oq-q9q0-14nq-2524-996q129rpq@hfrlbherfc.bet.hx>
 <CANSA5-s+1RgvLL3eDvYDYMZ8JFchW8KuishUqmRpc2E8nzB6=w@mail.gmail.com>
 <20220408160059.ebaeec238538734e6e7687b6@laposte.net>
 <CACLujjwqYSq2s0Z8RN3fa7z9MCM-=X3h_LHfXhq6g9q5Z9Lo4Q@mail.gmail.com>
 <7b2207353f6bd8a396b832fde0769b83fb03d6f0.camel@gmail.com>
 <CACLujjyFyXkLyWn8u75NTds8FOFw=pguu8+G1p6mMEdJxUiAOg@mail.gmail.com>
 <961a9a2a-eade-4247-ad7a-91cac814b0bc@linux.com>
Message-ID: <68a78b2a-15da-696a-2efa-f533e935dbd3@linux.com>

On 9/4/22 08:58, Christoph Willing wrote:
> On 9/4/22 06:57, Luc Van Rompaey wrote:
>>
>>
>> Op vr 8 apr. 2022 om 18:43 schreef Ozan T?rky?lmaz
>> <ozan.turkyilmaz at gmail.com <mailto:ozan.turkyilmaz at gmail.com>>:
>>
>>     Cum, 2022-04-08 tarihinde 18:27 +0200 saatinde, Luc Van Rompaey yazd?:
>>     > > I ran a few more tests, with the following results:
>>     > * After the Slackware64 15.0 system updates got installed, rebuild
>>     > the
>>     > gcc5 package and install it.
>>     > Then, try to rebuild openjdk7.
>>     > The openjdk7 build keeps on failing.
>>     > * Downgrade the zlib package to 1.2.11 (i.e., the version found on
>>     > the
>>     > Slackware64 15.0 ISO).
>>     > Again, try to rebuild openjdk7.
>>     > This completes successfully.
>>     > So, yes, the problem is with zlib 1.2.12.
>>     >
>>
>>     I have quickly looked at the commit messages of the zlib. There has
>>     been serious work on crc in zlib between 1.2.11 and 1.2.12.
>>
>>     REgards,
>>     Ozan
>>     _______________________________________________
>>     SlackBuilds-users mailing list
>>     SlackBuilds-users at slackbuilds.org
>>     <mailto:SlackBuilds-users at slackbuilds.org>
>>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>>     Archives -
>>     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>>     FAQ - https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/>
>>
>> A few more notes: At the point of failure, I can manually repeat the
>> failing command, which is:
>>
>> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar \
>> ? ?uf \
>> ?
>> ?/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>> \
>> ? ?-C
>> /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes \
>> ? ?META-INF/services/com.sun.jdi.connect.Connector
>>
>> (It's a jar 'update' command.)
>>
>> If I then downgrade zlib back to 1.2.11, the update will keep failing.
>> However, if, at this point, I run the jar 'create' command first, then
>> the 'update' command will complete successfully:
>>
>> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar \
>> ? ?cf \
>> ?
>> ?/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>> \
>> ? ?-C
>> /tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/
>> \
>> ? ?.
>> /tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar \
>> ? ?uf \
>> ?
>> ?/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar
>> \
>> ? ?-C
>> /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes \
>> ? ?META-INF/services/com.sun.jdi.connect.Connector
>>
>> If I knew how to create a small test case that demonstrates the problem
>> in isolation, I would be happy to file a bug report about it, but I have
>> no idea where to start.
>>
> 
> 
> This thread might have been a lot shorter if it had been made clear at
> the beginning that the problem related to Slackware-current. Perhaps it
> was mentioned somewhere along the line but I missed that and was under
> the impression we were talking about Slackware-15.0.
> 
> Slackware-15.0 comes with zlib-1.2.11 (and the build works under any
> conditions for me), whereas zlib-1.2.12 is part of Slackware-current.
> 
> My understanding has always been that this list is to discuss
> SlackBuilds for stable Slackware i.e. Slackware-15.0, NOT Slackware-current.
>

Sorry about that - it was just pointed out to me that zlib-1.2.12 is
included as a patch for 15.0. Now I'm a bit confused and will have to
investigate why slackpkg hasn't upgraded it on my system.

chris

From sbo at linuxgalaxy.org  Fri Apr  8 23:30:25 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Fri, 08 Apr 2022 23:30:25 +0000
Subject: [Slackbuilds-users] building luarocks for different lua versions
In-Reply-To: <20220407223428.3a4958d7@kiwi.kuchen>
References: <CAMjRrgRuu4VAXi9ueLzVzwmB266rAER2xbFiMbZmNsr3b0_PCw@mail.gmail.com>
 <20220407223428.3a4958d7@kiwi.kuchen>
Message-ID: <8c885f7d-519b-b0fd-fc2f-648c0cfb5ee0@linuxgalaxy.org>

On 4/7/22 13:34, Ruben Schuller wrote:
> Hi,
>
> 2022-04-07 evandrofisico <evandrofisico at gmail.com>:
>
>> Just installed slack 15 and while testing my own slackbuild scripts,
>> I saw that now we have both lua 5.1, 5.2 and 5.3 in the repositories,
>> and all of them beautifully capable of being installed side by side.
>> I heavily use luarocks as my build system for lua, and it is usually
>> configured with a specific lua runtime/version, said configuration
>> happening during build time.
>>
>> I believe I've seen this asked before, but in such cases, what is the
>> best option? to provide a flag on the building script, enabling the
>> user to select which version to build the package for, to provide
>> multiple scripts, or try to detect the installed versions?
>
> I have modified lua-lpeg [1] to be build for every installed lua. As I
> only use lua because some stuff requires it I'm no expert on it or if
> this helps with luarocks.
>
> Cheers
> Ruben
>
> [1]
> https://git.slackbuilds.org/slackbuilds/tree/libraries/lua-lpeg/lua-lpeg.SlackBuild#n80
>

The problem I've bumped in to with luaXX, is that although you can
fiddle pkg-config, the final program executable will have trouble
finding the correct lua executable.

-Ed



From sbo at linuxgalaxy.org  Sat Apr  9 00:22:00 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Sat, 09 Apr 2022 00:22:00 +0000
Subject: [Slackbuilds-users] make -j${NUMJOBS} discussion
In-Reply-To: <CANi9qSseQSO8PaNYrG4m9Fy-HcNY0SJ5anipWUaVy1Ep-tkpVg@mail.gmail.com>
References: <b7018ace-ca29-c71b-c81d-815e1be10098@linuxgalaxy.org>
 <cdc5af12-de2e-7af-dc3e-2de1b0547d6c@slackware.uk>
 <2b75ad06-404f-a6b1-5c34-8118061c1f5f@linuxgalaxy.org>
 <CANi9qSseQSO8PaNYrG4m9Fy-HcNY0SJ5anipWUaVy1Ep-tkpVg@mail.gmail.com>
Message-ID: <96a8745f-d103-3a7e-a00b-2b072f4ce950@linuxgalaxy.org>

On 4/4/22 01:41, Jeremy Hansen wrote:
> On Sun, Apr 3, 2022, 5:44 PM Slackbuilds <sbo at linuxgalaxy.org
> <mailto:sbo at linuxgalaxy.org>> wrote:
>
...
>
>     I'm still not convinced that globally setting MAKEFLAGS won't have
>     unintended consequences. I keep seeing in the make docs that the
>     toplevel make creates/sets MAKEFILE for sub-makes, but isn't clear in
>     what happens if MAKEFILES is already set, unless upstream source adds
>     that logic.
>
>     Setting 'make -j$NUMJOBS' seems a safer path, and is what Pat does in
>     Slackware source.
>
>
> This had been discussed on LQ and it was found that make is smart enough
> to talk with its own sub-makes to ensure no more than the max number of
> jobs can take place (specifically post #23, which is mine).
>
> https://www.linuxquestions.org/questions/slackware-14/multi-thread-builds-via-sbopkg-slackbuilds-4175684827/
> <https://www.linuxquestions.org/questions/slackware-14/multi-thread-builds-via-sbopkg-slackbuilds-4175684827/>
>
> The only time it doesn't happen is if a makefile is poorly made as
> demonstrated by pan64. However, I've had a global MAKEFLAGS set with
> only what essentially sets -j17 in there since 2017 and I've never seen
> build issues from it.
>
> So, while theoretical, global MAKEFLAGS can cause issues with a poorly
> made MAKEFILE, it seems they are extremely uncommon (if they exist at all).
>
> NOTE: This is not to say we shouldn't have NUMJOBS in SlackBuilds (I
> don't really have a preference), but just to say that setting -jXX in a
> global MAKEFLAGS is unlikely to cause any issues in practice.
>
> Here's the content of my /etc/profile.d/make-exports.sh. I have it do
> the number of CPUs the kernel sees + 1 (this will include total threads,
> at least on AMD systems).
>
> export MAKEFLAGS="-j$(expr $(nproc) + 1)"
>
> Jeremy
>

Thanks. I had missed that thread.  I'll try 'export MAKEFLAGS...' here
for the VMs, leaving the script parallel agnostic, to avoid issues with
other users' environment etc. and to avoid silly conflicts with SBo admins.

-Ed



From willysr at slackbuilds.org  Sat Apr  9 01:02:59 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 9 Apr 2022 08:02:59 +0700
Subject: [Slackbuilds-users] SBo 15.0 git kig
In-Reply-To: <4c89a081-c933-abfb-1fa4-c02539b2a1fd@slackware.uk>
References: <CANBHt+PvATZdopaTGZmvs+cy2DyU95mbH4qNVVpKOfZOdfbCAQ@mail.gmail.com>
 <4c89a081-c933-abfb-1fa4-c02539b2a1fd@slackware.uk>
Message-ID: <11ed18f5-69dc-91bc-3e2a-e7ca0d832437@slackbuilds.org>

>> I am seeing that multimedia is misspelled as multimedir on the
>> pipe-viewer
>> entry.
>>
>> But that could be my simplistic LC_ALL=C environment?:)?
> 
> No, that was a plain old typo, my fault. I normally have a script
> that prefixes my commit message with the category and build name, the
> "multimedia/pipe-viewer: " part should have been generated by that.
> 
> If I didn't have such a script, there would be *many* bad commit
> messages from me...
> 
> However, pipe-viewer was a new submission (not an update to an
> existing build), and at the time, the submission form on the site was
> closed. So I submitted it via git (which is not normally allowed, even
> for admins), and had to type the message manually because my script
> wasn't smart enough to handle new submissions via git... and obviously
> I fat-fingered it.
> 
> It happened a couple months ago. IMO, it's not really worth rebasing
> everything to fix that one typo. Willy, what do you think?

Since it happened and it's only a commit message, i don't think we can
do anything about it and rebasing master is big no :)


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220409/d849f8a6/attachment.asc>

From ozan.turkyilmaz at gmail.com  Sat Apr  9 06:21:49 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Sat, 09 Apr 2022 09:21:49 +0300
Subject: [Slackbuilds-users] openjdk8 compile (either manually or via
 sbotools) failing at openjdk7
In-Reply-To: <7b2207353f6bd8a396b832fde0769b83fb03d6f0.camel@gmail.com>
References: <np483s32-oop-6os4-qs20-949571rp554@hfrlbherfc.bet.hx>
 <ab745272-d160-10d1-9097-cc2339b5f64b@slackbuilds.org>
 <6p29962-o7op-n5o3-4r69-7p340nq564@hfrlbherfc.bet.hx>
 <ns8r9n83-6348-60sq-r3p-4r6930n26q@hfrlbherfc.bet.hx>
 <40727bc9-31cb-2eb0-8cc3-a76294663db8@slackbuilds.org>
 <n256s3-33r-r865-552r-p37no070n63o@hfrlbherfc.bet.hx>
 <443oq0-3ss9-37s3-5614-r20664r05s@hfrlbherfc.bet.hx>
 <8e62d436-13d4-f63b-5354-da5d20371892@linux.com>
 <113s4np4-no47-pp72-4646-4o02r3s5s6n@hfrlbherfc.bet.hx>
 <20220406100956.54bc2b3c408b5a9c69e27ce7@laposte.net>
 <CACLujjw9Jc2h8fG9gzQT482eyTkXzktZQ1_aeGf5jMefKDLWbQ@mail.gmail.com>
 <p6r6rs4-nr8-22rq-nr50-sso4qr7nq987@hfrlbherfc.bet.hx>
 <CACLujjwRGsQikSNwW8BuBDKYaXY4bhnhSrZiy2cX0KLx9EsOZw@mail.gmail.com>
 <CACLujjwMU1+GeaHUPOKz-zP+njssH6dNNf6SHLpD6dGtZnB08w@mail.gmail.com>
 <1ro945oq-q9q0-14nq-2524-996q129rpq@hfrlbherfc.bet.hx>
 <CANSA5-s+1RgvLL3eDvYDYMZ8JFchW8KuishUqmRpc2E8nzB6=w@mail.gmail.com>
 <20220408160059.ebaeec238538734e6e7687b6@laposte.net>
 <CACLujjwqYSq2s0Z8RN3fa7z9MCM-=X3h_LHfXhq6g9q5Z9Lo4Q@mail.gmail.com>
 <7b2207353f6bd8a396b832fde0769b83fb03d6f0.camel@gmail.com>
Message-ID: <425a60ce90a01b5efae80d37d89d29a8ae1d1363.camel@gmail.com>

Cum, 2022-04-08 tarihinde 19:42 +0300 saatinde, Ozan T?rky?lmaz yazd?:
> I have quickly looked at the commit messages of the zlib. There has
> been serious work on crc in zlib between 1.2.11 and 1.2.12.
> 
> REgards,
> Ozan

Also have a look at this bug report:
https://github.com/madler/zlib/issues/618
Looks like there's a common problem with crc calculations now. However,
I got somehow good news:
https://github.com/madler/zlib/commit/ec3df00224d4b396e2ac6586ab5d25f673caa4c2
Probably fixes the issue.

Regards,
Ozan

From willysr at slackbuilds.org  Sat Apr  9 09:06:56 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 9 Apr 2022 16:06:56 +0700
Subject: [Slackbuilds-users] Updates - 20220409.1
Message-ID: <f3482758-360c-0d35-d75c-f795be17790c@slackbuilds.org>

Sat Apr  9 08:47:00 UTC 2022
academic/Gabedit: Added (Graphical UI to computational chemistry)
academic/Gridcoin-Research: Remove NUMJOBS per maillist
academic/Gridcoin-Research: Upgraded for version 5.3.3.0
academic/OpenFOAM: Updated for version 9.
academic/aeskulap: Fix shebang.
academic/amplifx: Fix download URL.
academic/armadillo: Fix download URL, doc dir.
academic/bedGraphToBigWig: Strip binary.
academic/cap3: Fix docs.
academic/convertall: Fix docs.
academic/genpak: Fix docs.
academic/scipy3: Updated for version 1.8.0. New maintainer.
academic/suitesparse: Updated for version 5.11.0
academic/xsimd: Added (C++ wrappers for SIMD intrinsics)
audio/MusicMixer: Add doinst.sh.
audio/aacplusenc: Fix docs.
audio/alsa-tools: Remove bad symlinks, empty /etc dir.
audio/alsamixergui: Fix docs and PRINT_PACKAGE_NAME.
audio/amSynth: Fix doinst.sh.
audio/ario: Fix docs.
audio/atunes: Make arch-dependent (not noarch).
audio/celt051: Fix docs.
audio/celt: Fix docs.
audio/qmmp-plugin-pack-qt5: Updated for version 1.5.3.
audio/qmmp-qt5: Updated for version 1.5.4.
audio/wireplumber: Added (policy manager for PipeWire).
business/beancount: Fix docs.
desktop/afterstep: Fix minor conflict with dpkg.
desktop/arandr: Add doinst.sh to support .desktop file.
desktop/areao43-icon-theme: Fix icon perms, don't write to $CWD.
desktop/aweather: Add doinst.sh.
desktop/bashrun2: Fix docs.
desktop/bemenu: Gzip man page, use SLKCFLAGS.
desktop/birdtray: Fix .desktop file.
desktop/cairo-clock: Fix docs.
desktop/crystalcursors: Fix permmissions, broken symlinks.
desktop/mint-themes: Align to template.
desktop/recoll: Updated for version 1.32.0.
desktop/swaybg: Wrap README at 72 columns.
desktop/xss-lock: fix cmake policy obsoloscence warning
development/4th: Fix docs.
development/Fennel: Updated for version 1.0.0.
development/OpenJDK11: Fix github tarball handling.
development/OpenJDK17: Fix github tarball handling.
development/REDasm: Added (Cross Platform Dissassembler).
development/amazon-corretto: Fix PRINT_PACKAGE_NAME support.
development/apache-jmeter: Fix docs, symlinks.
development/apache-log4cxx: Fix docs, rm static lib.
development/arm-binutils: Fix docs.
development/asem51: Clean up package.
development/avr8-burn-o-mat: Make noarch, fix .desktop.
development/bed: Remove some cruft.
development/binwalk: Fix docs.
development/bzr: Remove INSTALL from doc dir.
development/cc65: Fix docs.
development/ccl: Fix download URL.
development/clojure: Added (Dynamic programming language for JVM).
development/colordiff: Fix download URL, fix docs.
development/cppcheck: Add doinst, fix translations.
development/cppcheck: Fix icon size (65x65 => 64x64).
development/cream: Fix icons, .desktop, doinst.sh.
development/cunit: Fix docs.
development/ghex: Update for 42.0; new maintainer
development/ghidra: Added (Reverse Engineering Tool).
development/jupyter-ipykernel: Update README
development/jupyter-nbconvert: Fix REQUIRES.
development/jupyter-nbformat: Updated for version 5.3.0.
development/micro: Added (Text Editor).
development/mmtf-cpp: Remove template comment.
development/rstudio-desktop-legacy: Added (R Statistical IDE).
development/rstudio-desktop: Updated for version 2022.02.1+461.
development/ruff: install missing diagram.tcl file.
development/squeak-vm: Added (squeak virtual machine).
development/tiled: updated for version 1.8.4
development/xmake: Added (cross-platform build utility based on Lua)
games/FlightGear-data: Updated for version 2020.3.13.
games/FlightGear: Updated for version 2020.3.13.
games/SpaceZero: Fix doc permissions.
games/adl: Fix doc permissions.
games/ags: updated for version 3.5.1.17
games/alienarena: Fix docs.
games/antares: Fix .desktop file.
games/antimicrox: Fix docs, doinst.sh.
games/armagetronad: Fix docs, doinst.sh.
games/arnold-cpc: Fix docs.
games/arx-libertatis: Fix doinst.sh.
games/assaultcube-reloaded: Strip binaries.
games/atari800: Strip binary.
games/bomberclone: Fix icon, .desktop.
games/briquolo: Add SlackBuild to doc dir.
games/cgames: Fix build.
games/devilutionx: Added (Port of Diablo).
games/edgar: Updated for version 1.35.
games/epsxe: Add missing file.
games/fceux: Updated for version 2.6.4.
games/mupen64plus-video-gliden64: Added (Plugin for mupen64plus).
games/protontricks: Added (winetricks wrapper for proton).
games/steamtinkerlaunch: Added (Linux wrapper tool for Steam client)
games/waterCloset: Update README.
games/wesnoth: Update for version 1.16.2
gis/gdal: fix download file.
gis/google-earth: Fix MD5SUM.
graphics/OpenVSP: Update DOWNLOAD URL.
graphics/apitrace: Fix conflict with dpkg.
graphics/birdfont: Added (free font editor).
graphics/blender: Fix doc and icon dirs, strip python stuff.
graphics/brlcad: Fix broken symlink in doc dir.
graphics/fontforge: Fix doc dir and PRINT_PACKAGE_NAME.
graphics/gscan2pdf: fix missing dependency
graphics/hugin: Updated for version 2021.0.0.
graphics/kColorPicker: Added (Qt based Color Picker).
graphics/kImageAnnotator: Added (Tool for annotating images).
graphics/ksnip: Added (Screenshot Tool).
graphics/mangohud: Add missing patch.
ham/ax25-apps: Strip binaries.
ham/ax25-tools: Strip binaries.
ham/baudline: Actually set ARCH.
ham/libax25: Strip libraries.
ham/tucnak: Install doinst.
libraries/PDCurses: Updated for version 3.9.
libraries/SimGear: Updated for version 2020.3.13.
libraries/activemq-cpp: Fix docs, rm static lib.
libraries/adns: Strip binaries.
libraries/afflib: Strip library.
libraries/allegro4: Use correct doc dir.
libraries/alure: Remove empty /usr/share from package.
libraries/aqbanking: Fix docs.
libraries/cloog: Added (code generation library).
libraries/cppzmq: Remove tabs from README.
libraries/dcmtk: Fix docs.
libraries/gnome-autoar: Added (Archives library)
libraries/libmpdclient: Fix docs.
libraries/libmsym: Align to template.
libraries/libpano13: Updated for version 2.9.21.
libraries/libxmlbird: Remove template comments.
libraries/luadbi: Updated for version 0.7.2.
libraries/miniupnnpc: Remove python3 check.
libraries/qmltermwidget: Updated for version 20220109_6322802.
libraries/qt4: Fix docs, icon, .desktop.
libraries/seatd: Added (Seat management library and daemon).
libraries/setproctitle: Remove python3 check.
libraries/soci: Added (Database Access Library for C++).
libraries/stormlib: Added (Library to handle MPQ).
libraries/uhttpmock: Added (Library for Mocking web service API's).
libraries/wimlib: Updated for version 1.13.5.
libraries/wlroots: Added (wayland compositor library).
libraries/ytnef: Added (Yerase's TNEF Stream Reader).
misc/ardesia: Remove /usr/share/doc, don't write to /root.
misc/asterixInspector: Strip binary, fix .desktop.
misc/bbrun: Use SLKCFLAGS, strip binary.
misc/bodr: Fix docs.
misc/bsdsfv: COLOR=yes by default, fix docs.
misc/dex: Fix slack-desc.
misc/simh-classic (SimH Simulator).
multimedia/aegisub: Add SlackBuild to doc dir.
multimedia/audio-recorder: Fix template order (PRINT_PACKAGE_NAME).
multimedia/avidemux: Fix man page.
multimedia/bdtools: Fix docs.
multimedia/bdtools: Fix docs.
multimedia/haruna: Added (Video Player).
network/Electrum: Updated for version 4.2.1.
network/MEGAcmd: Fix slack-desc.
network/aoetools: Fix permissions.
network/arping: Fix docs.
network/asciinema: Install docs to correct dir.
network/awstats: Install SlackBuild in doc dir.
network/axel: Strip binary.
network/bollux: Make noarch, fix manpage perms.
network/ckermit: Fix doc and man permissions.
network/clipgrab: Fix docs.
network/clipgrab: Fix download URL and docs.
network/clusterit: Added (distributed shell)
network/mailspring: Updated for version 1.10.2.
network/microsoft-edge: Added (browser).
network/neomutt: Updated for version 20220408.
network/nextcloud-desktop: Fix Tarball.
network/nextcloud-desktop: Updated for version 3.4.4.
network/nordvpn: Updated for version 3.12.5.
network/openconnect-sso: Added (Wrapper for OpenConnect).
network/owncloud-client: Update for 2.10.1.7187
network/sfeed: Updated for version 1.4.
network/signal-desktop: Updated for version 5.38.0.
network/syncthing: Revert maintainer.
network/syncthing: Update for 1.19.2
office/MasterPDFEditor: Updated for version 5.8.46.
office/aigaion: Fix doc ownership.
office/apvlv: Fix doinst.sh.
office/basket: Fix .desktop perm, HTML doc path.
office/basket: Fix icon.
office/bibutils: Use SLKCFLAGS, strip binaries.
office/gnucash-docs: Updated for version 4.10.1.
office/gnucash: Updated for version 4.10.
office/keepassxc: updated for version 2.7.1
office/pstoedit: Updated for version 3.77.
perl/perl-GooCanvas2: fix missing dependency
perl/perl-Locale-Codes: Added (modules to handle locale codes)
perl/perl-PDF-Builder: Updated for version 3.023
python/artifacts: Fix docs.
python/buildbot-badges: Added (Plugin for buildbot).
python/cppy: Added (C++ header library)
python/cryptography: Fix docs.
python/icalendar: Added (parser / generator for iCalendar).
python/iniconfig: Added (INI file parsing).
python/psutil: Remove python3 check.
python/pyinotify: Build Python3 by default.
python/python-beniget: Added (static analyzer for Python code)
python/python-bitstring: Updated for version 3.1.9.
python/python-gast: Added (AST abstracts underlying Python version)
python/python-prometheus_client: Update for 0.14.0
python/python-watchdog: Added (Filesystem events monitoring).
python/python2-automat: updated REQUIRES (wheel needed for build)
python/python2-pyhamcrest: Added (Python module).
python/python2-twisted: updated for version 20.3.0
python/python3-automat: updated REQUIRES (wheel needed for build)
python/python3-fastjsonschema: Added (Fast JSON schema validator).
python/python3-kiwisolver: Updated for v. 1.4.2. New maintainer.
python/python3-klein: Added (micro-framework for web services).
python/python3-panda: Updated for version 1.4.2.
python/python3-pytest: Updated for version 7.1.1.
python/python3-pythran: Added (AOT compiler for numeric kernels)
python/typing-extensions: Fix docs.
system/afuse: Clean up doc dir.
system/alien: Remove perllocal.pod.
system/android-udev-rules: Added (udev rules and permissions).
system/andromeda: Fix .desktop file.
system/apache-activemq: Remove wrong-architecture binaries.
system/apcupsd: Fix icons and .desktop.
system/argyllcms: Fix doc permissions.
system/autoarchive: Fix broken man page symlink.
system/autojump: Don't install python modules to /usr/bin.
system/autoslackpkg: Removed (use slackupdr).
system/babeltrace: Remove static libs and /usr/share/doc.
system/bcache-tools: Strip binaries, move to /usr/sbin.
system/blake2: Strip binary, use SLKCFLAGS.
system/bogofilter: Fix doc dir.
system/bottom: Added (system/process monitor).
system/btrbk: Make noarch, gzip man pages.
system/bulk_extractor: Fix docs.
system/byobu: Fix doc dir and .desktop.
system/cfengine: Fix build when avahi installed.
system/cool-retro-term: Updated for version 1.2.0.
system/ddrescueview: Added (GUI For ddrescue).
system/dosbox: Fix icon and .desktop.
system/fzf: Updated for version 0.30.0.
system/hexcompare: Added (console-mode visual binary diff)
system/hyperfine: Added (command-line benchmarking tool).
system/iotop-c: Added (I/O top).
system/jenkins: Updated for version 2.332.2.
system/nvidia-legacy390-kernel: Remove unneeded patch.
system/pcem-roms: Fix github tarball handling.
system/piper: Update HOMEPAGE
system/powerline-status: Updated for version 2.8.2.
system/s6-rc: Updated for version 0.5.3.1.
system/sane-airscan: Added (Scanner Access Now Easy).
system/sbo-maintainer-tools: Added (lint tools for SBo maintainers)
system/slackupdr: Added (slackpkg automation).
system/slpkg: Updated for version 3.9.6.
system/smpq: Added (StormLib MPQ archiving utility).
system/tmsu-bin: Added (tool for tagging files)
system/watchdog: Moved from python.
+--------------------------+


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220409/d12306ca/attachment-0001.asc>

From slackbuilds at schoepfer.info  Sat Apr  9 13:46:38 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 09 Apr 2022 15:46:38 +0200
Subject: [Slackbuilds-users] md5sum nextcloud-desktop-3.4.4
Message-ID: <5c2490758c1dcbf04a99d35470988d7f@schoepfer.info>

Hi,

the md5sum for nextcloud-desktop doesn't match, it should be
7f5f0a209fa726533b18c7a19890e027

Johannes

From willysr at slackbuilds.org  Sat Apr  9 16:04:40 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 9 Apr 2022 23:04:40 +0700
Subject: [Slackbuilds-users] md5sum nextcloud-desktop-3.4.4
In-Reply-To: <5c2490758c1dcbf04a99d35470988d7f@schoepfer.info>
References: <5c2490758c1dcbf04a99d35470988d7f@schoepfer.info>
Message-ID: <2b12c155-e16f-1c73-74bd-e04b93fa4021@slackbuilds.org>

> the md5sum for nextcloud-desktop doesn't match, it should be
> 7f5f0a209fa726533b18c7a19890e027

Thanks
fixed in my branch


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220409/4d00bd1e/attachment.asc>

From phalange at komputermatrix.com  Sat Apr  9 16:08:05 2022
From: phalange at komputermatrix.com (Andrew Payne)
Date: Sat, 9 Apr 2022 12:08:05 -0400 (EDT)
Subject: [Slackbuilds-users] md5sum nextcloud-desktop-3.4.4
In-Reply-To: <2b12c155-e16f-1c73-74bd-e04b93fa4021@slackbuilds.org>
References: <5c2490758c1dcbf04a99d35470988d7f@schoepfer.info>
 <2b12c155-e16f-1c73-74bd-e04b93fa4021@slackbuilds.org>
Message-ID: <5e8a7c9-2d11-c46-82df-97304688895@imap.fatcow.com>


It's not the md5sum that's wrong, that github URL is wrong.

The link wrongs says .../refs/tags/v3.4.3/...

it should be v3.4.4


On Sat, 9 Apr 2022, Willy Sudiarto Raharjo wrote:

> > the md5sum for nextcloud-desktop doesn't match, it should be
> > 7f5f0a209fa726533b18c7a19890e027
>
> Thanks
> fixed in my branch
>
>
> --
> Willy Sudiarto Raharjo
>

From willysr at slackbuilds.org  Sat Apr  9 16:33:39 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 9 Apr 2022 23:33:39 +0700
Subject: [Slackbuilds-users] md5sum nextcloud-desktop-3.4.4
In-Reply-To: <5e8a7c9-2d11-c46-82df-97304688895@imap.fatcow.com>
References: <5c2490758c1dcbf04a99d35470988d7f@schoepfer.info>
 <2b12c155-e16f-1c73-74bd-e04b93fa4021@slackbuilds.org>
 <5e8a7c9-2d11-c46-82df-97304688895@imap.fatcow.com>
Message-ID: <0e6072dd-549e-4f3c-f785-d372d8c093c8@slackbuilds.org>

> 
> It's not the md5sum that's wrong, that github URL is wrong.
> 
> The link wrongs says .../refs/tags/v3.4.3/...
> 
> it should be v3.4.4

Ah, you are right
i missed that one

thanks


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220409/be4a8525/attachment.asc>

From urchlay at slackware.uk  Mon Apr 11 17:55:45 2022
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 11 Apr 2022 13:55:45 -0400 (EDT)
Subject: [Slackbuilds-users] extra files in $PKG/install
Message-ID: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>


I've been going through a lot of packages, looking for issues...

How many of you have files named like these?

$ ls -d /installpkg-*
/installpkg-424f0b9b8dfa39116f400a1e28c81427/
/installpkg-48c5f1121baf117bc8cd5cb81d4c315a/
/installpkg-8ce33bb6875a083c1b82af332c9a1175/
/installpkg-a6c16f0748bbc7f892dd56447a375fa6/
/installpkg-ad84c0c457f72e604075589930b129de/
/installpkg-c863767111eaaddfb8623271f76a6c8b/
/installpkg-cd8a50cc9a20baff05436e5e21b3b89b/
/installpkg-d9f3419d09ef5f9fe23a0a1a2c198b8d/
/installpkg-e4b7c85746cc950dff947233cb978aaa/
/installpkg-f850ef68bdfdb986ee187fd495acf84d/

It turns out that SlackBuilds which put extra files in $PKG/install
cause these 'turds' to be installed. The installpkg command creates
these, with the contents of 'install/' in the package (meaning they
contain slack-desc and doinst.sh, if it exists), but it doesn't
remove them if they contain extra files, because it deletes/moves
the slack-desck and doinst.sh, then uses rmdir to delete the
/installpkg-<hash> directory.

As an added bonus, any code in doinst.sh that expects to use a file
in /install (e.g. freeimpi tries to use /install/conffiles), will fail
because by the time doinst.sh runs, the directory has been renamed.

I can and will fix the ones I know about, but everyone, you should
check your builds to see if they do this.

From erich.public at protonmail.com  Mon Apr 11 18:57:50 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Mon, 11 Apr 2022 18:57:50 +0000
Subject: [Slackbuilds-users] graphcis/fontforge: Fails to build (for me)
Message-ID: <7G_3XBrNSiBuJE0wRanGZm-zzkJcGihjJDoxPfmftxy6R2pTnBK_R9Z9wvKYL5VToh_8WjERziBd3y9Frc-buK2dnqyXuf4mO_GSggARwv0=@protonmail.com>

Is it just me, or did the latest update to fontforge break the build?

I do not build with the optional Sphinx dependency, which I assume is the reason it fails.

Here is the tail end of my build log:

-- Installing: /tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/locale/vi/LC_MESSAGES/FontForge.mo
-- Installing: /tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/locale/zh_CN/LC_MESSAGES/FontForge.mo
-- Installing: /tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/locale/zh_TW/LC_MESSAGES/FontForge.mo
-- Installing: /tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/fontforge/hotkeys/default
-- Installing: /tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/fontforge/prefs
Adobe-CNS1-5.cidmap
Adobe-GB1-5.cidmap
Adobe-Identity-0.cidmap
Adobe-Japan1-6.cidmap
Adobe-Japan2-0.cidmap
Adobe-Korea1-2.cidmap
mv: cannot stat '/tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/doc/fontforge/*': No such file or directory
graphics/fontforge: fontforge.SlackBuild failed (status 1)              18:00:35
Unmounting chroot ...
:-( graphics/fontforge FAILED )-:

This new line added to the SlackBuild is the culprit:

mv $PKG/usr/share/doc/$PRGNAM/* $PKG/usr/doc/$PRGNAM-$VERSION

I commented it out and the build succeeded, and as expected the resulting package does not contain /usr/share/doc.

Erich

From erich.public at protonmail.com  Mon Apr 11 19:16:14 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Mon, 11 Apr 2022 19:16:14 +0000
Subject: [Slackbuilds-users] graphcis/fontforge: Fails to build (for me)
In-Reply-To: <7G_3XBrNSiBuJE0wRanGZm-zzkJcGihjJDoxPfmftxy6R2pTnBK_R9Z9wvKYL5VToh_8WjERziBd3y9Frc-buK2dnqyXuf4mO_GSggARwv0=@protonmail.com>
References: <7G_3XBrNSiBuJE0wRanGZm-zzkJcGihjJDoxPfmftxy6R2pTnBK_R9Z9wvKYL5VToh_8WjERziBd3y9Frc-buK2dnqyXuf4mO_GSggARwv0=@protonmail.com>
Message-ID: <-opo_jhqoxG4dcdT2by6UoxCuRqfbwSzPOfXak7cyX1SRp_OkFCYPhTpNmRIgGILvxIwW0jxIJqXvi5Hy3LagJe_gsbXMDpFYH68S7Q_yrM=@protonmail.com>

------- Original Message -------
On Monday, April 11th, 2022 at 1:57 PM, Erich Ritz via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:


>
>
>
> Is it just me, or did the latest update to fontforge break the build?
>
> I do not build with the optional Sphinx dependency, which I assume is the reason it fails.
>
> Here is the tail end of my build log:
>
> -- Installing: /tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/locale/vi/LC_MESSAGES/FontForge.mo
> -- Installing: /tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/locale/zh_CN/LC_MESSAGES/FontForge.mo
> -- Installing: /tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/locale/zh_TW/LC_MESSAGES/FontForge.mo
> -- Installing: /tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/fontforge/hotkeys/default
> -- Installing: /tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/fontforge/prefs
> Adobe-CNS1-5.cidmap
> Adobe-GB1-5.cidmap
> Adobe-Identity-0.cidmap
> Adobe-Japan1-6.cidmap
> Adobe-Japan2-0.cidmap
> Adobe-Korea1-2.cidmap
> mv: cannot stat '/tmp/slackrepo/etr/slackrepo.VutkkO/build_fontforge/package-fontforge/usr/share/doc/fontforge/': No such file or directory
> graphics/fontforge: fontforge.SlackBuild failed (status 1) 18:00:35
> Unmounting chroot ...
> :-( graphics/fontforge FAILED )-:
>
> This new line added to the SlackBuild is the culprit:
>
> mv $PKG/usr/share/doc/$PRGNAM/ $PKG/usr/doc/$PRGNAM-$VERSION
>
> I commented it out and the build succeeded, and as expected the resulting package does not contain /usr/share/doc.

Sorry for spamming the list... I see it's already fixed in git.  I really need to check first before mailing...

Erich

From slack at giand.it  Mon Apr 11 20:23:03 2022
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=)
Date: Mon, 11 Apr 2022 22:23:03 +0200
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
Message-ID: <de44bd7f-2b7c-f9a3-b163-b2d03e2604ca@giand.it>

Il 11/04/22 19:55, B. Watson ha scritto:
>
> I've been going through a lot of packages, looking for issues...
>
> How many of you have files named like these?
>
> $ ls -d /installpkg-*
> /installpkg-424f0b9b8dfa39116f400a1e28c81427/
> /installpkg-48c5f1121baf117bc8cd5cb81d4c315a/
> /installpkg-8ce33bb6875a083c1b82af332c9a1175/
> /installpkg-a6c16f0748bbc7f892dd56447a375fa6/
> /installpkg-ad84c0c457f72e604075589930b129de/
> /installpkg-c863767111eaaddfb8623271f76a6c8b/
> /installpkg-cd8a50cc9a20baff05436e5e21b3b89b/
> /installpkg-d9f3419d09ef5f9fe23a0a1a2c198b8d/
> /installpkg-e4b7c85746cc950dff947233cb978aaa/
> /installpkg-f850ef68bdfdb986ee187fd495acf84d/
>
> It turns out that SlackBuilds which put extra files in $PKG/install
> cause these 'turds' to be installed. The installpkg command creates
> these, with the contents of 'install/' in the package (meaning they
> contain slack-desc and doinst.sh, if it exists), but it doesn't
> remove them if they contain extra files, because it deletes/moves
> the slack-desck and doinst.sh, then uses rmdir to delete the
> /installpkg-<hash> directory.
>
> As an added bonus, any code in doinst.sh that expects to use a file
> in /install (e.g. freeimpi tries to use /install/conffiles), will fail
> because by the time doinst.sh runs, the directory has been renamed.
>
> I can and will fix the ones I know about, but everyone, you should
> check your builds to see if they do this.

I think this could be a singular issue in your system. I have built 
hudrends of different slackbuilds but no files like these exist (I 
searched in / and in /tmp/SBo). Sometimes I check and empty the 
directory but I never found files like these.


-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it
https://twitter.com/gian_d_gian

Slackware Linux... because it works!
*********************************************************


From erich.public at protonmail.com  Mon Apr 11 20:26:16 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Mon, 11 Apr 2022 20:26:16 +0000
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <de44bd7f-2b7c-f9a3-b163-b2d03e2604ca@giand.it>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
 <de44bd7f-2b7c-f9a3-b163-b2d03e2604ca@giand.it>
Message-ID: <qYJeKI7XgJ8Q-hbY_z9y8GGemukNJFqKH9FwOMuE1EMZC7hBGhqXMfqE3PzVCqCLfsQu49dK_7VQy1SXpARblsJxvGQT4sWeoRnYRqYIPNQ=@protonmail.com>

------- Original Message -------
On Monday, April 11th, 2022 at 3:23 PM, Giancarlo Dess? <slack at giand.it> wrote:


>
>
>
> Il 11/04/22 19:55, B. Watson ha scritto:
>
> > I've been going through a lot of packages, looking for issues...
> >
> > How many of you have files named like these?
> >
> > $ ls -d /installpkg-*
> > /installpkg-424f0b9b8dfa39116f400a1e28c81427/
> > /installpkg-48c5f1121baf117bc8cd5cb81d4c315a/
> > /installpkg-8ce33bb6875a083c1b82af332c9a1175/
> > /installpkg-a6c16f0748bbc7f892dd56447a375fa6/
> > /installpkg-ad84c0c457f72e604075589930b129de/
> > /installpkg-c863767111eaaddfb8623271f76a6c8b/
> > /installpkg-cd8a50cc9a20baff05436e5e21b3b89b/
> > /installpkg-d9f3419d09ef5f9fe23a0a1a2c198b8d/
> > /installpkg-e4b7c85746cc950dff947233cb978aaa/
> > /installpkg-f850ef68bdfdb986ee187fd495acf84d/
> >
> > It turns out that SlackBuilds which put extra files in $PKG/install
> > cause these 'turds' to be installed. The installpkg command creates
> > these, with the contents of 'install/' in the package (meaning they
> > contain slack-desc and doinst.sh, if it exists), but it doesn't
> > remove them if they contain extra files, because it deletes/moves
> > the slack-desck and doinst.sh, then uses rmdir to delete the
> > /installpkg-<hash> directory.
> >
> > As an added bonus, any code in doinst.sh that expects to use a file
> > in /install (e.g. freeimpi tries to use /install/conffiles), will fail
> > because by the time doinst.sh runs, the directory has been renamed.
> >
> > I can and will fix the ones I know about, but everyone, you should
> > check your builds to see if they do this.
>
>
> I think this could be a singular issue in your system. I have built
> hudrends of different slackbuilds but no files like these exist (I
> searched in / and in /tmp/SBo). Sometimes I check and empty the
> directory but I never found files like these.
>
>

It is (semi-) documented behavior of installpkg.  From /sbin/installpkg:

# Tue Apr 17 17:26:44 UTC 2018
# Quit with the funny business in /install. Note however that /install still
# isn't a safe directory to use in a package for anything other than package
# metadata. Other files placed there are going to be left on the system in
# /installpkg-$(mcookie). That could be worked around, but we'll wait until
# someone reports there is a need. The main reason to do this is that /install
# was a collision point if more than one copy of installpkg was running at
# once. With this change, the pkgtools are (more or less) thread-safe.

Erich

> --
> *********************************************************
> Giancarlo Dess?
> https://www.giand.it
> https://twitter.com/gian_d_gian
>
> Slackware Linux... because it works!
> *********************************************************
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/

From urchlay at slackware.uk  Mon Apr 11 22:24:40 2022
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 11 Apr 2022 18:24:40 -0400 (EDT)
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <de44bd7f-2b7c-f9a3-b163-b2d03e2604ca@giand.it>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
 <de44bd7f-2b7c-f9a3-b163-b2d03e2604ca@giand.it>
Message-ID: <58a79578-e5b-c659-424c-c0367312f07c@slackware.uk>


Sorry, this turned out to be longer than I expected. But I think it
covers the issue in enough detail that it's worth it...

On Mon, 11 Apr 2022, Giancarlo Dess? wrote:

> I think this could be a singular issue in your system. I have built 
> hudrends of different slackbuilds but no files like these exist (I 
> searched in / and in /tmp/SBo). Sometimes I check and empty the 
> directory but I never found files like these.

You wouldn't have seen this on Slackware 14.2 or earlier; it's caused
by a change to installpkg that happened in 2018 (so you might have
seen it on pre-15.0 -current, if you ran that).

It's happened on two different 15.0 systems here. It's not a problem
with my setup, it's a problem with a few specific SlackBuilds. So far,
I've discovered it in:

multimedia/l-smash
network/ipxnet
system/freeipmi

To see what I'm talking about, build and install one of these
packages. Don't take my word for it, try it.... note that I'm not
pointing fingers at anyone: Two of those are maintained by me, so I'd
have to point at myself with both hands.

The reason for asking about it on the mailing list is that I'm trying
to find any other SBo builds that have the same problem, that people
might have run into.

What these builds all have in common: they put extra files in
$PKG/install (besides slack-desc and doinst.sh). I've fixed them in my
git branch, so if you want to test them, do it before the next update.

There are comments in /sbin/installpkg that explain the situation.
Starting from line 64:

# Tue Apr 17 17:26:44 UTC 2018
# Quit with the funny business in /install. Note however that /install still
# isn't a safe directory to use in a package for anything other than package
# metadata. Other files placed there are going to be left on the system in
# /installpkg-$(mcookie). That could be worked around, but we'll wait until
# someone reports there is a need. The main reason to do this is that /install
# was a collision point if more than one copy of installpkg was running at
# once. With this change, the pkgtools are (more or less) thread-safe.

"Other files placed there" include the README from l-smash:
the script incorrectly installed it in $PKG/install instead of
$PKG/usr/doc/$PRGNAM-$VERSION.

You could also edit any slackbuild in the repo and add a command like
"touch $PKG/install/somefile" before the makepkg command, to see what
happens.

You can also duplicate the problem with a 'skeleton' slackware package:

   rm -rf /tmp/foo
   mkdir -p /tmp/foo/{usr/bin,install}
   cd /tmp/foo
   touch usr/bin/foo install/slack-desc install/bad.file
   makepkg -l y -c n /tmp/foo-0.0-noarch-1.tgz

...if you then say "installpkg /tmp/foo-0.0-noarch-1.tgz", followed by
"ls /", you'll see a /installpkg-<hash> directory has been created. If
you remove the package, that directory doesn't get removed. If you
install it again, another directory (with a different hash) will get
created.

If you re-run that set of commands, without the "install/bad.file"
in the touch command, you *won't* get a /installpkg-<blah> directory
after the package is installed. (installpkg will create such a
directory, but it will then remove it).

From urchlay at slackware.uk  Mon Apr 11 22:26:40 2022
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 11 Apr 2022 18:26:40 -0400 (EDT)
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <qYJeKI7XgJ8Q-hbY_z9y8GGemukNJFqKH9FwOMuE1EMZC7hBGhqXMfqE3PzVCqCLfsQu49dK_7VQy1SXpARblsJxvGQT4sWeoRnYRqYIPNQ=@protonmail.com>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
 <de44bd7f-2b7c-f9a3-b163-b2d03e2604ca@giand.it>
 <qYJeKI7XgJ8Q-hbY_z9y8GGemukNJFqKH9FwOMuE1EMZC7hBGhqXMfqE3PzVCqCLfsQu49dK_7VQy1SXpARblsJxvGQT4sWeoRnYRqYIPNQ=@protonmail.com>
Message-ID: <b76b4cd3-699-7335-611a-cadaffd5a059@slackware.uk>



On Mon, 11 Apr 2022, Erich Ritz via SlackBuilds-users wrote:

> It is (semi-) documented behavior of installpkg.  From /sbin/installpkg:
>
> # Tue Apr 17 17:26:44 UTC 2018
> # Quit with the funny business in /install. Note however that /install still
> # isn't a safe directory to use in a package for anything other than package
> # metadata. Other files placed there are going to be left on the system in
> # /installpkg-$(mcookie). That could be worked around, but we'll wait until
> # someone reports there is a need. The main reason to do this is that /install
> # was a collision point if more than one copy of installpkg was running at
> # once. With this change, the pkgtools are (more or less) thread-safe.

Right, I quoted the same thing in my 2nd email...

What I'm trying to do is find out which SBo build actually have this
problem. So far I know about 3 of them, I bet the're more.

From lists at osh.id.au  Mon Apr 11 23:48:03 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Tue, 12 Apr 2022 07:48:03 +0800
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
Message-ID: <9a4aaa5c-b091-405e-9a97-cf8464b19d75@www.fastmail.com>

On Tue, 12 Apr 2022, at 1:55 AM, B. Watson wrote:
> How many of you have files named like these?
>
> $ ls -d /installpkg-*

Weirdly, I had one /installpkg-* type directory, with some libebml content. However, when I remove/rebuild/install libebml, I don't get the directory being created again, so I don't know what happened there.

From ozan.turkyilmaz at gmail.com  Tue Apr 12 05:55:55 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Tue, 12 Apr 2022 08:55:55 +0300
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <9a4aaa5c-b091-405e-9a97-cf8464b19d75@www.fastmail.com>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
 <9a4aaa5c-b091-405e-9a97-cf8464b19d75@www.fastmail.com>
Message-ID: <6c16f544a58cbfa875c9891890a241d5fee133e6.camel@gmail.com>

Sal, 2022-04-12 tarihinde 07:48 +0800 saatinde, David O'Shaughnessy
yazd?:
> On Tue, 12 Apr 2022, at 1:55 AM, B. Watson wrote:
> > How many of you have files named like these?
> > 
> > $ ls -d /installpkg-*
> 
> Weirdly, I had one /installpkg-* type directory, with some libebml
> content. However, when I remove/rebuild/install libebml, I don't get
> the directory being created again, so I don't know what happened
> there.
> 

Do you remember what was inside? I just did a test build and install/
only had slack-desc and doinst.sh.

Regards,
Ozan

From urchlay at slackware.uk  Tue Apr 12 06:30:47 2022
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 12 Apr 2022 02:30:47 -0400 (EDT)
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <9a4aaa5c-b091-405e-9a97-cf8464b19d75@www.fastmail.com>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
 <9a4aaa5c-b091-405e-9a97-cf8464b19d75@www.fastmail.com>
Message-ID: <c6218ffb-abf-26f5-cd40-29822b6afd16@slackware.uk>



On Tue, 12 Apr 2022, David O'Shaughnessy wrote:

> On Tue, 12 Apr 2022, at 1:55 AM, B. Watson wrote:
>> How many of you have files named like these?
>>
>> $ ls -d /installpkg-*
>
> Weirdly, I had one /installpkg-* type directory, with some libebml content. However, when I remove/rebuild/install libebml, I don't get the directory being created again, so I don't know what happened there.

Possibly an older version of libebml had the problem, and it's since
been fixed? I checked just now, the version of libebml in the repo now
is fine.

From gen-bch at useyouresp.org.uk  Tue Apr 12 08:39:37 2022
From: gen-bch at useyouresp.org.uk (Habs)
Date: Tue, 12 Apr 2022 09:39:37 +0100 (BST)
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <58a79578-e5b-c659-424c-c0367312f07c@slackware.uk>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
 <de44bd7f-2b7c-f9a3-b163-b2d03e2604ca@giand.it>
 <58a79578-e5b-c659-424c-c0367312f07c@slackware.uk>
Message-ID: <1psn356-s025-q9q-566r-s87p6981r1r7@hfrlbherfc.bet.hx>

On Mon, 11 Apr 2022, B. Watson wrote:

>
> Sorry, this turned out to be longer than I expected. But I think it
> covers the issue in enough detail that it's worth it...
>
> On Mon, 11 Apr 2022, Giancarlo Dess? wrote:
>
>> I think this could be a singular issue in your system. I have built 
>> hudrends of different slackbuilds but no files like these exist (I searched 
>> in / and in /tmp/SBo). Sometimes I check and empty the directory but I 
>> never found files like these.
>
> You wouldn't have seen this on Slackware 14.2 or earlier; it's caused
> by a change to installpkg that happened in 2018 (so you might have
> seen it on pre-15.0 -current, if you ran that).
>
> It's happened on two different 15.0 systems here. It's not a problem
> with my setup, it's a problem with a few specific SlackBuilds. So far,
> I've discovered it in:
>
> multimedia/l-smash
> network/ipxnet
> system/freeipmi
>

good day folks

finding all SlackBuild files (on the repo snap created by sbotools) and 
then some grotty line grep and sed stuff on each SlackBuild, reveals only 
those three builds mentioned above having anything other than slack-desc, 
doinst.sh or douninst.sh put in '$PKG/install'.

it was a basic attempt to get a rough picture on this issue reported, so 
some 'may have got through' the sift.

regards
Habs

grep pattern  '>$PKG/install/' or '> $PKG/install/'

sed patterm   '/slack-desc$\|doinst\.sh$\|douninst\.sh$/ d'


--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html

From slackbuilds at schoepfer.info  Tue Apr 12 08:54:24 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 12 Apr 2022 10:54:24 +0200
Subject: [Slackbuilds-users] Maintenance gummi
Message-ID: <38d7990ac7969ceb1c68df71d4e0b168@schoepfer.info>

Hi,

since Larry Hajali seems not be active anymore i'd like to take over 
maintenance for https://slackbuilds.org/repository/15.0/office/gummi/
Any objections?

Johannes

From urchlay at slackware.uk  Tue Apr 12 14:22:05 2022
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 12 Apr 2022 10:22:05 -0400 (EDT)
Subject: [Slackbuilds-users] Maintenance gummi
In-Reply-To: <38d7990ac7969ceb1c68df71d4e0b168@schoepfer.info>
References: <38d7990ac7969ceb1c68df71d4e0b168@schoepfer.info>
Message-ID: <7cb82eaf-ba6b-9c17-e137-ba358d76ef3@slackware.uk>



On Tue, 12 Apr 2022, Franzen via SlackBuilds-users wrote:

> Hi,
>
> since Larry Hajali seems not be active anymore i'd like to take over 
> maintenance for https://slackbuilds.org/repository/15.0/office/gummi/
> Any objections?

Have you tried to contact Larry? His last activity was April 2021,
which isn't *that* long ago...

From urchlay at slackware.uk  Tue Apr 12 14:27:07 2022
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 12 Apr 2022 10:27:07 -0400 (EDT)
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <1psn356-s025-q9q-566r-s87p6981r1r7@hfrlbherfc.bet.hx>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
 <de44bd7f-2b7c-f9a3-b163-b2d03e2604ca@giand.it>
 <58a79578-e5b-c659-424c-c0367312f07c@slackware.uk>
 <1psn356-s025-q9q-566r-s87p6981r1r7@hfrlbherfc.bet.hx>
Message-ID: <b6d53458-3c61-b24f-cb2f-7f9dec1647b@slackware.uk>



On Tue, 12 Apr 2022, Habs wrote:

>
> finding all SlackBuild files (on the repo snap created by sbotools) and then 
> some grotty line grep and sed stuff on each SlackBuild, reveals only those 
> three builds mentioned above having anything other than slack-desc, doinst.sh 
> or douninst.sh put in '$PKG/install'.

I did some similar checking with grep myself, and got the same
results. So maybe it only ever was those 3.

From jebrhansen+SBo at gmail.com  Tue Apr 12 14:29:02 2022
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Tue, 12 Apr 2022 08:29:02 -0600
Subject: [Slackbuilds-users] Maintenance gummi
In-Reply-To: <7cb82eaf-ba6b-9c17-e137-ba358d76ef3@slackware.uk>
References: <38d7990ac7969ceb1c68df71d4e0b168@schoepfer.info>
 <7cb82eaf-ba6b-9c17-e137-ba358d76ef3@slackware.uk>
Message-ID: <CANi9qSt5ACt5iaQ9L8Y+tiG4Sjpgxuzr=RJV1bvAtDpOhyve=Q@mail.gmail.com>

On Tue, Apr 12, 2022, 8:22 AM B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Tue, 12 Apr 2022, Franzen via SlackBuilds-users wrote:
>
> > Hi,
> >
> > since Larry Hajali seems not be active anymore i'd like to take over
> > maintenance for https://slackbuilds.org/repository/15.0/office/gummi/
> > Any objections?
>
> Have you tried to contact Larry? His last activity was April 2021,
> which isn't *that* long ago...
>

I tried contacting him about a month ago to take over Kodi without a
response either.

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220412/7fd7fba0/attachment.htm>

From slack at giand.it  Tue Apr 12 15:56:18 2022
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=)
Date: Tue, 12 Apr 2022 17:56:18 +0200
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <58a79578-e5b-c659-424c-c0367312f07c@slackware.uk>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
 <de44bd7f-2b7c-f9a3-b163-b2d03e2604ca@giand.it>
 <58a79578-e5b-c659-424c-c0367312f07c@slackware.uk>
Message-ID: <fc66a21c-6508-1a95-0424-b846d9426c0e@giand.it>

Il 12/04/22 00:24, B. Watson ha scritto:
>
> Sorry, this turned out to be longer than I expected. But I think it
> covers the issue in enough detail that it's worth it...
>
> On Mon, 11 Apr 2022, Giancarlo Dess? wrote:
>
>> I think this could be a singular issue in your system. I have built 
>> hudrends of different slackbuilds but no files like these exist (I 
>> searched in / and in /tmp/SBo). Sometimes I check and empty the 
>> directory but I never found files like these.
>
> You wouldn't have seen this on Slackware 14.2 or earlier; it's caused
> by a change to installpkg that happened in 2018 (so you might have
> seen it on pre-15.0 -current, if you ran that).

[cut]

I'm afraid, you are right!

I tried l-smash just now and an "installpkg-..." directory appears 
including the README file.

I didn't know about this problem, I use current since several years, I 
don't know if this is important, but I never met this fact.


-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it
https://twitter.com/gian_d_gian

Slackware Linux... because it works!
*********************************************************


From arnaud.garcia-fernandez at laposte.net  Tue Apr 12 17:30:44 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Tue, 12 Apr 2022 19:30:44 +0200
Subject: [Slackbuilds-users] 
 =?utf-8?q?Contacting_Audrius_Ka=C5=BEukauska?= =?utf-8?q?s?=
In-Reply-To: <20220401135932.0c6da4bfd3eae11373a50b72@laposte.net>
References: <20220401135932.0c6da4bfd3eae11373a50b72@laposte.net>
Message-ID: <20220412193044.cd1a35311471122e0fbce23b@laposte.net>

> Hi!
> 
> 	I've tried contacting Audrius Ka?ukauskas 3 weeks ago, about his
> SlackBuilds, but received no answers.
> His last contribution was more than a year ago.
> 
> Does anyone know if he's still active and well ?
> 
> Else I my need to upgrade some of his packages (redis and hg-git, probably some
> containerd/runc related stuff too as I use them at work).
> 
> Thanks,
> 
> 	- Yth.

Hello fellow Slackers,

	seeing as I've still had answers neither from Audrius, nor from anybody
on the list with informations, I'll take over maintainance of some of his
SlackBuilds.
Namely :
 - dulwich: it is the python2 build, I already maintain python3-dulwich.
 - hg-git: doesn't work as it is, needs update to python3
 - pgbadger, pgsanity: if nobody wants them, I already maintain psycopg2.
 - redis: I use it, already updated at home, I'm ok with keeping it up-to-date.
 - graphviz: I use it too.
 - pypy, pypy3: python stuff, I already have so many, what's two or ten more ?
 - smem, iotop: why not ?
 - uwsgi: interesting, I'll look into it.


There are also a lot of container/docker related SlackBuilds there, some not very
up-to-date. If nobody wishes to care for them, I may step up in a few weeks, but
I'd be glad not to add too much stuff on my plate.
This concerns those SlackBuilds, at least :
 - python2-cached-property
 - python2-docker-pycreds
 - python2-docker
 - python2-dockerpty
 - python2-texttable
 - containerd
 - docker-cli
 - docker-compose
 - docker-machine-kvm
 - docker-machine
 - docker-proxy
 - docker
 - runc
 - tini
I have not checked whether the python2 packages exists in python3 version and
could be removed as requirements of docker related stuff, switching everything to
python3.


If all that's OK, I'll submit updates (for the first list only) this week.

Cheers :)

	- Yth / Arnaud.

From lists at osh.id.au  Wed Apr 13 02:40:07 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Wed, 13 Apr 2022 10:40:07 +0800
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <6c16f544a58cbfa875c9891890a241d5fee133e6.camel@gmail.com>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
 <9a4aaa5c-b091-405e-9a97-cf8464b19d75@www.fastmail.com>
 <6c16f544a58cbfa875c9891890a241d5fee133e6.camel@gmail.com>
Message-ID: <773abc44-b600-4371-b463-c392065a5e20@www.fastmail.com>

On Tue, 12 Apr 2022, at 1:55 PM, Ozan T?rky?lmaz wrote:
> Do you remember what was inside? I just did a test build and install/
> only had slack-desc and doinst.sh.

Unfortunately not, but "libebml" was in there somewhere.

On Tue, 12 Apr 2022, at 2:30 PM, B. Watson wrote:
> Possibly an older version of libebml had the problem, and it's since
> been fixed? I checked just now, the version of libebml in the repo now
> is fine.

Probably yeah, it definitely doesn't happen now.

From urchlay at slackware.uk  Wed Apr 13 04:57:04 2022
From: urchlay at slackware.uk (B. Watson)
Date: Wed, 13 Apr 2022 00:57:04 -0400 (EDT)
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <773abc44-b600-4371-b463-c392065a5e20@www.fastmail.com>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
 <9a4aaa5c-b091-405e-9a97-cf8464b19d75@www.fastmail.com>
 <6c16f544a58cbfa875c9891890a241d5fee133e6.camel@gmail.com>
 <773abc44-b600-4371-b463-c392065a5e20@www.fastmail.com>
Message-ID: <54497b5a-f297-d7f6-5cc7-144f2475bf4c@slackware.uk>



On Wed, 13 Apr 2022, David O'Shaughnessy wrote:

> Unfortunately not, but "libebml" was in there somewhere.

The other possibility: if installpkg gets interrupted with ^C, it
might leave the /installpkg-<blah> stuff lying around just because it
got killed before it could remove it.

Not sure if that can happen when installpkg runs out of disk space. In
general it doesn't really handle running out of space gracefully
though.

From lists at osh.id.au  Wed Apr 13 05:49:09 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Wed, 13 Apr 2022 13:49:09 +0800
Subject: [Slackbuilds-users] extra files in $PKG/install
In-Reply-To: <54497b5a-f297-d7f6-5cc7-144f2475bf4c@slackware.uk>
References: <3feca14c-391d-3d3e-7e1-fc93d785ace3@slackware.uk>
 <9a4aaa5c-b091-405e-9a97-cf8464b19d75@www.fastmail.com>
 <6c16f544a58cbfa875c9891890a241d5fee133e6.camel@gmail.com>
 <773abc44-b600-4371-b463-c392065a5e20@www.fastmail.com>
 <54497b5a-f297-d7f6-5cc7-144f2475bf4c@slackware.uk>
Message-ID: <27ed8b82-df4c-4425-a435-4ef2f3a987e5@www.fastmail.com>

On Wed, 13 Apr 2022, at 12:57 PM, B. Watson wrote:
> The other possibility: if installpkg gets interrupted with ^C, it
> might leave the /installpkg-<blah> stuff lying around just because it
> got killed before it could remove it.

This is it, I just tested it out, and ctrl-c fast enough during installpkg leaves the directory behind in /

From slackbuilds at schoepfer.info  Wed Apr 13 07:40:53 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Wed, 13 Apr 2022 09:40:53 +0200
Subject: [Slackbuilds-users] Maintenance gummi
In-Reply-To: <CANi9qSt5ACt5iaQ9L8Y+tiG4Sjpgxuzr=RJV1bvAtDpOhyve=Q@mail.gmail.com>
References: <38d7990ac7969ceb1c68df71d4e0b168@schoepfer.info>
 <7cb82eaf-ba6b-9c17-e137-ba358d76ef3@slackware.uk>
 <CANi9qSt5ACt5iaQ9L8Y+tiG4Sjpgxuzr=RJV1bvAtDpOhyve=Q@mail.gmail.com>
Message-ID: <6536cb2ec110f44d179d37ee483f51c9@schoepfer.info>

>>> since Larry Hajali seems not be active anymore i'd like to take
>> over
>>> maintenance for
>> https://slackbuilds.org/repository/15.0/office/gummi/
>>> Any objections?
>> 
>> Have you tried to contact Larry? His last activity was April 2021,
>> which isn't *that* long ago...
> 
> I tried contacting him about a month ago to take over Kodi without a
> response either.

I didn't try to contact him as Willy wrote some weeks ago on this 
list(if i remember correctly)
that Larry seems not active anymore.

He's in cc now, Larry may i take gummi?

Johannes

From mab974 at misouk.com  Wed Apr 13 18:59:49 2022
From: mab974 at misouk.com (Mab974)
Date: Wed, 13 Apr 2022 22:59:49 +0400
Subject: [Slackbuilds-users] perl-PDF-Builder build
In-Reply-To: <20220406215840.31d1b7fc56f9b1872ac55e14@misouk.com>
References: <20220406215840.31d1b7fc56f9b1872ac55e14@misouk.com>
Message-ID: <20220413225949.74339ce7e5000f0b72ac6d63@misouk.com>

Hi,

This error disappeared after the last update and I can not reproduce it.

So I?m going to take it as fixed.... 

Thank you for your positive vibes.

Regards,

Selon Mab974 via SlackBuilds-users <slackbuilds-users at slackbuilds.org> :
> Hello everyone,
> 
> On a clean and updated Slackware 15, following perl-template,
> 
> I can't build current 'perl-PDF-Builder' with sbopkg but the slackbuild
> works fine manually.
> 
> The problem is the different assignment of INSTALLDIRS in makefile.
> ('site' instead of 'vendor') 
> 
> Part of log is below ...
> 
> I can?t figure out what the problem is and how to fix it.
> Any help will be welcome
> 
> Regards,
> 
> -*- 
> Mab974 <mab974 at misouk.com>
> 

-*- 
Mab974 <mab974 at misouk.com>

From dpross1100 at msn.com  Wed Apr 13 19:45:17 2022
From: dpross1100 at msn.com (Daniel Prosser)
Date: Wed, 13 Apr 2022 15:45:17 -0400
Subject: [Slackbuilds-users] Hosting source tarballs
Message-ID: <SN6PR03MB353616D9D43D1383B468A7E3CCEC9@SN6PR03MB3536.namprd03.prod.outlook.com>

I would like to submit an update for one of my SlackBuilds, xflr5. The 
source code for this is only available via a per-request snapshot from 
the project's "Code" section on SourceForge, which can't be obtained by 
a direct link in a repeatable way. It's been awhile since I updated 
this, and I forgot how I uploaded a source tarball the last time. It 
looks like the current one is hosted on sbosrcarch. I also recall 
uploading things to an SBo source code repository on SourceForge in the 
past with ftp, but I can't remember the details of how that worked 
either. Can someone help me out?

Regards,

Dan


From willysr at slackbuilds.org  Wed Apr 13 23:01:35 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 14 Apr 2022 06:01:35 +0700
Subject: [Slackbuilds-users] Hosting source tarballs
In-Reply-To: <SN6PR03MB353616D9D43D1383B468A7E3CCEC9@SN6PR03MB3536.namprd03.prod.outlook.com>
References: <SN6PR03MB353616D9D43D1383B468A7E3CCEC9@SN6PR03MB3536.namprd03.prod.outlook.com>
Message-ID: <5c6f59f5-b9f9-857e-ee1c-fa35275364a3@slackbuilds.org>

> I would like to submit an update for one of my SlackBuilds, xflr5. The
> source code for this is only available via a per-request snapshot from
> the project's "Code" section on SourceForge, which can't be obtained by
> a direct link in a repeatable way. It's been awhile since I updated
> this, and I forgot how I uploaded a source tarball the last time. It
> looks like the current one is hosted on sbosrcarch. I also recall
> uploading things to an SBo source code repository on SourceForge in the
> past with ftp, but I can't remember the details of how that worked
> either. Can someone help me out?

Send me your SourceForge account (username) and i will add you to list
of members who can upload sources there


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220414/b3097e69/attachment.asc>

From dpross1100 at msn.com  Thu Apr 14 02:44:30 2022
From: dpross1100 at msn.com (Daniel Prosser)
Date: Wed, 13 Apr 2022 22:44:30 -0400
Subject: [Slackbuilds-users] Hosting source tarballs
In-Reply-To: <5c6f59f5-b9f9-857e-ee1c-fa35275364a3@slackbuilds.org>
References: <SN6PR03MB353616D9D43D1383B468A7E3CCEC9@SN6PR03MB3536.namprd03.prod.outlook.com>
 <5c6f59f5-b9f9-857e-ee1c-fa35275364a3@slackbuilds.org>
Message-ID: <BYAPR03MB352721A91D60E023FEDDD29ACCEF9@BYAPR03MB3527.namprd03.prod.outlook.com>

Hey Willy,

My username on SourceForge is montagdp. I think I may already have 
access to upload sources there, but I don't remember where or how.

Thanks,

Dan

On 4/13/22 19:01, Willy Sudiarto Raharjo wrote:
>> I would like to submit an update for one of my SlackBuilds, xflr5. The
>> source code for this is only available via a per-request snapshot from
>> the project's "Code" section on SourceForge, which can't be obtained by
>> a direct link in a repeatable way. It's been awhile since I updated
>> this, and I forgot how I uploaded a source tarball the last time. It
>> looks like the current one is hosted on sbosrcarch. I also recall
>> uploading things to an SBo source code repository on SourceForge in the
>> past with ftp, but I can't remember the details of how that worked
>> either. Can someone help me out?
> Send me your SourceForge account (username) and i will add you to list
> of members who can upload sources there
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From ozan.turkyilmaz at gmail.com  Thu Apr 14 11:22:23 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Thu, 14 Apr 2022 14:22:23 +0300
Subject: [Slackbuilds-users] doinst.sh question
Message-ID: <e9fd91bdd6548f820bd05655136e9c0814166a1a.camel@gmail.com>

Hello All,

I noticed a problem with doinst.sh files of my package (namely
lingweather). I checked the file it is generated fine and will create
the needed soft links however sometimes it won't create all the links.
I noticed when evolution-data-server didnt link to the libgweather
inside a test system (Thanks to Dave Woodfall for catching it). 

I am not sure what I really do wrong. I am attaching two doinst.sh
files: doinst.sh for the one included with the buildscript and
doinst.sh.package for the generated one. I don't see any errors while
installing the package on my machine. My test system gave the below
error doing installation:

Executing install script for libgweather-40.0-x86_64-1_SBo.tgz.
/bin/bash: line 11: syntax error: unexpected end of file

Regards,
Ozan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: doinst.sh
Type: application/x-shellscript
Size: 177 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220414/fd7e5457/attachment.bin>
-------------- next part --------------

if [ -e usr/share/glib-2.0/schemas ]; then
  if [ -x /usr/bin/glib-compile-schemas ]; then
    /usr/bin/glib-compile-schemas usr/share/glib-2.0/schemas >/dev/null 2>&1
  fi
if
( cd usr/lib64 ; rm -rf libgweather-3.so )
( cd usr/lib64 ; ln -sf libgweather-3.so.16 libgweather-3.so )
( cd usr/lib64 ; rm -rf libgweather-3.so.16 )
( cd usr/lib64 ; ln -sf libgweather-3.so.16.0.0 libgweather-3.so.16 )

From marav8 at free.fr  Thu Apr 14 11:30:18 2022
From: marav8 at free.fr (marav)
Date: Thu, 14 Apr 2022 13:30:18 +0200
Subject: [Slackbuilds-users] doinst.sh question
In-Reply-To: <e9fd91bdd6548f820bd05655136e9c0814166a1a.camel@gmail.com>
References: <e9fd91bdd6548f820bd05655136e9c0814166a1a.camel@gmail.com>
Message-ID: <e840e4bf-f2b1-7352-1f4f-8da4f306379b@free.fr>

Le 14/04/2022 ? 13:22, Ozan T?rky?lmaz a ?crit?:
> Hello All,
>
> I noticed a problem with doinst.sh files of my package (namely
> lingweather). I checked the file it is generated fine and will create
> the needed soft links however sometimes it won't create all the links.
> I noticed when evolution-data-server didnt link to the libgweather
> inside a test system (Thanks to Dave Woodfall for catching it).
>
> I am not sure what I really do wrong. I am attaching two doinst.sh
> files: doinst.sh for the one included with the buildscript and
> doinst.sh.package for the generated one. I don't see any errors while
> installing the package on my machine. My test system gave the below
> error doing installation:
>
> Executing install script for libgweather-40.0-x86_64-1_SBo.tgz.
> /bin/bash: line 11: syntax error: unexpected end of file
>
> Regards,
> Ozan
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ -https://slackbuilds.org/faq/
>
typo at the end of the file


+if [ -e usr/share/glib-2.0/schemas ]; then
+ if [ -x /usr/bin/glib-compile-schemas ]; then
+ /usr/bin/glib-compile-schemas usr/share/glib-2.0/schemas >/dev/null 2>&1
+ fi
*+if*

must be "fi"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220414/706eb217/attachment.htm>

From ozan.turkyilmaz at gmail.com  Thu Apr 14 11:37:38 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Thu, 14 Apr 2022 14:37:38 +0300
Subject: [Slackbuilds-users] doinst.sh question
In-Reply-To: <e840e4bf-f2b1-7352-1f4f-8da4f306379b@free.fr>
References: <e9fd91bdd6548f820bd05655136e9c0814166a1a.camel@gmail.com>
 <e840e4bf-f2b1-7352-1f4f-8da4f306379b@free.fr>
Message-ID: <ac1aee52ee0b4e9f6403451c94c80ac6c1c36efd.camel@gmail.com>

Pr?, 2022-04-14 tarihinde 13:30 +0200 saatinde, marav yazd?:
> Le 14/04/2022 ? 13:22, Ozan T?rky?lmaz a ?crit?:
> > 
> typo at the end of the file
> 
> +if [ -e usr/share/glib-2.0/schemas ]; then
> + if [ -x /usr/bin/glib-compile-schemas ]; then
> + /usr/bin/glib-compile-schemas usr/share/glib-2.0/schemas >/dev/null
> 2>&1
> + fi
> +if
> 
> must be "fi" 

Damn it. That could explain why it works sometimes and not other times.

Regards,
Ozan

From willysr at slackbuilds.org  Thu Apr 14 13:25:35 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 14 Apr 2022 20:25:35 +0700
Subject: [Slackbuilds-users] Hosting source tarballs
In-Reply-To: <BYAPR03MB352721A91D60E023FEDDD29ACCEF9@BYAPR03MB3527.namprd03.prod.outlook.com>
References: <SN6PR03MB353616D9D43D1383B468A7E3CCEC9@SN6PR03MB3536.namprd03.prod.outlook.com>
 <5c6f59f5-b9f9-857e-ee1c-fa35275364a3@slackbuilds.org>
 <BYAPR03MB352721A91D60E023FEDDD29ACCEF9@BYAPR03MB3527.namprd03.prod.outlook.com>
Message-ID: <676b6a24-a9e5-4c8b-a052-bf22d91736ec@slackbuilds.org>

> My username on SourceForge is montagdp. I think I may already have
> access to upload sources there, but I don't remember where or how.

Then you can connect to web.sourceforge.net using your SF account and
you can create directory according to your script name and upload it there


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220414/a63fab07/attachment.asc>

From dpross1100 at msn.com  Thu Apr 14 14:15:33 2022
From: dpross1100 at msn.com (Daniel Prosser)
Date: Thu, 14 Apr 2022 10:15:33 -0400
Subject: [Slackbuilds-users] Hosting source tarballs
In-Reply-To: <676b6a24-a9e5-4c8b-a052-bf22d91736ec@slackbuilds.org>
References: <SN6PR03MB353616D9D43D1383B468A7E3CCEC9@SN6PR03MB3536.namprd03.prod.outlook.com>
 <5c6f59f5-b9f9-857e-ee1c-fa35275364a3@slackbuilds.org>
 <BYAPR03MB352721A91D60E023FEDDD29ACCEF9@BYAPR03MB3527.namprd03.prod.outlook.com>
 <676b6a24-a9e5-4c8b-a052-bf22d91736ec@slackbuilds.org>
Message-ID: <SN6PR03MB35363078265D6B761D37EA47CCEF9@SN6PR03MB3536.namprd03.prod.outlook.com>

Willy,

Thanks. That wasn't really clear to me, but I remembered how to upload 
to slackbuildsdirectlinks on SourceForge. For anyone wondering:

 1. You need a SourceForge account and Willy to give you appropriate
    permissions to the slackbuildsdirectlinks project.
 2. Use sftp to connect to <username>@frs.sourceforge.net
 3. Navigate to /home/frs/project/slackbuildsdirectlinks and create a
    directory there for your SlackBuild if it doesn't already exist.
 4. Upload the file.

Note: mc can handle connecting and uploading the file with SFTP.

Dan

On 4/14/22 09:25, Willy Sudiarto Raharjo wrote:
>> My username on SourceForge is montagdp. I think I may already have
>> access to upload sources there, but I don't remember where or how.
> Then you can connect to web.sourceforge.net using your SF account and
> you can create directory according to your script name and upload it there
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ -https://slackbuilds.org/faq/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220414/6212abbe/attachment-0001.htm>

From richard at aaazen.com  Thu Apr 14 16:03:40 2022
From: richard at aaazen.com (Richard Narron)
Date: Thu, 14 Apr 2022 09:03:40 -0700 (PDT)
Subject: [Slackbuilds-users] Pleae remove THE.tar.gz from pending list
Message-ID: <e1fea5f0-684b-6153-d650-c3e5c12e41e@aaazen.com>

My checksum does not seem to be working...

Can someone please remove the THE.tar.gz from the pending list or
send me the correct checksum?

I have a newer better build of THE to submit.

Richard Narron


From dave at slackbuilds.org  Thu Apr 14 21:33:12 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Thu, 14 Apr 2022 22:33:12 +0100
Subject: [Slackbuilds-users] Pleae remove THE.tar.gz from pending list
In-Reply-To: <e1fea5f0-684b-6153-d650-c3e5c12e41e@aaazen.com>
References: <e1fea5f0-684b-6153-d650-c3e5c12e41e@aaazen.com>
Message-ID: <YliTGEBnQ9hmGevj@localhost>

On 14/04/22 09:03,
Richard Narron <richard at aaazen.com> put forth the proposition:
> My checksum does not seem to be working...
> Can someone please remove the THE.tar.gz from the pending list or
> send me the correct checksum?
> I have a newer better build of THE to submit.
> Richard Narron

Try it now.
--
Dave

From ozan.turkyilmaz at gmail.com  Fri Apr 15 06:10:08 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Fri, 15 Apr 2022 09:10:08 +0300
Subject: [Slackbuilds-users] libgweather
Message-ID: <1707084695d4cdd031fbae35b9b776603c40f0cc.camel@gmail.com>

Hello All,

Can of the admins fix the below problem?
doinst.sh file should be like below: (Last line was if and it should be
fi)
if [ -e usr/share/glib-2.0/schemas ]; then
  if [ -x /usr/bin/glib-compile-schemas ]; then
    /usr/bin/glib-compile-schemas usr/share/glib-2.0/schemas >/dev/null
2>&1
  fi
fi

Regards,
Ozan

From dave at slackbuilds.org  Fri Apr 15 11:41:39 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Fri, 15 Apr 2022 12:41:39 +0100
Subject: [Slackbuilds-users] libgweather
In-Reply-To: <1707084695d4cdd031fbae35b9b776603c40f0cc.camel@gmail.com>
References: <1707084695d4cdd031fbae35b9b776603c40f0cc.camel@gmail.com>
Message-ID: <YllZ89GFf7ZH0b2H@localhost>

On 15/04/22 09:10,
Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com> put forth the proposition:
> Hello All,
> Can of the admins fix the below problem?
> doinst.sh file should be like below: (Last line was if and it should be
> fi)
> if [ -e usr/share/glib-2.0/schemas ]; then
>   if [ -x /usr/bin/glib-compile-schemas ]; then
>     /usr/bin/glib-compile-schemas usr/share/glib-2.0/schemas >/dev/null
> 2>&1
>   fi
> fi
> Regards,
> Ozan

Done.

--
Dave

From ozan.turkyilmaz at gmail.com  Fri Apr 15 14:30:20 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Fri, 15 Apr 2022 17:30:20 +0300
Subject: [Slackbuilds-users] evolution-data-server
Message-ID: <5b63fdc6e72b7a83b5bd70c4f05d2828625bae83.camel@gmail.com>

Hello All,

I checked but evolution-data-server does not show up in pending or
approved yet the submission form complains about it being in the
pending.

Regards,
Ozan 

From dave at slackbuilds.org  Fri Apr 15 15:55:31 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Fri, 15 Apr 2022 16:55:31 +0100
Subject: [Slackbuilds-users] evolution-data-server
In-Reply-To: <5b63fdc6e72b7a83b5bd70c4f05d2828625bae83.camel@gmail.com>
References: <5b63fdc6e72b7a83b5bd70c4f05d2828625bae83.camel@gmail.com>
Message-ID: <YlmVc+hS+Wap+xeO@localhost>

On 15/04/22 17:30,
Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com> put forth the proposition:
> Hello All,
> I checked but evolution-data-server does not show up in pending or
> approved yet the submission form complains about it being in the
> pending.
> Regards,
> Ozan

Please try now.

--
Dave

From phalange at komputermatrix.com  Fri Apr 15 20:27:57 2022
From: phalange at komputermatrix.com (Andrew Payne)
Date: Fri, 15 Apr 2022 16:27:57 -0400
Subject: [Slackbuilds-users] Admins - Question about Brave browser
In-Reply-To: <c4f437c5-19fb-7318-cf35-e6f9895699b6@gmail.com>
References: <CAFy1yb3N6sZnVjJNevTwFqDmpu0M+4P4ioc+bLMjxp5ZvOy4oQ@mail.gmail.com>
 <c4f437c5-19fb-7318-cf35-e6f9895699b6@gmail.com>
Message-ID: <d17bdddebdb01459db8ff76abc5d5e3b.squirrel@email.fatcow.com>


I'll pose this to the admins.

I would be happy to add this to the readme:

This slackbuild will adjust MIME settings for Brave. If you
wish to retain your current MIME settings, you can remove:

if [ -x /usr/bin/update-mime-database ]; then
    /usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
fi

from the doinst.sh file before building.

++

OR pull the MIME lines out of doinst.sh altogether.

Thoughts?


>
>
> -------- Forwarded Message --------
> Subject: 	[Slackbuilds-users] Question about Brave browser
> Date: 	Thu, 24 Mar 2022 10:54:05 -0600
> From: 	Luveh Keraph <1.41421 at gmail.com>
> Reply-To: 	SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
> To: 	SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
>
>
>
> I have installed the Brave browser in my 15.0 system using the
> Slackbuilds software for the purpose. I noticed that, after the
> installation is completed, some MIME handling settings are silently
> changed:
>
>  ?? ?? $ xdg-mime query default x-scheme-handler/http
>  ?? ?? brave-browser.desktop
>
>  ?? ?? $ xdg-mime query default x-scheme-handler/https
>  ?? ?? brave-browser.desktop
>
> Before installing Brave, the output of these commands was, in my case,
> chromium.desktop. The default browser setting remains unchanged though:
>
>  ?? ?? $ xdg-settings ??get default-web-browser
>  ?? ?? ??chromium.desktop
>
> The above changes imply that when clicking on a link embedded in an
> email in Thunderbird, the Brave browser will be launched,??instead of
> whatever was the default before - Chromium, in my case.?? This is OK if
> you want to use the Brave browser for that purpose. It is, however, a
> bit annoying??that the changes are carried out under the wraps and
> without asking the person in charge of the installation of this browser
> whether such an action is what one wants to do - installing a browser
> does not necessarily mean that it is meant to become the default browser
> for MIME data handling.
>
> It is easy enough to restore the MIME settings to what they were - in my
> case I would do
>
>  ?? ?? $ xdg-mime default chromium.desktop x-scheme-handler/http
>  ?? ?? $ xdg-mime default chromium.desktop x-scheme-handler/https
>
> However, it would be nice if the installation software were not??to
> change the MIME settings silently, or, at the very least, for the
> documentation in the Slackbuilds installer to warn about this action and
> explain how to revert it.
>
> Looking into the files in the Slackbuilds installation software it would
> seem that doinst.sh has something to do with all this, but being totally
> ignorant about such issues, I wouldn't know - the xdg-mime recipes that
> I mentioned I got from a network search, they work for me, and that's
> all I know about them.



From dave at slackbuilds.org  Fri Apr 15 21:15:17 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Fri, 15 Apr 2022 22:15:17 +0100
Subject: [Slackbuilds-users] Admins - Question about Brave browser
In-Reply-To: <d17bdddebdb01459db8ff76abc5d5e3b.squirrel@email.fatcow.com>
References: <CAFy1yb3N6sZnVjJNevTwFqDmpu0M+4P4ioc+bLMjxp5ZvOy4oQ@mail.gmail.com>
 <c4f437c5-19fb-7318-cf35-e6f9895699b6@gmail.com>
 <d17bdddebdb01459db8ff76abc5d5e3b.squirrel@email.fatcow.com>
Message-ID: <YlngZdgpOagvHXO7@localhost>

On 15/04/22 16:27,
Andrew Payne <phalange at komputermatrix.com> put forth the proposition:
> I'll pose this to the admins.
> I would be happy to add this to the readme:
> This slackbuild will adjust MIME settings for Brave. If you
> wish to retain your current MIME settings, you can remove:
> if [ -x /usr/bin/update-mime-database ]; then
>     /usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
> fi
> from the doinst.sh file before building.
> ++
> OR pull the MIME lines out of doinst.sh altogether.
> Thoughts?
> >
> >
> > -------- Forwarded Message --------
> > Subject: 	[Slackbuilds-users] Question about Brave browser
> > Date: 	Thu, 24 Mar 2022 10:54:05 -0600
> > From: 	Luveh Keraph <1.41421 at gmail.com>
> > Reply-To: 	SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
> > To: 	SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
> >
> >
> >
> > I have installed the Brave browser in my 15.0 system using the
> > Slackbuilds software for the purpose. I noticed that, after the
> > installation is completed, some MIME handling settings are silently
> > changed:
> >
> >  ?? ?? $ xdg-mime query default x-scheme-handler/http
> >  ?? ?? brave-browser.desktop
> >
> >  ?? ?? $ xdg-mime query default x-scheme-handler/https
> >  ?? ?? brave-browser.desktop
> >
> > Before installing Brave, the output of these commands was, in my case,
> > chromium.desktop. The default browser setting remains unchanged though:
> >
> >  ?? ?? $ xdg-settings ??get default-web-browser
> >  ?? ?? ??chromium.desktop
> >
> > The above changes imply that when clicking on a link embedded in an
> > email in Thunderbird, the Brave browser will be launched,??instead of
> > whatever was the default before - Chromium, in my case.?? This is OK if
> > you want to use the Brave browser for that purpose. It is, however, a
> > bit annoying??that the changes are carried out under the wraps and
> > without asking the person in charge of the installation of this browser
> > whether such an action is what one wants to do - installing a browser
> > does not necessarily mean that it is meant to become the default browser
> > for MIME data handling.
> >
> > It is easy enough to restore the MIME settings to what they were - in my
> > case I would do
> >
> >  ?? ?? $ xdg-mime default chromium.desktop x-scheme-handler/http
> >  ?? ?? $ xdg-mime default chromium.desktop x-scheme-handler/https
> >
> > However, it would be nice if the installation software were not??to
> > change the MIME settings silently, or, at the very least, for the
> > documentation in the Slackbuilds installer to warn about this action and
> > explain how to revert it.
> >
> > Looking into the files in the Slackbuilds installation software it would
> > seem that doinst.sh has something to do with all this, but being totally
> > ignorant about such issues, I wouldn't know - the xdg-mime recipes that
> > I mentioned I got from a network search, they work for me, and that's
> > all I know about them.

You could make it optional and add something like the following to
the slackbuild:

if [ "${BRAVE_MIME:-yes}" = "yes" ]; then
  echo '
if [ -x /usr/bin/update-mime-database ]; then
  /usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
fi' >> doinst.sh
fi

to default to yes, or Change the first line to:

if [ "${BRAVE_MIME:-no}" = "yes" ]; then

to default to no.

--
Dave

From phalange at komputermatrix.com  Fri Apr 15 21:31:18 2022
From: phalange at komputermatrix.com (Andrew Payne)
Date: Fri, 15 Apr 2022 17:31:18 -0400
Subject: [Slackbuilds-users] Admins - Question about Brave browser
In-Reply-To: <YlngZdgpOagvHXO7@localhost>
References: <CAFy1yb3N6sZnVjJNevTwFqDmpu0M+4P4ioc+bLMjxp5ZvOy4oQ@mail.gmail.com>
 <c4f437c5-19fb-7318-cf35-e6f9895699b6@gmail.com>
 <d17bdddebdb01459db8ff76abc5d5e3b.squirrel@email.fatcow.com>
 <YlngZdgpOagvHXO7@localhost>
Message-ID: <c9a674255ff3db0d3a7ce7ce56c2233d.squirrel@email.fatcow.com>

> On 15/04/22 16:27,
> Andrew Payne <phalange at komputermatrix.com> put forth the proposition:
>> I'll pose this to the admins.
>> I would be happy to add this to the readme:
>> This slackbuild will adjust MIME settings for Brave. If you
>> wish to retain your current MIME settings, you can remove:
>> if [ -x /usr/bin/update-mime-database ]; then
>>     /usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
>> fi
>> from the doinst.sh file before building.
>> ++
>> OR pull the MIME lines out of doinst.sh altogether.
>> Thoughts?
>> >
>> >
>> > -------- Forwarded Message --------
>> > Subject: 	[Slackbuilds-users] Question about Brave browser
>> > Date: 	Thu, 24 Mar 2022 10:54:05 -0600
>> > From: 	Luveh Keraph <1.41421 at gmail.com>
>> > Reply-To: 	SlackBuilds.org Users List
>> <slackbuilds-users at slackbuilds.org>
>> > To: 	SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
>> >
>> >
>> >
>> > I have installed the Brave browser in my 15.0 system using the
>> > Slackbuilds software for the purpose. I noticed that, after the
>> > installation is completed, some MIME handling settings are silently
>> > changed:
>> >
>> >  ???? ???? $ xdg-mime query default x-scheme-handler/http
>> >  ???? ???? brave-browser.desktop
>> >
>> >  ???? ???? $ xdg-mime query default x-scheme-handler/https
>> >  ???? ???? brave-browser.desktop
>> >
>> > Before installing Brave, the output of these commands was, in my case,
>> > chromium.desktop. The default browser setting remains unchanged
>> though:
>> >
>> >  ???? ???? $ xdg-settings ????get default-web-browser
>> >  ???? ???? ????chromium.desktop
>> >
>> > The above changes imply that when clicking on a link embedded in an
>> > email in Thunderbird, the Brave browser will be launched,????instead
>> of
>> > whatever was the default before - Chromium, in my case.???? This is OK
>> if
>> > you want to use the Brave browser for that purpose. It is, however, a
>> > bit annoying????that the changes are carried out under the wraps and
>> > without asking the person in charge of the installation of this
>> browser
>> > whether such an action is what one wants to do - installing a browser
>> > does not necessarily mean that it is meant to become the default
>> browser
>> > for MIME data handling.
>> >
>> > It is easy enough to restore the MIME settings to what they were - in
>> my
>> > case I would do
>> >
>> >  ???? ???? $ xdg-mime default chromium.desktop x-scheme-handler/http
>> >  ???? ???? $ xdg-mime default chromium.desktop x-scheme-handler/https
>> >
>> > However, it would be nice if the installation software were not????to
>> > change the MIME settings silently, or, at the very least, for the
>> > documentation in the Slackbuilds installer to warn about this action
>> and
>> > explain how to revert it.
>> >
>> > Looking into the files in the Slackbuilds installation software it
>> would
>> > seem that doinst.sh has something to do with all this, but being
>> totally
>> > ignorant about such issues, I wouldn't know - the xdg-mime recipes
>> that
>> > I mentioned I got from a network search, they work for me, and that's
>> > all I know about them.
>
> You could make it optional and add something like the following to
> the slackbuild:
>
> if [ "${BRAVE_MIME:-yes}" = "yes" ]; then
>   echo '
> if [ -x /usr/bin/update-mime-database ]; then
>   /usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
> fi' >> doinst.sh
> fi
>
> to default to yes, or Change the first line to:
>
> if [ "${BRAVE_MIME:-no}" = "yes" ]; then
>
> to default to no.
>
> --
> Dave
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

Thanks Dave, I'll do that.


From urchlay at slackware.uk  Fri Apr 15 21:54:56 2022
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 15 Apr 2022 17:54:56 -0400 (EDT)
Subject: [Slackbuilds-users] Admins - Question about Brave browser
In-Reply-To: <d17bdddebdb01459db8ff76abc5d5e3b.squirrel@email.fatcow.com>
References: <CAFy1yb3N6sZnVjJNevTwFqDmpu0M+4P4ioc+bLMjxp5ZvOy4oQ@mail.gmail.com>
 <c4f437c5-19fb-7318-cf35-e6f9895699b6@gmail.com>
 <d17bdddebdb01459db8ff76abc5d5e3b.squirrel@email.fatcow.com>
Message-ID: <43206d92-c4b1-533b-8128-7df6e231eb80@slackware.uk>



On Fri, 15 Apr 2022, Andrew Payne wrote:

> This slackbuild will adjust MIME settings for Brave. If you
> wish to retain your current MIME settings, you can remove:
>
> if [ -x /usr/bin/update-mime-database ]; then
>    /usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
> fi
>
> from the doinst.sh file before building.
>
> ++
>
> OR pull the MIME lines out of doinst.sh altogether.

You should remove the update-mime-database lines from the doinst.sh,
since they don't do anything anyway, other than waste a bit of time.
update-mime-database doesn't do what you thought it did...

Explanation distilled from 'man update-mime-database' and the
freedesktop shared mime-info specification:

https://specifications.freedesktop.org/shared-mime-info-spec/shared-mime-info-spec-0.21.html

Basically, the mime database in /usr/share/mime defines MIME types
like image/png or text/plain. It doesn't have anything to do with user
preferences (your doinst.sh won't make Brave the default browser)...
update-mime-database just reads the XML files in /usr/share/mime
and creates a /usr/share/mime/mime.cache file that's faster for
applications to use than it would be if they had to parse the XML
files every time.

Looking at the brave-browser package, there's nothing in
$PKG/usr/share/mime anyway, so update-mime-database won't actually
change anything when it runs. It will look at the XML files in
/usr/share/mime, and create a new /usr/share/mime/mime.cache... which
will be identical to the old one because no XML files get added,
deleted, or modified when you install the package.

Try this, on a system without brave-browser installed:

# rm -rf /usr/share/mime/mime.cache  # yes, it's OK to do this
# update-mime-database /usr/share/mime
# md5sum /usr/share/mime/mime.cache

...install your brave-browser package, with the update-mime-database
lines in the doinst.sh, then:

# md5sum /usr/share/mime/mime.cache

The md5sum should be identical to what it was before you installed the
package. Meaning, installing the package didn't modify the cache.

From urchlay at slackware.uk  Fri Apr 15 21:58:11 2022
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 15 Apr 2022 17:58:11 -0400 (EDT)
Subject: [Slackbuilds-users] Admins - Question about Brave browser
In-Reply-To: <c9a674255ff3db0d3a7ce7ce56c2233d.squirrel@email.fatcow.com>
References: <CAFy1yb3N6sZnVjJNevTwFqDmpu0M+4P4ioc+bLMjxp5ZvOy4oQ@mail.gmail.com>
 <c4f437c5-19fb-7318-cf35-e6f9895699b6@gmail.com>
 <d17bdddebdb01459db8ff76abc5d5e3b.squirrel@email.fatcow.com>
 <YlngZdgpOagvHXO7@localhost>
 <c9a674255ff3db0d3a7ce7ce56c2233d.squirrel@email.fatcow.com>
Message-ID: <11a68620-186b-3cc6-1c7f-e68912aa3a65@slackware.uk>



On Fri, 15 Apr 2022, Andrew Payne wrote:

>> You could make it optional and add something like the following to
>> the slackbuild:
>>
>> if [ "${BRAVE_MIME:-yes}" = "yes" ]; then
>>   echo '
>> if [ -x /usr/bin/update-mime-database ]; then
>>   /usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
>> fi' >> doinst.sh
>> fi
> Thanks Dave, I'll do that.

Please, no. This is extra work and complexity for something that
doesn't *do* anything at all (see my previous message).

Adding this won't hurt the SlackBuild (it will still work), but it
will act as a red herring, a thing that will confuse users and cause
them to think it's somehow important, and waste their time trying to
decide what option to choose.

In reality both options are the same: nothing happens to
/usr/share/mime/mime.cache at all, either way.

From dave at slackbuilds.org  Fri Apr 15 22:05:21 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Fri, 15 Apr 2022 23:05:21 +0100
Subject: [Slackbuilds-users] Admins - Question about Brave browser
In-Reply-To: <11a68620-186b-3cc6-1c7f-e68912aa3a65@slackware.uk>
References: <CAFy1yb3N6sZnVjJNevTwFqDmpu0M+4P4ioc+bLMjxp5ZvOy4oQ@mail.gmail.com>
 <c4f437c5-19fb-7318-cf35-e6f9895699b6@gmail.com>
 <d17bdddebdb01459db8ff76abc5d5e3b.squirrel@email.fatcow.com>
 <YlngZdgpOagvHXO7@localhost>
 <c9a674255ff3db0d3a7ce7ce56c2233d.squirrel@email.fatcow.com>
 <11a68620-186b-3cc6-1c7f-e68912aa3a65@slackware.uk>
Message-ID: <YlnsIX91UFM0ya85@localhost>

On 15/04/22 17:58,
B. Watson <urchlay at slackware.uk> put forth the proposition:
> Please, no. This is extra work and complexity for something that
> doesn't *do* anything at all (see my previous message).
> Adding this won't hurt the SlackBuild (it will still work), but it
> will act as a red herring, a thing that will confuse users and cause
> them to think it's somehow important, and waste their time trying to
> decide what option to choose.
> In reality both options are the same: nothing happens to
> /usr/share/mime/mime.cache at all, either way.

Yes, on thinking about it again, the command will run the next time
something is installed that updates the cache anyway.

--
Dave

From dave at slackbuilds.org  Fri Apr 15 22:35:20 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Fri, 15 Apr 2022 23:35:20 +0100
Subject: [Slackbuilds-users] Admins - Question about Brave browser
In-Reply-To: <d17bdddebdb01459db8ff76abc5d5e3b.squirrel@email.fatcow.com>
References: <CAFy1yb3N6sZnVjJNevTwFqDmpu0M+4P4ioc+bLMjxp5ZvOy4oQ@mail.gmail.com>
 <c4f437c5-19fb-7318-cf35-e6f9895699b6@gmail.com>
 <d17bdddebdb01459db8ff76abc5d5e3b.squirrel@email.fatcow.com>
Message-ID: <YlnzKFedPGlLuA3b@localhost>

On 15/04/22 16:27,
Andrew Payne <phalange at komputermatrix.com> put forth the proposition:
> > -------- Forwarded Message --------
> > Subject: 	[Slackbuilds-users] Question about Brave browser
> > Date: 	Thu, 24 Mar 2022 10:54:05 -0600
> > From: 	Luveh Keraph <1.41421 at gmail.com>
> > Reply-To: 	SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
> > To: 	SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
> >
> >  ?? ?? $ xdg-mime query default x-scheme-handler/http
> >  ?? ?? brave-browser.desktop
> >
> >  ?? ?? $ xdg-mime query default x-scheme-handler/https
> >  ?? ?? brave-browser.desktop

I just installed brave-browser to see and the first time that I
started it a window popped up asking to make brave the default
browser, ticked yes by default, so I guess he missed that.

--
Dave

From willysr at slackbuilds.org  Sat Apr 16 03:37:31 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 16 Apr 2022 10:37:31 +0700
Subject: [Slackbuilds-users] Maintenance gummi
In-Reply-To: <6536cb2ec110f44d179d37ee483f51c9@schoepfer.info>
References: <38d7990ac7969ceb1c68df71d4e0b168@schoepfer.info>
 <7cb82eaf-ba6b-9c17-e137-ba358d76ef3@slackware.uk>
 <CANi9qSt5ACt5iaQ9L8Y+tiG4Sjpgxuzr=RJV1bvAtDpOhyve=Q@mail.gmail.com>
 <6536cb2ec110f44d179d37ee483f51c9@schoepfer.info>
Message-ID: <fde28bbd-f0d2-7af9-d096-f7906bf021ed@slackbuilds.org>

> I didn't try to contact him as Willy wrote some weeks ago on this
> list(if i remember correctly)
> that Larry seems not active anymore.
> 
> He's in cc now, Larry may i take gummi?

sure


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/34160af5/attachment.asc>

From willysr at slackbuilds.org  Sat Apr 16 05:48:22 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 16 Apr 2022 12:48:22 +0700
Subject: [Slackbuilds-users] Updates - 20220416.1
Message-ID: <f2e13dae-89a8-0fa3-0e69-d5ae6adb4d3f@slackbuilds.org>

Another reminder to new or existing maintainers: Please use the latest
version of the SlackBuild script and templates for your submissions. We
rejected a lot of submissions this week because the update reverted our
changes back. Also, keep monitoring https://slackbuilds.org/ready/ as we
might update your scripts if there's an issue, so you need to make the
same adjustment before submitting.

Please use sbo-maintainer-tools
(https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools) to
test your script before you submit it, either via github/gitlab or
submission form. It's the same tool we used to check your submissions.


Sat Apr 16 05:25:03 UTC 2022
academic/R: Updated for version 4.1.3.
academic/bcftools: Updted to version 1.15.1
academic/bibletime: Updated for version 3.0.2.
academic/openboard: Fix build for current.
academic/rpy2: Updated to version 3.5.0
academic/samtools: Updated to version 1.15.1
academic/sword-data-kjv: Updated for version 1.9.0_1.
academic/sword: Updated for version 1.9.0.
academic/xflr5: Updated for version 6.54.
academic/xiphos: Fix build.
audio/rplay: Fix /usr/include permissions.
audio/sayonara-player: Updated for version 1.7.0_stable3.
desktop/Matcha-gtk-theme: Added (flat design theme).
desktop/Matcha-gtk-theme: Fix Github URL.
desktop/Tela-icon-theme: Added (flat icon theme).
desktop/bemenu: Add missing scdoc dependency.
desktop/bottles: Added (easily manage wineprefix using environments)
desktop/flatpak: Updated for version 1.12.7.
desktop/sway: Added (wayland i3 clone)
desktop/xwallpaper: Added (X wallpaper utility).
development/THE: Updated for version 3.3RC8.
development/dotnet-runtime-3.1: Update for version 3.1.24.
development/dotnet-runtime-5.0: Update for version 5.0.16.
development/dotnet-runtime-6.0: Update for version 6.0.4.
development/dotnet-sdk-3.1: Update for version 3.1.418.
development/dotnet-sdk-5.0: Update for version 5.0.407.
development/dotnet-sdk-6.0: Update for version 6.0.202.
development/erlang-otp: Strip binaries.
development/fpc: Clean up /usr/bin dir.
development/github-cli: Updated for version 2.8.0
development/gnustep-base: Strip binaries.
development/google-go-lang: Updated for version 1.17.9.
development/gtest: Fix docs, shared lib perms.
development/hugo: Updated for version 0.97.0.
development/jupyter-ipykernel: Update for 6.13.0
development/jupyter_client: Update for 7.2.2
development/jupyterlab_pygments: Update for 0.2.0
development/kotlin: Updated for version 1.6.20.
development/lazarus: Fix PRINT_PACKAGE_NAME, doinst, docs, symlink.
development/micro: Fix installing doinst.sh.
development/mongodb-compass: Updated for version 1.31.1.
development/nodejs: Updated for version 17.9.0.
development/ocaml: Fix docs.
development/rr: Added (Record and Replay Framework).
development/rstudio-desktop: Fix github tarball handling.
development/rstudio-desktop: Use zulu-openjdk8.
development/vscode-bin: Updated for version 1.66.1.
games/ags: Strip binary.
games/devilutionx: Fix github tarball handling.
games/freeciv: updated for version 3.0.1
graphics/OpenVSP: Add missing dependency fltk.
graphics/fontforge: Fix doc location.
graphics/mangohud: Fix github tarball handling.
graphics/tuxpaint-stamps: Updated for version 2021.11.25.
libraries/PDCurses: Remove file libpdcurses-x11.pc.
libraries/QtUsb: Fix /usr/include permissions.
libraries/adns: Fix empty package.
libraries/aspnetcore-runtime-3.1: Update for version 3.1.24.
libraries/aspnetcore-runtime-5.0: Update for version 5.0.16.
libraries/aspnetcore-runtime-6.0: Update for version 6.0.4.
libraries/cogl: Added (3D Graphics API).
libraries/confuse: Fix docs.
libraries/cppzmq: Add missing Catch dependency.
libraries/htslib: Updted to version 1.15.1
libraries/iddawc: Updated for version 1.1.2.
libraries/lablgtk: Fix docs.
libraries/libaal: Fix docs.
libraries/libbonoboui: Fix doc, .desktop.
libraries/libchewing: /usr/share/info => /usr/info.
libraries/libcsv: Fix docs.
libraries/libfilezilla: Updated for version 0.37.1.
libraries/libgdata: Added (online services APIs access)
libraries/libgksu: Fix docs and .desktop.
libraries/libgnomecanvas: Fix docs.
libraries/libgweather: Added (weather library for GNOME)
libraries/libgweather: Fix doinst.sh typo.
libraries/libpaper: Updated for version 1.1.28build2.
libraries/qmltermwidget: Fix build on 32bit.
libraries/rhonabwy: Updated for version 1.1.4.
libraries/seatd: Fix alternative tarball name handling.
libraries/stormlib: Use correct github URL.
libraries/ulfius: Updated for version 2.7.9.
libraries/vcglib: Make noarch; put docs in doc dir.
libraries/wxGTK3: Install generated HTML docs, not source.
libraries/wxPython3: Fix doc and include permissions.
libraries/wxPython: Fix permissions and .desktop.
misc/cwiid: Fix /usr/include permissions.
misc/gnome-mime-data: Make noarch, fix docs.
misc/recode: Strip binaries.
multimedia/intel-gmmlib: Fix github tarball handling.
multimedia/intel-media-driver: Fix github tarball handling.
multimedia/intel-media-sdk: Fix github tarball handling.
multimedia/l-smash: Fix /installpkg-* mess.
multimedia/plexmediaserver: Updated for v 1.25.9.5721_965587f64.
multimedia/strawberry: Updated for version 1.0.4.
network/argus-clients: Fix /usr/include permissions.
network/avahi: No empty /run dir in package.
network/brave-browser: Updated for version 1.37.116.
network/clusterit: Fix ordering of info file entries.
network/cni-plugins: Updated for version 1.1.1.
network/dropbear: Don't overwrite /usr/bin/scp by default; fix docs.
network/element-desktop: Added (secure + independent communication).
network/filezilla: Updated for version 3.59.0.
network/franz: Updated for version 5.9.1.
network/haproxy: Updated for version 2.5.5.
network/ipxnet: Fix /installpkg-* mess.
network/nextcloud-desktop: Fix URL.
network/nordvpn: Fix ARCH handling.
network/prosody-mod-http-upload: Updated for version hg4906.
network/snownews: Added (feed reader).
network/tor-browser: Updated for version 11.0.10.
network/zabbix_agentd: Updated for version 6.0.3.
network/zabbix_java_gateway: Updated for version 6.0.3.
network/zabbix_proxy: Updated for version 6.0.3.
network/zabbix_server: Updated for version 6.0.3.
office/fop: Update README, symlink.
office/pandoc-bin: Updated for versoin 2.18.
perl/perl-Curses: Fix docs.
perl/perl-File-Slurp: Make noarch, fix docs.
perl/perl-Locale-Codes: Fix slack-desc to be valid.
python/click-log: Added (Python Module).
python/click-threading: Added (add multithreading).
python/debugpy: Fix MD5SUM.
python/doit: Updated for version 0.35.0.
python/dulwich: removed, unused and replaced by python3 version
python/foolscap: Fix DOWNLOAD/HOMEPAGE.
python/hg-git: updated for version 1.0.0, new maintainer
python/nest_asyncio: Update for 1.5.5
python/pdfarranger: Fix installing doinst.sh.
python/pygsl: Updated for version 2.3.2.
python/python-evdev: Update README.
python/python-prometheus_client: Update for 0.14.1
python/python-xkbcommon: Added (Python bindings for libxkbcommon)
python/python2-automat: Add missing python-m2r dependency.
python/python2-soupsieve: Fix docs.
python/python3-automat: Add missing python-m2r dependency.
python/python3-build: Added (Python module).
python/python3-pep517: Added (API to call PEP 517 hooks).
python/python3-pythran: Fix lib dir usage on 32bit.
python/python3-pyzmq: Updated for version 22.3.0
python/python3-soupsieve: Fix docs.
python/python3-twisted: Updated for version 22.4.0.
python/pywayland: Added (Python bindings for the libwayland library)
python/pywlroots: Added (Python binding to the wlroots library)
system/ccrypt: Fix docs.
system/cdemu-client: Fix docs.
system/cdemu-daemon: Fix docs.
system/cdrkit: Fix docs.
system/clamsmtp: Fix docs.
system/cnijfilter2: Strip binaries.
system/conky: Fix doinst.sh.
system/courier-prime: Fix docs.
system/cpu-g: Fix permissions.
system/crashplan: Fix .desktop, respect environment ARCH.
system/crmsh: Fix docs.
system/crunch: Fix permissions.
system/csh: Fix doinst.sh.
system/culmus: Fix ARCH, docs.
system/curlftpfs: Fix docs.
system/cutecom: Fix build.
system/d-feet: Fix doinst.sh, symlinks.
system/dar: Fix docs.
system/ddrescueview: Fix man page path.
system/docker-cli: Strip binary.
system/docker-machine-kvm: Strip binary.
system/docker-proxy: Strip binary.
system/dosbox-dev: Fix icon and .desktop.
system/driconf: Fix icon path, add doinst.sh.
system/dtach: Updated for version 0.9, strip binary.
system/dvdisaster: Fix doinst.sh.
system/evolution-data-server: Added (Desktop Information Store)
system/execline: Fix docs.
system/f3: Strip binary.
system/fatsort: Fix man page permission.
system/fileschanged: Don't spam /usr/lib.
system/firejail: Add SlackBuild to doc dir.
system/firetools: Add SlackBuild to doc dir.
system/fish: Updated for version 3.4.0.
system/font-manager: Fix doinst.sh.
system/foomatic-db: Fix doc perms, PPD symlink.
system/freeipmi: Fix /installpkg-* mess, symlinks.
system/freeswitch: Fix docs.
system/fuse-exfat: Fix doinst.sh.
system/fuse-zip: Remove /usr/share/doc.
system/fuseiso: Fix docs.
system/gdmap: Fix .desktop.
system/gencfs: Fix .desktop.
system/gentoo: Fix icon and .desktop.
system/geoclue: Add doinst.sh (glib schemas).
system/gnome-commander: Fix icon and symlinks.
system/gnome-online-accounts: Added (access GNOME online accounts)
system/goaccess: Fix docs.
system/hdapsd: Don't step on existing config file.
system/heartbeat: Fix doinst.sh.
system/hfsprogs: Strip binaries.
system/iscan: Fix .desktop, symlink, docs.
system/kafka: Fix symlink.
system/lcdf-typetools: Added (Program for Font Manipulation).
system/letsencrypt: Updated for version 1.26.0.
system/libratbag: Strip binaries.
system/lilyterm: Add doinst.sh, fix .desktop.
system/lvm2-cluster: Strip library.
system/lxsession: Fix docs.
system/multipath-tools: Strip binaries, fix docs.
system/musl: Updated for version 1.2.3.
system/nagvis: Fix docs, symlinks.
system/nss_ldap: Strip library, fix docs.
system/openrazer-daemon: Updated for version 3.3.0.
system/openrazer-kernel: Updated for version 3.3.0.
system/opensc: Fix doinst.sh.
system/pass-import: Fix man page dir.
system/pcmanfm: Fix docs.
system/pcsc-perl: Strip shared lib.
system/pgbadger: updated for version 11.8, new maintainer
system/pgsanity: updated for version 0.2.9, python3, new maintainer
system/pommed-light: Strip binary.
system/postgresql: Strip pg_config binary.
system/qterminal: Fix .desktop and doinst.sh.
system/qtgzmanager: Fix doinst.sh and .desktop.
system/rabbitmq-server: Fix docs.
system/rar2fs: Strip binaries.
system/reiser4progs: Fix docs, static libs.
system/restic: Updated for version 0.13.1
system/runc: Strip binary.
system/s3fs-fuse: Updated for version 1.91.
system/s6-linux-init: Fix docs.
system/s6-rc: Fix docs.
system/s6: Fix docs.
system/scalpel: Fix docs.
system/scanmem: Updated for version 0.17, use python3.
system/smem: updated for version 1.5, python3, new maintainer
system/squashfuse: Added (FUSE filesystem to mount squashfs).
system/telegraf: Updated for version 1.22.1
system/ticpp: Fix /usr/include permissions.
system/tmsu-bin: Only x86_64 is supported.
system/unetbootin: Fix icon perms and .desktop.
system/wmfsm: Fix docs.
system/xorgxrdp: Fix docs.
system/xrdp: Fix doinst.sh.
system/yelp: Updated for version 42.1.
system/yelp: Use WebKit 4.0 API.
+--------------------------+


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/4b09ed1a/attachment-0001.asc>

From ozan.turkyilmaz at gmail.com  Sat Apr 16 06:31:07 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Sat, 16 Apr 2022 09:31:07 +0300
Subject: [Slackbuilds-users] WebPage Source Code
Message-ID: <ff84cc88587c3bf3a5cfd5e54c1ecba436d8bbc8.camel@gmail.com>

Hello Admins,

Out of curiosity I am asking, is there any plans to open the web page's
source code?

Regards,
Ozan

From willysr at slackbuilds.org  Sat Apr 16 06:38:41 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 16 Apr 2022 13:38:41 +0700
Subject: [Slackbuilds-users] WebPage Source Code
In-Reply-To: <ff84cc88587c3bf3a5cfd5e54c1ecba436d8bbc8.camel@gmail.com>
References: <ff84cc88587c3bf3a5cfd5e54c1ecba436d8bbc8.camel@gmail.com>
Message-ID: <202fb068-40b9-8c29-a684-01d340953607@slackbuilds.org>

> Out of curiosity I am asking, is there any plans to open the web page's
> source code?

is there any changes needed?


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/4f9dbed3/attachment.asc>

From ozan.turkyilmaz at gmail.com  Sat Apr 16 06:40:56 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Sat, 16 Apr 2022 09:40:56 +0300
Subject: [Slackbuilds-users] WebPage Source Code
In-Reply-To: <202fb068-40b9-8c29-a684-01d340953607@slackbuilds.org>
References: <ff84cc88587c3bf3a5cfd5e54c1ecba436d8bbc8.camel@gmail.com>
 <202fb068-40b9-8c29-a684-01d340953607@slackbuilds.org>
Message-ID: <5f43bef33c7362e23e85515279e7a04596557ab3.camel@gmail.com>

Cts, 2022-04-16 tarihinde 13:38 +0700 saatinde, Willy Sudiarto Raharjo
yazd?:
> > Out of curiosity I am asking, is there any plans to open the web
> > page's
> > source code?
> 
> is there any changes needed?
> 
It's not really about changes needed but other people looking at the
source and fixing around. I see a lot of projects put their web page in
git repo as well as their program and let people fix bugs etc.
Also I see a lot of emails about packages not showing up in pending yet
not allowing the submission.

Regards,
Ozan

From willysr at slackbuilds.org  Sat Apr 16 06:53:59 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 16 Apr 2022 13:53:59 +0700
Subject: [Slackbuilds-users] WebPage Source Code
In-Reply-To: <5f43bef33c7362e23e85515279e7a04596557ab3.camel@gmail.com>
References: <ff84cc88587c3bf3a5cfd5e54c1ecba436d8bbc8.camel@gmail.com>
 <202fb068-40b9-8c29-a684-01d340953607@slackbuilds.org>
 <5f43bef33c7362e23e85515279e7a04596557ab3.camel@gmail.com>
Message-ID: <d0859951-4f5d-b815-e3f0-01fe7cfdae6b@slackbuilds.org>

> It's not really about changes needed but other people looking at the
> source and fixing around. I see a lot of projects put their web page in
> git repo as well as their program and let people fix bugs etc.
> Also I see a lot of emails about packages not showing up in pending yet
> not allowing the submission.

If people send in proper way, it will showed up in /pending
Once it's approved, it will be moved to /ready, waiting for public
update in weekend.

If things go wrong, it will be rejected and need to be submitted again.
The workflow has been working well so far
if you remove a submission, then you need to make sure it's not a new
dependency for another new script that you submit.
For example you submit new script A which is a new dependency for new
script B and then A got rejected. You need to remove B first, and then A
or else the system will reject the removal because it will make B broken
without A being approved first.



-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/8d20515e/attachment.asc>

From ozan.turkyilmaz at gmail.com  Sat Apr 16 06:55:57 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Sat, 16 Apr 2022 09:55:57 +0300
Subject: [Slackbuilds-users] WebPage Source Code
In-Reply-To: <d0859951-4f5d-b815-e3f0-01fe7cfdae6b@slackbuilds.org>
References: <ff84cc88587c3bf3a5cfd5e54c1ecba436d8bbc8.camel@gmail.com>
 <202fb068-40b9-8c29-a684-01d340953607@slackbuilds.org>
 <5f43bef33c7362e23e85515279e7a04596557ab3.camel@gmail.com>
 <d0859951-4f5d-b815-e3f0-01fe7cfdae6b@slackbuilds.org>
Message-ID: <72afa80a5152ead99c1b6dd6864f4a1bf1332527.camel@gmail.com>

Cts, 2022-04-16 tarihinde 13:53 +0700 saatinde, Willy Sudiarto Raharjo
yazd?:
> > It's not really about changes needed but other people looking at
> > the
> > source and fixing around. I see a lot of projects put their web
> > page in
> > git repo as well as their program and let people fix bugs etc.
> > Also I see a lot of emails about packages not showing up in pending
> > yet
> > not allowing the submission.
> 
> If people send in proper way, it will showed up in /pending
> Once it's approved, it will be moved to /ready, waiting for public
> update in weekend.
> 
> If things go wrong, it will be rejected and need to be submitted
> again.
> The workflow has been working well so far
> if you remove a submission, then you need to make sure it's not a new
> dependency for another new script that you submit.
> For example you submit new script A which is a new dependency for new
> script B and then A got rejected. You need to remove B first, and
> then A
> or else the system will reject the removal because it will make B
> broken
> without A being approved first.

I was talking about the situtation when the script is rejected but the
submission does not let a new upload saying it is already in the
pending while it is not listed in the pending.

From willysr at slackbuilds.org  Sat Apr 16 07:04:55 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 16 Apr 2022 14:04:55 +0700
Subject: [Slackbuilds-users] WebPage Source Code
In-Reply-To: <72afa80a5152ead99c1b6dd6864f4a1bf1332527.camel@gmail.com>
References: <ff84cc88587c3bf3a5cfd5e54c1ecba436d8bbc8.camel@gmail.com>
 <202fb068-40b9-8c29-a684-01d340953607@slackbuilds.org>
 <5f43bef33c7362e23e85515279e7a04596557ab3.camel@gmail.com>
 <d0859951-4f5d-b815-e3f0-01fe7cfdae6b@slackbuilds.org>
 <72afa80a5152ead99c1b6dd6864f4a1bf1332527.camel@gmail.com>
Message-ID: <22b29b33-5e56-b9da-59fb-ae43f3228cbf@slackbuilds.org>

> I was talking about the situtation when the script is rejected but the
> submission does not let a new upload saying it is already in the
> pending while it is not listed in the pending.

admins need to remove it from DB which is manual process.
Just send an email to the list and it will be removed.

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/b579abd6/attachment.asc>

From vijaymarcel at outlook.com  Fri Apr 15 12:16:00 2022
From: vijaymarcel at outlook.com (vijay marcel)
Date: Fri, 15 Apr 2022 12:16:00 +0000
Subject: [Slackbuilds-users] couldn't reupload after removing from system
Message-ID: <SJ0PR02MB7760C4872906745FFDD50CABE1EE9@SJ0PR02MB7760.namprd02.prod.outlook.com>

Hi,

I uploaded a slackbuild called chafa but later found that it needed some corrections so I removed it and the dependent slackbuild but when I try to reupload, it  says it is already in the system. I apologize for the inconvenience caused I hope you can help me.

regards
Vijay Marcel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220415/3bc48640/attachment-0001.htm>

From mjolnirdam at gmail.com  Sat Apr 16 07:18:24 2022
From: mjolnirdam at gmail.com (Damian Perticone)
Date: Sat, 16 Apr 2022 04:18:24 -0300
Subject: [Slackbuilds-users] waybar submission
Message-ID: <CAEW3CoFcrRj69Wroj=psnSBRhXMQEftHVW-7_xv7auvARu-xwQ@mail.gmail.com>

Hi I can't  re-upload my SB for waybar, it says : "File exists; a
submission by the name 'waybar' is already pending approval."

best regards!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/ecca11af/attachment.htm>

From willysr at slackbuilds.org  Sat Apr 16 07:36:06 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 16 Apr 2022 14:36:06 +0700
Subject: [Slackbuilds-users] couldn't reupload after removing from system
In-Reply-To: <SJ0PR02MB7760C4872906745FFDD50CABE1EE9@SJ0PR02MB7760.namprd02.prod.outlook.com>
References: <SJ0PR02MB7760C4872906745FFDD50CABE1EE9@SJ0PR02MB7760.namprd02.prod.outlook.com>
Message-ID: <0535af23-4e9f-cfa6-989e-609867119589@slackbuilds.org>

> I uploaded a slackbuild called chafa but later found that it needed some corrections so I removed it and the dependent slackbuild but when I try to reupload, it  says it is already in the system. I apologize for the inconvenience caused I hope you can help me.

you can resubmit now


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/6271c7ca/attachment.asc>

From willysr at slackbuilds.org  Sat Apr 16 07:36:36 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 16 Apr 2022 14:36:36 +0700
Subject: [Slackbuilds-users] waybar submission
In-Reply-To: <CAEW3CoFcrRj69Wroj=psnSBRhXMQEftHVW-7_xv7auvARu-xwQ@mail.gmail.com>
References: <CAEW3CoFcrRj69Wroj=psnSBRhXMQEftHVW-7_xv7auvARu-xwQ@mail.gmail.com>
Message-ID: <ba0aaad8-ac74-cc75-bf79-6a80a5cda836@slackbuilds.org>

> Hi I can't  re-upload my SB for waybar, it says : "File exists; a
> submission by the name 'waybar' is already pending approval."

you can resubmit now


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/81233a57/attachment.asc>

From poprocks at gmail.com  Sat Apr 16 16:03:55 2022
From: poprocks at gmail.com (Logan Rathbone)
Date: Sat, 16 Apr 2022 12:03:55 -0400
Subject: [Slackbuilds-users] Admins - Question about Brave browser
In-Reply-To: <43206d92-c4b1-533b-8128-7df6e231eb80@slackware.uk>
References: <CAFy1yb3N6sZnVjJNevTwFqDmpu0M+4P4ioc+bLMjxp5ZvOy4oQ@mail.gmail.com>
 <c4f437c5-19fb-7318-cf35-e6f9895699b6@gmail.com>
 <d17bdddebdb01459db8ff76abc5d5e3b.squirrel@email.fatcow.com>
 <43206d92-c4b1-533b-8128-7df6e231eb80@slackware.uk>
Message-ID: <Ylro695rJoYbv6Fu@thinkpad.local.domain>

On Fri, Apr 15, 2022 at 05:54:56PM EDT, B. Watson wrote:
> On Fri, 15 Apr 2022, Andrew Payne wrote:
> > This slackbuild will adjust MIME settings for Brave. If you
> > wish to retain your current MIME settings, you can remove:
> > 
> > if [ -x /usr/bin/update-mime-database ]; then
> >    /usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
> > fi
> > 
> > from the doinst.sh file before building.
> > 
> > ++
> > 
> > OR pull the MIME lines out of doinst.sh altogether.
> 
> You should remove the update-mime-database lines from the doinst.sh,
> since they don't do anything anyway, other than waste a bit of time.
> update-mime-database doesn't do what you thought it did...
[snip]
> Basically, the mime database in /usr/share/mime defines MIME types
> like image/png or text/plain. It doesn't have anything to do with user
> preferences (your doinst.sh won't make Brave the default browser)...
[snip]

In case anyone is perusing this list and wondering what *does* set user
preferences for app associations for MIME types pursuant to the XDG
standards, this section of an article on the Arch Wiki provides a good
summary:

https://wiki.archlinux.org/title/XDG_MIME_Applications#mimeapps.list

tldr: it's file called mimeapps.list, looked for in various directories
in a hierarchical fashion.

From anddt at ukr.net  Sat Apr 16 18:19:45 2022
From: anddt at ukr.net (Andrew)
Date: Sat, 16 Apr 2022 18:19:45 +0000
Subject: [Slackbuilds-users] Updates for hostapd, parcellite, qt5ct, yt-dlp,
 rclone
Message-ID: <C6E17D39-C313-4D05-B860-9AA714DA840A@ukr.net>

Hello, people, long time no see.
I started to use slackware again (liveslak, full 15.0 install with patches, 32-bit).
I have noticed that some of slackbuilds are outdated a little bit, so I want to share them as git-format-patch'es (after I read the https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html page).
I haven't used hostapd much. If there are any regressions in 2.10, you are free to not apply a patch.
About rclone: also haven't used it, just noticed that my platform is unsupported and wanted to fix it.
At the time I write this letter I don't see any of this slackbuilds in pending/approved.
If there won't be any objections, I will send further updates via this list.
Thank you for attention and sorry for my bad English.

--
Best wishes from Ukraine,
Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-network-hostapd-Updated-for-version-2.10.patch
Type: application/octet-stream
Size: 21722 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/86922d49/attachment-0005.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-desktop-parcellite-Updated-for-version-1.2.1.patch
Type: application/octet-stream
Size: 3143 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/86922d49/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0004-network-yt-dlp-Updated-for-version-2022.04.08.patch
Type: application/octet-stream
Size: 1391 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/86922d49/attachment-0007.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-desktop-qt5ct-Updated-for-version-1.5.patch
Type: application/octet-stream
Size: 1766 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/86922d49/attachment-0008.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0005-network-rclone-Added-support-for-i586.patch
Type: application/octet-stream
Size: 2621 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220416/86922d49/attachment-0009.obj>

From sbo at linuxgalaxy.org  Sat Apr 16 20:13:04 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Sat, 16 Apr 2022 20:13:04 +0000
Subject: [Slackbuilds-users] Updates - 20220416.1
In-Reply-To: <f2e13dae-89a8-0fa3-0e69-d5ae6adb4d3f@slackbuilds.org>
References: <f2e13dae-89a8-0fa3-0e69-d5ae6adb4d3f@slackbuilds.org>
Message-ID: <c1073fce-1348-4a74-f92b-a17ece9f9e1b@linuxgalaxy.org>

On 4/15/22 22:48, Willy Sudiarto Raharjo wrote:
> Please use sbo-maintainer-tools
> (https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools) to
> test your script before you submit it, either via github/gitlab or
> submission form. It's the same tool we used to check your submissions.

FYI,

Clicking on the link (via Thunderbird -> Firefox) results in

Sorry, that page could not be found on SlackBuilds.org.

However from the main https://slackbuilds.org page, browsing (with 15.0
in drop down list)

repository -> system -> sbo-maintainer-tools

gets to the right place.  The URL in the address bar is the same but has
a trailing /; if I copy that one to a new tab/window it works.  If I
manually copy the posted link above it fails.

TL;DR:

posted link = bad
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools

correct link = good
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/

-Ed


From richard at aaazen.com  Sat Apr 16 20:54:29 2022
From: richard at aaazen.com (Richard Narron)
Date: Sat, 16 Apr 2022 13:54:29 -0700 (PDT)
Subject: [Slackbuilds-users] THE.SlackBuild
Message-ID: <4db51a36-a341-fb94-4492-d6b18273eafe@aaazen.com>

I recently submitted a new THE.SlackBuild script that copied
documentation from the install directory like this:

install -m0644 COPYING FAQ HISTORY INSTALL README* TODO \
         $PKG/usr/doc/$PRGNAM-$VERSION

But when it was installed, the first line leaves out the INSTALL document:

install -m0644 COPYING FAQ HISTORY README* TODO \

Here is a patch to correct the installed THE.SlackBuild:

----------------------cut here---------------------------------------
--- a/THE.SlackBuild    2022-04-15 22:28:08.632905883 -0700
+++ b/THE.SlackBuild    2022-04-14 15:01:39.153193239 -0700
@@ -113,7 +113,7 @@
          $PKG/usr/doc/$PRGNAM-$VERSION/html

 cd $TMP/$PRGNAM-$VERSION
-install -m0644 COPYING FAQ HISTORY README* TODO \
+install -m0644 COPYING FAQ HISTORY INSTALL README* TODO \
          $PKG/usr/doc/$PRGNAM-$VERSION

 # Try to  make the X11 version of THE by using PDCurses (XCurses)
----------------------cut here---------------------------------------

Can you fix it?

Please advise.

Richard Narron

From willysr at slackbuilds.org  Sun Apr 17 02:55:20 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 17 Apr 2022 09:55:20 +0700
Subject: [Slackbuilds-users] Updates - 20220416.1
In-Reply-To: <c1073fce-1348-4a74-f92b-a17ece9f9e1b@linuxgalaxy.org>
References: <f2e13dae-89a8-0fa3-0e69-d5ae6adb4d3f@slackbuilds.org>
 <c1073fce-1348-4a74-f92b-a17ece9f9e1b@linuxgalaxy.org>
Message-ID: <d86b5f5d-e349-714e-75d6-5ffb761299a8@slackbuilds.org>

> TL;DR:
> 
> posted link = bad
> https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools
> 
> correct link = good
> https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/

yeah i accidentally removed them when trying to remove the space before
ending )


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220417/4de2b9fa/attachment.asc>

From dave at slackbuilds.org  Sun Apr 17 06:24:06 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 17 Apr 2022 07:24:06 +0100
Subject: [Slackbuilds-users] THE.SlackBuild
In-Reply-To: <4db51a36-a341-fb94-4492-d6b18273eafe@aaazen.com>
References: <4db51a36-a341-fb94-4492-d6b18273eafe@aaazen.com>
Message-ID: <YluyhpG6ORXaC3Br@localhost>

On 16/04/22 13:54,
Richard Narron <richard at aaazen.com> put forth the proposition:
> I recently submitted a new THE.SlackBuild script that copied
> documentation from the install directory like this:
> install -m0644 COPYING FAQ HISTORY INSTALL README* TODO \
>          $PKG/usr/doc/$PRGNAM-$VERSION
> But when it was installed, the first line leaves out the INSTALL document:
> install -m0644 COPYING FAQ HISTORY README* TODO \
> ...
> Please advise.
> Richard Narron

We don't really need INSTALL documents, because it's already
installed by the time anyone reads it, right?

--
Dave

From andrew.david.strong at gmail.com  Sun Apr 17 08:08:52 2022
From: andrew.david.strong at gmail.com (andrew)
Date: Sun, 17 Apr 2022 18:08:52 +1000
Subject: [Slackbuilds-users] 'Correct' download link from Github?
Message-ID: <YlvLFIP3kl+a81Fa@ilium.andrews-corner.org>

I am putting a new Slackbuild together for opustags, which is hosted
on github:

https://github.com/fmang/opustags

I am a little unsure of the correct download link from github which
shows some variation whether wget or browser is used.

Is there an SBo policy about such links?

Thanks,

Andrew
-- 
You think that's air you're breathing now?

From dave at slackbuilds.org  Sun Apr 17 08:33:33 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 17 Apr 2022 09:33:33 +0100
Subject: [Slackbuilds-users] 'Correct' download link from Github?
In-Reply-To: <YlvLFIP3kl+a81Fa@ilium.andrews-corner.org>
References: <YlvLFIP3kl+a81Fa@ilium.andrews-corner.org>
Message-ID: <YlvQ3YgiYeGV0ZW5@localhost>

On 17/04/22 18:08,
andrew <andrew.david.strong at gmail.com> put forth the proposition:
> I am putting a new Slackbuild together for opustags, which is hosted
> on github:
> https://github.com/fmang/opustags
> I am a little unsure of the correct download link from github which
> shows some variation whether wget or browser is used.
> Is there an SBo policy about such links?

No policy yet AFAIK but you can find the release tag (add /tags/ to
the end of the URL) and then do something like:

URL/archive/TAG/PRGNAM-TAG.tar.gz which would be:

https://github.com/fmang/opustags/archive/1.2.3/opustags-1.2.3.tar.gz

or

https://github.com/fmang/opustags/archive/v1.2.3/opustags-1.2.3.tar.gz

(note the v before the first TAG sometimes works if the first URL
gives a 404.)

The downloaded tarball can be tested with `tar tf <archive> | head'
to see if the directory name really matches the expected version
number.

HTH

--
Dave

From andrew.david.strong at gmail.com  Sun Apr 17 08:49:09 2022
From: andrew.david.strong at gmail.com (andrew)
Date: Sun, 17 Apr 2022 18:49:09 +1000
Subject: [Slackbuilds-users] 'Correct' download link from Github?
In-Reply-To: <YlvQ3YgiYeGV0ZW5@localhost>
References: <YlvLFIP3kl+a81Fa@ilium.andrews-corner.org>
 <YlvQ3YgiYeGV0ZW5@localhost>
Message-ID: <YlvUhUo5/oGCp6N6@ilium.andrews-corner.org>

On Sun, Apr 17, 2022 at 09:33:33AM +0100, Dave Woodfall wrote:

> No policy yet AFAIK but you can find the release tag (add /tags/ to
> the end of the URL) and then do something like:
> 
> URL/archive/TAG/PRGNAM-TAG.tar.gz which would be:
> 
> https://github.com/fmang/opustags/archive/1.2.3/opustags-1.2.3.tar.gz

Thanks, this one worked perfectly :)

Andrew
-- 
You think that's air you're breathing now?

From ozan.turkyilmaz at gmail.com  Sun Apr 17 10:08:14 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Sun, 17 Apr 2022 13:08:14 +0300
Subject: [Slackbuilds-users] 'Correct' download link from Github?
In-Reply-To: <YlvQ3YgiYeGV0ZW5@localhost>
References: <YlvLFIP3kl+a81Fa@ilium.andrews-corner.org>
 <YlvQ3YgiYeGV0ZW5@localhost>
Message-ID: <defe09dfc30554ab4a5756788941afbc71e88ed3.camel@gmail.com>

Paz, 2022-04-17 tarihinde 09:33 +0100 saatinde, Dave Woodfall yazd?:
> No policy yet AFAIK but you can find the release tag (add /tags/ to
> the end of the URL) and then do something like:
> 
> 
I remember a talk about content disposition (and how wget ignores it by
default) and github links should give same file with or without content
disposition. I dont remember when thou. My memory is not as it used to
be.

Regards,
Ozan 

From sb at rbn.im  Sun Apr 17 12:42:02 2022
From: sb at rbn.im (Ruben Schuller)
Date: Sun, 17 Apr 2022 14:42:02 +0200
Subject: [Slackbuilds-users] 'Correct' download link from Github?
In-Reply-To: <defe09dfc30554ab4a5756788941afbc71e88ed3.camel@gmail.com>
References: <YlvLFIP3kl+a81Fa@ilium.andrews-corner.org>
 <YlvQ3YgiYeGV0ZW5@localhost>
 <defe09dfc30554ab4a5756788941afbc71e88ed3.camel@gmail.com>
Message-ID: <20220417144202.51cb775b@kiwi.kuchen>

Hi,

2022-04-17 Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>:

> Paz, 2022-04-17 tarihinde 09:33 +0100 saatinde, Dave Woodfall yazd?:
> > No policy yet AFAIK but you can find the release tag (add /tags/ to
> > the end of the URL) and then do something like:
> > 
> >   
> I remember a talk about content disposition (and how wget ignores it
> by default) and github links should give same file with or without
> content disposition. I dont remember when thou. My memory is not as
> it used to be.

I think the decision was that scripts should assume content disposition
is used. I usually use

tar xvf v${VERSION}.tar.gz || tar ${PRGNAM}-${VERSION}.tar.gz 

(or the other way around..) in my scripts to catch the case when it
isn't. I think it's fine, either of those tarballs should be MD5-checked
anyway.

Cheers
Ruben

From richard at aaazen.com  Sun Apr 17 13:08:36 2022
From: richard at aaazen.com (Richard Narron)
Date: Sun, 17 Apr 2022 06:08:36 -0700 (PDT)
Subject: [Slackbuilds-users] THE.SlackBuild
In-Reply-To: <YluyhpG6ORXaC3Br@localhost>
References: <4db51a36-a341-fb94-4492-d6b18273eafe@aaazen.com>
 <YluyhpG6ORXaC3Br@localhost>
Message-ID: <37846dd7-dd6d-786-8761-d27edcedc790@aaazen.com>

On Sun, 17 Apr 2022, Dave Woodfall wrote:

> On 16/04/22 13:54,
> Richard Narron <richard at aaazen.com> put forth the proposition:
> > I recently submitted a new THE.SlackBuild script that copied
> > documentation from the install directory like this:
> > install -m0644 COPYING FAQ HISTORY INSTALL README* TODO \
> >          $PKG/usr/doc/$PRGNAM-$VERSION
> > But when it was installed, the first line leaves out the INSTALL document:
> > install -m0644 COPYING FAQ HISTORY README* TODO \
>
> We don't really need INSTALL documents, because it's already
> installed by the time anyone reads it, right?

Install documents gives information about what can be
installed as well as where it can be installed.

For example after reading the THE install document, I know that the program
has a text ncurses version, a graphical X11 version and that it runs on
Red Hat Linux.

Richard

From urchlay at slackware.uk  Sun Apr 17 15:25:07 2022
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 17 Apr 2022 11:25:07 -0400 (EDT)
Subject: [Slackbuilds-users] THE.SlackBuild
In-Reply-To: <4db51a36-a341-fb94-4492-d6b18273eafe@aaazen.com>
References: <4db51a36-a341-fb94-4492-d6b18273eafe@aaazen.com>
Message-ID: <f4d567e1-b39b-355-1698-fead8884de97@slackware.uk>



On Sat, 16 Apr 2022, Richard Narron wrote:

> But when it was installed, the first line leaves out the INSTALL document:
>
> install -m0644 COPYING FAQ HISTORY README* TODO \
>
> Here is a patch to correct the installed THE.SlackBuild:

The INSTALL file is probably being left out on purpose. Have you read
it? It's useless for a package user. It describes how to compile THE,
or install it from RPMs.

However, if you already installed THE from a package built by the SBo
script, there's no need to read the INSTALL document: the SBo script
already compiled the software for you.

This is true of pretty much every INSTALL file (or INSTALL.txt,
INSTALL.md) in almost every package. *Rarely*, there's also some
useful config/setup information in INSTALL, but in general, SBo
packages shouldn't include install instructions.

From urchlay at slackware.uk  Sun Apr 17 15:31:43 2022
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 17 Apr 2022 11:31:43 -0400 (EDT)
Subject: [Slackbuilds-users] THE.SlackBuild
In-Reply-To: <37846dd7-dd6d-786-8761-d27edcedc790@aaazen.com>
References: <4db51a36-a341-fb94-4492-d6b18273eafe@aaazen.com>
 <YluyhpG6ORXaC3Br@localhost> <37846dd7-dd6d-786-8761-d27edcedc790@aaazen.com>
Message-ID: <aa78e580-e0c6-337b-fc38-9194363e1cba@slackware.uk>



On Sun, 17 Apr 2022, Richard Narron wrote:

> For example after reading the THE install document, I know that the program
> has a text ncurses version, a graphical X11 version and that it runs on
> Red Hat Linux.

The README already tells you two of those things: That there's a "text
mode and native X11 application", and "THE uses curses as its screen
handler".

README doesn't say anything about Red Hat, but that's not particularly
useful information to include in a Slackware package anyway. It does
say "most Unix systems".

From dave at slackbuilds.org  Sun Apr 17 15:53:34 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 17 Apr 2022 16:53:34 +0100
Subject: [Slackbuilds-users] 'Correct' download link from Github?
In-Reply-To: <20220417144202.51cb775b@kiwi.kuchen>
References: <YlvLFIP3kl+a81Fa@ilium.andrews-corner.org>
 <YlvQ3YgiYeGV0ZW5@localhost>
 <defe09dfc30554ab4a5756788941afbc71e88ed3.camel@gmail.com>
 <20220417144202.51cb775b@kiwi.kuchen>
Message-ID: <Ylw3/tRgYToRyJVd@localhost>

On 17/04/22 14:42,
Ruben Schuller <sb at rbn.im> put forth the proposition:
> Hi,
> 2022-04-17 Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>:
> > Paz, 2022-04-17 tarihinde 09:33 +0100 saatinde, Dave Woodfall yazd?:
> > > No policy yet AFAIK but you can find the release tag (add /tags/ to
> > > the end of the URL) and then do something like:
> > >
> > >
> > I remember a talk about content disposition (and how wget ignores it
> > by default) and github links should give same file with or without
> > content disposition. I dont remember when thou. My memory is not as
> > it used to be.

I think what you're referring to is that github will tend to send any
name tarball that you ask for from some links, but using the release
source links sends the format 1.2.3.tar.gz by default.  This isn't
very useful if you use sbopkg and /var/cache/sbopkg fills up with
1.2.3.tar.gz, 3.4.5.tar.gz etc., because at some point you might need
to find some source and seeing them named like that is unhelpful.

> I think the decision was that scripts should assume content disposition
> is used. I usually use
> tar xvf v${VERSION}.tar.gz || tar ${PRGNAM}-${VERSION}.tar.gz
> (or the other way around..) in my scripts to catch the case when it
> isn't. I think it's fine, either of those tarballs should be MD5-checked

We can't assume that it is always used.  Content-Disposition doesn't
always work, and is still marked as experimental in wget(1), and in
curl can give errors when mixed with other flags like -C.

"--content-disposition
     If this is set to on, experimental (not fully-functional) support for
     "Content-Disposition" headers is enabled. This can currently result in
     extra round-trips to the server for a "HEAD" request, and is known to
     suffer from a few bugs, which is why it is not currently enabled by
     default."

The method I showed should always download $PRGNAM-$VERSION.tar.gz
and I change github URLs in submissions when I come across one.

One simple way to do this (test without -i first):

source the .info
sed -E "s,(https://github.com/[^/]+/$PRGNAM)/archive/refs/tags/v?($VERSION)(.tar.gz),\1/archive/v\2/$PRGNAM-\2\3," -i $PRGNAM.info

--
Dave

From d.zlatanidis at gmail.com  Sun Apr 17 17:55:52 2022
From: d.zlatanidis at gmail.com (Dimitris Zlatanidis)
Date: Sun, 17 Apr 2022 20:55:52 +0300
Subject: [Slackbuilds-users] Please your support
Message-ID: <f44ea676-a959-ce5b-3984-65ab8c3945f3@gmail.com>

Greetings to all members,

I would like to ask for your support.
I'm giving a job interview (Python Developer) and my Gitlab repository, 
will play an important role, so whoever wants to add an asterisk in my 
Projects and especially in slpkg, colored, sun, dropbox-filemanager, 
sbo-templates etc., I would appreciate it a lot!

Thank you very much,
Dimitris

-- 
Dimitris Zlatanidis
https://dslackw.gitlab.io/slpkg/
https://gitlab.com/dslackw


From richard at aaazen.com  Sun Apr 17 21:20:07 2022
From: richard at aaazen.com (Richard Narron)
Date: Sun, 17 Apr 2022 14:20:07 -0700 (PDT)
Subject: [Slackbuilds-users] THE.SlackBuild
In-Reply-To: <aa78e580-e0c6-337b-fc38-9194363e1cba@slackware.uk>
References: <4db51a36-a341-fb94-4492-d6b18273eafe@aaazen.com>
 <YluyhpG6ORXaC3Br@localhost> <37846dd7-dd6d-786-8761-d27edcedc790@aaazen.com>
 <aa78e580-e0c6-337b-fc38-9194363e1cba@slackware.uk>
Message-ID: <27299621-42df-3c47-1078-a24829c3d7ac@aaazen.com>

On Sun, 17 Apr 2022, B. Watson wrote:

> On Sun, 17 Apr 2022, Richard Narron wrote:
>
> > For example after reading the THE install document, I know that the program
> > has a text ncurses version, a graphical X11 version and that it runs on
> > Red Hat Linux.
>
> README doesn't say anything about Red Hat, but that's not particularly
> useful information to include in a Slackware package anyway. It does
> say "most Unix systems".

I don't judge information and I do not presume to know what a user might or
might not be interested in.

When I look on my system I find over 500 "INSTALL" documents in the
/usr/doc directory.

Richard Narron

From klaatu at mixedsignals.ml  Sun Apr 17 22:09:26 2022
From: klaatu at mixedsignals.ml (Klaatu)
Date: Sun, 17 Apr 2022 22:09:26 +0000
Subject: [Slackbuilds-users] 'Correct' download link from Github?
In-Reply-To: <YlvQ3YgiYeGV0ZW5@localhost>
References: <YlvLFIP3kl+a81Fa@ilium.andrews-corner.org>
 <YlvQ3YgiYeGV0ZW5@localhost>
Message-ID: <D916953B-9600-44C4-9A4F-223C051773A5@mixedsignals.ml>

This is a very common.  I think it would be nice to add an example of David's answer to the SlackBuild templates for both new and experienced maintainers.  I've wasted countless minutes looking up the "secret formula" when starting or updating my scripts. 

On 17 April 2022 8:33:33 AM UTC, Dave Woodfall <dave at slackbuilds.org> wrote:
>On 17/04/22 18:08,
>andrew <andrew.david.strong at gmail.com> put forth the proposition:
>> I am putting a new Slackbuild together for opustags, which is hosted
>> on github:
>> https://github.com/fmang/opustags
>> I am a little unsure of the correct download link from github which
>> shows some variation whether wget or browser is used.
>> Is there an SBo policy about such links?
>
>No policy yet AFAIK but you can find the release tag (add /tags/ to
>the end of the URL) and then do something like:
>
>URL/archive/TAG/PRGNAM-TAG.tar.gz which would be:
>
>https://github.com/fmang/opustags/archive/1.2.3/opustags-1.2.3.tar.gz
>
>or
>
>https://github.com/fmang/opustags/archive/v1.2.3/opustags-1.2.3.tar.gz
>
>(note the v before the first TAG sometimes works if the first URL
>gives a 404.)
>
>The downloaded tarball can be tested with `tar tf <archive> | head'
>to see if the directory name really matches the expected version
>number.
>
>HTH
>
>--
>Dave
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/
>

-- 
Klaatu

From francois.gingras at gmail.com  Mon Apr 18 03:06:44 2022
From: francois.gingras at gmail.com (Francois Gingras)
Date: Sun, 17 Apr 2022 23:06:44 -0400
Subject: [Slackbuilds-users] Please your support
In-Reply-To: <CAOY50mtP0OAQZcEOtT=fEKfzzWmR0DV7RouaVfLbdJ45jWVVig@mail.gmail.com>
References: <f44ea676-a959-ce5b-3984-65ab8c3945f3@gmail.com>
 <CAOY50mtP0OAQZcEOtT=fEKfzzWmR0DV7RouaVfLbdJ45jWVVig@mail.gmail.com>
Message-ID: <CAOY50mtnHYWyTKM83Rxk4WaXmf2AO4UVTmdTcjFaJD+ZrEYU4Q@mail.gmail.com>

Are you seriously asking us to commit to your gitlab? Can you grab a few
projects yourself and commit those on your own?


On Sun, 17 Apr 2022 at 23:04, Frank Gingras <thumbs at apache.org> wrote:

> Are you seriously asking us to commit to your gitlab? Can you do grab a
> few projects yourself and commit those on your own?
>
> On Sun, 17 Apr 2022 at 13:54, Dimitris Zlatanidis <d.zlatanidis at gmail.com>
> wrote:
>
>> Greetings to all members,
>>
>> I would like to ask for your support.
>> I'm giving a job interview (Python Developer) and my Gitlab repository,
>> will play an important role, so whoever wants to add an asterisk in my
>> Projects and especially in slpkg, colored, sun, dropbox-filemanager,
>> sbo-templates etc., I would appreciate it a lot!
>>
>> Thank you very much,
>> Dimitris
>>
>> --
>> Dimitris Zlatanidis
>> https://dslackw.gitlab.io/slpkg/
>> https://gitlab.com/dslackw
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220417/b5e813df/attachment-0001.htm>

From jebrhansen+SBo at gmail.com  Mon Apr 18 03:09:43 2022
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sun, 17 Apr 2022 21:09:43 -0600
Subject: [Slackbuilds-users] Please your support
In-Reply-To: <CAOY50mtnHYWyTKM83Rxk4WaXmf2AO4UVTmdTcjFaJD+ZrEYU4Q@mail.gmail.com>
References: <f44ea676-a959-ce5b-3984-65ab8c3945f3@gmail.com>
 <CAOY50mtP0OAQZcEOtT=fEKfzzWmR0DV7RouaVfLbdJ45jWVVig@mail.gmail.com>
 <CAOY50mtnHYWyTKM83Rxk4WaXmf2AO4UVTmdTcjFaJD+ZrEYU4Q@mail.gmail.com>
Message-ID: <CANi9qSsa5H=V1dxttLtGQEG=idsVo3gDwMf-JrzhAUw3HwPriw@mail.gmail.com>

On Sun, Apr 17, 2022, 9:06 PM Francois Gingras <francois.gingras at gmail.com>
wrote:

> Are you seriously asking us to commit to your gitlab? Can you grab a few
> projects yourself and commit those on your own?
>
>
> On Sun, 17 Apr 2022 at 23:04, Frank Gingras <thumbs at apache.org> wrote:
>
>> Are you seriously asking us to commit to your gitlab? Can you do grab a
>> few projects yourself and commit those on your own?
>>
>> On Sun, 17 Apr 2022 at 13:54, Dimitris Zlatanidis <d.zlatanidis at gmail.com>
>> wrote:
>>
>>> Greetings to all members,
>>>
>>> I would like to ask for your support.
>>> I'm giving a job interview (Python Developer) and my Gitlab repository,
>>> will play an important role, so whoever wants to add an asterisk in my
>>> Projects and especially in slpkg, colored, sun, dropbox-filemanager,
>>> sbo-templates etc., I would appreciate it a lot!
>>>
>>> Thank you very much,
>>> Dimitris
>>>
>>> --
>>> Dimitris Zlatanidis
>>> https://dslackw.gitlab.io/slpkg/
>>> https://gitlab.com/dslackw
>>>
>>
No, I think he's asking us to "star" or basically favorite his projects if
you've think they've been helpful to you.

Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220417/6e857fb7/attachment.htm>

From francois.gingras at gmail.com  Mon Apr 18 03:19:34 2022
From: francois.gingras at gmail.com (Francois Gingras)
Date: Sun, 17 Apr 2022 23:19:34 -0400
Subject: [Slackbuilds-users] Please your support
In-Reply-To: <CANi9qSsa5H=V1dxttLtGQEG=idsVo3gDwMf-JrzhAUw3HwPriw@mail.gmail.com>
References: <f44ea676-a959-ce5b-3984-65ab8c3945f3@gmail.com>
 <CAOY50mtP0OAQZcEOtT=fEKfzzWmR0DV7RouaVfLbdJ45jWVVig@mail.gmail.com>
 <CAOY50mtnHYWyTKM83Rxk4WaXmf2AO4UVTmdTcjFaJD+ZrEYU4Q@mail.gmail.com>
 <CANi9qSsa5H=V1dxttLtGQEG=idsVo3gDwMf-JrzhAUw3HwPriw@mail.gmail.com>
Message-ID: <CAOY50mtUi_g_Qm3Q-gNp7kYsqvEaP9eqJvXGxQpTfAjoE5CO2w@mail.gmail.com>

That looks pretty spam-ish, then. Let's hope other unrelated MLs were not
hit by the same thing.

On Sun, 17 Apr 2022 at 23:09, Jeremy Hansen <jebrhansen+SBo at gmail.com>
wrote:

> On Sun, Apr 17, 2022, 9:06 PM Francois Gingras <francois.gingras at gmail.com>
> wrote:
>
>> Are you seriously asking us to commit to your gitlab? Can you grab a few
>> projects yourself and commit those on your own?
>>
>>
>> On Sun, 17 Apr 2022 at 23:04, Frank Gingras <thumbs at apache.org> wrote:
>>
>>> Are you seriously asking us to commit to your gitlab? Can you do grab a
>>> few projects yourself and commit those on your own?
>>>
>>> On Sun, 17 Apr 2022 at 13:54, Dimitris Zlatanidis <
>>> d.zlatanidis at gmail.com> wrote:
>>>
>>>> Greetings to all members,
>>>>
>>>> I would like to ask for your support.
>>>> I'm giving a job interview (Python Developer) and my Gitlab repository,
>>>> will play an important role, so whoever wants to add an asterisk in my
>>>> Projects and especially in slpkg, colored, sun, dropbox-filemanager,
>>>> sbo-templates etc., I would appreciate it a lot!
>>>>
>>>> Thank you very much,
>>>> Dimitris
>>>>
>>>> --
>>>> Dimitris Zlatanidis
>>>> https://dslackw.gitlab.io/slpkg/
>>>> https://gitlab.com/dslackw
>>>>
>>>
> No, I think he's asking us to "star" or basically favorite his projects if
> you've think they've been helpful to you.
>
> Jeremy
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220417/5adece72/attachment.htm>

From klaatu at mixedsignals.ml  Mon Apr 18 03:59:03 2022
From: klaatu at mixedsignals.ml (Klaatu)
Date: Mon, 18 Apr 2022 15:59:03 +1200
Subject: [Slackbuilds-users] Please your support
In-Reply-To: <CAOY50mtUi_g_Qm3Q-gNp7kYsqvEaP9eqJvXGxQpTfAjoE5CO2w@mail.gmail.com>
References: <f44ea676-a959-ce5b-3984-65ab8c3945f3@gmail.com>
 <CANi9qSsa5H=V1dxttLtGQEG=idsVo3gDwMf-JrzhAUw3HwPriw@mail.gmail.com>
 <CAOY50mtUi_g_Qm3Q-gNp7kYsqvEaP9eqJvXGxQpTfAjoE5CO2w@mail.gmail.com>
Message-ID: <5418661.IbC2pHGDlb@beast.slackermedia.local>

I don't find this spammy. Were he a stranger, I would feel differently, but 
Dimitris maintains several SlackBuild scripts:
https://slackbuilds.org/advsearch.php?q=Zlatanidis&stype=maint

He also produces a very useful tool `slpkg` (among others) for use with SBo.

Is seems reasonable to ask other users of SBo to take a moment to click what 
is essentially a "Like" button, so that his prospective employer sees that his 
work online actually has an impact on people.

Personally I hope Dimitris gets the job he's applying for, and is well paid, 
and can continue to work on SBo and SBo-related tools well into the future. 
Imaginary Internet Stars are mostly free (clicking buttons took about 5 
minutes of my time), so I've given him a bunch.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220418/36aa1369/attachment.htm>

From z.coldplayer at gmail.com  Mon Apr 18 04:29:29 2022
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Mon, 18 Apr 2022 08:29:29 +0400
Subject: [Slackbuilds-users] Please your support
In-Reply-To: <5418661.IbC2pHGDlb@beast.slackermedia.local>
References: <f44ea676-a959-ce5b-3984-65ab8c3945f3@gmail.com>
 <CANi9qSsa5H=V1dxttLtGQEG=idsVo3gDwMf-JrzhAUw3HwPriw@mail.gmail.com>
 <CAOY50mtUi_g_Qm3Q-gNp7kYsqvEaP9eqJvXGxQpTfAjoE5CO2w@mail.gmail.com>
 <5418661.IbC2pHGDlb@beast.slackermedia.local>
Message-ID: <CAEWL1_-s3icJg-JC3OKzp4wEg-9mHDduzJun+hkB04d_GKybzg@mail.gmail.com>

Just make his projects your star

On Mon, 18 Apr 2022, 07:59 Klaatu, <klaatu at mixedsignals.ml> wrote:

> I don't find this spammy. Were he a stranger, I would feel differently,
> but Dimitris maintains several SlackBuild scripts:
>
> https://slackbuilds.org/advsearch.php?q=Zlatanidis&stype=maint
>
> He also produces a very useful tool `slpkg` (among others) for use with
> SBo.
>
> Is seems reasonable to ask other users of SBo to take a moment to click
> what is essentially a "Like" button, so that his prospective employer sees
> that his work online actually has an impact on people.
>
> Personally I hope Dimitris gets the job he's applying for, and is well
> paid, and can continue to work on SBo and SBo-related tools well into the
> future.
>
> Imaginary Internet Stars are mostly free (clicking buttons took about 5
> minutes of my time), so I've given him a bunch.
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220418/89c63f82/attachment.htm>

From urchlay at slackware.uk  Mon Apr 18 06:00:00 2022
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 18 Apr 2022 02:00:00 -0400 (EDT)
Subject: [Slackbuilds-users] THE.SlackBuild
In-Reply-To: <27299621-42df-3c47-1078-a24829c3d7ac@aaazen.com>
References: <4db51a36-a341-fb94-4492-d6b18273eafe@aaazen.com>
 <YluyhpG6ORXaC3Br@localhost> <37846dd7-dd6d-786-8761-d27edcedc790@aaazen.com>
 <aa78e580-e0c6-337b-fc38-9194363e1cba@slackware.uk>
 <27299621-42df-3c47-1078-a24829c3d7ac@aaazen.com>
Message-ID: <a5289961-cd21-905b-7d74-cfeccb4bb57d@slackware.uk>



On Sun, 17 Apr 2022, Richard Narron wrote:

> I don't judge information and I do not presume to know what a user might or
> might not be interested in.

Sorry, I do. A user who installs a package isn't going to compile it
manually. Or, if he decides to, he's going to start by extracting the
source (and can find the INSTALL there).

> When I look on my system I find over 500 "INSTALL" documents in the
> /usr/doc directory.

Yes, and most if not all of them, you wouldn't miss them if they
were gone. Just because something is commonly done doesn't mean it
necessarily should be.

From kjhambrick at gmail.com  Mon Apr 18 10:01:18 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Mon, 18 Apr 2022 05:01:18 -0500
Subject: [Slackbuilds-users] Please your support
In-Reply-To: <5418661.IbC2pHGDlb@beast.slackermedia.local>
References: <f44ea676-a959-ce5b-3984-65ab8c3945f3@gmail.com>
 <CANi9qSsa5H=V1dxttLtGQEG=idsVo3gDwMf-JrzhAUw3HwPriw@mail.gmail.com>
 <CAOY50mtUi_g_Qm3Q-gNp7kYsqvEaP9eqJvXGxQpTfAjoE5CO2w@mail.gmail.com>
 <5418661.IbC2pHGDlb@beast.slackermedia.local>
Message-ID: <CANBHt+O3dLU6RhsMyL7n0A21ate50QfpzqkREmFUBUtBx1O-PQ@mail.gmail.com>

On Sun, Apr 17, 2022 at 10:59 PM Klaatu <klaatu at mixedsignals.ml> wrote:

> I don't find this spammy. Were he a stranger, I would feel differently,
> but Dimitris maintains several SlackBuild scripts:
>
> https://slackbuilds.org/advsearch.php?q=Zlatanidis&stype=maint
>
> He also produces a very useful tool `slpkg` (among others) for use with
> SBo.
>
> Is seems reasonable to ask other users of SBo to take a moment to click
> what is essentially a "Like" button, so that his prospective employer sees
> that his work online actually has an impact on people.
>
> Personally I hope Dimitris gets the job he's applying for, and is well
> paid, and can continue to work on SBo and SBo-related tools well into the
> future.
>
> Imaginary Internet Stars are mostly free (clicking buttons took about 5
> minutes of my time), so I've given him a bunch.
>

Got my Stars, Dimitris !

Thanks for all the SlackBuilds and all you do for Slackware !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220418/4695ebc8/attachment.htm>

From marav8 at free.fr  Mon Apr 18 10:03:10 2022
From: marav8 at free.fr (marav)
Date: Mon, 18 Apr 2022 12:03:10 +0200
Subject: [Slackbuilds-users] Please your support
In-Reply-To: <f44ea676-a959-ce5b-3984-65ab8c3945f3@gmail.com>
References: <f44ea676-a959-ce5b-3984-65ab8c3945f3@gmail.com>
Message-ID: <5467f88d-8b35-cce7-11d3-9593d4acfa3f@free.fr>

Le 17/04/2022 ? 19:55, Dimitris Zlatanidis a ?crit?:
> Greetings to all members,
>
> I would like to ask for your support.
> I'm giving a job interview (Python Developer) and my Gitlab 
> repository, will play an important role, so whoever wants to add an 
> asterisk in my Projects and especially in slpkg, colored, sun, 
> dropbox-filemanager, sbo-templates etc., I would appreciate it a lot!
>
> Thank you very much,
> Dimitris
>
Done!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220418/f64cd3d2/attachment.htm>

From arnaud.garcia-fernandez at laposte.net  Mon Apr 18 10:07:01 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Mon, 18 Apr 2022 10:07:01 +0000
Subject: [Slackbuilds-users] Please your support
In-Reply-To: <5467f88d-8b35-cce7-11d3-9593d4acfa3f@free.fr>
References: <f44ea676-a959-ce5b-3984-65ab8c3945f3@gmail.com>
 <5467f88d-8b35-cce7-11d3-9593d4acfa3f@free.fr>
Message-ID: <FF094908-168B-411F-82C2-6E922C05B3EB@laposte.net>

Same here ??

 ? Yth.

Le 18 avril 2022 10:03:10 UTC, marav <marav8 at free.fr> a ?crit?:
>Le 17/04/2022 ? 19:55, Dimitris Zlatanidis a ?crit?:
>> Greetings to all members,
>>
>> I would like to ask for your support.
>> I'm giving a job interview (Python Developer) and my Gitlab 
>> repository, will play an important role, so whoever wants to add an 
>> asterisk in my Projects and especially in slpkg, colored, sun, 
>> dropbox-filemanager, sbo-templates etc., I would appreciate it a lot!
>>
>> Thank you very much,
>> Dimitris
>>
>Done!

-- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220418/8ab31652/attachment.htm>

From d.zlatanidis at gmail.com  Mon Apr 18 12:14:26 2022
From: d.zlatanidis at gmail.com (Dimitris Zlatanidis)
Date: Mon, 18 Apr 2022 15:14:26 +0300
Subject: [Slackbuilds-users] Please your support
In-Reply-To: <FF094908-168B-411F-82C2-6E922C05B3EB@laposte.net>
References: <f44ea676-a959-ce5b-3984-65ab8c3945f3@gmail.com>
 <5467f88d-8b35-cce7-11d3-9593d4acfa3f@free.fr>
 <FF094908-168B-411F-82C2-6E922C05B3EB@laposte.net>
Message-ID: <f11156bf-a147-0161-b23c-18847fd73c15@gmail.com>

Thank you all for your support!!!

On 4/18/22 13:07, Arnaud via SlackBuilds-users wrote:
> Same here ??
>
> ? Yth.
>
> Le 18 avril 2022 10:03:10 UTC, marav <marav8 at free.fr> a ?crit?:
>
>     Le 17/04/2022 ? 19:55, Dimitris Zlatanidis a ?crit?:
>>     Greetings to all members,
>>
>>     I would like to ask for your support.
>>     I'm giving a job interview (Python Developer) and my Gitlab
>>     repository, will play an important role, so whoever wants to add
>>     an asterisk in my Projects and especially in slpkg, colored, sun,
>>     dropbox-filemanager, sbo-templates etc., I would appreciate it a
>>     lot!
>>
>>     Thank you very much,
>>     Dimitris
>>
>     Done!
>
> -- 
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ -https://slackbuilds.org/faq/
>

-- 
Dimitris Zlatanidis
https://dslackw.gitlab.io/slpkg/
https://gitlab.com/dslackw
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220418/3eadec51/attachment.htm>

From sbo at linuxgalaxy.org  Mon Apr 18 22:52:40 2022
From: sbo at linuxgalaxy.org (KB_SBo)
Date: Mon, 18 Apr 2022 22:52:40 +0000
Subject: [Slackbuilds-users] 'Correct' download link from Github?
In-Reply-To: <D916953B-9600-44C4-9A4F-223C051773A5@mixedsignals.ml>
References: <YlvLFIP3kl+a81Fa@ilium.andrews-corner.org>
 <YlvQ3YgiYeGV0ZW5@localhost>
 <D916953B-9600-44C4-9A4F-223C051773A5@mixedsignals.ml>
Message-ID: <a603a82f-e45d-e181-d8f6-c3611ed24de3@linuxgalaxy.org>

On 4/17/22 15:09, Klaatu wrote:
> This is a very common.  I think it would be nice to add an example of David's answer to the SlackBuild templates for both new and experienced maintainers.  I've wasted countless minutes looking up the "secret formula" when starting or updating my scripts.
>
> On 17 April 2022 8:33:33 AM UTC, Dave Woodfall <dave at slackbuilds.org> wrote:
>> On 17/04/22 18:08,
>> andrew <andrew.david.strong at gmail.com> put forth the proposition:
>>> I am putting a new Slackbuild together for opustags, which is hosted
>>> on github:
>>> https://github.com/fmang/opustags
>>> I am a little unsure of the correct download link from github which
>>> shows some variation whether wget or browser is used.
>>> Is there an SBo policy about such links?

I concur. Adding am example or "best practice" in the templates would be
handy. I can't even count the number of times I've gotten tripped up by
githubs "system".

-Ed




From erich.public at protonmail.com  Wed Apr 20 15:10:32 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Wed, 20 Apr 2022 15:10:32 +0000
Subject: [Slackbuilds-users] office/brscan4 (Brother scanner utility)
Message-ID: <_yeyxs1aM5otPpVwLe61yWGnGa4Bs3os1kBzrFE_Fz4A0VrHKwJVZheu1zgpI6WedHHnINrNO42XuS41nUcUfAxGSMklS4M8NDEUOXNjN2k=@protonmail.com>

Hello list,

I wrote a SlackBuild for brscan4 a while back; when submissions opened up for 15.0 2 things happened:

1. SBo admins rejected my submission due to download URL (see notes in README).
2. sane-airscan was added to SBo.

I tried out sane-airscan and it works for me, so I decided to use that instead and abandon brscan4.

However it occurred to me that maybe someone else would benefit from using brscan4 over sane-airscan, so here it is in case anyone would like to use it:

https://gitlab.com/ErichRitz/slackbuilds/-/tree/brscan4/office/brscan4

Erich


From belka at caraus.de  Wed Apr 20 18:31:49 2022
From: belka at caraus.de (Eugen Wissner)
Date: Wed, 20 Apr 2022 20:31:49 +0200
Subject: [Slackbuilds-users] office/brscan4 (Brother scanner utility)
In-Reply-To: <_yeyxs1aM5otPpVwLe61yWGnGa4Bs3os1kBzrFE_Fz4A0VrHKwJVZheu1zgpI6WedHHnINrNO42XuS41nUcUfAxGSMklS4M8NDEUOXNjN2k=@protonmail.com>
References: <_yeyxs1aM5otPpVwLe61yWGnGa4Bs3os1kBzrFE_Fz4A0VrHKwJVZheu1zgpI6WedHHnINrNO42XuS41nUcUfAxGSMklS4M8NDEUOXNjN2k=@protonmail.com>
Message-ID: <20220420183149.hld4tv2wnt43l73x@desktop.caraus.net>

Thanks. I was so lazy, that I installed brscan4 and a few more Brother's
utilities from their official rpms which works so far. But it would be
really nice to have native slackware packages. Also thanks for
mentioning sane-airscan - I didn't know about it.

Eugen

On Wed, Apr 20, 2022 at 03:10:32PM +0000, Erich Ritz via SlackBuilds-users wrote:
> Hello list,
> 
> I wrote a SlackBuild for brscan4 a while back; when submissions opened up for 15.0 2 things happened:
> 
> 1. SBo admins rejected my submission due to download URL (see notes in README).
> 2. sane-airscan was added to SBo.
> 
> I tried out sane-airscan and it works for me, so I decided to use that instead and abandon brscan4.
> 
> However it occurred to me that maybe someone else would benefit from using brscan4 over sane-airscan, so here it is in case anyone would like to use it:
> 
> https://gitlab.com/ErichRitz/slackbuilds/-/tree/brscan4/office/brscan4
> 
> Erich
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From arnaud.garcia-fernandez at laposte.net  Thu Apr 21 09:43:56 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Thu, 21 Apr 2022 11:43:56 +0200
Subject: [Slackbuilds-users] Updating Redis - and whats depends on it...
Message-ID: <20220421114356.eb324fab24048f4f28eb2bd5@laposte.net>

Hi everybody,

	I'm in the process of taking over Redis and updating it (from 4.0.9 released 4 years ago, to 6.2.6).
That works pretty nicely, but a few projects are depending on it, and are pretty outdated.

 - libraries/php-redis: May be bumped from 4.2.0 to 5.3.7, but seems to work fine anyway. Though its maintainer, Ebben Aries, hasn't been active in 2 years.
I will post an update for it, and if nobody maintains it by two weeks, I'll take over, as it is kinda linked to redis.

 - system/redis-py: Also very obsolete (2.10.5 is more than 6 years old !), builds for python2 (we ought to mercifully kill that beast), and its maintainer is very much active here.
So Dimitris, do you want me to handle that one for you ?

 - system/trmaid: builds on Python2 (again !?), but its dependencies are not all python2. Namely feedparser builds only Python3. Hence this will not work.
I don't very much want to take over that one, but I will update it if nobody does, just so that it works.

 - network/openvas-libraries: another outdated thingy. OpenVAS is still pretty much active, but it seems that openvas-libraries in itself doesn't exist anymore, the whole bunch of SlackBuilds relating to OpenVAS ought to be reworked, and I don't really want to do that. Its maintainer, Kent Fritz, seems inative for 1 year and a half. I won't do anything about it, and I don't know if updating Redis will break it, but since it doesn't build anyway (source isn't available anymore), that won't change much.
Maybe remove all (openvas-cli, openvas-scanner, openvas-libraries), if nobody wants to take over maintainership there ?

To summarize :
 - I will post updates for php-redis, redis-py and trmaid, if nobody steps up soon.
 - I will take over maitainership of php-redis in a few weeks if there is still no active maintainer.
 - I'm willing to take over redis-py from Dimitris Zlatanidis, because it seems pertinent since I will be maintainer of Redis itself.

 - I don't especially want to maintain trmaid, I'm just OK to make it work today.
 - I will not look into OpenVAS.


Cheers,

	- Yth / Arnaud

From poprocks at gmail.com  Thu Apr 21 17:17:29 2022
From: poprocks at gmail.com (Logan Rathbone)
Date: Thu, 21 Apr 2022 13:17:29 -0400
Subject: [Slackbuilds-users] meson template
Message-ID: <YmGRqS/tM3Yb47Ev@thinkpad.local.domain>

Hey all,

Couple of thoughts on the meson template.

First, --buildtype should probably be "plain" and not "release", because
"release" will stick a -O3 in there regardless of what CFLAGS are set
to -- yes, the CFLAGS passed in the standard template will follow and
override that, but it seems to be a cleaner approach to use "plain"
which will give full control over the debug and optimization flags.

I have seen some meson SlackBuilds that don't pass --buildtype at all,
and so what will land up happening there is, meson will default to
--buildtype=debug, which sticks a -g in there, so the standard Slackware
CFLAGS patched into the build command line will follow that, resulting
in an optimized build with debugging symbols. Yes, 'strip' will (I
assume) get rid of those, but it is leaving the door open for
unnecessary complexity and possible clashes that may serve to confuse.

As well, I would suggest -v be added to the ninja command, so that the
build command lines will actually show when the compile is happening,
similar to what a standard GNU make command would show. This will also
make it easier to track down issues with build flags (if any) that may
arise.

Thanks,
Logan (poprocks)

From belka at caraus.de  Fri Apr 22 16:37:45 2022
From: belka at caraus.de (Eugen Wissner)
Date: Fri, 22 Apr 2022 18:37:45 +0200
Subject: [Slackbuilds-users] Updating Redis - and whats depends on it...
In-Reply-To: <20220421114356.eb324fab24048f4f28eb2bd5@laposte.net>
References: <20220421114356.eb324fab24048f4f28eb2bd5@laposte.net>
Message-ID: <20220422163745.rdft6i6gisvbj6hf@desktop.caraus.net>

On Thu, Apr 21, 2022 at 11:43:56AM +0200, Arnaud via SlackBuilds-users wrote:
> Hi everybody,
> 
> 	I'm in the process of taking over Redis and updating it (from 4.0.9 released 4 years ago, to 6.2.6).
> That works pretty nicely, but a few projects are depending on it, and are pretty outdated.
> 
>  - libraries/php-redis: May be bumped from 4.2.0 to 5.3.7, but seems to work fine anyway. Though its maintainer, Ebben Aries, hasn't been active in 2 years.
> I will post an update for it, and if nobody maintains it by two weeks, I'll take over, as it is kinda linked to redis.

Can confirm this. I'm using redis 6.2.6 and php-redis 5.3.4 on a
production server for a while now and it works fine (if I remember
correctly, I used the original build scripts and only changed the
version).

> 
>  - system/redis-py: Also very obsolete (2.10.5 is more than 6 years old !), builds for python2 (we ought to mercifully kill that beast), and its maintainer is very much active here.
> So Dimitris, do you want me to handle that one for you ?
> 
>  - system/trmaid: builds on Python2 (again !?), but its dependencies are not all python2. Namely feedparser builds only Python3. Hence this will not work.
> I don't very much want to take over that one, but I will update it if nobody does, just so that it works.
> 
>  - network/openvas-libraries: another outdated thingy. OpenVAS is still pretty much active, but it seems that openvas-libraries in itself doesn't exist anymore, the whole bunch of SlackBuilds relating to OpenVAS ought to be reworked, and I don't really want to do that. Its maintainer, Kent Fritz, seems inative for 1 year and a half. I won't do anything about it, and I don't know if updating Redis will break it, but since it doesn't build anyway (source isn't available anymore), that won't change much.
> Maybe remove all (openvas-cli, openvas-scanner, openvas-libraries), if nobody wants to take over maintainership there ?
> 
> To summarize :
>  - I will post updates for php-redis, redis-py and trmaid, if nobody steps up soon.
>  - I will take over maitainership of php-redis in a few weeks if there is still no active maintainer.
>  - I'm willing to take over redis-py from Dimitris Zlatanidis, because it seems pertinent since I will be maintainer of Redis itself.
> 
>  - I don't especially want to maintain trmaid, I'm just OK to make it work today.
>  - I will not look into OpenVAS.
> 
> 
> Cheers,
> 
> 	- Yth / Arnaud
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From mjolnirdam at gmail.com  Fri Apr 22 20:24:47 2022
From: mjolnirdam at gmail.com (Damian Perticone)
Date: Fri, 22 Apr 2022 17:24:47 -0300
Subject: [Slackbuilds-users] hi, i cant remove tllist and fcft submisiion
Message-ID: <CAEW3CoH94+0ReRnAes0xODUTW+MB6F_2_M7bPw6UvWEy_KxVgw@mail.gmail.com>

it say file exist *;* a submission by the name 'tllist' is already pending
approval. i need to fix slac-desc files.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220422/6c4eda9b/attachment.htm>

From willysr at slackbuilds.org  Fri Apr 22 20:32:32 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 23 Apr 2022 03:32:32 +0700
Subject: [Slackbuilds-users] hi, i cant remove tllist and fcft submisiion
In-Reply-To: <CAEW3CoH94+0ReRnAes0xODUTW+MB6F_2_M7bPw6UvWEy_KxVgw@mail.gmail.com>
References: <CAEW3CoH94+0ReRnAes0xODUTW+MB6F_2_M7bPw6UvWEy_KxVgw@mail.gmail.com>
Message-ID: <0c954854-c8b0-b5f5-1a1e-d0691ff89481@slackbuilds.org>

> it say file exist *;* a submission by the name 'tllist' is already pending
> approval. i need to fix slac-desc files.

Now you can resubmit tllist, but i need to remove fuzzel and fcft as
well, so you need to resubmit again


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220423/d6920774/attachment.asc>

From b.pribs11 at gmail.com  Sat Apr 23 04:53:20 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Fri, 22 Apr 2022 21:53:20 -0700
Subject: [Slackbuilds-users] Modifying config.mk's CFLAGS variable
Message-ID: <CAC3J=Zab0+3BqUDbAnuPEHjdSBJPJRN063rKvhnKw62dr7mvfg@mail.gmail.com>

Hi,

I have a situation with an application I'm packaging. The CFLAGS variable,
et al in config.mk can't be prepended.

CFLAGS = -std=c99 ...

instead of

CFLAGS += -std=c99 ...

so as is I can't prepend $SLKFLAGS to $CFLAGS. It also contains an
optimization flag: -Os which conflicts with Slackware's.

The solution I came up with is to change '=' to '+='

sed -i '/CFLAGS/s/=/+=/' config.mk

and remove the optimization flag -Os

sed -i '/CFLAGS/s/-Os//' config.mk

This works fine but I would like to know if there is a more preferable
solution with a slackbuild.

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220422/bc201f82/attachment-0001.htm>

From dickson.tim at googlemail.com  Sat Apr 23 10:04:16 2022
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Sat, 23 Apr 2022 11:04:16 +0100
Subject: [Slackbuilds-users] Modifying config.mk's CFLAGS variable
In-Reply-To: <CAC3J=Zab0+3BqUDbAnuPEHjdSBJPJRN063rKvhnKw62dr7mvfg@mail.gmail.com>
References: <CAC3J=Zab0+3BqUDbAnuPEHjdSBJPJRN063rKvhnKw62dr7mvfg@mail.gmail.com>
Message-ID: <48620724-122e-9249-c2c8-c03e784d09d3@googlemail.com>

for longer term solution submit a patch upstream. you might want to 
check the optimization flag because some applications don't run 
well/have runtime issues with some flags. In those cases you don't want 
to override them. (I have at least one package with that issue.)
Regards Tim

On 23/04/2022 05:53, Brandon Pribula wrote:
> Hi,
>
> I have a situation with an application I'm packaging. The CFLAGS 
> variable, et al in config.mk <http://config.mk> can't be prepended.
>
> CFLAGS = -std=c99 ...
>
> instead of
>
> CFLAGS += -std=c99 ...
>
> so as is I can't prepend $SLKFLAGS to $CFLAGS. It also contains an 
> optimization flag: -Os which conflicts with Slackware's.
>
> The solution I came up with is to change '=' to '+='
>
> sed -i '/CFLAGS/s/=/+=/' config.mk <http://config.mk>
>
> and remove the optimization flag -Os
>
> sed -i '/CFLAGS/s/-Os//' config.mk <http://config.mk>
>
> This works fine but I would like to know if there is a more preferable 
> solution with a slackbuild.
>
> Thanks
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ -https://slackbuilds.org/faq/
>


-- 
This email has been checked for viruses by AVG.
https://www.avg.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220423/af19bddb/attachment.htm>

From willysr at slackbuilds.org  Sat Apr 23 19:13:27 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 24 Apr 2022 02:13:27 +0700
Subject: [Slackbuilds-users] Updates - 20220423.1
Message-ID: <f74ce8ca-0d04-4c64-c276-ca1046f0fadc@slackbuilds.org>

Hi all

our rejection rate is still a bit high for this week as some maintainer
haven't use our linting tool available from SBo
(https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/).
Please consider to install it and check your script (using sbolint)
before submitting.

You might want to use sbopkglint /tmp/<output-package>.tgz as well to
check the resulting binary for SBo compliance It's very helpful to
reduce our work of testing all the submissions during our spare time.

Please ensure your script is well tested before submitting. Don't abuse
the removal system to resend the fixes multiple times. It may cause your
submission email notification get lost

Sat Apr 23 18:49:13 UTC 2022
academic/FreeFem: Updated for version 4.11.
academic/avogadroapp: Added (graphic user interface of Avogadro 2)
academic/avogadrolibs: Added (Libraries for Avogadro 2)
academic/dakota: Added documentation.
academic/gcompris-qt: Updated for version 2.4.
academic/getfem: Added (finite element modeling software)
academic/gwyddion: Updated for version 2.60.
academic/molequeue: Updated for version 0.9.0.
academic/petsc: Added (toolkit for scientific computation).
academic/rpy2: Updated to version 3.5.1.
audio/JDSP4Linux: Added (Pipewire system equalizer).
audio/ncmpcpp: Updated for version 0.9.2.
audio/opustags: Added (View and edit Ogg Opus comments.)
desktop/Tela-icon-theme: Fix github tarball handling.
desktop/anki: Fix DOWNLOAD url.
desktop/bottles: Updated for version 2022.4.14.trento.2.
desktop/foot: Added (native wayland terminal emulator)
desktop/fuzzel: Added (wayland native application launcher)
desktop/qtile: Updated README.
desktop/yambar: Added (status panel for X11 and Wayland)
development/Catch: Fix docs; make self-test optional.
development/ghex: Update for 42.1
development/jupyter-notebook: Updated for version 6.4.11.
development/jupyter_core: Updated for version 4.10.0.
development/jupyterlab_pygments: Revert to version 0.1.2.
development/kotlin: Updated for version 1.6.21.
development/mongodb-compass: Updated for version 1.31.2.
development/mysql-workbench: Add upstream patch.
development/neovim: Updated for version 0.7.0.
development/openjdk7: Fix script.
development/openjdk8: Updated for version 8u322.
development/portaudio: new maintainer.
development/protobuf3: Updated for version 3.20.0.
development/valgrind: Updated for version .
games/0ad-data: Updated for version 0.0.25b.
games/0ad: Updated for version 0.0.25b.
games/lutris: Updated to 0.5.10
games/mgba: Updated for version 0.9.3.
games/nestopia: Updated for version 1.51.1.
games/ppsspp: Updated for version 1.12.3.
gis/google-earth: Use correct VERSION.
gis/python3-pyproj: Updated for version 3.3.1
graphics/vuescan: Updated for version 9.7.83.
ham/qt-dab: Added (Software DAB Decoder)
libraries/Botan: Fix docs.
libraries/CCfits: Fix docs.
libraries/CGAL: Fix man page location.
libraries/DevIL: Fix docs.
libraries/FormEncode: Fix docs.
libraries/GLee: Fix docs.
libraries/Geraldo: Fix docs.
libraries/HawkNL: Fix symlinks, rm static lib.
libraries/Impacket: Fix docs.
libraries/SDL_gfx: Fix docs.
libraries/VitaMTP: Fix docs.
libraries/antlr4: Updated for version 4.10.1.
libraries/avr-libc: Fix PRINT_PACKAGE_NAME.
libraries/barry: Fix docs.
libraries/belle-sip: Fix docs.
libraries/bullet: Updated for version 3.22b.
libraries/bzrtp: Fix docs.
libraries/cloog: Fix PRINT_PACKAGE_NAME.
libraries/clutter-gtk: Added (GTK+ Integration library for Clutter).
libraries/clutter: Added (OpenGL based interactive canvas library).
libraries/cogl: Fix build with multiple jobs.
libraries/compface: Strip libraries.
libraries/ctemplate: Strip libraries.
libraries/edelib: Fix docs.
libraries/fcft: Added (font loading and glyph rasterization library)
libraries/fcgi: Fix docs.
libraries/ffms2: Fix docs.
libraries/fmt: Updated for version 8.1.1.
libraries/gconfmm: Fix docs.
libraries/gdata: Fix docs.
libraries/genshi: Strip library.
libraries/gf2x: Fix docs, mention SSE2 in README.
libraries/giblib: Fix docs.
libraries/gmtk: Fix docs.
libraries/goffice0.8: Fix docs.
libraries/goffice: Fix docs.
libraries/grx: Fix docs, disable parallel builds.
libraries/gsm: Fix build.
libraries/gsound: Fix docs.
libraries/gspell: Fix PRINT_PACKAGE_NAME.
libraries/gtk-sharp: Fix docs.
libraries/gtkhtml: Fix doc, doinst.sh.
libraries/htslib: Fix MD5SUM.
libraries/iniparser: Use SLKCFLAGS, fix shared lib, rm static.
libraries/jbigkit: Strip binaries.
libraries/libEMF: Remove .la files.
libraries/libasr: Fix man page permissions.
libraries/libchamplain: Added (C library).
libraries/libcitadel: Strip library.
libraries/libclaw: Fix docs, rm static libs.
libraries/libcoap: Make API docs optional.
libraries/libcryptui: Add doinst.sh, fix icons.
libraries/libdatrie: Fix docs.
libraries/libdbi-drivers: fixup the postgres flags
libraries/libdbus-c++: Fix docs.
libraries/libdca: Fix docs, broken symlink.
libraries/libdca: New maintainer.
libraries/libeatmydata: Fix PRINT_PACKAGE_NAME.
libraries/libetpan: Fix docs.
libraries/libfastjson: Fix docs.
libraries/libgaminggear: Fix docs.
libraries/libgnomecups: Strip library.
libraries/libgringotts: Fix docs.
libraries/libhtp: Fix docs.
libraries/libiptcdata: Fix docs.
libraries/libircclient: Fix PRINT_PACKAGE_NAME.
libraries/libkate: Remove static lib, fix docs.
libraries/libmaa: Strip binaries.
libraries/libmimic: Fix docs.
libraries/libmms: Fix docs.
libraries/libmspack: Fix docs.
libraries/liboauth: Strip lib, fix PRINT_PACKAGE_NAME.
libraries/liboglappth: Fix docs.
libraries/libopenshot-audio: Make API doc optional.
libraries/liborigin: Fix docs.
libraries/libotf: Fix docs.
libraries/libpar2: Fix docs.
libraries/libpgf: Remove dos2unix dep; fix docs.
libraries/libprelude: Strip binaries.
libraries/librcd: Fix docs.
libraries/libshout: New maintainer.
libraries/libsieve: Strip binaries, fix tarball handling.
libraries/libsmdev: Fix docs.
libraries/libsoup3: Fix PRINT_PACKAGE_NAME.
libraries/libticables2: Strip binaries.
libraries/libticonv: Strip lib, fix docs.
libraries/libtorrent-rasterbar: Fix PRINT_PACKAGE_NAME, strip.
libraries/libtorrent: Fix docs.
libraries/libtpms: Added (library for emulating TPM 1.2 and 2.0)
libraries/libuchardet: Fix docs.
libraries/libuinputplus: Fix PRINT_PACKAGE_NAME.
libraries/libxfcegui4: Fix docs.
libraries/libxlsxwriter: Fix docs.
libraries/libxmi: Fix docs.
libraries/libxmp: Fix PRINT_PACKAGE_NAME.
libraries/libxnvctrl: Strip shared libary.
libraries/live555: Update maintainer.
libraries/lksctp-tools: Fix docs.
libraries/log4shib: Fix conflict with graphviz.
libraries/lua-luv: Updated for version 1.43.0_0.
libraries/lxqt-notificationd: Fix .desktop, add doinst.sh.
libraries/mbedtls: Fix PRINT_PACKAGE_NAME.
libraries/meanwhile: Fix docs.
libraries/msgpack-c: Fix docs.
libraries/mujs: Fix docs.
libraries/mxml: Fix docs, rm static lib.
libraries/mysql-connector-c++: Fix docs.
libraries/mysqltcl: Fix docs.
libraries/nlohmann_json: Added (JSON for Modern C++)
libraries/nlopt: Fix (gzip) man pages.
libraries/ogre: Fix docs.
libraries/onevpl: Fix docs.
libraries/opencl-amd: Fix package filename, docs.
libraries/paho-mqtt: Fix PRINT_PACKAGE_NAME.
libraries/pangox-compat: Fix docs.
libraries/pidgin-mra: Fix icon permissions.
libraries/podofo: Fix PRINT_PACKAGE_NAME.
libraries/progressbar: Fix PRINT_PACKAGE_NAME.
libraries/ptypes: Fix docs.
libraries/qt3: Fix docs, doinst, symlink.
libraries/qwt: Don't build examples by defalt.
libraries/rapidjson: Fix docs.
libraries/spdlog: Strip binaries.
libraries/tDOM: Fix tarball handling.
libraries/tclap: Make API docs optional.
libraries/tcllib: Fix docs.
libraries/tllist: Added (typed linked list c header file)
libraries/tlsh: Fix docs.
libraries/totem-pl-parser: Strip binaries.
libraries/udunits: Fix docs.
libraries/ulfius: Fix docs.
libraries/vdk: Fix man page.
libraries/vigra: Fix docs.
libraries/wcslib: Fix permissions, rm static lib.
libraries/webkit2gtk4.1: Fix PRINT_PACKAGE_NAME.
libraries/webkit2gtk: Fix PRINT_PACKAGE_NAME.
libraries/wxGTK3: Make API docs optional.
libraries/xapian-bindings: Do not include /tmp in the package.
libraries/xforms: Strip demos.
libraries/xlt: Fix docs.
libraries/xmpppy: Fix docs.
libraries/xview: Fix docs.
misc/fcitx-mozc: Updated for version 2.26.4220.102.1.
misc/simh-classic: Gzip patch to preserve line endings.
multimedia/haruna: Updated for version 0.8.0.
multimedia/openshot: Fix doinst.sh, stop spamming /usr.
multimedia/zvbi: Update maintainer. Template fixes.
network/axel: Updated for version 2.17.11.
network/brave-browser: Fix BUILD variable usage.
network/dropbear: Updated for version 2022.82.
network/element-desktop: Updated for version 1.10.10.
network/franz: Updated for version 5.9.2.
network/hostapd: Updated for version 2.10.
network/isync: Updated for version 1.4.4.
network/mailspring: Updated for version 1.10.3
network/microsoft-edge: Update for version 100.0.1185.50.
network/mrtg: Update maintainer email
network/signal-desktop: Updated for version 5.40.1.
network/skypeforlinux: Updated for version 8.83.0.408.
network/sslscan: Updated for version 2.0.13.
network/strongswan: Updated for version 5.9.5.
network/teamviewer: Added (remote control application).
network/telegram: Updated for version 3.7.0.
network/zoom-linux: Updated for version 5.10.3.2778.
office/MasterPDFEditor: Updated for version 5.8.49.
office/etmtk: Updated for version 3.2.39.
office/gnucash: Update DEP.
office/hunspell-en: Update for 2020.12.07 (+new maintainer)
office/pdfarranger: moved from python; adapted doinst.sh for icons
office/tudu: Updated for version 0.10.4.
python/objgraph: Added (Python Module).
python/pikepdf: Updated to version 5.1.2.
python/python-xkbcommon: Fix github tarball handling.
python/python3-pytest-cov: Added (coverage plugin for pytest)
ruby/ruby-build: Updated for version 20220324.
ruby/sequel: Updated for version 5.55.0.
system/brlaser: Added (CUPS driver for Brother laser printers).
system/efiboots: Added (GTK3 frontend for efibootmgr).
system/evolution-data-server: Fix script.
system/fish: Remove /usr/share/doc, fix doinst.sh.
system/fswatch: Updated for version 1.16.0.
system/mpollux-digisign-client: Added (smart card middleware).
system/netdata: Updated for version 1.34.1.
system/osquery-bin: Updated for version 5.2.3.
system/pcem: update to version f4a1ab9.20220418
system/prometheus: Updated for version 2.35.0.
system/scdoc: Updated for version 1.11.2.
system/swapinzram: Added (Configure a swap block device in RAM).
system/trash-cli: Update for 0.22.4.16 (+new maintainer)
system/trousers: Added (TSS implementation by IBM)
system/winetricks: Update for 20220411 (+new maintainer)
system/xen: Updated for version 4.16.1.
system/yelp: Update README.
+--------------------------+


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/82de15f6/attachment.asc>

From 1.41421 at gmail.com  Sat Apr 23 21:07:13 2022
From: 1.41421 at gmail.com (Luveh Keraph)
Date: Sat, 23 Apr 2022 15:07:13 -0600
Subject: [Slackbuilds-users] netdata fails to build
Message-ID: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>

The latest netdata package fails to build on my Slackware64 15.0 boxes:

  CC       database/rrd.o
  CC       database/rrdset.o
  CC       database/rrdsetvar.o
  CC       database/rrdvar.o
  CC       database/sqlite/sqlite_functions.o
  CC       database/sqlite/sqlite_aclk.o
In file included from database/sqlite/../../aclk/aclk.h:6,
                 from database/sqlite/sqlite_aclk.c:10:
database/sqlite/../../aclk/aclk_util.h:6:10: fatal error:
mqtt_wss_client.h: No such file or directory
    6 | #include "mqtt_wss_client.h"
      |          ^~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [Makefile:5610: database/sqlite/sqlite_aclk.o] Error 1
make[2]: Leaving directory '/tmp/SBo/netdata-1.34.1'
make[1]: *** [Makefile:6322: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/netdata-1.34.1'
make: *** [Makefile:3455: all] Error 2

There is indeed no mqtt_wss_client.h file in my systems.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220423/acc92fa8/attachment.htm>

From ozan.turkyilmaz at gmail.com  Sat Apr 23 22:11:44 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Sun, 24 Apr 2022 01:11:44 +0300
Subject: [Slackbuilds-users] Updates - 20220423.1
In-Reply-To: <f74ce8ca-0d04-4c64-c276-ca1046f0fadc@slackbuilds.org>
References: <f74ce8ca-0d04-4c64-c276-ca1046f0fadc@slackbuilds.org>
Message-ID: <ee65c0d1783a5b17fb05e89e34fcf61a4caabffa.camel@gmail.com>

Paz, 2022-04-24 tarihinde 02:13 +0700 saatinde, Willy Sudiarto Raharjo
yazd?:
> Hi all
> 
> games/lutris: Updated to 0.5.10
I hope it will fine for everybody. As far as I can see, meson just
works better for installation than setuptools. Upstream always warns
against using setuptools to install and instead recommends to run it
inside the folder directly.

Regards,
Ozan

From willysr at slackbuilds.org  Sun Apr 24 01:07:22 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 24 Apr 2022 08:07:22 +0700
Subject: [Slackbuilds-users] netdata fails to build
In-Reply-To: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>
References: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>
Message-ID: <75b0e327-d51e-ec96-4418-2127bdbb23f5@slackbuilds.org>

> The latest netdata package fails to build on my Slackware64 15.0 boxes:
> 
>   CC       database/rrd.o
>   CC       database/rrdset.o
>   CC       database/rrdsetvar.o
>   CC       database/rrdvar.o
>   CC       database/sqlite/sqlite_functions.o
>   CC       database/sqlite/sqlite_aclk.o
> In file included from database/sqlite/../../aclk/aclk.h:6,
>                  from database/sqlite/sqlite_aclk.c:10:
> database/sqlite/../../aclk/aclk_util.h:6:10: fatal error:
> mqtt_wss_client.h: No such file or directory
>     6 | #include "mqtt_wss_client.h"
>       |          ^~~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[2]: *** [Makefile:5610: database/sqlite/sqlite_aclk.o] Error 1
> make[2]: Leaving directory '/tmp/SBo/netdata-1.34.1'
> make[1]: *** [Makefile:6322: all-recursive] Error 1
> make[1]: Leaving directory '/tmp/SBo/netdata-1.34.1'
> make: *** [Makefile:3455: all] Error 2
> 
> There is indeed no mqtt_wss_client.h file in my systems.

I built this on a clean VM and it works fine
can you check if you have other third party packages? maybe it picks up
and requires a new deps


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/6ef89242/attachment.asc>

From fourtysixandtwo at sliderr.net  Sun Apr 24 01:18:56 2022
From: fourtysixandtwo at sliderr.net (fourtysix andtwo)
Date: Sat, 23 Apr 2022 19:18:56 -0600
Subject: [Slackbuilds-users] fmt update breaks spdlog build
Message-ID: <CAAZ8Haif=AHsyL77-Gt_OLSyrEuK8PPyeLVEkpqMjnDCcVLkmg@mail.gmail.com>

Hi all.

If fmt-8.1.1 is installed spdlog-1.8.1 will fail to build.

Updating to spdlog-1.10.0 fixes the issue and is noted in the release notes
on github.

I've attached the update patch.

Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220423/3ed0739c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-libraries-spdlog-Updated-for-version-1.10.0.patch
Type: text/x-patch
Size: 1355 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220423/3ed0739c/attachment.bin>

From fourtysixandtwo at sliderr.net  Sun Apr 24 01:34:49 2022
From: fourtysixandtwo at sliderr.net (fourtysix andtwo)
Date: Sat, 23 Apr 2022 19:34:49 -0600
Subject: [Slackbuilds-users] fmt update breaks spdlog build
In-Reply-To: <CAAZ8Haif=AHsyL77-Gt_OLSyrEuK8PPyeLVEkpqMjnDCcVLkmg@mail.gmail.com>
References: <CAAZ8Haif=AHsyL77-Gt_OLSyrEuK8PPyeLVEkpqMjnDCcVLkmg@mail.gmail.com>
Message-ID: <CAAZ8Hahz5Yk4dY-5415jtF=HtO0V8PWBG5=vqRaUgF-3N0jKdA@mail.gmail.com>

Ignore the previous patch as I forgot to bump the BUILD variable back to
1.

Cheers




On Sat, Apr 23, 2022 at 7:18 PM fourtysix andtwo <
fourtysixandtwo at sliderr.net> wrote:

> Hi all.
>
> If fmt-8.1.1 is installed spdlog-1.8.1 will fail to build.
>
> Updating to spdlog-1.10.0 fixes the issue and is noted in the release
> notes on github.
>
> I've attached the update patch.
>
> Cheers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220423/66c591d6/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-libraries-spdlog-Updated-for-version-1.10.0.patch
Type: text/x-patch
Size: 1378 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220423/66c591d6/attachment.bin>

From 1.41421 at gmail.com  Sun Apr 24 01:47:59 2022
From: 1.41421 at gmail.com (Luveh Keraph)
Date: Sat, 23 Apr 2022 19:47:59 -0600
Subject: [Slackbuilds-users] netdata fails to build
In-Reply-To: <75b0e327-d51e-ec96-4418-2127bdbb23f5@slackbuilds.org>
References: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>
 <75b0e327-d51e-ec96-4418-2127bdbb23f5@slackbuilds.org>
Message-ID: <CAFy1yb01RNPrjKFMyzz-DgrMQ5uq0HNKDJ+jExif0wtav7JAPg@mail.gmail.com>

Its page at slackbuilds.org says that python2-PyYAML is the only dependency
- which is already installed in my systems.  nodejs, psycopg2 and
MySQL-python are listed as optional dependencies.  Since you have been able
to build it, and unless the build process somehow defaults to
different options in your system than it does in mine, you must
have mqtt_wss_client.h.h somewhere in your system. Could you possibly tell
what package installs it? It is in none of the packages listed under
/var/log/packages in mine.

Anyway, this seems to be something already noticed a few months ago - check
out https://github.com/netdata/netdata/issues/11652.

On Sat, Apr 23, 2022 at 7:07 PM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > The latest netdata package fails to build on my Slackware64 15.0 boxes:
> >
> >   CC       database/rrd.o
> >   CC       database/rrdset.o
> >   CC       database/rrdsetvar.o
> >   CC       database/rrdvar.o
> >   CC       database/sqlite/sqlite_functions.o
> >   CC       database/sqlite/sqlite_aclk.o
> > In file included from database/sqlite/../../aclk/aclk.h:6,
> >                  from database/sqlite/sqlite_aclk.c:10:
> > database/sqlite/../../aclk/aclk_util.h:6:10: fatal error:
> > mqtt_wss_client.h: No such file or directory
> >     6 | #include "mqtt_wss_client.h"
> >       |          ^~~~~~~~~~~~~~~~~~~
> > compilation terminated.
> > make[2]: *** [Makefile:5610: database/sqlite/sqlite_aclk.o] Error 1
> > make[2]: Leaving directory '/tmp/SBo/netdata-1.34.1'
> > make[1]: *** [Makefile:6322: all-recursive] Error 1
> > make[1]: Leaving directory '/tmp/SBo/netdata-1.34.1'
> > make: *** [Makefile:3455: all] Error 2
> >
> > There is indeed no mqtt_wss_client.h file in my systems.
>
> I built this on a clean VM and it works fine
> can you check if you have other third party packages? maybe it picks up
> and requires a new deps
>
>
> --
> Willy Sudiarto Raharjo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220423/4ad5bffd/attachment.htm>

From willysr at slackbuilds.org  Sun Apr 24 02:07:39 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 24 Apr 2022 09:07:39 +0700
Subject: [Slackbuilds-users] fmt update breaks spdlog build
In-Reply-To: <CAAZ8Haif=AHsyL77-Gt_OLSyrEuK8PPyeLVEkpqMjnDCcVLkmg@mail.gmail.com>
References: <CAAZ8Haif=AHsyL77-Gt_OLSyrEuK8PPyeLVEkpqMjnDCcVLkmg@mail.gmail.com>
Message-ID: <01ddd588-c320-4cf2-93bb-f1518ace8ac5@slackbuilds.org>

> If fmt-8.1.1 is installed spdlog-1.8.1 will fail to build.
> 
> Updating to spdlog-1.10.0 fixes the issue and is noted in the release notes
> on github.
> 
> I've attached the update patch.

Applied on my branch

thanks


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/316867e3/attachment-0001.asc>

From willysr at slackbuilds.org  Sun Apr 24 02:09:48 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 24 Apr 2022 09:09:48 +0700
Subject: [Slackbuilds-users] netdata fails to build
In-Reply-To: <CAFy1yb01RNPrjKFMyzz-DgrMQ5uq0HNKDJ+jExif0wtav7JAPg@mail.gmail.com>
References: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>
 <75b0e327-d51e-ec96-4418-2127bdbb23f5@slackbuilds.org>
 <CAFy1yb01RNPrjKFMyzz-DgrMQ5uq0HNKDJ+jExif0wtav7JAPg@mail.gmail.com>
Message-ID: <4219dbd5-5bdc-ed51-4980-5d4b126c4a5f@slackbuilds.org>

> Its page at slackbuilds.org says that python2-PyYAML is the only dependency
> - which is already installed in my systems.  nodejs, psycopg2 and
> MySQL-python are listed as optional dependencies.  Since you have been able
> to build it, and unless the build process somehow defaults to
> different options in your system than it does in mine, you must
> have mqtt_wss_client.h.h somewhere in your system. Could you possibly tell
> what package installs it? It is in none of the packages listed under
> /var/log/packages in mine.

I checked and there wasn't any file named mqtt_wss_client.h on my vm


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/b0a4520e/attachment.asc>

From b.pribs11 at gmail.com  Sun Apr 24 07:04:28 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Sun, 24 Apr 2022 00:04:28 -0700
Subject: [Slackbuilds-users] Modifying config.mk's CFLAGS variable
In-Reply-To: <48620724-122e-9249-c2c8-c03e784d09d3@googlemail.com>
References: <CAC3J=Zab0+3BqUDbAnuPEHjdSBJPJRN063rKvhnKw62dr7mvfg@mail.gmail.com>
 <48620724-122e-9249-c2c8-c03e784d09d3@googlemail.com>
Message-ID: <CAC3J=ZYV_5k0O14-SMfCpAn7Y2v_NWHrhXJD=+Sw7vnbLY9sqA@mail.gmail.com>

On Sat, Apr 23, 2022, 3:04 AM Tim Dickson via SlackBuilds-users, <
slackbuilds-users at slackbuilds.org> wrote:

> for longer term solution submit a patch upstream. you might want to check
> the optimization flag because some applications don't run well/have runtime
> issues with some flags. In those cases you don't want to override them. (I
> have at least one package with that issue.)
> Regards Tim
>
> On 23/04/2022 05:53, Brandon Pribula wrote:
>
> Hi,
>
> I have a situation with an application I'm packaging. The CFLAGS variable,
> et al in config.mk can't be prepended.
>
> CFLAGS = -std=c99 ...
>
> instead of
>
> CFLAGS += -std=c99 ...
>
> so as is I can't prepend $SLKFLAGS to $CFLAGS. It also contains an
> optimization flag: -Os which conflicts with Slackware's.
>
> The solution I came up with is to change '=' to '+='
>
> sed -i '/CFLAGS/s/=/+=/' config.mk
>
> and remove the optimization flag -Os
>
> sed -i '/CFLAGS/s/-Os//' config.mk
>
> This works fine but I would like to know if there is a more preferable
> solution with a slackbuild.
>
> Thanks
>
> _______________________________________________
> SlackBuilds-users mailing listSlackBuilds-users at slackbuilds.orghttps://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
>
> ------------------------------
> [image: AVG logo] <https://www.avg.com/internet-security>
>
> This email has been checked for viruses by AVG antivirus software.
> www.avg.com <https://www.avg.com/internet-security>
>
> <#m_9096267948796403190_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/


Thanks for the reply, Tim.

The optimization it uses is -Os, which is optimize for size. I will test
more tomorrow with and without that flag but I will probably just keep it
as upstream intended.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/fc889491/attachment.htm>

From 1.41421 at gmail.com  Sun Apr 24 14:04:23 2022
From: 1.41421 at gmail.com (Luveh Keraph)
Date: Sun, 24 Apr 2022 08:04:23 -0600
Subject: [Slackbuilds-users] netdata fails to build
In-Reply-To: <4219dbd5-5bdc-ed51-4980-5d4b126c4a5f@slackbuilds.org>
References: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>
 <75b0e327-d51e-ec96-4418-2127bdbb23f5@slackbuilds.org>
 <CAFy1yb01RNPrjKFMyzz-DgrMQ5uq0HNKDJ+jExif0wtav7JAPg@mail.gmail.com>
 <4219dbd5-5bdc-ed51-4980-5d4b126c4a5f@slackbuilds.org>
Message-ID: <CAFy1yb3ptGFGiteUkFMVqS_m=gO=OPWXuYeHwimx+7zF0=xoAg@mail.gmail.com>

The problem starts with the protobuf3 package. When this package is
installed, the netdata build framework assumes that the new cloud protocol
(whatever it is) is to be used. It therefore defines some internal symbol
that causes it to attempt to include the mqtt_wss_client.h file. This file
is part of the netdata source code - but only when the netdata source code
tarball has been created correctly from the netdata git repository - i.e.
with something like git clone https://github.com/netdata/netdata.git
--depth=100 --recursive.  At any rate, the tarball that one downloads using
the link specified in slackbuilds.org for netdata does not contain that
include file (nor the ancillary source code files) hence the build failure
that I reported.

In a nutshell, such as things currently are, under Slackware64 15.0 the
latest release of netdata will not build if protobuf3 is already installed.


On Sat, Apr 23, 2022 at 8:09 PM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > Its page at slackbuilds.org says that python2-PyYAML is the only
> dependency
> > - which is already installed in my systems.  nodejs, psycopg2 and
> > MySQL-python are listed as optional dependencies.  Since you have been
> able
> > to build it, and unless the build process somehow defaults to
> > different options in your system than it does in mine, you must
> > have mqtt_wss_client.h.h somewhere in your system. Could you possibly
> tell
> > what package installs it? It is in none of the packages listed under
> > /var/log/packages in mine.
>
> I checked and there wasn't any file named mqtt_wss_client.h on my vm
>
>
> --
> Willy Sudiarto Raharjo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/03c535cf/attachment.htm>

From willysr at slackbuilds.org  Sun Apr 24 14:28:37 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 24 Apr 2022 21:28:37 +0700
Subject: [Slackbuilds-users] netdata fails to build
In-Reply-To: <CAFy1yb3ptGFGiteUkFMVqS_m=gO=OPWXuYeHwimx+7zF0=xoAg@mail.gmail.com>
References: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>
 <75b0e327-d51e-ec96-4418-2127bdbb23f5@slackbuilds.org>
 <CAFy1yb01RNPrjKFMyzz-DgrMQ5uq0HNKDJ+jExif0wtav7JAPg@mail.gmail.com>
 <4219dbd5-5bdc-ed51-4980-5d4b126c4a5f@slackbuilds.org>
 <CAFy1yb3ptGFGiteUkFMVqS_m=gO=OPWXuYeHwimx+7zF0=xoAg@mail.gmail.com>
Message-ID: <c4945925-4191-2efb-21bc-941b1655e5f3@slackbuilds.org>

> The problem starts with the protobuf3 package. When this package is
> installed, the netdata build framework assumes that the new cloud protocol
> (whatever it is) is to be used. It therefore defines some internal symbol
> that causes it to attempt to include the mqtt_wss_client.h file. This file
> is part of the netdata source code - but only when the netdata source code
> tarball has been created correctly from the netdata git repository - i.e.
> with something like git clone https://github.com/netdata/netdata.git
> --depth=100 --recursive.  At any rate, the tarball that one downloads using
> the link specified in slackbuilds.org for netdata does not contain that
> include file (nor the ancillary source code files) hence the build failure
> that I reported.
> 
> In a nutshell, such as things currently are, under Slackware64 15.0 the
> latest release of netdata will not build if protobuf3 is already installed.

Probably best i can do is add a note in README


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/0bf37e51/attachment.asc>

From urchlay at slackware.uk  Sun Apr 24 14:40:41 2022
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 24 Apr 2022 10:40:41 -0400 (EDT)
Subject: [Slackbuilds-users] Modifying config.mk's CFLAGS variable
In-Reply-To: <CAC3J=Zab0+3BqUDbAnuPEHjdSBJPJRN063rKvhnKw62dr7mvfg@mail.gmail.com>
References: <CAC3J=Zab0+3BqUDbAnuPEHjdSBJPJRN063rKvhnKw62dr7mvfg@mail.gmail.com>
Message-ID: <ed4d1e17-1198-f3de-178d-4233823a46a9@slackware.uk>



On Fri, 22 Apr 2022, Brandon Pribula wrote:

> The solution I came up with is to change '=' to '+='
> 
> sed -i '/CFLAGS/s/=/+=/' config.mk
> 
> and remove the optimization flag -Os
> 
> sed -i '/CFLAGS/s/-Os//' config.mk
> 
> This works fine but I would like to know if there is a more preferable
> solution with a slackbuild.

That sounds like it should work fine. I might have sedded the
flags directly in:

sed -i "/CFLAGS/s,-Os,$SLKCFLAGS," config.mk

...but there's nothing wrong with the way you did it.

From urchlay at slackware.uk  Sun Apr 24 14:42:41 2022
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 24 Apr 2022 10:42:41 -0400 (EDT)
Subject: [Slackbuilds-users] netdata fails to build
In-Reply-To: <CAFy1yb3ptGFGiteUkFMVqS_m=gO=OPWXuYeHwimx+7zF0=xoAg@mail.gmail.com>
References: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>
 <75b0e327-d51e-ec96-4418-2127bdbb23f5@slackbuilds.org>
 <CAFy1yb01RNPrjKFMyzz-DgrMQ5uq0HNKDJ+jExif0wtav7JAPg@mail.gmail.com>
 <4219dbd5-5bdc-ed51-4980-5d4b126c4a5f@slackbuilds.org>
 <CAFy1yb3ptGFGiteUkFMVqS_m=gO=OPWXuYeHwimx+7zF0=xoAg@mail.gmail.com>
Message-ID: <639ffde-5dec-2b7b-33c-13f61a2b845c@slackware.uk>



On Sun, 24 Apr 2022, Luveh Keraph wrote:

> In a nutshell, such as things currently are, under Slackware64 15.0 the
> latest release of netdata will not build if protobuf3 is already?installed.

Is there no --disable-protobuf3 or similar?

From 1.41421 at gmail.com  Sun Apr 24 15:01:14 2022
From: 1.41421 at gmail.com (Luveh Keraph)
Date: Sun, 24 Apr 2022 09:01:14 -0600
Subject: [Slackbuilds-users] netdata fails to build
In-Reply-To: <639ffde-5dec-2b7b-33c-13f61a2b845c@slackware.uk>
References: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>
 <75b0e327-d51e-ec96-4418-2127bdbb23f5@slackbuilds.org>
 <CAFy1yb01RNPrjKFMyzz-DgrMQ5uq0HNKDJ+jExif0wtav7JAPg@mail.gmail.com>
 <4219dbd5-5bdc-ed51-4980-5d4b126c4a5f@slackbuilds.org>
 <CAFy1yb3ptGFGiteUkFMVqS_m=gO=OPWXuYeHwimx+7zF0=xoAg@mail.gmail.com>
 <639ffde-5dec-2b7b-33c-13f61a2b845c@slackware.uk>
Message-ID: <CAFy1yb1ucEhPQu1XJbrxk46UqLT7VMSLjH=r0YLZce5Oh9P=9w@mail.gmail.com>

The configure invocation in netdata.Slackbuild could indeed be changed so
that the --without-new-cloud-protocol option is used. In truth, however,
the problem is in the way in which the netdata source code tarball is
created by the netdata people.

On Sun, Apr 24, 2022 at 8:42 AM B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Sun, 24 Apr 2022, Luveh Keraph wrote:
>
> > In a nutshell, such as things currently are, under Slackware64 15.0 the
> > latest release of netdata will not build if protobuf3 is
> already installed.
>
> Is there no --disable-protobuf3 or
> similar?_______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/f6823764/attachment.htm>

From 1.41421 at gmail.com  Sun Apr 24 15:22:25 2022
From: 1.41421 at gmail.com (Luveh Keraph)
Date: Sun, 24 Apr 2022 09:22:25 -0600
Subject: [Slackbuilds-users] netdata fails to build
In-Reply-To: <CAFy1yb1ucEhPQu1XJbrxk46UqLT7VMSLjH=r0YLZce5Oh9P=9w@mail.gmail.com>
References: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>
 <75b0e327-d51e-ec96-4418-2127bdbb23f5@slackbuilds.org>
 <CAFy1yb01RNPrjKFMyzz-DgrMQ5uq0HNKDJ+jExif0wtav7JAPg@mail.gmail.com>
 <4219dbd5-5bdc-ed51-4980-5d4b126c4a5f@slackbuilds.org>
 <CAFy1yb3ptGFGiteUkFMVqS_m=gO=OPWXuYeHwimx+7zF0=xoAg@mail.gmail.com>
 <639ffde-5dec-2b7b-33c-13f61a2b845c@slackware.uk>
 <CAFy1yb1ucEhPQu1XJbrxk46UqLT7VMSLjH=r0YLZce5Oh9P=9w@mail.gmail.com>
Message-ID: <CAFy1yb0r_+0s8ccK7JxjR8+ZJk8rF7wMjZw6B_drZJhqiV5BVA@mail.gmail.com>

Just for completeness:

1. If one adds --without-new-cloud-protocol to the configure invocation in
netdata.Slackbuild then the build process completes successfully even when
protobuf3 is installed.
2. If one uses a netdata-1.34.1.tar.gz tarball created from the netdata git
repository as cloned with the git command that I mentioned in a previous
email, the build process completes successfully when protobuf3 is present
and netdata.Slackbuild is unmodified.  I assume things run as expected with
netdata from this point onward, but that's a different story.

The responsibility falls entirely on the shoulders of whoever is tasked
with creating the netdata source code tarball that the Slackbuilds link has
us download. I would have thought that, out of the two options above it
would make more sense to adopt option 1, until such time that the netdata
people package the netdata sources correctly.

On Sun, Apr 24, 2022 at 9:01 AM Luveh Keraph <1.41421 at gmail.com> wrote:

> The configure invocation in netdata.Slackbuild could indeed be changed so
> that the --without-new-cloud-protocol option is used. In truth, however,
> the problem is in the way in which the netdata source code tarball is
> created by the netdata people.
>
> On Sun, Apr 24, 2022 at 8:42 AM B. Watson <urchlay at slackware.uk> wrote:
>
>>
>>
>> On Sun, 24 Apr 2022, Luveh Keraph wrote:
>>
>> > In a nutshell, such as things currently are, under Slackware64 15.0 the
>> > latest release of netdata will not build if protobuf3 is
>> already installed.
>>
>> Is there no --disable-protobuf3 or
>> similar?_______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/461898ef/attachment.htm>

From pprkut at slackbuilds.org  Sun Apr 24 15:29:34 2022
From: pprkut at slackbuilds.org (Heinz Wiesinger)
Date: Sun, 24 Apr 2022 17:29:34 +0200
Subject: [Slackbuilds-users] netdata fails to build
In-Reply-To: <CAFy1yb1ucEhPQu1XJbrxk46UqLT7VMSLjH=r0YLZce5Oh9P=9w@mail.gmail.com>
References: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>
 <639ffde-5dec-2b7b-33c-13f61a2b845c@slackware.uk>
 <CAFy1yb1ucEhPQu1XJbrxk46UqLT7VMSLjH=r0YLZce5Oh9P=9w@mail.gmail.com>
Message-ID: <4528390.vXUDI8C0e8@amaterasu.liwjatan.org>

On Sunday, 24 April 2022 17:01:14 CEST Luveh Keraph wrote:
> On Sun, Apr 24, 2022 at 8:42 AM B. Watson <urchlay at slackware.uk> wrote:
> > On Sun, 24 Apr 2022, Luveh Keraph wrote:
> > > In a nutshell, such as things currently are, under Slackware64 15.0 the
> > > latest release of netdata will not build if protobuf3 is
> > 
> > already installed.
> > 
> > Is there no --disable-protobuf3 or
> > similar?_______________________________________________
>
> The configure invocation in netdata.Slackbuild could indeed be changed so
> that the --without-new-cloud-protocol option is used. In truth, however,
> the problem is in the way in which the netdata source code tarball is
> created by the netdata people.
> 

I think we're just using the wrong download. This one does include the 
mentioned file:

https://github.com/netdata/netdata/releases/download/v1.34.1/netdata-v1.34.1.tar.gz

Grs,
Heinz 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/b502faea/attachment.asc>

From willysr at slackbuilds.org  Sun Apr 24 17:26:42 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 25 Apr 2022 00:26:42 +0700
Subject: [Slackbuilds-users] netdata fails to build
In-Reply-To: <4528390.vXUDI8C0e8@amaterasu.liwjatan.org>
References: <CAFy1yb3fS-+DpBhqDR82e8cNbvy4BzUxGxpXO4NRFmhNsEs2pw@mail.gmail.com>
 <639ffde-5dec-2b7b-33c-13f61a2b845c@slackware.uk>
 <CAFy1yb1ucEhPQu1XJbrxk46UqLT7VMSLjH=r0YLZce5Oh9P=9w@mail.gmail.com>
 <4528390.vXUDI8C0e8@amaterasu.liwjatan.org>
Message-ID: <e3d28524-567e-afca-4a74-cbeb97c1912d@slackbuilds.org>

> I think we're just using the wrong download. This one does include the 
> mentioned file:
> 
> https://github.com/netdata/netdata/releases/download/v1.34.1/netdata-v1.34.1.tar.gz

Yeap, just build this with protobuf3 and it built just fine
i'm going to change this on my branch


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220425/e26c7332/attachment.asc>

From chytraeu at sdf.org  Sun Apr 24 17:34:41 2022
From: chytraeu at sdf.org (chytraeu at sdf.org)
Date: Sun, 24 Apr 2022 12:34:41 -0500
Subject: [Slackbuilds-users] abandoning all my slackbuilds
Message-ID: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>

I've abandoned all my slackbuilds.

anorack  [dependees]  Donald Cooley <chytraeu at sdf.org>
bamf  [dependees]  Donald Cooley <chytraeus at protonmail.com>
bitrot  [dependees]  Donald Cooley <chytraeu at sdf.org>
discount  [dependees]  Donald Cooley <chytraeu at sdf.org>
dos2unix  [dependees]  Donald Cooley <chytraeu at sdf.org>
dothost  [dependees]  Donald Cooley <chytraeu at sdf.org>
dump  [dependees]  Donald Cooley <chytraeu at sdf.org>
frostwire  [dependees]  Donald Cooley <chytraeu at sdf.org>
gedit  [dependees]  Donald Cooley <chytraeu at sdf.org>
gedit-plugins  [dependees]  Donald Cooley <chytraeu at sdf.org>
gnome-menus  [dependees]  Donald Cooley <chytraeus at protonmail.com>
gprename  [dependees]  Donald Cooley <chytraeu at sdf.org>
gtk-sharp  [dependees]  Donald Cooley <chytraeu at sdf.org>
gtorrentviewer  [dependees]  Donald Cooley <chytraeu at sdf.org>
hiawatha  [dependees]  Donald Cooley <chytraeu at sdf.org>
leafpad  [dependees]  Donald Cooley <chytraeu at sdf.org>
libtorrent-rasterbar  [dependees]  Donald Cooley <chytraeu at sdf.org>
mosh  [dependees]  Donald Cooley <chytraeu at sdf.org>
openoffice.org  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-Cpanel-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-Data-Random  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-Gtk2-Unique  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-IO-HTML  [dependees]  Donald Cooley <chytraeus at protonmail.com>
perl-IO-Tty  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-LWP-Protocol-socks  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-Path-Class  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-Proc-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-Test-MockTime  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-Types-Serialiser  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-URI-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-WebService-Gyazo-B  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-common-sense  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-gnome2  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-gnome2-canvas  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-gnome2-vfs  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-gnome2-wnck  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-goo-canvas  [dependees]  Donald Cooley <chytraeus at protonmail.com>
perl-gtk2-imageview  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-html-form  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-http-response-encoding  [dependees]  Donald Cooley 
<chytraeus at protonmail.com>
perl-http-server-simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
perl-x11-protocol  [dependees]  Donald Cooley <chytraeus at protonmail.com>
plank  [dependees]  Donald Cooley <chytraeus at protonmail.com>
qbittorrent  [dependees]  Donald Cooley <chytraeu at sdf.org>
qpdfview  [dependees]  Donald Cooley <chytraeu at sdf.org>
qpdfview-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
quassel  [dependees]  Donald Cooley <chytraeu at sdf.org>
quassel-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
sakura  [dependees]  Donald Cooley <chytraeu at sdf.org>
shutter  [dependees]  Donald Cooley <chytraeu at sdf.org>
smoffice2016  [dependees]  Donald Cooley <chytraeu at sdf.org>
smoffice2018  [dependees]  Donald Cooley <chytraeu at sdf.org>
smoffice2021  [dependees]  Donald Cooley <chytraeu at sdf.org>
soundkonverter  [dependees]  Donald Cooley <chytraeu at sdf.org>
tal  [dependees]  Donald Cooley <chytraeu at sdf.org>

From b.pribs11 at gmail.com  Sun Apr 24 18:16:32 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Sun, 24 Apr 2022 11:16:32 -0700
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
Message-ID: <CAC3J=ZarxcbNoJz-RspQYBZ_uWT0cZTX004DY5feKTkCShjLiQ@mail.gmail.com>

On Sun, Apr 24, 2022, 10:34 AM , <chytraeu at sdf.org> wrote:

> I've abandoned all my slackbuilds.
>
> anorack  [dependees]  Donald Cooley <chytraeu at sdf.org>
> bamf  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> bitrot  [dependees]  Donald Cooley <chytraeu at sdf.org>
> discount  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dos2unix  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dothost  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dump  [dependees]  Donald Cooley <chytraeu at sdf.org>
> frostwire  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gedit  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gedit-plugins  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gnome-menus  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> gprename  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gtk-sharp  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gtorrentviewer  [dependees]  Donald Cooley <chytraeu at sdf.org>
> hiawatha  [dependees]  Donald Cooley <chytraeu at sdf.org>
> leafpad  [dependees]  Donald Cooley <chytraeu at sdf.org>
> libtorrent-rasterbar  [dependees]  Donald Cooley <chytraeu at sdf.org>
> mosh  [dependees]  Donald Cooley <chytraeu at sdf.org>
> openoffice.org  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Cpanel-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Data-Random  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Gtk2-Unique  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-IO-HTML  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> perl-IO-Tty  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-LWP-Protocol-socks  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Path-Class  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Proc-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Test-MockTime  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Types-Serialiser  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-URI-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-WebService-Gyazo-B  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-common-sense  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-canvas  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-vfs  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-wnck  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-goo-canvas  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> perl-gtk2-imageview  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-html-form  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-http-response-encoding  [dependees]  Donald Cooley
> <chytraeus at protonmail.com>
> perl-http-server-simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-x11-protocol  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> plank  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> qbittorrent  [dependees]  Donald Cooley <chytraeu at sdf.org>
> qpdfview  [dependees]  Donald Cooley <chytraeu at sdf.org>
> qpdfview-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
> quassel  [dependees]  Donald Cooley <chytraeu at sdf.org>
> quassel-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
> sakura  [dependees]  Donald Cooley <chytraeu at sdf.org>
> shutter  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2016  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2018  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2021  [dependees]  Donald Cooley <chytraeu at sdf.org>
> soundkonverter  [dependees]  Donald Cooley <chytraeu at sdf.org>
> tal  [dependees]  Donald Cooley <chytraeu at sdf.org>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/


I'll take over dos2unix.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/2265a1d6/attachment.htm>

From b.pribs11 at gmail.com  Sun Apr 24 18:22:00 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Sun, 24 Apr 2022 11:22:00 -0700
Subject: [Slackbuilds-users] Modifying config.mk's CFLAGS variable
In-Reply-To: <ed4d1e17-1198-f3de-178d-4233823a46a9@slackware.uk>
References: <CAC3J=Zab0+3BqUDbAnuPEHjdSBJPJRN063rKvhnKw62dr7mvfg@mail.gmail.com>
 <ed4d1e17-1198-f3de-178d-4233823a46a9@slackware.uk>
Message-ID: <CAC3J=ZZ3UK51icT+FaCEiM5xZ3Yr=TOrp_xtW2MJ5R9JgnFU9w@mail.gmail.com>

On Sun, Apr 24, 2022, 7:40 AM B. Watson, <urchlay at slackware.uk> wrote:

>
>
> On Fri, 22 Apr 2022, Brandon Pribula wrote:
>
> > The solution I came up with is to change '=' to '+='
> >
> > sed -i '/CFLAGS/s/=/+=/' config.mk
> >
> > and remove the optimization flag -Os
> >
> > sed -i '/CFLAGS/s/-Os//' config.mk
> >
> > This works fine but I would like to know if there is a more preferable
> > solution with a slackbuild.
>
> That sounds like it should work fine. I might have sedded the
> flags directly in:
>
> sed -i "/CFLAGS/s,-Os,$SLKCFLAGS," config.mk
>
> ...but there's nothing wrong with the way you did it.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/


Thanks, B. Watson.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/a47aa288/attachment.htm>

From b.pribs11 at gmail.com  Sun Apr 24 18:27:26 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Sun, 24 Apr 2022 11:27:26 -0700
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <CAC3J=ZarxcbNoJz-RspQYBZ_uWT0cZTX004DY5feKTkCShjLiQ@mail.gmail.com>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <CAC3J=ZarxcbNoJz-RspQYBZ_uWT0cZTX004DY5feKTkCShjLiQ@mail.gmail.com>
Message-ID: <CAC3J=ZZeL-f6ZQ5UL1ZwmtdjPd7OdHSz57p1F+iXsCWkjY_fGQ@mail.gmail.com>

On Sun, Apr 24, 2022, 11:16 AM Brandon Pribula, <b.pribs11 at gmail.com> wrote:

>
>
> On Sun, Apr 24, 2022, 10:34 AM , <chytraeu at sdf.org> wrote:
>
>> I've abandoned all my slackbuilds.
>>
>> anorack  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> bamf  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>> bitrot  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> discount  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> dos2unix  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> dothost  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> dump  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> frostwire  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> gedit  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> gedit-plugins  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> gnome-menus  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>> gprename  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> gtk-sharp  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> gtorrentviewer  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> hiawatha  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> leafpad  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> libtorrent-rasterbar  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> mosh  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> openoffice.org  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-Cpanel-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-Data-Random  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-Gtk2-Unique  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-IO-HTML  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>> perl-IO-Tty  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-LWP-Protocol-socks  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-Path-Class  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-Proc-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-Test-MockTime  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-Types-Serialiser  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-URI-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-WebService-Gyazo-B  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-common-sense  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-gnome2  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-gnome2-canvas  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-gnome2-vfs  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-gnome2-wnck  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-goo-canvas  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>> perl-gtk2-imageview  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-html-form  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-http-response-encoding  [dependees]  Donald Cooley
>> <chytraeus at protonmail.com>
>> perl-http-server-simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> perl-x11-protocol  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>> plank  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>> qbittorrent  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> qpdfview  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> qpdfview-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> quassel  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> quassel-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> sakura  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> shutter  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> smoffice2016  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> smoffice2018  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> smoffice2021  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> soundkonverter  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> tal  [dependees]  Donald Cooley <chytraeu at sdf.org>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>
>
> I'll take over dos2unix.
>

I probably should've asked what the procedure is for taking over as
maintainer?

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/569e9acc/attachment-0001.htm>

From poprocks at gmail.com  Sun Apr 24 18:34:51 2022
From: poprocks at gmail.com (Logan Rathbone)
Date: Sun, 24 Apr 2022 14:34:51 -0400
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <CAC3J=ZZeL-f6ZQ5UL1ZwmtdjPd7OdHSz57p1F+iXsCWkjY_fGQ@mail.gmail.com>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <CAC3J=ZarxcbNoJz-RspQYBZ_uWT0cZTX004DY5feKTkCShjLiQ@mail.gmail.com>
 <CAC3J=ZZeL-f6ZQ5UL1ZwmtdjPd7OdHSz57p1F+iXsCWkjY_fGQ@mail.gmail.com>
Message-ID: <CAFOgM0qN47ygV4z1=toXrAWr+qAuFsWRssJTPJ6zaUMPiOoHcQ@mail.gmail.com>

I'll at least take libtorrrent-rasterbar since I have a project that
depends on it (deluge) and had been discussing it with Donald recently
anyway.

Regards
Logan

On Sun., Apr. 24, 2022, 2:27 p.m. Brandon Pribula, <b.pribs11 at gmail.com>
wrote:

>
>
> On Sun, Apr 24, 2022, 11:16 AM Brandon Pribula, <b.pribs11 at gmail.com>
> wrote:
>
>>
>>
>> On Sun, Apr 24, 2022, 10:34 AM , <chytraeu at sdf.org> wrote:
>>
>>> I've abandoned all my slackbuilds.
>>>
>>> anorack  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> bamf  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>>> bitrot  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> discount  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> dos2unix  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> dothost  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> dump  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> frostwire  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> gedit  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> gedit-plugins  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> gnome-menus  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>>> gprename  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> gtk-sharp  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> gtorrentviewer  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> hiawatha  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> leafpad  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> libtorrent-rasterbar  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> mosh  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> openoffice.org  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-Cpanel-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-Data-Random  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-Gtk2-Unique  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-IO-HTML  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>>> perl-IO-Tty  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-LWP-Protocol-socks  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-Path-Class  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-Proc-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-Test-MockTime  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-Types-Serialiser  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-URI-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-WebService-Gyazo-B  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-common-sense  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-gnome2  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-gnome2-canvas  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-gnome2-vfs  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-gnome2-wnck  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-goo-canvas  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>>> perl-gtk2-imageview  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-html-form  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-http-response-encoding  [dependees]  Donald Cooley
>>> <chytraeus at protonmail.com>
>>> perl-http-server-simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> perl-x11-protocol  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>>> plank  [dependees]  Donald Cooley <chytraeus at protonmail.com>
>>> qbittorrent  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> qpdfview  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> qpdfview-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> quassel  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> quassel-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> sakura  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> shutter  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> smoffice2016  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> smoffice2018  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> smoffice2021  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> soundkonverter  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> tal  [dependees]  Donald Cooley <chytraeu at sdf.org>
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>
>>
>> I'll take over dos2unix.
>>
>
> I probably should've asked what the procedure is for taking over as
> maintainer?
>
>> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220424/b9db57fb/attachment.htm>

From erich.public at protonmail.com  Sun Apr 24 20:55:49 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Sun, 24 Apr 2022 20:55:49 +0000
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <CAC3J=ZZeL-f6ZQ5UL1ZwmtdjPd7OdHSz57p1F+iXsCWkjY_fGQ@mail.gmail.com>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <CAC3J=ZarxcbNoJz-RspQYBZ_uWT0cZTX004DY5feKTkCShjLiQ@mail.gmail.com>
 <CAC3J=ZZeL-f6ZQ5UL1ZwmtdjPd7OdHSz57p1F+iXsCWkjY_fGQ@mail.gmail.com>
Message-ID: <24X2588_4rLitrSJi4HJPdiolRnNpgFpUh_s43fmJtEzo3Ve3aDlH9LIKG1CGBt9q7nETd-TKLCDJEXHOOELr7r01YBhtiflMEMIpoRtdBo=@protonmail.com>

------- Original Message -------
On Sunday, April 24th, 2022 at 1:27 PM, Brandon Pribula <b.pribs11 at gmail.com> wrote:
>
>
> I probably should've asked what the procedure is for taking over as maintainer?


Note this text on http://slackbuilds.org/submit/

> If you are not the current MAINTAINER you need permission from that person to take over.

I believe this email thread constitutes appropriate permission :)  I would just add a note about it in the "additional notes" text field provided on the submission page.

Alternatively, a git pull request / merge request is acceptable as well - just be sure to note that you are taking over maintainership and point to this email thread.

I say all this not as an admin, but as someone who has taken over maintainership before.

Erich

From phalange at komputermatrix.com  Sun Apr 24 20:59:01 2022
From: phalange at komputermatrix.com (Andrew Payne)
Date: Sun, 24 Apr 2022 16:59:01 -0400
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
Message-ID: <5f12b7b51d2f4df69e7fda27aaa3d9bf.squirrel@email.fatcow.com>

I?ll take sakura

> I've abandoned all my slackbuilds.
>
> anorack  [dependees]  Donald Cooley <chytraeu at sdf.org>
> bamf  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> bitrot  [dependees]  Donald Cooley <chytraeu at sdf.org>
> discount  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dos2unix  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dothost  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dump  [dependees]  Donald Cooley <chytraeu at sdf.org>
> frostwire  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gedit  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gedit-plugins  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gnome-menus  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> gprename  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gtk-sharp  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gtorrentviewer  [dependees]  Donald Cooley <chytraeu at sdf.org>
> hiawatha  [dependees]  Donald Cooley <chytraeu at sdf.org>
> leafpad  [dependees]  Donald Cooley <chytraeu at sdf.org>
> libtorrent-rasterbar  [dependees]  Donald Cooley <chytraeu at sdf.org>
> mosh  [dependees]  Donald Cooley <chytraeu at sdf.org>
> openoffice.org  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Cpanel-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Data-Random  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Gtk2-Unique  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-IO-HTML  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> perl-IO-Tty  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-LWP-Protocol-socks  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Path-Class  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Proc-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Test-MockTime  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Types-Serialiser  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-URI-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-WebService-Gyazo-B  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-common-sense  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-canvas  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-vfs  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-wnck  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-goo-canvas  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> perl-gtk2-imageview  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-html-form  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-http-response-encoding  [dependees]  Donald Cooley
> <chytraeus at protonmail.com>
> perl-http-server-simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-x11-protocol  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> plank  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> qbittorrent  [dependees]  Donald Cooley <chytraeu at sdf.org>
> qpdfview  [dependees]  Donald Cooley <chytraeu at sdf.org>
> qpdfview-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
> quassel  [dependees]  Donald Cooley <chytraeu at sdf.org>
> quassel-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
> sakura  [dependees]  Donald Cooley <chytraeu at sdf.org>
> shutter  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2016  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2018  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2021  [dependees]  Donald Cooley <chytraeu at sdf.org>
> soundkonverter  [dependees]  Donald Cooley <chytraeu at sdf.org>
> tal  [dependees]  Donald Cooley <chytraeu at sdf.org>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>



From sb at rbn.im  Sun Apr 24 21:23:15 2022
From: sb at rbn.im (Ruben Schuller)
Date: Sun, 24 Apr 2022 23:23:15 +0200
Subject: [Slackbuilds-users] hyperscan fails to build
Message-ID: <20220424232315.7d3e0f93@kiwi.kuchen>

Hi,

hyperscan 5.4.0 fails to build with

In file included from /usr/include/signal.h:328,
                 from
/tmp/SBo/hyperscan-5.4.0/tools/hscollider/sig.cpp:40:
/tmp/SBo/hyperscan-5.4.0/tools/hscollider/sig.cpp:178:40: error: size
of array ?alt_stack_loc? is not an integral constant-expression 178 |
static TLS_VARIABLE char alt_stack_loc[SIGSTKSZ]; |
                   ^~~~~~~~ make[2]: ***
[tools/hscollider/CMakeFiles/hscollider.dir/build.make:221:
tools/hscollider/CMakeFiles/hscollider.dir/sig.cpp.o] Error 1

There is an issue [1] about this on GitHub suggesting -DFAT_RUNTIME=off,
but this didn't help here. Any suggestions?

So long
Ruben

[1] https://github.com/intel/hyperscan/issues/344

From b.pribs11 at gmail.com  Sun Apr 24 21:47:19 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Sun, 24 Apr 2022 14:47:19 -0700
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <24X2588_4rLitrSJi4HJPdiolRnNpgFpUh_s43fmJtEzo3Ve3aDlH9LIKG1CGBt9q7nETd-TKLCDJEXHOOELr7r01YBhtiflMEMIpoRtdBo=@protonmail.com>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <CAC3J=ZarxcbNoJz-RspQYBZ_uWT0cZTX004DY5feKTkCShjLiQ@mail.gmail.com>
 <CAC3J=ZZeL-f6ZQ5UL1ZwmtdjPd7OdHSz57p1F+iXsCWkjY_fGQ@mail.gmail.com>
 <24X2588_4rLitrSJi4HJPdiolRnNpgFpUh_s43fmJtEzo3Ve3aDlH9LIKG1CGBt9q7nETd-TKLCDJEXHOOELr7r01YBhtiflMEMIpoRtdBo=@protonmail.com>
Message-ID: <87y1zui088.fsf@bit-whore.slacker.org>


Erich Ritz via SlackBuilds-users <slackbuilds-users at slackbuilds.org> writes:

> ------- Original Message -------
> On Sunday, April 24th, 2022 at 1:27 PM, Brandon Pribula <b.pribs11 at gmail.com> wrote:
>>
>>
>> I probably should've asked what the procedure is for taking over as maintainer?
>
>
> Note this text on http://slackbuilds.org/submit/
>
>> If you are not the current MAINTAINER you need permission from that person to take over.
>
> I believe this email thread constitutes appropriate permission :)  I would just add a note about it in the "additional notes" text field provided on the submission page.
>
> Alternatively, a git pull request / merge request is acceptable as well - just be sure to note that you are taking over maintainership and point to this email thread.
>
> I say all this not as an admin, but as someone who has taken over maintainership before.
>
> Erich
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/

Thanks for the help, Erich. I wasn't sure if I should use the submission
page or a pull request :) I'm going to go with a pull request.

From dchmelik at gmail.com  Mon Apr 25 00:15:54 2022
From: dchmelik at gmail.com (David Chmelik)
Date: Sun, 24 Apr 2022 17:15:54 -0700
Subject: [Slackbuilds-users] SoulSeek?
In-Reply-To: <9a835028-58ef-43ed-31a7-6a1baba3f510@o2.pl>
References: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com>
 <9a835028-58ef-43ed-31a7-6a1baba3f510@o2.pl>
Message-ID: <3bfcc910-99ab-c910-d3ca-9ed9209ac790@gmail.com>

On 3/18/22 10:45 AM, Dominik Drobek wrote:
> W dniu 18.03.2022 o?04:37, David Chmelik pisze:
>> It's good EiskaltDC++ and SoulSeek are still on but latter's six 
>> years old but for some idiotic reason they made newer version require 
>> SELinux.
>
> Hi David,
>
> I'm the maintainer of SoulseekQt. There is a workaround for this 
> SELinux dependency, I just didn't have the motivation to implement it 
> and post an update to SBo. But I can look into this if there's demand 
> for it.
>
> I recommend Nicotine+ over the official client anyway. :) [...] 

Nicotine+ never seemed to work--I guess I managed to add account but 
wasn't able to search and/or join rooms, etc... seems far fewer features 
than the official client.? I'd still like to see the official client 
updated soon as I use it almost all the time.


From lists at osh.id.au  Mon Apr 25 01:57:04 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Mon, 25 Apr 2022 09:57:04 +0800
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
Message-ID: <7f6ea64e-a3fc-4eb2-bbea-b353271e4cce@www.fastmail.com>

I'll grab qbittorrent.

On Mon, 25 Apr 2022, at 1:34 AM, chytraeu at sdf.org wrote:
> I've abandoned all my slackbuilds.
>
> anorack  [dependees]  Donald Cooley <chytraeu at sdf.org>
> bamf  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> bitrot  [dependees]  Donald Cooley <chytraeu at sdf.org>
> discount  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dos2unix  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dothost  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dump  [dependees]  Donald Cooley <chytraeu at sdf.org>
> frostwire  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gedit  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gedit-plugins  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gnome-menus  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> gprename  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gtk-sharp  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gtorrentviewer  [dependees]  Donald Cooley <chytraeu at sdf.org>
> hiawatha  [dependees]  Donald Cooley <chytraeu at sdf.org>
> leafpad  [dependees]  Donald Cooley <chytraeu at sdf.org>
> libtorrent-rasterbar  [dependees]  Donald Cooley <chytraeu at sdf.org>
> mosh  [dependees]  Donald Cooley <chytraeu at sdf.org>
> openoffice.org  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Cpanel-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Data-Random  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Gtk2-Unique  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-IO-HTML  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> perl-IO-Tty  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-LWP-Protocol-socks  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Path-Class  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Proc-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Test-MockTime  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Types-Serialiser  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-URI-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-WebService-Gyazo-B  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-common-sense  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-canvas  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-vfs  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-wnck  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-goo-canvas  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> perl-gtk2-imageview  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-html-form  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-http-response-encoding  [dependees]  Donald Cooley 
> <chytraeus at protonmail.com>
> perl-http-server-simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-x11-protocol  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> plank  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> qbittorrent  [dependees]  Donald Cooley <chytraeu at sdf.org>
> qpdfview  [dependees]  Donald Cooley <chytraeu at sdf.org>
> qpdfview-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
> quassel  [dependees]  Donald Cooley <chytraeu at sdf.org>
> quassel-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
> sakura  [dependees]  Donald Cooley <chytraeu at sdf.org>
> shutter  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2016  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2018  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2021  [dependees]  Donald Cooley <chytraeu at sdf.org>
> soundkonverter  [dependees]  Donald Cooley <chytraeu at sdf.org>
> tal  [dependees]  Donald Cooley <chytraeu at sdf.org>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/

From poprocks at gmail.com  Mon Apr 25 04:01:03 2022
From: poprocks at gmail.com (Logan Rathbone)
Date: Mon, 25 Apr 2022 00:01:03 -0400
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <7f6ea64e-a3fc-4eb2-bbea-b353271e4cce@www.fastmail.com>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <7f6ea64e-a3fc-4eb2-bbea-b353271e4cce@www.fastmail.com>
Message-ID: <CAFOgM0qCegpLFnhXSBfbx5XxYzMmvQ7xMA7QpBMMUAk8rTh_nA@mail.gmail.com>

On Sun., Apr. 24, 2022, 9:57 p.m. David O'Shaughnessy, <lists at osh.id.au> 
wrote:

> I'll grab qbittorrent.

We should chat to coordinate, since libtorrrent-rasterbar is also a 
dependency of qbittorrent, so I want to make sure that it updating it for 
deluge doesn't break qbittorrent.

I'll email you separately about this.

From poprocks at gmail.com  Mon Apr 25 05:26:35 2022
From: poprocks at gmail.com (Logan Rathbone)
Date: Mon, 25 Apr 2022 01:26:35 -0400
Subject: [Slackbuilds-users] hyperscan fails to build
In-Reply-To: <20220424232315.7d3e0f93@kiwi.kuchen>
References: <20220424232315.7d3e0f93@kiwi.kuchen>
Message-ID: <YmYxCztJkFyzmHSO@thinkpad.local.domain>

On Sun, Apr 24, 2022 at 05:23:15PM EDT, Ruben Schuller wrote:
> Hi,
> 
> hyperscan 5.4.0 fails to build with
> 
> In file included from /usr/include/signal.h:328,
>                  from
> /tmp/SBo/hyperscan-5.4.0/tools/hscollider/sig.cpp:40:
> /tmp/SBo/hyperscan-5.4.0/tools/hscollider/sig.cpp:178:40: error: size
> of array ?alt_stack_loc? is not an integral constant-expression 178 |
> static TLS_VARIABLE char alt_stack_loc[SIGSTKSZ]; |
>                    ^~~~~~~~ make[2]: ***
> [tools/hscollider/CMakeFiles/hscollider.dir/build.make:221:
> tools/hscollider/CMakeFiles/hscollider.dir/sig.cpp.o] Error 1
> 
> There is an issue [1] about this on GitHub suggesting -DFAT_RUNTIME=off,
> but this didn't help here. Any suggestions?

It built fine for me.

Are you on 15.0 or current?  Perusing through the system headers I saw
some comment that SIGSTKSZ was being redefined from a constant to
something potentially variable in glibc >= 2.34.  So if you're on
current with glibc 2.35, you may be getting a build failure that is not
reproducible on 15.0.

From sb at rbn.im  Mon Apr 25 09:39:24 2022
From: sb at rbn.im (Ruben Schuller)
Date: Mon, 25 Apr 2022 11:39:24 +0200
Subject: [Slackbuilds-users] hyperscan fails to build
In-Reply-To: <YmYxCztJkFyzmHSO@thinkpad.local.domain>
References: <20220424232315.7d3e0f93@kiwi.kuchen>
 <YmYxCztJkFyzmHSO@thinkpad.local.domain>
Message-ID: <20220425113924.604c980e@kiwi.kuchen>

Hi Logan, hi list,

2022-04-25 Logan Rathbone <poprocks at gmail.com>:

> On Sun, Apr 24, 2022 at 05:23:15PM EDT, Ruben Schuller wrote:
> > [...]
> 
> It built fine for me.
> 
> Are you on 15.0 or current?  Perusing through the system headers I saw
> some comment that SIGSTKSZ was being redefined from a constant to
> something potentially variable in glibc >= 2.34.  So if you're on
> current with glibc 2.35, you may be getting a build failure that is
> not reproducible on 15.0.

Thanks! That was the issue, it builds fine on 15.0. Could have thought
about that, sorry for the noise!

Cheers
Ruben

From tonus1 at gmail.com  Mon Apr 25 10:54:59 2022
From: tonus1 at gmail.com (Tonus)
Date: Mon, 25 Apr 2022 12:54:59 +0200
Subject: [Slackbuilds-users] Donald Cooley abandoned SlackBuilds
In-Reply-To: <mailman.693.1650833953.31924.slackbuilds-users@slackbuilds.org>
References: <mailman.693.1650833953.31924.slackbuilds-users@slackbuilds.org>
Message-ID: <20220425105459.divrqqkn6bg2425m@Baldr.vingolf.info>

Hi list,

I already have a few perl modules and these are on my build queue as 
well, I can take them unless someone wants to step in.

> > perl-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>

> > perl-Types-Serialiser  [dependees]  Donald Cooley <chytraeu at sdf.org>

> > perl-common-sense  [dependees]  Donald Cooley <chytraeu at sdf.org>


-- 
Regards,

Tonus

From urchlay at slackware.uk  Mon Apr 25 14:01:16 2022
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 25 Apr 2022 10:01:16 -0400 (EDT)
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
Message-ID: <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>



On Sun, 24 Apr 2022, chytraeu at sdf.org wrote:

> I've abandoned all my slackbuilds.

Will it bother you if the people who take over maintenance of your
builds decide to change the license?

From b.pribs11 at gmail.com  Mon Apr 25 16:00:39 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Mon, 25 Apr 2022 09:00:39 -0700
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
Message-ID: <CAC3J=ZYPneGZq0Gc+Ga1B7QpyVpV6BzeGZtSJAL_bPCg5BayVw@mail.gmail.com>

I grabbed the following:

anorack
bitrot
discount
dos2unix
gedit
gedit-plugins
leafpad
sakura
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220425/b87b7547/attachment.htm>

From dominik.drobek at o2.pl  Mon Apr 25 16:02:48 2022
From: dominik.drobek at o2.pl (Dominik Drobek)
Date: Mon, 25 Apr 2022 18:02:48 +0200
Subject: [Slackbuilds-users] SoulSeek?
In-Reply-To: <3bfcc910-99ab-c910-d3ca-9ed9209ac790@gmail.com>
References: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com>
 <9a835028-58ef-43ed-31a7-6a1baba3f510@o2.pl>
 <3bfcc910-99ab-c910-d3ca-9ed9209ac790@gmail.com>
Message-ID: <e19adfa2-5b3c-d88f-3117-1a7481a06869@o2.pl>

W dniu 25.04.2022 o?02:15, David Chmelik pisze:
> I'd still like to see the official client 
> updated soon as I use it almost all the time.

All right, I'll look into it.

Regards,
Dominik

From lists at osh.id.au  Mon Apr 25 16:16:25 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Tue, 26 Apr 2022 00:16:25 +0800
Subject: [Slackbuilds-users] SoulSeek?
In-Reply-To: <e19adfa2-5b3c-d88f-3117-1a7481a06869@o2.pl>
References: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com>
 <9a835028-58ef-43ed-31a7-6a1baba3f510@o2.pl>
 <3bfcc910-99ab-c910-d3ca-9ed9209ac790@gmail.com>
 <e19adfa2-5b3c-d88f-3117-1a7481a06869@o2.pl>
Message-ID: <400dcb04-777d-4731-b72b-d0b2703f58cc@www.fastmail.com>

I think Linux development on the official client is dead, 2018 is the last Linux release:

https://www.slsknet.org/news/node/1

Nicotine+ is where it's at :)

On Tue, 26 Apr 2022, at 12:02 AM, Dominik Drobek wrote:
> W dniu 25.04.2022 o?02:15, David Chmelik pisze:
>> I'd still like to see the official client 
>> updated soon as I use it almost all the time.
>
> All right, I'll look into it.
>
> Regards,
> Dominik

From phalange at komputermatrix.com  Mon Apr 25 16:34:27 2022
From: phalange at komputermatrix.com (Andrew Payne)
Date: Mon, 25 Apr 2022 12:34:27 -0400
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <CAC3J=ZYPneGZq0Gc+Ga1B7QpyVpV6BzeGZtSJAL_bPCg5BayVw@mail.gmail.com>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
 <CAC3J=ZYPneGZq0Gc+Ga1B7QpyVpV6BzeGZtSJAL_bPCg5BayVw@mail.gmail.com>
Message-ID: <8468e982e7e1e251af77d490f63f91c7.squirrel@email.fatcow.com>

Hi Brandon, to clarify I offered to take over Sakura on Sunday. Did you
post you post your intentions to the group? I only saw dos2unix in your
initial request.

> I grabbed the following:
>
> anorack
> bitrot
> discount
> dos2unix
> gedit
> gedit-plugins
> leafpad
> sakura
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>



From poprocks at gmail.com  Mon Apr 25 16:41:04 2022
From: poprocks at gmail.com (Logan Rathbone)
Date: Mon, 25 Apr 2022 12:41:04 -0400
Subject: [Slackbuilds-users] hyperscan fails to build
In-Reply-To: <20220425113924.604c980e@kiwi.kuchen>
References: <20220424232315.7d3e0f93@kiwi.kuchen>
 <YmYxCztJkFyzmHSO@thinkpad.local.domain>
 <20220425113924.604c980e@kiwi.kuchen>
Message-ID: <YmbPIO4dOUV4tgz9@thinkpad.local.domain>

On Mon, Apr 25, 2022 at 05:39:24AM EDT, Ruben Schuller wrote:
> 2022-04-25 Logan Rathbone <poprocks at gmail.com>:
> > On Sun, Apr 24, 2022 at 05:23:15PM EDT, Ruben Schuller wrote:
> > > [...]
> > 
> > It built fine for me.
> > 
> > Are you on 15.0 or current?  Perusing through the system headers I saw
> > some comment that SIGSTKSZ was being redefined from a constant to
> > something potentially variable in glibc >= 2.34.  So if you're on
> > current with glibc 2.35, you may be getting a build failure that is
> > not reproducible on 15.0.
> 
> Thanks! That was the issue, it builds fine on 15.0. Could have thought
> about that, sorry for the noise!

No worries! You can always report issues of SlackBuilds not building on
current on this LQ thread:

https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/

Looks like someone has already noticed this thread on the ML and
cross-posted to that thread, but in future it may be a useful resource.

Regards,
Logan (poprocks)

From b.pribs11 at gmail.com  Mon Apr 25 16:49:29 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Mon, 25 Apr 2022 09:49:29 -0700
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <8468e982e7e1e251af77d490f63f91c7.squirrel@email.fatcow.com>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
 <CAC3J=ZYPneGZq0Gc+Ga1B7QpyVpV6BzeGZtSJAL_bPCg5BayVw@mail.gmail.com>
 <8468e982e7e1e251af77d490f63f91c7.squirrel@email.fatcow.com>
Message-ID: <CAC3J=ZahUBnPOOutkfxB9E7CNWpL0nZtae3UEb9GQxZN_t7stA@mail.gmail.com>

On Mon, Apr 25, 2022, 9:35 AM Andrew Payne, <phalange at komputermatrix.com>
wrote:

> Hi Brandon, to clarify I offered to take over Sakura on Sunday. Did you
> post you post your intentions to the group? I only saw dos2unix in your
> initial request.
>
> > I grabbed the following:
> >
> > anorack
> > bitrot
> > discount
> > dos2unix
> > gedit
> > gedit-plugins
> > leafpad
> > sakura
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/


That's my fault. I decided to go through them yesterday evening and I
forgot to post the ones I grabbed to the mailing list until Dave Woodfall
reminded me this morning and I must've missed your post. Hectic weekend.

Sakura's all yours :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220425/6a95d2ad/attachment-0001.htm>

From chytraeu at sdf.org  Mon Apr 25 18:33:53 2022
From: chytraeu at sdf.org (Donald Cooley)
Date: Mon, 25 Apr 2022 13:33:53 -0500
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
Message-ID: <2FA5EB98-7C6F-4152-9754-625E9DCF9DF6@sdf.org>

On April 25, 2022 9:01:16 AM CDT, "B. Watson" <urchlay at slackware.uk> wrote:
>
>
>On Sun, 24 Apr 2022, chytraeu at sdf.org wrote:
>
>> I've abandoned all my slackbuilds.
>
>Will it bother you if the people who take over maintenance of your
>builds decide to change the license?

Seems unnecessary to change the liberal license. If you want to change the license retain my name as the author.

From poprocks at gmail.com  Mon Apr 25 18:59:38 2022
From: poprocks at gmail.com (Logan Rathbone)
Date: Mon, 25 Apr 2022 14:59:38 -0400
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <2FA5EB98-7C6F-4152-9754-625E9DCF9DF6@sdf.org>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
 <2FA5EB98-7C6F-4152-9754-625E9DCF9DF6@sdf.org>
Message-ID: <YmbvmhQ8B6q909hO@thinkpad.local.domain>

On Mon, Apr 25, 2022 at 02:33:53PM EDT, Donald Cooley wrote:
> On April 25, 2022 9:01:16 AM CDT, "B. Watson" <urchlay at slackware.uk> wrote:
> >
> >
> >On Sun, 24 Apr 2022, chytraeu at sdf.org wrote:
> >
> >> I've abandoned all my slackbuilds.
> >
> >Will it bother you if the people who take over maintenance of your
> >builds decide to change the license?
> 
> Seems unnecessary to change the liberal license. If you want to change the license retain my name as the author.

That doesn't necessarily answer the question, because some licences
don't require proof of original authorship to be retained.  As well, if
re-licensing is to occur, someone needs to hold the copyright going
forward from as at the point of changing of the licence.

Would it be agreeable to you for new maintainers to put a blurb saying
"Original Author: Donald Cooley" or equivalent as a courtesy, and to
retain your name as copyright holder from [whatever year] to 2022?

From urchlay at slackware.uk  Mon Apr 25 19:46:42 2022
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 25 Apr 2022 15:46:42 -0400 (EDT)
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <2FA5EB98-7C6F-4152-9754-625E9DCF9DF6@sdf.org>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
 <2FA5EB98-7C6F-4152-9754-625E9DCF9DF6@sdf.org>
Message-ID: <138abd46-14f6-e6e5-e1aa-3ffc91fa99bc@slackware.uk>



On Mon, 25 Apr 2022, Donald Cooley wrote:

> Seems unnecessary to change the liberal license. If you want to change the license retain my name as the author.

Keeping the original author's name and credit is SBo policy, I
wouldn't remove it.

I plan to change the license to the WTFPL for a few that I'm taking
over. It's even more liberal than the existing license, and it doesn't
require me to look at a bunch of ALL CAPS LEGALESE when editing the
script.

From didier at slint.fr  Mon Apr 25 19:53:02 2022
From: didier at slint.fr (Didier Spaier)
Date: Mon, 25 Apr 2022 21:53:02 +0200
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <YmbvmhQ8B6q909hO@thinkpad.local.domain>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
 <2FA5EB98-7C6F-4152-9754-625E9DCF9DF6@sdf.org>
 <YmbvmhQ8B6q909hO@thinkpad.local.domain>
Message-ID: <150e01f3-91cd-0b05-8580-e305f760d764@slint.fr>

Le 25/04/2022 ? 20:59, Logan Rathbone a ?crit?:
> On Mon, Apr 25, 2022 at 02:33:53PM EDT, Donald Cooley wrote:
>> On April 25, 2022 9:01:16 AM CDT, "B. Watson" <urchlay at slackware.uk> wrote:
>>>
>>>
>>> On Sun, 24 Apr 2022, chytraeu at sdf.org wrote:
>>>
>>>> I've abandoned all my slackbuilds.
>>>
>>> Will it bother you if the people who take over maintenance of your
>>> builds decide to change the license?
>>
>> Seems unnecessary to change the liberal license. If you want to change the license retain my name as the author.
> 
> That doesn't necessarily answer the question, because some licences
> don't require proof of original authorship to be retained.  As well, if
> re-licensing is to occur, someone needs to hold the copyright going
> forward from as at the point of changing of the licence.
> 
> Would it be agreeable to you for new maintainers to put a blurb saying
> "Original Author: Donald Cooley" or equivalent as a courtesy, and to
> retain your name as copyright holder from [whatever year] to 2022?

[OT]Tempest in a tea pot in my NRO (Not Requested Opinion):
1. B. Watson often uses the WTFL (rather a copy left than a copyright), which at
least has the advantage to be less verbose that the text in the templates.
2. I wonder why the SlackBuilds on SBo need to mention a license, while the
PKBUILDs on Arch do not (but package, maintainer and contributors are named),
with no issue that I am aware of (this is just an example). Does anyone
seriously think that there is a legal risk for a (generally small) file which is
of no use out of context? Time and space wasted.
I am no more in concern, but still...[/OT]

From chytraeu at sdf.org  Mon Apr 25 19:56:54 2022
From: chytraeu at sdf.org (Donald Cooley)
Date: Mon, 25 Apr 2022 14:56:54 -0500
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <138abd46-14f6-e6e5-e1aa-3ffc91fa99bc@slackware.uk>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
 <2FA5EB98-7C6F-4152-9754-625E9DCF9DF6@sdf.org>
 <138abd46-14f6-e6e5-e1aa-3ffc91fa99bc@slackware.uk>
Message-ID: <35DDFE56-E8CC-4DA3-AD26-2AC1E70DC401@sdf.org>

On April 25, 2022 2:46:42 PM CDT, "B. Watson" <urchlay at slackware.uk> wrote:
>
>
>On Mon, 25 Apr 2022, Donald Cooley wrote:
>
>> Seems unnecessary to change the liberal license. If you want to change the license retain my name as the author.
>
>Keeping the original author's name and credit is SBo policy, I
>wouldn't remove it.
>
>I plan to change the license to the WTFPL for a few that I'm taking
>over. It's even more liberal than the existing license, and it doesn't
>require me to look at a bunch of ALL CAPS LEGALESE when editing the
>script.

Sounds fine to me.

From urchlay at slackware.uk  Mon Apr 25 20:31:08 2022
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 25 Apr 2022 16:31:08 -0400 (EDT)
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <35DDFE56-E8CC-4DA3-AD26-2AC1E70DC401@sdf.org>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
 <2FA5EB98-7C6F-4152-9754-625E9DCF9DF6@sdf.org>
 <138abd46-14f6-e6e5-e1aa-3ffc91fa99bc@slackware.uk>
 <35DDFE56-E8CC-4DA3-AD26-2AC1E70DC401@sdf.org>
Message-ID: <38ee0ba-bc9d-d242-db66-854991f392ad@slackware.uk>



On Mon, 25 Apr 2022, Donald Cooley wrote:

> Sounds fine to me.

Thanks!

From sultmhoor at gmail.com  Mon Apr 25 21:21:22 2022
From: sultmhoor at gmail.com (Kevin Bryant)
Date: Mon, 25 Apr 2022 17:21:22 -0400
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
Message-ID: <CAK2P7buzuJdSmj4L99=2aJjm3SUh+eiBiJakDjS7uJAcwb_VNA@mail.gmail.com>

Being both a long term perl, slackware, and slackbuilds user, I'd be happy
to take over the perl-* mods. It's about time I contributed :)

Kevin Bryant

On Sun, Apr 24, 2022 at 1:34 PM <chytraeu at sdf.org> wrote:

> I've abandoned all my slackbuilds.
>
> anorack  [dependees]  Donald Cooley <chytraeu at sdf.org>
> bamf  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> bitrot  [dependees]  Donald Cooley <chytraeu at sdf.org>
> discount  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dos2unix  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dothost  [dependees]  Donald Cooley <chytraeu at sdf.org>
> dump  [dependees]  Donald Cooley <chytraeu at sdf.org>
> frostwire  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gedit  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gedit-plugins  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gnome-menus  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> gprename  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gtk-sharp  [dependees]  Donald Cooley <chytraeu at sdf.org>
> gtorrentviewer  [dependees]  Donald Cooley <chytraeu at sdf.org>
> hiawatha  [dependees]  Donald Cooley <chytraeu at sdf.org>
> leafpad  [dependees]  Donald Cooley <chytraeu at sdf.org>
> libtorrent-rasterbar  [dependees]  Donald Cooley <chytraeu at sdf.org>
> mosh  [dependees]  Donald Cooley <chytraeu at sdf.org>
> openoffice.org  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Cpanel-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Data-Random  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Gtk2-Unique  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-IO-HTML  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> perl-IO-Tty  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-JSON-XS  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-LWP-Protocol-socks  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Path-Class  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Proc-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Test-MockTime  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-Types-Serialiser  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-URI-Simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-WebService-Gyazo-B  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-common-sense  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-canvas  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-vfs  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-gnome2-wnck  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-goo-canvas  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> perl-gtk2-imageview  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-html-form  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-http-response-encoding  [dependees]  Donald Cooley
> <chytraeus at protonmail.com>
> perl-http-server-simple  [dependees]  Donald Cooley <chytraeu at sdf.org>
> perl-x11-protocol  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> plank  [dependees]  Donald Cooley <chytraeus at protonmail.com>
> qbittorrent  [dependees]  Donald Cooley <chytraeu at sdf.org>
> qpdfview  [dependees]  Donald Cooley <chytraeu at sdf.org>
> qpdfview-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
> quassel  [dependees]  Donald Cooley <chytraeu at sdf.org>
> quassel-qt5  [dependees]  Donald Cooley <chytraeu at sdf.org>
> sakura  [dependees]  Donald Cooley <chytraeu at sdf.org>
> shutter  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2016  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2018  [dependees]  Donald Cooley <chytraeu at sdf.org>
> smoffice2021  [dependees]  Donald Cooley <chytraeu at sdf.org>
> soundkonverter  [dependees]  Donald Cooley <chytraeu at sdf.org>
> tal  [dependees]  Donald Cooley <chytraeu at sdf.org>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220425/564805e3/attachment-0001.htm>

From richard at aaazen.com  Tue Apr 26 21:09:29 2022
From: richard at aaazen.com (Richard Narron)
Date: Tue, 26 Apr 2022 14:09:29 -0700 (PDT)
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <138abd46-14f6-e6e5-e1aa-3ffc91fa99bc@slackware.uk>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
 <2FA5EB98-7C6F-4152-9754-625E9DCF9DF6@sdf.org>
 <138abd46-14f6-e6e5-e1aa-3ffc91fa99bc@slackware.uk>
Message-ID: <16bbcb59-1c47-80fd-9aeb-2eec0f81fae@aaazen.com>

On Mon, 25 Apr 2022, B. Watson wrote:

> On Mon, 25 Apr 2022, Donald Cooley wrote:
>
> > Seems unnecessary to change the liberal license. If you want to change the
> > license retain my name as the author.
>
> Keeping the original author's name and credit is SBo policy, I
> wouldn't remove it.
>
> I plan to change the license to the WTFPL for a few that I'm taking
> over. It's even more liberal than the existing license, and it doesn't
> require me to look at a bunch of ALL CAPS LEGALESE when editing the
> script.

The existing 1 clause BSD style license is there because it seems to be
what Patrick Volkerding uses for Slackware.

This makes it easier to promote a SlackBuild if Patrick accepts it into
the main distribution.

When Patrick switches to WTFPL then I would say go for it, otherwise I
would just leave it alone.

Richard Narron


From b.pribs11 at gmail.com  Wed Apr 27 02:51:37 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Tue, 26 Apr 2022 19:51:37 -0700
Subject: [Slackbuilds-users] network/snownews
Message-ID: <CAC3J=ZbKHtoqedNi8N1dqx00qQV761_sY4DUqqL_gfxy5Hepzw@mail.gmail.com>

Hi,

Could you please remove snownews from SBo. I just noticed when I went to
update that it's included in Slackware already. I'm sorry for the
inconvenience.

Thanks,

Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220426/0c47f1bc/attachment.htm>

From urchlay at slackware.uk  Wed Apr 27 03:39:19 2022
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 26 Apr 2022 23:39:19 -0400 (EDT)
Subject: [Slackbuilds-users] abandoning all my slackbuilds
In-Reply-To: <16bbcb59-1c47-80fd-9aeb-2eec0f81fae@aaazen.com>
References: <2f9a3642fdf31ef2474f0e95c710d6c4@sdf.org>
 <209e4d6d-37d8-c130-80c7-62c266170d2@slackware.uk>
 <2FA5EB98-7C6F-4152-9754-625E9DCF9DF6@sdf.org>
 <138abd46-14f6-e6e5-e1aa-3ffc91fa99bc@slackware.uk>
 <16bbcb59-1c47-80fd-9aeb-2eec0f81fae@aaazen.com>
Message-ID: <ab881719-e7ec-e18f-fd4c-d1f7fc30d9e6@slackware.uk>



On Tue, 26 Apr 2022, Richard Narron wrote:

> The existing 1 clause BSD style license is there because it seems to be
> what Patrick Volkerding uses for Slackware.
>
> This makes it easier to promote a SlackBuild if Patrick accepts it into
> the main distribution.
>
> When Patrick switches to WTFPL then I would say go for it, otherwise I
> would just leave it alone.

WTFPL says "Do WTF you want with this". Including relicensing it as
BSD. If PV wants to adopt one of my builds, he can do that.

Actually, see:

https://slackware.uk/slackware/slackware64-15.0/source/ap/man-db/man-db.SlackBuild

...in which PV *did* adopt one of my builds, and left it as WTFPL.

On the other hand:

https://slackware.uk/slackware/slackware64-15.0/source/xap/xaos/xaos.SlackBuild

...he adopted that one, which didn't originally have a license at all,
and he put the BSD-ish 1-clause license on it. No problems there,
either.

I guess what I'm trying to say is, I (and other SBo maintainers)
shouldn't be forced to use the same license PV uses, just because PV
uses it.

There are other things Pat does differently in his SlackBuilds, such
as using NUMJOBS, or calculating VERSION by extracting it from the
tarball filename, that we don't do with SBo builds.

From dave at slackbuilds.org  Wed Apr 27 03:45:38 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Wed, 27 Apr 2022 04:45:38 +0100
Subject: [Slackbuilds-users] network/snownews
In-Reply-To: <CAC3J=ZbKHtoqedNi8N1dqx00qQV761_sY4DUqqL_gfxy5Hepzw@mail.gmail.com>
References: <CAC3J=ZbKHtoqedNi8N1dqx00qQV761_sY4DUqqL_gfxy5Hepzw@mail.gmail.com>
Message-ID: <Ymi8Yhjj0K4OhZVx@localhost>

On 26/04/22 19:51,
Brandon Pribula <b.pribs11 at gmail.com> put forth the proposition:
> Hi,
> Could you please remove snownews from SBo. I just noticed when I went to
> update that it's included in Slackware already. I'm sorry for the
> inconvenience.
> Thanks,
> Brandon

Done

--
Dave

From b.pribs11 at gmail.com  Wed Apr 27 04:48:51 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Tue, 26 Apr 2022 21:48:51 -0700
Subject: [Slackbuilds-users] network/snownews
In-Reply-To: <Ymi8Yhjj0K4OhZVx@localhost>
References: <CAC3J=ZbKHtoqedNi8N1dqx00qQV761_sY4DUqqL_gfxy5Hepzw@mail.gmail.com>
 <Ymi8Yhjj0K4OhZVx@localhost>
Message-ID: <CAC3J=ZY1FttBxAtdQJZ4iRNW-A7NngZtUGuFid=P13RK8sKjJw@mail.gmail.com>

On Tue, Apr 26, 2022, 8:45 PM Dave Woodfall, <dave at slackbuilds.org> wrote:

> On 26/04/22 19:51,
> Brandon Pribula <b.pribs11 at gmail.com> put forth the proposition:
> > Hi,
> > Could you please remove snownews from SBo. I just noticed when I went to
> > update that it's included in Slackware already. I'm sorry for the
> > inconvenience.
> > Thanks,
> > Brandon
>
> Done
>
> --
> Dave
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/


Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220426/83774531/attachment.htm>

From alessandro.baggi at gmail.com  Wed Apr 27 16:27:32 2022
From: alessandro.baggi at gmail.com (Alessandro Baggi)
Date: Wed, 27 Apr 2022 18:27:32 +0200
Subject: [Slackbuilds-users] BOINC fails to build [configure step]
Message-ID: <a125d6e0-234e-b300-5080-6513f0ab7d11@gmail.com>

Hi,
I'm trying to compile boinc using slackbuilds but during the configure 
step it fails with:

checking for /usr/lib64/wx/config/gtk3-unicode-3.0... no
configure: error: No suitable wxWidgets library found.


Reading the slackbuild I found this:

--with-wx-config=/usr/lib$LIBDIRSUFFIX/wx/config/gtk3-unicode-3.0

this path really does not exist after wxGTK3 installation (statically 
compiled).

Changing

/usr/lib$LIBDIRSUFFIX/wx/config/gtk3-unicode-3.0

into

/usr/lib$LIBDIRSUFFIX/wx/config/gtk3-unicode-static-3.0

fix the problem.

Hope that helps.


From urchlay at slackware.uk  Wed Apr 27 19:48:50 2022
From: urchlay at slackware.uk (B. Watson)
Date: Wed, 27 Apr 2022 15:48:50 -0400 (EDT)
Subject: [Slackbuilds-users] BOINC fails to build [configure step]
In-Reply-To: <a125d6e0-234e-b300-5080-6513f0ab7d11@gmail.com>
References: <a125d6e0-234e-b300-5080-6513f0ab7d11@gmail.com>
Message-ID: <54d28b74-bfeb-4e8a-1786-8414d2604533@slackware.uk>



On Wed, 27 Apr 2022, Alessandro Baggi wrote:

> --with-wx-config=/usr/lib$LIBDIRSUFFIX/wx/config/gtk3-unicode-3.0
>
> this path really does not exist after wxGTK3 installation (statically 
> compiled).

You're right... but why'd you compile wxGTK3 statically?

If there's a common use case for it, if lots of people are compiling
wxGTK3 statically, the logic for detecting the correct wx-config
will have to be updated (in *every build* that uses either wxGTK3 or
wxPython)... I still haven't finished updating all of them to have the
detection at all, so if I've got to change my approach, better to do
it now.

For those unaware: the problem is that both wxGTK3 and wxPython
install a /usr/bin/wx-config symlink that points to a "config" shell
script that spits out things like CFLAGS and linker flags for linking
with that version of wx*.

For years now, we've had a situation where SlackBuild that need wxGTK3
won't build, if wxPython is also installed and was installed after
wxGTK3. The --with-wx-config stuff is an attempt to fix this.

During the run-up to the 15.0 repository, I added detection code to
quite a few (but not all) scripts that depend on wxGTK3 or wxPython,
so they'll build with the correct wx version, regardless of the order
they were installpkg'ed in.

Are lots of you compiling wxGTK3 with STATIC=yes?

From alessandro.baggi at gmail.com  Thu Apr 28 06:32:40 2022
From: alessandro.baggi at gmail.com (Alessandro Baggi)
Date: Thu, 28 Apr 2022 08:32:40 +0200
Subject: [Slackbuilds-users] BOINC fails to build [configure step]
In-Reply-To: <54d28b74-bfeb-4e8a-1786-8414d2604533@slackware.uk>
References: <a125d6e0-234e-b300-5080-6513f0ab7d11@gmail.com>
 <54d28b74-bfeb-4e8a-1786-8414d2604533@slackware.uk>
Message-ID: <1122c846-5da3-e536-bd46-e4f94afdac05@gmail.com>



Il 27/04/22 21:48, B. Watson ha scritto:
> You're right... but why'd you compile wxGTK3 statically?

Hi,
I followed the instructions found on 
https://slackbuilds.org/repository/15.0/academic/boinc/ that reports this:

"Building

(1) BOINC needs a static library for wxGTK3, compile with

   STATIC=yes ./wxGTK3.SlackBuild"



From urchlay at slackware.uk  Thu Apr 28 08:28:02 2022
From: urchlay at slackware.uk (B. Watson)
Date: Thu, 28 Apr 2022 04:28:02 -0400 (EDT)
Subject: [Slackbuilds-users] BOINC fails to build [configure step]
In-Reply-To: <1122c846-5da3-e536-bd46-e4f94afdac05@gmail.com>
References: <a125d6e0-234e-b300-5080-6513f0ab7d11@gmail.com>
 <54d28b74-bfeb-4e8a-1786-8414d2604533@slackware.uk>
 <1122c846-5da3-e536-bd46-e4f94afdac05@gmail.com>
Message-ID: <5bb62ea3-7378-3d8f-24b1-dcd14c9a95a@slackware.uk>



On Thu, 28 Apr 2022, Alessandro Baggi wrote:

>
>
> Il 27/04/22 21:48, B. Watson ha scritto:
>> You're right... but why'd you compile wxGTK3 statically?
>
> Hi,
> I followed the instructions found on 
> https://slackbuilds.org/repository/15.0/academic/boinc/ that reports this:
>
> "Building
>
> (1) BOINC needs a static library for wxGTK3, compile with
>
>  STATIC=yes ./wxGTK3.SlackBuild"

Hm. I wonder if that's still true. I know I compiled boinc with a
shared wxGTK3 (without STATIC=yes) at the time I edited its SlackBuild.

I utterly failed to notice the "needs a static library" in the README;
I was in the middle of mass-rebuilding the entire libraries/ dir (over
1000 builds). boinc failed to build because of the wxGTK3 vs. wxPython
conflict, so I fixed it... but the fix didn't take the "must be
static" into account because I just didn't notice it. The package
built anyway, so I moved on to the next build failure from the queue
(there were hundreds of them).

And running ldd on the various binaries the package, I see that
/usr/bin/boincmgr is dynamically linked with the wxGTK3 libraries
(libwx_gtk3u_xrc-3.0.so.0, etc).

boincmgr seems to run just fine, when built that way. I get a GUI
with a main window and a "choose project" dialog, both windows seem to
behave just fine.

None of the other binaries in the boinc package link with wxGTK3. I'm
assuming none of them are intended to have a GUI ("boinc" and
"boinc_client" just show messages in the terminal I start them from,
"boinccmd" shows a usage message, etc).

Can you try this yourself? Built wxGTK3 without STATIC=yes, build
boinc (without changing the script), see if it behaves properly for
you? I'm thinking the note in boinc's README is outdated and should
go away.

From slackbuilds at schoepfer.info  Thu Apr 28 11:40:46 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Thu, 28 Apr 2022 13:40:46 +0200
Subject: [Slackbuilds-users] Maintenance gummi
In-Reply-To: <fde28bbd-f0d2-7af9-d096-f7906bf021ed@slackbuilds.org>
References: <38d7990ac7969ceb1c68df71d4e0b168@schoepfer.info>
 <7cb82eaf-ba6b-9c17-e137-ba358d76ef3@slackware.uk>
 <CANi9qSt5ACt5iaQ9L8Y+tiG4Sjpgxuzr=RJV1bvAtDpOhyve=Q@mail.gmail.com>
 <6536cb2ec110f44d179d37ee483f51c9@schoepfer.info>
 <fde28bbd-f0d2-7af9-d096-f7906bf021ed@slackbuilds.org>
Message-ID: <b222e49262a2b4c06c4a393370e686ce@schoepfer.info>

On 2022-04-16 05:37, Willy Sudiarto Raharjo wrote:
>> I didn't try to contact him as Willy wrote some weeks ago on this
>> list(if i remember correctly)
>> that Larry seems not active anymore.
>> 
>> He's in cc now, Larry may i take gummi?
> 
> sure

Since the there is no reply from Larry i'll take gummi,
i'd also take the outdated trigger-rally from him.

Johannes

From sbo at linuxgalaxy.org  Fri Apr 29 00:59:54 2022
From: sbo at linuxgalaxy.org (KB_SBo)
Date: Fri, 29 Apr 2022 00:59:54 +0000
Subject: [Slackbuilds-users] BOINC fails to build [configure step]
In-Reply-To: <5bb62ea3-7378-3d8f-24b1-dcd14c9a95a@slackware.uk>
References: <a125d6e0-234e-b300-5080-6513f0ab7d11@gmail.com>
 <54d28b74-bfeb-4e8a-1786-8414d2604533@slackware.uk>
 <1122c846-5da3-e536-bd46-e4f94afdac05@gmail.com>
 <5bb62ea3-7378-3d8f-24b1-dcd14c9a95a@slackware.uk>
Message-ID: <7fe4ff1d-25b2-1bb8-cdf1-5c5701322f7f@linuxgalaxy.org>

On 4/28/22 01:28, B. Watson wrote:
>
>
> On Thu, 28 Apr 2022, Alessandro Baggi wrote:
>
>>
>>
>> Il 27/04/22 21:48, B. Watson ha scritto:
>>> You're right... but why'd you compile wxGTK3 statically?
>>
>> Hi,
>> I followed the instructions found on
>> https://slackbuilds.org/repository/15.0/academic/boinc/ that reports this:
>>
>> "Building
>>
>> (1) BOINC needs a static library for wxGTK3, compile with
>>
>>  STATIC=yes ./wxGTK3.SlackBuild"
>
> Hm. I wonder if that's still true. I know I compiled boinc with a
> shared wxGTK3 (without STATIC=yes) at the time I edited its SlackBuild.
>

I'll check the BOINC people if this is still true. I've used STATIC=yes
for years and years and years with no issues including other stuff that
needs wxGTK3. The BOINC wiki for the build deps may be outdated. Not too
surprising.

Only boincmgr GUI needs wxGTK3. pretty pictures and all that.


-Ed.
Boinc SBo Maintainer.


From sbo at linuxgalaxy.org  Fri Apr 29 01:37:22 2022
From: sbo at linuxgalaxy.org (KB_SBo)
Date: Fri, 29 Apr 2022 01:37:22 +0000
Subject: [Slackbuilds-users] BOINC fails to build [configure step]
In-Reply-To: <54d28b74-bfeb-4e8a-1786-8414d2604533@slackware.uk>
References: <a125d6e0-234e-b300-5080-6513f0ab7d11@gmail.com>
 <54d28b74-bfeb-4e8a-1786-8414d2604533@slackware.uk>
Message-ID: <dd0cbcec-c3c7-262a-6457-6e55788c031f@linuxgalaxy.org>

On 4/27/22 12:48, B. Watson wrote:
>
>
> On Wed, 27 Apr 2022, Alessandro Baggi wrote:
>
>> --with-wx-config=/usr/lib$LIBDIRSUFFIX/wx/config/gtk3-unicode-3.0
>>
>> this path really does not exist after wxGTK3 installation (statically
>> compiled).
>
> You're right... but why'd you compile wxGTK3 statically?
>

Because I said so in the README (as already mentioned in another
response).  Thus, you get
/usr/bin/wx-config -> /usr/lib64/wx/config/gtk3-unicode-static-3.0

> If there's a common use case for it, if lots of people are compiling
> wxGTK3 statically, the logic for detecting the correct wx-config
> will have to be updated

Static {yes | no} will depend on upstream source. One should never assume.

>
> For those unaware: the problem is that both wxGTK3 and wxPython
> install a /usr/bin/wx-config symlink that points to a "config" shell
> script that spits out things like CFLAGS and linker flags for linking
> with that version of wx*.

This was discussed and address at length and on this list and
Linuxquestions.  Heck, even I've forgotten a time or two (e.g. wxcam
that needs wxPython), thinking that I needed to drop it fro 15.0 until
someone on this list slapped me awake.

>
> For years now, we've had a situation where SlackBuild that need wxGTK3
> won't build, if wxPython is also installed and was installed after
> wxGTK3. The --with-wx-config stuff is an attempt to fix this.

 Perhaps an earlier if/then clause to check for and then set the correct
'--with-wx-config' path.  Perhaps something like

if [ -x /usr/lib$LIBDIRSUFFIX/wx/config/gtk3-unicode-3.0 ]; then
   WX="--with-wx-config=/usr/lib$LIBDIRSUFFIX/wx/config/gtk3-unicode-3.0"
else
   if [ -x /usr/lib$LIBDIRSUFFIX/wx/config/gtk3-unicode-3.0 ]; then

WX="--with-wx-config=/usr/lib$LIBDIRSUFFIX/wx/config/gtk3-unicode-static-3.0
   else
      WX=""
   fi
fi

I didn't catch this when I was testing, since I wasn't informed that
anyone was monkeying with the slackbuild...or didn't bother to read the
README for build requirements..or tell me that this was a problem that
needed fixing.

>
> Are lots of you compiling wxGTK3 with STATIC=yes?

Who Knows?  I know I am. No issues yet that I can recall, unless a
dangling '--with-wx-config' without notice or explanation.

Since I am working on a version update, I'll check on this static thing
an add the '--with-wx-config' if/or as needed.  If you change something,
I better get a freakin' email about it.

-Ed
Grumpy Boinc SBo Maintainer.


From fourtysixandtwo at sliderr.net  Fri Apr 29 17:26:51 2022
From: fourtysixandtwo at sliderr.net (fourtysix andtwo)
Date: Fri, 29 Apr 2022 11:26:51 -0600
Subject: [Slackbuilds-users] Taking over maintenance
Message-ID: <CAAZ8HagQr=Wd9fC9O_9875OSb+vgjd3fy=fC5wNU7zD-STLxGQ@mail.gmail.com>

Hi all,

I've been asked to take over maintenance on the following slackbuilds and
will be updating versions.

#Dominik Drobek
werkzeug

#Edinaldo P. Silva
mutagen

#Dimitris Zlatanidis
click
Flask
audioread
pyacoustid
pylast
jellyfish
musicbrainzngs
munkres
beets

Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220429/1a2a839f/attachment.htm>

From fourtysixandtwo at sliderr.net  Fri Apr 29 19:18:45 2022
From: fourtysixandtwo at sliderr.net (fourtysix andtwo)
Date: Fri, 29 Apr 2022 13:18:45 -0600
Subject: [Slackbuilds-users] Taking over maintenance
In-Reply-To: <20220429200442.027de8ed40ef90c6051f4c96@ythogtha.org>
References: <CAAZ8HagQr=Wd9fC9O_9875OSb+vgjd3fy=fC5wNU7zD-STLxGQ@mail.gmail.com>
 <20220429200442.027de8ed40ef90c6051f4c96@ythogtha.org>
Message-ID: <CAAZ8HagMm6mQVYJ4tdmYW2Fj9s+Z4qg836cDxxmYpsCJsbANDQ@mail.gmail.com>

I was wondering if that might be the best (easiest?) solution.  I've only
tested the updated versions of werkzeug, click, and Flask against each
other so far.

We can take this offline, compare notes and come up with a plan of attack
there if that's ok with you?

FYI, I'm working on the ones with the shortest list of dependencies first
to get them out of the way.

Cheers

On Fri, Apr 29, 2022 at 12:04 PM Arnaud <yth at ythogtha.org> wrote:

> > Hi all,
> >
> > I've been asked to take over maintenance on the following slackbuilds and
> > will be updating versions.
> >
> > #Dominik Drobek
> > werkzeug
> >
> > #Edinaldo P. Silva
> > mutagen
> >
> > #Dimitris Zlatanidis
> > click
> > Flask
> > audioread
> > pyacoustid
> > pylast
> > jellyfish
> > musicbrainzngs
> > munkres
> > beets
> >
> > Cheers
>
> Hello !
>
>         I've got a python3-werkzeug package ready, as a dependency of
> buildbot-badges, updated at the latest version, which is not python2
> compatible.
>
> Do you want to separate werkzeug in python2-werkzeug and python3-werkzeug
> packages, to allow updating the python3 version ?
>
> I can send you my version of the python3-werkzeug slackbuild, or take it
> as my
> own as you keep the python2-werkzeug slackBuild, your choice.
>
> Also, I actually own click-plugins, there are other click-* SlackBuilds
> around,
> maybe we could organize a centralized handling of those.
>
> Cheers !
>
>         - Yth
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220429/a55e5a84/attachment.htm>

From willysr at slackbuilds.org  Sat Apr 30 07:17:09 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 30 Apr 2022 14:17:09 +0700
Subject: [Slackbuilds-users] Updates - 20200430.1
Message-ID: <44466ca3-a048-83b1-0c09-725488963b95@slackbuilds.org>

People have been asking about how to get a consistent filename from
Github URL. Dave has written a detailed HOWTO and you can read it here
https://slackbuilds.org/GITHUB_URLs.txt


Sat Apr 30 06:54:56 UTC 2022
academic/AlphaPlot: Added (data analysis and visualization)
academic/avogadroapp: Fix DOWNLOAD.
academic/avogadroapp: Provide option to build shared/static.
academic/dakota: Update BUILD.
academic/getdp: Update README.
academic/getfem: Fix slack-desc.
academic/gmsh: Updated for version 4.10.0.
academic/x48: Added (HP48 Calculator emulator)
audio/flacon: Updated for version 8.3.0.
audio/pulseaudio-ctl: Updated for version 1.70.
audio/rack: Added (The Eurorack Simulator)
desktop/BlockstreamGreen: Added (A Bitcoin Wallet).
desktop/doctest: Added (C++ testing framework).
desktop/dunst: Updated for version 1.8.1
desktop/gfi: Added (GTK Flatpak Installer)
desktop/gmrun: Updated for version 1.3w.
desktop/jgmenu: Updated for version 4.4.0.
desktop/qt5ct: Updated for version 1.5.
desktop/sl-fortune: Added (fortune in X with a slack-ish icon)
desktop/waybar: Added (bar for wlroots based compositors).
desktop/wayfire: Added (3D wayland compositor).
desktop/wcm: Added (config manager for wayfire).
desktop/wf-config: Added (Configuration library).
desktop/wf-shell: Added (GTK3-based panel for wayfire).
desktop/xfce4-windowck-plugin: add upstream patch
desktop/yambar: Fix slack-desc.
desktop/zenity: Update for 3.42.1; update website.
development/avr-binutils: Updated for version 2.38.
development/avrdude: Updated for version 6.4.
development/composer: Updated for version 2.3.5
development/dbeaver-ce: Updated for version 22.0.3.
development/dpkg: Updated for version 1.21.7.
development/gedit-plugins: Updated for version 42.0. New maintainer.
development/gedit: Updated for version 42.0. New maintainer.
development/ghidra: Updated for version 10.1.3
development/git-lfs: Updated for version 3.1.4.
development/github-cli: Updated for version 2.9.0
development/hugo: Updated for version 0.98.0
development/idea: Updated for version 2022.1.
development/jupyter-nbclient: Update for 0.6.0
development/jupyter-nbconvert: Update for 6.5.0
development/jupyter-notebook_shim: Added (shim for Jupyter Notebook)
development/jupyter_client: Update for 7.3.0
development/jupyter_packaging: Added (Jupyter Packaging Utilities)
development/jupyter_server: Added (Jupyter Backend)
development/jupyterlab: Added (Jupyter next-gen user interface)
development/jupyterlab_server: Added (Launch a JupyterLab app)
development/mdbook: Strip binaries.
development/mysql-workbench: Updated for version 8.0.29.
development/pgmodeler: Added (PostgreSQL Database Modeler)
development/postman: Updated for version 9.16.0
development/protobuf3: Updated for version 3.20.1.
development/recutils: Added (tools/libraries to access recfiles).
development/rstudio-desktop: Update for 2022.02.2+485
development/universal-ctags: Updated for version p5.9.20211205.0
development/xmake: Updated for version 2.6.5.
games/ZEsarUX: Updated for version 10.0.
games/devilutionx: Updated for version 1.4.0.
games/dwarffortress: Added (A single-player fantasy adventure game)
games/nestopia: Add newline at EOF to README.
games/openttd: Updated for version 12.2.
games/trigger-rally: Updated for version 0.6.6.1. New maintainer.
games/worldofpadman: Remove cruft, fix icons, desktop, add wrappers.
graphics/farbfeld: Added (lossless image format)
graphics/peek: Added (an animated GIF recorder).
graphics/vuescan: Updated MD5SUMs.
graphics/vuescan: Updated for version 9.7.84.
graphics/yed: Updated for version 3.22
libraries/aqbanking: Updated for version 6.5.0.
libraries/audioread: Updated for version 2.1.9.
libraries/bullet: Updated for version 3.24.
libraries/date: Added (date and time library)
libraries/gtk-layer-shell: Added (Layer Shell GTK appls libs).
libraries/gtkglext: Fix docs.
libraries/gtkmm-utils: Fix docs.
libraries/gwenhywfar: Updated for version 5.9.0.
libraries/hoel: updated for version 1.4.22
libraries/iddawc: updated for version 1.1.3
libraries/levmar: Fix docs.
libraries/libchamplain: Fix typo in the build script
libraries/libdbi-drivers: Fix docs.
libraries/libde265: Remove tests. Update README.
libraries/libdmapsharing: Fix docs.
libraries/libfprint: Strip library; fix docs.
libraries/libg3d: Fix docs.
libraries/libgdata: Make sure we use the correct switch for tests
libraries/libgnomeuimm: Fix docs.
libraries/libgweather: Remove unused options
libraries/libheif: Updated for version 1.12.0.
libraries/libmrss: Strip library.
libraries/libquicktime: Fix docs.
libraries/libskk: Fix docs.
libraries/libticalcs2: Strip library, fix docs.
libraries/libtifiles2: Strip library, fix docs.
libraries/libtorrent-rasterbar: Update for 1.2.16
libraries/libtpms: Updated for version 0.9.4
libraries/libucil: Fix docs.
libraries/libvirt: Strip binaries.
libraries/libxdg-basedir: Updated for version 1.2.3.
libraries/lua-cjson: Strip library, use SLKCFLAGS.
libraries/lua-md5: Fix doc permissions.
libraries/mowitz: Fix docs.
libraries/munkres: Updated for version 1.1.4.
libraries/musicbrainzngs: New maintainer.
libraries/nlohmann_json: Fix slack-desc.
libraries/opendht: Fix docs.
libraries/php-redis: updated for version 5.3.7, new maintainer
libraries/process-cpp: Fix docs.
libraries/properties-cpp: Fix docs.
libraries/pyacoustid: Updated for version 1.2.2.
libraries/qt-assistant-compat: Fix doc permissions.
libraries/rabbitmq-c: Updated for version 0.11.0.
libraries/raylib: Added (Game development library).
libraries/rhonabwy: updated for version 1.1.5
libraries/simbody: Fix docs.
libraries/slib: Fix docs, make noarch.
libraries/slv2: Strip binaries.
libraries/spdlog: Updated for version 1.10.0.
libraries/tolua++: Fix doc permissions.
libraries/webkit2gtk4.1: Updated for version 2.36.1.
libraries/webkit2gtk: Updated for version 2.36.1.
libraries/wxPython4: Fix docs.
libraries/xalan-c: Fix doc permissions.
libraries/xmlrpc-c: Fix doc perms, add -j1 to make.
misc/discount: New Maintainer.
misc/dos2unix: Updated for version 7.4.2
misc/ghostpcl: Updated for version 9.56.1.
misc/gprename: Updated for version 20220206, new maintainer.
misc/sbo-templates: Updated for version 1.3.4.
misc/tal: New maintainer.
multimedia/MuseScore: build and README update
multimedia/QMPlay2: Updated for version 22.03.19.
multimedia/parole: Updated for version 4.16.0.
network/AdGuardHome: Update script.
network/AdGuardHome: Updated for version 0.107.6.
network/bitcoin: Updated for version 23.0.
network/brave-browser: Updated for version 1.38.109
network/clipgrab: Updated for version 3.9.7.
network/deluge: Update for 2.0.5
network/dropbox: Updated for version 147.4.4800.
network/elinks: Add Patches: disable suspend, -no-connect
network/fdns: Updated for version 0.9.68.
network/haproxy: Updated for version 2.5.6.
network/js185: Added (SpiderMonkey - Mozilla's JavaScript Engine).
network/mattermost-desktop: Update BUILD. New maintainer.
network/mattermost-desktop: Updated for version 5.0.4.
network/mosh: New maintainer, bash completion, ufw support.
network/opera-developer: Updated for version 88.0.4395.0.
network/opera: Updated for version 86.0.4363.23.
network/quassel-qt5: Removed (redundant; use quassel).
network/quassel: New maintainer.
network/rclone: Updated for version 1.58.1
network/seadrive-fuse: Added (SeaDrive daemon with FUSE interface)
network/signal-desktop: Updated for version 5.41.0
network/snownews: Removed (part of slackWare).
network/teamviewer: Updated for version 15.29.4
network/telegram: Updated for version 3.7.1.
network/telegram: Updated for version 3.7.3.
network/vdirsyncer: Added (cli calendar/address book sync tool)
network/wsdd2: Updated for version 1.8.6.
network/zoom-linux: Updated for version 5.10.4.2845
office/JabRef: Updated for version 5.6.
office/anorack: New Maintainer.
office/calibre-bin: Updated for version 5.41.0.
office/evolution-ews: Added (Exchange Web Services)
office/evolution: Added (Email and calendaring application)
office/gmdb2: Added (official GUI for mdbtools).
office/khal: Added (terminal/cli calendar program)
office/khard: Added (an address book for the Unix console)
office/leafpad: New Maintainer.
office/mdbtools: Updated for version 1.0.0.
office/qpdfview-qt5: Removed (redundant; use qpdfview).
office/qpdfview: New maintainer.
perl/MoarVM: Updated for version 2022.04
perl/nqp: Updated for version 2022.04
perl/perl-Devel-Trace: Added (Print each line before execution)
perl/perl-JSON-XS: Updated for version 4.03. New maintainer.
perl/perl-Types-Serialiser: Updated for v 1.01. New maintainer.
perl/perl-common-sense: Remove empty man page. New maintainer.
perl/perl-extutils-depends: Updated for version 0.8001.
perl/perl-file-basedir: Updated for version 0.09.
perl/perl-file-mimeinfo: Updated for version 0.32.
perl/rakudo: Updated for version 2022.04
python/bleach: updated for version 5.0.0
python/doit: Updated for version 0.36.0.
python/ipython: Update for 8.3.0
python/jellyfish: Updated for version 0.9.0.
python/python-confuse: Added (painless YAML config files)
python/python-mediafile: Added (read and write audio files' tags)
python/python3-aiohttp: Remove gunicorn from DEPs
python/python3-amqp: updated for version 5.1.1
python/python3-anyio: Added (Asynchronous framework)
python/python3-babel: updated for version 2.10.1
python/python3-celery: updated for version 5.2.6
python/python3-deprecation: Added (lib for handling deprecations)
python/python3-json5: Added (Python implementation of JSON5)
python/python3-prompt_toolkit: updated for version 3.0.29
python/python3-psycopg3: Added (python3 PostgreSQL database adapter)
python/python3-pytest: Update for 7.1.2
python/python3-requests-unixsocket: Added (talk to HTTP)
python/python3-sniffio: Added (detect async library)
python/python3-tomlkit: Added (Style-preserving TOML library)
ruby/3llo: Added (The interactive CLI application for Trello)
ruby/pastel: Added (independent coloring component f/ TTY toolkit.)
ruby/tty-color: Added (Terminal color capabilities detection.)
ruby/tty-cursor: Added (move the cursor and manipulate text)
ruby/tty-prompt: Added (A powerful interactive command line prompt)
ruby/tty-reader: Added (process keyboard input in character)
ruby/tty-screen: Added (Terminal screen size detection)
ruby/wisper: Added (Ruby objects w/ Publish-Subscribe capabilities.)
system/backintime: Added (simple backup tool)
system/bitrot: New Maintainer.
system/bleachbit: Updated for version 4.4.2.
system/bulk_extractor: Updated to v2.0.0
system/dosbox-dev: updated for version 0.75_pre4474
system/dump: New maintainer.
system/f3: Updated for version 8.0.
system/fprintd: Added (fingerprint scanning daemon over D-Bus)
system/linkchecker: Update DEP for GUI.
system/makeself: Don't put files directly in /usr/share.
system/monitorix: Fix download URL.
system/munin-node: Add doc directory.
system/netdata: Update README.
system/netdata: Update source to fix build with protobuf3.
system/nsca-ng: Exit nonzero if user/group don't exist.
system/nvidia-driver: Updated for version 510.68.02.
system/nvidia-kernel: Updated for version 510.68.02.
system/openrazer-kernel: Fix PRINT_PACKAGE_NAME & docs dir.
system/openrc-services: Updated for version 20210926.
system/passwordsafe: Fix doinst.sh.
system/phoronix-test-suite: Updated for version 10.8.3.
system/piper: Add doinst.sh.
system/powershell: Update for version 7.2.3.
system/python-urwid: Strip binaries.
system/razerCommander: Fix doinst.sh.
system/redis-py: updated for version 4.2.2, python3, new maintainer
system/redis: updated for version 6.2.6, new maintainer
system/sakura: New Maintainer.
system/slackrepo-hints: Updated for version 20220429.
system/sleuthkit: Updated for version 4.11.1
system/swtpm: Added (libtpms-based TPM emulator)
system/trmaid: removed, upstream disappeared, removed from pypi
system/veracrypt: Remove empty /usr/share/doc dir.
system/zsh-completions: Updated for version 0.33.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220430/15057dba/attachment-0001.asc>

From kjhambrick at gmail.com  Sat Apr 30 12:03:08 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 30 Apr 2022 07:03:08 -0500
Subject: [Slackbuilds-users] Updates - 20200430.1
In-Reply-To: <44466ca3-a048-83b1-0c09-725488963b95@slackbuilds.org>
References: <44466ca3-a048-83b1-0c09-725488963b95@slackbuilds.org>
Message-ID: <CANBHt+NfXo0Aw5RtGS4Z=9ZX3z61=-AiXZohAkMRD-AUdrdg=Q@mail.gmail.com>

On Sat, Apr 30, 2022 at 2:17 AM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> People have been asking about how to get a consistent filename from
> Github URL. Dave has written a detailed HOWTO and you can read it here
> https://slackbuilds.org/GITHUB_URLs.txt
>
>
Sat Apr 30 06:54:56 UTC 2022
>
<<snip>>

Thank you Dave and Willy for the HowTo !

-- kjh(<G> those Github URLs have been killin' me <G>)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220430/74b038c9/attachment.htm>

From phalange at komputermatrix.com  Sat Apr 30 16:17:16 2022
From: phalange at komputermatrix.com (Andrew Payne)
Date: Sat, 30 Apr 2022 12:17:16 -0400
Subject: [Slackbuilds-users] Content Disposition part 2
Message-ID: <30e6a11a74eee4cb44f192307ef220fb.squirrel@email.fatcow.com>

Hi all, revisiting the Github tarball 'content disposition' problem.

While manually tweaking the tarball url to

https://github.com/DEVELOPER/PRGNAM/archive/refs/tags/vVERSION/PRGNAM-VERSION.tar.gz

works, I have a case where the devs use underscores instead of dots and I
cannot seem to get a workable url with the above.

The result is that using wget or in my case python's urllib.request I get
a truncated tarball name, whereas downloading with firefox will retrieve
the full name.

Before I dive into how to manually fix the url or fool with content
disposition, what about using some variant of this in the slackbuild:

tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || tar xvf $CWD/$VERSION.tar.gz

This means I can copy paste the Github tarball url into the *.info file,
and it matters not how the user downloads it.

Thoughts?



From urchlay at slackware.uk  Sat Apr 30 16:43:49 2022
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 30 Apr 2022 12:43:49 -0400 (EDT)
Subject: [Slackbuilds-users] Content Disposition part 2
In-Reply-To: <30e6a11a74eee4cb44f192307ef220fb.squirrel@email.fatcow.com>
References: <30e6a11a74eee4cb44f192307ef220fb.squirrel@email.fatcow.com>
Message-ID: <4cf6e254-65e8-af8d-671b-e86120f38d39@slackware.uk>



On Sat, 30 Apr 2022, Andrew Payne wrote:

> Hi all, revisiting the Github tarball 'content disposition' problem.
>
> While manually tweaking the tarball url to
>
> https://github.com/DEVELOPER/PRGNAM/archive/refs/tags/vVERSION/PRGNAM-VERSION.tar.gz
>
> works, I have a case where the devs use underscores instead of dots and I
> cannot seem to get a workable url with the above.

Can you show us the actual URL you're having problems with?

> tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || tar xvf $CWD/$VERSION.tar.gz
>
> This means I can copy paste the Github tarball url into the *.info file,
> and it matters not how the user downloads it.
>
> Thoughts?

That will work, but it's suboptimal. If there's no other way to get a
consistent filename, it'll have to be done that way.

But it can cause problem for automated tools that people use to
download the file and check its md5sum. It can also cause problems
for the SBo source archive: https://slackware.uk/sbosrcarch/

You might want to host the file on a different web server, if you have
one handy.

From dave at slackbuilds.org  Sat Apr 30 20:09:16 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sat, 30 Apr 2022 21:09:16 +0100
Subject: [Slackbuilds-users] Content Disposition part 2
In-Reply-To: <30e6a11a74eee4cb44f192307ef220fb.squirrel@email.fatcow.com>
References: <30e6a11a74eee4cb44f192307ef220fb.squirrel@email.fatcow.com>
Message-ID: <Ym2XbE3OFiCc87VR@localhost>

On 30/04/22 12:17,
Andrew Payne <phalange at komputermatrix.com> put forth the proposition:
> Hi all, revisiting the Github tarball 'content disposition' problem.
> While manually tweaking the tarball url to
> https://github.com/DEVELOPER/PRGNAM/archive/refs/tags/vVERSION/PRGNAM-VERSION.tar.gz
> works, I have a case where the devs use underscores instead of dots and I
> cannot seem to get a workable url with the above.
> The result is that using wget or in my case python's urllib.request I get
> a truncated tarball name, whereas downloading with firefox will retrieve
> the full name.
> Before I dive into how to manually fix the url or fool with content
> disposition, what about using some variant of this in the slackbuild:


> tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || tar xvf $CWD/$VERSION.tar.gz

I mentioned using this as a last resort but if you can let us know
the link to the repo we could take a look.

> This means I can copy paste the Github tarball url into the *.info file,
> and it matters not how the user downloads it.
> Thoughts?

I have one that uses underscores in the tag - libxlswriter:

https://github.com/jmcnamara/libxlsxwriter/archive/RELEASE_1.0.2/libxlsxwriter-RELEASE_1.0.2.tar.gz

With that I use:

tar xvf $CWD/$PRGNAM-RELEASE_$VERSION.tar.gz

I should add that there are also files that are added manually by the
developer as `assets' in Github-speak, that are extra to the
automatic tag releases and can be named any way the developer likes.

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/

From kjhambrick at gmail.com  Sat Apr 30 20:23:29 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 30 Apr 2022 15:23:29 -0500
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
Message-ID: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>

All --

Been playing with the OTB.SlackBuild and OTB Version 8.0.0

I am getting clean builds and the program works as expected.

`sbolint` returns no errors or warnings, but when I run

sbopkglint /tmp/OTB-8.0.0-x86_64-1_SBo.tgz I get a hint:

Running test: 35-desktop...usr/share/applications/monteverdi.desktop: hint:
value "Education;Science;ImageProcessing;Geography;Qt;" for key
"Categories" in group "Desktop Entry" contains more than one main category;
application might appear more than once in the application menu
OK

Otherwise, all tests are OK

Note that sbopkglint returns the same hint on the  OTB Version 7.3.0
Package file.

There is a doinst.sh script that I took from the Version 7.3 SlackBuild (
below by sig )

What is the proper way to set up a Desktop App in an SBo ?

Thanks.

-- kjh

# ------------------cut  here - doinst.sh ------------------
if [ -x /usr/bin/update-desktop-database ]; then
  /usr/bin/update-desktop-database -q usr/share/applications
fi

if [ -x /usr/bin/update-mime-database ]; then
  /usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
fi

if [ -e usr/share/icons/hicolor/icon-theme.cache ]; then
  if [ -x /usr/bin/gtk-update-icon-cache ]; then
    /usr/bin/gtk-update-icon-cache -f usr/share/icons/hicolor >/dev/null
2>&1
  fi
fi
# ------------------cut there - doinst.sh ------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220430/302f874b/attachment.htm>

From dave at slackbuilds.org  Sat Apr 30 21:11:01 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sat, 30 Apr 2022 22:11:01 +0100
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
Message-ID: <Ym2l5SsbUDx6Ece5@localhost>

On 30/04/22 15:23,
Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> All --
> Been playing with the OTB.SlackBuild and OTB Version 8.0.0
> I am getting clean builds and the program works as expected.
> `sbolint` returns no errors or warnings, but when I run
> sbopkglint /tmp/OTB-8.0.0-x86_64-1_SBo.tgz I get a hint:
> Running test: 35-desktop...usr/share/applications/monteverdi.desktop: hint:
> value "Education;Science;ImageProcessing;Geography;Qt;" for key
> "Categories" in group "Desktop Entry" contains more than one main category;
> application might appear more than once in the application menu
> OK
> Otherwise, all tests are OK
> Note that sbopkglint returns the same hint on the  OTB Version 7.3.0
> Package file.
> There is a doinst.sh script that I took from the Version 7.3 SlackBuild (
> below by sig )
> What is the proper way to set up a Desktop App in an SBo ?
> Thanks.

You need to decide which menu category the application should be in,
then edit the .desktop to match.

> value "Education;Science;ImageProcessing;Geography;Qt;"

>From the description, I'd say ImageProcessing.

OTB.desktop file is installed by the application so the usual way is
to sed the file somewhere after the make install.

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/

From phalange at komputermatrix.com  Sat Apr 30 21:24:07 2022
From: phalange at komputermatrix.com (Andrew Payne)
Date: Sat, 30 Apr 2022 17:24:07 -0400
Subject: [Slackbuilds-users] Content Disposition part 2
In-Reply-To: <4cf6e254-65e8-af8d-671b-e86120f38d39@slackware.uk>
References: <30e6a11a74eee4cb44f192307ef220fb.squirrel@email.fatcow.com>
 <4cf6e254-65e8-af8d-671b-e86120f38d39@slackware.uk>
Message-ID: <6d688fc5cda40206d6714b6622398b1d.squirrel@email.fatcow.com>

D & B, it's the script I just took over for Sakura.

https://github.com/dabisu/sakura/tags

I'm sure there's a bespoke url that can be crafted, but I was curious
about a more generic solution to a problem that pops up a lot.

I can't visualize how the || "if" statement would cause trouble, but I
accept it if this is not the right fix.

In my experience, tweaking the url must be done by hand and is thus prone
to typos.

For example, my NC url had this typo:
https://github.com/nextcloud/desktop/archive/refs/tags/v3.4.3/desktop-3.4.4.tar.gz

(see the mismatched versions) and the 3.4.3 version was downloaded with no
error. (?) Copy-paste from github tarball urls is mostly fool proof.

As for my sakura slackbuild, the tarball naming is "sakura-SAKURA_3_8_5",
which is silly so I did this:

SRCNAM = SAKURA_3_8_5
[...]
tar xvf $CWD/$PRGNAM-$SRCNAM.tar.gz || tar xvf $CWD/$SRCNAM.tar.gz
mv $TMP/$PRGNAM-$SRCNAM $TMP/$PRGNAM-$VERSION
[...]


>
>
> On Sat, 30 Apr 2022, Andrew Payne wrote:
>
>> Hi all, revisiting the Github tarball 'content disposition' problem.
>>
>> While manually tweaking the tarball url to
>>
>> https://github.com/DEVELOPER/PRGNAM/archive/refs/tags/vVERSION/PRGNAM-VERSION.tar.gz
>>
>> works, I have a case where the devs use underscores instead of dots and
>> I
>> cannot seem to get a workable url with the above.
>
> Can you show us the actual URL you're having problems with?
>
>> tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || tar xvf $CWD/$VERSION.tar.gz
>>
>> This means I can copy paste the Github tarball url into the *.info file,
>> and it matters not how the user downloads it.
>>
>> Thoughts?
>
> That will work, but it's suboptimal. If there's no other way to get a
> consistent filename, it'll have to be done that way.
>
> But it can cause problem for automated tools that people use to
> download the file and check its md5sum. It can also cause problems
> for the SBo source archive: https://slackware.uk/sbosrcarch/
>
> You might want to host the file on a different web server, if you have
> one handy.
>



From urchlay at slackware.uk  Sat Apr 30 21:35:20 2022
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 30 Apr 2022 17:35:20 -0400 (EDT)
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
Message-ID: <dbcc455a-89b6-2ca0-3997-1727914d932@slackware.uk>



On Sat, 30 Apr 2022, Konrad J Hambrick wrote:

> Running test: 35-desktop...usr/share/applications/monteverdi.desktop: hint:
> value "Education;Science;ImageProcessing;Geography;Qt;" for key "Categories"
> in group "Desktop Entry" contains more than one main category; application
> might appear more than once in the application menu
> OK

This is not a serious problem. desktop-file-validate warns about it,
but doesn't count it as an error.

Personally, if it were my build, I might try to get rid of the
warning, but it's not a huge deal.

From kjhambrick at gmail.com  Sat Apr 30 21:37:21 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 30 Apr 2022 16:37:21 -0500
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <Ym2l5SsbUDx6Ece5@localhost>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
 <Ym2l5SsbUDx6Ece5@localhost>
Message-ID: <CANBHt+M18x7LKubo4VXdh-YxcHn=WEPMEBXJr7HicOxAs9tOTA@mail.gmail.com>

On Sat, Apr 30, 2022 at 4:11 PM Dave Woodfall <dave at slackbuilds.org> wrote:

> On 30/04/22 15:23,
> Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> > All --
> > Been playing with the OTB.SlackBuild and OTB Version 8.0.0
> > I am getting clean builds and the program works as expected.
> > `sbolint` returns no errors or warnings, but when I run
> > sbopkglint /tmp/OTB-8.0.0-x86_64-1_SBo.tgz I get a hint:
> > Running test: 35-desktop...usr/share/applications/monteverdi.desktop:
> hint:
> > value "Education;Science;ImageProcessing;Geography;Qt;" for key
> > "Categories" in group "Desktop Entry" contains more than one main
> category;
> > application might appear more than once in the application menu
> > OK
> > Otherwise, all tests are OK
> > Note that sbopkglint returns the same hint on the  OTB Version 7.3.0
> > Package file.
> > There is a doinst.sh script that I took from the Version 7.3 SlackBuild (
> > below by sig )
> > What is the proper way to set up a Desktop App in an SBo ?
> > Thanks.
>
> You need to decide which menu category the application should be in,
> then edit the .desktop to match.
>
> > value "Education;Science;ImageProcessing;Geography;Qt;"
>
> From the description, I'd say ImageProcessing.
>
> OTB.desktop file is installed by the application so the usual way is
> to sed the file somewhere after the make install.
>
> --
> Dave
>

Thanks Dave !

I've added an if-block to the OTB.SlackBuild:

# ---------------- cut  here -------------------
if [ "$MONTEVERDI" = "ON" ] ; then
   sed -i -e '/s/^Categories=.*$/Categories=ImageProcessing;/' \
   $PKG/usr/share/applications/monteverdi.desktop
fi
# ---------------- cut there -------------------

Rerunning `MONTEVERDI=ON ./OTB.SlackBuild` 2>&1 |tee
OTB.SlackBuild-8.0.0.log

Will know in 30 min or so :)

Thanks again !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220430/48e3f66c/attachment.htm>

From kjhambrick at gmail.com  Sat Apr 30 21:43:55 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 30 Apr 2022 16:43:55 -0500
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <dbcc455a-89b6-2ca0-3997-1727914d932@slackware.uk>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
 <dbcc455a-89b6-2ca0-3997-1727914d932@slackware.uk>
Message-ID: <CANBHt+M8zVr6bKreUYXVc6OLN=cE5n1EDrtnRf7yOUDdskKy5g@mail.gmail.com>

On Sat, Apr 30, 2022 at 4:35 PM B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Sat, 30 Apr 2022, Konrad J Hambrick wrote:
>
> > Running test: 35-desktop...usr/share/applications/monteverdi.desktop:
> hint:
> > value "Education;Science;ImageProcessing;Geography;Qt;" for key
> "Categories"
> > in group "Desktop Entry" contains more than one main category;
> application
> > might appear more than once in the application menu
> > OK
>
> This is not a serious problem. desktop-file-validate warns about it,
> but doesn't count it as an error.
>
> Personally, if it were my build, I might try to get rid of the
> warning, but it's not a huge deal.
>
> Thanks B. Watson

That's how I feel about it too :)

I think I've got it thanks to Dave's hint :)

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220430/4b85e952/attachment.htm>

From dave at slackbuilds.org  Sat Apr 30 21:54:08 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sat, 30 Apr 2022 22:54:08 +0100
Subject: [Slackbuilds-users] Content Disposition part 2
In-Reply-To: <6d688fc5cda40206d6714b6622398b1d.squirrel@email.fatcow.com>
References: <30e6a11a74eee4cb44f192307ef220fb.squirrel@email.fatcow.com>
 <4cf6e254-65e8-af8d-671b-e86120f38d39@slackware.uk>
 <6d688fc5cda40206d6714b6622398b1d.squirrel@email.fatcow.com>
Message-ID: <Ym2wAGFiClb+hOFK@localhost>

On 30/04/22 17:24,
Andrew Payne <phalange at komputermatrix.com> put forth the proposition:
> D & B, it's the script I just took over for Sakura.
> https://github.com/dabisu/sakura/tags
> I'm sure there's a bespoke url that can be crafted, but I was curious
> about a more generic solution to a problem that pops up a lot.
> I can't visualize how the || "if" statement would cause trouble, but I
> accept it if this is not the right fix.
> In my experience, tweaking the url must be done by hand and is thus prone
> to typos.
> For example, my NC url had this typo:
> https://github.com/nextcloud/desktop/archive/refs/tags/v3.4.3/desktop-3.4.4.tar.gz
> (see the mismatched versions) and the 3.4.3 version was downloaded with no
> error. (?) Copy-paste from github tarball urls is mostly fool proof.

In the end the tag wins.  The file will download as any name you
choose, so in that link it will be version 3.4.3.  This is the
correct URL for version 3.4.4:

https://github.com/nextcloud/desktop/archive/v3.4.4/desktop-3.4.4.tar.gz


> As for my sakura slackbuild, the tarball naming is "sakura-SAKURA_3_8_5",
> which is silly so I did this:
> SRCNAM = SAKURA_3_8_5
> [...]
> tar xvf $CWD/$PRGNAM-$SRCNAM.tar.gz || tar xvf $CWD/$SRCNAM.tar.gz
> mv $TMP/$PRGNAM-$SRCNAM $TMP/$PRGNAM-$VERSION
> [...]

This seems the same as libxlswriter except you have SAKURA_ instead
of RELEASE_.

SAKURA_3_8_5 is the tag/version so:

https://github.com/dabisu/sakura/archive/SAKURA_3_8_5/sakura-SAKURA_3_8_5.tar.gz

Which will extract a directory: sakura-SAKURA_3_8_5

With a more normal version 3.8.5 and like you have:

> SRCNAM = SAKURA_3_8_5

That should be OK:

tar xvf $CWD/$PRGNAM-$SRCNAM.tar.gz

Should be all that's needed.  I might be tempted to use $SRCVER
perhaps, since it is the version according to github.

> >
> > On Sat, 30 Apr 2022, Andrew Payne wrote:
> >
> >> Hi all, revisiting the Github tarball 'content disposition' problem.
> >>
> >> While manually tweaking the tarball url to
> >>
> >> https://github.com/DEVELOPER/PRGNAM/archive/refs/tags/vVERSION/PRGNAM-VERSION.tar.gz
> >>
> >> works, I have a case where the devs use underscores instead of dots and
> >> I
> >> cannot seem to get a workable url with the above.
> >
> > Can you show us the actual URL you're having problems with?
> >
> >> tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || tar xvf $CWD/$VERSION.tar.gz
> >>
> >> This means I can copy paste the Github tarball url into the *.info file,
> >> and it matters not how the user downloads it.
> >>
> >> Thoughts?
> >
> > That will work, but it's suboptimal. If there's no other way to get a
> > consistent filename, it'll have to be done that way.
> >
> > But it can cause problem for automated tools that people use to
> > download the file and check its md5sum. It can also cause problems
> > for the SBo source archive: https://slackware.uk/sbosrcarch/
> >
> > You might want to host the file on a different web server, if you have
> > one handy.
> >

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/

From phalange at komputermatrix.com  Sat Apr 30 22:00:36 2022
From: phalange at komputermatrix.com (Andrew Payne)
Date: Sat, 30 Apr 2022 18:00:36 -0400
Subject: [Slackbuilds-users] Content Disposition part 2
In-Reply-To: <Ym2wAGFiClb+hOFK@localhost>
References: <30e6a11a74eee4cb44f192307ef220fb.squirrel@email.fatcow.com>
 <4cf6e254-65e8-af8d-671b-e86120f38d39@slackware.uk>
 <6d688fc5cda40206d6714b6622398b1d.squirrel@email.fatcow.com>
 <Ym2wAGFiClb+hOFK@localhost>
Message-ID: <adef1034760f5dbbe6b3ddc222a07baa.squirrel@email.fatcow.com>

> On 30/04/22 17:24,
> Andrew Payne <phalange at komputermatrix.com> put forth the proposition:
>> D & B, it's the script I just took over for Sakura.
>> https://github.com/dabisu/sakura/tags
>> I'm sure there's a bespoke url that can be crafted, but I was curious
>> about a more generic solution to a problem that pops up a lot.
>> I can't visualize how the || "if" statement would cause trouble, but I
>> accept it if this is not the right fix.
>> In my experience, tweaking the url must be done by hand and is thus
>> prone
>> to typos.
>> For example, my NC url had this typo:
>> https://github.com/nextcloud/desktop/archive/refs/tags/v3.4.3/desktop-3.4.4.tar.gz
>> (see the mismatched versions) and the 3.4.3 version was downloaded with
>> no
>> error. (?) Copy-paste from github tarball urls is mostly fool proof.
>
> In the end the tag wins.  The file will download as any name you
> choose, so in that link it will be version 3.4.3.  This is the
> correct URL for version 3.4.4:
>
> https://github.com/nextcloud/desktop/archive/v3.4.4/desktop-3.4.4.tar.gz
>
>
>> As for my sakura slackbuild, the tarball naming is
>> "sakura-SAKURA_3_8_5",
>> which is silly so I did this:
>> SRCNAM = SAKURA_3_8_5
>> [...]
>> tar xvf $CWD/$PRGNAM-$SRCNAM.tar.gz || tar xvf $CWD/$SRCNAM.tar.gz
>> mv $TMP/$PRGNAM-$SRCNAM $TMP/$PRGNAM-$VERSION
>> [...]
>
> This seems the same as libxlswriter except you have SAKURA_ instead
> of RELEASE_.
>
> SAKURA_3_8_5 is the tag/version so:
>
> https://github.com/dabisu/sakura/archive/SAKURA_3_8_5/sakura-SAKURA_3_8_5.tar.gz
>
> Which will extract a directory: sakura-SAKURA_3_8_5
>
> With a more normal version 3.8.5 and like you have:
>
>> SRCNAM = SAKURA_3_8_5
>
> That should be OK:
>
> tar xvf $CWD/$PRGNAM-$SRCNAM.tar.gz
>
> Should be all that's needed.  I might be tempted to use $SRCVER
> perhaps, since it is the version according to github.
>
>> >
>> > On Sat, 30 Apr 2022, Andrew Payne wrote:
>> >
>> >> Hi all, revisiting the Github tarball 'content disposition' problem.
>> >>
>> >> While manually tweaking the tarball url to
>> >>
>> >> https://github.com/DEVELOPER/PRGNAM/archive/refs/tags/vVERSION/PRGNAM-VERSION.tar.gz
>> >>
>> >> works, I have a case where the devs use underscores instead of dots
>> and
>> >> I
>> >> cannot seem to get a workable url with the above.
>> >
>> > Can you show us the actual URL you're having problems with?
>> >
>> >> tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || tar xvf $CWD/$VERSION.tar.gz
>> >>
>> >> This means I can copy paste the Github tarball url into the *.info
>> file,
>> >> and it matters not how the user downloads it.
>> >>
>> >> Thoughts?
>> >
>> > That will work, but it's suboptimal. If there's no other way to get a
>> > consistent filename, it'll have to be done that way.
>> >
>> > But it can cause problem for automated tools that people use to
>> > download the file and check its md5sum. It can also cause problems
>> > for the SBo source archive: https://slackware.uk/sbosrcarch/
>> >
>> > You might want to host the file on a different web server, if you have
>> > one handy.
>> >
>
> --
> Dave
>
> sbo-maintainer-tools:
> https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
> SBo templates:
> https://slackbuilds.org/templates/
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

Ok, thanks Dave, I'll kill the "if" statement and use that URL.



From dave at slackbuilds.org  Sat Apr 30 22:10:37 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sat, 30 Apr 2022 23:10:37 +0100
Subject: [Slackbuilds-users] Content Disposition part 2
In-Reply-To: <adef1034760f5dbbe6b3ddc222a07baa.squirrel@email.fatcow.com>
References: <30e6a11a74eee4cb44f192307ef220fb.squirrel@email.fatcow.com>
 <4cf6e254-65e8-af8d-671b-e86120f38d39@slackware.uk>
 <6d688fc5cda40206d6714b6622398b1d.squirrel@email.fatcow.com>
 <Ym2wAGFiClb+hOFK@localhost>
 <adef1034760f5dbbe6b3ddc222a07baa.squirrel@email.fatcow.com>
Message-ID: <Ym2z3Ri87G4rPToM@localhost>

On 30/04/22 18:00,
Andrew Payne <phalange at komputermatrix.com> put forth the proposition:
> > On 30/04/22 17:24,
> > Andrew Payne <phalange at komputermatrix.com> put forth the proposition:
> >> For example, my NC url had this typo:
> >> https://github.com/nextcloud/desktop/archive/refs/tags/v3.4.3/desktop-3.4.4.tar.gz
> >
> > In the end the tag wins.  The file will download as any name you
> > choose, so in that link it will be version 3.4.3.  This is the
> > correct URL for version 3.4.4:
> >
> > https://github.com/nextcloud/desktop/archive/v3.4.4/desktop-3.4.4.tar.gz
> >
> >
> >> As for my sakura slackbuild, the tarball naming is
> >> "sakura-SAKURA_3_8_5",
> >> which is silly so I did this:
> >> SRCNAM = SAKURA_3_8_5
> >> [...]
> >> tar xvf $CWD/$PRGNAM-$SRCNAM.tar.gz || tar xvf $CWD/$SRCNAM.tar.gz
> >> mv $TMP/$PRGNAM-$SRCNAM $TMP/$PRGNAM-$VERSION
> >> [...]
> >
> > This seems the same as libxlswriter except you have SAKURA_ instead
> > of RELEASE_.
> >
> > SAKURA_3_8_5 is the tag/version so:
> >
> > https://github.com/dabisu/sakura/archive/SAKURA_3_8_5/sakura-SAKURA_3_8_5.tar.gz
> >
> > Which will extract a directory: sakura-SAKURA_3_8_5
> >
> > With a more normal version 3.8.5 and like you have:
> >
> >> SRCNAM = SAKURA_3_8_5
> >
> > That should be OK:
> >
> > tar xvf $CWD/$PRGNAM-$SRCNAM.tar.gz
> >
> > Should be all that's needed.  I might be tempted to use $SRCVER
> > perhaps, since it is the version according to github.
> >
> Ok, thanks Dave, I'll kill the "if" statement and use that URL.

Just to prove that the tag always wins, try:

wget https://github.com/dabisu/sakura/archive/SAKURA_3_8_5/mickey-mouse.tar.gz

It will download as mickey-mouse.tar.gz, but test it and:

tar tf mickey-mouse.tar.gz | head -n1
sakura-SAKURA_3_8_5/

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/