All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: bzr is online
Date: Sun, 08 Nov 2009 16:36:03 +0100	[thread overview]
Message-ID: <4AF6E563.9070208@gmail.com> (raw)

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 vectors.
--2a format should block it but don't even try please. Use
sftp://bzr.savannah.gnu.org/srv/bzr/grub/
<sftp://bzr.savannah.gnu.org/srv/bzr/grub/trunk/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 patch
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 = 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

-- 

Regards
Vladimir 'phcoder' Serbinenko





             reply	other threads:[~2009-11-08 15:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08 15:36 Vladimir 'phcoder' Serbinenko [this message]
2009-11-08 20:32 ` bzr is online Bean
2009-11-08 20:45   ` Vladimir 'phcoder' Serbinenko
2009-11-09  8:26     ` Bean
2009-11-09  8:41       ` Vladimir 'phcoder' Serbinenko
2009-11-09  8:53         ` Bean
2009-11-09 14:12           ` Robert Millan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AF6E563.9070208@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.