On Fri, 17 May 2002, Jeremy C. Reed wrote:

> "cvs update -d -P" under /usr/src (using Tag "Tnetbsd-1-5"). (It first
> hung and a few hours later I killed and started again; it completed 138
> minutes later.)

So you did "cvs update -d -P -rnetbsd-1-5", or something else?

> Did a "make obj" under /usr/src; in two minutes, it stopped at:
>
> obj ===> sys/dev/wscons
> make: don't know how to make obj. Stop
>
> >From looking at my cvs update logs, I see many messages like:
> "cvs server: sys/dev/wscons/Makefile is no longer in the repository".
>
> But I didn't see any reference to these wscons changes/removals in
> CHANGES-1.5.3.

That file has not been removed from the repository. It's still there,
for me, in sys/dev/wscons, after

	cvs update -rnetbsd-1-5 Makefile

and

	cvs update -rnetbsd-1-5-PATCH003 Makefile

and

	cvs update -A Makefile

But watch what happens if I give a bogus tag:

	cvs update -rfoo Makefile
	cvs server: Makefile is no longer in the repository

I suspect that you mistyped, in which case "cvs" would have happily
deleted nearly everything in your checkout, and it would take it's
time doing it, too. It could also be that the repository you used is
corrupt. Can you check out that one file, now?

> Any ideas on what I should do to get around this issue?

Checking out a clean tree via anoncvs is fairly inefficient. If you're
checkout turn out to be deeply borked, it might make sense to restore
it by downloading and untarring the entire contents of

  ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-release-1-5/tar_files/src/

before trying "update" again (perhaps with a "cvs -d ... update ..."),
to specify a different repository than the one in the tarballs.

Frederick