Mark Ovens wrote:
I'll try pulling a new tree using CVSup instead.
That did the trick; I zapped src/ and ports/ and started again with
CVSup (pulling the trees directly, prefix=/usr, rather than via a local
repository).
Thanks again.
Regards,
Mark
Thanks for your help guys.
Regards,
Mark
Loren M. Lang wrote:
On Sat, Mar 13, 2004 at 01:00:38AM +, Mark Ovens wrote:
Kris Kennaway wrote:
On Fri, Mar 12, 2004 at 07:51:48PM +, Mark Ovens wrote:
Surely not? I was advised that a problem I'm experiencing is
fixed in -current. I just updated my source tree to -current
with ''cvs co
On Sat, Mar 13, 2004 at 01:00:38AM +, Mark Ovens wrote:
> Kris Kennaway wrote:
> >On Fri, Mar 12, 2004 at 07:51:48PM +, Mark Ovens wrote:
> >>Surely not? I was advised that a problem I'm experiencing is fixed in
> >>-current. I just updated my source tree to -current with ''cvs co src/''
Kris Kennaway wrote:
On Fri, Mar 12, 2004 at 07:51:48PM +, Mark Ovens wrote:
Surely not? I was advised that a problem I'm experiencing is fixed in
-current. I just updated my source tree to -current with ''cvs co src/''
but no files have been updated :-/
Did you cvsup your CVS repository firs
On Fri, Mar 12, 2004 at 07:51:48PM +, Mark Ovens wrote:
> Surely not? I was advised that a problem I'm experiencing is fixed in
> -current. I just updated my source tree to -current with ''cvs co src/''
> but no files have been updated :-/
Did you cvsup your CVS repository first?
Kris
pgp
