[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Éric Araujo added the comment: Yep, see subthread starting at http://mail.python.org/pipermail/python-dev/2011-March/109819.html ___ PSF Meta Tracker ___

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Vinay Sajip added the comment: > Éric Araujo added the comment: > > My GSoC student found the reason of the problem: When we put a full > Mercurial >URI like http://blah#branch, the patch generation fails, we have to go to the >edit repo form (on another page) and fill in separately the

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Éric Araujo added the comment: Great, thanks! -- status: resolved -> chatting ___ PSF Meta Tracker ___ __

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Martin v. Löwis added the comment: This is now fixed in r88855 -- status: chatting -> resolved ___ PSF Meta Tracker ___ _

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Éric Araujo added the comment: How did it fail in a browser? It does not link to a fragment of the page, but the URI prior to the # sign still references a clonable Mercurial repo. About the schema: sure, no need to change it. Thanks for supporting repo#branch. _

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Martin v. Löwis added the comment: Ah, ok. I recall trying the format in a browser, and it (probably not surprisingly) failed. I guess it's then ok to support the format when adding repositories; I wouldn't change the schema, though (i.e. keep repo and branch separated).

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Éric Araujo added the comment: repo#branch is a supported format, not a convention for notation. For example, I always recommend using “hg clone http://hg.python.org/cpython#default” to avoid pulling 2.x branches. ___ PSF Meta Tracker

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Martin v. Löwis added the comment: I was hesitant to add another field into the UI, which is already overloaded, and it would make people assume that they have to fill out the branch field. I assumed that using named branches would be uncommon enough to let people who use them go through a sep

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Éric Araujo added the comment: My GSoC student found the reason of the problem: When we put a full Mercurial URI like http://blah#branch, the patch generation fails, we have to go to the edit repo form (on another page) and fill in separately the base URI and the branch. It would be easier i

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Éric Araujo added the comment: Same error on http://bugs.python.org/issue12344 -- nosy: +eric.araujo status: unread -> chatting ___ PSF Meta Tracker

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

New submission from Vinay Sajip : I'm working on Issue 12291 in the Python tracker: http://bugs.python.org/issue12291 I just pushed my changes to a public sandbox on hg.python.org, into a new branch that I created: fix12291: http://hg.python.org/sandbox/vsajip#fix12291 I added the above repo