no idea what's going on here but 1.12.10 is giving me a lot of errors when 1.12.9 works just fine for example: root@vapier 0 binutils # pwd /usr/local/gentoo-x86/sys-devel/binutils root@vapier 0 binutils # cvs up root@vapier 0 binutils # cvs-1.12.10 up cvs-1.12.10 update: move away `files/2.15/05_all_binutils-2.15-elf32-arm-textrel.patch'; it is in the way C files/2.15/05_all_binutils-2.15-elf32-arm-textrel.patch cvs-1.12.10 update: move away `files/2.15/40_all_binutils-uclibc-linker.patch'; it is in the way C files/2.15/40_all_binutils-uclibc-linker.patch cvs-1.12.10 update: move away `files/2.15/52_all_binutils-20040527-uclibc-100-conf.patch'; it is in the way C files/2.15/52_all_binutils-20040527-uclibc-100-conf.patch and another: root@vapier 0 gentoo-x86 # pwd /usr/local/gentoo-x86 root@vapier 0 gentoo-x86 # cvs up app-accessibility root@vapier 0 gentoo-x86 # cvs-1.12.10 up app-accessibility cvs update: nothing known about app-accessibility Portage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041006-r0, 2.6.10-rc2 i686) ================================================================= System uname: 2.6.10-rc2 i686 Intel(R) Pentium(R) 4 CPU 1.80GHz Gentoo Base System version 1.6.6 distcc 2.18.2 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r6,sys-devel/autoconf-2.13 Automake: sys-devel/automake-1.5,sys-devel/automake-1.9.3,sys-devel/automake-1.8.5-r2,sys-devel/automake-1.7.9,sys-devel/automake-1.6.3,sys-devel/automake-1.4_p6 Binutils: sys-devel/binutils-1,sys-devel/binutils-1-r1,sys-devel/binutils-2.15.92.0.2-r1,sys-devel/binutils-1-r2,sys-devel/binutils-1-r3,sys-devel/binutils-1-r4,sys-devel/binutils-1-r5,sys-devel/binutils-2.15.92.0.2-r2 Headers: sys-kernel/linux26-headers-1,sys-kernel/linux26-headers-2.6.8.1-r2 Libtools: sys-devel/libtool-1.5.10 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-pipe -march=pentium4 -O2 -frename-registers -fomit-frame-pointer -mmmx -msse -msse2 -fdelete-null-pointer-checks -funroll-loops -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /opt/glftpd/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-pipe -march=pentium4 -O2 -frename-registers -fomit-frame-pointer -mmmx -msse -msse2 -fdelete-null-pointer-checks -funroll-loops -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache cvs distlocks noauto noinfo sandbox sfperms sign" GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo" MAKEOPTS="-j4" PKGDIR="/mnt/space/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://gentoo/gentoo-portage" USE="X aalib acl acpi adns alsa apache2 avi bitmap-fonts cdr crypt cscope cups dedicated dga directfb dvd dvdr emu10k1 encode esd f77 fbcon flac flash foomaticdb fortran gd gd-external gdbm gif gpm gstreamer gtk gtk2 imagemagick imap imlib ipv6 joystick jpeg kde libwww mad maildir mikmod mmx moznocompose moznoirc moznomail mpeg mysql nas ncurses nls nocardbus nptl nptlonly offensive oggvorbis opengl oss pam pdflib perl php pic plotutils png pnp python quicktime readline samba sdl skey slp snmp socks5 speex spell sqlite sse ssl svga tcltk tcpd tiff truetype wavelan x86 xine xml xml2 xmms xv zlib video_cards_nvidia"
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
