On 2013-10-31 14:29, Matthias Apitz wrote: > > Hello, > > I have the following problem while updating an item in the ports tree: > > the SVN checkout was done on October 1; when I do now > > # cd /usr/ports/net > # rm -r vnc > # svn up vnc > Updating 'vnc': > Restored 'vnc' > Restored 'vnc/pkg-plist' > Restored 'vnc/Makefile' > Restored 'vnc/distinfo' > Restored 'vnc/pkg-descr' > Restored 'vnc/files' > Restored 'vnc/files/FreeBSD.cf-patch' > Restored 'vnc/files/extra-patch-xc-config-util-printver.c' > Restored 'vnc/files/vnc.def-patch' > Restored 'vnc/files/extra-patch-fix_Xvnc_no_valid_address' > Restored 'vnc/files/patch-unix-xc-programs-Xserver-vnc-Imakefile' > Restored 'vnc/files/extra-patch-xfree86' > Restored 'vnc/files/patch-unix-x0vncserver-x0vncserver.cxx' > Restored 'vnc/files/patch-unix-xc-programs-Xserver-vnc-XserverDesktop.h' > Restored 'vnc/files/patch-xc-programs-Xserver-vnc-vncExtInit.cc' > At revision 332203. > > some files are missing (marked below) > > also a > > # rm -r vnc > # svn co svn://svn.freebsd.org/ports/head/net/vnc > > does not help; only doing the checkout in an empty space like > > # cd /tmp > # svn co svn://svn.freebsd.org/ports/head/net/vnc > A vnc/pkg-plist > A vnc/Makefile > A vnc/distinfo > A vnc/pkg-descr > A vnc/files > A vnc/files/patch-unix-tx-TXImage.cxx > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > A vnc/files/patch-unix-x0vncserver-x0vncserver.cxx > A vnc/files/patch-common-network-TcpSocket.cxx > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > A vnc/files/patch-unix-xc-programs-Xserver-vnc-XserverDesktop.h > A vnc/files/patch-xc-programs-Xserver-vnc-vncExtInit.cc > A vnc/files/FreeBSD.cf-patch > A vnc/files/extra-patch-xc-config-util-printver.c > A vnc/files/vnc.def-patch > A vnc/files/extra-patch-fix_Xvnc_no_valid_address > A vnc/files/patch-unix-x0vncserver-Image.cxx > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > A vnc/files/patch-unix-xc-programs-Xserver-vnc-Imakefile > A vnc/files/extra-patch-xfree86 > Checked out revision 332240. > > brings the marked files to my disk; why is this? It's more interesting to look with `svn stat' if your copy has cached some local modifications or blocking conflicts from local editing. Tip: running from time to time the command `svn cleanup' should prevent this issue. http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.cleanup.html Nice side effect from `svn cleanup' > du -h -d1 /usr/ports/.svn/ 619M /usr/ports/.svn/pristine 2.0k /usr/ports/.svn/tmp 695M /usr/ports/.svn/ > find /usr/ports/.svn/ -type f | wc -l 134004 > svn cleanup > du -h -d1 /usr/ports/.svn/ 430M /usr/ports/.svn/pristine 2.0k /usr/ports/.svn/tmp 506M /usr/ports/.svn/ > find /usr/ports/.svn/ -type f | wc -l 117269 PS: If you even want to get back some more space try the command > sqlite3 .svn/wc.db "vacuum" -- Regards, olliReceived on Thu Oct 31 2013 - 20:05:33 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:43 UTC