From lukenshiro at ngi.it Sun Jun 2 11:52:25 2013 From: lukenshiro at ngi.it (LukenShiro) Date: Sun, 2 Jun 2013 13:52:25 +0200 Subject: [Slackbuilds-users] claws-mail & libchamplain Message-ID: <20130602135225.4c6eea4c@hamalayi.mnt> Hello guys :) claws-mail's README file says: """ The geolocation plugin requires libchamplain """ but libchamplain is no longer available on SBo. TIA. -- GNU/Linux * Slackware64 current LU #210970 SU #12583 LM #98222/#412913 From ardovm at yahoo.it Sun Jun 2 09:04:58 2013 From: ardovm at yahoo.it (Arrigo Marchiori) Date: Sun, 2 Jun 2013 11:04:58 +0200 Subject: [Slackbuilds-users] Patch for builiding ocaml-3.11.1 on Slackware 14.0 Message-ID: <20130602090458.GB15039@snail.casa> Hello, on my Slackware 14.0 system (packages installed from DVD) ocaml did not build. The error message was the same as this Gentoo bug report: https://bugs.gentoo.org/show_bug.cgi?id=361767 I could make up a patch from this commit: http://caml.inria.fr/cgi-bin/viewvc.cgi?view=revision&revision=10980 You can find it attached. To apply it, I added the following line before the configure in ocaml.SlackBuild: patch -p0 < $CWD/patch.txt Please note I don't know OCaml at all; I just needed it to build unison. I only know that, after applying this patch, the build problem disappeared. If you need any more information feel free to ask, but please send e-mails to me directly, as I am not subscribed to the list. HTH. -- rigo http://rigo.altervista.org -------------- next part -------------- --- asmcomp/i386/emit.mlp 2011/03/10 06:27:24 10979 +++ asmcomp/i386/emit.mlp 2011/03/13 13:33:17 10980 @@ -905,12 +905,12 @@ emit_all true fundecl.fun_body; List.iter emit_call_gc !call_gc_sites; emit_call_bound_errors (); - List.iter emit_float_constant !float_constants; - match Config.system with + begin match Config.system with "linux_elf" | "bsd_elf" | "gnu" -> ` .type {emit_symbol fundecl.fun_name}, at function\n`; ` .size {emit_symbol fundecl.fun_name},.-{emit_symbol fundecl.fun_name}\n` - | _ -> () + | _ -> () end; + List.iter emit_float_constant !float_constants (* Emission of data *) --- asmcomp/amd64/emit.mlp 2011/03/10 06:27:24 10979 +++ asmcomp/amd64/emit.mlp 2011/03/13 13:33:17 10980 @@ -691,17 +691,18 @@ emit_all true fundecl.fun_body; List.iter emit_call_gc !call_gc_sites; emit_call_bound_errors (); + begin match Config.system with + "linux" | "gnu" -> + ` .type {emit_symbol fundecl.fun_name}, at function\n`; + ` .size {emit_symbol fundecl.fun_name},.-{emit_symbol fundecl.fun_name}\n` + | _ -> () + end; if !float_constants <> [] then begin if macosx then ` .literal8\n` else ` .section .rodata.cst8,\"a\", at progbits\n`; List.iter emit_float_constant !float_constants - end; - match Config.system with - "linux" | "gnu" -> - ` .type {emit_symbol fundecl.fun_name}, at function\n`; - ` .size {emit_symbol fundecl.fun_name},.-{emit_symbol fundecl.fun_name}\n` - | _ -> () + end (* Emission of data *) From rworkman at slackbuilds.org Sun Jun 2 22:53:54 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 2 Jun 2013 17:53:54 -0500 Subject: [Slackbuilds-users] claws-mail & libchamplain In-Reply-To: <20130602135225.4c6eea4c@hamalayi.mnt> References: <20130602135225.4c6eea4c@hamalayi.mnt> Message-ID: <20130602175354.3600a973@home.rlworkman.net> On Sun, 2 Jun 2013 13:52:25 +0200 LukenShiro wrote: > Hello guys :) > > claws-mail's README file says: > """ > The geolocation plugin requires libchamplain > """ > > but libchamplain is no longer available on SBo. > > TIA. Fixed up in my git branch ; thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From ferenc.deak at gmail.com Mon Jun 3 13:17:50 2013 From: ferenc.deak at gmail.com (Deak, Ferenc) Date: Mon, 3 Jun 2013 15:17:50 +0200 Subject: [Slackbuilds-users] Patch for builiding ocaml-3.11.1 on Slackware 14.0 In-Reply-To: <20130602090458.GB15039@snail.casa> References: <20130602090458.GB15039@snail.casa> Message-ID: On Sun, Jun 2, 2013 at 11:04 AM, Arrigo Marchiori wrote: > Hello, > > on my Slackware 14.0 system (packages installed from DVD) ocaml did > not build. The error message was the same as this Gentoo bug report: > https://bugs.gentoo.org/show_bug.cgi?id=361767 > > I could make up a patch from this commit: > http://caml.inria.fr/cgi-bin/viewvc.cgi?view=revision&revision=10980 > You can find it attached. > > To apply it, I added the following line before the configure in > ocaml.SlackBuild: > > patch -p0 < $CWD/patch.txt > > Please note I don't know OCaml at all; I just needed it to build > unison. I only know that, after applying this patch, the build problem > disappeared. > > If you need any more information feel free to ask, but please send > e-mails to me directly, as I am not subscribed to the list. > > Hi! You mention that you try to build 3.11.1. The SBo repo contains 3.12.1. I quickly removed and built ocaml. It is built without any error on my machine which is not a clean install. I would like to ask, that your 3.11.1 is a typo, or you really want to build 3.11.1? - if it is really 3.11.1, than you should update your SBo repo, and try to build it again - If it is a typo than could you re-check it in a clean updated slackware and updated SBo repo? If you cannot check I will do it later in this week. fdeak -------------- next part -------------- An HTML attachment was scrubbed... URL: From ardovm at yahoo.it Mon Jun 3 14:24:18 2013 From: ardovm at yahoo.it (Arrigo Marchiori) Date: Mon, 3 Jun 2013 16:24:18 +0200 Subject: [Slackbuilds-users] Patch for builiding ocaml-3.11.1 on Slackware 14.0 In-Reply-To: References: <20130602090458.GB15039@snail.casa> Message-ID: <20130603142418.GA3991@snail.casa> Hello Ferenc, On Mon, Jun 03, 2013 at 03:17:50PM +0200, Deak, Ferenc wrote: > On Sun, Jun 2, 2013 at 11:04 AM, Arrigo Marchiori wrote: > > > Hello, > > > > on my Slackware 14.0 system (packages installed from DVD) ocaml did > > not build. The error message was the same as this Gentoo bug report: > > https://bugs.gentoo.org/show_bug.cgi?id=361767 > > > > I could make up a patch from this commit: > > http://caml.inria.fr/cgi-bin/viewvc.cgi?view=revision&revision=10980 > > You can find it attached. > > > > To apply it, I added the following line before the configure in > > ocaml.SlackBuild: > > > > patch -p0 < $CWD/patch.txt > > > > Please note I don't know OCaml at all; I just needed it to build > > unison. I only know that, after applying this patch, the build problem > > disappeared. > > > > If you need any more information feel free to ask, but please send > > e-mails to me directly, as I am not subscribed to the list. > > > > > Hi! > > You mention that you try to build 3.11.1. The SBo repo contains 3.12.1. I > quickly removed > and built ocaml. It is built without any error on my machine which is not a > clean install. > > I would like to ask, that your 3.11.1 is a typo, or you really want to > build 3.11.1? Ah! It wasn't a typo, but a PBCAK. :-) I found the package using google, and I was directed to the SlackBuild for Slackware 13.1, that is version 3.11.1. _That_ version seems not to compile under Slackware 14.0 without the patch. So... thank you for double checking. I am sorry for the noise and for wasting your time! Regards, -- rigo http://rigo.altervista.org From rneri at libero.it Mon Jun 3 16:10:29 2013 From: rneri at libero.it (rneri at libero.it) Date: Mon, 3 Jun 2013 18:10:29 +0200 (CEST) Subject: [Slackbuilds-users] rodent in the Approved queue? Message-ID: <2078039099.2748931370275829540.JavaMail.defaultUser@defaultHost> Hi, I'd like to report that about a week ago I deleted the rodent SlackBuild from the Pending queue because a new (bugfix) version had been released in the meantime; a few minutes ago I've re-submitted it, but then I've seen that the previous one (the one I thought I deleted) is in the approved queue. It looks like the deletion didn't work, although I did receive the confirmation page as if it had actually worked. Anyway, could you please replace the approved one with this one. Thanks Roberto From rworkman at slackbuilds.org Mon Jun 3 16:43:27 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 3 Jun 2013 11:43:27 -0500 Subject: [Slackbuilds-users] rodent in the Approved queue? In-Reply-To: <2078039099.2748931370275829540.JavaMail.defaultUser@defaultHost> References: <2078039099.2748931370275829540.JavaMail.defaultUser@defaultHost> Message-ID: <20130603114327.7a091b6f@home.rlworkman.net> On Mon, 3 Jun 2013 18:10:29 +0200 (CEST) "rneri at libero.it" wrote: > Hi, > I'd like to report that about a week ago I deleted the rodent > SlackBuild from the Pending queue because a new (bugfix) version had > been released in the meantime; a few minutes ago I've re-submitted > it, but then I've seen that the previous one (the one I thought I > deleted) is in the approved queue. It looks like the deletion didn't > work, although I did receive the confirmation page as if it had > actually worked. Anyway, could you please replace the approved one > with this one. Thanks My fault - it was deleted fine, but I still had a local copy of it, and in my "fix all the things and fix them forever!!!" rage last night (I approved somewhere around 50 builds), it got checked and put in my git repo. :-) I've just updated it to 5.0.5 and added the icon theme too. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From miguel at thedeanda.com Mon Jun 3 16:44:53 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Mon, 3 Jun 2013 09:44:53 -0700 Subject: [Slackbuilds-users] mongodb Message-ID: I submitted a mongodb update about a month ago (near May 8) and I haven't seen it in the queue for about 2 weeks now but the build script still isn't updated. Did the script not get accepted or does it normally take this long? I basically just had to update a few version numbers and checksums and I've been running that version without any issues. I also asked the maintainer of nginx for an update or to allow me to take over it and he quickly updated his script and its also not updated but that one still shows up in the queue. It would be great if there was some kind of peer review system to help the slackbuilds maintainers a bit to reduce their load. I'd volunteer to "beta test" all the programs I normally use. -m -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Mon Jun 3 17:03:23 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 3 Jun 2013 12:03:23 -0500 Subject: [Slackbuilds-users] mongodb In-Reply-To: References: Message-ID: <20130603120323.590cdf52@home.rlworkman.net> On Mon, 3 Jun 2013 09:44:53 -0700 Miguel De Anda wrote: > I submitted a mongodb update about a month ago (near May 8) and I > haven't seen it in the queue for about 2 weeks now but the build > script still isn't updated. Did the script not get accepted or does > it normally take this long? I basically just had to update a few > version numbers and checksums and I've been running that version > without any issues. It's 4745f3a6b3de0a13224368014576344cc5fbd552 in XGizzmo's git branch, which means it will be in the next public update. > I also asked the maintainer of nginx for an update or to allow me to > take over it and he quickly updated his script and its also not > updated but that one still shows up in the queue. Yeah, it's still there; I'll try to get it at some point today. -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 Jun 4 05:36:08 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 4 Jun 2013 00:36:08 -0500 Subject: [Slackbuilds-users] Updates - 20130604.1 Message-ID: <20130604003608.5a6fedad@home.rlworkman.net> Tue Jun 4 05:14:53 UTC 2013 academic/R: Updated for version 3.0.1. academic/copasi: Updated for version 55. academic/mendeleydesktop: Updated for version 1.8.4. academic/scilab: Updated for version 5.4.1. academic/smath-studio: Updated for version 0.96.4868. audio/guitarix: Updated for version 0.27.1. audio/lsmi: Added (map device input to ALSA MIDI sequencer events) audio/xmp: Updated for version 4.0.6. desktop/cwp: Updated for version 1.7.3. desktop/e16: Updated for version 1.0.13. desktop/ede: Added (Equinox Desktop Environment) desktop/enlightenment: Updated for version 0.17.3. desktop/rodent-icon-theme: Added (Rodent vector icon theme) development/Cython: Updated for version 0.19.1. development/anjuta: Updated for version 3.8.1. development/bas: Added (classic basic interpreter) development/eagle: Updated for version 6.4.0. development/eclipse: Updated for version 4.2.2. development/gambas3: Updated for version 3.4.1. development/git-cola: Updated for version 1.8.2. development/nqp: Updated for version 2013.05. development/parrot: Updated for version 5.4.0. development/vile: Updated for version 9.8j. development/xvile: Updated for version 9.8j. games/bsnes: Removed (use games/higan instead) games/desmume: Updated for version 0.9.9. games/fortune_doctor_who: Added (quotes from Doctor Who) games/gzdoom: Updated for version 1.7.01. games/higan: Added (Nintendo multi-system emulator) games/openttd: Updated for version 1.3.1. games/pcsxr: Fixed download link games/wesnoth: Fix segfault using upstream patch games/xonotic: Updated for version 0.6.0. games/yamagi-quake2: Updated for version 5.11. graphics/darktable: Updated for version 1.2. graphics/fyre: Added (A tool for producing computational artwork) graphics/gpaint: Added (GNU Paint: a small-scale GTK2 painting program) graphics/graphviz: Updated for version 2.30.1. graphics/jhead: Updated for version 2.97. graphics/luminance-hdr: Updated for version 2.3.1. graphics/meshlab: Added (process and edit 3D triangular meshes) graphics/teighafileconverter: Updated for version 3.08.2. graphics/teighaviewer: Updated for version 3.08.2. haskell/haskell-platform: Removed (build failure) libraries/c++-gtk-utils: Updated for version 2.0.16. libraries/dietlibc: Updated for version 0.33. libraries/e_dbus: Updated for version 1.7.7. libraries/ecore: Updated for version 1.7.7. libraries/edelib: Added (C++ library for EDE) libraries/edje: Updated for version 1.7.7. libraries/eet: Updated for version 1.7.7. libraries/efreet: Updated for version 1.7.7. libraries/eina: Updated for version 1.7.7. libraries/eio: Updated for version 1.7.7. libraries/embryo: Updated for version 1.7.7. libraries/evas: Updated for version 1.7.7. libraries/flickcurl: Updated for version 1.24. libraries/hdf5: Updated for version 1.8.10_patch1. libraries/io_lib: Updated for version 1.13.0. libraries/libskk: Added (Japanese kana-to-kanji conversion library) libraries/libxmp: Added (The Extended Module Player library) libraries/log4shib: Updated for version 1.0.6. libraries/miniupnpc: Updated for version 1.8. libraries/opencv: Updated for version 2.4.5. libraries/quazip: Added (Qt/C++ wrapper for ZIP/UNZIP package) libraries/reportlab: Updated for version 2.7. misc/foxtrotgps: Updated for version 1.1.1. misc/gramps: Updated for version 3.4.3. misc/ibus-skk: Added (SKK engine for IBus) multimedia/flash-player-plugin: Updated for version 11.2.202.285. multimedia/gtkpod: Patched to work with Anjuta 3.8.x. multimedia/hexter: Updated for version 1.0.0. multimedia/makemkv: Updated for version 1.8.3. multimedia/smplayer: Updated for version 0.8.5. network/claws-mail: Note that libchamplain is not on SBo network/claws-mail: Removed html2ps note network/fail2ban: Updated for version 0.8.9. network/hipchat: Added (private group messaging) network/jabberd2: Added (XMPP server) network/kismet: Updated for version 2013_03_R1b. network/memcached: Updated for version 1.4.15. network/msmtp: Updated for version 1.4.31. network/mumble: Updated for version 1.2.4. network/murmur: Updated for version 1.2.4. network/newsbeuter: Updated for version 2.6. network/p0f: Updated for version 3.06b. network/radvd: Updated for version 1.9.3. network/skype: Updated for version 4.2.0.11. network/smb4k: Updated for version 1.0.7. network/synergy: Updated for version 1.4.12. network/udns: Added (DNS resolver library) network/users-agent: Added (Jabber User Directory) network/uwsgi: Updated for version 1.9.6. network/weechat: Updated for version 0.4.1. office/ProjectLibre: Updated for version 1.5.5. office/adobe-reader: Updated for version 9.5.5. office/elyxer: Updated for version 1.2.5. office/pdftk: Updated for version 2.00. office/texmaker: Updated for version 4.0.2. perl/libwww-perl: Updated for version 6.05. perl/perl-Authen-PAM: Added (Perl interface to PAM library) perl/perl-Class-ReturnValue: Added (a return-value object) perl/perl-Config-IniFiles: Updated for version 2.82. perl/perl-Devel-StackTrace: Updated for version 1.30. perl/perl-Font-AFM: Added (interface to Adobe Font Metrics files) perl/perl-Image-Info: Updated for version 1.35. perl/perl-Locale-Maketext-Lexicon: Added (Use other catalog formats in Maketext) perl/perl-Module-Versions-Report: Added (report versions of in-memory perl modules) perl/perl-NetAddr-IP: Updated for version 4.068. perl/perl-Regext-IPv6: Added (Regular expression for IPv6 addresses) perl/perl-SNMP-Info: Updated for version 3.01. perl/perl-Test-LongString: Added (tests strings for equality) perl/perl-Test-Pod: Updated for version 1.48. perl/perl-Tree-Simple: Added (a simple tree object) perl/perl-html-parser: Updated for version 3.70. perl/perl-net-http: Updated for version 6.06. python/Pygments: Updated for version 1.6. python/cssselect: Updated for version 0.8. python/numexpr: Updated for version 2.1. python/pep8: Updated for version 1.4.5. python/pip: Updated for version 1.3.1. python/pyflakes: Updated for version 0.7.2. python/pyinotify: Updated for version 0.9.4. python/python-pmw: Updated for version 1.3.3a. python/python3: Updated for version 3.3.2. python/virtualenv: Updated for version 1.9.1. system/adobe-source-sans-pro-font: Updated for version 1.050. system/apcupsd: Add --with-dev="" to configure flags system/apcupsd: Fix lockdir definition and usage system/freeswitch: Added (Open source telephony platform) system/fsviewer: Updated download andhomepage links. system/gparted: Updated for version 0.16.0. system/gpsd: Updated for version 3.9. system/heirloom-doctools: Added (classic implementation of the troff tools) system/i8kutils: Added (utilities for Dell Inspiron and Latitude laptops) system/kvm-kmod: Updated for version 3.9. system/makeself: Updated for version 2.2.0. system/mksh: Updated for version R46. system/mongodb: Updated for version 2.4.3. system/nvidia-driver: Updated for version 319.17. system/nvidia-kernel: Updated for version 319.17. system/pcsc-perl: Updated for version 1.4.13. system/redis: Updated for version 2.6.12. system/rodent: Updated for version 5.0.3. system/rodent: Updated for version 5.0.5. system/rsyslog: Updated for version 7.2.6. system/unshield: Added (extractor for Microsoft InstallShield cabinet files) system/vifm: Updated for version 0.7.5. system/virt-viewer: Updated for version 0.5.5. system/xen: Updated for version 4.2.2 (and 3.2.45 kernel) system/zpaq: Added (journaling, incremental, deduplicating archiver) +--------------------------+ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From robby at rlworkman.net Wed Jun 5 08:33:36 2013 From: robby at rlworkman.net (Robby Workman) Date: Wed, 5 Jun 2013 03:33:36 -0500 Subject: [Slackbuilds-users] Updates - 20130605.1 Message-ID: <20130605033336.32d820f0.robby@rlworkman.net> commit 8f8263186ccc60e69296f64c80b7434451e1a760 Author: Robby Workman Date: Wed Jun 5 03:20:11 2013 -0500 Public www update: Wed Jun 5 08:19:26 UTC 2013 It's been seven years since we decided to give this idea a shot, so thanks for all of your support over that time. Here's hoping for at least seven more productive years... Signed-off-by: Robby Workman Wed Jun 5 08:19:26 UTC 2013 audio/fIcy: Added (icecast/shoutcast stream grabber suite) audio/jvmetro: Added (Jack Visual Metronome) audio/soundkonverter: Added (frontend to various audio converters) desktop/cheser-icon-theme: Added (Tango-style icons for Xfce) development/crosstool-ng: Added (Toolchain Generator) games/openttd: Fixed md5sums in .info file graphics/pngquant: Added (PNG conversion tool) libraries/glfw: Added (OpenGL framework) libraries/gnome-python2-gconf: Added (GConf bindings for Python2) libraries/libburn: Updated for version 1.3.0. libraries/libg3d: Added (3-d environment importing library) libraries/libisoburn: Updated for version 1.3.0. libraries/libisofs: Updated for version 1.3.0. misc/dmg2img: Added (disk image file conversion tool) multimedia/smtube: Updated for version 1.7. network/filezilla: Updated for version 3.7.0.2. network/midori: Updated for version 0.5.2. network/nginx: Updated for version 1.4.1. office/gcal: Added (Gnu terminal calendar application) office/text2pdf: Added (Converts text files to PDF) python/lockfile: Added (API for locking files) python/python-daemon: Added (create pythonic daemon processes) python/stem: Added (Python controller library for Tor) system/ack: Added (grep for coders) system/apcupsd: Added "missingok" to the logrotate script system/dtrx: Added (Intelligent archive extraction) system/epson-inkjet-printer-escpr: Added (generic printer driver) system/systrace: Added (interactive policy gen. for system calls) From kingbeowulf at gmail.com Fri Jun 7 01:19:27 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 06 Jun 2013 18:19:27 -0700 Subject: [Slackbuilds-users] Updates - 20130605.1 In-Reply-To: <20130605033336.32d820f0.robby@rlworkman.net> References: <20130605033336.32d820f0.robby@rlworkman.net> Message-ID: <51B1351F.7020604@gmail.com> On 06/05/2013 01:33 AM, Robby Workman wrote: > commit 8f8263186ccc60e69296f64c80b7434451e1a760 Author: Robby > Workman Date: Wed Jun 5 03:20:11 2013 > -0500 > > Public www update: Wed Jun 5 08:19:26 UTC 2013 > > It's been seven years since we decided to give this idea a shot, so > thanks for all of your support over that time. Here's hoping for at > least seven more productive years... > > Signed-off-by: Robby Workman > Congratulations and thanks to all. SBo has made my life just a bit easier these past years. From chess at chessgriffin.com Fri Jun 7 13:12:36 2013 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 7 Jun 2013 09:12:36 -0400 Subject: [Slackbuilds-users] Updates - 20130605.1 In-Reply-To: <51B1351F.7020604@gmail.com> References: <20130605033336.32d820f0.robby@rlworkman.net> <51B1351F.7020604@gmail.com> Message-ID: <20130607131235.GA15977@localhost> * King Beowulf [2013-06-06 18:19:27]: > On 06/05/2013 01:33 AM, Robby Workman wrote: > > commit 8f8263186ccc60e69296f64c80b7434451e1a760 Author: Robby > > Workman Date: Wed Jun 5 03:20:11 2013 > > -0500 > > > > Public www update: Wed Jun 5 08:19:26 UTC 2013 > > > > It's been seven years since we decided to give this idea a shot, so > > thanks for all of your support over that time. Here's hoping for at > > least seven more productive years... > > > > Signed-off-by: Robby Workman > > > > Congratulations and thanks to all. SBo has made my life just a bit > easier these past years. Agreed. Thank you to all the SBo admins, contributors, and maintainers. SBo is a fantastic project. -- Chess Griffin From larryhaja at gmail.com Fri Jun 7 17:02:22 2013 From: larryhaja at gmail.com (Larry Hajali) Date: Fri, 7 Jun 2013 10:02:22 -0700 Subject: [Slackbuilds-users] Updates - 20130605.1 In-Reply-To: <20130607131235.GA15977@localhost> References: <20130605033336.32d820f0.robby@rlworkman.net> <51B1351F.7020604@gmail.com> <20130607131235.GA15977@localhost> Message-ID: Yes, much obliged to the SBo admins and the maintainers. It makes for a very robust system where multiple eyes are looking over the build scripts. -Larry On Fri, Jun 7, 2013 at 6:12 AM, Chess Griffin wrote: > * King Beowulf [2013-06-06 18:19:27]: > > > On 06/05/2013 01:33 AM, Robby Workman wrote: > > > commit 8f8263186ccc60e69296f64c80b7434451e1a760 Author: Robby > > > Workman Date: Wed Jun 5 03:20:11 2013 > > > -0500 > > > > > > Public www update: Wed Jun 5 08:19:26 UTC 2013 > > > > > > It's been seven years since we decided to give this idea a shot, so > > > thanks for all of your support over that time. Here's hoping for at > > > least seven more productive years... > > > > > > Signed-off-by: Robby Workman > > > > > > > Congratulations and thanks to all. SBo has made my life just a bit > > easier these past years. > > Agreed. Thank you to all the SBo admins, contributors, and maintainers. > SBo is a fantastic project. > > -- > Chess Griffin > _______________________________________________ > 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 info at microlinux.fr Fri Jun 7 18:09:40 2013 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 07 Jun 2013 20:09:40 +0200 Subject: [Slackbuilds-users] Updates - 20130605.1 In-Reply-To: <51B1351F.7020604@gmail.com> References: <20130605033336.32d820f0.robby@rlworkman.net> <51B1351F.7020604@gmail.com> Message-ID: <51B221E4.2090408@microlinux.fr> Le 07/06/2013 03:19, King Beowulf a ?crit : > Congratulations and thanks to all. SBo has made my life just a bit > easier these past years. A warm THANK YOU SLACKBUILDS.ORG ADMINS from the sunny South of France. You're Slackware's fourth dimension. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From ozan.turkyilmaz at gmail.com Sat Jun 8 03:18:23 2013 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 8 Jun 2013 08:18:23 +0500 Subject: [Slackbuilds-users] Updates - 20130605.1 In-Reply-To: <20130605033336.32d820f0.robby@rlworkman.net> References: <20130605033336.32d820f0.robby@rlworkman.net> Message-ID: 013/6/5 Robby Workman > commit 8f8263186ccc60e69296f64c80b7434451e1a760 > Author: Robby Workman > Date: Wed Jun 5 03:20:11 2013 -0500 > > Public www update: Wed Jun 5 08:19:26 UTC 2013 > > It's been seven years since we decided to give this idea > a shot, so thanks for all of your support over that time. > Here's hoping for at least seven more productive years... > > Signed-off-by: Robby Workman > > Time flies when you have fun. It's been a fun seven years (I came over to write my first build script years later the project started). Together to next seven years, >From Tengiz, with love. -- Ozan, BSc, BEng -------------- next part -------------- An HTML attachment was scrubbed... URL: From mats.bertil.tegner at gmail.com Sat Jun 8 06:42:11 2013 From: mats.bertil.tegner at gmail.com (Mats Bertil Tegner) Date: Sat, 08 Jun 2013 08:42:11 +0200 Subject: [Slackbuilds-users] krb5 SlackBuild fails with Tcl 8.6.0 Message-ID: <51B2D243.5070106@gmail.com> Hi, krb5 fails to build with Tcl 8.6.0 under -current. Add these lines to krb5.SlackBuild after cd $PRGNAM-$VERSION/src and it builds nicely: #TCL 8.6 build fix sed -e "s at python2.5/Python.h@& python2.7/Python.h at g" \ -e "s at -lpython2.5]@&,\n AC_CHECK_LIB(python2.7,main,[PYTHON_LIB=-lpython2.7])@g" \ -i configure.in && sed -e "s at interp->result at Tcl_GetStringResult(interp)@g" \ -i kadmin/testing/util/tcl_kadm5.c && Regards, Mats Tegner From willysr at gmail.com Sat Jun 8 07:03:00 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sat, 8 Jun 2013 14:03:00 +0700 Subject: [Slackbuilds-users] krb5 SlackBuild fails with Tcl 8.6.0 In-Reply-To: <51B2D243.5070106@gmail.com> References: <51B2D243.5070106@gmail.com> Message-ID: > > > krb5 fails to build with Tcl 8.6.0 under -current. Add these lines to > krb5.SlackBuild after cd $PRGNAM-$VERSION/src > and it builds nicely: > #TCL 8.6 build fix > sed -e "s at python2.5/Python.h@& python2.7/Python.h at g" \ > -e "s at -lpython2.5]@&,\n AC_CHECK_LIB(python2.7,main,[**PYTHON_LIB=-lpython2.7])@g" > \ > -i configure.in && > sed -e "s at interp->result at Tcl_**GetStringResult(interp)@g" \ > -i kadmin/testing/util/tcl_kadm5.**c && > > Current is not officially supported, so i guess the maintainer will submit an update when slackware 14.1 gets relesed -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From audrius at neutrino.lt Sat Jun 8 07:57:05 2013 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Sat, 8 Jun 2013 10:57:05 +0300 Subject: [Slackbuilds-users] Updates - 20130605.1 In-Reply-To: <20130605033336.32d820f0.robby@rlworkman.net> References: <20130605033336.32d820f0.robby@rlworkman.net> Message-ID: <20130608075705.GA13075@kiras> On Wed, 2013-06-05 at 03:33:36 -0500, Robby Workman wrote: > It's been seven years since we decided to give this idea > a shot, so thanks for all of your support over that time. > Here's hoping for at least seven more productive years... I'm not really good at saying these things, but thank you to all the people involved in SlackBuilds.org project (admins, contributors, maintainers, users), I learned from you a lot during all these years. Without you Slackware wouldn't be as fun to use as it is now. -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From mats.bertil.tegner at gmail.com Sat Jun 8 08:07:45 2013 From: mats.bertil.tegner at gmail.com (Mats Bertil Tegner) Date: Sat, 08 Jun 2013 10:07:45 +0200 Subject: [Slackbuilds-users] krb5 SlackBuild fails with Tcl 8.6.0 In-Reply-To: References: <51B2D243.5070106@gmail.com> Message-ID: <51B2E651.8010002@gmail.com> On 06/08/2013 09:03 AM, Willy Sudiarto Raharjo wrote: > krb5 fails to build with Tcl 8.6.0 under -current. Add these lines > to krb5.SlackBuild after cd $PRGNAM-$VERSION/src > and it builds nicely: > #T.L 8.6 build fix > sed -e "s at python2.5/Python.h@& python2.7/Python.h at g" \ > -e "s at -lpython2.5]@&,\n > AC_CHECK_LIB(python2.7,main,[__PYTHON_LIB=-lpython2.7])@g" \ > -i configure.in && > sed -e "s at interp->result at Tcl___GetStringResult(interp)@g" \ > -i kadmin/testing/util/tcl_kadm5.__c && > > Current is not officially supported, so I guess the maintainer will > submit an update when slackware 14.1 gets released. Ok, but if -current users wants to build krb5 in the meantime they can use the above mentioned fix courtesy of BLFS: http://www.linuxfromscratch.org/blfs/view/svn/postlfs/mitkrb.html Mats From ivanp84 at gmail.com Sat Jun 8 12:51:15 2013 From: ivanp84 at gmail.com (Ivan Pavicevic) Date: Sat, 8 Jun 2013 14:51:15 +0200 Subject: [Slackbuilds-users] povray problem S64-current Message-ID: Hi! I just noticed that povray returns error about boostlib. Recently I updated system to fresh (Jun, 04.) Slackware64-current. And here is povrays' message: checking for boostlib >= 1.37... yes checking whether the Boost::Thread library is available... yes checking for exit in -lboost_thread... yes checking whether the boost thread library is usable... no configure: error: in `/tmp/SBo/povray-3.7.0.RC7': configure: error: cannot link with the boost thread library See `config.log' for more details -- If you don't care where you are, then you ain't lost -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at gmail.com Sat Jun 8 13:24:21 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sat, 8 Jun 2013 20:24:21 +0700 Subject: [Slackbuilds-users] povray problem S64-current In-Reply-To: References: Message-ID: > Hi! I just noticed that povray returns error about boostlib. Recently I > updated system to fresh (Jun, 04.) Slackware64-current. And here is > povrays' message: > > checking for boostlib >= 1.37... yes > checking whether the Boost::Thread library is available... yes > checking for exit in -lboost_thread... yes > checking whether the boost thread library is usable... no > configure: error: in `/tmp/SBo/povray-3.7.0.RC7': > configure: error: cannot link with the boost thread library > See `config.log' for more details > > That is normal thing as SBo are designed to work with stable releases, not current -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ivanp84 at gmail.com Sat Jun 8 13:47:43 2013 From: ivanp84 at gmail.com (Ivan Pavicevic) Date: Sat, 8 Jun 2013 15:47:43 +0200 Subject: [Slackbuilds-users] povray problem S64-current In-Reply-To: References: Message-ID: I know, povray was pretty happy on 14.0.. but, has anyone faced similar problem, and is there any suggestion how to get over it... I'll try on LQ, but as this is slackware connected issue, first step was to check with SBo community. On Sat, Jun 8, 2013 at 3:24 PM, Willy Sudiarto Raharjo wrote: > > Hi! I just noticed that povray returns error about boostlib. Recently I >> updated system to fresh (Jun, 04.) Slackware64-current. And here is >> povrays' message: >> >> checking for boostlib >= 1.37... yes >> checking whether the Boost::Thread library is available... yes >> checking for exit in -lboost_thread... yes >> checking whether the boost thread library is usable... no >> configure: error: in `/tmp/SBo/povray-3.7.0.RC7': >> configure: error: cannot link with the boost thread library >> See `config.log' for more details >> >> That is normal thing as SBo are designed to work with stable releases, > not current > > > -- > Willy Sudiarto Raharjo > Personal Blog : http://willysr.blogspot.com > Linux Blog: http://slackblogs.blogspot.com > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -- If you don't care where you are, then you ain't lost -------------- next part -------------- An HTML attachment was scrubbed... URL: From artourter at gmail.com Sat Jun 8 14:32:36 2013 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sat, 8 Jun 2013 15:32:36 +0100 Subject: [Slackbuilds-users] povray problem S64-current In-Reply-To: References: Message-ID: There is nothing normal about a package not compiling on something. The fact that SBo doesn't support -current only means that there is no guaranty that a package will compile, not that packages are sure not to compile. now looking around, the version of boost on -current seems to require an additional linking flag. if you add -lboost_system to your LDFLAGS in the .SlackBuild porvray will compile on -current. This change will also work on slackware-14.0 Hope this Helps ArTourter On 8 June 2013 14:47, Ivan Pavicevic wrote: > I know, povray was pretty happy on 14.0.. but, has anyone faced similar > problem, and is there any suggestion how to get over it... I'll try on LQ, > but as this is slackware connected issue, first step was to check with SBo > community. > > > On Sat, Jun 8, 2013 at 3:24 PM, Willy Sudiarto Raharjo wrote: > >> >> Hi! I just noticed that povray returns error about boostlib. Recently I >>> updated system to fresh (Jun, 04.) Slackware64-current. And here is >>> povrays' message: >>> >>> checking for boostlib >= 1.37... yes >>> checking whether the Boost::Thread library is available... yes >>> checking for exit in -lboost_thread... yes >>> checking whether the boost thread library is usable... no >>> configure: error: in `/tmp/SBo/povray-3.7.0.RC7': >>> configure: error: cannot link with the boost thread library >>> See `config.log' for more details >>> >>> That is normal thing as SBo are designed to work with stable releases, >> not current >> >> >> -- >> Willy Sudiarto Raharjo >> Personal Blog : http://willysr.blogspot.com >> Linux Blog: http://slackblogs.blogspot.com >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> >> > > > -- > If you don't care where you are, then you ain't lost > > _______________________________________________ > 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 ivanp84 at gmail.com Sat Jun 8 15:21:35 2013 From: ivanp84 at gmail.com (Ivan Pavicevic) Date: Sat, 8 Jun 2013 17:21:35 +0200 Subject: [Slackbuilds-users] povray problem S64-current In-Reply-To: References: Message-ID: Thanks Greg! Finally, povray is here. I just quickly modifed SB script as: ... elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-fPIC -lboost_system" to try if it works, but it's a good hint for povray.SlackBuild maintainer to get a look at LDFLAGS. Thanks again, and cheers :) On Sat, Jun 8, 2013 at 4:32 PM, Greg' Ar Tourter wrote: > There is nothing normal about a package not compiling on something. The > fact that SBo doesn't support -current only means that there is no guaranty > that a package will compile, not that packages are sure not to compile. > > now looking around, the version of boost on -current seems to require an > additional linking flag. if you add -lboost_system to your LDFLAGS in the > .SlackBuild porvray will compile on -current. This change will also work on > slackware-14.0 > > > Hope this Helps > > ArTourter > > > On 8 June 2013 14:47, Ivan Pavicevic wrote: > >> I know, povray was pretty happy on 14.0.. but, has anyone faced similar >> problem, and is there any suggestion how to get over it... I'll try on LQ, >> but as this is slackware connected issue, first step was to check with SBo >> community. >> >> >> On Sat, Jun 8, 2013 at 3:24 PM, Willy Sudiarto Raharjo > > wrote: >> >>> >>> Hi! I just noticed that povray returns error about boostlib. Recently I >>>> updated system to fresh (Jun, 04.) Slackware64-current. And here is >>>> povrays' message: >>>> >>>> checking for boostlib >= 1.37... yes >>>> checking whether the Boost::Thread library is available... yes >>>> checking for exit in -lboost_thread... yes >>>> checking whether the boost thread library is usable... no >>>> configure: error: in `/tmp/SBo/povray-3.7.0.RC7': >>>> configure: error: cannot link with the boost thread library >>>> See `config.log' for more details >>>> >>>> That is normal thing as SBo are designed to work with stable releases, >>> not current >>> >>> >>> -- >>> Willy Sudiarto Raharjo >>> Personal Blog : http://willysr.blogspot.com >>> Linux Blog: http://slackblogs.blogspot.com >>> >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - http://slackbuilds.org/faq/ >>> >>> >>> >> >> >> -- >> If you don't care where you are, then you ain't lost >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -- If you don't care where you are, then you ain't lost -------------- next part -------------- An HTML attachment was scrubbed... URL: From mats.bertil.tegner at gmail.com Sat Jun 8 15:52:33 2013 From: mats.bertil.tegner at gmail.com (Mats Bertil Tegner) Date: Sat, 08 Jun 2013 17:52:33 +0200 Subject: [Slackbuilds-users] povray problem S64-current In-Reply-To: References: Message-ID: <51B35341.3030902@gmail.com> On 06/08/2013 05:21 PM, Ivan Pavicevic wrote: > Thanks Greg! Finally, povray is here. I just quickly modifed SB script as: > ... > elif [ "$ARCH" = "x86_64" ]; then > SLKCFLAGS="-fPIC -lboost_system" > > to try if it works, but it's a good hint for povray.SlackBuild > maintainer to get a look at LDFLAGS. > Thanks again, and cheers :) It also works if you add LIBS="-lboost_system" \ to the ./configure section of the SlackBuild scipt. Mats From ivanp84 at gmail.com Sat Jun 8 21:48:27 2013 From: ivanp84 at gmail.com (Ivan Pavicevic) Date: Sat, 8 Jun 2013 23:48:27 +0200 Subject: [Slackbuilds-users] povray problem S64-current In-Reply-To: <51B35341.3030902@gmail.com> References: <51B35341.3030902@gmail.com> Message-ID: Thanks Mats, I'll remember that. Povray is only addition to Jmol for more beautiful protein models, and I rarely use it. But, it is a useful info for me, because I'm planning to write SB scripts for several biochemistry related programs, and evenly to share with SB community. Cheers, Ivan :) On Sat, Jun 8, 2013 at 5:52 PM, Mats Bertil Tegner < mats.bertil.tegner at gmail.com> wrote: > On 06/08/2013 05:21 PM, Ivan Pavicevic wrote: > >> Thanks Greg! Finally, povray is here. I just quickly modifed SB script as: >> ... >> elif [ "$ARCH" = "x86_64" ]; then >> SLKCFLAGS="-fPIC -lboost_system" >> >> to try if it works, but it's a good hint for povray.SlackBuild >> maintainer to get a look at LDFLAGS. >> Thanks again, and cheers :) >> > > It also works if you add LIBS="-lboost_system" \ to the ./configure > section of the SlackBuild scipt. > > Mats > > > ______________________________**_________________ > 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 you don't care where you are, then you ain't lost -------------- next part -------------- An HTML attachment was scrubbed... URL: From niels.horn at gmail.com Sat Jun 8 23:39:50 2013 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 8 Jun 2013 20:39:50 -0300 Subject: [Slackbuilds-users] povray problem S64-current In-Reply-To: References: <51B35341.3030902@gmail.com> Message-ID: On Sat, Jun 8, 2013 at 6:48 PM, Ivan Pavicevic wrote: > Thanks Mats, I'll remember that. Povray is only addition to Jmol for more > beautiful protein models, and I rarely use it. But, it is a useful info for > me, because I'm planning to write SB scripts for several biochemistry > related programs, and evenly to share with SB community. > Cheers, Ivan :) > > On Sat, Jun 8, 2013 at 5:52 PM, Mats Bertil Tegner < > mats.bertil.tegner at gmail.com> wrote: > >> On 06/08/2013 05:21 PM, Ivan Pavicevic wrote: >> >>> Thanks Greg! Finally, povray is here. I just quickly modifed SB script >>> as: >>> ... >>> elif [ "$ARCH" = "x86_64" ]; then >>> SLKCFLAGS="-fPIC -lboost_system" >>> >>> to try if it works, but it's a good hint for povray.SlackBuild >>> maintainer to get a look at LDFLAGS. >>> Thanks again, and cheers :) >>> >> >> It also works if you add LIBS="-lboost_system" \ to the ./configure >> section of the SlackBuild scipt. >> >> Mats >> >> > As the maintainer of the povray script, I have received some direct messages about this. Since I'm very short on time lately, I haven't tested this on -current yet, but I'm glad you all solved this for me :) I personally use povray for Lego models, nothing fancy like biochemistry stuff ;) I'll include the flag in the next update, so that it will build on -current systems. Thanks, -- Niels Horn -------------- next part -------------- An HTML attachment was scrubbed... URL: From ivanp84 at gmail.com Sun Jun 9 08:32:55 2013 From: ivanp84 at gmail.com (Ivan Pavicevic) Date: Sun, 9 Jun 2013 10:32:55 +0200 Subject: [Slackbuilds-users] povray problem S64-current In-Reply-To: References: <51B35341.3030902@gmail.com> Message-ID: Hi Niels! Thanks. :) On Sun, Jun 9, 2013 at 1:39 AM, Niels Horn wrote: > On Sat, Jun 8, 2013 at 6:48 PM, Ivan Pavicevic wrote: > >> Thanks Mats, I'll remember that. Povray is only addition to Jmol for more >> beautiful protein models, and I rarely use it. But, it is a useful info for >> me, because I'm planning to write SB scripts for several biochemistry >> related programs, and evenly to share with SB community. >> Cheers, Ivan :) >> >> On Sat, Jun 8, 2013 at 5:52 PM, Mats Bertil Tegner < >> mats.bertil.tegner at gmail.com> wrote: >> >>> On 06/08/2013 05:21 PM, Ivan Pavicevic wrote: >>> >>>> Thanks Greg! Finally, povray is here. I just quickly modifed SB script >>>> as: >>>> ... >>>> elif [ "$ARCH" = "x86_64" ]; then >>>> SLKCFLAGS="-fPIC -lboost_system" >>>> >>>> to try if it works, but it's a good hint for povray.SlackBuild >>>> maintainer to get a look at LDFLAGS. >>>> Thanks again, and cheers :) >>>> >>> >>> It also works if you add LIBS="-lboost_system" \ to the ./configure >>> section of the SlackBuild scipt. >>> >>> Mats >>> >>> >> > As the maintainer of the povray script, I have received some direct > messages about this. > Since I'm very short on time lately, I haven't tested this on -current > yet, but I'm glad you all solved this for me :) > > I personally use povray for Lego models, nothing fancy like biochemistry > stuff ;) > > I'll include the flag in the next update, so that it will build on > -current systems. > > Thanks, > > -- > Niels Horn > > _______________________________________________ > 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 you don't care where you are, then you ain't lost -------------- next part -------------- An HTML attachment was scrubbed... URL: From xgizzmo at slackbuilds.org Sun Jun 9 17:35:52 2013 From: xgizzmo at slackbuilds.org (David Somero) Date: Sun, 9 Jun 2013 13:35:52 -0400 Subject: [Slackbuilds-users] Updates 20130609.1 Message-ID: <20130609173552.GA2547@slackbuilds.org> SELF2013 update. This update is live from the Southeast Linux fest. Sun Jun 9 17:04:13 UTC 2013 academic/clustalo: Updated for version 1.1.1. academic/grass: Fixed build with recent ffmpeg + other tweaks. academic/mafft: Updated for version 7.037. academic/ncbi-blast-plus: Updated for version 2.2.28. academic/qgis: Updated for version 1.8.0 + new maintainer academic/seaview: Updated for version 4.4.1. audio/qmmp: Updated for version 0.7.1. desktop/spectrwm: Updated for version 2.3.0. development/codeblocks: Updated for version 12.11. development/gob2: Updated for version 2.0.19. development/newlisp: Updated for version 10.5.0. games/scummvm: Updated for version 1.6.0. games/stone_soup: Updated for version 0.12.1. games/yamagi-quake2: Fix VERSION in .info graphics/gallery3: Updated for version 3.0.8. libraries/gdal: Updated for version 1.9.2. libraries/libgda: Updated for version 5.1.2. libraries/libmygpo-qt: Updated for version 1.0.7. multimedia/gpodder: Updated for version 3.5.1. multimedia/spotify: Updated for version 0.9.0.133.gd18ed58.259. multimedia/xbmc: Updated for version 12.2. network/ClusterSSH: Updated for version 4.02_01. network/allmydata-tahoe: Updated for version 1.10.0. network/dwb: Updated for version 2013.03.30. network/phpmyadmin: Updated for version 4.0.2. network/qbittorrent: Updated for version 3.0.9. network/qupzilla: Updated for version 1.4.2. office/calibre: Updated for version 0.9.34. perl/perl-BerkeleyDB: Updated for version 0.52. perl/perl-CPANPLUS-Dist-Slackware: Updated for version 1.011. perl/perl-Exception-Class: Updated for version 1.36. perl/perl-IP-Country: Updated for version 2.28. perl/perl-NetAddr-IP: Updated for version 4.069. python/cssutils: Updated for version 0.9.10. python/lxml: Remove distribute dependency. python/lxml: Updated for version 3.2.1. python/psutil: Updated for version 0.7.1. system/plan9port: Updated for version 20130308. system/tiger: Updated with a few bug fixing patches. system/xboxdrv-linux: Updated for version 0.8.5. +--------------------------+ From openpandora at free.fr Sun Jun 9 18:23:17 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Sun, 9 Jun 2013 20:23:17 +0200 (CEST) Subject: [Slackbuilds-users] gksu-polkit does not work here. In-Reply-To: <502573153.97063967.1370802076165.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <1677449433.97071344.1370802197867.JavaMail.root@zimbra53-e8.priv.proxad.net> Hi ! As libgksu/gksu seems deprecated, i use now gksu-polkit. I'm under Slackware ARM + Xfce + slim. Here's the message: Warning: This program is an suid-root program or is being run by the root user. The full text of the error or warning message cannot be safely formatted in this environment. You may get a more descriptive message by running the program as a non-root user or by removing the suid bit on the executable. From matteo.bernardini at gmail.com Mon Jun 10 07:04:05 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 10 Jun 2013 09:04:05 +0200 Subject: [Slackbuilds-users] gksu-polkit does not work here. In-Reply-To: <1677449433.97071344.1370802197867.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <502573153.97063967.1370802076165.JavaMail.root@zimbra53-e8.priv.proxad.net> <1677449433.97071344.1370802197867.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: could be related to that specific binary (no clue which is) not supporting to be launched as root, you can have a try with ktsuss. BTW, soon I'll drop maintanership of gksu-polkit (I'm using ktsuss myself). Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From openpandora at free.fr Mon Jun 10 15:44:29 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Mon, 10 Jun 2013 17:44:29 +0200 (CEST) Subject: [Slackbuilds-users] gksu-polkit does not work here. In-Reply-To: Message-ID: <34336910.98443703.1370879069906.JavaMail.root@zimbra53-e8.priv.proxad.net> Same with ktsuss. I simply try to launch xterm. Kdesu works, but i'd prefer to use something less heavy. ----- Mail original ----- De: "Matteo Bernardini" ?: "SlackBuilds.org Users List" Envoy?: Lundi 10 Juin 2013 09:04:05 Objet: Re: [Slackbuilds-users] gksu-polkit does not work here. could be related to that specific binary (no clue which is) not supporting to be launched as root, you can have a try with ktsuss. BTW, soon I'll drop maintanership of gksu-polkit (I'm using ktsuss myself). Matteo _______________________________________________ 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 info at microlinux.fr Tue Jun 11 19:32:21 2013 From: info at microlinux.fr (Niki Kovacs) Date: Tue, 11 Jun 2013 21:32:21 +0200 Subject: [Slackbuilds-users] Exaile won't start Message-ID: <51B77B45.6090605@microlinux.fr> Hi, I just built Exaile from SBo (after gst-python and mutagen). When I clicked on the menu icon, nothing happened. So I launched it from the Xfce terminal and got the following result: [kikinovak at alphamule:~] $ exaile INFO : Loading Exaile 0.3.2.1... INFO : Loading settings... ** Message: pygobject_register_sinkfunc is deprecated (GstObject) INFO : Loading plugins... Traceback (most recent call last): File "/usr/lib64/exaile/xl/plugins.py", line 123, in enable_plugin if not plugin: raise Exception("Error loading plugin") Exception: Error loading plugin WARNING : Unable to enable plugin osd INFO : Loading collection... INFO : Loading devices... WARNING : Failed to connect to HAL, autodetection of devices will be disabled. INFO : Loading interface... INFO : Loading main window... INFO : Connecting main window events... INFO : Loading panels... Traceback (most recent call last): File "/usr/lib64/exaile/exaile.py", line 62, in main() File "/usr/lib64/exaile/exaile.py", line 59, in main exaile = main.Exaile() File "/usr/lib64/exaile/xl/main.py", line 102, in __init__ self.__init() File "/usr/lib64/exaile/xl/main.py", line 226, in __init self.gui = xlgui.Main(self) File "/usr/lib64/exaile/xlgui/__init__.py", line 108, in __init__ exaile.collection, _show_collection_empty_message=True) File "/usr/lib64/exaile/xlgui/panel/collection.py", line 187, in __init__ self.load_tree() File "/usr/lib64/exaile/xlgui/panel/collection.py", line 541, in load_tree self.resort_tracks() File "/usr/lib64/exaile/xlgui/panel/collection.py", line 520, in resort_tracks self.collection.get_tracks()) File "/usr/lib64/exaile/xl/trax/util.py", line 90, in sort_tracks return sorted(iter, key=keyfunc, reverse=reverse) File "/usr/lib64/exaile/xl/trax/util.py", line 89, in artist_compilations=artist_compilations) for field in fields] File "/usr/lib64/exaile/xl/trax/track.py", line 484, in get_tag_sort retval = self.format_sort(retval) File "/usr/lib64/exaile/xl/trax/track.py", line 695, in format_sort return [cls.format_sort(v) for v in values] File "/usr/lib64/exaile/xl/trax/track.py", line 697, in format_sort values = cls.strip_leading(values) File "/usr/lib64/exaile/xl/trax/track.py", line 746, in strip_leading stripped = value.lstrip(" `~!@#$%^&*()_+-={}|[]\\\";'<>?,./") AttributeError: 'ASFUnicodeAttribute' object has no attribute 'lstrip' Anyone knows what's happening here? Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From unix_lists at f-m.fm Thu Jun 13 20:39:00 2013 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Thu, 13 Jun 2013 15:39:00 -0500 Subject: [Slackbuilds-users] Fwd: Fwd: Build Failure: Slackbuild easymp3gain References: <1371155820.28788.140661243647109.79C35BC4@webmail.messagingengine.com> Message-ID: <1371155940.29085.140661243647377.7783355D@webmail.messagingengine.com> Sent this to maintainer a week ago but haven't heard back yet. ----- Original message ----- From: unix_lists at f-m.fm To: manbornofwoman at gmail.com Subject: Build Failure: Slackbuild easymp3gain Date: Thu, 06 Jun 2013 23:17:52 -0500 Hello, I am trying to build easymp3gain with your slackbuild but I encounter the following error: patching file unitmain.pas patching file easymp3gain.lpi Hunk #1 succeeded at 490 (offset -4 lines). chmod +x ./clean.sh ./clean.sh chmod +x ./make.sh ./make.sh Target architecture: i386 Target operating system: linux Compiler version: 2.6.0 Building easyMP3Gain ... primary config path: /root/.lazarus Error: invalid Lazarus directory "": directory lcl not found Failed building easymp3gain.lpr make: *** [all] Error 2 All dependencies are installed and I am running Slackware 14.0. -- Regards, 2>&1 -- Regards, 2>&1 From kava at online.be Thu Jun 13 21:23:15 2013 From: kava at online.be (Karel Venken) Date: Thu, 13 Jun 2013 23:23:15 +0200 Subject: [Slackbuilds-users] Fwd: Fwd: Build Failure: Slackbuild easymp3gain In-Reply-To: <1371155940.29085.140661243647377.7783355D@webmail.messagingengine.com> References: <1371155820.28788.140661243647109.79C35BC4@webmail.messagingengine.com> <1371155940.29085.140661243647377.7783355D@webmail.messagingengine.com> Message-ID: <51BA3843.1070405@online.be> unix_lists at f-m.fm wrote: > > Sent this to maintainer a week ago but haven't heard back yet. > > > > ----- Original message ----- > From: unix_lists at f-m.fm > To: manbornofwoman at gmail.com > Subject: Build Failure: Slackbuild easymp3gain > Date: Thu, 06 Jun 2013 23:17:52 -0500 > > Hello, > I am trying to build easymp3gain with your slackbuild but I encounter > the following error: > > patching file unitmain.pas > patching file easymp3gain.lpi > Hunk #1 succeeded at 490 (offset -4 lines). > chmod +x ./clean.sh > ./clean.sh > chmod +x ./make.sh > ./make.sh > Target architecture: i386 > Target operating system: linux > Compiler version: 2.6.0 > Building easyMP3Gain ... > primary config path: /root/.lazarus > Error: invalid Lazarus directory "": directory lcl not found > Failed building easymp3gain.lpr > make: *** [all] Error 2 > > All dependencies are installed and I am running Slackware 14.0. It 's missing .lazarus in its home (/root/.lazarus), After building and installing lazarus (it's a dependency for easymp3gain) you must effectively start this command (/usr/bin/lazarus) in a graphical environment after which it will create the missing directory. Then you can continue. From unix_lists at f-m.fm Fri Jun 14 01:30:34 2013 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Thu, 13 Jun 2013 20:30:34 -0500 Subject: [Slackbuilds-users] Fwd: Re: Fwd: Fwd: Build Failure: Slackbuild easymp3gain References: <1371173392.21770.140661243727433.43346C3D@webmail.messagingengine.com> Message-ID: <1371173434.21805.140661243728185.39EF3211@webmail.messagingengine.com> On Thu, Jun 13, 2013, at 04:23 PM, Karel Venken wrote: > unix_lists at f-m.fm wrote: > > > > Sent this to maintainer a week ago but haven't heard back yet. > > > > > > > > ----- Original message ----- > > From: unix_lists at f-m.fm > > To: manbornofwoman at gmail.com > > Subject: Build Failure: Slackbuild easymp3gain > > Date: Thu, 06 Jun 2013 23:17:52 -0500 > > > > Hello, > > I am trying to build easymp3gain with your slackbuild but I encounter > > the following error: > > > > patching file unitmain.pas > > patching file easymp3gain.lpi > > Hunk #1 succeeded at 490 (offset -4 lines). > > chmod +x ./clean.sh > > ./clean.sh > > chmod +x ./make.sh > > ./make.sh > > Target architecture: i386 > > Target operating system: linux > > Compiler version: 2.6.0 > > Building easyMP3Gain ... > > primary config path: /root/.lazarus > > Error: invalid Lazarus directory "": directory lcl not found > > Failed building easymp3gain.lpr > > make: *** [all] Error 2 > > > > All dependencies are installed and I am running Slackware 14.0. > It 's missing .lazarus in its home (/root/.lazarus), > After building and installing lazarus (it's a dependency for > easymp3gain) you must effectively start this command (/usr/bin/lazarus) > in a graphical environment after which it will create the missing > directory. Then you can continue. > > Now I have a /root/.lazarus. Ran the build again: Hunk #1 succeeded at 490 (offset -4 lines). chmod +x ./clean.sh ./clean.sh chmod +x ./make.sh ./make.sh Target architecture: i386 Target operating system: linux Compiler version: 2.6.0 Building easyMP3Gain ... primary config path: /root/.lazarus Error: invalid Lazarus directory "": directory lcl not found Failed building easymp3gain.lpr make: *** [all] Error 2 So, I manually create lcl inside of .lazarus: root at localhost:~/.lazarus# mkdir lcl root at localhost:~/.lazarus# ls -al total 12 drwxr-xr-x 3 root root 4096 Jun 13 20:27 ./ drwx--x--- 15 root root 4096 Jun 13 20:21 ../ drwxr-xr-x 2 root root 4096 Jun 13 20:27 lcl/ I next ran the build script once more: Hunk #1 succeeded at 490 (offset -4 lines). chmod +x ./clean.sh ./clean.sh chmod +x ./make.sh ./make.sh Target architecture: i386 Target operating system: linux Compiler version: 2.6.0 Building easyMP3Gain ... primary config path: /root/.lazarus Error: invalid Lazarus directory "": directory packager/globallinks not found Failed building easymp3gain.lpr make: *** [all] Error 2 -- Regards, 2>&1 From kven at sandbubble.org Fri Jun 14 15:44:36 2013 From: kven at sandbubble.org (Karel Venken) Date: Fri, 14 Jun 2013 17:44:36 +0200 Subject: [Slackbuilds-users] Fwd: Re: Fwd: Fwd: Build Failure: Slackbuild easymp3gain In-Reply-To: <1371173434.21805.140661243728185.39EF3211@webmail.messagingengine.com> References: <1371173392.21770.140661243727433.43346C3D@webmail.messagingengine.com> <1371173434.21805.140661243728185.39EF3211@webmail.messagingengine.com> Message-ID: <51BB3A64.30402@sandbubble.org> unix_lists at f-m.fm wrote: > On Thu, Jun 13, 2013, at 04:23 PM, Karel Venken wrote: >> unix_lists at f-m.fm wrote: >>> Sent this to maintainer a week ago but haven't heard back yet. >>> >>> >>> >>> ----- Original message ----- >>> From: unix_lists at f-m.fm >>> To: manbornofwoman at gmail.com >>> Subject: Build Failure: Slackbuild easymp3gain >>> Date: Thu, 06 Jun 2013 23:17:52 -0500 >>> >>> Hello, >>> I am trying to build easymp3gain with your slackbuild but I encounter >>> the following error: >>> >>> patching file unitmain.pas >>> patching file easymp3gain.lpi >>> Hunk #1 succeeded at 490 (offset -4 lines). >>> chmod +x ./clean.sh >>> ./clean.sh >>> chmod +x ./make.sh >>> ./make.sh >>> Target architecture: i386 >>> Target operating system: linux >>> Compiler version: 2.6.0 >>> Building easyMP3Gain ... >>> primary config path: /root/.lazarus >>> Error: invalid Lazarus directory "": directory lcl not found >>> Failed building easymp3gain.lpr >>> make: *** [all] Error 2 >>> >>> All dependencies are installed and I am running Slackware 14.0. >> It 's missing .lazarus in its home (/root/.lazarus), >> After building and installing lazarus (it's a dependency for >> easymp3gain) you must effectively start this command (/usr/bin/lazarus) >> in a graphical environment after which it will create the missing >> directory. Then you can continue. >> >> > Now I have a /root/.lazarus. Ran the build again: > > Hunk #1 succeeded at 490 (offset -4 lines). > chmod +x ./clean.sh > ./clean.sh > chmod +x ./make.sh > ./make.sh > Target architecture: i386 > Target operating system: linux > Compiler version: 2.6.0 > Building easyMP3Gain ... > primary config path: /root/.lazarus > Error: invalid Lazarus directory "": directory lcl not found > Failed building easymp3gain.lpr > make: *** [all] Error 2 > > So, I manually create lcl inside of .lazarus: > > root at localhost:~/.lazarus# mkdir lcl > root at localhost:~/.lazarus# ls -al > total 12 > drwxr-xr-x 3 root root 4096 Jun 13 20:27 ./ > drwx--x--- 15 root root 4096 Jun 13 20:21 ../ > drwxr-xr-x 2 root root 4096 Jun 13 20:27 lcl/ > > I next ran the build script once more: > > Hunk #1 succeeded at 490 (offset -4 lines). > chmod +x ./clean.sh > ./clean.sh > chmod +x ./make.sh > ./make.sh > Target architecture: i386 > Target operating system: linux > Compiler version: 2.6.0 > Building easyMP3Gain ... > primary config path: /root/.lazarus > Error: invalid Lazarus directory "": directory packager/globallinks not > found > Failed building easymp3gain.lpr > make: *** [all] Error 2 Indeed, apparently just starting lazarus is not enough. The problem is (at least) the includelinks.xml in the ~/.lazarus which does not have the necessary includes defined. This seems however to be solved when you run the demo form from within the lazarus ide. Mine is (after stopping lazarus) 1689 in stead of 98 bytes in size. Note with a correct includelinks.xml, you do not have to copy the lcl, leave it in the /usr/share/lazarus. Hope this helps. From yalhcru at gmail.com Sat Jun 15 16:03:07 2013 From: yalhcru at gmail.com (B Watson) Date: Sat, 15 Jun 2013 12:03:07 -0400 Subject: [Slackbuilds-users] bristol Message-ID: There's a bristol build in the pending queue, not put there by me. AFAIK, I'm the maintainer... did I miss a memo or something? From niels.horn at gmail.com Sat Jun 15 16:12:53 2013 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 15 Jun 2013 13:12:53 -0300 Subject: [Slackbuilds-users] bristol In-Reply-To: References: Message-ID: No, you did not miss a memo, we simply didn't check that one yet :) It's an update from 0.60.10 to 0.60.11. I'll reject it, sending a note to the submitter. Thanks, -- Niels Horn On Sat, Jun 15, 2013 at 1:03 PM, B Watson wrote: > There's a bristol build in the pending queue, not put there by me. AFAIK, > I'm the maintainer... did I miss a memo or something? > _______________________________________________ > 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 yalhcru at gmail.com Sat Jun 15 16:34:35 2013 From: yalhcru at gmail.com (B Watson) Date: Sat, 15 Jun 2013 12:34:35 -0400 Subject: [Slackbuilds-users] bristol In-Reply-To: References: Message-ID: On 6/15/13, Niels Horn wrote: > > I'll reject it, sending a note to the submitter. Thanks. I just submitted my update, too. From niels.horn at slackbuilds.org Sun Jun 16 02:33:08 2013 From: niels.horn at slackbuilds.org (Niels Horn) Date: Sat, 15 Jun 2013 23:33:08 -0300 Subject: [Slackbuilds-users] Updates - 20130616.1 Message-ID: <51BD23E4.4040208@slackbuilds.org> Sun Jun 16 02:08:06 UTC 2013 accessibility/espeak: Updated for version 1.47.11. accessibility/wgetpaste: Updated for version 2.22. audio/invada_studio_plugins_lv2: Updated homepage info. audio/millennium-plugins: Updated download location. games/defendguin: Updated for version 0.0.12. games/fizmo: Updated for version 0.7.7. games/fortune-dune: Updated homepage info. games/maelstrom: Updated homepage info. games/mame: Updated for version 0.149. games/playonlinux: Updated for version 4.2.1. games/qmc2: Updated for version 0.39. games/typhoon_2001: Updated homepage, fix ARCH setting. games/ucr: Updated download link. misc/dos2unix: Updated for version 6.0.3. multimedia/flash-player-plugin: Updated for version 11.2.202.291. network/radvd: Create piddir and chown before start() network/radvd: Do not create /var/run/radvd during packaging office/texlive: Fixup duplicate manpages in wrong places perl/perl-Data-Dump: Removed (dupe of perl/perl-data-dump) perl/perl-Test-Trap: Fixed dep info system/isomd5sum: Updated for version 1.0.10. -- Niels Horn From miguel at thedeanda.com Tue Jun 18 10:17:43 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Tue, 18 Jun 2013 03:17:43 -0700 Subject: [Slackbuilds-users] on creating users Message-ID: what's the best practice for server/daemon apps that we want to run as an unprivileged user/group? for example, apache often runs as apache.apache and mysql as mysql.mysql. i found one build script that has a grep for /etc/passwd and /etc/group and has some hard-coded uid/gid's in the suggested user/groups. my concern with this method is that if you archive the tgz file (to install on a remote machine for example) you have to remember that you ran some commands against the buidl system. do we want to add a similar check in the doinst.sh script? maybe a warning? thanks, miguel -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailing at markhu.de Tue Jun 18 10:22:15 2013 From: mailing at markhu.de (Markus Hutmacher) Date: Tue, 18 Jun 2013 12:22:15 +0200 Subject: [Slackbuilds-users] LXDE -- lxlauncher depends on menu-cache Message-ID: <51C034D7.1070006@markhu.de> Hi Matteo, I've built LXDE on current and found "menu-cache" to be a depency for lxlauncher. This is not mentioned in the infofile for lxlauncher. I don't think that this is a problem of Slackware-current only(but can't test this for Slackware-14.0). Could you please check this. Regards Markus -- Markus Hutmacher mailing at markhu.de From matteo.bernardini at gmail.com Tue Jun 18 11:01:28 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 18 Jun 2013 13:01:28 +0200 Subject: [Slackbuilds-users] LXDE -- lxlauncher depends on menu-cache In-Reply-To: <51C034D7.1070006@markhu.de> References: <51C034D7.1070006@markhu.de> Message-ID: Thanks Markus: you're right. I'll submit soon a fix for the .info file. Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristofru at gmail.com Tue Jun 18 11:39:06 2013 From: kristofru at gmail.com (Chris Abela) Date: Tue, 18 Jun 2013 13:39:06 +0200 Subject: [Slackbuilds-users] Error in libnova.info Message-ID: <51C046DA.5090406@gmail.com> The HOMEPAGE entry of libnova has a double http:// prefix: $ grep HOMEPAGE /var/lib/sbopkg/SBo/14.0/libraries/libnova/libnova.info HOMEPAGE="http://http://libnova.sourceforge.net/" From rworkman at slackbuilds.org Tue Jun 18 15:12:47 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 18 Jun 2013 10:12:47 -0500 Subject: [Slackbuilds-users] Error in libnova.info In-Reply-To: <51C046DA.5090406@gmail.com> References: <51C046DA.5090406@gmail.com> Message-ID: <20130618101247.5571f619@home.rlworkman.net> On Tue, 18 Jun 2013 13:39:06 +0200 Chris Abela wrote: > The HOMEPAGE entry of libnova has a double http:// prefix: > > $ grep > HOMEPAGE /var/lib/sbopkg/SBo/14.0/libraries/libnova/libnova.info > HOMEPAGE="http://http://libnova.sourceforge.net/" Fixed in my git branch ; thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Tue Jun 18 15:15:16 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 18 Jun 2013 10:15:16 -0500 Subject: [Slackbuilds-users] LXDE -- lxlauncher depends on menu-cache In-Reply-To: References: <51C034D7.1070006@markhu.de> Message-ID: <20130618101516.6752733d@home.rlworkman.net> On Tue, 18 Jun 2013 13:01:28 +0200 Matteo Bernardini wrote: > Thanks Markus: you're right. > I'll submit soon a fix for the .info file. No need to submit - you can just fix it up in a git branch for something trivial like this. No need this time though - I got it in mine since I was just sitting here doing nothing :-) -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 Jun 18 15:21:25 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 18 Jun 2013 10:21:25 -0500 Subject: [Slackbuilds-users] on creating users In-Reply-To: References: Message-ID: <20130618102125.57dece27@home.rlworkman.net> On Tue, 18 Jun 2013 03:17:43 -0700 Miguel De Anda wrote: > what's the best practice for server/daemon apps that we want to run > as an unprivileged user/group? for example, apache often runs as > apache.apache and mysql as mysql.mysql. > > i found one build script that has a grep for /etc/passwd > and /etc/group and has some hard-coded uid/gid's in the suggested > user/groups. my concern with this method is that if you archive the > tgz file (to install on a remote machine for example) you have to > remember that you ran some commands against the buidl system. do we > want to add a similar check in the doinst.sh script? maybe a warning? I've been bitten by this on some of my own systems, but I'm not convinced that there's a *good* solution to it. A note in doinst.sh is likely (almost sure) to be missed by many admins (e.g. me) who do "batch installs" of add-ons to newly deployed systems, so the extra work of adding notes there isn't really something I want to commit to doing. I also don't really like the idea of checking for existence of any required user/group and automatically creating it/them if it/they do not already exist, and again I'll draw on my own experience for that: I like to keep my UIDs and GIDs in sync across all of my systems, so I'd rather have something fail horribly due to a missing user/group than have a stealthily created (and wrong/inconsistent) user and uid present. I use NFS locally so UID/GID consistency is a big deal for me. All that said, I'm not against doing all of this in a better way, but I'll have to be convinced that it's actually better :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From matteo.bernardini at gmail.com Tue Jun 18 15:23:52 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 18 Jun 2013 17:23:52 +0200 Subject: [Slackbuilds-users] LXDE -- lxlauncher depends on menu-cache In-Reply-To: <20130618101516.6752733d@home.rlworkman.net> References: <51C034D7.1070006@markhu.de> <20130618101516.6752733d@home.rlworkman.net> Message-ID: tnx Robby :) Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Tue Jun 18 16:35:06 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 18 Jun 2013 09:35:06 -0700 Subject: [Slackbuilds-users] on creating users In-Reply-To: <20130618102125.57dece27@home.rlworkman.net> References: <20130618102125.57dece27@home.rlworkman.net> Message-ID: I'll vote for the manual method already used in some SBo scripts: 1. Note default settings In README, instructing user to set up user/group before running script 2. Option such as GRP=blah ./script as needed to set up rc etc I think this is the most generic, easiest to avoid stomping on settings. Ed On 6/18/13, Robby Workman wrote: > On Tue, 18 Jun 2013 03:17:43 -0700 > Miguel De Anda wrote: > >> what's the best practice for server/daemon apps that we want to run >> as an unprivileged user/group? for example, apache often runs as >> apache.apache and mysql as mysql.mysql. >> >> i found one build script that has a grep for /etc/passwd >> and /etc/group and has some hard-coded uid/gid's in the suggested >> user/groups. my concern with this method is that if you archive the >> tgz file (to install on a remote machine for example) you have to >> remember that you ran some commands against the buidl system. do we >> want to add a similar check in the doinst.sh script? maybe a warning? > > > I've been bitten by this on some of my own systems, but I'm not > convinced that there's a *good* solution to it. > > A note in doinst.sh is likely (almost sure) to be missed by many > admins (e.g. me) who do "batch installs" of add-ons to newly > deployed systems, so the extra work of adding notes there isn't > really something I want to commit to doing. > > I also don't really like the idea of checking for existence of > any required user/group and automatically creating it/them if > it/they do not already exist, and again I'll draw on my own > experience for that: I like to keep my UIDs and GIDs in sync > across all of my systems, so I'd rather have something fail > horribly due to a missing user/group than have a stealthily > created (and wrong/inconsistent) user and uid present. I use > NFS locally so UID/GID consistency is a big deal for me. > > All that said, I'm not against doing all of this in a better > way, but I'll have to be convinced that it's actually better :-) > > -RW > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From niels.horn at gmail.com Tue Jun 18 16:45:55 2013 From: niels.horn at gmail.com (Niels Horn) Date: Tue, 18 Jun 2013 13:45:55 -0300 Subject: [Slackbuilds-users] on creating users In-Reply-To: References: <20130618102125.57dece27@home.rlworkman.net> Message-ID: The manual method is fine if you build-once / install once. But if I understood correctly, Miguel's question is about build-once / install-many, storing the created package centrally and then installing it on several boxes. In this case, one might forget to create the user / group on the box where you're installing it. I have this same issue and never found a nice & clean solution. I'm also against automatic user creation and just throwing out a warning after installation (in doinst.sh) might not be very effective. As an administrator of several servers and desktops, I use a local solution: - a shell script wrapper that calls installpkg - a centralized file with pre- & post- commands to run (pre- like checking for a user I need, post- like copying some standard configuration files I use for a specific package) But this is for local administration and I see no way to implement this in the SlackBuilds. But, as Robby, I'm open to suggestions to make my life easier :) -- Niels Horn On Tue, Jun 18, 2013 at 1:35 PM, King Beowulf wrote: > I'll vote for the manual method already used in some SBo scripts: > 1. Note default settings In README, instructing user to set up > user/group before running script > 2. Option such as GRP=blah ./script as needed to set up rc etc > > I think this is the most generic, easiest to avoid stomping on settings. > > Ed > > > > On 6/18/13, Robby Workman wrote: > > On Tue, 18 Jun 2013 03:17:43 -0700 > > Miguel De Anda wrote: > > > >> what's the best practice for server/daemon apps that we want to run > >> as an unprivileged user/group? for example, apache often runs as > >> apache.apache and mysql as mysql.mysql. > >> > >> i found one build script that has a grep for /etc/passwd > >> and /etc/group and has some hard-coded uid/gid's in the suggested > >> user/groups. my concern with this method is that if you archive the > >> tgz file (to install on a remote machine for example) you have to > >> remember that you ran some commands against the buidl system. do we > >> want to add a similar check in the doinst.sh script? maybe a warning? > > > > > > I've been bitten by this on some of my own systems, but I'm not > > convinced that there's a *good* solution to it. > > > > A note in doinst.sh is likely (almost sure) to be missed by many > > admins (e.g. me) who do "batch installs" of add-ons to newly > > deployed systems, so the extra work of adding notes there isn't > > really something I want to commit to doing. > > > > I also don't really like the idea of checking for existence of > > any required user/group and automatically creating it/them if > > it/they do not already exist, and again I'll draw on my own > > experience for that: I like to keep my UIDs and GIDs in sync > > across all of my systems, so I'd rather have something fail > > horribly due to a missing user/group than have a stealthily > > created (and wrong/inconsistent) user and uid present. I use > > NFS locally so UID/GID consistency is a big deal for me. > > > > All that said, I'm not against doing all of this in a better > > way, but I'll have to be convinced that it's actually better :-) > > > > -RW > > > > -- > Sent from my mobile device > > You! What PLANET is this! > -- McCoy, "The City on the Edge of Forever", stardate 3134.0 > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Tue Jun 18 17:58:03 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Tue, 18 Jun 2013 10:58:03 -0700 Subject: [Slackbuilds-users] on creating users In-Reply-To: References: <20130618102125.57dece27@home.rlworkman.net> Message-ID: thanks. i guess the safest answer is to not automatically create the user. i'm thinking of adding a note in the slack-desc and possibly in the rc script as well. something along the lines of echo "$PRGNAME failed to start because it requires a group/user $GRPNAME/$USRNAME" exit 1 miguel On Tue, Jun 18, 2013 at 9:45 AM, Niels Horn wrote: > The manual method is fine if you build-once / install once. > But if I understood correctly, Miguel's question is about build-once / > install-many, storing the created package centrally and then installing it > on several boxes. > > In this case, one might forget to create the user / group on the box where > you're installing it. > > I have this same issue and never found a nice & clean solution. > I'm also against automatic user creation and just throwing out a warning > after installation (in doinst.sh) might not be very effective. > > As an administrator of several servers and desktops, I use a local > solution: > - a shell script wrapper that calls installpkg > - a centralized file with pre- & post- commands to run (pre- like checking > for a user I need, post- like copying some standard configuration files I > use for a specific package) > But this is for local administration and I see no way to implement this in > the SlackBuilds. > > But, as Robby, I'm open to suggestions to make my life easier :) > > > -- > Niels Horn > > > On Tue, Jun 18, 2013 at 1:35 PM, King Beowulf wrote: > >> I'll vote for the manual method already used in some SBo scripts: >> 1. Note default settings In README, instructing user to set up >> user/group before running script >> 2. Option such as GRP=blah ./script as needed to set up rc etc >> >> I think this is the most generic, easiest to avoid stomping on settings. >> >> Ed >> >> >> >> On 6/18/13, Robby Workman wrote: >> > On Tue, 18 Jun 2013 03:17:43 -0700 >> > Miguel De Anda wrote: >> > >> >> what's the best practice for server/daemon apps that we want to run >> >> as an unprivileged user/group? for example, apache often runs as >> >> apache.apache and mysql as mysql.mysql. >> >> >> >> i found one build script that has a grep for /etc/passwd >> >> and /etc/group and has some hard-coded uid/gid's in the suggested >> >> user/groups. my concern with this method is that if you archive the >> >> tgz file (to install on a remote machine for example) you have to >> >> remember that you ran some commands against the buidl system. do we >> >> want to add a similar check in the doinst.sh script? maybe a warning? >> > >> > >> > I've been bitten by this on some of my own systems, but I'm not >> > convinced that there's a *good* solution to it. >> > >> > A note in doinst.sh is likely (almost sure) to be missed by many >> > admins (e.g. me) who do "batch installs" of add-ons to newly >> > deployed systems, so the extra work of adding notes there isn't >> > really something I want to commit to doing. >> > >> > I also don't really like the idea of checking for existence of >> > any required user/group and automatically creating it/them if >> > it/they do not already exist, and again I'll draw on my own >> > experience for that: I like to keep my UIDs and GIDs in sync >> > across all of my systems, so I'd rather have something fail >> > horribly due to a missing user/group than have a stealthily >> > created (and wrong/inconsistent) user and uid present. I use >> > NFS locally so UID/GID consistency is a big deal for me. >> > >> > All that said, I'm not against doing all of this in a better >> > way, but I'll have to be convinced that it's actually better :-) >> > >> > -RW >> > >> >> -- >> Sent from my mobile device >> >> You! What PLANET is this! >> -- McCoy, "The City on the Edge of Forever", stardate 3134.0 >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> > > _______________________________________________ > 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 miguel at thedeanda.com Tue Jun 18 18:13:46 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Tue, 18 Jun 2013 11:13:46 -0700 Subject: [Slackbuilds-users] on creating users In-Reply-To: References: <20130618102125.57dece27@home.rlworkman.net> Message-ID: I just realized something... I'm looking at the jboss and tomcat scripts as they need users as well... the build script chown's some files under that user/group. I think this would cause the package to fail if the gid/uid on the target system doesn't match the build system right? Should the rc script chown files as needed each time it starts? On Tue, Jun 18, 2013 at 10:58 AM, Miguel De Anda wrote: > thanks. i guess the safest answer is to not automatically create the user. > i'm thinking of adding a note in the slack-desc and possibly in the rc > script as well. something along the lines of > > echo "$PRGNAME failed to start because it requires a group/user > $GRPNAME/$USRNAME" > exit 1 > > miguel > > > On Tue, Jun 18, 2013 at 9:45 AM, Niels Horn wrote: > >> The manual method is fine if you build-once / install once. >> But if I understood correctly, Miguel's question is about build-once / >> install-many, storing the created package centrally and then installing it >> on several boxes. >> >> In this case, one might forget to create the user / group on the box >> where you're installing it. >> >> I have this same issue and never found a nice & clean solution. >> I'm also against automatic user creation and just throwing out a warning >> after installation (in doinst.sh) might not be very effective. >> >> As an administrator of several servers and desktops, I use a local >> solution: >> - a shell script wrapper that calls installpkg >> - a centralized file with pre- & post- commands to run (pre- like >> checking for a user I need, post- like copying some standard configuration >> files I use for a specific package) >> But this is for local administration and I see no way to implement this >> in the SlackBuilds. >> >> But, as Robby, I'm open to suggestions to make my life easier :) >> >> >> -- >> Niels Horn >> >> >> On Tue, Jun 18, 2013 at 1:35 PM, King Beowulf wrote: >> >>> I'll vote for the manual method already used in some SBo scripts: >>> 1. Note default settings In README, instructing user to set up >>> user/group before running script >>> 2. Option such as GRP=blah ./script as needed to set up rc etc >>> >>> I think this is the most generic, easiest to avoid stomping on settings. >>> >>> Ed >>> >>> >>> >>> On 6/18/13, Robby Workman wrote: >>> > On Tue, 18 Jun 2013 03:17:43 -0700 >>> > Miguel De Anda wrote: >>> > >>> >> what's the best practice for server/daemon apps that we want to run >>> >> as an unprivileged user/group? for example, apache often runs as >>> >> apache.apache and mysql as mysql.mysql. >>> >> >>> >> i found one build script that has a grep for /etc/passwd >>> >> and /etc/group and has some hard-coded uid/gid's in the suggested >>> >> user/groups. my concern with this method is that if you archive the >>> >> tgz file (to install on a remote machine for example) you have to >>> >> remember that you ran some commands against the buidl system. do we >>> >> want to add a similar check in the doinst.sh script? maybe a warning? >>> > >>> > >>> > I've been bitten by this on some of my own systems, but I'm not >>> > convinced that there's a *good* solution to it. >>> > >>> > A note in doinst.sh is likely (almost sure) to be missed by many >>> > admins (e.g. me) who do "batch installs" of add-ons to newly >>> > deployed systems, so the extra work of adding notes there isn't >>> > really something I want to commit to doing. >>> > >>> > I also don't really like the idea of checking for existence of >>> > any required user/group and automatically creating it/them if >>> > it/they do not already exist, and again I'll draw on my own >>> > experience for that: I like to keep my UIDs and GIDs in sync >>> > across all of my systems, so I'd rather have something fail >>> > horribly due to a missing user/group than have a stealthily >>> > created (and wrong/inconsistent) user and uid present. I use >>> > NFS locally so UID/GID consistency is a big deal for me. >>> > >>> > All that said, I'm not against doing all of this in a better >>> > way, but I'll have to be convinced that it's actually better :-) >>> > >>> > -RW >>> > >>> >>> -- >>> Sent from my mobile device >>> >>> You! What PLANET is this! >>> -- McCoy, "The City on the Edge of Forever", stardate 3134.0 >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - http://slackbuilds.org/faq/ >>> >>> >> >> _______________________________________________ >> 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 melikamp at melikamp.com Tue Jun 18 18:37:02 2013 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Tue, 18 Jun 2013 14:37:02 -0400 Subject: [Slackbuilds-users] on creating users In-Reply-To: References: <20130618102125.57dece27@home.rlworkman.net> Message-ID: <51C0A8CE.30003@melikamp.com> Just throwing it out there, so don't judge me harshly :P Why not have the post-install script create user/group automagically, but have the slackbuild process variables, say, PKG_USER, PKG_GROUP, PKG_UID, and PKG_GID, and that way you can build your package with custom credentials which jive with your setup. If either variable is undefined, skip user/group creation. On 06/18/2013 01:58 PM, Miguel De Anda wrote: > thanks. i guess the safest answer is to not automatically create the user. > i'm thinking of adding a note in the slack-desc and possibly in the rc script > as well. something along the lines of > > echo "$PRGNAME failed to start because it requires a group/user > $GRPNAME/$USRNAME" exit 1 > > miguel > > > On Tue, Jun 18, 2013 at 9:45 AM, Niels Horn > wrote: > > The manual method is fine if you build-once / install once. But if I > understood correctly, Miguel's question is about build-once / install-many, > storing the created package centrally and then installing it on several > boxes. > > In this case, one might forget to create the user / group on the box where > you're installing it. > > I have this same issue and never found a nice & clean solution. I'm also > against automatic user creation and just throwing out a warning after > installation (in doinst.sh) might not be very effective. > > As an administrator of several servers and desktops, I use a local solution: > - a shell script wrapper that calls installpkg - a centralized file with pre- > & post- commands to run (pre- like checking for a user I need, post- like > copying some standard configuration files I use for a specific package) But > this is for local administration and I see no way to implement this in the > SlackBuilds. > > But, as Robby, I'm open to suggestions to make my life easier :) > > > -- Niels Horn > > > On Tue, Jun 18, 2013 at 1:35 PM, King Beowulf > wrote: > > I'll vote for the manual method already used in some SBo scripts: 1. Note > default settings In README, instructing user to set up user/group before > running script 2. Option such as GRP=blah ./script as needed to set up rc > etc > > I think this is the most generic, easiest to avoid stomping on settings. > > Ed > > > > On 6/18/13, Robby Workman > wrote: >> On Tue, 18 Jun 2013 03:17:43 -0700 Miguel De Anda > > wrote: >> >>> what's the best practice for server/daemon apps that we want to run as an >>> unprivileged user/group? for example, apache often runs as apache.apache >>> and mysql as mysql.mysql. >>> >>> i found one build script that has a grep for /etc/passwd and /etc/group >>> and has some hard-coded uid/gid's in the suggested user/groups. my >>> concern with this method is that if you archive the tgz file (to install >>> on a remote machine for example) you have to remember that you ran some >>> commands against the buidl system. do we want to add a similar check in >>> the doinst.sh script? maybe a warning? >> >> >> I've been bitten by this on some of my own systems, but I'm not convinced >> that there's a *good* solution to it. >> >> A note in doinst.sh is likely (almost sure) to be missed by many admins >> (e.g. me) who do "batch installs" of add-ons to newly deployed systems, so >> the extra work of adding notes there isn't really something I want to >> commit to doing. >> >> I also don't really like the idea of checking for existence of any required >> user/group and automatically creating it/them if it/they do not already >> exist, and again I'll draw on my own experience for that: I like to keep my >> UIDs and GIDs in sync across all of my systems, so I'd rather have >> something fail horribly due to a missing user/group than have a stealthily >> created (and wrong/inconsistent) user and uid present. I use NFS locally >> so UID/GID consistency is a big deal for me. >> >> All that said, I'm not against doing all of this in a better way, but I'll >> have to be convinced that it's actually better :-) >> >> -RW >> > > -- Sent from my mobile device > > You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", > stardate 3134.0 _______________________________________________ > SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - > http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - > http://slackbuilds.org/faq/ > > > > _______________________________________________ SlackBuilds-users mailing > list SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - > http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - > http://slackbuilds.org/faq/ > > > > > > _______________________________________________ SlackBuilds-users mailing > list SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - > http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - > http://slackbuilds.org/faq/ > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 901 bytes Desc: OpenPGP digital signature URL: From niels.horn at gmail.com Tue Jun 18 20:59:04 2013 From: niels.horn at gmail.com (Niels Horn) Date: Tue, 18 Jun 2013 17:59:04 -0300 Subject: [Slackbuilds-users] on creating users In-Reply-To: References: <20130618102125.57dece27@home.rlworkman.net> Message-ID: Miguel, This is not an issue. If the script creates a package with a file owned by user ABC with UID xyz, it will be installed with that UID. If the user does not exist on the box where you're installing the package, the file will still have that UID. Listing the files it won't show a user name, just the UID as the owner. I hope I managed to make it clear :) -- Niels Horn On Tue, Jun 18, 2013 at 3:13 PM, Miguel De Anda wrote: > I just realized something... I'm looking at the jboss and tomcat scripts > as they need users as well... the build script chown's some files under > that user/group. I think this would cause the package to fail if the > gid/uid on the target system doesn't match the build system right? Should > the rc script chown files as needed each time it starts? > > > On Tue, Jun 18, 2013 at 10:58 AM, Miguel De Anda wrote: > >> thanks. i guess the safest answer is to not automatically create the >> user. i'm thinking of adding a note in the slack-desc and possibly in the >> rc script as well. something along the lines of >> >> echo "$PRGNAME failed to start because it requires a group/user >> $GRPNAME/$USRNAME" >> exit 1 >> >> miguel >> >> >> On Tue, Jun 18, 2013 at 9:45 AM, Niels Horn wrote: >> >>> The manual method is fine if you build-once / install once. >>> But if I understood correctly, Miguel's question is about build-once / >>> install-many, storing the created package centrally and then installing it >>> on several boxes. >>> >>> In this case, one might forget to create the user / group on the box >>> where you're installing it. >>> >>> I have this same issue and never found a nice & clean solution. >>> I'm also against automatic user creation and just throwing out a warning >>> after installation (in doinst.sh) might not be very effective. >>> >>> As an administrator of several servers and desktops, I use a local >>> solution: >>> - a shell script wrapper that calls installpkg >>> - a centralized file with pre- & post- commands to run (pre- like >>> checking for a user I need, post- like copying some standard configuration >>> files I use for a specific package) >>> But this is for local administration and I see no way to implement this >>> in the SlackBuilds. >>> >>> But, as Robby, I'm open to suggestions to make my life easier :) >>> >>> >>> -- >>> Niels Horn >>> >>> >>> On Tue, Jun 18, 2013 at 1:35 PM, King Beowulf wrote: >>> >>>> I'll vote for the manual method already used in some SBo scripts: >>>> 1. Note default settings In README, instructing user to set up >>>> user/group before running script >>>> 2. Option such as GRP=blah ./script as needed to set up rc etc >>>> >>>> I think this is the most generic, easiest to avoid stomping on settings. >>>> >>>> Ed >>>> >>>> >>>> >>>> On 6/18/13, Robby Workman wrote: >>>> > On Tue, 18 Jun 2013 03:17:43 -0700 >>>> > Miguel De Anda wrote: >>>> > >>>> >> what's the best practice for server/daemon apps that we want to run >>>> >> as an unprivileged user/group? for example, apache often runs as >>>> >> apache.apache and mysql as mysql.mysql. >>>> >> >>>> >> i found one build script that has a grep for /etc/passwd >>>> >> and /etc/group and has some hard-coded uid/gid's in the suggested >>>> >> user/groups. my concern with this method is that if you archive the >>>> >> tgz file (to install on a remote machine for example) you have to >>>> >> remember that you ran some commands against the buidl system. do we >>>> >> want to add a similar check in the doinst.sh script? maybe a warning? >>>> > >>>> > >>>> > I've been bitten by this on some of my own systems, but I'm not >>>> > convinced that there's a *good* solution to it. >>>> > >>>> > A note in doinst.sh is likely (almost sure) to be missed by many >>>> > admins (e.g. me) who do "batch installs" of add-ons to newly >>>> > deployed systems, so the extra work of adding notes there isn't >>>> > really something I want to commit to doing. >>>> > >>>> > I also don't really like the idea of checking for existence of >>>> > any required user/group and automatically creating it/them if >>>> > it/they do not already exist, and again I'll draw on my own >>>> > experience for that: I like to keep my UIDs and GIDs in sync >>>> > across all of my systems, so I'd rather have something fail >>>> > horribly due to a missing user/group than have a stealthily >>>> > created (and wrong/inconsistent) user and uid present. I use >>>> > NFS locally so UID/GID consistency is a big deal for me. >>>> > >>>> > All that said, I'm not against doing all of this in a better >>>> > way, but I'll have to be convinced that it's actually better :-) >>>> > >>>> > -RW >>>> > >>>> >>>> -- >>>> Sent from my mobile device >>>> >>>> You! What PLANET is this! >>>> -- McCoy, "The City on the Edge of Forever", stardate 3134.0 >>>> _______________________________________________ >>>> SlackBuilds-users mailing list >>>> SlackBuilds-users at slackbuilds.org >>>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>>> FAQ - http://slackbuilds.org/faq/ >>>> >>>> >>> >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - http://slackbuilds.org/faq/ >>> >>> >>> >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From niels.horn at gmail.com Tue Jun 18 21:03:43 2013 From: niels.horn at gmail.com (Niels Horn) Date: Tue, 18 Jun 2013 18:03:43 -0300 Subject: [Slackbuilds-users] on creating users In-Reply-To: <51C0A8CE.30003@melikamp.com> References: <20130618102125.57dece27@home.rlworkman.net> <51C0A8CE.30003@melikamp.com> Message-ID: On Tue, Jun 18, 2013 at 3:37 PM, Ivan Zaigralin wrote: > Just throwing it out there, so don't judge me harshly :P > > Why not have the post-install script create user/group automagically, > but have the slackbuild process variables, say, PKG_USER, PKG_GROUP, > PKG_UID, and PKG_GID, and that way you can build your package with > custom credentials which jive with your setup. If either variable is > undefined, skip user/group creation. > > As said previously, I don't like the idea of automagically creating users... I prefer solving a problem with a program not working because of a missing user then to have users being created without my knowledge, with all the security risks involved. -- Niels Horn -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Wed Jun 19 04:38:26 2013 From: yalhcru at gmail.com (B Watson) Date: Wed, 19 Jun 2013 00:38:26 -0400 Subject: [Slackbuilds-users] Taking over mupdf Message-ID: The previous maintainer stopped using Slackware... I maintain zathura-pdf-mupdf, the only package on SBo that depends on mupdf, so it makes sense for me to take this one. Email from old maintainer: ---------- Forwarded message ---------- From: Hubert Hesse Date: Tue, 18 Jun 2013 09:56:13 +0200 Subject: Re: SBo mupdf 1.2 update? To: B Watson Hi, I totally forgot that I still maintain packages @ SBo. I don't have a slackware 14.0 installation at hand, I switched to Ubuntu ten months ago. So I would be happy I you could take over. Otherwise it will take a while, setting up a VM and so forth. From rworkman at slackbuilds.org Wed Jun 19 05:16:59 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 19 Jun 2013 00:16:59 -0500 Subject: [Slackbuilds-users] on creating users In-Reply-To: References: <20130618102125.57dece27@home.rlworkman.net> Message-ID: <20130619001659.62427623@home.rlworkman.net> On Tue, 18 Jun 2013 11:13:46 -0700 Miguel De Anda wrote: > I just realized something... I'm looking at the jboss and tomcat > scripts as they need users as well... the build script chown's some > files under that user/group. I think this would cause the package to > fail if the gid/uid on the target system doesn't match the build > system right? Should the rc script chown files as needed each time it > starts? I can't figure out how to say this, so I'll just show it - I *think* this is what you're asking: root at pkgdev32:~# groupadd -g 300 testgroup root at pkgdev32:~# useradd -d /dev/null -s /bin/false -u 300 -g 300 testuser root at pkgdev32:~# touch testfile root at pkgdev32:~# chown testuser:testgroup testfile root at pkgdev32:~# ls -lh testfile -rw-r--r-- 1 testuser testgroup 0 Jun 19 00:13 testfile root at pkgdev32:~# tar cf test.tar testfile root at pkgdev32:~# tar tvf test.tar -rw-r--r-- testuser/testgroup 0 2013-06-19 00:13 testfile root at pkgdev32:~# getent group testgroup ; getent passwd testuser testgroup:x:300: testuser:x:300:300::/dev/null:/bin/false root at pkgdev32:~# scp test.tar pkgdev64:. The authenticity of host 'pkgdev64 (2001:470:8:937:a00:27ff:fe00:42)' can't be established. ECDSA key fingerprint is f3:c6:c5:28:19:94:25:ec:e4:55:bd:c7:81:c9:26:fa. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'pkgdev64,2001:470:8:937:a00:27ff:fe00:42' (ECDSA) to the list of known hosts. root at pkgdev64's password: test.tar ... switching to pkgdev64 host ... root at pkgdev64:~# ls -lh test.tar -rw-r--r-- 1 root root 10K Jun 19 00:12 test.tar root at pkgdev64:~# tar tvf test.tar -rw-r--r-- testuser/testgroup 0 2013-06-19 00:13 testfile root at pkgdev64:~# groupadd -g 700 testgroup root at pkgdev64:~# useradd -d /dev/null -s /bin/false -u 900 -g 700 testuser root at pkgdev64:~# tar xvf test.tar testfile root at pkgdev64:~# ls -lh testfile -rw-r--r-- 1 testuser testgroup 0 Jun 19 00:13 testfile root at pkgdev64:~# getent group testgroup ; getent passwd testuser testgroup:x:700: testuser:x:900:700::/dev/null:/bin/false -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Wed Jun 19 05:18:12 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 19 Jun 2013 00:18:12 -0500 Subject: [Slackbuilds-users] on creating users In-Reply-To: References: <20130618102125.57dece27@home.rlworkman.net> Message-ID: <20130619001812.4f95c59e@home.rlworkman.net> On Tue, 18 Jun 2013 10:58:03 -0700 Miguel De Anda wrote: > thanks. i guess the safest answer is to not automatically create the > user. i'm thinking of adding a note in the slack-desc and possibly in > the rc script as well. something along the lines of > > echo "$PRGNAME failed to start because it requires a group/user > $GRPNAME/$USRNAME" > exit 1 I think it's needless cruft in the slack-desc. It *might* be possible to convince me that the init script would be a decent place to do that. r -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From C.J.Theunissen at differ.nl Wed Jun 19 10:24:27 2013 From: C.J.Theunissen at differ.nl (Kees Theunissen) Date: Wed, 19 Jun 2013 12:24:27 +0200 (CEST) Subject: [Slackbuilds-users] on creating users In-Reply-To: <20130619001812.4f95c59e@home.rlworkman.net> References: <20130618102125.57dece27@home.rlworkman.net> <20130619001812.4f95c59e@home.rlworkman.net> Message-ID: On Wed, 19 Jun 2013, Robby Workman wrote: >On Tue, 18 Jun 2013 10:58:03 -0700 >Miguel De Anda wrote: > >> thanks. i guess the safest answer is to not automatically create the >> user. i'm thinking of adding a note in the slack-desc and possibly in >> the rc script as well. something along the lines of >> >> echo "$PRGNAME failed to start because it requires a group/user >> $GRPNAME/$USRNAME" >> exit 1 > > >I think it's needless cruft in the slack-desc. > >It *might* be possible to convince me that the init script would >be a decent place to do that. r > >-RW > An application or daemon should IMHO not chance the system configuration when started. If a program can not run as intended/configured if should simply fail to start and log/report that failure. If (a badly written) daemon would run as root when the intended user/group is missing then the init script should test if the user/group exists. You (RW) wrote yesterday: ... so I'd rather have something fail horribly due to a missing user/group than have a stealthily created (and wrong/inconsistent) user and uid present. I'd rather have things fail nicely in such a case. :-) Groeten, Kees. -- Kees Theunissen, Systeem- en netwerkbeheerder, Tel: 030-6096724 Dutch Institute For Fundamental Energy Research (DIFFER) e-mailadres: C.J.Theunissen at differ.nl postadres: Postbus 1207, 3430 BE Nieuwegein bezoekersadres: Edisonbaan 14, 3439 MN Nieuwegein From miguel at thedeanda.com Wed Jun 19 16:08:22 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Wed, 19 Jun 2013 09:08:22 -0700 Subject: [Slackbuilds-users] on creating users In-Reply-To: References: <20130618102125.57dece27@home.rlworkman.net> <20130619001812.4f95c59e@home.rlworkman.net> Message-ID: thanks robby -- that's exactly was i was worried about (different gid/uid on different machine) On Wed, Jun 19, 2013 at 3:24 AM, Kees Theunissen wrote: > On Wed, 19 Jun 2013, Robby Workman wrote: > > >On Tue, 18 Jun 2013 10:58:03 -0700 > >Miguel De Anda wrote: > > > >> thanks. i guess the safest answer is to not automatically create the > >> user. i'm thinking of adding a note in the slack-desc and possibly in > >> the rc script as well. something along the lines of > >> > >> echo "$PRGNAME failed to start because it requires a group/user > >> $GRPNAME/$USRNAME" > >> exit 1 > > > > > >I think it's needless cruft in the slack-desc. > > > >It *might* be possible to convince me that the init script would > >be a decent place to do that. r > > > >-RW > > > > An application or daemon should IMHO not chance the system configuration > when started. If a program can not run as intended/configured if should > simply fail to start and log/report that failure. > > If (a badly written) daemon would run as root when the intended user/group > is missing then the init script should test if the user/group exists. > > You (RW) wrote yesterday: > ... so I'd rather have something fail > horribly due to a missing user/group than have a stealthily > created (and wrong/inconsistent) user and uid present. > > I'd rather have things fail nicely in such a case. :-) > > Groeten, > > Kees. > > -- > Kees Theunissen, Systeem- en netwerkbeheerder, Tel: 030-6096724 > Dutch Institute For Fundamental Energy Research (DIFFER) > e-mailadres: C.J.Theunissen at differ.nl > postadres: Postbus 1207, 3430 BE Nieuwegein > bezoekersadres: Edisonbaan 14, 3439 MN Nieuwegein > > _______________________________________________ > 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 northrupthebandgeek at gmail.com Wed Jun 19 16:39:31 2013 From: northrupthebandgeek at gmail.com (Ryan Northrup) Date: Wed, 19 Jun 2013 09:39:31 -0700 Subject: [Slackbuilds-users] on creating users In-Reply-To: References: <20130618102125.57dece27@home.rlworkman.net> <51C0A8CE.30003@melikamp.com> Message-ID: On Tue, Jun 18, 2013 at 2:03 PM, Niels Horn wrote: > As said previously, I don't like the idea of automagically creating users... > I prefer solving a problem with a program not working because of a missing > user then to have users being created without my knowledge, with all the > security risks involved. Even if it defaults to not creating the user? I think that's what Ivan was going for: default to building a "safe" package that doesn't create new users, while providing the option for builders to create an "automagical" package by specifying those users/groups/UIDs/GIDs if desired. Just my two cents. - Ryan From slackbuilds at jq.oc9.com Fri Jun 21 00:13:57 2013 From: slackbuilds at jq.oc9.com (slackbuilds at jq.oc9.com) Date: Thu, 20 Jun 2013 20:13:57 -0400 (EDT) Subject: [Slackbuilds-users] on creating users In-Reply-To: References: <20130618102125.57dece27@home.rlworkman.net> <20130619001812.4f95c59e@home.rlworkman.net> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello All, I vote for leaving the passwd/group files alone, I manage them myself across several machines with scripts, without yellow pages and I do not recall Slackware messing with them before. Warnings and instructions on how to create users/groups printed on the screen at installpkg time or in init scripts are OK although. When possible, I create users for daemons even if they are not required, I also run them chroot when possible. Named (BIND) is a good example so the current behaviour is fine with me. - -ls -----BEGIN PGP SIGNATURE----- Comment: Signature num?rique / Digital signature : iD4DBQFRw5rHrcvAnluw1AYRArtZAJYmDua/j44Q6h1I2tTesZiBDCkoAKCBfUF/ tqXSH74c8d9DoeyQMc8Vpg== =59US -----END PGP SIGNATURE----- From rob0 at slackbuilds.org Fri Jun 21 05:10:56 2013 From: rob0 at slackbuilds.org (Rob McGee) Date: Fri, 21 Jun 2013 00:10:56 -0500 Subject: [Slackbuilds-users] lists.slackbuilds.org hardware problem Message-ID: <20130621051056.GA4182@harrier.slackbuilds.org> Harrier.slackbuilds.org a/k/a lists.slackbuilds.org, your humble list host, is having hardware problems: looks like two (count-'em! two!) hard drives are pinin' for the fjords. We're not sure what we'll have to do nor when we'll be able to do it, but we'll try to keep you posted in IRC. The mailing list (as well as all @slackbuilds.org addresses) might be down for 1-3 days. I expect it to be closer to the 1 than the 3, but you know how that goes. We should be able to get to Birmingham, Alabama tomorrow if necessary. Note: this is NOT a solicitation for donations, but it's as good a time as any to thank you all again for your response to the 2011 request. Yes, this is that machine that was built with your donations. Go figure. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From yochanon at lavabit.com Fri Jun 21 11:15:21 2013 From: yochanon at lavabit.com (JB) Date: Fri, 21 Jun 2013 06:15:21 -0500 Subject: [Slackbuilds-users] lists.slackbuilds.org hardware problem In-Reply-To: <20130621051056.GA4182@harrier.slackbuilds.org> References: <20130621051056.GA4182@harrier.slackbuilds.org> Message-ID: <20130621061521.37bbc179@beer.bong> On Fri, 21 Jun 2013 00:10:56 -0500 Rob McGee wrote: > Harrier.slackbuilds.org a/k/a lists.slackbuilds.org, your humble list > host, is having hardware problems: looks like two (count-'em! two!) > hard drives are pinin' for the fjords. > > We're not sure what we'll have to do nor when we'll be able to do it, > but we'll try to keep you posted in IRC. The mailing list (as well as > all @slackbuilds.org addresses) might be down for 1-3 days. > > I expect it to be closer to the 1 than the 3, but you know how that > goes. We should be able to get to Birmingham, Alabama tomorrow if > necessary. > > Note: this is NOT a solicitation for donations, but it's as good a > time as any to thank you all again for your response to the 2011 > request. Yes, this is that machine that was built with your > donations. Go figure. Drat...an hdd only lasting two years sucks! I wish I could help donate but it's the end of the month and I splurged $80 on going to a VNVLV/MC rally two weekends ago so I'm broke...literally (disability checks don't go very far whether I splurge or not, heh). -- "Americans [have] the right and advantage of being armed, unlike the citizens of other countries whose governments are afraid to trust their people with arms." -James Madison -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 230 bytes Desc: not available URL: From rob0 at slackbuilds.org Fri Jun 21 15:06:14 2013 From: rob0 at slackbuilds.org (Rob McGee) Date: Fri, 21 Jun 2013 10:06:14 -0500 Subject: [Slackbuilds-users] lists.slackbuilds.org hardware problem In-Reply-To: <20130621061521.37bbc179@beer.bong> References: <20130621051056.GA4182@harrier.slackbuilds.org> <20130621061521.37bbc179@beer.bong> Message-ID: <20130621150614.GB4182@harrier.slackbuilds.org> Status update: It's still running. Mail seems fine, but HTTP (which includes the list archives and the web interface to subscriptions) is down. We're showing a ridiculous load average (93 as I type here) which seems mostly due to httpd zombies which tried to read from suspected bad drives. The suspects are a pair of "green" drives in RAID. Each are showing I/O errors in dmesg. No, we did not buy those with donated money; these were hardware donations from one of us. For the record: avoid "green" drives, especially in servers. I doubt they truly save any energy, what with all the energy that the inevitably early failures waste. Ideally the downtime will be brief. We'll know more and let you know in a bit. On Fri, Jun 21, 2013 at 06:15:21AM -0500, JB wrote: > > On Fri, 21 Jun 2013 00:10:56 -0500 > Rob McGee wrote: > > > Note: this is NOT a solicitation for donations, but it's as good > > a time as any to thank you all again for your response to the > > 2011 request. Yes, this is that machine that was built with your > > donations. Go figure. > > Drat...an hdd only lasting two years sucks! I wish I could help > donate but ... ... but we are NOT soliciting nor accepting donations at this time. Thanks for the thought, but no, not now. :) Anyone with money burning holes in pockets is welcome to donate to Slackware: http://store.slackware.com/cgi-bin/store/slackdonation?id=2qYiiCh4&mv_pc=202 That's what we did with the excess funds from our 2011 request. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From kingbeowulf at gmail.com Fri Jun 21 15:34:23 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 21 Jun 2013 08:34:23 -0700 Subject: [Slackbuilds-users] lists.slackbuilds.org hardware problem In-Reply-To: <20130621150614.GB4182@harrier.slackbuilds.org> References: <20130621051056.GA4182@harrier.slackbuilds.org> <20130621061521.37bbc179@beer.bong> <20130621150614.GB4182@harrier.slackbuilds.org> Message-ID: I've never had much luck with the WD "green" drives. The blue and black consumer level drives seem ok (got 2 blues 500 GB at 5 and 3 yrs old still error free). However, since I have a bunch of family digital pics, home movies that I don't want to risk loosing, I'm looking at the WD RE4 series enterprise class. A bit pricey but specs look impressive. Ed On 6/21/13, Rob McGee wrote: > Status update: It's still running. Mail seems fine, but HTTP (which > includes the list archives and the web interface to subscriptions) is > down. We're showing a ridiculous load average (93 as I type here) > which seems mostly due to httpd zombies which tried to read from > suspected bad drives. > > The suspects are a pair of "green" drives in RAID. Each are showing > I/O errors in dmesg. No, we did not buy those with donated money; > these were hardware donations from one of us. > > For the record: avoid "green" drives, especially in servers. I doubt > they truly save any energy, what with all the energy that the > inevitably early failures waste. > > Ideally the downtime will be brief. We'll know more and let you know > in a bit. > > > On Fri, Jun 21, 2013 at 06:15:21AM -0500, JB wrote: >> >> On Fri, 21 Jun 2013 00:10:56 -0500 >> Rob McGee wrote: >> >> > Note: this is NOT a solicitation for donations, but it's as good >> > a time as any to thank you all again for your response to the >> > 2011 request. Yes, this is that machine that was built with your >> > donations. Go figure. >> >> Drat...an hdd only lasting two years sucks! I wish I could help >> donate but ... > > ... but we are NOT soliciting nor accepting donations at this time. > Thanks for the thought, but no, not now. :) > > Anyone with money burning holes in pockets is welcome to donate to > Slackware: > > http://store.slackware.com/cgi-bin/store/slackdonation?id=2qYiiCh4&mv_pc=202 > > That's what we did with the excess funds from our 2011 request. > -- > Rob McGee - /dev/rob0 - rob0 at slackbuilds.org > _______________________________________________ > 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 rworkman at slackbuilds.org Fri Jun 21 15:45:24 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 21 Jun 2013 10:45:24 -0500 Subject: [Slackbuilds-users] lists.slackbuilds.org hardware problem In-Reply-To: <20130621061521.37bbc179@beer.bong> References: <20130621051056.GA4182@harrier.slackbuilds.org> <20130621061521.37bbc179@beer.bong> Message-ID: <20130621104524.1551f8fb@home.rlworkman.net> On Fri, 21 Jun 2013 06:15:21 -0500 JB wrote: > On Fri, 21 Jun 2013 00:10:56 -0500 > Rob McGee wrote: > > > Harrier.slackbuilds.org a/k/a lists.slackbuilds.org, your humble > > list host, is having hardware problems: looks like two (count-'em! > > two!) hard drives are pinin' for the fjords. > > > > We're not sure what we'll have to do nor when we'll be able to do > > it, but we'll try to keep you posted in IRC. The mailing list (as > > well as all @slackbuilds.org addresses) might be down for 1-3 days. > > > > I expect it to be closer to the 1 than the 3, but you know how that > > goes. We should be able to get to Birmingham, Alabama tomorrow if > > necessary. > > > > Note: this is NOT a solicitation for donations, but it's as good a > > time as any to thank you all again for your response to the 2011 > > request. Yes, this is that machine that was built with your > > donations. Go figure. > > Drat...an hdd only lasting two years sucks! I wish I could help > donate but it's the end of the month and I splurged $80 on going to a > VNVLV/MC rally two weekends ago so I'm broke...literally (disability > checks don't go very far whether I splurge or not, heh). No worries - I've got a few enterprise-grade 1TB drives lying around somewhere, and if I *have* to, I'll steal a couple of 2TB drives from my backup fileserver... :-) The difficult part right now is coordinating a trip to the datacenter; my wife is leaving for out of town this evening with one of the kids, and I've got the other one for the weekend. I suspect our colo host will not look kindly upon a three year old in the server room ;-) -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 Fri Jun 21 15:46:24 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 21 Jun 2013 10:46:24 -0500 Subject: [Slackbuilds-users] lists.slackbuilds.org hardware problem In-Reply-To: References: <20130621051056.GA4182@harrier.slackbuilds.org> <20130621061521.37bbc179@beer.bong> <20130621150614.GB4182@harrier.slackbuilds.org> Message-ID: <20130621104624.6af7475d@home.rlworkman.net> On Fri, 21 Jun 2013 08:34:23 -0700 King Beowulf wrote: > I've never had much luck with the WD "green" drives. The blue and > black consumer level drives seem ok (got 2 blues 500 GB at 5 and 3 yrs > old still error free). However, since I have a bunch of family > digital pics, home movies that I don't want to risk loosing, I'm > looking at the WD RE4 series enterprise class. A bit pricey but specs > look impressive. As it often seems with hardware, you get what you pay for, eh? :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From chris at teria.org Fri Jun 21 16:13:30 2013 From: chris at teria.org (Chris) Date: Fri, 21 Jun 2013 18:13:30 +0200 Subject: [Slackbuilds-users] lists.slackbuilds.org hardware problem In-Reply-To: <20130621104624.6af7475d@home.rlworkman.net> References: <20130621051056.GA4182@harrier.slackbuilds.org> <20130621061521.37bbc179@beer.bong> <20130621150614.GB4182@harrier.slackbuilds.org> <20130621104624.6af7475d@home.rlworkman.net> Message-ID: <20130621181330.29899018@station.paris.ld> WD Green drives are subject to aggressive head parking ... This is sadly a well known issue :/ Eventually in a RAID environment, it destroys the drives ... I lost myself one of these drives. Everything is exaplained here : http://koitsu.wordpress.com/2012/05/30/wd30ezrx-and-aggressive-head-parking/ The solution is to disable the Idle3 functionality of these drives. Official WD tool to do this is a DOS floppy disk (yeah ...). Fortunately some people released an unofficial tool which works like a charm under Slackware e.g. http://sourceforge.net/projects/idle3-tools/ On Fri, 21 Jun 2013 10:46:24 -0500 Robby Workman wrote: > On Fri, 21 Jun 2013 08:34:23 -0700 > King Beowulf wrote: > > > I've never had much luck with the WD "green" drives. The blue and > > black consumer level drives seem ok (got 2 blues 500 GB at 5 and 3 yrs > > old still error free). However, since I have a bunch of family > > digital pics, home movies that I don't want to risk loosing, I'm > > looking at the WD RE4 series enterprise class. A bit pricey but specs > > look impressive. > > > As it often seems with hardware, you get what you pay for, eh? :-) > > -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From slackware at caisteal.net Fri Jun 21 23:19:42 2013 From: slackware at caisteal.net (W. D. Milner) Date: Fri, 21 Jun 2013 20:19:42 -0300 Subject: [Slackbuilds-users] lists.slackbuilds.org hardware problem In-Reply-To: <20130621181330.29899018@station.paris.ld> References: <20130621051056.GA4182@harrier.slackbuilds.org> <20130621061521.37bbc179@beer.bong> <20130621150614.GB4182@harrier.slackbuilds.org> <20130621104624.6af7475d@home.rlworkman.net> <20130621181330.29899018@station.paris.ld> Message-ID: <51C4DF8E.3090901@caisteal.net> On 06/21/2013 01:13 PM, Chris wrote: > > > WD Green drives are subject to aggressive head parking ... This is sadly a well known issue :/ Eventually in a RAID environment, it destroys the drives ... I lost myself one of these drives. > Everything is exaplained here : > http://koitsu.wordpress.com/2012/05/30/wd30ezrx-and-aggressive-head-parking/ > > The solution is to disable the Idle3 functionality of these drives. Official WD tool to do this is a DOS floppy disk (yeah ...). Fortunately some people released an unofficial tool which works like a charm under Slackware e.g. > http://sourceforge.net/projects/idle3-tools/ The solution is to use appropriate drives for the purpose. There are reasons some drives are specified for RAID/enterprise use. Yes they cost more, but they are also far more reliable and longer lasting than desktop drives used in the same environment. -- W. D. Milner (a.k.a. NyteOwl) Slackware Documentation Project - Editor http://docs.slackware.com/ #slackdocs on irc.freenode.net From yalhcru at gmail.com Sat Jun 22 00:48:39 2013 From: yalhcru at gmail.com (B Watson) Date: Fri, 21 Jun 2013 20:48:39 -0400 Subject: [Slackbuilds-users] lists.slackbuilds.org hardware problem In-Reply-To: <51C4DF8E.3090901@caisteal.net> References: <20130621051056.GA4182@harrier.slackbuilds.org> <20130621061521.37bbc179@beer.bong> <20130621150614.GB4182@harrier.slackbuilds.org> <20130621104624.6af7475d@home.rlworkman.net> <20130621181330.29899018@station.paris.ld> <51C4DF8E.3090901@caisteal.net> Message-ID: On 6/21/13, W. D. Milner wrote: > The solution is to use appropriate drives for the purpose. There are > reasons some drives are specified for RAID/enterprise use. Yes they cost > more, but they are also far more reliable and longer lasting than > desktop drives used in the same environment. >From reading the linked articles, it looks like these "desktop" drives are useless even for casual desktop use (they still die young, and they cause GUIs to freeze up while waiting for the heads to unpark). From ml at mareichelt.com Sat Jun 22 16:52:12 2013 From: ml at mareichelt.com (Markus Reichelt) Date: Sat, 22 Jun 2013 18:52:12 +0200 Subject: [Slackbuilds-users] allmydata-tahoe keyword fix Message-ID: <20130622165212.GA3572@pc21.mareichelt.com> http://slackbuilds.org/repository/14.0/network/allmydata-tahoe/ lists 'ditributed' instead of 'distributed' keyword. please fix. From niels.horn at slackbuilds.org Sun Jun 23 01:17:11 2013 From: niels.horn at slackbuilds.org (Niels Horn) Date: Sat, 22 Jun 2013 22:17:11 -0300 Subject: [Slackbuilds-users] Updates - 20130623.1 Message-ID: <51C64C97.2090103@slackbuilds.org> In the tradition of the latest "themed updates", this one comes live from Brazil, host of the Confederations Cup (and several protests on the streets). Sun Jun 23 00:45:58 UTC 2013 academic/mapnik: Updated for version 2.2.0. audio/alsa-tools: Updated for version 1.0.27. audio/bristol: Updated for version 0.60.11. audio/jackmeter: Added (console peak meter for jack) audio/soundconverter: Updated for version 2.1.0. audio/transcribe: Updated for version 8.31.1. desktop/lxlauncher: Fixed dep info (add menu-cache) desktop/menulibre: Added (Menu editor with quicklist support) desktop/thunar-archive-plugin: Updated for version 0.3.1. desktop/thunar-media-tags-plugin: Updated for version 0.2.1. desktop/xfce4-dict: Updated for version 0.7.0. desktop/xfce4-mailwatch-plugin: Added (Xfce plugin for checking mails) desktop/xfce4-xkb-plugin: Updated for version 0.5.5. development/amd-app-sdk: Updated for version 2.8. development/anjuta: Updated for version 3.8.4. development/jdk: Updated for version 7u25. development/npm2tgz: Added (node.js module to Slackware package) development/rakudo: Updated for version 2013.05. games/alephone: Updated for version 20120514. games/atari++: Updated for version 1.72. games/dunelegacy: Updated for version 0.96.3. games/garden: Added (2D vertical shoot-em-up game) games/gzdoom: Updated for version 1.8.00. games/marathon-data: Updated for version 20120514. games/marathon-infinity-data: Updated for version 20120514. games/marathon2-data: Updated for version 20120514. games/qtsixa: Added (Sixaxis Joystick Manager) games/rocksndiamonds: Added (boulder dash-like arcade games) games/tintin: Added (console MUD client) games/xroar: Updated for version 0.29.5. graphics/SweetHome3D: Updated for version 4.1. graphics/exact-image: Updated for version 0.8.8. haskell/haskell-hxt-charproperties: Added (XML Character properties) haskell/haskell-hxt-regex-xmlschema: Added (XML Schema reg.exp.) haskell/haskell-hxt-unicode: Added (Unicode encoding and decoding) haskell/haskell-hxt: Added (Haskell XML Toolbox) libraries/ORBit2: Fix build on -current (harmless on 14.0) libraries/c-ares: Updated for version 1.10.0. libraries/gnome-media: Miscellaneous cleanup libraries/libbsd: Updated for version 0.5.2. libraries/libnfs: Updated for version 1.6.0. libraries/libnova: Fixed homepage link libraries/vte3: Updated for version 0.34.6. misc/dcc: Added (Distributed Checksum Clearinghouses) misc/nixnote: Added (Open Source Client for Evernote) network/etherape: Updated for version 0.9.13. network/frostwire: Updated for version 5.6.0. network/metasploit: Updated for version 4.6.0. network/opensmtpd: Updated for version 5.3.3p1. network/remmina: BUILD bump, added some patches. network/shorewall-core: Updated for version 4.5.17.1. network/shorewall6: Updated for version 4.5.17.1. network/shorewall: Updated for version 4.5.17.1. network/transmission-remote-gtk: Updated for version 1.1.1. network/yturl: Updated for version 20130618. office/ganttproject: Updated for version 2.6.1_r1499. perl/perl-CPANPLUS-Dist-Slackware: Updated for version 1.013. perl/perl-CSS-Squish: Added (Compact CSS files into one big file) perl/perl-DBD-SQLite: Updated for version 1.39. perl/perl-Text-Password-Pronounceable: Added (pronouncable passw.) perl/perl-Text-Quoted: Added (Extract structure of quoted message) perl/perl-data-dump: Updated for version 1.22. python/PyGreSQL: Added (Python PostgreSQL Interfaces) system/burp: Updated for version 1.3.32. system/cronie: Updated for version 1.4.9. system/ksh-openbsd: Updated for version 20130611. system/mongodb: Updated for version 2.4.4. system/numactl: Added (NUMA process control) system/reptyr: Updated for version 0.5_20130618. system/terminator: Updated for version 0.97. system/trackfs: Updated for version 0.1.0. system/unp: Added (unpack almost everything with one command) system/v86d: Added (x86 Emulation Daemon) -- Niels Horn From miguel at thedeanda.com Sun Jun 23 08:39:58 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Sun, 23 Jun 2013 01:39:58 -0700 Subject: [Slackbuilds-users] lists.slackbuilds.org hardware problem In-Reply-To: References: <20130621051056.GA4182@harrier.slackbuilds.org> <20130621061521.37bbc179@beer.bong> <20130621150614.GB4182@harrier.slackbuilds.org> <20130621104624.6af7475d@home.rlworkman.net> <20130621181330.29899018@station.paris.ld> <51C4DF8E.3090901@caisteal.net> Message-ID: aha! no wonder my computer am broke all the time. i bought a handful of these for my workstation and another machine acting as a nfs server used strictly for backup -- backups went to a software raid 5 on green drives. -m On Fri, Jun 21, 2013 at 5:48 PM, B Watson wrote: > On 6/21/13, W. D. Milner wrote: > > The solution is to use appropriate drives for the purpose. There are > > reasons some drives are specified for RAID/enterprise use. Yes they cost > > more, but they are also far more reliable and longer lasting than > > desktop drives used in the same environment. > > From reading the linked articles, it looks like these "desktop" drives > are useless even for casual desktop use (they still die young, and they > cause GUIs to freeze up while waiting for the heads to unpark). > _______________________________________________ > 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 yavor at atanasov.us Wed Jun 12 18:44:03 2013 From: yavor at atanasov.us (Yavor Atanasov) Date: Wed, 12 Jun 2013 14:44:03 -0400 Subject: [Slackbuilds-users] Unable to install package gimp-registry-plugins (0.0.2) Message-ID: Hello, I have a problem with installing the package "gimp-registry-plugins (0.0.2)" usign sboinstall... Here is and error for that failure: __________________________________________________________ Install queue: gimp-registry-plugins Are you sure you wish to continue? [y]: --2013-06-12 14:36:02-- http://registry.gimp.org/files/Eg-AddFilmGrain.scm Resolving registry.gimp.org (registry.gimp.org)... 188.40.148.209 Connecting to registry.gimp.org (registry.gimp.org)|188.40.148.209|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 4607 (4.5K) [application/octet-stream] Saving to: 'Eg-AddFilmGrain.scm' 100%[================================================================================================================================>] 4,607 29.2KB/s in 0.2s 2013-06-12 14:36:03 (29.2 KB/s) - 'Eg-AddFilmGrain.scm' saved [4607/4607] Unable to download/verify source file(s) for gimp-registry-plugins: md5sum failure for /usr/sbo/distfiles/Eg-AddFilmGrain.scm. Do you want to proceed? [n] y cp: cannot stat '/usr/sbo/graphics/gimp-registry-plugins/*.scm': No such file or directory Failures: gimp-registry-plugins: md5sum failure for /usr/sbo/distfiles/Eg-AddFilmGrain.scm. gimp-registry-plugins: gimp-registry-plugins.SlackBuild return non-zero ___________________________________________________________ P.S. Just for information - manual installation i.e. downloading package sources plus slackbuild script from your website and making package then install it working fine :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: From croftab at gmail.com Wed Jun 12 20:27:51 2013 From: croftab at gmail.com (Adam Croft) Date: Wed, 12 Jun 2013 16:27:51 -0400 Subject: [Slackbuilds-users] openmotif package update Message-ID: Wanted to know if someone would consider updating the openmotif slackbuild to v2.3.1. I emailed the maintainer but it seems the email address is no longer valid. Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: From j at dawnrazor.net Mon Jun 24 19:32:52 2013 From: j at dawnrazor.net (J) Date: Mon, 24 Jun 2013 14:32:52 -0500 Subject: [Slackbuilds-users] Unable to install package gimp-registry-plugins (0.0.2) Message-ID: <20130624143252.Horde.E5SotatIDJRWsU5lKd9ZMA1@mail.dawnrazor.net> Quoting Yavor Atanasov : > Hello, > I have a problem with installing the package "gimp-registry-plugins > (0.0.2)" usign sboinstall... Here is and error for that failure: > __________________________________________________________ > Install queue: gimp-registry-plugins > > Are you sure you wish to continue? [y]: > --2013-06-12 14:36:02-- http://registry.gimp.org/files/Eg-AddFilmGrain.scm > Resolving registry.gimp.org (registry.gimp.org)... 188.40.148.209 > Connecting to registry.gimp.org (registry.gimp.org)|188.40.148.209|:80... > connected. > HTTP request sent, awaiting response... 200 OK > Length: 4607 (4.5K) [application/octet-stream] > Saving to: 'Eg-AddFilmGrain.scm' > > 100%[================================================================================================================================>] > 4,607 29.2KB/s in 0.2s > > 2013-06-12 14:36:03 (29.2 KB/s) - 'Eg-AddFilmGrain.scm' saved [4607/4607] > > Unable to download/verify source file(s) for gimp-registry-plugins: > md5sum failure for /usr/sbo/distfiles/Eg-AddFilmGrain.scm. > > Do you want to proceed? [n] y > cp: cannot stat '/usr/sbo/graphics/gimp-registry-plugins/*.scm': No such > file or directory > Failures: > gimp-registry-plugins: md5sum failure for > /usr/sbo/distfiles/Eg-AddFilmGrain.scm. > gimp-registry-plugins: gimp-registry-plugins.SlackBuild return non-zero > ___________________________________________________________ > > P.S. Just for information - manual installation i.e. downloading package > sources plus slackbuild script from your website and making package then > install it working fine :-) Note that sbotools is a third party package not maintained by, endorsed by, or otherwise affiliated with SlackBuilds.org; if a SlackBuild installs normally when the SlackBuild is run manually, and fails using sboinstall, the situation should be reported not to this list but to the sbotools developers; you can find our contact information in any of the man pages included with sbotools, or in an obfuscated format on the sbotools site. Regarding this, it is an unfortunate fact that with certain pieces of software it is more difficult than others to keep the md5sum in sync with the source download; in deciding how to handle this with sbotools, it seemed evident that in the case of an md5sum failure, the only course of action for the user is to either find a download that matches, or instead the non-matching source to determine its validity; hence the error, the question, and the resulting failure - and, equally, your ability to run the SlackBuild manually. To put it concisely, this is the expected result for this condition. Thanks, J From slackbuilds at jq.oc9.com Mon Jun 24 21:08:53 2013 From: slackbuilds at jq.oc9.com (slackbuilds at jq.oc9.com) Date: Mon, 24 Jun 2013 17:08:53 -0400 (EDT) Subject: [Slackbuilds-users] Unable to install package gimp-registry-plugins (0.0.2) In-Reply-To: <20130624143252.Horde.E5SotatIDJRWsU5lKd9ZMA1@mail.dawnrazor.net> References: <20130624143252.Horde.E5SotatIDJRWsU5lKd9ZMA1@mail.dawnrazor.net> Message-ID: On Mon, 24 Jun 2013, J wrote: > Quoting Yavor Atanasov : > >> Hello, >> I have a problem with installing the package "gimp-registry-plugins >> (0.0.2)" usign sboinstall... Here is and error for that failure: >> __________________________________________________________ >> Install queue: gimp-registry-plugins >> >> Are you sure you wish to continue? [y]: >> --2013-06-12 14:36:02-- http://registry.gimp.org/files/Eg-AddFilmGrain.scm >> Resolving registry.gimp.org (registry.gimp.org)... 188.40.148.209 >> Connecting to registry.gimp.org (registry.gimp.org)|188.40.148.209|:80... >> connected. >> HTTP request sent, awaiting response... 200 OK >> Length: 4607 (4.5K) [application/octet-stream] >> Saving to: 'Eg-AddFilmGrain.scm' >> >> 100%[================================================================================================================================>] >> 4,607 29.2KB/s in 0.2s >> >> 2013-06-12 14:36:03 (29.2 KB/s) - 'Eg-AddFilmGrain.scm' saved [4607/4607] >> >> Unable to download/verify source file(s) for gimp-registry-plugins: >> md5sum failure for /usr/sbo/distfiles/Eg-AddFilmGrain.scm. >> >> Do you want to proceed? [n] y >> cp: cannot stat '/usr/sbo/graphics/gimp-registry-plugins/*.scm': No such >> file or directory >> Failures: >> gimp-registry-plugins: md5sum failure for >> /usr/sbo/distfiles/Eg-AddFilmGrain.scm. >> gimp-registry-plugins: gimp-registry-plugins.SlackBuild return non-zero >> ___________________________________________________________ >> >> P.S. Just for information - manual installation i.e. downloading package >> sources plus slackbuild script from your website and making package then >> install it working fine :-) > > Note that sbotools is a third party package not maintained by, endorsed by, > or otherwise affiliated with SlackBuilds.org; if a SlackBuild installs > normally when the SlackBuild is run manually, and fails using sboinstall, the > situation should be reported not to this list but to the sbotools developers; > you can find our contact information in any of the man pages included with > sbotools, or in an obfuscated format on the sbotools site. > > Regarding this, it is an unfortunate fact that with certain pieces of > software it is more difficult than others to keep the md5sum in sync with the > source download; in deciding how to handle this with sbotools, it seemed > evident that in the case of an md5sum failure, the only course of action for > the user is to either find a download that matches, or instead the > non-matching source to determine its validity; hence the error, the question, > and the resulting failure - and, equally, your ability to run the SlackBuild > manually. > > To put it concisely, this is the expected result for this condition. > > Thanks, > J > Yep, I started to use Slackbuilds a few months ago and it took me about 5 minutes to hack the Slackbuild script to build newer versions instead of the one the Slackbuild script expected... -ls > > > _______________________________________________ > 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 thomas at beingboiled.info Tue Jun 25 11:36:36 2013 From: thomas at beingboiled.info (Thomas Morper) Date: Tue, 25 Jun 2013 13:36:36 +0200 (CEST) Subject: [Slackbuilds-users] lighttpd & nginx In-Reply-To: References: Message-ID: On Mon, 29 Apr 2013, Thomas Morper wrote: > In November 2012 lighttpd 1.4.32 was released, containing a fix for a > critical bug. The SlackBuild, however, is still at 1.4.31. It's been two month and there has been neither an update nor a reply from Paul (I tried contacting him off-list, too). I don't want to take over maintenance as I'm in the process of migrating everything to nginx (which fits my needs better), but lighttpd is a nice webserver (easy to set up and well-documented) and shouldn't go unmaintained. Any lighty-users willing to step up? -- From matejek.martin at gmail.com Tue Jun 25 14:06:37 2013 From: matejek.martin at gmail.com (=?UTF-8?B?TWFydGluIE1hdMSbamVr?=) Date: Tue, 25 Jun 2013 16:06:37 +0200 Subject: [Slackbuilds-users] lighttpd & nginx In-Reply-To: References: Message-ID: <51C9A3ED.7080103@gmail.com> Dne 25.6.2013 13:36, Thomas Morper napsal(a): > On Mon, 29 Apr 2013, Thomas Morper wrote: > >> In November 2012 lighttpd 1.4.32 was released, containing a fix for a >> critical bug. The SlackBuild, however, is still at 1.4.31. > > It's been two month and there has been neither an update nor a reply from > Paul (I tried contacting him off-list, too). > > I don't want to take over maintenance as I'm in the process of migrating > everything to nginx (which fits my needs better), but lighttpd is a nice > webserver (easy to set up and well-documented) and shouldn't go > unmaintained. > > Any lighty-users willing to step up? > Lighttpd user here. I have manually rebuild packages on every servers from slackbuild, so I'd like to see upstream slackbuild updated. If maintainer won't respond, I'm willing to maintain lighty because I use it everywhere I can. From rshepard at appl-ecosys.com Wed Jun 26 00:29:08 2013 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 25 Jun 2013 17:29:08 -0700 (PDT) Subject: [Slackbuilds-users] Python Pandas Message-ID: Many of the Python scientific libraries can be found on the SBo site, but pandas is not there. Is there no one here using this library? On the pandas home page I read that it wants cpython installed, and there's no SlackBuild script for that either. Has anyone plans on creating and maintaining build scripts for these tools? Rich -- Richard B. Shepard, Ph.D. | Have knowledge, will travel. Applied Ecosystem Services, Inc. | Voice: 503-667-4517 Fax: 503-667-8863 From yalhcru at gmail.com Wed Jun 26 01:21:55 2013 From: yalhcru at gmail.com (B Watson) Date: Tue, 25 Jun 2013 21:21:55 -0400 Subject: [Slackbuilds-users] Python Pandas In-Reply-To: References: Message-ID: On 6/25/13, Rich Shepard wrote: > On the pandas home page I read that it wants cpython installed, and > there's no SlackBuild script for that either. I'm pretty sure "CPython" just means the C implementation of Python, aka the python 2.x package in core Slackware. No need for a separate SBo package, unless it specifically needs python 3.x (in which case, there's already a python3 on SBo). Someone correct me if I'm wrong. From rshepard at appl-ecosys.com Wed Jun 26 01:39:08 2013 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 25 Jun 2013 18:39:08 -0700 (PDT) Subject: [Slackbuilds-users] Python Pandas In-Reply-To: References: Message-ID: On Tue, 25 Jun 2013, B Watson wrote: > I'm pretty sure "CPython" just means the C implementation of Python, > aka the python 2.x package in core Slackware. I always thought Python was written in C which makes me wonder what the pandas folks think are other flavors of Python that they specify CPython. Thanks, Rich -- Richard B. Shepard, Ph.D. | Have knowledge, will travel. Applied Ecosystem Services, Inc. | Voice: 503-667-4517 Fax: 503-667-8863 From c.willing at uq.edu.au Wed Jun 26 01:45:25 2013 From: c.willing at uq.edu.au (Christoph Willing) Date: Wed, 26 Jun 2013 11:45:25 +1000 Subject: [Slackbuilds-users] Python Pandas In-Reply-To: References: Message-ID: <7867EBE0-88B3-4B72-BF50-8B1299FA1321@uq.edu.au> On 26/06/2013, at 10:29 AM, Rich Shepard wrote: > Many of the Python scientific libraries can be found on the SBo site, but > pandas is not there. Is there no one here using this library? > > On the pandas home page I read that it wants cpython installed, It refers to Cython (not CPython). From http://pandas.pydata.org/pandas-docs/stable/install.html, "Make sure you have Cython installed ..." There is a slackbuild for Cython. chris > and > there's no SlackBuild script for that either. Has anyone plans on creating > and maintaining build scripts for these tools? > > Rich > > -- > Richard B. Shepard, Ph.D. | Have knowledge, will travel. > Applied Ecosystem Services, Inc. | > Voice: 503-667-4517 Fax: 503-667-8863 > > _______________________________________________ > 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/ > Christoph Willing +61 7 3365 8316 Research Computing Centre University of Queensland From rshepard at appl-ecosys.com Wed Jun 26 01:48:36 2013 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 25 Jun 2013 18:48:36 -0700 (PDT) Subject: [Slackbuilds-users] Python Pandas In-Reply-To: <7867EBE0-88B3-4B72-BF50-8B1299FA1321@uq.edu.au> References: <7867EBE0-88B3-4B72-BF50-8B1299FA1321@uq.edu.au> Message-ID: On Wed, 26 Jun 2013, Christoph Willing wrote: > It refers to Cython (not CPython). From http://pandas.pydata.org/pandas-docs/stable/install.html, > "Make sure you have Cython installed ..." Thanks, Chris. I did not internalize the difference. > There is a slackbuild for Cython. OK. Tomorrow. Regards, Rich -- Richard B. Shepard, Ph.D. | Have knowledge, will travel. Applied Ecosystem Services, Inc. | Voice: 503-667-4517 Fax: 503-667-8863 From rworkman at slackbuilds.org Wed Jun 26 17:53:07 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 26 Jun 2013 12:53:07 -0500 Subject: [Slackbuilds-users] Server maintenance - 20130626 Message-ID: <20130626125307.6f7e0213@home.rlworkman.net> Somewhere are 1830-1900 UTC, I will be powering down the server that hosts SBo mailing lists, dns, and email (along with mirrors.slackware.com, rlworkman.net, slackpkg.org, sbopkg.org, slackbook.org, alienBOB's blog, and probably some other important things that I've forgotten. I will be replacing a couple of bad hard drives and probobly moving it to a different spot in the rack (well, that part depends on the datacenter guys - their call), so downtime should be relatively short. However, we all know how that goes. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From vito.detullio at gmail.com Wed Jun 26 18:19:11 2013 From: vito.detullio at gmail.com (Vito De Tullio) Date: Wed, 26 Jun 2013 20:19:11 +0200 Subject: [Slackbuilds-users] Python Pandas References: Message-ID: Rich Shepard wrote: >> I'm pretty sure "CPython" just means the C implementation of Python, >> aka the python 2.x package in core Slackware. > > I always thought Python was written in C which makes me wonder what the > pandas folks think are other flavors of Python that they specify CPython. as a side note: there are at least 4 "major" python-the-language implementations CPython (the classic "python", what you have on the slack, implemented in C) Jython (implemented in java - http://www.jython.org/) IronPython (implemented in c# - http://ironpython.net/) PyPy (implemented in python - http://pypy.org/) but the list is not exhaustive... on http://wiki.python.org/moin/PythonImplementations you can find others -- ZeD From rworkman at slackbuilds.org Wed Jun 26 23:31:37 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 26 Jun 2013 18:31:37 -0500 Subject: [Slackbuilds-users] Server maintenance - 20130626 In-Reply-To: <20130626125307.6f7e0213@home.rlworkman.net> References: <20130626125307.6f7e0213@home.rlworkman.net> Message-ID: <20130626183137.6da8be0c@home.rlworkman.net> On Wed, 26 Jun 2013 12:53:07 -0500 Robby Workman wrote: > Somewhere are 1830-1900 UTC, I will be powering down the > server that hosts SBo mailing lists, dns, and email > (along with mirrors.slackware.com, rlworkman.net, > slackpkg.org, sbopkg.org, slackbook.org, alienBOB's > blog, and probably some other important things that I've > forgotten. > > I will be replacing a couple of bad hard drives and > probobly moving it to a different spot in the rack (well, > that part depends on the datacenter guys - their call), > so downtime should be relatively short. However, we all > know how that goes. And of course, all went well - I just now got back home because I stopped at Hop City (any place that you can shop for beer while also drinking a beer is a must-visit, right?) and then visited a friend at another business in BHM. This is a good time to say "thank you" again to everyone who helped us buy that server, but I also want to sing some praises for the folks at TekLinks. They provide us with rack space, a /29 ipv4 address block, and bandwidth at no cost, and all they asked for in return was a link on our webpages. We've done that, of course, but it just doesn't seem like enough, so I want to publicly acknowledge their contributions again. They're good people and they know what they're doing - all of you IT pros whose companies uses services like what they provide, please consider them, and if you elect to contract with them, please advise them of why you considered them. Have a look: http://teklinks.com/ Once again, thanks to all and happy Slacking :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From miguel at thedeanda.com Thu Jun 27 06:35:01 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Wed, 26 Jun 2013 23:35:01 -0700 Subject: [Slackbuilds-users] building gparted Message-ID: whew its beeen a long night... it turns out i can't build gtkmm because the gnome mirror doesn't always server old files. closest i found to work is 2.24.3 (2.24.2 in SlackBuild). after a few modifications to the script, i found that gtkmm requires pangomm (not listed on the site). anyway new gtk/gnome stuff seems to use xz files so replace tar xvf foo.tar.gz with xz -d foo.tar.xz tar xvf foo.tar but i'm not sure how that affects things like sbopkg that might cache downloads. (xz -d file.tar.xz removes the .xz file and leaves only the tar) i'll keep everyone posted on notes and try to contact maintainers as well. regards, miguel -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Thu Jun 27 07:39:35 2013 From: yalhcru at gmail.com (B Watson) Date: Thu, 27 Jun 2013 03:39:35 -0400 Subject: [Slackbuilds-users] building gparted In-Reply-To: References: Message-ID: On 6/27/13, Miguel De Anda wrote: > anyway new gtk/gnome stuff seems to use xz files so replace > > tar xvf foo.tar.gz > > with > > xz -d foo.tar.xz > tar xvf foo.tar What version of Slackware are you using? "tar xvf" works fine on .tar.xz files in 14.0 and IIRC 13.37 also. From niels.horn at gmail.com Thu Jun 27 10:51:37 2013 From: niels.horn at gmail.com (Niels Horn) Date: Thu, 27 Jun 2013 07:51:37 -0300 Subject: [Slackbuilds-users] building gparted In-Reply-To: References: Message-ID: On Thu, Jun 27, 2013 at 3:35 AM, Miguel De Anda wrote: > > <...> > after a few modifications to the script, i found that gtkmm requires > pangomm (not listed on the site). > <...> > > regards, > miguel > > gtkmm needs atkmm, which needs pangomm, both listed on the site. And pangomm needs cairomm, which needs glibmm, which needs libsigc++. We only list direct dependencies of each SlackBuild, not "dependencies-of-dependencies". Regards, -- Niels Horn -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at gmail.com Thu Jun 27 12:19:21 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Thu, 27 Jun 2013 19:19:21 +0700 Subject: [Slackbuilds-users] building gparted In-Reply-To: References: Message-ID: > it turns out i can't build gtkmm because the gnome mirror doesn't always > server old files. closest i found to work is 2.24.3 (2.24.2 in SlackBuild). gtkmm 2.24.3 breaks several applications, such as MySQL-Workbench and also VMWare Workstation, so i would suggest you to stay away from 2.24.3 :) -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From miguel at thedeanda.com Thu Jun 27 17:47:13 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Thu, 27 Jun 2013 10:47:13 -0700 Subject: [Slackbuilds-users] building gparted In-Reply-To: References: Message-ID: thanks. i'll try again. it seems the gnome mirror is working this morning. On Thu, Jun 27, 2013 at 5:19 AM, Willy Sudiarto Raharjo wrote: > > it turns out i can't build gtkmm because the gnome mirror doesn't always > > server old files. closest i found to work is 2.24.3 (2.24.2 in > SlackBuild). > > gtkmm 2.24.3 breaks several applications, such as MySQL-Workbench and > also VMWare Workstation, so i would suggest you to stay away from > 2.24.3 :) > > > > -- > Willy Sudiarto Raharjo > Personal Blog : http://willysr.blogspot.com > Linux Blog: http://slackblogs.blogspot.com > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Fri Jun 28 16:48:49 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Fri, 28 Jun 2013 09:48:49 -0700 Subject: [Slackbuilds-users] building gparted In-Reply-To: References: Message-ID: i was finally able to build gtkmm -- i couldn't get it to work from sbopkg as the download failed. in fact, it failed from home as well when manually going to gtkmm site. from work i was able to get it so i had to copy it over then run the .SlackBuild directly. On Thu, Jun 27, 2013 at 10:47 AM, Miguel De Anda wrote: > > thanks. i'll try again. it seems the gnome mirror is working this morning. > > > On Thu, Jun 27, 2013 at 5:19 AM, Willy Sudiarto Raharjo > wrote: > >> > it turns out i can't build gtkmm because the gnome mirror doesn't always >> > server old files. closest i found to work is 2.24.3 (2.24.2 in >> SlackBuild). >> >> gtkmm 2.24.3 breaks several applications, such as MySQL-Workbench and >> also VMWare Workstation, so i would suggest you to stay away from >> 2.24.3 :) >> >> >> >> -- >> Willy Sudiarto Raharjo >> Personal Blog : http://willysr.blogspot.com >> Linux Blog: http://slackblogs.blogspot.com >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From niels.horn at slackbuilds.org Sat Jun 29 20:18:13 2013 From: niels.horn at slackbuilds.org (Niels Horn) Date: Sat, 29 Jun 2013 17:18:13 -0300 Subject: [Slackbuilds-users] Updates - 20130629.1 Message-ID: <51CF4105.4070902@slackbuilds.org> Hi, Our "approved" page has changed a bit since the previous public update, giving some more information on scripts that are ready: http://slackbuilds.org/ready/ Hope you all enjoy it as much as we do :) Sun Jun 23 00:45:58 UTC 2013 academic/mapnik: Updated for version 2.2.0. audio/alsa-tools: Updated for version 1.0.27. audio/bristol: Updated for version 0.60.11. audio/jackmeter: Added (console peak meter for jack) audio/soundconverter: Updated for version 2.1.0. audio/transcribe: Updated for version 8.31.1. desktop/lxlauncher: Fixed dep info (add menu-cache) desktop/menulibre: Added (Menu editor with quicklist support) desktop/thunar-archive-plugin: Updated for version 0.3.1. desktop/thunar-media-tags-plugin: Updated for version 0.2.1. desktop/xfce4-dict: Updated for version 0.7.0. desktop/xfce4-mailwatch-plugin: Added (Xfce plugin for checking mails) desktop/xfce4-xkb-plugin: Updated for version 0.5.5. development/amd-app-sdk: Updated for version 2.8. development/anjuta: Updated for version 3.8.4. development/jdk: Updated for version 7u25. development/npm2tgz: Added (node.js module to Slackware package) development/rakudo: Updated for version 2013.05. games/alephone: Updated for version 20120514. games/atari++: Updated for version 1.72. games/dunelegacy: Updated for version 0.96.3. games/garden: Added (2D vertical shoot-em-up game) games/gzdoom: Updated for version 1.8.00. games/marathon-data: Updated for version 20120514. games/marathon-infinity-data: Updated for version 20120514. games/marathon2-data: Updated for version 20120514. games/qtsixa: Added (Sixaxis Joystick Manager) games/rocksndiamonds: Added (boulder dash-like arcade games) games/tintin: Added (console MUD client) games/xroar: Updated for version 0.29.5. graphics/SweetHome3D: Updated for version 4.1. graphics/exact-image: Updated for version 0.8.8. haskell/haskell-hxt-charproperties: Added (XML Character properties) haskell/haskell-hxt-regex-xmlschema: Added (XML Schema reg.exp.) haskell/haskell-hxt-unicode: Added (Unicode encoding and decoding) haskell/haskell-hxt: Added (Haskell XML Toolbox) libraries/ORBit2: Fix build on -current (harmless on 14.0) libraries/c-ares: Updated for version 1.10.0. libraries/gnome-media: Miscellaneous cleanup libraries/libbsd: Updated for version 0.5.2. libraries/libnfs: Updated for version 1.6.0. libraries/libnova: Fixed homepage link libraries/vte3: Updated for version 0.34.6. misc/dcc: Added (Distributed Checksum Clearinghouses) misc/nixnote: Added (Open Source Client for Evernote) network/etherape: Updated for version 0.9.13. network/frostwire: Updated for version 5.6.0. network/metasploit: Updated for version 4.6.0. network/opensmtpd: Updated for version 5.3.3p1. network/remmina: BUILD bump, added some patches. network/shorewall-core: Updated for version 4.5.17.1. network/shorewall6: Updated for version 4.5.17.1. network/shorewall: Updated for version 4.5.17.1. network/transmission-remote-gtk: Updated for version 1.1.1. network/yturl: Updated for version 20130618. office/ganttproject: Updated for version 2.6.1_r1499. perl/perl-CPANPLUS-Dist-Slackware: Updated for version 1.013. perl/perl-CSS-Squish: Added (Compact CSS files into one big file) perl/perl-DBD-SQLite: Updated for version 1.39. perl/perl-Text-Password-Pronounceable: Added (pronouncable passw.) perl/perl-Text-Quoted: Added (Extract structure of quoted message) perl/perl-data-dump: Updated for version 1.22. python/PyGreSQL: Added (Python PostgreSQL Interfaces) system/burp: Updated for version 1.3.32. system/cronie: Updated for version 1.4.9. system/ksh-openbsd: Updated for version 20130611. system/mongodb: Updated for version 2.4.4. system/numactl: Added (NUMA process control) system/reptyr: Updated for version 0.5_20130618. system/terminator: Updated for version 0.97. system/trackfs: Updated for version 0.1.0. system/unp: Added (unpack almost everything with one command) system/v86d: Added (x86 Emulation Daemon) -- Niels Horn From t3slider at gmail.com Sat Jun 29 21:05:39 2013 From: t3slider at gmail.com (T3slider) Date: Sat, 29 Jun 2013 17:05:39 -0400 Subject: [Slackbuilds-users] girara/zathura version mismatch Message-ID: <20130629210539.GA3160@MyPC.phub.net.cable.rogers.com> There is a mismatch between the .SlackBuild and .info files for girara and zathura on the site compared to the tarball. The explicit files are up to date (0.1.6 for girara and 0.2.3 for zathura) but the tarballs are the older versions (0.1.3 for girara and 0.2.0 for zathura). The source links and md5sums on slackbuilds.org for each package are the old ones as well. This obviously puts sbopkg into an upgrade loop. -T3slider From niels.horn at gmail.com Sat Jun 29 21:31:23 2013 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 29 Jun 2013 18:31:23 -0300 Subject: [Slackbuilds-users] girara/zathura version mismatch In-Reply-To: <20130629210539.GA3160@MyPC.phub.net.cable.rogers.com> References: <20130629210539.GA3160@MyPC.phub.net.cable.rogers.com> Message-ID: On Sat, Jun 29, 2013 at 6:05 PM, T3slider wrote: > There is a mismatch between the .SlackBuild and .info files for girara > and zathura on the site compared to the tarball. The explicit files are > up to date (0.1.6 for girara and 0.2.3 for zathura) but the tarballs are > the older versions (0.1.3 for girara and 0.2.0 for zathura). The source > links and md5sums on slackbuilds.org for each package are the old ones > as well. This obviously puts sbopkg into an upgrade loop. > > -T3slider > _______________________________________________ > 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/ > > Sorry, mea culpa... I did something in the wrong order but it *should* be all OK again. -- Niels Horn -------------- next part -------------- An HTML attachment was scrubbed... URL: From niels.horn at slackbuilds.org Sat Jun 29 21:44:42 2013 From: niels.horn at slackbuilds.org (Niels Horn) Date: Sat, 29 Jun 2013 18:44:42 -0300 Subject: [Slackbuilds-users] Fwd: Updates - 20130629.1 In-Reply-To: <51CF4105.4070902@slackbuilds.org> References: <51CF4105.4070902@slackbuilds.org> Message-ID: <51CF554A.7070509@slackbuilds.org> Hi, Err... This is the correct ChangeLog :) Sat Jun 29 19:29:45 UTC 2013 audio/caps: Updated for version 0.9.7. audio/ecasound: Updated for version 2.9.0. audio/jack-tools: Updated for version 20130616. audio/sooperlooper: Updated for version 1.7.0. audio/tap_plugins: Updated for version 0.7.2. audio/waon: Updated for version 0.10. desktop/xfce4-xkb-plugin: Updated for version 0.5.6. development/psycopg2: Updated for version 2.5.1. development/tcc: Updated for version 0.9.26. games/PyLotRO: Build bump. games/connectagram: Added (word unscrambling game) games/doomseeker: Updated for version 0.10b. games/firestorm-opensim: Added (an alternative Second Life client) games/firestorm: Updated for version 4.4.1.34164. games/pentagram: Updated for version 20130617_svn. games/sauerbraten: Updated for version 2013_02_03. games/tanglet: Added (single player word finding game) games/xonotic: Updated for version 0.7.0. games/xu4: Updated for version 20130612_svn. games/zdbsp: Updated for version 1.18.1. graphics/mirage: Fixes in SlackBuild. libraries/girara: Updated for version 0.1.6. libraries/jbig2dec: New maintainer + remove static lib. libraries/libnetfilter_acct: Updated for version 1.0.2. libraries/libnetfilter_conntrack: Updated for version 1.0.3. libraries/liboglappth: Fix for x86_64 libraries/libsecret: Added (library for accessing Secret Service API) misc/asterixInspector: Updated for version 0.9.3. misc/cwiid: Updated for version 0.6.00+svn201. misc/zyGrib: Updated for version 6.1.4. network/QuiteRSS: Added (RSS/Atom feed reader) network/fail2ban: Updated for version 0.8.10. network/hipchat: Fixed download links and tarball extraction network/metasploit: Fixed typo. network/razor-agents: Update license text. network/uget: Updated for version 1.10.3. office/mupdf: Upated for version 1.2 + new maintainer. office/texstudio: Updated for version 2.6.0. office/zathura-djvu: Updated fir version 0.2.3. office/zathura-pdf-mupdf: Updated for version 0.2.4. office/zathura-ps: Updated for version 0.2.2. office/zathura: Updated for version 0.2.3. python/Pyro4: Updated for version 4.20. python/python-urllib3: Updated for version 1.6. system/gdm: Fix crypt() usage with glibc-2.17+ system/seahorse: Updated for version 3.8.1. -- Niels Horn From info at microlinux.fr Sun Jun 30 09:39:52 2013 From: info at microlinux.fr (Niki Kovacs) Date: Sun, 30 Jun 2013 11:39:52 +0200 Subject: [Slackbuilds-users] Can't build libgda on Slackware64 14.0 Message-ID: <51CFFCE8.1080807@microlinux.fr> Hi, I just tried to build libgda (dependency for gtkpod). Built fine on 32-bit Slackware, but on 64-bit, I get the following build error: make[2] : on quitte le r?pertoire ? /tmp/microlinux/libgda-5.1.2/providers/sqlcipher ? Making all in ldap make[2] : on entre dans le r?pertoire ? /tmp/microlinux/libgda-5.1.2/providers/ldap ? CC gdaprov-data-model-ldap.lo CC gda-ldap-provider.lo CC gda-ldap-util.lo CC libmain.lo ITMRG ldap_specs_dsn.xml ITMRG ldap_specs_auth.xml CCLD libgda-ldap.la /usr/lib/libgobject-2.0.so: could not read symbols: File in wrong format collect2: error: ld returned 1 exit status make[2]: *** [libgda-ldap.la] Erreur 1 make[2] : on quitte le r?pertoire ? /tmp/microlinux/libgda-5.1.2/providers/ldap ? make[1]: *** [all-recursive] Erreur 1 make[1] : on quitte le r?pertoire ? /tmp/microlinux/libgda-5.1.2/providers ? make: *** [all-recursive] Erreur 1 Which leaves me clueless. Any suggestions? Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From ozan.turkyilmaz at gmail.com Sun Jun 30 09:57:23 2013 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sun, 30 Jun 2013 14:57:23 +0500 Subject: [Slackbuilds-users] Can't build libgda on Slackware64 14.0 In-Reply-To: <51CFFCE8.1080807@microlinux.fr> References: <51CFFCE8.1080807@microlinux.fr> Message-ID: 2013/6/30 Niki Kovacs > Hi, > > I just tried to build libgda (dependency for gtkpod). Built fine on 32-bit > Slackware, but on 64-bit, I get the following build error: > > > Which leaves me clueless. > > Any suggestions? > > try running the script like this: LDFLAGS="-L/usr/lib64" sh libgda.SlackBuild -- Ozan, BSc, BEng -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at microlinux.fr Sun Jun 30 14:51:07 2013 From: info at microlinux.fr (Niki Kovacs) Date: Sun, 30 Jun 2013 16:51:07 +0200 Subject: [Slackbuilds-users] Can't build libgda on Slackware64 14.0 In-Reply-To: References: <51CFFCE8.1080807@microlinux.fr> Message-ID: <51D045DB.4090107@microlinux.fr> Le 30/06/2013 11:57, Ozan T?rky?lmaz a ?crit : > try running the script like this: > > > LDFLAGS="-L/usr/lib64" sh libgda.SlackBuild > Worked like a charm. Thank you very much. http://www.microlinux.fr/slackware/MLED-14.0-64bit/ChangeLog.txt :o) Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From andrew.maraev60 at yandex.ru Sun Jun 30 16:41:18 2013 From: andrew.maraev60 at yandex.ru (Andrey Maraev) Date: Sun, 30 Jun 2013 20:41:18 +0400 Subject: [Slackbuilds-users] [Slackbuilds-devel] New SBo Upload: worker In-Reply-To: <51D04B33.5040404@slackbuilds.org> References: <20130627001641.52CB868401D@dexter.onyxlight.net> <51D04B33.5040404@slackbuilds.org> Message-ID: <20130630204118.6f9e8bad@ed.ed.19> ? Sun, 30 Jun 2013 12:13:55 -0300 Niels Horn ?????: > Hi, > > Sorry, but I'm going to reject this, as the update is not based on > the version currently in our repo. > This makes it difficult, if not impossible, to see what really > changed with the new version. > And it causes extra work for the admins to reapply changes we made > earlier... > > Please resubmit using the files we currently have as a base. > > Thanks, > Sorry, upload Change: - version - delete unneeded option --enable-xft \ From mdhalstead at att.net Sun Jun 30 19:09:06 2013 From: mdhalstead at att.net (Mark Halstead) Date: Sun, 30 Jun 2013 15:09:06 -0400 Subject: [Slackbuilds-users] Inkscape Build Broken on Current Message-ID: <51D08252.5060700@att.net> Hi Folks, Recent updates have broken the build for inkscape-0.48.4. The compiler complains of a stray comma on line 242 and terminates. I built the package successfully after removing the comma from the source code. This has been fixed upstream in the source head at inkscape so a patch might be in order for the present. Here is the pertinent data: inkscape-0.48.4/src/widgets/desktop-widget.h private: GtkWidget *tool_toolbox; GtkWidget *aux_toolbox; --- GtkWidget *commands_toolbox,; ### Line 242, stray comma +++GtkWidget *commands_toolbox; GtkWidget *snap_toolbox; Thanks, Mark Halstead From rworkman at slackbuilds.org Sun Jun 30 20:34:03 2013 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 30 Jun 2013 15:34:03 -0500 Subject: [Slackbuilds-users] Inkscape Build Broken on Current In-Reply-To: <51D08252.5060700@att.net> References: <51D08252.5060700@att.net> Message-ID: <20130630153403.453772ca@home.rlworkman.net> On Sun, 30 Jun 2013 15:09:06 -0400 Mark Halstead wrote: > Hi Folks, > > Recent updates have broken the build for inkscape-0.48.4. The > compiler complains of a stray comma on line 242 and terminates. I > built the package successfully after removing the comma from the > source code. This has been fixed upstream in the source head at > inkscape so a patch might be in order for the present. Here is the > pertinent data: > > inkscape-0.48.4/src/widgets/desktop-widget.h > > private: > GtkWidget *tool_toolbox; > GtkWidget *aux_toolbox; > --- GtkWidget *commands_toolbox,; ### Line 242, stray comma > +++GtkWidget *commands_toolbox; > GtkWidget *snap_toolbox; > > Thanks, > > Mark Halstead Thanks, Mark - it's queued for 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: