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."
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
