Can't find the Sourceforge hg repo

[Terry Duell]

Hello All,
I regularly check for changes to the hugin repository, and do this by
pointing my browser at <http://sourceforge.net/projects/hugin/>.
On this web page I select "code" and in the menu I choose "mercurial", and
from there I can look at the recent patches to hugin or any of the
branches.
This morning when I tried this, selecting "code" didn't give any choices
and dropped me into the svn repo from 2010!
I know Sourceforge have been re-jigging things of late, but it would seem
that they have got this wrong.
If the location of the hg repo has changed, I would still would expect the
web page to provide access via the "code" menu.


Cheers,
--
Regards,
Terry Duell

[Terry Duell]

On Thu, 16 May 2013 09:17:31 +1000, Terry Duell <tdu...@iinet.net.au>
wrote:

> Hello All,
> I regularly check for changes to the hugin repository, and do this by
> pointing my browser at <http://sourceforge.net/projects/hugin/>.
> On this web page I select "code" and in the menu I choose "mercurial",
> and from there I can look at the recent patches to hugin or any of the
> branches.
> This morning when I tried this, selecting "code" didn't give any choices
> and dropped me into the svn repo from 2010!

[snip]

I have contacted "forge:site-support", and pointed out the problem,
hopefully it will be corrected soon.

[Thomas Pryds]

Perhaps something to do with this? (I thought everyone with write access to the hg repo was sent such a mail):

----------------

Your code repository in upgraded project hugin is now ready for use.

Old repository url: http://hugin.svn.sourceforge.net/svnroot/hugin

New repository checkout command: svn checkout --username=username svn+ssh://user...@svn.code.sf.net/p/hugin/code/ hugin-code

You should do a checkout using the new repository location.  The old repository is read-only now.

For more detailed instructions on migrating to your new repo, please see https://sourceforge.net/p/forge/community-docs/Repository%20Upgrade%20FAQ/

[Terry Duell]

Hello Thomas,

On Thu, 16 May 2013 14:35:40 +1000, Thomas Pryds <tho...@pryds.eu> wrote:

> Perhaps something to do with this? (I thought everyone with write access
> to
> the hg repo was sent such a mail):
>
> ----------------
>
> Your code repository in upgraded project hugin is now ready for use.
>
> Old repository url: http://hugin.svn.sourceforge.net/svnroot/hugin
>
> New repository checkout command: svn checkout --username=username
> svn+ssh://
> user...@svn.code.sf.net/p/hugin/code/ hugin-code

Yes, I think it is, but it seems to me that they have got it wrong.
Hopefully fixed soon.

[Bruno Postle]

On Thu 16-May-2013 at 09:17 +1000, Terry Duell wrote:
>I regularly check for changes to the hugin repository, and do this by
>pointing my browser at <http://sourceforge.net/projects/hugin/>.
>On this web page I select "code" and in the menu I choose
>"mercurial", and from there I can look at the recent patches to hugin
>or any of the branches.
>This morning when I tried this, selecting "code" didn't give any
>choices and dropped me into the svn repo from 2010!

They 'upgraded' us, but only migrated the unused SVN repository.
The old Mercurial repository is still there, read-only I think:
http://hugin.hg.sourceforge.net/hgweb/hugin/

I'll migrate the Mercurial repositories and post again when it is
all working.

--
Bruno

[Terry Duell]

Hello Bruno,

On Fri, 17 May 2013 05:57:36 +1000, Bruno Postle <br...@postle.net> wrote:

> They 'upgraded' us, but only migrated the unused SVN repository. The
> old Mercurial repository is still there, read-only I think:
> http://hugin.hg.sourceforge.net/hgweb/hugin/
>
> I'll migrate the Mercurial repositories and post again when it is all
> working.
>

Cory Johns responded to my [forge:site-support] contact...
"It appears the Hg repository didn't migrate when the project was
upgraded. I can restore it for you, or, if you prefer, you can add a
Mercurial tool on the [Tools Admin
page](https://sourceforge.net/p/hugin/admin/tools/) and then push your
copy of the repo to it."

and I responded, asking if they could restore it, thinking they were
probably less likely to stuff it up.

[Bruno Postle]

On Fri 17-May-2013 at 08:28 +1000, Terry Duell wrote:
>On Fri, 17 May 2013 05:57:36 +1000, Bruno Postle <br...@postle.net> wrote:
>
>>They 'upgraded' us, but only migrated the unused SVN repository.
>>The old Mercurial repository is still there, read-only I think:
>>http://hugin.hg.sourceforge.net/hgweb/hugin/

>Cory Johns responded to my [forge:site-support] contact...
>"It appears the Hg repository didn't migrate when the project was
>upgraded. I can restore it for you, or, if you prefer, you can add a
>Mercurial tool on the [Tools Admin
>page](https://sourceforge.net/p/hugin/admin/tools/) and then push
>your copy of the repo to it."
>
>and I responded, asking if they could restore it, thinking they were
>probably less likely to stuff it up.

I migrated all of the Mercurial repositories, except for hugin
itself - which keeps timing out during the push.

I'll try one more time, then somebody else with better bandwidth
needs to give it a go.

--
Bruno

[Terry Duell]

On Fri, 17 May 2013 09:10:24 +1000, Bruno Postle <br...@postle.net> wrote:


> I migrated all of the Mercurial repositories, except for hugin itself -
> which keeps timing out during the push.
>
> I'll try one more time, then somebody else with better bandwidth needs
> to give it a go.
>

OK, thanks Bruno.
It will probably time out for me too, pretty slow speed here.

[Matthew Petroff]

I just pushed the repository using a fast university connection.

-Matthew

[Terry Duell]

Hello Matthew,

On Fri, 17 May 2013 15:55:57 +1000, Matthew Petroff <mat...@mpetroff.net>
wrote:

> I just pushed the repository using a fast university connection.

Thanks.
We should now be back in business.