From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Cc: Vladimir Serbinenko <phcoder@gmail.com>,
Colin Watson <cjwatson@ubuntu.com>
Subject: Important notice regarding Bazaar repository
Date: Fri, 30 Oct 2009 16:20:49 +0100 [thread overview]
Message-ID: <20091030152049.GA9604@thorin> (raw)
Bazaar repository has been reconstructed and will soon be uploaded. Here
are some important notes to take into account in order to prevent this
from happening again.
- Don't use a bzr-svn version earlier than 1.0.0. At 0.4.10 is buggy and
corrupts your repository. Actually, if you can, avoid bzr-svn completely.
I will use it to resync trunk, and this should suffice for now.
- Remove bzr-svn cache. Data corruption most likely spread to it (this
happened to me):
$ rm -rf ~/.bazaar/svn-cache/
- Don't use bzr-svn to commit to trunk (either original or mirror). Use
svn against the original svn repository.
- Some of the pre-existing branches were corrupted and must NOT be re-pushed
as-is. Before pushing any new work to the repository (be it a new branch
or an update to an existing one), verify that it is clean:
- Make sure bzr-svn cache was removed.
- Enter a directory that is NOT part of any local shared-repo.
- bzr co ../path/to/local/branch
In some branches, (for example, /people/robertmh/ntldr), this will result
in bzr error indicating the data is corrupt. If that doesn't happen, go
ahead with the push but please NOTIFY ME either by mail or IRC.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next reply other threads:[~2009-10-30 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 15:20 Robert Millan [this message]
2009-10-30 18:45 ` Important notice regarding Bazaar repository 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=20091030152049.GA9604@thorin \
--to=rmh@aybabtu.com \
--cc=cjwatson@ubuntu.com \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.com \
/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.