From rworkman at slackbuilds.org Tue Mar 1 16:16:14 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 1 Mar 2011 16:16:14 +0000 Subject: [Slackbuilds-users] Updates - 20110301.1 Message-ID: <20110301161614.GA24827@slackbuilds.org> Tue Mar 1 16:01:28 UTC 2011 audio/shntool: Miscellaneous script tweaks audio/shorten: Miscellaneous cleanups desktop/Vanilla-DMZ: Miscellaneous cleanups desktop/root-tail: Miscellaneous cleanups development/Xdialog: Miscellaneous cleanups development/gtkdialog: Miscellaneous cleanups graphics/mtpaint: Miscellaneous cleanups and a bugfix libraries/perl-Cache-FastMmap: Updated for version 1.36. libraries/perl-Config-IniFiles: Updated for version 2.66. libraries/perl-Crypt-OpenSSL-RSA: Fixed dep info in README. libraries/perl-Statistics-Descriptive: Added (stats functions) libraries/perl-Test-Exception: Updated for version 0.31. misc/dwdiff: Miscellaneous cleanups misc/gcolor2: misc cleanups; drop a mystery patch misc/gxmessage: Miscellaneous cleanups misc/par: Miscellaneous cleanups misc/rlwrap: misc cleanups and a bugfix network/openrdate: Miscellaneous cleanups network/perl-MIME-tools: Updated for version 5.500. network/perl-Mail-DKIM: Updated for version 0.39. network/perl-NetAddr-IP: Updated for version 4.038. system/dtach: Miscellaneous cleanups system/heirloom-sh: Miscellaneous cleanups system/parallel: Updated for version 20110205. system/rox-filer: Miscellaneous cleanups From pc_warner at yahoo.com Wed Mar 2 02:37:03 2011 From: pc_warner at yahoo.com (Phillip Warner) Date: Tue, 1 Mar 2011 18:37:03 -0800 (PST) Subject: [Slackbuilds-users] flashplayer-plugin: old link in .info file In-Reply-To: <20110301161614.GA24827@slackbuilds.org> Message-ID: <622010.27972.qm@web161713.mail.bf1.yahoo.com> It appears that the flashplayer-plugin .info file still points to version 10_2 while the slackbuild is for 10_3 --phillip From artourter at gmail.com Wed Mar 2 02:50:36 2011 From: artourter at gmail.com (Greg' Ar Tourter) Date: Wed, 2 Mar 2011 02:50:36 +0000 Subject: [Slackbuilds-users] flashplayer-plugin: old link in .info file In-Reply-To: <622010.27972.qm@web161713.mail.bf1.yahoo.com> References: <20110301161614.GA24827@slackbuilds.org> <622010.27972.qm@web161713.mail.bf1.yahoo.com> Message-ID: Hi, There are no 10.3 version for the 32bit version of the flash plugin, only the 64bit. While the SBo format allows to have different sources for 32bit and 64bit, there is currently no way to encode the fact that the version numbers are different on each platform. If you read the slackbuild in more details, you will see that it gets the version number of the plugin directly from the binary eventually. Hope this clarifies things a bit. ArTourter On 2 March 2011 02:37, Phillip Warner wrote: > It appears that the flashplayer-plugin .info file still points to version 10_2 while the slackbuild is for 10_3 > > --phillip From rworkman at slackbuilds.org Fri Mar 4 16:33:43 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 4 Mar 2011 16:33:43 +0000 Subject: [Slackbuilds-users] Updates - 20110304.1 Message-ID: <20110304163343.GA435@slackbuilds.org> Fri Mar 4 16:13:41 UTC 2011 academic/maxima: Updated for version 5.23.2. academic/tuxtype2: Updated for version 1.8.0 (+new maintainer). audio/TiMidity++: Misc tweaks including +jack +speex -arts audio/kradio: Added (KDE AM/FM/Internet radio) audio/mpd: Updated for version 0.16.1. desktop/QtCurve-Gtk2: Updated for version 1.8.6. desktop/QtCurve-KDE4: Updated for version 1.8.5. development/bzr: Updated for version 2.3.0 development/erlang-otp: Updated for version 14B01. development/gob2: Updated for version 2.0.18. development/haskell-test-framework-hunit: Added (hunit test support) development/haskell-test-framework-quickcheck2: Added (quickcheck2 test framework) development/haskell-test-framework: Added (Haskell test framework) development/pasdoc: Updated for version 0.12.1. development/pep8: Updated for version 0.6.1. development/pforth: Added (portable forth) development/pip: Updated for version 0.8.2. games/scid: Updated for version 4.2.2 (+ new maintainer). libraries/fltk2: Updated for version 2.0.x_r8365. libraries/haskell-GLURaw: Added (raw binding for opengl GLU) libraries/haskell-GLUT: Added (OpenGL GLUT binding for Haskell) libraries/haskell-ObjectName: Added (explicitly handled object names) libraries/haskell-OpenGL: Added (binding for opengl graphics system) libraries/haskell-OpenGLRaw: Added (raw binding for opengl) libraries/haskell-StateVar: Added (Haskell state variables) libraries/haskell-Tensor: Added (tensor data types) libraries/haskell-ansi-terminal: Added (ansi terminal support) libraries/haskell-ansi-wl-pprint: Added (the wadler/leijen pretty printer) libraries/haskell-dataenc: Added (data encoding library) libraries/haskell-hashed-storage: Added (hashed file storage support) libraries/haskell-hostname: Added (gethostname function for haskell) libraries/haskell-lcs: Added (find common sublist of two lists) libraries/haskell-mmap: Added (Memory mapper for POSIX and Windows) libraries/haskell-tar: Added (Haskell's tar library) libraries/haskell-text: Added (Unicode text manipulation library) libraries/libAfterImage: Updated for version 1.20. libraries/libgee: Updated for version 0.6.1. libraries/libnetfilter_conntrack: Updated for version 0.9.1. libraries/libxml++: Updated for version 2.33.2. libraries/zziplib: Updated for version 0.13.60. misc/ibus-chewing: Updated for version 1.3.9.2. misc/merkaartor: Updated for version 0.17.2. multimedia/bombono-dvd: Updated for version 1.0.1. multimedia/ripit: Added (command line audio CD ripper) network/awstats: Updated for version 7.0. network/choqok: Updated for version 1.0. network/conntrack-tools: Updated for version 1.0.0. network/dnstop: Updated for version 20110127. network/hiawatha: Updated for version 7.4. network/kismet: Updated for version 2011_01_R1. network/midori: Updated for version 0.3.0. network/newsbeuter: Updated for version 2.4. network/node: Updated for version 0.2.6. network/phpmyadmin: Updated for version 3.3.9.2. network/uwsgi: Updated for version 0.9.6.7. network/vnstat: Fixed code in rc.vnstat office/adobe-reader: Updated for version 9.4.2. office/elyxer: Updated for version 1.2.0. office/kmymoney: Updated for version 4.5.2. office/libreoffice-langpack: Updated for version 3.3.1. office/libreoffice: Updated for version 3.3.1. office/tellico: Miscellaneous cleanup system/amanda: Updated for version 3.2.1. system/atop: Updated for version 1.26. system/cdw: Added (ncurses front-end for media burning tools) system/fsarchiver: Updated for version 0.6.12. system/gdisk: Don't override C(XX)FLAGS during build system/lrzip: Updated for version 0.570. system/pbzip2: Updated for version 1.1.2. system/python-ranger: Updated for version 1.4.1. system/ttf-ubuntu-font-family: Updated for version 0.70.1. From pc_warner at yahoo.com Sat Mar 5 02:20:24 2011 From: pc_warner at yahoo.com (Phillip Warner) Date: Fri, 4 Mar 2011 18:20:24 -0800 (PST) Subject: [Slackbuilds-users] flashplayer-plugin: old link in .info file In-Reply-To: Message-ID: <67138.31492.qm@web161709.mail.bf1.yahoo.com> --- On Tue, 3/1/11, Greg' Ar Tourter wrote: > There are no 10.3 version for the 32bit version of the > flash plugin, > only the 64bit. > > While the SBo format allows to have different sources for > 32bit and > 64bit, there is currently no way to encode the fact that > the version > numbers are different on each platform. I did not know the versions for 64 and 32 bit were different. Mystery solved! > Hope this clarifies things a bit. It does, thanks! --phillip From rworkman at slackbuilds.org Sat Mar 5 02:40:45 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 4 Mar 2011 20:40:45 -0600 Subject: [Slackbuilds-users] wmii + two dependencies In-Reply-To: References: Message-ID: <20110304204045.735e8f3e@liberty.rlwhome.lan> On Thu, 24 Feb 2011 18:24:31 +0000 (UTC) Glenn Becker wrote: > I tried to build wmii using the SlackBuild and found that the link > for the source code was outdated. > > Short story shorter, I contacted the gentleman listed as maintainer > and he told me he is, in fact, no longer maintaining the package -- > nor the two dependencies he formerly maintained, libixp and plan9port. > > I am happy to make updates to these if no one else has claimed them. Sure, have at them, but be aware that the submission form is currently closed, so it might be a while before you can submit updates for them. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From burningc at SDF.LONESTAR.ORG Sat Mar 5 15:32:00 2011 From: burningc at SDF.LONESTAR.ORG (Glenn Becker) Date: Sat, 5 Mar 2011 15:32:00 +0000 (UTC) Subject: [Slackbuilds-users] wmii + two dependencies In-Reply-To: <20110304204045.735e8f3e@liberty.rlwhome.lan> References: <20110304204045.735e8f3e@liberty.rlwhome.lan> Message-ID: >> I tried to build wmii using the SlackBuild and found that the link >> for the source code was outdated. >> >> Short story shorter, I contacted the gentleman listed as maintainer >> and he told me he is, in fact, no longer maintaining the package -- >> nor the two dependencies he formerly maintained, libixp and plan9port. >> >> I am happy to make updates to these if no one else has claimed them. > > > Sure, have at them, but be aware that the submission form is > currently closed, so it might be a while before you can submit > updates for them. Actually, another person wrote me to say that he had already started or completed a wmii SlackBuild (the dependencies are apparently no longer needed) ... I told him to go ahead with it since I hadn't even had a chance to get started ... I suggested he send a msg to the list. Thanks, /gb +-----------------------------------------------------+ Glenn Becker - burningc at sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org +-----------------------------------------------------+ From nishant at mnspace.net Sun Mar 6 07:20:02 2011 From: nishant at mnspace.net (Nishant Limbachia) Date: Sun, 06 Mar 2011 01:20:02 -0600 Subject: [Slackbuilds-users] offlineimap new tarball Message-ID: <4D7335A2.9080207@mnspace.net> Hi Admins, I just removed my previous offlineimap submission from pending since I have a newer version to submit but it seems new submissions are closed for now. Just asking a rhetorical question. Should I wait for submissions to open? From pprkut at liwjatan.at Sun Mar 6 12:33:39 2011 From: pprkut at liwjatan.at (Heinz Wiesinger) Date: Sun, 6 Mar 2011 13:33:39 +0100 Subject: [Slackbuilds-users] nvidia SlackBuilds EOL Message-ID: <201103061333.48083.pprkut@liwjatan.at> Hey guys, I'd like to announce that I will no longer maintain the nvidia set of SlackBuilds with the next Slackware release. I've switched to nouveau completely and it fulfills all my needs. If someone else wants to take over those scripts, feel free to do so. I gladly offer advise on their maintenance as well. The scripts affected by this: system/nvidia-driver system/nvidia-kernel system/nvidia-legacy96-driver system/nvidia-legacy96-kernel system/nvidia-legacy173-driver system/nvidia-legacy173-kernel libraries/libvdpau misc/vdpauinfo Grs, Heinz -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From binhnguyen at fastmail.fm Sun Mar 6 13:54:30 2011 From: binhnguyen at fastmail.fm (Binh Nguyen) Date: Sun, 6 Mar 2011 20:54:30 +0700 Subject: [Slackbuilds-users] offlineimap new tarball In-Reply-To: <4D7335A2.9080207@mnspace.net> References: <4D7335A2.9080207@mnspace.net> Message-ID: <20110306205430.7d7a6654@darkstar.example.net> On Sun, 06 Mar 2011 01:20:02 -0600 Nishant Limbachia wrote: > Hi Admins, > > I just removed my previous offlineimap submission from pending since > I have a newer version to submit but it seems new submissions are > closed for now. > > Just asking a rhetorical question. Should I wait for submissions to > open? > I remember that an admin said in a email before that if the SlackBuild update is for critical security fix, you can send an attachment to this list. Otherwise, wait for the re-open because all admins are very busy at this time. -- Binh Nguyen From kingbeowulf at gmail.com Mon Mar 7 18:12:06 2011 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 7 Mar 2011 10:12:06 -0800 Subject: [Slackbuilds-users] nvidia SlackBuilds EOL In-Reply-To: <201103061333.48083.pprkut@liwjatan.at> References: <201103061333.48083.pprkut@liwjatan.at> Message-ID: I'll take them on. I need to volunteer more time to Slackware anyway. Also I and no doubt others would prefer nvidia for certain gaming performance. So sign me up! -Ed On 3/6/11, Heinz Wiesinger wrote: > Hey guys, > > I'd like to announce that I will no longer maintain the nvidia set of > SlackBuilds with the next Slackware release. I've switched to nouveau > completely and it fulfills all my needs. > > If someone else wants to take over those scripts, feel free to do so. I > gladly > offer advise on their maintenance as well. > > The scripts affected by this: > system/nvidia-driver > system/nvidia-kernel > system/nvidia-legacy96-driver > system/nvidia-legacy96-kernel > system/nvidia-legacy173-driver > system/nvidia-legacy173-kernel > libraries/libvdpau > misc/vdpauinfo > > Grs, > Heinz > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From pprkut at liwjatan.at Mon Mar 7 22:20:04 2011 From: pprkut at liwjatan.at (Heinz Wiesinger) Date: Mon, 7 Mar 2011 23:20:04 +0100 Subject: [Slackbuilds-users] nvidia SlackBuilds EOL In-Reply-To: References: <201103061333.48083.pprkut@liwjatan.at> Message-ID: <201103072320.08838.pprkut@liwjatan.at> On Monday 07 March 2011 19:12:06 King Beowulf wrote: > On 3/6/11, Heinz Wiesinger wrote: > > Hey guys, > > > > I'd like to announce that I will no longer maintain the nvidia set of > > SlackBuilds with the next Slackware release. I've switched to nouveau > > completely and it fulfills all my needs. > > > > If someone else wants to take over those scripts, feel free to do so. I > > gladly > > offer advise on their maintenance as well. > > > > The scripts affected by this: > > system/nvidia-driver > > system/nvidia-kernel > > system/nvidia-legacy96-driver > > system/nvidia-legacy96-kernel > > system/nvidia-legacy173-driver > > system/nvidia-legacy173-kernel > > libraries/libvdpau > > misc/vdpauinfo > > I'll take them on. I need to volunteer more time to Slackware anyway. > Also I and no doubt others would prefer nvidia for certain gaming > performance. > > So sign me up! Great! Could you please send tarballs with updated maintainer information to either me or slackbuilds-devel? I'll take care of it as soon as possible, as long as an other admin doesn't beat me to it :) Grs, Heinz -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From kd5zex at gmail.com Tue Mar 8 00:48:13 2011 From: kd5zex at gmail.com (Alan) Date: Mon, 7 Mar 2011 18:48:13 -0600 Subject: [Slackbuilds-users] nvidia SlackBuilds EOL In-Reply-To: References: <201103061333.48083.pprkut@liwjatan.at> Message-ID: On Mon, Mar 7, 2011 at 12:12, King Beowulf wrote: > I'll take them on. I need to volunteer more time to Slackware anyway. > Also I and no doubt others would prefer nvidia for certain gaming > performance. > > So sign me up! > > Thanks for picking these up and thanks to Heinz for the past maintenance! Cheers, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Tue Mar 8 01:54:38 2011 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 7 Mar 2011 17:54:38 -0800 Subject: [Slackbuilds-users] nvidia SlackBuilds EOL In-Reply-To: <201103072320.08838.pprkut@liwjatan.at> References: <201103061333.48083.pprkut@liwjatan.at> <201103072320.08838.pprkut@liwjatan.at> Message-ID: As soon as I get back to the homestead I'll whip the maintainer tarballs over to you. Traveling for work with a *gasp* WinXP laptop, so it'll be a few days since I forgot to open a port for ssh on my router before I left. Silly me. Ed On 3/7/11, Heinz Wiesinger wrote: > On Monday 07 March 2011 19:12:06 King Beowulf wrote: >> On 3/6/11, Heinz Wiesinger wrote: >> > Hey guys, >> > >> > I'd like to announce that I will no longer maintain the nvidia set of >> > SlackBuilds with the next Slackware release. I've switched to nouveau >> > completely and it fulfills all my needs. >> > >> > If someone else wants to take over those scripts, feel free to do so. I >> > gladly >> > offer advise on their maintenance as well. >> > >> > The scripts affected by this: >> > system/nvidia-driver >> > system/nvidia-kernel >> > system/nvidia-legacy96-driver >> > system/nvidia-legacy96-kernel >> > system/nvidia-legacy173-driver >> > system/nvidia-legacy173-kernel >> > libraries/libvdpau >> > misc/vdpauinfo >> >> I'll take them on. I need to volunteer more time to Slackware anyway. >> Also I and no doubt others would prefer nvidia for certain gaming >> performance. >> >> So sign me up! > > Great! > > Could you please send tarballs with updated maintainer information to either > me or slackbuilds-devel? > I'll take care of it as soon as possible, as long as an other admin doesn't > beat me to it :) > > Grs, > Heinz > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From crockabiscuit at yahoo.com Tue Mar 8 14:54:51 2011 From: crockabiscuit at yahoo.com (crocket) Date: Tue, 8 Mar 2011 06:54:51 -0800 (PST) Subject: [Slackbuilds-users] There is a problem with installing tor via sbopkg. Message-ID: <591830.33182.qm@web120318.mail.ne1.yahoo.com> I typed "sbopkg -i tor". Although tor.info stored on my computer contained DOWNLOAD="https://www.torproject.org/dist/tor-0.2.1.29.tar.gz", sbopkg tried to download https://www.torproject.org/dist/tor-0.2.1.28.tar.gz which didn't exist. It happened on my slackware64 13.1 server. My slackware64-current desktop didn't encounter this problem. Can anybody guess what the problem might be? From pwcazenave at gmail.com Tue Mar 8 15:03:59 2011 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Tue, 08 Mar 2011 15:03:59 +0000 Subject: [Slackbuilds-users] There is a problem with installing tor via sbopkg. In-Reply-To: <591830.33182.qm@web120318.mail.ne1.yahoo.com> References: <591830.33182.qm@web120318.mail.ne1.yahoo.com> Message-ID: <4D76455F.8080103@gmail.com> On 08/03/2011 14:54, crocket wrote: > I typed "sbopkg -i tor". > Although tor.info stored on my computer contained > DOWNLOAD="https://www.torproject.org/dist/tor-0.2.1.29.tar.gz", > sbopkg tried to download https://www.torproject.org/dist/tor-0.2.1.28.tar.gz > which didn't exist. > > It happened on my slackware64 13.1 server. > My slackware64-current desktop didn't encounter this problem. > > Can anybody guess what the problem might be? > > > > _______________________________________________ > 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/ > Do you have a custom .info file with a different $DOWNLOAD value? Check in $REPO_ROOT/$REPO_NAME/$REPO_BRANCH/network/tor for a tor.info.sbopkg file. Pierre From sid77 at slackware.it Tue Mar 8 15:23:38 2011 From: sid77 at slackware.it (Marco Bonetti) Date: Tue, 08 Mar 2011 16:23:38 +0100 Subject: [Slackbuilds-users] There is a problem with installing tor via sbopkg. In-Reply-To: <4D76455F.8080103@gmail.com> References: <591830.33182.qm@web120318.mail.ne1.yahoo.com> <4D76455F.8080103@gmail.com> Message-ID: <4D7649FA.4080804@slackware.it> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/08/2011 04:03 PM, Pierre Cazenave wrote: > Do you have a custom .info file with a different $DOWNLOAD value? Check > in $REPO_ROOT/$REPO_NAME/$REPO_BRANCH/network/tor for a tor.info.sbopkg > file. +1 By the way, if anyone needs 0.2.1.30 before submissions will reopen, the SlackBuild is up on my repo: https://github.com/sid77/SBo/tree/master/tor Minor improvements, there is just a major fix which prevents a DOS against Directory Authorities but I don't think any of the nine of them is using this SlackBuilds anyway so it does not really qualify as an important security fix :-P (at least w.r.t. www.slackbuilds.org) ciao - -- Marco Bonetti Tor research and other stuff: http://sid77.slackware.it/ Slackintosh Linux Project Developer: http://workaround.ch/ Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/ My GnuPG key id: 0x0B60BC5F -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk12SfoACgkQTYvJ9gtgvF/yTgCfU1e1D0Z3WBZirB/ryiAF7hge q+wAoJ3/7cWUkvMKiOIGy6/g+bn07k0h =oyr4 -----END PGP SIGNATURE----- From ml at mareichelt.com Tue Mar 8 19:39:00 2011 From: ml at mareichelt.com (markus reichelt) Date: Tue, 8 Mar 2011 20:39:00 +0100 Subject: [Slackbuilds-users] There is a problem with installing tor via sbopkg. In-Reply-To: <4D7649FA.4080804@slackware.it> References: <591830.33182.qm@web120318.mail.ne1.yahoo.com> <4D76455F.8080103@gmail.com> <4D7649FA.4080804@slackware.it> Message-ID: <20110308193900.GB19480@pc21.mareichelt.com> * Marco Bonetti wrote: > By the way, if anyone needs 0.2.1.30 before submissions will reopen Thanks for the heads up, I can use that :-) The frontpage of torproject still states 0.2.1.29 as most recent version. Somehow the "Announcement" part is updated only once in a while. -- left blank, right bald -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From kingbeowulf at gmail.com Tue Mar 8 22:08:44 2011 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 8 Mar 2011 14:08:44 -0800 Subject: [Slackbuilds-users] nvidia SlackBuilds EOL In-Reply-To: References: <201103061333.48083.pprkut@liwjatan.at> Message-ID: On Mon, Mar 7, 2011 at 4:48 PM, Alan wrote: > > > On Mon, Mar 7, 2011 at 12:12, King Beowulf wrote: > >> I'll take them on. I need to volunteer more time to Slackware anyway. >> Also I and no doubt others would prefer nvidia for certain gaming >> performance. >> >> So sign me up! >> >> > Thanks for picking these up and thanks to Heinz for the past maintenance! > > Cheers, > > Alan > > > _______________________________________________ > 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/ > > > No problem. Since I use these, I might as well stop sponging off the work of others! Ed -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From crockabiscuit at yahoo.com Wed Mar 9 00:29:59 2011 From: crockabiscuit at yahoo.com (crocket) Date: Tue, 8 Mar 2011 16:29:59 -0800 (PST) Subject: [Slackbuilds-users] There is a problem with installing tor via sbopkg. In-Reply-To: <591830.33182.qm@web120318.mail.ne1.yahoo.com> References: <591830.33182.qm@web120318.mail.ne1.yahoo.com> Message-ID: <312099.5052.qm@web120305.mail.ne1.yahoo.com> I tried again, and this time it worked. I think I executed "sbopkg -r" before "sbopkg -i tor". Maybe I executed "sbopkg -i tor" before "sbopkg -r". ----- Original Message ---- From: crocket To: slackbuilds-users at slackbuilds.org Sent: Tue, March 8, 2011 11:54:51 PM Subject: [Slackbuilds-users] There is a problem with installing tor via sbopkg. I typed "sbopkg -i tor". Although tor.info stored on my computer contained DOWNLOAD="https://www.torproject.org/dist/tor-0.2.1.29.tar.gz", sbopkg tried to download https://www.torproject.org/dist/tor-0.2.1.28.tar.gz which didn't exist. It happened on my slackware64 13.1 server. My slackware64-current desktop didn't encounter this problem. Can anybody guess what the problem might be? _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ From ozan.turkyilmaz at gmail.com Wed Mar 9 14:54:59 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Wed, 9 Mar 2011 16:54:59 +0200 Subject: [Slackbuilds-users] Static and Shared Libs togetter Message-ID: Hey all, As submissions are closed, I take my time with libembl libmarkosya and mkvtoolnix. And now my question; I am thinking of making the libs with both shared and static libs. And thoughts or comments. -- Ozan, BSc, BEng From rworkman at slackbuilds.org Wed Mar 9 17:06:46 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 9 Mar 2011 17:06:46 +0000 Subject: [Slackbuilds-users] Updates - 20110308.1 Message-ID: <20110309170646.GA29180@slackbuilds.org> Tue Mar 8 18:15:47 UTC 2011 academic/artha: Added (cross-platform thesaurus) audio/alsaequal: Fixed build/use on x86_64 audio/audacity: Patched for portaudio + new ffmpeg switch. audio/cmus: Updated for version 2.3.4. desktop/cairo-dock-plugins: Added. A set of plugins for cairo-dock. desktop/cairo-dock: Added. a light and eye-candy dock. desktop/smaragd: Added (a window decoration engine for KDE) desktop/xfce4-diskperf-plugin: Updated for version 2.3.0. desktop/xfce4-weather-plugin: Updated for version 0.7.4. development/darcs: Added (revision control system in Haskell) development/sbcl: Added (Steel Bank Common Lisp) development/shc: Added (generic SHell script Compiler) games/Domination: Added (World domination strategy game) games/ckmame: Updated for version 0.11. games/fceux: Moved to /usr/games + changed icon. games/pcsxr: Included cdrom and alsa support games/xmoto: Updated for version 0.5.5. graphics/frescobaldi: Added (LilyPond sheet music editor) graphics/lcdtest: Added (utility to display LCD monitor test patterns) graphics/pinta: Updated for version 0.6. libraries/BeautifulSoup: Updated for version 3.2.0. libraries/SFML: Added (Simple and Fast Multimedia Library) libraries/libcitadel: Added. Common Citadel libraries. libraries/libicns: Added (MacOS X .icns icon format library) libraries/libmemcached: Updated for version 0.46. libraries/libsieve: Added (interpreter for Sieve scripts) libraries/menu-cache: Changed listed maintainer libraries/openbabel: Updated for version 2.3.0. libraries/perl-Digest-MD4: Digest::MD4 perl module libraries/python-bigfloat: Added (floating point arithmetic library) libraries/python-cmdln: Added (enhanced cmdln module for python) libraries/python-mpd: Updated for version 0.3.0. libraries/python-openid: Added (python openid library) libraries/tDOM: Added (XML parsing and generation for TCL) libraries/zeromq: Added (lightweight messaging kernel library) misc/ardesia: Added (Pen/Touch ready on-screen annotation) misc/cups-windows: Added (CUPS PostScript driver for Windows) misc/curtain: Added (Display a curtain on the desktop) misc/figlet: Updated download info + misc. cleanups misc/ibus: Updated for versin 1.3.9. misc/mosquitto: Added (MQTT server) misc/spotlighter: Added (show a spot light on the desktop) misc/temper: Added. A USB Temperature Sensor Linux Driver. multimedia/media-player-info: Updated for version 12. multimedia/miro: Updated for version 3.5.1. network/arm: Added (monitor for Tor relays) network/chromium: Updated for version 9.0.597.107. network/citadel: Added (e-mail and collaboration suite) network/cowpatty: Added. WPA-PSK dictionary attack tool. network/freenx: Misc. cleaning up. network/fwknop: Added (Single Packet Authorization / Port Knocking) network/gq: Added (gtk+ ldap client and browser utility) network/hamachi: Added (LogMeIn VPN client) network/mldonkey: Updated for version 3.0.7. network/mobile-broadband-provider-info: Updated for version 20110218 network/nikto: Updated for version 2.1.4. network/nx: Updated with latest tarballs network/nxclient: Moved install location to /opt network/openvpn-auth-ldap: (LDAP authentication and authorization) network/openvswitch: Added (multilayer virtual switch) network/pidgin-privacy-please: Added (privacy plugin for pidgin) network/qbittorrent: Updated for version 2.6.6. network/rssh: Added (restricted ssh) network/rubygem-sup: Updated for version 0.12.1. network/teamviewer: Fixed binary name so menu entries keep working network/zabbix_agentd: Updated for version 1.8.4. network/zabbix_proxy: Updated for version 1.8.4. network/zabbix_server: Updated for version 1.8.4. office/aigaion: New maintainer office/calibre: Updated for version 0.7.45. office/gocr: Updated for version 0.49. office/kchmviewer: Updated for version 5.3. system/aespipe: Updated for version 2.4c. system/fpm2: Updated for version 0.79. system/grub4dos: Updated for version 0.4.5b_2011_02_20. system/macutils: Added (tools to handle Macintosh files) system/mongodb: Added (Database Software) system/rmw: Updated for version 0.98.3.9beta. From rworkman at slackbuilds.org Wed Mar 9 17:08:27 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 9 Mar 2011 11:08:27 -0600 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo Message-ID: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Okay, everybody saw the 13.37 rc1 announcement, I guess, so now you know why we closed pending a few days ago :-) We're doing some early work on getting ready for 13.37, and we'll be soliciting feedback for that soon, but at the moment, I personally would like to know if there are any pressing issues that need to be handled in our 13.1 repo. I'm not making any promises to do anything, but if you have some important things that need to be addressed there, now is the time to let me know (and make it as easy as possible to do - i.e. provide a tarball, git pull request, etcetera). I've already got the update to tor, so don't mention that one. My goal is to finalize 13.1 so that we can all focus on getting everything in place for 13.37. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From ozan.turkyilmaz at gmail.com Wed Mar 9 17:29:07 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Wed, 9 Mar 2011 19:29:07 +0200 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110309110827.73e0e9e1@liberty.rlwhome.lan> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: 2011/3/9 Robby Workman : > Okay, everybody saw the 13.37 rc1 announcement, I guess, so now you > know why we closed pending a few days ago :-) ?We're doing some early > work on getting ready for 13.37, and we'll be soliciting feedback for > that soon, but at the moment, I personally would like to know if there > are any pressing issues that need to be handled in our 13.1 repo. > I'm not making any promises to do anything, but if you have some > important things that need to be addressed there, now is the time to > let me know (and make it as easy as possible to do - i.e. provide a > tarball, git pull request, etcetera). ?I've already got the update > to tor, so don't mention that one. ?My goal is to finalize 13.1 so > that we can all focus on getting everything in place for 13.37. > I'm cooking some for mkv. Others have small fixes and I'll go over them and send it a patch. -- Ozan, BSc, BEng From banderols at gmail.com Wed Mar 9 17:44:44 2011 From: banderols at gmail.com (Murat D. Kadirov) Date: Wed, 9 Mar 2011 22:44:44 +0500 Subject: [Slackbuilds-users] Static and Shared Libs togetter In-Reply-To: References: Message-ID: <20110309174444.GA4456@gera> On Wed, Mar 09, 2011 at 04:54:59PM +0200, Ozan T?rky?lmaz wrote: > Hey all, > > As submissions are closed, I take my time with libembl libmarkosya and > mkvtoolnix. And now my question; > I am thinking of making the libs with both shared and static libs. And > thoughts or comments. What is the reason? -- Murat D. Kadirov PGP fingerprint: 3081 EBFA 5CB9 BD24 4DB6 76EE 1B97 0A0E CEC0 6AA0 From nickblizzard1776 at gmail.com Wed Mar 9 17:55:12 2011 From: nickblizzard1776 at gmail.com (Nick Blizzard) Date: Wed, 09 Mar 2011 12:55:12 -0500 Subject: [Slackbuilds-users] broadcom-sta Message-ID: <4D77BF00.1030904@gmail.com> If you are doing pre-release testing, this page has a one line code change to get broadcom-sta working again. http://task3.cc/1934/configure-slackware-13-1-for-macbook-pro-62/ From rworkman at slackbuilds.org Wed Mar 9 18:13:24 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 9 Mar 2011 12:13:24 -0600 Subject: [Slackbuilds-users] Static and Shared Libs togetter In-Reply-To: <20110309174444.GA4456@gera> References: <20110309174444.GA4456@gera> Message-ID: <20110309121324.6b69fa85@liberty.rlwhome.lan> On Wed, 9 Mar 2011 22:44:44 +0500 "Murat D. Kadirov" wrote: > On Wed, Mar 09, 2011 at 04:54:59PM +0200, Ozan T?rky?lmaz wrote: > > Hey all, > > > > As submissions are closed, I take my time with libembl libmarkosya > > and mkvtoolnix. And now my question; > > I am thinking of making the libs with both shared and static libs. > > And thoughts or comments. > > What is the reason? Yeah, what he said... :-) Honestly though, it doesn't really matter for us - we're not distributing packages anyway, so space doesn't much matter. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rshepard at appl-ecosys.com Wed Mar 9 18:12:57 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 9 Mar 2011 10:12:57 -0800 (PST) Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110309110827.73e0e9e1@liberty.rlwhome.lan> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: On Wed, 9 Mar 2011, Robby Workman wrote: > Okay, everybody saw the 13.37 rc1 announcement, First I've seen of it. Just curious why the version is 13.37 rather than 13.2. Rich From rworkman at slackbuilds.org Wed Mar 9 18:24:29 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 9 Mar 2011 12:24:29 -0600 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: <20110309122429.3fcc2a30@liberty.rlwhome.lan> On Wed, 9 Mar 2011 10:12:57 -0800 (PST) Rich Shepard wrote: > On Wed, 9 Mar 2011, Robby Workman wrote: > > > Okay, everybody saw the 13.37 rc1 announcement, > > First I've seen of it. > > Just curious why the version is 13.37 rather than 13.2. Why would it be 13.2 rather than 13.37? :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From eric.b.pratt at gmail.com Wed Mar 9 18:24:36 2011 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Wed, 9 Mar 2011 13:24:36 -0500 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: It was in the changelog. If you remove the '.' in 13.37, its like 'elite' in l33t speak. On Wed, Mar 9, 2011 at 1:12 PM, Rich Shepard wrote: > On Wed, 9 Mar 2011, Robby Workman wrote: > >> Okay, everybody saw the 13.37 rc1 announcement, > > ?First I've seen of it. > > ?Just curious why the version is 13.37 rather than 13.2. > > Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From ozan.turkyilmaz at gmail.com Wed Mar 9 18:33:10 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Wed, 9 Mar 2011 20:33:10 +0200 Subject: [Slackbuilds-users] Static and Shared Libs togetter In-Reply-To: <20110309121324.6b69fa85@liberty.rlwhome.lan> References: <20110309174444.GA4456@gera> <20110309121324.6b69fa85@liberty.rlwhome.lan> Message-ID: 2011/3/9 Robby Workman : > > Yeah, what he said... ?:-) > > Honestly though, it doesn't really matter for us - we're not > distributing packages anyway, so space doesn't much matter. > I don't know the user needs for it. I'll make it optimal for user who need it. -- Ozan, BSc, BEng From rworkman at slackbuilds.org Wed Mar 9 18:42:24 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 9 Mar 2011 12:42:24 -0600 Subject: [Slackbuilds-users] broadcom-sta In-Reply-To: <4D77BF00.1030904@gmail.com> References: <4D77BF00.1030904@gmail.com> Message-ID: <20110309124224.53969dcd@liberty.rlwhome.lan> On Wed, 09 Mar 2011 12:55:12 -0500 Nick Blizzard wrote: > If you are doing pre-release testing, this page has a one line code > change to get broadcom-sta working again. > > http://task3.cc/1934/configure-slackware-13-1-for-macbook-pro-62/ Thanks for the tip - it's in my 'rworkman-13.37' git branch now. On that note, I feel obligated to remind everyone that our personal git branches are not carrying a promise of stability or history preservation or anything else - they are subject to rebasing, deletion, force pushes, and anything else, so DO NOT base any changesets on them. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Wed Mar 9 18:46:32 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 9 Mar 2011 12:46:32 -0600 Subject: [Slackbuilds-users] Static and Shared Libs togetter In-Reply-To: References: <20110309174444.GA4456@gera> <20110309121324.6b69fa85@liberty.rlwhome.lan> Message-ID: <20110309124632.3d79031f@liberty.rlwhome.lan> On Wed, 9 Mar 2011 20:33:10 +0200 Ozan T?rky?lmaz wrote: > 2011/3/9 Robby Workman : > > > > Yeah, what he said... ?:-) > > > > Honestly though, it doesn't really matter for us - we're not > > distributing packages anyway, so space doesn't much matter. > > > > I don't know the user needs for it. I'll make it optimal for user who > need it. Is there other software out there that *needs* the static libraries? If so, then sure. If not, then: are there (common,valid) usage scenarios to link any of these statically? I mean, sure, someone somewhere *might* need to do a lot of things, but if the something they're doing to require it is very non-standard, then they should expect to run into other non-standard stuff... ;-) That said, it's okay either way - there's no harm, but there's very little gain in most cases 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 kingbeowulf at gmail.com Wed Mar 9 18:53:01 2011 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 9 Mar 2011 10:53:01 -0800 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110309110827.73e0e9e1@liberty.rlwhome.lan> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: Well, I guess I need to check the changelog more that once or twice a week! Holy l337-speak batman! I will hop on it as soon as I can and check the slackbuilds I maintain ater I update my VMs. I'll send in updated stuff to for the nvidia binary blobs I took over. I forgot "volunteering" also meant "work" ;-) On 3/9/11, Robby Workman wrote: > Okay, everybody saw the 13.37 rc1 announcement, I guess, so now you > know why we closed pending a few days ago :-) We're doing some early > work on getting ready for 13.37, and we'll be soliciting feedback for > that soon, but at the moment, I personally would like to know if there > are any pressing issues that need to be handled in our 13.1 repo. > I'm not making any promises to do anything, but if you have some > important things that need to be addressed there, now is the time to > let me know (and make it as easy as possible to do - i.e. provide a > tarball, git pull request, etcetera). I've already got the update > to tor, so don't mention that one. My goal is to finalize 13.1 so > that we can all focus on getting everything in place for 13.37. > > -RW > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From rshepard at appl-ecosys.com Wed Mar 9 19:19:11 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 9 Mar 2011 11:19:11 -0800 (PST) Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110309122429.3fcc2a30@liberty.rlwhome.lan> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> <20110309122429.3fcc2a30@liberty.rlwhome.lan> Message-ID: On Wed, 9 Mar 2011, Robby Workman wrote: > Why would it be 13.2 rather than 13.37? :-) Because 2 comes before 37 when counting? Because previous minor version numbers have been 1 and 2? If there's no particular reason that's fine with me. At least we don't have silly version names like the ubuntus do. :-) Rich From andrew at andrews-corner.org Wed Mar 9 21:16:19 2011 From: andrew at andrews-corner.org (andrew) Date: Thu, 10 Mar 2011 08:16:19 +1100 Subject: [Slackbuilds-users] Static and Shared Libs togetter In-Reply-To: References: Message-ID: <20110309211619.GA1971@skamandros.andrews-corner.org> On Wed, Mar 09, 2011 at 04:54:59PM +0200, Ozan T?rky?lmaz wrote: > As submissions are closed, I take my time with libembl libmarkosya and > mkvtoolnix. As you have probably already seen the new version of mkvtoolnix does not actually need an external libebml and libmatroska any more. Andrew -- Do you think that's air you're breathing? From matteo.bernardini at gmail.com Wed Mar 9 21:33:07 2011 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 09 Mar 2011 22:33:07 +0100 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110309110827.73e0e9e1@liberty.rlwhome.lan> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: <4D77F213.3050302@gmail.com> Il 09/03/2011 18:08, Robby Workman ha scritto: > if you have some > important things that need to be addressed there, now is the time to > let me know (and make it as easy as possible to do - i.e. provide a > tarball, git pull request, etcetera) I have three thingies that I promised to take over maintaining but I hadn't submitted yet, just changed maintainer data in the .info files http://ompldr.org/vN3Frbw/libfm.tar.gz http://ompldr.org/vN3FrZg/lxpanel.tar.gz http://ompldr.org/vN3Frag/pcmanfm.tar.gz if you prefeer a "git send-email" just let me know :) Matteo P.S. to all: if can be useful, this is the stuff I'm building on RC1, feel free to have a look :D http://cgit.ponce.cc/slackbuilds/refs/heads From ozan.turkyilmaz at gmail.com Wed Mar 9 22:34:22 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Thu, 10 Mar 2011 00:34:22 +0200 Subject: [Slackbuilds-users] Static and Shared Libs togetter In-Reply-To: <20110309211619.GA1971@skamandros.andrews-corner.org> References: <20110309211619.GA1971@skamandros.andrews-corner.org> Message-ID: 2011/3/9 andrew : > On Wed, Mar 09, 2011 at 04:54:59PM +0200, Ozan T?rky?lmaz wrote: > >> As submissions are closed, I take my time with libembl libmarkosya and >> mkvtoolnix. > > As you have probably already seen the new version of mkvtoolnix does > not actually need an external libebml and libmatroska any more. > "mkvtoolnix requires libebml 1.2.0 and libmatroska 1.1.0 for compilation. Both have been released a few days ago. However, starting with this release mkvtoolnix includes the source of libebml and libmatroska. configure will still try to find globally installed copies of libebml and libmatroska like before and use them if they?re recent enough. If they?re not then configure will fall back to using the included versions." -- Ozan, BSc, BEng From chaos.proton at gmail.com Thu Mar 10 01:12:11 2011 From: chaos.proton at gmail.com (Grissiom) Date: Thu, 10 Mar 2011 09:12:11 +0800 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: On Thu, Mar 10, 2011 at 2:24 AM, Eric Pratt wrote: > It was in the changelog. > > If you remove the '.' in 13.37, its like 'elite' in l33t speak. > Not mentioned in slackware64-current ChangeLog.txt tough... I think there is an other reason to be numbered as .37 -- RC1 use 2.6.37 kernel, which is going to be the kernel in next release. -- Cheers, Grissiom > On Wed, Mar 9, 2011 at 1:12 PM, Rich Shepard wrote: >> On Wed, 9 Mar 2011, Robby Workman wrote: >> >>> Okay, everybody saw the 13.37 rc1 announcement, >> >> ?First I've seen of it. >> >> ?Just curious why the version is 13.37 rather than 13.2. >> >> Rich From gwenhael.le.moine at gmail.com Thu Mar 10 03:36:37 2011 From: gwenhael.le.moine at gmail.com (Gwenhael Le Moine) Date: Thu, 10 Mar 2011 10:36:37 +0700 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110309110827.73e0e9e1@liberty.rlwhome.lan> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: 2011/3/10 Robby Workman : > Okay, everybody saw the 13.37 rc1 announcement, I guess, so now you > know why we closed pending a few days ago :-) ?We're doing some early > work on getting ready for 13.37, and we'll be soliciting feedback for > that soon, but at the moment, I personally would like to know if there > are any pressing issues that need to be handled in our 13.1 repo. > I'm not making any promises to do anything, but if you have some > important things that need to be addressed there, now is the time to > let me know (and make it as easy as possible to do - i.e. provide a > tarball, git pull request, etcetera). ?I've already got the update > to tor, so don't mention that one. ?My goal is to finalize 13.1 so > that we can all focus on getting everything in place for 13.37. > > -RW I just have the updated .info for gem2tgz @ https://github.com/cycojesus/slackbuilds/tree/master/SBo/gem2tgz It's not at all tied to a release of Slackware so feel free to ignore it from now and I'll re-submit it when things calm down. From binhnguyen at fastmail.fm Thu Mar 10 04:07:26 2011 From: binhnguyen at fastmail.fm (Binh Nguyen) Date: Thu, 10 Mar 2011 11:07:26 +0700 Subject: [Slackbuilds-users] Updates - 20110308.1 In-Reply-To: <20110309170646.GA29180@slackbuilds.org> References: <20110309170646.GA29180@slackbuilds.org> Message-ID: <20110310110726.14c8d635@fastmail.fm> On Wed, 9 Mar 2011 17:06:46 +0000 Robby Workman wrote: > Tue Mar 8 18:15:47 UTC 2011 > network/teamviewer: Fixed binary name so menu entries keep working > Just a tiny typo: README lacks a '.' in its last line. -- Binh Nguyen From rworkman at slackbuilds.org Thu Mar 10 04:29:25 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 9 Mar 2011 22:29:25 -0600 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: <20110309222925.2128156d@liberty.rlwhome.lan> On Thu, 10 Mar 2011 10:36:37 +0700 Gwenhael Le Moine wrote: > I just have the updated .info for gem2tgz @ > https://github.com/cycojesus/slackbuilds/tree/master/SBo/gem2tgz > It's not at all tied to a release of Slackware so feel free to ignore > it from now and I'll re-submit it when things calm down. I've got this queued for addition to 13.1 since I was working on that branch anyway. Thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Thu Mar 10 04:34:44 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 9 Mar 2011 22:34:44 -0600 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <4D77F213.3050302@gmail.com> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> <4D77F213.3050302@gmail.com> Message-ID: <20110309223444.1b9c3873@liberty.rlwhome.lan> On Wed, 09 Mar 2011 22:33:07 +0100 Matteo Bernardini wrote: > Il 09/03/2011 18:08, Robby Workman ha scritto: > > if you have some > > important things that need to be addressed there, now is the time to > > let me know (and make it as easy as possible to do - i.e. provide a > > tarball, git pull request, etcetera) > > I have three thingies that I promised to take over maintaining but I > hadn't submitted yet, just changed maintainer data in the .info files > > http://ompldr.org/vN3Frbw/libfm.tar.gz > http://ompldr.org/vN3FrZg/lxpanel.tar.gz > http://ompldr.org/vN3Frag/pcmanfm.tar.gz > > if you prefeer a "git send-email" just let me know :) Got them; thanks! -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Thu Mar 10 05:20:51 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 10 Mar 2011 05:20:51 +0000 Subject: [Slackbuilds-users] Updates - 20110310.1 Message-ID: <20110310052050.GA22736@slackbuilds.org> Thu Mar 10 05:12:38 UTC 2011 desktop/lxpanel: Changed maintainer in .info file development/gem2tgz: Added (create Slackware packages from Rubygems) libraries/libfm: Changed maintainer in .info file network/google-chrome: Updated for version 10.0.648.127. network/tor: Updated for version 0.2.1.30. system/pcmanfm: Changed maintainer in .info file From kylebrown at ec.rr.com Thu Mar 10 20:00:28 2011 From: kylebrown at ec.rr.com (Kyle Brown) Date: Thu, 10 Mar 2011 15:00:28 -0500 Subject: [Slackbuilds-users] Idea for slackbuilds.org Message-ID: <4D792DDC.2060301@ec.rr.com> I have an idea that I would like to pass to slackbuilds.org for consideration: I believe it would be emmensely useful to have a short description displayed when browsing each of the slackbuilds.org directories. Currently only "Name", "Version", "Updated On" are displayed in the lists. I believe changing this to "Name",**"Description"**,"Version","Updated On" would be very helpful. Many times I come looking for slackbuild ready software at slackbuilds.org but I always have to go click on each link to see what the software is. It would be nice to be able to just scroll through and read a short discription on what the slackbuild/software does. I would think it should be a simple database call that could provide a much increased ease of use on the website. Just a thought. Thanks, Kyle Brown A Slackware User From erik at slackbuilds.org Thu Mar 10 20:22:14 2011 From: erik at slackbuilds.org (Erik Hanson) Date: Thu, 10 Mar 2011 14:22:14 -0600 Subject: [Slackbuilds-users] Idea for slackbuilds.org In-Reply-To: <4D792DDC.2060301@ec.rr.com> References: <4D792DDC.2060301@ec.rr.com> Message-ID: <20110310142214.0c90e8a8@shaggy.doo> On Thu, 10 Mar 2011 15:00:28 -0500 Kyle Brown wrote: > I believe it would be emmensely useful to have a short description > displayed when browsing each of the slackbuilds.org directories. > > Currently only "Name", "Version", "Updated On" are displayed in the > lists. > > I believe changing this to > "Name",**"Description"**,"Version","Updated On" would be very helpful. I coded this a long time ago, but it was very slow because a short description is not in the db, it had to be pulled from each slack-desc. If we get that data in the db then it should be easy to add. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From ozan.turkyilmaz at gmail.com Thu Mar 10 20:38:07 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Thu, 10 Mar 2011 22:38:07 +0200 Subject: [Slackbuilds-users] Idea for slackbuilds.org In-Reply-To: <20110310142214.0c90e8a8@shaggy.doo> References: <4D792DDC.2060301@ec.rr.com> <20110310142214.0c90e8a8@shaggy.doo> Message-ID: 2011/3/10 Erik Hanson : > On Thu, 10 Mar 2011 15:00:28 -0500 > Kyle Brown wrote: > >> I believe it would be emmensely useful to have a short description >> displayed when browsing each of the slackbuilds.org directories. >> >> Currently only "Name", "Version", "Updated On" are displayed in the >> lists. >> >> I believe changing this to >> "Name",**"Description"**,"Version","Updated On" would be very helpful. > > I coded this a long time ago, but it was very slow because a short > description is not in the db, it had to be pulled from each slack-desc. > If we get that data in the db then it should be easy to add. > How about making it mandatory for .infos. Short-desc would be really useful for browsers of the repo. -- Ozan, BSc, BEng From kingbeowulf at gmail.com Thu Mar 10 21:00:27 2011 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 10 Mar 2011 13:00:27 -0800 Subject: [Slackbuilds-users] Idea for slackbuilds.org In-Reply-To: References: <4D792DDC.2060301@ec.rr.com> <20110310142214.0c90e8a8@shaggy.doo> Message-ID: I'll go along with that. Easy to add a line, limited to maybe 50 char or less, to the .info Ed On 3/10/11, Ozan T?rky?lmaz wrote: > 2011/3/10 Erik Hanson : >> On Thu, 10 Mar 2011 15:00:28 -0500 >> Kyle Brown wrote: >> >>> I believe it would be emmensely useful to have a short description >>> displayed when browsing each of the slackbuilds.org directories. >>> >>> Currently only "Name", "Version", "Updated On" are displayed in the >>> lists. >>> >>> I believe changing this to >>> "Name",**"Description"**,"Version","Updated On" would be very helpful. >> >> I coded this a long time ago, but it was very slow because a short >> description is not in the db, it had to be pulled from each slack-desc. >> If we get that data in the db then it should be easy to add. >> > > How about making it mandatory for .infos. Short-desc would be really > useful for browsers of the repo. > > -- > Ozan, BSc, BEng > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Sent from my mobile device You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 From andrew at andrews-corner.org Thu Mar 10 23:21:40 2011 From: andrew at andrews-corner.org (andrew) Date: Fri, 11 Mar 2011 10:21:40 +1100 Subject: [Slackbuilds-users] rtorrent on slackware -current / 13.37 Message-ID: <20110310232140.GA10471@skamandros.andrews-corner.org> Hi, Looks like rtorrent requires a small patch to compile against the new ncurses in the upcoming 13.37 release: http://www.linuxquestions.org/questions/slackware-14/update-to-current-rtorrent-throws-error-wont-start-867779/ I cc the current maintainer as well... Andrew -- Do you think that's air you're breathing? From slakmagik at gmail.com Fri Mar 11 02:58:54 2011 From: slakmagik at gmail.com (slakmagik) Date: Thu, 10 Mar 2011 21:58:54 -0500 Subject: [Slackbuilds-users] Idea for slackbuilds.org In-Reply-To: References: <4D792DDC.2060301@ec.rr.com> <20110310142214.0c90e8a8@shaggy.doo> Message-ID: <20110311025854.GA30449@devbox> On 2011-03-10 (Thu) 13:00:27 [-0800], King Beowulf wrote: > I'll go along with that. Easy to add a line, limited to maybe 50 char > or less, to the .info > > Ed > > > On 3/10/11, Ozan T?rky?lmaz wrote: > > 2011/3/10 Erik Hanson : > >> On Thu, 10 Mar 2011 15:00:28 -0500 > >> Kyle Brown wrote: > >> > >>> I believe it would be emmensely useful to have a short description > >>> displayed when browsing each of the slackbuilds.org directories. > >>> > >>> Currently only "Name", "Version", "Updated On" are displayed in the > >>> lists. > >>> > >>> I believe changing this to > >>> "Name",**"Description"**,"Version","Updated On" would be very helpful. > >> > >> I coded this a long time ago, but it was very slow because a short > >> description is not in the db, it had to be pulled from each slack-desc. > >> If we get that data in the db then it should be easy to add. > >> > > > > How about making it mandatory for .infos. Short-desc would be really > > useful for browsers of the repo. > > If there was any way to re-use the slack-desc's 'app (shortdesc)' line I think that would be much better than duplicating the info with a new .info field. I have no idea about the backend but it seems like a db column could be populated from the slack-descs once and repopulated at each update and be as fast as anything else in the meantimes. Whatever the method, the data is already there - seems like adding it again shouldn't help. From erik at slackbuilds.org Fri Mar 11 03:30:47 2011 From: erik at slackbuilds.org (Erik Hanson) Date: Thu, 10 Mar 2011 21:30:47 -0600 Subject: [Slackbuilds-users] Idea for slackbuilds.org In-Reply-To: <20110311025854.GA30449@devbox> References: <4D792DDC.2060301@ec.rr.com> <20110310142214.0c90e8a8@shaggy.doo> <20110311025854.GA30449@devbox> Message-ID: <20110310213047.54ee67ea@shaggy.doo> On Thu, 10 Mar 2011 21:58:54 -0500 slakmagik wrote: > On 2011-03-10 (Thu) 13:00:27 [-0800], King Beowulf wrote: > > I'll go along with that. Easy to add a line, limited to maybe 50 > > char or less, to the .info > > > > Ed > > > > > > On 3/10/11, Ozan T?rky?lmaz wrote: > > > 2011/3/10 Erik Hanson : > > >> On Thu, 10 Mar 2011 15:00:28 -0500 > > >> Kyle Brown wrote: > > >> > > >>> I believe it would be emmensely useful to have a short > > >>> description displayed when browsing each of the slackbuilds.org > > >>> directories. > > >>> > > >>> Currently only "Name", "Version", "Updated On" are displayed in > > >>> the lists. > > >>> > > >>> I believe changing this to > > >>> "Name",**"Description"**,"Version","Updated On" would be very > > >>> helpful. > > >> > > >> I coded this a long time ago, but it was very slow because a > > >> short description is not in the db, it had to be pulled from > > >> each slack-desc. If we get that data in the db then it should be > > >> easy to add. > > >> > > > > > > How about making it mandatory for .infos. Short-desc would be > > > really useful for browsers of the repo. > > > > > If there was any way to re-use the slack-desc's 'app (shortdesc)' > line I think that would be much better than duplicating the info with > a new .info field. I have no idea about the backend but it seems like > a db column could be populated from the slack-descs once and > repopulated at each update and be as fast as anything else in the > meantimes. Whatever the method, the data is already there - seems > like adding it again shouldn't help. This is what we've been discussing. It seems possible. Technical things need to be solved first. We will not be requiring redundant data in the .info file. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Fri Mar 11 08:20:18 2011 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 11 Mar 2011 00:20:18 -0800 Subject: [Slackbuilds-users] New maintainer: nvidia, libvdpau, vdpauinfo Message-ID: With Heinz' recent blessing, I have volunteered to take over the slackbuilds he announced as EOL. They are alive and kicking. I have updated the .info but have otherwise made no changes to the 13.1 scripts. I will test against 13.37 rc1 "soon" and also test legacy drivers when I find my old GeforceDDR AGP card. As I mentioned on #slackbuilds IRC recently, post here or to my email any comments or suggestions. Admins, since submissions are closed, see links below. http://www.koenigcomputers.com/sbo-ewk/libvdpau.tar.gz http://www.koenigcomputers.com/sbo-ewk/nvidia-driver.tar.gz http://www.koenigcomputers.com/sbo-ewk/nvidia-kernel.tar.gz http://www.koenigcomputers.com/sbo-ewk/nvidia-legacy173-driver.tar.gz http://www.koenigcomputers.com/sbo-ewk/nvidia-legacy173-kernel.tar.gz http://www.koenigcomputers.com/sbo-ewk/nvidia-legacy96-driver.tar.gz http://www.koenigcomputers.com/sbo-ewk/nvidia-legacy96-kernel.tar.gz http://www.koenigcomputers.com/sbo-ewk/vdpauinfo.tar.gz Ed Koenig -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozan.turkyilmaz at gmail.com Sat Mar 12 19:39:03 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 12 Mar 2011 21:39:03 +0200 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110309110827.73e0e9e1@liberty.rlwhome.lan> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: 2011/3/9 Robby Workman : > Okay, everybody saw the 13.37 rc1 announcement, I guess, so now you > know why we closed pending a few days ago :-) ?We're doing some early > work on getting ready for 13.37, and we'll be soliciting feedback for > that soon, but at the moment, I personally would like to know if there > are any pressing issues that need to be handled in our 13.1 repo. > I'm not making any promises to do anything, but if you have some > important things that need to be addressed there, now is the time to > let me know (and make it as easy as possible to do - i.e. provide a > tarball, git pull request, etcetera). ?I've already got the update > to tor, so don't mention that one. ?My goal is to finalize 13.1 so > that we can all focus on getting everything in place for 13.37. > Updates attached. Updated scripts; libebml (version bump and option to build static), libmatroska (version bump and option to build static) libtbb (version bump) gsnmp(version bump. And I know web site is down but ftp works fine) mkvtoolnix (version bump and option to build QT gui). -- Ozan, BSc, BEng -------------- next part -------------- A non-text attachment was scrubbed... Name: update.tar.gz Type: application/x-gzip Size: 5991 bytes Desc: not available URL: From artourter at gmail.com Sat Mar 12 23:15:54 2011 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sat, 12 Mar 2011 23:15:54 +0000 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110309110827.73e0e9e1@liberty.rlwhome.lan> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: Hi, There are quite a few packages that, although do not need to be upgraded to work in 13.37, they need to be recompiled as the libraries they depend on have changed. this include all the perl modules, texlive (pdftex at least does not work due to poppler) pdftk (due to libgcj). I suspect there are others but it gives a good idea of the issue. Should be bump the build number of these package on the 13.37 repo when there isn't a new version available, to help users? Cheers Greg On 9 March 2011 17:08, Robby Workman wrote: > Okay, everybody saw the 13.37 rc1 announcement, I guess, so now you > know why we closed pending a few days ago :-) ?We're doing some early > work on getting ready for 13.37, and we'll be soliciting feedback for > that soon, but at the moment, I personally would like to know if there > are any pressing issues that need to be handled in our 13.1 repo. > I'm not making any promises to do anything, but if you have some > important things that need to be addressed there, now is the time to > let me know (and make it as easy as possible to do - i.e. provide a > tarball, git pull request, etcetera). ?I've already got the update > to tor, so don't mention that one. ?My goal is to finalize 13.1 so > that we can all focus on getting everything in place for 13.37. > > -RW > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > From erik at slackbuilds.org Sat Mar 12 23:34:24 2011 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 12 Mar 2011 17:34:24 -0600 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: <20110312173424.28f9d2b6@shaggy.doo> On Sat, 12 Mar 2011 23:15:54 +0000 "Greg' Ar Tourter" wrote: > There are quite a few packages that, although do not need to be > upgraded to work in 13.37, they need to be recompiled as the libraries > they depend on have changed. > this include all the perl modules, texlive (pdftex at least does not > work due to poppler) pdftk (due to libgcj). I suspect there are others > but it gives a good idea of the issue. > > Should be bump the build number of these package on the 13.37 repo > when there isn't a new version available, to help users? Although I see your point, we haven't done this in the past, so I'm inclined to say no. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From ozan.turkyilmaz at gmail.com Sat Mar 12 23:42:05 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sun, 13 Mar 2011 01:42:05 +0200 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110312173424.28f9d2b6@shaggy.doo> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> <20110312173424.28f9d2b6@shaggy.doo> Message-ID: 2011/3/13 Erik Hanson : > On Sat, 12 Mar 2011 23:15:54 +0000 > "Greg' Ar Tourter" wrote: > >> There are quite a few packages that, although do not need to be >> upgraded to work in 13.37, they need to be recompiled as the libraries >> they depend on have changed. >> this include all the perl modules, texlive (pdftex at least does not >> work due to poppler) pdftk (due to libgcj). I suspect there are others >> but it gives a good idea of the issue. >> >> Should be bump the build number of these package on the 13.37 repo >> when there isn't a new version available, to help users? > > Although I see your point, we haven't done this in the past, so I'm > inclined to say no. Any sane user would recompile them anyway. -- Ozan, BSc, BEng From ml at mareichelt.com Sat Mar 12 23:55:39 2011 From: ml at mareichelt.com (markus reichelt) Date: Sun, 13 Mar 2011 00:55:39 +0100 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: <20110312235539.GF20371@pc21.mareichelt.com> * Greg' Ar Tourter wrote: > Should be bump the build number of these package on the 13.37 repo > when there isn't a new version available, to help users? I wondered about that too, but decided not to fiddle with build numbers since the upcoming stable release is a new branch on SBo anyway. That said, I can tell that the scripts I maintain all work on -rc1 and thus are most likely ready to be bumped to the upcoming release branch, namely: libraries/Botan system/aespipe libraries/dietlibc system/extundelete libraries/libowfat network/opera network/sslscan development/tcc network/vidalia graphics/xzgv network/GeoIP (new maintainer) I took the opportunity to add the missing GeoIP support to vidalia, since I promised to also take over the GeoIP SlackBuild. Both will run just fine on -rc1 as-is and are by no means a security update. Whoever may need the updated SlackBuilds: http://mareichelt.de/tmp/GeoIP.tar.gz http://mareichelt.de/tmp/vidalia.tar.gz HTH -- left blank, right bald -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Mar 14 02:30:52 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 13 Mar 2011 21:30:52 -0500 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110312173424.28f9d2b6@shaggy.doo> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> <20110312173424.28f9d2b6@shaggy.doo> Message-ID: <20110313213052.7a0fc003@liberty.rlwhome.lan> On Sat, 12 Mar 2011 17:34:24 -0600 Erik Hanson wrote: > On Sat, 12 Mar 2011 23:15:54 +0000 > "Greg' Ar Tourter" wrote: > > > There are quite a few packages that, although do not need to be > > upgraded to work in 13.37, they need to be recompiled as the > > libraries they depend on have changed. > > this include all the perl modules, texlive (pdftex at least does not > > work due to poppler) pdftk (due to libgcj). I suspect there are > > others but it gives a good idea of the issue. > > > > Should be bump the build number of these package on the 13.37 repo > > when there isn't a new version available, to help users? > > Although I see your point, we haven't done this in the past, so I'm > inclined to say no. Same inclination here. :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From jedi.kenjiro at gmail.com Mon Mar 14 11:35:10 2011 From: jedi.kenjiro at gmail.com (Yucatan "Kenjiro" Costa) Date: Mon, 14 Mar 2011 08:35:10 -0300 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110313213052.7a0fc003@liberty.rlwhome.lan> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> <20110312173424.28f9d2b6@shaggy.doo> <20110313213052.7a0fc003@liberty.rlwhome.lan> Message-ID: Just to let you guys know, the chromium.SlackBuild works with 13.1 and -current (13.37rc1), so no changes need on this regard. I barely can't wait for the official release of 13.37 :D On Sun, Mar 13, 2011 at 11:30 PM, Robby Workman wrote: > On Sat, 12 Mar 2011 17:34:24 -0600 > Erik Hanson wrote: > > > On Sat, 12 Mar 2011 23:15:54 +0000 > > "Greg' Ar Tourter" wrote: > > > > > There are quite a few packages that, although do not need to be > > > upgraded to work in 13.37, they need to be recompiled as the > > > libraries they depend on have changed. > > > this include all the perl modules, texlive (pdftex at least does not > > > work due to poppler) pdftk (due to libgcj). I suspect there are > > > others but it gives a good idea of the issue. > > > > > > Should be bump the build number of these package on the 13.37 repo > > > when there isn't a new version available, to help users? > > > > Although I see your point, we haven't done this in the past, so I'm > > inclined to say no. > > > Same inclination here. :-) > > -RW > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -- May the Force be with you! Yucatan "Kenjiro" Costa -------------- next part -------------- An HTML attachment was scrubbed... URL: From dragonwisard at gmail.com Mon Mar 14 12:48:30 2011 From: dragonwisard at gmail.com (Ben Mendis) Date: Mon, 14 Mar 2011 08:48:30 -0400 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110313213052.7a0fc003@liberty.rlwhome.lan> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> <20110312173424.28f9d2b6@shaggy.doo> <20110313213052.7a0fc003@liberty.rlwhome.lan> Message-ID: On Sun, Mar 13, 2011 at 10:30 PM, Robby Workman wrote: > On Sat, 12 Mar 2011 17:34:24 -0600 > Erik Hanson wrote: > > > On Sat, 12 Mar 2011 23:15:54 +0000 > > "Greg' Ar Tourter" wrote: > > > > > There are quite a few packages that, although do not need to be > > > upgraded to work in 13.37, they need to be recompiled as the > > > libraries they depend on have changed. > > > this include all the perl modules, texlive (pdftex at least does not > > > work due to poppler) pdftk (due to libgcj). I suspect there are > > > others but it gives a good idea of the issue. > > > > > > Should be bump the build number of these package on the 13.37 repo > > > when there isn't a new version available, to help users? > > > > Although I see your point, we haven't done this in the past, so I'm > > inclined to say no. > > > Same inclination here. :-) > Out of curiosity, what would be the potential downsides to bumping the build numbers? Is it just that it's inconsistent with previous releases, or that it involves a lot of work? (I'm not implying that you're lazy, I appreciate the valuable time you donate to helping us out.) Or are there some other problems that it might introduce that I'm not aware of? I'd just like to understand the reasoning behind this decision. Thanks, Ben > > -RW > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.abela at maltats.com Mon Mar 14 13:21:15 2011 From: chris.abela at maltats.com (Chris Abela) Date: Mon, 14 Mar 2011 14:21:15 +0100 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: Message-ID: >> Out of curiosity, what would be the potential downsides to bumping the build numbers? We write SlackBuilds so build numbers should reflect SlackBuilds. It is up to the users to compile, package and install on their machines. -------------- next part -------------- An HTML attachment was scrubbed... URL: From xgizzmo at slackbuilds.org Mon Mar 14 13:41:11 2011 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Mon, 14 Mar 2011 09:41:11 -0400 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: Message-ID: <201103140941.12204.xgizzmo@slackbuilds.org> On Monday 14 March 2011 09:21:15 Chris Abela wrote: > > We write SlackBuilds so build numbers should reflect SlackBuilds. It is up > to the users to compile, package and install on their machines. > > That is correct the build number reflects the changes to the SlackBuild in our case. But just for fun lets say you want to use the logic that this is a new Slackware version and the build numbers need to be changed, then they should all be reset to 1. In any case we don't dictate how the admin manage their system but we do make provisions for the admin to change the build number if they want to. For example BUILD="5" TAG="_SBo_13.37" ./Some.SlackBuild --dsomero From hba.nihilismus at gmail.com Mon Mar 14 15:04:11 2011 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Mon, 14 Mar 2011 09:04:11 -0600 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <201103140941.12204.xgizzmo@slackbuilds.org> References: <201103140941.12204.xgizzmo@slackbuilds.org> Message-ID: On Mon, Mar 14, 2011 at 7:41 AM, wrote: > That is correct the build number reflects the changes to the SlackBuild in > our case. But just for fun lets say you want to use the logic that this is > a new Slackware version and the build numbers need to be changed, then they > should all be reset to 1. In any case we don't dictate how the admin manage > their system but we do make provisions for the admin to change the build > number if they want to. For example BUILD="5" TAG="_SBo_13.37" ./Some.SlackBuild > Keeping BUILD the same helps to those one (like me) who still uses 13.0, so they just rsync its local port with SBo 13.1/13.37 and theres no need to worry (mostly) about changes between slackware version, BUILD and SBo ports at all... so i don?t see any need (at least for me) to use that "change-the-build-number-if-they-want" thing ;) -- - hba From dragonwisard at gmail.com Mon Mar 14 17:38:10 2011 From: dragonwisard at gmail.com (Ben Mendis) Date: Mon, 14 Mar 2011 13:38:10 -0400 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <201103140941.12204.xgizzmo@slackbuilds.org> Message-ID: 2011/3/14 Antonio Hern?ndez Blas > On Mon, Mar 14, 2011 at 7:41 AM, wrote: > > That is correct the build number reflects the changes to the SlackBuild > in > > our case. But just for fun lets say you want to use the logic that this > is > > a new Slackware version and the build numbers need to be changed, then > they > > should all be reset to 1. In any case we don't dictate how the admin > manage > > their system but we do make provisions for the admin to change the build > > number if they want to. For example BUILD="5" TAG="_SBo_13.37" > ./Some.SlackBuild > > > > Keeping BUILD the same helps to those one (like me) who still uses > 13.0, so they just rsync its local port with SBo 13.1/13.37 and theres > no need to worry (mostly) about changes between slackware version, > BUILD and SBo ports at all... so i don?t see any need (at least for > me) to use that "change-the-build-number-if-they-want" thing ;) > Perhaps I misunderstood. I thought the proposal was to bump the build number for SlackBuilds in the new 13.37 repository that would need to be rebuilt after updating from 13.1 (as a convenience to sbopkg users). I had assumed that the SlackBuilds in the 13.1 repository would stay the same since no re-build was necessary. Also, I realize that the build number can be specified at build-time, but that doesn't provide any assistance to sbopkg users at all, they would still need to manually add each package to the queue to be rebuilt. (Furthermore, sbopkg seems to lack the ability to override the default BUILD or TAG on a per-package basis, but that has nothing to do with SBo itself.) I can accept the argument that the build number reflects changes in the SlackBuild itself, but there didn't seem to be any harm in making an exception in this situation. Oh well, it just means that users will need to do a bit more manual work (and we'll probably find ourselves answering a lot of very similar questions on LQ and ##slackware after people upgrade), but that really nothing new. Would it be acceptable for maintainers to submit a build bump if they wanted to, or is there a hard "NO" on this issue? Not that it even affects me since I don't currently maintain any packages which would be affected. > -- > - hba > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Mon Mar 14 18:01:50 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 14 Mar 2011 13:01:50 -0500 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110312235539.GF20371@pc21.mareichelt.com> References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> <20110312235539.GF20371@pc21.mareichelt.com> Message-ID: <20110314130150.6fcf7b65@liberty.rlwhome.lan> On Sun, 13 Mar 2011 00:55:39 +0100 markus reichelt wrote: > * Greg' Ar Tourter wrote: > > > Should be bump the build number of these package on the 13.37 repo > > when there isn't a new version available, to help users? > > I wondered about that too, but decided not to fiddle with build > numbers since the upcoming stable release is a new branch on SBo > anyway. > > That said, I can tell that the scripts I maintain all work on -rc1 > and thus are most likely ready to be bumped to the upcoming release > branch, namely: > > libraries/Botan > system/aespipe > libraries/dietlibc > system/extundelete > libraries/libowfat > network/opera > network/sslscan > development/tcc > network/vidalia > graphics/xzgv I've noted these as good. > network/GeoIP (new maintainer) > > I took the opportunity to add the missing GeoIP support to vidalia, > since I promised to also take over the GeoIP SlackBuild. Both will > run just fine on -rc1 as-is and are by no means a security update. > > Whoever may need the updated SlackBuilds: > > http://mareichelt.de/tmp/GeoIP.tar.gz > http://mareichelt.de/tmp/vidalia.tar.gz For us, these can wait until after the release :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Mar 14 18:03:04 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 14 Mar 2011 13:03:04 -0500 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> <20110312173424.28f9d2b6@shaggy.doo> <20110313213052.7a0fc003@liberty.rlwhome.lan> Message-ID: <20110314130304.062c39f2@liberty.rlwhome.lan> On Mon, 14 Mar 2011 08:48:30 -0400 Ben Mendis wrote: > On Sun, Mar 13, 2011 at 10:30 PM, Robby Workman > wrote: > > > On Sat, 12 Mar 2011 17:34:24 -0600 > > Erik Hanson wrote: > > > > > On Sat, 12 Mar 2011 23:15:54 +0000 > > > "Greg' Ar Tourter" wrote: > > > > > > > There are quite a few packages that, although do not need to be > > > > upgraded to work in 13.37, they need to be recompiled as the > > > > libraries they depend on have changed. > > > > this include all the perl modules, texlive (pdftex at least > > > > does not work due to poppler) pdftk (due to libgcj). I suspect > > > > there are others but it gives a good idea of the issue. > > > > > > > > Should be bump the build number of these package on the 13.37 > > > > repo when there isn't a new version available, to help users? > > > > > > Although I see your point, we haven't done this in the past, so > > > I'm inclined to say no. > > > > > > Same inclination here. :-) > > > > Out of curiosity, what would be the potential downsides to bumping > the build numbers? > Is it just that it's inconsistent with previous releases, or that it > involves a lot of work? (I'm not implying that you're lazy, I > appreciate the valuable time you donate to helping us out.) > Or are there some other problems that it might introduce that I'm not > aware of? > > I'd just like to understand the reasoning behind this decision. We're lazy and it involves a lot of work, and it really doesn't add any benefit to admins who keep well-managed systems anyway. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From t3slider at gmail.com Mon Mar 14 18:12:18 2011 From: t3slider at gmail.com (T3slider) Date: Mon, 14 Mar 2011 14:12:18 -0400 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <201103140941.12204.xgizzmo@slackbuilds.org> Message-ID: <20110314181218.GA3133@KeithPC.phub.net.cable.rogers.com> Bumping the version number for every package on SBo would be the equivalent of doing `slackpkg clean-system` and recompiling each third-party application from slackbuilds.org -- which would be the standard advice for anyone having such troubles with multiple packages. Otherwise, applications that may be ABI-compatible with dependencies from Slackware 13.37 would need to maintain the same build number while others that would require a recompile would need a bump. Determining which ones would need this is too much effort in my opinion, especially when you get into issues like an application breaking not because it isn't ABI-compatible with Slackware packages, but because it isn't ABI-compatible with an SBo dependency that breaks with new Slackware. You can take your chances running old 13.1-compiled apps on 13.37 and recompile those that are broken, or clean-system and rebuild them all (`ls /var/log/packages/*_SBo` would get a list). Of course you would need to build them in the right order which would involve reading READMEs or using build queues. In the end, I don't think bumping versions has *any* benefit that I can see and it's certainly more work anyway. On Mon, Mar 14, 2011 at 01:38:10PM -0400, Ben Mendis wrote: > Perhaps I misunderstood. I thought the proposal was to bump the build > number for SlackBuilds in the new 13.37 repository that would need to be > rebuilt after updating from 13.1 (as a convenience to sbopkg users). I had > assumed that the SlackBuilds in the 13.1 repository would stay the same > since no re-build was necessary. > > Also, I realize that the build number can be specified at build-time, but > that doesn't provide any assistance to sbopkg users at all, they would > still need to manually add each package to the queue to be rebuilt. > (Furthermore, sbopkg seems to lack the ability to override the default > BUILD or TAG on a per-package basis, but that has nothing to do with SBo > itself.) > > I can accept the argument that the build number reflects changes in the > SlackBuild itself, but there didn't seem to be any harm in making an > exception in this situation. > > Oh well, it just means that users will need to do a bit more manual work > (and we'll probably find ourselves answering a lot of very similar > questions on LQ and ##slackware after people upgrade), but that really > nothing new. > > Would it be acceptable for maintainers to submit a build bump if they > wanted to, or is there a hard "NO" on this issue? > Not that it even affects me since I don't currently maintain any packages > which would be affected. > > -- > - hba > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > _______________________________________________ > 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 rworkman at slackbuilds.org Mon Mar 14 18:49:51 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 14 Mar 2011 13:49:51 -0500 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <201103140941.12204.xgizzmo@slackbuilds.org> Message-ID: <20110314134951.5e104919@liberty.rlwhome.lan> On Mon, 14 Mar 2011 13:38:10 -0400 Ben Mendis wrote: > Perhaps I misunderstood. I thought the proposal was to bump the build > number for SlackBuilds in the new 13.37 repository that would need to > be rebuilt after updating from 13.1 (as a convenience to sbopkg > users). I had assumed that the SlackBuilds in the 13.1 repository > would stay the same since no re-build was necessary. > > Also, I realize that the build number can be specified at build-time, > but that doesn't provide any assistance to sbopkg users at all, they > would still need to manually add each package to the queue to be > rebuilt. (Furthermore, sbopkg seems to lack the ability to override > the default BUILD or TAG on a per-package basis, but that has nothing > to do with SBo itself.) > > I can accept the argument that the build number reflects changes in > the SlackBuild itself, but there didn't seem to be any harm in making > an exception in this situation. This is the first release that we've been using git during the change from previous to new, so the workflow is a bit different, and we can't do what we've always done, which is reset all of the BUILD numbers to "1" regardless. It's never caused problems (that we're aware of) for sbopkg before, and I don't see why it should, and even if it does, I still don't think that would be a large enough issue to change what we do. Besides, I'd be quite surprised if sbopkg didn't allow setting BUILD locally. > Would it be acceptable for maintainers to submit a build bump if they > wanted to, or is there a hard "NO" on this issue? No, that's a timesink that we can't afford at this point. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Mar 14 18:50:43 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 14 Mar 2011 13:50:43 -0500 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110314181218.GA3133@KeithPC.phub.net.cable.rogers.com> References: <201103140941.12204.xgizzmo@slackbuilds.org> <20110314181218.GA3133@KeithPC.phub.net.cable.rogers.com> Message-ID: <20110314135043.40f32a2e@liberty.rlwhome.lan> On Mon, 14 Mar 2011 14:12:18 -0400 T3slider wrote: > Bumping the version number for every package on SBo would be the > equivalent of doing `slackpkg clean-system` and recompiling each > third-party application from slackbuilds.org -- which would be the > standard advice for anyone having such troubles with multiple > packages. Otherwise, applications that may be ABI-compatible with > dependencies from Slackware 13.37 would need to maintain the same > build number while others that would require a recompile would need a > bump. Determining which ones would need this is too much effort in my > opinion, especially when you get into issues like an application > breaking not because it isn't ABI-compatible with Slackware packages, > but because it isn't ABI-compatible with an SBo dependency that > breaks with new Slackware. > > You can take your chances running old 13.1-compiled apps on 13.37 and > recompile those that are broken, or clean-system and rebuild them all > (`ls /var/log/packages/*_SBo` would get a list). Of course you would > need to build them in the right order which would involve reading > READMEs or using build queues. In the end, I don't think bumping > versions has *any* benefit that I can see and it's certainly more work > anyway. Good summary there too. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Mar 14 18:51:25 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 14 Mar 2011 13:51:25 -0500 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <20110309110827.73e0e9e1@liberty.rlwhome.lan> Message-ID: <20110314135125.799608fa@liberty.rlwhome.lan> On Sat, 12 Mar 2011 21:39:03 +0200 Ozan T?rky?lmaz wrote: > 2011/3/9 Robby Workman : > > Okay, everybody saw the 13.37 rc1 announcement, I guess, so now you > > know why we closed pending a few days ago :-) ?We're doing some > > early work on getting ready for 13.37, and we'll be soliciting > > feedback for that soon, but at the moment, I personally would like > > to know if there are any pressing issues that need to be handled in > > our 13.1 repo. I'm not making any promises to do anything, but if > > you have some important things that need to be addressed there, now > > is the time to let me know (and make it as easy as possible to do - > > i.e. provide a tarball, git pull request, etcetera). ?I've already > > got the update to tor, so don't mention that one. ?My goal is to > > finalize 13.1 so that we can all focus on getting everything in > > place for 13.37. > > > > Updates attached. Updated scripts; libebml (version bump and option to > build static), libmatroska (version bump and option to build static) > libtbb (version bump) gsnmp(version bump. And I know web site is down > but ftp works fine) mkvtoolnix (version bump and option to build QT > gui). Is this stuff that's necessary (REALLY needed) for 13.1, or can it wait for submissions to open after 13.37 releases? -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From dragonwisard at gmail.com Mon Mar 14 18:57:21 2011 From: dragonwisard at gmail.com (Ben Mendis) Date: Mon, 14 Mar 2011 14:57:21 -0400 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110314181218.GA3133@KeithPC.phub.net.cable.rogers.com> References: <201103140941.12204.xgizzmo@slackbuilds.org> <20110314181218.GA3133@KeithPC.phub.net.cable.rogers.com> Message-ID: Ah, this explanation makes perfect sense. Thanks! On Mon, Mar 14, 2011 at 2:12 PM, T3slider wrote: > Bumping the version number for every package on SBo would be the > equivalent of doing `slackpkg clean-system` and recompiling each > third-party application from slackbuilds.org -- which would be the > standard advice for anyone having such troubles with multiple packages. > Otherwise, applications that may be ABI-compatible with dependencies > from Slackware 13.37 would need to maintain the same build number while > others that would require a recompile would need a bump. Determining > which ones would need this is too much effort in my opinion, especially > when you get into issues like an application breaking not because it > isn't ABI-compatible with Slackware packages, but because it isn't > ABI-compatible with an SBo dependency that breaks with new Slackware. > > You can take your chances running old 13.1-compiled apps on 13.37 and > recompile those that are broken, or clean-system and rebuild them all > (`ls /var/log/packages/*_SBo` would get a list). Of course you would > need to build them in the right order which would involve reading > READMEs or using build queues. In the end, I don't think bumping > versions has *any* benefit that I can see and it's certainly more work > anyway. > > On Mon, Mar 14, 2011 at 01:38:10PM -0400, Ben Mendis wrote: > > Perhaps I misunderstood. I thought the proposal was to bump the build > > number for SlackBuilds in the new 13.37 repository that would need to > be > > rebuilt after updating from 13.1 (as a convenience to sbopkg users). I > had > > assumed that the SlackBuilds in the 13.1 repository would stay the > same > > since no re-build was necessary. > > > > Also, I realize that the build number can be specified at build-time, > but > > that doesn't provide any assistance to sbopkg users at all, they would > > still need to manually add each package to the queue to be rebuilt. > > (Furthermore, sbopkg seems to lack the ability to override the default > > BUILD or TAG on a per-package basis, but that has nothing to do with > SBo > > itself.) > > > > I can accept the argument that the build number reflects changes in > the > > SlackBuild itself, but there didn't seem to be any harm in making an > > exception in this situation. > > > > Oh well, it just means that users will need to do a bit more manual > work > > (and we'll probably find ourselves answering a lot of very similar > > questions on LQ and ##slackware after people upgrade), but that really > > nothing new. > > > > Would it be acceptable for maintainers to submit a build bump if they > > wanted to, or is there a hard "NO" on this issue? > > Not that it even affects me since I don't currently maintain any > packages > > which would be affected. > > > > -- > > - hba > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - > http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - http://slackbuilds.org/faq/ > > > _______________________________________________ > > 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 slakmagik at gmail.com Tue Mar 15 02:55:58 2011 From: slakmagik at gmail.com (slakmagik) Date: Mon, 14 Mar 2011 22:55:58 -0400 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110314134951.5e104919@liberty.rlwhome.lan> References: <201103140941.12204.xgizzmo@slackbuilds.org> <20110314134951.5e104919@liberty.rlwhome.lan> Message-ID: <20110315025558.GA31861@devbox> On 2011-03-14 (Mon) 13:49:51 [-0500], Robby Workman wrote: > On Mon, 14 Mar 2011 13:38:10 -0400 > Ben Mendis wrote: > > > > > Also, I realize that the build number can be specified at build-time, > > but that doesn't provide any assistance to sbopkg users at all, they > > would still need to manually add each package to the queue to be > > rebuilt. (Furthermore, sbopkg seems to lack the ability to override > > the default BUILD or TAG on a per-package basis, but that has nothing > > to do with SBo itself.) > > > > This is the first release that we've been using git during the change > from previous to new, so the workflow is a bit different, and we can't > do what we've always done, which is reset all of the BUILD numbers to > "1" regardless. It's never caused problems (that we're aware of) for > sbopkg before, and I don't see why it should, and even if it does, I > still don't think that would be a large enough issue to change what > we do. Besides, I'd be quite surprised if sbopkg didn't allow setting > BUILD locally. > Well... :) I'm surprised it doesn't allow it properly. A way to change the build on a per package basis from the command line is to use the 'per app options' syntax on the command line and use standard vars (BUILD, etc.) like special vars (WITH_WHIZBANG_FEATURE, etc.): # sbopkg -i app:BUILD=build However, doing the same for TAG fails because sbopkg uses an internal variable. The following is *wrong* (because the user shouldn't use this variable) but "works" (at least as far as building): # sbopkg -i app:REPO_TAG=tag The queuefiles don't-quite-work the same way: app|BUILD=build REPO_TAG=tag >From the menu interface, using the 'OPTIONS' item is the same - though, if you didn't mind changing the SlackBuild, you'd could also use 'CUSTOM' to do it directly. And, regardless, this isn't directly documented. IOW, Ben, you should have reported this as a bug and there's work to do. If there's anything you can do *without* sbopkg that you can't do *with* sbopkg, it's at least theoretically a bug. But, while possibly simple to fix (hope springs eternal), the general issue is in a lot of areas of the code, some of it really squirrelly, and a proper fix may have to wait until next time. As is (aside from one small glitch whose tiny patch just needs to be tested a little more and committed), sbopkg seems to be working (though changing BUILD and TAG is awkward and inconsistent) and I wouldn't want to break anything right now trying to smooth that out. If this needs more discussion, shifting this part to sbopkg-users would be best. One last note: I don't know what you mean by "need to manually add each package to the queue to be rebuilt". I keep a master queue of every SBo package (or sub-queue of packages) on a given system (and one of local stuff) and habitually rebuild everything at new Slackware/SBo releases by reusing that (them). If you don't have such a queue then, from the menu interface, there's 'Add/Add all installed packages to the queue', 'Sort/Sort items in build queue', and 'Save/Save the current build queue' (though I'd just use $EDITOR for sorting in that case). From eric.b.pratt at gmail.com Tue Mar 15 03:49:08 2011 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Mon, 14 Mar 2011 23:49:08 -0400 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110315025558.GA31861@devbox> References: <201103140941.12204.xgizzmo@slackbuilds.org> <20110314134951.5e104919@liberty.rlwhome.lan> <20110315025558.GA31861@devbox> Message-ID: On Mon, Mar 14, 2011 at 10:55 PM, slakmagik wrote: > > If there's anything you can do *without* sbopkg that you can't do *with* > sbopkg, it's at least theoretically a bug. > I knew it was a bug when I couldn't make a pot pie with sbopkg. I just KNEW it! From rworkman at slackbuilds.org Tue Mar 15 04:03:34 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 14 Mar 2011 23:03:34 -0500 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <201103140941.12204.xgizzmo@slackbuilds.org> <20110314134951.5e104919@liberty.rlwhome.lan> <20110315025558.GA31861@devbox> Message-ID: <20110314230334.786c068a@liberty.rlwhome.lan> On Mon, 14 Mar 2011 23:49:08 -0400 Eric Pratt wrote: > On Mon, Mar 14, 2011 at 10:55 PM, slakmagik > wrote: > > > > If there's anything you can do *without* sbopkg that you can't do > > *with* sbopkg, it's at least theoretically a bug. > > > > I knew it was a bug when I couldn't make a pot pie with sbopkg. I > just KNEW it! While we're fixing these egregious oversights, someone should figure out how to make it bring me a beer. ;-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From slakmagik at gmail.com Tue Mar 15 21:04:52 2011 From: slakmagik at gmail.com (slakmagik) Date: Tue, 15 Mar 2011 17:04:52 -0400 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110314230334.786c068a@liberty.rlwhome.lan> References: <201103140941.12204.xgizzmo@slackbuilds.org> <20110314134951.5e104919@liberty.rlwhome.lan> <20110315025558.GA31861@devbox> <20110314230334.786c068a@liberty.rlwhome.lan> Message-ID: <20110315210452.GA3090@devbox> On 2011-03-14 (Mon) 23:03:34 [-0500], Robby Workman wrote: > On Mon, 14 Mar 2011 23:49:08 -0400 > Eric Pratt wrote: > > > On Mon, Mar 14, 2011 at 10:55 PM, slakmagik > > wrote: > > > > > > If there's anything you can do *without* sbopkg that you can't do > > > *with* sbopkg, it's at least theoretically a bug. > > > > > > > I knew it was a bug when I couldn't make a pot pie with sbopkg. I > > just KNEW it! > > > While we're fixing these egregious oversights, someone should figure > out how to make it bring me a beer. ;-) > Oops :) - scope error. I mean "anything related to building SBo packages". Though, actually, then it should still probably bring pot pies and beer. ;) Oh, and to Ben, I have a question - I was originally thinking about abstract consistency for per app settings but is there a use case where you'd *want* to set the BUILD of all packages to the same number or the TAG of a set of packages to different values? While not the most consistent (but, after all, they're doing different things), # sbopkg -i foo:BUILD=build # per app # TAG=tag sbopkg -i foo # all apps should cover most needs. From vmj at linuxbox.fi Tue Mar 15 21:16:02 2011 From: vmj at linuxbox.fi (Mikko Varri) Date: Tue, 15 Mar 2011 23:16:02 +0200 Subject: [Slackbuilds-users] 13.37rc1 and my slackbuilds Message-ID: <20110315211602.GC18300@linuxbox.fi> Hi, I know you (admins) didn't ask for it, but since I've built them, I thought I'd let you know: all the SlackBuilds that I maintain, and their dependencies, seem to work without any changes on 13.37rc1. In detail: my 32-bit VM is up-to-date with current as of Sat Mar 12 21:07:12 UTC 2011; my 64-bit VM is up-to-date with current as of Mon Mar 14 05:32:14 UTC 2011; git clone of SBo master branch is at d28a31146bc2bfe284c9547632fd50bb04059640 (Fri Mar 11 08:48:56 2011 -0600). Below is the list of SlackBuilds I've built in both VMs. desktop/bashrun desktop/bashrun2 desktop/dzen2 desktop/qtwitter desktop/xmonad development/Pygments development/Sphinx development/alex development/darcs development/docutils development/gaphor development/gazpacho development/ghc development/happy development/haskell-test-framework development/haskell-test-framework-hunit development/haskell-test-framework-quickcheck2 development/kiwi development/nose development/pysetuptools development/setuptools_git development/zope.interface development/zope.testing libraries/FormEncode libraries/Jinja2 libraries/SQLObject libraries/ZConfig libraries/ZODB3 libraries/decorator libraries/gaphas libraries/haskell-GLURaw libraries/haskell-GLUT libraries/haskell-HTTP libraries/haskell-HUnit libraries/haskell-MonadCatchIO-mtl libraries/haskell-ObjectName libraries/haskell-OpenGL libraries/haskell-OpenGLRaw libraries/haskell-QuickCheck libraries/haskell-StateVar libraries/haskell-Tensor libraries/haskell-X11 libraries/haskell-ansi-terminal libraries/haskell-ansi-wl-pprint libraries/haskell-binary libraries/haskell-cgi libraries/haskell-dataenc libraries/haskell-deepseq libraries/haskell-digest libraries/haskell-editline libraries/haskell-fgl libraries/haskell-ghc-paths libraries/haskell-hashed-storage libraries/haskell-haskeline libraries/haskell-haskell-src libraries/haskell-hostname libraries/haskell-html libraries/haskell-lcs libraries/haskell-mmap libraries/haskell-mtl libraries/haskell-network libraries/haskell-packedstring libraries/haskell-parallel libraries/haskell-parsec libraries/haskell-regex-base libraries/haskell-regex-compat libraries/haskell-regex-posix libraries/haskell-stm libraries/haskell-syb libraries/haskell-tar libraries/haskell-terminfo libraries/haskell-text libraries/haskell-transformers libraries/haskell-utf8-string libraries/haskell-xhtml libraries/haskell-xml libraries/haskell-zip-archive libraries/haskell-zlib libraries/libedit libraries/python-transaction libraries/python2-chardet libraries/qoauth libraries/simplegeneric libraries/subvertpy libraries/xmonad-contrib libraries/zc.lockfile libraries/zdaemon libraries/zope.component libraries/zope.configuration libraries/zope.event libraries/zope.hookable libraries/zope.i18nmessageid libraries/zope.location libraries/zope.proxy libraries/zope.schema libraries/zope.security network/canto -vmj From dragonwisard at gmail.com Wed Mar 16 01:57:09 2011 From: dragonwisard at gmail.com (Ben Mendis) Date: Tue, 15 Mar 2011 21:57:09 -0400 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: <20110315210452.GA3090@devbox> References: <201103140941.12204.xgizzmo@slackbuilds.org> <20110314134951.5e104919@liberty.rlwhome.lan> <20110315025558.GA31861@devbox> <20110314230334.786c068a@liberty.rlwhome.lan> <20110315210452.GA3090@devbox> Message-ID: On Tue, Mar 15, 2011 at 5:04 PM, slakmagik wrote: > On 2011-03-14 (Mon) 23:03:34 [-0500], Robby Workman wrote: > > On Mon, 14 Mar 2011 23:49:08 -0400 > > Eric Pratt wrote: > > > > > On Mon, Mar 14, 2011 at 10:55 PM, slakmagik > > > wrote: > > > > > > > > If there's anything you can do *without* sbopkg that you can't do > > > > *with* sbopkg, it's at least theoretically a bug. > > > > > > > > > > I knew it was a bug when I couldn't make a pot pie with sbopkg. I > > > just KNEW it! > > > > > > While we're fixing these egregious oversights, someone should figure > > out how to make it bring me a beer. ;-) > > > > Oops :) - scope error. I mean "anything related to building SBo > packages". Though, actually, then it should still probably bring pot > pies and beer. ;) > > Oh, and to Ben, I have a question - I was originally thinking about > abstract consistency for per app settings but is there a use case where > you'd *want* to set the BUILD of all packages to the same number or the > TAG of a set of packages to different values? While not the most > consistent (but, after all, they're doing different things), > > # sbopkg -i foo:BUILD=build # per app > # TAG=tag sbopkg -i foo # all apps > > should cover most needs. > I didn't realize it was possible to use the "foo:BUILD=build" syntax to set per-package build numbers. Off the top of my head, I can't think of any reason to mangle either value, but I'm sure someone could find a clever way to abuse either or both. Also, I had always assumed that the BUILD number represented the package build and not the SlackBuild revision. Eg, if Pat were to rebuild a package against a new library using the same SlackBuild, wouldn't he bump the BUILD of that package in the tree? But I guess SBo is doing it differently since they host SlackBuilds and not packages. (And the issue of complex dependency chains makes perfect sense as well.) > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Wed Mar 16 02:07:28 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 15 Mar 2011 21:07:28 -0500 Subject: [Slackbuilds-users] [ANNOUNCE]: Slackware 13.37 rc1 and SBo In-Reply-To: References: <201103140941.12204.xgizzmo@slackbuilds.org> <20110314134951.5e104919@liberty.rlwhome.lan> <20110315025558.GA31861@devbox> <20110314230334.786c068a@liberty.rlwhome.lan> <20110315210452.GA3090@devbox> Message-ID: <20110315210728.55275a67@liberty.rlwhome.lan> On Tue, 15 Mar 2011 21:57:09 -0400 Ben Mendis wrote: > Also, I had always assumed that the BUILD number represented the > package build and not the SlackBuild revision. Eg, if Pat were to > rebuild a package against a new library using the same SlackBuild, > wouldn't he bump the BUILD of that package in the tree? But I guess > SBo is doing it differently since they host SlackBuilds and not > packages. Bingo. BUILD for *us* is something that we increment when changes on our end would result in changes to the resulting package. For example, if we make edits to README, we would not increment BUILD, while modification of an installed config file would result in a BUILD increment. However, BUILD for *you* (and other sysadmins) is whatever *you* want it to be. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From vmj at linuxbox.fi Thu Mar 17 09:55:49 2011 From: vmj at linuxbox.fi (Mikko Varri) Date: Thu, 17 Mar 2011 11:55:49 +0200 Subject: [Slackbuilds-users] 13.37rc1 and my slackbuilds In-Reply-To: <20110315211602.GC18300@linuxbox.fi> References: <20110315211602.GC18300@linuxbox.fi> Message-ID: <20110317095548.GD18300@linuxbox.fi> On Tue, Mar 15, 2011 at 11:16:02PM +0200, Mikko Varri wrote: > > all the SlackBuilds that I maintain, and their dependencies, seem to > work without any changes on 13.37rc1. > Make that rc2. This is boring. -vmj From sid77 at slackware.it Fri Mar 18 14:59:11 2011 From: sid77 at slackware.it (Marco Bonetti) Date: Fri, 18 Mar 2011 15:59:11 +0100 Subject: [Slackbuilds-users] Puppet (and more!) for Slackware Message-ID: <4D83733F.1080105@slackware.it> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, I'm working on a complete puppet setup for Slackware. I'm going to submit my work to SlackBuilds.org, however it will not happen soon as puppet still requires ruby 1.8, so I had to prepare a workaround for this. In the meanwhile, may I ask to reserve these values: puppet ======= User: puppet UID: 249 GID: 249 Group: puppet GID: 249 this will greatly help me so I will not have to chase any changes to http://slackbuilds.org/uid_gid.txt If you are interested in the project, you will be able to track changes and contribute over at https://github.com/sid77/puppet-slackware Thanks! - -- Marco Bonetti Tor research and other stuff: http://sid77.slackware.it/ Slackintosh Linux Project Developer: http://workaround.ch/ Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/ My GnuPG key id: 0x0B60BC5F -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2Dcz8ACgkQTYvJ9gtgvF+w0ACbB7MnVaJ7XDhKQXRCaV3uIjnR 07wAoNr/G2nOOm18WWuGEIBU7z1+OzlA =pECq -----END PGP SIGNATURE----- From niels.horn at gmail.com Fri Mar 18 15:11:55 2011 From: niels.horn at gmail.com (Niels Horn) Date: Fri, 18 Mar 2011 12:11:55 -0300 Subject: [Slackbuilds-users] Puppet (and more!) for Slackware In-Reply-To: <4D83733F.1080105@slackware.it> References: <4D83733F.1080105@slackware.it> Message-ID: On Fri, Mar 18, 2011 at 11:59 AM, Marco Bonetti wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello all, > I'm working on a complete puppet setup for Slackware. I'm going to > submit my work to SlackBuilds.org, however it will not happen soon as > puppet still requires ruby 1.8, so I had to prepare a workaround for this. > In the meanwhile, may I ask to reserve these values: > > puppet > ======= > User: ? puppet ?UID: 249 ? ? ? ?GID: 249 > Group: ?puppet ? ? ? ? ? ? ? ? ?GID: 249 > > this will greatly help me so I will not have to chase any changes to > http://slackbuilds.org/uid_gid.txt > > If you are interested in the project, you will be able to track changes > and contribute over at https://github.com/sid77/puppet-slackware > > Thanks! > > - -- > Marco Bonetti OK, done. -- Niels Horn From estranho at diogoleal.com Fri Mar 18 16:58:07 2011 From: estranho at diogoleal.com (Diogo Leal) Date: Fri, 18 Mar 2011 13:58:07 -0300 Subject: [Slackbuilds-users] Puppet (and more!) for Slackware In-Reply-To: References: <4D83733F.1080105@slackware.it> Message-ID: Hi, I'm also working with the puppet and suffered with the problem of version. I am using to manage rvm versions of ruby. I would like to help with this, if possible. Diogo Leal [aka estranho] http://diogoleal.com msn | gtalk: estranho at diogoleal.com On Fri, Mar 18, 2011 at 12:11 PM, Niels Horn wrote: > On Fri, Mar 18, 2011 at 11:59 AM, Marco Bonetti wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hello all, >> I'm working on a complete puppet setup for Slackware. I'm going to >> submit my work to SlackBuilds.org, however it will not happen soon as >> puppet still requires ruby 1.8, so I had to prepare a workaround for this. >> In the meanwhile, may I ask to reserve these values: >> >> puppet >> ======= >> User: ? puppet ?UID: 249 ? ? ? ?GID: 249 >> Group: ?puppet ? ? ? ? ? ? ? ? ?GID: 249 >> >> this will greatly help me so I will not have to chase any changes to >> http://slackbuilds.org/uid_gid.txt >> >> If you are interested in the project, you will be able to track changes >> and contribute over at https://github.com/sid77/puppet-slackware >> >> Thanks! >> >> - -- >> Marco Bonetti > > OK, done. > > -- > 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/ > > From sid77 at slackware.it Fri Mar 18 17:01:20 2011 From: sid77 at slackware.it (Marco Bonetti) Date: Fri, 18 Mar 2011 18:01:20 +0100 Subject: [Slackbuilds-users] Puppet (and more!) for Slackware In-Reply-To: References: <4D83733F.1080105@slackware.it> Message-ID: <4D838FE0.8070909@slackware.it> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/18/2011 05:58 PM, Diogo Leal wrote: > Hi, > I'm also working with the puppet and suffered with the problem of version. eh, I know :) > I am using to manage rvm versions of ruby. nice one, but I'd like to use something more system-specific > I would like to help with this, if possible. feel free to fork and contribute :) - -- Marco Bonetti Tor research and other stuff: http://sid77.slackware.it/ Slackintosh Linux Project Developer: http://workaround.ch/ Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/ My GnuPG key id: 0x0B60BC5F -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2Dj+AACgkQTYvJ9gtgvF9iPwCgpgnaI0PkbI0vUHlsUlZz83qy 8j4AnjpH0YuXh38coRybpL7PcGsi9SdI =I2s1 -----END PGP SIGNATURE----- From matteo.bernardini at gmail.com Fri Mar 18 17:17:28 2011 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 18 Mar 2011 18:17:28 +0100 Subject: [Slackbuilds-users] Puppet (and more!) for Slackware In-Reply-To: <4D83733F.1080105@slackware.it> References: <4D83733F.1080105@slackware.it> Message-ID: <4D8393A8.60900@gmail.com> Il 18/03/2011 15:59, Marco Bonetti ha scritto: > I'm working on a complete puppet setup for Slackware. I'm going to > submit my work to SlackBuilds.org, however it will not happen soon as > puppet still requires ruby 1.8, so I had to prepare a workaround for this. I'm interested a lot in that and will surely have a look, tnx marco :) btw fyi, I'm happily using redmine on l33t with vincent's 1.8 packages (they should be able to live together with the 1.9 version) http://cardinal.lizella.net/~vbatts/downloads/updates/ruby/ http://cardinal.lizella.net/~vbatts/downloads/ Matteo From joshuakwood at gmail.com Fri Mar 18 18:12:20 2011 From: joshuakwood at gmail.com (JK Wood) Date: Fri, 18 Mar 2011 13:12:20 -0500 Subject: [Slackbuilds-users] Puppet (and more!) for Slackware In-Reply-To: <4D838FE0.8070909@slackware.it> References: <4D83733F.1080105@slackware.it> <4D838FE0.8070909@slackware.it> Message-ID: On Fri, Mar 18, 2011 at 12:01 PM, Marco Bonetti wrote: > nice one, but I'd like to use something more system-specific > > I'm usually against one-size-fits-all solutions, but rvm is the cleanest one I've seen in a long time. Slackware handles Ruby in a far better way than any other distro I've encountered, but rvm is still an extremely useful tool. I only wish it were provided such that packaging was a simple matter. -JK -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas at beingboiled.info Tue Mar 22 13:47:55 2011 From: thomas at beingboiled.info (Thomas Morper) Date: Tue, 22 Mar 2011 14:47:55 +0100 Subject: [Slackbuilds-users] Exim 4.74 download link Message-ID: <20110322134755.GA18850@arktinen> Exim 4.75 has just been released which means that the download link to 4.74 is broken now. Can one of the admins please edit the exim.info file and make it point to the source's new location at: ftp://ftp.exim.org/pub/exim/exim4/old/exim-4.74.tar.bz2 Exim 4.74 is safe to use and will happily run on slackware-current. I'll submit an update for Exim 4.75 once Slackware 13.37 is ready. -- http://beingboiled.info/slackware/ From willysr at gmail.com Wed Mar 23 12:49:32 2011 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Wed, 23 Mar 2011 19:49:32 +0700 Subject: [Slackbuilds-users] GConf and GORbit Message-ID: Hi, GConf and GORbit are now included in -Current, so i guess it can be deleted from SBo ? -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From spledger91 at yahoo.com Wed Mar 23 21:12:46 2011 From: spledger91 at yahoo.com (Steven Ste) Date: Wed, 23 Mar 2011 14:12:46 -0700 (PDT) Subject: [Slackbuilds-users] flash-player-plugin - 32-Bit download link is dead Message-ID: <173828.36476.qm@web120608.mail.ne1.yahoo.com> Hi, the 32-Bit download link for flash-player-plugin appears to be broken. -Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: From volkerdi at slackware.com Thu Mar 24 04:59:05 2011 From: volkerdi at slackware.com (Patrick J. Volkerding) Date: Wed, 23 Mar 2011 23:59:05 -0500 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: References: Message-ID: <4D8ACF99.50202@slackware.com> On 03/23/2011 07:49 AM, Willy Sudiarto Raharjo wrote: > Hi, > > GConf and GORbit are now included in -Current, so i guess it can be > deleted from SBo ? I'm not so sure that they should be. I mean, I did try to hide them a bit -- they aren't just directory in /extra. Maybe there should be a differently named directory than /extra for things like GConf and ORBit2. I'll leave the name of such a directory as an exercise for the reader. From willysr at gmail.com Thu Mar 24 05:48:13 2011 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Thu, 24 Mar 2011 12:48:13 +0700 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: <4D8ACF99.50202@slackware.com> References: <4D8ACF99.50202@slackware.com> Message-ID: > I'm not so sure that they should be. ?I mean, I did try to hide them a bit > -- they aren't just directory in /extra. ?Maybe there should be a > differently named directory than /extra for things like GConf and ORBit2. > > I'll leave the name of such a directory as an exercise for the reader. contrib ? -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From higuita at GMX.net Thu Mar 24 09:29:41 2011 From: higuita at GMX.net (higuita) Date: Thu, 24 Mar 2011 09:29:41 +0000 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: <4D8ACF99.50202@slackware.com> References: <4D8ACF99.50202@slackware.com> Message-ID: <20110324092941.6eef3df3@Couracado.homelinux.net> > I'll leave the name of such a directory as an exercise for the reader. slackbuilds :? higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From chris.abela at maltats.com Thu Mar 24 10:53:48 2011 From: chris.abela at maltats.com (Chris Abela) Date: Thu, 24 Mar 2011 11:53:48 +0100 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: <20110324092941.6eef3df3@Couracado.homelinux.net> Message-ID: higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946 The community does not deserve this. The Nazi reference is unwarranted and insults the memory of victims of dictatorship. Chris Abela Ing. Christopher Abela B. Elec. Eng. (Hons) M.Sc. Eng (Malta) Senior Head Technical Services Malta Air Traffic Services Ltd. PO Box 1 Malta International Airport LQA 5000 Malta e-mail: chris.abela at maltats.com Please consider your environmental responsibility before printing this e-mail. Confidentiality Note: This message and any files transmitted with it may be legally privileged and is intended for the recipient/s to whom it is addressed. If you are not the intended recipient, please notify the sender by reply of mail and delete it and any attachment from your system. Any unauthorized use or disclosure of the content of this message is strictly prohibited and may be unlawful. Any views expressed in this message are those of the sender. -------------- next part -------------- An HTML attachment was scrubbed... URL: From joshuakwood at gmail.com Thu Mar 24 11:16:36 2011 From: joshuakwood at gmail.com (JK Wood) Date: Thu, 24 Mar 2011 06:16:36 -0500 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: References: <20110324092941.6eef3df3@Couracado.homelinux.net> Message-ID: On Thu, Mar 24, 2011 at 5:53 AM, Chris Abela wrote: > > > The community does not deserve this. The Nazi reference is unwarranted and > insults the memory of victims of dictatorship. > > > > Chris Abela > > > > > Chris - It's just a quote in an email signature, it has nothing to do with the present conversation. Much like the giant confidentiality notification on your outgoing email, or Willy's links in his. --JK -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.abela at maltats.com Thu Mar 24 12:00:55 2011 From: chris.abela at maltats.com (Chris Abela) Date: Thu, 24 Mar 2011 13:00:55 +0100 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: Message-ID: Chris - It's just a quote in an email signature, it has nothing to do with the present conversation. Much like the giant confidentiality notification on your outgoing email, or Willy's links in his. --JK higuita and All, I did not understand that it was a signature, thus I apologise for over-reacting. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From ml at mareichelt.com Thu Mar 24 17:43:52 2011 From: ml at mareichelt.com (markus reichelt) Date: Thu, 24 Mar 2011 18:43:52 +0100 Subject: [Slackbuilds-users] snappy Message-ID: <20110324174352.GL32638@pc21.mareichelt.com> Aloha, you might have heard of snappy (Google's compression/decompression library). It has been released recently and is licensed under the Apache license, version 2.0: http://code.google.com/p/snappy/ In case you want to try it check my slackbuild (13.1/-current) @ http://mareichelt.de/tmp/snappy.tar.gz -- left blank, right bald -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From t3slider at gmail.com Thu Mar 24 18:46:18 2011 From: t3slider at gmail.com (T3slider) Date: Thu, 24 Mar 2011 14:46:18 -0400 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: <4D8ACF99.50202@slackware.com> References: <4D8ACF99.50202@slackware.com> Message-ID: <20110324184618.GA2780@KeithPC.phub.net.cable.rogers.com> On Wed, Mar 23, 2011 at 11:59:05PM -0500, Patrick J. Volkerding wrote: > I'm not so sure that they should be. I mean, I did try to hide them a > bit -- they aren't just directory in /extra. Maybe there should be a > differently named directory than /extra for things like GConf and ORBit2. > > I'll leave the name of such a directory as an exercise for the reader. I'm not sure how well an 'expletive' directory would go over with the Slackware faithful... From ml at mareichelt.com Thu Mar 24 19:09:17 2011 From: ml at mareichelt.com (markus reichelt) Date: Thu, 24 Mar 2011 20:09:17 +0100 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: <20110324184618.GA2780@KeithPC.phub.net.cable.rogers.com> References: <4D8ACF99.50202@slackware.com> <20110324184618.GA2780@KeithPC.phub.net.cable.rogers.com> Message-ID: <20110324190917.GM32638@pc21.mareichelt.com> * T3slider wrote: > I'm not sure how well an 'expletive' directory would go over with > the Slackware faithful... lost+found -- left blank, right bald -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From josiahb at gmail.com Thu Mar 24 19:34:46 2011 From: josiahb at gmail.com (Josiah Boothby) Date: Thu, 24 Mar 2011 12:34:46 -0700 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: <20110324184618.GA2780@KeithPC.phub.net.cable.rogers.com> References: <4D8ACF99.50202@slackware.com> <20110324184618.GA2780@KeithPC.phub.net.cable.rogers.com> Message-ID: <20110324123446.4bfbf09a@strega.troglophonic.org> > > I'll leave the name of such a directory as an exercise for the > > reader. > > I'm not sure how well an 'expletive' directory would go over with the > Slackware faithful... Given the etymology of the word 'expletive', that would be a great word to use for software that fills out a hole that might otherwise be preferred left unoccupied... -- Josiah Boothby josiahb at gmail.com http://josiahboothby.org 206-427-8588 From ml at mareichelt.com Thu Mar 24 20:11:19 2011 From: ml at mareichelt.com (markus reichelt) Date: Thu, 24 Mar 2011 21:11:19 +0100 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: <20110324123446.4bfbf09a@strega.troglophonic.org> References: <4D8ACF99.50202@slackware.com> <20110324184618.GA2780@KeithPC.phub.net.cable.rogers.com> <20110324123446.4bfbf09a@strega.troglophonic.org> Message-ID: <20110324201119.GN32638@pc21.mareichelt.com> * Josiah Boothby wrote: > Given the etymology of the word 'expletive', that would be a great > word to use for software that fills out a hole that might otherwise > be preferred left unoccupied... I just hope theres gonna be a new section in CHANGES_AND_HINTS.TXT about such foo, going into detail about whatnot. Just like Nobel Peace Prizes in politics. "Barack Obama has now fired more cruise missiles than all other Nobel Peace prize winners combined" -- http://www.fark.com/politics/ (scnr) -- left blank, right bald -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From pwcazenave at gmail.com Thu Mar 24 22:39:51 2011 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Thu, 24 Mar 2011 22:39:51 +0000 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: <20110324201119.GN32638@pc21.mareichelt.com> References: <4D8ACF99.50202@slackware.com> <20110324184618.GA2780@KeithPC.phub.net.cable.rogers.com> <20110324123446.4bfbf09a@strega.troglophonic.org> <20110324201119.GN32638@pc21.mareichelt.com> Message-ID: <4D8BC837.4030009@gmail.com> On 24/03/2011 20:11, markus reichelt wrote: > * Josiah Boothby wrote: > >> Given the etymology of the word 'expletive', that would be a great >> word to use for software that fills out a hole that might otherwise >> be preferred left unoccupied... > > I just hope theres gonna be a new section in CHANGES_AND_HINTS.TXT > about such foo, going into detail about whatnot. > > Just like Nobel Peace Prizes in politics. > > "Barack Obama has now fired more cruise missiles than all other Nobel > Peace prize winners combined" -- http://www.fark.com/politics/ (scnr) > > > > > _______________________________________________ > 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/ > Probably worthwhile mentioning that as National Security Advisor to President Nixon, Nobel Peace Prize winner Henry Kissinger dropped 2.7 million tons of bombs over Cambodia (http://en.wikipedia.org/wiki/Operation_Menu). From atyrelyoung at gmail.com Fri Mar 25 00:28:32 2011 From: atyrelyoung at gmail.com (Adam Young) Date: Thu, 24 Mar 2011 17:28:32 -0700 Subject: [Slackbuilds-users] google-chrome Message-ID: So I awoke from my away time from the internet to discover google-chrome in extra, nearly the same SlackBuild we have been using for some time. There was also the addition of obviously needed dependencies that are not included in stock slackware, which Pat has generously provided in the chrome directory in /extra. I personally am a developer channel user, which for those unfamiliar is the next cycle development for chrome. The problem here is that in chrome 11.x PAM is now a dependency. Fortunately it doesn't need to be system wide, and as such I have attached a modified version of the SlackBuild now available in current, with the changes I have made to make my dev channel version work. Static building of the PAM lib is not the most elegant solution, but until upstream adds a switch ignore the need for PAM it would appear to be the only real solution. The main reason I bring this up, is because the move to chrome 11 code in chrome stable looms on the horizon, and will break the /extra SlackBuild. Pat, chrome slackbuild maintainers, and/or sbo admins feel free to use/modify as they see fit. Regards, atyoung -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: google-chrome.SlackBuild Type: application/octet-stream Size: 5505 bytes Desc: not available URL: From jedi.kenjiro at gmail.com Fri Mar 25 03:42:45 2011 From: jedi.kenjiro at gmail.com (Yucatan "Kenjiro" Costa) Date: Fri, 25 Mar 2011 00:42:45 -0300 Subject: [Slackbuilds-users] google-chrome In-Reply-To: References: Message-ID: Interesting... Why would we possibly have a PAM dependent software in extra when we can have one that doensn't depend on it? I am not here to say PAM is worthless or not. But since Slackware tradition is not to use PAM... ;) Not to mention we can have google-chrome/chromium running without the need of some other dependencies like Orbit2 or Gconf. And...are we already rid of that 'jpeg upload' bug on this version of google-chrome? Please, I am not bashing the good work you guys (Adam, Erik and Patrick) have done so far. I know you guys do what can be done and I aplaud you for that. On Thu, Mar 24, 2011 at 9:28 PM, Adam Young wrote: > So I awoke from my away time from the internet to discover google-chrome in > extra, nearly the same SlackBuild we have been using for some time. There > was also the addition of obviously needed dependencies that are not included > in stock slackware, which Pat has generously provided in the chrome > directory in /extra. > > I personally am a developer channel user, which for those unfamiliar is the > next cycle development for chrome. The problem here is that in chrome 11.x > PAM is now a dependency. Fortunately it doesn't need to be system wide, and > as such I have attached a modified version of the SlackBuild now available > in current, with the changes I have made to make my dev channel version > work. > > Static building of the PAM lib is not the most elegant solution, but until > upstream adds a switch ignore the need for PAM it would appear to be the > only real solution. The main reason I bring this up, is because the move to > chrome 11 code in chrome stable looms on the horizon, and will break the > /extra SlackBuild. > > Pat, chrome slackbuild maintainers, and/or sbo admins feel free to > use/modify as they see fit. > > Regards, > > atyoung > > _______________________________________________ > 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/ > > > -- May the Force be with you! Yucatan "Kenjiro" Costa -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Fri Mar 25 03:56:24 2011 From: erik at slackbuilds.org (Erik Hanson) Date: Thu, 24 Mar 2011 22:56:24 -0500 Subject: [Slackbuilds-users] google-chrome In-Reply-To: References: Message-ID: <20110324225624.552527a2@shaggy.doo> On Fri, 25 Mar 2011 00:42:45 -0300 "Yucatan \"Kenjiro\" Costa" wrote: > Not to mention we can have google-chrome/chromium running without the > need of some other dependencies like Orbit2 or Gconf. Repackaging the debian binary will continue to require these, and eventually will require PAM as well. I confirmed this recently by trying the unstable channel, at the time was 11.0. The only answer I can really think of here is to include some sort of pam-solibs type package along with ORBit2/GConf. This is not a task I wish to undertake, however. These days I simply compile chromium using your script. :) -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From chaos.proton at gmail.com Fri Mar 25 05:36:59 2011 From: chaos.proton at gmail.com (Grissiom) Date: Fri, 25 Mar 2011 13:36:59 +0800 Subject: [Slackbuilds-users] google-chrome In-Reply-To: <20110324225624.552527a2@shaggy.doo> References: <20110324225624.552527a2@shaggy.doo> Message-ID: On Fri, Mar 25, 2011 at 11:56 AM, Erik Hanson wrote: > On Fri, 25 Mar 2011 00:42:45 -0300 > "Yucatan \"Kenjiro\" Costa" wrote: > >> Not to mention we can have google-chrome/chromium running without the >> need of some other dependencies like Orbit2 or Gconf. > > Repackaging the debian binary will continue to require these, and > eventually will require PAM as well. Yes, I think it will happen sooner or later. > I confirmed this recently by trying the unstable channel, at the time was 11.0. The only answer I > can really think of here is to include some sort of pam-solibs type > package along with ORBit2/GConf. This is not a task I wish to > undertake, however. These days I simply compile chromium using your > script. :) > I think Slackware may include a fully functional PAM in the next release after 13.37(may be 14 or 14.xx?). As time goes by, PAM is more and more mature and is not the one years ago. Lots of distro have PAM and it is well tested in some degree. If we have PAM, building KDE might be easier too. -- Cheers, Grissiom From mfilpot at gmail.com Fri Mar 25 06:01:26 2011 From: mfilpot at gmail.com (Matthew Fillpot) Date: Fri, 25 Mar 2011 02:01:26 -0400 Subject: [Slackbuilds-users] google-chrome In-Reply-To: References: <20110324225624.552527a2@shaggy.doo> Message-ID: On Fri, Mar 25, 2011 at 1:36 AM, Grissiom wrote: > I think Slackware may include a fully functional PAM in the next > release after 13.37(may be 14 or 14.xx?). As time goes by, PAM is more > and more mature and is not the one years ago. Lots of distro have PAM > and it is well tested in some degree. If we have PAM, building KDE > might be easier too. I was thinking the same thing, that based upon the recent history it may be a good time to consider including PAM and potentially selinux. I am planning to build a collection of slackbuild scripts after the release of 13.37 to attempt to get PAM and selinux working on a fresh build, hopefully that information can be used to test for future possible inclusions. From volkerdi at slackware.com Fri Mar 25 06:29:21 2011 From: volkerdi at slackware.com (Patrick J. Volkerding) Date: Fri, 25 Mar 2011 01:29:21 -0500 Subject: [Slackbuilds-users] google-chrome In-Reply-To: References: <20110324225624.552527a2@shaggy.doo> Message-ID: <4D8C3641.5010108@slackware.com> On 03/25/2011 01:01 AM, Matthew Fillpot wrote: > I was thinking the same thing, that based upon the recent history it > may be a good time to consider including PAM and potentially selinux. > I am planning to build a collection of slackbuild scripts after the > release of 13.37 to attempt to get PAM and selinux working on a fresh > build, hopefully that information can be used to test for future > possible inclusions. It may be a good time to consider PAM sometime after this release, but it's almost never a good time for selinux. Pat From willysr at gmail.com Fri Mar 25 06:49:28 2011 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Fri, 25 Mar 2011 13:49:28 +0700 Subject: [Slackbuilds-users] google-chrome In-Reply-To: <4D8C3641.5010108@slackware.com> References: <20110324225624.552527a2@shaggy.doo> <4D8C3641.5010108@slackware.com> Message-ID: > It may be a good time to consider PAM sometime after this release, but it's > almost never a good time for selinux. I agree... most application must be tweaked in order to work with SELinux -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From mfilpot at gmail.com Fri Mar 25 07:24:50 2011 From: mfilpot at gmail.com (Matthew Fillpot) Date: Fri, 25 Mar 2011 03:24:50 -0400 Subject: [Slackbuilds-users] google-chrome In-Reply-To: References: <20110324225624.552527a2@shaggy.doo> <4D8C3641.5010108@slackware.com> Message-ID: On Fri, Mar 25, 2011 at 2:49 AM, Willy Sudiarto Raharjo wrote: >> It may be a good time to consider PAM sometime after this release, but it's >> almost never a good time for selinux. > > I agree... > most application must be tweaked in order to work with SELinux I can see your point, SELinux does add some painful complexity that does not correspond with the simplicity of Slackware. However I will separate my efforts into two parts, adding full PAM support and then adding SELlinux on top of PAM, both actions will be performed for me to better understand the core libraries and necessary modifications. The two actions will be separated in my scripts so that the information is available for anyone who wishes to undertake the same painful processes. I don't expect my actions to lead back to the official Slackware or Slackbuilds projects due to the need to modify official packages, however I always welcome others to expand upon my work to fulfill their needs. Now I only need to wait for the official release or 13.37 before I begin my project. Back to the subject, the potential inclusion of PAM support on future releases will definitely assist to simplify building of google-chome and other applications, including using alternate authentication functions which correspond to my personal uses and goals. Thank you all for considering this option. -- -Thank You, -Matthew Fillpot From jens at tuxane.com Fri Mar 25 08:26:42 2011 From: jens at tuxane.com (TuxaneMedia) Date: Fri, 25 Mar 2011 09:26:42 +0100 Subject: [Slackbuilds-users] google-chrome In-Reply-To: <4D8C3641.5010108@slackware.com> References: <20110324225624.552527a2@shaggy.doo> <4D8C3641.5010108@slackware.com> Message-ID: <4D8C51C2.1090507@tuxane.com> Am 25.03.2011 07:29, schrieb Patrick J. Volkerding: > but it's almost never a good time for selinux. I agree absolutely, I wouldn't like Selinux to go into Slackware. I can live perfectly without it -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.abela at maltats.com Fri Mar 25 12:23:34 2011 From: chris.abela at maltats.com (Chris Abela) Date: Fri, 25 Mar 2011 13:23:34 +0100 Subject: [Slackbuilds-users] google-chrome In-Reply-To: <4D8C3641.5010108@slackware.com> Message-ID: It may be a good time to consider PAM sometime after this release, but it's almost never a good time for selinux. Pat I needed to re-built open-ldap and samba against PAM, and so I had written my own SlackBuild. Someone might find the attachment useful, even if it was straight-forward. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Linux-PAM.tar.gz Type: application/x-gzip Size: 2992 bytes Desc: not available URL: From pfeifer.felix at googlemail.com Fri Mar 25 12:48:34 2011 From: pfeifer.felix at googlemail.com (Felix Pfeifer) Date: Fri, 25 Mar 2011 13:48:34 +0100 Subject: [Slackbuilds-users] google-chrome In-Reply-To: References: <4D8C3641.5010108@slackware.com> Message-ID: Voice of a user: ^^ My choice for Slackware was because it doesn't use PAM or selinux. There are a lot of distros using it and if i wanted PAM or selinux i would use these distros, like Fedora which also has 32bit compat packages for the 64bit version. However - i use Slackware. From schultzter at gmail.com Fri Mar 25 12:59:21 2011 From: schultzter at gmail.com (Eric Schultz) Date: Fri, 25 Mar 2011 08:59:21 -0400 Subject: [Slackbuilds-users] google-chrome Message-ID: > And...are we already rid of that 'jpeg upload' bug on this version of google-chrome? I'm pretty sure this was a library version issue - can't remember which right now. But still, getting it resolved would be AWESOME!!! I know the re-packaged deb ends up installing to /opt so would it be as easy as adding the version of the JPEG library that Chrome depends on into Chrome's bin directory? Or a sibling lib directory that's earlier on Chrome's LIBPATH? (Hopefully that last paragraph makes sense - I'm neither in front of my Slackware computer at this point nor very experienced at this sort of thing) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozan.turkyilmaz at gmail.com Fri Mar 25 13:25:20 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Fri, 25 Mar 2011 15:25:20 +0200 Subject: [Slackbuilds-users] google-chrome In-Reply-To: References: Message-ID: 2011/3/25 Eric Schultz > > >?And...are we already rid of that 'jpeg upload' bug on this version of google-chrome? > I'm pretty sure this was a library version issue - can't remember which right now. ?But still, getting it resolved would be AWESOME!!! > I know the re-packaged deb ends up installing to /opt so would it be as easy as adding the version of the JPEG library that Chrome depends on into Chrome's bin directory? ?Or a sibling lib directory that's earlier on Chrome's LIBPATH? > (Hopefully that last paragraph makes sense - I'm neither in front of my Slackware computer at this point nor very experienced at this sort of thing) ?Similar to Firefox, It uses wrapper script to set LIBPATH accordingly so it uses bumbled libraries instead of system ones. -- Ozan, BSc, BEng From didier.spaier at epsm.fr Fri Mar 25 13:30:16 2011 From: didier.spaier at epsm.fr (Didier Spaier) Date: Fri, 25 Mar 2011 14:30:16 +0100 Subject: [Slackbuilds-users] google-chrome In-Reply-To: References: <4D8C3641.5010108@slackware.com> Message-ID: <4D8C98E8.3030600@epsm.fr> Le 25/03/2011 13:48, Felix Pfeifer a ?crit : > Voice of a user: ^^ > My choice for Slackware was because it doesn't > use PAM or selinux. There are a lot of distros using > it and if i wanted PAM or selinux i would use these > distros, like Fedora which also has 32bit compat > packages for the 64bit version. However - i use > Slackware. Voice of another user: ^^ Well, at present PAM would be of no use to me, aside being able to use my Thinkpad's fingerprint reader, which I consider a somehow cosmetic issue. But I would not object it to be shipped with Slackware, provided I can choose to enable/disable it, e.g. chmod (+||-)x /etc/rc.d/rc.PAM. I would not object either google-chrome being built --without-pam if possible, nor built with PAM statically linked if possible. Though "comparaison n'est pas raison" I am happy with Eric's package for VLC wich include all needed dependencies. Didier From erik at slackbuilds.org Fri Mar 25 14:21:48 2011 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 25 Mar 2011 09:21:48 -0500 Subject: [Slackbuilds-users] google-chrome In-Reply-To: <4D8C98E8.3030600@epsm.fr> References: <4D8C3641.5010108@slackware.com> <4D8C98E8.3030600@epsm.fr> Message-ID: <20110325092148.172660a1@shaggy.doo> On Fri, 25 Mar 2011 14:30:16 +0100 Didier Spaier wrote: > I would not object either google-chrome being built --without-pam if > possible, nor built with PAM statically linked if possible. The SlackBuild does not build google-chrome, it repackages a binary that Google builds, and they are unlikely to disable the PAM requirement. The chromium SlackBuild however, we have currently building without PAM or GConf/ORBit2 dependencies. This script should be available in the 13.37 repo when it goes live. It is also available here: https://github.com/yucatan/chromium -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From erik at slackbuilds.org Fri Mar 25 14:51:50 2011 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 25 Mar 2011 09:51:50 -0500 Subject: [Slackbuilds-users] google-chrome In-Reply-To: References: Message-ID: <20110325095150.2a723165@shaggy.doo> On Fri, 25 Mar 2011 08:59:21 -0400 Eric Schultz wrote: > > And...are we already rid of that 'jpeg upload' bug on this version > > of > google-chrome? > > I'm pretty sure this was a library version issue - can't remember > which right now. But still, getting it resolved would be AWESOME!!! > > I know the re-packaged deb ends up installing to /opt so would it be > as easy as adding the version of the JPEG library that Chrome depends > on into Chrome's bin directory? Or a sibling lib directory that's > earlier on Chrome's LIBPATH? I could be wrong about this, it's been a while since I've dug through the bug reports. The crash happens in the GTK file selector dialog. google-chrome is linked against libjpeg.so.62 and GTK is linked against libjpeg.so.8. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From didier.spaier at epsm.fr Fri Mar 25 14:58:31 2011 From: didier.spaier at epsm.fr (Didier Spaier) Date: Fri, 25 Mar 2011 15:58:31 +0100 Subject: [Slackbuilds-users] google-chrome In-Reply-To: <20110325092148.172660a1@shaggy.doo> References: <4D8C3641.5010108@slackware.com> <4D8C98E8.3030600@epsm.fr> <20110325092148.172660a1@shaggy.doo> Message-ID: <4D8CAD97.5020301@epsm.fr> Le 25/03/2011 15:21, Erik Hanson a ?crit : > On Fri, 25 Mar 2011 14:30:16 +0100 > Didier Spaier wrote: > >> I would not object either google-chrome being built --without-pam if >> possible, nor built with PAM statically linked if possible. > > The SlackBuild does not build google-chrome, it repackages a binary > that Google builds, and they are unlikely to disable the PAM > requirement. The chromium SlackBuild however, we have currently > building without PAM or GConf/ORBit2 dependencies. This script should > be available in the 13.37 repo when it goes live. It is also available > here: > https://github.com/yucatan/chromium > I'll give it a try then, thanks Erik Didier Spaier From ozan.turkyilmaz at gmail.com Fri Mar 25 23:09:32 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 26 Mar 2011 01:09:32 +0200 Subject: [Slackbuilds-users] libcap-ng and prelink Message-ID: Attached patch fixes the problem of libcap-ng.MlackBuild. It's in the end a simple version bump. prelink fails to builds because it need static libelf. 13.37 rc3 version doesnot include static versions of libelf. -- Ozan, BSc, BEng From rworkman at slackbuilds.org Fri Mar 25 23:18:18 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 25 Mar 2011 18:18:18 -0500 Subject: [Slackbuilds-users] libcap-ng and prelink In-Reply-To: References: Message-ID: <20110325181818.4c187864@liberty.rlwhome.lan> On Sat, 26 Mar 2011 01:09:32 +0200 Ozan T?rky?lmaz wrote: > Attached patch fixes the problem of libcap-ng.MlackBuild. It's in the > end a simple version bump. > prelink fails to builds because it need static libelf. 13.37 rc3 > version doesnot include static versions of libelf. You forgot the attachment :-) -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Mar 28 01:13:42 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 27 Mar 2011 20:13:42 -0500 Subject: [Slackbuilds-users] rtorrent on slackware -current / 13.37 In-Reply-To: <20110310232140.GA10471@skamandros.andrews-corner.org> References: <20110310232140.GA10471@skamandros.andrews-corner.org> Message-ID: <20110327201342.0412cd48@liberty.rlwhome.lan> On Fri, 11 Mar 2011 10:21:40 +1100 andrew wrote: > Looks like rtorrent requires a small patch to compile against the new > ncurses in the upcoming 13.37 release: > > http://www.linuxquestions.org/questions/slackware-14/update-to-current-rtorrent-throws-error-wont-start-867779/ I just pushed this to my git branch. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Mar 28 01:15:40 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 27 Mar 2011 20:15:40 -0500 Subject: [Slackbuilds-users] Exim 4.74 download link In-Reply-To: <20110322134755.GA18850@arktinen> References: <20110322134755.GA18850@arktinen> Message-ID: <20110327201540.0617942b@liberty.rlwhome.lan> On Tue, 22 Mar 2011 14:47:55 +0100 Thomas Morper wrote: > Exim 4.75 has just been released which means that the download link to > 4.74 is broken now. Can one of the admins please edit the exim.info > file and make it point to the source's new location at: > > ftp://ftp.exim.org/pub/exim/exim4/old/exim-4.74.tar.bz2 I just pushed this to my git branch. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Mon Mar 28 01:20:28 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 27 Mar 2011 20:20:28 -0500 Subject: [Slackbuilds-users] 13.37rc1 and my slackbuilds In-Reply-To: <20110315211602.GC18300@linuxbox.fi> References: <20110315211602.GC18300@linuxbox.fi> Message-ID: <20110327202028.5b428006@liberty.rlwhome.lan> On Tue, 15 Mar 2011 23:16:02 +0200 Mikko Varri wrote: > I know you (admins) didn't ask for it, but since I've built them, I > thought I'd let you know: all the SlackBuilds that I maintain, and > their dependencies, seem to work without any changes on 13.37rc1. > [snipped long list] Thanks; all of these passed XGizzmo's smoke test 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 sid77 at slackware.it Mon Mar 28 12:14:10 2011 From: sid77 at slackware.it (Marco Bonetti) Date: Mon, 28 Mar 2011 14:14:10 +0200 Subject: [Slackbuilds-users] Slackintosh 12.1 - in sync again Message-ID: <4D907B92.3030301@slackware.it> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody! I'm uploading a batch of updates to Slackintosh 12.1 right now, they should bring the stable distribution fully in sync with Slackware 12.1. Ciao, Marco - -- Marco Bonetti Tor research and other stuff: http://sid77.slackware.it/ Slackintosh Linux Project Developer: http://workaround.ch/ Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/ My GnuPG key id: 0x0B60BC5F -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2Qe5EACgkQTYvJ9gtgvF8I1gCePyWVv99ymTXjW5J7OcGuMyGT dwQAn0G2j8mVxwoJl5hYH9XBuHZUSMj9 =7H7l -----END PGP SIGNATURE----- From sid77 at slackware.it Mon Mar 28 17:30:49 2011 From: sid77 at slackware.it (Marco Bonetti) Date: Mon, 28 Mar 2011 19:30:49 +0200 Subject: [Slackbuilds-users] Slackintosh 12.1 - in sync again In-Reply-To: <4D907B92.3030301@slackware.it> References: <4D907B92.3030301@slackware.it> Message-ID: <4D90C5C9.2060408@slackware.it> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oh crap... sorry for the spam, folks: I misread thunderbird autocomplete and sent the announce letter to the wrong address. I've really got too many slack* addresses in my inbox ;-) - -- Marco Bonetti Tor research and other stuff: http://sid77.slackware.it/ Slackintosh Linux Project Developer: http://workaround.ch/ Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/ My GnuPG key id: 0x0B60BC5F -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2QxckACgkQTYvJ9gtgvF8pBwCgksplh/cWAZdU9GoAUpKbjRNG DsUAn1ip0Bcw/SrOzvJI8FP3PEgT/+eu =80Fu -----END PGP SIGNATURE----- From vmj at linuxbox.fi Mon Mar 28 22:21:23 2011 From: vmj at linuxbox.fi (Mikko Varri) Date: Tue, 29 Mar 2011 01:21:23 +0300 Subject: [Slackbuilds-users] libraries/gaphas: source disappeared. Message-ID: <20110328222123.GG18300@linuxbox.fi> Hi, A day or two ago gaphas was updated, and for some reason old source tarball was removed. A simple update[1] fixes this. [1] https://github.com/vmj/slackbuilds/commit/f8b393694deb94729bc507376f455eefec8da8e5 This affects 13.1 and master branches. If you would like, you can cherry-pick it: git remote add -t gaphas -f gaphas git://github.com/vmj/slackbuilds git cherry-pick -s f8b393694deb94729bc507376f455eefec8da8e5 git remote rm gaphas Or you can ignore this and I'll submit an update when the form opens. (gaphor, which is the only one requiring this lib, is fine with the new version.) -vmj From rworkman at slackbuilds.org Mon Mar 28 22:53:47 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 28 Mar 2011 17:53:47 -0500 Subject: [Slackbuilds-users] libraries/gaphas: source disappeared. In-Reply-To: <20110328222123.GG18300@linuxbox.fi> References: <20110328222123.GG18300@linuxbox.fi> Message-ID: <20110328175347.50c1e350@liberty.rlwhome.lan> On Tue, 29 Mar 2011 01:21:23 +0300 Mikko Varri wrote: > A day or two ago gaphas was updated, and for some reason old source > tarball was removed. A simple update[1] fixes this. > > [1] > https://github.com/vmj/slackbuilds/commit/f8b393694deb94729bc507376f455eefec8da8e5 > > This affects 13.1 and master branches. If you would like, you can > cherry-pick it: > > git remote add -t gaphas -f gaphas git://github.com/vmj/slackbuilds > git cherry-pick -s f8b393694deb94729bc507376f455eefec8da8e5 > git remote rm gaphas > > Or you can ignore this and I'll submit an update when the form opens. > > (gaphor, which is the only one requiring this lib, is fine with the > new version.) Committed to my branch in git; 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 Mar 29 04:59:27 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 28 Mar 2011 23:59:27 -0500 Subject: [Slackbuilds-users] Abandoning some scripts... Message-ID: <20110328235927.2be2ac6a@liberty.rlwhome.lan> Unless someone wants to take over maintenance, I'm planning to remove the following builds (all mine) from the repo before we open things up for 13.37: * desktop/xfce4-cpugraph-plugin - xfce4-systemload-plugin handles this and more * desktop/xfce4-fsguard-plugin * desktop/xfce4-time-out-plugin * desktop/xfce4-timer-plugin * desktop/xfce4-wavelan-plugin - I personally don't see the usefulness of these * system/cdfs - I don't use this, and I don't remember why I even made a build for it... If you want any of these, reply to this mail with your desired MAINTAINER and EMAIL values, and I'll transfer it to you. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Tue Mar 29 06:33:25 2011 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 28 Mar 2011 23:33:25 -0700 Subject: [Slackbuilds-users] GConf and GORbit In-Reply-To: <4D8ACF99.50202@slackware.com> References: <4D8ACF99.50202@slackware.com> Message-ID: On Wed, Mar 23, 2011 at 9:59 PM, Patrick J. Volkerding < volkerdi at slackware.com> wrote: > On 03/23/2011 07:49 AM, Willy Sudiarto Raharjo wrote: > >> Hi, >> >> GConf and GORbit are now included in -Current, so i guess it can be >> deleted from SBo ? >> > > I'm not so sure that they should be. I mean, I did try to hide them a bit > -- they aren't just directory in /extra. Maybe there should be a > differently named directory than /extra for things like GConf and ORBit2. > > I'll leave the name of such a directory as an exercise for the reader. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > The one reason I haven't tried chrome is "GConf is a configuration database system, functionally similar to the Windows registry." And now I am convinced it should be purged from both Slackware and SBo. Anything mentioning "Windows Registry" gives me a rash in my nether regions. 'Twas Winders that drove me to Slackware... ...don't even get me started. -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From novalazy at gmail.com Tue Mar 29 07:21:07 2011 From: novalazy at gmail.com (Peter Wang) Date: Tue, 29 Mar 2011 18:21:07 +1100 Subject: [Slackbuilds-users] Abandoning some scripts... In-Reply-To: <20110328235927.2be2ac6a@liberty.rlwhome.lan> References: <20110328235927.2be2ac6a@liberty.rlwhome.lan> Message-ID: <20110329072107.GA17048@plug.localdomain> On 2011-03-28, Robby Workman wrote: > Unless someone wants to take over maintenance, I'm planning to > remove the following builds (all mine) from the repo before we > open things up for 13.37: > > * desktop/xfce4-cpugraph-plugin > - xfce4-systemload-plugin handles this and more I like the graph. MAINTAINER="Peter Wang" EMAIL="novalazy at gmail.com" From ozan.turkyilmaz at gmail.com Tue Mar 29 07:34:43 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Tue, 29 Mar 2011 10:34:43 +0300 Subject: [Slackbuilds-users] Abandoning some scripts... In-Reply-To: <20110328235927.2be2ac6a@liberty.rlwhome.lan> References: <20110328235927.2be2ac6a@liberty.rlwhome.lan> Message-ID: 2011/3/29 Robby Workman : > Unless someone wants to take over maintenance, I'm planning to > remove the following builds (all mine) from the repo before we > open things up for 13.37: > > * desktop/xfce4-cpugraph-plugin > ?- xfce4-systemload-plugin handles this and more I'll take systeload-plugin. I use it. -- Ozan, BSc, BEng From pwcazenave at gmail.com Tue Mar 29 10:35:28 2011 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Tue, 29 Mar 2011 11:35:28 +0100 Subject: [Slackbuilds-users] My SlackBuilds on -current. Message-ID: <4D91B5F0.1090607@gmail.com> I've tested my SlackBuilds and the following ones require no modification to run on -current as of 2011/03/28: cryptoki truecrypt netcdf synergy-plus temper CImg wxcam fdupes netcat rastertospp libav1394 libied61883 viking get_iplayer detox fish recorder These require only version bumps (see attached): GMT - from v4.5.5 to v4.5.6 x11vnc - from v0.9.10 to v0.9.12 The following two require new download locations, but otherwise build fine: flvstreamer - http://download.savannah.gnu.org/releases/flvstreamer/source/flvstreamer-2.1a.tar.gz motion - http://downloads.sourceforge.net/project/motion/motion%20-%203.2/3.2.12/motion-3.2.12.tar.gz I couldn't test midori because I couldn't get libproxy to build (even Ponce's one on github...) and therefore couldn't get webkitgtk to build. trash-cli built OK but won't run properly. Pierre -------------- next part -------------- A non-text attachment was scrubbed... Name: x11vnc.tar.bz2 Type: application/octet-stream Size: 2830 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: GMT.tar.bz2 Type: application/octet-stream Size: 4106 bytes Desc: not available URL: From matteo.bernardini at gmail.com Tue Mar 29 10:51:41 2011 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 29 Mar 2011 12:51:41 +0200 Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: <4D91B5F0.1090607@gmail.com> References: <4D91B5F0.1090607@gmail.com> Message-ID: <4D91B9BD.1050005@gmail.com> On 29/03/2011 12:35, Pierre Cazenave wrote: > I couldn't test midori because I couldn't get libproxy to build (even > Ponce's one on github...) and therefore couldn't get webkitgtk to build. I have built libsoup without libproxy support (should be optional), this way everything towards midori (0.3.3 compiles fine, just the last of $DOCS is missing) built smooth :) Matteo From matteo.bernardini at gmail.com Tue Mar 29 10:56:21 2011 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 29 Mar 2011 12:56:21 +0200 Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: <4D91B5F0.1090607@gmail.com> References: <4D91B5F0.1090607@gmail.com> Message-ID: <4D91BAD5.7080703@gmail.com> On 29/03/2011 12:35, Pierre Cazenave wrote: > I couldn't get libproxy to build FYI, I tried now with the updated (0.4.6) version on git master http://slackbuilds.org/gitweb/?p=slackbuilds.git;a=commitdiff;h=ac83402644da63bc7d8f362ae0961ab1d6e0e202 and builds fine on l33t. :) Matteo From rworkman at slackbuilds.org Tue Mar 29 11:11:14 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 29 Mar 2011 06:11:14 -0500 Subject: [Slackbuilds-users] Abandoning some scripts... In-Reply-To: References: <20110328235927.2be2ac6a@liberty.rlwhome.lan> Message-ID: <20110329061114.67f2f41e@liberty.rlwhome.lan> On Tue, 29 Mar 2011 10:34:43 +0300 Ozan T?rky?lmaz wrote: > 2011/3/29 Robby Workman : > > Unless someone wants to take over maintenance, I'm planning to > > remove the following builds (all mine) from the repo before we > > open things up for 13.37: > > > > * desktop/xfce4-cpugraph-plugin > > ?- xfce4-systemload-plugin handles this and more > > I'll take systeload-plugin. I use it. Well, actually I wasn't offering that one - I was explaining why I'm abandoning xfce4-cpugraph (because systemload does the same thing better IMHO). However, if you want it, you can certainly have it :-) -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 Mar 29 11:13:44 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 29 Mar 2011 06:13:44 -0500 Subject: [Slackbuilds-users] Abandoning some scripts... In-Reply-To: <20110329072107.GA17048@plug.localdomain> References: <20110328235927.2be2ac6a@liberty.rlwhome.lan> <20110329072107.GA17048@plug.localdomain> Message-ID: <20110329061344.26a88267@liberty.rlwhome.lan> On Tue, 29 Mar 2011 18:21:07 +1100 Peter Wang wrote: > On 2011-03-28, Robby Workman wrote: > > Unless someone wants to take over maintenance, I'm planning to > > remove the following builds (all mine) from the repo before we > > open things up for 13.37: > > > > * desktop/xfce4-cpugraph-plugin > > - xfce4-systemload-plugin handles this and more > > I like the graph. > > MAINTAINER="Peter Wang" > EMAIL="novalazy at gmail.com" Thanks; pushed to my git branch. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From lmello.009 at gmail.com Tue Mar 29 11:42:19 2011 From: lmello.009 at gmail.com (Luis Henrique F. Cardoso de Mello) Date: Tue, 29 Mar 2011 08:42:19 -0300 Subject: [Slackbuilds-users] LibreOffice broken link In-Reply-To: <20110329061344.26a88267@liberty.rlwhome.lan> References: <20110328235927.2be2ac6a@liberty.rlwhome.lan> <20110329072107.GA17048@plug.localdomain> <20110329061344.26a88267@liberty.rlwhome.lan> Message-ID: <4D91C59B.5040005@gmail.com> The link for the LibreOffice binaries is broken. It must be updated to 3.3.2, I guess - Luis From jens at tuxane.com Tue Mar 29 14:05:41 2011 From: jens at tuxane.com (TuxaneMedia) Date: Tue, 29 Mar 2011 16:05:41 +0200 Subject: [Slackbuilds-users] cairo-dock and cairo-dock -plugins SlackBuilds In-Reply-To: <4D91B9BD.1050005@gmail.com> References: <4D91B5F0.1090607@gmail.com> <4D91B9BD.1050005@gmail.com> Message-ID: <4D91E735.4080809@tuxane.com> I guess there is a typo in the package . The SlackBuild files are called Slackbuild so it can't build. Try to use 'Edit SlackBuild' in SboPkg and you'll see it's empty From pwcazenave at gmail.com Tue Mar 29 14:11:24 2011 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Tue, 29 Mar 2011 15:11:24 +0100 Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: <4D91BAD5.7080703@gmail.com> References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> Message-ID: <4D91E88C.2040703@gmail.com> On 29/03/2011 11:56, Matteo Bernardini wrote: > On 29/03/2011 12:35, Pierre Cazenave wrote: >> I couldn't get libproxy to build > > FYI, I tried now with the updated (0.4.6) version on git master > > http://slackbuilds.org/gitweb/?p=slackbuilds.git;a=commitdiff;h=ac83402644da63bc7d8f362ae0961ab1d6e0e202 > > and builds fine on l33t. :) > > 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/ > Got that one to work; not sure what was wrong before... As such, midori can also be added as a "works". Pierre From ml at mareichelt.com Tue Mar 29 16:58:43 2011 From: ml at mareichelt.com (markus reichelt) Date: Tue, 29 Mar 2011 18:58:43 +0200 Subject: [Slackbuilds-users] Abandoning some scripts... In-Reply-To: <20110328235927.2be2ac6a@liberty.rlwhome.lan> References: <20110328235927.2be2ac6a@liberty.rlwhome.lan> Message-ID: <20110329165843.GA20403@pc21.mareichelt.com> * Robby Workman wrote: > * system/cdfs MAINTAINER="markus reichelt" EMAIL="slackbuilds at mareichelt.de" -- left blank, right bald -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From niels.horn at gmail.com Tue Mar 29 18:00:02 2011 From: niels.horn at gmail.com (Niels Horn) Date: Tue, 29 Mar 2011 15:00:02 -0300 Subject: [Slackbuilds-users] LibreOffice broken link In-Reply-To: <4D91C59B.5040005@gmail.com> References: <20110328235927.2be2ac6a@liberty.rlwhome.lan> <20110329072107.GA17048@plug.localdomain> <20110329061344.26a88267@liberty.rlwhome.lan> <4D91C59B.5040005@gmail.com> Message-ID: Yes, and it has already been done :) You can get the updated version from the git repo on SlackBuilds.org or from my site: http://nielshorn.net -- Niels On 3/29/11, Luis Henrique F. Cardoso de Mello wrote: > The link for the LibreOffice binaries is broken. It must be updated to > 3.3.2, I guess > > - Luis > _______________________________________________ > 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/ > > -- Niels Horn Rio de Janeiro, RJ Brasil site: www.nielshorn.net e-mail: niels.horn at gmail.com From baildon.research at googlemail.com Tue Mar 29 19:38:47 2011 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 29 Mar 2011 20:38:47 +0100 Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: <4D91E88C.2040703@gmail.com> References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> Message-ID: Am I allowed to recycle this thread for some more packages? (1) I see from git that R is being removed (unmaintained). Well, qgis (one of my packages) incorrectly lists R as a dependency in the README. In fact qgis does not depend on R these days, so it would be great to just edit the README to remove the reference to R. Thanks! (2) postgis (not one of my packages) doesn't build at the moment. This is not a 13.37 problem -- the cause is the recent Postgresql 9 upgrade. Upgrading postgis to the latest version upstream (1.5.2) is straightforward and solves the build problem. Best wishes -Dave Spencer From rshepard at appl-ecosys.com Tue Mar 29 19:48:48 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 29 Mar 2011 12:48:48 -0700 (PDT) Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> Message-ID: On Tue, 29 Mar 2011, David Spencer wrote: > (1) I see from git that R is being removed (unmaintained). So, for future versions of R I build from source without a SlackBuild script? Rich From ivanp84 at gmail.com Tue Mar 29 19:59:40 2011 From: ivanp84 at gmail.com (Ivan Pavicevic) Date: Tue, 29 Mar 2011 21:59:40 +0200 Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> Message-ID: As biochemist, I often use R on Slackware64, it is the most powerful data analysis framework. And of course, always built from src with SlackBuild script. I hope that SlackBuilds.org will continue to support R. On Tue, Mar 29, 2011 at 9:48 PM, Rich Shepard wrote: > On Tue, 29 Mar 2011, David Spencer wrote: > > (1) I see from git that R is being removed (unmaintained). >> > > So, for future versions of R I build from source without a SlackBuild > script? > > Rich > > _______________________________________________ > 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 pwcazenave at gmail.com Tue Mar 29 20:03:44 2011 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Tue, 29 Mar 2011 21:03:44 +0100 Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> Message-ID: <4D923B20.80104@gmail.com> On 29/03/2011 20:59, Ivan Pavicevic wrote: > As biochemist, I often use R on Slackware64, it is the most powerful data > analysis framework. And of course, always built from src with SlackBuild > script. I hope that SlackBuilds.org will continue to support R. > > On Tue, Mar 29, 2011 at 9:48 PM, Rich Shepardwrote: > >> On Tue, 29 Mar 2011, David Spencer wrote: >> >> (1) I see from git that R is being removed (unmaintained). >>> >> >> So, for future versions of R I build from source without a SlackBuild >> script? >> >> Rich >> >> _______________________________________________ >> 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/ > It's not SlackBuilds.org that support it -- we're the ones who support whatever software we want. If something isn't included that you want included, you can always ask to take over the maintenance of that package. Since the script for R already exists, it's probably just a case of bumping version numbers when a new release comes out and making sure it still compiles. Piere From baildon.research at googlemail.com Tue Mar 29 20:06:48 2011 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 29 Mar 2011 21:06:48 +0100 Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> Message-ID: > ?So, for future versions of R I build from source without a SlackBuild > script? You could be the new maintainer :D It was offered on the list last year but nobody volunteered :O ---------------------- Damn, I knew there was something else. Could the Admins please remove multimedia/jmf? It has no useful purpose since Libreoffice gave us proper multimedia support. (Unless someone else has a different opinion...) Thanks! -D. From rshepard at appl-ecosys.com Tue Mar 29 20:11:49 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 29 Mar 2011 13:11:49 -0700 (PDT) Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> Message-ID: On Tue, 29 Mar 2011, Ivan Pavicevic wrote: > As biochemist, I often use R on Slackware64, it is the most powerful data > analysis framework. And of course, always built from src with SlackBuild > script. I hope that SlackBuilds.org will continue to support R. I'm an aquatic ecologist/fluvial geomorphologist and I've just started to use R for a couple of large projects. It would be nice to continue to use the SlackBuild script. Rich From rshepard at appl-ecosys.com Tue Mar 29 20:13:25 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 29 Mar 2011 13:13:25 -0700 (PDT) Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: <4D923B20.80104@gmail.com> References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> <4D923B20.80104@gmail.com> Message-ID: On Tue, 29 Mar 2011, Pierre Cazenave wrote: > Since the script for R already exists, it's probably just a case of > bumping version numbers when a new release comes out and making sure it > still compiles. Piere, Doesn't this also require another system on which the release candidate version can be installed for testing? I have only my desktop server/workstation and my laptop. Rich From rshepard at appl-ecosys.com Tue Mar 29 20:14:27 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 29 Mar 2011 13:14:27 -0700 (PDT) Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> Message-ID: On Tue, 29 Mar 2011, David Spencer wrote: > You could be the new maintainer :D What's required? > It was offered on the list last year but nobody volunteered :O I wasn't regularly following the list. Rich From ivanp84 at gmail.com Tue Mar 29 20:14:25 2011 From: ivanp84 at gmail.com (Ivan Pavicevic) Date: Tue, 29 Mar 2011 22:14:25 +0200 Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: <4D923B20.80104@gmail.com> References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> <4D923B20.80104@gmail.com> Message-ID: I figured it, Piere. :) And yes, there is no patches section in the script, so current SB script for R works for R 2.12.2 (built on S64-current, a week ago, just changed version number). I will try to contribute and write SB scripts for programs I often use (Jmol, Chimera, Bioclipse, AutoDoc, ...). On Tue, Mar 29, 2011 at 10:03 PM, Pierre Cazenave wrote: > On 29/03/2011 20:59, Ivan Pavicevic wrote: > >> As biochemist, I often use R on Slackware64, it is the most powerful data >> analysis framework. And of course, always built from src with SlackBuild >> script. I hope that SlackBuilds.org will continue to support R. >> >> On Tue, Mar 29, 2011 at 9:48 PM, Rich Shepard> >wrote: >> >> On Tue, 29 Mar 2011, David Spencer wrote: >>> >>> (1) I see from git that R is being removed (unmaintained). >>> >>>> >>>> >>> So, for future versions of R I build from source without a SlackBuild >>> script? >>> >>> Rich >>> >>> _______________________________________________ >>> 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/ >> >> > It's not SlackBuilds.org that support it -- we're the ones who support > whatever software we want. If something isn't included that you want > included, you can always ask to take over the maintenance of that package. > > Since the script for R already exists, it's probably just a case of bumping > version numbers when a new release comes out and making sure it still > compiles. > > Piere > > > _______________________________________________ > 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 ml at mareichelt.com Tue Mar 29 20:18:46 2011 From: ml at mareichelt.com (markus reichelt) Date: Tue, 29 Mar 2011 22:18:46 +0200 Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> <4D923B20.80104@gmail.com> Message-ID: <20110329201846.GC20403@pc21.mareichelt.com> * Ivan Pavicevic wrote: > ago, just changed version number). I will try to contribute and > write SB scripts for programs I often use (Jmol, Chimera, I'm looking forward to Jmol & Chimera scripts :) -- left blank, right bald -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From pwcazenave at gmail.com Tue Mar 29 20:24:25 2011 From: pwcazenave at gmail.com (Pierre Cazenave) Date: Tue, 29 Mar 2011 21:24:25 +0100 Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> <4D923B20.80104@gmail.com> Message-ID: <4D923FF9.6020405@gmail.com> On 29/03/2011 21:13, Rich Shepard wrote: > On Tue, 29 Mar 2011, Pierre Cazenave wrote: > >> Since the script for R already exists, it's probably just a case >> of bumping version numbers when a new release comes out and making >> sure it still compiles. > > Piere, > > Doesn't this also require another system on which the release > candidate version can be installed for testing? I have only my > desktop server/workstation and my laptop. > > Rich _______________________________________________ > 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/ > Generally you are only expected to maintain your scripts for the current stable release of Slackware. At the moment, scripts at SlackBuilds.org are only officially supported on 13.1. When 13.37 is released, everyone will have to make sure their scripts work on 13.37, fix any that don't (just updating to the most recent release of your program usually fixes most problems), and then resubmit them. The SlackBuilds.org admins at do do a lot of testing themselves when there's a new release of Slackware on its way, but their time is limited and there are a lot of scripts. I maintian 20 or so scripts. Cumulatively, it probably takes me a few hours a month to check their up to date and fix those that aren't. I occasionally get emails from people with suggestions or problems building something, which is gratifying in some ways, as then I know there's at least one other person using the script! The easiest way to maintain scripts is to use a virtual machine (I use VirtualBox) to have a clean installation of Slackware. The nice thing about Slackware is that even if you're a bit short of horsepower, you can be really quite stingy with the virtual machine's "hardware" and still test your scripts. This way you can have a day-to-day installation with all the software you want installed, and for testing your SlackBuilds, you use the virtual machine so that you're not introducing unnecessary complexity into the build process. Pierre (can't believe I mistyped my name in my last email!) From rshepard at appl-ecosys.com Tue Mar 29 23:52:20 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 29 Mar 2011 16:52:20 -0700 (PDT) Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: <4D923FF9.6020405@gmail.com> References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> <4D923B20.80104@gmail.com> <4D923FF9.6020405@gmail.com> Message-ID: On Tue, 29 Mar 2011, Pierre Cazenave wrote: > Generally you are only expected to maintain your scripts for the current > stable release of Slackware. At the moment, scripts at SlackBuilds.org are > only officially supported on 13.1. When 13.37 is released, everyone will > have to make sure their scripts work on 13.37, fix any that don't (just > updating to the most recent release of your program usually fixes most > problems), and then resubmit them. Thanks, Pierre. > The easiest way to maintain scripts is to use a virtual machine (I use > VirtualBox) to have a clean installation of Slackware. The nice thing > about Slackware is that even if you're a bit short of horsepower, you can > be really quite stingy with the virtual machine's "hardware" and still > test your scripts. I've run Slackware since 2003, including on very limited hardware. That's why I stick with it. I ran Red Hat from 1997-2003 and got tired of the dependency hell every time I'd try to upgrade a package. And I didn't want to be on the bleeding edge. > Pierre (can't believe I mistyped my name in my last email!) Time for sleep? :-) I wondered about the spelling but figured you know how to spell your name. Merci, Rich From rworkman at slackbuilds.org Thu Mar 31 03:44:42 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 30 Mar 2011 22:44:42 -0500 Subject: [Slackbuilds-users] My SlackBuilds on -current. In-Reply-To: References: <4D91B5F0.1090607@gmail.com> <4D91BAD5.7080703@gmail.com> <4D91E88C.2040703@gmail.com> Message-ID: <20110330224442.0a4262c2@liberty.rlwhome.lan> On Tue, 29 Mar 2011 21:06:48 +0100 David Spencer wrote: > Damn, I knew there was something else. Could the Admins please remove > multimedia/jmf? It has no useful purpose since Libreoffice gave us > proper multimedia support. (Unless someone else has a different > opinion...) Done; will be pushed to master soon. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rworkman at slackbuilds.org Thu Mar 31 03:46:53 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 30 Mar 2011 22:46:53 -0500 Subject: [Slackbuilds-users] Abandoning some scripts... In-Reply-To: <20110329165843.GA20403@pc21.mareichelt.com> References: <20110328235927.2be2ac6a@liberty.rlwhome.lan> <20110329165843.GA20403@pc21.mareichelt.com> Message-ID: <20110330224653.232fb3e4@liberty.rlwhome.lan> On Tue, 29 Mar 2011 18:58:43 +0200 markus reichelt wrote: > * Robby Workman wrote: > > > * system/cdfs > > MAINTAINER="markus reichelt" > EMAIL="slackbuilds at mareichelt.de" Got it; 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 rshepard at appl-ecosys.com Thu Mar 31 15:44:44 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 31 Mar 2011 08:44:44 -0700 (PDT) Subject: [Slackbuilds-users] Postfix Message-ID: I see on the web site that postfix-2.6.1 is shown as the version; that's well behind the current version. I just successfully upgraded the package from -2.7.1 to -2.8.2 on -13.1. The only minor cleanup that could be done is during installation: Executing install script for postfix-2.8.2-i486-1_SBo.tgz. chown: cannot access /etc/postfix/README_FILES/MULTI_INSTANCE_README': No such file or directory HTH, Rich