Re: portsdb -U fails

2004-02-02 Thread Chris
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 02 February 2004 03:19 pm, Kris Kennaway wrote: > On Mon, Feb 02, 2004 at 09:45:00PM +0100, r t g tan wrote: > > > Then why not quit banging you head on a wall and use "make index". Your > > > failure to adapt is spamming the list. Portsdb -U

Re: portsdb -U fails

2004-02-02 Thread Kent Stewart
On Monday 02 February 2004 12:45 pm, r t g tan wrote: > > Then why not quit banging you head on a wall and use "make index". > > Your failure to adapt is spamming the list. Portsdb -U has not > > produced totally clean INDEX runs since I can remember. Make index, > > on the other hand, is currently

Re: portsdb -U fails

2004-02-02 Thread Kris Kennaway
On Mon, Feb 02, 2004 at 09:45:00PM +0100, r t g tan wrote: > > Then why not quit banging you head on a wall and use "make index". Your > > failure to adapt is spamming the list. Portsdb -U has not produced > > totally clean INDEX runs since I can remember. Make index, on the other > > hand, is c

Re: portsdb -U fails

2004-02-02 Thread r t g tan
> Then why not quit banging you head on a wall and use "make index". Your > failure to adapt is spamming the list. Portsdb -U has not produced > totally clean INDEX runs since I can remember. Make index, on the other > hand, is currently producing clean makes. > > There are times when one doesn

Re: portsdb -U fails

2004-02-02 Thread Kent Stewart
On Sunday 01 February 2004 11:55 pm, r t g tan wrote: > On Sun, Feb 01, 2004 at 01:23:48PM -0800, Kris Kennaway wrote: > > On Sat, Jan 31, 2004 at 10:03:30PM +0100, r t g tan wrote: > > > > portsdb -U is broken - I sent mail to the author the other day, > > > > but didn't receive a reply yet. In t

Re: portsdb -U fails

2004-02-02 Thread Kris Kennaway
On Mon, Feb 02, 2004 at 08:55:12AM +0100, r t g tan wrote: > At this time I just cvsupped my ports again, and tried > it again with:open("|cd #{dir} && make -k -f -", 'w') do |w| OK, please verify that you are cvsupping the entire ports collection (i.e. ports-all), and if so then post th

Re: portsdb -U fails

2004-02-02 Thread r t g tan
On Sun, Feb 01, 2004 at 01:23:48PM -0800, Kris Kennaway wrote: > On Sat, Jan 31, 2004 at 10:03:30PM +0100, r t g tan wrote: > > > > portsdb -U is broken - I sent mail to the author the other day, but > > > didn't receive a reply yet. In the meantime, you can edit > > > /usr/local/sbin/make_descri

Re: portsdb -U fails

2004-02-01 Thread Kris Kennaway
On Sat, Jan 31, 2004 at 10:03:30PM +0100, r t g tan wrote: > > portsdb -U is broken - I sent mail to the author the other day, but > > didn't receive a reply yet. In the meantime, you can edit > > /usr/local/sbin/make_describe_pass1 and change the 'make -j3' to > > 'make'. > > > > Kris > > Hi K

Re: portsdb -U fails

2004-01-31 Thread r t g tan
; > 3 - pkgdb -F > > > > However portsdb -U fails and generates a lot of > > error messages like the following: > > > >*** Error code 2: malformed entry: *** Error code 2 > >*** Error code 2: malformed entry: *** Error code 2 > >*** Erro

Re: portsdb -U fails

2004-01-30 Thread Kris Kennaway
On Fri, Jan 30, 2004 at 05:57:52PM -0500, parv wrote: > in message <[EMAIL PROTECTED]>, > wrote Kris Kennaway thusly... > > > > On Fri, Jan 30, 2004 at 08:51:43PM +0100, r t g tan wrote: > > > However portsdb -U fails and generates a lot of > &

Re: portsdb -U fails

2004-01-30 Thread parv
in message <[EMAIL PROTECTED]>, wrote Kris Kennaway thusly... > > On Fri, Jan 30, 2004 at 08:51:43PM +0100, r t g tan wrote: > > However portsdb -U fails and generates a lot of > > error messages like the following: > > > >*** Error code 2: malformed entr

Re: portsdb -U fails

2004-01-30 Thread Kris Kennaway
fresh ports cvsup for all the ports > > > 2 - rm /var/db/pkg/pkgdb.db > > > 3 - pkgdb -F > > > > > > However portsdb -U fails and generates a lot of > > > error messages like the following: > > > > > >*** Error code 2: malformed

Re: portsdb -U fails

2004-01-30 Thread Kent Stewart
On Friday 30 January 2004 01:28 pm, Kris Kennaway wrote: > On Fri, Jan 30, 2004 at 08:51:43PM +0100, r t g tan wrote: > > Hi, > > > > Have done at least the following: > > 1 - fresh ports cvsup for all the ports > > 2 - rm /var/db/pkg/pkgdb.db > > 3

Re: portsdb -U fails

2004-01-30 Thread Kent Stewart
On Friday 30 January 2004 11:51 am, r t g tan wrote: > Hi, > > Have done at least the following: > 1 - fresh ports cvsup for all the ports > 2 - rm /var/db/pkg/pkgdb.db > 3 - pkgdb -F > > However portsdb -U fails and generates a lot of > error messages like the

Re: portsdb -U fails

2004-01-30 Thread Kris Kennaway
On Fri, Jan 30, 2004 at 08:51:43PM +0100, r t g tan wrote: > Hi, > > Have done at least the following: > 1 - fresh ports cvsup for all the ports > 2 - rm /var/db/pkg/pkgdb.db > 3 - pkgdb -F > > However portsdb -U fails and generates a lot of > error

portsdb -U fails

2004-01-30 Thread r t g tan
Hi, Have done at least the following: 1 - fresh ports cvsup for all the ports 2 - rm /var/db/pkg/pkgdb.db 3 - pkgdb -F However portsdb -U fails and generates a lot of error messages like the following: *** Error code 2: malformed entry: *** Error code 2 *** Error code 2: malformed