[Bug 3701] New: HTTP Error: 404 - Issue with Mercurial and Tortoise 2.x clients during PULL.
bugzilla-daemon at bz.selenic.com
bugzilla-daemon at bz.selenic.com
Wed Nov 14 11:00:22 CST 2012
http://bz.selenic.com/show_bug.cgi?id=3701
Priority: normal
Bug ID: 3701
CC: mercurial-devel at selenic.com
Assignee: bugzilla at selenic.com
Summary: HTTP Error: 404 - Issue with Mercurial and Tortoise
2.x clients during PULL.
Severity: bug
Classification: Unclassified
OS: Windows
Reporter: blair at blairmany.com
Hardware: PC
Status: UNCONFIRMED
Version: 2.4
Component: Mercurial
Product: Mercurial
HTTP Error: 404 - Issue with Mercurial and Tortoise 2.x clients during PULL.
During a PULL the 2.x clients continually experience this 404 error.
This has started after a secondary branch (we call STABLE) has been
closed/reopened and or after changes are transplanted (grafted) to it.
We primarily develop and use the "DEFAULT" branch. However our deliverable
is stabilized periodically and then the “STABLE” branch is opened moving all
changes from the DEFAULT branch over to the new “STABLE”.
We also transplant code from “DEFAULT” to STABLE as necessary.
After either of the above scenarios occur the 2.x clients receive an HTTP 404
not found error.
The 1.x clients do not get this error.
We have been able to work around this issue in 2 different ways.
1 - Revert the workstation's client to 1.x and pull works fine.
2 - Selectively pull one branch, then the other, then subsequent PULLS work
fine.
(Subsequent pulls work fine pulling either/both/all branches until the above
scenarios reoccur)
Trying the same command from DOS (Using the Mercurial TEXT command results in
the same issue, this makes be believe the issue is in Mercurial not the GUI
Tortoise.
Here are the details from the LOG on the client.
% hg --repository C:\Code-Branch\default\Formats pull --verbose --force
https://bldsrv02.paragonedge.local/hg/Formats/
pulling from https://bldsrv02.paragonedge.local/hg/Formats/
searching for changes
HTTP Error: 404 (Not Found)
[command returned code 255 Wed Nov 14 10:54:52 2012]
Details about our setup:
Repository that was created using Mercurial 1.7.x
We have clients running Tortoise 1.1.x and Trotoise 2.x (2.3 and 2.5)
The clients using Tortoise 1.1.x have not experienced this issue.
The clients with 2.x have experienced this issue.
Problem version(s)
TortoiseHg 2.5.1 / Mercurial 2.3.2
TortoiseHg 2.3.5 /
Version that work properly
TortoiseHG 1.1.7 / Mercurial 1.7.2
TottoiseHG 1.1.10 / Mercurial 1.8.1
The Server runs IIS7
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list