From dragonwisard at gmail.com Mon Nov 1 07:50:14 2010 From: dragonwisard at gmail.com (Ben Mendis) Date: Mon, 1 Nov 2010 03:50:14 -0400 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: <4CCD7A1E.6080808@gmail.com> References: <201010300900.11587.xgizzmo@slackbuilds.org> <20101030175015.GA29425@devbox> <4CCD7A1E.6080808@gmail.com> Message-ID: On Sun, Oct 31, 2010 at 10:15 AM, B Kirkpatrick wrote: > I do not want to start a flame war here, but I would like an explanation of > why the large majority of Slackware users, those who have & use bash, have > to write ash-compliant scripts for those who are using that shell. I know > that it has been done that way forever, I know that ash is run during > install, I know that it is run in BusyBox, but when the system is installed, > why can't I write any bash-compliant code & not get "bashed" by other users? > Regards, > Bill > > My personal feeling has always been that if the script begins with #!/bin/sh then it should be written to work with _any_ Bourne-compatible shell. If you want/need to use features specific to a particular implementation such as Bash or Ksh, then state that explicitly in your shebang. If you're unsure, put #!/bin/bash or whatever shell you tested in. Demanding to use Bash-specific features in Bourne shell is like demanding a garbage collector in C. -------------- next part -------------- An HTML attachment was scrubbed... URL: From eha at alienbase.nl Mon Nov 1 11:24:07 2010 From: eha at alienbase.nl (Eric Hameleers) Date: Mon, 1 Nov 2010 12:24:07 +0100 (CET) Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: <201010300900.11587.xgizzmo@slackbuilds.org> <20101030175015.GA29425@devbox> <4CCD7A1E.6080808@gmail.com> Message-ID: On Mon, 1 Nov 2010, Ben Mendis wrote: > On Sun, Oct 31, 2010 at 10:15 AM, B Kirkpatrick wrote: > >> I do not want to start a flame war here, but I would like an explanation of >> why the large majority of Slackware users, those who have & use bash, have >> to write ash-compliant scripts for those who are using that shell. I know >> that it has been done that way forever, I know that ash is run during >> install, I know that it is run in BusyBox, but when the system is installed, >> why can't I write any bash-compliant code & not get "bashed" by other users? >> Regards, >> Bill >> >> > My personal feeling has always been that if the script begins with #!/bin/sh > then it should be written to work with _any_ Bourne-compatible shell. If you > want/need to use features specific to a particular implementation such as > Bash or Ksh, then state that explicitly in your shebang. If you're unsure, > put #!/bin/bash or whatever shell you tested in. > > Demanding to use Bash-specific features in Bourne shell is like demanding a > garbage collector in C. The SlackBuild scripts hosted by http://slackbuilds.org have to be executed by the root user. Slackware assumes that the root user uses the bash shell. I agree though that /bin/sh can point to any shell the local computer administrator likes best. So, bashisms should be kept to a minimum in SlackBuild scripts, and if anything is used that works only with bash, the shebang line should read "#!/bin/bash" explicitly. However! I do not want a "bash test" to be mandatory for the SlackBuild maintainer. Rather, I would like to leave it to the users of the script to report incompatibilities. If any user of a script finds that the script actually requires bash, he or she can communicate this to the maintainer who can then update the SlackBuild with an explicit "#!/bin/bash" line. Note that this is my personal opinion, not discussed with the other admins. Cheers, Eric -- Eric Hameleers Email: alien at slackware.com Jabber: alien at jabber.xs4all.nl Gpg fingerprint: F2CE 1B92 EE1F 2C0C E97E 581E 5E56 AAAF A75C BDA0 The two basic principles of Windows system administration: * For minor problems, reboot * For major problems, reinstall From bailey at akamai.com Mon Nov 1 11:37:53 2010 From: bailey at akamai.com (R. Andrew Bailey) Date: Mon, 1 Nov 2010 07:37:53 -0400 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: Message-ID: <20101101113753.GS12118@akamai.com> On 30/10/10 06:28 -0400, Max Miorim wrote: >Hello folks, > >Recently I have been tinkering with one of my boxes to use ash as ... Don't you think its a lot easier for you to remember to exec these scripts with bash, than to get everybody else to change their scripts to work with your symlink? :) .andy >Regards, > >Max >_______________________________________________ >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 baildon.research at googlemail.com Mon Nov 1 12:00:17 2010 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 1 Nov 2010 12:00:17 +0000 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: <20101101113753.GS12118@akamai.com> References: <20101101113753.GS12118@akamai.com> Message-ID: > ?Don't you think its a lot easier for you to remember to exec these > ?scripts with bash, than to get everybody else to change their scripts > ?to work with your symlink? :) Technical measures are always better than "remembering". That's what "#!/bin/bash" is for. What follows is just a personal opinion. I try to write my scripts to the highest standards. If I start with #!/bin/sh, and then I write a bashism, then #!/bin/sh was a lie, and when someone points that out, I am embarassed and grateful, especially when the fix is really, really easy. I'm not "everybody", but then, not everybody's script starts with a lie. Just three of mine :-/ -D. From bailey at akamai.com Mon Nov 1 12:27:21 2010 From: bailey at akamai.com (R. Andrew Bailey) Date: Mon, 1 Nov 2010 08:27:21 -0400 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: <20101101113753.GS12118@akamai.com> Message-ID: <20101101122721.GA2971@akamai.com> On 01/11/10 08:00 -0400, David Spencer wrote: >> ?Don't you think its a lot easier for you to remember to exec these >> ?scripts with bash, than to get everybody else to change their scripts >> ?to work with your symlink? :) > >Technical measures are always better than "remembering". That's what >"#!/bin/bash" is for. > >What follows is just a personal opinion. I try to write my scripts to >the highest standards. If I start with #!/bin/sh, and then I write a >bashism, then #!/bin/sh was a lie, and when someone points that out, I >am embarassed and grateful, especially when the fix is really, really >easy. I'm not "everybody", but then, not everybody's script starts >with a lie. Just three of mine :-/ So changing the shbang lines to read #!/bin/bash would suffice, no? .andy > >-D. >_______________________________________________ >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 baildon.research at googlemail.com Mon Nov 1 13:04:32 2010 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 1 Nov 2010 13:04:32 +0000 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: <20101101122721.GA2971@akamai.com> References: <20101101113753.GS12118@akamai.com> <20101101122721.GA2971@akamai.com> Message-ID: > So changing the shbang lines to read #!/bin/bash would suffice, no? Yes. That's what pretty much everyone has been saying since the start of this discussion. Which is ok, really; it helps keep the mailing list ticking over. -D. From kingbeowulf at gmail.com Mon Nov 1 13:07:28 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 1 Nov 2010 06:07:28 -0700 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: <20101101122721.GA2971@akamai.com> References: <20101101113753.GS12118@akamai.com> <20101101122721.GA2971@akamai.com> Message-ID: I would say so. My 2 cents: SBo hosts packages for Slackware. Slackware default shell is bash. Slackbuild scripts should be bash compliant. Anything else is an exercise for the end user (eg dependency resolution etc). Personally, I have a hard enough time keeping up with bash; I have no interest in the globs of other shells out there. -Ed On 11/1/10, R. Andrew Bailey wrote: > On 01/11/10 08:00 -0400, David Spencer wrote: >>> ?Don't you think its a lot easier for you to remember to exec these >>> ?scripts with bash, than to get everybody else to change their scripts >>> ?to work with your symlink? :) >> >>Technical measures are always better than "remembering". That's what >>"#!/bin/bash" is for. >> >>What follows is just a personal opinion. I try to write my scripts to >>the highest standards. If I start with #!/bin/sh, and then I write a >>bashism, then #!/bin/sh was a lie, and when someone points that out, I >>am embarassed and grateful, especially when the fix is really, really >>easy. I'm not "everybody", but then, not everybody's script starts >>with a lie. Just three of mine :-/ > > So changing the shbang lines to read #!/bin/bash would suffice, no? > > .andy > > >> >>-D. >>_______________________________________________ >>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/ > > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From mccnews at free.fr Mon Nov 1 14:27:51 2010 From: mccnews at free.fr (mc collilieux) Date: Mon, 01 Nov 2010 15:27:51 +0100 Subject: [Slackbuilds-users] help for tintii slackbuild Message-ID: <4CCECE67.9000500@free.fr> Hello, i am trying to make a slackbuild for tintii* 2.2.3 and i have (of course) some problems. minor questions: i have to add a tintii.desktop, I have seen this is not the first time a desktop file is added but is this correct ? +----------------------- [Desktop Entry] Name=tintii Categories=Graphics;RasterGraphics; Type=Application Terminal=false StartupNotify=true Exec=tintii TryExec=tintii Icon=tintii GenericName=Image Tinter Comment=Photo Editor for colour-select effects +---------------------------- I have also improvise a tintii.png but after a good night, it don't seem a good idea... major question: tintii is built with scons and the config.py contain this: +----------------------- # # Configuration file. # # Any values given in this file override the default build options on # your system, but are overriden by options given on the command # line. To use the default value for a particular option, simply # comment it out. Options may also be specified on the command line # when calling scons. # # To see the full list of options, type `scons -h`. # # Linux/g++ compiler options CXX='g++' #CXXFLAGS='-O3 -Wall -funroll-loops -fomit-frame-pointer `wx-config --cxxflags` -fopenmp -ffast-math' LINKFLAGS='`wx-config --libs` `wx-config --libs aui` -fopenmp' NDEBUG='yes' +-------------------------------------- it seems to me quite different of wich is in others slackbuilds and i don't know what is really important or not. Any idea ? Without `wx-config --cxxflags`, it don't compile. Thanks for help. +------------ * tintii takes full colour photos and processes them into black and white with some select regions highlighted in colour. http://www.indii.org/software/tintii requires wxGTK, (boost), scons, and libmspack The latest tintii needs wxwidgets 2.9.1 -- mcc From ozan.turkyilmaz at gmail.com Mon Nov 1 14:52:35 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Mon, 1 Nov 2010 16:52:35 +0200 Subject: [Slackbuilds-users] help for tintii slackbuild In-Reply-To: <4CCECE67.9000500@free.fr> References: <4CCECE67.9000500@free.fr> Message-ID: 2010/11/1 mc collilieux : > Hello, i am trying to make a slackbuild for tintii* 2.2.3 and i have (of > course) some problems. > > minor questions: > i have to add a tintii.desktop, I have seen this is not the first time a > desktop file is added but is this correct ? http://www.freedesktop.org/wiki/Howto_desktop_files start from there. IT looks okay to me, still check the howto. -- Ozan, BSc, BEng From willysr at gmail.com Mon Nov 1 15:21:08 2010 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Mon, 1 Nov 2010 22:21:08 +0700 Subject: [Slackbuilds-users] Invalid link on perl-Magick Message-ID: The source on http://slackbuilds.org/repository/13.1/libraries/perl-Magick/ is invalid the source has been upgraded to 6.59, but the SBo still link to 6.59 ftp://ftp.carnet.hr/mirrors/misc/imagemagick/perl/PerlMagick-6.59.tar.gz -- Willy Sudiarto Raharjo Registered Linux User : 336579 Web : http://www.informatix.or.id/willy Blog : http://willysr.blogspot.com http://slackblogs.blogspot.com From mccnews at free.fr Mon Nov 1 16:15:57 2010 From: mccnews at free.fr (mc collilieux) Date: Mon, 01 Nov 2010 17:15:57 +0100 Subject: [Slackbuilds-users] help for tintii slackbuild In-Reply-To: References: <4CCECE67.9000500@free.fr> Message-ID: <4CCEE7BD.80407@free.fr> Le 01/11/2010 15:52, Ozan T?rky?lmaz a ?crit : > 2010/11/1 mc collilieux: >> Hello, i am trying to make a slackbuild for tintii* 2.2.3 and i have (of >> course) some problems. >> >> minor questions: >> i have to add a tintii.desktop, I have seen this is not the first time a >> desktop file is added but is this correct ? > > http://www.freedesktop.org/wiki/Howto_desktop_files > start from there. IT looks okay to me, still check the howto. > You are right, I have remove "RasterGraphics" from Categories. others lines seem correct. Thanks. -- mcc From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Mon Nov 1 20:49:29 2010 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Mon, 01 Nov 2010 21:49:29 +0100 Subject: [Slackbuilds-users] numpy, scipy, sympy and matplotlib In-Reply-To: References: Message-ID: <4CCF27D9.8090800@skmail.ikp.physik.tu-darmstadt.de> Hello! I submitted the above mentioned slackbuilds with updated maintainer info and some small changes including a check for pytz from within the matplotlib script, such that, if pytz is missing, build/installation don't occur. pytz is now mentioned in the README as a dependency for matplotlib. Thanks go to Heinz Wiesinger who reported that matplotlib's setup.py automatically installs pytz if this is not already present. Best regards, Serban Udrea From t3slider at gmail.com Mon Nov 1 22:05:35 2010 From: t3slider at gmail.com (T3slider) Date: Mon, 1 Nov 2010 18:05:35 -0400 Subject: [Slackbuilds-users] Request to remove remind from pending Message-ID: <20101101220535.GA3591@KeithPC.phub.net.cable.rogers.com> I submitted a SlackBuild for remind yesterday. I am requesting that it be removed from pending since I have rewritten much of it to make it more user-friendly (the previous submission required direct editing of two configuration files, while the new one uses a variety of environment variables, making it easier for those using sbopkg, for example). Once removed I will resubmit my new SlackBuild which has already been completed. I apologize for any inconvenience this may have caused. -T3slider From dragonwisard at gmail.com Tue Nov 2 04:27:14 2010 From: dragonwisard at gmail.com (Ben Mendis) Date: Tue, 2 Nov 2010 00:27:14 -0400 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: <20101101113753.GS12118@akamai.com> <20101101122721.GA2971@akamai.com> Message-ID: On Mon, Nov 1, 2010 at 9:07 AM, King Beowulf wrote: > I would say so. > > My 2 cents: SBo hosts packages for Slackware. Slackware default shell > is bash. Slackbuild scripts should be bash compliant. Anything else > is an exercise for the end user (eg dependency resolution etc). > Yes, the *default* shell is Bash, however not the _only_ shell. Having a default does not, IMHO, excuse you from following the standard. It would be perfectly valid to say, "SBo expects a full Slackware Install. A full Slackware install includes /bin/bash. Therefore, all Slackbuild are allowed to begin with #!/bin/bash". And, in fact, I would prefer that they _do_ begin with /bin/bash if that was the only shell they were ever tested in. However, I don't consider it valid to say, "SBo expects a full Slackware Install. In the *default* install 'sh' is a symlink to 'bash'. Therefore, all Slackbuilds are allowed to assume 'sh' and 'bash are the same thing." You are at the same time acknowledging the existence of other shells (and the fact that there are mechanisms in place to properly handle a multi-shell environment) and dismissing that fact as unimportant because it would require you to type two extra characters each time you wrote a Slackbuild. Contrary to Mr. Beowulf, I think that, by default, we should comply with the standard and use #!/bin/bash for scripts that were written and tested with the assumption that they would be run in Bash. If someone wants to explicitly (rather than implicitly) run the script in a different shell, then we can leave THAT as an exercise to the individual user. Speaking practically, however, I don't expect this to be enforced. It would create a disproportionate burden on all maintainers and the SBo admins to have to test that the correct shell is declared in the shebang. However I think it would be reasonable to make a note of suggestion in the template or on the submission page that Slackbuilds (like all shell scripts) that specify 'sh' are expected to conform to pure Bourne Shell, and that it is perfectly acceptable to specify 'bash' for you script instead. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Nov 2 09:29:10 2010 From: yalhcru at gmail.com (B Watson) Date: Tue, 2 Nov 2010 05:29:10 -0400 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: <20101101113753.GS12118@akamai.com> <20101101122721.GA2971@akamai.com> Message-ID: On 11/2/10, Ben Mendis wrote: > it is perfectly acceptable to specify 'bash' for you script instead. It is? I'd always assumed that the "follow our templates whenever possible" rule meant the #!/bin/sh (from the template) is required... If it's allowed to say #!/bin/bash, I'll do that for all my future submissions. Maybe the admins could make a note of it on the submissions page, or even change the template to start with #!/bin/bash (is there any reason not to do this? My opinion is there's not, but I'm just a luser...) Am not advocating mass-updating existing slackbuilds to change the shebang line, mind. Just the template. Maybe with a comment saying "do not change to #!/bin/sh unless you've actually tested your script with at least ash and ksh"? Pretty much a separate (possibly off-topic) question here: why would anyone even care to use ash for /bin/sh on a build host? On an embedded system it makes sense, but on the dev box where you build its packages? From miorimmax at gmail.com Tue Nov 2 13:11:38 2010 From: miorimmax at gmail.com (Max Miorim) Date: Tue, 2 Nov 2010 11:11:38 -0200 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: <20101101113753.GS12118@akamai.com> <20101101122721.GA2971@akamai.com> Message-ID: On Tue, Nov 2, 2010 at 7:29 AM, B Watson wrote: > On 11/2/10, Ben Mendis wrote: >> it is perfectly acceptable to specify 'bash' for you script instead. > > It is? I'd always assumed that the "follow our templates whenever > possible" rule meant the #!/bin/sh (from the template) is required... If > it's allowed to say #!/bin/bash, I'll do that for all my future > submissions. Unless we're talking about using either /bin/bash or /bin/sh, the problem that I see with this is that it would open the precedence to accept submissions of scripts using other shells like csh and zsh, that could be a problem for the people that review the scripts, as they'd have to learn the particularities of other shells - it could slow down the process of review->approval considerably. > Maybe the admins could make a note of it on the submissions page, or > even change the template to start with #!/bin/bash (is there any reason > not to do this? My opinion is there's not, but I'm just a luser...) > > Am not advocating mass-updating existing slackbuilds to change the > shebang line, mind. Just the template. Maybe with a comment saying > "do not change to #!/bin/sh unless you've actually tested your script > with at least ash and ksh"? I like the idea of updating the template. A note saying "you should run these slackbuilds with bash" would be fine too. The current FAQ and HOWTO assumes that the user know that Slackware assumes that /bin/sh is a symlink to bash, that's a lot of assumptions if you ask me. :) > Pretty much a separate (possibly off-topic) question here: why would > anyone even care to use ash for /bin/sh on a build host? On an embedded > system it makes sense, but on the dev box where you build its packages? Why not? It doesn't matters if my /bin/sh is maxsownsh, bash or ash, the shebang denotes that the script is compatible with the bourne shell and, as long as my shell is compatible with it, it should run just fine. ;) My motivation to change the shell was because a co-worker, which uses Debian Sid, has the same hardware that I do and his notebook runs our sh-compatible scripts considerably faster than mine. We compared configurations/optimizations and did a quite exhaustive research on gnu.bash.bug looking for performance regressions. Then, I changed the shebang of these scripts to use /bin/ash and, mind you, the same thing that took 16.702 seconds using bash as /bin/sh took 6.803 with ash and pretty much the same happens to every script that we tested. As I can't change every shebang or run the scripts using "lightandfastsh script.sh", I did exactly what the others did in their respective computers: changed my /bin/sh to a shell other than bash. BTW, I don't have a "build host" - If the box that is building is slow or if I just need more processing power, I use distcc. From dragonwisard at gmail.com Tue Nov 2 13:31:46 2010 From: dragonwisard at gmail.com (Ben Mendis) Date: Tue, 2 Nov 2010 09:31:46 -0400 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: <20101101113753.GS12118@akamai.com> <20101101122721.GA2971@akamai.com> Message-ID: On Tue, Nov 2, 2010 at 5:29 AM, B Watson wrote: > > Pretty much a separate (possibly off-topic) question here: why would > anyone even care to use ash for /bin/sh on a build host? On an embedded > system it makes sense, but on the dev box where you build its packages? > A counter argument might be, why should we preclude the ability to build packages on the system where they are to be deployed? Slackware has an official ARM port now and while ARM is getting faster, you might still want to run with a lighter-weight shell to conserve memory or improve performance. I'm no authority on the matter, but my impression is that it's very "un-Slackware" to dictate that users must conform to an arbitrary default. Especially when that would violate the standard. As far as opening up submissions to other shells, I agree that could become an issue. Perl and Python are also in the default Slackware install but I don't wish to see SlackBuilds written in those languages on SBo. I'm not in a position to set policy but I would suggest that our benevolent admins accept either /bin/bash or /bin/sh, with the polite request that /bin/sh should be used _only_ if it has been tested in another Bourne-compliant shell like ash. I think that is reasonable. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Nov 2 19:30:30 2010 From: yalhcru at gmail.com (B Watson) Date: Tue, 2 Nov 2010 15:30:30 -0400 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: <20101101113753.GS12118@akamai.com> <20101101122721.GA2971@akamai.com> Message-ID: On 11/2/10, Max Miorim wrote: > Unless we're talking about using either /bin/bash or /bin/sh, the > problem that I see with this is that it would open the precedence to > accept submissions of scripts using other shells like csh and zsh, > that could be a problem for the people that review the scripts, as > they'd have to learn the particularities of other shells - it could > slow down the process of review->approval considerably. Yah, I hadn't thought about csh. Definitely agree the rule should be /bin/bash, or /bin/sh for scripts that were tested with ash. > the same thing that took 16.702 seconds using bash as /bin/sh took > 6.803 with ash and pretty much the same happens to every script that > we tested. Interesting. Never even occurred to me to test performance, I expect interpreters to be slow, and at least subconsciously I was aware that bash is bloated... but wouldn't have guessed ash would be *that* much faster. Hm. I just now thought I'd try a couple of things in ash, as an interactive shell, on slack64 13.1, and the damn thing segfaulted halfway through typing the first command. /me runs off to do some more testing... From joshuakwood at gmail.com Tue Nov 2 20:09:09 2010 From: joshuakwood at gmail.com (JK Wood) Date: Tue, 2 Nov 2010 15:09:09 -0500 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: <20101101113753.GS12118@akamai.com> <20101101122721.GA2971@akamai.com> Message-ID: On Tue, Nov 2, 2010 at 2:30 PM, B Watson wrote: > On 11/2/10, Max Miorim wrote: > > > Unless we're talking about using either /bin/bash or /bin/sh, the > > problem that I see with this is that it would open the precedence to > > accept submissions of scripts using other shells like csh and zsh, > > that could be a problem for the people that review the scripts, as > > they'd have to learn the particularities of other shells - it could > > slow down the process of review->approval considerably. > > Yah, I hadn't thought about csh. Definitely agree the rule should be > /bin/bash, or /bin/sh for scripts that were tested with ash. > > > the same thing that took 16.702 seconds using bash as /bin/sh took > > 6.803 with ash and pretty much the same happens to every script that > > we tested. > > Interesting. Never even occurred to me to test performance, I expect > interpreters to be slow, and at least subconsciously I was aware that bash > is bloated... but wouldn't have guessed ash would be *that* much faster. > > Hm. I just now thought I'd try a couple of things in ash, as an > interactive shell, on slack64 13.1, and the damn thing segfaulted halfway > through typing the first command. /me runs off to do some more testing... > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > Certainly Bash is slower. It supports a wider array of scripting options, after all. Remember the golden rule of software: You can have it fast, you can have it cheap, you can have it good. Pick two. (Note: Not saying ash is not good. It just doesn't compare feature-wise to Bash, which is also free...) --JK -------------- next part -------------- An HTML attachment was scrubbed... URL: From donaldcallen at gmail.com Tue Nov 2 20:15:27 2010 From: donaldcallen at gmail.com (Donald Allen) Date: Tue, 2 Nov 2010 16:15:27 -0400 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: <20101101113753.GS12118@akamai.com> <20101101122721.GA2971@akamai.com> Message-ID: On Tue, Nov 2, 2010 at 3:30 PM, B Watson wrote: > On 11/2/10, Max Miorim wrote: > > > Unless we're talking about using either /bin/bash or /bin/sh, the > > problem that I see with this is that it would open the precedence to > > accept submissions of scripts using other shells like csh and zsh, > > that could be a problem for the people that review the scripts, as > > they'd have to learn the particularities of other shells - it could > > slow down the process of review->approval considerably. > > Yah, I hadn't thought about csh. Definitely agree the rule should be > /bin/bash, or /bin/sh for scripts that were tested with ash. > > > the same thing that took 16.702 seconds using bash as /bin/sh took > > 6.803 with ash and pretty much the same happens to every script that > > we tested. > > Interesting. Never even occurred to me to test performance, I expect > interpreters to be slow, and at least subconsciously I was aware that bash > is bloated... but wouldn't have guessed ash would be *that* much faster. > > Hm. I just now thought I'd try a couple of things in ash, as an > interactive shell, on slack64 13.1, and the damn thing segfaulted halfway > through typing the first command. /me runs off to do some more testing... > Yes, but it was really fast until it blew up .... I've had the same experience in search of a less bloated browser than Firefox (really solid, reliable code of significant complexity is not so easy to come by). They all make sense, according to their developers, until you try to use them in real-life situations. > _______________________________________________ > 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 Manuel.Spam at nurfuerspam.de Tue Nov 2 20:14:53 2010 From: Manuel.Spam at nurfuerspam.de (Manuel Reimer) Date: Tue, 02 Nov 2010 21:14:53 +0100 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: Message-ID: Max Miorim wrote: > Recently I have been tinkering with one of my boxes to use ash as > /bin/sh and noticed that doing so some SlackBuilds aren't working as > intended anymore. Should fail. Slackware's init scripts also use bashism... For example /etc/rc.d/rc.inet1 uses arrays, which are not standardized. Some time ago, I planned to try how fast Slackware would boot up with a faster shell, but failed with those scripts. Yours Manuel From andrew.antle at gmail.com Thu Nov 4 14:30:10 2010 From: andrew.antle at gmail.com (Andrew Antle) Date: Thu, 4 Nov 2010 10:30:10 -0400 Subject: [Slackbuilds-users] gprolog README typo fixes Message-ID: A few minor typo fixes. Diff attached: --- README.orig 2010-11-04 10:20:04.412448942 -0400 +++ README 2010-11-04 10:20:30.663595260 -0400 @@ -1,10 +1,9 @@ -The gprolog configure script appears to ignore the execc-prefix +The gprolog configure script appears to ignore the exec-prefix information handed to it which indicates where compiled binaries should be installed. It insists on installing everything into /usr/gprolog-$VERSION/ and then creating symlinks in /usr/bin. This script will correct this by moving the files in -/usr/gprolog-$VERSION to their propper places in /usr, +/usr/gprolog-$VERSION to their proper places in /usr, ie: binaries are placed in /usr/bin, libraries in /usr/lib or /usr/lib64 and documentation in /usr/doc/gprolog-$VERSION. - -- Andrew Antle -------------- next part -------------- --- README.orig 2010-11-04 10:20:04.412448942 -0400 +++ README 2010-11-04 10:20:30.663595260 -0400 @@ -1,10 +1,9 @@ -The gprolog configure script appears to ignore the execc-prefix +The gprolog configure script appears to ignore the exec-prefix information handed to it which indicates where compiled binaries should be installed. It insists on installing everything into /usr/gprolog-$VERSION/ and then creating symlinks in /usr/bin. This script will correct this by moving the files in -/usr/gprolog-$VERSION to their propper places in /usr, +/usr/gprolog-$VERSION to their proper places in /usr, ie: binaries are placed in /usr/bin, libraries in /usr/lib or /usr/lib64 and documentation in /usr/doc/gprolog-$VERSION. - From andrew.antle at gmail.com Thu Nov 4 15:06:32 2010 From: andrew.antle at gmail.com (Andrew Antle) Date: Thu, 4 Nov 2010 11:06:32 -0400 Subject: [Slackbuilds-users] gprolog build error Message-ID: This is pretty long. I apologize in advance. make[1]: Entering directory `/tmp/SBo/gprolog-1.3.1/src/Fd2C' gplc -c --fast-math fd2c.pl fd2c.pl:215-220: fatal error: exception raised: error(instantiation_error,sort/2) compilation failed make[1]: *** [fd2c.o] Error 1 make[1]: Leaving directory `/tmp/SBo/gprolog-1.3.1/src/Fd2C' make: *** [all] Error 1 Seems to ignore $CFLAGS: ------------------------------- --- GNU PROLOG INSTALLATION --- ------------------------------- GNU Prolog version: 1.3.1 (Feb 10 2009) Operating system : linux-gnu Processor : i486 Size of a word : 32 bits C compiler : gcc C flags : -O3 -fomit-frame-pointer C flags machine : -march=i486 Loader flags : Loader libraries : -lm Use line editor : Yes Use piped consult : Yes Use sockets : Yes Use FD solver : Yes Use fast call : Yes Use machine regs. : Yes Working sigaction : Yes Used register(s) : ebx (TR) ------------------------------ So, I changed the SlackBuild to read: ./configure \ --prefix=/usr \ --build=$ARCH-slackware-linux \ --with-c-flags="$SLKCFLAGS" ------------------------------- --- GNU PROLOG INSTALLATION --- ------------------------------- GNU Prolog version: 1.3.1 (Feb 10 2009) Operating system : linux-gnu Processor : i486 Size of a word : 32 bits C compiler : gcc C flags : -O2 -march=i486 -mtune=i686 C flags machine : -march=i486 Loader flags : Loader libraries : -lm Use line editor : Yes Use piped consult : Yes Use sockets : Yes Use FD solver : Yes Use fast call : Yes Use machine regs. : Yes Working sigaction : Yes Used register(s) : ebx (TR) ------------------------------ But still: make[1]: Entering directory `/tmp/SBo/gprolog-1.3.1/src/Fd2C' gplc -c --fast-math fd2c.pl fd2c.pl:215-220: fatal error: exception raised: error(instantiation_error,sort/2) compilation failed make[1]: *** [fd2c.o] Error 1 make[1]: Leaving directory `/tmp/SBo/gprolog-1.3.1/src/Fd2C' make: *** [all] Error 1 So then, I downloaded the latest unstable version as suggested on the gprolog site: http://gprolog.univ-paris1.fr/unstable/gprolog-20100713.tgz and tried a vanilla ./configure and received: ------------------------------- --- GNU PROLOG INSTALLATION --- ------------------------------- GNU Prolog version: 1.4.0 (Jul 13 2010) Operating system : linux-gnu Processor : i686 Size of a word : 32 bits C compiler : gcc C flags : -O3 -fomit-frame-pointer C flags machine : -march=pentiumpro Loader flags : Loader libraries : -lm Use line editor : Yes Use piped consult : Yes Use sockets : Yes Use FD solver : Yes Working sigaction : Yes Use fast call : Yes Use machine regs. : Yes Used register(s) : ebx (TR) ------------------------------ So I tried disabling the fd solver: ./configure --disable-fd-solver ------------------------------- --- GNU PROLOG INSTALLATION --- ------------------------------- GNU Prolog version: 1.4.0 (Jul 13 2010) Operating system : linux-gnu Processor : i686 Size of a word : 32 bits C compiler : gcc C flags : -O3 -fomit-frame-pointer C flags machine : -march=pentiumpro Loader flags : Loader libraries : -lm Use line editor : Yes Use piped consult : Yes Use sockets : Yes Use FD solver : No Working sigaction : Yes Use fast call : Yes Use machine regs. : Yes Used register(s) : ebx (TR) ------------------------------ and it built successfully. The SlackBuild builds successfully as well. I'm not sure if this defeats the purpose though, as gprolog's tagline is "a free Prolog compiler with constraint solving over finite domains". Hope this helps, -- Andrew Antle From egregora at gmail.com Thu Nov 4 15:26:38 2010 From: egregora at gmail.com (luciano) Date: Thu, 4 Nov 2010 13:26:38 -0200 Subject: [Slackbuilds-users] Task link error Message-ID: Task doesn't build. The link seems wrong. It gives 404 message. From baildon.research at googlemail.com Fri Nov 5 21:32:58 2010 From: baildon.research at googlemail.com (David Spencer) Date: Fri, 5 Nov 2010 21:32:58 +0000 Subject: [Slackbuilds-users] Today's "please nuke from pending" request -- gdal Message-ID: Could one of our admin folks please nuke gdal from pending? It contains a howling error. I'll resubmit :-/ Thanks in advance -D. From baildon.research at googlemail.com Fri Nov 5 22:33:16 2010 From: baildon.research at googlemail.com (David Spencer) Date: Fri, 5 Nov 2010 22:33:16 +0000 Subject: [Slackbuilds-users] Today's second "please nuke from pending" request -- qgis Message-ID: AAAGH! Damn! Damn! Could one of you also please remove qgis? Sorry & thanks again -D. From rshepard at appl-ecosys.com Fri Nov 5 22:39:33 2010 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 5 Nov 2010 15:39:33 -0700 (PDT) Subject: [Slackbuilds-users] New R Version Released In-Reply-To: References: Message-ID: The version of R is out of date; R-2.12.0 has been released. I tried to send a mail message directly to Joel, but the gmail address in the R description bounced. Rich From erik at slackbuilds.org Fri Nov 5 22:41:11 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 5 Nov 2010 17:41:11 -0500 Subject: [Slackbuilds-users] Today's "please nuke from pending" request -- gdal In-Reply-To: References: Message-ID: <20101105174111.312752f9@shaggy.doo> On Fri, 5 Nov 2010 21:32:58 +0000 David Spencer wrote: > Could one of our admin folks please nuke gdal from pending? It > contains a howling error. I'll resubmit :-/ gdal and qgis have been removed. -- 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 binhnguyen at fastmail.fm Sat Nov 6 06:28:16 2010 From: binhnguyen at fastmail.fm (Binh Nguyen) Date: Sat, 6 Nov 2010 13:28:16 +0700 Subject: [Slackbuilds-users] Sonata lyric fetching failed Message-ID: <20101106132816.5f41c5f4@darkstar.example.net> I just noticed that sonata didn't fetch lyrics anymore. So I looked around and found that it uses lyricwiki.org for the purpose. And since the lyric site has been moved to lyrics.wikia.com, it leads to non-functional lyric module. The file in source that bears lyric funtion is sonata/info.py. So while waiting for the sonata next version, a simple line can be added to sonata.SlackBuild (just before 'python setup.py install ... ') to solve this issue: sed -i "s#lyricwiki.org#lyrics.wikia.org#g" sonata/info.py Regards, -- Binh Nguyen From jens at tuxane.com Sat Nov 6 10:27:22 2010 From: jens at tuxane.com (TuxaneMedia) Date: Sat, 06 Nov 2010 11:27:22 +0100 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: <20101101113753.GS12118@akamai.com> <20101101122721.GA2971@akamai.com> Message-ID: <4CD52D8A.5070501@tuxane.com> I think slackbuilds should read #!/bin/bash (and not sh or ash) for maximum safety and compatility. It's a 2 minute job for everyone the alter the script to build with ash (if it would build with ash or any other) but it can't be the job of every maintainer to test building against all the different shells. Le 02.11.2010 21:15, Donald Allen a ?crit : > > > On Tue, Nov 2, 2010 at 3:30 PM, B Watson > wrote: > > On 11/2/10, Max Miorim > wrote: > > > Unless we're talking about using either /bin/bash or /bin/sh, the > > problem that I see with this is that it would open the precedence to > > accept submissions of scripts using other shells like csh and zsh, > > that could be a problem for the people that review the scripts, as > > they'd have to learn the particularities of other shells - it could > > slow down the process of review->approval considerably. > > Yah, I hadn't thought about csh. Definitely agree the rule should be > /bin/bash, or /bin/sh for scripts that were tested with ash. > > > the same thing that took 16.702 seconds using bash as /bin/sh took > > 6.803 with ash and pretty much the same happens to every script that > > we tested. > > Interesting. Never even occurred to me to test performance, I expect > interpreters to be slow, and at least subconsciously I was aware > that bash > is bloated... but wouldn't have guessed ash would be *that* much > faster. > > Hm. I just now thought I'd try a couple of things in ash, as an > interactive shell, on slack64 13.1, and the damn thing segfaulted > halfway > through typing the first command. /me runs off to do some more > testing... > > > Yes, but it was really fast until it blew up .... > > I've had the same experience in search of a less bloated browser than > Firefox (really solid, reliable code of significant complexity is not > so easy to come by). They all make sense, according to their > developers, until you try to use them in real-life situations. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pprkut at slackbuilds.org Sat Nov 6 15:37:56 2010 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Sat, 6 Nov 2010 16:37:56 +0100 Subject: [Slackbuilds-users] Task link error In-Reply-To: References: Message-ID: <201011061637.56498.pprkut@slackbuilds.org> On Thursday 04 November 2010 16:26:38 luciano wrote: > Task doesn't build. The link seems wrong. It gives 404 message. Thanks for the report! I fixed this in my branch, it should be part of the next push of updates. Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From pprkut at slackbuilds.org Sat Nov 6 15:38:51 2010 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Sat, 6 Nov 2010 16:38:51 +0100 Subject: [Slackbuilds-users] gprolog README typo fixes In-Reply-To: References: Message-ID: <201011061638.52190.pprkut@slackbuilds.org> On Thursday 04 November 2010 15:30:10 Andrew Antle wrote: > A few minor typo fixes. Diff attached: > > --- README.orig 2010-11-04 10:20:04.412448942 -0400 > +++ README 2010-11-04 10:20:30.663595260 -0400 > @@ -1,10 +1,9 @@ > -The gprolog configure script appears to ignore the execc-prefix > +The gprolog configure script appears to ignore the exec-prefix > information handed to it which indicates where compiled binaries > should be installed. It insists on installing everything into > /usr/gprolog-$VERSION/ and then creating symlinks in /usr/bin. > > This script will correct this by moving the files in > -/usr/gprolog-$VERSION to their propper places in /usr, > +/usr/gprolog-$VERSION to their proper places in /usr, > ie: binaries are placed in /usr/bin, libraries in /usr/lib or > /usr/lib64 and documentation in /usr/doc/gprolog-$VERSION. > - Fixed in my branch, thanks! Should be part of the next push of updates. Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From egregora at gmail.com Sat Nov 6 16:25:43 2010 From: egregora at gmail.com (luciano) Date: Sat, 6 Nov 2010 14:25:43 -0200 Subject: [Slackbuilds-users] Task link error In-Reply-To: <201011061637.56498.pprkut@slackbuilds.org> References: <201011061637.56498.pprkut@slackbuilds.org> Message-ID: Nice. Thank you On Sat, Nov 6, 2010 at 1:37 PM, Heinz Wiesinger wrote: > On Thursday 04 November 2010 16:26:38 luciano wrote: >> Task doesn't build. The link seems wrong. It gives 404 message. > > Thanks for the report! > I fixed this in my branch, it should be part of the next push of updates. > > Grs, > Heinz > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > From andrew.antle at gmail.com Sat Nov 6 17:13:28 2010 From: andrew.antle at gmail.com (Andrew Antle) Date: Sat, 6 Nov 2010 13:13:28 -0400 Subject: [Slackbuilds-users] gprolog README typo fixes In-Reply-To: <201011061638.52190.pprkut@slackbuilds.org> References: <201011061638.52190.pprkut@slackbuilds.org> Message-ID: On Sat, Nov 6, 2010 at 11:38 AM, Heinz Wiesinger wrote: > On Thursday 04 November 2010 15:30:10 Andrew Antle wrote: >> A few minor typo fixes. Diff attached: > > Fixed in my branch, thanks! > Should be part of the next push of updates. > > Grs, > Heinz Thanks, Heinz! -- Andrew Antle From andrew.antle at gmail.com Sat Nov 6 17:13:00 2010 From: andrew.antle at gmail.com (Andrew Antle) Date: Sat, 6 Nov 2010 13:13:00 -0400 Subject: [Slackbuilds-users] gprolog README typo fixes In-Reply-To: <201011061638.52190.pprkut@slackbuilds.org> References: <201011061638.52190.pprkut@slackbuilds.org> Message-ID: On Sat, Nov 6, 2010 at 11:38 AM, Heinz Wiesinger wrote: > On Thursday 04 November 2010 15:30:10 Andrew Antle wrote: >> A few minor typo fixes. Diff attached: > > Fixed in my branch, thanks! > Should be part of the next push of updates. > > Grs, > Heinz Thanks, Heinz! -- Andrew Antle From andrew.antle at gmail.com Sat Nov 6 17:13:00 2010 From: andrew.antle at gmail.com (Andrew Antle) Date: Sat, 6 Nov 2010 13:13:00 -0400 Subject: [Slackbuilds-users] gprolog README typo fixes In-Reply-To: <201011061638.52190.pprkut@slackbuilds.org> References: <201011061638.52190.pprkut@slackbuilds.org> Message-ID: On Sat, Nov 6, 2010 at 11:38 AM, Heinz Wiesinger wrote: > On Thursday 04 November 2010 15:30:10 Andrew Antle wrote: >> A few minor typo fixes. Diff attached: > > Fixed in my branch, thanks! > Should be part of the next push of updates. > > Grs, > Heinz Thanks, Heinz! -- Andrew Antle From leva at ecentrum.hu Sun Nov 7 22:45:05 2010 From: leva at ecentrum.hu (LEVAI Daniel) Date: Sun, 7 Nov 2010 23:45:05 +0100 Subject: [Slackbuilds-users] dropping system/pdksh Message-ID: <20101107224505.GB20170@serenity.digicable.hu> Hi! I'm stopping maintaining system/pdksh in favor of system/ksh. The latter is superior in every way and is actively maintained by upstream. Daniel -- L?VAI D?niel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F From elcaio at gmail.com Tue Nov 9 21:43:19 2010 From: elcaio at gmail.com (caio) Date: Tue, 9 Nov 2010 18:43:19 -0300 Subject: [Slackbuilds-users] rsnapshot broken link Message-ID: Hello, Could you fix the download url of rsnapshot-1.3.1? The right one seem to be at: http://rsnapshot.org/downloads/rsnapshot-1.3.1.tar.gz (note without "www.") If already was fixed or I'm not reporting as should be, please my apllogies. Regards, Claudio From disturbed1976 at gmail.com Tue Nov 9 23:52:15 2010 From: disturbed1976 at gmail.com (Keith Richie) Date: Tue, 9 Nov 2010 18:52:15 -0500 Subject: [Slackbuilds-users] Small error in Transmission Build Script Message-ID: http://www.linuxquestions.org/questions/showthread.php?p=4154127&posted=1#post4154127 The ARCH is hard coded in the script, which negates the use of the uname -m case to find the particular arch. Removing ARCH=${ARCH:-i486} Fixes the problem. From michiel at slackbuilds.org Wed Nov 10 00:21:16 2010 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Wed, 10 Nov 2010 00:21:16 +0000 Subject: [Slackbuilds-users] Small error in Transmission Build Script In-Reply-To: References: Message-ID: <20101110002116.6c6a3cbf@hades.esn.local> On Tue, 9 Nov 2010 18:52:15 -0500 Keith Richie wrote: > http://www.linuxquestions.org/questions/showthread.php?p=4154127&posted=1#post4154127 > Thanks, fixed this in my branch, so it gets pushed out on next update. -M. -- Michiel van Wessem http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From binhnguyen at fastmail.fm Wed Nov 10 06:05:33 2010 From: binhnguyen at fastmail.fm (Binh Nguyen) Date: Wed, 10 Nov 2010 13:05:33 +0700 Subject: [Slackbuilds-users] Geany home page in SlackBuild broken Message-ID: <20101110130533.7f0ea0ba@darkstar.example.net> It is now http://www.geany.org/ Regards, -- Binh Nguyen From lukenshiro at ngi.it Wed Nov 10 13:40:36 2010 From: lukenshiro at ngi.it (LukenShiro) Date: Wed, 10 Nov 2010 14:40:36 +0100 Subject: [Slackbuilds-users] perl-digest-hmac duplication in "ready" Message-ID: <20101110144036.66f6d2e0lukenshiro@ngi.it@sigil.norad> I've just noticed a new perl-digest-HMAC submission by Daniel Levai is in "ready". It's clearly a duplication of my already approved perl-digest-hmac (same version), so I guess this new one should be removed. P.S. I would not want to sound too harsh, but, as it's not the first time it happens with perl modules, it would be an absolutely _wonderful_ thing if a potential maintainer verified if a package is already existing, before submitting a new package (it would save maintainer and SBo staff's time). Thank for your cooperation. -- GNU/Linux * Slackware64 current LU #210970 SU #12583 LM #98222/#412913 From pwcazenave at gmail.com Wed Nov 10 17:19:20 2010 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Wed, 10 Nov 2010 17:19:20 +0000 Subject: [Slackbuilds-users] Submission removal request of the day: synergy-plus Message-ID: <4CDAD418.9010603@gmail.com> Could synergy-plus.tar.bz2 be removed from the pending list please? I've identified a problem with the submission and have a corrected version ready. Thanks, Pierre From michiel at slackbuilds.org Wed Nov 10 17:49:53 2010 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Wed, 10 Nov 2010 17:49:53 +0000 Subject: [Slackbuilds-users] Submission removal request of the day: synergy-plus In-Reply-To: <4CDAD418.9010603@gmail.com> References: <4CDAD418.9010603@gmail.com> Message-ID: <20101110174953.395086d5@hades.esn.local> On Wed, 10 Nov 2010 17:19:20 +0000 Pierre Cazenave wrote: > Could synergy-plus.tar.bz2 be removed from the pending list please? > I've identified a problem with the submission and have a corrected > version ready. Done - removed. -M. -- Michiel van Wessem http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From t3slider at gmail.com Wed Nov 10 20:58:03 2010 From: t3slider at gmail.com (T3slider) Date: Wed, 10 Nov 2010 15:58:03 -0500 Subject: [Slackbuilds-users] Request to remove remind from pending Message-ID: <20101110205803.GA3305@KeithPC.phub.net.cable.rogers.com> I'm not sure if this slipped through the cracks or if things just take a while to get done, but is it possible to get remind removed from pending? Three other pending removal requests have been submitted to this list and fulfilled since I sent this one... Sorry again for any inconvenience. -T3slider On Mon, Nov 01, 2010 at 06:05:35PM -0400, T3slider wrote: > I submitted a SlackBuild for remind yesterday. I am requesting that it > be removed from pending since I have rewritten much of it to make it > more user-friendly (the previous submission required direct editing of > two configuration files, while the new one uses a variety of environment > variables, making it easier for those using sbopkg, for example). Once > removed I will resubmit my new SlackBuild which has already been > completed. > > I apologize for any inconvenience this may have caused. > > -T3slider From michiel at slackbuilds.org Wed Nov 10 21:57:31 2010 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Wed, 10 Nov 2010 21:57:31 +0000 Subject: [Slackbuilds-users] Request to remove remind from pending In-Reply-To: <20101110205803.GA3305@KeithPC.phub.net.cable.rogers.com> References: <20101110205803.GA3305@KeithPC.phub.net.cable.rogers.com> Message-ID: <20101110215731.385cab8f@hades.esn.local> On Wed, 10 Nov 2010 15:58:03 -0500 T3slider wrote: > I'm not sure if this slipped through the cracks or if things just > take a while to get done, but is it possible to get remind removed > from pending? Three other pending removal requests have been > submitted to this list and fulfilled since I sent this one... > > Sorry again for any inconvenience. Must have slipped through the cracks of the internet. ;) Anyway, removed now. -- Michiel van Wessem http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From michiel at slackbuilds.org Wed Nov 10 22:29:03 2010 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Wed, 10 Nov 2010 22:29:03 +0000 Subject: [Slackbuilds-users] perl-digest-hmac duplication in "ready" In-Reply-To: <20101110144036.66f6d2e0lukenshiro@ngi.it@sigil.norad> References: <20101110144036.66f6d2e0lukenshiro@ngi.it@sigil.norad> Message-ID: <20101110222903.6f66533d@hades.esn.local> On Wed, 10 Nov 2010 14:40:36 +0100 LukenShiro wrote: > I've just noticed a new perl-digest-HMAC submission by Daniel Levai is > in "ready". > It's clearly a duplication of my already approved perl-digest-hmac > (same version), so I guess this new one should be removed. > Okay, I am partly to blame for this, I noticed that perl-Authen-SASL, required perl-digest-hmac and despite having a quick look I somehow must have overlooked this, and thus asked him to submit this dependency. So, I will remove this from my branch (and READY/), luckily it's writen as perl-Digest-HMAC instead of your perl-digest-hmac, so they don't overwrite each other regardless. Mea Culpa. :) -- Michiel van Wessem http://slackbuilds.org/ -------------- 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 Thu Nov 11 04:14:01 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 10 Nov 2010 22:14:01 -0600 Subject: [Slackbuilds-users] dropping system/pdksh In-Reply-To: <20101107224505.GB20170@serenity.digicable.hu> References: <20101107224505.GB20170@serenity.digicable.hu> Message-ID: <20101110221401.37adbbf6@liberty> On Sun, 7 Nov 2010 23:45:05 +0100 LEVAI Daniel wrote: > I'm stopping maintaining system/pdksh in favor of system/ksh. The > latter is superior in every way and is actively maintained by > upstream. Noted; 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 jsunx1 at bellsouth.net Fri Nov 12 04:33:25 2010 From: jsunx1 at bellsouth.net (slakmagik) Date: Thu, 11 Nov 2010 23:33:25 -0500 Subject: [Slackbuilds-users] Sbopkg 0.34.0 Released Message-ID: <20101112043325.GA18139@devbox> sbopkg 0.34.0 is released. This release has been awhile in coming and includes some revisions in the directory initialization and in the command line interface, including the ability to pass app-specific options on the command line and to specify the -b, -g, -i, and -s flags multiple times. It also fixes the -s option, which had been broken for awhile. It also includes a revised configuration file, new man pages, and has various other enhancements and bugfixes. Thanks to all sbopkg users who help out with bug reports, suggestions, and whose appreciation of sbopkg is appreciated. :) This release can be downloaded from http://www.sbopkg.org or http://code.google.com/p/sbopkg/ Here are the specific changes since the last release: * Revised man pages - these are very different and now document a couple of previously undocumented things and are worth a (re-)read. Thanks to Marie-Claude Collilieux for the French translations of these. * The HACKING file now includes a man page style guide in addition to the coding style guide. * The LOGDIR variable has been removed from sbopkg.conf - DIR can be specified in LOGFILE. * The DEBUG variable has been renamed to DEBUG_UPDATES in sbopkg.conf. * The default timeout values in {WGET,RSYNC}FLAGS have been raised from 10/15 to 30 in sbopkg.conf. * All parameters in sbopkg.conf now use default values only if the variable hasn't been previously set (meaning they can all be overridden by passing variables on the command line). * sbopkg.conf has been reordered - this may make any merging that may be needed more interesting this time but hopefully it's worth it. * The directory initialization process has been changed - at first run or otherwise when encountering missing directories, the user will now be presented with a single list of them and a (C)reate/(A)bort prompt. * The command line user interface has been overhauled in terms of more consistent validated command line messages and prompts. * Fix an ARCH display issue in the updates screen; thanks to alkos333, Marc Payne, and David Spencer for confirming the issue and thanks to David Spencer for testing the fix. * Fixed bugs with dzen2 and *zarafa* not downloading/building properly. Note that, while the changes fix these issues and should make it easier to handle similar problems in the future, this change may introduce regressions. If a download or build fails due to a downloaded tarball looking something like 'blah?actual_tarball.tar.gz' or the like, please report it to us. * Fixed bugs with the '-s' option where only the first of multiple arguments would be returned and where the command line select menu was broken. Also where it and the -g flag might inadvertently expand globs wrongly. * It's now possible to specify the b,g,i,s flags multiple times. Previously multiple arguments to these flags had to be quoted (-b "foo bar") but now they can be given as '-b foo -b bar'. The original style is still supported. * With the new style of passing multiple arguments, it is now possible to specify app-specific options on the command line. These take the form of, e.g., '-i app1:opt1="foo bar":opt2=baz app2:opt=mu'. If that's cryptic, see the manual for details. * Users now have the option of interactively retrying a failed https download, invoking wget with '--no-check-certificate', as this can be caused by 'self-signed certificates' and the like. From pprkut at slackbuilds.org Sat Nov 13 12:47:14 2010 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Sat, 13 Nov 2010 13:47:14 +0100 Subject: [Slackbuilds-users] rsnapshot broken link In-Reply-To: References: Message-ID: <201011131347.20310.pprkut@slackbuilds.org> On Tuesday 09 November 2010 22:43:19 caio wrote: > Hello, > > Could you fix the download url of rsnapshot-1.3.1? > > The right one seem to be at: > > http://rsnapshot.org/downloads/rsnapshot-1.3.1.tar.gz > > (note without "www.") > > If already was fixed or I'm not reporting as should be, please my > apllogies. The current link works fine for me. Could you please re-check? Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From pprkut at slackbuilds.org Sat Nov 13 16:10:30 2010 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Sat, 13 Nov 2010 17:10:30 +0100 Subject: [Slackbuilds-users] Geany home page in SlackBuild broken In-Reply-To: <20101110130533.7f0ea0ba@darkstar.example.net> References: <20101110130533.7f0ea0ba@darkstar.example.net> Message-ID: <201011131710.35150.pprkut@slackbuilds.org> On Wednesday 10 November 2010 07:05:33 Binh Nguyen wrote: > It is now http://www.geany.org/ Thanks! Fixed in my branch, will be part of the next update. Grs. Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From mrc.ildp at gmail.com Sun Nov 14 19:51:43 2010 From: mrc.ildp at gmail.com (Marco Cecchetti) Date: Sun, 14 Nov 2010 20:51:43 +0100 Subject: [Slackbuilds-users] Maintenance Message-ID: Dear friends, unfortunately I cannot find time any more to get my slackbuilds updated. I think someone else can do it better than me now. So I have to leave the maintenance. This the list: gst-gnome-vfs exaile mlterm avant-window-navigator ufw eliza bootchart ginac orsa thanks -- Marco Cecchetti -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozan.turkyilmaz at gmail.com Sun Nov 14 20:25:49 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sun, 14 Nov 2010 22:25:49 +0200 Subject: [Slackbuilds-users] Maintenance In-Reply-To: References: Message-ID: 2010/11/14 Marco Cecchetti : > ?eliza > ?bootchart I'll take two or this. I'll submit updated info files when I went back to Home. -- Ozan, BSc, BEng From estranho at diogoleal.com Sun Nov 14 20:38:39 2010 From: estranho at diogoleal.com (Diogo Leal) Date: Sun, 14 Nov 2010 18:38:39 -0200 Subject: [Slackbuilds-users] Maintenance In-Reply-To: References: Message-ID: I would assume the maintenance of these packages: gst-gnome-vfs exaile How should I proceed? Diogo Leal [aka estranho] http://diogoleal.com msn | gtalk: estranho at diogoleal.com 2010/11/14 Ozan T?rky?lmaz : > 2010/11/14 Marco Cecchetti : >> ?eliza >> ?bootchart > > I'll take two or this. I'll submit updated info files when I went back to Home. > > -- > Ozan, BSc, BEng > _______________________________________________ > 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 mfilpot at gmail.com Sun Nov 14 21:43:47 2010 From: mfilpot at gmail.com (Matthew Fillpot) Date: Sun, 14 Nov 2010 16:43:47 -0500 Subject: [Slackbuilds-users] Maintenance of orphans Message-ID: With the recent rash of maintainers giving up their builds, I would like to request for the3 admins to add a list on the website of orphaned slackbuild scripts. This will make it easier for current and potential maintainers to view a complete list of available builds that need to switch hands. I currently have a list of all orphaned builds that were announced in the last month and would gladly pass it onto the site to start the list. In addition would it be possible to add a section to the site were people can request for builds to be made of known apps, so the maintainers can also review that list for future projects? -- -Thank You, -Matthew Fillpot From elcaio at gmail.com Mon Nov 15 12:32:28 2010 From: elcaio at gmail.com (caio) Date: Mon, 15 Nov 2010 09:32:28 -0300 Subject: [Slackbuilds-users] rsnapshot broken link In-Reply-To: <201011131347.20310.pprkut@slackbuilds.org> References: <201011131347.20310.pprkut@slackbuilds.org> Message-ID: Hi, maybe it's my dns problem, however checking also with other dns the result is the same.. rsnapshot: --2010-11-15 09:28:00-- http://www.rsnapshot.org/downloads/rsnapshot-1.3.1.tar.gz Resolving www.rsnapshot.org (www.rsnapshot.org)... failed: Name or service not known. wget: unable to resolve host address ?www.rsnapshot.org? $ host www.rsnapshot.org Host www.rsnapshot.org not found: 3(NXDOMAIN) $ host www.rsnapshot.org 8.8.8.8 Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 Aliases: Host www.rsnapshot.org not found: 3(NXDOMAIN) $ host www.rsnapshot.org 208.67.222.222 Using domain server: Name: 208.67.222.222 Address: 208.67.222.222#53 Aliases: www.rsnapshot.org has address 67.215.65.132 Host www.rsnapshot.org not found: 3(NXDOMAIN) Thanks. Claudio On Sat, Nov 13, 2010 at 9:47 AM, Heinz Wiesinger wrote: > On Tuesday 09 November 2010 22:43:19 caio wrote: >> Hello, >> >> Could you fix the download url of rsnapshot-1.3.1? >> >> The right one seem to be at: >> >> http://rsnapshot.org/downloads/rsnapshot-1.3.1.tar.gz >> >> (note without "www.") >> >> If already was fixed or I'm not reporting as should be, please my >> apllogies. > > The current link works fine for me. Could you please re-check? > > Grs, > Heinz > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > From binhnguyen at fastmail.fm Mon Nov 15 13:19:36 2010 From: binhnguyen at fastmail.fm (Binh Nguyen) Date: Mon, 15 Nov 2010 20:19:36 +0700 Subject: [Slackbuilds-users] rsnapshot broken link In-Reply-To: References: <201011131347.20310.pprkut@slackbuilds.org> Message-ID: <20101115201936.491e3d38@darkstar.example.net> On Mon, 15 Nov 2010 09:32:28 -0300 caio wrote: > Hi, maybe it's my dns problem, however checking also with other dns > the result is the same.. > > rsnapshot: > --2010-11-15 09:28:00-- > http://www.rsnapshot.org/downloads/rsnapshot-1.3.1.tar.gz > Resolving www.rsnapshot.org (www.rsnapshot.org)... failed: Name or > service not known. > wget: unable to resolve host address ?www.rsnapshot.org? > Cannot access the site from here too. Maybe it's temporarily down. -- Binh Nguyen From kingbeowulf at gmail.com Mon Nov 15 14:32:17 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 15 Nov 2010 06:32:17 -0800 Subject: [Slackbuilds-users] Maintenance of orphans In-Reply-To: References: Message-ID: An orphan list on SBo would be grand; maybe a transfer of maintainer section as well. A form where people can add to a wish list might also be helpful. On 11/14/10, Matthew Fillpot wrote: > With the recent rash of maintainers giving up their builds, I would > like to request for the3 admins to add a list on the website of > orphaned slackbuild scripts. This will make it easier for current and > potential maintainers to view a complete list of available builds that > need to switch hands. > I currently have a list of all orphaned builds that were announced in > the last month and would gladly pass it onto the site to start the > list. > > In addition would it be possible to add a section to the site were > people can request for builds to be made of known apps, so the > maintainers can also review that list for future projects? > > -- > -Thank You, > -Matthew Fillpot > _______________________________________________ > 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/ > > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From hba.nihilismus at gmail.com Mon Nov 15 15:45:16 2010 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Mon, 15 Nov 2010 09:45:16 -0600 Subject: [Slackbuilds-users] Maintenance of orphans In-Reply-To: References: Message-ID: On Mon, Nov 15, 2010 at 8:32 AM, King Beowulf wrote: > An orphan list on SBo would be grand; maybe a transfer of maintainer > section as well. A form where people can add to a wish list might also > be helpful. > > > > On 11/14/10, Matthew Fillpot wrote: >> With the recent rash of maintainers giving up their builds, I would >> like to request for the3 admins to add a list on the website of >> orphaned slackbuild scripts. This will make it easier for current and >> potential maintainers to view a complete list of available builds that >> need to switch hands. >> I currently have a list of all orphaned builds that were announced in >> the last month and would gladly pass it onto the site to start the >> list. >> >> In addition would it be possible to add a section to the site were >> people can request for builds to be made of known apps, so the >> maintainers can also review that list for future projects? >> >> -- >> -Thank You, >> -Matthew Fillpot >> _______________________________________________ >> 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/ >> >> > > -- > Sent from my mobile device > > You! What PLANET is this! > ? ? ? ?-- McCoy, "The City on the Edge of Forever", stardate 3134.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/ > > IMHO theres no need for an "orphaned slackbuild scripts list", with a "simple solution" as the creation of another mail list (maybe SlackBuilds-maintainers), so any maintainer that want to drop out the maintainership of his/her slackbuild should send a message indicating which slackbuild would be orphaned but also send an update to reflect this, in *.info file should be 'MAINTAINER="ORPHAN"' and 'EMAIL=ORPHANED"'. The Subject of the email would be "[MAINTAINERSHIP] SECTION/PKGNAM", for example "[MAINTAINERSHIP] system/qemu-kvm"... i hope there?s nobody who uses "orphaned" as its nickname :) The same situation arise when someone want to maintain an orphaned slackbuild, responds to the mail of the original maintainer indicating that he/she want to take care of the slackbuild and also should send an update with the *.info file updated with his/her own data in MAINTAINER/EMAIL variables. About the "request for builds", you can use this same mail list, but with a Subject to something like "[REQUEST] PKGNAM HOMEPAGE", for example "[REQUEST] libmodplug modplug-xmms.sourceforge.net". There?s a chance that someone else already has the SlackBuild, but maybe it need more testing... i don?t know. Sure, i know that you could just use this same mail list for maintainer and users (after all its just the Subject what change), but i thing its better organized our communication in this way. In few words, there?s a lack of communication in this community.... -- - hba From mfilpot at gmail.com Mon Nov 15 16:30:26 2010 From: mfilpot at gmail.com (Matthew Fillpot) Date: Mon, 15 Nov 2010 11:30:26 -0500 Subject: [Slackbuilds-users] Maintenance of orphans In-Reply-To: References: Message-ID: Hba, changing the maintainers name to orphaned does sound like a simpler solution since most of us keep local mirrors. I like your recommendations and eagerly await some input from the admins. - sent from my nexus one On Nov 15, 2010 10:45 AM, "Antonio Hern?ndez Blas" wrote: > On Mon, Nov 15, 2010 at 8:32 AM, King Beowulf wrote: >> An orphan list on SBo would be grand; maybe a transfer of maintainer >> section as well. A form where people can add to a wish list might also >> be helpful. >> >> >> >> On 11/14/10, Matthew Fillpot wrote: >>> With the recent rash of maintainers giving up their builds, I would >>> like to request for the3 admins to add a list on the website of >>> orphaned slackbuild scripts. This will make it easier for current and >>> potential maintainers to view a complete list of available builds that >>> need to switch hands. >>> I currently have a list of all orphaned builds that were announced in >>> the last month and would gladly pass it onto the site to start the >>> list. >>> >>> In addition would it be possible to add a section to the site were >>> people can request for builds to be made of known apps, so the >>> maintainers can also review that list for future projects? >>> >>> -- >>> -Thank You, >>> -Matthew Fillpot >>> _______________________________________________ >>> 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/ >>> >>> >> >> -- >> Sent from my mobile device >> >> You! What PLANET is this! >> -- McCoy, "The City on the Edge of Forever", stardate 3134.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/ >> >> > > IMHO theres no need for an "orphaned slackbuild scripts list", with a > "simple solution" as the creation of another mail list (maybe > SlackBuilds-maintainers), so any maintainer that want to drop out the > maintainership of his/her slackbuild should send a message indicating > which slackbuild would be orphaned but also send an update to reflect > this, in *.info file should be 'MAINTAINER="ORPHAN"' and > 'EMAIL=ORPHANED"'. The Subject of the email would be "[MAINTAINERSHIP] > SECTION/PKGNAM", for example "[MAINTAINERSHIP] system/qemu-kvm"... i > hope there?s nobody who uses "orphaned" as its nickname :) > > The same situation arise when someone want to maintain an orphaned > slackbuild, responds to the mail of the original maintainer indicating > that he/she want to take care of the slackbuild and also should send > an update with the *.info file updated with his/her own data in > MAINTAINER/EMAIL variables. > > About the "request for builds", you can use this same mail list, but > with a Subject to something like "[REQUEST] PKGNAM HOMEPAGE", for > example "[REQUEST] libmodplug modplug-xmms.sourceforge.net". There?s a > chance that someone else already has the SlackBuild, but maybe it need > more testing... i don?t know. > > Sure, i know that you could just use this same mail list for > maintainer and users (after all its just the Subject what change), but > i thing its better organized our communication in this way. > > In few words, there?s a lack of communication in this community.... > > -- > - hba > _______________________________________________ > 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 crockabiscuit at yahoo.com Tue Nov 16 08:27:43 2010 From: crockabiscuit at yahoo.com (crocket) Date: Tue, 16 Nov 2010 00:27:43 -0800 (PST) Subject: [Slackbuilds-users] Maintenance of orphans In-Reply-To: References: Message-ID: <543068.10003.qm@web120312.mail.ne1.yahoo.com> What if a maintainer uses a nickname, orphaned? Poop, it's joke!!! ________________________________ From: Matthew Fillpot To: SlackBuilds.org Users List Sent: Tue, November 16, 2010 1:30:26 AM Subject: Re: [Slackbuilds-users] Maintenance of orphans Hba, changing the maintainers name to orphaned does sound like a simpler solution since most of us keep local mirrors. I like your recommendations and eagerly await some input from the admins. - sent from my nexus one On Nov 15, 2010 10:45 AM, "Antonio Hern?ndez Blas" wrote: > On Mon, Nov 15, 2010 at 8:32 AM, King Beowulf wrote: >> An orphan list on SBo would be grand; maybe a transfer of maintainer >> section as well. A form where people can add to a wish list might also >> be helpful. >> >> >> >> On 11/14/10, Matthew Fillpot wrote: >>> With the recent rash of maintainers giving up their builds, I would >>> like to request for the3 admins to add a list on the website of >>> orphaned slackbuild scripts. This will make it easier for current and >>> potential maintainers to view a complete list of available builds that >>> need to switch hands. >>> I currently have a list of all orphaned builds that were announced in >>> the last month and would gladly pass it onto the site to start the >>> list. >>> >>> In addition would it be possible to add a section to the site were >>> people can request for builds to be made of known apps, so the >>> maintainers can also review that list for future projects? >>> >>> -- >>> -Thank You, >>> -Matthew Fillpot >>> _______________________________________________ >>> 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/ >>> >>> >> >> -- >> Sent from my mobile device >> >> You! What PLANET is this! >> -- McCoy, "The City on the Edge of Forever", stardate 3134.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/ >> >> > > IMHO theres no need for an "orphaned slackbuild scripts list", with a > "simple solution" as the creation of another mail list (maybe > SlackBuilds-maintainers), so any maintainer that want to drop out the > maintainership of his/her slackbuild should send a message indicating > which slackbuild would be orphaned but also send an update to reflect > this, in *.info file should be 'MAINTAINER="ORPHAN"' and > 'EMAIL=ORPHANED"'. The Subject of the email would be "[MAINTAINERSHIP] > SECTION/PKGNAM", for example "[MAINTAINERSHIP] system/qemu-kvm"... i > hope there?s nobody who uses "orphaned" as its nickname :) > > The same situation arise when someone want to maintain an orphaned > slackbuild, responds to the mail of the original maintainer indicating > that he/she want to take care of the slackbuild and also should send > an update with the *.info file updated with his/her own data in > MAINTAINER/EMAIL variables. > > About the "request for builds", you can use this same mail list, but > with a Subject to something like "[REQUEST] PKGNAM HOMEPAGE", for > example "[REQUEST] libmodplug modplug-xmms.sourceforge.net". There?s a > chance that someone else already has the SlackBuild, but maybe it need > more testing... i don?t know. > > Sure, i know that you could just use this same mail list for > maintainer and users (after all its just the Subject what change), but > i thing its better organized our communication in this way. > > In few words, there?s a lack of communication in this community.... > > -- > - hba > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From kingbeowulf at gmail.com Tue Nov 16 17:40:33 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 16 Nov 2010 09:40:33 -0800 Subject: [Slackbuilds-users] Maintenance of orphans In-Reply-To: References: Message-ID: I can live with the "last" maintainer putting in "orphaned" in the .info however, "most of us" should be corrected to "some of us" for the mirrors. I don't maintain such a mirror since a lot of the software doesn't interest me (and just lost a 160Gb Sata with my slackware stuff too so space is at a premium). I was thinking of a simple page on SBo for a quick review instead of having to search through the mail list and all of the info files. On 11/15/10, Matthew Fillpot wrote: > Hba, changing the maintainers name to orphaned does sound like a simpler > solution since most of us keep local mirrors. I like your recommendations > and eagerly await some input from the admins. > > - sent from my nexus one > On Nov 15, 2010 10:45 AM, "Antonio Hern?ndez Blas" > > wrote: >> On Mon, Nov 15, 2010 at 8:32 AM, King Beowulf > wrote: >>> An orphan list on SBo would be grand; maybe a transfer of maintainer >>> section as well. A form where people can add to a wish list might also >>> be helpful. >>> >>> >>> >>> On 11/14/10, Matthew Fillpot wrote: >>>> With the recent rash of maintainers giving up their builds, I would >>>> like to request for the3 admins to add a list on the website of >>>> orphaned slackbuild scripts. This will make it easier for current and >>>> potential maintainers to view a complete list of available builds that >>>> need to switch hands. >>>> I currently have a list of all orphaned builds that were announced in >>>> the last month and would gladly pass it onto the site to start the >>>> list. >>>> >>>> In addition would it be possible to add a section to the site were >>>> people can request for builds to be made of known apps, so the >>>> maintainers can also review that list for future projects? >>>> >>>> -- >>>> -Thank You, >>>> -Matthew Fillpot >>>> _______________________________________________ >>>> 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/ >>>> >>>> >>> >>> -- >>> Sent from my mobile device >>> >>> You! What PLANET is this! >>> -- McCoy, "The City on the Edge of Forever", stardate 3134.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/ >>> >>> >> >> IMHO theres no need for an "orphaned slackbuild scripts list", with a >> "simple solution" as the creation of another mail list (maybe >> SlackBuilds-maintainers), so any maintainer that want to drop out the >> maintainership of his/her slackbuild should send a message indicating >> which slackbuild would be orphaned but also send an update to reflect >> this, in *.info file should be 'MAINTAINER="ORPHAN"' and >> 'EMAIL=ORPHANED"'. The Subject of the email would be "[MAINTAINERSHIP] >> SECTION/PKGNAM", for example "[MAINTAINERSHIP] system/qemu-kvm"... i >> hope there?s nobody who uses "orphaned" as its nickname :) >> >> The same situation arise when someone want to maintain an orphaned >> slackbuild, responds to the mail of the original maintainer indicating >> that he/she want to take care of the slackbuild and also should send >> an update with the *.info file updated with his/her own data in >> MAINTAINER/EMAIL variables. >> >> About the "request for builds", you can use this same mail list, but >> with a Subject to something like "[REQUEST] PKGNAM HOMEPAGE", for >> example "[REQUEST] libmodplug modplug-xmms.sourceforge.net". There?s a >> chance that someone else already has the SlackBuild, but maybe it need >> more testing... i don?t know. >> >> Sure, i know that you could just use this same mail list for >> maintainer and users (after all its just the Subject what change), but >> i thing its better organized our communication in this way. >> >> In few words, there?s a lack of communication in this community.... >> >> -- >> - hba >> _______________________________________________ >> 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/ >> > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From vmj at linuxbox.fi Tue Nov 16 20:36:23 2010 From: vmj at linuxbox.fi (Mikko Varri) Date: Tue, 16 Nov 2010 22:36:23 +0200 Subject: [Slackbuilds-users] Maintenance of orphans In-Reply-To: References: Message-ID: <20101116203623.GM28447@linuxbox.fi> I seem to remember that there used to be a convention of setting MAINTAINER="nobody". In master branch, there's only three of those now, though - not much of a convention. vmj at ununoctium:~/src/slackbuilds$ grep -i "MAINTAINER=\"nobody\"" */*/*.info libraries/libgnomecups/libgnomecups.info:MAINTAINER="nobody" libraries/libgnomeprint/libgnomeprint.info:MAINTAINER="nobody" libraries/libgnomeprintui/libgnomeprintui.info:MAINTAINER="nobody" -vmj From andrew.antle at gmail.com Wed Nov 17 23:53:13 2010 From: andrew.antle at gmail.com (Andrew Antle) Date: Wed, 17 Nov 2010 18:53:13 -0500 Subject: [Slackbuilds-users] audacity typo fix Message-ID: Small typo fix. Diff attached. $ diff -u audacity.SlackBuild.orig audacity.SlackBuild --- audacity.SlackBuild.orig 2010-11-17 18:49:20.386716894 -0500 +++ audacity.SlackBuild 2010-11-17 18:49:46.109738092 -0500 @@ -121,7 +121,7 @@ install -D -m 0644 images/AudacityLogo48x48.xpm \ $PKG/usr/share/pixmaps/audacity.xpm -# Move manpage directory to proper loacation; pages are gzipped already +# Move manpage directory to proper location; pages are gzipped already mv $PKG/usr/share/man $PKG/usr mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION -- Andrew Antle -------------- next part -------------- --- audacity.SlackBuild.orig 2010-11-17 18:49:20.386716894 -0500 +++ audacity.SlackBuild 2010-11-17 18:49:46.109738092 -0500 @@ -121,7 +121,7 @@ install -D -m 0644 images/AudacityLogo48x48.xpm \ $PKG/usr/share/pixmaps/audacity.xpm -# Move manpage directory to proper loacation; pages are gzipped already +# Move manpage directory to proper location; pages are gzipped already mv $PKG/usr/share/man $PKG/usr mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION From niels.horn at gmail.com Thu Nov 18 11:13:46 2010 From: niels.horn at gmail.com (Niels Horn) Date: Thu, 18 Nov 2010 09:13:46 -0200 Subject: [Slackbuilds-users] remmina download link Message-ID: Not sure if this was already mentioned before, but the download link for remmina is not working. The link on SBo is: http://downloads.sourceforge.net/project/remmina/0.8/remmina-0.8.0.tar.gz One that works is: http://downloads.sourceforge.net/remmina/remmina-0.8.0.tar.gz Regards, Niels Horn Rio de Janeiro, RJ Brasil From niels.horn at gmail.com Thu Nov 18 11:21:12 2010 From: niels.horn at gmail.com (Niels Horn) Date: Thu, 18 Nov 2010 09:21:12 -0200 Subject: [Slackbuilds-users] remmina download link In-Reply-To: References: Message-ID: On Thu, Nov 18, 2010 at 9:13 AM, Niels Horn wrote: > Not sure if this was already mentioned before, but the download link > for remmina is not working. > > The link on SBo is: > http://downloads.sourceforge.net/project/remmina/0.8/remmina-0.8.0.tar.gz > > One that works is: > http://downloads.sourceforge.net/remmina/remmina-0.8.0.tar.gz > Ah, and the same goes for remmina-plugins... Just remove the "project" and "0.8" parts from the path... > Regards, > > Niels Horn > Rio de Janeiro, RJ > Brasil > From mark at theathertons.org.uk Sun Nov 21 11:32:18 2010 From: mark at theathertons.org.uk (Mark Atherton) Date: Sun, 21 Nov 2010 11:32:18 +0000 Subject: [Slackbuilds-users] ffmpeg.SlackBuild doesn't install man page Message-ID: <20101121113218.07973173@hermes> When I run the supplied ffmpeg.SlacBuild script it fails with the message: ffmpeg.SlackBuild.old: line 194: cd: /tmp/SBo/package-ffmpeg/usr/man: No such file or directory I think the man page needs to be installed explicitly with "make install-man". When I patch as below the script builds the package properly. patch ffmpeg.SlackBuild <<"EOF" 189c189 < make install DESTDIR=$PKG --- > make install install-man DESTDIR=$PKG EOF Mark From belka.ew at gmail.com Sun Nov 21 14:05:10 2010 From: belka.ew at gmail.com (Eugen Wissner) Date: Sun, 21 Nov 2010 15:05:10 +0100 Subject: [Slackbuilds-users] ffmpeg.SlackBuild doesn't install man page In-Reply-To: <20101121113218.07973173@hermes> References: <20101121113218.07973173@hermes> Message-ID: http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-June/005750.html 2010/11/21 Mark Atherton : > When I run the supplied ffmpeg.SlacBuild script it fails with the > message: > > ffmpeg.SlackBuild.old: line 194: cd: /tmp/SBo/package-ffmpeg/usr/man: > No such file or directory > > I think the man page needs to be installed explicitly with > "make install-man". When I patch as below the script builds the > package properly. > > patch ffmpeg.SlackBuild <<"EOF" > 189c189 > < make install DESTDIR=$PKG > --- >> make install install-man DESTDIR=$PKG > EOF > > > Mark > _______________________________________________ > 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 mark at theathertons.org.uk Sun Nov 21 19:31:07 2010 From: mark at theathertons.org.uk (Mark Atherton) Date: Sun, 21 Nov 2010 19:31:07 +0000 Subject: [Slackbuilds-users] ffmpeg.SlackBuild doesn't install man page In-Reply-To: References: <20101121113218.07973173@hermes> Message-ID: <20101121193107.18d850a7@harlequin> On Sun, 21 Nov 2010 15:05:10 +0100 Eugen Wissner wrote: > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-June/005750.html Ah, apologies. I suspect this is the problem. I will check later. Best wishes, Mark From mark at theathertons.org.uk Sun Nov 21 20:37:56 2010 From: mark at theathertons.org.uk (Mark Atherton) Date: Sun, 21 Nov 2010 20:37:56 +0000 Subject: [Slackbuilds-users] ffmpeg.SlackBuild doesn't install man page In-Reply-To: <20101121193107.18d850a7@harlequin> References: <20101121113218.07973173@hermes> <20101121193107.18d850a7@harlequin> Message-ID: <20101121203756.1606ca53@harlequin.theathertons> On Sun, 21 Nov 2010 19:31:07 +0000 Mark Atherton wrote: > > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-June/005750.html > > Ah, apologies. I suspect this is the problem. I will check later. Yes, after "su -" the slackbuild works fine. From asaf at lingnu.com Sun Nov 21 21:13:25 2010 From: asaf at lingnu.com (Asaf) Date: Sun, 21 Nov 2010 23:13:25 +0200 Subject: [Slackbuilds-users] early mini announcement of project slacktools Message-ID: <4CE98B75.9070509@lingnu.com> https://github.com/asaf-oh/slacktools currently contains the 'autoslack.sh' script that uses m4 template (generic.SlackBuild.as) and a config file (sample: cfg.d/wine.conf) to generate wine.SlackBuild (for example). all the m4 macros are in autoslack.m4 future versions will also * generate wine.info and maybe more. * attempt to auto-upgrade by bumping versions. * enable to change configuration options and the like. I'm thinking of integrating those things into sbopkg, what do you think ? From kingbeowulf at gmail.com Sun Nov 21 22:16:34 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 21 Nov 2010 14:16:34 -0800 Subject: [Slackbuilds-users] Limewire and Frostwre Message-ID: Limewire seems down for the count. The current download link is dead and the main site is "on hold" due to a court ordered injunction. So we may when to pull Limewire from the repository. On the other hand Frostwire is still up and the current frostwire.slackbuild seems to repackage Frostwire-4.21-1 just fine and dandy. The maintainer might want to consider a version bump. -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at gmail.com Mon Nov 22 00:16:04 2010 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Mon, 22 Nov 2010 07:16:04 +0700 Subject: [Slackbuilds-users] Please Remove FileZilla on Pending Queue Message-ID: I have updated SlackBuild script for FileZilla 3.3.5.1 which has been released by now, so please delete the current one on pending queue so i can re-submit the new one Thanks -- Willy Sudiarto Raharjo Registered Linux User : 336579 Web : http://www.informatix.or.id/willy Blog : http://willysr.blogspot.com http://slackblogs.blogspot.com From michiel at slackbuilds.org Mon Nov 22 02:05:50 2010 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Mon, 22 Nov 2010 02:05:50 +0000 Subject: [Slackbuilds-users] Please Remove FileZilla on Pending Queue In-Reply-To: References: Message-ID: <20101122020550.2176f3e6@hades.esn.local> On Mon, 22 Nov 2010 07:16:04 +0700 Willy Sudiarto Raharjo wrote: > I have updated SlackBuild script for FileZilla 3.3.5.1 which has been > released by now, so please delete the current one on pending queue so > i can re-submit the new one Done. -- Michiel van Wessem http://slackbuilds.org/ -------------- 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 Nov 22 02:51:26 2010 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Mon, 22 Nov 2010 09:51:26 +0700 Subject: [Slackbuilds-users] Please Remove FileZilla on Pending Queue In-Reply-To: <20101122020550.2176f3e6@hades.esn.local> References: <20101122020550.2176f3e6@hades.esn.local> Message-ID: >> I have updated SlackBuild script for FileZilla 3.3.5.1 which has been >> released by now, so please delete the current one on pending queue so >> i can re-submit the new one > > Done. Thanks I have re-submit the new SlackBuild script for 3.3.5.1 -- Willy Sudiarto Raharjo Registered Linux User : 336579 Web : http://www.informatix.or.id/willy Blog : http://willysr.blogspot.com http://slackblogs.blogspot.com From mpagnan at acanac.net Mon Nov 22 03:35:01 2010 From: mpagnan at acanac.net (Martin Pagnan) Date: Sun, 21 Nov 2010 22:35:01 -0500 Subject: [Slackbuilds-users] Nvidia driver update - for GoogleEarth and Amaya Builds, perhaps others Message-ID: <4CE9E4E5.1070301@acanac.net> Both GoogleEarth.Slackbuild and Amaya.Slackbuild failed for me in that they both crashed KDE. After a long painstaking search I found a recommendation to reinstall the Nvidia driver. Reinstalling my old driver (version x86_64-256) did not fix the problem. The error log indicated that the GLX module was not loaded - even though it was specified in the xorg.conf file and the GLXmodules were installed. Then I looked to the Nvidia site for a new driver and downloaded and installed the latest version - NVIDIA-Linux-x86_64-260.19.21.run. This fixed both problems. KDE no longer crashes. The GLX module now loads. The release notes for this new version state that it fixes a problem where "multi-threaded applications" would sometimes crash. I have notified the maintainers of the GoogleEarth and Amaya Slackbuilds on this, but I thought that others may be experiencing similar problems with other builds so I am posting this here. From crockabiscuit at yahoo.com Mon Nov 22 09:55:27 2010 From: crockabiscuit at yahoo.com (crocket) Date: Mon, 22 Nov 2010 01:55:27 -0800 (PST) Subject: [Slackbuilds-users] I request removing cclive from the pending queue. Message-ID: <869363.12672.qm@web120305.mail.ne1.yahoo.com> I modified README in cclive.tar.bz2, and I want to submit the new slackbuild. From chris.abela at maltats.com Mon Nov 22 10:14:00 2010 From: chris.abela at maltats.com (Chris Abela) Date: Mon, 22 Nov 2010 11:14:00 +0100 Subject: [Slackbuilds-users] Nvidia driver update - for GoogleEarth and Amaya Builds, perhaps others In-Reply-To: <4CE9E4E5.1070301@acanac.net> Message-ID: Same here with Googleearth on Nvidia. All you (we) need are both the 64 bit and the 32 bit nvidia drivers. See: http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib "Caveats After installing the "-compat32" packages, you may have to re-install your binary Nvidia or Ati video X.Org drivers. These driver packages contain both 64bit and 32bit libraries to be maximally useful on a 64bit multilib OS. If you installed the driver files for both architectures, the "mesa-compat32" package will overwrite some of the 32bit library files. On the other hand, if you originally only installed the 64bit driver libraries for your Nvidia/Ati card, it is recommended after installation of the multilib packages, to re-install the binary driver package. This time, choose to install the 32bit driver files as well. The graphical 32bit applications that you are going to run on your multilib installation will require these 32bit driver libraries. Crashes are likely to occur if you fail to install the correct files." -----Original Message----- From: slackbuilds-users-bounces at slackbuilds.org [mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of Martin Pagnan Sent: 22 November 2010 04:35 To: SlackBuilds-users at slackbuilds.org Subject: [Slackbuilds-users] Nvidia driver update - for GoogleEarth and Amaya Builds, perhaps others Both GoogleEarth.Slackbuild and Amaya.Slackbuild failed for me in that they both crashed KDE. After a long painstaking search I found a recommendation to reinstall the Nvidia driver. Reinstalling my old driver (version x86_64-256) did not fix the problem. The error log indicated that the GLX module was not loaded - even though it was specified in the xorg.conf file and the GLXmodules were installed. Then I looked to the Nvidia site for a new driver and downloaded and installed the latest version - NVIDIA-Linux-x86_64-260.19.21.run. This fixed both problems. KDE no longer crashes. The GLX module now loads. The release notes for this new version state that it fixes a problem where "multi-threaded applications" would sometimes crash. I have notified the maintainers of the GoogleEarth and Amaya Slackbuilds on this, but I thought that others may be experiencing similar problems with other builds so I am posting this here. _______________________________________________ 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 michiel at slackbuilds.org Mon Nov 22 14:45:15 2010 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Mon, 22 Nov 2010 14:45:15 +0000 Subject: [Slackbuilds-users] I request removing cclive from the pending queue. In-Reply-To: <869363.12672.qm@web120305.mail.ne1.yahoo.com> References: <869363.12672.qm@web120305.mail.ne1.yahoo.com> Message-ID: <20101122144515.64d31c33@hades.esn.local> On Mon, 22 Nov 2010 01:55:27 -0800 (PST) crocket wrote: > I modified README in cclive.tar.bz2, and I want to submit the new > slackbuild. Done. -- Michiel van Wessem http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From nishant at mnspace.net Mon Nov 22 15:44:32 2010 From: nishant at mnspace.net (Nishant Limbachia) Date: Mon, 22 Nov 2010 09:44:32 -0600 Subject: [Slackbuilds-users] perl-NetAddr-IP in pending Message-ID: <4CEA8FE0.5080007@mnspace.net> Admins, Please remove this from pending. I'll submit a newer version later today. Thanks, From mpagnan at acanac.net Mon Nov 22 16:24:57 2010 From: mpagnan at acanac.net (Martin Pagnan) Date: Mon, 22 Nov 2010 11:24:57 -0500 Subject: [Slackbuilds-users] Nvidia driver update - for GoogleEarth and Amaya Builds, perhaps others In-Reply-To: References: Message-ID: <4CEA9959.2090803@acanac.net> Chris, This is interesting. The GoogleEarth.SlackBuild that I used has the arch set as 486 and does a binary install. The Amaya.Slackbuild tests the architecture (and in my case chose 64bit) and compiles from source. The new Nvidia driver that I installed is apparently, from its name, for 64bit (like my old one). But now both Amaya and GoogleEarth work great and I did not install the 32bit Nvidia driver. I have installed multilib and read the recommendations. Could it be that Nvidia's new 64bit driver has a 32bit thunk built in? On 11/22/2010 05:14 AM, Chris Abela wrote: > On the other hand, if you originally only installed the 64bit driver > libraries for your Nvidia/Ati card, it is recommended after installation of > the multilib packages, to re-install the binary driver package. This time, > choose to install the 32bit driver files as well. > > The graphical 32bit applications that you are going to run on your multilib > installation will require these 32bit driver libraries. Crashes are likely > to occur if you fail to install the correct files." > > > > -----Original Message----- > From: slackbuilds-users-bounces at slackbuilds.org > [mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of Martin > Pagnan > Sent: 22 November 2010 04:35 > To: SlackBuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] Nvidia driver update - for GoogleEarth and > Amaya Builds, perhaps others > > Both GoogleEarth.Slackbuild and Amaya.Slackbuild failed for me in that > they both crashed KDE. After a long painstaking search I found a > recommendation to reinstall the Nvidia driver. Reinstalling my old > driver (version x86_64-256) did not fix the problem. The error log > indicated that the GLX module was not loaded - even though it was > specified in the xorg.conf file and the GLXmodules were installed. Then > I looked to the Nvidia site for a new driver and downloaded and > installed the latest version - NVIDIA-Linux-x86_64-260.19.21.run. This > fixed both problems. KDE no longer crashes. The GLX module now loads. > The release notes for this new version state that it fixes a problem > where "multi-threaded applications" would sometimes crash. I have > notified the maintainers of the GoogleEarth and Amaya Slackbuilds on > this, but I thought that others may be experiencing similar problems > with other builds so I am posting this here. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > From chris.abela at maltats.com Mon Nov 22 16:54:02 2010 From: chris.abela at maltats.com (chris.abela at maltats.com) Date: Mon, 22 Nov 2010 16:54:02 +0000 Subject: [Slackbuilds-users] Nvidia driver update - for GoogleEarth andAmaya Builds, perhaps others In-Reply-To: <4CEA9959.2090803@acanac.net> References: <4CEA9959.2090803@acanac.net> Message-ID: <1945397115-1290444817-cardhu_decombobulator_blackberry.rim.net-10077689-@b16.c6.bise7.blackberry> Hi, My reply was based on my experience of the googleearth and nvidia Slackbuilds. I did not try the Amaya application and I never installed the nvidia from the source script so I cannot reply. Chris Powered by BlackBerry? from Vodafone -----Original Message----- From: Martin Pagnan Sender: slackbuilds-users-bounces at slackbuilds.org Date: Mon, 22 Nov 2010 11:24:57 To: SlackBuilds.org Users List Reply-To: "SlackBuilds.org Users List" Subject: Re: [Slackbuilds-users] Nvidia driver update - for GoogleEarth and Amaya Builds, perhaps others Chris, This is interesting. The GoogleEarth.SlackBuild that I used has the arch set as 486 and does a binary install. The Amaya.Slackbuild tests the architecture (and in my case chose 64bit) and compiles from source. The new Nvidia driver that I installed is apparently, from its name, for 64bit (like my old one). But now both Amaya and GoogleEarth work great and I did not install the 32bit Nvidia driver. I have installed multilib and read the recommendations. Could it be that Nvidia's new 64bit driver has a 32bit thunk built in? On 11/22/2010 05:14 AM, Chris Abela wrote: > On the other hand, if you originally only installed the 64bit driver > libraries for your Nvidia/Ati card, it is recommended after installation of > the multilib packages, to re-install the binary driver package. This time, > choose to install the 32bit driver files as well. > > The graphical 32bit applications that you are going to run on your multilib > installation will require these 32bit driver libraries. Crashes are likely > to occur if you fail to install the correct files." > > > > -----Original Message----- > From: slackbuilds-users-bounces at slackbuilds.org > [mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of Martin > Pagnan > Sent: 22 November 2010 04:35 > To: SlackBuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] Nvidia driver update - for GoogleEarth and > Amaya Builds, perhaps others > > Both GoogleEarth.Slackbuild and Amaya.Slackbuild failed for me in that > they both crashed KDE. After a long painstaking search I found a > recommendation to reinstall the Nvidia driver. Reinstalling my old > driver (version x86_64-256) did not fix the problem. The error log > indicated that the GLX module was not loaded - even though it was > specified in the xorg.conf file and the GLXmodules were installed. Then > I looked to the Nvidia site for a new driver and downloaded and > installed the latest version - NVIDIA-Linux-x86_64-260.19.21.run. This > fixed both problems. KDE no longer crashes. The GLX module now loads. > The release notes for this new version state that it fixes a problem > where "multi-threaded applications" would sometimes crash. I have > notified the maintainers of the GoogleEarth and Amaya Slackbuilds on > this, but I thought that others may be experiencing similar problems > with other builds so I am posting this here. > _______________________________________________ > 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/ > > > _______________________________________________ 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 joshuakwood at gmail.com Mon Nov 22 18:00:09 2010 From: joshuakwood at gmail.com (JK Wood) Date: Mon, 22 Nov 2010 12:00:09 -0600 Subject: [Slackbuilds-users] Nvidia driver update - for GoogleEarth andAmaya Builds, perhaps others In-Reply-To: <1945397115-1290444817-cardhu_decombobulator_blackberry.rim.net-10077689-@b16.c6.bise7.blackberry> References: <4CEA9959.2090803@acanac.net> <1945397115-1290444817-cardhu_decombobulator_blackberry.rim.net-10077689-@b16.c6.bise7.blackberry> Message-ID: On Mon, Nov 22, 2010 at 10:54 AM, wrote: > Hi, > > My reply was based on my experience of the googleearth and nvidia > Slackbuilds. I did not try the Amaya application and I never installed the > nvidia from the source script so I cannot reply. > > Chris > > Powered by BlackBerry? from Vodafone > > -----Original Message----- > From: Martin Pagnan > Sender: slackbuilds-users-bounces at slackbuilds.org > Date: Mon, 22 Nov 2010 11:24:57 > To: SlackBuilds.org Users List > Reply-To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Nvidia driver update - for GoogleEarth and > Amaya Builds, perhaps others > > Chris, > This is interesting. The GoogleEarth.SlackBuild that I used has the arch > set as 486 and does a binary install. The Amaya.Slackbuild tests the > architecture (and in my case chose 64bit) and compiles from source. The > new Nvidia driver that I installed is apparently, from its name, for > 64bit (like my old one). But now both Amaya and GoogleEarth work great > and I did not install the 32bit Nvidia driver. > > I have installed multilib and read the recommendations. Could it be that > Nvidia's new 64bit driver has a 32bit thunk built in? > > On 11/22/2010 05:14 AM, Chris Abela wrote: > > On the other hand, if you originally only installed the 64bit driver > > libraries for your Nvidia/Ati card, it is recommended after installation > of > > the multilib packages, to re-install the binary driver package. This > time, > > choose to install the 32bit driver files as well. > > > > The graphical 32bit applications that you are going to run on your > multilib > > installation will require these 32bit driver libraries. Crashes are > likely > > to occur if you fail to install the correct files." > > > > > > > > -----Original Message----- > > From: slackbuilds-users-bounces at slackbuilds.org > > [mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of Martin > > Pagnan > > Sent: 22 November 2010 04:35 > > To: SlackBuilds-users at slackbuilds.org > > Subject: [Slackbuilds-users] Nvidia driver update - for GoogleEarth and > > Amaya Builds, perhaps others > > > > Both GoogleEarth.Slackbuild and Amaya.Slackbuild failed for me in that > > they both crashed KDE. After a long painstaking search I found a > > recommendation to reinstall the Nvidia driver. Reinstalling my old > > driver (version x86_64-256) did not fix the problem. The error log > > indicated that the GLX module was not loaded - even though it was > > specified in the xorg.conf file and the GLXmodules were installed. Then > > I looked to the Nvidia site for a new driver and downloaded and > > installed the latest version - NVIDIA-Linux-x86_64-260.19.21.run. This > > fixed both problems. KDE no longer crashes. The GLX module now loads. > > The release notes for this new version state that it fixes a problem > > where "multi-threaded applications" would sometimes crash. I have > > notified the maintainers of the GoogleEarth and Amaya Slackbuilds on > > this, but I thought that others may be experiencing similar problems > > with other builds so I am posting this here. > > _______________________________________________ > > 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/ > > > > > > > _______________________________________________ > 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/ > > The 64-bit Nvidia driver comes with the option to install 32-bit compatibility libraries. There are actually two different packages available, one with and one without the compatibility libs. ftp://download.nvidia.com/XFree86/Linux-x86_64/260.19.21/NVIDIA-Linux-x86_64-260.19.21-no-compat32.run ftp://download.nvidia.com/XFree86/Linux-x86_64/260.19.21/NVIDIA-Linux-x86_64-260.19.21.run The no-compat32 is 20 megs smaller, and I'd imagine that would be the one used for the Slackbuild, since SBo doesn't officially support multilib. Alternatively, it's possible that it's running the driver installation script and answering "No" to the compat32 question. In any case, I suspect that's what's going on here. --JK -------------- next part -------------- An HTML attachment was scrubbed... URL: From michiel at slackbuilds.org Mon Nov 22 18:13:33 2010 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Mon, 22 Nov 2010 18:13:33 +0000 Subject: [Slackbuilds-users] perl-NetAddr-IP in pending In-Reply-To: <4CEA8FE0.5080007@mnspace.net> References: <4CEA8FE0.5080007@mnspace.net> Message-ID: <20101122181333.78a3b795@hades.esn.local> On Mon, 22 Nov 2010 09:44:32 -0600 Nishant Limbachia wrote: > Admins, > > Please remove this from pending. I'll submit a newer version later > today. Done, M. -- Michiel van Wessem http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From pprkut at slackbuilds.org Mon Nov 22 20:23:13 2010 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Mon, 22 Nov 2010 21:23:13 +0100 Subject: [Slackbuilds-users] Updates - 20101122.1 Message-ID: <201011222123.19358.pprkut@slackbuilds.org> Mon Nov 22 18:51:42 UTC 2010 academic/scipy: New Maintainer. academic/sympy: New Maintainer. audio/Pd-extended: Added (real-time audio processing). audio/cmus: Small script cleanups and new maintainer. audio/hydrogen: Updated for version 0.9.4.2. audio/milkytracker: Fixed homepage and download link audio/portmidi: Updated for version 217. audio/qmmp: Updated for version 0.4.3 audio/zynaddsubfx: Added (Software Synthesizer) desktop/cwp: Updated for version 1.3.0. desktop/enlightenment: Updated for version 0.16.999.52995. desktop/murrine: Updated for version 0.98.0. desktop/sound-theme-freedesktop: Added. (freedesktop sound theme) desktop/xfce4-volstatus-icon: Fixed download link in .info file development/acpica: Updated for version 20100915. development/eagle: Added. (schematic capture program) development/eclipse: Updated for version 3.6.1 development/geany: Fixed homepage link. development/gprolog: Fix typos in README development/gsoap: Updated for version 2.8.0. development/lua: Small script cleanups and new maintainer. development/numpy: New Maintainer. development/p4v: Updated for version 2010.1.265509. development/splint: New Maintainer. development/yasm: Updated for version 1.1.0. games/blobby2: Added (Blobby Volley 2 game) games/bsnes: Updated for version 0.072. games/scummvm: Added. (SCUMM game engine interpreter) games/zsnes: New Maintainer. graphics/luminance-hdr: Updated for version 2.0.1.1. libraries/agg: New Maintainer. libraries/cbase: New Maintainer. libraries/e_dbus: Updated for version 1.0.0.beta. libraries/ecore: Updated for version 1.0.0.beta. libraries/edje: Updated for version 1.0.0.beta. libraries/eet: Updated for version 1.4.0.beta. libraries/efreet: Updated for version 1.0.0.beta. libraries/eina: Updated for version 1.0.0.beta. libraries/embryo: Updated for version 1.0.0.beta. libraries/evas: Updated for version 1.0.0.beta. libraries/gnet: New Maintainer. libraries/gsnmp: New Maintainer. libraries/itcl: Added. (o-o programming contructs to Tcl) libraries/libcanberra: Updated README. libraries/libcap-ng: New Maintainer. libraries/libffado: Updated for version 2.0.1. libraries/libmms: Updated for version 0.6. libraries/liboop: New Maintainer. libraries/libtbb: New Maintainer. libraries/libtorrent: Updated for version 0.12.7. libraries/libxml++: Updated for version 2.32.0. libraries/matplotlib: Script fixes and new maintainer. libraries/perl-Authen-SASL: Added (SASL Authentication framework) libraries/perl-TermReadKey: Added. (module for terminal control) misc/chm2pdf: New Maintainer. misc/keychain: New Maintainer. misc/task: Fixed download URL multimedia/HandBrake: Adjust download location of mp4v2 multimedia/cinelerra: Updated for version cv_einar_701e5e5f multimedia/ffmpeg: Updated for version 0.6.1. multimedia/gecko-mediaplayer: Updated for version 1.0.0. multimedia/gnome-mplayer: Updated for version 1.0.0. multimedia/k9copy: Updated for version 2.3.6 multimedia/kdenlive: Updated for version 0.7.8 multimedia/mlt: Updated for version 0.5.10 multimedia/schroedinger: Updated for version 1.0.10 multimedia/x264: Updated for version 20101023. network/broadcom-sta: Updated for version 5.60.246.2. network/claws-mail-extra-plugins: Updated for version 3.7.7. network/claws-mail: Updated for version 3.7.7. network/dnstop: New Maintainer. network/dnstracer: New Maintainer. network/mod_chroot: New Maintainer. network/mod_evasive: New Maintainer. network/perl-IO-Socket-INET6: Updated for version 0.23. network/pptpd: fix pptpd-logwtmp.so loading on x86_64 network/rtorrent: Updated for version 0.8.7. network/transmission: Fixed/Removed old ARCH=${ARCH=i486} line. system/apachetop: New Maintainer. system/atop: New Maintainer. system/hddtemp: Fixed download link system/krusader: Patched for xz-support and new maintainer. system/ksh: Updated for version openbsd48. system/numlockx: Updated for version 1.2. New Maintainer. system/pdksh: Removed (use system/ksh instead) system/terminus-font: New Maintainer. system/vboxgtk: Updated for version 0.5.2. system/xen: Minor adjustments including updated dom0 scripts. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From bkirkp at gmail.com Mon Nov 22 22:10:51 2010 From: bkirkp at gmail.com (B Kirkpatrick) Date: Mon, 22 Nov 2010 16:10:51 -0600 Subject: [Slackbuilds-users] gramps package in pending Message-ID: <4CEAEA6B.7090504@gmail.com> A few days ago the GRAMPS project released a new version. Could someone please delete the one in the pending queue & I will then resubmit the newer one. Regards, Bill Kirkpatrick From asaf at lingnu.com Mon Nov 22 23:30:12 2010 From: asaf at lingnu.com (Asaf Ohaion) Date: Tue, 23 Nov 2010 01:30:12 +0200 (IST) Subject: [Slackbuilds-users] Releasing svn snapshot - Where to stroe tarball ? Message-ID: <39712.77.125.3.19.1290468612.squirrel@www.lingnu.com> Hello I want to create a package for svn snapshot (Created by me, not by the upstream maintainer), is it possible to store it on slackbuilds.org ? -- Asaf Ohaion Lingnu Open Source Consulting Ltd 09-7655871 (204), 0547-920828 http://www.lingnu.com From pc_warner at yahoo.com Tue Nov 23 00:04:57 2010 From: pc_warner at yahoo.com (Phillip Warner) Date: Mon, 22 Nov 2010 16:04:57 -0800 (PST) Subject: [Slackbuilds-users] Limewire and Frostwre In-Reply-To: Message-ID: <783510.16753.qm@web57703.mail.re3.yahoo.com> --- On Sun, 11/21/10, King Beowulf wrote: On the other hand Frostwire is still up and the current frostwire.slackbuild seems to repackage Frostwire-4.21-1 just fine and dandy.? The maintainer might want to consider a version bump. I'm still the maintainer for Frostwire, but I no longer have an interest in it. ?Feel free to update it and take over maintenance of it. ?Please just let the list know when an update is submitted. If nobody takes over maintenance of it, I will submit an update in a couple of weeks. --phillip -------------- next part -------------- An HTML attachment was scrubbed... URL: From mpagnan at acanac.net Tue Nov 23 00:30:50 2010 From: mpagnan at acanac.net (Martin Pagnan) Date: Mon, 22 Nov 2010 19:30:50 -0500 Subject: [Slackbuilds-users] Nvidia driver update - for GoogleEarth andAmaya Builds, perhaps others In-Reply-To: References: <4CEA9959.2090803@acanac.net> <1945397115-1290444817-cardhu_decombobulator_blackberry.rim.net-10077689-@b16.c6.bise7.blackberry> Message-ID: <4CEB0B3A.2000102@acanac.net> JK, A perfect explanation for what I experienced. On 11/22/2010 01:00 PM, JK Wood wrote: > > The 64-bit Nvidia driver comes with the option to install 32-bit > compatibility libraries. There are actually two different packages > available, one with and one without the compatibility libs. > ftp://download.nvidia.com/XFree86/Linux-x86_64/260.19.21/NVIDIA-Linux-x86_64-260.19.21-no-compat32.run > ftp://download.nvidia.com/XFree86/Linux-x86_64/260.19.21/NVIDIA-Linux-x86_64-260.19.21.run > > The no-compat32 is 20 megs smaller, and I'd imagine that would be the > one used for the Slackbuild, since SBo doesn't officially support > multilib. Alternatively, it's possible that it's running the driver > installation script and answering "No" to the compat32 question. In > any case, I suspect that's what's going on here. > > From crockabiscuit at yahoo.com Tue Nov 23 02:34:25 2010 From: crockabiscuit at yahoo.com (crocket) Date: Mon, 22 Nov 2010 18:34:25 -0800 (PST) Subject: [Slackbuilds-users] I want to resubmit lugaru. Message-ID: <21447.41027.qm@web120306.mail.ne1.yahoo.com> The slackbuild needs a modification. I need it to be removed from the pending queue. Seems like I'm doing resubmission a lot. I need to check thoroughly. From michiel at slackbuilds.org Tue Nov 23 07:07:45 2010 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Tue, 23 Nov 2010 07:07:45 +0000 Subject: [Slackbuilds-users] gramps package in pending In-Reply-To: <4CEAEA6B.7090504@gmail.com> References: <4CEAEA6B.7090504@gmail.com> Message-ID: <20101123070745.10762e10@hades.esn.local> On Mon, 22 Nov 2010 16:10:51 -0600 B Kirkpatrick wrote: > A few days ago the GRAMPS project released a new version. Could > someone please delete the one in the pending queue Done. -M. -- Michiel van Wessem http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From michiel at slackbuilds.org Tue Nov 23 07:08:57 2010 From: michiel at slackbuilds.org (Michiel van Wessem) Date: Tue, 23 Nov 2010 07:08:57 +0000 Subject: [Slackbuilds-users] I want to resubmit lugaru. In-Reply-To: <21447.41027.qm@web120306.mail.ne1.yahoo.com> References: <21447.41027.qm@web120306.mail.ne1.yahoo.com> Message-ID: <20101123070857.6878ac9c@hades.esn.local> On Mon, 22 Nov 2010 18:34:25 -0800 (PST) crocket wrote: > The slackbuild needs a modification. > I need it to be removed from the pending queue. > Seems like I'm doing resubmission a lot. Done. -- Michiel van Wessem http://slackbuilds.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From thomas at beingboiled.info Tue Nov 23 09:41:03 2010 From: thomas at beingboiled.info (Thomas Morper) Date: Tue, 23 Nov 2010 10:41:03 +0100 Subject: [Slackbuilds-users] Updates - 20101122.1 In-Reply-To: <201011222123.19358.pprkut@slackbuilds.org> References: <201011222123.19358.pprkut@slackbuilds.org> Message-ID: <20101123104103.0b729493@arktinen.local> On Mon, 22 Nov 2010 21:23:13 +0100 Heinz Wiesinger wrote: > network/broadcom-sta: Updated for version 5.60.246.2. This driver version has already been superseded by 5.60.246.6 and unfortunately the previous versions are no longer available for download. -- From dave at unrealize.co.uk Tue Nov 23 13:19:00 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Tue, 23 Nov 2010 13:19:00 +0000 Subject: [Slackbuilds-users] x264 - source link seems to be dead Message-ID: <20101123131900.GA28119@Junius> --2010-11-23 13:13:51-- ftp://ftp.videolan.org/pub/videolan/x264/snapshots/x264-snapshot-20101023-2245.tar.bz2 => `x264-snapshot-20101023-2245.tar.bz2' Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2 Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:21... failed: Connection refused. David -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From baildon.research at googlemail.com Tue Nov 23 13:21:51 2010 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 23 Nov 2010 13:21:51 +0000 Subject: [Slackbuilds-users] x264 - source link seems to be dead In-Reply-To: <20101123131900.GA28119@Junius> References: <20101123131900.GA28119@Junius> Message-ID: > ?ftp://ftp.videolan.org/pub/videolan/x264/snapshots/x264-snapshot-20101023-2245.tar.bz2 > ? ? ? ? ? => `x264-snapshot-20101023-2245.tar.bz2' > Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2 > Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:21... > failed: Connection refused. If you replace ftp:// by http:// it'll work. Also there's a slight problem with ARCH if you want x86_64 ;-) -D. From pprkut at slackbuilds.org Tue Nov 23 20:50:35 2010 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Tue, 23 Nov 2010 21:50:35 +0100 Subject: [Slackbuilds-users] x264 - source link seems to be dead In-Reply-To: References: <20101123131900.GA28119@Junius> Message-ID: <201011232150.40715.pprkut@slackbuilds.org> On Tuesday 23 November 2010 14:21:51 David Spencer wrote: > > ftp://ftp.videolan.org/pub/videolan/x264/snapshots/x264-snapshot-2010102 > > 3-2245.tar.bz2 => `x264-snapshot-20101023-2245.tar.bz2' > > Resolving ftp.videolan.org (ftp.videolan.org)... 88.191.250.2 > > Connecting to ftp.videolan.org (ftp.videolan.org)|88.191.250.2|:21... > > failed: Connection refused. > > If you replace ftp:// by http:// it'll work. > > Also there's a slight problem with ARCH if you want x86_64 ;-) Fixed in my branch. Should be out with the next push of updates. Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From pprkut at slackbuilds.org Tue Nov 23 20:51:33 2010 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Tue, 23 Nov 2010 21:51:33 +0100 Subject: [Slackbuilds-users] remmina download link In-Reply-To: References: Message-ID: <201011232151.33436.pprkut@slackbuilds.org> On Thursday 18 November 2010 12:21:12 Niels Horn wrote: > On Thu, Nov 18, 2010 at 9:13 AM, Niels Horn wrote: > > Not sure if this was already mentioned before, but the download link > > for remmina is not working. > > > > The link on SBo is: > > http://downloads.sourceforge.net/project/remmina/0.8/remmina-0.8.0.tar.gz > > > > One that works is: > > http://downloads.sourceforge.net/remmina/remmina-0.8.0.tar.gz > > Ah, and the same goes for remmina-plugins... Just remove the "project" > and "0.8" parts from the path... Both fixed in my branch. Should be out with the next push of updates. Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From pprkut at slackbuilds.org Tue Nov 23 20:52:13 2010 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Tue, 23 Nov 2010 21:52:13 +0100 Subject: [Slackbuilds-users] audacity typo fix In-Reply-To: References: Message-ID: <201011232152.15684.pprkut@slackbuilds.org> On Thursday 18 November 2010 00:53:13 Andrew Antle wrote: > Small typo fix. Diff attached. > > > $ diff -u audacity.SlackBuild.orig audacity.SlackBuild > --- audacity.SlackBuild.orig 2010-11-17 18:49:20.386716894 -0500 > +++ audacity.SlackBuild 2010-11-17 18:49:46.109738092 -0500 > @@ -121,7 +121,7 @@ > install -D -m 0644 images/AudacityLogo48x48.xpm \ > $PKG/usr/share/pixmaps/audacity.xpm > > -# Move manpage directory to proper loacation; pages are gzipped already > +# Move manpage directory to proper location; pages are gzipped already > mv $PKG/usr/share/man $PKG/usr > > mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION Included in my branch. Should be part of the next update. Thanks! Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From pprkut at slackbuilds.org Tue Nov 23 20:53:31 2010 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Tue, 23 Nov 2010 21:53:31 +0100 Subject: [Slackbuilds-users] Maintenance In-Reply-To: References: Message-ID: <201011232153.31855.pprkut@slackbuilds.org> On Sunday 14 November 2010 21:38:39 Diogo Leal wrote: > I would assume the maintenance of these packages: > > gst-gnome-vfs > exaile > > How should I proceed? Sorry for the delay on this. Same as before, please submit them with changed maintainer information. Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From artourter at gmail.com Wed Nov 24 01:17:09 2010 From: artourter at gmail.com (Greg' Ar Tourter) Date: Wed, 24 Nov 2010 01:17:09 +0000 Subject: [Slackbuilds-users] QtCurve-* in pending Message-ID: Hi, My turn to request the removal of packages in pending. Can the QtCurve packages in pending be removed. I will submit a newer version for both of them which fixes some ugly bugs. Thanks Greg From mjjzf at syntaktisk.dk Wed Nov 24 07:55:56 2010 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Wed, 24 Nov 2010 02:55:56 -0500 Subject: [Slackbuilds-users] Pending Message-ID: <20101124025556.3cbb4134@espero.syntaktisk.dk> Dear Slackbuilders, Would you like us to hold back on submitting SBs for now, until the queue is cleared? I can see that quite a few are accumulating. Yours, Morten __ Morten Juhl-Johansen Z?lde-Fej?r mjjzf at syntaktisk.dk * www.syntaktisk.dk From the_emmel at gmx.net Wed Nov 24 16:28:56 2010 From: the_emmel at gmx.net (emmel) Date: Wed, 24 Nov 2010 17:28:56 +0100 Subject: [Slackbuilds-users] Xen on x86_64 Message-ID: <20101124162856.GA3100@pollux.mlnet> So I tried building Xen and it failed. Obviously it sets the build flags "-m32 -march=i686" even though I'm running on Slack64. Am I missing something here? The build script does have the usual arch bits from the template, so the arch should be set correctly, but the output says otherwise. Help? Note: This message has been sent to the SlackBuild users list and the maintainer. Any help is welcome, though. -- GPG signed Fingerprint: 60B4 D8E3 9617 900C 6726 168F D677 5AAD D40F CCE7 Certserver : hkp://pgp.mit.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From mario at slackverse.org Wed Nov 24 16:45:21 2010 From: mario at slackverse.org (mario) Date: Wed, 24 Nov 2010 17:45:21 +0100 Subject: [Slackbuilds-users] Xen on x86_64 In-Reply-To: <20101124162856.GA3100@pollux.mlnet> References: <20101124162856.GA3100@pollux.mlnet> Message-ID: <4CED4121.7080708@slackverse.org> And you are running 13.0 / 13.1 or -current? On 11/24/2010 05:28 PM, emmel wrote: > So I tried building Xen and it failed. Obviously it sets the build flags > "-m32 -march=i686" even though I'm running on Slack64. Am I missing > something here? > The build script does have the usual arch bits from the template, so the > arch should be set correctly, but the output says otherwise. Help? > > Note: This message has been sent to the SlackBuild users list and the > maintainer. Any help is welcome, though. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Wed Nov 24 23:37:09 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 24 Nov 2010 17:37:09 -0600 Subject: [Slackbuilds-users] QtCurve-* in pending In-Reply-To: References: Message-ID: <20101124173709.0d356566@liberty> On Wed, 24 Nov 2010 01:17:09 +0000 "Greg' Ar Tourter" wrote: > My turn to request the removal of packages in pending. Can the QtCurve > packages in pending be removed. I will submit a newer version for > both of them which fixes some ugly bugs. 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 binhnguyen at fastmail.fm Thu Nov 25 15:22:38 2010 From: binhnguyen at fastmail.fm (Binh Nguyen) Date: Thu, 25 Nov 2010 22:22:38 +0700 Subject: [Slackbuilds-users] Updates - 20101122.1 In-Reply-To: <201011222123.19358.pprkut@slackbuilds.org> References: <201011222123.19358.pprkut@slackbuilds.org> Message-ID: <20101125222238.2b895abd@darkstar.example.net> On Mon, 22 Nov 2010 21:23:13 +0100 Heinz Wiesinger wrote: > Mon Nov 22 18:51:42 UTC 2010 > development/geany: Fixed homepage link. The old Homepage is already on web interface: http://slackbuilds.org/repository/13.1/development/geany/ -- Binh Nguyen From rworkman at slackbuilds.org Thu Nov 25 16:09:15 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 25 Nov 2010 10:09:15 -0600 Subject: [Slackbuilds-users] Limewire and Frostwre In-Reply-To: References: Message-ID: <20101125100915.4603191a@liberty> On Sun, 21 Nov 2010 14:16:34 -0800 King Beowulf wrote: > Limewire seems down for the count. The current download link is dead > and the main site is "on hold" due to a court ordered injunction. So > we may when to pull Limewire from the repository. > > On the other hand Frostwire is still up and the current > frostwire.slackbuild seems to repackage Frostwire-4.21-1 just fine > and dandy. The maintainer might want to consider a version bump. LimeWire will be removed from the repo in our next update, but I'm not going to be taking over Frostwire (see Phillip's response in this thread), so someone else will want to do that. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From binhnguyen at fastmail.fm Thu Nov 25 17:19:06 2010 From: binhnguyen at fastmail.fm (Binh Nguyen) Date: Fri, 26 Nov 2010 00:19:06 +0700 Subject: [Slackbuilds-users] TuxPaint dependencies Message-ID: <20101126001906.3864c362@darkstar.example.net> Hi, In tuxpaint's README, librsvg is mentioned as an optional dependency, but it's an official Slackware package. Regards, -- Binh Nguyen From rworkman at slackbuilds.org Thu Nov 25 21:32:23 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 25 Nov 2010 15:32:23 -0600 Subject: [Slackbuilds-users] TuxPaint dependencies In-Reply-To: <20101126001906.3864c362@darkstar.example.net> References: <20101126001906.3864c362@darkstar.example.net> Message-ID: <20101125153223.11bbf58b@liberty> On Fri, 26 Nov 2010 00:19:06 +0700 Binh Nguyen wrote: > In tuxpaint's README, librsvg is mentioned as an optional dependency, > but it's an official Slackware package. Fixed in my 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 Thu Nov 25 21:33:56 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 25 Nov 2010 15:33:56 -0600 Subject: [Slackbuilds-users] Updates - 20101122.1 In-Reply-To: <20101125222238.2b895abd@darkstar.example.net> References: <201011222123.19358.pprkut@slackbuilds.org> <20101125222238.2b895abd@darkstar.example.net> Message-ID: <20101125153356.38619c32@liberty> On Thu, 25 Nov 2010 22:22:38 +0700 Binh Nguyen wrote: > On Mon, 22 Nov 2010 21:23:13 +0100 > Heinz Wiesinger wrote: > > > Mon Nov 22 18:51:42 UTC 2010 > > > development/geany: Fixed homepage link. > > The old Homepage is already on web interface: > > http://slackbuilds.org/repository/13.1/development/geany/ Fixed; 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 Thu Nov 25 21:35:01 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 25 Nov 2010 15:35:01 -0600 Subject: [Slackbuilds-users] Maintenance of orphans In-Reply-To: References: Message-ID: <20101125153501.5f77e00e@liberty> On Sun, 14 Nov 2010 16:43:47 -0500 Matthew Fillpot wrote: > With the recent rash of maintainers giving up their builds, I would > like to request for the3 admins to add a list on the website of > orphaned slackbuild scripts. This will make it easier for current and > potential maintainers to view a complete list of available builds that > need to switch hands. > I currently have a list of all orphaned builds that were announced in > the last month and would gladly pass it onto the site to start the > list. > > In addition would it be possible to add a section to the site were > people can request for builds to be made of known apps, so the > maintainers can also review that list for future projects? We'e got enough to do already :) If someone wants to maintain such a list, feel free to do so (and to periodically/as needed provide a link on this list). -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 Thu Nov 25 21:50:44 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 25 Nov 2010 15:50:44 -0600 Subject: [Slackbuilds-users] Submitted SlackBuild for yad then realised not best download link In-Reply-To: <002201cb75ae$2156d850$0f02000a@cw8xp> References: <002201cb75ae$2156d850$0f02000a@cw8xp> Message-ID: <20101125155044.05fa469d@liberty> On Wed, 27 Oct 2010 13:38:20 +0530 wrote: > I just submitted a SlackBuild for yad then realised the download link > in yad.info is not the simplest. Resubmission is not possible because > yad.tar.gz is already in the pending queue. > > It should be > DOWNLOAD="http://yad.googlecode.com/files/yad-0.5.2.tar.xz" The README appeared to be for the wrong app too, so I just deleted the whole thing - you can resubmit now :-) -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 Thu Nov 25 21:53:01 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 25 Nov 2010 15:53:01 -0600 Subject: [Slackbuilds-users] category correction for "argus" In-Reply-To: <20101027180038.GM12118@akamai.com> References: <20101027180038.GM12118@akamai.com> Message-ID: <20101125155301.4ae8aa5a@liberty> On Wed, 27 Oct 2010 14:00:38 -0400 "R. Andrew Bailey" wrote: > I noticed a moment ago that the "argus" Slackbuild is presently in the > "development" category in Slackbuilds. This was almost certainly a > result of my accidentally selecting that in the box. The correct > category is "network", along with its sister package "argus-clients". I just moved both of them in my branch, so they'll be correct in the next update. -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 Thu Nov 25 21:57:57 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 25 Nov 2010 13:57:57 -0800 Subject: [Slackbuilds-users] Limewire and Frostwre In-Reply-To: <20101125100915.4603191a@liberty> References: <20101125100915.4603191a@liberty> Message-ID: > > I'm not going to be taking over Frostwire (see Phillip's response > in this thread), so someone else will want to do that. > > I guess this as good as any a time to stop sponging off the Slackware Community. I can take over as maintainer of Frostwire. I'll review the submission stuff and bundle it all up this weekend sometime when I get a chance to hide out from all the visiting relatives. Happy Thanksgiving! -Ed -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Thu Nov 25 22:36:24 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 25 Nov 2010 14:36:24 -0800 Subject: [Slackbuilds-users] Limewire and Frostwre In-Reply-To: <783510.16753.qm@web57703.mail.re3.yahoo.com> References: <783510.16753.qm@web57703.mail.re3.yahoo.com> Message-ID: I just submitted the updated slackbuild stuff. If its okey dokey with Philip, I'll take over as the Frostwire maintainer. -Ed On Mon, Nov 22, 2010 at 4:04 PM, Phillip Warner wrote: > --- On *Sun, 11/21/10, King Beowulf * wrote: > > On the other hand Frostwire is still up and the current > frostwire.slackbuild seems to repackage Frostwire-4.21-1 just fine and > dandy. The maintainer might want to consider a version bump. > > I'm still the maintainer for Frostwire, but I no longer have an interest in > it. Feel free to update it and take over maintenance of it. Please just > let the list know when an update is submitted. > > If nobody takes over maintenance of it, I will submit an update in a couple > of weeks. > > --phillip > > > _______________________________________________ > 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/ > > > -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Thu Nov 25 22:48:24 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 25 Nov 2010 16:48:24 -0600 Subject: [Slackbuilds-users] Sonata lyric fetching failed In-Reply-To: <20101106132816.5f41c5f4@darkstar.example.net> References: <20101106132816.5f41c5f4@darkstar.example.net> Message-ID: <20101125164824.07a6769f@liberty> On Sat, 6 Nov 2010 13:28:16 +0700 Binh Nguyen wrote: > I just noticed that sonata didn't fetch lyrics anymore. So I looked > around and found that it uses lyricwiki.org for the purpose. And since > the lyric site has been moved to lyrics.wikia.com, it leads to > non-functional lyric module. > > The file in source that bears lyric funtion is sonata/info.py. So > while waiting for the sonata next version, a simple line can be added > to sonata.SlackBuild (just before 'python setup.py install ... ') to > solve this issue: > > sed -i "s#lyricwiki.org#lyrics.wikia.org#g" sonata/info.py I just committed this to my branch, so I hope it's correct (and okay with maintainer - Andrew?) :-) -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 Thu Nov 25 22:50:50 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 25 Nov 2010 16:50:50 -0600 Subject: [Slackbuilds-users] Invalid link on perl-Magick In-Reply-To: References: Message-ID: <20101125165050.4b8e5316@liberty> On Mon, 1 Nov 2010 22:21:08 +0700 Willy Sudiarto Raharjo wrote: > The source on > http://slackbuilds.org/repository/13.1/libraries/perl-Magick/ is > invalid the source has been upgraded to 6.59, but the SBo still link > to 6.59 > ftp://ftp.carnet.hr/mirrors/misc/imagemagick/perl/PerlMagick-6.59.tar.gz I don't understand - everything looks consistent with respect to what's in our repo. If the issue is that the source tarball is no longer available, and thus the version needs to be upgraded, then mail the maintainer about that. -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 Thu Nov 25 23:42:54 2010 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Fri, 26 Nov 2010 06:42:54 +0700 Subject: [Slackbuilds-users] Invalid link on perl-Magick In-Reply-To: <20101125165050.4b8e5316@liberty> References: <20101125165050.4b8e5316@liberty> Message-ID: >> The source on >> http://slackbuilds.org/repository/13.1/libraries/perl-Magick/ is >> invalid the source has been upgraded to 6.59, but the SBo still link >> to 6.59 >> ftp://ftp.carnet.hr/mirrors/misc/imagemagick/perl/PerlMagick-6.59.tar.gz > > > I don't understand - everything looks consistent with respect > to what's in our repo. ?If the issue is that the source tarball > is no longer available, and thus the version needs to be upgraded, > then mail the maintainer about that. What i mean is that the source is no longer exist, ie. broken link the source has been updated to 6.59, but the SlackBuild script is still pointing to 6.53, so people will not be able to get the source -- Willy Sudiarto Raharjo Registered Linux User : 336579 Web : http://www.informatix.or.id/willy Blog : http://willysr.blogspot.com http://slackblogs.blogspot.com From rworkman at slackbuilds.org Fri Nov 26 01:57:43 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 25 Nov 2010 19:57:43 -0600 Subject: [Slackbuilds-users] Invalid link on perl-Magick In-Reply-To: References: <20101125165050.4b8e5316@liberty> Message-ID: <20101125195743.551bbb1d@liberty> On Fri, 26 Nov 2010 06:42:54 +0700 Willy Sudiarto Raharjo wrote: > >> The source on > >> http://slackbuilds.org/repository/13.1/libraries/perl-Magick/ is > >> invalid the source has been upgraded to 6.59, but the SBo still > >> link to 6.59 > >> ftp://ftp.carnet.hr/mirrors/misc/imagemagick/perl/PerlMagick-6.59.tar.gz > > > > > > I don't understand - everything looks consistent with respect > > to what's in our repo. ?If the issue is that the source tarball > > is no longer available, and thus the version needs to be upgraded, > > then mail the maintainer about that. > > What i mean is that the source is no longer exist, ie. broken link > > the source has been updated to 6.59, but the SlackBuild script is > still pointing to 6.53, so people will not be able to get the source Ah, okay. Yeah, that definitely needs the maintainer's attention then - he/she should submit an update to us. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From abrouwers at gmail.com Fri Nov 26 00:16:58 2010 From: abrouwers at gmail.com (Andrew Brouwers) Date: Thu, 25 Nov 2010 19:16:58 -0500 Subject: [Slackbuilds-users] Sonata lyric fetching failed In-Reply-To: <20101125164824.07a6769f@liberty> References: <20101106132816.5f41c5f4@darkstar.example.net> <20101125164824.07a6769f@liberty> Message-ID: > > I just committed this to my branch, so I hope it's correct > (and okay with maintainer - Andrew?) ?:-) > > -RW > Sounds great - I tried it out with the last bump of mpd, and it worked as described - thanks for saving me a submission :) From pc_warner at yahoo.com Sun Nov 28 00:01:25 2010 From: pc_warner at yahoo.com (Phillip Warner) Date: Sat, 27 Nov 2010 16:01:25 -0800 (PST) Subject: [Slackbuilds-users] Limewire and Frostwre In-Reply-To: Message-ID: <507956.6555.qm@web57706.mail.re3.yahoo.com> Sounds good! ?Have fun with it! --phillip --- On Thu, 11/25/10, King Beowulf wrote: From: King Beowulf Subject: Re: [Slackbuilds-users] Limewire and Frostwre To: "SlackBuilds.org Users List" Date: Thursday, November 25, 2010, 2:36 PM I just submitted the updated slackbuild stuff.? If its okey dokey with Philip, I'll take over as the Frostwire maintainer. -Ed On Mon, Nov 22, 2010 at 4:04 PM, Phillip Warner wrote: --- On Sun, 11/21/10, King Beowulf wrote: On the other hand Frostwire is still up and the current frostwire.slackbuild seems to repackage Frostwire-4.21-1 just fine and dandy.? The maintainer might want to consider a version bump. I'm still the maintainer for Frostwire, but I no longer have an interest in it. ?Feel free to update it and take over maintenance of it. ?Please just let the list know when an update is submitted. If nobody takes over maintenance of it, I will submit an update in a couple of weeks. --phillip _______________________________________________ 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/ -- You! What PLANET is this! ? ? -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -----Inline Attachment Follows----- _______________________________________________ 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 matteo.bernardini at gmail.com Sun Nov 28 09:57:17 2010 From: matteo.bernardini at gmail.com (ponce) Date: Sun, 28 Nov 2010 10:57:17 +0100 Subject: [Slackbuilds-users] email address change Message-ID: <4CF2277D.5020308@gmail.com> I have changed my primary mail address from matteo.bernardini at sns.it to matteo.bernardini at gmail.com. If possible, the slackbuilds I submitted should be adapted to reflectit: I prepared a commit with the diffs interested https://github.com/Ponce/slackbuilds/commit/db066b367bcafda9d7c2c7963187d8f76d9f1f88 thanks in advance :) Matteo From pprkut at slackbuilds.org Mon Nov 29 12:32:42 2010 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Mon, 29 Nov 2010 13:32:42 +0100 Subject: [Slackbuilds-users] Updates - 20101129.1 Message-ID: <201011291332.49172.pprkut@slackbuilds.org> Mon Nov 29 11:55:05 UTC 2010 audio/audacity: Correct typo in SlackBuild audio/clementine: Updated for version 0.5.3 audio/mpd: Updated for version 0.15.15. audio/portmidi: removed leftover patch audio/rhythmbox: Added (music library management application) audio/sonata: Fix fetching of lyrics desktop/cwp: Updated for version 1.3.1. desktop/vbox-runner: Added (kde plugin for vbox) desktop/yad: Added (Yet Another Dialog display utility) development/generatorrunner: Added. (Binding generator controller) development/pyside-tools: Added. (Tools for the PySide Bindings) development/shiboken: Added. (PySide bindings generator plugin) games/Chatbot-Eliza: New Maintainer. games/bsnes: Deleted stale patch file games/hex-a-hop: Added. (hexagonal tile-based puzzle game) graphics/darktable: Updated for version 0.7. graphics/tuxpaint: Fixed dep info in README. libraries/efreet: Fix approver information libraries/gnome-media: Added (media utilities for GNOME) libraries/gnome-python-desktop: Added (python modules for GNOME) libraries/gnome-sharp: Updated for version 2.24.2. libraries/iniparser: Added (stand-alone INI file parsing library) libraries/libmemcached: Updated for version 0.44 libraries/libmirage: Updated for version 1.3.0 and new maintainer libraries/libsndfile: Updated for version 1.0.23 libraries/log4c: Added (C library for flexible logging to files) libraries/pyside: Added. (LGPL python bindings for Qt) libraries/totem-pl-parser: Added (totem playlist parser) misc/gramps: Updated for version 3.2.4. misc/krename: Updated for version 4.0.5. multimedia/mediainfo-gui: Added (GUI for mediainfo) multimedia/mediainfo: Added (supplies media information) multimedia/x264: Fix ARCH detection and download link network/LimeWire: Removed due to lack of maintenance. network/argus{-clients}: Moved (back) from Development category. network/claws-mail: Create the system-wide theme directory in pkg network/csync: Added (file synchronizer) network/filezilla: Updated for version 3.3.5.1. network/frostwire: Updated for version 4.21.1. network/httping: Updated for version 1.4.4. network/phpmyadmin: Updated for version 3.3.8. network/remmina-plugins: Updated for version 0.8.4 network/remmina: Updated for version 0.8.3 network/shorewall6: Updated for version 4.4.14. network/shorewall: Updated for version 4.4.14. network/webalizer: Added (web server log file analysis program) network/wireshark: Updated for version 1.4.2 network/xinetd: Added (inetd replacement) network/znc: Updated for version 0.096. office/kmymoney: Updated for version 4.5.1. office/libreoffice-langpack: Added (language packs for LO) office/libreoffice: Updated for version 3.3.0_beta3. office/tellico: Updated for version 2.3.1 system/bootchart: New Maintainer. system/cdemu-client: Added. (command-line client for CDEmu-daemon) system/cdemu-daemon: Updated for version 1.3.0 and new maintainer system/cdemu-tray: Added. (cdemu client) system/dash: Updated for version 0.5.6.1. system/rxvt-unicode: Updated for verson 9.09. system/tmux: Updated for version 1.3 system/ttf-ubuntu-font-family: Added (sans-serif typeface) system/vhba-module: Updated for version 20100822 and new maintainer system/virtualbox-kernel-addons: Updated for version 3.2.10. system/virtualbox-kernel: Updated for version 3.2.10. system/virtualbox-ose-addons: Updated for version 3.2.10. system/virtualbox-ose: Updated for version 3.2.10. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From binhnguyen at fastmail.fm Mon Nov 29 13:53:06 2010 From: binhnguyen at fastmail.fm (Binh Nguyen) Date: Mon, 29 Nov 2010 20:53:06 +0700 Subject: [Slackbuilds-users] Updates - 20101129.1 In-Reply-To: <201011291332.49172.pprkut@slackbuilds.org> References: <201011291332.49172.pprkut@slackbuilds.org> Message-ID: <20101129205307.5bf4af66@darkstar.example.net> On Mon, 29 Nov 2010 13:32:42 +0100 Heinz Wiesinger wrote: > Mon Nov 29 11:55:05 UTC 2010 > network/webalizer: Added (web server log file analysis program) There's a typo in webalizer.SlackBuild. It says: "# Slackware build script for HTTPing" -- Binh Nguyen From miorimmax at gmail.com Mon Nov 29 14:48:14 2010 From: miorimmax at gmail.com (Max Miorim) Date: Mon, 29 Nov 2010 12:48:14 -0200 Subject: [Slackbuilds-users] nginx and pigz: New maintainer Message-ID: Hi, I'm not maintaining nginx and pigz anymore, Diogo Leal is taking over. -- Max From banderols at gmail.com Mon Nov 29 20:47:26 2010 From: banderols at gmail.com (Murat D. Kadirov) Date: Tue, 30 Nov 2010 01:47:26 +0500 Subject: [Slackbuilds-users] Updates - 20101129.1 In-Reply-To: <201011291332.49172.pprkut@slackbuilds.org> References: <201011291332.49172.pprkut@slackbuilds.org> Message-ID: <20101129204726.GA26490@darkstar> On Mon, Nov 29, 2010 at 01:32:42PM +0100, Heinz Wiesinger wrote: > office/libreoffice-langpack: Added (language packs for LO) Typo in README (web-page). URI to languagepack point to beta2 (should be beta3). -- Murat D. Kadirov PGP fingerprint: 3081 EBFA 5CB9 BD24 4DB6 76EE 1B97 0A0E CEC0 6AA0 From niels.horn at gmail.com Mon Nov 29 21:30:06 2010 From: niels.horn at gmail.com (Niels Horn) Date: Mon, 29 Nov 2010 19:30:06 -0200 Subject: [Slackbuilds-users] Updates - 20101129.1 In-Reply-To: <20101129204726.GA26490@darkstar> References: <201011291332.49172.pprkut@slackbuilds.org> <20101129204726.GA26490@darkstar> Message-ID: On Mon, Nov 29, 2010 at 6:47 PM, Murat D. Kadirov wrote: > On Mon, Nov 29, 2010 at 01:32:42PM +0100, Heinz Wiesinger wrote: >> office/libreoffice-langpack: Added (language packs for LO) > > Typo in README (web-page). URI to languagepack point to beta2 (should be > beta3). > > -- > Murat D. Kadirov > PGP fingerprint: 3081 EBFA 5CB9 BD24 4DB6 ?76EE 1B97 0A0E CEC0 6AA0 Yes, you're completely right, I forgot to check the README before submitting... Can an admin change this or do I need to resubmit? Niels From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Mon Nov 29 21:33:10 2010 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Mon, 29 Nov 2010 22:33:10 +0100 Subject: [Slackbuilds-users] dvdrip In-Reply-To: <201011291332.49172.pprkut@slackbuilds.org> References: <201011291332.49172.pprkut@slackbuilds.org> Message-ID: <4CF41C16.80209@skmail.ikp.physik.tu-darmstadt.de> Hello, I installed dvdrip on one of my machines which still runs Slackware 13.0(*) and had to manually install Gtk2::Ex::FormFactory and Event::ExecFlow from CPAN for it to work. I thought that I missed something, but searching through the hole mailing list did not provide me with any hint and the two missing perl modules seem not to be provided on Slackbuilds.org and are not mentioned in the README. I did not have time to test the installation on a 13.1 box, but since the README didn't change much ... Best regards, Serban Udrea (*) Using just slackbuilds for 13.0 From kingbeowulf at gmail.com Tue Nov 30 07:14:47 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 29 Nov 2010 23:14:47 -0800 Subject: [Slackbuilds-users] dvdrip In-Reply-To: <4CF41C16.80209@skmail.ikp.physik.tu-darmstadt.de> References: <201011291332.49172.pprkut@slackbuilds.org> <4CF41C16.80209@skmail.ikp.physik.tu-darmstadt.de> Message-ID: I had it running on 13.0 but don't remember the dependency list - it was my own slackbuild adapted from SLAMD64. The dvdrip site has a table of which perl modules are required to compile, which to run, and which are optional run time deps. My issue a few days ago was that my dvdrip install runs, but fails to read the DVD TOC after the last big update cycle (kernel patch I think). It worked fine earlier. k9copy still works ok. I really out to start writing this stuff down.... -Ed -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozan.turkyilmaz at gmail.com Tue Nov 30 11:44:04 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Tue, 30 Nov 2010 13:44:04 +0200 Subject: [Slackbuilds-users] prelink WARNING Message-ID: non-prelinked binaries may cause SEGFAULT in prelinked systems. I noticed it today when I followed segfault to prelink. I'm submiting a updated README now. Later I'll send in a updated submission with one new script for prelinking all the system. -- Ozan, BSc, BEng -------------- next part -------------- A non-text attachment was scrubbed... Name: README Type: application/octet-stream Size: 1039 bytes Desc: not available URL: From estranho at diogoleal.com Tue Nov 30 12:32:39 2010 From: estranho at diogoleal.com (Diogo Leal) Date: Tue, 30 Nov 2010 10:32:39 -0200 Subject: [Slackbuilds-users] nginx and pigz: New maintainer In-Reply-To: References: Message-ID: Hello, Soon, I will be updating the version of ngnix. Diogo Leal [aka estranho] http://diogoleal.com msn | gtalk: estranho at diogoleal.com On Mon, Nov 29, 2010 at 12:48 PM, Max Miorim wrote: > Hi, > > I'm not maintaining nginx and pigz anymore, Diogo Leal is taking over. > > > -- Max > _______________________________________________ > 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 mfilpot at gmail.com Tue Nov 30 18:22:57 2010 From: mfilpot at gmail.com (Matthew Fillpot) Date: Tue, 30 Nov 2010 13:22:57 -0500 Subject: [Slackbuilds-users] Maintenance of orphans In-Reply-To: <20101125153501.5f77e00e@liberty> References: <20101125153501.5f77e00e@liberty> Message-ID: On Thu, Nov 25, 2010 at 4:35 PM, Robby Workman wrote: > On Sun, 14 Nov 2010 16:43:47 -0500 > Matthew Fillpot wrote: > >> With the recent rash of maintainers giving up their builds, I would >> like to request for the3 admins to add a list on the website of >> orphaned slackbuild scripts. This will make it easier for current and >> potential maintainers to view a complete list of available builds that >> need to switch hands. >> I currently have a list of all orphaned builds that were announced in >> the last month and would gladly pass it onto the site to start the >> list. >> >> In addition would it be possible to add a section to the site were >> people can request for builds to be made of known apps, so the >> maintainers can also review that list for future projects? > > > We'e got enough to do already :) ?If someone wants to maintain > such a list, feel free to do so (and to periodically/as needed > provide a link on this list). > > -RW > Thanks for looking over the idea Robby. I have found an individual who will volunteer some server space to accomidate this list which I will maintain. For those that are interested: What fields should we require a user to fill in when submitting a request for a new build so that it will give enough info for packagers to quickly determine their interest? At the very least I was thinking App Category, App Name, Link to Homepage and a Short description. I plan to pull similar data from orphaned builds to allow the two lists to be merged as one, so please try not to ask for too much. -- -Thank You, -Matthew Fillpot From ozan.turkyilmaz at gmail.com Tue Nov 30 19:12:37 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Tue, 30 Nov 2010 21:12:37 +0200 Subject: [Slackbuilds-users] Maintenance of orphans In-Reply-To: References: <20101125153501.5f77e00e@liberty> Message-ID: 2010/11/30 Matthew Fillpot : > On Thu, Nov 25, 2010 at 4:35 PM, Robby Workman wrote: > For those that are interested: > What fields should we require a user to fill in when submitting a > request for a new build so that it will give enough info for packagers > to quickly determine their interest? At the very least I was thinking > App Category, App Name, Link to Homepage and a Short description. > License? -- Ozan, BSc, BEng From slakmagik at gmail.com Tue Nov 30 20:28:15 2010 From: slakmagik at gmail.com (slakmagik) Date: Tue, 30 Nov 2010 15:28:15 -0500 Subject: [Slackbuilds-users] Maintenance of orphans In-Reply-To: References: <20101125153501.5f77e00e@liberty> Message-ID: <20101130202815.GA3944@devbox> On 2010-11-30 (Tue) 13:22:57 [-0500], Matthew Fillpot wrote: > > For those that are interested: > What fields should we require a user to fill in when submitting a > request for a new build so that it will give enough info for packagers > to quickly determine their interest? At the very least I was thinking > App Category, App Name, Link to Homepage and a Short description. > Some information on language/build system and possibly known deps might be useful. All probably extractable from the homepage (or general site) but it might be good to have those as clear fields. It would be good to know if something was written in C using autotools with no deps or if it were written in brainfuck and uses zmake++ and depends on gconf. From kingbeowulf at gmail.com Tue Nov 30 22:34:35 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 30 Nov 2010 14:34:35 -0800 Subject: [Slackbuilds-users] Maintenance of orphans In-Reply-To: <20101130202815.GA3944@devbox> References: <20101125153501.5f77e00e@liberty> <20101130202815.GA3944@devbox> Message-ID: I think simple is better. Name, project site, lang/arch, brief description would be enough. Anyone interested in picking up the maintainership can go look up deps and more (and should anyway since projects can change). Some of the info will be in old slackbuilds for the previous slackware versions as well. On 11/30/10, slakmagik wrote: > On 2010-11-30 (Tue) 13:22:57 [-0500], Matthew Fillpot wrote: >> >> For those that are interested: >> What fields should we require a user to fill in when submitting a >> request for a new build so that it will give enough info for packagers >> to quickly determine their interest? At the very least I was thinking >> App Category, App Name, Link to Homepage and a Short description. >> > > Some information on language/build system and possibly known deps might > be useful. All probably extractable from the homepage (or general site) > but it might be good to have those as clear fields. It would be good to > know if something was written in C using autotools with no deps or if it > were written in brainfuck and uses zmake++ and depends on gconf. > _______________________________________________ > 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/ > > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0