From t3slider at gmail.com  Mon Feb  1 01:15:53 2016
From: t3slider at gmail.com (T3slider)
Date: Sun, 31 Jan 2016 20:15:53 -0500
Subject: [Slackbuilds-users] MakeMKV update
Message-ID: <20160201011553.GB2797@MyPC.phub.net.cable.rogers.com>

I wouldn't normally submit an update when submissions are closed but as
it is the sources have moved (as they always do in version changes for
MakeMKV) so it would need to be adjusted for when 14.2 is released
anyway.

I have attached 2 patches, one that just points to the moved sources for
1.9.7 and another that updates to 1.9.9. You can choose whichever one
you want, though obviously when submissions re-open I would end up
submitting the updated version anyway.

Thanks,
T3slider
-------------- next part --------------
diff -ur a/makemkv.info b/makemkv.info
--- a/makemkv.info	2015-10-09 22:19:48.000000000 -0400
+++ b/makemkv.info	2016-01-31 20:03:55.198005720 -0500
@@ -1,8 +1,8 @@
 PRGNAM="makemkv"
 VERSION="1.9.7"
 HOMEPAGE="http://www.makemkv.com/"
-DOWNLOAD="http://www.makemkv.com/download/makemkv-oss-1.9.7.tar.gz \
-          http://www.makemkv.com/download/makemkv-bin-1.9.7.tar.gz"
+DOWNLOAD="http://www.makemkv.com/download/old/makemkv-oss-1.9.7.tar.gz \
+          http://www.makemkv.com/download/old/makemkv-bin-1.9.7.tar.gz"
 MD5SUM="2c0b0d31d1e1fb8576db024c7f02399c \
         52bd49e4667284ce27cbec6a5d8b8877"
 DOWNLOAD_x86_64=""
-------------- next part --------------
diff --git a/inttypes.patch b/inttypes.patch
new file mode 100644
index 0000000..cd99f0e
--- /dev/null
+++ b/inttypes.patch
@@ -0,0 +1,23 @@
+diff -ur a/libmakemkv/src/libmkv.cpp b/libmakemkv/src/libmkv.cpp
+--- a/libmakemkv/src/libmkv.cpp	2016-01-15 06:39:10.000000000 -0500
++++ b/libmakemkv/src/libmkv.cpp	2016-01-31 17:14:32.761225345 -0500
+@@ -18,6 +18,9 @@
+     Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
+ 
+ */
++#ifndef __STDC_FORMAT_MACROS
++#define __STDC_FORMAT_MACROS 1
++#endif
+ #include <libmkv/libmkv.h>
+ #include <libmkv/internal.h>
+ #include <libmkv/ebmlwrite.h>
+@@ -27,9 +30,6 @@
+ #include <lgpl/world.h>
+ #include <vector>
+ 
+-#ifndef __STDC_FORMAT_MACROS
+-#define __STDC_FORMAT_MACROS 1
+-#endif
+ #include <inttypes.h>
+ 
+ #define TIMECODE_SCALE              1000000
diff --git a/makemkv.SlackBuild b/makemkv.SlackBuild
index c679d96..beb63c0 100755
--- a/makemkv.SlackBuild
+++ b/makemkv.SlackBuild
@@ -23,7 +23,7 @@
 # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 PRGNAM=makemkv
-VERSION=${VERSION:-1.9.7}
+VERSION=${VERSION:-1.9.9}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
@@ -86,6 +86,11 @@ find -L . \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
+# inttypes.h gets included (by libebml, I think) before
+# __STDC_FORMAT_MACROS is set. Make sure this gets set before inttypes.h
+# gets loaded
+patch -p1 < $CWD/inttypes.patch
+
 CFLAGS="$SLKCFLAGS" \
 CXXFLAGS="$SLKCFLAGS" \
 ./configure \
diff --git a/makemkv.info b/makemkv.info
index 5037075..ac61c7c 100644
--- a/makemkv.info
+++ b/makemkv.info
@@ -1,10 +1,10 @@
 PRGNAM="makemkv"
-VERSION="1.9.7"
+VERSION="1.9.9"
 HOMEPAGE="http://www.makemkv.com/"
-DOWNLOAD="http://www.makemkv.com/download/makemkv-oss-1.9.7.tar.gz \
-          http://www.makemkv.com/download/makemkv-bin-1.9.7.tar.gz"
-MD5SUM="2c0b0d31d1e1fb8576db024c7f02399c \
-        52bd49e4667284ce27cbec6a5d8b8877"
+DOWNLOAD="http://www.makemkv.com/download/makemkv-oss-1.9.9.tar.gz \
+          http://www.makemkv.com/download/makemkv-bin-1.9.9.tar.gz"
+MD5SUM="5bdfdb4fd5e5136787ecfa8856f485c8 \
+        22ae44280ad88d87d9150743d167f4e5"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES="ffmpeg"

From willysr at slackbuilds.org  Mon Feb  1 11:32:00 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 1 Feb 2016 18:32:00 +0700
Subject: [Slackbuilds-users] MakeMKV update
In-Reply-To: <20160201011553.GB2797@MyPC.phub.net.cable.rogers.com>
References: <20160201011553.GB2797@MyPC.phub.net.cable.rogers.com>
Message-ID: <56AF4230.9010609@slackbuilds.org>

> I have attached 2 patches, one that just points to the moved sources for
> 1.9.7 and another that updates to 1.9.9. You can choose whichever one
> you want, though obviously when submissions re-open I would end up
> submitting the updated version anyway.

Applied the updates to 1.9.9 into 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/20160201/3f772bfd/attachment-0001.asc>

From richard at aaazen.com  Thu Feb  4 04:35:48 2016
From: richard at aaazen.com (Richard)
Date: Wed, 3 Feb 2016 20:35:48 -0800 (PST)
Subject: [Slackbuilds-users] OpenSMTPD 5.7.3p2 fix for OpenSSL 1.0.2f (for
	current and 14.1)
Message-ID: <alpine.LNX.2.20.1602031918290.30404@monday.test>

There is a new patch version of OpenSMTPD, 5.7.3p2

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

- OpenSSL 1.0.2f was released by the OpenSSL project to address security
  issues, unfortunately that patchlevel release also introduces a change
  in the API we relied upon for our privileges separated RSA engine.

It builds and runs fine on Slackware64 current with OpenSSL 1.0.2f (and
with 1.0.2e)

And it builds and runs fine on Slackware64 14.1 with OpenSSL 1.0.1r

Richard Narron
-------------- next part --------------
Only in opensmtpd-5.7.3p1: opensmtpd-5.7.3p1.tar.gz
Only in opensmtpd-5.7.3p2: opensmtpd-5.7.3p2.tar.gz
diff -r -u opensmtpd-5.7.3p1/opensmtpd.SlackBuild opensmtpd-5.7.3p2/opensmtpd.SlackBuild
--- opensmtpd-5.7.3p1/opensmtpd.SlackBuild	2015-10-05 07:10:55.000000000 -0700
+++ opensmtpd-5.7.3p2/opensmtpd.SlackBuild	2016-02-03 10:53:26.000000000 -0800
@@ -3,7 +3,7 @@
 # Slackware build script for opensmtpd
 
 # Copyright 2013-2014  Robby Workman, Northport, Alabama, USA
-# Copyright 2015  Richard Narron, California, USA
+# Copyright 2015-2016  Richard Narron, California, USA
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -24,7 +24,7 @@
 #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 PRGNAM=opensmtpd
-VERSION=${VERSION:-5.7.3p1}
+VERSION=${VERSION:-5.7.3p2}
 EXTRAS=${EXTRAS:-5.7.1}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
diff -r -u opensmtpd-5.7.3p1/opensmtpd.info opensmtpd-5.7.3p2/opensmtpd.info
--- opensmtpd-5.7.3p1/opensmtpd.info	2015-10-05 07:32:07.000000000 -0700
+++ opensmtpd-5.7.3p2/opensmtpd.info	2016-02-02 11:14:13.000000000 -0800
@@ -1,8 +1,8 @@
 PRGNAM="opensmtpd"
-VERSION="5.7.3p1"
+VERSION="5.7.3p2"
 HOMEPAGE="http://www.opensmtpd.org/"
-DOWNLOAD="http://www.opensmtpd.org/archives/opensmtpd-5.7.3p1.tar.gz"
-MD5SUM="754abb7f08c094273f098d761c8c2221"   
+DOWNLOAD="http://www.opensmtpd.org/archives/opensmtpd-5.7.3p2.tar.gz"
+MD5SUM="85bdccf1f28945771f79fd33e893cc43"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES="libasr"

From marc at mos6581.de  Thu Feb  4 18:24:25 2016
From: marc at mos6581.de (Marcel Saegebarth)
Date: Thu, 4 Feb 2016 19:24:25 +0100
Subject: [Slackbuilds-users] New maintainer for bitlbee
Message-ID: <56B39759.7050007@mos6581.de>

Michiel asked me if I want to takeover maintenance of bitlbee and I'll
do that.
Since there's no newer version out there, it still builds fine on
-current and submissions are closed anyway, I'd like to ask one of the
admins to change the maintainer of bitlbee.

Quote:

On 01/24/2016 03:17 PM, Michiel van Wessem wrote:
> I am currently withdrawing myself as maintainer from most of my builds.
> Would you be interested in taking over maintenance of the bitlbee
> Slackbuild from me?
>
> Michiel

The information is the same as for any other of my SlackBuilds.

Thanks

-marc

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

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

From matteo.bernardini at gmail.com  Thu Feb  4 18:32:41 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 4 Feb 2016 19:32:41 +0100
Subject: [Slackbuilds-users] New maintainer for bitlbee
In-Reply-To: <56B39759.7050007@mos6581.de>
References: <56B39759.7050007@mos6581.de>
Message-ID: <CAPsDuS7cHQx2iwt_v15-pEyStJWbk-cHj0WQk_ocBaw+tjmt3A@mail.gmail.com>

2016-02-04 19:24 GMT+01:00 Marcel Saegebarth <marc at mos6581.de>:
> Michiel asked me if I want to takeover maintenance of bitlbee and I'll
> do that.
> Since there's no newer version out there, it still builds fine on
> -current and submissions are closed anyway, I'd like to ask one of the
> admins to change the maintainer of bitlbee.
>
> Quote:
>
> On 01/24/2016 03:17 PM, Michiel van Wessem wrote:
>> I am currently withdrawing myself as maintainer from most of my builds.
>> Would you be interested in taking over maintenance of the bitlbee
>> Slackbuild from me?
>>
>> Michiel
>
> The information is the same as for any other of my SlackBuilds.

Done in my branch.

Matteo

From marc at mos6581.de  Thu Feb  4 20:56:27 2016
From: marc at mos6581.de (Marcel Saegebarth)
Date: Thu, 4 Feb 2016 21:56:27 +0100
Subject: [Slackbuilds-users] Dropped support Seafile
Message-ID: <56B3BAFB.7090809@mos6581.de>

Due to some heavy workload in the last couple of months I can't provide
support anymore.
Seafile is comfortable on the web UI and very appealing compared to
other open source projects and could be a serious competitor to
commercial and closed source software.
But from an administrator point of view it's a mess.
It heavily builds on Debian or Debian-based distros and from my
point of view, there's simply no real structure with all their
weird shell/python/daemon scripts and lacks good logs for
debugging.

-marc

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

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

From willysr at slackbuilds.org  Fri Feb  5 00:27:42 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 5 Feb 2016 07:27:42 +0700
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
Message-ID: <56B3EC7E.5070806@slackbuilds.org>

Hi folks,


i have just merged all branches in SBo to master branch and it includes
most of the bug and build fixes across all categories that we can fix in
the past few days.

There are still a lot of build failures out there and we need your help
to make sure our repository is ready for 14.2 when it has been released.

Here are the list of build failures compiled by David Spencer last week

  academic/openmodelica (i486)
  academic/tophat
  audio/ardour
  audio/audtty
  audio/azr3
  audio/guitarix
  audio/sooperlooper
  audio/wmauda
  desktop/conky-manager (i486)
  desktop/crystal
  desktop/kde-gtk-config
  desktop/rsl
  desktop/simon
  desktop/wmpinboard
  development/latrace
  development/mono2
  development/monodevelop
  development/mtd-utils
  development/noweb (x86_64)
  development/phantomjs
  development/pyclewn
  development/sbcl (i486)
  games/ValyriaTear
  games/cgmadness
  games/ckmame
  games/dolphin-emu (i486)
  games/ember
  games/etlegacy
  games/foobillardplus
  games/game_1945 (i486)
  games/generator_cbiere (i486)
  games/ioquake3 (i486)
  games/jfsw (i486)
  games/megaglest
  games/singularity (i486)
  games/unvanquished
  games/vbam (i486)
  gis/OTB
  gis/horao
  gis/pointcloud
  graphics/aeskulap
  graphics/autotrace
  graphics/brlcad
  graphics/fontmatrix
  graphics/kphotoalbum
  graphics/osgEarth
  graphics/rawtherapee
  graphics/scantailor
  haskell/haskell-platform
  libraries/barry
  libraries/ggz-base-libs
  libraries/gwenhywfar
  libraries/hug
  libraries/libffado
  libraries/libvmime
  libraries/python-ecore
  libraries/python-edje
  libraries/vdpau-video
  libraries/vid.stab
  misc/klibc (i486)
  misc/par2cmdline-tbb (i486)
  misc/seahorse-plugins
  multimedia/bombono-dvd
  multimedia/cantata
  multimedia/gnash
  multimedia/harmonySEQ
  multimedia/mplayer-codecs32 (x86_64)
  multimedia/mythtv
  multimedia/stills2dv
  multimedia/subtitleeditor
  multimedia/telepathy-qt
  network/dsniff (i486)
  network/mosaic-ck
  network/openvswitch
  network/retroshare
  network/seafile-server
  network/smstools3
  network/sockstress
  network/spamassassin
  network/t38modem
  network/wmget
  system/ksplice
  system/memtest86
  system/ofono
  system/s3ql
  system/xen

i486 means it happened on 32 bit arch only
x86_64 means it happened on 64 bit arch only
the rest happened on both platform

there might be some false alarm so please help us confirm those list

we have also set up a new branch removal-review for those we think it's
good to be removed due to many reasons (no upstream work, no longer
build, etc). If you need them please make sure it build and send patches
to us via this list or push the fixes to somewhere public where we can
see them (i personally accept git pull request from github)

please make sure you test them on latest clean slackware-current
environment.

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/20160205/fd5c31e8/attachment.asc>

From slackalaxy at gmail.com  Fri Feb  5 08:55:07 2016
From: slackalaxy at gmail.com (Petar Petrov)
Date: Fri, 5 Feb 2016 10:55:07 +0200
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B3EC7E.5070806@slackbuilds.org>
References: <56B3EC7E.5070806@slackbuilds.org>
Message-ID: <CAKXpWBfVWSnX7+R29gaPa9jhGrh_d-1_4Ztr00yDRWNs-0HCKQ@mail.gmail.com>

hi,

i'll see what i can do for academic/tophat over the weekend. If i can't fix
it, then we will have to remove it and possibly add it later if a new
version that builds is released. Alternatively, i can take the ready
binaries from the External Tools of Ugene (http://ugene.net/external.html)
and host it on SF myself.

-petar

2016-02-05 2:27 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:

> Hi folks,
>
>
> i have just merged all branches in SBo to master branch and it includes
> most of the bug and build fixes across all categories that we can fix in
> the past few days.
>
> There are still a lot of build failures out there and we need your help
> to make sure our repository is ready for 14.2 when it has been released.
>
> Here are the list of build failures compiled by David Spencer last week
>
>   academic/openmodelica (i486)
>   academic/tophat
>   audio/ardour
>   audio/audtty
>   audio/azr3
>   audio/guitarix
>   audio/sooperlooper
>   audio/wmauda
>   desktop/conky-manager (i486)
>   desktop/crystal
>   desktop/kde-gtk-config
>   desktop/rsl
>   desktop/simon
>   desktop/wmpinboard
>   development/latrace
>   development/mono2
>   development/monodevelop
>   development/mtd-utils
>   development/noweb (x86_64)
>   development/phantomjs
>   development/pyclewn
>   development/sbcl (i486)
>   games/ValyriaTear
>   games/cgmadness
>   games/ckmame
>   games/dolphin-emu (i486)
>   games/ember
>   games/etlegacy
>   games/foobillardplus
>   games/game_1945 (i486)
>   games/generator_cbiere (i486)
>   games/ioquake3 (i486)
>   games/jfsw (i486)
>   games/megaglest
>   games/singularity (i486)
>   games/unvanquished
>   games/vbam (i486)
>   gis/OTB
>   gis/horao
>   gis/pointcloud
>   graphics/aeskulap
>   graphics/autotrace
>   graphics/brlcad
>   graphics/fontmatrix
>   graphics/kphotoalbum
>   graphics/osgEarth
>   graphics/rawtherapee
>   graphics/scantailor
>   haskell/haskell-platform
>   libraries/barry
>   libraries/ggz-base-libs
>   libraries/gwenhywfar
>   libraries/hug
>   libraries/libffado
>   libraries/libvmime
>   libraries/python-ecore
>   libraries/python-edje
>   libraries/vdpau-video
>   libraries/vid.stab
>   misc/klibc (i486)
>   misc/par2cmdline-tbb (i486)
>   misc/seahorse-plugins
>   multimedia/bombono-dvd
>   multimedia/cantata
>   multimedia/gnash
>   multimedia/harmonySEQ
>   multimedia/mplayer-codecs32 (x86_64)
>   multimedia/mythtv
>   multimedia/stills2dv
>   multimedia/subtitleeditor
>   multimedia/telepathy-qt
>   network/dsniff (i486)
>   network/mosaic-ck
>   network/openvswitch
>   network/retroshare
>   network/seafile-server
>   network/smstools3
>   network/sockstress
>   network/spamassassin
>   network/t38modem
>   network/wmget
>   system/ksplice
>   system/memtest86
>   system/ofono
>   system/s3ql
>   system/xen
>
> i486 means it happened on 32 bit arch only
> x86_64 means it happened on 64 bit arch only
> the rest happened on both platform
>
> there might be some false alarm so please help us confirm those list
>
> we have also set up a new branch removal-review for those we think it's
> good to be removed due to many reasons (no upstream work, no longer
> build, etc). If you need them please make sure it build and send patches
> to us via this list or push the fixes to somewhere public where we can
> see them (i personally accept git pull request from github)
>
> please make sure you test them on latest clean slackware-current
> environment.
>
> Thanks
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> 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/20160205/07e3c4d8/attachment-0001.html>

From marc at mos6581.de  Fri Feb  5 09:14:58 2016
From: marc at mos6581.de (Marcel Saegebarth)
Date: Fri, 5 Feb 2016 10:14:58 +0100
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B3EC7E.5070806@slackbuilds.org>
References: <56B3EC7E.5070806@slackbuilds.org>
Message-ID: <56B46812.7050405@mos6581.de>

On 02/05/2016 01:27 AM, Willy Sudiarto Raharjo wrote:
>   network/seafile-server

It's working again since my libevhtp commit yesterday.

-------------- 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/20160205/583cc659/attachment.asc>

From pfeifer.felix at gmail.com  Fri Feb  5 09:25:00 2016
From: pfeifer.felix at gmail.com (Felix Pfeifer)
Date: Fri, 5 Feb 2016 10:25:00 +0100
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B46812.7050405@mos6581.de>
References: <56B3EC7E.5070806@slackbuilds.org>
	<56B46812.7050405@mos6581.de>
Message-ID: <CAPANF77LxJd5zzhwvuV4MMvmmOC=s2_uTwpQFhdTqD9nstHjEg@mail.gmail.com>

Hi,

i checked if i am still maintainer of emacs-w3m. As it is i am
although there were already 2 candidates who wanted to take
it over. Please remove either the package or my name under it. ;)

Also whoever asked to maintain it, yes please claim it!

Greetings,
Felix

On 5 February 2016 at 10:14, Marcel Saegebarth <marc at mos6581.de> wrote:
> On 02/05/2016 01:27 AM, Willy Sudiarto Raharjo wrote:
>>   network/seafile-server
>
> It's working again since my libevhtp commit yesterday.
>
>
> _______________________________________________
> 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  Fri Feb  5 11:51:29 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 5 Feb 2016 18:51:29 +0700
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B46812.7050405@mos6581.de>
References: <56B3EC7E.5070806@slackbuilds.org> <56B46812.7050405@mos6581.de>
Message-ID: <56B48CC1.1090801@slackbuilds.org>

>>   network/seafile-server
> 
> It's working again since my libevhtp commit yesterday.

Hi Marcel

the list was generated before your commits so probably some of them are
no longer valid since there were some commits by other maintainers as well.

David will try to build another list again this week based on latest
master branch

Big thanks for all your help!!!


-- 
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/20160205/77fd0faf/attachment.asc>

From martijn at inlv.org  Fri Feb  5 12:48:28 2016
From: martijn at inlv.org (Martijn Dekker)
Date: Fri, 05 Feb 2016 12:48:28 +0000
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B3EC7E.5070806@slackbuilds.org>
References: <56B3EC7E.5070806@slackbuilds.org>
Message-ID: <56B49A1C.1060502@inlv.org>

Willy Sudiarto Raharjo schreef op 05-02-16 om 00:27:
> There are still a lot of build failures out there and we need your help
> to make sure our repository is ready for 14.2 when it has been released.

Is this a good moment to bring up a few more general issues?

I'm thinking of two things for now:

1. That -fPIC compiler flag for x86_64. The -fPIC flag is only necessary
for shared libraries. For normal binaries, it's unnecessary and causes
binaries to be much larger. Bloat should be avoided.

Years ago it may have been convenient to add this flag explicitly
because many build systems failed to account for x86_64 -- the lack of
-fPIC in shared libraries would cause build failures. But now we're
living in 2016 and almost everyone uses x86_64, so every current build
system will know how to add the -fPIC flag itself where it is necessary.
I think it's past time to remove -fPIC from the template.

2. The following horrible, broken and obsolete eyesore:

find -L . \
 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
  -o -perm 511 \) -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

can be replaced by:

   chmod -R a-st,u+rwX,go-w+rX .

which (a) accounts for every possible case, unless the 'find' voodooa
bove; (b) is much shorter and (c) is *much* faster. (The capital X sets
+x only if at least one of the user, group or other is already set +x,
so the above will do the right thing and make all directories 755 and
all files either 755 or 664.)

Proof that this works:

   mkdir tempdir
   cd tempdir
   for M in {0..4}{0..7}{0..7}{0..7}; do touch f$M && chmod $M f$M; done
   ls -l | less  # see every possible permission
   chmod -R a-st,u+rwX,go-w+rX .
   ls -l | less  # they're all either 755 or 644

These two things have been annoying me for some time, so I hope you're
willing to consider this.

- Martijn


From rsamurti at gmail.com  Fri Feb  5 15:08:17 2016
From: rsamurti at gmail.com (Ananda Murthy R S)
Date: Fri, 5 Feb 2016 20:38:17 +0530
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B3EC7E.5070806@slackbuilds.org>
References: <56B3EC7E.5070806@slackbuilds.org>
Message-ID: <CAMwjf3UCLsh-GSAGpTsEiBFaJOBACVCox+z8CjSztd=NC8+vzA@mail.gmail.com>

Hello,

Please remove openmodelica for now. I will upload the buildscript later
after it builds properly on current.

Anand

On Fri, Feb 5, 2016 at 5:57 AM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> Hi folks,
>
>
> i have just merged all branches in SBo to master branch and it includes
> most of the bug and build fixes across all categories that we can fix in
> the past few days.
>
> There are still a lot of build failures out there and we need your help
> to make sure our repository is ready for 14.2 when it has been released.
>
> Here are the list of build failures compiled by David Spencer last week
>
>   academic/openmodelica (i486)
>   academic/tophat
>   audio/ardour
>   audio/audtty
>   audio/azr3
>   audio/guitarix
>   audio/sooperlooper
>   audio/wmauda
>   desktop/conky-manager (i486)
>   desktop/crystal
>   desktop/kde-gtk-config
>   desktop/rsl
>   desktop/simon
>   desktop/wmpinboard
>   development/latrace
>   development/mono2
>   development/monodevelop
>   development/mtd-utils
>   development/noweb (x86_64)
>   development/phantomjs
>   development/pyclewn
>   development/sbcl (i486)
>   games/ValyriaTear
>   games/cgmadness
>   games/ckmame
>   games/dolphin-emu (i486)
>   games/ember
>   games/etlegacy
>   games/foobillardplus
>   games/game_1945 (i486)
>   games/generator_cbiere (i486)
>   games/ioquake3 (i486)
>   games/jfsw (i486)
>   games/megaglest
>   games/singularity (i486)
>   games/unvanquished
>   games/vbam (i486)
>   gis/OTB
>   gis/horao
>   gis/pointcloud
>   graphics/aeskulap
>   graphics/autotrace
>   graphics/brlcad
>   graphics/fontmatrix
>   graphics/kphotoalbum
>   graphics/osgEarth
>   graphics/rawtherapee
>   graphics/scantailor
>   haskell/haskell-platform
>   libraries/barry
>   libraries/ggz-base-libs
>   libraries/gwenhywfar
>   libraries/hug
>   libraries/libffado
>   libraries/libvmime
>   libraries/python-ecore
>   libraries/python-edje
>   libraries/vdpau-video
>   libraries/vid.stab
>   misc/klibc (i486)
>   misc/par2cmdline-tbb (i486)
>   misc/seahorse-plugins
>   multimedia/bombono-dvd
>   multimedia/cantata
>   multimedia/gnash
>   multimedia/harmonySEQ
>   multimedia/mplayer-codecs32 (x86_64)
>   multimedia/mythtv
>   multimedia/stills2dv
>   multimedia/subtitleeditor
>   multimedia/telepathy-qt
>   network/dsniff (i486)
>   network/mosaic-ck
>   network/openvswitch
>   network/retroshare
>   network/seafile-server
>   network/smstools3
>   network/sockstress
>   network/spamassassin
>   network/t38modem
>   network/wmget
>   system/ksplice
>   system/memtest86
>   system/ofono
>   system/s3ql
>   system/xen
>
> i486 means it happened on 32 bit arch only
> x86_64 means it happened on 64 bit arch only
> the rest happened on both platform
>
> there might be some false alarm so please help us confirm those list
>
> we have also set up a new branch removal-review for those we think it's
> good to be removed due to many reasons (no upstream work, no longer
> build, etc). If you need them please make sure it build and send patches
> to us via this list or push the fixes to somewhere public where we can
> see them (i personally accept git pull request from github)
>
> please make sure you test them on latest clean slackware-current
> environment.
>
> Thanks
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> 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/
>
>
>


-- 
Close Windows ! Open source !!
Free software from proprietary mafia !!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160205/45887995/attachment.html>

From willysr at slackbuilds.org  Fri Feb  5 15:38:09 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 5 Feb 2016 22:38:09 +0700
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <CAMwjf3UCLsh-GSAGpTsEiBFaJOBACVCox+z8CjSztd=NC8+vzA@mail.gmail.com>
References: <56B3EC7E.5070806@slackbuilds.org>
 <CAMwjf3UCLsh-GSAGpTsEiBFaJOBACVCox+z8CjSztd=NC8+vzA@mail.gmail.com>
Message-ID: <56B4C1E1.6090407@slackbuilds.org>

> Please remove openmodelica for now. I will upload the buildscript later
> after it builds properly on current.

Thanks
pushed to removed-review for now


-- 
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/20160205/db548ab8/attachment.asc>

From hostmaster at slackonly.com  Fri Feb  5 18:10:38 2016
From: hostmaster at slackonly.com (Panagiotis Nikolaou)
Date: Fri, 5 Feb 2016 13:10:38 -0500
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B3EC7E.5070806@slackbuilds.org>
References: <56B3EC7E.5070806@slackbuilds.org>
Message-ID: <56B4E59E.8040307@slackonly.com>

> graphics/rawtherapee
The source is to old for gcc-5.3.

As until now 4.2 is the last release i have self hosted a fresh
snapshot from git and also i make a small modification to SlackBuild.

It builds fine now in both arch!
 
Thanks Panagiotis.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: rawtherapee.tar.gz
Type: application/gzip
Size: 3675 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160205/18cd5d5a/attachment-0001.bin>

From willysr at slackbuilds.org  Fri Feb  5 18:18:34 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 6 Feb 2016 01:18:34 +0700
Subject: [Slackbuilds-users] OpenSMTPD 5.7.3p2 fix for OpenSSL 1.0.2f
 (for current and 14.1)
In-Reply-To: <alpine.LNX.2.20.1602031918290.30404@monday.test>
References: <alpine.LNX.2.20.1602031918290.30404@monday.test>
Message-ID: <56B4E77A.5010301@slackbuilds.org>

> There is a new patch version of OpenSMTPD, 5.7.3p2
> 
> Issues fixed in this release (since 5.7.3p1):
> =============================================
> 
> - OpenSSL 1.0.2f was released by the OpenSSL project to address security
>   issues, unfortunately that patchlevel release also introduces a change
>   in the API we relied upon for our privileges separated RSA engine.
> 
> It builds and runs fine on Slackware64 current with OpenSSL 1.0.2f (and
> with 1.0.2e)
> 
> And it builds and runs fine on Slackware64 14.1 with OpenSSL 1.0.1r

Thanks
pushed to 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/20160206/2e710c6e/attachment.asc>

From willysr at slackbuilds.org  Fri Feb  5 20:35:13 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 6 Feb 2016 03:35:13 +0700
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <CAKXpWBfVWSnX7+R29gaPa9jhGrh_d-1_4Ztr00yDRWNs-0HCKQ@mail.gmail.com>
References: <56B3EC7E.5070806@slackbuilds.org>
 <CAKXpWBfVWSnX7+R29gaPa9jhGrh_d-1_4Ztr00yDRWNs-0HCKQ@mail.gmail.com>
Message-ID: <56B50781.5040104@slackbuilds.org>

> i'll see what i can do for academic/tophat over the weekend. If i can't fix
> it, then we will have to remove it and possibly add it later if a new
> version that builds is released. Alternatively, i can take the ready
> binaries from the External Tools of Ugene (http://ugene.net/external.html)
> and host it on SF myself.

I think i got it fixed, but it will require a new source, Seqan 1.4
according to ARCH Linux
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=tophat

please review my changes on my branch
https://slackbuilds.org/cgit/slackbuilds/log/?h=willysr-for-14.2


-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Fri Feb  5 20:42:53 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 6 Feb 2016 03:42:53 +0700
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B4E59E.8040307@slackonly.com>
References: <56B3EC7E.5070806@slackbuilds.org> <56B4E59E.8040307@slackonly.com>
Message-ID: <56B5094D.8080905@slackbuilds.org>

>> graphics/rawtherapee
> The source is to old for gcc-5.3.
> 
> As until now 4.2 is the last release i have self hosted a fresh
> snapshot from git and also i make a small modification to SlackBuild.
> 
> It builds fine now in both arch!

Hi Panagiotis

i have made a simpler fix on my branch to use new c++11x standard
please review my changes from my branch
https://slackbuilds.org/cgit/slackbuilds/log/?h=willysr-for-14.2


-- 
Willy Sudiarto Raharjo

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

From hostmaster at slackonly.com  Fri Feb  5 20:53:23 2016
From: hostmaster at slackonly.com (Panagiotis Nikolaou)
Date: Fri, 5 Feb 2016 15:53:23 -0500
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B5094D.8080905@slackbuilds.org>
References: <56B3EC7E.5070806@slackbuilds.org>
 <56B4E59E.8040307@slackonly.com> <56B5094D.8080905@slackbuilds.org>
Message-ID: <56B50BC3.6040007@slackonly.com>


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

On 02/05/2016 03:42 PM, Willy Sudiarto Raharjo wrote:
>>> graphics/rawtherapee >> The source is to old for gcc-5.3. >> >> As until now 4.2 is the last
release i have self hosted a fresh >> snapshot from git and also i make
a small modification to SlackBuild. >> >> It builds fine now in both
arch! > > Hi Panagiotis > > i have made a simpler fix on my branch to
use new c++11x standard > please review my changes from my branch >
https://slackbuilds.org/cgit/slackbuilds/log/?h=willysr-for-14.2 > > > >
> _______________________________________________ > 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/ >
Alright Willy!

But because the git version have some new improvements
if you want change the source.

Also maybe add this to the cmake options:
To make a build using "native" optimizations, write:
-DPROC_TARGET_NUMBER="2"

Thanks Panagiotis

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWtQvAAAoJEHEA/7TwEbKG3aYQALrPsiS3CqF3AF8FYmrtDah0
8fVNiUDPUK4DBPCNik5qe+HmK9LPgF/0pHgsS/yjGJ7W7rbzY1bqjb+XvFtFJe8F
1i3ZZloEMhgFcRyKTryAocbGQGhmYqk7pCD9I73X6vw4lrN5jwr589FGr4JIx3eB
ec/Rypz+TiWVISFfonc8Hmra0gpv8XO4B2G0dwbABtz1KeCfkTpDwwBy+VWaBNiz
FQtkULVRpPtsbyTbAvXyol5UbxaTj7UdsxhE/Js/VJFIA39BaA6mGxmz2S/yIl5B
tBnd/q6TB4yqfDC/1Y5GayxZWwBPMzIFfWdklfygiexmvZzeQsmUrOd604JWgN3N
dvOZDhR6jjyrKAHGdNCJq8yBU/yzEK3Z77a7jAQ1D2DOpkdokfiqZayzLev27/Pk
+a/76M9j8B14bDEJcQk+msJuI0TZFuBenFovMbSd+Imwb+AoJFsqET85myaWf3Rz
cOkB+u7O85NfnzYaN4Wh9viwKbp552uFVTYka24MnZwduYo/XwWSZHYs4CZOqxPy
Y1ZrlgT/QSGJaGH3Acrs6XugioIYaez9PWZSBkGTf4TNFSM77Zh+oFAuY1aGEHoc
BY0voT33CSlAp8RsYBTl9MI9yTvTQ8JZbUz7cIl+O0DHi4pYbaa4YihlsLDpI2bt
JjHIzZ0hUY1x4gHG0YIY
=zS7+
-----END PGP SIGNATURE-----

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

From willysr at slackbuilds.org  Fri Feb  5 20:57:19 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 6 Feb 2016 03:57:19 +0700
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B50BC3.6040007@slackonly.com>
References: <56B3EC7E.5070806@slackbuilds.org>
 <56B4E59E.8040307@slackonly.com> <56B5094D.8080905@slackbuilds.org>
 <56B50BC3.6040007@slackonly.com>
Message-ID: <56B50CAF.6020407@slackbuilds.org>

> But because the git version have some new improvements
> if you want change the source.
> 
> Also maybe add this to the cmake options:
> To make a build using "native" optimizations, write:
> -DPROC_TARGET_NUMBER="2"

Done
merged your changes with mine


-- 
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/20160206/cec76fdd/attachment.asc>

From slackbuilds at jaxartes.net  Sat Feb  6 19:45:36 2016
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Sat, 6 Feb 2016 11:45:36 -0800
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B3EC7E.5070806@slackbuilds.org>
References: <56B3EC7E.5070806@slackbuilds.org>
Message-ID: <56B64D60.1050202@jaxartes.net>

On 04/02/16 04:27 PM, Willy Sudiarto Raharjo wrote:
>    gis/OTB
>    gis/horao

Please remove these two from 14.2.

>    gis/pointcloud

This builds and runs fine for me.



From slackbuilds at jaxartes.net  Sat Feb  6 19:50:36 2016
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Sat, 6 Feb 2016 11:50:36 -0800
Subject: [Slackbuilds-users] SlackBuilds up for grabs
Message-ID: <56B64E8C.10903@jaxartes.net>

Hey everyone,

I'm not planning to maintain the following SlackBuild scripts for 14.2. 
Please consider them all up for grabs.

audio/podget
desktop/kfaenza-icon-theme
desktop/kpartsplugin
desktop/plasma-runner-browsefirefoxbookmarks
desktop/plasmaxplanet
desktop/vim-qt
desktop/wmfs
development/apache-jmeter
development/jython
development/spl
gis/geogig
gis/geogig-py
gis/geoserver
gis/geoserver-control-flow
gis/geoserver-css
gis/geoserver-javascript
gis/geoserver-oracle
gis/geoserver-pyramid
gis/geoserver-python
gis/geoserver-wps
gis/mobac
gis/prepair
gis/udig
libraries/jai
libraries/jai-imageio
libraries/lua-cmsgpack
network/glassfish
network/hostsblock
office/qamus 
 

python/py4j
system/thinkfan

Thanks, Ben

From artourter at gmail.com  Sat Feb  6 21:04:30 2016
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Sat, 6 Feb 2016 21:04:30 +0000
Subject: [Slackbuilds-users] SlackBuilds up for grabs
In-Reply-To: <56B64E8C.10903@jaxartes.net>
References: <56B64E8C.10903@jaxartes.net>
Message-ID: <CAK09-vmPm6yF7LQng0h1hBydNHW58w07xPh_sx0aPXX_hJsKMA@mail.gmail.com>

I can pick up vim-qt if noone else want it.

Cheers

Greg
On 6 Feb 2016 19:52, "Benjamin Trigona-Harany" <slackbuilds at jaxartes.net>
wrote:

> Hey everyone,
>
> I'm not planning to maintain the following SlackBuild scripts for 14.2.
> Please consider them all up for grabs.
>
> audio/podget
> desktop/kfaenza-icon-theme
> desktop/kpartsplugin
> desktop/plasma-runner-browsefirefoxbookmarks
> desktop/plasmaxplanet
> desktop/vim-qt
> desktop/wmfs
> development/apache-jmeter
> development/jython
> development/spl
> gis/geogig
> gis/geogig-py
> gis/geoserver
> gis/geoserver-control-flow
> gis/geoserver-css
> gis/geoserver-javascript
> gis/geoserver-oracle
> gis/geoserver-pyramid
> gis/geoserver-python
> gis/geoserver-wps
> gis/mobac
> gis/prepair
> gis/udig
> libraries/jai
> libraries/jai-imageio
> libraries/lua-cmsgpack
> network/glassfish
> network/hostsblock
> office/qamus
>
> python/py4j
> system/thinkfan
>
> Thanks, Ben
> _______________________________________________
> 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/20160206/d51db4c9/attachment-0001.html>

From willysr at slackbuilds.org  Sun Feb  7 00:23:40 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Feb 2016 07:23:40 +0700
Subject: [Slackbuilds-users] SlackBuilds up for grabs
In-Reply-To: <56B64E8C.10903@jaxartes.net>
References: <56B64E8C.10903@jaxartes.net>
Message-ID: <56B68E8C.8080306@slackbuilds.org>

> I'm not planning to maintain the following SlackBuild scripts for 14.2.
> Please consider them all up for grabs.

> development/apache-jmeter
> network/hostsblock

I will take these two :)

-- 
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/20160207/219fbc0e/attachment.asc>

From willysr at slackbuilds.org  Sun Feb  7 00:41:04 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Feb 2016 07:41:04 +0700
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B64D60.1050202@jaxartes.net>
References: <56B3EC7E.5070806@slackbuilds.org> <56B64D60.1050202@jaxartes.net>
Message-ID: <56B692A0.8020303@slackbuilds.org>

>>    gis/OTB
>>    gis/horao
> 
> Please remove these two from 14.2.

done, added to removal-review

>>    gis/pointcloud
> 
> This builds and runs fine for me.

Unfortunately not for us

gcc -o cu_tester cu_tester.o cu_pc_bytes.o cu_pc_schema.o cu_pc_point.o
cu_pc_patch.o cu_pc_patch_ght.o ../libpc.a -lxml2 -lz -lm -ldl -lcunit
-lz  -lm
make[2]: Leaving directory '/tmp/SBo/pointcloud-1.0.1/lib/cunit'
make[1]: Leaving directory '/tmp/SBo/pointcloud-1.0.1/lib'
make -C pgsql all
make[1]: Entering directory '/tmp/SBo/pointcloud-1.0.1/pgsql'
gcc -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute
-Wformat-security -fno-strict-aliasing -fwrapv
-fexcess-precision=standard -O2 -fPIC -fpic -I../lib -I. -I./
-I/usr/include/postgresql/server -I/usr/include/postgresql/internal
-D_GNU_SOURCE -I/usr/include/libxml2   -c -o pc_inout.o pc_inout.c
gcc -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute
-Wformat-security -fno-strict-aliasing -fwrapv
-fexcess-precision=standard -O2 -fPIC -fpic -I../lib -I. -I./
-I/usr/include/postgresql/server -I/usr/include/postgresql/internal
-D_GNU_SOURCE -I/usr/include/libxml2   -c -o pc_access.o pc_access.c
pc_access.c: In function ?pointcloud_agg_transfn?:
pc_access.c:318:46: error: ?AggState {aka struct AggState}? has no
member named ?aggcontext?
   aggcontext = ((AggState *) fcinfo->context)->aggcontext;
                                              ^
<builtin>: recipe for target 'pc_access.o' failed
make[1]: *** [pc_access.o] Error 1
make[1]: Leaving directory '/tmp/SBo/pointcloud-1.0.1/pgsql'
Makefile:3: recipe for target 'all' failed
make: *** [all] Error 2


-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Sun Feb  7 01:10:16 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Feb 2016 08:10:16 +0700
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B692A0.8020303@slackbuilds.org>
References: <56B3EC7E.5070806@slackbuilds.org> <56B64D60.1050202@jaxartes.net>
 <56B692A0.8020303@slackbuilds.org>
Message-ID: <56B69978.8080806@slackbuilds.org>

>> This builds and runs fine for me.
> 
> Unfortunately not for us
> 
> gcc -o cu_tester cu_tester.o cu_pc_bytes.o cu_pc_schema.o cu_pc_point.o
> cu_pc_patch.o cu_pc_patch_ght.o ../libpc.a -lxml2 -lz -lm -ldl -lcunit
> -lz  -lm
> make[2]: Leaving directory '/tmp/SBo/pointcloud-1.0.1/lib/cunit'
> make[1]: Leaving directory '/tmp/SBo/pointcloud-1.0.1/lib'
> make -C pgsql all
> make[1]: Entering directory '/tmp/SBo/pointcloud-1.0.1/pgsql'
> gcc -Wall -Wmissing-prototypes -Wpointer-arith
> -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute
> -Wformat-security -fno-strict-aliasing -fwrapv
> -fexcess-precision=standard -O2 -fPIC -fpic -I../lib -I. -I./
> -I/usr/include/postgresql/server -I/usr/include/postgresql/internal
> -D_GNU_SOURCE -I/usr/include/libxml2   -c -o pc_inout.o pc_inout.c
> gcc -Wall -Wmissing-prototypes -Wpointer-arith
> -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute
> -Wformat-security -fno-strict-aliasing -fwrapv
> -fexcess-precision=standard -O2 -fPIC -fpic -I../lib -I. -I./
> -I/usr/include/postgresql/server -I/usr/include/postgresql/internal
> -D_GNU_SOURCE -I/usr/include/libxml2   -c -o pc_access.o pc_access.c
> pc_access.c: In function ?pointcloud_agg_transfn?:
> pc_access.c:318:46: error: ?AggState {aka struct AggState}? has no
> member named ?aggcontext?
>    aggcontext = ((AggState *) fcinfo->context)->aggcontext;
>                                               ^
> <builtin>: recipe for target 'pc_access.o' failed
> make[1]: *** [pc_access.o] Error 1
> make[1]: Leaving directory '/tmp/SBo/pointcloud-1.0.1/pgsql'
> Makefile:3: recipe for target 'all' failed
> make: *** [all] Error 2

just managed to fix it now
i added upstream commit to build properly against postgresql 9.5
please remove the patch when 1.1.0 is released

-- 
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/20160207/89aa147a/attachment.asc>

From alik at ejik.org  Sun Feb  7 01:34:20 2016
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sun, 07 Feb 2016 04:34:20 +0300
Subject: [Slackbuilds-users] broken source for google-droid-fonts
Message-ID: <1454808860.3411972.514023930.331D0D6B@webmail.messagingengine.com>

Hello,

the source file for google-droid-fonts
(platform_frameworks_base-5.x-20141010-fonts.tar.xz) contains only
DroidSansFallback.ttf
DroidSansFallbackFull.ttf
DroidSansMono.ttf

I think, the previous version
http://sourceforge.net/projects/slackbuildsdirectlinks/files/google-droid-fonts/platform_frameworks_base-4.x.fonts.tar.gz
should be used.  It contains:
DroidKufi-Bold.ttf
DroidKufi-Regular.ttf
DroidNaskh-Bold.ttf
DroidNaskh-Regular.ttf
DroidNaskhUI-Regular.ttf
DroidSans-Bold.ttf
DroidSans.ttf
DroidSansArabic.ttf
DroidSansArmenian.ttf
DroidSansEthiopic-Bold.ttf
DroidSansEthiopic-Regular.ttf
DroidSansFallback.ttf
DroidSansFallbackFull.ttf
DroidSansFallbackLegacy.ttf
DroidSansGeorgian.ttf
DroidSansHebrew-Bold.ttf
DroidSansHebrew-Regular.ttf
DroidSansJapanese.ttf
DroidSansMono.ttf
DroidSerif-Bold.ttf
DroidSerif-BoldItalic.ttf
DroidSerif-Italic.ttf
DroidSerif-Regular.ttf

Alexander

From novalazy at gmail.com  Sun Feb  7 01:58:47 2016
From: novalazy at gmail.com (Peter Wang)
Date: Sun, 7 Feb 2016 12:58:47 +1100
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B3EC7E.5070806@slackbuilds.org>
References: <56B3EC7E.5070806@slackbuilds.org>
Message-ID: <20160207125847.GC7648@hili.localdomain>

On Fri, 5 Feb 2016 07:27:42 +0700, Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:
>   development/latrace

Please remove latrace.

Peter

From willysr at slackbuilds.org  Sun Feb  7 02:00:28 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Feb 2016 09:00:28 +0700
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <20160207125847.GC7648@hili.localdomain>
References: <56B3EC7E.5070806@slackbuilds.org>
 <20160207125847.GC7648@hili.localdomain>
Message-ID: <56B6A53C.8070608@slackbuilds.org>

>>   development/latrace
> 
> Please remove latrace.

Done


-- 
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/20160207/3dd7c269/attachment.asc>

From unix_lists at f-m.fm  Sun Feb  7 02:15:26 2016
From: unix_lists at f-m.fm (unix_lists at f-m.fm)
Date: Sat, 06 Feb 2016 20:15:26 -0600
Subject: [Slackbuilds-users] SlackBuilds up for grabs
In-Reply-To: <56B68E8C.8080306@slackbuilds.org>
References: <56B64E8C.10903@jaxartes.net> <56B68E8C.8080306@slackbuilds.org>
Message-ID: <1454811326.1331813.514045754.106C4665@webmail.messagingengine.com>



On Sat, Feb 6, 2016, at 06:23 PM, Willy Sudiarto Raharjo wrote:
> > I'm not planning to maintain the following SlackBuild scripts for 14.2.
> > Please consider them all up for grabs.
> 
I'll take system/thinkfan
-- 
 Regards,
Donald Cooley

From ryan.q at linux.com  Sun Feb  7 04:11:17 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Sat, 6 Feb 2016 20:11:17 -0800
Subject: [Slackbuilds-users] broken source for google-droid-fonts
In-Reply-To: <1454808860.3411972.514023930.331D0D6B@webmail.messagingengine.com>
References: <1454808860.3411972.514023930.331D0D6B@webmail.messagingengine.com>
Message-ID: <CAAcyf-pQCMG0312KvkNChNfYwkoUEStrOKa5-uH-HzCK8bdnqg@mail.gmail.com>

On Feb 6, 2016 5:34 PM, "Alexander Verbovetsky" <alik at ejik.org> wrote:
>
> Hello,
>
> the source file for google-droid-fonts
> (platform_frameworks_base-5.x-20141010-fonts.tar.xz) contains only
> DroidSansFallback.ttf
> DroidSansFallbackFull.ttf
> DroidSansMono.ttf
>
> I think, the previous version
>
http://sourceforge.net/projects/slackbuildsdirectlinks/files/google-droid-fonts/platform_frameworks_base-4.x.fonts.tar.gz
> should be used.  It contains:
> DroidKufi-Bold.ttf
> DroidKufi-Regular.ttf
> DroidNaskh-Bold.ttf
> DroidNaskh-Regular.ttf
> DroidNaskhUI-Regular.ttf
> DroidSans-Bold.ttf
> DroidSans.ttf
> DroidSansArabic.ttf
> DroidSansArmenian.ttf
> DroidSansEthiopic-Bold.ttf
> DroidSansEthiopic-Regular.ttf
> DroidSansFallback.ttf
> DroidSansFallbackFull.ttf
> DroidSansFallbackLegacy.ttf
> DroidSansGeorgian.ttf
> DroidSansHebrew-Bold.ttf
> DroidSansHebrew-Regular.ttf
> DroidSansJapanese.ttf
> DroidSansMono.ttf
> DroidSerif-Bold.ttf
> DroidSerif-BoldItalic.ttf
> DroidSerif-Italic.ttf
> DroidSerif-Regular.ttf

This is an upstream issue, right?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160206/aa263fd9/attachment-0001.html>

From willysr at slackbuilds.org  Sun Feb  7 08:22:35 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Feb 2016 15:22:35 +0700
Subject: [Slackbuilds-users] Next Round of Testing
Message-ID: <56B6FECB.8030200@slackbuilds.org>

Hi guys

Merged all branches into master branch just now and this are the changes
since last merge:

libraries/libgtop: Updated for version 2.32.0.
libraries/libwnck3: Updated for version 3.14.1.
games/frozen-bubble: Update maintainer information.
libraries/php-ssh2: Fix php ini file location.
libraries/php-redis: Add missing pecl registration.
libraries/php-pgsql: Updated for version 5.6.18.
libraries/php-pdo_dblib: Updated for version 5.6.18.
libraries/php-mssql: Updated for version 5.6.18.
libraries/php-memcached: Fix php ini file location.
libraries/php-memcache: Fix php ini file location.
libraries/php-imagick: Updated for version 3.3.0.
graphics/graphviz: Fix php ini file location.
development/xdebug: Updated for version 2.3.3.
development/php-pinba: Fix php ini file location.
development/php-apcu: Fix php ini file location.
development/ming: Fix php ini file location.
development/ioncube-loader: Fix php ini file location.
development/ecl: Drop note about gc/libatomic_ops from README.
libraries/libatomic_ops: Removed. Included in Slackware 14.2.
libraries/libopensync: Removed. Dead upstream.
libraries/barry: Fix build on 14.2.
libraries/hug: Updated for version 0.100.
development/bacon: Updated for version 3.2.2.
libraries/libvmime: Updated for version 156edf5c.
network/hostsblock: New maintainer.
development/apache-jmeter: New maintainer.
libraries/libffado: Updated for version 2.2.1.
gis/pointcloud: Fix build against postgresql 9.5.
network/tor-browser: Updated for version 5.5.
libraries/libwfut: Remove references to non-exist header.
graphics/osgEarth: Update Build.
libraries/CEGUI0.7: Fix Build.
libraries/ogre: Fix build.
graphics/rawtherapee: Update to newer source.
graphics/kphotoalbum: Updated for version 4.7.
academic/tophat: Fix Build.
development/re2c: Updated for version 0.16.
development/poedit: Updated for version 1.8.7.
network/opensmtpd: Updated for version 5.7.3p2.
games/ckmame: Updated for version 0.12.
games/cgmadness: Fix build.
office/LibreOffice: Fix Build on x86.
games/megaglest: Fix build.
games/etlegacy: Update MD5SUM.
audio/gogglesmm: Updated for version 1.0.12.
libraries/fox-toolkit-devel: Added (FOX C++ Graphical Toolkit).

most of the commits above fixed the one listed in the BUILD FAIL
compiled by David Spencer.

i accidentally missed Dimitris' branch while merging, so his work will
be part of the next update.

here are the remaining entries of the BUILD FAIL from last week

  audio/ardour
  audio/audtty
  audio/azr3
  audio/guitarix
  audio/sooperlooper
  audio/wmauda
  desktop/conky-manager
  desktop/crystal
  desktop/kde-gtk-config
  desktop/rsl
  desktop/simon
  desktop/wmpinboard
  development/latrace
  development/mono2
  development/monodevelop
  development/mtd-utils
  development/noweb
  development/phantomjs
  development/pyclewn
  games/ValyriaTear
  games/dolphin-emu
  games/ember
  games/foobillardplus
  games/ioquake3
  games/jfsw
  games/singularity
  games/unvanquished
  games/vbam
  graphics/aeskulap
  graphics/autotrace
  graphics/brlcad
  graphics/fontmatrix
  graphics/scantailor
  haskell/haskell-platform
  libraries/ggz-base-libs
  libraries/gwenhywfar
  libraries/vdpau-video
  libraries/vid.stab
  misc/klibc
  misc/par2cmdline-tbb
  misc/seahorse-plugins
  multimedia/bombono-dvd
  multimedia/cantata
  multimedia/gnash
  multimedia/harmonySEQ
  multimedia/mplayer-codecs32
  multimedia/mythtv
  multimedia/stills2dv
  multimedia/subtitleeditor
  multimedia/telepathy-qt
  network/dsniff
  network/mosaic-ck
  network/openvswitch
  network/retroshare
  network/smstools3
  network/sockstress
  network/spamassassin
  network/t38modem
  network/wmget
  system/xen


-- 
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/20160207/907496de/attachment.asc>

From didier at slint.fr  Sun Feb  7 09:42:32 2016
From: didier at slint.fr (Didier Spaier)
Date: Sun, 7 Feb 2016 10:42:32 +0100
Subject: [Slackbuilds-users] Next Round of Testing => Developer wanted
In-Reply-To: <56B6FECB.8030200@slackbuilds.org>
References: <56B6FECB.8030200@slackbuilds.org>
Message-ID: <56B71188.6000600@slint.fr>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/02/2016 09:22, Willy Sudiarto Raharjo wrote:
> development/poedit: Updated for version 1.8.7.

Thanks for this one Willy. Some Slint translators prefer poedit over
lokalize.

By the way, I ave made feature request some time ago:
show cursor position in statusbar to allow easy length checking #218
https://github.com/vslavik/poedit/issues/218

As requested by V?clav I would like to have provided a patch,
unfortunately I never wrote a single line of C.

Look at this and do the job, anyone?

This would make me very happy as that's the only missing feature that
prevents me to use poedit.

Didier
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJWtxGIAAoJENUCAu9gwD7qOXkH/3alpsskkGXtVnmbu610L9zl
E/vWM4hA3M6+f0X5O/e6PjRnnpYDKDKeqDB4YyPog1DyUX56hbrsKfWMZX44o+9O
G0RTaORe7R8NjPu2Inpqz+8xpYsUi4uWcLX2DT4LJwLhogjlc5bfxbTPwW7uD76p
q/lX645OYvF9JB5rJI4WyvEWeHtHycOTobkHMcPpuOxrVXWS6rH6NKXythvhzVx6
z2OTYbN8DPKjjqH2EWg6/VpwoaZ9PRkUTzsBl+URvYKDnyhnD6OQwnvjecUNtkRV
tDZm4buO5GvzfO3C+MbWhtrzPUWuZd6RkchP7Int5dko3Tlxon6TkvpUQx4IyFw=
=VfIj
-----END PGP SIGNATURE-----
-------------- 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/20160207/5fe0a728/attachment.bin>

From matteo.bernardini at gmail.com  Sun Feb  7 09:46:03 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 7 Feb 2016 10:46:03 +0100
Subject: [Slackbuilds-users] Next Round of Testing
In-Reply-To: <56B6FECB.8030200@slackbuilds.org>
References: <56B6FECB.8030200@slackbuilds.org>
Message-ID: <CAPsDuS6LS8z8-=Yyo_j2s-uXtPxEAheECjUO-aA2eFkZDBkG1Q@mail.gmail.com>

2016-02-07 9:22 GMT+01:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:
>   games/dolphin-emu

I've pushed an update for this on my branch: maybe Larry should want
to have a look at this but for the little testing I have done it seems
to work.

Matteo

From alik at ejik.org  Sun Feb  7 10:46:50 2016
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sun, 07 Feb 2016 13:46:50 +0300
Subject: [Slackbuilds-users] broken source for google-droid-fonts
In-Reply-To: <CAAcyf-pQCMG0312KvkNChNfYwkoUEStrOKa5-uH-HzCK8bdnqg@mail.gmail.com>
References: <1454808860.3411972.514023930.331D0D6B@webmail.messagingengine.com>
 <CAAcyf-pQCMG0312KvkNChNfYwkoUEStrOKa5-uH-HzCK8bdnqg@mail.gmail.com>
Message-ID: <1454842010.3553348.514197194.03400B67@webmail.messagingengine.com>

On Sun, Feb 7, 2016, at 07:11, Ryan P.C. McQuen wrote:
> On Feb 6, 2016 5:34 PM, "Alexander Verbovetsky" <alik at ejik.org> wrote:
> >
> > Hello,
> >
> > the source file for google-droid-fonts
> > (platform_frameworks_base-5.x-20141010-fonts.tar.xz) contains only
> > DroidSansFallback.ttf
> > DroidSansFallbackFull.ttf
> > DroidSansMono.ttf
> >
> > I think, the previous version
> >
> http://sourceforge.net/projects/slackbuildsdirectlinks/files/google-droid-fonts/platform_frameworks_base-4.x.fonts.tar.gz
> > should be used.  It contains:
> > DroidKufi-Bold.ttf
> > DroidKufi-Regular.ttf
> > DroidNaskh-Bold.ttf
> > DroidNaskh-Regular.ttf
> > DroidNaskhUI-Regular.ttf
> > DroidSans-Bold.ttf
> > DroidSans.ttf
> > DroidSansArabic.ttf
> > DroidSansArmenian.ttf
> > DroidSansEthiopic-Bold.ttf
> > DroidSansEthiopic-Regular.ttf
> > DroidSansFallback.ttf
> > DroidSansFallbackFull.ttf
> > DroidSansFallbackLegacy.ttf
> > DroidSansGeorgian.ttf
> > DroidSansHebrew-Bold.ttf
> > DroidSansHebrew-Regular.ttf
> > DroidSansJapanese.ttf
> > DroidSansMono.ttf
> > DroidSerif-Bold.ttf
> > DroidSerif-BoldItalic.ttf
> > DroidSerif-Italic.ttf
> > DroidSerif-Regular.ttf
> 
> This is an upstream issue, right?

No, the file
/etc/fonts/conf.avail/35-droid.conf
refers to the fonts that are not installed (DroidSerif-Regular.ttf and
DroidSans.ttf).

Also, with source version 5 we here at SBo are loosing the Droid fonts
as they were, why?

Alexander

From info at microlinux.fr  Sun Feb  7 11:24:17 2016
From: info at microlinux.fr (Nicolas Kovacs)
Date: Sun, 7 Feb 2016 12:24:17 +0100
Subject: [Slackbuilds-users] broken source for google-droid-fonts
In-Reply-To: <1454808860.3411972.514023930.331D0D6B@webmail.messagingengine.com>
References: <1454808860.3411972.514023930.331D0D6B@webmail.messagingengine.com>
Message-ID: <56B72961.60803@microlinux.fr>

Le 07/02/2016 02:34, Alexander Verbovetsky a ?crit :
> I think, the previous version
> http://sourceforge.net/projects/slackbuildsdirectlinks/files/google-droid-fonts/platform_frameworks_base-4.x.fonts.tar.gz
> should be used.  It contains:

I also noticed that problem. I solved it by using the previous version
of Google Droid for my MLED repo.

Cheers,

Niki

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

From didier at slint.fr  Sun Feb  7 12:37:01 2016
From: didier at slint.fr (Didier Spaier)
Date: Sun, 7 Feb 2016 13:37:01 +0100
Subject: [Slackbuilds-users] broken source for google-droid-fonts
In-Reply-To: <1454808860.3411972.514023930.331D0D6B@webmail.messagingengine.com>
References: <1454808860.3411972.514023930.331D0D6B@webmail.messagingengine.com>
Message-ID: <56B73A6D.4040000@slint.fr>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On 07/02/2016 02:34, Alexander Verbovetsky wrote:
> Hello,
> 
> the source file for google-droid-fonts 
> (platform_frameworks_base-5.x-20141010-fonts.tar.xz) contains only 
> DroidSansFallback.ttf DroidSansFallbackFull.ttf DroidSansMono.ttf
> 
> I think, the previous version 
> http://sourceforge.net/projects/slackbuildsdirectlinks/files/google-droid-fonts/platform_frameworks_base-4.x.fonts.tar.gz
>
> 
should be used.  It contains:
> DroidKufi-Bold.ttf DroidKufi-Regular.ttf DroidNaskh-Bold.ttf 
> DroidNaskh-Regular.ttf DroidNaskhUI-Regular.ttf DroidSans-Bold.ttf 
> DroidSans.ttf DroidSansArabic.ttf DroidSansArmenian.ttf 
> DroidSansEthiopic-Bold.ttf DroidSansEthiopic-Regular.ttf 
> DroidSansFallback.ttf DroidSansFallbackFull.ttf 
> DroidSansFallbackLegacy.ttf DroidSansGeorgian.ttf 
> DroidSansHebrew-Bold.ttf DroidSansHebrew-Regular.ttf 
> DroidSansJapanese.ttf DroidSansMono.ttf DroidSerif-Bold.ttf 
> DroidSerif-BoldItalic.ttf DroidSerif-Italic.ttf 
> DroidSerif-Regular.ttf
> 
> Alexander

IMO we should consider moving to the noto fonts anyway.

See "Special Note on Droid Fonts" at the bottom of:
https://github.com/googlei18n/noto-fonts

I will check that out.

I was leaded there because Behdad Esfahbod is one of the developers.

Cheers, Didier
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJWtzptAAoJENUCAu9gwD7qRRYIALu+o+WYUMM3/gpQaahbVRtm
hnVvXygLwzQ400W7/iddIe9FanG8ZE/0mvf17+3MaewwvnXQCcxLlwRZrfOwC3AT
wLwcqhyDFPSS97Sgjs98H/WSBuA7ODhkVlOM1iCdOICqMjjaz7tyhzwtkLLMMnId
sBakfu2bhthaiMl4PCgIUAjC7gD7yapbqfK4HNfa2arolwzdKvqqNQ/kQfW3F3vB
o2WBmTe7Wjn6MWcyW1r1CzBUxZvka+we2+6BriNergcLeq9DLnpuPM4imOUWjhof
Wfb9R4Ke6RrNyXz7pydHmM5OLDL0kgAZ40bXCCUHheAxWyVhxamqzxn+0xelAnQ=
=afdk
-----END PGP SIGNATURE-----
-------------- 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/20160207/2cd599d4/attachment.bin>

From chris.willing at iinet.net.au  Sun Feb  7 12:59:28 2016
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Sun, 7 Feb 2016 22:59:28 +1000
Subject: [Slackbuilds-users] Next Round of Testing - mythtv
In-Reply-To: <56B6FECB.8030200@slackbuilds.org>
References: <56B6FECB.8030200@slackbuilds.org>
Message-ID: <56B73FB0.7010207@iinet.net.au>

On 07/02/16 18:22, Willy Sudiarto Raharjo wrote:

>
> here are the remaining entries of the BUILD FAIL from last week
>
...
>    multimedia/mythtv

I just tried a quick build using the latest source code from 
https://codeload.github.com/MythTV/mythtv/tar.gz/fixes/0.27
(this is 0.27.6 apparently). It builds to completion if the 
--enable-libvpx option is removed from the configure command.

I don't use mythtv myself so I can't really say if this is a reasonable 
omission to enable the build, although I see it is not enabled by default.

chris


From didier at slint.fr  Sun Feb  7 13:13:21 2016
From: didier at slint.fr (Didier Spaier)
Date: Sun, 7 Feb 2016 14:13:21 +0100
Subject: [Slackbuilds-users] broken source for google-droid-fonts
In-Reply-To: <56B73A6D.4040000@slint.fr>
References: <1454808860.3411972.514023930.331D0D6B@webmail.messagingengine.com>
 <56B73A6D.4040000@slint.fr>
Message-ID: <56B742F1.9080409@slint.fr>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/02/2016 13:37, Didier Spaier wrote:
> IMO we should consider moving to the noto fonts anyway.
> 
> See "Special Note on Droid Fonts" at the bottom of: 
> https://github.com/googlei18n/noto-fonts
> 
> I will check that out.
> 
Done, no issue. I just followed the instructions here:
https://www.google.com/get/noto/

The "all in one" source zip file is huge (471,2 MB) , so maybe one could
consider making separate packages for CJK/nonCJK fonts.

I assume that Ryan will volunteer to maintain SlackBuilds for noto ;)

Else and only if nobody else is interested I will do that.

Cheers, Didier
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJWt0LxAAoJENUCAu9gwD7qdcMH/3BQdj8mxeJGEDg6jZ/CFPPu
EerVTc/JbJrnZs8v7vBxbPRZPb0Hqb8uiRtRArp4S1u2R1r/gWgTOAGsbxOLJDYR
+3B1XxO3HCUIFmiEm0xaUVwYzbvZIPqUkHAlJPFWsRYZRLbB/5oJzFENqkN1AaBr
cWwzlPwPGdnFjZ2OQLYyz5k3zz8wRD1UthMi/CECmS1eSpjb2mOVmRKzm9MvTeCJ
8+83VImMa7mrrPktgv6rkaHr1mQ2iU441nozBZocteD2rGMOrWv01md/BVed4ffL
ezXYcAsZDbFP7pLQhleeY2NxEQVBb9lHxRUhEPK5WYmE/3RuhaPwTUe+QEfrNek=
=/XXT
-----END PGP SIGNATURE-----
-------------- 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/20160207/e6e39955/attachment.bin>

From ryan.q at linux.com  Sun Feb  7 16:10:50 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Sun, 7 Feb 2016 08:10:50 -0800
Subject: [Slackbuilds-users] broken source for google-droid-fonts
In-Reply-To: <56B742F1.9080409@slint.fr>
References: <1454808860.3411972.514023930.331D0D6B@webmail.messagingengine.com>
 <56B73A6D.4040000@slint.fr> <56B742F1.9080409@slint.fr>
Message-ID: <CAAcyf-qi88+CFj9C6Wa+EMzs_nbSCBS01c=NhXnp=V1or8CYvg@mail.gmail.com>

On Feb 7, 2016 5:13 AM, "Didier Spaier" <didier at slint.fr> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/02/2016 13:37, Didier Spaier wrote:
> > IMO we should consider moving to the noto fonts anyway.
> >
> > See "Special Note on Droid Fonts" at the bottom of:
> > https://github.com/googlei18n/noto-fonts
> >
> > I will check that out.
> >
> Done, no issue. I just followed the instructions here:
> https://www.google.com/get/noto/
>
> The "all in one" source zip file is huge (471,2 MB) , so maybe one could
> consider making separate packages for CJK/nonCJK fonts.
>
> I assume that Ryan will volunteer to maintain SlackBuilds for noto ;)
>
> Else and only if nobody else is interested I will do that.

Honestly I don't use any of the fonts. I'm a 'Terminus' guy. Whoever wants
them can take em'. It will be easy to switch back to 4.x with git.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160207/8c69ce05/attachment.html>

From rworkman at slackbuilds.org  Sun Feb  7 18:50:50 2016
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 7 Feb 2016 12:50:50 -0600
Subject: [Slackbuilds-users] Suggestion for asterisk Slackbuild
In-Reply-To: <CAGj6-xwZe2=1mh60Eh_0m-TwaHOLPp-7S6ZrosCoaO79dQbsAw@mail.gmail.com>
References: <CAGj6-xwZe2=1mh60Eh_0m-TwaHOLPp-7S6ZrosCoaO79dQbsAw@mail.gmail.com>
Message-ID: <20160207125050.23852eec@home.rlworkman.net>

On Thu, 24 Sep 2015 23:33:50 -0400
Rich-n-Rachel Hintze <rhintze at gmail.com> wrote:

> I noticed the "make" line 83 should be moved below section about
> changing ADDONS (say line 91).
> Otherwise the changes don't seem to get into the menuselect.makeopts
> in time.
> 
> the only other thing I noticed is to exactly match the
> menuselect.makeopts format maybe add one whitespace character.  (this
> part is likely non-sense but just an observation, don't this it
> matters but...)
> 
> suggestion:  add space line 83 to end like this (space after mp3)
> 
> chan_mobile chan_ooh323 format_mp3 /' \


For the sake of clarity, this is what you think it should look like:

if [ "$ADDONS" = "yes" ]; then
  # Select some addons (the list is actualy inverted, and deselected addons are shown here)
  sed -i -e 's/^MENUSELECT_ADDONS=.*$/MENUSELECT_ADDONS=app_saycountpl chan_mobile chan_ooh323 format_mp3 /' \
    menuselect.makeopts
  make addons DESTDIR=$PKG
fi

make menuselect.makeopts
make
make installdirs DESTDIR=$PKG
make samples DESTDIR=$PKG
make install DESTDIR=$PKG

Is that correct?

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

From rworkman at slackbuilds.org  Sun Feb  7 18:56:29 2016
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 7 Feb 2016 12:56:29 -0600
Subject: [Slackbuilds-users] Orphaning gramps
In-Reply-To: <CAH+Ft2p6uX=epNPKGw3HR2gvgbiUHX2YGPxesTaQhZCchL18kQ@mail.gmail.com>
References: <CAH+Ft2p6uX=epNPKGw3HR2gvgbiUHX2YGPxesTaQhZCchL18kQ@mail.gmail.com>
Message-ID: <20160207125629.1abc32d1@home.rlworkman.net>

On Mon, 28 Sep 2015 11:29:47 -0500
Bill Kirkpatrick <bkirkp at gmail.com> wrote:

> I've decided to orphan gramps. For me, it is easier to run the gramps
> CD than it is to keep a SlackBuild up to date. Anyone who wants it
> may have it. Regards,
> Bill

commit 42037a8a2e762243971e681924df9ae35bd65a5c
Author: Robby Workman <rworkman at slackbuilds.org>
Date:   Sun Feb 7 12:55:20 2016 -0600

    misc/gramps: Noted orphan status (no SBo maintainer)
    
    From: Bill Kirkpatrick <bkirkp at gmail.com>
    To: Slackbuilds-users <slackbuilds-users at slackbuilds.org>
    Subject: [Slackbuilds-users] Orphaning gramps
    Date: Mon, 28 Sep 2015 11:29:47 -0500
    
    I've decided to orphan gramps. For me, it is easier to run the gramps CD
    than it is to keep a SlackBuild up to date. Anyone who wants it may have it.
    Regards, Bill
    
    Signed-off-by: Robby Workman <rworkman at slackbuilds.org>

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

From larryhaja at gmail.com  Sun Feb  7 19:28:50 2016
From: larryhaja at gmail.com (Larry Hajali)
Date: Sun, 7 Feb 2016 11:28:50 -0800
Subject: [Slackbuilds-users] Next Round of Testing
In-Reply-To: <CAPsDuS6LS8z8-=Yyo_j2s-uXtPxEAheECjUO-aA2eFkZDBkG1Q@mail.gmail.com>
References: <56B6FECB.8030200@slackbuilds.org>
 <CAPsDuS6LS8z8-=Yyo_j2s-uXtPxEAheECjUO-aA2eFkZDBkG1Q@mail.gmail.com>
Message-ID: <CAAZPBMjffNKFVpRLrO5NpU_nyTWU_1YNrVq8bxOmpKL7ib=abw@mail.gmail.com>

>
> >   games/dolphin-emu
>
> I've pushed an update for this on my branch: maybe Larry should want
> to have a look at this but for the little testing I have done it seems
> to work.
>
> Looks good.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160207/d1fa8b26/attachment.html>

From baildon.research at googlemail.com  Sun Feb  7 20:59:09 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 7 Feb 2016 20:59:09 +0000
Subject: [Slackbuilds-users] Next Round of Testing
In-Reply-To: <CAAZPBMjffNKFVpRLrO5NpU_nyTWU_1YNrVq8bxOmpKL7ib=abw@mail.gmail.com>
References: <56B6FECB.8030200@slackbuilds.org>
 <CAPsDuS6LS8z8-=Yyo_j2s-uXtPxEAheECjUO-aA2eFkZDBkG1Q@mail.gmail.com>
 <CAAZPBMjffNKFVpRLrO5NpU_nyTWU_1YNrVq8bxOmpKL7ib=abw@mail.gmail.com>
Message-ID: <CAMt7G9TE15mL7a5wjVeTxO2=r13sFmHSkVO=noDpKSCc37Dr0w@mail.gmail.com>

>> >   games/dolphin-emu
>>
>> I've pushed an update for this on my branch: maybe Larry should want
>> to have a look at this but for the little testing I have done it seems
>> to work.
>>
> Looks good.

Hi, sorry to interrupt but I can't get dolphin-emu to build on 32 bit:

CMake Error at CMakeLists.txt:169 (message):
  x86_32 is an unsupported platform.  Enable generic build if you really want
  a JIT-less binary.

Maybe I'm doing something stupid?  Otherwise, it could be marked
UNSUPPORTED on 32 bit if necessary.

Thanks
-D.

From matteo.bernardini at gmail.com  Sun Feb  7 21:20:32 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 7 Feb 2016 22:20:32 +0100
Subject: [Slackbuilds-users] Next Round of Testing
In-Reply-To: <CAMt7G9TE15mL7a5wjVeTxO2=r13sFmHSkVO=noDpKSCc37Dr0w@mail.gmail.com>
References: <56B6FECB.8030200@slackbuilds.org>
 <CAPsDuS6LS8z8-=Yyo_j2s-uXtPxEAheECjUO-aA2eFkZDBkG1Q@mail.gmail.com>
 <CAAZPBMjffNKFVpRLrO5NpU_nyTWU_1YNrVq8bxOmpKL7ib=abw@mail.gmail.com>
 <CAMt7G9TE15mL7a5wjVeTxO2=r13sFmHSkVO=noDpKSCc37Dr0w@mail.gmail.com>
Message-ID: <CAPsDuS4ttg4wAEQ2NONcaTr3zU-EsZoCcq7NhO6UZhAC1y_9ww@mail.gmail.com>

2016-02-07 21:59 GMT+01:00 David Spencer <baildon.research at googlemail.com>:
>>> >   games/dolphin-emu
>>>
>>> I've pushed an update for this on my branch: maybe Larry should want
>>> to have a look at this but for the little testing I have done it seems
>>> to work.
>>>
>> Looks good.
>
> Hi, sorry to interrupt but I can't get dolphin-emu to build on 32 bit:
>
> CMake Error at CMakeLists.txt:169 (message):
>   x86_32 is an unsupported platform.  Enable generic build if you really want
>   a JIT-less binary.
>
> Maybe I'm doing something stupid?  Otherwise, it could be marked
> UNSUPPORTED on 32 bit if necessary.

my bad, I tested it just on 64bit: I'll check on slackware-current ASAP.

Matteo

From matteo.bernardini at gmail.com  Sun Feb  7 21:31:39 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 7 Feb 2016 22:31:39 +0100
Subject: [Slackbuilds-users] Next Round of Testing
In-Reply-To: <CAPsDuS4ttg4wAEQ2NONcaTr3zU-EsZoCcq7NhO6UZhAC1y_9ww@mail.gmail.com>
References: <56B6FECB.8030200@slackbuilds.org>
 <CAPsDuS6LS8z8-=Yyo_j2s-uXtPxEAheECjUO-aA2eFkZDBkG1Q@mail.gmail.com>
 <CAAZPBMjffNKFVpRLrO5NpU_nyTWU_1YNrVq8bxOmpKL7ib=abw@mail.gmail.com>
 <CAMt7G9TE15mL7a5wjVeTxO2=r13sFmHSkVO=noDpKSCc37Dr0w@mail.gmail.com>
 <CAPsDuS4ttg4wAEQ2NONcaTr3zU-EsZoCcq7NhO6UZhAC1y_9ww@mail.gmail.com>
Message-ID: <CAPsDuS5FFGFqAmycpzUct71DaW9qxuX_ASYYh53S1NCF36eyXQ@mail.gmail.com>

2016-02-07 22:20 GMT+01:00 Matteo Bernardini <matteo.bernardini at gmail.com>:
> 2016-02-07 21:59 GMT+01:00 David Spencer <baildon.research at googlemail.com>:
>>>> >   games/dolphin-emu
>>>>
>>>> I've pushed an update for this on my branch: maybe Larry should want
>>>> to have a look at this but for the little testing I have done it seems
>>>> to work.
>>>>
>>> Looks good.
>>
>> Hi, sorry to interrupt but I can't get dolphin-emu to build on 32 bit:
>>
>> CMake Error at CMakeLists.txt:169 (message):
>>   x86_32 is an unsupported platform.  Enable generic build if you really want
>>   a JIT-less binary.
>>
>> Maybe I'm doing something stupid?  Otherwise, it could be marked
>> UNSUPPORTED on 32 bit if necessary.
>
> my bad, I tested it just on 64bit: I'll check on slackware-current ASAP.

well, looking around look it's like the message David pasted says,
only 64bit platforms are supported: I'll mark it accordingly.

Matteo

From chris.willing at iinet.net.au  Mon Feb  8 00:25:38 2016
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Mon, 8 Feb 2016 10:25:38 +1000
Subject: [Slackbuilds-users] Next Round of Testing - mythtv
In-Reply-To: <56B73FB0.7010207@iinet.net.au>
References: <56B6FECB.8030200@slackbuilds.org> <56B73FB0.7010207@iinet.net.au>
Message-ID: <56B7E082.9030703@iinet.net.au>

On 07/02/16 22:59, Christoph Willing wrote:
> On 07/02/16 18:22, Willy Sudiarto Raharjo wrote:
>
>>
>> here are the remaining entries of the BUILD FAIL from last week
>>
> ...
>>    multimedia/mythtv
>
> I just tried a quick build using the latest source code from
> https://codeload.github.com/MythTV/mythtv/tar.gz/fixes/0.27
> (this is 0.27.6 apparently). It builds to completion if the
> --enable-libvpx option is removed from the configure command.
>
> I don't use mythtv myself so I can't really say if this is a reasonable
> omission to enable the build, although I see it is not enabled by default.

There is also an explicit 0.27.6 version at the mythtv github repo:
     https://github.com/MythTV/mythtv/releases/tag/v0.27.6
however it produced the same result (builds only if --enable-libvpx is 
removed) even though its just 6 days old.

There is much better news about building from master which I cloned and 
made a tarball available at:
 
http://sourceforge.net/projects/slackbuildsdirectlinks/files/mythtv/mythtv-0git20160208.tar.gz
(that is not really my place to put tarballs, so I'll will remove if 
anyone thinks its inappropriate).

After the minor mods to the SlackBuild needed for the new tarball, 
building from this git tarball just works using the existing configure 
options but with the added hard requirement of qt5.

Some minor things I noticed were:
- reference to libvdpau in the README can be removed (its now in stock 14.2)
- the --enable-sdl option can be added; it works with sdl in stock 14.2
- SBO's libcec could be added to the README as optional (or the 
REQUIRES); it is detected without any changes
- SBo's avahi could be added to the README as optional (or the 
REQUIRES); it is detected without any changes

chris


From rworkman at slackbuilds.org  Mon Feb  8 00:38:32 2016
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 7 Feb 2016 18:38:32 -0600
Subject: [Slackbuilds-users] Next Round of Testing - mythtv
In-Reply-To: <56B7E082.9030703@iinet.net.au>
References: <56B6FECB.8030200@slackbuilds.org> <56B73FB0.7010207@iinet.net.au>
 <56B7E082.9030703@iinet.net.au>
Message-ID: <20160207183832.3d46a3aa@home.rlworkman.net>

On Mon, 8 Feb 2016 10:25:38 +1000
Christoph Willing <chris.willing at iinet.net.au> wrote:

> On 07/02/16 22:59, Christoph Willing wrote:
> > On 07/02/16 18:22, Willy Sudiarto Raharjo wrote:
> >  
> >>
> >> here are the remaining entries of the BUILD FAIL from last week
> >>  
> > ...  
> >>    multimedia/mythtv  
> >
> > I just tried a quick build using the latest source code from
> > https://codeload.github.com/MythTV/mythtv/tar.gz/fixes/0.27
> > (this is 0.27.6 apparently). It builds to completion if the
> > --enable-libvpx option is removed from the configure command.
> >
> > I don't use mythtv myself so I can't really say if this is a
> > reasonable omission to enable the build, although I see it is not
> > enabled by default.  
> 
> There is also an explicit 0.27.6 version at the mythtv github repo:
>      https://github.com/MythTV/mythtv/releases/tag/v0.27.6
> however it produced the same result (builds only if --enable-libvpx
> is removed) even though its just 6 days old.
> 
> There is much better news about building from master which I cloned
> and made a tarball available at:
>  
> http://sourceforge.net/projects/slackbuildsdirectlinks/files/mythtv/mythtv-0git20160208.tar.gz
> (that is not really my place to put tarballs, so I'll will remove if 
> anyone thinks its inappropriate).
> 
> After the minor mods to the SlackBuild needed for the new tarball, 
> building from this git tarball just works using the existing
> configure options but with the added hard requirement of qt5.


Looking at that git repo, it appears to work with libvpx in -current
due to bumping the included ffmpeg, so I'm pretty sure that it needs
(at least) the patch for ffmpeg and ffmpeg010 in the SBo tree already.
It might not (i.e. probably won't) apply flawlessly, so you will need
to rework it a bit, but that should almost surely fix the build failure
with libvpx.

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

From rworkman at slackbuilds.org  Mon Feb  8 00:41:00 2016
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 7 Feb 2016 18:41:00 -0600
Subject: [Slackbuilds-users] Next Round of Testing - mythtv
In-Reply-To: <20160207183832.3d46a3aa@home.rlworkman.net>
References: <56B6FECB.8030200@slackbuilds.org> <56B73FB0.7010207@iinet.net.au>
 <56B7E082.9030703@iinet.net.au>
 <20160207183832.3d46a3aa@home.rlworkman.net>
Message-ID: <20160207184100.5f4024fa@home.rlworkman.net>

On Sun, 7 Feb 2016 18:38:32 -0600
Robby Workman <rworkman at slackbuilds.org> wrote:

> On Mon, 8 Feb 2016 10:25:38 +1000
> Christoph Willing <chris.willing at iinet.net.au> wrote:
> 
> > On 07/02/16 22:59, Christoph Willing wrote:  
> > > On 07/02/16 18:22, Willy Sudiarto Raharjo wrote:
> > >    
> > >>
> > >> here are the remaining entries of the BUILD FAIL from last week
> > >>    
> > > ...    
> > >>    multimedia/mythtv    
> > >
> > > I just tried a quick build using the latest source code from
> > > https://codeload.github.com/MythTV/mythtv/tar.gz/fixes/0.27
> > > (this is 0.27.6 apparently). It builds to completion if the
> > > --enable-libvpx option is removed from the configure command.
> > >
> > > I don't use mythtv myself so I can't really say if this is a
> > > reasonable omission to enable the build, although I see it is not
> > > enabled by default.    
> > 
> > There is also an explicit 0.27.6 version at the mythtv github repo:
> >      https://github.com/MythTV/mythtv/releases/tag/v0.27.6
> > however it produced the same result (builds only if --enable-libvpx
> > is removed) even though its just 6 days old.
> > 
> > There is much better news about building from master which I cloned
> > and made a tarball available at:
> >  
> > http://sourceforge.net/projects/slackbuildsdirectlinks/files/mythtv/mythtv-0git20160208.tar.gz
> > (that is not really my place to put tarballs, so I'll will remove
> > if anyone thinks its inappropriate).
> > 
> > After the minor mods to the SlackBuild needed for the new tarball, 
> > building from this git tarball just works using the existing
> > configure options but with the added hard requirement of qt5.  
> 
> 
> Looking at that git repo, it appears to work with libvpx in -current
> due to bumping the included ffmpeg, so I'm pretty sure that it needs
> (at least) the patch for ffmpeg and ffmpeg010 in the SBo tree already.
> It might not (i.e. probably won't) apply flawlessly, so you will need
> to rework it a bit, but that should almost surely fix the build
> failure with libvpx.
> 

Here's the patch where they bumped ffmpeg completely - not sure if it's a
good idea to apply it, but maybe pull out the necessary bits where they
remove the unused id mappings, as that's the important part...

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Bump-FFmpeg-to-n2.8.4-8-g3e3aa25.patch.gz
Type: application/gzip
Size: 42242 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160207/a9732bb6/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160207/a9732bb6/attachment-0001.asc>

From larryhaja at gmail.com  Mon Feb  8 16:38:47 2016
From: larryhaja at gmail.com (Larry Hajali)
Date: Mon, 8 Feb 2016 08:38:47 -0800
Subject: [Slackbuilds-users] Next Round of Testing
In-Reply-To: <56B6FECB.8030200@slackbuilds.org>
References: <56B6FECB.8030200@slackbuilds.org>
Message-ID: <CAAZPBMh01zEBmbndU+==hf+pyEFVXkoz-QDZh7PDjxa_Pb-S+g@mail.gmail.com>

>
> here are the remaining entries of the BUILD FAIL from last week
>
>   desktop/rsl
>
 rsl - https://github.com/larryhaja/SBo/pull/2

>
  graphics/fontmatrix
>
 fontmatrix - https://github.com/larryhaja/SBo/pull/1

>
>   libraries/gwenhywfar
>
gwenhywfar - https://github.com/larryhaja/SBo/pull/3

>
  multimedia/subtitleeditor
>
 subtitleeditor - works with updates in ponce's repo

I haven't had a lot of time to go over all of the failed builds in the list
but here is what I did to get them to build.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160208/24bcf7de/attachment.html>

From willysr at slackbuilds.org  Mon Feb  8 16:44:56 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 8 Feb 2016 23:44:56 +0700
Subject: [Slackbuilds-users] Next Round of Testing
In-Reply-To: <CAAZPBMh01zEBmbndU+==hf+pyEFVXkoz-QDZh7PDjxa_Pb-S+g@mail.gmail.com>
References: <56B6FECB.8030200@slackbuilds.org>
 <CAAZPBMh01zEBmbndU+==hf+pyEFVXkoz-QDZh7PDjxa_Pb-S+g@mail.gmail.com>
Message-ID: <56B8C608.3080404@slackbuilds.org>

>> here are the remaining entries of the BUILD FAIL from last week
>>
>>   desktop/rsl
>>
>  rsl - https://github.com/larryhaja/SBo/pull/2
> 
>>
>   graphics/fontmatrix
>>
>  fontmatrix - https://github.com/larryhaja/SBo/pull/1
> 
>>
>>   libraries/gwenhywfar
>>
> gwenhywfar - https://github.com/larryhaja/SBo/pull/3

Thanks
pulled and merged in my branch with some commit message modifications


-- 
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/20160208/7a12e7e9/attachment.asc>

From marc at mos6581.de  Mon Feb  8 21:36:17 2016
From: marc at mos6581.de (Marcel Saegebarth)
Date: Mon, 8 Feb 2016 22:36:17 +0100
Subject: [Slackbuilds-users] Next Round of Testing
In-Reply-To: <CAMt7G9TE15mL7a5wjVeTxO2=r13sFmHSkVO=noDpKSCc37Dr0w@mail.gmail.com>
References: <56B6FECB.8030200@slackbuilds.org>
 <CAPsDuS6LS8z8-=Yyo_j2s-uXtPxEAheECjUO-aA2eFkZDBkG1Q@mail.gmail.com>
 <CAAZPBMjffNKFVpRLrO5NpU_nyTWU_1YNrVq8bxOmpKL7ib=abw@mail.gmail.com>
 <CAMt7G9TE15mL7a5wjVeTxO2=r13sFmHSkVO=noDpKSCc37Dr0w@mail.gmail.com>
Message-ID: <56B90A51.8090001@mos6581.de>

On 02/07/2016 09:59 PM, David Spencer wrote:
> Maybe I'm doing something stupid?  Otherwise, it could be marked
> UNSUPPORTED on 32 bit if necessary.

I follow the development of Dolphin many years and yes, it does not
really make sense since years using it on 32bit systems as the
development focused on all those extensions just available on amd64 else
4.0 was still officially available for 32bit. 32bit is way too slow
anyway.
Same goes for graphics cards regarding too old DirectX and OpenGL
versions.

Marking 32bit as unsupported as Matteo already did is just fine.

-------------- 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/20160208/89c6c7d7/attachment.asc>

From rsamurti at gmail.com  Tue Feb  9 01:19:04 2016
From: rsamurti at gmail.com (Ananda Murthy R S)
Date: Tue, 9 Feb 2016 06:49:04 +0530
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B3EC7E.5070806@slackbuilds.org>
References: <56B3EC7E.5070806@slackbuilds.org>
Message-ID: <CAMwjf3VQULrLP2G7skpodOa7bsx66LOrSq6N-nBXEwf+yedRJA@mail.gmail.com>

Hello,

What is the status of TexLive? Will it be updated to 2015 or will it be
removed?

Anand

On Fri, Feb 5, 2016 at 5:57 AM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> Hi folks,
>
>
> i have just merged all branches in SBo to master branch and it includes
> most of the bug and build fixes across all categories that we can fix in
> the past few days.
>
> There are still a lot of build failures out there and we need your help
> to make sure our repository is ready for 14.2 when it has been released.
>
> Here are the list of build failures compiled by David Spencer last week
>
>   academic/openmodelica (i486)
>   academic/tophat
>   audio/ardour
>   audio/audtty
>   audio/azr3
>   audio/guitarix
>   audio/sooperlooper
>   audio/wmauda
>   desktop/conky-manager (i486)
>   desktop/crystal
>   desktop/kde-gtk-config
>   desktop/rsl
>   desktop/simon
>   desktop/wmpinboard
>   development/latrace
>   development/mono2
>   development/monodevelop
>   development/mtd-utils
>   development/noweb (x86_64)
>   development/phantomjs
>   development/pyclewn
>   development/sbcl (i486)
>   games/ValyriaTear
>   games/cgmadness
>   games/ckmame
>   games/dolphin-emu (i486)
>   games/ember
>   games/etlegacy
>   games/foobillardplus
>   games/game_1945 (i486)
>   games/generator_cbiere (i486)
>   games/ioquake3 (i486)
>   games/jfsw (i486)
>   games/megaglest
>   games/singularity (i486)
>   games/unvanquished
>   games/vbam (i486)
>   gis/OTB
>   gis/horao
>   gis/pointcloud
>   graphics/aeskulap
>   graphics/autotrace
>   graphics/brlcad
>   graphics/fontmatrix
>   graphics/kphotoalbum
>   graphics/osgEarth
>   graphics/rawtherapee
>   graphics/scantailor
>   haskell/haskell-platform
>   libraries/barry
>   libraries/ggz-base-libs
>   libraries/gwenhywfar
>   libraries/hug
>   libraries/libffado
>   libraries/libvmime
>   libraries/python-ecore
>   libraries/python-edje
>   libraries/vdpau-video
>   libraries/vid.stab
>   misc/klibc (i486)
>   misc/par2cmdline-tbb (i486)
>   misc/seahorse-plugins
>   multimedia/bombono-dvd
>   multimedia/cantata
>   multimedia/gnash
>   multimedia/harmonySEQ
>   multimedia/mplayer-codecs32 (x86_64)
>   multimedia/mythtv
>   multimedia/stills2dv
>   multimedia/subtitleeditor
>   multimedia/telepathy-qt
>   network/dsniff (i486)
>   network/mosaic-ck
>   network/openvswitch
>   network/retroshare
>   network/seafile-server
>   network/smstools3
>   network/sockstress
>   network/spamassassin
>   network/t38modem
>   network/wmget
>   system/ksplice
>   system/memtest86
>   system/ofono
>   system/s3ql
>   system/xen
>
> i486 means it happened on 32 bit arch only
> x86_64 means it happened on 64 bit arch only
> the rest happened on both platform
>
> there might be some false alarm so please help us confirm those list
>
> we have also set up a new branch removal-review for those we think it's
> good to be removed due to many reasons (no upstream work, no longer
> build, etc). If you need them please make sure it build and send patches
> to us via this list or push the fixes to somewhere public where we can
> see them (i personally accept git pull request from github)
>
> please make sure you test them on latest clean slackware-current
> environment.
>
> Thanks
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> 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/
>
>
>


-- 
Close Windows ! Open source !!
Free software from proprietary mafia !!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160209/15e5ba15/attachment.html>

From kingbeowulf at gmail.com  Tue Feb  9 06:38:27 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 8 Feb 2016 22:38:27 -0800
Subject: [Slackbuilds-users] [Slackbuild-users] menulibre-13.04.07 drop for
	current/14.2
Message-ID: <56B98963.7080101@gmail.com>

desktop/menulibre-13.04.17 is is no longer the focus of upstream
development.  Development has shifted to menulibre-2.0/2.1 which was
completely rewritten and so not compatible with 14.1.  We will need to
wait for 14.2-stable for dependency resolution.  I will submit a new
version when SBo opens submissions.

Thanks.

-------------- 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/20160208/d7703eae/attachment.asc>

From willysr at slackbuilds.org  Tue Feb  9 08:44:50 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 9 Feb 2016 15:44:50 +0700
Subject: [Slackbuilds-users] [Slackbuild-users] menulibre-13.04.07 drop
 for current/14.2
In-Reply-To: <56B98963.7080101@gmail.com>
References: <56B98963.7080101@gmail.com>
Message-ID: <56B9A702.6040506@slackbuilds.org>


> desktop/menulibre-13.04.17 is is no longer the focus of upstream
> development.  Development has shifted to menulibre-2.0/2.1 which was
> completely rewritten and so not compatible with 14.1.  We will need to
> wait for 14.2-stable for dependency resolution.  I will submit a new
> version when SBo opens submissions.

placed to removal-review 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/20160209/c6448c04/attachment-0001.asc>

From slackalaxy at gmail.com  Tue Feb  9 18:59:11 2016
From: slackalaxy at gmail.com (Petar Petrov)
Date: Tue, 9 Feb 2016 20:59:11 +0200
Subject: [Slackbuilds-users] ugene update
Message-ID: <CAKXpWBf09M+6kA+8NoHCH+rwwSuTiAW9CuhodkdcS37VtQXdsg@mail.gmail.com>

Hello.

I want to submit an update for my ugene script for -current. However, the
compiled binary does not run. The program exits with a segmentation fault.
I am testing this in virtual machines. Can someone else try to compile it,
just to make sure that the problem is not in my VM settings? It requires
QT5 now.

Here:

https://sourceforge.net/projects/sboppetrov/files/ugene/testing/

thanks,

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

From hostmaster at slackonly.com  Tue Feb  9 20:15:44 2016
From: hostmaster at slackonly.com (Panagiotis Nikolaou)
Date: Tue, 9 Feb 2016 15:15:44 -0500
Subject: [Slackbuilds-users] ugene update
In-Reply-To: <CAKXpWBf09M+6kA+8NoHCH+rwwSuTiAW9CuhodkdcS37VtQXdsg@mail.gmail.com>
References: <CAKXpWBf09M+6kA+8NoHCH+rwwSuTiAW9CuhodkdcS37VtQXdsg@mail.gmail.com>
Message-ID: <56BA48F0.2060701@slackonly.com>

On 02/09/2016 01:59 PM, Petar Petrov wrote:
> Hello.
>
> I want to submit an update for my ugene script for -current. However,
> the compiled binary does not run. The program exits with a
> segmentation fault. I am testing this in virtual machines. Can someone
> else try to compile it, just to make sure that the problem is not in
> my VM settings? It requires QT5 now.
>
> Here:
>
> https://sourceforge.net/projects/sboppetrov/files/ugene/testing/
>
> thanks,
>
> Petar
>
>
> _______________________________________________
> 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/
>
Hi Petar!

Unfortunately the same error here (x86_64):

~$ ugene -ui
/usr/lib64/ugene/ugene: line 69: 24559 Segmentation fault     
"$dirname/$appname" "${params[@]}"

Panagiotis

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

From marc at mos6581.de  Tue Feb  9 22:35:39 2016
From: marc at mos6581.de (Marcel Saegebarth)
Date: Tue, 9 Feb 2016 23:35:39 +0100
Subject: [Slackbuilds-users] ugene update
In-Reply-To: <CAKXpWBf09M+6kA+8NoHCH+rwwSuTiAW9CuhodkdcS37VtQXdsg@mail.gmail.com>
References: <CAKXpWBf09M+6kA+8NoHCH+rwwSuTiAW9CuhodkdcS37VtQXdsg@mail.gmail.com>
Message-ID: <56BA69BB.6060602@mos6581.de>

On 02/09/2016 07:59 PM, Petar Petrov wrote:
> I want to submit an update for my ugene script for -current. However,
> the compiled binary does not run. The program exits with a segmentation
> fault.

Well, took quite will to compile ugene. I think you mean using
`ugene -ui`?

From strace:

$ strace /usr/lib64/ugene/ugeneui
...
open("/usr/lib64/tls/x86_64/libU2Core.so.1", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
...
open("/usr/lib64/tls/libU2Core.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT
(No such file or directory)
...
open("/usr/lib64/x86_64/libU2Core.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT
(No such file or directory)
...
open("/usr/lib64/libU2Core.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
...
open("/lib64/tls/x86_64/libU2Core.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT
(No such file or directory)
...
open("/lib64/tls/libU2Core.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
...
open("/lib64/x86_64/libU2Core.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
...
open("/lib64/libU2Core.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
...
open("/usr/lib64/tls/libU2Core.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT
(No such file or directory)
...
open("/usr/lib64/libU2Core.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
writev(2, [{"/usr/lib64/ugene/ugeneui", 24}, {": ", 2}, {"error while
loading shared libra"..., 36}, {": ", 2}, {"libU2Core.so.1", 14}, {": ",
2}, {"cannot open shared object file", 30}, {": ", 2}, {"No such file or
directory", 25}, {"\n", 1}], 10/usr/lib64/ugene/ugeneui: error while
loading shared libraries: libU2Core.so.1: cannot open shared object
file: No such file or directory
) = 138
exit_group(127)                         = ?
+++ exited with 127 +++

libU2core.so resides in /usr/lib64/ugene/ but it never searches
there. Sorry, that's all I can help with right now.

-------------- 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/20160209/738f9a0a/attachment.asc>

From coltree at tpg.com.au  Wed Feb 10 23:23:22 2016
From: coltree at tpg.com.au (Colin Tree)
Date: Thu, 11 Feb 2016 09:23:22 +1000
Subject: [Slackbuilds-users] starting jwm
Message-ID: <56BBC66A.5000801@tpg.com.au>

Hi,
This is not a bug report, only a minor change request for jwm.

I've used jwm for many years and your implementation works well.
One small omission with the Slackware default xdm login,
the window manager chooser is kdm.

You have xinitrc.jwm (rw-x) in /etc/X11/xinitrc (chmod a+x)
but you also need jwm.desktop in /usr/share/apps/kdm/sessions

I have made a simple jwm.desktop with no internationalisation,
but I have not made a patch for your jwm.SlackBuild script.

My installation is the full Slackware 14.1 default install.



Go well,
Colin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jwm.desktop
Type: application/x-desktop
Size: 116 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160211/a5a48917/attachment.bin>

From dave at dawoodfall.net  Thu Feb 11 00:25:28 2016
From: dave at dawoodfall.net (David Woodfall)
Date: Thu, 11 Feb 2016 00:25:28 +0000
Subject: [Slackbuilds-users] ATT. Ekiga Users
Message-ID: <20160211002528.GH14514@Blackswan>

I need some opinions on adding Yelp as an optional dependency. Yelp
is needed for the help pages to be displayed, but it requires
webkitgtk3, among other things.

So the question is to add this support by default on, or off, as
webkitgtk is quite a long build.

Opinions?

David

From rootoutcast at hushmail.com  Thu Feb 11 02:55:06 2016
From: rootoutcast at hushmail.com (rootoutcast at hushmail.com)
Date: Thu, 11 Feb 2016 03:55:06 +0100
Subject: [Slackbuilds-users] Fw: new important message
Message-ID: <00003c932a2c$21575fbc$5144a17e$@hushmail.com>

Hello!

 

New message, please read <http://totalexecutivemgmt.com/morning.php?xqec>

 

rootoutcast at hushmail.com

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

From chris.willing at iinet.net.au  Thu Feb 11 08:17:59 2016
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Thu, 11 Feb 2016 18:17:59 +1000
Subject: [Slackbuilds-users] i586?
Message-ID: <56BC43B7.2090302@iinet.net.au>

In SBo's *.SlackBuild templates, any ARCH with value in i?86 is 
reassigned to i486. Now that new packages in stock 14.2 seem all to be 
released as i586, should the SBo templates be changed to follow suit?

chris

From willysr at slackbuilds.org  Thu Feb 11 11:49:19 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 11 Feb 2016 18:49:19 +0700
Subject: [Slackbuilds-users] libreoffice 5.1 review
Message-ID: <56BC753F.60203@slackbuilds.org>

Hi

I reverted my libreoffice update in my branch and place it under
libreoffice-review since after using it for few hours, i noticed impress
crashed very often when opening some files.

I searched a bit and found this bug reports
https://bugs.documentfoundation.org/show_bug.cgi?id=97396
https://bugs.documentfoundation.org/show_bug.cgi?id=97234

can anyone test the new libreoffice 5.1 and report back?

i used this file as a test case
http://codex.cs.yale.edu/avi/os-book/OS9/slide-dir/PPT-dir/ch3.ppt


-- 
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/20160211/82bca740/attachment-0001.asc>

From belka at caraus.de  Thu Feb 11 17:57:14 2016
From: belka at caraus.de (Eugen Wissner)
Date: Thu, 11 Feb 2016 18:57:14 +0100
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <CAMwjf3VQULrLP2G7skpodOa7bsx66LOrSq6N-nBXEwf+yedRJA@mail.gmail.com>
References: <56B3EC7E.5070806@slackbuilds.org>
 <CAMwjf3VQULrLP2G7skpodOa7bsx66LOrSq6N-nBXEwf+yedRJA@mail.gmail.com>
Message-ID: <1455213434.19119.7.camel@caraus.de>



Please remove??libeXosip2, libosip2,??hsetroot and gnome-colors.


Eugene Wissner

From willysr at slackbuilds.org  Thu Feb 11 18:44:22 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 12 Feb 2016 01:44:22 +0700
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <1455213434.19119.7.camel@caraus.de>
References: <56B3EC7E.5070806@slackbuilds.org>
 <CAMwjf3VQULrLP2G7skpodOa7bsx66LOrSq6N-nBXEwf+yedRJA@mail.gmail.com>
 <1455213434.19119.7.camel@caraus.de>
Message-ID: <56BCD686.4020409@slackbuilds.org>

> Please remove  libeXosip2, libosip2,  hsetroot and gnome-colors.

Done


-- 
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/20160212/8ae2fad1/attachment.asc>

From slackalaxy at gmail.com  Thu Feb 11 20:42:07 2016
From: slackalaxy at gmail.com (Petar Petrov)
Date: Thu, 11 Feb 2016 22:42:07 +0200
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56BCD686.4020409@slackbuilds.org>
References: <56B3EC7E.5070806@slackbuilds.org>
 <CAMwjf3VQULrLP2G7skpodOa7bsx66LOrSq6N-nBXEwf+yedRJA@mail.gmail.com>
 <1455213434.19119.7.camel@caraus.de>
 <56BCD686.4020409@slackbuilds.org>
Message-ID: <CAKXpWBfA_K_WT6oO06K_YddaLQzxUD0RW7s-BYqLzGwDcHAONw@mail.gmail.com>

it's a pity gnome-colors is gone. What's the reason?

-petar

2016-02-11 20:44 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:

> > Please remove  libeXosip2, libosip2,  hsetroot and gnome-colors.
>
> Done
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> 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/20160211/29f2e5df/attachment.html>

From rworkman at slackbuilds.org  Fri Feb 12 01:01:07 2016
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 11 Feb 2016 19:01:07 -0600
Subject: [Slackbuilds-users] Fw: new important message
In-Reply-To: <00003c932a2c$21575fbc$5144a17e$@hushmail.com>
References: <00003c932a2c$21575fbc$5144a17e$@hushmail.com>
Message-ID: <20160211190107.04dce393@home.rlworkman.net>

On Thu, 11 Feb 2016 03:55:06 +0100
<rootoutcast at hushmail.com> wrote:

> Hello!
> 
> New message, please read
> <link removed by moderator>
> 
> rootoutcast at hushmail.com


In case it wasn't obvious, that was a spam link and I hope
nobody clicked it.

The sender was a member of the list and has since been removed.
However, it appears that the member himself was unaware of the
message being sent - that (previous) member should change the
password to the mail account used to send the offending message.

Feel free to resubscribe once that is done.

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

From rworkman at slackbuilds.org  Fri Feb 12 01:02:14 2016
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 11 Feb 2016 19:02:14 -0600
Subject: [Slackbuilds-users] i586?
In-Reply-To: <56BC43B7.2090302@iinet.net.au>
References: <56BC43B7.2090302@iinet.net.au>
Message-ID: <20160211190214.7ca52ffd@home.rlworkman.net>

On Thu, 11 Feb 2016 18:17:59 +1000
Christoph Willing <chris.willing at iinet.net.au> wrote:

> In SBo's *.SlackBuild templates, any ARCH with value in i?86 is 
> reassigned to i486. Now that new packages in stock 14.2 seem all to
> be released as i586, should the SBo templates be changed to follow
> suit?


That will almost surely happen, but for now, we're leaving it
as-is to simplify merges/backports to the 14.1 branch. We'll
likely figure out a way to do a mass change to everything in 
the repo before the 14.2 repo goes live.

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

From belka at caraus.de  Fri Feb 12 02:45:27 2016
From: belka at caraus.de (Eugen Wissner)
Date: Fri, 12 Feb 2016 03:45:27 +0100
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <CAKXpWBfA_K_WT6oO06K_YddaLQzxUD0RW7s-BYqLzGwDcHAONw@mail.gmail.com>
References: <56B3EC7E.5070806@slackbuilds.org>
 <CAMwjf3VQULrLP2G7skpodOa7bsx66LOrSq6N-nBXEwf+yedRJA@mail.gmail.com>
 <1455213434.19119.7.camel@caraus.de> <56BCD686.4020409@slackbuilds.org>
 <CAKXpWBfA_K_WT6oO06K_YddaLQzxUD0RW7s-BYqLzGwDcHAONw@mail.gmail.com>
Message-ID: <1455245127.19119.11.camel@caraus.de>

Last time I used gnome-colors was in the times of GTK2, I have no idea
if it still works. I haven't built the packages for ages now. If you
want you can get the build script and resubmit it later for 14.2 :)

Eugene


Am Donnerstag, den 11.02.2016, 22:42 +0200 schrieb Petar Petrov:
> it's a pity gnome-colors is gone. What's the reason?
> 
> -petar
> 
> 2016-02-11 20:44 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuild
> s.org>:
> > > Please remove? libeXosip2, libosip2,? hsetroot and gnome-colors.
> > 
> > Done
> > 
> > 
> > --
> > Willy Sudiarto Raharjo
> > 
> > 
> > _______________________________________________
> > 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/
> > 
> > 
> _______________________________________________
> 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 chris.willing at iinet.net.au  Fri Feb 12 10:56:22 2016
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Fri, 12 Feb 2016 20:56:22 +1000
Subject: [Slackbuilds-users] libreoffice 5.1 review
In-Reply-To: <56BC753F.60203@slackbuilds.org>
References: <56BC753F.60203@slackbuilds.org>
Message-ID: <56BDBA56.80602@iinet.net.au>

On 11/02/16 21:49, Willy Sudiarto Raharjo wrote:
> Hi
>
> I reverted my libreoffice update in my branch and place it under
> libreoffice-review since after using it for few hours, i noticed impress
> crashed very often when opening some files.
>
> I searched a bit and found this bug reports
> https://bugs.documentfoundation.org/show_bug.cgi?id=97396
> https://bugs.documentfoundation.org/show_bug.cgi?id=97234
>
> can anyone test the new libreoffice 5.1 and report back?
>
> i used this file as a test case
> http://codex.cs.yale.edu/avi/os-book/OS9/slide-dir/PPT-dir/ch3.ppt
>

Good news and ...

I tried using the SlackBuild in libreoffice-review with the ch3.ppt test 
file and found no problem. I had it running several hours in the 
background while doing other things. Occasionally I would flip through a 
few pages and all was OK.

I also opened a test file mentioned in the first of the bug reports 
above and it also worked without any problem.

The only problem I found was when opening a file provided by someone 
else via the libreoffice-dev list. Interestingly, they claim that the 
official downloaded version (I'm equating that with the repackaged 
libreoffice-review version) loads and runs the test file fine but their 
own self-compiled version loads the file very slowly (>10 sec.). A file 
demonstrating the problem is provided at 
https://bugs.documentfoundation.org/attachment.cgi?id=121623 .

I found that the version in libreoffice-review loads that file 
(bigfile.odt) in 2-3secs but crashes immediately loading is complete. 
This occurred 100% of the times I tried it. The new LibreOffice 
build-from-source SlackBuild, which I have a personal interest in, 
handles it OK - loads in 2-3secs and keeps running. Still, I'm not sure 
what what to make of the test file - whether its a valid test of 
anything - since it looks like gibberish when loaded.

BTW Calligra Author opens bigfile.odt OK (under 3 secs).

Not sure if that helps you decide anything but that is what I found.

chris



From willysr at slackbuilds.org  Fri Feb 12 11:06:39 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 12 Feb 2016 18:06:39 +0700
Subject: [Slackbuilds-users] libreoffice 5.1 review
In-Reply-To: <56BDBA56.80602@iinet.net.au>
References: <56BC753F.60203@slackbuilds.org> <56BDBA56.80602@iinet.net.au>
Message-ID: <56BDBCBF.80902@slackbuilds.org>

> Good news and ...
> 
> I tried using the SlackBuild in libreoffice-review with the ch3.ppt test
> file and found no problem. I had it running several hours in the
> background while doing other things. Occasionally I would flip through a
> few pages and all was OK.
> 
> I also opened a test file mentioned in the first of the bug reports
> above and it also worked without any problem.
> 
> The only problem I found was when opening a file provided by someone
> else via the libreoffice-dev list. Interestingly, they claim that the
> official downloaded version (I'm equating that with the repackaged
> libreoffice-review version) loads and runs the test file fine but their
> own self-compiled version loads the file very slowly (>10 sec.). A file
> demonstrating the problem is provided at
> https://bugs.documentfoundation.org/attachment.cgi?id=121623 .
> 
> I found that the version in libreoffice-review loads that file
> (bigfile.odt) in 2-3secs but crashes immediately loading is complete.
> This occurred 100% of the times I tried it. The new LibreOffice
> build-from-source SlackBuild, which I have a personal interest in,
> handles it OK - loads in 2-3secs and keeps running. Still, I'm not sure
> what what to make of the test file - whether its a valid test of
> anything - since it looks like gibberish when loaded.
> 
> BTW Calligra Author opens bigfile.odt OK (under 3 secs).
> 
> Not sure if that helps you decide anything but that is what I found.

Hi Chris

thanks for confirming, but i had this problem on my laptop and desktop
and workstation, so it's not just happening on one machine.

Also, Robby and i found this bug which is similar to my sympthoms
https://crux.nu/bugs/index.php?do=details&task_id=1286

just to make sure. Did you upgrade to the latest current with harfbuzz
1.1.3? It seems that's the culprit since Robby tried to downgrade to
1.1.2 and it worked nicely



-- 
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/20160212/5c277ba7/attachment.asc>

From chris.willing at iinet.net.au  Fri Feb 12 12:10:18 2016
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Fri, 12 Feb 2016 22:10:18 +1000
Subject: [Slackbuilds-users] libreoffice 5.1 review
In-Reply-To: <56BDBCBF.80902@slackbuilds.org>
References: <56BC753F.60203@slackbuilds.org> <56BDBA56.80602@iinet.net.au>
 <56BDBCBF.80902@slackbuilds.org>
Message-ID: <56BDCBAA.5090002@iinet.net.au>

On 12/02/16 21:06, Willy Sudiarto Raharjo wrote:
>> Good news and ...
>>
>> I tried using the SlackBuild in libreoffice-review with the ch3.ppt test
>> file and found no problem. I had it running several hours in the
>> background while doing other things. Occasionally I would flip through a
>> few pages and all was OK.
>>
>> I also opened a test file mentioned in the first of the bug reports
>> above and it also worked without any problem.
>>
>> The only problem I found was when opening a file provided by someone
>> else via the libreoffice-dev list. Interestingly, they claim that the
>> official downloaded version (I'm equating that with the repackaged
>> libreoffice-review version) loads and runs the test file fine but their
>> own self-compiled version loads the file very slowly (>10 sec.). A file
>> demonstrating the problem is provided at
>> https://bugs.documentfoundation.org/attachment.cgi?id=121623 .
>>
>> I found that the version in libreoffice-review loads that file
>> (bigfile.odt) in 2-3secs but crashes immediately loading is complete.
>> This occurred 100% of the times I tried it. The new LibreOffice
>> build-from-source SlackBuild, which I have a personal interest in,
>> handles it OK - loads in 2-3secs and keeps running. Still, I'm not sure
>> what what to make of the test file - whether its a valid test of
>> anything - since it looks like gibberish when loaded.
>>
>> BTW Calligra Author opens bigfile.odt OK (under 3 secs).
>>
>> Not sure if that helps you decide anything but that is what I found.
>
> Hi Chris
>
> thanks for confirming, but i had this problem on my laptop and desktop
> and workstation, so it's not just happening on one machine.
>
> Also, Robby and i found this bug which is similar to my sympthoms
> https://crux.nu/bugs/index.php?do=details&task_id=1286
>
> just to make sure. Did you upgrade to the latest current with harfbuzz
> 1.1.3? It seems that's the culprit since Robby tried to downgrade to
> 1.1.2 and it worked nicely

chris at d6:~$ ls -l /var/log/packages/harfbuzz-1.1.3-x86_64-1
-rw-r--r-- 1 root root 5931 Feb  9 11:40 
/var/log/packages/harfbuzz-1.1.3-x86_64-1



From jbernts at broadpark.no  Fri Feb 12 13:02:03 2016
From: jbernts at broadpark.no (Jostein Berntsen)
Date: Fri, 12 Feb 2016 14:02:03 +0100
Subject: [Slackbuilds-users] libreoffice 5.1 review
In-Reply-To: <56BC753F.60203@slackbuilds.org>
References: <56BC753F.60203@slackbuilds.org>
Message-ID: <20160212130203.GC2614@jostein>

On 11.02.16,18:49, Willy Sudiarto Raharjo wrote:
>Hi
>
>I reverted my libreoffice update in my branch and place it under
>libreoffice-review since after using it for few hours, i noticed impress
>crashed very often when opening some files.
>
>I searched a bit and found this bug reports
>https://bugs.documentfoundation.org/show_bug.cgi?id=97396
>https://bugs.documentfoundation.org/show_bug.cgi?id=97234
>
>can anyone test the new libreoffice 5.1 and report back?
>
>i used this file as a test case
>http://codex.cs.yale.edu/avi/os-book/OS9/slide-dir/PPT-dir/ch3.ppt
>

Should this build be updated to v. 5.1.0.3 to check if this is corrected?

Another question:

Is there a reason for installing libreoffice to /opt instead of /usr/lib64?


Jostein

From willysr at slackbuilds.org  Fri Feb 12 15:27:40 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 12 Feb 2016 22:27:40 +0700
Subject: [Slackbuilds-users] libreoffice 5.1 review
In-Reply-To: <20160212130203.GC2614@jostein>
References: <56BC753F.60203@slackbuilds.org> <20160212130203.GC2614@jostein>
Message-ID: <56BDF9EC.6030500@slackbuilds.org>

> Should this build be updated to v. 5.1.0.3 to check if this is corrected?
> 
> Another question:
> 
> Is there a reason for installing libreoffice to /opt instead of /usr/lib64?

5.1.0.3 is the internal build number used by upstream developer, but the
use 5.1 as the "public number"

the reason is because it's only repackage from binary package, so we
keep the original location.


-- 
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/20160212/1e802fab/attachment.asc>

From kingbeowulf at gmail.com  Sat Feb 13 22:29:51 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 13 Feb 2016 14:29:51 -0800
Subject: [Slackbuilds-users] ATT. Ekiga Users
In-Reply-To: <20160211002528.GH14514@Blackswan>
References: <20160211002528.GH14514@Blackswan>
Message-ID: <56BFAE5F.102@gmail.com>

On 02/10/2016 04:25 PM, David Woodfall wrote:
> I need some opinions on adding Yelp as an optional dependency. Yelp
> is needed for the help pages to be displayed, but it requires
> webkitgtk3, among other things.
> 
> So the question is to add this support by default on, or off, as
> webkitgtk is quite a long build.
> 
> Opinions?
> 
> David

Since Yelp is an optional, external program, you can leave the help
support on by default noting that Yelp (and its dependencies ) is
required to view them.

Doesn't KDE have a help viewer for docbook xml (khelpcenter)?

Or perhaps something silly in the slackbuild script like

docbook2html -u -o <path-for-output> <path-to-ekiga-help doc>/ekiga.xml

to convert the docbook to HTML, etc etc.



-------------- 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/20160213/33e90c54/attachment.asc>

From Jim.Diamond at acadiau.ca  Sat Feb 13 23:23:40 2016
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Sat, 13 Feb 2016 19:23:40 -0400
Subject: [Slackbuilds-users] b0rken build: MasterPDFEditor
Message-ID: <20160213232340.GA13200@jdiamond-nb2>

Hi,

I realize all of you are busy getting ready for 14.2 (thanks!), but
the d/l link for MasterPDFEditor at
https://slackbuilds.org/repository/14.1/office/MasterPDFEditor/
instead gets master-pdf-editor-3.6.00_amd64.tar.gz which, not
surprisingly, has a different checksum than
master-pdf-editor-3.5.81_amd64.tar.gz, throwing a wrench in the works.

Cheers.

                                Jim

From dave at dawoodfall.net  Sat Feb 13 23:24:23 2016
From: dave at dawoodfall.net (David Woodfall)
Date: Sat, 13 Feb 2016 23:24:23 +0000
Subject: [Slackbuilds-users] ATT. Ekiga Users
In-Reply-To: <56BFAE5F.102@gmail.com>
References: <20160211002528.GH14514@Blackswan>
 <56BFAE5F.102@gmail.com>
Message-ID: <20160213232423.GK14514@Blackswan>

>On 02/10/2016 04:25 PM, David Woodfall wrote:
>> I need some opinions on adding Yelp as an optional dependency. Yelp
>> is needed for the help pages to be displayed, but it requires
>> webkitgtk3, among other things.
>>
>> So the question is to add this support by default on, or off, as
>> webkitgtk is quite a long build.
>>
>> Opinions?
>>
>> David
>
>Since Yelp is an optional, external program, you can leave the help
>support on by default noting that Yelp (and its dependencies ) is
>required to view them.

Yes, I'm thinking the same thing.

>Doesn't KDE have a help viewer for docbook xml (khelpcenter)?
>
>Or perhaps something silly in the slackbuild script like
>
>docbook2html -u -o <path-for-output> <path-to-ekiga-help doc>/ekiga.xml
>
>to convert the docbook to HTML, etc etc.


From willysr at slackbuilds.org  Sun Feb 14 00:57:16 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 14 Feb 2016 07:57:16 +0700
Subject: [Slackbuilds-users] b0rken build: MasterPDFEditor
In-Reply-To: <20160213232340.GA13200@jdiamond-nb2>
References: <20160213232340.GA13200@jdiamond-nb2>
Message-ID: <56BFD0EC.2090709@slackbuilds.org>

> I realize all of you are busy getting ready for 14.2 (thanks!), but
> the d/l link for MasterPDFEditor at
> https://slackbuilds.org/repository/14.1/office/MasterPDFEditor/
> instead gets master-pdf-editor-3.6.00_amd64.tar.gz which, not
> surprisingly, has a different checksum than
> master-pdf-editor-3.5.81_amd64.tar.gz, throwing a wrench in the works.

Hi Jim

Thanks for reporting it
in the meantime i have changed the download location to
https://sourceforge.net/projects/slackbuildsdirectlinks/files/MasterPDFEditor/master-pdf-editor-3.5.81_amd64.tar.gz

please note that this change is only the source links, not the one in
.info since i don't make anymore changes in 14.1 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/20160214/fcf6ecc4/attachment.asc>

From willysr at slackbuilds.org  Sun Feb 14 08:23:36 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 14 Feb 2016 15:23:36 +0700
Subject: [Slackbuilds-users] package to grab: retroshare
In-Reply-To: <56C00BBB.20505@sacrideo.us>
References: <56C00BBB.20505@sacrideo.us>
Message-ID: <56C03988.7050802@slackbuilds.org>

Anyone wanted to maintain this package?
currently it failed to build properly but a new version (0.6.0-rc2) is
available, but it requires new deps (qt5).

this is the original email i got from current maintainer


-------- Forwarded Message --------
Subject: Re: retroshare
Date: Sun, 14 Feb 2016 00:08:11 -0500
From: Aaron W. Hsu <arcfide at sacrideo.us>
To: Willy Sudiarto Raharjo <willysr at slackbuilds.org>

Thanks for your inquiry. Unfortunately, I am not currently running
RetroShare and I'm unable to continue maintainership of the RetroShare
Slackbuild. I would be happy to have someone take this over.


-- 
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/20160214/b48ca37b/attachment.asc>

From willysr at slackbuilds.org  Sun Feb 14 11:22:58 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 14 Feb 2016 18:22:58 +0700
Subject: [Slackbuilds-users] Next Round of Testing - mythtv
In-Reply-To: <20160207183832.3d46a3aa@home.rlworkman.net>
References: <56B6FECB.8030200@slackbuilds.org> <56B73FB0.7010207@iinet.net.au>
 <56B7E082.9030703@iinet.net.au>
 <20160207183832.3d46a3aa@home.rlworkman.net>
Message-ID: <56C06392.70408@slackbuilds.org>

>>> I just tried a quick build using the latest source code from
>>> https://codeload.github.com/MythTV/mythtv/tar.gz/fixes/0.27
>>> (this is 0.27.6 apparently). It builds to completion if the
>>> --enable-libvpx option is removed from the configure command.
>>>
>>> I don't use mythtv myself so I can't really say if this is a
>>> reasonable omission to enable the build, although I see it is not
>>> enabled by default.  
>>
>> There is also an explicit 0.27.6 version at the mythtv github repo:
>>      https://github.com/MythTV/mythtv/releases/tag/v0.27.6
>> however it produced the same result (builds only if --enable-libvpx
>> is removed) even though its just 6 days old.
>>
>> There is much better news about building from master which I cloned
>> and made a tarball available at:
>>  
>> http://sourceforge.net/projects/slackbuildsdirectlinks/files/mythtv/mythtv-0git20160208.tar.gz
>> (that is not really my place to put tarballs, so I'll will remove if 
>> anyone thinks its inappropriate).
>>
>> After the minor mods to the SlackBuild needed for the new tarball, 
>> building from this git tarball just works using the existing
>> configure options but with the added hard requirement of qt5.
> 
> 
> Looking at that git repo, it appears to work with libvpx in -current
> due to bumping the included ffmpeg, so I'm pretty sure that it needs
> (at least) the patch for ffmpeg and ffmpeg010 in the SBo tree already.
> It might not (i.e. probably won't) apply flawlessly, so you will need
> to rework it a bit, but that should almost surely fix the build failure
> with libvpx.

found a patch from ARCH Linux that should fix this issue
https://projects.archlinux.org/svntogit/community.git/tree/trunk/ffmpeg-libvpxenc-remove-some-unused-ctrl-id-mappings.patch?h=packages/mythtv

i'm building it now and if it compiles, you will see them on my branch
soon enough :)


-- 
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/20160214/9320e60f/attachment.asc>

From kingbeowulf at gmail.com  Sun Feb 14 18:45:52 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 14 Feb 2016 10:45:52 -0800
Subject: [Slackbuilds-users]  menulibre up for adoption to a new home
Message-ID: <56C0CB60.5090907@gmail.com>

I was hoping to test the new menulibre-2.1.x but have run into a snag.
Upstream has moved the code to Python3 (in SBo) and changed a bunch of
dependencies that I don't have the time and resources to support.  Here
is the dep list:

gir1.2-gdkpixbuf-2.0
gir1.2-glib-2.0
gir1.2-gemu-3.0 >=3.5.3
gir1.2-gtk-3.0
gnome-menus (in SBo)
pyhthon3 (in SBo)
python3-gi >= 3.0
python3-psutil

I think gir1.2-* refers to GObject Introspection
https://wiki.gnome.org/Projects/GObjectIntrospection

At this point, I am a bit lost as top how to proceed.
Damn it, SBo, I'm a chemist not a programmer!


-------------- 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/20160214/397da340/attachment-0001.asc>

From willysr at slackbuilds.org  Sun Feb 14 18:51:51 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 15 Feb 2016 01:51:51 +0700
Subject: [Slackbuilds-users] menulibre up for adoption to a new home
In-Reply-To: <56C0CB60.5090907@gmail.com>
References: <56C0CB60.5090907@gmail.com>
Message-ID: <56C0CCC7.4040004@slackbuilds.org>

> I was hoping to test the new menulibre-2.1.x but have run into a snag.
> Upstream has moved the code to Python3 (in SBo) and changed a bunch of
> dependencies that I don't have the time and resources to support.  Here
> is the dep list:
> 
> gir1.2-gdkpixbuf-2.0
> gir1.2-glib-2.0
> gir1.2-gemu-3.0 >=3.5.3
> gir1.2-gtk-3.0
> gnome-menus (in SBo)
> pyhthon3 (in SBo)
> python3-gi >= 3.0
> python3-psutil
> 
> I think gir1.2-* refers to GObject Introspection
> https://wiki.gnome.org/Projects/GObjectIntrospection

see here for a quick reference
https://aur.archlinux.org/packages/menulibre/

python3-psutil is already supported in psutil. You need to run
PYTHON3=yes ./psutil.SlackBuild

not all of those are hard deps i guess


-- 
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/20160215/a8a38205/attachment.asc>

From ruan.klein at gmail.com  Sun Feb 14 19:30:24 2016
From: ruan.klein at gmail.com (Ruan)
Date: Sun, 14 Feb 2016 17:30:24 -0200
Subject: [Slackbuilds-users] [update] winusb-1.0.11
Message-ID: <CAA9ENOsE0qBO18G=KkG+2OcgaPGKpUYOg_q=cTYa_71_=vcGrA@mail.gmail.com>

Fixed broken link in winusb.info - $DOWNLOAD variable

-- 



*Sincera e fraternalmente,Ruan K. F, R.'.C.'.MP.'.P*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160214/e09c5bf4/attachment.html>

From ruan.klein at gmail.com  Sun Feb 14 19:31:12 2016
From: ruan.klein at gmail.com (Ruan)
Date: Sun, 14 Feb 2016 17:31:12 -0200
Subject: [Slackbuilds-users] [update] winusb-1.0.11
In-Reply-To: <CAA9ENOsE0qBO18G=KkG+2OcgaPGKpUYOg_q=cTYa_71_=vcGrA@mail.gmail.com>
References: <CAA9ENOsE0qBO18G=KkG+2OcgaPGKpUYOg_q=cTYa_71_=vcGrA@mail.gmail.com>
Message-ID: <CAA9ENOvujd8b61osT9iP16NuoqGeCOs4UVcdjZN8dGPDc6neRA@mail.gmail.com>

Anexo.

2016-02-14 17:30 GMT-02:00 Ruan <ruan.klein at gmail.com>:

> Fixed broken link in winusb.info - $DOWNLOAD variable
>
> --
>
>
>
> *Sincera e fraternalmente,Ruan K. F, R.'.C.'.MP.'.P*
>



-- 



*Sincera e fraternalmente,Ruan K. F, R.'.C.'.MP.'.P*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160214/46a18da2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winusb.tar.gz
Type: application/x-gzip
Size: 3728 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160214/46a18da2/attachment.bin>

From willysr at slackbuilds.org  Sun Feb 14 19:47:17 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 15 Feb 2016 02:47:17 +0700
Subject: [Slackbuilds-users] [update] winusb-1.0.11
In-Reply-To: <CAA9ENOsE0qBO18G=KkG+2OcgaPGKpUYOg_q=cTYa_71_=vcGrA@mail.gmail.com>
References: <CAA9ENOsE0qBO18G=KkG+2OcgaPGKpUYOg_q=cTYa_71_=vcGrA@mail.gmail.com>
Message-ID: <56C0D9C5.4060307@slackbuilds.org>

> Fixed broken link in winusb.info - $DOWNLOAD variable

Fixed

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/20160215/24b67517/attachment.asc>

From pc_warner at yahoo.com  Sun Feb 14 20:53:40 2016
From: pc_warner at yahoo.com (Phillip Warner)
Date: Sun, 14 Feb 2016 20:53:40 +0000 (UTC)
Subject: [Slackbuilds-users] Pianobar fix for TLS fingerprint mismatch error
In-Reply-To: <1455245127.19119.11.camel@caraus.de>
References: <1455245127.19119.11.camel@caraus.de>
Message-ID: <354414831.4034929.1455483220468.JavaMail.yahoo@mail.yahoo.com>

Around the end of last year Pandora changed their certificate, so pianobar will not work unless you give it the new fingerprint.
In your pianobar config file (~/.config/pianobar/config) you need to have the following line:???? tls_fingerprint = 13CC51AC0C31CD96C55015C76914360F7AC41A00
(By the way, an example config file is in /usr/doc/pianobar-$VERSION/)
The next time Pandora updates their cert again, you can quickly find the value needed by executing:???? sh /usr/doc/pianobar-$VERSION/example-scripts/tls_fingerprint.sh
Finally, some people may wonder why I have not updated the SlackBuild for pianobar to the latest version.? The reason is because the 2013.09.15 version is the last one that does not require ffmpeg as a build dependency, and that version still works fine.? While some people may already have ffmpeg installed (myself included), I prefer to keep the dependencies as minor as possible.? If, however, pianobar users would rather me update the buildscript please let me know.

Warmest Regards,
--phillip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160214/7fd26901/attachment-0001.html>

From kingbeowulf at gmail.com  Sun Feb 14 21:04:18 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 14 Feb 2016 13:04:18 -0800
Subject: [Slackbuilds-users]  wxcam needs a new home
Message-ID: <56C0EBD2.8060906@gmail.com>

I'm dropping maintenance of wxcam for 14.2.  Anyone who wants it can
have it.

Reason: not updated for years and is not running stable
(crashes/segfault, freezes, loses webcam).  I don't have the skill to
patch it.

Thanks.

-------------- 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/20160214/96450703/attachment.asc>

From kingbeowulf at gmail.com  Sun Feb 14 21:44:34 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 14 Feb 2016 13:44:34 -0800
Subject: [Slackbuilds-users]  mumble / murmur home page correction
Message-ID: <56C0F542.30904@gmail.com>

The correct homepage for both mumble and murmur is

http://wiki.mumble.info/wiki/Main_Page

Thanks


-------------- 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/20160214/907da2eb/attachment.asc>

From willysr at slackbuilds.org  Sun Feb 14 23:35:36 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 15 Feb 2016 06:35:36 +0700
Subject: [Slackbuilds-users] wxcam needs a new home
In-Reply-To: <56C0EBD2.8060906@gmail.com>
References: <56C0EBD2.8060906@gmail.com>
Message-ID: <56C10F48.7020109@slackbuilds.org>

> I'm dropping maintenance of wxcam for 14.2.  Anyone who wants it can
> have it.
> 
> Reason: not updated for years and is not running stable
> (crashes/segfault, freezes, loses webcam).  I don't have the skill to
> patch it.

actually there is an update
https://github.com/galimba/wxcam
last update was in 2014, much better than original wxcam that was in 2011


-- 
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/20160215/d4e85c62/attachment.asc>

From willysr at slackbuilds.org  Sun Feb 14 23:38:12 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 15 Feb 2016 06:38:12 +0700
Subject: [Slackbuilds-users] mumble / murmur home page correction
In-Reply-To: <56C0F542.30904@gmail.com>
References: <56C0F542.30904@gmail.com>
Message-ID: <56C10FE4.4090306@slackbuilds.org>

> The correct homepage for both mumble and murmur is
> 
> http://wiki.mumble.info/wiki/Main_Page

Updated on my branch


-- 
Willy Sudiarto Raharjo

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

From miguel at thedeanda.com  Mon Feb 15 22:15:48 2016
From: miguel at thedeanda.com (Miguel De Anda)
Date: Mon, 15 Feb 2016 14:15:48 -0800
Subject: [Slackbuilds-users] nginx permissions?
In-Reply-To: <CAA62KfSUsQXoZMYUYDyp4ReSxMiwjdBKeaOCJvPvkyC1gbS7fA@mail.gmail.com>
References: <CAA62KfSUsQXoZMYUYDyp4ReSxMiwjdBKeaOCJvPvkyC1gbS7fA@mail.gmail.com>
Message-ID: <CAA62KfT4+8Aq03sw739ps1z1Mb9GYOGO7=KP91Mp+Hpe-dGCog@mail.gmail.com>

i actually [finally] figured out the problem. i only revisit this
problem each time i setup a new system and run into the same issue and
i think i solve it a different way each time. anyway, the solution to
this issue is that the permissions to the /var/lib/nginx folder are
700 and should be 755. can we try to fix that? i feel like i've had to
re-solve this a few times now. :-P

On Tue, May 5, 2015 at 10:01 PM, Miguel De Anda <miguel at thedeanda.com> wrote:
> i've installed nginx from the slackbuild and i have it run as a proxy for
> tomcat with a config something like this...
>
> sever {
>   server_name example.com;
>   location / {
>     proxy_pass http://localhost:8080;
>     proxy_set_header X-Real-IP $remote_addr;
>     proxy_set_header X-Forwarded-For $remote_addr;
>     proxy_set_header Host $host;
>   }
> }
>
> when it tries to load some files, it fails with the following error:
>
> 2015/05/05 14:59:31 [crit] 25274#0: *5 open()
> "/var/lib/nginx/proxy/3/00/0000000003" failed (13: Permission denied) while
> reading upstream, client: 192.168.1.2, server: example.com, request: "GET
> /foo-file.css HTTP/1.1", upstream: "http://127.0.0.1:8080/foo-file.css",
> host: "example.com", referrer: "http://example.com/index.html"
>
> it seems to kind of work if i add a
>
> user mdeanda users;
>
> to the config and change the permission to /var/lib/nginx/* to my local user
> (and create lots of folders in the proxy directory) but that's obviously not
> the correct way. has anybody dealt with this? i know ubuntu and others tend
> to run nginx as a www-data user, is that what we need for nginx? a new user?
>
> -m
>

From info at microlinux.fr  Wed Feb 17 15:06:16 2016
From: info at microlinux.fr (Nicolas Kovacs)
Date: Wed, 17 Feb 2016 16:06:16 +0100
Subject: [Slackbuilds-users] qemu: small mistake in README (wrong libusb
	version)
Message-ID: <56C48C68.8040708@microlinux.fr>

Hi,

I'm currently fiddling with qemu. The README says:

Slackware's libusb is too old. Thus, to enable usb redirection, install
usbredir, download libusb-1.19, and build with LIBUSB=yes ./qemu.SlackBuild

This should read:

Slackware's libusb is too old. Thus, to enable usb redirection, install
usbredir, download libusb-1.0.19, and build with LIBUSB=yes
./qemu.SlackBuild

Cheers,

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

From willysr at slackbuilds.org  Wed Feb 17 15:12:36 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 17 Feb 2016 22:12:36 +0700
Subject: [Slackbuilds-users] qemu: small mistake in README (wrong libusb
 version)
In-Reply-To: <56C48C68.8040708@microlinux.fr>
References: <56C48C68.8040708@microlinux.fr>
Message-ID: <56C48DE4.5000608@slackbuilds.org>

> I'm currently fiddling with qemu. The README says:
> 
> Slackware's libusb is too old. Thus, to enable usb redirection, install
> usbredir, download libusb-1.19, and build with LIBUSB=yes ./qemu.SlackBuild
> 
> This should read:
> 
> Slackware's libusb is too old. Thus, to enable usb redirection, install
> usbredir, download libusb-1.0.19, and build with LIBUSB=yes
> ./qemu.SlackBuild

Robby has taken care of that in master branch

https://slackbuilds.org/cgit/slackbuilds/commit/?id=83cbc71ea2b02e9ab3108fa20b42b4d6c2cbe063


-- 
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/20160217/f36ed550/attachment.asc>

From jens at tuxane.com  Wed Feb 17 15:38:19 2016
From: jens at tuxane.com (Jens)
Date: Wed, 17 Feb 2016 16:38:19 +0100
Subject: [Slackbuilds-users] package to grab: Site
Message-ID: <56C493EB.40308@localhost>

Hello everybody,
if someone would like to maintain Scite, I'll be happy to give it to a  
new maintainer.

Scite updates are quite regular and I don't have the time to do it 
properly at the moment.

If not, I would keep it but I would not be able to keep it current

Thanks,
Jens

From ryan.q at linux.com  Wed Feb 17 15:48:17 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Wed, 17 Feb 2016 07:48:17 -0800
Subject: [Slackbuilds-users] package to grab: Site
In-Reply-To: <56C493EB.40308@localhost>
References: <56C493EB.40308@localhost>
Message-ID: <CAAcyf-oUFPRHx30yJzeX0-F8n_WKm_GCb19gQq2GbjOi+3xmMw@mail.gmail.com>

On Feb 17, 2016 7:38 AM, "Jens" <jens at tuxane.com> wrote:
>
> Hello everybody,
> if someone would like to maintain Scite, I'll be happy to give it to a
new maintainer.
>
> Scite updates are quite regular and I don't have the time to do it
properly at the moment.
>
> If not, I would keep it but I would not be able to keep it current

Yes please!!!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160217/52c49ae7/attachment-0001.html>

From jens at tuxane.com  Wed Feb 17 15:51:56 2016
From: jens at tuxane.com (Jens)
Date: Wed, 17 Feb 2016 16:51:56 +0100
Subject: [Slackbuilds-users] package to grab: Site
In-Reply-To: <CAAcyf-oUFPRHx30yJzeX0-F8n_WKm_GCb19gQq2GbjOi+3xmMw@mail.gmail.com>
References: <56C493EB.40308@localhost>
 <CAAcyf-oUFPRHx30yJzeX0-F8n_WKm_GCb19gQq2GbjOi+3xmMw@mail.gmail.com>
Message-ID: <56C4971C.8020501@localhost>

Ryan, I was hoping you said this :)
So please go ahead!



Am 17.02.2016 um 16:48 schrieb Ryan P.C. McQuen:
>
>
> On Feb 17, 2016 7:38 AM, "Jens" <jens at tuxane.com 
> <mailto:jens at tuxane.com>> wrote:
> >
> > Hello everybody,
> > if someone would like to maintain Scite, I'll be happy to give it to 
> a  new maintainer.
> >
> > Scite updates are quite regular and I don't have the time to do it 
> properly at the moment.
> >
> > If not, I would keep it but I would not be able to keep it current
>
> Yes please!!!!
>
>
>
> _______________________________________________
> 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/20160217/ff63668c/attachment.html>

From kingbeowulf at gmail.com  Wed Feb 17 20:04:11 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Wed, 17 Feb 2016 12:04:11 -0800
Subject: [Slackbuilds-users] libreoffice 5.1 review
In-Reply-To: <56BC753F.60203@slackbuilds.org>
References: <56BC753F.60203@slackbuilds.org>
Message-ID: <56C4D23B.1070202@gmail.com>

On 02/11/2016 03:49 AM, Willy Sudiarto Raharjo wrote:
> Hi
> 
> I reverted my libreoffice update in my branch and place it under
> libreoffice-review since after using it for few hours, i noticed impress
> crashed very often when opening some files.
> 
> I searched a bit and found this bug reports
> https://bugs.documentfoundation.org/show_bug.cgi?id=97396
> https://bugs.documentfoundation.org/show_bug.cgi?id=97234
> 
> can anyone test the new libreoffice 5.1 and report back?
> 
> i used this file as a test case
> http://codex.cs.yale.edu/avi/os-book/OS9/slide-dir/PPT-dir/ch3.ppt
> 

I confirmed this glitch on a draw file (odg, newsletter, mixed text and
graphics) on 5.1.0.3, for the repackaged version.  This newsletter
worked fine in 4.4 and even re-writing it from scratch did not work.

The impress ppt was fine, although a bit slow to change slides. No
issues so far opening and using various text files (odf)

5.0.4 had random glitches with the same odg newsletter, but no other
issues observed.

5.0.5 works ok except for the draw component (odg crashes on all files:
4.4 created odg or new).  ch3.ppt opens but is initially slow; the
bigfile.odt crashes here but works ok with 4.4.

Maybe worth considering the fully compiled version if that seems more
stable?

-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/20160217/e139cebc/attachment.asc>

From willysr at slackbuilds.org  Wed Feb 17 23:47:03 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 18 Feb 2016 06:47:03 +0700
Subject: [Slackbuilds-users] libreoffice 5.1 review
In-Reply-To: <56C4D23B.1070202@gmail.com>
References: <56BC753F.60203@slackbuilds.org> <56C4D23B.1070202@gmail.com>
Message-ID: <56C50677.4090700@slackbuilds.org>

> Maybe worth considering the fully compiled version if that seems more
> stable?

Chris Willing have a package for that called LibreOffice


-- 
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/20160218/6d58948c/attachment.asc>

From willysr at slackbuilds.org  Thu Feb 18 18:41:13 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 18 Feb 2016 10:41:13 -0800
Subject: [Slackbuilds-users] libreoffice 5.1 review
In-Reply-To: <56C4D23B.1070202@gmail.com>
References: <56BC753F.60203@slackbuilds.org> <56C4D23B.1070202@gmail.com>
Message-ID: <56C61049.7060408@slackbuilds.org>

> I confirmed this glitch on a draw file (odg, newsletter, mixed text and
> graphics) on 5.1.0.3, for the repackaged version.  This newsletter
> worked fine in 4.4 and even re-writing it from scratch did not work.
> 
> The impress ppt was fine, although a bit slow to change slides. No
> issues so far opening and using various text files (odf)
> 
> 5.0.4 had random glitches with the same odg newsletter, but no other
> issues observed.
> 
> 5.0.5 works ok except for the draw component (odg crashes on all files:
> 4.4 created odg or new).  ch3.ppt opens but is initially slow; the
> bigfile.odt crashes here but works ok with 4.4.
> 
> Maybe worth considering the fully compiled version if that seems more
> stable?

on my laptop, downgrading to harfbuzz 1.1.2 fix the problem


-- 
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/20160218/5a53574f/attachment.asc>

From lynx at panix.com  Thu Feb 18 07:36:49 2016
From: lynx at panix.com (Arthur W. Green)
Date: Thu, 18 Feb 2016 00:36:49 -0700
Subject: [Slackbuilds-users] libreoffice 5.1 review
In-Reply-To: <56C61049.7060408@slackbuilds.org>
References: <56BC753F.60203@slackbuilds.org> <56C4D23B.1070202@gmail.com>
 <56C61049.7060408@slackbuilds.org>
Message-ID: <56C57491.10400@panix.com>



On 02/18/2016 11:41 AM, Willy Sudiarto Raharjo wrote:
> on my laptop, downgrading to harfbuzz 1.1.2 fix the problem

My experience is the same--with the upgrade to harfbuzz 1.1.3 (on
x86_64), LibreOffice 5.0.4.2 would always crash (and subsequently fail
recovery) when attempting to load certain summaries I drafted in Writer
that had no prior issues.  And my experience with 5.1 was much as others
reported.

Downgrading to harfbuzz 1.1.2 indeed seems to have resolved all
crash/recovery issues I was experiencing in both versions of LibreOffice.

\\ Arthur

From ruan.klein at gmail.com  Thu Feb 18 11:17:02 2016
From: ruan.klein at gmail.com (Ruan)
Date: Thu, 18 Feb 2016 09:17:02 -0200
Subject: [Slackbuilds-users] sbagen update (build 2)
Message-ID: <CAA9ENOtzLDfdEUtk78Ts7-SUYoVGRqoKk3kXLYS0wpk0fb-OcQ@mail.gmail.com>

Dropped sbagen-oss
Added padsp to play sequencies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160218/ca1f5f18/attachment.html>

From ruan.klein at gmail.com  Thu Feb 18 11:17:33 2016
From: ruan.klein at gmail.com (Ruan)
Date: Thu, 18 Feb 2016 09:17:33 -0200
Subject: [Slackbuilds-users] sbagen update (build 2)
In-Reply-To: <CAA9ENOtzLDfdEUtk78Ts7-SUYoVGRqoKk3kXLYS0wpk0fb-OcQ@mail.gmail.com>
References: <CAA9ENOtzLDfdEUtk78Ts7-SUYoVGRqoKk3kXLYS0wpk0fb-OcQ@mail.gmail.com>
Message-ID: <CAA9ENOuJBvvmBzDqsuSxJyu5KkW=h=Q2K4xJD1JSEwUYLKMoQg@mail.gmail.com>

Anexo.

2016-02-18 9:17 GMT-02:00 Ruan <ruan.klein at gmail.com>:

> Dropped sbagen-oss
> Added padsp to play sequencies
>



-- 



*Sincera e fraternalmente,Ruan K. F, R.'.C.'.MP.'.P*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160218/d23b0064/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sbagen.tar.gz
Type: application/x-gzip
Size: 3018 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160218/d23b0064/attachment-0001.bin>

From ruan.klein at gmail.com  Thu Feb 18 11:33:29 2016
From: ruan.klein at gmail.com (Ruan)
Date: Thu, 18 Feb 2016 09:33:29 -0200
Subject: [Slackbuilds-users] sbagen update (build 2)
In-Reply-To: <CAA9ENOuJBvvmBzDqsuSxJyu5KkW=h=Q2K4xJD1JSEwUYLKMoQg@mail.gmail.com>
References: <CAA9ENOtzLDfdEUtk78Ts7-SUYoVGRqoKk3kXLYS0wpk0fb-OcQ@mail.gmail.com>
 <CAA9ENOuJBvvmBzDqsuSxJyu5KkW=h=Q2K4xJD1JSEwUYLKMoQg@mail.gmail.com>
Message-ID: <CAA9ENOuobf0mK8f7HG8yAU9hHs+n7Pj1-+4mkt_kyt72aNgnUQ@mail.gmail.com>

Sorry, disregard my last email!

I'm attaching the correct SlackBuild.

2016-02-18 9:17 GMT-02:00 Ruan <ruan.klein at gmail.com>:

> Anexo.
>
> 2016-02-18 9:17 GMT-02:00 Ruan <ruan.klein at gmail.com>:
>
>> Dropped sbagen-oss
>> Added padsp to play sequencies
>>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160218/55fda29f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sbagen.tar.gz
Type: application/x-gzip
Size: 2957 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160218/55fda29f/attachment.bin>

From chris.willing at iinet.net.au  Thu Feb 18 11:59:15 2016
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Thu, 18 Feb 2016 21:59:15 +1000
Subject: [Slackbuilds-users] libreoffice 5.1 review
In-Reply-To: <56C61049.7060408@slackbuilds.org>
References: <56BC753F.60203@slackbuilds.org> <56C4D23B.1070202@gmail.com>
 <56C61049.7060408@slackbuilds.org>
Message-ID: <56C5B213.3030601@iinet.net.au>

On 19/02/16 04:41, Willy Sudiarto Raharjo wrote:
>> I confirmed this glitch on a draw file (odg, newsletter, mixed text and
>> graphics) on 5.1.0.3, for the repackaged version.  This newsletter
>> worked fine in 4.4 and even re-writing it from scratch did not work.
>>
>> The impress ppt was fine, although a bit slow to change slides. No
>> issues so far opening and using various text files (odf)
>>
>> 5.0.4 had random glitches with the same odg newsletter, but no other
>> issues observed.
>>
>> 5.0.5 works ok except for the draw component (odg crashes on all files:
>> 4.4 created odg or new).  ch3.ppt opens but is initially slow; the
>> bigfile.odt crashes here but works ok with 4.4.
>>
>> Maybe worth considering the fully compiled version if that seems more
>> stable?
>
> on my laptop, downgrading to harfbuzz 1.1.2 fix the problem

This may be relevant:
     https://bugs.freedesktop.org/show_bug.cgi?id=94009

- particularly comments 12 to 17 which, if correct, explain why the 
repackaged official build has the problem but the "build from source" 
SlackBuild does not (since it uses --with-system-harfbuzz).

chris


From kingbeowulf at gmail.com  Thu Feb 18 17:56:27 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 18 Feb 2016 09:56:27 -0800
Subject: [Slackbuilds-users] libreoffice 5.1 review
In-Reply-To: <56C5B213.3030601@iinet.net.au>
References: <56BC753F.60203@slackbuilds.org> <56C4D23B.1070202@gmail.com>
 <56C61049.7060408@slackbuilds.org> <56C5B213.3030601@iinet.net.au>
Message-ID: <CAPiArqO4935LQq+0i6isgEnTKXBX6Ucg-u0SUHcYvwTnyxs0bQ@mail.gmail.com>

On Thursday, February 18, 2016, Christoph Willing <
chris.willing at iinet.net.au> wrote:

>
>> on my laptop, downgrading to harfbuzz 1.1.2 fix the problem
>>
>
> This may be relevant:
>     https://bugs.freedesktop.org/show_bug.cgi?id=94009
>
> - particularly comments 12 to 17 which, if correct, explain why the
> repackaged official build has the problem but the "build from source"
> SlackBuild does not (since it uses --with-system-harfbuzz).
>
> chris
>
>
Indeed. I saw those posts after my email.  I grabbed alienbob's libreoffice
pre-built package for current ( not having time to start a lengthy
compile), and it ran fine.  This indicates the "danger" of using pre-built
binaries,  unless the build is done on the same/similar system software
configuration
-Ed


-- 
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/20160218/256c56a9/attachment.html>

From bryanlharris at gmail.com  Fri Feb 19 13:53:17 2016
From: bryanlharris at gmail.com (Bryan Harris)
Date: Fri, 19 Feb 2016 08:53:17 -0500
Subject: [Slackbuilds-users] Question about current package: monit
Message-ID: <CAJ00z7CCv=k8wM9okP2A4XDFKAA6veag5YNi7E8Dv6VqDUdh8Q@mail.gmail.com>

Hi all,

After installing the SBo monit on Slackware and CentOS, I noticed
CentOS had a /etc/monit.conf but not Slackware.  When I look in the
package list (/var/log/packages/monit...) I don't see it listed.

It's provided by the upstream author, only they call it monitrc.  The
Red Hat people renamed it to /etc/monit.conf but it looks like the
same file.

It is listed in the Makefile, but I don't know enough about Makefiles
to understand why it's not being included.  I manually did the build
steps on my own, and all I got was the executable and the man page in
my DESTDIR, nothing more.

I guess my question is this.  Is it possible to just update one part
of a SBo package?  Since the package already exists I mean.

I have not created a SBo package in years but my best guess would be
to add a line to the current monit.Slackbuild which would copy monitrc
to an appropriate place in the $PKG folder, probably ./etc/monit.conf
like the Red Hat people did, and I guess there is something that needs
to be done to the doinst.sh script.  Can such a change be made to the
current monit on SBo?

Thanks in advance.

V/r,
Bryan

From willysr at slackbuilds.org  Fri Feb 19 17:20:06 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 20 Feb 2016 00:20:06 +0700
Subject: [Slackbuilds-users] Question about current package: monit
In-Reply-To: <CAJ00z7CCv=k8wM9okP2A4XDFKAA6veag5YNi7E8Dv6VqDUdh8Q@mail.gmail.com>
References: <CAJ00z7CCv=k8wM9okP2A4XDFKAA6veag5YNi7E8Dv6VqDUdh8Q@mail.gmail.com>
Message-ID: <56C74EC6.4030502@slackbuilds.org>

> After installing the SBo monit on Slackware and CentOS, I noticed
> CentOS had a /etc/monit.conf but not Slackware.  When I look in the
> package list (/var/log/packages/monit...) I don't see it listed.
> 
> It's provided by the upstream author, only they call it monitrc.  The
> Red Hat people renamed it to /etc/monit.conf but it looks like the
> same file.
> 
> It is listed in the Makefile, but I don't know enough about Makefiles
> to understand why it's not being included.  I manually did the build
> steps on my own, and all I got was the executable and the man page in
> my DESTDIR, nothing more.
> 
> I guess my question is this.  Is it possible to just update one part
> of a SBo package?  Since the package already exists I mean.
> 
> I have not created a SBo package in years but my best guess would be
> to add a line to the current monit.Slackbuild which would copy monitrc
> to an appropriate place in the $PKG folder, probably ./etc/monit.conf
> like the Red Hat people did, and I guess there is something that needs
> to be done to the doinst.sh script.  Can such a change be made to the
> current monit on SBo?

Fixed in my branch and updated to the latest release

Thanks for the suggestion

-- 
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/20160220/8efe0376/attachment.asc>

From bryanlharris at gmail.com  Fri Feb 19 18:01:57 2016
From: bryanlharris at gmail.com (Bryan Harris)
Date: Fri, 19 Feb 2016 13:01:57 -0500
Subject: [Slackbuilds-users] Question about current package: monit
In-Reply-To: <56C74EC6.4030502@slackbuilds.org>
References: <CAJ00z7CCv=k8wM9okP2A4XDFKAA6veag5YNi7E8Dv6VqDUdh8Q@mail.gmail.com>
 <56C74EC6.4030502@slackbuilds.org>
Message-ID: <CAJ00z7D_MB=0Guv9R5EyKRLA55KJ2cbzx6AgJ25tqir+nS=yig@mail.gmail.com>

Oh very nice.  Okay thanks and have a good weekend.

V/r,
Bryan

On Fri, Feb 19, 2016 at 12:20 PM, Willy Sudiarto Raharjo
<willysr at slackbuilds.org> wrote:
>> After installing the SBo monit on Slackware and CentOS, I noticed
>> CentOS had a /etc/monit.conf but not Slackware.  When I look in the
>> package list (/var/log/packages/monit...) I don't see it listed.
>>
>> It's provided by the upstream author, only they call it monitrc.  The
>> Red Hat people renamed it to /etc/monit.conf but it looks like the
>> same file.
>>
>> It is listed in the Makefile, but I don't know enough about Makefiles
>> to understand why it's not being included.  I manually did the build
>> steps on my own, and all I got was the executable and the man page in
>> my DESTDIR, nothing more.
>>
>> I guess my question is this.  Is it possible to just update one part
>> of a SBo package?  Since the package already exists I mean.
>>
>> I have not created a SBo package in years but my best guess would be
>> to add a line to the current monit.Slackbuild which would copy monitrc
>> to an appropriate place in the $PKG folder, probably ./etc/monit.conf
>> like the Red Hat people did, and I guess there is something that needs
>> to be done to the doinst.sh script.  Can such a change be made to the
>> current monit on SBo?
>
> Fixed in my branch and updated to the latest release
>
> Thanks for the suggestion
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> 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 ruan.klein at gmail.com  Sat Feb 20 00:49:26 2016
From: ruan.klein at gmail.com (Ruan)
Date: Fri, 19 Feb 2016 22:49:26 -0200
Subject: [Slackbuilds-users] Add slack-desktop 1.2.6 to SlackBuilds
Message-ID: <CAA9ENOuWvxfP1C=BqNGn8jb9xXqE58bzMmXYwM_XvbDq-0ssEA@mail.gmail.com>

"Slack" has nothing to do with the "Slackware"; Slack is a messaging app
for teams that is on a mission to make your working life simpler, more
pleasant, and more productive.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160219/4fae23d5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: slack-desktop.tar.gz
Type: application/x-gzip
Size: 2441 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160219/4fae23d5/attachment.bin>

From ryan.q at linux.com  Sat Feb 20 00:59:17 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Fri, 19 Feb 2016 16:59:17 -0800
Subject: [Slackbuilds-users] Add slack-desktop 1.2.6 to SlackBuilds
In-Reply-To: <CAA9ENOuWvxfP1C=BqNGn8jb9xXqE58bzMmXYwM_XvbDq-0ssEA@mail.gmail.com>
References: <CAA9ENOuWvxfP1C=BqNGn8jb9xXqE58bzMmXYwM_XvbDq-0ssEA@mail.gmail.com>
Message-ID: <CAAcyf-o1yXOy8z0jE+k=GMDeqQmvQ69tHWzqFdufXqBOD9DPJg@mail.gmail.com>

On Feb 19, 2016 4:49 PM, "Ruan" <ruan.klein at gmail.com> wrote:
>
> "Slack" has nothing to do with the "Slackware"; Slack is a messaging app
for teams that is on a mission to make your working life simpler, more
pleasant, and more productive.

Anyone can submit builds to SBo. Ihave one for Slack in the works, but it
still needs testing before it is ready for SBo:

https://github.com/ryanpcmcquen/ryanpc-slackbuilds/tree/master/unofficial/slack
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160219/4bc63c6b/attachment.html>

From ruan.klein at gmail.com  Sat Feb 20 01:04:17 2016
From: ruan.klein at gmail.com (Ruan)
Date: Fri, 19 Feb 2016 23:04:17 -0200
Subject: [Slackbuilds-users] Add slack-desktop 1.2.6 to SlackBuilds
In-Reply-To: <CAAcyf-o1yXOy8z0jE+k=GMDeqQmvQ69tHWzqFdufXqBOD9DPJg@mail.gmail.com>
References: <CAA9ENOuWvxfP1C=BqNGn8jb9xXqE58bzMmXYwM_XvbDq-0ssEA@mail.gmail.com>
 <CAAcyf-o1yXOy8z0jE+k=GMDeqQmvQ69tHWzqFdufXqBOD9DPJg@mail.gmail.com>
Message-ID: <CAA9ENOtEMDis9CNq4NPK83GsNWnBUS=XAouhif_2SO6C+g2-yA@mail.gmail.com>

Ok, thanks for the info.

2016-02-19 22:59 GMT-02:00 Ryan P.C. McQuen <ryan.q at linux.com>:

>
> On Feb 19, 2016 4:49 PM, "Ruan" <ruan.klein at gmail.com> wrote:
> >
> > "Slack" has nothing to do with the "Slackware"; Slack is a messaging app
> for teams that is on a mission to make your working life simpler, more
> pleasant, and more productive.
>
> Anyone can submit builds to SBo. Ihave one for Slack in the works, but it
> still needs testing before it is ready for SBo:
>
>
> https://github.com/ryanpcmcquen/ryanpc-slackbuilds/tree/master/unofficial/slack
>
> _______________________________________________
> 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/
>
>
>


-- 



*Sincera e fraternalmente,Ruan K. F, R.'.C.'.MP.'.P*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160219/cae7be07/attachment.html>

From fernando.lopezjr at gmail.com  Sun Feb 21 01:25:23 2016
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sat, 20 Feb 2016 18:25:23 -0700
Subject: [Slackbuilds-users] kodi slackpkg.
Message-ID: <CALrQ46Dmg0N1FEneWwSWTDoEz4s+uUsH3XQegW5N0F5SuABM0A@mail.gmail.com>

kodi home url still points to the old xbmc url...


-- 

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

From willysr at slackbuilds.org  Sun Feb 21 01:38:13 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 21 Feb 2016 08:38:13 +0700
Subject: [Slackbuilds-users] kodi slackpkg.
In-Reply-To: <CALrQ46Dmg0N1FEneWwSWTDoEz4s+uUsH3XQegW5N0F5SuABM0A@mail.gmail.com>
References: <CALrQ46Dmg0N1FEneWwSWTDoEz4s+uUsH3XQegW5N0F5SuABM0A@mail.gmail.com>
Message-ID: <56C91505.4010909@slackbuilds.org>

> kodi home url still points to the old xbmc url...

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/20160221/0bc9a0a2/attachment.asc>

From z.coldplayer at gmail.com  Mon Feb 22 06:31:35 2016
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Mon, 22 Feb 2016 10:31:35 +0400
Subject: [Slackbuilds-users] libbluray cannot be downloaded using wget
Message-ID: <CAEWL1_9Rks0MN8n3nSAS_pDSO7zM+puQL86f_2m9nr2YYgd88A@mail.gmail.com>

Hi, usually slackbuilds downloads stuffs using wget.

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


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


But using curl , I was able to download libbluray.

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


I'm using slackware-current.

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

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

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

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

Originally written by Hrvoje Niksic <hniksic at xemacs.org>.
Please send bug reports and questions to <bug-wget at gnu.org>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160222/89049a17/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libbluray.png
Type: image/png
Size: 194573 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160222/89049a17/attachment-0001.png>

From artourter at gmail.com  Mon Feb 22 13:40:00 2016
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Mon, 22 Feb 2016 13:40:00 +0000
Subject: [Slackbuilds-users] libbluray cannot be downloaded using wget
In-Reply-To: <CAEWL1_9Rks0MN8n3nSAS_pDSO7zM+puQL86f_2m9nr2YYgd88A@mail.gmail.com>
References: <CAEWL1_9Rks0MN8n3nSAS_pDSO7zM+puQL86f_2m9nr2YYgd88A@mail.gmail.com>
Message-ID: <CAK09-vkB-5K9K1DdBN57hrgqsqStPFGwH7vnbMNLK47e3+ZVJg@mail.gmail.com>

if one changes the the url to use the http protocol (
http://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2)
it works fine.

I suspect something was changed on the configuration of their ftp server.

Cheers

Greg

On 22 February 2016 at 06:31, Jheengut Pritvi <z.coldplayer at gmail.com>
wrote:

> Hi, usually slackbuilds downloads stuffs using wget.
>
> I'm building the package libbluray but I'm getting the following error ::
>
>
> libbluray:
> libbluray not found in /var/cache/sbopkg.
> --2016-02-22 10:24:52--
> ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
>            => 'libbluray-0.9.2.tar.bz2'
> Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2,
> 2a01:e0d:1:3:58bf:fa02:c0de:20
> Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:21...
> connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done.    ==> PWD ... done.
> ==> TYPE I ... done.  ==> CWD (1) /pub/videolan/libbluray/0.9.2 ... done.
> ==> SIZE libbluray-0.9.2.tar.bz2 ... 704357
> ==> PASV ... couldn't connect to 127.0.1.1 port 62782: Connection refused
>
>
> But using curl , I was able to download libbluray.
>
> curl
> ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
> >libbluray-0.9.2.tar.bz2
>   % Total    % Received % Xferd  Average Speed   Time    Time     Time
> Current
>                                  Dload  Upload   Total   Spent    Left
> Speed
> 100  687k  100  687k    0     0  47257      0  0:00:14  0:00:14 --:--:--
> 96258
>
>
> I'm using slackware-current.
>
> wget --version
> GNU Wget 1.14 built on linux-gnu.
>
> +digest +https +ipv6 +iri +large-file +nls +ntlm +opie +ssl/openssl
>
> Wgetrc:
>     /etc/wgetrc (system)
> Locale: /usr/share/locale
> Compile: gcc -DHAVE_CONFIG_H -DSYSTEM_WGETRC="/etc/wgetrc"
>     -DLOCALEDIR="/usr/share/locale" -I. -I../lib -I../lib -O2 -fPIC
> Link: gcc -O2 -fPIC -lssl -lcrypto -lz -ldl -lz -lz -lidn -luuid -lpcre
>     ftp-opie.o openssl.o http-ntlm.o ../lib/libgnu.a
>
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://www.gnu.org/licenses/gpl.html>.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Originally written by Hrvoje Niksic <hniksic at xemacs.org>.
> Please send bug reports and questions to <bug-wget at gnu.org>.
>
>
>
> _______________________________________________
> 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/20160222/a50ae97a/attachment.html>

From glenn.becker at gmail.com  Mon Feb 22 14:38:50 2016
From: glenn.becker at gmail.com (Glenn Becker)
Date: Mon, 22 Feb 2016 09:38:50 -0500
Subject: [Slackbuilds-users] perl-glib source URL
Message-ID: <CANCo2a3TimtQ7iz4hkBm1CuVEk69Uz9M7+XKH9Mzfc-gukynWg@mail.gmail.com>

Hi --

I maintain the SlackBuild for the *perl-glib* module. Yesterday a user
informed me that the URL for the tarball did not work.

Could someone with access update two things in that SlackBuild:

source URL in perl-glib.info should be

https://cpan.metacpan.org/authors/id/X/XA/XAOC/Glib-1.307.tar.gz

and (if it's easy - if not, I'll hold until 14.2 is out) update my contact
email to

glenn.becker at gmail.com

Thanks,

Glenn

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

From willysr at slackbuilds.org  Mon Feb 22 15:11:55 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 22 Feb 2016 22:11:55 +0700
Subject: [Slackbuilds-users] perl-glib source URL
In-Reply-To: <CANCo2a3TimtQ7iz4hkBm1CuVEk69Uz9M7+XKH9Mzfc-gukynWg@mail.gmail.com>
References: <CANCo2a3TimtQ7iz4hkBm1CuVEk69Uz9M7+XKH9Mzfc-gukynWg@mail.gmail.com>
Message-ID: <56CB253B.70606@slackbuilds.org>

> I maintain the SlackBuild for the *perl-glib* module. Yesterday a user
> informed me that the URL for the tarball did not work.
> 
> Could someone with access update two things in that SlackBuild:
> 
> source URL in perl-glib.info should be
> 
> https://cpan.metacpan.org/authors/id/X/XA/XAOC/Glib-1.307.tar.gz

done

> and (if it's easy - if not, I'll hold until 14.2 is out) update my contact
> email to
> 
> glenn.becker at gmail.com

done

-- 
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/20160222/39caf699/attachment.asc>

From willysr at slackbuilds.org  Mon Feb 22 15:30:28 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 22 Feb 2016 22:30:28 +0700
Subject: [Slackbuilds-users] libbluray cannot be downloaded using wget
In-Reply-To: <CAK09-vkB-5K9K1DdBN57hrgqsqStPFGwH7vnbMNLK47e3+ZVJg@mail.gmail.com>
References: <CAEWL1_9Rks0MN8n3nSAS_pDSO7zM+puQL86f_2m9nr2YYgd88A@mail.gmail.com>
 <CAK09-vkB-5K9K1DdBN57hrgqsqStPFGwH7vnbMNLK47e3+ZVJg@mail.gmail.com>
Message-ID: <8F678EFC-F4BE-41A5-AA28-0E10C2A8066F@slackbuilds.org>


> if one changes the the url to use the http protocol (http://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2) it works fine.
> 
> I suspect something was changed on the configuration of their ftp server.

Fixed in my branch

--
Willy Sudiarto Raharjo

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

From gerardo.zamudio at linux.com  Mon Feb 22 15:53:19 2016
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Mon, 22 Feb 2016 09:53:19 -0600
Subject: [Slackbuilds-users] Fixes for teamviewer.SlackBuild
In-Reply-To: <56936DF3.3030708@slackbuilds.org>
References: <5693608F.7040907@microlinux.fr>
 <569366F6.4010309@slackbuilds.org> <56936C6E.3080306@microlinux.fr>
 <56936DF3.3030708@slackbuilds.org>
Message-ID: <56CB2EEF.3070502@linux.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 01/11/2016 02:55 AM, Willy Sudiarto Raharjo wrote:
>>> about the last line (ln -s), makepkg will detect the path and 
>>> write it into the doinst.sh properly. If you use $PKG, then it 
>>> will point to /tmp/SBo/xxx whichh is incorrect
>> 
>> Why not use a relative path for the symlink?
> 
> i just follow what others have been doing and so far, it works :)
> 
> 
> 
> _______________________________________________ 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/
> 

Any reason TeamViewer was marked as UNSUPPORTED for 64bit?

See commit 964a402355ae8e20d320e541c2ea5ad61476dbd5 on SBo.

There is a 64bit download available here:

http://download.teamviewer.com/download/teamviewer_amd64.deb

The README on SBo states "If you are running 64-bit machines, you will
need a multilib system", which I have. I had to modify the SlackBuild
to get 64bit TeamViewer to download and install. It's worked fine for
over a year on both version 10 and 11.

gzamudio at hades:~ $ ls -l /var/log/packages/ | grep teamviewer
- -rw-r--r-- 1 root root   15324 Jan  5 19:45
teamviewer-11.0.53191-x86_64-1_SBo

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJWyy7sAAoJEPbPpamee1lXdbUQAKs0onOuNVk94x9rjCSxpynT
ddbX/2thGuKmAIIpf2yBEjHR+mLzW7bmncYugQCPmAgeeAPlyDoWdit8OAWpy1Zf
eKaZlIHnbkDzHt7VW11TOmASdW+lUMzpc1m/NvxMDwxjxvnAmCyBL8CH46cSXBLm
cH0cLzEKHWmyWT3H3szVmMAPsXF9K3m5ShEgE2ZDkoEmUKbEdqQxnIQ+hHWoDYL5
DwN75aRHNUNOTpe+sizn2Etdh9BFCXT0oHaH9vkUWAqyBn83Lt3tUPANrFL5eeYn
keZjknmW7IAFVikK1cpwMJo6GewVeYRXKqDUKSMURnj4NZMJDNYoNtsh1WtarwRi
exm9VfH1KSd/g4y9AvAATUYyhzW6HADp0rcQBwQrvMDLeNT1WUXXpRyyO3YSkKUr
CTTHN0azTP+Q27HzMkE5kwRG9PZ/9DGpKLg39ZclLjb3tJFmCASLWA++3EO1gexM
8l4G9DdVyHG/OY7ozqZQgCP/usv9tB+vAnJsYcniSOQ688OJBVeLjy8ddcFFSFjO
gEzwzjUqsU4jVdSkp7p3unyfju3rAU9dxDGNKE5mvYa+fqGruxPz2O/xm+8EJDkE
I9FaV70OReBE3L94ok2RU9upbqnOrryipmvruS9FtaCmCfAGbMQ1oazmWGkkcw6Z
qV684Ccz814S3HJxfDXt
=RIWb
-----END PGP SIGNATURE-----

From belka at caraus.de  Mon Feb 22 15:55:55 2016
From: belka at caraus.de (Eugen Wissner)
Date: Mon, 22 Feb 2016 16:55:55 +0100
Subject: [Slackbuilds-users] Fixes for teamviewer.SlackBuild
In-Reply-To: <56CB2EEF.3070502@linux.com>
References: <5693608F.7040907@microlinux.fr>
 <569366F6.4010309@slackbuilds.org> <56936C6E.3080306@microlinux.fr>
 <56936DF3.3030708@slackbuilds.org> <56CB2EEF.3070502@linux.com>
Message-ID: <1456156555.13753.0.camel@caraus.de>


"64 bit" means pure 64-bit, not multilib. Sure it works on multilib
like everything else that is 32bit.

Am Montag, den 22.02.2016, 09:53 -0600 schrieb Gerardo Zamudio:
> On 01/11/2016 02:55 AM, Willy Sudiarto Raharjo wrote:
> > 
> > > 
> > > > 
> > > > about the last line (ln -s), makepkg will detect the path and?
> > > > write it into the doinst.sh properly. If you use $PKG, then it?
> > > > will point to /tmp/SBo/xxx whichh is incorrect
> > > Why not use a relative path for the symlink?
> > i just follow what others have been doing and so far, it works :)
> > 
> > 
> > 
> > _______________________________________________ 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/
> > 
> Any reason TeamViewer was marked as UNSUPPORTED for 64bit?
> 
> See commit 964a402355ae8e20d320e541c2ea5ad61476dbd5 on SBo.
> 
> There is a 64bit download available here:
> 
> http://download.teamviewer.com/download/teamviewer_amd64.deb
> 
> The README on SBo states "If you are running 64-bit machines, you
> will
> need a multilib system", which I have. I had to modify the SlackBuild
> to get 64bit TeamViewer to download and install. It's worked fine for
> over a year on both version 10 and 11.
> 
> gzamudio at hades:~ $ ls -l /var/log/packages/ | grep teamviewer
> -rw-r--r-- 1 root root???15324 Jan??5 19:45
> teamviewer-11.0.53191-x86_64-1_SBo
> 
> _______________________________________________
> 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  Mon Feb 22 15:56:09 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 22 Feb 2016 22:56:09 +0700
Subject: [Slackbuilds-users] Fixes for teamviewer.SlackBuild
In-Reply-To: <56CB2EEF.3070502@linux.com>
References: <5693608F.7040907@microlinux.fr>
 <569366F6.4010309@slackbuilds.org> <56936C6E.3080306@microlinux.fr>
 <56936DF3.3030708@slackbuilds.org> <56CB2EEF.3070502@linux.com>
Message-ID: <56CB2F99.6080802@slackbuilds.org>

> Any reason TeamViewer was marked as UNSUPPORTED for 64bit?
> 
> See commit 964a402355ae8e20d320e541c2ea5ad61476dbd5 on SBo.
> 
> There is a 64bit download available here:
> 
> http://download.teamviewer.com/download/teamviewer_amd64.deb
> 
> The README on SBo states "If you are running 64-bit machines, you will
> need a multilib system", which I have. I had to modify the SlackBuild
> to get 64bit TeamViewer to download and install. It's worked fine for
> over a year on both version 10 and 11.
> 
> gzamudio at hades:~ $ ls -l /var/log/packages/ | grep teamviewer
> -rw-r--r-- 1 root root   15324 Jan  5 19:45
> teamviewer-11.0.53191-x86_64-1_SBo

the 64 bit is indeed requires multilib and since i don't use multilib
(and it's not officially supported by SBo), i can't give any support nor
test it.

people may use the 64 bit in multilib environment but not from official
support (ie: they are on their own).


-- 
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/20160222/afde6a68/attachment.asc>

From gerardo.zamudio at linux.com  Mon Feb 22 16:05:39 2016
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Mon, 22 Feb 2016 10:05:39 -0600
Subject: [Slackbuilds-users] Fixes for teamviewer.SlackBuild
In-Reply-To: <56CB2F99.6080802@slackbuilds.org>
References: <5693608F.7040907@microlinux.fr>
 <569366F6.4010309@slackbuilds.org> <56936C6E.3080306@microlinux.fr>
 <56936DF3.3030708@slackbuilds.org> <56CB2EEF.3070502@linux.com>
 <56CB2F99.6080802@slackbuilds.org>
Message-ID: <56CB31D3.7020402@linux.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 02/22/2016 09:56 AM, Willy Sudiarto Raharjo wrote:
> 
> the 64 bit is indeed requires multilib and since i don't use
> multilib (and it's not officially supported by SBo), i can't give
> any support nor test it.
> 
> people may use the 64 bit in multilib environment but not from
> official support (ie: they are on their own).
> 

This if block effectively forces 32bit regardless if multilib is
installed or not:

if [ "$ARCH" = "i486" ]; then
  DEBARCH="i386"
  LIBDIRSUFFIX=""
else
  echo "Package for $(uname -m) architecture is not available."
  exit 1
fi

I am aware multilib is not supported by SBo but the last line in the
README leads one to believe the SlackBuild will at least build on
multilib as is.

I'd recommend changing that line in the README to say it works on
multilib with some modifications to the SlackBuild or simply not
mention it at all.

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJWyzHOAAoJEPbPpamee1lXvaMQAIDouMYtpSHq+17bibsSh2ot
QCn9uoc773c3N9zwEA2dKh/KZzPXuziG1zgG3oPTwpnGwdI/VAbW0/aqNjU6IXzC
nJmynnR5JUt/eToWcRzXa6X8JIaanwGSsRV4Rj6fZdTfuXHCNU+DFNmZE8/MFsK0
A+PLpPO5tQg2t6oEgW1ctPBUL2FMbbMEHXwq1AQPYV78pQAUO7jh5IyRVUnzFDCE
pj6O0pLOuhkM4kAlW0K9ffuOhftVwvDQxwglDKwnXiTny23+CSHWr90Crdg+yg7v
K6TxFvwADTyEf14u5RDT+2uXkwaltWvcY18615dkA5F6x1TMEcXBVGoADDv8JF5e
2+MVYjdY28BqcfUR5ZmfBnYwVuCtk6JoSr+CRdX2JNM8LbY9R1qdaZ1erGNd8f5y
uawjn55A7Akz1qeQnP0wAkN9xBGWLdLZeQA1AxAD0yqgwqQb7zLzvfxUrP7s+Tbe
3XPIuq4MpOEeubTUcQl0y4Z1FXFEmWtdFD+w66kIJPf5nKsIx5Dc3FiuO7n7Lf7Y
70c1Q9u745V8IG0kHQal5jKwxwfu17EtfEWut2y/FMBJ+2Zj8y5nqrPZs4WSAwtw
nWVTJAyos03Ot6G8OQHeuX6yYmsiPaESrk8n/04bWjnij7uxe+wPEBitdN2LowW6
AIrLOJo4kqaq292U6MJp
=SCKt
-----END PGP SIGNATURE-----

From willysr at slackbuilds.org  Mon Feb 22 18:10:43 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 23 Feb 2016 01:10:43 +0700
Subject: [Slackbuilds-users] ffmpeg updates
Message-ID: <56CB4F23.5010803@slackbuilds.org>

I have just merged all changes during the last few days back to master
and it includes ffmpeg updates to 2.8.x branch.

there are a lot of packages depends on ffmpeg and we need your help to
confirm if those packages are built properly against ffmpeg 2.8.

please let us know if there are problems and even better, send us the
patches or fixes to it.

most of the entries in the previous BUILD FAILURE list has been fixed
and these are the remaining broken packages

  audio/ardour
  audio/azr3
  audio/guitarix
  development/monodevelop
  development/phantomjs
  games/foobillardplus
  games/jfsw
  games/singularity
  games/unvanquished
  haskell/haskell-platform
  libraries/ggz-base-libs
  multimedia/cantata
  network/mosaic-ck
  network/retroshare
  network/smstools3
  network/sockstress

happy testing :)


-- 
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/20160223/68f6e10d/attachment.asc>

From slackbuilds at schoepfer.info  Mon Feb 22 22:53:15 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 22 Feb 2016 23:53:15 +0100
Subject: [Slackbuilds-users] Maintainable texlive texmf-tree
Message-ID: <da53af49db66309b9c159170dd3057f5@schoepfer.info>

Hi,

maybe i better should post this on LQ, just tell me.
As it seems that texlive will never be a stock slackware-package mostly  
because of its size, i wrote a script that should help maintaining a 
smaller texmf-tree.
http://slackware.schoepfer.info/stuff/texmf_get.sh
The approach is similar to the texlive-netinstaller, but the script has 
the advantage in the ability to add/exclude single tex-packages, not 
only schemes and collections, output is a tar.xz.
Schemes/collections/packages may be mixed in the ADD/EXCLUDE variables 
inside the script.
By using the excludes, it should be possible e.g. to provide a small 
base-texlive-slackware-package with some additional tex-packages, and a 
further big(tetex?-scheme minus base-tex-packages) 
texlive-slackware-package.
Might this be of any use for the texlive-maintainers on this list?
Feedback is welcome, thanks.

Regards

Franzen

From rworkman at slackbuilds.org  Mon Feb 22 23:48:20 2016
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 22 Feb 2016 17:48:20 -0600
Subject: [Slackbuilds-users] Maintainable texlive texmf-tree
In-Reply-To: <da53af49db66309b9c159170dd3057f5@schoepfer.info>
References: <da53af49db66309b9c159170dd3057f5@schoepfer.info>
Message-ID: <20160222174820.3dd89b0c@home.rlworkman.net>

On Mon, 22 Feb 2016 23:53:15 +0100
Franzen <slackbuilds at schoepfer.info> wrote:

> Hi,
> 
> maybe i better should post this on LQ, just tell me.
> As it seems that texlive will never be a stock slackware-package
> mostly because of its size, i wrote a script that should help
> maintaining a smaller texmf-tree.
> http://slackware.schoepfer.info/stuff/texmf_get.sh
> The approach is similar to the texlive-netinstaller, but the script
> has the advantage in the ability to add/exclude single tex-packages,
> not only schemes and collections, output is a tar.xz.
> Schemes/collections/packages may be mixed in the ADD/EXCLUDE
> variables inside the script.
> By using the excludes, it should be possible e.g. to provide a small 
> base-texlive-slackware-package with some additional tex-packages, and
> a further big(tetex?-scheme minus base-tex-packages) 
> texlive-slackware-package.
> Might this be of any use for the texlive-maintainers on this list?
> Feedback is welcome, thanks.


I'd be happy for you to take over the texlive SBo build and do
with it as you wish. I'm tired of trying to maintain that beast.

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

From slackbuilds at schoepfer.info  Tue Feb 23 06:25:34 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 23 Feb 2016 07:25:34 +0100
Subject: [Slackbuilds-users] Maintainable texlive texmf-tree
In-Reply-To: <20160222174820.3dd89b0c@home.rlworkman.net>
References: <da53af49db66309b9c159170dd3057f5@schoepfer.info>
 <20160222174820.3dd89b0c@home.rlworkman.net>
Message-ID: <56b0f227b96e19b0b8bee235297a6240@schoepfer.info>

> I'd be happy for you to take over the texlive SBo build and do
> with it as you wish. I'm tired of trying to maintain that beast.

Mhm, i'll think about it, i don't know if i can handle it.
How is the workflow? Checkout git, send git-diffs/patches to this list?


Regards

Franzen

From atelszewski at gmail.com  Tue Feb 23 11:51:27 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 23 Feb 2016 12:51:27 +0100
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56B49A1C.1060502@inlv.org>
References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org>
Message-ID: <56CC47BF.2010105@gmail.com>

On 05/02/16 13:48, Martijn Dekker wrote:
> 2. The following horrible, broken and obsolete eyesore:
>
> find -L . \
>   \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
>    -o -perm 511 \) -exec chmod 755 {} \; -o \
>   \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
>    -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
>
> can be replaced by:
>
>     chmod -R a-st,u+rwX,go-w+rX .

I advocate this solution.
Can we switch for it?
Or at least would the SlackBuild be accepted if I used this construct?

-- 
Best regards,
Andrzej Telszewski

From info at microlinux.fr  Tue Feb 23 12:01:53 2016
From: info at microlinux.fr (Nicolas Kovacs)
Date: Tue, 23 Feb 2016 13:01:53 +0100
Subject: [Slackbuilds-users] spice-gtk vs. usbredir
Message-ID: <56CC4A31.2000007@microlinux.fr>

Hi,

The spice-gtk package can use usbredir as an optional dependency,
according to the README on SBo. On the other hand, creating a virtual
machine spews out a "USB redirection support not compiled in" error in
virt-manager, so I suggest usbredir should be mandatory.

What's your take on this?

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

From atelszewski at gmail.com  Tue Feb 23 12:05:39 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 23 Feb 2016 13:05:39 +0100
Subject: [Slackbuilds-users] Source code hosting offer
Message-ID: <56CC4B13.9070705@gmail.com>

Hi,

Some SlackBuilds require the source code in the form of svn/git/etc. 
checkout repackaged in tarball.

For that purpose I was once (ab)using Ponce's kindly provided 
support/disk space.
Since I now have my own server/hosting, I can do the same, that is 
provide my space to interested people.

Just drop me an e-mail.

-- 
Best regards,
Andrzej Telszewski

From slackbuilds at schoepfer.info  Tue Feb 23 12:17:50 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 23 Feb 2016 13:17:50 +0100
Subject: [Slackbuilds-users] Source code hosting offer
In-Reply-To: <56CC4B13.9070705@gmail.com>
References: <56CC4B13.9070705@gmail.com>
Message-ID: <56CC4DEE.3000205@schoepfer.info>

Hi,

> Some SlackBuilds require the source code in the form of svn/git/etc.
> checkout repackaged in tarball.
>
> For that purpose I was once (ab)using Ponce's kindly provided
> support/disk space.
> Since I now have my own server/hosting, I can do the same, that is
> provide my space to interested people.

Is there a policy where those tarballs should be hostet?
If i take over texlive, i'll have to provide custom texmf-tarballs at 
about 2Gb, which i could do on my own server.

Regards

Franzen

From didier at slint.fr  Tue Feb 23 12:56:20 2016
From: didier at slint.fr (Didier Spaier)
Date: Tue, 23 Feb 2016 13:56:20 +0100
Subject: [Slackbuilds-users] Source code hosting offer
In-Reply-To: <56CC4B13.9070705@gmail.com>
References: <56CC4B13.9070705@gmail.com>
Message-ID: <56CC56F4.3070007@slint.fr>

/02/2016 13:05, Andrzej Telszewski wrote:
> Some SlackBuilds require the source code in the form of svn/git/etc.
> checkout repackaged in tarball.
>
> For that purpose I was once (ab)using Ponce's kindly provided
> support/disk space.
> Since I now have my own server/hosting, I can do the same, that is
> provide my space to interested people.

Maybe http://slackware.org.uk/sbosrcarch/ could be used instead?

Nice of you to offer that possibility. However IMHO if possible it would
be preferable to have all source archives in the same place. Here is the
initial announce by B. Watson:
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-October/015081.html

From atelszewski at gmail.com  Tue Feb 23 13:01:20 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 23 Feb 2016 14:01:20 +0100
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56CC47BF.2010105@gmail.com>
References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org>
 <56CC47BF.2010105@gmail.com>
Message-ID: <56CC5820.2060400@gmail.com>

On 23/02/16 12:51, Andrzej Telszewski wrote:
> On 05/02/16 13:48, Martijn Dekker wrote:
>> 2. The following horrible, broken and obsolete eyesore:
>>
>> find -L . \
>>   \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
>>    -o -perm 511 \) -exec chmod 755 {} \; -o \
>>   \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
>>    -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
>>
>> can be replaced by:
>>
>>     chmod -R a-st,u+rwX,go-w+rX .
>
> I advocate this solution.
> Can we switch for it?
> Or at least would the SlackBuild be accepted if I used this construct?
>

For the moment I was worried about what is going to happen with symbolic 
links, man page to the rescue:

"chmod never changes the permissions of symbolic links; the chmod system 
call cannot change their permissions. This is not a problem since the 
permissions of symbolic links are never used. However, for each symbolic 
link listed on the command line, chmod changes the permissions of the 
pointed-to file. *In contrast, chmod ignores symbolic links encountered 
during recursive directory traversals.*"

Tested, works as expected.

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Tue Feb 23 13:05:47 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 23 Feb 2016 14:05:47 +0100
Subject: [Slackbuilds-users] Source code hosting offer
In-Reply-To: <56CC56F4.3070007@slint.fr>
References: <56CC4B13.9070705@gmail.com> <56CC56F4.3070007@slint.fr>
Message-ID: <56CC592B.6070403@gmail.com>

On 23/02/16 13:56, Didier Spaier wrote:
> /02/2016 13:05, Andrzej Telszewski wrote:
>> Some SlackBuilds require the source code in the form of svn/git/etc.
>> checkout repackaged in tarball.
>>
>> For that purpose I was once (ab)using Ponce's kindly provided
>> support/disk space.
>> Since I now have my own server/hosting, I can do the same, that is
>> provide my space to interested people.
>
> Maybe http://slackware.org.uk/sbosrcarch/ could be used instead?
>
> Nice of you to offer that possibility. However IMHO if possible it would
> be preferable to have all source archives in the same place. Here is the
> initial announce by B. Watson:
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-October/015081.html

Could be an option. The only thing I'm worried about is not to overload 
the maintainer. I've been thinking about a bit of PHP scripting, that 
would allow people to add the tarballs themselves.

> _______________________________________________
> 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 dave at dawoodfall.net  Tue Feb 23 14:36:28 2016
From: dave at dawoodfall.net (David Woodfall)
Date: Tue, 23 Feb 2016 14:36:28 +0000
Subject: [Slackbuilds-users] Lost in the ether: lomoco and xforge
Message-ID: <20160223143628.GP14514@Blackswan>

I've just had a look to see if any sources are missing/moved and have
found the following missing:

system/lomoco 1.0
audio/xforge 0.2.2

(That's xforge the audio editor, not the xml generator).

If anyone has the sources for these available, please let me know,
otherwise they can be dropped.

Thanks

-D

From matteo.bernardini at gmail.com  Tue Feb 23 14:42:39 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 23 Feb 2016 15:42:39 +0100
Subject: [Slackbuilds-users] spice-gtk vs. usbredir
In-Reply-To: <56CC4A31.2000007@microlinux.fr>
References: <56CC4A31.2000007@microlinux.fr>
Message-ID: <CAPsDuS55ngKaYH78z3=y7hZJR60nTHoO5y3QdjCtrU=_9WcwhQ@mail.gmail.com>

2016-02-23 13:01 GMT+01:00 Nicolas Kovacs <info at microlinux.fr>:
> Hi,
>
> The spice-gtk package can use usbredir as an optional dependency,
> according to the README on SBo. On the other hand, creating a virtual
> machine spews out a "USB redirection support not compiled in" error in
> virt-manager, so I suggest usbredir should be mandatory.
>
> What's your take on this?

could it be you got that message because you have built usbredir
support in other components of the virt-manager stack?
I haven't tried it myself but I suppose you shouldn't have that
message if you build the stack from scratch withut usbredir at all...

Matteo

From matteo.bernardini at gmail.com  Tue Feb 23 14:47:21 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 23 Feb 2016 15:47:21 +0100
Subject: [Slackbuilds-users] Lost in the ether: lomoco and xforge
In-Reply-To: <20160223143628.GP14514@Blackswan>
References: <20160223143628.GP14514@Blackswan>
Message-ID: <CAPsDuS4Ram_2XCXf+uzgemV13mPBq4yUcQP1kETkS1FRSjKq4g@mail.gmail.com>

I uploaded a copy on my server and I'll update the links in git

http://ponce.cc/slackware/sources/repo/lomoco-1.0.tar.gz
http://ponce.cc/slackware/sources/repo/xforge-0.2.2.tar.gz

Matteo

From willysr at slackbuilds.org  Tue Feb 23 19:24:34 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 24 Feb 2016 02:24:34 +0700
Subject: [Slackbuilds-users] Source code hosting offer
In-Reply-To: <56CC4B13.9070705@gmail.com>
References: <56CC4B13.9070705@gmail.com>
Message-ID: <56CCB1F2.1050703@slackbuilds.org>

> Some SlackBuilds require the source code in the form of svn/git/etc.
> checkout repackaged in tarball.
> 
> For that purpose I was once (ab)using Ponce's kindly provided
> support/disk space.
> Since I now have my own server/hosting, I can do the same, that is
> provide my space to interested people.

there's another option for hosting the source code in sourceforge.net
Ryan has created a project for us to host the source code there

https://sourceforge.net/projects/slackbuildsdirectlinks/

if you need to host it there, drop him an email along with your SF
account name and he will add you to the contributor list

-- 
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/20160224/2a5c9ebb/attachment.asc>

From ryan.q at linux.com  Tue Feb 23 19:26:54 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Tue, 23 Feb 2016 19:26:54 +0000
Subject: [Slackbuilds-users] Source code hosting offer
In-Reply-To: <56CCB1F2.1050703@slackbuilds.org>
References: <56CC4B13.9070705@gmail.com> <56CCB1F2.1050703@slackbuilds.org>
Message-ID: <CAAcyf-pVhYRPMC=yRa474j4Y1shuXMBOpMPm9jO9c1fDH7_fPA@mail.gmail.com>

On Tue, Feb 23, 2016 at 11:24 AM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > Some SlackBuilds require the source code in the form of svn/git/etc.
> > checkout repackaged in tarball.
> >
> > For that purpose I was once (ab)using Ponce's kindly provided
> > support/disk space.
> > Since I now have my own server/hosting, I can do the same, that is
> > provide my space to interested people.
>
> there's another option for hosting the source code in sourceforge.net
> Ryan has created a project for us to host the source code there
>
> https://sourceforge.net/projects/slackbuildsdirectlinks/
>
> if you need to host it there, drop him an email along with your SF
> account name and he will add you to the contributor list
>


Thanks Willy for mentioning it! All are welcome to contribute, it seems to
have worked pretty well so far.  :^)

It would be great if Andrzej would mirror the sbosrcarch though (can't have
enough mirrors).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160223/ab3506aa/attachment-0001.html>

From dave at dawoodfall.net  Tue Feb 23 20:17:16 2016
From: dave at dawoodfall.net (David Woodfall)
Date: Tue, 23 Feb 2016 20:17:16 +0000
Subject: [Slackbuilds-users] Lost in the ether: lomoco and xforge
In-Reply-To: <CAPsDuS4Ram_2XCXf+uzgemV13mPBq4yUcQP1kETkS1FRSjKq4g@mail.gmail.com>
References: <20160223143628.GP14514@Blackswan>
 <CAPsDuS4Ram_2XCXf+uzgemV13mPBq4yUcQP1kETkS1FRSjKq4g@mail.gmail.com>
Message-ID: <20160223201716.GQ14514@Blackswan>

>I uploaded a copy on my server and I'll update the links in git
>
>http://ponce.cc/slackware/sources/repo/lomoco-1.0.tar.gz
>http://ponce.cc/slackware/sources/repo/xforge-0.2.2.tar.gz
>
>Matteo

Thanks, Matteo

From info at microlinux.fr  Tue Feb 23 20:17:45 2016
From: info at microlinux.fr (Nicolas Kovacs)
Date: Tue, 23 Feb 2016 21:17:45 +0100
Subject: [Slackbuilds-users] spice-gtk vs. usbredir
In-Reply-To: <CAPsDuS55ngKaYH78z3=y7hZJR60nTHoO5y3QdjCtrU=_9WcwhQ@mail.gmail.com>
References: <56CC4A31.2000007@microlinux.fr>
 <CAPsDuS55ngKaYH78z3=y7hZJR60nTHoO5y3QdjCtrU=_9WcwhQ@mail.gmail.com>
Message-ID: <56CCBE69.8010703@microlinux.fr>

Le 23/02/2016 15:42, Matteo Bernardini a ?crit :
> could it be you got that message because you have built usbredir
> support in other components of the virt-manager stack?

Indeed, I built qemu against it.

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

From atelszewski at gmail.com  Tue Feb 23 20:53:08 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 23 Feb 2016 21:53:08 +0100
Subject: [Slackbuilds-users] Source code hosting offer
In-Reply-To: <CAAcyf-pVhYRPMC=yRa474j4Y1shuXMBOpMPm9jO9c1fDH7_fPA@mail.gmail.com>
References: <56CC4B13.9070705@gmail.com> <56CCB1F2.1050703@slackbuilds.org>
 <CAAcyf-pVhYRPMC=yRa474j4Y1shuXMBOpMPm9jO9c1fDH7_fPA@mail.gmail.com>
Message-ID: <56CCC6B4.7050806@gmail.com>

On 23/02/16 20:26, Ryan P.C. McQuen wrote:
> It would be great if Andrzej would mirror the sbosrcarch though (can't
> have enough mirrors).

Is rsync an option?

-- 
Best regards,
Andrzej Telszewski

From miguel at thedeanda.com  Wed Feb 24 00:39:17 2016
From: miguel at thedeanda.com (Miguel De Anda)
Date: Tue, 23 Feb 2016 16:39:17 -0800
Subject: [Slackbuilds-users] ffmpeg updates
In-Reply-To: <56CB4F23.5010803@slackbuilds.org>
References: <56CB4F23.5010803@slackbuilds.org>
Message-ID: <CAA62KfR3RJ-=LEtA3gWBJfa891KH6hUSdgcU+DBakWKA7j92gw@mail.gmail.com>

i started trying to build ffmpeg and as many dependencies as possible
from what's on the website first before trying the newer one but i ran
into issues. i was building this against a new install (about 2 weeks
old) running all current and no 32-bit compat. libs using sbopkg:

sbopkg -i libaacs
...
--2016-02-23 16:19:15--
ftp://ftp.videolan.org/pub/videolan/libaacs/0.8.1/libaacs-0.8.1.tar.bz2
           => 'libaacs-0.8.1.tar.bz2'
Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2,
2a01:e0d:1:3:58bf:fa02:c0de:20
Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /pub/videolan/libaacs/0.8.1 ... done.
==> SIZE libaacs-0.8.1.tar.bz2 ... 315231
==> PASV ... couldn't connect to 127.0.1.1 port 62389: Connection refused




sbopkg -i decklink-sdk

Found Blackmagic_DeckLink_SDK_10.1.4.zip in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for Blackmagic_DeckLink_SDK_10.1.4.zip ... FAILED!
    Expected: 16fbc2f49dc62fecac15835c538f78d4
    Found:    561847ddc4780f347fbd0ee076573a98


using the downloaded source results in...


Do you want to use the downloaded decklink-sdk source:
Blackmagic_DeckLink_SDK_10.1.4.zip in /var/cache/sbopkg?

You can choose among the following options:
 - (Y)es, keep the source and continue the build process;
 - (N)o, delete the source and abort the build process; or
 - (R)etry download and continue the build process.

(Y)es, (N)o, (R)etry?: y
    Keeping the source and continuing.
Building package for decklink-sdk...
Archive:  /var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of
/var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip
or
        /var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip.zip,
and cannot find
/var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip.ZIP,
period.





sbopkg -i libvpx

...
    [CXX] third_party/googletest/src/src/gtest-all.cc.o
    [AR] libgtest_g.a
    [STRIP] libgtest.a < libgtest_g.a
    [CC] test/../md5_utils.c.o
    [CC] test/../nestegg/halloc/src/halloc.c.o
In file included from ../test/../nestegg/halloc/src/halloc.c:19:0:
../test/../nestegg/halloc/src/align.h:33:25: error: conflicting types
for 'max_align_t'
 typedef union max_align max_align_t;
                         ^
In file included from ../test/../nestegg/halloc/src/../halloc.h:18:0,
                 from ../test/../nestegg/halloc/src/halloc.c:18:
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/include/stddef.h:429:3:
note: previous declaration of 'max_align_t' was here
 } max_align_t;
   ^
Makefile:128: recipe for target 'test/../nestegg/halloc/src/halloc.c.o' failed
make[1]: *** [test/../nestegg/halloc/src/halloc.c.o] Error 1
Makefile:17: recipe for target '.DEFAULT' failed
make: *** [.DEFAULT] Error 2





sbopkg -i libbdplus

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




sbopkg -i libbluray

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






sbopkg -i graphviz


Making all in webp
make[3]: Entering directory '/tmp/SBo/graphviz-2.38.0/plugin/webp'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin/webp'
Making all in poppler
make[3]: Entering directory '/tmp/SBo/graphviz-2.38.0/plugin/poppler'
  CC       gvplugin_poppler.lo
  CC       gvloadimage_poppler.lo
  CCLD     libgvplugin_poppler_C.la
  CCLD     libgvplugin_poppler.la
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld:
cannot find -lopenjp2
collect2: error: ld returned 1 exit status
Makefile:665: recipe for target 'libgvplugin_poppler.la' failed
make[3]: *** [libgvplugin_poppler.la] Error 1
make[3]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin/poppler'
Makefile:531: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin'
Makefile:774: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/graphviz-2.38.0'
Makefile:583: recipe for target 'all' failed
make: *** [all] Error 2



i'm not sure if the network errors are something specific to my
network setup. its a bit odd that it tries to resolve to 127.0.1.1
though. does anybody else have issues building any of these?

On Mon, Feb 22, 2016 at 10:10 AM, Willy Sudiarto Raharjo
<willysr at slackbuilds.org> wrote:
> I have just merged all changes during the last few days back to master
> and it includes ffmpeg updates to 2.8.x branch.
>
> there are a lot of packages depends on ffmpeg and we need your help to
> confirm if those packages are built properly against ffmpeg 2.8.
>
> please let us know if there are problems and even better, send us the
> patches or fixes to it.
>
> most of the entries in the previous BUILD FAILURE list has been fixed
> and these are the remaining broken packages
>
>   audio/ardour
>   audio/azr3
>   audio/guitarix
>   development/monodevelop
>   development/phantomjs
>   games/foobillardplus
>   games/jfsw
>   games/singularity
>   games/unvanquished
>   haskell/haskell-platform
>   libraries/ggz-base-libs
>   multimedia/cantata
>   network/mosaic-ck
>   network/retroshare
>   network/smstools3
>   network/sockstress
>
> happy testing :)
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> 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  Wed Feb 24 00:48:02 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 24 Feb 2016 07:48:02 +0700
Subject: [Slackbuilds-users] ffmpeg updates
In-Reply-To: <CAA62KfR3RJ-=LEtA3gWBJfa891KH6hUSdgcU+DBakWKA7j92gw@mail.gmail.com>
References: <56CB4F23.5010803@slackbuilds.org>
 <CAA62KfR3RJ-=LEtA3gWBJfa891KH6hUSdgcU+DBakWKA7j92gw@mail.gmail.com>
Message-ID: <56CCFDC2.8060305@slackbuilds.org>

> sbopkg -i libaacs
> ...
> --2016-02-23 16:19:15--
> ftp://ftp.videolan.org/pub/videolan/libaacs/0.8.1/libaacs-0.8.1.tar.bz2
>            => 'libaacs-0.8.1.tar.bz2'
> Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2,
> 2a01:e0d:1:3:58bf:fa02:c0de:20
> Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:21... connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done.    ==> PWD ... done.
> ==> TYPE I ... done.  ==> CWD (1) /pub/videolan/libaacs/0.8.1 ... done.
> ==> SIZE libaacs-0.8.1.tar.bz2 ... 315231
> ==> PASV ... couldn't connect to 127.0.1.1 port 62389: Connection refused
> 
> 
> 
> 
> sbopkg -i decklink-sdk
> 
> Found Blackmagic_DeckLink_SDK_10.1.4.zip in /var/cache/sbopkg.
> Checking MD5SUM:
>   MD5SUM check for Blackmagic_DeckLink_SDK_10.1.4.zip ... FAILED!
>     Expected: 16fbc2f49dc62fecac15835c538f78d4
>     Found:    561847ddc4780f347fbd0ee076573a98
> 
> 
> using the downloaded source results in...
> 
> 
> Do you want to use the downloaded decklink-sdk source:
> Blackmagic_DeckLink_SDK_10.1.4.zip in /var/cache/sbopkg?
> 
> You can choose among the following options:
>  - (Y)es, keep the source and continue the build process;
>  - (N)o, delete the source and abort the build process; or
>  - (R)etry download and continue the build process.
> 
> (Y)es, (N)o, (R)etry?: y
>     Keeping the source and continuing.
> Building package for decklink-sdk...
> Archive:  /var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip
>   End-of-central-directory signature not found.  Either this file is not
>   a zipfile, or it constitutes one disk of a multi-part archive.  In the
>   latter case the central directory and zipfile comment will be found on
>   the last disk(s) of this archive.
> unzip:  cannot find zipfile directory in one of
> /var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip
> or
>         /var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip.zip,
> and cannot find
> /var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip.ZIP,
> period.
> 
> 
> 
> 
> 
> sbopkg -i libvpx
> 
> ...
>     [CXX] third_party/googletest/src/src/gtest-all.cc.o
>     [AR] libgtest_g.a
>     [STRIP] libgtest.a < libgtest_g.a
>     [CC] test/../md5_utils.c.o
>     [CC] test/../nestegg/halloc/src/halloc.c.o
> In file included from ../test/../nestegg/halloc/src/halloc.c:19:0:
> ../test/../nestegg/halloc/src/align.h:33:25: error: conflicting types
> for 'max_align_t'
>  typedef union max_align max_align_t;
>                          ^
> In file included from ../test/../nestegg/halloc/src/../halloc.h:18:0,
>                  from ../test/../nestegg/halloc/src/halloc.c:18:
> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/include/stddef.h:429:3:
> note: previous declaration of 'max_align_t' was here
>  } max_align_t;
>    ^
> Makefile:128: recipe for target 'test/../nestegg/halloc/src/halloc.c.o' failed
> make[1]: *** [test/../nestegg/halloc/src/halloc.c.o] Error 1
> Makefile:17: recipe for target '.DEFAULT' failed
> make: *** [.DEFAULT] Error 2


> sbopkg -i libbdplus
> 
> libbdplus not found in /var/cache/sbopkg.
> --2016-02-23 16:29:52--
> ftp://ftp.videolan.org/pub/videolan/libbdplus/0.1.2/libbdplus-0.1.2.tar.bz2
>            => 'libbdplus-0.1.2.tar.bz2'
> Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2,
> 2a01:e0d:1:3:58bf:fa02:c0de:20
> Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:21... connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done.    ==> PWD ... done.
> ==> TYPE I ... done.  ==> CWD (1) /pub/videolan/libbdplus/0.1.2 ... done.
> ==> SIZE libbdplus-0.1.2.tar.bz2 ... 319828
> ==> PASV ... couldn't connect to 127.0.1.1 port 62758: Connection refused
> 
> 
> 
> 
> sbopkg -i libbluray
> 
> libbluray not found in /var/cache/sbopkg.
> --2016-02-23 16:30:51--
> ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
>            => 'libbluray-0.9.2.tar.bz2'
> Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2,
> 2a01:e0d:1:3:58bf:fa02:c0de:20
> Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:21... connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done.    ==> PWD ... done.
> ==> TYPE I ... done.  ==> CWD (1) /pub/videolan/libbluray/0.9.2 ... done.
> ==> SIZE libbluray-0.9.2.tar.bz2 ... 704357
> ==> PASV ... couldn't connect to 127.0.1.1 port 62226: Connection refused
> 
> 
> 
> 
> 
> 
> sbopkg -i graphviz
> 
> 
> Making all in webp
> make[3]: Entering directory '/tmp/SBo/graphviz-2.38.0/plugin/webp'
> make[3]: Nothing to be done for 'all'.
> make[3]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin/webp'
> Making all in poppler
> make[3]: Entering directory '/tmp/SBo/graphviz-2.38.0/plugin/poppler'
>   CC       gvplugin_poppler.lo
>   CC       gvloadimage_poppler.lo
>   CCLD     libgvplugin_poppler_C.la
>   CCLD     libgvplugin_poppler.la
> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld:
> cannot find -lopenjp2
> collect2: error: ld returned 1 exit status
> Makefile:665: recipe for target 'libgvplugin_poppler.la' failed
> make[3]: *** [libgvplugin_poppler.la] Error 1
> make[3]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin/poppler'
> Makefile:531: recipe for target 'all-recursive' failed
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin'
> Makefile:774: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/tmp/SBo/graphviz-2.38.0'
> Makefile:583: recipe for target 'all' failed
> make: *** [all] Error 2

the videolan links are not really stable at the moment

about graphviz, David has a fix and it has been merged to master
https://slackbuilds.org/cgit/slackbuilds/commit/?id=62797bab131631b7af36f3d3d7856b90a12ef042

i will check on libvpx and decklink-sdk later

-- 
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/20160224/baf29955/attachment.asc>

From chris.willing at iinet.net.au  Wed Feb 24 02:14:47 2016
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Wed, 24 Feb 2016 12:14:47 +1000
Subject: [Slackbuilds-users] ffmpeg updates
In-Reply-To: <CAA62KfR3RJ-=LEtA3gWBJfa891KH6hUSdgcU+DBakWKA7j92gw@mail.gmail.com>
References: <56CB4F23.5010803@slackbuilds.org>
 <CAA62KfR3RJ-=LEtA3gWBJfa891KH6hUSdgcU+DBakWKA7j92gw@mail.gmail.com>
Message-ID: <56CD1217.80301@iinet.net.au>

On 24/02/16 10:39, Miguel De Anda wrote:
> i started trying to build ffmpeg and as many dependencies as possible
> from what's on the website first before trying the newer one but i ran
> into issues. i was building this against a new install (about 2 weeks
> old) running all current and no 32-bit compat. libs using sbopkg:
...
>
> sbopkg -i decklink-sdk
>
> Found Blackmagic_DeckLink_SDK_10.1.4.zip in /var/cache/sbopkg.
> Checking MD5SUM:
>    MD5SUM check for Blackmagic_DeckLink_SDK_10.1.4.zip ... FAILED!
>      Expected: 16fbc2f49dc62fecac15835c538f78d4
>      Found:    561847ddc4780f347fbd0ee076573a98
>
>
> using the downloaded source results in...
>
>
> Do you want to use the downloaded decklink-sdk source:
> Blackmagic_DeckLink_SDK_10.1.4.zip in /var/cache/sbopkg?
>
> You can choose among the following options:
>   - (Y)es, keep the source and continue the build process;
>   - (N)o, delete the source and abort the build process; or
>   - (R)etry download and continue the build process.
>
> (Y)es, (N)o, (R)etry?: y
>      Keeping the source and continuing.
> Building package for decklink-sdk...
> Archive:  /var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip
>    End-of-central-directory signature not found.  Either this file is not
>    a zipfile, or it constitutes one disk of a multi-part archive.  In the
>    latter case the central directory and zipfile comment will be found on
>    the last disk(s) of this archive.
> unzip:  cannot find zipfile directory in one of
> /var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip
> or
>          /var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip.zip,
> and cannot find
> /var/lib/sbopkg/SBo/14.1/development/decklink-sdk/Blackmagic_DeckLink_SDK_10.1.4.zip.ZIP,
> period.
>

Unfortunately Blackmagic Design company has changed their download 
mechanism to use only a web page that requires name & email details of 
the downloader; then issues some sort of download authority so that wget 
could be used. However that authority it is time limited, so not worth 
adding that to the .info file.

It has been that way for a while for newer versions and I held the 
version back at 10.1.4 purely because it was still directly 
downloadable. Looks like they've eventually realised and closed that 
loophole.


This is, more or less, the same situation as the SlackBuild for jdk; the 
DOWNLOAD file must be downloaded separately first.

An alternative would be to host the download file somewhere else like 
slackbuildsdirectlinks but there may be legal implications to consider. 
Any insights welcome ...

chris


From z.coldplayer at gmail.com  Wed Feb 24 06:28:40 2016
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Wed, 24 Feb 2016 10:28:40 +0400
Subject: [Slackbuilds-users] libbluray cannot be downloaded using wget
Message-ID: <CAEWL1__N6fTzSP5yTmmhPjq0-XO05qSSfH1nzAjBFV_AQosEkA@mail.gmail.com>

Hi, usually slackbuilds downloads stuffs using wget.

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


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


But using curl , I was able to download libbluray.

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


I'm using slackware-current.

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

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

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

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

Originally written by Hrvoje Niksic <hniksic at xemacs.org>.
Please send bug reports and questions to <bug-wget at gnu.org>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160224/99bf5dbe/attachment.html>

From matteo.bernardini at gmail.com  Wed Feb 24 06:34:19 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 24 Feb 2016 07:34:19 +0100
Subject: [Slackbuilds-users] libbluray cannot be downloaded using wget
In-Reply-To: <CAEWL1__N6fTzSP5yTmmhPjq0-XO05qSSfH1nzAjBFV_AQosEkA@mail.gmail.com>
References: <CAEWL1__N6fTzSP5yTmmhPjq0-XO05qSSfH1nzAjBFV_AQosEkA@mail.gmail.com>
Message-ID: <CAPsDuS4FH3q8q-2s5M5=bA2W0ujH0Eq=ZECNpveJRh6Q2=cgpA@mail.gmail.com>

2016-02-24 7:28 GMT+01:00 Jheengut Pritvi <z.coldplayer at gmail.com>:
> Hi, usually slackbuilds downloads stuffs using wget.
>
> I'm building the package libbluray but I'm getting the following error ::
>
>
> libbluray:
> libbluray not found in /var/cache/sbopkg.
> --2016-02-22 10:24:52--
> ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
>            => 'libbluray-0.9.2.tar.bz2'
> Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2,
> 2a01:e0d:1:3:58bf:fa02:c0de:20
> Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:21...
> connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done.    ==> PWD ... done.
> ==> TYPE I ... done.  ==> CWD (1) /pub/videolan/libbluray/0.9.2 ... done.
> ==> SIZE libbluray-0.9.2.tar.bz2 ... 704357
> ==> PASV ... couldn't connect to 127.0.1.1 port 62782: Connection refused
>
>
> But using curl , I was able to download libbluray.
>
> curl
> ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
>>libbluray-0.9.2.tar.bz2
>   % Total    % Received % Xferd  Average Speed   Time    Time     Time
> Current
>                                  Dload  Upload   Total   Spent    Left
> Speed
> 100  687k  100  687k    0     0  47257      0  0:00:14  0:00:14 --:--:--
> 96258
>
>
> I'm using slackware-current.
>
> wget --version
> GNU Wget 1.14 built on linux-gnu.
>
> +digest +https +ipv6 +iri +large-file +nls +ntlm +opie +ssl/openssl
>
> Wgetrc:
>     /etc/wgetrc (system)
> Locale: /usr/share/locale
> Compile: gcc -DHAVE_CONFIG_H -DSYSTEM_WGETRC="/etc/wgetrc"
>     -DLOCALEDIR="/usr/share/locale" -I. -I../lib -I../lib -O2 -fPIC
> Link: gcc -O2 -fPIC -lssl -lcrypto -lz -ldl -lz -lz -lidn -luuid -lpcre
>     ftp-opie.o openssl.o http-ntlm.o ../lib/libgnu.a
>
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://www.gnu.org/licenses/gpl.html>.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Originally written by Hrvoje Niksic <hniksic at xemacs.org>.
> Please send bug reports and questions to <bug-wget at gnu.org>.

looks like a momentary problem with ftp.videolan.org via ftp (the same
address via http works), in previous mailing list messages of a few
hours ago others reported similar issues...
most probably it will be fixed soon (days?), if not maybe the less
invasive solution is to change the download links pointing to http.

Matteo

From elyk03 at gmail.com  Wed Feb 24 06:37:05 2016
From: elyk03 at gmail.com (Kyle Guinn)
Date: Wed, 24 Feb 2016 00:37:05 -0600
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56CC47BF.2010105@gmail.com>
References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org>
 <56CC47BF.2010105@gmail.com>
Message-ID: <CAJCpn81XMh6f43fDU3K00rcb=PB4f=9CqMvCxi0zje4v5+6_7g@mail.gmail.com>

On 2/23/16, Andrzej Telszewski <atelszewski at gmail.com> wrote:
> On 05/02/16 13:48, Martijn Dekker wrote:
>> 2. The following horrible, broken and obsolete eyesore:
>>
>> find -L . \
>>   \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
>>    -o -perm 511 \) -exec chmod 755 {} \; -o \
>>   \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
>>    -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
>>
>> can be replaced by:
>>
>>     chmod -R a-st,u+rwX,go-w+rX .
>
> I advocate this solution.
> Can we switch for it?
> Or at least would the SlackBuild be accepted if I used this construct?

Even shorter and simpler to understand:
chmod -R u+w,go-w,a+rX-st .

-Kyle

From atelszewski at gmail.com  Wed Feb 24 07:22:43 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 24 Feb 2016 08:22:43 +0100
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <CAJCpn81XMh6f43fDU3K00rcb=PB4f=9CqMvCxi0zje4v5+6_7g@mail.gmail.com>
References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org>
 <56CC47BF.2010105@gmail.com>
 <CAJCpn81XMh6f43fDU3K00rcb=PB4f=9CqMvCxi0zje4v5+6_7g@mail.gmail.com>
Message-ID: <56CD5A43.5040402@gmail.com>

On 24/02/16 07:37, Kyle Guinn wrote:
> On 2/23/16, Andrzej Telszewski <atelszewski at gmail.com> wrote:
>> On 05/02/16 13:48, Martijn Dekker wrote:
>>> 2. The following horrible, broken and obsolete eyesore:
>>>
>>> find -L . \
>>>    \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
>>>     -o -perm 511 \) -exec chmod 755 {} \; -o \
>>>    \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
>>>     -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
>>>
>>> can be replaced by:
>>>
>>>      chmod -R a-st,u+rwX,go-w+rX .
>>
>> I advocate this solution.
>> Can we switch for it?
>> Or at least would the SlackBuild be accepted if I used this construct?
>
> Even shorter and simpler to understand:
> chmod -R u+w,go-w,a+rX-st .
>

Yep, even nicer ;)

> -Kyle
> _______________________________________________
> 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  Wed Feb 24 07:54:26 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 24 Feb 2016 14:54:26 +0700
Subject: [Slackbuilds-users] libbluray cannot be downloaded using wget
In-Reply-To: <CAEWL1__N6fTzSP5yTmmhPjq0-XO05qSSfH1nzAjBFV_AQosEkA@mail.gmail.com>
References: <CAEWL1__N6fTzSP5yTmmhPjq0-XO05qSSfH1nzAjBFV_AQosEkA@mail.gmail.com>
Message-ID: <56CD61B2.1050106@slackbuilds.org>

> I'm building the package libbluray but I'm getting the following error ::
> 
> 
> libbluray:
> libbluray not found in /var/cache/sbopkg.
> --2016-02-22 10:24:52--
> ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
>            => 'libbluray-0.9.2.tar.bz2'
> Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2,

works fine here

willysr at laptop:~]$ wget
http://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
--2016-02-24 14:53:41--
http://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2,
2a01:e0d:1:3:58bf:fa02:c0de:20
Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 704357 (688K) [application/octet-stream]
Saving to: ?libbluray-0.9.2.tar.bz2?


-- 
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/20160224/e4f7c40d/attachment.asc>

From willysr at slackbuilds.org  Wed Feb 24 07:56:42 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 24 Feb 2016 14:56:42 +0700
Subject: [Slackbuilds-users] libbluray cannot be downloaded using wget
In-Reply-To: <56CD61B2.1050106@slackbuilds.org>
References: <CAEWL1__N6fTzSP5yTmmhPjq0-XO05qSSfH1nzAjBFV_AQosEkA@mail.gmail.com>
 <56CD61B2.1050106@slackbuilds.org>
Message-ID: <56CD623A.4050500@slackbuilds.org>

>> I'm building the package libbluray but I'm getting the following error ::
>>
>>
>> libbluray:
>> libbluray not found in /var/cache/sbopkg.
>> --2016-02-22 10:24:52--
>> ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
>>            => 'libbluray-0.9.2.tar.bz2'
>> Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2,
> 
> works fine here

I updated the URL around 41h (almost 2 days) ago, so you probably
haven't sync your repository to use the latest one in master branch

https://slackbuilds.org/cgit/slackbuilds/commit/?id=0bc80d553dcec7d14c2c2ec8efe2d6aec5f76840


-- 
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/20160224/46e80c2b/attachment.asc>

From lems at gmx.net  Wed Feb 24 08:58:48 2016
From: lems at gmx.net (Leonard Schmidt)
Date: Wed, 24 Feb 2016 09:58:48 +0100
Subject: [Slackbuilds-users] git master: check.info lists old version
Message-ID: <0Lbujs-1a771i0G5k-00jHxI@mail.gmx.com>

Hello,

I cloned the latest git slackbuilds tree, and noticed that
development/check has been updated to 0.10.0, but check.info
contains:
VERSION=0.9.10

Leonard

From willysr at slackbuilds.org  Wed Feb 24 09:45:09 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 24 Feb 2016 16:45:09 +0700
Subject: [Slackbuilds-users] git master: check.info lists old version
In-Reply-To: <0Lbujs-1a771i0G5k-00jHxI@mail.gmx.com>
References: <0Lbujs-1a771i0G5k-00jHxI@mail.gmx.com>
Message-ID: <56CD7BA5.2080204@slackbuilds.org>

> I cloned the latest git slackbuilds tree, and noticed that
> development/check has been updated to 0.10.0, but check.info
> contains:
> VERSION=0.9.10

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/20160224/90037b67/attachment.asc>

From willysr at slackbuilds.org  Wed Feb 24 10:21:16 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 24 Feb 2016 17:21:16 +0700
Subject: [Slackbuilds-users] ffmpeg updates
In-Reply-To: <CAA62KfR3RJ-=LEtA3gWBJfa891KH6hUSdgcU+DBakWKA7j92gw@mail.gmail.com>
References: <56CB4F23.5010803@slackbuilds.org>
 <CAA62KfR3RJ-=LEtA3gWBJfa891KH6hUSdgcU+DBakWKA7j92gw@mail.gmail.com>
Message-ID: <56CD841C.2010605@slackbuilds.org>

> sbopkg -i libvpx
> 
> ...
>     [CXX] third_party/googletest/src/src/gtest-all.cc.o
>     [AR] libgtest_g.a
>     [STRIP] libgtest.a < libgtest_g.a
>     [CC] test/../md5_utils.c.o
>     [CC] test/../nestegg/halloc/src/halloc.c.o
> In file included from ../test/../nestegg/halloc/src/halloc.c:19:0:
> ../test/../nestegg/halloc/src/align.h:33:25: error: conflicting types
> for 'max_align_t'
>  typedef union max_align max_align_t;
>                          ^
> In file included from ../test/../nestegg/halloc/src/../halloc.h:18:0,
>                  from ../test/../nestegg/halloc/src/halloc.c:18:
> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/include/stddef.h:429:3:
> note: previous declaration of 'max_align_t' was here
>  } max_align_t;
>    ^
> Makefile:128: recipe for target 'test/../nestegg/halloc/src/halloc.c.o' failed
> make[1]: *** [test/../nestegg/halloc/src/halloc.c.o] Error 1
> Makefile:17: recipe for target '.DEFAULT' failed
> make: *** [.DEFAULT] Error 2

Hi Miguel

libvpx is now included in current, so we remove it on master
https://slackbuilds.org/cgit/slackbuilds/commit/?id=eb8b47aebd0456903dca8ab381b4ac2aa7b67048



-- 
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/20160224/8103c6b9/attachment.asc>

From willysr at slackbuilds.org  Wed Feb 24 10:32:23 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 24 Feb 2016 17:32:23 +0700
Subject: [Slackbuilds-users] ffmpeg updates
In-Reply-To: <CAA62KfR3RJ-=LEtA3gWBJfa891KH6hUSdgcU+DBakWKA7j92gw@mail.gmail.com>
References: <56CB4F23.5010803@slackbuilds.org>
 <CAA62KfR3RJ-=LEtA3gWBJfa891KH6hUSdgcU+DBakWKA7j92gw@mail.gmail.com>
Message-ID: <56CD86B7.7060102@slackbuilds.org>

> sbopkg -i graphviz
> 
> 
> Making all in webp
> make[3]: Entering directory '/tmp/SBo/graphviz-2.38.0/plugin/webp'
> make[3]: Nothing to be done for 'all'.
> make[3]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin/webp'
> Making all in poppler
> make[3]: Entering directory '/tmp/SBo/graphviz-2.38.0/plugin/poppler'
>   CC       gvplugin_poppler.lo
>   CC       gvloadimage_poppler.lo
>   CCLD     libgvplugin_poppler_C.la
>   CCLD     libgvplugin_poppler.la
> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld:
> cannot find -lopenjp2
> collect2: error: ld returned 1 exit status
> Makefile:665: recipe for target 'libgvplugin_poppler.la' failed
> make[3]: *** [libgvplugin_poppler.la] Error 1
> make[3]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin/poppler'
> Makefile:531: recipe for target 'all-recursive' failed
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin'
> Makefile:774: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/tmp/SBo/graphviz-2.38.0'
> Makefile:583: recipe for target 'all' failed
> make: *** [all] Error 2

tested with latest master branch and it's building fine here

Slackware package /tmp/graphviz-2.38.0-x86_64-1_SBo.tgz created.


-- 
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/20160224/27c67746/attachment.asc>

From info at microlinux.fr  Wed Feb 24 12:01:05 2016
From: info at microlinux.fr (Nicolas Kovacs)
Date: Wed, 24 Feb 2016 13:01:05 +0100
Subject: [Slackbuilds-users] libvirt: mistake in rc.libvirt
Message-ID: <56CD9B81.4050505@microlinux.fr>

Hi,

I've installed libvirt from SBo. I can build virtual machines OK and
everything seems to run fine. As far as I can tell, there's only one
small mistake in rc.libvirt.

As per the README, I added a little startup stanza to /etc/rc.d/rc.local:

# Start libvirt:
if [ -x /etc/rc.d/rc.libvirt ]; then
  /etc/rc.d/rc.libvirt start
fi

And the corresponding stanza in /etc/rc.d/rc.local_shutdown:

# Stop libvirt:
if [ -x /etc/rc.d/rc.libvirt ]; then
  /etc/rc.d/rc.libvirt stop
fi

Now when the machine shuts down (shutdown -h now), I get two error
messages concerning rc.libvirt. At the respective lines 29 and 40 of the
script, there's a "virsh: command not found" error.

Cheers,

Niki

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

From matteo.bernardini at gmail.com  Wed Feb 24 12:08:13 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 24 Feb 2016 13:08:13 +0100
Subject: [Slackbuilds-users] libvirt: mistake in rc.libvirt
In-Reply-To: <56CD9B81.4050505@microlinux.fr>
References: <56CD9B81.4050505@microlinux.fr>
Message-ID: <CAPsDuS4Do2qu6GQpoWfz6Mpe9H6F1N4x_EF5LE00BWN=iO33KQ@mail.gmail.com>

2016-02-24 13:01 GMT+01:00 Nicolas Kovacs <info at microlinux.fr>:
> Hi,
>
> I've installed libvirt from SBo. I can build virtual machines OK and
> everything seems to run fine. As far as I can tell, there's only one
> small mistake in rc.libvirt.
>
> As per the README, I added a little startup stanza to /etc/rc.d/rc.local:
>
> # Start libvirt:
> if [ -x /etc/rc.d/rc.libvirt ]; then
>   /etc/rc.d/rc.libvirt start
> fi
>
> And the corresponding stanza in /etc/rc.d/rc.local_shutdown:
>
> # Stop libvirt:
> if [ -x /etc/rc.d/rc.libvirt ]; then
>   /etc/rc.d/rc.libvirt stop
> fi
>
> Now when the machine shuts down (shutdown -h now), I get two error
> messages concerning rc.libvirt. At the respective lines 29 and 40 of the
> script, there's a "virsh: command not found" error.

hi Niki,

I fixed this in our git but when submission for 14.1 were already
closed: I simply changed all the occurences of "virsh" in rc.libvirt
with the absolute path, "/usr/sbin/virsh".

Matteo

From info at microlinux.fr  Wed Feb 24 12:11:47 2016
From: info at microlinux.fr (Nicolas Kovacs)
Date: Wed, 24 Feb 2016 13:11:47 +0100
Subject: [Slackbuilds-users] libvirt: mistake in rc.libvirt
In-Reply-To: <CAPsDuS4Do2qu6GQpoWfz6Mpe9H6F1N4x_EF5LE00BWN=iO33KQ@mail.gmail.com>
References: <56CD9B81.4050505@microlinux.fr>
 <CAPsDuS4Do2qu6GQpoWfz6Mpe9H6F1N4x_EF5LE00BWN=iO33KQ@mail.gmail.com>
Message-ID: <56CD9E03.4050206@microlinux.fr>

Le 24/02/2016 13:08, Matteo Bernardini a ?crit :
> hi Niki,
> 
> I fixed this in our git but when submission for 14.1 were already
> closed: I simply changed all the occurences of "virsh" in rc.libvirt
> with the absolute path, "/usr/sbin/virsh".

Thanks Matteo !

And happy birthday to you !

Cheers,

Niki

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

From miguel at thedeanda.com  Wed Feb 24 12:46:13 2016
From: miguel at thedeanda.com (Miguel De Anda)
Date: Wed, 24 Feb 2016 04:46:13 -0800
Subject: [Slackbuilds-users] ffmpeg updates
In-Reply-To: <56CD86B7.7060102@slackbuilds.org>
References: <56CB4F23.5010803@slackbuilds.org>
 <CAA62KfR3RJ-=LEtA3gWBJfa891KH6hUSdgcU+DBakWKA7j92gw@mail.gmail.com>
 <56CD86B7.7060102@slackbuilds.org>
Message-ID: <CAA62KfRx8Lm=X50rhBqoKQJUtsyYigdaOrOa5+hzMoQ8GpH6jg@mail.gmail.com>

Thanks I'll try again in the morning.
On Feb 24, 2016 2:32 AM, "Willy Sudiarto Raharjo" <willysr at slackbuilds.org>
wrote:

> > sbopkg -i graphviz
> >
> >
> > Making all in webp
> > make[3]: Entering directory '/tmp/SBo/graphviz-2.38.0/plugin/webp'
> > make[3]: Nothing to be done for 'all'.
> > make[3]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin/webp'
> > Making all in poppler
> > make[3]: Entering directory '/tmp/SBo/graphviz-2.38.0/plugin/poppler'
> >   CC       gvplugin_poppler.lo
> >   CC       gvloadimage_poppler.lo
> >   CCLD     libgvplugin_poppler_C.la
> >   CCLD     libgvplugin_poppler.la
> >
> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld:
> > cannot find -lopenjp2
> > collect2: error: ld returned 1 exit status
> > Makefile:665: recipe for target 'libgvplugin_poppler.la' failed
> > make[3]: *** [libgvplugin_poppler.la] Error 1
> > make[3]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin/poppler'
> > Makefile:531: recipe for target 'all-recursive' failed
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory '/tmp/SBo/graphviz-2.38.0/plugin'
> > Makefile:774: recipe for target 'all-recursive' failed
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory '/tmp/SBo/graphviz-2.38.0'
> > Makefile:583: recipe for target 'all' failed
> > make: *** [all] Error 2
>
> tested with latest master branch and it's building fine here
>
> Slackware package /tmp/graphviz-2.38.0-x86_64-1_SBo.tgz created.
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> 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/20160224/8ddce311/attachment.html>

From erik at slackbuilds.org  Wed Feb 24 15:14:18 2016
From: erik at slackbuilds.org (Erik Hanson)
Date: Wed, 24 Feb 2016 09:14:18 -0600
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <56CD5A43.5040402@gmail.com>
References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org>
 <56CC47BF.2010105@gmail.com>
 <CAJCpn81XMh6f43fDU3K00rcb=PB4f=9CqMvCxi0zje4v5+6_7g@mail.gmail.com>
 <56CD5A43.5040402@gmail.com>
Message-ID: <20160224091418.3f914aa0@shaggy.doo>

On Wed, 24 Feb 2016 08:22:43 +0100
Andrzej Telszewski <atelszewski at gmail.com> wrote:

> On 24/02/16 07:37, Kyle Guinn wrote:
> > On 2/23/16, Andrzej Telszewski <atelszewski at gmail.com> wrote:  
> >> On 05/02/16 13:48, Martijn Dekker wrote:  
> >>> 2. The following horrible, broken and obsolete eyesore:
> >>>
> >>> find -L . \
> >>>    \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm
> >>> 555 \ -o -perm 511 \) -exec chmod 755 {} \; -o \
> >>>    \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm
> >>> 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
> >>>
> >>> can be replaced by:
> >>>
> >>>      chmod -R a-st,u+rwX,go-w+rX .  
> >>
> >> I advocate this solution.
> >> Can we switch for it?
> >> Or at least would the SlackBuild be accepted if I used this
> >> construct?  
> >
> > Even shorter and simpler to understand:
> > chmod -R u+w,go-w,a+rX-st .
> >  
> 
> Yep, even nicer ;)

These 'hammer everything' solutions change permissions on files that
the find command specifically misses, which may have been set on purpose
by upstream.

Note that I'm not adverse to submissions using a single chmod line,
many of my scripts did this in the past. It requires an extra level
of awareness though, that might be a trap for new players. For the
template, we should leave the find command in place. Bulk swapping
them out in the repo is not an option.


-- 
Erik

From atelszewski at gmail.com  Wed Feb 24 15:48:18 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 24 Feb 2016 16:48:18 +0100
Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc
In-Reply-To: <20160224091418.3f914aa0@shaggy.doo>
References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org>
 <56CC47BF.2010105@gmail.com>
 <CAJCpn81XMh6f43fDU3K00rcb=PB4f=9CqMvCxi0zje4v5+6_7g@mail.gmail.com>
 <56CD5A43.5040402@gmail.com> <20160224091418.3f914aa0@shaggy.doo>
Message-ID: <56CDD0C2.8060705@gmail.com>

On 24/02/16 16:14, Erik Hanson wrote:
> On Wed, 24 Feb 2016 08:22:43 +0100
> Andrzej Telszewski <atelszewski at gmail.com> wrote:
>
>> On 24/02/16 07:37, Kyle Guinn wrote:
>>> On 2/23/16, Andrzej Telszewski <atelszewski at gmail.com> wrote:
>>>> On 05/02/16 13:48, Martijn Dekker wrote:
>>>>> 2. The following horrible, broken and obsolete eyesore:
>>>>>
>>>>> find -L . \
>>>>>     \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm
>>>>> 555 \ -o -perm 511 \) -exec chmod 755 {} \; -o \
>>>>>     \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm
>>>>> 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
>>>>>
>>>>> can be replaced by:
>>>>>
>>>>>       chmod -R a-st,u+rwX,go-w+rX .
>>>>
>>>> I advocate this solution.
>>>> Can we switch for it?
>>>> Or at least would the SlackBuild be accepted if I used this
>>>> construct?
>>>
>>> Even shorter and simpler to understand:
>>> chmod -R u+w,go-w,a+rX-st .
>>>
>>
>> Yep, even nicer ;)
>
> These 'hammer everything' solutions change permissions on files that
> the find command specifically misses, which may have been set on purpose
> by upstream.
>

Can you elaborate?

> Note that I'm not adverse to submissions using a single chmod line,
> many of my scripts did this in the past. It requires an extra level
> of awareness though, that might be a trap for new players. For the
> template, we should leave the find command in place. Bulk swapping
> them out in the repo is not an option.
>
>

Depends on who you ask;) For me it's the "find magic" that always has 
been something I've never even tried to understand;) On the other side, 
chmod approach is crystal clear.

-- 
Best regards,
Andrzej Telszewski

From chris at chrisn.me.uk  Wed Feb 24 22:05:11 2016
From: chris at chrisn.me.uk (Chris Novakovic)
Date: Wed, 24 Feb 2016 22:05:11 +0000
Subject: [Slackbuilds-users] perl-glib source URL
In-Reply-To: <56CB253B.70606@slackbuilds.org>
References: <CANCo2a3TimtQ7iz4hkBm1CuVEk69Uz9M7+XKH9Mzfc-gukynWg@mail.gmail.com>
 <56CB253B.70606@slackbuilds.org>
Message-ID: <56CE2917.7050407@chrisn.me.uk>

On 22/02/2016 15:11, Willy Sudiarto Raharjo wrote:
>> source URL in perl-glib.info should be
>>
>> https://cpan.metacpan.org/authors/id/X/XA/XAOC/Glib-1.307.tar.gz
> 
> done

In general, I'd recommend using BackPAN for links to Perl module
distribution tarballs on SBo. Module authors are able (in fact, are
encouraged) to delete old versions of their module distributions from
PAUSE, and we're typically still referring to those files long after
they've been deleted from the CPAN mirrors. BackPAN maintains a
permanent archive of everything that has been uploaded to PAUSE.

The BackPAN link for Glib-1.307 is

http://backpan.perl.org/authors/id/X/XA/XAOC/Glib-1.307.tar.gz

and will work indefinitely. (cpan.metacpan.org also seems to be storing
some rather old files, but I can't find a guarantee that they won't be
deleted at some point.)

Cheers,
Chris

From glenn.becker at gmail.com  Wed Feb 24 22:12:10 2016
From: glenn.becker at gmail.com (Glenn Becker)
Date: Wed, 24 Feb 2016 17:12:10 -0500
Subject: [Slackbuilds-users] perl-glib source URL
In-Reply-To: <56CE2917.7050407@chrisn.me.uk>
References: <CANCo2a3TimtQ7iz4hkBm1CuVEk69Uz9M7+XKH9Mzfc-gukynWg@mail.gmail.com>
 <56CB253B.70606@slackbuilds.org> <56CE2917.7050407@chrisn.me.uk>
Message-ID: <CANCo2a2nYVn0gvsVBU5eM0Q3TCS5EbM4vXkm1g6WE+RqHvmjnw@mail.gmail.com>

Good point. Thanks!

<http://projecteuler.net/profile/gbecker.png>

On Wed, Feb 24, 2016 at 5:05 PM, Chris Novakovic <chris at chrisn.me.uk> wrote:

> On 22/02/2016 15:11, Willy Sudiarto Raharjo wrote:
> >> source URL in perl-glib.info should be
> >>
> >> https://cpan.metacpan.org/authors/id/X/XA/XAOC/Glib-1.307.tar.gz
> >
> > done
>
> In general, I'd recommend using BackPAN for links to Perl module
> distribution tarballs on SBo. Module authors are able (in fact, are
> encouraged) to delete old versions of their module distributions from
> PAUSE, and we're typically still referring to those files long after
> they've been deleted from the CPAN mirrors. BackPAN maintains a
> permanent archive of everything that has been uploaded to PAUSE.
>
> The BackPAN link for Glib-1.307 is
>
> http://backpan.perl.org/authors/id/X/XA/XAOC/Glib-1.307.tar.gz
>
> and will work indefinitely. (cpan.metacpan.org also seems to be storing
> some rather old files, but I can't find a guarantee that they won't be
> deleted at some point.)
>
> Cheers,
> Chris
> _______________________________________________
> 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/20160224/2879df89/attachment.html>

From z.coldplayer at gmail.com  Thu Feb 25 11:22:28 2016
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Thu, 25 Feb 2016 15:22:28 +0400
Subject: [Slackbuilds-users] bad url for spatialite-tools
In-Reply-To: <CAEWL1_-efmMb51qA-3wjWc6gz2ONLu1CiSYjhqeZ+D_1-L=+mg@mail.gmail.com>
References: <CAEWL1_-Y=7dON34S6qsRo9_DE71Hde2OfJ8mPr8Hr-pk+bKhSQ@mail.gmail.com>
 <CAEWL1_-efmMb51qA-3wjWc6gz2ONLu1CiSYjhqeZ+D_1-L=+mg@mail.gmail.com>
Message-ID: <CAEWL1__cFmSM-GmooXBPnqgy4QsDWj0dmCcOxia0fOUroahJqA@mail.gmail.com>

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

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

I am using SBo-master on slackware-current.

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

>
> ---------- Forwarded message ----------
> From: Jheengut Pritvi <z.coldplayer at gmail.com>
> Date: 17 November 2015 at 10:19
> Subject: bad url for spatialite-tools
> To: mailman at slackbuilds.org
>
>
>  I was compiling spatialite-tools and found the download url to be
> www.gaia-gis.it/gaia-sins/spatialite-tools-sources/spatialite-tools-4.2.0.tar.gz
> instead of  http://www.gaia-gis.it/gaia-sins/spatialite-tools-4.2.0.tar.gz
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160225/83d5d087/attachment-0001.html>

From willysr at slackbuilds.org  Thu Feb 25 16:26:07 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 25 Feb 2016 23:26:07 +0700
Subject: [Slackbuilds-users] bad url for spatialite-tools
In-Reply-To: <CAEWL1__cFmSM-GmooXBPnqgy4QsDWj0dmCcOxia0fOUroahJqA@mail.gmail.com>
References: <CAEWL1_-Y=7dON34S6qsRo9_DE71Hde2OfJ8mPr8Hr-pk+bKhSQ@mail.gmail.com>
 <CAEWL1_-efmMb51qA-3wjWc6gz2ONLu1CiSYjhqeZ+D_1-L=+mg@mail.gmail.com>
 <CAEWL1__cFmSM-GmooXBPnqgy4QsDWj0dmCcOxia0fOUroahJqA@mail.gmail.com>
Message-ID: <56CF2B1F.90101@slackbuilds.org>

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

all applied to my branch

Thanks


-- 
Willy Sudiarto Raharjo

-------------- 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/20160225/c05adbf8/attachment.asc>

From duncan_roe at acslink.net.au  Thu Feb 25 23:55:44 2016
From: duncan_roe at acslink.net.au (Duncan Roe)
Date: Fri, 26 Feb 2016 10:55:44 +1100
Subject: [Slackbuilds-users] Error building inkscape-0.91
Message-ID: <20160225235544.GA11640@dimstar.local.net>

Hi all,

This looks to me to be a problem for upstream. I'm posting here because of the
workaround and also because I guess any bug report to upstream should come from
the maintainer.

At least on 32-bit, the SlackBuild terminates with this error:
>   CXXLD    inkscape
> /usr/lib/libdbus-glib-1.so.2: undefined reference to `dbus_message_iter_abandon_container'
> collect2: error: ld returned 1 exit status
> make[3]: *** [inkscape] Error 1

In brief, the workaround is to complete the SlackBuild by hand, inserting
"-ldbus-1" near the end of g++ lines that invoke ld (one for inkscape, one for
inkview).

THE WORKAROUND

To get the g++ command line, as root cd to /tmp/SBo/inkscape-0.91 and run
> make V=1
redirecting output to a file. Edit this file into a shell script e.g.
> #!/bin/sh
> cd /tmp/SBo/inkscape-0.91/src
> g++ -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual ...

The g++ line above is over 16KB but vi copes. At the end, change
 > /usr/lib/libglib-2.0.so -pthread -fopenmp
 to
 > /usr/lib/libglib-2.0.so -ldbus-1 -pthread -fopenmp

Now run make. It will fail similarly when loading inkview. Repeat steps above.

Run make again. It will complete.

Paste in to your root build xterm enough of the SlackBuild to set all the
upper-case shell variables (i.e. from "TMP=" through "fi"). Set CWD to be the
original directory containing inkscape.SlackBuild. Your curent working directory
should still be /tmp/SBo/inkscape-0.91.

To be safe, re-issue the mkdir -p at line 60 (I changed it to -pv and it claimed
to make something).

Paste in and execute everything from the make install on line 84 onwards.

SOME KIND OF AN EXPLANATION

The g++ line doesn't mention libdbus-glib-1. It seems some other .so is pulling
it in as a dependency.

As it happens, I have a tool, findit(*), which can investigate this sort of
problem. It agreed with ld:
> 23:45:32# findit /usr/lib/libdbus-glib-1.so.2 dbus_message_iter_abandon_container
> /usr/lib/libdbus-glib-1.so.2: undefined symbol: dbus_message_iter_abandon_container. (dlsym)

/usr/lib/libdbus-glib-1.la advertises a number of dependencies:
> # Libraries that this one depends upon.
> dependency_libs=' /usr/lib/libdbus-1.la -lrt /usr/lib/libgio-2.0.la ...

libdbus-1.la only shows -lpthread -lrt as dependencies. Ignoring that:
> 23:58:31# findit -ldbus-1 /usr/lib/libdbus-glib-1.so.2 dbus_message_iter_abandon_container
> Found dbus_message_iter_abandon_container in /usr/lib/libdbus-glib-1.so.2 at 0xb75a9fb0

It's been my experience in the past that shared libraries will sometimes provide
a symbol without loading dependencies and sometimes they won't. Or the same
shared library may provide some symbols and not others. Hence the workaround.

WHERE IS THE BUG REALLY?

I would say the fault lies with whatever library is pulling in libdbus-glib-1.
It should also pull in libdbus-1. Maybe someone will "just know" which library
"it" is.

Cheers ... Duncan.

(*) findit is part of https://github.com/duncan-roe/command_line_tools
    If you would like it, feel free to take a clone

From fernando.lopezjr at gmail.com  Fri Feb 26 00:01:24 2016
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Thu, 25 Feb 2016 17:01:24 -0700
Subject: [Slackbuilds-users] Error building inkscape-0.91
In-Reply-To: <20160225235544.GA11640@dimstar.local.net>
References: <20160225235544.GA11640@dimstar.local.net>
Message-ID: <CALrQ46CYnEaJ5C3U84Y7XwZZGw09DwZd3fGAswSZMds+ptO9_A@mail.gmail.com>

I am the maintainer for inkscape. I only run 64 bits.

On Thu, Feb 25, 2016 at 4:55 PM, Duncan Roe <duncan_roe at acslink.net.au>
wrote:

> Hi all,
>
> This looks to me to be a problem for upstream. I'm posting here because of
> the
> workaround and also because I guess any bug report to upstream should come
> from
> the maintainer.
>
> At least on 32-bit, the SlackBuild terminates with this error:
> >   CXXLD    inkscape
> > /usr/lib/libdbus-glib-1.so.2: undefined reference to
> `dbus_message_iter_abandon_container'
> > collect2: error: ld returned 1 exit status
> > make[3]: *** [inkscape] Error 1
>
> In brief, the workaround is to complete the SlackBuild by hand, inserting
> "-ldbus-1" near the end of g++ lines that invoke ld (one for inkscape, one
> for
> inkview).
>
> THE WORKAROUND
>
> To get the g++ command line, as root cd to /tmp/SBo/inkscape-0.91 and run
> > make V=1
> redirecting output to a file. Edit this file into a shell script e.g.
> > #!/bin/sh
> > cd /tmp/SBo/inkscape-0.91/src
> > g++ -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual ...
>
> The g++ line above is over 16KB but vi copes. At the end, change
>  > /usr/lib/libglib-2.0.so -pthread -fopenmp
>  to
>  > /usr/lib/libglib-2.0.so -ldbus-1 -pthread -fopenmp
>
> Now run make. It will fail similarly when loading inkview. Repeat steps
> above.
>
> Run make again. It will complete.
>
> Paste in to your root build xterm enough of the SlackBuild to set all the
> upper-case shell variables (i.e. from "TMP=" through "fi"). Set CWD to be
> the
> original directory containing inkscape.SlackBuild. Your curent working
> directory
> should still be /tmp/SBo/inkscape-0.91.
>
> To be safe, re-issue the mkdir -p at line 60 (I changed it to -pv and it
> claimed
> to make something).
>
> Paste in and execute everything from the make install on line 84 onwards.
>
> SOME KIND OF AN EXPLANATION
>
> The g++ line doesn't mention libdbus-glib-1. It seems some other .so is
> pulling
> it in as a dependency.
>
> As it happens, I have a tool, findit(*), which can investigate this sort of
> problem. It agreed with ld:
> > 23:45:32# findit /usr/lib/libdbus-glib-1.so.2
> dbus_message_iter_abandon_container
> > /usr/lib/libdbus-glib-1.so.2: undefined symbol:
> dbus_message_iter_abandon_container. (dlsym)
>
> /usr/lib/libdbus-glib-1.la advertises a number of dependencies:
> > # Libraries that this one depends upon.
> > dependency_libs=' /usr/lib/libdbus-1.la -lrt /usr/lib/libgio-2.0.la ...
>
> libdbus-1.la only shows -lpthread -lrt as dependencies. Ignoring that:
> > 23:58:31# findit -ldbus-1 /usr/lib/libdbus-glib-1.so.2
> dbus_message_iter_abandon_container
> > Found dbus_message_iter_abandon_container in
> /usr/lib/libdbus-glib-1.so.2 at 0xb75a9fb0
>
> It's been my experience in the past that shared libraries will sometimes
> provide
> a symbol without loading dependencies and sometimes they won't. Or the same
> shared library may provide some symbols and not others. Hence the
> workaround.
>
> WHERE IS THE BUG REALLY?
>
> I would say the fault lies with whatever library is pulling in
> libdbus-glib-1.
> It should also pull in libdbus-1. Maybe someone will "just know" which
> library
> "it" is.
>
> Cheers ... Duncan.
>
> (*) findit is part of https://github.com/duncan-roe/command_line_tools
>     If you would like it, feel free to take a clone
>



-- 

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

From willysr at slackbuilds.org  Fri Feb 26 08:45:44 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 26 Feb 2016 15:45:44 +0700
Subject: [Slackbuilds-users] Error building inkscape-0.91
In-Reply-To: <CALrQ46CYnEaJ5C3U84Y7XwZZGw09DwZd3fGAswSZMds+ptO9_A@mail.gmail.com>
References: <20160225235544.GA11640@dimstar.local.net>
 <CALrQ46CYnEaJ5C3U84Y7XwZZGw09DwZd3fGAswSZMds+ptO9_A@mail.gmail.com>
Message-ID: <56D010B8.7080007@slackbuilds.org>

>> This looks to me to be a problem for upstream. I'm posting here because of
>> the
>> workaround and also because I guess any bug report to upstream should come
>> from
>> the maintainer.
>>
>> At least on 32-bit, the SlackBuild terminates with this error:
>>>   CXXLD    inkscape
>>> /usr/lib/libdbus-glib-1.so.2: undefined reference to
>> `dbus_message_iter_abandon_container'
>>> collect2: error: ld returned 1 exit status
>>> make[3]: *** [inkscape] Error 1
>>
>> In brief, the workaround is to complete the SlackBuild by hand, inserting
>> "-ldbus-1" near the end of g++ lines that invoke ld (one for inkscape, one
>> for
>> inkview).
>>
>> THE WORKAROUND
>>
>> To get the g++ command line, as root cd to /tmp/SBo/inkscape-0.91 and run
>>> make V=1
>> redirecting output to a file. Edit this file into a shell script e.g.
>>> #!/bin/sh
>>> cd /tmp/SBo/inkscape-0.91/src
>>> g++ -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual ...
>>
>> The g++ line above is over 16KB but vi copes. At the end, change
>>  > /usr/lib/libglib-2.0.so -pthread -fopenmp
>>  to
>>  > /usr/lib/libglib-2.0.so -ldbus-1 -pthread -fopenmp
>>
>> Now run make. It will fail similarly when loading inkview. Repeat steps
>> above.
>>
>> Run make again. It will complete.
>>
>> Paste in to your root build xterm enough of the SlackBuild to set all the
>> upper-case shell variables (i.e. from "TMP=" through "fi"). Set CWD to be
>> the
>> original directory containing inkscape.SlackBuild. Your curent working
>> directory
>> should still be /tmp/SBo/inkscape-0.91.
>>
>> To be safe, re-issue the mkdir -p at line 60 (I changed it to -pv and it
>> claimed
>> to make something).
>>
>> Paste in and execute everything from the make install on line 84 onwards.
>>
>> SOME KIND OF AN EXPLANATION
>>
>> The g++ line doesn't mention libdbus-glib-1. It seems some other .so is
>> pulling
>> it in as a dependency.
>>
>> As it happens, I have a tool, findit(*), which can investigate this sort of
>> problem. It agreed with ld:
>>> 23:45:32# findit /usr/lib/libdbus-glib-1.so.2
>> dbus_message_iter_abandon_container
>>> /usr/lib/libdbus-glib-1.so.2: undefined symbol:
>> dbus_message_iter_abandon_container. (dlsym)
>>
>> /usr/lib/libdbus-glib-1.la advertises a number of dependencies:
>>> # Libraries that this one depends upon.
>>> dependency_libs=' /usr/lib/libdbus-1.la -lrt /usr/lib/libgio-2.0.la ...
>>
>> libdbus-1.la only shows -lpthread -lrt as dependencies. Ignoring that:
>>> 23:58:31# findit -ldbus-1 /usr/lib/libdbus-glib-1.so.2
>> dbus_message_iter_abandon_container
>>> Found dbus_message_iter_abandon_container in
>> /usr/lib/libdbus-glib-1.so.2 at 0xb75a9fb0
>>
>> It's been my experience in the past that shared libraries will sometimes
>> provide
>> a symbol without loading dependencies and sometimes they won't. Or the same
>> shared library may provide some symbols and not others. Hence the
>> workaround.
>>
>> WHERE IS THE BUG REALLY?
>>
>> I would say the fault lies with whatever library is pulling in
>> libdbus-glib-1.
>> It should also pull in libdbus-1. Maybe someone will "just know" which
>> library
>> "it" is.

working fine here using sbopkg

numpy:
  MD5SUM check for numpy-1.9.1.tar.gz ... OK
  Building package numpy-1.9.1-i486-1_SBo.tgz ... OK
  Installing package numpy-1.9.1-i486-1_SBo.tgz ... OK

BeautifulSoup:
  MD5SUM check for BeautifulSoup-3.2.1.tar.gz ... OK
  Building package BeautifulSoup-3.2.1-i486-1_SBo.tgz ... OK
  Installing package BeautifulSoup-3.2.1-i486-1_SBo.tgz ... OK

lxml:
  MD5SUM check for lxml-3.5.0.tar.gz ... OK
  Building package lxml-3.5.0-i486-1_SBo.tgz ... OK
  Installing package lxml-3.5.0-i486-1_SBo.tgz ... OK

inkscape:
  MD5SUM check for inkscape-0.91.tar.bz2 ... OK
  Building package inkscape-0.91-i486-1_SBo.tgz ... OK
  Installing package inkscape-0.91-i486-1_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/20160226/c132b2ee/attachment.asc>

From duncan_roe at acslink.net.au  Fri Feb 26 10:30:01 2016
From: duncan_roe at acslink.net.au (Duncan Roe)
Date: Fri, 26 Feb 2016 21:30:01 +1100
Subject: [Slackbuilds-users] Error building inkscape-0.91
In-Reply-To: <56D010B8.7080007@slackbuilds.org>
References: <20160225235544.GA11640@dimstar.local.net>
 <CALrQ46CYnEaJ5C3U84Y7XwZZGw09DwZd3fGAswSZMds+ptO9_A@mail.gmail.com>
 <56D010B8.7080007@slackbuilds.org>
Message-ID: <20160226103001.GD11640@dimstar.local.net>

On Fri, Feb 26, 2016 at 03:45:44PM +0700, Willy Sudiarto Raharjo wrote:
> >> This looks to me to be a problem for upstream. I'm posting here because of
> >> the
> >> workaround and also because I guess any bug report to upstream should come
> >> from
> >> the maintainer.
> >>
> >> At least on 32-bit, the SlackBuild terminates with this error:
> >>>   CXXLD    inkscape
> >>> /usr/lib/libdbus-glib-1.so.2: undefined reference to
> >> `dbus_message_iter_abandon_container'
> >>> collect2: error: ld returned 1 exit status
> >>> make[3]: *** [inkscape] Error 1
> >>
> >> In brief, the workaround is to complete the SlackBuild by hand, inserting
> >> "-ldbus-1" near the end of g++ lines that invoke ld (one for inkscape, one
> >> for
> >> inkview).
> >>
> >> THE WORKAROUND
> >>
> >> To get the g++ command line, as root cd to /tmp/SBo/inkscape-0.91 and run
> >>> make V=1
> >> redirecting output to a file. Edit this file into a shell script e.g.
> >>> #!/bin/sh
> >>> cd /tmp/SBo/inkscape-0.91/src
> >>> g++ -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual ...
> >>
> >> The g++ line above is over 16KB but vi copes. At the end, change
> >>  > /usr/lib/libglib-2.0.so -pthread -fopenmp
> >>  to
> >>  > /usr/lib/libglib-2.0.so -ldbus-1 -pthread -fopenmp
> >>
> >> Now run make. It will fail similarly when loading inkview. Repeat steps
> >> above.
> >>
> >> Run make again. It will complete.
> >>
> >> Paste in to your root build xterm enough of the SlackBuild to set all the
> >> upper-case shell variables (i.e. from "TMP=" through "fi"). Set CWD to be
> >> the
> >> original directory containing inkscape.SlackBuild. Your curent working
> >> directory
> >> should still be /tmp/SBo/inkscape-0.91.
> >>
> >> To be safe, re-issue the mkdir -p at line 60 (I changed it to -pv and it
> >> claimed
> >> to make something).
> >>
> >> Paste in and execute everything from the make install on line 84 onwards.
> >>
> >> SOME KIND OF AN EXPLANATION
> >>
> >> The g++ line doesn't mention libdbus-glib-1. It seems some other .so is
> >> pulling
> >> it in as a dependency.
> >>
> >> As it happens, I have a tool, findit(*), which can investigate this sort of
> >> problem. It agreed with ld:
> >>> 23:45:32# findit /usr/lib/libdbus-glib-1.so.2
> >> dbus_message_iter_abandon_container
> >>> /usr/lib/libdbus-glib-1.so.2: undefined symbol:
> >> dbus_message_iter_abandon_container. (dlsym)
> >>
> >> /usr/lib/libdbus-glib-1.la advertises a number of dependencies:
> >>> # Libraries that this one depends upon.
> >>> dependency_libs=' /usr/lib/libdbus-1.la -lrt /usr/lib/libgio-2.0.la ...
> >>
> >> libdbus-1.la only shows -lpthread -lrt as dependencies. Ignoring that:
> >>> 23:58:31# findit -ldbus-1 /usr/lib/libdbus-glib-1.so.2
> >> dbus_message_iter_abandon_container
> >>> Found dbus_message_iter_abandon_container in
> >> /usr/lib/libdbus-glib-1.so.2 at 0xb75a9fb0
> >>
> >> It's been my experience in the past that shared libraries will sometimes
> >> provide
> >> a symbol without loading dependencies and sometimes they won't. Or the same
> >> shared library may provide some symbols and not others. Hence the
> >> workaround.
> >>
> >> WHERE IS THE BUG REALLY?
> >>
> >> I would say the fault lies with whatever library is pulling in
> >> libdbus-glib-1.
> >> It should also pull in libdbus-1. Maybe someone will "just know" which
> >> library
> >> "it" is.
>
> working fine here using sbopkg
>
> numpy:
>   MD5SUM check for numpy-1.9.1.tar.gz ... OK
>   Building package numpy-1.9.1-i486-1_SBo.tgz ... OK
>   Installing package numpy-1.9.1-i486-1_SBo.tgz ... OK
>
> BeautifulSoup:
>   MD5SUM check for BeautifulSoup-3.2.1.tar.gz ... OK
>   Building package BeautifulSoup-3.2.1-i486-1_SBo.tgz ... OK
>   Installing package BeautifulSoup-3.2.1-i486-1_SBo.tgz ... OK
>
> lxml:
>   MD5SUM check for lxml-3.5.0.tar.gz ... OK
>   Building package lxml-3.5.0-i486-1_SBo.tgz ... OK
>   Installing package lxml-3.5.0-i486-1_SBo.tgz ... OK
>
> inkscape:
>   MD5SUM check for inkscape-0.91.tar.bz2 ... OK
>   Building package inkscape-0.91-i486-1_SBo.tgz ... OK
>   Installing package inkscape-0.91-i486-1_SBo.tgz ... OK
>
>
> --
> Willy Sudiarto Raharjo
>
Thanks for trying that Willy.

I built a number of (optional(?)) dependencies:

 gtkmm-2.24.4-i486-1_SBo
 atkmm-2.22.7-i486-1_SBo
 mm-common-0.9.7-noarch-1_SBo
 pangomm-2.34.0-i486-1_SBo
 cairomm-1.10.0-i486-1_SBo
 glibmm-2.36.2-i486-1_SBo
 libsigc++-2.2.11-i486-1_SBo
 gsl-1.16-i486-1_SBo
 libwpg-0.2.2-i486-1_SBo

IIRC, some of the packages you listed would not build for me w/out at least some
of the above.

I missed a numpy update - have numpy-1.8.0-i486-1_SBo installed here.

I can try in a freshly installed VM when I get Virtualbox working with kernel
4.4,

Cheers ... Duncan.

From slackbuilds at schoepfer.info  Fri Feb 26 15:56:21 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 26 Feb 2016 16:56:21 +0100
Subject: [Slackbuilds-users] texlive 2015
Message-ID: <56D075A5.9000100@schoepfer.info>

Hi,

i'm not sure if this is the way to update a package, anyway, here is my 
try to update texlive on slackware current.
texlive2015 git diff against master-branch attached.
I successfully compiled some tex-documents with this build, much more 
testing may be needed.
Maybe the docs should be put a separate package also.


Regards

Franzen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: texlive2015.diff
Type: text/x-patch
Size: 6853 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160226/d8aea28e/attachment.bin>

From fernando.lopezjr at gmail.com  Fri Feb 26 23:50:03 2016
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Fri, 26 Feb 2016 16:50:03 -0700
Subject: [Slackbuilds-users] Error building inkscape-0.91
In-Reply-To: <20160226103001.GD11640@dimstar.local.net>
References: <20160225235544.GA11640@dimstar.local.net>
 <CALrQ46CYnEaJ5C3U84Y7XwZZGw09DwZd3fGAswSZMds+ptO9_A@mail.gmail.com>
 <56D010B8.7080007@slackbuilds.org>
 <20160226103001.GD11640@dimstar.local.net>
Message-ID: <CALrQ46AwPP9m6dDazEz9MbHA1+XJBVkr3nr=jzXV-FZpXPAp=w@mail.gmail.com>

i am currently running kernel 4.4.1. I just updated. will try to compile
tonight.

On Fri, Feb 26, 2016 at 3:30 AM, Duncan Roe <duncan_roe at acslink.net.au>
wrote:

> On Fri, Feb 26, 2016 at 03:45:44PM +0700, Willy Sudiarto Raharjo wrote:
> > >> This looks to me to be a problem for upstream. I'm posting here
> because of
> > >> the
> > >> workaround and also because I guess any bug report to upstream should
> come
> > >> from
> > >> the maintainer.
> > >>
> > >> At least on 32-bit, the SlackBuild terminates with this error:
> > >>>   CXXLD    inkscape
> > >>> /usr/lib/libdbus-glib-1.so.2: undefined reference to
> > >> `dbus_message_iter_abandon_container'
> > >>> collect2: error: ld returned 1 exit status
> > >>> make[3]: *** [inkscape] Error 1
> > >>
> > >> In brief, the workaround is to complete the SlackBuild by hand,
> inserting
> > >> "-ldbus-1" near the end of g++ lines that invoke ld (one for
> inkscape, one
> > >> for
> > >> inkview).
> > >>
> > >> THE WORKAROUND
> > >>
> > >> To get the g++ command line, as root cd to /tmp/SBo/inkscape-0.91 and
> run
> > >>> make V=1
> > >> redirecting output to a file. Edit this file into a shell script e.g.
> > >>> #!/bin/sh
> > >>> cd /tmp/SBo/inkscape-0.91/src
> > >>> g++ -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual
> ...
> > >>
> > >> The g++ line above is over 16KB but vi copes. At the end, change
> > >>  > /usr/lib/libglib-2.0.so -pthread -fopenmp
> > >>  to
> > >>  > /usr/lib/libglib-2.0.so -ldbus-1 -pthread -fopenmp
> > >>
> > >> Now run make. It will fail similarly when loading inkview. Repeat
> steps
> > >> above.
> > >>
> > >> Run make again. It will complete.
> > >>
> > >> Paste in to your root build xterm enough of the SlackBuild to set all
> the
> > >> upper-case shell variables (i.e. from "TMP=" through "fi"). Set CWD
> to be
> > >> the
> > >> original directory containing inkscape.SlackBuild. Your curent working
> > >> directory
> > >> should still be /tmp/SBo/inkscape-0.91.
> > >>
> > >> To be safe, re-issue the mkdir -p at line 60 (I changed it to -pv and
> it
> > >> claimed
> > >> to make something).
> > >>
> > >> Paste in and execute everything from the make install on line 84
> onwards.
> > >>
> > >> SOME KIND OF AN EXPLANATION
> > >>
> > >> The g++ line doesn't mention libdbus-glib-1. It seems some other .so
> is
> > >> pulling
> > >> it in as a dependency.
> > >>
> > >> As it happens, I have a tool, findit(*), which can investigate this
> sort of
> > >> problem. It agreed with ld:
> > >>> 23:45:32# findit /usr/lib/libdbus-glib-1.so.2
> > >> dbus_message_iter_abandon_container
> > >>> /usr/lib/libdbus-glib-1.so.2: undefined symbol:
> > >> dbus_message_iter_abandon_container. (dlsym)
> > >>
> > >> /usr/lib/libdbus-glib-1.la advertises a number of dependencies:
> > >>> # Libraries that this one depends upon.
> > >>> dependency_libs=' /usr/lib/libdbus-1.la -lrt /usr/lib/libgio-2.0.la
> ...
> > >>
> > >> libdbus-1.la only shows -lpthread -lrt as dependencies. Ignoring
> that:
> > >>> 23:58:31# findit -ldbus-1 /usr/lib/libdbus-glib-1.so.2
> > >> dbus_message_iter_abandon_container
> > >>> Found dbus_message_iter_abandon_container in
> > >> /usr/lib/libdbus-glib-1.so.2 at 0xb75a9fb0
> > >>
> > >> It's been my experience in the past that shared libraries will
> sometimes
> > >> provide
> > >> a symbol without loading dependencies and sometimes they won't. Or
> the same
> > >> shared library may provide some symbols and not others. Hence the
> > >> workaround.
> > >>
> > >> WHERE IS THE BUG REALLY?
> > >>
> > >> I would say the fault lies with whatever library is pulling in
> > >> libdbus-glib-1.
> > >> It should also pull in libdbus-1. Maybe someone will "just know" which
> > >> library
> > >> "it" is.
> >
> > working fine here using sbopkg
> >
> > numpy:
> >   MD5SUM check for numpy-1.9.1.tar.gz ... OK
> >   Building package numpy-1.9.1-i486-1_SBo.tgz ... OK
> >   Installing package numpy-1.9.1-i486-1_SBo.tgz ... OK
> >
> > BeautifulSoup:
> >   MD5SUM check for BeautifulSoup-3.2.1.tar.gz ... OK
> >   Building package BeautifulSoup-3.2.1-i486-1_SBo.tgz ... OK
> >   Installing package BeautifulSoup-3.2.1-i486-1_SBo.tgz ... OK
> >
> > lxml:
> >   MD5SUM check for lxml-3.5.0.tar.gz ... OK
> >   Building package lxml-3.5.0-i486-1_SBo.tgz ... OK
> >   Installing package lxml-3.5.0-i486-1_SBo.tgz ... OK
> >
> > inkscape:
> >   MD5SUM check for inkscape-0.91.tar.bz2 ... OK
> >   Building package inkscape-0.91-i486-1_SBo.tgz ... OK
> >   Installing package inkscape-0.91-i486-1_SBo.tgz ... OK
> >
> >
> > --
> > Willy Sudiarto Raharjo
> >
> Thanks for trying that Willy.
>
> I built a number of (optional(?)) dependencies:
>
>  gtkmm-2.24.4-i486-1_SBo
>  atkmm-2.22.7-i486-1_SBo
>  mm-common-0.9.7-noarch-1_SBo
>  pangomm-2.34.0-i486-1_SBo
>  cairomm-1.10.0-i486-1_SBo
>  glibmm-2.36.2-i486-1_SBo
>  libsigc++-2.2.11-i486-1_SBo
>  gsl-1.16-i486-1_SBo
>  libwpg-0.2.2-i486-1_SBo
>
> IIRC, some of the packages you listed would not build for me w/out at
> least some
> of the above.
>
> I missed a numpy update - have numpy-1.8.0-i486-1_SBo installed here.
>
> I can try in a freshly installed VM when I get Virtualbox working with
> kernel
> 4.4,
>
> Cheers ... Duncan.
> _______________________________________________
> 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/20160226/5481da3d/attachment.html>

From ruan.klein at gmail.com  Sat Feb 27 00:03:55 2016
From: ruan.klein at gmail.com (Ruan)
Date: Fri, 26 Feb 2016 21:03:55 -0300
Subject: [Slackbuilds-users] LibreOffice 5.0.5 "Application Error" (?)
Message-ID: <CAA9ENOv=5HhuUr1fR42+khMJgQ4Ex0B7RmYAWT=+5vYiE=uO3g@mail.gmail.com>

Hi,

I installed the LibreOffice via SlackBuild, but if run from terminal:

~ $ soffice
Application Error

I have no idea what it is.

* I updated manually to version 5.1, but the same error appears.

-- 
*Ruan *
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160226/866ca3b8/attachment-0001.html>

From willysr at gmail.com  Sat Feb 27 00:55:50 2016
From: willysr at gmail.com (Willy Sudiarto Raharjo)
Date: Sat, 27 Feb 2016 07:55:50 +0700
Subject: [Slackbuilds-users] Error building inkscape-0.91
In-Reply-To: <20160226103001.GD11640@dimstar.local.net>
References: <20160225235544.GA11640@dimstar.local.net>
 <CALrQ46CYnEaJ5C3U84Y7XwZZGw09DwZd3fGAswSZMds+ptO9_A@mail.gmail.com>
 <56D010B8.7080007@slackbuilds.org>
 <20160226103001.GD11640@dimstar.local.net>
Message-ID: <CAJ+QsaL-uzmfEx35FsvSVySkofZK-mj6cbUcbZ3fCLtxQw6e2w@mail.gmail.com>

> I built a number of (optional(?)) dependencies:
>
>  gtkmm-2.24.4-i486-1_SBo
>  atkmm-2.22.7-i486-1_SBo
>  mm-common-0.9.7-noarch-1_SBo
>  pangomm-2.34.0-i486-1_SBo
>  cairomm-1.10.0-i486-1_SBo
>  glibmm-2.36.2-i486-1_SBo
>  libsigc++-2.2.11-i486-1_SBo
>  gsl-1.16-i486-1_SBo
>  libwpg-0.2.2-i486-1_SBo
>
> IIRC, some of the packages you listed would not build for me w/out at
least some
> of the above.

Some of those packages are now in current so no need to build them

Willy Sudiarto Raharjo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160227/3324a36d/attachment.html>

From rsamurti at gmail.com  Fri Feb 26 14:50:17 2016
From: rsamurti at gmail.com (Ananda Murthy R S)
Date: Fri, 26 Feb 2016 20:20:17 +0530
Subject: [Slackbuilds-users] Error building inkscape-0.91
In-Reply-To: <56D010B8.7080007@slackbuilds.org>
References: <20160225235544.GA11640@dimstar.local.net>
 <CALrQ46CYnEaJ5C3U84Y7XwZZGw09DwZd3fGAswSZMds+ptO9_A@mail.gmail.com>
 <56D010B8.7080007@slackbuilds.org>
Message-ID: <CAMwjf3VSOLLV2_jXuYE7+93jvuawcsg+fmEg22evQ3rwvz7C0A@mail.gmail.com>

Hello,

But on my system running on Slackware-14.2 Beta-2 of 23-Feb-2016, Inkscape
is not building. I get the error message given below:


?
Any clues to correct this?

Thanks for your help.

Anand

On Fri, Feb 26, 2016 at 2:15 PM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> >> This looks to me to be a problem for upstream. I'm posting here because
> of
> >> the
> >> workaround and also because I guess any bug report to upstream should
> come
> >> from
> >> the maintainer.
> >>
> >> At least on 32-bit, the SlackBuild terminates with this error:
> >>>   CXXLD    inkscape
> >>> /usr/lib/libdbus-glib-1.so.2: undefined reference to
> >> `dbus_message_iter_abandon_container'
> >>> collect2: error: ld returned 1 exit status
> >>> make[3]: *** [inkscape] Error 1
> >>
> >> In brief, the workaround is to complete the SlackBuild by hand,
> inserting
> >> "-ldbus-1" near the end of g++ lines that invoke ld (one for inkscape,
> one
> >> for
> >> inkview).
> >>
> >> THE WORKAROUND
> >>
> >> To get the g++ command line, as root cd to /tmp/SBo/inkscape-0.91 and
> run
> >>> make V=1
> >> redirecting output to a file. Edit this file into a shell script e.g.
> >>> #!/bin/sh
> >>> cd /tmp/SBo/inkscape-0.91/src
> >>> g++ -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual
> ...
> >>
> >> The g++ line above is over 16KB but vi copes. At the end, change
> >>  > /usr/lib/libglib-2.0.so -pthread -fopenmp
> >>  to
> >>  > /usr/lib/libglib-2.0.so -ldbus-1 -pthread -fopenmp
> >>
> >> Now run make. It will fail similarly when loading inkview. Repeat steps
> >> above.
> >>
> >> Run make again. It will complete.
> >>
> >> Paste in to your root build xterm enough of the SlackBuild to set all
> the
> >> upper-case shell variables (i.e. from "TMP=" through "fi"). Set CWD to
> be
> >> the
> >> original directory containing inkscape.SlackBuild. Your curent working
> >> directory
> >> should still be /tmp/SBo/inkscape-0.91.
> >>
> >> To be safe, re-issue the mkdir -p at line 60 (I changed it to -pv and it
> >> claimed
> >> to make something).
> >>
> >> Paste in and execute everything from the make install on line 84
> onwards.
> >>
> >> SOME KIND OF AN EXPLANATION
> >>
> >> The g++ line doesn't mention libdbus-glib-1. It seems some other .so is
> >> pulling
> >> it in as a dependency.
> >>
> >> As it happens, I have a tool, findit(*), which can investigate this
> sort of
> >> problem. It agreed with ld:
> >>> 23:45:32# findit /usr/lib/libdbus-glib-1.so.2
> >> dbus_message_iter_abandon_container
> >>> /usr/lib/libdbus-glib-1.so.2: undefined symbol:
> >> dbus_message_iter_abandon_container. (dlsym)
> >>
> >> /usr/lib/libdbus-glib-1.la advertises a number of dependencies:
> >>> # Libraries that this one depends upon.
> >>> dependency_libs=' /usr/lib/libdbus-1.la -lrt /usr/lib/libgio-2.0.la
> ...
> >>
> >> libdbus-1.la only shows -lpthread -lrt as dependencies. Ignoring that:
> >>> 23:58:31# findit -ldbus-1 /usr/lib/libdbus-glib-1.so.2
> >> dbus_message_iter_abandon_container
> >>> Found dbus_message_iter_abandon_container in
> >> /usr/lib/libdbus-glib-1.so.2 at 0xb75a9fb0
> >>
> >> It's been my experience in the past that shared libraries will sometimes
> >> provide
> >> a symbol without loading dependencies and sometimes they won't. Or the
> same
> >> shared library may provide some symbols and not others. Hence the
> >> workaround.
> >>
> >> WHERE IS THE BUG REALLY?
> >>
> >> I would say the fault lies with whatever library is pulling in
> >> libdbus-glib-1.
> >> It should also pull in libdbus-1. Maybe someone will "just know" which
> >> library
> >> "it" is.
>
> working fine here using sbopkg
>
> numpy:
>   MD5SUM check for numpy-1.9.1.tar.gz ... OK
>   Building package numpy-1.9.1-i486-1_SBo.tgz ... OK
>   Installing package numpy-1.9.1-i486-1_SBo.tgz ... OK
>
> BeautifulSoup:
>   MD5SUM check for BeautifulSoup-3.2.1.tar.gz ... OK
>   Building package BeautifulSoup-3.2.1-i486-1_SBo.tgz ... OK
>   Installing package BeautifulSoup-3.2.1-i486-1_SBo.tgz ... OK
>
> lxml:
>   MD5SUM check for lxml-3.5.0.tar.gz ... OK
>   Building package lxml-3.5.0-i486-1_SBo.tgz ... OK
>   Installing package lxml-3.5.0-i486-1_SBo.tgz ... OK
>
> inkscape:
>   MD5SUM check for inkscape-0.91.tar.bz2 ... OK
>   Building package inkscape-0.91-i486-1_SBo.tgz ... OK
>   Installing package inkscape-0.91-i486-1_SBo.tgz ... OK
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> 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/
>
>
>


-- 
Close Windows ! Open source !!
Free software from proprietary mafia !!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160226/26fbb80d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: inkscape-build-failure.png
Type: image/png
Size: 110702 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160226/26fbb80d/attachment-0001.png>

From willysr at slackbuilds.org  Sat Feb 27 03:14:52 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 27 Feb 2016 10:14:52 +0700
Subject: [Slackbuilds-users] LibreOffice 5.0.5 "Application Error" (?)
In-Reply-To: <CAA9ENOv=5HhuUr1fR42+khMJgQ4Ex0B7RmYAWT=+5vYiE=uO3g@mail.gmail.com>
References: <CAA9ENOv=5HhuUr1fR42+khMJgQ4Ex0B7RmYAWT=+5vYiE=uO3g@mail.gmail.com>
Message-ID: <56D114AC.7030001@slackbuilds.org>

> I installed the LibreOffice via SlackBuild, but if run from terminal:
> 
> ~ $ soffice
> Application Error
> 
> I have no idea what it is.
> 
> * I updated manually to version 5.1, but the same error appears.

Just to be clear, is the libreoffice (binary repackaging) or LibreOffice
(compiled from source)?

I used the libreoffice (binary repackaging) 5.1 and it's working fine here


-- 
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/20160227/ef71fec0/attachment.asc>

From rworkman at slackbuilds.org  Sat Feb 27 13:25:14 2016
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 27 Feb 2016 07:25:14 -0600
Subject: [Slackbuilds-users] LibreOffice 5.0.5 "Application Error" (?)
In-Reply-To: <CAA9ENOv=5HhuUr1fR42+khMJgQ4Ex0B7RmYAWT=+5vYiE=uO3g@mail.gmail.com>
References: <CAA9ENOv=5HhuUr1fR42+khMJgQ4Ex0B7RmYAWT=+5vYiE=uO3g@mail.gmail.com>
Message-ID: <20160227072514.5e44d4d9@home.rlworkman.net>

On Fri, 26 Feb 2016 21:03:55 -0300
Ruan <ruan.klein at gmail.com> wrote:

> Hi,
> 
> I installed the LibreOffice via SlackBuild, but if run from terminal:
> 
> ~ $ soffice
> Application Error
> 
> I have no idea what it is.
> 
> * I updated manually to version 5.1, but the same error appears.


On -current?

Almost surely an issue with harfbuzz-1.1.3.

I think the next libreoffice version should have that fixed, as it
is a bug in LO.

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

From ruan.klein at gmail.com  Sat Feb 27 13:29:30 2016
From: ruan.klein at gmail.com (Ruan)
Date: Sat, 27 Feb 2016 10:29:30 -0300
Subject: [Slackbuilds-users] LibreOffice 5.0.5 "Application Error" (?)
In-Reply-To: <56D114AC.7030001@slackbuilds.org>
References: <CAA9ENOv=5HhuUr1fR42+khMJgQ4Ex0B7RmYAWT=+5vYiE=uO3g@mail.gmail.com>
 <56D114AC.7030001@slackbuilds.org>
Message-ID: <CAA9ENOsbfTE9mqiObeF7B1o4nbuQirFmNKbX4517_0xnOWWH+g@mail.gmail.com>

Hi Willy and Robby,

It is the libreoffice (binary repackaging) 5.0.5 from official SlackBuilds
git. My system: slackware current



2016-02-27 0:14 GMT-03:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:

> > I installed the LibreOffice via SlackBuild, but if run from terminal:
> >
> > ~ $ soffice
> > Application Error
> >
> > I have no idea what it is.
> >
> > * I updated manually to version 5.1, but the same error appears.
>
> Just to be clear, is the libreoffice (binary repackaging) or LibreOffice
> (compiled from source)?
>
> I used the libreoffice (binary repackaging) 5.1 and it's working fine here
>
>
> --
> Willy Sudiarto Raharjo
>
>
> _______________________________________________
> 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/
>
>
>


-- 
*Ruan *
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160227/9469ffcd/attachment.html>

From ruan.klein at gmail.com  Sat Feb 27 13:51:28 2016
From: ruan.klein at gmail.com (Ruan)
Date: Sat, 27 Feb 2016 10:51:28 -0300
Subject: [Slackbuilds-users] LibreOffice 5.0.5 "Application Error" (?)
In-Reply-To: <CAA9ENOsbfTE9mqiObeF7B1o4nbuQirFmNKbX4517_0xnOWWH+g@mail.gmail.com>
References: <CAA9ENOv=5HhuUr1fR42+khMJgQ4Ex0B7RmYAWT=+5vYiE=uO3g@mail.gmail.com>
 <56D114AC.7030001@slackbuilds.org>
 <CAA9ENOsbfTE9mqiObeF7B1o4nbuQirFmNKbX4517_0xnOWWH+g@mail.gmail.com>
Message-ID: <CAA9ENOupFdCUG59cTeOuBXUE6ZT2jVM4Yr1=MooNn1Yh35zNrQ@mail.gmail.com>

Well, I did a downgrade in the harfbuzz package to 1.1.2 and now works!

Thanks!

2016-02-27 10:29 GMT-03:00 Ruan <ruan.klein at gmail.com>:

> Hi Willy and Robby,
>
> It is the libreoffice (binary repackaging) 5.0.5 from official SlackBuilds
> git. My system: slackware current
>
>
>
> 2016-02-27 0:14 GMT-03:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>
> :
>
>> > I installed the LibreOffice via SlackBuild, but if run from terminal:
>> >
>> > ~ $ soffice
>> > Application Error
>> >
>> > I have no idea what it is.
>> >
>> > * I updated manually to version 5.1, but the same error appears.
>>
>> Just to be clear, is the libreoffice (binary repackaging) or LibreOffice
>> (compiled from source)?
>>
>> I used the libreoffice (binary repackaging) 5.1 and it's working fine here
>>
>>
>> --
>> Willy Sudiarto Raharjo
>>
>>
>> _______________________________________________
>> 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/
>>
>>
>>
>
>
> --
> *Ruan *
>



-- 
*Ruan *
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160227/84cc5796/attachment.html>

From willysr at slackbuilds.org  Sat Feb 27 14:04:23 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 27 Feb 2016 21:04:23 +0700
Subject: [Slackbuilds-users] LibreOffice 5.0.5 "Application Error" (?)
In-Reply-To: <20160227072514.5e44d4d9@home.rlworkman.net>
References: <CAA9ENOv=5HhuUr1fR42+khMJgQ4Ex0B7RmYAWT=+5vYiE=uO3g@mail.gmail.com>
 <20160227072514.5e44d4d9@home.rlworkman.net>
Message-ID: <56D1ACE7.5060504@slackbuilds.org>

>> I installed the LibreOffice via SlackBuild, but if run from terminal:
>>
>> ~ $ soffice
>> Application Error
>>
>> I have no idea what it is.
>>
>> * I updated manually to version 5.1, but the same error appears.
> 
> 
> On -current?
> 
> Almost surely an issue with harfbuzz-1.1.3.
> 
> I think the next libreoffice version should have that fixed, as it
> is a bug in LO.

Yes, that's why i put the LO 5.1 in a separate branch until that bug is
sorted out then we can merge it into master


-- 
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/20160227/3d8c50b4/attachment.asc>

From rworkman at slackbuilds.org  Sat Feb 27 14:07:59 2016
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 27 Feb 2016 08:07:59 -0600
Subject: [Slackbuilds-users] LibreOffice 5.0.5 "Application Error" (?)
In-Reply-To: <56D1ACE7.5060504@slackbuilds.org>
References: <CAA9ENOv=5HhuUr1fR42+khMJgQ4Ex0B7RmYAWT=+5vYiE=uO3g@mail.gmail.com>
 <20160227072514.5e44d4d9@home.rlworkman.net>
 <56D1ACE7.5060504@slackbuilds.org>
Message-ID: <20160227080759.7647976d@home.rlworkman.net>

On Sat, 27 Feb 2016 21:04:23 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> > On -current?
> > 
> > Almost surely an issue with harfbuzz-1.1.3.
> > 
> > I think the next libreoffice version should have that fixed, as it
> > is a bug in LO.  
> 
> Yes, that's why i put the LO 5.1 in a separate branch until that bug
> is sorted out then we can merge it into master


It's an issue with the other LibreOffice versions too (i.e. the older
ones don't work either), so you may as well merge it now.

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

From willysr at slackbuilds.org  Sat Feb 27 14:08:53 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 27 Feb 2016 21:08:53 +0700
Subject: [Slackbuilds-users] LibreOffice 5.0.5 "Application Error" (?)
In-Reply-To: <20160227080759.7647976d@home.rlworkman.net>
References: <CAA9ENOv=5HhuUr1fR42+khMJgQ4Ex0B7RmYAWT=+5vYiE=uO3g@mail.gmail.com>
 <20160227072514.5e44d4d9@home.rlworkman.net>
 <56D1ACE7.5060504@slackbuilds.org>
 <20160227080759.7647976d@home.rlworkman.net>
Message-ID: <56D1ADF5.8020002@slackbuilds.org>

>> Yes, that's why i put the LO 5.1 in a separate branch until that bug
>> is sorted out then we can merge it into master
> 
> 
> It's an issue with the other LibreOffice versions too (i.e. the older
> ones don't work either), so you may as well merge it now.

will do

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/20160227/d68faada/attachment-0001.asc>

From willysr at slackbuilds.org  Sat Feb 27 16:07:47 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 27 Feb 2016 23:07:47 +0700
Subject: [Slackbuilds-users] Error building inkscape-0.91
In-Reply-To: <CAMwjf3VSOLLV2_jXuYE7+93jvuawcsg+fmEg22evQ3rwvz7C0A@mail.gmail.com>
References: <20160225235544.GA11640@dimstar.local.net>
 <CALrQ46CYnEaJ5C3U84Y7XwZZGw09DwZd3fGAswSZMds+ptO9_A@mail.gmail.com>
 <56D010B8.7080007@slackbuilds.org>
 <CAMwjf3VSOLLV2_jXuYE7+93jvuawcsg+fmEg22evQ3rwvz7C0A@mail.gmail.com>
Message-ID: <DD762DF6-C37A-4E46-B820-721A630C4D9B@slackbuilds.org>


> But on my system running on Slackware-14.2 Beta-2 of 23-Feb-2016, Inkscape is not building. I get the error message given below

Hi Ananda

Did you sync the latest master branch? 


--
Willy Sudiarto Raharjo

From mail_me at riseup.net  Sun Feb 28 18:38:05 2016
From: mail_me at riseup.net (y)
Date: Sun, 28 Feb 2016 19:38:05 +0100
Subject: [Slackbuilds-users] OSSv4 patch for Slackware 14.2
Message-ID: <56D33E8D.4000704@riseup.net>

Hi folks

I've noticed that the OSSv4 build 2011 package for Slackware 14.2 was
not working correctly, so after some tweaking and researching I
finally got it working.

I've merged all previous patches into one patch. It includes
1. gcc-5.patch
2. remove-hal.patch
3. rm-init-scripts.patch
4. kmod-link.patch
5. ossvermagic.patch
6. linux-4.0.patch
7. added return 1; for USB output
8. changed grc_max and CONFIG_OSS_GRC_MAX_QUALITY to 6 in order to make 
use of the "src_quality=6" setting in osscore.conf


./configure --enable-libsalsa=NO --regparm

Note that the patch now uses /usr/lib64 by default. If you're using a
32 bit system you have to revert the change in the OSSv4 configure
file before compiling.

Here's the raw patch:
https://paste.clickbait.eu/view/raw/2b041525

To get rid of the annoying stuttering I've changed a few settings in 
/usr/lib64/oss/conf/osscore.conf
----------------------------
max_intrate=1000
src_quality=6
cooked_enable=0
-----------------------------

Cooked mode seems to be the main cause of stuttering.

And with pulseaudio enabled it works fine with all browsers and other
applications that do not support OSSv4 natively.

Happy testing.

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

From thedoogster at gmail.com  Sun Feb 28 18:44:44 2016
From: thedoogster at gmail.com (Doogster)
Date: Sun, 28 Feb 2016 10:44:44 -0800
Subject: [Slackbuilds-users] OSSv4 patch for Slackware 14.2
In-Reply-To: <56D33E8D.4000704@riseup.net>
References: <56D33E8D.4000704@riseup.net>
Message-ID: <CAE5oDaZqek5+T2+6eUzxq1Kwt1m+=uXRHLFm_x2DkQDdeU57dw@mail.gmail.com>

Thanks for that.

And if you missed the earlier thread where the OSSv4 SlackBuild
maintainer changed, it's now B Watson.

On Sun, Feb 28, 2016 at 10:38 AM, y <mail_me at riseup.net> wrote:
> Hi folks
>
> I've noticed that the OSSv4 build 2011 package for Slackware 14.2 was
> not working correctly, so after some tweaking and researching I
> finally got it working.
>
> I've merged all previous patches into one patch. It includes
> 1. gcc-5.patch
> 2. remove-hal.patch
> 3. rm-init-scripts.patch
> 4. kmod-link.patch
> 5. ossvermagic.patch
> 6. linux-4.0.patch
> 7. added return 1; for USB output
> 8. changed grc_max and CONFIG_OSS_GRC_MAX_QUALITY to 6 in order to make use
> of the "src_quality=6" setting in osscore.conf
>
>
> ./configure --enable-libsalsa=NO --regparm
>
> Note that the patch now uses /usr/lib64 by default. If you're using a
> 32 bit system you have to revert the change in the OSSv4 configure
> file before compiling.
>
> Here's the raw patch:
> https://paste.clickbait.eu/view/raw/2b041525
>
> To get rid of the annoying stuttering I've changed a few settings in
> /usr/lib64/oss/conf/osscore.conf
> ----------------------------
> max_intrate=1000
> src_quality=6
> cooked_enable=0
> -----------------------------
>
> Cooked mode seems to be the main cause of stuttering.
>
> And with pulseaudio enabled it works fine with all browsers and other
> applications that do not support OSSv4 natively.
>
> Happy testing.
>
>
> _______________________________________________
> 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 chipwzxc at gmail.com  Sun Feb 28 20:20:52 2016
From: chipwzxc at gmail.com (Chip Widmer)
Date: Sun, 28 Feb 2016 15:20:52 -0500
Subject: [Slackbuilds-users] Possible issue with "nvidia-kernel"
Message-ID: <20160228202052.GA13554@plethora>

Hello,

My apologies if I'm just overlooking something, but there seems to be an
issue with the "nvidia-kernel" Slackbuild, where the nvidia-uvm.ko
module doesn't get built and installed.

The script calls "unset ARCH", and then later uses ARCH to check if the
system is x86_64. I've attached a small patch which instead uses TARGET
for the check.

Thanks,
Chip


From chipwzxc at gmail.com  Sun Feb 28 20:24:44 2016
From: chipwzxc at gmail.com (Chip Widmer)
Date: Sun, 28 Feb 2016 15:24:44 -0500
Subject: [Slackbuilds-users] Possible issue with "nvidia-kernel"
In-Reply-To: <20160228202052.GA13554@plethora>
References: <20160228202052.GA13554@plethora>
Message-ID: <CAEJFXVAGLpcUFV-phYs=MnWNQShGy98N7nxdkZkEOwRmg_ZwTw@mail.gmail.com>

It appears I forgot the attachment.

On Sun, Feb 28, 2016 at 3:20 PM, Chip Widmer <chipwzxc at gmail.com> wrote:
> Hello,
>
> My apologies if I'm just overlooking something, but there seems to be an
> issue with the "nvidia-kernel" Slackbuild, where the nvidia-uvm.ko
> module doesn't get built and installed.
>
> The script calls "unset ARCH", and then later uses ARCH to check if the
> system is x86_64. I've attached a small patch which instead uses TARGET
> for the check.
>
> Thanks,
> Chip
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nvidia-kernel.SlackBuild.patch
Type: text/x-patch
Size: 850 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160228/af88bbe2/attachment.bin>

From jbernts at broadpark.no  Mon Feb 29 17:04:29 2016
From: jbernts at broadpark.no (Jostein Berntsen)
Date: Mon, 29 Feb 2016 18:04:29 +0100
Subject: [Slackbuilds-users] adobe-reader error
Message-ID: <20160229170429.GA21136@jostein>

Running acroread after installing adobe-reader gives this error:

/usr/bin/acroread: line 22: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: No such file or directory

Looking in the referenced directory a binary acroread file exists there.
Anything to check here?


Jostein

From didier at slint.fr  Mon Feb 29 17:08:57 2016
From: didier at slint.fr (Didier Spaier)
Date: Mon, 29 Feb 2016 18:08:57 +0100
Subject: [Slackbuilds-users] adobe-reader error
In-Reply-To: <20160229170429.GA21136@jostein>
References: <20160229170429.GA21136@jostein>
Message-ID: <56D47B29.1030603@slint.fr>

On 29/02/2016 18:04, Jostein Berntsen wrote:
> Running acroread after installing adobe-reader gives this error:
> 
> /usr/bin/acroread: line 22:
> /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: No such file or
> directory
> 
> Looking in the referenced directory a binary acroread file exists there.
> Anything to check here?

Blind guess: you installed it on x86_64 aka 65-bit Slackwaren but
that is not supported. To check type:
uname -m
file /opt/Adobe/Reader9/Reader/intellinux/bin/acroread

From pessoal at profcavalheiro.com  Mon Feb 29 17:11:11 2016
From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro)
Date: Mon, 29 Feb 2016 14:11:11 -0300
Subject: [Slackbuilds-users] adobe-reader error
In-Reply-To: <20160229170429.GA21136@jostein>
References: <20160229170429.GA21136@jostein>
Message-ID: <20160229141111.445efb48.pessoal@profcavalheiro.com>

What can you find in /opt/Adobe in your machine?

Em 29 de 02 de 2016 ?s 18:04:29T+0100, Jostein Berntsen <jbernts at broadpark.no> escreveu:

> Running acroread after installing adobe-reader gives this error:
> 
> /usr/bin/acroread: line 22: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: No such file or directory
> 
> Looking in the referenced directory a binary acroread file exists there.
> Anything to check here?
> 
> 
> Jostein
> _______________________________________________
> 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/
> 


-- 
93 93/93
Lu?s Fernando Carvalho Cavalheiro
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Assinatura digital OpenPGP
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160229/9441e90c/attachment-0001.asc>

From didier at slint.fr  Mon Feb 29 17:12:35 2016
From: didier at slint.fr (Didier Spaier)
Date: Mon, 29 Feb 2016 18:12:35 +0100
Subject: [Slackbuilds-users] adobe-reader error
In-Reply-To: <56D47B29.1030603@slint.fr>
References: <20160229170429.GA21136@jostein> <56D47B29.1030603@slint.fr>
Message-ID: <56D47C03.1090408@slint.fr>

On 29/02/2016 18:08, Didier Spaier wrote:
> Blind guess: you installed it on x86_64 aka 65-bit Slackwaren but

Sorry for the typos. 65-bit architecture is yet to be invented...

Dider

From kingbeowulf at gmail.com  Mon Feb 29 18:43:13 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 29 Feb 2016 10:43:13 -0800
Subject: [Slackbuilds-users] Possible issue with "nvidia-kernel"
In-Reply-To: <CAEJFXVAGLpcUFV-phYs=MnWNQShGy98N7nxdkZkEOwRmg_ZwTw@mail.gmail.com>
References: <20160228202052.GA13554@plethora>
 <CAEJFXVAGLpcUFV-phYs=MnWNQShGy98N7nxdkZkEOwRmg_ZwTw@mail.gmail.com>
Message-ID: <56D49141.30500@gmail.com>

On 02/28/2016 12:24 PM, Chip Widmer wrote:
> It appears I forgot the attachment.
> 
> On Sun, Feb 28, 2016 at 3:20 PM, Chip Widmer <chipwzxc at gmail.com> wrote:
>> Hello,
>>
>> My apologies if I'm just overlooking something, but there seems to be an
>> issue with the "nvidia-kernel" Slackbuild, where the nvidia-uvm.ko
>> module doesn't get built and installed.
>>
>> The script calls "unset ARCH", and then later uses ARCH to check if the
>> system is x86_64. I've attached a small patch which instead uses TARGET
>> for the check.
>>
>> Thanks,
>> Chip
>>

Confirmed, thanks.  I will have a work with my QA department.  This will
sting come bonus time.

Admins, please fix and backport to 14.1. Thanks.


-------------- 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/20160229/e2b7d198/attachment.asc>

From atelszewski at gmail.com  Mon Feb 29 19:57:29 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 29 Feb 2016 20:57:29 +0100
Subject: [Slackbuilds-users] libev source downloaded by web browser cannot
	be extracted by tar
Message-ID: <56D4A2A9.6080805@gmail.com>

Hi,

Just for your information:

$ md5sum libev-4.15.tar.gz_seamonkey
bd3fe50a18a86f977f91cfc46783f52d  libev-4.15.tar.gz_seamonkey

$ md5sum libev-4.15.tar.gz_wget
3a73f247e790e2590c01f3492136ed31  libev-4.15.tar.gz_wget

$ tar -xf libev-4.15.tar.gz_seamonkey
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors

$ bsdtar -xf libev-4.15.tar.gz_seamonkey

$ tar -xf libev-4.15.tar.gz_wget

$ bsdtar -xf libev-4.15.tar.gz_wget


Probably not the concern of SBo, but if the source of libev is 
downloaded using web browser, e.g. SeaMonkey, it cannot be extracted 
using tar.

As can be seen from the commands output above:
- MD5 sums are different, depending if the source was downloaded using 
web browser or wget,
- tar is not able to extract the source downloaded using SeaMonkey, but 
is able to extract source downloaded by wget,
- bsdtar can extract source downloaded using SeaMonkey and wget.

If using links, the MD5 is the same as for wget.

The moral is, don't use GUI tools ;)

-- 
Best regards,
Andrzej Telszewski

From didier at slint.fr  Mon Feb 29 20:11:02 2016
From: didier at slint.fr (Didier Spaier)
Date: Mon, 29 Feb 2016 21:11:02 +0100
Subject: [Slackbuilds-users] libev source downloaded by web browser
 cannot be extracted by tar
In-Reply-To: <56D4A2A9.6080805@gmail.com>
References: <56D4A2A9.6080805@gmail.com>
Message-ID: <56D4A5D6.5090304@slint.fr>

On 29/02/2016 20:57, Andrzej Telszewski wrote:
> $ md5sum libev-4.15.tar.gz_seamonkey
> bd3fe50a18a86f977f91cfc46783f52d  libev-4.15.tar.gz_seamonkey
> 
> $ md5sum libev-4.15.tar.gz_wget
> 3a73f247e790e2590c01f3492136ed31  libev-4.15.tar.gz_wget
> 
> $ tar -xf libev-4.15.tar.gz_seamonkey
> tar: This does not look like a tar archive
> tar: Skipping to next header
> tar: Exiting with failure status due to previous errors
> 
> $ bsdtar -xf libev-4.15.tar.gz_seamonkey
> 
> $ tar -xf libev-4.15.tar.gz_wget
> 
> $ bsdtar -xf libev-4.15.tar.gz_wget
> 
> 
> Probably not the concern of SBo, but if the source of libev is
> downloaded using web browser, e.g. SeaMonkey, it cannot be extracted
> using tar.
> 
> As can be seen from the commands output above:
> - MD5 sums are different, depending if the source was downloaded using
> web browser or wget,
> - tar is not able to extract the source downloaded using SeaMonkey, but
> is able to extract source downloaded by wget,
> - bsdtar can extract source downloaded using SeaMonkey and wget.
> 
> If using links, the MD5 is the same as for wget.
> 
> The moral is, don't use GUI tools ;)

You are not alone.
http://www.linuxquestions.org/questions/slackware-14/%5Bannounce%5D-eudev-for-slackware-14-1-is-available-for-testing-purposes-4175505218/page2.html#post5174868
The browser's behavior can probably be corrected using proper settings
in about:config or something, but I agree: it's often safer to use
command line tools.

Didier

From atelszewski at gmail.com  Mon Feb 29 20:50:16 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 29 Feb 2016 21:50:16 +0100
Subject: [Slackbuilds-users] libev source downloaded by web browser
 cannot be extracted by tar
In-Reply-To: <56D4A5D6.5090304@slint.fr>
References: <56D4A2A9.6080805@gmail.com> <56D4A5D6.5090304@slint.fr>
Message-ID: <56D4AF08.8070104@gmail.com>

On 29/02/16 21:11, Didier Spaier wrote:
> On 29/02/2016 20:57, Andrzej Telszewski wrote:
>> $ md5sum libev-4.15.tar.gz_seamonkey
>> bd3fe50a18a86f977f91cfc46783f52d  libev-4.15.tar.gz_seamonkey
>>
>> $ md5sum libev-4.15.tar.gz_wget
>> 3a73f247e790e2590c01f3492136ed31  libev-4.15.tar.gz_wget
>>
>> $ tar -xf libev-4.15.tar.gz_seamonkey
>> tar: This does not look like a tar archive
>> tar: Skipping to next header
>> tar: Exiting with failure status due to previous errors
>>
>> $ bsdtar -xf libev-4.15.tar.gz_seamonkey
>>
>> $ tar -xf libev-4.15.tar.gz_wget
>>
>> $ bsdtar -xf libev-4.15.tar.gz_wget
>>
>>
>> Probably not the concern of SBo, but if the source of libev is
>> downloaded using web browser, e.g. SeaMonkey, it cannot be extracted
>> using tar.
>>
>> As can be seen from the commands output above:
>> - MD5 sums are different, depending if the source was downloaded using
>> web browser or wget,
>> - tar is not able to extract the source downloaded using SeaMonkey, but
>> is able to extract source downloaded by wget,
>> - bsdtar can extract source downloaded using SeaMonkey and wget.
>>
>> If using links, the MD5 is the same as for wget.
>>
>> The moral is, don't use GUI tools ;)
>
> You are not alone.
> http://www.linuxquestions.org/questions/slackware-14/%5Bannounce%5D-eudev-for-slackware-14-1-is-available-for-testing-purposes-4175505218/page2.html#post5174868
> The browser's behavior can probably be corrected using proper settings
> in about:config or something, but I agree: it's often safer to use
> command line tools.
>

I changed _network.http.accept-encoding_ as you proposed in the post and 
now the download is correct.

Thanks!

> Didier
> _______________________________________________
> 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