From ronayne.thomas at gmail.com Mon Jul 1 19:17:56 2013 From: ronayne.thomas at gmail.com (Thomas Ronayne) Date: Mon, 01 Jul 2013 15:17:56 -0400 Subject: [Slackbuilds-users] Apache-Tomcat v. 7.0.22 (really old) versus 7.0.41 (current) Message-ID: <51D1D5E4.6060407@gmail.com> Apparently, Apache Tomcat versions 7.0.29 and lower suffer from a memory leak requiring an unusual high amount of memory to run some Java applications. Version 7.0.30 and above do not have the problem. Anybody know if 7.0.41 will build properly with the current SlackBuild (before I try to do it and blow some stuff up)? -- A riddle, wrapped in a mystery, inside an enigma but that's my story and I'm stickin' to it. From slackbuilds at jq.oc9.com Mon Jul 1 23:32:19 2013 From: slackbuilds at jq.oc9.com (slackbuilds at jq.oc9.com) Date: Mon, 1 Jul 2013 19:32:19 -0400 (EDT) Subject: [Slackbuilds-users] Apache-Tomcat v. 7.0.22 (really old) versus 7.0.41 (current) In-Reply-To: <51D1D5E4.6060407@gmail.com> References: <51D1D5E4.6060407@gmail.com> Message-ID: On Mon, 1 Jul 2013, Thomas Ronayne wrote: > Apparently, Apache Tomcat versions 7.0.29 and lower suffer from a memory leak > requiring an unusual high amount of memory to run some Java applications. > Version 7.0.30 and above do not have the problem. > > Anybody know if 7.0.41 will build properly with the current SlackBuild > (before I try to do it and blow some stuff up)? > I am surprised to learn that there is a Slackbuild for tomcat. Tomcat is pretty easy to install without a Slackbuild. Just unzip it in some directory and your are good to go. As a bonus, you can run/test multiple versions of Tomcat this way. Just rm -rf the directory to uninstall without any traces left on your system. My 2 cents for what it's worth ;-) -ls From kingbeowulf at gmail.com Mon Jul 1 23:37:27 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 01 Jul 2013 16:37:27 -0700 Subject: [Slackbuilds-users] Pylotro points to wrong download Message-ID: <51D212B7.9000001@gmail.com> FYI The PyLotRO download link points to http://downloads.sourceforge.net/gnochm/pychm-0.8.4.tar.gz The correct link (for wget, etc.) is https://sites.google.com/site/leeslinuxblog/PyLotRO-0.1.15.zip Have fun ! Ed From joshuakwood at gmail.com Tue Jul 2 12:02:46 2013 From: joshuakwood at gmail.com (JK Wood) Date: Tue, 2 Jul 2013 07:02:46 -0500 Subject: [Slackbuilds-users] Pylotro points to wrong download In-Reply-To: <51D212B7.9000001@gmail.com> References: <51D212B7.9000001@gmail.com> Message-ID: Looks fine to me? On Mon, Jul 1, 2013 at 6:37 PM, King Beowulf wrote: > FYI > > The PyLotRO download link points to > > http://downloads.sourceforge.net/gnochm/pychm-0.8.4.tar.gz > > The correct link (for wget, etc.) is > > https://sites.google.com/site/leeslinuxblog/PyLotRO-0.1.15.zip > > Have fun ! > Ed > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Tue Jul 2 21:18:04 2013 From: erik at slackbuilds.org (Erik Hanson) Date: Tue, 2 Jul 2013 16:18:04 -0500 Subject: [Slackbuilds-users] Updates - 20130702.1 Message-ID: <20130702161804.242a2e35@shaggy.doo> Tue Jul 2 21:09:49 UTC 2013 academic/ImageJ: Updated for version 1.47. academic/aline: Added (Tk graphical interface for Perl) academic/mafft: Updated for version 7.047. academic/mkDSSP: Added (A program that calculates DSSP entries from PDB entries) accessibility/unclutter: Updated for version 1.09. audio/lmms: Updated for version 0.4.15. audio/qtractor: Updated for version 0.5.9. audio/sunvox: Updated for version 1.7.3c. audio/yoshimi: Added (software synthesiser) desktop/gtkman: Added (A simple GTK+2 manual page viewer) desktop/murrine-themes: Updated for version 0.98.5. desktop/slack-wallpapers: Updated for version 0.212. development/KKEdit: Added (a simple text editor) development/luajit: Added (just-in-time compiler for Lua) development/pudb: Added (A full-screen, console-based Python debugger) games/eduke32: Updated for version 20130620_3893. games/f1spirit: Added (F-1 Spirit Remake) games/firestorm-opensim: Updated for version 4.4.2.34167. games/firestorm: Updated for version 4.4.2.34167. games/hexalate: Added (color matching game) games/oblige: Updated for version 4.28b games/odamex: Updated for version 0.6.3. graphics/Pixie: Added (3D renderer) graphics/g3dviewer: Added (3-D model viewer) graphics/inkscape: Build fix on -current (harmless on 14.0) graphics/teighafileconverter: Updated for version 3.09.0. graphics/teighaviewer: Updated for version 3.09.0. graphics/yed: Updated for version 3.11. libraries/libdbi: Updated for version 0.9.0. libraries/libnetfilter_log: Changed header with license. libraries/mxml: Fix download link. libraries/vsqlite++: Added (SQLite Wrapper Library) libraries/zend-opcache: Added (PHP opcode caching and optimization) misc/BISP: Added (The Nexus Personal BankID client) misc/xbanish: Added (banish the mouse cursor when typing) multimedia/harmonySEQ: Added (a MIDI sequencer for Linux) network/bitcoin: Updated for version 0.8.3. network/dovecot-pigeonhole: Updated for version 0.3.5. network/filezilla: Updated for version 3.7.1.1. network/ip2location-c: Updated for version 6.0.1. network/ipv6calc: Updated for version 0.94.1. network/luakit: Added (micro-browser framework) network/miredo: Updated for version 1.2.6. network/node: Updated for version 0.10.12. network/qupzilla: Updated for version 1.4.3. network/yate: Added (Yet Another Telephony Engine) network/zabbix_agentd: Updated for version 2.0.6. network/zabbix_proxy: Updated for version 2.0.6. network/zabbix_server: Updated for version 2.0.6. office/pdfpc: Added (a GTK based presentation viewer application) perl/perl-Bit-Vector: Fix download link & md5sum. python/python-requests: Added (Requests: HTTP for Humans) system/clamtk: Updated for version 4.45. system/flexbackup: Added (a flexible backup tool) system/fs-uae: Updated for version 2.2.3. system/iotop: Updated for version 0.6. system/pigz: Updated for version 2.3, new maintainer. system/redis: Updated for version 2.6.14. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Tue Jul 2 22:33:41 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 02 Jul 2013 15:33:41 -0700 Subject: [Slackbuilds-users] Pylotro points to wrong download In-Reply-To: References: <51D212B7.9000001@gmail.com> Message-ID: <51D35545.7080909@gmail.com> On 07/02/2013 05:02 AM, JK Wood wrote: > Looks fine to me? > > > On Mon, Jul 1, 2013 at 6:37 PM, King Beowulf > wrote: > > FYI > > The PyLotRO download link points to > > http://downloads.sourceforge.net/gnochm/pychm-0.8.4.tar.gz > > The correct link (for wget, etc.) is > > https://sites.google.com/site/leeslinuxblog/PyLotRO-0.1.15.zip > > Have fun ! > Ed > All right! Who's the wiseguy? At 16:38 July 1, it sure didn't. Either that or senility is coming on early this season. -Ed From mancha1 at hush.com Wed Jul 3 04:55:17 2013 From: mancha1 at hush.com (mancha) Date: Wed, 03 Jul 2013 04:55:17 +0000 Subject: [Slackbuilds-users] [SLiM] Potential NULL pointer dereference Message-ID: <20130703045517.993D3600E5@smtp.hushmail.com> Hello. When SLiM uses crypt() to authenticate and it returns a NULL pointer (as glibc 2.17+ does for invalid input such as a locked account with a "!" prepended password field), then logging in to such an account via SLiM crashes the daemon. --- slim[1819]: segfault at 0 ip b7220909 sp bf85deb4 error 4 in libc- 2.17.so[b71a0000+186000] --- I have been in touch with SLiM's primary developer and he has committed my fix here: http://git.berlios.de/cgi- bin/cgit.cgi/slim/commit/?id=fbdfae3b406b1bb6f4e5e440e79b9b8bb8f071f b This fix applies cleanly to 1.3.5 and prevents the segfaults on Slackware-current and is fully backwards compatible with older Slackware versions. --mancha PS. Upon subscribing to the list, my password and other info (name, email, etc.) were sent cleartext. Having it go over SSL is very easy to do. Here's a good how-to: http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+b y+using+Secure+HTTP-SSL From mancha1 at hush.com Wed Jul 3 05:02:34 2013 From: mancha1 at hush.com (mancha) Date: Wed, 03 Jul 2013 05:02:34 +0000 Subject: [Slackbuilds-users] [SLiM] Potential NULL pointer dereference Message-ID: <20130703050234.8A1FD600E5@smtp.hushmail.com> On Wed, 03 Jul 2013 04:55:25 +0000 "mancha" wrote: >PS. Upon subscribing to the list, my password and other >info (name, email, etc.) were sent cleartext. Having it >go over SSL is very easy to do. Here's a good how-to: Never mind my postscript. It is set-up to support SSL transport already just not by default. Thanks. --mancha From niels.horn at gmail.com Wed Jul 3 09:59:10 2013 From: niels.horn at gmail.com (Niels Horn) Date: Wed, 3 Jul 2013 06:59:10 -0300 Subject: [Slackbuilds-users] [SLiM] Potential NULL pointer dereference In-Reply-To: <20130703045517.993D3600E5@smtp.hushmail.com> References: <20130703045517.993D3600E5@smtp.hushmail.com> Message-ID: Thanks for the fix! I'll include it soonish and submit an update. -- Niels Horn On Wed, Jul 3, 2013 at 1:55 AM, mancha wrote: > Hello. > > When SLiM uses crypt() to authenticate and it returns a NULL > pointer (as glibc 2.17+ does for invalid input such as a > locked account with a "!" prepended password field), then > logging in to such an account via SLiM crashes the daemon. > > --- > slim[1819]: segfault at 0 ip b7220909 sp bf85deb4 error 4 in libc- > 2.17.so[b71a0000+186000] > --- > > I have been in touch with SLiM's primary developer and he > has committed my fix here: > > http://git.berlios.de/cgi- > bin/cgit.cgi/slim/commit/?id=fbdfae3b406b1bb6f4e5e440e79b9b8bb8f071f > b > > This fix applies cleanly to 1.3.5 and prevents the segfaults > on Slackware-current and is fully backwards compatible > with older Slackware versions. > > --mancha > > PS. Upon subscribing to the list, my password and other > info (name, email, etc.) were sent cleartext. Having it > go over SSL is very easy to do. Here's a good how-to: > http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+b > y+using+Secure+HTTP-SSL > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.granvej6 at gmail.com Wed Jul 3 10:24:58 2013 From: thomas.granvej6 at gmail.com (=?ISO-8859-1?Q?Thomas_L=F8cke?=) Date: Wed, 3 Jul 2013 12:24:58 +0200 Subject: [Slackbuilds-users] SLiM 1.3.5 problem Message-ID: Hey all, When using SLiM 1.3.5 on my Slackware64 14.0 systems, the "numlock on" configuration setting doesn't work. I've tried this on three different 14.0 machines, and the same thing happens on all three: "numlock on" doesn't do anything. Reverting to SLiM 1.3.2 fixes this, and "numlock on" once again turn Num Lock ON. I've no idea if this problem is specific to my setup[1], if it's a bug in 1.3.5 itself, or if it is due to changes in the slackbuild script. I just thought I'd let you know. :o) Thomas L?cke [1] Full Slackware64 14.0 install on all three machines, kernel 3.4.43, SLiM as login manager, xmonad as WM. Nothing else added or removed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mancha1 at hush.com Wed Jul 3 19:43:43 2013 From: mancha1 at hush.com (mancha) Date: Wed, 03 Jul 2013 19:43:43 +0000 Subject: [Slackbuilds-users] [SLiM] Potential NULL pointer dereference Message-ID: <20130703194343.8B06E60115@smtp.hushmail.com> On Wed, 03 Jul 2013 09:59:12 +0000 "Niels Horn" wrote: >Thanks for the fix! > >I'll include it soonish and submit an update. > >-- >Niels Horn You're very welcome. Cheers. --mancha From niels.horn at gmail.com Sun Jul 7 00:39:35 2013 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 6 Jul 2013 21:39:35 -0300 Subject: [Slackbuilds-users] SLiM 1.3.5 problem In-Reply-To: References: Message-ID: On Wed, Jul 3, 2013 at 7:24 AM, Thomas L?cke wrote: > Hey all, > > When using SLiM 1.3.5 on my Slackware64 14.0 systems, the "numlock on" > configuration setting doesn't work. > > I've tried this on three different 14.0 machines, and the same thing > happens on all three: "numlock on" doesn't do anything. > > Reverting to SLiM 1.3.2 fixes this, and "numlock on" once again turn Num > Lock ON. > > I've no idea if this problem is specific to my setup[1], if it's a bug in > 1.3.5 itself, or if it is due to changes in the slackbuild script. I just > thought I'd let you know. > > :o) > Thomas L?cke > > [1] Full Slackware64 14.0 install on all three machines, kernel 3.4.43, > SLiM as login manager, xmonad as WM. Nothing else added or removed. > > Hi, numlock handling has changed in slim since version 1.3.4. They included the code fom NumLockX in slim, using the xkb calls. On my netbook it works fine, but it has a non-standard keyboard. On my other systems I don't use any login manager at all, so I cannot really check it. If this continues to be a problem for you, you might want to contact the slim author(s), the are usually helpful and responsive. If nothing else works out, I might try this out on a desktop, but I'm with very limited spare time nowadays, so it may take a while... -- Niels Horn -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Sun Jul 7 05:50:11 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 06 Jul 2013 22:50:11 -0700 Subject: [Slackbuilds-users] Nvidia updates Message-ID: <51D90193.5040100@gmail.com> All: I just uploaded updates to the proprietary Nvidia driver set: nvidia-legacy96 - FINAL update. nvidia-legacy173 - updated nvidia-legacy304 - NEW nvidia-319.xx - updated I'm dropping support for the 96.xx drivers after this update since I no longer have any old hardware to test. (Sigh.) I will continue to update the 173.xx and 304.xx versions. If anyone wants to take over 96.xx (and 173.xx since I only have one AGP GPU box left), you have my permission. nouveau should be plenty good enough for these old GPUs. For the impatient, get the unofficial archives here: https://git.gitorious.org/kingbeowulf-slackbuilds/kingbeowulf-slackbuilds.git As always, I welcome testers to find any errors. Also, I could use some help figuring out what to do with the new nvidia-modprobe and persistenced utilities. Supposedly, these allow userspace swapping of the nvidia module for multi GPU systems. -Ed From michael at niemeck.org Sun Jul 7 10:48:50 2013 From: michael at niemeck.org (Michael Niemeck) Date: Sun, 07 Jul 2013 12:48:50 +0200 Subject: [Slackbuilds-users] Ardour 3 Slackbuild Message-ID: <5kw9yeaen1lb5ksap6l930m3.1373194051414@email.android.com> Hi all, Is anyone actively working on a new Slackbuild for Ardour 3? I found a thread a while back on some dependency issues, but nothing more, and Ardour 3 has been around for some time now. I can contribute if need be... Mike From niels.horn at slackbuilds.org Sun Jul 7 12:51:38 2013 From: niels.horn at slackbuilds.org (Niels Horn) Date: Sun, 07 Jul 2013 09:51:38 -0300 Subject: [Slackbuilds-users] Updates - 20130707.1 Message-ID: <51D9645A.1040004@slackbuilds.org> Sun Jul 7 12:24:16 UTC 2013 academic/clustalo: Updated for version 1.2.0. academic/glpk: Updated for version 4.48. academic/ij-plugins-LOCI: Updated for version 4.4.8. academic/jalview: Added (A Sequence Alignment Editor and Viewer) academic/mapnik: Removed reference to optional cairomm dependency. academic/qucs: Updated for version 0.0.17. academic/seaview: Updated for version 4.4.2. audio/lmms: Use an improved version of 02-stutter_audio.patch desktop/j4-dmenu-desktop: Added (dmenu menu generator) development/ecl: Added (Embeddable Common-Lisp) development/gambit: Added (a Scheme compiler and interpreter) development/glade: Added (GTK+ User Interface Builder) development/nexus: Fix VERSION string to not make a broken package development/nexus: Rearrange and OCDize some build lines development/nexus: Trivial doinst.sh fix (whitespace removal) development/nexus: Update comments in slack-desc development/nexus: Updated for version 2.5.0_04. libraries/libcec: Updated for version 2.1.3. libraries/libdbi-drivers: Updated for version 0.9.0. libraries/mysql-connector-c++: Added (MySQL Connector in C++) network/jetty: Added (web server) network/ocsync: Added (file synchronizer) network/owncloud-client: Added (ownCloud sync client) network/surf: Added (minimalist web browser) network/vblade: Added (virtual EtherDrive (R) blade) office/task: Updated for version 2.2.0. python/Unidecode: Added (Python port of the Text::Unidecode Perl module) python/feedgenerator: Fixed dep info python/pelican: Added (static site generator, written in Python) python/winpdb: Updated for version 1.4.8. system/ansible: Added (a ssh based config management framework) system/sakura: Updated for version 3.1.0 (and new maintainer) system/worker: Updated for version 3.0.0. -- Niels Horn From rworkman at slackbuilds.org Mon Jul 8 06:27:54 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 8 Jul 2013 01:27:54 -0500 Subject: [Slackbuilds-users] Dependencies for mpd In-Reply-To: <5191CA49.5020407@microlinux.fr> References: <5191CA49.5020407@microlinux.fr> Message-ID: <20130708012754.5b48dd20@home.rlworkman.net> On Tue, 14 May 2013 07:23:21 +0200 Niki Kovacs wrote: > I just built mpd (Music Player Daemon) on a server running > Slackware64 14.0. The mpd page on SlackBuilds.org states, among other > libs, libmpcdec as a dependency. > > This library has been deprecated for quite some time and is now in > fact provided by the 'musepack-tools' package. Maybe you should > change the according text mentioning optional dependencies. Done in my git branch. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Jul 8 06:31:47 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 8 Jul 2013 01:31:47 -0500 Subject: [Slackbuilds-users] virtualenv SlackBuild In-Reply-To: <20130428102517.GA2014@kiras> References: <20130428102517.GA2014@kiras> Message-ID: <20130708013147.3e0b54b4@home.rlworkman.net> On Sun, 28 Apr 2013 13:25:17 +0300 Audrius Ka?ukauskas wrote: > Hi, slackers, > > About a couple of months ago I sent an email to Larry Hajali and > Vincent Batts asking if one of them could update virtualenv build > script. I wrote to them both because Larry had orphaned this script > (among the others) and Vincent claimed[*] it, but this happened on > 2011-10-24, and since then there were no updates to the script, while > virtualenv itself had numerous releases. In other words, I wasn't > sure who was the current maintainer. > > Larry replied that he indeed is not the maintainer anymore. > Unfortunately, I haven't heard from Vincent at all (I sent the email > to his hashbangbash.com address), perhaps he was busy with life at > that time and simply forgot to reply later, or maybe my email was > eaten by a grue while on its way to Vincent, who knows what really > happened. > > So I'm trying again, this time to this mailing list. If Vincent isn't > interested anymore, I'll gladly take over the script. It's one of > those tools that are essential to my workflow while writing Python > code. > > [*] > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2011-October/008223.html Well, I don't know what happened in the meantime - maybe I made some mistake in pushing an updated version of the script, but I have this commit just recently: commit 3e440ec9bc06d9f5fe780f9e7dec1e4d1cc56584 Author: Larry Hajali Date: Sun Jun 2 23:42:07 2013 -0500 python/virtualenv: Updated for version 1.9.1. Signed-off-by: Robby Workman Larry, Vincent, et al ??? -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Jul 8 06:35:04 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 8 Jul 2013 01:35:04 -0500 Subject: [Slackbuilds-users] netperf's and nickle's categorization In-Reply-To: <20130323171205.42d9797e@hamalayi.mnt> References: <20130323171205.42d9797e@hamalayi.mnt> Message-ID: <20130708013504.4a5b0ca3@home.rlworkman.net> On Sat, 23 Mar 2013 17:12:05 +0100 LukenShiro wrote: > Hi all, > > I'd say these two scripts should be moved to a more appropriate > category: > 1) nickle is a programming language, so "development" directory seems > more suitable; > 2) netperf is a network tool, so it seems more pertinent to "network" > directory. A bit later, but done in my git branch. Thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Jul 8 06:38:53 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 8 Jul 2013 01:38:53 -0500 Subject: [Slackbuilds-users] SDL_gfx not ARM-friendly In-Reply-To: <1627212564.5035653.1363995550885.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <937394871.5035460.1363995535662.JavaMail.root@zimbra53-e8.priv.proxad.net> <1627212564.5035653.1363995550885.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <20130708013853.7f88a041@home.rlworkman.net> On Sat, 23 Mar 2013 00:39:10 +0100 (CET) openpandora at free.fr wrote: > Hi ! > > elif [ "$ARCH" = "arm" ]; then > SLKCFLAGS="-O2 -fPIC" > LIBDIRSUFFIX="" > MIX=${MIX:-"dis"} > > is missing I added the usual "catchall" instead: else SLKCGLAGS="-O2" LIBDIRSUFFIX="" MIX=${MIX:-"dis"} -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Mon Jul 8 06:40:12 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 07 Jul 2013 23:40:12 -0700 Subject: [Slackbuilds-users] Missing keywords: Sauerbraten 2013-02-03 Message-ID: <51DA5ECC.7010705@gmail.com> Looks like the keywords are missing from this latest update. (I blame Firefox). Could someone add game,first person shooter,fps Thanks Ed From rworkman at slackbuilds.org Mon Jul 8 06:44:23 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 8 Jul 2013 01:44:23 -0500 Subject: [Slackbuilds-users] spideroak SlackBuild is obsolete In-Reply-To: <514ADC34.7020801@charlesmatkinson.org> References: <514ADC34.7020801@charlesmatkinson.org> Message-ID: <20130708014423.70ae6c5a@home.rlworkman.net> On Thu, 21 Mar 2013 15:38:52 +0530 Charles wrote: > The spideroak SlackBuild (which creates a Slackware package from > Spideroak's .deb) is now obsolete. > > According to the file names shown when downloading from > https://spideroak.com/opendownload, Spideroak's "Slackware Based" > packages now have the same version numbers as their "Debian Based" > packages. > > The spideroak SlackBuild maintainer has not replied to emails about it > using a superseded .deb download so I have not told them about this > news. Looks like the best option right now is to just remove the build script from our repo entirely. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Jul 8 06:47:24 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 8 Jul 2013 01:47:24 -0500 Subject: [Slackbuilds-users] Some questions In-Reply-To: <13d86e88222.1811855674161453429.-5795131210365982897@zoho.com> References: <13d86e88222.1811855674161453429.-5795131210365982897@zoho.com> Message-ID: <20130708014724.2ec70933@home.rlworkman.net> On Wed, 20 Mar 2013 01:26:57 -0700 lipkab wrote: > I've wrote a few SlackBuilds and would be interested to submit them > to SBo. I have some questions though: One of my scripts uses third > party patches. How should I include those? Where should I indicate > their source and put their legal notice? Second, would the Steam > client be allowed on your site? Sorry for the delay - no idea if this got a reply or not, but I'm not seeing one in my mail client, so here goes... If you have a download url for the patches, put them in the .info file and you don't have to worry about legal notices, licenses, etcetera - that will be a concern of the the individual who downloads them. Re Steam client, assuming you have a stable download location and it's something that we can test (the build/packaging process) without registering or some crap like that, sure. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Jul 8 06:49:03 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 8 Jul 2013 01:49:03 -0500 Subject: [Slackbuilds-users] Missing keywords: Sauerbraten 2013-02-03 In-Reply-To: <51DA5ECC.7010705@gmail.com> References: <51DA5ECC.7010705@gmail.com> Message-ID: <20130708014903.54ea42b1@home.rlworkman.net> On Sun, 07 Jul 2013 23:40:12 -0700 King Beowulf wrote: > Looks like the keywords are missing from this latest update. (I blame > Firefox). Could someone add > > game,first person shooter,fps Done. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Jul 8 06:49:55 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 8 Jul 2013 01:49:55 -0500 Subject: [Slackbuilds-users] on creating users In-Reply-To: References: <20130618102125.57dece27@home.rlworkman.net> <20130619001812.4f95c59e@home.rlworkman.net> Message-ID: <20130708014955.3bfa579c@home.rlworkman.net> On Wed, 19 Jun 2013 12:24:27 +0200 (CEST) Kees Theunissen wrote: > On Wed, 19 Jun 2013, Robby Workman wrote: > > >On Tue, 18 Jun 2013 10:58:03 -0700 > >Miguel De Anda wrote: > > > >> thanks. i guess the safest answer is to not automatically create > >> the user. i'm thinking of adding a note in the slack-desc and > >> possibly in the rc script as well. something along the lines of > >> > >> echo "$PRGNAME failed to start because it requires a group/user > >> $GRPNAME/$USRNAME" > >> exit 1 > > > > > >I think it's needless cruft in the slack-desc. > > > >It *might* be possible to convince me that the init script would > >be a decent place to do that. r > > > >-RW > > > > An application or daemon should IMHO not chance the system > configuration when started. If a program can not run as > intended/configured if should simply fail to start and log/report > that failure. > > If (a badly written) daemon would run as root when the intended > user/group is missing then the init script should test if the > user/group exists. > > You (RW) wrote yesterday: > ... so I'd rather have something fail > horribly due to a missing user/group than have a stealthily > created (and wrong/inconsistent) user and uid present. > > I'd rather have things fail nicely in such a case. :-) Yeah, I tend to agree, so I won't argue :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From willysr at gmail.com Mon Jul 8 06:54:51 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Mon, 8 Jul 2013 13:54:51 +0700 Subject: [Slackbuilds-users] SDL_gfx not ARM-friendly In-Reply-To: <20130708013853.7f88a041@home.rlworkman.net> References: <937394871.5035460.1363995535662.JavaMail.root@zimbra53-e8.priv.proxad.net> <1627212564.5035653.1363995550885.JavaMail.root@zimbra53-e8.priv.proxad.net> <20130708013853.7f88a041@home.rlworkman.net> Message-ID: > I added the usual "catchall" instead: > > else > SLKCGLAGS="-O2" > LIBDIRSUFFIX="" > MIX=${MIX:-"dis"} Can you remove this configure parameter as wel? --disable-debug \ it's no longer known by the configure script -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From rworkman at slackbuilds.org Mon Jul 8 06:56:05 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 8 Jul 2013 01:56:05 -0500 Subject: [Slackbuilds-users] [BUG] SlackBuild templates In-Reply-To: References: Message-ID: <20130708015605.0d7c0923@home.rlworkman.net> On Fri, 21 Dec 2012 11:58:32 +0400 Serg Bormant wrote: > From: Serg Bormant > To: slackbuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] [BUG] SlackBuild templates > Date: Fri, 21 Dec 2012 11:58:32 +0400 > Reply-To: "SlackBuilds.org Users List" > Sender: > slackbuilds-users-bounces at slackbuilds.org > > Hi, > > Consider something like this in source tarball: > > $ mkdir test; cd test > $ mkdir docs; touch docs/README docs/COPYING > $ ln -s docs/* . > $ ls -o * > lrwxrwxrwx 1 user 12 Dec 21 11:45 COPYING -> docs/COPYING > lrwxrwxrwx 1 user 11 Dec 21 11:45 README -> docs/README > > docs: > total 0 > -rw-r--r-- 1 user 0 Dec 21 11:45 COPYING > -rw-r--r-- 1 user 0 Dec 21 11:45 README > > > *.SlackBuild templates offer this to sanitize permissions: > > find . \ > \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \ > -exec chmod 755 {} \; -o \ > \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o > -perm 400 \) \ > -exec chmod 644 {} \; > > > But -perm 777 will fire on symlinks and will set eXecutable > permissions to docs/COPYING and docs/README. > > Using "find -L ..." or "... ! -type l ..." can help to avoid this. Yep, seems reasonable. I've just committed this in my git branch of the templates repo; we'll merge it to master at some point. Thanks for the report and fix! CC'd Pat because he may want to edit his templates too... -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Jul 8 06:58:55 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 8 Jul 2013 01:58:55 -0500 Subject: [Slackbuilds-users] SDL_gfx not ARM-friendly In-Reply-To: References: <937394871.5035460.1363995535662.JavaMail.root@zimbra53-e8.priv.proxad.net> <1627212564.5035653.1363995550885.JavaMail.root@zimbra53-e8.priv.proxad.net> <20130708013853.7f88a041@home.rlworkman.net> Message-ID: <20130708015855.68c4e643@home.rlworkman.net> On Mon, 8 Jul 2013 13:54:51 +0700 Willy Sudiarto Raharjo wrote: > > I added the usual "catchall" instead: > > > > else > > SLKCGLAGS="-O2" > > LIBDIRSUFFIX="" > > MIX=${MIX:-"dis"} > > Can you remove this configure parameter as wel? > > --disable-debug \ > > it's no longer known by the configure script Done. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Jul 8 07:02:25 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 8 Jul 2013 02:02:25 -0500 Subject: [Slackbuilds-users] No Unread Mails!!! :-) Message-ID: <20130708020225.26d03af7@home.rlworkman.net> THIS, ladies and gentlemen, is something I've not seen in years: http://slackware.com/~rworkman/NoUnreadMails.png -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From vbatts at hashbangbash.com Mon Jul 8 09:56:03 2013 From: vbatts at hashbangbash.com (Vincent Batts) Date: Mon, 8 Jul 2013 05:56:03 -0400 Subject: [Slackbuilds-users] No Unread Mails!!! :-) In-Reply-To: <20130708020225.26d03af7@home.rlworkman.net> References: <20130708020225.26d03af7@home.rlworkman.net> Message-ID: Show off. ;-) On Jul 8, 2013 3:02 AM, "Robby Workman" wrote: > THIS, ladies and gentlemen, is something I've not seen in years: > > http://slackware.com/~rworkman/NoUnreadMails.png > > -RW > > _______________________________________________ > 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: From klaatu at straightedgelinux.com Mon Jul 8 13:47:49 2013 From: klaatu at straightedgelinux.com (Klaatu) Date: Mon, 08 Jul 2013 09:47:49 -0400 Subject: [Slackbuilds-users] No Unread Mails!!! :-) In-Reply-To: <20130708020225.26d03af7@home.rlworkman.net> References: <20130708020225.26d03af7@home.rlworkman.net> Message-ID: <1405447.nMKAeP3oSV@slackk> On Monday, July 08, 2013 02:02:25 AM Robby Workman wrote: > THIS, ladies and gentlemen, is something I've not seen in years: > > http://slackware.com/~rworkman/NoUnreadMails.png > > -RW Fake, obviously GIMP'd. - klaatu From larryhaja at gmail.com Mon Jul 8 17:20:22 2013 From: larryhaja at gmail.com (Larry Hajali) Date: Mon, 8 Jul 2013 10:20:22 -0700 Subject: [Slackbuilds-users] virtualenv SlackBuild In-Reply-To: <20130708013147.3e0b54b4@home.rlworkman.net> References: <20130428102517.GA2014@kiras> <20130708013147.3e0b54b4@home.rlworkman.net> Message-ID: Yeah, that was me. I pushed an updated version as I didn't see anyone else updating it. I no longer use virtualenv, so whoever wants it is welcome to own it. --Larry On Sun, Jul 7, 2013 at 11:31 PM, Robby Workman wrote: > On Sun, 28 Apr 2013 13:25:17 +0300 > Audrius Ka?ukauskas wrote: > > > Hi, slackers, > > > > About a couple of months ago I sent an email to Larry Hajali and > > Vincent Batts asking if one of them could update virtualenv build > > script. I wrote to them both because Larry had orphaned this script > > (among the others) and Vincent claimed[*] it, but this happened on > > 2011-10-24, and since then there were no updates to the script, while > > virtualenv itself had numerous releases. In other words, I wasn't > > sure who was the current maintainer. > > > > Larry replied that he indeed is not the maintainer anymore. > > Unfortunately, I haven't heard from Vincent at all (I sent the email > > to his hashbangbash.com address), perhaps he was busy with life at > > that time and simply forgot to reply later, or maybe my email was > > eaten by a grue while on its way to Vincent, who knows what really > > happened. > > > > So I'm trying again, this time to this mailing list. If Vincent isn't > > interested anymore, I'll gladly take over the script. It's one of > > those tools that are essential to my workflow while writing Python > > code. > > > > [*] > > > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2011-October/008223.html > > > Well, I don't know what happened in the meantime - maybe I made > some mistake in pushing an updated version of the script, but I > have this commit just recently: > > commit 3e440ec9bc06d9f5fe780f9e7dec1e4d1cc56584 > Author: Larry Hajali > Date: Sun Jun 2 23:42:07 2013 -0500 > > python/virtualenv: Updated for version 1.9.1. > > Signed-off-by: Robby Workman > > > Larry, Vincent, et al ??? > > -RW > -------------- next part -------------- An HTML attachment was scrubbed... URL: From audrius at neutrino.lt Mon Jul 8 19:02:28 2013 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Mon, 8 Jul 2013 22:02:28 +0300 Subject: [Slackbuilds-users] virtualenv SlackBuild In-Reply-To: References: <20130428102517.GA2014@kiras> <20130708013147.3e0b54b4@home.rlworkman.net> Message-ID: <20130708190228.GB3000@varna> On Mon, 2013-07-08 at 10:20:22 -0700, Larry Hajali wrote: > Yeah, that was me. I pushed an updated version as I didn't see anyone else > updating it. I no longer use virtualenv, so whoever wants it is welcome to > own it. If nobody objects, I'd gladly take it over. -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From info at microlinux.fr Wed Jul 10 08:43:38 2013 From: info at microlinux.fr (Niki Kovacs) Date: Wed, 10 Jul 2013 10:43:38 +0200 Subject: [Slackbuilds-users] Permissions in perl-BerkeleyDB Message-ID: <51DD1EBA.5090308@microlinux.fr> Hi, Small bug of no consequence, but here goes. The documentation files in perl-BerkeleyDB (Changes, README, ...) have the execution bit set. Solution: chmod 0644 $PKG/usr/doc/$PRGNAM-$VERSION/* in the SlackBuild. 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 thomas at beingboiled.info Thu Jul 11 10:35:07 2013 From: thomas at beingboiled.info (Thomas Morper) Date: Thu, 11 Jul 2013 12:35:07 +0200 (CEST) Subject: [Slackbuilds-users] lighttpd & nginx In-Reply-To: <51C9A3ED.7080103@gmail.com> References: <51C9A3ED.7080103@gmail.com> Message-ID: On Tue, 25 Jun 2013, Martin Mat?jek wrote: > Lighttpd user here. I have manually rebuild packages on every servers > from slackbuild, so I'd like to see upstream slackbuild updated. If > maintainer won't respond, I'm willing to maintain lighty because I use > it everywhere I can. Since Paul still hasn't replied yet I'd say: please go ahead, submit an updated SlackBuild, and take over future maintenance. -- From xavier at maillard.im Fri Jul 12 06:43:51 2013 From: xavier at maillard.im (Xavier Maillard) Date: Fri, 12 Jul 2013 08:43:51 +0200 Subject: [Slackbuilds-users] No Unread Mails!!! :-) In-Reply-To: <1405447.nMKAeP3oSV@slackk> (klaatu@straightedgelinux.com's message of "Mon, 08 Jul 2013 09:47:49 -0400") References: <20130708020225.26d03af7@home.rlworkman.net> <1405447.nMKAeP3oSV@slackk> Message-ID: Klaatu writes: > On Monday, July 08, 2013 02:02:25 AM Robby Workman wrote: >> THIS, ladies and gentlemen, is something I've not seen in years: >> >> http://slackware.com/~rworkman/NoUnreadMails.png >> >> -RW > > Fake, obviously GIMP'd. +1 :D /Xavier From rworkman at slackbuilds.org Fri Jul 12 07:20:31 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 12 Jul 2013 02:20:31 -0500 Subject: [Slackbuilds-users] No Unread Mails!!! :-) In-Reply-To: References: <20130708020225.26d03af7@home.rlworkman.net> <1405447.nMKAeP3oSV@slackk> Message-ID: <20130712022031.087b1868@home.rlworkman.net> On Fri, 12 Jul 2013 08:43:51 +0200 Xavier Maillard wrote: > Klaatu writes: > > > On Monday, July 08, 2013 02:02:25 AM Robby Workman wrote: > >> THIS, ladies and gentlemen, is something I've not seen in years: > >> > >> http://slackware.com/~rworkman/NoUnreadMails.png > >> > > > > Fake, obviously GIMP'd. > > +1 :D > The joke's on you guys. I suck at gimp. ;-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From yochanon at lavabit.com Fri Jul 12 09:59:21 2013 From: yochanon at lavabit.com (JB) Date: Fri, 12 Jul 2013 04:59:21 -0500 Subject: [Slackbuilds-users] No Unread Mails!!! :-) In-Reply-To: <20130712022031.087b1868@home.rlworkman.net> References: <20130708020225.26d03af7@home.rlworkman.net> <1405447.nMKAeP3oSV@slackk> <20130712022031.087b1868@home.rlworkman.net> Message-ID: <20130712045921.7cbf8cae@beer.bong> On Fri, 12 Jul 2013 02:20:31 -0500 Robby Workman wrote: > On Fri, 12 Jul 2013 08:43:51 +0200 > Xavier Maillard wrote: > > > Klaatu writes: > > > > > On Monday, July 08, 2013 02:02:25 AM Robby Workman wrote: > > >> THIS, ladies and gentlemen, is something I've not seen in years: > > >> > > >> http://slackware.com/~rworkman/NoUnreadMails.png > > >> > > > > > > Fake, obviously GIMP'd. > > > > +1 :D > > > > The joke's on you guys. I suck at gimp. ;-) > > -RW pffft! After only 13 years of using Linux (with gimp installed of course) I only just last week found out how to make a perfect circle with it! -- ?Those who suppress freedom always do so in the name of law and order.? -John v. Lindsey -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 230 bytes Desc: not available URL: From Hullen at t-online.de Fri Jul 12 10:12:00 2013 From: Hullen at t-online.de (Helmut Hullen) Date: 12 Jul 2013 12:12:00 +0200 Subject: [Slackbuilds-users] No Unread Mails!!! :-) In-Reply-To: <20130712045921.7cbf8cae@beer.bong> Message-ID: Hallo, JB, Du meintest am 12.07.13: >>>>> http://slackware.com/~rworkman/NoUnreadMails.png >>>> Fake, obviously GIMP'd. > pffft! After only 13 years of using Linux (with gimp installed of > course) I only just last week found out how to make a perfect > circle with it! Where's the problem? You only need a wooden plate ("desktop"), a nail, a hammer and a mouse (no "cordless" mouse!). Hammer the nail half into the desktop, and make a knot (with an open loop) into the mouse cord. Throw the loop over the nail, and then you can rotate the mouse around the nail. Really old gardeners may know a similar process for making perfect circles in a garden, even without a computer. Maybe the tail of the mouse is a bit too short ... (please excuse my gerlish ...) Viele Gruesse! Helmut From mjjzf at syntaktisk.dk Fri Jul 12 11:08:56 2013 From: mjjzf at syntaktisk.dk (=?UTF-8?Q?Morten_Juhl-Johansen_Z=C3=B6lde-Fej=C3=A9r?=) Date: Fri, 12 Jul 2013 13:08:56 +0200 Subject: [Slackbuilds-users] No Unread Mails!!! :-) Message-ID: <850a5db248862ed69a078c616032a7cf@syntaktisk.dk> On 2013-07-12 12:12, Hullen at t-online.de wrote: >> pffft! After only 13 years of using Linux (with gimp installed of >> course) I only just last week found out how to make a perfect >> circle with it! > > Where's the problem? You only need a wooden plate ("desktop"), a nail, > a > hammer and a mouse (no "cordless" mouse!). > > Hammer the nail half into the desktop, and make a knot (with an open > loop) into the mouse cord. Throw the loop over the nail, and then you > can rotate the mouse around the nail. > > Really old gardeners may know a similar process for making perfect > circles in a garden, even without a computer. Maybe the tail of the > mouse is a bit too short ... > > (please excuse my gerlish ...) > > Viele Gruesse! > Helmut Of ocurse, if the knot is too tight and the nail too thick, you end up with the Debian logo. -M __ Morten Juhl-Johansen Z?lde-Fej?r http://syntaktisk.dk * mjjzf at syntaktisk.dk From C.J.Theunissen at differ.nl Fri Jul 12 17:46:04 2013 From: C.J.Theunissen at differ.nl (Kees Theunissen) Date: Fri, 12 Jul 2013 19:46:04 +0200 (CEST) Subject: [Slackbuilds-users] No Unread Mails!!! :-) In-Reply-To: References: Message-ID: On Fri, 12 Jul 2013, Helmut Hullen wrote: >Hallo, JB, > >Du meintest am 12.07.13: > >>>>>> http://slackware.com/~rworkman/NoUnreadMails.png > >>>>> Fake, obviously GIMP'd. > >> pffft! After only 13 years of using Linux (with gimp installed of >> course) I only just last week found out how to make a perfect >> circle with it! > >Where's the problem? You only need a wooden plate ("desktop"), a nail, a >hammer and a mouse (no "cordless" mouse!). > >Hammer the nail half into the desktop, and make a knot (with an open >loop) into the mouse cord. Throw the loop over the nail, and then you >can rotate the mouse around the nail. > >Really old gardeners may know a similar process for making perfect >circles in a garden, even without a computer. Maybe the tail of the >mouse is a bit too short ... Hmm. Not convinced yet. I think there must be a better way. When rotating my mouse around the nail -as described above- the cursor only moved in the X-direction. :-( Did I something wrong? Regards, Kees Theunissen. -- Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724 Dutch Institute For Fundamental Energy Research (DIFFER) e-mail address: C.J.Theunissen at differ.nl postal address: PO Box 1207, 3430 BE Nieuwegein, NL visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL From mailing at markhu.de Fri Jul 12 18:33:46 2013 From: mailing at markhu.de (Markus Hutmacher) Date: Fri, 12 Jul 2013 20:33:46 +0200 Subject: [Slackbuilds-users] No Unread Mails!!! :-) In-Reply-To: References: Message-ID: <51E04C0A.30702@markhu.de> Am 12.07.2013 19:46, schrieb Kees Theunissen: > On Fri, 12 Jul 2013, Helmut Hullen wrote: > >> Hallo, JB, >> >> Du meintest am 12.07.13: >> >>>>>>> http://slackware.com/~rworkman/NoUnreadMails.png >>>>>> Fake, obviously GIMP'd. >>> pffft! After only 13 years of using Linux (with gimp installed of >>> course) I only just last week found out how to make a perfect >>> circle with it! >> Where's the problem? You only need a wooden plate ("desktop"), a nail, a >> hammer and a mouse (no "cordless" mouse!). >> >> Hammer the nail half into the desktop, and make a knot (with an open >> loop) into the mouse cord. Throw the loop over the nail, and then you >> can rotate the mouse around the nail. >> >> Really old gardeners may know a similar process for making perfect >> circles in a garden, even without a computer. Maybe the tail of the >> mouse is a bit too short ... > > Hmm. Not convinced yet. > I think there must be a better way. > When rotating my mouse around the nail -as described above- the cursor > only moved in the X-direction. :-( > Did I something wrong? > > > Regards, > > Kees Theunissen. > I don't think that you made a mistake but you will probably achieve a better (more exact) result when you only hold the mouse and two people turn the desktop ... Regards Markus -- Markus Hutmacher mailing at markhu.de From rshepard at appl-ecosys.com Fri Jul 12 18:48:11 2013 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 12 Jul 2013 11:48:11 -0700 (PDT) Subject: [Slackbuilds-users] No Unread Mails!!! :-) In-Reply-To: <51E04C0A.30702@markhu.de> References: <51E04C0A.30702@markhu.de> Message-ID: On Fri, 12 Jul 2013, Markus Hutmacher wrote: > I don't think that you made a mistake but you will probably achieve a > better (more exact) result when you only hold the mouse and two people > turn the desktop ... Markus, Now you're getting into the realm of how Microsoft tells users to resolve issues with their software. Rich From rworkman at slackbuilds.org Sat Jul 13 07:54:15 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 13 Jul 2013 02:54:15 -0500 Subject: [Slackbuilds-users] python setuptools | distribute Message-ID: <20130713025415.3cf6ebe2@home.rlworkman.net> Everyone who has python packages that depend on distribute or setuptools, please have a look at the setuptools branch: http://slackbuilds.org/cgit/slackbuilds/log/?h=setuptools We've got pysetuptools-0.8 in the ready queue, so I installed it and built everything that called for distribute to confirm that they still worked. The results are in that branch. If anyone has any objections to merging that branch to master, I'd like to hear them :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sat Jul 13 07:57:04 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 13 Jul 2013 02:57:04 -0500 Subject: [Slackbuilds-users] Permissions in perl-BerkeleyDB In-Reply-To: <51DD1EBA.5090308@microlinux.fr> References: <51DD1EBA.5090308@microlinux.fr> Message-ID: <20130713025704.2c93cbfb@home.rlworkman.net> On Wed, 10 Jul 2013 10:43:38 +0200 Niki Kovacs wrote: > Small bug of no consequence, but here goes. > > The documentation files in perl-BerkeleyDB (Changes, README, ...) > have the execution bit set. > > Solution: > > chmod 0644 $PKG/usr/doc/$PRGNAM-$VERSION/* in the SlackBuild. Fixed in my git branch; thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Sat Jul 13 07:59:45 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 13 Jul 2013 02:59:45 -0500 Subject: [Slackbuilds-users] virtualenv SlackBuild In-Reply-To: <20130708190228.GB3000@varna> References: <20130428102517.GA2014@kiras> <20130708013147.3e0b54b4@home.rlworkman.net> <20130708190228.GB3000@varna> Message-ID: <20130713025945.367b6de5@home.rlworkman.net> On Mon, 8 Jul 2013 22:02:28 +0300 Audrius Ka?ukauskas wrote: > On Mon, 2013-07-08 at 10:20:22 -0700, Larry Hajali wrote: > > Yeah, that was me. I pushed an updated version as I didn't see > > anyone else updating it. I no longer use virtualenv, so whoever > > wants it is welcome to own it. > > If nobody objects, I'd gladly take it over. > Thanks for your service, Larry :-) Audrius, it's yours in my git branch; thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From larryhaja at gmail.com Sat Jul 13 15:43:49 2013 From: larryhaja at gmail.com (Larry Hajali) Date: Sat, 13 Jul 2013 08:43:49 -0700 Subject: [Slackbuilds-users] python setuptools | distribute In-Reply-To: <20130713025415.3cf6ebe2@home.rlworkman.net> References: <20130713025415.3cf6ebe2@home.rlworkman.net> Message-ID: I pick distribute for my python packages because it was actively maintained. If upstream maintains setuptools then I have no issue with this change. --Larry On Sat, Jul 13, 2013 at 12:54 AM, Robby Workman wrote: > Everyone who has python packages that depend on distribute > or setuptools, please have a look at the setuptools branch: > http://slackbuilds.org/cgit/slackbuilds/log/?h=setuptools > > We've got pysetuptools-0.8 in the ready queue, so I installed > it and built everything that called for distribute to confirm > that they still worked. The results are in that branch. > If anyone has any objections to merging that branch to master, > I'd like to hear them :-) > > -RW > > _______________________________________________ > 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: From rworkman at slackbuilds.org Sat Jul 13 16:47:10 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 13 Jul 2013 11:47:10 -0500 Subject: [Slackbuilds-users] python setuptools | distribute In-Reply-To: References: <20130713025415.3cf6ebe2@home.rlworkman.net> Message-ID: <20130713114710.6764c30d@home.rlworkman.net> On Sat, 13 Jul 2013 08:43:49 -0700 Larry Hajali wrote: > I pick distribute for my python packages because it was actively > maintained. If upstream maintains setuptools then I have no issue > with this change. Yeah, the two projects merged again :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Sat Jul 13 18:27:44 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 13 Jul 2013 11:27:44 -0700 Subject: [Slackbuilds-users] Some questions In-Reply-To: <20130708014724.2ec70933@home.rlworkman.net> References: <13d86e88222.1811855674161453429.-5795131210365982897@zoho.com> <20130708014724.2ec70933@home.rlworkman.net> Message-ID: <51E19C20.2070408@gmail.com> On 07/07/2013 11:47 PM, Robby Workman wrote: > On Wed, 20 Mar 2013 01:26:57 -0700 > lipkab wrote: > >> I've wrote a few SlackBuilds and would be interested to submit them >> to SBo. I have some questions though: One of my scripts uses third >> party patches. How should I include those? Where should I indicate >> their source and put their legal notice? Second, would the Steam >> client be allowed on your site? > ----snip---- > > Re Steam client, assuming you have a stable download location > and it's something that we can test (the build/packaging process) > without registering or some crap like that, sure. > > -RW > My 2 cents: Eric H.'s (Alien Bob) steam slackbuild script is sorta the "gold standard" for the Slackware Steam community due to some slackware specific fixes to the steam startup script (as well as a clear specification of 32-bit compatibility dependencies for x86_64). Even though this script is fine for Slackware32, I would skip inclusion of a Steam slackbuild at this time as it requires a full 32-bit compatibility conversion of Slackware64. Perhaps, when Valve releases a proper 64-bit Steam Client, we an include it in SBo. -Ed From kingbeowulf at gmail.com Sat Jul 13 18:56:10 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 13 Jul 2013 11:56:10 -0700 Subject: [Slackbuilds-users] python setuptools | distribute In-Reply-To: <20130713025415.3cf6ebe2@home.rlworkman.net> References: <20130713025415.3cf6ebe2@home.rlworkman.net> Message-ID: <51E1A2CA.1000706@gmail.com> On 07/13/2013 12:54 AM, Robby Workman wrote: > Everyone who has python packages that depend on distribute or > setuptools, please have a look at the setuptools branch: > http://slackbuilds.org/cgit/slackbuilds/log/?h=setuptools > > We've got pysetuptools-0.8 in the ready queue, so I installed it > and built everything that called for distribute to confirm that > they still worked. The results are in that branch. If anyone has > any objections to merging that branch to master, I'd like to hear > them :-) > > -RW > > No objections here. Now I just need to remember what packages I have then depend on Distribute (man, I really need to get organized!). From rworkman at slackbuilds.org Sat Jul 13 22:17:14 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 13 Jul 2013 17:17:14 -0500 Subject: [Slackbuilds-users] python setuptools | distribute In-Reply-To: <51E1A2CA.1000706@gmail.com> References: <20130713025415.3cf6ebe2@home.rlworkman.net> <51E1A2CA.1000706@gmail.com> Message-ID: <20130713171714.6e764135@home.rlworkman.net> On Sat, 13 Jul 2013 11:56:10 -0700 King Beowulf wrote: > On 07/13/2013 12:54 AM, Robby Workman wrote: > > Everyone who has python packages that depend on distribute or > > setuptools, please have a look at the setuptools branch: > > http://slackbuilds.org/cgit/slackbuilds/log/?h=setuptools > > > > We've got pysetuptools-0.8 in the ready queue, so I installed it > > and built everything that called for distribute to confirm that > > they still worked. The results are in that branch. If anyone has > > any objections to merging that branch to master, I'd like to hear > > them :-) > > > > > > No objections here. Now I just need to remember what packages I have > then depend on Distribute (man, I really need to get organized!). Once that branch is merged, the answer is zero. :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Sat Jul 13 23:44:58 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 13 Jul 2013 16:44:58 -0700 Subject: [Slackbuilds-users] python setuptools | distribute In-Reply-To: <20130713171714.6e764135@home.rlworkman.net> References: <20130713025415.3cf6ebe2@home.rlworkman.net> <51E1A2CA.1000706@gmail.com> <20130713171714.6e764135@home.rlworkman.net> Message-ID: <51E1E67A.2070104@gmail.com> On 07/13/2013 03:17 PM, Robby Workman wrote: > On Sat, 13 Jul 2013 11:56:10 -0700 King Beowulf > wrote: > > >> >> No objections here. Now I just need to remember what packages I >> have then depend on Distribute (man, I really need to get >> organized!). > > > Once that branch is merged, the answer is zero. :-) > > -RW > > You, sir, are a very funny man.... -Ed From manbornofwoman at gmail.com Sun Jul 14 20:19:36 2013 From: manbornofwoman at gmail.com (John Smith) Date: Mon, 15 Jul 2013 00:19:36 +0400 Subject: [Slackbuilds-users] Fwd: Re: Fwd: Fwd: Build Failure: Slackbuild easymp3gain In-Reply-To: <51BB3A64.30402@sandbubble.org> References: <1371173392.21770.140661243727433.43346C3D@webmail.messagingengine.com> <1371173434.21805.140661243728185.39EF3211@webmail.messagingengine.com> <51BB3A64.30402@sandbubble.org> Message-ID: 2013/6/7 > Hello, > I am trying to build easymp3gain with your slackbuild but I encounter > the following error: > > patching file unitmain.pas > patching file easymp3gain.lpi > Hunk #1 succeeded at 490 (offset -4 lines). > chmod +x ./clean.sh > ./clean.sh > chmod +x ./make.sh > ./make.sh > Target architecture: i386 > Target operating system: linux > Compiler version: 2.6.0 > Building easyMP3Gain ... > primary config path: /root/.lazarus > Error: invalid Lazarus directory "": directory lcl not found > Failed building easymp3gain.lpr > make: *** [all] Error 2 > > All dependencies are installed and I am running Slackware 14.0. > > -- > Regards, > 2>&1 > Hello and sorry for the very late answer. Could you try lazarus 0.9.30.4 from here: http://slackbuilds.org/repository/13.37/development/lazarus/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From robby at rlworkman.net Sun Jul 14 22:41:48 2013 From: robby at rlworkman.net (Robby Workman) Date: Sun, 14 Jul 2013 17:41:48 -0500 Subject: [Slackbuilds-users] Updates - 20130714.{1,2} Message-ID: <20130714174148.2d8a576e.robby@rlworkman.net> Two separate updates bundled into one notification mail: Sun Jul 14 22:32:20 UTC 2013 perl/perl-xml-sax: Fixed dep info. +--------------------------+ Sun Jul 14 22:09:17 UTC 2013 academic/ImageJ: Updated for version 1.47v. academic/squizz: Added (A sequence/alignment format checker and converter) audio/jokosher: sed s,distribute,pysetuptools, *.info audio/mktoc: sed s,distribute,pysetuptools, *.info audio/mpd: Fixed optional dep information in README audio/opus: Updated for version 1.0.3. desktop/screenfetch: Updated for version 3.0.5. desktop/sync-engine: sed s,distribute,pysetuptools, *.info desktop/synce-kpm: sed s,distribute,pysetuptools, *.info desktop/xmms-skins-ater: Added (Ater skins for XMMS) development/MySQL-python: sed s,distribute,pysetuptools, *.info development/SQLAlchemy: sed s,distribute,pysetuptools, *.info development/Sphinx: sed s,distribute,pysetuptools, *.info development/blassic: New homepage. development/glade: Renamed script with correct extension. development/google-go-lang: Updated for version 1.1.1. development/nickle: Moved from System category development/ninja: sed s,distribute,pysetuptools, *.info development/nose: sed s,distribute,pysetuptools, *.info development/setuptools-git: sed s,distribute,pysetuptools, *.info development/trac: sed s,distribute,pysetuptools, *.info development/viewvc: Updated for version 1.1.20. development/zope.interface: sed s,distribute,pysetuptools, *.info development/zope.testing: sed s,distribute,pysetuptools, *.info games/cgoban: Added (Complete Goban Mark 1) games/hnefatafl: Added (Norse board game) games/m64py: Added (mupen64plus GUI) graphics/gallery3: Removed (renamed to graphics/gallery) graphics/gallery: Updated for version 3.0.9. graphics/mcomix: sed s,distribute,pysetuptools, *.info graphics/qrencode: Updated for version 3.4.2. libraries/FormEncode: sed s,distribute,pysetuptools, *.info libraries/GeoIP-Python: Updated for version 1.2.8. libraries/SDL_gfx: Added catchall to SLKCFLAGS block libraries/SDL_gfx: Deleted an obsolete configure argument libraries/ZConfig: sed s,distribute,pysetuptools, *.info libraries/cfitsio: Updated for version 3.35. libraries/dbh: Added (disk based hashtables library) libraries/decorator: sed s,distribute,pysetuptools, *.info libraries/genshi: sed s,distribute,pysetuptools, *.info libraries/libewf: Updated for version 20130416. libraries/log4shib: Updated for version 1.0.8. libraries/opensaml: Updated for version 2.5.3. libraries/simplegeneric: sed s,distribute,pysetuptools, *.info libraries/tubo: Added (remote process execution library) libraries/vte3: Updated for version 0.34.7. libraries/xml-security-c: Updated for version 1.7.2. libraries/xmltooling: Updated for version 1.5.3. libraries/zc.lockfile: sed s,distribute,pysetuptools, *.info libraries/zope.event: sed s,distribute,pysetuptools, *.info libraries/zope.hookable: sed s,distribute,pysetuptools, *.info libraries/zope.i18nmessageid: sed s,distribute,pysetuptools, *.info misc/gcp: sed s,distribute,pysetuptools, *.info misc/protobuf: sed s,distribute,pysetuptools, *.info misc/readesm: Added (shows content of digital tachograph files) multimedia/get_iplayer: Updated for version 2.83. network/fail2ban: New download link. network/httrack: Updated for version 3.47.21. network/identicurse: sed s,distribute,pysetuptools, *.info network/netperf: Moved from System category. network/niceshaper: Added (dynamic traffic shaper) network/ocsync: Updated for version 0.80.0. network/owncloud-client: Updated for version 1.3.0. network/phpmyadmin: Updated for version 4.0.4.1. network/shibboleth-sp: Updated for version 2.5.2. network/spideroak: Removed (build script obsolete and misleading) office/ProjectLibre: Updated for version 1.5.6. office/calibre: Updated for version 0.9.38. office/libreoffice-helppack: Updated for version 4.0.4. office/libreoffice-langpack: Updated for version 4.0.4. office/libreoffice: Updated for version 4.0.4. office/mu: Updated for version 0.9.9.5. office/notmuch: Updated for version 0.15.2. office/tellico: Updated for version 2.3.8. office/texlive: Change the order of the commands in doinst.sh perl/perl-BerkeleyDB: Fix perms on some docs perl/perl-xml-namespacesupport: Removed (dupe package) python/MarkupSafe: sed s,distribute,pysetuptools, *.info python/boto: sed s,distribute,pysetuptools, *.info python/cssselect: sed s,distribute,pysetuptools, *.info python/cssutils: sed s,distribute,pysetuptools, *.info python/distribute: Removed (merged with upstream setuptools) python/feedparser: sed s,distribute,pysetuptools, *.info python/lockfile: sed s,distribute,pysetuptools, *.info python/mechanize: sed s,distribute,pysetuptools, *.info python/netifaces: sed s,distribute,pysetuptools, *.info python/pep8: sed s,distribute,pysetuptools, *.info python/pip: sed s,distribute,pysetuptools, *.info python/psutil: Updated for version 1.0.1. python/pyinotify: sed s,distribute,pysetuptools, README python/pyquery: sed s,distribute,pysetuptools, *.info python/pysetuptools: Updated for version 0.8. python/pystatsd: sed s,distribute,pysetuptools, *.info python/python-Levenshtein: sed s,distribute,pysetuptools, *.info python/python-daemon: sed s,distribute,pysetuptools, *.info python/python-dateutil: sed s,distribute,pysetuptools, *.info python/python-distutils-extra: sed s,distribute,pysetuptools, *.info python/python-magic: sed s,distribute,pysetuptools, *.info python/python-morbid: sed s,distribute,pysetuptools, *.info python/python-oauth2: sed s,distribute,pysetuptools, *.info python/python-stomper: sed s,distribute,pysetuptools, *.info python/python-transaction: sed s,distribute,pysetuptools, *.info python/pyudev: sed s,distribute,pysetuptools, *.info python/rope: sed s,distribute,pysetuptools, README python/tweepy: sed s,distribute,pysetuptools, *.info python/virtualenv: New maintainer (no other changes) python/virtualenv: sed s,distribute,pysetuptools, README system/fs-uae: sed s,distribute,pysetuptools, *.info system/hntool: sed s,distribute,pysetuptools, *.info system/multicorn: sed s,distribute,pysetuptools, *.info system/nvidia-driver: Updated for version 319.32. system/nvidia-kernel: Updated for version 319.32. system/nvidia-legacy173-driver: Added. system/nvidia-legacy173-kernel: Added. system/nvidia-legacy304-driver: Added. system/nvidia-legacy304-kernel: Added. system/nvidia-legacy96-driver: Added. system/nvidia-legacy96-kernel: Added. system/rodent: Updated for version 5.1.0. system/sakura: Trivial - added "updated" comment to script system/sleuthkit: Updated for version 4.1.0. system/tabbed: Updated for version 0.5. From unix_lists at f-m.fm Mon Jul 15 01:48:11 2013 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Sun, 14 Jul 2013 20:48:11 -0500 Subject: [Slackbuilds-users] Fwd: Re: Fwd: Fwd: Build Failure: Slackbuild easymp3gain In-Reply-To: References: <1371173392.21770.140661243727433.43346C3D@webmail.messagingengine.com> <1371173434.21805.140661243728185.39EF3211@webmail.messagingengine.com> <51BB3A64.30402@sandbubble.org> Message-ID: <1373852891.26528.140661255635701.54ED99AC@webmail.messagingengine.com> On Sun, Jul 14, 2013, at 03:19 PM, John Smith wrote: > 2013/6/7 > > > Hello, > > I am trying to build easymp3gain with your slackbuild but I encounter > > the following error: > > > > patching file unitmain.pas > > patching file easymp3gain.lpi > > Hunk #1 succeeded at 490 (offset -4 lines). > > chmod +x ./clean.sh > > ./clean.sh > > chmod +x ./make.sh > > ./make.sh > > Target architecture: i386 > > Target operating system: linux > > Compiler version: 2.6.0 > > Building easyMP3Gain ... > > primary config path: /root/.lazarus > > Error: invalid Lazarus directory "": directory lcl not found > > Failed building easymp3gain.lpr > > make: *** [all] Error 2 > > > > All dependencies are installed and I am running Slackware 14.0. > > > > -- > > Regards, > > 2>&1 > > > > Hello and sorry for the very late answer. > Could you try lazarus 0.9.30.4 from here: > http://slackbuilds.org/repository/13.37/development/lazarus/ Hi, Just tried again and received the following error: patching file easymp3gain.lpi Hunk #1 succeeded at 490 (offset -4 lines). chmod +x ./clean.sh ./clean.sh chmod +x ./make.sh ./make.sh Target architecture: i386 Target operating system: linux Compiler version: 2.6.0 Building easyMP3Gain ... primary config path: /root/.lazarus Error: invalid Lazarus directory "": directory lcl not found Failed building easymp3gain.lpr make: *** [all] Error 2 Regards, 2>&1 From manbornofwoman at gmail.com Mon Jul 15 16:32:08 2013 From: manbornofwoman at gmail.com (manbornofwoman) Date: Mon, 15 Jul 2013 20:32:08 +0400 Subject: [Slackbuilds-users] Fwd: Re: Fwd: Fwd: Build Failure: Slackbuild easymp3gain In-Reply-To: <1373852891.26528.140661255635701.54ED99AC@webmail.messagingengine.com> References: <1371173392.21770.140661243727433.43346C3D@webmail.messagingengine.com> <1371173434.21805.140661243728185.39EF3211@webmail.messagingengine.com> <51BB3A64.30402@sandbubble.org> <1373852891.26528.140661255635701.54ED99AC@webmail.messagingengine.com> Message-ID: I am not sure what to try next. With lazarus-0.9.30.4, I was able to build easymp3gain 1 - aacgain-1.9-i486-3_SBo.tgz 2 - mp3gain-1.5.2.r2-i486-1_SBo.tgz 3 - vorbisgain-0.37-i486-1_SBo.tgz 4 - fpc-2.6.0-i386-2_SBo.tgz 5 - fpc-source-2.6.0-noarch-1_SBo.tgz 6 - lazarus-0.9.30.4-i386-1_SBo.tgz 7 - easymp3gain-0.5.0-i386-1_SBo.tgz # pwd /root # ls -l .lazarus/ total 0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From artourter at gmail.com Mon Jul 15 17:52:20 2013 From: artourter at gmail.com (Greg' Ar Tourter) Date: Mon, 15 Jul 2013 18:52:20 +0100 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info Message-ID: Hi, All the recently released/updated nvidia*-driver.info file are missing the source files and associated md5sum for the 64bit version. There are indeed common to bot the 32 and 64 bit version but need to be specified for both. Currently sbopkg fails because it isn't downloading the tar.xz files on 64bit machines since only the .run file is specified. I attach a patch for the non legacy version but the legacy ones need a similar treatment. Cheers Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-driver.info_64bit.patch Type: application/octet-stream Size: 1353 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Jul 15 17:56:58 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 15 Jul 2013 12:56:58 -0500 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: References: Message-ID: <20130715125658.0f714fef@home.rlworkman.net> On Mon, 15 Jul 2013 18:52:20 +0100 "Greg' Ar Tourter" wrote: > All the recently released/updated nvidia*-driver.info file are > missing the source files and associated md5sum for the 64bit version. > There are indeed common to bot the 32 and 64 bit version but need to > be specified for both. Currently sbopkg fails because it isn't > downloading the tar.xz files on 64bit machines since only the .run > file is specified. Hrm, my fault, but I'm not convinced that sbopkg is DTRT. I'm going to CC the sbopkg list to solicit feedback, but it's my point of view that sbopkg should *always* pull the things specified in $DOWNLOAD, and if on x86_64, pull the things specified in $DOWNLOAD_x86_64. Unless my memory is failing me, that is how we envisioned things working when we added the *_x86_64 variables to the .info file. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From artourter at gmail.com Mon Jul 15 19:31:58 2013 From: artourter at gmail.com (Greg' Ar Tourter) Date: Mon, 15 Jul 2013 20:31:58 +0100 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: <20130715125658.0f714fef@home.rlworkman.net> References: <20130715125658.0f714fef@home.rlworkman.net> Message-ID: Hi Robby, Well looking through the repository, the nvidia-driver (and avr8-gnu-toolchain, but that's only for the pdf manual) packages are the only ones with files in common. So asking to download both version seems rather a waste of bandwitdh Moreover, for some packages (ucsc-blat, p4, p4v ), the source file name is the same for 32 and 64 bit version but are downloaded from different locations and have different checksum. in these case, wget with append .1 to the second one and therefore making the slackbuild use the 32bit version instead.(unless sbopkg instruct wget to overwrites the previous version which again would be a waste of bandwidth) just my 2p worth though. Cheers Greg On 15 July 2013 18:56, Robby Workman wrote: > On Mon, 15 Jul 2013 18:52:20 +0100 > "Greg' Ar Tourter" wrote: > > > All the recently released/updated nvidia*-driver.info file are > > missing the source files and associated md5sum for the 64bit version. > > There are indeed common to bot the 32 and 64 bit version but need to > > be specified for both. Currently sbopkg fails because it isn't > > downloading the tar.xz files on 64bit machines since only the .run > > file is specified. > > > Hrm, my fault, but I'm not convinced that sbopkg is DTRT. > > I'm going to CC the sbopkg list to solicit feedback, but it's my point > of view that sbopkg should *always* pull the things specified in > $DOWNLOAD, and if on x86_64, pull the things specified in > $DOWNLOAD_x86_64. Unless my memory is failing me, that is how we > envisioned things working when we added the *_x86_64 variables to > the .info file. > > -RW > -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Mon Jul 15 19:45:41 2013 From: erik at slackbuilds.org (Erik Hanson) Date: Mon, 15 Jul 2013 14:45:41 -0500 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: <20130715125658.0f714fef@home.rlworkman.net> References: <20130715125658.0f714fef@home.rlworkman.net> Message-ID: <20130715144541.6e09ffb1@shaggy.doo> On Mon, 15 Jul 2013 12:56:58 -0500 Robby Workman wrote: > Unless my memory is failing me, that is how we envisioned things > working when we added the *_x86_64 variables to the .info file. This may have been the original idea, however I think it doesn't work well in practice. Treating it that way causes unnecessary downloads in the case of many things, such as binary repacks. LibreOffice comes to mind as something I think most people would prefer not to download twice. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From jbernts at broadpark.no Mon Jul 15 22:09:48 2013 From: jbernts at broadpark.no (Jostein Berntsen) Date: Tue, 16 Jul 2013 00:09:48 +0200 Subject: [Slackbuilds-users] CurseTheWeather not found Message-ID: <20130715220948.GD2980@jostein> I get this error message when installing CurseTheWeather: Processing CurseTheWeather CurseTheWeather: CurseTheWeather not found in /var/cache/sbopkg. --2013-07-16 00:07:53-- http://opensource.hld.ca/trac.cgi/export/317/trunk/ctw/dist/CurseTheWeather-0.6.tar.gz Resolving opensource.hld.ca (opensource.hld.ca)... 54.235.86.208 Connecting to opensource.hld.ca (opensource.hld.ca)|54.235.86.208|:80... connected. HTTP foresp?rsel sendt, mottar topptekster... 404 Not Found 2013-07-16 00:07:53 FEIL 404: Not Found. Jostein From rneri at libero.it Tue Jul 16 05:34:35 2013 From: rneri at libero.it (rneri at libero.it) Date: Tue, 16 Jul 2013 07:34:35 +0200 (CEST) Subject: [Slackbuilds-users] Obsolete patch in system/rodent Message-ID: <26441874.1690721373952875681.JavaMail.defaultUser@defaultHost> Hi, could you please remove the file rodent-5.0.5.patch from system/rodent, it's just a leftover from previous version. Thanks Roberto From rworkman at slackbuilds.org Tue Jul 16 05:52:10 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 16 Jul 2013 00:52:10 -0500 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: References: <20130715125658.0f714fef@home.rlworkman.net> Message-ID: <20130716005210.45ecbdd5@home.rlworkman.net> On Mon, 15 Jul 2013 20:31:58 +0100 "Greg' Ar Tourter" wrote: > Hi Robby, > > Well looking through the repository, the nvidia-driver (and > avr8-gnu-toolchain, but that's only for the pdf manual) packages are > the only ones with files in common. So asking to download both > version seems rather a waste of bandwitdh Okay, fair point. > Moreover, for some packages (ucsc-blat, p4, p4v ), the source file > name is the same for 32 and 64 bit version but are downloaded from > different locations and have different checksum. in these case, wget > with append .1 to the second one and therefore making the slackbuild > use the 32bit version instead. Oh wow, I wasn't aware of that. Given all of this and erik's reply, I think it's probably a good change to make. Don't feel obligated to do this, as I don't mind doing it myself, but since I'm a bit tied up on another project right now, patches for all of the affected stuff would make this easier :) Also, since you pointed it out, you should be credited with the fixes anyway. Seriously, though, if you don't want to do it or don't have time, that's fine. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Tue Jul 16 06:57:28 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 15 Jul 2013 23:57:28 -0700 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: <20130716005210.45ecbdd5@home.rlworkman.net> References: <20130715125658.0f714fef@home.rlworkman.net> <20130716005210.45ecbdd5@home.rlworkman.net> Message-ID: <51E4EED8.1010604@gmail.com> On 07/15/2013 10:52 PM, Robby Workman wrote: > On Mon, 15 Jul 2013 20:31:58 +0100 > "Greg' Ar Tourter" wrote: > >> Hi Robby, >> >> Well looking through the repository, the nvidia-driver (and >> avr8-gnu-toolchain, but that's only for the pdf manual) packages are >> the only ones with files in common. So asking to download both >> version seems rather a waste of bandwitdh > > > Okay, fair point. > > >> Moreover, for some packages (ucsc-blat, p4, p4v ), the source file >> name is the same for 32 and 64 bit version but are downloaded from >> different locations and have different checksum. in these case, wget >> with append .1 to the second one and therefore making the slackbuild >> use the 32bit version instead. > > > Oh wow, I wasn't aware of that. > > Given all of this and erik's reply, I think it's probably a good > change to make. > > Don't feel obligated to do this, as I don't mind doing it myself, > but since I'm a bit tied up on another project right now, patches > for all of the affected stuff would make this easier :) Also, > since you pointed it out, you should be credited with the fixes > anyway. > > Seriously, though, if you don't want to do it or don't have time, > that's fine. > > -RW > > > Well, the question I have, as a script maintainer, what will be the policy going forward? This is a bit of a chicken/egg problem as well: do we fix SBo to work with how sbopkg does things, or does sbopkg change to accommodate SBo? Perhaps an idea is, instead of increasing the complexity/redundancy of the .info file, we fix the sbopkg to correctly deal with the 32/64 downloads (re: Greg's examples; you only get ONE source file block - pick one). For cases like nvidia-*, we separate out the utilities into a separate arch agnostic package, with the nvidia-driver package just for the 2 arch downloads. Simplicity == Ruggedness == Stability Personally, I volunteer to assist SBo, and don't really give a fig about sbopkg (popular though it is). Unless, of course, sbopkg is now an officially sanctioned SBo utility - similar to how slackpkg is now in the official Slackware tree. Although, I doubt the slackpkg team us telling our BDFL how to fix his package tree to make it easier for them... -Ed From c.willing at uq.edu.au Tue Jul 16 07:23:43 2013 From: c.willing at uq.edu.au (Christoph Willing) Date: Tue, 16 Jul 2013 17:23:43 +1000 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: <51E4EED8.1010604@gmail.com> References: <20130715125658.0f714fef@home.rlworkman.net> <20130716005210.45ecbdd5@home.rlworkman.net> <51E4EED8.1010604@gmail.com> Message-ID: On 16/07/2013, at 4:57 PM, King Beowulf wrote: > On 07/15/2013 10:52 PM, Robby Workman wrote: >> On Mon, 15 Jul 2013 20:31:58 +0100 >> "Greg' Ar Tourter" wrote: >> >>> Hi Robby, >>> >>> Well looking through the repository, the nvidia-driver (and >>> avr8-gnu-toolchain, but that's only for the pdf manual) packages are >>> the only ones with files in common. So asking to download both >>> version seems rather a waste of bandwitdh >> >> >> Okay, fair point. >> >> >>> Moreover, for some packages (ucsc-blat, p4, p4v ), the source file >>> name is the same for 32 and 64 bit version but are downloaded from >>> different locations and have different checksum. in these case, wget >>> with append .1 to the second one and therefore making the slackbuild >>> use the 32bit version instead. >> >> >> Oh wow, I wasn't aware of that. >> >> Given all of this and erik's reply, I think it's probably a good >> change to make. >> >> Don't feel obligated to do this, as I don't mind doing it myself, >> but since I'm a bit tied up on another project right now, patches >> for all of the affected stuff would make this easier :) Also, >> since you pointed it out, you should be credited with the fixes >> anyway. >> >> Seriously, though, if you don't want to do it or don't have time, >> that's fine. >> >> -RW >> >> >> > > Well, the question I have, as a script maintainer, what will be the > policy going forward? This is a bit of a chicken/egg problem as well: > do we fix SBo to work with how sbopkg does things, or does sbopkg change > to accommodate SBo? > > Perhaps an idea is, instead of increasing the complexity/redundancy of > the .info file, we fix the sbopkg to correctly deal with the 32/64 > downloads (re: Greg's examples; you only get ONE source file block - > pick one). For cases like nvidia-*, we separate out the utilities into > a separate arch agnostic package, with the nvidia-driver package just > for the 2 arch downloads. > > Simplicity == Ruggedness == Stability > > Personally, I volunteer to assist SBo, and don't really give a fig about > sbopkg (popular though it is). I don't use sbopkg but have my own build system wrapping SBo's. If building for x86_64, it uses the DOWNLOAD_x86_64 field if its not empty, otherwise uses whatever is in the DOWNLOAD field. 32bit builds use just the DOWNLOAD field. Isn't that the way its supposed to work i.e. DOWNLOAD_x86_64 only contains something if something x86_64 specific is needed, otherwise the ordinary DOWNLOAD field contains whatever is needed? I'm not sure what the use case would be to download both. > Unless, of course, sbopkg is now an > officially sanctioned SBo utility - similar to how slackpkg is now in > the official Slackware tree. Although, I doubt the slackpkg team us > telling our BDFL how to fix his package tree to make it easier for them? > > -Ed Yes, I agree; fix the non conforming stuff rather than cater to it. chris From pprkut at liwjatan.at Tue Jul 16 09:26:01 2013 From: pprkut at liwjatan.at (Heinz Wiesinger) Date: Tue, 16 Jul 2013 11:26:01 +0200 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: <20130715125658.0f714fef@home.rlworkman.net> References: <20130715125658.0f714fef@home.rlworkman.net> Message-ID: <1626782.psE4A77K31@callisto> On Monday 15 July 2013 12:56:58 Robby Workman wrote: > On Mon, 15 Jul 2013 18:52:20 +0100 > > "Greg' Ar Tourter" wrote: > > All the recently released/updated nvidia*-driver.info file are > > missing the source files and associated md5sum for the 64bit version. > > There are indeed common to bot the 32 and 64 bit version but need to > > be specified for both. Currently sbopkg fails because it isn't > > downloading the tar.xz files on 64bit machines since only the .run > > file is specified. > > Hrm, my fault, but I'm not convinced that sbopkg is DTRT. > > I'm going to CC the sbopkg list to solicit feedback, but it's my point > of view that sbopkg should *always* pull the things specified in > $DOWNLOAD, and if on x86_64, pull the things specified in > $DOWNLOAD_x86_64. Unless my memory is failing me, that is how we > envisioned things working when we added the *_x86_64 variables to > the .info file. It's a little bit more complicated. The way it was meant: When DOWNLOAD_x86_64 is empty, use DOWNLOAD (indicating source is the same for both platforms), if filled (and not UNSUPPORTED/UNTESTED) use DOWNLOAD_x86_64 (different source per platform). And then there is also the rather rare case where DOWNLOAD could be UNSUPPORTED/UNTESTED (app works only on x86_64). This is also more or less how the website logic works when displaying download links to the sources. Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 230 bytes Desc: This is a digitally signed message part. URL: From niels.horn at gmail.com Tue Jul 16 11:48:33 2013 From: niels.horn at gmail.com (Niels Horn) Date: Tue, 16 Jul 2013 08:48:33 -0300 Subject: [Slackbuilds-users] Obsolete patch in system/rodent In-Reply-To: <26441874.1690721373952875681.JavaMail.defaultUser@defaultHost> References: <26441874.1690721373952875681.JavaMail.defaultUser@defaultHost> Message-ID: On Tue, Jul 16, 2013 at 2:34 AM, rneri at libero.it wrote: > Hi, > could you please remove the file rodent-5.0.5.patch from system/rodent, > it's > just a leftover from previous version. > Thanks > Roberto > > Fixed in my branch. Thanks! -- Niels Horn -------------- next part -------------- An HTML attachment was scrubbed... URL: From artourter at gmail.com Tue Jul 16 12:52:59 2013 From: artourter at gmail.com (Greg' Ar Tourter) Date: Tue, 16 Jul 2013 13:52:59 +0100 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: <20130716005210.45ecbdd5@home.rlworkman.net> References: <20130715125658.0f714fef@home.rlworkman.net> <20130716005210.45ecbdd5@home.rlworkman.net> Message-ID: Hi Robby, No problems, it was easy enough to do. I include the remaining 3 patches in the same format as the previous one. If you prefer them differently let me know. Cheers Greg On 16 July 2013 06:52, Robby Workman wrote: > On Mon, 15 Jul 2013 20:31:58 +0100 > "Greg' Ar Tourter" wrote: > > > Hi Robby, > > > > Well looking through the repository, the nvidia-driver (and > > avr8-gnu-toolchain, but that's only for the pdf manual) packages are > > the only ones with files in common. So asking to download both > > version seems rather a waste of bandwitdh > > > Okay, fair point. > > > > Moreover, for some packages (ucsc-blat, p4, p4v ), the source file > > name is the same for 32 and 64 bit version but are downloaded from > > different locations and have different checksum. in these case, wget > > with append .1 to the second one and therefore making the slackbuild > > use the 32bit version instead. > > > Oh wow, I wasn't aware of that. > > Given all of this and erik's reply, I think it's probably a good > change to make. > > Don't feel obligated to do this, as I don't mind doing it myself, > but since I'm a bit tied up on another project right now, patches > for all of the affected stuff would make this easier :) Also, > since you pointed it out, you should be credited with the fixes > anyway. > > Seriously, though, if you don't want to do it or don't have time, > that's fine. > > -RW > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-legacy96-driver.patch Type: application/octet-stream Size: 1125 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-legacy173-driver.patch Type: application/octet-stream Size: 1137 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-legacy304-driver.patch Type: application/octet-stream Size: 1142 bytes Desc: not available URL: From andrew.maraev60 at yandex.ru Tue Jul 16 19:58:05 2013 From: andrew.maraev60 at yandex.ru (Andrey Maraev) Date: Tue, 16 Jul 2013 23:58:05 +0400 Subject: [Slackbuilds-users] Format for SlackBuild Upload Form Message-ID: <20130716235805.1d3994f0@ed.ed.19> Sorry, I probably skipped the message in mailinglist. What should download format for updates to new versions of software on the SlackBuild Upload Form - diff or full (SlackBuild, info, etc)? Thanks From matteo.bernardini at gmail.com Tue Jul 16 20:41:07 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 16 Jul 2013 22:41:07 +0200 Subject: [Slackbuilds-users] Format for SlackBuild Upload Form In-Reply-To: <20130716235805.1d3994f0@ed.ed.19> References: <20130716235805.1d3994f0@ed.ed.19> Message-ID: 2013/7/16 Andrey Maraev : > Sorry, I probably skipped the message in mailinglist. What should > download format for updates to new versions of software on the > SlackBuild Upload Form - diff or full (SlackBuild, info, etc)? a tarball with everything inside: this still applies http://slackbuilds.org/guidelines/ From andrew.maraev60 at yandex.ru Tue Jul 16 20:56:35 2013 From: andrew.maraev60 at yandex.ru (Andrey Maraev) Date: Wed, 17 Jul 2013 00:56:35 +0400 Subject: [Slackbuilds-users] Format for SlackBuild Upload Form In-Reply-To: References: <20130716235805.1d3994f0@ed.ed.19> Message-ID: <20130717005635.3789dbf8@ed.ed.19> ? Tue, 16 Jul 2013 22:41:07 +0200 Matteo Bernardini ?????: > a tarball with everything inside: this still applies > > http://slackbuilds.org/guidelines/ Thanks From thomasrling at gmail.com Tue Jul 16 21:22:33 2013 From: thomasrling at gmail.com (Thomas) Date: Tue, 16 Jul 2013 17:22:33 -0400 Subject: [Slackbuilds-users] games/einstein source link broken Message-ID: It seems the website for this game has been down since about late January. http://games.flowix.com/ With some changes it's possible to use Debian's source. I've generated a diff if anyone is interested. http://pastebin.com/PKVYWFPs It adds the Debian patches for using DejaVuSans.ttf as the font. It also patches the .SlackBuild script to make the einstein.res archive needed by the program. I've only tested this on my machine which is Slackware 14.0 i686 From nishant at mnspace.net Wed Jul 17 02:58:47 2013 From: nishant at mnspace.net (Nishant Limbachia) Date: Tue, 16 Jul 2013 21:58:47 -0500 Subject: [Slackbuilds-users] Updates - 20130714.{1,2} In-Reply-To: <20130714174148.2d8a576e.robby@rlworkman.net> References: <20130714174148.2d8a576e.robby@rlworkman.net> Message-ID: <51E60867.3000105@mnspace.net> On 7/14/2013 5:41 PM, Robby Workman wrote: > +--------------------------+ > Sun Jul 14 22:09:17 UTC 2013 > network/fail2ban: New download link. Hi Admins, Seems like the download link for fail2ban still points to the github link which is incorrect. The download link should point to the dropbox location as in the info file. Thanks, From niels.horn at gmail.com Wed Jul 17 03:27:18 2013 From: niels.horn at gmail.com (Niels Horn) Date: Wed, 17 Jul 2013 00:27:18 -0300 Subject: [Slackbuilds-users] Updates - 20130714.{1,2} In-Reply-To: <51E60867.3000105@mnspace.net> References: <20130714174148.2d8a576e.robby@rlworkman.net> <51E60867.3000105@mnspace.net> Message-ID: Should be fixed now... -- Niels Horn On Tue, Jul 16, 2013 at 11:58 PM, Nishant Limbachia wrote: > On 7/14/2013 5:41 PM, Robby Workman wrote: > > +--------------------------+ > > Sun Jul 14 22:09:17 UTC 2013 > > network/fail2ban: New download link. > Hi Admins, > > Seems like the download link for fail2ban still points to the github > link which is incorrect. The download link should > point to the dropbox location as in the info file. > > Thanks, > _______________________________________________ > 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: From unix_lists at f-m.fm Wed Jul 17 03:46:38 2013 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Tue, 16 Jul 2013 22:46:38 -0500 Subject: [Slackbuilds-users] Fwd: an update to your slackbuild of qpdfview References: <1372898492.6959.140661251690249.5349C027@webmail.messagingengine.com> Message-ID: <1374032798.3645.140661256552285.65AB6819@webmail.messagingengine.com> Hi, Sent the following about two weeks ago and haven't gotten a response ----- Original message ----- From: dfc at warpmail.net To: smithmark347 at gmail.com Subject: an update to your slackbuild of qpdfview Date: Wed, 03 Jul 2013 19:41:32 -0500 Hello, I've attached two patches to update qpdfview to 4.3. Works for me on x86. --- qpdfview.info 2013-07-03 19:15:33.833705270 -0500 +++ qpdfview.info.diff 2013-07-03 19:22:18.528028011 -0500 @@ -1,8 +1,8 @@ PRGNAM="qpdfview" -VERSION="0.3.7" +VERSION="0.4.3." HOMEPAGE="https://launchpad.net/qpdfview" -DOWNLOAD="https://launchpad.net/qpdfview/trunk/0.3.7/+download/qpdfview-0.3.7.tar.gz" -MD5SUM="2aed46338a10d98af9c815126b435025" +DOWNLOAD="https://launchpad.net/qpdfview/trunk/0.4.3/+download/qpdfview-0.4.3.tar.gz" +MD5SUM="97b7f095adb101f4897aabe831006124" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" --- qpdfview.SlackBuild 2013-07-03 19:15:15.035572964 -0500 +++ qpdfview.SlackBuild.diff 2013-07-03 19:24:06.538044065 -0500 @@ -25,7 +25,7 @@ set -e PRGNAM=qpdfview -VERSION=0.3.7 +VERSION=0.4.3 BUILD=${BUILD:-1} TAG=${TAG:-_SBo} @@ -77,7 +77,7 @@ -exec chmod 644 {} \; #Configure qpdfview. Installation paths are correctly set in qpdfview.pri -qmake QMAKE_CFLAGS="$SLKCFLAGS" QMAKE_CXXFLAGS="$SLKCFLAGS" +qmake QMAKE_CFLAGS="$SLKCFLAGS" QMAKE_CXXFLAGS="$SLKCFLAGS" qpdfview.pro # Compile the application and install it into the $PKG directory make -- Regards, Donald Cooley -------------- next part -------------- A non-text attachment was scrubbed... Name: qpdfview.info.patch Type: application/octet-stream Size: 537 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: qpdfview.SlackBuild.patch Type: application/octet-stream Size: 568 bytes Desc: not available URL: From rworkman at slackbuilds.org Wed Jul 17 04:25:56 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 16 Jul 2013 23:25:56 -0500 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: <1626782.psE4A77K31@callisto> References: <20130715125658.0f714fef@home.rlworkman.net> <1626782.psE4A77K31@callisto> Message-ID: <20130716232556.3b9eb147@home.rlworkman.net> On Tue, 16 Jul 2013 11:26:01 +0200 Heinz Wiesinger wrote: > On Monday 15 July 2013 12:56:58 Robby Workman wrote: > > On Mon, 15 Jul 2013 18:52:20 +0100 > > > > "Greg' Ar Tourter" wrote: > > > All the recently released/updated nvidia*-driver.info file are > > > missing the source files and associated md5sum for the 64bit > > > version. There are indeed common to bot the 32 and 64 bit version > > > but need to be specified for both. Currently sbopkg fails because > > > it isn't downloading the tar.xz files on 64bit machines since > > > only the .run file is specified. > > > > Hrm, my fault, but I'm not convinced that sbopkg is DTRT. > > > > I'm going to CC the sbopkg list to solicit feedback, but it's my > > point of view that sbopkg should *always* pull the things specified > > in $DOWNLOAD, and if on x86_64, pull the things specified in > > $DOWNLOAD_x86_64. Unless my memory is failing me, that is how we > > envisioned things working when we added the *_x86_64 variables to > > the .info file. > > It's a little bit more complicated. The way it was meant: When > DOWNLOAD_x86_64 is empty, use DOWNLOAD (indicating source is the same > for both platforms), if filled (and not UNSUPPORTED/UNTESTED) use > DOWNLOAD_x86_64 (different source per platform). And then there is > also the rather rare case where DOWNLOAD could be > UNSUPPORTED/UNTESTED (app works only on x86_64). This is also more or > less how the website logic works when displaying download links to > the sources. Okay, that makes sense - thanks for the clarification. We should probably document that somewhere public if we haven't already. I should probably keep up better ;-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Wed Jul 17 04:28:09 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 16 Jul 2013 23:28:09 -0500 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: References: <20130715125658.0f714fef@home.rlworkman.net> <20130716005210.45ecbdd5@home.rlworkman.net> <51E4EED8.1010604@gmail.com> Message-ID: <20130716232809.029e5767@home.rlworkman.net> On Tue, 16 Jul 2013 17:23:43 +1000 Christoph Willing wrote: > > On 16/07/2013, at 4:57 PM, King Beowulf wrote: > > > Well, the question I have, as a script maintainer, what will be the > > policy going forward? This is a bit of a chicken/egg problem as > > well: do we fix SBo to work with how sbopkg does things, or does > > sbopkg change to accommodate SBo? > > > > Perhaps an idea is, instead of increasing the complexity/redundancy > > of the .info file, we fix the sbopkg to correctly deal with the > > 32/64 downloads (re: Greg's examples; you only get ONE source file > > block - pick one). For cases like nvidia-*, we separate out the > > utilities into a separate arch agnostic package, with the > > nvidia-driver package just for the 2 arch downloads. > > > > Simplicity == Ruggedness == Stability > > > > Personally, I volunteer to assist SBo, and don't really give a fig > > about sbopkg (popular though it is). > > I don't use sbopkg but have my own build system wrapping SBo's. If > building for x86_64, it uses the DOWNLOAD_x86_64 field if its not > empty, otherwise uses whatever is in the DOWNLOAD field. 32bit builds > use just the DOWNLOAD field. Isn't that the way its supposed to work > i.e. DOWNLOAD_x86_64 only contains something if something x86_64 > specific is needed, otherwise the ordinary DOWNLOAD field contains > whatever is needed? > > I'm not sure what the use case would be to download both. I think Heinz's reply should clarify any misunderstanding I caused here :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Wed Jul 17 04:31:57 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 16 Jul 2013 23:31:57 -0500 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: <51E4EED8.1010604@gmail.com> References: <20130715125658.0f714fef@home.rlworkman.net> <20130716005210.45ecbdd5@home.rlworkman.net> <51E4EED8.1010604@gmail.com> Message-ID: <20130716233157.6f19ff5c@home.rlworkman.net> On Mon, 15 Jul 2013 23:57:28 -0700 King Beowulf wrote: > Well, the question I have, as a script maintainer, what will be the > policy going forward? This is a bit of a chicken/egg problem as well: > do we fix SBo to work with how sbopkg does things, or does sbopkg > change to accommodate SBo? > > Perhaps an idea is, instead of increasing the complexity/redundancy of > the .info file, we fix the sbopkg to correctly deal with the 32/64 > downloads (re: Greg's examples; you only get ONE source file block - > pick one). For cases like nvidia-*, we separate out the utilities > into a separate arch agnostic package, with the nvidia-driver package > just for the 2 arch downloads. I think pprkut's reply earlier should clarify the misunderstanding that I created here :/ Also, I'd like to point out that you had submitted all of these nvidia-* builds correctly, and then *I* removed the dupe links in *_x86_64 lines in the .info file. In summary, you did it right - I screwed it up. Sorry :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Wed Jul 17 04:41:37 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 16 Jul 2013 23:41:37 -0500 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: References: <20130715125658.0f714fef@home.rlworkman.net> <20130716005210.45ecbdd5@home.rlworkman.net> Message-ID: <20130716234137.5e5a5dd0@home.rlworkman.net> On Tue, 16 Jul 2013 13:52:59 +0100 "Greg' Ar Tourter" wrote: > No problems, it was easy enough to do. I include the remaining 3 > patches in the same format as the previous one. If you prefer them > differently let me know. All pushed to my git branch, with one minor fixup in the legacy96 download link -- the "6" in "XFree86" got dropped somehow. Thanks for handling this - much appreciated :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Wed Jul 17 04:53:59 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 16 Jul 2013 23:53:59 -0500 Subject: [Slackbuilds-users] CurseTheWeather not found In-Reply-To: <20130715220948.GD2980@jostein> References: <20130715220948.GD2980@jostein> Message-ID: <20130716235359.0be4b53f@home.rlworkman.net> On Tue, 16 Jul 2013 00:09:48 +0200 Jostein Berntsen wrote: > I get this error message when installing CurseTheWeather: > > Processing CurseTheWeather > > CurseTheWeather: > CurseTheWeather not found in /var/cache/sbopkg. > --2013-07-16 00:07:53-- > http://opensource.hld.ca/trac.cgi/export/317/trunk/ctw/dist/CurseTheWeather-0.6.tar.gz > Resolving opensource.hld.ca (opensource.hld.ca)... 54.235.86.208 > Connecting to opensource.hld.ca > (opensource.hld.ca)|54.235.86.208|:80... connected. > HTTP foresp?rsel sendt, mottar topptekster... 404 Not Found > 2013-07-16 00:07:53 FEIL 404: Not Found. Homepage and download link give 404 error. Get it here (just pushed this to git too): http://ftp.slackware.org.uk/salix/i486/14.0/source/ap/CurseTheWeather/CurseTheWeather-0.6.tar.gz -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From erik at slackbuilds.org Wed Jul 17 05:07:18 2013 From: erik at slackbuilds.org (Erik Hanson) Date: Wed, 17 Jul 2013 00:07:18 -0500 Subject: [Slackbuilds-users] games/einstein source link broken In-Reply-To: References: Message-ID: <20130717000718.6ce629a8@shaggy.doo> On Tue, 16 Jul 2013 17:22:33 -0400 Thomas wrote: > It seems the website for this game has been down since about late January. > http://games.flowix.com/ Thanks for letting me know, I've updated the download link. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From thomasrling at gmail.com Wed Jul 17 05:29:30 2013 From: thomasrling at gmail.com (Thomas) Date: Wed, 17 Jul 2013 01:29:30 -0400 Subject: [Slackbuilds-users] games/einstein source link broken In-Reply-To: <20130717000718.6ce629a8@shaggy.doo> References: <20130717000718.6ce629a8@shaggy.doo> Message-ID: Thanks much. Apparently I didn't look hard enough for another place to download einstein-2.0-src.tar.gz... hence the diff. On Wed, Jul 17, 2013 at 1:07 AM, Erik Hanson wrote: > On Tue, 16 Jul 2013 17:22:33 -0400 > Thomas wrote: > >> It seems the website for this game has been down since about late January. >> http://games.flowix.com/ > > Thanks for letting me know, I've updated the download link. > > -- > Erik Hanson > > _______________________________________________ > 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 dchmelik at hipplanet.com Wed Jul 17 10:53:55 2013 From: dchmelik at hipplanet.com (David Melik) Date: Wed, 17 Jul 2013 03:53:55 -0700 Subject: [Slackbuilds-users] wxcam SlackBuild failed. Its maintainer no longer uses Slackware Message-ID: <20130717035355.CBC25028@m0005311.ppops.net> From: Pierre Cazenave To: David N Melik Subject: Re: wxcam SlackBuild failure Date: Wed, 17 Jul 2013 09:39:02 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 Hi David, I'm afraid I'm no longer using Slackware which means I can't test and update a new version. If you want to take over maintenance, feel free to do so. Thanks, Pierre On 14/07/13 01:26, David N Melik wrote: > The wxcam SlackBuild fails with the output below. > > > [...] > > CC avilib.o > avilib.c: In function 'AVI_open_input_file': > avilib.c:646:8: warning: variable 'auds_strf_seen' set but not used > [-Wunused-but-set-variable] CXX BaseEncoder.o > CC ccvt.o > ccvt.c: In function 'ccvt_yuyv': > ccvt.c:314:20: warning: variable 'linewidth' set but not used > [-Wunused-but-set-variable] CXX cfile.o > CXX configure.o > In file included from /usr/include/wx-2.8/wx/window.h:23:0, > from /usr/include/wx-2.8/wx/toplevel.h:21, > from /usr/include/wx-2.8/wx/dialog.h:17, > from configure.h:25, > from configure.cpp:21: > /usr/include/wx-2.8/wx/cursor.h: In constructor > 'wxBusyCursorSuspender::wxBusyCursorSuspender()': /usr/include/wx-2.8/wx/cursor.h:65:22: > error: 'wxIsBusy' was not declared in this > scope /usr/include/wx-2.8/wx/cursor.h:67:26: error: 'wxBusyCursor' has > not been declared /usr/include/wx-2.8/wx/cursor.h:67:58: error: > 'wxSetCursor' was not declared in this > scope /usr/include/wx-2.8/wx/cursor.h: In destructor > 'wxBusyCursorSuspender::~wxBusyCursorSuspender()': /usr/include/wx-2.8/wx/cursor.h:72:22: > error: 'wxIsBusy' was not declared in this > scope /usr/include/wx-2.8/wx/cursor.h:74:26: error: 'wxBusyCursor' has > not been declared /usr/include/wx-2.8/wx/cursor.h:74:56: error: > 'wxSetCursor' was not declared in this scope In file included > from /usr/include/wx-2.8/wx/window.h:26:0, > from /usr/include/wx-2.8/wx/toplevel.h:21, > from /usr/include/wx-2.8/wx/dialog.h:17, from configure.h:25, from > configure.cpp:21: /usr/include/wx-2.8/wx/region.h: In member function > 'bool wxRegionBase::Intersect(const > wxRect&)': /usr/include/wx-2.8/wx/region.h:251:37: error: invalid use > of incomplete type 'class wxRegion' In file included > from /usr/include/wx-2.8/wx/region.h:16:0, > from /usr/include/wx-2.8/wx/window.h:26, > from /usr/include/wx-2.8/wx/toplevel.h:21, > from /usr/include/wx-2.8/wx/dialog.h:17, from configure.h:25, from > configure.cpp:21: /usr/include/wx-2.8/wx/gdicmn.h:38:28: error: forward > declaration of 'class wxRegion' In file included > from /usr/include/wx-2.8/wx/window.h:26:0, > from /usr/include/wx-2.8/wx/toplevel.h:21, > from /usr/include/wx-2.8/wx/dialog.h:17, from configure.h:25, from > configure.cpp:21: /usr/include/wx-2.8/wx/region.h: In member function > 'bool wxRegionBase::Subtract(const > wxRect&)': /usr/include/wx-2.8/wx/region.h:256:36: error: invalid use > of incomplete type 'class wxRegion' In file included > from /usr/include/wx-2.8/wx/region.h:16:0, > from /usr/include/wx-2.8/wx/window.h:26, > from /usr/include/wx-2.8/wx/toplevel.h:21, > from /usr/include/wx-2.8/wx/dialog.h:17, from configure.h:25, from > configure.cpp:21: /usr/include/wx-2.8/wx/gdicmn.h:38:28: error: forward > declaration of 'class wxRegion' In file included > from /usr/include/wx-2.8/wx/window.h:26:0, > from /usr/include/wx-2.8/wx/toplevel.h:21, > from /usr/include/wx-2.8/wx/dialog.h:17, from configure.h:25, from > configure.cpp:21: /usr/include/wx-2.8/wx/region.h: In member function > 'bool wxRegionBase::Xor(const > wxRect&)': /usr/include/wx-2.8/wx/region.h:261:31: error: invalid use > of incomplete type 'class wxRegion' In file included > from /usr/include/wx-2.8/wx/region.h:16:0, > from /usr/include/wx-2.8/wx/window.h:26, > from /usr/include/wx-2.8/wx/toplevel.h:21, > from /usr/include/wx-2.8/wx/dialog.h:17, from configure.h:25, from > configure.cpp:21: /usr/include/wx-2.8/wx/gdicmn.h:38:28: error: forward > declaration of 'class wxRegion' In file included > from /usr/include/wx-2.8/wx/toplevel.h:21:0, > from /usr/include/wx-2.8/wx/dialog.h:17, from configure.h:25, > from configure.cpp:21: > /usr/include/wx-2.8/wx/window.h: At global scope: > /usr/include/wx-2.8/wx/window.h:82:12: error: field 'font' has > incomplete type /usr/include/wx-2.8/wx/window.h:85:14: error: field > 'colFg' has incomplete type /usr/include/wx-2.8/wx/window.h:89:14: > error: field 'colBg' has incomplete > type /usr/include/wx-2.8/wx/window.h:920:35: error: 'wxUpdateUIEvent' > has not been declared /usr/include/wx-2.8/wx/window.h:1116:30: error: > 'wxSysColourChangedEvent' has not been > declared /usr/include/wx-2.8/wx/window.h:1117:24: error: > 'wxInitDialogEvent' has not been > declared /usr/include/wx-2.8/wx/window.h:1118:25: error: 'wxMouseEvent' > has not been declared /usr/include/wx-2.8/wx/window.h:1133:13: error: > 'WXWidget' does not name a > type /usr/include/wx-2.8/wx/window.h:1135:34: error: 'WXWidget' has not > been declared /usr/include/wx-2.8/wx/window.h:1230:26: error: field > 'm_cursor' has incomplete type /usr/include/wx-2.8/wx/window.h:1231:26: > error: field 'm_font' has incomplete > type /usr/include/wx-2.8/wx/window.h:1232:26: error: field > 'm_backgroundColour' has incomplete > type /usr/include/wx-2.8/wx/window.h:1233:26: error: field > 'm_foregroundColour' has incomplete > type /usr/include/wx-2.8/wx/window.h:1240:26: error: field > 'm_updateRegion' has incomplete > type /usr/include/wx-2.8/wx/window.h:562:39: error: incomplete type > 'wxNavigationKeyEvent' used in nested name > specifier /usr/include/wx-2.8/wx/window.h: In member function 'const > wxRegion& wxWindowBase::GetUpdateRegion() > const': /usr/include/wx-2.8/wx/window.h:761:54: error: 'm_updateRegion' > was not declared in this scope /usr/include/wx-2.8/wx/window.h: In > member function 'wxRegion& > wxWindowBase::GetUpdateRegion()': /usr/include/wx-2.8/wx/window.h:762:42: > error: 'm_updateRegion' was not declared in this > scope /usr/include/wx-2.8/wx/window.h: In member function 'const > wxCursor& wxWindowBase::GetCursor() > const': /usr/include/wx-2.8/wx/window.h:850:48: error: 'm_cursor' was > not declared in this scope /usr/include/wx-2.8/wx/window.h: In member > function 'wxWindow* wxWindowBase::GetGrandParent() > const': /usr/include/wx-2.8/wx/window.h:1547:31: error: invalid use of > incomplete type 'class wxWindow' In file included > from /usr/include/wx-2.8/wx/wx.h:27:0, from configure.h:24, from > configure.cpp:21: /usr/include/wx-2.8/wx/utils.h:51:24: error: forward > declaration of 'class wxWindow' In file included > from /usr/include/wx-2.8/wx/dialog.h:17:0, from configure.h:25, from > configure.cpp:21: /usr/include/wx-2.8/wx/toplevel.h: At global > scope: /usr/include/wx-2.8/wx/toplevel.h:119:1: error: invalid use of > incomplete type 'class wxWindow' In file included > from /usr/include/wx-2.8/wx/wx.h:27:0, from configure.h:24, from > configure.cpp:21: /usr/include/wx-2.8/wx/utils.h:51:24: error: forward > declaration of 'class wxWindow' In file included > from /usr/include/wx-2.8/wx/dialog.h:17:0, from configure.h:25, from > configure.cpp:21: /usr/include/wx-2.8/wx/toplevel.h:238:24: error: > 'wxCloseEvent' has not been > declared /usr/include/wx-2.8/wx/toplevel.h:239:17: error: 'wxSizeEvent' > has not been declared /usr/include/wx-2.8/wx/toplevel.h:246:21: error: > 'wxActivateEvent' has not been > declared /usr/include/wx-2.8/wx/toplevel.h:249:35: error: > 'wxUpdateUIEvent' has not been > declared /usr/include/wx-2.8/wx/toplevel.h: In member function 'virtual > bool > wxTopLevelWindowBase::IsActive()': /usr/include/wx-2.8/wx/toplevel.h:183:68: > error: 'FindFocus' was not declared in this > scope /usr/include/wx-2.8/wx/toplevel.h: In member function 'virtual > bool wxTopLevelWindowBase::IsVisible() > const': /usr/include/wx-2.8/wx/toplevel.h:235:53: error: 'IsShown' was > not declared in this scope /usr/include/wx-2.8/wx/toplevel.h: In member > function 'virtual void wxTopLevelWindowBase::DoGetScreenPosition(int*, > int*) const': /usr/include/wx-2.8/wx/toplevel.h:273:27: error: > 'DoGetPosition' was not declared in this scope In file included from > configure.h:25:0, from > configure.cpp:21: /usr/include/wx-2.8/wx/dialog.h: At global > scope: /usr/include/wx-2.8/wx/dialog.h:33:1: error: expected class-name > before '{' token /usr/include/wx-2.8/wx/dialog.h:101:36: error: > 'wxKeyEvent' does not name a > type /usr/include/wx-2.8/wx/dialog.h:101:48: error: ISO C++ forbids > declaration of 'event' with no type > [-fpermissive] /usr/include/wx-2.8/wx/dialog.h:126:21: error: > 'wxKeyEvent' has not been > declared /usr/include/wx-2.8/wx/dialog.h:129:24: error: 'wxCloseEvent' > has not been declared /usr/include/wx-2.8/wx/dialog.h:132:19: error: > 'wxCommandEvent' has not been > declared /usr/include/wx-2.8/wx/dialog.h:135:29: error: > 'wxSysColourChangedEvent' has not been > declared /usr/include/wx-2.8/wx/dialog.h:140:5: error: > 'wxChildFocusEvent' has not been declared In file included from > configure.cpp:21:0: configure.h:36:1: error: expected class-name before > '{' token configure.h:46:9: error: 'wxPanel' does not name a type > configure.h:47:9: error: 'wxPanel' does not name a type > configure.h:48:9: error: 'wxPanel' does not name a type > configure.h:51:9: error: 'wxComboBox' does not name a type > configure.h:52:9: error: 'wxComboBox' does not name a type > configure.h:53:9: error: 'wxRadioBox' does not name a type > configure.h:54:9: error: 'wxRadioBox' does not name a type > configure.h:55:9: error: 'wxRadioBox' does not name a type > configure.h:56:9: error: 'wxStaticBox' does not name a type > configure.h:57:9: error: 'wxStaticBox' does not name a type > configure.h:58:9: error: 'wxSlider' does not name a type > configure.h:59:9: error: 'wxSlider' does not name a type > configure.h:60:9: error: 'wxCheckBox' does not name a type > configure.h:61:9: error: 'wxStaticText' does not name a type > configure.h:62:9: error: 'wxStaticText' does not name a type > configure.h:65:26: error: 'wxCommandEvent' has not been declared > configure.h:66:26: error: 'wxCommandEvent' has not been declared > configure.h:67:19: error: 'wxCommandEvent' has not been declared > configure.h:68:36: error: 'wxCommandEvent' has not been declared > configure.h:69:29: error: 'wxCommandEvent' has not been declared > configure.cpp:36:1: error: 'wxPropertySheetDialog' has not been > declared configure.cpp:38:1: error: 'wxPropertySheetDialog' has not > been declared configure.cpp:39:1: error: invalid use of non-static > member function 'void ConfigureDialog::OnSaveImage(int&)' > configure.cpp:39:1: error: 'wxCommandEventHandler' was not declared in > this scope configure.cpp:40:1: error: invalid use of non-static member > function 'void ConfigureDialog::OnSaveVideo(int&)' configure.cpp:40:1: > error: 'wxCommandEventHandler' was not declared in this scope > configure.cpp:41:1: error: invalid use of non-static member function > 'void ConfigureDialog::OnOk(int&)' configure.cpp:41:1: error: > 'wxCommandEventHandler' was not declared in this scope > configure.cpp:42:1: error: invalid use of non-static member function > 'void ConfigureDialog::OnRadioBoxCompression(int&)' configure.cpp:42:1: > error: 'wxCommandEventHandler' was not declared in this scope > configure.cpp:43:1: error: invalid use of non-static member function > 'void ConfigureDialog::OnAudioChanged(int&)' configure.cpp:43:1: error: > 'wxCommandEventHandler' was not declared in this scope configure.cpp: > In constructor 'ConfigureDialog::ConfigureDialog(wxWindow*)': > configure.cpp:48:71: error: 'SetExtraStyle' was not declared in this > scope configure.cpp:60:22: error: 'wxPROPSHEET_SHRINKTOFIT' was not > declared in this scope configure.cpp:62:19: error: > 'wxPROPSHEET_TOOLBOOK' was not declared in this scope > configure.cpp:64:29: error: 'SetSheetStyle' was not declared in this > scope configure.cpp:65:26: error: 'SetSheetInnerBorder' was not > declared in this scope configure.cpp:66:26: error: > 'SetSheetOuterBorder' was not declared in this scope > configure.cpp:71:39: error: invalid use of incomplete type 'class > wxIcon' In file included from /usr/include/wx-2.8/wx/region.h:16:0, > from /usr/include/wx-2.8/wx/window.h:26, > from /usr/include/wx-2.8/wx/toplevel.h:21, > from /usr/include/wx-2.8/wx/dialog.h:17, from configure.h:25, from > configure.cpp:21: /usr/include/wx-2.8/wx/gdicmn.h:35:28: error: forward > declaration of 'class wxIcon' configure.cpp:72:37: error: invalid use > of incomplete type 'class wxIcon' In file included > from /usr/include/wx-2.8/wx/region.h:16:0, > from /usr/include/wx-2.8/wx/window.h:26, > from /usr/include/wx-2.8/wx/toplevel.h:21, > from /usr/include/wx-2.8/wx/dialog.h:17, from configure.h:25, from > configure.cpp:21: /usr/include/wx-2.8/wx/gdicmn.h:35:28: error: forward > declaration of 'class wxIcon' configure.cpp:73:37: error: invalid use > of incomplete type 'class wxIcon' In file included > from /usr/include/wx-2.8/wx/region.h:16:0, > from /usr/include/wx-2.8/wx/window.h:26, > from /usr/include/wx-2.8/wx/toplevel.h:21, > from /usr/include/wx-2.8/wx/dialog.h:17, from configure.h:25, from > configure.cpp:21: /usr/include/wx-2.8/wx/gdicmn.h:35:28: error: forward > declaration of 'class wxIcon' configure.cpp:76:31: error: 'Create' was > not declared in this scope configure.cpp:78:42: error: 'CreateButtons' > was not declared in this scope configure.cpp:80:5: error: > 'wxBookCtrlBase' was not declared in this scope configure.cpp:80:21: > error: 'notebook' was not declared in this scope configure.cpp:80:44: > error: 'GetBookCtrl' was not declared in this scope configure.cpp:83:5: > error: 'wxPanel' was not declared in this scope configure.cpp:83:14: > error: 'generalSettings' was not declared in this scope > configure.cpp:83:65: error: 'CreateGlobalSettingsPage' was not declared > in this scope configure.cpp:84:14: error: 'saveSettings' was not > declared in this scope configure.cpp:84:64: error: > 'CreateSaveFileSettingsPage' was not declared in this scope > configure.cpp:85:14: error: 'videoSettings' was not declared in this > scope configure.cpp:85:62: error: 'CreateVideoSettingsPage' was not > declared in this scope configure.cpp:91:18: error: 'LayoutDialog' was > not declared in this scope configure.cpp: At global scope: > configure.cpp:94:1: error: 'wxPanel' does not name a type > configure.cpp:141:1: error: 'wxPanel' does not name a type > configure.cpp:166:1: error: 'wxPanel' does not name a type > configure.cpp:241:35: error: variable or field 'OnSaveImage' declared > void configure.cpp:241:35: error: 'wxCommandEvent' was not declared in > this scope configure.cpp:241:68: error: expected primary-expression > before ')' token make[2]: *** [configure.o] Error 1 make[2]: Leaving > directory `/tmp/SBo/wxcam-1.1/src' make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/tmp/SBo/wxcam-1.1' make: *** [all] Error 2 > Failures: wxcam: wxcam.SlackBuild return non-zero > _____________________________________________________________ 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 dave at dawoodfall.net Wed Jul 17 13:07:36 2013 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 17 Jul 2013 14:07:36 +0100 Subject: [Slackbuilds-users] Javascript on slackbuilds.org search results page Message-ID: <20130717130736.GC26657@Blackswan> I've been experiencing an annoying problem in Chromium browser with links on the search results page. I tend to middleclick search results links to open several at once in background tabs. The problem is that Chromium determines a left or a middle click to be a click and so what happens is that the links open tabs, but the location of the results page changes too. >From http://www.w3schools.com/jsref/event_onclick.asp : "Execute a JavaScript when a button is clicked" It is strange that after all the years that javascript has been around that there are no separate 'onleftclick' or 'onmiddleclick' events... So I'm not blaming you guys for it since according to the onclick event it can be any click. But I do have a question: is it /really/ necesary for you to use javascript for simple links in that way? I've had to disable javascript on the slackbuilds site anyway so it seems a bit pointless. FWIW Firefox doesn't share this behaviour. Regards David From miguel at thedeanda.com Wed Jul 17 14:24:21 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Wed, 17 Jul 2013 07:24:21 -0700 Subject: [Slackbuilds-users] Javascript on slackbuilds.org search results page In-Reply-To: <20130717130736.GC26657@Blackswan> References: <20130717130736.GC26657@Blackswan> Message-ID: Thanks David. Ive had the same... Complaint(?) but never voiced it. Ive even gone so far as to right click, open link in new tab but then that makes a single click turn into two with a pause to read the six options that appear. My vote is +1 M On Jul 17, 2013 6:07 AM, "David Woodfall" wrote: > I've been experiencing an annoying problem in Chromium browser with > links on the search results page. > > I tend to middleclick search results links to open several at once in > background tabs. > > The problem is that Chromium determines a left or a middle click to be > a click and so what happens is that the links open tabs, but the > location of the results page changes too. > > From http://www.w3schools.com/**jsref/event_onclick.asp: > > "Execute a JavaScript when a button is clicked" > > It is strange that after all the years that javascript has been around > that there are no separate 'onleftclick' or 'onmiddleclick' events... > > So I'm not blaming you guys for it since according to the onclick > event it can be any click. But I do have a question: is it /really/ > necesary for you to use javascript for simple links in that way? > > I've had to disable javascript on the slackbuilds site anyway so it > seems a bit pointless. > > FWIW Firefox doesn't share this behaviour. > > Regards > > David > > > > ______________________________**_________________ > 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: From willysr at gmail.com Wed Jul 17 15:26:40 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Wed, 17 Jul 2013 22:26:40 +0700 Subject: [Slackbuilds-users] wxcam SlackBuild failed. Its maintainer no longer uses Slackware In-Reply-To: <20130717035355.CBC25028@m0005311.ppops.net> References: <20130717035355.CBC25028@m0005311.ppops.net> Message-ID: > From: Pierre Cazenave > To: David N Melik > Subject: Re: wxcam SlackBuild failure > Date: Wed, 17 Jul 2013 09:39:02 +0100 > User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 > > Hi David, > > I'm afraid I'm no longer using Slackware which means I can't test and > update a new version. If you want to take over maintenance, feel free to > do so. I'm able to build this on my -Current machine with all dependencies packages from SBo, except for wxpython I have wxwidgets compiled manually and it uses 2.9.4, not 2.8.12, but i guess it's OK to se 2.8.12 as that's the stable version. I used 2.9.4 since i have an application that requires 2.9.x branch -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From yalhcru at gmail.com Wed Jul 17 20:43:44 2013 From: yalhcru at gmail.com (B Watson) Date: Wed, 17 Jul 2013 16:43:44 -0400 Subject: [Slackbuilds-users] wxcam SlackBuild failed. Its maintainer no longer uses Slackware In-Reply-To: References: <20130717035355.CBC25028@m0005311.ppops.net> Message-ID: Builds fine here, Slackware64 14.0, with: CImg-1.4.6-noarch-1_SBo mjpegtools-1.9.0-x86_64-3_SBo wxPython-2.8.12.1-x86_64-1_SBo xvidcore-1.3.2-x86_64-1_SBo Was your failed build happening on 14 or -current? From ml at mareichelt.com Wed Jul 17 21:15:01 2013 From: ml at mareichelt.com (Markus Reichelt) Date: Wed, 17 Jul 2013 23:15:01 +0200 Subject: [Slackbuilds-users] source links broken Message-ID: <20130717211501.GC18904@pc21.mareichelt.com> Aloha! I've heard there's OMGWTF situations wrt broken source links: They all are crystal-clear cases of "Mad Cloud Disease"! Seriously, I've had the habit of mirroring sources needed for buildscripts I maintain, for obvious reasons. I managed to place them at the usual place: http://mareichelt.com/pub/notmine/ From kingbeowulf at gmail.com Fri Jul 19 05:57:46 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 18 Jul 2013 22:57:46 -0700 Subject: [Slackbuilds-users] nvidia-driver.info missing 64bit file info In-Reply-To: <20130716233157.6f19ff5c@home.rlworkman.net> References: <20130715125658.0f714fef@home.rlworkman.net> <20130716005210.45ecbdd5@home.rlworkman.net> <51E4EED8.1010604@gmail.com> <20130716233157.6f19ff5c@home.rlworkman.net> Message-ID: <51E8D55A.2020705@gmail.com> On 07/16/2013 09:31 PM, Robby Workman wrote: > On Mon, 15 Jul 2013 23:57:28 -0700 > King Beowulf wrote: > >> Well, the question I have, as a script maintainer, what will be the >> policy going forward? ..... > > > I think pprkut's reply earlier should clarify the misunderstanding > that I created here :/ > > Also, I'd like to point out that you had submitted all of these > nvidia-* builds correctly, and then *I* removed the dupe links > in *_x86_64 lines in the .info file. In summary, you did it > right - I screwed it up. Sorry :-) > > -RW > No worries. I should have looked at what Greg was patching and why (and the patches!) before I flew off the handle. Maybe overwork and sleep deprivation. Yeah, that's my story and I'm stickin' to it! ;-) I'm just glad we got them all posted finally, since I've had quite a few requests. Kudos to pprkut for a concise explanation and for injecting some sanity before we all started swinging flaming hammers. -Ed From C.J.Theunissen at differ.nl Tue Jul 23 18:35:26 2013 From: C.J.Theunissen at differ.nl (Kees Theunissen) Date: Tue, 23 Jul 2013 20:35:26 +0200 (CEST) Subject: [Slackbuilds-users] celt051 fails to build on Slackware64-14.0 with compat32 libs installed. Message-ID: Hi, Building celt051 failed on my Slackware64-14.0 system with AlienBob's compat32 packages installed. The last few lines from the build output: .... x86_64-slackware-linux-gcc -O2 -fPIC -fvisibility=hidden -W -Wstrict-prototypes -Wall -Wextra -Wcast-align -Wnested-externs -Wshadow -Wno-parentheses -Wno-unused-parameter -Wno-sign-compare -o .libs/celtenc051 celtenc.o wav_io.o skeleton.o ../libcelt/.libs/libcelt051.so -L/usr/lib /usr/lib/libogg.so -lm -Wl,--rpath -Wl,/usr/lib64 /usr/lib/libogg.so: could not read symbols: File in wrong format collect2: error: ld returned 1 exit status make[2]: *** [celtenc051] Error 1 make[2]: Leaving directory `/tmp/SBo/celt-0.5.1.3/tools' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/SBo/celt-0.5.1.3' make: *** [all] Error 2 Note that /usr/lib/libogg.so is a 32-bits lib installed from the libogg-compat32-1.3.0-x86_64-1compat32 package. Adding "--with-ogg-libraries=/usr/lib${LIBDIRSUFFIX}" to the ./configure command solved the problem but IMHO the already present "--libdir=/usr/lib${LIBDIRSUFFIX}" should have been sufficient to build properly. Anyway, the patch below worked and looks innocent. Not tested on other systems though. --- celt051.SlackBuild 2012-09-29 06:34:37.000000000 +0200 +++ celt051.SlackBuild.sbopkg 2013-07-23 14:25:00.669176128 +0200 @@ -74,6 +74,7 @@ ./configure \ --prefix=/usr \ --libdir=/usr/lib${LIBDIRSUFFIX} \ + --with-ogg-libraries=/usr/lib${LIBDIRSUFFIX} \ --sysconfdir=/etc \ --localstatedir=/var \ --mandir=/usr/man \ Regards, Kees Theunissen. -- Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724 Dutch Institute For Fundamental Energy Research (DIFFER) e-mail address: C.J.Theunissen at differ.nl postal address: PO Box 1207, 3430 BE Nieuwegein, NL visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL From nickblizzard1776 at gmail.com Tue Jul 23 19:10:10 2013 From: nickblizzard1776 at gmail.com (Nick Blizzard) Date: Tue, 23 Jul 2013 15:10:10 -0400 Subject: [Slackbuilds-users] celt051 fails to build on Slackware64-14.0 with compat32 libs installed. In-Reply-To: References: Message-ID: See point #18 from this page to fix the slackbuild script for multilib. http://slackbuilds.org/faq/#multilib On Tue, Jul 23, 2013 at 2:35 PM, Kees Theunissen wrote: > Hi, > > Building celt051 failed on my Slackware64-14.0 system with AlienBob's > compat32 packages installed. > > The last few lines from the build output: > > .... > x86_64-slackware-linux-gcc -O2 -fPIC -fvisibility=hidden -W > -Wstrict-prototypes -Wall -Wextra -Wcast-align -Wnested-externs -Wshadow > -Wno-parentheses -Wno-unused-parameter -Wno-sign-compare -o > .libs/celtenc051 celtenc.o wav_io.o skeleton.o > ../libcelt/.libs/libcelt051.so -L/usr/lib /usr/lib/libogg.so -lm > -Wl,--rpath -Wl,/usr/lib64 > /usr/lib/libogg.so: could not read symbols: File in wrong format > collect2: error: ld returned 1 exit status > make[2]: *** [celtenc051] Error 1 > make[2]: Leaving directory `/tmp/SBo/celt-0.5.1.3/tools' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/tmp/SBo/celt-0.5.1.3' > make: *** [all] Error 2 > > > Note that /usr/lib/libogg.so is a 32-bits lib installed from the > libogg-compat32-1.3.0-x86_64-1compat32 package. > Adding "--with-ogg-libraries=/usr/lib${LIBDIRSUFFIX}" to the > ./configure command solved the problem but IMHO the already present > "--libdir=/usr/lib${LIBDIRSUFFIX}" should have been sufficient to > build properly. > Anyway, the patch below worked and looks innocent. Not tested on > other systems though. > > > > --- celt051.SlackBuild 2012-09-29 06:34:37.000000000 +0200 > +++ celt051.SlackBuild.sbopkg 2013-07-23 14:25:00.669176128 +0200 > @@ -74,6 +74,7 @@ > ./configure \ > --prefix=/usr \ > --libdir=/usr/lib${LIBDIRSUFFIX} \ > + --with-ogg-libraries=/usr/lib${LIBDIRSUFFIX} \ > --sysconfdir=/etc \ > --localstatedir=/var \ > --mandir=/usr/man \ > > > > Regards, > > Kees Theunissen. > > -- > Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724 > Dutch Institute For Fundamental Energy Research (DIFFER) > e-mail address: C.J.Theunissen at differ.nl > postal address: PO Box 1207, 3430 BE Nieuwegein, NL > visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL > > _______________________________________________ > 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: From C.J.Theunissen at differ.nl Tue Jul 23 19:31:38 2013 From: C.J.Theunissen at differ.nl (Kees Theunissen) Date: Tue, 23 Jul 2013 21:31:38 +0200 (CEST) Subject: [Slackbuilds-users] celt051 fails to build on Slackware64-14.0 with compat32 libs installed. In-Reply-To: References: Message-ID: On Tue, 23 Jul 2013, Nick Blizzard wrote: >See point #18 from this page to fix the slackbuild script for multilib. > >http://slackbuilds.org/faq/#multilib Thanks, That did the job. Regards, Kees Theunissen. -- Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724 Dutch Institute For Fundamental Energy Research (DIFFER) e-mail address: C.J.Theunissen at differ.nl postal address: PO Box 1207, 3430 BE Nieuwegein, NL visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL From kristofru at gmail.com Wed Jul 24 18:39:26 2013 From: kristofru at gmail.com (Chris Abela) Date: Wed, 24 Jul 2013 20:39:26 +0200 Subject: [Slackbuilds-users] Termination notice for maintenance for openproj - Use ProjectLibre instead Message-ID: <51F01F5E.5090304@gmail.com> I am not maintaining openproj anymore. I am not using it as it has been abandoned since 2008 and now it does not compile on my Slack64-current. I use ProjectLibre instead - it is similar but better maintained. From chaos.proton at gmail.com Thu Jul 25 01:40:28 2013 From: chaos.proton at gmail.com (Grissiom) Date: Thu, 25 Jul 2013 09:40:28 +0800 Subject: [Slackbuilds-users] SBo pyside upgrade In-Reply-To: References: Message-ID: Hi all, As someone has noticed, the pyside packages are out of date and Chan is the first one come to tell me there should be an update. And I think Chan might be suitable for maintaining the scripts. So I would like to hand over the maintainer to him/her. The full conversion is attached below for reference. -- Cheers, Grissiom On Thu, Jul 25, 2013 at 12:43 AM, Kenneth Chan wrote: > Sure. I think I can handle it, although I'm a beginner in Python. > > So what's the hand over ritual? > > > On Tue, Jul 23, 2013 at 9:51 AM, Grissiom wrote: > >> Hi Chan, >> >> Thank you very much for using and improving that scripts. I'm no longer >> use these packages anymore and would you take maintainership of those? >> >> If all things are done, you can submit them in >> http://slackbuilds.org/guidelines/ and tell the admin the exchange of >> the maintainers. >> >> Thank you very much again. >> >> -- >> Cheers, >> Grissiom >> >> On Sun, Jul 21, 2013 at 10:03 PM, Kenneth Chan wrote: >> >>> Hi there. >>> >>> Recently I tried to install with sbopkg these packages: >>> >>> shiboken >>> pyside >>> pyside-tools. >>> >>> Since you're the maintainer of the packages I'd like to tell you that >>> the current build scripts no longer build the packages. I have updated the >>> .SlackBuild and .info scripts with the new links of the latest stable >>> version. >>> >>> I'm wondering what's the procedure to submit them to SBo. >>> >>> >>> Regards, >>> >>> Ken >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdhalstead at att.net Mon Jul 29 14:27:19 2013 From: mdhalstead at att.net (Mark Halstead) Date: Mon, 29 Jul 2013 10:27:19 -0400 Subject: [Slackbuilds-users] Clementine build failed on CURRENT x86_64 Message-ID: <51F67BC7.4030300@att.net> Hi Folks, The last couple of updates broke Clementine for me. Seems to be a "warning treated as error" thing, but the fix seems simple. At line 286 of src/main.cpp g_type_init is deprecated and according to documentation no longer does anything. // This makes us show up nicely in gnome-volume-control g_type_init(); /* THIS LINE 286 */ g_set_application_name(QCoreApplication::applicationName().toLocal8Bit()); I commented it out and the build went smoothly. Based on the Gnome go-object documentation, I think this line can safely be removed. Thanks, Mark Halstead From willysr at gmail.com Mon Jul 29 14:32:11 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Mon, 29 Jul 2013 21:32:11 +0700 Subject: [Slackbuilds-users] Clementine build failed on CURRENT x86_64 In-Reply-To: <51F67BC7.4030300@att.net> References: <51F67BC7.4030300@att.net> Message-ID: > The last couple of updates broke Clementine for me. Seems to be a "warning > treated as error" thing, but the fix seems simple. At line 286 of > src/main.cpp g_type_init is deprecated and according to documentation no > longer does anything. > > // This makes us show up nicely in gnome-volume-control > g_type_init(); /* THIS LINE 286 */ > g_set_application_name(QCoreApplication::applicationName().toLocal8Bit()); > > I commented it out and the build went smoothly. Based on the Gnome go-object > documentation, I think this line can safely be removed. Will it broke users using Slackware 14.0? -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From mdhalstead at att.net Mon Jul 29 14:50:10 2013 From: mdhalstead at att.net (Mark Halstead) Date: Mon, 29 Jul 2013 10:50:10 -0400 Subject: [Slackbuilds-users] Clementine build failed on CURRENT x86_64 In-Reply-To: References: <51F67BC7.4030300@att.net> Message-ID: <51F68122.6020206@att.net> I only track CURRENT so not sure. I suspect that it will build ok, but perhaps do something bad to "gnome-volume-control" for those that might use it. GLib-2.36 is the culprit. Perhaps someone who runs 14.0 could try it? Mark H. On 07/29/2013 10:32 AM, Willy Sudiarto Raharjo wrote: >> The last couple of updates broke Clementine for me. Seems to be a "warning >> treated as error" thing, but the fix seems simple. At line 286 of >> src/main.cpp g_type_init is deprecated and according to documentation no >> longer does anything. >> >> // This makes us show up nicely in gnome-volume-control >> g_type_init(); /* THIS LINE 286 */ >> g_set_application_name(QCoreApplication::applicationName().toLocal8Bit()); >> >> I commented it out and the build went smoothly. Based on the Gnome go-object >> documentation, I think this line can safely be removed. > Will it broke users using Slackware 14.0? > From dave at dawoodfall.net Mon Jul 29 17:34:57 2013 From: dave at dawoodfall.net (David Woodfall) Date: Mon, 29 Jul 2013 18:34:57 +0100 Subject: [Slackbuilds-users] Clementine build failed on CURRENT x86_64 In-Reply-To: <51F68122.6020206@att.net> References: <51F67BC7.4030300@att.net> <51F68122.6020206@att.net> Message-ID: <20130729173457.GC24462@Blackswan> On (29/07/13 10:50), Mark Halstead put forth the proposition: >I only track CURRENT so not sure. I suspect that it will build ok, but >perhaps do something bad to "gnome-volume-control" for those that >might use it. GLib-2.36 is the culprit. Perhaps someone who runs 14.0 >could try it? > >Mark H. Yes it does build on 14.0. It is designed to build on the repo branch that is chosen when searching on slackbuilds.org. I do not support building it on -current as it would be a nightmare to keep up with all the changes. You may notice that on the slackbuilds.org website there is no option in the drop-down box for -current, so whether it builds or not in -current is irrelevant. Anyway, thanks for bringing this to my attention. If needed, the fix will be put into the 14.1 version when it is released. Regards D. >On 07/29/2013 10:32 AM, Willy Sudiarto Raharjo wrote: >>>The last couple of updates broke Clementine for me. Seems to be a "warning >>>treated as error" thing, but the fix seems simple. At line 286 of >>>src/main.cpp g_type_init is deprecated and according to documentation no >>>longer does anything. >>> >>> // This makes us show up nicely in gnome-volume-control >>> g_type_init(); /* THIS LINE 286 */ >>>g_set_application_name(QCoreApplication::applicationName().toLocal8Bit()); >>> >>>I commented it out and the build went smoothly. Based on the Gnome go-object >>>documentation, I think this line can safely be removed. >>Will it broke users using Slackware 14.0? >> > >_______________________________________________ >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 mancha1 at hush.com Mon Jul 29 18:26:43 2013 From: mancha1 at hush.com (mancha) Date: Mon, 29 Jul 2013 14:26:43 -0400 Subject: [Slackbuilds-users] Clementine build failed on CURRENT x86_64 Message-ID: <20130729182643.82CD0600D2@smtp.hushmail.com> On Mon, 29 Jul 2013 13:35:37 -0400 "David Woodfall" wrote: >Yes it does build on 14.0. It is designed to build on the repo branch >that is chosen when searching on slackbuilds.org. I believe Willy was curious if the *change* that allows it to build on -current breaks building it on 14.0. The reason he asked that is obvious. --mancha From mdhalstead at att.net Mon Jul 29 18:47:09 2013 From: mdhalstead at att.net (Mark Halstead) Date: Mon, 29 Jul 2013 14:47:09 -0400 Subject: [Slackbuilds-users] Clementine build failed on CURRENT x86_64 In-Reply-To: <20130729173457.GC24462@Blackswan> References: <51F67BC7.4030300@att.net> <51F68122.6020206@att.net> <20130729173457.GC24462@Blackswan> Message-ID: <51F6B8AD.6090907@att.net> I hardly expect you to maintain for CURRENT. This was just a heads-up for next go-round. I can make it work for myself. Thanks for paying attention and maintaining an excellent piece of software. Mark H. On 07/29/2013 01:34 PM, David Woodfall wrote: > On (29/07/13 10:50), Mark Halstead put forth the > proposition: >> I only track CURRENT so not sure. I suspect that it will build ok, >> but perhaps do something bad to "gnome-volume-control" for those that >> might use it. GLib-2.36 is the culprit. Perhaps someone who runs 14.0 >> could try it? >> >> Mark H. > > Yes it does build on 14.0. It is designed to build on the repo branch > that is chosen when searching on slackbuilds.org. > > I do not support building it on -current as it would be a > nightmare to keep up with all the changes. > > You may notice that on the slackbuilds.org website there is no option > in the drop-down box for -current, so whether it builds or not in > -current is irrelevant. > > Anyway, thanks for bringing this to my attention. If needed, the fix > will be put into the 14.1 version when it is released. > > Regards > > D. > >> On 07/29/2013 10:32 AM, Willy Sudiarto Raharjo wrote: >>>> The last couple of updates broke Clementine for me. Seems to be a >>>> "warning >>>> treated as error" thing, but the fix seems simple. At line 286 of >>>> src/main.cpp g_type_init is deprecated and according to >>>> documentation no >>>> longer does anything. >>>> >>>> // This makes us show up nicely in gnome-volume-control >>>> g_type_init(); /* THIS LINE 286 */ >>>> g_set_application_name(QCoreApplication::applicationName().toLocal8Bit()); >>>> >>>> >>>> I commented it out and the build went smoothly. Based on the Gnome >>>> go-object >>>> documentation, I think this line can safely be removed. >>> Will it broke users using Slackware 14.0? >>> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From dave at dawoodfall.net Mon Jul 29 21:23:55 2013 From: dave at dawoodfall.net (David Woodfall) Date: Mon, 29 Jul 2013 22:23:55 +0100 Subject: [Slackbuilds-users] Clementine build failed on CURRENT x86_64 In-Reply-To: <51F6B8AD.6090907@att.net> References: <51F67BC7.4030300@att.net> <51F68122.6020206@att.net> <20130729173457.GC24462@Blackswan> <51F6B8AD.6090907@att.net> Message-ID: <20130729212355.GE24462@Blackswan> On (29/07/13 14:47), Mark Halstead put forth the proposition: >I hardly expect you to maintain for CURRENT. This was just a heads-up >for next go-round. I can make it work for myself. Thanks for paying >attention and maintaining an excellent piece of software. > >Mark H. > >On 07/29/2013 01:34 PM, David Woodfall wrote: >>On (29/07/13 10:50), Mark Halstead put forth >>the proposition: >>>I only track CURRENT so not sure. I suspect that it will build ok, >>>but perhaps do something bad to "gnome-volume-control" for those >>>that might use it. GLib-2.36 is the culprit. Perhaps someone who >>>runs 14.0 could try it? >>> >>>Mark H. >> >>Yes it does build on 14.0. It is designed to build on the repo branch >>that is chosen when searching on slackbuilds.org. >> >>I do not support building it on -current as it would be a >>nightmare to keep up with all the changes. >> >>You may notice that on the slackbuilds.org website there is no option >>in the drop-down box for -current, so whether it builds or not in >>-current is irrelevant. >> >>Anyway, thanks for bringing this to my attention. If needed, the fix >>will be put into the 14.1 version when it is released. >> >>Regards >> >>D. >> >>>On 07/29/2013 10:32 AM, Willy Sudiarto Raharjo wrote: >>>>>The last couple of updates broke Clementine for me. Seems to >>>>>be a "warning >>>>>treated as error" thing, but the fix seems simple. At line 286 of >>>>>src/main.cpp g_type_init is deprecated and according to >>>>>documentation no >>>>>longer does anything. >>>>> >>>>> // This makes us show up nicely in gnome-volume-control >>>>> g_type_init(); /* THIS LINE 286 */ >>>>>g_set_application_name(QCoreApplication::applicationName().toLocal8Bit()); >>>>> >>>>> >>>>>I commented it out and the build went smoothly. Based on the >>>>>Gnome go-object >>>>>documentation, I think this line can safely be removed. >>>>Will it broke users using Slackware 14.0? I can confirm that it does build and run on 14.0 with the patch I made from OP's info. I can't tell if it works any better with gnome-volume-control (or at all). That particular app seems to be part of the much larger gnome control center, which I don't feel inclined to build at the moment. If anyone does want to test though I've attached the patch. Just needs patch -p1 --verbose < $CWD/gnome-vol.patch before 'mkdir build' in the slackbuild. D. -------------- next part -------------- diff -Naur a/src/main.cpp b/src/main.cpp --- a/src/main.cpp 2012-11-18 08:51:27.000000000 +0000 +++ b/src/main.cpp 2013-07-29 21:59:53.149781604 +0100 @@ -265,7 +265,7 @@ #endif // This makes us show up nicely in gnome-volume-control - g_type_init(); + //g_type_init(); g_set_application_name(QCoreApplication::applicationName().toLocal8Bit()); RegisterMetaTypes(); From unix_lists at f-m.fm Tue Jul 30 04:01:45 2013 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Mon, 29 Jul 2013 23:01:45 -0500 Subject: [Slackbuilds-users] take maintenance of sparkleshare References: <51F6260D.1040005@gmail.com> Message-ID: <1375156905.14534.3093959.049BC8EC@webmail.messagingengine.com> ----- Original message ----- From: Pierre Cazenave To: dfc at warpmail.net Subject: Re: diffs to update sparkleshare to 1.1.0 Date: Mon, 29 Jul 2013 09:21:33 +0100 On 25/07/13 06:37, dfc at warpmail.net wrote: > Hi, > Here are a couple of diffs to update your slackbuild of sparkleshare to > latest stable release. > N.B. apparently the disable nautilus config option is no longer > supported so that's why I removed it in my diff. > Lightly test on x86_64. > -- > Regards, > Donald Cooley > Hi Donald, I'm afraid I no longer use Slackware, so you're welcome to take over maintenance of the SlackBuild if you want. Pierre I'd like to takeover the sparkleshare slackbuild if there are no objections. Regards, Donald Cooley From info at microlinux.fr Tue Jul 30 08:52:53 2013 From: info at microlinux.fr (Niki Kovacs) Date: Tue, 30 Jul 2013 10:52:53 +0200 Subject: [Slackbuilds-users] Apache Open Office 4.0 Message-ID: <51F77EE5.7080901@microlinux.fr> Hi, I've built some packages for Apache Open Office 4.0. The app itself is running fine on both 32-bit and 64-bit Slackware. I'm having trouble with the language packs though. I've published a little article on my blog here: http://www.kikinovak.net/index.php?post/2013/07/30/Apache-Open-Office-4.0-packages-for-Slackware As soon as I can find the bug in the language packages, I plan to submit these to SlackBuilds.org. Any suggestion is appreciated. 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