Re: ports-collection borked?

2004-07-22 Thread Svein Halvor Halvorsen

[Kent Stewart, 2004-07-21]
  Sometimes mirrors break. The only way to find out is to try a different
  one. The port fastest_cvsup is a good starting point. Just remember
  that the closest may not produce the overall fastest cvsup.

Not that I've tested this in any scientific manner, but I think the
closest one is also the fastest in my case, as it is on the same
/16-network that I'm on. In fact it's only about a km away, and it's 2Gbps
all the way from my dorm room to the mirror, so I think my 10/100 nic is
the limiting factor here.

It could be out of sync or something, though. Whatever it was, it seems to
be in order now (it may still be somewhat behind the master cvs-server,
but the fixed index has at least found its way to the mirror now. And
from there to my box.)


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


ports-collection borked?

2004-07-21 Thread Svein Halvor Halvorsen

When rebuilding the index after cvsup-ing the ports collection I get lots
and lots of these lines:

/usr/ports/INDEX-5:11379:Port info line must consist of 10 fields.


This from a 15 min old port collection. The same happened earlier today
(which is why I retried just now). Is this a local problem, or is the
collection borken. Is there anything I could do locally?


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


Re: ports-collection borked?

2004-07-21 Thread Kent Stewart
On Wednesday 21 July 2004 11:57 am, Svein Halvor Halvorsen wrote:
 When rebuilding the index after cvsup-ing the ports collection I get
 lots and lots of these lines:

 /usr/ports/INDEX-5:11379:Port info line must consist of 10 fields.


 This from a 15 min old port collection. The same happened earlier
 today (which is why I retried just now). Is this a local problem, or
 is the collection borken. Is there anything I could do locally?



Your make.conf and installed ports can affect the INDEX build. The USE_ 
or WITH_ adds features. My make.conf files don't have anything of that 
nature.

FWIW, I grabbed the cvsup16 1900 UTC update and had no problems building 
an INDEX on 4-stable or 5-current. Right now, I use portindex to build 
INDEX[-5]. The messages like you were seeing were occuring yesterday I 
tried a make index on 4-stable around 0700 UTC and didn't have any 
problem with 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: ports-collection borked?

2004-07-21 Thread 3BSD
On Wed, 21 Jul 2004 20:57:25 +0200 (CEST), Svein Halvor Halvorsen
[EMAIL PROTECTED] wrote:
 
 When rebuilding the index after cvsup-ing the ports collection I get lots
 and lots of these lines:
 
 /usr/ports/INDEX-5:11379:Port info line must consist of 10 fields.
 
 This from a 15 min old port collection. The same happened earlier today
 (which is why I retried just now). Is this a local problem, or is the
 collection borken. Is there anything I could do locally?

I did a cvsup after I read your e-mail just now and it finished
updating successfully, so its a problem on your end, unfortunately, I
can't help you with the problem since I've never had to encounter one
like it before. Sorry, hope I was of more help.

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


Re: ports-collection borked?

2004-07-21 Thread Dan Rue
On Wed, Jul 21, 2004 at 12:47:29PM -0700, 3BSD wrote:
 On Wed, 21 Jul 2004 20:57:25 +0200 (CEST), Svein Halvor Halvorsen
 [EMAIL PROTECTED] wrote:
  
  When rebuilding the index after cvsup-ing the ports collection I get lots
  and lots of these lines:
  
  /usr/ports/INDEX-5:11379:Port info line must consist of 10 fields.
  
  This from a 15 min old port collection. The same happened earlier today
  (which is why I retried just now). Is this a local problem, or is the
  collection borken. Is there anything I could do locally?
 
 I did a cvsup after I read your e-mail just now and it finished
 updating successfully, so its a problem on your end, unfortunately, I
 can't help you with the problem since I've never had to encounter one
 like it before. Sorry, hope I was of more help.

I can confirm the problem cvsup'd this morning and can't portsdb -Uu
without getting all those 10 fields lines..

5.2.1-RELEASE-p3, fwiw

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


Re: ports-collection borked?

2004-07-21 Thread Soo-Hyun Choi
On my side, the cvsup server is running without any problem. I think it
could be figured out if you use another cvs server. If it still generates
the same messages, it may be no longer a server problem.

Soo-Hyun


- Original Message - 
From: Dan Rue [EMAIL PROTECTED]
To: 3BSD [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, July 21, 2004 9:00 PM
Subject: Re: ports-collection borked?


 On Wed, Jul 21, 2004 at 12:47:29PM -0700, 3BSD wrote:
  On Wed, 21 Jul 2004 20:57:25 +0200 (CEST), Svein Halvor Halvorsen
  [EMAIL PROTECTED] wrote:
  
   When rebuilding the index after cvsup-ing the ports collection I get
lots
   and lots of these lines:
  
   /usr/ports/INDEX-5:11379:Port info line must consist of 10 fields.
  
   This from a 15 min old port collection. The same happened earlier
today
   (which is why I retried just now). Is this a local problem, or is the
   collection borken. Is there anything I could do locally?
 
  I did a cvsup after I read your e-mail just now and it finished
  updating successfully, so its a problem on your end, unfortunately, I
  can't help you with the problem since I've never had to encounter one
  like it before. Sorry, hope I was of more help.

 I can confirm the problem cvsup'd this morning and can't portsdb -Uu
 without getting all those 10 fields lines..

 5.2.1-RELEASE-p3, fwiw

 dan
 ___
 [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]


Re: ports-collection borked?

2004-07-21 Thread Kent Stewart
On Wednesday 21 July 2004 01:00 pm, Dan Rue wrote:
 On Wed, Jul 21, 2004 at 12:47:29PM -0700, 3BSD wrote:
  On Wed, 21 Jul 2004 20:57:25 +0200 (CEST), Svein Halvor Halvorsen
 
  [EMAIL PROTECTED] wrote:
   When rebuilding the index after cvsup-ing the ports collection I
   get lots and lots of these lines:
  
   /usr/ports/INDEX-5:11379:Port info line must consist of 10
   fields.
  
   This from a 15 min old port collection. The same happened earlier
   today (which is why I retried just now). Is this a local problem,
   or is the collection borken. Is there anything I could do
   locally?
 
  I did a cvsup after I read your e-mail just now and it finished
  updating successfully, so its a problem on your end, unfortunately,
  I can't help you with the problem since I've never had to encounter
  one like it before. Sorry, hope I was of more help.

 I can confirm the problem cvsup'd this morning and can't portsdb -Uu
 without getting all those 10 fields lines..

 5.2.1-RELEASE-p3, fwiw


My mirror updates on the odd hours + 30. It takes a while to build a 
make index on 5-current and make index worked. 

I saw the 10 field messages for a short time yesterday but don't 
remember if it was for  the index build or the INDEX.db build. It was 
in an off hour cron job where I saw them and so they weren't logged. I 
haven't seen them since but I also switched to using portindex because 
I can create an INDEX[-5] in less than a minute. The first time 
portindex is run, it fills a database and it is very fast the next 
time.

Do you have any options in your /etc/make.conf to specify any features?

Kris is on vaction and the fetchindex option has been turned off. 
Something crashed and he didn't have time to fix 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: ports-collection borked?

2004-07-21 Thread Svein Halvor Halvorsen

[Kent Stewart, 2004-07-21]
  I saw the 10 field messages for a short time yesterday but don't
:
  Do you have any options in your /etc/make.conf to specify any features?


It now seems to work. All I did was to cvsup again.

It seems that most people experienced this yesterday. Could it be that I'm
fetching the ports collection from a mirror, and that this is causing a
time delay in the distribution of the files?

Anyway... all's good now :)



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


Re: ports-collection borked?

2004-07-21 Thread Kent Stewart
On Wednesday 21 July 2004 03:53 pm, Svein Halvor Halvorsen wrote:
 [Kent Stewart, 2004-07-21]

   I saw the 10 field messages for a short time yesterday but don't
 
   Do you have any options in your /etc/make.conf to specify any
  features?

 It now seems to work. All I did was to cvsup again.

 It seems that most people experienced this yesterday. Could it be
 that I'm fetching the ports collection from a mirror, and that this
 is causing a time delay in the distribution of the files?

 Anyway... all's good now :)



If you aren't an official mirror you have to cvsup from a mirror.

Sometimes mirrors break. The only way to find out is to try a different 
one. The port fastest_cvsup is a good starting point. Just remember 
that the closest may not produce the overall fastest cvsup.

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]