Re: [Slackbuilds-users] sbopkg-0.37.1 has been released.

[Jheengut Pritvi]

> -- Forwarded message --
> From: Didier Spaier 
> To: "SlackBuilds.org Users List" 
> Cc:
> Date: Thu, 29 Oct 2015 00:36:39 +0100
> Subject: [Slackbuilds-users] sbopkg-0.37.1 has been released.
> Willy didn't announce it yet, but sbopkg-0.37.1 is available.
>
> Highlights:
> _ The option --visit-items in dialogs that display a list of items
>   allow users of Braille terminals (aka screen readers) to follow
>   the cursor and know which item is highlighted.
> _ The SBo master branch repo (git) has been added.
>
> Thanks Willy for this release!
>
Great news.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

[Slackbuilds-users] Fwd: bad url for spatialite-tools

[Jheengut Pritvi]

-- Forwarded message --
From: Jheengut Pritvi <z.coldpla...@gmail.com>
Date: 17 November 2015 at 10:19
Subject: bad url for spatialite-tools
To: mail...@slackbuilds.org


 I was compiling spatialite-tools and found the download url to be
www.gaia-gis.it/gaia-sins/spatialite-tools-sources/spatialite-tools-4.2.0.tar.gz
instead of  http://www.gaia-gis.it/gaia-sins/spatialite-tools-4.2.0.tar.gz
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Moving stuff to gis/ ?

[Jheengut Pritvi]

I support to move packages into categories whose names are more intuitive
and makes more sense rather than a general category such as haskell which
does not help at all considering the large number of packages hosted there.
The next time I dwelve into slackbuilds/sbopkg to create a queue to create
new packages, I won't have to search through many categories to find one
slackbuild.

Move the packages to gis as soon as possible so that we can test whether it
does not break any automized scripts.
On 7 Jun 2016 6:13 pm, "Willy Sudiarto Raharjo" 
wrote:

> > Were you providing that as an already existing example to confirm my
> > category selection (if so, thanks) or to possibly imply that I may not
> need
> > to submit acd_cli? If it's the latter, I don't believe awscli supports
> > Amazon Cloud Drive... at least, I couldn't find any references of it.
>
> i was just pointing a probably similar application/library so you can
> take it as an example. It uses python, but it's still located in network
>
> --
> Willy Sudiarto Raharjo
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

[Slackbuilds-users] libbluray cannot be downloaded using wget

[Jheengut Pritvi]

Hi, usually slackbuilds downloads stuffs using wget.

I'm building the package libbluray but I'm getting the following error ::


libbluray:
libbluray not found in /var/cache/sbopkg.
--2016-02-22 10:24:52--
ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
   => 'libbluray-0.9.2.tar.bz2'
Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2,
2a01:e0d:1:3:58bf:fa02:c0de:20
Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:21...
connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /pub/videolan/libbluray/0.9.2 ... done.
==> SIZE libbluray-0.9.2.tar.bz2 ... 704357
==> PASV ... couldn't connect to 127.0.1.1 port 62782: Connection refused


But using curl , I was able to download libbluray.

curl
ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
>libbluray-0.9.2.tar.bz2
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed
100  687k  100  687k0 0  47257  0  0:00:14  0:00:14 --:--:--
96258


I'm using slackware-current.

wget --version
GNU Wget 1.14 built on linux-gnu.

+digest +https +ipv6 +iri +large-file +nls +ntlm +opie +ssl/openssl

Wgetrc:
/etc/wgetrc (system)
Locale: /usr/share/locale
Compile: gcc -DHAVE_CONFIG_H -DSYSTEM_WGETRC="/etc/wgetrc"
-DLOCALEDIR="/usr/share/locale" -I. -I../lib -I../lib -O2 -fPIC
Link: gcc -O2 -fPIC -lssl -lcrypto -lz -ldl -lz -lz -lidn -luuid -lpcre
ftp-opie.o openssl.o http-ntlm.o ../lib/libgnu.a

Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Originally written by Hrvoje Niksic .
Please send bug reports and questions to .
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] bad url for spatialite-tools

[Jheengut Pritvi]

Sorry to bug in again but there are other sources who need to have their
url corrected in the the Gaia-SINS federated projects home-page.

diff --git a/academic/spatialite_gui/spatialite_gui.info
b/academic/spatialite_gui/spatialite_gui.info
index 817f539..02b1dff 100644
--- a/academic/spatialite_gui/spatialite_gui.info
+++ b/academic/spatialite_gui/spatialite_gui.info
@@ -1,7 +1,7 @@
 PRGNAM="spatialite_gui"
 VERSION="1.7.1"
 HOMEPAGE="https://www.gaia-gis.it/fossil/spatialite_gui/index;
-DOWNLOAD="http://www.gaia-gis.it/gaia-sins/spatialite_gui-1.7.1.tar.gz;
+DOWNLOAD="
http://www.gaia-gis.it/gaia-sins/spatialite-gui-sources/spatialite_gui-1.7.1.tar.gz
"
 MD5SUM="c917f40810607784528b4db58cd36efb"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
diff --git a/libraries/librasterlite/librasterlite.info
b/libraries/librasterlite/librasterlite.info
index 447a91d..12310e6 100644
--- a/libraries/librasterlite/librasterlite.info
+++ b/libraries/librasterlite/librasterlite.info
@@ -1,7 +1,7 @@
 PRGNAM="librasterlite"
 VERSION="1.1g"
 HOMEPAGE="https://www.gaia-gis.it/fossil/librasterlite/index;
-DOWNLOAD="http://www.gaia-gis.it/gaia-sins/librasterlite-1.1g.tar.gz;
+DOWNLOAD="
http://www.gaia-gis.it/librasterlite-sources/gaia-sins/librasterlite-1.1g.tar.gz
"
 MD5SUM="6c6e8f83ac8a06c78f3fdcee63dc5e3e"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
diff --git a/libraries/libspatialite/libspatialite.info
b/libraries/libspatialite/libspatialite.info
index 359559f..1213d61 100644
--- a/libraries/libspatialite/libspatialite.info
+++ b/libraries/libspatialite/libspatialite.info
@@ -1,7 +1,7 @@
 PRGNAM="libspatialite"
 VERSION="4.2.0"
 HOMEPAGE="https://www.gaia-gis.it/fossil/libspatialite/index;
-DOWNLOAD="
http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-4.2.0.tar.gz
"
+DOWNLOAD="
http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-sources/libspatialite-4.2.0.tar.gz
"
 MD5SUM="83305ed694a77152120d1f74c5151779"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
diff --git a/libraries/readosm/readosm.info b/libraries/readosm/readosm.info
index 434f953..5969d64 100644
--- a/libraries/readosm/readosm.info
+++ b/libraries/readosm/readosm.info
@@ -1,7 +1,7 @@
 PRGNAM="readosm"
 VERSION="1.0.0d"
 HOMEPAGE="https://www.gaia-gis.it/fossil/readosm/index;
-DOWNLOAD="http://www.gaia-gis.it/gaia-sins/readosm-1.0.0d.tar.gz;
+DOWNLOAD="
http://www.gaia-gis.it/readosm-sources/gaia-sins/readosm-1.0.0d.tar.gz;
 MD5SUM="ba74b5141f115de5d240cf4a40478336"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""

I am using SBo-master on slackware-current.

On 3 December 2015 at 13:36, Jheengut Pritvi <z.coldpla...@gmail.com> wrote:

>
> -- Forwarded message --
> From: Jheengut Pritvi <z.coldpla...@gmail.com>
> Date: 17 November 2015 at 10:19
> Subject: bad url for spatialite-tools
> To: mail...@slackbuilds.org
>
>
>  I was compiling spatialite-tools and found the download url to be
> www.gaia-gis.it/gaia-sins/spatialite-tools-sources/spatialite-tools-4.2.0.tar.gz
> instead of  http://www.gaia-gis.it/gaia-sins/spatialite-tools-4.2.0.tar.gz
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] bad url for spatialite-tools

[Jheengut Pritvi]

Hi, the website of spatialite has undergone a revamp.
The source url has changed again.

diff --git a/libraries/librasterlite/librasterlite.info
b/libraries/librasterlite/librasterlite.info$
index 12310e6..447a91d 100644$
--- a/libraries/librasterlite/librasterlite.info$
+++ b/libraries/librasterlite/librasterlite.info$
@@ -1,7 +1,7 @@$
 PRGNAM="librasterlite"$
 VERSION="1.1g"$
 HOMEPAGE="https://www.gaia-gis.it/fossil/librasterlite/index"$
-DOWNLOAD="
http://www.gaia-gis.it/librasterlite-sources/gaia-sins/librasterlite-1.1g.tar.gz
"$
+DOWNLOAD="http://www.gaia-gis.it/gaia-sins/librasterlite-1.1g.tar.gz"$
 MD5SUM="6c6e8f83ac8a06c78f3fdcee63dc5e3e"$
 DOWNLOAD_x86_64=""$
 MD5SUM_x86_64=""$
diff --git a/libraries/libspatialite/libspatialite.info
b/libraries/libspatialite/libspatialite.info$
index 1213d61..359559f 100644$
--- a/libraries/libspatialite/libspatialite.info$
+++ b/libraries/libspatialite/libspatialite.info$
@@ -1,7 +1,7 @@$
 PRGNAM="libspatialite"$
 VERSION="4.2.0"$
 HOMEPAGE="https://www.gaia-gis.it/fossil/libspatialite/index"$
-DOWNLOAD="
http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-sources/libspatialite-4.2.0.tar.gz
"$
+DOWNLOAD="
http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-4.2.0.tar.gz
"$
 MD5SUM="83305ed694a77152120d1f74c5151779"$
 DOWNLOAD_x86_64=""$
 MD5SUM_x86_64=""$
diff --git a/libraries/readosm/readosm.info b/libraries/readosm/readosm.info
$
index 5969d64..c67964a 100644$
--- a/libraries/readosm/readosm.info$
+++ b/libraries/readosm/readosm.info$
@@ -1,7 +1,7 @@$
 PRGNAM="readosm"$
 VERSION="1.0.0d"$
 HOMEPAGE="https://www.gaia-gis.it/fossil/readosm/index"$
-DOWNLOAD="
http://www.gaia-gis.it/readosm-sources/gaia-sins/readosm-1.0.0d.tar.gz"$
+DOWNLOAD="
http://www.gaia-gis.it/gaia-sins/readosm-sources/readosm-1.0.0d.tar.gz"$
 MD5SUM="ba74b5141f115de5d240cf4a40478336"$
 DOWNLOAD_x86_64=""$
 MD5SUM_x86_64=""$



On 25 February 2016 at 20:26, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > Sorry to bug in again but there are other sources who need to have their
> > url corrected in the the Gaia-SINS federated projects home-page.
> >
> > diff --git a/academic/spatialite_gui/spatialite_gui.info
> > b/academic/spatialite_gui/spatialite_gui.info
> > index 817f539..02b1dff 100644
> > --- a/academic/spatialite_gui/spatialite_gui.info
> > +++ b/academic/spatialite_gui/spatialite_gui.info
> > @@ -1,7 +1,7 @@
> >  PRGNAM="spatialite_gui"
> >  VERSION="1.7.1"
> >  HOMEPAGE="https://www.gaia-gis.it/fossil/spatialite_gui/index;
> > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/spatialite_gui-1.7.1.tar.gz;
> > +DOWNLOAD="
> >
> http://www.gaia-gis.it/gaia-sins/spatialite-gui-sources/spatialite_gui-1.7.1.tar.gz
> > "
> >  MD5SUM="c917f40810607784528b4db58cd36efb"
> >  DOWNLOAD_x86_64=""
> >  MD5SUM_x86_64=""
> > diff --git a/libraries/librasterlite/librasterlite.info
> > b/libraries/librasterlite/librasterlite.info
> > index 447a91d..12310e6 100644
> > --- a/libraries/librasterlite/librasterlite.info
> > +++ b/libraries/librasterlite/librasterlite.info
> > @@ -1,7 +1,7 @@
> >  PRGNAM="librasterlite"
> >  VERSION="1.1g"
> >  HOMEPAGE="https://www.gaia-gis.it/fossil/librasterlite/index;
> > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/librasterlite-1.1g.tar.gz;
> > +DOWNLOAD="
> >
> http://www.gaia-gis.it/librasterlite-sources/gaia-sins/librasterlite-1.1g.tar.gz
> > "
> >  MD5SUM="6c6e8f83ac8a06c78f3fdcee63dc5e3e"
> >  DOWNLOAD_x86_64=""
> >  MD5SUM_x86_64=""
> > diff --git a/libraries/libspatialite/libspatialite.info
> > b/libraries/libspatialite/libspatialite.info
> > index 359559f..1213d61 100644
> > --- a/libraries/libspatialite/libspatialite.info
> > +++ b/libraries/libspatialite/libspatialite.info
> > @@ -1,7 +1,7 @@
> >  PRGNAM="libspatialite"
> >  VERSION="4.2.0"
> >  HOMEPAGE="https://www.gaia-gis.it/fossil/libspatialite/index;
> > -DOWNLOAD="
> >
> http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-4.2.0.tar.gz
> > "
> > +DOWNLOAD="
> >
> http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-sources/libspatialite-4.2.0.tar.gz
> > "
> >  MD5SUM="83305ed694a77152120d1f74c5151779"
> >  DOWNLOAD_x86_64=""
> >  MD5SUM_x86_64=""
> > diff --git a/libraries/readosm/readosm.info b/libraries/readosm/
> readosm.info
> > index 434f953..5969d64 100644
> > --- a/libraries/readosm/readosm.info
> > +++ b/libraries/readosm/readosm.info
> > @@ -1,7 +1,7 @@
> >  PRGNAM="readosm"
> >  VERSION="1.0.0d"
> >  HOMEPAGE="https://www.gaia-gis.it/fossil/readosm/index;
> > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/readosm-1.0.0d.tar.gz;
> > +DOWNLOAD="
> > http://www.gaia-gis.it/readosm-sources/gaia-sins/readosm-1.0.0d.tar.gz;
> >  MD5SUM="ba74b5141f115de5d240cf4a40478336"
> >  DOWNLOAD_x86_64=""
> >  MD5SUM_x86_64=""
> >
> > I am using SBo-master on slackware-current.
>
> all applied to my branch
>
> Thanks
>
>
> --
> Willy Sudiarto Raharjo
>
>
> ___
> SlackBuilds-users mailing list
> 

Re: [Slackbuilds-users] bad url for spatialite-tools

[Jheengut Pritvi]

I visited the Gaia-SINS http://www.gaia-gis.it/gaia-sins/index.html websit.

There are two Obsolete / Discontinued software [no longer maintained] ::
libgaiagraphics  sources  a library supporting common-utility raster
handling methods
librasterlite  sources  a library allowing to store huge raster coverages
within a SpatiaLite DBMS

Would it be safe to continue to use these software in 14.2?

PS: librasterlite has a new version::
librasterlite2  sources  an advanced library supporting raster handling
method

On 25 February 2016 at 20:26, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > Sorry to bug in again but there are other sources who need to have their
> > url corrected in the the Gaia-SINS federated projects home-page.
> >
> > diff --git a/academic/spatialite_gui/spatialite_gui.info
> > b/academic/spatialite_gui/spatialite_gui.info
> > index 817f539..02b1dff 100644
> > --- a/academic/spatialite_gui/spatialite_gui.info
> > +++ b/academic/spatialite_gui/spatialite_gui.info
> > @@ -1,7 +1,7 @@
> >  PRGNAM="spatialite_gui"
> >  VERSION="1.7.1"
> >  HOMEPAGE="https://www.gaia-gis.it/fossil/spatialite_gui/index;
> > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/spatialite_gui-1.7.1.tar.gz;
> > +DOWNLOAD="
> >
> http://www.gaia-gis.it/gaia-sins/spatialite-gui-sources/spatialite_gui-1.7.1.tar.gz
> > "
> >  MD5SUM="c917f40810607784528b4db58cd36efb"
> >  DOWNLOAD_x86_64=""
> >  MD5SUM_x86_64=""
> > diff --git a/libraries/librasterlite/librasterlite.info
> > b/libraries/librasterlite/librasterlite.info
> > index 447a91d..12310e6 100644
> > --- a/libraries/librasterlite/librasterlite.info
> > +++ b/libraries/librasterlite/librasterlite.info
> > @@ -1,7 +1,7 @@
> >  PRGNAM="librasterlite"
> >  VERSION="1.1g"
> >  HOMEPAGE="https://www.gaia-gis.it/fossil/librasterlite/index;
> > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/librasterlite-1.1g.tar.gz;
> > +DOWNLOAD="
> >
> http://www.gaia-gis.it/librasterlite-sources/gaia-sins/librasterlite-1.1g.tar.gz
> > "
> >  MD5SUM="6c6e8f83ac8a06c78f3fdcee63dc5e3e"
> >  DOWNLOAD_x86_64=""
> >  MD5SUM_x86_64=""
> > diff --git a/libraries/libspatialite/libspatialite.info
> > b/libraries/libspatialite/libspatialite.info
> > index 359559f..1213d61 100644
> > --- a/libraries/libspatialite/libspatialite.info
> > +++ b/libraries/libspatialite/libspatialite.info
> > @@ -1,7 +1,7 @@
> >  PRGNAM="libspatialite"
> >  VERSION="4.2.0"
> >  HOMEPAGE="https://www.gaia-gis.it/fossil/libspatialite/index;
> > -DOWNLOAD="
> >
> http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-4.2.0.tar.gz
> > "
> > +DOWNLOAD="
> >
> http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-sources/libspatialite-4.2.0.tar.gz
> > "
> >  MD5SUM="83305ed694a77152120d1f74c5151779"
> >  DOWNLOAD_x86_64=""
> >  MD5SUM_x86_64=""
> > diff --git a/libraries/readosm/readosm.info b/libraries/readosm/
> readosm.info
> > index 434f953..5969d64 100644
> > --- a/libraries/readosm/readosm.info
> > +++ b/libraries/readosm/readosm.info
> > @@ -1,7 +1,7 @@
> >  PRGNAM="readosm"
> >  VERSION="1.0.0d"
> >  HOMEPAGE="https://www.gaia-gis.it/fossil/readosm/index;
> > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/readosm-1.0.0d.tar.gz;
> > +DOWNLOAD="
> > http://www.gaia-gis.it/readosm-sources/gaia-sins/readosm-1.0.0d.tar.gz;
> >  MD5SUM="ba74b5141f115de5d240cf4a40478336"
> >  DOWNLOAD_x86_64=""
> >  MD5SUM_x86_64=""
> >
> > I am using SBo-master on slackware-current.
>
> all applied to my branch
>
> Thanks
>
>
> --
> Willy Sudiarto Raharjo
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

[Slackbuilds-users] PRGNAM="calf" VERSION="0.0.60"

[Jheengut Pritvi]

Hi the program calf has a typo in its slackbuild

 git diff|cat
diff --git a/audio/calf/calf.SlackBuild b/audio/calf/calf.SlackBuild
index fe8e9ba..f148517 100644
--- a/audio/calf/calf.SlackBuild
+++ b/audio/calf/calf.SlackBuild
@@ -60,7 +60,7 @@ rm -rf $PKG
 mkdir -p $TMP $PKG $OUTPUT
 cd $TMP
 rm -rf $PRGNAM-$VERSION
-tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $VERSION.tar.gz
+tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $CWD/$VERSION.tar.gz
 cd $PRGNAM-$VERSION
 chown -R root:root .
 find -L . \
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] package for grab: sage

[Jheengut Pritvi]

Hi, I'm willing to take over,  this is an important component of my Slack
boxes.
On 26 Mar 2016 2:13 pm, "Willy Sudiarto Raharjo" 
wrote:

> Anyone who is interested to maintain sage please let me know
>
> NOTE: This package takes quite a long time and requires big space to build
>
> --
> Willy Sudiarto Raharjo
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] A few issues with qgis

[Jheengut Pritvi]

Even on slackware 14.1, it gives that error, I just ignore it.

On 2 September 2016 at 17:27, Cristiano Urban  wrote:

> Hi,
>
> is there anyone who has tried to install qgis recently?
>
> I tried to install it and I get a runtime error similar to this one
> 
> when launching qgis.
>
> It seems I solved installing python-requests (as suggested).
>
>
> Cristiano.
> ___
> Site/blog @ http://crish4cks.net/
> Registered user #488179 @ http://linuxcounter.net
> Slackware, because it works! =)
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20170326.1

[Jheengut Pritvi]

I Still love it

On 29 March 2017 at 21:18, Matteo Bernardini
 wrote:
> 2017-03-29 19:03 GMT+02:00 King Beowulf :
>> "So let it be written. So let it be done."
>
> isn't that a quote from "Creeping Death"?
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Orphaned Scripts

[Jheengut Pritvi]

unfortunately except jag , I have not used any other programs

On 15 April 2017 at 20:36, Willy Sudiarto Raharjo 
wrote:

> There are some orphaned scripts in our repository.
> We are inviting any interested users/maintainers to take over some of
> these scripts.
>
> for scripts that are not a dependency for others *will* be removed in
> the next development cycle (we still don't know when).
>
> As this list may change very often, please see pasture branch for
> up-to-date list
> https://slackbuilds.org/cgit/slackbuilds/log/?h=pasture
>
> academic/slatec
> academic/suitesparse
> accessibility/Synkron
> audio/cuberok
> audio/flac123
> audio/podget
> audio/xmms-ctl
> desktop/Window_Manager_Scripts
> desktop/avant-window-navigator
> desktop/awn-extras
> desktop/gtk-kde4
> desktop/kfaenza-icon-theme
> desktop/macopix
> desktop/mimi
> desktop/neutral
> desktop/uwm
> desktop/wbar
> desktop/wmii
> development/alloy
> development/bigloo
> development/bsdiff
> development/cppcms
> development/cppdb
> development/curlpp
> development/gnustep-startup
> development/google-appengine-gosdk
> development/google-appengine-pysdk
> development/gprolog
> development/jython
> development/mcrl2
> development/mlton
> development/spin
> development/spl
> development/src-vcs
> development/thunderpad
> development/tyrutils-ericw
> development/vispatch
> games/d1x-rebirth
> games/d2x-rebirth
> games/golly
> games/jackhammer
> games/jag
> games/qstat
> games/ut2004
> gis/geogig-py
> gis/geogig
> gis/geoserver-control-flow
> gis/geoserver-css
> gis/geoserver-javascript
> gis/geoserver-oracle
> gis/geoserver-pyramid
> gis/geoserver-python
> gis/geoserver-wps
> gis/geoserver
> gis/gmapcatcher
> gis/mobac
> gis/udig
> graphics/discwrapper
> graphics/gimp-plugin-bimp
> graphics/tuxpaint-stamps
> graphics/tuxpaint
> libraries/audiere
> libraries/gliblib
> libraries/gloox
> libraries/gtkextra
> libraries/jai-imageio
> libraries/jai
> libraries/jbigkit
> libraries/libaosd
> libraries/libdesktop-agnostic
> libraries/libgringotts
> libraries/libpaper
> libraries/libtar
> libraries/lua-cmsgpack
> libraries/physfs
> misc/asterixInspector
> misc/wcd
> multimedia/dvbsnoop
> multimedia/fdkaac
> multimedia/lircaile
> multimedia/nightingale
> multimedia/subtitlecomposer
> multimedia/videocut
> network/boxcryptor
> network/glassfish
> network/gui-ufw
> network/licq
> network/pidgin-skypeweb
> network/purple-facebook
> network/skype4pidgin
> network/surfraw
> network/xinetd
> office/color-theme
> office/wink
> office/xmind
> perl/perl-Astro-SunTime
> perl/perl-CSS-Squish
> perl/perl-Class-ReturnValue
> perl/perl-Convert-UU
> perl/perl-Device-SerialPort
> perl/perl-Email-Date-Format
> perl/perl-Font-AFM
> perl/perl-IO-HTML
> perl/perl-Locale-Maketext-Lexicon
> perl/perl-MIME-Lite
> perl/perl-Module-Versions-Report
> perl/perl-PHP-Serialization
> perl/perl-PerlIO-Layers
> perl/perl-Regexp-IPv6
> perl/perl-Sub-Exporter-Progressive
> perl/perl-Sys-Mmap
> perl/perl-Test-LongString
> perl/perl-Test-Number-Delta
> perl/perl-Text-Password-Pronounceable
> perl/perl-Tree-Simple
> perl/perl-X10
> perl/perl-goo-canvas
> perl/perl-html-form
> perl/perl-http-response-encoding
> perl/perl-http-server-simple
> perl/perl-x11-protocol
> python/py4j
> python/pylirc
> system/cronie
> system/incron
> system/komparator4
> system/picocom
> system/splix
>
>
> --
> Willy Sudiarto Raharjo
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Beignet package

[Jheengut Pritvi]

On 17 April 2017 at 20:29, 414N <4...@slacky.it> wrote:

> Alan



Hi Alan , it would  be a pleasure to help since I  my laptop uses bumblebee
technology.

Question 1::

Is the Slackbuild for beignet found online? If yes, where ?

Question 2 ::
I still have not tested beignet, does the build process enable splitting
the program into several packages ,

ie, in the Linux Kernel SC, there are

make help ::

  modules_install - Install all modules to INSTALL_MOD_PATH (default: /)
  firmware_install- Install all firmware to INSTALL_FW_PATH
(default: $(INSTALL_MOD_PATH)/lib/firmware)
  headers_install - Install sanitised kernel headers to INSTALL_HDR_PATH


Do you have any idea how to install OpenCL in my case, since bumblebee is
not part of sbopkg or slackware(14.1) ? [[I will be upgrading soon, don't
worry ]]
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] slackbuilds site down =\

[Jheengut Pritvi]

it is working now

On 7 April 2017 at 22:12, Matteo Bernardini <matteo.bernard...@gmail.com> wrote:
> 2017-04-07 19:54 GMT+02:00 Jheengut Pritvi <z.coldpla...@gmail.com>:
>> rsync is not working on my side though
>>
>> ===
>> rsync slackbuilds.org::slackbuilds/14.2 .
>> rsync: failed to connect to slackbuilds.org (208.94.238.115):
>> Connection refused (111)
>> rsync error: error in socket IO (code 10) at clientserver.c(128)
>> [Receiver=3.1.0]
>> root@ # rsync rsync://slackbuilds.org/slackbuilds .
>> rsync: failed to connect to slackbuilds.org (208.94.238.115):
>> Connection refused (111)
>> rsync error: error in socket IO (code 10) at clientserver.c(128)
>> [Receiver=3.1.0]
>> root@ # nmap slackbuilds.org
>>
>> Starting Nmap 6.40 ( http://nmap.org ) at 2017-04-07 21:50 +04
>> Nmap scan report for slackbuilds.org (208.94.238.115)
>> Host is up (0.73s latency).
>> Not shown: 985 closed ports
>> PORT  STATESERVICE
>> 21/tcpopen ftp
>> 22/tcpopen ssh
>> 23/tcpfiltered telnet
>> 80/tcpopen http
>> 113/tcp   open ident
>> 135/tcp   filtered msrpc
>> 139/tcp   filtered netbios-ssn
>> 443/tcp   open https
>> 445/tcp   filtered microsoft-ds
>> 1433/tcp  filtered ms-sql-s
>> 2967/tcp  filtered symantec-av
>> 9418/tcp  open git
>> 13722/tcp filtered netbackup
>> 13782/tcp filtered netbackup
>> 13783/tcp filtered netbackup
>>
>> Nmap done: 1 IP address (1 host up) scanned in 20.30 seconds
>
> please, try again now.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] slackbuilds site down =\

[Jheengut Pritvi]

rsync is not working on my side though

===
rsync slackbuilds.org::slackbuilds/14.2 .
rsync: failed to connect to slackbuilds.org (208.94.238.115):
Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(128)
[Receiver=3.1.0]
root@ # rsync rsync://slackbuilds.org/slackbuilds .
rsync: failed to connect to slackbuilds.org (208.94.238.115):
Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(128)
[Receiver=3.1.0]
root@ # nmap slackbuilds.org

Starting Nmap 6.40 ( http://nmap.org ) at 2017-04-07 21:50 +04
Nmap scan report for slackbuilds.org (208.94.238.115)
Host is up (0.73s latency).
Not shown: 985 closed ports
PORT  STATESERVICE
21/tcpopen ftp
22/tcpopen ssh
23/tcpfiltered telnet
80/tcpopen http
113/tcp   open ident
135/tcp   filtered msrpc
139/tcp   filtered netbios-ssn
443/tcp   open https
445/tcp   filtered microsoft-ds
1433/tcp  filtered ms-sql-s
2967/tcp  filtered symantec-av
9418/tcp  open git
13722/tcp filtered netbackup
13782/tcp filtered netbackup
13783/tcp filtered netbackup

Nmap done: 1 IP address (1 host up) scanned in 20.30 seconds



Can we help you guys??

On 7 April 2017 at 17:34, Alexander Verbovetsky  wrote:
> It is back up!
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20170729.1

[Jheengut Pritvi]

Hello Ispencer,


Mea culpa for not having to report and/or find a fix to this problem.


*nvidia-35241-playing-bad-with-gnulinux.html
.*
My Slackbox running only nvidia GPU is a bit unstable and is not being
used. I think I forgot about that issue.


On 30 July 2017 at 22:29,  wrote:

> Found an error in nvidia-driver which breaks 32-bit builds, lib64 was
> hard-coded in a couple of lines.
>
> Here's my fix:
>
> ---
>
> --- nvidia-driver.SlackBuild.orig   2017-07-13 01:57:49.0 -0400
> +++ nvidia-driver.SlackBuild2017-07-30 14:14:19.059036373 -0400
> @@ -235,8 +235,8 @@
>--no-rpms --no-distro-scripts --no-kernel-module-source \
>--no-x-check --force-libglx-indirect \
>--x-prefix=$PKG/usr \
> -  --x-module-path=$PKG/usr/lib64/xorg/modules \
> -  --x-library-path=$PKG/usr/lib64 \
> +  --x-module-path=$PKG/usr/lib$LIBDIRSUFFIX/xorg/modules \
> +  --x-library-path=$PKG/usr/lib$LIBDIRSUFFIX \
>--x-sysconfig-path=$PKG/etc/X11/xorg.conf.d \
>--opengl-prefix=$PKG/usr \
>--utility-prefix=$PKG/usr \
>
> ---
>
> Hope this helps.
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] SBo services reboot today

[Jheengut Pritvi]

sbopkg -r
Syncing with the remote repository into /var/lib/sbopkg/SBo/14.1.
receiving incremental file list

sent 6,997 bytes  received 1,084,997 bytes  12,338.92 bytes/sec
total size is 76,904,353  speedup is 70.43

Rsync with the SBo repository for Slackware 14.1 complete.

Importing SBo repository for Slackware 14.1 GPG Key...
Import done.

***SYNC COMPLETE***

Slackbuilds works fine on my systems


On 28 June 2017 at 02:38, Robby Workman  wrote:

> On Tue, 27 Jun 2017 17:07:43 -0500
> Robby Workman  wrote:
>
> > We'll be rebooting the SBo host server at some point today
> > to come back up on a new non-stack-clashing kernel.
> >
> > http, ftp, rsync, and git will be offline during this reboot.
> > Mailing lists will still be accessible, although that
> > server will also need a reboot soon. We'll do them one at
> > a time...
>
>
> Back up and hopefully we'll have a long time before another
> reboot is required.
>
> -RW
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] (Temporarily) giving up my SlackBuilds

[Jheengut Pritvi]

Bonne chance a ton nouveau boulot, Niki

Cheers

Pritvi

On 22 June 2017 at 21:52, Nicolas Kovacs  wrote:

> Hi everybody,
>
> Due to an unforeseen workload, I'm currently unable to maintain my
> Slackware packages, so I'd like to give up maintenance to anybody who
> might be willing to take them.
>
> For the moment, there's at least one package that needs an urgent
> version bump: elementary-xfce. Sources for the old version aren't
> available anymore.
>
> On a side note: I'm currently working as a hired admin for a french
> administration, and I'm spending my time getting up to speed with the
> innards of CentOS 7.
>
> Cheers,
>
> Niki
> --
> Microlinux - Solutions informatiques durables
> 7, place de l'église - 30730 Montpezat
> Web  : http://www.microlinux.fr
> Mail : i...@microlinux.fr
> Tél. : 04 66 63 10 32
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] All SlackBuilds.org services migrated - Sat May 20 03:04:17 UTC 2017

[Jheengut Pritvi]

Happy Slacking

On 20 May 2017 at 07:04, Robby Workman  wrote:

> As willysr mentioned in his earlier Updates mail, we have officially
> migrated all SlackBuilds.org services to virtual machines hosted on
> our new hardware provided by combined donations from our datacenter
> ( http://onyxlight.net ), DistroWatch ( http://distrowatch.com ),
> and members of the SBo community.
>
> DNS updates should be propagated to all well-behaved DNS servers
> by now. If the homepage doesn't look just a little bit different
> than it used to, then you are not seeing the new machine (hint:
> there's a note at the top of the page).
>
> Please take a look at the contributors page and pass along appropriate
> appreciation for those individuals and organizations; as I've said
> before, words can't adequately express just how thankful we are
> for the support we get from our community.  If you are one of the
> contributors and would like a hyperlink to somewhere with your
> name, let us know and we'll make that happen.
>
> I'd also like to thank the other SBo admins; erik and I did the
> setup and configuration of the host machine, but ponce handled
> the lighttpd integration with cgit on the git machine, and
> rob0 handled the dns and helped troubleshoot some mail issues
> with the submit form, and pprkut, idlemoor, and willysr helped
> out with the website migration, database issues, testing (of
> course), and various other things I've surely forgotten. On
> that note, there's almost surely someone else who helped out
> and feels sad that I didn't mention them, so if you are that
> person, ping me and I'll fix that.
>
> As usual, we tested this pretty well before we went live with it,
> but we probably missed something - let us know if anything seems
> off.
>
> Happy Slacking!
>
> -RW
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Batch update to Perl homepage/download URLs

[Jheengut Pritvi]

Kudos to Chris for the great work

On Sun, 27 May 2018, 08:14 Willy Sudiarto Raharjo, 
wrote:

> >> Can you send your PR to https://github.com/SlackBuildsOrg/slackbuilds/
> ?
> >> It will be easier to merge :)
> >
> > Sorry, I didn't notice the GitHub mirror --- here you go:
> >
> > https://github.com/SlackBuildsOrg/slackbuilds/pull/111
>
> and merged to my branch already
>
> Again, big thanks!!
>
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Jheengut Pritvi]

With the forthcoming of Slackware 15.0, I have been nostalgic of the
days when I tried crazy thing with my Slackbox. One of those was using
BSD's ports and portage within Slackware. It was a succees and a
failure too. In those times, I was not using slackbuilds.org.
The big question:::
Is it worthwhile for a ports/portage/pacman like package manager for
Slackware that manages both binary and source packages?


It could be tool on top of pkgtool and sbopkg.

What is your opinion?
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Jheengut Pritvi]

But pkgsrc does not use the slackbuilds.org Slackbuilds to build packages.

On 16 February 2018 at 14:11, Noryungi <noryu...@gmail.com> wrote:
> If you go that way, may I draw your attention to the fact that NetBSD pkgsrc
> exists and works very well under Slackware?
>
> Why reinvent the wheel?
>
> On Feb 16, 2018 09:29, "Jheengut Pritvi" <z.coldpla...@gmail.com> wrote:
>>
>> With the forthcoming of Slackware 15.0, I have been nostalgic of the
>> days when I tried crazy thing with my Slackbox. One of those was using
>> BSD's ports and portage within Slackware. It was a succees and a
>> failure too. In those times, I was not using slackbuilds.org.
>> The big question:::
>> Is it worthwhile for a ports/portage/pacman like package manager for
>> Slackware that manages both binary and source packages?
>>
>>
>> It could be tool on top of pkgtool and sbopkg.
>>
>> What is your opinion?
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Jheengut Pritvi]

On 19 Feb 2018 12:47 am, "Didier Spaier"  wrote:

Le 18/02/2018 à 21:19, B Watson a écrit :
> On 2/18/18, Didier Spaier  wrote:
>>>
>>> When installing software, if a package is available through slapt-get,
>>> it will install it, otherwise it will install it through slapt-src. If
>>> any SlackBuild dependencies are available through slapt-get, it will
>>> install them through slapt-get.
>
> This sounds like a recipe for disaster.

Possibly,indeed, it it's misused.

> SBo packages are tested with
> dependencies from SBo, this thing would install binaries from elsewhere if
> it can find them?

>From elsewhere but not from anywhere.

I did my best to warn at least the Slint users, cf.
http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-
get/slapt-getrc.x86_64
which links to:
http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-
get/README.slaptgetrc.Slint

But have all users read the docs won't happen, I know...

> Right now there's a guy on IRC complaining that alienbob's vlc package
> segfaults, and it turns out to be because he's using SBo's qt5 instead
> of alienbob's. Mixing and matching repos is the cause, in other words.

Yes. Incidentally that's why I ended up including in the Slint repo a
vlc-2.2.8 package built against qt4, using Eric's SlackBuild.

Cheers, Didier
___



I will look into the slapt-xxx,

Cheers Pritvi
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Jheengut Pritvi]

On 16 February 2018 at 12:29, Jheengut Pritvi <z.coldpla...@gmail.com> wrote:

> The big question:::
> Is it worthwhile for a ports/portage/pacman like package manager for
> Slackware that manages both binary and source packages?
>
>
> It could be tool on top of pkgtool and sbopkg.


On 18 February 2018 at 11:37, B Watson <yalh...@gmail.com> wrote:
> On 2/18/18, Jheengut Pritvi <z.coldpla...@gmail.com> wrote:
>> But pkgsrc does not use the slackbuilds.org Slackbuilds to build packages.
>


> Have you looked at sbotools? It's at least somewhat similar to
> ports/pkgsrc (or anyway it's been described to me that way, I haven't
> actually used it).
>

Sbotools provide a big overhead in providing dependency resolution in
the form of  handling of requirements from a slackbuild’s .info file,

I am looking forward for something that can manage packages from both
Slackware and slackbuilds.org.
Slackpkg+ deals with multiple online/offline repositories.

Slax used to build a Live ISO from Slackbuilds from the Slackware Source repo.

In the long run, I am projecting to alleviate between building
packages from scratch like gentoo for an optimized built for my
SlackBoxes,
for testing purposes.


> If you google for Slackware + pkgsrc, you probably will find an ancient
> set of directions that you should *not* follow (it involves replacing
> most of the OS with pkgsrc equivalents, and "rm -rf /var/log/packages"
> is one of the steps in the procedure...)

I tried it along time back and still not fancy it that much.


My supposition  is the ability to manage packages from a singular
command from maybe multiple binary repo and source repo.


Slackware is meant to be installed as a whole.
What if you want the simplicity of Slackware and the ability to
install a small base along with with a few other packages and optimize
it with reduced dependencies for new packages. This is a lot to ask,
other distro offer some of these options but gives you too much
overhead and headache.

The answer might lie in using something else, I am unable to put it in words,..
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Proposal for Slackware category in SBo

[Jheengut Pritvi]

On 22 March 2018 at 23:46, Ricardo J. Barberis  wrote:
> El Jueves 22/03/2018 a las 16:00, David Woodfall escribió:
>> On Friday 23 March 2018 07:27,
>> kla...@mixedsignals.ml  put forth the proposition:
>> >Rich's recent question (from which I learned much) made me think that
>> >maybe there ought to be a "Slackware" category in the SBo repo.
>> >
>> >A "Slackware" category would contain applications that are useful only
>> >in Slackware. That is to say: there are applications that are useful
>> >across Linux, and then there are tools that are designed exclusively
>> >for Slackware (usually package management, often based on either
>> >Slackpkg or SBo). Tools that are useful in BOTH Linux and Slackware
>> >would *not* appear in this category.
>> >
>> >Here are some examples. See how many of them you knew existed, and how
>> >many you know about but think more people might need help finding:
>> >* sbopkg
>> >* sboui
>> >* sbbdep
>> >* slackpkg+
>> >* sport
>> >* sbotools
>
> Some of those are not on SBo.
>
>> * mkslack :)
>
> Nice one!
>
>
> Also: https://slackbuilds.org/result/?search=slackware
>
> That query returns, among others:
>
> asbt
> slack-utils
> slackchlog
> slackroll
> slpkg
> sun
> swun
>
> So, maybe simply tagging Slackware specific utilities with "slackware" would
> be enough.
>
> Or at least a start :)
>

thumbs up


>
>> >It seems to me like hiding great Slackware-specific sys utils harms
>> >discoverability, and mixing them into other, broader categories serves
>> >no purpose anyway. Sure, sboui might be a System tool, but let's face
>> >it: it's a Slackware "addon" that nobody knows to look for, and it's
>> >not just a system tool, it's a Slackware tool. Why not create a
>> >category we can all go to when we have questions like Rich's, and see
>> >what cool script or application one of our colleagues has written to
>> >scratch the itch?
>> >
>> >Can anyone think of a reason this would be harmful, or not helpful?
>> >
>> >-klaatu
>
> --
> Ricardo J. Barberis
> Usuario Linux Nº 250625: http://counter.li.org/
> Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
> Senior SysAdmin / IT Architect - www.DonWeb.com
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Feedback needed: nodejs changes

[Jheengut Pritvi]

Hi,
I have only one project depending upon nodejs so I will help as much as is
possible.

Cheers Pritvi

On Sat, 29 Dec 2018, 03:40 Willy Sudiarto Raharjo  Hi all,
>
> Nodejs6 has entered maintenance release since April 2018 and it will be
> EOL'ed in April 2019. Since nothing is depending on this package, i plan
> to remove this package in 2019 if no one objected. I will push the
> latest stable update in today's public update.
>
> Current nodejs will be upgraded to nodejs v10 as the latest LTS release
> and it will be considered an active release until April 2020 and EOL'ed
> in April 2021
>
> A new nodejs8 will be submitted if needed just in case there are some
> packages that still incompatible with the latest nodejs v10. I will push
> it after today's public update and give some time for users to migrate
> and test their applications.
>
> Any suggestions?
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm

[Jheengut Pritvi]

On Fri, 14 Dec 2018, 23:23 Matteo Bernardini  Il giorno ven 14 dic 2018 alle ore 16:13 Jheengut Pritvi
>  ha scritto:
> > /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such
> file or directory
> >
> > I have been reading some forums and it seems this issue started when
> there was a change in
> > gcc version bump as from 6.0.  Could you please confirm or  I will make
> a new thread.
> >
> > I am using Slackware-current and sbopkg. Three times I compiled and got
> the same error.
>
> hi Pritvi,
>
> just version-bump qbs to 1.12.2 and qt-creator to 4.8.0 using the
> existing SlackBuilds and they will build fine also on current.
>
> Matteo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/


Thanks for your reply,
This is what I am now doing .

This evening I will check if everything has built well.

>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm

[Jheengut Pritvi]

On Sun, 16 Dec 2018 at 11:50, Andrzej Telszewski 
wrote:

> On 16/12/2018 06:52, Jheengut Pritvi wrote:
> >
> >
> > On Fri, 14 Dec 2018, 23:23 Matteo Bernardini
> > mailto:matteo.bernard...@gmail.com> wrote:
> >
> > Il giorno ven 14 dic 2018 alle ore 16:13 Jheengut Pritvi
> > mailto:z.coldpla...@gmail.com>> ha scritto:
> >  > /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No
> > such file or directory
> >  >
> >  > I have been reading some forums and it seems this issue started
> > when there was a change in
> >  > gcc version bump as from 6.0.  Could you please confirm or  I
> > will make a new thread.
> >  >
> >  > I am using Slackware-current and sbopkg. Three times I compiled
> > and got the same error.
> >
> > hi Pritvi,
> >
> > just version-bump qbs to 1.12.2 and qt-creator to 4.8.0 using the
> > existing SlackBuilds and they will build fine also on current.
> >
> > Matteo
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@slackbuilds.org
> > <mailto:SlackBuilds-users@slackbuilds.org>
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives -
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> >
> > Thanks for your reply,
> > This is what I am now doing .
> >
> > This evening I will check if everything has built well.
> >
>
> Hi,
>
> I'm in the process of updating the SlackBuilds.
>
> So far, I successfully compiled Qbs (1.12.2) and Qt Creator (4.8).
>
> I was also able to compile the LLVM/Clang (7.0) from
> https://code.qt.io/clang/llvm
> This is the recommended version of Clang to be used with QtC 4.8+.
>
> BUT, I haven't yet tested building QtC against this Clang version.
>
> If all goes well, the updated SlackBuilds should land in SBo in a couple
> of days.
>
> I'm building on 14.2.
>
> --
> Best regards,
> Andrzej Telszewski
>


Awesome, thanks for the update!

I have successfully build qtcreator 4.8 with qbs 1.12.1 using  alien bob's
qt5 5.11.2, not slackbuilds qt5.

Best Regards

Pritvi Jheengut
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm

[Jheengut Pritvi]

On Tue, 15 May 2018 at 17:25, Andrzej Telszewski 
wrote:

> On 11/05/18 02:27, B Watson wrote:
> > On 5/10/18, Andrzej Telszewski  wrote:
> >>
> >> Because it builds fine on my side, I run out of ideas what might be
> >> wrong on his side.
> >
> > You and your user both using the same version of Slackware, the same arch
> > (32-bit or 64-bit)? With or without multilib, if you're both on 64-bit?
>
> He confirms that our setups are mostly the same.
> Anyway, I asked him to post to the ML.
>
> Thanks.
>
> --
> Best regards / Pozdrawiam,
> Andrzej Telszewski
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/




Hi,
I am also having some issues but I need to confirm if this is the case to
continue in this thread since I am not using qt-creator-llvm.
I could not compile qt-creator-llvm initially, I will try again and post in
the future.
























*cd clangbackend/ && ( test -e Makefile || /usr/bin/qmake-qt5 -o Makefile
/tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/src/tools/clangbackend/clangbackend.pro
 'QMAKE_CXXFLAGS=-O2 -fPIC' QTC_PREFIX=/usr
IDE_LIBRARY_BASENAME=lib64 LLVM_INSTALL_DIR= QBS_INSTALL_DIR=/usr
DEFINES+=QBS_ENABLE_PROJECT_FILE_UPDATES ) && make -f Makefile Project
WARNING: Clang LibTooling is disabled because only version 5.0 is
supported.make[3]: Entering directory
'/tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/src/tools/clangbackend'g++ -c -O2
-fPIC -Wno-noexcept-type -O2 -O2 -fPIC -std=gnu++1y -Wall -W -D_REENTRANT
-fPIC -DQBS_ENABLE_PROJECT_FILE_UPDATES
-D'RELATIVE_PLUGIN_PATH="../lib64/qtcreator/plugins"'
-D'RELATIVE_LIBEXEC_PATH="../libexec/qtcreator"'
-D'RELATIVE_DATA_PATH="../share/qtcreator"'
-D'RELATIVE_DOC_PATH="../doc/qt-creator-4.6.2"'
-DIDE_LIBRARY_BASENAME=\"lib64\" -DQT_CREATOR -DQT_NO_CAST_TO_ASCII
-DQT_RESTRICTED_CAST_FROM_ASCII -DQT_DISABLE_DEPRECATED_BEFORE=0x050600
-DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_FAST_CONCATENATION -DQT_NO_DEBUG
-DQT_CONCURRENT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB
-DQT_CORE_LIB -I../../../src -I../../../src -I../../libs
-I/tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/tools -I../../plugins -I../../libs
-I../../libs/sqlite -I../../libs/clangsupport -Isource -isystem
/usr/include -isystem /usr/include/qt5 -isystem
/usr/include/qt5/QtConcurrent -isystem /usr/include/qt5/QtWidgets -isystem
/usr/include/qt5/QtGui -isystem /usr/include/qt5/QtNetwork -isystem
/usr/include/qt5/QtCore -I.moc/release-shared -isystem /usr/include/libdrm
-I/usr/lib64/qt5/mkspecs/linux-g++ -o
.obj/release-shared/clangcodecompleteresults.o
source/clangcodecompleteresults.cppIn file included from
/usr/include/c++/8.2.0/bits/stl_algo.h:59, from
/usr/include/c++/8.2.0/algorithm:62, from
/usr/include/qt5/QtCore/qglobal.h:142, from
/usr/include/qt5/QtCore/QtGlobal:1, from
../../libs/sqlite/sqliteglobal.h:30, from
../../libs/sqlite/utf8string.h:28, from
source/clangcodecompleteresults.h:30, from
source/clangcodecompleteresults.cpp:26:/usr/include/c++/8.2.0/cstdlib:75:15:
fatal error: stdlib.h: No such file or directory #include_next
   ^~compilation terminated.make[3]: ***
[Makefile:785: .obj/release-shared/clangcodecompleteresults.o] Error
1make[3]: Leaving directory
'/tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/src/tools/clangbackend'make[2]: ***
[Makefile:229: sub-clangbackend-make_first] Error 2make[2]: Leaving
directory '/tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/src/tools'make[1]: ***
[Makefile:179: sub-tools-make_first-ordered] Error 2make[1]: Leaving
directory '/tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/src'make: *** [Makefile:46:
sub-src-make_first-ordered] Error 2*

Especially ::

/usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such file
or directory

I have been reading some forums and it seems this issue started when there
was a change in
gcc version bump as from 6.0.  Could you please confirm or  I will make a
new thread.

I am using Slackware-current and sbopkg. Three times I compiled and got the
same error.


Cheers Pritvi
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20181229.1

[Jheengut Pritvi]

Happy new year to you all

Cheers Pritvi

On Sat, 29 Dec 2018, 05:20 Rich Shepard  On Sat, 29 Dec 2018, andrew wrote:
>
> > Thanks for all of your work in 2018 and all the other people who make SBo
> > great!
>
>And the same from me.
>
> Regards,
>
> Rich
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Feedback needed: nodejs changes

[Jheengut Pritvi]

On Sat, 29 Dec 2018, 06:47 Willy Sudiarto Raharjo  > Current nodejs will be upgraded to nodejs v10 as the latest LTS release
> > and it will be considered an active release until April 2020 and EOL'ed
> > in April 2021
>
> It turns out node 10 removed Open SSL 1.0.2 support
> (https://github.com/nodejs/node/issues/22025), so node 10 will only be
> available for next Slackware release and not in current cycle.
>
> So in the meantime, we will stick with nodejs 8 as our latest release in
> SBo repository.
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/




Hi willy,

By current cycle do you mean Slackware 14.2.
If that is the case, then I would be testing node 10 under Slackware -
current.
I only need to check whether openssl greater than 1.0.2 is available

Cheers Pritvi
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] opencv-legacy issue

[Jheengut Pritvi]

I had been able to build digikam with opencv-legacy only.

I'll give it a try next time.


On Thu, 7 Mar 2019, 11:31 Christoph Willing, 
wrote:

> On 7/3/19 6:15 am, Tim Dickson via SlackBuilds-users wrote:
> > since updating python to 3.7.2 opencv-legacy fails to build with ..
> >
> > [ 85%] Generating pyopencv_generated_include.h,
> > pyopencv_generated_funcs.h, pyopencv_generated_types.h,
> > pyopencv_generated_type_reg.h, pyopencv_generated_ns_reg.h
> > cd /tmp/SBo/opencv-3.1.0/build/modules/python3 && /usr/bin/python3
> > /tmp/SBo/opencv-3.1.0/modules/python/python3/..//src2/gen2.py
> > /tmp/SBo/opencv-3.1.0/build/modules/python3
> > /tmp/SBo/opencv-3.1.0/build/modules/python3/headers.txt
> > Note: Class l has more than 1 base class (not supported by Python C
> > extensions)
> >   Bases:  cv::a, cv::s, cv::s, cv::A, cv::l, cv::g, cv::o, cv::r,
> > cv::i, cv::t, cv::h, cv::m
> >   Only the first base class will be used
> > Note: Class l has more than 1 base class (not supported by Python C
> > extensions)
> >   Bases:  cv::a, cv::s, cv::s, cv::F, cv::i, cv::l, cv::e, cv::S,
> > cv::t, cv::o, cv::r, cv::a, cv::g, cv::e
> >   Only the first base class will be used
> > Generator error: class l (cname=cv::l) already exists
> > modules/python3/CMakeFiles/opencv_python3.dir/build.make:276: recipe for
> > target 'modules/python3/pyopencv_generated_include.h' failed
> > make[2]: *** [modules/python3/pyopencv_generated_include.h] Error 255
> > make[2]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
> > CMakeFiles/Makefile2:14021: recipe for target
> > 'modules/python3/CMakeFiles/opencv_python3.dir/all' failed
> > make[1]: *** [modules/python3/CMakeFiles/opencv_python3.dir/all] Error 2
> > make[1]: Leaving directory '/tmp/SBo/opencv-3.1.0/build'
> > Makefile:160: recipe for target 'all' failed
> > make: *** [all] Error 2
> >
> > I've checked, and made sure  opencv-legacy was not previously installed
> > when trying to recreate the package.
> > any ideas?
>
> It seems python3-3.7.2 is necessary but not sufficient by itself to
> trigger this fault. It's actually the presence of the optional numpy3
> (which requires python3) during configuration that enables building of
> the python3 wrappers, generating the error above during compilation.
>
> The simplest fix is to remove numpy3 from the system. Even with python3
> still installed (perhaps needed for other packages), the python3
> wrappers will not be generated if numpy is not available during
> configuration.
>
> This strategy allows opencv-legacy to build to completion but, of course
> without python3 wrappings. Is that a bit deal? Maybe but mitigated by:
> 1. possible use of python2 wrappings instead by installing numpy
> (not numpy3) which will use built in python2 to generate python2 wrappings.
> 2. initially, the only reason for having the opencv-legacy
> SlackBuild at all was to satisfy building a particular version of
> libkface which was required, in turn, for a particular version of
> digikam. AFAIK the python3 wrappings are not needed for this use case.
>
> Serious opencv users that may want the python3 bindings won't be using
> opencv-legacy anyway; rather the main opencv. The building of the main
> opencv package doesn't suffer this python3/numpy3 problem so I'm
> prepared to leave things as they are for opencv-legacy. Of course, if
> someone wants to research a fix, I'll happily apply it.
>
> chris
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Package name change: how to proceed

[Jheengut Pritvi]

On Sat, 2 Feb 2019, 20:46 Willy Sudiarto Raharjo  > I maintain two packages one named obnc and the other obnc-libstd. The
> > first is an Oberon compiler and basic library and the second is a
> > library for it with extra functionality. The author of the compiler has
> > decided to rename second from obnc-libstd to obnc-libext.
> >
> > How should I proceed? Should I make a new SlackBuild named obnc-libext
> > and request the removal of obnc-libstd?
>
> You can keep the same name if you like or submit a new name and leave a
> comment section  to remove the old name.
>
> > Additionally, I wanted to ask which is the correct way to proceed when
> > using the mirror of Slackbuilds on github
> > (https://github.com/willysr/slackbuilds). Is the correct way fork that
> > repository, make changes and then do a pull request? Is this better
> > (easier) for the team maintaing Slackbuilds.org than submitting the
> tar.gz?
>
> It's better to send PR/MR through this repositories:
>
> https://github.com/SlackBuildsOrg/slackbuilds/
> https://gitlab.com/SlackBuilds.org/slackbuilds/
>
> Both submission and PR/MR works fine with us
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/




Thanks so much for the update

Cheers Pritvi

>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] steam status

[Jheengut Pritvi]

Nice, keep up the work

On Sun, 2 Jun 2019 at 08:07, Willy Sudiarto Raharjo 
wrote:

> > I emailed the games/steam maintainer over a week ago about an update and
> > some extra stuff needed in the SlackBuild. I've had no reply and the
> > last update of any of his SlackBuilds looks like April 2017.
> >
> > Therefore, if no one objects within the next few days, I'd like to take
> > over the maintainership of steam and submit an updated SlackBuild.
>
> Feel free to do it
> the maintainer last commit was 3y ago
>
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Happy 13th Year SBo

[Jheengut Pritvi]

Hello,

Wow, In two months would also be 13 years since I had my first computer and
of course Slackware 10.2 was installed after 18hours of struggle.

Congratulations on the good work and

May the Source be with you.



On Sat, 8 Jun 2019 at 17:28, Didier Spaier  wrote:

> Hello,
>
> On 08/06/2019 15:16, Arkadiusz Drabczyk wrote:
> > Why does https://slackbuilds.org/contributors/ works but
> > https://slackbuilds.org/contributors says 'Sorry, that page could not
> > be found on SlackBuilds.org'?
>
> Probably that needs to add some RewriteRule in the web server
> configuration or through a .htaccess file, see for instance:
>
> https://stackoverflow.com/questions/5080495/mode-rewrite-with-without-trailing-slash-on-end-of-url
>
> Best, Didier
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20190518.1 - intel-microcode

[Jheengut Pritvi]

On Mon, 20 May 2019 at 23:06, Andrzej Telszewski 
wrote:

> Hi,
>
> The script as I submitted it, worked for me fine under slackrepo.
> I hope the updated one will work as well, but I'm too lazy to test it
> now :-)
>
> Cheers.
>
> --
> Best regards,
> Andrzej Telszewski
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

hi Andrzej,

If you are a bit busy, next time I will CC the mailing list too

Cheers
Pritvi {@zcoldplayer}
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted

[Jheengut Pritvi]

On Fri, 16 Aug 2019 at 21:22, King Beowulf  wrote:

> On 8/16/19 12:35 AM, Jheengut Pritvi wrote:
> > Hi,
> >
> > Do you mean changes about dropping support for non-GLVND libraries!
> >
> > https://devtalk.nvidia.com/default/topic/1060977
> >
> > My NVIDIA GPU's might be a bit old too, GTX840m.
> >
> > Cheers
> > Pritvi
> >
>
> Yes, that was the announcement for the new beta driver. 435.17-beta
> still supports the GT[X] 8xx series GPUs.  The cutoff is the GTX 600
> series, and my spare cards are older than that. Yours is still "new"!
>
> -Ed
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

 From this link , I found out what you mean.

https://www.geforce.co.uk/drivers


thanks
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted

[Jheengut Pritvi]

Hi,

Do you mean changes about dropping support for non-GLVND libraries!

https://devtalk.nvidia.com/default/topic/1060977

My NVIDIA GPU's might be a bit old too, GTX840m.

Cheers
Pritvi


On Fri, 16 Aug 2019 at 01:50, King Beowulf  wrote:

> Hello all
>
> Nvidia is getting ready to drop non-GLVND libraries.  This is my first
> pass to refactor the SBo scripts and get ready for 15.0 "real soon now."
>
> 430.40 mainly adds support for RTX 2080 Super cards and some minor bug
> fixes.
>
> These WILL NOT work on -current, at all, as of yet, since I need to
> resolve Mesa library conflicts and any version conflicts with libglvnd
> in the driver vs. the version in current.  I haven't had time yet to
> build a box with current and a Nvidia GPU.  All the extra Nvidia GPUs I
> have are too old for the 4xx Nvidia driver generation. Come to think of
> it, I also need a newer mobo, CPU and memory
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted

[Jheengut Pritvi]

Thanks for the information


Kool

On Sat, 17 Aug 2019 at 22:32, King Beowulf  wrote:

> On 8/17/19 8:05 AM, Jheengut Pritvi wrote:
> >
> >
> > On Fri, 16 Aug 2019 at 21:22, King Beowulf  > <mailto:kingbeow...@gmail.com>> wrote:
> >
> > On 8/16/19 12:35 AM, Jheengut Pritvi wrote:
> > > Hi,
> > >
> > > Do you mean changes about dropping support for non-GLVND libraries!
> > >
> > > https://devtalk.nvidia.com/default/topic/1060977
> > >
> > > My NVIDIA GPU's might be a bit old too, GTX840m.
> > >
> > > Cheers
> > > Pritvi
> > >
> >
> > Yes, that was the announcement for the new beta driver. 435.17-beta
> > still supports the GT[X] 8xx series GPUs.  The cutoff is the GTX 600
> > series, and my spare cards are older than that. Yours is still "new"!
> >
> > -Ed
> >
>
> >
> >  From this link , I found out what you mean.
> >
> > https://www.geforce.co.uk/drivers
> >
> >
> > thanks
> >
>
> I thought I was obvious, but ok.  Geforce.com is primarily for Windows
> users. These links are also more direct:
>
> https://www.nvidia.com/en-gb/drivers/unix/
> https://www.nvidia.com/en-gb/drivers/unix/linux-amd64-display-archive/
>
> https://www.nvidia.com/en-us/drivers/unix/
> https://www.nvidia.com/en-us/drivers/unix/linux-amd64-display-archive/
>
> And the primary support and news location is:
>
> https://devtalk.nvidia.com/
> https://devtalk.nvidia.com/default/board/98/linux/
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Hacktoberfest 2019

[Jheengut Pritvi]

Hi,

I have been participating in Hacktoberfest organised by DigitalOcean and
Github.

This year, I am organising some hackathon sessions during the month of
october in different
venues, including upcoming Google Devfest.


Would it be possible to use the Slackbuilds mirror repo on github.com for
the Hacktoberfest?

The idea is to make more people involve in Open Source, FLOSS.

Salutations
Pritvi
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Hacktoberfest 2019

[Jheengut Pritvi]

On Fri, 16 Aug 2019 at 17:17, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > I have been participating in Hacktoberfest organised by DigitalOcean and
> > Github.
> >
> > This year, I am organising some hackathon sessions during the month of
> > october in different
> > venues, including upcoming Google Devfest.
> >
> >
> > Would it be possible to use the Slackbuilds mirror repo on github.com
> >  for the Hacktoberfest?
> >
> > The idea is to make more people involve in Open Source, FLOSS.
>
> What are your plans for SBo?
>
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
Hi Willy,

I am assuming you and the rest of the Slackbuild users are aware about the
Hacktoberfest and how
it is organised. If not, ping me, I'll try my best.

For a first, it is going to be difficult to find updates to many/most
packages. In this view, is to build a
list of Slackbuilds with no maintainers or those difficult to contact. If I
get a few Slackbuilds updated,
with no active maintainers would be cool.

Secondly, I would to test some rarely used Slackbuilds under different
environments.

I have already contacted some lecturers to use one of their session for a
hackathon.
I will target future System Administrators to become acquainted in the know
how of
building your own packages.

This is a bit of an idea what I can help through this hackathon.

Salutations,
Pritvi
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Hacktoberfest 2019

[Jheengut Pritvi]

Thanks

I will surely start here and try to convert people to Slackware.

Cheers
Pritvi

On Sun, 25 Aug 2019 at 04:05, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > I am assuming you and the rest of the Slackbuild users are aware about
> > the Hacktoberfest and how
> > it is organised. If not, ping me, I'll try my best.
> >
> > For a first, it is going to be difficult to find updates to many/most
> > packages. In this view, is to build a
> > list of Slackbuilds with no maintainers or those difficult to contact.
> > If I get a few Slackbuilds updated,
> > with no active maintainers would be cool.
>
> You can start with scripts listed in pasture
> https://git.slackbuilds.org/slackbuilds/log/?h=pasture
>
> most (if not all) of it have no maintainers
>
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Suggestions for SlackBuild Usage Howto

[Jheengut Pritvi]

Hi,

Great initiative.

Keep up the good work.



On Sun, 21 Jul 2019 at 20:19, Michael Siegel  wrote:

> Hello,
>
> I have some suggestions for improving the SlackBuild Usage HOWTO at
> http://slackbuilds.org/howto/.
>
> The first section (“Caveat”) currently reads like this:
>
>   All of our scripts are written and tested for usage on the latest
>   stable release of Slackware with full installation and updated with
>   latest patches; if you're trying them on older versions of Slackware,
>   you should read this page referenced in our FAQ.
>
> My suggestion is to change that to:
>
>   All of our scripts are written and tested for usage on a full
>   installation of the latest stable release of Slackware updated with
>   the latest patches. If you're trying them on older versions of
>   Slackware, you should read this page referenced in our FAQ.
>
> Then, the Howto does not mention verification of the downloaded source
> packages. I think this should either be added to step one or be
> step two. It could be worded like this:
>
>   To verify the downloaded source's integrity, first run `md5sum
>   chemtool-1.6.14.tar.gz' to get the MD5 sum of the downloaded source
>   archive. Then compare it to the MD5 sum shown in the `chemtool.info'
>   file. If they don't match, something is wrong.
>
> I just realized that Step 1 already doesn't mention verifying the
> SlackBuild's GPG signature. I think that should be included in the Howto
> as well.
>
> So, maybe, it would be best to split Step 1 up like this:
>
>   * Step 1 – Download and verify the SlackBuild archive
>   * Step 2 – Download and verify the application's source archive
>
> What do you think?
>
>
> Best
> Michael
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Suggestions for SlackBuild Usage Howto

[Jheengut Pritvi]

Hi,

unfortunately, there is no public source code of the how-to similar to the
slacbuilds repo


https://gitlab.com/SlackBuilds.org/slackbuilds



cheers Pritvi

On Sat, 3 Aug 2019 at 01:37, Michael Siegel  wrote:

>
> Am 28.07.19 um 21:52 schrieb Jheengut Pritvi:
> > Hi,
> >
> > Great initiative.
> >
> > Keep up the good work.
>
> Thanks for the kind words.
>
> The problem is that keeping up that good work doesn't really make any
> sense if no one with write access to that page agrees to merge it. So,
> I'm just gonna wait.
>
>
> Michael
>
> > On Sun, 21 Jul 2019 at 20:19, Michael Siegel  wrote:
> >
> >> Hello,
> >>
> >> I have some suggestions for improving the SlackBuild Usage HOWTO at
> >> http://slackbuilds.org/howto/.
> >>
> >> The first section (“Caveat”) currently reads like this:
> >>
> >>   All of our scripts are written and tested for usage on the latest
> >>   stable release of Slackware with full installation and updated with
> >>   latest patches; if you're trying them on older versions of Slackware,
> >>   you should read this page referenced in our FAQ.
> >>
> >> My suggestion is to change that to:
> >>
> >>   All of our scripts are written and tested for usage on a full
> >>   installation of the latest stable release of Slackware updated with
> >>   the latest patches. If you're trying them on older versions of
> >>   Slackware, you should read this page referenced in our FAQ.
> >>
> >> Then, the Howto does not mention verification of the downloaded source
> >> packages. I think this should either be added to step one or be
> >> step two. It could be worded like this:
> >>
> >>   To verify the downloaded source's integrity, first run `md5sum
> >>   chemtool-1.6.14.tar.gz' to get the MD5 sum of the downloaded source
> >>   archive. Then compare it to the MD5 sum shown in the `chemtool.info'
> >>   file. If they don't match, something is wrong.
> >>
> >> I just realized that Step 1 already doesn't mention verifying the
> >> SlackBuild's GPG signature. I think that should be included in the Howto
> >> as well.
> >>
> >> So, maybe, it would be best to split Step 1 up like this:
> >>
> >>   * Step 1 – Download and verify the SlackBuild archive
> >>   * Step 2 – Download and verify the application's source archive
> >>
> >> What do you think?
> >>
> >>
> >> Best
> >> Michael
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] ANNOUNCE: new nvidia buildscripts

[Jheengut Pritvi]

Kool,

This is why there the kernel has been  bumped to 5.4.x on current.



On Sat, 30 Nov 2019 at 00:13, King Beowulf  wrote:

> Hello all,
> For those that use the SBo scripts for Nvidia, new buildscripts for
> 440.36 are now in pending.  These scripts work on both 14.2 (stable) and
> 15.0 (current); for current you will need kernel-5.4.0 from /testing in
> order to successfully compile the kernel module interface.
>
> Hightlights:
>
> 1. libglvnd only.
> 2. nvidia-switch removed - no longer needed.
> 3. *.la removed
> 4.nouveau blacklist still required.
>
> Please note, use "CURRENT=yes ./nvidia-driver" when on 15.0.  This is to
> keep Nvidia installer from stomping on the existing libglvnd package.
> As always, it works here (so far). On one of my boxes (GTX 1060 w/ 4K
> monitor, GTX660 w/ 2x 1080p monitors), I experienced occasional stutters
> running Borderlands 2 (native, Steam), but this could just be my weird
> setup.  The current Ryzen box completed several phoronix test suite GPU
> benchmarks successfully (GTX 950, hoping for a AMD Navi card soon).
>
> Let me know if you catch any bugs.
> -Ed
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] nodejs update for review

[Jheengut Pritvi]

On Sat, 12 Oct 2019 at 07:33, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > i'm planning to push nodejs to 10.16.x for next public update and at
> > this moment, i'm testing some packages that depends on nodejs package.
> >
> > You can see the changes in nodejs-review branch
> >
> > If you are a maintainer who have scripts that depends on nodejs, please
> > test against latest nodejs 10.16.x.
>
> Please disregard the original email
> i accidentally put the build in my current build machine instead of
> stable build machine. NodeJS 10.x will not build in stable as it
> requires OpenSSL 1.1.
>
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
Maybe that is why I had no issue when building it.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20191231.1

[Jheengut Pritvi]

Happy new year to you all.

On Tue, 31 Dec 2019 at 19:24, Glenn Becker  wrote:

> I'm not currently maintaining any Builds, but I still Slack on and it's
> made considerably more fun because of the work you all do.
>
> Special kudos to Willy who I think does a fantastic job keeping this
> monster running.
>
> Happy New Year to you all!
>
> 
> "Doctor, I have come to ask you to tell me everything you know about the
> night."
>   - Djuna Barnes,
> *Nightwood*
>
> 
>
>
> On Tue, Dec 31, 2019 at 6:22 AM Willy Sudiarto Raharjo <
> will...@slackbuilds.org> wrote:
>
>> This will be the last update in 2019 as we are heading towards 2020 in
>> few hours. It's been another wonderful year in SBo community, thanks to
>> all the maintainers who did all the great work of submitting and
>> maintaining their scripts as well as reporting any issues back to us.
>>
>> We are looking forward for more contributions in 2020.
>>
>> I wish you a happy new year 2020 :)
>>
>>
>> Tue Dec 31 11:08:04 UTC 2019
>> academic/R: Updated for version 3.6.2.
>> academic/bibletime: Updated for version 3.0_beta2.
>> academic/cadabra2: Updated for version 2.2.8.
>> academic/fet: Updated for version 5.42.1.
>> accessibility/svox: Fix download URL.
>> audio/aseqview: Fix homepage.
>> development/SQLAlchemy: Updated for version 1.3.12.
>> development/Sphinx: Updated for version 2.3.2.
>> development/as31: Minor build fix.
>> development/bed: Fix re2 builds.
>> development/check: Fix script.
>> development/cloc: Update to 1.84
>> development/dart-sdk: Added (An SDK for API).
>> development/dart: Removed (Replaced with dart-sdk).
>> development/digikey-kicad-library: Updated for v 20191024+0802230.
>> development/eclipse-cpp: Updated for version 4.14.
>> development/eclipse-java: Updated for version 4.14.
>> development/eclipse-jee: Updated for version 4.14.
>> development/gede: Updated for version 2.15.1.
>> development/git-cola: Updated for version 3.6.
>> development/meson: Update to 0.52.1
>> development/postman: Updated for version 7.14.0.
>> development/samurai: Updated for version 1.0.
>> development/vscode-bin: Updated for version 1.41.1.
>> games/fortune-farscape: Added (Farscape quotes for fortune).
>> games/zelda-roth-se: Fix MD5SUM.
>> gis/polyline: Updated for 1.4.0.
>> graphics/azpainter: Added (full color painting software)
>> graphics/draw.io: Updated for version 12.4.2.
>> graphics/gdk-pixbuf-psd: Added (gdk-pixbuf2 loader for PSD files).
>> graphics/pcx-pixbuf-loader: Added (PCX loader for gdk-pixbuf2).
>> graphics/qiv: Updated for version 2.3.2, add image formats.
>> graphics/tesseract: Updated for version 4.1.1.
>> graphics/vuescan: Updated for version 9.7.16.
>> graphics/webp-pixbuf-loader: Added (WEBP loader for gdk-pixbuf2).
>> graphics/white_dune: Fix MD5SUM.
>> graphics/xcf-pixbuf-loader: Added (gdk-pixbuf2 loader for Gimp).
>> ham/dxcc: Updated for version 20191204.
>> ham/lpsk31: Added (psk31 program for linux).
>> ham/psk31lx: Updated for version 2.2.
>> ham/twhamqth: Updated for version 2.0.
>> ham/wxapt: Updated for version 1.7.2.
>> ham/xdemorse: Updated for version 3.0.1.
>> ham/xfhell: Updated for version 3.3.
>> ham/xpsk31: Updated for version 3.3.
>> ham/xwxapt: Updated for version 2.9.
>> libraries/SOPE: Updated for version 4.2.0.
>> libraries/bullet: Updated for version 2.89.
>> libraries/glfw3: Fix download URL + i486=>i586.
>> libraries/libmediainfo: Update to 19.09
>> libraries/libwacom: Updated for version 1.2.
>> libraries/tomcat-native: Updated for version 1.2.23.
>> misc/jmri: Updated for version 4.18.
>> misc/pinfo: Updated for version 0.6.13, new maintainer.
>> multimedia/mediainfo: Update to 19.09
>> multimedia/strawberry: Updated for version 0.6.7.
>> network/AdGuardHome: Updated for version 0.100.8.
>> network/asterisk: Updated for version 16.7.0.
>> network/brave-browser: Updated for version 1.1.23.
>> network/dropbox: Updated for version 87.4.138.
>> network/hylafax+: Updated for version 7.0.1.
>> network/linksys-tftp: Added (tftp client).
>> network/newsboat: Updated for version 2.18.
>> network/nordvpn: Updated for version 3.5.0.
>> network/openresolv: Update to 3.9.2
>> network/opera-developer: Updated for version 67.0.3541.0.
>> network/qbittorrent-qt5: Updated for version 4.2.1.
>> network/qbittorrent: New maintainer and email
>> network/skypeforlinux: Updated for version 8.55.0.141.
>> network/slurm: Updated for version 19.05.5.
>> network/transgui: Update to 5.18.0
>> network/wireshark: Add missing patch.
>> network/zabbix_agentd: Updated for version 4.4.4.
>> network/zabbix_java_gateway: Updated for version 4.4.4.
>> network/zabbix_proxy: Updated for version 4.4.4.
>> network/zabbix_server: Updated for 

Re: [Slackbuilds-users] ffmpeg4 not building

[Jheengut Pritvi]

Hi,
I have not tried the latest version but can you confirm if the legacy
opencv is needed instead.


On Sun, 19 Apr 2020 at 20:15, Luveh Keraph <1.41...@gmail.com> wrote:

> I am using the following ffmpeg4.sqf file in a freshly installed (and
> up-to-date) 14.2 system:
>
> libass
> chromaprint
> frei0r
> ladspa_sdk
> libaom
> libbluray
> libbs2b
> celt
> libdc1394
> libfdk-aac
> flite
> libgme
> gsm
> libiec61883
> libavc1394
> libilbc
> libmodplug
> lame
> opencore-amr
> opencv
> opus
> rtmpdump
> rubberband
> snappy
> speex
> tesseract
> twolame
> vid.stab
> libwebp
> x264
> x265
> xvidcore
> zeromq
> zvbi
> ffmpeg4 | BINS=yes CHROMAPRINT=yes FREI0R=yes LADSPA=yes LIBAOM=yes
> LIBBLURAY=yes LIBBS2B=yes LIBCELT=yes LIBDC1394=yes LIBFDK_AAC=yes
> LIBFLITE=yes LIBGME=yes LIBGSM=yes LIBIEC61883=yes LIBILBC=yes
> LIBMODPLUG=yes LIBMP3LAME=yes LIBOPENCORE=yes LIBOPENCV=yes LIBOPUS=yes
> LIBRTMP=yes LIBRUBBERBAND=yes LIBSNAPPY=yes LIBSPEEX=yes LIBTESSERACT=yes
> LIBTWOLAME=yes LIBVIDSTAB=yes LIBWEBP=yes LIBX264=yes LIBX265=yes
> LIBXVID=yes LIBZMQ=yes LIBZVBI=yes
>
> I encountered the following issues:
>
> 1. var-plugin-sdk is required for rubberband.
> 2. leptonica is required for tesseract (I think).
> 3. ffmpeg4 seems to be looking for opencv, while the script above installs
> opencv4:
>
> ffmpeg-4.1/tests/checkasm/jpeg2000dsp.c
> ffmpeg-4.1/tests/checkasm/synth_filter.c
> ffmpeg-4.1/tests/checkasm/vf_nlmeans.c
> ffmpeg-4.1/tests/tiny_psnr.c
> ffmpeg-4.1/COPYING.LGPLv2.1
> ffmpeg-4.1/README.md
> ffmpeg-4.1/CONTRIBUTING.md
> ERROR: opencv not found using pkg-config
>
> # pkg-config --list-all|grep opencv
> opencv4 OpenCV - Open Source Computer Vision
> Library
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] help

[Jheengut Pritvi]

what is the issue here ??
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] ffmpeg4 not building

[Jheengut Pritvi]

Hi Luveh,

I checked ffmpeg, ffmpeg3 builds with opencv-legacy.
The readme of ffmpeg4 does not mention this detail BTW.

The ffmpeg4 of slackware64-current builds without the need of openvc
though.

On Mon, 20 Apr 2020 at 22:13, Luveh Keraph <1.41...@gmail.com> wrote:

> With the provisos mentioned in my previous communication, I was able to
> build ffmpeg4.
>
> On Mon, Apr 20, 2020 at 11:36 AM Luveh Keraph <1.41...@gmail.com> wrote:
>
>> It is building all right, in that it did not choke on opencv as I
>> reported here before. However, I could not get opencv-legacy to build with
>> tesseract already installed. I had to remove tesseract, build and install
>> opencv-legacy, build and install tesseract, and then launch the build of
>> ffmpeg4.  The build job for ffmpeg4 is still ongoing; I'll report on the
>> outcome.
>>
>> On Mon, Apr 20, 2020 at 8:49 AM Jheengut Pritvi 
>> wrote:
>>
>>> Hi,
>>> I have not tried the latest version but can you confirm if the legacy
>>> opencv is needed instead.
>>>
>>>
>>> On Sun, 19 Apr 2020 at 20:15, Luveh Keraph <1.41...@gmail.com> wrote:
>>>
>>>> I am using the following ffmpeg4.sqf file in a freshly installed (and
>>>> up-to-date) 14.2 system:
>>>>
>>>> libass
>>>> chromaprint
>>>> frei0r
>>>> ladspa_sdk
>>>> libaom
>>>> libbluray
>>>> libbs2b
>>>> celt
>>>> libdc1394
>>>> libfdk-aac
>>>> flite
>>>> libgme
>>>> gsm
>>>> libiec61883
>>>> libavc1394
>>>> libilbc
>>>> libmodplug
>>>> lame
>>>> opencore-amr
>>>> opencv
>>>> opus
>>>> rtmpdump
>>>> rubberband
>>>> snappy
>>>> speex
>>>> tesseract
>>>> twolame
>>>> vid.stab
>>>> libwebp
>>>> x264
>>>> x265
>>>> xvidcore
>>>> zeromq
>>>> zvbi
>>>> ffmpeg4 | BINS=yes CHROMAPRINT=yes FREI0R=yes LADSPA=yes LIBAOM=yes
>>>> LIBBLURAY=yes LIBBS2B=yes LIBCELT=yes LIBDC1394=yes LIBFDK_AAC=yes
>>>> LIBFLITE=yes LIBGME=yes LIBGSM=yes LIBIEC61883=yes LIBILBC=yes
>>>> LIBMODPLUG=yes LIBMP3LAME=yes LIBOPENCORE=yes LIBOPENCV=yes LIBOPUS=yes
>>>> LIBRTMP=yes LIBRUBBERBAND=yes LIBSNAPPY=yes LIBSPEEX=yes LIBTESSERACT=yes
>>>> LIBTWOLAME=yes LIBVIDSTAB=yes LIBWEBP=yes LIBX264=yes LIBX265=yes
>>>> LIBXVID=yes LIBZMQ=yes LIBZVBI=yes
>>>>
>>>> I encountered the following issues:
>>>>
>>>> 1. var-plugin-sdk is required for rubberband.
>>>> 2. leptonica is required for tesseract (I think).
>>>> 3. ffmpeg4 seems to be looking for opencv, while the script above
>>>> installs opencv4:
>>>>
>>>> ffmpeg-4.1/tests/checkasm/jpeg2000dsp.c
>>>> ffmpeg-4.1/tests/checkasm/synth_filter.c
>>>> ffmpeg-4.1/tests/checkasm/vf_nlmeans.c
>>>> ffmpeg-4.1/tests/tiny_psnr.c
>>>> ffmpeg-4.1/COPYING.LGPLv2.1
>>>> ffmpeg-4.1/README.md
>>>> ffmpeg-4.1/CONTRIBUTING.md
>>>> ERROR: opencv not found using pkg-config
>>>>
>>>> # pkg-config --list-all|grep opencv
>>>> opencv4 OpenCV - Open Source Computer
>>>> Vision Library
>>>> ___
>>>> SlackBuilds-users mailing list
>>>> SlackBuilds-users@slackbuilds.org
>>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>>> FAQ - https://slackbuilds.org/faq/
>>>>
>>>> ___
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users@slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] sbopkg wants to upgrade non-installed package

[Jheengut Pritvi]

Hi Rich,

what does ls /var/log/packages/ | grep docuwiki -i show up?


On Sat, 3 Oct 2020 at 22:12, Rich Shepard  wrote:

> Not long ago I deleted docuwiki since I wasn't using it. Each week when I
> run sbopkg to upgrade to patched packages installed here, it wants to
> upgrade docuwiki, even when I don't check that box. Then it fails when
> attempting to process the file.
>
> Where do I look to find why it's behaving this way?
>
> Rich
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] sqg for teapot

[Jheengut Pritvi]

Hi,

where do you get this info ??

:: Uncomment SKIP_EMPTY to change this.

On Mon, 16 Nov 2020 at 22:50, Jude DaShiell  wrote:

> teapot: empty REQUIRES line. No queuefile generated.
> Uncomment SKIP_EMPTY to change this.
> Done.
>
> Where do I uncomment SKIP_EMPTY?  I want to find out if installing this
> package again gets me a user guide in /usr/share/doc/teapot.
>
>
> --
> United States has 633 Billionaires with only 10 doing any annual
> significant giving.
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] douninst.sh in SBo packages

[Jheengut Pritvi]

you might have given the answer with  nvidia-legacy script. I do not
remember douninst.sh being documented.  Need to check that .

On Wed, 27 Oct 2021 at 19:09, Erich Ritz via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> Hello list,
>
> (This question pertains to -current, not 14.2).
>
> I want to ask about allowable/preferred behavior in doinst.sh and
> douninst.sh.
>
> Motivation:  I maintain a package (system76-io-dkms) that makes use of
> dkms.  This allows new kernel modules to be automatically built for new
> kernel versions without requiring a package rebuild.  Obviously these files
> won't be tracked by pkgtools, but they are tracked by dkms.  The desire
> then is that when removing the package (by removepkg) it calls out to dkms
> to remove all files.
>
> Hurdles in implementation: removepkg removes all package files before
> calling douninst.sh, so any configuration files owned by the package won't
> be available by douninst.sh.  This complicates using dkms.
>
> Solution: Lucky for me another user described a simple solution:
> https://www.linuxquestions.org/questions/slackware-14/how-can-removepkg-be-triggered-to-remove-stuff-placed-by-a-doinst-sh-4175672073/page4.html#post6109767.
> Create a copy of the dkms configuration file in doinst.sh.  This will
> create a file that is not tracked by pkgtools.  Now in douninst.sh use that
> file to call out to dkms to remove the remaining modules that may have been
> automatically built, and finally remove that file.  The end result is that
> after calling removepkg no more files remain on the filesystem from the
> package.
>
> Here is the patch to system76-io-dkms that implements this behavior:
> https://gitlab.com/ErichRitz/slackbuilds/-/commit/9c48fe02ac32c382fdac871373054865642440f0
>
> Question: is this behavior acceptable for SBo?  I would assume so, but so
> far there is only 1 other package that makes use of douninst.sh
> (nvidia-legacy390-driver), so I thought it best to ask first.
>
> Erich
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] sbopkg -c note

[Jheengut Pritvi]

My /tmp is a tmpfs

On Fri, 22 Oct 2021 at 05:20, Jeremy Hansen 
wrote:

>
>
> On Thu, Oct 21, 2021, 6:33 PM Duncan Roe 
> wrote:
>
>> On Thu, Oct 21, 2021 at 10:42:04AM -0600, Jeremy Hansen wrote:
>> > On Thu, Oct 21, 2021, 3:45 AM Jude DaShiell  wrote:
>> >
>> > > Note: repo version not obtainable by standard method, may be
>> inaccurate.
>> > > Can this be cleared by now or should it be cleared later by
>> configuration?
>> > > One thing I have noticed about slackware and maybe this applies to
>> other
>> > > linux distros is that the /tmp directory tree tends to be rather
>> permanent
>> > > unless cleaned out every so often.  I've had instances where the root
>> user
>> > > ran out of space on the system and this was with I think the standard
>> 30gb
>> > > root partition install space a while ago.
>> > > I need to go through logs and clean some of those out too so disk
>> quota
>> > > situations don't happen again for a while.
>> > >
>> >
>> > I can't answer about your error, but while sbopkg doesn't clean up the
>> > files in /tmp/ by default, you can change it by setting the following in
>> > /etc/sbopkg/sbopkg.conf
>> >
>> > CLEANUP=${CLEANUP:-NO}
>> >
>> > to
>> >
>> > CLEANUP=YES
>> >
>> > Jeremy
>>
>> I think you are meant to:
>>
>> export CLEANUP=YES
>>
>> before running (un-amended) sbopkg
>>
>> Cheers ... Duncan.
>>
>
> If you want this to stick, you'd need to add the export to your ~/.profile
> or change the config file I mentioned earlier.
>
> Exporting it will only save it for that instance of bash (and any bash
> sessions spawned from this one) and won't stick to any other sessions
> already running.
>
> Jeremy
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Please remove TexText-0.4.4 from the Slackware-15.0 repository.

[Jheengut Pritvi]

Hi,

did you mean this version
https://github.com/textext/textext/releases/tag/1.8.1 ??

On Sun, 13 Mar 2022 at 09:01, Ananda Murthy  wrote:

> Yes. It works perfectly.
>
> On Sat, Mar 12, 2022 at 11:02 PM Franzen via SlackBuilds-users <
> slackbuilds-users@slackbuilds.org> wrote:
>
>> On 2022-03-12 18:11, Ananda Murthy wrote:
>> > Hello,
>> >
>> > This version does not work with Inkscape 1.1.2.
>>
>> Have you tried you tried a newer version from here
>> https://github.com/textext/textext ?
>>
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>
> --
>
>
> Close Windows ! Open source !!
> Free software from proprietary mafia !!!
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Creating First Slackbuilds and Github

[Jheengut Pritvi]

Hi Brandon,

You should consult this page first https://slackbuilds.org/guidelines/.

If you have trouble , you can continue on this thread.

Enjoy a good day


Pritvi Jheengut

On Sat, 19 Mar 2022 at 09:08, Brandon Pribula  wrote:

> Hi,
>
> I'm new to creating SlackBuilds and using github so I apologize if this is
> obvious.
>
> I'm in the process of putting my first SlackBuilds together. The repos are
> on github. The first repo has archived releases but I would like to use
> master up to the most recent commit.
> And the second repo only has a master and no archived releases.
>
> I'm curious what the policy is regarding slackbuilds.org hosting tarballs?
>
> Thanks
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Slackware 15.0 Released

[Jheengut Pritvi]

I don't think so.



On Fri, 4 Feb 2022 at 19:36, Franzen via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> > So what about SBo 15.0 repo?
> > Well, we are still working on it at this moment and YOU can help us
> > making it faster to get released by testing scripts in our repository
> > against latest 15.0 installation (full installation is always
> > recommended).
>
> Is there a list of "not-testet-yet" or "known-as-failed/needing-a-fix"
> scripts?
> Otherwise it's very random/inefficient what the community can do to help
> out.
>
> Johannes
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Update Apache Tomcat for new version 22

[Jheengut Pritvi]

Hi,

Apache Tomcat has been updated to version 10.0.22.

Please accept the diff ==>


root:/var/lib/sbopkg/SBo/15.0/system/apache-tomcat# diff apache-tomcat.info
apache-tomcat.info.sbopkg
2c2
< VERSION="10.0.20"
---
> VERSION="10.0.22"
4,5c4,5
< DOWNLOAD="
https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.20/bin/apache-tomcat-10.0.20.tar.gz;

< MD5SUM="cc94dae513e06c3f9dae191a73cdd558"
---
> DOWNLOAD="
https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.22/bin/apache-tomcat-10.0.22.tar.gz;

> MD5SUM="e01967a23bd19fa1cc314215edfbe92d"

root:/var/lib/sbopkg/SBo/15.0/system/apache-tomcat# diff
apache-tomcat.SlackBuild  apache-tomcat.SlackBuild.sbopkg
29c29
< VERSION=${VERSION:-10.0.20}
---
> VERSION=${VERSION:-10.0.22}



Best regards
Pritvi Jheengut
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Please your support

[Jheengut Pritvi]

Just make his projects your star

On Mon, 18 Apr 2022, 07:59 Klaatu,  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=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@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Update Apache Tomcat for new version 22

[Jheengut Pritvi]

Hi,

It's been a while since I have not heard from the maintainer and Tomcat has
bumped to a new version by now.

Please advise.

Pritvi

On Mon, 18 Jul 2022, 15:54 Dave Woodfall,  wrote:

> On 18/07/22 15:45,
> Jheengut Pritvi  put forth the proposition:
> > Hi Dave,
> >
> > I was never before requested to send patches as such and I sent the email
> > to the maintainer and CC to slackbuilds. By experience, if the maintainer
> > is  not free or could not have time to update, someone in the admins
> would
> > patch it themselves.
>
> We do accept patches if you don't hear back from the maintainer
> within a reasonable time.  It's usually best to wait a few days to
> give them chance to reply.
>
> Or if you know that the maintainer hasn't been active for a very long
> time then that's OK too.
>
> > Thanks
> > Pritvi
> >
> > On Mon, 18 Jul 2022 at 15:25, Dave Woodfall 
> wrote:
> >
> > > On 18/07/22 12:21,
> > > Dave Woodfall  put forth the proposition:
> > > > On 18/07/22 15:01,
> > > > Jheengut Pritvi  put forth the proposition:
> > > > > Hi,
> > > > >
> > > > > Apache Tomcat has been updated to version 10.0.22.
> > > > >
> > > > > Please accept the diff ==>
> > > > >
> > > > >
> > > > > root:/var/lib/sbopkg/SBo/15.0/system/apache-tomcat# diff
> > > apache-tomcat.info
> > > > > apache-tomcat.info.sbopkg
> > > > > 2c2
> > > > > < VERSION="10.0.20"
> > > > > ---
> > > > > > VERSION="10.0.22"
> > > > > 4,5c4,5
> > > > > < DOWNLOAD="
> > > > >
> > >
> https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.20/bin/apache-tomcat-10.0.20.tar.gz
> > > "
> > > > >
> > > > > < MD5SUM="cc94dae513e06c3f9dae191a73cdd558"
> > > > > ---
> > > > > > DOWNLOAD="
> > > > >
> > >
> https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.22/bin/apache-tomcat-10.0.22.tar.gz
> > > "
> > > > >
> > > > > > MD5SUM="e01967a23bd19fa1cc314215edfbe92d"
> > > > >
> > > > > root:/var/lib/sbopkg/SBo/15.0/system/apache-tomcat# diff
> > > > > apache-tomcat.SlackBuild  apache-tomcat.SlackBuild.sbopkg
> > > > > 29c29
> > > > > < VERSION=${VERSION:-10.0.20}
> > > > > ---
> > > > > > VERSION=${VERSION:-10.0.22}
> > > > >
> > > > >
> > > > >
> > > > > Best regards
> > > > > Pritvi Jheengut
> > > >
> > > > Can you please add patches as attachments?
> > > >
> > > > Quick way without git - `a' is the old slackbuild directory, `b' is
> > > > the updated slackbuild directory:
> > > >
> > > >  LC_ALL=C TZ=UTC0 diff -Naur a b > whatever-update.patch
> > > >
> > > > Then attach the patch here.
> > > >
> > > > Thanks.
> > > >
> > > > It's easier for us than copy/pasting from emails.
> > > >
> > > > Willy has a HOWTO on making git patches on his blog.
> > > >
> > >
> > > You aren't the maintainer.  If you haven't yet, please first contact
> > > the maintainer to ask about updating it.
> > >
> > > Thanks
> > >
> > > --
> > > Dave
> > >
> > > sbo-maintainer-tools:
> > > https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
> > > SBo templates:
> > > https://slackbuilds.org/templates/
> > > How to format github downloads:
> > > https://slackbuilds.org/GITHUB_URLs.txt
> > >
> > >
>
> > 2c2
> > < VERSION="10.0.20"
> > ---
> > > VERSION="10.0.22"
> > 4,5c4,5
> > < DOWNLOAD="
> https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.20/bin/apache-tomcat-10.0.20.tar.gz
> "
> > < MD5SUM="cc94dae513e06c3f9dae191a73cdd558"
> > ---
> > > DOWNLOAD="
> https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.22/bin/apache-tomcat-10.0.22.tar.gz
> "
> > > MD5SUM="e01967a23bd19fa1cc314215edfbe92d"
>
> > 29c29
> > < VERSION=${VERSION:-10.0.20}
> > ---
> > > VERSION=${VERSION:-10.0.22}
>
> --
> Dave
>
> sbo-maintainer-tools:
> https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
> SBo templates:
> https://slackbuilds.org/templates/
> How to format github downloads:
> https://slackbuilds.org/GITHUB_URLs.txt
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] RFC updates for gdal slackbuild

[Jheengut Pritvi]

Hi,

Is that why some programs gave this problem ??
error while loading shared libraries: libgdal.so.31:


On Sun, 3 Dec 2023 at 00:38, Greg Tourte  wrote:

> Hi,
>
> I have been looking at the gdal slackbuild for version 3.8. I have held
> off for now as it had an issue with building when an older version was
> installed. Since I reported the issue upstream and a patch has since then
> been written, I can now work on it.
>
> The new release is rather trivial although it bumps the shared library
> version. However, the current script doesn't really specify most
> dependencies and basically relies on what is already installed on the
> system. Most other distro packages will build gdal with enforced
> dependencies and I am very tempted to change the script to do so as well
> (especially now that the circular libspatialite  dependency is no longer an
> issue).
>
> What do people think. Do any one have any objections?
>
> Cheers
>
> Greg
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] tracking down SBo "dependencies"

[Jheengut Pritvi]

sqg -p dav1d

On Thu, 29 Feb 2024 at 20:12, Jim  wrote:

> I recently upgraded the SBo dav1d, which upgraded the library from
> libdav1d.so.6 to libdav1d.so.7.
>
> Unfortunately, a couple of other SBo packages (libheif and vlc) had
> references to (specifically) libdav1d.so.6, which caused them to whine a
> bit.
>
> It was easy enough to recompile libheif and vlc after I found the problem,
> but this got me wondering...
>
> Does anyone have an easy way of tracking down this sort of "breakage" which
> might happen when upgrading an SBo package?
>
> Thanks.
> Jim
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/