| Summary: | cvs-1.12.1[0-2] spits out a lot of errors when none exist | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | SpanKY <vapier> |
| Component: | [OLD] Development | Assignee: | Maintainers for cvs, and cvs related tools (the version control system) [OBSOLETE] <cvs-utils+obsolete> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://ccvs.cvshome.org/issues/show_bug.cgi?id=249 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | uclibc.tar.bz2 | ||
|
Description
SpanKY
2004-11-21 20:07:03 UTC
just committed cvs-1.12.11 - does that by any chance solve your problem? 1.12.11 does the same crap just noticed the following today: rm ~/.cvsrc cvs up # works fine cvs up -P # works fine cvs up -d # spits errors cvs up -Pd # spits errors ive always had 'update -P -d' in my ~/.cvsrc which is why i started getting these errors 1.12.12 does the same crap spanky: for a directory where you get these errors, please post up the output, and the contents of CVS/Entries Created attachment 58163 [details]
uclibc.tar.bz2
looks like it just cant handle subdirectories or something, here's the output:
root@vapier 0 uclibc # cvs-1.12.9 up
root@vapier 0 uclibc # cvs-1.12.12 up
cvs-1.12.12 update: move away `arm/2.4/packages'; it is in the way
C arm/2.4/packages
cvs-1.12.12 update: move away `arm/2.4/parent'; it is in the way
C arm/2.4/parent
cvs-1.12.12 update: move away `arm/armeb/make.defaults'; it is in the way
C arm/armeb/make.defaults
cvs-1.12.12 update: move away `arm/armeb/parent'; it is in the way
C arm/armeb/parent
cvs-1.12.12 update: move away `arm/armeb/2.4/packages'; it is in the way
C arm/armeb/2.4/packages
cvs-1.12.12 update: move away `arm/armeb/2.4/parent'; it is in the way
C arm/armeb/2.4/parent
cvs-1.12.12 update: move away `mips/mipsel/hardened/make.defaults'; it is in
the way
C mips/mipsel/hardened/make.defaults
cvs-1.12.12 update: move away `mips/mipsel/hardened/parent'; it is in the way
C mips/mipsel/hardened/parent
cvs-1.12.12 update: move away `x86/2.4/packages'; it is in the way
C x86/2.4/packages
cvs-1.12.12 update: move away `x86/2.4/parent'; it is in the way
C x86/2.4/parent
cvs-1.12.12 update: move away `x86/hardened/2.4/packages'; it is in the way
C x86/hardened/2.4/packages
cvs-1.12.12 update: move away `x86/hardened/2.4/parent'; it is in the way
C x86/hardened/2.4/parent
root@vapier 0 uclibc # cd arm
root@vapier 0 arm # cvs-1.12.12 up
cvs-1.12.12 update: move away `2.4/packages'; it is in the way
C 2.4/packages
cvs-1.12.12 update: move away `2.4/parent'; it is in the way
C 2.4/parent
cvs-1.12.12 update: move away `armeb/make.defaults'; it is in the way
C armeb/make.defaults
cvs-1.12.12 update: move away `armeb/parent'; it is in the way
C armeb/parent
cvs-1.12.12 update: move away `armeb/2.4/packages'; it is in the way
C armeb/2.4/packages
cvs-1.12.12 update: move away `armeb/2.4/parent'; it is in the way
C armeb/2.4/parent
root@vapier 0 arm # cd 2.4
root@vapier 0 2.4 # cvs-1.12.12 up
root@vapier 0 2.4 #
my current ~/.cvsrc since it matters: cvs -q -z2 diff -uN #checkout -P update -Pd like i said in Comment #3, if i drop the '-d' from the update param, it'll stop showing errors Hmm, strange. I can't reproduce the error on my side at all, even with the identical version of cvs and your .cvsrc. As a test, could you try this: mv /usr/portage/profiles/uclibc /tmp/uclibc (totally outside the CVS tree) cd /usr/portage/profiles cvs up and see if it still throws the errors? ok, did that, and found the issue when i ran a `diff -ur` between the trees the dirs that are giving me problems, the CVS/Root file is missing a trailing / bad: root@vapier 1 hardened # cat 2.4/CVS/Root vapier@cvs.gentoo.org:/var/cvsroot root@vapier 1 hardened # cvs-1.12.12 up cvs-1.12.12 update: move away `2.4/packages'; it is in the way C 2.4/packages cvs-1.12.12 update: move away `2.4/parent'; it is in the way C 2.4/parent root@vapier 1 hardened # good: root@vapier 1 hardened # cat 2.4/CVS/Root vapier@cvs.gentoo.org:/var/cvsroot/ root@vapier 1 hardened # cvs-1.12.12 up root@vapier 1 hardened # root@vapier 0 uclibc # cat `find -name Root -iwholename '*/CVS/*'` | grep 'cvsroot/$' | wc -l 14 root@vapier 0 uclibc # cat `find -name Root -iwholename '*/CVS/*'` | grep 'cvsroot$' | wc -l 4 hmm, I wonder how that happened that you have some without the /. definetly an upstream issue :-). 'UPSTREAM' as in 'we arent going to look at it and if you want it fixed i have to file a bug upstream myself' ? :P the diff between 1.12.9 and 1.12.10 is 1Mb+ (after excluding another 5Mb of junk) and a lot of changes to the path handling. I can't trace the error in it myself. Absolutely all of my machines have the trailing /, and they have seen practically every version of CVS since 1.10.something. So I think while it is an upstream issue, it's very minor (since it only seems to affect you ;-). so the answer is 'please take this upstream' :p will do |
