Mercurial 1.7.1 released!

JonnyDee jonny.dee.1 at googlemail.com
Thu Nov 18 05:42:29 CST 2010


Hi Matt,

> [Please don't send private mail to developers, we much prefer to answer
> questions in public where they'll benefit multiple people.]

Sorry, this won't happen again.

> >         > We use SSH access to our repositories and, unfortunately,
> >         pushing/
> >         > pulling bookmarks over SSH still doesn't work with 1.7.1.
> >         Invoking "hg
> >         > pull -B" results in "no changed bookmarks found", even if
> >         the remote
> >         > repository has bookmarks while the local clone doesn't. I've
> >         made sure
> >         > the remote machine (Ubuntu Linux) as well as my local
> >         machine (Windows
> >         > XP) have 1.7.1 installed with the "bookmarks" extension
> >         activated.
>
> >         The bugfix in 1.7.1 only affects push on HTTP. All other
> >         combinations of
> >         in/out/push/pull with http/ssh/local are tested in the test
> >         suite.
>
> >         Please try the following test:
>
> >          $ hg debugpushkey ssh://yourserver/your/repo namespaces
> >          namespaces
> >          bookmarks
>
> >         If you get back anything from this command, the protocol
> >         portion of
> >         bookmarks is working perfectly. But if you get back just
> >         'namespaces',
> >         that means bookmarks are NOT properly enabled. That is likely
> >         a
> >         configuration problem due to trust:
>
> >        http://mercurial.selenic.com/wiki/Trust
>
> > I've just executed the command you suggested. And, indeed, I do only
> > get back just 'namespaces'. However, there seems to be no issue
> > regarding 'Trust'. I've made sure the file ownerships of the "server
> > side" repository are correct.
>
> Correct as in owned by you?

I've narrowed down the problem. We use "mercurial-server" software for
shared SSH access. And the issue with not being able to pull bookmarks
only arises if I access a repository through this software. As soon as
I access this repository without it there is no problem anymore. So it
seems like this doesn't have anything to do with Mercurial itself.

Thank you very much for your help and sorry for the time you spent for
investigating my issue.

Best regards,
Jonny


More information about the Mercurial mailing list