[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cvs problems on 1998 Sep 7 current
On Wednesday, September 9, "William Allen Simpson" wrote:
> I ran cvs up -PAd for src for the first time in over a month on Monday
> (holiday), and had a number of problems.
> === 1
> A number of files are still hanging around here, but have been lost in
> the cvs tree:
Current is a moving target. This means that the CVS tree gets cleaned up
from time to time, and unwanted or unneeded programs and source may get
deleted entirely from the repository. When this happens, there is usually
an e-mail sent to email@example.com, telling developers about potential
> ? kerberosIV/kadm/kadm_err.h
> ? kerberosIV/kadm/kadm_err.c
> ? kerberosIV/krb/krb_err.h
> ? kerberosIV/krb/krb_err.c
These seem to have been removed.
> ? usr.bin/audioctl/audioctl
> ? usr.bin/audioctl/audioctl.cat1
> ? usr.bin/mixerctl/mixerctl
> ? usr.bin/mixerctl/mixerctl.cat1
These are a problem with your obj tree.
> ? gnu/usr.sbin/e2fsprogs/lib/et/diff3.core
> ? gnu/usr.sbin/e2fsprogs/lib/ss/diff3.core
The e2fsprogs seem to have been removed.
> === 2
> Some folks have moved around a fair number of files and directories, and
> make obj failed. I had to rm -rf /usr/obj and run make obj again.
A simple 'make obj' should have "fixed" things for you. Granted, you would
have stale objects in your obj tree...
> === 3
> The update is failing in one section of the tree, although the make
> build went OK (as far as I can tell).
> cvs server: Updating gnu/usr.sbin/e2fsprogs/lib/et
> [...lots and lots more of the same...]
Unless you have local changes in that part of the tree, the best way (that I
know of) to update that portion, is to remove it, and run the update again.