Re: [another "me too"] Re: portindex/portindexdb
On Tue, Sep 07, 2004 at 07:38:07PM +0200, Nico Meijer wrote: > Hi Matthew, > > >Another workaround is simply to set: > > > >PORTS_DBDRIVER=bdb1_hash > > > >in your environment, and then use portsdb and portupgrade as usual. > > May I bluntly - yet politely - ask why you would prefer this workaround > as opposed to replacing `portsdb -Uu` with `portindex && portindexdb`, > other than to avoid having to install extra software? > > I can imagine a few, but I value your opinion. Not having to install any extra software is the specific reason to prefer this. Using portsindex and portsindexdb is perfectly good as well, but that means installing python and possibly the Postgres DB client. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpxL2PDX5HXf.pgp Description: PGP signature
Re: [another "me too"] Re: portindex/portindexdb
Hi Matthew, Another workaround is simply to set: PORTS_DBDRIVER=bdb1_hash in your environment, and then use portsdb and portupgrade as usual. May I bluntly - yet politely - ask why you would prefer this workaround as opposed to replacing `portsdb -Uu` with `portindex && portindexdb`, other than to avoid having to install extra software? I can imagine a few, but I value your opinion. Thanks a bunch... Nico ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [another "me too"] Re: portindex/portindexdb
On Tue, Sep 07, 2004 at 07:24:49AM +0100, Matthew Seaman wrote: > > Another workaround is simply to set: > > PORTS_DBDRIVER=bdb1_hash This is the Berkeley, AKA Sleepycat, bdb? I ask because I am also (suddenly) encountering the famous Exim "Failed to open DBM file /var/spool/exim/db/retry for writing:" message. Oddly, until recently this error was not in evidence; and prior to recently, it was in evidence and I fixed it; prior to that failure, it (wait for it) Just Worked[1]. I wonder if the issue as evidenced by the Exim error could possibly be related to the ruby error? I hear, from time to time, vague rumblings about how the bdb software seeming to annoy people. I know one thing I've learned, and hope it is accurate: when installing Exim (and likely any other MTA as a substitute for Sendmail) build it from source the first time, because installing a binary and then using portupgrade will likely cause problems down the road. Of course, that lesson is probably covered in an FAQ somewhere, and I just forgot it. > in your environment, and then use portsdb and portupgrade as usual. > There are a number of variations on this workaround, but the other > ways of doing that involve installing some extra software. > > See: > > http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/015902.html > http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/015922.html Thanks; that last one looks interesting. [1] So: it worked, it failed, it worked, and now, shortly before the ruby issue, it began to fail. My previous cure for the Exim error was, vis-a-vis this last failure, ineffectual. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [another "me too"] Re: portindex/portindexdb
On Tue, Sep 07, 2004 at 06:32:23AM +0200, Nico Meijer wrote: > Hi Joe, > > >Sigh: > > Lighten up! ;-) Hehthanks, I will. > >/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: > >[BUG] Bus Error > >ruby 1.8.2 (2004-07-29) [i386-freebsd4] > > Have you tried replacing the portsdb-sequence with `portindex && > portindexdb`? Not yet; but I will. I was reading over the thread(s) mentioned by racerx last night. > So: > > - cvsup (or whatever tool you use) > - portindex > - portindexdb > - portversion -vL = (or whatever switches you use) > > The upside to using portindex is that it merges changes instead of > building the entire index every time. So your first run will take quite > some time, but your following runs will run quite a bit faster. AhI see now the advantage. That is nice. Thanks. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [another "me too"] Re: portindex/portindexdb
On Tue, Sep 07, 2004 at 06:32:23AM +0200, Nico Meijer wrote: > Hi Joe, > > >Sigh: > > Lighten up! ;-) > > >/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: > >[BUG] Bus Error > >ruby 1.8.2 (2004-07-29) [i386-freebsd4] > > Have you tried replacing the portsdb-sequence with `portindex && > portindexdb`? > > So: > > - cvsup (or whatever tool you use) > - portindex > - portindexdb > - portversion -vL = (or whatever switches you use) > > The upside to using portindex is that it merges changes instead of > building the entire index every time. So your first run will take quite > some time, but your following runs will run quite a bit faster. Another workaround is simply to set: PORTS_DBDRIVER=bdb1_hash in your environment, and then use portsdb and portupgrade as usual. There are a number of variations on this workaround, but the other ways of doing that involve installing some extra software. See: http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/015902.html http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/015922.html Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpa7VPOKd5Ax.pgp Description: PGP signature
Re: [another "me too"] Re: portindex/portindexdb
Hi Joe, Sigh: Lighten up! ;-) /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd4] Have you tried replacing the portsdb-sequence with `portindex && portindexdb`? So: - cvsup (or whatever tool you use) - portindex - portindexdb - portversion -vL = (or whatever switches you use) The upside to using portindex is that it merges changes instead of building the entire index every time. So your first run will take quite some time, but your following runs will run quite a bit faster. HTH and good luck... Nico ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [another "me too"] Re: portindex/portindexdb
- Original Message - From: "Joe Altman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 06, 2004 7:35 PM Subject: Re: [another "me too"] Re: portindex/portindexdb > On Mon, Sep 06, 2004 at 09:20:14AM +0200, Nico Meijer wrote: > > Hi Donald, > > > > >Nico - I suggest you try it again tomorrow. I thought I had it fixed > > >yesterday. Then I re-cvsup'd today and redid my things. Ruby18 is > > >again seg faulting for me. Not going into a loop and continuously > > >seg faulting, but bad enough. > > > > After cvsupping my ports tree, running portindex (not portindexdb!) and > > portsdb -u (which gave core dumps) all is well. No more 'bus errors'. > > > > portindex seems like a wonderful tool, so I'm keeping it around. > > Sigh: > > on voip in /var/db # portsdb -Uu > Updating the ports index ... Generating INDEX.tmp - please > wait.. Done. > done > [Updating the portsdb in /usr/ports ... - 11736 > port entries found > .1000.2000.3000.4000. > 5000.6000.7000.8000 > /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: > [BUG] Bus Error > ruby 1.8.2 (2004-07-29) [i386-freebsd4] > > Abort (core dumped) > > I'm thinking, at this point, that I'm seeing something > hardware-related. Good thing I'm replacing voip w/ new hardware and > moving to 5.3, I guess. No, it's not hardware.. I've fixed mine following the earlier threads. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [another "me too"] Re: portindex/portindexdb
On Mon, Sep 06, 2004 at 09:20:14AM +0200, Nico Meijer wrote: > Hi Donald, > > >Nico - I suggest you try it again tomorrow. I thought I had it fixed > >yesterday. Then I re-cvsup'd today and redid my things. Ruby18 is > >again seg faulting for me. Not going into a loop and continuously > >seg faulting, but bad enough. > > After cvsupping my ports tree, running portindex (not portindexdb!) and > portsdb -u (which gave core dumps) all is well. No more 'bus errors'. > > portindex seems like a wonderful tool, so I'm keeping it around. Sigh: on voip in /var/db # portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait.. Done. done [Updating the portsdb in /usr/ports ... - 11736 port entries found .1000.2000.3000.4000. 5000.6000.7000.8000 /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd4] Abort (core dumped) I'm thinking, at this point, that I'm seeing something hardware-related. Good thing I'm replacing voip w/ new hardware and moving to 5.3, I guess. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [another "me too"] Re: portindex/portindexdb
Hi Donald, Nico - I suggest you try it again tomorrow. I thought I had it fixed yesterday. Then I re-cvsup'd today and redid my things. Ruby18 is again seg faulting for me. Not going into a loop and continuously seg faulting, but bad enough. After cvsupping my ports tree, running portindex (not portindexdb!) and portsdb -u (which gave core dumps) all is well. No more 'bus errors'. portindex seems like a wonderful tool, so I'm keeping it around. HTH and good luck... Nico ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [another "me too"] Re: portindex/portindexdb
Nico - I suggest you try it again tomorrow. I thought I had it fixed yesterday. Then I re-cvsup'd today and redid my things. Ruby18 is again seg faulting for me. Not going into a loop and continuously seg faulting, but bad enough. Don Donald J. O'Neill [EMAIL PROTECTED] <>> On Sunday 05 September 2004 01:46 pm, Nico Meijer wrote: > Hi All, > > My apologies for another "me too": using portindex and > portindexdb solved the issue for me. portupgrade does its > miracles again. > > Bye... Nico > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[another "me too"] Re: portindex/portindexdb
Hi All, My apologies for another "me too": using portindex and portindexdb solved the issue for me. portupgrade does its miracles again. Bye... Nico ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portindex/portindexdb
Count me in too on this issue. I've had the "ruby18" problem and core dumps, and do not have portindex/portmanetc. installed. Happens after cvsup & running portsdb -Uu. Best regards, Jack L. Stone - Original Message - From: "Matthew Seaman" <[EMAIL PROTECTED]> To: "Donald J. O'Neill" <[EMAIL PROTECTED]> Cc: "Steve Hodgson" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "kstewart" <[EMAIL PROTECTED]> Sent: Sunday, September 05, 2004 3:17 AM Subject: Re: portindex/portindexdb ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portindex/portindexdb
On Sat, Sep 04, 2004 at 02:43:51PM -0500, Donald J. O'Neill wrote: > This is not a moot point. I've been struggling with this problem > since this morning. The problem would just not go away. Yes. Yesterday morning, I cvsup'd as usual and everything happened to work OK. Tried again this morning, and it's back to ruby core dumping. What ever is triggering this appears to be quite subtle, and it's not affecting anything else that does similar jobs with the ports system. > The one I found was, on 090104 I did a portupgrade of portmanager. I > also had portsman installed (probablu inconsequential). I did a > "make deinstall" of portmanager and portsman. After that > portversion -rRvc worked, ruby18 was no longer seg faulting. I > suspect the problem had something to do with the upgrade of > portmanger. As you say, removing portsmanager and portsman was probably inconsequential. Unfortunately there's not a lot that can be done except to provide any debugging info that developers ask for and to remain patient. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpvGxfRGaCXh.pgp Description: PGP signature
Re: portindex/portindexdb
Hello Mattthew, This is not a moot point. I've been struggling with this problem since this morning. The problem would just not go away. After I cvsup the ports, I use "make index" and then portversion -rRvc. I also run script whenever I cvsup, portupgrade, or install a new port. On 090104 I cvsup'd ports and successfully portupgraded the ports (except a couple of php5 extentions and qcad, no big deal, I'll wait a while). On 090204 I again cvsup'd ports and successfully portupgraded the ports (exceptions previously noted). Today, I cvsup'd the ports, ran "make index", and when I ran portupgrade -rRcv, it went into a loop, on ttyv0 I was getting a message that "ruby18 uid 0: exited on signal 6 (coredumped). That ruby18.core file is over 10mb, would it be of use to anyone? After several different cvsup's, and other ways to generate INDEX-5, all of which worked by the way, but all the ways of checking for ports needing updating caused ruby18 to fail. The one I found was, on 090104 I did a portupgrade of portmanager. I also had portsman installed (probablu inconsequential). I did a "make deinstall" of portmanager and portsman. After that portversion -rRvc worked, ruby18 was no longer seg faulting. I suspect the problem had something to do with the upgrade of portmanger. It solved my problem anyway. I am not investigating any further. I have other things that I'm trying to accomplish. However, I someone wants the ruby18.core file, I e-mail it. It is over 10mb and a lot of e-mail programs won't take an atachment that big. Don Donald J. O'Neill [EMAIL PROTECTED] <<>> On Saturday 04 September 2004 09:10 am, Matthew Seaman wrote: > On Sat, Sep 04, 2004 at 11:08:49AM +0100, Steve Hodgson wrote: > > > FWIW, portindexdb will generate INDEX-5.db just fine on > > > 5-current. It doesn't have the problem with ruby bus erroring > > > like portsdb -u does. > > > > This also works for me on 5.2.1-p9. Am I missing something in > > asking why couldn't "portsdb -u" be replaced by portindex? > > Obviously this couldn't happen now with the code-freeze for > > 5.3, but for 5.4? > > The question would seem to be moot now. As of this morning > portsdb is able to build an INDEX.db once again. Although I > cannot see exactly what was committed in order to make that work. > > Since both portindex and protupgrade are 3rd party tools, and > neither are likely to be committed either to the base system or > to become part of the official ports infrastructure[1], it's > entirely up to you which one you choose. > > Cheers, > > Matthew > > [1] In the grand tradition of cvsup(1), it seems that any > insanely useful tools for managing ports will be written in > languages other than those provided as standard. -- Donald J. O'Neill [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portindex/portindexdb
On Sat, Sep 04, 2004 at 11:08:49AM +0100, Steve Hodgson wrote: > > FWIW, portindexdb will generate INDEX-5.db just fine on 5-current. It > > doesn't have the problem with ruby bus erroring like portsdb -u does. > This also works for me on 5.2.1-p9. Am I missing something in asking why > couldn't "portsdb -u" be replaced by portindex? Obviously this couldn't > happen now with the code-freeze for 5.3, but for 5.4? The question would seem to be moot now. As of this morning portsdb is able to build an INDEX.db once again. Although I cannot see exactly what was committed in order to make that work. Since both portindex and protupgrade are 3rd party tools, and neither are likely to be committed either to the base system or to become part of the official ports infrastructure[1], it's entirely up to you which one you choose. Cheers, Matthew [1] In the grand tradition of cvsup(1), it seems that any insanely useful tools for managing ports will be written in languages other than those provided as standard. -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpM1hPIOtljz.pgp Description: PGP signature
Re: portindex/portindexdb
> > FWIW, portindexdb will generate INDEX-5.db just fine on 5-current. It > doesn't have the problem with ruby bus erroring like portsdb -u does. > > Kent This also works for me on 5.2.1-p9. Am I missing something in asking why couldn't "portsdb -u" be replaced by portindex? Obviously this couldn't happen now with the code-freeze for 5.3, but for 5.4? Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portindex/portindexdb
On Thursday 02 September 2004 06:17 am, Lucas Holt wrote: > After seeing several posts recently on portindex, I decided to try it > out. Most of the posts claimed you had to run portsdb -u after > portindex. > > Is it safe to use portindexdb instead of portsdb -u? > > Another words I want to do this: > cvsup ... > portindex > portindexdb > portversion -v | grep "<" > > Lucas Holt FWIW, portindexdb will generate INDEX-5.db just fine on 5-current. It doesn't have the problem with ruby bus erroring like portsdb -u does. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html Support the Bison at http://www.buffalofieldcampaign.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portindex/portindexdb
On Thu, 2 Sep 2004, Lucas Holt wrote: After seeing several posts recently on portindex, I decided to try it out. Most of the posts claimed you had to run portsdb -u after portindex. You *can* run it after portindex, but the man page for portsdb says it is "automatically updated on demand when it gets older than the index file." And you'll see the ...1000...2000 display from portsdb then. -Warren Block * Rapid City, South Dakota USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portindex/portindexdb
After seeing several posts recently on portindex, I decided to try it out. Most of the posts claimed you had to run portsdb -u after portindex. Is it safe to use portindexdb instead of portsdb -u? Another words I want to do this: cvsup ... portindex portindexdb portversion -v | grep "<" Lucas Holt [EMAIL PROTECTED] FoolishGames.com (Jewel Fan Site) JustJournal.com (Free blogging) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
