From x80 at telus.net  Thu Mar  1 00:08:39 2018
From: x80 at telus.net (x80)
Date: Wed, 28 Feb 2018 16:08:39 -0800
Subject: [Slackbuilds-users] Lilypond compile failure
In-Reply-To: <7fd5067e-adac-2d81-05bd-d6d5f68656bb@telus.net>
References: <7fd5067e-adac-2d81-05bd-d6d5f68656bb@telus.net>
Message-ID: <621dffa8-6c97-29cd-a564-a2f10be01c4f@telus.net>

That's great! I'm looking forward to reading it, thanks!


On 02/28/2018 03:38 PM, Klaatu wrote:
> Funny you mention that. I have it on good authority that a tutorial 
> article on Rosegarden is going to be published on opensource.com soon. 
> I also happen to know that the author of the article writes his 
> tutorials on Slackware with packages from SBo. I'll try to remember to 
> post a link when it is released.
>
> On 1 March 2018 9:57:13 AM NZDT, x80 <x80 at telus.net> wrote:
>
>
>     On 02/22/2018 03:41 PM, Klaatu wrote:
>
>         Is anyone else having trouble building lilypond? I get failure
>         during ./configure, hinting that i need a more robust Tex
>         stack. checking for epsf.tex... ./configure: line 13764:
>         kpsewhich: command not found not found checking for Cyrillic
>         characters support in TeX... ./configure: line 13777:
>         kpsewhich: command not found not found I am *not* attempting
>         to build its docs, which the SlackBuild's README specifically
>         says cannot be done without installing texi2html. The project
>         docs mention some dependencies that don't appear in the
>         SlackBuild .info file, so that might be part of the problem,
>         but the error I'm getting doesn't really seem to correlate to
>         Metafont or Metapost (two things listed in the project docs
>         but not the SlackBuild docs). Anybody try this lately?
>
>
>
>     No problems on a fresh 64-14.2 fully updated.
>
>     Jack is giving me problems tho - I get no sound in rosegarden, and
>     apparently I need to install a synth. I haven't a clue, I've never got
>     rosegarden to compile before and I don't know how to set it up.
>     Time to rtfm I guess.
>     ------------------------------------------------------------------------
>
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org
>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     FAQ -https://slackbuilds.org/faq/
>
> -- Klaatu
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180228/a27ac265/attachment-0001.html>

From Jim.Diamond at acadiau.ca  Thu Mar  1 00:57:49 2018
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Wed, 28 Feb 2018 20:57:49 -0400
Subject: [Slackbuilds-users] runc build error
In-Reply-To: <20180228202835.6179d4f8@fiete.bug.net>
References: <20180228184452.GA10582@tux3.acadiau.ca>
 <20180228202835.6179d4f8@fiete.bug.net>
Message-ID: <20180301005749.GE17822@jdiamond-mb.acadiau.ca>

On Wed, Feb 28, 2018 at 20:28 (+0100), rundstutzen at gmx.de wrote:

> did you make sure you installed (and use) the google-go-lang slackbuild?

I have it installed.

> the go compiler that comes with slackware (gcc-go) is not sufficient.
> "go version" will tell you if you use the right compiler.

I have /usr/bin in my PATH before /usr/lib64/go1.9.2/go/bin and
didn't realize that was the issue.

With a changed PATH all is good.

Thanks for the help.

                                Jim

From willysr at slackbuilds.org  Thu Mar  1 01:04:24 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 1 Mar 2018 08:04:24 +0700
Subject: [Slackbuilds-users] Retroshare do not work Slackware.
In-Reply-To: <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
References: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
 <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
Message-ID: <995dd75d-936d-efaa-53f8-e1e7a05b5fff@slackbuilds.org>

>> I opened a post in linuxquestions.org slackware forum, about "Retroshare
>> 6.0.3" slackbuild.
>>
>> https://www.linuxquestions.org/questions/showthread.php?p=5825342#post5825342
>>
>> Ponce suspect an issue with the newer " libupnp ".
> 
> I'll try to clarify a little: retroshare.SlackBuild lacks a "set -e"
> line so a package is created also if build breaks and this might have
> lead into the belief that compiling had been succesful.
> 
> the error is this:
> 
> g++ -c -pipe -Wno-deprecated -Wno-deprecated-declarations -Wno-cpp
> -std=c++0x -Wall -D_FILE_OFFSET_BITS=64 -O2 -pthread -fPIC -Wall -W
> -DRS_ENABLE_GXS -DENABLE_WEBUI -DRS_NO_WARN_DEPRECATED
> -DRS_NO_WARN_CPP -DRS_GXS_TRANS -DRS_USE_BITDHT -DPATCHED_LIBUPNP
> -DPLUGIN_DIR="\"/usr/lib64/retroshare/extensions6\""
> -DDATA_DIR="\"/usr/share/retroshare\"" -DRS_USE_LIBUPNP
> -DSQLITE_HAS_CODEC -DGXS_ENABLE_SYNC_MSGS
> -I/usr/lib64/qt/mkspecs/linux-g++ -I. -I. -I../../libbitdht/src
> -I../../openpgpsdk/src -I/usr/include/upnp -o
> temp/linux-g++/obj/rsinit.o rsserver/rsinit.cc
> In file included from ./upnp/UPnPBase.h:35:0,
>                  from ./upnp/upnphandler_linux.h:13,
>                  from rsserver/rsinit.cc:805:
> /usr/include/upnp/upnpdebug.h:40:24: fatal error: ThreadPool.h: No
> such file or directory
> compilation terminated.
> Makefile.libretroshare:5411: recipe for target
> 'temp/linux-g++/obj/rsinit.o' failed
> make[1]: *** [temp/linux-g++/obj/rsinit.o] Error 1
> make[1]: Leaving directory '/tmp/SBo/RetroShare-0.6.3/libretroshare/src'
> Makefile:90: recipe for target
> 'sub-libretroshare-src-libretroshare-pro-make_default' failed
> make: *** [sub-libretroshare-src-libretroshare-pro-make_default] Error 2

Matteo is right
ThreadPool is still being worked on 1.8.x releases and this release
(1.8.x) is API-incompatible with 1.6.x.

I would suggest to revert back to 1.6.x for now. Upstream stated that
both branch will continue to be maintained and until we got all packages
ready for 1.8, we can still use 1.6.x and avoiding more breakage.

Ozan, what's your opinion on this?


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180301/86a8186a/attachment.asc>

From rundstutzen at gmx.de  Thu Mar  1 09:19:44 2018
From: rundstutzen at gmx.de (rundstutzen at gmx.de)
Date: Thu, 1 Mar 2018 10:19:44 +0100
Subject: [Slackbuilds-users] sbog ping: invalid download urls in .info files
Message-ID: <20180301101944.06b70fab@fiete.example.net>

dear slackbuild maintainers,

i am about to release version 0.3 of my slackbuild command line tool
sbog (hosted here: https://bitbucket.org/trueslack/sbog,
linuxquestions.org thread here:
https://www.linuxquestions.org/questions/slackware-14/%5Bann%5D-sbog-sbopkg-c-on-steroids-4175623847/)

the new command "sbog ping" tests the download links of all .info files
found in a given directory tree and prints a list with errors.

i tested all packages in the slackbuild.org "current" branch. you find
the result here: https://pastebin.com/pbFdSAyW

the list contains 3 columns, separated by tab:
package name, email address of the maintainer, error message including
the url

i obfuscated the email addresses, replacing '@' with '###'.

"sbog ping" found 252 issues. note that some of them are
false positives.

for some error messages it's clear that there is a problem, ruling out
a false positive:
- http 404/ftp 550 code (file not found): these download files are
  gone (there are 134 dead links).
- http 401 (unauthorized): some links now need an authentifikation.
- "no such host": the host is gone.
- "403 SSL is required": this is easy to fix, change the protocol scheme
  to https.

probably false positives:
- timeout messages: especially sourceforge.net is a big problem and i
  tried to resolve this issue without luck. i gave up on this. i don't
  trust sf.net anyway.
- "x509: certificate signed by unknown authority": the link is probably
ok, but the certificate is not authorized.

there are more errors, like internal server errors and the like. 

to understand the cause of some errors one has to know
how "sbog ping" works. for http urls a http "HEAD" request is send to
test if the url is valid. this can cause trouble, as some servers are
picky about the request method ("GET" vs. "HEAD"). spog will follow
redirections, which can cause confusing error messages. use "curl -vLI
<url>" to learn went wrong.
for ftp addresses sbog will connect to the ftp server, login as
"anonymous" and ask for the filesize. if this fails we know something
is wrong.

to find out if one of your slackbuilds is affected just search for your
email address in that list (email address is obfuscated, read above).

maybe you find this list useful. when sbog 0.3 is released (in a few
days) you can use this tool yourself.

keep up the good work!

regards,

heiko

From kjhambrick at gmail.com  Thu Mar  1 13:34:27 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Thu, 1 Mar 2018 07:34:27 -0600
Subject: [Slackbuilds-users] Postgresql Version 10.3 is available.
Message-ID: <CANBHt+OF-m9jRHBKMaZBqC8TDE3P22bO6YELFF=FX4s-c7JZ2w@mail.gmail.com>

Adis --

There is an update for postgresql to version 10.3 this morning.

The update builds and runs fine on Slackware64 14.2 + Multilib.

All I had to change in the postgresql.SlackBuild was:

   VERSION=${VERSION:-10.3}

And for consistency, I updated the postgresql.info file as follows:

   DOWNLOAD="https://ftp.postgresql.org/pub/source/v10.
3/postgresql-10.3.tar.bz2"
   MD5SUM="506498796a314c549388cafb3d5c717a"

The MD5SUM Value came directly from the published
~/source/v10.3/postgresql-10.3.tar.bz2.md5 file

Version 10.3 addresses CVE-2018-1058: Uncontrolled search path element in
pg_dump and other client
applications

Please visit https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:
_Protect_Your_Search_Path
for a full explanation of the CVE-2018-1058.

Thanks for the postgresql.SlackBuild Adis !

-- kjh

Note that the same CVE is addressed in postgresql version 9.6.8 which I
still run on my Production Box.

It also builds, installs and runs fine 'over there'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180301/213189ac/attachment.html>

From kjhambrick at gmail.com  Thu Mar  1 13:38:17 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Thu, 1 Mar 2018 07:38:17 -0600
Subject: [Slackbuilds-users] Postgresql Version 10.3 is available.
In-Reply-To: <CANBHt+OF-m9jRHBKMaZBqC8TDE3P22bO6YELFF=FX4s-c7JZ2w@mail.gmail.com>
References: <CANBHt+OF-m9jRHBKMaZBqC8TDE3P22bO6YELFF=FX4s-c7JZ2w@mail.gmail.com>
Message-ID: <CANBHt+NeYyjj0dGJa9HX1ZB=BttB+KQA6poFVf-_EQojEkTRtA@mail.gmail.com>

Adis --

I said:  And for consistency, I updated the postgresql.info file as follows:

I meant:  And for consistency, I updated MY COPY OF the postgresql.info
file as follows:

I did not mean to imply that I somehow modified your official
postgresql.info file :)

-- kjh

On Thu, Mar 1, 2018 at 7:34 AM, Konrad J Hambrick <kjhambrick at gmail.com>
wrote:

> Adis --
>
> There is an update for postgresql to version 10.3 this morning.
>
> The update builds and runs fine on Slackware64 14.2 + Multilib.
>
> All I had to change in the postgresql.SlackBuild was:
>
>    VERSION=${VERSION:-10.3}
>
> And for consistency, I updated the postgresql.info file as follows:
>
>    DOWNLOAD="https://ftp.postgresql.org/pub/source/v10.3/
> postgresql-10.3.tar.bz2"
>    MD5SUM="506498796a314c549388cafb3d5c717a"
>
> The MD5SUM Value came directly from the published
> ~/source/v10.3/postgresql-10.3.tar.bz2.md5 file
>
> Version 10.3 addresses CVE-2018-1058: Uncontrolled search path element in
> pg_dump and other client
> applications
>
> Please visit https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_
> Protect_Your_Search_Path
> for a full explanation of the CVE-2018-1058.
>
> Thanks for the postgresql.SlackBuild Adis !
>
> -- kjh
>
> Note that the same CVE is addressed in postgresql version 9.6.8 which I
> still run on my Production Box.
>
> It also builds, installs and runs fine 'over there'
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180301/5097e604/attachment-0001.html>

From adis at linux.org.ba  Thu Mar  1 14:34:50 2018
From: adis at linux.org.ba (Adis Nezirovic)
Date: Thu, 1 Mar 2018 15:34:50 +0100
Subject: [Slackbuilds-users] Postgresql Version 10.3 is available.
In-Reply-To: <CANBHt+NeYyjj0dGJa9HX1ZB=BttB+KQA6poFVf-_EQojEkTRtA@mail.gmail.com>
References: <CANBHt+OF-m9jRHBKMaZBqC8TDE3P22bO6YELFF=FX4s-c7JZ2w@mail.gmail.com>
 <CANBHt+NeYyjj0dGJa9HX1ZB=BttB+KQA6poFVf-_EQojEkTRtA@mail.gmail.com>
Message-ID: <CALHPnviaewF_8T3sA8yhRucMwmfy+gCknn2zn5=LdAA=5Lyyqg@mail.gmail.com>

Hello,

Thanks for heads up, I'll look into releasing new version next week (I
always prefer to wait a little, even for minor releases, to avoid
nasty suprises).

As for public schema security problems, that was known for a long
time, info was/is in the official docs, e.g.
https://www.postgresql.org/docs/7.3/static/ddl-schemas.html
So if someone was keen to exploit that, he could start doing that long
long time ago :-D

Best regards,
Adis


On Thu, Mar 1, 2018 at 2:38 PM, Konrad J Hambrick <kjhambrick at gmail.com> wrote:
> Adis --
>
> I said:  And for consistency, I updated the postgresql.info file as follows:
>
> I meant:  And for consistency, I updated MY COPY OF the postgresql.info file
> as follows:
>
> I did not mean to imply that I somehow modified your official
> postgresql.info file :)
>
> -- kjh
>
> On Thu, Mar 1, 2018 at 7:34 AM, Konrad J Hambrick <kjhambrick at gmail.com>
> wrote:
>>
>> Adis --
>>
>> There is an update for postgresql to version 10.3 this morning.
>>
>> The update builds and runs fine on Slackware64 14.2 + Multilib.
>>
>> All I had to change in the postgresql.SlackBuild was:
>>
>>    VERSION=${VERSION:-10.3}
>>
>> And for consistency, I updated the postgresql.info file as follows:
>>
>>
>> DOWNLOAD="https://ftp.postgresql.org/pub/source/v10.3/postgresql-10.3.tar.bz2"
>>    MD5SUM="506498796a314c549388cafb3d5c717a"
>>
>> The MD5SUM Value came directly from the published
>> ~/source/v10.3/postgresql-10.3.tar.bz2.md5 file
>>
>> Version 10.3 addresses CVE-2018-1058: Uncontrolled search path element in
>> pg_dump and other client
>> applications
>>
>> Please visit
>> https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path
>> for a full explanation of the CVE-2018-1058.
>>
>> Thanks for the postgresql.SlackBuild Adis !
>>
>> -- kjh
>>
>> Note that the same CVE is addressed in postgresql version 9.6.8 which I
>> still run on my Production Box.
>>
>> It also builds, installs and runs fine 'over there'
>>
>

From yalhcru at gmail.com  Thu Mar  1 19:21:12 2018
From: yalhcru at gmail.com (B Watson)
Date: Thu, 1 Mar 2018 14:21:12 -0500
Subject: [Slackbuilds-users] sbog ping: invalid download urls in .info
 files
In-Reply-To: <20180301101944.06b70fab@fiete.example.net>
References: <20180301101944.06b70fab@fiete.example.net>
Message-ID: <CAN1hMuAfRrkATAHAywjOZ-szpE++Xv5W+1e1Ey8vGmch5sDLUQ@mail.gmail.com>

On 3/1/18, rundstutzen at gmx.de <rundstutzen at gmx.de> wrote:
>
> to understand the cause of some errors one has to know
> how "sbog ping" works. for http urls a http "HEAD" request is send to
> test if the url is valid. this can cause trouble, as some servers are
> picky about the request method ("GET" vs. "HEAD").

I ran into this when working on sbosrcarch. Not only do some servers
not allow HEAD, there are also some that allow it but don't report the
same info as GET (missing Content-length header, usually). The way I
work around it is to do an actual GET request, but close the connection
after the headers are received (before the content).

sbosrcarch calls the curl command line tool, so it does this:

curl --head -X GET $url

sbog is written in a compiled language, presumably doesn't call external
commands like this, but you can do the same thing. Send a GET request,
read the headers until you get a blank line, then close the connection.

From kingbeowulf at gmail.com  Fri Mar  2 02:54:51 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 1 Mar 2018 18:54:51 -0800
Subject: [Slackbuilds-users] RFC: patch for cfitsio for some astronomy
 software
Message-ID: <aafdbc0a-44b5-ce8f-457c-6ceed5aacee4@gmail.com>

hello

As discussed here at LQ,
https://www.linuxquestions.org/questions/slackware-14/indi-library-on-slackware-compilation-help-before-i-nag-upstream-on-github-4175624539/#post5824749

I recommend applying the Fedora patch to cfitsio to fix underlinking to
bzip2 for some astronomy software. This effects libindi that I plan to
submit to SBo, and perhaps others. That way, we can avoid adding extra
LDFLAGS, or be befuddled by phantom dependencies.  Patches to cfistio
source and SlackBuild are attached.

Thanks to ponce and 55020 on LQ for pointing me in the right direction.

cc: cftsio maintainer.

-Ed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cfitsio-zlib.patch
Type: text/x-patch
Size: 2813 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180301/de4365e8/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cfitsio.SB.patch
Type: text/x-patch
Size: 697 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180301/de4365e8/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180301/de4365e8/attachment.asc>

From s.arcus at open-t.co.uk  Fri Mar  2 11:19:59 2018
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Fri, 2 Mar 2018 11:19:59 +0000
Subject: [Slackbuilds-users] A little helps with packaging C software which
 doesn't use make or autotools?
Message-ID: <bdc0fb34-8e68-c6e4-d546-ba222cf539c7@open-t.co.uk>

I am trying to package usbrelay (https://github.com/darrylb123/usbrelay) 
for SBo - a very useful little utility to control cheap USB relays. The 
instructions at the page above only include the following step:

# gcc -o usbrelay usbrelay.c -lhidapi-libusb

which works fine.

I'm not sure what or where to include in usbrelay.SlackBuild. Would the 
above go instead of the whole lot below?:

# Your application will probably need different configure flags;
# these are provided as an example only.
# Be sure to build only shared libraries unless there's some need for
# static.
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
   --prefix=/usr \
   --libdir=/usr/lib${LIBDIRSUFFIX} \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --mandir=/usr/man \
   --docdir=/usr/doc/$PRGNAM-$VERSION \
   --build=$ARCH-slackware-linux

# Compile the application and install it into the $PKG directory
make
make install DESTDIR=$PKG



How do we replicate the "make install DESTDIR=$PKG" step?

From willysr at slackbuilds.org  Fri Mar  2 12:00:22 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 2 Mar 2018 19:00:22 +0700
Subject: [Slackbuilds-users] A little helps with packaging C software
 which doesn't use make or autotools?
In-Reply-To: <bdc0fb34-8e68-c6e4-d546-ba222cf539c7@open-t.co.uk>
References: <bdc0fb34-8e68-c6e4-d546-ba222cf539c7@open-t.co.uk>
Message-ID: <59333faa-97c0-888d-d739-ff2331e37df2@slackbuilds.org>

> I am trying to package usbrelay (https://github.com/darrylb123/usbrelay)
> for SBo - a very useful little utility to control cheap USB relays. The
> instructions at the page above only include the following step:
> 
> # gcc -o usbrelay usbrelay.c -lhidapi-libusb
> 
> which works fine.
> 
> I'm not sure what or where to include in usbrelay.SlackBuild. Would the
> above go instead of the whole lot below?:
> 
> # Your application will probably need different configure flags;
> # these are provided as an example only.
> # Be sure to build only shared libraries unless there's some need for
> # static.
> CFLAGS="$SLKCFLAGS" \
> CXXFLAGS="$SLKCFLAGS" \
> ./configure \
> ? --prefix=/usr \
> ? --libdir=/usr/lib${LIBDIRSUFFIX} \
> ? --sysconfdir=/etc \
> ? --localstatedir=/var \
> ? --mandir=/usr/man \
> ? --docdir=/usr/doc/$PRGNAM-$VERSION \
> ? --build=$ARCH-slackware-linux
> 
> # Compile the application and install it into the $PKG directory
> make
> make install DESTDIR=$PKG
> 
> 
> 
> How do we replicate the "make install DESTDIR=$PKG" step?

There's a Makefile, so you can use

CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
make usbrelay
make install DESTDIR=$PKG


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180302/e16c39b0/attachment.asc>

From s.arcus at open-t.co.uk  Fri Mar  2 12:51:53 2018
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Fri, 2 Mar 2018 12:51:53 +0000
Subject: [Slackbuilds-users] A little helps with packaging C software
 which doesn't use make or autotools?
In-Reply-To: <59333faa-97c0-888d-d739-ff2331e37df2@slackbuilds.org>
References: <bdc0fb34-8e68-c6e4-d546-ba222cf539c7@open-t.co.uk>
 <59333faa-97c0-888d-d739-ff2331e37df2@slackbuilds.org>
Message-ID: <d83efa13-fead-5043-f983-77ab9e8da1fd@open-t.co.uk>


On 02/03/18 12:00, Willy Sudiarto Raharjo wrote:
>> I am trying to package usbrelay (https://github.com/darrylb123/usbrelay)
>> for SBo - a very useful little utility to control cheap USB relays. The
>> instructions at the page above only include the following step:
>>
>> # gcc -o usbrelay usbrelay.c -lhidapi-libusb
>>
>> which works fine.
>>
>> I'm not sure what or where to include in usbrelay.SlackBuild. Would the
>> above go instead of the whole lot below?:
>>
>> # Your application will probably need different configure flags;
>> # these are provided as an example only.
>> # Be sure to build only shared libraries unless there's some need for
>> # static.
>> CFLAGS="$SLKCFLAGS" \
>> CXXFLAGS="$SLKCFLAGS" \
>> ./configure \
>>  ? --prefix=/usr \
>>  ? --libdir=/usr/lib${LIBDIRSUFFIX} \
>>  ? --sysconfdir=/etc \
>>  ? --localstatedir=/var \
>>  ? --mandir=/usr/man \
>>  ? --docdir=/usr/doc/$PRGNAM-$VERSION \
>>  ? --build=$ARCH-slackware-linux
>>
>> # Compile the application and install it into the $PKG directory
>> make
>> make install DESTDIR=$PKG
>>
>>
>>
>> How do we replicate the "make install DESTDIR=$PKG" step?
> 
> There's a Makefile, so you can use
> 
> CFLAGS="$SLKCFLAGS" \
> CXXFLAGS="$SLKCFLAGS" \
> make usbrelay
> make install DESTDIR=$PKG

Thank you - that's brilliant!

From rundstutzen at gmx.de  Fri Mar  2 16:46:35 2018
From: rundstutzen at gmx.de (rundstutzen at gmx.de)
Date: Fri, 2 Mar 2018 17:46:35 +0100
Subject: [Slackbuilds-users] sbog ping: invalid download urls in .info
 files
In-Reply-To: <CAN1hMuAfRrkATAHAywjOZ-szpE++Xv5W+1e1Ey8vGmch5sDLUQ@mail.gmail.com>
References: <20180301101944.06b70fab@fiete.example.net>
 <CAN1hMuAfRrkATAHAywjOZ-szpE++Xv5W+1e1Ey8vGmch5sDLUQ@mail.gmail.com>
Message-ID: <20180302174635.7d32c051@fiete.bug.net>

i didn't even know that sbosrcarch does exist (even though i have seen
slackware.uk before). so the functionality i programmed does already
exist. i can't find the sources of your ping script, though.

On Thu, 1 Mar 2018 14:21:12 -0500
B Watson <yalhcru at gmail.com> wrote:

> On 3/1/18, rundstutzen at gmx.de <rundstutzen at gmx.de> wrote:
> >
> > to understand the cause of some errors one has to know
> > how "sbog ping" works. for http urls a http "HEAD" request is send
> > to test if the url is valid. this can cause trouble, as some
> > servers are picky about the request method ("GET" vs. "HEAD").  
> 
> I ran into this when working on sbosrcarch. Not only do some servers
> not allow HEAD, there are also some that allow it but don't report the
> same info as GET (missing Content-length header, usually). The way I
> work around it is to do an actual GET request, but close the
> connection after the headers are received (before the content).

i hate workarounds with passion. its one of the banes of the software
industry. what i am trying to do is actually what HEAD requests were
made for. 
i had to fiddle but i got it working - most of the times. i had to add
some code for amazons3 servers (you probably know why), this saved me
from using get, so this is the price i'm willing to pay. i am happy
with the result (except the amazons3 code). there are a few servers
that will fail - but alas - these servers are not supported by "sbog
ping". if a server is not able to properly handle a HEAD request (which
is not hard) then this is not the fault of sbog.

> 
> sbosrcarch calls the curl command line tool, so it does this:
> 
> curl --head -X GET $url

if i read the output of "curl -v --head -X GET $url" correctly: the
server will get a GET request, so the server (or proxy) will start
sending the body (before the request is closed/cancelled), causing
traffic overhead. correct me if i'm wrong. i don't want to do that.

there is another reason i am don't want to use GET requests: sbog uses a
client pool, sending request concurrently to servers. this speeds
things up *a lot*. i don't want to send several GET request to a
server simultaneously.

regards,

heiko

From yalhcru at gmail.com  Fri Mar  2 18:49:55 2018
From: yalhcru at gmail.com (B Watson)
Date: Fri, 2 Mar 2018 13:49:55 -0500
Subject: [Slackbuilds-users] sbog ping: invalid download urls in .info
 files
In-Reply-To: <20180302174635.7d32c051@fiete.bug.net>
References: <20180301101944.06b70fab@fiete.example.net>
 <CAN1hMuAfRrkATAHAywjOZ-szpE++Xv5W+1e1Ey8vGmch5sDLUQ@mail.gmail.com>
 <20180302174635.7d32c051@fiete.bug.net>
Message-ID: <CAN1hMuChn5sAgALAvXWdTbfLcf5RjxMX4xAhVrQAP6p3kwzOyQ@mail.gmail.com>

On 3/2/18, rundstutzen at gmx.de <rundstutzen at gmx.de> wrote:
> i didn't even know that sbosrcarch does exist (even though i have seen
> slackware.uk before). so the functionality i programmed does already
> exist.

Not exactly: it's the archive creation/maintenance script that does all
the "fake HEAD" requests. It's looking at the headers to decide whether
the file has changed. If it thinks the file's different, it downloads
a new copy for the archive. There's no "check links, but don't download
files" mode, so it doesn't do what "sbog ping" does.

> i can't find the sources of your ping script, though.

Here: http://urchlay.naptime.net/repos/sbostuff/tree/

...or: git clone git://urchlay.naptime.net/sbostuff.git

It's in perl, and not what I'd call beautiful code, so you might want
to put on your goggles before looking at it :)

> i hate workarounds with passion. its one of the banes of the software
> industry. what i am trying to do is actually what HEAD requests were
> made for.
> ...
> but alas - these servers are not supported by "sbog
> ping". if a server is not able to properly handle a HEAD request (which
> is not hard) then this is not the fault of sbog.

Right. In a perfect world, all web servers would comply with the spec,
and would support HEAD requests. Your approach is valid, but I took
a different approach, since I wanted sbosrcarch to be as complete an
archive as possible. The only things it doesn't have are files hidden
behind a click-through license (like Oracle's jdk download).

You might at least look through your logs and make a list of the servers
that don't do HEAD requests, and add some code that logs "this server
doesn't support HEAD requests", so the user knows it's the server's fault.

> if i read the output of "curl -v --head -X GET $url" correctly: the
> server will get a GET request, so the server (or proxy) will start
> sending the body (before the request is closed/cancelled), causing
> traffic overhead. correct me if i'm wrong. i don't want to do that.

You're right. How much overhead depends on how the server/proxy is
configured, but it seems to be 64K bytes per request usually. I decided
that wasn't a problem, partly because the guy who hosts the archive said
so (I wrote the script, he runs it and lets people download the files
it collects).

> there is another reason i am don't want to use GET requests: sbog uses a
> client pool, sending request concurrently to servers. this speeds
> things up *a lot*. i don't want to send several GET request to a
> server simultaneously.

Make the client pool smart enough to serialize requests to the same
server, and do them in parallel only when they're for different servers?
That seems like it'd be worth doing even with regular HEAD requests like
you use now.

sbosrcarch doesn't do anything in parallel, it's one request after
another. Normally it's run non-interactively (via cron job) so it doesn't
matter if it takes a long time to finish.

From rundstutzen at gmx.de  Fri Mar  2 19:35:20 2018
From: rundstutzen at gmx.de (rundstutzen at gmx.de)
Date: Fri, 2 Mar 2018 20:35:20 +0100
Subject: [Slackbuilds-users] sbog ping: invalid download urls in .info
 files
In-Reply-To: <CAN1hMuChn5sAgALAvXWdTbfLcf5RjxMX4xAhVrQAP6p3kwzOyQ@mail.gmail.com>
References: <20180301101944.06b70fab@fiete.example.net>
 <CAN1hMuAfRrkATAHAywjOZ-szpE++Xv5W+1e1Ey8vGmch5sDLUQ@mail.gmail.com>
 <20180302174635.7d32c051@fiete.bug.net>
 <CAN1hMuChn5sAgALAvXWdTbfLcf5RjxMX4xAhVrQAP6p3kwzOyQ@mail.gmail.com>
Message-ID: <20180302203520.62598811@fiete.bug.net>

On Fri, 2 Mar 2018 13:49:55 -0500
B Watson <yalhcru at gmail.com> wrote:

> On 3/2/18, rundstutzen at gmx.de <rundstutzen at gmx.de> wrote:
> > i didn't even know that sbosrcarch does exist (even though i have
> > seen slackware.uk before). so the functionality i programmed does
> > already exist.  
> 
> ...or: git clone git://urchlay.naptime.net/sbostuff.git
> 
> It's in perl, and not what I'd call beautiful code, so you might want
> to put on your goggles before looking at it :)

thank you, this will be an interesting read. i don't care about code
quality - i care more about knowledge that usually lies within the
code. you know probably more about the sbo stuff than i do.
> 
> You might at least look through your logs and make a list of the
> servers that don't do HEAD requests, and add some code that logs
> "this server doesn't support HEAD requests", so the user knows it's
> the server's fault.
> 

please read my starter post, there is a pastebin link to the output of
"sbog ping". i print all errors to stdout, easy to parse. errors
caused by HEAD request failures are only a few. "forbidden" errors are
about 10 or so. can be easily found with grep.

> 
> You're right. How much overhead depends on how the server/proxy is
> configured, but it seems to be 64K bytes per request usually. I
> decided that wasn't a problem, partly because the guy who hosts the
> archive said so (I wrote the script, he runs it and lets people
> download the files it collects).

there used to be times where starting several downloads simultaneously
from the same server was frowned upon. i don't know if this has changed.

> 
> Make the client pool smart enough to serialize requests to the same
> server, and do them in parallel only when they're for different
> servers? That seems like it'd be worth doing even with regular HEAD
> requests like you use now.

i did a lot of "curl -LIv" testing on download urls - and *many* of them
have redirects. no way to tell the real download server by the
url found in the .info file. but i will find a way. right now i do some
runs, printing a lot of data and collect statistics - so i know what i
am actually dealing with.

saying that, i have no problem sending 5 or 10 HEAD request to the same
server simultaneously. GET is another story. 

From kingbeowulf at gmail.com  Fri Mar  2 23:40:36 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Fri, 2 Mar 2018 15:40:36 -0800
Subject: [Slackbuilds-users] RFC: patch for cfitsio for some astronomy
 software
In-Reply-To: <7f63cb24-a73b-d30c-3a5f-82c3846f41f4@o2.pl>
References: <aafdbc0a-44b5-ce8f-457c-6ceed5aacee4@gmail.com>
 <7f63cb24-a73b-d30c-3a5f-82c3846f41f4@o2.pl>
Message-ID: <2c2edd49-ca5b-f429-4711-5f21a362f124@gmail.com>

On 03/02/2018 01:55 PM, Dominik Drobek wrote:
> W dniu 02.03.2018 o?03:54, King Beowulf pisze:
>> I recommend applying the Fedora patch to cfitsio to fix underlinking to
>> bzip2 for some astronomy software.
> 
> Hi,
> 
> Thanks for notifying me.
> 
> I'd like to clarify one thing. Ed's suggested modification to
> cfitsio.SlackBuild removes most of the bundled zlib sources. I'm not
> sure this step is necessary, as the Fedora patch removes these source
> files from ZLIB_SOURCES variable in Makefile.in. Applying the patch
> seems to be enough to avoid compilation of these files.
> 
> By the way, cfitsio has just been updated to version 3.430. Fedora patch
> still applies, so I can include it in the next update.
> 
> Regards,
> Dominik
> 

I wasn't aware that the patch also removes the bundled zlib. Since zlib
(and bzip2) are part of Slackware, would there be any unintended
consequences? I'm still sorting out libindi and drivers compilation and
so have not yet tested if anything works.

-Ed


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180302/ed39b74e/attachment.asc>

From willysr at slackbuilds.org  Sat Mar  3 02:15:20 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 3 Mar 2018 09:15:20 +0700
Subject: [Slackbuilds-users] Updates - 20180303.1
Message-ID: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>

Hi,

Welcome to first update in March.
This batch consist of a LOT of URL fixes, thanks to several problems
1 SourceForge is in maintenance mode
2 Java.net is closed
3 Many upstream removed older version still being used in our repository
4 Source relocation to new folder or domain

Point 3 and 4 are expected to continue in the future, so we need
maintainer's help to make sure their sources are still valid.

It's all thanks to Heiko for starting the work on this one. We started
to fix them in the past few days until the last minute before this
public update, but we think it's quite important to deliver this update
as well, so we will continue working on fixing this issue in the next batch.

Maintainers, please see https://pastebin.com/pbFdSAyW
If your name came up, please take some time to fix the URLs.
If you can't find alternative link, you can use sbosrcharch
(http://slackware.uk/sbosrcarch/).
Please note that some of those entries have been fixed in this batch,
while others might have false positive alerts

In this batch, we have another big update such as libreoffice 6.0.2 (for
both binary repackaging and source-based compilation), vlc 3.0.1,
postfix 3.3.0, Blender 2.79a, rust 1.24.1, meson 0.44.1, and wireshark
2.4.5. David also push some fixes for building in 32 bit architecture
and some build fixes for -current as well.

Also it's a good idea to take a look on pasture branch again. There we
have more than 100 scripts with no maintainers and some of them probably
have broken links or even broken build as well. We hope someone would
adopt the scripts and update it so it built find on -stable and works
properly. Otherwise, i propose to start picking which one can be removed
from the repository to reduce the number of scripts unmaintained in our
repository. This will also help us during next development cycle.


Sat Mar  3 01:43:43 UTC 2018
academic/Gblocks: Fix download url.
academic/PhyML: Fix download url.
academic/artha: Fix download url.
academic/calc: Fix download url.
academic/ncbi-blast: Updated downloar urls.
academic/pyfits: Update download url.
academic/qtoctave: Update download url.
academic/smath-studio: Fix download urls.
academic/veusz: Updated for version 2.2.
academic/xflr5: Added (analysis tool for airfoils, wings, planes).
accessibility/jpilot: Fix download url.
audio/iripdb: Fix download url.
audio/snd: Update download url.
audio/soxr: Fix download url.
audio/whysynth: Fix download url.
desktop/cmatrix: Fix download url.
desktop/icewm-themes: Fix download url.
desktop/maitreya: Fix download url.
desktop/numix-icon-theme: Fix download url.
desktop/oranchelo-icon-theme: Updated for version 0.7.5.9.
desktop/protozoa-cursor-themes: Fix download urls.
desktop/searchmonkey: Fix download url.
desktop/wmbutton: Update download url.
desktop/xfce4-kbdleds-plugin: Fix download url.
desktop/yad: Updated for version 0.40.0.
development/Arduino: Update download url.
development/Sphinx: Updated for version 1.7.1.
development/alloy: Fix download url.
development/arm-binutils: Updated for version 2.30.
development/arm-gdb: Updated for version 8.1.
development/bas55: Updated for version 1.14.
development/cargo-vendor: Fix building on -current.
development/codeblocks: Fix build on 32 bit.
development/dart: Fix build with ARCH=i686.
development/eclim: Fix building with latest Sphinx version.
development/gcc-d: Updated for gcc version 5.5.0
development/gcclegacy494: Fixed build on -current.
development/glm: Updated for version 0.9.8.5.
development/meson: Updated for version 0.44.1.
development/openjdk6: Update download url.
development/p4: Updated for version 2017.2.1611521.
development/p4d: Updated for version 2017.2.1622831.
development/perf: Updated for version 4.4.118.
development/racer: Fix building on -current.
development/rust: Updated for version 1.24.1.
development/staruml: Update download url.
development/swift: Unsupported on 32 bit.
development/universal-ctags: Updated for version 059ed2c
development/zile: Updated for version 2.4.14.
games/OpenXcom: Updated for version 20180217_1352.
games/ioquake3: Fix build on 32 bit.
games/iortcw: Fix build on 32 bit.
games/jackhammer: Update download url.
games/openmsx: Added dmk tools from Contrib.
games/quakeforge: Fix build with ARCH=i686.
games/warsow: Update download url.
gis/gdal: Add python3 support.
graphics/Blender: Updated for version 2.79a
graphics/FreeCAD: Updated for version 0.16.6712.
graphics/feh: Updated for version 2.24.
graphics/gource: Updated for version 0.48.
graphics/openimageio: Updated for version 1.8.9
graphics/yacreader: Updated for version 9.0.0.
libraries/SDL2: Updated for version 2.0.8.
libraries/gtk3-nocsd: Added (disable gtk+ 3 client side decoration).
libraries/libabw: Updated for version 0.1.2.
libraries/libe-book: Updated for version 0.1.3.
libraries/libepubgen: Added (EPUB generator for librevenge).
libraries/libixion: Updated for version 0.13.0.
libraries/libmspub: Updated for version 0.1.3.
libraries/liborcus: Updated for version 0.13.3.
libraries/libpagemaker: Updated for version 0.0.4.
libraries/libqxp: Added (QuarkXPress documents parser library).
libraries/libtorrent-rasterbar: Adjust CXXFLAGS.
libraries/live555: Updated for version 2018.02.28
libraries/xview: Fix build with ARCH=i686.
libraries/xview: Update download url.
misc/mosquitto: Updated for version 1.4.15
misc/tegaki-zinnia-japanese: Update download url.
multimedia/gpodder: Updated for version 3.10.1.
multimedia/huludesktop: Update download url.
multimedia/makemkv: Update download url.
multimedia/opera-ffmpeg-codecs: Updated for version 64.0.3282.168.
multimedia/qsampler: Update download url.
multimedia/smplayer: Updated for version 18.2.2.
multimedia/spotify: Updated for version 1.0.72.
multimedia/vlc: Updated for version 3.0.1
network/Electrum-DASH: Update download url.
network/argus: Update download url.
network/arpwatch: Update download url.
network/basilisk-src: Added (browser).
network/bird: Update download url.
network/bitcoin: Updated for version 0.16.0.
network/boxcryptor: Update download url.
network/btsync: Update download url.
network/cadaver: Update download url.
network/cicb: Update download url.
network/clipgrab: Updated for version 3.6.8.
network/clive: Update download url.
network/dnscrypt-proxy: Fix DOWNLOAD url.
network/dropbear: Updated for version 2018.76
network/dropbox: Update download url.
network/emacs-w3m: Update download url.
network/firehol: Update download url.
network/fping6: Update download url.
network/freeradius-server: Update download url.
network/hostsblock: Update download url.
network/httping: Update download url.
network/kasp_updater: Update download url.
network/kcm_ufw: Update download url.
network/leafnode: Update download url.
network/lizardfs: Added (GPLv3 implementation of GoogleFS).
network/mod_chroot: Update download url.
network/netperf: Update download url.
network/opera-developer: Updated for version 52.0.2871.0.
network/opera: Updated for version 51.0.2830.40.
network/palemoon: Updated for version 27.8.0.
network/pidgin-birthday-reminder: Update download url.
network/pidgin-visnotes: Update download url.
network/postfix: Updated for version 3.3.0.
network/seahub: Update download url.
network/shorewall-core: Updated for version 5.1.12.3.
network/shorewall6: Updated for version 5.1.12.3.
network/shorewall: Updated for version 5.1.12.3.
network/signal-desktop: Added (Signal for Desktop).
network/varnish: Update download url.
network/vcspull: Update download url.
network/vimb: Update script.
network/vivaldi: Updated for version 1.14.1077.55.
network/wireshark: Updated for version 2.4.5.
network/yandex-browser-beta: Update download url.
office/JabRef: Update download url.
office/LibreOffice: Updated for version 6.0.2.1
office/hevea: Update download url.
office/keepassxc: Updated for version 2.3.0.
office/keepnote: Update download url.
office/libreoffice-helppack: Updated for version 6.0.2.
office/libreoffice-langpack: Updated for version 6.0.2.
office/libreoffice: Update README.
office/libreoffice: Updated for version 6.0.2.
office/mu: Updated for version 1.0.
office/notmuch: Updated for version 0.26.
office/teapot: Update download url.
office/trelby: Update download url.
office/verbiste: Update download url.
office/xmind: Update download url.
perl/perl-DBD-Pg: Update download url.
perl/perl-X10: Updated for version 0.04.
perl/perl-YAML-Tiny: Updated for version 1.73.
python/dfdatetime: Update download url.
python/dfwinreg: Update download url.
python/dhcpy6d: Update download url.
python/mock: Switch to https.
python/p4python: Update download url.
python/pynzb: Switch to https.
python/pyquery: Switch to https.
python/pystatsd: Switch to https.
python/python-cheetah: Switch to https.
python/python-discid: Switch to https.
python/python-fonttools: Updated for version 3.24.0
python/python-oauth: Switch to https.
python/python-orbited: Switch to https.
python/python-yenc: Update download url.
python/pyudev: Switch to https.
python/rope: Switch to https.
python/websocket-client: Updated for version 0.47.0.
ruby/ruby-build: Updated for version 20180224.
ruby/sequel: Updated for version 5.5.0.
system/GentiumPlus: Update download url.
system/alacritty: Updated for version git475ebec.
system/ansible: Updated for version 2.4.3.0.
system/audit: Switch to i586, fix i686 build.
system/blake2: Update download url.
system/chipsec: Fix build on 32 bit.
system/eaglemode: Update download url.
system/efitools: Update download url.
system/emelfm2: Update download url.
system/epson-inkjet-printer-escpr: Update download url.
system/exa: Fix building on -current.
system/exomizer: Update download url.
system/fd: Fix building on -current.
system/fswatch: Fix build on 32 bit.
system/kafka: Update download url.
system/kbfs: Updated for version 1.0.44_20180223200436.
system/keybase: Updated for version 1.0.44 1.0.44.
system/mktorrent: Updated for version 1.1.
system/nanum-coding-fonts-ttf: Update download url.
system/noto-fonts: Fix script.
system/open-vm-tools: Fix optional deps in README.
system/pce: Update download url.
system/pcsc-tools: Update download url.
system/qemu-guest-agent: Updated for version 2.11.1.
system/rfdump: Update download url.
system/sbbdep: Updated for version 0.3.0.
system/slackchlog: Update download url.
system/tkdvd: Update download url.
system/ttf-arphic-uming: Update download url.
system/ttmkfdir: Update download url.
system/usbrelay: Added (software for HID usb relays).
system/vtcol: Fix building on -current.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180303/a9029e0e/attachment-0001.asc>

From rundstutzen at gmx.de  Sat Mar  3 07:34:10 2018
From: rundstutzen at gmx.de (rundstutzen at gmx.de)
Date: Sat, 3 Mar 2018 08:34:10 +0100
Subject: [Slackbuilds-users] Updates - 20180303.1
In-Reply-To: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>
References: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>
Message-ID: <20180303083410.04fca56d@fiete.bug.net>

dear maintainers,

On Sat, 3 Mar 2018 09:15:20 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> Hi,
> 
> It's all thanks to Heiko for starting the work on this one. We started
> to fix them in the past few days until the last minute before this
> public update, but we think it's quite important to deliver this
> update as well, so we will continue working on fixing this issue in
> the next batch.
> 

i consider slackbuild.org essential for using slackware, so i am happy
that i can help in a way (and that you care for what i am doing).

it seems some people here have use for sbog so i pushed out a new
release: this is sbog 0.3-rc1.

this version implements the "ping" command. the documentation ("sbog
help") is lacking, but using ping is easy:

sbog ping <sborepodir>

ping errors are written to stdout, others to stderr, as usual. have fun
with it.

when downloading please verify the checksums:

cb8a516f122940f71c04db02f1839652f68ee3fc3a662f2be938e7df232e5bc07f8c7361254e16e225c8c4355b3c8e6523150a0fa7f9cef5cfae2d26a28ca725   sbog-0.3-rc1-x64

6ff04169162ea3594696840815b115fcf12ce0d506c5d60e69cad3d0cd51310b12e8d754e97ae07c9555c8d96cc38bd702c4d54320e013898a0956d403010cb7  sbog-0.3-rc1-x64_64

keep up the good work!

regards,

heiko

From philip at vd-hoeven.nl  Sat Mar  3 09:39:25 2018
From: philip at vd-hoeven.nl (Philip van der Hoeven)
Date: Sat, 03 Mar 2018 10:39:25 +0100
Subject: [Slackbuilds-users] Updates - 20180303.1
In-Reply-To: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>
References: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>
Message-ID: <db6a92d5ce87a560bce6070569ae749d@vd-hoeven.nl>

On 2018-03-03 03:15, Willy Sudiarto Raharjo wrote:

> Maintainers, please see https://pastebin.com/pbFdSAyW
> If your name came up, please take some time to fix the URLs.
> If you can't find alternative link, you can use sbosrcharch
> (http://slackware.uk/sbosrcarch/).
> Please note that some of those entries have been fixed in this batch,
> while others might have false positive alerts
> hkjgdf

Hi,

The btsync can be removed as far as I am concerned.
Since they went commercial I don't think anybody uses this anymore since 
open source alternatives exist, such as syncthing.

Philip

From artourter at gmail.com  Sat Mar  3 13:55:15 2018
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Sat, 3 Mar 2018 13:55:15 +0000
Subject: [Slackbuilds-users] Updates - 20180303.1
In-Reply-To: <db6a92d5ce87a560bce6070569ae749d@vd-hoeven.nl>
References: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>
 <db6a92d5ce87a560bce6070569ae749d@vd-hoeven.nl>
Message-ID: <CAK09-vmfUk8ZQBWL0q6A92LmCK2_pbPYP-ZEz9yaWqYs4tkY0Q@mail.gmail.com>

Hi,

keepassxc md5sum mismatch on the lastest release:

  MD5SUM check for keepassxc-2.3.0-src.tar.xz ... FAILED!
    Expected: 1dba769f0eb1303ef3fbd873acd81901
    Found:    127490ae7e4b3f49426619ec6f902bb6

Cheers

Greg

On 3 March 2018 at 09:39, Philip van der Hoeven <philip at vd-hoeven.nl> wrote:

> On 2018-03-03 03:15, Willy Sudiarto Raharjo wrote:
>
> Maintainers, please see https://pastebin.com/pbFdSAyW
>> If your name came up, please take some time to fix the URLs.
>> If you can't find alternative link, you can use sbosrcharch
>> (http://slackware.uk/sbosrcarch/).
>> Please note that some of those entries have been fixed in this batch,
>> while others might have false positive alerts
>> hkjgdf
>>
>
> Hi,
>
> The btsync can be removed as far as I am concerned.
> Since they went commercial I don't think anybody uses this anymore since
> open source alternatives exist, such as syncthing.
>
> Philip
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180303/16a5b868/attachment.html>

From rundstutzen at gmx.de  Sat Mar  3 14:01:05 2018
From: rundstutzen at gmx.de (rundstutzen at gmx.de)
Date: Sat, 3 Mar 2018 15:01:05 +0100
Subject: [Slackbuilds-users] Updates - 20180303.1
In-Reply-To: <20180303083410.04fca56d@fiete.bug.net>
References: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>
 <20180303083410.04fca56d@fiete.bug.net>
Message-ID: <20180303150105.6824d4ab@fiete.bug.net>

sorry, i forget to mention the download url: 

https://bitbucket.org/trueslack/sbog/downloads/


On Sat, 3 Mar 2018 08:34:10 +0100
<rundstutzen at gmx.de> wrote:

> 
> it seems some people here have use for sbog so i pushed out a new
> release: this is sbog 0.3-rc1.
> 
> this version implements the "ping" command. the documentation ("sbog
> help") is lacking, but using ping is easy:
> 
> sbog ping <sborepodir>
> 
> ping errors are written to stdout, others to stderr, as usual. have
> fun with it.
> 
> when downloading please verify the checksums:
> 
> cb8a516f122940f71c04db02f1839652f68ee3fc3a662f2be938e7df232e5bc07f8c7361254e16e225c8c4355b3c8e6523150a0fa7f9cef5cfae2d26a28ca725
> sbog-0.3-rc1-x64
> 
> 6ff04169162ea3594696840815b115fcf12ce0d506c5d60e69cad3d0cd51310b12e8d754e97ae07c9555c8d96cc38bd702c4d54320e013898a0956d403010cb7
> sbog-0.3-rc1-x64_64
> 

From willysr at slackbuilds.org  Sat Mar  3 14:08:29 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 3 Mar 2018 21:08:29 +0700
Subject: [Slackbuilds-users] Updates - 20180303.1
In-Reply-To: <CAK09-vmfUk8ZQBWL0q6A92LmCK2_pbPYP-ZEz9yaWqYs4tkY0Q@mail.gmail.com>
References: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>
 <db6a92d5ce87a560bce6070569ae749d@vd-hoeven.nl>
 <CAK09-vmfUk8ZQBWL0q6A92LmCK2_pbPYP-ZEz9yaWqYs4tkY0Q@mail.gmail.com>
Message-ID: <b7993b03-7b7e-89f1-4811-272a71f71b0c@slackbuilds.org>

> keepassxc md5sum mismatch on the lastest release:
> 
> ? MD5SUM check for keepassxc-2.3.0-src.tar.xz ... FAILED!
> ??? Expected: 1dba769f0eb1303ef3fbd873acd81901
> ??? Found:??? 127490ae7e4b3f49426619ec6f902bb6

Thanks

Fixed in my branch


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180303/a57300e3/attachment.asc>

From dominik.drobek at o2.pl  Fri Mar  2 21:55:35 2018
From: dominik.drobek at o2.pl (Dominik Drobek)
Date: Fri, 2 Mar 2018 22:55:35 +0100
Subject: [Slackbuilds-users] RFC: patch for cfitsio for some astronomy
 software
In-Reply-To: <aafdbc0a-44b5-ce8f-457c-6ceed5aacee4@gmail.com>
References: <aafdbc0a-44b5-ce8f-457c-6ceed5aacee4@gmail.com>
Message-ID: <7f63cb24-a73b-d30c-3a5f-82c3846f41f4@o2.pl>

W dniu 02.03.2018 o?03:54, King Beowulf pisze:
> I recommend applying the Fedora patch to cfitsio to fix underlinking to
> bzip2 for some astronomy software.

Hi,

Thanks for notifying me.

I'd like to clarify one thing. Ed's suggested modification to 
cfitsio.SlackBuild removes most of the bundled zlib sources. I'm not 
sure this step is necessary, as the Fedora patch removes these source 
files from ZLIB_SOURCES variable in Makefile.in. Applying the patch 
seems to be enough to avoid compilation of these files.

By the way, cfitsio has just been updated to version 3.430. Fedora patch 
still applies, so I can include it in the next update.

Regards,
Dominik

From dominik.drobek at o2.pl  Sat Mar  3 00:42:09 2018
From: dominik.drobek at o2.pl (Dominik Drobek)
Date: Sat, 3 Mar 2018 01:42:09 +0100
Subject: [Slackbuilds-users] RFC: patch for cfitsio for some astronomy
 software
In-Reply-To: <2c2edd49-ca5b-f429-4711-5f21a362f124@gmail.com>
References: <aafdbc0a-44b5-ce8f-457c-6ceed5aacee4@gmail.com>
 <7f63cb24-a73b-d30c-3a5f-82c3846f41f4@o2.pl>
 <2c2edd49-ca5b-f429-4711-5f21a362f124@gmail.com>
Message-ID: <b2216a28-c48d-d278-dae3-f3385b76c44f@o2.pl>

W dniu 03.03.2018 o?00:40, King Beowulf pisze:
> I wasn't aware that the patch also removes the bundled zlib. Since zlib
> (and bzip2) are part of Slackware, would there be any unintended
> consequences? 
I have some doubts about that as well. I suppose that cfitsio authors 
have a good reason to include zlib in their source tarball. Apart from 
that, removing bundled zlib would violate the SlackBuilds.org 
recommendation "No custom patches unless absolutely necessary".

> I'm still sorting out libindi and drivers compilation and
> so have not yet tested if anything works.
Could you test something for me, Ed?

In my cfitsio.SlackBuild ./configure has an option --with-bzip2. Could 
you remove --with-bzip2, recompile cfitsio (without applying any 
patches), reinstall, and then try to compile libindi once more? Will it 
report any linking errors?

Regards,
Dominik

From dominik.drobek at o2.pl  Sat Mar  3 17:59:43 2018
From: dominik.drobek at o2.pl (Dominik Drobek)
Date: Sat, 3 Mar 2018 18:59:43 +0100
Subject: [Slackbuilds-users] RFC: patch for cfitsio for some astronomy
 software
In-Reply-To: <b2216a28-c48d-d278-dae3-f3385b76c44f@o2.pl>
References: <aafdbc0a-44b5-ce8f-457c-6ceed5aacee4@gmail.com>
 <7f63cb24-a73b-d30c-3a5f-82c3846f41f4@o2.pl>
 <2c2edd49-ca5b-f429-4711-5f21a362f124@gmail.com>
 <b2216a28-c48d-d278-dae3-f3385b76c44f@o2.pl>
Message-ID: <7548f0bc-7e56-e622-9805-03d19e446855@o2.pl>

Hi again,

Turns out you don't need to compile libindi to reproduce the issue. It's 
sufficient to simply attempt to compile anything with gcc using -lcfitsio.

The problem is in the way configure script in cfitsio handles 
--with-bzip2 option. It has an "optional" argument, which is supposed to 
be a path to where libbz2.so resides. Notice this snippet from configure.in:

# BZIP2 flags:
if test "x$BZIP2_PATH" != x; then
    CFLAGS="$CFLAGS -I${BZIP2_PATH}/include"
    LDFLAGS="$LDFLAGS -L${BZIP2_PATH}/lib -lbz2"
fi

If "optional" argument to --with-bzip2 is not supplied then $BZIP2_PATH 
is empty, and -lbz2 doesn't get added to LDFLAGS. If $BZIP2_PATH is not 
empty then -lbz2 will be added to LDFLAGS. Additionally, -L option will 
be added. This will not have a correct path in Slackware64 (because it 
always ends with "/lib"), but it actually doesn't matter, since system 
libbz2.so is in the default search location.

I prefer to fix this issue with my SlackBuild by simply removing 
--with-bzip2 option from ./configure. And I will do it this way, unless 
you will tell me that you need bzip2 support in cfitsio. :)

I naively assumed that simply adding --with-bzip2 will enable this 
feature without any further problems. Sorry for the inconvenience.

Regards,
Dominik

From ewj at pigs.ag  Sat Mar  3 22:12:48 2018
From: ewj at pigs.ag (E. Wayne Johnson)
Date: Sun, 4 Mar 2018 06:12:48 +0800
Subject: [Slackbuilds-users] Rstudio
Message-ID: <bd3a6922-fe8c-39b7-7974-256d1c8dfeb9@pigs.ag>

Hello.

The Slackbuild for Rstudio fails compilation with a series of boost errors.

Others have reported this problem.

See:

https://www.linuxquestions.org/questions/slackware-14/rstudio-compile-fails-on-current-4175571764/

Thank your for your efforts and interest.

EWJ

From willysr at slackbuilds.org  Sat Mar  3 22:23:06 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 4 Mar 2018 05:23:06 +0700
Subject: [Slackbuilds-users] Rstudio
In-Reply-To: <bd3a6922-fe8c-39b7-7974-256d1c8dfeb9@pigs.ag>
References: <bd3a6922-fe8c-39b7-7974-256d1c8dfeb9@pigs.ag>
Message-ID: <867b1808-8096-ac70-7905-f09a646585e5@slackbuilds.org>

> The Slackbuild for Rstudio fails compilation with a series of boost errors.
> 
> Others have reported this problem.
> 
> See:
> 
> https://www.linuxquestions.org/questions/slackware-14/rstudio-compile-fails-on-current-4175571764/

Have you tried to compile on -stable?
Remember that SBo targets for -stable, not -current


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180304/eddffeb7/attachment.asc>

From matteo.bernardini at gmail.com  Sun Mar  4 10:55:26 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 4 Mar 2018 11:55:26 +0100
Subject: [Slackbuilds-users] rstudio-desktop
Message-ID: <CAPsDuS5e-pF0tdCSdKiYP=h5e4f+jOJWV2pPxBAntD1y9M6JFQ@mail.gmail.com>

after a chat with the admins and checking:

- the reports on LinuxQuestions;

- our mailing list archive;

- its git history
https://git.slackbuilds.org/slackbuilds/log/development/rstudio-desktop

we concluded that the present maintainer of rstudio-desktop is
MIA/non-responsive so the script is up for grabs for whoever feels
like to update it and maintain it from now on.

From slackware at lemintown.eu  Sun Mar  4 14:39:40 2018
From: slackware at lemintown.eu (Brian)
Date: Sun, 4 Mar 2018 15:39:40 +0100
Subject: [Slackbuilds-users] Keepassxc missing dependency
Message-ID: <2a69f072-04f7-1171-4c8d-8b8e060da41d@lemintown.eu>

Hello,

Browser support needs the package libsodium (available on SBo) which 
should be listed as required since the default slackbuild features 
XC_BROWSER=ON

Brian


From slackbuilds at jaxartes.net  Sun Mar  4 14:47:35 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Sun, 04 Mar 2018 06:47:35 -0800
Subject: [Slackbuilds-users] Keepassxc missing dependency
In-Reply-To: <2a69f072-04f7-1171-4c8d-8b8e060da41d@lemintown.eu>
References: <2a69f072-04f7-1171-4c8d-8b8e060da41d@lemintown.eu>
Message-ID: <1742258.9cUOcc9Ysf@wintermute.sprawl.net>

On Sunday, 4 March 2018 06:39:40 PST Brian wrote:
> Hello,
> 
> Browser support needs the package libsodium (available on SBo) which
> should be listed as required since the default slackbuild features
> XC_BROWSER=ON
> 
> Brian
> 

Fixed, thanks.



From kjhambrick at gmail.com  Sun Mar  4 15:00:31 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 4 Mar 2018 09:00:31 -0600
Subject: [Slackbuilds-users] pdftk on Slackware Current
Message-ID: <CANBHt+PKMDMyWbr7JK_U71fcsYXfqv2iQjLy3_CjowKWA93OEQ@mail.gmail.com>

ArTourter --

I documented what I had to do after to build pdftk installing Alien Bob's
gcc5.SlackBuild on Slackware64-current in this thread on LQ:

https://www.linuxquestions.org/questions/slackware-14/building-pdftk-on-slackware-15-0-current-4175624922/

These three patch files modify the SlackBuild Files:

   -rw-r--r-- 1 root root  497 Mar  4 07:39
/home/tmp/README-Slackware-15.0.patch.txt
   -rw-r--r-- 1 root root  694 Mar  4 07:40
/home/tmp/pdftk.SlackBuild-Slackware-15.0.patch.txt
   -rw-r--r-- 1 root root  300 Mar  4 07:40
/home/tmp/pdftk.info-Slackware-15.0.patch.txt

This patch file replaces the existing pdftk-1.44-add_custom_optflags.patch
for Slackware -current + gcc5 in the SlackBuild Directory:

   -rw-r--r-- 1 root root  665 Mar  4 07:40
/home/tmp/pdftk-2.02-on-Slackware-15.patch.txt

I imagine there is a better way than my kludgy SLACKVER=15 Variable to
differentiate Slackware 15.0 from Slackware 14.2 in the pdftk.SlackBuild.

The only real change was to force GXX=gcc-5 in the
pdftk/Makefile.Slackware-13.1 Makefile ...

Thanks for the pdftk.SlackBuild ArTourter -- it is an essential tool where
I work !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180304/44b0f554/attachment.html>
-------------- next part --------------
--- pdftk/README	2018-02-17 16:26:26.371132683 -0600
+++ pdftk-15.0/README	2018-03-04 06:53:51.638842490 -0600
@@ -4,3 +4,6 @@
 in the top drawer of your desktop and use it to merge PDF documents, 
 split PDF documents, apply watermarks, repair corrupt PDF, update PDF 
 metadata, and more.  pdftk does not require Acrobat and is free software.
+
+Note:  Starting with Slackware 15.0 pdftk compilation requires SBo gcc-5 
+because gcc-java was dropped from the GNU Compiler Collection as of gcc-7
-------------- next part --------------
--- pdftk/pdftk.SlackBuild	2018-02-17 16:26:26.371132683 -0600
+++ pdftk-15.0/pdftk.SlackBuild	2018-03-04 07:00:19.578831027 -0600
@@ -28,6 +28,8 @@
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
+SLACKVER=${SLACKVER:-15}
+
 if [ -z "$ARCH" ]; then
   case "$( uname -m )" in
     i?86) ARCH=i486 ;;
@@ -71,7 +73,13 @@
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
 # Use our SLKCFLAGS
-patch -p1 < $CWD/pdftk-1.44-add_custom_optflags.patch
+
+if [ -n "$SLACKVER" -a "$SLACKVER" -ge "15" ]
+then
+   patch -p1 < $CWD/pdftk-2.02-on-Slackware-15.patch
+else
+   patch -p1 < $CWD/pdftk-1.44-add_custom_optflags.patch
+fi
 
 cd $PRGNAM
   # Hardcode "-j1" since this fails with multiple make jobs
-------------- next part --------------
--- pdftk/pdftk.info	2018-02-17 16:26:26.371132683 -0600
+++ pdftk-15.0/pdftk.info	2018-03-04 06:52:13.255845397 -0600
@@ -5,6 +5,6 @@
 MD5SUM="6534365fd6727724f288a556ede33faa"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES=""
+REQUIRES="gcc-5"
 MAINTAINER="ArTourter"
 EMAIL="artourter at gmail.com"
-------------- next part --------------
# diff -Nurp pdftk/Makefile.Slackware-13.1.orig pdftk/Makefile.Slackware-13.1
--- orig/pdftk/Makefile.Slackware-13.1  2013-07-24 13:27:46.000000000 -0500
+++ pdftk/Makefile.Slackware-13.1       2018-03-04 06:20:55.312900883 -0600
@@ -21,8 +21,9 @@
 # tools
 # need direct path to libgcj for gcjh (starting in gcj 4.1.2 per Aur??lien G?R?ME)
 TOOLPATH=
-export VERSUFF=-4.4.4
-export CXX= $(TOOLPATH)g++
+GCCMAJORTAG=-5                            # kjh was here
+export VERSUFF=-5.5.0                     # kjh was here
+export CXX= $(TOOLPATH)g++$(GCCMAJORTAG)  # kjh was here
 export GCJ= $(TOOLPATH)gcj
 export GCJH= $(TOOLPATH)gcjh
 export GJAR= $(TOOLPATH)gjar

From kjhambrick at gmail.com  Sun Mar  4 15:03:04 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 4 Mar 2018 09:03:04 -0600
Subject: [Slackbuilds-users] pdftk on Slackware Current
In-Reply-To: <CANBHt+PKMDMyWbr7JK_U71fcsYXfqv2iQjLy3_CjowKWA93OEQ@mail.gmail.com>
References: <CANBHt+PKMDMyWbr7JK_U71fcsYXfqv2iQjLy3_CjowKWA93OEQ@mail.gmail.com>
Message-ID: <CANBHt+MBj3CJQCiHoktzvve97cKm9rrorxM-NL5c9E--CD+Btg@mail.gmail.com>

Dang !

I said:   I documented what I had to do after to build pdftk installing
Alien Bob's gcc5.SlackBuild on Slackware64-current in this thread on LQ:

I meant:  I documented what I had to do to build pdftk after installing
Alien Bob's gcc5.SlackBuild on Slackware64-current in this thread on LQ:

Sorry ... I REALLY need a 'preview' feature :)

-- kjh

On Sun, Mar 4, 2018 at 9:00 AM, Konrad J Hambrick <kjhambrick at gmail.com>
wrote:

> ArTourter --
>
> I documented what I had to do after to build pdftk installing Alien Bob's
> gcc5.SlackBuild on Slackware64-current in this thread on LQ:
>
> https://www.linuxquestions.org/questions/slackware-14/
> building-pdftk-on-slackware-15-0-current-4175624922/
>
> These three patch files modify the SlackBuild Files:
>
>    -rw-r--r-- 1 root root  497 Mar  4 07:39 /home/tmp/README-Slackware-15.
> 0.patch.txt
>    -rw-r--r-- 1 root root  694 Mar  4 07:40 /home/tmp/pdftk.SlackBuild-
> Slackware-15.0.patch.txt
>    -rw-r--r-- 1 root root  300 Mar  4 07:40 /home/tmp/pdftk.info-
> Slackware-15.0.patch.txt
>
> This patch file replaces the existing pdftk-1.44-add_custom_optflags.patch
> for Slackware -current + gcc5 in the SlackBuild Directory:
>
>    -rw-r--r-- 1 root root  665 Mar  4 07:40 /home/tmp/pdftk-2.02-on-
> Slackware-15.patch.txt
>
> I imagine there is a better way than my kludgy SLACKVER=15 Variable to
> differentiate Slackware 15.0 from Slackware 14.2 in the pdftk.SlackBuild.
>
> The only real change was to force GXX=gcc-5 in the
> pdftk/Makefile.Slackware-13.1 Makefile ...
>
> Thanks for the pdftk.SlackBuild ArTourter -- it is an essential tool where
> I work !
>
> -- kjh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180304/524993f0/attachment-0001.html>

From slackbuilds at jaxartes.net  Sun Mar  4 15:41:42 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Sun, 04 Mar 2018 07:41:42 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
Message-ID: <15224385.AzDNfkVVfH@wintermute.sprawl.net>

If anyone is interested in running QGIS 3.0.0 on Slackware 14.2, I have 
working build scripts available. I would like feedback and bug reports, of 
course, but I'm also interested in hearing how much demand there is for QGIS 3 
to be an official SlackBuild.

Instructions and new SlackBuilds are located here https://github.com/bosth/
qgis3-slackbuild (this is still a work in progress so not everything is 
intended to be ready for submission). The end product won't be compatible with 
an existing QGIS 2.x installation.

For the missing but optional Python 3 modules I mentioned in the README, you 
can just use pip3 install $NAME --user to install them until we have proper 
Python 3 SlackBuilds. I believe it is just psycopg2, owslib and Jinja2 that 
need this treatment.

Ben



From kjhambrick at gmail.com  Sun Mar  4 16:46:28 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 4 Mar 2018 10:46:28 -0600
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
Message-ID: <CANBHt+OPhWg8z4veuK73k32kBXb7ww_KQ42Tjy1OO0=nnutCKw@mail.gmail.com>

Wow Ben.

I checked out QGIS' Home Page:  https://qgis.org/en/site/

It is a very impressive piece of work !

Speaking of work, I wish I had time to test your qgis-3.SlackBuild but I've
got my hands full right now.

We do have a project coming up later this summer where QGIS might be a
great way to display tax jurisdictions in certain US Locations.

Anyhow ... thanks for turning me on to QGIS and good luck with your
qgis-3.SlackBuild Project !

-- kjh

On Sun, Mar 4, 2018 at 9:41 AM, Benjamin Trigona-Harany <
slackbuilds at jaxartes.net> wrote:

> If anyone is interested in running QGIS 3.0.0 on Slackware 14.2, I have
> working build scripts available. I would like feedback and bug reports, of
> course, but I'm also interested in hearing how much demand there is for
> QGIS 3
> to be an official SlackBuild.
>
> Instructions and new SlackBuilds are located here
> https://github.com/bosth/
> qgis3-slackbuild (this is still a work in progress so not everything is
> intended to be ready for submission). The end product won't be compatible
> with
> an existing QGIS 2.x installation.
>
> For the missing but optional Python 3 modules I mentioned in the README,
> you
> can just use pip3 install $NAME --user to install them until we have proper
> Python 3 SlackBuilds. I believe it is just psycopg2, owslib and Jinja2 that
> need this treatment.
>
> Ben
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180304/e62ecfcb/attachment.html>

From artourter at gmail.com  Sun Mar  4 16:50:14 2018
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Sun, 4 Mar 2018 16:50:14 +0000
Subject: [Slackbuilds-users] pdftk on Slackware Current
In-Reply-To: <CANBHt+MBj3CJQCiHoktzvve97cKm9rrorxM-NL5c9E--CD+Btg@mail.gmail.com>
References: <CANBHt+PKMDMyWbr7JK_U71fcsYXfqv2iQjLy3_CjowKWA93OEQ@mail.gmail.com>
 <CANBHt+MBj3CJQCiHoktzvve97cKm9rrorxM-NL5c9E--CD+Btg@mail.gmail.com>
Message-ID: <CAK09-vmRQk1k16GVoT=myLMoKcFdAGPexkN7M_Pc5bxd33Uq3g@mail.gmail.com>

Hi Konrad,

Thanks for that. I have had the same setup ready for a while now, basically
since Eric released his gcc-5 package. I have been reluctant to actually
release it due to its reliance on a package that is neither available on
slackbuilds.org nor officially part of slackware.

I was in a way waiting to see if the gcc-legacy package here would start
build gcj as part of it. but since sbo doesn't officially support -current,
it was not at the top of my todo list to chase things up. Your email shows
that there is demand so maybe I should start thinking about the best way to
proceed.

SBo admins, what is the policy about requiring a package not available on
slackware or slackbuild?

Cheers

Greg

On 4 March 2018 at 15:03, Konrad J Hambrick <kjhambrick at gmail.com> wrote:

>
> Dang !
>
> I said:   I documented what I had to do after to build pdftk installing
> Alien Bob's gcc5.SlackBuild on Slackware64-current in this thread on LQ:
>
> I meant:  I documented what I had to do to build pdftk after installing
> Alien Bob's gcc5.SlackBuild on Slackware64-current in this thread on LQ:
>
> Sorry ... I REALLY need a 'preview' feature :)
>
> -- kjh
>
> On Sun, Mar 4, 2018 at 9:00 AM, Konrad J Hambrick <kjhambrick at gmail.com>
> wrote:
>
>> ArTourter --
>>
>> I documented what I had to do after to build pdftk installing Alien Bob's
>> gcc5.SlackBuild on Slackware64-current in this thread on LQ:
>>
>> https://www.linuxquestions.org/questions/slackware-14/buildi
>> ng-pdftk-on-slackware-15-0-current-4175624922/
>>
>> These three patch files modify the SlackBuild Files:
>>
>>    -rw-r--r-- 1 root root  497 Mar  4 07:39 /home/tmp/README-Slackware-15.
>> 0.patch.txt
>>    -rw-r--r-- 1 root root  694 Mar  4 07:40 /home/tmp/pdftk.SlackBuild-Sla
>> ckware-15.0.patch.txt
>>    -rw-r--r-- 1 root root  300 Mar  4 07:40 /home/tmp/pdftk.info-Slackware
>> -15.0.patch.txt
>>
>> This patch file replaces the existing pdftk-1.44-add_custom_optflags.patch
>> for Slackware -current + gcc5 in the SlackBuild Directory:
>>
>>    -rw-r--r-- 1 root root  665 Mar  4 07:40 /home/tmp/pdftk-2.02-on-Slackw
>> are-15.patch.txt
>>
>> I imagine there is a better way than my kludgy SLACKVER=15 Variable to
>> differentiate Slackware 15.0 from Slackware 14.2 in the pdftk.SlackBuild.
>>
>> The only real change was to force GXX=gcc-5 in the
>> pdftk/Makefile.Slackware-13.1 Makefile ...
>>
>> Thanks for the pdftk.SlackBuild ArTourter -- it is an essential tool
>> where I work !
>>
>> -- kjh
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180304/e956aa96/attachment.html>

From matteo.bernardini at gmail.com  Sun Mar  4 17:11:03 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 4 Mar 2018 18:11:03 +0100
Subject: [Slackbuilds-users] pdftk on Slackware Current
In-Reply-To: <CAK09-vmRQk1k16GVoT=myLMoKcFdAGPexkN7M_Pc5bxd33Uq3g@mail.gmail.com>
References: <CANBHt+PKMDMyWbr7JK_U71fcsYXfqv2iQjLy3_CjowKWA93OEQ@mail.gmail.com>
 <CANBHt+MBj3CJQCiHoktzvve97cKm9rrorxM-NL5c9E--CD+Btg@mail.gmail.com>
 <CAK09-vmRQk1k16GVoT=myLMoKcFdAGPexkN7M_Pc5bxd33Uq3g@mail.gmail.com>
Message-ID: <CAPsDuS6hQF10pQGYn5d-bLZNypVZB50TaTb0XSr0eL4bGwjSGw@mail.gmail.com>

2018-03-04 17:50 GMT+01:00 Greg' Ar Tourter <artourter at gmail.com>:
> Hi Konrad,
>
> Thanks for that. I have had the same setup ready for a while now, basically
> since Eric released his gcc-5 package. I have been reluctant to actually
> release it due to its reliance on a package that is neither available on
> slackbuilds.org nor officially part of slackware.
>
> I was in a way waiting to see if the gcc-legacy package here would start
> build gcj as part of it. but since sbo doesn't officially support -current,
> it was not at the top of my todo list to chase things up. Your email shows
> that there is demand so maybe I should start thinking about the best way to
> proceed.
>
> SBo admins, what is the policy about requiring a package not available on
> slackware or slackbuild?

for what concerns SBo you should wait until submission for the next
release are open, we support only the latest stable release.

that said, in the meantime I pushed Eric's gcc5 and Konrad patches to
the unofficial repository for current on my github (they will go in
the main branch at the next update): if you wish to patch pdftk
differently there just notice me.

http://cgit.ponce.cc/slackbuilds/log/?h=gcc5
http://cgit.ponce.cc/slackbuilds/commit/?h=pdftk

Matteo

From willysr at slackbuilds.org  Sun Mar  4 17:14:32 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 5 Mar 2018 00:14:32 +0700
Subject: [Slackbuilds-users] pdftk on Slackware Current
In-Reply-To: <CAK09-vmRQk1k16GVoT=myLMoKcFdAGPexkN7M_Pc5bxd33Uq3g@mail.gmail.com>
References: <CANBHt+PKMDMyWbr7JK_U71fcsYXfqv2iQjLy3_CjowKWA93OEQ@mail.gmail.com>
 <CANBHt+MBj3CJQCiHoktzvve97cKm9rrorxM-NL5c9E--CD+Btg@mail.gmail.com>
 <CAK09-vmRQk1k16GVoT=myLMoKcFdAGPexkN7M_Pc5bxd33Uq3g@mail.gmail.com>
Message-ID: <896ec9d0-ce7a-e61f-e54d-065d122de571@slackbuilds.org>

> SBo admins, what is the policy about requiring a package not available
> on slackware or slackbuild?

Hi Greg,

Unfortunately we can't accept such submissions.
The dependencies must be included in Slackware's full installation +
latest update OR available in SBo repository.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180305/eaedd90d/attachment-0001.asc>

From rshepard at appl-ecosys.com  Sun Mar  4 18:34:10 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 4 Mar 2018 10:34:10 -0800 (PST)
Subject: [Slackbuilds-users] Google-earth: dangling symlinks
Message-ID: <alpine.LNX.2.20.1803041032100.11584@salmo.appl-ecosys.com>

   Upgrading SBo packages on a 14.2/64-bit host. Google-earth failed because
of a couple of dangling symlinks. I did not capture the errors, but will if
necessary.

   Am I the only one with this issue?

Rich

From willysr at slackbuilds.org  Sun Mar  4 18:38:55 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 5 Mar 2018 01:38:55 +0700
Subject: [Slackbuilds-users] Google-earth: dangling symlinks
In-Reply-To: <alpine.LNX.2.20.1803041032100.11584@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1803041032100.11584@salmo.appl-ecosys.com>
Message-ID: <d96d8c96-3484-4a52-3091-854f4419d3d1@slackbuilds.org>

> ? Upgrading SBo packages on a 14.2/64-bit host. Google-earth failed because
> of a couple of dangling symlinks. I did not capture the errors, but will if
> necessary.
> 
> ? Am I the only one with this issue?

Tested on both -stable and -current and it works just fine here

There are 2 dangling symlinks
chmod: cannot operate on dangling symlink
'./opt/google/earth/pro/google-earth-pro'
chmod: cannot operate on dangling symlink './usr/bin/google-earth-pro'
but they should be harmless and it shouldn't cause the build to break.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180305/71fb9154/attachment.asc>

From rshepard at appl-ecosys.com  Sun Mar  4 18:43:10 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 4 Mar 2018 10:43:10 -0800 (PST)
Subject: [Slackbuilds-users] Google-earth: dangling symlinks
In-Reply-To: <d96d8c96-3484-4a52-3091-854f4419d3d1@slackbuilds.org>
References: <alpine.LNX.2.20.1803041032100.11584@salmo.appl-ecosys.com>
 <d96d8c96-3484-4a52-3091-854f4419d3d1@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.1803041041430.11584@salmo.appl-ecosys.com>

On Mon, 5 Mar 2018, Willy Sudiarto Raharjo wrote:

> Tested on both -stable and -current and it works just fine here

Willy,

   I'll try again when the current list is finished.

> There are 2 dangling symlinks
> chmod: cannot operate on dangling symlink
> './opt/google/earth/pro/google-earth-pro'
> chmod: cannot operate on dangling symlink './usr/bin/google-earth-pro'
> but they should be harmless and it shouldn't cause the build to break.

   That looks like them. Here, 7.3.0.3847 is still present.

Thanks,

Rich

From willysr at slackbuilds.org  Sun Mar  4 18:47:03 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 5 Mar 2018 01:47:03 +0700
Subject: [Slackbuilds-users] Google-earth: dangling symlinks
In-Reply-To: <alpine.LNX.2.20.1803041041430.11584@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1803041032100.11584@salmo.appl-ecosys.com>
 <d96d8c96-3484-4a52-3091-854f4419d3d1@slackbuilds.org>
 <alpine.LNX.2.20.1803041041430.11584@salmo.appl-ecosys.com>
Message-ID: <121120ce-3933-b733-2dfa-1bc0d0a73b02@slackbuilds.org>

> ? That looks like them. Here, 7.3.0.3847 is still present.

Latest version is 7.3.1.4507
you should remove the old source first


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180305/9e8a762c/attachment.asc>

From rshepard at appl-ecosys.com  Sun Mar  4 19:05:01 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 4 Mar 2018 11:05:01 -0800 (PST)
Subject: [Slackbuilds-users] Google-earth: dangling symlinks [RESOLVED]
In-Reply-To: <121120ce-3933-b733-2dfa-1bc0d0a73b02@slackbuilds.org>
References: <alpine.LNX.2.20.1803041032100.11584@salmo.appl-ecosys.com>
 <d96d8c96-3484-4a52-3091-854f4419d3d1@slackbuilds.org>
 <alpine.LNX.2.20.1803041041430.11584@salmo.appl-ecosys.com>
 <121120ce-3933-b733-2dfa-1bc0d0a73b02@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.1803041103230.11584@salmo.appl-ecosys.com>

On Mon, 5 Mar 2018, Willy Sudiarto Raharjo wrote:

> Latest version is 7.3.1.4507
> you should remove the old source first

Willy,

   Apparently sbopkg did not remove the old source. I downloaded it (with a
new build script) and it worked just fine.

   Next time I'll upgrade separate from sbopkg.

Thanks,

Rich

From kingbeowulf at gmail.com  Mon Mar  5 01:35:17 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 4 Mar 2018 17:35:17 -0800
Subject: [Slackbuilds-users] Sage build still broken?
In-Reply-To: <9f22edf1-9724-f5f2-b607-ea110a917de5@slint.fr>
References: <CAFy1yb2=5=G_5LBWoVvJuwjebkCrJDm=q=zH4Kq7quj0JJhaSw@mail.gmail.com>
 <9f22edf1-9724-f5f2-b607-ea110a917de5@slint.fr>
Message-ID: <074755ab-89ae-b880-1581-310c549d7f35@gmail.com>

On 02/25/2018 11:02 AM, Didier Spaier wrote:
> Hello,
--snip---
> I just unpacked  a git archive then ran:
> 
> tar xf sage-8.1.tar.gz 
> cd sage-8.1
> ./configure | tee /tmp/config.LOG
> time make 2>/tmp/sageERR |tee /tmp/sageLOG
> 
> I attach config.LOG but not sageLOG, too heavy (25M), but here is hw it ends:
> 
>> Testing that Sage starts...
>> [2018-02-06 23:26:22] SageMath version 8.1, Release Date: 2017-12-07
>> This looks like the first time you are running Sage.
>> Cleaning up, do not interrupt this.
>> Done cleaning.
>> Yes, Sage starts.
>> make[2]?: on quitte le r?pertoire ??/tmp/sage-8.1/build/make??
>> make[1]?: on quitte le r?pertoire ??/tmp/sage-8.1/build/make??
>>
>> real	257m49.177s
>> user	262m42.133s
>> sys	11m29.261s
>> Sage build/upgrade complete!
>>
...snip
> 
> It worked here, that's all I know.
> 

pulling down the source, extracting to a directory, compiling as a
regular user in that directory and then running from that SAME directory
has always worked. That's what those knuckle heads want us to do. The
issue is getting the package built for installation to /opt/sage (or any
other $SAGEROOT).  This is what I have so far:

MACHINE A
1. download and extract to /tmp/SBo/sage-8.1
2. cd /tmp/SBo/sage-8.1, configure/compile
3. move bits to /tmp/SBo/package-sage and create package (/opt/sage tree)
4. installpkg /tmp/sage-8.1-x86_64-1_SBo.tgz
...
************************************************************************
It seems that you are attempting to run Sage from an unpacked source
...
(ok since doinst.sh runs sage as root to set new paths?)

5. login as regular user
cd /opt/sage
./sage

WHOO-HOO runs!!!

MACHINE B
1. copy over nfs to 2nd machine, same Slackware
2. installpkg /tmp/sage-8.1-x86_64-1_SBo.tgz
...
************************************************************************
It seems that you are attempting to run Sage from an unpacked source
...
3.
$ cd /opt/sage
$ ./sage
************************************************************************
It seems that you are attempting to run Sage from an unpacked source
tarball, but you have not compiled it yet (or maybe the build has not
finished). You should run `make` in the Sage root directory first.
If you did not intend to build Sage from source, you should download
a binary tarball instead. Read README.txt for more information.
************************************************************************
$

WTF????

THAT is the problem I can't seem to figure out or understand WTF sage is
doing. sage continues to run on MACHINE A (build box) even after
deleting the /tmp/SBo directories so its not like its looking at those.
The created package ONLY runs on MACHINE A where is was built.

-Ed






-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180304/f64c9727/attachment.asc>

From glenn.becker at gmail.com  Mon Mar  5 02:21:41 2018
From: glenn.becker at gmail.com (Glenn Becker)
Date: Sun, 4 Mar 2018 21:21:41 -0500
Subject: [Slackbuilds-users] packages still listed as mine
Message-ID: <CANCo2a0Ua+pFvDEo=F4yL5uiU7w2NCSdJ5g3YF7J-VU2ZhK+gw@mail.gmail.com>

Hi Folks --

I thought I had put up all my SBo packages for adoption, but there are some
for which I'm still listed as maintainer on Slackbuilds.org.

Would someone be interested in giving these a good home? There may come a
day when I can come back and be a maintainer, but it isn't the case now.

Thanks. Glenn

development/bsdiff
development/gprolog

games/nethack
games/golly

libraries/jbigkit

perl/perl-Test-Number-Delta
perl/perl-IO-HTML
perl/perl-x11-protocol
perl/perl-convert-UU
perl/perl-html-form
perl/perl-html-server-simple
perl/perl-perlIO-Layers
perl/perl-Astro-SunTime
perl/perl-goo-canvas
perl/perl-X10
perl/perl-Sub-Exporter-Progressive
perl/perl-Sys-Mmap
perl/perl-MIME-Lite
perl/perl-http-response-encoding
perl/perl-Device-SerialPort
perl/perl-Email-Date-Format
perl/perl-PHP-Serialization

system/splix

Glenn Becker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180304/d13c85f1/attachment.html>

From kingbeowulf at gmail.com  Mon Mar  5 03:22:32 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 4 Mar 2018 19:22:32 -0800
Subject: [Slackbuilds-users] RFC: patch for cfitsio for some astronomy
 software
In-Reply-To: <7548f0bc-7e56-e622-9805-03d19e446855@o2.pl>
References: <aafdbc0a-44b5-ce8f-457c-6ceed5aacee4@gmail.com>
 <7f63cb24-a73b-d30c-3a5f-82c3846f41f4@o2.pl>
 <2c2edd49-ca5b-f429-4711-5f21a362f124@gmail.com>
 <b2216a28-c48d-d278-dae3-f3385b76c44f@o2.pl>
 <7548f0bc-7e56-e622-9805-03d19e446855@o2.pl>
Message-ID: <c6c579bd-68bc-b0fe-4558-04b72f953a16@gmail.com>

On 03/03/2018 09:59 AM, Dominik Drobek wrote:
> Hi again,
> 
> Turns out you don't need to compile libindi to reproduce the issue. It's
> sufficient to simply attempt to compile anything with gcc using -lcfitsio.
> 
> The problem is in the way configure script in cfitsio handles
> --with-bzip2 option. It has an "optional" argument, which is supposed to
> be a path to where libbz2.so resides. Notice this snippet from
> configure.in:
> 
> # BZIP2 flags:
> if test "x$BZIP2_PATH" != x; then
> ?? CFLAGS="$CFLAGS -I${BZIP2_PATH}/include"
> ?? LDFLAGS="$LDFLAGS -L${BZIP2_PATH}/lib -lbz2"
> fi
> 
> If "optional" argument to --with-bzip2 is not supplied then $BZIP2_PATH
> is empty, and -lbz2 doesn't get added to LDFLAGS. If $BZIP2_PATH is not
> empty then -lbz2 will be added to LDFLAGS. Additionally, -L option will
> be added. This will not have a correct path in Slackware64 (because it
> always ends with "/lib"), but it actually doesn't matter, since system
> libbz2.so is in the default search location.
> 
> I prefer to fix this issue with my SlackBuild by simply removing
> --with-bzip2 option from ./configure. And I will do it this way, unless
> you will tell me that you need bzip2 support in cfitsio. :)
> 
> I naively assumed that simply adding --with-bzip2 will enable this
> feature without any further problems. Sorry for the inconvenience.
> 
> Regards,
> Dominik
> 

Dominik,

So far so good.  libindi compiled OK. I'm till sifting through
dependenices for the driver script.  Once that's working I'll see if it
all works!

Thanks
Ed


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180304/4342d590/attachment-0001.asc>

From dave at dawoodfall.net  Mon Mar  5 03:28:41 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Mon, 5 Mar 2018 03:28:41 +0000
Subject: [Slackbuilds-users] packages still listed as mine
In-Reply-To: <CANCo2a0Ua+pFvDEo=F4yL5uiU7w2NCSdJ5g3YF7J-VU2ZhK+gw@mail.gmail.com>
References: <CANCo2a0Ua+pFvDEo=F4yL5uiU7w2NCSdJ5g3YF7J-VU2ZhK+gw@mail.gmail.com>
Message-ID: <20180305032840.GF21983@raven>

On (04/03/18 21:21), Glenn Becker <glenn.becker at gmail.com> put forth the proposition:
>Hi Folks --
>
>I thought I had put up all my SBo packages for adoption, but there are some
>for which I'm still listed as maintainer on Slackbuilds.org.
>
>Would someone be interested in giving these a good home? There may come a
>day when I can come back and be a maintainer, but it isn't the case now.
>
>Thanks. Glenn
>
>development/bsdiff
>development/gprolog
>
>games/nethack

^ This one please.

Dave

>games/golly
>
>libraries/jbigkit
>
>perl/perl-Test-Number-Delta
>perl/perl-IO-HTML
>perl/perl-x11-protocol
>perl/perl-convert-UU
>perl/perl-html-form
>perl/perl-html-server-simple
>perl/perl-perlIO-Layers
>perl/perl-Astro-SunTime
>perl/perl-goo-canvas
>perl/perl-X10
>perl/perl-Sub-Exporter-Progressive
>perl/perl-Sys-Mmap
>perl/perl-MIME-Lite
>perl/perl-http-response-encoding
>perl/perl-Device-SerialPort
>perl/perl-Email-Date-Format
>perl/perl-PHP-Serialization
>
>system/splix
>
>Glenn Becker

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


From kingbeowulf at gmail.com  Mon Mar  5 07:24:51 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 4 Mar 2018 23:24:51 -0800
Subject: [Slackbuilds-users] RFC: patch for cfitsio for some astronomy
 software
In-Reply-To: <7548f0bc-7e56-e622-9805-03d19e446855@o2.pl>
References: <aafdbc0a-44b5-ce8f-457c-6ceed5aacee4@gmail.com>
 <7f63cb24-a73b-d30c-3a5f-82c3846f41f4@o2.pl>
 <2c2edd49-ca5b-f429-4711-5f21a362f124@gmail.com>
 <b2216a28-c48d-d278-dae3-f3385b76c44f@o2.pl>
 <7548f0bc-7e56-e622-9805-03d19e446855@o2.pl>
Message-ID: <7813695f-9d82-1009-f7a6-e821746ee724@gmail.com>

On 03/03/2018 09:59 AM, Dominik Drobek wrote:
> Hi again,
> 
> Turns out you don't need to compile libindi to reproduce the issue. It's
> sufficient to simply attempt to compile anything with gcc using -lcfitsio.
> 
--snip---
> 
> I prefer to fix this issue with my SlackBuild by simply removing
> --with-bzip2 option from ./configure. And I will do it this way, unless
> you will tell me that you need bzip2 support in cfitsio. :)
> 
> I naively assumed that simply adding --with-bzip2 will enable this
> feature without any further problems. Sorry for the inconvenience.
> 
> Regards,
> Dominik
> 

Dominik,

success.  with your new cfitsio, and a few other new and SBo deps, I
have libindi running and working via a indi client to connect to my ASI
camera and collect FITS and SER data.  I left "export LDFLAGS="-lbz2" in
my script just in case.'.can't hurt.

I'll post the indi stuff soonest.

Unfortunately, 14.2 Kstars is too old, so I'll have to wait until 15.0
and KDE 5.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180304/70e5763a/attachment.asc>

From chris.willing at linux.com  Mon Mar  5 09:24:33 2018
From: chris.willing at linux.com (Christoph Willing)
Date: Mon, 5 Mar 2018 19:24:33 +1000
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <CAC8E-U_J9K7D-bhuv3Q6Zs=tNo-RPyOfCo+H+XkBzdR5-YPRNw@mail.gmail.com>
References: <CAC8E-U_J9K7D-bhuv3Q6Zs=tNo-RPyOfCo+H+XkBzdR5-YPRNw@mail.gmail.com>
Message-ID: <d70a6267-517b-41a5-6f6a-ce917d5de8ec@linux.com>

On 05/02/18 00:25, Andr? Barboza wrote:

> audio/opencore-amr

I'll take this one.

chris

From yalhcru at gmail.com  Mon Mar  5 09:28:46 2018
From: yalhcru at gmail.com (B Watson)
Date: Mon, 5 Mar 2018 04:28:46 -0500
Subject: [Slackbuilds-users] packages still listed as mine
In-Reply-To: <CANCo2a0Ua+pFvDEo=F4yL5uiU7w2NCSdJ5g3YF7J-VU2ZhK+gw@mail.gmail.com>
References: <CANCo2a0Ua+pFvDEo=F4yL5uiU7w2NCSdJ5g3YF7J-VU2ZhK+gw@mail.gmail.com>
Message-ID: <CAN1hMuBy3Q8=--TsbESQPzAPGfA38ZNffR8s6Cpknkg2Jh52aw@mail.gmail.com>

On 3/4/18, Glenn Becker <glenn.becker at gmail.com> wrote:
>
> development/bsdiff
> games/golly

I'll take these two.

> libraries/jbigkit

Whoever takes splix should take jbigkit. I don't want splix as I haven't
got any of the printers it supports... but if nobody steps up & takes
splix, I'll take jbigkit rather than see it removed from the repo (I've
used it in one of my personal half-finished projects, which may one day
be finished).

I may take some of the perl modules, if nobody else wants them, but
please don't anybody save them for me.

From falsetti at clansco.org  Mon Mar  5 10:50:51 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Mon, 5 Mar 2018 11:50:51 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
Message-ID: <20180305115051.e18e0a4fc5a272e865d8daa3@clansco.org>

Hi,
an idea of what I did wrong ?

patching file qwtfunctions.pri
Info: creating stash file /tmp/SBo/qwt-6.1.3/build/.qmake.stash
cd src/ && ( test -e Makefile || /usr/bin/qmake-qt5 /tmp/SBo/qwt-6.1.3/src/src.pro LIBDIRSUFFIX= -o Makefile ) && make -f Makefile 
make[1]?: on entre dans le r?pertoire ??/tmp/SBo/qwt-6.1.3/build/src??
compiling ../../src/qwt_abstract_scale_draw.cpp
In file included from ../../src/qwt_global.h:13:0,
                 from ../../src/qwt_abstract_scale_draw.h:13,
                 from ../../src/qwt_abstract_scale_draw.cpp:10:
/usr/include/qt5/QtCore/qglobal.h:1113:4: erreur?: #error "You must build your code with position independent code if Qt was built with -reduce-relocations. " "Compile your code with -fPIC (-fPIE is not enough)."
 #  error "You must build your code with position independent code if Qt was built with -r
    ^



On Sun, 04 Mar 2018 07:41:42 -0800
Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:

> If anyone is interested in running QGIS 3.0.0 on Slackware 14.2, I have 
> working build scripts available. I would like feedback and bug reports, of 
> course, but I'm also interested in hearing how much demand there is for QGIS 3 
> to be an official SlackBuild.
> 
> Instructions and new SlackBuilds are located here https://github.com/bosth/
> qgis3-slackbuild (this is still a work in progress so not everything is 
> intended to be ready for submission). The end product won't be compatible with 
> an existing QGIS 2.x installation.
> 
> For the missing but optional Python 3 modules I mentioned in the README, you 
> can just use pip3 install $NAME --user to install them until we have proper 
> Python 3 SlackBuilds. I believe it is just psycopg2, owslib and Jinja2 that 
> need this treatment.
> 
> Ben
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From matteo.bernardini at gmail.com  Mon Mar  5 11:18:18 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 5 Mar 2018 12:18:18 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <20180305115051.e18e0a4fc5a272e865d8daa3@clansco.org>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305115051.e18e0a4fc5a272e865d8daa3@clansco.org>
Message-ID: <CAPsDuS6wPMRY+WxRGskdbDCr3EZv=iXb3LQzKWFpm_aLxaTrjA@mail.gmail.com>

2018-03-05 11:50 GMT+01:00 Fr?d?ric Falsetti <falsetti at clansco.org>:
> Hi,
> an idea of what I did wrong ?
>
> patching file qwtfunctions.pri
> Info: creating stash file /tmp/SBo/qwt-6.1.3/build/.qmake.stash
> cd src/ && ( test -e Makefile || /usr/bin/qmake-qt5 /tmp/SBo/qwt-6.1.3/src/src.pro LIBDIRSUFFIX= -o Makefile ) && make -f Makefile
> make[1] : on entre dans le r?pertoire ? /tmp/SBo/qwt-6.1.3/build/src ?
> compiling ../../src/qwt_abstract_scale_draw.cpp
> In file included from ../../src/qwt_global.h:13:0,
>                  from ../../src/qwt_abstract_scale_draw.h:13,
>                  from ../../src/qwt_abstract_scale_draw.cpp:10:
> /usr/include/qt5/QtCore/qglobal.h:1113:4: erreur : #error "You must build your code with position independent code if Qt was built with -reduce-relocations. " "Compile your code with -fPIC (-fPIE is not enough)."
>  #  error "You must build your code with position independent code if Qt was built with -r
>     ^

Hi Frederic,

which version of qt5 do you have installed in your system?

From falsetti at clansco.org  Mon Mar  5 11:30:19 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Mon, 5 Mar 2018 12:30:19 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <CAPsDuS6wPMRY+WxRGskdbDCr3EZv=iXb3LQzKWFpm_aLxaTrjA@mail.gmail.com>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305115051.e18e0a4fc5a272e865d8daa3@clansco.org>
 <CAPsDuS6wPMRY+WxRGskdbDCr3EZv=iXb3LQzKWFpm_aLxaTrjA@mail.gmail.com>
Message-ID: <20180305123019.2e21555cec981267b52e1efa@clansco.org>

On Mon, 5 Mar 2018 12:18:18 +0100
Matteo Bernardini <matteo.bernardini at gmail.com> wrote:


> 
> Hi Frederic,
> 
> which version of qt5 do you have installed in your system?
qt5-5.7.1-i586-1_SBo
on 32-bit machine

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

From slackbuilds at jaxartes.net  Mon Mar  5 15:28:41 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Mon, 05 Mar 2018 07:28:41 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <CANBHt+OPhWg8z4veuK73k32kBXb7ww_KQ42Tjy1OO0=nnutCKw@mail.gmail.com>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <CANBHt+OPhWg8z4veuK73k32kBXb7ww_KQ42Tjy1OO0=nnutCKw@mail.gmail.com>
Message-ID: <1800690.M97lFvIze6@wintermute.sprawl.net>

On Sunday, 4 March 2018 08:46:28 PST Konrad J Hambrick wrote:
> Wow Ben.
> 
> I checked out QGIS' Home Page:  https://qgis.org/en/site/
> 
> It is a very impressive piece of work !
> 
> Speaking of work, I wish I had time to test your qgis-3.SlackBuild but I've
> got my hands full right now.

If you do get a chance, let me know how it goes.
 
> We do have a project coming up later this summer where QGIS might be a
> great way to display tax jurisdictions in certain US Locations.
> 
> Anyhow ... thanks for turning me on to QGIS and good luck with your
> qgis-3.SlackBuild Project !

Thanks!

> -- kjh
> 
> On Sun, Mar 4, 2018 at 9:41 AM, Benjamin Trigona-Harany <
> 
> slackbuilds at jaxartes.net> wrote:
> > If anyone is interested in running QGIS 3.0.0 on Slackware 14.2, I have
> > working build scripts available. I would like feedback and bug reports, of
> > course, but I'm also interested in hearing how much demand there is for
> > QGIS 3
> > to be an official SlackBuild.
> > 
> > Instructions and new SlackBuilds are located here
> > https://github.com/bosth/
> > qgis3-slackbuild (this is still a work in progress so not everything is
> > intended to be ready for submission). The end product won't be compatible
> > with
> > an existing QGIS 2.x installation.
> > 
> > For the missing but optional Python 3 modules I mentioned in the README,
> > you
> > can just use pip3 install $NAME --user to install them until we have
> > proper
> > Python 3 SlackBuilds. I believe it is just psycopg2, owslib and Jinja2
> > that
> > need this treatment.
> > 
> > Ben
> > 
> > 
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/





From slackbuilds at jaxartes.net  Mon Mar  5 15:33:10 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Mon, 05 Mar 2018 07:33:10 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <20180305115051.e18e0a4fc5a272e865d8daa3@clansco.org>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305115051.e18e0a4fc5a272e865d8daa3@clansco.org>
Message-ID: <27663767.FNhhsf7Fh5@wintermute.sprawl.net>

On Monday, 5 March 2018 02:50:51 PST Fr?d?ric Falsetti wrote:
> Hi,
> an idea of what I did wrong ?
> 
> patching file qwtfunctions.pri
> Info: creating stash file /tmp/SBo/qwt-6.1.3/build/.qmake.stash
> cd src/ && ( test -e Makefile || /usr/bin/qmake-qt5
> /tmp/SBo/qwt-6.1.3/src/src.pro LIBDIRSUFFIX= -o Makefile ) && make -f
> Makefile make[1] : on entre dans le r?pertoire
> ? /tmp/SBo/qwt-6.1.3/build/src ? compiling
> ../../src/qwt_abstract_scale_draw.cpp
> In file included from ../../src/qwt_global.h:13:0,
>                  from ../../src/qwt_abstract_scale_draw.h:13,
>                  from ../../src/qwt_abstract_scale_draw.cpp:10:
> /usr/include/qt5/QtCore/qglobal.h:1113:4: erreur : #error "You must build
> your code with position independent code if Qt was built with
> -reduce-relocations. " "Compile your code with -fPIC (-fPIE is not
> enough)." #  error "You must build your code with position independent code
> if Qt was built with -r ^

Hi Fr?d?ric, I should have mentioned that I only tested on Slackware64, so 
thanks for checking the process on 32-bit Slackware.

Could you try adding -fPIC to line 82 of the SlackBuild so it looks like this:

CXXFLAGS+="$SLKCFLAGS -std=c++11 -fPIC"

The error message suggests that this is the issue.

> On Sun, 04 Mar 2018 07:41:42 -0800
> 
> Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:
> > If anyone is interested in running QGIS 3.0.0 on Slackware 14.2, I have
> > working build scripts available. I would like feedback and bug reports, of
> > course, but I'm also interested in hearing how much demand there is for
> > QGIS 3 to be an official SlackBuild.
> > 
> > Instructions and new SlackBuilds are located here
> > https://github.com/bosth/
> > qgis3-slackbuild (this is still a work in progress so not everything is
> > intended to be ready for submission). The end product won't be compatible
> > with an existing QGIS 2.x installation.
> > 
> > For the missing but optional Python 3 modules I mentioned in the README,
> > you can just use pip3 install $NAME --user to install them until we have
> > proper Python 3 SlackBuilds. I believe it is just psycopg2, owslib and
> > Jinja2 that need this treatment.
> > 
> > Ben
> > 
> > 
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/





From ewfalor at gmail.com  Mon Mar  5 15:36:06 2018
From: ewfalor at gmail.com (Erik Falor)
Date: Mon, 5 Mar 2018 08:36:06 -0700
Subject: [Slackbuilds-users] packages still listed as mine
In-Reply-To: <CANCo2a0Ua+pFvDEo=F4yL5uiU7w2NCSdJ5g3YF7J-VU2ZhK+gw@mail.gmail.com>
References: <CANCo2a0Ua+pFvDEo=F4yL5uiU7w2NCSdJ5g3YF7J-VU2ZhK+gw@mail.gmail.com>
Message-ID: <20180305153606.2c54ylsafthocleh@viking2.falor>

On Sun, Mar 04, 2018 at 09:21:41PM -0500, Glenn Becker wrote:

>    development/gprolog

I'll take gprolog


>    games/nethack

Oops, looks like I snoozed too long to get this one :'(


>    Glenn Becker

Thanks for all of your hard work through the years, Glenn.

-- 
Erik Falor
Registered Linux User #445632                    http://unnovative.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180305/1f94a0e7/attachment.asc>

From falsetti at clansco.org  Mon Mar  5 17:23:41 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Mon, 5 Mar 2018 18:23:41 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <27663767.FNhhsf7Fh5@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305115051.e18e0a4fc5a272e865d8daa3@clansco.org>
 <27663767.FNhhsf7Fh5@wintermute.sprawl.net>
Message-ID: <20180305182341.ae6e4f7c6fb7565f0b6da7cc@clansco.org>

On Mon, 05 Mar 2018 07:33:10 -0800
Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:

> 
> Hi Fr?d?ric, I should have mentioned that I only tested on Slackware64, so 
> thanks for checking the process on 32-bit Slackware.
> 
> Could you try adding -fPIC to line 82 of the SlackBuild so it looks like this:
> 
> CXXFLAGS+="$SLKCFLAGS -std=c++11 -fPIC"
> 
> The error message suggests that this is the issue.
> 

many thanks, it works fine !

attention:
https://github.com/bosth/qgis3-slackbuild/blob/master/qgis3/qgis3.info :
DOWNLOAD="http://qgis.org/downloads/qgis-2.18.16.tar.bz2"

;)






From falsetti at clansco.org  Mon Mar  5 17:31:38 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Mon, 5 Mar 2018 18:31:38 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <1800690.M97lFvIze6@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <CANBHt+OPhWg8z4veuK73k32kBXb7ww_KQ42Tjy1OO0=nnutCKw@mail.gmail.com>
 <1800690.M97lFvIze6@wintermute.sprawl.net>
Message-ID: <20180305183138.b0b42669a5b3722eee0ce6dc@clansco.org>

qca-qt5.info
DOWNLOAD="https://github.com/KDE/qca/archive/v2.1.3.tar.gz"

qca-qt5.SlackBuild
SRCNAM=qca
PRGNAM=$SRCNAM-qt5
VERSION=${VERSION:-2.1.3}

--> mv v2.1.3.tar.gz qca-2.1.3.tar.gz

On Mon, 05 Mar 2018 07:28:41 -0800
Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:

> On Sunday, 4 March 2018 08:46:28 PST Konrad J Hambrick wrote:
> > Wow Ben.
> > 
> > I checked out QGIS' Home Page:  https://qgis.org/en/site/
> > 
> > It is a very impressive piece of work !
> > 
> > Speaking of work, I wish I had time to test your qgis-3.SlackBuild but I've
> > got my hands full right now.
> 
> If you do get a chance, let me know how it goes.
>  
> > We do have a project coming up later this summer where QGIS might be a
> > great way to display tax jurisdictions in certain US Locations.
> > 
> > Anyhow ... thanks for turning me on to QGIS and good luck with your
> > qgis-3.SlackBuild Project !
> 
> Thanks!
> 
> > -- kjh
> > 
> > On Sun, Mar 4, 2018 at 9:41 AM, Benjamin Trigona-Harany <
> > 
> > slackbuilds at jaxartes.net> wrote:
> > > If anyone is interested in running QGIS 3.0.0 on Slackware 14.2, I have
> > > working build scripts available. I would like feedback and bug reports, of
> > > course, but I'm also interested in hearing how much demand there is for
> > > QGIS 3
> > > to be an official SlackBuild.
> > > 
> > > Instructions and new SlackBuilds are located here
> > > https://github.com/bosth/
> > > qgis3-slackbuild (this is still a work in progress so not everything is
> > > intended to be ready for submission). The end product won't be compatible
> > > with
> > > an existing QGIS 2.x installation.
> > > 
> > > For the missing but optional Python 3 modules I mentioned in the README,
> > > you
> > > can just use pip3 install $NAME --user to install them until we have
> > > proper
> > > Python 3 SlackBuilds. I believe it is just psycopg2, owslib and Jinja2
> > > that
> > > need this treatment.
> > > 
> > > Ben
> > > 
> > > 
> > > _______________________________________________
> > > SlackBuilds-users mailing list
> > > SlackBuilds-users at slackbuilds.org
> > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > > FAQ - https://slackbuilds.org/faq/
> 
> 
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From yalhcru at gmail.com  Mon Mar  5 18:25:21 2018
From: yalhcru at gmail.com (B Watson)
Date: Mon, 5 Mar 2018 13:25:21 -0500
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <20180305183138.b0b42669a5b3722eee0ce6dc@clansco.org>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <CANBHt+OPhWg8z4veuK73k32kBXb7ww_KQ42Tjy1OO0=nnutCKw@mail.gmail.com>
 <1800690.M97lFvIze6@wintermute.sprawl.net>
 <20180305183138.b0b42669a5b3722eee0ce6dc@clansco.org>
Message-ID: <CAN1hMuD2ZENe_Mfop6mw4_TC+jKNmD7WOBNyJ53oRRDfFGYq8A@mail.gmail.com>

On 3/5/18, Fr?d?ric Falsetti <falsetti at clansco.org> wrote:

> DOWNLOAD="https://github.com/KDE/qca/archive/v2.1.3.tar.gz"

No!

Use this URL:

https://github.com/KDE/qca/archive/v2.1.3/qca-2.1.3.tar.gz

This will result in the downloaded file being called qca-2.1.3.tar.gz
regardless of whether content-disposition is supported by the client or
not. Makes life easier for everyone.

From ekinakoglu at gmail.com  Mon Mar  5 18:41:50 2018
From: ekinakoglu at gmail.com (Ekin Akoglu)
Date: Mon, 5 Mar 2018 21:41:50 +0300
Subject: [Slackbuilds-users] Keepassxc MD5SUM does not match
Message-ID: <94376cf9-6789-c99c-d4f4-b8c77bf315af@gmail.com>

Hi,

This is what I get from md5sum check:

md5sum <<<"1dba769f0eb1303ef3fbd873acd81901 keepassxc-2.3.0-src.tar.xz"
3a23e743875536ebcb3d8ba7dc1fff44? -

Is there something wrong?

Best,

Ekin


From ekinakoglu at gmail.com  Mon Mar  5 18:44:35 2018
From: ekinakoglu at gmail.com (Ekin Akoglu)
Date: Mon, 5 Mar 2018 21:44:35 +0300
Subject: [Slackbuilds-users] smplayer MD5SUM does not match
Message-ID: <994dcf3e-909b-5e75-59c5-62c92caaa682@gmail.com>

Hi,

This is what I get from md5sum check:

md5sum <<<"a9627ca9e0011a422f5255be0173f271 smplayer-18.2.2.tar.bz2"
8d32dcea7c78aa17c05d9d65c02aef50? -

Could there be something wrong?

Best,

Ekin


From willysr at slackbuilds.org  Mon Mar  5 18:54:37 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 6 Mar 2018 01:54:37 +0700
Subject: [Slackbuilds-users] Keepassxc MD5SUM does not match
In-Reply-To: <94376cf9-6789-c99c-d4f4-b8c77bf315af@gmail.com>
References: <94376cf9-6789-c99c-d4f4-b8c77bf315af@gmail.com>
Message-ID: <e0c9a44d-e39e-4ee7-ad6f-a94374340a26@slackbuilds.org>

> This is what I get from md5sum check:
> 
> md5sum <<<"1dba769f0eb1303ef3fbd873acd81901 keepassxc-2.3.0-src.tar.xz"
> 3a23e743875536ebcb3d8ba7dc1fff44? -
> 
> Is there something wrong?

Hi Ekin

It has been fixed in GIT
https://git.slackbuilds.org/slackbuilds/commit/?id=0eb028b08


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180306/e1961139/attachment-0001.asc>

From willysr at slackbuilds.org  Mon Mar  5 18:56:57 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 6 Mar 2018 01:56:57 +0700
Subject: [Slackbuilds-users] smplayer MD5SUM does not match
In-Reply-To: <994dcf3e-909b-5e75-59c5-62c92caaa682@gmail.com>
References: <994dcf3e-909b-5e75-59c5-62c92caaa682@gmail.com>
Message-ID: <69986348-233f-fcc0-4a6c-e002807affbf@slackbuilds.org>

> This is what I get from md5sum check:
> 
> md5sum <<<"a9627ca9e0011a422f5255be0173f271 smplayer-18.2.2.tar.bz2"
> 8d32dcea7c78aa17c05d9d65c02aef50? -
> 
> Could there be something wrong?

I checked and it gives me a correct checksum
md5sum smplayer-18.2.2.tar.bz2
a9627ca9e0011a422f5255be0173f271  smplayer-18.2.2.tar.bz2

perhaps it's just an after-effect from SF maintenance period.
Try to redownload the source again from different mirrors


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180306/1bb372bc/attachment.asc>

From ekinakoglu at gmail.com  Mon Mar  5 18:59:42 2018
From: ekinakoglu at gmail.com (Ekin Akoglu)
Date: Mon, 5 Mar 2018 21:59:42 +0300
Subject: [Slackbuilds-users] smplayer MD5SUM does not match
In-Reply-To: <994dcf3e-909b-5e75-59c5-62c92caaa682@gmail.com>
References: <994dcf3e-909b-5e75-59c5-62c92caaa682@gmail.com>
Message-ID: <7778453d-12fb-faa6-888c-251185256158@gmail.com>

Sorry, this is totally my stupid mistake, I excluded the "-c" switch 
that is why I got a mismatch.

Please excuse me.

Best,

Ekin


On 05/03/18 21:44, Ekin Akoglu wrote:
> Hi,
>
> This is what I get from md5sum check:
>
> md5sum <<<"a9627ca9e0011a422f5255be0173f271 smplayer-18.2.2.tar.bz2"
> 8d32dcea7c78aa17c05d9d65c02aef50? -
>
> Could there be something wrong?
>
> Best,
>
> Ekin
>


From willysr at slackbuilds.org  Mon Mar  5 19:30:22 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 6 Mar 2018 02:30:22 +0700
Subject: [Slackbuilds-users] Updates - 20180305.1
Message-ID: <d49e204e-c888-98b8-b12e-9c8f4a594754@slackbuilds.org>

Hi,

Following last week's update, here's another big batch which mirrors
some of the sources into Ponce's personal repository to provide more
alternative for hosting the sources. It's almost 300 commits so it has
to be pushed forward before it gets bigger.

We also have some updates such as hhvm, opencv, tor, clamav, and
teamviewer. As for teamviewer, it seems that upstream have finally fixed
the panel issue in GNOME-based DE.

PS: there's a typo in one of the update (ne). It's missing a closing "'"
in the DOWNLOAD line. It has been fixed in the tarball, but for those
who are using third party tools you will see some warning/errors on that
part. Sorry for that.

Mon Mar  5 19:05:12 UTC 2018
academic/artha: Mirror download url.
academic/avogadro: Update download url.
academic/galculator: Fix download url.
academic/paml: Mirror download url.
academic/qtoctave: Mirror download url.
academic/tkgate: Update download url.
accessibility/svkbd: Mirror download url.
audio/clyrics: Updated for version 0.10.
audio/fmit: Mirror download url.
audio/mhwaveedit: Mirror download url.
audio/nero-aac: Mirror download url.
audio/ngjackspa: Mirror download url.
audio/playmp3list: Fix download + switch to i586.
audio/rplay: Update download url.
audio/sfarkxtc: Mirror download url.
audio/snd: Mirror download url.
audio/specimen: Update download url.
desktop/ClipboardViewer: Update download url.
desktop/XDecorations: Mirror download url.
desktop/Xfce-Theme-Manager: Mirror download url.
desktop/afterstep: Update download url.
desktop/cryptkeeper: Removed (Abandoned upstream).
desktop/crystal: Update download url.
desktop/dunst: Fix source url.
desktop/faenza-icon-theme: Mirror download url.
desktop/gntp-send: Update download url.
desktop/gtk-nodoka-engine: Mirror download url.
desktop/kde44-oxygen-molecule: Update download url.
desktop/numix-icon-theme: Updated for version 20171225.
desktop/numix-sx-theme: Update download url.
desktop/oranchelo-icon-theme: Updated for version 0.7.6.
desktop/pekwm: Update download url.
desktop/plasma-adjustable-clock: Update download url.
desktop/plasma-eyasdp: Update download url.
desktop/qtile: Updated for version 0.11.1.
desktop/quickaccess: Update download url.
desktop/rootactions_servicemenu: Update download url.
desktop/skulpture: Update download url.
desktop/sun: Updated for version 1.2.2.
desktop/xtrascreenhacks: Mirror download url.
development/Arduino: Mirror download url.
development/bas: Updated for version 2.4.
development/bluefish: Update download url.
development/chibi-scheme: Updated for version 0.8.
development/cim: Update download url.
development/cudnn: Update download url.
development/d-tools: Updated for version 2.079.0
development/dbeaver: Mirror download url.
development/dmd: Updated for version 2.079.0
development/ebe: Mirror download url.
development/gecode: Mirror download url.
development/git-lfs: Updated for version 2.4.0.
development/global: Updated for version 6.6.2.
development/gnome-inform7: Update download url.
development/gprolog: New maintainer.
development/gsoap: Mirror download url.
development/hhvm: Updated for version 3.24.3
development/kforth: Update download url.
development/kotlin: Updated for version 1.2.30.
development/libxbgi: Update download url.
development/likepython: Update download url.
development/lmdb: Mirror download url.
development/mcu8051ide: Update download url.
development/monkey-studio: Mirror download url.
development/ne: Update download url.
development/nedit: Update download url.
development/newlisp: Update download url.
development/omake: Mirror download url.
development/omniORBpy: Update download url.
development/openjdk6: Mirror download url.
development/pasdoc: Update download url.
development/phpDocumentor: Update download url.
development/qconf: Update download url.
development/regina-rexx: Update download url.
development/sbcl: Updated for version 1.4.5.
development/sdcc: Update download url.
development/shed: Update download url.
development/smartgit: Mirror download url.
development/smartsvn: Update download url.
development/splint: Update download url.
development/sqliteman: Update download url.
development/stgit: Mirror download url.
development/vile: Update download url.
development/xemacs: Mirror download url.
development/xvile: Update download url.
development/zope.testing: Switch to https.
games/abe: Update download url.
games/bloodcm: Mirror download url.
games/cosmic_assault: Update download url.
games/doom_shareware_data: Update download url.
games/galaxyv2: Mirror download url.
games/gens-gs: Update download url.
games/gnonograms: Update download url.
games/heretic_shareware_data: Update download url.
games/hexen_demo_data: Update download url.
games/jackhammer: Mirror download url.
games/javacpc: Update download url.
games/larn: Update download url.
games/lmpc: Update download url.
games/mrboom: Updated for version 4.4.
games/openjazz: Update download url.
games/quake3_shareware_data: Update download url.
games/quake_shareware_data: Update download url.
games/roadfighter: Update download url.
games/talkfilters: Update download url.
games/transfusion: Update download url.
games/typhoon_2001: Update download url.
games/warmux: Mirror download url.
games/warsow: Mirror download url.
gis/josm: Update download url.
gis/navit: Update download url.
gis/osgEarth: Mirror download url.
gis/proj: Updated for version 5.0.0.
gis/qgis: Updated for version 2.18.17.
graphics/dcraw: Update download url.
graphics/draftsight: Update download url.
graphics/dxftoqet: Update download url.
graphics/fbpic: Mirror download url.
graphics/fbv: Update download url.
graphics/feh: Updated for version 2.25.
graphics/fotoxx: Mirror download url.
graphics/openclipart: Update download url.
graphics/raw-thumbnailer: Mirror download url.
graphics/textext: Update download url.
graphics/tintii: Update download url.
graphics/urbanlightscape: Update download url.
graphics/yed: Mirror download url.
ham/7plus: Update download url.
ham/chirp: Update download url.
ham/cwstation: Mirror download url.
ham/demorse: Mirror download url.
ham/direwolf: Mirror download url.
ham/fldigi: Update download url.
ham/flrig: Update download url.
ham/xdemorse: Mirror download url.
ham/xwxapt: Mirror download url.
libraries/FormEncode: Update download url.
libraries/Geraldo: Update download url.
libraries/activemq-cpp: Update download url.
libraries/alglib: Update download url.
libraries/cdk: Update download url.
libraries/cfitsio: Updated for version 3.43.
libraries/gtk-aurora-engine: Fixed DOWNLOAD.
libraries/imlib2: Updated for version 1.5.0.
libraries/libAfterImage: Mirror download url.
libraries/libbde: Update download url.
libraries/libcitadel: Update download url.
libraries/libeot: Minor cleanup.
libraries/libfvde: Update download url.
libraries/libfwnt: Update download url.
libraries/libfwsi: Update download url.
libraries/liblnk: Update download url.
libraries/libmsiecf: Update download url.
libraries/libmspub: Updated for version 0.1.4.
libraries/libolecf: Update download url.
libraries/liboop: Update download url.
libraries/liborcus: Updated for version 0.13.4.
libraries/libpaper: Update download url.
libraries/libsmdev: Update download url.
libraries/libsmraw: Update download url.
libraries/libtorrent-rasterbar: Update for qbittorrent-qt5.
libraries/libvshadow: Update download url.
libraries/mariadb_client: Update download url.
libraries/mujs: Update download url.
libraries/opencv: Updated for version 3.4.1
libraries/p4api: Update download url.
libraries/progressbar: Switch to https.
libraries/xmltooling: Update download url.
libraries/xview: Mirror download url.
libraries/zita-resampler: Update download url.
misc/BISP: Update download url.
misc/ardesia: Mirror download url.
misc/bdf2psf: Mirror download url.
misc/ccze: Update download url.
misc/floating-IPS: Mirror download url.
misc/nfoview: Mirror download url.
misc/tegaki-zinnia-japanese: Mirror download url.
multimedia/QMPlay2: Updated for version 18.03.02.
multimedia/a2jmidid: Mirror download url.
multimedia/flvtool2: Mirror download url.
multimedia/gmidimonitor: Mirror download url.
multimedia/huludesktop: Mirror download url.
multimedia/makemkv: Mirror download url.
multimedia/opera-developer-ffmpeg-codecs: Updated for v65.0.3325.53.
multimedia/qsampler: Mirror download url.
multimedia/ripit: Mirror download url.
multimedia/subtitleeditor: Mirror download url.
network/Electrum-DASH: Mirror download url.
network/PaleMoon: Updated for version 27.8.0.
network/arpwatch: Mirror download url.
network/bird: Mirror download url.
network/boxcryptor: Mirror download url.
network/btsync: Removed (maintainer's request).
network/cadaver: Mirror download url.
network/cicb: Mirror download url.
network/clive: Mirror download url.
network/dnstracer: Mirror download url.
network/dropbox: Mirror download url.
network/easyrsa: Updated for version 3.0.4.
network/emacs-w3m: Mirror download url.
network/firehol: Mirror download url.
network/fping6: Mirror download url.
network/freeradius-server: Mirror download url.
network/googler: Updated for version 3.5.
network/hostsblock: Mirror download url.
network/httping: Mirror download url.
network/icecat: Updated for version 52.6.0.
network/kasp_updater: Mirror download url.
network/kcm_ufw: Mirror download url.
network/leafnode: Mirror download url.
network/mod_chroot: Mirror download url.
network/netperf: Mirror download url.
network/opensmtpd: Fix permissions.
network/opera-developer: Updated for version 53.0.2880.0.
network/pidgin-birthday-reminder: Mirror download url.
network/pidgin-visnotes: Mirror download url.
network/qbittorrent-qt5: Updated for version 4.0.4.
network/seahub: Mirror download url.
network/shadowsocks-libev: Added (secure socks5 proxy).
network/teamviewer: Updated for version 13.0.9865.
network/tor: Updated for version 0.3.2.10.
network/varnish: Mirror download url.
network/vcspull: Mirror download url.
network/yandex-browser-beta: Updated for version 18.1.1.952.
office/JabRef: Mirror download url.
office/hevea: Mirror download url.
office/kate-latex-plugin: Mirror download url.
office/keepassxc: .info fixes.
office/keepnote: Mirror download url.
office/sc-im: Updated for version 0.7.0.
office/teapot: Mirror download url.
office/trelby: Mirror download url.
office/verbiste: Mirror download url.
office/xmind: Mirror download url.
perl/libpurple-kwallet-plugin: Mirror download url.
perl/perl-DBD-Pg: Mirror download url.
perl/perl-Date-Manip: Updated for version 6.70.
perl/perl-DateTime-Format-Strptime: Mirror download url.
perl/perl-IO-Socket-INET6: Mirror download url.
perl/perl-Log-Dispatch: Mirror download url.
perl/perl-Test-Harness: Updated for version 3.41.
python/dfdatetime: Mirror download url.
python/dfwinreg: Mirror download url.
python/dhcpy6d: Mirror download url.
python/p4python: Mirror download url.
python/pychart: Mirror download url.
python/python-neovim: Updated for version 0.2.1.
python/python-notify2: Updated for version 0.3.1.
python/python-suds: Mirror download url.
python/python-yenc: Mirror download url.
python/python3-augeas: Mirror download url.
ruby/rubygem-mail: Updated for version 2.7.0.
system/Iosevka: Updated for version 1.14.1.
system/clamav: Updated for version 0.99.4.
system/ddrescue-gui: Updated for version 1.7.2.
system/eaglemode: Mirror download url.
system/efitools: Mirror download url.
system/emelfm2: Mirror download url.
system/epson-inkjet-printer-escpr: Mirror download url.
system/exomizer: Mirror download url.
system/kafka: Mirror download url.
system/microcode_ctl: Mirror download url.
system/mkslack: Updated for version 5.2.
system/nanum-coding-fonts-ttf: Mirror download url.
system/pce: Mirror download url.
system/pcsc-tools: Mirror download url.
system/rfdump: Mirror download url.
system/slackchlog: Mirror download url.
system/slackyd: Mirror download url.
system/smbldap-tools: Mirror download url.
system/sysdig: Updated for version 0.20.0
system/targetcli-fb: Mirror download url.
system/tkdvd: Mirror download url.
system/ttf-arphic-uming: Mirror download url.
system/ttmkfdir: Mirror download url.
system/virt-viewer: Mirror download url.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180306/067ec079/attachment.asc>

From falsetti at clansco.org  Mon Mar  5 19:32:45 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Mon, 5 Mar 2018 20:32:45 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
Message-ID: <20180305203245.17ffb57ccbc5152c02fede0b@clansco.org>

QScintilla-qt5 configure fails with:

install -m 755 -p libqscintillaplugin.so /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillaplugin.so
strip --strip-unneeded /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillaplugin.so
/tmp/SBo/QScintilla_gpl-2.10.2
Usage: python configure.py [options]

configure.py: error: '/usr/bin/python-sip' is not an executable



I have 
/usr/bin/python3-sip from python3-sip-4.19.6-i586-1_SBo


From slackbuilds at jaxartes.net  Mon Mar  5 20:37:08 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Mon, 05 Mar 2018 12:37:08 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <20180305203245.17ffb57ccbc5152c02fede0b@clansco.org>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305203245.17ffb57ccbc5152c02fede0b@clansco.org>
Message-ID: <3114364.sqAN6ORQRt@wintermute.sprawl.net>

On Monday, 5 March 2018 11:32:45 PST Fr?d?ric Falsetti wrote:
> QScintilla-qt5 configure fails with:
> 
> install -m 755 -p libqscintillaplugin.so
> /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillap
> lugin.so strip --strip-unneeded
> /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillap
> lugin.so /tmp/SBo/QScintilla_gpl-2.10.2
> Usage: python configure.py [options]
> 
> configure.py: error: '/usr/bin/python-sip' is not an executable

I just pushed an update to my repo with a fix. However, I also noticed that 
PyQt5 and python3-PyQt5 seem to write over eachother's files, so I recommend 
uninstalling PyQt5 (QGIS doesn't need it) and reinstalling python3-PyQt5 to 
make sure you don't have any incompatible files that might prevent QScintilla-
qt5 from building properly.

Thanks for finding this issue!



From jebrhansen+SBo at gmail.com  Tue Mar  6 00:17:18 2018
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Tue, 06 Mar 2018 00:17:18 +0000
Subject: [Slackbuilds-users] Updates - 20180303.1
In-Reply-To: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>
References: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>
Message-ID: <CANi9qStx44J3b=t5yGPVf9sFxpGU88BO_U_H0qS5zKhTkOvtfA@mail.gmail.com>

On Fri, Mar 2, 2018, 8:16 PM Willy Sudiarto Raharjo <willysr at slackbuilds.org>
wrote:

> Also it's a good idea to take a look on pasture branch again. There we
> have more than 100 scripts with no maintainers and some of them probably
> have broken links or even broken build as well. We hope someone would
> adopt the scripts and update it so it built find on -stable and works
> properly. Otherwise, i propose to start picking which one can be removed
> from the repository to reduce the number of scripts unmaintained in our
> repository. This will also help us during next development cycle.
>

What's the easiest way to view what scripts are in pasture? Are we supposed
to just look through the commit log for the pasture branch or is there some
easily viewable list of all SlackBuilds in pasture available?

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180306/f4c05ebf/attachment-0001.html>

From willysr at slackbuilds.org  Tue Mar  6 00:45:47 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 6 Mar 2018 07:45:47 +0700
Subject: [Slackbuilds-users] Updates - 20180303.1
In-Reply-To: <CANi9qStx44J3b=t5yGPVf9sFxpGU88BO_U_H0qS5zKhTkOvtfA@mail.gmail.com>
References: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>
 <CANi9qStx44J3b=t5yGPVf9sFxpGU88BO_U_H0qS5zKhTkOvtfA@mail.gmail.com>
Message-ID: <9dc4ecb1-8e7d-91e3-5d4c-881b8f4cb19f@slackbuilds.org>

> What's the easiest way to view what scripts are in pasture? Are we
> supposed to just look through the commit log for the pasture branch or
> is there some easily viewable list of all SlackBuilds in pasture available?

Yes, unfortunately the only way to see is by looking at pasture branch
https://git.slackbuilds.org/slackbuilds/log/?h=pasture

-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180306/bf6aed78/attachment.asc>

From baildon.research at googlemail.com  Tue Mar  6 06:46:57 2018
From: baildon.research at googlemail.com (David Spencer)
Date: Tue, 6 Mar 2018 06:46:57 +0000
Subject: [Slackbuilds-users] Updates - 20180303.1
In-Reply-To: <9dc4ecb1-8e7d-91e3-5d4c-881b8f4cb19f@slackbuilds.org>
References: <dfb374cf-dd53-4ac9-d30f-1bc802b678fb@slackbuilds.org>
 <CANi9qStx44J3b=t5yGPVf9sFxpGU88BO_U_H0qS5zKhTkOvtfA@mail.gmail.com>
 <9dc4ecb1-8e7d-91e3-5d4c-881b8f4cb19f@slackbuilds.org>
Message-ID: <CAMt7G9RRx9AYf7MjgpAhGK201s=NfB0gWOpFRFhg8mrbAODKUg@mail.gmail.com>

>> What's the easiest way to view what scripts are in pasture? Are we
>> supposed to just look through the commit log for the pasture branch or
>> is there some easily viewable list of all SlackBuilds in pasture available?
>
> Yes, unfortunately the only way to see is by looking at pasture branch
> https://git.slackbuilds.org/slackbuilds/log/?h=pasture

I made a list from there (please note, it'll get out-of-date... slowly)

academic/slatec
audio/HamsiManager
audio/cuberok
audio/volwheel
audio/xmms-ctl
desktop/Window_Manager_Scripts
desktop/avant-window-navigator
desktop/awn-extras
desktop/macopix
desktop/mimi
desktop/neutral
desktop/uwm
desktop/wbar
desktop/wmii
development/alloy
development/bigloo
development/curlpp
development/gnustep-startup
development/google-appengine-gosdk
development/google-appengine-pysdk
development/jython
development/mcrl2
development/spin
development/spl
development/thunderpad
development/tyrutils-ericw
development/vispatch
games/jackhammer
games/qstat
gis/geogig
gis/geogig-py
gis/geoserver
gis/geoserver-control-flow
gis/geoserver-css
gis/geoserver-javascript
gis/geoserver-oracle
gis/geoserver-pyramid
gis/geoserver-python
gis/geoserver-wps
gis/gmapcatcher
gis/mobac
gis/udig
graphics/discwrapper
libraries/gloox
libraries/jai
libraries/jai-imageio
libraries/libdesktop-agnostic
libraries/lua-MessagePack
libraries/lua-cmsgpack
misc/asterixInspector
multimedia/dvbsnoop
multimedia/lircaile
multimedia/nightingale
network/boxcryptor
network/emesene
network/glassfish
network/gui-ufw
network/licq
network/pidgin-skypeweb
network/smb4k
office/color-theme
python/py4j
python/pylirc
system/komparator4
system/picocom

Thanks to all!
-D.

From falsetti at clansco.org  Tue Mar  6 14:49:54 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Tue, 6 Mar 2018 15:49:54 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <3114364.sqAN6ORQRt@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305203245.17ffb57ccbc5152c02fede0b@clansco.org>
 <3114364.sqAN6ORQRt@wintermute.sprawl.net>
Message-ID: <20180306154954.14a23813f1ec305b2191a9b0@clansco.org>

On Mon, 05 Mar 2018 12:37:08 -0800
Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:

> On Monday, 5 March 2018 11:32:45 PST Fr?d?ric Falsetti wrote:
> > QScintilla-qt5 configure fails with:
> > 
> > install -m 755 -p libqscintillaplugin.so
> > /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillap
> > lugin.so strip --strip-unneeded
> > /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintillap
> > lugin.so /tmp/SBo/QScintilla_gpl-2.10.2
> > Usage: python configure.py [options]
> > 
> > configure.py: error: '/usr/bin/python-sip' is not an executable
> 
> I just pushed an update to my repo with a fix. However, I also noticed that 
> PyQt5 and python3-PyQt5 seem to write over eachother's files, so I recommend 
> uninstalling PyQt5 (QGIS doesn't need it) and reinstalling python3-PyQt5 to 
> make sure you don't have any incompatible files that might prevent QScintilla-
> qt5 from building properly.
> 
> Thanks for finding this issue!

now  QScintilla fails : No file or folder of this type:
> /usr/share/sip/PyQt5/QtWidgets/qwidget.sip:28:21: fatal error: qwidget.h 



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

From rshepard at appl-ecosys.com  Tue Mar  6 15:04:55 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 6 Mar 2018 07:04:55 -0800 (PST)
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <20180306154954.14a23813f1ec305b2191a9b0@clansco.org>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305203245.17ffb57ccbc5152c02fede0b@clansco.org>
 <3114364.sqAN6ORQRt@wintermute.sprawl.net>
 <20180306154954.14a23813f1ec305b2191a9b0@clansco.org>
Message-ID: <alpine.LNX.2.20.1803060701440.32069@salmo.appl-ecosys.com>

On Tue, 6 Mar 2018, Fr?d?ric Falsetti wrote:

> now  QScintilla fails : No file or folder of this type:
>> /usr/share/sip/PyQt5/QtWidgets/qwidget.sip:28:21: fatal error: qwidget.h

Fr?d?ric,

   For what it's worth, on my 14.2/32-bit system that header file is found
here:

$ locate qwidget.h
/usr/include/qt5/QtWidgets/qwidget.h
/usr/lib/qt/include/Qt/qwidget.h
/usr/lib/qt/include/QtGui/qwidget.h

   But, I cannot build the latest SBo qgis on this host; there's a different
error at the 91% completion level, but I didn't write it down because I use
GRASS more than qgis.

Regards,

Rich

From slackbuilds at jaxartes.net  Tue Mar  6 15:15:25 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Tue, 06 Mar 2018 07:15:25 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <20180306154954.14a23813f1ec305b2191a9b0@clansco.org>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <3114364.sqAN6ORQRt@wintermute.sprawl.net>
 <20180306154954.14a23813f1ec305b2191a9b0@clansco.org>
Message-ID: <1673108.AyMrsYrbx8@wintermute.sprawl.net>

On Tuesday, 6 March 2018 06:49:54 PST Fr?d?ric Falsetti wrote:
> On Mon, 05 Mar 2018 12:37:08 -0800
> 
> Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:
> > On Monday, 5 March 2018 11:32:45 PST Fr?d?ric Falsetti wrote:
> > > QScintilla-qt5 configure fails with:
> > > 
> > > install -m 755 -p libqscintillaplugin.so
> > > /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintil
> > > lap
> > > lugin.so strip --strip-unneeded
> > > /tmp/SBo/package-QScintilla-qt5/usr/lib/qt5/plugins/designer/libqscintil
> > > lap
> > > lugin.so /tmp/SBo/QScintilla_gpl-2.10.2
> > > Usage: python configure.py [options]
> > > 
> > > configure.py: error: '/usr/bin/python-sip' is not an executable
> > 
> > I just pushed an update to my repo with a fix. However, I also noticed
> > that
> > PyQt5 and python3-PyQt5 seem to write over eachother's files, so I
> > recommend uninstalling PyQt5 (QGIS doesn't need it) and reinstalling
> > python3-PyQt5 to make sure you don't have any incompatible files that
> > might prevent QScintilla- qt5 from building properly.
> > 
> > Thanks for finding this issue!
> 
> now  QScintilla fails : No file or folder of this type:
> > /usr/share/sip/PyQt5/QtWidgets/qwidget.sip:28:21: fatal error: qwidget.h

Can you confirm which version of python3-PyQt5 you have installed? Also if you 
could attach a longer error message with more context that could help.





From falsetti at clansco.org  Tue Mar  6 16:03:47 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Tue, 6 Mar 2018 17:03:47 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <1673108.AyMrsYrbx8@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <3114364.sqAN6ORQRt@wintermute.sprawl.net>
 <20180306154954.14a23813f1ec305b2191a9b0@clansco.org>
 <1673108.AyMrsYrbx8@wintermute.sprawl.net>
Message-ID: <20180306170347.9cee8eeb8f12518ce7cf9060@clansco.org>

On Tue, 06 Mar 2018 07:15:25 -0800
Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:


> Can you confirm which version of python3-PyQt5 you have installed? Also if you 
> could attach a longer error message with more context that could help.

python3-PyQt5-5.7.1-i586-1_SBo


-------------- next part --------------
A non-text attachment was scrubbed...
Name: QScintilla-qt5.output
Type: application/octet-stream
Size: 4531 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180306/1eb9164b/attachment.obj>

From skaendo at excite.com  Tue Mar  6 16:16:37 2018
From: skaendo at excite.com (Ed Ender)
Date: Tue, 06 Mar 2018 11:16:37 -0500
Subject: [Slackbuilds-users] Updates - 20180303.1
Message-ID: <20180306111637.16934@web008.roc2.bluetie.com>

I can take

/network/gui-ufw

and I have a update (18.04.0) ready, but it would require that
python-distutils-extra be built with python3 support.

So maybe a update should wait until Slackware-15 and
python-distutils-extra gets python3 support in SBo?

-Ed

-----Original Message-----
From: "David Spencer" [baildon.research at googlemail.com]
Date: 03/06/2018 12:47 AM
To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
Subject: Re: [Slackbuilds-users] Updates - 20180303.1

>> What's the easiest way to view what scripts are in pasture? Are we
>> supposed to just look through the commit log for the pasture branch or
>> is there some easily viewable list of all SlackBuilds in pasture available?
>
> Yes, unfortunately the only way to see is by looking at pasture branch
> https://git.slackbuilds.org/slackbuilds/log/?h=pasture

I made a list from there (please note, it'll get out-of-date... slowly)

academic/slatec
audio/HamsiManager
audio/cuberok
audio/volwheel
audio/xmms-ctl
desktop/Window_Manager_Scripts
desktop/avant-window-navigator
desktop/awn-extras
desktop/macopix
desktop/mimi
desktop/neutral
desktop/uwm
desktop/wbar
desktop/wmii
development/alloy
development/bigloo
development/curlpp
development/gnustep-startup
development/google-appengine-gosdk
development/google-appengine-pysdk
development/jython
development/mcrl2
development/spin
development/spl
development/thunderpad
development/tyrutils-ericw
development/vispatch
games/jackhammer
games/qstat
gis/geogig
gis/geogig-py
gis/geoserver
gis/geoserver-control-flow
gis/geoserver-css
gis/geoserver-javascript
gis/geoserver-oracle
gis/geoserver-pyramid
gis/geoserver-python
gis/geoserver-wps
gis/gmapcatcher
gis/mobac
gis/udig
graphics/discwrapper
libraries/gloox
libraries/jai
libraries/jai-imageio
libraries/libdesktop-agnostic
libraries/lua-MessagePack
libraries/lua-cmsgpack
misc/asterixInspector
multimedia/dvbsnoop
multimedia/lircaile
multimedia/nightingale
network/boxcryptor
network/emesene
network/glassfish
network/gui-ufw
network/licq
network/pidgin-skypeweb
network/smb4k
office/color-theme
python/py4j
python/pylirc
system/komparator4
system/picocom

Thanks to all!
-D.
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/




From slackbuilds at jaxartes.net  Tue Mar  6 16:21:51 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Tue, 06 Mar 2018 08:21:51 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <20180306170347.9cee8eeb8f12518ce7cf9060@clansco.org>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <1673108.AyMrsYrbx8@wintermute.sprawl.net>
 <20180306170347.9cee8eeb8f12518ce7cf9060@clansco.org>
Message-ID: <1936644.pNfofqWnVg@wintermute.sprawl.net>

On Tuesday, 6 March 2018 08:03:47 PST Fr?d?ric Falsetti wrote:
> On Tue, 06 Mar 2018 07:15:25 -0800
> 
> Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:
> > Can you confirm which version of python3-PyQt5 you have installed? Also if
> > you could attach a longer error message with more context that could
> > help.
> python3-PyQt5-5.7.1-i586-1_SBo

Thanks. Can you confirm that you have qwidget.h installed as part of the  
qt5-5.7.1 package? I assume you do and the QScintilla build isn't finding it, 
which I should be able to fix.





From falsetti at clansco.org  Tue Mar  6 16:25:09 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Tue, 6 Mar 2018 17:25:09 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <1936644.pNfofqWnVg@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <1673108.AyMrsYrbx8@wintermute.sprawl.net>
 <20180306170347.9cee8eeb8f12518ce7cf9060@clansco.org>
 <1936644.pNfofqWnVg@wintermute.sprawl.net>
Message-ID: <20180306172509.e215ae2552a0fac3dd56c233@clansco.org>

On Tue, 06 Mar 2018 08:21:51 -0800
Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:

> On Tuesday, 6 March 2018 08:03:47 PST Fr?d?ric Falsetti wrote:
> > On Tue, 06 Mar 2018 07:15:25 -0800
> > 
> > Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:
> > > Can you confirm which version of python3-PyQt5 you have installed? Also if
> > > you could attach a longer error message with more context that could
> > > help.
> > python3-PyQt5-5.7.1-i586-1_SBo
> 
> Thanks. Can you confirm that you have qwidget.h installed as part of the  
> qt5-5.7.1 package? I assume you do and the QScintilla build isn't finding it, 
> which I should be able to fix.

 slocate qwidget.h
/usr/include/qt5/QtWidgets/qwidget.h

cat /var/log/packages/qt5-5.7.1-i586-1_SBo|grep qwidget.h
usr/include/qt5/QtWidgets/qwidget.h

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

From falsetti at clansco.org  Tue Mar  6 16:43:47 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Tue, 6 Mar 2018 17:43:47 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <alpine.LNX.2.20.1803060701440.32069@salmo.appl-ecosys.com>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305203245.17ffb57ccbc5152c02fede0b@clansco.org>
 <3114364.sqAN6ORQRt@wintermute.sprawl.net>
 <20180306154954.14a23813f1ec305b2191a9b0@clansco.org>
 <alpine.LNX.2.20.1803060701440.32069@salmo.appl-ecosys.com>
Message-ID: <20180306174347.2d508a4e8ffb7dbacc21b76b@clansco.org>

On Tue, 6 Mar 2018 07:04:55 -0800 (PST)
Rich Shepard <rshepard at appl-ecosys.com> wrote:

> On Tue, 6 Mar 2018, Fr?d?ric Falsetti wrote:
> 
> > now  QScintilla fails : No file or folder of this type:
> >> /usr/share/sip/PyQt5/QtWidgets/qwidget.sip:28:21: fatal error: qwidget.h
> 
> Fr?d?ric,
> 
>    For what it's worth, on my 14.2/32-bit system that header file is found
> here:
> 
> $ locate qwidget.h
> /usr/include/qt5/QtWidgets/qwidget.h
> /usr/lib/qt/include/Qt/qwidget.h
> /usr/lib/qt/include/QtGui/qwidget.h
> 
>    But, I cannot build the latest SBo qgis on this host; there's a different
> error at the 91% completion level, but I didn't write it down because I use
> GRASS more than qgis.
> 

Hi Rich,

I have the same here, 
the install of qgis-2.18.16-i586-1_SBo worked fine me

regards
ff


> 

From rvnues at tesco.net  Tue Mar  6 17:03:18 2018
From: rvnues at tesco.net (rob van nues)
Date: Tue, 6 Mar 2018 17:03:18 +0000
Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 143, Issue 12;
 Updates - 20180303.1
In-Reply-To: <mailman.4146.1520353009.21966.slackbuilds-users@slackbuilds.org>
References: <mailman.4146.1520353009.21966.slackbuilds-users@slackbuilds.org>
Message-ID: <20180306170112.2e8d4ba5@webmail.tesco.net>

Hi, 

The Slackbuild for clamav-0.99.4 in ponce's -current branch stalls.
The patch-line needs to be removed/commented out (this line is gone
from the clamav.Slackbuild for the stable-branch which works ok)

Hth

Rob


From matteo.bernardini at gmail.com  Tue Mar  6 17:10:44 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 6 Mar 2018 18:10:44 +0100
Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 143, Issue 12;
 Updates - 20180303.1
In-Reply-To: <20180306170112.2e8d4ba5@webmail.tesco.net>
References: <mailman.4146.1520353009.21966.slackbuilds-users@slackbuilds.org>
 <20180306170112.2e8d4ba5@webmail.tesco.net>
Message-ID: <CAPsDuS7FE9TzvTOsAhtmvuW0AfOkzzpzDyn3NV9Xd7uk251wzg@mail.gmail.com>

2018-03-06 18:03 GMT+01:00 rob van nues <rvnues at tesco.net>:
> Hi,
>
> The Slackbuild for clamav-0.99.4 in ponce's -current branch stalls.
> The patch-line needs to be removed/commented out (this line is gone
> from the clamav.Slackbuild for the stable-branch which works ok)

hi Rob,

thanks for reporting but this is not the proper place, SlackBuilds.org
supports only the latest stable Slackware release.

if you have issues with building anything from the scripts in my
unofficial repository (not supported or endorsed by SBo) please use
the dedicated LQ thread

https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/

Matteo

From rshepard at appl-ecosys.com  Tue Mar  6 17:19:39 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 6 Mar 2018 09:19:39 -0800 (PST)
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <20180306174347.2d508a4e8ffb7dbacc21b76b@clansco.org>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305203245.17ffb57ccbc5152c02fede0b@clansco.org>
 <3114364.sqAN6ORQRt@wintermute.sprawl.net>
 <20180306154954.14a23813f1ec305b2191a9b0@clansco.org>
 <alpine.LNX.2.20.1803060701440.32069@salmo.appl-ecosys.com>
 <20180306174347.2d508a4e8ffb7dbacc21b76b@clansco.org>
Message-ID: <alpine.LNX.2.20.1803060910010.32069@salmo.appl-ecosys.com>

On Tue, 6 Mar 2018, Fr?d?ric Falsetti wrote:

> I have the same here,
> the install of qgis-2.18.16-i586-1_SBo worked fine me

ff,

   I'm trying to upgrade from 2.18.15 to 2.18.17. One problem I solved was
the loss of gdal and libLAS when I upgraded the kernel to 4.4.118. For some
reason the latest flurry of kernel upgrades remove the libraries or
executables of some files while the packages are still shown as installed.
So, a re-installation of gdal fixed that.

   Now I have another issue (along with a question about compile-time
options).

   In the qgis.SlackBuild script I have these set:

WITHGRASS="yes"
if pkg-config --exists grass; then
   WITHGRASS="-DGRASS_PREFIX=$(pkg-config --variable=prefix grass)"
fi

WITHSERVER="-DWITH_SERVER=FALSE"
CGIBINDIR="${CGIBINDIR:-/var/www/cgi-bin/qgis}"
if [ "${SERVER:-no}" = "yes" ]; then
   WITHSERVER="-DWITH_SERVER=TRUE -DQGIS_CGIBIN_SUBDIR=$CGIBINDIR"
fi

WITHNINJA="yes"
if [ "${NINJA:-no}" = "yes" ]; then
   WITHNINJA="-GNinja"
fi

   And I do not see where to add support for postgres and postgis in the
script. It's not on Ben's SBo gdal page, either.

   So, setting grass and ninja to 'yes' produces this error:

...
qgis-2.18.17/tools/
qgis-2.18.17/tools/qgis-qt3to4.pl
patching file src/providers/arcgisrest/CMakeLists.txt
CMake Error: The source directory "/opt/SBo/qgis-2.18.17/build/yes" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.

   This must be a syntax error I made specifying inclusion of grass and ninja
so I would appreciate learning how to correctly do this.

TIA,

Rich

From willysr at slackbuilds.org  Tue Mar  6 17:20:40 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 7 Mar 2018 00:20:40 +0700
Subject: [Slackbuilds-users] Updates - 20180303.1
In-Reply-To: <20180306111637.16934@web008.roc2.bluetie.com>
References: <20180306111637.16934@web008.roc2.bluetie.com>
Message-ID: <f18818d5-ff8f-dd1b-1609-9137a5b34ca7@slackbuilds.org>

> /network/gui-ufw
> 
> and I have a update (18.04.0) ready, but it would require that
> python-distutils-extra be built with python3 support.
> 
> So maybe a update should wait until Slackware-15 and
> python-distutils-extra gets python3 support in SBo?

It already have python3 support if you pass the extra parameter
PYTHON3=yes ./python-distutils-extra.SlackBuild


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180307/3bb4808e/attachment.asc>

From skaendo at excite.com  Tue Mar  6 17:28:41 2018
From: skaendo at excite.com (Ed Ender)
Date: Tue, 06 Mar 2018 12:28:41 -0500
Subject: [Slackbuilds-users] Updates - 20180303.1
Message-ID: <20180306122841.18844@web001.roc2.bluetie.com>

10-4. I will submit an update.

-----Original Message-----
From: "Willy Sudiarto Raharjo" [willysr at slackbuilds.org]
Date: 03/06/2018 11:21 AM
To: slackbuilds-users at slackbuilds.org
Subject: Re: [Slackbuilds-users] Updates - 20180303.1

> /network/gui-ufw
> 
> and I have a update (18.04.0) ready, but it would require that
> python-distutils-extra be built with python3 support.
> 
> So maybe a update should wait until Slackware-15 and
> python-distutils-extra gets python3 support in SBo?

It already have python3 support if you pass the extra parameter
PYTHON3=yes ./python-distutils-extra.SlackBuild


-- 
Willy Sudiarto Raharjo




From slackbuilds at jaxartes.net  Tue Mar  6 17:29:01 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Tue, 06 Mar 2018 17:29:01 +0000
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <alpine.LNX.2.20.1803060910010.32069@salmo.appl-ecosys.com>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305203245.17ffb57ccbc5152c02fede0b@clansco.org>
 <3114364.sqAN6ORQRt@wintermute.sprawl.net>
 <20180306154954.14a23813f1ec305b2191a9b0@clansco.org>
 <alpine.LNX.2.20.1803060701440.32069@salmo.appl-ecosys.com>
 <20180306174347.2d508a4e8ffb7dbacc21b76b@clansco.org>
 <alpine.LNX.2.20.1803060910010.32069@salmo.appl-ecosys.com>
Message-ID: <2511B38C-7B1B-4C52-B007-76CBC4A4EAF0@jaxartes.net>

Could you start a new thread for QGIS issues that didn't relate to QGIS 3?

On March 6, 2018 5:19:39 PM UTC, Rich Shepard <rshepard at appl-ecosys.com> wrote:
>   Now I have another issue (along with a question about compile-time
>options).
>
>   In the qgis.SlackBuild script I have these set:
>
>WITHGRASS="yes"
>if pkg-config --exists grass; then
>   WITHGRASS="-DGRASS_PREFIX=$(pkg-config --variable=prefix grass)"
>fi

The script will auto-detect GRASS. Setting "yes" will just cause an error.
>
>WITHSERVER="-DWITH_SERVER=FALSE"
>CGIBINDIR="${CGIBINDIR:-/var/www/cgi-bin/qgis}"
>if [ "${SERVER:-no}" = "yes" ]; then
>   WITHSERVER="-DWITH_SERVER=TRUE -DQGIS_CGIBIN_SUBDIR=$CGIBINDIR"
>fi
>
>WITHNINJA="yes"
>if [ "${NINJA:-no}" = "yes" ]; then
>   WITHNINJA="-GNinja"
>fi
>
>  And I do not see where to add support for postgres and postgis in the
>script. It's not on Ben's SBo gdal page, either.

This is automatic for GDAL and QGIS. No special parameters are needed. 

>   So, setting grass and ninja to 'yes' produces this error:
>
>...
>qgis-2.18.17/tools/
>qgis-2.18.17/tools/qgis-qt3to4.pl
>patching file src/providers/arcgisrest/CMakeLists.txt
>CMake Error: The source directory "/opt/SBo/qgis-2.18.17/build/yes"
>does not exist.
>Specify --help for usage, or press the help button on the CMake GUI.

Try running the script with no modifications and no options and you should get what you want. 

>This must be a syntax error I made specifying inclusion of grass and
>ninja
>so I would appreciate learning how to correctly do this.
>
>TIA,
>
>Rich
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

From rshepard at appl-ecosys.com  Tue Mar  6 17:33:26 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 6 Mar 2018 09:33:26 -0800 (PST)
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <2511B38C-7B1B-4C52-B007-76CBC4A4EAF0@jaxartes.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305203245.17ffb57ccbc5152c02fede0b@clansco.org>
 <3114364.sqAN6ORQRt@wintermute.sprawl.net>
 <20180306154954.14a23813f1ec305b2191a9b0@clansco.org>
 <alpine.LNX.2.20.1803060701440.32069@salmo.appl-ecosys.com>
 <20180306174347.2d508a4e8ffb7dbacc21b76b@clansco.org>
 <alpine.LNX.2.20.1803060910010.32069@salmo.appl-ecosys.com>
 <2511B38C-7B1B-4C52-B007-76CBC4A4EAF0@jaxartes.net>
Message-ID: <alpine.LNX.2.20.1803060931510.32069@salmo.appl-ecosys.com>

On Tue, 6 Mar 2018, Benjamin Trigona-Harany wrote:

> The script will auto-detect GRASS. Setting "yes" will just cause an error.

Ben,

   I wondered about this.

> This is automatic for GDAL and QGIS. No special parameters are needed.

   Then I mis-interpreted the SBo page.

> Try running the script with no modifications and no options and you should
> get what you want.

   Thanks very much for clarifying!

Best regards,

Rich

From rshepard at appl-ecosys.com  Tue Mar  6 18:43:22 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 6 Mar 2018 10:43:22 -0800 (PST)
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <alpine.LNX.2.20.1803060931510.32069@salmo.appl-ecosys.com>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <20180305203245.17ffb57ccbc5152c02fede0b@clansco.org>
 <3114364.sqAN6ORQRt@wintermute.sprawl.net>
 <20180306154954.14a23813f1ec305b2191a9b0@clansco.org>
 <alpine.LNX.2.20.1803060701440.32069@salmo.appl-ecosys.com>
 <20180306174347.2d508a4e8ffb7dbacc21b76b@clansco.org>
 <alpine.LNX.2.20.1803060910010.32069@salmo.appl-ecosys.com>
 <2511B38C-7B1B-4C52-B007-76CBC4A4EAF0@jaxartes.net>
 <alpine.LNX.2.20.1803060931510.32069@salmo.appl-ecosys.com>
Message-ID: <alpine.LNX.2.20.1803061035520.28861@salmo.appl-ecosys.com>

On Tue, 6 Mar 2018, Rich Shepard wrote:

>> Try running the script with no modifications and no options and you should
>> get what you want.
>
>  Thanks very much for clarifying!

Ben,

   I downloaded fresh *.tar.gz and source tarball.

   What might I be missing now with this error?

[ 97%] Building CXX object src/app/CMakeFiles/qgis_app.dir/moc_qgsvariantdelegate.cxx.o
[ 97%] Linking CXX shared library ../../output/lib/libqgis_app.so
[ 97%] Built target qgis_app
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2

   Looking in /opt/SBo/qgis-2.18.17/ I don't see a Makefile in the top-level
directory and don't know where the script is looking for the Makefile that
failed.

Regards,

Rich

From slackbuilds at jaxartes.net  Tue Mar  6 20:11:31 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Tue, 06 Mar 2018 12:11:31 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <20180306172509.e215ae2552a0fac3dd56c233@clansco.org>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <1936644.pNfofqWnVg@wintermute.sprawl.net>
 <20180306172509.e215ae2552a0fac3dd56c233@clansco.org>
Message-ID: <1729579.Ot8fpvbGVj@wintermute.sprawl.net>

On Tuesday, 6 March 2018 08:25:09 PST Fr?d?ric Falsetti wrote:
> On Tue, 06 Mar 2018 08:21:51 -0800
> 
> Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:
> > On Tuesday, 6 March 2018 08:03:47 PST Fr?d?ric Falsetti wrote:
> > > On Tue, 06 Mar 2018 07:15:25 -0800
> > > 
> > > Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:
> > > > Can you confirm which version of python3-PyQt5 you have installed?
> > > > Also if
> > > > you could attach a longer error message with more context that could
> > > > help.
> > > 
> > > python3-PyQt5-5.7.1-i586-1_SBo
> > 
> > Thanks. Can you confirm that you have qwidget.h installed as part of the
> > qt5-5.7.1 package? I assume you do and the QScintilla build isn't finding
> > it, which I should be able to fix.
> 
>  slocate qwidget.h
> /usr/include/qt5/QtWidgets/qwidget.h
> 
> cat /var/log/packages/qt5-5.7.1-i586-1_SBo|grep qwidget.h
> usr/include/qt5/QtWidgets/qwidget.h

Hi Fr?d?ric,

Can you try inserting the following two lines in the build script immediately 
before the "python3 configure.py ..." line?

sed -i "1423i\    pro.write('INCLUDEPATH += /usr/include/qt5/QtWidgets\\\n')" 
configure.py
sed -i "1423i\    pro.write('INCLUDEPATH += /usr/include/qt5/QtPrintSupport\\
\n')" configure.py

For some reason this is not necessary on my x86_64 install. qmake-qt5 
automatically adds the right include paths but not for you. I hope these lines 
will be enough.




From slackbuilds at jaxartes.net  Wed Mar  7 00:18:17 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Tue, 06 Mar 2018 16:18:17 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <alpine.LNX.2.20.1803061035520.28861@salmo.appl-ecosys.com>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <alpine.LNX.2.20.1803060931510.32069@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1803061035520.28861@salmo.appl-ecosys.com>
Message-ID: <3736133.IW9tBe3F7S@wintermute.sprawl.net>

On Tuesday, 6 March 2018 10:43:22 PST Rich Shepard wrote:
> On Tue, 6 Mar 2018, Rich Shepard wrote:
> >> Try running the script with no modifications and no options and you
> >> should
> >> get what you want.
> >> 
> >  Thanks very much for clarifying!
> 
> Ben,
> 
>    I downloaded fresh *.tar.gz and source tarball.
> 
>    What might I be missing now with this error?
> 
> [ 97%] Building CXX object
> src/app/CMakeFiles/qgis_app.dir/moc_qgsvariantdelegate.cxx.o [ 97%] Linking
> CXX shared library ../../output/lib/libqgis_app.so
> [ 97%] Built target qgis_app
> Makefile:149: recipe for target 'all' failed
> make: *** [all] Error 2
> 
>    Looking in /opt/SBo/qgis-2.18.17/ I don't see a Makefile in the top-level
> directory and don't know where the script is looking for the Makefile that
> failed.

QGIS uses cmake, which by convention means the makefiles end up in the build 
directory. In any case, we'd need to see much more output to see what's 
happening when you are building 2.18.17.



From rshepard at appl-ecosys.com  Wed Mar  7 00:41:34 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 6 Mar 2018 16:41:34 -0800 (PST)
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <3736133.IW9tBe3F7S@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <alpine.LNX.2.20.1803060931510.32069@salmo.appl-ecosys.com>
 <alpine.LNX.2.20.1803061035520.28861@salmo.appl-ecosys.com>
 <3736133.IW9tBe3F7S@wintermute.sprawl.net>
Message-ID: <alpine.LNX.2.20.1803061639500.28861@salmo.appl-ecosys.com>

On Tue, 6 Mar 2018, Benjamin Trigona-Harany wrote:

> QGIS uses cmake, which by convention means the makefiles end up in the
> build directory. In any case, we'd need to see much more output to see
> what's happening when you are building 2.18.17.

Ben,

   How much output should I provide? It ran approximately 59 minutes to the
point it failed. I suppose that I could tee the output to a file if that
would help.

Regards,

Rich

From slackbuilds at jaxartes.net  Wed Mar  7 00:49:36 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Tue, 06 Mar 2018 16:49:36 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <alpine.LNX.2.20.1803061639500.28861@salmo.appl-ecosys.com>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <3736133.IW9tBe3F7S@wintermute.sprawl.net>
 <alpine.LNX.2.20.1803061639500.28861@salmo.appl-ecosys.com>
Message-ID: <1924548.KtnZx37obm@wintermute.sprawl.net>

On Tuesday, 6 March 2018 16:41:34 PST Rich Shepard wrote:
> On Tue, 6 Mar 2018, Benjamin Trigona-Harany wrote:
> > QGIS uses cmake, which by convention means the makefiles end up in the
> > build directory. In any case, we'd need to see much more output to see
> > what's happening when you are building 2.18.17.
> 
> Ben,
> 
>    How much output should I provide? It ran approximately 59 minutes to the
> point it failed. I suppose that I could tee the output to a file if that
> would help.

Hard to say with big builds like QGIS. If you go to the build directory and 
run "make > output.log" and attach the file here or put it in a pastebin that 
will be enough. You'll need to do that as root or change the ownership of the 
directory.



From rshepard at appl-ecosys.com  Wed Mar  7 01:01:59 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 6 Mar 2018 17:01:59 -0800 (PST)
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <1924548.KtnZx37obm@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <3736133.IW9tBe3F7S@wintermute.sprawl.net>
 <alpine.LNX.2.20.1803061639500.28861@salmo.appl-ecosys.com>
 <1924548.KtnZx37obm@wintermute.sprawl.net>
Message-ID: <alpine.LNX.2.20.1803061701120.28861@salmo.appl-ecosys.com>

On Tue, 6 Mar 2018, Benjamin Trigona-Harany wrote:

> Hard to say with big builds like QGIS. If you go to the build directory
> and run "make > output.log" and attach the file here or put it in a
> pastebin that will be enough. You'll need to do that as root or change the
> ownership of the directory.

Ben,

   That was quick and easy. The log file's attached.

Thanks,

Rich
-------------- next part --------------
[  0%] Built target version
[ 18%] Built target qgis_core
[ 20%] Built target qgis_analysis
[ 21%] Built target qgis_networkanalysis
[ 29%] Built target ui
[ 57%] Built target qgis_gui
[ 57%] Built target basicauthmethod
[ 57%] Built target identcertauthmethod
[ 58%] Built target pkipathsauthmethod
[ 58%] Built target pkcs12authmethod
[ 58%] Built target arcgisfeatureserverprovider
[ 59%] Built target arcgismapserverprovider
[ 59%] Built target memoryprovider
[ 59%] Built target ogrprovider
[ 60%] Built target wmsprovider_a
[ 61%] Built target wmsprovider
[ 61%] Built target delimitedtextprovider
[ 61%] Built target gdalprovider
[ 61%] Built target mssqlprovider
[ 61%] Built target owsprovider
[ 61%] Built target wcsprovider
[ 61%] Built target gpxprovider
[ 62%] Built target wfsprovider
[ 62%] Built target spatialiteprovider
[ 63%] Built target virtuallayerprovider
[ 64%] Built target db2provider
[ 65%] Built target postgresprovider
[ 65%] Built target crssync
[ 66%] Built target libdxfrw
[ 82%] Built target qgis_app
[ 82%] Generating qrc_testdata.cxx
[ 82%] Generating qrc_images.cxx
Scanning dependencies of target qgis
[ 82%] Building CXX object src/app/CMakeFiles/qgis.dir/main.cpp.o
[ 82%] Building CXX object src/app/CMakeFiles/qgis.dir/qrc_images.cxx.o
[ 82%] Building CXX object src/app/CMakeFiles/qgis.dir/qrc_testdata.cxx.o
[ 82%] Linking CXX executable ../../output/bin/qgis
[ 82%] Built target qgis
[ 82%] Built target qgis_help
[ 82%] Built target qbrowser
[ 83%] Built target interpolationplugin
[ 84%] Built target oracleplugin
[ 84%] Built target rasterterrainplugin
[ 84%] Built target coordinatecaptureplugin
[ 85%] Built target dxf2shpconverterplugin
[ 86%] Built target evis
[ 87%] Built target spatialqueryplugin
[ 88%] Built target roadgraphplugin
[ 88%] Built target zonalstatisticsplugin
[ 90%] Built target georefplugin
[ 91%] Built target gpsimporterplugin
[ 92%] Built target topolplugin
[ 93%] Built target offlineeditingplugin
[ 93%] Built target heatmapplugin
[ 95%] Built target geometrycheckerplugin
[ 96%] Built target geometrysnapperplugin
[ 96%] Built target qgispython
Scanning dependencies of target translations
[ 96%] Generating ../output/i18n/qgis_ar.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_ar.qm'...
    Generated 9431 translation(s) (9301 finished and 130 unfinished)
    Ignored 8807 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_bg.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_bg.qm'...
    Generated 12470 translation(s) (12384 finished and 86 unfinished)
    Ignored 5768 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_bs.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_bs.qm'...
    Generated 18093 translation(s) (18091 finished and 2 unfinished)
    Ignored 145 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_ca.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_ca.qm'...
    Generated 13036 translation(s) (12981 finished and 55 unfinished)
    Ignored 5202 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_cs.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_cs.qm'...
    Generated 14771 translation(s) (14735 finished and 36 unfinished)
    Ignored 3467 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_da.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_da.qm'...
    Generated 17891 translation(s) (17889 finished and 2 unfinished)
    Ignored 347 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_de.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_de.qm'...
    Generated 18368 translation(s) (18368 finished and 0 unfinished)
[ 96%] Generating ../output/i18n/qgis_el.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_el.qm'...
    Generated 10797 translation(s) (10749 finished and 48 unfinished)
    Ignored 7441 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_es.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_es.qm'...
    Generated 18174 translation(s) (18174 finished and 0 unfinished)
    Ignored 64 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_et.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_et.qm'...
    Generated 13315 translation(s) (13224 finished and 91 unfinished)
    Ignored 4923 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_eu.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_eu.qm'...
    Generated 18238 translation(s) (18238 finished and 0 unfinished)
[ 96%] Generating ../output/i18n/qgis_fi.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_fi.qm'...
    Generated 14345 translation(s) (14062 finished and 283 unfinished)
    Ignored 3893 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_fr.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_fr.qm'...
    Generated 18220 translation(s) (18220 finished and 0 unfinished)
    Ignored 18 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_gl.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_gl.qm'...
    Generated 18237 translation(s) (18237 finished and 0 unfinished)
    Ignored 1 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_hi.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_hi.qm'...
    Generated 12591 translation(s) (12472 finished and 119 unfinished)
    Ignored 5647 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_hr.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_hr.qm'...
    Generated 7431 translation(s) (7298 finished and 133 unfinished)
    Ignored 10807 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_hu.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_hu.qm'...
    Generated 16652 translation(s) (16648 finished and 4 unfinished)
    Ignored 1586 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_id.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_id.qm'...
    Generated 10992 translation(s) (10726 finished and 266 unfinished)
    Ignored 7246 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_it.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_it.qm'...
    Generated 14105 translation(s) (14025 finished and 80 unfinished)
    Ignored 4133 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_ja.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_ja.qm'...
    Generated 17375 translation(s) (17374 finished and 1 unfinished)
    Ignored 863 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_km.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_km.qm'...
    Generated 9478 translation(s) (9347 finished and 131 unfinished)
    Ignored 8760 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_ko.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_ko.qm'...
    Generated 11891 translation(s) (11769 finished and 122 unfinished)
    Ignored 6347 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_lt.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_lt.qm'...
    Generated 11464 translation(s) (11339 finished and 125 unfinished)
    Ignored 6774 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_lv.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_lv.qm'...
    Generated 9378 translation(s) (9178 finished and 200 unfinished)
    Ignored 8860 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_nb.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_nb.qm'...
    Generated 14642 translation(s) (14612 finished and 30 unfinished)
    Ignored 3596 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_nl.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_nl.qm'...
    Generated 18233 translation(s) (18233 finished and 0 unfinished)
    Ignored 5 untranslated source text(s)
[ 96%] Generating ../output/i18n/qgis_pl.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_pl.qm'...
    Generated 14883 translation(s) (14874 finished and 9 unfinished)
    Ignored 3355 untranslated source text(s)
[ 97%] Generating ../output/i18n/qgis_pt_BR.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_pt_BR.qm'...
    Generated 18238 translation(s) (18238 finished and 0 unfinished)
[ 97%] Generating ../output/i18n/qgis_pt_PT.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_pt_PT.qm'...
    Generated 15641 translation(s) (15623 finished and 18 unfinished)
    Ignored 2597 untranslated source text(s)
[ 97%] Generating ../output/i18n/qgis_ro.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_ro.qm'...
    Generated 18238 translation(s) (18238 finished and 0 unfinished)
[ 97%] Generating ../output/i18n/qgis_ru.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_ru.qm'...
    Generated 15597 translation(s) (15558 finished and 39 unfinished)
    Ignored 2641 untranslated source text(s)
[ 97%] Generating ../output/i18n/qgis_sk.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_sk.qm'...
    Generated 8576 translation(s) (7770 finished and 806 unfinished)
    Ignored 9662 untranslated source text(s)
[ 97%] Generating ../output/i18n/qgis_sl.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_sl.qm'...
    Generated 9641 translation(s) (9520 finished and 121 unfinished)
    Ignored 8597 untranslated source text(s)
[ 97%] Generating ../output/i18n/qgis_sv.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_sv.qm'...
    Generated 18238 translation(s) (18238 finished and 0 unfinished)
[ 97%] Generating ../output/i18n/qgis_tr.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_tr.qm'...
    Generated 10958 translation(s) (10871 finished and 87 unfinished)
    Ignored 7280 untranslated source text(s)
[ 97%] Generating ../output/i18n/qgis_vi.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_vi.qm'...
    Generated 16633 translation(s) (16621 finished and 12 unfinished)
    Ignored 1605 untranslated source text(s)
[ 97%] Generating ../output/i18n/qgis_zh-Hans.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_zh-Hans.qm'...
    Generated 16177 translation(s) (16161 finished and 16 unfinished)
    Ignored 2061 untranslated source text(s)
[ 97%] Generating ../output/i18n/qgis_zh-Hant.qm
Updating '/opt/SBo/qgis-2.18.17/build/output/i18n/qgis_zh-Hant.qm'...
    Generated 14167 translation(s) (14090 finished and 77 unfinished)
    Ignored 4071 untranslated source text(s)
[ 97%] Built target translations
[ 97%] Built target python_module_qgis__analysis
[ 97%] Built target python_module_qgis__gui
[ 97%] Built target pysix
[ 97%] Built target zzz-GdalTools-3-depend
[ 97%] Built target zzz-GdalTools-1-depend
[ 97%] Built target pyutils
[ 97%] Built target pyqtcompat
[ 97%] Built target pygui
[ 97%] Built target python_module_qgis__core
[ 97%] Built target pycore
Scanning dependencies of target zzz-GdalTools-2-depend
[ 97%] Generating ui_widgetSieve.py
python/plugins/GdalTools/tools/CMakeFiles/zzz-GdalTools-2-depend.dir/build.make:117: recipe for target 'python/plugins/GdalTools/tools/ui_widgetSieve.py' failed
CMakeFiles/Makefile2:4276: recipe for target 'python/plugins/GdalTools/tools/CMakeFiles/zzz-GdalTools-2-depend.dir/all' failed
Makefile:149: recipe for target 'all' failed

From slackbuilds at jaxartes.net  Wed Mar  7 01:25:11 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Tue, 06 Mar 2018 17:25:11 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <alpine.LNX.2.20.1803061701120.28861@salmo.appl-ecosys.com>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <1924548.KtnZx37obm@wintermute.sprawl.net>
 <alpine.LNX.2.20.1803061701120.28861@salmo.appl-ecosys.com>
Message-ID: <3062690.X610dqcBXX@wintermute.sprawl.net>

On Tuesday, 6 March 2018 17:01:59 PST Rich Shepard wrote:
> On Tue, 6 Mar 2018, Benjamin Trigona-Harany wrote:
> > Hard to say with big builds like QGIS. If you go to the build directory
> > and run "make > output.log" and attach the file here or put it in a
> > pastebin that will be enough. You'll need to do that as root or change the
> > ownership of the directory.
> 
> Ben,
> 
>    That was quick and easy. The log file's attached.

I think I'll need a bit more since I've encountered failures with the GDAL 
plugin before and it's never been simple to resolve. In the build dir can you 
do this:

rm -r python/plugins/GdalTools
make > output.log

The new logfile should have a lot more info this time.



From rshepard at appl-ecosys.com  Wed Mar  7 02:13:18 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 6 Mar 2018 18:13:18 -0800 (PST)
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <3062690.X610dqcBXX@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <1924548.KtnZx37obm@wintermute.sprawl.net>
 <alpine.LNX.2.20.1803061701120.28861@salmo.appl-ecosys.com>
 <3062690.X610dqcBXX@wintermute.sprawl.net>
Message-ID: <alpine.LNX.2.20.1803061809450.28861@salmo.appl-ecosys.com>

On Tue, 6 Mar 2018, Benjamin Trigona-Harany wrote:

> rm -r python/plugins/GdalTools
> make > output.log

Ben,

   Log file (about 3k smaller) is attached, and I think I see the problem. On the v.t. I see:

/usr/lib/gcc/i586-slackware-linux/5.5.0/../../../../i586-slackware-linux/bin/ld: warning: libproj.so.12, needed by /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../libspatialite.so, not found (try using -rpath or -rpath-link)
/usr/lib/gcc/i586-slackware-linux/5.5.0/../../../../i586-slackware-linux/bin/ld: warning: libproj.so.12, needed by /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../libspatialite.so, not found (try using -rpath or -rpath-link)
/usr/lib/gcc/i586-slackware-linux/5.5.0/../../../../i586-slackware-linux/bin/ld: warning: libproj.so.12, needed by /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../libspatialite.so, not found (try using -rpath or -rpath-link)
/usr/lib/gcc/i586-slackware-linux/5.5.0/../../../../i586-slackware-linux/bin/ld: warning: libproj.so.12, needed by /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../libspatialite.so, not found (try using -rpath or -rpath-link)
Traceback (most recent call last):
   File "../../../../../scripts/pyuic-wrapper.py", line 26, in <module>
     import qgis.PyQt.uic.pyuic
   File "/opt/SBo/qgis-2.18.17/build/output/python/qgis/__init__.py", line 27, in <module>
     from qgis.core import QgsFeature, QgsGeometry
   File "/opt/SBo/qgis-2.18.17/build/output/python/qgis/core/__init__.py", line 30, in <module>
     from qgis._core import *
ImportError: libproj.so.12: cannot open shared object file: No such file or directory
make[2]: *** [python/plugins/GdalTools/tools/ui_widgetSieve.py] Error 1
make[1]: *** [python/plugins/GdalTools/tools/CMakeFiles/zzz-GdalTools-2-depend.dir/all] Error 2
make: *** [all] Error 2

and the build is looking for libproj.so.12. Here, libproj-4.4.7-i486-2 is
installed and provides /usr/lib/libproj.so.13.

HTH,

Rich
-------------- next part --------------
-- QGIS version: 2.18.17 Las Palmas (21817)
-- Could not find GRASS 6
-- Could not find GRASS 7
-- Found Proj: /usr/lib/libproj.so
-- Found GEOS: /usr/lib/libgeos_c.so (3.6.2)
-- Found GDAL: /usr/lib/libgdal.so (2.2.3)
-- Found Expat: /usr/lib/libexpat.so
-- Found Spatialindex: /usr/lib/libspatialindex.so
-- Found Qwt: /usr/lib/libqwt.so (6.1.3)
-- Found Sqlite3: /usr/lib/libsqlite3.so
-- Found PostgreSQL: /usr/lib/postgresql/10.2/lib/libpq.so
-- Found SpatiaLite: /usr/lib/libspatialite.so
-- Qt WebKit support enabled
-- Found Qt version: 4.8.7
-- Touch support disabled
-- Found QScintilla2: /usr/lib/libqscintilla2.so (2.4)
-- Found QCA: /usr/lib/libqca.so (2.1.1)
-- Found QCA OpenSSL plugin
-- Pedantic compiler settings enabled
-- Found Python executable: /usr/bin/python2.7
-- Found Python version: 2.7.14
-- Found Python library: /usr/lib/libpython2.7.so
-- Found PyQt4 version: 4.11.4
-- Found SIP version: 4.18
-- Found QScintilla2 PyQt module: 2.9.1
-- Found QwtPolar: /usr/lib/libqwtpolar.so
-- Found GSL: -L/usr/lib -lgsl -lgslcblas -lm
-- txt2tags not found - disabled
-- Configuring done
-- Generating done
-- Build files have been written to: /opt/SBo/qgis-2.18.17/build
[  0%] Built target version
Scanning dependencies of target qgis_core
[  0%] Building CXX object src/core/CMakeFiles/qgis_core.dir/qgis.cpp.o
[  0%] Building CXX object src/core/CMakeFiles/qgis_core.dir/qgserror.cpp.o
[  0%] Linking CXX shared library ../../output/lib/libqgis_core.so
[ 18%] Built target qgis_core
[ 18%] Linking CXX shared library ../../output/lib/libqgis_analysis.so
[ 20%] Built target qgis_analysis
[ 20%] Linking CXX shared library ../../../output/lib/libqgis_networkanalysis.so
[ 21%] Built target qgis_networkanalysis
[ 29%] Built target ui
[ 29%] Linking CXX shared library ../../output/lib/libqgis_gui.so
[ 57%] Built target qgis_gui
[ 57%] Linking CXX shared module ../../../output/lib/qgis/libbasicauthmethod.so
[ 57%] Built target basicauthmethod
[ 57%] Linking CXX shared module ../../../output/lib/qgis/libidentcertauthmethod.so
[ 57%] Built target identcertauthmethod
[ 57%] Linking CXX shared module ../../../output/lib/qgis/libpkipathsauthmethod.so
[ 58%] Built target pkipathsauthmethod
[ 58%] Linking CXX shared module ../../../output/lib/qgis/libpkcs12authmethod.so
[ 58%] Built target pkcs12authmethod
[ 58%] Linking CXX shared module ../../../output/lib/qgis/libarcgisfeatureserverprovider.so
[ 58%] Built target arcgisfeatureserverprovider
[ 59%] Linking CXX shared module ../../../output/lib/qgis/libarcgismapserverprovider.so
[ 59%] Built target arcgismapserverprovider
[ 59%] Linking CXX shared module ../../../output/lib/qgis/libmemoryprovider.so
[ 59%] Built target memoryprovider
[ 59%] Linking CXX shared module ../../../output/lib/qgis/libogrprovider.so
[ 59%] Built target ogrprovider
[ 60%] Built target wmsprovider_a
[ 60%] Linking CXX shared module ../../../output/lib/qgis/libwmsprovider.so
[ 61%] Built target wmsprovider
[ 61%] Linking CXX shared module ../../../output/lib/qgis/libdelimitedtextprovider.so
[ 61%] Built target delimitedtextprovider
[ 61%] Linking CXX shared module ../../../output/lib/qgis/libgdalprovider.so
[ 61%] Built target gdalprovider
[ 61%] Linking CXX shared module ../../../output/lib/qgis/libmssqlprovider.so
[ 61%] Built target mssqlprovider
[ 61%] Linking CXX shared module ../../../output/lib/qgis/libowsprovider.so
[ 61%] Built target owsprovider
[ 61%] Linking CXX shared module ../../../output/lib/qgis/libwcsprovider.so
[ 61%] Built target wcsprovider
[ 61%] Linking CXX shared module ../../../output/lib/qgis/libgpxprovider.so
[ 61%] Built target gpxprovider
[ 61%] Linking CXX shared module ../../../output/lib/qgis/libwfsprovider.so
[ 62%] Built target wfsprovider
[ 62%] Linking CXX shared module ../../../output/lib/qgis/libspatialiteprovider.so
[ 62%] Built target spatialiteprovider
[ 63%] Linking CXX shared module ../../../output/lib/qgis/libvirtuallayerprovider.so
[ 63%] Built target virtuallayerprovider
[ 63%] Linking CXX shared module ../../../output/lib/qgis/libdb2provider.so
[ 64%] Built target db2provider
[ 65%] Linking CXX shared module ../../../output/lib/qgis/libpostgresprovider.so
[ 65%] Built target postgresprovider
[ 65%] Linking CXX executable ../../output/bin/crssync
[ 65%] Built target crssync
[ 66%] Built target libdxfrw
[ 66%] Linking CXX shared library ../../output/lib/libqgis_app.so
[ 82%] Built target qgis_app
Scanning dependencies of target qgis
[ 82%] Building CXX object src/app/CMakeFiles/qgis.dir/main.cpp.o
[ 82%] Linking CXX executable ../../output/bin/qgis
[ 82%] Built target qgis
[ 82%] Linking CXX executable ../../output/lib/qgis/qgis_help
[ 82%] Built target qgis_help
[ 82%] Linking CXX executable ../../output/bin/qbrowser
[ 82%] Built target qbrowser
[ 82%] Linking CXX shared module ../../../output/lib/qgis/libinterpolationplugin.so
[ 83%] Built target interpolationplugin
[ 83%] Linking CXX shared module ../../../output/lib/qgis/liboracleplugin.so
[ 84%] Built target oracleplugin
[ 84%] Linking CXX shared module ../../../output/lib/qgis/librasterterrainplugin.so
[ 84%] Built target rasterterrainplugin
[ 84%] Linking CXX shared module ../../../output/lib/qgis/libcoordinatecaptureplugin.so
[ 84%] Built target coordinatecaptureplugin
[ 84%] Linking CXX shared module ../../../output/lib/qgis/libdxf2shpconverterplugin.so
[ 85%] Built target dxf2shpconverterplugin
[ 85%] Linking CXX shared module ../../../output/lib/qgis/libevis.so
[ 86%] Built target evis
[ 86%] Linking CXX shared module ../../../output/lib/qgis/libspatialqueryplugin.so
[ 87%] Built target spatialqueryplugin
[ 87%] Linking CXX shared module ../../../output/lib/qgis/libroadgraphplugin.so
[ 88%] Built target roadgraphplugin
[ 88%] Linking CXX shared module ../../../output/lib/qgis/libzonalstatisticsplugin.so
[ 88%] Built target zonalstatisticsplugin
[ 88%] Linking CXX shared module ../../../output/lib/qgis/libgeorefplugin.so
[ 90%] Built target georefplugin
[ 91%] Linking CXX shared module ../../../output/lib/qgis/libgpsimporterplugin.so
[ 91%] Built target gpsimporterplugin
[ 91%] Linking CXX shared module ../../../output/lib/qgis/libtopolplugin.so
[ 92%] Built target topolplugin
[ 92%] Linking CXX shared module ../../../output/lib/qgis/libofflineeditingplugin.so
[ 93%] Built target offlineeditingplugin
[ 93%] Linking CXX shared module ../../../output/lib/qgis/libheatmapplugin.so
[ 93%] Built target heatmapplugin
[ 93%] Linking CXX shared module ../../../output/lib/qgis/libgeometrycheckerplugin.so
[ 95%] Built target geometrycheckerplugin
[ 95%] Linking CXX shared module ../../../output/lib/qgis/libgeometrysnapperplugin.so
[ 96%] Built target geometrysnapperplugin
[ 96%] Linking CXX shared library ../../output/lib/libqgispython.so
[ 96%] Built target qgispython
[ 97%] Built target translations
[ 97%] Linking CXX shared module ../output/python/qgis/_analysis.so
[ 97%] Built target python_module_qgis__analysis
[ 97%] Linking CXX shared module ../output/python/qgis/_gui.so
[ 97%] Built target python_module_qgis__gui
[ 97%] Built target pysix
Scanning dependencies of target zzz-GdalTools-3-depend
[ 97%] Built target zzz-GdalTools-3-depend
Scanning dependencies of target zzz-GdalTools-1-depend
[ 97%] Generating resources_rc.py
[ 97%] Built target zzz-GdalTools-1-depend
[ 97%] Built target pyutils
[ 97%] Built target pyqtcompat
[ 97%] Built target pygui
[ 97%] Linking CXX shared module ../output/python/qgis/_core.so
[ 97%] Built target python_module_qgis__core
[ 97%] Built target pycore
Scanning dependencies of target zzz-GdalTools-2-depend
[ 97%] Generating ui_widgetSieve.py
python/plugins/GdalTools/tools/CMakeFiles/zzz-GdalTools-2-depend.dir/build.make:117: recipe for target 'python/plugins/GdalTools/tools/ui_widgetSieve.py' failed
CMakeFiles/Makefile2:4276: recipe for target 'python/plugins/GdalTools/tools/CMakeFiles/zzz-GdalTools-2-depend.dir/all' failed
Makefile:149: recipe for target 'all' failed

From slackbuilds at jaxartes.net  Wed Mar  7 03:08:04 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Tue, 06 Mar 2018 19:08:04 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <alpine.LNX.2.20.1803061809450.28861@salmo.appl-ecosys.com>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <3062690.X610dqcBXX@wintermute.sprawl.net>
 <alpine.LNX.2.20.1803061809450.28861@salmo.appl-ecosys.com>
Message-ID: <1733507.ipU4MVEUpB@wintermute.sprawl.net>

On Tuesday, 6 March 2018 18:13:18 PST Rich Shepard wrote:
> On Tue, 6 Mar 2018, Benjamin Trigona-Harany wrote:
> > rm -r python/plugins/GdalTools
> > make > output.log
> 
> Ben,
> 
>    Log file (about 3k smaller) is attached, and I think I see the problem.
> On the v.t. I see:
> 
> /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../../i586-slackware-linux/bin
> /ld: warning: libproj.so.12, needed by
> /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../libspatialite.so, not
> found (try using -rpath or -rpath-link)
> /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../../i586-slackware-linux/bi
> n/ld: warning: libproj.so.12, needed by
> /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../libspatialite.so, not
> found (try using -rpath or -rpath-link)
> /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../../i586-slackware-linux/bi
> n/ld: warning: libproj.so.12, needed by
> /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../libspatialite.so, not
> found (try using -rpath or -rpath-link)
> /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../../i586-slackware-linux/bi
> n/ld: warning: libproj.so.12, needed by
> /usr/lib/gcc/i586-slackware-linux/5.5.0/../../../libspatialite.so, not
> found (try using -rpath or -rpath-link) Traceback (most recent call last):
>    File "../../../../../scripts/pyuic-wrapper.py", line 26, in <module>
>      import qgis.PyQt.uic.pyuic
>    File "/opt/SBo/qgis-2.18.17/build/output/python/qgis/__init__.py", line
> 27, in <module> from qgis.core import QgsFeature, QgsGeometry
>    File "/opt/SBo/qgis-2.18.17/build/output/python/qgis/core/__init__.py",
> line 30, in <module> from qgis._core import *
> ImportError: libproj.so.12: cannot open shared object file: No such file or
> directory make[2]: *** [python/plugins/GdalTools/tools/ui_widgetSieve.py]
> Error 1 make[1]: ***
> [python/plugins/GdalTools/tools/CMakeFiles/zzz-GdalTools-2-depend.dir/all]
> Error 2 make: *** [all] Error 2
> 
> and the build is looking for libproj.so.12. Here, libproj-4.4.7-i486-2 is
> installed and provides /usr/lib/libproj.so.13.
> 
> HTH,
> 
> Rich

Is it possible you installed proj 5.0.0? In any case, you've probably upgraded 
proj at some point and not recompiled everything that depends on it (at least 
gdal, libspatialite and postgis).

Rebuild those and try QGIS again and I'm betting it also builds.




From falsetti at clansco.org  Wed Mar  7 05:01:41 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Wed, 7 Mar 2018 06:01:41 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <1729579.Ot8fpvbGVj@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <1936644.pNfofqWnVg@wintermute.sprawl.net>
 <20180306172509.e215ae2552a0fac3dd56c233@clansco.org>
 <1729579.Ot8fpvbGVj@wintermute.sprawl.net>
Message-ID: <20180307060141.d3201b11b8d1e52aa95c90e2@clansco.org>

On Tue, 06 Mar 2018 12:11:31 -0800
Benjamin Trigona-Harany <slackbuilds at jaxartes.net> wrote:


> 
> Can you try inserting the following two lines in the build script immediately 
> before the "python3 configure.py ..." line?
> 
> sed -i "1423i\    pro.write('INCLUDEPATH += /usr/include/qt5/QtWidgets\\\n')" 
> configure.py
> sed -i "1423i\    pro.write('INCLUDEPATH += /usr/include/qt5/QtPrintSupport\\
> \n')" configure.py
> 
> For some reason this is not necessary on my x86_64 install. qmake-qt5 
> automatically adds the right include paths but not for you. I hope these lines 
> will be enough.

thanks Benjamin, it works!
QScintilla-qt5-2.10.2-i586-1_SBo.tgz installed

From falsetti at clansco.org  Wed Mar  7 07:18:11 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Wed, 7 Mar 2018 08:18:11 +0100
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <20180307060141.d3201b11b8d1e52aa95c90e2@clansco.org>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <1936644.pNfofqWnVg@wintermute.sprawl.net>
 <20180306172509.e215ae2552a0fac3dd56c233@clansco.org>
 <1729579.Ot8fpvbGVj@wintermute.sprawl.net>
 <20180307060141.d3201b11b8d1e52aa95c90e2@clansco.org>
Message-ID: <20180307081811.9d80a65f1641d3ab3c359aa5@clansco.org>

Package qgis3-3.0.0-i586-1_SBo.tgz installed

 thanks Benjamin!

From rshepard at appl-ecosys.com  Wed Mar  7 17:10:10 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 7 Mar 2018 09:10:10 -0800 (PST)
Subject: [Slackbuilds-users] QGIS 3 on Slackware [FIXED]
In-Reply-To: <1733507.ipU4MVEUpB@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <3062690.X610dqcBXX@wintermute.sprawl.net>
 <alpine.LNX.2.20.1803061809450.28861@salmo.appl-ecosys.com>
 <1733507.ipU4MVEUpB@wintermute.sprawl.net>
Message-ID: <alpine.LNX.2.20.1803070905260.10363@salmo.appl-ecosys.com>

On Tue, 6 Mar 2018, Benjamin Trigona-Harany wrote:

> Is it possible you installed proj 5.0.0? In any case, you've probably
> upgraded proj at some point and not recompiled everything that depends on
> it (at least gdal, libspatialite and postgis).

Ben,

  Yes, proj-5.0.0 is installed, and the latest packages for gdal,
libspatialite, and postgis are shown as present in /var/log/packages.
Unfortunately, not only did the kernel upgrade to 4.4.118 remove the gdal
executable (which I built and re-installed yesterday), but it also borked
the libspatialite and postgis executables.

> Rebuild those and try QGIS again and I'm betting it also builds.

   I rebuilt and re-installed libspatialite and postgis and you're correct,
qgis now built to completion and allowed me to upgrade the version.

   I caught the gdal issue yesterday when attemting to build the latest grass
version, but did not check the other qgis dependencies.

Thanks for your help,

Rich

From slackbuilds at jaxartes.net  Wed Mar  7 17:42:50 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Wed, 07 Mar 2018 09:42:50 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware [FIXED]
In-Reply-To: <alpine.LNX.2.20.1803070905260.10363@salmo.appl-ecosys.com>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <1733507.ipU4MVEUpB@wintermute.sprawl.net>
 <alpine.LNX.2.20.1803070905260.10363@salmo.appl-ecosys.com>
Message-ID: <4912632.AhNjaY6FMb@wintermute.sprawl.net>

On Wednesday, 7 March 2018 09:10:10 PST Rich Shepard wrote:
>   Yes, proj-5.0.0 is installed, and the latest packages for gdal,
> libspatialite, and postgis are shown as present in /var/log/packages.
> Unfortunately, not only did the kernel upgrade to 4.4.118 remove the gdal
> executable (which I built and re-installed yesterday), but it also borked
> the libspatialite and postgis executables.

I can't say what's happening on your system but I doubt that a new kernel 
would break gdal, spatialite and postgis, whereas I know that a proj upgrade 
to version 5.0.0 would break all three of them.



From rshepard at appl-ecosys.com  Wed Mar  7 17:41:47 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 7 Mar 2018 09:41:47 -0800 (PST)
Subject: [Slackbuilds-users] QGIS 3 on Slackware [FIXED]
In-Reply-To: <4912632.AhNjaY6FMb@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
 <1733507.ipU4MVEUpB@wintermute.sprawl.net>
 <alpine.LNX.2.20.1803070905260.10363@salmo.appl-ecosys.com>
 <4912632.AhNjaY6FMb@wintermute.sprawl.net>
Message-ID: <alpine.LNX.2.20.1803070940370.10363@salmo.appl-ecosys.com>

On Wed, 7 Mar 2018, Benjamin Trigona-Harany wrote:

> I can't say what's happening on your system but I doubt that a new kernel
> would break gdal, spatialite and postgis, whereas I know that a proj
> upgrade to version 5.0.0 would break all three of them.

Ben,

   I did the kernel upgrade recently; don't recall when I upgraded proj. But,
I'll accept your explanation and be aware of this when proj is again
upgraded.

Thanks again,

Rich

From ewj at pigs.ag  Thu Mar  8 08:45:06 2018
From: ewj at pigs.ag (E. Wayne Johnson)
Date: Thu, 8 Mar 2018 16:45:06 +0800
Subject: [Slackbuilds-users] strongswan
Message-ID: <d22ecf6d-d73e-bf51-b43d-78174ce47d83@pigs.ag>

The SlackBuild for strongswan (5.3.4) does not build under -current but 
fails with errors.

I found nothing for strongswan in Ponce's -current SlackBuilds repo.

Substituting the most recent version of strongswan 
(https://download.strongswan.org/strongswan-5.6.2.tar.gz)
does work with the SlackBuild after a change of the strongswan version 
to 5.6.2 resulting in functional package.

EWJ

From ewj at pigs.ag  Thu Mar  8 08:52:25 2018
From: ewj at pigs.ag (E. Wayne Johnson)
Date: Thu, 8 Mar 2018 16:52:25 +0800
Subject: [Slackbuilds-users] Rstudio
In-Reply-To: <mailman.4105.1520175786.21966.slackbuilds-users@slackbuilds.org>
References: <mailman.4105.1520175786.21966.slackbuilds-users@slackbuilds.org>
Message-ID: <d1c7f21d-ae56-96f9-c4c5-77060b1bf80a@pigs.ag>

slackbuilds-users-request at slackbuilds.org wrote:
> Date: Sun, 4 Mar 2018 05:23:06 +0700
> From: Willy Sudiarto Raharjo<willysr at slackbuilds.org>
> To:slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] Rstudio
> Message-ID:<867b1808-8096-ac70-7905-f09a646585e5 at slackbuilds.org>
> Content-Type: text/plain; charset="utf-8"
>
>> The Slackbuild for Rstudio fails compilation with a series of boost errors.
>>
>> Others have reported this problem.
>>
>> See:
>>
>> https://www.linuxquestions.org/questions/slackware-14/rstudio-compile-fails-on-current-4175571764/
> Have you tried to compile on -stable?
> Remember that SBo targets for -stable, not -current
 From the SlackBuilds FAQ:

15.? For what version of Slackware are these scripts designed? Will they 
work on newer versions?

  * All of our scripts should work with the most recently released
    version of Slackware; if this is not the case, you should file a Bug
    Report <https://slackbuilds.org/bugs/>. Except as noted in the next
    FAQ entry <https://slackbuilds.org/faq/#older>, the scripts should
    also work on older versions of Slackware. /*Slackware -current is
    not supported, but as a general rule, the scripts should work on it
    as well.*/

/**
*/Questions:

Can it be considered a bug?

Should SlackBuilds.org website include a link to Ponce's alternatives, 
for the benefit
of those who do not regularly follow LinuxQuestions?

More seriously, thanks for all your help.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180308/9a1a9a24/attachment.html>

From matteo.bernardini at gmail.com  Thu Mar  8 08:56:39 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 8 Mar 2018 09:56:39 +0100
Subject: [Slackbuilds-users] Rstudio
In-Reply-To: <d1c7f21d-ae56-96f9-c4c5-77060b1bf80a@pigs.ag>
References: <mailman.4105.1520175786.21966.slackbuilds-users@slackbuilds.org>
 <d1c7f21d-ae56-96f9-c4c5-77060b1bf80a@pigs.ag>
Message-ID: <CAPsDuS6uoQc++1kLbeoz+ycYX04JaL_q_hC0_9oS4CBdMjXftQ@mail.gmail.com>

2018-03-08 9:52 GMT+01:00 E. Wayne Johnson <ewj at pigs.ag>:
> From the SlackBuilds FAQ:
>
> 15.  For what version of Slackware are these scripts designed? Will they
> work on newer versions?
>
> All of our scripts should work with the most recently released version of
> Slackware; if this is not the case, you should file a Bug Report. Except as
> noted in the next FAQ entry, the scripts should also work on older versions
> of Slackware. Slackware -current is not supported, but as a general rule,
> the scripts should work on it as well.
>
> *
> Questions:
>
> Can it be considered a bug?

no, because it works on stable.

> Should SlackBuilds.org website include a link to Ponce's alternatives, for
> the benefit
> of those who do not regularly follow LinuxQuestions?

IMHO it shouldn't because that unofficial fork is not supported or
endorsed by SlackBuilds.org.

Matteo

P.S. rstudio-desktop is up for grabs for whoever wants to maintain it.

From matteo.bernardini at gmail.com  Thu Mar  8 09:01:00 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 8 Mar 2018 10:01:00 +0100
Subject: [Slackbuilds-users] strongswan
In-Reply-To: <d22ecf6d-d73e-bf51-b43d-78174ce47d83@pigs.ag>
References: <d22ecf6d-d73e-bf51-b43d-78174ce47d83@pigs.ag>
Message-ID: <CAPsDuS69Ow2W2KthjhGKOhWMWzEcy8pdJ5b982QKDA43y-_FEg@mail.gmail.com>

2018-03-08 9:45 GMT+01:00 E. Wayne Johnson <ewj at pigs.ag>:
> The SlackBuild for strongswan (5.3.4) does not build under -current but
> fails with errors.
>
> I found nothing for strongswan in Ponce's -current SlackBuilds repo.
>
> Substituting the most recent version of strongswan
> (https://download.strongswan.org/strongswan-5.6.2.tar.gz)
> does work with the SlackBuild after a change of the strongswan version to
> 5.6.2 resulting in functional package.

hi EWJ,

thanks for reporting but, as I wrote in the other email thread that
you started, you should point out issues with stuff not building in
current in the appropriate LQ thread.

From ekinakoglu at gmail.com  Thu Mar  8 10:26:26 2018
From: ekinakoglu at gmail.com (Ekin Akoglu)
Date: Thu, 8 Mar 2018 13:26:26 +0300
Subject: [Slackbuilds-users] Rstudio
In-Reply-To: <CAPsDuS6uoQc++1kLbeoz+ycYX04JaL_q_hC0_9oS4CBdMjXftQ@mail.gmail.com>
References: <mailman.4105.1520175786.21966.slackbuilds-users@slackbuilds.org>
 <d1c7f21d-ae56-96f9-c4c5-77060b1bf80a@pigs.ag>
 <CAPsDuS6uoQc++1kLbeoz+ycYX04JaL_q_hC0_9oS4CBdMjXftQ@mail.gmail.com>
Message-ID: <00d9288a-ea24-c51e-eff1-8f051a681d65@gmail.com>

I would like to take it, if no one else has already grabbed it.

Best,

Ekin


On 08/03/18 11:56, Matteo Bernardini wrote:
> 2018-03-08 9:52 GMT+01:00 E. Wayne Johnson <ewj at pigs.ag>:
>>  From the SlackBuilds FAQ:
>>
>> 15.  For what version of Slackware are these scripts designed? Will they
>> work on newer versions?
>>
>> All of our scripts should work with the most recently released version of
>> Slackware; if this is not the case, you should file a Bug Report. Except as
>> noted in the next FAQ entry, the scripts should also work on older versions
>> of Slackware. Slackware -current is not supported, but as a general rule,
>> the scripts should work on it as well.
>>
>> *
>> Questions:
>>
>> Can it be considered a bug?
> no, because it works on stable.
>
>> Should SlackBuilds.org website include a link to Ponce's alternatives, for
>> the benefit
>> of those who do not regularly follow LinuxQuestions?
> IMHO it shouldn't because that unofficial fork is not supported or
> endorsed by SlackBuilds.org.
>
> Matteo
>
> P.S. rstudio-desktop is up for grabs for whoever wants to maintain it.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


From matteo.bernardini at gmail.com  Thu Mar  8 11:11:07 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 8 Mar 2018 12:11:07 +0100
Subject: [Slackbuilds-users] Rstudio
In-Reply-To: <00d9288a-ea24-c51e-eff1-8f051a681d65@gmail.com>
References: <mailman.4105.1520175786.21966.slackbuilds-users@slackbuilds.org>
 <d1c7f21d-ae56-96f9-c4c5-77060b1bf80a@pigs.ag>
 <CAPsDuS6uoQc++1kLbeoz+ycYX04JaL_q_hC0_9oS4CBdMjXftQ@mail.gmail.com>
 <00d9288a-ea24-c51e-eff1-8f051a681d65@gmail.com>
Message-ID: <CAPsDuS6SSoPDTU-Hx_HcOzbGZGBHraihk3xHvUhq1ePO8zy+ag@mail.gmail.com>

2018-03-08 11:26 GMT+01:00 Ekin Akoglu <ekinakoglu at gmail.com>:
> I would like to take it, if no one else has already grabbed it.
>
> On 08/03/18 11:56, Matteo Bernardini wrote:
>> P.S. rstudio-desktop is up for grabs for whoever wants to maintain it.

it's yours: it isn't updated since four years so I think an up-to-date
version will be welcomed!

From ekinakoglu at gmail.com  Thu Mar  8 11:28:59 2018
From: ekinakoglu at gmail.com (Ekin Akoglu)
Date: Thu, 8 Mar 2018 14:28:59 +0300
Subject: [Slackbuilds-users] Rstudio
In-Reply-To: <CAPsDuS6SSoPDTU-Hx_HcOzbGZGBHraihk3xHvUhq1ePO8zy+ag@mail.gmail.com>
References: <mailman.4105.1520175786.21966.slackbuilds-users@slackbuilds.org>
 <d1c7f21d-ae56-96f9-c4c5-77060b1bf80a@pigs.ag>
 <CAPsDuS6uoQc++1kLbeoz+ycYX04JaL_q_hC0_9oS4CBdMjXftQ@mail.gmail.com>
 <00d9288a-ea24-c51e-eff1-8f051a681d65@gmail.com>
 <CAPsDuS6SSoPDTU-Hx_HcOzbGZGBHraihk3xHvUhq1ePO8zy+ag@mail.gmail.com>
Message-ID: <03015881-4365-3c13-f581-38212a138255@gmail.com>

Sure, I will work on it, but it will take a little while though.

Best,

Ekin


On 08/03/18 14:11, Matteo Bernardini wrote:
> 2018-03-08 11:26 GMT+01:00 Ekin Akoglu <ekinakoglu at gmail.com>:
>> I would like to take it, if no one else has already grabbed it.
>>
>> On 08/03/18 11:56, Matteo Bernardini wrote:
>>> P.S. rstudio-desktop is up for grabs for whoever wants to maintain it.
> it's yours: it isn't updated since four years so I think an up-to-date
> version will be welcomed!
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


From artourter at gmail.com  Thu Mar  8 14:52:16 2018
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Thu, 8 Mar 2018 14:52:16 +0000
Subject: [Slackbuilds-users] Rstudio
In-Reply-To: <03015881-4365-3c13-f581-38212a138255@gmail.com>
References: <mailman.4105.1520175786.21966.slackbuilds-users@slackbuilds.org>
 <d1c7f21d-ae56-96f9-c4c5-77060b1bf80a@pigs.ag>
 <CAPsDuS6uoQc++1kLbeoz+ycYX04JaL_q_hC0_9oS4CBdMjXftQ@mail.gmail.com>
 <00d9288a-ea24-c51e-eff1-8f051a681d65@gmail.com>
 <CAPsDuS6SSoPDTU-Hx_HcOzbGZGBHraihk3xHvUhq1ePO8zy+ag@mail.gmail.com>
 <03015881-4365-3c13-f581-38212a138255@gmail.com>
Message-ID: <CAK09-vkxhwgZLYa6xcFhMAi-rGjQ54Ju44=oNcRLhL2Bw=kJ0g@mail.gmail.com>

The new version require qt5 btw. I have manage to make it work recently if
that is of interest

Greg

On 8 March 2018 at 11:28, Ekin Akoglu <ekinakoglu at gmail.com> wrote:

> Sure, I will work on it, but it will take a little while though.
>
> Best,
>
> Ekin
>
>
>
> On 08/03/18 14:11, Matteo Bernardini wrote:
>
>> 2018-03-08 11:26 GMT+01:00 Ekin Akoglu <ekinakoglu at gmail.com>:
>>
>>> I would like to take it, if no one else has already grabbed it.
>>>
>>> On 08/03/18 11:56, Matteo Bernardini wrote:
>>>
>>>> P.S. rstudio-desktop is up for grabs for whoever wants to maintain it.
>>>>
>>> it's yours: it isn't updated since four years so I think an up-to-date
>> version will be welcomed!
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180308/0203570f/attachment.html>

From ekinakoglu at gmail.com  Thu Mar  8 16:22:14 2018
From: ekinakoglu at gmail.com (Ekin Akoglu)
Date: Thu, 08 Mar 2018 16:22:14 +0000
Subject: [Slackbuilds-users] Rstudio
In-Reply-To: <CAK09-vkxhwgZLYa6xcFhMAi-rGjQ54Ju44=oNcRLhL2Bw=kJ0g@mail.gmail.com>
References: <mailman.4105.1520175786.21966.slackbuilds-users@slackbuilds.org>
 <d1c7f21d-ae56-96f9-c4c5-77060b1bf80a@pigs.ag>
 <CAPsDuS6uoQc++1kLbeoz+ycYX04JaL_q_hC0_9oS4CBdMjXftQ@mail.gmail.com>
 <00d9288a-ea24-c51e-eff1-8f051a681d65@gmail.com>
 <CAPsDuS6SSoPDTU-Hx_HcOzbGZGBHraihk3xHvUhq1ePO8zy+ag@mail.gmail.com>
 <03015881-4365-3c13-f581-38212a138255@gmail.com>
 <CAK09-vkxhwgZLYa6xcFhMAi-rGjQ54Ju44=oNcRLhL2Bw=kJ0g@mail.gmail.com>
Message-ID: <CAJXHm+KSSN2Ub88M90bpsJUE-JdakEFhKLBPKxqDnQR46Xm1mA@mail.gmail.com>

Thank you, Greg. That's why I repackaged the Debian binary, which is
statically linked to the dependencies. You can find it in pending
submissions and If you have time you may test it if it works for you.

Best,

Ekin

On Thu, 8 Mar 2018, 17:52 Greg' Ar Tourter, <artourter at gmail.com> wrote:

> The new version require qt5 btw. I have manage to make it work recently if
> that is of interest
>
> Greg
>
> On 8 March 2018 at 11:28, Ekin Akoglu <ekinakoglu at gmail.com> wrote:
>
>> Sure, I will work on it, but it will take a little while though.
>>
>> Best,
>>
>> Ekin
>>
>>
>>
>> On 08/03/18 14:11, Matteo Bernardini wrote:
>>
>>> 2018-03-08 11:26 GMT+01:00 Ekin Akoglu <ekinakoglu at gmail.com>:
>>>
>>>> I would like to take it, if no one else has already grabbed it.
>>>>
>>>> On 08/03/18 11:56, Matteo Bernardini wrote:
>>>>
>>>>> P.S. rstudio-desktop is up for grabs for whoever wants to maintain it.
>>>>>
>>>> it's yours: it isn't updated since four years so I think an up-to-date
>>> version will be welcomed!
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180308/b526c4c5/attachment.html>

From slackbuilds at jaxartes.net  Thu Mar  8 18:25:46 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Thu, 08 Mar 2018 10:25:46 -0800
Subject: [Slackbuilds-users] QGIS 3 on Slackware
In-Reply-To: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
References: <15224385.AzDNfkVVfH@wintermute.sprawl.net>
Message-ID: <1975647.qYLSqbDtTa@wintermute.sprawl.net>

Update on QGIS 3: I've made a few fixes to the build process, and there are 
now two README files in the repository (https://github.com/bosth/qgis3-slackbuild), one for 14.2 and one for current.

QGIS 3 is now building and running on the following configurations:

- Slackware64 14.2
- Slackware 14.2 (thanks to Fr?d?ric)
- Slackware64 current
- Slackware64 current + ktown

I've also updated the remaining SlackBuilds that needed Python 3 support so 
that all of the default plugins work.

If there are any more questions or issues, contact me on/off list or file a 
GitHub issue.

Ben



From xavier at maillard.im  Tue Mar  6 12:14:19 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Tue, 06 Mar 2018 13:14:19 +0100
Subject: [Slackbuilds-users] Out of space when building RUST ?
Message-ID: <87k1up5rl0.fsf@maillard.im>

Hello,

I've tried twice to build rust (it is a dependancy of ripgrep 
sadly) and it failed twice in a row. The problem, I going out of 
space.

Here is my root dev:

Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p7   20G   15G  4.5G  76% /

4,5G is not enough ?! Does anybody know how large should it be ?

Regards
--
Xaver

From aclemons at runbox.no  Fri Mar  9 00:18:59 2018
From: aclemons at runbox.no (Andrew Clemons)
Date: Fri, 9 Mar 2018 13:18:59 +1300
Subject: [Slackbuilds-users] Out of space when building RUST ?
In-Reply-To: <87k1up5rl0.fsf@maillard.im>
References: <87k1up5rl0.fsf@maillard.im>
Message-ID: <20180309001858.GA25116@runbox.no>

On 2018-03-06 13:14:19 +0100, xavier at maillard.im wrote:
> [...]
> 4,5G is not enough ?! Does anybody know how large should it be ?

I have this in my build logs:

x86_64:
Build time 70 min, peak load 10.23, peak memory 3477M, peak tmp 6691M

x86:
Build time 96 min, peak load 10.12, peak memory 2447M, peak tmp 6684M

Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180309/b7e130d1/attachment-0001.asc>

From thedoogster at gmail.com  Fri Mar  9 00:37:34 2018
From: thedoogster at gmail.com (Doogster)
Date: Thu, 8 Mar 2018 16:37:34 -0800
Subject: [Slackbuilds-users] Out of space when building RUST ?
In-Reply-To: <20180309001858.GA25116@runbox.no>
References: <87k1up5rl0.fsf@maillard.im> <20180309001858.GA25116@runbox.no>
Message-ID: <CAE5oDaak3VxK=OoTMWSa6oP=vWZoTXaQt0kk4y4KvFV7EuU_Vw@mail.gmail.com>

Here's my SlackBuild to download and package the latest binary RipGrep
release. I've only tried it on -current, but no reason to believe it
won't work on 14.1 (Rust is not a runtime dependency).

https://raw.githubusercontent.com/duganchen/my_slackbuilds/master/ripgrep.SlackBuild

On Thu, Mar 8, 2018 at 4:18 PM, Andrew Clemons <aclemons at runbox.no> wrote:
> On 2018-03-06 13:14:19 +0100, xavier at maillard.im wrote:
>> [...]
>> 4,5G is not enough ?! Does anybody know how large should it be ?
>
> I have this in my build logs:
>
> x86_64:
> Build time 70 min, peak load 10.23, peak memory 3477M, peak tmp 6691M
>
> x86:
> Build time 96 min, peak load 10.12, peak memory 2447M, peak tmp 6684M
>
> Andrew
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

From yalhcru at gmail.com  Fri Mar  9 00:53:52 2018
From: yalhcru at gmail.com (B Watson)
Date: Thu, 8 Mar 2018 19:53:52 -0500
Subject: [Slackbuilds-users] Out of space when building RUST ?
In-Reply-To: <20180309001858.GA25116@runbox.no>
References: <87k1up5rl0.fsf@maillard.im> <20180309001858.GA25116@runbox.no>
Message-ID: <CAN1hMuAR_D59KV584PnFZtG3qKrpws75mBhfOmT2HE3vd7JP6g@mail.gmail.com>

On 3/8/18, Andrew Clemons <aclemons at runbox.no> wrote:

> x86_64:
> Build time 70 min, peak load 10.23, peak memory 3477M, peak tmp 6691M
>
> x86:
> Build time 96 min, peak load 10.12, peak memory 2447M, peak tmp 6684M

It'd be nice if builds like this would actually mention the amount of
space required in the README... some do already. Probably should be a rule
of thumb that if it takes more than 2GB in /tmp, a note should be made in
the README... 2GB may sound small, but some people mount tmpfs on /tmp,
which has a capacity of half the RAM in the machine by default. Lots of
users still chugging along with only 4GB of RAM.

From xavier at maillard.im  Fri Mar  9 05:45:49 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Fri, 09 Mar 2018 06:45:49 +0100
Subject: [Slackbuilds-users] Out of space when building RUST ?
In-Reply-To: <20180309001858.GA25116@runbox.no>
References: <87k1up5rl0.fsf@maillard.im> <20180309001858.GA25116@runbox.no>
Message-ID: <87ina5x0mq.fsf@maillard.im>


Andrew Clemons <aclemons at runbox.no> writes:

> On 2018-03-06 13:14:19 +0100, xavier at maillard.im wrote:
>> [...]
>> 4,5G is not enough ?! Does anybody know how large should it be 
>> ?
>
> I have this in my build logs:
>
> x86_64:
> Build time 70 min, peak load 10.23, peak memory 3477M, peak tmp 
> 6691M
>
> x86:
> Build time 96 min, peak load 10.12, peak memory 2447M, peak tmp 
> 6684M

Thank you Andrew. I can't build Rust here then :/

--
Xavier

From xavier at maillard.im  Fri Mar  9 05:49:20 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Fri, 09 Mar 2018 06:49:20 +0100
Subject: [Slackbuilds-users] Out of space when building RUST ?
In-Reply-To: <CAN1hMuAR_D59KV584PnFZtG3qKrpws75mBhfOmT2HE3vd7JP6g@mail.gmail.com>
References: <87k1up5rl0.fsf@maillard.im> <20180309001858.GA25116@runbox.no>
 <CAN1hMuAR_D59KV584PnFZtG3qKrpws75mBhfOmT2HE3vd7JP6g@mail.gmail.com>
Message-ID: <87h8ppx0gv.fsf@maillard.im>


B Watson <yalhcru at gmail.com> writes:

> On 3/8/18, Andrew Clemons <aclemons at runbox.no> wrote:
>
>> x86_64:
>> Build time 70 min, peak load 10.23, peak memory 3477M, peak tmp 
>> 6691M
>>
>> x86:
>> Build time 96 min, peak load 10.12, peak memory 2447M, peak tmp 
>> 6684M
>
> It'd be nice if builds like this would actually mention the 
> amount of
> space required in the README... some do already. Probably should 
> be a rule
> of thumb that if it takes more than 2GB in /tmp, a note should 
> be made in
> the README... 2GB may sound small, but some people mount tmpfs 
> on /tmp,
> which has a capacity of half the RAM in the machine by 
> default. Lots of
> users still chugging along with only 4GB of RAM.

I second that. We should indicate this for really extraordinary 
cases requiring a lot of resources.

Rust is the perfect candidate here.

--
Xavier

From xavier at maillard.im  Fri Mar  9 06:08:26 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Fri, 09 Mar 2018 07:08:26 +0100
Subject: [Slackbuilds-users] Out of space when building RUST ?
In-Reply-To: <CAE5oDaak3VxK=OoTMWSa6oP=vWZoTXaQt0kk4y4KvFV7EuU_Vw@mail.gmail.com>
References: <87k1up5rl0.fsf@maillard.im> <20180309001858.GA25116@runbox.no>
 <CAE5oDaak3VxK=OoTMWSa6oP=vWZoTXaQt0kk4y4KvFV7EuU_Vw@mail.gmail.com>
Message-ID: <87fu59wzl1.fsf@maillard.im>

Hello Doogster,

Doogster <thedoogster at gmail.com> writes:

> Here's my SlackBuild to download and package the latest binary 
> RipGrep
> release. I've only tried it on -current, but no reason to 
> believe it
> won't work on 14.1 (Rust is not a runtime dependency).
>
> https://raw.githubusercontent.com/duganchen/my_slackbuilds/master/ripgrep.SlackBuild

Thank you very much. I wish I would have seen that Rust was not a 
runtime dependency before trying to build it.
Anyway, your SBo script works perfectly on my 14.2 install.

--
Xavier

From aclemons at runbox.no  Fri Mar  9 06:40:39 2018
From: aclemons at runbox.no (Andrew Clemons)
Date: Fri, 9 Mar 2018 19:40:39 +1300
Subject: [Slackbuilds-users] Out of space when building RUST ?
In-Reply-To: <87h8ppx0gv.fsf@maillard.im>
References: <87k1up5rl0.fsf@maillard.im> <20180309001858.GA25116@runbox.no>
 <CAN1hMuAR_D59KV584PnFZtG3qKrpws75mBhfOmT2HE3vd7JP6g@mail.gmail.com>
 <87h8ppx0gv.fsf@maillard.im>
Message-ID: <20180309064038.GA22904@runbox.no>

On 2018-03-09 06:49:20 +0100, xavier at maillard.im wrote:
> > It'd be nice if builds like this would actually mention the amount of
> > space required in the README... some do already. Probably should be a
> > [...]
>
> I second that. We should indicate this for really extraordinary cases
> requiring a lot of resources.
> [...]

I?ve added a note for rust on my branch.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180309/d8d37a74/attachment.asc>

From aclemons at runbox.no  Fri Mar  9 06:49:32 2018
From: aclemons at runbox.no (Andrew Clemons)
Date: Fri, 9 Mar 2018 19:49:32 +1300
Subject: [Slackbuilds-users] Out of space when building RUST ?
In-Reply-To: <87fu59wzl1.fsf@maillard.im>
References: <87k1up5rl0.fsf@maillard.im> <20180309001858.GA25116@runbox.no>
 <CAE5oDaak3VxK=OoTMWSa6oP=vWZoTXaQt0kk4y4KvFV7EuU_Vw@mail.gmail.com>
 <87fu59wzl1.fsf@maillard.im>
Message-ID: <20180309064931.GB22904@runbox.no>

On 2018-03-09 07:08:26 +0100, xavier at maillard.im wrote:
> [...]
> Thank you very much. I wish I would have seen that Rust was not a
> runtime dependency before trying to build it.
> [...]

I have a note on a couple of my slackbuilds which use rust mentioning
that you only need rust to build and that it can be safely removed
after, i.e. here?. I'll add a similar note to ripgrep too.

It doesn?t really help in your case though, since you'd still have to
build rust to build ripgrep. But yes, you can use the binaries
BurntSushi provides on the project page without having rust installed.

Andrew

? https://slackbuilds.org/repository/14.2/system/vtcol/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180309/909058ee/attachment.asc>

From didier at slint.fr  Fri Mar  9 09:36:25 2018
From: didier at slint.fr (Didier Spaier)
Date: Fri, 9 Mar 2018 10:36:25 +0100
Subject: [Slackbuilds-users] Error compiling webkitgtk
Message-ID: <a87ee754-19bd-5f30-2d37-a51c1cbde832@slint.fr>

Hello,

I apologize if this is the wrong place to ask.

I ma trying to compile webkit2gtk 2.8.26 statically and stripped down, just to afterwards bundling it with yelp without this resulting in a too huge package.

In that aim I have written the attached build script that removes a lot of features that I assume yelp doesn't need.

However the build fails at around 94% completion (end of log attached)

I have tried with -j2 and -j1, same result.

However, I previously built it successfully, but full featured and shared.

A web search came empty.

Any clue appreciated.

Have a good day,

Diider



From fernando.lopezjr at gmail.com  Fri Mar  9 09:39:23 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Fri, 9 Mar 2018 02:39:23 -0700
Subject: [Slackbuilds-users] Error compiling webkitgtk
In-Reply-To: <a87ee754-19bd-5f30-2d37-a51c1cbde832@slint.fr>
References: <a87ee754-19bd-5f30-2d37-a51c1cbde832@slint.fr>
Message-ID: <CALrQ46BUOT=eufaLNXYWx-haRi1x7ZV5VQAfc+N5-HB=rptnDA@mail.gmail.com>

i don't see the attache file.

On Fri, Mar 9, 2018 at 2:36 AM, Didier Spaier <didier at slint.fr> wrote:

> Hello,
>
> I apologize if this is the wrong place to ask.
>
> I ma trying to compile webkit2gtk 2.8.26 statically and stripped down,
> just to afterwards bundling it with yelp without this resulting in a too
> huge package.
>
> In that aim I have written the attached build script that removes a lot of
> features that I assume yelp doesn't need.
>
> However the build fails at around 94% completion (end of log attached)
>
> I have tried with -j2 and -j1, same result.
>
> However, I previously built it successfully, but full featured and shared.
>
> A web search came empty.
>
> Any clue appreciated.
>
> Have a good day,
>
> Diider
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180309/d1f1f681/attachment-0001.html>

From didier at slint.fr  Fri Mar  9 09:40:55 2018
From: didier at slint.fr (Didier Spaier)
Date: Fri, 9 Mar 2018 10:40:55 +0100
Subject: [Slackbuilds-users] Error compiling webkitgtk
In-Reply-To: <a87ee754-19bd-5f30-2d37-a51c1cbde832@slint.fr>
References: <a87ee754-19bd-5f30-2d37-a51c1cbde832@slint.fr>
Message-ID: <adc9939f-f462-b986-814d-4d7bf8c13d45@slint.fr>

Sorry for the missing files, now attached as well as the configlog.

Didier

Le 09/03/2018 ? 10:36, Didier Spaier a ?crit?:
> Hello,
> 
> I apologize if this is the wrong place to ask.
> 
> I ma trying to compile webkit2gtk 2.8.26 statically and stripped down, just to afterwards bundling it with yelp without this resulting in a too huge package.
> 
> In that aim I have written the attached build script that removes a lot of features that I assume yelp doesn't need.
> 
> However the build fails at around 94% completion (end of log attached)
> 
> I have tried with -j2 and -j1, same result.
> 
> However, I previously built it successfully, but full featured and shared.
> 
> A web search came empty.
> 
> Any clue appreciated.
> 
> Have a good day,
> 
> Diider
> 
> 
-------------- next part --------------
         doMouseEvent(GDK_BUTTON_RELEASE, page.viewWidget(), viewPosition, gdkButton, state);
                      ^
/home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebKit/UIProcess/Automation/gtk/WebAutomationSessionGtk.cpp: At 
global scope:
/home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebKit/UIProcess/Automation/gtk/WebAutomationSessionGtk.cpp:132:30: 
erreur?: variable or field ?doKeyStrokeEvent? declared void
 static void doKeyStrokeEvent(GdkEventType type, GtkWidget* widget, unsigned keyVal, unsigned state, bool doReleaseAfterPress = false)
                              ^
/home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebKit/UIProcess/Automation/gtk/WebAutomationSessionGtk.cpp:132:30: 
erreur?: ?GdkEventType? was not declared in this scope
/home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebKit/UIProcess/Automation/gtk/WebAutomationSessionGtk.cpp:132:58: 
erreur?: expected primary-expression before ?*? token
 static void doKeyStrokeEvent(GdkEventType type, GtkWidget* widget, unsigned keyVal, unsigned state, bool doReleaseAfterPress = false)
                                                          ^
/home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebKit/UIProcess/Automation/gtk/WebAutomationSessionGtk.cpp:132:60: 
erreur?: ?widget? was not declared in this scope
 static void doKeyStrokeEvent(GdkEventType type, GtkWidget* widget, unsigned keyVal, unsigned state, bool doReleaseAfterPress = false)
                                                            ^
/home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebKit/UIProcess/Automation/gtk/WebAutomationSessionGtk.cpp:132:68: 
erreur?: expected primary-expression before ?unsigned?
 static void doKeyStrokeEvent(GdkEventType type, GtkWidget* widget, unsigned keyVal, unsigned state, bool doReleaseAfterPress = false)
                                                                    ^
/home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebKit/UIProcess/Automation/gtk/WebAutomationSessionGtk.cpp:132:85: 
erreur?: expected primary-expression before ?unsigned?
 static void doKeyStrokeEvent(GdkEventType type, GtkWidget* widget, unsigned keyVal, unsigned state, bool doReleaseAfterPress = false)
                                                                                     ^
/home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebKit/UIProcess/Automation/gtk/WebAutomationSessionGtk.cpp:132:101: 
erreur?: expected primary-expression before ?bool?
 static void doKeyStrokeEvent(GdkEventType type, GtkWidget* widget, unsigned keyVal, unsigned state, bool doReleaseAfterPress = false)
                                                                                                     ^
/home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebKit/UIProcess/Automation/gtk/WebAutomationSessionGtk.cpp:312:1: 
erreur?: expected ?}? at end of input
 } // namespace WebKit
 ^
Source/WebKit/CMakeFiles/WebKit2.dir/build.make:15487?: la recette pour la cible 
??Source/WebKit/CMakeFiles/WebKit2.dir/UIProcess/Automation/gtk/WebAutomationSessionGtk.cpp.o?? a ?chou?e
make[2]: *** [Source/WebKit/CMakeFiles/WebKit2.dir/UIProcess/Automation/gtk/WebAutomationSessionGtk.cpp.o] Erreur 1
CMakeFiles/Makefile2:1263?: la recette pour la cible ??Source/WebKit/CMakeFiles/WebKit2.dir/all?? a ?chou?e
make[1]: *** [Source/WebKit/CMakeFiles/WebKit2.dir/all] Erreur 2

-------------- next part --------------
#!/bin/sh
CWD=$(pwd)
pkgname=webkitgtk
pkgver=2.18.6
rm -rf ${pkgname}-$pkgver
if [ -e $CWD/libs ]; then
	echo "$CWD/libs already exist. Exiting"
	exit
fi
mkdir $CWD/libs
tar xf ${pkgname}-${pkgver}.tar.xz
cd ${pkgname}-$pkgver
chown -R root:root .
find -L . \
 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
  -o -perm 511 \) -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
rm -rf build
mkdir build
cd build
SLKCFLAGS="-O2 -fPIC"
LIBDIRSUFFIX="64"
cmake ..	-DPORT=GTK \
		-DCMAKE_BUILD_TYPE=Release \
		-DCMAKE_SKIP_RPATH=ON \
		-DENABLE_DRAG_SUPPORT=OFF \
		-DENABLE_GEOLOCATION=OFF \
		-DENABLE_ICONDATABASE=OFF \
		-DENABLE_INTROSPECTION=OFF \
		-DENABLE_PLUGIN_PROCESS_GTK2=OFF \
		-DENABLE_JIT=OFF \
		-DENABLE_OPENGL=OFF \
		-DENABLE_SAMPLING_PROFILER=OFF \
		-DENABLE_SPELLCHECK=OFF \
		-DENABLE_TOUCH_EVENTS=OFF \
		-DENABLE_VIDEO=OFF \
		-DENABLE_WEBDRIVER=OFF \
		-DENABLE_WEB_AUDIO=OFF \
		-DENABLE_WEB_CRYPTO=OFF \
		-DBUILD_SHARED_LIBS=OFF \
		-DCMAKE_INSTALL_PREFIX=/usr \
		-DLIB_INSTALL_DIR=/usr/lib${LIBDIRSUFFIX} \
		-DLIBEXEC_INSTALL_DIR=/usr/lib${LIBDIRSUFFIX}/webkit2gtk-4.0 \
		-DUSE_LIBHYPHEN=OFF \
		-DUSE_LIBNOTIFY=OFF \
		-DUSE_LIBSECRET=OFF \
		-DENABLE_GTKDOC=OFF \
		2>&1| tee ../../NEWLOG
make -j 1 || return 1
make install DESTDIR=$CWD/libs
-------------- next part --------------
-- The C compiler identification is GNU 5.5.0
-- The CXX compiler identification is GNU 5.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- The CMake build type is: Release
-- Found Gperf: /usr/bin/gperf (Required is at least version "3.0.1") 
-- Found Perl: /usr/bin/perl (found suitable version "5.22.2", minimum required is "5.10.0") 
-- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.14", minimum required is "2.7.0") 
-- Found Ruby: /usr/bin/ruby (found suitable version "2.2.0", minimum required is "1.9") 
-- Performing Test C_COMPILER_SUPPORTS_-fno-strict-aliasing
-- Performing Test C_COMPILER_SUPPORTS_-fno-strict-aliasing - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-fno-strict-aliasing
-- Performing Test CXX_COMPILER_SUPPORTS_-fno-strict-aliasing - Success
-- Performing Test C_COMPILER_SUPPORTS_-fno-exceptions
-- Performing Test C_COMPILER_SUPPORTS_-fno-exceptions - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-fno-exceptions
-- Performing Test CXX_COMPILER_SUPPORTS_-fno-exceptions - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-std=c++14
-- Performing Test CXX_COMPILER_SUPPORTS_-std=c++14 - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-fno-rtti
-- Performing Test CXX_COMPILER_SUPPORTS_-fno-rtti - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wall
-- Performing Test C_COMPILER_SUPPORTS_-Wall - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wextra
-- Performing Test C_COMPILER_SUPPORTS_-Wextra - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wcast-align
-- Performing Test C_COMPILER_SUPPORTS_-Wcast-align - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wformat-security
-- Performing Test C_COMPILER_SUPPORTS_-Wformat-security - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wmissing-format-attribute
-- Performing Test C_COMPILER_SUPPORTS_-Wmissing-format-attribute - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wpointer-arith
-- Performing Test C_COMPILER_SUPPORTS_-Wpointer-arith - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wundef
-- Performing Test C_COMPILER_SUPPORTS_-Wundef - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wwrite-strings
-- Performing Test C_COMPILER_SUPPORTS_-Wwrite-strings - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wall
-- Performing Test CXX_COMPILER_SUPPORTS_-Wall - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wextra
-- Performing Test CXX_COMPILER_SUPPORTS_-Wextra - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wcast-align
-- Performing Test CXX_COMPILER_SUPPORTS_-Wcast-align - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wformat-security
-- Performing Test CXX_COMPILER_SUPPORTS_-Wformat-security - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wmissing-format-attribute
-- Performing Test CXX_COMPILER_SUPPORTS_-Wmissing-format-attribute - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wpointer-arith
-- Performing Test CXX_COMPILER_SUPPORTS_-Wpointer-arith - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wundef
-- Performing Test CXX_COMPILER_SUPPORTS_-Wundef - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wwrite-strings
-- Performing Test CXX_COMPILER_SUPPORTS_-Wwrite-strings - Success
-- Performing Test C_COMPILER_SUPPORTS_-Qunused-arguments
-- Performing Test C_COMPILER_SUPPORTS_-Qunused-arguments - Failed
-- Performing Test C_COMPILER_SUPPORTS_-Wno-expansion-to-defined
-- Performing Test C_COMPILER_SUPPORTS_-Wno-expansion-to-defined - Failed
-- Performing Test C_COMPILER_SUPPORTS_-Wno-maybe-uninitialized
-- Performing Test C_COMPILER_SUPPORTS_-Wno-maybe-uninitialized - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wno-noexcept-type
-- Performing Test C_COMPILER_SUPPORTS_-Wno-noexcept-type - Failed
-- Performing Test C_COMPILER_SUPPORTS_-Wno-parentheses-equality
-- Performing Test C_COMPILER_SUPPORTS_-Wno-parentheses-equality - Failed
-- Performing Test CXX_COMPILER_SUPPORTS_-Qunused-arguments
-- Performing Test CXX_COMPILER_SUPPORTS_-Qunused-arguments - Failed
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-expansion-to-defined
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-expansion-to-defined - Failed
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-maybe-uninitialized
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-maybe-uninitialized - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-noexcept-type
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-noexcept-type - Failed
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-parentheses-equality
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-parentheses-equality - Failed
-- Looking for features.h
-- Looking for features.h - found
-- Looking for errno.h
-- Looking for errno.h - found
-- Looking for langinfo.h
-- Looking for langinfo.h - found
-- Looking for sys/mman.h
-- Looking for sys/mman.h - found
-- Looking for pthread_np.h
-- Looking for pthread_np.h - not found
-- Looking for strings.h
-- Looking for strings.h - found
-- Looking for sys/param.h
-- Looking for sys/param.h - found
-- Looking for sys/time.h
-- Looking for sys/time.h - found
-- Looking for sys/timeb.h
-- Looking for sys/timeb.h - found
-- Looking for _aligned_malloc
-- Looking for _aligned_malloc - not found
-- Looking for IsDebuggerPresent
-- Looking for IsDebuggerPresent - not found
-- Looking for localtime_r
-- Looking for localtime_r - found
-- Looking for strnstr
-- Looking for strnstr - not found
-- Looking for timegm
-- Looking for timegm - found
-- Looking for vasprintf
-- Looking for vasprintf - found
-- Looking for regexec
-- Looking for regexec - found
-- Looking for SIGTRAP
-- Looking for SIGTRAP - found
-- Performing Test HAVE_STAT_BIRTHTIME_value
-- Performing Test HAVE_STAT_BIRTHTIME_value - Failed
-- Performing Test HAVE_TM_GMTOFF_value
-- Performing Test HAVE_TM_GMTOFF_value - Success
-- Performing Test HAVE_TM_ZONE_value
-- Performing Test HAVE_TM_ZONE_value - Success
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of __int128_t
-- Check size of __int128_t - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2") 
-- Found Cairo: /usr/include/cairo (found suitable version "1.14.6", minimum required is "1.10.2") 
-- Checking for module 'fontconfig'
--   Found fontconfig, version 2.11.1
-- Found Fontconfig: /usr/lib64/libfontconfig.so (Required is at least version "2.8.0") 
-- Checking for module 'freetype2'
--   Found freetype2, version 18.3.12
-- Found Freetype2: /usr/include/freetype2/freetype;/usr/include/freetype2 (Required is at least version "2.4.2") 
-- Found LibGcrypt: /usr/lib64/libgcrypt.so (found suitable version "1.7.9", minimum required is "1.6.0") 
-- Checking for module 'gtk+-3.0'
--   Found gtk+-3.0, version 3.18.9
-- Checking for module 'gtk+-quartz-3.0'
--   No package 'gtk+-quartz-3.0' found
-- Checking for module 'gtk+-x11-3.0'
--   Found gtk+-x11-3.0, version 3.18.9
-- Checking for module 'gtk+-wayland-3.0'
--   No package 'gtk+-wayland-3.0' found
-- Found GTK3: /usr/include/gtk-3.0;/usr/include/at-spi2-atk/2.0;/usr/include/at-spi-2.0;/usr/include/dbus-1.0;/usr/lib64/dbus-1.0/include;/usr/include/gtk-3.0;/usr/include/gio-unix-2.0/;/usr/include/cairo;/usr/include/pango-1.0;/usr/include/atk-1.0;/usr/include/cairo;/usr/include/pixman-1;/usr/include/freetype2;/usr/include/libpng16;/usr/include/harfbuzz;/usr/include/glib-2.0;/usr/lib64/glib-2.0/include;/usr/include/freetype2;/usr/include/harfbuzz;/usr/include/libdrm;/usr/include/libpng16;/usr/include/gdk-pixbuf-2.0;/usr/include/libpng16;/usr/include/glib-2.0;/usr/lib64/glib-2.0/include (Required is at least version "3.6.0") 
-- Checking for module 'gdk-3.0'
--   Found gdk-3.0, version 3.18.9
-- Found GDK3: /usr/include/gtk-3.0;/usr/include/gio-unix-2.0/;/usr/include/cairo;/usr/include/pango-1.0;/usr/include/gdk-pixbuf-2.0;/usr/include/libpng16;/usr/include/cairo;/usr/include/pixman-1;/usr/include/freetype2;/usr/include/libpng16;/usr/include/harfbuzz;/usr/include/glib-2.0;/usr/lib64/glib-2.0/include;/usr/include/freetype2;/usr/include/harfbuzz;/usr/include/libdrm;/usr/include/libpng16;/usr/include/glib-2.0;/usr/lib64/glib-2.0/include (Required is at least version "3.6.0") 
-- Checking for module 'harfbuzz>=0.9.7'
--   Found harfbuzz, version 1.2.7
-- Checking for module 'harfbuzz-icu>=0.9.18'
--   Found harfbuzz-icu, version 1.2.7
-- Found HarfBuzz: /usr/include/harfbuzz (Required is at least version "0.9.2") 
-- Checking for module 'icu-uc'
--   Found icu-uc, version 56.1
-- Checking for module 'icu-i18n'
--   Found icu-i18n, version 56.1
-- Found ICU header files in /usr/include
-- Found ICU libraries: /usr/lib64/libicuuc.so
-- Found ICU internationaliation libraries: /usr/lib64/libicui18n.so
-- Found ICU data libraries: /usr/lib64/libicudata.so
-- Found JPEG: /usr/lib64/libjpeg.so  
-- Found LibSoup: /usr/include/libsoup-2.4 (found suitable version "2.52.2", minimum required is "2.42.0") 
-- Found LibXml2: /usr/lib64/libxml2.so (found suitable version "2.9.5", minimum required is "2.8.0") 
-- Found ZLIB: /usr/lib64/libz.so (found version "1.2.8") 
-- Found PNG: /usr/lib64/libpng.so (found version "1.6.27") 
-- Checking for module 'sqlite3'
--   Found sqlite3, version 3.13.0
-- Found Sqlite: /usr/include  
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
-- Checking for module 'atk'
--   Found atk, version 2.27.1
-- Found ATK: /usr/include/atk-1.0 (found version "2.27.1") 
-- Found WebP: /usr/include  
-- Checking for module 'atspi-2'
--   Found atspi-2, version 2.26.2
-- Found ATSPI: /usr/include/at-spi-2.0;/usr/include/dbus-1.0;/usr/lib64/dbus-1.0/include;/usr/include/glib-2.0;/usr/lib64/glib-2.0/include (Required is at least version "2.5.3") 
-- Checking for module 'egl'
--   Found egl, version 11.2.2
-- Found EGL: /usr/include  
-- Checking for module 'gtk+-unix-print-3.0'
--   Found gtk+-unix-print-3.0, version 3.18.9
-- Found GTKUnixPrint: /usr/include/gtk-3.0/unix-print;/usr/include/gtk-3.0;/usr/include/at-spi2-atk/2.0;/usr/include/at-spi-2.0;/usr/include/dbus-1.0;/usr/lib64/dbus-1.0/include;/usr/include/gtk-3.0;/usr/include/gio-unix-2.0/;/usr/include/cairo;/usr/include/pango-1.0;/usr/include/atk-1.0;/usr/include/cairo;/usr/include/pixman-1;/usr/include/freetype2;/usr/include/libpng16;/usr/include/harfbuzz;/usr/include/glib-2.0;/usr/lib64/glib-2.0/include;/usr/include/freetype2;/usr/include/harfbuzz;/usr/include/libdrm;/usr/include/libpng16;/usr/include/gdk-pixbuf-2.0;/usr/include/libpng16;/usr/include/glib-2.0;/usr/lib64/glib-2.0/include  
-- Checking for module 'gl'
--   Found gl, version 11.2.2
-- Found OpenGL: /usr/include  
-- Looking for include file GL/glx.h
-- Looking for include file GL/glx.h - found
-- Checking for module 'glesv2'
--   Found glesv2, version 11.2.2
-- Found OpenGLES2: /usr/include  
-- Disabling ENABLE_3D_TRANSFORMS since ENABLE_OPENGL is disabled.
-- Disabling ENABLE_DFG_JIT since ENABLE_JIT is disabled.
-- Disabling ENABLE_FTL_JIT since ENABLE_DFG_JIT is disabled.
-- Disabling ENABLE_MEDIA_CONTROLS_SCRIPT since ENABLE_VIDEO is disabled.
-- Disabling ENABLE_SUBTLE_CRYPTO since ENABLE_WEB_CRYPTO is disabled.
-- Disabling ENABLE_VIDEO_TRACK since ENABLE_VIDEO is disabled.
-- Disabling ENABLE_WEBASSEMBLY since ENABLE_FTL_JIT is disabled.
-- Disabling ENABLE_WEBGL since ENABLE_OPENGL is disabled.
-- Disabling USE_GSTREAMER_GL since ENABLE_OPENGL is disabled.
-- Disabling USE_REDIRECTED_XCOMPOSITE_WINDOW since ENABLE_OPENGL is disabled.
-- Found GLIB: /usr/include/glib-2.0;/usr/lib64/glib-2.0/include (found suitable version "2.46.2", minimum required is "2.36") 
-- Found LibXslt: /usr/lib64/libxslt.so (found suitable version "1.1.29", minimum required is "1.1.7") 
-- Looking for XOpenDisplay in /usr/lib64/libX11.so;/usr/lib64/libXext.so
-- Looking for XOpenDisplay in /usr/lib64/libX11.so;/usr/lib64/libXext.so - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found X11: /usr/lib64/libX11.so
-- Using platform-specific CMakeLists: /home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WTF/wtf/PlatformGTK.cmake
-- Using platform-specific CMakeLists: /home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/JavaScriptCore/PlatformGTK.cmake
-- Using platform-specific CMakeLists: /home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/JavaScriptCore/shell/PlatformGTK.cmake
-- Performing Test C_COMPILER_SUPPORTS_-Wno-cast-align
-- Performing Test C_COMPILER_SUPPORTS_-Wno-cast-align - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wno-implicit-fallthrough
-- Performing Test C_COMPILER_SUPPORTS_-Wno-implicit-fallthrough - Failed
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-cast-align
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-cast-align - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-implicit-fallthrough
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-implicit-fallthrough - Failed
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-sign-compare
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-sign-compare - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-unused-variable
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-unused-variable - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-unused-parameter
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-unused-parameter - Success
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-unused-but-set-variable
-- Performing Test CXX_COMPILER_SUPPORTS_-Wno-unused-but-set-variable - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wno-sign-compare
-- Performing Test C_COMPILER_SUPPORTS_-Wno-sign-compare - Success
-- Performing Test C_COMPILER_SUPPORTS_-Wno-unused-parameter
-- Performing Test C_COMPILER_SUPPORTS_-Wno-unused-parameter - Success
-- Using platform-specific CMakeLists: /home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebCore/PAL/pal/PlatformGTK.cmake
-- Using platform-specific CMakeLists: /home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebCore/PlatformGTK.cmake
-- Performing Test ATOMIC_INT64_IS_BUILTIN
-- Performing Test ATOMIC_INT64_IS_BUILTIN - Success
-- Looking for shm_open
-- Looking for shm_open - not found
-- Looking for shm_open
-- Looking for shm_open - found
-- Using platform-specific CMakeLists: /home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/WebKit/PlatformGTK.cmake
-- Using platform-specific CMakeLists: /home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/Source/PlatformGTK.cmake
-- Found Gettext: /usr/bin/msgmerge (found version "0.19.8.1") 
-- Enabled features:
--  ENABLE_ACCELERATED_2D_CANVAS .......... OFF
--  ENABLE_DRAG_SUPPORT                     OFF
--  ENABLE_GEOLOCATION .................... OFF
--  ENABLE_GLES2                            OFF
--  ENABLE_GTKDOC ......................... OFF
--  ENABLE_ICONDATABASE                     OFF
--  ENABLE_INTROSPECTION .................. OFF
--  ENABLE_JIT                              OFF
--  ENABLE_MINIBROWSER .................... OFF
--  ENABLE_OPENGL                           OFF
--  ENABLE_PLUGIN_PROCESS_GTK2 ............ OFF
--  ENABLE_QUARTZ_TARGET                    OFF
--  ENABLE_SAMPLING_PROFILER .............. OFF
--  ENABLE_SPELLCHECK                       OFF
--  ENABLE_TOUCH_EVENTS ................... OFF
--  ENABLE_VIDEO                            OFF
--  ENABLE_WAYLAND_TARGET ................. OFF
--  ENABLE_WEBDRIVER                        OFF
--  ENABLE_WEB_AUDIO ...................... OFF
--  ENABLE_WEB_CRYPTO                       OFF
--  ENABLE_X11_TARGET ..................... ON
--  USE_LIBHYPHEN                           OFF
--  USE_LIBNOTIFY ......................... OFF
--  USE_LIBSECRET                           OFF
--  USE_SYSTEM_MALLOC ..................... OFF
-- Configuring done
-- Generating done
-- Build files have been written to: /home/didier/Slint/repo/x86_64/slint-14.2.1/next/source/yelp/webkitgtk-2.18.6/build

From didier at slint.fr  Fri Mar  9 09:43:22 2018
From: didier at slint.fr (Didier Spaier)
Date: Fri, 9 Mar 2018 10:43:22 +0100
Subject: [Slackbuilds-users] Error compiling webkitgtk
In-Reply-To: <CALrQ46BUOT=eufaLNXYWx-haRi1x7ZV5VQAfc+N5-HB=rptnDA@mail.gmail.com>
References: <a87ee754-19bd-5f30-2d37-a51c1cbde832@slint.fr>
 <CALrQ46BUOT=eufaLNXYWx-haRi1x7ZV5VQAfc+N5-HB=rptnDA@mail.gmail.com>
Message-ID: <7f6d0071-4744-c7e8-5d93-4578ca9615ab@slint.fr>

Now sent, thanks.

Also the webkitgtk version is of course 2.18.6, not 2.8.26.

Le 09/03/2018 ? 10:39, Fernando Lopez a ?crit?:
> i don't see the attache file.
> 
> On Fri, Mar 9, 2018 at 2:36 AM, Didier Spaier <didier at slint.fr <mailto:didier at slint.fr>> wrote:
> 
>     Hello,
> 
>     I apologize if this is the wrong place to ask.
> 
>     I ma trying to compile webkit2gtk 2.8.26 statically and stripped down, just to afterwards bundling it with yelp without this resulting in a too huge package.
> 
>     In that aim I have written the attached build script that removes a lot of features that I assume yelp doesn't need.
> 
>     However the build fails at around 94% completion (end of log attached)
> 
>     I have tried with -j2 and -j1, same result.
> 
>     However, I previously built it successfully, but full featured and shared.
> 
>     A web search came empty.
> 
>     Any clue appreciated.
> 
>     Have a good day,
> 
>     Diider
> 
> 
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org <mailto:SlackBuilds-users at slackbuilds.org>
>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>     Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>     FAQ - https://slackbuilds.org/faq/
> 
> 
> 
> 
> -- 
> 
> ------------
> Regards,
> ? ? Fernando Lopez Jr.
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From fernando.lopezjr at gmail.com  Fri Mar  9 09:44:23 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Fri, 9 Mar 2018 02:44:23 -0700
Subject: [Slackbuilds-users] Error compiling webkitgtk
In-Reply-To: <7f6d0071-4744-c7e8-5d93-4578ca9615ab@slint.fr>
References: <a87ee754-19bd-5f30-2d37-a51c1cbde832@slint.fr>
 <CALrQ46BUOT=eufaLNXYWx-haRi1x7ZV5VQAfc+N5-HB=rptnDA@mail.gmail.com>
 <7f6d0071-4744-c7e8-5d93-4578ca9615ab@slint.fr>
Message-ID: <CALrQ46AuiiR=oSR_UGSni5yTFHU7R6kvdEzy-92K4u7fi-sbvQ@mail.gmail.com>

i'll try and see if i can compile it...

On Fri, Mar 9, 2018 at 2:43 AM, Didier Spaier <didier at slint.fr> wrote:

> Now sent, thanks.
>
> Also the webkitgtk version is of course 2.18.6, not 2.8.26.
>
> Le 09/03/2018 ? 10:39, Fernando Lopez a ?crit :
> > i don't see the attache file.
> >
> > On Fri, Mar 9, 2018 at 2:36 AM, Didier Spaier <didier at slint.fr <mailto:
> didier at slint.fr>> wrote:
> >
> >     Hello,
> >
> >     I apologize if this is the wrong place to ask.
> >
> >     I ma trying to compile webkit2gtk 2.8.26 statically and stripped
> down, just to afterwards bundling it with yelp without this resulting in a
> too huge package.
> >
> >     In that aim I have written the attached build script that removes a
> lot of features that I assume yelp doesn't need.
> >
> >     However the build fails at around 94% completion (end of log
> attached)
> >
> >     I have tried with -j2 and -j1, same result.
> >
> >     However, I previously built it successfully, but full featured and
> shared.
> >
> >     A web search came empty.
> >
> >     Any clue appreciated.
> >
> >     Have a good day,
> >
> >     Diider
> >
> >
> >     _______________________________________________
> >     SlackBuilds-users mailing list
> >     SlackBuilds-users at slackbuilds.org <mailto:SlackBuilds-users@
> slackbuilds.org>
> >     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users <
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >     Archives - https://lists.slackbuilds.org/
> pipermail/slackbuilds-users/ <https://lists.slackbuilds.
> org/pipermail/slackbuilds-users/>
> >     FAQ - https://slackbuilds.org/faq/
> >
> >
> >
> >
> > --
> >
> > ------------
> > Regards,
> >     Fernando Lopez Jr.
> >
> >
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180309/0fb59f98/attachment.html>

From rundstutzen at gmx.de  Fri Mar  9 09:56:49 2018
From: rundstutzen at gmx.de (rundstutzen at gmx.de)
Date: Fri, 9 Mar 2018 10:56:49 +0100
Subject: [Slackbuilds-users] Error compiling webkitgtk
In-Reply-To: <adc9939f-f462-b986-814d-4d7bf8c13d45@slint.fr>
References: <a87ee754-19bd-5f30-2d37-a51c1cbde832@slint.fr>
 <adc9939f-f462-b986-814d-4d7bf8c13d45@slint.fr>
Message-ID: <20180309105649.7c76bf81@fiete.bug.net>

i can only speak for webkitgtk 1, but i ran into a similar
issue.

i tried to disable as much as possible and the build failed. the
reason is that in the build process a lot of files are autogenerated.
later these files are used in the compilation process. seems the
compilation stage has no clue about the config stage, so even if you
disable some features the compiler needs these autogenerated files
(for features you disabled) to succeed.

maybe you ran into a similar issue.

one of the reasons i gave up on webkit, it's a mess.

On Fri, 9 Mar 2018 10:40:55 +0100
Didier Spaier <didier at slint.fr> wrote:

> Sorry for the missing files, now attached as well as the configlog.
> 
> Didier
> 
> Le 09/03/2018 ? 10:36, Didier Spaier a ?crit?:
> > Hello,
> > 
> > I apologize if this is the wrong place to ask.
> > 
> > I ma trying to compile webkit2gtk 2.8.26 statically and stripped
> > down, just to afterwards bundling it with yelp without this
> > resulting in a too huge package.
> > 
> > In that aim I have written the attached build script that removes a
> > lot of features that I assume yelp doesn't need.
> > 
> > However the build fails at around 94% completion (end of log
> > attached)
> > 
> > I have tried with -j2 and -j1, same result.
> > 
> > However, I previously built it successfully, but full featured and
> > shared.
> > 
> > A web search came empty.
> > 
> > Any clue appreciated.
> > 
> > Have a good day,
> > 
> > Diider
> > 
> > 


From spaceman at antispaceman.com  Fri Mar  9 17:34:01 2018
From: spaceman at antispaceman.com (spaceman)
Date: Fri, 09 Mar 2018 17:34:01 +0000
Subject: [Slackbuilds-users] Error compiling webkitgtk
In-Reply-To: <20180309105649.7c76bf81@fiete.bug.net>
References: <a87ee754-19bd-5f30-2d37-a51c1cbde832@slint.fr>
 <adc9939f-f462-b986-814d-4d7bf8c13d45@slint.fr>
 <20180309105649.7c76bf81@fiete.bug.net>
Message-ID: <20180309173401.AB6C3923@home.antispaceman.com>

> I ma trying to compile webkit2gtk 2.8.26 statically and stripped
> down, just to afterwards bundling it with yelp without this
> resulting in a too huge package.

I have managed to get a reasonably minimal (linked) build of 2.18.6
going with the following config:

  cmake -DPORT=GTK \
        -DCMAKE_BUILD_TYPE=Release \
        -DCMAKE_SKIP_RPATH=ON \
        -DCMAKE_INSTALL_PREFIX=/usr \
        -DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
        -DENABLE_GEOLOCATION=false \
        -DENABLE_SPELLCHECK=false \
        -DENABLE_VIDEO=false \
        -DENABLE_WEB_AUDIO=false \
        -DENABLE_INDEXED_DATABASE=false \
        -DENABLE_PLUGIN_PROCESS_GTK2=false \
        -DENABLE_DRAG_SUPPORT=false \
        -DENABLE_NOTIFICATIONS=false \
        -DENABLE_WEBDRIVER=false \
        -DENABLE_WEB_CRYPTO=false \
        -DENABLE_ICONDATABASE=false \
        -DUSE_SYSTEM_MALLOC=true \
        -DUSE_LIBHYPHEN=false \
        -DUSE_LIBNOTIFY=false \
        -DUSE_LIBSECRET=false \
        -DUSE_LIBWEBP=false \
        -DLIB_INSTALL_DIR=/usr/lib${LIBDIRSUFFIX} \
        -DLIBEXEC_INSTALL_DIR=/usr/lib${LIBDIRSUFFIX}/webkit2gtk-4.0 \
        ..

Try putting back opengl, jit or touch events, one of them (i think touch
events suprisingly) caused my build to fail.

From didier at slint.fr  Fri Mar  9 18:24:55 2018
From: didier at slint.fr (Didier Spaier)
Date: Fri, 9 Mar 2018 19:24:55 +0100
Subject: [Slackbuilds-users] Error compiling webkitgtk
In-Reply-To: <20180309173401.AB6C3923@home.antispaceman.com>
References: <a87ee754-19bd-5f30-2d37-a51c1cbde832@slint.fr>
 <adc9939f-f462-b986-814d-4d7bf8c13d45@slint.fr>
 <20180309105649.7c76bf81@fiete.bug.net>
 <20180309173401.AB6C3923@home.antispaceman.com>
Message-ID: <7be4d655-9c1e-e775-88f9-fbe0b06c6aeb@slint.fr>

Le 09/03/2018 ? 18:34, spaceman a ?crit?:

> I have managed to get a reasonably minimal (linked) build of 2.18.6
> going with the following config:

Thanks a lot, much appreciated.

I have another build running, will try your configuration as soon as
possible and will let you know the outcome.

Best regards,

Didier

From willysr at slackbuilds.org  Sat Mar 10 00:30:48 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Mar 2018 07:30:48 +0700
Subject: [Slackbuilds-users] Updates - 20180310.1
Message-ID: <9b87e97f-a6f9-d40a-5543-c511e52b8b23@slackbuilds.org>

Hi,

here comes another batch of updates along with some highlight
- nodejs and nodejs6 have been bumped to the latest LTS release 8.10.0
and 6.13.1 and vscode 1.21.0 is now working with latest nodejs. We will
keep nodejs6 for some time, but my plan is to remove them in the next
cycle since no other scripts depends on it currently.
- letsencrypt 0.22.0 now supports wildcards certs, but i personally
haven't tried this feature yet, so no updates on the documentation for now.
- wxGTK3 is now at 3.0.4
- Matteo is mirroring more sources in his repository for backups
- stansoft is updated to 7.13 and this is personally maintained by the
company that develop it.


Sat Mar 10 00:12:40 UTC 2018
academic/avogadro: Mirror download url.
academic/papi: Fixed ownership.
academic/tkgate: Mirror download url.
academic/xflr5: Fix slack-desc, add doinst.sh.
audio/hydrogen: Updated for version 0.9.7.
audio/museeks: Updated for version 0.9.0.
audio/opencore-amr: New maintainer
audio/rplay: Mirror download url.
audio/specimen: Mirror download url.
business/stansoft: Updated for version 7.13.
desktop/ClipboardViewer: Mirror download url.
desktop/aero-mouse-theme: Added (Aero cursor theme).
desktop/afterstep: Mirror download url.
desktop/crystal: Mirror download url.
desktop/flatpak: Updated for version 0.11.3.
desktop/kde44-oxygen-molecule: Mirror download url.
desktop/numix-sx-theme: Mirror download url.
desktop/oomox: Updated for version 1.5.0.5.
desktop/pekwm: Mirror download url.
desktop/plasma-adjustable-clock: Mirror download url.
desktop/plasma-eyasdp: Mirror download url.
desktop/qt5ct: Updated for version 0.35.
desktop/quickaccess: Mirror download url.
desktop/rootactions_servicemenu: Mirror download url.
desktop/skulpture: Mirror download url.
development/beautysh: Updated for version 3.8.
development/bluefish: Mirror download url.
development/cim: Mirror download url.
development/diffoscope: Updated for version 91.
development/gnome-inform7: Mirror download url.
development/kforth: Mirror download url.
development/libxbgi: Mirror download url.
development/likepython: Mirror download url.
development/mcu8051ide: Mirror download url.
development/ne: Fix .info.
development/nedit: Mirror download url.
development/newlisp: Mirror download url.
development/nodejs6: Updated for version 6.13.1.
development/nodejs: Updated for version 8.10.0.
development/omniORBpy: Mirror download url.
development/pasdoc: Mirror download url.
development/phpDocumentor: Mirror download url.
development/psycopg2: Add Python 3 support.
development/qconf: Mirror download url.
development/regina-rexx: Mirror download url.
development/rstudio-desktop: Updated for version 1.1.423.
development/rust: Note tmp build requirements in README.
development/sassc: Updated for version 3.5.0.
development/sdcc: Mirror download url.
development/shed: Mirror download url.
development/splint: Mirror download url.
development/sqliteman: Mirror download url.
development/tiled: Updated for version 1.1.3.
development/vile: Mirror download url.
development/vscode: Updated for version 1.21.0.
development/xvile: Mirror download url.
development/yarn: Updated for version 1.5.1.
games/SameBoy-libretro: Removed (replaced by SameBoy).
games/SameBoy: Added (Gameboy and Gameboy Color emulator).
games/abe: Mirror download url.
games/cosmic_assault: Mirror download url.
games/doom_shareware_data: Mirror download url.
games/gens-gs: Mirror download url.
games/gnonograms: Mirror download url.
games/heretic_shareware_data: Mirror download url.
games/hexen_demo_data: Mirror download url.
games/javacpc: Mirror download url.
games/larn: Mirror download url.
games/lmpc: Mirror download url.
games/nethack: New maintainer.
games/openjazz: Mirror download url.
games/quake3_shareware_data: Mirror download url.
games/quake_shareware_data: Mirror download url.
games/roadfighter: Mirror download url.
games/solarus-quest-editor: Patched to add a png logo.
games/talkfilters: Mirror download url.
games/transfusion: Mirror download url.
games/typhoon_2001: Mirror download url.
games/zelda-roth-se: Patched.
games/zsdx: Patched.
games/zsxd: Patched.
gis/OWSLib: Add Python 3 support.
gis/Shapely: Add Python 3 support.
gis/josm: Mirror download url.
gis/mapnik: Updated for version 3.0.19.
gis/navit: Mirror download url.
graphics/dcraw: Mirror download url.
graphics/draftsight: Mirror download url.
graphics/dxftoqet: Mirror download url.
graphics/fbv: Mirror download url.
graphics/feh: Updated for version 2.25.1.
graphics/graphite2: Updated for version 1.3.11.
graphics/openclipart: Mirror download url.
graphics/textext: Mirror download url.
graphics/tintii: Mirror download url.
graphics/urbanlightscape: Mirror download url.
ham/7plus: Mirror download url.
ham/chirp: Mirror download url.
ham/fldigi: Mirror download url.
ham/flrig: Mirror download url.
ham/svxlink: Updated for version 17.12.2.
libraries/SDL2_image: Updated for version 2.0.3.
libraries/activemq-cpp: Mirror download url.
libraries/alglib: Mirror download url.
libraries/ccrtp: Switch to i586, remove /usr/info/dir.
libraries/cdk: Mirror download url.
libraries/libbde: Mirror download url.
libraries/libcitadel: Mirror download url.
libraries/libfvde: Mirror download url.
libraries/libfwnt: Mirror download url.
libraries/libfwsi: Mirror download url.
libraries/liblnk: Mirror download url.
libraries/libmsiecf: Mirror download url.
libraries/libolecf: Mirror download url.
libraries/liboop: Mirror download url.
libraries/libsass: Updated for version 3.5.0.
libraries/libsmdev: Mirror download url.
libraries/libsmraw: Mirror download url.
libraries/libu2f-host: Updated for version 1.1.5.
libraries/libvirt: Properly initialize $count in rc.libvirt
libraries/libvshadow: Mirror download url.
libraries/libwacom: Updated for version 0.29.
libraries/libxnvctrl: Updated for version 390.25.
libraries/mariadb_client: Mirror download url.
libraries/mujs: Mirror download url.
libraries/opencv: Updated patch for version 3.4.1
libraries/wxGTK3: Updated for version 3.0.4.
libraries/zita-resampler: Mirror download url.
misc/BISP: Mirror download url.
misc/ccze: Mirror download url.
misc/floating-IPS: Minor cleanup.
multimedia/devedeng: Updated for version 4.8.12.
multimedia/opera-developer-ffmpeg-codecs: Updated for v 66.0.3343.3.
network/PaleMoon: Updated for version 27.8.1.
network/WireGuard: Updated for version 0.0.20180304.
network/gui-ufw: Updated for version 18.04.0 + new maintainer.
network/nmh: Updated for version 1.7.1.
network/opera-developer: Updated for version 53.0.2885.0.
network/opera: Updated for version 51.0.2830.55.
network/palemoon: Updated for version 27.8.1.
network/signal-desktop: Make sure to exit.
network/tornado: Updated for version 5.0.0.
network/vnstat: Updated for version 1.18.
office/gcal: Updated for version 4.1.
office/impressive: Updated for version 0.12.0.
office/keepassxc: Updated for version 2.3.1.
office/watson: Updated for version 1.5.2.
perl/perl-Math-MPFR: Updated for version 4.01.
python/arrow: Added (python library for dates, times).
python/bleach: Updated for version 2.1.3.
python/python-fonttools: Updated for version 3.24.1.
python/python3-tornado: Updated for version 5.0.0.
python/tqdm: Compress manpage.
system/alacritty: Updated for version gitf298ebb.
system/busybox: Added (The Swiss Army Knife of Embedded Linux).
system/exa: Update README.
system/fd: Update README.
system/fio: Updated for version 3.5.
system/firetools: Updated for version 0.9.52.
system/letsencrypt: Updated for version 0.22.0.
system/lynis: Updated for version 2.6.3.
system/mlterm: Updated for version 3.8.5.
system/ripgrep: Update README.
system/salt: Updated for version 2017.7.4.
system/virt-manager: Updated for version 1.5.1.
system/vtcol: Update README.
system/xen: Updated for version 4.10.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/dd94e7b9/attachment.asc>

From fernando.lopezjr at gmail.com  Sat Mar 10 01:56:13 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Fri, 9 Mar 2018 18:56:13 -0700
Subject: [Slackbuilds-users] MEGAsync required deps?
Message-ID: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>

I was able to compile MEGAsync
<https://slackbuilds.org/repository/14.2/network/MEGAsync/> without
FreeImage <https://slackbuilds.org/repository/14.2/libraries/FreeImage/>...
is FreeImage a required dependency?

can you guys check on this?


thank you!

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180309/b4479960/attachment.html>

From fernando.lopezjr at gmail.com  Sat Mar 10 02:19:04 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Fri, 9 Mar 2018 19:19:04 -0700
Subject: [Slackbuilds-users] MEGAsync required deps?
In-Reply-To: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
References: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
Message-ID: <CALrQ46D+qXG31OEywfdUx8+9VhN0JWAeOZN6BSbg8WHDSdR41Q@mail.gmail.com>

according to the MEGAsync github repo <https://github.com/meganz/MEGAsync>:

sudo apt-get install build-essential autoconf automake m4 libtool
libtool-bin qt4-qmake make libqt4-dev libcrypto++-dev libsqlite3-dev
libc-ares-dev libcurl4-openssl-dev libssl-dev
# Optional, if you wish to build nautilus extension:
sudo apt-get install libnautilus-extension-dev


sudo dnf install libtool gcc-c++ c-ares-devel cryptopp-devel
openssl-devel qt-devel sqlite-devel zlib-devel


I don't see it listed anywhere...



On Fri, Mar 9, 2018 at 6:56 PM, Fernando Lopez <fernando.lopezjr at gmail.com>
wrote:

> I was able to compile MEGAsync
> <https://slackbuilds.org/repository/14.2/network/MEGAsync/> without
> FreeImage <https://slackbuilds.org/repository/14.2/libraries/FreeImage/>...
> is FreeImage a required dependency?
>
> can you guys check on this?
>
>
> thank you!
>
> --
>
> ------------
> Regards,
>     Fernando Lopez Jr.
>



-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180309/2c89ce89/attachment.html>

From duncan_roe at optusnet.com.au  Sat Mar 10 08:43:08 2018
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Sat, 10 Mar 2018 19:43:08 +1100
Subject: [Slackbuilds-users] Sage build still broken?
In-Reply-To: <00e0f742-ca9e-ae5f-5565-f59664e12ca3@gmail.com>
References: <CAFy1yb2=5=G_5LBWoVvJuwjebkCrJDm=q=zH4Kq7quj0JJhaSw@mail.gmail.com>
 <00e0f742-ca9e-ae5f-5565-f59664e12ca3@gmail.com>
Message-ID: <20180310084308.GB3899@dimstar.local.net>

On Sun, Feb 25, 2018 at 10:59:25AM -0800, King Beowulf wrote:
> On 02/25/2018 08:44 AM, JCA wrote:
> > I built Sage 8.0 as available to Slackware 14.2 using the relevant
> > sbopkg queue.  The build process closes as follows:
> >
> > RROR:  The Sage installation tree has moved
> >
> > from /tmp/SBo/sage-8.0
> >   to /opt/sage
> >
> ---snip----
> >
> >    This in a freshly installed 14.2 system, with 24G RAM and 1TB disk
> > space. The compilation was completed normally, ending up with 13GB worth
> > of files in /tmp/SBo, and more than 5GB in /opt/sage.
> >
> >    What have I done wrong? If nothing, is there any point in keeping
> > Sage in Slackbuilds? Even in a beefy system, compiling Sage takes a
> > several hours - and ending up with lots of GBs eaten up in your hard
> > drive and a nonfunctional application is frustrating.
> >
>
> I feel your pain, and I do not have a workable solution yet.  Sage
> upstream is completely hostile to relocatable packages it seems...  The
> core problem is in how the sage devs have designed their build system.
>
> There are 2 options to get sage working:
> 1. Download their compiled binary and run their script which will patch
> the hard coded paths.
> 2. Compile the sage source in a specific path and leave it there.  You
> will note that after running sage.Slackbuild it works just fine when
> invoked from /tmp/SBo/sage-8.0
> 3. Compile the sage source in a specific path (/opt/sage) and package it
> from there.
> 4. Compile the sage source in /tmp/sage-x but have a script to patch the
> paths to make the package relocatable.  This is what the devs do for
> their binary.
>
> I could just do (1) and forgo compiling.  SBo does that for some, but
> that is not optimal. (2) is non-starter: we just can't leave stuff
> littering /tmp!  Perhaps (3) in a chroot, etc, but I think (4) is
> cleaner if I can ever figure out how the script works in (1).  I'm
> missing a path or variable somewhere.
>
> tl;dr
>
> I'm working on it.
>
> -Ed
>
Hey Ed,

SBo has mkchroot which was put together to solve this kind of problem,

Cheers ... Duncan.

From willysr at slackbuilds.org  Sat Mar 10 10:32:00 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Mar 2018 17:32:00 +0700
Subject: [Slackbuilds-users] MEGAsync required deps?
In-Reply-To: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
References: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
Message-ID: <3992e34e-6f11-1e7b-86c4-f186fe959936@slackbuilds.org>

> I was able to compile MEGAsync
> <https://slackbuilds.org/repository/14.2/network/MEGAsync/> without
> FreeImage
> <https://slackbuilds.org/repository/14.2/libraries/FreeImage/>... is
> FreeImage a required dependency?
> 
> can you guys check on this?

I think because the maintainer enable this option
--with-freeimage


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/1adbbbbc/attachment.asc>

From dn2010 at gmail.com  Sat Mar 10 11:13:52 2018
From: dn2010 at gmail.com (Daniil Bratashov)
Date: Sat, 10 Mar 2018 15:13:52 +0400
Subject: [Slackbuilds-users] Updates - 20180305.1
In-Reply-To: <d49e204e-c888-98b8-b12e-9c8f4a594754@slackbuilds.org>
References: <d49e204e-c888-98b8-b12e-9c8f4a594754@slackbuilds.org>
Message-ID: <CAJ6MA1F4tQrsSBu81FBbz0tSd6eGAs3S4nbKpLcR-VNBxyYjAA@mail.gmail.com>

cfitsio is reporting wrong md5sum now.

WBR, Daniil Bratashov.

On Mon, Mar 5, 2018 at 11:30 PM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> Hi,
>
> Following last week's update, here's another big batch which mirrors
> some of the sources into Ponce's personal repository to provide more
> alternative for hosting the sources. It's almost 300 commits so it has
> to be pushed forward before it gets bigger.
>
> We also have some updates such as hhvm, opencv, tor, clamav, and
> teamviewer. As for teamviewer, it seems that upstream have finally fixed
> the panel issue in GNOME-based DE.
>
> PS: there's a typo in one of the update (ne). It's missing a closing "'"
> in the DOWNLOAD line. It has been fixed in the tarball, but for those
> who are using third party tools you will see some warning/errors on that
> part. Sorry for that.
>
> Mon Mar  5 19:05:12 UTC 2018
> academic/artha: Mirror download url.
> academic/avogadro: Update download url.
> academic/galculator: Fix download url.
> academic/paml: Mirror download url.
> academic/qtoctave: Mirror download url.
> academic/tkgate: Update download url.
> accessibility/svkbd: Mirror download url.
> audio/clyrics: Updated for version 0.10.
> audio/fmit: Mirror download url.
> audio/mhwaveedit: Mirror download url.
> audio/nero-aac: Mirror download url.
> audio/ngjackspa: Mirror download url.
> audio/playmp3list: Fix download + switch to i586.
> audio/rplay: Update download url.
> audio/sfarkxtc: Mirror download url.
> audio/snd: Mirror download url.
> audio/specimen: Update download url.
> desktop/ClipboardViewer: Update download url.
> desktop/XDecorations: Mirror download url.
> desktop/Xfce-Theme-Manager: Mirror download url.
> desktop/afterstep: Update download url.
> desktop/cryptkeeper: Removed (Abandoned upstream).
> desktop/crystal: Update download url.
> desktop/dunst: Fix source url.
> desktop/faenza-icon-theme: Mirror download url.
> desktop/gntp-send: Update download url.
> desktop/gtk-nodoka-engine: Mirror download url.
> desktop/kde44-oxygen-molecule: Update download url.
> desktop/numix-icon-theme: Updated for version 20171225.
> desktop/numix-sx-theme: Update download url.
> desktop/oranchelo-icon-theme: Updated for version 0.7.6.
> desktop/pekwm: Update download url.
> desktop/plasma-adjustable-clock: Update download url.
> desktop/plasma-eyasdp: Update download url.
> desktop/qtile: Updated for version 0.11.1.
> desktop/quickaccess: Update download url.
> desktop/rootactions_servicemenu: Update download url.
> desktop/skulpture: Update download url.
> desktop/sun: Updated for version 1.2.2.
> desktop/xtrascreenhacks: Mirror download url.
> development/Arduino: Mirror download url.
> development/bas: Updated for version 2.4.
> development/bluefish: Update download url.
> development/chibi-scheme: Updated for version 0.8.
> development/cim: Update download url.
> development/cudnn: Update download url.
> development/d-tools: Updated for version 2.079.0
> development/dbeaver: Mirror download url.
> development/dmd: Updated for version 2.079.0
> development/ebe: Mirror download url.
> development/gecode: Mirror download url.
> development/git-lfs: Updated for version 2.4.0.
> development/global: Updated for version 6.6.2.
> development/gnome-inform7: Update download url.
> development/gprolog: New maintainer.
> development/gsoap: Mirror download url.
> development/hhvm: Updated for version 3.24.3
> development/kforth: Update download url.
> development/kotlin: Updated for version 1.2.30.
> development/libxbgi: Update download url.
> development/likepython: Update download url.
> development/lmdb: Mirror download url.
> development/mcu8051ide: Update download url.
> development/monkey-studio: Mirror download url.
> development/ne: Update download url.
> development/nedit: Update download url.
> development/newlisp: Update download url.
> development/omake: Mirror download url.
> development/omniORBpy: Update download url.
> development/openjdk6: Mirror download url.
> development/pasdoc: Update download url.
> development/phpDocumentor: Update download url.
> development/qconf: Update download url.
> development/regina-rexx: Update download url.
> development/sbcl: Updated for version 1.4.5.
> development/sdcc: Update download url.
> development/shed: Update download url.
> development/smartgit: Mirror download url.
> development/smartsvn: Update download url.
> development/splint: Update download url.
> development/sqliteman: Update download url.
> development/stgit: Mirror download url.
> development/vile: Update download url.
> development/xemacs: Mirror download url.
> development/xvile: Update download url.
> development/zope.testing: Switch to https.
> games/abe: Update download url.
> games/bloodcm: Mirror download url.
> games/cosmic_assault: Update download url.
> games/doom_shareware_data: Update download url.
> games/galaxyv2: Mirror download url.
> games/gens-gs: Update download url.
> games/gnonograms: Update download url.
> games/heretic_shareware_data: Update download url.
> games/hexen_demo_data: Update download url.
> games/jackhammer: Mirror download url.
> games/javacpc: Update download url.
> games/larn: Update download url.
> games/lmpc: Update download url.
> games/mrboom: Updated for version 4.4.
> games/openjazz: Update download url.
> games/quake3_shareware_data: Update download url.
> games/quake_shareware_data: Update download url.
> games/roadfighter: Update download url.
> games/talkfilters: Update download url.
> games/transfusion: Update download url.
> games/typhoon_2001: Update download url.
> games/warmux: Mirror download url.
> games/warsow: Mirror download url.
> gis/josm: Update download url.
> gis/navit: Update download url.
> gis/osgEarth: Mirror download url.
> gis/proj: Updated for version 5.0.0.
> gis/qgis: Updated for version 2.18.17.
> graphics/dcraw: Update download url.
> graphics/draftsight: Update download url.
> graphics/dxftoqet: Update download url.
> graphics/fbpic: Mirror download url.
> graphics/fbv: Update download url.
> graphics/feh: Updated for version 2.25.
> graphics/fotoxx: Mirror download url.
> graphics/openclipart: Update download url.
> graphics/raw-thumbnailer: Mirror download url.
> graphics/textext: Update download url.
> graphics/tintii: Update download url.
> graphics/urbanlightscape: Update download url.
> graphics/yed: Mirror download url.
> ham/7plus: Update download url.
> ham/chirp: Update download url.
> ham/cwstation: Mirror download url.
> ham/demorse: Mirror download url.
> ham/direwolf: Mirror download url.
> ham/fldigi: Update download url.
> ham/flrig: Update download url.
> ham/xdemorse: Mirror download url.
> ham/xwxapt: Mirror download url.
> libraries/FormEncode: Update download url.
> libraries/Geraldo: Update download url.
> libraries/activemq-cpp: Update download url.
> libraries/alglib: Update download url.
> libraries/cdk: Update download url.
> libraries/cfitsio: Updated for version 3.43.
> libraries/gtk-aurora-engine: Fixed DOWNLOAD.
> libraries/imlib2: Updated for version 1.5.0.
> libraries/libAfterImage: Mirror download url.
> libraries/libbde: Update download url.
> libraries/libcitadel: Update download url.
> libraries/libeot: Minor cleanup.
> libraries/libfvde: Update download url.
> libraries/libfwnt: Update download url.
> libraries/libfwsi: Update download url.
> libraries/liblnk: Update download url.
> libraries/libmsiecf: Update download url.
> libraries/libmspub: Updated for version 0.1.4.
> libraries/libolecf: Update download url.
> libraries/liboop: Update download url.
> libraries/liborcus: Updated for version 0.13.4.
> libraries/libpaper: Update download url.
> libraries/libsmdev: Update download url.
> libraries/libsmraw: Update download url.
> libraries/libtorrent-rasterbar: Update for qbittorrent-qt5.
> libraries/libvshadow: Update download url.
> libraries/mariadb_client: Update download url.
> libraries/mujs: Update download url.
> libraries/opencv: Updated for version 3.4.1
> libraries/p4api: Update download url.
> libraries/progressbar: Switch to https.
> libraries/xmltooling: Update download url.
> libraries/xview: Mirror download url.
> libraries/zita-resampler: Update download url.
> misc/BISP: Update download url.
> misc/ardesia: Mirror download url.
> misc/bdf2psf: Mirror download url.
> misc/ccze: Update download url.
> misc/floating-IPS: Mirror download url.
> misc/nfoview: Mirror download url.
> misc/tegaki-zinnia-japanese: Mirror download url.
> multimedia/QMPlay2: Updated for version 18.03.02.
> multimedia/a2jmidid: Mirror download url.
> multimedia/flvtool2: Mirror download url.
> multimedia/gmidimonitor: Mirror download url.
> multimedia/huludesktop: Mirror download url.
> multimedia/makemkv: Mirror download url.
> multimedia/opera-developer-ffmpeg-codecs: Updated for v65.0.3325.53.
> multimedia/qsampler: Mirror download url.
> multimedia/ripit: Mirror download url.
> multimedia/subtitleeditor: Mirror download url.
> network/Electrum-DASH: Mirror download url.
> network/PaleMoon: Updated for version 27.8.0.
> network/arpwatch: Mirror download url.
> network/bird: Mirror download url.
> network/boxcryptor: Mirror download url.
> network/btsync: Removed (maintainer's request).
> network/cadaver: Mirror download url.
> network/cicb: Mirror download url.
> network/clive: Mirror download url.
> network/dnstracer: Mirror download url.
> network/dropbox: Mirror download url.
> network/easyrsa: Updated for version 3.0.4.
> network/emacs-w3m: Mirror download url.
> network/firehol: Mirror download url.
> network/fping6: Mirror download url.
> network/freeradius-server: Mirror download url.
> network/googler: Updated for version 3.5.
> network/hostsblock: Mirror download url.
> network/httping: Mirror download url.
> network/icecat: Updated for version 52.6.0.
> network/kasp_updater: Mirror download url.
> network/kcm_ufw: Mirror download url.
> network/leafnode: Mirror download url.
> network/mod_chroot: Mirror download url.
> network/netperf: Mirror download url.
> network/opensmtpd: Fix permissions.
> network/opera-developer: Updated for version 53.0.2880.0.
> network/pidgin-birthday-reminder: Mirror download url.
> network/pidgin-visnotes: Mirror download url.
> network/qbittorrent-qt5: Updated for version 4.0.4.
> network/seahub: Mirror download url.
> network/shadowsocks-libev: Added (secure socks5 proxy).
> network/teamviewer: Updated for version 13.0.9865.
> network/tor: Updated for version 0.3.2.10.
> network/varnish: Mirror download url.
> network/vcspull: Mirror download url.
> network/yandex-browser-beta: Updated for version 18.1.1.952.
> office/JabRef: Mirror download url.
> office/hevea: Mirror download url.
> office/kate-latex-plugin: Mirror download url.
> office/keepassxc: .info fixes.
> office/keepnote: Mirror download url.
> office/sc-im: Updated for version 0.7.0.
> office/teapot: Mirror download url.
> office/trelby: Mirror download url.
> office/verbiste: Mirror download url.
> office/xmind: Mirror download url.
> perl/libpurple-kwallet-plugin: Mirror download url.
> perl/perl-DBD-Pg: Mirror download url.
> perl/perl-Date-Manip: Updated for version 6.70.
> perl/perl-DateTime-Format-Strptime: Mirror download url.
> perl/perl-IO-Socket-INET6: Mirror download url.
> perl/perl-Log-Dispatch: Mirror download url.
> perl/perl-Test-Harness: Updated for version 3.41.
> python/dfdatetime: Mirror download url.
> python/dfwinreg: Mirror download url.
> python/dhcpy6d: Mirror download url.
> python/p4python: Mirror download url.
> python/pychart: Mirror download url.
> python/python-neovim: Updated for version 0.2.1.
> python/python-notify2: Updated for version 0.3.1.
> python/python-suds: Mirror download url.
> python/python-yenc: Mirror download url.
> python/python3-augeas: Mirror download url.
> ruby/rubygem-mail: Updated for version 2.7.0.
> system/Iosevka: Updated for version 1.14.1.
> system/clamav: Updated for version 0.99.4.
> system/ddrescue-gui: Updated for version 1.7.2.
> system/eaglemode: Mirror download url.
> system/efitools: Mirror download url.
> system/emelfm2: Mirror download url.
> system/epson-inkjet-printer-escpr: Mirror download url.
> system/exomizer: Mirror download url.
> system/kafka: Mirror download url.
> system/microcode_ctl: Mirror download url.
> system/mkslack: Updated for version 5.2.
> system/nanum-coding-fonts-ttf: Mirror download url.
> system/pce: Mirror download url.
> system/pcsc-tools: Mirror download url.
> system/rfdump: Mirror download url.
> system/slackchlog: Mirror download url.
> system/slackyd: Mirror download url.
> system/smbldap-tools: Mirror download url.
> system/sysdig: Updated for version 0.20.0
> system/targetcli-fb: Mirror download url.
> system/tkdvd: Mirror download url.
> system/ttf-arphic-uming: Mirror download url.
> system/ttmkfdir: Mirror download url.
> system/virt-viewer: Mirror download url.
> +--------------------------+
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/1d045c3f/attachment-0001.html>

From willysr at slackbuilds.org  Sat Mar 10 12:05:10 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Mar 2018 19:05:10 +0700
Subject: [Slackbuilds-users] Updates - 20180305.1
In-Reply-To: <CAJ6MA1F4tQrsSBu81FBbz0tSd6eGAs3S4nbKpLcR-VNBxyYjAA@mail.gmail.com>
References: <d49e204e-c888-98b8-b12e-9c8f4a594754@slackbuilds.org>
 <CAJ6MA1F4tQrsSBu81FBbz0tSd6eGAs3S4nbKpLcR-VNBxyYjAA@mail.gmail.com>
Message-ID: <2eb73ef9-4dce-6362-2823-c97ea8431637@slackbuilds.org>

> cfitsio is reporting wrong md5sum now.

Thanks for reporting
Fixed in my branch


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/4d05cf72/attachment.asc>

From sbolokanov at abv.bg  Sat Mar 10 12:12:24 2018
From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvdGK4oCT0KHQtdCy0LDRgA==?= =?utf-8?B?0Yog0JHQvtC70L7QutCw0L3QvtCy0Yo=?=)
Date: Sat, 10 Mar 2018 14:12:24 +0200 (EET)
Subject: [Slackbuilds-users] MEGAsync required deps?
In-Reply-To: <3992e34e-6f11-1e7b-86c4-f186fe959936@slackbuilds.org>
References: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
 <3992e34e-6f11-1e7b-86c4-f186fe959936@slackbuilds.org>
Message-ID: <1414218863.1674637.1520683944617.JavaMail.apache@nm52.abv.bg>

--without-freeimage

 to build with no freeimage on the system (freeimage fails to build on -current anyway).  
  Dunno what freeimage is used for, but the client seems to run without it.
Haven't tested the client thoroughly though.
  
 -- ?. ?. ??????????



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/05838996/attachment.html>

From sbolokanov at abv.bg  Sat Mar 10 13:29:48 2018
From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvdGK4oCT0KHQtdCy0LDRgA==?= =?utf-8?B?0Yog0JHQvtC70L7QutCw0L3QvtCy0Yo=?=)
Date: Sat, 10 Mar 2018 15:29:48 +0200 (EET)
Subject: [Slackbuilds-users] What about slack-{required,suggests} files?
Message-ID: <423851233.1709577.1520688588154.JavaMail.apache@nm51.abv.bg>

 Are we allowed to add slack-required, slack-suggests and slack-conflicts files to our scripts?  
  Have been thinking about this for ages, so here it goes.
  
 -- ?. ?. ??????????
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/2bd29d17/attachment.html>

From baildon.research at googlemail.com  Sat Mar 10 15:37:56 2018
From: baildon.research at googlemail.com (David Spencer)
Date: Sat, 10 Mar 2018 15:37:56 +0000
Subject: [Slackbuilds-users] What about slack-{required, suggests} files?
In-Reply-To: <423851233.1709577.1520688588154.JavaMail.apache@nm51.abv.bg>
References: <423851233.1709577.1520688588154.JavaMail.apache@nm51.abv.bg>
Message-ID: <CAMt7G9S2k4M5c9z=Zb0SbhR0wqm+0JMM_XXPGqtWv+oeD7emiw@mail.gmail.com>

> Are we allowed to add slack-required, slack-suggests and slack-conflicts
> files to our scripts?

At the moment, no. If you can find some, it was probably a mistake, or
maybe a specially negotiated exception, but I don't think there are
any :)

*Personal opinions*

slack-required in the SBo repository is pointless, we already have
REQUIRES= in the .info file. When your preferred build tool builds the
package, it can create and package the slack-required file, and/or
create a .dep file, and/or PACKAGE REQUIRED line in a .meta file.

slack-suggests in the SBo repository duplicates the 'Optional
Requirements' in the README file.  sbotools (for example) can read
that!  When the package is built, your options become hard
requirements (with very few exceptions). So slack-suggests in a
package is almost always pointless. Your build tool can add your
*actually* *selected* optional dependencies into the final built
package's slack-required, file and/or the .dep file, and/or PACKAGE
REQUIRED line in the .meta file.

slack-conflicts is a rare case. At the moment we add some advice in
README and we add %README% to REQUIRES=. I would be personally quite
happy to kill %README% forever, by putting a new CONFLICTS= line in
the .info file, which would be more elegant than having a separate
slack-conflicts file. But see below :)

Some more personal opinions:

slack-required potentially has a too-complex syntax. Adding version
constraints is *evil*, it creates an NP-hard problem for your
installer, instead of the human maintainers doing their jobs properly.

slack-suggests does not have a sufficiently complex syntax, it can't
do what we sometimes need in the real world, for example packageA
*needs* packageB to have been built with its optional python3
dependency. (it's not just python3, there are others too)

slack-conflicts does not have a sufficiently complex syntax, it can't
do what we sometimes need in the real world, like the conflicts
between nvidia-driver and mesa+xorg-server.

A final personal opinion: our policies evolve when people ask good
questions, and this is a good question. Thank you :)

Cheers
-D.

From anddt at ukr.net  Sat Mar 10 16:50:02 2018
From: anddt at ukr.net (Andrew)
Date: Sat, 10 Mar 2018 16:50:02 +0000
Subject: [Slackbuilds-users] What about slack-{required, suggests} files?
In-Reply-To: <CAMt7G9S2k4M5c9z=Zb0SbhR0wqm+0JMM_XXPGqtWv+oeD7emiw@mail.gmail.com>
References: <423851233.1709577.1520688588154.JavaMail.apache@nm51.abv.bg>
 <CAMt7G9S2k4M5c9z=Zb0SbhR0wqm+0JMM_XXPGqtWv+oeD7emiw@mail.gmail.com>
Message-ID: <55CFE3A2-7B56-4D79-A61B-FA945A577D59@ukr.net>



On March 10, 2018 3:37:56 PM UTC, David Spencer <baildon.research at googlemail.com> wrote:
>
>*Personal opinions*
>
>slack-conflicts is a rare case. At the moment we add some advice in
>README and we add %README% to REQUIRES=. I would be personally quite
>happy to kill %README% forever, by putting a new CONFLICTS= line in
>the .info file, which would be more elegant than having a separate
>slack-conflicts file. But see below :)
>

I think we should have MAKEDEP and RUNDEP lines in info file for listing build-time and runtime dependencies there.

Also, can we add SHA256SUM to .info file for slackers with paranoia? ;-)

>A final personal opinion: our policies evolve when people ask good
>questions, and this is a good question. Thank you :)
>
>Cheers
>-D.
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/

--
          Andrew

From brent at exitstatusone.com  Sat Mar 10 17:27:05 2018
From: brent at exitstatusone.com (Brenton Earl)
Date: Sat, 10 Mar 2018 10:27:05 -0700
Subject: [Slackbuilds-users] What about slack-{required, suggests} files?
In-Reply-To: <55CFE3A2-7B56-4D79-A61B-FA945A577D59@ukr.net>
References: <423851233.1709577.1520688588154.JavaMail.apache@nm51.abv.bg>
 <CAMt7G9S2k4M5c9z=Zb0SbhR0wqm+0JMM_XXPGqtWv+oeD7emiw@mail.gmail.com>
 <55CFE3A2-7B56-4D79-A61B-FA945A577D59@ukr.net>
Message-ID: <9311feaa-f604-7639-deb5-603f24a1a800@exitstatusone.com>



On 03/10/2018 09:50 AM, Andrew wrote:
> Also, can we add SHA256SUM to .info file for slackers with paranoia? ;-)
> 
> --
>           Andrew

+1

I wouldn't call it paranoia, just peace of mind.

-- 
Brenton Earl

From erik at slackbuilds.org  Sat Mar 10 18:02:42 2018
From: erik at slackbuilds.org (Erik Hanson)
Date: Sat, 10 Mar 2018 12:02:42 -0600
Subject: [Slackbuilds-users] What about slack-{required, suggests} files?
In-Reply-To: <55CFE3A2-7B56-4D79-A61B-FA945A577D59@ukr.net>
References: <423851233.1709577.1520688588154.JavaMail.apache@nm51.abv.bg>
 <CAMt7G9S2k4M5c9z=Zb0SbhR0wqm+0JMM_XXPGqtWv+oeD7emiw@mail.gmail.com>
 <55CFE3A2-7B56-4D79-A61B-FA945A577D59@ukr.net>
Message-ID: <510a4b72-eec3-7119-7f89-a588c2c5dab6@slackbuilds.org>

On 03/10/2018 10:50 AM, Andrew wrote:

> I think we should have MAKEDEP and RUNDEP lines in info file for listing build-time and runtime dependencies there.

No need to complicate things, we're only concerned with what's required
to build a package. Anything that can be removed later should already be
noted in the README.

> Also, can we add SHA256SUM to .info file for slackers with paranoia? ;-)

The sums are not used for security, we have no control over upstream
sources anyway. It's just there so end users can verify they're using
the same source files that the script was tested against.


-- 
Erik

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/518f1aad/attachment.asc>

From yalhcru at gmail.com  Sat Mar 10 19:23:20 2018
From: yalhcru at gmail.com (B Watson)
Date: Sat, 10 Mar 2018 14:23:20 -0500
Subject: [Slackbuilds-users] What about slack-{required, suggests} files?
In-Reply-To: <CAMt7G9S2k4M5c9z=Zb0SbhR0wqm+0JMM_XXPGqtWv+oeD7emiw@mail.gmail.com>
References: <423851233.1709577.1520688588154.JavaMail.apache@nm51.abv.bg>
 <CAMt7G9S2k4M5c9z=Zb0SbhR0wqm+0JMM_XXPGqtWv+oeD7emiw@mail.gmail.com>
Message-ID: <CAN1hMuDxjwDYmebW7b7RGhJpkrP7DY81FF1ouMfA+n7apFPLNA@mail.gmail.com>

On 3/10/18, David Spencer <baildon.research at googlemail.com> wrote:

> slack-required in the SBo repository is pointless, we already have
> REQUIRES= in the .info file. When your preferred build tool builds the
> package, it can create and package the slack-required file, and/or
> create a .dep file, and/or PACKAGE REQUIRED line in a .meta file.

Also, tools that use slack-required are probably going to get confused
by the fact that our REQUIRES doesn't list core Slackware packages,
only SBo ones.

> slack-conflicts is a rare case. At the moment we add some advice in
> README and we add %README% to REQUIRES=. I would be personally quite
> happy to kill %README% forever, by putting a new CONFLICTS= line in
> the .info file, which would be more elegant than having a separate
> slack-conflicts file. But see below :)

Same deal with this, it would have to be able to list core Slack packages.
Example would be texlive for 14.2 (conflicts with tetex).

The idea about separate variables for build-time vs. runtime deps is
almost appealing to me. If "foo" is a build dep that can be removed
afterward, and "bar" and "baz" are runtime deps:

REQUIRES="foo bar baz"
BUILDREQ="foo"

...meaning there's some redundancy (foo is listed in both places), but
it'd be backwards compatible with existing tools and workflows. To start
out with, some kind SBo admin would write a script that adds a BUILDREQ=""
line to every .info file, and maintainers could fill them in piecemeal.

From fernando.lopezjr at gmail.com  Sat Mar 10 20:33:47 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sat, 10 Mar 2018 13:33:47 -0700
Subject: [Slackbuilds-users] MEGAsync required deps?
In-Reply-To: <1414218863.1674637.1520683944617.JavaMail.apache@nm52.abv.bg>
References: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
 <3992e34e-6f11-1e7b-86c4-f186fe959936@slackbuilds.org>
 <1414218863.1674637.1520683944617.JavaMail.apache@nm52.abv.bg>
Message-ID: <CALrQ46AK-4LLMnW0XtHJzG6N1W0+yFgOSoyoK8UTpepvJA_MYQ@mail.gmail.com>

I ran it with "--with-freeimage" just as is in the slackbuild and it
compiled and ran
successfully with out the freeimage. Can we remove it from required
dependency
and add it as an optional dependency?

also, can we update it to 3.6.0.0?

thank you!

On Sat, Mar 10, 2018 at 5:12 AM, ????????????? ?????????? <sbolokanov at abv.bg
> wrote:

> --without-freeimage
>
> to build with no freeimage on the system (freeimage fails to build on
> -current anyway).
>
> Dunno what freeimage is used for, but the client seems to run without it.
> Haven't tested the client thoroughly though.
>
> -- ?. ?. ??????????
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>


-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/d572e3d5/attachment.html>

From kingbeowulf at gmail.com  Sat Mar 10 20:40:18 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 10 Mar 2018 12:40:18 -0800
Subject: [Slackbuilds-users] Sage build still broken?
In-Reply-To: <20180310084308.GB3899@dimstar.local.net>
References: <CAFy1yb2=5=G_5LBWoVvJuwjebkCrJDm=q=zH4Kq7quj0JJhaSw@mail.gmail.com>
 <00e0f742-ca9e-ae5f-5565-f59664e12ca3@gmail.com>
 <20180310084308.GB3899@dimstar.local.net>
Message-ID: <53af4f82-2b8f-54b4-b581-9208382d64e5@gmail.com>

On 03/10/2018 12:43 AM, Duncan Roe wrote:
> On Sun, Feb 25, 2018 at 10:59:25AM -0800, King Beowulf wrote:
>> On 02/25/2018 08:44 AM, JCA wrote:
>>> I built Sage 8.0 as available to Slackware 14.2 using the relevant
>>> sbopkg queue.  The build process closes as follows:
>>>
>>> RROR:  The Sage installation tree has moved
>>>
>>> from /tmp/SBo/sage-8.0
>>>   to /opt/sage
>>>
>> ---snip----
>>>
>>>    This in a freshly installed 14.2 system, with 24G RAM and 1TB disk
>>> space. The compilation was completed normally, ending up with 13GB worth
>>> of files in /tmp/SBo, and more than 5GB in /opt/sage.
>>>
>>>    What have I done wrong? If nothing, is there any point in keeping
>>> Sage in Slackbuilds? Even in a beefy system, compiling Sage takes a
>>> several hours - and ending up with lots of GBs eaten up in your hard
>>> drive and a nonfunctional application is frustrating.
>>>
>>
>> I feel your pain, and I do not have a workable solution yet.  Sage
>> upstream is completely hostile to relocatable packages it seems...  The
>> core problem is in how the sage devs have designed their build system.
>>
>--snip--
>>
> Hey Ed,
> 
> SBo has mkchroot which was put together to solve this kind of problem,
> 
> Cheers ... Duncan.

Thanks.  I was hoping to avoid that since upstream now has a way to
generate a 'relocate.py' script to compile a git branch that I can't
seem to get to work. Guess I'll give up and try mkchroot.

-Ed


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/a3ea21d8/attachment.asc>

From fernando.lopezjr at gmail.com  Sat Mar 10 20:49:08 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sat, 10 Mar 2018 13:49:08 -0700
Subject: [Slackbuilds-users] MEGAsync required deps?
In-Reply-To: <CALrQ46AK-4LLMnW0XtHJzG6N1W0+yFgOSoyoK8UTpepvJA_MYQ@mail.gmail.com>
References: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
 <3992e34e-6f11-1e7b-86c4-f186fe959936@slackbuilds.org>
 <1414218863.1674637.1520683944617.JavaMail.apache@nm52.abv.bg>
 <CALrQ46AK-4LLMnW0XtHJzG6N1W0+yFgOSoyoK8UTpepvJA_MYQ@mail.gmail.com>
Message-ID: <CALrQ46AeHNev6AfyokNfPiZV6-Qxi7xGUUqyyrsfUPVcg=kSng@mail.gmail.com>

I don't think that many of the list options need to be added...

**--with-cares \
**--with-cryptopp \
**--with-curl \
  --with-sodium \
  --with-sqlite \
**--with-zlib \
  --with-termcap \
  --with-freeimage \
  --enable-chat \
  --enable-gcc-hardening


according to the mega SDK configure options:

bash-4.4$ ./configure --help

Usage:
 configure [-e] [-f] [-g] [-q] [-z]

Configure MEGA SDK (creates config.h file)

Options:
 -e : Download and link CARES statically.
 -f : Force software packages rebuild.
 -g : Download and link CURL statically.
 -q : Download and link CRYPTOPP statically.
 -z : Do not download and link ZLIB statically.



On Sat, Mar 10, 2018 at 1:33 PM, Fernando Lopez <fernando.lopezjr at gmail.com>
wrote:

> I ran it with "--with-freeimage" just as is in the slackbuild and it
> compiled and ran
> successfully with out the freeimage. Can we remove it from required
> dependency
> and add it as an optional dependency?
>
> also, can we update it to 3.6.0.0?
>
> thank you!
>
> On Sat, Mar 10, 2018 at 5:12 AM, ????????????? ?????????? <
> sbolokanov at abv.bg> wrote:
>
>> --without-freeimage
>>
>> to build with no freeimage on the system (freeimage fails to build on
>> -current anyway).
>>
>> Dunno what freeimage is used for, but the client seems to run without it.
>> Haven't tested the client thoroughly though.
>>
>> -- ?. ?. ??????????
>>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>>
>
>
> --
>
> ------------
> Regards,
>     Fernando Lopez Jr.
>



-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/6f7a5602/attachment.html>

From fernando.lopezjr at gmail.com  Sat Mar 10 20:50:52 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sat, 10 Mar 2018 13:50:52 -0700
Subject: [Slackbuilds-users] MEGAsync required deps?
In-Reply-To: <CALrQ46AeHNev6AfyokNfPiZV6-Qxi7xGUUqyyrsfUPVcg=kSng@mail.gmail.com>
References: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
 <3992e34e-6f11-1e7b-86c4-f186fe959936@slackbuilds.org>
 <1414218863.1674637.1520683944617.JavaMail.apache@nm52.abv.bg>
 <CALrQ46AK-4LLMnW0XtHJzG6N1W0+yFgOSoyoK8UTpepvJA_MYQ@mail.gmail.com>
 <CALrQ46AeHNev6AfyokNfPiZV6-Qxi7xGUUqyyrsfUPVcg=kSng@mail.gmail.com>
Message-ID: <CALrQ46Cin10HMHS7eEyVdrpp4ELo1VHUrLxW_Nuwu1CyKfkPJQ@mail.gmail.com>

bash-4.4$ ldd megasync
linux-vdso.so.1 (0x00007fff865f9000)
libuv.so.1 => /usr/lib64/libuv.so.1 (0x00007f638f238000)
libsqlite3.so.0 => /usr/lib64/libsqlite3.so.0 (0x00007f638ef27000)
librt.so.1 => /lib64/librt.so.1 (0x00007f638ed1f000)
libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f638eaa5000)
libz.so.1 => /lib64/libz.so.1 (0x00007f638e88e000)
libcryptopp.so.5.6 => /usr/lib64/libcryptopp.so.5.6 (0x00007f638e2e1000)
libcares.so.2 => /usr/lib64/libcares.so.2 (0x00007f638e0cf000)
libsodium.so.23 => /usr/lib64/libsodium.so.23 (0x00007f638de7a000)
libssl.so.1 => /lib64/libssl.so.1 (0x00007f638dc08000)
libcrypto.so.1 => /lib64/libcrypto.so.1 (0x00007f638d7b5000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f638d5b1000)
libQtDBus.so.4 => /usr/lib64/qt/lib/libQtDBus.so.4 (0x00007f638d32b000)
libQtXml.so.4 => /usr/lib64/qt/lib/libQtXml.so.4 (0x00007f638d0e3000)
libQtSvg.so.4 => /usr/lib64/qt/lib/libQtSvg.so.4 (0x00007f638ce8a000)
libQtGui.so.4 => /usr/lib64/qt/lib/libQtGui.so.4 (0x00007f638c19d000)
libQtNetwork.so.4 => /usr/lib64/qt/lib/libQtNetwork.so.4
(0x00007f638be4d000)
libQtCore.so.4 => /usr/lib64/qt/lib/libQtCore.so.4 (0x00007f638b955000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f638b736000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f638b3b7000)
libm.so.6 => /lib64/libm.so.6 (0x00007f638b01c000)
libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f638ae05000)
libc.so.6 => /lib64/libc.so.6 (0x00007f638aa1b000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f638a802000)
libicui18n.so.60 => /usr/lib64/libicui18n.so.60 (0x00007f638a343000)
libicuuc.so.60 => /usr/lib64/libicuuc.so.60 (0x00007f6389f83000)
libicudata.so.60 => /usr/lib64/libicudata.so.60 (0x00007f63883db000)
libidn2.so.0 => /usr/lib64/libidn2.so.0 (0x00007f63881be000)
libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x00007f6387f91000)
libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007f6387d48000)
liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007f6387b3a000)
/lib64/ld-linux-x86-64.so.2 (0x00007f638f460000)
libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007f6387938000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f6387627000)
libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007f63873f4000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f6387142000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f6386ef0000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f6386ce9000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f6386ace000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f63868c4000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007f6386680000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f638646e000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f6386133000)
libunistring.so.2 => /usr/lib64/libunistring.so.2 (0x00007f6385db4000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f6385b9a000)
libsasl2.so.3 => /usr/lib64/libsasl2.so.3 (0x00007f638597e000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f638570c000)
libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007f6385470000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f6385260000)
libffi.so.6 => /usr/lib64/../lib64/libffi.so.6 (0x00007f6385058000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f6384e51000)
libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f6384c1f000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f63849fa000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f63847f7000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f63845f2000)


bash-4.4$ ldd megatron
linux-vdso.so.1 (0x00007fff00370000)
libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007f8179fb5000)
liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007f8179da7000)
libsasl2.so.3 => /usr/lib64/libsasl2.so.3 (0x00007f8179b8b000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f8179987000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f817976d000)
libssl.so.1 => /lib64/libssl.so.1 (0x00007f81794fb000)
libcrypto.so.1 => /lib64/libcrypto.so.1 (0x00007f81790a8000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f8178e89000)
libc.so.6 => /lib64/libc.so.6 (0x00007f8178a9f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f817a1fe000)


On Sat, Mar 10, 2018 at 1:49 PM, Fernando Lopez <fernando.lopezjr at gmail.com>
wrote:

> I don't think that many of the list options need to be added...
>
> **--with-cares \
> **--with-cryptopp \
> **--with-curl \
>   --with-sodium \
>   --with-sqlite \
> **--with-zlib \
>   --with-termcap \
>   --with-freeimage \
>   --enable-chat \
>   --enable-gcc-hardening
>
>
> according to the mega SDK configure options:
>
> bash-4.4$ ./configure --help
>
> Usage:
>  configure [-e] [-f] [-g] [-q] [-z]
>
> Configure MEGA SDK (creates config.h file)
>
> Options:
>  -e : Download and link CARES statically.
>  -f : Force software packages rebuild.
>  -g : Download and link CURL statically.
>  -q : Download and link CRYPTOPP statically.
>  -z : Do not download and link ZLIB statically.
>
>
>
> On Sat, Mar 10, 2018 at 1:33 PM, Fernando Lopez <
> fernando.lopezjr at gmail.com> wrote:
>
>> I ran it with "--with-freeimage" just as is in the slackbuild and it
>> compiled and ran
>> successfully with out the freeimage. Can we remove it from required
>> dependency
>> and add it as an optional dependency?
>>
>> also, can we update it to 3.6.0.0?
>>
>> thank you!
>>
>> On Sat, Mar 10, 2018 at 5:12 AM, ????????????? ?????????? <
>> sbolokanov at abv.bg> wrote:
>>
>>> --without-freeimage
>>>
>>> to build with no freeimage on the system (freeimage fails to build on
>>> -current anyway).
>>>
>>> Dunno what freeimage is used for, but the client seems to run without it.
>>> Haven't tested the client thoroughly though.
>>>
>>> -- ?. ?. ??????????
>>>
>>>
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>>
>>>
>>
>>
>> --
>>
>> ------------
>> Regards,
>>     Fernando Lopez Jr.
>>
>
>
>
> --
>
> ------------
> Regards,
>     Fernando Lopez Jr.
>



-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/9f9a834c/attachment-0001.html>

From jebrhansen+SBo at gmail.com  Sat Mar 10 21:26:00 2018
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sat, 10 Mar 2018 21:26:00 +0000
Subject: [Slackbuilds-users] MEGAsync required deps?
In-Reply-To: <CALrQ46AK-4LLMnW0XtHJzG6N1W0+yFgOSoyoK8UTpepvJA_MYQ@mail.gmail.com>
References: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
 <3992e34e-6f11-1e7b-86c4-f186fe959936@slackbuilds.org>
 <1414218863.1674637.1520683944617.JavaMail.apache@nm52.abv.bg>
 <CALrQ46AK-4LLMnW0XtHJzG6N1W0+yFgOSoyoK8UTpepvJA_MYQ@mail.gmail.com>
Message-ID: <CANi9qSvi+CvwRAEGDR7_La9cSQv7MEzXkoUdr-RB085tJJjH1Q@mail.gmail.com>

On Sat, Mar 10, 2018, 2:33 PM Fernando Lopez <fernando.lopezjr at gmail.com>
wrote:

> I ran it with "--with-freeimage" just as is in the slackbuild and it
> compiled and ran
> successfully with out the freeimage. Can we remove it from required
> dependency
> and add it as an optional dependency?
>
> also, can we update it to 3.6.0.0?
>
> thank you!
>

Just so you know, a "required" dependency on SBo is something the
maintainer decided was required, not necessarily something that is actually
required for compilation/running. It may provide a feature that the
maintainer feels is a big enough deal to make it required on his package.

If you feel it should be removed, it should be taken up with the
maintainer, not the mailing list.

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/967ae687/attachment.html>

From yalhcru at gmail.com  Sat Mar 10 22:50:28 2018
From: yalhcru at gmail.com (B Watson)
Date: Sat, 10 Mar 2018 17:50:28 -0500
Subject: [Slackbuilds-users] MEGAsync required deps?
In-Reply-To: <CANi9qSvi+CvwRAEGDR7_La9cSQv7MEzXkoUdr-RB085tJJjH1Q@mail.gmail.com>
References: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
 <3992e34e-6f11-1e7b-86c4-f186fe959936@slackbuilds.org>
 <1414218863.1674637.1520683944617.JavaMail.apache@nm52.abv.bg>
 <CALrQ46AK-4LLMnW0XtHJzG6N1W0+yFgOSoyoK8UTpepvJA_MYQ@mail.gmail.com>
 <CANi9qSvi+CvwRAEGDR7_La9cSQv7MEzXkoUdr-RB085tJJjH1Q@mail.gmail.com>
Message-ID: <CAN1hMuA=yQXyQa9zipkNT41QoNaxv=9PUOz5Th1QhDCBghcKcw@mail.gmail.com>

On 3/10/18, Jeremy Hansen <jebrhansen+SBo at gmail.com> wrote:
> Just so you know, a "required" dependency on SBo is something the
> maintainer decided was required, not necessarily something that is actually
> required for compilation/running. It may provide a feature that the
> maintainer feels is a big enough deal to make it required on his package.

Thanks for putting that into words. I wish it were part of the SBo
documentation.

There's a guy on IRC who insists that e.g. my espeak build shouldn't
have portaudio listed as a dependency, because espeak can be compiled &
run without it... but if you want it to actually *speak* in realtime
(instead of rendering to a .wav file), portaudio is required.

Another example: gzdoom can be built & run without OpenAL, but in that
case it will make NO sound at all, which is definitely not what people
expect when they play a game of Doom.

From fernando.lopezjr at gmail.com  Sat Mar 10 23:18:09 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sat, 10 Mar 2018 16:18:09 -0700
Subject: [Slackbuilds-users] MEGAsync required deps?
In-Reply-To: <CAN1hMuA=yQXyQa9zipkNT41QoNaxv=9PUOz5Th1QhDCBghcKcw@mail.gmail.com>
References: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
 <3992e34e-6f11-1e7b-86c4-f186fe959936@slackbuilds.org>
 <1414218863.1674637.1520683944617.JavaMail.apache@nm52.abv.bg>
 <CALrQ46AK-4LLMnW0XtHJzG6N1W0+yFgOSoyoK8UTpepvJA_MYQ@mail.gmail.com>
 <CANi9qSvi+CvwRAEGDR7_La9cSQv7MEzXkoUdr-RB085tJJjH1Q@mail.gmail.com>
 <CAN1hMuA=yQXyQa9zipkNT41QoNaxv=9PUOz5Th1QhDCBghcKcw@mail.gmail.com>
Message-ID: <CALrQ46BNb+P-xnnuktpHqGsYFmrAsezfGcPhgaY7=-W6AUgp0Q@mail.gmail.com>

yeah I get your point, Jeremy and Watson... but in this case FreeImage is
not being used
at all by the program... not even with the switch "--with-freeimage"

I don't think "--with-freeimage" is a valid switch or needed dependency for
this program.

I compiled all requirements: "libuv", "FreeImage", "cryptopp",
"c-ares", "libsodium"
then I
compiled megasync from sbo.

MEGAsync is not using FreeImage at all. It is not needed.

I used a virtual machine with clean slackware 14.2

this is the ldd of megasync:
linux-vdso.so.1 (0x00007ffe49767000) libuv.so.1 => /usr/lib64/libuv.so.1
(0x00007f0835f4d000) libsqlite3.so.0 => /usr/lib64/libsqlite3.so.0
(0x00007f0835c7b000) librt.so.1 => /lib64/librt.so.1 (0x00007f0835a73000)
libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f0835803000) libz.so.1 =>
/lib64/libz.so.1 (0x00007f08355ed000) libcryptopp.so.5.6 =>
/usr/lib64/libcryptopp.so.5.6 (0x00007f0835029000) libcares.so.2 =>
/usr/lib64/libcares.so.2 (0x00007f0834e17000) libsodium.so.23 =>
/usr/lib64/libsodium.so.23 (0x00007f0834bc0000) libssl.so.1 =>
/lib64/libssl.so.1 (0x00007f083494e000) libcrypto.so.1 =>
/lib64/libcrypto.so.1 (0x00007f08344fe000) libdl.so.2 => /lib64/libdl.so.2
(0x00007f08342f9000) libQtDBus.so.4 => /usr/lib64/qt/lib/libQtDBus.so.4
(0x00007f0834073000) libQtXml.so.4 => /usr/lib64/qt/lib/libQtXml.so.4
(0x00007f0833e2e000) libQtSvg.so.4 => /usr/lib64/qt/lib/libQtSvg.so.4
(0x00007f0833bd4000) libQtGui.so.4 => /usr/lib64/qt/lib/libQtGui.so.4
(0x00007f0832ed8000) libQtNetwork.so.4 =>
/usr/lib64/qt/lib/libQtNetwork.so.4 (0x00007f0832b83000) libQtCore.so.4 =>
/usr/lib64/qt/lib/libQtCore.so.4 (0x00007f0832688000) libpthread.so.0 =>
/lib64/libpthread.so.0 (0x00007f083246b000) libstdc++.so.6 =>
/usr/lib64/libstdc++.so.6 (0x00007f08320f1000) libm.so.6 =>
/lib64/libm.so.6 (0x00007f0831de7000) libgcc_s.so.1 =>
/usr/lib64/libgcc_s.so.1 (0x00007f0831bd0000) libc.so.6 => /lib64/libc.so.6
(0x00007f0831807000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f08315ec000)
libicui18n.so.56 => /usr/lib64/libicui18n.so.56 (0x00007f083115b000)
libicuuc.so.56 => /usr/lib64/libicuuc.so.56 (0x00007f0830dc3000)
libicudata.so.56 => /usr/lib64/libicudata.so.56 (0x00007f082f3df000)
libidn.so.11 => /usr/lib64/libidn.so.11 (0x00007f082f1ac000) libssh2.so.1
=> /usr/lib64/libssh2.so.1 (0x00007f082ef7f000) liblber-2.4.so.2 =>
/usr/lib64/liblber-2.4.so.2 (0x00007f082ed70000) libldap-2.4.so.2 =>
/usr/lib64/libldap-2.4.so.2 (0x00007f082eb27000)
/lib64/ld-linux-x86-64.so.2 (0x000055c5ae190000) libgthread-2.0.so.0 =>
/usr/lib64/libgthread-2.0.so.0 (0x00007f082e925000) libglib-2.0.so.0 =>
/usr/lib64/libglib-2.0.so.0 (0x00007f082e5ef000) libpng16.so.16 =>
/usr/lib64/libpng16.so.16 (0x00007f082e3bd000) libfreetype.so.6 =>
/usr/lib64/libfreetype.so.6 (0x00007f082e120000) libgobject-2.0.so.0 =>
/usr/lib64/libgobject-2.0.so.0 (0x00007f082decf000) libSM.so.6 =>
/usr/lib64/libSM.so.6 (0x00007f082dcc8000) libICE.so.6 =>
/usr/lib64/libICE.so.6 (0x00007f082daac000) libXrender.so.1 =>
/usr/lib64/libXrender.so.1 (0x00007f082d8a3000) libfontconfig.so.1 =>
/usr/lib64/libfontconfig.so.1 (0x00007f082d667000) libXext.so.6 =>
/usr/lib64/libXext.so.6 (0x00007f082d454000) libX11.so.6 =>
/usr/lib64/libX11.so.6 (0x00007f082d117000) libresolv.so.2 =>
/lib64/libresolv.so.2 (0x00007f082cefb000) libsasl2.so.3 =>
/usr/lib64/libsasl2.so.3 (0x00007f082ccdf000) libharfbuzz.so.0 =>
/usr/lib64/libharfbuzz.so.0 (0x00007f082ca61000) libbz2.so.1 =>
/lib64/libbz2.so.1 (0x00007f082c850000) libffi.so.6 =>
/usr/lib64/../lib64/libffi.so.6 (0x00007f082c648000) libuuid.so.1 =>
/lib64/libuuid.so.1 (0x00007f082c443000) libxcb.so.1 =>
/usr/lib64/libxcb.so.1 (0x00007f082c224000) libXau.so.6 =>
/usr/lib64/libXau.so.6 (0x00007f082c021000) libXdmcp.so.6 =>
/usr/lib64/libXdmcp.so.6 (0x00007f082be1b000) libexpat.so.1 =>
/usr/lib64/libexpat.so.1 (0x00007f082bbf2000)


and this is the contents of FreeImage-3.17.0-x86_64-1_SBo.tgz sbo package:
drwxr-xr-x root/root 0 2018-03-10 16:00 ./ drwxr-xr-x root/root 0
2018-03-10 16:00 install/ -rw-r--r-- root/root 450 2018-03-10 16:00
install/doinst.sh -rw-r--r-- root/root 974 2018-03-10 16:00
install/slack-desc drwxr-xr-x root/root 0 2018-03-10 16:00 usr/ drwxr-xr-x
root/root 0 2018-03-10 16:00 usr/include/ -rw-r--r-- root/root 57727
2018-03-10 16:00 usr/include/FreeImage.h -rw-r--r-- root/root 54371
2018-03-10 16:00 usr/include/FreeImagePlus.h drwxr-xr-x root/root 0
2018-03-10 16:00 usr/doc/ drwxr-xr-x root/root 0 2018-03-10 16:00
usr/doc/FreeImage-3.17.0/ -rw-r--r-- root/root 17878 2012-02-25 04:16
usr/doc/FreeImage-3.17.0/license-gplv2.txt -rw-r--r-- root/root 77077
2015-03-15 16:16 usr/doc/FreeImage-3.17.0/Whatsnew.txt -rw-r--r-- root/root
2425 2018-03-10 16:00 usr/doc/FreeImage-3.17.0/FreeImage.SlackBuild
drwxr-xr-x root/root 0 2015-03-15 16:18 usr/doc/FreeImage-3.17.0/Examples/
drwxr-xr-x root/root 0 2015-03-15 16:18
usr/doc/FreeImage-3.17.0/Examples/Plugin/ -rw-r--r-- root/root 9455
2004-07-20 09:48 usr/doc/FreeImage-3.17.0/Examples/Plugin/PluginCradle.cpp
-rw-r--r-- root/root 1501 2015-03-02 01:50
usr/doc/FreeImage-3.17.0/Examples/Plugin/PluginCradle.h drwxr-xr-x
root/root 0 2015-03-15 16:18 usr/doc/FreeImage-3.17.0/Examples/OpenGL/
drwxr-xr-x root/root 0 2015-03-15 16:18
usr/doc/FreeImage-3.17.0/Examples/OpenGL/TextureManager/ -rw-r--r--
root/root 3933 2008-01-29 14:13
usr/doc/FreeImage-3.17.0/Examples/OpenGL/TextureManager/TextureManager.cpp
-rw-r--r-- root/root 1426 2015-03-02 01:50
usr/doc/FreeImage-3.17.0/Examples/OpenGL/TextureManager/TextureManager.h
-rw-r--r-- root/root 1124 2008-01-29 14:11
usr/doc/FreeImage-3.17.0/Examples/OpenGL/TextureManager/readme.txt
drwxr-xr-x root/root 0 2015-03-15 16:18
usr/doc/FreeImage-3.17.0/Examples/Linux/ -rw-r--r-- root/root 2181
2010-06-30 16:56 usr/doc/FreeImage-3.17.0/Examples/Linux/linux-gtk.c
-rw-r--r-- root/root 1599 2005-10-23 07:59
usr/doc/FreeImage-3.17.0/Examples/Linux/linux-svgalib.c -rw-r--r--
root/root 568 2010-06-30 16:56
usr/doc/FreeImage-3.17.0/Examples/Linux/Makefile drwxr-xr-x root/root 0
2015-03-15 16:18 usr/doc/FreeImage-3.17.0/Examples/Generic/ -rw-r--r--
root/root 3832 2004-07-20 09:48
usr/doc/FreeImage-3.17.0/Examples/Generic/FIIO_Mem.cpp -rw-r--r-- root/root
10081 2007-01-22 14:25
usr/doc/FreeImage-3.17.0/Examples/Generic/ShowMetadata.cpp -rw-r--r--
root/root 5016 2004-09-04 08:56
usr/doc/FreeImage-3.17.0/Examples/Generic/FIFImportExport.cpp -rw-r--r--
root/root 4265 2007-01-22 14:30
usr/doc/FreeImage-3.17.0/Examples/Generic/LoadFromHandle.cpp -rw-r--r--
root/root 2760 2004-03-29 16:45
usr/doc/FreeImage-3.17.0/Examples/Generic/LoadFromMemory.cpp -rw-r--r--
root/root 3413 2004-09-04 08:56
usr/doc/FreeImage-3.17.0/Examples/Generic/CloneMultiPage.cpp -rw-r--r--
root/root 2555 2015-03-02 01:50
usr/doc/FreeImage-3.17.0/Examples/Generic/FIIO_Mem.h -rw-r--r-- root/root
5650 2007-01-22 14:30
usr/doc/FreeImage-3.17.0/Examples/Generic/CreateAlpha.cpp -rw-r--r--
root/root 2966 2004-03-29 16:45
usr/doc/FreeImage-3.17.0/Examples/Generic/LoadFromMemory-classified.cpp
-rw-r--r-- root/root 6507 2007-01-22 14:30
usr/doc/FreeImage-3.17.0/Examples/Generic/BatchLoad.cpp -rw-r--r--
root/root 2072 2007-09-06 01:08 usr/doc/FreeImage-3.17.0/README.linux
-rw-r--r-- root/root 34801 2012-02-25 04:17
usr/doc/FreeImage-3.17.0/license-gplv3.txt drwxr-xr-x root/root 0
2015-03-15 16:18 usr/doc/FreeImage-3.17.0/TestAPI/ -rw-r--r-- root/root
14124 2014-10-13 17:23 usr/doc/FreeImage-3.17.0/TestAPI/Test.2013.vcxproj
-rw-r--r-- root/root 4672 2015-02-25 11:04
usr/doc/FreeImage-3.17.0/TestAPI/testMemIO.cpp -rw-r--r-- root/root 4047
2014-04-08 06:36 usr/doc/FreeImage-3.17.0/TestAPI/testThumbnail.cpp
-rw-r--r-- root/root 1227 2014-10-12 04:02
usr/doc/FreeImage-3.17.0/TestAPI/Test.2008.sln -rw-r--r-- root/root 9766
2014-03-19 09:03 usr/doc/FreeImage-3.17.0/TestAPI/testJPEG.cpp -rw-r--r--
root/root 3110 2015-03-02 01:50
usr/doc/FreeImage-3.17.0/TestAPI/TestSuite.h -rw-r--r-- root/root 8403
2010-04-26 15:46 usr/doc/FreeImage-3.17.0/TestAPI/testMPageMemory.cpp
-rw-r--r-- root/root 10186 2014-10-01 21:42
usr/doc/FreeImage-3.17.0/TestAPI/Test.2008.vcproj -rw-r--r-- root/root 3970
2014-04-08 07:51 usr/doc/FreeImage-3.17.0/TestAPI/testWrappedBuffer.cpp
-rw-r--r-- root/root 872 2010-02-09 21:46
usr/doc/FreeImage-3.17.0/TestAPI/Test.2005.sln -rw-r--r-- root/root 1610
2004-03-29 16:45 usr/doc/FreeImage-3.17.0/TestAPI/testPlugins.cpp
-rw-r--r-- root/root 6438 2010-04-26 13:19
usr/doc/FreeImage-3.17.0/TestAPI/testMPageStream.cpp -rw-r--r-- root/root
5448 2010-07-11 15:43 usr/doc/FreeImage-3.17.0/TestAPI/Test.2005.vcproj
-rw-r--r-- root/root 3232 2015-02-25 09:08
usr/doc/FreeImage-3.17.0/TestAPI/MainTestSuite.cpp -rw-r--r-- root/root
261497 2015-02-25 09:04 usr/doc/FreeImage-3.17.0/TestAPI/exif.jxr
-rw-r--r-- root/root 123 2004-07-20 09:48
usr/doc/FreeImage-3.17.0/TestAPI/Makefile -rw-r--r-- root/root 7158
2010-07-15 17:22 usr/doc/FreeImage-3.17.0/TestAPI/testHeaderOnly.cpp
-rw-r--r-- root/root 2686 2010-04-24 19:35
usr/doc/FreeImage-3.17.0/TestAPI/testTools.cpp -rw-r--r-- root/root 5933
2010-04-24 18:05 usr/doc/FreeImage-3.17.0/TestAPI/testMPage.cpp -rw-r--r--
root/root 3902 2010-04-24 19:38
usr/doc/FreeImage-3.17.0/TestAPI/testChannels.cpp -rw-r--r-- root/root
44606 2005-01-04 15:34 usr/doc/FreeImage-3.17.0/TestAPI/exif.jpg -rw-r--r--
root/root 14579 2010-08-17 06:10
usr/doc/FreeImage-3.17.0/TestAPI/testImageType.cpp -rw-r--r-- root/root
42913 2004-12-09 13:09 usr/doc/FreeImage-3.17.0/TestAPI/sample.png
-rw-r--r-- root/root 1335 2014-10-12 03:59
usr/doc/FreeImage-3.17.0/TestAPI/Test.2013.sln -rw-r--r-- root/root 17577
2004-03-29 16:45 usr/doc/FreeImage-3.17.0/license-fi.txt drwxr-xr-x
root/root 0 2018-03-10 16:00 usr/lib64/ -rw-r--r-- root/root 11079976
2018-03-10 16:00 usr/lib64/libfreeimage.a -rwxr-xr-x root/root 6306904
2018-03-10 16:00 usr/lib64/libfreeimageplus-3.17.0.so -rwxr-xr-x root/root
6277752 2018-03-10 16:00 usr/lib64/libfreeimage-3.17.0.so -rw-r--r--
root/root 11146412 2018-03-10 16:00 usr/lib64/libfreeimageplus.a





On Sat, Mar 10, 2018 at 3:50 PM, B Watson <yalhcru at gmail.com> wrote:

> On 3/10/18, Jeremy Hansen <jebrhansen+SBo at gmail.com> wrote:
> > Just so you know, a "required" dependency on SBo is something the
> > maintainer decided was required, not necessarily something that is
> actually
> > required for compilation/running. It may provide a feature that the
> > maintainer feels is a big enough deal to make it required on his package.
>
> Thanks for putting that into words. I wish it were part of the SBo
> documentation.
>
> There's a guy on IRC who insists that e.g. my espeak build shouldn't
> have portaudio listed as a dependency, because espeak can be compiled &
> run without it... but if you want it to actually *speak* in realtime
> (instead of rendering to a .wav file), portaudio is required.
>
> Another example: gzdoom can be built & run without OpenAL, but in that
> case it will make NO sound at all, which is definitely not what people
> expect when they play a game of Doom.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/feb8c683/attachment-0001.html>

From capent at yahoo.com  Sun Mar 11 01:10:26 2018
From: capent at yahoo.com (Felipe Bugno)
Date: Sat, 10 Mar 2018 22:10:26 -0300
Subject: [Slackbuilds-users] MEGAsync required deps?
In-Reply-To: <CALrQ46BNb+P-xnnuktpHqGsYFmrAsezfGcPhgaY7=-W6AUgp0Q@mail.gmail.com>
References: <CALrQ46AXbX6Zdi7zAf_OnN-yzaHCNbiHEDBGuEkJXHJ6yGNE5w@mail.gmail.com>
 <3992e34e-6f11-1e7b-86c4-f186fe959936@slackbuilds.org>
 <1414218863.1674637.1520683944617.JavaMail.apache@nm52.abv.bg>
 <CALrQ46AK-4LLMnW0XtHJzG6N1W0+yFgOSoyoK8UTpepvJA_MYQ@mail.gmail.com>
 <CANi9qSvi+CvwRAEGDR7_La9cSQv7MEzXkoUdr-RB085tJJjH1Q@mail.gmail.com>
 <CAN1hMuA=yQXyQa9zipkNT41QoNaxv=9PUOz5Th1QhDCBghcKcw@mail.gmail.com>
 <CALrQ46BNb+P-xnnuktpHqGsYFmrAsezfGcPhgaY7=-W6AUgp0Q@mail.gmail.com>
Message-ID: <e7fea34b-50d0-a32e-c511-04c6fb872194@yahoo.com>

Hi Fernando,

I'm the maintainer of MEGASync package.

About the Freeimage, the thing is: since MEGA is a fully encrypted file
hosting service, it can't create image thumbnails on server side. Thus,
file previews are sent by the application alongside the file during the
upload process. Without that, when you use the web version of MEGA, you
will not have image previews.

This is explained in their SDK docs (https://mega.nz/doc), section
6.4.4, that i quote below:

"6.4.4 Thumbnails

All applications capable of uploading image files should add thumbnails
in the process (remember that there is no way for us to do this on the
server side). Thumbnails are stored as type 0 file attributes and should
be 120p*120p JPEGs compressed to around 3-4 KB. The sample application
supplied with the SDK demonstrates how to do this using the FreeImage
library. As the extraction of a thumbnail from a large image can take a
considerable amount of time, it is also suggested to perform this in
separate worker threads to avoid stalling the application."

Taking a peek at their source, looks like it can fallback to QT to
create thumbnails if you compile without Freeimage, but it supports far
less file formats.

Why it don't show on ldd i don't know yet, maybe it compile statically
but i must confirm first by looking at SDK automake files. The reason
that i include --with-freeimage on SlackBuild is because the MEGA
developers themselves recommends that for the builds of every platform
(see: https://github.com/meganz/sdk/blob/master/doc/), thus i wanted do
provide the same functionality as the official binary.

On 10/03/2018 20:18, Fernando Lopez wrote:
> yeah I get your point, Jeremy and Watson... but in this
> case?FreeImage?is not being used
> at all by the program... not even with the switch "--with-freeimage"
> I don't think "--with-freeimage" is a valid switch or needed
> dependency for this program.
> I compiled all requirements:
> "libuv",?"FreeImage",?"cryptopp",?"c-ares",?"libsodium" then I
> compiled megasync from sbo.
> MEGAsync is not using FreeImage at all. It is not needed.
> I used a virtual machine with clean slackware 14.2
> this is the ldd of megasync:
> linux-vdso.so.1 (0x00007ffe49767000) libuv.so.1 =>
> /usr/lib64/libuv.so.1 (0x00007f0835f4d000) libsqlite3.so.0 =>
> /usr/lib64/libsqlite3.so.0 (0x00007f0835c7b000) librt.so.1 =>
> /lib64/librt.so.1 (0x00007f0835a73000) libcurl.so.4 =>
> /usr/lib64/libcurl.so.4 (0x00007f0835803000) libz.so.1 =>
> /lib64/libz.so.1 (0x00007f08355ed000) libcryptopp.so.5.6 =>
> /usr/lib64/libcryptopp.so.5.6 (0x00007f0835029000) libcares.so.2 =>
> /usr/lib64/libcares.so.2 (0x00007f0834e17000) libsodium.so.23 =>
> /usr/lib64/libsodium.so.23 (0x00007f0834bc0000) libssl.so.1 =>
> /lib64/libssl.so.1 (0x00007f083494e000) libcrypto.so.1 =>
> /lib64/libcrypto.so.1 (0x00007f08344fe000) libdl.so.2 =>
> /lib64/libdl.so.2 (0x00007f08342f9000) libQtDBus.so.4 =>
> /usr/lib64/qt/lib/libQtDBus.so.4 (0x00007f0834073000) libQtXml.so.4 =>
> /usr/lib64/qt/lib/libQtXml.so.4 (0x00007f0833e2e000) libQtSvg.so.4 =>
> /usr/lib64/qt/lib/libQtSvg.so.4 (0x00007f0833bd4000) libQtGui.so.4 =>
> /usr/lib64/qt/lib/libQtGui.so.4 (0x00007f0832ed8000) libQtNetwork.so.4
> => /usr/lib64/qt/lib/libQtNetwork.so.4 (0x00007f0832b83000)
> libQtCore.so.4 => /usr/lib64/qt/lib/libQtCore.so.4
> (0x00007f0832688000) libpthread.so.0 => /lib64/libpthread.so.0
> (0x00007f083246b000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6
> (0x00007f08320f1000) libm.so.6 => /lib64/libm.so.6
> (0x00007f0831de7000) libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1
> (0x00007f0831bd0000) libc.so.6 => /lib64/libc.so.6
> (0x00007f0831807000) libnsl.so.1 => /lib64/libnsl.so.1
> (0x00007f08315ec000) libicui18n.so.56 => /usr/lib64/libicui18n.so.56
> (0x00007f083115b000) libicuuc.so.56 => /usr/lib64/libicuuc.so.56
> (0x00007f0830dc3000) libicudata.so.56 => /usr/lib64/libicudata.so.56
> (0x00007f082f3df000) libidn.so.11 => /usr/lib64/libidn.so.11
> (0x00007f082f1ac000) libssh2.so.1 => /usr/lib64/libssh2.so.1
> (0x00007f082ef7f000) liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2
> (0x00007f082ed70000) libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2
> (0x00007f082eb27000) /lib64/ld-linux-x86-64.so.2 (0x000055c5ae190000)
> libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0
> (0x00007f082e925000) libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0
> (0x00007f082e5ef000) libpng16.so.16 => /usr/lib64/libpng16.so.16
> (0x00007f082e3bd000) libfreetype.so.6 => /usr/lib64/libfreetype.so.6
> (0x00007f082e120000) libgobject-2.0.so.0 =>
> /usr/lib64/libgobject-2.0.so.0 (0x00007f082decf000) libSM.so.6 =>
> /usr/lib64/libSM.so.6 (0x00007f082dcc8000) libICE.so.6 =>
> /usr/lib64/libICE.so.6 (0x00007f082daac000) libXrender.so.1 =>
> /usr/lib64/libXrender.so.1 (0x00007f082d8a3000) libfontconfig.so.1 =>
> /usr/lib64/libfontconfig.so.1 (0x00007f082d667000) libXext.so.6 =>
> /usr/lib64/libXext.so.6 (0x00007f082d454000) libX11.so.6 =>
> /usr/lib64/libX11.so.6 (0x00007f082d117000) libresolv.so.2 =>
> /lib64/libresolv.so.2 (0x00007f082cefb000) libsasl2.so.3 =>
> /usr/lib64/libsasl2.so.3 (0x00007f082ccdf000) libharfbuzz.so.0 =>
> /usr/lib64/libharfbuzz.so.0 (0x00007f082ca61000) libbz2.so.1 =>
> /lib64/libbz2.so.1 (0x00007f082c850000) libffi.so.6 =>
> /usr/lib64/../lib64/libffi.so.6 (0x00007f082c648000) libuuid.so.1 =>
> /lib64/libuuid.so.1 (0x00007f082c443000) libxcb.so.1 =>
> /usr/lib64/libxcb.so.1 (0x00007f082c224000) libXau.so.6 =>
> /usr/lib64/libXau.so.6 (0x00007f082c021000) libXdmcp.so.6 =>
> /usr/lib64/libXdmcp.so.6 (0x00007f082be1b000) libexpat.so.1 =>
> /usr/lib64/libexpat.so.1 (0x00007f082bbf2000)
> and this is the contents of FreeImage-3.17.0-x86_64-1_SBo.tgz sbo package:
> drwxr-xr-x root/root 0 2018-03-10 16:00 ./ drwxr-xr-x root/root 0
> 2018-03-10 16:00 install/ -rw-r--r-- root/root 450 2018-03-10 16:00
> install/doinst.sh -rw-r--r-- root/root 974 2018-03-10 16:00
> install/slack-desc drwxr-xr-x root/root 0 2018-03-10 16:00 usr/
> drwxr-xr-x root/root 0 2018-03-10 16:00 usr/include/ -rw-r--r--
> root/root 57727 2018-03-10 16:00 usr/include/FreeImage.h -rw-r--r--
> root/root 54371 2018-03-10 16:00 usr/include/FreeImagePlus.h
> drwxr-xr-x root/root 0 2018-03-10 16:00 usr/doc/ drwxr-xr-x root/root
> 0 2018-03-10 16:00 usr/doc/FreeImage-3.17.0/ -rw-r--r-- root/root
> 17878 2012-02-25 04:16 usr/doc/FreeImage-3.17.0/license-gplv2.txt
> -rw-r--r-- root/root 77077 2015-03-15 16:16
> usr/doc/FreeImage-3.17.0/Whatsnew.txt -rw-r--r-- root/root 2425
> 2018-03-10 16:00 usr/doc/FreeImage-3.17.0/FreeImage.SlackBuild
> drwxr-xr-x root/root 0 2015-03-15 16:18
> usr/doc/FreeImage-3.17.0/Examples/ drwxr-xr-x root/root 0 2015-03-15
> 16:18 usr/doc/FreeImage-3.17.0/Examples/Plugin/ -rw-r--r-- root/root
> 9455 2004-07-20 09:48
> usr/doc/FreeImage-3.17.0/Examples/Plugin/PluginCradle.cpp -rw-r--r--
> root/root 1501 2015-03-02 01:50
> usr/doc/FreeImage-3.17.0/Examples/Plugin/PluginCradle.h drwxr-xr-x
> root/root 0 2015-03-15 16:18 usr/doc/FreeImage-3.17.0/Examples/OpenGL/
> drwxr-xr-x root/root 0 2015-03-15 16:18
> usr/doc/FreeImage-3.17.0/Examples/OpenGL/TextureManager/ -rw-r--r--
> root/root 3933 2008-01-29 14:13
> usr/doc/FreeImage-3.17.0/Examples/OpenGL/TextureManager/TextureManager.cpp
> -rw-r--r-- root/root 1426 2015-03-02 01:50
> usr/doc/FreeImage-3.17.0/Examples/OpenGL/TextureManager/TextureManager.h
> -rw-r--r-- root/root 1124 2008-01-29 14:11
> usr/doc/FreeImage-3.17.0/Examples/OpenGL/TextureManager/readme.txt
> drwxr-xr-x root/root 0 2015-03-15 16:18
> usr/doc/FreeImage-3.17.0/Examples/Linux/ -rw-r--r-- root/root 2181
> 2010-06-30 16:56 usr/doc/FreeImage-3.17.0/Examples/Linux/linux-gtk.c
> -rw-r--r-- root/root 1599 2005-10-23 07:59
> usr/doc/FreeImage-3.17.0/Examples/Linux/linux-svgalib.c -rw-r--r--
> root/root 568 2010-06-30 16:56
> usr/doc/FreeImage-3.17.0/Examples/Linux/Makefile drwxr-xr-x root/root
> 0 2015-03-15 16:18 usr/doc/FreeImage-3.17.0/Examples/Generic/
> -rw-r--r-- root/root 3832 2004-07-20 09:48
> usr/doc/FreeImage-3.17.0/Examples/Generic/FIIO_Mem.cpp -rw-r--r--
> root/root 10081 2007-01-22 14:25
> usr/doc/FreeImage-3.17.0/Examples/Generic/ShowMetadata.cpp -rw-r--r--
> root/root 5016 2004-09-04 08:56
> usr/doc/FreeImage-3.17.0/Examples/Generic/FIFImportExport.cpp
> -rw-r--r-- root/root 4265 2007-01-22 14:30
> usr/doc/FreeImage-3.17.0/Examples/Generic/LoadFromHandle.cpp
> -rw-r--r-- root/root 2760 2004-03-29 16:45
> usr/doc/FreeImage-3.17.0/Examples/Generic/LoadFromMemory.cpp
> -rw-r--r-- root/root 3413 2004-09-04 08:56
> usr/doc/FreeImage-3.17.0/Examples/Generic/CloneMultiPage.cpp
> -rw-r--r-- root/root 2555 2015-03-02 01:50
> usr/doc/FreeImage-3.17.0/Examples/Generic/FIIO_Mem.h -rw-r--r--
> root/root 5650 2007-01-22 14:30
> usr/doc/FreeImage-3.17.0/Examples/Generic/CreateAlpha.cpp -rw-r--r--
> root/root 2966 2004-03-29 16:45
> usr/doc/FreeImage-3.17.0/Examples/Generic/LoadFromMemory-classified.cpp
> -rw-r--r-- root/root 6507 2007-01-22 14:30
> usr/doc/FreeImage-3.17.0/Examples/Generic/BatchLoad.cpp -rw-r--r--
> root/root 2072 2007-09-06 01:08 usr/doc/FreeImage-3.17.0/README.linux
> -rw-r--r-- root/root 34801 2012-02-25 04:17
> usr/doc/FreeImage-3.17.0/license-gplv3.txt drwxr-xr-x root/root 0
> 2015-03-15 16:18 usr/doc/FreeImage-3.17.0/TestAPI/ -rw-r--r--
> root/root 14124 2014-10-13 17:23
> usr/doc/FreeImage-3.17.0/TestAPI/Test.2013.vcxproj -rw-r--r--
> root/root 4672 2015-02-25 11:04
> usr/doc/FreeImage-3.17.0/TestAPI/testMemIO.cpp -rw-r--r-- root/root
> 4047 2014-04-08 06:36
> usr/doc/FreeImage-3.17.0/TestAPI/testThumbnail.cpp -rw-r--r--
> root/root 1227 2014-10-12 04:02
> usr/doc/FreeImage-3.17.0/TestAPI/Test.2008.sln -rw-r--r-- root/root
> 9766 2014-03-19 09:03 usr/doc/FreeImage-3.17.0/TestAPI/testJPEG.cpp
> -rw-r--r-- root/root 3110 2015-03-02 01:50
> usr/doc/FreeImage-3.17.0/TestAPI/TestSuite.h -rw-r--r-- root/root 8403
> 2010-04-26 15:46 usr/doc/FreeImage-3.17.0/TestAPI/testMPageMemory.cpp
> -rw-r--r-- root/root 10186 2014-10-01 21:42
> usr/doc/FreeImage-3.17.0/TestAPI/Test.2008.vcproj -rw-r--r-- root/root
> 3970 2014-04-08 07:51
> usr/doc/FreeImage-3.17.0/TestAPI/testWrappedBuffer.cpp -rw-r--r--
> root/root 872 2010-02-09 21:46
> usr/doc/FreeImage-3.17.0/TestAPI/Test.2005.sln -rw-r--r-- root/root
> 1610 2004-03-29 16:45 usr/doc/FreeImage-3.17.0/TestAPI/testPlugins.cpp
> -rw-r--r-- root/root 6438 2010-04-26 13:19
> usr/doc/FreeImage-3.17.0/TestAPI/testMPageStream.cpp -rw-r--r--
> root/root 5448 2010-07-11 15:43
> usr/doc/FreeImage-3.17.0/TestAPI/Test.2005.vcproj -rw-r--r-- root/root
> 3232 2015-02-25 09:08
> usr/doc/FreeImage-3.17.0/TestAPI/MainTestSuite.cpp -rw-r--r--
> root/root 261497 2015-02-25 09:04
> usr/doc/FreeImage-3.17.0/TestAPI/exif.jxr -rw-r--r-- root/root 123
> 2004-07-20 09:48 usr/doc/FreeImage-3.17.0/TestAPI/Makefile -rw-r--r--
> root/root 7158 2010-07-15 17:22
> usr/doc/FreeImage-3.17.0/TestAPI/testHeaderOnly.cpp -rw-r--r--
> root/root 2686 2010-04-24 19:35
> usr/doc/FreeImage-3.17.0/TestAPI/testTools.cpp -rw-r--r-- root/root
> 5933 2010-04-24 18:05 usr/doc/FreeImage-3.17.0/TestAPI/testMPage.cpp
> -rw-r--r-- root/root 3902 2010-04-24 19:38
> usr/doc/FreeImage-3.17.0/TestAPI/testChannels.cpp -rw-r--r-- root/root
> 44606 2005-01-04 15:34 usr/doc/FreeImage-3.17.0/TestAPI/exif.jpg
> -rw-r--r-- root/root 14579 2010-08-17 06:10
> usr/doc/FreeImage-3.17.0/TestAPI/testImageType.cpp -rw-r--r--
> root/root 42913 2004-12-09 13:09
> usr/doc/FreeImage-3.17.0/TestAPI/sample.png -rw-r--r-- root/root 1335
> 2014-10-12 03:59 usr/doc/FreeImage-3.17.0/TestAPI/Test.2013.sln
> -rw-r--r-- root/root 17577 2004-03-29 16:45
> usr/doc/FreeImage-3.17.0/license-fi.txt drwxr-xr-x root/root 0
> 2018-03-10 16:00 usr/lib64/ -rw-r--r-- root/root 11079976 2018-03-10
> 16:00 usr/lib64/libfreeimage.a -rwxr-xr-x root/root 6306904 2018-03-10
> 16:00 usr/lib64/libfreeimageplus-3.17.0.so
> <http://libfreeimageplus-3.17.0.so> -rwxr-xr-x root/root 6277752
> 2018-03-10 16:00 usr/lib64/libfreeimage-3.17.0.so
> <http://libfreeimage-3.17.0.so> -rw-r--r-- root/root 11146412
> 2018-03-10 16:00 usr/lib64/libfreeimageplus.a
>
> On Sat, Mar 10, 2018 at 3:50 PM, B Watson <yalhcru at gmail.com
> <mailto:yalhcru at gmail.com>> wrote:
>
>     On 3/10/18, Jeremy Hansen <jebrhansen+SBo at gmail.com
>     <mailto:jebrhansen%2BSBo at gmail.com>> wrote:
>     > Just so you know, a "required" dependency on SBo is something the
>     > maintainer decided was required, not necessarily something that
>     is actually
>     > required for compilation/running. It may provide a feature that the
>     > maintainer feels is a big enough deal to make it required on his
>     package.
>
>     Thanks for putting that into words. I wish it were part of the SBo
>     documentation.
>
>     There's a guy on IRC who insists that e.g. my espeak build shouldn't
>     have portaudio listed as a dependency, because espeak can be
>     compiled &
>     run without it... but if you want it to actually *speak* in realtime
>     (instead of rendering to a .wav file), portaudio is required.
>
>     Another example: gzdoom can be built & run without OpenAL, but in that
>     case it will make NO sound at all, which is definitely not what people
>     expect when they play a game of Doom.
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>     Archives -
>     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>     FAQ - https://slackbuilds.org/faq/
>
>
>
>
> -- 
>
> ------------
> Regards,
> ? ? Fernando Lopez Jr.
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180310/10b50a81/attachment-0001.html>

From chris.willing at iinet.net.au  Sun Mar 11 21:48:28 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Mon, 12 Mar 2018 07:48:28 +1000
Subject: [Slackbuilds-users] Out of space when building RUST ?
In-Reply-To: <CAN1hMuAR_D59KV584PnFZtG3qKrpws75mBhfOmT2HE3vd7JP6g@mail.gmail.com>
References: <87k1up5rl0.fsf@maillard.im> <20180309001858.GA25116@runbox.no>
 <CAN1hMuAR_D59KV584PnFZtG3qKrpws75mBhfOmT2HE3vd7JP6g@mail.gmail.com>
Message-ID: <50a897c8-7dad-e317-8952-e0f822ac5cc7@iinet.net.au>

> 
>> x86_64:
>> Build time 70 min, peak load 10.23, peak memory 3477M, peak tmp 6691M
>>
>> x86:
>> Build time 96 min, peak load 10.12, peak memory 2447M, peak tmp 6684M
> 

How are these particular build stats generated?

chris

From baildon.research at googlemail.com  Sun Mar 11 23:37:07 2018
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 11 Mar 2018 23:37:07 +0000
Subject: [Slackbuilds-users] Out of space when building RUST ?
In-Reply-To: <50a897c8-7dad-e317-8952-e0f822ac5cc7@iinet.net.au>
References: <87k1up5rl0.fsf@maillard.im> <20180309001858.GA25116@runbox.no>
 <CAN1hMuAR_D59KV584PnFZtG3qKrpws75mBhfOmT2HE3vd7JP6g@mail.gmail.com>
 <50a897c8-7dad-e317-8952-e0f822ac5cc7@iinet.net.au>
Message-ID: <CAMt7G9Teh9hSjD+7M88u3Zf89ye9jwYdNmv5zwUJZPj=9LWD4g@mail.gmail.com>

> How are these particular build stats generated?

slackrepo spits these stats out for any build that takes more than 300
sec. Memory and tmp are bogus if there's other activity on the system,
and memory is highly dependent on the number of jobs, but it's enough
to diagnose build failures.

Cheers
-D.

From chris.willing at iinet.net.au  Mon Mar 12 03:58:47 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Mon, 12 Mar 2018 13:58:47 +1000
Subject: [Slackbuilds-users] Out of space when building RUST ?
In-Reply-To: <CAMt7G9Teh9hSjD+7M88u3Zf89ye9jwYdNmv5zwUJZPj=9LWD4g@mail.gmail.com>
References: <87k1up5rl0.fsf@maillard.im> <20180309001858.GA25116@runbox.no>
 <CAN1hMuAR_D59KV584PnFZtG3qKrpws75mBhfOmT2HE3vd7JP6g@mail.gmail.com>
 <50a897c8-7dad-e317-8952-e0f822ac5cc7@iinet.net.au>
 <CAMt7G9Teh9hSjD+7M88u3Zf89ye9jwYdNmv5zwUJZPj=9LWD4g@mail.gmail.com>
Message-ID: <9ef3e2d1-25b6-8807-7404-d71dfc525afb@iinet.net.au>

On 12/03/18 09:37, David Spencer wrote:
>> How are these particular build stats generated?
> 
> slackrepo spits these stats out for any build that takes more than 300
> sec. Memory and tmp are bogus if there's other activity on the system,
> and memory is highly dependent on the number of jobs, but it's enough
> to diagnose build failures.
>

Thanks David,

It looks like slackrepo's resource_monitor function is what I could use
then :)

chris

From didier at slint.fr  Mon Mar 12 10:42:00 2018
From: didier at slint.fr (Didier Spaier)
Date: Mon, 12 Mar 2018 11:42:00 +0100
Subject: [Slackbuilds-users] What about slack-{required, suggests} files?
In-Reply-To: <CAN1hMuDxjwDYmebW7b7RGhJpkrP7DY81FF1ouMfA+n7apFPLNA@mail.gmail.com>
References: <423851233.1709577.1520688588154.JavaMail.apache@nm51.abv.bg>
 <CAMt7G9S2k4M5c9z=Zb0SbhR0wqm+0JMM_XXPGqtWv+oeD7emiw@mail.gmail.com>
 <CAN1hMuDxjwDYmebW7b7RGhJpkrP7DY81FF1ouMfA+n7apFPLNA@mail.gmail.com>
Message-ID: <2ef75a2c-926c-4570-b507-00e83f70a586@slint.fr>

Caveat: this rant doesn't bring much added value to David's answer to
the OP. Still, here it is, as maybe not every submitter is aware of how
the information about deps is used by some tools.

Le 10/03/2018 ? 20:23, B Watson a ?crit :
> On 3/10/18, David Spencer <baildon.research at googlemail.com> wrote:
> 
>> slack-required in the SBo repository is pointless, we already have
>> REQUIRES= in the .info file. When your preferred build tool builds the
>> package, it can create and package the slack-required file, and/or
>> create a .dep file, and/or PACKAGE REQUIRED line in a .meta file.
> 
> Also, tools that use slack-required are probably going to get confused
> by the fact that our REQUIRES doesn't list core Slackware packages,
> only SBo ones.

the slapt-get tool reads the metada in PACKAGES.TXT like this one for
espeak:

PACKAGE NAME:  espeak-1.48.04-x86_64-4slint.txz
PACKAGE LOCATION:  ./slint
PACKAGE SIZE (compressed):  1096 K
PACKAGE SIZE (uncompressed):  4384 K
PACKAGE REQUIRED:  aaa_elflibs|alsa-lib,aaa_elflibs|gcc,aaa_elflibs|gcc-g++,portaudio
PACKAGE CONFLICTS:  
PACKAGE SUGGESTS:  
PACKAGE DESCRIPTION:
espeak: eSpeak (a compact open source software speech synthesizer)
espeak: 
espeak: eSpeak produces good quality English speech. It uses a different
espeak: synthesis method from other open source text to speech (TTS) engines,
espeak: and sounds quite different. It's perhaps not as natural or smooth,
espeak: but some find the articulation clearer and easier to listen to for
espeak: long periods. It can run as a command line program to speak text from
espeak: a file or from stdin.
espeak: 
espeak: HomePage:http://espeak.sourceforge.net/
espeak: 

In this case PACKAGE REQUIRED lists core Slackware packages as deps, as
they are written by a script that reads the .dep files, themselves
written using George Vlahavas' depfinder, then edited manually when
necessary.

Of course the list of deps depends on the context of the build.
It recently failed to start mate-terminal because I had built it with
webkit2gtk installed, but since removed.

About using the deps to build (not install) a package, the information
is already included in SLACKBUILD.TXT, e.g. this one:
https://slackbuilds.org/slackbuilds/14.2/SLACKBUILDS.TXT

Let's take again the espeak example.

SLACKBUILD NAME: espeak
SLACKBUILD LOCATION: ./accessibility/espeak
SLACKBUILD FILES: README espeak.1 espeak.SlackBuild espeak.info makefile.patch slack-desc
SLACKBUILD VERSION: 1.48.04
SLACKBUILD DOWNLOAD: http://downloads.sourceforge.net/espeak/espeak-1.48.04-source.zip
SLACKBUILD DOWNLOAD_x86_64: 
SLACKBUILD MD5SUM: cadd7482eaafe9239546bdc09fa244c3
SLACKBUILD MD5SUM_x86_64: 
SLACKBUILD REQUIRES: portaudio
SLACKBUILD SHORT DESCRIPTION:  espeak (a compact open source software speech synthesizer)

These lines are copied from espeak.info:
https://slackbuilds.org/slackbuilds/14.2/accessibility/espeak/espeak.info

Here portaudio is rightly listed here as the only needed dependency
beyond a full Slackware installation.

As an aside, slapt-src, used by Slint, Salix and other Slackware
derivatives use this file to manage the dependencies.

So, having a separate slack-required file in a submission would
be redundant at least for this use case IMHO.

I didn't check that slapt-src builds the deps in the right order as
the one give by sqg, but if it could using a similar algorithm.

Have a good day,
Didier

From willysr at slackbuilds.org  Tue Mar 13 07:07:43 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 13 Mar 2018 14:07:43 +0700
Subject: [Slackbuilds-users] MasterPDFEditor on 32 bit
Message-ID: <6250269c-2028-bd72-05ea-c2c3fa871e75@slackbuilds.org>

Hi all,

I got a report that MasterPDFeditor has an OCR issue when using the Qt4
version and upstream recommended to use Qt5 version.

Unfortunately, the Qt5 version is only available for 64 bit
architecture, leaving users who are still using 32 bit at lost.

So, i need to ask the audience in this mailing list whether you are
using MasterPDFEditor and still using 32 bit machine?

I will wait until the end of this month. If there's no one matches the
above criteria, i'm happy to move to Qt5 version and only for 64 bit
architecture.

Thanks

-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180313/10abd491/attachment.asc>

From ozan.turkyilmaz at gmail.com  Tue Mar 13 09:51:03 2018
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 13 Mar 2018 14:51:03 +0500
Subject: [Slackbuilds-users] Retroshare do not work Slackware.
In-Reply-To: <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
References: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
 <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
Message-ID: <CA+da1orA8+L=hbHpPU5obMb=Brdy9g1VAAyBpRCTWNdX2NKPLw@mail.gmail.com>

I have updated libupnp script. I am still on vacation, though.
I am attaching the file for testing. It looks OK from here but I need
better testing with other programs.

2018-02-28 22:59 GMT+05:00 Matteo Bernardini <matteo.bernardini at gmail.com>:

> 2018-02-28 17:40 GMT+01:00 radio radio <hamradioea7 at gmail.com>:
> > I opened a post in linuxquestions.org slackware forum, about "Retroshare
> > 6.0.3" slackbuild.
> >
> > https://www.linuxquestions.org/questions/showthread.php?
> p=5825342#post5825342
> >
> > Ponce suspect an issue with the newer " libupnp ".
>
> I'll try to clarify a little: retroshare.SlackBuild lacks a "set -e"
> line so a package is created also if build breaks and this might have
> lead into the belief that compiling had been succesful.
>
> the error is this:
>
> g++ -c -pipe -Wno-deprecated -Wno-deprecated-declarations -Wno-cpp
> -std=c++0x -Wall -D_FILE_OFFSET_BITS=64 -O2 -pthread -fPIC -Wall -W
> -DRS_ENABLE_GXS -DENABLE_WEBUI -DRS_NO_WARN_DEPRECATED
> -DRS_NO_WARN_CPP -DRS_GXS_TRANS -DRS_USE_BITDHT -DPATCHED_LIBUPNP
> -DPLUGIN_DIR="\"/usr/lib64/retroshare/extensions6\""
> -DDATA_DIR="\"/usr/share/retroshare\"" -DRS_USE_LIBUPNP
> -DSQLITE_HAS_CODEC -DGXS_ENABLE_SYNC_MSGS
> -I/usr/lib64/qt/mkspecs/linux-g++ -I. -I. -I../../libbitdht/src
> -I../../openpgpsdk/src -I/usr/include/upnp -o
> temp/linux-g++/obj/rsinit.o rsserver/rsinit.cc
> In file included from ./upnp/UPnPBase.h:35:0,
>                  from ./upnp/upnphandler_linux.h:13,
>                  from rsserver/rsinit.cc:805:
> /usr/include/upnp/upnpdebug.h:40:24: fatal error: ThreadPool.h: No
> such file or directory
> compilation terminated.
> Makefile.libretroshare:5411: recipe for target
> 'temp/linux-g++/obj/rsinit.o' failed
> make[1]: *** [temp/linux-g++/obj/rsinit.o] Error 1
> make[1]: Leaving directory '/tmp/SBo/RetroShare-0.6.3/libretroshare/src'
> Makefile:90: recipe for target
> 'sub-libretroshare-src-libretroshare-pro-make_default' failed
> make: *** [sub-libretroshare-src-libretroshare-pro-make_default] Error 2
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


-- 
Ozan, BSc, BEng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180313/6a032ee0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libupnp.tar.gz
Type: application/gzip
Size: 3325 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180313/6a032ee0/attachment-0001.bin>

From yth at ythogtha.org  Tue Mar 13 10:04:18 2018
From: yth at ythogtha.org (Ythogtha)
Date: Tue, 13 Mar 2018 11:04:18 +0100
Subject: [Slackbuilds-users] ffmpeg does not compile with opencv 3.4.1
Message-ID: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>

Hi everybody !

	it seems that ffmpeg can't compile with opencv version 3.4.1, here is
the message, it happens straight after the un-tar-ing of the source :

####
[...]
ffmpeg-3.4/COPYING.LGPLv2.1
ffmpeg-3.4/README.md
ffmpeg-3.4/CONTRIBUTING.md
ERROR: opencv not found

If you think configure made a mistake, make sure you are using the latest
version from Git.  If the latest version fails, report the problem to the
ffmpeg-user at ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.
####

Opencv 3.4.1 does seem to work on its own.
ffmpeg compiles fine with OpenCV 3.4.0.
ffmpeg does not work when compiled against OpenCV 3.4.0, if OpenCV is updated to
3.4.1 - but that was to be expected, ffmpeg is pretty touchy with specific
versions of the libraries it uses.

The error is the same if I try with ffmpeg 3.4.2 (the latest).

I don't have a solution, and I just wanted to point that out, since I don't
really use OpenCV, so I can compile my ffmpeg without it (or with the previous
version). I just like my ffmpeg bloated with options ^^

-- 
Arnaud <yth at ythogtha.org>

From matteo.bernardini at gmail.com  Tue Mar 13 10:28:34 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 13 Mar 2018 11:28:34 +0100
Subject: [Slackbuilds-users] Retroshare do not work Slackware.
In-Reply-To: <CA+da1orA8+L=hbHpPU5obMb=Brdy9g1VAAyBpRCTWNdX2NKPLw@mail.gmail.com>
References: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
 <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
 <CA+da1orA8+L=hbHpPU5obMb=Brdy9g1VAAyBpRCTWNdX2NKPLw@mail.gmail.com>
Message-ID: <CAPsDuS4SKL2z7vzk1cRgZhaRAFy+p3uD6bwLt9SKLr_-9PpAAw@mail.gmail.com>

2018-03-13 10:51 GMT+01:00 Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>:
> I have updated libupnp script. I am still on vacation, though.
> I am attaching the file for testing. It looks OK from here but I need better
> testing with other programs.

thanks, I pushed it in my branch.

Matteo

From ozan.turkyilmaz at gmail.com  Tue Mar 13 10:33:53 2018
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 13 Mar 2018 15:33:53 +0500
Subject: [Slackbuilds-users] Retroshare do not work Slackware.
In-Reply-To: <CAPsDuS4SKL2z7vzk1cRgZhaRAFy+p3uD6bwLt9SKLr_-9PpAAw@mail.gmail.com>
References: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
 <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
 <CA+da1orA8+L=hbHpPU5obMb=Brdy9g1VAAyBpRCTWNdX2NKPLw@mail.gmail.com>
 <CAPsDuS4SKL2z7vzk1cRgZhaRAFy+p3uD6bwLt9SKLr_-9PpAAw@mail.gmail.com>
Message-ID: <CA+da1ooGngV8oLkxqGSWMX4B3WAC-kov7qQS-ceF3sUeMsTQvA@mail.gmail.com>

2018-03-13 15:28 GMT+05:00 Matteo Bernardini <matteo.bernardini at gmail.com>:

> 2018-03-13 10:51 GMT+01:00 Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>:
> > I have updated libupnp script. I am still on vacation, though.
> > I am attaching the file for testing. It looks OK from here but I need
> better
> > testing with other programs.
>
> thanks, I pushed it in my branch.
>

I havent been able to compile retroshare but problem is not with libupnp
right now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180313/739594a1/attachment.html>

From chris.willing at iinet.net.au  Tue Mar 13 11:15:03 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 13 Mar 2018 21:15:03 +1000
Subject: [Slackbuilds-users] Retroshare do not work Slackware.
In-Reply-To: <CA+da1ooGngV8oLkxqGSWMX4B3WAC-kov7qQS-ceF3sUeMsTQvA@mail.gmail.com>
References: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
 <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
 <CA+da1orA8+L=hbHpPU5obMb=Brdy9g1VAAyBpRCTWNdX2NKPLw@mail.gmail.com>
 <CAPsDuS4SKL2z7vzk1cRgZhaRAFy+p3uD6bwLt9SKLr_-9PpAAw@mail.gmail.com>
 <CA+da1ooGngV8oLkxqGSWMX4B3WAC-kov7qQS-ceF3sUeMsTQvA@mail.gmail.com>
Message-ID: <135d24bb-91e8-bf8f-cc71-8bc0cf0d44c2@iinet.net.au>

On 13/03/18 20:33, Ozan T?rky?lmaz wrote:
> 
> 2018-03-13 15:28 GMT+05:00 Matteo Bernardini
> <matteo.bernardini at gmail.com <mailto:matteo.bernardini at gmail.com>>:
> 
>     2018-03-13 10:51 GMT+01:00 Ozan T?rky?lmaz
>     <ozan.turkyilmaz at gmail.com <mailto:ozan.turkyilmaz at gmail.com>>:
>     > I have updated libupnp script. I am still on vacation, though.
>     > I am attaching the file for testing. It looks OK from here but I need better
>     > testing with other programs.
> 
>     thanks, I pushed it in my branch.
> 
> 
> I havent been able to compile retroshare but problem is not with libupnp
> right now.
> 

Yes, that patch is just a partial fix.

The API for libupnp has changed in the new 1.8.x versions (SBo has
libupnp-1.8.3 at the moment). Retroshare devs will need to update their
code to utilize the new libupnp API.

Without any indication of how long that might take, maybe we need a
libupnp-legacy SlackBuild with version capped at the latest in the 1.6.x
series so that retroshare can continue to be built. Otherwise we sit
tight with a SlackBuild that won't build until upstream updates their code.

chris

From matteo.bernardini at gmail.com  Tue Mar 13 11:40:33 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 13 Mar 2018 12:40:33 +0100
Subject: [Slackbuilds-users] Retroshare do not work Slackware.
In-Reply-To: <135d24bb-91e8-bf8f-cc71-8bc0cf0d44c2@iinet.net.au>
References: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
 <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
 <CA+da1orA8+L=hbHpPU5obMb=Brdy9g1VAAyBpRCTWNdX2NKPLw@mail.gmail.com>
 <CAPsDuS4SKL2z7vzk1cRgZhaRAFy+p3uD6bwLt9SKLr_-9PpAAw@mail.gmail.com>
 <CA+da1ooGngV8oLkxqGSWMX4B3WAC-kov7qQS-ceF3sUeMsTQvA@mail.gmail.com>
 <135d24bb-91e8-bf8f-cc71-8bc0cf0d44c2@iinet.net.au>
Message-ID: <CAPsDuS58ckwoHfg_U2-XBG74WyFOGO+Q4z_t17TSO2O_eZTNjQ@mail.gmail.com>

2018-03-13 12:15 GMT+01:00 Christoph Willing <chris.willing at iinet.net.au>:
> On 13/03/18 20:33, Ozan T?rky?lmaz wrote:
>> I havent been able to compile retroshare but problem is not with libupnp
>> right now.
>>
>
> Yes, that patch is just a partial fix.
>
> The API for libupnp has changed in the new 1.8.x versions (SBo has
> libupnp-1.8.3 at the moment). Retroshare devs will need to update their
> code to utilize the new libupnp API.
>
> Without any indication of how long that might take, maybe we need a
> libupnp-legacy SlackBuild with version capped at the latest in the 1.6.x
> series so that retroshare can continue to be built. Otherwise we sit
> tight with a SlackBuild that won't build until upstream updates their code.

yes, I can confirm the issue seems still related to the newer libupnp

https://pastebin.com/raw/Yk07FRuA

From rshepard at appl-ecosys.com  Tue Mar 13 12:45:03 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 13 Mar 2018 05:45:03 -0700 (PDT)
Subject: [Slackbuilds-users] MasterPDFEditor on 32 bit
In-Reply-To: <6250269c-2028-bd72-05ea-c2c3fa871e75@slackbuilds.org>
References: <6250269c-2028-bd72-05ea-c2c3fa871e75@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.1803130543020.28718@salmo.appl-ecosys.com>

On Tue, 13 Mar 2018, Willy Sudiarto Raharjo wrote:

> So, i need to ask the audience in this mailing list whether you are using
> MasterPDFEditor and still using 32 bit machine?

Willy,

   Yes, I am, on two hosts: desktop and Dell Latitude 2100 with an Atom
processor. Currently running MasterPDFEditor-4.3.82 with Qt4.

Rich

From orbea at fredslev.dk  Tue Mar 13 05:23:41 2018
From: orbea at fredslev.dk (orbea at fredslev.dk)
Date: Mon, 12 Mar 2018 22:23:41 -0700
Subject: [Slackbuilds-users] python-xlib
Message-ID: <20180312222341.66ff8881@Akita.witch.org>

Hi,

I am maintaining the python3-xlib build script which when I first
submitted it was distinct from python-xlib which was already in the
repo. However at some point this changed and python3 support was added
to the main python-xlib upstream. Consequently my requirement for it in
pyewmh and caffeine-ng is now python-xlib rather than python3-xlib
which has not received any updates upstream since.

The problem is that the python-xlib at SBo is rather out of date, lacks
python3 support and when I contacted the maintainer with the e-mail in
the .info file I received a mailer-daemon reply saying the address no
longer exists.

If anyone knows how to contact the maintainer that would be helpful. If
needed I can take over python-xlib which should replace python3-xlib.

From matteo.bernardini at gmail.com  Tue Mar 13 13:09:12 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 13 Mar 2018 14:09:12 +0100
Subject: [Slackbuilds-users] python-xlib
In-Reply-To: <20180312222341.66ff8881@Akita.witch.org>
References: <20180312222341.66ff8881@Akita.witch.org>
Message-ID: <CAPsDuS5AnhPpoJ+w+Fxo-u0B73OTfGeicDfS5bg0qeH4U0e-fw@mail.gmail.com>

2018-03-13 6:23 GMT+01:00 orbea at fredslev.dk <orbea at fredslev.dk>:
> Hi,
>
> I am maintaining the python3-xlib build script which when I first
> submitted it was distinct from python-xlib which was already in the
> repo. However at some point this changed and python3 support was added
> to the main python-xlib upstream. Consequently my requirement for it in
> pyewmh and caffeine-ng is now python-xlib rather than python3-xlib
> which has not received any updates upstream since.
>
> The problem is that the python-xlib at SBo is rather out of date, lacks
> python3 support and when I contacted the maintainer with the e-mail in
> the .info file I received a mailer-daemon reply saying the address no
> longer exists.
>
> If anyone knows how to contact the maintainer that would be helpful. If
> needed I can take over python-xlib which should replace python3-xlib.

IMHO it's perfectly fine for you to take over python-xlib as its
maintainer is completely inactive since eight years.

From chris.willing at iinet.net.au  Tue Mar 13 13:33:53 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 13 Mar 2018 23:33:53 +1000
Subject: [Slackbuilds-users] ffmpeg does not compile with opencv 3.4.1
In-Reply-To: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>
References: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>
Message-ID: <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>

On 13/03/18 20:04, Ythogtha wrote:
> Hi everybody !
> 
> 	it seems that ffmpeg can't compile with opencv version 3.4.1, here is
> the message, it happens straight after the un-tar-ing of the source :
> 
> ####
> [...]
> ffmpeg-3.4/COPYING.LGPLv2.1
> ffmpeg-3.4/README.md
> ffmpeg-3.4/CONTRIBUTING.md
> ERROR: opencv not found
> 
> If you think configure made a mistake, make sure you are using the latest
> version from Git.  If the latest version fails, report the problem to the
> ffmpeg-user at ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
> Include the log file "ffbuild/config.log" produced by configure as this will help
> solve the problem.
> ####
> 
> Opencv 3.4.1 does seem to work on its own.
> ffmpeg compiles fine with OpenCV 3.4.0.
> ffmpeg does not work when compiled against OpenCV 3.4.0, if OpenCV is updated to
> 3.4.1 - but that was to be expected, ffmpeg is pretty touchy with specific
> versions of the libraries it uses.
> 
> The error is the same if I try with ffmpeg 3.4.2 (the latest).
> 
> I don't have a solution, and I just wanted to point that out, since I don't
> really use OpenCV, so I can compile my ffmpeg without it (or with the previous
> version). I just like my ffmpeg bloated with options ^^
> 

An interesting problem - opencv is optional for ffmpeg and ffmpeg is
optional for opencv i.e. an optional circular dependency.

chris


From fellype at gmail.com  Tue Mar 13 13:38:14 2018
From: fellype at gmail.com (Fellype do Nascimento)
Date: Tue, 13 Mar 2018 10:38:14 -0300
Subject: [Slackbuilds-users] MasterPDFEditor on 32 bit
In-Reply-To: <alpine.LNX.2.20.1803130543020.28718@salmo.appl-ecosys.com>
References: <6250269c-2028-bd72-05ea-c2c3fa871e75@slackbuilds.org>
 <alpine.LNX.2.20.1803130543020.28718@salmo.appl-ecosys.com>
Message-ID: <bc9d11b3-fff8-5807-073b-34fee790fdb9@gmail.com>

On 03/13/2018 09:45 AM, Rich Shepard wrote:
> On Tue, 13 Mar 2018, Willy Sudiarto Raharjo wrote:
>
>> So, i need to ask the audience in this mailing list whether you are 
>> using
>> MasterPDFEditor and still using 32 bit machine?
>
> Willy,
>
> ? Yes, I am, on two hosts: desktop and Dell Latitude 2100 with an Atom
> processor. Currently running MasterPDFEditor-4.3.82 with Qt4.
Hi Willy,
I also still using a 32 bits machine and MasterPDFEditor 4 + Qt4. But I 
don't care if it is kept in version 4.3.82. That is, I don't need it to 
be updated.
So, it is OK for me if you move to Qt5 version and for 64 bit only.

Fellype

From willysr at slackbuilds.org  Tue Mar 13 13:45:34 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 13 Mar 2018 20:45:34 +0700
Subject: [Slackbuilds-users] MasterPDFEditor on 32 bit
In-Reply-To: <bc9d11b3-fff8-5807-073b-34fee790fdb9@gmail.com>
References: <6250269c-2028-bd72-05ea-c2c3fa871e75@slackbuilds.org>
 <alpine.LNX.2.20.1803130543020.28718@salmo.appl-ecosys.com>
 <bc9d11b3-fff8-5807-073b-34fee790fdb9@gmail.com>
Message-ID: <f14f23ae-75c8-53e3-f41d-16a8048b49ae@slackbuilds.org>

>> ? Yes, I am, on two hosts: desktop and Dell Latitude 2100 with an Atom
>> processor. Currently running MasterPDFEditor-4.3.82 with Qt4.
> Hi Willy,
> I also still using a 32 bits machine and MasterPDFEditor 4 + Qt4. But I
> don't care if it is kept in version 4.3.82. That is, I don't need it to
> be updated.
> So, it is OK for me if you move to Qt5 version and for 64 bit only.

Hi Fellype

Upstream support both Qt4 and Qt5, but Qt5 is only for 64 bit
architecture, so if i moved to Qt5, the Qt4 will no longer be available
in the repository.

That's why i need to ask whether there are users who still use 32 bit
machines. Since there are some people who still use 32 bit, i'm going to
keep providing Qt4 version in the repository.

I will make a note in the README for those who wanted to use Qt5 version.



-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180313/fe3398f4/attachment.asc>

From yth at ythogtha.org  Tue Mar 13 13:59:14 2018
From: yth at ythogtha.org (Ythogtha)
Date: Tue, 13 Mar 2018 14:59:14 +0100
Subject: [Slackbuilds-users] ffmpeg does not compile with opencv 3.4.1
In-Reply-To: <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>
References: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>
 <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>
Message-ID: <20180313145914.129330ad528f5c053b4e31c5@ythogtha.org>

> On 13/03/18 20:04, Ythogtha wrote:
> > Hi everybody !
> > 
> > 	it seems that ffmpeg can't compile with opencv version 3.4.1, here is
> > the message, it happens straight after the un-tar-ing of the source :
> > 
> > ####
> > [...]
> > ffmpeg-3.4/COPYING.LGPLv2.1
> > ffmpeg-3.4/README.md
> > ffmpeg-3.4/CONTRIBUTING.md
> > ERROR: opencv not found
> > 
> > If you think configure made a mistake, make sure you are using the latest
> > version from Git.  If the latest version fails, report the problem to the
> > ffmpeg-user at ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
> > Include the log file "ffbuild/config.log" produced by configure as this will
> > help solve the problem.
> > ####
> > 
> > Opencv 3.4.1 does seem to work on its own.
> > ffmpeg compiles fine with OpenCV 3.4.0.
> > ffmpeg does not work when compiled against OpenCV 3.4.0, if OpenCV is
> > updated to 3.4.1 - but that was to be expected, ffmpeg is pretty touchy with
> > specific versions of the libraries it uses.
> > 
> > The error is the same if I try with ffmpeg 3.4.2 (the latest).
> > 
> > I don't have a solution, and I just wanted to point that out, since I don't
> > really use OpenCV, so I can compile my ffmpeg without it (or with the
> > previous version). I just like my ffmpeg bloated with options ^^
> > 
> 
> An interesting problem - opencv is optional for ffmpeg and ffmpeg is
> optional for opencv i.e. an optional circular dependency.
> 
> chris

Yep, that's pretty funny :)
	Though in the past it wasn't very difficult to handle.
Opencv can be built against ffmpeg even if ffmpeg doesn't run because you just
removed the opencv against which it was built, and rebuilding ffmpeg with the
new opencv after that doesn't break opencv. (You follow me ? :))
	So well usually, when one of them is updated, you just had to rebuild
it, install it, then rebuild the other one.
	I haven't tested going at it from scratch on a clean 14.2 VM, but the
error doesn't suggest there is a side effect of this circular dependency.
Something changed in OpenCV 3.4.1, and ffmpeg can't find it anymore.
And the git diff on opencv's slackbuild does not help me there either, it was a
pretty simple version bump.

-- 
Arnaud <yth at ythogtha.org>

From rshepard at appl-ecosys.com  Tue Mar 13 14:11:40 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 13 Mar 2018 07:11:40 -0700 (PDT)
Subject: [Slackbuilds-users] MasterPDFEditor on 32 bit
In-Reply-To: <f14f23ae-75c8-53e3-f41d-16a8048b49ae@slackbuilds.org>
References: <6250269c-2028-bd72-05ea-c2c3fa871e75@slackbuilds.org>
 <alpine.LNX.2.20.1803130543020.28718@salmo.appl-ecosys.com>
 <bc9d11b3-fff8-5807-073b-34fee790fdb9@gmail.com>
 <f14f23ae-75c8-53e3-f41d-16a8048b49ae@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.1803130711190.28718@salmo.appl-ecosys.com>

On Tue, 13 Mar 2018, Willy Sudiarto Raharjo wrote:

> Since there are some people who still use 32 bit, i'm going to keep
> providing Qt4 version in the repository.

   Thanks, Willy.

Rich

From falsetti at clansco.org  Tue Mar 13 15:53:37 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Tue, 13 Mar 2018 16:53:37 +0100
Subject: [Slackbuilds-users] ffmpeg does not compile with opencv 3.4.1
In-Reply-To: <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>
References: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>
 <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>
Message-ID: <20180313165337.14c09e6487301df19cd8aa58@clansco.org>

On Tue, 13 Mar 2018 23:33:53 +1000
Christoph Willing <chris.willing at iinet.net.au> wrote:


> 
> An interesting problem - opencv is optional for ffmpeg and ffmpeg is
> optional for opencv i.e. an optional circular dependency.
> 

to compile ffmpeg against  I have to :
1) build ffmpeg without CHROMAPRINT,
2) rebuild CHROMAPRINT,
3) compile ffmpeg with CHROMAPRINT

From x80 at telus.net  Tue Mar 13 16:15:54 2018
From: x80 at telus.net (x80)
Date: Tue, 13 Mar 2018 09:15:54 -0700
Subject: [Slackbuilds-users] Jack-rack make failure
Message-ID: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>

ld returns an odd error "jack_rack-midi.o: undefined reference to symbol 
'pthread_create@@GLIBC_2.2.5'

/lib64/libpthread.so.0: error adding symbols: DSO missing from command line"

This is on a fully updated 14.2 box. I see no errors in the configure 
log and all lib paths are ok.

I'm not quite sure how to get past this one.


From falsetti at clansco.org  Tue Mar 13 16:19:18 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Tue, 13 Mar 2018 17:19:18 +0100
Subject: [Slackbuilds-users] ffmpeg does not compile with opencv 3.4.1
In-Reply-To: <20180313165337.14c09e6487301df19cd8aa58@clansco.org>
References: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>
 <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>
 <20180313165337.14c09e6487301df19cd8aa58@clansco.org>
Message-ID: <20180313171918.609c514261ec4d84d4186103@clansco.org>

On Tue, 13 Mar 2018 16:53:37 +0100
Fr?d?ric Falsetti <falsetti at clansco.org> wrote:

> On Tue, 13 Mar 2018 23:33:53 +1000
> Christoph Willing <chris.willing at iinet.net.au> wrote:
> 
> 
> > 
> > An interesting problem - opencv is optional for ffmpeg and ffmpeg is
> > optional for opencv i.e. an optional circular dependency.
> > 
> 
> to compile ffmpeg against  I have to :
to compile ffmpeg against CHROMAPRINT ;/

> 1) build ffmpeg without CHROMAPRINT,
> 2) rebuild CHROMAPRINT,
> 3) compile ffmpeg with CHROMAPRINT

perhaps this can help  for opencv




From yalhcru at gmail.com  Tue Mar 13 18:21:12 2018
From: yalhcru at gmail.com (B Watson)
Date: Tue, 13 Mar 2018 14:21:12 -0400
Subject: [Slackbuilds-users] Jack-rack make failure
In-Reply-To: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
References: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
Message-ID: <CAN1hMuAbRh3DUA-zwvq9R7nA9+WroDFsewy5G5-2s_fu7dcyvw@mail.gmail.com>

On 3/13/18, x80 <x80 at telus.net> wrote:
> ld returns an odd error "jack_rack-midi.o: undefined reference to symbol
> 'pthread_create@@GLIBC_2.2.5'
>
> /lib64/libpthread.so.0: error adding symbols: DSO missing from command
> line"
>
> This is on a fully updated 14.2 box. I see no errors in the configure
> log and all lib paths are ok.
>
> I'm not quite sure how to get past this one.

Hm. The 2nd error message usually means "-lpthread" is missing,
during linking.

It builds fine on my fully-updated 64-bit 14.2 box...

Check the file /usr/lib64/pkgconfig/jack.pc and see if has a line
like this:

Libs: -L${libdir} -ljack -lpthread

Also, it's just occurred to me... are you using jack-audio-connection-kit
(AKA jack-0.125.0), or jack2 (AKA jack2-1.9.10)? I just recently took
over maintenance of jack2, but haven't done anything with it yet.

From x80 at telus.net  Tue Mar 13 19:37:46 2018
From: x80 at telus.net (x80)
Date: Tue, 13 Mar 2018 12:37:46 -0700
Subject: [Slackbuilds-users] Jack-rack make failure
In-Reply-To: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
References: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
Message-ID: <d1359bd3-7fe4-923b-b5ab-f743bb5ef811@telus.net>



On 03/13/2018 11:21 AM, B Watson wrote:
> On 3/13/18, x80 <x80 at telus.net> wrote:
>> ld returns an odd error "jack_rack-midi.o: undefined reference to symbol
>> 'pthread_create@@GLIBC_2.2.5'
>>
>> /lib64/libpthread.so.0: error adding symbols: DSO missing from command
>> line"
>>
>> This is on a fully updated 14.2 box. I see no errors in the configure
>> log and all lib paths are ok.
>>
>> I'm not quite sure how to get past this one.
> Hm. The 2nd error message usually means "-lpthread" is missing,
> during linking.
>
> It builds fine on my fully-updated 64-bit 14.2 box...
>
> Check the file /usr/lib64/pkgconfig/jack.pc and see if has a line
> like this:
>
> Libs: -L${libdir} -ljack -lpthread
>
> Also, it's just occurred to me... are you using jack-audio-connection-kit
> (AKA jack-0.125.0), or jack2 (AKA jack2-1.9.10)? I just recently took
> over maintenance of jack2, but haven't done anything with it yet.
>
Yes it's jack2.
The Libs line in jack.pc looks like this:

Libs: -L/usr/lib64 -ljack

Seems it wasn't compiled with pthreads. I wonder if it's not a corrupt lib?


From yalhcru at gmail.com  Tue Mar 13 21:54:41 2018
From: yalhcru at gmail.com (B Watson)
Date: Tue, 13 Mar 2018 17:54:41 -0400
Subject: [Slackbuilds-users] Jack-rack make failure
In-Reply-To: <d1359bd3-7fe4-923b-b5ab-f743bb5ef811@telus.net>
References: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
 <d1359bd3-7fe4-923b-b5ab-f743bb5ef811@telus.net>
Message-ID: <CAN1hMuDmJj5YRpQUE3FwojE2W0P7EkcjfR2qV=h7fcs+PuaZtg@mail.gmail.com>

On 3/13/18, x80 <x80 at telus.net> wrote:
> Yes it's jack2.
> The Libs line in jack.pc looks like this:
>
> Libs: -L/usr/lib64 -ljack
>
> Seems it wasn't compiled with pthreads. I wonder if it's not a corrupt lib?

Eh, it probably isn't "corrupt", it's probably just that jack-rack
expects the .pc file for the jack library to always include -lpthread,
so doesn't include -lpthread explicitly.

You can use ldd on the jack library to find out whether or not it was
compiled with pthreads (I suspect it was), but whether or not jack2 was
built with pthreads, jack-rack has to be.

In jack-rack.SlackBuild, the configure command reads:

LDFLAGS="-lm -ldl" \
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
  --prefix=/usr \
  --libdir=/usr/lib${LIBDIRSUFFIX} \
  --sysconfdir=/etc \
  --localstatedir=/var \
  --mandir=/usr/man \
  $LASH_OPT \
  --disable-gnome \
  --build=$ARCH-slackware-linux

Change the first line of that to read:

LDFLAGS="-lm -ldl -lpthread" \

...don't forget the trailing backslash!

Let me know whether or not that fixes the problem... and even if it
fixes this specific issue, there may be others.

If that fixes it, I'll probably just patch jack2's .pc file to include
-lpthread, since I suspect lots of other jack apps will have the same
problem when built with jack2.

Basically, jack2 on SBo is almost completely untested. Someone
submitted it a few years back and never updated it, and none of the
READMEs for any of the JACK-related stuff mentions it. They all list
jack-audio-connection-kit (AKA jack1) as a dependency in their .info
files, so that's what people end up using.

You're the first user I've met who has even tried jack2, so I'm very
interested to know what you've done with it. What SBo JACK stuff have
you installed, and how well do they work, that sort of thing.

From yth at ythogtha.org  Wed Mar 14 13:41:32 2018
From: yth at ythogtha.org (Ythogtha)
Date: Wed, 14 Mar 2018 14:41:32 +0100
Subject: [Slackbuilds-users] OpenCV SlackBuild bug - Was: ffmpeg does not
 compile with opencv 3.4.1
In-Reply-To: <20180313171918.609c514261ec4d84d4186103@clansco.org>
References: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>
 <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>
 <20180313165337.14c09e6487301df19cd8aa58@clansco.org>
 <20180313171918.609c514261ec4d84d4186103@clansco.org>
Message-ID: <20180314144132.f8b8923856e25885e16710c5@ythogtha.org>

> On Tue, 13 Mar 2018 16:53:37 +0100
> Fr?d?ric Falsetti <falsetti at clansco.org> wrote:
> 
> > On Tue, 13 Mar 2018 23:33:53 +1000
> > Christoph Willing <chris.willing at iinet.net.au> wrote:
> > 
> > 
> > > 
> > > An interesting problem - opencv is optional for ffmpeg and ffmpeg is
> > > optional for opencv i.e. an optional circular dependency.
> > > 
> > 
> > to compile ffmpeg against  I have to :
> to compile ffmpeg against CHROMAPRINT ;/
> 
> > 1) build ffmpeg without CHROMAPRINT,
> > 2) rebuild CHROMAPRINT,
> > 3) compile ffmpeg with CHROMAPRINT
> 
> perhaps this can help  for opencv

Well, that's the initial step for building ffmpeg with OpenCV.
That or the reverse : building openCV without ffmpeg, then ffmpeg with openCV
then openCV with ffmpeg.
But I did that quite some time ago and since then I could always build one of
them with the existing other one built against the older version.
And besides, OpenCV builds just fine, and the various binaries are launching
with every version.

	Anyway, I found the problem.
It's with the opencv.SlackBuild, or more precisely with opencv itself because
the SlackBuild didn't change and was working fine before.
OpenCV libraries are installed in /usr/lib6464/ !
In the opencv.SlackBuild there is a LIBDIRSUFFIX="64" configured when ARCH=x86_64
and it seems the opencv make process now does that step itself, installing
itself into /usr/lib64, so adding the LIBDIRSUFFIX="64" moves the .so files
into /usr/lib6464/

	So setting LIBDIRSUFFIX="" looks like a good idea.
Except then there are python libraries installed in /usr/lib/ !
usr/lib/python2.7/site-packages/cv2.so
usr/lib/python3.6/site-packages/cv2.cpython-36m-x86_64-linux-gnu.so
And import cv2 doesn't work in either python or python3.

	I tried moving usr/lib/python* into usr/lib64/ just before makepkg in the
SlackBuild, and everything seems to work fine, I can import cv2 in python and
python3. The hack is ugly and there should be a cleaner way to handle that.

	The ffmpeg problem is fully solved, it compiles fine with openCV
installed correctly in /usr/lib64/, and it even works when built against
OpenCV 3.4.0 with OpenCV is bumped to 3.4.1. And it still works when bumping
ffmpeg to 3.4.2.

Here is my opencv.SlackBuild diff :
diff --git a/libraries/opencv/opencv.SlackBuild
b/libraries/opencv/opencv.SlackBuild index 13e5dea42b..0a0a569600 100644
--- a/libraries/opencv/opencv.SlackBuild
+++ b/libraries/opencv/opencv.SlackBuild
@@ -27,7 +27,7 @@
 PRGNAM=opencv
 PRGNAM2=opencv_contrib
 VERSION=${VERSION:-3.4.1}
-BUILD=${BUILD:-2}
+BUILD=${BUILD:-3}
 TAG=${TAG:-_SBo}

 if [ -z "$ARCH" ]; then
@@ -51,7 +51,7 @@ elif [ "$ARCH" = "i686" ]; then
   LIBDIRSUFFIX=""
 elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
-  LIBDIRSUFFIX="64"
+  LIBDIRSUFFIX=""
 else
   SLKCFLAGS="-O2"
   LIBDIRSUFFIX=""
@@ -137,4 +137,6 @@ mkdir -p $PKG/install
 cat $CWD/slack-desc > $PKG/install/slack-desc

 cd $PKG
+mv usr/lib/* usr/lib64
+rmdir usr/lib
 /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.
${PKGTYPE:-tgz}

	I, sadly, don't have enough time to investigate further on how to
correct the build so that everything is at the right place.

-- 
Arnaud <yth at ythogtha.org>

From yth at ythogtha.org  Wed Mar 14 13:57:11 2018
From: yth at ythogtha.org (Ythogtha)
Date: Wed, 14 Mar 2018 14:57:11 +0100
Subject: [Slackbuilds-users] OpenCV SlackBuild bug - Was: ffmpeg does
 not compile with opencv 3.4.1
In-Reply-To: <20180314144132.f8b8923856e25885e16710c5@ythogtha.org>
References: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>
 <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>
 <20180313165337.14c09e6487301df19cd8aa58@clansco.org>
 <20180313171918.609c514261ec4d84d4186103@clansco.org>
 <20180314144132.f8b8923856e25885e16710c5@ythogtha.org>
Message-ID: <20180314145711.599170e2cbf0a8295fa9b07f@ythogtha.org>

> 	The ffmpeg problem is fully solved, it compiles fine with openCV
> installed correctly in /usr/lib64/, and it even works when built against
> OpenCV 3.4.0 with OpenCV is bumped to 3.4.1. And it still works when bumping
> ffmpeg to 3.4.2.

Oops, my mistake here, the ffmpeg problem is still unsolved after correction of
OpenCV libraries path. It still refuses t build complaining that:
ERROR: opencv not found

So back to square one :)


-- 
Arnaud <yth at ythogtha.org>

From x80 at telus.net  Wed Mar 14 17:54:00 2018
From: x80 at telus.net (x80)
Date: Wed, 14 Mar 2018 10:54:00 -0700
Subject: [Slackbuilds-users] Jack-rack make failure
In-Reply-To: <d1359bd3-7fe4-923b-b5ab-f743bb5ef811@telus.net>
References: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
 <d1359bd3-7fe4-923b-b5ab-f743bb5ef811@telus.net>
Message-ID: <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>



On 03/13/2018 02:54 PM, B Watson wrote:
> On 3/13/18, x80 <x80 at telus.net> wrote:
>> Yes it's jack2.
>> The Libs line in jack.pc looks like this:
>>
>> Libs: -L/usr/lib64 -ljack
>>
>> Seems it wasn't compiled with pthreads. I wonder if it's not a corrupt lib?
> Eh, it probably isn't "corrupt", it's probably just that jack-rack
> expects the .pc file for the jack library to always include -lpthread,
> so doesn't include -lpthread explicitly.
>
> You can use ldd on the jack library to find out whether or not it was
> compiled with pthreads (I suspect it was), but whether or not jack2 was
> built with pthreads, jack-rack has to be.
ldd /usr/bin/jackd returns that it was built against libpthread.
> In jack-rack.SlackBuild, the configure command reads:
>
> LDFLAGS="-lm -ldl" \
> CFLAGS="$SLKCFLAGS" \
> CXXFLAGS="$SLKCFLAGS" \
> ./configure \
>    --prefix=/usr \
>    --libdir=/usr/lib${LIBDIRSUFFIX} \
>    --sysconfdir=/etc \
>    --localstatedir=/var \
>    --mandir=/usr/man \
>    $LASH_OPT \
>    --disable-gnome \
>    --build=$ARCH-slackware-linux
>
> Change the first line of that to read:
>
> LDFLAGS="-lm -ldl -lpthread" \
>
> ...don't forget the trailing backslash!
I'll do a reinstall with the above changes later today.
>
> Let me know whether or not that fixes the problem... and even if it
> fixes this specific issue, there may be others.
>
> If that fixes it, I'll probably just patch jack2's .pc file to include
> -lpthread, since I suspect lots of other jack apps will have the same
> problem when built with jack2.
>
> Basically, jack2 on SBo is almost completely untested. Someone
> submitted it a few years back and never updated it, and none of the
> READMEs for any of the JACK-related stuff mentions it. They all list
> jack-audio-connection-kit (AKA jack1) as a dependency in their .info
> files, so that's what people end up using.
Jack2 is the optional dependency for qjackctl. Maybe I'll remove jack2 
and reinstall jack1.
I see alsa is routed to pulseaudio in /etc/asound.conf. That scares me. 
I was content with only alsa.
>
> You're the first user I've met who has even tried jack2, so I'm very
> interested to know what you've done with it. What SBo JACK stuff have
> you installed, and how well do they work, that sort of thing.
I use ffmpeg, mplayer/mencoder for video and audio repair and 
conversion. Also Blender. The idea with jack was to enable midi and a 
sequencer so I could do my own soundtracks and effects on home produced 
short films.

So, Version modified SBo's for required libs and includes, manual builds 
for the software I use.

The Jack stuff I've built with SBo's include jack-keyboard, qjackctl 
built against qt5 (mfw HUGE!) and alsa-plugin-jack.

I do have an unrelated day job, but I could be made available for some 
SBo testing if you need it.


From ozan.turkyilmaz at gmail.com  Wed Mar 14 19:01:10 2018
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Thu, 15 Mar 2018 00:01:10 +0500
Subject: [Slackbuilds-users] Retroshare do not work Slackware.
In-Reply-To: <135d24bb-91e8-bf8f-cc71-8bc0cf0d44c2@iinet.net.au>
References: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
 <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
 <CA+da1orA8+L=hbHpPU5obMb=Brdy9g1VAAyBpRCTWNdX2NKPLw@mail.gmail.com>
 <CAPsDuS4SKL2z7vzk1cRgZhaRAFy+p3uD6bwLt9SKLr_-9PpAAw@mail.gmail.com>
 <CA+da1ooGngV8oLkxqGSWMX4B3WAC-kov7qQS-ceF3sUeMsTQvA@mail.gmail.com>
 <135d24bb-91e8-bf8f-cc71-8bc0cf0d44c2@iinet.net.au>
Message-ID: <CA+da1opzLQpCkq4j5WdTTe1JgdRseQkhSj9rq0H8Uobz08PFqQ@mail.gmail.com>

2018-03-13 16:15 GMT+05:00 Christoph Willing <chris.willing at iinet.net.au>:

> Yes, that patch is just a partial fix.
>
> The API for libupnp has changed in the new 1.8.x versions (SBo has
> libupnp-1.8.3 at the moment). Retroshare devs will need to update their
> code to utilize the new libupnp API.
>
> Without any indication of how long that might take, maybe we need a
> libupnp-legacy SlackBuild with version capped at the latest in the 1.6.x
> series so that retroshare can continue to be built. Otherwise we sit
> tight with a SlackBuild that won't build until upstream updates their code.
>
>
>
I have started working on a legacy packge right now.



-- 
Ozan, BSc, BEng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180315/c0b43b57/attachment-0001.html>

From dave at dawoodfall.net  Wed Mar 14 19:07:24 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Wed, 14 Mar 2018 19:07:24 +0000
Subject: [Slackbuilds-users] Searchmonkey
Message-ID: <20180314190724.GA9676@blackswan>

Greetings

I'm passing on maintainership of Searchmonkey to Adam Cottrell
<adam at embeddediq.com>

I haven't used it for years.

Dave

From dave at dawoodfall.net  Wed Mar 14 19:08:52 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Wed, 14 Mar 2018 19:08:52 +0000
Subject: [Slackbuilds-users] Jack-rack make failure
In-Reply-To: <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>
References: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
 <d1359bd3-7fe4-923b-b5ab-f743bb5ef811@telus.net>
 <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>
Message-ID: <20180314190852.GB9676@blackswan>

On (14/03/18 10:54), x80 <x80 at telus.net> put forth the proposition:
>
>
>On 03/13/2018 02:54 PM, B Watson wrote:
>>On 3/13/18, x80 <x80 at telus.net> wrote:
>>>Yes it's jack2.
>>>The Libs line in jack.pc looks like this:
>>>
>>>Libs: -L/usr/lib64 -ljack
>>>
>>>Seems it wasn't compiled with pthreads. I wonder if it's not a corrupt lib?
>>Eh, it probably isn't "corrupt", it's probably just that jack-rack
>>expects the .pc file for the jack library to always include -lpthread,
>>so doesn't include -lpthread explicitly.
>>
>>You can use ldd on the jack library to find out whether or not it was
>>compiled with pthreads (I suspect it was), but whether or not jack2 was
>>built with pthreads, jack-rack has to be.
>ldd /usr/bin/jackd returns that it was built against libpthread.
>>In jack-rack.SlackBuild, the configure command reads:
>>
>>LDFLAGS="-lm -ldl" \
>>CFLAGS="$SLKCFLAGS" \
>>CXXFLAGS="$SLKCFLAGS" \
>>./configure \
>>   --prefix=/usr \
>>   --libdir=/usr/lib${LIBDIRSUFFIX} \
>>   --sysconfdir=/etc \
>>   --localstatedir=/var \
>>   --mandir=/usr/man \
>>   $LASH_OPT \
>>   --disable-gnome \
>>   --build=$ARCH-slackware-linux
>>
>>Change the first line of that to read:
>>
>>LDFLAGS="-lm -ldl -lpthread" \
>>
>>...don't forget the trailing backslash!
>I'll do a reinstall with the above changes later today.
>>
>>Let me know whether or not that fixes the problem... and even if it
>>fixes this specific issue, there may be others.
>>
>>If that fixes it, I'll probably just patch jack2's .pc file to include
>>-lpthread, since I suspect lots of other jack apps will have the same
>>problem when built with jack2.
>>
>>Basically, jack2 on SBo is almost completely untested. Someone
>>submitted it a few years back and never updated it, and none of the
>>READMEs for any of the JACK-related stuff mentions it. They all list
>>jack-audio-connection-kit (AKA jack1) as a dependency in their .info
>>files, so that's what people end up using.
>Jack2 is the optional dependency for qjackctl. Maybe I'll remove jack2
>and reinstall jack1.
>I see alsa is routed to pulseaudio in /etc/asound.conf. That scares
>me. I was content with only alsa.
>>
>>You're the first user I've met who has even tried jack2, so I'm very
>>interested to know what you've done with it. What SBo JACK stuff have
>>you installed, and how well do they work, that sort of thing.
>I use ffmpeg, mplayer/mencoder for video and audio repair and
>conversion. Also Blender. The idea with jack was to enable midi and a
>sequencer so I could do my own soundtracks and effects on home
>produced short films.
>
>So, Version modified SBo's for required libs and includes, manual
>builds for the software I use.
>
>The Jack stuff I've built with SBo's include jack-keyboard, qjackctl
>built against qt5 (mfw HUGE!) and alsa-plugin-jack.
>
>I do have an unrelated day job, but I could be made available for some
>SBo testing if you need it.

I've been using jack2 for years with no problems. All our stuff at
studioware.org uses it, including jack-rack.

We use CFLAGS="-lm -ldl -lpthread $SLKCFLAGS" in jack-rack.

http://www.studioware.org/slackbuilds/14.2/audio/effects/jack-rack/

Regards

Dave

From matteo.bernardini at gmail.com  Wed Mar 14 19:51:34 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 14 Mar 2018 20:51:34 +0100
Subject: [Slackbuilds-users] OpenCV SlackBuild bug - Was: ffmpeg does
 not compile with opencv 3.4.1
In-Reply-To: <20180314144132.f8b8923856e25885e16710c5@ythogtha.org>
References: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>
 <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>
 <20180313165337.14c09e6487301df19cd8aa58@clansco.org>
 <20180313171918.609c514261ec4d84d4186103@clansco.org>
 <20180314144132.f8b8923856e25885e16710c5@ythogtha.org>
Message-ID: <CAPsDuS5eS=9o-n8vA=xo1CiK2-imOr+ABJyG9dY=GAExv_WnrQ@mail.gmail.com>

2018-03-14 14:41 GMT+01:00 Ythogtha <yth at ythogtha.org>:
>         Anyway, I found the problem.
> It's with the opencv.SlackBuild, or more precisely with opencv itself because
> the SlackBuild didn't change and was working fine before.
> OpenCV libraries are installed in /usr/lib6464/ !
> In the opencv.SlackBuild there is a LIBDIRSUFFIX="64" configured when ARCH=x86_64
> and it seems the opencv make process now does that step itself, installing
> itself into /usr/lib64, so adding the LIBDIRSUFFIX="64" moves the .so files
> into /usr/lib6464/
>
>         So setting LIBDIRSUFFIX="" looks like a good idea.
> Except then there are python libraries installed in /usr/lib/ !
> usr/lib/python2.7/site-packages/cv2.so
> usr/lib/python3.6/site-packages/cv2.cpython-36m-x86_64-linux-gnu.so
> And import cv2 doesn't work in either python or python3.
>
>         I tried moving usr/lib/python* into usr/lib64/ just before makepkg in the
> SlackBuild, and everything seems to work fine, I can import cv2 in python and
> python3. The hack is ugly and there should be a cleaner way to handle that.

IMHO the best solution for that is to modify a little more the patch
used by the SlackBuild: I attach the new version

Matteo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch_fsh-3.4.1.diff
Type: text/x-patch
Size: 1930 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180314/2cd4a1f3/attachment.bin>

From x80 at telus.net  Wed Mar 14 21:25:39 2018
From: x80 at telus.net (x80)
Date: Wed, 14 Mar 2018 14:25:39 -0700
Subject: [Slackbuilds-users] Jack-rack make failure
In-Reply-To: <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>
References: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
 <d1359bd3-7fe4-923b-b5ab-f743bb5ef811@telus.net>
 <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>
Message-ID: <45127c73-306f-f55b-3c2e-3b8a1125fb0e@telus.net>



On 03/14/2018 12:08 PM, David Woodfall wrote:
> On (14/03/18 10:54), x80 <x80 at telus.net> put forth the proposition:
>>
>>
>> On 03/13/2018 02:54 PM, B Watson wrote:
>>> On 3/13/18, x80 <x80 at telus.net> wrote:
>>>> Yes it's jack2.
>>>> The Libs line in jack.pc looks like this:
>>>>
>>>> Libs: -L/usr/lib64 -ljack
>>>>
>>>> Seems it wasn't compiled with pthreads. I wonder if it's not a 
>>>> corrupt lib?
>>> Eh, it probably isn't "corrupt", it's probably just that jack-rack
>>> expects the .pc file for the jack library to always include -lpthread,
>>> so doesn't include -lpthread explicitly.
>>>
>>> You can use ldd on the jack library to find out whether or not it was
>>> compiled with pthreads (I suspect it was), but whether or not jack2 was
>>> built with pthreads, jack-rack has to be.
>> ldd /usr/bin/jackd returns that it was built against libpthread.
>>> In jack-rack.SlackBuild, the configure command reads:
>>>
>>> LDFLAGS="-lm -ldl" \
>>> CFLAGS="$SLKCFLAGS" \
>>> CXXFLAGS="$SLKCFLAGS" \
>>> ./configure \
>>>   --prefix=/usr \
>>>   --libdir=/usr/lib${LIBDIRSUFFIX} \
>>>   --sysconfdir=/etc \
>>>   --localstatedir=/var \
>>>   --mandir=/usr/man \
>>>   $LASH_OPT \
>>>   --disable-gnome \
>>>   --build=$ARCH-slackware-linux
>>>
>>> Change the first line of that to read:
>>>
>>> LDFLAGS="-lm -ldl -lpthread" \
>>>
>>> ...don't forget the trailing backslash!
>> I'll do a reinstall with the above changes later today.
>>>
>>> Let me know whether or not that fixes the problem... and even if it
>>> fixes this specific issue, there may be others.
>>>
>>> If that fixes it, I'll probably just patch jack2's .pc file to include
>>> -lpthread, since I suspect lots of other jack apps will have the same
>>> problem when built with jack2.
>>>
>>> Basically, jack2 on SBo is almost completely untested. Someone
>>> submitted it a few years back and never updated it, and none of the
>>> READMEs for any of the JACK-related stuff mentions it. They all list
>>> jack-audio-connection-kit (AKA jack1) as a dependency in their .info
>>> files, so that's what people end up using.
>> Jack2 is the optional dependency for qjackctl. Maybe I'll remove jack2
>> and reinstall jack1.
>> I see alsa is routed to pulseaudio in /etc/asound.conf. That scares
>> me. I was content with only alsa.
>>>
>>> You're the first user I've met who has even tried jack2, so I'm very
>>> interested to know what you've done with it. What SBo JACK stuff have
>>> you installed, and how well do they work, that sort of thing.
>> I use ffmpeg, mplayer/mencoder for video and audio repair and
>> conversion. Also Blender. The idea with jack was to enable midi and a
>> sequencer so I could do my own soundtracks and effects on home
>> produced short films.
>>
>> So, Version modified SBo's for required libs and includes, manual
>> builds for the software I use.
>>
>> The Jack stuff I've built with SBo's include jack-keyboard, qjackctl
>> built against qt5 (mfw HUGE!) and alsa-plugin-jack.
>>
>> I do have an unrelated day job, but I could be made available for some
>> SBo testing if you need it.
>
> I've been using jack2 for years with no problems. All our stuff at
> studioware.org uses it, including jack-rack.
>
> We use CFLAGS="-lm -ldl -lpthread $SLKCFLAGS" in jack-rack.
>
> http://www.studioware.org/slackbuilds/14.2/audio/effects/jack-rack/
>
> Regards
>
> Dave
>
>
I had no idea this existed. Thank you Dave, I'll try the install script 
for studioware on a fresh install and upgrade.

From yalhcru at gmail.com  Wed Mar 14 22:08:18 2018
From: yalhcru at gmail.com (B Watson)
Date: Wed, 14 Mar 2018 18:08:18 -0400
Subject: [Slackbuilds-users] Jack-rack make failure
In-Reply-To: <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>
References: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
 <d1359bd3-7fe4-923b-b5ab-f743bb5ef811@telus.net>
 <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>
Message-ID: <CAN1hMuAPW3b7mSSjvsoUn74a7kKyFCWMgsVjFLChegBS9aWWLw@mail.gmail.com>

On 3/14/18, x80 <x80 at telus.net> wrote:

> Jack2 is the optional dependency for qjackctl. Maybe I'll remove jack2
> and reinstall jack1.

In theory, at least, you should be able to install jack1, compile stuff
against it, then replace jack1 with jack2 without recompiling anything
else. It's supposed to be an API-compatible drop-in replacement. Not
sure how well this works in practice though.

> I see alsa is routed to pulseaudio in /etc/asound.conf. That scares me.
> I was content with only alsa.

If you configure jackd to use the hardware (device names beginning with
hw:), it won't get routed to pulse. However jackd will refuse to start
if pulse is already using the device...

My solution to the pulseaudio thing is to log in as root and:

mv /etc/asound.conf /etc/asound.conf.orig
chmod -x /usr/bin/pulseaudio
killall pulseaudio

...and kill/restart any already-running applications that might be
using pulse (which would include KDE, if you run that). This will get
you 14.1-like behaviour. However I'm not sure whether the latest firefox
versions will be able to make sound without pulseaudio (I'm running an
old 'insecure' version, with javascript disabled on 99.9% of the web,
and no flash plugin installed, and it works fine).

Anyway you can restore the default 14.2 behaviour:

mv /etc/asound.conf.orig /etc/asound.conf
chmod a+x /usr/bin/pulseaudio

...I highly recommend *not* running anything else when you're using jack,
anyway. Even better would be to use a dedicated machine for jack stuff
and nothing else (where you can leave pulse disabled always).

I've considered adding this info to the jack-audio-connection-kit README,
but I suspect I'd encounter resistance from the "use a clean Slackware
install" crowd...

From dave at dawoodfall.net  Wed Mar 14 22:30:55 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Wed, 14 Mar 2018 22:30:55 +0000
Subject: [Slackbuilds-users] Searchmonkey
In-Reply-To: <20180314190724.GA9676@blackswan>
References: <20180314190724.GA9676@blackswan>
Message-ID: <20180314223055.GE9676@blackswan>

On (14/03/18 19:07), Dave Woodfall <dave at dawoodfall.net> put forth the proposition:
>Greetings
>
>I'm passing on maintainership of Searchmonkey to Adam Cottrell
><adam at embeddediq.com>
>
>I haven't used it for years.
>
>Dave

Well, it looks like he's not going to take it on now. If anyone is
interested then it's up for grabs.

Dave

From mickski56 at hotmail.com  Wed Mar 14 23:41:06 2018
From: mickski56 at hotmail.com (mickski 56)
Date: Wed, 14 Mar 2018 23:41:06 +0000
Subject: [Slackbuilds-users] Jack-rack make failure
In-Reply-To: <CAN1hMuAPW3b7mSSjvsoUn74a7kKyFCWMgsVjFLChegBS9aWWLw@mail.gmail.com>
References: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
 <d1359bd3-7fe4-923b-b5ab-f743bb5ef811@telus.net>
 <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>
 <CAN1hMuAPW3b7mSSjvsoUn74a7kKyFCWMgsVjFLChegBS9aWWLw@mail.gmail.com>
Message-ID: <AM4PR07MB307460DD6F2F45F335B9EBA0B1D10@AM4PR07MB3074.eurprd07.prod.outlook.com>

>On 3/14/18, x80 <x80 at telus.net> wrote:
>
>> Jack2 is the optional dependency for qjackctl. Maybe I'll remove
>> jack2 and reinstall jack1.  
>
>In theory, at least, you should be able to install jack1, compile stuff
>against it, then replace jack1 with jack2 without recompiling anything
>else. It's supposed to be an API-compatible drop-in replacement. Not
>sure how well this works in practice though.
>
>> I see alsa is routed to pulseaudio in /etc/asound.conf. That scares
>> me. I was content with only alsa.  
>
>If you configure jackd to use the hardware (device names beginning with
>hw:), it won't get routed to pulse. However jackd will refuse to start
>if pulse is already using the device...
>
>My solution to the pulseaudio thing is to log in as root and:
>
>mv /etc/asound.conf /etc/asound.conf.orig
>chmod -x /usr/bin/pulseaudio
>killall pulseaudio
>
>...and kill/restart any already-running applications that might be
>using pulse (which would include KDE, if you run that). This will get
>you 14.1-like behaviour. However I'm not sure whether the latest
>firefox versions will be able to make sound without pulseaudio (I'm
>running an old 'insecure' version, with javascript disabled on 99.9%
>of the web, and no flash plugin installed, and it works fine).
>
>Anyway you can restore the default 14.2 behaviour:
>
>mv /etc/asound.conf.orig /etc/asound.conf
>chmod a+x /usr/bin/pulseaudio
>
>...I highly recommend *not* running anything else when you're using
>jack, anyway. Even better would be to use a dedicated machine for jack
>stuff and nothing else (where you can leave pulse disabled always).
>
>I've considered adding this info to the jack-audio-connection-kit
>README, but I suspect I'd encounter resistance from the "use a clean
>Slackware install" crowd...

On board sound + higher quality pci card that pulse knows nothing about
works well for me. Although it does involve more wires and a swich box
or mixer.

From x80 at telus.net  Wed Mar 14 23:58:22 2018
From: x80 at telus.net (x80)
Date: Wed, 14 Mar 2018 16:58:22 -0700
Subject: [Slackbuilds-users] Jack-rack make failure
In-Reply-To: <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>
References: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
 <d1359bd3-7fe4-923b-b5ab-f743bb5ef811@telus.net>
 <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>
Message-ID: <e099acdc-8b50-d849-4bf2-1f680f23fa35@telus.net>



On 03/14/2018 03:08 PM, B Watson wrote:
> On 3/14/18, x80 <x80 at telus.net> wrote:
>
>> Jack2 is the optional dependency for qjackctl. Maybe I'll remove jack2
>> and reinstall jack1.
> In theory, at least, you should be able to install jack1, compile stuff
> against it, then replace jack1 with jack2 without recompiling anything
> else. It's supposed to be an API-compatible drop-in replacement. Not
> sure how well this works in practice though.
>
>> I see alsa is routed to pulseaudio in /etc/asound.conf. That scares me.
>> I was content with only alsa.
> If you configure jackd to use the hardware (device names beginning with
> hw:), it won't get routed to pulse. However jackd will refuse to start
> if pulse is already using the device...
>
> My solution to the pulseaudio thing is to log in as root and:
>
> mv /etc/asound.conf /etc/asound.conf.orig
> chmod -x /usr/bin/pulseaudio
> killall pulseaudio
Heh, I had to take a breath at chmod -x, it almost came out rm -f when I 
did it. Systemd, D-bus, and pulseaudio keep my pharmacist providing me 
with blood pressure meds.
>
> ...and kill/restart any already-running applications that might be
> using pulse (which would include KDE, if you run that). This will get
> you 14.1-like behaviour. However I'm not sure whether the latest firefox
> versions will be able to make sound without pulseaudio (I'm running an
> old 'insecure' version, with javascript disabled on 99.9% of the web,
> and no flash plugin installed, and it works fine).
>
> Anyway you can restore the default 14.2 behaviour:
>
> mv /etc/asound.conf.orig /etc/asound.conf
> chmod a+x /usr/bin/pulseaudio
>
> ...I highly recommend *not* running anything else when you're using jack,
> anyway. Even better would be to use a dedicated machine for jack stuff
> and nothing else (where you can leave pulse disabled always).
>
> I've considered adding this info to the jack-audio-connection-kit README,
> but I suspect I'd encounter resistance from the "use a clean Slackware
> install" crowd...
This machine is stand alone. Not even any network, just a printer, 
scanner, burner, and turtle beach sound card. I thought it would be a 
fitting retirement for a 13 year old Tyan board.

I'll run a network cable and try the install script for studioware. Once 
I figure out what software I want to use, then I'll retry the SBo scripts.

Thanks for tips anyway.

Phil


From chris.willing at linux.com  Thu Mar 15 06:15:58 2018
From: chris.willing at linux.com (Christoph Willing)
Date: Thu, 15 Mar 2018 16:15:58 +1000
Subject: [Slackbuilds-users] OpenCV SlackBuild bug - Was: ffmpeg does
 not compile with opencv 3.4.1
In-Reply-To: <CAPsDuS5eS=9o-n8vA=xo1CiK2-imOr+ABJyG9dY=GAExv_WnrQ@mail.gmail.com>
References: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>
 <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>
 <20180313165337.14c09e6487301df19cd8aa58@clansco.org>
 <20180313171918.609c514261ec4d84d4186103@clansco.org>
 <20180314144132.f8b8923856e25885e16710c5@ythogtha.org>
 <CAPsDuS5eS=9o-n8vA=xo1CiK2-imOr+ABJyG9dY=GAExv_WnrQ@mail.gmail.com>
Message-ID: <686b19d1-7d98-73a0-5b39-36e43e2a786c@linux.com>

On 15/03/18 05:51, Matteo Bernardini wrote:
> 2018-03-14 14:41 GMT+01:00 Ythogtha <yth at ythogtha.org>:
>>         Anyway, I found the problem.
>> It's with the opencv.SlackBuild, or more precisely with opencv itself because
>> the SlackBuild didn't change and was working fine before.
>> OpenCV libraries are installed in /usr/lib6464/ !
>> In the opencv.SlackBuild there is a LIBDIRSUFFIX="64" configured when ARCH=x86_64
>> and it seems the opencv make process now does that step itself, installing
>> itself into /usr/lib64, so adding the LIBDIRSUFFIX="64" moves the .so files
>> into /usr/lib6464/
>>
>>         So setting LIBDIRSUFFIX="" looks like a good idea.
>> Except then there are python libraries installed in /usr/lib/ !
>> usr/lib/python2.7/site-packages/cv2.so
>> usr/lib/python3.6/site-packages/cv2.cpython-36m-x86_64-linux-gnu.so
>> And import cv2 doesn't work in either python or python3.
>>
>>         I tried moving usr/lib/python* into usr/lib64/ just before makepkg in the
>> SlackBuild, and everything seems to work fine, I can import cv2 in python and
>> python3. The hack is ugly and there should be a cleaner way to handle that.
> 
> IMHO the best solution for that is to modify a little more the patch
> used by the SlackBuild: I attach the new version
> 

Thanks all for spotting the problem. I've just pushed a fix for it.

While working through this myself, I noticed that the requirement for
python3 to generate a python3 binding no longer works unless numpy3 is
also installed at build time. Since numpy3 requires python3, I've
replaced the requirement for python3 with numpy3.

Back to the original problem of building ffmpeg with opencv support, I
haven't been able to compile that successfully. The configure phase
finds opencv OK but compilation fails with:

In file included from /usr/include/opencv2/core/types_c.h:59:0,
                 from /usr/include/opencv2/core/core_c.h:48,
                 from libavfilter/vf_libopencv.c:28:
/usr/include/opencv2/core/cvdef.h:485:1: error: unknown type name
'namespace'
 namespace cv {
 ^
/usr/include/opencv2/core/cvdef.h:485:14: error: expected '=', ',', ';',
'asm' or '__attribute__' before '{' token
 namespace cv {
              ^
common.mak:60: recipe for target 'libavfilter/vf_libopencv.o' failed
make: *** [libavfilter/vf_libopencv.o] Error 1


It's not something I want to spend a lot of time trying to fix - for my
own use I have the dependency the other way around by building opencv
with ffmpeg support. However if anyone can propose a fix, I'm happy (and
grateful) to include it in the SlackBuild.

chris

From dave at unrealize.co.uk  Wed Mar 14 18:07:43 2018
From: dave at unrealize.co.uk (Dave)
Date: Wed, 14 Mar 2018 18:07:43 +0000
Subject: [Slackbuilds-users] Jack-rack make failure
In-Reply-To: <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>
References: <3a1c1bfd-7789-cc71-74fa-3cca38ae45c9@telus.net>
 <d1359bd3-7fe4-923b-b5ab-f743bb5ef811@telus.net>
 <7818bdcd-ddf9-4922-24c0-b97fbec20d15@telus.net>
Message-ID: <20180314180743.GA4267@blackswan>

On (14/03/18 10:54), x80 <x80 at telus.net> put forth the proposition:
>
>
>On 03/13/2018 02:54 PM, B Watson wrote:
>>On 3/13/18, x80 <x80 at telus.net> wrote:
>>>Yes it's jack2.
>>>The Libs line in jack.pc looks like this:
>>>
>>>Libs: -L/usr/lib64 -ljack
>>>
>>>Seems it wasn't compiled with pthreads. I wonder if it's not a corrupt lib?
>>Eh, it probably isn't "corrupt", it's probably just that jack-rack
>>expects the .pc file for the jack library to always include -lpthread,
>>so doesn't include -lpthread explicitly.
>>
>>You can use ldd on the jack library to find out whether or not it was
>>compiled with pthreads (I suspect it was), but whether or not jack2 was
>>built with pthreads, jack-rack has to be.
>ldd /usr/bin/jackd returns that it was built against libpthread.
>>In jack-rack.SlackBuild, the configure command reads:
>>
>>LDFLAGS="-lm -ldl" \
>>CFLAGS="$SLKCFLAGS" \
>>CXXFLAGS="$SLKCFLAGS" \
>>./configure \
>>   --prefix=/usr \
>>   --libdir=/usr/lib${LIBDIRSUFFIX} \
>>   --sysconfdir=/etc \
>>   --localstatedir=/var \
>>   --mandir=/usr/man \
>>   $LASH_OPT \
>>   --disable-gnome \
>>   --build=$ARCH-slackware-linux
>>
>>Change the first line of that to read:
>>
>>LDFLAGS="-lm -ldl -lpthread" \
>>
>>...don't forget the trailing backslash!
>I'll do a reinstall with the above changes later today.
>>
>>Let me know whether or not that fixes the problem... and even if it
>>fixes this specific issue, there may be others.
>>
>>If that fixes it, I'll probably just patch jack2's .pc file to include
>>-lpthread, since I suspect lots of other jack apps will have the same
>>problem when built with jack2.
>>
>>Basically, jack2 on SBo is almost completely untested. Someone
>>submitted it a few years back and never updated it, and none of the
>>READMEs for any of the JACK-related stuff mentions it. They all list
>>jack-audio-connection-kit (AKA jack1) as a dependency in their .info
>>files, so that's what people end up using.
>Jack2 is the optional dependency for qjackctl. Maybe I'll remove jack2 
>and reinstall jack1.
>I see alsa is routed to pulseaudio in /etc/asound.conf. That scares 
>me. I was content with only alsa.
>>
>>You're the first user I've met who has even tried jack2, so I'm very
>>interested to know what you've done with it. What SBo JACK stuff have
>>you installed, and how well do they work, that sort of thing.
>I use ffmpeg, mplayer/mencoder for video and audio repair and 
>conversion. Also Blender. The idea with jack was to enable midi and a 
>sequencer so I could do my own soundtracks and effects on home 
>produced short films.
>
>So, Version modified SBo's for required libs and includes, manual 
>builds for the software I use.
>
>The Jack stuff I've built with SBo's include jack-keyboard, qjackctl 
>built against qt5 (mfw HUGE!) and alsa-plugin-jack.
>
>I do have an unrelated day job, but I could be made available for some 
>SBo testing if you need it.

I've been using jack2 for years with no problems. ALl our stuff at
studioware.org uses it, including jack-rack.

We use CFLAGS="-lm -ldl -lpthread $SLKCFLAGS" in jack-rack.

http://www.studioware.org/slackbuilds/14.2/audio/effects/jack-rack/

Regards

Dave

From Jim.Diamond at acadiau.ca  Thu Mar 15 20:46:23 2018
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Thu, 15 Mar 2018 17:46:23 -0300
Subject: [Slackbuilds-users] libwacom-0.29.tar.bz2 md5sum failure
Message-ID: <20180315204623.GA25316@jdiamond-mb.acadiau.ca>

Hi all,

# sboupgrade libwacom

libwacom (Library to identify Wacom tablets and their features)

Manages the libraries, configuration, and diagnostic tools for Wacom
tablets running under Linux. It also maintains updated  Linux  kernel
drivers and Xorg/XFree86 XInput drivers.

Proceed with libwacom? [y]  
libwacom added to upgrade queue.

Upgrade queue: libwacom

Are you sure you wish to continue? [y] 
--2018-03-15 17:45:20--  https://sourceforge.net/projects/linuxwacom/files/libwacom/libwacom-0.29.tar.bz2
Resolving sourceforge.net... 216.105.38.13
Connecting to sourceforge.net|216.105.38.13|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://sourceforge.net/projects/linuxwacom/files/libwacom/libwacom-0.29.tar.bz2/download [following]
--2018-03-15 17:45:20--  https://sourceforge.net/projects/linuxwacom/files/libwacom/libwacom-0.29.tar.bz2/download
Connecting to sourceforge.net|216.105.38.13|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 457344 (447K) [text/html]
Saving to: ?libwacom-0.29.tar.bz2?

libwacom-0.29.tar.bz 100%[===================>] 446.62K  1.08MB/s    in 0.4s    

2018-03-15 17:45:21 (1.08 MB/s) - ?libwacom-0.29.tar.bz2? saved [457344/457344]

--2018-03-15 17:45:21--  ftp://slackware.uk/sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681/libwacom-0.29.tar.bz2
           => ?libwacom-0.29.tar.bz2?
Resolving slackware.uk... 91.109.244.240
Connecting to slackware.uk|91.109.244.240|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681 ... 
No such directory ?sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681?.

Unable to download/verify source file(s) for libwacom:
  md5sum failure for /usr/local/poo/usr-sbo-142/distfiles/libwacom-0.29.tar.bz2.


From willysr at slackbuilds.org  Thu Mar 15 21:07:01 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 16 Mar 2018 04:07:01 +0700
Subject: [Slackbuilds-users] libwacom-0.29.tar.bz2 md5sum failure
In-Reply-To: <20180315204623.GA25316@jdiamond-mb.acadiau.ca>
References: <20180315204623.GA25316@jdiamond-mb.acadiau.ca>
Message-ID: <b4abc459-d632-6506-2601-53a8fe678749@slackbuilds.org>

> Are you sure you wish to continue? [y] 
> --2018-03-15 17:45:20--  https://sourceforge.net/projects/linuxwacom/files/libwacom/libwacom-0.29.tar.bz2
> Resolving sourceforge.net... 216.105.38.13
> Connecting to sourceforge.net|216.105.38.13|:443... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: https://sourceforge.net/projects/linuxwacom/files/libwacom/libwacom-0.29.tar.bz2/download [following]
> --2018-03-15 17:45:20--  https://sourceforge.net/projects/linuxwacom/files/libwacom/libwacom-0.29.tar.bz2/download
> Connecting to sourceforge.net|216.105.38.13|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 457344 (447K) [text/html]
> Saving to: ?libwacom-0.29.tar.bz2?
> 
> libwacom-0.29.tar.bz 100%[===================>] 446.62K  1.08MB/s    in 0.4s    
> 
> 2018-03-15 17:45:21 (1.08 MB/s) - ?libwacom-0.29.tar.bz2? saved [457344/457344]
> 
> --2018-03-15 17:45:21--  ftp://slackware.uk/sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681/libwacom-0.29.tar.bz2
>            => ?libwacom-0.29.tar.bz2?
> Resolving slackware.uk... 91.109.244.240
> Connecting to slackware.uk|91.109.244.240|:21... connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done.    ==> PWD ... done.
> ==> TYPE I ... done.  ==> CWD (1) /sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681 ... 
> No such directory ?sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681?.
> 
> Unable to download/verify source file(s) for libwacom:
>   md5sum failure for /usr/local/poo/usr-sbo-142/distfiles/libwacom-0.29.tar.bz2.

libwacom works fine here

Connecting to excellmedia.dl.sourceforge.net
(excellmedia.dl.sourceforge.net)|202.153.32.19|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 495549 (484K) [application/octet-stream]
Saving to: ?libwacom-0.29.tar.bz2?

libwacom-0.29.tar.b 100%[===================>] 483.93K   567KB/s    in
0.9s

2018-03-16 04:04:10 (567 KB/s) - ?libwacom-0.29.tar.bz2? saved
[495549/495549]

Found libwacom-0.29.tar.bz2 in /data/source.
Checking MD5SUM:
  MD5SUM check for libwacom-0.29.tar.bz2 ... OK


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180316/aab298fd/attachment-0001.asc>

From Jim.Diamond at acadiau.ca  Thu Mar 15 21:40:00 2018
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Thu, 15 Mar 2018 18:40:00 -0300
Subject: [Slackbuilds-users] libwacom-0.29.tar.bz2 md5sum failure
In-Reply-To: <b4abc459-d632-6506-2601-53a8fe678749@slackbuilds.org>
References: <20180315204623.GA25316@jdiamond-mb.acadiau.ca>
 <b4abc459-d632-6506-2601-53a8fe678749@slackbuilds.org>
Message-ID: <20180315214000.GA27589@jdiamond-mb.acadiau.ca>

On Fri, Mar 16, 2018 at 04:07 (+0700), Willy Sudiarto Raharjo wrote:

>> Are you sure you wish to continue? [y] 
>> --2018-03-15 17:45:20--  https://sourceforge.net/projects/linuxwacom/files/libwacom/libwacom-0.29.tar.bz2
>> Resolving sourceforge.net... 216.105.38.13

<snip>

>> --2018-03-15 17:45:21--  ftp://slackware.uk/sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681/libwacom-0.29.tar.bz2
>>            => ?libwacom-0.29.tar.bz2?
>> Resolving slackware.uk... 91.109.244.240
>> Connecting to slackware.uk|91.109.244.240|:21... connected.
>> Logging in as anonymous ... Logged in!
>> ==> SYST ... done.    ==> PWD ... done.
>> ==> TYPE I ... done.  ==> CWD (1) /sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681 ... 
>> No such directory ?sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681?.

>> Unable to download/verify source file(s) for libwacom:
>> md5sum failure for /usr/local/poo/usr-sbo-142/distfiles/libwacom-0.29.tar.bz2.

> libwacom works fine here

> Connecting to excellmedia.dl.sourceforge.net
> (excellmedia.dl.sourceforge.net)|202.153.32.19|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 495549 (484K) [application/octet-stream]
> Saving to: ?libwacom-0.29.tar.bz2?

> libwacom-0.29.tar.b 100%[===================>] 483.93K   567KB/s    in
> 0.9s

> 2018-03-16 04:04:10 (567 KB/s) - ?libwacom-0.29.tar.bz2? saved
> [495549/495549]

> Found libwacom-0.29.tar.bz2 in /data/source.
> Checking MD5SUM:
> MD5SUM check for libwacom-0.29.tar.bz2 ... OK

Hmmm... you went to sourceforge.  sboupgrade sent me to
    ftp://slackware.uk/sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681
which, indeed, does not currently exist.

Just out of curiosity, did you use sboupgrade or some other tool?

Thanks.

                                Jim

From willysr at slackbuilds.org  Thu Mar 15 21:45:02 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 16 Mar 2018 04:45:02 +0700
Subject: [Slackbuilds-users] libwacom-0.29.tar.bz2 md5sum failure
In-Reply-To: <20180315214000.GA27589@jdiamond-mb.acadiau.ca>
References: <20180315204623.GA25316@jdiamond-mb.acadiau.ca>
 <b4abc459-d632-6506-2601-53a8fe678749@slackbuilds.org>
 <20180315214000.GA27589@jdiamond-mb.acadiau.ca>
Message-ID: <191bf2f4-8e63-f4c9-b720-3b26ee5877e2@slackbuilds.org>

> Hmmm... you went to sourceforge.  sboupgrade sent me to
>     ftp://slackware.uk/sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681
> which, indeed, does not currently exist.
> 
> Just out of curiosity, did you use sboupgrade or some other tool?

I use sbopkg


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180316/9c664f5c/attachment.asc>

From willysr at slackbuilds.org  Fri Mar 16 00:07:56 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 16 Mar 2018 07:07:56 +0700
Subject: [Slackbuilds-users] webkit2gtk 2.20 for review
Message-ID: <f9ae0025-b43a-b581-72b8-96a8a483d98b@slackbuilds.org>

Hi all

i have pushed a new branch, webkit2gtk-review in git for a public
review. This is a major release and came up with a new dependencies,
woff2, and geoclue2. Woff2 itself requires brotli, another new package
All the new deps (woff2 and brotli) are already in David's branch for
this week's public update, except for geoclue2 which is already on our
repository.

These are the packages that list webkit2gtk as hard dependency:
development/wxHexEditor
graphics/shotwell
network/gui-ufw
network/luakit
network/midori
network/surf
network/vimb
system/yelp

in a quick test, most of them built just fine with the new webkit2gtk,
but i'm not taking a risk of breaking scripts.

So if you used the above packages, please help by testing the new
webkit2gtk before it got merged in master.

Thanks


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180316/bb4302cd/attachment.asc>

From skaendo at excite.com  Fri Mar 16 04:13:57 2018
From: skaendo at excite.com (Ed Ender)
Date: Fri, 16 Mar 2018 00:13:57 -0400
Subject: [Slackbuilds-users] webkit2gtk 2.20 for review
Message-ID: <20180316001357.7823@web001.roc2.bluetie.com>

Hey Willy,

I just tested gui-ufw and yelp against webkit2gtk-2.20.0 and I have no
problems. Everything seems to be working normally. 

Ed

-----Original Message-----
From: "Willy Sudiarto Raharjo" [willysr at slackbuilds.org]
Date: 03/15/2018 07:09 PM
To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
Subject: [Slackbuilds-users] webkit2gtk 2.20 for review

Hi all

i have pushed a new branch, webkit2gtk-review in git for a public
review. This is a major release and came up with a new dependencies,
woff2, and geoclue2. Woff2 itself requires brotli, another new package
All the new deps (woff2 and brotli) are already in David's branch for
this week's public update, except for geoclue2 which is already on our
repository.

These are the packages that list webkit2gtk as hard dependency:
development/wxHexEditor
graphics/shotwell
network/gui-ufw
network/luakit
network/midori
network/surf
network/vimb
system/yelp

in a quick test, most of them built just fine with the new webkit2gtk,
but i'm not taking a risk of breaking scripts.

So if you used the above packages, please help by testing the new
webkit2gtk before it got merged in master.

Thanks


-- 
Willy Sudiarto Raharjo




From kris240376 at gmail.com  Fri Mar 16 12:59:49 2018
From: kris240376 at gmail.com (Christopher Walker)
Date: Fri, 16 Mar 2018 07:59:49 -0500
Subject: [Slackbuilds-users] opencv issue
Message-ID: <CAPiaOgy0fs-dCPx3VHHqpECGf+ecC2ty70hQjMJGynXb2FWx5w@mail.gmail.com>

When compiling opencv on Slackware using the Slackbuilds script and I
noticed that opencv is creating a folder /usr/lib6464.  Has anyone else
noticed this?

I ran across this when I was trying to build ffmpeg against opencv and it
couldn't find the opencv.pc file in the usual location (/usr/lib64).

Thanks,
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180316/b2f9d792/attachment.html>

From yth at ythogtha.org  Fri Mar 16 13:30:56 2018
From: yth at ythogtha.org (Ythogtha)
Date: Fri, 16 Mar 2018 14:30:56 +0100
Subject: [Slackbuilds-users] opencv issue
In-Reply-To: <CAPiaOgy0fs-dCPx3VHHqpECGf+ecC2ty70hQjMJGynXb2FWx5w@mail.gmail.com>
References: <CAPiaOgy0fs-dCPx3VHHqpECGf+ecC2ty70hQjMJGynXb2FWx5w@mail.gmail.com>
Message-ID: <20180316143056.26418ea79ed5247709fe59a7@ythogtha.org>

> When compiling opencv on Slackware using the Slackbuilds script and I
> noticed that opencv is creating a folder /usr/lib6464.  Has anyone else
> noticed this?
> 
> I ran across this when I was trying to build ffmpeg against opencv and it
> couldn't find the opencv.pc file in the usual location (/usr/lib64).
> 
> Thanks,
> Chris

Yeah, well, I just started a whole conversation on that topic three days ago.
There's a patched version of the OpenCV SlackBuild pushed by Christoph Willing.

Still, ffmpeg continues to refuse to build even with the corrected OpenCV.

If you need ffmpeg working with OpenCV now, then unbump it to 3.4.0 instead of
3.4.1, and everything will work fine.

-- 
Arnaud <yth at ythogtha.org>

From yth at ythogtha.org  Fri Mar 16 13:48:05 2018
From: yth at ythogtha.org (Ythogtha)
Date: Fri, 16 Mar 2018 14:48:05 +0100
Subject: [Slackbuilds-users] OpenCV SlackBuild bug - Was: ffmpeg does
 not compile with opencv 3.4.1
In-Reply-To: <686b19d1-7d98-73a0-5b39-36e43e2a786c@linux.com>
References: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>
 <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>
 <20180313165337.14c09e6487301df19cd8aa58@clansco.org>
 <20180313171918.609c514261ec4d84d4186103@clansco.org>
 <20180314144132.f8b8923856e25885e16710c5@ythogtha.org>
 <CAPsDuS5eS=9o-n8vA=xo1CiK2-imOr+ABJyG9dY=GAExv_WnrQ@mail.gmail.com>
 <686b19d1-7d98-73a0-5b39-36e43e2a786c@linux.com>
Message-ID: <20180316144805.e2525c4dd96e69927b13b855@ythogtha.org>

> Thanks all for spotting the problem. I've just pushed a fix for it.
> 
> While working through this myself, I noticed that the requirement for
> python3 to generate a python3 binding no longer works unless numpy3 is
> also installed at build time. Since numpy3 requires python3, I've
> replaced the requirement for python3 with numpy3.
> 
> Back to the original problem of building ffmpeg with opencv support, I
> haven't been able to compile that successfully. The configure phase
> finds opencv OK but compilation fails with:
> 
> In file included from /usr/include/opencv2/core/types_c.h:59:0,
>                  from /usr/include/opencv2/core/core_c.h:48,
>                  from libavfilter/vf_libopencv.c:28:
> /usr/include/opencv2/core/cvdef.h:485:1: error: unknown type name
> 'namespace'
>  namespace cv {
>  ^
> /usr/include/opencv2/core/cvdef.h:485:14: error: expected '=', ',', ';',
> 'asm' or '__attribute__' before '{' token
>  namespace cv {
>               ^
> common.mak:60: recipe for target 'libavfilter/vf_libopencv.o' failed
> make: *** [libavfilter/vf_libopencv.o] Error 1
> 
> 
> It's not something I want to spend a lot of time trying to fix - for my
> own use I have the dependency the other way around by building opencv
> with ffmpeg support. However if anyone can propose a fix, I'm happy (and
> grateful) to include it in the SlackBuild.
> 
> chris

Hi!

	I just went back into this, used your updated build for OpenCV and
failed to compile ffmpeg.
Then I found this :
https://github.com/opencv/opencv/issues/10963
	So I modified the file /usr/include/opencv2/core/cvdef.h according to
what's said there.
And well, it works fine.
ffmpeg compiles and runs perfectly.

	So maybe including a patch to OpenCV since this seems to affect other
softwares, like VLC apparently ?
Your call Chris :)

-- 
Arnaud <yth at ythogtha.org>

From kris240376 at gmail.com  Fri Mar 16 15:49:03 2018
From: kris240376 at gmail.com (Christopher Walker)
Date: Fri, 16 Mar 2018 10:49:03 -0500
Subject: [Slackbuilds-users] opencv issue
In-Reply-To: <20180316143056.26418ea79ed5247709fe59a7@ythogtha.org>
References: <CAPiaOgy0fs-dCPx3VHHqpECGf+ecC2ty70hQjMJGynXb2FWx5w@mail.gmail.com>
 <20180316143056.26418ea79ed5247709fe59a7@ythogtha.org>
Message-ID: <CAPiaOgzow5K9YVokDmyrK_ajjo11PSZSWBEfyF1-OzfvJD4qfg@mail.gmail.com>

On Fri, Mar 16, 2018 at 8:30 AM, Ythogtha <yth at ythogtha.org> wrote:

> > When compiling opencv on Slackware using the Slackbuilds script and I
> > noticed that opencv is creating a folder /usr/lib6464.  Has anyone else
> > noticed this?
> >
> > I ran across this when I was trying to build ffmpeg against opencv and it
> > couldn't find the opencv.pc file in the usual location (/usr/lib64).
> >
> > Thanks,
> > Chris
>
> Yeah, well, I just started a whole conversation on that topic three days
> ago.
> There's a patched version of the OpenCV SlackBuild pushed by Christoph
> Willing.
>
> Still, ffmpeg continues to refuse to build even with the corrected OpenCV.
>
> If you need ffmpeg working with OpenCV now, then unbump it to 3.4.0
> instead of
> 3.4.1, and everything will work fine.
>
> --
> Arnaud <yth at ythogtha.org>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
Ah, just saw your original post.  I'll just install version 3.4.0.  Thanks
for the heads up.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180316/d465358f/attachment.html>

From sam_web at yahoo.de  Fri Mar 16 16:07:44 2018
From: sam_web at yahoo.de (Marek Srejma)
Date: Fri, 16 Mar 2018 17:07:44 +0100
Subject: [Slackbuilds-users] webkit2gtk 2.20 for review
In-Reply-To: <f9ae0025-b43a-b581-72b8-96a8a483d98b@slackbuilds.org>
References: <f9ae0025-b43a-b581-72b8-96a8a483d98b@slackbuilds.org>
Message-ID: <802fb8d0-daf2-a304-dde7-a715ecac6ee1@yahoo.de>

Hi Willy,

the latest development version of Luakit from GitHub works with 
WebKitGTK 2.20.

According to a statement on IRC by Aidan Holm (the main Luakit 
developer), there will soon be a new stable version:
> 2018-03-15 17:32:39???? groolot | aidanh: do you think of a next 
> version soon?
> 2018-03-15 17:44:30???? aidanh? | yeah, fairly soon; probably within a 
> week


Marek


Willy Sudiarto Raharjo schrieb:
> Hi all
>
> i have pushed a new branch, webkit2gtk-review in git for a public
> review. This is a major release and came up with a new dependencies,
> woff2, and geoclue2. Woff2 itself requires brotli, another new package
> All the new deps (woff2 and brotli) are already in David's branch for
> this week's public update, except for geoclue2 which is already on our
> repository.
>
> These are the packages that list webkit2gtk as hard dependency:
> development/wxHexEditor
> graphics/shotwell
> network/gui-ufw
> network/luakit
> network/midori
> network/surf
> network/vimb
> system/yelp
>
> in a quick test, most of them built just fine with the new webkit2gtk,
> but i'm not taking a risk of breaking scripts.
>
> So if you used the above packages, please help by testing the new
> webkit2gtk before it got merged in master.
>
> Thanks
>
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


From skaendo at excite.com  Fri Mar 16 18:47:26 2018
From: skaendo at excite.com (Ed Ender)
Date: Fri, 16 Mar 2018 14:47:26 -0400
Subject: [Slackbuilds-users] webkit2gtk 2.20 for review
Message-ID: <20180316144726.11541@web007.roc2.bluetie.com>

Willy,

wxHexEditor is working normal here also.

Ed

From didier at slint.fr  Fri Mar 16 22:22:31 2018
From: didier at slint.fr (Didier Spaier)
Date: Fri, 16 Mar 2018 23:22:31 +0100
Subject: [Slackbuilds-users] webkit2gtk 2.20 for review
In-Reply-To: <f9ae0025-b43a-b581-72b8-96a8a483d98b@slackbuilds.org>
References: <f9ae0025-b43a-b581-72b8-96a8a483d98b@slackbuilds.org>
Message-ID: <03f12a0a-42ae-7a65-fc4c-a243c7afbdcc@slint.fr>

Le 16/03/2018 ? 01:07, Willy Sudiarto Raharjo a ?crit?:
> So if you used the above packages, please help by testing the new
> webkit2gtk before it got merged in master.

No issue here with yelp, thanks!

[OT]my own builds of webkit2gtk-2.20.0 failed cf.:
https://bugs.webkit.org/show_bug.cgi?id=183595

Maybe because I removed too many features
although that works for 2.18.6.

I think that I'll stick with a stripped down
2.18.6 (shared but in a hidden location),
bundled with yelp for Slint.[/OT] 

Cheers,
Didier

From skaendo at excite.com  Sat Mar 17 00:52:45 2018
From: skaendo at excite.com (Ed Ender)
Date: Fri, 16 Mar 2018 20:52:45 -0400
Subject: [Slackbuilds-users] webkit2gtk 2.20 for review
Message-ID: <20180316205245.9011@web005.roc2.bluetie.com>

Willy,

Midori seems to be working well here too.

Ed



From chris.willing at iinet.net.au  Sat Mar 17 02:15:00 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Sat, 17 Mar 2018 12:15:00 +1000
Subject: [Slackbuilds-users] OpenCV SlackBuild bug - Was: ffmpeg does
 not compile with opencv 3.4.1
In-Reply-To: <20180316144805.e2525c4dd96e69927b13b855@ythogtha.org>
References: <20180313110418.990f42555e0c1d7632e9ec43@ythogtha.org>
 <d8455bd6-09dd-8075-1781-b5a1389e4d7a@iinet.net.au>
 <20180313165337.14c09e6487301df19cd8aa58@clansco.org>
 <20180313171918.609c514261ec4d84d4186103@clansco.org>
 <20180314144132.f8b8923856e25885e16710c5@ythogtha.org>
 <CAPsDuS5eS=9o-n8vA=xo1CiK2-imOr+ABJyG9dY=GAExv_WnrQ@mail.gmail.com>
 <686b19d1-7d98-73a0-5b39-36e43e2a786c@linux.com>
 <20180316144805.e2525c4dd96e69927b13b855@ythogtha.org>
Message-ID: <420ca91e-cab8-0b98-b58e-80c7f0f6cf55@iinet.net.au>

On 16/03/18 23:48, Ythogtha wrote:
>> Thanks all for spotting the problem. I've just pushed a fix for it.
>>
>> While working through this myself, I noticed that the requirement for
>> python3 to generate a python3 binding no longer works unless numpy3 is
>> also installed at build time. Since numpy3 requires python3, I've
>> replaced the requirement for python3 with numpy3.
>>
>> Back to the original problem of building ffmpeg with opencv support, I
>> haven't been able to compile that successfully. The configure phase
>> finds opencv OK but compilation fails with:
>>
>> In file included from /usr/include/opencv2/core/types_c.h:59:0,
>>                  from /usr/include/opencv2/core/core_c.h:48,
>>                  from libavfilter/vf_libopencv.c:28:
>> /usr/include/opencv2/core/cvdef.h:485:1: error: unknown type name
>> 'namespace'
>>  namespace cv {
>>  ^
>> /usr/include/opencv2/core/cvdef.h:485:14: error: expected '=', ',', ';',
>> 'asm' or '__attribute__' before '{' token
>>  namespace cv {
>>               ^
>> common.mak:60: recipe for target 'libavfilter/vf_libopencv.o' failed
>> make: *** [libavfilter/vf_libopencv.o] Error 1
>>
>>
>> It's not something I want to spend a lot of time trying to fix - for my
>> own use I have the dependency the other way around by building opencv
>> with ffmpeg support. However if anyone can propose a fix, I'm happy (and
>> grateful) to include it in the SlackBuild.
>>
>> chris
> 
> Hi!
> 
> 	I just went back into this, used your updated build for OpenCV and
> failed to compile ffmpeg.
> Then I found this :
> https://github.com/opencv/opencv/issues/10963
> 	So I modified the file /usr/include/opencv2/core/cvdef.h according to
> what's said there.
> And well, it works fine.
> ffmpeg compiles and runs perfectly.
> 
> 	So maybe including a patch to OpenCV since this seems to affect other
> softwares, like VLC apparently ?
> Your call Chris :)
> 

I just missed the cut off for the SBo update - it included only the
partial fix mentioned previously.

I'll check the additional cvdef.h patch and include it in the next
update. Thanks for finding it.

chris

From willysr at slackbuilds.org  Sat Mar 17 02:35:39 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 17 Mar 2018 09:35:39 +0700
Subject: [Slackbuilds-users] Updates - 20180317.1
Message-ID: <1c98168e-9b06-cdef-71d2-82dd8f625532@slackbuilds.org>

Hi,

we have the latest openjdk, openjdk8, hhvm, and latest intel-microcode
that was released by Intel few days ago.

Sat Mar 17 01:53:40 UTC 2018
academic/R: Updated for version 3.4.4.
academic/cld2: Fix build on current.
academic/suitesparse: Updated for version 5.2.0
academic/veusz: Updated for version 2.2.1.
audio/audacity: Updated for version 2.2.2.
audio/minimodem: Switch to i586.
audio/opus-tools: Updated for version 0.1.10.
audio/opusfile: Updated for version 0.10.
desktop/caffeine-ng: Updated for version 3.4.0.
desktop/kwalletcli: Switch to i586.
desktop/oranchelo-icon-theme: Updated for version 0.7.6.4.
desktop/polybar: Added (a fast and easy-to-use status bar).
desktop/screenkey: Add FontAwesome as dependency.
desktop/ssr: Updated for version 0.3.10.
desktop/xfce-hkmon: Added (Hacker's Monitor for Xfce).
desktop/xkblayout-state: Updated for version 1b_git20180118.
development/SQLAlchemy: Updated for version 1.2.5.
development/brotli: Added (compression algorithm).
development/colm: Updated for version 0.13.0.5.
development/cunit: Switch to i586.
development/eclipse-php: Added (Eclipse IDE for PHP Developers).
development/envytools: Updated for version 2018.03.10_dd0d6c2.
development/eovim: Updated for version 0.1.2.
development/hhvm: Updated for version 3.24.4
development/ioncube-loader: Updated for version 10.2.0
development/jupyter_client: Updated for version 5.2.3.
development/ocamlbuild: Updated for version 0.12.0.
development/openjdk8: Updated for version 8u161.
development/openjdk: Updated for version 7u171.
development/ragel: Updated for version 7.0.0.10.
development/tanya: Updated for version 0.7.9
development/textadept: Updated for version 9.6.
development/universal-ctags: Updated for version 5010e84
development/urjtag: Updated for version 2017.10pre2.
development/woff2: Added (Web Open Font Format 2).
games/RetroArch: More README information.
games/lutris: Updated for version 0.4.14.
games/openspades: Updated for version 0.1.2.
games/planetblupi: Updated for version 1.12.4.
games/stone_soup: Updated for version 0.21.1.
gis/Fiona: Add Python 3 support.
gis/Geohash: Add Python 3 support.
gis/cligj: Add Python 3 support.
gis/geographiclib-python: Add Python 3 support.
gis/geojson: Add Python 3 support.
gis/geopy: Updated for version 1.12.0.
gis/gpxsee: Updated for version 5.4.
gis/opencpn: Updated for version 4.8.2.
gis/openorienteering-mapper: Updated for version 0.8.1.
gis/qmapshack: Updated for version 1.11.0.
gis/xplanet: Fix build on current.
graphics/photoqt: Updated for version 1.6.
graphics/resynthesizer: Updated for version 2.0.3.
haskell/haskell-basement: Added (basic primitives).
haskell/haskell-cmark: Updated for version 0.5.6.
haskell/haskell-cryptonite: Updated for version 0.25.
haskell/haskell-foundation: Updated for version 0.0.20.
haskell/haskell-memory: Updated for version 0.14.16.
haskell/haskell-regex-tdfa: Updated for version 1.2.3.
libraries/allegro: Updated for version 5.2.4.0.
libraries/appstream-glib: Updated for version 0.7.7.
libraries/aqbanking: Updated for version 5.7.8.
libraries/botocore: Updated for version 1.9.6.
libraries/cfitsio: Update MD5SUM.
libraries/chromaprint: Updated for version 1.4.3.
libraries/frei0r: Updated for version 1.6.1, cleanups.
libraries/gwenhywfar: Updated for version 4.20.0.
libraries/lgi: Updated for version 0.9.2.
libraries/libcacard: Updated for version 2.5.3.
libraries/libfastjson: Updated for version 0.99.8.
libraries/libfdk-aac: Updated for version 0.1.6
libraries/libftdi1: Updated for version 1.4.
libraries/libgee: Updated for version 0.20.1.
libraries/libmikmod: Updated for version 3.3.11.1, changed homepage.
libraries/libmwaw: Updated for version 0.3.13.
libraries/libosinfo: Updated for version 1.1.0.
libraries/libsass: Updated for version 3.5.1.
libraries/libupnp: Add upstream patch to remove a private header.
libraries/libvirt: (Really) properly initialize $count in rc.libvirt
libraries/libvterm: Updated for version 20180220.
libraries/lxqt-build-tools: Updated for version 0.4.0.
libraries/netcdf: Updated for version 4.6.0.
libraries/opencv: Fix library path
libraries/qtermwidget: Updated for version 0.8.0.
libraries/tre: Add Python 3 support.
libraries/vte3-ng: Updated for version 0.50.2.a.
libraries/wxsvg: Updated for version 1.5.12.
multimedia/dvdstyler: Updated for version 3.0.4.
multimedia/flashplayer-plugin: Updated for version 29.0.0.113.
multimedia/opera-ffmpeg-codecs: Updated for version 64.0.3282.186.
multimedia/pepperflash-plugin: Updated for version 29.0.0.113.
multimedia/yarock: Updated for version 1.3.1.
network/Electrum: Updated for version 3.1.0.
network/GeoIP: Updated for version 1.6.12.
network/awscli: Updated for version 1.14.53.
network/conkeror: Updated for version 1.0.4.
network/lighttpd: Updated for version 1.4.49.
network/nextcloud-server: Updated for version 13.0.0.
network/opera-developer: Updated for version 53.0.2893.0.
network/phodav: Updated for version 2.2.
network/signal-desktop: Updated for version 1.6.0.
network/snort: Updated for version 2.9.11.1.
network/sqlmap: Updated for version 1.2.3.
network/tor-browser: Updated for version 7.5.1.
network/twine: Updated for version 1.10.0.
network/youtube-dl: Updated for version 2018.03.10.
office/juffed: Updated for version 20180114_9b7af21.
office/lyx: Updated for version 2.3.0.
office/pdf2djvu: Updated for version 0.9.8.
office/smoffice2018: Added (office suite).
office/xtrkcad: Updated for version 5.1.0.
perl/perl-file-basedir: Updated for version 0.08.
python/pluggy: Updated for version 0.6.0.
python/pycld2: Add Python 3 support.
python/pyewmh: Updated for version 0.1.6.
python/pytest-runner: Updated for version 4.0.
python/pytest: Updated for version 3.4.2.
python/python-autobahn: Updated for version 18.3.1.
python/python-m2r: Updated for version 0.1.13.
python/python-neovim: Updated for version 0.2.4.
python/python-txaio: Updated for version 2.9.0.
python/python-xcffib: Updated for version 0.6.0.
python/python-xlib: Updated for version 0.21 + new maintainer.
python/python3-dateutil: Updated for version 2.7.0.
python/python3-jupyter_client: Updated for version 5.2.3.
python/python3-xlib: Removed (replaced by python-xlib).
python/pyxdg: Updated for version 0.26.
python/s3transfer: Updated for version 0.1.13.
python/selenium: Updated for version 3.10.0.
python/setuptools-scm: Updated for version 1.15.7.
python/trollius: Updated for version 2.2.
system/BasiliskII: Removed (included in macemu).
system/ProFont: Added (bitmap font).
system/ack: Updated for version 2.22.
system/alacritty: Updated for version git6debc4f.
system/btrbk: Updated for version 0.26.1.
system/cantarell-fonts: Updated for version 0.101.
system/courier-screenplay: Added (a courier font).
system/dosbox-dev: Updated for version 0.74.r4085.
system/fakechroot: Added (gives a fake chroot environment).
system/fwupd: Updated for version 1.0.6.
system/intel-microcode: Updated for version 20180312.
system/macemu: Updated for version 20180225_2e302d6, cleanups.
system/osinfo-db: Updated for version 20180311.
system/qterminal: Updated for version 0.8.0.
system/rhash: Updated for version 1.3.5
system/rsyslog: Updated for version 8.33.1.
system/siji-font: Added (bitmap font).
system/spice-vdagent: Updated for version 0.17.0.
system/spkg: Updated for version 1.1.
system/termite: Updated for version 13.
system/the_silver_searcher: Script clean up.
system/thinkfan: Switch to i586.
system/ttf-lato: Added (TrueType Font).
system/udevil: Updated for version 0.4.4.
system/vagrant: Updated for version 2.0.3.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180317/76ee5be1/attachment.asc>

From didier at slint.fr  Sat Mar 17 10:34:51 2018
From: didier at slint.fr (Didier Spaier)
Date: Sat, 17 Mar 2018 11:34:51 +0100
Subject: [Slackbuilds-users] webkit2gtk 2.20 for review
In-Reply-To: <03f12a0a-42ae-7a65-fc4c-a243c7afbdcc@slint.fr>
References: <f9ae0025-b43a-b581-72b8-96a8a483d98b@slackbuilds.org>
 <03f12a0a-42ae-7a65-fc4c-a243c7afbdcc@slint.fr>
Message-ID: <e726eaa1-3814-f02d-d8de-232dcdf78e64@slint.fr>

Le 16/03/2018 ? 23:22, Didier Spaier a ?crit?:
> No issue here with yelp, thanks!

I forgot to tell: yelp version 3.26.0

From zanculmarktum at gmail.com  Sat Mar 17 22:59:07 2018
From: zanculmarktum at gmail.com (Azure Zanculmarktum)
Date: Sun, 18 Mar 2018 05:59:07 +0700
Subject: [Slackbuilds-users] geoclue seems to depends on gpsd
Message-ID: <CAPbfrh+c0ovK6-WNm9eOr0Hgd7GEjcj1NevcsnG0ej1f6bVKjw@mail.gmail.com>

Error log:
configure: error: Couldn't find gpsd dependencies.

From didier at slint.fr  Sat Mar 17 23:14:49 2018
From: didier at slint.fr (Didier Spaier)
Date: Sun, 18 Mar 2018 00:14:49 +0100
Subject: [Slackbuilds-users] geoclue seems to depends on gpsd
In-Reply-To: <CAPbfrh+c0ovK6-WNm9eOr0Hgd7GEjcj1NevcsnG0ej1f6bVKjw@mail.gmail.com>
References: <CAPbfrh+c0ovK6-WNm9eOr0Hgd7GEjcj1NevcsnG0ej1f6bVKjw@mail.gmail.com>
Message-ID: <b7d295cd-1fd4-aa1c-c1e8-e34710459eb9@slint.fr>



Le 17/03/2018 ? 23:59, Azure Zanculmarktum a ?crit?:
> Error log:
> configure: error: Couldn't find gpsd dependencies.

Not here:

...
Le paquet Slackware /usr/src/slapt-src/system/geoclue/geoclue-0.12.99-x86_64-1_SBo.tgz a ?t? cr??.

Didier

From zanculmarktum at gmail.com  Sat Mar 17 23:41:50 2018
From: zanculmarktum at gmail.com (Azure Zanculmarktum)
Date: Sun, 18 Mar 2018 06:41:50 +0700
Subject: [Slackbuilds-users] geoclue seems to depends on gpsd
In-Reply-To: <b7d295cd-1fd4-aa1c-c1e8-e34710459eb9@slint.fr>
References: <CAPbfrh+c0ovK6-WNm9eOr0Hgd7GEjcj1NevcsnG0ej1f6bVKjw@mail.gmail.com>
 <b7d295cd-1fd4-aa1c-c1e8-e34710459eb9@slint.fr>
Message-ID: <CAPbfrhKEZDHsXqyuL_s4YAxdzw=3f4R5Ltr=HBp-o1-r_FTu8g@mail.gmail.com>

> Not here:
>
> ...
> Le paquet Slackware
> /usr/src/slapt-src/system/geoclue/geoclue-0.12.99-x86_64-1_SBo.tgz a ?t?
> cr??.
>
> Didier

You're right.
Seems that I uninstalled some core packages.

From s.arcus at open-t.co.uk  Sun Mar 18 11:47:27 2018
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Sun, 18 Mar 2018 11:47:27 +0000
Subject: [Slackbuilds-users] Changes Postgresql SBo scripts as version
 numbering has changed?
Message-ID: <12e4ed9f-3acc-6d47-7a35-87aa6f7072a8@open-t.co.uk>

As Postgresql number scheme has changed with version 10 (and going 
forward), and only the first number is the major version number, I was 
wondering if it is worth amending the SBo scripts to reflect that. The 
data dir, bin dir and log dir usually need to only be prefixed with the 
major number, not the full version - to help with upgrades from one 
major version to another.

I would have made a patch myself, but I got a bit lost on how the old 
SBo scripts used to use the full (e.g. 9.6.2) version in 
postgresql.SlackBuild, yet end up with only the major version (e.g. 9.6) 
further down the line, in rc.postgresql, setup.postgresql and other 
scripts - so maybe someone can help?

From atelszewski at gmail.com  Sun Mar 18 12:00:57 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 18 Mar 2018 13:00:57 +0100
Subject: [Slackbuilds-users] test
Message-ID: <2f29d5c3-fbbb-716f-2ead-0e692364ad69@gmail.com>

Hi,

Can you see me? :-)

-- 
Best regards / Pozdrawiam,
Andrzej Telszewski

From s.arcus at open-t.co.uk  Sun Mar 18 12:04:10 2018
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Sun, 18 Mar 2018 12:04:10 +0000
Subject: [Slackbuilds-users] Changes Postgresql SBo scripts as version
 numbering has changed?
In-Reply-To: <12e4ed9f-3acc-6d47-7a35-87aa6f7072a8@open-t.co.uk>
References: <12e4ed9f-3acc-6d47-7a35-87aa6f7072a8@open-t.co.uk>
Message-ID: <dbc9b339-bb19-a4cf-7396-f048d7b0bd9f@open-t.co.uk>


On 18/03/18 11:47, Sebastian Arcus wrote:
> As Postgresql number scheme has changed with version 10 (and going 
> forward), and only the first number is the major version number, I was 
> wondering if it is worth amending the SBo scripts to reflect that. The 
> data dir, bin dir and log dir usually need to only be prefixed with the 
> major number, not the full version - to help with upgrades from one 
> major version to another.
> 
> I would have made a patch myself, but I got a bit lost on how the old 
> SBo scripts used to use the full (e.g. 9.6.2) version in 
> postgresql.SlackBuild, yet end up with only the major version (e.g. 9.6) 
> further down the line, in rc.postgresql, setup.postgresql and other 
> scripts - so maybe someone can help?

Partially answering the question myself - in postgresql.SlackBuild there 
is a "VERSION=" and a "PG_VERSION=". It looks like "PG_VERSION=" would 
need to be amended to 10, instead of 10.2 - and hopefully everything 
else would fall into place.

From alleytrotter at gmail.com  Sun Mar 18 12:06:38 2018
From: alleytrotter at gmail.com (John Yost)
Date: Sun, 18 Mar 2018 08:06:38 -0400
Subject: [Slackbuilds-users] Bounce
Message-ID: <74fe38f8-9b22-7d5e-3d48-e70514d0643f@gmail.com>

Is it possible to get a copy of the "bounced messages" for my ISP so I
can investigate the reasons for the bounces?
-- 
John David Yost
AlleyTrotter
pub   2048D/F3BDEB55 2014-05-23 [expires: Never]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xF3BDEB55.asc
Type: application/pgp-keys
Size: 2312 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180318/80c1ce35/attachment.bin>

From bormant at gmail.com  Sun Mar 18 12:09:01 2018
From: bormant at gmail.com (Serg Bormant)
Date: Sun, 18 Mar 2018 15:09:01 +0300
Subject: [Slackbuilds-users] Bounce
In-Reply-To: <74fe38f8-9b22-7d5e-3d48-e70514d0643f@gmail.com>
References: <74fe38f8-9b22-7d5e-3d48-e70514d0643f@gmail.com>
Message-ID: <CAD7s_azfg04hEf1TeGkE98JSEqqfKnTaGWHUewj3ZGZmt-v_xw@mail.gmail.com>

The same here.

-- 
wbr, sb
18.03.2018 15:06 ???????????? "John Yost" <alleytrotter at gmail.com> ???????:

> Is it possible to get a copy of the "bounced messages" for my ISP so I
> can investigate the reasons for the bounces?
> --
> John David Yost
> AlleyTrotter
> pub   2048D/F3BDEB55 2014-05-23 [expires: Never]
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180318/fa6cdc4a/attachment.html>

From didier at slint.fr  Sun Mar 18 12:10:23 2018
From: didier at slint.fr (Didier Spaier)
Date: Sun, 18 Mar 2018 13:10:23 +0100
Subject: [Slackbuilds-users] test
In-Reply-To: <2f29d5c3-fbbb-716f-2ead-0e692364ad69@gmail.com>
References: <2f29d5c3-fbbb-716f-2ead-0e692364ad69@gmail.com>
Message-ID: <1226156a-d819-4031-de6b-5db9cf843734@slint.fr>

Hi,

Le 18/03/2018 ? 13:00, Andrzej Telszewski a ?crit?:
> Hi,
> 
> Can you see me? :-)

No, there is no attached picture.

But at least we can hear you :-)

From atelszewski at gmail.com  Sun Mar 18 12:17:52 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 18 Mar 2018 13:17:52 +0100
Subject: [Slackbuilds-users] test
In-Reply-To: <1226156a-d819-4031-de6b-5db9cf843734@slint.fr>
References: <2f29d5c3-fbbb-716f-2ead-0e692364ad69@gmail.com>
 <1226156a-d819-4031-de6b-5db9cf843734@slint.fr>
Message-ID: <3748a46b-6403-f9d7-aacb-3a01e7d662e0@gmail.com>

On 18/03/18 13:10, Didier Spaier wrote:
> Hi,
> 
> Le 18/03/2018 ? 13:00, Andrzej Telszewski a ?crit?:
>> Hi,
>>
>> Can you see me? :-)
> 
> No, there is no attached picture.
> 
> But at least we can hear you :-)

Fair enough ;-)

-- 
Best regards / Pozdrawiam,
Andrzej Telszewski

From rob0 at slackbuilds.org  Sun Mar 18 19:04:01 2018
From: rob0 at slackbuilds.org (Rob McGee)
Date: Sun, 18 Mar 2018 14:04:01 -0500
Subject: [Slackbuilds-users] Bounce
In-Reply-To: <CAD7s_azfg04hEf1TeGkE98JSEqqfKnTaGWHUewj3ZGZmt-v_xw@mail.gmail.com>
References: <74fe38f8-9b22-7d5e-3d48-e70514d0643f@gmail.com>
 <CAD7s_azfg04hEf1TeGkE98JSEqqfKnTaGWHUewj3ZGZmt-v_xw@mail.gmail.com>
Message-ID: <20180318190401.GB2515@harrier.slackbuilds.org>

> 18.03.2018 15:06 "John Yost" <alleytrotter at gmail.com>:
> 
> > Is it possible to get a copy of the "bounced messages" for my
> > ISP so I can investigate the reasons for the bounces?

On Sun, Mar 18, 2018 at 03:09:01PM +0300, Serg Bormant wrote:
> The same here.

Not sure what you are asking.  Are either of you having trouble 
receiving mail from, or posting to, this mailing list?  If so I have 
logs which might shed some light on the problem.  I'd need to know 
details, of course -- when and how, et c.

Otherwise, you're not on topic asking here, but your answer is, 
"Probably not."
-- 
    Rob McGee - /dev/rob0 - rob0 at slackbuilds.org

From matteo.bernardini at gmail.com  Sun Mar 18 19:12:27 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 18 Mar 2018 20:12:27 +0100
Subject: [Slackbuilds-users] Bounce
In-Reply-To: <20180318190401.GB2515@harrier.slackbuilds.org>
References: <74fe38f8-9b22-7d5e-3d48-e70514d0643f@gmail.com>
 <CAD7s_azfg04hEf1TeGkE98JSEqqfKnTaGWHUewj3ZGZmt-v_xw@mail.gmail.com>
 <20180318190401.GB2515@harrier.slackbuilds.org>
Message-ID: <CAPsDuS4MCnbD1sCB4LuZ4UD0U08=8rLvQzdPwJhh_aporAJcFQ@mail.gmail.com>

2018-03-18 20:04 GMT+01:00 Rob McGee <rob0 at slackbuilds.org>:
>> 18.03.2018 15:06 "John Yost" <alleytrotter at gmail.com>:
>>
>> > Is it possible to get a copy of the "bounced messages" for my
>> > ISP so I can investigate the reasons for the bounces?
>
> On Sun, Mar 18, 2018 at 03:09:01PM +0300, Serg Bormant wrote:
>> The same here.
>
> Not sure what you are asking.  Are either of you having trouble
> receiving mail from, or posting to, this mailing list?  If so I have
> logs which might shed some light on the problem.  I'd need to know
> details, of course -- when and how, et c.
>
> Otherwise, you're not on topic asking here, but your answer is,
> "Probably not."

I think he is referring to this email that most probably every account
on gmail subscribed to the ML seems to have received 7.30 hours ago...

- - -

Your membership in the mailing list SlackBuilds-users has been
disabled due to excessive bounces The last bounce received from you
was dated 18-Mar-2018.  You will not get any more messages from this
list until you re-enable your membership.  You will receive 3 more
reminders like this before your membership in the list is deleted.

To re-enable your membership, you can simply respond to this message
(leaving the Subject: line intact), or visit the confirmation page at

    https://lists.slackbuilds.org/mailman/confirm/slackbuilds-users/{hash}


You can also visit your membership page at

    https://lists.slackbuilds.org/mailman/options/slackbuilds-users/matteo.bernardini%40gmail.com


On your membership page, you can change various delivery options such
as your email address and whether you get digests or not.  As a
reminder, your membership password is

    {supersecretpassword}

If you have any questions or problems, you can contact the list owner
at

    slackbuilds-users-owner at slackbuilds.org

From brent at exitstatusone.com  Sun Mar 18 19:25:19 2018
From: brent at exitstatusone.com (Brenton Earl)
Date: Sun, 18 Mar 2018 13:25:19 -0600
Subject: [Slackbuilds-users] test
In-Reply-To: <2f29d5c3-fbbb-716f-2ead-0e692364ad69@gmail.com>
References: <2f29d5c3-fbbb-716f-2ead-0e692364ad69@gmail.com>
Message-ID: <49b09fbb-585c-5b1c-71b4-e71fa91530e5@exitstatusone.com>

On 03/18/2018 06:00 AM, Andrzej Telszewski wrote:
> Hi,
> 
> Can you see me? :-)

Yes I can.

-- 
Brenton Earl

From harald.achitz at gmail.com  Sun Mar 18 19:41:10 2018
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sun, 18 Mar 2018 20:41:10 +0100
Subject: [Slackbuilds-users] what means: membership disabled due to
 excessive bounces
Message-ID: <CAPh+tzNj0z=2behC6JP7siVKtckL41wMgqo8K+oKBeLeDJSBXw@mail.gmail.com>

Hi

I got a mail with text

Your membership in the mailing list SlackBuilds-users has been disabled due
to excessive bounces

What does this mean?

I have not sent any mails, am I hacked?

Thanks for info!

/Harald
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180318/4b80a38a/attachment.html>

From ekinakoglu at gmail.com  Sun Mar 18 19:45:04 2018
From: ekinakoglu at gmail.com (Ekin Akoglu)
Date: Sun, 18 Mar 2018 22:45:04 +0300
Subject: [Slackbuilds-users] Fwd: confirm
 15268c469c9080183d369d0b98238e0bff4a2bfa
In-Reply-To: <mailman.85.1521373702.2394.slackbuilds-users@slackbuilds.org>
References: <mailman.85.1521373702.2394.slackbuilds-users@slackbuilds.org>
Message-ID: <096b2417-65d6-78a6-b650-60e37037c843@gmail.com>

I have also received the e-mail below. I removed the private content in 
the e-mail.

Best,

Ekin

-------- Forwarded Message --------
Subject: 	confirm 15268c469c9080183d369d0b98238e0bff4a2bfa
Date: 	Sun, 18 Mar 2018 11:48:22 +0000
From: 	slackbuilds-users-request at slackbuilds.org
To: 	ekinakoglu at gmail.com


Your membership in the mailing list SlackBuilds-users has been

disabled due to excessive bounces The last bounce received from you
was dated 18-Mar-2018.  You will not get any more messages from this
list until you re-enable your membership.  You will receive 3 more
reminders like this before your membership in the list is deleted.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180318/808580d3/attachment.html>

From thedoogster at gmail.com  Sun Mar 18 19:49:37 2018
From: thedoogster at gmail.com (Doogster)
Date: Sun, 18 Mar 2018 12:49:37 -0700
Subject: [Slackbuilds-users] what means: membership disabled due to
 excessive bounces
In-Reply-To: <CAPh+tzNj0z=2behC6JP7siVKtckL41wMgqo8K+oKBeLeDJSBXw@mail.gmail.com>
References: <CAPh+tzNj0z=2behC6JP7siVKtckL41wMgqo8K+oKBeLeDJSBXw@mail.gmail.com>
Message-ID: <CAE5oDaZN_ivyP3XNSXS6+ZKb4=hamxfvQ17v7SByxwcdvXh1bQ@mail.gmail.com>

I got it too.

I assume it means that the SBo mailing list server had trouble
delivering mail to me, for some reason.

On Sun, Mar 18, 2018 at 12:41 PM, Harald Achitz <harald.achitz at gmail.com> wrote:
> Hi
>
> I got a mail with text
>
> Your membership in the mailing list SlackBuilds-users has been disabled due
> to excessive bounces
>
> What does this mean?
>
> I have not sent any mails, am I hacked?
>
> Thanks for info!
>
> /Harald
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

From alanians at telus.net  Sun Mar 18 19:51:48 2018
From: alanians at telus.net (Alan Ianson)
Date: Sun, 18 Mar 2018 12:51:48 -0700
Subject: [Slackbuilds-users] Fwd: confirm
 15268c469c9080183d369d0b98238e0bff4a2bfa
References: <mailman.85.1521373702.2394.slackbuilds-users@slackbuilds.org>
Message-ID: <20180318125148.816e7dbdad89d74cdbd0f071@telus.net>

On Sun, 18 Mar 2018 22:45:04 +0300
Ekin Akoglu <ekinakoglu at gmail.com> wrote:

> I have also received the e-mail below. I removed the private content in 
> the e-mail.

Must be some sort of gmail thing, I got it too but am resubscribed now.

From kingbeowulf at gmail.com  Sun Mar 18 20:01:38 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 18 Mar 2018 13:01:38 -0700
Subject: [Slackbuilds-users] what means: membership disabled due to
 excessive bounces
In-Reply-To: <CAPh+tzNj0z=2behC6JP7siVKtckL41wMgqo8K+oKBeLeDJSBXw@mail.gmail.com>
References: <CAPh+tzNj0z=2behC6JP7siVKtckL41wMgqo8K+oKBeLeDJSBXw@mail.gmail.com>
Message-ID: <f3ef490a-4305-a6da-80e1-b084f58771d5@gmail.com>

On 03/18/2018 12:41 PM, Harald Achitz wrote:
> Hi
> 
> I got a mail with text
> 
> Your membership in the mailing list SlackBuilds-users has been?disabled
> due to excessive bounces
> 
> What does this mean?
> 
> I have not sent any mails, am I hacked?
> 
> Thanks for info!
> 
> /Harald
> 
> 
> 

Its a gmail issue.  Already address here and on #slackbuilds.  Should be
fixed (for now).

-Ed



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180318/ca498ccb/attachment.asc>

From rob0 at slackbuilds.org  Sun Mar 18 20:20:04 2018
From: rob0 at slackbuilds.org (Rob McGee)
Date: Sun, 18 Mar 2018 15:20:04 -0500
Subject: [Slackbuilds-users] Today's DMARC debacle
Message-ID: <20180318202004.GC2515@harrier.slackbuilds.org>

Today a poster from a domain which published a DMARC "p=reject" 
policy posted to our mailing list.  Either his DMARC record is new, 
or gmail just started enforcing DMARC, and so, unseen by all our 
numerous gmail/googlemail and Google Apps subscribers, you were 
kicked off our list.

Yes, it's stupid.  DMARC allows third/fourth parties to do this 
denial of service.  Mailing lists since forever have used the 
original sender's "From:" header, but the list server's envelope 
sender.  DMARC looks at the header, not the envelope.

But, as with so many things, we are stuck with stupid stuff.

GNU Mailman already has a workaround for the problem: it looks up 
DMARC for the poster's domain, and if a "p=reject" is published, the 
From header is rewritten.  Yay, so you don't know who it was from.

(Another workaround is to simply disallow posts from such domains.)

Anyway, I'm working on the first workaround, and the poster who 
triggered all this is temporarily blocked from posting.

We have placed the list on emergency moderation mode for now.  
Please, no more posts about this until I get it resolved.  I will 
reply here when it is.

I'm sorry for the inconvenience.  I am sorry that DMARC exists.

Fortunately it was only the posts (two) from this poster which caused 
all the havoc.  Every subscriber who was removed from the list should 
have received their notification of removal.  The problem was not a 
matter of gmail not accepting mail from us; only that the DMARC 
perpetrator was listed in the From: header.  Not a factor for the 
removal notification mails from Mailman.
-- 
    Rob McGee - /dev/rob0 - rob0 at slackbuilds.org

From rob0 at slackbuilds.org  Sun Mar 18 21:08:01 2018
From: rob0 at slackbuilds.org (Rob McGee)
Date: Sun, 18 Mar 2018 16:08:01 -0500
Subject: [Slackbuilds-users] Today's DMARC debacle
In-Reply-To: <20180318202004.GC2515@harrier.slackbuilds.org>
References: <20180318202004.GC2515@harrier.slackbuilds.org>
Message-ID: <20180318210801.GD2515@harrier.slackbuilds.org>

On Sun, Mar 18, 2018 at 03:20:04PM -0500, Rob McGee wrote:
> We have placed the list on emergency moderation mode for now.  
> Please, no more posts about this until I get it resolved.  I will 
> reply here when it is.

DEFAULT_DMARC_MODERATION_ACTION = 1

This will rewrite the From: headers of posters from domains with 
DMARC reject or quarantine policies.  Personally I think those 
addresses should not be allowed to post to mailing lists at all, but 
this is less painful overall, especially considering that many 
subscribers don't control their email providers' policies.

Yes, I should have done this a few years ago.  Oh well.
-- 
    Rob McGee - /dev/rob0 - rob0 at slackbuilds.org

From zanculmarktum at gmail.com  Sun Mar 18 22:34:22 2018
From: zanculmarktum at gmail.com (Azure Zanculmarktum)
Date: Mon, 19 Mar 2018 05:34:22 +0700
Subject: [Slackbuilds-users] Updates - 20180317.1
Message-ID: <CAPbfrh+xeGdxDvCoVXuPPxQJMUpwvUP6+sR7nKZTFxjB=WTbpw@mail.gmail.com>

No webkit2gtk?

From zanculmarktum at gmail.com  Sun Mar 18 22:36:55 2018
From: zanculmarktum at gmail.com (Azure Zanculmarktum)
Date: Mon, 19 Mar 2018 05:36:55 +0700
Subject: [Slackbuilds-users] test
Message-ID: <CAPbfrhLabzyarEpnX9-K=v3h96vXXSdyxp9FyD73aPRxWSFTgA@mail.gmail.com>

test

From zanculmarktum at gmail.com  Sun Mar 18 22:39:48 2018
From: zanculmarktum at gmail.com (Azure Zanculmarktum)
Date: Mon, 19 Mar 2018 05:39:48 +0700
Subject: [Slackbuilds-users] test
Message-ID: <CAPbfrh+ncEyWkELWog1OSuCeXx5FwKXdYhjqN=R9zdnAoBna4Q@mail.gmail.com>

reply test

From martijn at inlv.org  Sun Mar 18 22:56:30 2018
From: martijn at inlv.org (Martijn Dekker)
Date: Sun, 18 Mar 2018 23:56:30 +0100
Subject: [Slackbuilds-users] what means: membership disabled due to
 excessive bounces
In-Reply-To: <CAPh+tzNj0z=2behC6JP7siVKtckL41wMgqo8K+oKBeLeDJSBXw@mail.gmail.com>
References: <CAPh+tzNj0z=2behC6JP7siVKtckL41wMgqo8K+oKBeLeDJSBXw@mail.gmail.com>
Message-ID: <d3ec8078-3dab-8bf0-f61f-f3aec34a66e3@inlv.org>

Op 18-03-18 om 20:41 schreef Harald Achitz:
> Your membership in the mailing list SlackBuilds-users has been?disabled
> due to excessive bounces
> 
> What does this mean?

It means the listserver was unable to deliver email to your address for
too long.

- M.

From mario at slackware.hr  Sun Mar 18 23:36:05 2018
From: mario at slackware.hr (Mario)
Date: Mon, 19 Mar 2018 00:36:05 +0100
Subject: [Slackbuilds-users] Asterisk
In-Reply-To: <1113081501.322201.1521225355677@privateemail.com>
References: <1113081501.322201.1521225355677@privateemail.com>
Message-ID: <ebb7de33-4d34-cb91-b9eb-decda8ffb830@slackware.hr>

On 03/16/2018 07:35 PM, admin at falseking.org admin at falseking.org wrote:
> Good evening,
> 
> What do you thin about updating asterisk to version 15? if you are not 
> intersted I really can do it.
> 
> Thank you,
> 

Hi,

Feel free to take it over and improve ;)

Regards,

-- 
Mario

From willysr at slackbuilds.org  Mon Mar 19 00:13:35 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 19 Mar 2018 07:13:35 +0700
Subject: [Slackbuilds-users] Updates - 20180317.1
In-Reply-To: <CAPbfrh+xeGdxDvCoVXuPPxQJMUpwvUP6+sR7nKZTFxjB=WTbpw@mail.gmail.com>
References: <CAPbfrh+xeGdxDvCoVXuPPxQJMUpwvUP6+sR7nKZTFxjB=WTbpw@mail.gmail.com>
Message-ID: <9065f5bb-3e47-c7ba-519c-ba62e70e2508@slackbuilds.org>

> No webkit2gtk?

It will be part of this week's update


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180319/6daeebfd/attachment.asc>

From chris.willing at iinet.net.au  Mon Mar 19 07:18:04 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Mon, 19 Mar 2018 17:18:04 +1000
Subject: [Slackbuilds-users] libupnp for linphone (was Re: Retroshare do not
 work Slackware.)
In-Reply-To: <CA+da1opzLQpCkq4j5WdTTe1JgdRseQkhSj9rq0H8Uobz08PFqQ@mail.gmail.com>
References: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
 <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
 <CA+da1orA8+L=hbHpPU5obMb=Brdy9g1VAAyBpRCTWNdX2NKPLw@mail.gmail.com>
 <CAPsDuS4SKL2z7vzk1cRgZhaRAFy+p3uD6bwLt9SKLr_-9PpAAw@mail.gmail.com>
 <CA+da1ooGngV8oLkxqGSWMX4B3WAC-kov7qQS-ceF3sUeMsTQvA@mail.gmail.com>
 <135d24bb-91e8-bf8f-cc71-8bc0cf0d44c2@iinet.net.au>
 <CA+da1opzLQpCkq4j5WdTTe1JgdRseQkhSj9rq0H8Uobz08PFqQ@mail.gmail.com>
Message-ID: <a49ee253-1f8c-3800-fcec-97c406df39a7@iinet.net.au>

On 15/03/18 05:01, Ozan T?rky?lmaz wrote:
> 
> 2018-03-13 16:15 GMT+05:00 Christoph Willing <chris.willing at iinet.net.au
> <mailto:chris.willing at iinet.net.au>>:
> 
>     Yes, that patch is just a partial fix.
> 
>     The API for libupnp has changed in the new 1.8.x versions (SBo has
>     libupnp-1.8.3 at the moment). Retroshare devs will need to update their
>     code to utilize the new libupnp API.
> 
>     Without any indication of how long that might take, maybe we need a
>     libupnp-legacy SlackBuild with version capped at the latest in the 1.6.x
>     series so that retroshare can continue to be built. Otherwise we sit
>     tight with a SlackBuild that won't build until upstream updates
>     their code.
> 
> 
> 
> I have started working on a legacy packge right now.
> 

It looks like linphone also needs a libupnp-legacy (linphone compilation
fails with most recent version of libupnp).

chris

From adis at linux.org.ba  Mon Mar 19 09:01:25 2018
From: adis at linux.org.ba (Adis Nezirovic)
Date: Mon, 19 Mar 2018 10:01:25 +0100
Subject: [Slackbuilds-users] Changes Postgresql SBo scripts as version
 numbering has changed?
In-Reply-To: <dbc9b339-bb19-a4cf-7396-f048d7b0bd9f@open-t.co.uk>
References: <12e4ed9f-3acc-6d47-7a35-87aa6f7072a8@open-t.co.uk>
 <dbc9b339-bb19-a4cf-7396-f048d7b0bd9f@open-t.co.uk>
Message-ID: <CALHPnvjySmgvj1Qm=f=_vN5jbgBkR7C6+we-vPYouZeE4oYe0g@mail.gmail.com>

Sebastian, you are right, we've switched to 10.2 not too long ago, and
I've forgot to shorten PG_VERSION to 10 only. I'll update the script,
but we have to be careful, since there might be people who have
datadir at /var/lib/pgsql/10.2/data.

Best regards,
Adis

On Sun, Mar 18, 2018 at 1:04 PM, Sebastian Arcus <s.arcus at open-t.co.uk> wrote:
>
> On 18/03/18 11:47, Sebastian Arcus wrote:
>>
>> As Postgresql number scheme has changed with version 10 (and going
>> forward), and only the first number is the major version number, I was
>> wondering if it is worth amending the SBo scripts to reflect that. The data
>> dir, bin dir and log dir usually need to only be prefixed with the major
>> number, not the full version - to help with upgrades from one major version
>> to another.
>>
>> I would have made a patch myself, but I got a bit lost on how the old SBo
>> scripts used to use the full (e.g. 9.6.2) version in postgresql.SlackBuild,
>> yet end up with only the major version (e.g. 9.6) further down the line, in
>> rc.postgresql, setup.postgresql and other scripts - so maybe someone can
>> help?
>
>
> Partially answering the question myself - in postgresql.SlackBuild there is
> a "VERSION=" and a "PG_VERSION=". It looks like "PG_VERSION=" would need to
> be amended to 10, instead of 10.2 - and hopefully everything else would fall
> into place.
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From slackbuilds at schoepfer.info  Mon Mar 19 09:16:28 2018
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 19 Mar 2018 10:16:28 +0100
Subject: [Slackbuilds-users] physfs
Message-ID: <3e6df33d4b3c1a215a484cb739d887a8@schoepfer.info>

Hi,

i've updated physfs to 3.0.1:
https://git.slackbuilds.org/slackbuilds/plain/libraries/physfs/physfs.SlackBuild?id=56e84de9a57f58850f7a3b6c4fabaab9ce3d0769

In case someone maintainers want to check, the following builds
depend on physfs:
d1x-rebirth
d2x-rebirth
trigger-rally
lincity-ng
glestae
sumwars
egoboo
neverball
solarus
blobby2
asc
supertux
warzone2100
love
love-legacy072
love-legacy080




From yth at ythogtha.org  Mon Mar 19 09:58:17 2018
From: yth at ythogtha.org (Ythogtha)
Date: Mon, 19 Mar 2018 10:58:17 +0100
Subject: [Slackbuilds-users] ARM download links and the syncthing slackbuild.
Message-ID: <20180319105817.a7033b040c2d9efd8e526a81@ythogtha.org>

Good morning slackbuild !

	today I want to ask for a optional change in the .info files of the
slackbuilds.
The problem is for slackbuilds with specific download links for non-x86 targets.
There are already the DOWNLOAD_x86_64 and MD5SUM_x86_64 lines for packages that
have a different source file for x86 and x86_64.

	Specifically, the syncthing slackbuild repackages the official binaries,
so the DOWNLOAD_x86_64 is used. But syncthing works very well on ARM targets,
and is quite useful on small SoC computers like RPi or XU4.
	There is nothing really problematic with adapting the
syncthing.slackbuild to handle making an ARM package, but the DOWNLOAD_ARM -
there, I wrote it - is notavailable, neither is its MD5.

	So, I know that slackbuilds does not officially support ARM platform,
but it does not not support it either, a lot of slackbuilds works just fine on
slackwarearm, which is good.
	Here I'm not asking for anybody to make any effort to make sure their
slackbuilds are building fine on ARM, but just to allow an optional modification
of the .info file to add those two lines :
DOWNLOAD_ARM=""
MD5SUM_ARM=""
Those two lines could be optional, but their syntax should be official, if there
is another package that may need them.

	It shouldn't disrupt anything, nothing changes really, only for tools,
or people, willing to handle ARM when there is something to handle, they can do
it. Else everybody can just ignore those lines and nothing changes.

	Granted, today, I know only of one slackbuild with this specific issue,
syncthing, but that should make it easier to allow for an optional way to handle
ARM platforms in the future, should we want to do it.


Have a nice day :)

-- 
Arnaud <yth at ythogtha.org>

From ozan.turkyilmaz at gmail.com  Mon Mar 19 14:58:04 2018
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Mon, 19 Mar 2018 19:58:04 +0500
Subject: [Slackbuilds-users] Retroshare do not work Slackware.
In-Reply-To: <CA+da1opzLQpCkq4j5WdTTe1JgdRseQkhSj9rq0H8Uobz08PFqQ@mail.gmail.com>
References: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
 <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
 <CA+da1orA8+L=hbHpPU5obMb=Brdy9g1VAAyBpRCTWNdX2NKPLw@mail.gmail.com>
 <CAPsDuS4SKL2z7vzk1cRgZhaRAFy+p3uD6bwLt9SKLr_-9PpAAw@mail.gmail.com>
 <CA+da1ooGngV8oLkxqGSWMX4B3WAC-kov7qQS-ceF3sUeMsTQvA@mail.gmail.com>
 <135d24bb-91e8-bf8f-cc71-8bc0cf0d44c2@iinet.net.au>
 <CA+da1opzLQpCkq4j5WdTTe1JgdRseQkhSj9rq0H8Uobz08PFqQ@mail.gmail.com>
Message-ID: <CA+da1oqR_YS1pn1RifaYv5r4BOYGJEzNA_WqPYnFiZ-S-uzt_g@mail.gmail.com>

2018-03-15 0:01 GMT+05:00 Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>:

>
> 2018-03-13 16:15 GMT+05:00 Christoph Willing <chris.willing at iinet.net.au>:
>
>> I have started working on a legacy packge right now.
>>
>
>
I have prepared a legacy package for libupnp. I got retroshare complining
with it. It's not possible to use it with libupnp package.
I work on it if it is possible for not conflicting with libunpnp

-- 
Ozan, BSc, BEng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180319/c5191fb2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libupnp-legacy.tar.gz
Type: application/gzip
Size: 2673 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180319/c5191fb2/attachment.bin>

From yth at ythogtha.org  Mon Mar 19 17:50:01 2018
From: yth at ythogtha.org (Ythogtha)
Date: Mon, 19 Mar 2018 18:50:01 +0100
Subject: [Slackbuilds-users] openjdk8 doesn't build when brlcad is installed.
Message-ID: <20180319185001.b418250aec91eb1827fe6b2b@ythogtha.org>

Hello, it's me again...

	today, the joke is that openjdk8 build fails when brlcad is installed,
it complains that some file isn't in BRL-CAD format.

	This particular problem doesn't matter at all, removepk brlcad, compile
openjdk8, then reinstall brlcad, and everything is pretty fine.
It might warrant a note on the openjdk8 slackbuild.

	I must concede that I am currently in absolutely no mood to investigate
the problem and try to solve it in another way :)
I refuse to loose time to try to understand why JAVA - whichever version that may
be - does what it does.

Cheers !

-- 
Arnaud <yth at ythogtha.org>

From ml at mareichelt.com  Mon Mar 19 17:56:11 2018
From: ml at mareichelt.com (Markus Reichelt)
Date: Mon, 19 Mar 2018 18:56:11 +0100
Subject: [Slackbuilds-users] python-mock up for grabs
Message-ID: <20180319175611.GA12621@pc21.mareichelt.com>

hear hear, python-mock is still up for grabs.

just in case we haven't already some of 'this foo is vacant @
SBo.org' procedure in place, could we /please/ get some?



* Markus Reichelt <ml at mareichelt.com> wrote:

> Hi Glenn,
> 
> It's been some time and I get requests to update mock from time to
> time cos I'm still listed as maintainer.
> 
> Are you going to adopt mock or not?
> 
> Cos if not, it's up for grabs still/again.
> 
> Thanks.
> -me
> 
> * Glenn Becker <glenn.becker at gmail.com> wrote:
> 
> > Date: Sat, 1 Aug 2015 16:57:23 -0400
> > From: Glenn Becker <glenn.becker at gmail.com>
> > To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> > Subject: Re: [Slackbuilds-users] python-mock up for grabs
> > 
> > I am willing to adopt.
> > 
> > - Glenn
> > 
> > <http://projecteuler.net/profile/gbecker.png>
> > 
> > On Sat, Aug 1, 2015 at 5:56 AM, Markus Reichelt <ml at mareichelt.com> wrote:
> > 
> > > Aloha!
> > >
> > > http://slackbuilds.org/repository/14.1/python/mock/ is up for grabs
> > >
> > > since v1.10.2 it's no longer a dep of allmydata-tahoe[1] but it may be
> > > useful for someone else maintaining a python project with unit tests.

From alanians at telus.net  Mon Mar 19 19:31:01 2018
From: alanians at telus.net (Alan Ianson)
Date: Mon, 19 Mar 2018 12:31:01 -0700
Subject: [Slackbuilds-users] physfs
Message-ID: <20180319123101.55e6d620b7ca22017c190430@telus.net>

On Mon, 19 Mar 2018 10:16:28 +0100
Franzen <slackbuilds at schoepfer.info> wrote:

> Hi,
> 
> i've updated physfs to 3.0.1:
> https://git.slackbuilds.org/slackbuilds/plain/libraries/physfs/physfs.SlackBuild?id=56e84de9a57f58850f7a3b6c4fabaab9ce3d0769
> 
> In case someone maintainers want to check, the following builds
> depend on physfs:

That's great. I'll try with these.. :)

> d1x-rebirth
> d2x-rebirth


From alik at ejik.org  Mon Mar 19 22:56:37 2018
From: alik at ejik.org (Alexander Verbovetsky)
Date: Tue, 20 Mar 2018 01:56:37 +0300
Subject: [Slackbuilds-users] ARM download links and the syncthing
 slackbuild.
In-Reply-To: <20180319105817.a7033b040c2d9efd8e526a81@ythogtha.org>
References: <20180319105817.a7033b040c2d9efd8e526a81@ythogtha.org>
Message-ID: <1521500197.3199343.1308900296.02B67FEC@webmail.messagingengine.com>

Hello,

On Mon, Mar 19, 2018, at 12:58, Ythogtha wrote:
> today I want to ask for a optional change in the .info files of the
> slackbuilds.  The problem is for slackbuilds with specific download
> links for non-x86 targets.  There are already the DOWNLOAD_x86_64 and
> MD5SUM_x86_64 lines for packages that have a different source file for
> x86 and x86_64.

> Granted, today, I know only of one slackbuild with this specific
> issue, syncthing, but that should make it easier to allow for an
> optional way to handle ARM platforms in the future, should we want to
> do it.

vivaldi and vivaldi-codecs-ffmpeg-extra are in the same situation. For
the moment, I provide the ARM download links in README.

Best regards,
Alexander

From ricardo at palmtx.com.ar  Tue Mar 20 02:31:34 2018
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Mon, 19 Mar 2018 23:31:34 -0300
Subject: [Slackbuilds-users] Taking over maintainership of git-cola and
 collectd
Message-ID: <201803192331.34716.ricardo@palmtx.com.ar>

Hi admins,

I just submitted slackbuilds for collectd and git-cola, taking over 
maintainership from Lionel Young and Andrew Rowland respectively.

Let me know if I should nag them to confirm on the list.

Re: collectd, I just realized that I submitted the exact same version of 
collectd as in SBo instead of my newer version :/

I'll submit an update in the next few days if SBo admins are OK with my take 
over.

Thanks!
-- 
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

From chris.willing at linux.com  Tue Mar 20 05:20:45 2018
From: chris.willing at linux.com (Christoph Willing)
Date: Tue, 20 Mar 2018 15:20:45 +1000
Subject: [Slackbuilds-users] Retroshare do not work Slackware.
In-Reply-To: <CA+da1oqR_YS1pn1RifaYv5r4BOYGJEzNA_WqPYnFiZ-S-uzt_g@mail.gmail.com>
References: <CAK9Umy+nXU6Nd6NEdqt-MQ62Jb=D9Exe=Koi0thw-oEOTyYGZg@mail.gmail.com>
 <CAPsDuS4HjFqUTSx1u_gcmWY1gZF5uh=5XKz=4H1HqcuTCtjZ_w@mail.gmail.com>
 <CA+da1orA8+L=hbHpPU5obMb=Brdy9g1VAAyBpRCTWNdX2NKPLw@mail.gmail.com>
 <CAPsDuS4SKL2z7vzk1cRgZhaRAFy+p3uD6bwLt9SKLr_-9PpAAw@mail.gmail.com>
 <CA+da1ooGngV8oLkxqGSWMX4B3WAC-kov7qQS-ceF3sUeMsTQvA@mail.gmail.com>
 <135d24bb-91e8-bf8f-cc71-8bc0cf0d44c2@iinet.net.au>
 <CA+da1opzLQpCkq4j5WdTTe1JgdRseQkhSj9rq0H8Uobz08PFqQ@mail.gmail.com>
 <CA+da1oqR_YS1pn1RifaYv5r4BOYGJEzNA_WqPYnFiZ-S-uzt_g@mail.gmail.com>
Message-ID: <e190b5c2-3112-fcec-8dc8-33b0fcc00e8e@linux.com>

On 20/03/18 00:58, Ozan T?rky?lmaz wrote:
> 2018-03-15 0:01 GMT+05:00 Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com
>
> 
> I have prepared a legacy package for libupnp. I got retroshare
> complining with it. It's not possible to use it with libupnp package.
> I work on it if it is possible for not conflicting with libunpnp
> 

A non-conflicting libupnp-legacy can be made by specifying a different
location for include & lib files e.g.
./configure \
   --prefix=/usr \
   --libdir=/usr/lib${LIBDIRSUFFIX}/libupnp-legacy \
   --includedir=/usr/include/libupnp-legacy \
   ...

Then rename & relocate the .pc file after make install:
  mv $PKG/usr/lib${LIBDIRSUFFIX}/libupnp-legacy/pkgconfig/libupnp.pc
$PKG/usr/lib${LIBDIRSUFFIX}/pkgconfig/libupnp-legacy.pc

After that, libupnp & libupnp-legacy should not conflict (at least no
files will be overwritten).

The different include & lib locations mean that SlackBuilds using
libupnp-legacy need slight modification to search those new locations. I
have built both retroshare and linphone using libupnp-legacy described
above after making the following alterations:

for network/retroshare:
diff --git a/network/retroshare/patch-libupnp-legacy.diff
b/network/retroshare/patch-libupnp-legacy.diff
new file mode 100644
index 0000000000..ad1266ae6b
--- /dev/null
+++ b/network/retroshare/patch-libupnp-legacy.diff
@@ -0,0 +1,19 @@
+--- libretroshare/src/libretroshare.pro.orig   2017-08-04
05:29:52.000000000 +1000
++++ libretroshare/src/libretroshare.pro        2018-03-20
11:37:57.906638456 +1000
+@@ -183,14 +183,14 @@
+     CONFIG += upnp_libupnp
+
+       # Check if the systems libupnp has been Debian-patched
+-      system(grep -E 'char[[:space:]]+PublisherUrl'
/usr/include/upnp/upnp.h >/dev/null 2>&1) {
++      system(grep -E 'char[[:space:]]+PublisherUrl'
/usr/include/libupnp-legacy/upnp/upnp.h >/dev/null 2>&1) {
+               # Normal libupnp
+       } else {
+               # Patched libupnp or new unreleased version
+               DEFINES *= PATCHED_LIBUPNP
+       }
+
+-      PKGCONFIG *= libssl libupnp
++      PKGCONFIG *= libssl libupnp-legacy
+       PKGCONFIG *= libcrypto zlib
+       LIBS *= -lpthread -ldl
+ }
diff --git a/network/retroshare/retroshare.SlackBuild
b/network/retroshare/retroshare.SlackBuild
index 672e8622ba..1c2440df58 100644
--- a/network/retroshare/retroshare.SlackBuild
+++ b/network/retroshare/retroshare.SlackBuild
@@ -19,7 +19,7 @@

 PRGNAM=retroshare
 VERSION=${VERSION:-0.6.3}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2}
 TAG=${TAG:-_SBo}

 SRCNAM=RetroShare
@@ -54,6 +54,8 @@ rm -rf $SRCNAM-$VERSION
 tar xvf $CWD/$SRCNAM-$VERSION.tar.gz
 cd $SRCNAM-$VERSION

+patch -p0 < $CWD/patch-libupnp-legacy.diff
+
 chown -R root:root .
 find -L . \
  \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
@@ -61,7 +63,7 @@ find -L . \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

-qmake PREFIX=/usr LIB_DIR=/usr/lib${LIBDIRSUFFIX} "CONFIG-=debug"
"CONFIG+=release"
+qmake PREFIX=/usr LIB_DIR=/usr/lib${LIBDIRSUFFIX} "CONFIG-=debug"
"CONFIG+=release" "INCLUDEPATH+=/usr/include/libupnp-legacy"
 make
 make INSTALL_ROOT=${PKG} install

diff --git a/network/retroshare/retroshare.info
b/network/retroshare/retroshare.info
index ed8e937fa5..0f697a6237 100644
--- a/network/retroshare/retroshare.info
+++ b/network/retroshare/retroshare.info
@@ -5,6 +5,6 @@
DOWNLOAD="https://github.com/RetroShare/RetroShare/archive/v0.6.3/RetroShare-0.6
 MD5SUM="9cb22e4cc5a11e043601795eb9a175cc"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES="libmicrohttpd libupnp speex protobuf sqlcipher"
+REQUIRES="libmicrohttpd libupnp-legacy speex protobuf sqlcipher"
 MAINTAINER="Alan Aversa"
 EMAIL="aveNOrsa at email.ariSPAMzona.edu"


and for network/linphone:
diff --git a/network/linphone/linphone.SlackBuild
b/network/linphone/linphone.SlackBuild
index 07eab0096e..9b4e26bedb 100644
--- a/network/linphone/linphone.SlackBuild
+++ b/network/linphone/linphone.SlackBuild
@@ -107,6 +107,8 @@ mv $MOD2SRCDIRNAME $MOD2DIRNAME
 sed -i 's|ms_message("Mediastreamer2 factory " MEDIASTREAMER_VERSION "
(git: " MS2_GIT_VERSION ") initialized.");|ms_message("Mediastreamer2
factory " MEDIASTREAMER_VERSION "  initialized.");|'
$MOD2DIRNAME/src/base/msfactory.c
 touch coreapi/gitversion.h

+patch -p0 < $CWD/patch-libupnp-legacy.diff
+
 chown -R root:root .
 find -L . \
  \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
diff --git a/network/linphone/linphone.info b/network/linphone/linphone.info
index 6fabd351e6..65a8b9f9f2 100644
--- a/network/linphone/linphone.info
+++ b/network/linphone/linphone.info
@@ -9,6 +9,6 @@ MD5SUM="8292dbaa0a5d0a448dcbbee125e947e4 \
         15b8b129a922180855d04d58cdd08d43"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES="bctoolbox belle-sip bzrtp ffmpeg libsrtp libupnp mbedtls speex"
+REQUIRES="bctoolbox belle-sip bzrtp ffmpeg libsrtp libupnp-legacy
mbedtls speex"
 MAINTAINER="Euan Thoms"
 EMAIL="euan at potensol dot com"
diff --git a/network/linphone/patch-libupnp-legacy.diff
b/network/linphone/patch-libupnp-legacy.diff
new file mode 100644
index 0000000000..881dbe8ec5
--- /dev/null
+++ b/network/linphone/patch-libupnp-legacy.diff
@@ -0,0 +1,65 @@
+--- configure.ac.orig  2017-06-29 19:20:47.000000000 +1000
++++ configure.ac       2018-03-20 10:13:48.325666257 +1000
+@@ -248,7 +248,7 @@
+       [build_tools=check]
+ )
+
+-dnl check for installed version of libupnp
++dnl check for installed version of libupnp-legacy
+ AC_ARG_ENABLE(upnp,
+       [AS_HELP_STRING([--disable-upnp], [Disable uPnP support])],
+       [case "${enableval}" in
+@@ -260,14 +260,14 @@
+ )
+
+ if test "$build_upnp" != "false" ; then
+-      PKG_CHECK_MODULES([LIBUPNP], [libupnp],
+-              [if  pkg-config --atleast-version=1.6 "libupnp < 1.7"; then
++      PKG_CHECK_MODULES([LIBUPNP], [libupnp-legacy],
++              [if  pkg-config --atleast-version=1.6 "libupnp-legacy <
1.7"; then
+                       build_upnp=true
+               else
+-                      AC_MSG_ERROR([libupnp >= 1.6 < 1.5 required.])
++                      AC_MSG_ERROR([libupnp-legacy >= 1.6 < 1.5
required.])
+               fi],
+               [if test "$build_upnp" == "true" ; then
+-                      AC_MSG_ERROR([libupnp not found.])
++                      AC_MSG_ERROR([libupnp-legacy not found.])
+               else
+                       build_upnp=false
+               fi]
+--- mediastreamer2/configure.ac.orig   2017-06-23 18:52:57.000000000 +1000
++++ mediastreamer2/configure.ac        2018-03-20 10:15:18.488139686 +1000
+@@ -704,7 +704,7 @@
+       AC_SUBST(SPANDSP_LIBS)
+ fi
+
+-dnl check for installed version of libupnp
++dnl check for installed version of libupnp-legacy
+ AC_ARG_ENABLE(upnp,
+       [AS_HELP_STRING([--disable-upnp], [Disable uPnP support])],
+       [case "${enableval}" in
+@@ -716,8 +716,8 @@
+ )
+
+ if test "$build_upnp" != "false" ; then
+-      PKG_CHECK_MODULES([LIBUPNP], [libupnp],
+-              [if  pkg-config --atleast-version=1.6 "libupnp < 1.7"; then
++      PKG_CHECK_MODULES([LIBUPNP], [libupnp-legacy],
++              [if  pkg-config --atleast-version=1.6 "libupnp-legacy <
1.7"; then
+                       build_upnp=true
+                       old_CFLAGS="$CFLAGS"
+                       CFLAGS="$CFLAGS $LIBUPNP_CFLAGS -Werror
-Wno-error=unused-variable"
+@@ -730,10 +730,10 @@
+                       AC_DEFINE(USE_PATCHED_UPNP, 1, [Define if upnp
is patched]))
+                       CFLAGS="$old_CFLAGS"
+               else
+-                      AC_MSG_ERROR([libupnp >= 1.6 < 1.5 required.])
++                      AC_MSG_ERROR([libupnp-legacy >= 1.6 < 1.5
required.])
+               fi],
+               [if test "$build_upnp" == "true" ; then
+-                      AC_MSG_ERROR([libupnp not found.])
++                      AC_MSG_ERROR([libupnp-legacy not found.])
+               else
+                       build_upnp=false
+               fi]



From s.arcus at open-t.co.uk  Tue Mar 20 07:27:23 2018
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Tue, 20 Mar 2018 07:27:23 +0000
Subject: [Slackbuilds-users] Lighttpd README.SLACKWARE could do with amending
Message-ID: <9aa8e17d-a6ae-e2c9-6d7f-2cc6d9023ca9@open-t.co.uk>

I think the README.SLACKWARE file bundled with Lighttpd SBo scripts 
could do with a few amendments as there have been some changes:

1. The procedure to configure fastcgi in the current Lighttpd involves 
uncommenting the relevant line in /etc/lighttpd/modules.conf and then 
finishing off the configuration in /etc/lighttpd/conf.d/fastcgi.conf

2. The default location for php.ini in Slackware now is in /etc/php.ini 
(I think it used to be in /etc/httpd) - and Lighttpd seems to work fine 
if it is left there

Best regards

From matteo.bernardini at gmail.com  Tue Mar 20 07:46:58 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 20 Mar 2018 08:46:58 +0100
Subject: [Slackbuilds-users] Lighttpd README.SLACKWARE could do with
 amending
In-Reply-To: <9aa8e17d-a6ae-e2c9-6d7f-2cc6d9023ca9@open-t.co.uk>
References: <9aa8e17d-a6ae-e2c9-6d7f-2cc6d9023ca9@open-t.co.uk>
Message-ID: <CAPsDuS7smbJ4uHK767AF3pc4M0mi=U6NcrcCv8JYAcQZsr_joQ@mail.gmail.com>

2018-03-20 8:27 GMT+01:00 Sebastian Arcus via SlackBuilds-users
<slackbuilds-users at slackbuilds.org>:
> I think the README.SLACKWARE file bundled with Lighttpd SBo scripts could do
> with a few amendments as there have been some changes:
>
> 1. The procedure to configure fastcgi in the current Lighttpd involves
> uncommenting the relevant line in /etc/lighttpd/modules.conf and then
> finishing off the configuration in /etc/lighttpd/conf.d/fastcgi.conf
>
> 2. The default location for php.ini in Slackware now is in /etc/php.ini (I
> think it used to be in /etc/httpd) - and Lighttpd seems to work fine if it
> is left there

thanks Sebastian! I adapted the text to comply with the new
conventions in my branch.

Matteo

From s.arcus at open-t.co.uk  Tue Mar 20 08:02:02 2018
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Tue, 20 Mar 2018 08:02:02 +0000
Subject: [Slackbuilds-users] Lighttpd README.SLACKWARE could do with
 amending
In-Reply-To: <CAPsDuS7smbJ4uHK767AF3pc4M0mi=U6NcrcCv8JYAcQZsr_joQ@mail.gmail.com>
References: <9aa8e17d-a6ae-e2c9-6d7f-2cc6d9023ca9@open-t.co.uk>
 <CAPsDuS7smbJ4uHK767AF3pc4M0mi=U6NcrcCv8JYAcQZsr_joQ@mail.gmail.com>
Message-ID: <71d1b46c-532f-a820-bb03-d4961db4d3b6@open-t.co.uk>

On 20/03/18 07:46, Matteo Bernardini wrote:
> 2018-03-20 8:27 GMT+01:00 Sebastian Arcus via SlackBuilds-users
> <slackbuilds-users at slackbuilds.org>:
>> I think the README.SLACKWARE file bundled with Lighttpd SBo scripts could do
>> with a few amendments as there have been some changes:
>>
>> 1. The procedure to configure fastcgi in the current Lighttpd involves
>> uncommenting the relevant line in /etc/lighttpd/modules.conf and then
>> finishing off the configuration in /etc/lighttpd/conf.d/fastcgi.conf
>>
>> 2. The default location for php.ini in Slackware now is in /etc/php.ini (I
>> think it used to be in /etc/httpd) - and Lighttpd seems to work fine if it
>> is left there
> 
> thanks Sebastian! I adapted the text to comply with the new
> conventions in my branch.

Thank you Matteo

From atelszewski at gmail.com  Tue Mar 20 13:59:15 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 20 Mar 2018 14:59:15 +0100
Subject: [Slackbuilds-users] Extend FAQ for UID/GID
Message-ID: <eb60f89f-66ca-2910-cca1-d6863f3db2c4@gmail.com>

Hi,

"13. Do you keep a list of non-standard uid and gid numbers that we 
should use in our scripts?"

Could this point have somewhere words "group" and "user" added?
It took me a minute to think that I have to look for "UID" or "GID" to 
find the relevant info.

Thanks!

-- 
Best regards / Pozdrawiam,
Andrzej Telszewski

From slackph at posteo.de  Tue Mar 20 14:21:11 2018
From: slackph at posteo.de (Philip Lacroix)
Date: Tue, 20 Mar 2018 15:21:11 +0100
Subject: [Slackbuilds-users] Bottle slackbuild
Message-ID: <179190fae13103dfc9478348f3b99c06@posteo.de>

Hi All

A few days ago I received an e-mail (off list) with the above title, but
I inadvertently deleted it along with spam before reading it. Whoever
wrote the original e-mail is invited to send it to me once again.

Sorry for the inconvenience.

Cheers
Philip

From arkadiusz at drabczyk.org  Tue Mar 20 19:46:24 2018
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Tue, 20 Mar 2018 20:46:24 +0100
Subject: [Slackbuilds-users] system/lsyncd requires Lua 5.2
Message-ID: <20180320194624.GA18699@comp.lan>

A new release of lsyncd requires at least Lua 5.2, in ChangeLog
https://github.com/axkibe/lsyncd/blob/master/ChangeLog it says:

change: needing now at least Lua 5.2 (Lua 5.1 no longer supported, Lua5.3 supported)

We used to have Lua 5.2 but it was removed in commit 9389d02 'until a
working way to manage multiple lua versions in the system is
provided'.  Moreover, development/lua README says:

"This package is for the version 5.1.x of lua, the one compatible with
the software that needs lua on slackbuilds.org."

Lua 5.1 line is really quite old, the oldest release was on 17 Feb
2012 according to this site https://www.lua.org/versions.html.  I
counted 66 packages that require lua:

find . -name "*.info" | xargs grep "^REQUIRES.*\blua\b" | wc -l

It would require a lot of manual work to check if all of these
packages could work with Lua 5.2.  Should I just wait and explain that
system/lsyncd would not be upgraded until Lua 5.2 becomes the default?

-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From matteo.bernardini at gmail.com  Tue Mar 20 20:11:35 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 20 Mar 2018 21:11:35 +0100
Subject: [Slackbuilds-users] system/lsyncd requires Lua 5.2
In-Reply-To: <20180320194624.GA18699@comp.lan>
References: <20180320194624.GA18699@comp.lan>
Message-ID: <CAPsDuS4hPVLjUsHyX9beyvy=6DPBgrURnDF3QRx-6DgjADuE_A@mail.gmail.com>

2018-03-20 20:46 GMT+01:00 Arkadiusz Drabczyk <arkadiusz at drabczyk.org>:
> A new release of lsyncd requires at least Lua 5.2, in ChangeLog
> https://github.com/axkibe/lsyncd/blob/master/ChangeLog it says:
>
> change: needing now at least Lua 5.2 (Lua 5.1 no longer supported, Lua5.3 supported)
>
> We used to have Lua 5.2 but it was removed in commit 9389d02 'until a
> working way to manage multiple lua versions in the system is
> provided'.  Moreover, development/lua README says:
>
> "This package is for the version 5.1.x of lua, the one compatible with
> the software that needs lua on slackbuilds.org."
>
> Lua 5.1 line is really quite old, the oldest release was on 17 Feb
> 2012 according to this site https://www.lua.org/versions.html.  I
> counted 66 packages that require lua:
>
> find . -name "*.info" | xargs grep "^REQUIRES.*\blua\b" | wc -l
>
> It would require a lot of manual work to check if all of these
> packages could work with Lua 5.2.  Should I just wait and explain that
> system/lsyncd would not be upgraded until Lua 5.2 becomes the default?

I don't think that lua will become the default, as many scripts still
want lua-5.1.x.
the ideal should be to have versioned versions of lua (like lua51,
lua52, lua53, etc.) all parallel-installable together so that whatever
needs one specific version could use it but this is not made easy by
the upstream lua developers.
if you (or whoever else) feel like to submit a new lua52.SlackBuild,
as a dependency of lsyncd, that will be parallel installable with the
lua we have, you are welcome: if you want/need you can also modify the
lua.SlackBuild that we have in our repository (you can even take
maintainership, if you prefer), taken that it will still play fine
with what we have in our repository.

Matteo

From ricardo at palmtx.com.ar  Tue Mar 20 20:58:03 2018
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Tue, 20 Mar 2018 17:58:03 -0300
Subject: [Slackbuilds-users] Taking over maintainership of git-cola and
 collectd
In-Reply-To: <201803192331.34716.ricardo@palmtx.com.ar>
References: <201803192331.34716.ricardo@palmtx.com.ar>
Message-ID: <201803201758.03967.ricardo@palmtx.com.ar>

I'm also taking geoipupdate from Oleg A. Deordiev, I'll submit an update 
tonight.

El Lunes 19/03/2018 a las 23:31, Ricardo J. Barberis escribi?:
> Hi admins,
>
> I just submitted slackbuilds for collectd and git-cola, taking over
> maintainership from Lionel Young and Andrew Rowland respectively.
>
> Let me know if I should nag them to confirm on the list.
>
> Re: collectd, I just realized that I submitted the exact same version of
> collectd as in SBo instead of my newer version :/
>
> I'll submit an update in the next few days if SBo admins are OK with my
> take over.
>
> Thanks!
-- 
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

From arkadiusz at drabczyk.org  Tue Mar 20 21:03:31 2018
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Tue, 20 Mar 2018 22:03:31 +0100
Subject: [Slackbuilds-users] system/lsyncd requires Lua 5.2
In-Reply-To: <CAPsDuS4hPVLjUsHyX9beyvy=6DPBgrURnDF3QRx-6DgjADuE_A@mail.gmail.com>
References: <20180320194624.GA18699@comp.lan>
 <CAPsDuS4hPVLjUsHyX9beyvy=6DPBgrURnDF3QRx-6DgjADuE_A@mail.gmail.com>
Message-ID: <20180320210331.GA11460@comp.lan>

On Tue, Mar 20, 2018 at 09:11:35PM +0100, Matteo Bernardini wrote:
> 2018-03-20 20:46 GMT+01:00 Arkadiusz Drabczyk <arkadiusz at drabczyk.org>:
> > Lua 5.1 line is really quite old, the oldest release was on 17 Feb
> > 2012 according to this site https://www.lua.org/versions.html.  I
> > counted 66 packages that require lua:
> >
> > find . -name "*.info" | xargs grep "^REQUIRES.*\blua\b" | wc -l
> >
> > It would require a lot of manual work to check if all of these
> > packages could work with Lua 5.2.  Should I just wait and explain that
> > system/lsyncd would not be upgraded until Lua 5.2 becomes the default?
> 
> I don't think that lua will become the default, as many scripts still
> want lua-5.1.x.
> the ideal should be to have versioned versions of lua (like lua51,
> lua52, lua53, etc.) all parallel-installable together so that whatever
> needs one specific version could use it but this is not made easy by
> the upstream lua developers.

Why isn't this?  What's the difference between Lua and, say, Python in
this regard?
-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From atelszewski at gmail.com  Tue Mar 20 21:23:02 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 20 Mar 2018 22:23:02 +0100
Subject: [Slackbuilds-users] Invoicing application recommendation
Message-ID: <b473048f-babd-6a8a-d946-6d8d2cb16139@gmail.com>

Hi,

Can anyone suggest an invoicing application?

Only something that you use personally and that works well.
Preferably no Java, web based is completely out of scope.

Preferably the application should have single functionality: making 
invoices, keeping clients and history.

Thanks!

-- 
Best regards / Pozdrawiam,
Andrzej Telszewski

From rob0 at slackbuilds.org  Thu Mar 22 04:39:08 2018
From: rob0 at slackbuilds.org (Rob McGee)
Date: Wed, 21 Mar 2018 23:39:08 -0500
Subject: [Slackbuilds-users] Today's DMARC debacle
In-Reply-To: <20180318202004.GC2515@harrier.slackbuilds.org>
References: <20180318202004.GC2515@harrier.slackbuilds.org>
Message-ID: <20180322043907.GC5126@harrier.slackbuilds.org>

Some of you might not have seen this because your list delivery was 
suspended.  We think we have all the subscribers reenabled now.

The "fix" has been implemented and confirmed to work.  "Fix" is the 
wrong word; it is a workaround for the shortcomings of the DMARC 
protocol.  Our list was fine, but we had to break it in case some 
other poster gets the same silly idea to play with DMARC.

If you missed anything from 2018-03-18 11:47 UTC to now, here's the
link to the archives:

https://lists.slackbuilds.org/pipermail/slackbuilds-users/2018-March/thread.html

On Sun, Mar 18, 2018 at 20:20 UTC, I wrote:
> Today a poster from a domain which published a DMARC "p=reject" 
> policy posted to our mailing list.  Either his DMARC record is new, 
> or gmail just started enforcing DMARC, and so, unseen by all our 
> numerous gmail/googlemail and Google Apps subscribers, you were 
> kicked off our list.
> 
> Yes, it's stupid.  DMARC allows third/fourth parties to do this 
> denial of service.  Mailing lists since forever have used the 
> original sender's "From:" header, but the list server's envelope 
> sender.  DMARC looks at the header, not the envelope.
> 
> But, as with so many things, we are stuck with stupid stuff.
> 
> GNU Mailman already has a workaround for the problem: it looks up 
> DMARC for the poster's domain, and if a "p=reject" is published, the 
> From header is rewritten.  Yay, so you don't know who it was from.
> 
> (Another workaround is to simply disallow posts from such domains.)
> 
> Anyway, I'm working on the first workaround, and the poster who 
> triggered all this is temporarily blocked from posting.
> 
> We have placed the list on emergency moderation mode for now.  
> Please, no more posts about this until I get it resolved.  I will 
> reply here when it is.
> 
> I'm sorry for the inconvenience.  I am sorry that DMARC exists.
> 
> Fortunately it was only the posts (two) from this poster which caused 
> all the havoc.  Every subscriber who was removed from the list should 
> have received their notification of removal.  The problem was not a 
> matter of gmail not accepting mail from us; only that the DMARC 
> perpetrator was listed in the From: header.  Not a factor for the 
> removal notification mails from Mailman.

-- 
    Rob McGee - /dev/rob0 - rob0 at slackbuilds.org

From gen-bch at useyouresp.org.uk  Thu Mar 22 08:34:33 2018
From: gen-bch at useyouresp.org.uk (Habs)
Date: Thu, 22 Mar 2018 08:34:33 +0000 (GMT)
Subject: [Slackbuilds-users] Today's DMARC debacle
In-Reply-To: <20180322043907.GC5126@harrier.slackbuilds.org>
References: <20180318202004.GC2515@harrier.slackbuilds.org>
 <20180322043907.GC5126@harrier.slackbuilds.org>
Message-ID: <alpine.LNX.2.20.1803220826420.1573@qi6920rn.ybpnyqbznva>


Hello List, Rob McGee

On Wed, 21 Mar 2018, Rob McGee wrote:

> Some of you might not have seen this because your list delivery was
> suspended.  We think we have all the subscribers reenabled now.
>
> The "fix" has been implemented and confirmed to work.  "Fix" is the
> wrong word; it is a workaround for the shortcomings of the DMARC
> protocol.  Our list was fine, but we had to break it in case some
> other poster gets the same silly idea to play with DMARC.
>


Does DMARC have to be specifically setup by a domain admin ? i.e. it can't 
just be inadvertently turned on.

I presume it does based on what I read briefly, about adding entries into 
the domain records etc. I have to admit until I read about it on this list 
I was almost fully clueless as to what DMARC was (acronyms to the ignorant 
and all that).

Habs

--- Sent using Alpine/Pine MUA ---

From rshepard at appl-ecosys.com  Thu Mar 22 13:42:13 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 22 Mar 2018 06:42:13 -0700 (PDT)
Subject: [Slackbuilds-users] Identifying users of a library
Message-ID: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>

   I need to upgrade wxPython yet have applications that depend on wxGTK+ so
I want to learn which installed applicatons depend on wxGTK+2 and wxGTK+3.
Aucacity depends on the latter, but I don't know which others do nor which
applications require wxGTK+2.

   Reading the man pages for installpkg and upgradepkg I see no options for
finding this information using them. The tool, 'ldd,' displays the libraries
required by a nemed package; I want to display the applications dependent on
a named library.

   In the Red Hat and Debian worlds rpm and dpkg apparently have options to
do this, but I've not found a way in Slackware.

   Advice and suggestions needed.

Rich

From ricardo at palmtx.com.ar  Thu Mar 22 15:32:35 2018
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Thu, 22 Mar 2018 12:32:35 -0300
Subject: [Slackbuilds-users] Identifying users of a library
In-Reply-To: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
Message-ID: <201803221232.35334.ricardo@palmtx.com.ar>

El Jueves 22/03/2018 a las 10:42, Rich Shepard escribi?:
>    I need to upgrade wxPython yet have applications that depend on wxGTK+
> so I want to learn which installed applicatons depend on wxGTK+2 and
> wxGTK+3. Aucacity depends on the latter, but I don't know which others do
> nor which applications require wxGTK+2.
>
>    Reading the man pages for installpkg and upgradepkg I see no options for
> finding this information using them. The tool, 'ldd,' displays the
> libraries required by a nemed package; I want to display the applications
> dependent on a named library.
>
>    In the Red Hat and Debian worlds rpm and dpkg apparently have options to
> do this, but I've not found a way in Slackware.
>
>    Advice and suggestions needed.

Chek out these two threads, there are a few ideas in there:

https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-September/019942.html
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-June/014407.html

Cheers,
-- 
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

From ricardo at palmtx.com.ar  Thu Mar 22 15:43:24 2018
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Thu, 22 Mar 2018 12:43:24 -0300
Subject: [Slackbuilds-users] Identifying users of a library
In-Reply-To: <201803221232.35334.ricardo@palmtx.com.ar>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <201803221232.35334.ricardo@palmtx.com.ar>
Message-ID: <201803221243.24862.ricardo@palmtx.com.ar>

El Jueves 22/03/2018 a las 12:32, Ricardo J. Barberis escribi?:
> El Jueves 22/03/2018 a las 10:42, Rich Shepard escribi?:
> >    I need to upgrade wxPython yet have applications that depend on wxGTK+
> > so I want to learn which installed applicatons depend on wxGTK+2 and
> > wxGTK+3. Aucacity depends on the latter, but I don't know which others do
> > nor which applications require wxGTK+2.
> >
> >    Reading the man pages for installpkg and upgradepkg I see no options
> > for finding this information using them. The tool, 'ldd,' displays the
> > libraries required by a nemed package; I want to display the applications
> > dependent on a named library.
> >
> >    In the Red Hat and Debian worlds rpm and dpkg apparently have options
> > to do this, but I've not found a way in Slackware.
> >
> >    Advice and suggestions needed.
>
> Chek out these two threads, there are a few ideas in there:
>
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-September/019942.html
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-June/014407.html

Hoorex is mentioned in one of those threads, but there's also sbbdep:

https://slackbuilds.org/repository/14.2/system/sbbdep/
https://slackbuilds.org/repository/14.2/misc/hoorex/

Cheers,
-- 
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

From rshepard at appl-ecosys.com  Thu Mar 22 16:18:19 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 22 Mar 2018 09:18:19 -0700 (PDT)
Subject: [Slackbuilds-users] Identifying users of a library [RESOLVED]
In-Reply-To: <201803221243.24862.ricardo@palmtx.com.ar>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <201803221232.35334.ricardo@palmtx.com.ar>
 <201803221243.24862.ricardo@palmtx.com.ar>
Message-ID: <alpine.LNX.2.20.1803220916330.25233@salmo.appl-ecosys.com>

On Thu, 22 Mar 2018, Ricardo J. Barberis wrote:

>> Check out these two threads, there are a few ideas in there:
>>
>> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-September/019942.html
>> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-June/014407.html
>
> Hoorex is mentioned in one of those threads, but there's also sbbdep:
>
> https://slackbuilds.org/repository/14.2/system/sbbdep/
> https://slackbuilds.org/repository/14.2/misc/hoorex/

Ricardo,

   It must have been last September's thread that I recalled.

   Thanks very much for all this information. I'll look at both hoorex and
sbbdep and use one of them.

Best regards,

Rich

From rob0 at slackbuilds.org  Thu Mar 22 17:37:46 2018
From: rob0 at slackbuilds.org (Rob McGee)
Date: Thu, 22 Mar 2018 12:37:46 -0500
Subject: [Slackbuilds-users] Today's DMARC debacle
In-Reply-To: <alpine.LNX.2.20.1803220826420.1573@qi6920rn.ybpnyqbznva>
References: <20180318202004.GC2515@harrier.slackbuilds.org>
 <20180322043907.GC5126@harrier.slackbuilds.org>
 <alpine.LNX.2.20.1803220826420.1573@qi6920rn.ybpnyqbznva>
Message-ID: <20180322173746.GD5126@harrier.slackbuilds.org>

On Thu, Mar 22, 2018 at 08:34:33AM +0000, Habs wrote:
> Does DMARC have to be specifically setup by a domain admin ? i.e. 
> it can't just be inadvertently turned on.
> 
> I presume it does based on what I read briefly, about adding 
> entries into the domain records etc.

That's how it is done, so yes.  If your domain is delegated to 
someone else to manage the DNS, it's possible that a DMARC record 
could be added without you knowing it.  But if you control your own 
DNS, you'll only set a DMARC record specifically.

> I have to admit until I read 
> about it on this list I was almost fully clueless as to what
> DMARC was (acronyms to the ignorant and all that).

Mail stuff is an awful mess, and DMARC was one of the things to 
exacerbate the situation.

One thing we had to consider is that most of our subscribers use 
email providers, so DMARC is beyond their control.  We don't want 
them to be penalized because of lack of clue (or indeed, malice) at 
their email provider.
-- 
    Rob McGee - /dev/rob0 - rob0 at slackbuilds.org

From rshepard at appl-ecosys.com  Thu Mar 22 17:58:34 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 22 Mar 2018 10:58:34 -0700 (PDT)
Subject: [Slackbuilds-users] Today's DMARC debacle
In-Reply-To: <20180322173746.GD5126@harrier.slackbuilds.org>
References: <20180318202004.GC2515@harrier.slackbuilds.org>
 <20180322043907.GC5126@harrier.slackbuilds.org>
 <alpine.LNX.2.20.1803220826420.1573@qi6920rn.ybpnyqbznva>
 <20180322173746.GD5126@harrier.slackbuilds.org>
Message-ID: <alpine.LNX.2.20.1803221053310.25233@salmo.appl-ecosys.com>

On Thu, 22 Mar 2018, Rob McGee wrote:

> That's how it is done, so yes. If your domain is delegated to someone else
> to manage the DNS, it's possible that a DMARC record could be added
> without you knowing it. But if you control your own DNS, you'll only set a
> DMARC record specifically.
   ...
> One thing we had to consider is that most of our subscribers use email
> providers, so DMARC is beyond their control. We don't want them to be
> penalized because of lack of clue (or indeed, malice) at their email
> provider.

Hi Rob,

   I use the DNS servers at my domain registrar. Is there a way for me to
directly determine if they have added DMARC? I run postfix as the MTA so
mail doesn't go through them or anyone else. Therfore, is DMARC not an issue
for me?

   I have successfully implemented SPF on stmp here, but am still struggling
to get openDKIM working.

Regards,

Rich



From klaatu at mixedsignals.ml  Thu Mar 22 18:27:08 2018
From: klaatu at mixedsignals.ml (klaatu at mixedsignals.ml)
Date: Fri, 23 Mar 2018 07:27:08 +1300
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <alpine.LNX.2.20.1803220916330.25233@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <201803221232.35334.ricardo@palmtx.com.ar>
 <201803221243.24862.ricardo@palmtx.com.ar>
 <alpine.LNX.2.20.1803220916330.25233@salmo.appl-ecosys.com>
Message-ID: <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>

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
* [insert your favourite obscure Slackware/SBo script or app here]

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

From atelszewski at gmail.com  Thu Mar 22 18:39:12 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 22 Mar 2018 19:39:12 +0100
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <201803221232.35334.ricardo@palmtx.com.ar>
 <201803221243.24862.ricardo@palmtx.com.ar>
 <alpine.LNX.2.20.1803220916330.25233@salmo.appl-ecosys.com>
 <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
Message-ID: <1bf5f380-9e71-abc6-990b-9f32f0ae0db7@gmail.com>

On 22/03/18 19:27, klaatu at mixedsignals.ml wrote:
> 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
> * [insert your favourite obscure Slackware/SBo script or app here]
> 
> 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?
> 

Well, I can actually think of a reason this wouldn't be harmful ;-)
Sounds good.

-- 
Best regards / Pozdrawiam,
Andrzej Telszewski

From dave at dawoodfall.net  Thu Mar 22 19:00:43 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Thu, 22 Mar 2018 19:00:43 +0000
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <201803221232.35334.ricardo@palmtx.com.ar>
 <201803221243.24862.ricardo@palmtx.com.ar>
 <alpine.LNX.2.20.1803220916330.25233@salmo.appl-ecosys.com>
 <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
Message-ID: <20180322190043.GF9449@blackswan>

On Friday 23 March 2018 07:27,
klaatu at mixedsignals.ml <klaatu at 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
* mkslack :) 

>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
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/
>


From ricardo at palmtx.com.ar  Thu Mar 22 19:46:26 2018
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Thu, 22 Mar 2018 16:46:26 -0300
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <20180322190043.GF9449@blackswan>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
 <20180322190043.GF9449@blackswan>
Message-ID: <201803221646.26409.ricardo@palmtx.com.ar>

El Jueves 22/03/2018 a las 16:00, David Woodfall escribi?:
> On Friday 23 March 2018 07:27,
> klaatu at mixedsignals.ml <klaatu at 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 :)


> >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

From didier at slint.fr  Thu Mar 22 20:20:02 2018
From: didier at slint.fr (Didier Spaier)
Date: Thu, 22 Mar 2018 21:20:02 +0100
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <201803221646.26409.ricardo@palmtx.com.ar>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
 <20180322190043.GF9449@blackswan> <201803221646.26409.ricardo@palmtx.com.ar>
Message-ID: <66a50793-5d8e-ad9e-b600-4d0b86d267f5@slint.fr>

Hello,

>>> 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!

>>>* [insert your favourite obscure Slackware/SBo script or app here]
+=I use it
?=I never heard about it until today
*=not in SBo:
asbt?
depfinder *+
deb2tgz
findpkg
slapt-src *+
sourcery *+
slpkg
slapt-get *+
gslapt *+
spi *+
spkg+
netpkg * # Zenwalk
slackroll?
slack-utils?
slachlog?
sun?
salix-update-notifier *+
swun?

Probably others :D

Didier

From rshepard at appl-ecosys.com  Thu Mar 22 20:37:10 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 22 Mar 2018 13:37:10 -0700 (PDT)
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <201803221232.35334.ricardo@palmtx.com.ar>
 <201803221243.24862.ricardo@palmtx.com.ar>
 <alpine.LNX.2.20.1803220916330.25233@salmo.appl-ecosys.com>
 <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
Message-ID: <alpine.LNX.2.20.1803221335090.25233@salmo.appl-ecosys.com>

On Fri, 23 Mar 2018, klaatu at mixedsignals.ml wrote:

> 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:

Klattu,

   sbopkg -- use
   slackpkg+ -- use

   Hadn't known about the others before you listed them.

   As an SBo user I support the idea of putting all these in a Slackware
category.

Thanks,

Rich

From sbolokanov at abv.bg  Thu Mar 22 20:56:06 2018
From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvdGK4oCT0KHQtdCy0LDRgA==?= =?utf-8?B?0Yog0JHQvtC70L7QutCw0L3QvtCy0Yo=?=)
Date: Thu, 22 Mar 2018 22:56:06 +0200 (EET)
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <201803221232.35334.ricardo@palmtx.com.ar>
 <201803221243.24862.ricardo@palmtx.com.ar>
 <alpine.LNX.2.20.1803220916330.25233@salmo.appl-ecosys.com>
 <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
Message-ID: <1970023829.509799.1521752166223.JavaMail.apache@nm53.abv.bg>

 I would rather see a ln to a Slackware category, but keep them where they are.  Or maybe apply slackware keyword to all thouse packages, so they can show up  when one do a search for 'slackware'. 
-- ?. ?. ??????????

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180322/21d549e7/attachment.html>

From martijn at inlv.org  Thu Mar 22 21:09:05 2018
From: martijn at inlv.org (Martijn Dekker)
Date: Thu, 22 Mar 2018 22:09:05 +0100
Subject: [Slackbuilds-users] Today's DMARC debacle
In-Reply-To: <20180318202004.GC2515@harrier.slackbuilds.org>
References: <20180318202004.GC2515@harrier.slackbuilds.org>
Message-ID: <825b9137-d483-e335-a2c7-193a039937ff@inlv.org>

Op 18-03-18 om 21:20 schreef Rob McGee:
> GNU Mailman already has a workaround for the problem: it looks up 
> DMARC for the poster's domain, and if a "p=reject" is published, the 
> From header is rewritten.  Yay, so you don't know who it was from.

Mailman keeps the free-form name, though, and moves the original email
address to the Cc header.

- M.

From slackware at lemintown.eu  Thu Mar 22 22:54:01 2018
From: slackware at lemintown.eu (Brian)
Date: Thu, 22 Mar 2018 23:54:01 +0100
Subject: [Slackbuilds-users] Chromaprint 1.4.3 fails to build with optionnal
 ffmpeg 3.2.4
Message-ID: <5ce7ab0d-3994-6564-3080-380cc815242e@lemintown.eu>

Hello,

Chromaprint will automatically build the fpcalc package thanks to ffmpeg 
if it gets detected by the slackbuild script.
My ffmpeg package was built from SBo with every optional package 
supported. Building chromaprint without ffmpeg support worked.

Brian

---------------------

src/cmd/CMakeFiles/fpcalc.dir/build.make:62: recipe for target 
'src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o' failed
make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1
CMakeFiles/Makefile2:245: recipe for target 
'src/cmd/CMakeFiles/fpcalc.dir/all' failed
make[1]: *** [src/cmd/CMakeFiles/fpcalc.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2


From bgrundy at gmail.com  Fri Mar 23 01:17:13 2018
From: bgrundy at gmail.com (Barry Grundy)
Date: Thu, 22 Mar 2018 21:17:13 -0400
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <201803221232.35334.ricardo@palmtx.com.ar>
 <201803221243.24862.ricardo@palmtx.com.ar>
 <alpine.LNX.2.20.1803220916330.25233@salmo.appl-ecosys.com>
 <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
Message-ID: <CAH74TFjBPCFMcbFH28TU-TxwX=cTxft2oZEBbX0O5-Aw2jzj=Q@mail.gmail.com>

On Thu, Mar 22, 2018 at 2:27 PM, <klaatu at mixedsignals.ml> wrote:

> 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
> * [insert your favourite obscure Slackware/SBo script or app here]
>
> 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?
>

Just my $.02, but I really like this idea.  It partially solves the "you
don't know what you don't know problem" with things like sboui and hoorex
(that I dearly love, but only recently discovered).

I've been thinking for awhile now about asking to add a category for
"Security" and related.  But I could'nt think of an obvious reason to make
it worth asking other than "it would be nice to have everything in one
pile".  A Slackware category makes sense and has obvious benefits.

-- 
----
Barry Grundy
bgrundy at gmail.com
bgrundy at linuxleo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180322/76028782/attachment-0001.html>

From matteo.bernardini at gmail.com  Fri Mar 23 06:16:55 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 23 Mar 2018 07:16:55 +0100
Subject: [Slackbuilds-users] Chromaprint 1.4.3 fails to build with
 optionnal ffmpeg 3.2.4
In-Reply-To: <5ce7ab0d-3994-6564-3080-380cc815242e@lemintown.eu>
References: <5ce7ab0d-3994-6564-3080-380cc815242e@lemintown.eu>
Message-ID: <CAPsDuS6MwntpdT50EHMxsr_Y9reyXs6JUPLwK_W4B49xyiUXUA@mail.gmail.com>

2018-03-22 23:54 GMT+01:00 Brian <slackware at lemintown.eu>:
> Hello,
>
> Chromaprint will automatically build the fpcalc package thanks to ffmpeg if
> it gets detected by the slackbuild script.
> My ffmpeg package was built from SBo with every optional package supported.
> Building chromaprint without ffmpeg support worked.
>
> Brian
>
> ---------------------
>
> src/cmd/CMakeFiles/fpcalc.dir/build.make:62: recipe for target
> 'src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o' failed
> make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1
> CMakeFiles/Makefile2:245: recipe for target
> 'src/cmd/CMakeFiles/fpcalc.dir/all' failed
> make[1]: *** [src/cmd/CMakeFiles/fpcalc.dir/all] Error 2
> Makefile:127: recipe for target 'all' failed
> make: *** [all] Error 2

Hi Brian,

I tested it and the build went fine here...
can you please post the full log somewhere line http://pastebin.com ?
I'm asking because the cause of the error is not visible in the lines
you posted.

Matteo

From slackware at lemintown.eu  Fri Mar 23 08:46:42 2018
From: slackware at lemintown.eu (Brian)
Date: Fri, 23 Mar 2018 09:46:42 +0100
Subject: [Slackbuilds-users] Chromaprint 1.4.3 fails to build with
 optionnal ffmpeg 3.2.4
In-Reply-To: <CAPsDuS6MwntpdT50EHMxsr_Y9reyXs6JUPLwK_W4B49xyiUXUA@mail.gmail.com>
References: <5ce7ab0d-3994-6564-3080-380cc815242e@lemintown.eu>
 <CAPsDuS6MwntpdT50EHMxsr_Y9reyXs6JUPLwK_W4B49xyiUXUA@mail.gmail.com>
Message-ID: <de2d2061-6d92-2b7f-8f9c-905d0b686e26@lemintown.eu>

On 23/03/2018 07:16, Matteo Bernardini wrote:
> 2018-03-22 23:54 GMT+01:00 Brian <slackware at lemintown.eu>:
>> Hello,
>>
>> Chromaprint will automatically build the fpcalc package thanks to ffmpeg if
>> it gets detected by the slackbuild script.
>> My ffmpeg package was built from SBo with every optional package supported.
>> Building chromaprint without ffmpeg support worked.
>>
>> Brian
>>
>> ---------------------
>>
>> src/cmd/CMakeFiles/fpcalc.dir/build.make:62: recipe for target
>> 'src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o' failed
>> make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1
>> CMakeFiles/Makefile2:245: recipe for target
>> 'src/cmd/CMakeFiles/fpcalc.dir/all' failed
>> make[1]: *** [src/cmd/CMakeFiles/fpcalc.dir/all] Error 2
>> Makefile:127: recipe for target 'all' failed
>> make: *** [all] Error 2
> Hi Brian,
>
> I tested it and the build went fine here...
> can you please post the full log somewhere line http://pastebin.com ?
> I'm asking because the cause of the error is not visible in the lines
> you posted.
>
> Matteo

Hi Matteo,

Sure, here's the full log: https://pastebin.com/0DvNhfCq

Brian


From matteo.bernardini at gmail.com  Fri Mar 23 09:17:22 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 23 Mar 2018 10:17:22 +0100
Subject: [Slackbuilds-users] Chromaprint 1.4.3 fails to build with
 optionnal ffmpeg 3.2.4
In-Reply-To: <de2d2061-6d92-2b7f-8f9c-905d0b686e26@lemintown.eu>
References: <5ce7ab0d-3994-6564-3080-380cc815242e@lemintown.eu>
 <CAPsDuS6MwntpdT50EHMxsr_Y9reyXs6JUPLwK_W4B49xyiUXUA@mail.gmail.com>
 <de2d2061-6d92-2b7f-8f9c-905d0b686e26@lemintown.eu>
Message-ID: <CAPsDuS7+wH+xxXWNBcShF0T-8mq3CC1N5beh-nxkcwqa1N=2pQ@mail.gmail.com>

2018-03-23 9:46 GMT+01:00 Brian <slackware at lemintown.eu>:
> Sure, here's the full log: https://pastebin.com/0DvNhfCq

I had a look at it: the errors seems to be these

In file included from /tmp/SBo/chromaprint-v1.4.3/src/cmd/fpcalc.cpp:7:0:
/tmp/SBo/chromaprint-v1.4.3/src/audio/ffmpeg_audio_reader.h:194:27:
error: ?avcodec_alloc_frame? was not declared in this scope
  m_frame = av_frame_alloc();
                           ^
In file included from /tmp/SBo/chromaprint-v1.4.3/src/cmd/fpcalc.cpp:7:0:
/tmp/SBo/chromaprint-v1.4.3/src/audio/ffmpeg_audio_reader.h: In member
function ?void chromaprint::FFmpegAudioReader::Close()?:
/tmp/SBo/chromaprint-v1.4.3/src/audio/ffmpeg_audio_reader.h:232:24:
error: ?avcodec_free_frame? was not declared in this scope
  av_frame_free(&m_frame);
                        ^

and that's strange, because I have ffmpeg-3.2.4 from SBo too installed
and I don't have those errors:
- are you sure you got that and not some other version?
- is anybody else experiencing the same errors as Brian building
chromaprint with ffmpeg installed?

Matteo

From willysr at slackbuilds.org  Sat Mar 24 00:27:45 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 24 Mar 2018 07:27:45 +0700
Subject: [Slackbuilds-users] Updates - 20180324.1
Message-ID: <99faf654-4efd-3257-c43b-a02c6f5fd916@slackbuilds.org>

Hi all,

Here's another big batch of updates. There are lots of updates in many
categories. perl-Moose is still in pending because it requires a new
version of perl-Devel-StackTrace so it will have to wait until next
public update. We have coordinated with the maintainer.

You might notice that we approved perl-Scalar-List-Utils, which is also
part of Slackware core packages (perl). David and Matteo has found a way
so that it doesn't replace any Slackware's file, so it got approved.

Sat Mar 24 00:01:07 UTC 2018
academic/WordNet: Switch homepage to https.
academic/amd: BUILD bump for SuiteSparse 5.2.0.
academic/btf: BUILD bump for SuiteSparse 5.2.0.
academic/camd: BUILD bump for SuiteSparse 5.2.0.
academic/ccolamd: BUILD bump for SuiteSparse 5.2.0.
academic/cholmod: Updated for version 3.0.12.
academic/colamd: BUILD bump for SuiteSparse 5.2.0.
academic/csparse: BUILD bump for SuiteSparse 5.2.0.
academic/cxsparse: BUILD bump for SuiteSparse 5.2.0.
academic/klu: Updated for version 1.3.9.
academic/ldl: BUILD bump for SuiteSparse 5.2.0.
academic/octave: Updated for version 4.2.2.
academic/rbio: BUILD bump for SuiteSparse 5.2.0.
academic/spqr: BUILD bump for SuiteSparse 5.2.0.
academic/suitesparseconfig: Updated for version 5.2.0.
academic/umfpack: BUILD bump for SuiteSparse 5.2.0.
audio/dssi-vst: Switch to https.
audio/ladspa-bs2b: Added (BS2B Library and Plugins).
audio/rosegarden: Switch to https.
audio/sonic-visualiser: Switch homepage to https.
audio/vamp-plugin-sdk: Switch homepage to https.
desktop/boston-icon-theme: Added (icon theme).
desktop/compton-conf: Updated for version 0.3.0.
desktop/enlightenment: Updated for version 0.22.2.
desktop/i3: Updated for version 4.15.
desktop/myGtkMenu: Update maintainer email.
desktop/oranchelo-icon-theme: Updated for version 0.7.6.5.
desktop/papirus-icon-theme: Added (icon theme).
desktop/rofi: Fixed homepage.
development/Sphinx: Updated for version 1.7.2.
development/apache-log4cxx: Fixed homepage.
development/apitrace: Update maintainer email.
development/diffoscope: Updated for version 92.
development/eclipse-cpp: Updated for version 4.7.3.
development/eclipse-java: Updated for version 4.7.3.
development/eclipse-jee: Updated for version 4.7.3.
development/envytools: Update maintainer email.
development/gisto: Switch homepage to https.
development/git-cola: Updated for version 3.0 + new maintainer.
development/google-webdesigner: Updated for version 3.0.0.0312.
development/guile-json: Update maintainer email.
development/hhvm: Updated for version 3.24.5
development/icecream: Updated for version 1.1.
development/jupyter-notebook: Updated for version 5.4.1.
development/kdesvn: Switch to i586 + new maintainer.
development/libretro-samples: Update maintainer email.
development/pkgconf: Update maintainer email.
development/rustup: Added (The Rust toolchain installer).
development/sdcc: Updated for version 3.7.0.
development/slibtool: Update maintainer email.
development/ucpp: Update maintainer email.
development/universal-ctags: Updated for version ec7b647
development/xdebug: Updated for version 2.5.5.
games/4do-libretro: Update maintainer email.
games/Craft-libretro: Update maintainer email.
games/Genesis-Plus-GX: Update maintainer email.
games/QuickNES-Core: Update maintainer email.
games/RetroArch: Update maintainer email.
games/SameBoy: Update maintainer email.
games/Tempus-Irae: Update maintainer email.
games/beetle-bsnes-libretro: Update maintainer email.
games/beetle-gba-libretro: Update maintainer email.
games/beetle-lynx-libretro: Update maintainer email.
games/beetle-ngp-libretro: Update maintainer email.
games/beetle-pce-fast-libretro: Update maintainer email.
games/beetle-pcfx-libretro: Update maintainer email.
games/beetle-psx-libretro: Update maintainer email.
games/beetle-saturn-libretro: Update maintainer email.
games/beetle-supergrafx-libretro: Update maintainer email.
games/beetle-vb-libretro: Update maintainer email.
games/beetle-wswan-libretro: Update maintainer email.
games/blastem-libretro: Update maintainer email.
games/blueMSX-libretro: Update maintainer email.
games/bnes-libretro: Update maintainer email.
games/bsnes-libretro: Update maintainer email.
games/bsnes-mercury: Update maintainer email.
games/dhewm3: Update maintainer email.
games/ecwolf: Update maintainer email.
games/exult: Update maintainer email.
games/fbalpha: Update maintainer email.
games/fmsx-libretro: Update maintainer email.
games/gambatte-libretro: Update maintainer email.
games/gpsp-libretro: Update maintainer email.
games/gw-libretro: Update maintainer email.
games/higan-libretro: Update maintainer email.
games/higan: Fixed homepage.
games/libretro-2048: Update maintainer email.
games/libretro-desmume: Update maintainer email.
games/libretro-fceumm: Update maintainer email.
games/libretro-handy: Update maintainer email.
games/libretro-lutro: Update maintainer email.
games/libretro-mgba: Update maintainer email.
games/libretro-ppsspp: Update maintainer email.
games/libretro-prboom: Update maintainer email.
games/libretro-reicast: Update maintainer email.
games/libretro-vecx: Update maintainer email.
games/libretro-yabause: Update maintainer email.
games/mame2000-libretro: Update maintainer email.
games/mame2010-libretro: Update maintainer email.
games/mame2014-libretro: Update maintainer email.
games/marathon-eternal-data: Update maintainer email.
games/marathon-evil-data: Update maintainer email.
games/marathon-red-data: Update maintainer email.
games/marathon-rubicon-data: Update maintainer email.
games/meteor-libretro: Update maintainer email.
games/mupen64plus-libretro: Update maintainer email.
games/nSide-libretro: Update maintainer email.
games/nestopia-libretro: Update maintainer email.
games/nuvie: Update maintainer email.
games/nxengine-libretro: Update maintainer email.
games/parallel-n64: Update maintainer email.
games/pcsx-rearmed: Update maintainer email.
games/pcsx2: Update maintainer email.
games/picodrive-libretro: Update maintainer email.
games/pinball: Update maintainer email.
games/pioneer: Update maintainer email.
games/prosystem-libretro: Update maintainer email.
games/scummvm-libretro: Update maintainer email.
games/snes9x-libretro: Update maintainer email.
games/snes9x2002: Update maintainer email.
games/snes9x2005: Update maintainer email.
games/snes9x2010: Update maintainer email.
games/solarus-quest-editor: Update maintainer email.
games/solarus: Update maintainer email.
games/stella-libretro: Update maintainer email.
games/tyrquake-libretro: Update maintainer email.
games/vba-next: Update maintainer email.
games/vbam-libretro: Update maintainer email.
games/virtualjaguar-libretro: Update maintainer email.
games/zelda-roth-se: Update maintainer email.
games/zsdx: Update maintainer email.
games/zsxd: Update maintainer email.
gis/gdal: Updated for version 2.2.4.
gis/josm: Switch homepage to https.
gis/mapnik: Switch to i586.
gis/pgrouting: Updated for version 2.6.0.
gis/pointcloud: Remove need for cunit dependency.
gis/polyline: Add Python 3 support.
gis/postgis: Script clean up.
gis/pyproj: Add Python 3 support.
gis/pyshp: Add Python 3 support.
gis/pyspatialite: Switch to i586.
gis/python-mapnik: Add Python 3 support.
gis/rasterio: Add Python 3 support.
graphics/FSPViewer: Added (spherical panorama viewer).
graphics/darktable: Updated for version 2.4.2.
graphics/feh: Update maintainer email.
graphics/graphite2: Update maintainer email.
graphics/gthumb: Fixed homepage.
graphics/leocad: Switch homepage to https.
graphics/leocad_pieces: Switch homepage to https.
graphics/vulkansdk: Updated for version 1.1.70.0.
ham/chirp: Switch homepage to https.
ham/klog: Switch homepage to https.
haskell/haskell-setlocale: Updated for version 1.0.0.6.
libraries/CoinMP: Update maintainer email.
libraries/efl: Updated for version 1.20.7.
libraries/hdf: Switch to i586.
libraries/hyphen: Update maintainer email.
libraries/imlib2: Updated for version 1.5.1.
libraries/libabw: Update maintainer email.
libraries/libbde: Updated for version 20170902.
libraries/libcdr: Update maintainer email.
libraries/libcmis: Update maintainer email.
libraries/libe-book: Update maintainer email.
libraries/libeot: Update maintainer email.
libraries/libepubgen: Update maintainer email.
libraries/libetonyek: Update maintainer email.
libraries/libexttextcat: Update maintainer email.
libraries/libfreehand: Update maintainer email.
libraries/libfvde: Updated for version 20180108.
libraries/libfwnt: Updated for version 20180117.
libraries/libfwsi: Updated for version 20171103.
libraries/libgltf: Update maintainer email.
libraries/libhoard: Switch back to http.
libraries/libhoard: Updated for version 3.12.
libraries/libixion: Update maintainer email.
libraries/liblangtag: Update maintainer email.
libraries/liblxi: Updated for version 1.12
libraries/libmsiecf: Updated for version 20170116.
libraries/libmspub: Update maintainer email.
libraries/libmwaw: Update maintainer email.
libraries/libolecf: Updated for version 20170825.
libraries/liborcus: Update maintainer email.
libraries/libpagemaker: Update maintainer email.
libraries/libqxp: Update maintainer email.
libraries/libsass: Updated for version 3.5.2.
libraries/libsmdev: Updated for version 20171112.
libraries/libsmraw: Updated for version 20180123.
libraries/libstaroffice: Update maintainer email.
libraries/libupnp-legacy: Added (Portable SDK for UPnP Devices).
libraries/libvshadow: Updated for version 20170902.
libraries/libwps: Update maintainer email.
libraries/libzmf: Update maintainer email.
libraries/lua-lpeg: Script clean up.
libraries/lua-mpack: Script clean up.
libraries/mdds: Update maintainer email.
libraries/msgpack-c: Script clean up.
libraries/netcdf: Updated for version 4.6.1.
libraries/physfs: Updated for version 3.0.1.
libraries/png++: Update maintainer email.
libraries/stfl: Add Python 3 support.
libraries/vdk: Added (Visual Development Kit).
libraries/webkit2gtk: Updated for version 2.20.0.
libraries/xerces-c: Fix download link.
libraries/zint: Added (Zint Barcode Generator).
misc/esniper: Update maintainer email.
misc/floating-IPS: Update maintainer email.
misc/grabc: Update maintainer email.
misc/langdrill: Added (language drill tests).
misc/lppf: Update maintainer email.
misc/xdelta3: Update maintainer email.
multimedia/devedeng: Update maintainer email.
multimedia/lightspark: Update maintainer email.
multimedia/obs-studio: Updated for version 21.1.1
multimedia/xvidcore: Updated for version 1.3.5.
network/Electrum: Updated for version 3.1.1.
network/PaleMoon: Updated for version 27.8.2.
network/basilisk: Updated for version 2018.03.21.
network/c-toxcore: Updated for version 0.2.1.
network/deluge: Switch homepage to https.
network/ekiga: Switch homepage to https.
network/geoipupdate: Updated for version 2.5.0.
network/lighttpd: Adapt README.SLACKWARE to the new conventions.
network/lxi-tools: Updated for version 1.19
network/nbd: Updated for version 3.17
network/opera-developer: Updated for version 53.0.2900.0.
network/palemoon: Updated for version 27.8.2.
network/pdns: Added (high-performance authoritative server).
network/prosody-mod-smacks: Updated for version hg2937.
network/qTox: Updated for version 1.14.1.
network/r8168: Update maintainer email.
network/riot-web: Added (Riot for Desktop).
network/siege: Updated for version 4.0.4.
network/signal-desktop: Updated for version 1.6.1.
network/skypeforlinux: Updated for version 8.18.0.6.
network/surfraw: Updated for version 2.3.0.
network/telegram: Updated for version 1.2.14.
network/tor-browser: Updated for version 7.5.2.
network/tornado: Alter optional and mandatory dependencies.
network/tornado: Updated for version 5.0.1.
network/weechat: Updated for version 2.1.
network/znc: Updated for version 1.6.6.
office/MasterPDFEditor: Updated for version 4.3.89.
office/devtodo: Switch to i586 + new maintainer.
office/keepassx: Fixed homepage.
office/mythes: Update maintainer email.
perl/perl-AnyEvent: Avoid prompting during build.
perl/perl-B-Hooks-EndOfScope: Added (execute code after compile).
perl/perl-B-Hooks-OP-Check: Added (Hook into XS modules).
perl/perl-B-Hooks-OP-PPAddr: Added (Hook into opcode execution).
perl/perl-Class-Load-XS: Added (XS implementation of Class::Load).
perl/perl-Clone: Added (Recursively copy Perl datatypes).
perl/perl-Devel-Declare: Added (Adding keywords to perl, in perl).
perl/perl-Devel-OverloadInfo: Added (Introspect overloaded ops).
perl/perl-File-Grep: Added (Find matches in files).
perl/perl-File-Type: Added (Determine file type using magic).
perl/perl-MRO-Compat: Added (mro::* interface compatibility).
perl/perl-Math-GSL-Linalg-SVD: Added (SVD and eigenvector decomp).
perl/perl-Module-Runtime-Conflicts: Added (Info on conflicts).
perl/perl-Scalar-List-Utils: Added (updated version of List:Utils).
perl/perl-Scope-Upper: Added (Act on upper scopes).
perl/perl-Sub-Exporter-ForMethods: Added (helper for Sub::Exporter).
perl/perl-Sub-Identify: Added (Retrieve names of code references).
perl/perl-Test-CleanNamespaces: Added (Check for uncleaned imports).
perl/perl-Test-Harness: Updated for version 3.42.
perl/perl-Test-Inter: Updated for version 1.07.
perl/perl-Variable-Magic: Added (user-defined magic).
perl/perl-aliased: Added (Use shorter versions of class names).
perl/perl-namespace-autoclean: Added (imports out of namespace).
perl/perl-namespace-clean: Added (Keep imports out of namespace).
perl/txt2html: Added (Text to HTML converter).
python/Mako: Update maintainer email.
python/XlsxWriter: Updated for version 1.0.2.
python/affine: Updated for version 2.2.0.
python/artifacts: Updated for version 20180115.
python/astroid: Updated for version 1.6.2.
python/backports.lzma: Added (Backport of Python 3.3 lzma library).
python/click-plugins: Updated for version 1.0.3.
python/dbus-python3: Update maintainer email.
python/dfdatetime: Updated for version 20180318.
python/dfvfs: Updated for version 20171230.
python/dfwinreg: Updated for version 20170706.
python/paramiko: Updated for version 2.4.1.
python/phply: Updated for version 1.2.4.
python/pkginfo: Updated for version 1.4.2.
python/plaso: Updated for version 20180127.
python/pygobject3-python3: Update maintainer email.
python/pyparsing: Updated for version 2.2.0.
python/pyperclip: Updated for version 1.6.0.
python/pysqlite: Added (Python interface to SQLite 3).
python/pytest-runner: Updated for version 4.2.
python/python3-tornado: Updated for version 5.0.1.
python/pytsk: Updated for version 20180225.
python/pytz: Updated for version 2018.3.
python/snuggs: Add Python 3 support.
python/stopit: Updated for version 1.1.2.
python/tqdm: Updated for version 4.19.8.
system/alacritty: Updated for version gitdcc4b75.
system/bin2iso: Update maintainer email.
system/can-utils: Added (SocketCAN userspace utilities and tools).
system/collectd: Switch to i586 + new maintainer.
system/dehydrated: Updated for version 0.6.1.
system/docbook-xml: Switch to https.
system/dovecot-pigeonhole: Updated for version 0.5.0.1.
system/dovecot: Updated for version 2.3.0.1.
system/drbd-utils: Updated for version 9.3.0.
system/ecm-tools: Update maintainer email.
system/exfat-utils: Updated for version 1.2.8.
system/fuse-exfat: Updated for version 1.2.8.
system/gpart: Update maintainer email.
system/guix: Update maintainer email.
system/kcollectd: Added (Qt4-based frontend for collectd).
system/mdf2iso: Update maintainer email.
system/nilfs-utils: Updated for version 2.2.7.
system/nvidia-firmware: Update maintainer email.
system/posh: Update maintainer email.
system/pspg: Updated for version 1.0.0.
system/rover: Update maintainer email.
system/slackroll: Updated for version v48.
system/sleuthkit: Updated for version 4.6.0.
system/spl-solaris: Updated for version 0.7.7.
system/tpm: Update maintainer email.
system/ttf-lato: Fixed slack-desc.
system/unrar: Updated for version 5.6.1.
system/usermin: Updated for version 1.740.
system/webmin: Updated for version 1.881.
system/wiimms-iso-tools: Update maintainer email.
system/zfs-on-linux: Updated for version 0.7.7.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180324/1afc0b80/attachment-0001.asc>

From matteo.bernardini at gmail.com  Sat Mar 24 06:56:53 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 24 Mar 2018 07:56:53 +0100
Subject: [Slackbuilds-users] Updates - 20180324.1
In-Reply-To: <99faf654-4efd-3257-c43b-a02c6f5fd916@slackbuilds.org>
References: <99faf654-4efd-3257-c43b-a02c6f5fd916@slackbuilds.org>
Message-ID: <CAPsDuS5bheNq2E+egQpO9MXhhMrDGdFPSosDnMxCrhJ-_VV0og@mail.gmail.com>

2018-03-24 1:27 GMT+01:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:
> You might notice that we approved perl-Scalar-List-Utils, which is also
> part of Slackware core packages (perl). David and Matteo has found a way
> so that it doesn't replace any Slackware's file, so it got approved.

to be fair just David handled this, I just commented about it and also
got it wrong :/

Matteo

From didier at slint.fr  Sat Mar 24 11:30:16 2018
From: didier at slint.fr (Didier Spaier)
Date: Sat, 24 Mar 2018 12:30:16 +0100
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <66a50793-5d8e-ad9e-b600-4d0b86d267f5@slint.fr>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
 <20180322190043.GF9449@blackswan> <201803221646.26409.ricardo@palmtx.com.ar>
 <66a50793-5d8e-ad9e-b600-4d0b86d267f5@slint.fr>
Message-ID: <4ce9b91a-75a2-9c54-e61d-381443fd0e7e@slint.fr>



Le 22/03/2018 ? 21:20, Didier Spaier a ?crit?:
> Hello,
> 
>>>> 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!
> 
>>>> * [insert your favorite obscure Slackware/SBo script or app here]
> +=I use it
> ?=I never heard about it until today
> *=not in SBo:
> asbt?
> depfinder *+
> deb2tgz
> findpkg
> slapt-src *+
> sourcery *+
> slpkg
> slapt-get *+
> gslapt *+
> spi *+
> spkg+
> netpkg * # Zenwalk
> slackroll?
> slack-utils?
> slachlog?
> sun?
> salix-update-notifier *+
> swun?
> 
> Probably others :D

One more: usm* (Unified Slackware package manager) # Porteus

From matteo.bernardini at gmail.com  Sat Mar 24 16:27:11 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 24 Mar 2018 17:27:11 +0100
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <4ce9b91a-75a2-9c54-e61d-381443fd0e7e@slint.fr>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
 <20180322190043.GF9449@blackswan>
 <201803221646.26409.ricardo@palmtx.com.ar>
 <66a50793-5d8e-ad9e-b600-4d0b86d267f5@slint.fr>
 <4ce9b91a-75a2-9c54-e61d-381443fd0e7e@slint.fr>
Message-ID: <CAPsDuS674tJXR0uBE6zvuJ+QwjffZMP8CjGJEiJOT4Mev1Q0jA@mail.gmail.com>

as nobody seems to have done it yet, I humbly suggest the addition of
slackrepo to the category...

From z.coldplayer at gmail.com  Sun Mar 25 07:46:34 2018
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Sun, 25 Mar 2018 11:46:34 +0400
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <201803221646.26409.ricardo@palmtx.com.ar>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
 <20180322190043.GF9449@blackswan>
 <201803221646.26409.ricardo@palmtx.com.ar>
Message-ID: <CAEWL1_9jqwrsL89HpMJaDmgWZoMrVoSWi0M2mqPtz6v4Z7dvRA@mail.gmail.com>

On 22 March 2018 at 23:46, Ricardo J. Barberis <ricardo at palmtx.com.ar> wrote:
> El Jueves 22/03/2018 a las 16:00, David Woodfall escribi?:
>> On Friday 23 March 2018 07:27,
>> klaatu at mixedsignals.ml <klaatu at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From z.coldplayer at gmail.com  Sun Mar 25 07:50:35 2018
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Sun, 25 Mar 2018 11:50:35 +0400
Subject: [Slackbuilds-users] Extend FAQ for UID/GID
In-Reply-To: <eb60f89f-66ca-2910-cca1-d6863f3db2c4@gmail.com>
References: <eb60f89f-66ca-2910-cca1-d6863f3db2c4@gmail.com>
Message-ID: <CAEWL1_-EA5AQ-f45Un9NSnqSmdS5ntd0WpgcbAnRJC=mKNvRhw@mail.gmail.com>

I don't remember having seen such a list which makes sense as much as
the list of network port numbers

On 20 March 2018 at 17:59, Andrzej Telszewski <atelszewski at gmail.com> wrote:
> Hi,
>
> "13. Do you keep a list of non-standard uid and gid numbers that we should
> use in our scripts?"
>
> Could this point have somewhere words "group" and "user" added?
> It took me a minute to think that I have to look for "UID" or "GID" to find
> the relevant info.
>
> Thanks!
>
> --
> Best regards / Pozdrawiam,
> Andrzej Telszewski
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From atelszewski at gmail.com  Sun Mar 25 08:07:27 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 25 Mar 2018 10:07:27 +0200
Subject: [Slackbuilds-users] Extend FAQ for UID/GID
In-Reply-To: <CAEWL1_-EA5AQ-f45Un9NSnqSmdS5ntd0WpgcbAnRJC=mKNvRhw@mail.gmail.com>
References: <eb60f89f-66ca-2910-cca1-d6863f3db2c4@gmail.com>
 <CAEWL1_-EA5AQ-f45Un9NSnqSmdS5ntd0WpgcbAnRJC=mKNvRhw@mail.gmail.com>
Message-ID: <b4f34141-0d70-ce2e-4766-06e5d5afbfeb@gmail.com>

On 25/03/18 09:50, Jheengut Pritvi wrote:
> I don't remember having seen such a list which makes sense as much as
> the list of network port numbers
> 
> On 20 March 2018 at 17:59, Andrzej Telszewski<atelszewski at gmail.com>  wrote:
>> Hi,
>>
>> "13. Do you keep a list of non-standard uid and gid numbers that we should
>> use in our scripts?"
>>
>> Could this point have somewhere words "group" and "user" added?
>> It took me a minute to think that I have to look for "UID" or "GID" to find
>> the relevant info.
>>
>> Thanks!

https://slackbuilds.org/uid_gid.txt

-- 
Best regards / Pozdrawiam,
Andrzej Telszewski

From atelszewski at gmail.com  Sun Mar 25 16:46:03 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 25 Mar 2018 18:46:03 +0200
Subject: [Slackbuilds-users] github doubling tarball name, again
Message-ID: <04cc566f-f165-f5e1-e295-3df628cb77d6@gmail.com>

Hi,

When I try to download:
https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz

the suggested tarball name is:

"elementary-xfce-elementary-xfce-0.11.tar.gz"

Can someone knowledgeable (I know we have some here ;-)) tell me if it's 
possible to get the link in a way so that the tarball is actually:

"elementary-xfce-0.11.tar.gz"

?

Thanks!

-- 
Best regards / Pozdrawiam,
Andrzej Telszewski

From didier at slint.fr  Sun Mar 25 16:56:17 2018
From: didier at slint.fr (Didier Spaier)
Date: Sun, 25 Mar 2018 18:56:17 +0200
Subject: [Slackbuilds-users] github doubling tarball name, again
In-Reply-To: <04cc566f-f165-f5e1-e295-3df628cb77d6@gmail.com>
References: <04cc566f-f165-f5e1-e295-3df628cb77d6@gmail.com>
Message-ID: <c02c9d26-cbf5-406c-cf78-ea45326acfd8@slint.fr>

Hi,

Le 25/03/2018 ? 18:46, Andrzej Telszewski a ?crit?:
> Hi,
> 
> When I try to download:
> https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz
> 
> the suggested tarball name is:
> 
> "elementary-xfce-elementary-xfce-0.11.tar.gz"
> 
> Can someone knowledgeable (I know we have some here ;-)) tell me if it's possible to get the link in a way so that the tarball is actually:
> 
> "elementary-xfce-0.11.tar.gz"

No issue here, using wget-1.19.4-x86_64-2_slack14.2

Command:
wget https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz

didier[~]$ ls -ltr elem*
-rw-r--r-- 1 didier users 7945508 mars  25 18:51 elementary-xfce-0.11.tar.gz


Didier

From matteo.bernardini at gmail.com  Sun Mar 25 17:11:52 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 25 Mar 2018 19:11:52 +0200
Subject: [Slackbuilds-users] github doubling tarball name, again
In-Reply-To: <04cc566f-f165-f5e1-e295-3df628cb77d6@gmail.com>
References: <04cc566f-f165-f5e1-e295-3df628cb77d6@gmail.com>
Message-ID: <CAPsDuS4p0fJHtgAyJLXuZ_xm+V661SdyBMidbHeE1k-JN7VSBA@mail.gmail.com>

2018-03-25 18:46 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:
> Hi,
>
> When I try to download:
> https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz
>
> the suggested tarball name is:
>
> "elementary-xfce-elementary-xfce-0.11.tar.gz"
>
> Can someone knowledgeable (I know we have some here ;-)) tell me if it's
> possible to get the link in a way so that the tarball is actually:
>
> "elementary-xfce-0.11.tar.gz"
>
> ?

I suppose you are using a browser to download it or wget with the
parameter "--content-disposition", but it's not your or github's
fault: if you look at the release page you can see that they seem to
have tagged it wrong, compare the releases below or equal to v0.9 to
the subsequent

https://github.com/shimmerproject/elementary-xfce/releases

with proper tagging, prepending the name of the tag should let you
specify a consistent (not depending on the download type) naming for
the tarball, for example

https://github.com/shimmerproject/elementary-xfce/archive/v0.9/elementary-xfce-0.9.tar.gz

but as tagging for the following releases is broken I don't have a
solution for you apart for adding an alternate extraction routine,
like

tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf
$CWD/$PRGNAM-$PRGNAM-$VERSION.tar.gz

Matteo

From atelszewski at gmail.com  Sun Mar 25 17:11:55 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 25 Mar 2018 19:11:55 +0200
Subject: [Slackbuilds-users] github doubling tarball name, again
In-Reply-To: <c02c9d26-cbf5-406c-cf78-ea45326acfd8@slint.fr>
References: <04cc566f-f165-f5e1-e295-3df628cb77d6@gmail.com>
 <c02c9d26-cbf5-406c-cf78-ea45326acfd8@slint.fr>
Message-ID: <0d54cdff-8412-1c15-2c2e-283f5966483f@gmail.com>

On 25/03/18 18:56, Didier Spaier wrote:
> Hi,
> 
> Le 25/03/2018 ? 18:46, Andrzej Telszewski a ?crit?:
>> Hi,
>>
>> When I try to download:
>> https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz
>>
>> the suggested tarball name is:
>>
>> "elementary-xfce-elementary-xfce-0.11.tar.gz"
>>
>> Can someone knowledgeable (I know we have some here ;-)) tell me if it's possible to get the link in a way so that the tarball is actually:
>>
>> "elementary-xfce-0.11.tar.gz"
> No issue here, using wget-1.19.4-x86_64-2_slack14.2
> 
> Command:
> wgethttps://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz
> 
> didier[~]$ ls -ltr elem*
> -rw-r--r-- 1 didier users 7945508 mars  25 18:51 elementary-xfce-0.11.tar.gz

OK then.
wget works as expected, Firefox doesn't.
Shit. Again.

-- 
Best regards / Pozdrawiam,
Andrzej Telszewski

From falsetti at clansco.org  Sun Mar 25 17:12:28 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Sun, 25 Mar 2018 19:12:28 +0200
Subject: [Slackbuilds-users] github doubling tarball name, again
In-Reply-To: <c02c9d26-cbf5-406c-cf78-ea45326acfd8@slint.fr>
References: <04cc566f-f165-f5e1-e295-3df628cb77d6@gmail.com>
 <c02c9d26-cbf5-406c-cf78-ea45326acfd8@slint.fr>
Message-ID: <20180325191228.bf089b9a82db1e9eff99c3bb@clansco.org>

On Sun, 25 Mar 2018 18:56:17 +0200
Didier Spaier <didier at slint.fr> wrote:

> Hi,
> 
> Le 25/03/2018 ? 18:46, Andrzej Telszewski a ?crit?:

> > When I try to download:
> > https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz
> > 
> > the suggested tarball name is:
> > 
> > "elementary-xfce-elementary-xfce-0.11.tar.gz"

> No issue here, using wget-1.19.4-x86_64-2_slack14.2
> 
> Command:
> wget https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz
> 

I confirm, firefox (nightly) give "elementary-xfce-elementary-xfce-0.11.tar.gz

From atelszewski at gmail.com  Sun Mar 25 17:15:14 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 25 Mar 2018 19:15:14 +0200
Subject: [Slackbuilds-users] github doubling tarball name, again
In-Reply-To: <CAPsDuS4p0fJHtgAyJLXuZ_xm+V661SdyBMidbHeE1k-JN7VSBA@mail.gmail.com>
References: <04cc566f-f165-f5e1-e295-3df628cb77d6@gmail.com>
 <CAPsDuS4p0fJHtgAyJLXuZ_xm+V661SdyBMidbHeE1k-JN7VSBA@mail.gmail.com>
Message-ID: <cc534622-c03b-1f52-f76c-98dde69cb4e5@gmail.com>

On 25/03/18 19:11, Matteo Bernardini wrote:
> 2018-03-25 18:46 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:
>> Hi,
>>
>> When I try to download:
>> https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz
>>
>> the suggested tarball name is:
>>
>> "elementary-xfce-elementary-xfce-0.11.tar.gz"
>>
>> Can someone knowledgeable (I know we have some here ;-)) tell me if it's
>> possible to get the link in a way so that the tarball is actually:
>>
>> "elementary-xfce-0.11.tar.gz"
>>
>> ?
> 
> I suppose you are using a browser to download it or wget with the
> parameter "--content-disposition", but it's not your or github's
> fault: if you look at the release page you can see that they seem to
> have tagged it wrong, compare the releases below or equal to v0.9 to
> the subsequent
> 
> https://github.com/shimmerproject/elementary-xfce/releases
> 
> with proper tagging, prepending the name of the tag should let you
> specify a consistent (not depending on the download type) naming for
> the tarball, for example
> 
> https://github.com/shimmerproject/elementary-xfce/archive/v0.9/elementary-xfce-0.9.tar.gz
> 
> but as tagging for the following releases is broken I don't have a
> solution for you apart for adding an alternate extraction routine,
> like
> 
> tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf
> $CWD/$PRGNAM-$PRGNAM-$VERSION.tar.gz
> 
> Matteo

Yep, I noticed this too.
curl shows that indeed that is the case:
Content-Disposition: attachment; 
filename=elementary-xfce-elementary-xfce-0.11.tar.gz

Maybe I'll open issue ticket there.

-- 
Best regards / Pozdrawiam,
Andrzej Telszewski

From didier at slint.fr  Sun Mar 25 17:39:09 2018
From: didier at slint.fr (Didier Spaier)
Date: Sun, 25 Mar 2018 19:39:09 +0200
Subject: [Slackbuilds-users] github doubling tarball name, again
In-Reply-To: <0d54cdff-8412-1c15-2c2e-283f5966483f@gmail.com>
References: <04cc566f-f165-f5e1-e295-3df628cb77d6@gmail.com>
 <c02c9d26-cbf5-406c-cf78-ea45326acfd8@slint.fr>
 <0d54cdff-8412-1c15-2c2e-283f5966483f@gmail.com>
Message-ID: <fe869920-fb72-a38b-400a-7f02f5d5dd8a@slint.fr>



Le 25/03/2018 ? 19:11, Andrzej Telszewski a ?crit?:
> On 25/03/18 18:56, Didier Spaier wrote:
>> Hi,
>>
>> Le 25/03/2018 ? 18:46, Andrzej Telszewski a ?crit?:
>>> Hi,
>>>
>>> When I try to download:
>>> https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz
>>>
>>> the suggested tarball name is:
>>>
>>> "elementary-xfce-elementary-xfce-0.11.tar.gz"
>>>
>>> Can someone knowledgeable (I know we have some here ;-)) tell me if it's possible to get the link in a way so that the tarball is actually:
>>>
>>> "elementary-xfce-0.11.tar.gz"
>> No issue here, using wget-1.19.4-x86_64-2_slack14.2
>>
>> Command:
>> wgethttps://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz
>>
>> didier[~]$ ls -ltr elem*
>> -rw-r--r-- 1 didier users 7945508 mars? 25 18:51 elementary-xfce-0.11.tar.gz
> 
> OK then.
> wget works as expected, Firefox doesn't.
> Shit. Again.

Yes. I avoid to use Firefox for downloading files, especially compressed ones.

From rellis at dp100.com  Sun Mar 25 17:46:58 2018
From: rellis at dp100.com (Richard Ellis)
Date: Sun, 25 Mar 2018 13:46:58 -0400
Subject: [Slackbuilds-users] Request for UID/GID allocation in uid_gid.txt
 for 'chrony'
Message-ID: <20180325174658.GR28923@d820.dp100.com>


Hello,

I am the maintainer of the SlackBuilds 'chrony' build script
(https://slackbuilds.org/repository/14.2/network/chrony/).  Last week a user
of the build script emailed me a patch that moved the scripts support up to
Chrony version 3.2 as well as added an rc.chrony start/stop script and made
use of version 3.2's ability to run chronyd as a user other than root.

I am in the process of updating the build script for resubmission, and so as
to avoid UID/GID overlap with other SlackBuild scripts, I am requesting a
UID/GID allocation in the uid_gid.txt file for chrony.

Thank you,
Richard


From baildon.research at googlemail.com  Sun Mar 25 18:16:06 2018
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 25 Mar 2018 19:16:06 +0100
Subject: [Slackbuilds-users] github doubling tarball name, again
In-Reply-To: <fe869920-fb72-a38b-400a-7f02f5d5dd8a@slint.fr>
References: <04cc566f-f165-f5e1-e295-3df628cb77d6@gmail.com>
 <c02c9d26-cbf5-406c-cf78-ea45326acfd8@slint.fr>
 <0d54cdff-8412-1c15-2c2e-283f5966483f@gmail.com>
 <fe869920-fb72-a38b-400a-7f02f5d5dd8a@slint.fr>
Message-ID: <CAMt7G9Rz0sxWchTPF5+Ym2G4gLk+AkjHmiHuBuo_uVm3H0nhsA@mail.gmail.com>

>> wget works as expected, Firefox doesn't.
>> Shit. Again.
>
> Yes. I avoid to use Firefox for downloading files, especially compressed ones.

Well, that's not my opinion.  IMO, what's broken is

(1) an http tool like wget that by default ignores what the http
protocol is telling it.

(2) github that doesn't document their download api.

(3) projects using stupid tags like 'elementary-xfce-0.11' or 'v0.1.2'
or 'Release_3.2.1' instead of just '1.2.3'

-D.

From matteo.bernardini at gmail.com  Sun Mar 25 18:16:20 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 25 Mar 2018 20:16:20 +0200
Subject: [Slackbuilds-users] Request for UID/GID allocation in
 uid_gid.txt for 'chrony'
In-Reply-To: <20180325174658.GR28923@d820.dp100.com>
References: <20180325174658.GR28923@d820.dp100.com>
Message-ID: <CAPsDuS7NEsW5b+unM4a2dqL0EkwdO+Bonk9TiFeGEDezxbxKkQ@mail.gmail.com>

2018-03-25 19:46 GMT+02:00 Richard Ellis via SlackBuilds-users
<slackbuilds-users at slackbuilds.org>:
>
> Hello,
>
> I am the maintainer of the SlackBuilds 'chrony' build script
> (https://slackbuilds.org/repository/14.2/network/chrony/).  Last week a user
> of the build script emailed me a patch that moved the scripts support up to
> Chrony version 3.2 as well as added an rc.chrony start/stop script and made
> use of version 3.2's ability to run chronyd as a user other than root.
>
> I am in the process of updating the build script for resubmission, and so as
> to avoid UID/GID overlap with other SlackBuild scripts, I am requesting a
> UID/GID allocation in the uid_gid.txt file for chrony.

there you go :)

chrony
========
User:   chrony        UID: 354        GID: 354
Group:  chrony                        GID: 354

Matteo

From kingbeowulf at gmail.com  Mon Mar 26 01:23:42 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 25 Mar 2018 18:23:42 -0700
Subject: [Slackbuilds-users] BOINC releases: more github downoad URL
 befuddlement
Message-ID: <b8eb45ba-a2c0-bda5-81d0-b7a2c836d719@gmail.com>

I know this comes up way to often, but I am stumped.  How do I get a
proper download URL from github for boinc?  On the release page

https://github.com/BOINC/boinc/releases

when I use a browser (e.g. Firefox) to d/l the tar.gz for
client_release/7.8/7.8.6 I get the file:
boinc-client_release-7.8-7.8.6.tar.gz

the same URL with wget (right-click, copy link location) gives:
7.8.6.tar.gz

The URL Firefox displays in the status bar to click on to d/l is:
https://github.com/BOINC/boinc/archive/client_release/7.8/7.8.6.tar.gz

If I extract the URL Firefox ended up using in its download progress window:
https://codeload.github.com/BOINC/boinc/tar.gz/client_release/7.8/7.8.6
I get a file named simply "7.8.6"

If I use:
wget --content-disposition
https://github.com/BOINC/boinc/archive/client_release/7.8/7.8.6.tar.gz

the downloaded file is as expected:
boinc-client_release-7.8-7.8.6.tar.gz

Why does this have to be so freaking obscure?  Obviously, "7.8.6.tar.gz"
is not usable in .info for SBo automated tools. Looking at other github
examples was of no help - lots of 'ERROR 404: Not Found.' trying to link
to the full file name directly.

TL;DR:
What do I put in boinc.info for a download URL for release posted on github?

Thanks
Ed




-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180325/3528d126/attachment.asc>

From willysr at slackbuilds.org  Mon Mar 26 01:47:08 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 26 Mar 2018 08:47:08 +0700
Subject: [Slackbuilds-users] BOINC releases: more github downoad URL
 befuddlement
In-Reply-To: <b8eb45ba-a2c0-bda5-81d0-b7a2c836d719@gmail.com>
References: <b8eb45ba-a2c0-bda5-81d0-b7a2c836d719@gmail.com>
Message-ID: <73e1547a-9519-8af9-f426-d315896bca34@slackbuilds.org>

> TL;DR:
> What do I put in boinc.info for a download URL for release posted on github?

try

https://github.com/BOINC/boinc/archive/client_release/7.10/7.9.3/boinc-client_release-7.9.3.tar.gz


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180326/afb5c258/attachment.asc>

From kingbeowulf at gmail.com  Mon Mar 26 03:16:32 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 25 Mar 2018 20:16:32 -0700
Subject: [Slackbuilds-users] BOINC releases: more github downoad URL
 befuddlement
In-Reply-To: <73e1547a-9519-8af9-f426-d315896bca34@slackbuilds.org>
References: <b8eb45ba-a2c0-bda5-81d0-b7a2c836d719@gmail.com>
 <73e1547a-9519-8af9-f426-d315896bca34@slackbuilds.org>
Message-ID: <efe4d3ec-5ba4-748f-9c72-52ac6e388b3b@gmail.com>

On 03/25/2018 06:47 PM, Willy Sudiarto Raharjo wrote:
>> TL;DR:
>> What do I put in boinc.info for a download URL for release posted on github?
> 
> try
> 
> https://github.com/BOINC/boinc/archive/client_release/7.10/7.9.3/boinc-client_release-7.9.3.tar.gz
> 
> 
Thanks.  The one permutation I didn't try.  Github (and github users)
makes no freaking sense.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180325/283931d0/attachment.asc>

From yalhcru at gmail.com  Mon Mar 26 05:06:12 2018
From: yalhcru at gmail.com (B Watson)
Date: Mon, 26 Mar 2018 01:06:12 -0400
Subject: [Slackbuilds-users] github doubling tarball name, again
In-Reply-To: <CAMt7G9Rz0sxWchTPF5+Ym2G4gLk+AkjHmiHuBuo_uVm3H0nhsA@mail.gmail.com>
References: <04cc566f-f165-f5e1-e295-3df628cb77d6@gmail.com>
 <c02c9d26-cbf5-406c-cf78-ea45326acfd8@slint.fr>
 <0d54cdff-8412-1c15-2c2e-283f5966483f@gmail.com>
 <fe869920-fb72-a38b-400a-7f02f5d5dd8a@slint.fr>
 <CAMt7G9Rz0sxWchTPF5+Ym2G4gLk+AkjHmiHuBuo_uVm3H0nhsA@mail.gmail.com>
Message-ID: <CAN1hMuCvLvtGaG-tztiZWvgfD4zbA6DRbe3q1eZmT3mTs6E5=A@mail.gmail.com>

On 3/25/18, David Spencer via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:

> (1) an http tool like wget that by default ignores what the http
> protocol is telling it.

wget didn't always support Content-Disposition. When support was added,
it was flagged as "experimental" and thus disabled by default. From the
man page:

       --content-disposition
           If this is set to on, experimental (not fully-functional) support for
           "Content-Disposition" headers is enabled. This can
currently result in
           extra round-trips to the server for a "HEAD" request, and is known to
           suffer from a few bugs, which is why it is not currently enabled by
           default.

I wouldn't call wget "broken" because of that. But, that's my opinion,
plenty of room for others...

From rworkman at slackbuilds.org  Mon Mar 26 06:00:54 2018
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 26 Mar 2018 01:00:54 -0500
Subject: [Slackbuilds-users] Extend FAQ for UID/GID
In-Reply-To: <eb60f89f-66ca-2910-cca1-d6863f3db2c4@gmail.com>
References: <eb60f89f-66ca-2910-cca1-d6863f3db2c4@gmail.com>
Message-ID: <20180326010054.7b477a90@home.rlworkman.net>

On Tue, 20 Mar 2018 14:59:15 +0100
Andrzej Telszewski <atelszewski at gmail.com> wrote:

> "13. Do you keep a list of non-standard uid and gid numbers that we 
> should use in our scripts?"
> 
> Could this point have somewhere words "group" and "user" added?
> It took me a minute to think that I have to look for "UID" or "GID"
> to find the relevant info.


Done.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180326/21080468/attachment.asc>

From ricardo at palmtx.com.ar  Mon Mar 26 17:08:32 2018
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Mon, 26 Mar 2018 14:08:32 -0300
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <4ce9b91a-75a2-9c54-e61d-381443fd0e7e@slint.fr>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <66a50793-5d8e-ad9e-b600-4d0b86d267f5@slint.fr>
 <4ce9b91a-75a2-9c54-e61d-381443fd0e7e@slint.fr>
Message-ID: <201803261408.32338.ricardo@palmtx.com.ar>

Those which are not on SBo, I found some homepages (inlined).

El S?bado 24/03/2018 a las 13:27, Matteo Bernardini escribi?:
> as nobody seems to have done it yet, I humbly suggest the addition of
> slackrepo to the category...
https://idlemoor.github.io/slackrepo/

El S?bado 24/03/2018 a las 08:30, Didier Spaier escribi?:
> Le 22/03/2018 ? 21:20, Didier Spaier a ?crit?:
> > Hello,
> >
> >>>> 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
https://www.sbopkg.org/

> >>>> * sboui
> >>>> * sbbdep
> >>>> * slackpkg+
http://www.slakfinder.org/slackpkg+.html

> >>>> * sport
http://slackermedia.info/sport/

> >>>> * sbotools
> >>
> >> Some of those are not on SBo.
> >>
> >>> * mkslack :)
> >>
> >> Nice one!
> >>
> >>>> * [insert your favorite obscure Slackware/SBo script or app here]
> >
> > +=I use it
> > ?=I never heard about it until today
> > *=not in SBo:
> > asbt?
> > depfinder *+
http://depfinder.sourceforge.net/

> > deb2tgz
> > findpkg
> > slapt-src *+
https://software.jaos.org/

> > sourcery *+
> > slpkg
> > slapt-get *+
https://software.jaos.org/

> > gslapt *+
https://software.jaos.org/

> > spi *+
> > spkg+
> > netpkg * # Zenwalk
> > slackroll?
> > slack-utils?
> > slachlog?
> > sun?
> > salix-update-notifier *+
> > swun?
> >
> > Probably others :D
>
> One more: usm* (Unified Slackware package manager) # Porteus
https://sourceforge.net/projects/usm/


-- 
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

From lspencer31 at cfl.rr.com  Tue Mar 27 01:14:59 2018
From: lspencer31 at cfl.rr.com (Lenard Spencer)
Date: Mon, 26 Mar 2018 21:14:59 -0400
Subject: [Slackbuilds-users] Gnucash SBo script
Message-ID: <67cc32af-5229-fc9d-a8be-9284a1dda0a7@cfl.rr.com>

The other day I sent an email to the maintainer of the gnucash 
slackbuild asking if he still maintained it, and if not could I take it 
over.? He said that since he no longer uses it I was welcome to it.

I already have some scripts to submit: an updated gnucash, gnucash-docs, 
and k9copy-reloaded (a DVD backup program).

With the powers-that-be's approval I can send them up tomorrow.

Thanks.



From lspencer31 at cfl.rr.com  Tue Mar 27 01:17:13 2018
From: lspencer31 at cfl.rr.com (Lenard Spencer)
Date: Mon, 26 Mar 2018 21:17:13 -0400
Subject: [Slackbuilds-users] gcc5 in Matteo's repo
Message-ID: <6229b6ec-d81d-0115-5c50-1f9c47b32ce6@cfl.rr.com>

This one is really only relevant in Matteo's repo (upcoming 15.0?).

I found a minor oops in the gcc5 slackbuild script:? it sets TAG to SBo 
instead of _SBo.? Just passing it along.

Thanks.



From andreas.guldstrand at gmail.com  Tue Mar 27 20:14:35 2018
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Tue, 27 Mar 2018 22:14:35 +0200
Subject: [Slackbuilds-users] system/lsyncd requires Lua 5.2
In-Reply-To: <20180320210331.GA11460@comp.lan>
References: <20180320194624.GA18699@comp.lan>
 <CAPsDuS4hPVLjUsHyX9beyvy=6DPBgrURnDF3QRx-6DgjADuE_A@mail.gmail.com>
 <20180320210331.GA11460@comp.lan>
Message-ID: <CAEQ5t81TnFc6F70SUCCUqm5HKBYE-5O-UaD_O5cVcQXZFCm+Gw@mail.gmail.com>

On 20 March 2018 at 22:03, Arkadiusz Drabczyk <arkadiusz at drabczyk.org> wrote:
> Why isn't this?  What's the difference between Lua and, say, Python in
> this regard?

I'm not an authority on this, but as far as I know lua is more
designed to be built-in inside the products using it, not installed
system-wide, so since SBo installs it system-wide that's outside the
normal usage of it and possibly that's the reason it works less than
superbly.

/ Andreas

From zanculmarktum at gmail.com  Wed Mar 28 06:52:03 2018
From: zanculmarktum at gmail.com (Azure Zanculmarktum)
Date: Wed, 28 Mar 2018 13:52:03 +0700
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
Message-ID: <CAPbfrhJ+k3dearUMKCq6g0cJYv=QJuwrNijSrKnBy_qt_bXc=Q@mail.gmail.com>

>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
>* [insert your favourite obscure Slackware/SBo script or app here]

>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

* https://github.com/zanculmarktum/sbomake
:^)

From giuseppe.diterlizzi at gmail.com  Wed Mar 28 08:41:20 2018
From: giuseppe.diterlizzi at gmail.com (Giuseppe Di Terlizzi)
Date: Wed, 28 Mar 2018 10:41:20 +0200
Subject: [Slackbuilds-users] Proposal for Slackware category in SBo
In-Reply-To: <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
References: <alpine.LNX.2.20.1803220636130.25233@salmo.appl-ecosys.com>
 <201803221232.35334.ricardo@palmtx.com.ar>
 <201803221243.24862.ricardo@palmtx.com.ar>
 <alpine.LNX.2.20.1803220916330.25233@salmo.appl-ecosys.com>
 <e9a049d34a941387ed97eb155c5085d6@mixedsignals.ml>
Message-ID: <CAFNWig-d5CLMoFtR_v9z0Kv-7O_yUXg+NJWzqDsqocDmtXovxA@mail.gmail.com>

* slackman -- https://lotarproject.github.io/slackman/

:-)

Giuseppe Di Terlizzi

2018-03-22 19:27 GMT+01:00 <klaatu at mixedsignals.ml>:

> 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
> * [insert your favourite obscure Slackware/SBo script or app here]
>
> 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
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180328/d460eec9/attachment.html>

From s.arcus at open-t.co.uk  Wed Mar 28 21:19:50 2018
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Wed, 28 Mar 2018 22:19:50 +0100
Subject: [Slackbuilds-users] Minor issue with Brave browser
Message-ID: <6c13ecda-d1f6-1eed-a63d-d68e56f34700@open-t.co.uk>

I have just installed yesterday Brave from SBo. The small issue I have 
with it is that in Fluxbox it doesn't display an icon in the iconbar, in 
the bottom taskbar when running - just the window title. All other 
software I run has its own icon in the taskbar when running - not just 
the window title. Is this a file missing in Brave itself, or something 
down to Fluxbox, or maybe wider still with the desktop environment 
framework, somewhere? Does anybody know?

From willysr at slackbuilds.org  Sat Mar 31 01:06:04 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 31 Mar 2018 08:06:04 +0700
Subject: [Slackbuilds-users] Updates - 20180331.1
Message-ID: <766451e8-ae12-3217-f866-3910fd612537@slackbuilds.org>

Hi

This will be the last update in Q1 2018
Some interesting highlights:
- We added lua52/53 for those who needs newer lua version
- rust, nodejs{6}, go-lang, kotlin, vscode are updated to latest version
- libretro-mgba is now removed and included in mgba
- nvidia-{kernel,driver} are updated to the latest version
- gnucash has a new maintainer and updated to latest version
- the usual browser updates (palemoon, PaleMoon, opera, qute)

Just a soft reminder that some of our packages are still using i486 for
x86 architecture. Please have a look on your scripts and update them to
i586 for future updates. Make sure you grab the latest version of the
SlackBuild script from our website/repository before submitting an
update. Don't use your local copy unless you have a regular sync with
our git repository.

Sat Mar 31 00:45:06 UTC 2018
academic/fet: Updated download.
audio/clockchimes: Added (plays clock chimes).
audio/cmus: Updated for version 20180219_20a738d.
audio/nas: Updated for version 1.9.4.
audio/portmidi: Script cleanup.
audio/retrovol: Updated for version 0.14.1.
audio/shell-fm: Updated for version 0.8.
audio/xforge: Script cleanup.
desktop/elementary-xfce: Updated for version 0.11.
desktop/myGtkMenu: Update script.
desktop/oranchelo-icon-theme: Updated for version 0.7.6.6.
desktop/xonclock: Switch to i586.
development/GitEye: Updated md5sum.
development/LLgen: Updated homepage.
development/SDL2_gfx: Updated for version 1.0.4.
development/atom-amd64: Updated for version 1.25.0.
development/checkbashisms: Updated download.
development/diffoscope: Updated for version 93.
development/google-go-lang: Updated for version 1.9.5.
development/kotlin: Updated for version 1.2.31.
development/lua52: Added (scripting language).
development/lua53: Added (scripting language).
development/nodejs6: Updated for version 6.14.1.
development/nodejs: Updated for version 8.11.1.
development/rust: Updated for version 1.25.0.
development/shed: Switch to i586.
development/tiled: Updated for version 1.1.4.
development/vscode: Updated for version 1.21.1.
games/Gearboy: Added (Nintendo Game Boy / GameBoy Color emulator).
games/commandergenius: Updated download.
games/flare-game: Updated for version 1.0.
games/flare: Updated for version 1.0.
games/javacpc: Updated for version 2.9.6b.
games/libretro-mgba: Removed (included in mgba).
games/mgba: Build libretro.
games/ppsspp: Updated for version 1.5.4.
gis/proj: Fix .info file.
gis/saga-gis: Updated for version 6.3.0.
graphics/Blender: Updated for version 2.79b
graphics/PyMOL: Updated for version 2.1.0.
graphics/photoprint: Switch to i586.
graphics/vuescan: Updated for version 9.6.07.
graphics/yed: Updated homepage.
ham/chirp: Updated for version 20180325.
libraries/GitPython: Updated for version 2.1.9.
libraries/PyYAML: Switch to i586.
libraries/libAfterImage: Switch to i586.
libraries/libilbc: Switch to i586.
libraries/libnice: Updated for version 0.1.14.
libraries/libversion: Updated for version 2.6.0.
libraries/nspluginwrapper: Switch to i586.
libraries/ptlib: Switch to i586.
libraries/stfl: Avoid build potential failure.
libraries/zint: Update README.
misc/esniper: Updated for version 2.33.0.
multimedia/farsight2: Switch to i586.
multimedia/k9copy-reloaded: Added (DVD backup program).
multimedia/opencaster: Updated md5sum.
multimedia/smplayer: Updated for version 18.3.0.
network/PaleMoon: Updated for version 27.8.3.
network/chrony: Updated for version 3.2.
network/ekiga: Update SlackBuild, switch to i586.
network/gtk-gnutella: Updated for version 1.1.13.
network/lighttpd: Additional path fixes.
network/milter-greylist: Switch to i586.
network/msmtp: Updated download + switch to i586.
network/newsboat: Updated for version 2.11.
network/nextcloud-server: Updated for version 13.0.1.
network/opera-developer: Updated for version 53.0.2906.0.
network/opera: Updated for version 52.0.2871.40.
network/palemoon: Updated for version 27.8.3.
network/phpmyadmin: Updated for version 4.7.9.
network/polipo: Update doinst.sh + switch to i586.
network/prosody-mod-http-upload: Updated for version hg2948.
network/prosody-mod-man-muc: Updated for version hg2949.
network/proxymini: Updated for version 0.2.3.
network/pyNeighborhood: Updated for version 0.5.4.
network/qutebrowser: Updated for version 1.2.1.
network/rclone: Updated for version 1.40.
network/slurm: Updated for version 17.02.10.
network/teamviewer: Updated for version 13.1.3026.
network/telegram: Updated for version 1.2.15.
network/tor-browser: Updated for version 7.5.3.
network/udpxy: Updated homepage.
network/wifi-radar: Updated SlackBuild.
network/xdman: Updated for version 2018.7.2.7.
office/gnucash-docs: Added (Gnucash help and user guides).
office/gnucash: Updated for version 2.6.19 + new maintainer.
office/htmldoc: Updated homepage.
office/rednotebook: Updated for version 2.4.
perl/perl-CPAN-Perl-Releases: Updated for version 3.50.
perl/perl-CPANPLUS-Dist-Slackware: Updated for version 1.027.
perl/perl-DBD-SQLite: Updated for version 1.58.
perl/perl-Devel-StackTrace: Updated for version 2.03.
perl/perl-File-Copy-Recursive: Updated for version 0.40.
perl/perl-Image-Info: Updated for version 1.41.
perl/perl-Mail-DKIM: Updated for version 0.52.
perl/perl-MailTools: Updated for version 2.20.
perl/perl-Mojolicious: Updated for version 7.71.
perl/perl-Net-DNS-Native: Updated for version 0.18.
perl/perl-Pegex: Updated for version 0.64.
perl/perl-Sys-CPU: Updated homepage.
perl/perl-Test-File: Added (test file attributes and data).
perl/perl-Test-Spec: Updated for version 0.54.
perl/perl-Test-utf8: Added (tests for UTF-8 strings).
perl/perl-Text-CSV_XS: Updated for version 1.35.
perl/perl-Time-Piece: Updated for version 1.3204.
perl/perl-YAML-LibYAML: Updated for version 0.69.
perl/perl-local-lib: Updated for version 2.000024.
perl/perlbrew: Updated for version 0.82.
python/Pyro4: Updated homepage and download.
python/git-fame: Updated for version 1.4.2.
python/halberd: Update homepage.
python/migen: Updated homepage.
python/python-argopt: Added (doc to argparse driven by docopt).
python/python-clamd: Switch to i586.
python/python-fonttools: Updated for version 3.24.2.
python/python-fusepy: Updated homepage + download url.
python/python3-dateutil: Updated for version 2.7.2.
ruby/ruby-build: Updated for version 20180329
ruby/rubygem-httparty: Updated homepage.
system/atool: Switch to i586.
system/collectd: Updated for version 5.8.0.
system/daa2iso: Switch to i586.
system/ecm-tools: Updated for version 1.0.3.
system/fd: Updated for version 7.0.0.
system/goaccess: Switch to i586.
system/gtk-vnc: Updated for version 0.7.2.
system/hack-font-ttf: Updated for version 3.003.
system/imwheel: Switch to i586.
system/isdct: Updated md5sum.
system/kbfs: Updated for version 1.0.46.
system/keybase: Updated for version 1.0.46.
system/lbench: Updated for version 3.5.
system/letsencrypt: Updated for version 0.22.2.
system/lomoco: Switch to i586.
system/mjpg-streamer: Updated homepage + switch to i586.
system/ncdu: Updated for version 1.13.
system/netdata: Updated for version 1.10.0.
system/noto-fonts: Updated for version 20180322.
system/nvidia-driver: Updated for version 390.42.
system/nvidia-kernel: Updated for version 390.42.
system/powernowd: Add rc file + switch to i586.
system/ptop: Updated homepage and download.
system/regionset: Switch to i586.
system/spacefm: Updated for version 1.0.6.
system/st: Updated for version 0.8.1.
system/uif2iso: Switch to i586.
system/zstd: Updated for version 1.3.4.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180331/55662b76/attachment-0001.asc>

From willysr at slackbuilds.org  Sat Mar 31 01:19:38 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 31 Mar 2018 08:19:38 +0700
Subject: [Slackbuilds-users] system/lsyncd requires Lua 5.2
In-Reply-To: <20180320194624.GA18699@comp.lan>
References: <20180320194624.GA18699@comp.lan>
Message-ID: <2555e8ed-5b77-2721-bb69-d2fbb70a9f74@slackbuilds.org>

> A new release of lsyncd requires at least Lua 5.2, in ChangeLog
> https://github.com/axkibe/lsyncd/blob/master/ChangeLog it says:
> 
> change: needing now at least Lua 5.2 (Lua 5.1 no longer supported, Lua5.3 supported)
> 
> We used to have Lua 5.2 but it was removed in commit 9389d02 'until a
> working way to manage multiple lua versions in the system is
> provided'.  Moreover, development/lua README says:
> 
> "This package is for the version 5.1.x of lua, the one compatible with
> the software that needs lua on slackbuilds.org."
> 
> Lua 5.1 line is really quite old, the oldest release was on 17 Feb
> 2012 according to this site https://www.lua.org/versions.html.  I
> counted 66 packages that require lua:
> 
> find . -name "*.info" | xargs grep "^REQUIRES.*\blua\b" | wc -l
> 
> It would require a lot of manual work to check if all of these
> packages could work with Lua 5.2.  Should I just wait and explain that
> system/lsyncd would not be upgraded until Lua 5.2 becomes the default?

we now have lua52/53 in the repo, so you can start testing it with newer lua


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180331/9c2d4398/attachment.asc>

From kingbeowulf at gmail.com  Sat Mar 31 02:59:23 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Fri, 30 Mar 2018 19:59:23 -0700
Subject: [Slackbuilds-users] nvidia-driver-390-42 symlink blunder
Message-ID: <1a7a16eb-6348-5271-d657-1934da93c37d@gmail.com>

Admins

Just noticed - that it came up just now and not earlier? - that the
GLVND GL library is now libGL.so.1.7.0 and not libGL.so.1.0.0. This was
not noted in Nvidia's README.txt so I didn't notice until I tried to
compile wine-3.5.  Weird that a few steam games didn't care...

This patch to nvidia-switch should fix:

-----------------8<--------------------
diff --git a/system/nvidia-driver/nvidia-switch
b/system/nvidia-driver/nvidia-switch
index 6c7a77cce0..ed6f5c36e9 100644
--- a/system/nvidia-driver/nvidia-switch
+++ b/system/nvidia-driver/nvidia-switch
@@ -65,8 +65,8 @@ save_GL(){
       mv libGL.la-nvidia libGL.la

       if [ "$GLVND" = "yes" ]; then
-        ln -sf libGL.so.1.0.0 libGL.so.1
-       ln -sf libGL.so.1.0.0 libGL.so
+        ln -sf libGL.so.1.7.0 libGL.so.1
+       ln -sf libGL.so.1.7.0 libGL.so
         ln -sf libEGL.so.1-nvidia libEGL.so.1
        ln -sf libEGL.so.1-nvidia libEGL.so
       else
----------------->8---------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180330/e25e31d1/attachment.asc>

From willysr at slackbuilds.org  Sat Mar 31 03:35:10 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 31 Mar 2018 10:35:10 +0700
Subject: [Slackbuilds-users] nvidia-driver-390-42 symlink blunder
In-Reply-To: <1a7a16eb-6348-5271-d657-1934da93c37d@gmail.com>
References: <1a7a16eb-6348-5271-d657-1934da93c37d@gmail.com>
Message-ID: <8ad97ae4-5b10-754e-53a3-42cb4b00b512@slackbuilds.org>

> Just noticed - that it came up just now and not earlier? - that the
> GLVND GL library is now libGL.so.1.7.0 and not libGL.so.1.0.0. This was
> not noted in Nvidia's README.txt so I didn't notice until I tried to
> compile wine-3.5.  Weird that a few steam games didn't care...
> 
> This patch to nvidia-switch should fix:
> 
> -----------------8<--------------------
> diff --git a/system/nvidia-driver/nvidia-switch
> b/system/nvidia-driver/nvidia-switch
> index 6c7a77cce0..ed6f5c36e9 100644
> --- a/system/nvidia-driver/nvidia-switch
> +++ b/system/nvidia-driver/nvidia-switch
> @@ -65,8 +65,8 @@ save_GL(){
>        mv libGL.la-nvidia libGL.la
> 
>        if [ "$GLVND" = "yes" ]; then
> -        ln -sf libGL.so.1.0.0 libGL.so.1
> -       ln -sf libGL.so.1.0.0 libGL.so
> +        ln -sf libGL.so.1.7.0 libGL.so.1
> +       ln -sf libGL.so.1.7.0 libGL.so
>          ln -sf libEGL.so.1-nvidia libEGL.so.1
>         ln -sf libEGL.so.1-nvidia libEGL.so
>        else
> ----------------->8---------------------

Thanks
pushed to my branch


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180331/6d3fe676/attachment.asc>

From matteo.bernardini at gmail.com  Sat Mar 31 08:32:16 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 31 Mar 2018 10:32:16 +0200
Subject: [Slackbuilds-users] system/lsyncd requires Lua 5.2
In-Reply-To: <2555e8ed-5b77-2721-bb69-d2fbb70a9f74@slackbuilds.org>
References: <20180320194624.GA18699@comp.lan>
 <2555e8ed-5b77-2721-bb69-d2fbb70a9f74@slackbuilds.org>
Message-ID: <CAPsDuS6Pceqy-4VgnV+d6nb5midveL074cao0aotmJcH9oCfvQ@mail.gmail.com>

2018-03-31 3:19 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:
> we now have lua52/53 in the repo, so you can start testing it with newer lua

just be sure to apply these little fixes to the shipped pkgconfigs or
you will have trouble linking to the new versions (your application
will still try to link to lua-5.1.x).

https://git.slackbuilds.org/slackbuilds/commit/?id=13980bb08068f9faf8bfdbdcf1fb49b21f00a141
https://git.slackbuilds.org/slackbuilds/commit/?id=1e567891b7cd5968dfb28c572ffb67f760dde3da

Matteo

From zanculmarktum at gmail.com  Sat Mar 31 09:48:54 2018
From: zanculmarktum at gmail.com (Azure Zanculmarktum)
Date: Sat, 31 Mar 2018 16:48:54 +0700
Subject: [Slackbuilds-users] system/lsyncd requires Lua 5.2
Message-ID: <CAPbfrh+xVeZYNv17DygS0Kjw3=8_x4hwytMm1+pizXYBNFDs9g@mail.gmail.com>

>just be sure to apply these little fixes to the shipped pkgconfigs or
>you will have trouble linking to the new versions (your application
>will still try to link to lua-5.1.x).
>
>https://git.slackbuilds.org/slackbuilds/commit/?id=13980bb08068f9faf8bfdbdcf1fb49b21f00a141
>https://git.slackbuilds.org/slackbuilds/commit/?id=1e567891b7cd5968dfb28c572ffb67f760dde3da
>
>Matteo

You're right, just checked on debian/lua.pc.in, it has:
-llua5.x
instead of:
-llua

From navigium at grindcore.ch  Sat Mar 31 10:12:18 2018
From: navigium at grindcore.ch (Beni)
Date: Sat, 31 Mar 2018 12:12:18 +0200
Subject: [Slackbuilds-users] GeoGebra download link is broken
Message-ID: <4b9d03a1-4d39-6340-22d2-94193825acbd@grindcore.ch>

Hi all,

The GeoGebra slackbuild download link is broken. Downloading the latest 
version (of version 5 classic) via the link 
https://download.geogebra.org/package/linux-port works fine except that 
it doesn't result in a useful file name using wget.


I downloaded the GeoGebra version 5.0.451.0. Because of their weird file 
naming scheme the extracted folder uses the version string 5-0-451-0. If 
you change this in the SlackBuild script, it still works with said version.

I assume this is why the slackbuild provides a Dropbox download link. 
For an older GeoGebra version apparently SourceForge was used

https://sourceforge.net/projects/slackbuildsdirectlinks/files/GeoGebra/

Could the SlackBuild be updated and the files be added to this 
SourceForge repo?


Regards

Beni

From rsamurti at gmail.com  Sat Mar 31 11:01:08 2018
From: rsamurti at gmail.com (Ananda Murthy R S)
Date: Sat, 31 Mar 2018 11:01:08 +0000
Subject: [Slackbuilds-users] GeoGebra download link is broken
In-Reply-To: <4b9d03a1-4d39-6340-22d2-94193825acbd@grindcore.ch>
References: <4b9d03a1-4d39-6340-22d2-94193825acbd@grindcore.ch>
Message-ID: <CAMwjf3U5c6cGs5SpoqveOv4Cs_DNB-pXB6qpZA8gdPus2y6FUw@mail.gmail.com>

I will look into this and get back to you.

Anand

On Sat 31 Mar, 2018, 3:42 PM Beni, <navigium at grindcore.ch> wrote:

> Hi all,
>
> The GeoGebra slackbuild download link is broken. Downloading the latest
> version (of version 5 classic) via the link
> https://download.geogebra.org/package/linux-port works fine except that
> it doesn't result in a useful file name using wget.
>
>
> I downloaded the GeoGebra version 5.0.451.0. Because of their weird file
> naming scheme the extracted folder uses the version string 5-0-451-0. If
> you change this in the SlackBuild script, it still works with said version.
>
> I assume this is why the slackbuild provides a Dropbox download link.
> For an older GeoGebra version apparently SourceForge was used
>
> https://sourceforge.net/projects/slackbuildsdirectlinks/files/GeoGebra/
>
> Could the SlackBuild be updated and the files be added to this
> SourceForge repo?
>
>
> Regards
>
> Beni
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180331/be95e1c3/attachment-0001.html>

From didier at slint.fr  Sat Mar 31 11:23:37 2018
From: didier at slint.fr (Didier Spaier)
Date: Sat, 31 Mar 2018 13:23:37 +0200
Subject: [Slackbuilds-users] Error compiling webkitgtk
Message-ID: <6644e5a8-1ea1-53f2-08f5-3274850c001b@slint.fr>

Hello,

this is an answer to this email:
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2018-March/021041.html
that I didn't keep in my mailbox.

spaceman wrote:
>> I ma trying to compile webkit2gtk 2.8.26 statically and stripped
>> down, just to afterwards bundling it with yelp without this
>> resulting in a too huge package.
>
>I have managed to get a reasonably minimal (linked) build of 2.18.6
>going with the following config:
>
>  cmake -DPORT=GTK \
>        -DCMAKE_BUILD_TYPE=Release \
>        -DCMAKE_SKIP_RPATH=ON \
>        -DCMAKE_INSTALL_PREFIX=/usr \
>        -DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
>        -DENABLE_GEOLOCATION=false \
>        -DENABLE_SPELLCHECK=false \
>        -DENABLE_VIDEO=false \
>        -DENABLE_WEB_AUDIO=false \
>        -DENABLE_INDEXED_DATABASE=false \
>        -DENABLE_PLUGIN_PROCESS_GTK2=false \
>        -DENABLE_DRAG_SUPPORT=false \
>        -DENABLE_NOTIFICATIONS=false \
>        -DENABLE_WEBDRIVER=false \
>        -DENABLE_WEB_CRYPTO=false \
>        -DENABLE_ICONDATABASE=false \
>        -DUSE_SYSTEM_MALLOC=true \
>        -DUSE_LIBHYPHEN=false \
>        -DUSE_LIBNOTIFY=false \
>        -DUSE_LIBSECRET=false \
>        -DUSE_LIBWEBP=false \
>        -DLIB_INSTALL_DIR=/usr/lib${LIBDIRSUFFIX} \
>        -DLIBEXEC_INSTALL_DIR=/usr/lib${LIBDIRSUFFIX}/webkit2gtk-4.0 \
>        ..
>
>Try putting back opengl, jit or touch events, one of them (i think touch
>events suprisingly) caused my build to fail.

I failed to compile it statically and anyway it was a bad idea as the
size of the installed package would have been way too big.

Instead the attached SlackBuild put it in a non-standard location,
known only by yelp (SlackBuild also attached), rpath set to it  for the
linker in both packages.

I wish I could have built a smaller package, but 60M installed
is still less than 102M.

I failed to build a package for version 2.20 for an unknown reason,
but for this specific use case I don't think this matters much.

At least the help files associated to MATE applications among
others are displayed as expected. 

Have a nice day,

Didier



-------------- next part --------------
#!/bin/sh
# Avoid over heating if need be.
# Here the max frequecy allowed is 3500000, adapt to your hardware.
# echo 2500000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# Maintainer: Didier Spaier <didier~at~slint~dot~fr>
# This pacakage does not replace webkit2gtk.
# It is stripped down (60M installed instead of 102) and intede to be
# used only by yelp as private libraries. For this reason it is intalled
# in a non-standard location: /usr/libexec/yelp-webkit
CWD=$(pwd)
PKGNAME=webkit2gtk-private
SOURCE=webkitgtk
VERSION=2.18.6
BUILD=1slint
CWD=$(pwd)
PKGDIR=$CWD/package-$PKGNAME
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i586 ;;
    arm*) ARCH=arm ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi
rm -rf ${SOURCE}-$VERSION $PKGDIR
tar xf ${SOURCE}-${VERSION}.tar.xz
cd ${SOURCE}-$VERSION
chown -R root:root .
find -L . \
 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
  -o -perm 511 \) -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
rm -rf build
mkdir build
cd build
LIBDIRSUFFIX="64"
CFLAGS="-Wno-expansion-to-defined"
CXXFLAGS="-Wno-expansion-to-defined"
CXXFLAGS+=" -fno-delete-null-pointer-checks"
CFLAGS+=" -fno-delete-null-pointer-checks"
LDFLAGS="-Wl,-rpath,/usr/libexec/yelp-webkit/lib64" \
cmake \
-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_INSTALL_PREFIX=/usr/libexec/yelp-webkit \
-DCMAKE_SKIP_RPATH=ON \
-DENABLE_DRAG_SUPPORT=OFF \
-DENABLE_GEOLOCATION=OFF \
-DENABLE_ICONDATABASE=OFF \
-DENABLE_INDEXED_DATABASE=OFF \
-DENABLE_NOTIFICATIONS=OFF \
-DENABLE_PLUGIN_PROCESS_GTK2=OFF \
-DENABLE_SPELLCHECK=OFF \
-DENABLE_VIDEO=OFF \
-DENABLE_WEBDRIVER=OFF \
-DENABLE_WEB_AUDIO=OFF \
-DENABLE_WEB_CRYPTO=OFF \
-DLIBEXEC_INSTALL_DIR=/usr/libexec/yelp-webkit/lib${LIBDIRSUFFIX}/webkit2gtk-4.0 \
-DLIB_INSTALL_DIR=/usr/libexec/yelp-webkit/lib${LIBDIRSUFFIX} \
-DPORT=GTK \
-DUSE_LIBHYPHEN=OFF \
-DUSE_LIBNOTIFY=OFF \
-DUSE_LIBSECRET=OFF \
-DUSE_SYSTEM_MALLOC=ON \
-DENABLE_3D_TRANSFORMS=OFF \
-DENABLE_CHANNEL_MESSAGING=OFF \
-DENABLE_CONTEXT_MENUS=ON \
-DENABLE_OPENGL=OFF \
-DENABLE_JIT=OFF \
-DENABLE_DFG_JIT=OFF \
-DENABLE_DOWNLOAD_ATTRIBUTE=OFF \
-DENABLE_FETCH_API=ON \
-DENABLE_FTL_JIT=OFF \
-DENABLE_FULLSCREEN_API=ON \
-DENABLE_INDEXED_DATABASE_IN_WORKERS=OFF \
-DENABLE_INDIE_UI=OFF \
-DENABLE_INPUT_TYPE_COLOR=ON \
-DENABLE_INTERSECTION_OBSERVER=OFF \
-DENABLE_LEGACY_VENDOR_PREFIXES=OFF \
-DENABLE_MATHML=ON \
-DENABLE_MEDIA_CONTROLS_SCRIPT=OFF \
-DENABLE_NETSCAPE_PLUGIN_API=OFF \
-DENABLE_REMOTE_INSPECTOR=ON \
-DENABLE_STREAMS_API=ON \
-DENABLE_SUBTLE_CRYPTO=OFF \
-DENABLE_VIDEO_TRACK=OFF \
-DENABLE_WEBASSEMBLY=OFF \
-DENABLE_WEBGL=OFF \
.. 2>&1| tee ../../CONFIGLOG$PKGNAME-$VERSION-$ARCH-$BUILD$TAG
make -j 2 2>&1| tee ../../MAKELOG$PKGNAME-$VERSION-$ARCH-$BUILD$TAG|| return 1
make install DESTDIR=$PKGDIR

mkdir -p $PKGDIR/usr/doc/$PKGNAME-$VERSION
cp -a ../NEWS $PKGDIR/usr/doc/$PKGNAME-$VERSION
cat $CWD/$PKGNAME.SlackBuild > $PKGDIR/usr/doc/$PKGNAME-$VERSION/$PKGNAME.SlackBuild

mkdir -p $PKGDIR/install
cat $CWD/slack-desc > $PKGDIR/install/slack-desc

cd $PKGDIR
/sbin/makepkg -l y -c n $CWD/$PKGNAME-$VERSION-$ARCH-$BUILD.txz
-------------- next part --------------
#!/bin/sh

# Slackware build script for yelp

# Copyright 2014-2016 Willy Sudiarto Raharjo <willysr at slackbuilds.org>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

# Modified for Slint by Didier Spaier <didier~at~slint~dot~fr> for Slint.
# webkit2gtk is a build and run time dependency made private for yelp
# hence the rpath /usr/libexec/yelp-webkit/lib$ARCH
# This needs that webkit2ftk be installed there, and us the same rpath
# as it is auto-dependent at run time. 

PRGNAM=yelp
VERSION=3.26.0
BUILD=1
TAG=slint

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

CWD=$(pwd)
TMP=$CWD
PKG=$TMP/package-$PRGNAM
OUTPUT=$CWD

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

rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$VERSION
tar xvf $CWD/$PRGNAM-$VERSION.tar.xz

cd $PRGNAM-$VERSION

chown -R root:root .
find -L . \
 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
 -o -perm 511 \) -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
 -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

# Let's yelp know where to find its private run time dependencies
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
LDFLAGS="-Wl,-L/usr/libexec/yelp-webkit/lib$ARCH" \
LDFLAGS+="-Wl,-rpath,/usr/libexec/yelp-webkit/lib$ARCH" \
PKG_CONFIG_PATH="$PKG_CONFIG_PATH:/usr/libexec/yelp-webkit/lib$ARCH/pkgconfig" \
./configure \
  --prefix=/usr \
  --libdir=/usr/lib${LIBDIRSUFFIX} \
  --sysconfdir=/etc \
  --localstatedir=/var \
  --mandir=/usr/man \
  --docdir=/usr/doc/$PRGNAM-$VERSION \
  --enable-static=no \
  --disable-schemas-compile \
  --build=$ARCH-slackware-linux
make
make install DESTDIR=$PKG

find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \
  | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true

mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a AUTHORS COPYING* ChangeLog INSTALL NEWS README $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild

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

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xD50202EF60C03EEA.asc
Type: application/pgp-keys
Size: 1718 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180331/d7710f54/attachment.bin>

From andreas.guldstrand at gmail.com  Sat Mar 31 12:03:06 2018
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Sat, 31 Mar 2018 14:03:06 +0200
Subject: [Slackbuilds-users] libwacom-0.29.tar.bz2 md5sum failure
In-Reply-To: <20180315214000.GA27589@jdiamond-mb.acadiau.ca>
References: <20180315204623.GA25316@jdiamond-mb.acadiau.ca>
 <b4abc459-d632-6506-2601-53a8fe678749@slackbuilds.org>
 <20180315214000.GA27589@jdiamond-mb.acadiau.ca>
Message-ID: <CAEQ5t82JOAsgc+p_xNtbiCzTqWSaycWx+kzB27E2jp+Zj4e_4Q@mail.gmail.com>

On 15 March 2018 at 22:40, Jim Diamond <Jim.Diamond at acadiau.ca> wrote:
> On Fri, Mar 16, 2018 at 04:07 (+0700), Willy Sudiarto Raharjo wrote:
>
>>> Are you sure you wish to continue? [y]
>>> --2018-03-15 17:45:20--  https://sourceforge.net/projects/linuxwacom/files/libwacom/libwacom-0.29.tar.bz2
>>> Resolving sourceforge.net... 216.105.38.13
>
> <snip>
>
>>> --2018-03-15 17:45:21--  ftp://slackware.uk/sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681/libwacom-0.29.tar.bz2
>>>            => ?libwacom-0.29.tar.bz2?
>>> Resolving slackware.uk... 91.109.244.240
>>> Connecting to slackware.uk|91.109.244.240|:21... connected.
>>> Logging in as anonymous ... Logged in!
>>> ==> SYST ... done.    ==> PWD ... done.
>>> ==> TYPE I ... done.  ==> CWD (1) /sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681 ...
>>> No such directory ?sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681?.
>
>>> Unable to download/verify source file(s) for libwacom:
>>> md5sum failure for /usr/local/poo/usr-sbo-142/distfiles/libwacom-0.29.tar.bz2.
>
>> libwacom works fine here
>
>> Connecting to excellmedia.dl.sourceforge.net
>> (excellmedia.dl.sourceforge.net)|202.153.32.19|:443... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: 495549 (484K) [application/octet-stream]
>> Saving to: ?libwacom-0.29.tar.bz2?
>
>> libwacom-0.29.tar.b 100%[===================>] 483.93K   567KB/s    in
>> 0.9s
>
>> 2018-03-16 04:04:10 (567 KB/s) - ?libwacom-0.29.tar.bz2? saved
>> [495549/495549]
>
>> Found libwacom-0.29.tar.bz2 in /data/source.
>> Checking MD5SUM:
>> MD5SUM check for libwacom-0.29.tar.bz2 ... OK
>
> Hmmm... you went to sourceforge.  sboupgrade sent me to
>     ftp://slackware.uk/sbosrcarch/by-md5/3/a/3a6b614b57518b25a102dcd9e51d6681
> which, indeed, does not currently exist.

Actually, sboupgrade tried sourceforge first:

On 15 March 2018 at 21:46, Jim Diamond <Jim.Diamond at acadiau.ca> wrote:
> Are you sure you wish to continue? [y]
> --2018-03-15 17:45:20--  https://sourceforge.net/projects/linuxwacom/files/libwacom/libwacom-0.29.tar.bz2
> Resolving sourceforge.net... 216.105.38.13
> Connecting to sourceforge.net|216.105.38.13|:443... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: https://sourceforge.net/projects/linuxwacom/files/libwacom/libwacom-0.29.tar.bz2/download [following]
> --2018-03-15 17:45:20--  https://sourceforge.net/projects/linuxwacom/files/libwacom/libwacom-0.29.tar.bz2/download
> Connecting to sourceforge.net|216.105.38.13|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 457344 (447K) [text/html]
> Saving to: ?libwacom-0.29.tar.bz2?
>
> libwacom-0.29.tar.bz 100%[===================>] 446.62K  1.08MB/s    in 0.4s
>
> 2018-03-15 17:45:21 (1.08 MB/s) - ?libwacom-0.29.tar.bz2? saved [457344/457344]

but the sourceforge link must not have verified via the md5sum, so it
tried to get it from slackware.uk's sbosrcarch instead, but the
attempt by the sbosrcarch script to download the file must not have
worked either - otherwise the directory and the file would exist
there, but since it doesn't exist there it must have failed.

I'm not sure why it worked for willy to download it from sourceforge
though. If you compare the downloads from sourceforge by willy and
you, there are several differences.

* First of all willy is connecting to excellmedia.dl.sourceforge.net
while you're connecting to sourceforge.net. I have no idea where willy
got the excellmedia.dl.sourceforge.net link from, it's not in the
.info file.
* Secondly, your connection gets redirected by sourceforge (that's the
302 Found line), willy's does not.
* Thirdly, when you do download it, sourceforge tells you it's a
text/html file of length 447K, while willy's download is an
application/octet-stream of length 484K.

I have no idea why sourceforge is giving out completely different
things to you and willy, but I would assume it has something to do
with where willy found the excellmedia.dl.sourceforge.net link from.

From willysr at slackbuilds.org  Sat Mar 31 14:25:13 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 31 Mar 2018 21:25:13 +0700
Subject: [Slackbuilds-users] libwacom-0.29.tar.bz2 md5sum failure
In-Reply-To: <CAEQ5t82JOAsgc+p_xNtbiCzTqWSaycWx+kzB27E2jp+Zj4e_4Q@mail.gmail.com>
References: <20180315204623.GA25316@jdiamond-mb.acadiau.ca>
 <b4abc459-d632-6506-2601-53a8fe678749@slackbuilds.org>
 <20180315214000.GA27589@jdiamond-mb.acadiau.ca>
 <CAEQ5t82JOAsgc+p_xNtbiCzTqWSaycWx+kzB27E2jp+Zj4e_4Q@mail.gmail.com>
Message-ID: <1d963547-a607-5463-4d14-142bea93e100@slackbuilds.org>

> I'm not sure why it worked for willy to download it from sourceforge
> though. If you compare the downloads from sourceforge by willy and
> you, there are several differences.
> 
> * First of all willy is connecting to excellmedia.dl.sourceforge.net
> while you're connecting to sourceforge.net. I have no idea where willy
> got the excellmedia.dl.sourceforge.net link from, it's not in the
> .info file.
> * Secondly, your connection gets redirected by sourceforge (that's the
> 302 Found line), willy's does not.
> * Thirdly, when you do download it, sourceforge tells you it's a
> text/html file of length 447K, while willy's download is an
> application/octet-stream of length 484K.
> 
> I have no idea why sourceforge is giving out completely different
> things to you and willy, but I would assume it has something to do
> with where willy found the excellmedia.dl.sourceforge.net link from.

Since sourceforge is mirrored through different servers, we will get a
different location closest to us. In most cases, i always get Taiwan or
Japan, but this time, i got excellmedia which is in India.
By stating it explicitly through excellmedia, it will be a direct
download instead of going through their round-robin load balancer.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180331/a155860b/attachment-0001.asc>

From arkadiusz at drabczyk.org  Sat Mar 31 16:38:45 2018
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Sat, 31 Mar 2018 18:38:45 +0200
Subject: [Slackbuilds-users] system/lsyncd requires Lua 5.2
In-Reply-To: <CAPsDuS6Pceqy-4VgnV+d6nb5midveL074cao0aotmJcH9oCfvQ@mail.gmail.com>
References: <20180320194624.GA18699@comp.lan>
 <2555e8ed-5b77-2721-bb69-d2fbb70a9f74@slackbuilds.org>
 <CAPsDuS6Pceqy-4VgnV+d6nb5midveL074cao0aotmJcH9oCfvQ@mail.gmail.com>
Message-ID: <20180331163845.GA31065@comp.lan>

On Sat, Mar 31, 2018 at 10:32:16AM +0200, Matteo Bernardini wrote:
> 2018-03-31 3:19 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:
> > we now have lua52/53 in the repo, so you can start testing it with newer lua
> 
> just be sure to apply these little fixes to the shipped pkgconfigs or
> you will have trouble linking to the new versions (your application
> will still try to link to lua-5.1.x).
> 
> https://git.slackbuilds.org/slackbuilds/commit/?id=13980bb08068f9faf8bfdbdcf1fb49b21f00a141
> https://git.slackbuilds.org/slackbuilds/commit/?id=1e567891b7cd5968dfb28c572ffb67f760dde3da

Thanks everyone for help, I've just pushed lsyncd 2.2.3 for review.
I've tested it and seems to work fine with lua53.
-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From s.arcus at open-t.co.uk  Sat Mar 31 18:33:59 2018
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Sat, 31 Mar 2018 19:33:59 +0100
Subject: [Slackbuilds-users] No taskbar icon for Brave browser
Message-ID: <6fbff26b-cb53-beb7-820b-82402b91f1eb@open-t.co.uk>

I'm reposting this issue, in case it got lost with the recent DMARC 
disruption. I've installed the Brave browser, and in Fluxbox, there is 
no icon on the taskbar window label, while it is running. I can't find 
some online info as to what controls this? Could this be an issue with 
packaging Brave itself, or is it specific to Fluxbox - or what controls 
those icons which appear next to the windows names in the taskbar, while 
the application is running?

Any hints much appreciated.

From lspencer31 at cfl.rr.com  Sat Mar 31 21:10:50 2018
From: lspencer31 at cfl.rr.com (Lenard Spencer)
Date: Sat, 31 Mar 2018 17:10:50 -0400
Subject: [Slackbuilds-users] Patch for k9copy-reloaded for -current
Message-ID: <94839ee2-3e36-ca7d-24f6-f9ffff04985e@cfl.rr.com>

This is a patch for the k9copy-reloaded SBo script to enable it to build 
on -current/15.0.? This should only be applied in Matteo's branch.? Thanks.

-------------------------------------------------------------------------------------------------------

diff -Naur k9copy-reloaded/README k9copy-reloaded.new/README
--- k9copy-reloaded/README??? 2018-03-26 11:18:28.000000000 -0400
+++ k9copy-reloaded.new/README??? 2018-03-31 17:06:22.622971383 -0400
@@ -16,7 +16,6 @@
 ?intended for copying of copyrighted commercial DVDs.? Therefore, there
 ?is NO CSS decription libary included in this package.

-Requires libmpeg2, dvdauthor
+Requires libmpeg2, dvdauthor, and gcc5

 ?http://k9copy-reloaded.sourceforge.net
-
diff -Naur k9copy-reloaded/k9copy-reloaded.SlackBuild 
k9copy-reloaded.new/k9copy-reloaded.SlackBuild
--- k9copy-reloaded/k9copy-reloaded.SlackBuild??? 2018-03-31 
16:58:18.968151120 -0400
+++ k9copy-reloaded.new/k9copy-reloaded.SlackBuild??? 2018-03-31 
17:05:19.067463726 -0400
@@ -2,7 +2,7 @@

 ?# Slackware build script for k9copy-reloaded

-# Copyright 2016 by Lenard Spencer (lspencer31-at-cfl-rr-com)
+# Copyright 2018 by Lenard Spencer (lspencer31-at-cfl-rr-com)
 ?# All rights reserved.
 ?#
 ?# ffmpeg static library section borrowed (stolen?) from 
xine-lib.SlackBuild
@@ -29,11 +29,10 @@
 ?PRGNAM=k9copy-reloaded
 ?SRCNAM=k9copy
 ?VERSION=${VERSION:-3.0.3}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2}
 ?FFMPEG_VERSION=${FFMPEG_VERSION:-2.8.13}
 ?TAG=${TAG:-_SBo}

-# Automatically determine the architecture we're building on:
 ?if [ -z "$ARCH" ]; then
 ?? case "$( uname -m )" in
 ???? i?86) ARCH=i586 ;;
@@ -68,12 +67,22 @@
 ?? FFARCHOPTS=""
 ?fi

-set -e # Exit on most errors
+set -e

 ?rm -rf $PKG
 ?mkdir -p $TMP $PKG $OUTPUT
 ?cd $TMP

+# check for gcc5 and abort if not found:
+if ! [ -x /usr/bin/gcc-5 ]; then
+? echo "Cannot find the gcc5 package.? Please install the gcc5 package"
+? echo "and rerun the SlackBuild script."
+? exit 1
+fi
+
+# Set gcc-5 vars to make it build with gcc5:
+source /etc/profile.d/gcc5.sh
+
 ?rm -rf ffmpeg*
 ?tar xvf $CWD/ffmpeg-$FFMPEG_VERSION.tar.?z* || exit 1
 ?cd ffmpeg* || exit 1
@@ -93,6 +102,12 @@
 ?? CXXFLAGS="$SLKCFLAGS -fvisibility=hidden -I/usr/include/openmj2-2.1" \
 ?? ./configure \
 ???? --prefix=$FFMPEGDIR/usr \
+??? --cc=gcc-5 \
+??? --cxx=g++-5 \
+??? --ar=gcc-ar-5 \
+??? --nm=gcc-nm-5 \
+??? --ranlib=gcc-ranlib-5 \
+??? --dep-cc=gcc-5 \
 ???? --libdir=$FFMPEGDIR/usr/lib${LIBDIRSUFFIX} \
 ???? --shlibdir=$FFMPEGDIR/usr/lib${LIBDIRSUFFIX} \
 ???? --enable-gpl \
diff -Naur k9copy-reloaded/k9copy-reloaded.info 
k9copy-reloaded.new/k9copy-reloaded.info
--- k9copy-reloaded/k9copy-reloaded.info??? 2017-12-04 
15:04:49.000000000 -0500
+++ k9copy-reloaded.new/k9copy-reloaded.info??? 2018-03-31 
17:02:14.924988370 -0400
@@ -7,6 +7,6 @@
 ???????? 9a0c752a490f7e30476eb46948a36d0e"
 ?DOWNLOAD_x86_64=""
 ?MD5SUM_x86_64=""
-REQUIRES="dvdauthor libmpeg2"
+REQUIRES="dvdauthor libmpeg2 gcc5"
 ?MAINTAINER="Lenard Spencer"
 ?EMAIL="lspencer31-at-cfl-rr-com"