From gen-bch at useyouresp.org.uk  Thu Jun  1 08:18:27 2017
From: gen-bch at useyouresp.org.uk (Habs)
Date: Thu, 1 Jun 2017 09:18:27 +0100
Subject: [Slackbuilds-users] icecat 52.1.0 build error
Message-ID: <20170601091827.08c94543@dv6920ea.localdomain>

Hello melikamp, good morning to all

I have just tried the icecat build and it quit after the following
message:

.
.
.
icecat/platform.ini
cp: cannot stat '[...]/icecat/Changelog.*': No
such file or directory



It seems to be because of a 'cp' of $CWD/README* and $CWD/Changelog.*,
where there is no Changelog.* in the CWD.

As a test, I removed the Changelog.* part and it was ok.  Is that bit
significant, or just an artifact from your setup ?


Thank you
Habs

From willysr at slackbuilds.org  Thu Jun  1 08:32:51 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 1 Jun 2017 15:32:51 +0700
Subject: [Slackbuilds-users] icecat 52.1.0 build error
In-Reply-To: <20170601091827.08c94543@dv6920ea.localdomain>
References: <20170601091827.08c94543@dv6920ea.localdomain>
Message-ID: <67124a34-a176-163f-8509-4585dfce4b92@slackbuilds.org>

> Hello melikamp, good morning to all
> 
> I have just tried the icecat build and it quit after the following
> message:
> .
> icecat/platform.ini
> cp: cannot stat '[...]/icecat/Changelog.*': No
> such file or directory
> 
> It seems to be because of a 'cp' of $CWD/README* and $CWD/Changelog.*,
> where there is no Changelog.* in the CWD.
> 
> As a test, I removed the Changelog.* part and it was ok.  Is that bit
> significant, or just an artifact from your setup ?

It has been fixed on my branch few hours ago


-- 
Willy Sudiarto Raharjo

-------------- 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/20170601/07ecd6cd/attachment.asc>

From gen-bch at useyouresp.org.uk  Thu Jun  1 08:43:59 2017
From: gen-bch at useyouresp.org.uk (Habs)
Date: Thu, 1 Jun 2017 09:43:59 +0100
Subject: [Slackbuilds-users] icecat 52.1.0 build error
In-Reply-To: <67124a34-a176-163f-8509-4585dfce4b92@slackbuilds.org>
References: <20170601091827.08c94543@dv6920ea.localdomain>
 <67124a34-a176-163f-8509-4585dfce4b92@slackbuilds.org>
Message-ID: <20170601094359.36981d1b@dv6920ea.localdomain>

On Thu, 1 Jun 2017 15:32:51 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> > Hello melikamp, good morning to all
> > 
> > I have just tried the icecat build and it quit after the following
> > message:
> > .
> > icecat/platform.ini
> > cp: cannot stat '[...]/icecat/Changelog.*': No
> > such file or directory
> > 
> > It seems to be because of a 'cp' of $CWD/README* and
> > $CWD/Changelog.*, where there is no Changelog.* in the CWD.
> > 
> > As a test, I removed the Changelog.* part and it was ok.  Is that
> > bit significant, or just an artifact from your setup ?  
> 
> It has been fixed on my branch few hours ago
> 
> 

Hi - excellent, thank you....what was the 'fix' please ?  

(apologies, i am not familiar with branches etc yet, to go check
there...i just use the website)

From willysr at slackbuilds.org  Thu Jun  1 08:45:24 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 1 Jun 2017 15:45:24 +0700
Subject: [Slackbuilds-users] icecat 52.1.0 build error
In-Reply-To: <20170601094359.36981d1b@dv6920ea.localdomain>
References: <20170601091827.08c94543@dv6920ea.localdomain>
 <67124a34-a176-163f-8509-4585dfce4b92@slackbuilds.org>
 <20170601094359.36981d1b@dv6920ea.localdomain>
Message-ID: <8f711f01-c75d-a8e8-5c36-208b7ef1f98d@slackbuilds.org>

> Hi - excellent, thank you....what was the 'fix' please ?  
> 
> (apologies, i am not familiar with branches etc yet, to go check
> there...i just use the website)

Probably it's easier to see it here:
https://slackbuilds.org/ready/

you can click on the commit ID to get you to the real commit


-- 
Willy Sudiarto Raharjo

-------------- 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/20170601/d2505c76/attachment.asc>

From gen-bch at useyouresp.org.uk  Thu Jun  1 08:52:38 2017
From: gen-bch at useyouresp.org.uk (Habs)
Date: Thu, 1 Jun 2017 09:52:38 +0100
Subject: [Slackbuilds-users] icecat 52.1.0 build error
In-Reply-To: <8f711f01-c75d-a8e8-5c36-208b7ef1f98d@slackbuilds.org>
References: <20170601091827.08c94543@dv6920ea.localdomain>
 <67124a34-a176-163f-8509-4585dfce4b92@slackbuilds.org>
 <20170601094359.36981d1b@dv6920ea.localdomain>
 <8f711f01-c75d-a8e8-5c36-208b7ef1f98d@slackbuilds.org>
Message-ID: <20170601095238.45e20246@dv6920ea.localdomain>

On Thu, 1 Jun 2017 15:45:24 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> > Hi - excellent, thank you....what was the 'fix' please ?  
> > 
> > (apologies, i am not familiar with branches etc yet, to go check
> > there...i just use the website)  
> 
> Probably it's easier to see it here:
> https://slackbuilds.org/ready/
> 
> you can click on the commit ID to get you to the real commit
> 
> 

thank you - bookmarked! :-)  have a nice day all.

From melikamp at melikamp.com  Thu Jun  1 16:13:09 2017
From: melikamp at melikamp.com (Ivan Zaigralin)
Date: Thu, 01 Jun 2017 09:13:09 -0700
Subject: [Slackbuilds-users] icecat 52.1.0 build error
In-Reply-To: <8f711f01-c75d-a8e8-5c36-208b7ef1f98d@slackbuilds.org>
References: <20170601091827.08c94543@dv6920ea.localdomain>
 <20170601094359.36981d1b@dv6920ea.localdomain>
 <8f711f01-c75d-a8e8-5c36-208b7ef1f98d@slackbuilds.org>
Message-ID: <1790010.Tp3gnWaNfg@ithil>

Willy, thanks for fixing that so promptly.

I think I submitted the build with another README as well as Changlog, but 
they got removed along the way? The binary build it's based on does not 
contain these very informative text files, they are in icecat source tarball 
only, and extracting them from source tarball seemed silly, so I figured, 
include them in the slackbuild.

Of course, it's just docs, so nothing functional is affected this way.

On Thursday, June 01, 2017 15:45:24 Willy Sudiarto Raharjo wrote:
> > Hi - excellent, thank you....what was the 'fix' please ?
> > 
> > (apologies, i am not familiar with branches etc yet, to go check
> > there...i just use the website)
> 
> Probably it's easier to see it here:
> https://slackbuilds.org/ready/
> 
> you can click on the commit ID to get you to the real commit
> 
> 
> --
> Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170601/f2417c07/attachment.asc>

From harald.achitz at gmail.com  Thu Jun  1 16:35:36 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Thu, 1 Jun 2017 18:35:36 +0200
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
Message-ID: <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>

Thanks for the info Andrzej
unfortunately I am not optimistic that soon for Qt, sbo will run a sane
version politic,
The current maintainer showed more or less that he/she does not care to
much and/or does not understand why a LTS version strategy is the right
thing for a distribution like Slackware.
So sbo has always some version of Qt onboard, and the do it yourself
approach is required.
This is of course my personal opinion that reflects, or not, the reality ;-)
I will update my 5.6.2 build to 5.9 on the weekend, thanks for mentioning
the pcre2 note!

/Harald



2017-05-31 23:19 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:

> Hi,
>
> Just to let you know, Qt 5.9 LTS has been released.
> If you plan to update the SBo version, pcre2 should be added to REQUIRES,
> otherwise, the bundled source for pcre2 will be used.
>
> Not that I built Qt 5.9 or tested it or whatever.
> Just a heads up.
>
> Cheers.
>
> --
> Best regards,
> Andrzej Telszewski
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170601/ce58aaab/attachment-0001.html>

From willysr at slackbuilds.org  Thu Jun  1 17:31:39 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 2 Jun 2017 00:31:39 +0700
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
 <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
Message-ID: <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>

> Thanks for the info Andrzej
> unfortunately I am not optimistic that soon for Qt, sbo will run a sane
> version politic,
> The current maintainer showed more or less that he/she does not care to
> much and/or does not understand why a LTS version strategy is the right
> thing for a distribution like Slackware.
> So sbo has always some version of Qt onboard, and the do it yourself
> approach is required.
> This is of course my personal opinion that reflects, or not, the reality ;-)
> I will update my 5.6.2 build to 5.9 on the weekend, thanks for mentioning
> the pcre2 note!

That will have to be decided by qt5 maintainer (Larry)
My suggestion (suppose we bump to 5.9) is to place them on -review
branch first and see if other scripts are working fine with it. If it
turns out to be OK, we can then merge it into master and 14.2.

based on rough count, we have more than 60 other scripts depending on
qt5 for hard dep and probably more with optional dep. That will take
some time to test.

-- 
Willy Sudiarto Raharjo

-------------- 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/20170602/fb9a54db/attachment.asc>

From atelszewski at gmail.com  Thu Jun  1 19:06:34 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 1 Jun 2017 21:06:34 +0200
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
 <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
 <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>
Message-ID: <f85503aa-6e63-a64e-7477-320df524dc64@gmail.com>

On 01/06/17 19:31, Willy Sudiarto Raharjo wrote:
>> Thanks for the info Andrzej
>> unfortunately I am not optimistic that soon for Qt, sbo will run a sane
>> version politic,
>> The current maintainer showed more or less that he/she does not care to
>> much and/or does not understand why a LTS version strategy is the right
>> thing for a distribution like Slackware.
>> So sbo has always some version of Qt onboard, and the do it yourself
>> approach is required.
>> This is of course my personal opinion that reflects, or not, the reality ;-)
>> I will update my 5.6.2 build to 5.9 on the weekend, thanks for mentioning
>> the pcre2 note!
> 
> That will have to be decided by qt5 maintainer (Larry)
> My suggestion (suppose we bump to 5.9) is to place them on -review
> branch first and see if other scripts are working fine with it. If it
> turns out to be OK, we can then merge it into master and 14.2.
> 
> based on rough count, we have more than 60 other scripts depending on
> qt5 for hard dep and probably more with optional dep. That will take
> some time to test.
> 
> 

Hi,

I'm fine with whatever Larry decides.
My only intent was to let you know the thing ;-)

-- 
Best regards,
Andrzej Telszewski

From rshepard at appl-ecosys.com  Fri Jun  2 15:40:34 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 2 Jun 2017 08:40:34 -0700 (PDT)
Subject: [Slackbuilds-users] Building glabels on 14.1
Message-ID: <alpine.LNX.2.11.1706020836180.15709@localhost>

   I tried to build glabels-3.4.0 on my -14.1/x86 workstation and learned
that several libraries need newer versions:

Requested 'glib-2.0 >= 2.42.0' but version of GLib is 2.36.4
Requested 'gtk+-3.0 >= 3.14.0' but version of GTK+ is 3.8.2
Requested 'librsvg-2.0 >= 2.39.0' but version of librsvg is 2.36.4

   Apparently there is no earlier version for 14.1, only 3.4.0 for 14.2. I
can upgrade gtk+3 and librsvg, yet I assume that an upgrade to glib requires
a kernel upgrade. Is this correct?

   I'd appreciate suggestions for building a working glabel on this system.

Regards,

Rich

From willysr at slackbuilds.org  Fri Jun  2 15:45:13 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 2 Jun 2017 22:45:13 +0700
Subject: [Slackbuilds-users] Building glabels on 14.1
In-Reply-To: <alpine.LNX.2.11.1706020836180.15709@localhost>
References: <alpine.LNX.2.11.1706020836180.15709@localhost>
Message-ID: <a3d2f1a8-262c-302d-0dbf-a0bad5324fb6@slackbuilds.org>

>   I tried to build glabels-3.4.0 on my -14.1/x86 workstation and learned
> that several libraries need newer versions:
> 
> Requested 'glib-2.0 >= 2.42.0' but version of GLib is 2.36.4
> Requested 'gtk+-3.0 >= 3.14.0' but version of GTK+ is 3.8.2
> Requested 'librsvg-2.0 >= 2.39.0' but version of librsvg is 2.36.4
> 
>   Apparently there is no earlier version for 14.1, only 3.4.0 for 14.2. I
> can upgrade gtk+3 and librsvg, yet I assume that an upgrade to glib
> requires
> a kernel upgrade. Is this correct?
> 
>   I'd appreciate suggestions for building a working glabel on this system.

No, there are 2 libraries which has similar names: glibc and glib

GLib is a library which includes support routines for C such as lists,
trees, hashes, memory allocation, and many other things.

glibc is the GNU C libraries and header files.

Since upgrading GTK stack requires a lot of efforts since there are lots
of components related AND affected by it, i would recommend to stick
with the current version of glabel for 14.1 or upgrade to 14.2.

-- 
Willy Sudiarto Raharjo

-------------- 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/20170602/4521bb62/attachment.asc>

From rshepard at appl-ecosys.com  Fri Jun  2 15:51:17 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 2 Jun 2017 08:51:17 -0700 (PDT)
Subject: [Slackbuilds-users] Building glabels on 14.1
In-Reply-To: <a3d2f1a8-262c-302d-0dbf-a0bad5324fb6@slackbuilds.org>
References: <alpine.LNX.2.11.1706020836180.15709@localhost>
 <a3d2f1a8-262c-302d-0dbf-a0bad5324fb6@slackbuilds.org>
Message-ID: <alpine.LNX.2.11.1706020849050.15709@localhost>

On Fri, 2 Jun 2017, Willy Sudiarto Raharjo wrote:

> No, there are 2 libraries which has similar names: glibc and glib

Willy,

   I realized this after sending the message.

> Since upgrading GTK stack requires a lot of efforts since there are lots
> of components related AND affected by it, i would recommend to stick
> with the current version of glabel for 14.1 or upgrade to 14.2.

   There is no SBo glabel package displayed for 14.1. I'll download the
source for glabel-3.2.1 and try that with the SBo build script.

   When time permits I'll finish connecting cables in the new
server/workstation and put 14.2 on it.

Thanks,

Rich

From rshepard at appl-ecosys.com  Fri Jun  2 16:03:54 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 2 Jun 2017 09:03:54 -0700 (PDT)
Subject: [Slackbuilds-users] Building glabels on 14.1
In-Reply-To: <alpine.LNX.2.11.1706020849050.15709@localhost>
References: <alpine.LNX.2.11.1706020836180.15709@localhost>
 <a3d2f1a8-262c-302d-0dbf-a0bad5324fb6@slackbuilds.org>
 <alpine.LNX.2.11.1706020849050.15709@localhost>
Message-ID: <alpine.LNX.2.11.1706020902220.15709@localhost>

On Fri, 2 Jun 2017, Rich Shepard wrote:

> There is no SBo glabel package displayed for 14.1. I'll download the
> source for glabel-3.2.1 and try that with the SBo build script.

   The earlier version builds with a change in version number to the build
script. It will be interesting to see how well glabels works at creating
business cards.

Carpe weekend all,

Rich

From slacker6896 at gmail.com  Fri Jun  2 16:41:54 2017
From: slacker6896 at gmail.com (Sebastien BALLET)
Date: Fri, 2 Jun 2017 18:41:54 +0200
Subject: [Slackbuilds-users] question about libjvm.so symlinks
Message-ID: <CAA2+phGREWw9SEMDrM=to1LsSqJiGXACU7QDFMoub5cjTkDApQ@mail.gmail.com>

Hello,

I would like to know if there is any (documented) reasons why the
slackbuilds for (open)jdk create the symlinks below.

jdk.SlackBuild:
cd $PKG/usr/lib${LIBDIRSUFFIX}
    ln -sf ./java/jre/lib/${LIB_ARCH}/server/libjvm.so .

openjdk.SlackBuild:
cd $PKG/usr/lib${LIBDIRSUFFIX}
 ln -sf ./$PRGNAM/jre/lib/${LIB_ARCH}/server/libjvm.so .

I've search the web and didn't find anything conclusive about that. In
fact, it seems that symlink is not needed and is more a hack used to fix
some specific issues.


Thanks.

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

From info at microlinux.fr  Fri Jun  2 18:41:09 2017
From: info at microlinux.fr (Nicolas Kovacs)
Date: Fri, 2 Jun 2017 20:41:09 +0200
Subject: [Slackbuilds-users] Building glabels on 14.1
In-Reply-To: <alpine.LNX.2.11.1706020836180.15709@localhost>
References: <alpine.LNX.2.11.1706020836180.15709@localhost>
Message-ID: <4e7b3319-09b2-3baa-ce96-2504adfb8b52@microlinux.fr>

Le 02/06/2017 ? 17:40, Rich Shepard a ?crit :
>   I tried to build glabels-3.4.0 on my -14.1/x86 workstation and learned
> that several libraries need newer versions:

On a side note: GtkCDLabel is a nifty application for CD labels. I've
been using it for the last twelve years or so. It's a bit quirky, but
once you get the hang of it, it's nice to use.

Cheers,

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32

From rshepard at appl-ecosys.com  Fri Jun  2 18:51:39 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 2 Jun 2017 11:51:39 -0700 (PDT)
Subject: [Slackbuilds-users] Building glabels on 14.1
In-Reply-To: <4e7b3319-09b2-3baa-ce96-2504adfb8b52@microlinux.fr>
References: <alpine.LNX.2.11.1706020836180.15709@localhost>
 <4e7b3319-09b2-3baa-ce96-2504adfb8b52@microlinux.fr>
Message-ID: <alpine.LNX.2.11.1706021149390.15709@localhost>

On Fri, 2 Jun 2017, Nicolas Kovacs wrote:

> On a side note: GtkCDLabel is a nifty application for CD labels. I've been
> using it for the last twelve years or so. It's a bit quirky, but once you
> get the hang of it, it's nice to use.

Niki,

   Good to know if I ever again need to print CD labels. :-)

   LibreOffice has a business card template, but it's very quirky and has no
support in the only downloadable document, the 'starter guide.' When I post
a use question on their mail list it's ignored. So, time to change tools. If
I don't like glabel I'll use LaTeX.

Carpe weekend,

Rich

From andrew.m.goth at gmail.com  Fri Jun  2 21:37:32 2017
From: andrew.m.goth at gmail.com (Andy Goth)
Date: Fri, 2 Jun 2017 16:37:32 -0500
Subject: [Slackbuilds-users] Submission status
In-Reply-To: <CAMQNOSmXA0OE73cJ36aAFH5KETGvymJqsE-D_Oh4fyxG3EsW9g@mail.gmail.com>
References: <CAMQNOSmQhqTE0T_ZtP9rmhkqqw96sQe-5heQLf5JE99FLrM+tQ@mail.gmail.com>
 <CAMQNOS=CCJ2DBgHUG39p9OeCHTkYPs7E-ztTXNEcgWX39bxLwA@mail.gmail.com>
 <CAMQNOSm-KgWeDGv1YZh=EEmML+N=0ArtS_oquTc_taVJP+4TGg@mail.gmail.com>
 <CAMQNOSnDJOeH5+i745bRLiMuRRZzWT+ZfCpPBdaddu7KPr9fuA@mail.gmail.com>
 <CAMQNOSnSoEg5qjyQirrqticgeDY7nnc+G0yHAf-wyw0Ad7rxcg@mail.gmail.com>
 <CAMQNOS=9zpqDvdeubiUdXJv5Pf8CArAB=KjT_63CA=eCpgBO6A@mail.gmail.com>
 <CAPsDuS7xGBMY9554BZw6y5h7Jh9iTOCU2KUt5Cdt=zY=u6_ffQ@mail.gmail.com>
 <CAMQNOSmXA0OE73cJ36aAFH5KETGvymJqsE-D_Oh4fyxG3EsW9g@mail.gmail.com>
Message-ID: <CAMQNOSnJOHLnizB_MD7_CXKoWUcqYZzu+cBVFDfggtgOvWKRvA@mail.gmail.com>

Sorry for the very long delay. Business travel kept me on the road and away
from the laptop which had my Slackbuilds development. Then when I finally
got to it, I discovered the reason I sent the old version twice was that I
had wiped the new one. Luckily I was able to piece together my Vim undo
files to get back what I had lost.

Resubmitted, and thank you for bearing with me.

On Fri, May 19, 2017 at 3:09 PM, Andy Goth <andrew.m.goth at gmail.com> wrote:

> Tomorrow I will be able to look into this. I'm sorry if I sent the wrong
> version, in which case I'll be sure to resubmit my latest (after merging in
> any changes you may have made). Thanks for checking.
>
> On May 19, 2017 15:06, "Matteo Bernardini" <matteo.bernardini at gmail.com>
> wrote:
>
>> 2017-05-19 21:18 GMT+02:00 Andy Goth <andrew.m.goth at gmail.com>:
>> > On April 13 I submitted a SlackBuild script update for Fossil version
>> 2.2
>> > and received the following email:
>> >
>> > New upload: fossil.tar.gz
>> > Category: Development
>> > Submission md5: eed5f9be7df09f9cf663d5b7ce84dabb
>> >
>> > What is the status of this submission? I do not see it in the pending
>> queue,
>> > nor is it in the accepted submission list.
>> >
>> > I'm not subscribed to the list, so please Cc: me on replies.
>>
>> Hi Andy,
>>
>> I had a look at the notifying emails we got about the submissions and
>> found this
>>
>> - - -
>> New upload: fossil.tar.gz (<your_email>)
>> Maintainer: Andy Goth
>> Email: <your_email>
>> Category: Development
>> Keywords:
>> Version: 2.1 (db: 2.1)
>> Home Page: https://www.fossil-scm.org/
>> Sources (32bit): http://fossil-scm.org/index.ht
>> ml/uv/fossil-src-2.1.tar.gz
>> MD5SUMS
>> <http://fossil-scm.org/index.html/uv/fossil-src-2.1.tar.gzMD5SUMS>
>> (32bit): 9f32b23cecb092d42cdf11bf003ebf8d
>> Sources (64bit):
>> MD5SUMS (64bit):
>> Requires:
>> Slackware: 14.2
>> Submission md5: eed5f9be7df09f9cf663d5b7ce84dabb
>> Comments:
>> - - -
>>
>> looking just at it seems like it was about the same version you
>> submitted a few days earlier and that got approved on the same day,
>> april 13th
>>
>> https://git.slackbuilds.org/slackbuilds/commit/?id=e5a9375ea
>> 1cc08fa3ff8bb0d41fa948f28b295be
>>
>> if it's ok for you, once submissions will reopen, could you please
>> resubmit it, rebasing your changes on what we have now in the
>> repository?
>>
>> Matteo
>>
>


-- 
Andy Goth | <andrew.m.goth/at/gmail/dot/com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170602/93f4c865/attachment.html>

From willysr at slackbuilds.org  Sat Jun  3 01:37:52 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 3 Jun 2017 08:37:52 +0700
Subject: [Slackbuilds-users] Updates - 20170603.1
Message-ID: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>

Hi Folks

welcome to first update in June.

Last week, one of the admin (David aka idlemoor) has done a full build
on all the script in the repo for both architectures and found some
build failures. Some of these failures are architecture spesific and the
rest are due to changes in their dependencies, missing sources, or
incorrect checksums. We relay the report to some maintainers and some
were fixed directly into git. You will find most of the fixes in this
batch are due to his reports. Big credits to David!

Many projects are now moving on to https-only domain. Please make sure
to check with your scripts for future updates. As a tip, have a look on
https://repology.org/repository/slackbuilds/problems to see whether your
script is listed there.

We also have some bad news. Some scripts were removed because they are
no longer working and abandoned (python-twisted-web2), upstream close
the project for the community and hide the source only to paying clients
(gradm), duplicate script (pass), and no longer compatible with deps in
our repository (monotone). We also made some changes to some scripts to
be x86_64 only since upstream no longer support x86 (folly, wangle,
proxygen, mongodb)

With all the changes, we still have some unfixed scripts in our list. We
are grateful if anyone came up with a patch or fixes for the following
scripts:

development/eclim (needs retest with new Sphinx)
development/newtonsoft-json
games/roccat-tools (due to updated libgaminggear)
graphics/pngcrush (i586 only, https://sourceforge.net/p/pmt/bugs/75/)
network/pydio-sync (x86_64 only)
office/fop

happy weekend


Sat Jun  3 01:03:32 UTC 2017
academic/GeoGebra: Updated for version 5.0.361.0.
academic/scidavis: Updated for version 1.17.
academic/solfege: Update HOMEPAGE and DOWNLOAD urls.
audio/gogglesmm: Updated for version 1.1.8.
desktop/ctwm: Updated for version 4.0.0.
desktop/hsetroot: Updated for version 1.0.2.
desktop/i3lock: Updated for version 2.9.
desktop/qt5ct: Updated for version 0.33.
desktop/qtpass: Fix desktop icon.
desktop/redshift: Updated for version 1.11 + new maintainer.
desktop/wmdate: Fix dockapp header path.
development/Sphinx: Updated for version 1.6.2.
development/ahven: Updated for version 2.6.
development/dmd: Updated for version 2.074.1.
development/eclim: Update DEP.
development/elixir: Update HOMEPAGE.
development/extra-cmake-modules: Updated for version 5.34.0.
development/fossil: Updated for version 2.2.
development/hopper: Updated for version 4.2.2.
development/kotlin: Added (Kotlin Compiler)
development/mkchroot: Updated for version 1.0.
development/mm-common: Update HOMEPAGE.
development/monotone: Removed (Not compatible with Botan 2).
development/newtonsoft-json: Switch to i586.
development/vscode: Fix build on x86.
games/FlightGear-data: Updated for version 2017.2.1.
games/FlightGear: Updated for version 2017.2.1.
games/fgrun: Updated for version 2016.4.0.
games/glob2: Update HOMEPAGE.
games/opendune: Fix x86 build.
games/scummvm-libretro: Update HOMEPAGE.
games/stone_soup: Updated for version 0.20.0.
games/tome-ah: Update HOMEPAGE.
games/xarchon: Fix build on x86.
gis/SFCGAL: Updated for version 1.3.1.
gis/osm2pgsql: Updated for version git28ce89d.
gis/qgis: Updated for version 2.18.9.
graphics/FreeCAD: Update HOMEPAGE.
graphics/darktable: Updated for version 2.2.5.
graphics/gmic: Updated for version 2.0.0.
graphics/opencollada: Updated for version 1.6.51
graphics/openimageio: Updated for version 1.7.15
graphics/paraview: Update HOMEPAGE and DOWNLOAD urls.
graphics/photivo: Updated for version 20160525.
graphics/qcad: Updated for version 3.17.1.1
graphics/vsxu: Updated for version 0.6.1.0
ham/chirp: Updated for version 20170526.
libraries/SimGear: Updated for version 2017.2.1.
libraries/allegro: Update HOMEPAGE.
libraries/allegro: Updated for version 5.2.2.0.
libraries/dropbox-python: Fixed deps.
libraries/folly: x86 is not supported.
libraries/frei0r: Updated for version 1.6.0.
libraries/gnome-vfsmm: Update HOMEPAGE.
libraries/imlib2_loaders: Added (image loaders for imlib2).
libraries/libc++: Fix build.
libraries/libedit: Updated for version 20170329_3.1.
libraries/libfilezilla: Updated for version 0.9.2.
libraries/libglademm: Update HOMEPAGE.
libraries/libgnomecanvasmm: Update HOMEPAGE.
libraries/libgnomemm: Update HOMEPAGE.
libraries/libgnomeuimm: Update HOMEPAGE.
libraries/libopenshot: Updated for version 0.1.7
libraries/libtomcrypt: Fix build failure on x86.
libraries/libuv: Updated for version 1.12.0.
libraries/libversion: Fix build on x86.
libraries/munkres: Updated for version 1.0.10.
libraries/pjsip: Fix build on x86.
libraries/proxygen: x86 is not supported.
libraries/pyte: Updated for version 0.6.0.
libraries/wangle: x86 is not supported.
libraries/webkit2gtk: Updated for version 2.16.3.
misc/mosquitto: Updated for version 1.4.12
misc/projectM: Patched for gcc 6/7.
multimedia/OpenPHT: Updated for version 1.8.0.148.
multimedia/miro: Fix build against new ffmpeg.
multimedia/mkvtoolnix: Removed wxPython from REQUIRES.
multimedia/openshot: Updated for version 2.3.4
multimedia/opera-developer-ffmpeg-codecs: Updated for version 59.0.
multimedia/opera-ffmpeg-codecs: Updated for version 58.0.3029.110.
multimedia/simpleburn: Updated for version 1.8.3, moved from system.
network/avahi: Updated for version 0.6.32.
network/bitlbee: Fixed md5sum.
network/etherpad-lite: Updated for version 1.6.1.
network/filezilla: Updated for version 3.26.1.
network/icecat: Fix build.
network/ip2location-c: Update MD5SUM.
network/nbd: Updated for version 3.16.1
network/ngrep: Fix build.
network/opera: Updated for version 45.0.2552.881.
network/psad: Do not download signature by default.
network/radicale: Updated for version 1.1.3.
network/sslstrip: Change dependency
network/telegram: Updated for version 1.1.7.
network/wireshark: Updated for version 2.2.7.
office/basket: Added (KDE note-taking application).
office/kmymoney: Fix build failure.
office/tasksh: Fix HOMEPAGE and DOWNLOAD urls.
perl/perl-CPAN-Perl-Releases: Updated for version 3.22.
perl/perl-ExtUtils-Install: Updated for version 2.12.
perl/perl-Inline-C: Updated for version 0.78.
perl/perl-Module-Build: Updated for version 0.4224.
perl/perl-Mojolicious: Updated for version 7.32.
python/APScheduler: Fixed deps.
python/ipython: Upgraded for version 5.4.0.
python/pytest-runner: Fixed deps.
python/pytest: Fixed deps.
python/python-d2to1: Added (distutils2 setup.cfg for setuptools).
python/python-rubymarshal: Added (read/write Ruby-marshalled data).
python/python-stsci.distutils: Added (STScI's packaging utilities).
python/python-twisted-web2: Removed (broken and abandoned upstream).
python/python3-ipython: Added missing dependency.
python/python3-ipython: Updated for version 6.1.0.
python/python3-jupyter-ipykernel: Added missing dependencies.
python/sphinxcontrib-plantuml: Added (Sphinx extension).
system/AnonymousPro: Update HOMEPAGE and DOWNLOAD urls.
system/ack: Updated for version 2.18.
system/agedu: Added (time-sensitive 'du' utility).
system/apcupsd: fixup a restart issue + minor tweaks
system/foomatic-db: Updated for version 20170531.
system/gradm: Removed.
system/guake: Updated for version 0.8.9.
system/hh: Update MD5SUM.
system/krusader: Updated for version 3.0.1.
system/lxterminal: Updated for version 20170514_0f2ca01.
system/mongodb: x86 is no longer supported.
system/newrelic-sysmond: Fix MD5SUM.
system/packagekit: Update README.
system/pass: Removed (duplicate of password-store).
system/password-store: Updated for version 1.7.1, new maintainer.
system/paxctl: Update README.
system/postgresql: Updated for version 9.6.3.
system/setconf: Added (configuration utility)
system/terminix: Update MD5SUM.
system/tinyvm: Fix build.
system/trashy: Updated for version 2.0.
system/veracrypt: Updated for version git_5103f19e.
system/wine-staging: Updated for version 2.9.
system/winetricks: Updated for version 20170517.
system/xen: Updated for version 4.8.1.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- 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/20170603/3e6c1d72/attachment.asc>

From willysr at slackbuilds.org  Sat Jun  3 07:46:16 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 3 Jun 2017 14:46:16 +0700
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
Message-ID: <02a513ea-1a67-489b-f281-454b9d0d8972@slackbuilds.org>

> development/eclim (needs retest with new Sphinx)

The fix is not included in 1.6.2, but it will be part of next 1.6.3
if someone is trying to build eclim, you need to rebuild Sphinx with
this patch first:
https://github.com/sphinx-doc/sphinx/commit/a347b0bb9869326622e8b695fb0f4c7e06e58d82



-- 
Willy Sudiarto Raharjo

-------------- 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/20170603/14d8e204/attachment.asc>

From artourter at gmail.com  Sat Jun  3 11:01:04 2017
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Sat, 3 Jun 2017 12:01:04 +0100
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
Message-ID: <CAK09-vkTMh3EV-1MobpwXk+jOYvOexUuZ3R0=p7k1ww3Oa=3qA@mail.gmail.com>

> system/apcupsd: fixup a restart issue + minor tweaks

The patches are not included in the slackbuild so this fails to build.

we are missing two files:

create_lockdir_in_init_script.diff and nitpicky-fixes-to-init-script.diff

any chances of getting them added to the repo?

Cheers

Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170603/60a89d3b/attachment.html>

From willysr at slackbuilds.org  Sat Jun  3 13:09:11 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 3 Jun 2017 20:09:11 +0700
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <CAK09-vkTMh3EV-1MobpwXk+jOYvOexUuZ3R0=p7k1ww3Oa=3qA@mail.gmail.com>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
 <CAK09-vkTMh3EV-1MobpwXk+jOYvOexUuZ3R0=p7k1ww3Oa=3qA@mail.gmail.com>
Message-ID: <b368f62b-5682-2110-7283-6afcf3376bd3@slackbuilds.org>

>> system/apcupsd: fixup a restart issue + minor tweaks
> 
> The patches are not included in the slackbuild so this fails to build.
> 
> we are missing two files:
> 
> create_lockdir_in_init_script.diff and nitpicky-fixes-to-init-script.diff
> 
> any chances of getting them added to the repo?

Thanks Greg
i have pushed a fix on my branch


-- 
Willy Sudiarto Raharjo

-------------- 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/20170603/d794efc4/attachment-0001.asc>

From 414N at slacky.it  Sat Jun  3 14:16:34 2017
From: 414N at slacky.it (414N)
Date: Sat, 3 Jun 2017 16:16:34 +0200
Subject: [Slackbuilds-users] Building glabels on 14.1
In-Reply-To: <alpine.LNX.2.11.1706020902220.15709@localhost>
References: <alpine.LNX.2.11.1706020836180.15709@localhost>
 <a3d2f1a8-262c-302d-0dbf-a0bad5324fb6@slackbuilds.org>
 <alpine.LNX.2.11.1706020849050.15709@localhost>
 <alpine.LNX.2.11.1706020902220.15709@localhost>
Message-ID: <835110a8-6238-6041-c5bb-3a2083b8da96@slacky.it>

Yep, 3.2.1 is indeed the last version that can work on Slackware 14.1.

I tested it last year when I first submitted the SlackBuild on SBo.

Cheers

Alan Alberghini

SBo clone: GitHub <https://github.com/414n/slackbuilds.org>

On 02/06/2017 18:03, Rich Shepard wrote:
> On Fri, 2 Jun 2017, Rich Shepard wrote:
>
>> There is no SBo glabel package displayed for 14.1. I'll download the
>> source for glabel-3.2.1 and try that with the SBo build script.
>
>   The earlier version builds with a change in version number to the build
> script. It will be interesting to see how well glabels works at creating
> business cards.
>
> Carpe weekend all,
>
> Rich
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170603/96d2a448/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170603/96d2a448/attachment.asc>

From rworkman at slackbuilds.org  Sat Jun  3 16:51:31 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 3 Jun 2017 11:51:31 -0500
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <CAK09-vkTMh3EV-1MobpwXk+jOYvOexUuZ3R0=p7k1ww3Oa=3qA@mail.gmail.com>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
 <CAK09-vkTMh3EV-1MobpwXk+jOYvOexUuZ3R0=p7k1ww3Oa=3qA@mail.gmail.com>
Message-ID: <20170603115131.78ca877b@home.rlworkman.net>

On Sat, 3 Jun 2017 12:01:04 +0100
"Greg' Ar Tourter" <artourter at gmail.com> wrote:

> > system/apcupsd: fixup a restart issue + minor tweaks  
> 
> The patches are not included in the slackbuild so this fails to build.
> 
> we are missing two files:
> 
> create_lockdir_in_init_script.diff and
> nitpicky-fixes-to-init-script.diff
> 
> any chances of getting them added to the repo?


Well, crap. I actually merged those two patches into the 
new patch that is present, so the real solution is to
fix the build script itself, which willysr did in his
branch.

Sorry for the oversight. I have no idea how that slipped
past me, especially given that I built and installed a
package produced from the "new" script. :-)

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

From atelszewski at gmail.com  Sat Jun  3 17:56:45 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 3 Jun 2017 19:56:45 +0200
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
Message-ID: <f4afc4c2-4f46-5461-b037-17f140a0930b@gmail.com>

On 03/06/17 03:37, Willy Sudiarto Raharjo wrote:
> system/krusader: Updated for version 3.0.1.

Some error must have occurred ;-)
There's no krusader 3.0.1 yet ;-)

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Sat Jun  3 17:58:49 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 4 Jun 2017 00:58:49 +0700
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <f4afc4c2-4f46-5461-b037-17f140a0930b@gmail.com>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
 <f4afc4c2-4f46-5461-b037-17f140a0930b@gmail.com>
Message-ID: <5e14f17b-55d2-d450-ee57-07a82cd454a7@slackbuilds.org>

>> system/krusader: Updated for version 3.0.1.
> 
> Some error must have occurred ;-)
> There's no krusader 3.0.1 yet ;-)

Yep, my bad
it was supposed to be system/image-analyzer


-- 
Willy Sudiarto Raharjo

-------------- 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/20170604/55619499/attachment.asc>

From ozan.turkyilmaz at gmail.com  Sat Jun  3 18:28:10 2017
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Sat, 3 Jun 2017 23:28:10 +0500
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
Message-ID: <CA+da1or6xZLXBWrM=YQT4Q5Y9H_7cQEtodXEmniuTfOBjJZv8w@mail.gmail.com>

Hello Willy,


> Many projects are now moving on to https-only domain. Please make sure
> to check with your scripts for future updates. As a tip, have a look on
> https://repology.org/repository/slackbuilds/problems to see whether your
> script is listed there.
>
>
I looked at my scripts:
chm2pdf: That program didn't change for a long time. I didn't find any new
homepage for it.
So I say let's leave it as it is for now.
ibus-anthy: I found the new homepage at github for it. I also tasted the
newest release.
Only a version change works. However ibus package needs some tinkering and
I'll update it after
ibus gets an update. Also ibus needs two packages: unicode emoji and cldr.
I got a submission for cldr.



-- 
Ozan, BSc, BEng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170603/9adef63a/attachment.html>

From gerardo.zamudio at linux.com  Sat Jun  3 20:54:17 2017
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Sat, 3 Jun 2017 15:54:17 -0500
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
Message-ID: <6fce33dc-5076-fde3-b99b-3c19c0501865@linux.com>



On 06/02/2017 08:37 PM, Willy Sudiarto Raharjo wrote:
> 
> With all the changes, we still have some unfixed scripts in our list. We
> are grateful if anyone came up with a patch or fixes for the following
> scripts:
> 
> games/roccat-tools (due to updated libgaminggear)

I will fix this. New version of roccat-tools requires some changes to
build properly.

-- 
Gerardo Zamudio



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

From willysr at slackbuilds.org  Sat Jun  3 23:57:11 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 4 Jun 2017 06:57:11 +0700
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <6fce33dc-5076-fde3-b99b-3c19c0501865@linux.com>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
 <6fce33dc-5076-fde3-b99b-3c19c0501865@linux.com>
Message-ID: <9d21cdcd-b201-146a-1538-719945c0e581@slackbuilds.org>

>> games/roccat-tools (due to updated libgaminggear)
> 
> I will fix this. New version of roccat-tools requires some changes to
> build properly.

Hi Gerardo

B. Watson has send me a patch for this and it's now already on my
branch. Can you verify whether this new version works with roccat
hardware (we both don't have one)
https://git.slackbuilds.org/slackbuilds/commit/?id=13445c133

Thanks


-- 
Willy Sudiarto Raharjo

-------------- 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/20170604/2db16760/attachment-0001.asc>

From yalhcru at gmail.com  Sun Jun  4 02:25:11 2017
From: yalhcru at gmail.com (B Watson)
Date: Sat, 3 Jun 2017 22:25:11 -0400
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <6fce33dc-5076-fde3-b99b-3c19c0501865@linux.com>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
 <6fce33dc-5076-fde3-b99b-3c19c0501865@linux.com>
Message-ID: <CAN1hMuBrZXgKqRcqU0LqsuB-bfZB6UvSLRTxWQhQz2Gtj3i0Kg@mail.gmail.com>

On 6/3/17, Gerardo Zamudio <gerardo.zamudio at linux.com> wrote:

> I will fix this. New version of roccat-tools requires some changes to
> build properly.

Have a look here:

https://git.slackbuilds.org/slackbuilds/commit/?h=willysr&id=13445c1334257499a7ef453b10060ad4ee9ccfe6

I updated the script, but I don't want to take it. Have a look & see
if it works the way it's supposed to (particularly, I had to make lua
a hard dep).

From larryhaja at gmail.com  Sun Jun  4 03:24:54 2017
From: larryhaja at gmail.com (Larry Hajali)
Date: Sat, 3 Jun 2017 20:24:54 -0700
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <f85503aa-6e63-a64e-7477-320df524dc64@gmail.com>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
 <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
 <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>
 <f85503aa-6e63-a64e-7477-320df524dc64@gmail.com>
Message-ID: <CAAZPBMhEySdJE7bx1Z1Tg7dK05Rgk6_dQ+4vgq6KG=Fi8A1r6A@mail.gmail.com>

> unfortunately I am not optimistic that soon for Qt, sbo will run a sane
>>> version politic,
>>> The current maintainer showed more or less that he/she does not care to
>>> much and/or does not understand why a LTS version strategy is the right
>>> thing for a distribution like Slackware.
>>>
>> All I'll say about this is that the above is a bogus statement!


> That will have to be decided by qt5 maintainer (Larry)
>> My suggestion (suppose we bump to 5.9) is to place them on -review
>> branch first and see if other scripts are working fine with it. If it
>> turns out to be OK, we can then merge it into master and 14.2.
>>
> I don't plan on upgrading Qt5 past the 5.7.X branch for Slackware 14.2.  I
like to keep PyQt5 around the same version as Qt5.  Unfortunately, PyQt5
5.7.1 requires sip 4.19 or above.  I can look at upgrading for -current but
I don't see it happening for 14.2.


> based on rough count, we have more than 60 other scripts depending on
>> qt5 for hard dep and probably more with optional dep. That will take
>> some time to test.
>>
> This is true.  It takes a while to go through all the builds that depend
on Qt5.

--Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170603/4de9156e/attachment.html>

From harald.achitz at gmail.com  Sun Jun  4 06:13:15 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sun, 4 Jun 2017 08:13:15 +0200
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <CAAZPBMhEySdJE7bx1Z1Tg7dK05Rgk6_dQ+4vgq6KG=Fi8A1r6A@mail.gmail.com>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
 <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
 <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>
 <f85503aa-6e63-a64e-7477-320df524dc64@gmail.com>
 <CAAZPBMhEySdJE7bx1Z1Tg7dK05Rgk6_dQ+4vgq6KG=Fi8A1r6A@mail.gmail.com>
Message-ID: <CAPh+tzPLJL4EgYNguNkAZzN9aRq=x_saxE4nWwN4a+8KBANYzw@mail.gmail.com>

thanks Larry that you self delivered the reason why the SBo version should
have been, and should be, on the LTS Version 5.6x and not on some
intermediate development release. The 5.6 never mad it into SBo, right? you
missed it,  too long on the outdated 5.5 than jump to 5.7 .  Excellent
expert version strategy!
Of course, not understanding such small, but important features, like LTS
support and the difference between LTS and the intermediate versions makes
it easy to call information people provide to you bogus, but I understand
that it helps to be ignorant when a certain knowledge is missing.
Have a nice weekend!



2017-06-04 5:24 GMT+02:00 Larry Hajali <larryhaja at gmail.com>:

>
> unfortunately I am not optimistic that soon for Qt, sbo will run a sane
>>>> version politic,
>>>> The current maintainer showed more or less that he/she does not care to
>>>> much and/or does not understand why a LTS version strategy is the right
>>>> thing for a distribution like Slackware.
>>>>
>>> All I'll say about this is that the above is a bogus statement!
>
>
>> That will have to be decided by qt5 maintainer (Larry)
>>> My suggestion (suppose we bump to 5.9) is to place them on -review
>>> branch first and see if other scripts are working fine with it. If it
>>> turns out to be OK, we can then merge it into master and 14.2.
>>>
>> I don't plan on upgrading Qt5 past the 5.7.X branch for Slackware 14.2.
> I like to keep PyQt5 around the same version as Qt5.  Unfortunately, PyQt5
> 5.7.1 requires sip 4.19 or above.  I can look at upgrading for -current but
> I don't see it happening for 14.2.
>
>
>> based on rough count, we have more than 60 other scripts depending on
>>> qt5 for hard dep and probably more with optional dep. That will take
>>> some time to test.
>>>
>> This is true.  It takes a while to go through all the builds that depend
> on Qt5.
>
> --Larry
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170604/7cedb37d/attachment.html>

From harald.achitz at gmail.com  Sun Jun  4 06:16:09 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sun, 4 Jun 2017 08:16:09 +0200
Subject: [Slackbuilds-users] question about libjvm.so symlinks
In-Reply-To: <CAA2+phGREWw9SEMDrM=to1LsSqJiGXACU7QDFMoub5cjTkDApQ@mail.gmail.com>
References: <CAA2+phGREWw9SEMDrM=to1LsSqJiGXACU7QDFMoub5cjTkDApQ@mail.gmail.com>
Message-ID: <CAPh+tzNEpOuhZjD-C_EyYtSHZPWF_f-uqTT8Ugs2rZck=h=xqA@mail.gmail.com>

for that other programs can find libjvm.so in the library search path
./$PRGNAM/jre/lib/${LIB_ARCH}/server/
is just some path only the program self knows

$PKG/usr/lib${LIBDIRSUFFIX}
is a path all other programs also know

/Harald




2017-06-02 18:41 GMT+02:00 Sebastien BALLET <slacker6896 at gmail.com>:

> Hello,
>
> I would like to know if there is any (documented) reasons why the
> slackbuilds for (open)jdk create the symlinks below.
>
> jdk.SlackBuild:
> cd $PKG/usr/lib${LIBDIRSUFFIX}
>     ln -sf ./java/jre/lib/${LIB_ARCH}/server/libjvm.so .
>
> openjdk.SlackBuild:
> cd $PKG/usr/lib${LIBDIRSUFFIX}
>  ln -sf ./$PRGNAM/jre/lib/${LIB_ARCH}/server/libjvm.so .
>
> I've search the web and didn't find anything conclusive about that. In
> fact, it seems that symlink is not needed and is more a hack used to fix
> some specific issues.
>
>
> Thanks.
>
> --
> SeB
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170604/81cd5f19/attachment-0001.html>

From matteo.bernardini at gmail.com  Sun Jun  4 06:26:00 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 4 Jun 2017 08:26:00 +0200
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <CAPh+tzPLJL4EgYNguNkAZzN9aRq=x_saxE4nWwN4a+8KBANYzw@mail.gmail.com>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
 <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
 <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>
 <f85503aa-6e63-a64e-7477-320df524dc64@gmail.com>
 <CAAZPBMhEySdJE7bx1Z1Tg7dK05Rgk6_dQ+4vgq6KG=Fi8A1r6A@mail.gmail.com>
 <CAPh+tzPLJL4EgYNguNkAZzN9aRq=x_saxE4nWwN4a+8KBANYzw@mail.gmail.com>
Message-ID: <CAPsDuS6qnuWJUT+sFj9GBNn0LAEF_RANjruz-Kws5qJgZemA+A@mail.gmail.com>

2017-06-04 8:13 GMT+02:00 Harald Achitz <harald.achitz at gmail.com>:
> thanks Larry that you self delivered the reason why the SBo version should
> have been, and should be, on the LTS Version 5.6x and not on some
> intermediate development release. The 5.6 never mad it into SBo, right? you
> missed it,  too long on the outdated 5.5 than jump to 5.7 .  Excellent
> expert version strategy!
> Of course, not understanding such small, but important features, like LTS
> support and the difference between LTS and the intermediate versions makes
> it easy to call information people provide to you bogus, but I understand
> that it helps to be ignorant when a certain knowledge is missing.
> Have a nice weekend!

https://git.slackbuilds.org/slackbuilds/log/?qt=grep&q=libraries%2Fqt5

From didier at slint.fr  Sun Jun  4 06:40:07 2017
From: didier at slint.fr (Didier Spaier)
Date: Sun, 4 Jun 2017 08:40:07 +0200
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <CAPsDuS6qnuWJUT+sFj9GBNn0LAEF_RANjruz-Kws5qJgZemA+A@mail.gmail.com>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
 <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
 <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>
 <f85503aa-6e63-a64e-7477-320df524dc64@gmail.com>
 <CAAZPBMhEySdJE7bx1Z1Tg7dK05Rgk6_dQ+4vgq6KG=Fi8A1r6A@mail.gmail.com>
 <CAPh+tzPLJL4EgYNguNkAZzN9aRq=x_saxE4nWwN4a+8KBANYzw@mail.gmail.com>
 <CAPsDuS6qnuWJUT+sFj9GBNn0LAEF_RANjruz-Kws5qJgZemA+A@mail.gmail.com>
Message-ID: <d31cff90-1dbc-b3dd-04f1-15a81add8b58@slint.fr>

Le 04/06/2017 ? 08:26, Matteo Bernardini a ?crit :
> 2017-06-04 8:13 GMT+02:00 Harald Achitz <harald.achitz at gmail.com>:
>> thanks Larry that you self delivered the reason why the SBo version should
>> have been, and should be, on the LTS Version 5.6x and not on some
>> intermediate development release. The 5.6 never mad it into SBo, right? you
>> missed it,  too long on the outdated 5.5 than jump to 5.7 .  Excellent
>> expert version strategy!
>> Of course, not understanding such small, but important features, like LTS
>> support and the difference between LTS and the intermediate versions makes
>> it easy to call information people provide to you bogus, but I understand
>> that it helps to be ignorant when a certain knowledge is missing.
>> Have a nice weekend!
> 
> https://git.slackbuilds.org/slackbuilds/log/?qt=grep&q=libraries%2Fqt5

See also:
http://slackware.uk/salix/x86_64/14.2/source/l/qt5/

Didier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x60C03EEA.asc
Type: application/pgp-keys
Size: 1718 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170604/bf16f658/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170604/bf16f658/attachment.asc>

From harald.achitz at gmail.com  Sun Jun  4 06:41:09 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sun, 4 Jun 2017 08:41:09 +0200
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <CAPsDuS6qnuWJUT+sFj9GBNn0LAEF_RANjruz-Kws5qJgZemA+A@mail.gmail.com>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
 <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
 <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>
 <f85503aa-6e63-a64e-7477-320df524dc64@gmail.com>
 <CAAZPBMhEySdJE7bx1Z1Tg7dK05Rgk6_dQ+4vgq6KG=Fi8A1r6A@mail.gmail.com>
 <CAPh+tzPLJL4EgYNguNkAZzN9aRq=x_saxE4nWwN4a+8KBANYzw@mail.gmail.com>
 <CAPsDuS6qnuWJUT+sFj9GBNn0LAEF_RANjruz-Kws5qJgZemA+A@mail.gmail.com>
Message-ID: <CAPh+tzNM_COczbeDg3vNB13iY7TGpW4n5ESG+o-ZWHMVnumzBQ@mail.gmail.com>

thanks, so there was for 3 month, until the ignored update to 5.6.2,  a not
outdated stable version available.
If you think that does make Qt from SBo more usable, I have to disagree.

2017-06-04 8:26 GMT+02:00 Matteo Bernardini <matteo.bernardini at gmail.com>:

> 2017-06-04 8:13 GMT+02:00 Harald Achitz <harald.achitz at gmail.com>:
> > thanks Larry that you self delivered the reason why the SBo version
> should
> > have been, and should be, on the LTS Version 5.6x and not on some
> > intermediate development release. The 5.6 never mad it into SBo, right?
> you
> > missed it,  too long on the outdated 5.5 than jump to 5.7 .  Excellent
> > expert version strategy!
> > Of course, not understanding such small, but important features, like LTS
> > support and the difference between LTS and the intermediate versions
> makes
> > it easy to call information people provide to you bogus, but I understand
> > that it helps to be ignorant when a certain knowledge is missing.
> > Have a nice weekend!
>
> https://git.slackbuilds.org/slackbuilds/log/?qt=grep&q=libraries%2Fqt5
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170604/c9b174d0/attachment.html>

From harald.achitz at gmail.com  Sun Jun  4 06:51:07 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sun, 4 Jun 2017 08:51:07 +0200
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <d31cff90-1dbc-b3dd-04f1-15a81add8b58@slint.fr>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
 <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
 <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>
 <f85503aa-6e63-a64e-7477-320df524dc64@gmail.com>
 <CAAZPBMhEySdJE7bx1Z1Tg7dK05Rgk6_dQ+4vgq6KG=Fi8A1r6A@mail.gmail.com>
 <CAPh+tzPLJL4EgYNguNkAZzN9aRq=x_saxE4nWwN4a+8KBANYzw@mail.gmail.com>
 <CAPsDuS6qnuWJUT+sFj9GBNn0LAEF_RANjruz-Kws5qJgZemA+A@mail.gmail.com>
 <d31cff90-1dbc-b3dd-04f1-15a81add8b58@slint.fr>
Message-ID: <CAPh+tzP92qM-O1R0u2q4Vfv2P7aO2b2sE53AkeACSf85nJP2OA@mail.gmail.com>

what do you want to tell me?
Ok, I was wrong, there was for some weeks a stable version of Qt on SBo,
did not notice it because at this time I had already to use my own builds,
why?
the update to 5.6 was a half year late, and than instead of staying on the
stable LTS version the jump to the next developer version was done.
And instead of having a 3 years supporter Qt version in SBo, what would
reduce the amount of work, now there is a version that is basically already
eof .
Calling this info bogus is as ignorant as putting some URLs up and ignore
the info I provide and do so as everything is wonderful
So what's the point in showing me the URLs and the version history of Qt in
SBo, it just shows that it is totally wrong. Have self a look at it and
understand why


2017-06-04 8:40 GMT+02:00 Didier Spaier <didier at slint.fr>:

> Le 04/06/2017 ? 08:26, Matteo Bernardini a ?crit :
> > 2017-06-04 8:13 GMT+02:00 Harald Achitz <harald.achitz at gmail.com>:
> >> thanks Larry that you self delivered the reason why the SBo version
> should
> >> have been, and should be, on the LTS Version 5.6x and not on some
> >> intermediate development release. The 5.6 never mad it into SBo, right?
> you
> >> missed it,  too long on the outdated 5.5 than jump to 5.7 .  Excellent
> >> expert version strategy!
> >> Of course, not understanding such small, but important features, like
> LTS
> >> support and the difference between LTS and the intermediate versions
> makes
> >> it easy to call information people provide to you bogus, but I
> understand
> >> that it helps to be ignorant when a certain knowledge is missing.
> >> Have a nice weekend!
> >
> > https://git.slackbuilds.org/slackbuilds/log/?qt=grep&q=libraries%2Fqt5
>
> See also:
> http://slackware.uk/salix/x86_64/14.2/source/l/qt5/
>
> Didier
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170604/74ca3235/attachment.html>

From willysr at slackbuilds.org  Sun Jun  4 07:44:17 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 4 Jun 2017 14:44:17 +0700
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <CAPh+tzP92qM-O1R0u2q4Vfv2P7aO2b2sE53AkeACSf85nJP2OA@mail.gmail.com>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
 <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
 <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>
 <f85503aa-6e63-a64e-7477-320df524dc64@gmail.com>
 <CAAZPBMhEySdJE7bx1Z1Tg7dK05Rgk6_dQ+4vgq6KG=Fi8A1r6A@mail.gmail.com>
 <CAPh+tzPLJL4EgYNguNkAZzN9aRq=x_saxE4nWwN4a+8KBANYzw@mail.gmail.com>
 <CAPsDuS6qnuWJUT+sFj9GBNn0LAEF_RANjruz-Kws5qJgZemA+A@mail.gmail.com>
 <d31cff90-1dbc-b3dd-04f1-15a81add8b58@slint.fr>
 <CAPh+tzP92qM-O1R0u2q4Vfv2P7aO2b2sE53AkeACSf85nJP2OA@mail.gmail.com>
Message-ID: <025175ce-3f6b-97a3-17c6-cecfc48b28a1@slackbuilds.org>

> what do you want to tell me?
> Ok, I was wrong, there was for some weeks a stable version of Qt on SBo,
> did not notice it because at this time I had already to use my own builds,
> why?
> the update to 5.6 was a half year late, and than instead of staying on the
> stable LTS version the jump to the next developer version was done.
> And instead of having a 3 years supporter Qt version in SBo, what would
> reduce the amount of work, now there is a version that is basically already
> eof .
> Calling this info bogus is as ignorant as putting some URLs up and ignore
> the info I provide and do so as everything is wonderful
> So what's the point in showing me the URLs and the version history of Qt in
> SBo, it just shows that it is totally wrong. Have self a look at it and
> understand why

Hi Harald,

Let me clarify a bit about the version history from GIT:

Qt 5.6 got released on March 2016 and 5.6.1 got released on June 2016.
During this period we had a submission freeze for SBo and we were
focused on testing all scripts in the repository. For a library such as
Qt which is used by many other projects, we prefer to wait until it
reached it's first point release (.1) because major release normally
breaks many things (removal of QWebKit in 5.6). That's why you see i
bumped Qt to 5.6.1 in June, 19 2016, 2 weeks after first point release.

Qt 5.7 was released in June, 16 2016, but as usual, we prefer to wait
for first point release, which was released in December 2016, so Larry
bumped to 5.7.1 in January (roughly 3 weeks from it's release date,
because we had to test other scripts first for about 1 week)

Now, the reason why Larry insist on staying at 5.7.x is because another
script (PyQt5) can't be bumped to higher version unless sip package in
Slackware got updated (which is not at this moment and it won't happen
in -stable since it will affect many other packages as well). I believe
it's reasonable and i can understand his opinion on this one. He is
willing to support newer Qt, but that is for next development cycle.

Bumping to 5.9 will surely break some scripts and some others may have
to be removed due to incompatibility with Qt 5.9. Not to mention the
efforts to make sure all scripts are compatible with the just-released
Qt 5.9. I would consider that (or Qt 5.10) for next development cycle :)

As for LTS, i can understand the benefit of a long term support, but
other than that, it's basically just a regular release. This is my
personal opinion, it doesn't reflect other admins opinions.

AlienBOB is *probably* looking at Qt 5.9 for his future KDE 5 / Plasma
releases.


-- 
Willy Sudiarto Raharjo

-------------- 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/20170604/55952f32/attachment-0001.asc>

From harald.achitz at gmail.com  Sun Jun  4 08:06:27 2017
From: harald.achitz at gmail.com (Harald Achitz)
Date: Sun, 4 Jun 2017 10:06:27 +0200
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <025175ce-3f6b-97a3-17c6-cecfc48b28a1@slackbuilds.org>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
 <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
 <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>
 <f85503aa-6e63-a64e-7477-320df524dc64@gmail.com>
 <CAAZPBMhEySdJE7bx1Z1Tg7dK05Rgk6_dQ+4vgq6KG=Fi8A1r6A@mail.gmail.com>
 <CAPh+tzPLJL4EgYNguNkAZzN9aRq=x_saxE4nWwN4a+8KBANYzw@mail.gmail.com>
 <CAPsDuS6qnuWJUT+sFj9GBNn0LAEF_RANjruz-Kws5qJgZemA+A@mail.gmail.com>
 <d31cff90-1dbc-b3dd-04f1-15a81add8b58@slint.fr>
 <CAPh+tzP92qM-O1R0u2q4Vfv2P7aO2b2sE53AkeACSf85nJP2OA@mail.gmail.com>
 <025175ce-3f6b-97a3-17c6-cecfc48b28a1@slackbuilds.org>
Message-ID: <CAPh+tzPg3D=n6bPSHCnMv+iTS_Q4SeFkBZfvO+-dWv7w3e1i9g@mail.gmail.com>

Hi Willy
Thanks for the explanation, even if it makes me sad to hear that, in case
of Qt, stability and predictability is not the primary concern of SBo. What
just confirms what I said, that it is better to use own Qt builds, LTS for
apps that make use of QT, own latest dev builds for future development of
application. What SBo provides is not a compromise, it is just something
random in between.
This is of course just IMHO, everyone is of course free to use what ever
unstable and not longer supported Qt version he or she wants to use, as it
is oK for SBo and some maintainer that calls technical facts bogus to
decide what to provide and what not.

/Harald

2017-06-04 9:44 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:

> > what do you want to tell me?
> > Ok, I was wrong, there was for some weeks a stable version of Qt on SBo,
> > did not notice it because at this time I had already to use my own
> builds,
> > why?
> > the update to 5.6 was a half year late, and than instead of staying on
> the
> > stable LTS version the jump to the next developer version was done.
> > And instead of having a 3 years supporter Qt version in SBo, what would
> > reduce the amount of work, now there is a version that is basically
> already
> > eof .
> > Calling this info bogus is as ignorant as putting some URLs up and ignore
> > the info I provide and do so as everything is wonderful
> > So what's the point in showing me the URLs and the version history of Qt
> in
> > SBo, it just shows that it is totally wrong. Have self a look at it and
> > understand why
>
> Hi Harald,
>
> Let me clarify a bit about the version history from GIT:
>
> Qt 5.6 got released on March 2016 and 5.6.1 got released on June 2016.
> During this period we had a submission freeze for SBo and we were
> focused on testing all scripts in the repository. For a library such as
> Qt which is used by many other projects, we prefer to wait until it
> reached it's first point release (.1) because major release normally
> breaks many things (removal of QWebKit in 5.6). That's why you see i
> bumped Qt to 5.6.1 in June, 19 2016, 2 weeks after first point release.
>
> Qt 5.7 was released in June, 16 2016, but as usual, we prefer to wait
> for first point release, which was released in December 2016, so Larry
> bumped to 5.7.1 in January (roughly 3 weeks from it's release date,
> because we had to test other scripts first for about 1 week)
>
> Now, the reason why Larry insist on staying at 5.7.x is because another
> script (PyQt5) can't be bumped to higher version unless sip package in
> Slackware got updated (which is not at this moment and it won't happen
> in -stable since it will affect many other packages as well). I believe
> it's reasonable and i can understand his opinion on this one. He is
> willing to support newer Qt, but that is for next development cycle.
>
> Bumping to 5.9 will surely break some scripts and some others may have
> to be removed due to incompatibility with Qt 5.9. Not to mention the
> efforts to make sure all scripts are compatible with the just-released
> Qt 5.9. I would consider that (or Qt 5.10) for next development cycle :)
>
> As for LTS, i can understand the benefit of a long term support, but
> other than that, it's basically just a regular release. This is my
> personal opinion, it doesn't reflect other admins opinions.
>
> AlienBOB is *probably* looking at Qt 5.9 for his future KDE 5 / Plasma
> releases.
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170604/b3021fb8/attachment.html>

From lists at osh.id.au  Sun Jun  4 08:17:46 2017
From: lists at osh.id.au (David O'Shaughnessy)
Date: Sun, 4 Jun 2017 18:17:46 +1000
Subject: [Slackbuilds-users] Qt 5.9 LTS released
In-Reply-To: <CAPh+tzPg3D=n6bPSHCnMv+iTS_Q4SeFkBZfvO+-dWv7w3e1i9g@mail.gmail.com>
References: <f5f1faa0-1bdf-f898-98ca-e2a83cc8731a@gmail.com>
 <CAPh+tzO+EHf-xnOFLznbug0hkaWezorzZpf2V58-a=ykq3KUcg@mail.gmail.com>
 <f7bb2753-0a4b-eafc-3ce0-05f237bfb8a1@slackbuilds.org>
 <f85503aa-6e63-a64e-7477-320df524dc64@gmail.com>
 <CAAZPBMhEySdJE7bx1Z1Tg7dK05Rgk6_dQ+4vgq6KG=Fi8A1r6A@mail.gmail.com>
 <CAPh+tzPLJL4EgYNguNkAZzN9aRq=x_saxE4nWwN4a+8KBANYzw@mail.gmail.com>
 <CAPsDuS6qnuWJUT+sFj9GBNn0LAEF_RANjruz-Kws5qJgZemA+A@mail.gmail.com>
 <d31cff90-1dbc-b3dd-04f1-15a81add8b58@slint.fr>
 <CAPh+tzP92qM-O1R0u2q4Vfv2P7aO2b2sE53AkeACSf85nJP2OA@mail.gmail.com>
 <025175ce-3f6b-97a3-17c6-cecfc48b28a1@slackbuilds.org>
 <CAPh+tzPg3D=n6bPSHCnMv+iTS_Q4SeFkBZfvO+-dWv7w3e1i9g@mail.gmail.com>
Message-ID: <befb528b-a938-6cb6-3293-4ed51583e9ef@osh.id.au>

On 06/04/2017 06:06 PM, Harald Achitz wrote:
> Thanks for the explanation, even if it makes me sad to hear that, in
> case of Qt, stability and predictability is not the primary concern of
> SBo.

I actually drew the opposite conclusion from Willy's post. For what it's
worth, I have not noticed any stability problems with the Qt 5 apps that
I run on Slack 14.2 (with Qt from SBo).

--
Dave

From slacker6896 at gmail.com  Sun Jun  4 16:03:46 2017
From: slacker6896 at gmail.com (Sebastien BALLET)
Date: Sun, 4 Jun 2017 18:03:46 +0200
Subject: [Slackbuilds-users] question about libjvm.so symlinks
In-Reply-To: <CAPh+tzNEpOuhZjD-C_EyYtSHZPWF_f-uqTT8Ugs2rZck=h=xqA@mail.gmail.com>
References: <CAA2+phGREWw9SEMDrM=to1LsSqJiGXACU7QDFMoub5cjTkDApQ@mail.gmail.com>
 <CAPh+tzNEpOuhZjD-C_EyYtSHZPWF_f-uqTT8Ugs2rZck=h=xqA@mail.gmail.com>
Message-ID: <CAA2+phHmGQsD85pt6Ji=CHxdyOpEE0QYki5a=2Y5bz6AY6YAeg@mail.gmail.com>

Hello,

I know why this symlink is in place. However, there's no documentation
which
specifies this symlink is a *requirement*. There's no serious softwares
which requires
it, and there's no other linux distribution which has a jdk with that
symlink.

Therefore, there's no reason to have this symlink installed by default. It
would be better
and cleaner to add a note about the possible need for this link, or, to add
the line below
in openjdk.sh / jdk.sh (and to update openjdk.csh / jdk.csh the same way) :

  export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$JAVA_HOME/jre/lib/$LIB_
ARCH/server/libjvm.so"

-- 
SeB

2017-06-04 8:16 GMT+02:00 Harald Achitz <harald.achitz at gmail.com>:

> for that other programs can find libjvm.so in the library search path
> ./$PRGNAM/jre/lib/${LIB_ARCH}/server/
> is just some path only the program self knows
>
> $PKG/usr/lib${LIBDIRSUFFIX}
> is a path all other programs also know
>
> /Harald
>
>
>
>
> 2017-06-02 18:41 GMT+02:00 Sebastien BALLET <slacker6896 at gmail.com>:
>
>> Hello,
>>
>> I would like to know if there is any (documented) reasons why the
>> slackbuilds for (open)jdk create the symlinks below.
>>
>> jdk.SlackBuild:
>> cd $PKG/usr/lib${LIBDIRSUFFIX}
>>     ln -sf ./java/jre/lib/${LIB_ARCH}/server/libjvm.so .
>>
>> openjdk.SlackBuild:
>> cd $PKG/usr/lib${LIBDIRSUFFIX}
>>  ln -sf ./$PRGNAM/jre/lib/${LIB_ARCH}/server/libjvm.so .
>>
>> I've search the web and didn't find anything conclusive about that. In
>> fact, it seems that symlink is not needed and is more a hack used to fix
>> some specific issues.
>>
>>
>> Thanks.
>>
>> --
>> SeB
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170604/71f3490d/attachment.html>

From atelszewski at gmail.com  Sun Jun  4 22:55:21 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 5 Jun 2017 00:55:21 +0200
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <5e14f17b-55d2-d450-ee57-07a82cd454a7@slackbuilds.org>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
 <f4afc4c2-4f46-5461-b037-17f140a0930b@gmail.com>
 <5e14f17b-55d2-d450-ee57-07a82cd454a7@slackbuilds.org>
Message-ID: <0bc7e665-072f-1850-368d-492f09723b69@gmail.com>

On 03/06/17 19:58, Willy Sudiarto Raharjo wrote:
>>> system/krusader: Updated for version 3.0.1.
>> Some error must have occurred ;-)
>> There's no krusader 3.0.1 yet ;-)
> Yep, my bad
> it was supposed to be system/image-analyzer

Maybe it would make sense to have the git hook to extract the version 
from *.info?

Then the whole "Updated for version X.X.X." message could be determined 
and generated automatically?

-- 
Best regards,
Andrzej Telszewski

From baildon.research at googlemail.com  Sun Jun  4 23:56:27 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Mon, 5 Jun 2017 00:56:27 +0100
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <0bc7e665-072f-1850-368d-492f09723b69@gmail.com>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
 <f4afc4c2-4f46-5461-b037-17f140a0930b@gmail.com>
 <5e14f17b-55d2-d450-ee57-07a82cd454a7@slackbuilds.org>
 <0bc7e665-072f-1850-368d-492f09723b69@gmail.com>
Message-ID: <CAMt7G9Qz7e+jBTS7pkz9Yje0UoQTAB5Rui3fbSm7Q+LH55QgCg@mail.gmail.com>

> Maybe it would make sense to have the git hook to extract the version from
> *.info?
>
> Then the whole "Updated for version X.X.X." message could be determined and
> generated automatically?

my own review script already generates the message and author this
way. But it generates the same message for build bumps where the
version hasn't changed, and unfortunately I don't always remember to
amend the message. Willy has saved me from this error multiple times
:)

The git hook could check the version in the message, also it would be
nice to check the category and prgnam, and check that no files outside
that directory are in the commit. Does anybody want to look at doing
that? pleeeeeeeease :)

Thanks
-D.

From duncan_roe at optusnet.com.au  Mon Jun  5 02:14:03 2017
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Mon, 5 Jun 2017 12:14:03 +1000
Subject: [Slackbuilds-users] What happened to libssh2?
Message-ID: <20170605021403.GA31383@dimstar.local.net>

xen lists libssh2 as an optional dependency, but I can't find it at SBo.

It was there on Nov 10  2016, that's when I last built it.

Did I miss an announcement?

Cheers ... Duncan.

From willysr at slackbuilds.org  Mon Jun  5 02:16:15 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 5 Jun 2017 09:16:15 +0700
Subject: [Slackbuilds-users] What happened to libssh2?
In-Reply-To: <20170605021403.GA31383@dimstar.local.net>
References: <20170605021403.GA31383@dimstar.local.net>
Message-ID: <bc056f9d-dc55-94ba-4e66-d164d35d6abc@slackbuilds.org>

> xen lists libssh2 as an optional dependency, but I can't find it at SBo.
> 
> It was there on Nov 10  2016, that's when I last built it.
> 
> Did I miss an announcement?

https://git.slackbuilds.org/slackbuilds/commit/?id=12dde3a325d5441a27dcd7ec48349d07af1073b0


-- 
Willy Sudiarto Raharjo

-------------- 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/20170605/2a832d3e/attachment.asc>

From duncan_roe at optusnet.com.au  Mon Jun  5 03:00:58 2017
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Mon, 5 Jun 2017 13:00:58 +1000
Subject: [Slackbuilds-users] What happened to libssh2?
Message-ID: <20170605030058.GB31383@dimstar.local.net>

xen lists libssh2 as an optional dependency, but I can't find it at SBo.

It was there on Nov 10  2016, that's when I last built it.

Did I miss an announcement?

Cheers ... Duncan.

From robby at rlworkman.net  Mon Jun  5 19:10:18 2017
From: robby at rlworkman.net (Robby Workman)
Date: Mon, 5 Jun 2017 14:10:18 -0500
Subject: [Slackbuilds-users] MaXX desktop - any takers?
Message-ID: <20170605141018.29f98b6d.robby@rlworkman.net>

So... I saw something somewhere about a MaXX desktop, a clone-ish
of SGI Irix desktop, and I got curious.

http://dev.maxxinteractive.com/trax/maxxdesktop

Well, I won't be using it, so I'm not going to submit and maintain
it, but if anyone else is interested, feel free to take it as your
own.

http://slackware.com/~rworkman/MaXX.tar.gz

-RW

From rworkman at slackbuilds.org  Mon Jun  5 19:12:52 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 5 Jun 2017 14:12:52 -0500
Subject: [Slackbuilds-users] MaXX desktop - any takers?
In-Reply-To: <20170605141018.29f98b6d.robby@rlworkman.net>
References: <20170605141018.29f98b6d.robby@rlworkman.net>
Message-ID: <20170605141252.7ab16e75@home.rlworkman.net>

On Mon, 5 Jun 2017 14:10:18 -0500
Robby Workman <robby at rlworkman.net> wrote:

> So... I saw something somewhere about a MaXX desktop, a clone-ish
> of SGI Irix desktop, and I got curious.
> 
> http://dev.maxxinteractive.com/trax/maxxdesktop
> 
> Well, I won't be using it, so I'm not going to submit and maintain
> it, but if anyone else is interested, feel free to take it as your
> own.
> 
> http://slackware.com/~rworkman/MaXX.tar.gz


Oh, and as an aside, it's quite likely that at least one of
the OpenMotif versions included in the build could be removed
in favor of the real motif included in Slackware, and there's
room for lots more cleanup of how it's packaged IF you are 
actually going to use it and maintain it through multiple
releases, but I'm done with it :-)

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

From kingbeowulf at gmail.com  Mon Jun  5 20:47:45 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 5 Jun 2017 13:47:45 -0700
Subject: [Slackbuilds-users] MaXX desktop - any takers?
In-Reply-To: <20170605141018.29f98b6d.robby@rlworkman.net>
References: <20170605141018.29f98b6d.robby@rlworkman.net>
Message-ID: <80d87538-6816-aac2-6c2c-025913e0f708@gmail.com>

On 06/05/2017 12:10 PM, Robby Workman wrote:
> So... I saw something somewhere about a MaXX desktop, a clone-ish
> of SGI Irix desktop, and I got curious.
> 
> http://dev.maxxinteractive.com/trax/maxxdesktop
> 
> Well, I won't be using it, so I'm not going to submit and maintain
> it, but if anyone else is interested, feel free to take it as your
> own.
> 
> http://slackware.com/~rworkman/MaXX.tar.gz
> 
> -RW


Waayyyy to much nostalgia for me.  Besides, maxxinteractive.com won't
load, maxxinteractive.co gives a hosting default page error and the only
site that loads is http://5dwm.org/ (a homage fan site) with dead links
except for sourceforge project page which has no files.

This does not instill me with a lot of confidence.  Besides, Thinking
back to late 20th Century WM/DEs (even CDE) just makes me feel old ;-)

-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/20170605/9cf36326/attachment.asc>

From matteo.bernardini at gmail.com  Mon Jun  5 21:32:45 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 5 Jun 2017 23:32:45 +0200
Subject: [Slackbuilds-users] MaXX desktop - any takers?
In-Reply-To: <80d87538-6816-aac2-6c2c-025913e0f708@gmail.com>
References: <20170605141018.29f98b6d.robby@rlworkman.net>
 <80d87538-6816-aac2-6c2c-025913e0f708@gmail.com>
Message-ID: <CAPsDuS4NRLR0o3Eit8MtzQgFCA_gZy48qNdOdGoE8DEOwkh-BA@mail.gmail.com>

we had two O2 in the office

https://en.wikipedia.org/wiki/SGI_O2

some realtime video effects they did are still amazing today.

they have also a facebook page https://www.facebook.com/maxxdesktop/

From chris.willing at iinet.net.au  Mon Jun  5 22:23:33 2017
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 6 Jun 2017 08:23:33 +1000
Subject: [Slackbuilds-users] MaXX desktop - any takers?
In-Reply-To: <CAPsDuS4NRLR0o3Eit8MtzQgFCA_gZy48qNdOdGoE8DEOwkh-BA@mail.gmail.com>
References: <20170605141018.29f98b6d.robby@rlworkman.net>
 <80d87538-6816-aac2-6c2c-025913e0f708@gmail.com>
 <CAPsDuS4NRLR0o3Eit8MtzQgFCA_gZy48qNdOdGoE8DEOwkh-BA@mail.gmail.com>
Message-ID: <0a9e85d3-7ae4-7530-f3df-fcc19b63280b@iinet.net.au>

On 06/06/17 07:32, Matteo Bernardini wrote:
> we had two O2 in the office
> 
> https://en.wikipedia.org/wiki/SGI_O2
> 
> some realtime video effects they did are still amazing today.
> 
> they have also a facebook page https://www.facebook.com/maxxdesktop/
>

For most of the 90's I worked in a visualization lab stocked exclusively
with SGI's on the desktop, starting out with mostly the Indigo model:
    https://en.wikipedia.org/wiki/SGI_Indigo
(also a small Cray Y-MP in the machine room - set behind glass so
visitors could admire it).

Anyway, ever since the Indigo machines were being replaced with O2's,
I've had an Indigo in storage - pretty much forgotten about till this
thread. I'd often thought about replacing the internals with a suitable
sized mobo running Linux but I see on the wikipedia page that NetBSD has
some support for Indigos. I wonder if mine still powers up?

chris

From willysr at slackbuilds.org  Tue Jun  6 01:22:25 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 6 Jun 2017 08:22:25 +0700
Subject: [Slackbuilds-users] Update - 20170606.1
Message-ID: <356622c6-e90c-9ff9-00fa-5f22bab4abd9@slackbuilds.org>

Hi Folks

Today marks 11 years since SBo was founded by Erik and Robby, so we make
an exception for this week's public update.

Happy 11th Anniversary for SBo!!!
At this moment, we have more than 6600 scripts in our repository, thanks
to all (past) maintainers who have done great contributions to this
project. Based on statistics, we have 460 contributors (active and
inactive) and 49.450 commits for this project.
We also got new hardware, thanks to the donation by the community
(https://slackbuilds.org/contributors/). It's now operational and
serving as the core infrastructure for this project.

Highlight for this batch of update:
We cut the remaining known build failure from last week's list down to 4
and we receive bunch of updates in the past few days, including the bump
of virtualbox to latest 5.0.x branch from Heinz.

Tue Jun  6 00:57:41 UTC 2017
academic/PyAMG: Update HOMEPAGE.
academic/libqalculate: Updated for version 0.9.12
academic/pyfits: Update deps.
academic/qalculate-gtk: Updated for version 0.9.12
audio/fst: Update DOWNLOAD url.
business/stansoft: Fix architecture naming.
desktop/oxygen-transparent: Removed.
desktop/razorqt: Update HOMEPAGE.
development/Bottleneck: Updated for version 1.2.1.
development/QStlink: Added (cross-platform STLinkV2 GUI).
development/acpica: Updated for version 20170531.
development/atom: Updated for version 1.17.2.
development/dwarf: Updated for version 20170416.
development/gsoap: Updated for version 2.8.46.
development/hugs98: Update DOWNLOAD url.
development/jupyter-nbconvert: Updated for version 5.2.1.
development/jupyter_console: Added (console frontend for Jupyter).
development/ming: Updated for version 0.4.8.
development/mkchroot: Updated for version 1.2.
development/mutagen: Updated for version 1.38.
development/ocambuild: Compress man pages.
development/xdebug: Updated for version 2.5.4.
games/bitfighter: Updated for version 019f.
games/fuse-emulator: Updated for version 1.3.6.
games/roccat-tools: Updated for version 5.6.0.
gis/Fiona: Updated for version 1.7.7.
gis/python-mapnik: Added (Python bindings for Mapnik).
graphics/Pixie: Update HOMEPAGE.
graphics/pngcrush: Fix x86 build.
graphics/scour: Added (python SVG cleaner).
libraries/QUSB: Fix VERSION.
libraries/dropbox-python: Updated for version 7.3.1.
libraries/libevhtp: Update DOWNLOAD url.
libraries/libmseed: Update HOMEPAGE.
libraries/libspectrum: Updated for version 1.3.4.
libraries/libx86emu: Updated for version 1.11.
libraries/live555: Updated for version 2017.06.04
libraries/php-imagick: Updated for version 3.4.3.
libraries/php-pgsql: Updated for version 5.6.30.
misc/KeePassHttp: Updated for version 1.8.4.2.
misc/gcp: Update to avoid dep download.
misc/kasumi: Updated for version 2.5.
misc/kronometer: Update HOMEPAGE and DOWNLOAD urls.
misc/zyGrib: Updated for version 8.0.1 + new maintainer.
network/cyrus-imapd: Update HOMEPAGE.
network/heimdal: Compress man pages.
network/hydra: Updated for version 8.5.
network/libident: Added (library for querying IDENT servers).
network/ngircd: Updated for version 24.
network/opera: Updated for version 45.0.2552.888.
network/seahub: Update DOWNLOAD url for x86_64.
network/slack: Fix path on x86_64.
network/twine: Updated for version 1.9.1.
network/you-get: Updated for version 0.4.750.
network/youtube-dl: Updated for version 2017.06.05.
office/basket: Added doinst.sh.
office/fop: Fix build against newer JDK.
perl/perl-Date-Manip: Updated for version 6.59.
perl/perl-ExtUtils-Install: Updated for version 2.14.
perl/perl-Glib-Object-Introspection: Updated for version 0.043.
perl/perl-Math-Decimal64: Updated for version 0.16.
perl/perl-Mojolicious: Updated for version 7.33.
perl/perl-linux-desktop-files: Updated for version 0.13.
python/PyRIC: Added (Linux wireless library for Python).
python/astroid: Updated for version 1.5.3.
python/autopep8: Updated for version 1.3.2.
python/jmespath: Updated for version 0.9.3.
python/lxml: Updated for version 3.8.0
python/netifaces: Updated for version 0.10.6
python/paramiko: Updated for version 2.1.2.
python/parsel: Updated for version 1.2.0.
python/py: Updated for version 1.4.34.
python/pytest: Updated for version 3.1.1.
python/python-keyring: Updated for version 10.3.3.
python/regex: Updated for version 2017.05.26.
python/selenium: Updated for version 3.4.3.
python/stevedore: Updated for version 1.23.0.
system/ZoneMinder: Fix man8 path.
system/apcupsd: Update build script.
system/cldr-emoji-annotation: Added (CLDR annotation files).
system/daemontools: Updated for version 0.76.
system/encfs: Updated for version 1.9.1.
system/firetools: Fix library path on x86_64.
system/fish: Updated for version 2.6.0.
system/fswatch: Added (A cross-platform file change monitor).
system/gammu: Updated for version 1.38.3.
system/hwinfo: Updated for version 21.46.
system/isdct: Update MD5SUM.
system/kbfs: Updated for version 1.0.24_20170601160157.
system/redis: Updated for version 3.2.9.
system/virtualbox-addons: Updated for version 5.0.40.
system/virtualbox-extension-pack: Updated for version 5.0.40.
system/virtualbox-kernel-addons: Updated for version 5.0.40.
system/virtualbox-kernel: Updated for version 5.0.40.
system/virtualbox: Updated for version 5.0.40.
system/xonsh: Updated for version 0.5.10.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- 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/20170606/2db6a9b0/attachment-0001.asc>

From slackbuilds at schoepfer.info  Tue Jun  6 07:43:49 2017
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 6 Jun 2017 09:43:49 +0200
Subject: [Slackbuilds-users] texlive download location
Message-ID: <856a4271-21d0-8f68-6543-25109f6f3145@schoepfer.info>

Hi,

texlive 2017 was released at the weekend, the 2016-tarball was removed 
from CTAN.
I'm working on the buildscripts for texlive 2017, meanwhile an SBo admin 
may change the downlaod-location to
http://slackware.schoepfer.info/slackbuilds/texlive/2016/texlive/texlive-20160523b-source.tar.xz
to keep the texlive-2016 build working.

Thanks,

Johannes

From matteo.bernardini at gmail.com  Tue Jun  6 08:33:35 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 6 Jun 2017 10:33:35 +0200
Subject: [Slackbuilds-users] texlive download location
In-Reply-To: <856a4271-21d0-8f68-6543-25109f6f3145@schoepfer.info>
References: <856a4271-21d0-8f68-6543-25109f6f3145@schoepfer.info>
Message-ID: <CAPsDuS7Ow5h4uZeu0CyArGpBuXttMo43BLDy94pTwd_-3y=nsg@mail.gmail.com>

2017-06-06 9:43 GMT+02:00 Franzen <slackbuilds at schoepfer.info>:
> Hi,
>
> texlive 2017 was released at the weekend, the 2016-tarball was removed from
> CTAN.
> I'm working on the buildscripts for texlive 2017, meanwhile an SBo admin may
> change the downlaod-location to
> http://slackware.schoepfer.info/slackbuilds/texlive/2016/texlive/texlive-20160523b-source.tar.xz
> to keep the texlive-2016 build working.

done in my branch.

Matteo

From thomas at beingboiled.info  Tue Jun  6 12:23:42 2017
From: thomas at beingboiled.info (Thomas Morper)
Date: Tue, 6 Jun 2017 14:23:42 +0200 (CEST)
Subject: [Slackbuilds-users] Update - 20170606.1
In-Reply-To: <356622c6-e90c-9ff9-00fa-5f22bab4abd9@slackbuilds.org>
References: <356622c6-e90c-9ff9-00fa-5f22bab4abd9@slackbuilds.org>
Message-ID: <alpine.LNX.2.21.1706061404490.608@ks3357608.2e128.net>

On Tue, 6 Jun 2017, Willy Sudiarto Raharjo wrote:

> network/slack: Fix path on x86_64.

This broke the package because the /usr/bin/slack symlink still points to 
the then non-existing /usr/lib/slack/slack. Also, the slack binaries don't 
support anything else than x86_64 currently, so there's no need to test 
$ARCH. A simple rename+relink should do.

  # Fix path
  mv $PKG/usr/lib $PKG/usr/lib64
  ( cd $PKG/usr/bin ; rm -f slack ; ln -s ../lib64/slack/slack )

-- 

From willysr at slackbuilds.org  Wed Jun  7 03:40:07 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 7 Jun 2017 10:40:07 +0700
Subject: [Slackbuilds-users] Update - 20170606.1
In-Reply-To: <alpine.LNX.2.21.1706061404490.608@ks3357608.2e128.net>
References: <356622c6-e90c-9ff9-00fa-5f22bab4abd9@slackbuilds.org>
 <alpine.LNX.2.21.1706061404490.608@ks3357608.2e128.net>
Message-ID: <a776059b-93d1-89e9-26b3-62bbd0b29042@slackbuilds.org>

> This broke the package because the /usr/bin/slack symlink still points to 
> the then non-existing /usr/lib/slack/slack. Also, the slack binaries don't 
> support anything else than x86_64 currently, so there's no need to test 
> $ARCH. A simple rename+relink should do.
> 
>   # Fix path
>   mv $PKG/usr/lib $PKG/usr/lib64
>   ( cd $PKG/usr/bin ; rm -f slack ; ln -s ../lib64/slack/slack )

Hi Thomas

I have applied your suggestion
please review the changes here
https://git.slackbuilds.org/slackbuilds/commit/?id=fc810ed28



-- 
Willy Sudiarto Raharjo

-------------- 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/20170607/6a9f87c4/attachment.asc>

From dn2010 at gmail.com  Wed Jun  7 04:36:14 2017
From: dn2010 at gmail.com (Daniil Bratashov)
Date: Wed, 7 Jun 2017 08:36:14 +0400
Subject: [Slackbuilds-users] texlive download location
In-Reply-To: <CAPsDuS7Ow5h4uZeu0CyArGpBuXttMo43BLDy94pTwd_-3y=nsg@mail.gmail.com>
References: <856a4271-21d0-8f68-6543-25109f6f3145@schoepfer.info>
 <CAPsDuS7Ow5h4uZeu0CyArGpBuXttMo43BLDy94pTwd_-3y=nsg@mail.gmail.com>
Message-ID: <CAJ6MA1F_3g3O_A8K1sji=UxjfgkHzy9nUumnR4furZQJHx1jWw@mail.gmail.com>

It is also non-working on -current with problems due to harfbuzz, so maybe
upgrading to texlive 2017 should be an option, it compiles fine.

WBR, Daniil Bratashov.

On Tue, Jun 6, 2017 at 12:33 PM, Matteo Bernardini <
matteo.bernardini at gmail.com> wrote:

> 2017-06-06 9:43 GMT+02:00 Franzen <slackbuilds at schoepfer.info>:
> > Hi,
> >
> > texlive 2017 was released at the weekend, the 2016-tarball was removed
> from
> > CTAN.
> > I'm working on the buildscripts for texlive 2017, meanwhile an SBo admin
> may
> > change the downlaod-location to
> > http://slackware.schoepfer.info/slackbuilds/texlive/2016/
> texlive/texlive-20160523b-source.tar.xz
> > to keep the texlive-2016 build working.
>
> done in my branch.
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170607/3eaf11bd/attachment.html>

From rworkman at slackbuilds.org  Wed Jun  7 13:54:53 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 7 Jun 2017 08:54:53 -0500
Subject: [Slackbuilds-users] Server maintenance this weekend
Message-ID: <20170607085453.4f12d763@home.rlworkman.net>

Just a heads-up: at some point this coming weekend, we will be doing some minor 
software enhancements and updates. Expect (hopefully) brief outages to http, ftp, 
rsync, and git services.  Mailing lists will still be available, and we'll of course still be 
on IRC.

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

From thomas at beingboiled.info  Wed Jun  7 14:09:15 2017
From: thomas at beingboiled.info (Thomas Morper)
Date: Wed, 7 Jun 2017 16:09:15 +0200 (CEST)
Subject: [Slackbuilds-users] Update - 20170606.1
In-Reply-To: <a776059b-93d1-89e9-26b3-62bbd0b29042@slackbuilds.org>
References: <356622c6-e90c-9ff9-00fa-5f22bab4abd9@slackbuilds.org>
 <alpine.LNX.2.21.1706061404490.608@ks3357608.2e128.net>
 <a776059b-93d1-89e9-26b3-62bbd0b29042@slackbuilds.org>
Message-ID: <alpine.LNX.2.21.1706071607540.608@ks3357608.2e128.net>

On Wed, 7 Jun 2017, Willy Sudiarto Raharjo wrote:

> I have applied your suggestion
> please review the changes here
> https://git.slackbuilds.org/slackbuilds/commit/?id=fc810ed28

Builds and works fine, thanks!

-- 

From rshepard at appl-ecosys.com  Thu Jun  8 19:35:41 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 8 Jun 2017 12:35:41 -0700 (PDT)
Subject: [Slackbuilds-users] Upgrading postgres
Message-ID: <alpine.LNX.2.11.1706081232030.11700@localhost>

   Now postgresql-9.6.2 is installed in /var/lib/pgsql/9.6/. To upgrade using
the SBo script to version -9.6.3 do I need to install it in a different
subdirectory then use pg_upgrade to transfer pointers to the binary and data
directories from the 9.6.2 location to the 9.6.3 location?

   Or, do I use pg_dumpall, upgrade micro versions, then use psql to read the
dumped data file into the new version?

Rich

From belka at caraus.de  Thu Jun  8 19:39:42 2017
From: belka at caraus.de (Eugen Wissner)
Date: Thu, 08 Jun 2017 21:39:42 +0200
Subject: [Slackbuilds-users] Upgrading postgres
In-Reply-To: <alpine.LNX.2.11.1706081232030.11700@localhost>
References: <alpine.LNX.2.11.1706081232030.11700@localhost>
Message-ID: <1496950782.1738.7.camel@caraus.de>

No, you don't.

You have to use pg_upgrade only if you make a major update (from 9.5 to
9.6 for example). Just build the package, stop postgresql, do
upgradepkg and start postgresql again.

Regards,
Eugene

Am Donnerstag, den 08.06.2017, 12:35 -0700 schrieb Rich Shepard:
> ???Now postgresql-9.6.2 is installed in /var/lib/pgsql/9.6/. To
> upgrade using
> the SBo script to version -9.6.3 do I need to install it in a
> different
> subdirectory then use pg_upgrade to transfer pointers to the binary
> and data
> directories from the 9.6.2 location to the 9.6.3 location?
> 
> ???Or, do I use pg_dumpall, upgrade micro versions, then use psql to
> read the
> dumped data file into the new version?
> 
> Rich
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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  Thu Jun  8 20:50:19 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 8 Jun 2017 13:50:19 -0700 (PDT)
Subject: [Slackbuilds-users] Upgrading postgres [RESOLVED]
In-Reply-To: <1496950782.1738.7.camel@caraus.de>
References: <alpine.LNX.2.11.1706081232030.11700@localhost>
 <1496950782.1738.7.camel@caraus.de>
Message-ID: <alpine.LNX.2.11.1706081346570.11700@localhost>

On Thu, 8 Jun 2017, Eugen Wissner wrote:

> No, you don't.

> You have to use pg_upgrade only if you make a major update (from 9.5 to
> 9.6 for example).

Eugene,

   That's what I understood when I read the pgupgrade page, but I've not
upgraded postgres at the third level before. Over the past couple of decades
I've stayed with older versions longer than I should, perhaps, but as a
single user I probably have no need for the latest enhancements.

> Just build the package, stop postgresql, do upgradepkg and start
> postgresql again.

   Well, that was certainly easy. Now I'm comfortable upgrading postgres to
keep current regardless of new version numbers.

Many thanks,

Rich

From adis at linux.org.ba  Thu Jun  8 21:07:14 2017
From: adis at linux.org.ba (Adis Nezirovic)
Date: Thu, 8 Jun 2017 23:07:14 +0200
Subject: [Slackbuilds-users] Upgrading postgres
In-Reply-To: <1496950782.1738.7.camel@caraus.de>
References: <alpine.LNX.2.11.1706081232030.11700@localhost>
 <1496950782.1738.7.camel@caraus.de>
Message-ID: <CALHPnvgHCT6Xrf6XSgsyxiHO-Ltac1HY=2pj2-NXpTjLGLLFnQ@mail.gmail.com>

Hi Rich,

While it is sensible to always have backups before doing the upgrade,
it is not necessary to run pg_upgrade or dump/restore cycle for minor
version updates, just follow Eugen's advice.

Best regards,
Adis

From rshepard at appl-ecosys.com  Thu Jun  8 21:28:22 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 8 Jun 2017 14:28:22 -0700 (PDT)
Subject: [Slackbuilds-users] Upgrading postgres
In-Reply-To: <CALHPnvgHCT6Xrf6XSgsyxiHO-Ltac1HY=2pj2-NXpTjLGLLFnQ@mail.gmail.com>
References: <alpine.LNX.2.11.1706081232030.11700@localhost>
 <1496950782.1738.7.camel@caraus.de>
 <CALHPnvgHCT6Xrf6XSgsyxiHO-Ltac1HY=2pj2-NXpTjLGLLFnQ@mail.gmail.com>
Message-ID: <alpine.LNX.2.11.1706081426530.11700@localhost>

On Thu, 8 Jun 2017, Adis Nezirovic wrote:

> While it is sensible to always have backups before doing the upgrade, it
> is not necessary to run pg_upgrade or dump/restore cycle for minor version
> updates, just follow Eugen's advice.

Adis,

   Thank you. I do run pg_dumpall before any postgres upgrade. The time
involved is so much less than restoring off the backup drive.

Regards,

Rich

From sombragris at sombragris.org  Thu Jun  8 22:55:03 2017
From: sombragris at sombragris.org (Eduardo Sanchez)
Date: Thu, 8 Jun 2017 18:55:03 -0400
Subject: [Slackbuilds-users] [Workaround] Problem running unvanquished
Message-ID: <neov9.4332150968.20170608185503.24ec88cf@loli.sombragris.org>

Using Slackware64-current, but I guess this is not related to any
Slackware-version.

The game "Unvanquished" fails to run. The relevant output is provided
below:

[eduardo:~]$
unvanquished Unvanquished 0.50 Linux x86_64 Jun  8
2017 cmdline: -libpath /usr/lib64/unvanquished
-pakpath /usr/share/games/unvanquished/pkg [FS] Lib
path: /usr/lib64/unvanquished [FS] Home
path: /home/eduardo/.unvanquished [FS] Pak search
path: /usr/share/games/unvanquished/pkg [FS] Pak search
path: /home/eduardo/.unvanquished/pkg [FS] Loading pak
'/usr/share/games/unvanquished/pkg/unvanquished_0.50.0.pk3'... Warn:
[FS] Could not find pak 'unvanquished' with version '0.49.0' required
by '/usr/share/games/unvanquished/pkg/unvanquished_0.50.0.pk3' Failed
to load pak 'unvanquished': Missing dependency Could not load base pak
'unvanquished', falling back to default 
couldn't exec
'default.cfg' Warn: Couldn't read conhistory: No such file or directory 
----- Client Initialization
----- Loading RSA keys from
pubkey Daemon RSA public-key
found. ----- Client Initialization Complete
----- Calling
GetRefAPI? SDL_Init( SDL_INIT_VIDEO
)... Using SDL Version
2.0.5 ]ATTENTION: default value of option force_s3tc_enable overridden
by environment. SDL using driver
"x11" Initializing OpenGL
display Display aspect:
1.778 ...setting mode
-2: 1920
1080 The change will take effect after
restart. The change will take effect after
restart. Warn: GLEW version < 2.0.0 doesn't support GL core profiles 
Using 24 Color bits, 24 depth, 8 stencil
display. Using GLEW
1.13.0 Using enhanced (GL3) Renderer in GL 2.x
mode... Available modes: '640x360 720x405 864x486 960x540 1024x576
1280x720 1600x900 1920x1080 1368x768 640x480 800x600 1024x768 1280x960
1400x1050 1280x1024 ' GL_RENDERER: Mesa DRI Intel(R) Haswell Mobile
Detected graphics driver class 'Mesa' Detected graphics hardware class
'generic' Initializing OpenGL extensions 
...ignoring GL_ARB_debug_output 
...found shading language version 130 
...using GL_ARB_half_float_pixel 
...using GL_ARB_texture_float 
...using GL_EXT_texture_integer 
...using GL_ARB_texture_rg 
...using GL_EXT_texture_filter_anisotropic 
...using GL_ARB_half_float_vertex 
...using GL_ARB_framebuffer_object 
...GL_ARB_get_program_binary found, but with no binary formats 
...using GL_ARB_buffer_storage 
...using GL_ARB_uniform_buffer_object 
...using GL_ARB_map_buffer_range 
...using GL_ARB_sync 
glsl shaders took 12574 msec to build 
Warn: R_InitImages: could not load 'gfx/2d/consolechars' 
[FS] Loading pak
'/usr/share/games/unvanquished/pkg/unvanquished_0.50.0.pk3'... Warn:
[FS] Could not find pak 'unvanquished' with version '0.49.0' required
by '/usr/share/games/unvanquished/pkg/unvanquished_0.50.0.pk3' Failed
to load pak 'unvanquished': Missing dependency Could not load base pak
'unvanquished', falling back to default 
[eduardo:~]$ 

======

I commented the problem upstream and with their instructions I was able
to run the game successfully. These changes should be made for the game
to successfully run:

1. First, the SlackBuild downloads just *one* pk3 file, while there
are many others. All these should be downloaded in the same location.

2. The 'daemon' executable should be alongside the /pkg directory. That
is, provided that this SlackBuild installs the pk3 files in
the /usr/share/games/unvanquished/pkg path, then it should install the
binaries in /usr/share/games/unvanquished.

Thanks,


Eduardo 
-- 
Eduardo S?nchez Gauto, Abog., Th.M.
Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol
Web: http://sombragris.org - Blog: http://shadow.sombragris.org
TW: @thegreyshadow - FB: /thegreyshadow
Tel?fono: (0991) 755-355 - Asunci?n, Paraguay
==================================================================
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170608/1a6175e1/attachment.asc>

From willysr at slackbuilds.org  Fri Jun  9 15:40:45 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 9 Jun 2017 22:40:45 +0700
Subject: [Slackbuilds-users] Server maintenance this weekend
In-Reply-To: <20170607085453.4f12d763@home.rlworkman.net>
References: <20170607085453.4f12d763@home.rlworkman.net>
Message-ID: <7f53e172-6099-877e-0751-ea1daf2e6739@slackbuilds.org>

> Just a heads-up: at some point this coming weekend, we will be doing some minor 
> software enhancements and updates. Expect (hopefully) brief outages to http, ftp, 
> rsync, and git services.  Mailing lists will still be available, and we'll of course still be 
> on IRC.

Follow ups from Robby's announcement:
the public update will be postponed AFTER the server maintenance is
finished.


-- 
Willy Sudiarto Raharjo

-------------- 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/20170609/47b041ac/attachment.asc>

From rworkman at slackbuilds.org  Sat Jun 10 02:13:56 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 9 Jun 2017 21:13:56 -0500
Subject: [Slackbuilds-users] Server maintenance this weekend
In-Reply-To: <20170607085453.4f12d763@home.rlworkman.net>
References: <20170607085453.4f12d763@home.rlworkman.net>
Message-ID: <20170609211356.08a6e539@home.rlworkman.net>

On Wed, 7 Jun 2017 08:54:53 -0500
Robby Workman <rworkman at slackbuilds.org> wrote:

> Just a heads-up: at some point this coming weekend, we will be doing
> some minor software enhancements and updates. Expect (hopefully)
> brief outages to http, ftp, rsync, and git services.  Mailing lists
> will still be available, and we'll of course still be on IRC.


Ping.  This will be occurring within the hour.

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

From willysr at slackbuilds.org  Sat Jun 10 04:11:59 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Jun 2017 11:11:59 +0700
Subject: [Slackbuilds-users] Updates - 20170610.1
Message-ID: <b382a246-093f-4597-36bd-b6a1d12b7eb2@slackbuilds.org>

Hi folks,

As the server maintenance is done, here comes the usual public update
highlight at weekend.

This week we have libvirt changes that saves running VMs on shutdown and
it will wait for 5 minutes before shutting down. You may need to adjust
the values if your VMs is quite big.

Tor browser is now bumped to 7.0 which is based on Firefox 52 ESR
release so it should be on par with what we have in -stable release. For
those who loves atom editor, but having problems on downloading all the
deps during build, we have atom-amd64 which is a precompiled version of
atom without any dependency.

Another important note: we have a new package skypeforlinux, which will
be replacing skype since upstream decided to kill the old legacy Skype
client (4.3 and older) per July 1. This new skypeforlinux works in
x86_64 only AND without multilib requirement. One more reason to start
migrating to x86_64 architecture. We will remove the old skype by
Saturday, July 1. As for now, we have put a notification in the README
so that gives user some time to migrate to the new client desktop
application.

Sat Jun 10 03:48:34 UTC 2017
academic/sage: Update README.
audio/clyrics: Updated for version 0.08.
audio/qjackctl: Updated for version 0.4.5.
audio/quodlibet: Updated for version 3.9.1.
desktop/ctwm: Updated for version 4.0.1.
development/CImg: Updated for version 2.0.0.
development/atom-amd64: Added (A hackable text editor).
development/hhvm: Updated for version 3.19.2.
development/mono-addins: Updated for version 1.3.5.
development/mono: Updated for version 5.0.1.1.
development/monodevelop: Remove nuget as dep.
development/zulu-openjdk7: Added (Open Implementation of JDK).
development/zulu-openjdk8: Added (Open Implementation of JDK).
games/instead: Updated for version 3.0.1.
games/iortcw: Updated for version 1.51.
games/mame: Updated for version 0.186, speed up build.
games/open-adventure: Added (Colossal Cave Adventure).
games/yamagi-quake2: Updated for version 7.00.
gis/Fiona: Reflect upstream change to source in md5sum.
gis/saga-gis: Updated for version 4.1.0.
graphics/opencollada: Updated for version 1.6.52
graphics/paraview: Updated for version 5.4.0
libraries/gnome-sharp: Updated for version 2.24.5.
libraries/gtk-sharp: Updated for version 2.12.43.
libraries/libgdiplus: Updated for version 5.4, new maintainer.
libraries/libjson-rpc-cpp: Added (C++ framework for json-rpc).
libraries/libmodplug: Updated for version 0.8.9.0
libraries/libvirt-python: Updated for version 3.4.0.
libraries/libvirt: Updated for version 3.4.0.
libraries/libvirt: managesave running VMs on shutdown by default
misc/dmg2img: Updated for version 1.6.7 + new maintainer.
network/Electrum: Updated for version 2.8.3.
network/TeamSpeak3: Updated for version 3.1.4, from multimedia.
network/dovecot: Updated for version 2.2.30.2.
network/firewalld: Added (dynamically managed firewall gui).
network/openfire: Updated for version 4.1.4.
network/skype: Put important notice in README.
network/skypeforlinux: Added (an instant messaging app).
network/slack: Fix symlink and remove ARCH detection.
network/slimjet: Updated for version 14.0.14.0.
network/tor-browser: Updated for version 7.0.
office/texlive: Changed download location.
perl/perl-Sidef: Updated for version 3.02.
perl/perl-Sub-Quote: Updated for version 2.004000.
perl/perl-local-lib: Updated for version 2.000023.
python/python-faulthandler: Added (display Python traceback).
python/python-fonttools: Updated for version 3.13.1.
python/python-slip: Added (convenience & extension code).
system/TLP: Updated for version 1.0.
system/acd_cli: Removed (discontinued upstream).
system/asbt: Updated for version 1.9.0.
system/conky: Fixed building with gcc-7.
system/fzf: Updated for version 0.16.8.
system/inxi: Updated for version 2.3.12.
system/openrc: Updated for version 0.27.
system/phoronix-test-suite: Updated for version 7.2.0.
system/qemu-guest-agent: Updated for version 2.9.0.
system/qemu: Updated for version 2.9.0.
system/the_silver_searcher: Updated for version 2.0.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- 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/20170610/4149edd1/attachment.asc>

From rworkman at slackbuilds.org  Sat Jun 10 05:04:31 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 10 Jun 2017 00:04:31 -0500
Subject: [Slackbuilds-users] Updates - 20170610.1
In-Reply-To: <b382a246-093f-4597-36bd-b6a1d12b7eb2@slackbuilds.org>
References: <b382a246-093f-4597-36bd-b6a1d12b7eb2@slackbuilds.org>
Message-ID: <20170610000431.6d81aa4c@home.rlworkman.net>

On Sat, 10 Jun 2017 11:11:59 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> As the server maintenance is done, here comes the usual public update
> highlight at weekend.


This "routine" maintenance has been a bit more frequent than we'd
like lately, especially given that we just switched over to new
hardware, but it seems that no matter how much we planned for a
nice easy transition, we keep finding some little nits that need
to be addressed.


> This week we have libvirt changes that saves running VMs on shutdown
> and it will wait for 5 minutes before shutting down. You may need to
> adjust the values if your VMs is quite big.


This seems to work well, for what it's worth - it's now been tested
on our own infrastructure :-)

I just pushed another commit to libvirt in my git branch to fixup
the default polkit rules (it won't affect anyone by default, but
it *will* affect you if you enable polkit access_control in 
libvirtd.conf) and installed the example polkit acl rules file to
the package documentation. Without going into great detail, I'll
just say that you should perform extensive testing of that before
you put it into production :-)


> network/firewalld: Added (dynamically managed firewall gui).


This was added by me, but I'd like to publicly state that I do not
and cannot ever imagine actually using it. It's something that I've
seen a few people here and there mention wanting, and I suppose it
could be useful in some situations, so I did a build for it. However,
if anyone wants to adopt it and maintain it down the road, consider
this an invitation.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170610/7bd4908c/attachment-0001.asc>

From ricardo at palmtx.com.ar  Sat Jun 10 23:57:47 2017
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Sat, 10 Jun 2017 20:57:47 -0300
Subject: [Slackbuilds-users] Typo in netifaces/README
Message-ID: <c41f71741eaa8d556896f5935cb7f186@palmtx.com.ar>

Hi, I noticed a typo in netifaces/README:

"Note: To install python3 bindings pass PYTHON3=yes to the slackbuild.

PYTHON3=yes ./six.SlackBuild"


Surely that's:

PYTHON3=yes ./netifaces.SlackBuild

CC'ed slackbuilds-users in case one of the admins can fix it on their 
end.

Cheers!
-- 
Living la vida Linux!

From willysr at slackbuilds.org  Sun Jun 11 00:01:42 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 11 Jun 2017 07:01:42 +0700
Subject: [Slackbuilds-users] Typo in netifaces/README
In-Reply-To: <c41f71741eaa8d556896f5935cb7f186@palmtx.com.ar>
References: <c41f71741eaa8d556896f5935cb7f186@palmtx.com.ar>
Message-ID: <8c973d61-5e07-e5cb-941c-b5f331afbaf9@slackbuilds.org>

> Hi, I noticed a typo in netifaces/README:
> 
> "Note: To install python3 bindings pass PYTHON3=yes to the slackbuild.
> 
> PYTHON3=yes ./six.SlackBuild"
> 
> 
> Surely that's:
> 
> PYTHON3=yes ./netifaces.SlackBuild
> 
> CC'ed slackbuilds-users in case one of the admins can fix it on their end.

Fixed on my branch

Thanks for the report


-- 
Willy Sudiarto Raharjo

-------------- 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/20170611/f145c80d/attachment.asc>

From rworkman at slackbuilds.org  Sun Jun 11 04:15:11 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 10 Jun 2017 23:15:11 -0500
Subject: [Slackbuilds-users] Brief server outage - upcoming
Message-ID: <20170610231511.03ab516e@home.rlworkman.net>

Well, it seems that we've encountered a bug with libvirt
<https://bugzilla.redhat.com/show_bug.cgi?id=1416043>
that showed up after enabling polkit access checking, 
and we didn't realize that a reboot of the host was
recommended before starting libvirt like that.

Long story short, we'll be rebooting the host machine
soon. Service outage should be brief, but last time
I said that, there was a problem - cross your fingers...

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

From rworkman at slackbuilds.org  Sun Jun 11 04:58:35 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 10 Jun 2017 23:58:35 -0500
Subject: [Slackbuilds-users] Brief server outage - upcoming
In-Reply-To: <20170610231511.03ab516e@home.rlworkman.net>
References: <20170610231511.03ab516e@home.rlworkman.net>
Message-ID: <20170610235835.03f8c821@home.rlworkman.net>

On Sat, 10 Jun 2017 23:15:11 -0500
Robby Workman <rworkman at slackbuilds.org> wrote:

> Well, it seems that we've encountered a bug with libvirt
> <https://bugzilla.redhat.com/show_bug.cgi?id=1416043>
> that showed up after enabling polkit access checking, 
> and we didn't realize that a reboot of the host was
> recommended before starting libvirt like that.
> 
> Long story short, we'll be rebooting the host machine
> soon. Service outage should be brief, but last time
> I said that, there was a problem - cross your fingers...


All of you who didn't cross your fingers are to be blamed.
However, we are back up, even though the outage was less
brief than was planned.

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

From fernando.lopezjr at gmail.com  Mon Jun 12 06:37:50 2017
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Mon, 12 Jun 2017 00:37:50 -0600
Subject: [Slackbuilds-users] re-package a java program?
In-Reply-To: <73396BCF-004E-4109-B216-17C86E61EECE@gmail.com>
References: <CALrQ46CKcEXQbhAVXZ8NAnvraCd2YDwroHE9-BJqwq9on5Q4gg@mail.gmail.com>
 <73396BCF-004E-4109-B216-17C86E61EECE@gmail.com>
Message-ID: <CALrQ46CS7h_AYdf1jc+X1HebDS2dGV7gP=6vyjh8+f-2w_qeEg@mail.gmail.com>

any ideas where I could host this package? since official web page requires
registration for download =(

On Mon, May 22, 2017 at 2:08 AM, ??????? ?????????? <korgie at gmail.com>
wrote:

> 22 ??? 2017, 8:55 ??, ?/? Fernando Lopez <fernando.lopezjr at gmail.com>
> ??????:
>
> Any guidelines on how to repackage a java program? Any existing
> buildscript examples?
>
>
> Josm is helpful?
>
> or anyone willing to do it for me... I'll maintain it afterwards.
>
> this is the intended victim:
> http://www.st.com/en/embedded-software/stsw-link007.html
>
> --
>
> ------------
> Regards,
>     Fernando Lopez Jr.
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170612/a012c732/attachment.html>

From alexm0n at gmail.com  Mon Jun 12 06:58:35 2017
From: alexm0n at gmail.com (Alexander Grotewohl)
Date: Mon, 12 Jun 2017 02:58:35 -0400
Subject: [Slackbuilds-users] re-package a java program?
In-Reply-To: <CALrQ46CS7h_AYdf1jc+X1HebDS2dGV7gP=6vyjh8+f-2w_qeEg@mail.gmail.com>
References: <CALrQ46CKcEXQbhAVXZ8NAnvraCd2YDwroHE9-BJqwq9on5Q4gg@mail.gmail.com>
 <73396BCF-004E-4109-B216-17C86E61EECE@gmail.com>
 <CALrQ46CS7h_AYdf1jc+X1HebDS2dGV7gP=6vyjh8+f-2w_qeEg@mail.gmail.com>
Message-ID: <CAKuLEQ0Mhm4TvQbt_G4eYyU+1evMxOW34cqvfQ6hmQc-orpwuQ@mail.gmail.com>

I'm not entirely sure it's a good idea to circumvent their registration
system..

The license is also worded in a way that could be taken as "anyone who
downloads this from ST only has license to use it" (ie: no distributing it
further)

Alex

On Jun 12, 2017 2:37 AM, "Fernando Lopez" <fernando.lopezjr at gmail.com>
wrote:

> any ideas where I could host this package? since official web page
> requires registration for download =(
>
> On Mon, May 22, 2017 at 2:08 AM, ??????? ?????????? <korgie at gmail.com>
> wrote:
>
>> 22 ??? 2017, 8:55 ??, ?/? Fernando Lopez <fernando.lopezjr at gmail.com>
>> ??????:
>>
>> Any guidelines on how to repackage a java program? Any existing
>> buildscript examples?
>>
>>
>> Josm is helpful?
>>
>> or anyone willing to do it for me... I'll maintain it afterwards.
>>
>> this is the intended victim:
>> http://www.st.com/en/embedded-software/stsw-link007.html
>>
>> --
>>
>> ------------
>> Regards,
>>     Fernando Lopez Jr.
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - 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
> http://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/20170612/ac738779/attachment-0001.html>

From fernando.lopezjr at gmail.com  Mon Jun 12 07:00:02 2017
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Mon, 12 Jun 2017 01:00:02 -0600
Subject: [Slackbuilds-users] re-package a java program?
In-Reply-To: <CAKuLEQ0Mhm4TvQbt_G4eYyU+1evMxOW34cqvfQ6hmQc-orpwuQ@mail.gmail.com>
References: <CALrQ46CKcEXQbhAVXZ8NAnvraCd2YDwroHE9-BJqwq9on5Q4gg@mail.gmail.com>
 <73396BCF-004E-4109-B216-17C86E61EECE@gmail.com>
 <CALrQ46CS7h_AYdf1jc+X1HebDS2dGV7gP=6vyjh8+f-2w_qeEg@mail.gmail.com>
 <CAKuLEQ0Mhm4TvQbt_G4eYyU+1evMxOW34cqvfQ6hmQc-orpwuQ@mail.gmail.com>
Message-ID: <CALrQ46A82ETSUZxzJgdWGTfsLNvke0Jyzb65gbb9eWeAZAC8WQ@mail.gmail.com>

fooc =\

On Mon, Jun 12, 2017 at 12:58 AM, Alexander Grotewohl <alexm0n at gmail.com>
wrote:

> I'm not entirely sure it's a good idea to circumvent their registration
> system..
>
> The license is also worded in a way that could be taken as "anyone who
> downloads this from ST only has license to use it" (ie: no distributing it
> further)
>
> Alex
>
> On Jun 12, 2017 2:37 AM, "Fernando Lopez" <fernando.lopezjr at gmail.com>
> wrote:
>
>> any ideas where I could host this package? since official web page
>> requires registration for download =(
>>
>> On Mon, May 22, 2017 at 2:08 AM, ??????? ?????????? <korgie at gmail.com>
>> wrote:
>>
>>> 22 ??? 2017, 8:55 ??, ?/? Fernando Lopez <fernando.lopezjr at gmail.com>
>>> ??????:
>>>
>>> Any guidelines on how to repackage a java program? Any existing
>>> buildscript examples?
>>>
>>>
>>> Josm is helpful?
>>>
>>> or anyone willing to do it for me... I'll maintain it afterwards.
>>>
>>> this is the intended victim:
>>> http://www.st.com/en/embedded-software/stsw-link007.html
>>>
>>> --
>>>
>>> ------------
>>> Regards,
>>>     Fernando Lopez Jr.
>>>
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>>
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - 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
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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/20170612/9c52a296/attachment.html>

From dchmelik at gmail.com  Mon Jun 12 10:00:23 2017
From: dchmelik at gmail.com (David Melik)
Date: Mon, 12 Jun 2017 03:00:23 -0700
Subject: [Slackbuilds-users] AQEMU?
Message-ID: <a9b2a161-10df-3e15-1952-03a9f37ab1e2@gmail.com>

I saw AQEMU released another version last year or so. Someone (Robby 
Workman?) abandoned the SlackBuild because of years of no releases 
before that, but now that they restarted, what about restarting the 
SlackBuild? I just reused the old one with version number update, and it 
works. AQEMU is a lot easier for me than all the other virtual machines, 
which seem to be more of a hassle to set up and use (too many options to 
choose, too many things to have to set up or install you don't need, 
etc.) QEMU just works.

-- 
Sincerely,
David
http://davidchmelik.com/ (homesite, updated first)
http://www.cwu.edu/~melikd/ (most stable homepage)


From gerardo.zamudio at linux.com  Mon Jun 12 13:36:35 2017
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Mon, 12 Jun 2017 08:36:35 -0500
Subject: [Slackbuilds-users] Updates - 20170603.1
In-Reply-To: <9d21cdcd-b201-146a-1538-719945c0e581@slackbuilds.org>
References: <2b38994e-2416-3d2e-518f-c6868422b017@slackbuilds.org>
 <6fce33dc-5076-fde3-b99b-3c19c0501865@linux.com>
 <9d21cdcd-b201-146a-1538-719945c0e581@slackbuilds.org>
Message-ID: <6ef187ed-30d6-f2ee-7615-9c12789a1bbe@linux.com>



On 06/03/2017 06:57 PM, Willy Sudiarto Raharjo wrote:
>>> games/roccat-tools (due to updated libgaminggear)
>>
>> I will fix this. New version of roccat-tools requires some changes to
>> build properly.
> 
> Hi Gerardo
> 
> B. Watson has send me a patch for this and it's now already on my
> branch. Can you verify whether this new version works with roccat
> hardware (we both don't have one)
> https://git.slackbuilds.org/slackbuilds/commit/?id=13445c133
> 
> Thanks
> 

I've tested this with my Roccat Kone Pure (ROC-11-700) and it works.
Thanks for the update, B. Watson.

Willy, please remove lines 30-31.

In the future I'd like a chance to tackle these issues myself

Regards,
Gerardo Zamudio

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

From falsetti at clansco.org  Mon Jun 12 15:30:45 2017
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Mon, 12 Jun 2017 17:30:45 +0200
Subject: [Slackbuilds-users] gpsbabel, long list of errors
Message-ID: <20170612173045.cb1a27fd12e2b649a21926a4@clansco.org>

Hi, anybody can build gpsbabel ?

error Qt requires a C++11 compiler and yours does not seem to be that.
a long list of errors and 

In file included from /usr/include/qt5/QtCore/qshareddata.h:46:0,
                 from /usr/include/qt5/QtCore/qdatetime.h:45,
                 from /usr/include/qt5/QtCore/QDateTime:1,
                 from src/core/datetime.h:27,
                 from defs.h:39,
                 from main.cc:22:
/usr/include/qt5/QtCore/qhash.h: Dans la fonction membre 'QPair<QHash<K, V>::iterator, QHash<K, V>::iterator> QHash<K, V>::equal_range(const Key&)':
/usr/include/qt5/QtCore/qhash.h:957:5: attention : 'auto' changes meaning in C++11; please remove it [-Wc++0x-compat]
     auto pair = qAsConst(*this).equal_range(akey);
     ^
/usr/include/qt5/QtCore/qhash.h:957:10: erreur: 'pair' does not name a type
     auto pair = qAsConst(*this).equal_range(akey);
          ^
/usr/include/qt5/QtCore/qhash.h:958:31: erreur: 'pair' was not declared in this scope
     return qMakePair(iterator(pair.first.i), iterator(pair.second.i));
                               ^
/usr/include/qt5/QtCore/qhash.h:958:31: note: suggested alternative:
In file included from /usr/include/c++/5.3.0/utility:70:0,
                 from /usr/include/qt5/QtCore/qcompilerdetection.h:1001,
                 from /usr/include/qt5/QtCore/qglobal.h:83,
                 from /usr/include/qt5/QtCore/qchar.h:43,
                 from /usr/include/qt5/QtCore/qstring.h:48,
                 from /usr/include/qt5/QtCore/qtextcodec.h:43,
                 from /usr/include/qt5/QtCore/QTextCodec:1,
                 from main.cc:20:
/usr/include/c++/5.3.0/bits/stl_pair.h:96:12: note:   'std::pair'
     struct pair
            ^
Makefile:128: recipe for target 'main.o' failed
make: *** [main.o] Error 1

From kingbeowulf at gmail.com  Mon Jun 12 16:32:13 2017
From: kingbeowulf at gmail.com (Edward Koenig)
Date: Mon, 12 Jun 2017 09:32:13 -0700
Subject: [Slackbuilds-users] AQEMU?
In-Reply-To: <a9b2a161-10df-3e15-1952-03a9f37ab1e2@gmail.com>
References: <a9b2a161-10df-3e15-1952-03a9f37ab1e2@gmail.com>
Message-ID: <D22C06FE-47AC-46C5-9697-66954E1B6062@gmail.com>




Sent from my iPad
> On Jun 12, 2017, at 3:00 AM, David Melik <dchmelik at gmail.com> wrote:
> 
> I saw AQEMU released another version last year or so. Someone (Robby Workman?) abandoned the SlackBuild because of years of no releases before that, but now that they restarted, what about restarting the SlackBuild? I just reused the old one with version number update, and it works. AQEMU is a lot easier for me than all the other virtual machines, which seem to be more of a hassle to set up and use (too many options to choose, too many things to have to set up or install you don't need, etc.) QEMU just works.
> 
> -- 
> Sincerely,
> David
> 

Looks promising.  I took used aqemu ages ago but stopped when upstream stalled (compile and emu support) .  I ended up just writing a shell script with zenity to avoid virt-manager.

My qemu-2.9.0 update is live now on SBo. Is that the version you're using?  I might give it a shot later this week.  Qemu development is pretty active so let's hope aqemu can keep up!

-Ed


From sam_web at yahoo.de  Mon Jun 12 19:11:16 2017
From: sam_web at yahoo.de (Marek Srejma)
Date: Mon, 12 Jun 2017 21:11:16 +0200
Subject: [Slackbuilds-users] gpsbabel, long list of errors
In-Reply-To: <20170612173045.cb1a27fd12e2b649a21926a4@clansco.org>
References: <20170612173045.cb1a27fd12e2b649a21926a4@clansco.org>
Message-ID: <faf0330d-10fb-a768-cfcf-1b9f8fafc560@yahoo.de>

Here I attached a patch which fixes that error.
To apply it, copy that file to your directory with gpsbabel.SlackBuild 
and run the command:

        patch -p1 < cxx-fix.patch

It adds "-std=c++11" to the C++ compiler flags.
After that gpsbabel.SlackBuild should build fine.

However, on my machine with QT5 it showed a new error:

    Info: creating stash file
    /home/tmp/SBo/gpsbabel-gpsbabel_1_5_3/gui/.qmake.stash
    Project ERROR: Unknown module(s) in QT: webkit webkitwidgets
    Makefile:387: recipe for target 'gui' failed

So I'll build qt5-webkit from SBo (which usually takes several hours to 
compile) and then try again.



Fr?d?ric Falsetti schrieb:
> Hi, anybody can build gpsbabel ?
>
> error Qt requires a C++11 compiler and yours does not seem to be that.
> a long list of errors and
>
> In file included from /usr/include/qt5/QtCore/qshareddata.h:46:0,
>                   from /usr/include/qt5/QtCore/qdatetime.h:45,
>                   from /usr/include/qt5/QtCore/QDateTime:1,
>                   from src/core/datetime.h:27,
>                   from defs.h:39,
>                   from main.cc:22:
> /usr/include/qt5/QtCore/qhash.h: Dans la fonction membre 'QPair<QHash<K, V>::iterator, QHash<K, V>::iterator> QHash<K, V>::equal_range(const Key&)':
> /usr/include/qt5/QtCore/qhash.h:957:5: attention : 'auto' changes meaning in C++11; please remove it [-Wc++0x-compat]
>       auto pair = qAsConst(*this).equal_range(akey);
>       ^
> /usr/include/qt5/QtCore/qhash.h:957:10: erreur: 'pair' does not name a type
>       auto pair = qAsConst(*this).equal_range(akey);
>            ^
> /usr/include/qt5/QtCore/qhash.h:958:31: erreur: 'pair' was not declared in this scope
>       return qMakePair(iterator(pair.first.i), iterator(pair.second.i));
>                                 ^
> /usr/include/qt5/QtCore/qhash.h:958:31: note: suggested alternative:
> In file included from /usr/include/c++/5.3.0/utility:70:0,
>                   from /usr/include/qt5/QtCore/qcompilerdetection.h:1001,
>                   from /usr/include/qt5/QtCore/qglobal.h:83,
>                   from /usr/include/qt5/QtCore/qchar.h:43,
>                   from /usr/include/qt5/QtCore/qstring.h:48,
>                   from /usr/include/qt5/QtCore/qtextcodec.h:43,
>                   from /usr/include/qt5/QtCore/QTextCodec:1,
>                   from main.cc:20:
> /usr/include/c++/5.3.0/bits/stl_pair.h:96:12: note:   'std::pair'
>       struct pair
>              ^
> Makefile:128: recipe for target 'main.o' failed
> make: *** [main.o] Error 1
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: cxx-fix.patch
Type: text/x-patch
Size: 382 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170612/2a660da9/attachment-0001.bin>

From rworkman at slackbuilds.org  Mon Jun 12 19:27:13 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 12 Jun 2017 14:27:13 -0500
Subject: [Slackbuilds-users] AQEMU?
In-Reply-To: <a9b2a161-10df-3e15-1952-03a9f37ab1e2@gmail.com>
References: <a9b2a161-10df-3e15-1952-03a9f37ab1e2@gmail.com>
Message-ID: <20170612142713.7f97d488@home.rlworkman.net>

On Mon, 12 Jun 2017 03:00:23 -0700
David Melik <dchmelik at gmail.com> wrote:

> I saw AQEMU released another version last year or so. Someone (Robby 
> Workman?) abandoned the SlackBuild because of years of no releases 
> before that, but now that they restarted, what about restarting the 
> SlackBuild? I just reused the old one with version number update, and
> it works. AQEMU is a lot easier for me than all the other virtual
> machines, which seem to be more of a hassle to set up and use (too
> many options to choose, too many things to have to set up or install
> you don't need, etc.) QEMU just works.


This new version requires qt5, but it shouldn't be problematic
otherwise. I'll look into bringing it back since upstream is
alive again.

-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/20170612/27fc028f/attachment.asc>

From kingbeowulf at gmail.com  Mon Jun 12 19:43:54 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 12 Jun 2017 12:43:54 -0700
Subject: [Slackbuilds-users] AQEMU?
In-Reply-To: <20170612142713.7f97d488@home.rlworkman.net>
References: <a9b2a161-10df-3e15-1952-03a9f37ab1e2@gmail.com>
 <20170612142713.7f97d488@home.rlworkman.net>
Message-ID: <60b9d6fa-486f-54d3-0bee-9b9cb7643c00@gmail.com>

On 06/12/2017 12:27 PM, Robby Workman wrote:
> On Mon, 12 Jun 2017 03:00:23 -0700
> David Melik <dchmelik at gmail.com> wrote:
> 
>> I saw AQEMU released another version last year or so. Someone (Robby 
>> Workman?) abandoned the SlackBuild because of years of no releases 
>> before that, but now that they restarted, what about restarting the 
>> SlackBuild? I just reused the old one with version number update, and
>> it works. AQEMU is a lot easier for me than all the other virtual
>> machines, which seem to be more of a hassle to set up and use (too
>> many options to choose, too many things to have to set up or install
>> you don't need, etc.) QEMU just works.
> 
> 
> This new version requires qt5, but it shouldn't be problematic
> otherwise. I'll look into bringing it back since upstream is
> alive again.
> 
> -RW 
> 
> 

Robby,
Since I have qemu, I was going to check "soon" (later today?) and maybe
take it on.  I used aqemu ages ago (qemu 1.4?) and liked it - way
simpler than wrestling with virt-manager/libvirt for features I'll never
use.  I already have qt5 built/installed for another program.

However, if you are just dying to take on another task...far be it from
me to stand in the way of your happiness ;-)

-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/20170612/440b4464/attachment.asc>

From rworkman at slackbuilds.org  Mon Jun 12 20:07:04 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 12 Jun 2017 15:07:04 -0500
Subject: [Slackbuilds-users] AQEMU?
In-Reply-To: <60b9d6fa-486f-54d3-0bee-9b9cb7643c00@gmail.com>
References: <a9b2a161-10df-3e15-1952-03a9f37ab1e2@gmail.com>
 <20170612142713.7f97d488@home.rlworkman.net>
 <60b9d6fa-486f-54d3-0bee-9b9cb7643c00@gmail.com>
Message-ID: <20170612150704.794d6f9c@home.rlworkman.net>

On Mon, 12 Jun 2017 12:43:54 -0700
King Beowulf <kingbeowulf at gmail.com> wrote:

> On 06/12/2017 12:27 PM, Robby Workman wrote:
> > On Mon, 12 Jun 2017 03:00:23 -0700
> > David Melik <dchmelik at gmail.com> wrote:
> >   
> >> I saw AQEMU released another version last year or so. Someone
> >> (Robby Workman?) abandoned the SlackBuild because of years of no
> >> releases before that, but now that they restarted, what about
> >> restarting the SlackBuild? I just reused the old one with version
> >> number update, and it works. AQEMU is a lot easier for me than all
> >> the other virtual machines, which seem to be more of a hassle to
> >> set up and use (too many options to choose, too many things to
> >> have to set up or install you don't need, etc.) QEMU just works.  
> > 
> > 
> > This new version requires qt5, but it shouldn't be problematic
> > otherwise. I'll look into bringing it back since upstream is
> > alive again.
> > 
> 
> Robby,
> Since I have qemu, I was going to check "soon" (later today?) and
> maybe take it on.  I used aqemu ages ago (qemu 1.4?) and liked it -
> way simpler than wrestling with virt-manager/libvirt for features
> I'll never use.  I already have qt5 built/installed for another
> program.
> 
> However, if you are just dying to take on another task...far be it
> from me to stand in the way of your happiness ;-)


I'm genuinely curious now, and I a few hours of passive involvement
every day for the remainder of the week, so I'll probably keep at
it. However, you can be the maintainer :)

-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/20170612/179ed65b/attachment.asc>

From sam_web at yahoo.de  Mon Jun 12 23:30:03 2017
From: sam_web at yahoo.de (Marek Srejma)
Date: Tue, 13 Jun 2017 01:30:03 +0200
Subject: [Slackbuilds-users] gpsbabel, long list of errors
In-Reply-To: <faf0330d-10fb-a768-cfcf-1b9f8fafc560@yahoo.de>
References: <20170612173045.cb1a27fd12e2b649a21926a4@clansco.org>
 <faf0330d-10fb-a768-cfcf-1b9f8fafc560@yahoo.de>
Message-ID: <30f84de7-6f1b-dcc6-29f8-126a7a7548d1@yahoo.de>

After building and installing qt5-webkit, I ran the SlackBuild again and 
the command "make gui" in the SlackBuild threw another error like "Qt 
requires a C++11 compiler and yours does not seem to be that.".
So I made another patch which fixes that error and attached it here.



Marek Srejma schrieb:
> Here I attached a patch which fixes that error.
> To apply it, copy that file to your directory with gpsbabel.SlackBuild 
> and run the command:
>
>        patch -p1 < cxx-fix.patch
>
> It adds "-std=c++11" to the C++ compiler flags.
> After that gpsbabel.SlackBuild should build fine.
>
> However, on my machine with QT5 it showed a new error:
>
>    Info: creating stash file
>    /home/tmp/SBo/gpsbabel-gpsbabel_1_5_3/gui/.qmake.stash
>    Project ERROR: Unknown module(s) in QT: webkit webkitwidgets
>    Makefile:387: recipe for target 'gui' failed
>
> So I'll build qt5-webkit from SBo (which usually takes several hours 
> to compile) and then try again.
>
>
>
> Fr?d?ric Falsetti schrieb:
>> Hi, anybody can build gpsbabel ?
>>
>> error Qt requires a C++11 compiler and yours does not seem to be that.
>> a long list of errors and
>>
>> In file included from /usr/include/qt5/QtCore/qshareddata.h:46:0,
>>                   from /usr/include/qt5/QtCore/qdatetime.h:45,
>>                   from /usr/include/qt5/QtCore/QDateTime:1,
>>                   from src/core/datetime.h:27,
>>                   from defs.h:39,
>>                   from main.cc:22:
>> /usr/include/qt5/QtCore/qhash.h: Dans la fonction membre 
>> 'QPair<QHash<K, V>::iterator, QHash<K, V>::iterator> QHash<K, 
>> V>::equal_range(const Key&)':
>> /usr/include/qt5/QtCore/qhash.h:957:5: attention : 'auto' changes 
>> meaning in C++11; please remove it [-Wc++0x-compat]
>>       auto pair = qAsConst(*this).equal_range(akey);
>>       ^
>> /usr/include/qt5/QtCore/qhash.h:957:10: erreur: 'pair' does not name 
>> a type
>>       auto pair = qAsConst(*this).equal_range(akey);
>>            ^
>> /usr/include/qt5/QtCore/qhash.h:958:31: erreur: 'pair' was not 
>> declared in this scope
>>       return qMakePair(iterator(pair.first.i), iterator(pair.second.i));
>>                                 ^
>> /usr/include/qt5/QtCore/qhash.h:958:31: note: suggested alternative:
>> In file included from /usr/include/c++/5.3.0/utility:70:0,
>>                   from 
>> /usr/include/qt5/QtCore/qcompilerdetection.h:1001,
>>                   from /usr/include/qt5/QtCore/qglobal.h:83,
>>                   from /usr/include/qt5/QtCore/qchar.h:43,
>>                   from /usr/include/qt5/QtCore/qstring.h:48,
>>                   from /usr/include/qt5/QtCore/qtextcodec.h:43,
>>                   from /usr/include/qt5/QtCore/QTextCodec:1,
>>                   from main.cc:20:
>> /usr/include/c++/5.3.0/bits/stl_pair.h:96:12: note: 'std::pair'
>>       struct pair
>>              ^
>> Makefile:128: recipe for target 'main.o' failed
>> make: *** [main.o] Error 1
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: cxx-fix.patch
Type: text/x-patch
Size: 535 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170613/4e5b5b6b/attachment.bin>

From elyk03 at gmail.com  Tue Jun 13 02:16:34 2017
From: elyk03 at gmail.com (Kyle Guinn)
Date: Mon, 12 Jun 2017 21:16:34 -0500
Subject: [Slackbuilds-users] gpsbabel, long list of errors
In-Reply-To: <20170612173045.cb1a27fd12e2b649a21926a4@clansco.org>
References: <20170612173045.cb1a27fd12e2b649a21926a4@clansco.org>
Message-ID: <CAJCpn82bvkWXhjtRaBbBND=0-TKKR8nxu-LMuOV5gt8tkudjhg@mail.gmail.com>

On 6/12/17, Fr?d?ric Falsetti <falsetti at clansco.org> wrote:
> Hi, anybody can build gpsbabel ?
>
> error Qt requires a C++11 compiler and yours does not seem to be that.
> a long list of errors and
>
> In file included from /usr/include/qt5/QtCore/qshareddata.h:46:0,
>                  from /usr/include/qt5/QtCore/qdatetime.h:45,
>                  from /usr/include/qt5/QtCore/QDateTime:1,
>                  from src/core/datetime.h:27,
>                  from defs.h:39,
>                  from main.cc:22:
> /usr/include/qt5/QtCore/qhash.h: Dans la fonction membre 'QPair<QHash<K,
> V>::iterator, QHash<K, V>::iterator> QHash<K, V>::equal_range(const Key&)':
> /usr/include/qt5/QtCore/qhash.h:957:5: attention : 'auto' changes meaning in
> C++11; please remove it [-Wc++0x-compat]
>      auto pair = qAsConst(*this).equal_range(akey);
>      ^
> /usr/include/qt5/QtCore/qhash.h:957:10: erreur: 'pair' does not name a type
>      auto pair = qAsConst(*this).equal_range(akey);
>           ^
> /usr/include/qt5/QtCore/qhash.h:958:31: erreur: 'pair' was not declared in
> this scope
>      return qMakePair(iterator(pair.first.i), iterator(pair.second.i));
>                                ^
> /usr/include/qt5/QtCore/qhash.h:958:31: note: suggested alternative:
> In file included from /usr/include/c++/5.3.0/utility:70:0,
>                  from /usr/include/qt5/QtCore/qcompilerdetection.h:1001,
>                  from /usr/include/qt5/QtCore/qglobal.h:83,
>                  from /usr/include/qt5/QtCore/qchar.h:43,
>                  from /usr/include/qt5/QtCore/qstring.h:48,
>                  from /usr/include/qt5/QtCore/qtextcodec.h:43,
>                  from /usr/include/qt5/QtCore/QTextCodec:1,
>                  from main.cc:20:
> /usr/include/c++/5.3.0/bits/stl_pair.h:96:12: note:   'std::pair'
>      struct pair
>             ^
> Makefile:128: recipe for target 'main.o' failed
> make: *** [main.o] Error 1

Looks like it's trying to build against Qt5.  I've only tested against Qt4.

Also there is a newer version, 1.5.4, but I've held back at 1.5.3
since 1.5.4 requires Qt5.  Can you try a simple version bump and see
if the errors go away with 1.5.4?

-Kyle

From dpross1100 at msn.com  Tue Jun 13 02:30:19 2017
From: dpross1100 at msn.com (Daniel Prosser)
Date: Tue, 13 Jun 2017 02:30:19 +0000
Subject: [Slackbuilds-users] gpsbabel, long list of errors
In-Reply-To: <CAJCpn82bvkWXhjtRaBbBND=0-TKKR8nxu-LMuOV5gt8tkudjhg@mail.gmail.com>
References: <20170612173045.cb1a27fd12e2b649a21926a4@clansco.org>
 <CAJCpn82bvkWXhjtRaBbBND=0-TKKR8nxu-LMuOV5gt8tkudjhg@mail.gmail.com>
Message-ID: <CO2PR0701MB7253CE1DC7865A645E70A55CCC20@CO2PR0701MB725.namprd07.prod.outlook.com>

I can confirm that the gpsbabel fails to build if you have Qt5
installed. Add this line in the SlackBuild, right before `autoreconf
-vif` to make sure it uses Qt4 instead:

sed -i 's/qmake-qt5 qmake-qt4 qmake/qmake qmake-qt4 qmake-qt5/g' configure.in

I have tested this and it works here.

Dan

On Mon, Jun 12, 2017 at 09:16:34PM -0500, Kyle Guinn wrote:
> On 6/12/17, Fr?d?ric Falsetti <falsetti at clansco.org> wrote:
> > Hi, anybody can build gpsbabel ?
> >
> > error Qt requires a C++11 compiler and yours does not seem to be that.
> > a long list of errors and
> >
> > In file included from /usr/include/qt5/QtCore/qshareddata.h:46:0,
> >                  from /usr/include/qt5/QtCore/qdatetime.h:45,
> >                  from /usr/include/qt5/QtCore/QDateTime:1,
> >                  from src/core/datetime.h:27,
> >                  from defs.h:39,
> >                  from main.cc:22:
> > /usr/include/qt5/QtCore/qhash.h: Dans la fonction membre 'QPair<QHash<K,
> > V>::iterator, QHash<K, V>::iterator> QHash<K, V>::equal_range(const Key&)':
> > /usr/include/qt5/QtCore/qhash.h:957:5: attention : 'auto' changes meaning in
> > C++11; please remove it [-Wc++0x-compat]
> >      auto pair = qAsConst(*this).equal_range(akey);
> >      ^
> > /usr/include/qt5/QtCore/qhash.h:957:10: erreur: 'pair' does not name a type
> >      auto pair = qAsConst(*this).equal_range(akey);
> >           ^
> > /usr/include/qt5/QtCore/qhash.h:958:31: erreur: 'pair' was not declared in
> > this scope
> >      return qMakePair(iterator(pair.first.i), iterator(pair.second.i));
> >                                ^
> > /usr/include/qt5/QtCore/qhash.h:958:31: note: suggested alternative:
> > In file included from /usr/include/c++/5.3.0/utility:70:0,
> >                  from /usr/include/qt5/QtCore/qcompilerdetection.h:1001,
> >                  from /usr/include/qt5/QtCore/qglobal.h:83,
> >                  from /usr/include/qt5/QtCore/qchar.h:43,
> >                  from /usr/include/qt5/QtCore/qstring.h:48,
> >                  from /usr/include/qt5/QtCore/qtextcodec.h:43,
> >                  from /usr/include/qt5/QtCore/QTextCodec:1,
> >                  from main.cc:20:
> > /usr/include/c++/5.3.0/bits/stl_pair.h:96:12: note:   'std::pair'
> >      struct pair
> >             ^
> > Makefile:128: recipe for target 'main.o' failed
> > make: *** [main.o] Error 1
> 
> Looks like it's trying to build against Qt5.  I've only tested against Qt4.
> 
> Also there is a newer version, 1.5.4, but I've held back at 1.5.3
> since 1.5.4 requires Qt5.  Can you try a simple version bump and see
> if the errors go away with 1.5.4?
> 
> -Kyle
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From rworkman at slackbuilds.org  Tue Jun 13 02:35:24 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 12 Jun 2017 21:35:24 -0500
Subject: [Slackbuilds-users] Another reboot - more details
Message-ID: <20170612213524.2f18a8c2@home.rlworkman.net>

Full disclosure on our frequent reboots here - we think we're
experiencing this bug, which is currently unsolved by upstream:

https://bugzilla.redhat.com/show_bug.cgi?id=1416043

Unfortunately, the only way to test potential fixes (or even
mitigations) involves restarting dbus, which really means
restarting the entire host system.

Bear with us. We've got another one coming soon, probably
within the hour. As usual, if all goes as planned, service
outage will be relatively brief.

-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/20170612/b85f1268/attachment.asc>

From rworkman at slackbuilds.org  Tue Jun 13 02:56:27 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 12 Jun 2017 21:56:27 -0500
Subject: [Slackbuilds-users] Another reboot - more details
In-Reply-To: <20170612213524.2f18a8c2@home.rlworkman.net>
References: <20170612213524.2f18a8c2@home.rlworkman.net>
Message-ID: <20170612215627.6b8e60ae@home.rlworkman.net>

On Mon, 12 Jun 2017 21:35:24 -0500
Robby Workman <rworkman at slackbuilds.org> wrote:

> Full disclosure on our frequent reboots here - we think we're
> experiencing this bug, which is currently unsolved by upstream:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1416043
> 
> Unfortunately, the only way to test potential fixes (or even
> mitigations) involves restarting dbus, which really means
> restarting the entire host system.
> 
> Bear with us. We've got another one coming soon, probably
> within the hour. As usual, if all goes as planned, service
> outage will be relatively brief.


We're back up - down for around three minutes isn't so bad, 
I suppose. 

I guess we'll know in a few days (or less) if the dbus change
is going to help.

-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/20170612/f689bd5d/attachment.asc>

From davidnchmelik at gmail.com  Tue Jun 13 05:56:46 2017
From: davidnchmelik at gmail.com (David Melik)
Date: Mon, 12 Jun 2017 22:56:46 -0700
Subject: [Slackbuilds-users] AQEMU?
In-Reply-To: <D22C06FE-47AC-46C5-9697-66954E1B6062@gmail.com>
References: <a9b2a161-10df-3e15-1952-03a9f37ab1e2@gmail.com>
 <D22C06FE-47AC-46C5-9697-66954E1B6062@gmail.com>
Message-ID: <8621c345-c801-0770-a568-73eadcde8c1c@gmail.com>

On 06/12/2017 09:32 AM, Edward Koenig wrote:
> 
> 
> 
> Sent from my iPad
>> On Jun 12, 2017, at 3:00 AM, David Melik <dchmelik-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
>>
>> I saw AQEMU released another version last year or so. Someone (Robby Workman?) abandoned the SlackBuild because of years of no releases before that, but now that they restarted, what about restarting the SlackBuild? I just reused the old one with version number update, and it works. AQEMU is a lot easier for me than all the other virtual machines, which seem to be more of a hassle to set up and use (too many options to choose, too many things to have to set up or install you don't need, etc.) QEMU just works.
>>
>> -- 
>> Sincerely,
>> David
>>
> 
> Looks promising.  I took used aqemu ages ago but stopped when upstream stalled (compile and emu support) .  I ended up just writing a shell script with zenity to avoid virt-manager.
> 
> My qemu-2.9.0 update is live now on SBo. Is that the version you're using?  I might give it a shot later this week.  Qemu development is pretty active so let's hope aqemu can keep up!

No; that may be the version they stopped at years ago. I'm using 2.9.2


From davidnchmelik at gmail.com  Tue Jun 13 06:35:08 2017
From: davidnchmelik at gmail.com (David Melik)
Date: Mon, 12 Jun 2017 23:35:08 -0700
Subject: [Slackbuilds-users] AQEMU?
In-Reply-To: <8621c345-c801-0770-a568-73eadcde8c1c@gmail.com>
References: <a9b2a161-10df-3e15-1952-03a9f37ab1e2@gmail.com>
 <D22C06FE-47AC-46C5-9697-66954E1B6062@gmail.com>
 <8621c345-c801-0770-a568-73eadcde8c1c@gmail.com>
Message-ID: <77c4f1bb-acaa-e0bb-1f14-1885d03b530d@gmail.com>

On 06/12/2017 10:56 PM, David Melik wrote:
> On 06/12/2017 09:32 AM, Edward Koenig wrote:
> > Looks promising.  I took used aqemu ages ago but stopped when upstream
>> stalled (compile and emu support) .  I ended up just writing a shell 
>> script with zenity to avoid virt-manager.
>>
>> My qemu-2.9.0 update is live now on SBo. Is that the version you're 
>> using?  I might give it a shot later this week.  Qemu development is 
>> pretty active so let's hope aqemu can keep up!
> 
> No; that may be the version they stopped at years ago. I'm using 2.9.2

To clarify/fix what I said above... you confused me. I'm talking about 
the AQEMU SlackBuild and am using AQEMU 0.9.2. Sure, I'm using it with 
QEMU 2.9.0, but that's not the main topic of my original post.

From rworkman at slackbuilds.org  Tue Jun 13 13:13:14 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 13 Jun 2017 08:13:14 -0500
Subject: [Slackbuilds-users] AQEMU?
In-Reply-To: <60b9d6fa-486f-54d3-0bee-9b9cb7643c00@gmail.com>
References: <a9b2a161-10df-3e15-1952-03a9f37ab1e2@gmail.com>
 <20170612142713.7f97d488@home.rlworkman.net>
 <60b9d6fa-486f-54d3-0bee-9b9cb7643c00@gmail.com>
Message-ID: <20170613081314.0e3bc1ea@home.rlworkman.net>

On Mon, 12 Jun 2017 12:43:54 -0700
King Beowulf <kingbeowulf at gmail.com> wrote:

> On 06/12/2017 12:27 PM, Robby Workman wrote:
> > On Mon, 12 Jun 2017 03:00:23 -0700
> > David Melik <dchmelik at gmail.com> wrote:
> >   
> >> I saw AQEMU released another version last year or so. Someone
> >> (Robby Workman?) abandoned the SlackBuild because of years of no
> >> releases before that, but now that they restarted, what about
> >> restarting the SlackBuild? I just reused the old one with version
> >> number update, and it works. AQEMU is a lot easier for me than all
> >> the other virtual machines, which seem to be more of a hassle to
> >> set up and use (too many options to choose, too many things to
> >> have to set up or install you don't need, etc.) QEMU just works.  
> > 
> > 
> > This new version requires qt5, but it shouldn't be problematic
> > otherwise. I'll look into bringing it back since upstream is
> > alive again.
>  
> 
> Robby,
> Since I have qemu, I was going to check "soon" (later today?) and
> maybe take it on.  I used aqemu ages ago (qemu 1.4?) and liked it -
> way simpler than wrestling with virt-manager/libvirt for features
> I'll never use.  I already have qt5 built/installed for another
> program.
> 
> However, if you are just dying to take on another task...far be it
> from me to stand in the way of your happiness ;-)


commit bbc934d01ba9c446ea00937e8dd2dd7235ac0b02
Author: Edward W. Koenig <kingbeowulf{at}gmail{dot}com>
Date:   Tue Jun 13 08:06:21 2017 -0500

    system/aqemu: Added (graphical interface to QEMU and KVM emulators)
    
    Signed-off-by: Robby Workman <rworkman at slackbuilds.org>


-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/20170613/2bd84d4e/attachment.asc>

From kingbeowulf at gmail.com  Tue Jun 13 19:11:21 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 13 Jun 2017 12:11:21 -0700
Subject: [Slackbuilds-users] AQEMU?
In-Reply-To: <77c4f1bb-acaa-e0bb-1f14-1885d03b530d@gmail.com>
References: <a9b2a161-10df-3e15-1952-03a9f37ab1e2@gmail.com>
 <D22C06FE-47AC-46C5-9697-66954E1B6062@gmail.com>
 <8621c345-c801-0770-a568-73eadcde8c1c@gmail.com>
 <77c4f1bb-acaa-e0bb-1f14-1885d03b530d@gmail.com>
Message-ID: <1358fb10-01b6-01c8-769f-48abea75c323@gmail.com>

On 06/12/2017 11:35 PM, David Melik wrote:
> On 06/12/2017 10:56 PM, David Melik wrote:
>> On 06/12/2017 09:32 AM, Edward Koenig wrote:
>> > Looks promising.  I took used aqemu ages ago but stopped when upstream
>>> stalled (compile and emu support) .  I ended up just writing a shell
>>> script with zenity to avoid virt-manager.
>>>
>>> My qemu-2.9.0 update is live now on SBo. Is that the version you're
>>> using?  I might give it a shot later this week.  Qemu development is
>>> pretty active so let's hope aqemu can keep up!
>>
>> No; that may be the version they stopped at years ago. I'm using 2.9.2
> 
> To clarify/fix what I said above... you confused me. I'm talking about
> the AQEMU SlackBuild and am using AQEMU 0.9.2. Sure, I'm using it with
> QEMU 2.9.0, but that's not the main topic of my original post.

Got it.  Of course, you can't really talk about aqemu without talking
about qemu as it is just a front end.  The reason aqemu was dropped was
when qemu added features and changed command line options, aqemu failed.

Since qemu is now 2.8/2.9 series and was 2.6/2.7 when aqemu-0.9.2 was
released, we need to do a bit more testing for SBo. I don't mind - I
liked aqemu back when and was sad when it went dormant.

-Ed




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

From thedoogster at gmail.com  Tue Jun 13 21:40:35 2017
From: thedoogster at gmail.com (Doogster)
Date: Tue, 13 Jun 2017 14:40:35 -0700
Subject: [Slackbuilds-users] How do I put stuff on sbodirectlinks
Message-ID: <CAE5oDaYSk950bzpFz5b=MOFVwRhL+coWtEKfbdzsc8kzZF4emA@mail.gmail.com>

I have a couple of source tarballs that I'd like to use sbodirectlinks
to host. How do I do that?

From willysr at slackbuilds.org  Wed Jun 14 01:21:30 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 14 Jun 2017 08:21:30 +0700
Subject: [Slackbuilds-users] How do I put stuff on sbodirectlinks
In-Reply-To: <CAE5oDaYSk950bzpFz5b=MOFVwRhL+coWtEKfbdzsc8kzZF4emA@mail.gmail.com>
References: <CAE5oDaYSk950bzpFz5b=MOFVwRhL+coWtEKfbdzsc8kzZF4emA@mail.gmail.com>
Message-ID: <f7c01e4d-9ea2-f171-458a-fa362d9774e0@slackbuilds.org>

> I have a couple of source tarballs that I'd like to use sbodirectlinks
> to host. How do I do that?

Send me your SF username and i can grant you a developer access so you
can put the tarballs there

-- 
Willy Sudiarto Raharjo

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

From dchmelik at gmail.com  Wed Jun 14 08:58:23 2017
From: dchmelik at gmail.com (David Melik)
Date: Wed, 14 Jun 2017 01:58:23 -0700
Subject: [Slackbuilds-users] Chromium SlackBuild?
Message-ID: <0c51f3f2-c8f6-4127-d015-07f248666ecc@gmail.com>

     SlackBuild.org's (SBo) Chromium SlackBuild hasn't been updated 
almost a year--about 10 major versions behind, thousands of minor 
versions.  The current SBo version has critical problems for users, 
including major security risks, and many/most major sites don't load 
properly so are unusable (something like Google stopped accepting some 
certificates.)  Even alienBOB's (who deals with hundreds of packages, so 
not always updated fast) SlackBuild is much newer. That's what I'm using 
now but hoping Chromium will be updated in SBo. If someone else has to 
maintain it, I can't be the person to do so (too complicated build for me.)

-- 
Sincerely,
David
http://davidchmelik.com/ (homesite, updated first)
http://www.cwu.edu/~melikd/ (most stable homepage)


From kingbeowulf at gmail.com  Wed Jun 14 19:02:35 2017
From: kingbeowulf at gmail.com (King Beowulf)
Date: Wed, 14 Jun 2017 12:02:35 -0700
Subject: [Slackbuilds-users] flite-2.0.0: patch to fix LDFLAGS issue
Message-ID: <f310f623-d81c-0363-249a-0342bb412fef@gmail.com>

Hello
Some external speech programs, such as speech-dispatcher, can't find
libflite.so.  Attached is a patch, and modified flite.slackbuild diff
from current master, adapted from Arch, to fix that problem.

------------------8<-------------------------
diff --git a/accessibility/flite/flite.SlackBuild
b/accessibility/flite/flite.SlackBuild
old mode 100644
new mode 100755
index 4e0248f..3deba93
--- a/accessibility/flite/flite.SlackBuild
+++ b/accessibility/flite/flite.SlackBuild
@@ -27,7 +27,7 @@

 PRGNAM=flite
 VERSION=${VERSION:-2.0.0}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2}
 TAG=${TAG:-_SBo}

 if [ -z "$ARCH" ]; then
@@ -72,6 +72,9 @@ 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 {} \;

+# fix LDLAGS to allow external programs to find libflite.so
+patch -p1 < $CWD/flite-ldflags-fix.patch
+
 CFLAGS="$SLKCFLAGS" \
 CXXFLAGS="$SLKCFLAGS" \
------------------>8-------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: flite-ldflags-fix.patch
Type: text/x-patch
Size: 1913 bytes
Desc: not available
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170614/b277cea4/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170614/b277cea4/attachment.asc>

From willysr at slackbuilds.org  Thu Jun 15 11:54:35 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 15 Jun 2017 18:54:35 +0700
Subject: [Slackbuilds-users] Updates - 20170615.1
Message-ID: <5330f2a0-cdca-2427-b9b8-66d9ba3f7054@slackbuilds.org>

Sorry for the unscheduled updates but we have several update that
contains security fixes on this batch and we think it's important to
have them delivered to you as soon as possible, thus this update is
pushed ahead of my weekend schedule. Some sources were missing and
Matteo (ponce) managed to fixed them as well.

Thu Jun 15 11:37:22 UTC 2017
accessibility/flite: Fix linking with libflite.so.
accessibility/speech-dispatcher: Updated for version 0.8.7.
audio/drumkv1: Updated for version 0.8.2, drop qt5 dep.
audio/fmit: Fixed download link.
audio/mhwaveedit: Fixed download link.
audio/ngjackspa: Fixed download link.
audio/samplv1: Updated for version 0.8.2, drop qt5 dep.
audio/synthv1: Updated for version 0.8.2, drop qt5 dep.
desktop/gtk-theme-Greybird: Updated for version 3.22.4.
desktop/ideviceinstaller: Updated for version 1.1.0.
desktop/numix-icon-theme: Updated for version 0.3.898.201705182217.
desktop/searchmonkey: Updated for version 2.0.0.
desktop/tint2: Updated for version 0.14.6.
development/binwalk: Added (Firmware Analysis Tool).
development/cargo: Updated for version 0.19.0.
development/dpkg: Updated for version 1.18.24.
development/gputils: Updated for version 1.5.0.
development/hhvm: Updated for version 3.20.2.
development/mkchroot: Updated for version 1.3.
development/nodejs: Updated for version 6.11.0.
development/rust: Updated for version 1.18.0.
development/stgit: Fixed download link.
development/universal-ctags: Updated for version 1bcb1fc.
games/advancemame: Updated for version 3.5.
games/bastet: Updated for version 0.43.2.
games/freeciv: Updated for version 2.5.7.
games/gzdoom-legacy: Added (OpenGL port of DOOM).
games/gzdoom: Updated for version 3.1.0.
games/hedgewars: Fixed download link.
games/roccat-tools: Remove text.
games/tome-sx: Added (fantasy adventure game).
games/warmux: Fixed download link.
gis/openorienteering-mapper: Updated for version 0.7.0.
libraries/cal3d: Fixed download link.
libraries/leptonica: Updated for version 1.74.4.
libraries/libinput: Updated for version 1.7.3.
libraries/libreadline-java: Build with getline & optional editline.
libraries/libvirt: Added soft_restart() to rc.libvirt
libraries/libvirt: Fix VIRTGROUP in default polkit rules
libraries/msgpack-c: Updated for version 2.1.2.
libraries/mygpoclient: Fixed homepage and download link.
libraries/wjelement: Updated for version 1.3.
libraries/wxSQLite3: Updated for version 3.5.5.
misc/nfoview: Fixed download link.
multimedia/QMPlay2: Updated for version 17.06.09.
multimedia/a2jmidid: Fixed download link.
multimedia/flashplayer-plugin: Updated for version 26.0.0.126.
multimedia/gaupol: Fixed download link.
multimedia/gmidimonitor: Fixed download link.
multimedia/mpv: Use waf version 1.9.8 supported by upstream.
multimedia/pepperflash-plugin: Updated for version 26.0.0.126.
multimedia/subtitleeditor: Fixed download link.
multimedia/youtube-viewer: Updated for version 3.2.8.
network/dovecot-pigeonhole: Updated for version 0.4.18.
network/filezilla: Updated for version 3.26.2.
network/nagios: Updated for version 4.3.2.
network/oidentd: Updated for version 2.1.0.
network/opera: Updated for version 45.0.2552.898.
network/qTox: Updated for version 1.10.2.
network/smcroute: Updated for version 2.3.0.
network/ssllabs-scan: Fixed source filename.
network/tor-browser: Updated for version 7.0.1.
network/tor: Updated for version 0.3.0.8.
office/MasterPDFEditor: Updated for version 4.2.12.
office/hebcal: Added (perpetual Jewish calendar).
office/kbibtex: Fixed download link.
perl/perl-IO-Socket-SSL: Updated for version 2.049.
python/git-fame: Added (Pretty-print git repository collaborators).
python/netifaces: Fix README.
python/pychart: Fixed download link.
python/pypy3: Updated for version 5.8_beta.
python/pypy: Updated for version 5.8.
python/python-cached-property: Added (caching properties decorator).
python/python-docker-pycreds: Added (docker credentials bindings).
python/python-docker: Added (Python library for Docker Engine API).
python/python-dockerpty: Added (pseudo-tty of docker container).
python/python-libsass: Updated for version 0.13.1.
python/python-requests: Updated for version 2.17.3.
python/python-texttable: Added (create simple ASCII tables).
system/apachetop: Updated for version 0.17.4.
system/aqemu: Added (graphical interface to QEMU and KVM emulators)
system/asbt: Updated for version 1.9.1.
system/ddrescue-gui: Updated for version 1.7.1.
system/docker-compose: Added (docker multi-container orchestration).
system/docker-machine: Updated for version 0.12.0.
system/docker: Misc README and slack-desc changes.
system/firejail: Updated for version 0.9.48.
system/font-manager: Added (GTK+ font manager).
system/geoclue2: Added (location information service).
system/gitolite: Updated for version 3.6.6.
system/inxi: Updated for version 2.3.20.
system/isomd5sum: Updated for version 1.2.1.
system/letsencrypt: Updated for version 0.15.0.
system/lynis: Updated for version 2.5.1.
system/monit: Updated for version 5.23.0.
system/monitoring-plugins: Updated for version 2.2.
system/nagios-plugins: Updated for version 2.2.1.
system/openrc: Updated for version 0.27.2.
system/rar2fs: Updated for version 1.24.1.
system/smbldap-tools: Fixed download link.
system/sqlcipher: Updated for version 3.4.1.
system/wine-staging: Updated for version 2.10.
+--------------------------+


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170615/e29d7f97/attachment.asc>

From willysr at slackbuilds.org  Thu Jun 15 13:19:17 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 15 Jun 2017 20:19:17 +0700
Subject: [Slackbuilds-users] letsencrypt users
Message-ID: <ffbed86d-2843-075d-a997-b2f3e12e13a0@slackbuilds.org>

Just to give you some heads-up for letsencrypt users

Due to python-requests bump to 2.17.3, certifi is now a mandatory
requirement for letsencrypt otherwise, it will complaint with these errors

Traceback (most recent call last):
  File "/usr/bin/letsencrypt", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 2927, in <module>
    @_call_aside
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 2913, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 2940, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 635, in _build_master
    ws.require(__requires__)
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 943, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
line 829, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'certifi>=2017.4.17'
distribution was not found and is required by requests


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170615/10736b64/attachment.asc>

From willysr at slackbuilds.org  Thu Jun 15 13:55:37 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 15 Jun 2017 20:55:37 +0700
Subject: [Slackbuilds-users] letsencrypt users
In-Reply-To: <ffbed86d-2843-075d-a997-b2f3e12e13a0@slackbuilds.org>
References: <ffbed86d-2843-075d-a997-b2f3e12e13a0@slackbuilds.org>
Message-ID: <793cc36d-7301-a8be-f106-6da88a9b2bbb@slackbuilds.org>

> Just to give you some heads-up for letsencrypt users
> 
> Due to python-requests bump to 2.17.3, certifi is now a mandatory
> requirement for letsencrypt otherwise, it will complaint with these errors
> 
> Traceback (most recent call last):
>   File "/usr/bin/letsencrypt", line 5, in <module>
>     from pkg_resources import load_entry_point
>   File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 2927, in <module>
>     @_call_aside
>   File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 2913, in _call_aside
>     f(*args, **kwargs)
>   File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 2940, in _initialize_master_working_set
>     working_set = WorkingSet._build_master()
>   File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 635, in _build_master
>     ws.require(__requires__)
>   File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 943, in require
>     needed = self.resolve(parse_requirements(requirements))
>   File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py",
> line 829, in resolve
>     raise DistributionNotFound(req, requirers)
> pkg_resources.DistributionNotFound: The 'certifi>=2017.4.17'
> distribution was not found and is required by requests

after further testing, it requires more than python-certifi
here's what i need to do in order for LE to work again
- python-certifi (new dep)
- python-chardet-3.0.4 (new dep and bump new version)
- idna-2.5 (bump new version)
- python-urllib3-1.21.1 (bump new version)

maintainers, can we bump those three scripts that belongs to you?

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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170615/9f00fbbe/attachment.asc>

From audrius at neutrino.lt  Thu Jun 15 15:40:27 2017
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Thu, 15 Jun 2017 18:40:27 +0300
Subject: [Slackbuilds-users] letsencrypt users
In-Reply-To: <793cc36d-7301-a8be-f106-6da88a9b2bbb@slackbuilds.org>
References: <ffbed86d-2843-075d-a997-b2f3e12e13a0@slackbuilds.org>
 <793cc36d-7301-a8be-f106-6da88a9b2bbb@slackbuilds.org>
Message-ID: <20170615154027.GA2406@varna>

On Thu, 2017-06-15 at 20:55:37 +0700, Willy Sudiarto Raharjo wrote:
> after further testing, it requires more than python-certifi
> here's what i need to do in order for LE to work again
> - python-certifi (new dep)
> - python-chardet-3.0.4 (new dep and bump new version)
> - idna-2.5 (bump new version)
> - python-urllib3-1.21.1 (bump new version)
> 
> maintainers, can we bump those three scripts that belongs to you?

Willy, these four are actually direct dependencies of python-requests,
as can be seen in its setup.py.  You should add them to python-requests
REQUIRES instead of letsencrypt.

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170615/c3207f7d/attachment-0001.asc>

From willysr at slackbuilds.org  Thu Jun 15 15:45:25 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 15 Jun 2017 22:45:25 +0700
Subject: [Slackbuilds-users] letsencrypt users
In-Reply-To: <20170615154027.GA2406@varna>
References: <ffbed86d-2843-075d-a997-b2f3e12e13a0@slackbuilds.org>
 <793cc36d-7301-a8be-f106-6da88a9b2bbb@slackbuilds.org>
 <20170615154027.GA2406@varna>
Message-ID: <ebf8ef68-cb70-1958-dcc8-dcd3b8e5ad8f@slackbuilds.org>

> Willy, these four are actually direct dependencies of python-requests,
> as can be seen in its setup.py.  You should add them to python-requests
> REQUIRES instead of letsencrypt.

Audrius
Thanks for spotting that. It build fine without it, so we never notice
it. I will add them to python-requests.


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170615/a70ab152/attachment.asc>

From audrius at neutrino.lt  Thu Jun 15 16:16:04 2017
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Thu, 15 Jun 2017 19:16:04 +0300
Subject: [Slackbuilds-users] letsencrypt users
In-Reply-To: <ebf8ef68-cb70-1958-dcc8-dcd3b8e5ad8f@slackbuilds.org>
References: <ffbed86d-2843-075d-a997-b2f3e12e13a0@slackbuilds.org>
 <793cc36d-7301-a8be-f106-6da88a9b2bbb@slackbuilds.org>
 <20170615154027.GA2406@varna>
 <ebf8ef68-cb70-1958-dcc8-dcd3b8e5ad8f@slackbuilds.org>
Message-ID: <20170615161604.GB2406@varna>

On Thu, 2017-06-15 at 22:45:25 +0700, Willy Sudiarto Raharjo wrote:
> Audrius
> Thanks for spotting that. It build fine without it, so we never notice
> it. I will add them to python-requests.

One small note: your changes to python/idna mangled years on copyright
line, probably the result of '2.1' regexp where dot here matches any
character (should have been '2\.1' instead).

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170615/fb45a7b2/attachment.asc>

From willysr at slackbuilds.org  Thu Jun 15 16:17:49 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 15 Jun 2017 23:17:49 +0700
Subject: [Slackbuilds-users] letsencrypt users
In-Reply-To: <20170615161604.GB2406@varna>
References: <ffbed86d-2843-075d-a997-b2f3e12e13a0@slackbuilds.org>
 <793cc36d-7301-a8be-f106-6da88a9b2bbb@slackbuilds.org>
 <20170615154027.GA2406@varna>
 <ebf8ef68-cb70-1958-dcc8-dcd3b8e5ad8f@slackbuilds.org>
 <20170615161604.GB2406@varna>
Message-ID: <7f953287-05e8-1d37-2d91-4eaae1a18c8c@slackbuilds.org>

> One small note: your changes to python/idna mangled years on copyright
> line, probably the result of '2.1' regexp where dot here matches any
> character (should have been '2\.1' instead).

Fixed
Thanks again


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170615/fa2288f1/attachment.asc>

From atelszewski at gmail.com  Thu Jun 15 18:00:09 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 15 Jun 2017 20:00:09 +0200
Subject: [Slackbuilds-users] Building rust with LOCAL_BOOTSTRAP=yes fails
Message-ID: <9fa661c2-890f-0111-d491-e6e6a1f581a1@gmail.com>

Hi,

I'm trying to build rust 1.18.0 with LOCAL_BOOTSTRAP=yes, but the build 
fails with error [1].

I have both previous versions of rust-1.17.0 and cargo-0.18.0 installed 
before building.

Help appreciated :-)


_The contents of config.toml is:_
$ cat config.toml
[build]
vendor = true
rustc = "/usr/bin/rustc"
cargo = "/usr/bin/cargo"
extended = false
submodules = false

[install]
prefix = "/tmp/slackrepo-desktop/package-rust/usr"
libdir = "lib64"
mandir = "man"

[rust]
channel = "stable"
rpath = false
codegen-tests = false

[target.x86_64-unknown-linux-gnu]
llvm-config = "/usr/bin/llvm-config"
# build fails using the system jemalloc
# jemalloc = "/usr/lib64/libjemalloc_pic.a"


_[1] The error message is:_
    Compiling getopts v0.2.14
    Compiling libc v0.2.21
    Compiling gcc v0.3.45
    Compiling rustc-serialize v0.3.23
    Compiling num_cpus v0.2.13
    Compiling filetime v0.1.10
    Compiling cmake v0.1.22
    Compiling build_helper v0.1.0 
(file:///tmp/slackrepo-desktop/rustc-1.18.0-src/src/build_helper)
    Compiling toml v0.1.30
    Compiling bootstrap v0.0.0 
(file:///tmp/slackrepo-desktop/rustc-1.18.0-src/src/bootstrap)
     Finished dev [unoptimized] target(s) in 21.79 secs


failed to execute command: 
"/tmp/slackrepo-desktop/rustc-1.18.0-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" 
"metadata" "--manifest-path" 
"/tmp/slackrepo-desktop/rustc-1.18.0-src/src/libstd/Cargo.toml"
error: No such file or directory (os error 2)

-- 
Best regards,
Andrzej Telszewski

From audrius at neutrino.lt  Thu Jun 15 19:19:41 2017
From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=)
Date: Thu, 15 Jun 2017 22:19:41 +0300
Subject: [Slackbuilds-users] letsencrypt users
In-Reply-To: <ebf8ef68-cb70-1958-dcc8-dcd3b8e5ad8f@slackbuilds.org>
References: <ffbed86d-2843-075d-a997-b2f3e12e13a0@slackbuilds.org>
 <793cc36d-7301-a8be-f106-6da88a9b2bbb@slackbuilds.org>
 <20170615154027.GA2406@varna>
 <ebf8ef68-cb70-1958-dcc8-dcd3b8e5ad8f@slackbuilds.org>
Message-ID: <20170615191941.GA7009@varna>

On Thu, 2017-06-15 at 22:45:25 +0700, Willy Sudiarto Raharjo wrote:
> Audrius
> Thanks for spotting that. It build fine without it, so we never notice
> it. I will add them to python-requests.

I searched for scripts that require both python-requests and one of its
four new dependencies.  Found these:

(have python-certifi)
development/jupyter-nbdime
multimedia/Mopidy
system/salt

(have python-urllib3)
libraries/dropbox-python
network/deis
system/virt-manager

My understanding is that admins prefer that maintainers only list first
level dependencies, so both python-certifi and python-urllib3 can be
dropped from all the listed packages REQUIRES, since these requirements
are now satisfied by python-requests.

-- 
Audrius Ka?ukauskas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170615/36d060a9/attachment.asc>

From slackbuilds at jaxartes.net  Thu Jun 15 21:50:37 2017
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Thu, 15 Jun 2017 14:50:37 -0700
Subject: [Slackbuilds-users] letsencrypt users
In-Reply-To: <20170615191941.GA7009@varna>
References: <ffbed86d-2843-075d-a997-b2f3e12e13a0@slackbuilds.org>
 <ebf8ef68-cb70-1958-dcc8-dcd3b8e5ad8f@slackbuilds.org>
 <20170615191941.GA7009@varna>
Message-ID: <1833997.xWclvcNvL5@wintermute>

On Thursday, June 15, 2017 12:19:41 PM PDT Audrius Ka?ukauskas wrote:
> On Thu, 2017-06-15 at 22:45:25 +0700, Willy Sudiarto Raharjo wrote:
> > Audrius
> > Thanks for spotting that. It build fine without it, so we never notice
> > it. I will add them to python-requests.
> 
> I searched for scripts that require both python-requests and one of its
> four new dependencies.  Found these:
> 
> (have python-certifi)
> development/jupyter-nbdime

Thanks. Just updated nbdime to reflect the change to python-requests.

From baildon.research at googlemail.com  Thu Jun 15 22:56:47 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 15 Jun 2017 23:56:47 +0100
Subject: [Slackbuilds-users] Building rust with LOCAL_BOOTSTRAP=yes fails
In-Reply-To: <9fa661c2-890f-0111-d491-e6e6a1f581a1@gmail.com>
References: <9fa661c2-890f-0111-d491-e6e6a1f581a1@gmail.com>
Message-ID: <CAMt7G9ToMFfBcWeoo3KHr9SoMC+EqAz97MOcrBhPyci-PSMW5g@mail.gmail.com>

> I'm trying to build rust 1.18.0 with LOCAL_BOOTSTRAP=yes, but the build
> fails with error [1].
>
> I have both previous versions of rust-1.17.0 and cargo-0.18.0 installed
> before building.

Reproduced both in slackrepo and sbopkg

https://github.com/rust-lang/rust/issues/42543
1.18 doesn't build with 1.17 #42543
Open
kyrias opened this Issue 7 days ago ? 3 comments

Cheers
-D.

From aclemons at runbox.no  Thu Jun 15 23:03:44 2017
From: aclemons at runbox.no (Andrew Clemons)
Date: Fri, 16 Jun 2017 11:03:44 +1200
Subject: [Slackbuilds-users] Building rust with LOCAL_BOOTSTRAP=yes fails
In-Reply-To: <9fa661c2-890f-0111-d491-e6e6a1f581a1@gmail.com>
References: <9fa661c2-890f-0111-d491-e6e6a1f581a1@gmail.com>
Message-ID: <20170615230343.GA28436@runbox.no>

On 2017-06-15 20:00:09 +0200, atelszewski at gmail.com wrote:
> Hi,
> 
> I'm trying to build rust 1.18.0 with LOCAL_BOOTSTRAP=yes, but the build
> fails with error [1].
> 
> I have both previous versions of rust-1.17.0 and cargo-0.18.0 installed
> before building.
> 
> Help appreciated :-)
> 
> [...]

I can reproduce. For me, removing `--verbose` in the call to `x.py
build` allows the build to complete. If that also works for you, I'll
submit an update which this change, although it's not clear to me from
a cursory read of the source why this should cause it to use the wrong
path to cargo.

Thanks,
Andrew

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

From baildon.research at googlemail.com  Thu Jun 15 23:14:50 2017
From: baildon.research at googlemail.com (David Spencer)
Date: Fri, 16 Jun 2017 00:14:50 +0100
Subject: [Slackbuilds-users] Building rust with LOCAL_BOOTSTRAP=yes fails
In-Reply-To: <20170615230343.GA28436@runbox.no>
References: <9fa661c2-890f-0111-d491-e6e6a1f581a1@gmail.com>
 <20170615230343.GA28436@runbox.no>
Message-ID: <CAMt7G9SBKB2YtVMcs1pVJMsHF3u0fWypo32eD9A-L9dLr7Y0BQ@mail.gmail.com>

> I can reproduce. For me, removing `--verbose` in the call to `x.py
> build` allows the build to complete. If that also works for you, I'll
> submit an update which this change, although it's not clear to me from
> a cursory read of the source why this should cause it to use the wrong
> path to cargo.

Fixes it here \o/

You might want to ping upstream ;-)

Thanks
-D.

From atelszewski at gmail.com  Thu Jun 15 23:24:59 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Fri, 16 Jun 2017 01:24:59 +0200
Subject: [Slackbuilds-users] Building rust with LOCAL_BOOTSTRAP=yes fails
In-Reply-To: <20170615230343.GA28436@runbox.no>
References: <9fa661c2-890f-0111-d491-e6e6a1f581a1@gmail.com>
 <20170615230343.GA28436@runbox.no>
Message-ID: <54e72e36-c881-73d6-2174-60e9235f94f5@gmail.com>

On 16/06/17 01:03, Andrew Clemons wrote:
> I can reproduce. For me, removing `--verbose` in the call to `x.py
> build` allows the build to complete. If that also works for you, I'll
> submit an update which this change, although it's not clear to me from
> a cursory read of the source why this should cause it to use the wrong
> path to cargo.
> 
> Thanks,
> Andrew

I just managed to build with the following change:

diff --git a/development/rust/rust.SlackBuild 
b/development/rust/rust.SlackBuild
index 013687e..06a510f 100644
--- a/development/rust/rust.SlackBuild
+++ b/development/rust/rust.SlackBuild
@@ -108,6 +108,8 @@ EOF

  if [ "$LOCAL_BOOTSTRAP" = "yes" ] ; then
    sed -i "s|^\(vendor = true\)$|\1\nrustc = \"/usr/bin/rustc\"\ncargo 
= \"/usr/bin/cargo\"|" config.toml
+  mkdir -p build/x86_64-unknown-linux-gnu/stage0/bin
+  (cd build/x86_64-unknown-linux-gnu/stage0/bin && ln -s /usr/bin/cargo )
  fi

  chown -R root:root .


But I have no idea it that's correct solution ;-)


-- 
Best regards,
Andrzej Telszewski

From aclemons at runbox.no  Thu Jun 15 23:34:00 2017
From: aclemons at runbox.no (Andrew Clemons)
Date: Fri, 16 Jun 2017 11:34:00 +1200
Subject: [Slackbuilds-users] Building rust with LOCAL_BOOTSTRAP=yes fails
In-Reply-To: <CAMt7G9SBKB2YtVMcs1pVJMsHF3u0fWypo32eD9A-L9dLr7Y0BQ@mail.gmail.com>
References: <9fa661c2-890f-0111-d491-e6e6a1f581a1@gmail.com>
 <20170615230343.GA28436@runbox.no>
 <CAMt7G9SBKB2YtVMcs1pVJMsHF3u0fWypo32eD9A-L9dLr7Y0BQ@mail.gmail.com>
Message-ID: <20170615233359.GB28436@runbox.no>

On 2017-06-16 00:14:50 +0100, baildon.research at googlemail.com wrote:
> [...]
> You might want to ping upstream ;-)

Done. Thanks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170616/260a29c1/attachment.asc>

From willysr at slackbuilds.org  Fri Jun 16 00:09:03 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 16 Jun 2017 07:09:03 +0700
Subject: [Slackbuilds-users] letsencrypt users
In-Reply-To: <20170615191941.GA7009@varna>
References: <ffbed86d-2843-075d-a997-b2f3e12e13a0@slackbuilds.org>
 <793cc36d-7301-a8be-f106-6da88a9b2bbb@slackbuilds.org>
 <20170615154027.GA2406@varna>
 <ebf8ef68-cb70-1958-dcc8-dcd3b8e5ad8f@slackbuilds.org>
 <20170615191941.GA7009@varna>
Message-ID: <6e7bd059-8057-775c-026f-43a9fca7c18d@slackbuilds.org>

> I searched for scripts that require both python-requests and one of its
> four new dependencies.  Found these:
> 
> (have python-certifi)
> development/jupyter-nbdime
> multimedia/Mopidy
> system/salt
> 
> (have python-urllib3)
> libraries/dropbox-python
> network/deis
> system/virt-manager
> 
> My understanding is that admins prefer that maintainers only list first
> level dependencies, so both python-certifi and python-urllib3 can be
> dropped from all the listed packages REQUIRES, since these requirements
> are now satisfied by python-requests.

Done updating all above (except for jupyter-nbdime which is updated by
Benjamin already)

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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170616/a6023a54/attachment.asc>

From willysr at slackbuilds.org  Fri Jun 16 00:16:33 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 16 Jun 2017 07:16:33 +0700
Subject: [Slackbuilds-users] Building rust with LOCAL_BOOTSTRAP=yes fails
In-Reply-To: <20170615233359.GB28436@runbox.no>
References: <9fa661c2-890f-0111-d491-e6e6a1f581a1@gmail.com>
 <20170615230343.GA28436@runbox.no>
 <CAMt7G9SBKB2YtVMcs1pVJMsHF3u0fWypo32eD9A-L9dLr7Y0BQ@mail.gmail.com>
 <20170615233359.GB28436@runbox.no>
Message-ID: <a8248f61-a1ce-a18c-9d6f-06d428c45716@slackbuilds.org>

>> You might want to ping upstream ;-)
> 
> Done. Thanks

Love it when our community contribute back to upstream :)


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170616/d9dfba3a/attachment.asc>

From willysr at slackbuilds.org  Fri Jun 16 00:44:06 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 16 Jun 2017 07:44:06 +0700
Subject: [Slackbuilds-users] gpsbabel, long list of errors
In-Reply-To: <CO2PR0701MB7253CE1DC7865A645E70A55CCC20@CO2PR0701MB725.namprd07.prod.outlook.com>
References: <20170612173045.cb1a27fd12e2b649a21926a4@clansco.org>
 <CAJCpn82bvkWXhjtRaBbBND=0-TKKR8nxu-LMuOV5gt8tkudjhg@mail.gmail.com>
 <CO2PR0701MB7253CE1DC7865A645E70A55CCC20@CO2PR0701MB725.namprd07.prod.outlook.com>
Message-ID: <e2266fd5-0211-7a0a-8362-b4601c1b20c4@slackbuilds.org>

>> Looks like it's trying to build against Qt5.  I've only tested against Qt4.
>>
>> Also there is a newer version, 1.5.4, but I've held back at 1.5.3
>> since 1.5.4 requires Qt5.  Can you try a simple version bump and see
>> if the errors go away with 1.5.4?

It seems the transition to qt5 is inevitable. Simply holding back to
1.5.3 means it's one year behind and definitely inability to work
properly with new devices and the lack of GeoJSON write support


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170616/d3324e9e/attachment.asc>

From elyk03 at gmail.com  Fri Jun 16 01:51:30 2017
From: elyk03 at gmail.com (Kyle Guinn)
Date: Thu, 15 Jun 2017 20:51:30 -0500
Subject: [Slackbuilds-users] gpsbabel, long list of errors
In-Reply-To: <e2266fd5-0211-7a0a-8362-b4601c1b20c4@slackbuilds.org>
References: <20170612173045.cb1a27fd12e2b649a21926a4@clansco.org>
 <CAJCpn82bvkWXhjtRaBbBND=0-TKKR8nxu-LMuOV5gt8tkudjhg@mail.gmail.com>
 <CO2PR0701MB7253CE1DC7865A645E70A55CCC20@CO2PR0701MB725.namprd07.prod.outlook.com>
 <e2266fd5-0211-7a0a-8362-b4601c1b20c4@slackbuilds.org>
Message-ID: <CAJCpn836wG22OBN0YWmZAYO7qjm1Vm8snPzZNwvGQCHPrDYQRw@mail.gmail.com>

On 6/15/17, Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:
>>> Looks like it's trying to build against Qt5.  I've only tested against
>>> Qt4.
>>>
>>> Also there is a newer version, 1.5.4, but I've held back at 1.5.3
>>> since 1.5.4 requires Qt5.  Can you try a simple version bump and see
>>> if the errors go away with 1.5.4?
>
> It seems the transition to qt5 is inevitable. Simply holding back to
> 1.5.3 means it's one year behind and definitely inability to work
> properly with new devices and the lack of GeoJSON write support

Good point.  I'm putting together an update to 1.5.4, and I'll leave a
note in the README for those who would rather not build Qt5.

Related question:  If I want to move this to the gis category, can I
do it from git, or should I submit using the form on the website?  I'm
not sure if there's any magic you need to do on your side for a
category move.

-Kyle

From willysr at slackbuilds.org  Fri Jun 16 03:21:47 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 16 Jun 2017 10:21:47 +0700
Subject: [Slackbuilds-users] gpsbabel, long list of errors
In-Reply-To: <CAJCpn836wG22OBN0YWmZAYO7qjm1Vm8snPzZNwvGQCHPrDYQRw@mail.gmail.com>
References: <20170612173045.cb1a27fd12e2b649a21926a4@clansco.org>
 <CAJCpn82bvkWXhjtRaBbBND=0-TKKR8nxu-LMuOV5gt8tkudjhg@mail.gmail.com>
 <CO2PR0701MB7253CE1DC7865A645E70A55CCC20@CO2PR0701MB725.namprd07.prod.outlook.com>
 <e2266fd5-0211-7a0a-8362-b4601c1b20c4@slackbuilds.org>
 <CAJCpn836wG22OBN0YWmZAYO7qjm1Vm8snPzZNwvGQCHPrDYQRw@mail.gmail.com>
Message-ID: <19cb59f5-6fe0-d5f4-9ade-4f9cb1df23a8@slackbuilds.org>

>> It seems the transition to qt5 is inevitable. Simply holding back to
>> 1.5.3 means it's one year behind and definitely inability to work
>> properly with new devices and the lack of GeoJSON write support
> 
> Good point.  I'm putting together an update to 1.5.4, and I'll leave a
> note in the README for those who would rather not build Qt5.
> 
> Related question:  If I want to move this to the gis category, can I
> do it from git, or should I submit using the form on the website?  I'm
> not sure if there's any magic you need to do on your side for a
> category move.

Yes, you can do it via git mv but remember to put it on the commit
message so that one of the admin notice that when we run the public
update because some post-actions must be executed in the backend as well.


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170616/0cdd937e/attachment-0001.asc>

From willysr at slackbuilds.org  Sat Jun 17 00:52:05 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 17 Jun 2017 07:52:05 +0700
Subject: [Slackbuilds-users] Updates - 20170617.1
Message-ID: <61c1a229-3168-d9f6-f169-8772c6e50d3d@slackbuilds.org>

Following last Thursday update, here's a small number of update this
week. It fixes building rust using local bootstrap and also
python-requests is updated to include 4 dependencies. For letsencrypt
users, you might need to install/upgrade this new deps in order to get
things working again. Big thanks to Audrius for spotting it.


Sat Jun 17 00:33:32 UTC 2017
development/atom-amd64: Updated for version 1.18.0.
development/global: Updated for version 6.5.7.
development/gpsim: Updated for version 0.29.0.
development/jupyter-nbdime: Updated dependencies.
development/rust: Fix build with local bootstrap.
development/simavr: Added (A lean, mean and hackable AVR simulator).
graphics/opencollada: Updated for version 1.6.54
libraries/dropbox-python: Update DEP.
libraries/msgpack-c: Updated for version 2.1.3.
misc/KeePass: Updated for version 2.36.
multimedia/Mopidy: Update DEP.
network/deis: Update DEP.
python/PythonQt: Updated for version 3.2.0
python/idna: Updated for version 2.5.
python/python-chardet: Updated for version 3.0.4.
python/python-requests: Update DEP.
python/python-urllib3: Updated for version 1.21.1.
system/gsmartcontrol: Updated for version 1.0.0.
system/salt: Update DEP.
system/virt-manager: Update DEP.
+--------------------------+


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170617/3f57ed66/attachment.asc>

From kjhambrick at gmail.com  Sat Jun 17 23:48:31 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sat, 17 Jun 2017 18:48:31 -0500
Subject: [Slackbuilds-users] md5sum on gsmartcontrol.info Version 1
Message-ID: <CANBHt+MPHky9aaZcsiE9s0+dxauRcmov3CoN76HyF1qQikM8Lw@mail.gmail.com>

Erik --

The MD5SUM Line in gsmartctl.info Version 1.0.0 is missing the leading
digit.

Patch attached.

Thank you for your time and effort !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170617/c36803df/attachment.html>
-------------- next part --------------
--- gsmartcontrol.info-orig	2017-06-17 18:37:06.957047791 -0500
+++ gsmartcontrol.info	2017-06-17 18:43:02.731081531 -0500
@@ -2,7 +2,7 @@
 VERSION="1.0.0"
 HOMEPAGE="https://sourceforge.net/projects/gsmartcontrol/"
 DOWNLOAD="https://sourceforge.net/projects/gsmartcontrol/files/1.0.0/gsmartcontrol-1.0.0.tar.bz2"
-MD5SUM="adec9d4533b8e388f03ab466f296121"
+MD5SUM="1adec9d4533b8e388f03ab466f296121"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""

From chris.willing at iinet.net.au  Sun Jun 18 01:00:28 2017
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Sun, 18 Jun 2017 11:00:28 +1000
Subject: [Slackbuilds-users] Updates - 20170615.1 (flashplayer)
In-Reply-To: <5330f2a0-cdca-2427-b9b8-66d9ba3f7054@slackbuilds.org>
References: <5330f2a0-cdca-2427-b9b8-66d9ba3f7054@slackbuilds.org>
Message-ID: <ef7d0c57-cd93-359c-9940-41a80cb7768e@iinet.net.au>

On 15/06/17 21:54, Willy Sudiarto Raharjo wrote:

> multimedia/flashplayer-plugin: Updated for version 26.0.0.126.
>

While updating this morning I found I couldn't download the source for
this version. Looks like its already been updated upstream to version
26.0.0.131.

chris

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

From willysr at slackbuilds.org  Sun Jun 18 01:26:08 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 18 Jun 2017 08:26:08 +0700
Subject: [Slackbuilds-users] Updates - 20170615.1 (flashplayer)
In-Reply-To: <ef7d0c57-cd93-359c-9940-41a80cb7768e@iinet.net.au>
References: <5330f2a0-cdca-2427-b9b8-66d9ba3f7054@slackbuilds.org>
 <ef7d0c57-cd93-359c-9940-41a80cb7768e@iinet.net.au>
Message-ID: <d714e421-1dcf-84a0-6b77-b551167389ee@slackbuilds.org>

>> multimedia/flashplayer-plugin: Updated for version 26.0.0.126.
>>
> 
> While updating this morning I found I couldn't download the source for
> this version. Looks like its already been updated upstream to version
> 26.0.0.131.

Thanks Christoph
I have update flashplayer and pepperflash-plugins to the latest version
on 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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170618/8fc2bce0/attachment.asc>

From willysr at slackbuilds.org  Sun Jun 18 01:28:08 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 18 Jun 2017 08:28:08 +0700
Subject: [Slackbuilds-users] md5sum on gsmartcontrol.info Version 1
In-Reply-To: <CANBHt+MPHky9aaZcsiE9s0+dxauRcmov3CoN76HyF1qQikM8Lw@mail.gmail.com>
References: <CANBHt+MPHky9aaZcsiE9s0+dxauRcmov3CoN76HyF1qQikM8Lw@mail.gmail.com>
Message-ID: <ea9257e2-f440-2528-c191-133dbd4b1ed0@slackbuilds.org>

> The MD5SUM Line in gsmartctl.info Version 1.0.0 is missing the leading
> digit.
> 
> Patch attached.
> 
> Thank you for your time and effort !

Fixed in my branch

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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170618/f689f4f8/attachment.asc>

From aaditya_gnulinux at zoho.com  Sun Jun 18 11:14:54 2017
From: aaditya_gnulinux at zoho.com (Aaditya Bagga)
Date: Sun, 18 Jun 2017 16:44:54 +0530
Subject: [Slackbuilds-users] redshift and geoclue2
Message-ID: <5ff1803d-ed38-dd4c-f149-08823148849c@zoho.com>

Hi guys,

Could an SBo admin update the redshift SlackBuild? I tried emailing the 
current maintainer but could not get a response.

Currently it checks for geoclue and disables geoclue2 support (needed 
for automatic location detection), while the correct behaviour is to 
check for geoclue-2.0 and then disable geoclue2 support.

I have attached a patch.

geoclue2 (added recently) can also be listed as an optional dependency 
in the README.

Thx,
Aaditya

-------------- next part --------------
A non-text attachment was scrubbed...
Name: redshift_geoclue2.patch
Type: text/x-patch
Size: 419 bytes
Desc: not available
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170618/92c03b40/attachment.bin>

From artourter at gmail.com  Sun Jun 18 20:00:33 2017
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Sun, 18 Jun 2017 21:00:33 +0100
Subject: [Slackbuilds-users] redshift and geoclue2
In-Reply-To: <5ff1803d-ed38-dd4c-f149-08823148849c@zoho.com>
References: <5ff1803d-ed38-dd4c-f149-08823148849c@zoho.com>
Message-ID: <CAK09-v=d6C6EY5NFm_ACWiHGR+4gA_URW+tuhUFLKHfQDC_46w@mail.gmail.com>

Hi,

I have an updated package ready but i have been busy. Will submit it for
next release.

Cheers

Greg

On 18 Jun 2017 12:15, "Aaditya Bagga" <aaditya_gnulinux at zoho.com> wrote:

> Hi guys,
>
> Could an SBo admin update the redshift SlackBuild? I tried emailing the
> current maintainer but could not get a response.
>
> Currently it checks for geoclue and disables geoclue2 support (needed for
> automatic location detection), while the correct behaviour is to check for
> geoclue-2.0 and then disable geoclue2 support.
>
> I have attached a patch.
>
> geoclue2 (added recently) can also be listed as an optional dependency in
> the README.
>
> Thx,
> Aaditya
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170618/77c0e8c1/attachment.html>

From chris.willing at iinet.net.au  Mon Jun 19 23:56:01 2017
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 20 Jun 2017 09:56:01 +1000
Subject: [Slackbuilds-users] Tracking version releases
In-Reply-To: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au>
References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au>
Message-ID: <e14dd071-798a-3751-572d-bfb3b66afdf3@iinet.net.au>

On 12/05/17 15:15, Christoph Willing wrote:
> Hi all,
> 
> I don't have a huge number of SlackBuilds to maintain but enough that
> its easy to lose track of upstream development and know when new
> versions have been released. Occasionally I do a find of .info files
> containing my name in the SBo file tree and go to each of the relevant
> websites looking for new releases. Sometimes a user sends me email about
> an update. Some repos can send email notifications, some have RSS feeds
> etc., but there doesn't seem to be a consistent mechanism for this sort
> of thing. There has to be a better way, so does anyone already have a
> better way to keep track before I write something to do it?
> 
> Well, before waiting for a reply to that question, I already started
> writing a tool of my own to do that. It's not quite complete but close
> enough - my 6 SlackBuild updates this week were all due to prompting
> while developing/testing/documenting the thing.
> 
> The new tool can currently deal with projects at github, sourceforge,
> pypi & libreoffice. It's been written to enable new  repo modules to be
> added fairly easily. My real question is whether anyone knows of other
> repositories that should be included (and preferably have some sort of
> API available for access), so that modules for them can be added?
> 
> I guess you should still let me know if this has already been done
> before I spend too much more time on it.
> 
> BTW its at:
>     https://github.com/cwilling/pvc
> 

Thanks for everyone's input on this - much of it has been incorporated.

It's differs from repology in being a command line tool (rather than
browser tool) and dealing with source code repository releases (rather
than various distro's package releases).

The built in modules for various repository types are currently:
alsa, freedesktop, generic, github, gnu, hackage, http, ibiblio,
iisland, libreoffice, metacpan, mirrorservice, pypi, samba, savannah,
sbdirectlinks, sgi, sourceforge & xiph.

This means projects from any of those repos can be trivially added to
your watch list with something like:
	pvc add -p pvc -t github -u cwilling/pvc
which adds the "pvc" project at github to my default watch list. I can
then check it's individual status at any time with:
	pvc check pvc
or check the entire default watch list with :
	pvc check

Additional user defined modules for other repos are supported, made
easier by provision of a template to work from.

Multiple watch lists are supported. There's always a default watch list,
but any number of additional watch lists can be easily configured. I use
the default watch list to track the upstream releases  of SBo scripts
which I maintain.

Out of interest (and testing purposes), I made another watch list to
track upstream releases of packages in -current's "ap" directory. As a
demonstration, here's what happens when checking that watch list (named
"set_ap"). In this case I've added timing too:

chris at d6:~$ time pvc check -w set_ap
Project flac  = 1.3.2
Project cdparanoia  = 10.2
Project most  = 5.0.0a
******* gphoto2 local version = 2.5.11 remote version = 2_5_14
Project acct  = 6.6.3
Project a2ps  = 4.14
******* diffutils local version = 3.5 remote version = 3.6
Project htop  = 2.0.2
Project lsscsi  = 0.28
Project enscript  = 1.6.6
Project bpe  = 2.01.00
Project cdrdao  = 1.2.3
Project dc3dd  = 7.2.646
Project cdrtools  = 3.01
Project ghostscript-fonts-std  = 8.11
******* gutenprint local version = 5.2.12 remote version = 5.2.13
Project dmapi  = 2.2.12
Project madplay  = 0.15.2b
Project joe  = 4.4
******* hplip local version = 3.17.4 remote version = 3.17.6
******* mpg123 local version = 1.23.4 remote version = 1.25.0
Project alsa-utils  = 1.1.4
Project radeontool  = 1.6.3
Project pamixer  = 1.3.1
Project vorbis-tools  = 1.4.0
Project groff  = 1.22.3
Project pm-utils  = 1.4.1
Project screen  = 4.5.1
******* dmidecode local version = 3.0 remote version = 3.1
Project nano  = 2.8.4
******* tmux local version = 2.4 remote version = 2.5
Project usbmuxd  = 1.1.0
Project normalize  = 0.7.7
Project sox  = 14.4.2
Project ksh93  = 2012-08-01
Project texinfo  = 6.3
Project sqlite  = 3190300
Project workbone  = 2.40
Project squashfs-tools  = 4.3
******* vim local version = 8.0.0600 remote version = 8.0.0648
Project terminus-font  = 4.40
******* cups-filters local version = 1.13.5 remote version = 1.14.0
Project seejpeg  = 1.10
Project sudo  = 1.8.20p2
Project rzip  = 2.1
Project xfsdump  = 3.1.6
Project zsh  = 5.3.1
Project jove  = 4.16.0.73
Project bc  = 1.07.1
******* soma local version = 2.10.4 remote version = 2.11.0
Project sc  = 7.16
Project ddrescue  = 1.22
Project vbetool  = 1.2.2
Project itstool  = 2.0.2
Project ispell  = 3.4.00
******* ghostscript local version = 9.20 remote version = 9.21
Project moc  = 2.5.2
Project libx86  = 1.1
******* mariadb local version = 10.0.30 remote version = 10.2.6
Project lsof  = 4.89
******* cgmanager local version = 0.39 remote version = 0.41
Project qpdf  = 6.0.0
******* sysstat local version = 11.2.1.1 remote version = 11.5.6
Project mc  = 4.8.19
******* rpm local version = 4.12.0.1 remote version = 4.13.0.1
Project jed  = 0.99-19
******* diffstat local version = 1.60 remote version = 1.61
******* lxc local version = 2.0.1 remote version = 2.0.8
Project cups  = 2.2.3
******* powertop local version = 2.8 remote version = 2.9
Project dvd+rw-tools  = 7.1

real    0m17.810s
user    0m0.778s
sys     0m0.047s


>From that output, it easy to see which projects have had new releases. I
don't track -current myself but I've been finding this really useful for
my SBo packages - I just run 'pvc check' each morning and I can
immediately see whether any project has been updated in the last day
(well, since last time I updated).

Feel free to try it out - any feedback welcome:
    https://github.com/cwilling/pvc

chris

BTW some GitHub projects have lots (and lots) of pages of releases which
pvc needs to look through for the latest release. Sometimes that is
necessary but often it is not. For instance the vim/vim project has 192
pages or releases, each entailing 2-3 seconds to find & download, even
though the desired result is on the first page. In such cases, please
read the documentation about configuring a "multipagelimit" for that
project, otherwise wait a long time for useless data to be downloaded.

From davidnchmelik at gmail.com  Tue Jun 20 07:57:14 2017
From: davidnchmelik at gmail.com (David Melik)
Date: Tue, 20 Jun 2017 00:57:14 -0700
Subject: [Slackbuilds-users] Tracking version releases
In-Reply-To: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au>
References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au>
Message-ID: <cbbdb6d6-41e7-0673-cd3d-5658046bc5ec@gmail.com>

On 05/11/2017 10:15 PM, Christoph Willing wrote:
> [...] I don't have a huge number of SlackBuilds to maintain but enough that
> its easy to lose track of upstream development and know when new
> versions have been released. Occasionally I do a find of .info files
> containing my name in the SBo file tree and go to each of the relevant
> websites looking for new releases. Sometimes a user sends me email about
> an update. Some repos can send email notifications, some have RSS feeds
> etc., but there doesn't seem to be a consistent mechanism for this sort
> of thing. There has to be a better way, so does anyone already have a
> better way to keep track before I write something to do it?
> 
> Well, before waiting for a reply to that question, I already started
> writing a tool of my own to do that. It's not quite complete but close
> enough - my 6 SlackBuild updates this week were all due to prompting
> while developing/testing/documenting the thing.
> 
> The new tool can currently deal with projects at github, sourceforge,
> pypi & libreoffice. It's been written to enable new  repo modules to be
> added fairly easily. My real question is whether anyone knows of other
> repositories that should be included (and preferably have some sort of
> API available for access), so that modules for them can be added?
> 
> I guess you should still let me know if this has already been done
> before I spend too much more time on it.
> 
> BTW its at:
>      https://github.com/cwilling/pvc [...]

I need that because many projects are notorious for not announcing new 
versions; they could not care less that package maintainers spread 
projects' software. Many projects are switching from newsgroups, 
listervs, IRC, and (though not as good) classic web-forums, to social 
networks and new web-chat rooms, or mixtures of those two, that few 
people want to sign up for... or they use newsgroups and/or listservs or 
version control sites posting lots of updates *except* actual version 
numbers. It's a mess. Though the more SlackBuilds I made, the more I got 
into habit to check, occasionally if I've been busy, it was maybe half a 
year before I noticed several new version of some software that I like, 
want to make available, if I don't actually often use it.

So, I installed pvc as root, and when I run it I get this error (similar 
error as root:)

d at cosmos:~$ pvc
fs.js:952
return binding.readdir(pathModule._makeLong(path), options.encoding);
^

Error: ENOENT: no such file or directory, scandir '/home/d/.local/share/pvc'
at Error (native)
at Object.fs.readdirSync (fs.js:952:18)
at /usr/share/pvc/pvcWatcher.js:14:6
at Array.forEach (native)
at Object.<anonymous> (/usr/share/pvc/pvcWatcher.js:9:13)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/usr/share/pvc/pvc:11:17)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)

From chris.willing at iinet.net.au  Tue Jun 20 09:51:32 2017
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 20 Jun 2017 19:51:32 +1000
Subject: [Slackbuilds-users] Tracking version releases
In-Reply-To: <cbbdb6d6-41e7-0673-cd3d-5658046bc5ec@gmail.com>
References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au>
 <cbbdb6d6-41e7-0673-cd3d-5658046bc5ec@gmail.com>
Message-ID: <0c20d417-22d3-1180-e1c1-9894bc47134e@iinet.net.au>

On 20/06/17 17:57, David Melik wrote:

>>      https://github.com/cwilling/pvc [...]
> 
> I need that because many projects are notorious for not announcing new
> versions; they could not care less that package maintainers spread
> projects' software. Many projects are switching from newsgroups,
> listervs, IRC, and (though not as good) classic web-forums, to social
> networks and new web-chat rooms, or mixtures of those two, that few
> people want to sign up for... or they use newsgroups and/or listservs or
> version control sites posting lots of updates *except* actual version
> numbers. It's a mess. Though the more SlackBuilds I made, the more I got
> into habit to check, occasionally if I've been busy, it was maybe half a
> year before I noticed several new version of some software that I like,
> want to make available, if I don't actually often use it.
> 
> So, I installed pvc as root, and when I run it I get this error (similar
> error as root:)
> 
> d at cosmos:~$ pvc
> fs.js:952
> return binding.readdir(pathModule._makeLong(path), options.encoding);
> ^
> 
> Error: ENOENT: no such file or directory, scandir
> '/home/d/.local/share/pvc'

That's a bit embarrassing - sorry about that. I'm just about to upload a
proper fix but in the meantime you could just create that directory
yourself and the rest will just work.

I see that one of your SBo SlackBuilds is python-jango-legacy which is
being held at 1.8.17. When you add that project to your watchlist with
something like:
    pvc add -p python-jango-legacy -t github -u django/django

it will find that the latest version is actually 1.11.2 and use that
value in the watch file entry it creates. You can "manually" change the
version recorded in your watchfile with:
    pvc update -p python-jango-legacy -v 1.8.17

The problem is that every time you do a 'pvc check' or 'pvc check
python-jango-legacy', it will report that your 1.8.17 version is out of
date. I'll have to think about how to deal with that sort of thing.

Thanks for reporting,
chris


From davidnchmelik at gmail.com  Tue Jun 20 10:32:16 2017
From: davidnchmelik at gmail.com (David Melik)
Date: Tue, 20 Jun 2017 03:32:16 -0700
Subject: [Slackbuilds-users] Tracking version releases
In-Reply-To: <0c20d417-22d3-1180-e1c1-9894bc47134e@iinet.net.au>
References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au>
 <cbbdb6d6-41e7-0673-cd3d-5658046bc5ec@gmail.com>
 <0c20d417-22d3-1180-e1c1-9894bc47134e@iinet.net.au>
Message-ID: <1c227998-e3c7-296e-4f6e-5b5b83044278@gmail.com>

On 06/20/2017 02:51 AM, Christoph Willing wrote:
> On 20/06/17 17:57, David Melik wrote:
> 
>>>       https://github.com/cwilling/pvc [...]
>> Error: ENOENT: no such file or directory, scandir
>> '/home/d/.local/share/pvc'
> 
> That's a bit embarrassing - sorry about that. I'm just about to upload a
> proper fix but in the meantime you could just create that directory
> yourself and the rest will just work.

I made the folder, and pvc couldn't find a configuration, so I tried to 
add a project (pvc,) hoping that would do it. Instead it said what's 
below this paragraph. I'm not sure NodeJS is working on my PC, though I 
did removepkg to the old 'Node,' maybe last year, and now just did 
'upgradepkg --reinstall' current NodeJS on SBo. I don't use other NodeJS 
software (except one thing on server) and don't really know how...
------------------------------------------------------------------------

d at cosmos:~$ pvc add --project pvc --type github --urlbase cwilling/pvc
Had ENOENT: empty configuration
fs.js:304
   binding.open(pathModule._makeLong(path),
           ^

TypeError: path must be a string or Buffer
     at TypeError (native)
     at Object.fs.readFile (fs.js:304:11)
     at loadWatchList (/usr/share/pvc/pvc:141:6)
     at EventEmitter.<anonymous> (/usr/share/pvc/pvc:85:3)
     at emitOne (events.js:96:13)
     at EventEmitter.emit (events.js:188:7)
     at ReadFileContext.callback (/usr/share/pvc/pvc:174:20)
     at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:366:13)

> I see that one of your SBo SlackBuilds is python-jango-legacy which is
> being held at 1.8.17. When you add that project to your watchlist with
> something like:
>      pvc add -p python-jango-legacy -t github -u django/django
> 
> it will find that the latest version is actually 1.11.2 and use that
> value in the watch file entry it creates. You can "manually" change the
> version recorded in your watchfile with:
>      pvc update -p python-jango-legacy -v 1.8.17
> 
> The problem is that every time you do a 'pvc check' or 'pvc check
> python-jango-legacy', it will report that your 1.8.17 version is out of
> date. I'll have to think about how to deal with that sort of thing.

I probably won't check python-django-legacy updates, as it's 
python-django renamed with old version, and I don't need to update until 
Mathics does, when it (if current enough) will use python-django, so 
I'll end or pass on python-django-legacy. As time of this post, Mathics 
hasn't had update mentioned in their 'Slack' (slack.com) room (their 
main quick communication place)... an unfortunately-named new web-chat, 
as in computing, 'Slack' was an informal 'Slackware' abbreviation...

D

From chris.willing at iinet.net.au  Tue Jun 20 12:19:49 2017
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 20 Jun 2017 22:19:49 +1000
Subject: [Slackbuilds-users] Tracking version releases
In-Reply-To: <1c227998-e3c7-296e-4f6e-5b5b83044278@gmail.com>
References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au>
 <cbbdb6d6-41e7-0673-cd3d-5658046bc5ec@gmail.com>
 <0c20d417-22d3-1180-e1c1-9894bc47134e@iinet.net.au>
 <1c227998-e3c7-296e-4f6e-5b5b83044278@gmail.com>
Message-ID: <b6bf31dd-2256-c446-1f8d-7325b1a14401@iinet.net.au>

On 20/06/17 20:32, David Melik wrote:
> On 06/20/2017 02:51 AM, Christoph Willing wrote:
>> On 20/06/17 17:57, David Melik wrote:
>>
>>>>       https://github.com/cwilling/pvc [...]
>>> Error: ENOENT: no such file or directory, scandir
>>> '/home/d/.local/share/pvc'
>>
>> That's a bit embarrassing - sorry about that. I'm just about to upload a
>> proper fix but in the meantime you could just create that directory
>> yourself and the rest will just work.
> 
> I made the folder, and pvc couldn't find a configuration, so I tried to
> add a project (pvc,) hoping that would do it. Instead it said what's
> below this paragraph. 

Hi David,

I've applied a fix but this time you'll need to download the new
version. If you installed from a tarball, the new one to download is
0.7.3. If you cloned the git repo, a 'git pull' should update to the
latest (fixed) code. Then just run (as root) 'make install' again.

BTW, we really shouldn't be using this list to debug this application.
If you have a GitHub account, you could open a new issue at the pvc
project; otherwise feel free to email me directly. I appreciate the
fresh eyes on the project.

chris

From willysr at slackbuilds.org  Wed Jun 21 11:03:09 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 21 Jun 2017 18:03:09 +0700
Subject: [Slackbuilds-users] opus 1.2
Message-ID: <7b93b14c-c7d4-62ad-95a1-7b6cc9a63d62@slackbuilds.org>

Hi guys,

just heads-up that i'm bumping opus 1.2 for this week's public update
Although the release notes saying that it doesn't break compatibility
nor any regressions found since 1.1.5, it's better to test our scripts
against 1.2.

Here's a list of scripts that requires opus directly
audio/butt
audio/opus-tools
audio/opusfile
games/iortcw
games/openspades
games/unvanquished
libraries/libopusenc
multimedia/HandBrake
multimedia/vlc
network/c-toxcore
network/mumble
network/toxcore


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170621/38e6ebb3/attachment.asc>

From nishant at mnspace.net  Wed Jun 21 13:47:19 2017
From: nishant at mnspace.net (Nishant Limbachia)
Date: Wed, 21 Jun 2017 08:47:19 -0500
Subject: [Slackbuilds-users] opus 1.2
In-Reply-To: <7b93b14c-c7d4-62ad-95a1-7b6cc9a63d62@slackbuilds.org>
References: <7b93b14c-c7d4-62ad-95a1-7b6cc9a63d62@slackbuilds.org>
Message-ID: <3032af12-d175-a484-8e22-3a7591504ed4@mnspace.net>


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 06/21/2017 06:03 AM, Willy Sudiarto Raharjo wrote:
> Hi guys, > > just heads-up that i'm bumping opus 1.2 for this week's public
update > Although the release notes saying that it doesn't break
compatibility > nor any regressions found since 1.1.5, it's better to
test our scripts > against 1.2. > > Here's a list of scripts that
requires opus directly > audio/butt > audio/opus-tools > audio/opusfile
> games/iortcw > games/openspades > games/unvanquished >
libraries/libopusenc > multimedia/HandBrake > multimedia/vlc >
network/c-toxcore > network/mumble > network/toxcore > > > > >
_______________________________________________ > SlackBuilds-users
mailing list > SlackBuilds-users at slackbuilds.org >
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >
FAQ - https://slackbuilds.org/faq/ >
Willy,

All these build fine with Opus 1.2.

audio/opus-tools
audio/opusfile
libraries/libopusenc

Thanks,

- -- 
Nishant Limbachia
nishant at mnspace.net
### Please note the new pgp keys
Old GPG Key: 0x0FF9D6D5 (expiring soon)
Old GPG Fingerprint: CC77 2954 DBDD CA46 49D5 BC90 786E 5DA2 0FF9 D6D5
New GPG Key: 0x3D46A2D1
New GPG Fingerprint: 44D1 27CE D07F 2ED1 B4AD 2BEE A828 D6D6 3D46 A2D1
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEERNEnztB/LtG0rSvuqCjW1j1GotEFAllKeOAACgkQqCjW1j1G
otGaGg/+LfhBxvGqXnKXVi2Bw+ElqK+m8SDXn1lktxCr6wiLHDsPYwMG8i7BkjjN
Hhl8EPupTQdC7vw7jGzVmwfWia1iz/Hrq2kccAR7kShk6zssf+Q018phQrgWVw1C
Ois6SVgcDVweYsEIIAQGC9k+cBI7ibBnZsTiLg9NDK/ObYcrYw8LKNYF6dCubWVi
OUquEwLT485wDtNPlKtHN1YGqWjczZCA12hD5jqJHxJRHM1Mx4MB0IZhkFxtyuOO
kiLVgPXZqHroGsYi1HSebbaX+35b41tabNVfdzgqPf1S/dkBR2n8P4X/kYM+cUwC
ZIwwvpr73RNkLxbq2MuDDnG2WRbn+haeJRpXAXOqJOByKFNCx7VEJ+ygoQLuaTNj
8Cv+R8M/OW3o76aII4cgaEFfY+N+YnM/INgSV84aEmZanep20Y6ib2xbmmEMBNlq
Xttbnqwt7rUz6p03QttYABSbH52pEGRF0vT05E5bi1aBPOnDpY2DZ8JhUu0ooz6y
W8smsg4Agi0WSkDd0d349OEhPaiu2MSiha+BXmqZWXTNXICyElZRUmS23sF4dIok
uZ88lVw/bP46U6qYM4oQl5Yhb3+tTQ5egz65SJDauIz71CT4ymamDT6LRLBjNek/
ylcO4mfWXklovCDC32pvo2lbL3sqzf+UYTERkWwjPvqkOIvfoug=
=GXP3
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170621/aaae1759/attachment-0001.html>

From slacker6896 at gmail.com  Wed Jun 21 15:15:50 2017
From: slacker6896 at gmail.com (Sebastien BALLET)
Date: Wed, 21 Jun 2017 17:15:50 +0200
Subject: [Slackbuilds-users] opus 1.2
In-Reply-To: <7b93b14c-c7d4-62ad-95a1-7b6cc9a63d62@slackbuilds.org>
References: <7b93b14c-c7d4-62ad-95a1-7b6cc9a63d62@slackbuilds.org>
Message-ID: <CAA2+phG-3+5bDR1bkHOOZ0sQE4dYJEnveinyHw569JW=eM5R0A@mail.gmail.com>

Hello,

No issue with games/iortcw.

-- 
SeB

2017-06-21 13:03 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:

> Hi guys,
>
> just heads-up that i'm bumping opus 1.2 for this week's public update
> Although the release notes saying that it doesn't break compatibility
> nor any regressions found since 1.1.5, it's better to test our scripts
> against 1.2.
>
> Here's a list of scripts that requires opus directly
> audio/butt
> audio/opus-tools
> audio/opusfile
> games/iortcw
> games/openspades
> games/unvanquished
> libraries/libopusenc
> multimedia/HandBrake
> multimedia/vlc
> network/c-toxcore
> network/mumble
> network/toxcore
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170621/4f08c615/attachment.html>

From marc at mos6581.de  Wed Jun 21 15:49:32 2017
From: marc at mos6581.de (Marcel Saegebarth)
Date: Wed, 21 Jun 2017 17:49:32 +0200
Subject: [Slackbuilds-users] opus 1.2
In-Reply-To: <7b93b14c-c7d4-62ad-95a1-7b6cc9a63d62@slackbuilds.org>
References: <7b93b14c-c7d4-62ad-95a1-7b6cc9a63d62@slackbuilds.org>
Message-ID: <346edb20-e5b8-3ec0-1ef6-298497e98278@mos6581.de>

On 06/21/2017 01:03 PM, Willy Sudiarto Raharjo wrote:
> just heads-up that i'm bumping opus 1.2 for this week's public update
> Although the release notes saying that it doesn't break compatibility
> nor any regressions found since 1.1.5, it's better to test our scripts
> against 1.2.

ffmpeg also builds fine against opus 1.2.

--------------------------------------------------------------------------------
PGP 32 bit Key ID: 0x69EC498D
PGP 64 bit Key ID: 0x8EE93B2D69EC498D
PGP Key fingerprint: D320 76CB 4053 D544 52BD  D461 8EE9 3B2D 69EC 498D

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

From chris.willing at iinet.net.au  Wed Jun 21 22:15:49 2017
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Thu, 22 Jun 2017 08:15:49 +1000
Subject: [Slackbuilds-users] opus 1.2
In-Reply-To: <7b93b14c-c7d4-62ad-95a1-7b6cc9a63d62@slackbuilds.org>
References: <7b93b14c-c7d4-62ad-95a1-7b6cc9a63d62@slackbuilds.org>
Message-ID: <8159f7b4-f76d-d0e8-eac4-dca24baa5b2a@iinet.net.au>

On 21/06/17 21:03, Willy Sudiarto Raharjo wrote:
> Hi guys,
> 
> just heads-up that i'm bumping opus 1.2 for this week's public update
> Although the release notes saying that it doesn't break compatibility
> nor any regressions found since 1.1.5, it's better to test our scripts
> against 1.2.
> 
> Here's a list of scripts that requires opus directly
...
> multimedia/vlc
...

vlc is OK with the new opus.

chris

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170622/191d4596/attachment.asc>

From info at microlinux.fr  Thu Jun 22 17:52:12 2017
From: info at microlinux.fr (Nicolas Kovacs)
Date: Thu, 22 Jun 2017 19:52:12 +0200
Subject: [Slackbuilds-users] (Temporarily) giving up my SlackBuilds
Message-ID: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>

Hi everybody,

Due to an unforeseen workload, I'm currently unable to maintain my
Slackware packages, so I'd like to give up maintenance to anybody who
might be willing to take them.

For the moment, there's at least one package that needs an urgent
version bump: elementary-xfce. Sources for the old version aren't
available anymore.

On a side note: I'm currently working as a hired admin for a french
administration, and I'm spending my time getting up to speed with the
innards of CentOS 7.

Cheers,

Niki
-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32

From atelszewski at gmail.com  Thu Jun 22 18:08:16 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 22 Jun 2017 20:08:16 +0200
Subject: [Slackbuilds-users] (Temporarily) giving up my SlackBuilds
In-Reply-To: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>
References: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>
Message-ID: <4a89802c-d6f6-90d9-4847-070aa80cfd51@gmail.com>

On 22/06/17 19:52, Nicolas Kovacs wrote:
> For the moment, there's at least one package that needs an urgent
> version bump: elementary-xfce. Sources for the old version aren't
> available anymore.

I'll take it.

Anyways, quick fix is to update download link to:
https://github.com/shimmerproject/elementary-xfce/archive/v0.7/elementary-xfce-0.7.tar.gz

MD5 is fine as is.

-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Thu Jun 22 18:20:36 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 22 Jun 2017 20:20:36 +0200
Subject: [Slackbuilds-users] (Temporarily) giving up my SlackBuilds
In-Reply-To: <4a89802c-d6f6-90d9-4847-070aa80cfd51@gmail.com>
References: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>
 <4a89802c-d6f6-90d9-4847-070aa80cfd51@gmail.com>
Message-ID: <CAPsDuS6Jt6AO49bBqFpNbRoHqVmdyxtEXdd44Bk1ybyV2mC+Dg@mail.gmail.com>

2017-06-22 20:08 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:
> On 22/06/17 19:52, Nicolas Kovacs wrote:
>>
>> For the moment, there's at least one package that needs an urgent
>> version bump: elementary-xfce. Sources for the old version aren't
>> available anymore.
>
>
> I'll take it.
>
> Anyways, quick fix is to update download link to:
> https://github.com/shimmerproject/elementary-xfce/archive/v0.7/elementary-xfce-0.7.tar.gz
>
> MD5 is fine as is.

pushed in my branch.

From matteo.bernardini at gmail.com  Thu Jun 22 18:21:33 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 22 Jun 2017 20:21:33 +0200
Subject: [Slackbuilds-users] (Temporarily) giving up my SlackBuilds
In-Reply-To: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>
References: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>
Message-ID: <CAPsDuS4zzR4TKx+MQ65F5aS-UKyZAm4hX0jqWONOa8e7R40SXw@mail.gmail.com>

2017-06-22 19:52 GMT+02:00 Nicolas Kovacs <info at microlinux.fr>:
> Hi everybody,
>
> Due to an unforeseen workload, I'm currently unable to maintain my
> Slackware packages, so I'd like to give up maintenance to anybody who
> might be willing to take them.
>
> For the moment, there's at least one package that needs an urgent
> version bump: elementary-xfce. Sources for the old version aren't
> available anymore.
>
> On a side note: I'm currently working as a hired admin for a french
> administration, and I'm spending my time getting up to speed with the
> innards of CentOS 7.

good luck with the new job, Niki!

From info at microlinux.fr  Thu Jun 22 19:06:02 2017
From: info at microlinux.fr (Nicolas Kovacs)
Date: Thu, 22 Jun 2017 21:06:02 +0200
Subject: [Slackbuilds-users] (Temporarily) giving up my SlackBuilds
In-Reply-To: <CAPsDuS4zzR4TKx+MQ65F5aS-UKyZAm4hX0jqWONOa8e7R40SXw@mail.gmail.com>
References: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>
 <CAPsDuS4zzR4TKx+MQ65F5aS-UKyZAm4hX0jqWONOa8e7R40SXw@mail.gmail.com>
Message-ID: <08d92ee1-0268-b3c8-24a2-789b8e950062@microlinux.fr>

Le 22/06/2017 ? 20:21, Matteo Bernardini a ?crit :
> good luck with the new job, Niki!

Thanks, Matteo. It's nothing highly regular, only a temporary mission.
But this opens a few perspectives.

Cheers,

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32

From z.coldplayer at gmail.com  Thu Jun 22 19:06:57 2017
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Thu, 22 Jun 2017 23:06:57 +0400
Subject: [Slackbuilds-users] (Temporarily) giving up my SlackBuilds
In-Reply-To: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>
References: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>
Message-ID: <CAEWL1_85pJyvsA0eCXfkg6j4gMnE=2VLbx5Nz7CH1xqr4pTO9A@mail.gmail.com>

Bonne chance a ton nouveau boulot, Niki

Cheers

Pritvi

On 22 June 2017 at 21:52, Nicolas Kovacs <info at microlinux.fr> wrote:

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

From willysr at slackbuilds.org  Thu Jun 22 19:44:23 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 23 Jun 2017 02:44:23 +0700
Subject: [Slackbuilds-users] (Temporarily) giving up my SlackBuilds
In-Reply-To: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>
References: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>
Message-ID: <5a159a31-eb9c-4b44-5fbf-7db4c92eb170@slackbuilds.org>

> Due to an unforeseen workload, I'm currently unable to maintain my
> Slackware packages, so I'd like to give up maintenance to anybody who
> might be willing to take them.

Here's the list (minus elementary-xfce)
desktop/luna-wallpapers
system/man-pages-fr
system/untex
system/man-pages-extras-fr
network/squidGuard


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170623/edb94938/attachment.asc>

From yalhcru at gmail.com  Thu Jun 22 20:34:14 2017
From: yalhcru at gmail.com (B Watson)
Date: Thu, 22 Jun 2017 16:34:14 -0400
Subject: [Slackbuilds-users] (Temporarily) giving up my SlackBuilds
In-Reply-To: <5a159a31-eb9c-4b44-5fbf-7db4c92eb170@slackbuilds.org>
References: <ce2a8acf-1acd-0a36-5418-21160d7e6ead@microlinux.fr>
 <5a159a31-eb9c-4b44-5fbf-7db4c92eb170@slackbuilds.org>
Message-ID: <CAN1hMuAisvZ+eBWhp1e_fTb6BkWNK0RCNYJQKMSMU5KriA4SmA@mail.gmail.com>

 system/man-pages-fr
 system/untex
 system/man-pages-extras-fr

I'll take these 3.

From yalhcru at gmail.com  Thu Jun 22 22:56:13 2017
From: yalhcru at gmail.com (B Watson)
Date: Thu, 22 Jun 2017 18:56:13 -0400
Subject: [Slackbuilds-users] possible submission
Message-ID: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>

Would anyone object to my submitting an openjdk-bin build? Basically
just a prebuilt binary repack of the same version of openjdk that's
currently in the openjdk build.

I think this would be useful because come next Slackware release, gcc-java
will be gone (gcc upstream dropped it). Which means we're back to the
old "open source openjdk depends on Oracle proprietary jdk" issue that
we resolved a few months back. I (and probably others) would rather be
able to bootstrap openjdk without having to deal with Oracle.

Thoughts, opinions, better ideas?

From artourter at gmail.com  Thu Jun 22 23:02:48 2017
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Fri, 23 Jun 2017 00:02:48 +0100
Subject: [Slackbuilds-users] possible submission
In-Reply-To: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
References: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
Message-ID: <CAK09-vm7gzRKOurhKCbH42RoDWBMBS+AEd_3eOHoyVDEENjb4g@mail.gmail.com>

Actually, the removal of gcc-java will be a problem for one of the package
I maintain (pdftk). I wonder if the gcc-legacy project would consider
picking it up as well.

Cheers

Greg

On 22 June 2017 at 23:56, B Watson <yalhcru at gmail.com> wrote:

> Would anyone object to my submitting an openjdk-bin build? Basically
> just a prebuilt binary repack of the same version of openjdk that's
> currently in the openjdk build.
>
> I think this would be useful because come next Slackware release, gcc-java
> will be gone (gcc upstream dropped it). Which means we're back to the
> old "open source openjdk depends on Oracle proprietary jdk" issue that
> we resolved a few months back. I (and probably others) would rather be
> able to bootstrap openjdk without having to deal with Oracle.
>
> Thoughts, opinions, better ideas?
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170623/f4fb33df/attachment.html>

From chris.willing at iinet.net.au  Thu Jun 22 23:58:39 2017
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Fri, 23 Jun 2017 09:58:39 +1000
Subject: [Slackbuilds-users] possible submission
In-Reply-To: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
References: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
Message-ID: <2c27d3ed-29e2-8c16-1d4e-4f64517b3585@iinet.net.au>

On 23/06/17 08:56, B Watson wrote:
> Would anyone object to my submitting an openjdk-bin build? Basically
> just a prebuilt binary repack of the same version of openjdk that's
> currently in the openjdk build.
> 
> I think this would be useful because come next Slackware release, gcc-java
> will be gone (gcc upstream dropped it). Which means we're back to the
> old "open source openjdk depends on Oracle proprietary jdk" issue that
> we resolved a few months back. I (and probably others) would rather be
> able to bootstrap openjdk without having to deal with Oracle.
> 

I was wondering about this too. Even now, openjdk8 depends on openjdk to
bootstrap the build which I always thought was a bit strange; it seems
somehow wrong that building any software depends on the previous version
of that software. With gcc-java to be gone soon, building that previous
version (openjdk) won't be possible anymore, hence why having a -bin
version is needed for the future.

Although how long is that sustainable? Imagine in 10 years time -
working back through the build dependencies of openjdk12 and finding you
need a binary version of the same software from 10 years ago. If you
instead use the Oracle jdk for bootstrapping, then what does "open" in
openjdk mean?

chris

From yalhcru at gmail.com  Fri Jun 23 05:18:51 2017
From: yalhcru at gmail.com (B Watson)
Date: Fri, 23 Jun 2017 01:18:51 -0400
Subject: [Slackbuilds-users] possible submission
In-Reply-To: <2c27d3ed-29e2-8c16-1d4e-4f64517b3585@iinet.net.au>
References: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
 <2c27d3ed-29e2-8c16-1d4e-4f64517b3585@iinet.net.au>
Message-ID: <CAN1hMuCQqttmhvrm_6-CHtmZoJmQF3YPcjZ1rbeqQZyBO3UqPw@mail.gmail.com>

(Apologies to the rest of the list, this turned out to be a much longer
post than originally intended...)

On 6/22/17, Christoph Willing <chris.willing at iinet.net.au> wrote:
>
> I was wondering about this too. Even now, openjdk8 depends on openjdk to
> bootstrap the build which I always thought was a bit strange; it seems
> somehow wrong that building any software depends on the previous version
> of that software.

That's pretty much how all compilers work, though. At least the ones
written in the language they're a compiler for. To build gcc, you need
an existing C compiler to build it with (it probably doesn't *have* to
be gcc itself, just some C compiler with good standards compliance).

...though compiling a JDK requires both a JDK *and* a C compiler (since
bits of it are written in C).

Also, openjdk uses apache-ant as its build system (which is the Java
world's answer to Make), and apache-ant is in Java so it needs a Java
runtime just to execute.

> With gcc-java to be gone soon, building that previous
> version (openjdk) won't be possible anymore, hence why having a -bin
> version is needed for the future.

My thinking exactly.

> Although how long is that sustainable? Imagine in 10 years time -
> working back through the build dependencies of openjdk12 and finding you
> need a binary version of the same software from 10 years ago.

As I understand it, the way it's intended to work with openjdk is that
each version needs to be compiled with the previous version. So openjdk8
needs version 7... sometime in the next 10 years, openjdk12 will need
openjdk11, and that could either be a source or binary install I suppose.

What I don't know (since I haven't paid attention to Java in 10+ years)
is whether future versions of jdk/openjdk will always be compatible
with code written for older versions (source code and/or compiled
classes/jars). Will we get stuck having to still have openjdk version
7 in 10 years, because some piece of software written in Java can't be
compiled or run with openjdk 8 and up?

...Or do we already have that situation, and that's why we have openjdk
versions 6, 7, and 8 in our repo?

> If you instead use the Oracle jdk for bootstrapping, then what does "open"
> in openjdk mean?

Again, my thought exactly.

From willysr at slackbuilds.org  Fri Jun 23 07:01:27 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 23 Jun 2017 14:01:27 +0700
Subject: [Slackbuilds-users] possible submission
In-Reply-To: <CAN1hMuCQqttmhvrm_6-CHtmZoJmQF3YPcjZ1rbeqQZyBO3UqPw@mail.gmail.com>
References: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
 <2c27d3ed-29e2-8c16-1d4e-4f64517b3585@iinet.net.au>
 <CAN1hMuCQqttmhvrm_6-CHtmZoJmQF3YPcjZ1rbeqQZyBO3UqPw@mail.gmail.com>
Message-ID: <bbdb2f7c-eece-be3f-b953-db541ac9d302@slackbuilds.org>

> ...Or do we already have that situation, and that's why we have openjdk
> versions 6, 7, and 8 in our repo?

someday, we can drop older version of openjdk which is no longer used
and supported upstream.

-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170623/1b8b9878/attachment.asc>

From slacker6896 at gmail.com  Fri Jun 23 07:12:58 2017
From: slacker6896 at gmail.com (Sebastien BALLET)
Date: Fri, 23 Jun 2017 09:12:58 +0200
Subject: [Slackbuilds-users] possible submission
In-Reply-To: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
References: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
Message-ID: <CAA2+phHt-aJ82yWpkRWzqfAQv77WOGDik0uV0doJXL-BUy2b0Q@mail.gmail.com>

Hello,

Otherwise, there are zulu-openjdk7/8 slackbuilds to repackage the Azul's
Zulu build of OpenJDK 7/8.

https://slackbuilds.org/repository/14.2/development/zulu-openjdk7/
https://slackbuilds.org/repository/14.2/development/zulu-openjdk8/
http://zulu.org/

-- 
SeB

2017-06-23 0:56 GMT+02:00 B Watson <yalhcru at gmail.com>:

> Would anyone object to my submitting an openjdk-bin build? Basically
> just a prebuilt binary repack of the same version of openjdk that's
> currently in the openjdk build.
>
> I think this would be useful because come next Slackware release, gcc-java
> will be gone (gcc upstream dropped it). Which means we're back to the
> old "open source openjdk depends on Oracle proprietary jdk" issue that
> we resolved a few months back. I (and probably others) would rather be
> able to bootstrap openjdk without having to deal with Oracle.
>
> Thoughts, opinions, better ideas?
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170623/c09253ec/attachment.html>

From yalhcru at gmail.com  Fri Jun 23 07:57:59 2017
From: yalhcru at gmail.com (B Watson)
Date: Fri, 23 Jun 2017 03:57:59 -0400
Subject: [Slackbuilds-users] possible submission
In-Reply-To: <CAA2+phHt-aJ82yWpkRWzqfAQv77WOGDik0uV0doJXL-BUy2b0Q@mail.gmail.com>
References: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
 <CAA2+phHt-aJ82yWpkRWzqfAQv77WOGDik0uV0doJXL-BUy2b0Q@mail.gmail.com>
Message-ID: <CAN1hMuAcE2OeodstXihDxxxtv_8qR=M6T0QEG1NMuROA4-ptGg@mail.gmail.com>

On 6/23/17, Sebastien BALLET <slacker6896 at gmail.com> wrote:
> Hello,
>
> Otherwise, there are zulu-openjdk7/8 slackbuilds to repackage the Azul's
> Zulu build of OpenJDK 7/8.
>
> https://slackbuilds.org/repository/14.2/development/zulu-openjdk7/
> https://slackbuilds.org/repository/14.2/development/zulu-openjdk8/
> http://zulu.org/

Hm. I didn't know those were even there. So basically what I was asking
about already exists (since June 8 of this year)... but only for x86_64.

I still might do a 32-bit-only openjdk-bin build. Or call it
"openjdk-bootstrap", make it the bare minimum needed to build the real
openjdk. If it's even possible to pare it down any, I mean.

From chris.willing at iinet.net.au  Fri Jun 23 09:47:18 2017
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Fri, 23 Jun 2017 19:47:18 +1000
Subject: [Slackbuilds-users] possible submission
In-Reply-To: <CAN1hMuAcE2OeodstXihDxxxtv_8qR=M6T0QEG1NMuROA4-ptGg@mail.gmail.com>
References: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
 <CAA2+phHt-aJ82yWpkRWzqfAQv77WOGDik0uV0doJXL-BUy2b0Q@mail.gmail.com>
 <CAN1hMuAcE2OeodstXihDxxxtv_8qR=M6T0QEG1NMuROA4-ptGg@mail.gmail.com>
Message-ID: <f734ae7c-70b2-4000-ccea-2dfcd2bf5285@iinet.net.au>

On 23/06/17 17:57, B Watson wrote:
> On 6/23/17, Sebastien BALLET <slacker6896 at gmail.com> wrote:
>> Hello,
>>
>> Otherwise, there are zulu-openjdk7/8 slackbuilds to repackage the Azul's
>> Zulu build of OpenJDK 7/8.
>>
>> https://slackbuilds.org/repository/14.2/development/zulu-openjdk7/
>> https://slackbuilds.org/repository/14.2/development/zulu-openjdk8/
>> http://zulu.org/
> 
> Hm. I didn't know those were even there. So basically what I was asking
> about already exists (since June 8 of this year)... but only for x86_64.
> 
> I still might do a 32-bit-only openjdk-bin build. Or call it
> "openjdk-bootstrap", make it the bare minimum needed to build the real
> openjdk. If it's even possible to pare it down any, I mean.
>

I hope we don't go this way. I like the ability to build from source
code. Repackaging binaries from elsewhere has its place but I think we,
as a community, should retain the ability to build everything ourselves.

If we need some binary java package to bootstrap building of subsequent
versions, then let's have a binary that we made ourselves, rather than
one of more or less unknown origin. I mean, who are these zulu.org people?

Looking at:
    http://zulu.org/tcs/
I see that the entity behind zulu,.org is Azul Systems, Inc. and while
it's no crime to be incorporated, what would be any different using
binaries from Zulu compared with accepting binaries from Oracle? At
least Oracle is up front enough to use a .com domain name and don't
pretend to be some touchy feely community driven .org.

Also, I had some difficulty finding their source code or anything to do
with their build system, finally finding:
    https://github.com/zulu-openjdk/zulu-openjdk/issues/3
where it is explained that source code is only available on request.
That's not as "open" as I like things to be.

chris

From Jim.Diamond at acadiau.ca  Fri Jun 23 11:47:14 2017
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Fri, 23 Jun 2017 08:47:14 -0300
Subject: [Slackbuilds-users] possible submission
In-Reply-To: <CAN1hMuCQqttmhvrm_6-CHtmZoJmQF3YPcjZ1rbeqQZyBO3UqPw@mail.gmail.com>
References: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
 <2c27d3ed-29e2-8c16-1d4e-4f64517b3585@iinet.net.au>
 <CAN1hMuCQqttmhvrm_6-CHtmZoJmQF3YPcjZ1rbeqQZyBO3UqPw@mail.gmail.com>
Message-ID: <20170623114714.GA23415@jdiamond-mb.acadiau.ca>

On Fri, Jun 23, 2017 at 01:18 (-0400), B Watson wrote:

> What I don't know (since I haven't paid attention to Java in 10+ years)
> is whether future versions of jdk/openjdk will always be compatible
> with code written for older versions (source code and/or compiled
> classes/jars). Will we get stuck having to still have openjdk version
> 7 in 10 years, because some piece of software written in Java can't be
> compiled or run with openjdk 8 and up?

While I make every effort to avoid Java, there is one program I use
written in Java which I haven't yet managed to expunge from my life.
And every time there is a new version of Java out, I have to spend a
couple of days trying to figure out how to do something in the new
version, because the old version has deprecated methods or some
methods now don't do quite what they used to, or I'm no longer allowed
to call that method in that context, or ...

My point is, I doubt I'm the only one who has this issue.  I suppose
the difference is that most people maintaining Java programs do Java
programming 24/7/365, and so they can amortize this "learn the new
correct one and only way to do it" time over lots more code than I
can.

Meanwhile, my 35-year old C programs happily compile and run with no
whining whatsoever.

Cheers.
                                Jim

From yalhcru at gmail.com  Fri Jun 23 15:27:54 2017
From: yalhcru at gmail.com (B Watson)
Date: Fri, 23 Jun 2017 11:27:54 -0400
Subject: [Slackbuilds-users] possible submission
In-Reply-To: <f734ae7c-70b2-4000-ccea-2dfcd2bf5285@iinet.net.au>
References: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
 <CAA2+phHt-aJ82yWpkRWzqfAQv77WOGDik0uV0doJXL-BUy2b0Q@mail.gmail.com>
 <CAN1hMuAcE2OeodstXihDxxxtv_8qR=M6T0QEG1NMuROA4-ptGg@mail.gmail.com>
 <f734ae7c-70b2-4000-ccea-2dfcd2bf5285@iinet.net.au>
Message-ID: <CAN1hMuAS6nQNMnxDpeMqvWpeFKL4RVaaAe4nHh0wwjqK=vr-BA@mail.gmail.com>

On 6/23/17, Christoph Willing <chris.willing at iinet.net.au> wrote:

> Also, I had some difficulty finding their source code or anything to do
> with their build system, finally finding:
>     https://github.com/zulu-openjdk/zulu-openjdk/issues/3
> where it is explained that source code is only available on request.
> That's not as "open" as I like things to be.

Yes, they seem to have a bizarre definition of "open". Plus, I have to
wonder why they don't just point to the source code our openjdk is built
from (makes me think they've modified it, and if so, what did they do?)

Anyway, licensing and paranoia aside, the zulu stuff is 64-bit only so
it it doesn't really work for what I had in mind.

From slacker6896 at gmail.com  Fri Jun 23 15:42:40 2017
From: slacker6896 at gmail.com (Sebastien BALLET)
Date: Fri, 23 Jun 2017 17:42:40 +0200
Subject: [Slackbuilds-users] possible submission
In-Reply-To: <20170623114714.GA23415@jdiamond-mb.acadiau.ca>
References: <CAN1hMuAoBnBG6o2b=0+scAHkFovAhc8-_RY9U5ZdpBHJy9riPA@mail.gmail.com>
 <2c27d3ed-29e2-8c16-1d4e-4f64517b3585@iinet.net.au>
 <CAN1hMuCQqttmhvrm_6-CHtmZoJmQF3YPcjZ1rbeqQZyBO3UqPw@mail.gmail.com>
 <20170623114714.GA23415@jdiamond-mb.acadiau.ca>
Message-ID: <CAA2+phH2VhNWOSaATgxQ7zNA3bUm9OK2jAU6wktVLN+u4xadQA@mail.gmail.com>

??
?Hello,

old java programs compile and run fine on newer java versions. You just
need to use the right javac options (ie. -source and -bootclasspath) if you
want to recompile old code with a newer compiler.

For instance, if you have a java 6 source code that you want to compile
with java 8, call javac as below :

$ javac -source 1.6 -bootclasspath /path/to/java6/rt.jar /path/to/foo.java

Furthermore, to preserve compatibility with older java runtimes, ?the
?option -target? must be used with -source and -bootclasspath.

For instance, if you have a java 6 source code that you want to compile
with java 8 and want it to be compatible with the JVM 6, 7 and 8, then,
call javac as below :

$ javac -target 1.6 -source 1.6 -bootclasspath /path/to/java6/rt.jar
/path/to/foo.java

-- 
SeB


2017-06-23 13:47 GMT+02:00 Jim Diamond <Jim.Diamond at acadiau.ca>:

> On Fri, Jun 23, 2017 at 01:18 (-0400), B Watson wrote:
>
> > What I don't know (since I haven't paid attention to Java in 10+ years)
> > is whether future versions of jdk/openjdk will always be compatible
> > with code written for older versions (source code and/or compiled
> > classes/jars). Will we get stuck having to still have openjdk version
> > 7 in 10 years, because some piece of software written in Java can't be
> > compiled or run with openjdk 8 and up?
>
> While I make every effort to avoid Java, there is one program I use
> written in Java which I haven't yet managed to expunge from my life.
> And every time there is a new version of Java out, I have to spend a
> couple of days trying to figure out how to do something in the new
> version, because the old version has deprecated methods or some
> methods now don't do quite what they used to, or I'm no longer allowed
> to call that method in that context, or ...
>
> My point is, I doubt I'm the only one who has this issue.  I suppose
> the difference is that most people maintaining Java programs do Java
> programming 24/7/365, and so they can amortize this "learn the new
> correct one and only way to do it" time over lots more code than I
> can.
>
> Meanwhile, my 35-year old C programs happily compile and run with no
> whining whatsoever.
>
> Cheers.
>                                 Jim
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170623/15aac674/attachment.html>

From willysr at slackbuilds.org  Sat Jun 24 02:13:50 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 24 Jun 2017 09:13:50 +0700
Subject: [Slackbuilds-users] Updates - 20170624.1
Message-ID: <a0f74ba3-d792-0b18-d827-b0d7d601ea4e@slackbuilds.org>

Hi folks,

we have several build fixes for -current which is safe for -stable for
this week's update along with opus 1.2, libreoffice 5.3.4 (both binary
repackage or source-based build), qbs 1.8.0, qt-creator 4.3.0, xen
security update, and many other updates.

Sat Jun 24 01:33:39 UTC 2017
academic/karma: Fix library issue.
academic/mpmath: Switch to i586.
academic/pulseview: Updated for version 0.4.0.
academic/scidavis: Updated for version 1.18.
academic/sigrok-cli: Updated for version 0.7.0.
accessibility/espeak: Fix build for -current.
accessibility/xdotool: Minor script tweak.
audio/bristol: Fix build for -current.
audio/foo-yc20: Fix build for -current.
audio/klick: Fix build for -current.
audio/lingot: Fix download URL.
audio/opus: Updated for version 1.2.
audio/sayonara-player: Updated for version 0.9.3 + new maintainer.
audio/sooperlooper: Fix build for -current.
desktop/elementary-xfce: Changed download location and maintainer.
desktop/neofetch: Updated for version 3.2.0.
desktop/wmwebcam: Fix homepage and download.
desktop/xed: Updated for version 1.4.3.
desktop/zuki-themes: Updated for version 3.24.1.
development/Catch: Updated for version 1.9.5.
development/SQLAlchemy: Updated for version 1.1.11.
development/cargo-vendor: Updated for version 0.1.11.
development/f2c: Added (Fortran-to-C converter).
development/henplus: Added (SQL shell).
development/jupyter_client: Updated for version 5.1.0.
development/kotlin: Updated for version 1.1.2_5.
development/ldns: Update md5sum for root-anchors.xml
development/mono-addins: Update HOMEPAGE.
development/p4: Updated for version 2017.1.1511680.
development/p4d: Updated for version 2017.1.1511680.
development/p4v: Updated for version 2017.2.1518788.
development/qbs: Updated for version 1.8.0.
development/qt-creator: Updated for version 4.3.0.
development/sbcl: Updated for version 1.3.18.
development/simavr: Corrected source download url.
development/srcML: Clarify java dependency in the README.
development/watchman: Fix build for -current.
games/adl: Fix build for -current.
games/bstone: Fix build for -current.
games/crack-attack: Added (Multiplayer puzzle game).
games/crispy-doom: Updated for version 4.1.
games/game_1945: Fixed download location.
games/glbsp: Fix build for -current.
games/liquidwar6: Fix build for -current.
games/lutris: Updated for version 0.4.12.
games/oblige-legacy4: Fix build for -current.
games/opentyrian: Fix build for -current.
games/pingus: Fix download location.
games/ppsspp: Updated for version 1.4.2.
games/stella: Fix build for -current.
games/trackballs: Fix build for -current.
games/wmquake: Fix download URL.
games/zoom: Fix build for -current.
gis/gpsbabel: Updated for version 1.5.4, moved from system/.
graphics/LDView: Fixed md5sum.
graphics/dcraw: Updated for version 9.27.0.
graphics/vuescan: Updated for version 9.5.80.
libraries/Botan: Updated for version 2.1.0.
libraries/SDL2: Update HOMEPAGE and DOWNLOAD url.
libraries/SDL2_image: Update HOMEPAGE and DOWNLOAD url.
libraries/SDL2_mixer: Update HOMEPAGE and DOWNLOAD url.
libraries/SDL2_net: Update HOMEPAGE and DOWNLOAD url.
libraries/SDL2_ttf: Update HOMEPAGE and DOWNLOAD url.
libraries/capnproto: Updated for version 0.6.1.
libraries/flatbuffers: Updated for version 1.7.1.
libraries/libbluray: Updated for version 1.0.1
libraries/libgaminggear: Updated for version 0.15.1
libraries/libnfs: Updated for version 2.0.0
libraries/libowfat: Updated for version 0.31.
libraries/libreadline-java: Forced -j1, build bump.
libraries/libsigrok: Updated for version 0.5.0.
libraries/libsigrokdecode: Updated for version 0.5.0.
libraries/liburcu: Updated for version 0.10.0.
libraries/tinyxml2: Updated for version 5.0.0
libraries/vigra: Updated for version 1.11.1.
misc/ibus-unikey: Fixed download location.
misc/ibus: Fixed download location.
misc/sigrok-firmware-fx2lafw: Updated for version 0.1.5.
multimedia/flashplayer-plugin: Updated for version 26.0.0.131.
multimedia/gpac: Updated for version 0.7.1.
multimedia/mkclean: Updated for version 0.8.9.
multimedia/mkvalidator: Updated for version 0.5.1.
multimedia/nted: Fix build for -current.
multimedia/nted: Fix download URL.
multimedia/obs-studio: Updated for version 19.0.3
multimedia/opera-developer-ffmpeg-codecs: Updated for version 60.0.
multimedia/pepperflash-plugin: Updated for version 26.0.0.131.
network/asciinema: Update HOMEPAGE.
network/c-toxcore: Updated for version 0.1.9.
network/deluge: Updated for version 1.3.15
network/fail2ban: Updated for version 0.9.7.
network/ip2location-c: Fixed build.
network/memcached: Updated for version 1.4.37.
network/netqmail: Added (the qmail MTA).
network/nginx: Remove -Werror from CFLAGS
network/offlineimap: Updated for version 7.1.1.
network/onioncat: Updated for version 0.2.2.r578.
network/opera-developer: Updated for version 47.0.2628.0.
network/opera-legacy: Updated for version 12.16.1860.
network/phpmyadmin: Updated for version 4.7.1.
network/sqlmap: Updated for version 1.1.6.
network/swaks: Added (Swiss Army Knife for SMTP).
network/transmission: Fix build for -current.
network/unbound: Updated for version 1.6.3
network/youtube-dl: Updated for version 2017.06.18.
office/LibreOffice: Updated for 5.3.4.2
office/libreoffice-helppack: Updated for version 5.3.4.
office/libreoffice-langpack: Updated for version 5.3.4.
office/libreoffice: Updated for version 5.3.4.
office/mupdf: Fix build for -current.
perl/perl-CPAN-Perl-Releases: Updated for version 3.24.
perl/perl-File-Slurp-Tiny: Added (renamed from perl-Slurp-Tiny).
perl/perl-Slurp-Tiny: Removed (renamed to perl-File-Slurp-Tiny).
perl/perl-Time-Piece: Updated for version 1.32.
perl/perl-tree-dagnode: Updated dep.
python/hyperlink: Added (A featureful, correct URL for Python.).
python/pelican: Updated for version 3.7.1.
python/python-twisted: Updated for version 17.5.0.
python/python3-jupyter_client: Updated for version 5.1.0.
python/python3-ptyprocess: Updated for version 0.5.2.
python/webassets: Updated for version 0.12.1.
ruby/rbenv: Updated for version 1.1.1.
system/Iosevka: Updated for version 1.13.1.
system/avfs: Updated for version 1.0.5.
system/bindfs: Updated for version 1.13.7.
system/cndrvcups-capt: Updated for version 2.71.
system/cndrvcups-common: Updated for version 3.21.
system/csh: Fix build for -current.
system/disk-manager: Updated for version 1.1.1.
system/exfat-utils: Updated for version 1.2.7.
system/fbterm: Fix build for -current.
system/fio: Updated for version 2.21.
system/forkstat: Updated for version 0.01.18.
system/fuse-exfat: Updated for version 1.2.7.
system/gsmartcontrol: Fix MD5SUM.
system/kitchen-sync: Updated for version 0.1.11.
system/noto-emoji: Updated for version git8692845.
system/noto-fonts: Updated for version 20170428.
system/overpass-desktop-fonts: Updated for version 3.0.2.
system/overpass-webfonts: Added (Open Source web fonts by RedHat).
system/rar2fs: Updated for version 1.25.2.
system/rar: Updated for version 5.5.b4.
system/reptyr: Fix build for -current.
system/unicode-character-database: Updated for version 10.0.0.
system/unrar: Updated for version 5.5.5.
system/vifm: Updated for version 0.9.
system/vlock: Fix build for -current.
system/winetricks: Updated for version 20170614.
system/worker: Updated for version 3.10.0.
system/xen: XSA 216-225 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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170624/fe533003/attachment.asc>

From rshepard at appl-ecosys.com  Sat Jun 24 13:21:33 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 24 Jun 2017 06:21:33 -0700 (PDT)
Subject: [Slackbuilds-users] flash plugins
Message-ID: <alpine.LNX.2.11.1706240617310.31940@localhost>

   In Willy's list up upgrades this week are flashplayer-plugin and
pepperflash-pluging. The SBo package descriptions of both are quite brief
and do not distinguish between them. I thought that I read a while ago that
flash was on its way out.

   What, if anything, makes them different? Related question is are there
reasons to select one over the other?

Rich


From willysr at slackbuilds.org  Sat Jun 24 13:40:19 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 24 Jun 2017 20:40:19 +0700
Subject: [Slackbuilds-users] flash plugins
In-Reply-To: <alpine.LNX.2.11.1706240617310.31940@localhost>
References: <alpine.LNX.2.11.1706240617310.31940@localhost>
Message-ID: <c0d06de3-a36e-190b-9b26-e642f4a53726@slackbuilds.org>

>   In Willy's list up upgrades this week are flashplayer-plugin and
> pepperflash-pluging. The SBo package descriptions of both are quite brief
> and do not distinguish between them. I thought that I read a while ago that
> flash was on its way out.
> 
>   What, if anything, makes them different? Related question is are there
> reasons to select one over the other?

pepperflash-plugin => PPAPI-based
flashplayer-plugin => NPAPI-based

Adobe was about to kill Flash Player in the past, but now they decided
to continue developing it so now we have 2 type of flash player based on
their technology


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170624/8e64737f/attachment-0001.asc>

From rshepard at appl-ecosys.com  Sat Jun 24 15:13:52 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 24 Jun 2017 08:13:52 -0700 (PDT)
Subject: [Slackbuilds-users] flash plugins
In-Reply-To: <c0d06de3-a36e-190b-9b26-e642f4a53726@slackbuilds.org>
References: <alpine.LNX.2.11.1706240617310.31940@localhost>
 <c0d06de3-a36e-190b-9b26-e642f4a53726@slackbuilds.org>
Message-ID: <alpine.LNX.2.11.1706240806410.31940@localhost>

On Sat, 24 Jun 2017, Willy Sudiarto Raharjo wrote:

> pepperflash-plugin => PPAPI-based
> flashplayer-plugin => NPAPI-based

Willy,

   My very limited understanding is that each is an interface to displaying
flash videos in a browser, with NPAPI being the older one originally
designed for Netscape.

   I watch very few videos (usually instructional ones) and no movies or TV
shows so I'm not deeply invested in them.

> Adobe was about to kill Flash Player in the past, but now they decided to
> continue developing it so now we have 2 type of flash player based on
> their technology

   Does it matter which I have installed, or if both are installed?

Thanks,

Rich



From willysr at slackbuilds.org  Sat Jun 24 15:20:26 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 24 Jun 2017 22:20:26 +0700
Subject: [Slackbuilds-users] flash plugins
In-Reply-To: <alpine.LNX.2.11.1706240806410.31940@localhost>
References: <alpine.LNX.2.11.1706240617310.31940@localhost>
 <c0d06de3-a36e-190b-9b26-e642f4a53726@slackbuilds.org>
 <alpine.LNX.2.11.1706240806410.31940@localhost>
Message-ID: <e7786dcd-d99c-327f-093c-59719d7487f1@slackbuilds.org>

>   Does it matter which I have installed, or if both are installed?

Both works, but it seems that in the future, Mozilla will mark it
deprecated after Firefox 59, so it would be best to take pepperflash
which is supported in the long term.

References:
https://blog.mozilla.org/futurereleases/2016/07/20/reducing-adobe-flash-usage-in-firefox/
https://www.bleepingcomputer.com/news/software/mozilla-to-drop-support-for-all-npapi-plugins-in-firefox-52-except-flash/


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170624/08b285c0/attachment.asc>

From rshepard at appl-ecosys.com  Sat Jun 24 15:56:32 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 24 Jun 2017 08:56:32 -0700 (PDT)
Subject: [Slackbuilds-users] flash plugins
In-Reply-To: <e7786dcd-d99c-327f-093c-59719d7487f1@slackbuilds.org>
References: <alpine.LNX.2.11.1706240617310.31940@localhost>
 <c0d06de3-a36e-190b-9b26-e642f4a53726@slackbuilds.org>
 <alpine.LNX.2.11.1706240806410.31940@localhost>
 <e7786dcd-d99c-327f-093c-59719d7487f1@slackbuilds.org>
Message-ID: <alpine.LNX.2.11.1706240855430.31940@localhost>

On Sat, 24 Jun 2017, Willy Sudiarto Raharjo wrote:

> Both works, but it seems that in the future, Mozilla will mark it

   flashplayer, I assume.

> ... deprecated after Firefox 59, so it would be best to take pepperflash
> which is supported in the long term.

   Thanks for clarifying.

Carpe weekend,

Rich

From jbernts at broadpark.no  Sat Jun 24 16:57:51 2017
From: jbernts at broadpark.no (Jostein Berntsen)
Date: Sat, 24 Jun 2017 18:57:51 +0200
Subject: [Slackbuilds-users] flash plugins
In-Reply-To: <e7786dcd-d99c-327f-093c-59719d7487f1@slackbuilds.org>
References: <alpine.LNX.2.11.1706240617310.31940@localhost>
 <c0d06de3-a36e-190b-9b26-e642f4a53726@slackbuilds.org>
 <alpine.LNX.2.11.1706240806410.31940@localhost>
 <e7786dcd-d99c-327f-093c-59719d7487f1@slackbuilds.org>
Message-ID: <20170624165751.GA19467@jostein>

On 24.06.17,22:20, Willy Sudiarto Raharjo wrote:
>>   Does it matter which I have installed, or if both are installed?
>
>Both works, but it seems that in the future, Mozilla will mark it
>deprecated after Firefox 59, so it would be best to take pepperflash
>which is supported in the long term.
>

Installing flashplayer-plugin with "sbopkg -i flashplayer-plugin" gives this
error:


###########################################
       New queue process started on:
       l?. 24. juni 18:56:09 +0200 2017
###########################################

+++++++++++++++++++++++++++++++++++++++++++
PRE-CHECK LOG
Using the SBo master git branch
Queue Process:  Download, build, and install

flashplayer-plugin:
  GPG checks not supported for the SBo repository.
  Processing flashplayer-plugin 25.0.0.148-1
  Using original .info file
  Using original SlackBuild file
  No build options selected.

+++++++++++++++++++++++++++++++++++++++++++

Pre-check complete.



Processing flashplayer-plugin

flashplayer-plugin:
flashplayer-plugin not found in /var/cache/sbopkg.
--2017-06-24 18:56:10--  https://fpdownload.adobe.com/get/flashplayer/pdc/25.0.0.148/flash_player_npapi_linux.x86_64.tar.gz
Sl?r opp vertsnavn fpdownload.adobe.com ? 104.123.114.131
Kobler til fpdownload.adobe.com|104.123.114.131|:443 ?tilkoblet.
HTTP-foresp?rsel sendt. Venter p? svar ? 404 Not Found
2017-06-24 18:56:10 PROGRAMFEIL 404: Not Found.



Jostein


From atelszewski at gmail.com  Sat Jun 24 17:09:37 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 24 Jun 2017 19:09:37 +0200
Subject: [Slackbuilds-users] flash plugins
In-Reply-To: <20170624165751.GA19467@jostein>
References: <alpine.LNX.2.11.1706240617310.31940@localhost>
 <c0d06de3-a36e-190b-9b26-e642f4a53726@slackbuilds.org>
 <alpine.LNX.2.11.1706240806410.31940@localhost>
 <e7786dcd-d99c-327f-093c-59719d7487f1@slackbuilds.org>
 <20170624165751.GA19467@jostein>
Message-ID: <b101c0d3-bb3b-46f9-abee-1da3800cc269@gmail.com>

On 24/06/17 18:57, Jostein Berntsen wrote:
> On 24.06.17,22:20, Willy Sudiarto Raharjo wrote:
>>>   Does it matter which I have installed, or if both are installed?
>>
>> Both works, but it seems that in the future, Mozilla will mark it
>> deprecated after Firefox 59, so it would be best to take pepperflash
>> which is supported in the long term.
>>
> 
> Installing flashplayer-plugin with "sbopkg -i flashplayer-plugin" gives 
> this
> error:
> 
> 
> ###########################################
>        New queue process started on:
>        l?. 24. juni 18:56:09 +0200 2017
> ###########################################
> 
> +++++++++++++++++++++++++++++++++++++++++++
> PRE-CHECK LOG
> Using the SBo master git branch
> Queue Process:  Download, build, and install
> 
> flashplayer-plugin:
>   GPG checks not supported for the SBo repository.
>   Processing flashplayer-plugin 25.0.0.148-1
>   Using original .info file
>   Using original SlackBuild file
>   No build options selected.
> 
> +++++++++++++++++++++++++++++++++++++++++++
> 
> Pre-check complete.
> 
> 
> 
> Processing flashplayer-plugin
> 
> flashplayer-plugin:
> flashplayer-plugin not found in /var/cache/sbopkg.
> --2017-06-24 18:56:10--  
> https://fpdownload.adobe.com/get/flashplayer/pdc/25.0.0.148/flash_player_npapi_linux.x86_64.tar.gz 
> 
> Sl?r opp vertsnavn fpdownload.adobe.com ? 104.123.114.131
> Kobler til fpdownload.adobe.com|104.123.114.131|:443 ?tilkoblet.
> HTTP-foresp?rsel sendt. Venter p? svar ? 404 Not Found
> 2017-06-24 18:56:10 PROGRAMFEIL 404: Not Found.
> 

Have you synced your local repo?

-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Sat Jun 24 17:13:02 2017
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 24 Jun 2017 19:13:02 +0200
Subject: [Slackbuilds-users] flash plugins
In-Reply-To: <20170624165751.GA19467@jostein>
References: <alpine.LNX.2.11.1706240617310.31940@localhost>
 <c0d06de3-a36e-190b-9b26-e642f4a53726@slackbuilds.org>
 <alpine.LNX.2.11.1706240806410.31940@localhost>
 <e7786dcd-d99c-327f-093c-59719d7487f1@slackbuilds.org>
 <20170624165751.GA19467@jostein>
Message-ID: <CAPsDuS51OrkkB0OPBNaz-8ccnDD6aV8vCh9cNMMpbLP4CexEjQ@mail.gmail.com>

2017-06-24 18:57 GMT+02:00 Jostein Berntsen <jbernts at broadpark.no>:
> Installing flashplayer-plugin with "sbopkg -i flashplayer-plugin" gives this
> error:
>
>
> ###########################################
>       New queue process started on:
>       l?. 24. juni 18:56:09 +0200 2017
> ###########################################
>
> +++++++++++++++++++++++++++++++++++++++++++
> PRE-CHECK LOG
> Using the SBo master git branch
> Queue Process:  Download, build, and install
>
> flashplayer-plugin:
>  GPG checks not supported for the SBo repository.
>  Processing flashplayer-plugin 25.0.0.148-1
>  Using original .info file
>  Using original SlackBuild file
>  No build options selected.
>
> +++++++++++++++++++++++++++++++++++++++++++
>
> Pre-check complete.
>
>
>
> Processing flashplayer-plugin
>
> flashplayer-plugin:
> flashplayer-plugin not found in /var/cache/sbopkg.
> --2017-06-24 18:56:10--
> https://fpdownload.adobe.com/get/flashplayer/pdc/25.0.0.148/flash_player_npapi_linux.x86_64.tar.gz
> Sl?r opp vertsnavn fpdownload.adobe.com ? 104.123.114.131
> Kobler til fpdownload.adobe.com|104.123.114.131|:443 ?tilkoblet.
> HTTP-foresp?rsel sendt. Venter p? svar ? 404 Not Found
> 2017-06-24 18:56:10 PROGRAMFEIL 404: Not Found.

hi Jostein, seem like you are tracking the master branch but you
haven't updated it: check if these help

https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-May/019127.html

https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-May/019137.html

Matteo

From rshepard at appl-ecosys.com  Sat Jun 24 18:46:43 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 24 Jun 2017 11:46:43 -0700 (PDT)
Subject: [Slackbuilds-users] Upgrading texlive on 14.1
Message-ID: <alpine.LNX.2.11.1706241138250.31940@localhost>

   Until I finish building/installing my new server/workstation I'm running
14.1/x86_i586 on this host. It has texlive-2014 installed (which works OK);
I want to upgrade to texlive-2016 because I use LaTeX/LyX for > 90% of my
writing. I've hit a wall and would like advice.

   Texlive would not build because the poppler library version
(poppler-0.24.3) is too old; it wants a version >= 0.30. It's likely that
the poppler-data version is also too old, but that's not yet been
encountered.

   I downloaded the 14.2 poppler source, build script, and desc. It fails to
complete because of this error:

make[4]: Entering directory /tmp/poppler-0.45.0/qt4/src'
   CXX      libpoppler_qt4_la-poppler-optcontent.lo
In file included from poppler-optcontent.cc:429:0:
poppler-optcontent.moc:13:2: error: #error "This file was generated using
the moc from 4.2.2. It"
  #error "This file was generated using the moc from 4.2.2. It"
   ^
poppler-optcontent.moc:14:2: error: #error "cannot be used with the include
files from this version of Qt."
  #error "cannot be used with the include files from this version of Qt."
   ^
poppler-optcontent.moc:15:2: error: #error "(The moc has changed too much.)"
  #error "(The moc has changed too much.)"
   ^

   Installed here are both qt-4.8.7 and qt5-5.5.1. In poppler.Slackbuild is
the line,
     --enable-poppler-qt4 \
which should find the 4.8.7 version.

   I've no idea where poppler-optcontent.moc originates. Is there a way for
me to correct this error?

TIA,

Rich


From jbernts at broadpark.no  Sat Jun 24 19:53:57 2017
From: jbernts at broadpark.no (Jostein Berntsen)
Date: Sat, 24 Jun 2017 21:53:57 +0200
Subject: [Slackbuilds-users] flash plugins
In-Reply-To: <CAPsDuS51OrkkB0OPBNaz-8ccnDD6aV8vCh9cNMMpbLP4CexEjQ@mail.gmail.com>
References: <alpine.LNX.2.11.1706240617310.31940@localhost>
 <c0d06de3-a36e-190b-9b26-e642f4a53726@slackbuilds.org>
 <alpine.LNX.2.11.1706240806410.31940@localhost>
 <e7786dcd-d99c-327f-093c-59719d7487f1@slackbuilds.org>
 <20170624165751.GA19467@jostein>
 <CAPsDuS51OrkkB0OPBNaz-8ccnDD6aV8vCh9cNMMpbLP4CexEjQ@mail.gmail.com>
Message-ID: <20170624195357.GB19467@jostein>

On 24.06.17,19:13, Matteo Bernardini wrote:
>2017-06-24 18:57 GMT+02:00 Jostein Berntsen <jbernts at broadpark.no>:
>> Installing flashplayer-plugin with "sbopkg -i flashplayer-plugin" gives this
...
>>
>> Processing flashplayer-plugin
>>
>> flashplayer-plugin:
>> flashplayer-plugin not found in /var/cache/sbopkg.
>> --2017-06-24 18:56:10--
>> https://fpdownload.adobe.com/get/flashplayer/pdc/25.0.0.148/flash_player_npapi_linux.x86_64.tar.gz
>> Sl?r opp vertsnavn fpdownload.adobe.com ? 104.123.114.131
>> Kobler til fpdownload.adobe.com|104.123.114.131|:443 ?tilkoblet.
>> HTTP-foresp?rsel sendt. Venter p? svar ? 404 Not Found
>> 2017-06-24 18:56:10 PROGRAMFEIL 404: Not Found.
>
>hi Jostein, seem like you are tracking the master branch but you
>haven't updated it: check if these help
>
>https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-May/019127.html
>
>https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-May/019137.html
>

That works fine, thanks.


Jostein



From slackbuilds at schoepfer.info  Sat Jun 24 20:31:18 2017
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 24 Jun 2017 22:31:18 +0200
Subject: [Slackbuilds-users] Upgrading texlive on 14.1
In-Reply-To: <alpine.LNX.2.11.1706241138250.31940@localhost>
References: <alpine.LNX.2.11.1706241138250.31940@localhost>
Message-ID: <161acec988d9c9c54422e80531e7b359@schoepfer.info>

Hi Rich,

>   Texlive would not build because the poppler library version
> (poppler-0.24.3) is too old; it wants a version >= 0.30. It's likely 
> that
> the poppler-data version is also too old, but that's not yet been
> encountered.

Remove
--with-system-poppler and
--with-system-xpdf (misleading, it has to to with poppler)

from texlive.Slackbuild and build again, leave your system poppler as it 
is.

Johannes

From rshepard at appl-ecosys.com  Sat Jun 24 21:50:10 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 24 Jun 2017 14:50:10 -0700 (PDT)
Subject: [Slackbuilds-users] Upgrading texlive on 14.1
In-Reply-To: <161acec988d9c9c54422e80531e7b359@schoepfer.info>
References: <alpine.LNX.2.11.1706241138250.31940@localhost>
 <161acec988d9c9c54422e80531e7b359@schoepfer.info>
Message-ID: <alpine.LNX.2.11.1706241449490.31940@localhost>

On Sat, 24 Jun 2017, Franzen wrote:

> Remove
> --with-system-poppler and
> --with-system-xpdf (misleading, it has to to with poppler)
> from texlive.Slackbuild and build again, leave your system poppler as it is.

Johannes,

   Thanks very much!

Rich

From atelszewski at gmail.com  Sat Jun 24 23:17:58 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 25 Jun 2017 01:17:58 +0200
Subject: [Slackbuilds-users] Updates - 20170624.1
In-Reply-To: <a0f74ba3-d792-0b18-d827-b0d7d601ea4e@slackbuilds.org>
References: <a0f74ba3-d792-0b18-d827-b0d7d601ea4e@slackbuilds.org>
Message-ID: <436f2d9a-09d9-1697-ca94-e3e3df5b8017@gmail.com>

On 24/06/17 04:13, Willy Sudiarto Raharjo wrote:
> network/youtube-dl: Updated for version 2017.06.18.

This fails for me because our beloved github returns source tarball 
without underscore when going to 
https://github.com/rg3/youtube-dl/archive/2017.06.18/youtube_dl-2017.06.18.tar.gz

i.e. tarball name is "youtube-dl-2017.06.18.tar.gz" and not 
"youtube_dl-2017.06.18.tar.gz"

Although, beware of dog.
Depends on which browser I use.
(And probably on which corner of the room I'm sitting in when downloading).

-- 
Best regards,
Andrzej Telszewski

From rshepard at appl-ecosys.com  Sat Jun 24 23:45:37 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 24 Jun 2017 16:45:37 -0700 (PDT)
Subject: [Slackbuilds-users] ess source code page 404
Message-ID: <alpine.LNX.2.11.1706241644160.31940@localhost>

   Cannot download the latest ess from SBo. Clicking on the source code link
brings up a 404 page not found error from ess.r-project.org.

Rich

From willysr at slackbuilds.org  Sun Jun 25 00:23:30 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 25 Jun 2017 07:23:30 +0700
Subject: [Slackbuilds-users] Updates - 20170624.1
In-Reply-To: <436f2d9a-09d9-1697-ca94-e3e3df5b8017@gmail.com>
References: <a0f74ba3-d792-0b18-d827-b0d7d601ea4e@slackbuilds.org>
 <436f2d9a-09d9-1697-ca94-e3e3df5b8017@gmail.com>
Message-ID: <0fd69937-2a0a-3b56-e25f-64e8981302fe@slackbuilds.org>

>> network/youtube-dl: Updated for version 2017.06.18.
> 
> This fails for me because our beloved github returns source tarball
> without underscore when going to
> https://github.com/rg3/youtube-dl/archive/2017.06.18/youtube_dl-2017.06.18.tar.gz
> 
> 
> i.e. tarball name is "youtube-dl-2017.06.18.tar.gz" and not
> "youtube_dl-2017.06.18.tar.gz"

i just tried to build i t manually and it does build fine
if you look at the SlackBuild, there's a different naming for the source

PRGNAM=youtube-dl
SRCNAM=$(echo $PRGNAM | tr - _)
.
.
tar xvf $CWD/$SRCNAM-$VERSION.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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170625/2e47264d/attachment.asc>

From willysr at slackbuilds.org  Sun Jun 25 00:29:27 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 25 Jun 2017 07:29:27 +0700
Subject: [Slackbuilds-users] ess source code page 404
In-Reply-To: <alpine.LNX.2.11.1706241644160.31940@localhost>
References: <alpine.LNX.2.11.1706241644160.31940@localhost>
Message-ID: <23eb873d-60ee-03c2-1bbf-e23368f8a75a@slackbuilds.org>

>   Cannot download the latest ess from SBo. Clicking on the source code link
> brings up a 404 page not found error from ess.r-project.org.

You can download the source here:
http://ess.r-project.org/downloads/ess/OLD/ess-5.14.tgz

it hasn't been touched for 6 years by the maintainer
anyone is up for this script?

-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170625/e75459bf/attachment.asc>

From rshepard at appl-ecosys.com  Sun Jun 25 00:47:50 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 24 Jun 2017 17:47:50 -0700 (PDT)
Subject: [Slackbuilds-users] ess source code page 404
In-Reply-To: <23eb873d-60ee-03c2-1bbf-e23368f8a75a@slackbuilds.org>
References: <alpine.LNX.2.11.1706241644160.31940@localhost>
 <23eb873d-60ee-03c2-1bbf-e23368f8a75a@slackbuilds.org>
Message-ID: <alpine.LNX.2.11.1706241744050.31940@localhost>

On Sun, 25 Jun 2017, Willy Sudiarto Raharjo wrote:

> You can download the source here:
> http://ess.r-project.org/downloads/ess/OLD/ess-5.14.tgz

   Thanks, Willy.

> it hasn't been touched for 6 years by the maintainer
> anyone is up for this script?

   I downloaded ess on this host (from the ess site) a few years ago.
Some time late last year or early this year I received an e-mail (on the
ess-r mail list) that a new version is in development and they wanted folks
to test it. I've no idea what version is currently installed in emacs or is
assigned to the newer version.

Rich


From andreas.guldstrand at gmail.com  Sun Jun 25 04:18:12 2017
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Sun, 25 Jun 2017 06:18:12 +0200
Subject: [Slackbuilds-users] Updates - 20170624.1
In-Reply-To: <0fd69937-2a0a-3b56-e25f-64e8981302fe@slackbuilds.org>
References: <a0f74ba3-d792-0b18-d827-b0d7d601ea4e@slackbuilds.org>
 <436f2d9a-09d9-1697-ca94-e3e3df5b8017@gmail.com>
 <0fd69937-2a0a-3b56-e25f-64e8981302fe@slackbuilds.org>
Message-ID: <CAEQ5t814mVJX9iMWJrsc0+Atc3atbsU2wU=BDKtwpHeE75kibw@mail.gmail.com>

On 25 June 2017 at 02:23, Willy Sudiarto Raharjo
<willysr at slackbuilds.org> wrote:
>>> network/youtube-dl: Updated for version 2017.06.18.
>>
>> This fails for me because our beloved github returns source tarball
>> without underscore when going to
>> https://github.com/rg3/youtube-dl/archive/2017.06.18/youtube_dl-2017.06.18.tar.gz
>>
>>
>> i.e. tarball name is "youtube-dl-2017.06.18.tar.gz" and not
>> "youtube_dl-2017.06.18.tar.gz"
>
> i just tried to build i t manually and it does build fine
> if you look at the SlackBuild, there's a different naming for the source
>
> PRGNAM=youtube-dl
> SRCNAM=$(echo $PRGNAM | tr - _)
> .
> .
> tar xvf $CWD/$SRCNAM-$VERSION.tar.gz
>

And did you try downloading the tarball with every browser in
existence? It sounds like some browsers may change the _ to a -, and
then the SRCNAM variable will not match it.

From willysr at slackbuilds.org  Sun Jun 25 05:05:57 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 25 Jun 2017 12:05:57 +0700
Subject: [Slackbuilds-users] Updates - 20170624.1
In-Reply-To: <CAEQ5t814mVJX9iMWJrsc0+Atc3atbsU2wU=BDKtwpHeE75kibw@mail.gmail.com>
References: <a0f74ba3-d792-0b18-d827-b0d7d601ea4e@slackbuilds.org>
 <436f2d9a-09d9-1697-ca94-e3e3df5b8017@gmail.com>
 <0fd69937-2a0a-3b56-e25f-64e8981302fe@slackbuilds.org>
 <CAEQ5t814mVJX9iMWJrsc0+Atc3atbsU2wU=BDKtwpHeE75kibw@mail.gmail.com>
Message-ID: <25101c8e-ab73-c3b1-1a53-b1962b7e9eae@slackbuilds.org>

>> PRGNAM=youtube-dl
>> SRCNAM=$(echo $PRGNAM | tr - _)
>> .
>> .
>> tar xvf $CWD/$SRCNAM-$VERSION.tar.gz
>>
> 
> And did you try downloading the tarball with every browser in
> existence? It sounds like some browsers may change the _ to a -, and
> then the SRCNAM variable will not match it.

if it's downloaded with "_", than tar will work without tr
if it's downloaded with "-", tr will convert to _ and tar will get the
results


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170625/c52b2ac2/attachment.asc>

From didier at slint.fr  Sun Jun 25 06:57:57 2017
From: didier at slint.fr (Didier Spaier)
Date: Sun, 25 Jun 2017 08:57:57 +0200
Subject: [Slackbuilds-users] Updates - 20170624.1
In-Reply-To: <CAEQ5t814mVJX9iMWJrsc0+Atc3atbsU2wU=BDKtwpHeE75kibw@mail.gmail.com>
References: <a0f74ba3-d792-0b18-d827-b0d7d601ea4e@slackbuilds.org>
 <436f2d9a-09d9-1697-ca94-e3e3df5b8017@gmail.com>
 <0fd69937-2a0a-3b56-e25f-64e8981302fe@slackbuilds.org>
 <CAEQ5t814mVJX9iMWJrsc0+Atc3atbsU2wU=BDKtwpHeE75kibw@mail.gmail.com>
Message-ID: <7c6f2b37-f5d2-b219-d1e4-80d3aef06b8d@slint.fr>

[quoted lines from Andreas Gudstrand on 25/06/2017 06:18]
> And did you try downloading the tarball with every browser in
> existence? It sounds like some browsers may change the _ to a -, and
> then the SRCNAM variable will not match it.

Use a web browser to download a compressed archive is very bad idea :D

Better use a specialized software like (?)ftp, curl, wget, whatever.

Have a good day,
Didier

From alik at ejik.org  Sun Jun 25 12:34:58 2017
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sun, 25 Jun 2017 15:34:58 +0300
Subject: [Slackbuilds-users] Updates - 20170624.1
In-Reply-To: <436f2d9a-09d9-1697-ca94-e3e3df5b8017@gmail.com>
References: <a0f74ba3-d792-0b18-d827-b0d7d601ea4e@slackbuilds.org>
 <436f2d9a-09d9-1697-ca94-e3e3df5b8017@gmail.com>
Message-ID: <1498394098.8675.1020566640.29559C59@webmail.messagingengine.com>

On Sun, Jun 25, 2017, at 02:17, Andrzej Telszewski wrote:
> On 24/06/17 04:13, Willy Sudiarto Raharjo wrote:
> > network/youtube-dl: Updated for version 2017.06.18.
> 
> This fails for me because our beloved github returns source tarball 
> without underscore when going to 
> https://github.com/rg3/youtube-dl/archive/2017.06.18/youtube_dl-2017.06.18.tar.gz

I also noticed that something changed because after the last update
slackrepo suddenly failed to download youtube-dl.

I changed the default hint MD5SUM="no" to PRAGMA="download_basename" ans
slackrepo succeeded.

Best regards,
Alexander

From andreas.guldstrand at gmail.com  Sun Jun 25 13:48:20 2017
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Sun, 25 Jun 2017 15:48:20 +0200
Subject: [Slackbuilds-users] Updates - 20170624.1
In-Reply-To: <1498394098.8675.1020566640.29559C59@webmail.messagingengine.com>
References: <a0f74ba3-d792-0b18-d827-b0d7d601ea4e@slackbuilds.org>
 <436f2d9a-09d9-1697-ca94-e3e3df5b8017@gmail.com>
 <1498394098.8675.1020566640.29559C59@webmail.messagingengine.com>
Message-ID: <CAEQ5t821a+N0JVvNgA3Sqhg3neD+KmDdGZBkb5qjrD6KHZKUAw@mail.gmail.com>

It seems to me that if the DOWNLOAD URL was changed to
https://github.com/rg3/youtube-dl/archive/2017.06.18/youtube-dl-2017.06.18.tar.gz
instead, there would be no need for the SRCNAM variable, and no
browser would have an issue.

From rshepard at appl-ecosys.com  Sun Jun 25 16:21:57 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 25 Jun 2017 09:21:57 -0700 (PDT)
Subject: [Slackbuilds-users] Descriptive list of packages
Message-ID: <alpine.LNX.2.11.1706250920000.6257@localhost>

   Is there a list of packages with the descriptive contents of their README
files? It would be useful to know what's available since it's difficult to
look for a tool without knowing its name. Has anyone tried extracting this
from the repository?

Rich

From dpross1100 at msn.com  Sun Jun 25 16:45:02 2017
From: dpross1100 at msn.com (Daniel Prosser)
Date: Sun, 25 Jun 2017 16:45:02 +0000
Subject: [Slackbuilds-users] Descriptive list of packages
In-Reply-To: <alpine.LNX.2.11.1706250920000.6257@localhost>
Message-ID: <CO2PR0701MB725FBC8B54DCE597F58E640CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>

If you have mirrored the repo locally you can just use find and grep, ie:

find $REPO_ROOT -maxdepth 3 -mindepth 3 -name "README" | xargs grep -i searchterm

I think some of the SBO package management tools might also have a function built in to search in READMEs. sboui (which I wrote) has it at least.

Dan


On Jun 25, 2017 9:21 AM, Rich Shepard <rshepard at appl-ecosys.com> wrote:

   Is there a list of packages with the descriptive contents of their README
files? It would be useful to know what's available since it's difficult to
look for a tool without knowing its name. Has anyone tried extracting this
from the repository?

Rich
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
http://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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170625/57022dc1/attachment.html>

From rshepard at appl-ecosys.com  Sun Jun 25 17:00:55 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 25 Jun 2017 10:00:55 -0700 (PDT)
Subject: [Slackbuilds-users] Descriptive list of packages
In-Reply-To: <CO2PR0701MB725FBC8B54DCE597F58E640CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>
References: <CO2PR0701MB725FBC8B54DCE597F58E640CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>
Message-ID: <alpine.LNX.2.11.1706250959080.6257@localhost>

On Sun, 25 Jun 2017, Daniel Prosser wrote:

> If you have mirrored the repo locally you can just use find and grep, ie:
> find $REPO_ROOT -maxdepth 3 -mindepth 3 -name "README" | xargs grep -i searchterm

Dan,

   Like a web search, sometimes the term we use is not the term used in the
package so we don't find what we want even if it exists.

> I think some of the SBO package management tools might also have a
> function built in to search in READMEs. sboui (which I wrote) has it at
> least.

   I tried using sbopkg's 'view README' but it dumped me back to the list of
packages.

Thanks for the reply,

Rich

From dpross1100 at msn.com  Sun Jun 25 17:12:16 2017
From: dpross1100 at msn.com (Daniel Prosser)
Date: Sun, 25 Jun 2017 17:12:16 +0000
Subject: [Slackbuilds-users] Descriptive list of packages
In-Reply-To: <alpine.LNX.2.11.1706250959080.6257@localhost>
Message-ID: <CO2PR0701MB725F184882BAF22D44BBBD2CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>

I guess I'm not sure what exactly you're looking for, then. Are you planning to read the entire descriptive list you mentioned? Because unless you plan to read everything, there is always the need to select search terms. And if you don't plan to read the whole thing, then you might as well just search the full READMEs (there would be no reason for the shortened descriptive list).

Dan

On Jun 25, 2017 10:00 AM, Rich Shepard <rshepard at appl-ecosys.com> wrote:

On Sun, 25 Jun 2017, Daniel Prosser wrote:

> If you have mirrored the repo locally you can just use find and grep, ie:
> find $REPO_ROOT -maxdepth 3 -mindepth 3 -name "README" | xargs grep -i searchterm

Dan,

   Like a web search, sometimes the term we use is not the term used in the
package so we don't find what we want even if it exists.

> I think some of the SBO package management tools might also have a
> function built in to search in READMEs. sboui (which I wrote) has it at
> least.

   I tried using sbopkg's 'view README' but it dumped me back to the list of
packages.

Thanks for the reply,

Rich
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
http://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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170625/bd763843/attachment-0001.html>

From atelszewski at gmail.com  Sun Jun 25 17:17:20 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 25 Jun 2017 19:17:20 +0200
Subject: [Slackbuilds-users] Descriptive list of packages
In-Reply-To: <CO2PR0701MB725FBC8B54DCE597F58E640CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>
References: <CO2PR0701MB725FBC8B54DCE597F58E640CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>
Message-ID: <3e7b7331-cd44-2c24-550f-ac9d8874e63d@gmail.com>

On 25/06/17 18:45, Daniel Prosser wrote:
> find $REPO_ROOT -maxdepth 3 -mindepth 3 -name "README" | xargs grep -i 
> searchterm

$ grep searchterm $REPO_ROOT/*/*/README ;-)

-- 
Best regards,
Andrzej Telszewski

From dpross1100 at msn.com  Sun Jun 25 17:20:32 2017
From: dpross1100 at msn.com (Daniel Prosser)
Date: Sun, 25 Jun 2017 17:20:32 +0000
Subject: [Slackbuilds-users] Descriptive list of packages
In-Reply-To: <3e7b7331-cd44-2c24-550f-ac9d8874e63d@gmail.com>
Message-ID: <CO2PR0701MB725ABAF40F2A72CD57B5664CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>

Indeed. Silly me. :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170625/effa7e28/attachment.html>

From atelszewski at gmail.com  Sun Jun 25 17:26:49 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 25 Jun 2017 19:26:49 +0200
Subject: [Slackbuilds-users] Descriptive list of packages
In-Reply-To: <CO2PR0701MB725ABAF40F2A72CD57B5664CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>
References: <CO2PR0701MB725ABAF40F2A72CD57B5664CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>
Message-ID: <089209cc-0ffe-f04e-62d2-c423d1744c80@gmail.com>

On 25/06/17 19:20, Daniel Prosser wrote:
> Indeed. Silly me. :)

There's nothing silly as long as you solve the problem ;-)

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Sun Jun 25 17:36:24 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 26 Jun 2017 00:36:24 +0700
Subject: [Slackbuilds-users] Descriptive list of packages
In-Reply-To: <alpine.LNX.2.11.1706250959080.6257@localhost>
References: <CO2PR0701MB725FBC8B54DCE597F58E640CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>
 <alpine.LNX.2.11.1706250959080.6257@localhost>
Message-ID: <20549b2c-a97b-a1f8-7eec-ee4e200be53d@slackbuilds.org>

>   I tried using sbopkg's 'view README' but it dumped me back to the list of
> packages.

It works fine here both using dialog or CLI (using -R -i option)

-- 
Willy Sudiarto Raharjo

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

From rshepard at appl-ecosys.com  Sun Jun 25 18:02:57 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 25 Jun 2017 11:02:57 -0700 (PDT)
Subject: [Slackbuilds-users] Descriptive list of packages
In-Reply-To: <CO2PR0701MB725F184882BAF22D44BBBD2CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>
References: <CO2PR0701MB725F184882BAF22D44BBBD2CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>
Message-ID: <alpine.LNX.2.11.1706251101030.6257@localhost>

On Sun, 25 Jun 2017, Daniel Prosser wrote:

> I guess I'm not sure what exactly you're looking for...

Dan,

   I'd like to see the desciptions in the README files for packages that
look interesting. I might find something useful that I did not know existed.
The brief one-liners in the queue aren't very descriptive.

Rich

From rshepard at appl-ecosys.com  Sun Jun 25 18:03:28 2017
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 25 Jun 2017 11:03:28 -0700 (PDT)
Subject: [Slackbuilds-users] Descriptive list of packages
In-Reply-To: <20549b2c-a97b-a1f8-7eec-ee4e200be53d@slackbuilds.org>
References: <CO2PR0701MB725FBC8B54DCE597F58E640CCDE0@CO2PR0701MB725.namprd07.prod.outlook.com>
 <alpine.LNX.2.11.1706250959080.6257@localhost>
 <20549b2c-a97b-a1f8-7eec-ee4e200be53d@slackbuilds.org>
Message-ID: <alpine.LNX.2.11.1706251103130.6257@localhost>

On Mon, 26 Jun 2017, Willy Sudiarto Raharjo wrote:

> It works fine here both using dialog or CLI (using -R -i option)

   Thanks, Willy. I'll try again.

Rich

From dn2010 at gmail.com  Mon Jun 26 06:44:54 2017
From: dn2010 at gmail.com (Daniil Bratashov)
Date: Mon, 26 Jun 2017 10:44:54 +0400
Subject: [Slackbuilds-users] intel-microcode should be updated
Message-ID: <CAJ6MA1FgGHEQ6trHkcR4gfMdg5GPSVkFe4QhPGxjhqe+84tMCA@mail.gmail.com>

here is the description of the problem:
https://lists.debian.org/debian-devel/2017/06/msg00308.html

WBR, Daniil Bratashov.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170626/fe9f7d8e/attachment.html>

From andreas.guldstrand at gmail.com  Mon Jun 26 07:02:41 2017
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Mon, 26 Jun 2017 09:02:41 +0200
Subject: [Slackbuilds-users] intel-microcode should be updated
In-Reply-To: <CAJ6MA1FgGHEQ6trHkcR4gfMdg5GPSVkFe4QhPGxjhqe+84tMCA@mail.gmail.com>
References: <CAJ6MA1FgGHEQ6trHkcR4gfMdg5GPSVkFe4QhPGxjhqe+84tMCA@mail.gmail.com>
Message-ID: <CAEQ5t81_ApteffZnVX_oUeTjxsPGrYB5GjtTys3hyax3PB1QMg@mail.gmail.com>

It's already updated. I used the version on SBo several hours ago and
it gave me microcode version 0xba which is a fixed version.

On 26 June 2017 at 08:44, Daniil Bratashov <dn2010 at gmail.com> wrote:
> here is the description of the problem:
> https://lists.debian.org/debian-devel/2017/06/msg00308.html
>
> WBR, Daniil Bratashov.
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

From dn2010 at gmail.com  Mon Jun 26 07:13:20 2017
From: dn2010 at gmail.com (Daniil Bratashov)
Date: Mon, 26 Jun 2017 11:13:20 +0400
Subject: [Slackbuilds-users] intel-microcode should be updated
In-Reply-To: <CAEQ5t81_ApteffZnVX_oUeTjxsPGrYB5GjtTys3hyax3PB1QMg@mail.gmail.com>
References: <CAJ6MA1FgGHEQ6trHkcR4gfMdg5GPSVkFe4QhPGxjhqe+84tMCA@mail.gmail.com>
 <CAEQ5t81_ApteffZnVX_oUeTjxsPGrYB5GjtTys3hyax3PB1QMg@mail.gmail.com>
Message-ID: <CAJ6MA1GDBYWJFLn6iNh-2B=AqMMddM_49fqtCHezeAn89FA74w@mail.gmail.com>

Yes, sorry for misleading information.

WBR, Daniil Bratashov.

On Mon, Jun 26, 2017 at 11:02 AM, Andreas Guldstrand <
andreas.guldstrand at gmail.com> wrote:

> It's already updated. I used the version on SBo several hours ago and
> it gave me microcode version 0xba which is a fixed version.
>
> On 26 June 2017 at 08:44, Daniil Bratashov <dn2010 at gmail.com> wrote:
> > here is the description of the problem:
> > https://lists.debian.org/debian-devel/2017/06/msg00308.html
> >
> > WBR, Daniil Bratashov.
> >
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> >
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170626/7dd37d89/attachment-0001.html>

From bocke at slackware-srbija.org  Mon Jun 26 13:59:18 2017
From: bocke at slackware-srbija.org (Bojan =?UTF-8?B?UG9wb3ZpxIc=?=)
Date: Mon, 26 Jun 2017 15:59:18 +0200
Subject: [Slackbuilds-users] Anyone interested in PyGame SlackBuild?
Message-ID: <20170626155918.4c15c611@malac.universe.local>

Hi everyone.

I'm not able to keep PyGame SlackBuild up to date. As I got some
queries about it, I tough it might be better to offer it to someone who
is using it actively or whose SlackBuild scripts depend on PyGame and
who will be able to keep up with the updates.

If none is interested I don't mind maintaining it further, but you will
have to cope with sparse updates. I test it once in a while, but I
can't really keep up with every update as I don't use it actively
anymore.

Cheers,

Bojan.

From d.zlatanidis at gmail.com  Mon Jun 26 16:55:47 2017
From: d.zlatanidis at gmail.com (Dimitris Zlatanidis)
Date: Mon, 26 Jun 2017 18:55:47 +0200
Subject: [Slackbuilds-users] Anyone interested in PyGame SlackBuild?
In-Reply-To: <20170626155918.4c15c611@malac.universe.local>
References: <20170626155918.4c15c611@malac.universe.local>
Message-ID: <CAP-+ARHA+OH-Th0m1XS=GAtEF1ekgPOqzBmgzRjbLZ9zBFdOeA@mail.gmail.com>

Yes, I am here please.

On Jun 26, 2017 15:53, "Bojan Popovi?" <bocke at slackware-srbija.org> wrote:

> Hi everyone.
>
> I'm not able to keep PyGame SlackBuild up to date. As I got some
> queries about it, I tough it might be better to offer it to someone who
> is using it actively or whose SlackBuild scripts depend on PyGame and
> who will be able to keep up with the updates.
>
> If none is interested I don't mind maintaining it further, but you will
> have to cope with sparse updates. I test it once in a while, but I
> can't really keep up with every update as I don't use it actively
> anymore.
>
> Cheers,
>
> Bojan.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170626/4203f094/attachment.html>

From bocke at slackware-srbija.org  Mon Jun 26 18:46:23 2017
From: bocke at slackware-srbija.org (Bojan =?UTF-8?B?UG9wb3ZpxIc=?=)
Date: Mon, 26 Jun 2017 20:46:23 +0200
Subject: [Slackbuilds-users] Anyone interested in PyGame SlackBuild?
In-Reply-To: <CAP-+ARHA+OH-Th0m1XS=GAtEF1ekgPOqzBmgzRjbLZ9zBFdOeA@mail.gmail.com>
References: <20170626155918.4c15c611@malac.universe.local>
 <CAP-+ARHA+OH-Th0m1XS=GAtEF1ekgPOqzBmgzRjbLZ9zBFdOeA@mail.gmail.com>
Message-ID: <20170626204623.12e2e252@malac.universe.local>

On Mon, 26 Jun 2017 18:55:47 +0200
Dimitris Zlatanidis <d.zlatanidis at gmail.com> wrote:

Deal. :) Admins, please note the change.

Cheers,

Bojan.


> Yes, I am here please.
> 

From tvbare at gmail.com  Mon Jun 26 19:47:39 2017
From: tvbare at gmail.com (Terry)
Date: Mon, 26 Jun 2017 14:47:39 -0500
Subject: [Slackbuilds-users] Portmidi build fails
Message-ID: <939c6d40-b98c-8862-e3ca-acbaa5c266bf@gmail.com>

Trying to build portmidi fails with the following:

[ 85%] Building C object 
pm_dylib/CMakeFiles/portmidi-dynamic.dir/__/porttime/ptlinux.c.o
[ 87%] Building C object 
pm_dylib/CMakeFiles/portmidi-dynamic.dir/__/pm_common/pmutil.c.o
[ 90%] Building C object 
pm_dylib/CMakeFiles/portmidi-dynamic.dir/__/pm_common/portmidi.c.o
[ 92%] Linking C shared library ../Release/libportmidi.so
[ 92%] Built target portmidi-dynamic
Scanning dependencies of target pmdefaults_target
[ 95%] Generating pmdefaults/PmDefaults.class
/bin/sh: javac: command not found
pm_java/CMakeFiles/pmdefaults_target.dir/build.make:75: recipe for 
target 'pm_java/pmdefaults/PmDefaults.class' failed
make[2]: *** [pm_java/pmdefaults/PmDefaults.class] Error 127
CMakeFiles/Makefile2:562: recipe for target 
'pm_java/CMakeFiles/pmdefaults_target.dir/all' failed
make[1]: *** [pm_java/CMakeFiles/pmdefaults_target.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

Can anyone shed some light on the error messages? Although I've used 
slack since
'95 with Slack 3.0, I'm a relative newbie to slackbuilds.

-- 
     Terry "Hoots"

          To stay young, never lose your sense of wonder.


                              *****
              My main photo gallery can be seen at:
            <URL:http://www.flickr.com/photos/tvbare/>

               I also keep a secondary gallery at:
<URL:http://www.facebook.com/pages/Osage-Plains-Images/300412117042>

                              *****


From willysr at slackbuilds.org  Mon Jun 26 19:54:26 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 27 Jun 2017 02:54:26 +0700
Subject: [Slackbuilds-users] Portmidi build fails
In-Reply-To: <939c6d40-b98c-8862-e3ca-acbaa5c266bf@gmail.com>
References: <939c6d40-b98c-8862-e3ca-acbaa5c266bf@gmail.com>
Message-ID: <6d066f0f-615c-d2e1-ebca-401da7e4fd20@slackbuilds.org>

> /bin/sh: javac: command not found

Either you don't have jdk or openjdk installed or you haven't logged out
and logged in again to get the new environment set up


-- 
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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170627/0544d947/attachment.asc>

From tvbare at gmail.com  Mon Jun 26 20:25:40 2017
From: tvbare at gmail.com (Terry)
Date: Mon, 26 Jun 2017 15:25:40 -0500
Subject: [Slackbuilds-users] Portmidi build fails
In-Reply-To: <6d066f0f-615c-d2e1-ebca-401da7e4fd20@slackbuilds.org>
References: <939c6d40-b98c-8862-e3ca-acbaa5c266bf@gmail.com>
 <6d066f0f-615c-d2e1-ebca-401da7e4fd20@slackbuilds.org>
Message-ID: <d6808ebb-7532-b317-8965-87990ac6b0f7@gmail.com>



On 06/26/2017 02:54 PM, Willy Sudiarto Raharjo wrote:
>> /bin/sh: javac: command not found
> Either you don't have jdk or openjdk installed or you haven't logged out
> and logged in again to get the new environment set up
>
>

Perfect! Thank you.

-- 
     Terry "Hoots"

          To stay young, never lose your sense of wonder.


                              *****
              My main photo gallery can be seen at:
            <URL:http://www.flickr.com/photos/tvbare/>

               I also keep a secondary gallery at:
<URL:http://www.facebook.com/pages/Osage-Plains-Images/300412117042>

                              *****


From kjhambrick at gmail.com  Mon Jun 26 22:25:26 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Mon, 26 Jun 2017 17:25:26 -0500
Subject: [Slackbuilds-users] intel-microcode.SlackBuild - slight mod to save
 releasenotes
Message-ID: <CANBHt+NqNSLKXsmM4Sxmw5FDnjFFY3edTm2JNJk7RJV6sgpwEA@mail.gmail.com>

Andrzej --

Attached is a patch for your intel-microcode.SlaclBuild so that it saves
the releasenotes file into /usr/docs/intel-microcode-$VERSION/

Might be handy to have after installing.

Thanks for your work !

I just used your SlackBuild to upgrade the ucode in my SkyLake 6700K !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170626/7c20ed18/attachment-0001.html>
-------------- next part --------------
--- intel-microcode.SlackBuild.orig	2017-05-26 21:11:54.595291790 -0500
+++ intel-microcode.SlackBuild	2017-06-26 17:17:38.165611080 -0500
@@ -44,8 +44,8 @@
 mkdir $SRCNAM-$VERSION
 tar xvf $CWD/$SRCNAM-$VERSION.tgz -C $SRCNAM-$VERSION
 cd $SRCNAM-$VERSION
-chown root:root microcode.dat
-chmod 0644      microcode.dat
+chown root:root microcode.dat releasenote
+chmod 0644      microcode.dat releasenote
 
 mkdir -p $PKG/lib/firmware
 cp -a microcode.dat $PKG/lib/firmware
@@ -58,6 +58,7 @@
 fi
 
 mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
+cp -p releasenote $PKG/usr/doc/$PRGNAM-$VERSION
 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
 
 mkdir -p $PKG/install

From fernando.lopezjr at gmail.com  Mon Jun 26 22:40:21 2017
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Mon, 26 Jun 2017 16:40:21 -0600
Subject: [Slackbuilds-users] help getting to run this program.
Message-ID: <CALrQ46DzATb0mpVrADpbfj98AhGEqtb0CLZF_NgTdB8+4=p-Mw@mail.gmail.com>

I would like to run this program it is the controller software for Ubiquity
UniFi AC HD(Model: *UAP-AC-HD*).

Problem is when I install the generated tarball I get this errors:

*bash-4.4# *ls
ubnt-apttool  unifi.init  wizard_api_sh
*bash-4.4# *./unifi.init
./unifi.init: line 91: /lib/lsb/init-functions: No such file or directory
./unifi.init: line 145: [: too many arguments
./unifi.init: line 175: /lib/lsb/init-functions: No such file or directory
./unifi.init: line 242: log_success_msg: command not found
*bash-4.4# *./wizard_api_sh
./wizard_api_sh: line 3: return: can only `return' from a function or
sourced script
/api/cmd/sitemgr
{"cmd":"add-default-admin","name":"","email":"","ubic_uuid":"","x_password":""}
failed:

I believe I have to run the server which is "*unifi.init*" then access the
supplied web pages. I don't think deb2tgz did a good job converting the
tarball.

So, any ideas on how to run this?

Thank you!



*You can download from official page:*
https://www.ubnt.com/download/unifi/unifi-ap-ac-hd/uapachd/unifi-5416-controller-debianubuntu-linux

*or alternate download:*
https://www.dropbox.com/s/vw004kxzzqrw9yz/unifi_sysvinit_all.deb?dl=0

*and the converted deb2tgz tarball:*
https://www.dropbox.com/s/jxtudxt1tx0lotf/unifi_sysvinit_all.txz?dl=0

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170626/6235ec13/attachment.html>

From atelszewski at gmail.com  Mon Jun 26 22:49:12 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 27 Jun 2017 00:49:12 +0200
Subject: [Slackbuilds-users] help getting to run this program.
In-Reply-To: <CALrQ46DzATb0mpVrADpbfj98AhGEqtb0CLZF_NgTdB8+4=p-Mw@mail.gmail.com>
References: <CALrQ46DzATb0mpVrADpbfj98AhGEqtb0CLZF_NgTdB8+4=p-Mw@mail.gmail.com>
Message-ID: <195d0490-530d-9edd-2482-ac2d76140ae6@gmail.com>

On 27/06/17 00:40, Fernando Lopez wrote:
> I would like to run this program it is the controller software for 
> Ubiquity UniFi AC HD(Model: *UAP-AC-HD*).
> 
> Problem is when I install the generated tarball I get this errors:
> 
> *bash-4.4# *ls
> ubnt-apttool  unifi.init  wizard_api_sh
> *bash-4.4# *./unifi.init
> ./unifi.init: line 91: /lib/lsb/init-functions: No such file or directory
> ./unifi.init: line 145: [: too many arguments
> ./unifi.init: line 175: /lib/lsb/init-functions: No such file or directory
> ./unifi.init: line 242: log_success_msg: command not found
> *bash-4.4# *./wizard_api_sh
> ./wizard_api_sh: line 3: return: can only `return' from a function or 
> sourced script
> /api/cmd/sitemgr 
> {"cmd":"add-default-admin","name":"","email":"","ubic_uuid":"","x_password":""} 
> failed:
> 
> I believe I have to run the server which is "*unifi.init*" then access 
> the supplied web pages. I don't think deb2tgz did a good job converting 
> the tarball.
> 
> So, any ideas on how to run this?
> 
> Thank you!
> 
> 
> 
> *You can download from official page:*
> https://www.ubnt.com/download/unifi/unifi-ap-ac-hd/uapachd/unifi-5416-controller-debianubuntu-linux
> 
> *or alternate download:*
> https://www.dropbox.com/s/vw004kxzzqrw9yz/unifi_sysvinit_all.deb?dl=0
> 
> *and the converted deb2tgz tarball:*
> https://www.dropbox.com/s/jxtudxt1tx0lotf/unifi_sysvinit_all.txz?dl=0
> 
> -- 
> 
> ------------
> Regards,
>      Fernando Lopez Jr.
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

Fernando, I suggest you go to LinuxQuestions.org
Although you might receive help here, it's not the most appropriate 
place for such a conversation.

-- 
Best regards,
Andrzej Telszewski

From rworkman at slackbuilds.org  Tue Jun 27 22:07:43 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 27 Jun 2017 17:07:43 -0500
Subject: [Slackbuilds-users] SBo services reboot today
Message-ID: <20170627170743.7e88562b@home.rlworkman.net>

We'll be rebooting the SBo host server at some point today
to come back up on a new non-stack-clashing kernel.

http, ftp, rsync, and git will be offline during this reboot.
Mailing lists will still be accessible, although that 
server will also need a reboot soon. We'll do them one at
a time...

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170627/2ace17db/attachment.asc>

From rworkman at slackbuilds.org  Tue Jun 27 22:38:46 2017
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 27 Jun 2017 17:38:46 -0500
Subject: [Slackbuilds-users] SBo services reboot today
In-Reply-To: <20170627170743.7e88562b@home.rlworkman.net>
References: <20170627170743.7e88562b@home.rlworkman.net>
Message-ID: <20170627173846.3d9c76e6@home.rlworkman.net>

On Tue, 27 Jun 2017 17:07:43 -0500
Robby Workman <rworkman at slackbuilds.org> wrote:

> We'll be rebooting the SBo host server at some point today
> to come back up on a new non-stack-clashing kernel.
> 
> http, ftp, rsync, and git will be offline during this reboot.
> Mailing lists will still be accessible, although that 
> server will also need a reboot soon. We'll do them one at
> a time...


Back up and hopefully we'll have a long time before another
reboot is required.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170627/75dab4ba/attachment.asc>

From jgraha8 at gmail.com  Wed Jun 28 03:31:39 2017
From: jgraha8 at gmail.com (Jason Graham)
Date: Tue, 27 Jun 2017 23:31:39 -0400
Subject: [Slackbuilds-users] hdf5: source link changed
Message-ID: <CALDF-3x0uCaxiLop5L04a9r=qVugv1c-6_MFaiSLk0wcXre=2g@mail.gmail.com>

Hi,

Looks like source file for hdf5 has been moved to:

https://support.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8/hdf5-1.8.15-patch1/src/hdf5-1.8.15-patch1.tar.bz2

The current SBo link is therefore broken.

Kind regards,
Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170627/225728f1/attachment.html>

From willysr at slackbuilds.org  Wed Jun 28 04:04:52 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 28 Jun 2017 11:04:52 +0700
Subject: [Slackbuilds-users] hdf5: source link changed
In-Reply-To: <CALDF-3x0uCaxiLop5L04a9r=qVugv1c-6_MFaiSLk0wcXre=2g@mail.gmail.com>
References: <CALDF-3x0uCaxiLop5L04a9r=qVugv1c-6_MFaiSLk0wcXre=2g@mail.gmail.com>
Message-ID: <06650a0a-1ad1-1cef-da15-43cc255f4b30@slackbuilds.org>

> Looks like source file for hdf5 has been moved to:
> 
> https://support.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8/hdf5-1.8.15-patch1/src/hdf5-1.8.15-patch1.tar.bz2
> 
> The current SBo link is therefore broken.

Done in my branch and in SBo link

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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170628/35ea1142/attachment.asc>

From atelszewski at gmail.com  Thu Jun 29 21:46:21 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 29 Jun 2017 23:46:21 +0200
Subject: [Slackbuilds-users] intel-microcode.SlackBuild - slight mod to
 save releasenotes
In-Reply-To: <CANBHt+NqNSLKXsmM4Sxmw5FDnjFFY3edTm2JNJk7RJV6sgpwEA@mail.gmail.com>
References: <CANBHt+NqNSLKXsmM4Sxmw5FDnjFFY3edTm2JNJk7RJV6sgpwEA@mail.gmail.com>
Message-ID: <ea979097-3d31-c47d-7312-01d033f17401@gmail.com>

On 27/06/17 00:25, Konrad J Hambrick wrote:
> Andrzej --
> 
> Attached is a patch for your intel-microcode.SlaclBuild so that it saves 
> the releasenotes file into /usr/docs/intel-microcode-$VERSION/
> 
> Might be handy to have after installing.
> 
> Thanks for your work !
> 
> I just used your SlackBuild to upgrade the ucode in my SkyLake 6700K !
> 
> -- kjh

Now in the pending queue.

-- 
Best regards,
Andrzej Telszewski

From edps.mundognu at gmail.com  Thu Jun 29 21:56:27 2017
From: edps.mundognu at gmail.com (Edinaldo)
Date: Thu, 29 Jun 2017 18:56:27 -0300
Subject: [Slackbuilds-users] nero-aac source is down
Message-ID: <op.y2l68d009z09aw@localhost>


Hi guys,

The sources for script nero-aac is down:

http://ftp6.nero.com/tools/NeroDigitalAudio.zip

I found the same sources only in sboarch:

http://slackware.uk/sbosrcarch/by-md5/4/3/432921e8d59028abe8f5549d9f99b3bc/NeroDigitalAudio.zip

Cheers,

Edinaldo

From edps.mundognu at gmail.com  Thu Jun 29 01:52:20 2017
From: edps.mundognu at gmail.com (Edinaldo)
Date: Wed, 28 Jun 2017 22:52:20 -0300
Subject: [Slackbuilds-users] link for nero-aac is down
Message-ID: <op.y2knhiqb9z09aw@localhost>

Hi guys,

The link for sources of the script nero-aac is down:

http://ftp6.nero.com/tools/NeroDigitalAudio.zip

I found the same sources only in sboarch:

http://slackware.uk/sbosrcarch/by-md5/4/3/432921e8d59028abe8f5549d9f99b3bc/NeroDigitalAudio.zip

Cheers,

Edinaldo

From kjhambrick at gmail.com  Thu Jun 29 22:19:14 2017
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Thu, 29 Jun 2017 17:19:14 -0500
Subject: [Slackbuilds-users] intel-microcode.SlackBuild - slight mod to
 save releasenotes
In-Reply-To: <ea979097-3d31-c47d-7312-01d033f17401@gmail.com>
References: <CANBHt+NqNSLKXsmM4Sxmw5FDnjFFY3edTm2JNJk7RJV6sgpwEA@mail.gmail.com>
 <ea979097-3d31-c47d-7312-01d033f17401@gmail.com>
Message-ID: <CANBHt+O-tgWZ7Jf-oumDuh2HTrpc1B5fp9yt01gK1mn0xpbE-Q@mail.gmail.com>

Thank you Andrzej !

I REALLY do appreciate all that you do for SBo and SlackWare !

-- kjh

On Thu, Jun 29, 2017 at 4:46 PM, Andrzej Telszewski <atelszewski at gmail.com>
wrote:

> On 27/06/17 00:25, Konrad J Hambrick wrote:
>
>> Andrzej --
>>
>> Attached is a patch for your intel-microcode.SlaclBuild so that it saves
>> the releasenotes file into /usr/docs/intel-microcode-$VERSION/
>>
>> Might be handy to have after installing.
>>
>> Thanks for your work !
>>
>> I just used your SlackBuild to upgrade the ucode in my SkyLake 6700K !
>>
>> -- kjh
>>
>
> Now in the pending queue.
>
> --
> Best regards,
> Andrzej Telszewski
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170629/8e0712e5/attachment.html>

From z.coldplayer at gmail.com  Wed Jun 28 16:27:58 2017
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Wed, 28 Jun 2017 20:27:58 +0400
Subject: [Slackbuilds-users] SBo services reboot today
In-Reply-To: <20170627173846.3d9c76e6@home.rlworkman.net>
References: <20170627170743.7e88562b@home.rlworkman.net>
 <20170627173846.3d9c76e6@home.rlworkman.net>
Message-ID: <CAEWL1_80OKPSakZ+S=dt6QqKkMDZrC+Bihh2X7yhXnuDAnVVzw@mail.gmail.com>

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

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

Rsync with the SBo repository for Slackware 14.1 complete.

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

***SYNC COMPLETE***

Slackbuilds works fine on my systems


On 28 June 2017 at 02:38, Robby Workman <rworkman at slackbuilds.org> wrote:

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

From willysr at slackbuilds.org  Fri Jun 30 01:17:17 2017
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 30 Jun 2017 08:17:17 +0700
Subject: [Slackbuilds-users] nero-aac source is down
In-Reply-To: <op.y2l68d009z09aw@localhost>
References: <op.y2l68d009z09aw@localhost>
Message-ID: <a0131392-6c35-dc85-9811-775475e171ba@slackbuilds.org>

On 06/30/2017 04:56 AM, Edinaldo wrote:
> 
> Hi guys,
> 
> The sources for script nero-aac is down:
> 
> http://ftp6.nero.com/tools/NeroDigitalAudio.zip
> 
> I found the same sources only in sboarch:
> 
> http://slackware.uk/sbosrcarch/by-md5/4/3/432921e8d59028abe8f5549d9f99b3bc/NeroDigitalAudio.zip

Fixed

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: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170630/1b16f20c/attachment.asc>

From atelszewski at gmail.com  Fri Jun 30 13:25:10 2017
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Fri, 30 Jun 2017 15:25:10 +0200
Subject: [Slackbuilds-users] Updates - 20170624.1
In-Reply-To: <0fd69937-2a0a-3b56-e25f-64e8981302fe@slackbuilds.org>
References: <a0f74ba3-d792-0b18-d827-b0d7d601ea4e@slackbuilds.org>
 <436f2d9a-09d9-1697-ca94-e3e3df5b8017@gmail.com>
 <0fd69937-2a0a-3b56-e25f-64e8981302fe@slackbuilds.org>
Message-ID: <13a3535a-ff22-c822-ec63-41f920cade06@gmail.com>

On 25/06/17 02:23, Willy Sudiarto Raharjo wrote:
>>> network/youtube-dl: Updated for version 2017.06.18.
>>
>> This fails for me because our beloved github returns source tarball
>> without underscore when going to
>> https://github.com/rg3/youtube-dl/archive/2017.06.18/youtube_dl-2017.06.18.tar.gz
>>
>>
>> i.e. tarball name is "youtube-dl-2017.06.18.tar.gz" and not
>> "youtube_dl-2017.06.18.tar.gz"
> 
> i just tried to build i t manually and it does build fine
> if you look at the SlackBuild, there's a different naming for the source
> 
> PRGNAM=youtube-dl
> SRCNAM=$(echo $PRGNAM | tr - _)
> .
> .
> tar xvf $CWD/$SRCNAM-$VERSION.tar.gz
> 
> 

Aha, I finally managed to understand the problem ;-)

If the file is saved as "youtube-dl-2017.06.18.tar.gz", which is my 
case, then:
SRCNAM=$(echo $PRGNAM | tr - _)

will make the SRCNAM to be "youtube_dl", but the file in the 
*filesystem* is still named "youtube-dl".

(Bcc'd maintainer).

-- 
Best regards,
Andrzej Telszewski

From yalhcru at gmail.com  Fri Jun 30 21:30:32 2017
From: yalhcru at gmail.com (B Watson)
Date: Fri, 30 Jun 2017 17:30:32 -0400
Subject: [Slackbuilds-users] link for nero-aac is down
In-Reply-To: <op.y2knhiqb9z09aw@localhost>
References: <op.y2knhiqb9z09aw@localhost>
Message-ID: <CAN1hMuCw_W6NPR7a3_TXj3ACM0rQfPQFyeLrBc21nuoXkg9seA@mail.gmail.com>

On 6/28/17, Edinaldo <edps.mundognu at gmail.com> wrote:
> I found the same sources only in sboarch:
>
> http://slackware.uk/sbosrcarch/by-md5/4/3/432921e8d59028abe8f5549d9f99b3bc/NeroDigitalAudio.zip

It's better to use non-sbosrcarch links when possible. Try this:

http://files.dddload.net/download/85bf41d0278fe597b5bea2f0a756ba6f/tIUqhjw/encode/NeroDigitalAudio.zip

Not sure how stable that link is though. See if it still works tomorrow
or next week?