From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1N7F47-0001CJ-9q for mharc-grub-devel@gnu.org; Sun, 08 Nov 2009 16:12:51 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N7F45-0001Bu-19 for grub-devel@gnu.org; Sun, 08 Nov 2009 16:12:49 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N7F3z-00018f-40 for grub-devel@gnu.org; Sun, 08 Nov 2009 16:12:47 -0500 Received: from [199.232.76.173] (port=45323 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N7F3z-00018c-00 for grub-devel@gnu.org; Sun, 08 Nov 2009 16:12:43 -0500 Received: from ey-out-1920.google.com ([74.125.78.149]:5531) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N7F3y-0007Ha-K2 for grub-devel@gnu.org; Sun, 08 Nov 2009 16:12:42 -0500 Received: by ey-out-1920.google.com with SMTP id 3so582600eyh.34 for ; Sun, 08 Nov 2009 13:12:41 -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=7Z2LD0PaTxNWVEXQ6bzCZY1xm81/8VeyzRhlIsDhig0=; b=r0uv+7A2/8vd5QUj6aCBU64rtQl9HgoXz/uP83//zPIpJo8FwuoEUR8lhevoAJNe+E 2JZycv1NmVvMeWsEoNSPCOZiQVyaDjsau8EhoQ8qKMGJ0pTnxwPRqJTjzHhfc+bFoMA0 0FdTThug8gCMgez1CP9v/eyAVXCD769io+S8I= 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=NAe63qb+KT9/j+qcBr8TxVBjcIx52vSq1+x4ojIEnW+P1nuzCe8TVNZ+TZgzH7i3hj tLX9cMaWIzxJCh4Qt+B8kRmHIhNlo+SlgLZrBKppw1LiSfHBQUc1Wq7TXv80Mdt0sMTQ WEaIu3tC5lXcnoabHEEXd8CubRcgiX7SlDQS4= Received: by 10.216.87.5 with SMTP id x5mr2251844wee.75.1257714761667; Sun, 08 Nov 2009 13:12:41 -0800 (PST) Received: from debian.bg45.phnet (gprs13.swisscom-mobile.ch [193.247.250.13]) by mx.google.com with ESMTPS id 10sm4592162eyd.2.2009.11.08.13.12.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 08 Nov 2009 13:12:40 -0800 (PST) Message-ID: <4AF72DCE.0@gmail.com> Date: Sun, 08 Nov 2009 21:45:02 +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> In-Reply-To: X-Enigmail-Version: 0.95.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigDAEF4F7142D65BECD57121D2" 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: Sun, 08 Nov 2009 21:12:49 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDAEF4F7142D65BECD57121D2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Bean wrote: > 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 corruption = in >> bzr repository. We couldn't find for sure what caused it but we could >> 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 vector= s. >> --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 pat= ch >> 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, for > 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 Regards Vladimir 'phcoder' Serbinenko --------------enigDAEF4F7142D65BECD57121D2 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 iF4EAREKAAYFAkr3LfUACgkQNak7dOguQgnJHQD9FSfAnrq01c5MPSlufa8tjuea WRU+oeWqVEU5yoozSNMA/iLiXkqX7gR2qVRb3qN5sWMlQOWXzcykkCzuVuRyEnni =sOiC -----END PGP SIGNATURE----- --------------enigDAEF4F7142D65BECD57121D2--