From ozan.turkyilmaz at gmail.com Sat Oct 2 17:34:18 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 2 Oct 2010 20:34:18 +0300 Subject: [Slackbuilds-users] Libtans1: Broken Link Message-ID: Hi, It seems Gnu moved the lib's folder from Gnutls to its own folder. I tested the tarball from new place and md5sum checked out. New address of the file: http://ftp.gnu.org/gnu/libtasn1/libtasn1-2.2.tar.gz -- Ozan, BSc, BEng From diogo at diogoleal.com Sun Oct 3 00:19:02 2010 From: diogo at diogoleal.com (Diogo Leal) Date: Sat, 2 Oct 2010 21:19:02 -0300 Subject: [Slackbuilds-users] Xulrunner link broken Message-ID: Hello, The link for download xulrunner is broken and the version is old. The correct link is http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.9.2.10/source/ Diogo Leal [aka estranho] http://diogoleal.com msn | gtalk: estranho at diogoleal.com From andrew.david.52 at gmail.com Tue Oct 5 03:29:16 2010 From: andrew.david.52 at gmail.com (andrew) Date: Tue, 5 Oct 2010 14:29:16 +1100 Subject: [Slackbuilds-users] Two small errors in subtitleripper CMakeLists.txt Message-ID: <20101005032916.GA22741@skamandros.andrews-corner.org> Hi, There are 2 small errors in the CMakeLists.txt file for subtitleripper 0.3_4 which firstly damage the script pgm2txt by over zealous sed replacement and secondly fail to give the correct path to allow pgm2txt to find the language filter files. This can be solved by replacing this line: COMMAND sed s|PATH_TO_LANGUAGE_FILTER.*|PATH_TO_LANGUAGE_FILTER=@CMAKE_INSTALL_PREFIX@/@DATA_INSTALL_DIR@/subtitleripper| with the following: COMMAND sed s|^PATH_TO_LANGUAGE_FILTER.*|PATH_TO_LANGUAGE_FILTER=@CMAKE_INSTALL_PREFIX@/@DATA_INSTALL_DIR@/subtitleripper/| Thanks for your trouble, Andrew Strong -- Do you think that's air you're breathing? From marc at freshbash.org Tue Oct 5 17:20:38 2010 From: marc at freshbash.org (Marcel Saegebarth) Date: Tue, 05 Oct 2010 19:20:38 +0200 Subject: [Slackbuilds-users] pokerth.SlackBuild Message-ID: <4CAB5E66.8020807@freshbash.org> I forgot to mention that the submitted PokerTH build also requires the already submitted libgsasl package. Sorry about that. Would someone take care of it? Many thanks. -marc From pablosantamaria at gmail.com Tue Oct 5 19:54:05 2010 From: pablosantamaria at gmail.com (Pablo Santamaria) Date: Tue, 5 Oct 2010 16:54:05 -0300 Subject: [Slackbuilds-users] Packages are looking for new mainteners. Message-ID: Hi! For several reasons I don't use them now, I want to hand over some package maintenance: pyyaml rednotebook audiere cuberok peksystray Cheers, Pablo Santamaria From dave at unrealize.co.uk Tue Oct 5 22:43:35 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Tue, 5 Oct 2010 23:43:35 +0100 Subject: [Slackbuilds-users] Packages are looking for new mainteners. In-Reply-To: References: Message-ID: <20101005224335.GA23561@Junius> On (16:54 05/10/10), Pablo Santamaria put forth the proposition: >Hi! > >For several reasons I don't use them now, I want to hand over >some package maintenance: > >pyyaml >rednotebook Rednotebook looks interesting so I will take that plus its dep pyyaml. Cheers David >audiere >cuberok >peksystray > >Cheers, > >Pablo Santamaria >_______________________________________________ >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/ -- 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 dave at unrealize.co.uk Wed Oct 6 05:19:14 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Wed, 6 Oct 2010 06:19:14 +0100 Subject: [Slackbuilds-users] Packages are looking for new mainteners. In-Reply-To: <20101005224335.GA23561@Junius> References: <20101005224335.GA23561@Junius> Message-ID: <20101006051914.GA27731@Junius> On (23:43 05/10/10), David Woodfall put forth the proposition: >On (16:54 05/10/10), Pablo Santamaria put forth the proposition: >>Hi! >> >>For several reasons I don't use them now, I want to hand over >>some package maintenance: >> >>pyyaml >>rednotebook > >Rednotebook looks interesting so I will take that plus its dep pyyaml. > >Cheers > >David Ok. SlackBuilds submitted. Note though that they are now named python-pyyaml and python-rednotebook to fit in with the new format. David > > >>audiere >>cuberok >>peksystray >> >>Cheers, >> >>Pablo Santamaria >>_______________________________________________ >>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/ > >-- >Don't look back, the lemmings are gaining on you. >_______________________________________________ >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/ > -- 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 dave at unrealize.co.uk Wed Oct 6 06:32:22 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Wed, 6 Oct 2010 07:32:22 +0100 Subject: [Slackbuilds-users] Packages are looking for new mainteners. In-Reply-To: <20101006051914.GA27731@Junius> References: <20101005224335.GA23561@Junius> <20101006051914.GA27731@Junius> Message-ID: <20101006063222.GA30011@Junius> On (06:19 06/10/10), David Woodfall put forth the proposition: >On (23:43 05/10/10), David Woodfall put forth the proposition: >>On (16:54 05/10/10), Pablo Santamaria put forth the proposition: >>>Hi! >>> >>>For several reasons I don't use them now, I want to hand over >>>some package maintenance: >>> >>>pyyaml >>>rednotebook >> >>Rednotebook looks interesting so I will take that plus its dep pyyaml. >> >>Cheers >> >>David > >Ok. SlackBuilds submitted. Note though that they are now named >python-pyyaml and python-rednotebook to fit in with the new format. After some discussion, renamed back to original names. > >David > >> >> >>>audiere >>>cuberok >>>peksystray >>> >>>Cheers, >>> >>>Pablo Santamaria >>>_______________________________________________ >>>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/ >> >>-- >>Don't look back, the lemmings are gaining on you. > > > >>_______________________________________________ >>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/ >> > > >-- >Don't look back, the lemmings are gaining on you. >_______________________________________________ >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/ > -- 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 mfilpot at gmail.com Wed Oct 6 13:33:15 2010 From: mfilpot at gmail.com (Matthew Fillpot) Date: Wed, 6 Oct 2010 09:33:15 -0400 Subject: [Slackbuilds-users] Packages are looking for new mainteners. In-Reply-To: References: Message-ID: On Tue, Oct 5, 2010 at 3:54 PM, Pablo Santamaria wrote: > Hi! > > For several reasons I don't use them now, I want to hand over > some package maintenance: > > pyyaml > rednotebook > audiere > cuberok > peksystray > > Cheers, > > Pablo Santamaria > _______________________________________________ > 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/ > > If audiere and cuberok have not been taken, then I can take them over. -- -Thank You, -Matthew Fillpot From crockabiscuit at yahoo.com Wed Oct 6 20:40:24 2010 From: crockabiscuit at yahoo.com (Crocka Biscuit) Date: Wed, 6 Oct 2010 13:40:24 -0700 (PDT) Subject: [Slackbuilds-users] I want to resubmit rhythmbox slackbuild. Message-ID: <244873.72337.qm@web120320.mail.ne1.yahoo.com> README of rhythmbox slackbuild is incomplete. I want to resubmit rhythmbox slackbuild. Can somebody remove rhythmbox in the pending queue? -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.david.52 at gmail.com Thu Oct 7 00:32:47 2010 From: andrew.david.52 at gmail.com (andrew) Date: Thu, 7 Oct 2010 11:32:47 +1100 Subject: [Slackbuilds-users] libmp3splt for 13.1: page incomplete Message-ID: <20101007003247.GA26108@skamandros.andrews-corner.org> Hi, libmp3splt page is only partly there and downloaded slackbuild does not extract: http://slackbuilds.org/repository/13.1/audio/libmp3splt/ Thanks for looking at this, Andrew -- Do you think that's air you're breathing? From erik at slackbuilds.org Thu Oct 7 01:04:26 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Wed, 6 Oct 2010 20:04:26 -0500 Subject: [Slackbuilds-users] libmp3splt for 13.1: page incomplete In-Reply-To: <20101007003247.GA26108@skamandros.andrews-corner.org> References: <20101007003247.GA26108@skamandros.andrews-corner.org> Message-ID: <20101006200426.14e2dce3@shaggy.doo> On Thu, 7 Oct 2010 11:32:47 +1100 andrew wrote: > Hi, > > libmp3splt page is only partly there and downloaded slackbuild does > not extract: > > http://slackbuilds.org/repository/13.1/audio/libmp3splt/ Small db error, has been fixed. Thanks. http://slackbuilds.org/repository/13.1/libraries/libmp3splt/ -- 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 miorimmax at gmail.com Thu Oct 7 19:22:32 2010 From: miorimmax at gmail.com (Max Miorim) Date: Thu, 7 Oct 2010 16:22:32 -0300 Subject: [Slackbuilds-users] libtasn1: broken DOWNLOAD and HOMEPAGE URLs Message-ID: Hi, Sometime ago the folks at GNU split libtasn1 from the GNUTLS tree, moving it to http://ftp.gnu.org/gnu/libtasn1/. With this chage libtasn1.info needs to be updated to point to the right HOMEPAGE and DOWNLOAD URLs, here's a patch to do so: diff --git a/libraries/libtasn1/libtasn1.info b/libraries/libtasn1/libtasn1.info index cccf460..d463665 100644 --- a/libraries/libtasn1/libtasn1.info +++ b/libraries/libtasn1/libtasn1.info @@ -1,7 +1,7 @@ PRGNAM="libtasn1" VERSION="2.2" -HOMEPAGE="http://ftp.gnu.org/gnu/gnutls/" -DOWNLOAD="http://ftp.gnu.org/gnu/gnutls/libtasn1-2.2.tar.gz" +HOMEPAGE="http://ftp.gnu.org/gnu/libtasn1/" +DOWNLOAD="http://ftp.gnu.org/gnu/libtasn1/libtasn1-2.2.tar.gz" MD5SUM="14cc361500d2e768a8a6ec538ce3fecb" DOWNLOAD_x86_64="" MD5SUM_x86_64="" -- Max From contato at brunorusso.eti.br Fri Oct 8 02:15:37 2010 From: contato at brunorusso.eti.br (Bruno Tadeu Russo) Date: Thu, 07 Oct 2010 23:15:37 -0300 Subject: [Slackbuilds-users] Link to bacula site error Message-ID: <4CAE7EC9.9050304@brunorusso.eti.br> Hello! The link to the official website of the bacula (http://slackbuilds.org/repository/13.1/system/bacula/) is wrong. http://slackbuilds.org/repository/13.1/system/bacula/www.bacula.org the correct link should be: http://www.bacula.org hugs, -- =============================== Bruno T. Russo (aka BrunoRusso) MSN: brunotadeurusso at hotmail.com twitter: @brunorusso "Keep It Simple, Stupid" From erik at slackbuilds.org Fri Oct 8 02:32:33 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Thu, 7 Oct 2010 21:32:33 -0500 Subject: [Slackbuilds-users] Link to bacula site error In-Reply-To: <4CAE7EC9.9050304@brunorusso.eti.br> References: <4CAE7EC9.9050304@brunorusso.eti.br> Message-ID: <20101007213233.30a86179@shaggy.doo> On Thu, 07 Oct 2010 23:15:37 -0300 Bruno Tadeu Russo wrote: > Hello! > > The link to the official website of the bacula > (http://slackbuilds.org/repository/13.1/system/bacula/) is wrong. > > http://slackbuilds.org/repository/13.1/system/bacula/www.bacula.org > > the correct link should be: > > http://www.bacula.org > > hugs, > Fixed in git nearly two weeks ago, one of us admins just needs to not be lazy and do some work *cough* http://slackbuilds.org/gitweb/?p=slackbuilds.git;a=commit;h=00956b -- 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 donaldcallen at gmail.com Fri Oct 8 13:58:51 2010 From: donaldcallen at gmail.com (Donald Allen) Date: Fri, 8 Oct 2010 09:58:51 -0400 Subject: [Slackbuilds-users] libtasn1 source link broken Message-ID: The link to the source on http://slackbuilds.org/repository/13.1/libraries/libtasn1/ is broken. /Don -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.david.52 at gmail.com Sun Oct 10 03:49:09 2010 From: andrew.david.52 at gmail.com (andrew) Date: Sun, 10 Oct 2010 14:49:09 +1100 Subject: [Slackbuilds-users] Two small errors in subtitleripper CMakeLists.txt In-Reply-To: <20101005032916.GA22741@skamandros.andrews-corner.org> References: <20101005032916.GA22741@skamandros.andrews-corner.org> Message-ID: <20101010034909.GA11140@skamandros.andrews-corner.org> On Tue, Oct 05, 2010 at 02:29:16PM +1100, andrew wrote: > There are 2 small errors in the CMakeLists.txt file for subtitleripper > 0.3_4 which firstly damage the script pgm2txt by over zealous sed > replacement and secondly fail to give the correct path to allow > pgm2txt to find the language filter files. Hmmm.... shall I just submit a package with the changes in the normal way? Without this installation change pgm2txt fails completely. Andrew -- Do you think that's air you're breathing? From rworkman at slackbuilds.org Sun Oct 10 05:06:26 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 10 Oct 2010 00:06:26 -0500 Subject: [Slackbuilds-users] libtasn1: broken DOWNLOAD and HOMEPAGE URLs In-Reply-To: References: Message-ID: <20101010000626.40d7e1d6@liberty.rlwhome.lan> On Thu, 7 Oct 2010 16:22:32 -0300 Max Miorim wrote: > Hi, > > Sometime ago the folks at GNU split libtasn1 from the GNUTLS tree, > moving it to http://ftp.gnu.org/gnu/libtasn1/. Fixed in my git branch and will be part of next update. 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 Sun Oct 10 05:08:45 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 10 Oct 2010 00:08:45 -0500 Subject: [Slackbuilds-users] Two small errors in subtitleripper CMakeLists.txt In-Reply-To: <20101010034909.GA11140@skamandros.andrews-corner.org> References: <20101005032916.GA22741@skamandros.andrews-corner.org> <20101010034909.GA11140@skamandros.andrews-corner.org> Message-ID: <20101010000845.6187a6df@liberty.rlwhome.lan> On Sun, 10 Oct 2010 14:49:09 +1100 andrew wrote: > On Tue, Oct 05, 2010 at 02:29:16PM +1100, andrew wrote: > > > There are 2 small errors in the CMakeLists.txt file for > > subtitleripper 0.3_4 which firstly damage the script pgm2txt by > > over zealous sed replacement and secondly fail to give the correct > > path to allow pgm2txt to find the language filter files. > > Hmmm.... shall I just submit a package with the changes in the normal > way? Without this installation change pgm2txt fails completely. The maintainer submitted an update with the fix. I'm going to try and get that one fixed in git tonight. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From andrew.david.52 at gmail.com Sun Oct 10 06:39:33 2010 From: andrew.david.52 at gmail.com (andrew) Date: Sun, 10 Oct 2010 17:39:33 +1100 Subject: [Slackbuilds-users] Two small errors in subtitleripper CMakeLists.txt In-Reply-To: <20101010000845.6187a6df@liberty.rlwhome.lan> References: <20101005032916.GA22741@skamandros.andrews-corner.org> <20101010034909.GA11140@skamandros.andrews-corner.org> <20101010000845.6187a6df@liberty.rlwhome.lan> Message-ID: <20101010063933.GA17533@skamandros.andrews-corner.org> On Sun, Oct 10, 2010 at 12:08:45AM -0500, Robby Workman wrote: > The maintainer submitted an update with the fix. I'm going to > try and get that one fixed in git tonight. Thanks Robby and Andr? :) Andrew -- Do you think that's air you're breathing? From andrew.david.52 at gmail.com Sun Oct 10 08:11:49 2010 From: andrew.david.52 at gmail.com (andrew) Date: Sun, 10 Oct 2010 19:11:49 +1100 Subject: [Slackbuilds-users] Two small errors in subtitleripper CMakeLists.txt In-Reply-To: <20101010063933.GA17533@skamandros.andrews-corner.org> References: <20101005032916.GA22741@skamandros.andrews-corner.org> <20101010034909.GA11140@skamandros.andrews-corner.org> <20101010000845.6187a6df@liberty.rlwhome.lan> <20101010063933.GA17533@skamandros.andrews-corner.org> Message-ID: <20101010081149.GA21001@skamandros.andrews-corner.org> On Sun, Oct 10, 2010 at 05:39:33PM +1100, andrew wrote: > On Sun, Oct 10, 2010 at 12:08:45AM -0500, Robby Workman wrote: > > > The maintainer submitted an update with the fix. I'm going to > > try and get that one fixed in git tonight. > > Thanks Robby and Andr? :) Mind you, just to reinforce the idea that I am a little pushy, I have had a look at the git changes and without the forward slash at the end of my suggested change: [...] LL_PREFIX@/@DATA_INSTALL_DIR@/subtitleripper/| ^^ the script will not be able to find the files gocrfilter_en.sed gocrfilter_fr.sed gocrfilter_none.sed and give an error message, but continue working. Thanks again, Andrew -- Do you think that's air you're breathing? From rworkman at slackbuilds.org Sun Oct 10 13:31:52 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 10 Oct 2010 08:31:52 -0500 Subject: [Slackbuilds-users] Two small errors in subtitleripper CMakeLists.txt In-Reply-To: <20101010081149.GA21001@skamandros.andrews-corner.org> References: <20101005032916.GA22741@skamandros.andrews-corner.org> <20101010034909.GA11140@skamandros.andrews-corner.org> <20101010000845.6187a6df@liberty.rlwhome.lan> <20101010063933.GA17533@skamandros.andrews-corner.org> <20101010081149.GA21001@skamandros.andrews-corner.org> Message-ID: <20101010083152.21ffce24@liberty.rlwhome.lan> On Sun, 10 Oct 2010 19:11:49 +1100 andrew wrote: > On Sun, Oct 10, 2010 at 05:39:33PM +1100, andrew wrote: > > On Sun, Oct 10, 2010 at 12:08:45AM -0500, Robby Workman wrote: > > > > > The maintainer submitted an update with the fix. I'm going to > > > try and get that one fixed in git tonight. > > > > Thanks Robby and Andr? :) > > Mind you, just to reinforce the idea that I am a little pushy, I have > had a look at the git changes and without the forward slash at the end > of my suggested change: > > [...] LL_PREFIX@/@DATA_INSTALL_DIR@/subtitleripper/| > ^^ > the script will not be able to find the files gocrfilter_en.sed > gocrfilter_fr.sed gocrfilter_none.sed and give an error message, but > continue working. Look again :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Tue Oct 12 06:04:54 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 12 Oct 2010 06:04:54 +0000 Subject: [Slackbuilds-users] Updates - 20101012 Message-ID: <20101012060454.GA23776@slackbuilds.org> Tue Oct 12 05:10:06 UTC 2010 Various: Fix some homepage links. audio/clementine: Updated for version 0.5 desktop/QtCurve-Gtk2: Updated for version 1.6.3. desktop/QtCurve-KDE4: Updated for version 1.6.3. desktop/i3: Miscellaneous cleanups/enhancements desktop/i3status: Added (status line generator for dzen2 / xmobar) desktop/notification-daemon: Added (the name says it all) desktop/rootactions_servicemenu: Added (RunAsRoot KDE menu addons) desktop/xfce4-cpugraph-plugin: Fixed download link in info file desktop/xfce4-datetime-plugin: Fixed download link in .info file desktop/xfce4-diskperf-plugin: Fixed download link in .info file desktop/xfce4-fsguard-plugin: Fixed download link in .info file desktop/xfce4-genmon-plugin: Fixed download link in .info file desktop/xfce4-mount-plugin: Fixed download link in .info file desktop/xfce4-mpc-plugin: Fixed download in .info file desktop/xfce4-netload-plugin: Fixed download link in .info file desktop/xfce4-quicklauncher-plugin: Fixed download link desktop/xfce4-sensors-plugin: Fixed download link in .info file desktop/xfce4-smartbookmark-plugin: Fixed download link desktop/xfce4-systemload-plugin: Fixed download link in .info file desktop/xfce4-time-out-plugin: Fixed download link in .info file desktop/xfce4-timer-plugin: Fixed download link in .info file desktop/xfce4-verve-plugin: Fixed download link in .info file desktop/xfce4-wavelan-plugin: Fixed download link in .info file desktop/xfce4-xkb-plugin: Fixed download link in .info file desktop/xfce4-xmms-plugin: Fixed download link in .info file development/check: Added (unit test framework) development/lua: Link libm in the shared library development/mono: Updated for version 2.8. games/glestae: Updated for version 0.3.1. games/tomenet: Removed per maintainer request libraries/ORBit2: Updated for version 2.14.19. New Maintainer. libraries/avr-libc: Added (libc for programming on the AVR platform) libraries/libgdiplus: Updated for version 2.8. libraries/libiconv: Added (text encoding conversion library) libraries/libtasn1: Fixed homepage and download links multimedia/clamz: Added (cli program to download MP3s from amazon) multimedia/flash-player-plugin: Updated for Preview 2. multimedia/subtitleripper: Fix build failure wrt CMakeLists.txt multimedia/vkeybd: Fix the desktop file by adding Categories network/quassel: Updated for version 0.7.1 network/youtube-dl: Corner case build fix and misc cleanups system/d-feet: Updated for version 0.1.12. system/gparted: Updated for version 0.6.3 system/xen: Added (the Xen virtualization hypervisor) From lukenshiro at ngi.it Wed Oct 13 20:43:04 2010 From: lukenshiro at ngi.it (LukenShiro) Date: Wed, 13 Oct 2010 22:43:04 +0200 Subject: [Slackbuilds-users] efax-gtk removal from pending request Message-ID: <20101013224304.66fd55b4lukenshiro@ngi.it@sigil.norad> Hi all! Unfortunately just today efax-gtk upstream developer has released a bugfix version. Can anyone remove my package from pending (in order to test and then resubmit efax-gtk's new version), please? TIA -- GNU/Linux * Slackware64 current LU #210970 SU #12583 LM #98222/#412913 From nickblizzard1776 at gmail.com Wed Oct 13 21:06:31 2010 From: nickblizzard1776 at gmail.com (Nick Blizzard) Date: Wed, 13 Oct 2010 17:06:31 -0400 Subject: [Slackbuilds-users] xulrunner needs update Message-ID: <4CB61F57.8000504@gmail.com> The slackbuild is a lil out of date, looks like they have moved onto .10 new source location: http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.9.2.10/source/ From mjjzf at syntaktisk.dk Fri Oct 15 00:47:45 2010 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Thu, 14 Oct 2010 20:47:45 -0400 Subject: [Slackbuilds-users] Creating a .desktop Message-ID: <20101014204745.1e44a88d@espero.eicet.org> Dear Slackers, I am writing a Slackbuild for TaskCoach. As it happens, it doesn't include a .desktop file. Is there a convention for how to do this? Is it acceptable if it is simply included in the Slackbuild folder? Yours, Morten From niels.horn at gmail.com Fri Oct 15 00:58:43 2010 From: niels.horn at gmail.com (Niels Horn) Date: Thu, 14 Oct 2010 21:58:43 -0300 Subject: [Slackbuilds-users] Creating a .desktop In-Reply-To: <20101014204745.1e44a88d@espero.eicet.org> References: <20101014204745.1e44a88d@espero.eicet.org> Message-ID: On Thu, Oct 14, 2010 at 9:47 PM, Morten Juhl-Johansen Z?lde-Fej?r wrote: > Dear Slackers, > > I am writing a Slackbuild for TaskCoach. As it happens, it doesn't > include a .desktop file. > Is there a convention for how to do this? Is it acceptable if it is > simply included in the Slackbuild folder? > > Yours, > Morten Hi, It is acceptable and I have done it a few times. Just add it to the .tar.gz and in the script copy it to /usr/share/applications/ Don't forget to add a doinst.sh with at least these lines: if [ -x /usr/bin/update-desktop-database ]; then /usr/bin/update-desktop-database -q usr/share/applications >/dev/null 2>&1 fi Regards, Niels From burningc at SDF.LONESTAR.ORG Fri Oct 15 18:06:00 2010 From: burningc at SDF.LONESTAR.ORG (Glenn Becker) Date: Fri, 15 Oct 2010 18:06:00 +0000 (UTC) Subject: [Slackbuilds-users] lshw: compilation fails Message-ID: Hi - I am trying to build lshw on one of my -current boxes, and the build is failing thusly: c++ -g -Wall -DPREFIX=\"/usr\" -DSBINDIR=\"/usr/sbin\" -DMANDIR=\"/usr/man\" -DDATADIR=\"/usr/share\" -O2 -march=i486 -mtune=i686 -c scsi.cc -o scsi.o scsi.cc: In function 'bool scan_hosts(hwNode&)': scsi.cc:845:74: error: cannot call constructor 'hwNode::hwNode' directly scsi.cc:845:74: error: for a function-style cast, remove the redundant '::hwNode' make[2]: *** [scsi.o] Error 1 make[2]: Leaving directory `/tmp/SBo/lshw-B.02.14/src/core' make[1]: *** [core] Error 2 make[1]: Leaving directory `/tmp/SBo/lshw-B.02.14/src' make: *** [all] Error 2 ... should I consider writing the upstream maintainer? This doesn't seem (to me) to have anything to do with the Slackbuild. Or should I report this to the lshw maintainer? I see on the lshw webpage that "The latest version is B.02.15" ... maybe that version'd work better ...? Sorry, not sure what the protocol is. Thanks, Glenn +-----------------------------------------------------+ Glenn Becker - burningc at sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org +-----------------------------------------------------+ From grbzks at xsmail.com Fri Oct 15 19:00:05 2010 From: grbzks at xsmail.com (Grigorios Bouzakis) Date: Fri, 15 Oct 2010 22:00:05 +0300 Subject: [Slackbuilds-users] lshw: compilation fails In-Reply-To: References: Message-ID: <1287169205.26346.1400278979@webmail.messagingengine.com> On Fri, 15 Oct 2010 18:06 +0000, "Glenn Becker" wrote: > > Hi - > > I am trying to build lshw on one of my -current boxes, and the build is > failing thusly: > > c++ -g -Wall -DPREFIX=\"/usr\" -DSBINDIR=\"/usr/sbin\" > -DMANDIR=\"/usr/man\" -DDATADIR=\"/usr/share\" -O2 -march=i486 > -mtune=i686 > -c scsi.cc -o scsi.o > scsi.cc: In function 'bool scan_hosts(hwNode&)': > scsi.cc:845:74: error: cannot call constructor 'hwNode::hwNode' directly > scsi.cc:845:74: error: for a function-style cast, remove the redundant > '::hwNode' > make[2]: *** [scsi.o] Error 1 > make[2]: Leaving directory `/tmp/SBo/lshw-B.02.14/src/core' > make[1]: *** [core] Error 2 > make[1]: Leaving directory `/tmp/SBo/lshw-B.02.14/src' > make: *** [all] Error 2 > > ... should I consider writing the upstream maintainer? This doesn't seem > (to me) to have anything to do with the Slackbuild. Or should I report > this to the lshw maintainer? > > I see on the lshw webpage that > > "The latest version is B.02.15" > > ... maybe that version'd work better ...? > > Sorry, not sure what the protocol is. > > Thanks, > > Glenn This is to be expected to some extend now that -current has a new toolchain. It is definitely worth checking out newer versions than the ones upload into SBo. Always check those (& even the upstream development trunk if possible) before contacting upstream. If the application has active development that usually means most building issues are worked out. FTR slackbuilds.org doesnt directly support current, so this cant considered a bug. But its in the convinience of the maintainer to update it to some later version that may solve such building problems, granted that the newer version can be used in the latest Slackware stable version as well. --- Greg From burningc at SDF.LONESTAR.ORG Fri Oct 15 19:14:34 2010 From: burningc at SDF.LONESTAR.ORG (Glenn Becker) Date: Fri, 15 Oct 2010 19:14:34 +0000 (UTC) Subject: [Slackbuilds-users] lshw: compilation fails In-Reply-To: <1287169205.26346.1400278979@webmail.messagingengine.com> References: <1287169205.26346.1400278979@webmail.messagingengine.com> Message-ID: > This is to be expected to some extend now that -current has a new > toolchain. > It is definitely worth checking out newer versions than the ones upload > into > SBo. Always check those (& even the upstream development trunk if > possible) > before contacting upstream. If the application has active development > that > usually means most building issues are worked out. > FTR slackbuilds.org doesnt directly support current, so this cant > considered > a bug. But its in the convinience of the maintainer to update it to some > later > version that may solve such building problems, granted that the newer > version > can be used in the latest Slackware stable version as well. Greg, Thanks so much for the informative reply. I should have thought about this some more before emailing. :) Regards, Glenn +-----------------------------------------------------+ Glenn Becker - burningc at sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org +-----------------------------------------------------+ From koolniczka at gmail.com Sun Oct 17 21:02:25 2010 From: koolniczka at gmail.com (John Doe) Date: Sun, 17 Oct 2010 23:02:25 +0200 Subject: [Slackbuilds-users] "Required" package listing in .info ? In-Reply-To: References: <1287169205.26346.1400278979@webmail.messagingengine.com> Message-ID: <4CBB6461.3040408@gmail.com> Hello all, I am (probably not alone ;-) ) benefiting from the quite stable quality of the packages produced from the SBo scripts. Taken this measure of reliability we've all learned to know and love I even produced (maybe I'm not alone here either) some layer of automation based on the scripts ("one touch build", ftp + wget + build). Now, all the above said, let me step on the thin ice (and please note beforehand that I am a long term Slack user and I'm aware of the general opinion on the automated dependency resolution and package management). I would like to check the opinion of the list members & SBo's core crew on the inclusion of machine readable information about packages required to build a given packages. This information is customarily provided in the README description (which is widely appreciated, I believe ;-) ) so it seems only logical to have it included in the PACKAGE.info file as well. I would propose to amend the guideline governing the format of .info files (as made available on SBo http://slackbuilds.org/guidelines ) with something like: REQUIRES=("package1" "package2" ... "packageX") where package[1..X] is defined as 1.) either the name of the package as provided by SBo if such package is available 2.) or the package name as provided by the source distributor if there is no SBo build for it Packages provided by stock Slack issue should not be listed here (as they are usually not mentioned in the README either ). This format will readily enable it's inclusion into "sh" based tools by source or eval of the .info file (as is case at the moment) My $0.02 Take care Koolniczka From rworkman at slackbuilds.org Sun Oct 17 22:16:18 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 17 Oct 2010 17:16:18 -0500 Subject: [Slackbuilds-users] remove dovecot-cmusieve In-Reply-To: <4C9CC202.5050404@mnspace.net> References: <4C9CC202.5050404@mnspace.net> Message-ID: <20101017171618.0ea6ce0b@liberty> On Fri, 24 Sep 2010 10:21:38 -0500 Nishant Limbachia wrote: > Hi admins, > > With dovecot 2.0 in our repo, dovecot-cmusieve is no longer needed and > is superseded by dovecot-pigeonhole. Sorry for the delay; this will be done 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 rworkman at slackbuilds.org Sun Oct 17 22:18:09 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 17 Oct 2010 17:18:09 -0500 Subject: [Slackbuilds-users] Opera 10.62 In-Reply-To: <20100930081905.GA2770@pollux.mlnet> References: <20100930081905.GA2770@pollux.mlnet> Message-ID: <20101017171809.1a48c774@liberty> On Thu, 30 Sep 2010 10:19:05 +0200 emmel wrote: > Oh, and the build script doesn't quite seem to adhere to the > build script template. Both the version and revision number should be > variables with defaults rather than set statically in the script. There's no real standard on which is "correct" so either is fine. That being said, it's probably *best* to allow the overrides, but still... :) > Of course now that opera seems to have solved the repackaging issue > regarding the tar.bz the script might go through a rewrite anyway, > but I just wanted to mention it. The rpm repackaging works fine, so it's staying as is unless someone cares enough to rewrite it for the tar.bz2, in which case that person can take over maintenance of the script :) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Oct 18 01:50:28 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 18 Oct 2010 01:50:28 +0000 Subject: [Slackbuilds-users] Updates - 20101018 Message-ID: <20101018015028.GA21088@slackbuilds.org> Mon Oct 18 01:25:45 UTC 2010 academic/calc: Updated for version 2.12.4.3. academic/genius: Updated for version 1.0.11. academic/grass: Added (Geographic Resources Analysis Support System) audio/lxmusic: Miscellaneous fixes. audio/mpd: Updated for version 0.15.13. audio/portmidi: Various script cleanups. desktop/QtCurve-Gtk2: Updated for version 1.6.4. desktop/QtCurve-KDE4: Updated for version 1.6.4. desktop/gtk-engines: Updated for version 2.20.2. desktop/lxde-common: Fixed naming of config files. desktop/lxpanel-xmms2: Added (xmms2 plugin for lxpanel) desktop/pidgin-guifications: Fixed download link desktop/wmMoonClock: Patched to fix southern hemisphere display. development/Cython: Updated for version 0.13. development/eric: Updated for version 4.4.8. development/latrace: Updated for version 0.5.9. development/pep8: Updated for version 0.6.0. development/tig: Updated for version 0.16.2. development/viewvc: Updated for version 1.1.7. games/pokerth: Updated for version 0.8 graphics/dcraw: Updated for version 9.04. graphics/goocanvas: Miscellaneous cleanups graphics/shutter: Added (feature-rich screenshot program) libraries/OpenAL: Updated for version 1.12.854. libraries/PyYAML: Renamed and updated for version 3.09. libraries/daq: Added (Data Acquisition libary) libraries/goffice: Updated for version 0.8.10. libraries/libgee: Updated for version 0.6.0. libraries/libgsasl: Updated for version 1.4.4. libraries/libmusicbrainz3: Updated for version 3.0.3. libraries/libwww-perl: Updated for version 5.837. libraries/perl-Image-Info: Updated for version 1.31. libraries/perl-Sub-Uplevel: Miscellaneous cleanups libraries/perl-Unicode-String: Added (Perl Unicode modules) libraries/perl-cairo: Fixed dep info in README. libraries/perl-digest-sha1: Updated for version 2.13. libraries/perl-gnome2-canvas: Fixed dep info in README. libraries/perl-gnome2-gconf: Added (Gnome2::GConf perl module) libraries/perl-gnome2-vfs: Fixed dep info in README. libraries/perl-gnome2-wnck: Added (Gnome2::Wnck perl module) libraries/perl-gnome2: Fixed dep info in README. libraries/perl-goo-canvas: Added (Goo::Canvas perl module) libraries/perl-gtk2-imageview: Fixed dep info in README. libraries/perl-gtk2: Fixed dep info in README. libraries/perl-html-parser: Updated for version 3.68. libraries/perl-http-response-encoding: Added (HTTP::Response::Encoding pm) libraries/perl-http-server-simple: Added (HTTP::Server::Simple pm) libraries/perl-net-dbus: Added (Net::DBus perl module) libraries/perl-pango: Fixed dep info in README. libraries/perl-proc/processtable: Added (Proc::ProcessTable pm) libraries/perl-test-warn: Added (Test::Warn perl module) libraries/perl-tree-dagnode: Added (Tree::DAG_Node perl module) libraries/perl-www-mechanize: Added (WWW::Mechanize perl module) libraries/perl-x11-protocol: Added (X11::Protocol perl module) libraries/podofo: Updated for version 0.8.2. libraries/pyyaml: Removed renamed PyYAML. libraries/quesoglc: Miscellaneous fixes. misc/ibus: Use GConf by default. misc/rsibreak: Added. (break reminder) multimedia/media-player-info: Updated for version 10. network/RSSOwl: Updated for version 2.0.6. network/barnyard2: Added (log parser for snort) network/base: Added (web front-end for Snort) network/dovecot-cmusieve: Removed (replaced by dovecot-pigeonhole) network/googlecl: Updated for version 0.9.10. network/knemo: Updated for version 0.6.80. network/mldonkey: Updated for version 3.0.5. network/nagios: Updated for version 3.2.3. network/opera: Updated for version 10.63. network/perl-MailTools: Updated for version 2.07. network/perl-NetAddr-IP: Updated for version 4.032. network/shorewall6: Updated for version 4.4.13.1. network/shorewall: Updated for version 4.4.13.1. network/smstools3: Added (SMS Server Tools) network/snort: Updated for version 2.9.0. office/adobe-reader: Updated for version 9.4. office/apvlv: Updated for version 0.0.9.8. office/gnumeric: Updated for version 1.10.10. office/libreoffice: Added (Fork of OpenOffice.org) office/rednotebook: Updated for version 1.1.1. office/scribus: Updated for version 1.3.8. office/wammu: Updated for version 0.34. system/ddrescure: Updated for version 1.13. system/encfs: Updated for version 1.7.2. system/lxtask: Removed man-compressing section. system/nilfs-utils: Updated for version 2.0.20. system/p7zip: Updated for version 9.13. system/ssdeep: Updated for version 2.6. From kingbeowulf at gmail.com Mon Oct 18 05:28:06 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 17 Oct 2010 22:28:06 -0700 Subject: [Slackbuilds-users] "Required" package listing in .info ? In-Reply-To: <4CBB6461.3040408@gmail.com> References: <1287169205.26346.1400278979@webmail.messagingengine.com> <4CBB6461.3040408@gmail.com> Message-ID: I'd be perfectly happy if the readme and info files listed the compile order for dependencies (e. g. Inkscape) so that I have a heads up for planning the build (this is sometimes "hinted" at by the list order). A machine readable fomat for SBo may be a lot a work for not much gain. I for one base part of my software choice decisions of the complexity of the dependencies with a preference for most of the dependencies being already present in Slackware. I also don't load up a lot of software 'just for fun' since I have work to do and only so much time. Thus, I don't upgrade unless there is a compelling reason. There are projects that assist in dependency tracking for slackware, such as slapt-get/gslapt via 'slack-required' There are numerous GNU/Linux distros that provide dependency tracking. I prefer Slackware, and SBo, with its current simplicity. And, after all, there is nothing to stop you from building a project to track dependencies. Just don't expect a lot of sympathy if you want someone else to do the work for you. Just my 2 cents. -Ed On 10/17/10, John Doe wrote: > Hello all, > > I am (probably not alone ;-) ) benefiting from the quite stable quality > of the packages produced from the SBo scripts. Taken this measure of > reliability we've all learned to know and love I even produced (maybe > I'm not alone here either) some layer of automation based on the scripts > ("one touch build", ftp + wget + build). > > Now, all the above said, let me step on the thin ice (and please note > beforehand that I am a long term Slack user and I'm aware of the general > opinion on the automated dependency resolution and package management). > > I would like to check the opinion of the list members & SBo's core crew > on the inclusion of machine readable information about packages required > to build a given packages. This information is customarily provided in > the README description (which is widely appreciated, I believe ;-) ) so > it seems only logical to have it included in the PACKAGE.info file as well. > > I would propose to amend the guideline governing the format of .info > files (as made available on SBo http://slackbuilds.org/guidelines ) with > something like: > > REQUIRES=("package1" "package2" ... "packageX") > > where package[1..X] is defined as > 1.) either the name of the package as provided by SBo if such package > is available > 2.) or the package name as provided by the source distributor if there > is no SBo build for it > > Packages provided by stock Slack issue should not be listed here (as > they are usually not mentioned in the README either ). > > > This format will readily enable it's inclusion into "sh" based tools by > source or eval of the .info file (as is case at the moment) > > My $0.02 > > Take care > Koolniczka > > _______________________________________________ > 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 kingbeowulf at gmail.com Mon Oct 18 05:47:14 2010 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 17 Oct 2010 22:47:14 -0700 Subject: [Slackbuilds-users] a note of appreciation Message-ID: Just a note to thank the SBo team and slackbuild maintainers for all their hard work. I really appreciate it. Its made my computer hobby (addiction?) a bit easier! Sometimes a simple "thank you" gets lost in the yelling and screaming. -Ed -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From chris.abela at maltats.com Mon Oct 18 08:57:00 2010 From: chris.abela at maltats.com (Chris Abela) Date: Mon, 18 Oct 2010 10:57:00 +0200 Subject: [Slackbuilds-users] "Required" package listing in .info ? In-Reply-To: <4CBB6461.3040408@gmail.com> Message-ID: SBo automated dependency resolution already exist: See: http://www.mail-archive.com/slackbuilds-users at slackbuilds.org/msg02733.html Installing gnome packages without sbopkg sqf can be painful. -----Original Message----- From: slackbuilds-users-bounces at slackbuilds.org [mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of John Doe Sent: 17 October 2010 23:02 To: SlackBuilds.org Users List Subject: [Slackbuilds-users] "Required" package listing in .info ? Hello all, I am (probably not alone ;-) ) benefiting from the quite stable quality of the packages produced from the SBo scripts. Taken this measure of reliability we've all learned to know and love I even produced (maybe I'm not alone here either) some layer of automation based on the scripts ("one touch build", ftp + wget + build). Now, all the above said, let me step on the thin ice (and please note beforehand that I am a long term Slack user and I'm aware of the general opinion on the automated dependency resolution and package management). I would like to check the opinion of the list members & SBo's core crew on the inclusion of machine readable information about packages required to build a given packages. This information is customarily provided in the README description (which is widely appreciated, I believe ;-) ) so it seems only logical to have it included in the PACKAGE.info file as well. I would propose to amend the guideline governing the format of .info files (as made available on SBo http://slackbuilds.org/guidelines ) with something like: REQUIRES=("package1" "package2" ... "packageX") where package[1..X] is defined as 1.) either the name of the package as provided by SBo if such package is available 2.) or the package name as provided by the source distributor if there is no SBo build for it Packages provided by stock Slack issue should not be listed here (as they are usually not mentioned in the README either ). This format will readily enable it's inclusion into "sh" based tools by source or eval of the .info file (as is case at the moment) My $0.02 Take care Koolniczka _______________________________________________ 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 ferenc.deak at gmail.com Mon Oct 18 09:59:16 2010 From: ferenc.deak at gmail.com (Deak, Ferenc) Date: Mon, 18 Oct 2010 11:59:16 +0200 Subject: [Slackbuilds-users] "Required" package listing in .info ? In-Reply-To: <4CBB6461.3040408@gmail.com> References: <1287169205.26346.1400278979@webmail.messagingengine.com> <4CBB6461.3040408@gmail.com> Message-ID: First, if you use sbopkg, it supports queue files (for dependencies), and an sbopkg co-developer Mauro Giachero has created a repository of sbopkg queuefiles. See http://sbopkg.org/queues.php, http://gitorious.org/sbopkg-slackware-queues. You can find queue files for all the packages. Second, I have similar opinion as yours. But I understand that sometimes there are many choices for satisfying the dependencies of a package, and it is good that (under slackware) we are free to do that without fighting with a package manager. So I would not call it dependency or I would not call it required packages, but I would call it default build environment or tested build/working environment (or even suggested environment) - in which the packager and the sbo maintainers tested the package, and perhaps the packager *use* the package daily - in which I can expect clean build and correct working - and has a reasonable feature set for the average user In my opinion it would be nice if we have an exact (machine readable) list of this environment, not just a part of a sentence somewhere in the readme file. For me as a packager having about ten packages it is not much work, to create one more line in the .info file, for correctness. And perhaps it would help the sbo maintainers (but i'm not a maintainer!) to easily create the same environment as the packager had when he/she built the package. But on the other hand, if you don't build every package in a clean slackware and only the "required" packages installed, you cannot expect the same result as the the packager had, because a configure script (and the build process) can use the extra packages you already have. fdeak From koolniczka at gmail.com Mon Oct 18 23:11:26 2010 From: koolniczka at gmail.com (John Doe) Date: Tue, 19 Oct 2010 01:11:26 +0200 Subject: [Slackbuilds-users] "Required" package listing in .info ? In-Reply-To: References: <1287169205.26346.1400278979@webmail.messagingengine.com> <4CBB6461.3040408@gmail.com> Message-ID: <4CBCD41E.8050605@gmail.com> Just to put a couple of things right, see inline: King Beowulf - Sun, 17 Oct 2010 22:28:06 -0700 : > I'd be perfectly happy if the readme and info files listed the compile > order for dependencies (e. g. Inkscape) so that I have a heads up for > planning the build (this is sometimes "hinted" at by the list order). > A machine readable fomat for SBo may be a lot a work for not much > gain. I for one base part of my software choice decisions of the .info files are perfectly "machine readable" in my eyes, you can source/eval the values in them for use in shell scripts. I'm not talking XML or whatnot. Just to add one other variable to the existing ones. > complexity of the dependencies with a preference for most of the > dependencies being already present in Slackware. I also don't load up > a lot of software 'just for fun' since I have work to do and only so > much time. Thus, I don't upgrade unless there is a compelling reason. > > There are projects that assist in dependency tracking for slackware, > such as slapt-get/gslapt via 'slack-required' > > There are numerous GNU/Linux distros that provide dependency tracking. > > I prefer Slackware, and SBo, with its current simplicity. Second that. > > And, after all, there is nothing to stop you from building a project > to track dependencies. Just don't expect a lot of sympathy if you want I certainly would not want SBo to turn into a dependency tracking project. I simply propose to capitalize on the work that someone has already invested into building a package ( and shares it with others ) a bit more by providing the info that is already there anyway (in the README usually) in an easily reusable format (shell array). > someone else to do the work for you. > > Just my 2 cents. > > -Ed > Best regards Koolniczka > > > On 10/17/10, John Doe wrote: >> Hello all, >> >> I am (probably not alone ;-) ) benefiting from the quite stable quality >> of the packages produced from the SBo scripts. Taken this measure of >> reliability we've all learned to know and love I even produced (maybe >> I'm not alone here either) some layer of automation based on the scripts >> ("one touch build", ftp + wget + build). >> >> Now, all the above said, let me step on the thin ice (and please note >> beforehand that I am a long term Slack user and I'm aware of the general >> opinion on the automated dependency resolution and package management). >> >> I would like to check the opinion of the list members & SBo's core crew >> on the inclusion of machine readable information about packages required >> to build a given packages. This information is customarily provided in >> the README description (which is widely appreciated, I believe ;-) ) so >> it seems only logical to have it included in the PACKAGE.info file as well. >> >> I would propose to amend the guideline governing the format of .info >> files (as made available on SBo http://slackbuilds.org/guidelines ) with >> something like: >> >> REQUIRES=("package1" "package2" ... "packageX") >> >> where package[1..X] is defined as >> 1.) either the name of the package as provided by SBo if such package >> is available >> 2.) or the package name as provided by the source distributor if there >> is no SBo build for it >> >> Packages provided by stock Slack issue should not be listed here (as >> they are usually not mentioned in the README either ). >> >> >> This format will readily enable it's inclusion into "sh" based tools by >> source or eval of the .info file (as is case at the moment) >> >> My $0.02 >> >> Take care >> Koolniczka >> >> _______________________________________________ >> 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 nickblizzard1776 at gmail.com Tue Oct 19 17:43:38 2010 From: nickblizzard1776 at gmail.com (Nick Blizzard) Date: Tue, 19 Oct 2010 13:43:38 -0400 Subject: [Slackbuilds-users] qemu Message-ID: <4CBDD8CA.9080603@gmail.com> just a heads up that qemu is now 13.0 Build script seems to work fine if version is changed. From erik at slackbuilds.org Wed Oct 20 16:06:18 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Wed, 20 Oct 2010 11:06:18 -0500 Subject: [Slackbuilds-users] Updates - 20101020.1 Message-ID: <20101020110618.5e1d54d3@shaggy.doo> Wed Oct 20 15:54:13 UTC 2010 academic/pcb: Added (printed circuit board editor) desktop/cwp: Updated for version 1.2.3. desktop/icewm: Updated for version 1.3.6. development/empty: Added (automate otherwise interactive sessions) development/erlang-otp: Updated for version 14B. development/geany-plugins: Added. (additional plugins for Geany) development/kdesvn: Updated for version 1.5.5. development/mono-debugger: Updated for version 2.8. development/orc: Updated for version 0.4.11. development/tcc: Added (Tiny C Compiler) games/gnubg: Updated for 20101017 snapshot. games/playonlinux: Updated for version 3.8.3. games/warzone2100: Updated for version 2.3.5. graphics/exact-image: Updated for version 0.8.2. libraries/SDL_gfx: Updated for version 2.0.22. libraries/hdf5: Updated for version 1.8.5_patch1. libraries/libdmapsharing: Added (lib for DMAP family of protocols). libraries/libinfinity: Added (Infinote library and daemon) libraries/libmediainfo: Added. (library for mediainfo). libraries/libqinfinity: Added (libinfinity for QT) libraries/libqsqlpsql: Updated for version 4.6.2_2d3d3e5. libraries/libzen: Added. (mandatory library for libmediainfo). libraries/reportlab: Updated for version 2.5. multimedia/guvcview: Updated for version 1.4.2. multimedia/openshot: Updated for version 1.2.2. network/chromium: Added (Open Source Web Browser) network/cyrus-imapd: Added. (scalable enterprise mail system). network/efax-gtk: Updated for version 3.2.4. network/heimdal: Updated for version 1.4. network/heimdal: Fixed permissions issues. network/kobby: Added (collaborative editor) network/mz: Updated for version 0.40. network/skype: Don't bail out automatically on x86_64 network/wireshark: Updated for version 1.4.1. office/gummi: Added. (Lightweight Latex editor written PyGTK) system/autojump: Updated for version 13. system/conky: Updated for version 1.8.1. system/kvm-kmod: Updated for version 2.6.35.6. system/lxdm: Updated for version 0.3.0. system/lxpolkit: Added. (policykit agent for LXDE). system/mariadb: Added (Drop-in replacement for MySQL) system/mariadb: Note libevent as optional dependency system/nagios-plugins: Updated for version 1.4.15. system/pcsc-lite: Updated for version 1.6.4. system/prelink: Added (ELF prelinking utility) system/unalz: Added (decompression utility for alz) system/watchdog: Minor fixes; thanks to Chris Abela. From cybercrowbr at gmail.com Thu Oct 21 16:11:06 2010 From: cybercrowbr at gmail.com (Molinero) Date: Thu, 21 Oct 2010 14:11:06 -0200 Subject: [Slackbuilds-users] kvm.Slackbuild - README - a little error description In-Reply-To: <20101020110618.5e1d54d3@shaggy.doo> References: <20101020110618.5e1d54d3@shaggy.doo> Message-ID: <4CC0661A.7020802@gmail.com> An HTML attachment was scrubbed... URL: From willysr at gmail.com Fri Oct 22 05:23:08 2010 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Fri, 22 Oct 2010 12:23:08 +0700 Subject: [Slackbuilds-users] Wrong version of Wesnoth Message-ID: Hello, I uploaded an updated SlackBuild script for Wesnoth, but it's said 1.8.4, where it should be 1.8.5. Sorry for the typo -- Willy Sudiarto Raharjo Registered Linux User : 336579 Web : http://www.informatix.or.id/willy Blog : http://willysr.blogspot.com http://slackblogs.blogspot.com From crockabiscuit at yahoo.com Fri Oct 22 07:07:21 2010 From: crockabiscuit at yahoo.com (crocket) Date: Fri, 22 Oct 2010 00:07:21 -0700 (PDT) Subject: [Slackbuilds-users] LinuxPAM has been in the pending queue for months. Message-ID: <705511.76862.qm@web120315.mail.ne1.yahoo.com> It seems LinuxPAM doesn't attract enough attention. Somebody needs to do something about this. -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier.spaier at epsm.fr Fri Oct 22 07:44:22 2010 From: didier.spaier at epsm.fr (Didier Spaier) Date: Fri, 22 Oct 2010 09:44:22 +0200 Subject: [Slackbuilds-users] LinuxPAM has been in the pending queue for months. In-Reply-To: <705511.76862.qm@web120315.mail.ne1.yahoo.com> References: <705511.76862.qm@web120315.mail.ne1.yahoo.com> Message-ID: <4CC140D6.8020909@epsm.fr> Le 22/10/2010 09:07, crocket a ?crit : > It seems LinuxPAM doesn't attract enough attention. > Somebody needs to do something about this. I am not an admin but here is a quote of Slackware 9.1's Changelog: "n/openssh-3.7.1p2-i486-1.tgz: Upgraded to openssh-3.7.1p2. This fixes security problems with PAM authentication. It also includes several code cleanups from Solar Designer. Slackware does not use PAM and is not vulnerable to any of the fixed problems. Please indulge me for this brief aside (as requests for PAM are on the rise): If you see a security problem reported which depends on PAM, you can be glad you run Slackware. I think a better name for PAM might be SCAM, for Swiss Cheese Authentication Modules, and have never felt that the small amount of convenience it provides is worth the great loss of system security. We miss out on half a dozen security problems a year by not using PAM, but you can always install it yourself if you feel that you're missing out on the fun. (No, don't do that) OK, I'm done ranting here. :-) I suppose this is still a: (* Security fix *)" May-be this explain that ? From chris.abela at maltats.com Fri Oct 22 07:53:25 2010 From: chris.abela at maltats.com (Chris Abela) Date: Fri, 22 Oct 2010 09:53:25 +0200 Subject: [Slackbuilds-users] LinuxPAM has been in the pending queue for months. In-Reply-To: <4CC140D6.8020909@epsm.fr> Message-ID: Packages included in Slackware should not be in SBo. Thus enhances the case for a PAM SlackBuild. While Pat is/was correct, PAM is usually included in my Linux Training documentation and so it must have academic interest. -----Original Message----- From: slackbuilds-users-bounces at slackbuilds.org [mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of Didier Spaier Sent: 22 October 2010 09:44 To: SlackBuilds.org Users List Subject: Re: [Slackbuilds-users] LinuxPAM has been in the pending queue for months. Le 22/10/2010 09:07, crocket a ?crit : > It seems LinuxPAM doesn't attract enough attention. > Somebody needs to do something about this. I am not an admin but here is a quote of Slackware 9.1's Changelog: "n/openssh-3.7.1p2-i486-1.tgz: Upgraded to openssh-3.7.1p2. This fixes security problems with PAM authentication. It also includes several code cleanups from Solar Designer. Slackware does not use PAM and is not vulnerable to any of the fixed problems. Please indulge me for this brief aside (as requests for PAM are on the rise): If you see a security problem reported which depends on PAM, you can be glad you run Slackware. I think a better name for PAM might be SCAM, for Swiss Cheese Authentication Modules, and have never felt that the small amount of convenience it provides is worth the great loss of system security. We miss out on half a dozen security problems a year by not using PAM, but you can always install it yourself if you feel that you're missing out on the fun. (No, don't do that) OK, I'm done ranting here. :-) I suppose this is still a: (* Security fix *)" May-be this explain that ? _______________________________________________ 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 erik at slackbuilds.org Fri Oct 22 09:44:26 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 22 Oct 2010 04:44:26 -0500 Subject: [Slackbuilds-users] LinuxPAM has been in the pending queue for months. In-Reply-To: <705511.76862.qm@web120315.mail.ne1.yahoo.com> References: <705511.76862.qm@web120315.mail.ne1.yahoo.com> Message-ID: <20101022044426.5fe8ca6c@shaggy.doo> On Fri, 22 Oct 2010 00:07:21 -0700 (PDT) crocket wrote: > It seems LinuxPAM doesn't attract enough attention. > Somebody needs to do something about this. I suppose I can throw my opinion at this. I haven't looked at this script. Not because of the author, not because it's PAM. I have no problem with PAM, and I think citing old security flaws as reasoning is silly. Mainstream distributions are getting along fine, and it affords them Nice Things that Slackware just Can't Have. That said, if Slackware is to get PAM, I'd much rather see it come from PV or his team. I think it integrates too tightly with the system for it to be something we host at SBo. -- 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 banderols at gmail.com Fri Oct 22 09:46:27 2010 From: banderols at gmail.com (Murat D. Kadirov) Date: Fri, 22 Oct 2010 15:46:27 +0600 Subject: [Slackbuilds-users] LinuxPAM has been in the pending queue for months. In-Reply-To: References: Message-ID: <4CC15D73.3000004@gmail.com> On 22.10.2010 13:53, Chris Abela wrote: > Packages included in Slackware should not be in SBo. Thus enhances the case > for a PAM SlackBuild. While Pat is/was correct, PAM is usually included in > my Linux Training documentation and so it must have academic interest. > Also, many of us can have a practical interest. I am including. -- Murat D. Kadirov PGP fingerprint: 3081 EBFA 5CB9 BD24 4DB6 76EE 1B97 0A0E CEC0 6AA0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From banderols at gmail.com Fri Oct 22 10:36:23 2010 From: banderols at gmail.com (Murat D. Kadirov) Date: Fri, 22 Oct 2010 16:36:23 +0600 Subject: [Slackbuilds-users] LinuxPAM has been in the pending queue for months. In-Reply-To: <20101022044426.5fe8ca6c@shaggy.doo> References: <705511.76862.qm@web120315.mail.ne1.yahoo.com> <20101022044426.5fe8ca6c@shaggy.doo> Message-ID: <4CC16927.3030609@gmail.com> On 22.10.2010 15:44, Erik Hanson wrote: > On Fri, 22 Oct 2010 00:07:21 -0700 (PDT) > crocket wrote: > >> It seems LinuxPAM doesn't attract enough attention. >> Somebody needs to do something about this. > I suppose I can throw my opinion at this. I haven't looked at this > script. Not because of the author, not because it's PAM. I have no > problem with PAM, and I think citing old security flaws as reasoning > is silly. Mainstream distributions are getting along fine, and it > affords them Nice Things that Slackware just Can't Have. > > That said, if Slackware is to get PAM, I'd much rather see it come from > PV or his team. I think it integrates too tightly with the system for > it to be something we host at SBo. It's true, but to integrate PAM into the system is not difficult when there ready infrastructure. I guess this sla?kbild in queue is engaged in its creation. In my opinion it is very convenient for those who need it. -- Murat D. Kadirov PGP fingerprint: 3081 EBFA 5CB9 BD24 4DB6 76EE 1B97 0A0E CEC0 6AA0 From chris.abela at maltats.com Fri Oct 22 11:13:26 2010 From: chris.abela at maltats.com (Chris Abela) Date: Fri, 22 Oct 2010 13:13:26 +0200 Subject: [Slackbuilds-users] LinuxPAM has been in the pending queue for months. In-Reply-To: <20101022044426.5fe8ca6c@shaggy.doo> Message-ID: If any good soul out there may forward me a copy of this despicable SlackBuild I will see personally in reporting back why the Slack Police ought to scan our machines for any trace of Swiss cheese on routine basis. -----Original Message----- From: slackbuilds-users-bounces at slackbuilds.org [mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of Erik Hanson Sent: 22 October 2010 11:44 To: slackbuilds-users at slackbuilds.org Subject: Re: [Slackbuilds-users] LinuxPAM has been in the pending queue for months. On Fri, 22 Oct 2010 00:07:21 -0700 (PDT) crocket wrote: > It seems LinuxPAM doesn't attract enough attention. > Somebody needs to do something about this. I suppose I can throw my opinion at this. I haven't looked at this script. Not because of the author, not because it's PAM. I have no problem with PAM, and I think citing old security flaws as reasoning is silly. Mainstream distributions are getting along fine, and it affords them Nice Things that Slackware just Can't Have. That said, if Slackware is to get PAM, I'd much rather see it come from PV or his team. I think it integrates too tightly with the system for it to be something we host at SBo. -- Erik Hanson From rshepard at appl-ecosys.com Fri Oct 22 23:18:58 2010 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 22 Oct 2010 16:18:58 -0700 (PDT) Subject: [Slackbuilds-users] Problems Building PostgreSQL-8.4.5 Message-ID: This is on a new system (mb, memory, cpu) with fresh install of 13.1. I'm using the SlackBuild script for postgres-8.4.5 so I can upgrade from the current -8.3.3. The configure step fails: checking libxml/parser.h usability... no checking libxml/parser.h presence... no checking for libxml/parser.h... no configure: error: header file is required for XML support However, parser.h is in the libxml2 package and installed here: [root at salmo /usr/include/libxml2/libxml]# ls parser.h parser.h What do I do to have the script run correctly? Rich From rshepard at appl-ecosys.com Fri Oct 22 23:22:49 2010 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 22 Oct 2010 16:22:49 -0700 (PDT) Subject: [Slackbuilds-users] Problems Building PostgreSQL-8.4.5 In-Reply-To: References: Message-ID: On Fri, 22 Oct 2010, Rich Shepard wrote: > This is on a new system (mb, memory, cpu) with fresh install of 13.1. Sorry. It's 13.0 not 13.1. Rich From xgizzmo at slackbuilds.org Fri Oct 22 23:24:28 2010 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Fri, 22 Oct 2010 19:24:28 -0400 Subject: [Slackbuilds-users] LinuxPAM has been in the pending queue for months. In-Reply-To: References: Message-ID: <201010221924.28837.xgizzmo@slackbuilds.org> On Friday 22 October 2010 07:13:26 Chris Abela wrote: > If any good soul out there may forward me a copy of this despicable > SlackBuild I will see personally in reporting back why the Slack Police > ought to scan our machines for any trace of Swiss cheese on routine basis. > Building Linux-Pam is not much more than stock configure, make, make install. The thing is just installing Linux-Pam does not give you a working pam enabled system. I do not think it is appropriate to send out copies of a build in pending. --dsomero From crockabiscuit at yahoo.com Sat Oct 23 04:14:16 2010 From: crockabiscuit at yahoo.com (crocket) Date: Fri, 22 Oct 2010 21:14:16 -0700 (PDT) Subject: [Slackbuilds-users] I want to remove conkyfonts and aquafont from the pending queue. Message-ID: <798881.87582.qm@web120320.mail.ne1.yahoo.com> Those packages are not yet complete. I want to resubmit them after having extra time to make them sufficient. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Sat Oct 23 04:27:31 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 22 Oct 2010 23:27:31 -0500 Subject: [Slackbuilds-users] I want to remove conkyfonts and aquafont from the pending queue. In-Reply-To: <798881.87582.qm@web120320.mail.ne1.yahoo.com> References: <798881.87582.qm@web120320.mail.ne1.yahoo.com> Message-ID: <20101022232731.31752178@liberty> On Fri, 22 Oct 2010 21:14:16 -0700 (PDT) crocket wrote: > Those packages are not yet complete. > > I want to resubmit them after having extra time to make them > sufficient. Removed. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From crockabiscuit at yahoo.com Sat Oct 23 10:06:22 2010 From: crockabiscuit at yahoo.com (crocket) Date: Sat, 23 Oct 2010 03:06:22 -0700 (PDT) Subject: [Slackbuilds-users] ibus slackbuild has gone missing from slackbuilds.org. Message-ID: <960922.65359.qm@web120319.mail.ne1.yahoo.com> I chcked it today and it was missing. http://slackbuilds.org/repository/13.1/desktop/ibus/ is the webpage for ibus slackbuild. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozan.turkyilmaz at gmail.com Sat Oct 23 10:13:26 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 23 Oct 2010 13:13:26 +0300 Subject: [Slackbuilds-users] ibus slackbuild has gone missing from slackbuilds.org. In-Reply-To: <960922.65359.qm@web120319.mail.ne1.yahoo.com> References: <960922.65359.qm@web120319.mail.ne1.yahoo.com> Message-ID: 2010/10/23 crocket : > I chcked it today and it was missing. > > http://slackbuilds.org/repository/13.1/desktop/ibus/ is the webpage for ibus > slackbuild. > I'm seeing the same problem, Files are missing. -- Ozan, BSc, BEng From xgizzmo at slackbuilds.org Sat Oct 23 10:19:35 2010 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Sat, 23 Oct 2010 06:19:35 -0400 Subject: [Slackbuilds-users] ibus slackbuild has gone missing from slackbuilds.org. In-Reply-To: References: <960922.65359.qm@web120319.mail.ne1.yahoo.com> Message-ID: <201010230619.35817.xgizzmo@slackbuilds.org> On Saturday 23 October 2010 06:13:26 Ozan T?rky?lmaz wrote: > 2010/10/23 crocket : > > I chcked it today and it was missing. > > > > http://slackbuilds.org/repository/13.1/desktop/ibus/ is the webpage for ibus > > slackbuild. > > > > I'm seeing the same problem, Files are missing. > > Fixed, The SlackBuild is in misc not desktop. --dsomero From adis at linux.org.ba Sat Oct 23 15:00:32 2010 From: adis at linux.org.ba (Adis Nezirovic) Date: Sat, 23 Oct 2010 17:00:32 +0200 Subject: [Slackbuilds-users] Problems Building PostgreSQL-8.4.5 In-Reply-To: References: Message-ID: Hi Rich If you don't need "xml" functionality, you can just remove the following "configure" options from the build script: --with-libxml --with-libxslt Meanwhile, I've submitted slackbuild for PostgreSQL 9.0.1 a few days ago, if you have time, you can wait for that version. In any case, if you need any help please drop me an email, I would be glad to help you. Best regards, Adis From rshepard at appl-ecosys.com Sat Oct 23 16:13:18 2010 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 23 Oct 2010 09:13:18 -0700 (PDT) Subject: [Slackbuilds-users] Problems Building PostgreSQL-8.4.5 In-Reply-To: References: Message-ID: On Sat, 23 Oct 2010, Adis Nezirovic wrote: > If you don't need "xml" functionality, you can just remove the following > "configure" options from the build script: > --with-libxml > --with-libxslt Adis, I thought of that, but I've no idea whether I need xml functionality. Certainly nothing in SQL-Ledger, CMS Made Simple, my scientific references, or collabnet. When I add spatial data with postGIS I don't think I'll need xml capabilities either. > Meanwhile, I've submitted slackbuild for PostgreSQL 9.0.1 a few days ago, > if you have time, you can wait for that version. In any case, if you need > any help please drop me an email, I would be glad to help you. I'll do the upgrade in two steps. I'll give pg_migrator a try and that's specific for the 8.3->8.4 upgrade, then the same tool with a different name is in contrib for 9.0 so I'll do that separately. While on the subject of the postgres package, I discovered this week why I've had difficulties starting the postmaster after a reboot. First, the original rc.postgresql script had 'su postgres -c ...' and it needs to be 'su - postgres -c ...'. Yet that change didn't make a difference. For some reason, when the script is run by root (at least here, over several Slackware versions and hardware changes) the postgres -D /var/lib/pgsql/data & command is not implemented. However, if I work manually on the command line, in two steps: $ su -c postgres $ password: $ postgres -D /var/lib/pgsql/data & it works flawlessly because I've entered postgres' password. Many thanks, Rich -- Richard B. Shepard, Ph.D. | The Plain English Science Consultant Applied Ecosystem Services, Inc. | Helping Ensure Our Clients' Futures Voice: 503-667-4517 Fax: 503-667-8863 From SlackBuilds at catcons.co.uk Sat Oct 23 16:33:35 2010 From: SlackBuilds at catcons.co.uk (SlackBuilds at catcons.co.uk) Date: Sat, 23 Oct 2010 22:03:35 +0530 Subject: [Slackbuilds-users] hddtemp source download link is broken Message-ID: <001101cb72d0$0bcc8d30$0f02000a@cw8xp> Hello :-) The 13.1 hddtemp source download link (http://www.very-clever.com/download/nongnu/hddtemp/hddtemp-0.3-beta15.tar.b z2) gave a 404 error on 18, 19, 22 October and again when tested just now. The source can be downloaded from http://download.savannah.gnu.org/releases/hddtemp/hddtemp-0.3-beta15.tar.bz2 which is in the same domain as hddtemp's homepage, https://savannah.nongnu.org/projects/hddtemp/ Best Charles From crockabiscuit at yahoo.com Sun Oct 24 09:18:41 2010 From: crockabiscuit at yahoo.com (crocket) Date: Sun, 24 Oct 2010 02:18:41 -0700 (PDT) Subject: [Slackbuilds-users] ndiswrapper can't be built. Message-ID: <960407.40433.qm@web120320.mail.ne1.yahoo.com> I tried to build ndiswrapper with ndiswrapper slackbuild. But I encountered errors. They are included as result1.txt in this message. Since they were caused by lack of wireless extension in kernel, I recompiled kernel and tried again to build ndiswrapper. This time I encountered another set of errors. The errors are included as result2.txt in this message. It seems like ndiswrapper needs a patch to be built fine. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: result1.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: result2.txt URL: From niels.horn at gmail.com Sun Oct 24 10:55:47 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sun, 24 Oct 2010 08:55:47 -0200 Subject: [Slackbuilds-users] ndiswrapper can't be built. In-Reply-To: <960407.40433.qm@web120320.mail.ne1.yahoo.com> References: <960407.40433.qm@web120320.mail.ne1.yahoo.com> Message-ID: On Sun, Oct 24, 2010 at 7:18 AM, crocket wrote: > I tried to build ndiswrapper with ndiswrapper slackbuild. > But I encountered errors. They are included as result1.txt in this message. > > Since they were caused by lack of wireless extension in kernel, I recompiled > kernel and tried again > to build ndiswrapper. > This time I encountered another set of errors. > The errors are included as result2.txt in this message. > > It seems like ndiswrapper needs a patch to be built fine. > > ndiswrapper built fine here on a clean 13.1 system. Did you use the KERNEL= parameter like mentioned in the README? Niels From niels.horn at gmail.com Sun Oct 24 11:23:45 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sun, 24 Oct 2010 09:23:45 -0200 Subject: [Slackbuilds-users] ndiswrapper can't be built. In-Reply-To: References: <960407.40433.qm@web120320.mail.ne1.yahoo.com> Message-ID: On Sun, Oct 24, 2010 at 8:55 AM, Niels Horn wrote: > On Sun, Oct 24, 2010 at 7:18 AM, crocket wrote: >> I tried to build ndiswrapper with ndiswrapper slackbuild. >> But I encountered errors. They are included as result1.txt in this message. >> >> Since they were caused by lack of wireless extension in kernel, I recompiled >> kernel and tried again >> to build ndiswrapper. >> This time I encountered another set of errors. >> The errors are included as result2.txt in this message. >> >> It seems like ndiswrapper needs a patch to be built fine. >> >> > > ndiswrapper built fine here on a clean 13.1 system. > > Did you use the KERNEL= parameter like mentioned in the README? > > Niels > Never mind my previous message... You might try the latest unstable version from svn. It seems to include some patches to make it work on newer kernels, including the multicast changes that stopped your build. Niels From matteo.bernardini at sns.it Sun Oct 24 11:30:09 2010 From: matteo.bernardini at sns.it (Matteo Bernardini) Date: Sun, 24 Oct 2010 13:30:09 +0200 Subject: [Slackbuilds-users] ndiswrapper can't be built. In-Reply-To: References: <960407.40433.qm@web120320.mail.ne1.yahoo.com> Message-ID: <4CC418C1.1030106@sns.it> On 24/10/2010 13:23, Niels Horn wrote: > You might try the latest unstableversion from svn. It seems to include > some patches to make it work on newer kernels, including the multicast > changes that stopped your build. if useful, I prepared a tarball of r2728 for a linuxquestions user that needed it http://ponce.cc/slackware/sources/repo/ndiswrapper-r2728.tar.gz Matteo From niels.horn at gmail.com Sun Oct 24 11:40:06 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sun, 24 Oct 2010 09:40:06 -0200 Subject: [Slackbuilds-users] ndiswrapper can't be built. In-Reply-To: <4CC418C1.1030106@sns.it> References: <960407.40433.qm@web120320.mail.ne1.yahoo.com> <4CC418C1.1030106@sns.it> Message-ID: On Sun, Oct 24, 2010 at 9:30 AM, Matteo Bernardini wrote: > On 24/10/2010 13:23, Niels Horn wrote: >> >> You might try the latest unstableversion from svn. It seems to include >> some patches to make it work on newer kernels, including the multicast >> changes that stopped your ?build. > > if useful, I prepared a tarball of r2728 for a linuxquestions user that > needed it > > http://ponce.cc/slackware/sources/repo/ndiswrapper-r2728.tar.gz > > Matteo Matteo, You were faster than me :) I just checked out revision 2728 myself and it builds fine on -current (w/ kernel 2.6.35.7). Niels From rshepard at appl-ecosys.com Sun Oct 24 23:06:51 2010 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 24 Oct 2010 16:06:51 -0700 (PDT) Subject: [Slackbuilds-users] Problems Building PostgreSQL-8.4.5 In-Reply-To: References: Message-ID: On Sat, 23 Oct 2010, Adis Nezirovic wrote: > In any case, if you need any help please drop me an email, I would be glad > to help you. Adis, I am curious why the SlackBuilds packages install into /var/lib/ instead of /usr/local/ as the non-SlackBuild packages do. Thanks, Rich -- Richard B. Shepard, Ph.D. | The Plain English Science Consultant Applied Ecosystem Services, Inc. | Helping Ensure Our Clients' Futures Voice: 503-667-4517 Fax: 503-667-8863 From rworkman at slackbuilds.org Sun Oct 24 23:24:48 2010 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 24 Oct 2010 18:24:48 -0500 Subject: [Slackbuilds-users] Problems Building PostgreSQL-8.4.5 In-Reply-To: References: Message-ID: <20101024182448.732ad990@liberty> On Sun, 24 Oct 2010 16:06:51 -0700 (PDT) Rich Shepard wrote: > Adis, > > I am curious why the SlackBuilds packages install into /var/lib/ > instead of /usr/local/ as the non-SlackBuild packages do. That's because /usr/local is the domain of the system administrator. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rshepard at appl-ecosys.com Mon Oct 25 00:02:59 2010 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 24 Oct 2010 17:02:59 -0700 (PDT) Subject: [Slackbuilds-users] Problems Building PostgreSQL-8.4.5 In-Reply-To: <20101024182448.732ad990@liberty> References: <20101024182448.732ad990@liberty> Message-ID: On Sun, 24 Oct 2010, Robby Workman wrote: > That's because /usr/local is the domain of the system administrator. Robby, I thought that /usr was, too, and that non-distribution-included packages would be installed in /usr/local or /opt. Thanks, Rich From didier.spaier at epsm.fr Mon Oct 25 11:25:04 2010 From: didier.spaier at epsm.fr (Didier Spaier) Date: Mon, 25 Oct 2010 13:25:04 +0200 Subject: [Slackbuilds-users] Problems Building PostgreSQL-8.4.5 In-Reply-To: References: <20101024182448.732ad990@liberty> Message-ID: <4CC56910.9080404@epsm.fr> Le 25/10/2010 02:02, Rich Shepard a ?crit : > On Sun, 24 Oct 2010, Robby Workman wrote: > >> That's because /usr/local is the domain of the system administrator. > > Robby, > > I thought that /usr was, too, and that non-distribution-included packages > would be installed in /usr/local or /opt. /var/lib : Variable state information Purpose This hierarchy holds state information pertaining to an application or the system. State information is data that programs modify while they run, and that pertains to one specific host. Users must never need to modify files in /var/lib to configure a package's operation. State information is generally used to preserve the condition of an application (or a group of inter-related applications) between invocations and between different instances of the same application. State information should generally remain valid after a reboot, should not be logging output, and should not be spooled data. An application (or a group of inter-related applications) must use a subdirectory of /var/lib for its data. There is one required subdirectory, /var/lib/misc, which is intended for state files that don't need a subdirectory; the other subdirectories should only be present if the application in question is included in the distribution. [38] /var/lib/ is the location that must be used for all distribution packaging support. Different distributions may use different names, of course. As long as /var/lib is used to hold database records, I suppose this choice conforms to the FHS. Didier From erik at slackbuilds.org Mon Oct 25 13:11:37 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Mon, 25 Oct 2010 08:11:37 -0500 Subject: [Slackbuilds-users] Updates - 20101025.1 Message-ID: <20101025081137.34562c3d@shaggy.doo> Mon Oct 25 12:58:42 UTC 2010 academic/gerbv: Added (viewer for Gerber RS-274X files) acadenic/xoscope: Added (digital oscilloscope) audio/atunes: Added (full-featured audio player and manager) audio/pianobar: Added (console Pandora client) audio/podget: Added (simple podcast aggregator) desktop/scrotwm: Updated for version 0.9.27. desktop/smooth-tasks: Added (task tray for KDE4) desktop/transset-df: Added (patched version of xorg's transset) development/arduino: Added (IDE) development/javacc: Added (Java Compiler Compiler [tm]) development/kicad-doc: Added (documentation for KiCad EDA Suite) development/kicad-library: Added (library for KiCad EDA Suite) development/kicad: Added (Open Source EDA Suite) development/numexpr: Added (numerical array expression evaluator) development/valgrind: Updated for version 3.6.0. development/wxHexEditor: Added (Free Hex Editor) games/fortune-dharma: Added (dharma for fortune) games/qjoypad: Added (control XWindow programs with game controller) games/spring: Added (a powerful free RTS engine) games/wesnoth: Updated for version 1.8.5. graphics/exact-image: Updated for version 0.8.3. graphics/fritzing: Added (electronic prototyping) liberaties/perl-DBD-SQLite: Added (RDBMS perl module) libraries/GLee: Added (GL Easy Extension library) libraries/apiextractor: Added (Api Extractor) libraries/gnonlin: Added (non-linear video editors library) libraries/libdbi: Updated for version 0.8.4. libraries/nettle: Added (low-level cryptographic library) libraries/perl-Audio-FLAC-Header: Added (interface to FLAC headers) libraries/perl-MP3-Info: Added. (Manipulate MP3 audio files) libraries/perl-Net-UPnP: Added. (perl extensions for Net-UPnP) libraries/perl-Ogg-Vorbis-Header-PurePerl: Added (ogg perl module) libraries/perl-dbd-sqlite: removed (replaced by perl-DBD-SQLite) misc/ibus: Updated for version 1.3.8. misc/siege: Updated for version 2.70. misc/xvnkb: Added (Vietnamese keyboard input for X-Window) multimedia/dvdauthor: Updated for version 0.7.0. network/APC: Added (The Alternative PHP Cache) network/bitlbee: Updated for version 3.0. network/chromium: Updated for version 8.0.558.0. network/chrony: Added. (maintain accuracy of RLT Clock over ntp). network/google-chrome: Updated for version 7.0.517.41. network/iperf: Updated for version 2.0.5. network/mysecureshell: Added (sftp server based on OpenSSH) network/python-demjson: Added (Encoder, decoder, and lint/validator) network/python-morbid: Added (messaging server) network/python-orbited: Added (RT Communication for the Browser) network/python-stomper: Added (client for the STOMP protocol) network/python-uuid: Added (UUID object and generation functions) network/uwsgi: Added (fast Python WSGI server) office/elyxer: Added (Lyx to HTML converter) office/gummi: Updated for version 0.5.2. office/pdf2djvu: Added (creates DjVu files from PDF files) office/zathura: Added (PDF viewer focusing on keyboard interaction) system/aide: Added (Advanced Intrusion Detection Environment) system/atop: Add an install statement for the atoprc(5) manpage. system/audit: Updated for version 2.0.5. system/bar: Updated for version 1.11.0. system/chrpath: Added (modify rpath of binaries) system/duplicity: Added (Encrypted backup using rsync algorithm) system/extundelete: Added (ext3 and ext4 undeletion utility) system/glyptodon: Added. (file-system analyzer). system/pigz: Added (Parallel gzip) system/postgresql: Updated for version 9.0.1. system/qemu-kvm: Updated for version 0.13.0. system/rdup: Added (utility to create a list for making backups) system/winetricks: Updated for version 20101008. From rshepard at appl-ecosys.com Mon Oct 25 13:17:07 2010 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 25 Oct 2010 06:17:07 -0700 (PDT) Subject: [Slackbuilds-users] Problems Building PostgreSQL-8.4.5 In-Reply-To: <4CC56910.9080404@epsm.fr> References: <20101024182448.732ad990@liberty> <4CC56910.9080404@epsm.fr> Message-ID: On Mon, 25 Oct 2010, Didier Spaier wrote: > This hierarchy holds state information pertaining to an application or the > system. State information is data that programs modify while they run, and > that pertains to one specific host. Users must never need to modify files > in /var/lib to configure a package's operation. Didier, Thank you. Makes good sense to me. Much appreciated, Rich From nishant at mnspace.net Tue Oct 26 02:38:26 2010 From: nishant at mnspace.net (Nishant Limbachia) Date: Mon, 25 Oct 2010 21:38:26 -0500 Subject: [Slackbuilds-users] Updates - 20101025.1 In-Reply-To: <20101025081137.34562c3d@shaggy.doo> References: <20101025081137.34562c3d@shaggy.doo> Message-ID: <4CC63F22.5030203@mnspace.net> On 10/25/2010 08:11 AM, Erik Hanson wrote: > libraries/perl-Net-UPnP: Added. (perl extensions for Net-UPnP) Seems like this one got mangled somewhere. No files are shown on the page. From erik at slackbuilds.org Tue Oct 26 02:47:02 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Mon, 25 Oct 2010 21:47:02 -0500 Subject: [Slackbuilds-users] Updates - 20101025.1 In-Reply-To: <4CC63F22.5030203@mnspace.net> References: <20101025081137.34562c3d@shaggy.doo> <4CC63F22.5030203@mnspace.net> Message-ID: <20101025214702.45673cf6@shaggy.doo> On Mon, 25 Oct 2010 21:38:26 -0500 Nishant Limbachia wrote: > On 10/25/2010 08:11 AM, Erik Hanson wrote: > > libraries/perl-Net-UPnP: Added. (perl extensions for Net-UPnP) Fixed. -- 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 druiloor at zonnet.nl Tue Oct 26 19:22:33 2010 From: druiloor at zonnet.nl (Menno Duursma) Date: Tue, 26 Oct 2010 21:22:33 +0200 (CEST) Subject: [Slackbuilds-users] Maintainership Message-ID: Hi all, I'd like to give up maintainership of the following scripts. Also including: pending/phrel.tar.gz Most i'm not currently using and i'd like to focus on other things. menno at pc:~$ find /var/lib/sbopkg/SBo/13.1 -name \*.info -exec grep -H druiloor@ {} \; | cut -d/ -f7,8 development/lua development/splint development/vic development/empty games/xbill libraries/agg libraries/cbase libraries/gnet libraries/gsnmp libraries/libcap-ng libraries/liboop libraries/libssh2 libraries/python-prctl libraries/php-htscanner libraries/php-ssh2 libraries/php-suhosin misc/keychain misc/misctools misc/siege misc/authprogs misc/ssh-keyinstall network/arptables network/dnsflood network/dnstop network/dnstracer network/heimdal network/mod_chroot network/mod_evasive network/mod_hosts_access network/mod_limitipconn network/nss-mdns network/scli network/suphp network/unfs3 network/lsh system/apachetop system/atop system/cage system/cdcopy system/cfengine system/chkconfig system/conserver system/cpulimit system/nss-mysql system/numlockx system/sash system/tiger system/bar system/watchdog Take care, -Menno. From matteo.bernardini at sns.it Tue Oct 26 19:58:13 2010 From: matteo.bernardini at sns.it (Matteo Bernardini) Date: Tue, 26 Oct 2010 21:58:13 +0200 Subject: [Slackbuilds-users] Maintainership In-Reply-To: References: Message-ID: <4CC732D5.9000906@sns.it> On 26/10/2010 21:22, Menno Duursma wrote: > development/lua > libraries/agg > network/mod_evasive > system/apachetop I can take care of these, if it's ok for you. Matteo From niels.horn at gmail.com Tue Oct 26 20:53:02 2010 From: niels.horn at gmail.com (Niels Horn) Date: Tue, 26 Oct 2010 18:53:02 -0200 Subject: [Slackbuilds-users] Maintainership In-Reply-To: References: Message-ID: On Tue, Oct 26, 2010 at 5:22 PM, Menno Duursma wrote: > > Hi all, > > I'd like to give up maintainership of the following scripts. > Also including: pending/phrel.tar.gz > > Most i'm not currently using and i'd like to focus on other things. > system/numlockx Apart from lua, which Matteo offered to maintain, numlockx is the only one I install and use on al my systems. And it won't be a huge workload to maintain :) > > Take care, > -Menno. Regards, Niels From grbzks at xsmail.com Tue Oct 26 21:00:30 2010 From: grbzks at xsmail.com (Grigorios Bouzakis) Date: Wed, 27 Oct 2010 00:00:30 +0300 Subject: [Slackbuilds-users] Maintainership In-Reply-To: References: Message-ID: <1288126830.11561.1402097379@webmail.messagingengine.com> On Tue, 26 Oct 2010 21:22 +0200, "Menno Duursma" wrote: > > Hi all, > > I'd like to give up maintainership of the following scripts. > misc/keychain > > Take care, > -Menno. I could pick up keychain :) --- Greg From estranho at diogoleal.com Tue Oct 26 21:04:56 2010 From: estranho at diogoleal.com (Diogo Leal) Date: Tue, 26 Oct 2010 19:04:56 -0200 Subject: [Slackbuilds-users] Maintainership In-Reply-To: <1288126830.11561.1402097379@webmail.messagingengine.com> References: <1288126830.11561.1402097379@webmail.messagingengine.com> Message-ID: Hello, I would assume these packages. network/dnsflood network/dnstop network/dnstracer network/mod_chroot network/mod_evasive network/mod_hosts_access network/mod_limitipconn system/apachetop system/atop Diogo Leal [aka estranho] http://diogoleal.com msn | gtalk: estranho at diogoleal.com On Tue, Oct 26, 2010 at 7:00 PM, Grigorios Bouzakis wrote: > On Tue, 26 Oct 2010 21:22 +0200, "Menno Duursma" > wrote: >> >> Hi all, >> >> I'd like to give up maintainership of the following scripts. >> misc/keychain >> >> Take care, >> -Menno. > > I could pick up keychain :) > > --- > Greg > _______________________________________________ > 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 ozan.turkyilmaz at gmail.com Tue Oct 26 21:18:34 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Wed, 27 Oct 2010 00:18:34 +0300 Subject: [Slackbuilds-users] Maintainership In-Reply-To: References: Message-ID: 010/10/26 Menno Duursma : > development/splint > libraries/cbase >libraries/gnet >libraries/gsnmp >libraries/libcap-ng >libraries/liboop I can take over them. -- Ozan, BSc, BEng From hba.nihilismus at gmail.com Tue Oct 26 22:55:57 2010 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Tue, 26 Oct 2010 17:55:57 -0500 Subject: [Slackbuilds-users] Maintainership. Message-ID: Hi all. Sorry for the inconvenience (if any), but at this moment i can?t keep an eye on any of my slackbuilds so if there?s anyone who wants to take care of them, go ahead: misc/chmlib-examples desktop/wmii audio/cmus games/zsnes libraries/libixp development/eclipse development/netbeans development/xdebug network/axel network/vde2 network/hiawatha network/thttpd system/ibam system/plan9port system/terminus-font system/tp_smapi If you want to be their maintainer and have a doubt with any of them (shell script), drop me an email to see if i can help you. -- - hba From bmg.andre at gmail.com Tue Oct 26 23:54:50 2010 From: bmg.andre at gmail.com (=?ISO-8859-1?Q?Andr=E9_Barboza?=) Date: Tue, 26 Oct 2010 21:54:50 -0200 Subject: [Slackbuilds-users] Maintainership. In-Reply-To: References: Message-ID: I can take of those: development/eclipse development/netbeans 2010/10/26 Antonio Hern?ndez Blas : > Hi all. > > Sorry for the inconvenience (if any), but at this moment i can?t keep > an eye on any of my slackbuilds so if there?s anyone who wants to take > care of them, go ahead: > > misc/chmlib-examples > desktop/wmii > audio/cmus > games/zsnes > libraries/libixp > development/eclipse > development/netbeans > development/xdebug > network/axel > network/vde2 > network/hiawatha > network/thttpd > system/ibam > system/plan9port > system/terminus-font > system/tp_smapi > > If you want to be their maintainer and have a doubt with any of them > (shell script), drop me an email to see if i can help you. > > -- > - 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 binhnguyen at fastmail.fm Wed Oct 27 00:52:44 2010 From: binhnguyen at fastmail.fm (Binh Nguyen) Date: Wed, 27 Oct 2010 07:52:44 +0700 Subject: [Slackbuilds-users] Maintainership. In-Reply-To: References: Message-ID: <20101027075244.441c0065@darkstar.example.net> On Tue, 26 Oct 2010 17:55:57 -0500 Antonio Hern?ndez Blas wrote: > Hi all. > > Sorry for the inconvenience (if any), but at this moment i can?t keep > an eye on any of my slackbuilds so if there?s anyone who wants to take > care of them, go ahead: > > system/terminus-font > I can take care of this. -- Binh Nguyen From bkirkp at gmail.com Wed Oct 27 02:47:33 2010 From: bkirkp at gmail.com (Bill Kirkpatrick) Date: Tue, 26 Oct 2010 21:47:33 -0500 Subject: [Slackbuilds-users] Maintainership. In-Reply-To: References: Message-ID: I've been a steady user of terminus-font. I can take it. Bill Kirkpatrick TSquaredF 2010/10/26 Antonio Hern?ndez Blas > Hi all. > > Sorry for the inconvenience (if any), but at this moment i can?t keep > an eye on any of my slackbuilds so if there?s anyone who wants to take > care of them, go ahead: > > misc/chmlib-examples > desktop/wmii > audio/cmus > games/zsnes > libraries/libixp > development/eclipse > development/netbeans > development/xdebug > network/axel > network/vde2 > network/hiawatha > network/thttpd > system/ibam > system/plan9port > system/terminus-font > system/tp_smapi > > If you want to be their maintainer and have a doubt with any of them > (shell script), drop me an email to see if i can help you. > > -- > - 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 carlos at strangeworlds.co.uk Wed Oct 27 07:11:33 2010 From: carlos at strangeworlds.co.uk (Carlos Corbacho) Date: Wed, 27 Oct 2010 08:11:33 +0100 Subject: [Slackbuilds-users] Maintainership. In-Reply-To: References: Message-ID: <201010270811.33882.carlos@strangeworlds.co.uk> On Tuesday 26 October 2010 23:55:57 Antonio Hern?ndez Blas wrote: > Hi all. > > Sorry for the inconvenience (if any), but at this moment i can?t keep > an eye on any of my slackbuilds so if there?s anyone who wants to take > care of them, go ahead: [..] > games/zsnes I can take zsnes, -Carlos -- E-Mail: carlos at strangeworlds.co.uk Web: strangeworlds.co.uk GPG Key ID: 0x23EE722D From matteo.bernardini at sns.it Wed Oct 27 07:39:15 2010 From: matteo.bernardini at sns.it (Matteo Bernardini) Date: Wed, 27 Oct 2010 09:39:15 +0200 Subject: [Slackbuilds-users] Maintainership. In-Reply-To: References: Message-ID: <4CC7D723.2060703@sns.it> Il 27/10/2010 00:55, Antonio Hern?ndez Blas ha scritto: > audio/cmus I use it a lot, I can take care of this if it's ok for you. Matteo From SlackBuilds at catcons.co.uk Wed Oct 27 08:08:20 2010 From: SlackBuilds at catcons.co.uk (SlackBuilds at catcons.co.uk) Date: Wed, 27 Oct 2010 13:38:20 +0530 Subject: [Slackbuilds-users] Submitted SlackBuild for yad then realised not best download link Message-ID: <002201cb75ae$2156d850$0f02000a@cw8xp> Hello :-) 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" Best Charles From bailey at akamai.com Wed Oct 27 18:00:38 2010 From: bailey at akamai.com (R. Andrew Bailey) Date: Wed, 27 Oct 2010 14:00:38 -0400 Subject: [Slackbuilds-users] category correction for "argus" Message-ID: <20101027180038.GM12118@akamai.com> 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". Thanks, .andy From joao.eel at gmail.com Wed Oct 27 21:24:16 2010 From: joao.eel at gmail.com (=?ISO-8859-1?Q?Jo=E3o_Felipe_Santos?=) Date: Wed, 27 Oct 2010 19:24:16 -0200 Subject: [Slackbuilds-users] Maintainership Message-ID: Hello all, My Slackware desktop isn't working anymore and right now I do not have the time to have a new one set up. Because of that, I will not maintain any of my SlackBuilds until the end of the year. It's my final year at the university, so I will need all the time I can find to work on my thesis! These are the scripts I was maintaining: academic/scipy academic/sympy libraries/pychm libraries/matplotlib libraries/libtbb misc/chm2pdf Feel free to assume maintainership for any one of those. -- Jo?o Felipe Santos From ozan.turkyilmaz at gmail.com Wed Oct 27 22:00:13 2010 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Thu, 28 Oct 2010 01:00:13 +0300 Subject: [Slackbuilds-users] Maintainership In-Reply-To: References: Message-ID: 2010/10/28 Jo?o Felipe Santos : > libraries/libtbb > misc/chm2pdf > I can take over this two. -- Ozan, BSc, BEng From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Thu Oct 28 09:58:47 2010 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Thu, 28 Oct 2010 11:58:47 +0200 Subject: [Slackbuilds-users] Maintainership In-Reply-To: References: Message-ID: <4CC94957.10308@skmail.ikp.physik.tu-darmstadt.de> Jo?o Felipe Santos wrote: > Hello all, > > My Slackware desktop isn't working anymore and right now I do not have the > > ... Hello! I'll take this three over. > ... > academic/scipy > academic/sympy > libraries/matplotlib > ... BTW, I was quite sure that Jo?o also took over numpy some time ago (see http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-May/005709.html ). But it looks like this is not the case. Grissiom, who thought I'm maintaining numpy (because of http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-February/005185.html )(*), wrote me these days about the newest released version and asked if I could update the script. Thus if Alexander, who is still mentioned as maintainer, has nothing against, I'll also take over numpy. Best regards, Serban (*) I actually intended to do it at that time, but had too much to do at work and somehow forgot. And then there was the already mentioned message from Jo?o. From asamardzic at gmail.com Thu Oct 28 10:30:06 2010 From: asamardzic at gmail.com (Aleksandar Samardzic) Date: Thu, 28 Oct 2010 12:30:06 +0200 Subject: [Slackbuilds-users] Maintainership In-Reply-To: <4CC94957.10308@skmail.ikp.physik.tu-darmstadt.de> References: <4CC94957.10308@skmail.ikp.physik.tu-darmstadt.de> Message-ID: On Thu, Oct 28, 2010 at 11:58 AM, Serban Udrea wrote: > > [ ... ] > > BTW, I was quite sure that Jo?o also took over numpy some time ago (see > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-May/005709.html > ). But it looks like this is not the case. Grissiom, who thought I'm > maintaining numpy (because of > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-February/005185.html > )(*), wrote me these days about the newest released version and asked if I > could update the script. Thus if Alexander, who is still mentioned as > maintainer, has nothing against, I'll also take over numpy. Sorry for the confusion, seems like I lost the track too... In any case, I'll be glad if you take numpy maintenance over - that certainly makes most sense here, as you're going to take the other three from Jo?o. Regards, Alex From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Thu Oct 28 10:35:17 2010 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Thu, 28 Oct 2010 12:35:17 +0200 Subject: [Slackbuilds-users] Maintainership In-Reply-To: References: <4CC94957.10308@skmail.ikp.physik.tu-darmstadt.de> Message-ID: <4CC951E5.6040804@skmail.ikp.physik.tu-darmstadt.de> Aleksandar Samardzic wrote: > On Thu, Oct 28, 2010 at 11:58 AM, Serban Udrea > wrote: >> [ ... ] >> >> BTW, I was quite sure that Jo?o also took over numpy some time ago (see >> http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-May/005709.html >> ). But it looks like this is not the case. Grissiom, who thought I'm >> maintaining numpy (because of >> http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-February/005185.html >> )(*), wrote me these days about the newest released version and asked if I >> could update the script. Thus if Alexander, who is still mentioned as >> maintainer, has nothing against, I'll also take over numpy. > > Sorry for the confusion, seems like I lost the track too... In any > case, I'll be glad if you take numpy maintenance over - that certainly > makes most sense here, as you're going to take the other three from > Jo?o. Fine, then it's clear now :-) Best regards, Serban From erik at slackbuilds.org Thu Oct 28 13:00:35 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Thu, 28 Oct 2010 08:00:35 -0500 Subject: [Slackbuilds-users] Maintainership Message-ID: <20101028080035.09572572@shaggy.doo> For everyone taking over maintenance of recently abandoned scripts, aside from letting the list know, could you please submit the scripts with your updated maintainer info. That way we can get them into the repo soon and not have to try and remember what's going on when you submit updates later. Thanks. -- 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 niels.horn at gmail.com Thu Oct 28 22:24:51 2010 From: niels.horn at gmail.com (Niels Horn) Date: Thu, 28 Oct 2010 20:24:51 -0200 Subject: [Slackbuilds-users] Maintainership In-Reply-To: <20101028080035.09572572@shaggy.doo> References: <20101028080035.09572572@shaggy.doo> Message-ID: On Thu, Oct 28, 2010 at 11:00 AM, Erik Hanson wrote: > For everyone taking over maintenance of recently abandoned scripts, > aside from letting the list know, could you please submit the scripts > with your updated maintainer info. That way we can get them into the > repo soon and not have to try and remember what's going on when you > submit updates later. > > Thanks. > > -- > Erik Hanson > Erik, I only "adopted" one abandoned scripts - numlockx. Since an update from upstream was available, I submitted the version bump with some slight changes to the script. Niels From hba.nihilismus at gmail.com Thu Oct 28 23:07:33 2010 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Thu, 28 Oct 2010 18:07:33 -0500 Subject: [Slackbuilds-users] Maintainership In-Reply-To: <20101028080035.09572572@shaggy.doo> References: <20101028080035.09572572@shaggy.doo> Message-ID: On Thu, Oct 28, 2010 at 8:00 AM, Erik Hanson wrote: > For everyone taking over maintenance of recently abandoned scripts, > aside from letting the list know, could you please submit the scripts > with your updated maintainer info. That way we can get them into the > repo soon and not have to try and remember what's going on when you > submit updates later. IMHO i think it would be better to make another threat about this *new policy* and also add it into the FAQ or guidelines. -- - hba From chaos.proton at gmail.com Fri Oct 29 14:06:06 2010 From: chaos.proton at gmail.com (Grissiom) Date: Fri, 29 Oct 2010 22:06:06 +0800 Subject: [Slackbuilds-users] possible bug in laptop_mode Message-ID: Hello all, In the official page of laptop_mode, the dev suggested add `/etc/rc.d/init.d/laptop-mode restart` in rc.local ( http://samwel.tk/laptop_mode/packages/slackware ). But the README in SBo's laptop_mode said we should add `/etc/rc.d/rc.laptop-mode start` in rc.local. i don't know which side is right... The reason of laptop_mode's dev is "Slackware doesn't completely clear /var/run on bootup". But after some investment in rc.S, we are cleaning /var/run (line 328 of that file). So what does "completely" there? Should we use "start" or "restart" in this case? Thanks. -- Cheers, Grissiom From erik at slackbuilds.org Fri Oct 29 17:34:50 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 29 Oct 2010 12:34:50 -0500 Subject: [Slackbuilds-users] Maintainership In-Reply-To: References: <20101028080035.09572572@shaggy.doo> Message-ID: <20101029123450.7901fc37@shaggy.doo> On Thu, 28 Oct 2010 18:07:33 -0500 Antonio Hern?ndez Blas wrote: > On Thu, Oct 28, 2010 at 8:00 AM, Erik Hanson > wrote: > > For everyone taking over maintenance of recently abandoned scripts, > > aside from letting the list know, could you please submit the > > scripts with your updated maintainer info. That way we can get them > > into the repo soon and not have to try and remember what's going on > > when you submit updates later. > > IMHO i think it would be better to make another threat about this *new > policy* and also add it into the FAQ or guidelines. Certainly no threat was made. You quoted me and everyone can see that. There is no new policy, I just want it to be easy for us admins to deal with the lump of recently dropped scripts. I don't think I'm out of line for asking that people do something that makes this a little bit easier for us. Something as simple as submitting new maintainer info now can reduce a lot of hassle later. While a maintainer may submit an update once in a blue moon, we have to deal with submissions every day. I'm sorry you don't understand that we have real lives as well. -- 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 joshuakwood at gmail.com Fri Oct 29 17:38:48 2010 From: joshuakwood at gmail.com (JK Wood) Date: Fri, 29 Oct 2010 12:38:48 -0500 Subject: [Slackbuilds-users] Maintainership In-Reply-To: References: <20101028080035.09572572@shaggy.doo> <20101029123450.7901fc37@shaggy.doo> Message-ID: I'm pretty sure he meant "thread" not "threat." Also, OMG TOP POSTING (Sorry, blame the terrible Android gmail app for that.) On Oct 29, 2010 12:34 PM, "Erik Hanson" wrote: On Thu, 28 Oct 2010 18:07:33 -0500 Antonio Hern?ndez Blas < hba.nihilismus at gmail.com> wrote: > On Th... Certainly no threat was made. You quoted me and everyone can see that. There is no new policy, I just want it to be easy for us admins to deal with the lump of recently dropped scripts. I don't think I'm out of line for asking that people do something that makes this a little bit easier for us. Something as simple as submitting new maintainer info now can reduce a lot of hassle later. While a maintainer may submit an update once in a blue moon, we have to deal with submissions every day. I'm sorry you don't understand that we have real lives as well. -- Erik Hanson _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukenshiro at ngi.it Fri Oct 29 17:48:43 2010 From: lukenshiro at ngi.it (LukenShiro) Date: Fri, 29 Oct 2010 19:48:43 +0200 Subject: [Slackbuilds-users] Maintainership In-Reply-To: <20101029123450.7901fc37@shaggy.doo> References: <20101028080035.09572572@shaggy.doo> <20101029123450.7901fc37@shaggy.doo> Message-ID: <20101029194843.662431eblukenshiro@ngi.it@sigil.norad> Il giorno Fri, 29 Oct 2010 12:34:50 -0500 Erik Hanson ha scritto: > > IMHO i think it would be better to make another threat about this > Certainly no threat was made. You quoted me and everyone can see that. Erik, I guess we got nothing more than a _typo_ in Antonio's message (unfortunately it's a word with a totally different meaning). threat -> thread -- GNU/Linux * Slackware64 current LU #210970 SU #12583 LM #98222/#412913 From hba.nihilismus at gmail.com Fri Oct 29 18:25:29 2010 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Fri, 29 Oct 2010 13:25:29 -0500 Subject: [Slackbuilds-users] Maintainership In-Reply-To: <20101029123450.7901fc37@shaggy.doo> References: <20101028080035.09572572@shaggy.doo> <20101029123450.7901fc37@shaggy.doo> Message-ID: On Fri, Oct 29, 2010 at 12:34 PM, Erik Hanson wrote: > On Thu, 28 Oct 2010 18:07:33 -0500 > Antonio Hern?ndez Blas wrote: > >> On Thu, Oct 28, 2010 at 8:00 AM, Erik Hanson >> wrote: >> > For everyone taking over maintenance of recently abandoned scripts, >> > aside from letting the list know, could you please submit the >> > scripts with your updated maintainer info. That way we can get them >> > into the repo soon and not have to try and remember what's going on >> > when you submit updates later. >> >> IMHO i think it would be better to make another threat about this *new >> policy* and also add it into the FAQ or guidelines. > > > Certainly no threat was made. You quoted me and everyone can see that. > > There is no new policy, I just want it to be easy for us admins to deal > with the lump of recently dropped scripts. I don't think I'm out of > line for asking that people do something that makes this a little bit > easier for us. Something as simple as submitting new maintainer info > now can reduce a lot of hassle later. While a maintainer may submit an > update once in a blue moon, we have to deal with submissions every day. > I'm sorry you don't understand that we have real lives as well. > > > -- > Erik Hanson > Ouch, sorry for the typo, s/threat/thread/... breath more deeply ;) -- - hba From erik at slackbuilds.org Fri Oct 29 18:39:49 2010 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 29 Oct 2010 13:39:49 -0500 Subject: [Slackbuilds-users] Maintainership In-Reply-To: References: <20101028080035.09572572@shaggy.doo> <20101029123450.7901fc37@shaggy.doo> Message-ID: <20101029133949.0a19d00f@shaggy.doo> On Fri, 29 Oct 2010 13:25:29 -0500 Antonio Hern?ndez Blas wrote: > On Fri, Oct 29, 2010 at 12:34 PM, Erik Hanson > wrote: > > On Thu, 28 Oct 2010 18:07:33 -0500 > > Antonio Hern?ndez Blas wrote: > > > >> On Thu, Oct 28, 2010 at 8:00 AM, Erik Hanson > >> wrote: > >> > For everyone taking over maintenance of recently abandoned > >> > scripts, aside from letting the list know, could you please > >> > submit the scripts with your updated maintainer info. That way > >> > we can get them into the repo soon and not have to try and > >> > remember what's going on when you submit updates later. > >> > >> IMHO i think it would be better to make another threat about this > >> *new policy* and also add it into the FAQ or guidelines. > > > > > > Certainly no threat was made. You quoted me and everyone can see > > that. > > > > There is no new policy, I just want it to be easy for us admins to > > deal with the lump of recently dropped scripts. I don't think I'm > > out of line for asking that people do something that makes this a > > little bit easier for us. Something as simple as submitting new > > maintainer info now can reduce a lot of hassle later. While a > > maintainer may submit an update once in a blue moon, we have to > > deal with submissions every day. I'm sorry you don't understand > > that we have real lives as well. > > > Ouch, sorry for the typo, s/threat/thread/... breath more deeply ;) Oh no, I really didn't consider that. I held off on hitting send this morning because I was (am) nursing a hangover. I couldn't figure out how in the heck I had threatened anyone. My apologies. -- 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 slava18 at gmail.com Fri Oct 29 18:47:30 2010 From: slava18 at gmail.com (V'yacheslav Stetskevych) Date: Fri, 29 Oct 2010 21:47:30 +0300 Subject: [Slackbuilds-users] possible bug in laptop_mode In-Reply-To: References: Message-ID: On Fri, Oct 29, 2010 at 5:06 PM, Grissiom wrote: > Hello all, Hi Grissiom. > In the official page of laptop_mode, the dev suggested add > `/etc/rc.d/init.d/laptop-mode restart` in rc.local ( > http://samwel.tk/laptop_mode/packages/slackware ). But the README in > SBo's laptop_mode said we should add `/etc/rc.d/rc.laptop-mode start` > in rc.local. i don't know which side is right... > > The reason of laptop_mode's dev is "Slackware doesn't completely clear > /var/run on bootup". But after some investment in rc.S, we are > cleaning /var/run (line 328 of that file). So what does "completely" > there? Should we use "start" or "restart" in this case? > As the writer of laptop-mode-tools SlackBuild, I can assure you that the info on the site is just outdated. I use "start" and it works fine. Slackware cleans /var/run properly. Cheers, V'yacheslav. -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Digital and all the music is free... ? ? ? ?http://www.linux.com From dave at unrealize.co.uk Fri Oct 29 23:10:09 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Sat, 30 Oct 2010 00:10:09 +0100 Subject: [Slackbuilds-users] choqok md5 Message-ID: <20101029231009.GA4618@Junius> Just noticed tonight that the source md5 has changed for version 0.9.90. Thought it worth relaying this to the list. I've 0.9.92 in pending at the moment though. If the source md5 changes again I'll see what upstream are doing to it. Cheers Dave -- 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 vmj at linuxbox.fi Sat Oct 30 10:51:57 2010 From: vmj at linuxbox.fi (Mikko Varri) Date: Sat, 30 Oct 2010 13:51:57 +0300 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: Message-ID: <20101030105157.GB28447@linuxbox.fi> On Sat, Oct 30, 2010 at 08:28:35AM -0200, Max Miorim wrote: > > ./libraries/Jinja2/Jinja2.SlackBuild > Perfect timing, Max! I'm just preparing an update of Jinja2.SlackBuild. Thank you. -vmj From baildon.research at googlemail.com Sat Oct 30 10:58:08 2010 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 30 Oct 2010 11:58:08 +0100 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: Message-ID: > 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. I once did something similar with ksh, so I sympathise with your intentions :-) and I'm rather shocked to be a three-strike offender :-( But I don't think the patch will work for grass.SlackBuild, which uses arrays due to bash's brain-dead whitespace handling. It can't be made to work in bash using only ash-compatible code, and most people will have bash as /bin/sh. SlackBuild.org policy is that a full Slackware installation is required, and a full Slackware installation includes bash, so perhaps the easy solution would be to use '#!/bin/bash' in scripts that really need bash functionality? But you're right that, in most cases, bash-specific code is trivially easy to avoid, and therefore I'll take a bit more care to do that in future. I'll leave the question of whether this needs a mass patch at SBo to the SBo admins. If it doesn't, I'll quietly update my SlackBuilds the next time they need revision for other reasons. -D. (cc trimmed, as presumably most people are subscribed to slackbuilds-users) From eha at alienbase.nl Sat Oct 30 11:30:33 2010 From: eha at alienbase.nl (Eric Hameleers) Date: Sat, 30 Oct 2010 13:30:33 +0200 (CEST) Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: Message-ID: On Sat, 30 Oct 2010, David Spencer 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. > > I'll leave the question of whether this needs a mass patch at SBo to > the SBo admins. If it doesn't, I'll quietly update my SlackBuilds the > next time they need revision for other reasons. Slackware assumes and requires that the root user uses bash as the default shell. Not just SlackBuild scripts but the init scripts will not all work the full 100% when using a limited version like ash. We are not going to demand or execute a mass patch here at SlackBuilds.org - we keep assuming that /bin/sh is linked to /bin/bash . 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 miorimmax at gmail.com Sat Oct 30 12:40:58 2010 From: miorimmax at gmail.com (Max Miorim) Date: Sat, 30 Oct 2010 10:40:58 -0200 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: Message-ID: On Sat, Oct 30, 2010 at 9:30 AM, Eric Hameleers wrote: > On Sat, 30 Oct 2010, David Spencer 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. >> >> I'll leave the question of whether this needs a mass patch at SBo to >> the SBo admins. ?If it doesn't, I'll quietly update my SlackBuilds the >> next time they need revision for other reasons. > > Slackware assumes and requires that the root user uses bash as the default > shell. Not just SlackBuild scripts but the init scripts will not all work > the full 100% when using a limited version like ash. Yeah, I have had to modify the init scripts to work around some problems like the absence of arrays in ash. > We are not going to demand or execute a mass patch here at SlackBuilds.org - > we keep assuming that /bin/sh is linked to /bin/bash . Although I don't like the assumption that /bin/sh is linked to bash (I'd rather use #!/bin/bash to ensure that I'm using the right shell), I kind of understand the reasons for doing so. I will modify my sbopkg to run "bash $PKGNAME.SlackBuild.build" instead of sh and just use "bash script.SlackBuild" from now on. :) -- Max From xgizzmo at slackbuilds.org Sat Oct 30 13:00:11 2010 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Sat, 30 Oct 2010 09:00:11 -0400 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: References: Message-ID: <201010300900.11587.xgizzmo@slackbuilds.org> On Saturday 30 October 2010 08:40:58 Max Miorim wrote: > On Sat, Oct 30, 2010 at 9:30 AM, Eric Hameleers wrote: > > On Sat, 30 Oct 2010, David Spencer 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. > >> > >> I'll leave the question of whether this needs a mass patch at SBo to > >> the SBo admins. ?If it doesn't, I'll quietly update my SlackBuilds the > >> next time they need revision for other reasons. > > > > Slackware assumes and requires that the root user uses bash as the default > > shell. Not just SlackBuild scripts but the init scripts will not all work > > the full 100% when using a limited version like ash. > > Yeah, I have had to modify the init scripts to work around some > problems like the absence of arrays in ash. > > > > We are not going to demand or execute a mass patch here at SlackBuilds.org - > > we keep assuming that /bin/sh is linked to /bin/bash . > > Although I don't like the assumption that /bin/sh is linked to bash > (I'd rather use #!/bin/bash to ensure that I'm using the right shell), > I kind of understand the reasons for doing so. > > I will modify my sbopkg to run "bash $PKGNAME.SlackBuild.build" > instead of sh and just use "bash script.SlackBuild" from now on. :) > > -- Max Thanks for your work on this. While we will not demand these changes be made the maintainers of affected builds are free to make these changes if they wish. --dsomero From miorimmax at gmail.com Sat Oct 30 10:28:35 2010 From: miorimmax at gmail.com (Max Miorim) Date: Sat, 30 Oct 2010 08:28:35 -0200 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts Message-ID: Hello folks, 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. After some debugging (ol' good "set -x"), I have noticed some "bashisms" such as the use of [[ ]] instead of [ ] or test and the use of == instead of = in either [ ] or test and so I'm proposing modifications (see attached patch) to remove the bashisms of the following scripts (whose maintainers are CC'ed): ./development/cppcheck/cppcheck.SlackBuild ./libraries/Jinja2/Jinja2.SlackBuild ./libraries/gdal/gdal.SlackBuild ./libraries/python-musicbrainz2/python-musicbrainz2.SlackBuild ./office/go_openoffice/go_openoffice.SlackBuild ./office/adobe-reader-fontpacks/adobe-reader-fontpacks.SlackBuild ./network/skype/skype.SlackBuild ./network/ekiga/ekiga.SlackBuild ./network/ngrep/ngrep.SlackBuild ./desktop/openbox/openbox.SlackBuild ./desktop/synergy-plus/synergy-plus.SlackBuild ./desktop/vwm/vwm.SlackBuild ./misc/ophcrack/ophcrack.SlackBuild ./misc/dwdiff/dwdiff.SlackBuild ./multimedia/xbmc/xbmc.SlackBuild ./audio/herrie/herrie.SlackBuild ./games/jag/jag.SlackBuild ./games/openttd/openttd.SlackBuild ./games/yabause/yabause.SlackBuild ./games/worldofgoo/worldofgoo.SlackBuild ./graphics/yafaray/yafaray.SlackBuild ./graphics/fontmatrix/fontmatrix.SlackBuild ./graphics/djview4/djview4.SlackBuild ./graphics/mtpaint/mtpaint.SlackBuild ./graphics/tesseract/tesseract.SlackBuild ./academic/itex2mml/itex2mml.SlackBuild ./academic/grass/grass.SlackBuild ./academic/GMT/GMT.SlackBuild ./system/vice/vice.SlackBuild ./system/ksh/ksh.SlackBuild ./system/xen/xen.SlackBuild ./system/truecrypt/truecrypt.SlackBuild ./system/gpsd/gpsd.SlackBuild ./system/pdksh/pdksh.SlackBuild ./system/xf86-input-evtouch/xf86-input-evtouch.SlackBuild By the way, I think it's worth nothing that the attached patch is a result of a sed looking for the aforementioned inconsistencies with test and the equals (see bellow) and that most of my tests were limited to building the packages with set -x and looking for errors in the output. Sed used to "fix" the bashisms: for f in `find . -type f -name *.SlackBuild | xargs egrep -l "\[.*==.*\]|\[\[.*\]\]"`; do sed -i -e "s#\[\(.*\)==\(.*\)\]#\[\1=\2\]#g; s#if \[\[\(.*\)\]\]#if \[\1\]#g; s#\[\[\(.*\)\]\]\([[:blank:]]\)\(&&|\|\|\)#\[\1\]\2#g" $f done Regards, Max -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Remove-some-bashisms.patch.gz Type: application/x-gzip Size: 6434 bytes Desc: not available URL: From slakmagik at gmail.com Sat Oct 30 17:50:15 2010 From: slakmagik at gmail.com (slakmagik) Date: Sat, 30 Oct 2010 13:50:15 -0400 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: <201010300900.11587.xgizzmo@slackbuilds.org> References: <201010300900.11587.xgizzmo@slackbuilds.org> Message-ID: <20101030175015.GA29425@devbox> On 2010-10-30 (Sat) 09:00:11 [-0400], xgizzmo at slackbuilds.org wrote: > On Saturday 30 October 2010 08:40:58 Max Miorim wrote: > > On Sat, Oct 30, 2010 at 9:30 AM, Eric Hameleers wrote: > > > On Sat, 30 Oct 2010, David Spencer 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. > > >> > > >> I'll leave the question of whether this needs a mass patch at SBo to > > >> the SBo admins. If it doesn't, I'll quietly update my SlackBuilds the > > >> next time they need revision for other reasons. > > > > > > Slackware assumes and requires that the root user uses bash as the default > > > shell. Not just SlackBuild scripts but the init scripts will not all work > > > the full 100% when using a limited version like ash. [snip] > > > We are not going to demand or execute a mass patch here at SlackBuilds.org - > > > we keep assuming that /bin/sh is linked to /bin/bash . [snip] > Thanks for your work on this. While we will not demand these changes be made > the maintainers of affected builds are free to make these changes if they wish. > > --dsomero Your patch won't work in some cases - I'm guilty of using '[[' in dwdiff and mtpaint but I also leave $VAR unquoted. Merely changing it to '[' will result in ash choking on either an unexpected operator or an expected argument if the variable is unset. But, as others have said, thanks for bringing it to my/our attention. I agree with the policy that sh is bash and that these changes aren't mandatory but also agree that SlackBuilds shouldn't be needlessly bashistic and I'll modify mine soon. From bkirkp at gmail.com Sun Oct 31 14:15:58 2010 From: bkirkp at gmail.com (B Kirkpatrick) Date: Sun, 31 Oct 2010 09:15:58 -0500 Subject: [Slackbuilds-users] Patch proposal to remove bashisms from some scripts In-Reply-To: <20101030175015.GA29425@devbox> References: <201010300900.11587.xgizzmo@slackbuilds.org> <20101030175015.GA29425@devbox> Message-ID: <4CCD7A1E.6080808@gmail.com> On 10/30/2010 12:50 PM, slakmagik wrote: > On 2010-10-30 (Sat) 09:00:11 [-0400], xgizzmo at slackbuilds.org wrote: >> On Saturday 30 October 2010 08:40:58 Max Miorim wrote: >>> On Sat, Oct 30, 2010 at 9:30 AM, Eric Hameleers wrote: >>>> On Sat, 30 Oct 2010, David Spencer 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. >>>>> I'll leave the question of whether this needs a mass patch at SBo to >>>>> the SBo admins. If it doesn't, I'll quietly update my SlackBuilds the >>>>> next time they need revision for other reasons. >>>> Slackware assumes and requires that the root user uses bash as the default >>>> shell. Not just SlackBuild scripts but the init scripts will not all work >>>> the full 100% when using a limited version like ash. > [snip] >>>> We are not going to demand or execute a mass patch here at SlackBuilds.org - >>>> we keep assuming that /bin/sh is linked to /bin/bash . > [snip] >> Thanks for your work on this. While we will not demand these changes be made >> the maintainers of affected builds are free to make these changes if they wish. >> >> --dsomero > Your patch won't work in some cases - I'm guilty of using '[[' in dwdiff > and mtpaint but I also leave $VAR unquoted. Merely changing it to '[' > will result in ash choking on either an unexpected operator or an > expected argument if the variable is unset. But, as others have said, > thanks for bringing it to my/our attention. I agree with the policy that > sh is bash and that these changes aren't mandatory but also agree > that SlackBuilds shouldn't be needlessly bashistic and I'll modify mine > soon. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ I 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 From vmj at linuxbox.fi Sun Oct 31 14:44:28 2010 From: vmj at linuxbox.fi (Mikko Varri) Date: Sun, 31 Oct 2010 16:44:28 +0200 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: <20101031144428.GC28447@linuxbox.fi> On Sun, Oct 31, 2010 at 09:15:58AM -0500, 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? > As admins already said, you don't have to. But, IMHO, if contributing those scripts to a larger community, it would make sense to try to be a good citizen... if you can, that is; some features just don't exist in ash. -vmj