From chess at chessgriffin.com Fri Mar 5 22:20:44 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 5 Mar 2010 17:20:44 -0500 Subject: [sbopkg-users] Sbopkg 0.32.0 Released Message-ID: <20100305222044.GA14717@localhost> I am happy to announce that sbopkg version 0.32.0 has been released. We have been working steadily since the last release to fix bugs and add a couple of new features. There is one new addition to the sbopkg.conf configuration file, so please check out the installed sbopkg.conf.new to merge the change. Here is the unedited ChangeLog: * Add several renames to 50-default renames file. * Add support for UNSUPPORTED/UNTESTED packages in the SBo repo; thanks to artourter for the bug report. * Honor the TAG exported by the user; thanks to Matteo Bernardini for the feature request. * Fix issue where delete sources in package info item menu did not work in some cases; thanks to artourter for the report, thanks to slakmagik for the hard work in fixing this and thanks to Mauro for the review and suggestions. * Add the ability to skip the prompts for sbopkg's directory creations via the new config file option MKDIR_PROMPT. This is useful, for example, if you have some SBo/sbopkg directories on a temporary filesystem and don't want to be bothered with repeated directory creation prompts. Thanks to agikhan for the report. * Address an issue where sbopkg could sometimes pick an older package to present for installation rather than the most recent one; thanks to artourter for the report. * Prevent sbopkg from spitting error messages when trying to determine the version of some packages (e.g. google-chrome, whose version is discovered looking into the source package which can be missing). Thanks to alkos333 for the bug report. * Add ability to temporarily change $ARCH in the 'options' submenu. Big thanks to all the sbopkg users who have pounded on this utility, reported bugs, and suggested enhancements. We hope you find this software useful and these updates beneficial. As always, a new package and source tarball are available for direct download from the sbopkg project website: http://www.sbopkg.org. Please report any issues to the sbopkg mailing list or, preferably, to the sbopkg Issue Tracker at the project's Google Code page. Thanks once again to my cohorts, Mauro Giachero and slakmagik, for their invaluable assistance. Enjoy! -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From me at alkos333.net Fri Mar 5 23:22:38 2010 From: me at alkos333.net (alkos333) Date: Fri, 5 Mar 2010 17:22:38 -0600 Subject: [sbopkg-users] [Slackbuilds-users] Sbopkg 0.32.0 Released In-Reply-To: <20100305222044.GA14717@localhost> References: <20100305222044.GA14717@localhost> Message-ID: On Fri, Mar 5, 2010 at 4:20 PM, Chess Griffin wrote: > I am happy to announce that sbopkg version 0.32.0 has been released. ?We > have been working steadily since the last release to fix bugs and add a > couple of new features. ?There is one new addition to the sbopkg.conf > configuration file, so please check out the installed sbopkg.conf.new to > merge the change. > > Here is the unedited ChangeLog: > > ?* Add several renames to 50-default renames file. > ?* Add support for UNSUPPORTED/UNTESTED packages in the SBo repo; thanks to > ? ?artourter for the bug report. > ?* Honor the TAG exported by the user; thanks to Matteo Bernardini for the > ? ?feature request. > ?* Fix issue where delete sources in package info item menu did not work in > ? ?some cases; thanks to artourter for the report, thanks to slakmagik for > ? ?the hard work in fixing this and thanks to Mauro for the review and > ? ?suggestions. > ?* Add the ability to skip the prompts for sbopkg's directory creations via > ? ?the new config file option MKDIR_PROMPT. This is useful, for example, if > ? ?you have some SBo/sbopkg directories on a temporary filesystem and don't > ? ?want to be bothered with repeated directory creation prompts. Thanks to > ? ?agikhan for the report. > ?* Address an issue where sbopkg could sometimes pick an older package to > ? ?present for installation rather than the most recent one; thanks to > ? ?artourter for the report. > ?* Prevent sbopkg from spitting error messages when trying to determine the > ? ?version of some packages (e.g. google-chrome, whose version is discovered > ? ?looking into the source package which can be missing). Thanks to alkos333 > ? ?for the bug report. > ?* Add ability to temporarily change $ARCH in the 'options' submenu. > > Big thanks to all the sbopkg users who have pounded on this utility, > reported bugs, and suggested enhancements. ?We hope you find this > software useful and these updates beneficial. > > As always, a new package and source tarball are available for direct > download from the sbopkg project website: ?http://www.sbopkg.org. > Please report any issues to the sbopkg mailing list or, preferably, to > the sbopkg Issue Tracker at the project's Google Code page. > > Thanks once again to my cohorts, Mauro Giachero and slakmagik, for their > invaluable assistance. > > Enjoy! > Thank you so much for all the work that you've done and continue to do. This tool has saved me a lot of time. http://sbopkg.googlecode.com/files/sbopkg-0.32.0-noarch-1_cng.tgz (link from sbopkg.org) is invalid -- Alex Lysenka Bachelor of Computer Science Operations Management & Information Systems Major Northern Illinois University alysenka at niu.edu From chess at chessgriffin.com Fri Mar 5 23:55:06 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 5 Mar 2010 18:55:06 -0500 Subject: [sbopkg-users] [Slackbuilds-users] Sbopkg 0.32.0 Released In-Reply-To: References: <20100305222044.GA14717@localhost> Message-ID: <20100305235506.GA14774@localhost> * alkos333 [2010-03-05 17:22:38]: > Thank you so much for all the work that you've done and continue to > do. This tool has saved me a lot of time. Great, glad to hear it! > > http://sbopkg.googlecode.com/files/sbopkg-0.32.0-noarch-1_cng.tgz > (link from sbopkg.org) is invalid > Hmm, works here with no issues... maybe a caching issue? Does it work for you from the Google Code site: http://code.google.com/p/sbopkg/downloads/list (click the first link) -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From chess at chessgriffin.com Sat Mar 6 01:48:42 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 5 Mar 2010 20:48:42 -0500 Subject: [sbopkg-users] [Slackbuilds-users] Sbopkg 0.32.0 Released In-Reply-To: References: <20100305222044.GA14717@localhost> Message-ID: <20100306014842.GC14774@localhost> * alkos333 [2010-03-05 17:22:38]: > http://sbopkg.googlecode.com/files/sbopkg-0.32.0-noarch-1_cng.tgz > (link from sbopkg.org) is invalid > I re-uploaded the file and now it appears to be working. -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From dave at unrealize.co.uk Mon Mar 8 17:41:22 2010 From: dave at unrealize.co.uk (David Woodfall) Date: Mon, 8 Mar 2010 17:41:22 +0000 Subject: [sbopkg-users] [Slackbuilds-users] Sbopkg 0.32.0 Released In-Reply-To: <20100306014842.GC14774@localhost> References: <20100305222044.GA14717@localhost> <20100306014842.GC14774@localhost> Message-ID: <20100308174122.GA26052@Junius> On (20:48 05/03/10), Chess Griffin put forth the proposition: >* alkos333 [2010-03-05 17:22:38]: > >> http://sbopkg.googlecode.com/files/sbopkg-0.32.0-noarch-1_cng.tgz >> (link from sbopkg.org) is invalid >> > >I re-uploaded the file and now it appears to be working. > >-- >Chess Griffin Is it just me or has everyone got double posts for this thread? >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - http://slackbuilds.org/faq/ > -- Don't look back, the lemmings are gaining on you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 489 bytes Desc: not available URL: From me at alkos333.net Tue Mar 9 18:23:34 2010 From: me at alkos333.net (alkos333) Date: Tue, 9 Mar 2010 12:23:34 -0600 Subject: [sbopkg-users] Compiling Clearlooks Engine as a 32-bit package on Slackware64 (multilib) Message-ID: I'm trying to compile Clearlooks GTK engine as a 32-bit package, so I'm passing the ARCH=i486 in sbopkg, but when I do that I get the following error: checking whether to enable maintainer-specific portions of Makefiles... no checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. -- Alex Lysenka Bachelor of Computer Science Operations Management & Information Systems Major Northern Illinois University alysenka at niu.edu From chess at chessgriffin.com Tue Mar 9 18:49:33 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Tue, 9 Mar 2010 13:49:33 -0500 Subject: [sbopkg-users] Compiling Clearlooks Engine as a 32-bit package on Slackware64 (multilib) In-Reply-To: References: Message-ID: <20100309184932.GA11027@localhost> * alkos333 [2010-03-09 12:23:34]: > I'm trying to compile Clearlooks GTK engine as a 32-bit package, so > I'm passing the ARCH=i486 in sbopkg, but when I do that I get the > following error: > > checking whether to enable maintainer-specific portions of Makefiles... no > checking build system type... x86_64-unknown-linux-gnu > checking host system type... x86_64-unknown-linux-gnu > checking for style of include used by make... GNU > checking for gcc... gcc > checking for C compiler default output file name... configure: error: > C compiler cannot create executables > See `config.log' for more details. > Does the same thing happen when you export ARCH=i486 and run the SlackBuild manually (outside of sbopkg)? -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From me at alkos333.net Tue Mar 9 19:09:20 2010 From: me at alkos333.net (alkos333) Date: Tue, 9 Mar 2010 13:09:20 -0600 Subject: [sbopkg-users] Compiling Clearlooks Engine as a 32-bit package on Slackware64 (multilib) In-Reply-To: <20100309184932.GA11027@localhost> References: <20100309184932.GA11027@localhost> Message-ID: On Tue, Mar 9, 2010 at 12:49 PM, Chess Griffin wrote: > Does the same thing happen when you export ARCH=i486 and run the > SlackBuild manually (outside of sbopkg)? Yes. -- Alex Lysenka Bachelor of Computer Science Operations Management & Information Systems Major Northern Illinois University alysenka at niu.edu From chess at chessgriffin.com Tue Mar 9 19:19:48 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Tue, 9 Mar 2010 14:19:48 -0500 Subject: [sbopkg-users] Compiling Clearlooks Engine as a 32-bit package on Slackware64 (multilib) In-Reply-To: References: <20100309184932.GA11027@localhost> Message-ID: <20100309191948.GA11034@localhost> * alkos333 [2010-03-09 13:09:20]: > On Tue, Mar 9, 2010 at 12:49 PM, Chess Griffin wrote: > > Does the same thing happen when you export ARCH=i486 and run the > > SlackBuild manually (outside of sbopkg)? > > Yes. > Then unless I'm misunderstanding something, it does not appear to be an sbopkg issue. Or do I need to be hit with the cluestick again? -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From me at alkos333.net Tue Mar 9 21:25:17 2010 From: me at alkos333.net (alkos333) Date: Tue, 9 Mar 2010 15:25:17 -0600 Subject: [sbopkg-users] Compiling Clearlooks Engine as a 32-bit package on Slackware64 (multilib) In-Reply-To: References: <20100309184932.GA11027@localhost> <20100309191948.GA11034@localhost> <20100309194412.GA11042@localhost> Message-ID: On Tue, Mar 9, 2010 at 3:12 PM, alkos333 wrote: >>> Ok, thanks for the update. ?When you get it squared away, can you post a >>> follow up to the list for future reference? >> >> Will do > > The problem was the one related to compiling 32-bit packages on a > multilib system, which Eric has explained very clearly on his wiki > page. ?I've read the whole thing prior to converting my system a > multilib-enabled one, just kind of forgot about the compiling part > when it came time to actually compile the first 32-bit package. > > This is the wiki page for anyone who runs into this issue in the > future: ?http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib > > Sorry for posting it here. ?That was irrelevant. -- Alex Lysenka Bachelor of Computer Science Operations Management & Information Systems Major Northern Illinois University alysenka at niu.edu From dfcooley at gmail.com Fri Mar 26 08:07:54 2010 From: dfcooley at gmail.com (Donald Cooley) Date: Fri, 26 Mar 2010 03:07:54 -0500 Subject: [sbopkg-users] Installing slackbuilds after reinstall of slackware Message-ID: <20100326080754.GA16460@lucan.localdomain> Hi, So i did a fresh reinstall of slackware 13. I have many slackbuild *.tgz packages that I want to install again with sbopkg. At first I thought I could move the SBo folder into /tmp and place all the *.tgz packages in /tmp and all would be well. hehe... Anyway, do I need to make a local repository to do this? I don't want to run installpkg on these. After I install the local packages I want to sync with slackbuilds.org to keep everything up-to-date. I read the manpage and repos.d but don't understand how sbopkg will find my pakages. Regards, Donald Cooley From chess at chessgriffin.com Fri Mar 26 17:53:46 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 26 Mar 2010 13:53:46 -0400 Subject: [sbopkg-users] Installing slackbuilds after reinstall of slackware In-Reply-To: <20100326080754.GA16460@lucan.localdomain> References: <20100326080754.GA16460@lucan.localdomain> Message-ID: <1269626026.13942.1366909051@webmail.messagingengine.com> On Fri, 26 Mar 2010 03:07 -0500, "Donald Cooley" wrote: > Hi, > So i did a fresh reinstall of slackware 13. I have many slackbuild *.tgz > packages that I want to install again with sbopkg. At first I thought > I could move the SBo folder into /tmp and place all the *.tgz packages > in /tmp and all would be well. hehe... Anyway, do I need to make a > local repository to do this? I don't want to run installpkg on these. > After I install the local packages I want to sync with slackbuilds.org > to keep everything up-to-date. I read the manpage and repos.d but > don't understand how sbopkg will find my pakages. > > > Regards, > Donald Cooley It should just work, but it's not clear from your email what is going wrong. Does sbopkg fail to work, or does it not see the installed packages, do you get any error messages etc. A bit more detail is needed. What is $OUTPUT set to in your sbopkg.conf? As far as not running installpkg, that is all that sbopkg does, so I'm not sure what you are saving. Are these packages you built from SlackBuild scripts from SBo? Do they have the "_SBo" tag in the package name? -- Chess Griffin From dfcooley at gmail.com Fri Mar 26 18:28:53 2010 From: dfcooley at gmail.com (Donald Cooley) Date: Fri, 26 Mar 2010 13:28:53 -0500 Subject: [sbopkg-users] Installing slackbuilds after reinstall of slackware In-Reply-To: <1269626026.13942.1366909051@webmail.messagingengine.com> References: <20100326080754.GA16460@lucan.localdomain> <1269626026.13942.1366909051@webmail.messagingengine.com> Message-ID: <20100326182852.GD16460@lucan.localdomain> On Fri, Mar 26, 2010 at 01:53:46PM -0400, Chess Griffin wrote: > On Fri, 26 Mar 2010 03:07 -0500, "Donald Cooley" > wrote: > > Hi, > > So i did a fresh reinstall of slackware 13. I have many slackbuild *.tgz > > packages that I want to install again with sbopkg. At first I thought > > I could move the SBo folder into /tmp and place all the *.tgz packages > > in /tmp and all would be well. hehe... Anyway, do I need to make a > > local repository to do this? I don't want to run installpkg on these. > > After I install the local packages I want to sync with slackbuilds.org > > to keep everything up-to-date. I read the manpage and repos.d but > > don't understand how sbopkg will find my pakages. > > > > > > Regards, > > Donald Cooley > > It should just work, but it's not clear from your email what is going > wrong. Does sbopkg fail to work, or does it not see the installed > packages, do you get any error messages etc. A bit more detail is > needed. sbopkg runs fine. It just ignores everything in /tmp/SBo and /tmp/*SBO.tgz. > What is $OUTPUT set to in your sbopkg.conf? $ cat /etc/sbopkg/sbopkg.conf | grep -i output export OUTPUT=${OUTPUT:-/tmp} > > As far as not running installpkg, that is all that sbopkg does, so I'm > not sure what you are saving. I thought that if I installed with sbopkg then I would know which pkgs were installed and when there were updates. I also have several queue files to install pkgs in order to get dependencies. > Are these packages you built from > SlackBuild scripts from SBo? Do they have the "_SBo" tag in the package > name? > Yes & Yes > -- > Chess Griffin > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users From dfcooley at gmail.com Fri Mar 26 19:12:55 2010 From: dfcooley at gmail.com (Donald Cooley) Date: Fri, 26 Mar 2010 14:12:55 -0500 Subject: [sbopkg-users] Installing slackbuilds after reinstall of slackware In-Reply-To: <1269626026.13942.1366909051@webmail.messagingengine.com> References: <20100326080754.GA16460@lucan.localdomain> <1269626026.13942.1366909051@webmail.messagingengine.com> Message-ID: <20100326191254.GA27778@lucan.localdomain> On Fri, Mar 26, 2010 at 01:53:46PM -0400, Chess Griffin wrote: > On Fri, 26 Mar 2010 03:07 -0500, "Donald Cooley" > wrote: > > It should just work, but it's not clear from your email what is going > wrong. Does sbopkg fail to work, or does it not see the installed > packages, do you get any error messages etc. A bit more detail is > needed. What is $OUTPUT set to in your sbopkg.conf? > > As far as not running installpkg, that is all that sbopkg does, so I'm > not sure what you are saving. Are these packages you built from > SlackBuild scripts from SBo? Do they have the "_SBo" tag in the package > name? > > -- > Chess Griffin > _______________________________________________ > sbopkg-users mailing list > sbopkg-users at sbopkg.org > http://sbopkg.org/mailman/listinfo/sbopkg-users I found the install option by searching for gc. It allowed me to install that package. I guess I have to install each package one at a time. Regards, Donald Cooley From marc321 at gmail.com Fri Mar 26 21:39:16 2010 From: marc321 at gmail.com (Marc Payne) Date: Fri, 26 Mar 2010 15:39:16 -0600 Subject: [sbopkg-users] Installing slackbuilds after reinstall of slackware In-Reply-To: <20100326191254.GA27778@lucan.localdomain> References: <20100326080754.GA16460@lucan.localdomain> <1269626026.13942.1366909051@webmail.messagingengine.com> <20100326191254.GA27778@lucan.localdomain> Message-ID: <6adc5e7e1003261439h6bfcc1ddqcfffd7d4c0cb06d@mail.gmail.com> Hello Donald, I'm merely a user of sbopkg, but I think I can help to clear up one part of your dilemma: > I thought that if I installed with sbopkg then I would know > which pkgs were installed and when there were updates. Sbopkg knows which "_SBo" packages are installed on your system simply by parsing the list of all installed packages in /var/log/packages. In other words, sbopkg doesn't maintain its own separate list or database of installed SBo packages. This means that you can safely use installpkg to install everything you placed in /tmp, and the next time you fire up sbopkg and look at your list of installed SBo packages, they will be there. Now, to update your packages, you do need to have a recently synced local repo. Sbopkg simply compares version numbers contained in the repo with version numbers of SBo packages in /var/log/packages to determine if updates are available. I suppose to sum up: as Chess was hinting, it is perfectly acceptable to cd to /tmp and run "installpkg *.tgz" ("upgradepkg --install-new *.tgz" may be better if you happened to install some of them already). Hope this makes some sense. :-) Best regards, Marc From dfcooley at gmail.com Fri Mar 26 22:14:39 2010 From: dfcooley at gmail.com (Donald Cooley) Date: Fri, 26 Mar 2010 17:14:39 -0500 Subject: [sbopkg-users] Installing slackbuilds after reinstall of slackware In-Reply-To: <6adc5e7e1003261439h6bfcc1ddqcfffd7d4c0cb06d@mail.gmail.com> References: <20100326080754.GA16460@lucan.localdomain> <1269626026.13942.1366909051@webmail.messagingengine.com> <20100326191254.GA27778@lucan.localdomain> <6adc5e7e1003261439h6bfcc1ddqcfffd7d4c0cb06d@mail.gmail.com> Message-ID: <20100326221437.GA23306@lucan.localdomain> On Fri, Mar 26, 2010 at 03:39:16PM -0600, Marc Payne wrote: > Hello Donald, > > I'm merely a user of sbopkg, but I think I can help to clear up one > part of your dilemma: > > > I thought that if I installed with sbopkg then I would know > > which pkgs were installed and when there were updates. > > Sbopkg knows which "_SBo" packages are installed on your system simply > by parsing the list of all installed packages in /var/log/packages. In > other words, sbopkg doesn't maintain its own separate list or database > of installed SBo packages. This means that you can safely use > installpkg to install everything you placed in /tmp, and the next time > you fire up sbopkg and look at your list of installed SBo packages, > they will be there. > > Now, to update your packages, you do need to have a recently synced > local repo. Sbopkg simply compares version numbers contained in the > repo with version numbers of SBo packages in /var/log/packages to > determine if updates are available. > > I suppose to sum up: as Chess was hinting, it is perfectly acceptable > to cd to /tmp and run "installpkg *.tgz" ("upgradepkg --install-new > *.tgz" may be better if you happened to install some of them already). > > Hope this makes some sense. :-) > > Best regards, > Marc Hi Marc, That makes perfect sense. Thank you. --- Regards, Donald Cooley From chess at chessgriffin.com Fri Mar 26 23:03:05 2010 From: chess at chessgriffin.com (Chess Griffin) Date: Fri, 26 Mar 2010 19:03:05 -0400 Subject: [sbopkg-users] Installing slackbuilds after reinstall of slackware In-Reply-To: <20100326221437.GA23306@lucan.localdomain> References: <20100326080754.GA16460@lucan.localdomain> <1269626026.13942.1366909051@webmail.messagingengine.com> <20100326191254.GA27778@lucan.localdomain> <6adc5e7e1003261439h6bfcc1ddqcfffd7d4c0cb06d@mail.gmail.com> <20100326221437.GA23306@lucan.localdomain> Message-ID: <20100326230305.GA31188@localhost> * Donald Cooley [2010-03-26 17:14:39]: > On Fri, Mar 26, 2010 at 03:39:16PM -0600, Marc Payne wrote: > > Hello Donald, > > > > I'm merely a user of sbopkg, but I think I can help to clear up one > > part of your dilemma: > > > > > I thought that if I installed with sbopkg then I would know > > > which pkgs were installed and when there were updates. > > > > Sbopkg knows which "_SBo" packages are installed on your system simply > > by parsing the list of all installed packages in /var/log/packages. In > > other words, sbopkg doesn't maintain its own separate list or database > > of installed SBo packages. This means that you can safely use > > installpkg to install everything you placed in /tmp, and the next time > > you fire up sbopkg and look at your list of installed SBo packages, > > they will be there. > > > > Now, to update your packages, you do need to have a recently synced > > local repo. Sbopkg simply compares version numbers contained in the > > repo with version numbers of SBo packages in /var/log/packages to > > determine if updates are available. > > > > I suppose to sum up: as Chess was hinting, it is perfectly acceptable > > to cd to /tmp and run "installpkg *.tgz" ("upgradepkg --install-new > > *.tgz" may be better if you happened to install some of them already). > > > > Hope this makes some sense. :-) > > > > Best regards, > > Marc > > Hi Marc, > That makes perfect sense. Thank you. > > --- > Regards, > Donald Cooley Thanks, Marc, for the excellent explanation! :-) Sorry if I was not more clear, Donald -- I hope it's working ok for you now. -- Chess Griffin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available URL: