From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1N7Poh-0008Ci-Kt for mharc-grub-devel@gnu.org; Mon, 09 Nov 2009 03:41:39 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N7Pof-0008AO-Du for grub-devel@gnu.org; Mon, 09 Nov 2009 03:41:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N7Pob-00086g-Pw for grub-devel@gnu.org; Mon, 09 Nov 2009 03:41:37 -0500 Received: from [199.232.76.173] (port=41048 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N7Pob-00086Z-N9 for grub-devel@gnu.org; Mon, 09 Nov 2009 03:41:33 -0500 Received: from fg-out-1718.google.com ([72.14.220.157]:19647) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N7Pob-0003NW-6a for grub-devel@gnu.org; Mon, 09 Nov 2009 03:41:33 -0500 Received: by fg-out-1718.google.com with SMTP id l26so1242743fgb.12 for ; Mon, 09 Nov 2009 00:41:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type; bh=hJQP4rBJq4aR1IOuvDfl6AxS1dGWsut4mc7Mj/pG+bg=; b=b1xETnE25jmN9PVeIvTNbNLNM+/Ls3luZsyB5thvQMoPwN9SOEHZ4hGU4Wu+0fMX2S RNebjuaNPQuY8y7dq7ewPcYdE70yfWxE17PvHQOxJ42VnCpUMjnLptWiYrx0SUUONDcK XEwowDx1M0ibWJSyqAfJ+IGFqJxk1ixXQOcCA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type; b=oWKyj4pMYCPmqsjpHk4S911Ox62pYfGFk4mexoyFzkaaHxsukwV2Wh5PqIC+3kayhr l9xb3JaPnb0N+1bsd3w7MAUDyiEom/K+go4DILKAwKg4ZSp/107pfXWFYrDba20oVjJN EUM+bAbezlYqDY3SlrYlXtCU5EQlcs2+WQVTM= Received: by 10.86.198.12 with SMTP id v12mr5943230fgf.17.1257756091870; Mon, 09 Nov 2009 00:41:31 -0800 (PST) Received: from debian.bg45.phnet (hg-public-dock-104-dhcp.ethz.ch [82.130.80.104]) by mx.google.com with ESMTPS id d6sm5132833fga.0.2009.11.09.00.41.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 09 Nov 2009 00:41:30 -0800 (PST) Message-ID: <4AF7D5A3.3050600@gmail.com> Date: Mon, 09 Nov 2009 09:41:07 +0100 From: Vladimir 'phcoder' Serbinenko User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701) MIME-Version: 1.0 To: The development of GNU GRUB References: <4AF6E563.9070208@gmail.com> <4AF72DCE.0@gmail.com> In-Reply-To: X-Enigmail-Version: 0.95.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig2E42FDB43ED339C69291E63F" X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Re: bzr is online X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2009 08:41:37 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2E42FDB43ED339C69291E63F Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Bean wrote: > On Mon, Nov 9, 2009 at 4:45 AM, Vladimir 'phcoder' Serbinenko > wrote: > =20 >> Bean wrote: >> =20 >>> On Sun, Nov 8, 2009 at 11:36 PM, Vladimir 'phcoder' Serbinenko >>> wrote: >>> >>> =20 >>>> Hello, all. As you may have heard or noticed we had a data corruptio= n in >>>> bzr repository. We couldn't find for sure what caused it but we coul= d >>>> recover it, Robert Millan is running regular backups. But please be >>>> careful in the future. >>>> 1) Don't use bzr-svn. The IDs won't match anyway so it's useless. I >>>> removed bzr-svn altogether >>>> 2) Don't use bzr+ssh. Old daemon on savannah is one of possible vect= ors. >>>> --2a format should block it but don't even try please. Use >>>> sftp://bzr.savannah.gnu.org/srv/bzr/grub/ >>>> >>>> 3) Take precautions when handling your current branches. As the IDs >>>> don't match the bzr trunk you need to migrate it anyway. If you have= >>>> small number of branches and history isn't important just create a p= atch >>>> and apply it to new bzr branch of current trunk. If you have large >>>> number of branches or no local copy contact me privately. >>>> 4) Regularly run "bzr check" on your repository >>>> 5) Sign your commits. For this add >>>> create_signatures =3D always >>>> to your bazaar.conf >>>> This has double use: security and integrity. >>>> >>>> Currentyl we haven't set up syncronisation between bzr and svn. Wait= >>>> further instructions before comitting to mainstream >>>> >>>> =20 >>> Hi, >>> >>> I just sync my branch with main bzr repo, and find similar issue. It >>> seems the bzr diff has bug that could cause problem with renames, fo= r >>> example, don't use this: >>> >>> old branch: >>> bzr diff > aa.diff >>> >>> new branch: >>> bzr patch aa.diff >>> >>> The renamed file could get lost in the process. The only reliable way= >>> to apply patch is to export the whole tree from old branch, and add >>> them in the new branch. >>> >>> >>> =20 >> I don't know what exactly do you mean but the concern is safety: your >> approach may result in corruption to be transfered to new repo >> =20 > > Hi, > > It's very easy to verify, for example, run these commands: > > bzr mv COPYING COPYING1 > bzr diff > aa.diff > > Output: > =3D=3D=3D renamed file 'COPYING' =3D> 'COPYING1' > > This is obviously wrong, as neither "patch" nor "bzr patch" recognize > this format, so if you apply it with: > > bzr patch aa.diff > > Nothing happens. Therefore, 'bzr diff' is useless to create patch file > containing renames. > > BTW, my bzr version is 2.0.2 > > =20 I understood this part but haven't understood what do you propose as an alternative. (BTW feel free to report this issue to bzr mainstream) --=20 Regards Vladimir 'phcoder' Serbinenko --------------enig2E42FDB43ED339C69291E63F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iF4EAREKAAYFAkr31bkACgkQNak7dOguQglUXwD/YSnBOldjJw6WiJMAzkkCSNp2 23tTcCTEvyPutInsSzgA/2JD+aZ9ff48Rm55QCCIjqRfdqini54F43PXbQTI2LFk =c2E7 -----END PGP SIGNATURE----- --------------enig2E42FDB43ED339C69291E63F--