> > As to how to repair a repository.. we'll, I'm not sure if we
> > need that though I'm alarmed if it's happening once a week.
>
> I, also, was surprised by that.
> I would expect to see bug reports, either to us or mercurial, when
> this happens. I haven't seen either.
>
> Can we get appropriate amounts of detail, please?
I am using mq quite heavily. If you don't follow quite precisely some
steps (for example if you have to merge, it says you to do 'hg up -C
rev; hg merge rev2'. But with mq you _have_ to use 'hg qpush -m'
instead). This results in mq being broken (can't qpush or qpull). The
way to fix it is to strip both working copy and mq, to the point before
the merge happened. After stripping at this point I found several times
the repository in unstable state. 'hg verify' said that there are no
problems, but I was not able to run even 'hg log', with the error
message about 00changelog.i. It's my fault that I have not invested time
in investigating those more closely. Thing is, that most of the problems
disappeared after I started to use bleeding edge development version of
hg. If I will be able to reproduce any issue with latest hg, I'll
contact it's developers.
--
Vlad
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 185 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/scm-migration-dev/attachments/20071019/8506eb0b/attachment.bin>
