I also was getting these errors, along with some odd behaviour in the ports
tree. I ended up simply blasting out my src and cvs files and pulling
everything down from scratch. Certainly a case of useing a broadswoard for a
letter opener, but it worked.
If you're getting these errors, be aware tha
On Mon, 25 Jun 2001, Scott Lambert wrote:
> It should have been cleared up by now with a nightly cvsup. Mine boxes just
> had the two instances where they downloaded all the libpam stuff. After that,
> it was business as usual.
>
> So, are you saying you get to download those files each time yo
On Tue, Jun 26, 2001 at 08:59:03AM +1200, Juha Saarinen wrote:
> On Mon, 25 Jun 2001, Scott Lambert wrote:
>
> > But how many CVSups on each machine.
>
> I run a daily cvsup cron job (well, it's nightly, really). I get the error
> messages if I do 'make update' in /usr/src as well.
>
>
> > The
On Mon, 25 Jun 2001, Scott Lambert wrote:
> But how many CVSups on each machine.
I run a daily cvsup cron job (well, it's nightly, really). I get the error
messages if I do 'make update' in /usr/src as well.
> There was a commit of libpam stuff that
> didn't work. Some time later the commit w
On Tue, Jun 26, 2001 at 08:36:18AM +1200, Juha Saarinen wrote:
> On Mon, 25 Jun 2001, John Polstra wrote:
>
> > No fix is needed. The message is telling you that CVSup has noticed
> > a problem and is fixing it itself. CVSup _will_not_ give you a bad
> > update unless your underlying hardware (
