.. in manifests not found / only partial clone

[Benito van der Zander]

Hi Matt,

> options ([+] can be repeated):

oh, I thought that [+] means you could write -r 123+



> Are you running verify/clone/branches all in the same repo?
>
> Does hg log -r 3217 work?
>
> Does hg log --hidden -r 3217 work?

Yes to all

hg push -f -r 3217 /tmp/randomrepo works too


hg pull -f -r 3217 ~/hg does not

> What hg version are you using?

3.0.1

> >From Mercurial's perspective, a remote repository is any repository that
> is not the one you're running the command in.
>

When I write hg clone . /tmp/target, am I not running the command in the 
repo that is cloned?


Bye,
Benito


On 12/22/2014 01:10 AM, Matt Mackall wrote:
> On Mon, 2014-12-22 at 00:27 +0100, Benito van der Zander wrote:
>> Hi Matt,
>>
>>> Was there a proximal cause to this data loss? Power outage? Abort caused
>>> by setting +a (even though I told you it was a bad idea)?
>> Not sure
>>
>> The abort might have happened  :(
>>
>>
>>> What filesystem are you using? Ext4?
>> Still ext3
>>
>>
>>> You can ask Mercurial which revisions you need to clone thusly:
>>>
>>> $ hg log -r "heads(not 3673::)"
>> How do you clone multiple revisions?
>>
> $ hg clone -h
> hg clone [OPTION]... SOURCE [DEST]
> ...
> options ([+] can be repeated):
> ...
>   -r --rev REV [+]       include the specified changeset
>
>>> That's very odd. May be a bug. Or it may be that you've got the branch
>>> cache marked append-only and it's now corrupt because Mercurial tried to
>>> update it and silently failed.
>>>
>> The entire cache is in .hg/cache ?
>> I have only marked stuff in .hg/store/data as append only
>>
>> Perhaps it is broken from the last time, when I deleted .i files and
>> restored them
>>
>> Or because the repository did not have a "default" branch, but another
>> named branch that I renamed to default some time ago?
>>
>>>> $ hg clone -r 3217:51428989e7dc . /tmp/wtf
>>>> abort: unknown revision '3217:51428989e7dc'!
>>> The string "3217:51428989e7dc" is not a revision.
>>> It's two different forms of the name for one revision.
>>> Much of Mercurial will now accept this as a revset: the one-element
>>> range of all revisions from 3217 to 51428989e7dc.
>> One alone does not work either:
>> $ hg clone -r 3217 . /tmp/wtf
>> abort: unknown revision '3217'!
> Are you running verify/clone/branches all in the same repo?
>
> Does hg log -r 3217 work?
>
> Does hg log --hidden -r 3217 work?
>
> What hg version are you using?
>
>>> But not clone, because
>>> it can't hand a revset to a remote server.
>> It is all local.
>> Cloning from one directory to another one
> >From Mercurial's perspective, a remote repository is any repository that
> is not the one you're running the command in.
>