From johnywhy at gmail.com  Fri May  1 02:38:27 2015
From: johnywhy at gmail.com (johny why)
Date: Fri, 1 May 2015 10:38:27 +0800
Subject: [Slackbuilds-users] Cannot Install PlayOnLinux
Message-ID: <CA+jNr66fBB+BeOTQYnHKaaOfcuf06w_XHbTxcNxhBh+C=Y7Atw@mail.gmail.com>

hi

total noob.

tried to compile PlayOnLinux_4.2.5.tar.gz, using:

playonlinux.SlackBuild

I got 'no such file or directory' on: "/sbin/makepkg".

i noticed there is no /sbin directory, which might explain the error.

i changed 'sbin' to 'bin' in the maker script, and same error. So it's
missing makepkg.....

what am i doing wrong?

running xSlacko, based on Slacko, a Slackware-based Puppy Linux
http://puppylinux.org/wikka/Puppy53
http://slacko.01micko.com/download.html
http://distrowatch.com/?newsid=08342

thx!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150501/1ffa2160/attachment.html>

From willysr at slackbuilds.org  Fri May  1 02:46:24 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 01 May 2015 09:46:24 +0700
Subject: [Slackbuilds-users] Cannot Install PlayOnLinux
In-Reply-To: <CA+jNr66fBB+BeOTQYnHKaaOfcuf06w_XHbTxcNxhBh+C=Y7Atw@mail.gmail.com>
References: <CA+jNr66fBB+BeOTQYnHKaaOfcuf06w_XHbTxcNxhBh+C=Y7Atw@mail.gmail.com>
Message-ID: <5542E900.7030902@slackbuilds.org>

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

> tried to compile PlayOnLinux_4.2.5.tar.gz, using:
> 
> playonlinux.SlackBuild
> 
> I got 'no such file or directory' on: "/sbin/makepkg".
> 
> i noticed there is no /sbin directory, which might explain the
> error.
> 
> i changed 'sbin' to 'bin' in the maker script, and same error. So
> it's missing makepkg.....
> 
> what am i doing wrong?
> 
> running xSlacko, based on Slacko, a Slackware-based Puppy Linux

I don't use xSlacko, but can you check if there's pkgtool in your list
of packages?


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVC6QAACgkQiHuDdNczM4FIlwCfftauqxoz/wyc6lySG8xaom3w
qC4An2SrYugNFk6jnDTIEXPr1MPk0x40
=3bZ1
-----END PGP SIGNATURE-----

From miguel at thedeanda.com  Fri May  1 04:44:49 2015
From: miguel at thedeanda.com (Miguel De Anda)
Date: Thu, 30 Apr 2015 21:44:49 -0700
Subject: [Slackbuilds-users] can't install flashplayer-plugin
Message-ID: <CAA62KfSNonkw_C3DbRRFM4zORM0tBkKHSu=YbEgYcjgSbipTJQ@mail.gmail.com>

mv: cannot stat '/tmp/SBo/package-flashplayer-plugin/LGPL/*': No such file
or directory


i guess they removed the directory/file with the latest release?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150430/a2d15848/attachment.html>

From kingbeowulf at gmail.com  Fri May  1 06:07:07 2015
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 30 Apr 2015 23:07:07 -0700
Subject: [Slackbuilds-users] Cannot Install PlayOnLinux
In-Reply-To: <CA+jNr66fBB+BeOTQYnHKaaOfcuf06w_XHbTxcNxhBh+C=Y7Atw@mail.gmail.com>
References: <CA+jNr66fBB+BeOTQYnHKaaOfcuf06w_XHbTxcNxhBh+C=Y7Atw@mail.gmail.com>
Message-ID: <CAPiArqOPs=xi_ggzceWRu3Dhd6ESMM-GDqEvx34d=nWaH_zBiQ@mail.gmail.com>

On Thursday, April 30, 2015, johny why <johnywhy at gmail.com> wrote:

> hi
>
> total noob.
>
> tried to compile PlayOnLinux_4.2.5.tar.gz, using:
>
> playonlinux.SlackBuild
>
> I got 'no such file or directory' on: "/sbin/makepkg".
>
> i noticed there is no /sbin directory, which might explain the error.
>
> i changed 'sbin' to 'bin' in the maker script, and same error. So it's
> missing makepkg.....
>
> what am i doing wrong?
>
> running xSlacko, based on Slacko, a Slackware-based Puppy Linux
> http://puppylinux.org/wikka/Puppy53
> http://slacko.01micko.com/download.html
> http://distrowatch.com/?newsid=08342
>
> thx!
>

It's been awhile since I played with slacko and derivs, but I recall that
slacko puppy has its own package management system. slacko is "binary
compatible" with Slackware (as of whatever version it's based on), but that
does not mean you can make Slackware packages from source.

Thus, if you want to create a Slackware binary Package (tar.gz or tar.xz),
you need Slackware to create it from the Slackbuilds.org (SBo) scripts.
Then you can install that binary using the slacko package tools.  You
really

Or you can check out precompiled packages at slacky.eu or Salix, or several
other slackware binary repos.

Finally, the SBo scripts expect that you have:
1.  A full Slackware install - any compile dependencies not listed are
expected to be already installed by default.
2.  Slackware's package tools package
3.  The script needs to be run as the root user.

Have fun!





-- 
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/20150430/91828455/attachment.html>

From klaatu at straightedgelinux.com  Fri May  1 06:48:36 2015
From: klaatu at straightedgelinux.com (Klaatu)
Date: Fri, 01 May 2015 18:48:36 +1200
Subject: [Slackbuilds-users] can't install flashplayer-plugin
In-Reply-To: <CAA62KfSNonkw_C3DbRRFM4zORM0tBkKHSu=YbEgYcjgSbipTJQ@mail.gmail.com>
References: <CAA62KfSNonkw_C3DbRRFM4zORM0tBkKHSu=YbEgYcjgSbipTJQ@mail.gmail.com>
Message-ID: <554321C4.8070204@straightedgelinux.com>

On 05/01/2015 04:44 PM, Miguel De Anda wrote:
> mv: cannot stat '/tmp/SBo/package-flashplayer-plugin/LGPL/*': No such file
> or directory
> 
> 
> i guess they removed the directory/file with the latest release?
> 
> 
> 
> _______________________________________________
> 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/
> 
This isn't quite an answer, but I have switched to the pepperflash
solution; use the Flash plugin from the Chromium-base. Works a heck of a
lot better than the aging flashplayer straight from Adobe.

AlienBob has a build of it:
http://www.slackware.com/~alien/slackbuilds/chromium-pepperflash-plugin/pkg64/14.1/



-klaatu

From willysr at slackbuilds.org  Fri May  1 07:52:01 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 01 May 2015 14:52:01 +0700
Subject: [Slackbuilds-users] can't install flashplayer-plugin
In-Reply-To: <CAA62KfSNonkw_C3DbRRFM4zORM0tBkKHSu=YbEgYcjgSbipTJQ@mail.gmail.com>
References: <CAA62KfSNonkw_C3DbRRFM4zORM0tBkKHSu=YbEgYcjgSbipTJQ@mail.gmail.com>
Message-ID: <554330A1.4010205@slackbuilds.org>

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

> mv: cannot stat '/tmp/SBo/package-flashplayer-plugin/LGPL/*': No
> such file or directory
> 
> 
> i guess they removed the directory/file with the latest release?

I Don't think so

tar tvf install_flash_player_11_linux.i386.tar.gz
- -rw-rw-r-- flplbldr/flplbldr 17437860 2015-04-12 08:26 libflashplayer.so
- -r--r--r-- flplbldr/flplbldr     4009 2015-04-12 08:26 readme.txt
drwxrwxr-x flplbldr/flplbldr        0 2015-04-12 08:26 LGPL/
- -r--r--r-- flplbldr/flplbldr     7402 2015-04-12 08:26 LGPL/LGPL.txt
- -r--r--r-- flplbldr/flplbldr       76 2015-04-12 08:26 LGPL/notice.txt


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVDMKEACgkQiHuDdNczM4FIUACfWrriqwigAY5paZQKXwDOGu3B
kwYAnAhw4pA9iqSS5XSFLh3L2kuJsnCM
=4zRT
-----END PGP SIGNATURE-----

From info at microlinux.fr  Fri May  1 08:16:44 2015
From: info at microlinux.fr (Niki Kovacs)
Date: Fri, 01 May 2015 10:16:44 +0200
Subject: [Slackbuilds-users] Two questions about building GNOME apps
Message-ID: <5543366C.4020506@microlinux.fr>

Hi,

I have two questions about building GNOME apps.

1. Some applications use the following option:

   --disable-scrollkeeper

What exactly does this do?

2. Some applications use this build option:

   -- disable-schemas-install

or sometimes:

   --disable-schemas-compile

Usually, the corresponding doinst.sh contains something similar to this:

if [ -e usr/share/glib-2.0/schemas ]; then
   if [ -x /usr/bin/glib-compile-schemas ]; then
     /usr/bin/glib-compile-schemas usr/share/glib-2.0/schemas >/dev/null 
2>&1
   fi
fi

What exactly does this do?

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  Fri May  1 08:32:58 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 01 May 2015 15:32:58 +0700
Subject: [Slackbuilds-users] Two questions about building GNOME apps
In-Reply-To: <5543366C.4020506@microlinux.fr>
References: <5543366C.4020506@microlinux.fr>
Message-ID: <55433A3A.40509@slackbuilds.org>

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

On 05/01/2015 03:16 PM, Niki Kovacs wrote:
> Hi,
> 
> I have two questions about building GNOME apps.
> 
> 1. Some applications use the following option:
> 
> --disable-scrollkeeper
> 
> What exactly does this do?


Taken from some sources online

What is scrollkeeper?

ScrollKeeper is a cataloging system for documentation on open systems.
It manages documentation metadata and provides a simple API to allow
help browsers to find, sort, and search the document catalog.

AFAIK nothing beyond the Gnome and KDE help browsers does anything
usefull with it.

How does it work?

Scrollkeeper reads files with meta data (provided in the packages of
programs that use this) and templates (provided by the scrollkeeper
package). It combines these into a database. This database can in turn
be read by the help browsers.

What does this mean for package builders?

Packages for programs that provide information through scrollkeeper
should contain *.omf files and put these in a directory under
${DEST}/usr/share/omf. If this directory is created, but does not
contain any files, then there probably went something wrong in the
build process.

The make install process for some programs generates a scrollkeeper
database under ${DEST}/var/lib/scrollkeeper or
${DEST}/var/scrollkeeper. Since the scrollkeeper database is a system
wide resource and system specific, these files should not end up in
the package. So the build scripts for programs that do this should
contain some command to remove this redundant database.

The database on the system where the package will be installed does
not update automatically when new files appear under /usr/share/omf.
So the doinst.sh script must take care of updating the scrollkeeper
database.

> 2. Some applications use this build option:
> 
> -- disable-schemas-install
> 
> or sometimes:
> 
> --disable-schemas-compile
> 
> Usually, the corresponding doinst.sh contains something similar to
> this:
> 
> if [ -e usr/share/glib-2.0/schemas ]; then if [ -x
> /usr/bin/glib-compile-schemas ]; then /usr/bin/glib-compile-schemas
> usr/share/glib-2.0/schemas >/dev/null 2>&1 fi fi
> 
> What exactly does this do?

What is gconf?

GConf is a configuration scheme currently used by the GNOME desktop.
Programs which use it setup default values in a $NAME.schemas file
which is installed under /etc/gconf/schemas/$NAME.schemas. These
defaults are then registered with the gconf daemon which monitors the
configuration values and alerts applications when values the
applications are interested in change. The schema files also provide
documentation about what each value in the configuration system means
(which gets displayed when you browse the database in the gconf-editor
program).

For packaging purposes, we have to disable schema installation during
build, or these will get installed in the packager's system instead of
put in the package itself. They can then be created and placed in the
package manually.

Disabling schemas installation

When a package requires the installation of gconf schemas, there is
usually a "--disable-schemas-install" configure option that can be
used to not let the makefile install any schemas to the system. You
can check if the configure script provides such an option with
"configure --help".


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVDOjoACgkQiHuDdNczM4EuXgCfbge/DXQ9ya1C/1q/k9YKsw1a
GnQAniMM00qEVxhgXUgN/lrcQDOM6Xub
=nIXe
-----END PGP SIGNATURE-----

From info at microlinux.fr  Fri May  1 08:40:21 2015
From: info at microlinux.fr (Niki Kovacs)
Date: Fri, 01 May 2015 10:40:21 +0200
Subject: [Slackbuilds-users] Two questions about building GNOME apps
In-Reply-To: <55433A3A.40509@slackbuilds.org>
References: <5543366C.4020506@microlinux.fr> <55433A3A.40509@slackbuilds.org>
Message-ID: <55433BF5.6020608@microlinux.fr>

Le 01/05/2015 10:32, Willy Sudiarto Raharjo a ?crit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 05/01/2015 03:16 PM, Niki Kovacs wrote:
>> Hi,
>>
>> I have two questions about building GNOME apps.
>>
>> 1. Some applications use the following option:
>>
>> --disable-scrollkeeper
>>
>> What exactly does this do?
>
>
> Taken from some sources online
>
> What is scrollkeeper?
>
> ScrollKeeper is a cataloging system for documentation on open systems.
> It manages documentation metadata and provides a simple API to allow
> help browsers to find, sort, and search the document catalog.
>
> AFAIK nothing beyond the Gnome and KDE help browsers does anything
> usefull with it.
>
> How does it work?
>
  <snip>

Thank you very much for your detailed explanation, Willy!

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 bocke at mycity.rs  Fri May  1 09:43:25 2015
From: bocke at mycity.rs (Bojan Popovic)
Date: Fri, 1 May 2015 11:43:25 +0200
Subject: [Slackbuilds-users] Two questions about building GNOME apps
In-Reply-To: <55433A3A.40509@slackbuilds.org>
References: <5543366C.4020506@microlinux.fr> <55433A3A.40509@slackbuilds.org>
Message-ID: <20150501114325.7c879fa2@artwo.universe.uni>

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

Great description. I would just add a comment or two of my own.

In modern Gnome, Scrollkeeper (last release: 2003) was replaced by a
Freedesktop project called "rarian" (available on SBo). It is "in place"
replacement of Scrollkeeper and is used to generate Yelp documentation
(Gnome's help system). So, it's usually pretty much optional.  

Cheers,

Bojan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJVQ0q9AAoJEBOUH7bZ9xhefmgP/10bcBEMB4zBzBc6KBjhLl2J
xdO0qY61UueQQmTiDLCM+JU8quE/zMEUGWOs6zr5Bx03Cxe8oStFwjwGJ7xTWacz
1jT5PNLE0ubBHizYT7Suv9WfVwnnEXsTpD5//UHieo/Priv5p8kVaAmJfQ14ax07
oJmNCAvXL8pYTNz0cSm5IgqlnjNj8Srp5c5DLIjiuUAybWvYBS7CgjpI6vT4dvpj
mtMn05IRrwhgBVFBCmTQHgH+eOe1cgj0qdJeG9fW87C+t6NpEy+LZChcZZQPCJxa
wTZ650uS/nlqhe5C0WbPnoroxaYTvQ1wbSf2AtezbiSBW0fBW6BaIImCafjjr0Bt
L4HnIvE7l+vhDV2vlSJnJNDz4U3Rl8g3xPsrEmIktWgTIQq/dTorwU289nT2Sj1L
A8AaYzoS/2hsliR231gQAvl3/1zO856k0NimiV3k6dPdNT5s1cXtShtgADgHdb0v
l5Zyn0oAvUeGe6ASIemvGUKF93Ct7a/ZxSmPzeTQzGq2MocJmLGrzrzprNVauiQG
7t3L7lbtQD6LyqnCuvMo7gntQ+M/snQLc86AREIgniYjD42xZZ/SgkuCvBsu0i4l
LvRu3wIZEmUQsa+HARmMfaSFvBGyxTONL73DZzj1CIJYY55u8ZLtakiWlY6XKpda
hDEeoxcdnO16S6Zab+fv
=o7KD
-----END PGP SIGNATURE-----

From xavier at maillard.im  Fri May  1 13:43:36 2015
From: xavier at maillard.im (Xavier Maillard)
Date: Fri, 01 May 2015 15:43:36 +0200
Subject: [Slackbuilds-users] =?utf-8?q?Op=C3=A9ration_repr=C3=A9saille_=3F?=
 =?utf-8?q?_=28was=3A__Two_questions_about_building_GNOME_apps=29?=
In-Reply-To: <55433BF5.6020608@microlinux.fr>
References: <5543366C.4020506@microlinux.fr> <55433A3A.40509@slackbuilds.org>
 <55433BF5.6020608@microlinux.fr>
Message-ID: <m0lhh8begn.fsf@kcals.intra.maillard.im>

Salut,

strictement rien ? voir avec le sujet mais je viens de d?couvrir en
parcourant ton site que tu ?tais poursuivi pour injure et
diffamation.

As-tu m?diatis? cette affaire dans le cercle des /hackers/ pour une
op?ration d'envergure ?

En tous cas, je salue ton civisme. Il faut nettoyer nos rues de
toutes cette puanteur qui l'envahit tous les jours un peu plus.

Cdt,
-- Xavier.

From xavier at maillard.im  Fri May  1 13:48:32 2015
From: xavier at maillard.im (Xavier Maillard)
Date: Fri, 01 May 2015 15:48:32 +0200
Subject: [Slackbuilds-users]
 =?utf-8?q?Op=C3=A9ration_repr=C3=A9saille__?=
 =?utf-8?q?=3F_=28was=3A__Two_questions_about_building_GNOME_apps=29?=
In-Reply-To: <m0lhh8begn.fsf@kcals.intra.maillard.im>
References: <5543366C.4020506@microlinux.fr> <55433A3A.40509@slackbuilds.org>
 <55433BF5.6020608@microlinux.fr> <m0lhh8begn.fsf@kcals.intra.maillard.im>
Message-ID: <m0ioccbe8f.fsf@kcals.intra.maillard.im>

Sorry, did a wrong Reply-to ALL ...

It should have stayed secret...

Cheers
-- Xavier.

From johnywhy at gmail.com  Fri May  1 21:55:08 2015
From: johnywhy at gmail.com (johny why)
Date: Sat, 2 May 2015 05:55:08 +0800
Subject: [Slackbuilds-users] Cannot Install PlayOnLinux
Message-ID: <CA+jNr667W4ZSpsK6Zcm74S3hj_TH+OD7R5wfkMbha8E4EonTZg@mail.gmail.com>

Many thanks, Willy S.R. and King B. I got my answer:

"makepkg is a script. Get it here and put it in /sbin (you do have it)."
http://ftp.slackware.no/slackware/slackware-12.0/source/a/pkgtools/scripts/makepkg

http://www.murga-linux.com/puppy/viewtopic.php?p=843131#843131

SlackBuilds said: "Package successfully created". I was then able to
install the package. Great!

But, new issue: i ran playonlinux.SlackBuild a second time, just for
giggles. I got:

tar: /root/PlayOnLinux_4.2.5.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

why is SlackBuild now looking for the source file in /root, instead of
in it's own directory?

thx!
ps, sorry if this breaks the thread, i'm replying to the digest version.


On 5/1/15, slackbuilds-users-request at slackbuilds.org
<slackbuilds-users-request at slackbuilds.org> wrote:
> Date: Fri, 01 May 2015 09:46:24 +0700
> From: Willy Sudiarto Raharjo <willysr at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] Cannot Install PlayOnLinux
> I don't use xSlacko, but can you check if there's pkgtool in your list
> of packages?
>


> Date: Thu, 30 Apr 2015 23:07:07 -0700
> From: King Beowulf <kingbeowulf at gmail.com>
> It's been awhile since I played with slacko and derivs, but I recall that
> slacko puppy has its own package management system. slacko is "binary
> compatible" with Slackware (as of whatever version it's based on), but that
> does not mean you can make Slackware packages from source.
>
> Thus, if you want to create a Slackware binary Package (tar.gz or tar.xz),
> you need Slackware to create it from the Slackbuilds.org (SBo) scripts.
> Then you can install that binary using the slacko package tools.
>
> Finally, the SBo scripts expect that you have:
> 1.  A full Slackware install - any compile dependencies not listed are
> expected to be already installed by default.
> 2.  Slackware's package tools package

From info at microlinux.fr  Sat May  2 06:29:16 2015
From: info at microlinux.fr (Niki Kovacs)
Date: Sat, 02 May 2015 08:29:16 +0200
Subject: [Slackbuilds-users] SquidGuard 1.4 vs. Squid 3.4 : patch for
	vanilla sources needed
Message-ID: <55446EBC.5090107@microlinux.fr>

Hi,

I'm using a combination of Squid and SquidGuard on my servers for web 
filtering, which is the "industrial grade" solution usable in schools 
and companies.

Up until recently, the combination worked well with Squid 3.3 and 
SquidGuard 1.4. Unfortunately, the upgrade to Squid 3.4 broke something, 
and SquidGuard doesn't work anymore.

I've googled a bit, and found out that SquidGuard 1.4 has to be patched 
in order to work with Squid >= 3.4.

Now I just spent some time hunting down that mysterious patch, but I 
failed, because all the patches are either distribution-specific 
(FreeBSD, Arch, etc.) and they don't work with vanilla sources, or the 
link to the original patch throws back a 404 error.

My guess is the SquidGuard application is quite badly maintained, 
judging from their homepage displaying a forest of patches and 
announcing a perpetual 1.5beta version for the last couple of years.

If anybody has an idea, that would be helpful.

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 info at microlinux.fr  Sat May  2 06:33:55 2015
From: info at microlinux.fr (Niki Kovacs)
Date: Sat, 02 May 2015 08:33:55 +0200
Subject: [Slackbuilds-users] SquidGuard 1.4 vs. Squid 3.4 : patch for
 vanilla sources needed
In-Reply-To: <55446EBC.5090107@microlinux.fr>
References: <55446EBC.5090107@microlinux.fr>
Message-ID: <55446FD3.5050301@microlinux.fr>

Le 02/05/2015 08:29, Niki Kovacs a ?crit :
> Hi,
>
> I'm using a combination of Squid and SquidGuard on my servers for web
> filtering, which is the "industrial grade" solution usable in schools
> and companies.
>
> Up until recently, the combination worked well with Squid 3.3 and
> SquidGuard 1.4. Unfortunately, the upgrade to Squid 3.4 broke something,
> and SquidGuard doesn't work anymore.
>
> I've googled a bit, and found out that SquidGuard 1.4 has to be patched
> in order to work with Squid >= 3.4.
>
> Now I just spent some time hunting down that mysterious patch, but I
> failed, because all the patches are either distribution-specific
> (FreeBSD, Arch, etc.) and they don't work with vanilla sources, or the
> link to the original patch throws back a 404 error.
>
> My guess is the SquidGuard application is quite badly maintained,
> judging from their homepage displaying a forest of patches and
> announcing a perpetual 1.5beta version for the last couple of years.
>
> If anybody has an idea, that would be helpful.
>
> Cheers,
>
> Niki

Some additional information. Here's the relevant bit from the SquidGuard 
mailing list. The URL to the included patch does not work.

On Thursday, 13. March 2014 21:57:39 Ming Hou wrote:
 > Hi,
 >
 > I have upgraded my squid proxy from 3.1.23 to 3.4.4 with squidGuard 1.4.
 >
 > For some reasons, the redirection from the result of squidGuard 
throws out
 > the 404 error. However, I switch back 3.1.23 and the issue goes away.
 >
 > Any suggestion?

please see this "bug" report:
http://bugs.squid-cache.org/show_bug.cgi?id=3978

-> You need to patch squidguard to work with newer squid versions.



-- 
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 hostmaster at slackonly.com  Sat May  2 06:48:45 2015
From: hostmaster at slackonly.com (Panagiotis Nikolaou)
Date: Sat, 02 May 2015 09:48:45 +0300
Subject: [Slackbuilds-users] SquidGuard 1.4 vs. Squid 3.4 : patch for
 vanilla sources needed
In-Reply-To: <55446FD3.5050301@microlinux.fr>
References: <55446EBC.5090107@microlinux.fr> <55446FD3.5050301@microlinux.fr>
Message-ID: <5544734D.1090109@slackonly.com>

Hi Niki

i have attached SquidGuard patch.

Cheers

On 05/02/2015 09:33 AM, Niki Kovacs wrote:
> Le 02/05/2015 08:29, Niki Kovacs a ?crit :
>> Hi,
>>
>> I'm using a combination of Squid and SquidGuard on my servers for web
>> filtering, which is the "industrial grade" solution usable in schools
>> and companies.
>>
>> Up until recently, the combination worked well with Squid 3.3 and
>> SquidGuard 1.4. Unfortunately, the upgrade to Squid 3.4 broke something,
>> and SquidGuard doesn't work anymore.
>>
>> I've googled a bit, and found out that SquidGuard 1.4 has to be patched
>> in order to work with Squid >= 3.4.
>>
>> Now I just spent some time hunting down that mysterious patch, but I
>> failed, because all the patches are either distribution-specific
>> (FreeBSD, Arch, etc.) and they don't work with vanilla sources, or the
>> link to the original patch throws back a 404 error.
>>
>> My guess is the SquidGuard application is quite badly maintained,
>> judging from their homepage displaying a forest of patches and
>> announcing a perpetual 1.5beta version for the last couple of years.
>>
>> If anybody has an idea, that would be helpful.
>>
>> Cheers,
>>
>> Niki
>
> Some additional information. Here's the relevant bit from the
> SquidGuard mailing list. The URL to the included patch does not work.
>
> On Thursday, 13. March 2014 21:57:39 Ming Hou wrote:
> > Hi,
> >
> > I have upgraded my squid proxy from 3.1.23 to 3.4.4 with squidGuard
> 1.4.
> >
> > For some reasons, the redirection from the result of squidGuard
> throws out
> > the 404 error. However, I switch back 3.1.23 and the issue goes away.
> >
> > Any suggestion?
>
> please see this "bug" report:
> http://bugs.squid-cache.org/show_bug.cgi?id=3978
>
> -> You need to patch squidguard to work with newer squid versions.
>
>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: squidGuard-1.4_upgrade.patch
Type: text/x-patch
Size: 2619 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150502/0fd83d9b/attachment.bin>

From info at microlinux.fr  Sat May  2 07:03:51 2015
From: info at microlinux.fr (Niki Kovacs)
Date: Sat, 02 May 2015 09:03:51 +0200
Subject: [Slackbuilds-users] SquidGuard 1.4 vs. Squid 3.4 : patch for
 vanilla sources needed
In-Reply-To: <5544734D.1090109@slackonly.com>
References: <55446EBC.5090107@microlinux.fr> <55446FD3.5050301@microlinux.fr>
 <5544734D.1090109@slackonly.com>
Message-ID: <554476D7.2040102@microlinux.fr>

Le 02/05/2015 08:48, Panagiotis Nikolaou a ?crit :
> Hi Niki
>
> i have attached SquidGuard patch.

This doesn't work with the vanilla sources.

-- 
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  Sat May  2 07:12:28 2015
From: miguel at thedeanda.com (Miguel De Anda)
Date: Sat, 2 May 2015 00:12:28 -0700
Subject: [Slackbuilds-users] can't install flashplayer-plugin
In-Reply-To: <554330A1.4010205@slackbuilds.org>
References: <CAA62KfSNonkw_C3DbRRFM4zORM0tBkKHSu=YbEgYcjgSbipTJQ@mail.gmail.com>
 <554330A1.4010205@slackbuilds.org>
Message-ID: <CAA62KfQ2wKgmFKFeocz36pYnt+RjoM=vG-cwW19mbcGk1ezqhw@mail.gmail.com>

willy: you're correct. the sbo is fine. it turns out my sbopkg sync wasn't
working as described here: (
http://www.linuxquestions.org/questions/slackware-14/sbopkg-resync-fails-gpg-key-after-latest-security-upgrades-advice-4175540461/
). i ran it off my local git checkout and it worked fine.

klaatu: awesome! never really paid much attention to the diffs because
chrome and chromium. aliens package worked great but it didn't work with
firefox (although i did see there was a separate extension to make it work,
but i didn't care to look into too much as i don't use firefox that often).

-m

On Fri, May 1, 2015 at 12:52 AM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> > mv: cannot stat '/tmp/SBo/package-flashplayer-plugin/LGPL/*': No
> > such file or directory
> >
> >
> > i guess they removed the directory/file with the latest release?
>
> I Don't think so
>
> tar tvf install_flash_player_11_linux.i386.tar.gz
> - -rw-rw-r-- flplbldr/flplbldr 17437860 2015-04-12 08:26 libflashplayer.so
> - -r--r--r-- flplbldr/flplbldr     4009 2015-04-12 08:26 readme.txt
> drwxrwxr-x flplbldr/flplbldr        0 2015-04-12 08:26 LGPL/
> - -r--r--r-- flplbldr/flplbldr     7402 2015-04-12 08:26 LGPL/LGPL.txt
> - -r--r--r-- flplbldr/flplbldr       76 2015-04-12 08:26 LGPL/notice.txt
>
>
> - --
> Willy Sudiarto Raharjo
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iEYEAREIAAYFAlVDMKEACgkQiHuDdNczM4FIUACfWrriqwigAY5paZQKXwDOGu3B
> kwYAnAhw4pA9iqSS5XSFLh3L2kuJsnCM
> =4zRT
> -----END PGP SIGNATURE-----
> _______________________________________________
> 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/20150502/f87e59d0/attachment.html>

From miguel at thedeanda.com  Sat May  2 07:26:58 2015
From: miguel at thedeanda.com (Miguel De Anda)
Date: Sat, 2 May 2015 00:26:58 -0700
Subject: [Slackbuilds-users] can't install flashplayer-plugin
In-Reply-To: <CAA62KfQ2wKgmFKFeocz36pYnt+RjoM=vG-cwW19mbcGk1ezqhw@mail.gmail.com>
References: <CAA62KfSNonkw_C3DbRRFM4zORM0tBkKHSu=YbEgYcjgSbipTJQ@mail.gmail.com>
 <554330A1.4010205@slackbuilds.org>
 <CAA62KfQ2wKgmFKFeocz36pYnt+RjoM=vG-cwW19mbcGk1ezqhw@mail.gmail.com>
Message-ID: <CAA62KfSiR=+uxkXdEsCHXPp8vsT8dddK6Aq0fsH14RFuL+Eg4Q@mail.gmail.com>

actually my last email had wrong reasoning for the issue. i think this is
the issue:

TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
...
tar xf $CWD/install_flash_player_${VERS_MAJ}_linux.${ARCH}.tar.gz -C $PKG

when run from sbopkg there must be something slightly different in the
value of TMP. i compared to another SlackBuild script (dar) and it looks
like this:

TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
...
cd $TMP
tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
cd $PRGNAM-$VERSION

most slackbuild scripts i've seen tend to follow this pattern:

tar xvf foo.tar.gz
cd foo
mv bar $PKG/path/to/bar

they don't typically mv from $PKG/foo to $PKG/path/to/foo



On Sat, May 2, 2015 at 12:12 AM, Miguel De Anda <miguel at thedeanda.com>
wrote:
>
> willy: you're correct. the sbo is fine. it turns out my sbopkg sync
wasn't working as described here: (
http://www.linuxquestions.org/questions/slackware-14/sbopkg-resync-fails-gpg-key-after-latest-security-upgrades-advice-4175540461/
). i ran it off my local git checkout and it worked fine.
>
> klaatu: awesome! never really paid much attention to the diffs because
chrome and chromium. aliens package worked great but it didn't work with
firefox (although i did see there was a separate extension to make it work,
but i didn't care to look into too much as i don't use firefox that often).
>
> -m
>
> On Fri, May 1, 2015 at 12:52 AM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> > mv: cannot stat '/tmp/SBo/package-flashplayer-plugin/LGPL/*': No
>> > such file or directory
>> >
>> >
>> > i guess they removed the directory/file with the latest release?
>>
>> I Don't think so
>>
>> tar tvf install_flash_player_11_linux.i386.tar.gz
>> - -rw-rw-r-- flplbldr/flplbldr 17437860 2015-04-12 08:26
libflashplayer.so
>> - -r--r--r-- flplbldr/flplbldr     4009 2015-04-12 08:26 readme.txt
>> drwxrwxr-x flplbldr/flplbldr        0 2015-04-12 08:26 LGPL/
>> - -r--r--r-- flplbldr/flplbldr     7402 2015-04-12 08:26 LGPL/LGPL.txt
>> - -r--r--r-- flplbldr/flplbldr       76 2015-04-12 08:26 LGPL/notice.txt
>>
>>
>> - --
>> Willy Sudiarto Raharjo
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2
>>
>> iEYEAREIAAYFAlVDMKEACgkQiHuDdNczM4FIUACfWrriqwigAY5paZQKXwDOGu3B
>> kwYAnAhw4pA9iqSS5XSFLh3L2kuJsnCM
>> =4zRT
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> 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/20150502/e09050d4/attachment-0001.html>

From spaceman at antispaceman.com  Sat May  2 13:41:48 2015
From: spaceman at antispaceman.com (spaceman)
Date: Sat, 2 May 2015 14:41:48 +0100
Subject: [Slackbuilds-users] SquidGuard 1.4 vs. Squid 3.4 : patch for
 vanilla sources needed
In-Reply-To: <554476D7.2040102@microlinux.fr>
References: <55446EBC.5090107@microlinux.fr> <55446FD3.5050301@microlinux.fr>
 <5544734D.1090109@slackonly.com> <554476D7.2040102@microlinux.fr>
Message-ID: <20150502134148.GA20137@home.antispaceman.com>

Hi Niki,

I have the following patch in addition to the squidGuard patch already in the 
slackbuild. I don't remember where I got it from.

patch -p1 < $CWD/squidGuard.patch
patch -p1 < $CWD/rewrite.patch

squidGuard appears to work after it is applied. You can merge them if you 
would like.

Regards,
spaceman

Just putting it out there.

On 2015/05/02 09:05:51 , Niki Kovacs wrote:
>Le 02/05/2015 08:48, Panagiotis Nikolaou a ?crit :
>>Hi Niki
>>
>>i have attached SquidGuard patch.
>
>This doesn't work with the vanilla sources.
>
>-- 
>Microlinux - Solutions informatiques durables
>7, place de l'?glise - 30730 Montpezat
>Web  : http://www.microlinux.fr
>Mail : info at microlinux.fr
>T?l. : 04 66 63 10 32
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - http://slackbuilds.org/faq/
>
-------------- next part --------------
--- squidGuard-1.4.orig/src/main.c	2013-12-11 17:42:15.000000000 +1300
+++ squidGuard-1.4.orig/src/main.c	2013-12-11 19:04:09.000000000 +1300
@@ -175,7 +175,7 @@ 
 	sgReloadConfig();
       }
       if(failsafe_mode) {
-	puts("");
+	puts("ERR message=\"squidGuard failsafe mode\"");
 	fflush(stdout);
 	if(sig_hup){
           sgReloadConfig();
@@ -184,7 +184,7 @@ 
       }
       if(parseLine(buf,&squidInfo) != 1){
 	sgLogError("Error parsing squid line: %s",buf);
-	puts("");
+	puts("BH message=\"squidGuard error parsing squid line\"");
       }
         else {
 	src = Source;
@@ -196,14 +196,14 @@ 
 	  acl = sgAclCheckSource(src);
 	  if((redirect = sgAclAccess(src,acl,&squidInfo)) == NULL){
 	    if(src == NULL || src->cont_search == 0){
-	      puts(""); 
+	      puts("ERR");
 	      break;
 	    } else
 	      if(src->next != NULL){
 		src = src->next;
 		continue;
 	      } else {
-		puts("");
+		puts("ERR");
 		break;
 	      }
 	  } else {
@@ -215,9 +215,10 @@ 
 	      squidInfo.ident[0] = '-';
 	      squidInfo.ident[1] = '\0';
 	    }
-	    fprintf(stdout,"%s %s/%s %s %s\n",redirect,squidInfo.src,
-		    squidInfo.srcDomain,squidInfo.ident,
-		    squidInfo.method);
+	    if (isdigit(redirect[0]) && isdigit(redirect[1]) && isdigit(redirect[2]) && redirect[3]==':') {
+	      fprintf(stdout,"OK status=%c%c%c url=\"%s\"\n", redirect[0], redirect[1], redirect[2], &redirect[4]);
+	    } else
+	      fprintf(stdout,"OK rewrite-url=\"%s\"\n",redirect);
             /* sgLogError("%s %s/%s %s %s\n",redirect,squidInfo.src,squidInfo.srcDomain,squidInfo.ident,squidInfo.method);  */
 	    break;
 	  }
--- squidGuard-1.4.orig/src/sgDiv.c	2013-12-11 17:42:15.000000000 +1300
+++ squidGuard-1.4.orig/src/sgDiv.c	2013-12-11 18:58:33.000000000 +1300
@@ -771,7 +771,7 @@ 
   }
   sgLogError("Going into emergency mode");
   while(fgets(buf, MAX_BUF, stdin) != NULL){
-    puts("");
+    puts("ERR");
     fflush(stdout);
   }
   sgLogError("ending emergency mode, stdin empty");
--- squidGuard-1.4.orig/src/sgDiv.c.in	2013-12-11 17:42:15.000000000 +1300
+++ squidGuard-1.4.orig/src/sgDiv.c.in	2013-12-11 18:58:40.000000000 +1300
@@ -782,7 +782,7 @@ 
   }
   sgLogError("Going into emergency mode");
   while(fgets(buf, MAX_BUF, stdin) != NULL){
-    puts("");
+    puts("ERR");
     fflush(stdout);
   }
   sgLogError("ending emergency mode, stdin empty");
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150502/f84def46/attachment.asc>

From Hullen at t-online.de  Sat May  2 13:46:00 2015
From: Hullen at t-online.de (Helmut Hullen)
Date: Sat, 2 May 2015 15:46:00 +0200
Subject: [Slackbuilds-users] SquidGuard 1.4 vs. Squid 3.4 : patch for
 vanilla sources needed
In-Reply-To: <55446EBC.5090107@microlinux.fr>
Message-ID: <DG6OoCLeCXB@helmut.hullen.de>

Hallo, Niki,

Du meintest am 02.05.15:

> I've googled a bit, and found out that SquidGuard 1.4 has to be
> patched in order to work with Squid >= 3.4.

Please take a look at

<http://arktur.shuttle.de/CD/beta/slack/n1/squidGuard-1.5beta-i486-2hln.tgz>

It includes a very small "Build" skript under /usr/doc/squidGuard (not  
yet SlackBuild style), this packet works without problems in schools  
with about 500 machines (not always running all at the same time).

Viele Gruesse!
Helmut


From info at microlinux.fr  Sat May  2 14:44:25 2015
From: info at microlinux.fr (Niki Kovacs)
Date: Sat, 02 May 2015 16:44:25 +0200
Subject: [Slackbuilds-users] SquidGuard 1.4 vs. Squid 3.4 : patch for
 vanilla sources needed
In-Reply-To: <20150502134148.GA20137@home.antispaceman.com>
References: <55446EBC.5090107@microlinux.fr> <55446FD3.5050301@microlinux.fr>
 <5544734D.1090109@slackonly.com> <554476D7.2040102@microlinux.fr>
 <20150502134148.GA20137@home.antispaceman.com>
Message-ID: <5544E2C9.5050807@microlinux.fr>

Le 02/05/2015 15:41, spaceman a ?crit :
> Hi Niki,
>
> I have the following patch in addition to the squidGuard patch already
> in the slackbuild. I don't remember where I got it from.
>
> patch -p1 < $CWD/squidGuard.patch
> patch -p1 < $CWD/rewrite.patch
>
> squidGuard appears to work after it is applied. You can merge them if
> you would like.
>
> Regards,
> spaceman
>
> Just putting it out there.

Hi spaceman,

Thank you very much, that's exactly what I was looking for. I rebuilt 
SquidGuard using the patch, and now it works perfectly.

You have an honorable mention in the MLES ChangeLog files. :o)

@Willy or anybody else from the SBo team: the 'rewrite.patch' from the 
previous post has to be applied to SquidGuard in order for it to work 
with Squid 3.4 (provided by SlackBuilds.org). Do I have to resubmit 
everything? Or can you just add the line along with the patch?

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  Sat May  2 14:53:14 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 02 May 2015 21:53:14 +0700
Subject: [Slackbuilds-users] SquidGuard 1.4 vs. Squid 3.4 : patch for
 vanilla sources needed
In-Reply-To: <5544E2C9.5050807@microlinux.fr>
References: <55446EBC.5090107@microlinux.fr> <55446FD3.5050301@microlinux.fr>
 <5544734D.1090109@slackonly.com> <554476D7.2040102@microlinux.fr>
 <20150502134148.GA20137@home.antispaceman.com>
 <5544E2C9.5050807@microlinux.fr>
Message-ID: <5544E4DA.9020703@slackbuilds.org>

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

> @Willy or anybody else from the SBo team: the 'rewrite.patch' from
> the previous post has to be applied to SquidGuard in order for it
> to work with Squid 3.4 (provided by SlackBuilds.org). Do I have to
> resubmit everything? Or can you just add the line along with the
> patch?

done


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVE5NoACgkQiHuDdNczM4FCYACePlooxTA3JsHqyxRxKZiaiaBE
VecAn3pWWDv1vQAtsNs5Ysg7hRI094oe
=CZhC
-----END PGP SIGNATURE-----

From info at microlinux.fr  Sat May  2 15:41:47 2015
From: info at microlinux.fr (Niki Kovacs)
Date: Sat, 02 May 2015 17:41:47 +0200
Subject: [Slackbuilds-users] SquidGuard 1.4 vs. Squid 3.4 : patch for
 vanilla sources needed
In-Reply-To: <5544E4DA.9020703@slackbuilds.org>
References: <55446EBC.5090107@microlinux.fr> <55446FD3.5050301@microlinux.fr>
 <5544734D.1090109@slackonly.com> <554476D7.2040102@microlinux.fr>
 <20150502134148.GA20137@home.antispaceman.com>
 <5544E2C9.5050807@microlinux.fr> <5544E4DA.9020703@slackbuilds.org>
Message-ID: <5544F03B.7070500@microlinux.fr>

Le 02/05/2015 16:53, Willy Sudiarto Raharjo a ?crit :

>
> done
>

Thanks very much, Willy!


-- 
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  Sun May  3 00:59:19 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 03 May 2015 07:59:19 +0700
Subject: [Slackbuilds-users] Updates - 20150503.1
Message-ID: <554572E7.2050106@slackbuilds.org>

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

Sun May  3 00:45:41 UTC 2015
academic/fet: Updated for version 5.27.0.
desktop/gnome-menus: Added (libgnome-menu library).
desktop/kde-gtk-config: Fix source.
desktop/qmapshack: Updated for version 1.2.1.
desktop/xfce4-volumed-pulse: Added (audio volume management daemon).
development/FreeBASIC: Updated for version 1.02.1.
development/SQLAlchemy: Updated for version 1.0.2.
development/brackets: Updated for version 1.3.
development/mosml: Added (Moscow Standard ML).
development/mysql-workbench: Removed obsolete patches.
development/qt-creator3: Updated for version 3.4.0.
development/source-highlight: Updated for version 3.1.8.
games/noteye: Fix DOWNLOAD url.
gis/Shapely: Updated for version 1.5.8.
gis/osm2pgsql: Updated for version 0.87.3.
gis/pdal: Updated for version 0.9.9.
graphics/LDView: Fix compatibility against libpng.
graphics/SweetHome3D: Updated for version 4.6.
graphics/darktable: Updated for version 1.6.6.
graphics/leocad: Updated for version 0.82.1.
libraries/CGAL: Updated for version 4.6.
libraries/LucenePlusPlus: Fix compatibility with newer boost.
libraries/libasr: Added (ASyncronous Resolver library).
libraries/libtar: Fix source.
libraries/libvdpau: Updated for version 1.1.
libraries/mysql-connector-python: Updated for version 2.0.4.
libraries/pycparser: Updated for version 2.12.
libraries/rudiments: Added (C++ class library).
libraries/tbb: Updated for version 4.3u5.
misc/hoorex: Added (Dependency Calculator).
misc/jstock: Updated for version 1.0.7.6.
misc/sbo-templates: Updated for version 0.13.0.
misc/vdpauinfo: Updated for version 1.0.
multimedia/Mopidy: Updated for version 1.0.2.
multimedia/vlc: Updated for version 2.2.1.
multimedia/x265: Updated for version 1.6.
network/Electrum: Updated for version 2.1.1.
network/arno-iptables-firewall: Fix source naming.
network/bitcoin: Updated for version 0.10.1.
network/copy: Fix ARCH and only install for ARCH.
network/freerdp: Fix compatibility with newer cmake.
network/hiawatha: Updated for version 9.12.
network/icinga2: Updated for version 2.3.4.
network/liferea: Updated for version 1.10.15.
network/livestreamer: Updated for version 1.12.2.
network/mrtg: Updated for version 2.17.4.
network/qTox: Updated for version 20150427.
network/rtl8188eu: Updated for version 5e6362f3.
network/speedometer: Added (Progress monitor for console).
network/sphinx: Updated for version 2.2.9.
network/sqlrelay: Added (DB Connection Management).
network/squidGuard: Fix compatibility with Squid 3.4.
network/tor-browser: Updated for version 4.5.
network/toxcore: Updated for version 20150428.
network/youtube-dl: Updated for version 2015.04.26.
office/ccal: Added (Chinese Lunar Calendar).
office/kmymoney: Updated for version 4.7.2.
python/argcomplete: Updated for version 0.8.8.
python/ecdsa: Updated for version 0.13.
python/jedi: Updated for version 0.9.0.
python/lxml: Updated for version 3.4.4.
python/ply: Updated for version 3.6.
python/pysed: Updated for version 0.7.6.
python/python-certifi: Updated for version 2015.04.28.
python/python-libsass: Updated for version 0.8.0.
python/sge-pygame: Updated for version 0.18.1.
system/cantarell-fonts: Added (font).
system/clamav: Updated for version 0.98.7.
system/mongodb: Updated for version 3.0.2.
system/nvidia-driver: Updated for version 346.59.
system/nvidia-kernel: Updated for version 346.59.
system/nvidia-legacy304-driver: Update MAINTAINER.
system/qemu: Updated for version 2.3.0.
system/rxvt-unicode: Updated for version 9.21 + new maintainer.
system/simpleburn: Updated for version 1.7.3.
system/the_silver_searcher: Updated for version 0.30.0.
system/trmaid: Updated for version 0.4.4.
+--------------------------+



- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVFcucACgkQiHuDdNczM4FabACePeGpNbU9GgfDIneCJ0kWpauV
OTcAoIjTVvcqHQHH92Srtf8063w4pT0A
=7iVV
-----END PGP SIGNATURE-----

From hostmaster at slackonly.com  Sun May  3 07:40:40 2015
From: hostmaster at slackonly.com (Panagiotis Nikolaou)
Date: Sun, 03 May 2015 10:40:40 +0300
Subject: [Slackbuilds-users] jdk
Message-ID: <5545D0F8.9020408@slackonly.com>

Hi!

The SlackBuild of jdk is in version 8u40, oracle in download
page have updated jdk source to 8u45.

Here is the old source:
http://app.nidc.kr/java/jdk-8u40-linux-i586.tar.gz
http://app.nidc.kr/java/jdk-8u40-linux-x64.tar.gz
(md5sum match)

fi



From willysr at slackbuilds.org  Sun May  3 08:20:29 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 03 May 2015 15:20:29 +0700
Subject: [Slackbuilds-users] jdk
In-Reply-To: <5545D0F8.9020408@slackonly.com>
References: <5545D0F8.9020408@slackonly.com>
Message-ID: <5545DA4D.9030107@slackbuilds.org>

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

> The SlackBuild of jdk is in version 8u40, oracle in download page
> have updated jdk source to 8u45.
> 
> Here is the old source: 
> http://app.nidc.kr/java/jdk-8u40-linux-i586.tar.gz 
> http://app.nidc.kr/java/jdk-8u40-linux-x64.tar.gz (md5sum match)

Done in my branch


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVF2k0ACgkQiHuDdNczM4E4dQCfeV06G52x7IZbAgilx2PRh8G+
a5MAoLBnGaIPrL6uVWhRbHg9ePM3m5OB
=r+6Q
-----END PGP SIGNATURE-----

From baildon.research at googlemail.com  Sun May  3 12:43:36 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 3 May 2015 13:43:36 +0100
Subject: [Slackbuilds-users] New Slackbuild for ffmpeg
In-Reply-To: <20150430164153.718394bc@stygian.lan>
References: <87a8xqoqog.fsf@aura.christopherculver.com>
 <55410923.60601@slackbuilds.org> <5541581E.1050503@iinet.net.au>
 <20150429202807.4c3c4038@stygian.lan>
 <CAAcyf-pjtb_LMzAOLFt0KzUJ3-8NhX5Bp7p6psVieKnaTzSqDA@mail.gmail.com>
 <20150430164153.718394bc@stygian.lan>
Message-ID: <CAMt7G9RDbcAOE6BWVkh9m9HX3mLYx6KrKZ-GyUZsX62_LONhRg@mail.gmail.com>

>>  David Spencer's slackrepo should make the testing pretty easy (at least
>> the build part).
>>
>> https://github.com/idlemoor/slackrepo
>>
>
> -- snip
>
> Very nice. Thanks, Ryan. I should have time this weekend to play around
> with this and also get acquainted with hoorex.

fyi, there's a much improved new version of slackrepo on its way
"within the coming few days or no less
than a week". (to quote Darl McBride)

Best regards & thanks
-D.

From beni at grindcore.ch  Sun May  3 12:20:42 2015
From: beni at grindcore.ch (Beni Keller)
Date: Sun, 3 May 2015 14:20:42 +0200
Subject: [Slackbuilds-users] Build error in Atom 0.173.0
Message-ID: <20150503142042.2d6dd15c@slackhome.lan>


Hey all

I just noticed that I'm unable to build the Atom package currently on
SBo. There is a problem with Node 12 which is reported and fixed
uptream:

https://github.com/atom/atom/issues/5591

I was able to manually build the latest (0.196.0) release of Atom where
the error doesn't come up anymore. So I figure this is just a matter of
updating the slackbuild.

Regards,

Beni

From ryan.q at linux.com  Sun May  3 15:58:06 2015
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Sun, 03 May 2015 15:58:06 +0000
Subject: [Slackbuilds-users] Build error in Atom 0.173.0
In-Reply-To: <20150503142042.2d6dd15c@slackhome.lan>
References: <20150503142042.2d6dd15c@slackhome.lan>
Message-ID: <CAAcyf-pBDBx5EH-b8oNxL=J3ETg5dznU_J4Sp7YC_Mg0oOQhSw@mail.gmail.com>

 On Sun, May 3, 2015, 8:16 AM Beni Keller <beni at grindcore.ch> wrote:


Hey all

I just noticed that I'm unable to build the Atom package currently on
SBo. There is a problem with Node 12 which is reported and fixed
uptream:

https://github.com/atom/atom/issues/5591

I was able to manually build the latest (0.196.0) release of Atom where
the error doesn't come up anymore. So I figure this is just a matter of
updating the slackbuild.

 I thought atom used iojs now ...


Regards,

Beni
_______________________________________________
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/20150503/bb2f4916/attachment.html>

From kingbeowulf at gmail.com  Sun May  3 20:08:48 2015
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 03 May 2015 13:08:48 -0700
Subject: [Slackbuilds-users] jdk
In-Reply-To: <5545D0F8.9020408@slackonly.com>
References: <5545D0F8.9020408@slackonly.com>
Message-ID: <55468050.4070902@gmail.com>

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

On 05/03/2015 12:40 AM, Panagiotis Nikolaou wrote:
> Hi!
> 
> The SlackBuild of jdk is in version 8u40, oracle in download page
> have updated jdk source to 8u45.
> 

As an FYI, I've run the SBo script with 8u45 and so far all appears
functional (including browser plugin, tested on jin and Sweethome3D).
 I sent the maintainer a heads up a few days ago.

- -Ed

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

iEYEARECAAYFAlVGgE4ACgkQXvwMaW61dLcm9ACfb4xAVNxGFShFhOZAgddu7mRN
sl8An38yZelVJMFMMuLNH/pk8fgjWixW
=KwCt
-----END PGP SIGNATURE-----

From jvogel4 at stny.rr.com  Mon May  4 01:33:37 2015
From: jvogel4 at stny.rr.com (John Vogel)
Date: Sun, 3 May 2015 21:33:37 -0400
Subject: [Slackbuilds-users] New Slackbuild for ffmpeg
In-Reply-To: <CAMt7G9RDbcAOE6BWVkh9m9HX3mLYx6KrKZ-GyUZsX62_LONhRg@mail.gmail.com>
References: <87a8xqoqog.fsf@aura.christopherculver.com>
 <55410923.60601@slackbuilds.org> <5541581E.1050503@iinet.net.au>
 <20150429202807.4c3c4038@stygian.lan>
 <CAAcyf-pjtb_LMzAOLFt0KzUJ3-8NhX5Bp7p6psVieKnaTzSqDA@mail.gmail.com>
 <20150430164153.718394bc@stygian.lan>
 <CAMt7G9RDbcAOE6BWVkh9m9HX3mLYx6KrKZ-GyUZsX62_LONhRg@mail.gmail.com>
Message-ID: <20150503213337.74f07f4f@stygian.lan>

On Sun, 3 May 2015 13:43:36 +0100
David Spencer <baildon.research at googlemail.com> wrote:

> >>  David Spencer's slackrepo should make the testing pretty easy (at least
> >> the build part).
> >>
> >> https://github.com/idlemoor/slackrepo
> >>
> >
> > -- snip
> >
> > Very nice. Thanks, Ryan. I should have time this weekend to play around
> > with this and also get acquainted with hoorex.
> 
> fyi, there's a much improved new version of slackrepo on its way
> "within the coming few days or no less
> than a week". (to quote Darl McBride)
> 
> Best regards & thanks
> -D.

Hi David,

I've got slackrepo working nicely for this so far. I'm not having any
luck getting the chroot option to work; I'm running kernel and modules for
3.18.11 built to stock configs, but still not working. I'll try again after
the new release, then if I run into troubles, I'll start trying to debug it
then. It could be something I'm doing wrong here, but I'm sure it will come
out in the wash eventually. I'm very happy to be able to automate this so
easily. Thanks for all your efforts.

Cheers,
John

From slackware at lemintown.eu  Mon May  4 21:58:45 2015
From: slackware at lemintown.eu (Lemin)
Date: Mon, 04 May 2015 23:58:45 +0200
Subject: [Slackbuilds-users] =?utf-8?q?VLC=C2=A02=2E2=2E1_configure_warnin?=
	=?utf-8?q?gs?=
Message-ID: <5547EB95.5030608@lemintown.eu>

Hi,

The latest VLC update would like libraries that are not provided by 14.1:
    - requires TagLib 1.9.0 but slackware-14.1 has 1.8.0.
    - requires cairo >= 1.13.1 but slackware-14.1 has 1.12.16.
    - requires libdvdread >= 4.9.0 but slackware-14.1 has 4.2.0.

You could also add these packages as options: libssh2, gstreamer1, x265.

Cheers
Lemin

From willysr at slackbuilds.org  Tue May  5 00:10:09 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 05 May 2015 07:10:09 +0700
Subject: [Slackbuilds-users]
 =?windows-1252?q?VLC=A02=2E2=2E1_configure_wa?=
 =?windows-1252?q?rnings?=
In-Reply-To: <5547EB95.5030608@lemintown.eu>
References: <5547EB95.5030608@lemintown.eu>
Message-ID: <55480A61.1060809@slackbuilds.org>

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

> The latest VLC update would like libraries that are not provided by
> 14.1: - requires TagLib 1.9.0 but slackware-14.1 has 1.8.0. -
> requires cairo >= 1.13.1 but slackware-14.1 has 1.12.16. - requires
> libdvdread >= 4.9.0 but slackware-14.1 has 4.2.0.
> 
> You could also add these packages as options: libssh2, gstreamer1,
> x265.

i built the VLC on slackware64-14.1 and it worked fine


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVICmEACgkQiHuDdNczM4Fi+gCfdSPiWRnosYZk9b0zAUplqpUJ
7x4AoIROXpSGpnoRyMhVxNlBzjXj5p5t
=+Hyy
-----END PGP SIGNATURE-----

From chris.willing at iinet.net.au  Tue May  5 03:29:03 2015
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 05 May 2015 13:29:03 +1000
Subject: [Slackbuilds-users]
 =?utf-8?q?VLC=C2=A02=2E2=2E1_configure_warnin?= =?utf-8?q?gs?=
In-Reply-To: <55480A61.1060809@slackbuilds.org>
References: <5547EB95.5030608@lemintown.eu> <55480A61.1060809@slackbuilds.org>
Message-ID: <554838FF.6060700@iinet.net.au>



On 05/05/2015 10:10 AM, Willy Sudiarto Raharjo wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>> The latest VLC update would like libraries that are not provided by
>> 14.1: - requires TagLib 1.9.0 but slackware-14.1 has 1.8.0. -
>> requires cairo >= 1.13.1 but slackware-14.1 has 1.12.16. - requires
>> libdvdread >= 4.9.0 but slackware-14.1 has 4.2.0.
>>
>> You could also add these packages as options: libssh2, gstreamer1,
>> x265.
>
> i built the VLC on slackware64-14.1 and it worked fine
>

Yes, I was pretty sure I'd built and tested vlc-2.2.1 on 14.1 just 
recently but couldn't check right now as my dev machine is deeply into 
rebuilding lots of packages in -current, so thanks for confirming Willy.

However I was able to build 2.2.1 on -current with the additional 
options that Lemin has suggested (although what used to be gstreamer1 is 
now just plain gstreamer in stock -current) and it all went fine. I'll 
check it again on 14.1 soon and, all being well, I'll submit an updated 
SlackBuild sometime this week.

chris

From slackware at lemintown.eu  Tue May  5 07:53:21 2015
From: slackware at lemintown.eu (Lemin)
Date: Tue, 05 May 2015 09:53:21 +0200
Subject: [Slackbuilds-users]
 =?windows-1252?q?VLC=A02=2E2=2E1_configure_wa?=
 =?windows-1252?q?rnings?=
In-Reply-To: <554838FF.6060700@iinet.net.au>
References: <5547EB95.5030608@lemintown.eu> <55480A61.1060809@slackbuilds.org>
 <554838FF.6060700@iinet.net.au>
Message-ID: <554876F1.9000507@lemintown.eu>

On 2015-05-05 05:29, Christoph Willing wrote:
>
>
> On 05/05/2015 10:10 AM, Willy Sudiarto Raharjo wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>>> The latest VLC update would like libraries that are not provided by
>>> 14.1: - requires TagLib 1.9.0 but slackware-14.1 has 1.8.0. -
>>> requires cairo >= 1.13.1 but slackware-14.1 has 1.12.16. - requires
>>> libdvdread >= 4.9.0 but slackware-14.1 has 4.2.0.
>>>
>>> You could also add these packages as options: libssh2, gstreamer1,
>>> x265.
>>
>> i built the VLC on slackware64-14.1 and it worked fine
>>
>
> Yes, I was pretty sure I'd built and tested vlc-2.2.1 on 14.1 just 
> recently but couldn't check right now as my dev machine is deeply into 
> rebuilding lots of packages in -current, so thanks for confirming Willy.
>
> However I was able to build 2.2.1 on -current with the additional 
> options that Lemin has suggested (although what used to be gstreamer1 
> is now just plain gstreamer in stock -current) and it all went fine. 
> I'll check it again on 14.1 soon and, all being well, I'll submit an 
> updated SlackBuild sometime this week.
>
> 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/
>
It works fine for playing most files, but I encountered an issue when 
trying to play a DVD, perhaps for libdvdread support was not built:

Your input can't be opened:VLC is unable to open the MRL 'dvd:///...'

The prior vlc could read it with libdvdread built. For now I encode 
using HandBrake then play with vlc.

Without TagLib, vlc is not reading the tag informations of mp3 files I 
also witnessed.
I could not say how vlc uses cairo, and if the lack of it brings any issue.

I have been using 2.2.1 with the addiotional options (gstreamer1 from 
SBo), and did not notice any issue.

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

From jvogel4 at stny.rr.com  Tue May  5 23:00:54 2015
From: jvogel4 at stny.rr.com (John Vogel)
Date: Tue, 5 May 2015 19:00:54 -0400
Subject: [Slackbuilds-users] libraries/ogre: upstream updated download file
Message-ID: <20150505190054.66846115@stygian.lan>

The source file for ogre has been updated after a recent branch merge.
The new md5sum is 'c41950f13cf4a8b6e83894920c1ea898'.
The new top level directory for the tarball is 'sinbad-ogre-55e89ae88219', so
the SRCNAM variable in the SlackBuild also needs to be updated.

From willysr at slackbuilds.org  Wed May  6 00:14:58 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 06 May 2015 07:14:58 +0700
Subject: [Slackbuilds-users] libraries/ogre: upstream updated download
 file
In-Reply-To: <20150505190054.66846115@stygian.lan>
References: <20150505190054.66846115@stygian.lan>
Message-ID: <55495D02.30009@slackbuilds.org>

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

> The source file for ogre has been updated after a recent branch
> merge. The new md5sum is 'c41950f13cf4a8b6e83894920c1ea898'. The
> new top level directory for the tarball is
> 'sinbad-ogre-55e89ae88219', so the SRCNAM variable in the
> SlackBuild also needs to be updated.

Fixed in my branch

Thanks


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVJXQIACgkQiHuDdNczM4HXQACgjp4whMpiyjTt8Hmb/3nPQZda
JpMAn3WY3vDAc6RUTie8MW7NusnClERo
=xiMC
-----END PGP SIGNATURE-----

From miguel at thedeanda.com  Wed May  6 05:01:45 2015
From: miguel at thedeanda.com (Miguel De Anda)
Date: Tue, 5 May 2015 22:01:45 -0700
Subject: [Slackbuilds-users] nginx permissions?
Message-ID: <CAA62KfSUsQXoZMYUYDyp4ReSxMiwjdBKeaOCJvPvkyC1gbS7fA@mail.gmail.com>

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150505/66e43bd0/attachment.html>

From chris.willing at iinet.net.au  Wed May  6 06:19:50 2015
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Wed, 06 May 2015 16:19:50 +1000
Subject: [Slackbuilds-users]
 =?utf-8?q?VLC=C2=A02=2E2=2E1_configure_warnin?= =?utf-8?q?gs?=
In-Reply-To: <554876F1.9000507@lemintown.eu>
References: <5547EB95.5030608@lemintown.eu> <55480A61.1060809@slackbuilds.org>
 <554838FF.6060700@iinet.net.au> <554876F1.9000507@lemintown.eu>
Message-ID: <5549B286.7080803@iinet.net.au>



On 05/05/2015 05:53 PM, Lemin wrote:
> On 2015-05-05 05:29, Christoph Willing wrote:
>>
>>
>> On 05/05/2015 10:10 AM, Willy Sudiarto Raharjo wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA256
>>>
>>>> The latest VLC update would like libraries that are not provided by
>>>> 14.1: - requires TagLib 1.9.0 but slackware-14.1 has 1.8.0. -
>>>> requires cairo >= 1.13.1 but slackware-14.1 has 1.12.16. - requires
>>>> libdvdread >= 4.9.0 but slackware-14.1 has 4.2.0.
>>>>
>>>> You could also add these packages as options: libssh2, gstreamer1,
>>>> x265.
>>>
>>> i built the VLC on slackware64-14.1 and it worked fine
>>>
>>
>> Yes, I was pretty sure I'd built and tested vlc-2.2.1 on 14.1 just
>> recently but couldn't check right now as my dev machine is deeply into
>> rebuilding lots of packages in -current, so thanks for confirming Willy.
>>
>> However I was able to build 2.2.1 on -current with the additional
>> options that Lemin has suggested (although what used to be gstreamer1
>> is now just plain gstreamer in stock -current) and it all went fine.
>> I'll check it again on 14.1 soon and, all being well, I'll submit an
>> updated SlackBuild sometime this week.
>>
>> 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/
>>
> It works fine for playing most files, but I encountered an issue when
> trying to play a DVD, perhaps for libdvdread support was not built:
>
> Your input can't be opened:VLC is unable to open the MRL 'dvd:///...'
>
> The prior vlc could read it with libdvdread built. For now I encode
> using HandBrake then play with vlc.
>
> Without TagLib, vlc is not reading the tag informations of mp3 files I
> also witnessed.
> I could not say how vlc uses cairo, and if the lack of it brings any issue.
>
> I have been using 2.2.1 with the addiotional options (gstreamer1 from
> SBo), and did not notice any issue.
>

I've confirmed these problems with vlc-2.2.1 on 14.1 and since its most 
improbable that lidvdread and taglib versions will be updated in 
official 14.1, I think we should revert to the latest version of vlc 
that is able to use those versions. That is vlc-2.1.6 which I've tested 
to confirm operation with dvd:///... and cdda:///... MRL's.

I'm just about to submit the SlackBuild for it, with libssh2, 
gstreamer1, gst1-plugins-base and x265 packages added to REQUIRES.

Thanks for reporting the problem and suggesting the extra options Lemin.

chris



From slackware at lemintown.eu  Wed May  6 07:58:47 2015
From: slackware at lemintown.eu (Lemin)
Date: Wed, 06 May 2015 09:58:47 +0200
Subject: [Slackbuilds-users]
 =?windows-1252?q?VLC=A02=2E2=2E1_configure_wa?=
 =?windows-1252?q?rnings?=
In-Reply-To: <5549B286.7080803@iinet.net.au>
References: <5547EB95.5030608@lemintown.eu> <55480A61.1060809@slackbuilds.org>
 <554838FF.6060700@iinet.net.au> <554876F1.9000507@lemintown.eu>
 <5549B286.7080803@iinet.net.au>
Message-ID: <5549C9B7.8050803@lemintown.eu>

On 2015-05-06 08:19, Christoph Willing wrote:
>
>
> On 05/05/2015 05:53 PM, Lemin wrote:
>> On 2015-05-05 05:29, Christoph Willing wrote:
>>>
>>>
>>> On 05/05/2015 10:10 AM, Willy Sudiarto Raharjo wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA256
>>>>
>>>>> The latest VLC update would like libraries that are not provided by
>>>>> 14.1: - requires TagLib 1.9.0 but slackware-14.1 has 1.8.0. -
>>>>> requires cairo >= 1.13.1 but slackware-14.1 has 1.12.16. - requires
>>>>> libdvdread >= 4.9.0 but slackware-14.1 has 4.2.0.
>>>>>
>>>>> You could also add these packages as options: libssh2, gstreamer1,
>>>>> x265.
>>>>
>>>> i built the VLC on slackware64-14.1 and it worked fine
>>>>
>>>
>>> Yes, I was pretty sure I'd built and tested vlc-2.2.1 on 14.1 just
>>> recently but couldn't check right now as my dev machine is deeply into
>>> rebuilding lots of packages in -current, so thanks for confirming Willy.
>>>
>>> However I was able to build 2.2.1 on -current with the additional
>>> options that Lemin has suggested (although what used to be gstreamer1
>>> is now just plain gstreamer in stock -current) and it all went fine.
>>> I'll check it again on 14.1 soon and, all being well, I'll submit an
>>> updated SlackBuild sometime this week.
>>>
>>> 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/
>>>
>> It works fine for playing most files, but I encountered an issue when
>> trying to play a DVD, perhaps for libdvdread support was not built:
>>
>> Your input can't be opened:VLC is unable to open the MRL 'dvd:///...'
>>
>> The prior vlc could read it with libdvdread built. For now I encode
>> using HandBrake then play with vlc.
>>
>> Without TagLib, vlc is not reading the tag informations of mp3 files I
>> also witnessed.
>> I could not say how vlc uses cairo, and if the lack of it brings any
>> issue.
>>
>> I have been using 2.2.1 with the addiotional options (gstreamer1 from
>> SBo), and did not notice any issue.
>>
>
> I've confirmed these problems with vlc-2.2.1 on 14.1 and since its most
> improbable that lidvdread and taglib versions will be updated in
> official 14.1, I think we should revert to the latest version of vlc
> that is able to use those versions. That is vlc-2.1.6 which I've tested
> to confirm operation with dvd:///... and cdda:///... MRL's.
>
> I'm just about to submit the SlackBuild for it, with libssh2,
> gstreamer1, gst1-plugins-base and x265 packages added to REQUIRES.
>
> Thanks for reporting the problem and suggesting the extra options Lemin.
>
> chris
>

It seems vlc-2.1.6 does not provide x265 and gstreamer1 support yet, 
quoting from the vlc-git NEWS file:

Changes between 2.1.6 and 2.2.0:
--------------------------------
[...]
Access:
* Added TLS support for ftp access and sout access
New schemes for implicit (ftps) and explicit (ftpes) modes
[...]
Encoder:
[...]
* Support for HEVC/H.265 encoding using x265

Confirmed with local compile of 2.1.6, however libssh2 is indeed in 
vlc-2.1.6, my apologies for reporting that late in the conversation... I 
agree with your decision of reverting to a version fully compatible with 
14.1.

Thanks for your work
Lemin

From chris.willing at iinet.net.au  Wed May  6 13:18:58 2015
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Wed, 06 May 2015 23:18:58 +1000
Subject: [Slackbuilds-users] call for testing - mongodb
In-Reply-To: <CAA62KfQnAdFz7gtG20M-QDwF4VAbWVB3pQS1UZgq5Hxq7OGEaQ@mail.gmail.com>
References: <CAA62KfQnAdFz7gtG20M-QDwF4VAbWVB3pQS1UZgq5Hxq7OGEaQ@mail.gmail.com>
Message-ID: <554A14C2.6040905@iinet.net.au>



On 04/14/2015 04:22 PM, Miguel De Anda wrote:
> hi all,
>
> i've modified the mongodb build script to actually build mongo from
> source instead of just repackaging the binaries. if i can get a couple
> of confirmed builds i'll submit the update.
>

Firstly, its great to see Miguel's effort to change a SlackBuild from 
simply repackaging someone else's work to building it ourselves. 
Repackaging always looks like we're not able to build it ourselves, or 
couldn't be bothered ("slack" in the worst meaning of the word).

After the last lot of updates which included the new "build from source" 
SlackBuild for mongodb, I ran the script but found that the contents of 
the new package's /usr/bin directory contained only some of the binaries 
that exist in the repackaged version i.e.
mongo
mongod
mongoperf
mongos
mongosniff

compared with:
mongostat
mongod
mongofiles
mongorestore
mongo
mongoperf
bsondump
mongooplog
mongos
mongodump
mongotop
mongoimport
mongoexport

After unsuccessfully trying various scons incantations in an attempt to 
produce the missing binaries, I eventually read the documentation. It 
seems, according to docs/building.md, that the "missing" pieces are now 
kept separately at https://github.com/mongodb/mongo-tools

The question then is whether a separate mongo-tools SlackBuild should be 
made for them or whether building them could be added into the existing 
SlackBuild (since this is how the mongo people are preparing their own 
release packages - the ones we used to repackage)?

chris

From miguel at thedeanda.com  Wed May  6 14:54:26 2015
From: miguel at thedeanda.com (Miguel De Anda)
Date: Wed, 6 May 2015 07:54:26 -0700
Subject: [Slackbuilds-users] call for testing - mongodb
In-Reply-To: <554A14C2.6040905@iinet.net.au>
References: <CAA62KfQnAdFz7gtG20M-QDwF4VAbWVB3pQS1UZgq5Hxq7OGEaQ@mail.gmail.com>
 <554A14C2.6040905@iinet.net.au>
Message-ID: <CAA62KfQuSYjPbrVGKxMbgADJ7x1Era8Mjd5J8AguD7GK2YLjAA@mail.gmail.com>

Ahh good point. I had full intentions of creating a separate SlackBuilds
for those tools and completely forgot. I was thinking of keeping them
separate as it'll make getting the sources easier - no need for repackaging
the vanilla sources.

Thoughts?
On May 6, 2015 6:19 AM, "Christoph Willing" <chris.willing at iinet.net.au>
wrote:

>
>
> On 04/14/2015 04:22 PM, Miguel De Anda wrote:
>
>> hi all,
>>
>> i've modified the mongodb build script to actually build mongo from
>> source instead of just repackaging the binaries. if i can get a couple
>> of confirmed builds i'll submit the update.
>>
>>
> Firstly, its great to see Miguel's effort to change a SlackBuild from
> simply repackaging someone else's work to building it ourselves.
> Repackaging always looks like we're not able to build it ourselves, or
> couldn't be bothered ("slack" in the worst meaning of the word).
>
> After the last lot of updates which included the new "build from source"
> SlackBuild for mongodb, I ran the script but found that the contents of the
> new package's /usr/bin directory contained only some of the binaries that
> exist in the repackaged version i.e.
> mongo
> mongod
> mongoperf
> mongos
> mongosniff
>
> compared with:
> mongostat
> mongod
> mongofiles
> mongorestore
> mongo
> mongoperf
> bsondump
> mongooplog
> mongos
> mongodump
> mongotop
> mongoimport
> mongoexport
>
> After unsuccessfully trying various scons incantations in an attempt to
> produce the missing binaries, I eventually read the documentation. It
> seems, according to docs/building.md, that the "missing" pieces are now
> kept separately at https://github.com/mongodb/mongo-tools
>
> The question then is whether a separate mongo-tools SlackBuild should be
> made for them or whether building them could be added into the existing
> SlackBuild (since this is how the mongo people are preparing their own
> release packages - the ones we used to repackage)?
>
> 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/20150506/f769777a/attachment-0001.html>

From yalhcru at gmail.com  Wed May  6 15:37:28 2015
From: yalhcru at gmail.com (B Watson)
Date: Wed, 6 May 2015 11:37:28 -0400
Subject: [Slackbuilds-users] call for testing - mongodb
In-Reply-To: <CAA62KfQuSYjPbrVGKxMbgADJ7x1Era8Mjd5J8AguD7GK2YLjAA@mail.gmail.com>
References: <CAA62KfQnAdFz7gtG20M-QDwF4VAbWVB3pQS1UZgq5Hxq7OGEaQ@mail.gmail.com>
 <554A14C2.6040905@iinet.net.au>
 <CAA62KfQuSYjPbrVGKxMbgADJ7x1Era8Mjd5J8AguD7GK2YLjAA@mail.gmail.com>
Message-ID: <CAN1hMuCfDH8rahWZumPP4F63gzkni_4tBFTS=xXx0S=OnujY_g@mail.gmail.com>

On 5/6/15, Miguel De Anda <miguel at thedeanda.com> wrote:
> Thoughts?

I know nothing about mongodb, but...

Will anyone ever want to have only the core mongodb installed, without
the tools? Are the tools useful without the core package? If the answer
to both questions is 'no', it's better to include the tools in the core
package instead of making them separate.

That's my 2 cents anyway...

From pilbender at gmail.com  Wed May  6 16:07:17 2015
From: pilbender at gmail.com (Richard Scott Smith)
Date: Wed, 6 May 2015 09:07:17 -0700
Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 109, Issue 6
In-Reply-To: <mailman.2583.1430924068.1126.slackbuilds-users@slackbuilds.org>
References: <mailman.2583.1430924068.1126.slackbuilds-users@slackbuilds.org>
Message-ID: <CAKfAq6qWQPY-5YsWSGkohawbpdCj=mnB1hboB+a2KjKcCWSDDw@mail.gmail.com>

My 2 cents.  I use Mongo quite a bit.  I can't see myself ever not
installing both.  So, for convenience I'd like to see them together.  But,
being more true to upstream sources, they should be separate.  I suppose I
lean towards having them together because of my own selfish perspective.

scott

On Wed, May 6, 2015 at 7:54 AM, <slackbuilds-users-request at slackbuilds.org>
wrote:

> Send SlackBuilds-users mailing list submissions to
>         slackbuilds-users at slackbuilds.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> or, via email, send a message with subject or body 'help' to
>         slackbuilds-users-request at slackbuilds.org
>
> You can reach the person managing the list at
>         slackbuilds-users-owner at slackbuilds.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SlackBuilds-users digest..."
>
>
> Today's Topics:
>
>    1. Re: libraries/ogre: upstream updated download file
>       (Willy Sudiarto Raharjo)
>    2. nginx permissions? (Miguel De Anda)
>    3. Re: VLC?2.2.1 configure warnings (Christoph Willing)
>    4. Re: VLC?2.2.1 configure warnings (Lemin)
>    5. Re: call for testing - mongodb (Christoph Willing)
>    6. Re: call for testing - mongodb (Miguel De Anda)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 06 May 2015 07:14:58 +0700
> From: Willy Sudiarto Raharjo <willysr at slackbuilds.org>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] libraries/ogre: upstream updated
>         download file
> Message-ID: <55495D02.30009 at slackbuilds.org>
> Content-Type: text/plain; charset=windows-1252
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> > The source file for ogre has been updated after a recent branch
> > merge. The new md5sum is 'c41950f13cf4a8b6e83894920c1ea898'. The
> > new top level directory for the tarball is
> > 'sinbad-ogre-55e89ae88219', so the SRCNAM variable in the
> > SlackBuild also needs to be updated.
>
> Fixed in my branch
>
> Thanks
>
>
> - --
> Willy Sudiarto Raharjo
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iEYEAREIAAYFAlVJXQIACgkQiHuDdNczM4HXQACgjp4whMpiyjTt8Hmb/3nPQZda
> JpMAn3WY3vDAc6RUTie8MW7NusnClERo
> =xiMC
> -----END PGP SIGNATURE-----
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 5 May 2015 22:01:45 -0700
> From: Miguel De Anda <miguel at thedeanda.com>
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>,
>         larryhaja at gmail.com
> Subject: [Slackbuilds-users] nginx permissions?
> Message-ID:
>         <
> CAA62KfSUsQXoZMYUYDyp4ReSxMiwjdBKeaOCJvPvkyC1gbS7fA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150505/66e43bd0/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Wed, 06 May 2015 16:19:50 +1000
> From: Christoph Willing <chris.willing at iinet.net.au>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] VLC?2.2.1 configure warnings
> Message-ID: <5549B286.7080803 at iinet.net.au>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
>
>
> On 05/05/2015 05:53 PM, Lemin wrote:
> > On 2015-05-05 05:29, Christoph Willing wrote:
> >>
> >>
> >> On 05/05/2015 10:10 AM, Willy Sudiarto Raharjo wrote:
> >>> -----BEGIN PGP SIGNED MESSAGE-----
> >>> Hash: SHA256
> >>>
> >>>> The latest VLC update would like libraries that are not provided by
> >>>> 14.1: - requires TagLib 1.9.0 but slackware-14.1 has 1.8.0. -
> >>>> requires cairo >= 1.13.1 but slackware-14.1 has 1.12.16. - requires
> >>>> libdvdread >= 4.9.0 but slackware-14.1 has 4.2.0.
> >>>>
> >>>> You could also add these packages as options: libssh2, gstreamer1,
> >>>> x265.
> >>>
> >>> i built the VLC on slackware64-14.1 and it worked fine
> >>>
> >>
> >> Yes, I was pretty sure I'd built and tested vlc-2.2.1 on 14.1 just
> >> recently but couldn't check right now as my dev machine is deeply into
> >> rebuilding lots of packages in -current, so thanks for confirming Willy.
> >>
> >> However I was able to build 2.2.1 on -current with the additional
> >> options that Lemin has suggested (although what used to be gstreamer1
> >> is now just plain gstreamer in stock -current) and it all went fine.
> >> I'll check it again on 14.1 soon and, all being well, I'll submit an
> >> updated SlackBuild sometime this week.
> >>
> >> 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/
> >>
> > It works fine for playing most files, but I encountered an issue when
> > trying to play a DVD, perhaps for libdvdread support was not built:
> >
> > Your input can't be opened:VLC is unable to open the MRL 'dvd:///...'
> >
> > The prior vlc could read it with libdvdread built. For now I encode
> > using HandBrake then play with vlc.
> >
> > Without TagLib, vlc is not reading the tag informations of mp3 files I
> > also witnessed.
> > I could not say how vlc uses cairo, and if the lack of it brings any
> issue.
> >
> > I have been using 2.2.1 with the addiotional options (gstreamer1 from
> > SBo), and did not notice any issue.
> >
>
> I've confirmed these problems with vlc-2.2.1 on 14.1 and since its most
> improbable that lidvdread and taglib versions will be updated in
> official 14.1, I think we should revert to the latest version of vlc
> that is able to use those versions. That is vlc-2.1.6 which I've tested
> to confirm operation with dvd:///... and cdda:///... MRL's.
>
> I'm just about to submit the SlackBuild for it, with libssh2,
> gstreamer1, gst1-plugins-base and x265 packages added to REQUIRES.
>
> Thanks for reporting the problem and suggesting the extra options Lemin.
>
> chris
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 06 May 2015 09:58:47 +0200
> From: Lemin <slackware at lemintown.eu>
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] VLC?2.2.1 configure warnings
> Message-ID: <5549C9B7.8050803 at lemintown.eu>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 2015-05-06 08:19, Christoph Willing wrote:
> >
> >
> > On 05/05/2015 05:53 PM, Lemin wrote:
> >> On 2015-05-05 05:29, Christoph Willing wrote:
> >>>
> >>>
> >>> On 05/05/2015 10:10 AM, Willy Sudiarto Raharjo wrote:
> >>>> -----BEGIN PGP SIGNED MESSAGE-----
> >>>> Hash: SHA256
> >>>>
> >>>>> The latest VLC update would like libraries that are not provided by
> >>>>> 14.1: - requires TagLib 1.9.0 but slackware-14.1 has 1.8.0. -
> >>>>> requires cairo >= 1.13.1 but slackware-14.1 has 1.12.16. - requires
> >>>>> libdvdread >= 4.9.0 but slackware-14.1 has 4.2.0.
> >>>>>
> >>>>> You could also add these packages as options: libssh2, gstreamer1,
> >>>>> x265.
> >>>>
> >>>> i built the VLC on slackware64-14.1 and it worked fine
> >>>>
> >>>
> >>> Yes, I was pretty sure I'd built and tested vlc-2.2.1 on 14.1 just
> >>> recently but couldn't check right now as my dev machine is deeply into
> >>> rebuilding lots of packages in -current, so thanks for confirming
> Willy.
> >>>
> >>> However I was able to build 2.2.1 on -current with the additional
> >>> options that Lemin has suggested (although what used to be gstreamer1
> >>> is now just plain gstreamer in stock -current) and it all went fine.
> >>> I'll check it again on 14.1 soon and, all being well, I'll submit an
> >>> updated SlackBuild sometime this week.
> >>>
> >>> 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/
> >>>
> >> It works fine for playing most files, but I encountered an issue when
> >> trying to play a DVD, perhaps for libdvdread support was not built:
> >>
> >> Your input can't be opened:VLC is unable to open the MRL 'dvd:///...'
> >>
> >> The prior vlc could read it with libdvdread built. For now I encode
> >> using HandBrake then play with vlc.
> >>
> >> Without TagLib, vlc is not reading the tag informations of mp3 files I
> >> also witnessed.
> >> I could not say how vlc uses cairo, and if the lack of it brings any
> >> issue.
> >>
> >> I have been using 2.2.1 with the addiotional options (gstreamer1 from
> >> SBo), and did not notice any issue.
> >>
> >
> > I've confirmed these problems with vlc-2.2.1 on 14.1 and since its most
> > improbable that lidvdread and taglib versions will be updated in
> > official 14.1, I think we should revert to the latest version of vlc
> > that is able to use those versions. That is vlc-2.1.6 which I've tested
> > to confirm operation with dvd:///... and cdda:///... MRL's.
> >
> > I'm just about to submit the SlackBuild for it, with libssh2,
> > gstreamer1, gst1-plugins-base and x265 packages added to REQUIRES.
> >
> > Thanks for reporting the problem and suggesting the extra options Lemin.
> >
> > chris
> >
>
> It seems vlc-2.1.6 does not provide x265 and gstreamer1 support yet,
> quoting from the vlc-git NEWS file:
>
> Changes between 2.1.6 and 2.2.0:
> --------------------------------
> [...]
> Access:
> * Added TLS support for ftp access and sout access
> New schemes for implicit (ftps) and explicit (ftpes) modes
> [...]
> Encoder:
> [...]
> * Support for HEVC/H.265 encoding using x265
>
> Confirmed with local compile of 2.1.6, however libssh2 is indeed in
> vlc-2.1.6, my apologies for reporting that late in the conversation... I
> agree with your decision of reverting to a version fully compatible with
> 14.1.
>
> Thanks for your work
> Lemin
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 06 May 2015 23:18:58 +1000
> From: Christoph Willing <chris.willing at iinet.net.au>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] call for testing - mongodb
> Message-ID: <554A14C2.6040905 at iinet.net.au>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
>
>
> On 04/14/2015 04:22 PM, Miguel De Anda wrote:
> > hi all,
> >
> > i've modified the mongodb build script to actually build mongo from
> > source instead of just repackaging the binaries. if i can get a couple
> > of confirmed builds i'll submit the update.
> >
>
> Firstly, its great to see Miguel's effort to change a SlackBuild from
> simply repackaging someone else's work to building it ourselves.
> Repackaging always looks like we're not able to build it ourselves, or
> couldn't be bothered ("slack" in the worst meaning of the word).
>
> After the last lot of updates which included the new "build from source"
> SlackBuild for mongodb, I ran the script but found that the contents of
> the new package's /usr/bin directory contained only some of the binaries
> that exist in the repackaged version i.e.
> mongo
> mongod
> mongoperf
> mongos
> mongosniff
>
> compared with:
> mongostat
> mongod
> mongofiles
> mongorestore
> mongo
> mongoperf
> bsondump
> mongooplog
> mongos
> mongodump
> mongotop
> mongoimport
> mongoexport
>
> After unsuccessfully trying various scons incantations in an attempt to
> produce the missing binaries, I eventually read the documentation. It
> seems, according to docs/building.md, that the "missing" pieces are now
> kept separately at https://github.com/mongodb/mongo-tools
>
> The question then is whether a separate mongo-tools SlackBuild should be
> made for them or whether building them could be added into the existing
> SlackBuild (since this is how the mongo people are preparing their own
> release packages - the ones we used to repackage)?
>
> chris
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 6 May 2015 07:54:26 -0700
> From: Miguel De Anda <miguel at thedeanda.com>
> To: "SlackBuilds. org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] call for testing - mongodb
> Message-ID:
>         <
> CAA62KfQuSYjPbrVGKxMbgADJ7x1Era8Mjd5J8AguD7GK2YLjAA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Ahh good point. I had full intentions of creating a separate SlackBuilds
> for those tools and completely forgot. I was thinking of keeping them
> separate as it'll make getting the sources easier - no need for repackaging
> the vanilla sources.
>
> Thoughts?
> On May 6, 2015 6:19 AM, "Christoph Willing" <chris.willing at iinet.net.au>
> wrote:
>
> >
> >
> > On 04/14/2015 04:22 PM, Miguel De Anda wrote:
> >
> >> hi all,
> >>
> >> i've modified the mongodb build script to actually build mongo from
> >> source instead of just repackaging the binaries. if i can get a couple
> >> of confirmed builds i'll submit the update.
> >>
> >>
> > Firstly, its great to see Miguel's effort to change a SlackBuild from
> > simply repackaging someone else's work to building it ourselves.
> > Repackaging always looks like we're not able to build it ourselves, or
> > couldn't be bothered ("slack" in the worst meaning of the word).
> >
> > After the last lot of updates which included the new "build from source"
> > SlackBuild for mongodb, I ran the script but found that the contents of
> the
> > new package's /usr/bin directory contained only some of the binaries that
> > exist in the repackaged version i.e.
> > mongo
> > mongod
> > mongoperf
> > mongos
> > mongosniff
> >
> > compared with:
> > mongostat
> > mongod
> > mongofiles
> > mongorestore
> > mongo
> > mongoperf
> > bsondump
> > mongooplog
> > mongos
> > mongodump
> > mongotop
> > mongoimport
> > mongoexport
> >
> > After unsuccessfully trying various scons incantations in an attempt to
> > produce the missing binaries, I eventually read the documentation. It
> > seems, according to docs/building.md, that the "missing" pieces are now
> > kept separately at https://github.com/mongodb/mongo-tools
> >
> > The question then is whether a separate mongo-tools SlackBuild should be
> > made for them or whether building them could be added into the existing
> > SlackBuild (since this is how the mongo people are preparing their own
> > release packages - the ones we used to repackage)?
> >
> > 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/20150506/f769777a/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
>
> ------------------------------
>
> End of SlackBuilds-users Digest, Vol 109, Issue 6
> *************************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150506/83b60f3a/attachment-0001.html>

From C.J.Theunissen at differ.nl  Wed May  6 17:26:43 2015
From: C.J.Theunissen at differ.nl (Kees Theunissen)
Date: Wed, 6 May 2015 19:26:43 +0200 (CEST)
Subject: [Slackbuilds-users] call for testing - mongodb
In-Reply-To: <CAA62KfQuSYjPbrVGKxMbgADJ7x1Era8Mjd5J8AguD7GK2YLjAA@mail.gmail.com>
References: <CAA62KfQnAdFz7gtG20M-QDwF4VAbWVB3pQS1UZgq5Hxq7OGEaQ@mail.gmail.com>
 <554A14C2.6040905@iinet.net.au>
 <CAA62KfQuSYjPbrVGKxMbgADJ7x1Era8Mjd5J8AguD7GK2YLjAA@mail.gmail.com>
Message-ID: <alpine.LNX.2.11.1505061905530.32714@pcict9.rijnh.nl>

On Wed, 6 May 2015, Miguel De Anda wrote:

>Ahh good point. I had full intentions of creating a separate SlackBuilds
>for those tools and completely forgot. I was thinking of keeping them
>separate as it'll make getting the sources easier - no need for repackaging
>the vanilla sources.
>
>Thoughts?

Repackaging the vanilla sources? You don't need to do that - even if you
combine several sources in the same package.
You can specify more than one download URL and corresponding md5 hashes
in the info file. See for example the system/xen package.



Regards,

Kees Theunissen.

-- 
Kees Theunissen,  System and network manager,   Tel: +31 (0)30 6096724
Dutch Institute For Fundamental Energy Research (DIFFER)
e-mail address:   C.J.Theunissen at differ.nl
postal address:   PO Box 1207, 3430 BE Nieuwegein, NL
visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL



From thomas at beingboiled.info  Thu May  7 18:53:32 2015
From: thomas at beingboiled.info (Thomas Morper)
Date: Thu, 7 May 2015 20:53:32 +0200 (CEST)
Subject: [Slackbuilds-users] nginx permissions?
In-Reply-To: <CAA62KfSUsQXoZMYUYDyp4ReSxMiwjdBKeaOCJvPvkyC1gbS7fA@mail.gmail.com>
References: <CAA62KfSUsQXoZMYUYDyp4ReSxMiwjdBKeaOCJvPvkyC1gbS7fA@mail.gmail.com>
Message-ID: <alpine.LNX.2.11.1505071958190.25514@ks3357608.kimsufi.com>

On Tue, 5 May 2015, Miguel De Anda wrote:

> i've installed nginx from the slackbuild and i have it run as a proxy for
> tomcat with a config something like this...

> when it tries to load some files, it fails with the following error:
> "/var/lib/nginx/proxy/3/00/0000000003" failed (13: Permission denied)

> it seems to kind of work if i add a
> user mdeanda users;
> to the config and change the permission to /var/lib/nginx/*

Nginx uses /var/lib/nginx for various temporary files, especially when 
proxying. The directory should belong to root:root. Upon start, nginx will 
then create the various subfolders and asign them to the $NGINXUSER unless 
they already exist.

I ran into problems once when I either reconfigured or rebuilt nginx to 
use a different user id but forgot about /var/lib/nginx/* still belonging 
to the old user. I don't know how you ended up with the wrong permissions, 
but if you stop nginx, remove the contents of /var/lib/nginx and restart 
you should be fine. If the permission problems remain you should check 
your config and your nginx package for possible errors (e.g. built in 
wrong environment, manually specified user doesn't exist, etc.).

Regarding the user id... the SlackBuild script follows best practices by 
using the defaults but still giving the user a choice. Having a dedicated 
"nginx" user is IMHO desirable with regards to permissions and security. 
It's not technically required, though.

-- 

From belka.ew at gmail.com  Fri May  8 01:39:17 2015
From: belka.ew at gmail.com (Eugen Wissner)
Date: Fri, 8 May 2015 03:39:17 +0200
Subject: [Slackbuilds-users] Old linphone dependencies
Message-ID: <CAN7gC88dSWyNNYMD2uToVsKkFH3CDF0LdK1AxMkcthVH17GJdQ@mail.gmail.com>

Hello,

some time ago I was linphone maintainer. The old version of linphone had
two dependencies, that are still on slackbuilds.org but aren't used anymore
by the newest linphone version maintained by Euan Thoms (thanks to him to
take over the responsibility for the linphone :)). These libraries are:

libeXosip2
libosip2

So far as I know nothing else depends on these two and I don't maintain
them anymore. So I think they could be removed from the repository (Unless
Euan wants to take over the maintenance for any reason).

Regards,
Eugene
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150508/0c3d6201/attachment.html>

From willysr at slackbuilds.org  Sun May 10 00:20:26 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 10 May 2015 07:20:26 +0700
Subject: [Slackbuilds-users] Updates - 20150510.1
Message-ID: <554EA44A.4030605@slackbuilds.org>

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

Sun May 10 00:07:13 UTC 2015
audio/alsa-tools: Updated for version 1.0.29.
audio/creox4: Fixed HOMEPAGE.
audio/fIcy: Updated for version 1.0.19.
audio/fmmidi: Fix .info file.
audio/midillo: Fix README
desktop/awoken-icon-theme: Added (gnome icon theme).
desktop/disper: Added (switch utility).
desktop/faba-icon-theme: Added (gnome icon theme).
desktop/faba-mono-icons: Added (gnome icon theme).
desktop/faience-icon-theme: Removed non deps.
desktop/moka-icon-theme: Added (gnome icon theme).
desktop/obshutdown: Added (Openbox shutdown manager).
desktop/slack-wallpapers: Updated for version 0.443.
desktop/xdgmenumaker: Fix .info and slack-desc.
desktop/xtrlock: Updated for version 2.7.
development/SQLAlchemy: Updated for version 1.0.4.
development/coccinelle: Updated for version 1.0.0.
development/crosstool-ng: Updated for version 1.20.0.
development/dbeaver: Updated for version 3.3.2.
development/jdk: Updated for version 8u45.
development/libbitcoin: Added (bitcoin library).
development/vstudio: Updated for version 5.8.5.
games/adl: Fix .info file.
games/chocolate-doom: Updated for version 2.1.0.
games/colem: Updated for version 3.3.
games/cuyo: Updated for version 2.1.0.
games/desmume: Updated for version 0.9.11.
games/doomseeker: Fix slack-desc.
games/dustrac: Updated for version 1.11.0.
games/eduke32: Fix slack-desc.
games/fortune-futurama: Fix .info file.
games/megaglest: Updated for version 3.11.1.
games/mrrescue: Fix slack-desc.
games/pentagram: Fix .info file.
games/stella: Updated for version 4.6.1.
games/vcmi: Updated for version 0.98 + new maintainer.
games/vera: Updated for version 1.22.
games/wolf4sdl: Fixed broken line endings in patches.
games/yahtzee: Updated for version 1.5.
graphics/PyMOL: Updated for version 1.7.6.0.
graphics/bdfedit: Fix .info file.
graphics/fbida: Updated for version 2.10, updated README.
graphics/mcomix: Updated for version 1.01.
graphics/psftools: Fix HOMEPAGE.
ham/cqrlog: Updated for version 1.9.0.
ham/svxlink: Updated for version 14.08.1.
libraries/batinfo: Updated for version 0.3.
libraries/botocore: Updated for version 0.107.0.
libraries/bullet: Updated for version 2.83.4.
libraries/futures: Updated for version 3.0.1.
libraries/libbluray: Updated for version 0.8.0.
libraries/libdesktop-agnostic: Updated for version 20150505.
libraries/libgdiplus: Updated for version 3.12.
libraries/libva-intel-driver: Added (Intel G45/HD graphics backend).
libraries/libvirt-python: Updated for version 1.2.15.
libraries/libvirt: Updated for version 1.2.15.
libraries/live555: Updated for version 2015.05.03.
libraries/ogre: Update upstream source.
libraries/pies2overrides: Updated for version 2.6.5.
libraries/pies: Updated for version 2.6.5.
libraries/pylast: Updated for version 1.2.1.
misc/mosquitto: Updated for version 1.4.2.
multimedia/Mopidy: Updated for version 1.0.4.
multimedia/lsdvd: Updated for version 0.17.
multimedia/picard-plugins: Updated for version 20150505.
multimedia/plex-home-theater: Updated for version 1.4.0.459.
multimedia/vlc: Downgraded to 2.1.6.
network/awscli: Updated for version 1.7.26.
network/bmon: Updated for version 3.6.
network/deis: Updated for version 1.6.0.
network/flexget: Updated for version 1.2.305.
network/insync: Updated for version 1.2.9.35139.
network/iojs: Updated for version 2.0.1.
network/kwakd: Added (web server).
network/openvswitch: Updated for version 2.3.1.
network/strongswan: Updated for version 5.3.0.
network/synergy: Updated for version 1.7.2.
network/tor: Updated for version 0.2.5.12.
network/transmission: Fix slack-desc.
network/vivaldi: Updated for version 1.0.167.2_1.
network/youtube-dl: Updated for version 2015.05.03.
office/libreoffice-helppack: Updated for version 4.4.3.
office/libreoffice-langpack: Updated for version 4.4.3.
office/libreoffice: Updated for version 4.4.3.
office/texstudio: Updated for version 2.9.4.
perl/perl-file-basedir: Updated for version 0.07.
python/PyXB: Added (Python W3C XML Schema Bindings).
python/ndg_httpsclient: Updated for version 0.4.0.
python/prompt_toolkit: Updated for version 0.35.
python/pytest: Updated for version 2.7.0.
python/python-requests: Updated for version 2.6.2.
python/requests-oauthlib: Updated for version 0.5.0.
system/aha: Fix .info file.
system/asbt: Updated for version 1.7.
system/barman: Updated for version 1.4.1.
system/bcache-tools: Add compatibility patch.
system/cpmtools: Updated for version 2.20.
system/docker: Updated for version 1.6.0.
system/lhasa: Updated for version 0.3.0.
system/linuxconsoletools: Updated for version 1.4.8.
system/man-db: Updated for version 2.7.1, libpipeline 1.4.0.
system/parallel: Updated for version 20150422.
system/profile-sync-daemon: Updated for version 5.73.
system/pyarchey: Updated for version 0.6.1.
system/read-edid: Updated for version 3.0.2.
system/reptyr: Updated for version 0.6.2.
system/sandy: Updated for version 0.4_20140727, fix HOMEPAGE.
system/slpkg: Updated for version 2.3.0.
system/t1utils: Updated for version 1.39.
system/thermal_daemon: Updated for version 1.4.
system/udiskie: Updated for version 1.2.0.
system/virt-manager: Updated for version 1.2.0.
+--------------------------+


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVOpEoACgkQiHuDdNczM4FAtgCeK1jh12KBYwS10NYOovpzWRVa
DdMAnAtjXKqwwF+llUVM7DVgEiz4BS4l
=KJb6
-----END PGP SIGNATURE-----

From leva at ecentrum.hu  Sun May 10 06:50:58 2015
From: leva at ecentrum.hu (=?iso-8859-1?Q?L=C9VAI_D=E1niel?=)
Date: Sun, 10 May 2015 08:50:58 +0200
Subject: [Slackbuilds-users] cowsay: fix download link
Message-ID: <20150510065057.GA1641@serenity.local>

Hi!

diff --git a/games/cowsay/cowsay.info b/games/cowsay/cowsay.info
index 2a8434a..fdfab5c 100644
--- a/games/cowsay/cowsay.info
+++ b/games/cowsay/cowsay.info
@@ -1,7 +1,7 @@
 PRGNAM="cowsay"
 VERSION="3.03"
 HOMEPAGE="http://www.nog.net/~tony/warez/cowsay.shtml"
-DOWNLOAD="http://pkgs.fedoraproject.org/repo/pkgs/cowsay/cowsay-3.03.tar.gz/b29169797359420dadb998079021a494/"
+DOWNLOAD="http://pkgs.fedoraproject.org/repo/pkgs/cowsay/cowsay-3.03.tar.gz/b29169797359420dadb998079021a494/cowsay-3.03.tar.gz"
 MD5SUM="b29169797359420dadb998079021a494"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""


Daniel

-- 
L?VAI D?niel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D  650C C69B BE4C 83B6 3A8F

From willysr at slackbuilds.org  Sun May 10 06:58:25 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 10 May 2015 13:58:25 +0700
Subject: [Slackbuilds-users] cowsay: fix download link
In-Reply-To: <20150510065057.GA1641@serenity.local>
References: <20150510065057.GA1641@serenity.local>
Message-ID: <554F0191.80201@slackbuilds.org>

> diff --git a/games/cowsay/cowsay.info b/games/cowsay/cowsay.info
> index 2a8434a..fdfab5c 100644
> --- a/games/cowsay/cowsay.info
> +++ b/games/cowsay/cowsay.info
> @@ -1,7 +1,7 @@
>  PRGNAM="cowsay"
>  VERSION="3.03"
>  HOMEPAGE="http://www.nog.net/~tony/warez/cowsay.shtml"
> -DOWNLOAD="http://pkgs.fedoraproject.org/repo/pkgs/cowsay/cowsay-3.03.tar.gz/b29169797359420dadb998079021a494/"
> +DOWNLOAD="http://pkgs.fedoraproject.org/repo/pkgs/cowsay/cowsay-3.03.tar.gz/b29169797359420dadb998079021a494/cowsay-3.03.tar.gz"
>  MD5SUM="b29169797359420dadb998079021a494"
>  DOWNLOAD_x86_64=""
>  MD5SUM_x86_64=""

Fixed in my branch

Thanks


-- 
Willy Sudiarto Raharjo

From leva at ecentrum.hu  Sun May 10 11:29:20 2015
From: leva at ecentrum.hu (=?iso-8859-1?Q?L=C9VAI_D=E1niel?=)
Date: Sun, 10 May 2015 13:29:20 +0200
Subject: [Slackbuilds-users] pax: fix download link
Message-ID: <20150510112920.GA16213@serenity.local>

Hi!


diff --git a/system/pax/pax.info b/system/pax/pax.info
index f762cf8..ac5cc73 100644
--- a/system/pax/pax.info
+++ b/system/pax/pax.info
@@ -1,7 +1,7 @@
 PRGNAM="pax"
 VERSION="3.4"
 HOMEPAGE="https://build.opensuse.org/package/files?package=pax&project=openSUSE%3AFactory"
-DOWNLOAD="https://api.opensuse.org/public/source/Archiving/pax/pax-3.4.tar.bz2"
+DOWNLOAD="http://pkgs.fedoraproject.org/repo/pkgs/pax/pax-3.4.tar.bz2/fbd9023b590b45ac3ade95870702a0d6/pax-3.4.tar.bz2"
 MD5SUM="fbd9023b590b45ac3ade95870702a0d6"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""


Daniel

-- 
L?VAI D?niel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D  650C C69B BE4C 83B6 3A8F

From willysr at slackbuilds.org  Sun May 10 13:34:46 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 10 May 2015 20:34:46 +0700
Subject: [Slackbuilds-users] pax: fix download link
In-Reply-To: <20150510112920.GA16213@serenity.local>
References: <20150510112920.GA16213@serenity.local>
Message-ID: <554F5E76.8060705@slackbuilds.org>

> diff --git a/system/pax/pax.info b/system/pax/pax.info
> index f762cf8..ac5cc73 100644
> --- a/system/pax/pax.info
> +++ b/system/pax/pax.info
> @@ -1,7 +1,7 @@
>  PRGNAM="pax"
>  VERSION="3.4"
>  HOMEPAGE="https://build.opensuse.org/package/files?package=pax&project=openSUSE%3AFactory"
> -DOWNLOAD="https://api.opensuse.org/public/source/Archiving/pax/pax-3.4.tar.bz2"
> +DOWNLOAD="http://pkgs.fedoraproject.org/repo/pkgs/pax/pax-3.4.tar.bz2/fbd9023b590b45ac3ade95870702a0d6/pax-3.4.tar.bz2"
>  MD5SUM="fbd9023b590b45ac3ade95870702a0d6"
>  DOWNLOAD_x86_64=""
>  MD5SUM_x86_64=""

Fixed in my branch

Thanks


-- 
Willy Sudiarto Raharjo

From icaro.perseo at gmail.com  Wed May 13 19:58:21 2015
From: icaro.perseo at gmail.com (Perseo)
Date: Wed, 13 May 2015 14:58:21 -0500
Subject: [Slackbuilds-users] tweepy SlackBuild error
Message-ID: <5553ACDD.4060004@gmail.com>

Good day!

In trying to build tweepy displays the following error:

tweepy-3.1.0/
tweepy-3.1.0/.coveragerc
tweepy-3.1.0/.gitignore
tweepy-3.1.0/.travis.yml
tweepy-3.1.0/ASCII_LOGO.txt
tweepy-3.1.0/CHANGELOG.md
tweepy-3.1.0/CONTRIBUTORS
tweepy-3.1.0/LICENSE
tweepy-3.1.0/MANIFEST.in
tweepy-3.1.0/README.md
tweepy-3.1.0/bindings_url_parser.py
tweepy-3.1.0/cassettes/
tweepy-3.1.0/cassettes/testaddremovelistmember.json
tweepy-3.1.0/cassettes/testaddremovelistmembers.json
tweepy-3.1.0/cassettes/testblocks.json
tweepy-3.1.0/cassettes/testblocksids.json
tweepy-3.1.0/cassettes/testcachedresult.json
tweepy-3.1.0/cassettes/testcreatedestroyblock.json
tweepy-3.1.0/cassettes/testcreatedestroyfavorite.json
tweepy-3.1.0/cassettes/testcreatedestroyfriendship.json
tweepy-3.1.0/cassettes/testcursorcursoritems.json
tweepy-3.1.0/cassettes/testcursorcursorpages.json
tweepy-3.1.0/cassettes/testcursornext.json
tweepy-3.1.0/cassettes/testdirectmessages.json
tweepy-3.1.0/cassettes/testfavorites.json
tweepy-3.1.0/cassettes/testfollowers.json
tweepy-3.1.0/cassettes/testfollowersids.json
tweepy-3.1.0/cassettes/testfriends.json
tweepy-3.1.0/cassettes/testfriendsids.json
tweepy-3.1.0/cassettes/testgeoapis.json
tweepy-3.1.0/cassettes/testgetlist.json
tweepy-3.1.0/cassettes/testgetoembed.json
tweepy-3.1.0/cassettes/testgetstatus.json
tweepy-3.1.0/cassettes/testgetuser.json
tweepy-3.1.0/cassettes/testhometimeline.json
tweepy-3.1.0/cassettes/testidcursoritems.json
tweepy-3.1.0/cassettes/testidcursorpages.json
tweepy-3.1.0/cassettes/testlistmembers.json
tweepy-3.1.0/cassettes/testlistsall.json
tweepy-3.1.0/cassettes/testlistsmemberships.json
tweepy-3.1.0/cassettes/testlistssubscriptions.json
tweepy-3.1.0/cassettes/testlistsubscribers.json
tweepy-3.1.0/cassettes/testlisttimeline.json
tweepy-3.1.0/cassettes/testlookupusers.json
tweepy-3.1.0/cassettes/testme.json
tweepy-3.1.0/cassettes/testmentionstimeline.json
tweepy-3.1.0/cassettes/testratelimitstatus.json
tweepy-3.1.0/cassettes/testretweeters.json
tweepy-3.1.0/cassettes/testretweets.json
tweepy-3.1.0/cassettes/testretweetsofme.json
tweepy-3.1.0/cassettes/testsavedsearches.json
tweepy-3.1.0/cassettes/testsearch.json
tweepy-3.1.0/cassettes/testsearchusers.json
tweepy-3.1.0/cassettes/testsendanddestroydirectmessage.json
tweepy-3.1.0/cassettes/testsentdirectmessages.json
tweepy-3.1.0/cassettes/testshowfriendship.json
tweepy-3.1.0/cassettes/testshowlistmember.json
tweepy-3.1.0/cassettes/testshowlistsubscriber.json
tweepy-3.1.0/cassettes/testsubscribeunsubscribelist.json
tweepy-3.1.0/cassettes/testsuggestedcategories.json
tweepy-3.1.0/cassettes/testsuggestedusers.json
tweepy-3.1.0/cassettes/testsuggesteduserstweets.json
tweepy-3.1.0/cassettes/testsupportedlanguages.json
tweepy-3.1.0/cassettes/testupdateanddestroystatus.json
tweepy-3.1.0/cassettes/testupdateprofile.json
tweepy-3.1.0/cassettes/testupdateprofilebannerimage.yaml
tweepy-3.1.0/cassettes/testupdateprofilecolors.json
tweepy-3.1.0/cassettes/testupdatestatuswithmedia.yaml
tweepy-3.1.0/cassettes/testusertimeline.json
tweepy-3.1.0/cassettes/testverifycredentials.json
tweepy-3.1.0/docs/
tweepy-3.1.0/docs/.gitignore
tweepy-3.1.0/docs/Makefile
tweepy-3.1.0/docs/api.rst
tweepy-3.1.0/docs/auth_tutorial.rst
tweepy-3.1.0/docs/code_snippet.rst
tweepy-3.1.0/docs/conf.py
tweepy-3.1.0/docs/cursor_tutorial.rst
tweepy-3.1.0/docs/getting_started.rst
tweepy-3.1.0/docs/index.rst
tweepy-3.1.0/docs/install.rst
tweepy-3.1.0/docs/make.bat
tweepy-3.1.0/docs/parameters.rst
tweepy-3.1.0/examples/
tweepy-3.1.0/examples/__init__.py
tweepy-3.1.0/examples/banner.png
tweepy-3.1.0/examples/oauth.py
tweepy-3.1.0/examples/streaming.py
tweepy-3.1.0/requirements.txt
tweepy-3.1.0/setup.cfg
tweepy-3.1.0/setup.py
tweepy-3.1.0/test_requirements.txt
tweepy-3.1.0/tests/
tweepy-3.1.0/tests/__init__.py
tweepy-3.1.0/tests/config.py
tweepy-3.1.0/tests/record.json
tweepy-3.1.0/tests/test_api.py
tweepy-3.1.0/tests/test_auth.py
tweepy-3.1.0/tests/test_cursors.py
tweepy-3.1.0/tests/test_rate_limit.py
tweepy-3.1.0/tests/test_resultset.py
tweepy-3.1.0/tests/test_streaming.py
tweepy-3.1.0/tests/test_utils.py
tweepy-3.1.0/tests/travis-tests.cfg
tweepy-3.1.0/tox.ini
tweepy-3.1.0/tweepy/
tweepy-3.1.0/tweepy/__init__.py
tweepy-3.1.0/tweepy/api.py
tweepy-3.1.0/tweepy/auth.py
tweepy-3.1.0/tweepy/binder.py
tweepy-3.1.0/tweepy/cache.py
tweepy-3.1.0/tweepy/cursor.py
tweepy-3.1.0/tweepy/error.py
tweepy-3.1.0/tweepy/models.py
tweepy-3.1.0/tweepy/parsers.py
tweepy-3.1.0/tweepy/streaming.py
tweepy-3.1.0/tweepy/utils.py
patching file setup.py
Traceback (most recent call last):
  File "setup.py", line 17, in <module>
    install_reqs = parse_requirements('requirements.txt',
session=uuid.uuid1())
TypeError: parse_requirements() got an unexpected keyword argument 'session'

Looking for a little within the SlackBuild directory I found that the
indicated line is inside the update_req_for_pip6.patch file (exactly on
line 18).

Does anyone else have a similar problem?

Thanks in advance!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xCE1F1C53.asc
Type: application/pgp-keys
Size: 3096 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150513/12e67f77/attachment-0001.bin>

From icaro.perseo at gmail.com  Wed May 13 20:39:47 2015
From: icaro.perseo at gmail.com (Perseo)
Date: Wed, 13 May 2015 15:39:47 -0500
Subject: [Slackbuilds-users] tweepy SlackBuild error
Message-ID: <5553B693.7090609@gmail.com>

Good day!

In trying to build tweepy displays the following error:

tweepy-3.1.0/
tweepy-3.1.0/.coveragerc
tweepy-3.1.0/.gitignore
tweepy-3.1.0/.travis.yml
tweepy-3.1.0/ASCII_LOGO.txt
tweepy-3.1.0/CHANGELOG.md
tweepy-3.1.0/CONTRIBUTORS
tweepy-3.1.0/LICENSE
tweepy-3.1.0/MANIFEST.in
tweepy-3.1.0/README.md
tweepy-3.1.0/bindings_url_parser.py
tweepy-3.1.0/cassettes/
tweepy-3.1.0/cassettes/testaddremovelistmember.json
tweepy-3.1.0/cassettes/testaddremovelistmembers.json
tweepy-3.1.0/cassettes/testblocks.json
tweepy-3.1.0/cassettes/testblocksids.json
tweepy-3.1.0/cassettes/testcachedresult.json
tweepy-3.1.0/cassettes/testcreatedestroyblock.json
tweepy-3.1.0/cassettes/testcreatedestroyfavorite.json
tweepy-3.1.0/cassettes/testcreatedestroyfriendship.json
tweepy-3.1.0/cassettes/testcursorcursoritems.json
tweepy-3.1.0/cassettes/testcursorcursorpages.json
tweepy-3.1.0/cassettes/testcursornext.json
tweepy-3.1.0/cassettes/testdirectmessages.json
tweepy-3.1.0/cassettes/testfavorites.json
tweepy-3.1.0/cassettes/testfollowers.json
tweepy-3.1.0/cassettes/testfollowersids.json
tweepy-3.1.0/cassettes/testfriends.json
tweepy-3.1.0/cassettes/testfriendsids.json
tweepy-3.1.0/cassettes/testgeoapis.json
tweepy-3.1.0/cassettes/testgetlist.json
tweepy-3.1.0/cassettes/testgetoembed.json
tweepy-3.1.0/cassettes/testgetstatus.json
tweepy-3.1.0/cassettes/testgetuser.json
tweepy-3.1.0/cassettes/testhometimeline.json
tweepy-3.1.0/cassettes/testidcursoritems.json
tweepy-3.1.0/cassettes/testidcursorpages.json
tweepy-3.1.0/cassettes/testlistmembers.json
tweepy-3.1.0/cassettes/testlistsall.json
tweepy-3.1.0/cassettes/testlistsmemberships.json
tweepy-3.1.0/cassettes/testlistssubscriptions.json
tweepy-3.1.0/cassettes/testlistsubscribers.json
tweepy-3.1.0/cassettes/testlisttimeline.json
tweepy-3.1.0/cassettes/testlookupusers.json
tweepy-3.1.0/cassettes/testme.json
tweepy-3.1.0/cassettes/testmentionstimeline.json
tweepy-3.1.0/cassettes/testratelimitstatus.json
tweepy-3.1.0/cassettes/testretweeters.json
tweepy-3.1.0/cassettes/testretweets.json
tweepy-3.1.0/cassettes/testretweetsofme.json
tweepy-3.1.0/cassettes/testsavedsearches.json
tweepy-3.1.0/cassettes/testsearch.json
tweepy-3.1.0/cassettes/testsearchusers.json
tweepy-3.1.0/cassettes/testsendanddestroydirectmessage.json
tweepy-3.1.0/cassettes/testsentdirectmessages.json
tweepy-3.1.0/cassettes/testshowfriendship.json
tweepy-3.1.0/cassettes/testshowlistmember.json
tweepy-3.1.0/cassettes/testshowlistsubscriber.json
tweepy-3.1.0/cassettes/testsubscribeunsubscribelist.json
tweepy-3.1.0/cassettes/testsuggestedcategories.json
tweepy-3.1.0/cassettes/testsuggestedusers.json
tweepy-3.1.0/cassettes/testsuggesteduserstweets.json
tweepy-3.1.0/cassettes/testsupportedlanguages.json
tweepy-3.1.0/cassettes/testupdateanddestroystatus.json
tweepy-3.1.0/cassettes/testupdateprofile.json
tweepy-3.1.0/cassettes/testupdateprofilebannerimage.yaml
tweepy-3.1.0/cassettes/testupdateprofilecolors.json
tweepy-3.1.0/cassettes/testupdatestatuswithmedia.yaml
tweepy-3.1.0/cassettes/testusertimeline.json
tweepy-3.1.0/cassettes/testverifycredentials.json
tweepy-3.1.0/docs/
tweepy-3.1.0/docs/.gitignore
tweepy-3.1.0/docs/Makefile
tweepy-3.1.0/docs/api.rst
tweepy-3.1.0/docs/auth_tutorial.rst
tweepy-3.1.0/docs/code_snippet.rst
tweepy-3.1.0/docs/conf.py
tweepy-3.1.0/docs/cursor_tutorial.rst
tweepy-3.1.0/docs/getting_started.rst
tweepy-3.1.0/docs/index.rst
tweepy-3.1.0/docs/install.rst
tweepy-3.1.0/docs/make.bat
tweepy-3.1.0/docs/parameters.rst
tweepy-3.1.0/examples/
tweepy-3.1.0/examples/__init__.py
tweepy-3.1.0/examples/banner.png
tweepy-3.1.0/examples/oauth.py
tweepy-3.1.0/examples/streaming.py
tweepy-3.1.0/requirements.txt
tweepy-3.1.0/setup.cfg
tweepy-3.1.0/setup.py
tweepy-3.1.0/test_requirements.txt
tweepy-3.1.0/tests/
tweepy-3.1.0/tests/__init__.py
tweepy-3.1.0/tests/config.py
tweepy-3.1.0/tests/record.json
tweepy-3.1.0/tests/test_api.py
tweepy-3.1.0/tests/test_auth.py
tweepy-3.1.0/tests/test_cursors.py
tweepy-3.1.0/tests/test_rate_limit.py
tweepy-3.1.0/tests/test_resultset.py
tweepy-3.1.0/tests/test_streaming.py
tweepy-3.1.0/tests/test_utils.py
tweepy-3.1.0/tests/travis-tests.cfg
tweepy-3.1.0/tox.ini
tweepy-3.1.0/tweepy/
tweepy-3.1.0/tweepy/__init__.py
tweepy-3.1.0/tweepy/api.py
tweepy-3.1.0/tweepy/auth.py
tweepy-3.1.0/tweepy/binder.py
tweepy-3.1.0/tweepy/cache.py
tweepy-3.1.0/tweepy/cursor.py
tweepy-3.1.0/tweepy/error.py
tweepy-3.1.0/tweepy/models.py
tweepy-3.1.0/tweepy/parsers.py
tweepy-3.1.0/tweepy/streaming.py
tweepy-3.1.0/tweepy/utils.py
patching file setup.py
Traceback (most recent call last):
  File "setup.py", line 17, in <module>
    install_reqs = parse_requirements('requirements.txt',
session=uuid.uuid1())
TypeError: parse_requirements() got an unexpected keyword argument 'session'

Looking for a little within the SlackBuild directory I found that the
indicated line is inside the update_req_for_pip6.patch file (line 18).

Sorry for the duplicated email (my internet connection s*cks!).

Thanks in advance!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xCE1F1C53.asc
Type: application/pgp-keys
Size: 3096 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150513/ea06fea5/attachment.bin>

From matteo.bernardini at gmail.com  Wed May 13 20:51:37 2015
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 13 May 2015 22:51:37 +0200
Subject: [Slackbuilds-users] tweepy SlackBuild error
In-Reply-To: <5553B693.7090609@gmail.com>
References: <5553B693.7090609@gmail.com>
Message-ID: <CAPsDuS5R9fej0TQ9uxUM__nXKy88LuQinqq5Bv36qGqi_c0UAg@mail.gmail.com>

2015-05-13 22:39 GMT+02:00 Perseo <icaro.perseo at gmail.com>:
> tweepy-3.1.0/tweepy/utils.py
> patching file setup.py
> Traceback (most recent call last):
>   File "setup.py", line 17, in <module>
>     install_reqs = parse_requirements('requirements.txt',
> session=uuid.uuid1())
> TypeError: parse_requirements() got an unexpected keyword argument 'session'

here seems to work fine.
are you passing some parameters to the slackbuild or are you running
it without parameters?

Matteo

From icaro.perseo at gmail.com  Wed May 13 20:57:34 2015
From: icaro.perseo at gmail.com (Perseo)
Date: Wed, 13 May 2015 15:57:34 -0500
Subject: [Slackbuilds-users] tweepy SlackBuild error
In-Reply-To: <CAPsDuS5R9fej0TQ9uxUM__nXKy88LuQinqq5Bv36qGqi_c0UAg@mail.gmail.com>
References: <5553B693.7090609@gmail.com>
 <CAPsDuS5R9fej0TQ9uxUM__nXKy88LuQinqq5Bv36qGqi_c0UAg@mail.gmail.com>
Message-ID: <5553BABE.1040005@gmail.com>

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

I run as follows:

fakeroot ./tweepy.SlackBuild


El 13/05/15 a las 15:51, Matteo Bernardini escribi?:
> 2015-05-13 22:39 GMT+02:00 Perseo <icaro.perseo at gmail.com>:
>> tweepy-3.1.0/tweepy/utils.py patching file setup.py Traceback
>> (most recent call last): File "setup.py", line 17, in <module> 
>> install_reqs = parse_requirements('requirements.txt', 
>> session=uuid.uuid1()) TypeError: parse_requirements() got an
>> unexpected keyword argument 'session'
> 
> here seems to work fine. are you passing some parameters to the
> slackbuild or are you running it without parameters?
> 
> Matteo _______________________________________________ 
> SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org 
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users 
> Archives -
> http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ -
> http://slackbuilds.org/faq/
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJVU7q+AAoJEPFiITbOHxxTgPkQAK0b3TwVTiVgqIeVkEEG9dnx
W7yyO9oERrJobcJIZwmC6gkyGyE0oqfqrA5aZ8E/jwuDu96cp7aWnL/IIYNx3H7T
F8FERYHtjFX0h0VmKVoKDCftzwV10y+V7jYG5wVsbO9mioezz1fg1Yo84Czf8qBp
72aHD4Tm5JF2IeDcy8lw3PTBNt6N8Jxp6twBISlV5AUj6gk1LWqbm4XqwEZqwbmj
qBL3AL/LbSXmEVkZnnyC4I5i3xtypmau9kLH/xDy5s5h2BMZqUdBi5dpZEsj/1KU
O0DrCAc9nsrNFBr+ExJTF+AkBrYS3dPNBKA+U2ytnbmHfh1JA7xMeXShgR1p4hbD
rw1yC24+2B8Qal130kMnPmx2AzThtCOgEnAIhXQhN+wiNkxt23EHPwuVNaPy+77K
Il0/M4KVLCxznYqFSFnPp/lD/dhcVF3Dvvmo8FHBg/tUEO9kORmetAYh+rK4rF6+
Y97v8Gfn8/y2fCKzEuQI0Sog7yd+GnHJCQEQRxcL+NlpMbCdUKXRJfP1hoJNbEVe
aoilWzYUwmSv6tCg6pq8DHzY0QfWmW3DTTJtHypxn+Pl+PUPON3LAuXePcajAE6p
2XtM2wdxysXW4qB1rAEMdwmOoKG2CslF93mD8in2XVuaht1Rru4BJlCWDgwMkWmd
Z4lBhijqqQHMW/Ty3zIW
=KaO9
-----END PGP SIGNATURE-----

From matteo.bernardini at gmail.com  Wed May 13 21:26:12 2015
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 13 May 2015 23:26:12 +0200
Subject: [Slackbuilds-users] tweepy SlackBuild error
In-Reply-To: <5553BABE.1040005@gmail.com>
References: <5553B693.7090609@gmail.com>
 <CAPsDuS5R9fej0TQ9uxUM__nXKy88LuQinqq5Bv36qGqi_c0UAg@mail.gmail.com>
 <5553BABE.1040005@gmail.com>
Message-ID: <CAPsDuS6FTHWzc_ashMOwRzzM6ecDr1NgfWy7sjm-ne-EB+Bsew@mail.gmail.com>

2015-05-13 22:57 GMT+02:00 Perseo <icaro.perseo at gmail.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I run as follows:
>
> fakeroot ./tweepy.SlackBuild

- are you sure you built all dependencies? also dependencies of dependencies?

- have you tried running it without fakeroot?

From icaro.perseo at gmail.com  Wed May 13 21:38:09 2015
From: icaro.perseo at gmail.com (Perseo)
Date: Wed, 13 May 2015 16:38:09 -0500
Subject: [Slackbuilds-users] tweepy SlackBuild error
In-Reply-To: <CAPsDuS6FTHWzc_ashMOwRzzM6ecDr1NgfWy7sjm-ne-EB+Bsew@mail.gmail.com>
References: <5553B693.7090609@gmail.com>
 <CAPsDuS5R9fej0TQ9uxUM__nXKy88LuQinqq5Bv36qGqi_c0UAg@mail.gmail.com>
 <5553BABE.1040005@gmail.com>
 <CAPsDuS6FTHWzc_ashMOwRzzM6ecDr1NgfWy7sjm-ne-EB+Bsew@mail.gmail.com>
Message-ID: <5553C441.90303@gmail.com>

Running as root:

root[tweepy]# ./tweepy.SlackBuild
tweepy-3.1.0/
tweepy-3.1.0/.coveragerc
tweepy-3.1.0/.gitignore
tweepy-3.1.0/.travis.yml
tweepy-3.1.0/ASCII_LOGO.txt
tweepy-3.1.0/CHANGELOG.md
tweepy-3.1.0/CONTRIBUTORS
tweepy-3.1.0/LICENSE
tweepy-3.1.0/MANIFEST.in
tweepy-3.1.0/README.md
tweepy-3.1.0/bindings_url_parser.py
tweepy-3.1.0/cassettes/
tweepy-3.1.0/cassettes/testaddremovelistmember.json
tweepy-3.1.0/cassettes/testaddremovelistmembers.json
tweepy-3.1.0/cassettes/testblocks.json
tweepy-3.1.0/cassettes/testblocksids.json
tweepy-3.1.0/cassettes/testcachedresult.json
tweepy-3.1.0/cassettes/testcreatedestroyblock.json
tweepy-3.1.0/cassettes/testcreatedestroyfavorite.json
tweepy-3.1.0/cassettes/testcreatedestroyfriendship.json
tweepy-3.1.0/cassettes/testcursorcursoritems.json
tweepy-3.1.0/cassettes/testcursorcursorpages.json
tweepy-3.1.0/cassettes/testcursornext.json
tweepy-3.1.0/cassettes/testdirectmessages.json
tweepy-3.1.0/cassettes/testfavorites.json
tweepy-3.1.0/cassettes/testfollowers.json
tweepy-3.1.0/cassettes/testfollowersids.json
tweepy-3.1.0/cassettes/testfriends.json
tweepy-3.1.0/cassettes/testfriendsids.json
tweepy-3.1.0/cassettes/testgeoapis.json
tweepy-3.1.0/cassettes/testgetlist.json
tweepy-3.1.0/cassettes/testgetoembed.json
tweepy-3.1.0/cassettes/testgetstatus.json
tweepy-3.1.0/cassettes/testgetuser.json
tweepy-3.1.0/cassettes/testhometimeline.json
tweepy-3.1.0/cassettes/testidcursoritems.json
tweepy-3.1.0/cassettes/testidcursorpages.json
tweepy-3.1.0/cassettes/testlistmembers.json
tweepy-3.1.0/cassettes/testlistsall.json
tweepy-3.1.0/cassettes/testlistsmemberships.json
tweepy-3.1.0/cassettes/testlistssubscriptions.json
tweepy-3.1.0/cassettes/testlistsubscribers.json
tweepy-3.1.0/cassettes/testlisttimeline.json
tweepy-3.1.0/cassettes/testlookupusers.json
tweepy-3.1.0/cassettes/testme.json
tweepy-3.1.0/cassettes/testmentionstimeline.json
tweepy-3.1.0/cassettes/testratelimitstatus.json
tweepy-3.1.0/cassettes/testretweeters.json
tweepy-3.1.0/cassettes/testretweets.json
tweepy-3.1.0/cassettes/testretweetsofme.json
tweepy-3.1.0/cassettes/testsavedsearches.json
tweepy-3.1.0/cassettes/testsearch.json
tweepy-3.1.0/cassettes/testsearchusers.json
tweepy-3.1.0/cassettes/testsendanddestroydirectmessage.json
tweepy-3.1.0/cassettes/testsentdirectmessages.json
tweepy-3.1.0/cassettes/testshowfriendship.json
tweepy-3.1.0/cassettes/testshowlistmember.json
tweepy-3.1.0/cassettes/testshowlistsubscriber.json
tweepy-3.1.0/cassettes/testsubscribeunsubscribelist.json
tweepy-3.1.0/cassettes/testsuggestedcategories.json
tweepy-3.1.0/cassettes/testsuggestedusers.json
tweepy-3.1.0/cassettes/testsuggesteduserstweets.json
tweepy-3.1.0/cassettes/testsupportedlanguages.json
tweepy-3.1.0/cassettes/testupdateanddestroystatus.json
tweepy-3.1.0/cassettes/testupdateprofile.json
tweepy-3.1.0/cassettes/testupdateprofilebannerimage.yaml
tweepy-3.1.0/cassettes/testupdateprofilecolors.json
tweepy-3.1.0/cassettes/testupdatestatuswithmedia.yaml
tweepy-3.1.0/cassettes/testusertimeline.json
tweepy-3.1.0/cassettes/testverifycredentials.json
tweepy-3.1.0/docs/
tweepy-3.1.0/docs/.gitignore
tweepy-3.1.0/docs/Makefile
tweepy-3.1.0/docs/api.rst
tweepy-3.1.0/docs/auth_tutorial.rst
tweepy-3.1.0/docs/code_snippet.rst
tweepy-3.1.0/docs/conf.py
tweepy-3.1.0/docs/cursor_tutorial.rst
tweepy-3.1.0/docs/getting_started.rst
tweepy-3.1.0/docs/index.rst
tweepy-3.1.0/docs/install.rst
tweepy-3.1.0/docs/make.bat
tweepy-3.1.0/docs/parameters.rst
tweepy-3.1.0/examples/
tweepy-3.1.0/examples/__init__.py
tweepy-3.1.0/examples/banner.png
tweepy-3.1.0/examples/oauth.py
tweepy-3.1.0/examples/streaming.py
tweepy-3.1.0/requirements.txt
tweepy-3.1.0/setup.cfg
tweepy-3.1.0/setup.py
tweepy-3.1.0/test_requirements.txt
tweepy-3.1.0/tests/
tweepy-3.1.0/tests/__init__.py
tweepy-3.1.0/tests/config.py
tweepy-3.1.0/tests/record.json
tweepy-3.1.0/tests/test_api.py
tweepy-3.1.0/tests/test_auth.py
tweepy-3.1.0/tests/test_cursors.py
tweepy-3.1.0/tests/test_rate_limit.py
tweepy-3.1.0/tests/test_resultset.py
tweepy-3.1.0/tests/test_streaming.py
tweepy-3.1.0/tests/test_utils.py
tweepy-3.1.0/tests/travis-tests.cfg
tweepy-3.1.0/tox.ini
tweepy-3.1.0/tweepy/
tweepy-3.1.0/tweepy/__init__.py
tweepy-3.1.0/tweepy/api.py
tweepy-3.1.0/tweepy/auth.py
tweepy-3.1.0/tweepy/binder.py
tweepy-3.1.0/tweepy/cache.py
tweepy-3.1.0/tweepy/cursor.py
tweepy-3.1.0/tweepy/error.py
tweepy-3.1.0/tweepy/models.py
tweepy-3.1.0/tweepy/parsers.py
tweepy-3.1.0/tweepy/streaming.py
tweepy-3.1.0/tweepy/utils.py
patching file setup.py
The temporary folder for building (/tmp/pip_build_root) is not owned by
your user!
pip will not work until the temporary folder is either deleted or owned
by your user account.
Traceback (most recent call last):
  File "setup.py", line 5, in <module>
    from pip.req import parse_requirements
  File "/usr/lib64/python2.7/site-packages/pip/__init__.py", line 10, in
<module>
    from pip.util import get_installed_distributions, get_prog
  File "/usr/lib64/python2.7/site-packages/pip/util.py", line 15, in
<module>
    from pip.locations import site_packages, running_under_virtualenv,
virtualenv_no_global
  File "/usr/lib64/python2.7/site-packages/pip/locations.py", line 92,
in <module>
    build_prefix = _get_build_prefix()
  File "/usr/lib64/python2.7/site-packages/pip/locations.py", line 82,
in _get_build_prefix
    raise pip.exceptions.InstallationError(msg)
pip.exceptions.InstallationError: The temporary folder for building
(/tmp/pip_build_root) is not owned by your user!

On the other hand, yes, I have installed its dependencies

:)

El 13/05/15 a las 16:26, Matteo Bernardini escribi?:
> 2015-05-13 22:57 GMT+02:00 Perseo <icaro.perseo at gmail.com>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I run as follows:
>>
>> fakeroot ./tweepy.SlackBuild
> 
> - are you sure you built all dependencies? also dependencies of dependencies?
> 
> - have you tried running it without fakeroot?
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
> 

From matteo.bernardini at gmail.com  Wed May 13 21:48:29 2015
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 13 May 2015 23:48:29 +0200
Subject: [Slackbuilds-users] tweepy SlackBuild error
In-Reply-To: <5553C441.90303@gmail.com>
References: <5553B693.7090609@gmail.com>
 <CAPsDuS5R9fej0TQ9uxUM__nXKy88LuQinqq5Bv36qGqi_c0UAg@mail.gmail.com>
 <5553BABE.1040005@gmail.com>
 <CAPsDuS6FTHWzc_ashMOwRzzM6ecDr1NgfWy7sjm-ne-EB+Bsew@mail.gmail.com>
 <5553C441.90303@gmail.com>
Message-ID: <CAPsDuS6=HynOQR6gTwDXawMcKTUyQxY8rb_HhkW0LV-A6WM42A@mail.gmail.com>

2015-05-13 23:38 GMT+02:00 Perseo <icaro.perseo at gmail.com>:
> The temporary folder for building (/tmp/pip_build_root) is not owned by
> your user!
> pip will not work until the temporary folder is either deleted or owned
> by your user account.

can you try removing this /tmp/pip_build_root as the build process
seems asking: as root issue a

rm -fR /tmp/pip_build_root

From k.venken at online.be  Wed May 13 21:52:35 2015
From: k.venken at online.be (Karel Venken)
Date: Wed, 13 May 2015 23:52:35 +0200
Subject: [Slackbuilds-users] tweepy SlackBuild error
In-Reply-To: <CAPsDuS6FTHWzc_ashMOwRzzM6ecDr1NgfWy7sjm-ne-EB+Bsew@mail.gmail.com>
References: <5553B693.7090609@gmail.com>
 <CAPsDuS5R9fej0TQ9uxUM__nXKy88LuQinqq5Bv36qGqi_c0UAg@mail.gmail.com>
 <5553BABE.1040005@gmail.com>
 <CAPsDuS6FTHWzc_ashMOwRzzM6ecDr1NgfWy7sjm-ne-EB+Bsew@mail.gmail.com>
Message-ID: <5553C7A3.5060409@online.be>

Matteo Bernardini wrote:
> 2015-05-13 22:57 GMT+02:00 Perseo <icaro.perseo at gmail.com>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I run as follows:
>>
>> fakeroot ./tweepy.SlackBuild
> - are you sure you built all dependencies? also dependencies of dependencies?
>
> - have you tried running it without fakeroot?
>
Not sure if it helps, but these are the dependencies

bash-4.2# getpkgs -o test -t shared -grH tweepy
tweepy
   pip
     pysetuptools
   requests-oauthlib
     python-requests
     python-oauthlib
       pysetuptools
       pycrypto
   six

builds fine (on 64 bit with multilib installed...)

K.

From alisonken1 at juno.com  Wed May 13 22:09:05 2015
From: alisonken1 at juno.com (Ken-Allison Roberts)
Date: Wed, 13 May 2015 22:09:05 GMT
Subject: [Slackbuilds-users] tweepy SlackBuild error
Message-ID: <20150513.150905.27186.0@webmail09.vgs.untd.com>


Notice these lines: The temporary folder for building (/tmp/pip_build_root) is not owned byyour user!pip will not work until the temporary folder is either deleted or ownedby your user account. As noted, might try deleting the tmp directory and/or creating a temp directory with the owner set to the same user


- Ken Roberts
Do you Slack? Slackware Linux since 1993
____________________________________________________________
What Apple Didn???t say
One little-known tech company behind Apple is positioned to dominate.
http://thirdpartyoffers.juno.com/TGL3131/5553cbd06dd104bd07b49st04vuc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150513/5c692484/attachment.html>

From icaro.perseo at gmail.com  Wed May 13 22:36:56 2015
From: icaro.perseo at gmail.com (Perseo)
Date: Wed, 13 May 2015 17:36:56 -0500
Subject: [Slackbuilds-users] tweepy SlackBuild error
In-Reply-To: <CAPsDuS6=HynOQR6gTwDXawMcKTUyQxY8rb_HhkW0LV-A6WM42A@mail.gmail.com>
References: <5553B693.7090609@gmail.com>
 <CAPsDuS5R9fej0TQ9uxUM__nXKy88LuQinqq5Bv36qGqi_c0UAg@mail.gmail.com>
 <5553BABE.1040005@gmail.com>
 <CAPsDuS6FTHWzc_ashMOwRzzM6ecDr1NgfWy7sjm-ne-EB+Bsew@mail.gmail.com>
 <5553C441.90303@gmail.com>
 <CAPsDuS6=HynOQR6gTwDXawMcKTUyQxY8rb_HhkW0LV-A6WM42A@mail.gmail.com>
Message-ID: <5553D208.8090701@gmail.com>

Thanks to all but no luck. Same issue :S

root[tweepy]# rm -fR /tmp/pip_build_root
root[tweepy]# ./tweepy.SlackBuild
tweepy-3.1.0/
tweepy-3.1.0/.coveragerc
tweepy-3.1.0/.gitignore
tweepy-3.1.0/.travis.yml
tweepy-3.1.0/ASCII_LOGO.txt
tweepy-3.1.0/CHANGELOG.md
tweepy-3.1.0/CONTRIBUTORS
tweepy-3.1.0/LICENSE
tweepy-3.1.0/MANIFEST.in
tweepy-3.1.0/README.md
tweepy-3.1.0/bindings_url_parser.py
tweepy-3.1.0/cassettes/
tweepy-3.1.0/cassettes/testaddremovelistmember.json
tweepy-3.1.0/cassettes/testaddremovelistmembers.json
tweepy-3.1.0/cassettes/testblocks.json
tweepy-3.1.0/cassettes/testblocksids.json
tweepy-3.1.0/cassettes/testcachedresult.json
tweepy-3.1.0/cassettes/testcreatedestroyblock.json
tweepy-3.1.0/cassettes/testcreatedestroyfavorite.json
tweepy-3.1.0/cassettes/testcreatedestroyfriendship.json
tweepy-3.1.0/cassettes/testcursorcursoritems.json
tweepy-3.1.0/cassettes/testcursorcursorpages.json
tweepy-3.1.0/cassettes/testcursornext.json
tweepy-3.1.0/cassettes/testdirectmessages.json
tweepy-3.1.0/cassettes/testfavorites.json
tweepy-3.1.0/cassettes/testfollowers.json
tweepy-3.1.0/cassettes/testfollowersids.json
tweepy-3.1.0/cassettes/testfriends.json
tweepy-3.1.0/cassettes/testfriendsids.json
tweepy-3.1.0/cassettes/testgeoapis.json
tweepy-3.1.0/cassettes/testgetlist.json
tweepy-3.1.0/cassettes/testgetoembed.json
tweepy-3.1.0/cassettes/testgetstatus.json
tweepy-3.1.0/cassettes/testgetuser.json
tweepy-3.1.0/cassettes/testhometimeline.json
tweepy-3.1.0/cassettes/testidcursoritems.json
tweepy-3.1.0/cassettes/testidcursorpages.json
tweepy-3.1.0/cassettes/testlistmembers.json
tweepy-3.1.0/cassettes/testlistsall.json
tweepy-3.1.0/cassettes/testlistsmemberships.json
tweepy-3.1.0/cassettes/testlistssubscriptions.json
tweepy-3.1.0/cassettes/testlistsubscribers.json
tweepy-3.1.0/cassettes/testlisttimeline.json
tweepy-3.1.0/cassettes/testlookupusers.json
tweepy-3.1.0/cassettes/testme.json
tweepy-3.1.0/cassettes/testmentionstimeline.json
tweepy-3.1.0/cassettes/testratelimitstatus.json
tweepy-3.1.0/cassettes/testretweeters.json
tweepy-3.1.0/cassettes/testretweets.json
tweepy-3.1.0/cassettes/testretweetsofme.json
tweepy-3.1.0/cassettes/testsavedsearches.json
tweepy-3.1.0/cassettes/testsearch.json
tweepy-3.1.0/cassettes/testsearchusers.json
tweepy-3.1.0/cassettes/testsendanddestroydirectmessage.json
tweepy-3.1.0/cassettes/testsentdirectmessages.json
tweepy-3.1.0/cassettes/testshowfriendship.json
tweepy-3.1.0/cassettes/testshowlistmember.json
tweepy-3.1.0/cassettes/testshowlistsubscriber.json
tweepy-3.1.0/cassettes/testsubscribeunsubscribelist.json
tweepy-3.1.0/cassettes/testsuggestedcategories.json
tweepy-3.1.0/cassettes/testsuggestedusers.json
tweepy-3.1.0/cassettes/testsuggesteduserstweets.json
tweepy-3.1.0/cassettes/testsupportedlanguages.json
tweepy-3.1.0/cassettes/testupdateanddestroystatus.json
tweepy-3.1.0/cassettes/testupdateprofile.json
tweepy-3.1.0/cassettes/testupdateprofilebannerimage.yaml
tweepy-3.1.0/cassettes/testupdateprofilecolors.json
tweepy-3.1.0/cassettes/testupdatestatuswithmedia.yaml
tweepy-3.1.0/cassettes/testusertimeline.json
tweepy-3.1.0/cassettes/testverifycredentials.json
tweepy-3.1.0/docs/
tweepy-3.1.0/docs/.gitignore
tweepy-3.1.0/docs/Makefile
tweepy-3.1.0/docs/api.rst
tweepy-3.1.0/docs/auth_tutorial.rst
tweepy-3.1.0/docs/code_snippet.rst
tweepy-3.1.0/docs/conf.py
tweepy-3.1.0/docs/cursor_tutorial.rst
tweepy-3.1.0/docs/getting_started.rst
tweepy-3.1.0/docs/index.rst
tweepy-3.1.0/docs/install.rst
tweepy-3.1.0/docs/make.bat
tweepy-3.1.0/docs/parameters.rst
tweepy-3.1.0/examples/
tweepy-3.1.0/examples/__init__.py
tweepy-3.1.0/examples/banner.png
tweepy-3.1.0/examples/oauth.py
tweepy-3.1.0/examples/streaming.py
tweepy-3.1.0/requirements.txt
tweepy-3.1.0/setup.cfg
tweepy-3.1.0/setup.py
tweepy-3.1.0/test_requirements.txt
tweepy-3.1.0/tests/
tweepy-3.1.0/tests/__init__.py
tweepy-3.1.0/tests/config.py
tweepy-3.1.0/tests/record.json
tweepy-3.1.0/tests/test_api.py
tweepy-3.1.0/tests/test_auth.py
tweepy-3.1.0/tests/test_cursors.py
tweepy-3.1.0/tests/test_rate_limit.py
tweepy-3.1.0/tests/test_resultset.py
tweepy-3.1.0/tests/test_streaming.py
tweepy-3.1.0/tests/test_utils.py
tweepy-3.1.0/tests/travis-tests.cfg
tweepy-3.1.0/tox.ini
tweepy-3.1.0/tweepy/
tweepy-3.1.0/tweepy/__init__.py
tweepy-3.1.0/tweepy/api.py
tweepy-3.1.0/tweepy/auth.py
tweepy-3.1.0/tweepy/binder.py
tweepy-3.1.0/tweepy/cache.py
tweepy-3.1.0/tweepy/cursor.py
tweepy-3.1.0/tweepy/error.py
tweepy-3.1.0/tweepy/models.py
tweepy-3.1.0/tweepy/parsers.py
tweepy-3.1.0/tweepy/streaming.py
tweepy-3.1.0/tweepy/utils.py
patching file setup.py
Traceback (most recent call last):
  File "setup.py", line 17, in <module>
    install_reqs = parse_requirements('requirements.txt',
session=uuid.uuid1())
TypeError: parse_requirements() got an unexpected keyword argument 'session'

I rechecked my dependencies but the problem is not in there

El 13/05/15 a las 16:48, Matteo Bernardini escribi?:
> 2015-05-13 23:38 GMT+02:00 Perseo <icaro.perseo at gmail.com>:
>> The temporary folder for building (/tmp/pip_build_root) is not owned by
>> your user!
>> pip will not work until the temporary folder is either deleted or owned
>> by your user account.
> 
> can you try removing this /tmp/pip_build_root as the build process
> seems asking: as root issue a
> 
> rm -fR /tmp/pip_build_root
> _______________________________________________
> 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 k.venken at online.be  Wed May 13 22:50:09 2015
From: k.venken at online.be (Karel Venken)
Date: Thu, 14 May 2015 00:50:09 +0200
Subject: [Slackbuilds-users] tweepy SlackBuild error
In-Reply-To: <5553D208.8090701@gmail.com>
References: <5553B693.7090609@gmail.com>
 <CAPsDuS5R9fej0TQ9uxUM__nXKy88LuQinqq5Bv36qGqi_c0UAg@mail.gmail.com>
 <5553BABE.1040005@gmail.com>
 <CAPsDuS6FTHWzc_ashMOwRzzM6ecDr1NgfWy7sjm-ne-EB+Bsew@mail.gmail.com>
 <5553C441.90303@gmail.com>
 <CAPsDuS6=HynOQR6gTwDXawMcKTUyQxY8rb_HhkW0LV-A6WM42A@mail.gmail.com>
 <5553D208.8090701@gmail.com>
Message-ID: <5553D521.9070504@online.be>

Perseo wrote:
> Thanks to all but no luck. Same issue :S
>
>
Just a guess, incorrect, old ? versions? Someone (googled) mentioned to 
update pip, mine is version

bash-4.2# pip --version
pip 6.1.1 from /usr/lib64/python2.7/site-packages (python 2.7)

K.

From icaro.perseo at gmail.com  Wed May 13 23:46:25 2015
From: icaro.perseo at gmail.com (Perseo)
Date: Wed, 13 May 2015 18:46:25 -0500
Subject: [Slackbuilds-users] tweepy SlackBuild error
In-Reply-To: <5553D521.9070504@online.be>
References: <5553B693.7090609@gmail.com>
 <CAPsDuS5R9fej0TQ9uxUM__nXKy88LuQinqq5Bv36qGqi_c0UAg@mail.gmail.com>
 <5553BABE.1040005@gmail.com>
 <CAPsDuS6FTHWzc_ashMOwRzzM6ecDr1NgfWy7sjm-ne-EB+Bsew@mail.gmail.com>
 <5553C441.90303@gmail.com>
 <CAPsDuS6=HynOQR6gTwDXawMcKTUyQxY8rb_HhkW0LV-A6WM42A@mail.gmail.com>
 <5553D208.8090701@gmail.com> <5553D521.9070504@online.be>
Message-ID: <5553E251.5090801@gmail.com>

Bingo!

Thanks a lot everybody, I had pip 1.4.1 :S I upgraded to 6.1.1

Now everything is perfect.

El 13/05/15 a las 17:50, Karel Venken escribi?:
> Perseo wrote:
>> Thanks to all but no luck. Same issue :S
>>
>>
> Just a guess, incorrect, old ? versions? Someone (googled) mentioned to
> update pip, mine is version
> 
> bash-4.2# pip --version
> pip 6.1.1 from /usr/lib64/python2.7/site-packages (python 2.7)
> 
> K.
> _______________________________________________
> 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 kingbeowulf at gmail.com  Fri May 15 00:15:41 2015
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 14 May 2015 17:15:41 -0700
Subject: [Slackbuilds-users]  qemu-2.3.0 Venom patch update
Message-ID: <55553AAD.6080604@gmail.com>

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

All

I just submitted a patched qemu.Slackbuild (thanks willy). I don't use
floppy drives so wouldn't know how to test this!

I suggests the admins fast track this one.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3456

http://git.qemu.org/?p=qemu.git;a=commitdiff;h=e907746266721f305d67bc071
8795fedee2e824c

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

iEYEARECAAYFAlVVOqMACgkQXvwMaW61dLd8MwCePkL1u6ln3LRAH6LjGpGqJ1U+
LbMAn0ly3dEZVuZPAWevlncVr/g8mz6l
=Np2Y
-----END PGP SIGNATURE-----

From willysr at slackbuilds.org  Fri May 15 00:24:02 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 15 May 2015 07:24:02 +0700
Subject: [Slackbuilds-users] qemu-2.3.0 Venom patch update
In-Reply-To: <55553AAD.6080604@gmail.com>
References: <55553AAD.6080604@gmail.com>
Message-ID: <55553CA2.60505@slackbuilds.org>

> I just submitted a patched qemu.Slackbuild (thanks willy). I don't use
> floppy drives so wouldn't know how to test this!
> 
> I suggests the admins fast track this one.
> 
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3456
> 
> http://git.qemu.org/?p=qemu.git;a=commitdiff;h=e907746266721f305d67bc071
> 8795fedee2e824c

I already applied this to my branch under my name yesterday, but it's
better for the maintainer to step up :)


-- 
Willy Sudiarto Raharjo

From kingbeowulf at gmail.com  Fri May 15 00:38:06 2015
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 14 May 2015 17:38:06 -0700
Subject: [Slackbuilds-users] qemu-2.3.0 Venom patch update
In-Reply-To: <55553CA2.60505@slackbuilds.org>
References: <55553AAD.6080604@gmail.com> <55553CA2.60505@slackbuilds.org>
Message-ID: <55553FEE.608@gmail.com>

On 05/14/2015 05:24 PM, Willy Sudiarto Raharjo wrote:
>> I just submitted a patched qemu.Slackbuild (thanks willy). I don't use
>> floppy drives so wouldn't know how to test this!
>>
>> I suggests the admins fast track this one.
>>
>> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3456
>>
>> http://git.qemu.org/?p=qemu.git;a=commitdiff;h=e907746266721f305d67bc071
>> 8795fedee2e824c
> 
> I already applied this to my branch under my name yesterday, but it's
> better for the maintainer to step up :)
> 
> 
Ha!  And you thought I didn't look at my Twitter account! ;-o



From willysr at slackbuilds.org  Fri May 15 00:40:33 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 15 May 2015 07:40:33 +0700
Subject: [Slackbuilds-users] qemu-2.3.0 Venom patch update
In-Reply-To: <55553FEE.608@gmail.com>
References: <55553AAD.6080604@gmail.com> <55553CA2.60505@slackbuilds.org>
 <55553FEE.608@gmail.com>
Message-ID: <55554081.2050000@slackbuilds.org>

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

> Ha!  And you thought I didn't look at my Twitter account! ;-o

I just worried that you are too busy and since i got no reply and this
is a critical applications, i applied the patch first, but now it's
under your name :)

- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVVQIEACgkQiHuDdNczM4FIggCffb7xfT59Z4KUSIWLfQEAd2t+
oIYAn0TubIyjh8zzRgCl7ODBnyhfWcUe
=kXUx
-----END PGP SIGNATURE-----

From info at microlinux.fr  Fri May 15 05:49:54 2015
From: info at microlinux.fr (Niki Kovacs)
Date: Fri, 15 May 2015 07:49:54 +0200
Subject: [Slackbuilds-users] Permissions on rc.postfix
Message-ID: <55558902.6070708@microlinux.fr>

Hi,

When I install Postfix using the SlackBuild script from SBo, rc.postfix 
is executable (0755) right after the installation.

Shouldn't a more sensible default configuration set /etc/rc.d/rc.postfix 
to 0644 post-install?

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  Fri May 15 06:37:14 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 15 May 2015 13:37:14 +0700
Subject: [Slackbuilds-users] Permissions on rc.postfix
In-Reply-To: <55558902.6070708@microlinux.fr>
References: <55558902.6070708@microlinux.fr>
Message-ID: <5555941A.7070707@slackbuilds.org>

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

> When I install Postfix using the SlackBuild script from SBo,
> rc.postfix is executable (0755) right after the installation.
> 
> Shouldn't a more sensible default configuration set
> /etc/rc.d/rc.postfix to 0644 post-install?

Fixed on my branch

Thanks


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVVlBoACgkQiHuDdNczM4Eh8gCfWhnp3QPRWPYA39la0aTVD0MZ
/sUAoKk49lLpcOwzIO+rLCKoBrzCVw0+
=RaTO
-----END PGP SIGNATURE-----

From rworkman at slackbuilds.org  Fri May 15 13:33:23 2015
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 15 May 2015 08:33:23 -0500
Subject: [Slackbuilds-users] Permissions on rc.postfix
In-Reply-To: <5555941A.7070707@slackbuilds.org>
References: <55558902.6070708@microlinux.fr> <5555941A.7070707@slackbuilds.org>
Message-ID: <20150515083323.3fba355c@home.rlworkman.net>

On Fri, 15 May 2015 13:37:14 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> > When I install Postfix using the SlackBuild script from SBo,
> > rc.postfix is executable (0755) right after the installation.
> > 
> > Shouldn't a more sensible default configuration set
> > /etc/rc.d/rc.postfix to 0644 post-install?
> 
> Fixed on my branch


A better fix, IMHO, would be to use the preserve_perms() function
in doinst.sh to keep whatever permissions are on the existing file
on the installed system (if one is there). Otherwise, it doesn't
matter what perms on rc.postfix, as it's not executed by any other
script on a default system.

-RW

From ryan.q at linux.com  Fri May 15 13:33:50 2015
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Fri, 15 May 2015 13:33:50 +0000
Subject: [Slackbuilds-users] qemu-2.3.0 Venom patch update
In-Reply-To: <55554081.2050000@slackbuilds.org>
References: <55553AAD.6080604@gmail.com> <55553CA2.60505@slackbuilds.org>
 <55553FEE.608@gmail.com> <55554081.2050000@slackbuilds.org>
Message-ID: <CAAcyf-o5AGQGbBzT7Mztt4JCT4WVcoZWbSy3hcB_LoOXVKi2Vw@mail.gmail.com>

 On Thu, May 14, 2015, 5:40 PM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

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

> Ha!  And you thought I didn't look at my Twitter account! ;-o

I just worried that you are too busy and since i got no reply and this
is a critical applications, i applied the patch first, but now it's
under your name :)

 According to one article I read, VirtualBox is also susceptible.


- --
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVVQIEACgkQiHuDdNczM4FIggCffb7xfT59Z4KUSIWLfQEAd2t+
oIYAn0TubIyjh8zzRgCl7ODBnyhfWcUe
=kXUx
-----END PGP SIGNATURE-----
_______________________________________________
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/20150515/905ae031/attachment.html>

From rob0 at slackbuilds.org  Fri May 15 14:00:38 2015
From: rob0 at slackbuilds.org (Rob McGee)
Date: Fri, 15 May 2015 09:00:38 -0500
Subject: [Slackbuilds-users] Permissions on rc.postfix
In-Reply-To: <55558902.6070708@microlinux.fr>
References: <55558902.6070708@microlinux.fr>
Message-ID: <20150515140038.GO23739@harrier.slackbuilds.org>

On Fri, May 15, 2015 at 07:49:54AM +0200, Niki Kovacs wrote:
> When I install Postfix using the SlackBuild script from SBo, 
> rc.postfix is executable (0755) right after the installation.
> 
> Shouldn't a more sensible default configuration set 
> /etc/rc.d/rc.postfix to 0644 post-install?

I wouldn't even use rc.postfix ... rc.sendmail can handle it.

# Start sendmail:
sendmail_start() {
  if [ -x /usr/sbin/sendmail ]; then
    echo "Starting sendmail MTA daemon:  /usr/sbin/sendmail -L sm-mta -bd -q25m"
    /usr/sbin/sendmail -L sm-mta -bd -q25m
    echo "Starting sendmail MSP queue runner:  /usr/sbin/sendmail -L sm-msp-queue -Ac -q25m"
    /usr/sbin/sendmail -L sm-msp-queue -Ac -q25m
  fi
}

The "-bd" in all of that is the only part that is not ignored.
That runs "postfix start".  The second command is entirely no-op.
-- 
    Rob McGee - /dev/rob0 - rob0 at slackbuilds.org

From willysr at slackbuilds.org  Fri May 15 15:32:19 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 15 May 2015 22:32:19 +0700
Subject: [Slackbuilds-users] Permissions on rc.postfix
In-Reply-To: <20150515083323.3fba355c@home.rlworkman.net>
References: <55558902.6070708@microlinux.fr> <5555941A.7070707@slackbuilds.org>
 <20150515083323.3fba355c@home.rlworkman.net>
Message-ID: <55561183.7060706@slackbuilds.org>

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

> A better fix, IMHO, would be to use the preserve_perms() function 
> in doinst.sh to keep whatever permissions are on the existing file 
> on the installed system (if one is there). Otherwise, it doesn't 
> matter what perms on rc.postfix, as it's not executed by any other 
> script on a default system.

Thanks
updated in my branch


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVWEYIACgkQiHuDdNczM4Ek8ACfRc21GlXZf+o+XWe8FLd0Eiet
DwkAnRg72sIYDGpiBRsoSqQmPBdRHlCX
=V3CA
-----END PGP SIGNATURE-----

From yalhcru at gmail.com  Sat May 16 15:18:30 2015
From: yalhcru at gmail.com (B Watson)
Date: Sat, 16 May 2015 11:18:30 -0400
Subject: [Slackbuilds-users] Fwd: mixxx.SlackBuild
In-Reply-To: <CAN1hMuCCN0_dZCs3W-wU9w+25HWf6eFgFks=LpcxV_oDT7er4A@mail.gmail.com>
References: <CAN1hMuCCN0_dZCs3W-wU9w+25HWf6eFgFks=LpcxV_oDT7er4A@mail.gmail.com>
Message-ID: <CAN1hMuD8txCSJd6S3=2kmnnnfFFmvSZSJxQm_jyiVdfzv4=dHg@mail.gmail.com>

Sent this out a while back, never got a response, sending to the list
in case the maintainer's on it.

---------- Forwarded message ----------
From: B Watson <yalhcru at gmail.com>
Date: Sun, 26 Apr 2015 18:43:05 -0400
Subject: mixxx.SlackBuild
To: hellvis69 at gmail.com

On 64-bit Slackware, mixxx installs plugins in /usr/lib/mixxx/plugins,
which should be /usr/lib64/mixxx/plugins...

Also, you've got libshout listed as a required dep in the .info file,
but in the SlackBuild, you've got 'shoutcast=0'. Should probably just
remove libshout from REQUIRES=, since mixxx builds fine on my system
without libshout installed.

You might add an option to build with faad, which gives mixxx the ability
to play AAC audio. Adding 'faad=1' to the scons command enables it,
but it shouldn't be on by default IMO. An option like 'FAAD=yes' in the
environment would be handy.

From matteo.bernardini at gmail.com  Sat May 16 17:33:04 2015
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 16 May 2015 19:33:04 +0200
Subject: [Slackbuilds-users] Fwd: mixxx.SlackBuild
In-Reply-To: <CAN1hMuD8txCSJd6S3=2kmnnnfFFmvSZSJxQm_jyiVdfzv4=dHg@mail.gmail.com>
References: <CAN1hMuCCN0_dZCs3W-wU9w+25HWf6eFgFks=LpcxV_oDT7er4A@mail.gmail.com>
 <CAN1hMuD8txCSJd6S3=2kmnnnfFFmvSZSJxQm_jyiVdfzv4=dHg@mail.gmail.com>
Message-ID: <CAPsDuS4NWmUsBT6zsU9g3n+d07GdL0MQMUTHyTCkWnWDH_M0MQ@mail.gmail.com>

2015-05-16 17:18 GMT+02:00 B Watson <yalhcru at gmail.com>:
> Sent this out a while back, never got a response, sending to the list
> in case the maintainer's on it.

Hi Ben,

as the maintainer is not too responsive (he should maintain this and
kvirc but I found I had to update the latter when broken on SBo) I
have rolled some mods in my personal repo

http://cgit.ponce.cc/slackbuilds/commit/?h=mixxx

I disabled temporarily shoutcast when I updated the script for 1.10.1
(I seem to recall because the old version won't build when we moved
from one slackware version to another) as detection was broken in that
version, but re-enabled in the newer one.
I'm inclined to think that maybe someone should take over
maintainership of this (and kvirc too).

Matteo

From thorsten.johannvorderbrueggen at t-online.de  Sat May 16 18:26:56 2015
From: thorsten.johannvorderbrueggen at t-online.de (thorsten.johannvorderbrueggen at t-online.de)
Date: Sat, 16 May 2015 20:26:56 +0200
Subject: [Slackbuilds-users] update of openmpi
Message-ID: <20150516202656.472ac2e2d2a87c0acb1ba1a7@t-online.de>

Hi at Erik,

there's an update for openmpi available -> 1.8.5 ... works/builds fine on amd64 and armv7 ...

Cheers
  Thorsten


-- 
thorsten.johannvorderbrueggen at t-online.de <thorsten.johannvorderbrueggen at t-online.de>

From yalhcru at gmail.com  Sat May 16 18:47:19 2015
From: yalhcru at gmail.com (B Watson)
Date: Sat, 16 May 2015 14:47:19 -0400
Subject: [Slackbuilds-users] Fwd: mixxx.SlackBuild
In-Reply-To: <CAPsDuS4NWmUsBT6zsU9g3n+d07GdL0MQMUTHyTCkWnWDH_M0MQ@mail.gmail.com>
References: <CAN1hMuCCN0_dZCs3W-wU9w+25HWf6eFgFks=LpcxV_oDT7er4A@mail.gmail.com>
 <CAN1hMuD8txCSJd6S3=2kmnnnfFFmvSZSJxQm_jyiVdfzv4=dHg@mail.gmail.com>
 <CAPsDuS4NWmUsBT6zsU9g3n+d07GdL0MQMUTHyTCkWnWDH_M0MQ@mail.gmail.com>
Message-ID: <CAN1hMuA+ZuM7342sCno-sWGjCUG=5KeXBY6d=BMoZ0xLQzpu0Q@mail.gmail.com>

On 5/16/15, Matteo Bernardini <matteo.bernardini at gmail.com> wrote:

> I'm inclined to think that maybe someone should take over
> maintainership of this (and kvirc too).

I'll take mixxx, unless someone else wants it badly. I use it (or more
accurately, I do tech support for someone who uses it professionally).

kvirc isn't very interesting to me (I use irssi).

From willysr at slackbuilds.org  Sat May 16 20:06:20 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 17 May 2015 03:06:20 +0700
Subject: [Slackbuilds-users] Early notifications: new lensfun
Message-ID: <5557A33C.9060800@slackbuilds.org>

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

Hi maintainers,

i will be submitting new lensfun after the public update so that we
can all test whether this new version breaks other packages.

there are several packages that has a hard dep of lensfun:
graphics/darktable
graphics/digikam
graphics/hugin
graphics/photivo
graphics/rawstudio
graphics/ufraw

please test against lensfun-0.3.1 after the changes has been pushed on
my branch

Thanks

- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVXozwACgkQiHuDdNczM4F9ZQCbBdVPf0I9FqoPa6EExu8RI/Wi
ZsUAn0CHJ1Xg9UWhLGRGKieEnKjglYm8
=7MR9
-----END PGP SIGNATURE-----

From erik at slackbuilds.org  Sun May 17 01:08:20 2015
From: erik at slackbuilds.org (Erik Hanson)
Date: Sat, 16 May 2015 20:08:20 -0500
Subject: [Slackbuilds-users] Scripts up for grabs
Message-ID: <20150516200820.68be24f5@shaggy.doo>


These are some scripts of mine that currently have outdated VERSIONs. They
can't be updated by simple version bumping, due to missing sources, build
errors, etc. I don't use them and don't really have the time to deal with
them. If anyone wants to take over feel free. They'll almost certainly be
dropped with the next repo version bump if no one wants them.

tmw
tmwmusic
egoboo
frozen-bubble
liblqr
gimp-lqr-plugin
allegro
guichan
physfs
openmpi
multitail
md5deep
lbzip2
pidgin-facebookchat
pidgin-privacy-please
umplayer
huludesktop


-- 
Erik Hanson
-------------- 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/20150516/9e8a06ec/attachment.asc>

From willysr at slackbuilds.org  Sun May 17 01:22:37 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 17 May 2015 08:22:37 +0700
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <20150516200820.68be24f5@shaggy.doo>
References: <20150516200820.68be24f5@shaggy.doo>
Message-ID: <5557ED5D.6080403@slackbuilds.org>

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

> liblqr multitail

I will take this two

- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVX7V0ACgkQiHuDdNczM4HHSgCfS83k7T0y4+6RW249xJdRSlZu
WIkAnjaG6UePS1yKGj4xFKBS4U8p+qHk
=jzEz
-----END PGP SIGNATURE-----

From ryan.q at linux.com  Sun May 17 01:25:27 2015
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Sun, 17 May 2015 01:25:27 +0000
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <5557ED5D.6080403@slackbuilds.org>
References: <20150516200820.68be24f5@shaggy.doo>
 <5557ED5D.6080403@slackbuilds.org>
Message-ID: <CAAcyf-oMaRYpY8qxmOLekcuTBa0Jx2LeccUNydGQn0L1jC_c8Q@mail.gmail.com>

On Sat, May 16, 2015 at 6:22 PM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> > liblqr multitail
>
> I will take this two
>
> i will take: allegro

> - --
> Willy Sudiarto Raharjo
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iEYEAREIAAYFAlVX7V0ACgkQiHuDdNczM4HHSgCfS83k7T0y4+6RW249xJdRSlZu
> WIkAnjaG6UePS1yKGj4xFKBS4U8p+qHk
> =jzEz
> -----END PGP SIGNATURE-----
> _______________________________________________
> 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/20150517/2bd0be47/attachment.html>

From andrew.david.strong at gmail.com  Sun May 17 01:30:10 2015
From: andrew.david.strong at gmail.com (andrew)
Date: Sun, 17 May 2015 11:30:10 +1000
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <20150516200820.68be24f5@shaggy.doo>
References: <20150516200820.68be24f5@shaggy.doo>
Message-ID: <20150517013010.GA28076@ilium.andrews-corner.org>

I can maintain PhysFS which is a requirement for compiling d2x-rebirth
and d1x-rebirth which I maintain for SBo.

Andrew Strong

On Sat, May 16, 2015 at 08:08:20PM -0500, Erik Hanson wrote:
> 
> These are some scripts of mine that currently have outdated VERSIONs. They
> can't be updated by simple version bumping, due to missing sources, build
> errors, etc. I don't use them and don't really have the time to deal with
> them. If anyone wants to take over feel free. They'll almost certainly be
> dropped with the next repo version bump if no one wants them.
>
> [...]
> physfs
> [...] 

-- 
You think that's air you're breathing now?

From emmanueln at gmail.com  Sun May 17 01:51:36 2015
From: emmanueln at gmail.com (Emmanuel)
Date: Sat, 16 May 2015 22:51:36 -0300
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <20150516200820.68be24f5@shaggy.doo>
References: <20150516200820.68be24f5@shaggy.doo>
Message-ID: <CAFhPZZf4dCGaTL_7tTdrXi88oWXZ-0rHq8fGnqZmxb_T_oFxJw@mail.gmail.com>

On Sat, May 16, 2015 at 10:08 PM, Erik Hanson <erik at slackbuilds.org> wrote:

>
> These are some scripts of mine that currently have outdated VERSIONs. They
> can't be updated by simple version bumping, due to missing sources, build
> errors, etc. I don't use them and don't really have the time to deal with
> them. If anyone wants to take over feel free. They'll almost certainly be
> dropped with the next repo version bump if no one wants them.
>
> tmw
> tmwmusic
> egoboo
> frozen-bubble
> liblqr
> gimp-lqr-plugin
> allegro
> guichan
> physfs
> openmpi
> multitail
> md5deep
> lbzip2
> pidgin-facebookchat
> pidgin-privacy-please
> umplayer
> huludesktop
>
>
> --
> Erik Hanson
>
>
Hi,

I know that I'm new to the list, but if nobody wants to take Openmpi, I
will like to volunteer to take it over.
I use it every day in a couple of Slackware workstations and in a small
Slackware HPC cluster.

Regards.


> _______________________________________________
> 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/
>
>
>


-- 
*****************
   Emmanuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150516/746ffe02/attachment.html>

From klaatu at straightedgelinux.com  Sun May 17 02:09:16 2015
From: klaatu at straightedgelinux.com (Klaatu)
Date: Sun, 17 May 2015 14:09:16 +1200
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <CAFhPZZf4dCGaTL_7tTdrXi88oWXZ-0rHq8fGnqZmxb_T_oFxJw@mail.gmail.com>
References: <20150516200820.68be24f5@shaggy.doo>
 <CAFhPZZf4dCGaTL_7tTdrXi88oWXZ-0rHq8fGnqZmxb_T_oFxJw@mail.gmail.com>
Message-ID: <5557F84C.2010401@straightedgelinux.com>

On 05/17/2015 01:51 PM, Emmanuel wrote:
> On Sat, May 16, 2015 at 10:08 PM, Erik Hanson <erik at slackbuilds.org> wrote:
> 
>>
>> These are some scripts of mine that currently have outdated VERSIONs. They
>> can't be updated by simple version bumping, due to missing sources, build
>> errors, etc. I don't use them and don't really have the time to deal with
>> them. If anyone wants to take over feel free. They'll almost certainly be
>> dropped with the next repo version bump if no one wants them.
>>
>> tmw
>> tmwmusic
>> egoboo
>> frozen-bubble
>> liblqr
>> gimp-lqr-plugin
>> allegro
>> guichan
>> physfs
>> openmpi
>> multitail
>> md5deep
>> lbzip2
>> pidgin-facebookchat
>> pidgin-privacy-please
>> umplayer
>> huludesktop
>>
>>
>> --
>> Erik Hanson
>>
>>
> Hi,
> 
> I know that I'm new to the list, but if nobody wants to take Openmpi, I
> will like to volunteer to take it over.
> I use it every day in a couple of Slackware workstations and in a small
> Slackware HPC cluster.
> 
> Regards.
> 
> 
>> _______________________________________________
>> 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/
> 

I will take:

guichan
gimp-lqr-plugin

-klaatu

From willysr at slackbuilds.org  Sun May 17 03:10:18 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 17 May 2015 10:10:18 +0700
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <20150516200820.68be24f5@shaggy.doo>
References: <20150516200820.68be24f5@shaggy.doo>
Message-ID: <5558069A.7040806@slackbuilds.org>

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

> md5deep

Let me take this as well


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVYBpoACgkQiHuDdNczM4GbYQCfR/XvP2Yl7PU4COlGa7bSHjXe
+BwAnR2ClKVkzYESMVOVexns7Q5ZYAJ8
=/oOY
-----END PGP SIGNATURE-----

From erik at slackbuilds.org  Sun May 17 03:11:58 2015
From: erik at slackbuilds.org (Erik Hanson)
Date: Sat, 16 May 2015 22:11:58 -0500
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <5557ED5D.6080403@slackbuilds.org>
References: <20150516200820.68be24f5@shaggy.doo>
 <5557ED5D.6080403@slackbuilds.org>
Message-ID: <20150516221158.39278bbe@shaggy.doo>

On Sun, 17 May 2015 08:22:37 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> > liblqr

gimp-lqr-plugin should probably go with this, I don't think anything else
uses it.


-- 
Erik Hanson
-------------- 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/20150516/137fbcc7/attachment.asc>

From willysr at slackbuilds.org  Sun May 17 03:33:53 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 17 May 2015 10:33:53 +0700
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <20150516221158.39278bbe@shaggy.doo>
References: <20150516200820.68be24f5@shaggy.doo>
 <5557ED5D.6080403@slackbuilds.org> <20150516221158.39278bbe@shaggy.doo>
Message-ID: <55580C21.4050600@slackbuilds.org>

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

>>> liblqr
> 
> gimp-lqr-plugin should probably go with this, I don't think
> anything else uses it.

Klaatu has step up to maintain gimp-lqr-plugin and i'm ok with that.
I will maintain liblqr since it's also a dependency for my digiKam
package.


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVYDCEACgkQiHuDdNczM4H6eACgmLUX8xtUzGabwQDhtRgBClh4
2D4AmgN31IRqLtAbxGKozTgjE+1zh9Hh
=Uug9
-----END PGP SIGNATURE-----

From klaatu at straightedgelinux.com  Sun May 17 03:36:48 2015
From: klaatu at straightedgelinux.com (Klaatu)
Date: Sun, 17 May 2015 15:36:48 +1200
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <55580C21.4050600@slackbuilds.org>
References: <20150516200820.68be24f5@shaggy.doo>
 <5557ED5D.6080403@slackbuilds.org> <20150516221158.39278bbe@shaggy.doo>
 <55580C21.4050600@slackbuilds.org>
Message-ID: <55580CD0.4060905@straightedgelinux.com>

On 05/17/2015 03:33 PM, Willy Sudiarto Raharjo wrote:
>>>> liblqr
> 
>> gimp-lqr-plugin should probably go with this, I don't think
>> anything else uses it.
> 
> Klaatu has step up to maintain gimp-lqr-plugin and i'm ok with that.
> I will maintain liblqr since it's also a dependency for my digiKam
> package.
> 
> 
> _______________________________________________
> 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/
> 
> 
> 

Yep, sounds good to me.

-klaatu

From pprkut at liwjatan.at  Sun May 17 09:47:57 2015
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Sun, 17 May 2015 11:47:57 +0200
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <20150516200820.68be24f5@shaggy.doo>
References: <20150516200820.68be24f5@shaggy.doo>
Message-ID: <2223710.3ltZzRldDf@titania>

On Saturday 16 May 2015 20:08:20 Erik Hanson wrote:
> These are some scripts of mine that currently have outdated VERSIONs. They
> can't be updated by simple version bumping, due to missing sources, build
> errors, etc. I don't use them and don't really have the time to deal with
> them. If anyone wants to take over feel free. They'll almost certainly be
> dropped with the next repo version bump if no one wants them.
> 
> frozen-bubble

I'll take that one.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150517/4ada5f3b/attachment.asc>

From willysr at slackbuilds.org  Sun May 17 17:16:08 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 18 May 2015 00:16:08 +0700
Subject: [Slackbuilds-users] Updates - 20150517.1
Message-ID: <5558CCD8.30907@slackbuilds.org>

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

Sun May 17 16:48:27 UTC 2015
academic/scilab: Updated for version 5.5.2.
academic/veusz: Updated for version 1.23.
academic/xiphos: Fix typo.
accessibility/flite: Updated for version 2.0.0, added docs.
audio/caps: Updated for version 0.9.24.
audio/clyrics: Added (An extensible lyrics fetcher).
audio/ecasound: Updated for version 2.9.1.
audio/google-musicmanager: Updated for version 1.0.182.3607.
audio/guitarix: Updated for version 0.32.3.
audio/pasystray: Updated for version 0.5.2.
audio/pavucontrol: Updated for version 3.0.
audio/pulseaudio: Updated for version 6.0.
audio/sooperlooper: Updated for version 1.7.3.
audio/speex: Patch to reinstate a missing header.
audio/transcribe: Updated for version 8.40.
audio/xmp: Updated for version 4.0.10.
desktop/alarm: Updated for version 2.0.
desktop/fbrowse-tray: Added (A simple file-browser).
desktop/j4-dmenu-desktop: Updated for version 2.12.
desktop/menutray: Added (A simple GTK+ application menu tray).
desktop/obbrowser: Added (simple script).
desktop/obmenu-generator: Added (A fast pipe/static menu generator).
desktop/py3status: Updated for version 2.4.
desktop/sun: Updated for version 1.0.9.
desktop/trayer-srg: Updated for version 20150512.
desktop/xfce4-fsguard-plugin: Updated for version 1.0.2.
desktop/xtrascreenhacks: Updated for version 0.7.
desktop/xvkbd: Updated for vesion 3.6.
desktop/zenity: Updated for version 3.16.2.
development/bas55: Added (Minimal BASIC System).
development/bashdb: Updated for vesion 4.3-0.91.
development/codelite: Updated for version 8.0.
development/gambas3: Updated for version 3.7.1.
development/gnome-common: Updated for version 3.14.0.
development/gob2: Updated for vesion 2.0.20.
development/highlight: Updated for version 3.22.
development/kaaedit: Updated for version 0.43.0.
development/mosml: Update README.
development/ne: Updated for version 2.6.
development/pandas: Updated for version 0.16.1.
development/regina-rexx: Update script.
development/rust: Updated for version 1.0.0.
development/xtruss: Updated for version 20150103.8828e85.
games/bitfighter: Updated for version 019e.
games/cowsay: Fix DOWNLOAD url.
games/doomseeker: Updated for version 1.0.
games/eduke32: Updated for version 20150510_5182.
games/liquidwar6: Updated for version 0.6.3902.
games/mrrescue: Updated for version 1.02c.
games/oblige: Updated for version 6.20.
games/openclonk: Updated for version 6.0.
games/stratagus: Updated for version 2.3.0.
games/teeworlds: Updated for version 0.6.3.
games/torcs: Updated for version 1.3.6.
games/trigger-rally: Added (Free OpenGL rally car racing game).
games/tty-solitaire: Updated for version 0.2.0.
games/wargus: Updated for version 2.3.0.
gis/qgis: Updated for version 2.8.2.
git/gitignore: Add RPM in gitignore.
graphics/digikam: Updated for version 4.10.0.
graphics/djview4: Updated for version 4.10.
graphics/yed: Updated for version 3.14.2.
ham/direwolf: Updated for version 1.1.
ham/fldigi: Updated for version 3.22.08.
ham/klog: Updated for version 0.9.1.1.
ham/tqsl: Updated for version 2.0.3.
ham/unixcw: Updated for version 3.4.1.
ham/xdemorse: Updated for version 2.9.
ham/xfhell: Updated for version 3.2.
ham/xgridloc: Updated for version 1.7.
ham/xnec2c: Updated for version 3.3.
ham/xpsk31: Updated for version 3.2.
ham/xwxapt: Updated for version 2.4.
libraries/GitPython: Updated for version 1.0.1.
libraries/SFML: Updated for version 2.3.
libraries/basemap: Added (matplotlib library).
libraries/botocore: Updated for version 0.108.0.
libraries/cffi: Updated for version 0.9.2.
libraries/discogs-client: Updated for version 2.1.0.
libraries/futures: Updated for version 3.0.2.
libraries/girara: Updated for version 0.2.4.
libraries/libclaw: Added (C++ Library).
libraries/libcue: Updated for version 1.4.0.
libraries/libdsk: Fix HOMEPAGE.
libraries/liblqr: Updated for version 0.4.2 + new maintainer.
libraries/libofx: Updated for version 0.9.9.
libraries/libpst: Updated for version 0.6.64.
libraries/libsodium: Updated for version 1.0.3.
libraries/libxmp: Updated for verion 4.3.8.
libraries/live555: Updated for version 2015.05.12.
libraries/pycparser: Updated for version 2.13.
libraries/python-librtmp: Updated for version 0.2.2.
libraries/sparsehash: Added (hash_map implementation).
libraries/yaml-cpp: Updated for version 0.5.2.
misc/clawsker: Updated for version 0.7.12.
misc/xca: Updated for version 1.2.0.
multimedia/smtube: Updated for version 15.5.10.
multimedia/spotify32: Fix DOWNLOAD.
multimedia/spotify64: Updated for version 0.9.17.8.gd06432d.31.
multimedia/youtube-viewer: Updated for version 3.1.4.
network/Flootty: Updated for version 3.1.3.
network/awscli: Updated for version 1.7.27.
network/deis: Updated for version 1.6.1.
network/flexget: Updated for version 1.2.308.
network/hiawatha: Updated for version 9.13.
network/irssi_otr: Updated for version 1.0.0.
network/midori: Updated for version 0.5.10.
network/openvswitch: Update scripts.
network/owncloud-server: Updated for version 8.0.3.
network/postfix: Fix permission.
network/qTox: Updated for version 20150516.
network/remmina: Fix temporary install location of libssh.
network/spice-gtk: Updated for version 0.28.
network/sshuttle: Provide alternative source name.
network/suricata: Updated for version 2.0.8.
network/teamviewer: Updated for version 10.0.41499.
network/toxcore: Updated for version 20150515.
network/vcspull: Updated for version 0.1.1.
network/vivaldi: Updated for version 1.0.174.8_1.
network/youtube-dl-server: Updated for version 0.2.
network/youtube-dl: Updated for version 2015.05.10.
office/homebank: Updated for vesion 5.0.2.
office/kchmviewer-qt: Updated for version 7.3.
office/mupdf: Updated for version 1.7a.
office/pyspread: Updated for version 0.4.1.
office/xtrkcad: Updated for version 4.2.0.
office/zathura-cb: Fixed HOMEPAGE.
office/zathura-djvu: Updated for version 0.2.4.
office/zathura-pdf-mupdf: Updated for version 0.2.7.
office/zathura-ps: Fixed HOMEPAGE.
office/zathura: Updated for version 0.3.3.
perl/perl-Module-Build: Updated for version 0.4212.
perl/perl-file-basedir: Update DEPS.
perl/perl-inc-latest: Added (bootstrap helper module).
perl/perl-lwp-useragent-cached: Added (UserAgent caching mechanism).
python/dulwich: Updated for version 0.10.0.
python/hg-git: Updated for version 0.8.1.
python/hgsubversion: Updated for version 1.8.1.
python/pluggy: Added (mechanisms for python).
python/prompt_toolkit: Updated for version 0.37.
python/pysetuptools: Updated for version 15.2.
python/python-requests: Updated for version 2.7.0.
python/stem: Updated for version 1.4.0.
python/tox: Updated for version 2.0.1.
ruby/heroku-client: Updated for version 3.36.17.
system/AnonymousPro: Added Anonymous Pro minus fonts.
system/Attic: Updated for version 0.16.
system/alien: Added (converting program).
system/brasero: Updated for version 3.12.1.
system/fslint: Updated for vesion 2.44.
system/gparted: Updated for version 0.22.0.
system/gsmartcontrol: Updated for version 0.8.7.
system/hwloc: Updated for version 1.10.1.
system/isomaster: Updated for version 1.3.13.
system/man-pages-ja: Updated for version 20150415.
system/md5deep: Updated for version 4.4 + new maintainer.
system/multitail: Updated for version 6.4.1 + new maintainer.
system/ncdu: Updated for version 1.11.
system/pax: Fix DOWNLOAD url.
system/pbzip2: Updated for version 1.1.12.
system/qemu: Added patch to fix VENOM vulnerability.
system/roxterm: Updated for version 2.9.7.
system/rtirq: Updated for version 20150216.
system/slpkg: Updated for version 2.3.1.
system/tmuxp: Updated for version 0.8.1.
system/trmaid: Updated for version 0.5.2.
system/xbindkeys: Updated for version 1.8.6.
system/xfsudo: Updated for version 0.6.1.
system/xjobs: Updated for version 20140125.
+--------------------------+



- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVYzNgACgkQiHuDdNczM4GzlwCaAuug6TPFnLX/R4jdnyiXALZ4
OVwAnjaIseQ4u41ziRzkmYZB66R2BzKx
=gy6C
-----END PGP SIGNATURE-----

From Jim.Diamond at acadiau.ca  Sun May 17 22:25:12 2015
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Sun, 17 May 2015 19:25:12 -0300
Subject: [Slackbuilds-users] Updates - 20150517.1
In-Reply-To: <5558CCD8.30907@slackbuilds.org>
References: <5558CCD8.30907@slackbuilds.org>
Message-ID: <20150517222512.GA6172@jdiamond-nb2>

On Mon, May 18, 2015 at 00:16 (+0700), Willy Sudiarto Raharjo wrote:

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

> office/zathura-cb: Fixed HOMEPAGE.
> office/zathura-djvu: Updated for version 0.2.4.
> office/zathura-pdf-mupdf: Updated for version 0.2.7.
> office/zathura-ps: Fixed HOMEPAGE.
> office/zathura: Updated for version 0.3.3.
> +--------------------------+

# sbocheck
Updating SlackBuilds tree...
Finished.
Checking for updated SlackBuilds...

adobe-source-sans-pro-font-2.010ro1.065it  <  needs updating (SBo has 2.10roman1.065italic)
pulseaudio-5.0  <  needs updating (SBo has 6.0)
zathura-0.2.7   <  needs updating (SBo has 0.3.3)

A copy of the above result is kept in /var/log/sbocheck.log

sbocheck  5.24s user 0.34s system 44% cup 12.412 total
# sboupgrade zathura

zathura is a highly customizable and functional PDF viewer based on the
poppler rendering library and the gtk+ toolkit. The idea behind zathura
is an application that provides a minimalistic and space saving interface
as well as an easy usage that mainly focuses on keyboard interaction.

This build includes the zathura core and the zathura-pdf-poppler plugin.

Other plugins exist to support other file types:

zathura-pdf-mupdf - Alternate PDF renderer (faster, maybe more accurate)
zathura-ps - PostScript
zathura-cb - Comic book archives (cbz/cbr/cb7/cbt)
zathura-djvu - DjVu

When upgrading zathura, you must rebuild all its plugins
against the new version of zathura, even if the version numbers
are the same.

Proceed with zathura? [y]:
zathura added to upgrade queue.

Upgrade queue: zathura

Are you sure you wish to continue? [y]:
--2015-05-17 19:21:16--  http://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz
Resolving www.pwmt.org (www.pwmt.org)... 95.129.55.168
Connecting to www.pwmt.org (www.pwmt.org)|95.129.55.168|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location:
https://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz [following]
--2015-05-17 19:21:17--  https://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz
Connecting to www.pwmt.org (www.pwmt.org)|95.129.55.168|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 203604 (199K) [application/x-tar]
Saving zathura-0.3.3.tar.gzto:

100%[======================================>] 203,604      214KB/s
in 0.9s

2015-05-17 19:21:18 (214 KB/zathura-0.3.3.tar. saved [203604/203604]gzs) -

Unable to download/verify source file(s) for zathura:
  md5sum failure for /usr/sob/distfiles/zathura-0.3.3.tar.gz.

  Do you want to proceed? [n]
  Failures:
    zathura: md5sum failure for /usr/sob/distfiles/zathura-0.3.3.tar.gz.
 sboupgrade zathura  5.31s user 0.13s system 34% cup 15.987 total



Cheers.  (And thanks for all the updates.)

                                Jim

From yalhcru at gmail.com  Sun May 17 23:03:03 2015
From: yalhcru at gmail.com (B Watson)
Date: Sun, 17 May 2015 19:03:03 -0400
Subject: [Slackbuilds-users] Updates - 20150517.1
In-Reply-To: <20150517222512.GA6172@jdiamond-nb2>
References: <5558CCD8.30907@slackbuilds.org>
 <20150517222512.GA6172@jdiamond-nb2>
Message-ID: <CAN1hMuDNXeNTk043VocpyD5P9jskv7DKt8-L=rO=p6fP=b1CkA@mail.gmail.com>

On 5/17/15, Jim Diamond <Jim.Diamond at acadiau.ca> wrote:
> Are you sure you wish to continue? [y]:
> --2015-05-17 19:21:16--
> http://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz
> Resolving www.pwmt.org (www.pwmt.org)... 95.129.55.168
> Connecting to www.pwmt.org (www.pwmt.org)|95.129.55.168|:80... connected.
> HTTP request sent, awaiting response... 301 Moved Permanently
> Location:
> https://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz
> [following]
> --2015-05-17 19:21:17--
> https://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz
> Connecting to www.pwmt.org (www.pwmt.org)|95.129.55.168|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 203604 (199K) [application/x-tar]
> Saving zathura-0.3.3.tar.gzto:
>
> 100%[======================================>] 203,604      214KB/s
> in 0.9s
>
> 2015-05-17 19:21:18 (214 KB/zathura-0.3.3.tar. saved [203604/203604]gzs) -
>
> Unable to download/verify source file(s) for zathura:
>   md5sum failure for /usr/sob/distfiles/zathura-0.3.3.tar.gz.

Hmm. Hard to see exactly what's going on, your output has somehow gotten
interleaved. Checked it here:

$ wget http://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz
--2015-05-17 18:57:31--
http://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz
Resolving www.pwmt.org (www.pwmt.org)... 95.129.55.168
Connecting to www.pwmt.org (www.pwmt.org)|95.129.55.168|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz
[following]
--2015-05-17 18:57:31--
https://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz
Connecting to www.pwmt.org (www.pwmt.org)|95.129.55.168|:443... connected.
WARNING: cannot verify www.pwmt.org's certificate, issued by
???/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate
Signing/CN=StartCom Class 2 Primary Intermediate Server CA???:
  Self-signed certificate encountered.
HTTP request sent, awaiting response... 200 OK
Length: 203604 (199K) [application/x-tar]
Saving to: ???zathura-0.3.3.tar.gz???

100%[==============================================>] 203,604
421KB/s   in 0.5s

2015-05-17 18:57:33 (421 KB/s) - ???zathura-0.3.3.tar.gz??? saved
[203604/203604]

$ md5sum zathura-0.3.3.tar.gz
d360252210ce51a29e8d341b1b72a7cc  zathura-0.3.3.tar.gz
$ cat *info
PRGNAM="zathura"
VERSION="0.3.3"
HOMEPAGE="http://www.pwmt.org/projects/zathura"
DOWNLOAD="http://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz \
          http://www.pwmt.org/projects/zathura-pdf-poppler/download/zathura-pdf-poppler-0.2.5.tar.gz"
MD5SUM="53124af80e974283a6678319a62e6666 \
        d360252210ce51a29e8d341b1b72a7cc"
DOWNLOAD_x86_64=""
MD5SUM_x86_64=""
REQUIRES="girara"
MAINTAINER="B. Watson"
EMAIL="yalhcru at gmail.com"

However, there *is* an md5sum failure for the other file,
zathura-pdf-poppler-0.2.5.tar.gz (my fault, failed to update it in the
.info file). Will fix.

From yalhcru at gmail.com  Sun May 17 23:08:48 2015
From: yalhcru at gmail.com (B Watson)
Date: Sun, 17 May 2015 19:08:48 -0400
Subject: [Slackbuilds-users] Updates - 20150517.1
In-Reply-To: <CAN1hMuDNXeNTk043VocpyD5P9jskv7DKt8-L=rO=p6fP=b1CkA@mail.gmail.com>
References: <5558CCD8.30907@slackbuilds.org>
 <20150517222512.GA6172@jdiamond-nb2>
 <CAN1hMuDNXeNTk043VocpyD5P9jskv7DKt8-L=rO=p6fP=b1CkA@mail.gmail.com>
Message-ID: <CAN1hMuB=Er2Pg593DsJbszZrbG7E_t9uyQ_iTupN99NZmfBz1g@mail.gmail.com>

On 5/17/15, B Watson <yalhcru at gmail.com> wrote:
> However, there *is* an md5sum failure for the other file,
> zathura-pdf-poppler-0.2.5.tar.gz (my fault, failed to update it in the
> .info file). Will fix.

I spoke too soon. Somehow the md5sum in the .info file isn't what I put
in there. Will investigate.

From yalhcru at gmail.com  Sun May 17 23:14:24 2015
From: yalhcru at gmail.com (B Watson)
Date: Sun, 17 May 2015 19:14:24 -0400
Subject: [Slackbuilds-users] Updates - 20150517.1
In-Reply-To: <CAN1hMuB=Er2Pg593DsJbszZrbG7E_t9uyQ_iTupN99NZmfBz1g@mail.gmail.com>
References: <5558CCD8.30907@slackbuilds.org>
 <20150517222512.GA6172@jdiamond-nb2>
 <CAN1hMuDNXeNTk043VocpyD5P9jskv7DKt8-L=rO=p6fP=b1CkA@mail.gmail.com>
 <CAN1hMuB=Er2Pg593DsJbszZrbG7E_t9uyQ_iTupN99NZmfBz1g@mail.gmail.com>
Message-ID: <CAN1hMuCcJ_NBY-bDoH4Zu=7x9gmdHJKco=6AgTpQL8bXZF3Jbw@mail.gmail.com>

On 5/17/15, B Watson <yalhcru at gmail.com> wrote:
> On 5/17/15, B Watson <yalhcru at gmail.com> wrote:
>> However, there *is* an md5sum failure for the other file,
>> zathura-pdf-poppler-0.2.5.tar.gz (my fault, failed to update it in the
>> .info file). Will fix.
>
> I spoke too soon. Somehow the md5sum in the .info file isn't what I put
> in there. Will investigate.

OK, fixed in my branch. Also attached the fixed zathura.info to this email,
thanks for bringing to my attention.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zathura.info.gz
Type: application/x-gzip
Size: 290 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150517/11aa34d1/attachment.bin>

From ryan.q at linux.com  Sun May 17 23:50:32 2015
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Sun, 17 May 2015 23:50:32 +0000
Subject: [Slackbuilds-users] Fwd: uwm download url
In-Reply-To: <CAMt7G9Sz1ok0XC4nsVhz-JY9d6o_gPhKSMd32Aapkm4zyPZ4MQ@mail.gmail.com>
References: <CAMt7G9Sz1ok0XC4nsVhz-JY9d6o_gPhKSMd32Aapkm4zyPZ4MQ@mail.gmail.com>
Message-ID: <CAAcyf-qkQQMtcKCpXuQLtP13MSufS+kR8owWnbQrZvAgYDHpqQ@mail.gmail.com>

It appears that when this URL was 'fixed', the link did not use the proper
HTML code for a space:

http://slackbuilds.org/cgit/slackbuilds/commit/?id=c31197f3a891abeb8b89a9508b659a585245d7fc



I don't mind people fixing links on things I maintain, but we probably
should make it correct.  ;^)

Ryan


---------- Forwarded message ---------
From: David Spencer <baildon.research at googlemail.com>
Date: Sun, May 17, 2015, 4:33 PM
Subject: uwm download url
To: Ryan P.C. McQuen <ryan.q at linux.com>

Hi Ryan,

Just a quick hint -- in the .info file for uwm, the DOWNLOAD url
contains a space that needs to be encoded as %20, otherwise all the
build tools will think it's two downloads.

All the best
-D.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150517/3f30e706/attachment.html>

From larryhaja at gmail.com  Mon May 18 00:13:56 2015
From: larryhaja at gmail.com (Larry Hajali)
Date: Sun, 17 May 2015 17:13:56 -0700
Subject: [Slackbuilds-users] Updates - 20150517.1
In-Reply-To: <CAN1hMuCcJ_NBY-bDoH4Zu=7x9gmdHJKco=6AgTpQL8bXZF3Jbw@mail.gmail.com>
References: <5558CCD8.30907@slackbuilds.org>
 <20150517222512.GA6172@jdiamond-nb2>
 <CAN1hMuDNXeNTk043VocpyD5P9jskv7DKt8-L=rO=p6fP=b1CkA@mail.gmail.com>
 <CAN1hMuB=Er2Pg593DsJbszZrbG7E_t9uyQ_iTupN99NZmfBz1g@mail.gmail.com>
 <CAN1hMuCcJ_NBY-bDoH4Zu=7x9gmdHJKco=6AgTpQL8bXZF3Jbw@mail.gmail.com>
Message-ID: <CAAZPBMh7j-6gAYiGQHzDYOfZhdEHwUfZ97CNZE=aJT=k8AN8-w@mail.gmail.com>

SFML doesn't have an md5sum value, instead it has a url.

>From sbopkg:
Found SFML-2.3-sources.zip in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for SFML-2.3-sources.zip ... FAILED!
    Expected: https://sourceforge.net/projects/slpkg
    Found:    abc06b4cdef6531143ac0221cd1b184a

Md5sum should be updated to 'abc06b4cdef6531143ac0221cd1b184a'.

Thanks,
--Larry

On Sun, May 17, 2015 at 4:14 PM, B Watson <yalhcru at gmail.com> wrote:

> On 5/17/15, B Watson <yalhcru at gmail.com> wrote:
> > On 5/17/15, B Watson <yalhcru at gmail.com> wrote:
> >> However, there *is* an md5sum failure for the other file,
> >> zathura-pdf-poppler-0.2.5.tar.gz (my fault, failed to update it in the
> >> .info file). Will fix.
> >
> > I spoke too soon. Somehow the md5sum in the .info file isn't what I put
> > in there. Will investigate.
>
> OK, fixed in my branch. Also attached the fixed zathura.info to this
> email,
> thanks for bringing to my attention.
>
> _______________________________________________
> 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/20150517/bd48e708/attachment.html>

From willysr at slackbuilds.org  Mon May 18 00:32:06 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 18 May 2015 07:32:06 +0700
Subject: [Slackbuilds-users] Fwd: uwm download url
In-Reply-To: <CAAcyf-qkQQMtcKCpXuQLtP13MSufS+kR8owWnbQrZvAgYDHpqQ@mail.gmail.com>
References: <CAMt7G9Sz1ok0XC4nsVhz-JY9d6o_gPhKSMd32Aapkm4zyPZ4MQ@mail.gmail.com>
 <CAAcyf-qkQQMtcKCpXuQLtP13MSufS+kR8owWnbQrZvAgYDHpqQ@mail.gmail.com>
Message-ID: <55593306.7000007@slackbuilds.org>

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

> It appears that when this URL was 'fixed', the link did not use the
> proper HTML code for a space:
> 
> http://slackbuilds.org/cgit/slackbuilds/commit/?id=c31197f3a891abeb8b8
9a9508b659a585245d7fc
>
> 
> 
> 
> I don't mind people fixing links on things I maintain, but we
> probably should make it correct.  ;^)

i tested in browser and wget "URL" and both works


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVZMwYACgkQiHuDdNczM4GKdQCgpJiFwrLwzf9crVZiRXuW4zo8
jN8An3SXmwYYfs8P3XXLaZrqLMlg6gie
=iIXJ
-----END PGP SIGNATURE-----

From willysr at slackbuilds.org  Mon May 18 00:35:11 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 18 May 2015 07:35:11 +0700
Subject: [Slackbuilds-users] Updates - 20150517.1
In-Reply-To: <CAAZPBMh7j-6gAYiGQHzDYOfZhdEHwUfZ97CNZE=aJT=k8AN8-w@mail.gmail.com>
References: <5558CCD8.30907@slackbuilds.org>
 <20150517222512.GA6172@jdiamond-nb2>
 <CAN1hMuDNXeNTk043VocpyD5P9jskv7DKt8-L=rO=p6fP=b1CkA@mail.gmail.com>
 <CAN1hMuB=Er2Pg593DsJbszZrbG7E_t9uyQ_iTupN99NZmfBz1g@mail.gmail.com>
 <CAN1hMuCcJ_NBY-bDoH4Zu=7x9gmdHJKco=6AgTpQL8bXZF3Jbw@mail.gmail.com>
 <CAAZPBMh7j-6gAYiGQHzDYOfZhdEHwUfZ97CNZE=aJT=k8AN8-w@mail.gmail.com>
Message-ID: <555933BF.8060405@slackbuilds.org>

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

> SFML doesn't have an md5sum value, instead it has a url.
> 
> From sbopkg: Found SFML-2.3-sources.zip in /var/cache/sbopkg. 
> Checking MD5SUM: MD5SUM check for SFML-2.3-sources.zip ... FAILED! 
> Expected: https://sourceforge.net/projects/slpkg Found:
> abc06b4cdef6531143ac0221cd1b184a
> 
> Md5sum should be updated to 'abc06b4cdef6531143ac0221cd1b184a'.

Sorry about that
will pay more attention to the maintainer's update next time
anyway, it has been fixed on my branch already

- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVZM78ACgkQiHuDdNczM4HjYwCeOyttbmd2rdinEIh6H8VoJF4z
YA8AnAkt5CgLxHVlqdm4/JDILQi1Iy2x
=aHiS
-----END PGP SIGNATURE-----

From willysr at slackbuilds.org  Mon May 18 01:08:33 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 18 May 2015 08:08:33 +0700
Subject: [Slackbuilds-users] Updates - 20150517.1
In-Reply-To: <CAN1hMuCcJ_NBY-bDoH4Zu=7x9gmdHJKco=6AgTpQL8bXZF3Jbw@mail.gmail.com>
References: <5558CCD8.30907@slackbuilds.org>
 <20150517222512.GA6172@jdiamond-nb2>
 <CAN1hMuDNXeNTk043VocpyD5P9jskv7DKt8-L=rO=p6fP=b1CkA@mail.gmail.com>
 <CAN1hMuB=Er2Pg593DsJbszZrbG7E_t9uyQ_iTupN99NZmfBz1g@mail.gmail.com>
 <CAN1hMuCcJ_NBY-bDoH4Zu=7x9gmdHJKco=6AgTpQL8bXZF3Jbw@mail.gmail.com>
Message-ID: <55593B91.5080909@slackbuilds.org>

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

> OK, fixed in my branch. Also attached the fixed zathura.info to
> this email, thanks for bringing to my attention.

perhaps you forgot to push your branch?
because i haven't seen it in cgit interface :)

- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVZO5EACgkQiHuDdNczM4He8wCfWuwrW2YtUl4i8VEdl0FETzE/
epcAn2qLG6CSMeZ2YaSUL2ty31evCS1t
=89+o
-----END PGP SIGNATURE-----

From ryan.q at linux.com  Mon May 18 01:35:43 2015
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Mon, 18 May 2015 01:35:43 +0000
Subject: [Slackbuilds-users] Fwd: uwm download url
In-Reply-To: <55593306.7000007@slackbuilds.org>
References: <CAMt7G9Sz1ok0XC4nsVhz-JY9d6o_gPhKSMd32Aapkm4zyPZ4MQ@mail.gmail.com>
 <CAAcyf-qkQQMtcKCpXuQLtP13MSufS+kR8owWnbQrZvAgYDHpqQ@mail.gmail.com>
 <55593306.7000007@slackbuilds.org>
Message-ID: <CAAcyf-qudBo5GD7szafKcjkuBeA50u=xw8hF=GpNQqCoVCdrKw@mail.gmail.com>

 On Sun, May 17, 2015, 5:32 PM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

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

> It appears that when this URL was 'fixed', the link did not use the
> proper HTML code for a space:
>
> http://slackbuilds.org/cgit/slackbuilds/commit/?id=c31197f3a891abeb8b8
<http://slackbuilds.org/cgit/slackbuilds/commit/?id=c31197f3a891abeb8b89a9508b659a585245d7fc>
9a9508b659a585245d7fc
<http://slackbuilds.org/cgit/slackbuilds/commit/?id=c31197f3a891abeb8b89a9508b659a585245d7fc>
>
>
>
>
> I don't mind people fixing links on things I maintain, but we
> probably should make it correct.  ;^)

i tested in browser and wget "URL" and both works

 Hmmm, what tool had an issue David?

I would be surprised if wget wasn't used by most tools ...


- --
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVZMwYACgkQiHuDdNczM4GKdQCgpJiFwrLwzf9crVZiRXuW4zo8
jN8An3SXmwYYfs8P3XXLaZrqLMlg6gie
=iIXJ
-----END PGP SIGNATURE-----
_______________________________________________
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/20150518/551aaf0d/attachment-0001.html>

From baildon.research at googlemail.com  Mon May 18 09:07:56 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Mon, 18 May 2015 10:07:56 +0100
Subject: [Slackbuilds-users] Fwd: uwm download url
In-Reply-To: <CAAcyf-qudBo5GD7szafKcjkuBeA50u=xw8hF=GpNQqCoVCdrKw@mail.gmail.com>
References: <CAMt7G9Sz1ok0XC4nsVhz-JY9d6o_gPhKSMd32Aapkm4zyPZ4MQ@mail.gmail.com>
 <CAAcyf-qkQQMtcKCpXuQLtP13MSufS+kR8owWnbQrZvAgYDHpqQ@mail.gmail.com>
 <55593306.7000007@slackbuilds.org>
 <CAAcyf-qudBo5GD7szafKcjkuBeA50u=xw8hF=GpNQqCoVCdrKw@mail.gmail.com>
Message-ID: <CAMt7G9QLVyXndTttJeVToR7B9LxJAwAuxgN5=96bEMhRLbBggw@mail.gmail.com>

Yo People,

The problem is that the DOWNLOAD variable in the .info file can define
multiple URLs to download, separated by whitespace. That's why you
can't have whitespace in URLs in the .info file. %-encoding gets round
the problem trivially.

Also, rfc3986...

Best regards
-D.

From matteo.bernardini at gmail.com  Mon May 18 09:35:07 2015
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 18 May 2015 11:35:07 +0200
Subject: [Slackbuilds-users] Fwd: uwm download url
In-Reply-To: <CAMt7G9QLVyXndTttJeVToR7B9LxJAwAuxgN5=96bEMhRLbBggw@mail.gmail.com>
References: <CAMt7G9Sz1ok0XC4nsVhz-JY9d6o_gPhKSMd32Aapkm4zyPZ4MQ@mail.gmail.com>
 <CAAcyf-qkQQMtcKCpXuQLtP13MSufS+kR8owWnbQrZvAgYDHpqQ@mail.gmail.com>
 <55593306.7000007@slackbuilds.org>
 <CAAcyf-qudBo5GD7szafKcjkuBeA50u=xw8hF=GpNQqCoVCdrKw@mail.gmail.com>
 <CAMt7G9QLVyXndTttJeVToR7B9LxJAwAuxgN5=96bEMhRLbBggw@mail.gmail.com>
Message-ID: <CAPsDuS47EZEH=j34tzFgHZahfaPdvFnnXJmf8jUBq9xRzei6_w@mail.gmail.com>

2015-05-18 11:07 GMT+02:00 David Spencer <baildon.research at googlemail.com>:
> Yo People,
>
> The problem is that the DOWNLOAD variable in the .info file can define
> multiple URLs to download, separated by whitespace. That's why you
> can't have whitespace in URLs in the .info file. %-encoding gets round
> the problem trivially.
>
> Also, rfc3986...

yup, you can see another effect of the whitespace also on

http://slackbuilds.org/repository/14.1/desktop/uwm/

besides what David says, let me state a thing about sourceforge urls
(I hope for the benefit of all submitters): as they often get extra
long and confusing, take in account that *ALL* downloads from there
can be in the form

http://downloads.sf.net/${name_of_the_project}/${tarball_name}

so, in this case

https://sourceforge.net/projects/udeproject/files/UWM/uwm-0.2.11a%20stable/uwm-0.2.11a.tar.gz

can be written also as

https://downloads.sf.net/udeproject/uwm-0.2.11a.tar.gz

that is so much less confusing (and error-prone)...

Matteo

From ryan.q at linux.com  Mon May 18 13:34:54 2015
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Mon, 18 May 2015 13:34:54 +0000
Subject: [Slackbuilds-users] Fwd: uwm download url
In-Reply-To: <CAPsDuS47EZEH=j34tzFgHZahfaPdvFnnXJmf8jUBq9xRzei6_w@mail.gmail.com>
References: <CAMt7G9Sz1ok0XC4nsVhz-JY9d6o_gPhKSMd32Aapkm4zyPZ4MQ@mail.gmail.com>
 <CAAcyf-qkQQMtcKCpXuQLtP13MSufS+kR8owWnbQrZvAgYDHpqQ@mail.gmail.com>
 <55593306.7000007@slackbuilds.org>
 <CAAcyf-qudBo5GD7szafKcjkuBeA50u=xw8hF=GpNQqCoVCdrKw@mail.gmail.com>
 <CAMt7G9QLVyXndTttJeVToR7B9LxJAwAuxgN5=96bEMhRLbBggw@mail.gmail.com>
 <CAPsDuS47EZEH=j34tzFgHZahfaPdvFnnXJmf8jUBq9xRzei6_w@mail.gmail.com>
Message-ID: <CAAcyf-rz3Cy20hryDp=GKyaeGQDVqVuWsw2czTjXThdUm9MBhA@mail.gmail.com>

On Mon, May 18, 2015 at 2:35 AM Matteo Bernardini <
matteo.bernardini at gmail.com> wrote:

> 2015-05-18 11:07 GMT+02:00 David Spencer <baildon.research at googlemail.com
> >:
> > Yo People,
> >
> > The problem is that the DOWNLOAD variable in the .info file can define
> > multiple URLs to download, separated by whitespace. That's why you
> > can't have whitespace in URLs in the .info file. %-encoding gets round
> > the problem trivially.
> >
> > Also, rfc3986...
>
> yup, you can see another effect of the whitespace also on
>
> http://slackbuilds.org/repository/14.1/desktop/uwm/
>
> besides what David says, let me state a thing about sourceforge urls
> (I hope for the benefit of all submitters): as they often get extra
> long and confusing, take in account that *ALL* downloads from there
> can be in the form
>
> http://downloads.sf.net/${name_of_the_project}/${tarball_name}
>
> so, in this case
>
>
> https://sourceforge.net/projects/udeproject/files/UWM/uwm-0.2.11a%20stable/uwm-0.2.11a.tar.gz
>
> can be written also as
>
> https://downloads.sf.net/udeproject/uwm-0.2.11a.tar.gz
>
> that is so much less confusing (and error-prone)...
>
>
Good advice Matteo.

Fixed in my branch.  ;^)


> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150518/2676382b/attachment.html>

From kingbeowulf at gmail.com  Mon May 18 15:17:09 2015
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 18 May 2015 08:17:09 -0700
Subject: [Slackbuilds-users]  CImg-1.5.9 download location removed
Message-ID: <555A0275.7010405@gmail.com>

Sourceforge (?) decided to remove older versions of CImg.  I'll submit
new once I can test those projects for which CImg is a dependency.  In
the meantime, I can temporarily host the file here:

http://www.linuxgalaxy.org/sbo-files

This ancient P4 server sits on my desk with a freedns.afraid.org dynamic
DNS poking through Comcast.  A more reliable location under SBo control
may be preferred.

Ping me off list if the files are not accessible.

-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/20150518/e4e5553c/attachment.asc>

From matteo.bernardini at gmail.com  Mon May 18 15:25:52 2015
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 18 May 2015 17:25:52 +0200
Subject: [Slackbuilds-users] CImg-1.5.9 download location removed
In-Reply-To: <555A0275.7010405@gmail.com>
References: <555A0275.7010405@gmail.com>
Message-ID: <CAPsDuS7fv5cApdUgmH0BAe8TPz5aqjwWG+uoEBHxY7NU+h0hHg@mail.gmail.com>

2015-05-18 17:17 GMT+02:00 King Beowulf <kingbeowulf at gmail.com>:
> This ancient P4 server sits on my desk with a freedns.afraid.org dynamic
> DNS poking through Comcast.  A more reliable location under SBo control
> may be preferred.

far from being "official" but I host other sources here so, if it's ok for you,

http://ponce.cc/slackware/sources/repo/CImg-1.5.9.zip

Matteo

From kingbeowulf at gmail.com  Mon May 18 16:09:50 2015
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 18 May 2015 09:09:50 -0700
Subject: [Slackbuilds-users] CImg-1.5.9 download location removed
In-Reply-To: <CAPsDuS7fv5cApdUgmH0BAe8TPz5aqjwWG+uoEBHxY7NU+h0hHg@mail.gmail.com>
References: <555A0275.7010405@gmail.com>
 <CAPsDuS7fv5cApdUgmH0BAe8TPz5aqjwWG+uoEBHxY7NU+h0hHg@mail.gmail.com>
Message-ID: <555A0ECE.80600@gmail.com>

On 05/18/2015 08:25 AM, Matteo Bernardini wrote:
> 2015-05-18 17:17 GMT+02:00 King Beowulf <kingbeowulf at gmail.com>:
>> This ancient P4 server sits on my desk with a freedns.afraid.org dynamic
>> DNS poking through Comcast.  A more reliable location under SBo control
>> may be preferred.
> 
> far from being "official" but I host other sources here so, if it's ok for you,
> 
> http://ponce.cc/slackware/sources/repo/CImg-1.5.9.zip
> 
> Matteo

Thanks.  I'm not quite ready to "self-host" and the hobby server is a
recycled HP box from the year 2000.  It has newer drives, but it is
anyone's guess how much longer it will last!  Not to mention being on
Comcast ISP...

Admins: please update the CImg download links to point to Matteo's server.

-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/20150518/4785f11b/attachment.asc>

From matteo.bernardini at gmail.com  Mon May 18 16:21:11 2015
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 18 May 2015 18:21:11 +0200
Subject: [Slackbuilds-users] CImg-1.5.9 download location removed
In-Reply-To: <555A0ECE.80600@gmail.com>
References: <555A0275.7010405@gmail.com>
 <CAPsDuS7fv5cApdUgmH0BAe8TPz5aqjwWG+uoEBHxY7NU+h0hHg@mail.gmail.com>
 <555A0ECE.80600@gmail.com>
Message-ID: <CAPsDuS53imHc=6PRELSKFvG+F5gp1SBbrjKYhT6X7Q0e3VLcJw@mail.gmail.com>

2015-05-18 18:09 GMT+02:00 King Beowulf <kingbeowulf at gmail.com>:
> Admins: please update the CImg download links to point to Matteo's server.

it's done in my personal branch, will go in the master one at the next
global update (if you don't submit the new version first).

Matteo

From t3slider at gmail.com  Mon May 18 21:23:16 2015
From: t3slider at gmail.com (T3slider)
Date: Mon, 18 May 2015 17:23:16 -0400
Subject: [Slackbuilds-users] Updates - 20150517.1
In-Reply-To: <5558CCD8.30907@slackbuilds.org>
References: <5558CCD8.30907@slackbuilds.org>
Message-ID: <20150518212316.GA1837@MyPC.phub.net.cable.rogers.com>

On Mon, May 18, 2015 at 12:16:08AM +0700, Willy Sudiarto Raharjo wrote:
> network/irssi_otr: Updated for version 1.0.0.

diff --git a/network/irssi_otr/irssi_otr.info b/network/irssi_otr/irssi_otr.info
index a32bb3f..63a6256 100644
--- a/network/irssi_otr/irssi_otr.info
+++ b/network/irssi_otr/irssi_otr.info
@@ -1,12 +1,10 @@
 PRGNAM="irssi_otr"
-VERSION="0.3"
-HOMEPAGE="http://irssi-otr.tuxfamily.org/"
-DOWNLOAD="ftp://download.tuxfamily.org/irssiotr/irssi-otr-0.3.tar.gz \
-          http://www.cypherpunks.ca/otr/libotr-3.2.1.tar.gz"
-MD5SUM="e3d46a31955470dd3fa0f6392c1dcfb4 \
-        974acf937d2ce0ee89b27a9815c17a3f"
+VERSION="1.0.0"
+HOMEPAGE="https://github.com/cryptodotis/irssi-otr"
+DOWNLOAD="https://github.com/cryptodotis/irssi-otr/archive/v1.0.0.tar.gz"
+MD5SUM="e3d46a31955470dd3fa0f6392c1dcfb4"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES=""
+REQUIRES="libotr"
 MAINTAINER="B. Watson"
 EMAIL="yalhcru at gmail.com"

Note the MD5SUM being carried over from 0.3 to 1.0.0. The new md5 should
be 5af78a07cae1b6082145416928c41a23. I have not tried building it to see
if it actually compiles.

From yalhcru at gmail.com  Mon May 18 22:44:10 2015
From: yalhcru at gmail.com (B Watson)
Date: Mon, 18 May 2015 18:44:10 -0400
Subject: [Slackbuilds-users] Updates - 20150517.1
In-Reply-To: <20150518212316.GA1837@MyPC.phub.net.cable.rogers.com>
References: <5558CCD8.30907@slackbuilds.org>
 <20150518212316.GA1837@MyPC.phub.net.cable.rogers.com>
Message-ID: <CAN1hMuBPR9CYXYge=wdYMKOXS0+1pWEjBiN_PhRZipF7gQfFqA@mail.gmail.com>

On 5/18/15, T3slider <t3slider at gmail.com> wrote:

> Note the MD5SUM being carried over from 0.3 to 1.0.0. The new md5 should
> be 5af78a07cae1b6082145416928c41a23. I have not tried building it to see
> if it actually compiles.

Fixed on my branch, thanks for pointing it out.

From x77 at shaw.ca  Tue May 19 03:07:57 2015
From: x77 at shaw.ca (x y)
Date: Mon, 18 May 2015 21:07:57 -0600 (MDT)
Subject: [Slackbuilds-users] Qbittorrent
Message-ID: <1593021375.52808110.1432004877396.JavaMail.root@shaw.ca>

Slackware64-14.1 

Upgraded Qbittorrent to 3.2.0 with 

GeoIP-1.5.1 
libtorrent-rasterbar-1.0.4 

I kept the GeoIP build script stock, as downloaded from slackbuilds.org 
I bumped the version in libtorrent-rasterbar.SlackBuild to 1.0.4 
I modified the qbittorrent.SlackBuild in two places, a version bump and removed the --qtdir flag that was passed to configure. First build attempt failed at that flag. 

It built fine, with a remarkable speed increase. Very worth the effort. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150518/f7316b05/attachment.html>

From yalhcru at gmail.com  Tue May 19 06:16:52 2015
From: yalhcru at gmail.com (B Watson)
Date: Tue, 19 May 2015 02:16:52 -0400
Subject: [Slackbuilds-users] Scripts up for grabs
In-Reply-To: <20150516200820.68be24f5@shaggy.doo>
References: <20150516200820.68be24f5@shaggy.doo>
Message-ID: <CAN1hMuDEMXdKvzuMyd01YMsaFjdAbEKA2ReWh1QuEVuD9wXQ1A@mail.gmail.com>

On 5/16/15, Erik Hanson <erik at slackbuilds.org> wrote:

> lbzip2

I'll take this one, if it's still available.

From dave at dawoodfall.net  Tue May 19 09:59:49 2015
From: dave at dawoodfall.net (David Woodfall)
Date: Tue, 19 May 2015 10:59:49 +0100
Subject: [Slackbuilds-users] Qbittorrent
In-Reply-To: <1593021375.52808110.1432004877396.JavaMail.root@shaw.ca>
References: <1593021375.52808110.1432004877396.JavaMail.root@shaw.ca>
Message-ID: <20150519095949.GM26891@Blackswan>

>Slackware64-14.1
>
>Upgraded Qbittorrent to 3.2.0 with
>
>GeoIP-1.5.1
>libtorrent-rasterbar-1.0.4
>
>I kept the GeoIP build script stock, as downloaded from slackbuilds.org
>I bumped the version in libtorrent-rasterbar.SlackBuild to 1.0.4
>I modified the qbittorrent.SlackBuild in two places, a version bump and removed the --qtdir flag that was passed to configure. First build attempt failed at that flag.
>
>It built fine, with a remarkable speed increase. Very worth the effort.

Thanks.

I will have a look later to see if it builds with
libtorrent-rasterbar 0.16.19, which is the version currently on sbo.

Dave

From crculver at christopherculver.com  Tue May 19 18:00:16 2015
From: crculver at christopherculver.com (Christopher Culver)
Date: Tue, 19 May 2015 21:00:16 +0300
Subject: [Slackbuilds-users] zathura md5sum mismatch
Message-ID: <87k2w4a1n3.fsf@aura.christopherculver.com>

When attempting to install zathura through sbopkg, the following error
is thrown due to a mismatch in the md5 sum:

Processing zathura

zathura:
zathura not found in /var/cache/sbopkg.
--2015-05-19 21:05:08--  http://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz
Resolving www.pwmt.org (www.pwmt.org)... 95.129.55.168
Connecting to www.pwmt.org (www.pwmt.org)|95.129.55.168|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz [following]
--2015-05-19 21:05:09--  https://www.pwmt.org/projects/zathura/download/zathura-0.3.3.tar.gz
Connecting to www.pwmt.org (www.pwmt.org)|95.129.55.168|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 203604 (199K) [application/x-tar]
Saving to: ?zathura-0.3.3.tar.gz?

100%[======================================>] 203,604     1.07MB/s   in 0.2s   

2015-05-19 21:05:10 (1.07 MB/s) - ?zathura-0.3.3.tar.gz? saved [203604/203604]

Found zathura-0.3.3.tar.gz in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for zathura-0.3.3.tar.gz ... FAILED!
    Expected: 53124af80e974283a6678319a62e6666
    Found:    d360252210ce51a29e8d341b1b72a7cc


From yalhcru at gmail.com  Tue May 19 18:23:54 2015
From: yalhcru at gmail.com (B Watson)
Date: Tue, 19 May 2015 14:23:54 -0400
Subject: [Slackbuilds-users] zathura md5sum mismatch
In-Reply-To: <87k2w4a1n3.fsf@aura.christopherculver.com>
References: <87k2w4a1n3.fsf@aura.christopherculver.com>
Message-ID: <CAN1hMuC4g+Lv49ASSXazOpmKZM8P2dcrCNxDMn29DTF1ET+9nA@mail.gmail.com>

On 5/19/15, Christopher Culver <crculver at christopherculver.com> wrote:
> When attempting to install zathura through sbopkg, the following error
> is thrown due to a mismatch in the md5 sum:

Yeah,, sorry about that. Fixed in my git branch. You can grab a copy
of the corrected info file here, if you don't want to wait for the
next update:

http://slackbuilds.org/cgit/slackbuilds/plain/office/zathura/zathura.info?h=user/urchlay/updates&id=5fdce54a30353c2af6ce106c2946736df7fc40cc

From alleytrotter at gmail.com  Tue May 19 19:22:32 2015
From: alleytrotter at gmail.com (John Yost)
Date: Tue, 19 May 2015 15:22:32 -0400
Subject: [Slackbuilds-users] QEMU
Message-ID: <555B8D78.3060309@gmail.com>

After the last update to qemu I am getting the following warning:
WARNING: Image format was not specified for '/mnt/build/buildvm' and
probing guessed raw.
         Automatically detecting the format is dangerous for raw images,
write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the restrictions.

Does anyone know where I should "Specify the 'raw' format"?

I use this as my start command:
[CODE]
usr/bin/qemu-system-x86_64 \
-boot c \
-name build \
-cpu qemu64 \
-smp cores=2 \
-enable-kvm \
-m 16G \
-localtime \
-soundhw es1370 \
-cdrom
/mnt/other/Slackware/slackware64-14.1-iso/slackware64-14.1-install-dvd.iso \
-usb \
-usbdevice host:0781:5581 \
-vga vmware \
-hda /mnt/build/buildvm
[/CODE]

TIA
john

-- 
John David Yost
AlleyTrotter
pub   2048D/F3BDEB55 2014-05-23 [expires: Never]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xF3BDEB55.asc
Type: application/pgp-keys
Size: 2312 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150519/882117e2/attachment.bin>

From kingbeowulf at gmail.com  Tue May 19 19:45:30 2015
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 19 May 2015 12:45:30 -0700
Subject: [Slackbuilds-users] QEMU
In-Reply-To: <555B8D78.3060309@gmail.com>
References: <555B8D78.3060309@gmail.com>
Message-ID: <CAPiArqNOeCFtoTWyxqzwkNsp9iyCsXwbPmf9C+eZOR6R_5KFWg@mail.gmail.com>

On Tuesday, May 19, 2015, John Yost <alleytrotter at gmail.com> wrote:

> After the last update to qemu I am getting the following warning:
> WARNING: Image format was not specified for '/mnt/build/buildvm' and
> probing guessed raw.
>          Automatically detecting the format is dangerous for raw images,
> write operations on block 0 will be restricted.
>          Specify the 'raw' format explicitly to remove the restrictions.
>
> Does anyone know where I should "Specify the 'raw' format"?
>
> I use this as my start command:
> [CODE]
> usr/bin/qemu-system-x86_64 \
> -boot c \
> -name build \
> -cpu qemu64 \
> -smp cores=2 \
> -enable-kvm \
> -m 16G \
> -localtime \
> -soundhw es1370 \
> -cdrom
> /mnt/other/Slackware/slackware64-14.1-iso/slackware64-14.1-install-dvd.iso
> \
> -usb \
> -usbdevice host:0781:5581 \
> -vga vmware \
> -hda /mnt/build/buildvm
> [/CODE]
>
> TIA
> john
>
>
>
if "buildvm" is truly a raw image created with "qemu-img create" the just
rename it "buildvm.raw"

also switch "-f raw" might be aplicable, check man page.  i always use
qcow2 so i csn use its fancy features such ad copy on write.

-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/20150519/385ba6cc/attachment-0001.html>

From alleytrotter at gmail.com  Tue May 19 19:54:47 2015
From: alleytrotter at gmail.com (John Yost)
Date: Tue, 19 May 2015 15:54:47 -0400
Subject: [Slackbuilds-users] QEMU
In-Reply-To: <CAPiArqNOeCFtoTWyxqzwkNsp9iyCsXwbPmf9C+eZOR6R_5KFWg@mail.gmail.com>
References: <555B8D78.3060309@gmail.com>
 <CAPiArqNOeCFtoTWyxqzwkNsp9iyCsXwbPmf9C+eZOR6R_5KFWg@mail.gmail.com>
Message-ID: <555B9507.5030009@gmail.com>

On 05/19/2015 03:45 PM, King Beowulf wrote:
> On Tuesday, May 19, 2015, John Yost <alleytrotter at gmail.com> wrote:
> 
>> After the last update to qemu I am getting the following warning:
>> WARNING: Image format was not specified for '/mnt/build/buildvm' and
>> probing guessed raw.
>>          Automatically detecting the format is dangerous for raw images,
>> write operations on block 0 will be restricted.
>>          Specify the 'raw' format explicitly to remove the restrictions.
>>
>> Does anyone know where I should "Specify the 'raw' format"?
>>
>> I use this as my start command:
>> [CODE]
>> usr/bin/qemu-system-x86_64 \
>> -boot c \
>> -name build \
>> -cpu qemu64 \
>> -smp cores=2 \
>> -enable-kvm \
>> -m 16G \
>> -localtime \
>> -soundhw es1370 \
>> -cdrom
>> /mnt/other/Slackware/slackware64-14.1-iso/slackware64-14.1-install-dvd.iso
>> \
>> -usb \
>> -usbdevice host:0781:5581 \
>> -vga vmware \
>> -hda /mnt/build/buildvm
>> [/CODE]
>>
>> TIA
>> john
>>
>>
>>
> if "buildvm" is truly a raw image created with "qemu-img create" the just
> rename it "buildvm.raw"
> 
> also switch "-f raw" might be aplicable, check man page.  i always use
> qcow2 so i csn use its fancy features such ad copy on write.
> 
> -ed
> 
> 
> 
> 
> _______________________________________________
> 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/
> 

Thanks King Beowulf

Adding the file extension '.raw' works fine. When referencing the manual
"http://qemu.weilnetz.de/qemu-doc.html" I could not find anything
tanks again john


From chris.willing at iinet.net.au  Wed May 20 01:32:17 2015
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Wed, 20 May 2015 11:32:17 +1000
Subject: [Slackbuilds-users] digikam - missing ENTITY
Message-ID: <555BE421.1010308@iinet.net.au>

Building digikam.SlackBuild on 14.1 fails for me with:
cd /tmp/SBo/digikam-4.10.0/doc-translated/nl && /usr/bin/meinproc4 
--check --cache 
/tmp/SBo/digikam-4.10.0/build/doc-translated/nl/index.cache.bz2 
/tmp/SBo/digikam-4.10.0/doc-translated/nl/index.docbook
index.docbook:120: parser error : Entity 'Ivo.de.Klerk' not defined
&Freek.de.Kruijf;&Ivo.de.Klerk;

That happens about half way through a fairly long build - it can be 
demonstrated more quickly using checkXML, as in:

root at vmbulider64-141:/tmp# checkXML 
digikam-4.10.0/doc-translated/nl/index.docbook
index.docbook:120: parser error : Entity 'Ivo.de.Klerk' not defined
&Freek.de.Kruijf;&Ivo.de.Klerk;


It turns out this is due to the kde version installed on the system - my 
14.1 has kdelibs-4.10.5-x86_64-2. The kde on -current is 
kdelibs-4.14.6-x86_64-1 and the problem does not show up there. There is 
also discussion/confirmation at: https://bugs.kde.org/show_bug.cgi?id=329637


I tried a few ways around this - all work and are probably OK for most 
situations:
1. don't build the translated docs - add
	-DBUILD_doc-translated:BOOL=OFF \
to the cmake options

2. remove or comment out line line 120 of 
doc-translated/nl/index.docbook file (or at least the reference 
'&Ivo.de.Klerk;')

3. patch the index.docbook file to replace the entity reference with an 
hopefully equivalent xml entry i.e. what the entity reference would have 
expanded out to, had it been valid. A working patch is attached.

I'm a bit surprised no one else seems to have had this problem - maybe 
everyone has already migrated to -current where this isn't an issue?


chris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: doc-deKlerk.diff
Type: text/x-patch
Size: 446 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150520/dc0b7aa6/attachment.bin>

From willysr at gmail.com  Wed May 20 03:49:47 2015
From: willysr at gmail.com (Willy Sudiarto Raharjo)
Date: Wed, 20 May 2015 10:49:47 +0700
Subject: [Slackbuilds-users] digikam - missing ENTITY
In-Reply-To: <555BE421.1010308@iinet.net.au>
References: <555BE421.1010308@iinet.net.au>
Message-ID: <CAJ+Qsa+YJ9g3D-26fC0TzxgE8SstJjtQr4B71c28OxB4NHBhRg@mail.gmail.com>

Sorry for that.
I have fixed it on my branch by not building the handbook

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

From willysr at slackbuilds.org  Wed May 20 17:50:40 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 21 May 2015 00:50:40 +0700
Subject: [Slackbuilds-users] call for testing: filezilla-3.11
Message-ID: <555CC970.3080202@slackbuilds.org>

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

Hi all

since last year, i tried to work on newer filezilla than what we have
in our repo (currently 3.8) and it seems that it was buggy so i had to
revert it.

Today i'm making another effort of upgrading filezilla to 3.11.
If you are using filezilla, please help on testing the new package by
looking at my filezilla-review branch
(http://slackbuilds.org/cgit/slackbuilds/log/?h=filezilla-review).

The new filezilla requires wxGTK3, but i also need to make some
changes into wxGTK3 as well, so there are 2 commits on that branch.

PS: i hope the changes in wxGTK3 doesn't affect other packages as well

Thanks


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVcyXAACgkQiHuDdNczM4H0JwCgrgphmskFZBEdiYeq2L3fOp30
TcMAn27Fle53+gLgvnevCAMgBG1WNfed
=Y2sw
-----END PGP SIGNATURE-----

From kingbeowulf at gmail.com  Thu May 21 23:49:43 2015
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 21 May 2015 16:49:43 -0700
Subject: [Slackbuilds-users] QEMU
In-Reply-To: <555B9507.5030009@gmail.com>
References: <555B8D78.3060309@gmail.com>
 <CAPiArqNOeCFtoTWyxqzwkNsp9iyCsXwbPmf9C+eZOR6R_5KFWg@mail.gmail.com>
 <555B9507.5030009@gmail.com>
Message-ID: <555E6F17.1090202@gmail.com>

On 05/19/2015 12:54 PM, John Yost wrote:


> 
> Thanks King Beowulf
> 
> Adding the file extension '.raw' works fine. When referencing the manual
> "http://qemu.weilnetz.de/qemu-doc.html" I could not find anything
> tanks again john
>

John

it's there.  Instead of invoking your guest as "-hda <image>" block
device, you can define hda:

-drive file=<image>,index=0,media=disk,format=raw

the format=<fmt> is there corrupted or untrusted format headers.

The "drive" switch has MANY more options to fully define the drive type,
bus, interface, etc.

Have fun
-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/20150521/d71b6cdc/attachment.asc>

From mherda at slackword.net  Fri May 22 22:03:50 2015
From: mherda at slackword.net (Marcin Herda)
Date: Fri, 22 May 2015 23:03:50 +0100
Subject: [Slackbuilds-users] dwb slackbuild anyone?
Message-ID: <555FA7C6.7090401@slackword.net>

Hi there,

I have not been using dwb for quite a long time. Does anyone want to 
take over this one?


As far as I can see, the stable version has not been updated for over 2 
years and it looks like it'll need some patching. See:
http://www.linuxquestions.org/questions/slackware-14/slackbuild-for-dwb-packege-fails-cannot-find-json-c-4175543333/

regards
Marcin

From alleytrotter at gmail.com  Sat May 23 16:41:19 2015
From: alleytrotter at gmail.com (John Yost)
Date: Sat, 23 May 2015 12:41:19 -0400
Subject: [Slackbuilds-users] QEMU
In-Reply-To: <555E6F17.1090202@gmail.com>
References: <555B8D78.3060309@gmail.com>
 <CAPiArqNOeCFtoTWyxqzwkNsp9iyCsXwbPmf9C+eZOR6R_5KFWg@mail.gmail.com>
 <555B9507.5030009@gmail.com> <555E6F17.1090202@gmail.com>
Message-ID: <5560ADAF.7050900@gmail.com>

On 05/21/2015 07:49 PM, King Beowulf wrote:
> On 05/19/2015 12:54 PM, John Yost wrote:
> 
> 
>> 
>> Thanks King Beowulf
>> 
>> Adding the file extension '.raw' works fine. When referencing the
>> manual "http://qemu.weilnetz.de/qemu-doc.html" I could not find
>> anything tanks again john
>> 
> 
> John
> 
> it's there.  Instead of invoking your guest as "-hda <image>"
> block device, you can define hda:
> 
> -drive file=<image>,index=0,media=disk,format=raw
> 
> the format=<fmt> is there corrupted or untrusted format headers.
> 
> The "drive" switch has MANY more options to fully define the drive
> type, bus, interface, etc.
> 
> Have fun -Ed
> 
> 
Thanks again Ed
I guess I am pretty old school.
I am just now switching over to using VM's for Linux
For all these years with Slackware (since about'98) I lived on
separate partitions for build, current, rescue, and production. Of
course this method requires a reboot to switch between worlds. So I am
now experimenting with Qemu. From your replies it seems I will need to
study the -drive switch and also look into 'copy on write'.
My biggest problem so far is passing info back and forth. I have been
using a usb stick but I see there are many other methods.
John


-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xF3BDEB55.asc
Type: application/pgp-keys
Size: 2312 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150523/b9f9c838/attachment.bin>

From pprkut at liwjatan.at  Sat May 23 17:33:01 2015
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Sat, 23 May 2015 19:33:01 +0200
Subject: [Slackbuilds-users] FFmpeg update
Message-ID: <2641720.EPdaEcPPNf@titania>

Hello everyone,

I got more and more requests from people about an update for the ffmpeg version 
we have in the repo as it is already quite a bit dated. Usually I wait until a 
new Slackware release with the update, since verifying everything still builds 
with it is easier this way. Even more so since the amount of packages 
depending/using ffmpeg grew so large that testing it all by myself is no longer 
feasible.

However, while the next Slackware release is definitely closer than it was a 
couple months ago, I guess it's still a ways off. So I figured we might as well 
try to test the update in a "crowdsourced" fashion and see how that goes :)

I pushed a branch with my changes to github. You can find it here:

https://github.com/pprkut/SlackBuilds/tree/ffmpeg

This contains an updated ffmpeg (2.6.3), x264 (20150223) and ffmpegthumbnailer 
(2.0.10) as well as build fixes for transcode.

What remains is testing all the remaining scripts to make sure nothing breaks.

I grepped the repo and had a look at everything that might depend on ffmpeg or 
x264. Below you can find a (hopefully) comprehensive list. Items I'm not sure 
about I marked with "(?)". I already tested

libraries/libquicktime
multimedia/mediatomb
multimedia/transcode

I kindly ask for help testing the remaining scripts to make sure nothing 
breaks :)

I already know John Vogel tested some of these, so it might be good to wait 
for his feedback before rushing off compiling things in order to reduce 
duplicate work. Although double-checking certainly won't hurt here :)

Thanks in advance for the help! Here we go with the list:

ffmpeg
===================
audio/audacity
audio/cmus
audio/deadbeef
audio/kid3
audio/kradio
audio/lastfm
audio/mpd
audio/qmmp
audio/soundconverter
audio/xmms2 (?)
audio/xwax
desktop/recorditnow
desktop/ssr
desktop/thunar-thumbnailers
games/alephone
games/dolphin-emu
games/openmw
games/vcmi
gis/grass
graphics/digikam
libraries/OpenSceneGraph (?)
libraries/alsa-plugins
libraries/audioread
libraries/chromaprint
libraries/ffms2
libraries/libunicap
libraries/libvdpau-va-gl
libraries/opal
libraries/opencv
libraries/wxsvg
multimedia/bombono-dvd
multimedia/cantata
multimedia/cinelerra
multimedia/devede
multimedia/dvd-slideshow
multimedia/dvdrip
multimedia/dvdstyler (?)
multimedia/emoc
multimedia/ffmpeg2theora
multimedia/flowblade
multimedia/get_iplayer
multimedia/gimp-gap
multimedia/gnupod
multimedia/gpac
multimedia/guvcview
multimedia/imagination
multimedia/kino
multimedia/kodi (?)
multimedia/lives
multimedia/lwks
multimedia/makemkv
multimedia/minidlna
multimedia/miro
multimedia/mlt
multimedia/mpv
multimedia/ripit
multimedia/rosa-media-player
multimedia/sinthgunt
multimedia/spek
multimedia/stills2dv
multimedia/vlc (?)
multimedia/winff
multimedia/xjadeo
multimedia/xvst
network/Pafy
network/cherokee
network/freerdp
network/imageshack-uploader (?)
network/linphone
network/you-get
network/youtube-dl
network/ZoneMinder
system/motion

x264
===================
libraries/gst1-plugins-ugly
multimedia/avidemux
multimedia/gst-plugins-ugly
multimedia/kdenlive
multimedia/mythtv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150523/e190ca81/attachment-0001.asc>

From jvogel4 at stny.rr.com  Sat May 23 17:47:02 2015
From: jvogel4 at stny.rr.com (John Vogel)
Date: Sat, 23 May 2015 13:47:02 -0400
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <2641720.EPdaEcPPNf@titania>
References: <2641720.EPdaEcPPNf@titania>
Message-ID: <20150523134702.72f76438@stygian.lan>

On Sat, 23 May 2015 19:33:01 +0200
Heinz Wiesinger <pprkut at liwjatan.at> wrote:

> Hello everyone,
> 
> I got more and more requests from people about an update for the ffmpeg version 
> we have in the repo as it is already quite a bit dated. Usually I wait until a 
> new Slackware release with the update, since verifying everything still builds 
> with it is easier this way. Even more so since the amount of packages 
> depending/using ffmpeg grew so large that testing it all by myself is no longer 
> feasible.
> 
> However, while the next Slackware release is definitely closer than it was a 
> couple months ago, I guess it's still a ways off. So I figured we might as well 
> try to test the update in a "crowdsourced" fashion and see how that goes :)
> 
> I pushed a branch with my changes to github. You can find it here:
> 
> https://github.com/pprkut/SlackBuilds/tree/ffmpeg
> 
> This contains an updated ffmpeg (2.6.3), x264 (20150223) and ffmpegthumbnailer 
> (2.0.10) as well as build fixes for transcode.
> 
> What remains is testing all the remaining scripts to make sure nothing breaks.
> 
> I grepped the repo and had a look at everything that might depend on ffmpeg or 
> x264. Below you can find a (hopefully) comprehensive list. Items I'm not sure 
> about I marked with "(?)". I already tested
> 
> libraries/libquicktime
> multimedia/mediatomb
> multimedia/transcode
> 
> I kindly ask for help testing the remaining scripts to make sure nothing 
> breaks :)
> 
> I already know John Vogel tested some of these, so it might be good to wait 
> for his feedback before rushing off compiling things in order to reduce 
> duplicate work. Although double-checking certainly won't hurt here :)
> 
> Thanks in advance for the help! Here we go with the list:
> 
> ffmpeg
> ===================
> audio/audacity
> audio/cmus
> audio/deadbeef
> audio/kid3
> audio/kradio
> audio/lastfm
> audio/mpd
> audio/qmmp
> audio/soundconverter
> audio/xmms2 (?)
> audio/xwax
> desktop/recorditnow
> desktop/ssr
> desktop/thunar-thumbnailers
> games/alephone
> games/dolphin-emu
> games/openmw
> games/vcmi
> gis/grass
> graphics/digikam
> libraries/OpenSceneGraph (?)
> libraries/alsa-plugins
> libraries/audioread
> libraries/chromaprint
> libraries/ffms2
> libraries/libunicap
> libraries/libvdpau-va-gl
> libraries/opal
> libraries/opencv
> libraries/wxsvg
> multimedia/bombono-dvd
> multimedia/cantata
> multimedia/cinelerra
> multimedia/devede
> multimedia/dvd-slideshow
> multimedia/dvdrip
> multimedia/dvdstyler (?)
> multimedia/emoc
> multimedia/ffmpeg2theora
> multimedia/flowblade
> multimedia/get_iplayer
> multimedia/gimp-gap
> multimedia/gnupod
> multimedia/gpac
> multimedia/guvcview
> multimedia/imagination
> multimedia/kino
> multimedia/kodi (?)
> multimedia/lives
> multimedia/lwks
> multimedia/makemkv
> multimedia/minidlna
> multimedia/miro
> multimedia/mlt
> multimedia/mpv
> multimedia/ripit
> multimedia/rosa-media-player
> multimedia/sinthgunt
> multimedia/spek
> multimedia/stills2dv
> multimedia/vlc (?)
> multimedia/winff
> multimedia/xjadeo
> multimedia/xvst
> network/Pafy
> network/cherokee
> network/freerdp
> network/imageshack-uploader (?)
> network/linphone
> network/you-get
> network/youtube-dl
> network/ZoneMinder
> system/motion
> 
> x264
> ===================
> libraries/gst1-plugins-ugly
> multimedia/avidemux
> multimedia/gst-plugins-ugly
> multimedia/kdenlive
> multimedia/mythtv

Thanks for the heads up, Heinz.

For work I have done so far and also have in progress, my repo is at:

https://github.com/jvvv/SBo-ffmpeg-related-build-fixes.

I've already contacted B. Watson about alephone patches. If I have time
this evening, I'll try to put together a build script for winff.
I haven't added it yet, but I'll also be adding an updated mpv SlackBuild
after dinner.

Cheers,
John

From jvogel4 at stny.rr.com  Sat May 23 20:31:08 2015
From: jvogel4 at stny.rr.com (John Vogel)
Date: Sat, 23 May 2015 16:31:08 -0400
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <20150523134702.72f76438@stygian.lan>
References: <2641720.EPdaEcPPNf@titania> <20150523134702.72f76438@stygian.lan>
Message-ID: <20150523163108.3a9d6a30@stygian.lan>

On Sat, 23 May 2015 13:47:02 -0400
John Vogel <jvogel4 at stny.rr.com> wrote:

-snip

> For work I have done so far and also have in progress, my repo is at:
> 
> https://github.com/jvvv/SBo-ffmpeg-related-build-fixes.
> 

I see that I mistakely added the . to the end of the link, should be:

https://github.com/jvvv/SBo-ffmpeg-related-build-fixes

with no period at the end. Sorry for any confusion caused.

- John

From gilles.chanteperdrix at xenomai.org  Sat May 23 22:51:26 2015
From: gilles.chanteperdrix at xenomai.org (Gilles Chanteperdrix)
Date: Sun, 24 May 2015 00:51:26 +0200
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <2641720.EPdaEcPPNf@titania>
References: <2641720.EPdaEcPPNf@titania>
Message-ID: <20150523225126.GE1987@hermes.click-hack.org>

On Sat, May 23, 2015 at 07:33:01PM +0200, Heinz Wiesinger wrote:
> multimedia/kodi (?)

Hi,

I am running ffmpeg 2.6.2, and tried and compile kodi 14.2 with that
release; it does not compile, kodi seems to rely on an ffmpeg
functions (as far as I understood for dvd support) which is no
longer available in recent versions. So, kodi has to be compiled
with the version of ffmpeg it contains, which is older. Maybe the
upcoming kodi 15 will avoid that issue, I have not tried yet.

Regards.

-- 
					    Gilles.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 811 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150524/3394de8e/attachment.asc>

From jvogel4 at stny.rr.com  Sun May 24 01:19:37 2015
From: jvogel4 at stny.rr.com (John Vogel)
Date: Sat, 23 May 2015 21:19:37 -0400
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <20150523225126.GE1987@hermes.click-hack.org>
References: <2641720.EPdaEcPPNf@titania>
 <20150523225126.GE1987@hermes.click-hack.org>
Message-ID: <20150523211937.56333399@stygian.lan>

On Sun, 24 May 2015 00:51:26 +0200
Gilles Chanteperdrix <gilles.chanteperdrix at xenomai.org> wrote:

> On Sat, May 23, 2015 at 07:33:01PM +0200, Heinz Wiesinger wrote:
> > multimedia/kodi (?)
> 
> Hi,
> 
> I am running ffmpeg 2.6.2, and tried and compile kodi 14.2 with that
> release; it does not compile, kodi seems to rely on an ffmpeg
> functions (as far as I understood for dvd support) which is no
> longer available in recent versions. So, kodi has to be compiled
> with the version of ffmpeg it contains, which is older. Maybe the
> upcoming kodi 15 will avoid that issue, I have not tried yet.
> 
> Regards.
> 
> -- 
> 					    Gilles.

xbmc forks ffmpeg and then patches it. This is also true for the beta
version of kodi 15, so I don't think it likely that external ffmpeg
will work well in that version either.

-- John

From willysr at slackbuilds.org  Sun May 24 01:58:41 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 24 May 2015 08:58:41 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <20150523225126.GE1987@hermes.click-hack.org>
References: <2641720.EPdaEcPPNf@titania>
 <20150523225126.GE1987@hermes.click-hack.org>
Message-ID: <55613051.1060008@slackbuilds.org>

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

> I am running ffmpeg 2.6.2, and tried and compile kodi 14.2 with
> that release; it does not compile, kodi seems to rely on an ffmpeg 
> functions (as far as I understood for dvd support) which is no 
> longer available in recent versions. So, kodi has to be compiled 
> with the version of ffmpeg it contains, which is older. Maybe the 
> upcoming kodi 15 will avoid that issue, I have not tried yet.


I just built kodi 14.2 and it is working fine

kodi:
  MD5SUM check for 14.2-Helix.tar.gz ... OK
  MD5SUM check for Helix_rc3.tar.gz ... OK
  MD5SUM check for 2.4.6-Helix.tar.gz ... OK
  Building package kodi-14.2-x86_64-1_SBo.tgz ... OK
  Installing package kodi-14.2-x86_64-1_SBo.tgz ... OK

AFAIK, kodi is built using ffmpeg that is defined in the DOWNLOAD, but
if you pass FFMPEG=yes, then it failed building it

DVDDemuxFFmpeg.cpp: In member function 'virtual void
CDVDDemuxFFmpeg::Flush()':
DVDDemuxFFmpeg.cpp:544:41: error: 'av_read_frame_flush' was not
declared in this scope
     av_read_frame_flush(m_pFormatContext);
                                         ^
make[1]: *** [DVDDemuxFFmpeg.o] Error 1
make: *** [xbmc/cores/dvdplayer/DVDDemuxers/DVDDemuxers.a] Error 2


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVhMFEACgkQiHuDdNczM4HSEQCeKYAKRLvAfPdLDRsnrRYnTdQ6
lDIAn1mTd1vGmVrMCkLr4aviMHIs/S35
=wQxT
-----END PGP SIGNATURE-----

From jvogel4 at stny.rr.com  Sun May 24 02:30:57 2015
From: jvogel4 at stny.rr.com (John Vogel)
Date: Sat, 23 May 2015 22:30:57 -0400
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <55613051.1060008@slackbuilds.org>
References: <2641720.EPdaEcPPNf@titania>
 <20150523225126.GE1987@hermes.click-hack.org>
 <55613051.1060008@slackbuilds.org>
Message-ID: <20150523223057.20e2aa80@stygian.lan>

On Sun, 24 May 2015 08:58:41 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> > I am running ffmpeg 2.6.2, and tried and compile kodi 14.2 with
> > that release; it does not compile, kodi seems to rely on an ffmpeg 
> > functions (as far as I understood for dvd support) which is no 
> > longer available in recent versions. So, kodi has to be compiled 
> > with the version of ffmpeg it contains, which is older. Maybe the 
> > upcoming kodi 15 will avoid that issue, I have not tried yet.
> 
> 
> I just built kodi 14.2 and it is working fine
> 
> kodi:
>   MD5SUM check for 14.2-Helix.tar.gz ... OK
>   MD5SUM check for Helix_rc3.tar.gz ... OK
>   MD5SUM check for 2.4.6-Helix.tar.gz ... OK
>   Building package kodi-14.2-x86_64-1_SBo.tgz ... OK
>   Installing package kodi-14.2-x86_64-1_SBo.tgz ... OK
> 
> AFAIK, kodi is built using ffmpeg that is defined in the DOWNLOAD, but
> if you pass FFMPEG=yes, then it failed building it
> 
> DVDDemuxFFmpeg.cpp: In member function 'virtual void
> CDVDDemuxFFmpeg::Flush()':
> DVDDemuxFFmpeg.cpp:544:41: error: 'av_read_frame_flush' was not
> declared in this scope
>      av_read_frame_flush(m_pFormatContext);
>                                          ^
> make[1]: *** [DVDDemuxFFmpeg.o] Error 1
> make: *** [xbmc/cores/dvdplayer/DVDDemuxers/DVDDemuxers.a] Error 2
> 
> 

Hi Willy,

Thanks for checking that. I think that kodi is a non-issue here.
kodi uses of it's own patched fork of ffmpeg, which makes building
kodi with mainstream ffmpeg either impossible or overly problematic.

Cheers,
John

From willysr at slackbuilds.org  Sun May 24 02:39:59 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 24 May 2015 09:39:59 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <20150523223057.20e2aa80@stygian.lan>
References: <2641720.EPdaEcPPNf@titania>
 <20150523225126.GE1987@hermes.click-hack.org>
 <55613051.1060008@slackbuilds.org> <20150523223057.20e2aa80@stygian.lan>
Message-ID: <556139FF.2040106@slackbuilds.org>

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

> Thanks for checking that. I think that kodi is a non-issue here. 
> kodi uses of it's own patched fork of ffmpeg, which makes building 
> kodi with mainstream ffmpeg either impossible or overly
> problematic.

True, that's what my sentence :)


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVhOf4ACgkQiHuDdNczM4FfYQCfajjsAfiDbidEFbFX45DvXAT8
PyUAn0QBcWlOl0+cVN44ftCD9dYM8NwN
=qZSr
-----END PGP SIGNATURE-----

From jvogel4 at stny.rr.com  Sun May 24 02:45:07 2015
From: jvogel4 at stny.rr.com (John Vogel)
Date: Sat, 23 May 2015 22:45:07 -0400
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <556139FF.2040106@slackbuilds.org>
References: <2641720.EPdaEcPPNf@titania>
 <20150523225126.GE1987@hermes.click-hack.org>
 <55613051.1060008@slackbuilds.org>
 <20150523223057.20e2aa80@stygian.lan>
 <556139FF.2040106@slackbuilds.org>
Message-ID: <20150523224507.0edf6edd@stygian.lan>

On Sun, 24 May 2015 09:39:59 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> 
> True, that's what my sentence :)

Ahh, I am so dense. Thanks for being so patient with me.

From willysr at slackbuilds.org  Sun May 24 03:00:42 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 24 May 2015 10:00:42 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <2641720.EPdaEcPPNf@titania>
References: <2641720.EPdaEcPPNf@titania>
Message-ID: <55613EDA.6020404@slackbuilds.org>

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

> graphics/digikam libraries/ffms2 libraries/opencv 
> multimedia/gimp-gap multimedia/guvcview

These are OK
opencv is not my package, but since it's part of digiKam's dependency,
i had to build it anyway

- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEAREIAAYFAlVhPtoACgkQiHuDdNczM4GwGgCfeijfWIH4/q7FozzDm9E0KOVD
+iQAn3O31q95o8NbuzYjJybsbhnltrU8
=mNtD
-----END PGP SIGNATURE-----

From jvogel4 at stny.rr.com  Sun May 24 05:18:36 2015
From: jvogel4 at stny.rr.com (John Vogel)
Date: Sun, 24 May 2015 01:18:36 -0400
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <2641720.EPdaEcPPNf@titania>
References: <2641720.EPdaEcPPNf@titania>
Message-ID: <20150524011836.07088c15@stygian.lan>

The following have been build tested:

audio/audacity (patched)
audio/cmus
audio/deadbeef
audio/kid3
audio/kradio
audio/lastfm
audio/mpd (0.19 failed; bumped to 0.19.9 succeeded)
audio/soundconverter
desktop/ffmpegthumbnailer
desktop/recorditnow
desktop/ssr
games/alephone (patched)
games/openmw
games/vcmi (disabled building launcher to avoid messing with qt5 dependency)
graphics/digikam (note: disabled building docs as per recent SBo git commit)
libraries/ffms2
libraries/libvdpau-va-gl
libraries/wxsvg
multimedia/bombono-dvd (patched)
multimedia/cantata
multimedia/cinelerra
multimedia/devede
multimedia/dvd-slideshow
multimedia/ffmpeg2theora
multimedia/get_iplayer
multimedia/guvcview
multimedia/imagination
multimedia/kino
multimedia/makemkv
multimedia/minidlna
multimedia/miro
multimedia/mlt (patched for unrelated issue; see multimedia/mlt/README)
multimedia/mpv (built 0.9.2)
multimedia/rosa-media-player
multimedia/sinthgunt
multimedia/spek
multimedia/transcode (patched)
multimedia/winff (skipped, binary package, ancient)
multimedia/xjadeo
network/freerdp
network/linphone

I realize that some of these are duplicates of other efforts.

I still need to notify maintainers for audacity and mpd. I'll do that
after I post this.

Cheers,
John

From willysr at slackbuilds.org  Sun May 24 06:42:40 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 24 May 2015 13:42:40 +0700
Subject: [Slackbuilds-users] Updates - 20150524.1
Message-ID: <556172E0.5070801@slackbuilds.org>

Sun May 24 06:28:19 UTC 2015
academic/R: Updated for version 3.2.0.
academic/sage: Updated for version 6.7.
desktop/boje-themes: Added (GTK2|GTK3 themes).
desktop/moka-themes: Added (GTK themes).
desktop/obkey: Added (Openbox key editor).
desktop/obsession: Added (Openbox session tools).
desktop/openbox-menu: Added (pipemenu for Openbox window manager).
desktop/rep-gtk: Added (Binding of the GTK and GDK libraries).
desktop/sawfish-pager: Added (A pager for sawfish).
desktop/sawfish-session-dialog: Added (Sawfish Extension).
desktop/sawfish: Added (Window Manager).
desktop/uwm: Fix DOWNLOAD.
development/CImg: Fixed download link.
development/Cython: Updated for version 0.22.
development/byacc: Added (parser generator)
development/fsharp: Updated for version 3.1.1.32.
development/gengetopt: Added (network scanner)
development/gnulib: Added (GNU portability library).
development/google-appengine-gosdk: Updated for version 1.9.20.
development/google-appengine-pysdk: Updated for version 1.9.20.
development/openjdk: Updated for version 7u79b14.
games/blobwars: Make game more child friendly.
games/edgar: Added (A 2D platform game).
games/eduke32: Build against SDL 1, not 2.
games/starfighter: Updated for version 1.3.3.
games/teeworlds: Fix .info file.
graphics/digikam: Disable building handbook.
graphics/photivo: Updated for version 20150519.
libraries/SFML: Fixed MD5SUM.
libraries/allegro: Updated for version 5.0.11 + new maintainer.
libraries/cffi: Updated for version 1.0.1.
libraries/ffms2: Updated for version 2.21.
libraries/lensfun: Updated for version 0.3.1.
libraries/libburn: Updated for version 1.4.0.
libraries/libisoburn: Updated for version 1.4.0.
libraries/libisofs: Updated for version 1.4.0.
libraries/libkvkontakte: Added (C++ Library)
libraries/librep: Added (Lisp system for Sawfish).
libraries/physfs: Change maintainer.
libraries/webkitgtk3: Updated for version 2.4.9.
libraries/webkitgtk: Updated for version 2.4.9.
libraries/wxGTK3: Build using --with-gtk=2.
misc/subsurface: Updated for version 4.4.2.
multimedia/x265: Updated for version 1.7.
multimedia/yarock: Added (Music player).
network/Electrum: Updated for version 2.2.
network/bitcoin: Updated for version 0.10.2.
network/filezilla: Updated for version 3.11.0.1.
network/haproxy: Updated for version 1.5.12 + new maintainer.
network/iojs: Updated for version 2.0.2.
network/irssi_otr: Fix MD5SUM.
network/phpmyadmin: Updated for version 4.4.7.
network/tor-browser: Updated for version 4.5.1.
network/vivaldi: Updated for version 1.0.178.2.
network/zmap: Added (network scanner)
office/zathura: Fix MD5SUMs.
perl/perl-CPAN-Meta-YAML: Updated for version 0.016.
python/flake8: Updated for version 2.4.1.
python/llfuse: Added (The Python LLFUSE Module).
python/pytest: Updated for version 2.7.1.
system/Attic: Update README.
system/dar: Updated for version 2.4.17.
system/docker: Updated for version 1.6.2.
system/epson-inkjet-printer-escpr: Updated for version 1.4.5.
system/glances: Updated for version 2.4.1.
system/inxi: Updated for version 2.2.21.
system/jq: Added (command-line JSON processor)
system/lbzip2: Updated for version 2.5.
system/slpkg: Updated for version 2.3.3.
system/suhosin: Updated for version 0.9.38.
system/thermal_daemon: Updated for version 1.4.2.
system/ttf-mscorefonts: Added (Microsoft TrueType core fonts)
system/usermin: Updated for version 1.660.
system/webmin: Updated for version 1.750.
system/xfsudo: Updated for version 0.7.1.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From ryan.q at linux.com  Sun May 24 15:10:08 2015
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Sun, 24 May 2015 15:10:08 +0000
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <20150524011836.07088c15@stygian.lan>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
Message-ID: <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>

 On Sun, May 24, 2015, 12:23 AM John Vogel <jvogel4 at stny.rr.com> wrote:

The following have been build tested:

audio/audacity (patched)


What did you have to patch on Audacity?

In my case adding:

LDFLAGS=/usr/lib${LIBDIRSUFFIX}

to the configure flags worked. At various times I have also had to add
'--disable-dynamic-loading', but I have built with ffmpeg 2.6.x without
that.

---


audio/cmus
audio/deadbeef
audio/kid3
audio/kradio
audio/lastfm
audio/mpd (0.19 failed; bumped to 0.19.9 succeeded)
audio/soundconverter
desktop/ffmpegthumbnailer
desktop/recorditnow
desktop/ssr
games/alephone (patched)
games/openmw
games/vcmi (disabled building launcher to avoid messing with qt5 dependency)
graphics/digikam (note: disabled building docs as per recent SBo git commit)
libraries/ffms2
libraries/libvdpau-va-gl
libraries/wxsvg
multimedia/bombono-dvd (patched)
multimedia/cantata
multimedia/cinelerra
multimedia/devede
multimedia/dvd-slideshow
multimedia/ffmpeg2theora
multimedia/get_iplayer
multimedia/guvcview
multimedia/imagination
multimedia/kino
multimedia/makemkv
multimedia/minidlna
multimedia/miro
multimedia/mlt (patched for unrelated issue; see multimedia/mlt/README)
multimedia/mpv (built 0.9.2)
multimedia/rosa-media-player
multimedia/sinthgunt
multimedia/spek
multimedia/transcode (patched)
multimedia/winff (skipped, binary package, ancient)
multimedia/xjadeo
network/freerdp
network/linphone

I realize that some of these are duplicates of other efforts.

I still need to notify maintainers for audacity and mpd. I'll do that
after I post this.

Cheers,
John
_______________________________________________
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/20150524/da04ff83/attachment.html>

From ryan.q at linux.com  Sun May 24 15:15:03 2015
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Sun, 24 May 2015 15:15:03 +0000
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
Message-ID: <CAAcyf-pWYKQgFwyQwuZgiFsY2NZ4gKQOs9ZLhbufBUAaFf=X_w@mail.gmail.com>

 On Sun, May 24, 2015, 10:10 AM Ryan P.C. McQuen <ryan.q at linux.com> wrote:


On Sun, May 24, 2015, 12:23 AM John Vogel <jvogel4 at stny.rr.com> wrote:

The following have been build tested:

audio/audacity (patched)

 What did you have to patch on Audacity?

In my case adding:

LDFLAGS=/usr/lib${LIBDIRSUFFIX}

to the configure flags worked. At various times I have also had to add
'--disable-dynamic-loading', but I have built with ffmpeg 2.6.x without
that.

 Wow, that was a poorly worded sentence. I meant to say, 'built audacity
with ffmpeg 2.6.x'.

---


audio/cmus
audio/deadbeef
audio/kid3
audio/kradio
audio/lastfm
audio/mpd (0.19 failed; bumped to 0.19.9 succeeded)
audio/soundconverter
desktop/ffmpegthumbnailer
desktop/recorditnow
desktop/ssr
games/alephone (patched)
games/openmw
games/vcmi (disabled building launcher to avoid messing with qt5 dependency)
graphics/digikam (note: disabled building docs as per recent SBo git commit)
libraries/ffms2
libraries/libvdpau-va-gl
libraries/wxsvg
multimedia/bombono-dvd (patched)
multimedia/cantata
multimedia/cinelerra
multimedia/devede
multimedia/dvd-slideshow
multimedia/ffmpeg2theora
multimedia/get_iplayer
multimedia/guvcview
multimedia/imagination
multimedia/kino
multimedia/makemkv
multimedia/minidlna
multimedia/miro
multimedia/mlt (patched for unrelated issue; see multimedia/mlt/README)
multimedia/mpv (built 0.9.2)
multimedia/rosa-media-player
multimedia/sinthgunt
multimedia/spek
multimedia/transcode (patched)
multimedia/winff (skipped, binary package, ancient)
multimedia/xjadeo
network/freerdp
network/linphone

I realize that some of these are duplicates of other efforts.

I still need to notify maintainers for audacity and mpd. I'll do that
after I post this.

Cheers,
John
_______________________________________________
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/20150524/ba0a5f56/attachment.html>

From willysr at slackbuilds.org  Sun May 24 15:46:37 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 24 May 2015 22:46:37 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <2641720.EPdaEcPPNf@titania>
References: <2641720.EPdaEcPPNf@titania>
Message-ID: <5561F25D.50003@slackbuilds.org>

> x264
> ===================
> libraries/gst1-plugins-ugly

OK

> multimedia/gst-plugins-ugly

Attached is patch for gst-plugins-ugly in order to build against new ffmpeg

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gst-plugins-ugly.patch
Type: text/x-patch
Size: 8832 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150524/201e652a/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150524/201e652a/attachment-0001.asc>

From willysr at slackbuilds.org  Sun May 24 15:59:22 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 24 May 2015 22:59:22 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <5561F25D.50003@slackbuilds.org>
References: <2641720.EPdaEcPPNf@titania> <5561F25D.50003@slackbuilds.org>
Message-ID: <5561F55A.3020402@slackbuilds.org>

>> multimedia/gst-plugins-ugly
> 
> Attached is patch for gst-plugins-ugly in order to build against new ffmpeg

Sorry, i was testing it on -current machine
it built fine without any patch needed in 14.1


-- 
Willy Sudiarto Raharjo

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

From kingbeowulf at gmail.com  Sun May 24 17:37:09 2015
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 24 May 2015 10:37:09 -0700
Subject: [Slackbuilds-users] QEMU
In-Reply-To: <5560ADAF.7050900@gmail.com>
References: <555B8D78.3060309@gmail.com>
 <CAPiArqNOeCFtoTWyxqzwkNsp9iyCsXwbPmf9C+eZOR6R_5KFWg@mail.gmail.com>
 <555B9507.5030009@gmail.com> <555E6F17.1090202@gmail.com>
 <5560ADAF.7050900@gmail.com>
Message-ID: <55620C45.1070707@gmail.com>

On 05/23/2015 09:41 AM, John Yost wrote:

> I guess I am pretty old school.
> I am just now switching over to using VM's for Linux
> For all these years with Slackware (since about'98) I lived on
> separate partitions for build, current, rescue, and production. Of
> course this method requires a reboot to switch between worlds. 

Same here: for ages I just had a number of partitions.  However, this
started to get tedious when I took on more SBo scripts.  A VM makes
testing new stuff in a "clean room" easier.  I used to use VirtualBox,
then Oracle grabbed them, so when QEMU was up for grabs I volunteered.

> So I am
> now experimenting with Qemu. From your replies it seems I will need to
> study the -drive switch and also look into 'copy on write'.
> My biggest problem so far is passing info back and forth. I have been
> using a usb stick but I see there are many other methods.
> John
> 

I've attached my qemu script for slackware-current, etc. It will give
you some ideas.  The virtio subsystem is very high performance. The VMs
are isolated from my network. Also, once the VM is running, the host
directory mounts with this fstab entry:

data    /mnt/hd    9p    trans=virtio   0   0

A host share, as well as the backing image I use makes a clean reset easy!

Enjoy,
Ed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: VM_Slackware64_current.sh
Type: application/x-shellscript
Size: 1929 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150524/a0136b13/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150524/a0136b13/attachment.asc>

From jvogel4 at stny.rr.com  Sun May 24 18:53:08 2015
From: jvogel4 at stny.rr.com (John Vogel)
Date: Sun, 24 May 2015 14:53:08 -0400
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
Message-ID: <20150524145308.409d864f@stygian.lan>

On Sun, 24 May 2015 15:10:08 +0000
"Ryan P.C. McQuen" <ryan.q at linux.com> wrote:

>  On Sun, May 24, 2015, 12:23 AM John Vogel <jvogel4 at stny.rr.com> wrote:
> 
> The following have been build tested:
> 
> audio/audacity (patched)
> 
> 
> What did you have to patch on Audacity?
> 
> In my case adding:
> 
> LDFLAGS=/usr/lib${LIBDIRSUFFIX}
> 
> to the configure flags worked. At various times I have also had to add
> '--disable-dynamic-loading', but I have built with ffmpeg 2.6.x without
> that.
> 

There's something weird about having to do that to LDFLAGS. Something
else is going on that is not obvious but looks like a tool chain issue.

-- John

From bielski.maciek at gmail.com  Sun May 24 23:37:52 2015
From: bielski.maciek at gmail.com (Maciej Bielski)
Date: Mon, 25 May 2015 01:37:52 +0200
Subject: [Slackbuilds-users] [afflib] SlackBuild bug
Message-ID: <556260D0.4070308@gmail.com>

Hi there,

I had problems during installation this library on x86_64.
It was linked with /usr/lib/libexpat.so instead of
/usr/lib64/libexpat.so. Similar with libstdc++. My quick solution was to
change SLKCFLAGS="-02 -fPIC" -> SLKCFLAGS="-02 -fPIC -L/usr/lib64" for
ARCH="x86_64".

link:
http://slackbuilds.org/repository/14.1/libraries/afflib/

Cheers,
Maciek

From willysr at slackbuilds.org  Mon May 25 00:36:48 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 25 May 2015 07:36:48 +0700
Subject: [Slackbuilds-users] [afflib] SlackBuild bug
In-Reply-To: <556260D0.4070308@gmail.com>
References: <556260D0.4070308@gmail.com>
Message-ID: <55626EA0.8060506@slackbuilds.org>

> I had problems during installation this library on x86_64.
> It was linked with /usr/lib/libexpat.so instead of
> /usr/lib64/libexpat.so. Similar with libstdc++. My quick solution was to
> change SLKCFLAGS="-02 -fPIC" -> SLKCFLAGS="-02 -fPIC -L/usr/lib64" for
> ARCH="x86_64".
> 
> link:
> http://slackbuilds.org/repository/14.1/libraries/afflib/

my guess is this system is running multilib?
http://slackbuilds.org/faq/#multilib

-- 
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/20150525/a98a42f6/attachment.asc>

From thomas at beingboiled.info  Mon May 25 01:49:16 2015
From: thomas at beingboiled.info (Thomas Morper)
Date: Mon, 25 May 2015 03:49:16 +0200 (CEST)
Subject: [Slackbuilds-users] Github file name issue
Message-ID: <alpine.LNX.2.11.1505250235050.13162@ks3357608.kimsufi.com>

Hello there,

A user of one of my SlackBuilds discovered an interesting problem:

If you follow the download link from the info file, pointing to a release 
on Github, you'll end up with different filenames depending on whether you 
use a browser or a tool like 'wget', thanks to a 'Content-Disposition' 
header. E.g.:

'Release' link on Github:
https://github.com/BlackIkeEagle/par2cmdline/archive/v0.6.11.tar.gz

As expected, wget will save the archive as 'v0.6.11.tar.gz'. However, 
Firefox will save it as 'par2cmdline-0.6.11.tar.gz', so anybody following 
the download link from the slackbuilds.org web site will get a non-working 
build. Most of the Github links I've checked behave this way.

What would be a good way to handle this? Editing the SlackBuild script to 
handle both names doesn't seem very desirable. Do we have to resort to 
self hosting?

-- 

From yalhcru at gmail.com  Mon May 25 02:35:10 2015
From: yalhcru at gmail.com (B Watson)
Date: Sun, 24 May 2015 22:35:10 -0400
Subject: [Slackbuilds-users] Github file name issue
In-Reply-To: <alpine.LNX.2.11.1505250235050.13162@ks3357608.kimsufi.com>
References: <alpine.LNX.2.11.1505250235050.13162@ks3357608.kimsufi.com>
Message-ID: <CAN1hMuDX8VRMFra1zjeBm5r75w-fmHOwJ-DWFSzoN59xwvxPag@mail.gmail.com>

On 5/24/15, Thomas Morper <thomas at beingboiled.info> wrote:


> What would be a good way to handle this? Editing the SlackBuild script to
> handle both names doesn't seem very desirable.

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

Desirable or not, a lot of builds do this now.

The only "broken build" problem you might get is from sbopkg,
which checks the source md5sum independently of the build itself.
It'd be nice if sbopkg could handle this more gracefully than it
does...

From pprkut at liwjatan.at  Mon May 25 08:43:34 2015
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Mon, 25 May 2015 10:43:34 +0200
Subject: [Slackbuilds-users] Github file name issue
In-Reply-To: <alpine.LNX.2.11.1505250235050.13162@ks3357608.kimsufi.com>
References: <alpine.LNX.2.11.1505250235050.13162@ks3357608.kimsufi.com>
Message-ID: <2110460.CDjtgMA5SS@titania>

On Monday 25 May 2015 03:49:16 Thomas Morper wrote:
> Hello there,
> 
> A user of one of my SlackBuilds discovered an interesting problem:
> 
> If you follow the download link from the info file, pointing to a release
> on Github, you'll end up with different filenames depending on whether you
> use a browser or a tool like 'wget', thanks to a 'Content-Disposition'
> header. E.g.:
> 
> 'Release' link on Github:
> https://github.com/BlackIkeEagle/par2cmdline/archive/v0.6.11.tar.gz
> 
> As expected, wget will save the archive as 'v0.6.11.tar.gz'. However,
> Firefox will save it as 'par2cmdline-0.6.11.tar.gz', so anybody following
> the download link from the slackbuilds.org web site will get a non-working
> build. Most of the Github links I've checked behave this way.
> 
> What would be a good way to handle this? Editing the SlackBuild script to
> handle both names doesn't seem very desirable. Do we have to resort to
> self hosting?

There is actually a download URL scheme that works better (IMHO, anyway), but 
it's not easily discoverable.

https://github.com/<user>/<project>/tarball/<tagname>/<tarballname>.tar.gz

In your case this would translate to

https://github.com/BlackIkeEagle/par2cmdline/tarball/v0.6.11/par2cmdline-0.6.11.tar.gz

The downside of this download is that the foldername inside the tarball differs 
with every version since it includes the git hash of the release tag.
Also, apparently this is using a github legacy API, so they might turn it off 
at some point, but for now it works fine for me.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150525/06324e43/attachment.asc>

From ryan.q at linux.com  Mon May 25 14:52:52 2015
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Mon, 25 May 2015 14:52:52 +0000
Subject: [Slackbuilds-users] Github file name issue
In-Reply-To: <2110460.CDjtgMA5SS@titania>
References: <alpine.LNX.2.11.1505250235050.13162@ks3357608.kimsufi.com>
 <2110460.CDjtgMA5SS@titania>
Message-ID: <CAAcyf-obh96rr1ZwOkfNZ4bGf4_rn+K6bMsv0D+P1asferO4kw@mail.gmail.com>

>tar xvf $PRGNAM-$VERSION.tar.gz || tar xvf v$VERSION.tar.gz

I use:

if [ -e $CWD/$VERSION.tar.gz ]; then
  tar xvf $CWD/$VERSION.tar.gz
else
  tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
fi

So that a 'no such file or directory' warning won't get displayed.

---

On Mon, May 25, 2015, 1:43 AM Heinz Wiesinger <pprkut at liwjatan.at> wrote:

> On Monday 25 May 2015 03:49:16 Thomas Morper wrote:
> > Hello there,
> >
> > A user of one of my SlackBuilds discovered an interesting problem:
> >
> > If you follow the download link from the info file, pointing to a release
> > on Github, you'll end up with different filenames depending on whether
> you
> > use a browser or a tool like 'wget', thanks to a 'Content-Disposition'
> > header. E.g.:
> >
> > 'Release' link on Github:
> > https://github.com/BlackIkeEagle/par2cmdline/archive/v0.6.11.tar.gz
> >
> > As expected, wget will save the archive as 'v0.6.11.tar.gz'. However,
> > Firefox will save it as 'par2cmdline-0.6.11.tar.gz', so anybody following
> > the download link from the slackbuilds.org web site will get a
> non-working
> > build. Most of the Github links I've checked behave this way.
> >
> > What would be a good way to handle this? Editing the SlackBuild script to
> > handle both names doesn't seem very desirable. Do we have to resort to
> > self hosting?
>
> There is actually a download URL scheme that works better (IMHO, anyway),
> but
> it's not easily discoverable.
>
> https://github.com/<user>/<project>/tarball/<tagname>/<tarballname>.tar.gz
>
> In your case this would translate to
>
>
> https://github.com/BlackIkeEagle/par2cmdline/tarball/v0.6.11/par2cmdline-0.6.11.tar.gz
>
> The downside of this download is that the foldername inside the tarball
> differs
> with every version since it includes the git hash of the release tag.
> Also, apparently this is using a github legacy API, so they might turn it
> off
> at some point, but for now it works fine for me.
>
> Grs,
> Heinz_______________________________________________
> 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/20150525/174e5b91/attachment-0001.html>

From baildon.research at googlemail.com  Mon May 25 20:44:46 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Mon, 25 May 2015 21:44:46 +0100
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <20150524145308.409d864f@stygian.lan>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
Message-ID: <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>

Ok, here is a roundup of what I'm seeing. I've tried to built the
whole of Heinz's list. In all cases the failure is the same on both
x86_64 and i686. If you need to know what deps and options I used,
you're welcome to ask, also there's a log of the i686 build at
http://pastebin.com/Cjizh8N4

(1) audio/audacity fails to build, I've not yet tried fixing it with
John V's solution but the patches look good with relation to the error
messages I see so I'll confirm that tomorrow.

(2) audio/mpd fails to build, again John V's upversion sounds like a
good plan so I'll confirm that tomorrow.

(3) games/alephone fails to build, once again John V has a fix!

(4) games/dolphin-emu fails to build, but the problem is independent
of ffmpeg (it was already broken before the update)

In file included from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:30:0,
                 from /usr/include/gtk-3.0/gdk/gdk.h:32,
                 from /usr/include/gtk-3.0/gtk/gtk.h:30,
                 from
/tmp/SBo/dolphin-4.0.2/Externals/wxWidgets3/src/aui/dockart.cpp:44:
/usr/include/gtk-3.0/gdk/gdktypes.h:127:39: error: conflicting
declaration 'typedef struct _GdkWindow GdkWindow'
 typedef struct _GdkWindow             GdkWindow;
                                       ^

(5) multimedia/bombono-dvd fails to build but here's John V has a fix
(yay!) so I'll confirm tomorrow

(6) multimedia/cinelerra fails to build, it's odd because I never
asked for x264 support?

qth264.c:9:18: fatal error: x264.h: No such file or directory
 #include "x264.h"

(7) multimedia/transcode fails to build. I think this is unrelated to
John V's patch. This is a strange problem, under 'optional package
support' it says
lame                           no
(which is correct), but then the build fails as below:

ERROR: option '--enable-lame' failed: cannot link against libmp3lame
libmp3lame can be found in the following packages:
  lame  http://www.mp3dev.org/

(8) multimedia/dvdrip and multimedia/mythtv cannot be built at the
moment due to dependency on transcode

(9) Random other things I noticed during this exercise:

* Can we reconsider ffmpeg's '_custom' ARCH suffix? AFAIK it's the
only such package anywhere, and it breaks slackpkgplus. (I can guess
the reaction to that question!)

* desktop/ffmpegthumbnailer/ffmpegthumbnailer.info on Heinz's branch
should have VERSION="2.0.10"

* network/imageshack-uploader has bad ownership 1000/users for lots of
stuff in the package

* system/ZoneMinder ships the unusual directory /tmp/zm/, I'm not
saying this is wrong, but it is unusual, but what *is* wrong are the
permissions on /tmp that it ships. Also, the doinst.sh calls both
'config etc/rc.d/rc.zm.new' and 'preserve_perms etc/rc.d/rc.zm.new' --
preserve_perms shows an error because etc/rc.d/rc.zm.new has already
been moved when it runs, the 'config' needs to be removed.

Hope this makes sense -- there should be more tomorrow
-D.

From philnx at posteo.de  Mon May 25 22:51:07 2015
From: philnx at posteo.de (Philip Lacroix)
Date: Tue, 26 May 2015 00:51:07 +0200
Subject: [Slackbuilds-users] Github file name issue
In-Reply-To: <CAAcyf-obh96rr1ZwOkfNZ4bGf4_rn+K6bMsv0D+P1asferO4kw@mail.gmail.com>
References: <alpine.LNX.2.11.1505250235050.13162@ks3357608.kimsufi.com>
 <2110460.CDjtgMA5SS@titania>
 <CAAcyf-obh96rr1ZwOkfNZ4bGf4_rn+K6bMsv0D+P1asferO4kw@mail.gmail.com>
Message-ID: <ee6f5c942976663b2f2753ce69fb603a@posteo.de>

Am 25.05.2015 16:52 schrieb Ryan P.C. McQuen:
> I use:
> 
> if [ -e $CWD/$VERSION.tar.gz ]; then
>   tar xvf $CWD/$VERSION.tar.gz
> else
>   tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
> fi
> 
> So that a 'no such file or directory' warning won't get displayed.

Yeah, that's exactly what I've been doing in my scripts as well, after I 
realized there was an issue with GitHub's file naming. :)

Cheers,
Philip

From willysr at slackbuilds.org  Tue May 26 00:42:27 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 26 May 2015 07:42:27 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
Message-ID: <5563C173.8050405@slackbuilds.org>

> (7) multimedia/transcode fails to build. I think this is unrelated to
> John V's patch. This is a strange problem, under 'optional package
> support' it says
> lame                           no
> (which is correct), but then the build fails as below:
> 
> ERROR: option '--enable-lame' failed: cannot link against libmp3lame
> libmp3lame can be found in the following packages:
>   lame  http://www.mp3dev.org/
> 
> (8) multimedia/dvdrip and multimedia/mythtv cannot be built at the
> moment due to dependency on transcode

Heinz has provide an update for transcode in his branch (github or SBo
server).
http://www.slackbuilds.org/cgit/slackbuilds/commit/?h=user/pprkut/ffmpeg&id=8c14c80c20bcf5280c0bcf8f64fc7aad56ed046e



-- 
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/20150526/d24e83d3/attachment.asc>

From willysr at slackbuilds.org  Tue May 26 01:23:14 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 26 May 2015 08:23:14 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
Message-ID: <5563CB02.9060001@slackbuilds.org>

> * network/imageshack-uploader has bad ownership 1000/users for lots of
> stuff in the package

Fixed it on my branch
please re-check


-- 
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/20150526/57e3438a/attachment.asc>

From willysr at slackbuilds.org  Tue May 26 01:31:32 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 26 May 2015 08:31:32 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
Message-ID: <5563CCF4.5040801@slackbuilds.org>

> * system/ZoneMinder ships the unusual directory /tmp/zm/, I'm not
> saying this is wrong, but it is unusual, but what *is* wrong are the
> permissions on /tmp that it ships. Also, the doinst.sh calls both
> 'config etc/rc.d/rc.zm.new' and 'preserve_perms etc/rc.d/rc.zm.new' --
> preserve_perms shows an error because etc/rc.d/rc.zm.new has already
> been moved when it runs, the 'config' needs to be removed.

I don't see any trace of /tmp/zm in the SlackBuild, so i guess it came
from the source itself. They need a temporary directory to hold the cctv
recordings and that's where it was placed. It should be configurable in
the configure script.

Anyway, i have fixed the doinst.sh duplicate entry


-- 
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/20150526/15f7b9e2/attachment.asc>

From chris.willing at iinet.net.au  Tue May 26 07:24:44 2015
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 26 May 2015 17:24:44 +1000
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <2641720.EPdaEcPPNf@titania>
References: <2641720.EPdaEcPPNf@titania>
Message-ID: <55641FBC.8040706@iinet.net.au>

Hi Heinz,

Since you're updating the SlackBuild, I wonder if you would consider a 
change to the way optional features are handled?

Unlike many other softwares, ffmpeg is quite good at detecting any 
necessary support packages needed to enable the various features. It 
assumes (and I believe this is a good assumption) that if all the 
conditions for a particular feature are present on the build machine, 
then that feature will be enabled unless it has been specifically 
disabled in the ./configure ... line.

At the moment many features are disabled in the SlackBuild by lines like:
libfrei0r=""; [ "${FREI0R:-no}" != "no" ] && libfrei0r="--enable-frei0r"

Would you consider removing all those lines so that all available 
features can be enabled rather than disabled? At the moment I have to 
edit the SlackBuild quite a bit, or have a very long (error prone) 
command line to re-enable all the features that should be included.

Those builders who don't want to include particular options, like freiOr 
for instance, would most likely not have it installed anyway so ffmpeg's 
own configuration system would not include it. In the more unlikely case 
that the build machine has freiOr installed but for some reason not 
wanted in the ffmpeg build, then that should be the time when the 
builder adds a --disable-freiOr option themselves.

I hope its not too radical a change - apart from being more convenient 
for me personally, I also think its more in line with the notion of 
leaving software as much as possible as the developers intended it to be.

chris

From yalhcru at gmail.com  Tue May 26 07:51:44 2015
From: yalhcru at gmail.com (B Watson)
Date: Tue, 26 May 2015 03:51:44 -0400
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <55641FBC.8040706@iinet.net.au>
References: <2641720.EPdaEcPPNf@titania>
	<55641FBC.8040706@iinet.net.au>
Message-ID: <CAN1hMuDLTMRrXRJWaLcxYEOR=N-E-j87nH=cjKVAWZTj86TQFQ@mail.gmail.com>

On 5/26/15, Christoph Willing <chris.willing at iinet.net.au> wrote:

> Would you consider removing all those lines so that all available
> features can be enabled rather than disabled? At the moment I have to
> edit the SlackBuild quite a bit, or have a very long (error prone)
> command line to re-enable all the features that should be included.

You don't have to edit the slackbuild, you can set them in the
environment.

That said, there are just too darned many environment variables. My
command to build ffmpeg with everything enabled (except pulseaudio!) ends
up looking like:

ASS=yes BLURAY=yes CELT=yes DC1394=yes FAAC=yes FREI0R=yes GSM=yes
IEC61883=yes ILBC=yes JP2=yes LADSPA=yes LAME=yes MODPLUG=yes
OPENAL=yes OPENCORE=yes OPENSSL=yes OPUS=yes RTMP=yes SCHROEDINGER=yes
SPEEX=yes TWOLAME=yes VPX=yes X264=yes XVID=yes sh ./ffmpeg.SlackBuild

Another thing about building ffmpeg: it uses texi2html to generate the
developer documentation, and chokes if it can't find it in the $PATH
(usually because the user did plain 'su' instead of 'su -', or because
the T series isn't installed). There's even extra code in there to check
for texi2html... And I'd estimate 99% of people running the build script
are never going to read the ffmpeg dev docs, because they're not writing
code that uses ffmpeg (they just need it for transcoding movies, or as a
dependency for something else).

Forcing people to jump through hoops to build documentation they're
never going to read is annoying, so I propose:

1. Add the tex directory to $PATH before checking for texi2html:
   export PATH=$PATH:/usr/share/texmf/bin

2. If texi2html still isn't found, add --disable-doc to the
   ./configure command.

3. Maybe have the slack-desc include a line reflecting whether the
   docs are included, 'This package was built (with|without) developer
   docs'.

Upstream already provides the --disable-doc option, so it's not really
a case of gratuitously changing things.

From chris.willing at iinet.net.au  Tue May 26 08:21:59 2015
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 26 May 2015 18:21:59 +1000
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAN1hMuDLTMRrXRJWaLcxYEOR=N-E-j87nH=cjKVAWZTj86TQFQ@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania>	<55641FBC.8040706@iinet.net.au>
 <CAN1hMuDLTMRrXRJWaLcxYEOR=N-E-j87nH=cjKVAWZTj86TQFQ@mail.gmail.com>
Message-ID: <55642D27.7050502@iinet.net.au>



On 26/05/15 17:51, B Watson wrote:
> On 5/26/15, Christoph Willing <chris.willing at iinet.net.au> wrote:
>
>> Would you consider removing all those lines so that all available
>> features can be enabled rather than disabled? At the moment I have to
>> edit the SlackBuild quite a bit, or have a very long (error prone)
>> command line to re-enable all the features that should be included.
>
> You don't have to edit the slackbuild, you can set them in the
> environment.
>
> That said, there are just too darned many environment variables. My
> command to build ffmpeg with everything enabled (except pulseaudio!) ends
> up looking like:
>
> ASS=yes BLURAY=yes CELT=yes DC1394=yes FAAC=yes FREI0R=yes GSM=yes
> IEC61883=yes ILBC=yes JP2=yes LADSPA=yes LAME=yes MODPLUG=yes
> OPENAL=yes OPENCORE=yes OPENSSL=yes OPUS=yes RTMP=yes SCHROEDINGER=yes
> SPEEX=yes TWOLAME=yes VPX=yes X264=yes XVID=yes sh ./ffmpeg.SlackBuild

Yes, that's what I meant about a very long, error prone, command line.

chris

>
> Another thing about building ffmpeg: it uses texi2html to generate the
> developer documentation, and chokes if it can't find it in the $PATH
> (usually because the user did plain 'su' instead of 'su -', or because
> the T series isn't installed). There's even extra code in there to check
> for texi2html... And I'd estimate 99% of people running the build script
> are never going to read the ffmpeg dev docs, because they're not writing
> code that uses ffmpeg (they just need it for transcoding movies, or as a
> dependency for something else).
>
> Forcing people to jump through hoops to build documentation they're
> never going to read is annoying, so I propose:
>
> 1. Add the tex directory to $PATH before checking for texi2html:
>     export PATH=$PATH:/usr/share/texmf/bin
>
> 2. If texi2html still isn't found, add --disable-doc to the
>     ./configure command.
>
> 3. Maybe have the slack-desc include a line reflecting whether the
>     docs are included, 'This package was built (with|without) developer
>     docs'.
>
> Upstream already provides the --disable-doc option, so it's not really
> a case of gratuitously changing things.
> _______________________________________________
> 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 dickson.tim at googlemail.com  Tue May 26 09:22:42 2015
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Tue, 26 May 2015 10:22:42 +0100
Subject: [Slackbuilds-users] fglrx slackbuild
Message-ID: <55643B62.6080200@googlemail.com>

I am working on a fglrx (amd/ati proprietary driver) package.
I am unsure as to what version number to use as the drivers have more 
than one name.
the downloadable driver is amd catalyst omega driver 14.12
but the linux driver inside is the fglrx 14.501.1003
I think I should call the package fglrx but I am leaning towards the 
14.12 for the version number to use.

Is there any sbo policy for such cases?

When I get it (the package) done, I would also appreciate some testing 
from other sbo users with real current ati hardware. The down-side of 
testing is needing real graphics hardware, so virtual machines can't be 
used. I will have tested it on a dual boot pc with A4 6300 apu at my 
place, but it is very time consuming so help testing would be appreciated.
regards, Tim

From chris.willing at iinet.net.au  Tue May 26 10:06:13 2015
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 26 May 2015 20:06:13 +1000
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <55641FBC.8040706@iinet.net.au>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
Message-ID: <55644595.5010308@iinet.net.au>



On 26/05/15 17:24, Christoph Willing wrote:
> Hi Heinz,
>
> Since you're updating the SlackBuild, I wonder if you would consider a
> change to the way optional features are handled?
>
> Unlike many other softwares, ffmpeg is quite good at detecting any
> necessary support packages needed to enable the various features. It
> assumes (and I believe this is a good assumption) that if all the
> conditions for a particular feature are present on the build machine,
> then that feature will be enabled unless it has been specifically
> disabled in the ./configure ... line.
>
> At the moment many features are disabled in the SlackBuild by lines like:
> libfrei0r=""; [ "${FREI0R:-no}" != "no" ] && libfrei0r="--enable-frei0r"
>
> Would you consider removing all those lines so that all available
> features can be enabled rather than disabled? At the moment I have to
> edit the SlackBuild quite a bit, or have a very long (error prone)
> command line to re-enable all the features that should be included.
>

I'm sorry, that's actually a dopey request. I've had my version edited 
for so long (to set all those options to "yes") that I thought it would 
be good just to remove all the option setting code without realising 
that these are options that ffmpeg does _not_ detect automagically.

Therefore, could I request instead that those options default to "yes"? 
It would also need the relevant packages names added to the .info file.

chris

From ozan.turkyilmaz at gmail.com  Tue May 26 10:13:23 2015
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 26 May 2015 15:13:23 +0500
Subject: [Slackbuilds-users] Alsa-Plugins
Message-ID: <CA+da1orMLFa6xiVZwBoV3QwBsbBma27mKHoQ9GsqGVPnNh-0zw@mail.gmail.com>

Hello All,

I had complains about alsa-plugings not complying with speex 1.2rc2. I
tried it on my system (clean system. Recently installed) and it
complies. Anyone has any problems with complying alsa-plugings.

PS: I has 64 bit system and no multilib.

-- 
Ozan, BSc, BEng

From matteo.bernardini at gmail.com  Tue May 26 10:30:13 2015
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 26 May 2015 12:30:13 +0200
Subject: [Slackbuilds-users] Alsa-Plugins
In-Reply-To: <CA+da1orMLFa6xiVZwBoV3QwBsbBma27mKHoQ9GsqGVPnNh-0zw@mail.gmail.com>
References: <CA+da1orMLFa6xiVZwBoV3QwBsbBma27mKHoQ9GsqGVPnNh-0zw@mail.gmail.com>
Message-ID: <CAPsDuS7auKPx2YHyGkceDuNEP5CperfzsxyPkSMqcqh-CLyqeA@mail.gmail.com>

2015-05-26 12:13 GMT+02:00 Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>:
> Hello All,
>
> I had complains about alsa-plugings not complying with speex 1.2rc2. I
> tried it on my system (clean system. Recently installed) and it
> complies. Anyone has any problems with complying alsa-plugings.

building alsa-plugins works fine with the latest version of the speex
build script in our repository: there was a bug in latest speex
version but I should have fixed it

https://www.linuxquestions.org/questions/slackware-14/that-which-could-be-fixed-in-sbo-thread-4175532869/page3.html#post5362337

http://slackbuilds.org/cgit/slackbuilds/commit/?id=cc20a4724230dbd2af69b4acbe1e19b64cfe70df

Matteo

From hba.nihilismus at gmail.com  Tue May 26 13:18:29 2015
From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=)
Date: Tue, 26 May 2015 08:18:29 -0500
Subject: [Slackbuilds-users] Alsa-Plugins
In-Reply-To: <CAPsDuS7auKPx2YHyGkceDuNEP5CperfzsxyPkSMqcqh-CLyqeA@mail.gmail.com>
References: <CA+da1orMLFa6xiVZwBoV3QwBsbBma27mKHoQ9GsqGVPnNh-0zw@mail.gmail.com>
 <CAPsDuS7auKPx2YHyGkceDuNEP5CperfzsxyPkSMqcqh-CLyqeA@mail.gmail.com>
Message-ID: <CAJx2MoGbeRcKMMm+YaL9FbSbKDGzjPMKMVXps3RWxOLU6-oyFQ@mail.gmail.com>

To fix it i added '-DHAVE_STDINT_H' to CFLAGS.

alsa-plugins.SlackBuild:
...
CFLAGS="$SLKCFLAGS -DHAVE_STDINT_H" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
  --prefix=/usr \
  --libdir=/usr/lib${LIBDIRSUFFIX} \
...

- Cheers


On Tue, May 26, 2015 at 5:30 AM, Matteo Bernardini <
matteo.bernardini at gmail.com> wrote:

> 2015-05-26 12:13 GMT+02:00 Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>:
> > Hello All,
> >
> > I had complains about alsa-plugings not complying with speex 1.2rc2. I
> > tried it on my system (clean system. Recently installed) and it
> > complies. Anyone has any problems with complying alsa-plugings.
>
> building alsa-plugins works fine with the latest version of the speex
> build script in our repository: there was a bug in latest speex
> version but I should have fixed it
>
>
> https://www.linuxquestions.org/questions/slackware-14/that-which-could-be-fixed-in-sbo-thread-4175532869/page3.html#post5362337
>
>
> http://slackbuilds.org/cgit/slackbuilds/commit/?id=cc20a4724230dbd2af69b4acbe1e19b64cfe70df
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>


-- 
Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx.
https://github.com/nihilismus | https://bitbucket.org/nihilismus |
https://twitter.com/nihilipster
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150526/7140bde8/attachment.html>

From matteo.bernardini at gmail.com  Tue May 26 13:38:49 2015
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Tue, 26 May 2015 15:38:49 +0200
Subject: [Slackbuilds-users] Alsa-Plugins
In-Reply-To: <CAJx2MoGbeRcKMMm+YaL9FbSbKDGzjPMKMVXps3RWxOLU6-oyFQ@mail.gmail.com>
References: <CA+da1orMLFa6xiVZwBoV3QwBsbBma27mKHoQ9GsqGVPnNh-0zw@mail.gmail.com>
 <CAPsDuS7auKPx2YHyGkceDuNEP5CperfzsxyPkSMqcqh-CLyqeA@mail.gmail.com>
 <CAJx2MoGbeRcKMMm+YaL9FbSbKDGzjPMKMVXps3RWxOLU6-oyFQ@mail.gmail.com>
Message-ID: <CAPsDuS5uBEpxLpHLuBiZNHgxVeVkXTt1_wHADWdnOMtFQiB8Lw@mail.gmail.com>

2015-05-26 15:18 GMT+02:00 Antonio Hern?ndez Blas <hba.nihilismus at gmail.com>:
> To fix it i added '-DHAVE_STDINT_H' to CFLAGS.
>
> alsa-plugins.SlackBuild:
> ...
> CFLAGS="$SLKCFLAGS -DHAVE_STDINT_H" \
> CXXFLAGS="$SLKCFLAGS" \
> ./configure \
>   --prefix=/usr \
>   --libdir=/usr/lib${LIBDIRSUFFIX} \
> ...

do you mean you needed that with the latest version of speex?

Matteo

From hba.nihilismus at gmail.com  Tue May 26 14:23:18 2015
From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=)
Date: Tue, 26 May 2015 09:23:18 -0500
Subject: [Slackbuilds-users] Alsa-Plugins
In-Reply-To: <CAPsDuS5uBEpxLpHLuBiZNHgxVeVkXTt1_wHADWdnOMtFQiB8Lw@mail.gmail.com>
References: <CA+da1orMLFa6xiVZwBoV3QwBsbBma27mKHoQ9GsqGVPnNh-0zw@mail.gmail.com>
 <CAPsDuS7auKPx2YHyGkceDuNEP5CperfzsxyPkSMqcqh-CLyqeA@mail.gmail.com>
 <CAJx2MoGbeRcKMMm+YaL9FbSbKDGzjPMKMVXps3RWxOLU6-oyFQ@mail.gmail.com>
 <CAPsDuS5uBEpxLpHLuBiZNHgxVeVkXTt1_wHADWdnOMtFQiB8Lw@mail.gmail.com>
Message-ID: <CAJx2MoGxQ2-nSU89G30PscybaKBJufS3PDFVRaOY-twDwjA_mg@mail.gmail.com>

No, but with speex-1.2rc2-x86_64-3 i fixed it in this way without the need
for a patch.

On Tue, May 26, 2015 at 8:38 AM, Matteo Bernardini <
matteo.bernardini at gmail.com> wrote:

> 2015-05-26 15:18 GMT+02:00 Antonio Hern?ndez Blas <
> hba.nihilismus at gmail.com>:
> > To fix it i added '-DHAVE_STDINT_H' to CFLAGS.
> >
> > alsa-plugins.SlackBuild:
> > ...
> > CFLAGS="$SLKCFLAGS -DHAVE_STDINT_H" \
> > CXXFLAGS="$SLKCFLAGS" \
> > ./configure \
> >   --prefix=/usr \
> >   --libdir=/usr/lib${LIBDIRSUFFIX} \
> > ...
>
> do you mean you needed that with the latest version of speex?
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>


-- 
Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx.
https://github.com/nihilismus | https://bitbucket.org/nihilismus |
https://twitter.com/nihilipster
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150526/9f247dc1/attachment-0001.html>

From baildon.research at googlemail.com  Tue May 26 14:35:20 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Tue, 26 May 2015 15:35:20 +0100
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <5563C173.8050405@slackbuilds.org>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
 <5563C173.8050405@slackbuilds.org>
Message-ID: <CAMt7G9QzrfccqWfQPFQdvvpDc-B7qtg+tN3SGs4BK1WtViQ-Ng@mail.gmail.com>

On 26 May 2015 at 01:42, Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:
>> (7) multimedia/transcode fails to build. I think this is unrelated to
>> John V's patch. This is a strange problem, under 'optional package
>> support' it says
>> lame                           no
>> (which is correct), but then the build fails as below:
>>
>> ERROR: option '--enable-lame' failed: cannot link against libmp3lame
>> libmp3lame can be found in the following packages:
>>   lame  http://www.mp3dev.org/
>>
>> (8) multimedia/dvdrip and multimedia/mythtv cannot be built at the
>> moment due to dependency on transcode
>
> Heinz has provide an update for transcode in his branch (github or SBo
> server).
> http://www.slackbuilds.org/cgit/slackbuilds/commit/?h=user/pprkut/ffmpeg&id=8c14c80c20bcf5280c0bcf8f64fc7aad56ed046e

Yes, but it failed for me *with* that commit -- I rebased on the
latest public SBo Sunday May 24 before starting to test the new ffmpeg
:-(

Best regards
-D.

From baildon.research at googlemail.com  Tue May 26 14:38:09 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Tue, 26 May 2015 15:38:09 +0100
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <5563CCF4.5040801@slackbuilds.org>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
 <5563CCF4.5040801@slackbuilds.org>
Message-ID: <CAMt7G9Qp07p-s=E9hGWG3pqDKifof6CniednRVa1PC6DYfsqaQ@mail.gmail.com>

> I don't see any trace of /tmp/zm in the SlackBuild, so i guess it came
> from the source itself. They need a temporary directory to hold the cctv
> recordings and that's where it was placed. It should be configurable in
> the configure script.
>
> Anyway, i have fixed the doinst.sh duplicate entry

Thanks, but what about the problem where it breaks the permissions on /tmp?

morticia# ls -ald /tmp/
drwxrwxrwt 25 root root 20480 May 26 15:23 /tmp/
morticia# installpkg
/SBo/14.1/packages/14.1/x86_64/system/ZoneMinder/ZoneMinder-1.27.0-x86_64-2_SBo.txz
Verifying package ZoneMinder-1.27.0-x86_64-2_SBo.txz.
Installing package ZoneMinder-1.27.0-x86_64-2_SBo.txz:
PACKAGE DESCRIPTION:
# ZoneMinder (Linux video camera security and surveillance solution)
#
# This suite is intended for use in single or multi-camera video
# security applications, commercial or home CCTV. It supports capture,
# analysis, recording, and monitoring of video data. PTZ cameras can
# be controlled via web or semi-automatically using a variety of
# protocols. It can also be integrated into a home automation system
# via X.10 or other protocols. This build includes cambozola and
# jscalendar.
#
# Homepage:  http://www.zoneminder.com/
Executing install script for ZoneMinder-1.27.0-x86_64-2_SBo.txz.
cat: etc/rc.d/rc.zm.new: No such file or directory

   If this is a new installation, you will need to create a MySQL database
   for ZoneMinder to use. See /usr/doc/ZoneMinder-<version>/README.SLACKWARE

   If you are upgrading, you will need to run the zmupdate.pl script:
   /usr/bin/zmupdate.pl version=<from version>
[--user=<my_database_user> --pass=<my_database_pass>]

Package ZoneMinder-1.27.0-x86_64-2_SBo.txz installed.

morticia# ls -ald /tmp/
drwxr-xr-x 26 root root 20480 May 24 21:56 /tmp/
morticia#

:-(
-D.

From willysr at slackbuilds.org  Tue May 26 14:40:00 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 26 May 2015 21:40:00 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAMt7G9QzrfccqWfQPFQdvvpDc-B7qtg+tN3SGs4BK1WtViQ-Ng@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
 <5563C173.8050405@slackbuilds.org>
 <CAMt7G9QzrfccqWfQPFQdvvpDc-B7qtg+tN3SGs4BK1WtViQ-Ng@mail.gmail.com>
Message-ID: <556485C0.3050304@slackbuilds.org>

> Yes, but it failed for me *with* that commit -- I rebased on the
> latest public SBo Sunday May 24 before starting to test the new ffmpeg

Strange
it built fine here
i have transcode-1.1.7-i486-4_SBo


-- 
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/20150526/875265e4/attachment.asc>

From willysr at slackbuilds.org  Tue May 26 14:44:21 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 26 May 2015 21:44:21 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAMt7G9Qp07p-s=E9hGWG3pqDKifof6CniednRVa1PC6DYfsqaQ@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
 <5563CCF4.5040801@slackbuilds.org>
 <CAMt7G9Qp07p-s=E9hGWG3pqDKifof6CniednRVa1PC6DYfsqaQ@mail.gmail.com>
Message-ID: <556486C5.7040303@slackbuilds.org>


> Thanks, but what about the problem where it breaks the permissions on /tmp?
> 
> morticia# ls -ald /tmp/
> drwxrwxrwt 25 root root 20480 May 26 15:23 /tmp/
> morticia# installpkg
> /SBo/14.1/packages/14.1/x86_64/system/ZoneMinder/ZoneMinder-1.27.0-x86_64-2_SBo.txz
> Verifying package ZoneMinder-1.27.0-x86_64-2_SBo.txz.
> Installing package ZoneMinder-1.27.0-x86_64-2_SBo.txz:
> PACKAGE DESCRIPTION:
> # ZoneMinder (Linux video camera security and surveillance solution)
> #
> # This suite is intended for use in single or multi-camera video
> # security applications, commercial or home CCTV. It supports capture,
> # analysis, recording, and monitoring of video data. PTZ cameras can
> # be controlled via web or semi-automatically using a variety of
> # protocols. It can also be integrated into a home automation system
> # via X.10 or other protocols. This build includes cambozola and
> # jscalendar.
> #
> # Homepage:  http://www.zoneminder.com/
> Executing install script for ZoneMinder-1.27.0-x86_64-2_SBo.txz.
> cat: etc/rc.d/rc.zm.new: No such file or directory
> 
>    If this is a new installation, you will need to create a MySQL database
>    for ZoneMinder to use. See /usr/doc/ZoneMinder-<version>/README.SLACKWARE
> 
>    If you are upgrading, you will need to run the zmupdate.pl script:
>    /usr/bin/zmupdate.pl version=<from version>
> [--user=<my_database_user> --pass=<my_database_pass>]
> 
> Package ZoneMinder-1.27.0-x86_64-2_SBo.txz installed.
> 
> morticia# ls -ald /tmp/
> drwxr-xr-x 26 root root 20480 May 24 21:56 /tmp/
> morticia#

I'm not sure about that one
i saw ARCH has switched to cmake instead of the old configure script to
build ZoneMinder

let me try building it again

-- 
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/20150526/ab0dd90e/attachment.asc>

From willysr at slackbuilds.org  Tue May 26 14:56:59 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 26 May 2015 21:56:59 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAMt7G9Qp07p-s=E9hGWG3pqDKifof6CniednRVa1PC6DYfsqaQ@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
 <5563CCF4.5040801@slackbuilds.org>
 <CAMt7G9Qp07p-s=E9hGWG3pqDKifof6CniednRVa1PC6DYfsqaQ@mail.gmail.com>
Message-ID: <556489BB.9090707@slackbuilds.org>

> Thanks, but what about the problem where it breaks the permissions on /tmp?
> 
> morticia# ls -ald /tmp/
> drwxrwxrwt 25 root root 20480 May 26 15:23 /tmp/

here on my VM it gave different results
ls -l /tmp
drwx------   2 apache  apache     4096 May 26 21:48 zm/

-- 
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/20150526/8de90cb1/attachment.asc>

From leva at ecentrum.hu  Wed May 27 07:26:11 2015
From: leva at ecentrum.hu (=?iso-8859-1?Q?L=C9VAI_D=E1niel?=)
Date: Wed, 27 May 2015 09:26:11 +0200
Subject: [Slackbuilds-users] remove spectrwm from ready
Message-ID: <20150527072611.GA20596@serenity.local>

Hi!

Would you guys be so kind as to revert the 2.7.1 update for spectrwm?
They fixed a pretty annoying issue in 2.7.2 -- the Modkey didn't work
with NumLock turned on.

I'll upload the new slackbuild for 2.7.2.

Thanks!

Daniel

-- 
L?VAI D?niel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D  650C C69B BE4C 83B6 3A8F

From willysr at slackbuilds.org  Wed May 27 09:08:14 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 27 May 2015 16:08:14 +0700
Subject: [Slackbuilds-users] remove spectrwm from ready
In-Reply-To: <20150527072611.GA20596@serenity.local>
References: <20150527072611.GA20596@serenity.local>
Message-ID: <5565897E.5090803@slackbuilds.org>

> Would you guys be so kind as to revert the 2.7.1 update for spectrwm?
> They fixed a pretty annoying issue in 2.7.2 -- the Modkey didn't work
> with NumLock turned on.
> 
> I'll upload the new slackbuild for 2.7.2.

Done
you can resubmit 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/20150527/ff3ce90f/attachment.asc>

From leva at ecentrum.hu  Wed May 27 11:56:46 2015
From: leva at ecentrum.hu (=?iso-8859-1?Q?L=C9VAI_D=E1niel?=)
Date: Wed, 27 May 2015 13:56:46 +0200
Subject: [Slackbuilds-users] remove spectrwm from ready
In-Reply-To: <5565897E.5090803@slackbuilds.org>
References: <20150527072611.GA20596@serenity.local>
 <5565897E.5090803@slackbuilds.org>
Message-ID: <20150527115645.GA30760@serenity.local>

On sze, m?j 27, 2015 at 16:08:14 +0700, Willy Sudiarto Raharjo wrote:
> > Would you guys be so kind as to revert the 2.7.1 update for spectrwm?
> > They fixed a pretty annoying issue in 2.7.2 -- the Modkey didn't work
> > with NumLock turned on.
> > 
> > I'll upload the new slackbuild for 2.7.2.
> 
> Done
> you can resubmit now

Thanks man!

From klaatu at straightedgelinux.com  Thu May 28 04:56:55 2015
From: klaatu at straightedgelinux.com (Klaatu)
Date: Thu, 28 May 2015 16:56:55 +1200
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
Message-ID: <5566A017.1000601@straightedgelinux.com>

Fellow SBo maintainers:

I have noticed that one of my own scripts depends on JACK, and that I
myself had listed the dependency as "jack-audio-connection-kit".

Then I realised that this listing is not quite correct, because in fact
ANY package that depends upon "JACK" actually depends on EITHER JACK
version 1 or JACK version 2.


On SBo, we currently have JACK v1 as: jack-audio-connection-kit
and JACK v2 as: jack2

So my question for myself and others is:

Should we normalise how we list a JACK dependency? it is definitely
incorrect to list "jack-audio-connection-kit" as the only package that
will resolve a JACK dependency, because "jack2" will do just as well.


Two solutions I can think of are:

1. list both jack;audio-connection-kit and jack2 in the README file if
your package requires JACK

or...

2. re-structure the jack-audio-connection-kit and jack2 scripts such
that they become one and the same script, by which the user can choose
to build either jack1 or jack2, depending on their requirements. This
solution would obviously require agreement between the maintainers of
those scripts.


For more information on this issue, please see:
https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2


Cheers-

klaatu

From yalhcru at gmail.com  Thu May 28 06:54:34 2015
From: yalhcru at gmail.com (B Watson)
Date: Thu, 28 May 2015 02:54:34 -0400
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <5566A017.1000601@straightedgelinux.com>
References: <5566A017.1000601@straightedgelinux.com>
Message-ID: <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>

On 5/28/15, Klaatu <klaatu at straightedgelinux.com> wrote:

> 1. list both jack;audio-connection-kit and jack2 in the README file if
> your package requires JACK

Kinda annoying if neither one is in REQUIRES in the .info file, it would
break sbotools or sqg's queue building.

> 2. re-structure the jack-audio-connection-kit and jack2 scripts such
> that they become one and the same script, by which the user can choose
> to build either jack1 or jack2, depending on their requirements. This
> solution would obviously require agreement between the maintainers of
> those scripts.

I vote for this, if we're voting. Though it means extra work for whoever
ends up maintaining the merged script.

From marc at mos6581.de  Thu May 28 08:11:11 2015
From: marc at mos6581.de (Marcel Saegebarth)
Date: Thu, 28 May 2015 10:11:11 +0200
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <5566A017.1000601@straightedgelinux.com>
References: <5566A017.1000601@straightedgelinux.com>
Message-ID: <5566CD9F.5050502@mos6581.de>

On 05/28/2015 06:56 AM, Klaatu wrote:

> 1. list both jack;audio-connection-kit and jack2 in the README file if
> your package requires JACK
> 
> or...
> 
> 2. re-structure the jack-audio-connection-kit and jack2 scripts such
> that they become one and the same script, by which the user can choose
> to build either jack1 or jack2, depending on their requirements. This
> solution would obviously require agreement between the maintainers of
> those scripts.

IMHO I don't see a reason to merge both into one SlackBuild.
I would say that JACK users are well aware that two versions exist and
this is also a decision from the upstream maintainers and those who
don't use JACK won't use it as it is may just a hard dependency from the
maintainer.
Also, both versions quite differ on some situations as you've stated
with the link to the JACK FAQ. It's not just a question of
dependencies.

-------------- 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/20150528/7b55d836/attachment.asc>

From baildon.research at googlemail.com  Thu May 28 08:14:20 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 28 May 2015 09:14:20 +0100
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <5566A017.1000601@straightedgelinux.com>
References: <5566A017.1000601@straightedgelinux.com>
Message-ID: <CAMt7G9THgSeBs9hHH9vdU4DFfE2PAg+C9h2hd0ZbneUJ6ygfsQ@mail.gmail.com>

> 2. re-structure the jack-audio-connection-kit and jack2 scripts such
> that they become one and the same script, by which the user can choose
> to build either jack1 or jack2, depending on their requirements.

What would be in DOWNLOAD= and VERSION=?

-D.

From klaatu at straightedgelinux.com  Thu May 28 10:05:51 2015
From: klaatu at straightedgelinux.com (Klaatu)
Date: Thu, 28 May 2015 22:05:51 +1200
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <CAMt7G9THgSeBs9hHH9vdU4DFfE2PAg+C9h2hd0ZbneUJ6ygfsQ@mail.gmail.com>
References: <5566A017.1000601@straightedgelinux.com>
 <CAMt7G9THgSeBs9hHH9vdU4DFfE2PAg+C9h2hd0ZbneUJ6ygfsQ@mail.gmail.com>
Message-ID: <5566E87F.4010804@straightedgelinux.com>

On 05/28/2015 08:14 PM, David Spencer wrote:
>> 2. re-structure the jack-audio-connection-kit and jack2 scripts such
>> that they become one and the same script, by which the user can choose
>> to build either jack1 or jack2, depending on their requirements.
> 
> What would be in DOWNLOAD= and VERSION=?
> 
> -D.

Oh, duh. You're right. I guess that wouldn't work.

-klaatu


From klaatu at straightedgelinux.com  Thu May 28 10:08:11 2015
From: klaatu at straightedgelinux.com (Klaatu)
Date: Thu, 28 May 2015 22:08:11 +1200
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <5566CD9F.5050502@mos6581.de>
References: <5566A017.1000601@straightedgelinux.com>
 <5566CD9F.5050502@mos6581.de>
Message-ID: <5566E90B.5020506@straightedgelinux.com>

> IMHO I don't see a reason to merge both into one SlackBuild.
> I would say that JACK users are well aware that two versions exist and
> this is also a decision from the upstream maintainers and those who
> don't use JACK won't use it as it is may just a hard dependency from the
> maintainer.
> Also, both versions quite differ on some situations as you've stated
> with the link to the JACK FAQ. It's not just a question of
> dependencies.
> 


I agree, and as David Spencer pointed out, that would not really work,
since the DOWNLOAD= links in .info are not conditional.

My concern really is that if a script claims to depend on jack1, that's
not correct, because it actually depends on either jack1 or jack2.


-klaatu

From klaatu at straightedgelinux.com  Thu May 28 10:15:22 2015
From: klaatu at straightedgelinux.com (Klaatu)
Date: Thu, 28 May 2015 22:15:22 +1200
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
References: <5566A017.1000601@straightedgelinux.com>
 <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
Message-ID: <5566EABA.2070402@straightedgelinux.com>

On 05/28/2015 06:54 PM, B Watson wrote:
> On 5/28/15, Klaatu <klaatu at straightedgelinux.com> wrote:
> 
>> 1. list both jack;audio-connection-kit and jack2 in the README file if
>> your package requires JACK
> 
> Kinda annoying if neither one is in REQUIRES in the .info file, it would
> break sbotools or sqg's queue building.
> 

Yes, and I guess that's what the %README% placeholder is for.

I think it could be argued that as long as there is a mention, something
to the effect of "This package will also build and function with jack2"
in the README file, that's more or less fair warning for the
semi-experienced JACK user.

I think in the future, I'll use %README% in REQUIRES to alert the user
that the version of JACK is optional.

- klaatu

From charles at charlesmatkinson.org  Thu May 28 07:27:54 2015
From: charles at charlesmatkinson.org (Charles)
Date: Thu, 28 May 2015 12:57:54 +0530
Subject: [Slackbuilds-users] Anybody want xapian-omega and yad?
Message-ID: <5566C37A.10907@charlesmatkinson.org>

With regret, voluntary work as a Debian and (cough) Ubuntu sysadmin
leaves me no time to update the xapian-omega and yad SlackBuilds :(

I am un-subscribing from this list so please address any mail to me
directly.

Best

Charles

From matteo.bernardini at gmail.com  Thu May 28 12:20:49 2015
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 28 May 2015 14:20:49 +0200
Subject: [Slackbuilds-users] Anybody want xapian-omega and yad?
In-Reply-To: <5566C37A.10907@charlesmatkinson.org>
References: <5566C37A.10907@charlesmatkinson.org>
Message-ID: <CAPsDuS4X-usWBqVuBbttXTNpdVceCJh55B1w=Dq_tNEN4SqXWg@mail.gmail.com>

2015-05-28 9:27 GMT+02:00 Charles <charles at charlesmatkinson.org>:
> With regret, voluntary work as a Debian and (cough) Ubuntu sysadmin
> leaves me no time to update the xapian-omega and yad SlackBuilds :(

I'll take yad, if nobody want it *badly*

Matteo

From willysr at slackbuilds.org  Thu May 28 12:20:57 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 28 May 2015 19:20:57 +0700
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <5566EABA.2070402@straightedgelinux.com>
References: <5566A017.1000601@straightedgelinux.com>
 <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
 <5566EABA.2070402@straightedgelinux.com>
Message-ID: <55670829.3080804@slackbuilds.org>

> I think in the future, I'll use %README% in REQUIRES to alert the user
> that the version of JACK is optional.

%README% is used to tell users that a package is conflicting/replacing
Slackware packages. Other than that, users are always assumed to read
README.


-- 
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/20150528/71e64524/attachment.asc>

From elyb at ioplasm.net  Thu May 28 13:11:43 2015
From: elyb at ioplasm.net (Brad Ely)
Date: Thu, 28 May 2015 09:11:43 -0400
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <5566E87F.4010804@straightedgelinux.com>
References: <5566A017.1000601@straightedgelinux.com>
 <CAMt7G9THgSeBs9hHH9vdU4DFfE2PAg+C9h2hd0ZbneUJ6ygfsQ@mail.gmail.com>
 <5566E87F.4010804@straightedgelinux.com>
Message-ID: <20150528091143.56823439.elyb@ioplasm.net>

On Thu, 28 May 2015 22:05:51 +1200
Klaatu <klaatu at straightedgelinux.com> wrote:

> On 05/28/2015 08:14 PM, David Spencer wrote:
> >> 2. re-structure the jack-audio-connection-kit and jack2 scripts
> >> such that they become one and the same script, by which the user
> >> can choose to build either jack1 or jack2, depending on their
> >> requirements.
> > 
> > What would be in DOWNLOAD= and VERSION=?
> > 
> > -D.
> 
> Oh, duh. You're right. I guess that wouldn't work.
> 
> -klaatu

Just thinking out loud...  You could have the separate scripts for jack1
and jack2 with their associated .info files set up as dependencies of
a jack-common (or whatever) build script which requires an argument to
select the version desired.  Perhaps build information could be passed
via environment variables?

-- 
Brad Ely

From baildon.research at googlemail.com  Thu May 28 13:17:57 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 28 May 2015 14:17:57 +0100
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <20150528091143.56823439.elyb@ioplasm.net>
References: <5566A017.1000601@straightedgelinux.com>
 <CAMt7G9THgSeBs9hHH9vdU4DFfE2PAg+C9h2hd0ZbneUJ6ygfsQ@mail.gmail.com>
 <5566E87F.4010804@straightedgelinux.com>
 <20150528091143.56823439.elyb@ioplasm.net>
Message-ID: <CAMt7G9QeXSKFmJWbS-mhgjoiQCeR1YSY_9vEsMzkS8M130uXAw@mail.gmail.com>

> Just thinking out loud...  You could have the separate scripts for jack1
> and jack2 with their associated .info files set up as dependencies of
> a jack-common (or whatever) build script which requires an argument to
> select the version desired.  Perhaps build information could be passed
> via environment variables?

Well, you just reinvented virtual packages or metapackages as found in
all the dependency hell distros... do we want to go there?

-D.

From klaatu at straightedgelinux.com  Thu May 28 13:55:44 2015
From: klaatu at straightedgelinux.com (Klaatu)
Date: Fri, 29 May 2015 01:55:44 +1200
Subject: [Slackbuilds-users] README [fork of Re: jack-audio-connection-kit
 vs jack2]
In-Reply-To: <55670829.3080804@slackbuilds.org>
References: <5566A017.1000601@straightedgelinux.com>
 <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
 <5566EABA.2070402@straightedgelinux.com> <55670829.3080804@slackbuilds.org>
Message-ID: <55671E60.2060600@straightedgelinux.com>

On 05/29/2015 12:20 AM, Willy Sudiarto Raharjo wrote:
>> I think in the future, I'll use %README% in REQUIRES to alert the user
>> that the version of JACK is optional.
> 
> %README% is used to tell users that a package is conflicting/replacing
> Slackware packages. Other than that, users are always assumed to read
> README.

Sorry, I don't want to get side-tracked, but according to my memory of
the discussion about the REQUIRES field when its creation was being
debated, as well as http://slackbuilds.org/guidelines/ text:

"Listing '%README%' as part of REQUIRES indicates more information about
optional requirements is available in the README."

If that has changed, we should probably change the text.

-klaatu

From pprkut at slackbuilds.org  Thu May 28 14:01:55 2015
From: pprkut at slackbuilds.org (Heinz Wiesinger)
Date: Thu, 28 May 2015 16:01:55 +0200
Subject: [Slackbuilds-users] README [fork of Re:
	jack-audio-connection-kit vs jack2]
In-Reply-To: <55671E60.2060600@straightedgelinux.com>
References: <5566A017.1000601@straightedgelinux.com>
 <55670829.3080804@slackbuilds.org> <55671E60.2060600@straightedgelinux.com>
Message-ID: <1689451.d8X5vZNjoY@titania>

On Friday 29 May 2015 01:55:44 Klaatu wrote:
> On 05/29/2015 12:20 AM, Willy Sudiarto Raharjo wrote:
> >> I think in the future, I'll use %README% in REQUIRES to alert the user
> >> that the version of JACK is optional.
> > 
> > %README% is used to tell users that a package is conflicting/replacing
> > Slackware packages. Other than that, users are always assumed to read
> > README.
> 
> Sorry, I don't want to get side-tracked, but according to my memory of
> the discussion about the REQUIRES field when its creation was being
> debated, as well as http://slackbuilds.org/guidelines/ text:
> 
> "Listing '%README%' as part of REQUIRES indicates more information about
> optional requirements is available in the README."
> 
> If that has changed, we should probably change the text.

It hasn't, but if jack is listed in REQUIRES, it's not an optional dependency 
either (but required, as the name states), and hence the %README% rule doesn't 
apply. And if it's not listed you can already explain more in the README, 
without the %README%. So really, %README% is completely irrelevant for this 
discussion.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/b73ba384/attachment.asc>

From klaatu at straightedgelinux.com  Thu May 28 14:03:44 2015
From: klaatu at straightedgelinux.com (Klaatu)
Date: Fri, 29 May 2015 02:03:44 +1200
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <55670829.3080804@slackbuilds.org>
References: <5566A017.1000601@straightedgelinux.com>
 <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
 <5566EABA.2070402@straightedgelinux.com> <55670829.3080804@slackbuilds.org>
Message-ID: <55672040.7010401@straightedgelinux.com>

On 05/29/2015 12:20 AM, Willy Sudiarto Raharjo wrote:
>> I think in the future, I'll use %README% in REQUIRES to alert the user
>> that the version of JACK is optional.
> 
> %README% is used to tell users that a package is conflicting/replacing
> Slackware packages. Other than that, users are always assumed to read
> README.
> 

Willy,

Is there currently a way to indicate that two packages are able to
satisfy one dependency?

I can't even think of an SBo precedence to base a resolution upon.

-klaatu

From joshuakwood at gmail.com  Thu May 28 14:27:34 2015
From: joshuakwood at gmail.com (JK Wood)
Date: Thu, 28 May 2015 09:27:34 -0500
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <55672040.7010401@straightedgelinux.com>
References: <5566A017.1000601@straightedgelinux.com>
 <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
 <5566EABA.2070402@straightedgelinux.com>
 <55670829.3080804@slackbuilds.org>
 <55672040.7010401@straightedgelinux.com>
Message-ID: <CA+j=baA3Kxmd9o8MM9Abg=cjF4DKH-n7t7nPXass43GZ_aDhjw@mail.gmail.com>

On May 28, 2015 9:03 AM, "Klaatu" <klaatu at straightedgelinux.com> wrote:
>
> On 05/29/2015 12:20 AM, Willy Sudiarto Raharjo wrote:
> >> I think in the future, I'll use %README% in REQUIRES to alert the user
> >> that the version of JACK is optional.
> >
> > %README% is used to tell users that a package is conflicting/replacing
> > Slackware packages. Other than that, users are always assumed to read
> > README.
> >
>
> Willy,
>
> Is there currently a way to indicate that two packages are able to
> satisfy one dependency?
>
> I can't even think of an SBo precedence to base a resolution upon.
>
> -klaatu
>

Sure, there's the wxPython/wxGTK/wxWhateverTheOtherOneWas.

--JK _______________________________________________
> 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/20150528/e4ede030/attachment.html>

From willysr at slackbuilds.org  Thu May 28 14:43:04 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 28 May 2015 21:43:04 +0700
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <55672040.7010401@straightedgelinux.com>
References: <5566A017.1000601@straightedgelinux.com>
 <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
 <5566EABA.2070402@straightedgelinux.com> <55670829.3080804@slackbuilds.org>
 <55672040.7010401@straightedgelinux.com>
Message-ID: <55672978.6080205@slackbuilds.org>

> Is there currently a way to indicate that two packages are able to
> satisfy one dependency?
> 
> I can't even think of an SBo precedence to base a resolution upon.

I would suggest put one of them as default dependency and list the other
one in README.
That's what i did with your aj-snapshot package.
http://www.slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=415a5a501a47f81388ad53dbfd981898b41dc995

Sorry i keep the category in audio not in multimedia

-- 
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/20150528/c32948cc/attachment.asc>

From matteo.bernardini at gmail.com  Thu May 28 16:45:50 2015
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 28 May 2015 18:45:50 +0200
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <556489BB.9090707@slackbuilds.org>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
 <5563CCF4.5040801@slackbuilds.org>
 <CAMt7G9Qp07p-s=E9hGWG3pqDKifof6CniednRVa1PC6DYfsqaQ@mail.gmail.com>
 <556489BB.9090707@slackbuilds.org>
Message-ID: <CAPsDuS7u5gVyzCY3AX1gA+vSHkDQ8-EDGZG7v-WpQ6puUmx9hw@mail.gmail.com>

2015-05-26 16:56 GMT+02:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:
>> Thanks, but what about the problem where it breaks the permissions on /tmp?
>>
>> morticia# ls -ald /tmp/
>> drwxrwxrwt 25 root root 20480 May 26 15:23 /tmp/
>
> here on my VM it gave different results
> ls -l /tmp
> drwx------   2 apache  apache     4096 May 26 21:48 zm/

sorry willy, I think David was referring to the permission of the /tmp
directory itself: from what I have understood it seem to overwrite the
normal permissions of 1777 with 0755...

BTW, I tested these with the new ffmpeg/x264 and they seems to work fine here

audio/audacity (I used the archlinux patch)
audio/cmus
libraries/wxsvg
multimedia/dvdstyler

also these build fine

libraries/chromaprint
libraries/libunicap (this builds)
multimedia/gpac
libraries/gst1-plugins-ugly
multimedia/avidemux
multimedia/kdenlive

regarding cinelerra I was able to build its -cv git version but I
think it definitely needs a maintainer (it doesn't work too well as
is). so I would be for dropping it if nobody steps in in place of
Giovanne Castro (that left maintainership of his stuff a while ago).

From baildon.research at googlemail.com  Thu May 28 16:53:47 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 28 May 2015 17:53:47 +0100
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
Message-ID: <CAMt7G9QhN23H-nkDvLKeb1gDnLGpswboSozyq8YjV=J-TXxsyA@mail.gmail.com>

Hey folks,

Everything on the list is now building ok on 14.1 here, both x86_64
and i686, but -current needs more work.

The problems were fixed as follows:

audio/audacity -- fixed with John V's patch
audio/mpd -- fixed with John V's upversion
games/alephone -- fixed with John V's patch on 14.1 *but* fails on -current
games/dolphin-emu -- fixed by removing the existing patch
multimedia/bombono-dvd -- fixed with John V's patch
multimedia/cinelerra -- needs lame and x264 in REQUIRES
multimedia/transcode -- needs lame in REQUIRES
network/imageshack-uploader -- fixed thanks to Willy
system/ZoneMinder -- fixed thanks to Willy, *note* it seems to need -j1 on 14.1

Commits for most of those are attached -- but there will be more later
when I get -current sorted out.

Thanks everybody!
-D.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0006-games-alephone-Patched-for-ffmpeg-2.6.3.patch
Type: text/x-diff
Size: 43133 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/40d1672f/attachment-0006.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0007-audio-audacity-Patched-for-ffmpeg-2.6.3.patch
Type: text/x-diff
Size: 2365 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/40d1672f/attachment-0007.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0008-multimedia-bombono-dvd-Patched-for-ffmpeg-2.6.3.patch
Type: text/x-diff
Size: 2239 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/40d1672f/attachment-0008.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0009-audio-mpd-Updated-for-version-0.19.9.patch
Type: text/x-diff
Size: 1325 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/40d1672f/attachment-0009.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0012-desktop-ffmpegthumbnailer-Fix-.info.patch
Type: text/x-diff
Size: 955 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/40d1672f/attachment-0010.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0013-games-dolphin-emu-Removed-patch.patch
Type: text/x-diff
Size: 2661 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/40d1672f/attachment-0011.bin>

From baildon.research at googlemail.com  Thu May 28 16:58:35 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 28 May 2015 17:58:35 +0100
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAPsDuS7u5gVyzCY3AX1gA+vSHkDQ8-EDGZG7v-WpQ6puUmx9hw@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
 <5563CCF4.5040801@slackbuilds.org>
 <CAMt7G9Qp07p-s=E9hGWG3pqDKifof6CniednRVa1PC6DYfsqaQ@mail.gmail.com>
 <556489BB.9090707@slackbuilds.org>
 <CAPsDuS7u5gVyzCY3AX1gA+vSHkDQ8-EDGZG7v-WpQ6puUmx9hw@mail.gmail.com>
Message-ID: <CAMt7G9R=nUUB+vpU=i9h7=bKO17B_QZBOXhcK5e0k51t7BGgDA@mail.gmail.com>

> sorry willy, I think David was referring to the permission of the /tmp
> directory itself: from what I have understood it seem to overwrite the
> normal permissions of 1777 with 0755...

Thanks Matteo, Willy and me sorted it out already, sorry for not
keeping the list up-to-date, but it was a bit of a side-track :D

(And you'll be getting some random -current patches from me soon, but
first my P4 needs to finish building
webkitgtk..............................)

Best regards to everybody
-D.

From pprkut at liwjatan.at  Thu May 28 17:45:58 2015
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Thu, 28 May 2015 19:45:58 +0200
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAMt7G9QhN23H-nkDvLKeb1gDnLGpswboSozyq8YjV=J-TXxsyA@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
 <CAMt7G9QhN23H-nkDvLKeb1gDnLGpswboSozyq8YjV=J-TXxsyA@mail.gmail.com>
Message-ID: <3834889.nHaI68q0rt@titania>

On Thursday 28 May 2015 17:53:47 David Spencer wrote:
> Hey folks,
> 
> Everything on the list is now building ok on 14.1 here, both x86_64
> and i686, but -current needs more work.
> 
> The problems were fixed as follows:
> [..]
> multimedia/transcode -- needs lame in REQUIRES

I pushed a different fix for this to github which should take care of it 
properly. Handling for lame must have changed at some point and nobody 
realized.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/b2acd888/attachment.asc>

From pprkut at liwjatan.at  Thu May 28 17:52:36 2015
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Thu, 28 May 2015 19:52:36 +0200
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAN1hMuDLTMRrXRJWaLcxYEOR=N-E-j87nH=cjKVAWZTj86TQFQ@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <CAN1hMuDLTMRrXRJWaLcxYEOR=N-E-j87nH=cjKVAWZTj86TQFQ@mail.gmail.com>
Message-ID: <1619151.bnnxUmjdBD@titania>

On Tuesday 26 May 2015 03:51:44 B Watson wrote:
> Another thing about building ffmpeg: it uses texi2html to generate the
> developer documentation, and chokes if it can't find it in the $PATH
> (usually because the user did plain 'su' instead of 'su -', or because
> the T series isn't installed). There's even extra code in there to check
> for texi2html... And I'd estimate 99% of people running the build script
> are never going to read the ffmpeg dev docs, because they're not writing
> code that uses ffmpeg (they just need it for transcoding movies, or as a
> dependency for something else).
> 
> Forcing people to jump through hoops to build documentation they're
> never going to read is annoying

I've always considered this my tiny contribution towards educating users to do 
things properly. I realize it's annoying, but it's intentionally so and at 
this point is already far less confrontational than earlier versions used to 
be. I don't intend to make any more concessions, sorry.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/df044faf/attachment.asc>

From baildon.research at googlemail.com  Thu May 28 17:58:12 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 28 May 2015 18:58:12 +0100
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <3834889.nHaI68q0rt@titania>
References: <2641720.EPdaEcPPNf@titania>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
 <CAMt7G9QhN23H-nkDvLKeb1gDnLGpswboSozyq8YjV=J-TXxsyA@mail.gmail.com>
 <3834889.nHaI68q0rt@titania>
Message-ID: <CAMt7G9QEhHsxEpE89yu+8sY_Gw=_v9wm=BwpppKH3cFagB-vWQ@mail.gmail.com>

> I pushed a different fix for this to github which should take care of it
> properly.

Heh, that's much better!
I wondered if that would work but never tried it!!  derp

Thanks
-D.

From pprkut at liwjatan.at  Thu May 28 18:00:19 2015
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Thu, 28 May 2015 20:00:19 +0200
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <55644595.5010308@iinet.net.au>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <55644595.5010308@iinet.net.au>
Message-ID: <1493213.AG7AW6lGM1@titania>

On Tuesday 26 May 2015 20:06:13 Christoph Willing wrote:
> On 26/05/15 17:24, Christoph Willing wrote:
> > Hi Heinz,
> > 
> > Since you're updating the SlackBuild, I wonder if you would consider a
> > change to the way optional features are handled?
> > 
> > Unlike many other softwares, ffmpeg is quite good at detecting any
> > necessary support packages needed to enable the various features. It
> > assumes (and I believe this is a good assumption) that if all the
> > conditions for a particular feature are present on the build machine,
> > then that feature will be enabled unless it has been specifically
> > disabled in the ./configure ... line.
> > 
> > At the moment many features are disabled in the SlackBuild by lines like:
> > libfrei0r=""; [ "${FREI0R:-no}" != "no" ] && libfrei0r="--enable-frei0r"
> > 
> > Would you consider removing all those lines so that all available
> > features can be enabled rather than disabled? At the moment I have to
> > edit the SlackBuild quite a bit, or have a very long (error prone)
> > command line to re-enable all the features that should be included.
> 
> I'm sorry, that's actually a dopey request. I've had my version edited
> for so long (to set all those options to "yes") that I thought it would
> be good just to remove all the option setting code without realising
> that these are options that ffmpeg does _not_ detect automagically.
> 
> Therefore, could I request instead that those options default to "yes"?
> It would also need the relevant packages names added to the .info file.

Sorry, I generally believe (with few exceptions) that optional dependencies 
should be opt-in to the user, not opt-out.

Additionally, setting everything to "yes" by default, means I'd have to add 
every optional, non-autodetected dep into REQUIRES, which conceptionally 
doesn't really leave them optional at all. Technically nothing forces you to 
install something that's listed in REQUIRES, but let's face it, who actually 
bothers to double check whether a required dependency is actually required?

Leaving everything at "no" is the only sensible choice I'm afraid.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/cfcf7871/attachment.asc>

From pprkut at slackbuilds.org  Thu May 28 18:11:43 2015
From: pprkut at slackbuilds.org (Heinz Wiesinger)
Date: Thu, 28 May 2015 20:11:43 +0200
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <5566A017.1000601@straightedgelinux.com>
References: <5566A017.1000601@straightedgelinux.com>
Message-ID: <6457998.4OrREDLIlI@titania>

On Thursday 28 May 2015 16:56:55 Klaatu wrote:
> Fellow SBo maintainers:
> 
> I have noticed that one of my own scripts depends on JACK, and that I
> myself had listed the dependency as "jack-audio-connection-kit".
> 
> Then I realised that this listing is not quite correct, because in fact
> ANY package that depends upon "JACK" actually depends on EITHER JACK
> version 1 or JACK version 2.

Conflicting alternative packages are really nothing out of the ordinary. 
There's quite a few examples additionally to jack:

- wxPython, wxGTK, wxX11
- libav, ffmpeg
- mysql, mariadb

The general guidelines we try to follow is this:

- All conflicting packages mention in the README what they conflict with (i.e. 
jack-audio-connection-kit should mention it conflicts with jack2, and jack2 
should mention it conflicts with jack-audio-connection-kit)
- One of the conflicting packages is picked and placed in REQUIRES, uniquely.
- Everything else is up to the user

Obviously, mistakes/insonsistencies can happen, especially if alternatives are 
introduced to the repo at a later stage. But generally, that's all there is 
and I don't see a particular need to change that for whatever little benefit it 
would provide, but as usual, if the arguments are sound enough, every rule and 
guideline is up for discussion.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/25f47d17/attachment.asc>

From yalhcru at gmail.com  Thu May 28 19:12:44 2015
From: yalhcru at gmail.com (B Watson)
Date: Thu, 28 May 2015 15:12:44 -0400
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <1493213.AG7AW6lGM1@titania>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <55644595.5010308@iinet.net.au> <1493213.AG7AW6lGM1@titania>
Message-ID: <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>

On 5/28/15, Heinz Wiesinger <pprkut at liwjatan.at> wrote:
> Leaving everything at "no" is the only sensible choice I'm afraid.

How about adding a copy/pastable line to bottom of the README with all
the environment variables set to yes? Something like:

---cut---
To build with all optional dependencies, run:

ASS=yes BLURAY=yes CELT=yes DC1394=yes FAAC=yes \
FREI0R=yes GSM=yes IEC61883=yes ILBC=yes JP2=yes \
LADSPA=yes LAME=yes MODPLUG=yes OPENAL=yes OPENCORE=yes \
OPENSSL=yes OPUS=yes PULSEAUDIO=yes RTMP=yes SCHROEDINGER=yes \
SPEEX=yes TWOLAME=yes VPX=yes X264=yes XVID=yes \
  ./ffmpeg.SlackBuild
---cut---

That would save a lot of typing for anyone wanting to build with all or
most of the dependencies.

From miguel at thedeanda.com  Thu May 28 19:45:04 2015
From: miguel at thedeanda.com (Miguel De Anda)
Date: Thu, 28 May 2015 12:45:04 -0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <55644595.5010308@iinet.net.au> <1493213.AG7AW6lGM1@titania>
 <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>
Message-ID: <CAA62KfRJKDFjncvjXqpgOC2-jH+UaoMVGzijvemUp8_wFU0PiA@mail.gmail.com>

is it an option to have it autodetect if each of those libraries are
installed?

On Thu, May 28, 2015 at 12:12 PM, B Watson <yalhcru at gmail.com> wrote:

> On 5/28/15, Heinz Wiesinger <pprkut at liwjatan.at> wrote:
> > Leaving everything at "no" is the only sensible choice I'm afraid.
>
> How about adding a copy/pastable line to bottom of the README with all
> the environment variables set to yes? Something like:
>
> ---cut---
> To build with all optional dependencies, run:
>
> ASS=yes BLURAY=yes CELT=yes DC1394=yes FAAC=yes \
> FREI0R=yes GSM=yes IEC61883=yes ILBC=yes JP2=yes \
> LADSPA=yes LAME=yes MODPLUG=yes OPENAL=yes OPENCORE=yes \
> OPENSSL=yes OPUS=yes PULSEAUDIO=yes RTMP=yes SCHROEDINGER=yes \
> SPEEX=yes TWOLAME=yes VPX=yes X264=yes XVID=yes \
>   ./ffmpeg.SlackBuild
> ---cut---
>
> That would save a lot of typing for anyone wanting to build with all or
> most of the dependencies.
> _______________________________________________
> 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/20150528/d32997c0/attachment-0001.html>

From baildon.research at googlemail.com  Thu May 28 19:57:15 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 28 May 2015 20:57:15 +0100
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <55644595.5010308@iinet.net.au> <1493213.AG7AW6lGM1@titania>
 <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>
Message-ID: <CAMt7G9RK3=_ra+UY0f8WeKecP2bX12Om5Bp9Z_ttTJ+FZJmbNw@mail.gmail.com>

At the risk of further bikeshedding, isn't it best to just keep your
choice of options somewhere? e.g. in the sbopkg queuefile, or in the
sbopkg saved .options file?

-D.

From willysr at slackbuilds.org  Thu May 28 21:01:02 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 29 May 2015 04:01:02 +0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAMt7G9QhN23H-nkDvLKeb1gDnLGpswboSozyq8YjV=J-TXxsyA@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <20150524011836.07088c15@stygian.lan>
 <CAAcyf-qKRnaDYivLuAN-WoSvGk+C8wXoWUUaY+zVsecemsmhzA@mail.gmail.com>
 <20150524145308.409d864f@stygian.lan>
 <CAMt7G9RfM54s5+pk4b1KYT9OdQ8WYp11DMdfkxOGXffmVo1LqQ@mail.gmail.com>
 <CAMt7G9QhN23H-nkDvLKeb1gDnLGpswboSozyq8YjV=J-TXxsyA@mail.gmail.com>
Message-ID: <74391DFC-7BA5-4BEA-9271-02D2D2DAF064@slackbuilds.org>


> system/ZoneMinder -- fixed thanks to Willy, *note* it seems to need -j1 on 14.1

I tested on 14.1 (64 bit) with default configuration and it worked. I set the VM to have 2 cores only.
Perhaps you have a MAKEFLAGS variable set up to use multiple cores?

--
Willy Sudiarto Raharjo

From chris.willing at iinet.net.au  Thu May 28 21:15:19 2015
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Fri, 29 May 2015 07:15:19 +1000
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAMt7G9RK3=_ra+UY0f8WeKecP2bX12Om5Bp9Z_ttTJ+FZJmbNw@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <55644595.5010308@iinet.net.au> <1493213.AG7AW6lGM1@titania>
 <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>
 <CAMt7G9RK3=_ra+UY0f8WeKecP2bX12Om5Bp9Z_ttTJ+FZJmbNw@mail.gmail.com>
Message-ID: <55678567.9030909@iinet.net.au>



On 29/05/15 05:57, David Spencer wrote:
> At the risk of further bikeshedding, isn't it best to just keep your
> choice of options somewhere? e.g. in the sbopkg queuefile, or in the
> sbopkg saved .options file?

That's only good for sbopkg users.

chris

From baildon.research at googlemail.com  Thu May 28 21:47:13 2015
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 28 May 2015 22:47:13 +0100
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <55678567.9030909@iinet.net.au>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <55644595.5010308@iinet.net.au> <1493213.AG7AW6lGM1@titania>
 <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>
 <CAMt7G9RK3=_ra+UY0f8WeKecP2bX12Om5Bp9Z_ttTJ+FZJmbNw@mail.gmail.com>
 <55678567.9030909@iinet.net.au>
Message-ID: <CAMt7G9Tj4G9OLobB24KcJnPBsKifjvoARFO_r6S3bXM+_6EDDA@mail.gmail.com>

> That's only good for sbopkg users.

There are plenty of alternatives to sbopkg these days. One of them is mine.

Manual building is good for learning and experimenting, but it's never
going to be reliable or convenient.

-D.

From ryan.q at linux.com  Thu May 28 22:16:19 2015
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Thu, 28 May 2015 15:16:19 -0700
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <6457998.4OrREDLIlI@titania>
References: <5566A017.1000601@straightedgelinux.com>
 <6457998.4OrREDLIlI@titania>
Message-ID: <CAAcyf-p-5Pe8BAcsivqOUo3yA7KE9d08RtZhhsxAO3doUbCBtQ@mail.gmail.com>

>But generally, that's all there is and I don't see a particular need to change that for whatever little benefit it would provide ...

I agree completely. Slackware is intended to be a system that treats
the user as if they are smart. Let's keep that tradition alive.

---


On 5/28/15, Heinz Wiesinger <pprkut at slackbuilds.org> wrote:
> On Thursday 28 May 2015 16:56:55 Klaatu wrote:
>> Fellow SBo maintainers:
>>
>> I have noticed that one of my own scripts depends on JACK, and that I
>> myself had listed the dependency as "jack-audio-connection-kit".
>>
>> Then I realised that this listing is not quite correct, because in fact
>> ANY package that depends upon "JACK" actually depends on EITHER JACK
>> version 1 or JACK version 2.
>
> Conflicting alternative packages are really nothing out of the ordinary.
> There's quite a few examples additionally to jack:
>
> - wxPython, wxGTK, wxX11
> - libav, ffmpeg
> - mysql, mariadb
>
> The general guidelines we try to follow is this:
>
> - All conflicting packages mention in the README what they conflict with
> (i.e.
> jack-audio-connection-kit should mention it conflicts with jack2, and jack2
>
> should mention it conflicts with jack-audio-connection-kit)
> - One of the conflicting packages is picked and placed in REQUIRES,
> uniquely.
> - Everything else is up to the user
>
> Obviously, mistakes/insonsistencies can happen, especially if alternatives
> are
> introduced to the repo at a later stage. But generally, that's all there is
>
> and I don't see a particular need to change that for whatever little benefit
> it
> would provide, but as usual, if the arguments are sound enough, every rule
> and
> guideline is up for discussion.
>
> Grs,
> Heinz


-- 
---
<ryanpcmcquen.com>

From andrew.david.strong at gmail.com  Thu May 28 22:49:17 2015
From: andrew.david.strong at gmail.com (andrew)
Date: Fri, 29 May 2015 08:49:17 +1000
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <CAMt7G9Tj4G9OLobB24KcJnPBsKifjvoARFO_r6S3bXM+_6EDDA@mail.gmail.com>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <55644595.5010308@iinet.net.au> <1493213.AG7AW6lGM1@titania>
 <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>
 <CAMt7G9RK3=_ra+UY0f8WeKecP2bX12Om5Bp9Z_ttTJ+FZJmbNw@mail.gmail.com>
 <55678567.9030909@iinet.net.au>
 <CAMt7G9Tj4G9OLobB24KcJnPBsKifjvoARFO_r6S3bXM+_6EDDA@mail.gmail.com>
Message-ID: <20150528224917.GA24651@ilium.andrews-corner.org>

On Thu, May 28, 2015 at 10:47:13PM +0100, David Spencer wrote:

> Manual building is good for learning and experimenting, but it's
> never going to be reliable or convenient.

Interesting to know the numbers of users of tools such as sbopkg and
the like compared to those like myself who do it 'manually' from SBo.

Andrew
-- 
You think that's air you're breathing now?

From ryan.q at linux.com  Thu May 28 23:04:11 2015
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Thu, 28 May 2015 16:04:11 -0700
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <20150528224917.GA24651@ilium.andrews-corner.org>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <55644595.5010308@iinet.net.au> <1493213.AG7AW6lGM1@titania>
 <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>
 <CAMt7G9RK3=_ra+UY0f8WeKecP2bX12Om5Bp9Z_ttTJ+FZJmbNw@mail.gmail.com>
 <55678567.9030909@iinet.net.au>
 <CAMt7G9Tj4G9OLobB24KcJnPBsKifjvoARFO_r6S3bXM+_6EDDA@mail.gmail.com>
 <20150528224917.GA24651@ilium.andrews-corner.org>
Message-ID: <CAAcyf-puLjYdsO5CRHAdNUr-8hsdDnFRvvRLnAPWtD=4eN-wtQ@mail.gmail.com>

On 5/28/15, andrew <andrew.david.strong at gmail.com> wrote:
> On Thu, May 28, 2015 at 10:47:13PM +0100, David Spencer wrote:
>
>> Manual building is good for learning and experimenting, but it's
>> never going to be reliable or convenient.
>
> Interesting to know the numbers of users of tools such as sbopkg and
> the like compared to those like myself who do it 'manually' from SBo.

I use sbopkg a lot, but I do NOT use sqg. I like to know the
dependencies and what is going on to my system.

---
>
> Andrew
> --
> You think that's air you're breathing now?
> _______________________________________________
> 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/
>
>


-- 
---
<ryanpcmcquen.com>

From x77 at shaw.ca  Fri May 29 04:43:29 2015
From: x77 at shaw.ca (PG Ouellette)
Date: Thu, 28 May 2015 22:43:29 -0600 (MDT)
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <20150528224917.GA24651@ilium.andrews-corner.org>
Message-ID: <2102345053.60428230.1432874609921.JavaMail.root@shaw.ca>



----- Original Message -----

From: "andrew" <andrew.david.strong at gmail.com> 
To: slackbuilds-users at slackbuilds.org 
Sent: Thursday, May 28, 2015 3:49:17 PM 
Subject: Re: [Slackbuilds-users] FFmpeg update 

On Thu, May 28, 2015 at 10:47:13PM +0100, David Spencer wrote: 

> Manual building is good for learning and experimenting, but it's 
> never going to be reliable or convenient. 

Interesting to know the numbers of users of tools such as sbopkg and 
the like compared to those like myself who do it 'manually' from SBo. 



I tend do do it manually, without slackbuilds... I only use them when a build fails, so I can get a patch or a hint. I don't know why, but for some reason 

related to the tool chain, there seems to be more build failures lately, like in the past year or two. 

But don't believe me, I may be crazy. Anyone else note this problem? 
-- 

PG Ouellette 

Social Media and Internet Marketing for http://www.tgihvac.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150528/cadb748e/attachment.html>

From elyk03 at gmail.com  Fri May 29 05:05:01 2015
From: elyk03 at gmail.com (Kyle Guinn)
Date: Fri, 29 May 2015 00:05:01 -0500
Subject: [Slackbuilds-users] README [fork of Re:
 jack-audio-connection-kit vs jack2]
In-Reply-To: <55671E60.2060600@straightedgelinux.com>
References: <5566A017.1000601@straightedgelinux.com>
 <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
 <5566EABA.2070402@straightedgelinux.com>
 <55670829.3080804@slackbuilds.org>
 <55671E60.2060600@straightedgelinux.com>
Message-ID: <CAJCpn82biQBrW3rmJOYxtBS72miAXJ7Oxdw76H+0asqD4o=JzQ@mail.gmail.com>

On 5/28/15, Klaatu <klaatu at straightedgelinux.com> wrote:
> On 05/29/2015 12:20 AM, Willy Sudiarto Raharjo wrote:
>> %README% is used to tell users that a package is conflicting/replacing
>> Slackware packages. Other than that, users are always assumed to read
>> README.
>
> Sorry, I don't want to get side-tracked, but according to my memory of
> the discussion about the REQUIRES field when its creation was being
> debated, as well as http://slackbuilds.org/guidelines/ text:
>
> "Listing '%README%' as part of REQUIRES indicates more information about
> optional requirements is available in the README."

What exactly is an "optional requirement"?  Seems like an oxymoron...

-Kyle

From willysr at slackbuilds.org  Fri May 29 05:12:27 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 29 May 2015 12:12:27 +0700
Subject: [Slackbuilds-users] README [fork of Re:
 jack-audio-connection-kit vs jack2]
In-Reply-To: <CAJCpn82biQBrW3rmJOYxtBS72miAXJ7Oxdw76H+0asqD4o=JzQ@mail.gmail.com>
References: <5566A017.1000601@straightedgelinux.com>
 <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
 <5566EABA.2070402@straightedgelinux.com>
 <55670829.3080804@slackbuilds.org>
 <55671E60.2060600@straightedgelinux.com>
 <CAJCpn82biQBrW3rmJOYxtBS72miAXJ7Oxdw76H+0asqD4o=JzQ@mail.gmail.com>
Message-ID: <CAJ+QsaJ8S3g9FFTCmDNTrnqtkPCA3eY+DL26CoOfoWFwq13xeQ@mail.gmail.com>

> What exactly is an "optional requirement"?  Seems like an oxymoron...

dependency that is not mandatory to have (either run time or build
time) and the package is still functional without it
if you have it, then you can have/enable additional features/functionality

-- 
Willy Sudiarto Raharjo

From klaatu at straightedgelinux.com  Fri May 29 06:39:35 2015
From: klaatu at straightedgelinux.com (Klaatu)
Date: Fri, 29 May 2015 18:39:35 +1200
Subject: [Slackbuilds-users] jack-audio-connection-kit vs jack2
In-Reply-To: <CAAcyf-p-5Pe8BAcsivqOUo3yA7KE9d08RtZhhsxAO3doUbCBtQ@mail.gmail.com>
References: <5566A017.1000601@straightedgelinux.com>
 <6457998.4OrREDLIlI@titania>
 <CAAcyf-p-5Pe8BAcsivqOUo3yA7KE9d08RtZhhsxAO3doUbCBtQ@mail.gmail.com>
Message-ID: <556809A7.50009@straightedgelinux.com>

On 05/29/2015 10:16 AM, Ryan P.C. McQuen wrote:
>> But generally, that's all there is and I don't see a particular need to change that for whatever little benefit it would provide ...
> 
> I agree completely. Slackware is intended to be a system that treats
> the user as if they are smart. Let's keep that tradition alive.
> 
> ---
> 
> 
> On 5/28/15, Heinz Wiesinger <pprkut at slackbuilds.org> wrote:
>> On Thursday 28 May 2015 16:56:55 Klaatu wrote:
>>> Fellow SBo maintainers:
>>>
>>> I have noticed that one of my own scripts depends on JACK, and that I
>>> myself had listed the dependency as "jack-audio-connection-kit".
>>>
>>> Then I realised that this listing is not quite correct, because in fact
>>> ANY package that depends upon "JACK" actually depends on EITHER JACK
>>> version 1 or JACK version 2.
>>
>> Conflicting alternative packages are really nothing out of the ordinary.
>> There's quite a few examples additionally to jack:
>>
>> - wxPython, wxGTK, wxX11
>> - libav, ffmpeg
>> - mysql, mariadb
>>
>> The general guidelines we try to follow is this:
>>
>> - All conflicting packages mention in the README what they conflict with
>> (i.e.
>> jack-audio-connection-kit should mention it conflicts with jack2, and jack2
>>
>> should mention it conflicts with jack-audio-connection-kit)
>> - One of the conflicting packages is picked and placed in REQUIRES,
>> uniquely.
>> - Everything else is up to the user
>>
>> Obviously, mistakes/insonsistencies can happen, especially if alternatives
>> are
>> introduced to the repo at a later stage. But generally, that's all there is
>>
>> and I don't see a particular need to change that for whatever little benefit
>> it
>> would provide, but as usual, if the arguments are sound enough, every rule
>> and
>> guideline is up for discussion.
>>
>> Grs,
>> Heinz
> 
> 


Sounds good to me. Thanks, everyone.

-klaatu

From chris.willing at iinet.net.au  Fri May 29 06:44:58 2015
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Fri, 29 May 2015 16:44:58 +1000
Subject: [Slackbuilds-users] Setting options (was: FFmpeg update)
In-Reply-To: <55678567.9030909@iinet.net.au>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <55644595.5010308@iinet.net.au> <1493213.AG7AW6lGM1@titania>
 <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>
 <CAMt7G9RK3=_ra+UY0f8WeKecP2bX12Om5Bp9Z_ttTJ+FZJmbNw@mail.gmail.com>
 <55678567.9030909@iinet.net.au>
Message-ID: <55680AEA.7010003@iinet.net.au>



On 29/05/15 07:15, Christoph Willing wrote:
>
>
> On 29/05/15 05:57, David Spencer wrote:
>> At the risk of further bikeshedding, isn't it best to just keep your
>> choice of options somewhere? e.g. in the sbopkg queuefile, or in the
>> sbopkg saved .options file?
>
> That's only good for sbopkg users.

So what about non-sbopkg users - myself, in particular? A better 
solution would be one that is not specific to a particular build 
framework. I've had an idea about it which I'll outline here and ask for 
any comments - its _not_ a proposal for any change at SBo.

As well as the SBo git master branch, I already have a local 'spbuilder' 
branch of it in which I keep any variations that I happen to want. In 
particular, for the packages I use, each .info file has an extra PREREQS 
field which contains any packages that I want beyond those already 
mentioned in the REQUIRES field. The PREREQS field also has $REQUIRES in 
it; therefore my personal build tool can use the PREREQS field to load 
up both the standard packages as well as my preferred extra packages.

Using that same idea, of adding to the local version of the .info file, 
why not add an OPTIONS field? Probably better might be OPTIONS_ON and 
OPTIONS_OFF fields e.g.
     OPTIONS_ON="ASS BLURAY CELT DC1394 FAAC FREI0R"
     OPTIONS_OFF="ILBC"
which the build tool would use to set options in the environment when it 
runs the SlackBuild.

Is it preferable to edit the .info file (rather than the .SlackBuild)? 
Well, I think it is preferable for two reasons. Firstly because the 
.info file is not executed and any additional fields in it should be 
completely transparent to any build system that doesn't know about the 
additions. Secondly because periodic merges from master _usually_ cause 
no conflicts when any local changes consist of additions at the end of a 
file (as would be the case here). On the other hand, changes in the 
middle of a file (like resetting various options from 'no' to 'yes' in 
the .SlackBuild file itself) are more likely to result in merge 
conflicts that need to be resolved.

Its just an idea at the moment. I'd welcome any comments (is it an 
inherently _bad_ idea?) before modifying my build tool to accommodate it.

chris

From klaatu at straightedgelinux.com  Fri May 29 06:45:54 2015
From: klaatu at straightedgelinux.com (Klaatu)
Date: Fri, 29 May 2015 18:45:54 +1200
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <2102345053.60428230.1432874609921.JavaMail.root@shaw.ca>
References: <2102345053.60428230.1432874609921.JavaMail.root@shaw.ca>
Message-ID: <55680B22.1020903@straightedgelinux.com>

On 05/29/2015 04:43 PM, PG Ouellette wrote:
> 
> 
> ----- Original Message -----
> 
> From: "andrew" <andrew.david.strong at gmail.com> 
> To: slackbuilds-users at slackbuilds.org 
> Sent: Thursday, May 28, 2015 3:49:17 PM 
> Subject: Re: [Slackbuilds-users] FFmpeg update 
> 
> On Thu, May 28, 2015 at 10:47:13PM +0100, David Spencer wrote: 
> 
>> Manual building is good for learning and experimenting, but it's 
>> never going to be reliable or convenient. 
> 
> Interesting to know the numbers of users of tools such as sbopkg and 
> the like compared to those like myself who do it 'manually' from SBo. 
> 
> 
> 
> I tend do do it manually, without slackbuilds... I only use them when a build fails, so I can get a patch or a hint. I don't know why, but for some reason 
> 
> related to the tool chain, there seems to be more build failures lately, like in the past year or two. 
> 
> But don't believe me, I may be crazy. Anyone else note this problem? 
> 
> 
> 
> _______________________________________________
> 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/
> 

Like many others, I use my own solution for automating what I need
automated. The most appealing thing about slackbuilds.org is its ability
to be done manually or scripted, and both are equal. I will always
favour the manual method, in terms of design. Let the scripters adapt to
the manual method; otherwise we run the risk of forcing people to
unravel scripts in order to do things manually, and I don't care for that.

I have not noticed any kind of failure with the tool chain, but I
suspect that this is because I use my own tool chain and perhaps you are
speaking of specific ones?

-klaatu

From lems at gmx.net  Fri May 29 07:35:08 2015
From: lems at gmx.net (Leonard Schmidt)
Date: Fri, 29 May 2015 09:35:08 +0200
Subject: [Slackbuilds-users] Setting options (was: FFmpeg update)
In-Reply-To: <55680AEA.7010003@iinet.net.au>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <55644595.5010308@iinet.net.au> <1493213.AG7AW6lGM1@titania>
 <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>
 <CAMt7G9RK3=_ra+UY0f8WeKecP2bX12Om5Bp9Z_ttTJ+FZJmbNw@mail.gmail.com>
 <55678567.9030909@iinet.net.au> <55680AEA.7010003@iinet.net.au>
Message-ID: <0Lkjuq-1ZYfV33aw0-00aYg2@mail.gmx.com>

Hello,

Christoph Willing writes:
>
>Using that same idea, of adding to the local version of the .info file, 
>why not add an OPTIONS field? Probably better might be OPTIONS_ON and 
>OPTIONS_OFF fields e.g.
>     OPTIONS_ON="ASS BLURAY CELT DC1394 FAAC FREI0R"
>     OPTIONS_OFF="ILBC"
>which the build tool would use to set options in the environment when it 
>runs the SlackBuild.

I don't know if I misunderstand you, but if with build tool you mean
your own solution, I don't see why you can't just as well add support
for `option handling' to your tool. I found compiling ffmpeg with my
desired dependencies tiresome, too, so my tool now is aware of .deps (and
.env) files I put into ~./script/options. The format is dep:VAR=VAL
(or simply dep) for .deps files, this will get picked up automatically
if I don't deactivate dependency handling. (In case of mpv, for example,
I override NUMJOBS via mpv.env to only contain an integer, no -j option,
otherwise it complains.)

The upside is that I can save these files and use them on other machines
easily, and no additional field in .info files is needed.

If I recall correctly, slackrepo also has (more powerful) so-called
hintfiles, and Karel Venken's `getpkgs' also has support for a HINTS
file, but I have little experience with these tools.

No offense, but I think people compiling SlackBuilds by hand know that
it won't be convenient, and those who use (their own) tools have the
ability to specify additional dependencies via their build tool, at
least theoretically. As long as additional dependencies are listed in
README, I see no reason for any big changes in the way we handle
SlackBuilds from SlackBuilds.org.

Regards

Leonard

From lems at gmx.net  Fri May 29 07:36:53 2015
From: lems at gmx.net (Leonard Schmidt)
Date: Fri, 29 May 2015 09:36:53 +0200
Subject: [Slackbuilds-users] README [fork of Re:
	jack-audio-connection-kit vs jack2]
In-Reply-To: <CAJCpn82biQBrW3rmJOYxtBS72miAXJ7Oxdw76H+0asqD4o=JzQ@mail.gmail.com>
References: <5566A017.1000601@straightedgelinux.com>
 <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
 <5566EABA.2070402@straightedgelinux.com> <55670829.3080804@slackbuilds.org>
 <55671E60.2060600@straightedgelinux.com>
 <CAJCpn82biQBrW3rmJOYxtBS72miAXJ7Oxdw76H+0asqD4o=JzQ@mail.gmail.com>
Message-ID: <0MAQ0o-1YnpWx33LW-00BcwQ@mail.gmx.com>

Hello,

Kyle Guinn writes:
>What exactly is an "optional requirement"?  Seems like an oxymoron...

maybe he meant "optional dependency"? Would make more sense, I guess.

Leonard

From info at microlinux.fr  Fri May 29 13:52:52 2015
From: info at microlinux.fr (Niki Kovacs)
Date: Fri, 29 May 2015 15:52:52 +0200
Subject: [Slackbuilds-users] gtkam translations not working
Message-ID: <55686F34.3040106@microlinux.fr>

Hi,

I just installed Gtkam 0.2.0 from SBo. Previous versions of Gtkam didn't 
support my Nikon 3100 camera and simply crashed. This version at last 
seems to work.

One thing that's odd. After peeking in the source code's po/ directory, 
the french translation seems to be fairly complete. On the other hand, 
the whole application displays in english in my environment (Xfce 4.12 
with LANG set to fr_FR.utf8).

I checked the SlackBuild to see if there's any --disable-nls or similar 
option, but there doesn't seem to be one.

Any idea how I can make my application work in French?

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 sbo-usxx.sender.grmblfjx at spamgourmet.com  Fri May 29 15:23:20 2015
From: sbo-usxx.sender.grmblfjx at spamgourmet.com (sbo-usxx.sender.grmblfjx at spamgourmet.com)
Date: Fri, 29 May 2015 17:23:20 +0200
Subject: [Slackbuilds-users] minitube broken
Message-ID: <op.xzek06fknzc709@0.0.0.64>

Hello,
would someone please bump the minitube version? The version currently on  
SBo stopped working due to a Youtube API change.
I mailed the maintainer one week ago and got no answer yet.

thanks in advance, Johannes


From willysr at slackbuilds.org  Fri May 29 15:37:15 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 29 May 2015 22:37:15 +0700
Subject: [Slackbuilds-users] minitube broken
In-Reply-To: <op.xzek06fknzc709@0.0.0.64>
References: <op.xzek06fknzc709@0.0.0.64>
Message-ID: <556887AB.4020208@slackbuilds.org>

> would someone please bump the minitube version? The version currently on
> SBo stopped working due to a Youtube API change.
> I mailed the maintainer one week ago and got no answer yet.

The new version requires a new Google API Key
The current maintainer is no longer active, so if someone want to step
up and maintain this package, please do so :)


-- 
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/20150529/4696fd2a/attachment-0001.asc>

From x77 at shaw.ca  Fri May 29 15:58:45 2015
From: x77 at shaw.ca (PG Ouellette)
Date: Fri, 29 May 2015 09:58:45 -0600 (MDT)
Subject: [Slackbuilds-users] FFmpeg update
In-Reply-To: <55680B22.1020903@straightedgelinux.com>
Message-ID: <1209007402.60826989.1432915125970.JavaMail.root@shaw.ca>



----- Original Message -----

From: "Klaatu" <klaatu at straightedgelinux.com> 
To: slackbuilds-users at slackbuilds.org 
Sent: Thursday, May 28, 2015 11:45:54 PM 
Subject: Re: [Slackbuilds-users] FFmpeg update 

On 05/29/2015 04:43 PM, PG Ouellette wrote: 
> 
> 
> ----- Original Message ----- 
> 
> From: "andrew" <andrew.david.strong at gmail.com> 
> To: slackbuilds-users at slackbuilds.org 
> Sent: Thursday, May 28, 2015 3:49:17 PM 
> Subject: Re: [Slackbuilds-users] FFmpeg update 
> 
> On Thu, May 28, 2015 at 10:47:13PM +0100, David Spencer wrote: 
> 
>> Manual building is good for learning and experimenting, but it's 
>> never going to be reliable or convenient. 
> 
> Interesting to know the numbers of users of tools such as sbopkg and 
> the like compared to those like myself who do it 'manually' from SBo. 
> 
> 
> 
> I tend do do it manually, without slackbuilds... I only use them when a build fails, so I can get a patch or a hint. I don't know why, but for some reason 
> 
> related to the tool chain, there seems to be more build failures lately, like in the past year or two. 
> 
> But don't believe me, I may be crazy. Anyone else note this problem? 
> 
> 
> 
> _______________________________________________ 
> 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/ 
> 

Like many others, I use my own solution for automating what I need 
automated. The most appealing thing about slackbuilds.org is its ability 
to be done manually or scripted, and both are equal. I will always 
favour the manual method, in terms of design. Let the scripters adapt to 
the manual method; otherwise we run the risk of forcing people to 
unravel scripts in order to do things manually, and I don't care for that. 

I have not noticed any kind of failure with the tool chain, but I 
suspect that this is because I use my own tool chain and perhaps you are 
speaking of specific ones? 

-klaatu 
_______________________________________________ 


> unravel scripts in order to do things manually 

That's how I get my hints! :) 

Actually mine is not a Slackbuilds issue or even a Slackware issue, and for that I'll retract my 

comment. 

Even though the GNU "configure and make" fails to keep up sometimes with both hardware and 

software detection, I cringe at the thought of using anything else. That's what I was on about. 


-- 

PG Ouellette 

Social Media and Internet Marketing for http://www.tgihvac.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150529/64e0ef80/attachment.html>

From yalhcru at gmail.com  Fri May 29 16:42:49 2015
From: yalhcru at gmail.com (B Watson)
Date: Fri, 29 May 2015 12:42:49 -0400
Subject: [Slackbuilds-users] README [fork of Re:
 jack-audio-connection-kit vs jack2]
In-Reply-To: <CAJCpn82biQBrW3rmJOYxtBS72miAXJ7Oxdw76H+0asqD4o=JzQ@mail.gmail.com>
References: <5566A017.1000601@straightedgelinux.com>
 <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
 <5566EABA.2070402@straightedgelinux.com>
 <55670829.3080804@slackbuilds.org>
 <55671E60.2060600@straightedgelinux.com>
 <CAJCpn82biQBrW3rmJOYxtBS72miAXJ7Oxdw76H+0asqD4o=JzQ@mail.gmail.com>
Message-ID: <CAN1hMuCjbFunh1DJ6zvJf1sju0-sc5H3rVzOXOhKNP+Bj2q9Gg@mail.gmail.com>

On 5/29/15, Kyle Guinn <elyk03 at gmail.com> wrote:
> What exactly is an "optional requirement"?  Seems like an oxymoron...

Example: ardour requires either jack-audio-connection-kit *or* jack2.

Most of the builds that use wxwidgets require either wxGTK or wxPython.

Not sure what the proper term for this would be. "Alternate requirement"
maybe?

From erik at slackbuilds.org  Fri May 29 17:39:14 2015
From: erik at slackbuilds.org (Erik Hanson)
Date: Fri, 29 May 2015 12:39:14 -0500
Subject: [Slackbuilds-users] README [fork of Re:
 jack-audio-connection-kit vs jack2]
In-Reply-To: <CAJCpn82biQBrW3rmJOYxtBS72miAXJ7Oxdw76H+0asqD4o=JzQ@mail.gmail.com>
References: <5566A017.1000601@straightedgelinux.com>
 <CAN1hMuCArvAOua+G-rNwePS=devCyg_62kn7o6cRQOsJJQ6KYg@mail.gmail.com>
 <5566EABA.2070402@straightedgelinux.com>
 <55670829.3080804@slackbuilds.org>
 <55671E60.2060600@straightedgelinux.com>
 <CAJCpn82biQBrW3rmJOYxtBS72miAXJ7Oxdw76H+0asqD4o=JzQ@mail.gmail.com>
Message-ID: <20150529123914.41e5ce42@shaggy.doo>

On Fri, 29 May 2015 00:05:01 -0500
Kyle Guinn <elyk03 at gmail.com> wrote:

> What exactly is an "optional requirement"?  Seems like an oxymoron...

The line in question was wrong regarding use of %README% - I've updated the
guidelines to better explain the original intended purpose.


-- 
Erik Hanson
-------------- 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/20150529/bfc7a279/attachment.asc>

From chris.willing at iinet.net.au  Sun May 31 00:41:08 2015
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Sun, 31 May 2015 10:41:08 +1000
Subject: [Slackbuilds-users] Setting options
In-Reply-To: <0Lkjuq-1ZYfV33aw0-00aYg2@mail.gmx.com>
References: <2641720.EPdaEcPPNf@titania> <55641FBC.8040706@iinet.net.au>
 <55644595.5010308@iinet.net.au> <1493213.AG7AW6lGM1@titania>
 <CAN1hMuDQnyarpVvrYtnV5_CNCBZr_CTNQuJCJwmCNNLt+paUeg@mail.gmail.com>
 <CAMt7G9RK3=_ra+UY0f8WeKecP2bX12Om5Bp9Z_ttTJ+FZJmbNw@mail.gmail.com>
 <55678567.9030909@iinet.net.au> <55680AEA.7010003@iinet.net.au>
 <0Lkjuq-1ZYfV33aw0-00aYg2@mail.gmx.com>
Message-ID: <556A58A4.4080603@iinet.net.au>



On 29/05/15 17:35, Leonard Schmidt wrote:
> Hello,
>
> Christoph Willing writes:
>>
>> Using that same idea, of adding to the local version of the .info file,
>> why not add an OPTIONS field? Probably better might be OPTIONS_ON and
>> OPTIONS_OFF fields e.g.
>>      OPTIONS_ON="ASS BLURAY CELT DC1394 FAAC FREI0R"
>>      OPTIONS_OFF="ILBC"
>> which the build tool would use to set options in the environment when it
>> runs the SlackBuild.
>
> I don't know if I misunderstand you, but if with build tool you mean
> your own solution, I don't see why you can't just as well add support
> for `option handling' to your tool. I found compiling ffmpeg with my
> desired dependencies tiresome, too, so my tool now is aware of .deps (and
> .env) files I put into ~./script/options. The format is dep:VAR=VAL
> (or simply dep) for .deps files, this will get picked up automatically
> if I don't deactivate dependency handling. (In case of mpv, for example,
> I override NUMJOBS via mpv.env to only contain an integer, no -j option,
> otherwise it complains.)
>
> The upside is that I can save these files and use them on other machines
> easily, and no additional field in .info files is needed.
>
> If I recall correctly, slackrepo also has (more powerful) so-called
> hintfiles, and Karel Venken's `getpkgs' also has support for a HINTS
> file, but I have little experience with these tools.
>
> No offense, but I think people compiling SlackBuilds by hand know that
> it won't be convenient, and those who use (their own) tools have the
> ability to specify additional dependencies via their build tool, at
> least theoretically. As long as additional dependencies are listed in
> README, I see no reason for any big changes in the way we handle
> SlackBuilds from SlackBuilds.org.

Hi Leonard,

I'm not proposing any changes to the way we handle SlackBuilds from 
SlackBuilds.org - from my earlier post:
> I've had an idea about it which I'll outline here and ask for any comments - its _not_ a proposal for any change at SBo.

My intention was to suggest a general method to handle the setting of 
options _locally_ i.e. by the person building packages, and ask for 
comments on that method. I assumed people would suggest alternatives 
that I could think about and you did that, thank you.

In fact I've since made a three line change to my build tool to do the 
job by processing a new ENVOPTS field which I've added to my local .info 
files, where needed; it looks something like:
     ENVOPTS="ASS=yes BLURAY=yes ... ILBC=no ..."
much like your .env files. The build tool just reads the field and 
exports each element into the environment before running the 
.SlackBuild. I works very well so far.

Thanks again for your input.

chris


From willysr at slackbuilds.org  Sun May 31 03:53:31 2015
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 31 May 2015 10:53:31 +0700
Subject: [Slackbuilds-users] Updates - 20150531.1
Message-ID: <556A85BB.6000603@slackbuilds.org>

Sun May 31 03:38:35 UTC 2015
academic/fet: Updated for version 5.27.2.
academic/gwyddion: Updated for version 2.41.
audio/aj-snapshot: Update README.
audio/apulse: Updated for version 20150525.
audio/decibel-audio-player: Added (GTK+ audio player for GNU/Linux).
audio/paman: Added (PulseAudio Manager).
audio/pasystray: Small change to README.
audio/pavumeter: Added (PulseAudio Volume Meter).
audio/pogo: Updated for version 0.8.4.
desktop/ccsm: Updated for version 0.8.10.
desktop/compton-conf: Added (Configuration Tool for Compton).
desktop/emerald-themes: Updated for version 0.8.10.
desktop/emerald: Updated for version 0.8.10.
desktop/seafile-gui: Updated for version 4.2.3.
desktop/siva-flat-themes: Added (GTK2|GTK3 themes).
desktop/skippy-xd: Added (full-screen task-switcher).
desktop/spectrwm: Updated for version 2.7.2.
desktop/xipper: Added (GUI for extract-xiso).
desktop/xvkbd: Fix building when lesstif is absent.
development/decklink-sdk: Added (Blackmagic Decklink SDK).
development/fossil: Updated for version 1.33.
development/gengetopt: Update slack-desc.
development/poedit: Updated for version 1.8.1.
games/dolphin-emu: Remove patch.
games/edgar: Fix empty line in .info.
games/mupen64plus: Updated for version 2.5.
games/openmw: Updated for version 0.36.0.
games/wesnoth: Fix parameters to build campaign server.
games/yamagi-quake2: Updated for version 5.30.
gis/Shapely: Updated for version 1.5.9.
gis/postgis: Add executables to /usr/bin.
graphics/gimagereader: Updated for version 3.1.
libraries/allegro: Add man pages.
libraries/botocore: Updated for version 1.0.0a3.
libraries/cbase: Updated for version 1.3.7.
libraries/cffi: Updated for version 1.1.0.
libraries/compiz-bcop: Updated for version 0.8.10.
libraries/compiz-plugins-extra: Updated for version 0.8.10.
libraries/compiz-plugins-main: Updated for version 0.8.10.
libraries/compiz-plugins-unsupported: Updated for version 0.8.10.
libraries/compizconfig-backend-kconfig4: Update DOWNLOAD url.
libraries/compizconfig-python: Updated for version 0.8.10.
libraries/libcompizconfig: Updated for version 0.8.10.
libraries/libepoxy: Added (OpenGL library).
libraries/libsidplayfp: Updated for version 1.7.2.
libraries/liburcu: Updated for version 0.8.7.
libraries/live555: Updated for version 2015.05.28.
libraries/oath-toolkit: Updated for version 2.6.0.
libraries/pexpect: Updated for version 3.3.
misc/qtspell: Updated for version 0.7.4.
multimedia/ffmpegyag: Added (FFmpeg GUI).
multimedia/mlt: Fixed lua bindings install location.
multimedia/plex-home-theater: Updated for version 1.4.1.469.
network/aria2: Updated for version 1.19.0.
network/awscli: Updated for version 1.7.31.
network/ccnet: Updated for version 4.2.1.
network/dropbox: Updated for version 3.4.6.
network/flexget: Updated for version 1.2.315.
network/freerapid: Added (Java downloader manager).
network/imageshack-uploader: Fix permissions.
network/insync: Updated for version 1.2.11.35149.
network/iojs: Updated for version 2.1.0.
network/netsniff-ng: Updated for version 0.5.9.
network/node: Updated for version 0.12.4.
network/nzbget: Updated for version 15.0.
network/pentadactyl: Updated for version 20150526.
network/proxychains: Updated for version 4.9.
network/seafile-client: Updated for version 4.2.1.
network/seafile-server: Updated for version 4.2.1.
network/seahub: Updated for version 4.2.2.
network/speedometer: Change txz -> tgz.
network/synergy: Updated for version 1.7.3.
network/tor: Updated for version 0.2.6.8.
network/youtube-dl: Updated for version 2015.05.20.
office/CherryTree: Updated for version 0.35.8.
perl/perl-Term-UI: Updated for version 0.46.
perl/perl-config-general: Updated for version 2.58.
python/jmespath: Updated for version 0.7.1.
python/msgpack-python: Updated for version 0.4.6.
python/pip: Updated for version 7.0.1.
python/py: Updated for version 1.4.28.
python/pysetuptools: Updated for version 17.0.
python/python-unicodecsv: Updated for version 0.13.0.
python/python2-pythondialog: Updated for version 3.3.0.
python/requirements-detector: Updated for version 0.4.
python/sge-pygame: Updated for version 0.18.2.
python/virtualenv: Updated for version 13.0.1.
system/ZoneMinder: Remove duplicate actions + fix permission.
system/asbt: Updated for version 1.7.1.
system/disk-manager: Added (simple filesystem configurator).
system/extract-xiso: Added (extract disc image).
system/lxsession: Change txz -> tgz.
system/openrc-services: Added (OpenRC services).
system/openrc: Added (dependency-based init system).
system/parallel: Updated for version 20150522.
system/roxterm: Fix building on multilib.
system/secure-delete: Added (wipe files securely).
system/slpkg: Updated for version 2.3.6.
system/solarize-12x29-psf: Added (large linux console font).
system/trmaid: Updated for version 0.5.3.1.
system/wmconfig: Updated for version 1.4.10.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From rshepard at appl-ecosys.com  Sun May 31 16:20:52 2015
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 31 May 2015 09:20:52 -0700 (PDT)
Subject: [Slackbuilds-users] Matplotlib Upgrade
Message-ID: <alpine.LNX.2.11.1505310915200.4239@localhost>

   Yesterday I upgraded numpy on two hosts (both running -14.1, one 32-bit,
the other 64-bit) to -1.9.1. Then I tried to upgrade matplotlib-1.4.2 from
-1.1.1. The upgrades failed because 'no numpy found'. Hmm-m-m.

   This morning, just for giggles, I removed numpy-1.9.1 and rebuilt it -- on
both hosts. Then the matplotlib.Slackbuild ran to completion on both.
Strange.

   I've no idea why the build script could not find the fresh numpy upgrade
the first time, but did when it was removed and re-installed. Have not seen
this before, either.

Rich

From alleytrotter at gmail.com  Sun May 31 19:37:29 2015
From: alleytrotter at gmail.com (John Yost)
Date: Sun, 31 May 2015 15:37:29 -0400
Subject: [Slackbuilds-users] QEMU
In-Reply-To: <55620C45.1070707@gmail.com>
References: <555B8D78.3060309@gmail.com>
 <CAPiArqNOeCFtoTWyxqzwkNsp9iyCsXwbPmf9C+eZOR6R_5KFWg@mail.gmail.com>
 <555B9507.5030009@gmail.com> <555E6F17.1090202@gmail.com>
 <5560ADAF.7050900@gmail.com> <55620C45.1070707@gmail.com>
Message-ID: <556B62F9.9060000@gmail.com>

On 05/24/2015 01:37 PM, King Beowulf wrote:
> On 05/23/2015 09:41 AM, John Yost wrote:
> 
>> I guess I am pretty old school.
>> I am just now switching over to using VM's for Linux
>> For all these years with Slackware (since about'98) I lived on
>> separate partitions for build, current, rescue, and production. Of
>> course this method requires a reboot to switch between worlds. 
> 
> Same here: for ages I just had a number of partitions.  However, this
> started to get tedious when I took on more SBo scripts.  A VM makes
> testing new stuff in a "clean room" easier.  I used to use VirtualBox,
> then Oracle grabbed them, so when QEMU was up for grabs I volunteered.
> 
>> So I am
>> now experimenting with Qemu. From your replies it seems I will need to
>> study the -drive switch and also look into 'copy on write'.
>> My biggest problem so far is passing info back and forth. I have been
>> using a usb stick but I see there are many other methods.
>> John
>>
> 
> I've attached my qemu script for slackware-current, etc. It will give
> you some ideas.  The virtio subsystem is very high performance. The VMs
> are isolated from my network. Also, once the VM is running, the host
> directory mounts with this fstab entry:
> 
> data    /mnt/hd    9p    trans=virtio   0   0
> 
> A host share, as well as the backing image I use makes a clean reset easy!
> 
> Enjoy,
> Ed
> 
> 
> 
> _______________________________________________
> 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/
> 
Another BIG thank you Ed
I have 9p working now with the generic kernel.
Having the same problem as you on huge.
Thank You
John

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xF3BDEB55.asc
Type: application/pgp-keys
Size: 2312 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150531/3bf92aaf/attachment.bin>