Re: [Slackbuilds-users] Package Without Maintainer

2013-11-24 Thread unix_lists
On Sat, Nov 23, 2013, at 10:07 PM, Willy Sudiarto Raharjo wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, i noticed that there are some packages that currently don't have a maintainer in our repository. Anyone is willing to take this packages? multimedia/realplayer -

[Slackbuilds-users] xmms-status-plugin

2013-11-24 Thread Petar Petrov
Hi guys it seems there's a problem with another entry of mine: xmms-status-plugin... It builds and works fine on 32bit system, however on a 64bit it builds and installs the file usr/lib64/xmms/General/libstatusdocklet.a in stead of the proper libstatusdocklet.so I do not know how to fix

Re: [Slackbuilds-users] Are we there yet?

2013-11-24 Thread David Woodfall
On (24/11/13 00:32), Chess Griffin ch...@chessgriffin.com put forth the proposition: On 24.11.2013 00:17, Robby Workman wrote: On Fri, 22 Nov 2013 11:14:36 + David Spencer baildon.resea...@googlemail.com wrote: graphics/shotwell: Removed (build failure) The root cause (at least, before

Re: [Slackbuilds-users] Package Without Maintainer

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'll take the following: graphics/shutter misc/gprenamenetwork/imageshack-uploader network/gtorrentviewer It's yours now commit 5b20aa51a071296b211639a7c0d1bba08410934d Author: Willy Sudiarto Raharjo will...@slackbuilds.org Date: Sun Nov 24

Re: [Slackbuilds-users] Package Without Maintainer

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'll take stalonetray because i'm using it. As of strongswan, it seems to be an interesting project, so I'll take it. Granted commit 6f48981686727d1abe482d302d1f985ba548799d Author: Willy Sudiarto Raharjo will...@slackbuilds.org Date: Sun Nov

[Slackbuilds-users] Unable to compile tsocks SlackBuild on old PC

2013-11-24 Thread Marius van Voorthuizen
Good evening. I attempted to compile tsocks (1.8beta5) from SlackBuild on an old PC with Slackware 14, but after about a minute the compilation fails ending with the following output: /bin/sh mkinstalldirs /tmp/SBo/package-tsocks/usr/man/man5 mkdir /tmp/SBo/package-tsocks/usr/man/man5

[Slackbuilds-users] [SlackBuilds-users] Unable to compile gnumeric

2013-11-24 Thread Yaroslav Panych
Fresh install of Slackware 14.1 Repo 14.0 goffice compiled and installed succefully gnumeric failed: CC dialog-stf-fixed-page.lo In file included from dialog-stf-fixed-page.c:29:0: dialog-stf-fixed-page.c: In function 'select_column': ../../src/dead-kittens.h:232:54: error:

Re: [Slackbuilds-users] Unable to compile tsocks SlackBuild on old PC

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I attempted to compile tsocks (1.8beta5) from SlackBuild on an old PC with Slackware 14, but after about a minute the compilation fails ending with the following output: /bin/sh mkinstalldirs /tmp/SBo/package-tsocks/usr/man/man5 mkdir

Re: [Slackbuilds-users] [SlackBuilds-users] Unable to compile gnumeric

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun 24 Nov 2013 08:27:19 PM WIT, Yaroslav Panych wrote: Fresh install of Slackware 14.1 Repo 14.0 goffice compiled and installed succefully gnumeric failed: CC dialog-stf-fixed-page.lo In file included from

[Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone, I just listed all maintainer's email and it seems that there are so many of you who submitted using different names and email addresses (perhaps you changed your email, but didn't update your email contact in all of your scripts).

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 markus reichelt - slackbui...@mareichelt.de My bad this one is already correct and somehow i missed it and include it Sorry Markus :) - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Robby Workman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 24 Nov 2013 21:21:35 +0700 Willy Sudiarto Raharjo will...@slackbuilds.org wrote: I just listed all maintainer's email and it seems that there are so many of you who submitted using different names and email addresses (perhaps you changed

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benjamin Trigona-Harany - btrig...@alumni.sfu.ca Benjamin Trigona-Harany - slackbui...@jaxartes.net Benjamin uses this email on his recent email to -user ML: Benjamin Trigona-Harany bo...@alumni.sfu.ca - -- Willy Sudiarto Raharjo -BEGIN PGP

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread David Woodfall
On (24/11/13 21:21), Willy Sudiarto Raharjo will...@slackbuilds.org put forth the proposition: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone, I just listed all maintainer's email and it seems that there are so many of you who submitted using different names and email addresses

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Markus Hutmacher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 11/24/2013 03:21 PM, schrieb Willy Sudiarto Raharjo: Hi everyone, I just listed all maintainer's email and it seems that there are so many of you who submitted using different names and email addresses (perhaps you changed your email, but

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm using mail...@markhu.de My address at gmail is still valid but I'm submitting new Slackbuilds and upgrades with the above address in the info file. Thanks now all changed to above address - -- Willy Sudiarto Raharjo -BEGIN PGP

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Woodfall - d...@dawoodfall.net This one please Done - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Ozan Türkyılmaz
2013/11/24 Willy Sudiarto Raharjo will...@slackbuilds.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ozan Türkyılmaz - ozan.turkyil...@gmail.com That one. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

[Slackbuilds-users] system/wavemon

2013-11-24 Thread Nick Warne
Hi All, I 'acked' this program a few weeks ago, but I have now found a problem, so I am not sure now if it is up to spec. for inclusion for 14.1 It builds fine, and appears to work fine... first a few caveats: F1, F2, F3 keys are used to switch display mode from: info lhist scan All works

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread David Spencer
David Spencer - nobb...@yahoo.co.uk The only one like that is javacomm, which I believed was no longer in the repo until someone last week reported it builds ok :O Just remove javacomm please, nobody will complain :D Thanks -D. ___ SlackBuilds-users

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just remove javacomm please, nobody will complain :D Unfortunately, javacomm is still needed by misc/jmri :) - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird -

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread korgman
On 24/11/2013 04:21 μμ, Willy Sudiarto Raharjo wrote: Thank you for your effort. Michales Michaloudes - kor...@gmail.com ^^ This is ok ^^ Michales Michaloudes - korgie_erase_this_and_t...@gmail.com ^^ fake and anti-spam, but is not needed. Google is doing a nice job ;)

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thank you for your effort. Michales Michaloudes - kor...@gmail.com ^^ This is ok ^^ Michales Michaloudes - korgie_erase_this_and_t...@gmail.com ^^ fake and anti-spam, but is not needed. Google is doing a nice job ;) I have fixed this before

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread David Spencer
Unfortunately, javacomm is still needed by misc/jmri :) *Damn* -- I thought that dep was gone, but the safe thing to do just to fix that email until submissions reopen. Thanks and sorry -D. ___ SlackBuilds-users mailing list

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Tito
Please let me know which one is the name/email address you want to use in your scripts. titopoquito - titopoqu...@gmail.com The other one is still valid, but take this one. Tito ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 titopoquito - titopoqu...@gmail.com The other one is still valid, but take this one. Applied commit 1449496f904e7f83115a8dc86229778599dbe6c3 Author: Willy Sudiarto Raharjo will...@slackbuilds.org Date: Mon Nov 25 01:46:26 2013 +0700

[Slackbuilds-users] brlcad: update status

2013-11-24 Thread John Vogel
I was too hasty with my statement that build of brlcad was successful. Yes it builds and mged seems to work fine. But archer, which I mistakenly didn't test, segfaults before even opening a window. I have been scrambling to find a fix, to no avail so far. The issue seems to be compatibility

[Slackbuilds-users] Any plans for iperf3?

2013-11-24 Thread Sebastian Arcus
I was looking the other day at iperf, and I noticed that iperf has been rewritten from scratch as iperf3. Are there any plans to include this at SBo? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Bojan Popovic
Hmmm... #3 is a typo. :| #1 #2 are both correct in a way. I'm using them both on a daily base. But for recent Slackbuilds I did tend to use #2. #1 might mean the SlackBuild is from an earlier period. I maintain several packages that don't get updated often (or at all) so there wasn't any need

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hmmm... #3 is a typo. :| #1 #2 are both correct in a way. I'm using them both on a daily base. But for recent Slackbuilds I did tend to use #2. #1 might mean the SlackBuild is from an earlier period. I maintain several packages that don't get

Re: [Slackbuilds-users] Any plans for iperf3?

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I was looking the other day at iperf, and I noticed that iperf has been rewritten from scratch as iperf3. Are there any plans to include this at SBo? You can submit the SlackBuild script once the submission is open :) - -- Willy Sudiarto Raharjo

Re: [Slackbuilds-users] Name/Email Inconsistencies

2013-11-24 Thread Willy Sudiarto Raharjo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please update them when the submission is open We are in commits freeze :) Ignore my previous message i have fixed them in my branch now - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using

Re: [Slackbuilds-users] Want to help with work toward 14.1 repo?

2013-11-24 Thread B-o-B De Mars
On 11/9/2013 1:31 PM, B-o-B De Mars wrote:: On 11/8/2013 2:49 PM, Robby Workman wrote:: Since Slackware 14.1 has been released, you are probably wondering how long it will take for us to get our repo ready for 14.1. Well, we don't know. However, we do know that we could use some help. Have a

Re: [Slackbuilds-users] xmms-status-plugin

2013-11-24 Thread Larry Hajali
Hi, The problem seems to be that there is a local version of libtool in the source directory that is used to link the libraries isn't /lib64 or /usr/lib64 aware. I created a simple hack to use the system libtool so that proper linking works. You can use it if you'd like. The static library is

Re: [Slackbuilds-users] xmms-status-plugin

2013-11-24 Thread Petar Petrov
hi! --- The problem seems to be that there is a local version of libtool in the source directory that is used to link the libraries isn't /lib64 or /usr/lib64 aware. I created a simple hack to use the system libtool so that proper linking works. You can use it if you'd like. The static