Re: Problem pulling particular directory from CVS
At 1:27 PM -0800 2002/11/29, Paul A. Scott wrote: Damn. I keep forgetting about the Mac OSX stupid, case-insesitive HFS+. Yeah, I've bitched about this for years. I mean, HFS was an improvement over MFS (can you imagine a filesystem structure that keeps everything at one level and doesn't use directories at all?), but they really blew chunks on this. Of course, HFS+ is only a minor improvement over HFS. But then, HFS is way, way better than MS-DOS 8.3, which is what it was being compared with at the time. Ya know, Apple stated on their Web site, "there is never any good reason to have a case-sensitive file system." Can you believe that? I wrote back to them and stated, "there is never any good reason to have a case-INsensitive filesystem." But, of course, they never replied. :) Try bitching at Jordan. Maybe he can get them to fix UFS instead. -- Brad Knowles, <[EMAIL PROTECTED]> "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
>> The cvs on MacOSX does not [work]. My mistake. > From: Mike Bristow <[EMAIL PROTECTED]> > CVS works just fine - it's just that the filesystem is case insensitive > [1], so when you check out src/contrib, the distinction between > src/contrib/CVS [2] src/contrib/cvs is lost, and Bad Shit happens. Damn. I keep forgetting about the Mac OSX stupid, case-insesitive HFS+. I HATE that! It's burned me more than once. Unfortunately, moving to UFS is not an option for a whole host of reasons. Ya know, Apple stated on their Web site, "there is never any good reason to have a case-sensitive file system." Can you believe that? I wrote back to them and stated, "there is never any good reason to have a case-INsensitive filesystem." But, of course, they never replied. :) > Try using Disk Copy to setup and mount a blank (UFS) image, or having a > separate UFS partition. I did this and cvs now works perfectly. Thanks for the great tip. I REALLY appreciate it. > [1] Unless your filesystem is UFS, rather than HFS+, in which case > you'll have lots of interesting other problmes. I know. I once tried to move to UFS. Big mistake. Apple's UFS limits file sizes to 2GB, and it doesn't support meta-data. > [2] CVS keeps a shedload of metadata here Ahhh. Since the topic has moved from FreeBSD to Apple Mac OSX, it's now off-topic and I should now kill this thread. Paul -- Paul A. Scott mailto:[EMAIL PROTECTED] http://skycoast.us/pscott/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
On Wednesday, November 27, 2002, at 11:34 pm, Paul A. Scott wrote: Oh, #$%@. I'm so embarrassed. My terminal session was logged into Mac OSX not FreeBSD, and I had mirrored the same directory structure, so I faked myself out. Bottom line is, cvs on Freebsd works like a champ. The cvs on MacOSX does not. My mistake. And I humbly appolgize for the stupid user error. CVS works just fine - it's just that the filesystem is case insensitive [1], so when you check out src/contrib, the distinction between src/contrib/CVS [2] src/contrib/cvs is lost, and Bad Shit happens. Try using Disk Copy to setup and mount a blank (UFS) image, or having a separate UFS partition. [1] Unless your filesystem is UFS, rather than HFS+, in which case you'll have lots of interesting other problmes. [2] CVS keeps a shedload of metadata here -- Am I getting older, or are these shows getting more entertaining? -- Flash, on Children in Need. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
Oh, #$%@. I'm so embarrassed. My terminal session was logged into Mac OSX not FreeBSD, and I had mirrored the same directory structure, so I faked myself out. Bottom line is, cvs on Freebsd works like a champ. The cvs on MacOSX does not. My mistake. And I humbly appolgize for the stupid user error. Let's just forget the whole thing. Thanks for all your help. Paul -- Paul A. Scott mailto:[EMAIL PROTECTED] http://skycoast.us/pscott/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
> setenv CVSROOT ":pserver:[EMAIL PROTECTED]:/home/ncvs"
> cvs login
> cvs co src/contrib
> From: Terry Lambert <[EMAIL PROTECTED]>
>> Nothing hidden, totally forthright.
>
> Except that's a different error than the one you said before. 8-).
No. I posted this same question at least 4 times (although sometimes to
questions and sometimes to current). The last time I left out the
src/contrib/cvs connection, but that's only because it seemed redundant. My
fault. I've always reported the same error though.
> This particular error usually when you are doing this
> as root, and have an overly-anal umask set. To correct it, you
> should delete the subtree from that point, and at an upper level,
> type:
>
> cvs update -d
>
> The subdirectories that would have been included in the original
> checkout will be brought in and created ("-d"), without you
> needing to repeat the "checkout".
That doesn't help. And I'm not running as root, either.
>>> Probably you can get around the problem by updating your 'cvs',
>> Running 'cvs -v' on FreeBSD 4.7:
>> Concurrent Versions System (CVS) 1.11.1p1-FreeBSD (client/server)
>>
>> This version works.
> I still find it hard to believe you aren't using a particular tag;
> the other procedure outlined above should work for you with the
> old CVS against the error message you are getting now.
Well, believe it. It couldn't be more simple. Start with a totally blank
working directory, do (with cvs 1.0 from FreeBSD 4.5):
setenv CVSROOT ":pserver:[EMAIL PROTECTED]:/home/ncvs"
cvs login
cvs co src/contrib
and the checkout stops on src/contrib/cvs
Plain and simple. Period. Nothing hidden.
> One possibility is that the source tree you are doing has a stick
> tag set?
I don't know. I am not the owner or a developer, so I can't see the source
tree except by checking it out, which I can't.
> In any case, if you have a workaround, you're probably more
> interested in the fact it works than in why. 8-) 8-).
Not true, I'm very interested in knowing what the problem is. It's true that
I'm happy to have a workaround (for which I thank you), but I'd sure like to
know why this happened in the first place.
Paul
--
Paul A. Scott
mailto:[EMAIL PROTECTED]
http://skycoast.us/pscott/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
On 2002-11-27 12:48, "Paul A. Scott" <[EMAIL PROTECTED]> wrote: > > > You are not being quite forthright, I think. > > Actually, I've been totally forthright. I start with an empty working > directory, and type: > > setenv CVSROOT ":pserver:[EMAIL PROTECTED]:/home/ncvs" > cvs login > cvs co src/contrib Hmmm. Can you try doing the same in parts? $ CVSROOT=':pserver:[EMAIL PROTECTED]:/home/ncvs' $ export CVSROOT $ cvs -q co -l src $ cd src $ cvs -q up -Adl contrib $ cvs -q up -APd contrib/cvs See if this works... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
"Paul A. Scott" wrote:
> setenv CVSROOT ":pserver:[EMAIL PROTECTED]:/home/ncvs"
> cvs login
> cvs co src/contrib
>
> When it gets to directory src/contrib/cvs, I get:
>
> cvs checkout: cannot open CVS/Entries for reading: No such file or directory
> cvs [checkout aborted]: cannot write : No such file or
> directory
>
> Nothing hidden, totally forthright.
Except that's a different error than the one you said before. 8-).
This particular error usually when you are doing this
as root, and have an overly-anal umask set. To correct it, you
should delete the subtree from that point, and at an upper level,
type:
cvs update -d
The subdirectories that would have been included in the original
checkout will be brought in and created ("-d"), without you
needing to repeat the "checkout".
> > Probably you can get around the problem by updating your 'cvs',
>
> Running 'cvs -v' on FreeBSD 4.5:
> Concurrent Versions System (CVS) 1.10 `Halibut' (client/server)
>
> This version breaks on checkout of src/contrib/cvs
>
> Running 'cvs -v' on FreeBSD 4.7:
> Concurrent Versions System (CVS) 1.11.1p1-FreeBSD (client/server)
>
> This version works.
>
> Thanks. I'll update my cvs.
I still find it hard to believe you aren't using a particular tag;
the other procedure outlined above should work for you with the
old CVS against the error message you are getting now.
One possibility is that the source tree you are doing has a stick
tag set?
In any case, if you have a workaround, you're probably more
interested in the fact it works than in why. 8-) 8-).
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
> You are not being quite forthright, I think. Actually, I've been totally forthright. I start with an empty working directory, and type: setenv CVSROOT ":pserver:[EMAIL PROTECTED]:/home/ncvs" cvs login cvs co src/contrib When it gets to directory src/contrib/cvs, I get: cvs checkout: cannot open CVS/Entries for reading: No such file or directory cvs [checkout aborted]: cannot write : No such file or directory Nothing hidden, totally forthright. > This normally happens on a cvs -R co, rather than a cvs co, when > you are asking for a specific date tag or a release tag which > no longer exists, when running against a read-only repository. As you can see, that's not the case. > Probably you can get around the problem by updating your 'cvs', Running 'cvs -v' on FreeBSD 4.5: Concurrent Versions System (CVS) 1.10 `Halibut' (client/server) This version breaks on checkout of src/contrib/cvs Running 'cvs -v' on FreeBSD 4.7: Concurrent Versions System (CVS) 1.11.1p1-FreeBSD (client/server) This version works. Thanks. I'll update my cvs. Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
"Paul A. Scott" wrote:
> I do the following:
> cvs co src/contrib
> cvs checkout: in directory src/contrib/cvs:
> cvs checkout: cannot open CVS/Entries for reading: No such file or directory
> cvs [checkout aborted]: cannot write : No such file or
> directory
>
> cvs co stops on the src/contrib/cvs directory and will not go further. I
> have plenty of space available on the file system. The problem may be a
> corrupt repository.
>
> Is there any way to do a checkout on src/contrib while bypassing
> src/contrib/cvs? Or, can this be fixed to work?
You are not being quite forthright, I think.
This normally happens on a cvs -R co, rather than a cvs co, when
you are asking for a specific date tag or a release tag which
no longer exists, when running against a read-only repository.
I ran into a similar problem recently, when someone suggested
I use cvs against a FreeBSD server in German, in order to match
their version of the source code so I could create a patch for
a problem they were having.
The answer is that the val-tags file is not writeable, and is
being used.
There was a long discussion on this file ablot 6 months back;
I believe the resolution of that discussion was to make the
${CVSROOT}/CVSROOT/val-tags file unnecessary, but advisory, in
the case that it was not writeable.
Probably you can get around the problem by updating your 'cvs',
though it may also be necessary to update the 'cvs' on the
remote host to have the new code, as well.
You can also checkout without a tag, or with a tag that is already
in the val-tags file on the serving host.
Alternately, have them add a line to val-tags with the tag you
want to checkout, e.g. [indentation mine]:
RELENG_2_2_2_RELEASE y
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
On 2002-11-27 02:01, "Paul A. Scott" <[EMAIL PROTECTED]> wrote: > I do the following: > > cvs co src/contrib > > and I get: > ... > cvs checkout: in directory src/contrib/cvs: > cvs checkout: cannot open CVS/Entries for reading: No such file or directory > cvs [checkout aborted]: cannot write : No such file or > directory Hmmm. What do the following print? % ls -bdlo src % ls -bdlo src/contrib % ls -bloF src/contrib/cvs BTW, it's a lot better to use CVSup for pulling the sources. It puts less strain on the servers, IIRC. - Giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problem pulling particular directory from CVS
I do the following: cvs co src/contrib and I get: . . . cvs server: Updating src/contrib/bison cvs server: Updating src/contrib/bzip2 cvs server: Updating src/contrib/com_err cvs server: Updating src/contrib/cpio cvs checkout: in directory src/contrib/cvs: cvs checkout: cannot open CVS/Entries for reading: No such file or directory cvs [checkout aborted]: cannot write : No such file or directory cvs co stops on the src/contrib/cvs directory and will not go further. I have plenty of space available on the file system. The problem may be a corrupt repository. Is there any way to do a checkout on src/contrib while bypassing src/contrib/cvs? Or, can this be fixed to work? Thanks, Paul -- Paul A. Scott mailto:[EMAIL PROTECTED] http://skycoast.us/pscott/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
