From kingbeowulf at gmail.com  Sun May  1 03:19:26 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 30 Apr 2016 20:19:26 -0700
Subject: [Slackbuilds-users]  14.2RC2 Update/fixes for nvidia 361.42
Message-ID: <d057053e-584a-96f1-cec4-c0308764f6f5@gmail.com>

nvidia-{driver | kernel} updated to 361.42

This update for 14.2RC2 is provides improvements and bugfixes; as well
as fixing failures when compiling certain programs such as wine-1.8.2

Also, nvidia-installer now compiles ok. It is not needed for this
packages but I can add it back if enough people require it.  Please
email me off list.

(fast) http://www.koenigcomputers.com/sbo-testing/
(slow) http://www.linuxgalaxy.org/files/sbo-testing/

Also, I am unable to test if this update can be back ported to 14.1. As
always test and bug reports welcome.

-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/20160430/e71c66ca/attachment.asc>

From matteo.bernardini at gmail.com  Sun May  1 09:01:07 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 1 May 2016 11:01:07 +0200
Subject: [Slackbuilds-users] 14.2RC2 Update/fixes for nvidia 361.42
In-Reply-To: <d057053e-584a-96f1-cec4-c0308764f6f5@gmail.com>
References: <d057053e-584a-96f1-cec4-c0308764f6f5@gmail.com>
Message-ID: <CAPsDuS4X=Q2hL4JAGPASVh3yxP_1r73v6d0ttNMcfzW2TfvNaw@mail.gmail.com>

2016-05-01 5:19 GMT+02:00 King Beowulf <kingbeowulf at gmail.com>:
> nvidia-{driver | kernel} updated to 361.42
>
> This update for 14.2RC2 is provides improvements and bugfixes; as well
> as fixing failures when compiling certain programs such as wine-1.8.2
>
> Also, nvidia-installer now compiles ok. It is not needed for this
> packages but I can add it back if enough people require it.  Please
> email me off list.
>
> (fast) http://www.koenigcomputers.com/sbo-testing/
> (slow) http://www.linuxgalaxy.org/files/sbo-testing/
>
> Also, I am unable to test if this update can be back ported to 14.1. As
> always test and bug reports welcome.

Hi Edward,

I applied this to my branch (for 14.2) in our git.
I just changed at the bottom applying of the additional "multi": as
BUILD should be a digit, I prepended the string to TAG, but the effect
should be exactly the same.
be sure to base future modifications on the version we have in our repository.

Matteo

From baildon.research at googlemail.com  Sun May  1 12:46:31 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 1 May 2016 13:46:31 +0100
Subject: [Slackbuilds-users] 14.2RC2 Update/fixes for nvidia 361.42
In-Reply-To: <CAPsDuS4X=Q2hL4JAGPASVh3yxP_1r73v6d0ttNMcfzW2TfvNaw@mail.gmail.com>
References: <d057053e-584a-96f1-cec4-c0308764f6f5@gmail.com>
 <CAPsDuS4X=Q2hL4JAGPASVh3yxP_1r73v6d0ttNMcfzW2TfvNaw@mail.gmail.com>
Message-ID: <CAMt7G9TLeSyDw7wPuAx=S62HCemE_AQPW00aBM20Twtr2PoQWg@mail.gmail.com>

> BUILD should be a digit, I prepended the string to TAG, but the effect
> should be exactly the same.

Ewwwwwwwww
Nothing else does that, and it potentially breaks slackpkg+
How about ${VERSION}_multi ?

Cheers
-D.

From matteo.bernardini at gmail.com  Sun May  1 15:45:50 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 1 May 2016 17:45:50 +0200
Subject: [Slackbuilds-users] 14.2RC2 Update/fixes for nvidia 361.42
In-Reply-To: <CAMt7G9TLeSyDw7wPuAx=S62HCemE_AQPW00aBM20Twtr2PoQWg@mail.gmail.com>
References: <d057053e-584a-96f1-cec4-c0308764f6f5@gmail.com>
 <CAPsDuS4X=Q2hL4JAGPASVh3yxP_1r73v6d0ttNMcfzW2TfvNaw@mail.gmail.com>
 <CAMt7G9TLeSyDw7wPuAx=S62HCemE_AQPW00aBM20Twtr2PoQWg@mail.gmail.com>
Message-ID: <CAPsDuS47+2mss6=AytKmzV1qpEAcC0PDGtT-W33TvVW-PhBWCA@mail.gmail.com>

2016-05-01 14:46 GMT+02:00 David Spencer <baildon.research at googlemail.com>:
>> BUILD should be a digit, I prepended the string to TAG, but the effect
>> should be exactly the same.
>
> Ewwwwwwwww
> Nothing else does that, and it potentially breaks slackpkg+
> How about ${VERSION}_multi ?

for me it's ok also added to $VERSION: what do you think about it, Edward?

Matteo

From matteo.bernardini at gmail.com  Sun May  1 16:05:31 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 1 May 2016 18:05:31 +0200
Subject: [Slackbuilds-users] 14.2RC2 Update/fixes for nvidia 361.42
In-Reply-To: <CAPsDuS47+2mss6=AytKmzV1qpEAcC0PDGtT-W33TvVW-PhBWCA@mail.gmail.com>
References: <d057053e-584a-96f1-cec4-c0308764f6f5@gmail.com>
 <CAPsDuS4X=Q2hL4JAGPASVh3yxP_1r73v6d0ttNMcfzW2TfvNaw@mail.gmail.com>
 <CAMt7G9TLeSyDw7wPuAx=S62HCemE_AQPW00aBM20Twtr2PoQWg@mail.gmail.com>
 <CAPsDuS47+2mss6=AytKmzV1qpEAcC0PDGtT-W33TvVW-PhBWCA@mail.gmail.com>
Message-ID: <CAPsDuS662mjzx6tEiHD+wDu94pfNu9_FMKTM445F+jOjN_D1Pg@mail.gmail.com>

2016-05-01 17:45 GMT+02:00 Matteo Bernardini <matteo.bernardini at gmail.com>:
> 2016-05-01 14:46 GMT+02:00 David Spencer <baildon.research at googlemail.com>:
>>> BUILD should be a digit, I prepended the string to TAG, but the effect
>>> should be exactly the same.
>>
>> Ewwwwwwwww
>> Nothing else does that, and it potentially breaks slackpkg+
>> How about ${VERSION}_multi ?
>
> for me it's ok also added to $VERSION: what do you think about it, Edward?

well, thinking about it a little bit more, potentially any build tool
could possibily have any kind of issue if we pass the build script
some variables and they are changed inside the SlackBuild.
using this as example TAG (or VERSION) has a value before the
SlackBuild is run but the package has a name using a different TAG (or
VERSION) at the end...
taking in account this my vote is to avoid completely altering the
variables values inside of the SlackBuild.

Matteo

P.S. while I was writing this it has come to mind that ffmpeg does
this for the ARCH field and, as for my experience, seems to be safe...

From baildon.research at googlemail.com  Sun May  1 16:39:11 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 1 May 2016 17:39:11 +0100
Subject: [Slackbuilds-users] 14.2RC2 Update/fixes for nvidia 361.42
In-Reply-To: <CAPsDuS662mjzx6tEiHD+wDu94pfNu9_FMKTM445F+jOjN_D1Pg@mail.gmail.com>
References: <d057053e-584a-96f1-cec4-c0308764f6f5@gmail.com>
 <CAPsDuS4X=Q2hL4JAGPASVh3yxP_1r73v6d0ttNMcfzW2TfvNaw@mail.gmail.com>
 <CAMt7G9TLeSyDw7wPuAx=S62HCemE_AQPW00aBM20Twtr2PoQWg@mail.gmail.com>
 <CAPsDuS47+2mss6=AytKmzV1qpEAcC0PDGtT-W33TvVW-PhBWCA@mail.gmail.com>
 <CAPsDuS662mjzx6tEiHD+wDu94pfNu9_FMKTM445F+jOjN_D1Pg@mail.gmail.com>
Message-ID: <CAMt7G9QbD=bVYHEjUFPg00XuX762q678WA2K9u4GgLDdD=U1gQ@mail.gmail.com>

> using this as example TAG (or VERSION) has a value before the
> SlackBuild is run but the package has a name using a different TAG (or
> VERSION) at the end...
> taking in account this my vote is to avoid completely altering the
> variables values inside of the SlackBuild.
>
> Matteo
>
> P.S. while I was writing this it has come to mind that ffmpeg does
> this for the ARCH field and, as for my experience, seems to be safe...

Well... packages that build kernel modules add the kernel version onto
$VERSION (e.g. nvidia_kernel), also some packages add the locale name
onto $VERSION (e.g. libreoffice-langpack)

ffmpeg with $ARCH_custom breaks slackpkg+, I'd be happy to see'
_custom' removed, but ffmpeg was using '_custom' for years before
slackpkg+ was invented .... it's Heinz's decision, however I seem to
remember that the reason for _custom is not so important any more?

Sorry to make this unneccessarily difficult :-/
-D.

From matteo.bernardini at gmail.com  Sun May  1 16:53:56 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 1 May 2016 18:53:56 +0200
Subject: [Slackbuilds-users] 14.2RC2 Update/fixes for nvidia 361.42
In-Reply-To: <CAMt7G9QbD=bVYHEjUFPg00XuX762q678WA2K9u4GgLDdD=U1gQ@mail.gmail.com>
References: <d057053e-584a-96f1-cec4-c0308764f6f5@gmail.com>
 <CAPsDuS4X=Q2hL4JAGPASVh3yxP_1r73v6d0ttNMcfzW2TfvNaw@mail.gmail.com>
 <CAMt7G9TLeSyDw7wPuAx=S62HCemE_AQPW00aBM20Twtr2PoQWg@mail.gmail.com>
 <CAPsDuS47+2mss6=AytKmzV1qpEAcC0PDGtT-W33TvVW-PhBWCA@mail.gmail.com>
 <CAPsDuS662mjzx6tEiHD+wDu94pfNu9_FMKTM445F+jOjN_D1Pg@mail.gmail.com>
 <CAMt7G9QbD=bVYHEjUFPg00XuX762q678WA2K9u4GgLDdD=U1gQ@mail.gmail.com>
Message-ID: <CAPsDuS4f52zMupQW=SmFK1sxpuGcnZReG2k9LxDf0e6erNZiEg@mail.gmail.com>

2016-05-01 18:39 GMT+02:00 David Spencer <baildon.research at googlemail.com>:
>> using this as example TAG (or VERSION) has a value before the
>> SlackBuild is run but the package has a name using a different TAG (or
>> VERSION) at the end...
>> taking in account this my vote is to avoid completely altering the
>> variables values inside of the SlackBuild.
>>
>> Matteo
>>
>> P.S. while I was writing this it has come to mind that ffmpeg does
>> this for the ARCH field and, as for my experience, seems to be safe...
>
> Well... packages that build kernel modules add the kernel version onto
> $VERSION (e.g. nvidia_kernel), also some packages add the locale name
> onto $VERSION (e.g. libreoffice-langpack)
>
> ffmpeg with $ARCH_custom breaks slackpkg+, I'd be happy to see'
> _custom' removed, but ffmpeg was using '_custom' for years before
> slackpkg+ was invented .... it's Heinz's decision, however I seem to
> remember that the reason for _custom is not so important any more?
>
> Sorry to make this unneccessarily difficult :-/

no, the discussion is interesting. :)

so, I'm ok going with adding "_multi" to the VERSION variable and I'll
commit that in the meantime, waiting for someone else to comment on
this.

Matteo

From kingbeowulf at gmail.com  Sun May  1 18:21:43 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 1 May 2016 11:21:43 -0700
Subject: [Slackbuilds-users] 14.2RC2 Update/fixes for nvidia 361.42
In-Reply-To: <CAPsDuS4f52zMupQW=SmFK1sxpuGcnZReG2k9LxDf0e6erNZiEg@mail.gmail.com>
References: <d057053e-584a-96f1-cec4-c0308764f6f5@gmail.com>
 <CAPsDuS4X=Q2hL4JAGPASVh3yxP_1r73v6d0ttNMcfzW2TfvNaw@mail.gmail.com>
 <CAMt7G9TLeSyDw7wPuAx=S62HCemE_AQPW00aBM20Twtr2PoQWg@mail.gmail.com>
 <CAPsDuS47+2mss6=AytKmzV1qpEAcC0PDGtT-W33TvVW-PhBWCA@mail.gmail.com>
 <CAPsDuS662mjzx6tEiHD+wDu94pfNu9_FMKTM445F+jOjN_D1Pg@mail.gmail.com>
 <CAMt7G9QbD=bVYHEjUFPg00XuX762q678WA2K9u4GgLDdD=U1gQ@mail.gmail.com>
 <CAPsDuS4f52zMupQW=SmFK1sxpuGcnZReG2k9LxDf0e6erNZiEg@mail.gmail.com>
Message-ID: <c0914005-23f9-f13a-ba1a-c90cb5231b6d@gmail.com>

On 05/01/2016 09:53 AM, Matteo Bernardini wrote:
> 2016-05-01 18:39 GMT+02:00 David Spencer <baildon.research at googlemail.com>:
>>> using this as example TAG (or VERSION) has a value before the
>>> SlackBuild is run but the package has a name using a different TAG (or
>>> VERSION) at the end...
>>> taking in account this my vote is to avoid completely altering the
>>> variables values inside of the SlackBuild.
>>>
>>> Matteo
>>>
>>> P.S. while I was writing this it has come to mind that ffmpeg does
>>> this for the ARCH field and, as for my experience, seems to be safe...
>>
>> Well... packages that build kernel modules add the kernel version onto
>> $VERSION (e.g. nvidia_kernel), also some packages add the locale name
>> onto $VERSION (e.g. libreoffice-langpack)
>>
>> ffmpeg with $ARCH_custom breaks slackpkg+, I'd be happy to see'
>> _custom' removed, but ffmpeg was using '_custom' for years before
>> slackpkg+ was invented .... it's Heinz's decision, however I seem to
>> remember that the reason for _custom is not so important any more?
>>
>> Sorry to make this unneccessarily difficult :-/
> 
> no, the discussion is interesting. :)
> 
> so, I'm ok going with adding "_multi" to the VERSION variable and I'll
> commit that in the meantime, waiting for someone else to comment on
> this.
> 
> Matteo

Either way is OK by me.  I didn't think about slackpkg+ breakage...Until
14.2 goes stable, I'm not using slackpkg+ and am also limiting slackpkg
use.  I also don't use sbopkg.  I was just thinking I needed to tag the
2 possible nvidia-driver versions (pure 64-bit and multilib/compat32)
since I ended up getting confused as to which package I was testing
here. I agree that we should try to do this in the most compatible way
as possible.

I was also thinking it might be time to separate out the COMPAT32 bits
into a separate package, akin to what Alien Bob does with his multilib
packages.  Its been a bit tedious to keep up with changes.

If you look at Alien Bob's multilib packages, for core system he uses:

$PRGNAM-$VERSION_mulilib-x84_64-$BUILD$TAG

and for the COMPAT32 converted files:

$PRGNAM-compat32-$VERSION-x86_64-$BUILD$TAG

with TAG in this case = compat32

This, at least here, was completely compatible with slackpkg/slackpkg+

-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/20160501/e443358b/attachment.asc>

From baildon.research at googlemail.com  Sun May  1 18:49:17 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 1 May 2016 19:49:17 +0100
Subject: [Slackbuilds-users] 14.2RC2 Update/fixes for nvidia 361.42
In-Reply-To: <c0914005-23f9-f13a-ba1a-c90cb5231b6d@gmail.com>
References: <d057053e-584a-96f1-cec4-c0308764f6f5@gmail.com>
 <CAPsDuS4X=Q2hL4JAGPASVh3yxP_1r73v6d0ttNMcfzW2TfvNaw@mail.gmail.com>
 <CAMt7G9TLeSyDw7wPuAx=S62HCemE_AQPW00aBM20Twtr2PoQWg@mail.gmail.com>
 <CAPsDuS47+2mss6=AytKmzV1qpEAcC0PDGtT-W33TvVW-PhBWCA@mail.gmail.com>
 <CAPsDuS662mjzx6tEiHD+wDu94pfNu9_FMKTM445F+jOjN_D1Pg@mail.gmail.com>
 <CAMt7G9QbD=bVYHEjUFPg00XuX762q678WA2K9u4GgLDdD=U1gQ@mail.gmail.com>
 <CAPsDuS4f52zMupQW=SmFK1sxpuGcnZReG2k9LxDf0e6erNZiEg@mail.gmail.com>
 <c0914005-23f9-f13a-ba1a-c90cb5231b6d@gmail.com>
Message-ID: <CAMt7G9Rf7Gxd0gmEif5qhZUz3wnN7+JvOYrjbqEfjA2+bNboPQ@mail.gmail.com>

> This, at least here, was completely compatible with slackpkg/slackpkg+

I should have been more specific (sorry!), I was thinking of
TAG_PRIORITY, which isn't set by default, but using it has saved my
sanity ... well, arguably saved my sanity.

[The ARCH_custom on ffmpeg is a different problem -- slackpkg+ just
doesn't see ffmpeg because the ARCH is 'special'.]

-D.

From matteo.bernardini at gmail.com  Tue May  3 08:08:56 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 3 May 2016 10:08:56 +0200
Subject: [Slackbuilds-users] Vivaldi
Message-ID: <CAPsDuS5PkGkv2mPjpsD-zUfHWFY2nr4oUgoixXZAJdiqapEyqg@mail.gmail.com>

It has been reported on LQ that the download link for vivaldi is broken

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

I had a look at the directory where the vivaldi people publish their
releases and concluded that they often remove old ones, breaking the
scripts in our repository.

so I had prepared a patch in my branch to:
- self host their tarballs avoiding breakage;
- move from snapshots to the stable release (seems it's more up2date
than the snapshots ;) ).

https://slackbuilds.org/cgit/slackbuilds/commit/?h=ponce-for-14.2&id=13031fffc0af538e73e9a6919a4d44aca5e89525

Matteo

From philip at vanderhoeven.org  Wed May  4 14:27:22 2016
From: philip at vanderhoeven.org (=?utf-8?Q?Philip_van_der_Hoeven?=)
Date: Wed, 4 May 2016 16:27:22 +0200
Subject: [Slackbuilds-users] Android-tools slackbuild
Message-ID: <zarafa.572a06ca.773d.6736fdc513f20b1a@zarafa.vd-hoeven.nl>

?Hi,



Did I understood correctly that updates for Slackware 14.2 should be sent to this mailing list ?

If so, attached is a patch for android-tools, if not please ignore the noise ;-)



Regards,

Philip



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160504/2aefcb32/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: android-tools.patch.gz
Type: application/x-targz
Size: 3801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160504/2aefcb32/attachment.bin>

From brent at exitstatusone.com  Wed May  4 18:00:02 2016
From: brent at exitstatusone.com (Brenton Earl)
Date: Wed, 4 May 2016 12:00:02 -0600
Subject: [Slackbuilds-users] heroku-client, bad dowload link
Message-ID: <7ad5476b-1817-95b9-1c35-ba126117fb80@exitstatusone.com>

Hello,

The heroku-client download url points to a tarball that is not updated
wit version information.  The md5 checksum fails due to this.

Maybe the tarball needs to be hosted on the Slackbuilds direct links
sourceforge page?  heroku-client may also need to be updated, but I did
not test any of this.

(https://s3.amazonaws.com/assets.heroku.com/heroku-client/heroku-client.tgz)

I found the tarball that is referred to in the SlackBuild on sbosrcarch,
here:

(http://slackware.uk/sbosrcarch/by-md5/6/6/66a50258f7d479ec0a12490794572534/heroku-client.tgz)

Thanks,
-- 
Brenton Earl

-------------- 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/20160504/9007e4c8/attachment-0001.asc>

From willysr at slackbuilds.org  Thu May  5 02:12:57 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 5 May 2016 09:12:57 +0700
Subject: [Slackbuilds-users] Android-tools slackbuild
In-Reply-To: <zarafa.572a06ca.773d.6736fdc513f20b1a@zarafa.vd-hoeven.nl>
References: <zarafa.572a06ca.773d.6736fdc513f20b1a@zarafa.vd-hoeven.nl>
Message-ID: <a44ccfbb-9eac-9ea3-57e1-01264d7aafcb@slackbuilds.org>

> Did I understood correctly that updates for Slackware 14.2 should be sent to this mailing list ?
> 
> If so, attached is a patch for android-tools, if not please ignore the noise ;-)

Applied in my branch

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/20160505/a9582c76/attachment.asc>

From willysr at slackbuilds.org  Thu May  5 02:18:17 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 5 May 2016 09:18:17 +0700
Subject: [Slackbuilds-users] heroku-client, bad dowload link
In-Reply-To: <7ad5476b-1817-95b9-1c35-ba126117fb80@exitstatusone.com>
References: <7ad5476b-1817-95b9-1c35-ba126117fb80@exitstatusone.com>
Message-ID: <ccc9f197-be7b-4f33-eb61-364754798c00@slackbuilds.org>

> The heroku-client download url points to a tarball that is not updated
> wit version information.  The md5 checksum fails due to this.
> 
> Maybe the tarball needs to be hosted on the Slackbuilds direct links
> sourceforge page?  heroku-client may also need to be updated, but I did
> not test any of this.
> 
> (https://s3.amazonaws.com/assets.heroku.com/heroku-client/heroku-client.tgz)
> 
> I found the tarball that is referred to in the SlackBuild on sbosrcarch,
> here:
> 
> (http://slackware.uk/sbosrcarch/by-md5/6/6/66a50258f7d479ec0a12490794572534/heroku-client.tgz)

Fixed in 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/20160505/cae92e8d/attachment.asc>

From philip at vanderhoeven.org  Thu May  5 08:18:09 2016
From: philip at vanderhoeven.org (=?utf-8?Q?Philip_van_der_Hoeven?=)
Date: Thu, 5 May 2016 10:18:09 +0200
Subject: [Slackbuilds-users] Android-tools slackbuild
Message-ID: <zarafa.572b01c1.34dc.0173110f16a442e3@zarafa.vd-hoeven.nl>

?



-----Original message-----
From: Willy Sudiarto Raharjo?<willysr at slackbuilds.org>
Sent: Thursday 5th May 2016 4:13
To: slackbuilds-users at slackbuilds.org
Subject: Re: [Slackbuilds-users] Android-tools slackbuild


> Did I understood correctly that updates for Slackware 14.2 should be sent to this mailing list ?
> 
> If so, attached is a patch for android-tools, if not please ignore the noise ;-)

Applied in my branch

Thanks


-- 
Willy Sudiarto Raharjo

?Thanks,



Here are some more for 14.2: openmsx and openmsx-catapult 0.12



Philip


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160505/5607cd68/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openmsx.patch.gz
Type: application/x-gzip
Size: 704 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160505/5607cd68/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openmsx-catapult.patch.gz
Type: application/x-gzip
Size: 829 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160505/5607cd68/attachment-0001.bin>

From philip at vanderhoeven.org  Thu May  5 13:13:36 2016
From: philip at vanderhoeven.org (=?utf-8?Q?Philip_van_der_Hoeven?=)
Date: Thu, 5 May 2016 15:13:36 +0200
Subject: [Slackbuilds-users] Android-tools slackbuild
In-Reply-To: <zarafa.572b01c1.34dc.0173110f16a442e3@zarafa.vd-hoeven.nl>
References: <zarafa.572b01c1.34dc.0173110f16a442e3@zarafa.vd-hoeven.nl>
Message-ID: <zarafa.572b4700.45e3.03badbcc4bc850f9@zarafa.vd-hoeven.nl>

?

-----Original message-----
From: Philip van der Hoeven?<philip at vanderhoeven.org>
Sent: Thursday 5th May 2016 11:47
To: SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
Subject: Re: [Slackbuilds-users] Android-tools slackbuild

?



-----Original message-----
From: Willy Sudiarto Raharjo?<willysr at slackbuilds.org>
Sent: Thursday 5th May 2016 4:13
To: slackbuilds-users at slackbuilds.org
Subject: Re: [Slackbuilds-users] Android-tools slackbuild


> Did I understood correctly that updates for Slackware 14.2 should be sent to this mailing list ?
> 
> If so, attached is a patch for android-tools, if not please ignore the noise ;-)

Applied in my branch

Thanks


-- 
Willy Sudiarto Raharjo

?Thanks,



Here are some more for 14.2: openmsx and openmsx-catapult 0.12



Philip

?Last ones for today:

LDraw_data and leocad_pieces



Philip





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160505/038e0ef2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: LDraw_data.patch.gz
Type: application/x-targz
Size: 659 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160505/038e0ef2/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: leocad_pieces.patch.gz
Type: application/x-targz
Size: 725 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160505/038e0ef2/attachment-0003.bin>

From willysr at slackbuilds.org  Thu May  5 16:54:03 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 5 May 2016 23:54:03 +0700
Subject: [Slackbuilds-users] Android-tools slackbuild
In-Reply-To: <zarafa.572b01c1.34dc.0173110f16a442e3@zarafa.vd-hoeven.nl>
References: <zarafa.572b01c1.34dc.0173110f16a442e3@zarafa.vd-hoeven.nl>
Message-ID: <fccab20d-7fb6-6ba1-ec4a-5318536ac02c@slackbuilds.org>

Philip,


I applied openmsx, openmsx-catapult 0.12, and LDraw_data without any
changes, but for leocad_pieces, i had to change a little bit due to
download URL is not a permanent, so i download manually and host it in
SBoDirectLinks


-- 
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/20160505/ff780fc8/attachment.asc>

From roger.krowiak at gmail.com  Thu May  5 18:39:33 2016
From: roger.krowiak at gmail.com (Roger Krowiak)
Date: Thu, 5 May 2016 20:39:33 +0200
Subject: [Slackbuilds-users] Broken link report
Message-ID: <CAGpsf_G57ax0U1a+on0HmywrwKp_COuLZCODpK7YxmD0yVyr5Q@mail.gmail.com>

Hello,

I would like to report a broken link, which prevent me from building a
package. On JDK page
https://slackbuilds.org/repository/14.1/development/jdk/ there is a link to
source:
https://download.oracle.com/otn-pub/java/jdk/8u66-b17/jdk-8u66-linux-i586.tar.gz
which is no longer valid.

Is this a right place to report this problem?


Thank you for your answer.
-- 
twitter: @SlavoFreso <https://twitter.com/SlavoFreso>
facebook: Slavomir Freso <http://www.facebook.com/roger.krowiak>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160505/fb78c447/attachment.html>

From philip at vanderhoeven.org  Thu May  5 19:23:31 2016
From: philip at vanderhoeven.org (=?utf-8?Q?Philip_van_der_Hoeven?=)
Date: Thu, 5 May 2016 21:23:31 +0200
Subject: [Slackbuilds-users] Android-tools slackbuild
In-Reply-To: <fccab20d-7fb6-6ba1-ec4a-5318536ac02c@slackbuilds.org>
References: <zarafa.572b01c1.34dc.0173110f16a442e3@zarafa.vd-hoeven.nl> 
 <fccab20d-7fb6-6ba1-ec4a-5318536ac02c@slackbuilds.org>
Message-ID: <zarafa.572b9db3.5aa9.0ed61f9600219028@zarafa.vd-hoeven.nl>

?

-----Original message-----
From: Willy Sudiarto Raharjo?<willysr at slackbuilds.org>
Sent: Thursday 5th May 2016 18:54
To: slackbuilds-users at slackbuilds.org
Subject: Re: [Slackbuilds-users] Android-tools slackbuild


Philip,


I applied openmsx, openmsx-catapult 0.12, and LDraw_data without any
changes, but for leocad_pieces, i had to change a little bit due to
download URL is not a permanent, so i download manually and host it in
SBoDirectLinks

?That's great, thanks !



Philip



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

From hadack at gmx.de  Thu May  5 18:47:09 2016
From: hadack at gmx.de (hadack at gmx.de)
Date: Thu, 5 May 2016 20:47:09 +0200
Subject: [Slackbuilds-users] Commit "network/copy: Removed (discontinued per
 May 1)." updates webkit2gtk
Message-ID: <20160505204709.2b5c77bc@schuttler>


Hi, 

I just noticed that this commit on the master branch also updates the
webkit2gtk version. Should be a seperate commit i guess?

Cheers, hadack

From willysr at slackbuilds.org  Thu May  5 19:28:51 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 6 May 2016 02:28:51 +0700
Subject: [Slackbuilds-users] Commit "network/copy: Removed (discontinued
 per May 1)." updates webkit2gtk
In-Reply-To: <20160505204709.2b5c77bc@schuttler>
References: <20160505204709.2b5c77bc@schuttler>
Message-ID: <e4ecde0b-c07d-905a-18f6-23a55e094cfd@slackbuilds.org>

> I just noticed that this commit on the master branch also updates the
> webkit2gtk version. Should be a seperate commit i guess?

Yes, it should be
it was my fault. I was in process of updating webkit2gtk and then i got
an email from copy that they discountinued their services. Got a little
distracted and didn't check the commit changes before pushing it to master.

since master should not be redo or rewritten, we leave it as it is

i will try to make sure such things doesn't happening again in the future

-- 
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/20160506/9cf0ab36/attachment.asc>

From willysr at slackbuilds.org  Thu May  5 19:32:23 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 6 May 2016 02:32:23 +0700
Subject: [Slackbuilds-users] Broken link report
In-Reply-To: <CAGpsf_G57ax0U1a+on0HmywrwKp_COuLZCODpK7YxmD0yVyr5Q@mail.gmail.com>
References: <CAGpsf_G57ax0U1a+on0HmywrwKp_COuLZCODpK7YxmD0yVyr5Q@mail.gmail.com>
Message-ID: <e4360b87-486e-7f53-c3c3-971dfdcb6149@slackbuilds.org>

> I would like to report a broken link, which prevent me from building a
> package. On JDK page
> https://slackbuilds.org/repository/14.1/development/jdk/ there is a link to
> source:
> https://download.oracle.com/otn-pub/java/jdk/8u66-b17/jdk-8u66-linux-i586.tar.gz
> which is no longer valid.
> 
> Is this a right place to report this problem?

jdk is already updated in master to 8u92

Other than that, the source must be downloaded manually via browser. You
can't use wget or any other tool since you must agree to Oracle's
agreement and for that, you need to click on a radio button on their
website.


-- 
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/20160506/c59984fa/attachment.asc>

From philip at vanderhoeven.org  Mon May  9 18:01:02 2016
From: philip at vanderhoeven.org (=?utf-8?Q?Philip_van_der_Hoeven?=)
Date: Mon, 9 May 2016 20:01:02 +0200
Subject: [Slackbuilds-users] Updates for 14.2
Message-ID: <zarafa.5730d05e.1bf2.7fd9728538505368@zarafa.vd-hoeven.nl>

?Hi,



Here are some more updates for 14.2:

- freerdp is updated to git master version as recommended by the developers.

- remmina is updated to the next git branch as recommended by the developers. It doesn't want to compile without vte3 so this is not optional anymore.

- sabnzbd updated to 1.0.2



Also I got permission from Marco Bonetti to take over pidgin-sipe which is updated to 1.21.0



Philip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160509/02194534/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: freerdp.patch.gz
Type: application/gzip
Size: 2507 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160509/02194534/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pidgin-sipe.patch.gz
Type: application/gzip
Size: 837 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160509/02194534/attachment-0005.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: remmina.patch.gz
Type: application/gzip
Size: 2358 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160509/02194534/attachment-0006.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sabnzbd.patch.gz
Type: application/gzip
Size: 566 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160509/02194534/attachment-0007.bin>

From willysr at slackbuilds.org  Tue May 10 00:57:57 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 10 May 2016 07:57:57 +0700
Subject: [Slackbuilds-users] Updates for 14.2
In-Reply-To: <zarafa.5730d05e.1bf2.7fd9728538505368@zarafa.vd-hoeven.nl>
References: <zarafa.5730d05e.1bf2.7fd9728538505368@zarafa.vd-hoeven.nl>
Message-ID: <04cbb756-4db2-c90c-a558-a11706d5407e@slackbuilds.org>

> Here are some more updates for 14.2:
> 
> - freerdp is updated to git master version as recommended by the
> developers.
> 
> - remmina is updated to the next git branch as recommended by the
> developers. It doesn't want to compile without vte3 so this is not
> optional anymore.
> 
> - sabnzbd updated to 1.0.2
> 
> Also I got permission from Marco Bonetti to take over pidgin-sipe
> which is updated to 1.21.0

All applied in my branch

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/20160510/7f484ee4/attachment.asc>

From atelszewski at gmail.com  Wed May 11 16:58:20 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 11 May 2016 18:58:20 +0200
Subject: [Slackbuilds-users] qt5 build 3 fails to build
Message-ID: <f13f23d9-f0ca-4420-95dd-8c63c5a70875@gmail.com>

Hi,

qt5 fails to build. I'm on -current as of Wed May 11 05:20:01 UTC 2016.
The error is very similar or identical to the previous one, regarding NSS.
Am I missing something obvious? :)

Error message follows:

ninja: Entering directory 
`/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core/Release'
[10/10262] CC 
obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o
FAILED: /usr/bin/gcc -MMD -MF 
obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o.d 
-DV8_DEPRECATION_WARNINGS -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 
-DNO_TCMALLOC -DCHROMIUM_BUILD -DTOOLKIT_VIEWS=1 
-DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 
-DUSE_DEFAULT_RENDER_THEME=1 -DUSE_LIBJPEG_TURBO=1 -DUSE_X11=1 
-DENABLE_ONE_CLICK_SIGNIN -DENABLE_PRE_SYNC_BACKUP -DUSE_XI2_MT=2 
-DENABLE_REMOTING=1 -DENABLE_WEBRTC=1 -DENABLE_PEPPER_CDMS 
-DENABLE_CONFIGURATION_POLICY -DENABLE_NOTIFICATIONS -DUSE_UDEV 
-DDONT_EMBED_BUILD_METADATA -DENABLE_TASK_MANAGER=1 
-DENABLE_EXTENSIONS=1 -DENABLE_PLUGINS=1 -DENABLE_SESSION_SERVICE=1 
-DENABLE_THEMES=1 -DENABLE_AUTOFILL_DIALOG=1 -DENABLE_BACKGROUND=1 
-DENABLE_GOOGLE_NOW=1 -DCLD_VERSION=2 -DCLD2_DATA_SOURCE=static 
-DENABLE_PRINTING=1 -DENABLE_BASIC_PRINTING=1 -DENABLE_PRINT_PREVIEW=1 
-DENABLE_SPELLCHECK=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 
-DENABLE_APP_LIST=1 -DENABLE_SETTINGS_APP=1 -DENABLE_MANAGED_USERS=1 
-DENABLE_MDNS=1 -DENABLE_SERVICE_DISCOVERY=1 
-DENABLE_LOAD_COMPLETION_HACKS=1 -DNO_PKCS11_BYPASS -DNSS_ENABLE_ECC 
-DUSE_UTIL_DIRECTLY -DUSE_LIBPCI=1 -DUSE_GLIB=1 -DUSE_NSS=1 -DNDEBUG 
-DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -Igen 
-I/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/bodge 
-I/usr/include/libdrm -fstack-protector --param=ssp-buffer-size=4 
-pthread -fno-strict-aliasing -Wno-unused-parameter 
-Wno-missing-field-initializers -fvisibility=hidden -pipe -fPIC 
-Wno-unused-local-typedefs -I/usr/include/xulrunner-41.0.2/nss 
-I/usr/include/xulrunner-41.0.2/nspr -Wno-format -Wno-unused-result 
-I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include 
-I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -m64 -march=x86-64 
-O2 -fno-ident -fdata-sections -ffunction-sections -funwind-tables -O2 
-fPIC  -c 
/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c 
-o obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o
/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c: 
In function ?ssl3_ChaCha20Poly1305?:
/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2091:15: 
error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no 
member named ?pNonce?
      aeadParams.pNonce = (unsigned char *) additionalData;
                ^
/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2092:15: 
error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no 
member named ?ulNonceLen?
      aeadParams.ulNonceLen = 8;
                ^
[10/10262] CC 
obj/src/3rdparty/chromium/third_party/libvpx/source/libvpx/vp9/common/x86/libvpx_intrinsics_sse2.vp9_idct_intrin_sse2.o
ninja: build stopped: subcommand failed.
Makefile.gyp_run:756: recipe for target 'invoke_ninja' failed
make[4]: *** [invoke_ninja] Error 1
make[4]: Leaving directory 
'/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core'
Makefile:63: recipe for target 'sub-gyp_run-pro-make_first' failed
make[3]: *** [sub-gyp_run-pro-make_first] Error 2
make[3]: Leaving directory 
'/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core'
Makefile:48: recipe for target 'sub-core-make_first' failed
make[2]: *** [sub-core-make_first] Error 2
make[2]: Leaving directory 
'/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src'
Makefile:44: recipe for target 'sub-src-make_first' failed
make[1]: *** [sub-src-make_first] Error 2
make[1]: Leaving directory 
'/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine'
Makefile:803: recipe for target 'module-qtwebengine-make_first' failed
make: *** [module-qtwebengine-make_first] Error 2

-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Wed May 11 17:13:19 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 11 May 2016 19:13:19 +0200
Subject: [Slackbuilds-users] qt5 build 3 fails to build
In-Reply-To: <f13f23d9-f0ca-4420-95dd-8c63c5a70875@gmail.com>
References: <f13f23d9-f0ca-4420-95dd-8c63c5a70875@gmail.com>
Message-ID: <CAPsDuS6YcbXmD1CTJVOdDBeKwZwz+=2+i5KgC=fA+GZAVt+n8w@mail.gmail.com>

2016-05-11 18:58 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:
> Hi,
>
> qt5 fails to build. I'm on -current as of Wed May 11 05:20:01 UTC 2016.
> The error is very similar or identical to the previous one, regarding NSS.
> Am I missing something obvious? :)
>
> Error message follows:
>
> ninja: Entering directory
> `/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core/Release'
> [10/10262] CC
> obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o
> FAILED: /usr/bin/gcc -MMD -MF
> obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o.d
> -DV8_DEPRECATION_WARNINGS -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -DNO_TCMALLOC
> -DCHROMIUM_BUILD -DTOOLKIT_VIEWS=1 -DUI_COMPOSITOR_IMAGE_TRANSPORT
> -DUSE_AURA=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_LIBJPEG_TURBO=1 -DUSE_X11=1
> -DENABLE_ONE_CLICK_SIGNIN -DENABLE_PRE_SYNC_BACKUP -DUSE_XI2_MT=2
> -DENABLE_REMOTING=1 -DENABLE_WEBRTC=1 -DENABLE_PEPPER_CDMS
> -DENABLE_CONFIGURATION_POLICY -DENABLE_NOTIFICATIONS -DUSE_UDEV
> -DDONT_EMBED_BUILD_METADATA -DENABLE_TASK_MANAGER=1 -DENABLE_EXTENSIONS=1
> -DENABLE_PLUGINS=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1
> -DENABLE_AUTOFILL_DIALOG=1 -DENABLE_BACKGROUND=1 -DENABLE_GOOGLE_NOW=1
> -DCLD_VERSION=2 -DCLD2_DATA_SOURCE=static -DENABLE_PRINTING=1
> -DENABLE_BASIC_PRINTING=1 -DENABLE_PRINT_PREVIEW=1 -DENABLE_SPELLCHECK=1
> -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE_APP_LIST=1
> -DENABLE_SETTINGS_APP=1 -DENABLE_MANAGED_USERS=1 -DENABLE_MDNS=1
> -DENABLE_SERVICE_DISCOVERY=1 -DENABLE_LOAD_COMPLETION_HACKS=1
> -DNO_PKCS11_BYPASS -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DUSE_LIBPCI=1
> -DUSE_GLIB=1 -DUSE_NSS=1 -DNDEBUG -DNVALGRIND
> -DDYNAMIC_ANNOTATIONS_ENABLED=0 -Igen
> -I/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/bodge
> -I/usr/include/libdrm -fstack-protector --param=ssp-buffer-size=4 -pthread
> -fno-strict-aliasing -Wno-unused-parameter -Wno-missing-field-initializers
> -fvisibility=hidden -pipe -fPIC -Wno-unused-local-typedefs
> -I/usr/include/xulrunner-41.0.2/nss -I/usr/include/xulrunner-41.0.2/nspr
> -Wno-format -Wno-unused-result -I/usr/include/dbus-1.0
> -I/usr/lib64/dbus-1.0/include -I/usr/include/dbus-1.0
> -I/usr/lib64/dbus-1.0/include -m64 -march=x86-64 -O2 -fno-ident
> -fdata-sections -ffunction-sections -funwind-tables -O2 -fPIC  -c
> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c
> -o obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o
> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:
> In function ?ssl3_ChaCha20Poly1305?:
> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2091:15:
> error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member
> named ?pNonce?
>      aeadParams.pNonce = (unsigned char *) additionalData;
>                ^
> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2092:15:
> error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member
> named ?ulNonceLen?
>      aeadParams.ulNonceLen = 8;
>                ^
> [10/10262] CC
> obj/src/3rdparty/chromium/third_party/libvpx/source/libvpx/vp9/common/x86/libvpx_intrinsics_sse2.vp9_idct_intrin_sse2.o
> ninja: build stopped: subcommand failed.
> Makefile.gyp_run:756: recipe for target 'invoke_ninja' failed
> make[4]: *** [invoke_ninja] Error 1
> make[4]: Leaving directory
> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core'
> Makefile:63: recipe for target 'sub-gyp_run-pro-make_first' failed
> make[3]: *** [sub-gyp_run-pro-make_first] Error 2
> make[3]: Leaving directory
> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core'
> Makefile:48: recipe for target 'sub-core-make_first' failed
> make[2]: *** [sub-core-make_first] Error 2
> make[2]: Leaving directory
> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src'
> Makefile:44: recipe for target 'sub-src-make_first' failed
> make[1]: *** [sub-src-make_first] Error 2
> make[1]: Leaving directory
> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine'
> Makefile:803: recipe for target 'module-qtwebengine-make_first' failed
> make: *** [module-qtwebengine-make_first] Error 2

Hi Andrzej,

which build script are you using, from which repository?

Matteo

From atelszewski at gmail.com  Wed May 11 17:22:31 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 11 May 2016 19:22:31 +0200
Subject: [Slackbuilds-users] qt5 build 3 fails to build
In-Reply-To: <CAPsDuS6YcbXmD1CTJVOdDBeKwZwz+=2+i5KgC=fA+GZAVt+n8w@mail.gmail.com>
References: <f13f23d9-f0ca-4420-95dd-8c63c5a70875@gmail.com>
 <CAPsDuS6YcbXmD1CTJVOdDBeKwZwz+=2+i5KgC=fA+GZAVt+n8w@mail.gmail.com>
Message-ID: <0584d1f6-aa51-2c80-b7a4-a345a7701c3c@gmail.com>

On 11/05/16 19:13, Matteo Bernardini wrote:
> 2016-05-11 18:58 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:
>> Hi,
>>
>> qt5 fails to build. I'm on -current as of Wed May 11 05:20:01 UTC 2016.
>> The error is very similar or identical to the previous one, regarding NSS.
>> Am I missing something obvious? :)
>>
>> Error message follows:
>>
>> ninja: Entering directory
>> `/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core/Release'
>> [10/10262] CC
>> obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o
>> FAILED: /usr/bin/gcc -MMD -MF
>> obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o.d
>> -DV8_DEPRECATION_WARNINGS -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -DNO_TCMALLOC
>> -DCHROMIUM_BUILD -DTOOLKIT_VIEWS=1 -DUI_COMPOSITOR_IMAGE_TRANSPORT
>> -DUSE_AURA=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_LIBJPEG_TURBO=1 -DUSE_X11=1
>> -DENABLE_ONE_CLICK_SIGNIN -DENABLE_PRE_SYNC_BACKUP -DUSE_XI2_MT=2
>> -DENABLE_REMOTING=1 -DENABLE_WEBRTC=1 -DENABLE_PEPPER_CDMS
>> -DENABLE_CONFIGURATION_POLICY -DENABLE_NOTIFICATIONS -DUSE_UDEV
>> -DDONT_EMBED_BUILD_METADATA -DENABLE_TASK_MANAGER=1 -DENABLE_EXTENSIONS=1
>> -DENABLE_PLUGINS=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1
>> -DENABLE_AUTOFILL_DIALOG=1 -DENABLE_BACKGROUND=1 -DENABLE_GOOGLE_NOW=1
>> -DCLD_VERSION=2 -DCLD2_DATA_SOURCE=static -DENABLE_PRINTING=1
>> -DENABLE_BASIC_PRINTING=1 -DENABLE_PRINT_PREVIEW=1 -DENABLE_SPELLCHECK=1
>> -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE_APP_LIST=1
>> -DENABLE_SETTINGS_APP=1 -DENABLE_MANAGED_USERS=1 -DENABLE_MDNS=1
>> -DENABLE_SERVICE_DISCOVERY=1 -DENABLE_LOAD_COMPLETION_HACKS=1
>> -DNO_PKCS11_BYPASS -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DUSE_LIBPCI=1
>> -DUSE_GLIB=1 -DUSE_NSS=1 -DNDEBUG -DNVALGRIND
>> -DDYNAMIC_ANNOTATIONS_ENABLED=0 -Igen
>> -I/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/bodge
>> -I/usr/include/libdrm -fstack-protector --param=ssp-buffer-size=4 -pthread
>> -fno-strict-aliasing -Wno-unused-parameter -Wno-missing-field-initializers
>> -fvisibility=hidden -pipe -fPIC -Wno-unused-local-typedefs
>> -I/usr/include/xulrunner-41.0.2/nss -I/usr/include/xulrunner-41.0.2/nspr
>> -Wno-format -Wno-unused-result -I/usr/include/dbus-1.0
>> -I/usr/lib64/dbus-1.0/include -I/usr/include/dbus-1.0
>> -I/usr/lib64/dbus-1.0/include -m64 -march=x86-64 -O2 -fno-ident
>> -fdata-sections -ffunction-sections -funwind-tables -O2 -fPIC  -c
>> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c
>> -o obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o
>> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:
>> In function ?ssl3_ChaCha20Poly1305?:
>> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2091:15:
>> error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member
>> named ?pNonce?
>>      aeadParams.pNonce = (unsigned char *) additionalData;
>>                ^
>> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2092:15:
>> error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member
>> named ?ulNonceLen?
>>      aeadParams.ulNonceLen = 8;
>>                ^
>> [10/10262] CC
>> obj/src/3rdparty/chromium/third_party/libvpx/source/libvpx/vp9/common/x86/libvpx_intrinsics_sse2.vp9_idct_intrin_sse2.o
>> ninja: build stopped: subcommand failed.
>> Makefile.gyp_run:756: recipe for target 'invoke_ninja' failed
>> make[4]: *** [invoke_ninja] Error 1
>> make[4]: Leaving directory
>> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core'
>> Makefile:63: recipe for target 'sub-gyp_run-pro-make_first' failed
>> make[3]: *** [sub-gyp_run-pro-make_first] Error 2
>> make[3]: Leaving directory
>> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core'
>> Makefile:48: recipe for target 'sub-core-make_first' failed
>> make[2]: *** [sub-core-make_first] Error 2
>> make[2]: Leaving directory
>> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src'
>> Makefile:44: recipe for target 'sub-src-make_first' failed
>> make[1]: *** [sub-src-make_first] Error 2
>> make[1]: Leaving directory
>> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine'
>> Makefile:803: recipe for target 'module-qtwebengine-make_first' failed
>> make: *** [module-qtwebengine-make_first] Error 2
>
> Hi Andrzej,
>
> which build script are you using, from which repository?
>

git master I believe.


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


-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Wed May 11 20:24:26 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 11 May 2016 22:24:26 +0200
Subject: [Slackbuilds-users] qt5 build 3 fails to build
In-Reply-To: <0584d1f6-aa51-2c80-b7a4-a345a7701c3c@gmail.com>
References: <f13f23d9-f0ca-4420-95dd-8c63c5a70875@gmail.com>
 <CAPsDuS6YcbXmD1CTJVOdDBeKwZwz+=2+i5KgC=fA+GZAVt+n8w@mail.gmail.com>
 <0584d1f6-aa51-2c80-b7a4-a345a7701c3c@gmail.com>
Message-ID: <CAPsDuS5rPhPo0F_K_W-TcaZmaq0_c-NJvjq4eAKpgKsb+hQO4g@mail.gmail.com>

2016-05-11 19:22 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:
> git master I believe.

that's strange, because, to verify, I just finished building it with
no issues from there on a clean slackware64-current full installation
with the latest updates...

http://ponce.cc/slackware/testing/qt5_build_log.txt.gz

Matteo

From atelszewski at gmail.com  Wed May 11 20:44:16 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 11 May 2016 22:44:16 +0200
Subject: [Slackbuilds-users] qt5 build 3 fails to build
In-Reply-To: <CAPsDuS5rPhPo0F_K_W-TcaZmaq0_c-NJvjq4eAKpgKsb+hQO4g@mail.gmail.com>
References: <f13f23d9-f0ca-4420-95dd-8c63c5a70875@gmail.com>
 <CAPsDuS6YcbXmD1CTJVOdDBeKwZwz+=2+i5KgC=fA+GZAVt+n8w@mail.gmail.com>
 <0584d1f6-aa51-2c80-b7a4-a345a7701c3c@gmail.com>
 <CAPsDuS5rPhPo0F_K_W-TcaZmaq0_c-NJvjq4eAKpgKsb+hQO4g@mail.gmail.com>
Message-ID: <60a11711-e7f0-1ee3-d952-cfff71377518@gmail.com>

On 11/05/16 22:24, Matteo Bernardini wrote:
> 2016-05-11 19:22 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:
>> git master I believe.
>
> that's strange, because, to verify, I just finished building it with
> no issues from there on a clean slackware64-current full installation
> with the latest updates...
>
> http://ponce.cc/slackware/testing/qt5_build_log.txt.gz
>
> Matteo

OK, I'm gonna give it one more shot.

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


-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Thu May 12 11:22:35 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 12 May 2016 13:22:35 +0200
Subject: [Slackbuilds-users] qt5 build 3 fails to build
In-Reply-To: <60a11711-e7f0-1ee3-d952-cfff71377518@gmail.com>
References: <f13f23d9-f0ca-4420-95dd-8c63c5a70875@gmail.com>
 <CAPsDuS6YcbXmD1CTJVOdDBeKwZwz+=2+i5KgC=fA+GZAVt+n8w@mail.gmail.com>
 <0584d1f6-aa51-2c80-b7a4-a345a7701c3c@gmail.com>
 <CAPsDuS5rPhPo0F_K_W-TcaZmaq0_c-NJvjq4eAKpgKsb+hQO4g@mail.gmail.com>
 <60a11711-e7f0-1ee3-d952-cfff71377518@gmail.com>
Message-ID: <b77ad8af-3873-7399-c0e2-556495d952d9@gmail.com>

On 11/05/16 22:44, Andrzej Telszewski wrote:
> On 11/05/16 22:24, Matteo Bernardini wrote:
>> 2016-05-11 19:22 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:
>>> git master I believe.
>>
>> that's strange, because, to verify, I just finished building it with
>> no issues from there on a clean slackware64-current full installation
>> with the latest updates...
>>
>> http://ponce.cc/slackware/testing/qt5_build_log.txt.gz
>>
>> Matteo
>
> OK, I'm gonna give it one more shot.
>

I tried the following scenario:
1. removed qbs package,
2. removed qt-creator3 package,
3. deleted libraries/qt5 and re-synced (sbopkg),
4. rebooted the machine.

and the build of qt5 fails.

Then I tried the following scenario:
1. removed qt5 package,
2. removed the whole SBo repository and re-synced (sbopkg),
4. updated to -current as of Thu May 12 01:50:21 UTC 2016, but it should 
be completely irrelevant,
3. rebooted the machine.

and the build of qt5 fails.

The error is the same one as previously, regarding NSS.

Do you have any suggestions on what might be wrong?

-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Thu May 12 11:31:04 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 12 May 2016 13:31:04 +0200
Subject: [Slackbuilds-users] qt5 build 3 fails to build
In-Reply-To: <b77ad8af-3873-7399-c0e2-556495d952d9@gmail.com>
References: <f13f23d9-f0ca-4420-95dd-8c63c5a70875@gmail.com>
 <CAPsDuS6YcbXmD1CTJVOdDBeKwZwz+=2+i5KgC=fA+GZAVt+n8w@mail.gmail.com>
 <0584d1f6-aa51-2c80-b7a4-a345a7701c3c@gmail.com>
 <CAPsDuS5rPhPo0F_K_W-TcaZmaq0_c-NJvjq4eAKpgKsb+hQO4g@mail.gmail.com>
 <60a11711-e7f0-1ee3-d952-cfff71377518@gmail.com>
 <b77ad8af-3873-7399-c0e2-556495d952d9@gmail.com>
Message-ID: <CAPsDuS5Uh1PvoQEOxwV9HhBZJaaG035LSUpihbtnAoXBL4bCEg@mail.gmail.com>

2016-05-12 13:22 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:
> The error is the same one as previously, regarding NSS.
>
> Do you have any suggestions on what might be wrong?

seeing your log I would suggest trying removing xulrunner and building
qt5 again.

then, if that fails, I suggest trying building in a fresh full install
in a virtual machine.

Matteo

From willysr at slackbuilds.org  Thu May 12 11:57:06 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 12 May 2016 18:57:06 +0700
Subject: [Slackbuilds-users] qt5 build 3 fails to build
In-Reply-To: <b77ad8af-3873-7399-c0e2-556495d952d9@gmail.com>
References: <f13f23d9-f0ca-4420-95dd-8c63c5a70875@gmail.com>
 <CAPsDuS6YcbXmD1CTJVOdDBeKwZwz+=2+i5KgC=fA+GZAVt+n8w@mail.gmail.com>
 <0584d1f6-aa51-2c80-b7a4-a345a7701c3c@gmail.com>
 <CAPsDuS5rPhPo0F_K_W-TcaZmaq0_c-NJvjq4eAKpgKsb+hQO4g@mail.gmail.com>
 <60a11711-e7f0-1ee3-d952-cfff71377518@gmail.com>
 <b77ad8af-3873-7399-c0e2-556495d952d9@gmail.com>
Message-ID: <13e744de-3ac7-1ce3-d2f4-d768a3d82932@slackbuilds.org>

> I tried the following scenario:
> 1. removed qbs package,
> 2. removed qt-creator3 package,
> 3. deleted libraries/qt5 and re-synced (sbopkg),
> 4. rebooted the machine.
> 
> and the build of qt5 fails.
> 
> Then I tried the following scenario:
> 1. removed qt5 package,
> 2. removed the whole SBo repository and re-synced (sbopkg),
> 4. updated to -current as of Thu May 12 01:50:21 UTC 2016, but it should
> be completely irrelevant,
> 3. rebooted the machine.
> 
> and the build of qt5 fails.
> 
> The error is the same one as previously, regarding NSS.

i just finished building qt5 using sbopkg on a vm

qt5:
  MD5SUM check for qt-everywhere-opensource-src-5.5.1.tar.xz ... OK
  Building package qt5-5.5.1-x86_64-3_SBo.tgz ... OK
  Installing package qt5-5.5.1-x86_64-3_SBo.tgz ... OK


-- 
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/20160512/845451be/attachment.asc>

From atelszewski at gmail.com  Thu May 12 19:05:07 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 12 May 2016 21:05:07 +0200
Subject: [Slackbuilds-users] qt5 build 3 fails to build
In-Reply-To: <CAPsDuS5Uh1PvoQEOxwV9HhBZJaaG035LSUpihbtnAoXBL4bCEg@mail.gmail.com>
References: <f13f23d9-f0ca-4420-95dd-8c63c5a70875@gmail.com>
 <CAPsDuS6YcbXmD1CTJVOdDBeKwZwz+=2+i5KgC=fA+GZAVt+n8w@mail.gmail.com>
 <0584d1f6-aa51-2c80-b7a4-a345a7701c3c@gmail.com>
 <CAPsDuS5rPhPo0F_K_W-TcaZmaq0_c-NJvjq4eAKpgKsb+hQO4g@mail.gmail.com>
 <60a11711-e7f0-1ee3-d952-cfff71377518@gmail.com>
 <b77ad8af-3873-7399-c0e2-556495d952d9@gmail.com>
 <CAPsDuS5Uh1PvoQEOxwV9HhBZJaaG035LSUpihbtnAoXBL4bCEg@mail.gmail.com>
Message-ID: <17babe90-8ef3-273e-f2e4-d0a794970b98@gmail.com>

On 12/05/16 13:31, Matteo Bernardini wrote:
> 2016-05-12 13:22 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com>:
>> The error is the same one as previously, regarding NSS.
>>
>> Do you have any suggestions on what might be wrong?
>
> seeing your log I would suggest trying removing xulrunner and building
> qt5 again.
>

I did the following:
1. removed xulrunner,
2. reinstalled mozilla-nss,
3. rebooted the machine.

and the build of qt5 succeeded.

Maybe it would be worth mentioning in the qt5 and xulrunner READMEs, 
that trying to install both at the same time might have unexpected side 
effects? Or maybe something has to be patched? ;)

If I'm not mistaken, xulrunner package has overwritten some files from 
mozilla-nss, so it's something to watch for.

I don't think I'm going to use xulrunner anytime soon, since I only 
needed it to test gnash. And since gnash has shown to be failure for me, 
I'm not gonna use it.


Thanks for the assistance!


> then, if that fails, I suggest trying building in a fresh full install
> in a virtual machine.
>

No need for that :)

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


-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Fri May 13 11:50:11 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 13 May 2016 13:50:11 +0200
Subject: [Slackbuilds-users] xulrunner deprecation
Message-ID: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>

as Andrzej reported xulrunner overwrites files from the mozilla-nss
package in Slackware.

also there's this: https://en.wikipedia.org/wiki/XULRunner#Deprecation

it seems that the best option for the moment would be to remove this
and the things that depends on it (evolus-pencil, gnash, vuze) from
our repository for 14.2.

please express any alternative proposal regarding xulrunner and what
depends on it.

Matteo

From willysr at slackbuilds.org  Fri May 13 12:06:20 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 13 May 2016 19:06:20 +0700
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
Message-ID: <c00ab766-5629-3835-345a-6228f3acbe1d@slackbuilds.org>

> as Andrzej reported xulrunner overwrites files from the mozilla-nss
> package in Slackware.
> 
> also there's this: https://en.wikipedia.org/wiki/XULRunner#Deprecation
> 
> it seems that the best option for the moment would be to remove this
> and the things that depends on it (evolus-pencil, gnash, vuze) from
> our repository for 14.2.
> 
> please express any alternative proposal regarding xulrunner and what
> depends on it.

as of evolus-pencil, a simple sed should fix this
sed -i "s|xulrunner|firefox|" $PKG/usr/bin/pencil

and then we can remove xulrunner dependency


-- 
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/20160513/fb2def8d/attachment.asc>

From atelszewski at gmail.com  Fri May 13 12:14:31 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Fri, 13 May 2016 14:14:31 +0200
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
Message-ID: <d4fbf66c-f8d4-f86c-79f3-2439b043ede2@gmail.com>

On 13/05/16 13:50, Matteo Bernardini wrote:
> as Andrzej reported xulrunner overwrites files from the mozilla-nss
> package in Slackware.
>

$ sort /var/log/packages/mozilla-nss-3.23-x86_64-1 > mozilla-nss
$ sort /var/log/removed_packages/xulrunner-41.0.2-x86_64-1_SBo > xulrunner
$ comm -1 -2 mozilla-nss xulrunner
./
FILE LIST:
PACKAGE DESCRIPTION:
install/
install/doinst.sh
install/slack-desc
usr/
usr/bin/
usr/doc/
usr/include/
usr/lib64/
usr/lib64/pkgconfig/
usr/lib64/pkgconfig/mozilla-nspr.pc
usr/lib64/pkgconfig/mozilla-nss.pc

> also there's this: https://en.wikipedia.org/wiki/XULRunner#Deprecation
>
> it seems that the best option for the moment would be to remove this
> and the things that depends on it (evolus-pencil, gnash, vuze) from
> our repository for 14.2.
>
> please express any alternative proposal regarding xulrunner and what
> depends on it.
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>


-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Fri May 13 12:55:29 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 13 May 2016 14:55:29 +0200
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <c00ab766-5629-3835-345a-6228f3acbe1d@slackbuilds.org>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
 <c00ab766-5629-3835-345a-6228f3acbe1d@slackbuilds.org>
Message-ID: <CAPsDuS4kieLwug__7Y-CBNt-cRmhB-vw+X2EnbZCQQNcW1QMjQ@mail.gmail.com>

2016-05-13 14:06 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:
>> as Andrzej reported xulrunner overwrites files from the mozilla-nss
>> package in Slackware.
>>
>> also there's this: https://en.wikipedia.org/wiki/XULRunner#Deprecation
>>
>> it seems that the best option for the moment would be to remove this
>> and the things that depends on it (evolus-pencil, gnash, vuze) from
>> our repository for 14.2.
>>
>> please express any alternative proposal regarding xulrunner and what
>> depends on it.
>
> as of evolus-pencil, a simple sed should fix this
> sed -i "s|xulrunner|firefox|" $PKG/usr/bin/pencil
>
> and then we can remove xulrunner dependency

maybe also vuze could be easily fixed, but let's hear it from its maintainer...

Matteo

From Jim.Diamond at acadiau.ca  Fri May 13 13:18:39 2016
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Fri, 13 May 2016 10:18:39 -0300
Subject: [Slackbuilds-users] strongswan: md5sum failure
Message-ID: <20160513131839.GA2918@jdiamond-nb.acadiau.ca>

Hi,

On Slackware 64 14.1
    sboupgrade strongswan
rewards me with

Unable to download/verify source file(s) for strongswan:
  md5sum failure for /poo/usr-sbo-141/distfiles/strongswan-5.3.4.tar.bz2.

Cheers.

                        Jim

From willysr at slackbuilds.org  Fri May 13 13:22:37 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 13 May 2016 20:22:37 +0700
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <CAPsDuS4kieLwug__7Y-CBNt-cRmhB-vw+X2EnbZCQQNcW1QMjQ@mail.gmail.com>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
 <c00ab766-5629-3835-345a-6228f3acbe1d@slackbuilds.org>
 <CAPsDuS4kieLwug__7Y-CBNt-cRmhB-vw+X2EnbZCQQNcW1QMjQ@mail.gmail.com>
Message-ID: <ca9d52ae-0c50-330b-fdc1-aee27887bb85@slackbuilds.org>

> maybe also vuze could be easily fixed, but let's hear it from its maintainer...

I'm not sure whether the maintainer is still active or not
his last contribution was adding vuze 5 years 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/20160513/6dfdfde6/attachment.asc>

From willysr at slackbuilds.org  Fri May 13 13:23:40 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 13 May 2016 20:23:40 +0700
Subject: [Slackbuilds-users] strongswan: md5sum failure
In-Reply-To: <20160513131839.GA2918@jdiamond-nb.acadiau.ca>
References: <20160513131839.GA2918@jdiamond-nb.acadiau.ca>
Message-ID: <8696287f-b5fa-fd01-df72-9539664833a1@slackbuilds.org>

> On Slackware 64 14.1
>     sboupgrade strongswan
> rewards me with
> 
> Unable to download/verify source file(s) for strongswan:
>   md5sum failure for /poo/usr-sbo-141/distfiles/strongswan-5.3.4.tar.bz2.


https://slackbuilds.org/cgit/slackbuilds/commit/?id=e84223a7bd41ab4e5b608dce3f708d254fcd6bf4

this fix doesn't get backported back to 14.1 unfortunately

-- 
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/20160513/568c7729/attachment.asc>

From matteo.bernardini at gmail.com  Fri May 13 13:26:59 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 13 May 2016 15:26:59 +0200
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <ca9d52ae-0c50-330b-fdc1-aee27887bb85@slackbuilds.org>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
 <c00ab766-5629-3835-345a-6228f3acbe1d@slackbuilds.org>
 <CAPsDuS4kieLwug__7Y-CBNt-cRmhB-vw+X2EnbZCQQNcW1QMjQ@mail.gmail.com>
 <ca9d52ae-0c50-330b-fdc1-aee27887bb85@slackbuilds.org>
Message-ID: <CAPsDuS69abtzs+vewsFCKmPk9J3PRwGqeTjEjb4g4MfQqHakuQ@mail.gmail.com>

2016-05-13 15:22 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:
>> maybe also vuze could be easily fixed, but let's hear it from its maintainer...
>
> I'm not sure whether the maintainer is still active or not
> his last contribution was adding vuze 5 years ago

I added him in cc: if he doesn't answer the best option, IMHO, is to
remove vuze and put it up for grabs is someone is interested.

Matteo

From ryan.q at linux.com  Fri May 13 13:32:47 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Fri, 13 May 2016 06:32:47 -0700
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <CAPsDuS69abtzs+vewsFCKmPk9J3PRwGqeTjEjb4g4MfQqHakuQ@mail.gmail.com>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
 <c00ab766-5629-3835-345a-6228f3acbe1d@slackbuilds.org>
 <CAPsDuS4kieLwug__7Y-CBNt-cRmhB-vw+X2EnbZCQQNcW1QMjQ@mail.gmail.com>
 <ca9d52ae-0c50-330b-fdc1-aee27887bb85@slackbuilds.org>
 <CAPsDuS69abtzs+vewsFCKmPk9J3PRwGqeTjEjb4g4MfQqHakuQ@mail.gmail.com>
Message-ID: <CAAcyf-rSh5spESLGcPdZW+zBaPigq=ompvOKOMw55aJcZDc_hA@mail.gmail.com>

>
> sed -i "s|xulrunner|firefox|" $PKG/usr/bin/pencil


Thanks for the fix Willy!


-- 
-Ryan
[ryanpcmcquen.org]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160513/e0739ac9/attachment.html>

From willysr at slackbuilds.org  Fri May 13 15:22:46 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 13 May 2016 22:22:46 +0700
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
Message-ID: <3d2ae1ba-39a8-4e7f-3a94-a40f7c0ae4d1@slackbuilds.org>

> as Andrzej reported xulrunner overwrites files from the mozilla-nss
> package in Slackware.
> 
> also there's this: https://en.wikipedia.org/wiki/XULRunner#Deprecation
> 
> it seems that the best option for the moment would be to remove this
> and the things that depends on it (evolus-pencil, gnash, vuze) from
> our repository for 14.2.
> 
> please express any alternative proposal regarding xulrunner and what
> depends on it.

as of gnash, it's still developed upstream, but no official release
except for git snapshot.

i wonder if it's still worthed to be kept in our repo as it doesn't
really support newer flash formats and it has being phased out since
2013 in Chrome
(http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html)
and by the end of 2016 by Mozilla
(https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/)


-- 
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/20160513/fdeeba82/attachment.asc>

From matteo.bernardini at gmail.com  Fri May 13 15:30:22 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 13 May 2016 17:30:22 +0200
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <3d2ae1ba-39a8-4e7f-3a94-a40f7c0ae4d1@slackbuilds.org>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
 <3d2ae1ba-39a8-4e7f-3a94-a40f7c0ae4d1@slackbuilds.org>
Message-ID: <CAPsDuS6uZ9jEenU0sc+aCLDCYL_TWqtL=u5nr4RZ5yrQ_mdupA@mail.gmail.com>

2016-05-13 17:22 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:
>> as Andrzej reported xulrunner overwrites files from the mozilla-nss
>> package in Slackware.
>>
>> also there's this: https://en.wikipedia.org/wiki/XULRunner#Deprecation
>>
>> it seems that the best option for the moment would be to remove this
>> and the things that depends on it (evolus-pencil, gnash, vuze) from
>> our repository for 14.2.
>>
>> please express any alternative proposal regarding xulrunner and what
>> depends on it.
>
> as of gnash, it's still developed upstream, but no official release
> except for git snapshot.
>
> i wonder if it's still worthed to be kept in our repo as it doesn't
> really support newer flash formats and it has being phased out since
> 2013 in Chrome
> (http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html)
> and by the end of 2016 by Mozilla
> (https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/)

well, as long as npapi plugins are supported it should make sense, and
if 14.2 sticks with 45.Xesr, it should be supported on the next
Slackware version.

it can be it's possible to build gnash without xulrunner, but I think
the maintainer should decide that it's the case of pursuing this way,
in case in the end we agree to drop xulrunner.

Matteo

From Jim.Diamond at acadiau.ca  Fri May 13 16:20:52 2016
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Fri, 13 May 2016 13:20:52 -0300
Subject: [Slackbuilds-users] strongswan: md5sum failure
In-Reply-To: <8696287f-b5fa-fd01-df72-9539664833a1@slackbuilds.org>
References: <20160513131839.GA2918@jdiamond-nb.acadiau.ca>
 <8696287f-b5fa-fd01-df72-9539664833a1@slackbuilds.org>
Message-ID: <20160513162051.GD4049@jdiamond-nb.acadiau.ca>

On Fri, May 13, 2016 at 20:23 (+0700), Willy Sudiarto Raharjo wrote:

>> On Slackware 64 14.1
>> sboupgrade strongswan
>> rewards me with

>> Unable to download/verify source file(s) for strongswan:
>> md5sum failure for /poo/usr-sbo-141/distfiles/strongswan-5.3.4.tar.bz2.


> https://slackbuilds.org/cgit/slackbuilds/commit/?id=e84223a7bd41ab4e5b608dce3f708d254fcd6bf4

> this fix doesn't get backported back to 14.1 unfortunately

OK, thanks.  I realize that little effort is being spent on 14.1, but
hope springs eternal.

(Actually, I'm really hoping that Pat calls it a day soon and releases
14.2.)

                                Jim

From willysr at slackbuilds.org  Fri May 13 17:05:04 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 14 May 2016 00:05:04 +0700
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <CAPsDuS6uZ9jEenU0sc+aCLDCYL_TWqtL=u5nr4RZ5yrQ_mdupA@mail.gmail.com>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
 <3d2ae1ba-39a8-4e7f-3a94-a40f7c0ae4d1@slackbuilds.org>
 <CAPsDuS6uZ9jEenU0sc+aCLDCYL_TWqtL=u5nr4RZ5yrQ_mdupA@mail.gmail.com>
Message-ID: <958cabb3-09f5-c66e-3f84-43d88e869815@slackbuilds.org>

> it can be it's possible to build gnash without xulrunner, but I think
> the maintainer should decide that it's the case of pursuing this way,
> in case in the end we agree to drop xulrunner.

yes, we can use --disable-npapi
http://git.savannah.gnu.org/cgit/gnash.git/commit/?id=ef2784b58f5b52ac547be1be10c65052db99b613

it's been there since 2013


-- 
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/20160514/f99e19a3/attachment.asc>

From selivanow at gmail.com  Fri May 13 17:19:28 2016
From: selivanow at gmail.com (Chris Lawrence)
Date: Fri, 13 May 2016 17:19:28 +0000
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <CAAcyf-rSh5spESLGcPdZW+zBaPigq=ompvOKOMw55aJcZDc_hA@mail.gmail.com>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
 <c00ab766-5629-3835-345a-6228f3acbe1d@slackbuilds.org>
 <CAPsDuS4kieLwug__7Y-CBNt-cRmhB-vw+X2EnbZCQQNcW1QMjQ@mail.gmail.com>
 <ca9d52ae-0c50-330b-fdc1-aee27887bb85@slackbuilds.org>
 <CAPsDuS69abtzs+vewsFCKmPk9J3PRwGqeTjEjb4g4MfQqHakuQ@mail.gmail.com>
 <CAAcyf-rSh5spESLGcPdZW+zBaPigq=ompvOKOMw55aJcZDc_hA@mail.gmail.com>
Message-ID: <CAEsaJKpUHGSCv8-6j9Tkh1q5yfcOJ39vP_tnHvxXLBh5gWac2g@mail.gmail.com>

Yes, I have been absent for a while. Mostly because I haven't upgraded the
version I use and free time not being what it used to be. I can hardly
believe it has been five years. I can certainly take a look and submit a
package/patch for 14.2
On Fri, May 13, 2016 at 09:32 Ryan P.C. McQuen <ryan.q at linux.com> wrote:

> sed -i "s|xulrunner|firefox|" $PKG/usr/bin/pencil
>
>
> Thanks for the fix Willy!
>
>
> --
> -Ryan
> [ryanpcmcquen.org]
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160513/d2d27239/attachment.html>

From selivanow at gmail.com  Fri May 13 17:21:00 2016
From: selivanow at gmail.com (Chris Lawrence)
Date: Fri, 13 May 2016 17:21:00 +0000
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <CAPsDuS69abtzs+vewsFCKmPk9J3PRwGqeTjEjb4g4MfQqHakuQ@mail.gmail.com>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
 <c00ab766-5629-3835-345a-6228f3acbe1d@slackbuilds.org>
 <CAPsDuS4kieLwug__7Y-CBNt-cRmhB-vw+X2EnbZCQQNcW1QMjQ@mail.gmail.com>
 <ca9d52ae-0c50-330b-fdc1-aee27887bb85@slackbuilds.org>
 <CAPsDuS69abtzs+vewsFCKmPk9J3PRwGqeTjEjb4g4MfQqHakuQ@mail.gmail.com>
Message-ID: <CAEsaJKqRwE7WEEL7+aHqidZw28ypRs8_mxjQKbPm27J_dz8fEg@mail.gmail.com>

Yes, I have been absent for a while. Mostly because I haven't upgraded the
version I use and free time not being what it used to be. I can hardly
believe it has been five years. I can certainly take a look and submit a
package/patch for 14.2

Sorry, I replied to the incorrect message.

On Fri, May 13, 2016 at 09:26 Matteo Bernardini <matteo.bernardini at gmail.com>
wrote:

> 2016-05-13 15:22 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org
> >:
> >> maybe also vuze could be easily fixed, but let's hear it from its
> maintainer...
> >
> > I'm not sure whether the maintainer is still active or not
> > his last contribution was adding vuze 5 years ago
>
> I added him in cc: if he doesn't answer the best option, IMHO, is to
> remove vuze and put it up for grabs is someone is interested.
>
> Matteo
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160513/7975a222/attachment.html>

From willysr at slackbuilds.org  Fri May 13 17:54:40 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 14 May 2016 00:54:40 +0700
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <CAEsaJKqRwE7WEEL7+aHqidZw28ypRs8_mxjQKbPm27J_dz8fEg@mail.gmail.com>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
 <c00ab766-5629-3835-345a-6228f3acbe1d@slackbuilds.org>
 <CAPsDuS4kieLwug__7Y-CBNt-cRmhB-vw+X2EnbZCQQNcW1QMjQ@mail.gmail.com>
 <ca9d52ae-0c50-330b-fdc1-aee27887bb85@slackbuilds.org>
 <CAPsDuS69abtzs+vewsFCKmPk9J3PRwGqeTjEjb4g4MfQqHakuQ@mail.gmail.com>
 <CAEsaJKqRwE7WEEL7+aHqidZw28ypRs8_mxjQKbPm27J_dz8fEg@mail.gmail.com>
Message-ID: <c0fdcff4-3955-53f7-7ecb-50085f75e4c7@slackbuilds.org>

> Yes, I have been absent for a while. Mostly because I haven't upgraded the
> version I use and free time not being what it used to be. I can hardly
> believe it has been five years. I can certainly take a look and submit a
> package/patch for 14.2

good to know that you are still using Slackware Chris :)

we do hope that this patch or update can be delivered soon enough if
that's OK with you as 14.2 is getting closer as well (though we don't
know when will the exact release date).


-- 
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/20160514/6cfe4cf3/attachment.asc>

From elyk03 at gmail.com  Sat May 14 03:50:46 2016
From: elyk03 at gmail.com (Kyle Guinn)
Date: Fri, 13 May 2016 22:50:46 -0500
Subject: [Slackbuilds-users] xulrunner deprecation
In-Reply-To: <958cabb3-09f5-c66e-3f84-43d88e869815@slackbuilds.org>
References: <CAPsDuS6KfpznMKk4k8TMO09CbcE=36e_-H04sMMwTFUNDi8g2g@mail.gmail.com>
 <3d2ae1ba-39a8-4e7f-3a94-a40f7c0ae4d1@slackbuilds.org>
 <CAPsDuS6uZ9jEenU0sc+aCLDCYL_TWqtL=u5nr4RZ5yrQ_mdupA@mail.gmail.com>
 <958cabb3-09f5-c66e-3f84-43d88e869815@slackbuilds.org>
Message-ID: <CAJCpn80_AO5G-kPdE1-+qUSxOLxqV-xJSyWKoJZtoUx2tSWhrg@mail.gmail.com>

On 5/13/16, Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:
>> it can be it's possible to build gnash without xulrunner, but I think
>> the maintainer should decide that it's the case of pursuing this way,
>> in case in the end we agree to drop xulrunner.
>
> yes, we can use --disable-npapi
> http://git.savannah.gnu.org/cgit/gnash.git/commit/?id=ef2784b58f5b52ac547be1be10c65052db99b613
>
> it's been there since 2013

If you have to disable the plugin, that's fine with me.  Unfortunately
I'm not in a position to test building it without xulrunner on 14.2
anytime soon.  If you can confirm that it works, go ahead and add that
flag if/when you drop xulrunner.

-Kyle

From atelszewski at gmail.com  Sat May 14 11:13:31 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 14 May 2016 13:13:31 +0200
Subject: [Slackbuilds-users] Wrong permissions after installation,
 broken download link
Message-ID: <092a74f3-3a11-18f3-7f4b-d364d585cee9@gmail.com>

Hi,

The other day I was playing with some icon themes available at SBo.
Among the other I tried 
https://slackbuilds.org/cgit/slackbuilds/tree/desktop/faba-mono-icons
But it turned out that the download link at SBo 
(https://raw.githubusercontent.com/moka-project/faba-mono-icons/master/faba-mono-icons-4.2.tar.gz) 
is broken.
So I downloaded the source from 
http://slackware.uk/sbosrcarch/by-name/desktop/faba-mono-icons/faba-mono-icons-4.2.tar.gz
After the installation, it turned out that the file permissions are wrong.

It makes sense, since faba-mono-icons.SlackBuild does not do _chmod_ at 
all and that is what you get when the source is extracted:

$ umask 022
$ tar -xf faba-mono-icons-4.2.tar.gz
$ cd faba-mono-icons-4.2
$ ls -l
total 52
-rw------- 1 antezu users   666 Feb 13  2015 AUTHORS
drwx------ 6 antezu users  4096 Feb 13  2015 Faba-Mono/
drwx------ 6 antezu users  4096 Feb 13  2015 Faba-Mono-Dark/
-rw------- 1 antezu users   371 Feb 13  2015 INSTALL
-rw------- 1 antezu users 35148 Feb 13  2015 LICENSE

It looks like in that case even our standard _find_ wouldn't do the job, 
since the directories have "this" special permissions.
I might be wrong though, and I don't have enough power to analyze ;).


Doing the (very) naive:
$ grep -L ^find */*/*.SlackBuild

reveals around 150 SlackBuilds that do not use find to set permissions.
And it's probably correct in most of the cases.

But more alarming might be the following fact:

$ grep -L ^find */*/*.SlackBuild | grep "icon-theme\|icons"
desktop/awoken-icon-theme/awoken-icon-theme.SlackBuild
desktop/faba-icon-theme/faba-icon-theme.SlackBuild
desktop/faba-mono-icons/faba-mono-icons.SlackBuild
desktop/moka-icon-theme/moka-icon-theme.SlackBuild
desktop/numix-icon-theme-bevel/numix-icon-theme-bevel.SlackBuild
desktop/numix-icon-theme-circle/numix-icon-theme-circle.SlackBuild
desktop/numix-icon-theme/numix-icon-theme.SlackBuild

and it looks like in some cases we depend solely on the permissions 
provided by the tarball packager.
Which might not work out well in every case.

-- 
Best regards,
Andrzej Telszewski

From baildon.research at googlemail.com  Sat May 14 16:35:31 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Sat, 14 May 2016 17:35:31 +0100
Subject: [Slackbuilds-users] DOWNLOAD advice for github
Message-ID: <CAMt7G9QagweP8TTWqwOm9nGFJpYg1iP6rK4a0tKTZ72JNYdX+A@mail.gmail.com>

Hi everybody,

For maintainers, here's some advice about what to put in DOWNLOAD in
the .info file for github URLs.

NOTE: you don't need to change any of your existing files, this is
just some general advice that we hope you will find helpful and
interesting and useful. Also, this is not related to 14.2, it is
actually some new advice about github that Heinz worked out yesterday
:)

Hopefully, most of you know already that github is "clever" with
download URLs. It uses an HTTP "content disposition" header to tell
browsers the name of the archive that githib has dynamically created.
But by default wget and curl do not use the "content disposition"
header and use the last component of the URL as a filename. Therefore
(until now) our SlackBuilds have needed to try both possible names for
the download, e.g.

tar xvf $CWD/v$VERSION.tar.gz || tar xvf $CWD/$PRGNAM-$VERSION.tar.gz

So, here's the new advice: Heinz has worked out that if we use (for example)

DOWNLOAD="https://github.com/trizen/clyrics/archive/0.04/clyrics-0.04.tar.gz"

then the archive will *always* be named clyrics-0.04.tar.gz, even if
we use wget or curl, and so we can just do the usual tar command in
the SlackBuild:

tar xvf $CWD/$PRGNAM-$VERSION.tar.gz

Apparently this will even work nicely for projects that include the
project name in the git tag, e.g.

DOWNLOAD="https://github.com/christophgysin/pasystray/archive/0.5.2/pasystray-0.5.2.tar.gz"

so we can now stop using confusing and ugly commands like these:

rm -rf $PRGNAM-$PRGNAM-$VERSION
tar xvf $CWD/$PRGNAM-$PRGNAM-$VERSION.tar.gz
cd $PRGNAM-$PRGNAM-$VERSION

I hope this is helpful to you.  Thanks to Heinz for finally working
out the right way of handling this!

Best regards to everybody
-D.

ps. If I've made any mistakes above, corrections will be gratefully received :D

From atelszewski at gmail.com  Sat May 14 17:06:20 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 14 May 2016 19:06:20 +0200
Subject: [Slackbuilds-users] DOWNLOAD advice for github
In-Reply-To: <CAMt7G9QagweP8TTWqwOm9nGFJpYg1iP6rK4a0tKTZ72JNYdX+A@mail.gmail.com>
References: <CAMt7G9QagweP8TTWqwOm9nGFJpYg1iP6rK4a0tKTZ72JNYdX+A@mail.gmail.com>
Message-ID: <8c64caa2-4e41-89b4-7aa8-70965f4908bb@gmail.com>

On 14/05/16 18:35, David Spencer wrote:
> Hi everybody,
>
> For maintainers, here's some advice about what to put in DOWNLOAD in
> the .info file for github URLs.
>
> NOTE: you don't need to change any of your existing files, this is
> just some general advice that we hope you will find helpful and
> interesting and useful. Also, this is not related to 14.2, it is
> actually some new advice about github that Heinz worked out yesterday
> :)
>
> Hopefully, most of you know already that github is "clever" with
> download URLs. It uses an HTTP "content disposition" header to tell
> browsers the name of the archive that githib has dynamically created.
> But by default wget and curl do not use the "content disposition"
> header and use the last component of the URL as a filename. Therefore
> (until now) our SlackBuilds have needed to try both possible names for
> the download, e.g.
>
> tar xvf $CWD/v$VERSION.tar.gz || tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
>
> So, here's the new advice: Heinz has worked out that if we use (for example)
>
> DOWNLOAD="https://github.com/trizen/clyrics/archive/0.04/clyrics-0.04.tar.gz"
>
> then the archive will *always* be named clyrics-0.04.tar.gz, even if
> we use wget or curl, and so we can just do the usual tar command in
> the SlackBuild:
>
> tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
>
> Apparently this will even work nicely for projects that include the
> project name in the git tag, e.g.
>
> DOWNLOAD="https://github.com/christophgysin/pasystray/archive/0.5.2/pasystray-0.5.2.tar.gz"
>
> so we can now stop using confusing and ugly commands like these:
>
> rm -rf $PRGNAM-$PRGNAM-$VERSION
> tar xvf $CWD/$PRGNAM-$PRGNAM-$VERSION.tar.gz
> cd $PRGNAM-$PRGNAM-$VERSION
>
> I hope this is helpful to you.  Thanks to Heinz for finally working
> out the right way of handling this!
>
> Best regards to everybody
> -D.
>
> ps. If I've made any mistakes above, corrections will be gratefully received :D

Well appreciated!

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


-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Sat May 14 17:45:32 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 15 May 2016 00:45:32 +0700
Subject: [Slackbuilds-users] Wrong permissions after installation,
 broken download link
In-Reply-To: <092a74f3-3a11-18f3-7f4b-d364d585cee9@gmail.com>
References: <092a74f3-3a11-18f3-7f4b-d364d585cee9@gmail.com>
Message-ID: <541647cb-226e-de7b-c767-deec88519e9a@slackbuilds.org>

> It looks like in that case even our standard _find_ wouldn't do the job,
> since the directories have "this" special permissions.
> I might be wrong though, and I don't have enough power to analyze ;).
> 
> 
> Doing the (very) naive:
> $ grep -L ^find */*/*.SlackBuild
> 
> reveals around 150 SlackBuilds that do not use find to set permissions.
> And it's probably correct in most of the cases.
> 
> But more alarming might be the following fact:
> 
> $ grep -L ^find */*/*.SlackBuild | grep "icon-theme\|icons"
> desktop/awoken-icon-theme/awoken-icon-theme.SlackBuild
> desktop/faba-icon-theme/faba-icon-theme.SlackBuild
> desktop/faba-mono-icons/faba-mono-icons.SlackBuild
> desktop/moka-icon-theme/moka-icon-theme.SlackBuild
> desktop/numix-icon-theme-bevel/numix-icon-theme-bevel.SlackBuild
> desktop/numix-icon-theme-circle/numix-icon-theme-circle.SlackBuild
> desktop/numix-icon-theme/numix-icon-theme.SlackBuild
> 
> and it looks like in some cases we depend solely on the permissions
> provided by the tarball packager.
> Which might not work out well in every case.

Thanks for spotting it
i have fixed some packages on my branch, but not all of them have wrong
permission at the resulting packages even though they didn't use the
find command to replace it.

let us know if you still find more wrong-permission packages.

-- 
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/20160515/f7e1ca73/attachment.asc>

From thedoogster at gmail.com  Sat May 14 22:13:40 2016
From: thedoogster at gmail.com (Doogster)
Date: Sat, 14 May 2016 15:13:40 -0700
Subject: [Slackbuilds-users] DOWNLOAD advice for github
In-Reply-To: <8c64caa2-4e41-89b4-7aa8-70965f4908bb@gmail.com>
References: <CAMt7G9QagweP8TTWqwOm9nGFJpYg1iP6rK4a0tKTZ72JNYdX+A@mail.gmail.com>
 <8c64caa2-4e41-89b4-7aa8-70965f4908bb@gmail.com>
Message-ID: <CAE5oDabnE02GzaVcML5yLUj1+CWazGP=vB76+u4XpX84ABofjQ@mail.gmail.com>

Thank, David and Heinz. That's great.

On Sat, May 14, 2016 at 10:06 AM, Andrzej Telszewski
<atelszewski at gmail.com> wrote:
> On 14/05/16 18:35, David Spencer wrote:
>>
>> Hi everybody,
>>
>> For maintainers, here's some advice about what to put in DOWNLOAD in
>> the .info file for github URLs.
>>
>> NOTE: you don't need to change any of your existing files, this is
>> just some general advice that we hope you will find helpful and
>> interesting and useful. Also, this is not related to 14.2, it is
>> actually some new advice about github that Heinz worked out yesterday
>> :)
>>
>> Hopefully, most of you know already that github is "clever" with
>> download URLs. It uses an HTTP "content disposition" header to tell
>> browsers the name of the archive that githib has dynamically created.
>> But by default wget and curl do not use the "content disposition"
>> header and use the last component of the URL as a filename. Therefore
>> (until now) our SlackBuilds have needed to try both possible names for
>> the download, e.g.
>>
>> tar xvf $CWD/v$VERSION.tar.gz || tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
>>
>> So, here's the new advice: Heinz has worked out that if we use (for
>> example)
>>
>>
>> DOWNLOAD="https://github.com/trizen/clyrics/archive/0.04/clyrics-0.04.tar.gz"
>>
>> then the archive will *always* be named clyrics-0.04.tar.gz, even if
>> we use wget or curl, and so we can just do the usual tar command in
>> the SlackBuild:
>>
>> tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
>>
>> Apparently this will even work nicely for projects that include the
>> project name in the git tag, e.g.
>>
>>
>> DOWNLOAD="https://github.com/christophgysin/pasystray/archive/0.5.2/pasystray-0.5.2.tar.gz"
>>
>> so we can now stop using confusing and ugly commands like these:
>>
>> rm -rf $PRGNAM-$PRGNAM-$VERSION
>> tar xvf $CWD/$PRGNAM-$PRGNAM-$VERSION.tar.gz
>> cd $PRGNAM-$PRGNAM-$VERSION
>>
>> I hope this is helpful to you.  Thanks to Heinz for finally working
>> out the right way of handling this!
>>
>> Best regards to everybody
>> -D.
>>
>> ps. If I've made any mistakes above, corrections will be gratefully
>> received :D
>
>
> Well appreciated!
>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>>
>
>
> --
> Best regards,
> Andrzej Telszewski
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>

From mats.bertil.tegner at gmail.com  Sun May 15 12:19:09 2016
From: mats.bertil.tegner at gmail.com (Mats Bertil Tegner)
Date: Sun, 15 May 2016 14:19:09 +0200
Subject: [Slackbuilds-users] Vivaldi
In-Reply-To: <CAPsDuS5PkGkv2mPjpsD-zUfHWFY2nr4oUgoixXZAJdiqapEyqg@mail.gmail.com>
References: <CAPsDuS5PkGkv2mPjpsD-zUfHWFY2nr4oUgoixXZAJdiqapEyqg@mail.gmail.com>
Message-ID: <484fb30f-a9bc-2833-0585-c46c370cb81a@gmail.com>

On 2016-05-03 10:08, Matteo Bernardini wrote:
> It has been reported on LQ that the download link for vivaldi is broken
> 
> https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/page4.html#post5538863
> 
> I had a look at the directory where the vivaldi people publish their
> releases and concluded that they often remove old ones, breaking the
> scripts in our repository.
> 
> so I had prepared a patch in my branch to:
> - self host their tarballs avoiding breakage;
> - move from snapshots to the stable release (seems it's more up2date
> than the snapshots ;) ).
> 
> https://slackbuilds.org/cgit/slackbuilds/commit/?h=ponce-for-14.2&id=13031fffc0af538e73e9a6919a4d44aca5e89525
> 
> Matteo

A small update to Vivaldi 1.1 has been released:
https://vivaldi.net/en-US/teamblog/114-snapshot-1-2-479-8-more-keyboard-shortcuts-and-a-small-update-to-1-1
https://update.vivaldi.com/update/1.0/relnotes/1.1.453.59.html

Mats


From slackph at posteo.de  Mon May 16 14:51:46 2016
From: slackph at posteo.de (Philip Lacroix)
Date: Mon, 16 May 2016 16:51:46 +0200
Subject: [Slackbuilds-users] DOWNLOAD advice for github
In-Reply-To: <CAMt7G9QagweP8TTWqwOm9nGFJpYg1iP6rK4a0tKTZ72JNYdX+A@mail.gmail.com>
References: <CAMt7G9QagweP8TTWqwOm9nGFJpYg1iP6rK4a0tKTZ72JNYdX+A@mail.gmail.com>
Message-ID: <6bcc1988ebbf8b598974bc2b3d0b1570@posteo.de>

Am 14.05.2016 18:35 schrieb David Spencer:
> So, here's the new advice: Heinz has worked out that if we use (for 
> example)
> 
> DOWNLOAD="https://github.com/trizen/clyrics/archive/0.04/clyrics-0.04.tar.gz"
> 
> then the archive will *always* be named clyrics-0.04.tar.gz, even if
> we use wget or curl, and so we can just do the usual tar command in
> the SlackBuild

Thanks!

It might be worth to mention that this works also with commit-specific 
downloads
(useful when there are no actual releases). For example:

https://github.com/unicap/ucview/archive/29bd93aeef0573c58c9aee665dc43fdfd1f77a1f/ucview-29bd93aeef0573c58c9aee665dc43fdfd1f77a1f.tar.gz

From atelszewski at gmail.com  Mon May 16 14:57:37 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 16 May 2016 16:57:37 +0200
Subject: [Slackbuilds-users] DOWNLOAD advice for github
In-Reply-To: <6bcc1988ebbf8b598974bc2b3d0b1570@posteo.de>
References: <CAMt7G9QagweP8TTWqwOm9nGFJpYg1iP6rK4a0tKTZ72JNYdX+A@mail.gmail.com>
 <6bcc1988ebbf8b598974bc2b3d0b1570@posteo.de>
Message-ID: <4829a049-3329-fc19-f648-9206ab8eb672@gmail.com>

On 16/05/16 16:51, Philip Lacroix wrote:
> Am 14.05.2016 18:35 schrieb David Spencer:
>> So, here's the new advice: Heinz has worked out that if we use (for
>> example)
>>
>> DOWNLOAD="https://github.com/trizen/clyrics/archive/0.04/clyrics-0.04.tar.gz"
>>
>>
>> then the archive will *always* be named clyrics-0.04.tar.gz, even if
>> we use wget or curl, and so we can just do the usual tar command in
>> the SlackBuild
>
> Thanks!
>
> It might be worth to mention that this works also with commit-specific
> downloads
> (useful when there are no actual releases). For example:
>
> https://github.com/unicap/ucview/archive/29bd93aeef0573c58c9aee665dc43fdfd1f77a1f/ucview-29bd93aeef0573c58c9aee665dc43fdfd1f77a1f.tar.gz
>

I was also looking at it, but I would prefer something like:
https://github.com/unicap/ucview/archive/29bd93aeef0573c58c9aee665dc43fdfd1f77a1f/ucview-git_%DATE_%HEAD.tar.gz

but couldn't find anything that would work in this manner.

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


-- 
Best regards,
Andrzej Telszewski

From richard at aaazen.com  Tue May 17 00:58:45 2016
From: richard at aaazen.com (Richard)
Date: Mon, 16 May 2016 17:58:45 -0700 (PDT)
Subject: [Slackbuilds-users] OpenSMTPD 5.9.2p1
Message-ID: <alpine.LNX.2.11.1605161739030.478@monday.test>

There is a new version of OpenSMTPD 5.9.2p1 available.

https://opensmtpd.org/announces/release-5.9.2.txt

This is a major release with reliability fixes mostly.

Issues fixed in this release (since 5.7.3):
===========================================

- remove dead code
- tons of code cleanup and simplification
- tons of code adaptations to ease portability
- reduce memory usage by invalidating envelopes cache earlier
- simplify a great deal the smtp session code
- get rid of 'kick' mechanism, we'll reintroduce a better one
- all smtpd processes now use the pledge() API
- kill support for 'dbm' db type, it cannot be made to work for us
- introduce "listen on socket"
- enqueuer is now setgid to avoid attacks against offline queue [1]
- fix mailq / smtpctl show queue breakage
- plug two memory leaks and one descriptor leak
- fix error code path for delivery loop that can lead to a fatal()

[1] follow-up to the Qualys Security audit fixes from 5.7.3


Attached is a unified diff of /opensmtpd-5.7.3p2 and /opensmtpd-5.9.2p1

I have tested the 5.9.2p1 package in both Slackware 14.1 and current and it runs fine.

--
Richard Narron
-------------- next part --------------
diff -u -r opensmtpd-5.7.3p2/README opensmtpd-5.9.2p1/README
--- opensmtpd-5.7.3p2/README	2013-12-14 09:05:47.000000000 -0800
+++ opensmtpd-5.9.2p1/README	2016-05-16 16:48:11.983971604 -0700
@@ -5,6 +5,7 @@
 
 You must have smtpd and smtpq users and groups on the system for
 privilege separation - something like this should suffice:
+
   groupadd -g 270 smtpd
   useradd -u 270 -g 270 -r -s /bin/false -d /var/empty smtpd
   groupadd -g 271 smtpq
@@ -17,3 +18,10 @@
 This package conflicts with the stock sendmail package included in
 Slackware and overwrites some of its files, so remove the sendmail
 package before installing opensmtpd.
+
+In the change from version 5.7.3p2 to 5.9.2p1 the ownership and permissions
+changed for the /var/spool/offline directory
+
+  chown -R root:smtpq /var/spool/offline
+  chmod 770           /var/spool/offline
+
Only in opensmtpd-5.7.3p2: configure.diff
diff -u -r opensmtpd-5.7.3p2/opensmtpd.SlackBuild opensmtpd-5.9.2p1/opensmtpd.SlackBuild
--- opensmtpd-5.7.3p2/opensmtpd.SlackBuild	2016-02-03 10:53:26.000000000 -0800
+++ opensmtpd-5.9.2p1/opensmtpd.SlackBuild	2016-05-16 16:43:26.167976182 -0700
@@ -24,7 +24,7 @@
 #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 PRGNAM=opensmtpd
-VERSION=${VERSION:-5.7.3p2}
+VERSION=${VERSION:-5.9.2p1}
 EXTRAS=${EXTRAS:-5.7.1}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
@@ -85,6 +85,7 @@
 rm -rf             $PRGNAM-$VERSION
 tar xvf       $CWD/$PRGNAM-$VERSION.tar.gz
 cd                 $PRGNAM-$VERSION
+
 chown -R root:root .
 find -L . \
  \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
@@ -92,8 +93,6 @@
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
-patch -p0 <$CWD/configure.diff
-
 CFLAGS="$SLKCFLAGS" \
 CXXFLAGS="$SLKCFLAGS" \
 ./configure \
@@ -101,16 +100,17 @@
   --libdir=/usr/lib${LIBDIRSUFFIX} \
   --sysconfdir=/etc/opensmtpd \
   --localstatedir=/var \
-  --with-sock-dir=/var/run \
+  --with-path-socket=/var/run \
   --mandir=/usr/man \
   --with-mantype=doc \
   --docdir=/usr/doc/$PRGNAM-$VERSION \
   --without-rpath \
-  --with-maildir=/var/spool/mail \
-  --with-privsep-user=smtpd \
-  --with-queue-user=smtpq \
-  --with-ca-file=/etc/ssl/certs/ca-certificates.crt \
-  --enable-table-db \
+  --with-path-mbox=/var/spool/mail \
+  --with-user-smtpd=smtpd \
+  --with-user-queue=smtpq \
+  --with-group-queue=smtpq \
+  --with-path-CAfile=/etc/ssl/certs/ca-certificates.crt \
+  --with-table-db \
   --build=$ARCH-slackware-linux
 
 make
@@ -124,9 +124,10 @@
 ln -s smtpctl $PKG/usr/sbin/sendmail
 ln -s ../sbin/sendmail $PKG/usr/bin/sendmail
 
-rm -f $PKG/usr/sbin/mailq $PKG/usr/sbin/newaliases
-ln -s makemap $PKG/usr/sbin/newaliases
+rm -f $PKG/usr/sbin/mailq $PKG/usr/sbin/newaliases $PKG/usr/sbin/makemap
 ln -s smtpctl $PKG/usr/sbin/mailq
+ln -s smtpctl $PKG/usr/sbin/newaliases
+ln -s smtpctl $PKG/usr/sbin/makemap
 
 mkdir -p $PKG/etc/rc.d
 cat $CWD/rc.opensmtpd > $PKG/etc/rc.d/rc.opensmtpd.new
@@ -144,6 +145,7 @@
 
 mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
 cp -a INSTALL LICENSE README.md THANKS $PKG/usr/doc/$PRGNAM-$VERSION
+cat $CWD/README             > $PKG/usr/doc/$PRGNAM-$VERSION/README
 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
 
 mkdir -p $PKG/install
@@ -151,4 +153,4 @@
 cat $CWD/doinst.sh > $PKG/install/doinst.sh
 
 cd $PKG
-/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
+/sbin/makepkg -l y -p -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
diff -u -r opensmtpd-5.7.3p2/opensmtpd.info opensmtpd-5.9.2p1/opensmtpd.info
--- opensmtpd-5.7.3p2/opensmtpd.info	2016-02-02 11:14:13.315111387 -0800
+++ opensmtpd-5.9.2p1/opensmtpd.info	2016-05-16 15:35:04.446041883 -0700
@@ -1,8 +1,8 @@
 PRGNAM="opensmtpd"
-VERSION="5.7.3p2"
+VERSION="5.9.2p1"
 HOMEPAGE="http://www.opensmtpd.org/"
-DOWNLOAD="http://www.opensmtpd.org/archives/opensmtpd-5.7.3p2.tar.gz"
-MD5SUM="85bdccf1f28945771f79fd33e893cc43"
+DOWNLOAD="https://www.opensmtpd.org/archives/opensmtpd-5.9.2p1.tar.gz"
+MD5SUM="d109374dcc4bc8be14f790b859f1dd31"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES="libasr"

From willysr at slackbuilds.org  Tue May 17 01:50:06 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 17 May 2016 08:50:06 +0700
Subject: [Slackbuilds-users] OpenSMTPD 5.9.2p1
In-Reply-To: <alpine.LNX.2.11.1605161739030.478@monday.test>
References: <alpine.LNX.2.11.1605161739030.478@monday.test>
Message-ID: <b58b0fdb-d365-2df6-e412-ddc3e36130bd@slackbuilds.org>

> There is a new version of OpenSMTPD 5.9.2p1 available.
> 
> https://opensmtpd.org/announces/release-5.9.2.txt
> 
> This is a major release with reliability fixes mostly.

> Attached is a unified diff of /opensmtpd-5.7.3p2 and /opensmtpd-5.9.2p1
> 
> I have tested the 5.9.2p1 package in both Slackware 14.1 and current and it runs fine.

Applied in my branch

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/20160517/e405b5a7/attachment.asc>

From s.arcus at open-t.co.uk  Wed May 18 08:35:31 2016
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Wed, 18 May 2016 09:35:31 +0100
Subject: [Slackbuilds-users] Question about copyright notice in slackbuild
 script
Message-ID: <6f0bfc04-178c-e764-f093-1d2aa371df2f@open-t.co.uk>

As I've just taken over the maintenance of Syncthing at SBo, I am about 
to apply some modifications to syncthing.SlackBuild. At the top of the 
file, the copyright notice starts with:

# Copyright 2015 Lionel Young, United States

What is the correct way to amend this? Do I replace it with my own name, 
or add another line underneath such as:

# Copyright 2015 Lionel Young, United States
# Copyright 2016 Sebastian Arcus, United Kingdom

From willysr at slackbuilds.org  Wed May 18 10:31:46 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 18 May 2016 17:31:46 +0700
Subject: [Slackbuilds-users] Question about copyright notice in
 slackbuild script
In-Reply-To: <6f0bfc04-178c-e764-f093-1d2aa371df2f@open-t.co.uk>
References: <6f0bfc04-178c-e764-f093-1d2aa371df2f@open-t.co.uk>
Message-ID: <98e7d499-9d77-c752-354a-e51ec6ceea30@slackbuilds.org>

> As I've just taken over the maintenance of Syncthing at SBo, I am about
> to apply some modifications to syncthing.SlackBuild. At the top of the
> file, the copyright notice starts with:
> 
> # Copyright 2015 Lionel Young, United States
> 
> What is the correct way to amend this? Do I replace it with my own name,
> or add another line underneath such as:
> 
> # Copyright 2015 Lionel Young, United States
> # Copyright 2016 Sebastian Arcus, United Kingdom

Yes, adding is better than replacing it


-- 
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/20160518/831448c9/attachment.asc>

From s.arcus at open-t.co.uk  Thu May 19 11:47:35 2016
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Thu, 19 May 2016 12:47:35 +0100
Subject: [Slackbuilds-users] Question about copyright notice in
 slackbuild script
In-Reply-To: <98e7d499-9d77-c752-354a-e51ec6ceea30@slackbuilds.org>
References: <6f0bfc04-178c-e764-f093-1d2aa371df2f@open-t.co.uk>
 <98e7d499-9d77-c752-354a-e51ec6ceea30@slackbuilds.org>
Message-ID: <eca79545-039a-2c09-86a2-550486193b01@open-t.co.uk>

On 18/05/16 11:31, Willy Sudiarto Raharjo wrote:
>> As I've just taken over the maintenance of Syncthing at SBo, I am about
>> to apply some modifications to syncthing.SlackBuild. At the top of the
>> file, the copyright notice starts with:
>>
>> # Copyright 2015 Lionel Young, United States
>>
>> What is the correct way to amend this? Do I replace it with my own name,
>> or add another line underneath such as:
>>
>> # Copyright 2015 Lionel Young, United States
>> # Copyright 2016 Sebastian Arcus, United Kingdom
> Yes, adding is better than replacing it
Thank you!


From s.arcus at open-t.co.uk  Thu May 19 12:42:23 2016
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Thu, 19 May 2016 13:42:23 +0100
Subject: [Slackbuilds-users] Syncthing - new v0.13.0 for testing
Message-ID: <6ba381c2-aa58-0fbd-b12d-32797046ae7b@open-t.co.uk>

Please find attached update version of SBo scripts for Syncthing - for 
testing, and if all looks good, inclusion in the new 14.2 repositories. 
I have done quite a few modifications to the previous version:

1. I've rewritten rc.syncthing to start syncthing under its own user and 
group, not as root - as per the developer's recommendation and previous 
discussions on this group.
2. I've used uid and gid 307 - already added to the SBo UID/GID list 
since last year, after my posts on this list.
3. I've re-factored the slack-desk and README files, with further 
details about the software and some installation notes.
4. I've added a logrotate script to be used if Syncthing is started as 
system daemon, with logging enabled.
5. I've modified syncthing.SlackBuild to check for the existence of the 
syncthing user/group, and create appropriate log and lib dirs.
6. Obviously, the version has been bumped to v0.13.0.

I've tried to follow the SBo docs and advice, and used similar packages 
as example - but as it is my fist submission and the changes have been 
quite extensive, I would appreciate any testing and feedback.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: syncthing.tar.gz
Type: application/gzip
Size: 3481 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160519/2126c21a/attachment.bin>

From Hullen at t-online.de  Thu May 19 18:05:00 2016
From: Hullen at t-online.de (Helmut Hullen)
Date: Thu, 19 May 2016 20:05:00 +0200
Subject: [Slackbuilds-users] clamav
Message-ID: <De8xWG49CXB@helmut.hullen.de>

Hallo, slackbuilds-users,

"clamav" seems to need 2 changes:

        --enable-pcre

as additional "configure" option

and "/usr/lib/libssh2.so" as symlink to "/usr/lib/libssh2.so.1".

These 2 changes avoid the clamscan message "... but pcre is disabled  
...".

The "libssh2" symlink is (perhaps ...) only needed for compilation, not  
for running "clamscan".

Viele Gruesse!
Helmut


From matteo.bernardini at gmail.com  Thu May 19 18:20:41 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 19 May 2016 20:20:41 +0200
Subject: [Slackbuilds-users] clamav
In-Reply-To: <De8xWG49CXB@helmut.hullen.de>
References: <De8xWG49CXB@helmut.hullen.de>
Message-ID: <CAPsDuS5iEJzifa+zZU+pjgj-XzpsD_2yFFUwM5o_48oYvHGJ8w@mail.gmail.com>

2016-05-19 20:05 GMT+02:00 Helmut Hullen <Hullen at t-online.de>:
> Hallo, slackbuilds-users,
>
> "clamav" seems to need 2 changes:
>
>         --enable-pcre
>
> as additional "configure" option
>
> and "/usr/lib/libssh2.so" as symlink to "/usr/lib/libssh2.so.1".
>
> These 2 changes avoid the clamscan message "... but pcre is disabled
> ...".
>
> The "libssh2" symlink is (perhaps ...) only needed for compilation, not
> for running "clamscan".

hi Helmut,

sorry, where are you trying that and which version of the build script is that?

I just tested what we have on SBo's git master branch on a
slackware64-current full installation and I have none of the
behaviours you are describing...

Matteo

From artourter at gmail.com  Thu May 19 18:24:16 2016
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Thu, 19 May 2016 19:24:16 +0100
Subject: [Slackbuilds-users] clamav
In-Reply-To: <De8xWG49CXB@helmut.hullen.de>
References: <De8xWG49CXB@helmut.hullen.de>
Message-ID: <CAK09-vn-rn4Ac4iP09iAuVOqzQyAK1H0rNHW5Yhj4KZC8oCbcg@mail.gmail.com>

not sure why these changes should be done. using the current SlackBuild
clamscan is compiled against libpcre without the need for additional
configure flag. It is on the other hand not compiled against libssh2 but
looking at the output of configure, it doesn't try to either.

There must be something weird on your system for it not to detect your
installed pcre. Can you specify why you think there is an issue with
libssh2 (although that is not something that the clamav slackbuild could do
anyway as it is not going to change system files to allow building).

Cheers

Greg

On 19 May 2016 at 19:05, Helmut Hullen <Hullen at t-online.de> wrote:

> Hallo, slackbuilds-users,
>
> "clamav" seems to need 2 changes:
>
>         --enable-pcre
>
> as additional "configure" option
>
> and "/usr/lib/libssh2.so" as symlink to "/usr/lib/libssh2.so.1".
>
> These 2 changes avoid the clamscan message "... but pcre is disabled
> ...".
>
> The "libssh2" symlink is (perhaps ...) only needed for compilation, not
> for running "clamscan".
>
> Viele Gruesse!
> Helmut
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160519/612b76cb/attachment-0001.html>

From willysr at slackbuilds.org  Thu May 19 18:31:24 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 20 May 2016 01:31:24 +0700
Subject: [Slackbuilds-users] Syncthing - new v0.13.0 for testing
In-Reply-To: <6ba381c2-aa58-0fbd-b12d-32797046ae7b@open-t.co.uk>
References: <6ba381c2-aa58-0fbd-b12d-32797046ae7b@open-t.co.uk>
Message-ID: <26b0c88b-6d0f-e3ac-c1af-22ecae731197@slackbuilds.org>

> Please find attached update version of SBo scripts for Syncthing - for
> testing, and if all looks good, inclusion in the new 14.2 repositories.
> I have done quite a few modifications to the previous version:
> 
> 1. I've rewritten rc.syncthing to start syncthing under its own user and
> group, not as root - as per the developer's recommendation and previous
> discussions on this group.
> 2. I've used uid and gid 307 - already added to the SBo UID/GID list
> since last year, after my posts on this list.
> 3. I've re-factored the slack-desk and README files, with further
> details about the software and some installation notes.
> 4. I've added a logrotate script to be used if Syncthing is started as
> system daemon, with logging enabled.
> 5. I've modified syncthing.SlackBuild to check for the existence of the
> syncthing user/group, and create appropriate log and lib dirs.
> 6. Obviously, the version has been bumped to v0.13.0.
> 
> I've tried to follow the SBo docs and advice, and used similar packages
> as example - but as it is my fist submission and the changes have been
> quite extensive, I would appreciate any testing and feedback.

applied in my branch with minor modifications

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/20160520/0abf8fbb/attachment.asc>

From Hullen at t-online.de  Thu May 19 19:33:00 2016
From: Hullen at t-online.de (Helmut Hullen)
Date: Thu, 19 May 2016 21:33:00 +0200
Subject: [Slackbuilds-users] clamav
In-Reply-To: <CAK09-vn-rn4Ac4iP09iAuVOqzQyAK1H0rNHW5Yhj4KZC8oCbcg@mail.gmail.com>
Message-ID: <De8xkJiPCXB@helmut.hullen.de>

Hallo, Greg',

Du meintest am 19.05.16:

> not sure why these changes should be done. using the current
> SlackBuild clamscan is compiled against libpcre without the need for
> additional configure flag. It is on the other hand not compiled
> against libssh2 but looking at the output of configure, it doesn't
> try to either.

> There must be something weird on your system for it not to detect
> your installed pcre.

It had detected "pcre" only with the option "--enable-pcre". Not as  
default.

> Can you specify why you think there is an issue
> with libssh2 (although that is not something that the clamav
> slackbuild could do anyway as it is not going to change system files
> to allow building).

Quite simple: without the symlink "/usr/lib/libssh2.so" compilation  
stopped with the error message that no such "file" was found.

Viele Gruesse!
Helmut


From Hullen at t-online.de  Thu May 19 19:32:00 2016
From: Hullen at t-online.de (Helmut Hullen)
Date: Thu, 19 May 2016 21:32:00 +0200
Subject: [Slackbuilds-users] clamav
In-Reply-To: <CAPsDuS5iEJzifa+zZU+pjgj-XzpsD_2yFFUwM5o_48oYvHGJ8w@mail.gmail.com>
Message-ID: <De8xk41PCXB@helmut.hullen.de>

Hallo, Matteo,

Du meintest am 19.05.16:

>> "clamav" seems to need 2 changes:
>>
>>         --enable-pcre
>>
>> as additional "configure" option
>>
>> and "/usr/lib/libssh2.so" as symlink to "/usr/lib/libssh2.so.1".
>>
>> These 2 changes avoid the clamscan message "... but pcre is disabled
>> ...".
>>
>> The "libssh2" symlink is (perhaps ...) only needed for compilation,
>> not for running "clamscan".

> sorry, where are you trying that and which version of the build
> script is that?

Slackware-current, 32bit, only CLI, no full installation.
Continuously updated since 1995 ...

> I just tested what we have on SBo's git master branch on a
> slackware64-current full installation and I have none of the
> behaviours you are describing...

Good to know ...

Viele Gruesse!
Helmut


From matteo.bernardini at gmail.com  Thu May 19 19:39:06 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 19 May 2016 21:39:06 +0200
Subject: [Slackbuilds-users] clamav
In-Reply-To: <De8xk41PCXB@helmut.hullen.de>
References: <CAPsDuS5iEJzifa+zZU+pjgj-XzpsD_2yFFUwM5o_48oYvHGJ8w@mail.gmail.com>
 <De8xk41PCXB@helmut.hullen.de>
Message-ID: <CAPsDuS63SGotMR_2ifJZip_UgspSi7b-X3euc0yM-fXUzkeNVQ@mail.gmail.com>

2016-05-19 21:32 GMT+02:00 Helmut Hullen <Hullen at t-online.de>:
> Hallo, Matteo,
>
> Du meintest am 19.05.16:
>
>>> "clamav" seems to need 2 changes:
>>>
>>>         --enable-pcre
>>>
>>> as additional "configure" option
>>>
>>> and "/usr/lib/libssh2.so" as symlink to "/usr/lib/libssh2.so.1".
>>>
>>> These 2 changes avoid the clamscan message "... but pcre is disabled
>>> ...".
>>>
>>> The "libssh2" symlink is (perhaps ...) only needed for compilation,
>>> not for running "clamscan".
>
>> sorry, where are you trying that and which version of the build
>> script is that?
>
> Slackware-current, 32bit, only CLI, no full installation.
> Continuously updated since 1995 ...
>
>> I just tested what we have on SBo's git master branch on a
>> slackware64-current full installation and I have none of the
>> behaviours you are describing...
>
> Good to know ...

I haven't the behaviours you are describing either on a
slackware-current (32bit) full installation so I really don't know
what to suggest (beside building it on a full install)...

Matteo

From atelszewski at gmail.com  Sat May 21 00:29:28 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 21 May 2016 02:29:28 +0200
Subject: [Slackbuilds-users] Search result for exact package name
Message-ID: <cf226755-e2a3-19a9-feb0-62b61ec2252e@gmail.com>

Dear admins,

Could you implement a search query that matches exact package name and 
only that?

What I mean is something like that:

https://slackbuilds.org/result/?search=libsigrok&match=exact

which would return only "libsigrok" package(s).

This would allow for websites that want to refer to given SBo package to 
be Slackware version agnostic and would remove the need for the website 
to be updated when new Slackware arrives.

Now the links have to be something like that:
https://slackbuilds.org/repository/14.1/libraries/libsigrok/

and when 14.2 comes, the website maintainer has to be noticed in order 
to introduce the change.

Thanks!

-- 
Best regards,
Andrzej Telszewski

From ryan.q at linux.com  Sat May 21 01:49:03 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Fri, 20 May 2016 18:49:03 -0700
Subject: [Slackbuilds-users] Search result for exact package name
In-Reply-To: <cf226755-e2a3-19a9-feb0-62b61ec2252e@gmail.com>
References: <cf226755-e2a3-19a9-feb0-62b61ec2252e@gmail.com>
Message-ID: <CAAcyf-oEABHxJETV+DPM=SR9BBC4OE9rCZ0vMsK30d_rSQzzRQ@mail.gmail.com>

> Could you implement a search query that matches exact package name and
only that?
>
> What I mean is something like that:
>
> https://slackbuilds.org/result/?search=libsigrok&match=exact
>
> which would return only "libsigrok" package(s).
>
> This would allow for websites that want to refer to given SBo package to
be Slackware version agnostic and would remove the need for the website to
be updated when new Slackware arrives.

https://slackbuilds.org/apps/libsigrok/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160520/51d9cb0f/attachment.html>

From erik at slackbuilds.org  Sat May 21 04:16:17 2016
From: erik at slackbuilds.org (Erik Hanson)
Date: Fri, 20 May 2016 23:16:17 -0500
Subject: [Slackbuilds-users] Search result for exact package name
In-Reply-To: <CAAcyf-oEABHxJETV+DPM=SR9BBC4OE9rCZ0vMsK30d_rSQzzRQ@mail.gmail.com>
References: <cf226755-e2a3-19a9-feb0-62b61ec2252e@gmail.com>
 <CAAcyf-oEABHxJETV+DPM=SR9BBC4OE9rCZ0vMsK30d_rSQzzRQ@mail.gmail.com>
Message-ID: <20160520231617.31d2e22d@shaggy.doo>

On Fri, 20 May 2016 18:49:03 -0700
"Ryan P.C. McQuen" <ryan.q at linux.com> wrote:

> > Could you implement a search query that matches exact package name
> > and  
> only that?
> >
> > What I mean is something like that:
> >
> > https://slackbuilds.org/result/?search=libsigrok&match=exact
> >
> > which would return only "libsigrok" package(s).
> >
> > This would allow for websites that want to refer to given SBo
> > package to  
> be Slackware version agnostic and would remove the need for the
> website to be updated when new Slackware arrives.
> 
> https://slackbuilds.org/apps/libsigrok/

We're nearing our 10 year anniversary (June 5th) and I forget that
things like this exist. Thanks for pointing it out, I definitely would
have gone down a rabbit hole trying to figure out if I could implement
it in the website back-end.

-- 
Erik

From atelszewski at gmail.com  Sat May 21 08:39:03 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 21 May 2016 10:39:03 +0200
Subject: [Slackbuilds-users] Search result for exact package name
In-Reply-To: <CAAcyf-oEABHxJETV+DPM=SR9BBC4OE9rCZ0vMsK30d_rSQzzRQ@mail.gmail.com>
References: <cf226755-e2a3-19a9-feb0-62b61ec2252e@gmail.com>
 <CAAcyf-oEABHxJETV+DPM=SR9BBC4OE9rCZ0vMsK30d_rSQzzRQ@mail.gmail.com>
Message-ID: <396b762a-457b-dd0c-705c-8b19ce492f24@gmail.com>

On 21/05/16 03:49, Ryan P.C. McQuen wrote:
>
>> Could you implement a search query that matches exact package name and
> only that?
>>
>> What I mean is something like that:
>>
>> https://slackbuilds.org/result/?search=libsigrok&match=exact
>>
>> which would return only "libsigrok" package(s).
>>
>> This would allow for websites that want to refer to given SBo package
> to be Slackware version agnostic and would remove the need for the
> website to be updated when new Slackware arrives.
>
> https://slackbuilds.org/apps/libsigrok/
>

Thank you very much! :)

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


-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Sat May 21 10:18:53 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 21 May 2016 12:18:53 +0200
Subject: [Slackbuilds-users] Meaning of PKGARCH=$(uname -m)_custom in
 ffmpeg.SlackBuild
Message-ID: <d51cf556-c980-9e2d-528e-446d5e1ab472@gmail.com>

Hi,

ffmpeg.SlackBuild sets the package arch to $(uname -m)_custom
Why is that?

This is somehow in reference to my previous question:
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-March/015772.html

So, can the ffmpeg package built on one machine be safely used on 
another machine?

Thanks!

-- 
Best regards,
Andrzej Telszewski

From fernando.lopezjr at gmail.com  Sat May 21 14:24:40 2016
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sat, 21 May 2016 08:24:40 -0600
Subject: [Slackbuilds-users] Meaning of PKGARCH=$(uname -m)_custom in
 ffmpeg.SlackBuild
In-Reply-To: <d51cf556-c980-9e2d-528e-446d5e1ab472@gmail.com>
References: <d51cf556-c980-9e2d-528e-446d5e1ab472@gmail.com>
Message-ID: <CALrQ46B=wKawzL5-Oq=0FcRuKPq24q6S=V4=R_L2p544M1wiKQ@mail.gmail.com>

thats only the architecture of your cpu... ej. 64 bits or 32 bits. it tells
either to compile for 64bits or 32bits.

On Sat, May 21, 2016 at 4:18 AM, Andrzej Telszewski <atelszewski at gmail.com>
wrote:

> Hi,
>
> ffmpeg.SlackBuild sets the package arch to $(uname -m)_custom
> Why is that?
>
> This is somehow in reference to my previous question:
>
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-March/015772.html
>
> So, can the ffmpeg package built on one machine be safely used on another
> machine?
>
> Thanks!
>
> --
> Best regards,
> Andrzej Telszewski
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>


-- 

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

From erik at slackbuilds.org  Sat May 21 14:53:41 2016
From: erik at slackbuilds.org (Erik Hanson)
Date: Sat, 21 May 2016 09:53:41 -0500
Subject: [Slackbuilds-users] Meaning of PKGARCH=$(uname -m)_custom in
 ffmpeg.SlackBuild
In-Reply-To: <d51cf556-c980-9e2d-528e-446d5e1ab472@gmail.com>
References: <d51cf556-c980-9e2d-528e-446d5e1ab472@gmail.com>
Message-ID: <20160521095341.28d802a3@shaggy.doo>

On Sat, 21 May 2016 12:18:53 +0200
Andrzej Telszewski <atelszewski at gmail.com> wrote:

> Hi,
> 
> ffmpeg.SlackBuild sets the package arch to $(uname -m)_custom
> Why is that?
> 
> This is somehow in reference to my previous question:
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-March/015772.html
> 
> So, can the ffmpeg package built on one machine be safely used on 
> another machine?

The result is a non-portable package. It's optimized for the CPU it's
been compiled with. If you're working in an environment that consists
of modern hardware, it's probably not too relevant. Consider it a
warning that using a newer/faster machine to build the package and then
installing it on an older/slower machine might mean the binary won't run
as expected.

For your previous question, "non-redistributable binary", that's
different and it was answered here:
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-March/015773.html

-- 
Erik

From atelszewski at gmail.com  Sat May 21 15:04:46 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 21 May 2016 17:04:46 +0200
Subject: [Slackbuilds-users] Meaning of PKGARCH=$(uname -m)_custom in
 ffmpeg.SlackBuild
In-Reply-To: <20160521095341.28d802a3@shaggy.doo>
References: <d51cf556-c980-9e2d-528e-446d5e1ab472@gmail.com>
 <20160521095341.28d802a3@shaggy.doo>
Message-ID: <74d26afc-e39d-001d-0468-2f1ce6ffe2f7@gmail.com>

On 21/05/16 16:53, Erik Hanson wrote:
> On Sat, 21 May 2016 12:18:53 +0200
> Andrzej Telszewski <atelszewski at gmail.com> wrote:
>
>> Hi,
>>
>> ffmpeg.SlackBuild sets the package arch to $(uname -m)_custom
>> Why is that?
>>
>> This is somehow in reference to my previous question:
>> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-March/015772.html
>>
>> So, can the ffmpeg package built on one machine be safely used on
>> another machine?
>
> The result is a non-portable package. It's optimized for the CPU it's
> been compiled with. If you're working in an environment that consists
> of modern hardware, it's probably not too relevant. Consider it a
> warning that using a newer/faster machine to build the package and then
> installing it on an older/slower machine might mean the binary won't run
> as expected.
>

Thanks. I haven't researched the topic yet and I'm just going to ask 
here, but feel free not to answer, since the question probably does not 
belong here:

Is it possible to have ffmpeg being built as any other Slackware package is?

That is, say I build for x86_64 and it will run without any further 
concern on any x86_64, just like x86_64 Slackware packages do?

> For your previous question, "non-redistributable binary", that's
> different and it was answered here:
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-March/015773.html
>

Yes, I understand. I just wanted to make sure.

-- 
Best regards,
Andrzej Telszewski

From erik at slackbuilds.org  Sat May 21 15:30:45 2016
From: erik at slackbuilds.org (Erik Hanson)
Date: Sat, 21 May 2016 10:30:45 -0500
Subject: [Slackbuilds-users] Meaning of PKGARCH=$(uname -m)_custom in
 ffmpeg.SlackBuild
In-Reply-To: <74d26afc-e39d-001d-0468-2f1ce6ffe2f7@gmail.com>
References: <d51cf556-c980-9e2d-528e-446d5e1ab472@gmail.com>
 <20160521095341.28d802a3@shaggy.doo>
 <74d26afc-e39d-001d-0468-2f1ce6ffe2f7@gmail.com>
Message-ID: <20160521103045.6250f515@shaggy.doo>

On Sat, 21 May 2016 17:04:46 +0200
Andrzej Telszewski <atelszewski at gmail.com> wrote:

> On 21/05/16 16:53, Erik Hanson wrote:
> > On Sat, 21 May 2016 12:18:53 +0200
> > Andrzej Telszewski <atelszewski at gmail.com> wrote:
> >  
> >> Hi,
> >>
> >> ffmpeg.SlackBuild sets the package arch to $(uname -m)_custom
> >> Why is that?
> >>
> >> This is somehow in reference to my previous question:
> >> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-March/015772.html
> >>
> >> So, can the ffmpeg package built on one machine be safely used on
> >> another machine?  
> >
> > The result is a non-portable package. It's optimized for the CPU
> > it's been compiled with. If you're working in an environment that
> > consists of modern hardware, it's probably not too relevant.
> > Consider it a warning that using a newer/faster machine to build
> > the package and then installing it on an older/slower machine might
> > mean the binary won't run as expected.
> >  
> 
> Thanks. I haven't researched the topic yet and I'm just going to ask 
> here, but feel free not to answer, since the question probably does
> not belong here:
> 
> Is it possible to have ffmpeg being built as any other Slackware
> package is?

I believe so, I seem to remember something (it's been a while, memory
is fuzzy) but you either pass a single parameter, like
"--no-optimizations" or several, such as "--no-sse --nosse2
--no-mmx" ... etc. These flags are examples, you'd need to research,
look at the output of 'configure --help' and determine how to do it.

Knowing the destination hardware, you could tune it. I will say, it
seems obvious that just gutting all the optimizations would give you
an ffmpeg binary that's pointlessly slow. I doubt anyone wants this.


-- 
Erik

From atelszewski at gmail.com  Sat May 21 16:52:46 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 21 May 2016 18:52:46 +0200
Subject: [Slackbuilds-users] Meaning of PKGARCH=$(uname -m)_custom in
 ffmpeg.SlackBuild
In-Reply-To: <20160521103045.6250f515@shaggy.doo>
References: <d51cf556-c980-9e2d-528e-446d5e1ab472@gmail.com>
 <20160521095341.28d802a3@shaggy.doo>
 <74d26afc-e39d-001d-0468-2f1ce6ffe2f7@gmail.com>
 <20160521103045.6250f515@shaggy.doo>
Message-ID: <1075f8a4-f795-e60c-6aee-f7a875d42279@gmail.com>

On 21/05/16 17:30, Erik Hanson wrote:
> On Sat, 21 May 2016 17:04:46 +0200
> Andrzej Telszewski <atelszewski at gmail.com> wrote:
>
>> On 21/05/16 16:53, Erik Hanson wrote:
>>> On Sat, 21 May 2016 12:18:53 +0200
>>> Andrzej Telszewski <atelszewski at gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> ffmpeg.SlackBuild sets the package arch to $(uname -m)_custom
>>>> Why is that?
>>>>
>>>> This is somehow in reference to my previous question:
>>>> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-March/015772.html
>>>>
>>>> So, can the ffmpeg package built on one machine be safely used on
>>>> another machine?
>>>
>>> The result is a non-portable package. It's optimized for the CPU
>>> it's been compiled with. If you're working in an environment that
>>> consists of modern hardware, it's probably not too relevant.
>>> Consider it a warning that using a newer/faster machine to build
>>> the package and then installing it on an older/slower machine might
>>> mean the binary won't run as expected.
>>>
>>
>> Thanks. I haven't researched the topic yet and I'm just going to ask
>> here, but feel free not to answer, since the question probably does
>> not belong here:
>>
>> Is it possible to have ffmpeg being built as any other Slackware
>> package is?
>
> I believe so, I seem to remember something (it's been a while, memory
> is fuzzy) but you either pass a single parameter, like
> "--no-optimizations" or several, such as "--no-sse --nosse2
> --no-mmx" ... etc. These flags are examples, you'd need to research,
> look at the output of 'configure --help' and determine how to do it.
>
> Knowing the destination hardware, you could tune it. I will say, it
> seems obvious that just gutting all the optimizations would give you
> an ffmpeg binary that's pointlessly slow. I doubt anyone wants this.
>
>

Thanks. Based on what you say, it's just gonna be easier to build on the 
target machine.

-- 
Best regards,
Andrzej Telszewski

From artourter at gmail.com  Sat May 21 23:50:51 2016
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Sun, 22 May 2016 00:50:51 +0100
Subject: [Slackbuilds-users] updates to my packages
Message-ID: <CAK09-vmRi+=XCCaA1_46hp7te=XYdZKGn712Q7gqmJhRtGJ_fg@mail.gmail.com>

I have put updates to nltk (3.2.1), shorewall{,6,-core} (5.0.8.2) and
kbibtex (0.6) on my github repo (https://github.com/ArTourter/Slackbuilds).
I know I have a  key set up somewhere for the slackbuilds git repo but I am
not sure how best to migrate to it.

If grabbing off github is not practical, I can sent the tarballs or wait
for the submissions to be reopen.

Cheers

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

From willysr at slackbuilds.org  Sun May 22 01:02:44 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 22 May 2016 08:02:44 +0700
Subject: [Slackbuilds-users] updates to my packages
In-Reply-To: <CAK09-vmRi+=XCCaA1_46hp7te=XYdZKGn712Q7gqmJhRtGJ_fg@mail.gmail.com>
References: <CAK09-vmRi+=XCCaA1_46hp7te=XYdZKGn712Q7gqmJhRtGJ_fg@mail.gmail.com>
Message-ID: <c4a0009e-9fb9-149a-8975-a66e6b02c067@slackbuilds.org>

> I have put updates to nltk (3.2.1), shorewall{,6,-core} (5.0.8.2) and
> kbibtex (0.6) on my github repo (https://github.com/ArTourter/Slackbuilds).
> I know I have a  key set up somewhere for the slackbuilds git repo but I am
> not sure how best to migrate to it.
> 
> If grabbing off github is not practical, I can sent the tarballs or wait
> for the submissions to be reopen.

Hi Greg

I can grab changes from your github repo, but if possible, please
rebase it from latest SBo GIT master branch.
At this moment, i saw a multiple commits on shorewall*. Probably better
to use a single commit for each package

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/20160522/fb033899/attachment.asc>

From kingbeowulf at gmail.com  Sun May 22 06:10:27 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 21 May 2016 23:10:27 -0700
Subject: [Slackbuilds-users] 14.2RC Updates for SBo packages as of kernel
 4.4.10
Message-ID: <72de72e9-457c-b155-93e2-23aea4a18c3f@gmail.com>

There are a number of updates for my packages; you can find them here:

http://www.linuxgalaxy.org/files/sbo-testing/
http://www.koenigcomputers.com/sbo-testing/

=======
Minor
=======
CImg               Version update

=======
Major
=======
murmur	Version update, upstream bugfixes/security
mumble	Version and feature update, upstream bugfixes/security

***NOTE: text-to-speech is now an available option in mumble with
SPEECHD=yes
 and requires additional optional dependencies:
-You will need one text-to-speech engine installed. For example:
   flite      on SBo, not working, no deps (optional voices)
   festival   not on SBo, not tested
   espeak     on Sbo tested/working, requires portaudio (on SBo)

-New dependency packages:
   accessibility/speech-dispatcher  (speechd)
   libraries/dotconf





-------------- 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/20160521/caea5052/attachment.asc>

From khronosschoty at utmail.net  Mon May 23 20:29:07 2016
From: khronosschoty at utmail.net (Vasily Sora)
Date: Mon, 23 May 2016 13:29:07 -0700
Subject: [Slackbuilds-users] fbreader fails to build with gtk option
In-Reply-To: <mailman.119.1463874655.3056.slackbuilds-users@slackbuilds.org>
References: <mailman.119.1463874655.3056.slackbuilds-users@slackbuilds.org>
Message-ID: <dc94f62c-89a1-8ca5-83a3-cfadddbaba37@utmail.net>

When I try and compile fbreader on current with the gtk option I get
this error:

Compiling ZLGtkUtil.o ...In file included from ZLGtkUtil.cpp:24:0:
ZLGtkDialogManager.h: In static member function 'static void
ZLGtkDialogManager::createInstance()':
ZLGtkDialogManager.h:33:70: error: invalid new-expression of abstract
class type 'ZLGtkDialogManager'
  static void createInstance() { ourInstance = new ZLGtkDialogManager(); }
                                                                      ^
ZLGtkDialogManager.h:30:7: note:   because the following virtual
functions are pure within 'ZLGtkDialogManager':
 class ZLGtkDialogManager : public ZLDialogManager {
       ^
In file included from ZLGtkDialogManager.h:28:0,
                 from ZLGtkUtil.cpp:24:
/home/tmp/SBo/fbreader-0.99.4/zlibrary/ui/../../zlibrary/core/include/ZLDialogManager.h:76:35:
note: 	virtual shared_ptr<ZLTreeDialog>
ZLDialogManager::createTreeDialog(const ZLResource&) const
  virtual shared_ptr<ZLTreeDialog> createTreeDialog(const ZLResource
&resource) const = 0;
                                   ^
/home/tmp/SBo/fbreader-0.99.4/zlibrary/ui/../../zlibrary/core/include/ZLDialogManager.h:88:39:
note: 	virtual shared_ptr<ZLProgressDialog>
ZLDialogManager::createProgressDialog(const ZLResourceKey&, bool) const
  virtual shared_ptr<ZLProgressDialog> createProgressDialog(const
ZLResourceKey &key, bool network) const = 0;
                                       ^
/home/tmp/SBo/fbreader-0.99.4/zlibrary/ui/../../makefiles/gtksubdir.mk:19:
recipe for target 'ZLGtkUtil.o' failed
make[2]: *** [ZLGtkUtil.o] Error 1
make[2]: Leaving directory
'/home/tmp/SBo/fbreader-0.99.4/zlibrary/ui/src/gtk/dialogs'
Makefile:94: recipe for target '.objects' failed
make[1]: *** [.objects] Error 1
make[1]: Leaving directory '/home/tmp/SBo/fbreader-0.99.4/zlibrary/ui'
Makefile:9: recipe for target 'all' failed
make: *** [all] Error 1

From willysr at slackbuilds.org  Mon May 23 20:52:12 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 24 May 2016 03:52:12 +0700
Subject: [Slackbuilds-users] fbreader fails to build with gtk option
In-Reply-To: <dc94f62c-89a1-8ca5-83a3-cfadddbaba37@utmail.net>
References: <mailman.119.1463874655.3056.slackbuilds-users@slackbuilds.org>
 <dc94f62c-89a1-8ca5-83a3-cfadddbaba37@utmail.net>
Message-ID: <178af5ff-2c91-6eff-a68d-117b63a4e20a@slackbuilds.org>

> When I try and compile fbreader on current with the gtk option I get
> this error:
> 
> Compiling ZLGtkUtil.o ...In file included from ZLGtkUtil.cpp:24:0:
> ZLGtkDialogManager.h: In static member function 'static void
> ZLGtkDialogManager::createInstance()':
> ZLGtkDialogManager.h:33:70: error: invalid new-expression of abstract
> class type 'ZLGtkDialogManager'
>   static void createInstance() { ourInstance = new ZLGtkDialogManager(); }
>                                                                       ^
> ZLGtkDialogManager.h:30:7: note:   because the following virtual
> functions are pure within 'ZLGtkDialogManager':
>  class ZLGtkDialogManager : public ZLDialogManager {
>        ^
> In file included from ZLGtkDialogManager.h:28:0,
>                  from ZLGtkUtil.cpp:24:
> /home/tmp/SBo/fbreader-0.99.4/zlibrary/ui/../../zlibrary/core/include/ZLDialogManager.h:76:35:
> note: 	virtual shared_ptr<ZLTreeDialog>
> ZLDialogManager::createTreeDialog(const ZLResource&) const
>   virtual shared_ptr<ZLTreeDialog> createTreeDialog(const ZLResource
> &resource) const = 0;
>                                    ^
> /home/tmp/SBo/fbreader-0.99.4/zlibrary/ui/../../zlibrary/core/include/ZLDialogManager.h:88:39:
> note: 	virtual shared_ptr<ZLProgressDialog>
> ZLDialogManager::createProgressDialog(const ZLResourceKey&, bool) const
>   virtual shared_ptr<ZLProgressDialog> createProgressDialog(const
> ZLResourceKey &key, bool network) const = 0;
>                                        ^
> /home/tmp/SBo/fbreader-0.99.4/zlibrary/ui/../../makefiles/gtksubdir.mk:19:
> recipe for target 'ZLGtkUtil.o' failed
> make[2]: *** [ZLGtkUtil.o] Error 1
> make[2]: Leaving directory
> '/home/tmp/SBo/fbreader-0.99.4/zlibrary/ui/src/gtk/dialogs'
> Makefile:94: recipe for target '.objects' failed
> make[1]: *** [.objects] Error 1
> make[1]: Leaving directory '/home/tmp/SBo/fbreader-0.99.4/zlibrary/ui'
> Makefile:9: recipe for target 'all' failed
> make: *** [all] Error 1

Since it's no longer maintained upstream and qt4 interface works, i will
remove the GTK UI part in my branch until someone give better solution.


-- 
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/20160524/904abbf1/attachment.asc>

From jjalmeida at gmail.com  Thu May 26 09:57:09 2016
From: jjalmeida at gmail.com (Jorge Almeida)
Date: Thu, 26 May 2016 02:57:09 -0700
Subject: [Slackbuilds-users] rust
Message-ID: <CAKpSnpL-iynZYtRgT-ax3_FuoSfbRy+k2G-sJ1jeLi4JoLNqEA@mail.gmail.com>

Compilation goes OK. However:

$  rustc --version
rustc 1.5.0 (3d7cd77e4 2015-12-04)

$ rustc hello_world.rs
hello_world.rs:1:1: 1:1 error: can't find crate for `std` [E0463]
hello_world.rs:1 fn main() {
                 ^
error: aborting due to previous error

$ cat hello_world.rs
fn main() {
    println!("Hello, world!");
}

TIA

Jorge Almeida

From didier at slint.fr  Thu May 26 12:20:59 2016
From: didier at slint.fr (Didier Spaier)
Date: Thu, 26 May 2016 14:20:59 +0200
Subject: [Slackbuilds-users] Wrong characters in slack-descs
Message-ID: <095a0574-d1a9-7ed9-f6a6-ea515082f1b9@slint.fr>

Hi admins and list,

A warning from "slapt-get -u" told me that there are erroneous characters in:
http://packages.slackonly.com/pub/packages/current-x86_64/PACKAGES.TXT

Obviously they are in the description coming from the slack-descs.

To find out I have run this script a copy of Ponce's git repo for -current:
? ---
#/bin/sh
LANG=en
rm -f liste errors
for d in $(find -name slack-desc -exec dirname '{}' ';'); do
  printf "%b" "\n$d/slack-desc" >> liste
  iconv -f UTF-8 -t ASCII $d/slack-desc 1>/dev/null  2>> liste
done
sed -n "/illegal/s/iconv//p" liste|sort > errors
rm -f liste
? ---

The file "errors" is attached.

These errors prevent displaying the package's description in packages tools.

FYI I find geany handy to highlight the offending characters.

My findings are for Slackware-current, maybe 14.1 could be scanned as well.

Cheers, Didier
-------------- next part --------------
./academic/mafft/slack-desc: illegal input sequence at position 734
./academic/spades/slack-desc: illegal input sequence at position 551
./audio/abcde/slack-desc: illegal input sequence at position 761
./audio/aften/slack-desc: illegal input sequence at position 698
./desktop/faba-icon-theme/slack-desc: illegal input sequence at position 880
./development/avra/slack-desc: illegal input sequence at position 644
./development/casperjs/slack-desc: illegal input sequence at position 698
./development/love-legacy072/slack-desc: illegal input sequence at position 618
./development/love-legacy080/slack-desc: illegal input sequence at position 574
./development/love/slack-desc: illegal input sequence at position 555
./development/mcrl2/slack-desc: illegal input sequence at position 778
./development/nodejs/slack-desc: illegal input sequence at position 546
./development/pycharm/slack-desc: illegal input sequence at position 554
./development/pyvim/slack-desc: illegal input sequence at position 699
./development/regexxer/slack-desc: illegal input sequence at position 697
./games/cutemaze/slack-desc: illegal input sequence at position 764
./games/instead/slack-desc: illegal input sequence at position 570
./games/marathon-rubicon-data/slack-desc: illegal input sequence at position 742
./games/playonlinux/slack-desc: illegal input sequence at position 548
./games/pybik/slack-desc: illegal input sequence at position 583
./games/qxw/slack-desc: illegal input sequence at position 649
./games/scribble/slack-desc: illegal input sequence at position 556
./games/smashbattle/slack-desc: illegal input sequence at position 524
./games/tome4/slack-desc: illegal input sequence at position 512
./gis/polyline/slack-desc: illegal input sequence at position 628
./graphics/Alchemy/slack-desc: illegal input sequence at position 684
./graphics/draftsight/slack-desc: illegal input sequence at position 740
./graphics/triangulizor/slack-desc: illegal input sequence at position 638
./graphics/unpaper/slack-desc: illegal input sequence at position 1049
./haskell/haskell-tf-random/slack-desc: illegal input sequence at position 979
./libraries/avbin/slack-desc: illegal input sequence at position 627
./libraries/ganv/slack-desc: illegal input sequence at position 591
./libraries/hoedown/slack-desc: illegal input sequence at position 713
./libraries/libclaw/slack-desc: illegal input sequence at position 695
./libraries/libsuinput/slack-desc: illegal input sequence at position 514
./libraries/pyte/slack-desc: illegal input sequence at position 547
./libraries/tDOM/slack-desc: illegal input sequence at position 944
./libraries/webkit2gtk/slack-desc: illegal input sequence at position 806
./misc/discount/slack-desc: illegal input sequence at position 627
./misc/gourmet/slack-desc: illegal input sequence at position 569
./misc/libydpdict/slack-desc: illegal input sequence at position 834
./misc/utimer/slack-desc: illegal input sequence at position 495
./misc/ydpdict/slack-desc: illegal input sequence at position 814
./multimedia/OpenLP/slack-desc: illegal input sequence at position 571
./multimedia/x264/slack-desc: illegal input sequence at position 729
./multimedia/yarock/slack-desc: illegal input sequence at position 614
./network/QuiteRSS/slack-desc: illegal input sequence at position 643
./office/LanguageTool/slack-desc: illegal input sequence at position 612
./python/numpydoc/slack-desc: illegal input sequence at position 552
./python/python-notify2/slack-desc: illegal input sequence at position 759
./python/python-orbited/slack-desc: illegal input sequence at position 876
./python/python-xlwt/slack-desc: illegal input sequence at position 557
./python/pyzmq/slack-desc: illegal input sequence at position 520
./python/wcwidth/slack-desc: illegal input sequence at position 607
./system/autoarchive/slack-desc: illegal input sequence at position 929
./system/ded/slack-desc: illegal input sequence at position 542
./system/guix/slack-desc: illegal input sequence at position 924
./system/isight-firmware-tools/slack-desc: illegal input sequence at position 995
./system/man-pages-es/slack-desc: illegal input sequence at position 522
./system/man-pages-ja/slack-desc: illegal input sequence at position 578
./system/reptyr/slack-desc: illegal input sequence at position 746
./system/the_silver_searcher/slack-desc: illegal input sequence at position 787
./system/unac/slack-desc: illegal input sequence at position 633
-------------- 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/20160526/196c2f35/attachment-0001.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/20160526/196c2f35/attachment-0001.asc>

From matteo.bernardini at gmail.com  Thu May 26 12:55:38 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 26 May 2016 14:55:38 +0200
Subject: [Slackbuilds-users] Wrong characters in slack-descs
In-Reply-To: <095a0574-d1a9-7ed9-f6a6-ea515082f1b9@slint.fr>
References: <095a0574-d1a9-7ed9-f6a6-ea515082f1b9@slint.fr>
Message-ID: <CAPsDuS6L4-MxJ6-+Uj93+biiX-j2FmZ+7d57vS_tnvc+XV1EZg@mail.gmail.com>

2016-05-26 14:20 GMT+02:00 Didier Spaier <didier at slint.fr>:
> Hi admins and list,
>
> A warning from "slapt-get -u" told me that there are erroneous characters in:
> http://packages.slackonly.com/pub/packages/current-x86_64/PACKAGES.TXT
>
> Obviously they are in the description coming from the slack-descs.
>
> To find out I have run this script a copy of Ponce's git repo for -current:
> ? ---
> #/bin/sh
> LANG=en
> rm -f liste errors
> for d in $(find -name slack-desc -exec dirname '{}' ';'); do
>   printf "%b" "\n$d/slack-desc" >> liste
>   iconv -f UTF-8 -t ASCII $d/slack-desc 1>/dev/null  2>> liste
> done
> sed -n "/illegal/s/iconv//p" liste|sort > errors
> rm -f liste
> ? ---
>
> The file "errors" is attached.
>
> These errors prevent displaying the package's description in packages tools.
>
> FYI I find geany handy to highlight the offending characters.
>
> My findings are for Slackware-current, maybe 14.1 could be scanned as well.

thanks Didier, good catch!

I'll have a look. most probably those utf8 characters disguised as
ascii slipped because we use utf8 editors so we didn't spotted them at
all.

I'll do a dedicated branch for them.

Matteo

From lramos.prof at yahoo.com.br  Thu May 26 13:46:25 2016
From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos)
Date: Thu, 26 May 2016 10:46:25 -0300
Subject: [Slackbuilds-users] libdv: a problem and a possible fix
Message-ID: <20160526134624.GA28929@giustizia>

Hello,

recently I've built libdv using the slackbuild, and got a problem.

Basically, the source libdv/enc_input.c uses a macro (VIDEO_MAX_FRAME)
possibly defined in /usr/include/linux/videodev.h. Looking at that file,
the macro isn't defined, and so the build process stop with a proper
error.

I have to say I'm not using the stock kernel, but 3.16.3. I 
don't know if this problem is specific to this kernel or if it applies
to the stock 14.1 kernel as well (or to -current).

Making some investigation, I've found that this macro is defined at
/usr/include/linux/videodev2.h, and it's defined with 32. Also,
at least one case was solved defining this macro at the application
level, such as
https://lists.debian.org/debian-glibc/2006/07/msg00149.html, for
instance (although recognizing this case is not about libdv at all).

What I did was defining that macro in libdv/enc_input.c if it's not
still not defined. I've built a patch to that file and included it at
the SlackBuild script. The git patch goes attached.

Another option, which I didn't try, was to substitute #include videodev.h to
#include videodev2.h.

Hope this can help the community!

Cheers,

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

-------------- next part --------------
>From 545f558d8e93bbde200b8ad51f8e87c572c1b69e Mon Sep 17 00:00:00 2001
From: Luiz Ramos <lramos.prof at yahoo.com.br>
Date: Thu, 26 May 2016 10:23:07 -0300
Subject: [PATCH] libraries/libdv: fixed compilation

Included a patch to libdv/enc_input.c, to define VIDEO_MAX_FRAME if
/usr/include/linux/videodev.h doesn't have it already defined.

-- Luiz Ramos, 26/May/2016
---
 libraries/libdv/01-define-video-max-frame.patch | 13 +++++++++++++
 libraries/libdv/libdv.SlackBuild                |  2 ++
 2 files changed, 15 insertions(+)
 create mode 100644 libraries/libdv/01-define-video-max-frame.patch

diff --git a/libraries/libdv/01-define-video-max-frame.patch b/libraries/libdv/01-define-video-max-frame.patch
new file mode 100644
index 0000000000000000000000000000000000000000..4074b5b4b675810e2aac4ffe4f02b36d6fa123ee
--- /dev/null
+++ b/libraries/libdv/01-define-video-max-frame.patch
@@ -0,0 +1,13 @@
+diff -urpN a/libdv/enc_input.c b/libdv/enc_input.c
+--- a/libdv/enc_input.c	2004-10-20 00:49:24.000000000 -0300
++++ b/libdv/enc_input.c	2016-05-25 23:26:24.211085619 -0300
+@@ -51,6 +51,9 @@
+ #define _LINUX_TIME_H
+ #include <sys/types.h>
+ #include <linux/videodev.h>
++#ifndef VIDEO_MAX_FRAME
++#define VIDEO_MAX_FRAME	32
++#endif
+ #include <sys/time.h>
+ #include <unistd.h>
+ #include <fcntl.h>
diff --git a/libraries/libdv/libdv.SlackBuild b/libraries/libdv/libdv.SlackBuild
index 845e7d9076c091f4fb3dc8020c861edee82afd07..50d14671002bcdc8c5f2ccdb3d71b880172a9af4 100644
--- a/libraries/libdv/libdv.SlackBuild
+++ b/libraries/libdv/libdv.SlackBuild
@@ -83,6 +83,8 @@ CXXFLAGS="$SLKCFLAGS" \
   --disable-gtktest \
   --build=$ARCH-slackware-linux
 
+patch -p1 -i${CWD}/01-define-video-max-frame.patch
+
 make
 make install-strip DESTDIR=$PKG
 
-- 
2.8.2


From kingbeowulf at gmail.com  Thu May 26 13:49:32 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 26 May 2016 06:49:32 -0700
Subject: [Slackbuilds-users] rust
In-Reply-To: <CAKpSnpL-iynZYtRgT-ax3_FuoSfbRy+k2G-sJ1jeLi4JoLNqEA@mail.gmail.com>
References: <CAKpSnpL-iynZYtRgT-ax3_FuoSfbRy+k2G-sJ1jeLi4JoLNqEA@mail.gmail.com>
Message-ID: <CAPiArqNoq_gnW25_BOwBp1AZUUTcDtP0jFsZPSVhn6doXWO8xw@mail.gmail.com>

On Thursday, May 26, 2016, Jorge Almeida <jjalmeida at gmail.com> wrote:

> Compilation goes OK. However:
>
> $  rustc --version
> rustc 1.5.0 (3d7cd77e4 2015-12-04)
>
> $ rustc hello_world.rs
> hello_world.rs:1:1: 1:1 error: can't find crate for `std` [E0463]
> hello_world.rs:1 fn main() {
>                  ^
> error: aborting due to previous error
>
> $ cat hello_world.rs
> fn main() {
>     println!("Hello, world!");
> }
>
> TIA
>
> Jorge Almeida
>
>
maybe this:
 https://github.com/ubuntu/ubuntu-make/issues/213



-- 
You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160526/9d9734c8/attachment.html>

From belka at caraus.de  Thu May 26 14:09:20 2016
From: belka at caraus.de (Eugen Wissner)
Date: Thu, 26 May 2016 16:09:20 +0200
Subject: [Slackbuilds-users] rust
In-Reply-To: <CAPiArqNoq_gnW25_BOwBp1AZUUTcDtP0jFsZPSVhn6doXWO8xw@mail.gmail.com>
References: <CAKpSnpL-iynZYtRgT-ax3_FuoSfbRy+k2G-sJ1jeLi4JoLNqEA@mail.gmail.com>
 <CAPiArqNoq_gnW25_BOwBp1AZUUTcDtP0jFsZPSVhn6doXWO8xw@mail.gmail.com>
Message-ID: <1464271760.2429.2.camel@caraus.de>

I don't think so. If I remember correctly, this script doesn't install
the rust stdlib from the official package,??rust-std-x86_64-unknown-
linux-gnu directory in the official binary package for x86_64.
And there is already version 1.8.0. I would advice always to use the
newest version in this case since rust is a young language and it has a
lot of breaking changes between the versions. You can try to install
with install.sh in the root directory of the official binary
distribution. It may give you a better user experience.

Am Donnerstag, den 26.05.2016, 06:49 -0700 schrieb King Beowulf:
> On Thursday, May 26, 2016, Jorge Almeida <jjalmeida at gmail.com> wrote:
> > Compilation goes OK. However:
> > 
> > $? rustc --version
> > rustc 1.5.0 (3d7cd77e4 2015-12-04)
> > 
> > $ rustc hello_world.rs
> > hello_world.rs:1:1: 1:1 error: can't find crate for `std` [E0463]
> > hello_world.rs:1 fn main() {
> > ? ? ? ? ? ? ? ? ?^
> > error: aborting due to previous error
> > 
> > $ cat hello_world.rs
> > fn main() {
> > ? ? println!("Hello, world!");
> > }
> > 
> > TIA
> > 
> > Jorge Almeida
> > 
> > 
> maybe this:
> ?https://github.com/ubuntu/ubuntu-make/issues/213
> 
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
> 

From willysr at slackbuilds.org  Thu May 26 14:22:34 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 26 May 2016 21:22:34 +0700
Subject: [Slackbuilds-users] libdv: a problem and a possible fix
In-Reply-To: <20160526134624.GA28929@giustizia>
References: <20160526134624.GA28929@giustizia>
Message-ID: <059a7ce4-4cf2-a840-52ef-a25a632e5546@slackbuilds.org>

> recently I've built libdv using the slackbuild, and got a problem.
> 
> Basically, the source libdv/enc_input.c uses a macro (VIDEO_MAX_FRAME)
> possibly defined in /usr/include/linux/videodev.h. Looking at that file,
> the macro isn't defined, and so the build process stop with a proper
> error.
> 
> I have to say I'm not using the stock kernel, but 3.16.3. I 
> don't know if this problem is specific to this kernel or if it applies
> to the stock 14.1 kernel as well (or to -current).
> 
> Making some investigation, I've found that this macro is defined at
> /usr/include/linux/videodev2.h, and it's defined with 32. Also,
> at least one case was solved defining this macro at the application
> level, such as
> https://lists.debian.org/debian-glibc/2006/07/msg00149.html, for
> instance (although recognizing this case is not about libdv at all).
> 
> What I did was defining that macro in libdv/enc_input.c if it's not
> still not defined. I've built a patch to that file and included it at
> the SlackBuild script. The git patch goes attached.
> 
> Another option, which I didn't try, was to substitute #include videodev.h to
> #include videodev2.h.
> 
> Hope this can help the community!

Hi Luiz

May i know which Slackware version do you use ?
14.1 or current?



-- 
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/20160526/337d45a5/attachment.asc>

From jjalmeida at gmail.com  Thu May 26 14:30:37 2016
From: jjalmeida at gmail.com (Jorge Almeida)
Date: Thu, 26 May 2016 07:30:37 -0700
Subject: [Slackbuilds-users] rust
In-Reply-To: <1464271760.2429.2.camel@caraus.de>
References: <CAKpSnpL-iynZYtRgT-ax3_FuoSfbRy+k2G-sJ1jeLi4JoLNqEA@mail.gmail.com>
 <CAPiArqNoq_gnW25_BOwBp1AZUUTcDtP0jFsZPSVhn6doXWO8xw@mail.gmail.com>
 <1464271760.2429.2.camel@caraus.de>
Message-ID: <CAKpSnpK9jSNJcWmkQGnK0YTV=0mgPg+Dg6tE9mxRmT_5-fPA2g@mail.gmail.com>

On Thu, May 26, 2016 at 7:09 AM, Eugen Wissner <belka at caraus.de> wrote:
> I don't think so. If I remember correctly, this script doesn't install
> the rust stdlib from the official package,  rust-std-x86_64-unknown-
> linux-gnu directory in the official binary package for x86_64.
> And there is already version 1.8.0. I would advice always to use the
> newest version in this case since rust is a young language and it has a
> lot of breaking changes between the versions. You can try to install
> with install.sh in the root directory of the official binary
> distribution. It may give you a better user experience.
>

Actually, I tried 1.8.0 first, and after it failed with the same
problem I tried 1.5.0, just to do it by the book. It seems the
slackbuild is not right. The install.sh is a 1010 pages shell script.
I suppose the documentation is the code itself.
Thanks anyway

Jorge Almeida

From belka at caraus.de  Thu May 26 14:49:03 2016
From: belka at caraus.de (Eugen Wissner)
Date: Thu, 26 May 2016 16:49:03 +0200
Subject: [Slackbuilds-users] rust
In-Reply-To: <CAKpSnpK9jSNJcWmkQGnK0YTV=0mgPg+Dg6tE9mxRmT_5-fPA2g@mail.gmail.com>
References: <CAKpSnpL-iynZYtRgT-ax3_FuoSfbRy+k2G-sJ1jeLi4JoLNqEA@mail.gmail.com>
 <CAPiArqNoq_gnW25_BOwBp1AZUUTcDtP0jFsZPSVhn6doXWO8xw@mail.gmail.com>
 <1464271760.2429.2.camel@caraus.de>
 <CAKpSnpK9jSNJcWmkQGnK0YTV=0mgPg+Dg6tE9mxRmT_5-fPA2g@mail.gmail.com>
Message-ID: <1464274143.2429.6.camel@caraus.de>

Hi Jorge,

Yes the build script is broken since it doesn't install everything.
I mean everything you have to do is to unpack the downloaded rust
distribution:
tar zxf rust-1.5.0-x86_64-unknown-linux-gnu.tar.gz

And move the?rust-1.5.0-x86_64-unknown-linux-gnu/rust-std-x86_64-
unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/
to?/usr/lib64/rustlib/:

mv rust-1.5.0-x86_64-unknown-linux-gnu/rust-std-x86_64-unknown-linux-
gnu/lib/rustlib/x86_64-unknown-linux-gnu/ /usr/lib64/rustlib/

and it will work.
For 1.8.0 and 32bit it should be similar.

Eugene

Am Donnerstag, den 26.05.2016, 07:30 -0700 schrieb Jorge Almeida:
> On Thu, May 26, 2016 at 7:09 AM, Eugen Wissner <belka at caraus.de>
> wrote:
> > 
> > I don't think so. If I remember correctly, this script doesn't
> > install
> > the rust stdlib from the official package,??rust-std-x86_64-
> > unknown-
> > linux-gnu directory in the official binary package for x86_64.
> > And there is already version 1.8.0. I would advice always to use
> > the
> > newest version in this case since rust is a young language and it
> > has a
> > lot of breaking changes between the versions. You can try to
> > install
> > with install.sh in the root directory of the official binary
> > distribution. It may give you a better user experience.
> > 
> Actually, I tried 1.8.0 first, and after it failed with the same
> problem I tried 1.5.0, just to do it by the book. It seems the
> slackbuild is not right. The install.sh is a 1010 pages shell script.
> I suppose the documentation is the code itself.
> Thanks anyway
> 
> Jorge Almeida
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
> 

From jjalmeida at gmail.com  Thu May 26 15:41:22 2016
From: jjalmeida at gmail.com (Jorge Almeida)
Date: Thu, 26 May 2016 08:41:22 -0700
Subject: [Slackbuilds-users] rust
In-Reply-To: <1464274143.2429.6.camel@caraus.de>
References: <CAKpSnpL-iynZYtRgT-ax3_FuoSfbRy+k2G-sJ1jeLi4JoLNqEA@mail.gmail.com>
 <CAPiArqNoq_gnW25_BOwBp1AZUUTcDtP0jFsZPSVhn6doXWO8xw@mail.gmail.com>
 <1464271760.2429.2.camel@caraus.de>
 <CAKpSnpK9jSNJcWmkQGnK0YTV=0mgPg+Dg6tE9mxRmT_5-fPA2g@mail.gmail.com>
 <1464274143.2429.6.camel@caraus.de>
Message-ID: <CAKpSnpLb9_S7J7BVEpsggavg4uA2N-Vg3OJnyvHt_o6zKLVy6g@mail.gmail.com>

On Thu, May 26, 2016 at 7:49 AM, Eugen Wissner <belka at caraus.de> wrote:
> Hi Jorge,
>
> Yes the build script is broken since it doesn't install everything.
> I mean everything you have to do is to unpack the downloaded rust
> distribution:
> tar zxf rust-1.5.0-x86_64-unknown-linux-gnu.tar.gz
>
> And move the rust-1.5.0-x86_64-unknown-linux-gnu/rust-std-x86_64-
> unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/
> to /usr/lib64/rustlib/:
>
> mv rust-1.5.0-x86_64-unknown-linux-gnu/rust-std-x86_64-unknown-linux-
> gnu/lib/rustlib/x86_64-unknown-linux-gnu/ /usr/lib64/rustlib/
>
> and it will work.
> For 1.8.0 and 32bit it should be similar.
>

I edited the Slackbuild according to your instructions (as I didn't
want to pollute the filesystem with stuff unknown to the Slackware
packaging system). Sure enough, it works fine now (with version 1.8.0,
32bit system)

Thanks!

Jorge

From lramos.prof at yahoo.com.br  Thu May 26 16:36:03 2016
From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos)
Date: Thu, 26 May 2016 13:36:03 -0300
Subject: [Slackbuilds-users] libdv: a problem and a possible fix
In-Reply-To: <059a7ce4-4cf2-a840-52ef-a25a632e5546@slackbuilds.org>
References: <20160526134624.GA28929@giustizia>
 <059a7ce4-4cf2-a840-52ef-a25a632e5546@slackbuilds.org>
Message-ID: <20160526163603.GA10222@giustizia>

On Thu, May 26, 2016 at 09:22:34PM +0700, Willy Sudiarto Raharjo wrote:
> > recently I've built libdv using the slackbuild, and got a problem.
> > 
> > Basically, the source libdv/enc_input.c uses a macro (VIDEO_MAX_FRAME)
> > possibly defined in /usr/include/linux/videodev.h. Looking at that file,
> > the macro isn't defined, and so the build process stop with a proper
> > error.
> > 
> > I have to say I'm not using the stock kernel, but 3.16.3. I 
> > don't know if this problem is specific to this kernel or if it applies
> > to the stock 14.1 kernel as well (or to -current).
> > 
> > Making some investigation, I've found that this macro is defined at
> > /usr/include/linux/videodev2.h, and it's defined with 32. Also,
> > at least one case was solved defining this macro at the application
> > level, such as
> > https://lists.debian.org/debian-glibc/2006/07/msg00149.html, for
> > instance (although recognizing this case is not about libdv at all).
> > 
> > What I did was defining that macro in libdv/enc_input.c if it's not
> > still not defined. I've built a patch to that file and included it at
> > the SlackBuild script. The git patch goes attached.
> > 
> > Another option, which I didn't try, was to substitute #include videodev.h to
> > #include videodev2.h.
> > 
> > Hope this can help the community!
> 
> Hi Luiz
> 
> May i know which Slackware version do you use ?
> 14.1 or current?
> 

14.1, with a different kernel as mentioned above (3.16.3).

> 
> 
> -- 
> Willy Sudiarto Raharjo
> 

Thanks!

Luiz



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


From matteo.bernardini at gmail.com  Thu May 26 17:12:36 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 26 May 2016 19:12:36 +0200
Subject: [Slackbuilds-users] libdv: a problem and a possible fix
In-Reply-To: <20160526163603.GA10222@giustizia>
References: <20160526134624.GA28929@giustizia>
 <059a7ce4-4cf2-a840-52ef-a25a632e5546@slackbuilds.org>
 <20160526163603.GA10222@giustizia>
Message-ID: <CAPsDuS5bRYdFeuRQWrU0b+TMUMhLaegD896ru01yxAVC8x6W+w@mail.gmail.com>

2016-05-26 18:36 GMT+02:00 Luiz Carlos Ramos <lramos.prof at yahoo.com.br>:
> On Thu, May 26, 2016 at 09:22:34PM +0700, Willy Sudiarto Raharjo wrote:
>> > recently I've built libdv using the slackbuild, and got a problem.
>> >
>> > Basically, the source libdv/enc_input.c uses a macro (VIDEO_MAX_FRAME)
>> > possibly defined in /usr/include/linux/videodev.h. Looking at that file,
>> > the macro isn't defined, and so the build process stop with a proper
>> > error.
>> >
>> > I have to say I'm not using the stock kernel, but 3.16.3. I
>> > don't know if this problem is specific to this kernel or if it applies
>> > to the stock 14.1 kernel as well (or to -current).
>> >
>> > Making some investigation, I've found that this macro is defined at
>> > /usr/include/linux/videodev2.h, and it's defined with 32. Also,
>> > at least one case was solved defining this macro at the application
>> > level, such as
>> > https://lists.debian.org/debian-glibc/2006/07/msg00149.html, for
>> > instance (although recognizing this case is not about libdv at all).
>> >
>> > What I did was defining that macro in libdv/enc_input.c if it's not
>> > still not defined. I've built a patch to that file and included it at
>> > the SlackBuild script. The git patch goes attached.
>> >
>> > Another option, which I didn't try, was to substitute #include videodev.h to
>> > #include videodev2.h.
>> >
>> > Hope this can help the community!
>>
>> Hi Luiz
>>
>> May i know which Slackware version do you use ?
>> 14.1 or current?
>>
>
> 14.1, with a different kernel as mentioned above (3.16.3).

Hi Luiz,

I just tried building libdv on slackware-14.1 and slackware64-14.1 and
in either case the build process just bypass that header

...
checking for unistd.h... (cached) yes
checking linux/videodev.h usability... no
checking linux/videodev.h presence... no
checking for linux/videodev.h... no
checking sys/soundcard.h usability... yes
...

libdv hasn't been updated since ten years and that header was part of
the old v4l, that unfortunately isn't available anymore.

the best solution, IMHO, is to left it as-is, ignoring support for v4l
devices in libdv.

Matteo

From willysr at slackbuilds.org  Thu May 26 17:14:42 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 27 May 2016 00:14:42 +0700
Subject: [Slackbuilds-users] rust
In-Reply-To: <CAKpSnpLb9_S7J7BVEpsggavg4uA2N-Vg3OJnyvHt_o6zKLVy6g@mail.gmail.com>
References: <CAKpSnpL-iynZYtRgT-ax3_FuoSfbRy+k2G-sJ1jeLi4JoLNqEA@mail.gmail.com>
 <CAPiArqNoq_gnW25_BOwBp1AZUUTcDtP0jFsZPSVhn6doXWO8xw@mail.gmail.com>
 <1464271760.2429.2.camel@caraus.de>
 <CAKpSnpK9jSNJcWmkQGnK0YTV=0mgPg+Dg6tE9mxRmT_5-fPA2g@mail.gmail.com>
 <1464274143.2429.6.camel@caraus.de>
 <CAKpSnpLb9_S7J7BVEpsggavg4uA2N-Vg3OJnyvHt_o6zKLVy6g@mail.gmail.com>
Message-ID: <20a6ddc8-ce9f-ed5b-d088-212408d13d31@slackbuilds.org>

>> Yes the build script is broken since it doesn't install everything.
>> I mean everything you have to do is to unpack the downloaded rust
>> distribution:
>> tar zxf rust-1.5.0-x86_64-unknown-linux-gnu.tar.gz
>>
>> And move the rust-1.5.0-x86_64-unknown-linux-gnu/rust-std-x86_64-
>> unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/
>> to /usr/lib64/rustlib/:
>>
>> mv rust-1.5.0-x86_64-unknown-linux-gnu/rust-std-x86_64-unknown-linux-
>> gnu/lib/rustlib/x86_64-unknown-linux-gnu/ /usr/lib64/rustlib/
>>
>> and it will work.
>> For 1.8.0 and 32bit it should be similar.
>>
> 
> I edited the Slackbuild according to your instructions (as I didn't
> want to pollute the filesystem with stuff unknown to the Slackware
> packaging system). Sure enough, it works fine now (with version 1.8.0,
> 32bit system)

a patch to fix this issue is very appreciated :)

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/20160527/79041d00/attachment.asc>

From jjalmeida at gmail.com  Thu May 26 19:41:02 2016
From: jjalmeida at gmail.com (Jorge Almeida)
Date: Thu, 26 May 2016 12:41:02 -0700
Subject: [Slackbuilds-users] rust
In-Reply-To: <20a6ddc8-ce9f-ed5b-d088-212408d13d31@slackbuilds.org>
References: <CAKpSnpL-iynZYtRgT-ax3_FuoSfbRy+k2G-sJ1jeLi4JoLNqEA@mail.gmail.com>
 <CAPiArqNoq_gnW25_BOwBp1AZUUTcDtP0jFsZPSVhn6doXWO8xw@mail.gmail.com>
 <1464271760.2429.2.camel@caraus.de>
 <CAKpSnpK9jSNJcWmkQGnK0YTV=0mgPg+Dg6tE9mxRmT_5-fPA2g@mail.gmail.com>
 <1464274143.2429.6.camel@caraus.de>
 <CAKpSnpLb9_S7J7BVEpsggavg4uA2N-Vg3OJnyvHt_o6zKLVy6g@mail.gmail.com>
 <20a6ddc8-ce9f-ed5b-d088-212408d13d31@slackbuilds.org>
Message-ID: <CAKpSnpJSgnMP_DM=7Ej8xae1EThj3H_h0t8qdVHqHT93XTN=ng@mail.gmail.com>

On Thu, May 26, 2016 at 10:14 AM, Willy Sudiarto Raharjo
<willysr at slackbuilds.org> wrote:
>>> Yes the build script is broken since it doesn't install everything.
>>> I mean everything you have to do is to unpack the downloaded rust
>>> distribution:
>>> tar zxf rust-1.5.0-x86_64-unknown-linux-gnu.tar.gz
>>>
>>> And move the rust-1.5.0-x86_64-unknown-linux-gnu/rust-std-x86_64-
>>> unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/
>>> to /usr/lib64/rustlib/:
>>>
>>> mv rust-1.5.0-x86_64-unknown-linux-gnu/rust-std-x86_64-unknown-linux-
>>> gnu/lib/rustlib/x86_64-unknown-linux-gnu/ /usr/lib64/rustlib/
>>>
>>> and it will work.
>>> For 1.8.0 and 32bit it should be similar.
>>>
>>
>> I edited the Slackbuild according to your instructions (as I didn't
>> want to pollute the filesystem with stuff unknown to the Slackware
>> packaging system). Sure enough, it works fine now (with version 1.8.0,
>> 32bit system)
>
> a patch to fix this issue is very appreciated :)
>
Cheers

Jorge
-------------- next part --------------
--- rust.SlackBuild	2015-12-19 00:29:55.000000000 +0000
+++ rust.SlackBuild_new	2016-05-26 20:29:23.241567345 +0100
@@ -24,7 +24,7 @@
 
 PRGNAM=rust
 PRGNAM2=cargo
-VERSION=${VERSION:-1.5.0}
+VERSION=${VERSION:-1.8.0}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
@@ -41,16 +41,12 @@
 OUTPUT=${OUTPUT:-/tmp}
 
 if [ "$ARCH" = "i486" ]; then
-  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
   LIBDIRSUFFIX=""
 elif [ "$ARCH" = "i686" ]; then
-  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
   LIBDIRSUFFIX=""
 elif [ "$ARCH" = "x86_64" ]; then
-  SLKCFLAGS="-O2 -fPIC"
   LIBDIRSUFFIX="64"
 else
-  SLKCFLAGS="-O2"
   LIBDIRSUFFIX=""
 fi
 
@@ -99,6 +95,8 @@
 chmod 755 $PKG/usr/doc/$PRGNAM-$VERSION/html
 find -L $PKG/usr/doc/$PRGNAM-$VERSION/html -type d -exec chmod 755 {} \;
 
+mv $PRGNAM-std-$ARCH-unknown-linux-gnu/lib/rustlib/$ARCH-unknown-linux-gnu $PKG/usr/lib$LIBDIRSUFFIX/rustlib/
+
 mkdir -p $PKG/install
 cat $CWD/slack-desc > $PKG/install/slack-desc
 

From willysr at slackbuilds.org  Fri May 27 00:21:12 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 27 May 2016 07:21:12 +0700
Subject: [Slackbuilds-users] rust
In-Reply-To: <CAKpSnpJSgnMP_DM=7Ej8xae1EThj3H_h0t8qdVHqHT93XTN=ng@mail.gmail.com>
References: <CAKpSnpL-iynZYtRgT-ax3_FuoSfbRy+k2G-sJ1jeLi4JoLNqEA@mail.gmail.com>
 <CAPiArqNoq_gnW25_BOwBp1AZUUTcDtP0jFsZPSVhn6doXWO8xw@mail.gmail.com>
 <1464271760.2429.2.camel@caraus.de>
 <CAKpSnpK9jSNJcWmkQGnK0YTV=0mgPg+Dg6tE9mxRmT_5-fPA2g@mail.gmail.com>
 <1464274143.2429.6.camel@caraus.de>
 <CAKpSnpLb9_S7J7BVEpsggavg4uA2N-Vg3OJnyvHt_o6zKLVy6g@mail.gmail.com>
 <20a6ddc8-ce9f-ed5b-d088-212408d13d31@slackbuilds.org>
 <CAKpSnpJSgnMP_DM=7Ej8xae1EThj3H_h0t8qdVHqHT93XTN=ng@mail.gmail.com>
Message-ID: <1ddc4b54-e6d8-76c1-f5a3-568cf1a413dd@slackbuilds.org>

>> a patch to fix this issue is very appreciated :)

Thanks Jorge

i bumped to 1.9.0 as well along with the patch


-- 
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/20160527/7fe07433/attachment.asc>

From kingbeowulf at gmail.com  Fri May 27 15:02:27 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Fri, 27 May 2016 08:02:27 -0700
Subject: [Slackbuilds-users] libdv: a problem and a possible fix
In-Reply-To: <CAPsDuS5bRYdFeuRQWrU0b+TMUMhLaegD896ru01yxAVC8x6W+w@mail.gmail.com>
References: <20160526134624.GA28929@giustizia>
 <059a7ce4-4cf2-a840-52ef-a25a632e5546@slackbuilds.org>
 <20160526163603.GA10222@giustizia>
 <CAPsDuS5bRYdFeuRQWrU0b+TMUMhLaegD896ru01yxAVC8x6W+w@mail.gmail.com>
Message-ID: <e7a86a29-8f67-32a5-9dc0-c8853f52fe3e@gmail.com>

On 05/26/2016 10:12 AM, Matteo Bernardini wrote:
> 2016-05-26 18:36 GMT+02:00 Luiz Carlos Ramos <lramos.prof at yahoo.com.br>:
>> On Thu, May 26, 2016 at 09:22:34PM +0700, Willy Sudiarto Raharjo wrote:
>>>> recently I've built libdv using the slackbuild, and got a problem.
>>>>
>>>> Basically, the source libdv/enc_input.c uses a macro (VIDEO_MAX_FRAME)
>>>> possibly defined in /usr/include/linux/videodev.h. Looking at that file,
>>>> the macro isn't defined, and so the build process stop with a proper
>>>> error.
>>>>
>>>> I have to say I'm not using the stock kernel, but 3.16.3. I
>>>> don't know if this problem is specific to this kernel or if it applies
>>>> to the stock 14.1 kernel as well (or to -current).
>>>>
>>>> Making some investigation, I've found that this macro is defined at
>>>> /usr/include/linux/videodev2.h, and it's defined with 32. Also,
>>>> at least one case was solved defining this macro at the application
>>>> level, such as
>>>> https://lists.debian.org/debian-glibc/2006/07/msg00149.html, for
>>>> instance (although recognizing this case is not about libdv at all).
>>>>
>>>> What I did was defining that macro in libdv/enc_input.c if it's not
>>>> still not defined. I've built a patch to that file and included it at
>>>> the SlackBuild script. The git patch goes attached.
>>>>
>>>> Another option, which I didn't try, was to substitute #include videodev.h to
>>>> #include videodev2.h.
>>>>
>>>> Hope this can help the community!
>>>
>>> Hi Luiz
>>>
>>> May i know which Slackware version do you use ?
>>> 14.1 or current?
>>>
>>
>> 14.1, with a different kernel as mentioned above (3.16.3).
> 
> Hi Luiz,
> 
> I just tried building libdv on slackware-14.1 and slackware64-14.1 and
> in either case the build process just bypass that header
> 
> ...
> checking for unistd.h... (cached) yes
> checking linux/videodev.h usability... no
> checking linux/videodev.h presence... no
> checking for linux/videodev.h... no
> checking sys/soundcard.h usability... yes
> ...
> 
> libdv hasn't been updated since ten years and that header was part of
> the old v4l, that unfortunately isn't available anymore.
> 
> the best solution, IMHO, is to left it as-is, ignoring support for v4l
> devices in libdv.
> 
> Matteo

Indeed. libdv is now just useful for firewire DV captures (say via
dvgrab for my old camcorder).  For v4l devices, say, USB webcams,
mplayer, ffmpeg, ffplay, wxcam, etc can grab the video.

libdv compiled last week ok on Slackware-current 4.4.10.

-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/20160527/9d1c93ed/attachment-0001.asc>

From slackware at lemintown.eu  Sat May 28 12:54:29 2016
From: slackware at lemintown.eu (Brian Lemin)
Date: Sat, 28 May 2016 14:54:29 +0200
Subject: [Slackbuilds-users] Epson packages for 14.2
Message-ID: <dc767304-3232-288d-ce9b-a53b9857b45e@lemintown.eu>

Greetings all,

I recently acquired a fairly recent Epson printer/scanner and found that
our beloved slackware might need some updates to properly support the
latest Epson products.


epson-inkjet-printer-escpr:

Currently 1.4.5 in sbo 14.1
I have tested the 1.6.5 package on current and it works fine until now.
https://download3.ebz.epson.net/dsc/f/03/00/04/54/27/b73564748bfde7b7ce625e20d4a3257d447bec79/epson-inkjet-printer-escpr-1.6.5-1lsb3.2.tar.gz
The 14.1 slackbuild script works fine if you remove "./bootstrap".


iscan:

Currently v2 in sbo 14.1
I believe it has been replaced with v3 by a new package named "imagescan"
old: http://support.epson.net/linux/src/scanner/iscan/
new: http://support.epson.net/linux/src/scanner/imagescanv3/
I am in the process of testing this but I would like to know if someone
has started to work on this already

The readme reads:
Utsushi - Next Generation Image Acquisition
Copyright (C) 2012-2016  SEIKO EPSON CORPORATION

Regards




From ruben at rbn.im  Sat May 28 13:02:54 2016
From: ruben at rbn.im (Ruben Schuller)
Date: Sat, 28 May 2016 15:02:54 +0200
Subject: [Slackbuilds-users] Epson packages for 14.2
In-Reply-To: <dc767304-3232-288d-ce9b-a53b9857b45e@lemintown.eu>
References: <dc767304-3232-288d-ce9b-a53b9857b45e@lemintown.eu>
Message-ID: <20160528150254.18934108@kiwi.kuchen>

Hi,

2016-05-28 14-54-29 Brian Lemin <slackware at lemintown.eu>

> epson-inkjet-printer-escpr:
> 
> Currently 1.4.5 in sbo 14.1
> I have tested the 1.6.5 package on current and it works fine until
> now.
> https://download3.ebz.epson.net/dsc/f/03/00/04/54/27/b73564748bfde7b7ce625e20d4a3257d447bec79/epson-inkjet-printer-escpr-1.6.5-1lsb3.2.tar.gz
> The 14.1 slackbuild script works fine if you remove "./bootstrap".

I'll take a look and submit an update, thanks for the notice!

Ruben

From lramos.prof at yahoo.com.br  Sat May 28 14:09:27 2016
From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos)
Date: Sat, 28 May 2016 11:09:27 -0300
Subject: [Slackbuilds-users] libdv: a problem and a possible fix
In-Reply-To: <CAPsDuS5bRYdFeuRQWrU0b+TMUMhLaegD896ru01yxAVC8x6W+w@mail.gmail.com>
References: <20160526134624.GA28929@giustizia>
 <059a7ce4-4cf2-a840-52ef-a25a632e5546@slackbuilds.org>
 <20160526163603.GA10222@giustizia>
 <CAPsDuS5bRYdFeuRQWrU0b+TMUMhLaegD896ru01yxAVC8x6W+w@mail.gmail.com>
Message-ID: <20160528140927.GA5769@giustizia>

On Thu, May 26, 2016 at 07:12:36PM +0200, Matteo Bernardini wrote:
> 2016-05-26 18:36 GMT+02:00 Luiz Carlos Ramos <lramos.prof at yahoo.com.br>:
> > On Thu, May 26, 2016 at 09:22:34PM +0700, Willy Sudiarto Raharjo wrote:
> >> > recently I've built libdv using the slackbuild, and got a problem.
> >> >
> >> > Basically, the source libdv/enc_input.c uses a macro (VIDEO_MAX_FRAME)
> >> > possibly defined in /usr/include/linux/videodev.h. Looking at that file,
> >> > the macro isn't defined, and so the build process stop with a proper
> >> > error.
> >> >
> >> > I have to say I'm not using the stock kernel, but 3.16.3. I
> >> > don't know if this problem is specific to this kernel or if it applies
> >> > to the stock 14.1 kernel as well (or to -current).
> >> >
> >> > Making some investigation, I've found that this macro is defined at
> >> > /usr/include/linux/videodev2.h, and it's defined with 32. Also,
> >> > at least one case was solved defining this macro at the application
> >> > level, such as
> >> > https://lists.debian.org/debian-glibc/2006/07/msg00149.html, for
> >> > instance (although recognizing this case is not about libdv at all).
> >> >
> >> > What I did was defining that macro in libdv/enc_input.c if it's not
> >> > still not defined. I've built a patch to that file and included it at
> >> > the SlackBuild script. The git patch goes attached.
> >> >
> >> > Another option, which I didn't try, was to substitute #include videodev.h to
> >> > #include videodev2.h.
> >> >
> >> > Hope this can help the community!
> >>
> >> Hi Luiz
> >>
> >> May i know which Slackware version do you use ?
> >> 14.1 or current?
> >>
> >
> > 14.1, with a different kernel as mentioned above (3.16.3).
> 
> Hi Luiz,
> 
> I just tried building libdv on slackware-14.1 and slackware64-14.1 and
> in either case the build process just bypass that header
> 
> ...
> checking for unistd.h... (cached) yes
> checking linux/videodev.h usability... no
> checking linux/videodev.h presence... no
> checking for linux/videodev.h... no
> checking sys/soundcard.h usability... yes
> ...
> 
> libdv hasn't been updated since ten years and that header was part of
> the old v4l, that unfortunately isn't available anymore.
> 
> the best solution, IMHO, is to left it as-is, ignoring support for v4l
> devices in libdv.
> 
> Matteo

Yes, Matteo, I've double check my installation and videodev.h seem like a
trash left there after some experiments (possibly with an older version of
skype).

Even I'm satisfied with the build with videodev.h, I agree with you
that it's better to leave as it is, that is, with videodev2.h.

Thanks,

Luiz


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

From rshepard at appl-ecosys.com  Sat May 28 18:58:48 2016
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 28 May 2016 11:58:48 -0700 (PDT)
Subject: [Slackbuilds-users] LyX-2.2.0
Message-ID: <alpine.LNX.2.11.1605281158020.13149@localhost>

   The LyX devs released version 2.2.0 yesterday. It builds with the existing
SlackBuild script.

Rich

From willysr at slackbuilds.org  Sun May 29 02:28:56 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 29 May 2016 09:28:56 +0700
Subject: [Slackbuilds-users] 14.2RC Updates for SBo packages as of
 kernel 4.4.10
In-Reply-To: <72de72e9-457c-b155-93e2-23aea4a18c3f@gmail.com>
References: <72de72e9-457c-b155-93e2-23aea4a18c3f@gmail.com>
Message-ID: <46bbf7fa-86ea-13c9-2532-bd9a96a77116@slackbuilds.org>

> There are a number of updates for my packages; you can find them here:
> 
> http://www.linuxgalaxy.org/files/sbo-testing/
> http://www.koenigcomputers.com/sbo-testing/
> 
> =======
> Minor
> =======
> CImg               Version update
> 
> =======
> Major
> =======
> murmur	Version update, upstream bugfixes/security
> mumble	Version and feature update, upstream bugfixes/security
> 
> ***NOTE: text-to-speech is now an available option in mumble with
> SPEECHD=yes
>  and requires additional optional dependencies:
> -You will need one text-to-speech engine installed. For example:
>    flite      on SBo, not working, no deps (optional voices)
>    festival   not on SBo, not tested
>    espeak     on Sbo tested/working, requires portaudio (on SBo)
> 
> -New dependency packages:
>    accessibility/speech-dispatcher  (speechd)
>    libraries/dotconf

All applied in my branch

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/20160529/615c8bf2/attachment.asc>

From willysr at slackbuilds.org  Sun May 29 02:31:57 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 29 May 2016 09:31:57 +0700
Subject: [Slackbuilds-users] Epson packages for 14.2
In-Reply-To: <20160528150254.18934108@kiwi.kuchen>
References: <dc767304-3232-288d-ce9b-a53b9857b45e@lemintown.eu>
 <20160528150254.18934108@kiwi.kuchen>
Message-ID: <bbfd4c34-0f59-fa12-f0e2-7f0bba8ee93a@slackbuilds.org>

>> epson-inkjet-printer-escpr:
>>
>> Currently 1.4.5 in sbo 14.1
>> I have tested the 1.6.5 package on current and it works fine until
>> now.
>> https://download3.ebz.epson.net/dsc/f/03/00/04/54/27/b73564748bfde7b7ce625e20d4a3257d447bec79/epson-inkjet-printer-escpr-1.6.5-1lsb3.2.tar.gz
>> The 14.1 slackbuild script works fine if you remove "./bootstrap".
> 
> I'll take a look and submit an update, thanks for the notice!

i have updated the script in my branch already
and with bootstrap it still build normally

i haven't touched iscan though


-- 
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/20160529/e0c25cf1/attachment.asc>

From glenn.becker at gmail.com  Sun May 29 22:43:03 2016
From: glenn.becker at gmail.com (Glenn Becker)
Date: Sun, 29 May 2016 18:43:03 -0400
Subject: [Slackbuilds-users] question about stable vs. current
Message-ID: <CANCo2a0y9dsqLyVr-DBXusfGRaw4JcDx30xv_JjjGpTLVvcGww@mail.gmail.com>

Hi --

This may be enshrined in a doc somewhere -- if so, let me know where. :)

As I've adopted more packages, I've started to approach release-times with
more and more ... erm, befuddlement.

I used to think that SBo packages were only guaranteed to run on stable,
and that was it ... but it's seemed more complicated than that for some
time, and I'm afraid I have done a terrible job of keeping up with it.

I want to do the best job I can with these packages, but I am unclear what
is expected surrounding a release. Could someone let me know?

Thanks,

Glenn

<http://projecteuler.net/profile/gbecker.png>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160529/ff97c3b5/attachment.html>

From baildon.research at googlemail.com  Sun May 29 23:23:14 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Mon, 30 May 2016 00:23:14 +0100
Subject: [Slackbuilds-users] Community Challenge! Help fix the last few
 SlackBuilds for 14.2
Message-ID: <CAMt7G9S1p=jSx9VNARkL2r7Nou5dk5fFfChQpj9UqH99zkheTA@mail.gmail.com>

Hey folks!

So here we all are, waiting for the release of Slackware 14.2. It's
looking good, but nobody knows when it will be good enough for Patrick
:)

Meanwhile, work is continuing to get SlackBuilds.org ready for the new
release. According to Willy there have been 2373 commits in the SBo
git repo since submissions were closed.  That's about one commit every
1hour 20min. You can see Willy's list here:

http://pastebin.com/S63pPStU

At this time there are only a few packages that fail to build, and all
the git commiters are getting a bit tired, so we would like to
challenge the community to help fix the last few problems.  Your
reward will be a nice Thank You in the git repo :D

Here are the first four ... if you can fix them, there will be some more later!


1. academic/Xyce

http://pastebin.com/nsMwxhgR

It looks like an underlinking error, but I can't see anything wrong
with the link. There is a new version 6.4 upstream, I have tried it,
but the same linking problem happens.  Maybe its dep
libraries/trilinos is involved -- Guilherme (maintainer of both Xyce
and trilinos) downgraded trilinos soon after it was first added.  I
can't find any bug reports.  Most other distros don't have Xyce.

If you don't want to register to download the source, there is a copy
of Xyce-6.4 on SlackBuilds Direct Links (Xyce is GPL, so
redistributing it is perfectly legal ;)
https://sourceforge.net/projects/slackbuildsdirectlinks/files/Xyce/


2. development/hhvm

http://pastebin.com/KvUmExsr

The problem is caused by changes in the latest glibc that are related
to std::isnan and std::isinf in c++. 3.11.0 is an old version, we
could try an upgrade but it's not clear whether newer versions fix the
problem.  Because hhvm uses a lot of git submodules, it's quite a lot
of work to add downloads, or to create and host a new repacked source
archive.

There was previously some discussion on this mailing list whether
anybody actually wants hhvm:
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-April/016006.html

So, if anybody wants hhvm, you are welcome to fix it ;)


3. games/ember

http://pastebin.com/Ny5PChhm

The build was broken by the new version of sigc++. Upstream is quite
active but seems to have stopped tagging proper releases. I tried the
latest git, but it needs its deps also updating to compatible
versions.

https://github.com/worldforge/ember
and deps at https://github.com/worldforge


4. graphics/photivo

http://pastebin.com/v5Yt3SYV

This looks like an underlinking error, but the build fails for me only
on x86_64 ... on i586 it builds ok!


That's all for now, if you have fixes for any of those you are welcome
to reply to this thread with patches or suggestions.

Thanks for your help and support!
-D.

From willysr at slackbuilds.org  Mon May 30 01:12:24 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 30 May 2016 08:12:24 +0700
Subject: [Slackbuilds-users] question about stable vs. current
In-Reply-To: <CANCo2a0y9dsqLyVr-DBXusfGRaw4JcDx30xv_JjjGpTLVvcGww@mail.gmail.com>
References: <CANCo2a0y9dsqLyVr-DBXusfGRaw4JcDx30xv_JjjGpTLVvcGww@mail.gmail.com>
Message-ID: <5c817a69-6ff5-cc6b-f49c-aea1cdd9c7ec@slackbuilds.org>

> I used to think that SBo packages were only guaranteed to run on stable,
> and that was it ... but it's seemed more complicated than that for some
> time, and I'm afraid I have done a terrible job of keeping up with it.
> 
> I want to do the best job I can with these packages, but I am unclear what
> is expected surrounding a release. Could someone let me know?

SBo is actually designed just as you described, guaranteed to run on
stable and it's still valid point.

The reason we started tracking current for this cycle is because were
very late in the previous (14.1) cycle, causing the repository to be
stalled for more than 3 months (CMIIW) until it's considered ready for
public.

With Slackware's 14.2 development that was considered big enough, Ponce
and David had already started in Ponce's personal repository in github
and then Robby decided to start preparing for 14.2 repository in around
January. We hoped that when 14.2 gets released, our repository is ready
and can be opened for public as soon as possible.

There's no need to rush things for maintainers. They are free to wait
until 14.2 gets released and test their packages OR they can start
testing it early by using current.


-- 
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/20160530/6d41fa20/attachment.asc>

From belka at caraus.de  Mon May 30 11:25:32 2016
From: belka at caraus.de (Eugen Wissner)
Date: Mon, 30 May 2016 13:25:32 +0200
Subject: [Slackbuilds-users] Community Challenge! Help fix the last few
 SlackBuilds for 14.2
In-Reply-To: <CAMt7G9S1p=jSx9VNARkL2r7Nou5dk5fFfChQpj9UqH99zkheTA@mail.gmail.com>
References: <CAMt7G9S1p=jSx9VNARkL2r7Nou5dk5fFfChQpj9UqH99zkheTA@mail.gmail.com>
Message-ID: <1464607532.15061.7.camel@caraus.de>

Hi,

hhvm..

I don't know. Yes I patched the sources (github sublibraries are
included):
http://download.dlackware.com/hosted-sources/hhvm/hhvm-3.11.0.tar.xz
http://download.dlackware.com/hosted-sources/hhvm/hhvm-3.11.1.tar.xz
http://download.dlackware.com/hosted-sources/hhvm/hhvm-3.12.1.tar.xz
http://download.dlackware.com/hosted-sources/hhvm/hhvm-3.13.1.tar.xz

That ones should work, I'm only not sure if I tested 3.13.1. And
facebook promised to fix this inconsistency between C and C++ isnan and
isinf.

But I don't really want to maintain hhvm. I wanted to use it on my
server, but it seems I won't do it since hhvm leaks constantly memory
and eats hdd space. And it has a lot of small dependencies.

So if someone interested, I will make an update and get it working on
current. If not, I would just remove it with all the hhvm dependencies
I maintain (they are only used by hhvm).

Regards
Eugene

Am Montag, den 30.05.2016, 00:23 +0100 schrieb David Spencer:
> Hey folks!
> 
> So here we all are, waiting for the release of Slackware 14.2. It's
> looking good, but nobody knows when it will be good enough for
> Patrick
> :)
> 
> Meanwhile, work is continuing to get SlackBuilds.org ready for the
> new
> release. According to Willy there have been 2373 commits in the SBo
> git repo since submissions were closed.??That's about one commit
> every
> 1hour 20min. You can see Willy's list here:
> 
> http://pastebin.com/S63pPStU
> 
> At this time there are only a few packages that fail to build, and
> all
> the git commiters are getting a bit tired, so we would like to
> challenge the community to help fix the last few problems.??Your
> reward will be a nice Thank You in the git repo :D
> 
> Here are the first four ... if you can fix them, there will be some
> more later!
> 
> 
> 1. academic/Xyce
> 
> http://pastebin.com/nsMwxhgR
> 
> It looks like an underlinking error, but I can't see anything wrong
> with the link. There is a new version 6.4 upstream, I have tried it,
> but the same linking problem happens.??Maybe its dep
> libraries/trilinos is involved -- Guilherme (maintainer of both Xyce
> and trilinos) downgraded trilinos soon after it was first added.??I
> can't find any bug reports.??Most other distros don't have Xyce.
> 
> If you don't want to register to download the source, there is a copy
> of Xyce-6.4 on SlackBuilds Direct Links (Xyce is GPL, so
> redistributing it is perfectly legal ;)
> https://sourceforge.net/projects/slackbuildsdirectlinks/files/Xyce/
> 
> 
> 2. development/hhvm
> 
> http://pastebin.com/KvUmExsr
> 
> The problem is caused by changes in the latest glibc that are related
> to std::isnan and std::isinf in c++. 3.11.0 is an old version, we
> could try an upgrade but it's not clear whether newer versions fix
> the
> problem.??Because hhvm uses a lot of git submodules, it's quite a lot
> of work to add downloads, or to create and host a new repacked source
> archive.
> 
> There was previously some discussion on this mailing list whether
> anybody actually wants hhvm:
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-April/
> 016006.html
> 
> So, if anybody wants hhvm, you are welcome to fix it ;)
> 
> 
> 3. games/ember
> 
> http://pastebin.com/Ny5PChhm
> 
> The build was broken by the new version of sigc++. Upstream is quite
> active but seems to have stopped tagging proper releases. I tried the
> latest git, but it needs its deps also updating to compatible
> versions.
> 
> https://github.com/worldforge/ember
> and deps at https://github.com/worldforge
> 
> 
> 4. graphics/photivo
> 
> http://pastebin.com/v5Yt3SYV
> 
> This looks like an underlinking error, but the build fails for me
> only
> on x86_64 ... on i586 it builds ok!
> 
> 
> That's all for now, if you have fixes for any of those you are
> welcome
> to reply to this thread with patches or suggestions.
> 
> Thanks for your help and support!
> -D.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
> 

From ryan.q at linux.com  Mon May 30 11:33:53 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Mon, 30 May 2016 04:33:53 -0700
Subject: [Slackbuilds-users] Community Challenge! Help fix the last few
 SlackBuilds for 14.2
In-Reply-To: <1464607532.15061.7.camel@caraus.de>
References: <CAMt7G9S1p=jSx9VNARkL2r7Nou5dk5fFfChQpj9UqH99zkheTA@mail.gmail.com>
 <1464607532.15061.7.camel@caraus.de>
Message-ID: <CAAcyf-oH7mg=d6Jd=sLcwSg65YVMPKJxqjYLd4VStNinJu3Lfw@mail.gmail.com>

> But I don't really want to maintain hhvm. I wanted to use it on my
> server, but it seems I won't do it since hhvm leaks constantly memory
> and eats hdd space. And it has a lot of small dependencies.
>
> So if someone interested, I will make an update and get it working on
> current. If not, I would just remove it with all the hhvm dependencies
> I maintain (they are only used by hhvm).

Hey Eugene,

I was happy to see it on SBo (I would love to see it stay) but I doubt I
would maintain it any better. It is nice having all the Facebook internal
tools available through SBo (we have Watchman and Flow also). I hope
someone steps up to keep it running.  :^)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160530/766aa5c9/attachment.html>

From belka at caraus.de  Mon May 30 13:11:17 2016
From: belka at caraus.de (Eugen Wissner)
Date: Mon, 30 May 2016 15:11:17 +0200
Subject: [Slackbuilds-users] Community Challenge! Help fix the last few
 SlackBuilds for 14.2
In-Reply-To: <CAAcyf-oH7mg=d6Jd=sLcwSg65YVMPKJxqjYLd4VStNinJu3Lfw@mail.gmail.com>
References: <CAMt7G9S1p=jSx9VNARkL2r7Nou5dk5fFfChQpj9UqH99zkheTA@mail.gmail.com>
 <1464607532.15061.7.camel@caraus.de>
 <CAAcyf-oH7mg=d6Jd=sLcwSg65YVMPKJxqjYLd4VStNinJu3Lfw@mail.gmail.com>
Message-ID: <1464613877.15061.10.camel@caraus.de>

Thanks for the feedback.

Attached is a git patch with the update to 3.13.1 (last stable) against
the slackbuilds git master.

Regards
Eugene

Am Montag, den 30.05.2016, 04:33 -0700 schrieb Ryan P.C. McQuen:
> 
> > But I don't really want to maintain hhvm. I wanted to use it on my
> > server, but it seems I won't do it since hhvm leaks constantly
> memory
> > and eats hdd space. And it has a lot of small dependencies.
> >
> > So if someone interested, I will make an update and get it working
> on
> > current. If not, I would just remove it with all the hhvm
> dependencies
> > I maintain (they are only used by hhvm).
> Hey Eugene,
> I was happy to see it on SBo (I would love to see it stay) but I
> doubt I would maintain it any better. It is nice having all the
> Facebook internal tools available through SBo (we have Watchman and
> Flow also). I hope someone steps up to keep it running.? :^)
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hhvm.diff
Type: text/x-patch
Size: 2740 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160530/a47679eb/attachment.bin>

From baildon.research at googlemail.com  Mon May 30 19:07:34 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Mon, 30 May 2016 20:07:34 +0100
Subject: [Slackbuilds-users] Community Challenge! Help fix the last few
 SlackBuilds for 14.2
In-Reply-To: <1464613877.15061.10.camel@caraus.de>
References: <CAMt7G9S1p=jSx9VNARkL2r7Nou5dk5fFfChQpj9UqH99zkheTA@mail.gmail.com>
 <1464607532.15061.7.camel@caraus.de>
 <CAAcyf-oH7mg=d6Jd=sLcwSg65YVMPKJxqjYLd4VStNinJu3Lfw@mail.gmail.com>
 <1464613877.15061.10.camel@caraus.de>
Message-ID: <CAMt7G9RynEbZ_LoD=wkBbVn1ukazUN0HaqLS+xH803f6uxaakw@mail.gmail.com>

*Thanks* Eugen!

Willy said he was building hhvm this afternoon, hopefully your fixed
version will show up soon on master :)

Cheers!
-D.

From willysr at slackbuilds.org  Mon May 30 22:05:14 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 31 May 2016 05:05:14 +0700
Subject: [Slackbuilds-users] Community Challenge! Help fix the last few
 SlackBuilds for 14.2
In-Reply-To: <CAMt7G9RynEbZ_LoD=wkBbVn1ukazUN0HaqLS+xH803f6uxaakw@mail.gmail.com>
References: <CAMt7G9S1p=jSx9VNARkL2r7Nou5dk5fFfChQpj9UqH99zkheTA@mail.gmail.com>
 <1464607532.15061.7.camel@caraus.de>
 <CAAcyf-oH7mg=d6Jd=sLcwSg65YVMPKJxqjYLd4VStNinJu3Lfw@mail.gmail.com>
 <1464613877.15061.10.camel@caraus.de>
 <CAMt7G9RynEbZ_LoD=wkBbVn1ukazUN0HaqLS+xH803f6uxaakw@mail.gmail.com>
Message-ID: <ffeaef88-0ca6-3c20-157a-5473c10ad2bf@slackbuilds.org>

> *Thanks* Eugen!
> 
> Willy said he was building hhvm this afternoon, hopefully your fixed
> version will show up soon on master :)

Confirmed to be fixed!
Congrats Eugen, you solved the first challenge :)


-- 
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/20160531/b0c3888e/attachment.asc>

From thomas at beingboiled.info  Tue May 31 01:42:09 2016
From: thomas at beingboiled.info (Thomas Morper)
Date: Tue, 31 May 2016 03:42:09 +0200 (CEST)
Subject: [Slackbuilds-users] Community Challenge! Help fix the last few
 SlackBuilds for 14.2
In-Reply-To: <CAMt7G9S1p=jSx9VNARkL2r7Nou5dk5fFfChQpj9UqH99zkheTA@mail.gmail.com>
References: <CAMt7G9S1p=jSx9VNARkL2r7Nou5dk5fFfChQpj9UqH99zkheTA@mail.gmail.com>
Message-ID: <alpine.LNX.2.11.1605310325340.2964@ks3357608.kimsufi.com>

On Mon, 30 May 2016, David Spencer wrote:

> 4. graphics/photivo
> 
> http://pastebin.com/v5Yt3SYV
> 
> This looks like an underlinking error, but the build fails for me only
> on x86_64 ... on i586 it builds ok!

I made this one build on x86_64 with the help of an extra compiler flag:

  env CFLAGS="$SLKCFLAGS -fno-finite-math-only" \
    CXXFLAGS="$SLKCFLAGS -fno-finite-math-only" make

...instead of the simple "make" in line 76.

The resulting package runs without crashing. I don't know if it actually 
*works* as the tool is strange to me.

-- 

From willysr at slackbuilds.org  Tue May 31 01:57:40 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 31 May 2016 08:57:40 +0700
Subject: [Slackbuilds-users] Community Challenge! Help fix the last few
 SlackBuilds for 14.2
In-Reply-To: <alpine.LNX.2.11.1605310325340.2964@ks3357608.kimsufi.com>
References: <CAMt7G9S1p=jSx9VNARkL2r7Nou5dk5fFfChQpj9UqH99zkheTA@mail.gmail.com>
 <alpine.LNX.2.11.1605310325340.2964@ks3357608.kimsufi.com>
Message-ID: <d2a016ae-21b8-536f-108a-5943ef57f0db@slackbuilds.org>

> I made this one build on x86_64 with the help of an extra compiler flag:
> 
>   env CFLAGS="$SLKCFLAGS -fno-finite-math-only" \
>     CXXFLAGS="$SLKCFLAGS -fno-finite-math-only" make
> 
> ...instead of the simple "make" in line 76.
> 
> The resulting package runs without crashing. I don't know if it actually 
> *works* as the tool is strange to me.


commit 67a8c7fc928a35bf01d19e991173e8108bba7bba
Author: Thomas Morper <thomas at beingboiled.info>
Date:   Tue May 31 08:56:41 2016 +0700

    graphics/photivo: Fix build with new GCC.

    Big thanks to Thomas Morper.

    Signed-off-by: Willy Sudiarto Raharjo <willysr at slackbuilds.org>

Second challenge solved :)


-- 
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/20160531/25745e40/attachment.asc>

From slacker6896 at gmail.com  Tue May 31 14:16:49 2016
From: slacker6896 at gmail.com (Sebastien BALLET)
Date: Tue, 31 May 2016 16:16:49 +0200
Subject: [Slackbuilds-users] p7zip vulnerabilities
Message-ID: <CAA2+phFOzrPUxzqCThqauVWyYwaVhBpEWB-o_5anjvo2EqTUWA@mail.gmail.com>

Hello,

p7zip 9.20.1 has two security issues :

CVE-2015-1038:
p7zip 9.20.1 allows remote attackers to write to arbitrary files via a
symlink attack in an archive.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1038
https://sourceforge.net/p/p7zip/bugs/147/#2f9c

CVE-2016-2335:
7zip UDF CInArchive::ReadFileItem Code Execution Vulnerability

http://www.talosintel.com/reports/TALOS-2016-0094/
https://sourceforge.net/p/p7zip/discussion/383043/thread/9d0fb86b/#1dba

The latest p7zip, ie. 15.14.1, is not affected by CVE-2015-1038, but
affected by CVE-2016-2335 and also by CVE-2016-2334.

In attachment, the patches for these issues, and for the slackbuild.

Notes:

p7zip.SlackBuild.patch
Applies the patches to fix vulnerabilities in p7zip 9.20.1

p7zip.15.14.1.SlackBuild.patch
Bumps VERSION to 15.14.1 and applies the patches to fix vulnerabilities in
this version.

Hope this help.

-- 
SeB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160531/16f13b7a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CVE-2015-1038.patch
Type: text/x-patch
Size: 8816 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160531/16f13b7a/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CVE-2016-2334.patch
Type: text/x-patch
Size: 889 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160531/16f13b7a/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CVE-2016-2335.patch
Type: text/x-patch
Size: 745 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160531/16f13b7a/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: p7zip.SlackBuild.patch
Type: text/x-patch
Size: 914 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160531/16f13b7a/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: p7zip.15.14.1.SlackBuild.patch
Type: text/x-patch
Size: 1017 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160531/16f13b7a/attachment-0004.bin>

From s.arcus at open-t.co.uk  Tue May 31 19:42:34 2016
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Tue, 31 May 2016 20:42:34 +0100
Subject: [Slackbuilds-users] Syncthing - type correction and version bump
Message-ID: <04f1a9fa-1297-7eff-c060-2721f29c9589@open-t.co.uk>

I've discovered a small typo in the rc.syncthing I've originally 
submitted - and I've taken the opportunity to also bump the version at 
the same time. Please see attached patch files. I've created them 
directly with diff - I'm not really sure if they are in the format 
expected by git?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rc.syncthing.patch
Type: text/x-patch
Size: 488 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160531/9edc73ac/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: syncthing.SlackBuild.patch
Type: text/x-patch
Size: 310 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160531/9edc73ac/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: syncthing.info.patch
Type: text/x-patch
Size: 950 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160531/9edc73ac/attachment-0005.bin>

From s.arcus at open-t.co.uk  Tue May 31 23:19:27 2016
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Wed, 1 Jun 2016 00:19:27 +0100
Subject: [Slackbuilds-users] Navit GPS
Message-ID: <8cb3e7b9-bdfe-dbf3-d366-eb67d5f3685c@open-t.co.uk>

I note that SBo doesn't have Navit in the repositories 
(www.navit-project.org). I've been using it for years, mainly as it 
appears to be the only gps navigation software capable of downloading 
and using offline the map of an entire country from OpenStreetMap in 
vector format (thus available at all zoom levels).

Do I remember correctly that Navit used to be available on SBo, and then 
got removed as it needed some dependencies which couldn't be satisfied 
at the time? I have just compiled and installed it on a Slack64 -current 
box, and it seems to have worked out just fine with no extra 
dependencies needed - using cmake.

From willysr at slackbuilds.org  Tue May 31 23:57:05 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 1 Jun 2016 06:57:05 +0700
Subject: [Slackbuilds-users] Syncthing - type correction and version bump
In-Reply-To: <04f1a9fa-1297-7eff-c060-2721f29c9589@open-t.co.uk>
References: <04f1a9fa-1297-7eff-c060-2721f29c9589@open-t.co.uk>
Message-ID: <5b9b60b3-105c-2ab1-6da0-00464dc8a3f5@slackbuilds.org>

> I've discovered a small typo in the rc.syncthing I've originally
> submitted - and I've taken the opportunity to also bump the version at
> the same time. Please see attached patch files. I've created them
> directly with diff - I'm not really sure if they are in the format
> expected by git?

Applied to my branch

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/20160601/0e66e18e/attachment.asc>

From gregkelemen at gmail.com  Mon May 30 15:44:02 2016
From: gregkelemen at gmail.com (Greg Kelemen)
Date: Mon, 30 May 2016 09:44:02 -0600
Subject: [Slackbuilds-users] Aigaion errors
Message-ID: <72C4E4C7-614D-4EDC-B80A-10834EC8C4F8@gmail.com>

Hello.

I?ve installed Aigaion 2.2.b on OS X 10.11.3 with MAMP 3.0.7.3/MySQL 5.5.38/PHP 5.6.2.

URL is http://localhost:8888/index.php

Installation proceeded OK. (Modded index.php to include non-standard HTTP port.)

I?ve attached a screen grab of the error message.

Is this a directory permissions issue?
-- 
Greg Kelemen
gregkelemen at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160530/4542f77d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aigaion-error.png
Type: image/png
Size: 115571 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160530/4542f77d/attachment-0001.png>