From shop at open-t.co.uk  Sun Aug  4 18:28:12 2013
From: shop at open-t.co.uk (Sebastian Arcus)
Date: Sun, 04 Aug 2013 19:28:12 +0100
Subject: [Slackbuilds-users] Latest libva available: 1.2.1. SBo version:
	0.31.1
Message-ID: <51FE9D3C.9050704@open-t.co.uk>

I noticed the other day when trying to compile get_iplayer that libva at 
SBo seems to be a long way behind latest official version 
(http://www.freedesktop.org/software/vaapi/releases/libva/). I tried 
contacting the maintainer of libva on SBo but no answer yet. Anybody 
knows of a specific reason why libva might need to stay on an older 
version (maybe compatibility issues)?

From kingbeowulf at gmail.com  Mon Aug  5 04:59:35 2013
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 04 Aug 2013 21:59:35 -0700
Subject: [Slackbuilds-users] RFC: changing .SlackBuild to allow separate
 source tree
Message-ID: <51FF3137.1000203@gmail.com>

What do you think of change to the slackbuild template along the lines of:

...
MYSRC=${MYSRC:-$CWD}
...
# with -C don't need a 'cd $TMP' line
tar xvf $MYSRC/$PRGNAM-$VERSION.tar.gz -C $TMP
...

This way, those of us (or just me) can have the sources outside the SBo
script tree and run as:

MYSRC=/far/far/away ./some_prog.SlackBuild

instead of remembering to moving source files around before doing 'git
pull|push' etc.

Just an idea, and no doubt will make no diff to users of sbopkg, but it
would make my hard drive SBo trees easier to organize.

Thanks,
Ed

From melikamp at melikamp.com  Mon Aug  5 16:54:01 2013
From: melikamp at melikamp.com (Ivan Zaigralin)
Date: Mon, 05 Aug 2013 12:54:01 -0400
Subject: [Slackbuilds-users] linphone and ffmpeg slackbuilds: The Eternal
	Struggle
Message-ID: <51FFD8A9.5000609@melikamp.com>

Hi everyone, and thanks again for being there for me when I need software,
without the pain.

When I am building linphone-3.5.2 and its pre-req ffmpeg-0.11.1 on Slackware
14.0 x64, straight from SB scripts, I get no video (the video device dropdown
in linphone is gray). linphone connects, though, with voice only, no problem.

When I use an older ffmpeg source and the same script (I think), everything
works. I don't know if that's relevant, but my video card is Intel Corporation
Ivy Bridge Graphics Controller (rev 09).

I guess, the question is, why doesn't my video work?

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

From ml at mareichelt.com  Mon Aug  5 16:55:07 2013
From: ml at mareichelt.com (Markus Reichelt)
Date: Mon, 5 Aug 2013 18:55:07 +0200
Subject: [Slackbuilds-users] RFC: changing .SlackBuild to allow separate
 source tree
In-Reply-To: <51FF3137.1000203@gmail.com>
References: <51FF3137.1000203@gmail.com>
Message-ID: <20130805165507.GA3859@pc21.mareichelt.com>

* King Beowulf <kingbeowulf at gmail.com> wrote:

> What do you think of change to the slackbuild template along the lines of:

+1


From bkirkp at gmail.com  Tue Aug  6 02:58:34 2013
From: bkirkp at gmail.com (B Kirkpatrick)
Date: Mon, 05 Aug 2013 21:58:34 -0500
Subject: [Slackbuilds-users] RFC: changing .SlackBuild to allow separate
 source tree
In-Reply-To: <20130805165507.GA3859@pc21.mareichelt.com>
References: <51FF3137.1000203@gmail.com>
	<20130805165507.GA3859@pc21.mareichelt.com>
Message-ID: <5200665A.4090400@gmail.com>

On 08/05/2013 11:55 AM, Markus Reichelt wrote:
> * King Beowulf <kingbeowulf at gmail.com> wrote:
>
>> What do you think of change to the slackbuild template along the lines of:
> +1
>
> _______________________________________________
> 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/
>
>
Why is that necessary? I have a file named ".sbopkg.conf  " in my /root 
directory that contains a line:

SRCDIR=/path/to/srcdir

Mine also has lines for QUEUEDIR, REPO_ROOT, REPO_NAME, & REPO_BRANCH, 
since none of them are at the default locations either.
Regards,
Bill


From kingbeowulf at gmail.com  Tue Aug  6 20:06:24 2013
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 06 Aug 2013 13:06:24 -0700
Subject: [Slackbuilds-users] RFC: changing .SlackBuild to allow separate
 source tree
In-Reply-To: <5200665A.4090400@gmail.com>
References: <51FF3137.1000203@gmail.com>
	<20130805165507.GA3859@pc21.mareichelt.com>
	<5200665A.4090400@gmail.com>
Message-ID: <52015740.1020906@gmail.com>

On 08/05/2013 07:58 PM, B Kirkpatrick wrote:
> Why is that necessary? I have a file named ".sbopkg.conf  " in my /root
> directory that contains a line:
> 
> SRCDIR=/path/to/srcdir
> 
> Mine also has lines for QUEUEDIR, REPO_ROOT, REPO_NAME, & REPO_BRANCH,
> since none of them are at the default locations either.
> Regards,
> Bill
> 

As I implied, I DO NOT USE sbopkg.  The change I propose will not effect
sbopkg users.  This change MIGHT be useful for those of us who DO NOT
use sbopkg or slackpkg and track multiple SBo and private script trees
and don't want to have source files copied back and forth.

-Ed


From yalhcru at gmail.com  Tue Aug  6 22:20:41 2013
From: yalhcru at gmail.com (B Watson)
Date: Tue, 6 Aug 2013 18:20:41 -0400
Subject: [Slackbuilds-users] RFC: changing .SlackBuild to allow separate
 source tree
In-Reply-To: <51FF3137.1000203@gmail.com>
References: <51FF3137.1000203@gmail.com>
Message-ID: <CAN1hMuCK4-CK6PTTXqxzjsgk3Y+w5kB+TnRdiiP4_uP18pbGaQ@mail.gmail.com>

On 8/5/13, King Beowulf <kingbeowulf at gmail.com> wrote:
> What do you think of change to the slackbuild template along the lines of:
>
> ...
> MYSRC=${MYSRC:-$CWD}
> ...
> # with -C don't need a 'cd $TMP' line
> tar xvf $MYSRC/$PRGNAM-$VERSION.tar.gz -C $TMP

Good plan.

I'd rather call it SRCDIR or something, but that's nitpicking.

From miguel at thedeanda.com  Wed Aug  7 00:23:04 2013
From: miguel at thedeanda.com (Miguel De Anda)
Date: Tue, 6 Aug 2013 17:23:04 -0700
Subject: [Slackbuilds-users] RFC: changing .SlackBuild to allow separate
 source tree
In-Reply-To: <CAN1hMuCK4-CK6PTTXqxzjsgk3Y+w5kB+TnRdiiP4_uP18pbGaQ@mail.gmail.com>
References: <51FF3137.1000203@gmail.com>
	<CAN1hMuCK4-CK6PTTXqxzjsgk3Y+w5kB+TnRdiiP4_uP18pbGaQ@mail.gmail.com>
Message-ID: <CAA62KfRrQ4AS+tR3fZbf+dX71ggMJ=Lw2FyWFPK=jJGJ+uFhsw@mail.gmail.com>

I'd be more interested in having the template pull variables off the .info
file. I often find myself updating version numbers in lots of files when
doing it once would normally be quicker and cleaner.


On Tue, Aug 6, 2013 at 3:20 PM, B Watson <yalhcru at gmail.com> wrote:

> On 8/5/13, King Beowulf <kingbeowulf at gmail.com> wrote:
> > What do you think of change to the slackbuild template along the lines
> of:
> >
> > ...
> > MYSRC=${MYSRC:-$CWD}
> > ...
> > # with -C don't need a 'cd $TMP' line
> > tar xvf $MYSRC/$PRGNAM-$VERSION.tar.gz -C $TMP
>
> Good plan.
>
> I'd rather call it SRCDIR or something, but that's nitpicking.
> _______________________________________________
> 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/20130806/bec7a4c4/attachment.html>

From nickblizzard1776 at gmail.com  Wed Aug  7 00:47:28 2013
From: nickblizzard1776 at gmail.com (Nick Blizzard)
Date: Tue, 6 Aug 2013 20:47:28 -0400
Subject: [Slackbuilds-users] RFC: changing .SlackBuild to allow separate
 source tree
In-Reply-To: <CAA62KfRrQ4AS+tR3fZbf+dX71ggMJ=Lw2FyWFPK=jJGJ+uFhsw@mail.gmail.com>
References: <51FF3137.1000203@gmail.com>
	<CAN1hMuCK4-CK6PTTXqxzjsgk3Y+w5kB+TnRdiiP4_uP18pbGaQ@mail.gmail.com>
	<CAA62KfRrQ4AS+tR3fZbf+dX71ggMJ=Lw2FyWFPK=jJGJ+uFhsw@mail.gmail.com>
Message-ID: <CA+xNRHfx6Knt17Z=e8H-5S_Ku1pCMxkD9X_Dq6J1fO_98E5OQQ@mail.gmail.com>

some tweak of this usually works for me (shamelessly stole from pats
scripts)

VERSION=${VERSION:-$(echo ${PRGNAM}-*.tar.?z* | rev | cut -f 3- -d . | cut
-f 1 -d - | rev)}

at most I have to tweak the 3 and 1 for how the source package gets
named... pair with a download script that pulls from the info... and it
just works.



On Tue, Aug 6, 2013 at 8:23 PM, Miguel De Anda <miguel at thedeanda.com> wrote:

> I'd be more interested in having the template pull variables off the .info
> file. I often find myself updating version numbers in lots of files when
> doing it once would normally be quicker and cleaner.
>
>
> On Tue, Aug 6, 2013 at 3:20 PM, B Watson <yalhcru at gmail.com> wrote:
>
>> On 8/5/13, King Beowulf <kingbeowulf at gmail.com> wrote:
>> > What do you think of change to the slackbuild template along the lines
>> of:
>> >
>> > ...
>> > MYSRC=${MYSRC:-$CWD}
>> > ...
>> > # with -C don't need a 'cd $TMP' line
>> > tar xvf $MYSRC/$PRGNAM-$VERSION.tar.gz -C $TMP
>>
>> Good plan.
>>
>> I'd rather call it SRCDIR or something, but that's nitpicking.
>> _______________________________________________
>> 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/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130806/ac1dc3f9/attachment.html>

From slackbuilds at jq.oc9.com  Wed Aug  7 01:14:04 2013
From: slackbuilds at jq.oc9.com (slackbuilds at jq.oc9.com)
Date: Tue, 6 Aug 2013 21:14:04 -0400 (EDT)
Subject: [Slackbuilds-users] RFC: changing .SlackBuild to allow separate
 source tree
In-Reply-To: <CA+xNRHfx6Knt17Z=e8H-5S_Ku1pCMxkD9X_Dq6J1fO_98E5OQQ@mail.gmail.com>
References: <51FF3137.1000203@gmail.com>
	<CAN1hMuCK4-CK6PTTXqxzjsgk3Y+w5kB+TnRdiiP4_uP18pbGaQ@mail.gmail.com>
	<CAA62KfRrQ4AS+tR3fZbf+dX71ggMJ=Lw2FyWFPK=jJGJ+uFhsw@mail.gmail.com>
	<CA+xNRHfx6Knt17Z=e8H-5S_Ku1pCMxkD9X_Dq6J1fO_98E5OQQ@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1308062106130.20732@java14.oc9.com>


On Tue, 6 Aug 2013, Nick Blizzard wrote:

> some tweak of this usually works for me (shamelessly stole from pats
> scripts)
>
> VERSION=${VERSION:-$(echo ${PRGNAM}-*.tar.?z* | rev | cut -f 3- -d . | cut
> -f 1 -d - | rev)}
>
> at most I have to tweak the 3 and 1 for how the source package gets
> named... pair with a download script that pulls from the info... and it
> just works.
>
>
>
> On Tue, Aug 6, 2013 at 8:23 PM, Miguel De Anda <miguel at thedeanda.com> wrote:
>
>> I'd be more interested in having the template pull variables off the .info
>> file. I often find myself updating version numbers in lots of files when
>> doing it once would normally be quicker and cleaner.
>>
>>
>> On Tue, Aug 6, 2013 at 3:20 PM, B Watson <yalhcru at gmail.com> wrote:
>>
>>> On 8/5/13, King Beowulf <kingbeowulf at gmail.com> wrote:
>>>> What do you think of change to the slackbuild template along the lines
>>> of:
>>>>
>>>> ...
>>>> MYSRC=${MYSRC:-$CWD}
>>>> ...
>>>> # with -C don't need a 'cd $TMP' line
>>>> tar xvf $MYSRC/$PRGNAM-$VERSION.tar.gz -C $TMP
>>>
>>> Good plan.
>>>
>>> I'd rather call it SRCDIR or something, but that's nitpicking.
>>> _______________________________________________

What about the md5 sums ? I noticed that I do not need to update them so 
what kind of install/build script uses them?

Just curious...

$ cat  linphone.info
PRGNAM="linphone"
VERSION="3.5.2"
HOMEPAGE="http://www.linphone.org/"
DOWNLOAD="http://download-mirror.savannah.gnu.org/releases/linphone/3.5.x/sources/linphone-3.5.2.tar.gz"
MD5SUM="4be6e940372dba1f6793aef849c1ff0d"
...

-ls

From yalhcru at gmail.com  Wed Aug  7 03:20:23 2013
From: yalhcru at gmail.com (B Watson)
Date: Tue, 6 Aug 2013 23:20:23 -0400
Subject: [Slackbuilds-users] RFC: changing .SlackBuild to allow separate
 source tree
In-Reply-To: <Pine.LNX.4.64.1308062106130.20732@java14.oc9.com>
References: <51FF3137.1000203@gmail.com>
	<CAN1hMuCK4-CK6PTTXqxzjsgk3Y+w5kB+TnRdiiP4_uP18pbGaQ@mail.gmail.com>
	<CAA62KfRrQ4AS+tR3fZbf+dX71ggMJ=Lw2FyWFPK=jJGJ+uFhsw@mail.gmail.com>
	<CA+xNRHfx6Knt17Z=e8H-5S_Ku1pCMxkD9X_Dq6J1fO_98E5OQQ@mail.gmail.com>
	<Pine.LNX.4.64.1308062106130.20732@java14.oc9.com>
Message-ID: <CAN1hMuBeK85Q+VUeR-GJtqExo=cUQjMaVRczgjmjNrNKzUN4og@mail.gmail.com>

On 8/6/13, slackbuilds at jq.oc9.com <slackbuilds at jq.oc9.com> wrote:
> What about the md5 sums ? I noticed that I do not need to update them so
> what kind of install/build script uses them?

sbopkg uses them, so does sbotools. People manually running SlackBuild
scripts should use them, and I'm sure I'm not the only one here who
wrote my own slackbuild automater script that uses them...

As it stands now, the .SlackBuild scripts themselves don't check the
md5sums. If we're voting, I vote to keep it that way.

From dave at dawoodfall.net  Wed Aug  7 07:29:47 2013
From: dave at dawoodfall.net (David Woodfall)
Date: Wed, 7 Aug 2013 08:29:47 +0100
Subject: [Slackbuilds-users] RFC: changing .SlackBuild to allow separate
 source tree
In-Reply-To: <CAN1hMuBeK85Q+VUeR-GJtqExo=cUQjMaVRczgjmjNrNKzUN4og@mail.gmail.com>
References: <51FF3137.1000203@gmail.com>
	<CAN1hMuCK4-CK6PTTXqxzjsgk3Y+w5kB+TnRdiiP4_uP18pbGaQ@mail.gmail.com>
	<CAA62KfRrQ4AS+tR3fZbf+dX71ggMJ=Lw2FyWFPK=jJGJ+uFhsw@mail.gmail.com>
	<CA+xNRHfx6Knt17Z=e8H-5S_Ku1pCMxkD9X_Dq6J1fO_98E5OQQ@mail.gmail.com>
	<Pine.LNX.4.64.1308062106130.20732@java14.oc9.com>
	<CAN1hMuBeK85Q+VUeR-GJtqExo=cUQjMaVRczgjmjNrNKzUN4og@mail.gmail.com>
Message-ID: <20130807082947.166f7612@raven.thebigvoid.org>

On Tue, 6 Aug 2013 23:20:23 -0400
B Watson <yalhcru at gmail.com> wrote:

> On 8/6/13, slackbuilds at jq.oc9.com <slackbuilds at jq.oc9.com> wrote:
> > What about the md5 sums ? I noticed that I do not need to update
> > them so what kind of install/build script uses them?
> 
> sbopkg uses them, so does sbotools. People manually running SlackBuild
> scripts should use them, and I'm sure I'm not the only one here who
> wrote my own slackbuild automater script that uses them...
> 
> As it stands now, the .SlackBuild scripts themselves don't check the
> md5sums. If we're voting, I vote to keep it that way.

I agree with that. They are there for a good reason, and that is for
the maintainer to check. Also I don't think it's a good idea to add
unnecessary things like SRCDIR to the .infos. They should be
independent of any local settings that a person may want to set and are
there for information.

Although it seems like a good idea to add a MYSRC to the slackbuild,
you could just as well do a ln -s /where/the/source/is/source.tar.xz .
and then run the slackbuild.

Either way you're typing extra bumf. It's seems much easier to me and
do a 'source *info && wget $DOWNLOAD'

Just my two pennies worth.

D.



From kingbeowulf at gmail.com  Wed Aug  7 15:36:39 2013
From: kingbeowulf at gmail.com (King Beowulf)
Date: Wed, 07 Aug 2013 08:36:39 -0700
Subject: [Slackbuilds-users] RFC: changing .SlackBuild to allow separate
 source tree
In-Reply-To: <20130807082947.166f7612@raven.thebigvoid.org>
References: <51FF3137.1000203@gmail.com>
	<CAN1hMuCK4-CK6PTTXqxzjsgk3Y+w5kB+TnRdiiP4_uP18pbGaQ@mail.gmail.com>
	<CAA62KfRrQ4AS+tR3fZbf+dX71ggMJ=Lw2FyWFPK=jJGJ+uFhsw@mail.gmail.com>
	<CA+xNRHfx6Knt17Z=e8H-5S_Ku1pCMxkD9X_Dq6J1fO_98E5OQQ@mail.gmail.com>
	<Pine.LNX.4.64.1308062106130.20732@java14.oc9.com>
	<CAN1hMuBeK85Q+VUeR-GJtqExo=cUQjMaVRczgjmjNrNKzUN4og@mail.gmail.com>
	<20130807082947.166f7612@raven.thebigvoid.org>
Message-ID: <52026987.30202@gmail.com>

On 08/07/2013 12:29 AM, David Woodfall wrote:
---snip----
> 
> Although it seems like a good idea to add a MYSRC to the slackbuild,
> you could just as well do a ln -s /where/the/source/is/source.tar.xz .
> and then run the slackbuild.
> 
> Either way you're typing extra bumf. It's seems much easier to me and
> do a 'source *info && wget $DOWNLOAD'
> 
> Just my two pennies worth.
> 
> D.
> 

Yep, used to do that way back but got tired of creating/fixing links all
the time. The problem with 'ln -s' is when updating the slackbuild
script tree, as in a git pull from SBo or elsewhere.  It will be also a
problem when doing a git push, or, say, making a tar.gz t upload to SBo.
The link still puts a "source file" in that directory.  Instead of
dealing with the source, you have to deal with the link. Since SBo
script packages don't have links, you have to add a step each time to
create one, or make sure you don't stomp on one, when getting a fresh copy.

-Ed


From dchmelik at hipplanet.com  Wed Aug  7 17:05:37 2013
From: dchmelik at hipplanet.com (David Melik)
Date: Wed, 7 Aug 2013 10:05:37 -0700
Subject: [Slackbuilds-users] questions if the SlackBuilds team helped me
 with the Moria SlackBuild, and on the license in the template, etc.
Message-ID: <20130807100537.1223205E@resin03.mta.everyone.net>

I considered how to license my SlackBuilds. I just added the license in the template. However, I took over the Angband game SlackBuild in the last year or few, but the previous was unlicensed--what do I do? Also, someone who I think is on the SlackBuilds team helped me with the Moria game build, so can I make it copyright me and that person, or--if it cannot be found who it was--the team? Unfortunately I have no IRC log from talking to him, and I deleted much of my old email from both GMail and my hard drive.

David
http://www.cwu.edu/~melikd/


_____________________________________________________________
Find out what's HIP!
Visit Hip Planet for news, shopping, forums, chatrooms, free personal and classified ads and much more!
Get FREE E-MAIL! at HipPlanet now!

It's all waiting for you, at http://www.hipplanet.com

From dchmelik at hipplanet.com  Wed Aug  7 17:29:15 2013
From: dchmelik at hipplanet.com (David Melik)
Date: Wed, 7 Aug 2013 10:29:15 -0700
Subject: [Slackbuilds-users] questions if the SlackBuilds team helped me
 with the Moria SlackBuild, and on the license in the template, etc.
Message-ID: <20130807102915.12372598@m0005299.ppops.net>

--- dchmelik at hipplanet.com wrote:
After looking more in my mboxes to see who helped me with Moria, I found a corrupt 'mail' consisting of a couple mails, and I think Robby Workman helped (and maybe someone else on IRC):

"Why do we need that big Debian diff?  Also, I think you found the least intuitive way possible to build that; I'll have some fixes for that when I add it.  If the Debian diff is really needed, you can send me a diff after I get it added, or resubmit based on the repo version after 14.0 releases.  Also, I'll remind you yet again that the extraneous comments in build scripts are supposed to be removed.

-RW"


So, Robby made the diff smaller, but I forgot if he wrote the commands that use it and ones that fix the Makefile (or if someone else on IRC did and if I changed the diff name in the script). So, when I upload with the SlackBuilds license, do I put copyright me and Robby (and whoever else may have been involved), and/or the SlackBuilds team...? It is not as big a deal to me as much as the fact that apparently it needs a license--even BSD-type--to be considered Free/Libre software, and so maybe for anyone to ever take it over easily in the future.

David


_____________________________________________________________
Find out what's HIP!
Visit Hip Planet for news, shopping, forums, chatrooms, free personal and classified ads and much more!
Get FREE E-MAIL! at HipPlanet now!

It's all waiting for you, at http://www.hipplanet.com

From klaatu at straightedgelinux.com  Wed Aug  7 17:42:16 2013
From: klaatu at straightedgelinux.com (Klaatu)
Date: Wed, 07 Aug 2013 13:42:16 -0400
Subject: [Slackbuilds-users] questions if the SlackBuilds team helped me
	with the Moria SlackBuild, and on the license in the template, etc.
In-Reply-To: <20130807102915.12372598@m0005299.ppops.net>
References: <20130807102915.12372598@m0005299.ppops.net>
Message-ID: <2300757.7Y2eutt7d5@slackk>

I'm no lawyer, but as far as I know, nothing in the US copyright code prevents 
you from assigning copyright to yourself AND someone else.

Adding a BSD/MIT style license is indeed recommended. I have found an even 
shorter license with the Gnu All-Permissive license; it seems to be exactly 
the same as a BSD style license but in only 4 or 5 lines of text.

I believe you should be able to do add such a permissive license regardless of 
the slackbuild's origin; if a previous maintainer did not specify a license, 
then that iinherently does not prevent you from licensing it in any way you 
please.

Again, not a lawyer, not giving legal advice.

-klaatu


On Wednesday, August 07, 2013 10:29:15 AM David Melik wrote:
> --- dchmelik at hipplanet.com wrote:
> After looking more in my mboxes to see who helped me with Moria, I found a
> corrupt 'mail' consisting of a couple mails, and I think Robby Workman
> helped (and maybe someone else on IRC):
> 
> "Why do we need that big Debian diff?  Also, I think you found the least
> intuitive way possible to build that; I'll have some fixes for that when I
> add it.  If the Debian diff is really needed, you can send me a diff after
> I get it added, or resubmit based on the repo version after 14.0 releases. 
> Also, I'll remind you yet again that the extraneous comments in build
> scripts are supposed to be removed.
> 
> -RW"
> 
> 
> So, Robby made the diff smaller, but I forgot if he wrote the commands that
> use it and ones that fix the Makefile (or if someone else on IRC did and if
> I changed the diff name in the script). So, when I upload with the
> SlackBuilds license, do I put copyright me and Robby (and whoever else may
> have been involved), and/or the SlackBuilds team...? It is not as big a
> deal to me as much as the fact that apparently it needs a license--even
> BSD-type--to be considered Free/Libre software, and so maybe for anyone to
> ever take it over easily in the future.
> 
> David
> 
> 
> _____________________________________________________________
> Find out what's HIP!
> Visit Hip Planet for news, shopping, forums, chatrooms, free personal and
> classified ads and much more! Get FREE E-MAIL! at HipPlanet now!
> 
> It's all waiting for you, at http://www.hipplanet.com
> _______________________________________________
> 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/
- klaatu

From slackbuilds at jq.oc9.com  Thu Aug  8 04:04:24 2013
From: slackbuilds at jq.oc9.com (slackbuilds at jq.oc9.com)
Date: Thu, 8 Aug 2013 00:04:24 -0400 (EDT)
Subject: [Slackbuilds-users] ipset on 3.2 kernels/slackware 14.0
In-Reply-To: <52026987.30202@gmail.com>
References: <51FF3137.1000203@gmail.com>
	<CAN1hMuCK4-CK6PTTXqxzjsgk3Y+w5kB+TnRdiiP4_uP18pbGaQ@mail.gmail.com>
	<CAA62KfRrQ4AS+tR3fZbf+dX71ggMJ=Lw2FyWFPK=jJGJ+uFhsw@mail.gmail.com>
	<CA+xNRHfx6Knt17Z=e8H-5S_Ku1pCMxkD9X_Dq6J1fO_98E5OQQ@mail.gmail.com>
	<Pine.LNX.4.64.1308062106130.20732@java14.oc9.com>
	<CAN1hMuBeK85Q+VUeR-GJtqExo=cUQjMaVRczgjmjNrNKzUN4og@mail.gmail.com>
	<20130807082947.166f7612@raven.thebigvoid.org>
	<52026987.30202@gmail.com>
Message-ID: <Pine.LNX.4.64.1308072350270.20732@java14.oc9.com>


Hello all,

Anybody here got any success running ipset on 3.2 kernels/Slackware 14? 
Most docs and googling say 2.4 and 2.6 kernels supported, even ipset home 
page and the slackbuilds page for slackware 14, which comes with kernel 
3.2 by default I think...

slackbuilds.org/repository/14.0/network/ipset/

I might give it a shot anyway but heads-ups would be great.

-ls

From Hullen at t-online.de  Thu Aug  8 09:53:00 2013
From: Hullen at t-online.de (Helmut Hullen)
Date: 08 Aug 2013 11:53:00 +0200
Subject: [Slackbuilds-users] "stress" homepage has moved
Message-ID: <CbU5CabeCXB@helmut.hullen.de>

Hallo, slackbuilds-users,

   http://slackbuilds.org/repository/14.0/system/stress/

mentions as homepage

   http://weather.ou.edu/~apw/projects/stress/

but that page is unreachable (and the source code packet too).

Is there any help?

Viele Gruesse!
Helmut

From vbatts at gmail.com  Thu Aug  8 14:26:44 2013
From: vbatts at gmail.com (Vincent Batts)
Date: Thu, 8 Aug 2013 10:26:44 -0400
Subject: [Slackbuilds-users] "stress" homepage has moved
In-Reply-To: <CbU5CabeCXB@helmut.hullen.de>
References: <CbU5CabeCXB@helmut.hullen.de>
Message-ID: <CAN6Zp5za4jOJ72HoiZs=dUJBtNnoATvLQZoXvEFUn9V579+5zA@mail.gmail.com>

that's unfortunate. The matching md5 source tarball is currently on
fedora's source repo [1]. We could yank it and host is somewhere. It's only
197k.

Take care,
vb

[1]
http://pkgs.fedoraproject.org/repo/pkgs/stress/stress-1.0.4.tar.gz/a607afa695a511765b40993a64c6e2f4/


On Thu, Aug 8, 2013 at 5:53 AM, Helmut Hullen <Hullen at t-online.de> wrote:

> Hallo, slackbuilds-users,
>
>    http://slackbuilds.org/repository/14.0/system/stress/
>
> mentions as homepage
>
>    http://weather.ou.edu/~apw/projects/stress/
>
> but that page is unreachable (and the source code packet too).
>
> Is there any help?
>
> Viele Gruesse!
> Helmut
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130808/cd6c329a/attachment-0001.html>

From ronayne.thomas at gmail.com  Thu Aug  8 15:11:12 2013
From: ronayne.thomas at gmail.com (Thomas Ronayne)
Date: Thu, 08 Aug 2013 11:11:12 -0400
Subject: [Slackbuilds-users] Apache Tomcat Upgrade to Current Version
Message-ID: <5203B510.6020002@gmail.com>

Hi,

Apache Tomcat is at v. 7.0.42 (the SlackBuilds.org is at 7.0.22, which 
has memory leaks).

Any chance of an upgrade (or does anybody know for sure that the current 
SlackBuild will correctly build 7.0.42)?

Thanks.

-- 
A riddle, wrapped in a mystery, inside an enigma but that's my story and I'm stickin' to it.


From Hullen at t-online.de  Thu Aug  8 15:18:00 2013
From: Hullen at t-online.de (Helmut Hullen)
Date: 08 Aug 2013 17:18:00 +0200
Subject: [Slackbuilds-users] "stress" homepage has moved
In-Reply-To: <CAN6Zp5za4jOJ72HoiZs=dUJBtNnoATvLQZoXvEFUn9V579+5zA@mail.gmail.com>
Message-ID: <CbU5zbLuCXB@helmut.hullen.de>

Hallo, Vincent,

Du meintest am 08.08.13:

> that's unfortunate. The matching md5 source tarball is currently on
> fedora's source repo [1]. We could yank it and host is somewhere.
> It's only 197k.

> Take care,
> vb

> [1]
> http://pkgs.fedoraproject.org/repo/pkgs/stress/stress-1.0.4.tar.gz/a6
> 07afa695a511765b40993a64c6e2f4/

It works - thank you!

Viele Gruesse!
Helmut

From dchmelik at hipplanet.com  Fri Aug  9 02:07:07 2013
From: dchmelik at hipplanet.com (David Melik)
Date: Thu, 8 Aug 2013 19:07:07 -0700
Subject: [Slackbuilds-users] questions if the SlackBuilds team helped me
 with theMoria SlackBuild, and on the license in the template, etc.
Message-ID: <20130808190707.122C895B@resin04.mta.everyone.net>

--- timp at timp.com.au wrote:
>The Submission form says that anything without a license in the file will be
>considered to be Public Domain:
>
>"If you do not specify a license, then your submission is assumed to be public
>domain, and as such, anyone can freely modify and/or distribute it with no
>restrictions."

Ok, great. There is still the question of attributing the person or people who wrote small parts of my Moria script... if they were ok with it being public domain, I do not know if they want me to, if someone might ask them questions, like if someone took the script over from me (and might ask them as well)... but I want to give him/them credit for their work. So, should I write Robby's (and the other person, if there was one, or 'The SlackBuilds Project') name after mine in the copyright, or will that complicate things?

D


_____________________________________________________________
Find out what's HIP!
Visit Hip Planet for news, shopping, forums, chatrooms, free personal and classified ads and much more!
Get FREE E-MAIL! at HipPlanet now!

It's all waiting for you, at http://www.hipplanet.com

From jgeboski at gmail.com  Sun Aug 11 02:09:02 2013
From: jgeboski at gmail.com (James Geboski)
Date: Sat, 10 Aug 2013 22:09:02 -0400
Subject: [Slackbuilds-users] Chromium SlackBuild
Message-ID: <CAB61YWMa9hRoFJFf0ckOWa3UPOW3DeXK_JGj7JtD-6Jt9jCHnQ@mail.gmail.com>

Hello all,

A little over two weeks ago (July 26), I contacted the maintainer of the
Chromium SlackBuild, Francisco Ambrozio.  I still have yet to hear back
from Francisco on issues pertaining to the Chromium SlackBuild.  There are
two key issues with the SlackBuild: 1) it is four releases behind; 2) it is
missing Google API keys.

Updating the SlackBuild is a trivial matter, but obtaining a set of Google
API keys is going to require a bit more effort.  As of chromium-23, API
keys are needed to access the Google APIs.  I have never noticed an issue
with the older API protocol versions in chromium =< 28, however, in
chromium >= 29, there is a notification informing the end-user that they
need to obtain a set of API keys.  Additionally, I have noticed that API
features are no longer working, including the login all together.

Other distributions have obtained "distribution" API keys, namely Arch and
Gentoo.  Since I doubt chromium will ever be included in Slackware, that
makes SlackBuilds.org the next target for obtaining these keys.  While I
currently maintain my own "fork" of the chromium SlackBuild, it's not
logical for me to reach out for a set of distribution keys.  If I can take
over and maintain the Chromium SlackBuild, I would like to reach out
upstream to obtain a set of distribution keys for SlackBuilds.org.

Would it be possible for me to take over and maintain the Chromium
SlackBuild?

Thanks in advance,
James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130810/27fcd99a/attachment.html>

From ml at mareichelt.com  Sun Aug 11 12:21:56 2013
From: ml at mareichelt.com (Markus Reichelt)
Date: Sun, 11 Aug 2013 14:21:56 +0200
Subject: [Slackbuilds-users] Chromium SlackBuild
In-Reply-To: <CAB61YWMa9hRoFJFf0ckOWa3UPOW3DeXK_JGj7JtD-6Jt9jCHnQ@mail.gmail.com>
References: <CAB61YWMa9hRoFJFf0ckOWa3UPOW3DeXK_JGj7JtD-6Jt9jCHnQ@mail.gmail.com>
Message-ID: <20130811122156.GB18319@pc21.mareichelt.com>

* James Geboski <jgeboski at gmail.com> wrote:

> A little over two weeks ago (July 26), I contacted the maintainer
> of the Chromium SlackBuild, Francisco Ambrozio.  I still have yet
> to hear back from Francisco on issues pertaining to the Chromium
> SlackBuild.  There are two key issues with the SlackBuild: 1) it is
> four releases behind; 2) it is missing Google API keys.

pardon me for being frank:

a) in my book, giving the maintainer four (4) weeks to respond is ok,
only if there's no reply after that it's ok to push for taking over
maintainership.  AFAIK, there's no official 'window of slacking'; of
course there's key system components / add-ons where things might be
dealt with faster with good reason (flash-player and a propriety
browser come to mind);

b) if the script works by just adapting $VERSION, that's ok. 
Maintainers are not obligated (yet?) to keep up with upstream for
such trivial things.

c) what exactly is the impact of (not) having google API keys as
maintainer in this context of taking over maintainership?  As you
stated, the SBo project should 'get them'; Does this need to be
happening right now or is this a general good strategy to have in
place for future chromium integration?  If so, how's the handling of
the API keys for projects at SBo documented?

d) I'm not a chromium user, so bare with me. Thanks.


-- 
The Tahoe-LAFS spirit.

From jgeboski at gmail.com  Sun Aug 11 17:50:29 2013
From: jgeboski at gmail.com (James Geboski)
Date: Sun, 11 Aug 2013 13:50:29 -0400
Subject: [Slackbuilds-users] Chromium SlackBuild
In-Reply-To: <20130811122156.GB18319@pc21.mareichelt.com>
References: <CAB61YWMa9hRoFJFf0ckOWa3UPOW3DeXK_JGj7JtD-6Jt9jCHnQ@mail.gmail.com>
	<20130811122156.GB18319@pc21.mareichelt.com>
Message-ID: <CAB61YWM94t+ky8UB6Y6GVrbqfM3aBZbcaz6pLQPk3KMjZh8pjQ@mail.gmail.com>

> a) in my book, giving the maintainer four (4) weeks to respond is ok,
> only if there's no reply after that it's ok to push for taking over
> maintainership.  AFAIK, there's no official 'window of slacking'; of
> course there's key system components / add-ons where things might be
> dealt with faster with good reason (flash-player and a propriety
> browser come to mind);

I was told two weeks by an SBo admin via IRC.

> b) if the script works by just adapting $VERSION, that's ok.
> Maintainers are not obligated (yet?) to keep up with upstream for
> such trivial things.

No, just switching the version will not work.  Chromium has switched
to a new build system, ninja, since the version posted on SBo.  Other
minor changes are required as well.

> c) what exactly is the impact of (not) having google API keys as
> maintainer in this context of taking over maintainership?  As you
> stated, the SBo project should 'get them'; Does this need to be
> happening right now or is this a general good strategy to have in
> place for future chromium integration?  If so, how's the handling of
> the API keys for projects at SBo documented?

http://www.chromium.org/developers/how-tos/api-keys
https://groups.google.com/a/chromium.org/d/msg/chromium-dev/Qks4W0xLxqc/MVhyo3o0JgoJ

James

On Sun, Aug 11, 2013 at 8:21 AM, Markus Reichelt <ml at mareichelt.com> wrote:
>
> * James Geboski <jgeboski at gmail.com> wrote:
>
> > A little over two weeks ago (July 26), I contacted the maintainer
> > of the Chromium SlackBuild, Francisco Ambrozio.  I still have yet
> > to hear back from Francisco on issues pertaining to the Chromium
> > SlackBuild.  There are two key issues with the SlackBuild: 1) it is
> > four releases behind; 2) it is missing Google API keys.
>
> pardon me for being frank:
>
> a) in my book, giving the maintainer four (4) weeks to respond is ok,
> only if there's no reply after that it's ok to push for taking over
> maintainership.  AFAIK, there's no official 'window of slacking'; of
> course there's key system components / add-ons where things might be
> dealt with faster with good reason (flash-player and a propriety
> browser come to mind);
>
> b) if the script works by just adapting $VERSION, that's ok.
> Maintainers are not obligated (yet?) to keep up with upstream for
> such trivial things.
>
> c) what exactly is the impact of (not) having google API keys as
> maintainer in this context of taking over maintainership?  As you
> stated, the SBo project should 'get them'; Does this need to be
> happening right now or is this a general good strategy to have in
> place for future chromium integration?  If so, how's the handling of
> the API keys for projects at SBo documented?
>
> d) I'm not a chromium user, so bare with me. Thanks.
>
>
> --
> The Tahoe-LAFS spirit.
> _______________________________________________
> 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 jbernts at broadpark.no  Mon Aug 12 16:12:29 2013
From: jbernts at broadpark.no (Jostein Berntsen)
Date: Mon, 12 Aug 2013 18:12:29 +0200
Subject: [Slackbuilds-users] feh
In-Reply-To: <CAN1hMuB20-F+4NtZ7PXmhj1vKfoPoqxokQZqgukdFp_0rWd2yA@mail.gmail.com>
References: <CAKpSnpKBVNyJx_PbRvV7Y9MfbcSkKC4mveQcWS7TmPyJXDpUfw@mail.gmail.com>
	<loom.20130325T064605-928@post.gmane.org>
	<CAN1hMuB20-F+4NtZ7PXmhj1vKfoPoqxokQZqgukdFp_0rWd2yA@mail.gmail.com>
Message-ID: <20130812161229.GE477@jostein>

On 25.03.13,14:56, B Watson wrote:
> On 3/25/13, joe <gmane at csrc.com> wrote:
> > +  CFLAGS="-g $SLKCFLAGS -Wall -Wextra -pedantic -DPREFIX=\\\"/usr\\\"
> > -DHAVE_LIBCURL -DHAVE_LIBXINERAMA -DPACKAGE=\\\"$PRGNAME\\\"
> > -DVERSION=\\\"$VERSION\\\""
> 
> It probably would make more sense (and be less brittle) for things like that
> to use a bit of sed:
> 
> sed -i "/CFLAGS=/s,-g,$SLKCFLAGS" Makefile
> 
> (Untested, I haven't looked at the feh source, just an example)

Any news on an updated feh build since this does not work very well?

Jostein



From info at microlinux.fr  Thu Aug 15 10:46:00 2013
From: info at microlinux.fr (Niki Kovacs)
Date: Thu, 15 Aug 2013 12:46:00 +0200
Subject: [Slackbuilds-users] Transmission: transmission-qt client does not
	load translations
Message-ID: <520CB168.3040009@microlinux.fr>

Hi,

I've been using Transmission for the last five years or so, it's my 
favourite BitTorrent client. Until recently I've always used the 
transmission-gtk client, since it integrates nicely into Xfce.

Currently I'm fiddling with my personal blend of KDE, so I thought I'd 
rather use the transmission-qt client. The program seems to work OK, but :

1) There's no desktop entry for the Qt client. Which is not a big deal, 
since I can simply create one manually and/or fire it up from a 
graphical terminal.

2) Translations aren't loaded, the Qt client only displays the interface 
in english. My workstation uses fr_FR.utf8 as locale, and sometimes 
de_DE.utf8.

I googled about this (transmission-qt translation), and the problem 
seems to affect many users. Various bug reports suggest to simply 
update, but version 2.77 (from SBo) is still affected by it. And I've 
found no usable solution for this yet.

Any suggestions?

Niki

PS: Niels, I'm forwarding this to you, since you're the maintainer.
-- 
Microlinux - Solutions informatiques 100% Linux et logiciels libres
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 markus.ka.rinne at gmail.com  Sat Aug 17 12:01:23 2013
From: markus.ka.rinne at gmail.com (Markus Rinne)
Date: Sat, 17 Aug 2013 15:01:23 +0300
Subject: [Slackbuilds-users] postgresql and pgadmin3 version compatibility
Message-ID: <20130817120123.GA6359@tursas>

Hi,

I installed postgresql and pgadmin3 from SlackBuilds.  When I start
pgadmin3, a warning dialog is shown with this message:

"This version of pgAdmin has only been tested with PostgreSQL version
9.0 and below and may not function correctly with this server.  Please
upgrade pgAdmin."

Maybe pgadmin3 needs to be upgraded?  The first pgadmin3 version that
doesn't show this warning is 1.16.0.

    Markus

From larryhaja at gmail.com  Sun Aug 18 00:04:09 2013
From: larryhaja at gmail.com (Larry Hajali)
Date: Sat, 17 Aug 2013 17:04:09 -0700
Subject: [Slackbuilds-users] Transmission: transmission-qt client does
 not load translations
In-Reply-To: <520CB168.3040009@microlinux.fr>
References: <520CB168.3040009@microlinux.fr>
Message-ID: <CAAZPBMhHagxZUGBMZjxXg-1eHfDafKWYggiRMys2WGy2f_18PQ@mail.gmail.com>

1) Qt desktop file is in transmission-$VERSION/qt/transmission-qt.desktop.
 Easy enough to add a line in the slackbuild to install the Qt desktop file.

2) I haven't tried it but gentoo has a translation patch for
transmission-qt.

Version 2.77:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-p2p/transmission/files/transmission-2.77-translations-path-fix.patch?revision=1.1&pathrev=MAIN

Version 2.80:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-p2p/transmission/files/transmission-2.80-translations-path-fix.patch?revision=1.1&pathrev=MAIN

Larry


On Thu, Aug 15, 2013 at 3:46 AM, Niki Kovacs <info at microlinux.fr> wrote:

> Hi,
>
> I've been using Transmission for the last five years or so, it's my
> favourite BitTorrent client. Until recently I've always used the
> transmission-gtk client, since it integrates nicely into Xfce.
>
> Currently I'm fiddling with my personal blend of KDE, so I thought I'd
> rather use the transmission-qt client. The program seems to work OK, but :
>
> 1) There's no desktop entry for the Qt client. Which is not a big deal,
> since I can simply create one manually and/or fire it up from a graphical
> terminal.
>
> 2) Translations aren't loaded, the Qt client only displays the interface
> in english. My workstation uses fr_FR.utf8 as locale, and sometimes
> de_DE.utf8.
>
> I googled about this (transmission-qt translation), and the problem seems
> to affect many users. Various bug reports suggest to simply update, but
> version 2.77 (from SBo) is still affected by it. And I've found no usable
> solution for this yet.
>
> Any suggestions?
>
> Niki
>
> PS: Niels, I'm forwarding this to you, since you're the maintainer.
> --
> Microlinux - Solutions informatiques 100% Linux et logiciels libres
> 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 <SlackBuilds-users at slackbuilds.org>
> http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**users<http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> Archives - http://lists.slackbuilds.org/**pipermail/slackbuilds-users/<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/20130817/58a40872/attachment.html>

From info at microlinux.fr  Sun Aug 18 04:52:22 2013
From: info at microlinux.fr (Niki Kovacs)
Date: Sun, 18 Aug 2013 06:52:22 +0200
Subject: [Slackbuilds-users] Transmission: transmission-qt client does
 not load translations
In-Reply-To: <CAAZPBMhHagxZUGBMZjxXg-1eHfDafKWYggiRMys2WGy2f_18PQ@mail.gmail.com>
References: <520CB168.3040009@microlinux.fr>
	<CAAZPBMhHagxZUGBMZjxXg-1eHfDafKWYggiRMys2WGy2f_18PQ@mail.gmail.com>
Message-ID: <52105306.3020602@microlinux.fr>

Le 18/08/2013 02:04, Larry Hajali a ?crit :
> 1) Qt desktop file is in
> transmission-$VERSION/qt/transmission-qt.desktop.  Easy enough to add a
> line in the slackbuild to install the Qt desktop file.
>
> 2) I haven't tried it but gentoo has a translation patch for
> transmission-qt.
>
> Version 2.77:
> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-p2p/transmission/files/transmission-2.77-translations-path-fix.patch?revision=1.1&pathrev=MAIN
>
> Version 2.80:
> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-p2p/transmission/files/transmission-2.80-translations-path-fix.patch?revision=1.1&pathrev=MAIN
>
> Larry

Thanks very much! I'll give this a spin.

Niki

-- 
Microlinux - Solutions informatiques 100% Linux et logiciels libres
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 niels.horn at gmail.com  Sun Aug 18 13:39:45 2013
From: niels.horn at gmail.com (Niels Horn)
Date: Sun, 18 Aug 2013 10:39:45 -0300
Subject: [Slackbuilds-users] Transmission: transmission-qt client does
 not load translations
In-Reply-To: <52105306.3020602@microlinux.fr>
References: <520CB168.3040009@microlinux.fr>
	<CAAZPBMhHagxZUGBMZjxXg-1eHfDafKWYggiRMys2WGy2f_18PQ@mail.gmail.com>
	<52105306.3020602@microlinux.fr>
Message-ID: <CAOrTnKpfmjktKPJ=FxcAafuGahoZ5DpH-Txr9P3BVyJF8LSa4A@mail.gmail.com>

Larry,

Thanks for the hints! I'm hopelessly behind with responding personal e-mail
and other non-job-related tasks.

Niki,

if it works, please tell us.
I only use xfce, so rarely test the qt version of Transmission.

Regards,

--
Niels Horn


On Sun, Aug 18, 2013 at 1:52 AM, Niki Kovacs <info at microlinux.fr> wrote:

> Le 18/08/2013 02:04, Larry Hajali a ?crit :
>
>  1) Qt desktop file is in
>> transmission-$VERSION/qt/**transmission-qt.desktop.  Easy enough to add a
>> line in the slackbuild to install the Qt desktop file.
>>
>> 2) I haven't tried it but gentoo has a translation patch for
>> transmission-qt.
>>
>> Version 2.77:
>> http://sources.gentoo.org/cgi-**bin/viewvc.cgi/gentoo-x86/net-**
>> p2p/transmission/files/**transmission-2.77-**translations-path-fix.patch?
>> **revision=1.1&pathrev=MAIN<http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-p2p/transmission/files/transmission-2.77-translations-path-fix.patch?revision=1.1&pathrev=MAIN>
>>
>> Version 2.80:
>> http://sources.gentoo.org/cgi-**bin/viewvc.cgi/gentoo-x86/net-**
>> p2p/transmission/files/**transmission-2.80-**translations-path-fix.patch?
>> **revision=1.1&pathrev=MAIN<http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-p2p/transmission/files/transmission-2.80-translations-path-fix.patch?revision=1.1&pathrev=MAIN>
>>
>> Larry
>>
>
> Thanks very much! I'll give this a spin.
>
> Niki
>
>
> --
> Microlinux - Solutions informatiques 100% Linux et logiciels libres
> 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 <SlackBuilds-users at slackbuilds.org>
> http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**users<http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> Archives - http://lists.slackbuilds.org/**pipermail/slackbuilds-users/<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/20130818/123c5ad9/attachment.html>

From adis at linux.org.ba  Mon Aug 19 15:02:56 2013
From: adis at linux.org.ba (Adis Nezirovic)
Date: Mon, 19 Aug 2013 17:02:56 +0200
Subject: [Slackbuilds-users] postgresql and pgadmin3 version
	compatibility
In-Reply-To: <20130817120123.GA6359@tursas>
References: <20130817120123.GA6359@tursas>
Message-ID: <CALHPnviJw5tmLn7Zfde5Cy9B0sOKot33A0PWAXK1T-+vHye8Nw@mail.gmail.com>

Basically, for the last few versions pgAdmin follows the PostgreSQL
release, so we have pairs (1.12, 9.0), (1.14, 9.1), (1.16, 9.2).

It's also safe to use "new" pgAdmin on older PostgreSQL version.


Best regards,
Adis


On Sat, Aug 17, 2013 at 2:01 PM, Markus Rinne <markus.ka.rinne at gmail.com>wrote:

> Hi,
>
> I installed postgresql and pgadmin3 from SlackBuilds.  When I start
> pgadmin3, a warning dialog is shown with this message:
>
> "This version of pgAdmin has only been tested with PostgreSQL version
> 9.0 and below and may not function correctly with this server.  Please
> upgrade pgAdmin."
>
> Maybe pgadmin3 needs to be upgraded?  The first pgadmin3 version that
> doesn't show this warning is 1.16.0.
>
>     Markus
> _______________________________________________
> 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/20130819/edc14551/attachment.html>

From chuck.mx at gmail.com  Sat Aug 24 15:14:53 2013
From: chuck.mx at gmail.com (Valdir Franco)
Date: Sat, 24 Aug 2013 12:14:53 -0300
Subject: [Slackbuilds-users] installing openoffice 3.3.0 - building error
Message-ID: <CANysyZT2EE9jo0zCvXek5i0JTpiuW1dk_6gkOje9XFaXx6EkGA@mail.gmail.com>

Hi.

Trying install openoffice using slackbuild got a error, stopping script.

SOURCEDIR: unbound variable

Any hint on fixing it?

thanks.
-- 
T+
[]?s
marx   :-p
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130824/00c98649/attachment-0001.html>

From larryhaja at gmail.com  Sat Aug 24 17:50:15 2013
From: larryhaja at gmail.com (Larry Hajali)
Date: Sat, 24 Aug 2013 10:50:15 -0700
Subject: [Slackbuilds-users] installing openoffice 3.3.0 - building error
In-Reply-To: <CANysyZT2EE9jo0zCvXek5i0JTpiuW1dk_6gkOje9XFaXx6EkGA@mail.gmail.com>
References: <CANysyZT2EE9jo0zCvXek5i0JTpiuW1dk_6gkOje9XFaXx6EkGA@mail.gmail.com>
Message-ID: <CAAZPBMhvG75RUacZaSb37JiwMxhUjr2kffeEtw-y=W-YYHXeJQ@mail.gmail.com>

On Sat, Aug 24, 2013 at 8:14 AM, Valdir Franco <chuck.mx at gmail.com> wrote:

> Hi.
>
> Trying install openoffice using slackbuild got a error, stopping script.
>
> SOURCEDIR: unbound variable
>
> Any hint on fixing it?
>
>
Yeah, download the openoffice.org tarball for your particular architecture
and put it in the same folder as the openoffice.org.SlackBuild.  The error
is stating that $SOURCEDIR is not defined because it can't find the tarball.

--Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130824/91e468cf/attachment.html>

From chuck.mx at gmail.com  Sun Aug 25 21:03:34 2013
From: chuck.mx at gmail.com (Valdir Franco)
Date: Sun, 25 Aug 2013 18:03:34 -0300
Subject: [Slackbuilds-users] installing openoffice 3.3.0 - building error
Message-ID: <CANysyZRqtNuMg5fnWQuF3pa-XEG9w0Em4K0-obNxxNw+V1Lzsg@mail.gmail.com>

>On Sat, Aug 24, 2013 at 8:14 AM, Valdir Franco <chuck.mx at gmail.com <http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>> wrote:

>*> Hi.*>>**>*>Trying install openoffice using slackbuild got an error, stopping script.*>>**>*>SOURCEDIR: unbound variable*>>**>*>Any hint on fixing it?*>>**>>**>Yeah, download the openoffice.org tarball for your particular architecture
>and put it in the same folder as the openoffice.org.SlackBuild.  The error
>is stating that $SOURCEDIR is not defined because it can't find the tarball.
>
>--Larry

Hi, again.
I did download again, at least three times.
For me the file name is correct. Below is my screen, with dir contents e
the script error.

------------------------------
root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org# ls
OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
README
doinst.sh
openoffice.org.SlackBuild*
openoffice.org.info
slack-desc
root at mrx:/home/marxz/Softwares/Apache
OpenOffice/openoffice.org#./openoffice.org.SlackBuild
OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
./openoffice.org.SlackBuild: line 103: SOURCEDIR: unbound variable
root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org#
------------------------------

I'm not a batch/script writing expert, but looks like is missing something
in the script excerpt:

------------------------------
# Check if we have the tarball
if [ ! -r $TARBALL ]; then
  echo "$TARBALL not found"
  exit 1
fi

# Ignore this - it's just to get the toplevel directory name of the
# extracted tarball archive
SOURCEDIR=$(tar tzf $CWD/$TARNAME 2>/dev/null | head -n 1 | tr -d \/)
# If the above operation failed for some reason, unset SOURCEDIR so that
# the "set -eu" below will cause us to bail out with an error
<<<<<<<<------shouldn't be an "if" statement here?
[ -z $SOURCEDIR ] && unset SOURCEDIR  <<<<<------ I understand this line as
a condition, but no loop command.....am I wrong?

set -eu

rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
rm -rf $TMP/$SOURCEDIR

# Extract tarball
tar xvf $CWD/$TARNAME -C $TMP
------------------------------

Thanks again...

-- 
T+
[]?s
marx   :-p
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130825/ac5a6568/attachment.html>

From mancha1 at hush.com  Mon Aug 26 01:19:25 2013
From: mancha1 at hush.com (mancha)
Date: Mon, 26 Aug 2013 01:19:25 +0000
Subject: [Slackbuilds-users] installing openoffice 3.3.0 - building error
Message-ID: <20130826011925.E2C8C200DE@smtp.hushmail.com>

On Sun, 25 Aug 2013 21:03:42 +0000 "Valdir Franco" wrote:
>I'm not a batch/script writing expert, but looks like is missing 
>something

Script looks fine to me. My guess is you have issues with your
tarball.

What output do you get with:

$ file OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz

and 

$ tar tzf OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz|head



From chuck.mx at gmail.com  Mon Aug 26 03:32:50 2013
From: chuck.mx at gmail.com (Valdir Franco)
Date: Mon, 26 Aug 2013 00:32:50 -0300
Subject: [Slackbuilds-users] installing openoffice 3.3.0 - building error
In-Reply-To: <20130826011925.E2C8C200DE@smtp.hushmail.com>
References: <20130826011925.E2C8C200DE@smtp.hushmail.com>
Message-ID: <CANysyZTpZGCwiPibit2HEyWJeZ+SDTu0JOCcWQhBT_0XLXTo2g@mail.gmail.com>

Here is the output:
-------------
root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org# file
OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz: gzip compressed data,
from Unix, last modified: Mon Jan 17 17:58:24 2011

root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org# tar tzf
OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz | head
OOO330_m20_native_packed-1_en-US.9567/
OOO330_m20_native_packed-1_en-US.9567/update
OOO330_m20_native_packed-1_en-US.9567/JavaSetup.jar
OOO330_m20_native_packed-1_en-US.9567/readmes/
OOO330_m20_native_packed-1_en-US.9567/readmes/README_en-US
OOO330_m20_native_packed-1_en-US.9567/readmes/README_en-US.html
OOO330_m20_native_packed-1_en-US.9567/setup
OOO330_m20_native_packed-1_en-US.9567/installdata/
OOO330_m20_native_packed-1_en-US.9567/installdata/xpd/
OOO330_m20_native_packed-1_en-US.9567/installdata/xpd/gid_Module_Optional_Testtool.xpd
root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org#

-------------

TIA


2013/8/25 mancha <mancha1 at hush.com>

> On Sun, 25 Aug 2013 21:03:42 +0000 "Valdir Franco" wrote:
> >I'm not a batch/script writing expert, but looks like is missing
> >something
>
> Script looks fine to me. My guess is you have issues with your
> tarball.
>
> What output do you get with:
>
> $ file OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
>
> and
>
> $ tar tzf OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz|head
>
>
>


-- 
T+
[]?s
marx   :-p
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130826/e52d8202/attachment.html>

From noel.butler at ausics.net  Mon Aug 26 03:52:16 2013
From: noel.butler at ausics.net (Noel Butler)
Date: Mon, 26 Aug 2013 13:52:16 +1000
Subject: [Slackbuilds-users] installing openoffice 3.3.0 - building error
In-Reply-To: <CANysyZTpZGCwiPibit2HEyWJeZ+SDTu0JOCcWQhBT_0XLXTo2g@mail.gmail.com>
References: <20130826011925.E2C8C200DE@smtp.hushmail.com>
	<CANysyZTpZGCwiPibit2HEyWJeZ+SDTu0JOCcWQhBT_0XLXTo2g@mail.gmail.com>
Message-ID: <1377489136.7320.2.camel@tardis>

3.3.0 is incredibly old, several years old.

Please try current stable version:  4.0

On Mon, 2013-08-26 at 00:32 -0300, Valdir Franco wrote:
> Here is the output:
> -------------
> root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org# file
> OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz 
> OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz: gzip compressed
> data, from Unix, last modified: Mon Jan 17 17:58:24 2011
> 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130826/0bb0ca95/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130826/0bb0ca95/attachment.asc>

From C.J.Theunissen at differ.nl  Mon Aug 26 03:53:44 2013
From: C.J.Theunissen at differ.nl (Kees Theunissen)
Date: Mon, 26 Aug 2013 05:53:44 +0200 (CEST)
Subject: [Slackbuilds-users] installing openoffice 3.3.0 - building error
In-Reply-To: <CANysyZRqtNuMg5fnWQuF3pa-XEG9w0Em4K0-obNxxNw+V1Lzsg@mail.gmail.com>
References: <CANysyZRqtNuMg5fnWQuF3pa-XEG9w0Em4K0-obNxxNw+V1Lzsg@mail.gmail.com>
Message-ID: <alpine.LNX.2.02.1308260543380.1888@pcict9.rijnh.nl>

On Sun, 25 Aug 2013, Valdir Franco wrote:

>>On Sat, Aug 24, 2013 at 8:14 AM, Valdir Franco <chuck.mx at gmail.com<http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>> wrote:
>
>>> Hi.
>>>
>>>Trying install openoffice using slackbuild got an error, stopping script.
>>>
>>>SOURCEDIR: unbound variable
>>>
>>>Any hint on fixing it?
>>>
>>>
>>Yeah, download the openoffice.org<http://openoffice.org> tarball for your particular architecture
>>and put it in the same folder as the openoffice.org.SlackBuild.  The error
>>is stating that $SOURCEDIR is not defined because it can't find the tarball.
>>
>>--Larry
>
>
>Hi, again.
>I did download again, at least three times.
>For me the file name is correct. Below is my screen, with dir contents e the script error.
>
>------------------------------
>root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org#<http://openoffice.org#> ls
>OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
>README
>doinst.sh
>openoffice.org.SlackBuild*
>openoffice.org.info<http://openoffice.org.info>
>slack-desc
>root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org#<http://openoffice.org#> ./openoffice.org.SlackBuild
>OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
>./openoffice.org.SlackBuild: line 103: SOURCEDIR: unbound variable
>root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org#<http://openoffice.org#>
>------------------------------

I guess that the space in your directory name "Apache OpenOffice" is
the cause of all trouble. Rename that directory to something without
spaces and try again.

>
>I'm not a batch/script writing expert, but looks like is missing something in the script excerpt:
>
>------------------------------
># Check if we have the tarball
>if [ ! -r $TARBALL ]; then
>  echo "$TARBALL not found"
>  exit 1
>fi

This check doesn't do anything besause $TARBALL is not defined. $TARNAME
is used everywhere else in the script. But that is not the cause of your
problem.

>
># Ignore this - it's just to get the toplevel directory name of the
># extracted tarball archive
>SOURCEDIR=$(tar tzf $CWD/$TARNAME 2>/dev/null | head -n 1 | tr -d \/)
># If the above operation failed for some reason, unset SOURCEDIR so that
># the "set -eu" below will cause us to bail out with an error  <<<<<<<<------shouldn't be an "if" statement here?
>[ -z $SOURCEDIR ] && unset SOURCEDIR  <<<<<------ I understand this line as a condition, but no loop command.....am I wrong?
>
>set -eu
>
>rm -rf $PKG
>mkdir -p $TMP $PKG $OUTPUT
>rm -rf $TMP/$SOURCEDIR
>
># Extract tarball
>tar xvf $CWD/$TARNAME -C $TMP
>------------------------------
>
>Thanks again...
>
>--
>T+
>[]?s
>marx   :-p
>


Groeten,

Kees.

-- 
Kees Theunissen, Systeem- en netwerkbeheerder,   Tel: 030-6096724
Dutch Institute For Fundamental Energy Research (DIFFER)
e-mailadres:     C.J.Theunissen at differ.nl
postadres:       Postbus 1207, 3430 BE Nieuwegein
bezoekersadres:  Edisonbaan 14, 3439 MN Nieuwegein


From evanton at tut.by  Tue Aug 13 03:13:23 2013
From: evanton at tut.by (James Bond)
Date: Tue, 13 Aug 2013 06:13:23 +0300
Subject: [Slackbuilds-users] Buildscript for virtualenvwrapper builds a
 Slackware package that is not functional
Message-ID: <CAHP6NK7GsLho1bpT-ENjhb0p3z0nnjZcr0rHwGn81RoBYxNFvg@mail.gmail.com>

The Slackware package builds fine, I assume that is the reason why the
SlackBuild passed through testing. However, attempt to use
virtualenvwrapper after installing the Slackware package fails because
sourcing virtualenvwrapper.sh like its documentation is suggesting
produces Python import errors. Reason: virtualenvwrapper has two runtime
dependencies [1], [2] which aren't mentioned in the README.

I have "cheated" my way out of this problem by installing the dependencies
using pip.

Everything above applies for a Slackware64-14.0 system.

1. https://pypi.python.org/pypi/stevedore

2. https://pypi.python.org/pypi/virtualenv-clone

PS: if someone is going to work on this and make buildscripts for the
dependencies, please consider updating the buildscript for
virtualenvwrapper as well. The latest stable version is 4.x already, but
the Slackware package seems to build (and work) fine with the buildscript
for 3.7 (as long as the runtime dependencies are satisfied).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130813/4d3e9b0d/attachment.html>

From info at microlinux.fr  Mon Aug 26 06:17:38 2013
From: info at microlinux.fr (Niki Kovacs)
Date: Mon, 26 Aug 2013 08:17:38 +0200
Subject: [Slackbuilds-users] installing openoffice 3.3.0 - building error
In-Reply-To: <CANysyZT2EE9jo0zCvXek5i0JTpiuW1dk_6gkOje9XFaXx6EkGA@mail.gmail.com>
References: <CANysyZT2EE9jo0zCvXek5i0JTpiuW1dk_6gkOje9XFaXx6EkGA@mail.gmail.com>
Message-ID: <521AF302.4000807@microlinux.fr>

Le 24/08/2013 17:14, Valdir Franco a ?crit :
> Hi.
>
> Trying install openoffice using slackbuild got a error, stopping script.

http://www.microlinux.fr/slackware/testing/

Some ready-made packages for 32-bit and 64-bit Slackware.

Cheers,

Niki

-- 
Microlinux - Solutions informatiques 100% Linux et logiciels libres
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 chuck.mx at gmail.com  Mon Aug 26 12:24:21 2013
From: chuck.mx at gmail.com (Valdir Franco)
Date: Mon, 26 Aug 2013 09:24:21 -0300
Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 87, Issue 6
In-Reply-To: <mailman.331.1377490433.2626.slackbuilds-users@slackbuilds.org>
References: <mailman.331.1377490433.2626.slackbuilds-users@slackbuilds.org>
Message-ID: <CANysyZRoy6NTWWen1AUPCAJ0675XFfrv06B-JEjYUVREYLL-Cg@mail.gmail.com>

Bingo!
Yeah, the space in dir name...

Following as sugested, after tested with OOo 3.3.0, installed OOo 4.0.0.
Working.
thanks all folks for the help.

[ ]


2013/8/26 <slackbuilds-users-request at slackbuilds.org>

> 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: installing openoffice 3.3.0 - building error (Larry Hajali)
>    2. Re: installing openoffice 3.3.0 - building error (Valdir Franco)
>    3. Re: installing openoffice 3.3.0 - building error (mancha)
>    4. Re: installing openoffice 3.3.0 - building error (Valdir Franco)
>    5. Re: installing openoffice 3.3.0 - building error (Noel Butler)
>    6. Re: installing openoffice 3.3.0 - building error (Kees Theunissen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 24 Aug 2013 10:50:15 -0700
> From: Larry Hajali <larryhaja at gmail.com>
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] installing openoffice 3.3.0 -
>         building error
> Message-ID:
>         <CAAZPBMhvG75RUacZaSb37JiwMxhUjr2kffeEtw-y=
> W-YYHXeJQ at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Sat, Aug 24, 2013 at 8:14 AM, Valdir Franco <chuck.mx at gmail.com> wrote:
>
> > Hi.
> >
> > Trying install openoffice using slackbuild got a error, stopping script.
> >
> > SOURCEDIR: unbound variable
> >
> > Any hint on fixing it?
> >
> >
> Yeah, download the openoffice.org tarball for your particular architecture
> and put it in the same folder as the openoffice.org.SlackBuild.  The error
> is stating that $SOURCEDIR is not defined because it can't find the
> tarball.
>
> --Larry
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130824/91e468cf/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Sun, 25 Aug 2013 18:03:34 -0300
> From: Valdir Franco <chuck.mx at gmail.com>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] installing openoffice 3.3.0 -
>         building error
> Message-ID:
>         <
> CANysyZRqtNuMg5fnWQuF3pa-XEG9w0Em4K0-obNxxNw+V1Lzsg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> >On Sat, Aug 24, 2013 at 8:14 AM, Valdir Franco <chuck.mx at gmail.com <
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>> wrote:
>
> >*> Hi.*>>**>*>Trying install openoffice using slackbuild got an error,
> stopping script.*>>**>*>SOURCEDIR: unbound variable*>>**>*>Any hint on
> fixing it?*>>**>>**>Yeah, download the openoffice.org tarball for your
> particular architecture
> >and put it in the same folder as the openoffice.org.SlackBuild.  The error
> >is stating that $SOURCEDIR is not defined because it can't find the
> tarball.
> >
> >--Larry
>
> Hi, again.
> I did download again, at least three times.
> For me the file name is correct. Below is my screen, with dir contents e
> the script error.
>
> ------------------------------
> root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org# ls
> OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
> README
> doinst.sh
> openoffice.org.SlackBuild*
> openoffice.org.info
> slack-desc
> root at mrx:/home/marxz/Softwares/Apache
> OpenOffice/openoffice.org#./openoffice.org.SlackBuild
> OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
> ./openoffice.org.SlackBuild: line 103: SOURCEDIR: unbound variable
> root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org#
> ------------------------------
>
> I'm not a batch/script writing expert, but looks like is missing something
> in the script excerpt:
>
> ------------------------------
> # Check if we have the tarball
> if [ ! -r $TARBALL ]; then
>   echo "$TARBALL not found"
>   exit 1
> fi
>
> # Ignore this - it's just to get the toplevel directory name of the
> # extracted tarball archive
> SOURCEDIR=$(tar tzf $CWD/$TARNAME 2>/dev/null | head -n 1 | tr -d \/)
> # If the above operation failed for some reason, unset SOURCEDIR so that
> # the "set -eu" below will cause us to bail out with an error
> <<<<<<<<------shouldn't be an "if" statement here?
> [ -z $SOURCEDIR ] && unset SOURCEDIR  <<<<<------ I understand this line as
> a condition, but no loop command.....am I wrong?
>
> set -eu
>
> rm -rf $PKG
> mkdir -p $TMP $PKG $OUTPUT
> rm -rf $TMP/$SOURCEDIR
>
> # Extract tarball
> tar xvf $CWD/$TARNAME -C $TMP
> ------------------------------
>
> Thanks again...
>
> --
> T+
> []?s
> marx   :-p
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130825/ac5a6568/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Mon, 26 Aug 2013 01:19:25 +0000
> From: "mancha" <mancha1 at hush.com>
> To: slackbuilds-users at slackbuilds.org, chuck.mx at gmail.com
> Subject: Re: [Slackbuilds-users] installing openoffice 3.3.0 -
>         building error
> Message-ID: <20130826011925.E2C8C200DE at smtp.hushmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> On Sun, 25 Aug 2013 21:03:42 +0000 "Valdir Franco" wrote:
> >I'm not a batch/script writing expert, but looks like is missing
> >something
>
> Script looks fine to me. My guess is you have issues with your
> tarball.
>
> What output do you get with:
>
> $ file OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
>
> and
>
> $ tar tzf OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz|head
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 26 Aug 2013 00:32:50 -0300
> From: Valdir Franco <chuck.mx at gmail.com>
> To: mancha1 at hush.com
> Cc: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] installing openoffice 3.3.0 -
>         building error
> Message-ID:
>         <
> CANysyZTpZGCwiPibit2HEyWJeZ+SDTu0JOCcWQhBT_0XLXTo2g at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Here is the output:
> -------------
> root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org# file
> OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
> OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz: gzip compressed data,
> from Unix, last modified: Mon Jan 17 17:58:24 2011
>
> root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org# tar tzf
> OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz | head
> OOO330_m20_native_packed-1_en-US.9567/
> OOO330_m20_native_packed-1_en-US.9567/update
> OOO330_m20_native_packed-1_en-US.9567/JavaSetup.jar
> OOO330_m20_native_packed-1_en-US.9567/readmes/
> OOO330_m20_native_packed-1_en-US.9567/readmes/README_en-US
> OOO330_m20_native_packed-1_en-US.9567/readmes/README_en-US.html
> OOO330_m20_native_packed-1_en-US.9567/setup
> OOO330_m20_native_packed-1_en-US.9567/installdata/
> OOO330_m20_native_packed-1_en-US.9567/installdata/xpd/
>
> OOO330_m20_native_packed-1_en-US.9567/installdata/xpd/gid_Module_Optional_Testtool.xpd
> root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org#
>
> -------------
>
> TIA
>
>
> 2013/8/25 mancha <mancha1 at hush.com>
>
> > On Sun, 25 Aug 2013 21:03:42 +0000 "Valdir Franco" wrote:
> > >I'm not a batch/script writing expert, but looks like is missing
> > >something
> >
> > Script looks fine to me. My guess is you have issues with your
> > tarball.
> >
> > What output do you get with:
> >
> > $ file OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
> >
> > and
> >
> > $ tar tzf OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz|head
> >
> >
> >
>
>
> --
> T+
> []?s
> marx   :-p
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130826/e52d8202/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 5
> Date: Mon, 26 Aug 2013 13:52:16 +1000
> From: Noel Butler <noel.butler at ausics.net>
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] installing openoffice 3.3.0 -
>         building error
> Message-ID: <1377489136.7320.2.camel at tardis>
> Content-Type: text/plain; charset="utf-8"
>
> 3.3.0 is incredibly old, several years old.
>
> Please try current stable version:  4.0
>
> On Mon, 2013-08-26 at 00:32 -0300, Valdir Franco wrote:
> > Here is the output:
> > -------------
> > root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org# file
> > OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
> > OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz: gzip compressed
> > data, from Unix, last modified: Mon Jan 17 17:58:24 2011
> >
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130826/0bb0ca95/attachment-0001.html
> >
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 490 bytes
> Desc: This is a digitally signed message part
> URL: <
> http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130826/0bb0ca95/attachment-0001.asc
> >
>
> ------------------------------
>
> Message: 6
> Date: Mon, 26 Aug 2013 05:53:44 +0200 (CEST)
> From: Kees Theunissen <C.J.Theunissen at differ.nl>
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] installing openoffice 3.3.0 -
>         building error
> Message-ID: <alpine.LNX.2.02.1308260543380.1888 at pcict9.rijnh.nl>
> Content-Type: TEXT/PLAIN; charset=iso-8859-1
>
> On Sun, 25 Aug 2013, Valdir Franco wrote:
>
> >>On Sat, Aug 24, 2013 at 8:14 AM, Valdir Franco <chuck.mx at gmail.com<
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>> wrote:
> >
> >>> Hi.
> >>>
> >>>Trying install openoffice using slackbuild got an error, stopping
> script.
> >>>
> >>>SOURCEDIR: unbound variable
> >>>
> >>>Any hint on fixing it?
> >>>
> >>>
> >>Yeah, download the openoffice.org<http://openoffice.org> tarball for
> your particular architecture
> >>and put it in the same folder as the openoffice.org.SlackBuild.  The
> error
> >>is stating that $SOURCEDIR is not defined because it can't find the
> tarball.
> >>
> >>--Larry
> >
> >
> >Hi, again.
> >I did download again, at least three times.
> >For me the file name is correct. Below is my screen, with dir contents e
> the script error.
> >
> >------------------------------
> >root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org#<
> http://openoffice.org#> ls
> >OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
> >README
> >doinst.sh
> >openoffice.org.SlackBuild*
> >openoffice.org.info<http://openoffice.org.info>
> >slack-desc
> >root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org#<
> http://openoffice.org#> ./openoffice.org.SlackBuild
> >OOo_3.3.0_Linux_x86-64_install-rpm-wJRE_en-US.tar.gz
> >./openoffice.org.SlackBuild: line 103: SOURCEDIR: unbound variable
> >root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org#<
> http://openoffice.org#>
> >------------------------------
>
> I guess that the space in your directory name "Apache OpenOffice" is
> the cause of all trouble. Rename that directory to something without
> spaces and try again.
>
> >
> >I'm not a batch/script writing expert, but looks like is missing
> something in the script excerpt:
> >
> >------------------------------
> ># Check if we have the tarball
> >if [ ! -r $TARBALL ]; then
> >  echo "$TARBALL not found"
> >  exit 1
> >fi
>
> This check doesn't do anything besause $TARBALL is not defined. $TARNAME
> is used everywhere else in the script. But that is not the cause of your
> problem.
>
> >
> ># Ignore this - it's just to get the toplevel directory name of the
> ># extracted tarball archive
> >SOURCEDIR=$(tar tzf $CWD/$TARNAME 2>/dev/null | head -n 1 | tr -d \/)
> ># If the above operation failed for some reason, unset SOURCEDIR so that
> ># the "set -eu" below will cause us to bail out with an error
>  <<<<<<<<------shouldn't be an "if" statement here?
> >[ -z $SOURCEDIR ] && unset SOURCEDIR  <<<<<------ I understand this line
> as a condition, but no loop command.....am I wrong?
> >
> >set -eu
> >
> >rm -rf $PKG
> >mkdir -p $TMP $PKG $OUTPUT
> >rm -rf $TMP/$SOURCEDIR
> >
> ># Extract tarball
> >tar xvf $CWD/$TARNAME -C $TMP
> >------------------------------
> >
> >Thanks again...
> >
> >--
> >T+
> >[]?s
> >marx   :-p
> >
>
>
> Groeten,
>
> Kees.
>
> --
> Kees Theunissen, Systeem- en netwerkbeheerder,   Tel: 030-6096724
> Dutch Institute For Fundamental Energy Research (DIFFER)
> e-mailadres:     C.J.Theunissen at differ.nl
> postadres:       Postbus 1207, 3430 BE Nieuwegein
> bezoekersadres:  Edisonbaan 14, 3439 MN Nieuwegein
>
>
>
> ------------------------------
>
> 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 87, Issue 6
> ************************************************
>



-- 
T+
[]?s
marx   :-p
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130826/531c39c8/attachment-0001.html>

From chuck.mx at gmail.com  Mon Aug 26 12:38:01 2013
From: chuck.mx at gmail.com (Valdir Franco)
Date: Mon, 26 Aug 2013 09:38:01 -0300
Subject: [Slackbuilds-users] installing openoffice 3.3.0 - building error
Message-ID: <CANysyZQk8z18jrpf0wm6xKQ2h+26Qm0O1SaqbJyznvtf0eVYxA@mail.gmail.com>

Bingo!
Yeah, the space in dir name...

Following as sugested, after tested with OOo 3.3.0, installed OOo 4.0.0.
Working.
thanks all folks for the help.


From: Kees Theunissen <C.J.Theunissen at differ.nl>
To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
Subject: Re: [Slackbuilds-users] installing openoffice 3.3.0 -
        building error
>root at mrx:/home/marxz/Softwares/Apache OpenOffice/openoffice.org#<
http://openoffice.org#>
>------------------------------
>
>
>I guess that the space in your directory name "Apache OpenOffice" is
>the cause of all trouble. Rename that directory to something without
>spaces and try again.

>

[ ]

-- 
T+
[]?s
marx   :-p
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130826/e719c05f/attachment.html>

From fellype at gmail.com  Mon Aug 26 20:51:13 2013
From: fellype at gmail.com (Fellype)
Date: Mon, 26 Aug 2013 17:51:13 -0300
Subject: [Slackbuilds-users] Wrong md5sum for playonlinux at SlackBuilds.org
	site
Message-ID: <521BBFC1.2080800@gmail.com>

The md5sum value for PlayOnLinux_4.2.1.tar.gz at SlackBuilds.org site is 
4f80195c28d5424045b6471032d173b3
But downloading it from PlayOnLinux site I got 
62edcdc38b8696ee1c84300583884263 (I checked it twice).
Please, update the data in SlackBuilds.org site.

-----
Unable to download/verify source file(s) for playonlinux:
   md5sum failure for /usr/sbo/distfiles/PlayOnLinux_4.2.1.tar.gz.

Do you want to proceed? [n]
Failures:
   playonlinux: md5sum failure for 
/usr/sbo/distfiles/PlayOnLinux_4.2.1.tar.gz

-- 

Fellype do Nascimento - fellype (at) gmail.com


From apatrza1 at gmail.com  Fri Aug 30 20:51:18 2013
From: apatrza1 at gmail.com (Aesopz Phable)
Date: Fri, 30 Aug 2013 16:51:18 -0400
Subject: [Slackbuilds-users] Error During Execution of
 ./libfwbuilder.SlackBuild (libfwbuilder-4.1.3.tar.gz src)
Message-ID: <CAAb_NQEsxVd3CB7nnx5O=Cx646m3SewX6zEzesYTnjdpS7d_JA@mail.gmail.com>

In file included from ThreadTools.cpp:29:0:
../fwbuilder/ThreadTools.h:168:5: error: 'ssize_t' does not name a type
ThreadTools.cpp:180:82: error: no 'ssize_t
libfwbuilder::TimeoutCounter::read(int, void*, size_t) const' member
function declared in class 'libfwbuilder::TimeoutCounter'
make[2]: *** [.obj/ThreadTools.o] Error 1
make[2]: Leaving directory `/tmp/SBo/libfwbuilder-4.1.3/src/fwbuilder'
make[1]: *** [sub-fwbuilder-make_default-ordered] Error 2
make[1]: Leaving directory `/tmp/SBo/libfwbuilder-4.1.3/src'
make: *** [sub-src-make_default] Error 2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130830/a9dec6ea/attachment.html>

From matteo.bernardini at gmail.com  Sat Aug 31 05:19:28 2013
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 31 Aug 2013 07:19:28 +0200
Subject: [Slackbuilds-users] Error During Execution of
 ./libfwbuilder.SlackBuild (libfwbuilder-4.1.3.tar.gz src)
In-Reply-To: <CAAb_NQEsxVd3CB7nnx5O=Cx646m3SewX6zEzesYTnjdpS7d_JA@mail.gmail.com>
References: <CAAb_NQEsxVd3CB7nnx5O=Cx646m3SewX6zEzesYTnjdpS7d_JA@mail.gmail.com>
Message-ID: <CAPsDuS7CEPOVyLqcrYjfAbq+v_czWAgohPfYoNeD5kUhDW0VDQ@mail.gmail.com>

this is the version we have in our repository of fwbuilder
(libfwbuilder is included)

http://slackbuilds.org/repository/14.0/network/fwbuilder/

it builds fine in the latest slackware stable (14.0, the one on which
has been tested and that we support).

that said I happen to have a slackware-13.37, the latest version for
which we shipped libfwbuilder (and for the version you tried), where I
build packages for my web hosts: I tested the build and it went well.

Matteo