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_describe_pass1 and change the 'make -j3' to
   'make'.
   
   Kris
  
  Hi Kris,
  
  The following line from /usr/local/sbin/make_describe_pass1:
  
  open(|cd #{dir}  make -k -j3 -f -, 'w') do |w|
  
  I changed to:
  
  open(|cd #{dir}  make -, 'w') do |w|
  
  now portsdb -U is running for quite some time.
  
  I have no idea what it is doing though.
 
 No, that's not quite what I said..just remove the -j3 and leave the other arguments 
 untouched.
 
 Kris

Hi Kris,

I did that at first but the problem still remained.

At this time I just cvsupped my ports again, and tried 
it again with:  open(|cd #{dir}  make -k -f -, 'w') do |w|

Still nu luck,

Robert




pgp0.pgp
Description: PGP signature


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 the error you receive.

kris


pgp0.pgp
Description: PGP signature


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 the meantime, you can edit
/usr/local/sbin/make_describe_pass1 and change the 'make -j3'
to 'make'.
   
Kris
  
   Hi Kris,
  
   The following line from /usr/local/sbin/make_describe_pass1:
  
 open(|cd #{dir}  make -k -j3 -f -, 'w') do |w|
  
   I changed to:
  
 open(|cd #{dir}  make -, 'w') do |w|
  
   now portsdb -U is running for quite some time.
  
   I have no idea what it is doing though.
 
  No, that's not quite what I said..just remove the -j3 and leave the
  other arguments untouched.
 
  Kris

 Hi Kris,

 I did that at first but the problem still remained.

 At this time I just cvsupped my ports again, and tried
 it again with:open(|cd #{dir}  make -k -f -, 'w') do |w|

 Still nu luck,


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't work and the other does. You just have 
to not refuse anything but ports/INDEX.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


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't work and the other does. You just have 
 to not refuse anything but ports/INDEX.
 
 Kent
 
 -- 
 Kent Stewart
 Richland, WA
 
 http://users.owt.com/kstewart/index.html

make index fails as well with a bunch of make_index: no entrie messages.

I guess Ill leave it at this waiting for it to get fixed.

Tnx all for your reply,

Robert.



pgp0.pgp
Description: PGP signature


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 currently producing clean makes.
  
  There are times when one doesn't work and the other does. You just have 
  to not refuse anything but ports/INDEX.
  
  Kent
  
  -- 
  Kent Stewart
  Richland, WA
  
  http://users.owt.com/kstewart/index.html
 
 make index fails as well with a bunch of make_index: no entrie messages.
 
 I guess Ill leave it at this waiting for it to get fixed.

It's not broken.  Please reread earlier advice given to you.

Kris


pgp0.pgp
Description: PGP signature


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 producing clean makes.
 
  There are times when one doesn't work and the other does. You just
  have to not refuse anything but ports/INDEX.
 

 make index fails as well with a bunch of make_index: no entrie
 messages.

 I guess Ill leave it at this waiting for it to get fixed.


You must be not cvsuping everything. I just updated my ports and had no 
errors with make index. I log everything and I haven't had an error 
message from make index going back to 30 Jan. I recently deleted 
everything before that date. 

Many of these error will creep in if you don't cvsup ports-all. The 
reason you refuse ports/INDEX is that cvsup will recognize that you 
replaced INDEX and download an old copy. That takes time even over my 
100mps network. Since you are going to replace it by running make index 
or portsdb -U, you might as well save your bandwidth by refusing it.

FWIW, I use both methods. I prefer make index but there are times when 
it simply dies and portsdb -U will produce useful output. It may not be 
complete but I may see 10,000+ ports instead of the 300 that make index 
produced. It pays to be flexible here but there are days when nothing 
works and the only way is to manually update the port.

I track freebsd-ports and frequently see a message from Kris' script 
before my cron job port update complains or dies from the same 
reason(s). Frequently, these messages go away in a matter of hours. 
Sometimes some port committer deserves a pointy hat but that goes with 
the territory. Any day that you don't make a mistake on a computer is a 
day that you didn't try to learn anything new. The port committers just 
get to make their mistake(s) where the whole world can see and all they 
can do is grin about it :).

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


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 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't work and the other does. You just have
   to not refuse anything but ports/INDEX.
  
   Kent
  
   --
   Kent Stewart
   Richland, WA
  
   http://users.owt.com/kstewart/index.html
 
  make index fails as well with a bunch of make_index: no entrie messages.
 
  I guess Ill leave it at this waiting for it to get fixed.

 It's not broken.  Please reread earlier advice given to you.

 Kris

Or - perhaps wiping /usr/ports and starting from the CD?


- -- 
Best regards,
Chris

-BEGIN PGP SIGNATURE-
Version: PGP 6.5.8

iQA/AwUBQB69ag+T/4DAG8NjEQJnfwCgs/Xq7GsgqzqdDcfEg0sRTuryexMAnjX3
oJaDvmgp3IV5ymwIoS5R3UNW
=fwxv
-END PGP SIGNATURE-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


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 Kris,
 
 The following line from /usr/local/sbin/make_describe_pass1:
   
   open(|cd #{dir}  make -k -j3 -f -, 'w') do |w|
 
 I changed to:
 
   open(|cd #{dir}  make -, 'w') do |w|
   
 now portsdb -U is running for quite some time.
 
 I have no idea what it is doing though.

No, that's not quite what I said..just remove the -j3 and leave the other arguments 
untouched.

Kris


pgp0.pgp
Description: PGP signature


Re: portsdb -U fails

2004-01-31 Thread r t g tan
On Fri, Jan 30, 2004 at 01:28:26PM -0800, 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 -  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
 *** Error code 2: malformed entry: *** Error code 2
 cd: can't cd to wmthemeinstall: malformed entry: cd: can't cd to wmthemeinstall
 cd: can't cd to wmx: malformed entry: cd: can't cd to wmx
 cd: can't cd to xfce: malformed entry: cd: can't cd to xfce
  
  What is corrupted, and how can I fix this?
 
 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 Kris,

The following line from /usr/local/sbin/make_describe_pass1:

open(|cd #{dir}  make -k -j3 -f -, 'w') do |w|

I changed to:

open(|cd #{dir}  make -, 'w') do |w|

now portsdb -U is running for quite some time.

I have no idea what it is doing though.

robert



pgp0.pgp
Description: PGP signature


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 entry: *** Error code 2
   *** Error code 2: malformed entry: *** Error code 2
   cd: can't cd to wmthemeinstall: malformed entry: cd: can't cd to wmthemeinstall
   cd: can't cd to wmx: malformed entry: cd: can't cd to wmx
   cd: can't cd to xfce: malformed entry: cd: can't cd to xfce

What is corrupted, and how can I fix this?

Tnx,

---
robert t g tan


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


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 -  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
 *** Error code 2: malformed entry: *** Error code 2
 cd: can't cd to wmthemeinstall: malformed entry: cd: can't cd to
  wmthemeinstall cd: can't cd to wmx: malformed entry: cd: can't cd
  to wmx cd: can't cd to xfce: malformed entry: cd: can't cd to xfce
 
  What is corrupted, and how can I fix this?

 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'.

Has your make index patch been added to the system? I didn't get 43% but 
1/3 faster was significant.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: portsdb -U fails

2004-01-30 Thread Kris Kennaway
On Fri, Jan 30, 2004 at 01:42:00PM -0800, Kent Stewart wrote:
 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 -  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
  *** Error code 2: malformed entry: *** Error code 2
  cd: can't cd to wmthemeinstall: malformed entry: cd: can't cd to
   wmthemeinstall cd: can't cd to wmx: malformed entry: cd: can't cd
   to wmx cd: can't cd to xfce: malformed entry: cd: can't cd to xfce
  
   What is corrupted, and how can I fix this?
 
  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'.
 
 Has your make index patch been added to the system? I didn't get 43% but 
 1/3 faster was significant.

Not yet..it's in testing.

Kris


pgp0.pgp
Description: PGP signature


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 entry: *** Error code 2
 *** Error code 2: malformed entry: *** Error code 2
 *** Error code 2: malformed entry: *** Error code 2
 cd: can't cd to wmthemeinstall: malformed entry: cd: can't cd to wmthemeinstall
 cd: can't cd to wmx: malformed entry: cd: can't cd to wmx
 cd: can't cd to xfce: malformed entry: cd: can't cd to xfce
 
 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'.

I remember you mail about that.  After modifying
make_describe_pass*, i still got error messages like above.  Mind
that i do not have the complete tree.


  - Parv

-- 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


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
   error messages like the following:
   
  *** Error code 2: malformed entry: *** Error code 2
  *** Error code 2: malformed entry: *** Error code 2
  *** Error code 2: malformed entry: *** Error code 2
  cd: can't cd to wmthemeinstall: malformed entry: cd: can't cd to 
   wmthemeinstall
  cd: can't cd to wmx: malformed entry: cd: can't cd to wmx
  cd: can't cd to xfce: malformed entry: cd: can't cd to xfce
  
  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'.
 
 I remember you mail about that.  After modifying
 make_describe_pass*, i still got error messages like above.  Mind
 that i do not have the complete tree.

All bets are off then.

Kris


pgp0.pgp
Description: PGP signature