From owner-freebsd-current@FreeBSD.ORG Thu Oct 31 21:05:33 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8002B8E3 for ; Thu, 31 Oct 2013 21:05:33 +0000 (UTC) (envelope-from ohauer@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0DB9522ED for ; Thu, 31 Oct 2013 21:05:32 +0000 (UTC) Received: from [192.168.0.100] ([87.139.233.65]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MGFz9-1VPf6D2OzX-00FFys for ; Thu, 31 Oct 2013 22:05:30 +0100 Message-ID: <5272C61C.6040809@gmx.de> Date: Thu, 31 Oct 2013 22:05:32 +0100 From: olli hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: mystery problem with SVN update in /head References: <20131031132903.GA11466@sh4-5.1blu.de> In-Reply-To: <20131031132903.GA11466@sh4-5.1blu.de> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:D9z/7xc4WikiXwPSJcnIkeJAanWvj0vM2Izl8Ea8Nu3aQfEL0b9 bTHIRcOKdE0y3vqv+UqjMiXw9DwomEqbCaqi+D5pyPc7VhJJJ5iFDTHZe0bGw4/sWDVvt19 a9bAv8xdIKaZLC2SJeU4uSdFg8rydXdG5x5cFuTOEvzetxm5q4Rk6EdoEXZMEsNQZ64nsmM fmCbXoTLUQno+iA9k28KQ== Cc: Matthias Apitz X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Oct 2013 21:05:33 -0000 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, olli