From owner-freebsd-git@freebsd.org Fri Jul 10 09:15:17 2020 Return-Path: Delivered-To: freebsd-git@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 379293649A7 for ; Fri, 10 Jul 2020 09:15:17 +0000 (UTC) (envelope-from uqs@freebsd.org) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a05:fc87:1:5::15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.spoerlein.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B36nw5J2Qz4MrV; Fri, 10 Jul 2020 09:15:16 +0000 (UTC) (envelope-from uqs@freebsd.org) Received: from localhost (acme.spoerlein.net [IPv6:2a05:fc87:1:5:0:0:0:15]) by acme.spoerlein.net (8.15.2/8.15.2) with ESMTPS id 06A9FDPh015426 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 10 Jul 2020 11:15:14 +0200 (CEST) (envelope-from uqs@freebsd.org) Date: Fri, 10 Jul 2020 11:15:13 +0200 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Ed Maste Cc: Ryan Steinmetz , freebsd-git@freebsd.org, "FreeBSD.org clusteradm" Subject: Re: svnsync discrepancies again Message-ID: <20200710091513.GG96323@acme.spoerlein.net> References: <20200709142053.GA60652@exodus.zi0r.com> <20200709165824.GE96323@acme.spoerlein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.2 (2019-09-21) X-Rspamd-Queue-Id: 4B36nw5J2Qz4MrV X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:39540, ipnet:2a05:fc87::/32, country:CH] X-BeenThere: freebsd-git@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussion of git use in the FreeBSD project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jul 2020 09:15:17 -0000 On Thu, 2020-07-09 at 15:46:52 -0400, Ed Maste wrote: > > > Not sure I'd call this "garbage" nor would I immediately assume that > > > we've decided to "point cluster machines at garbage" and "give the rest > > > of the world the good stuff." > > Garbage is perhaps unnecessarily inflammatory, so let's avoid calling > it that. However, I hope we all agree that if we have multiple copies > of the SVN repo they must contain the same data and metadata. > > We had this problem often in the past and I thought it was now "fixed" > by the scripts that run svnsync? Is the issue just that we can only > ever have one svnsync generation? Maybe it's inflammatory, maybe it was lost in translation. Maybe I'm just really angry about the time I've wasted chasing after what ended up being svnsync's fault more than once. It has 1 job and it fails to do that 1 job consistently. That is really frustrating. I wish we would not use svnsync for the mirrors. rsync(1) is a perfectly good alternative that wouldn't randomly munge the data. I also wish we wouldn't even mirror the repo in the first place. We're turning a centralized VCS into a decentralized one, that makes no sense. The added mirrors might add some sense of security I guess, other than that they probably have wasted more time and effort than we have gained by them :/ > > > - where is the actual canonical source of our SVN and > > - how can I get access to it from both a machine inside the cluster as > > well as outside? > > Having access to a SVN repository that's guaranteed to have the > correct data and metadata is a requirement for the svn-git migration > process. so I hope someone can answer those two shortly. Yes please. You might wonder why I'm so angry because of a 2s time delta, but svnsync is also known to not copy the author correctly and with git everything get's hashed, so the result would be a totally different repo. We don't want that. Thanks Uli