freeze during push with old versions of HG and scm-manager
Péter BIRÓ
Peter.BIRO at nng.com
Tue May 16 16:44:42 UTC 2023
NNG Confidential
Hi,
we are using way too old versions of hg/Tortoisehg and scm-manager, but everything worked well previously, when we have tried to update a newer hg version. After updating thg from 4.1.1. to 4.9 we could pull and clone repos but couldn't push. Hg got frozen. Somewhere here:
>hg push -v -debug
pushing to <repo>
using <repo>
sending capabilities command
using auth.nng.* for authentication
<url> certificate matched fingerprint sha256:<fingerprint>
no changes made to subrepo hgext\guestrepo since last push to <subrepo>
no changes made to subrepo hgext\win32lfn since last push to <subrepo>
query 1; heads
sending batch command
sending 4127 bytes
using auth.nng.* for authentication
searching for changes
all remote heads known locally
preparing listkeys for "phases"
sending listkeys command
sending 16 bytes
using auth.nng.* for authentication
received listkey for "phases": 15 bytes
checking for updated bookmarks
preparing listkeys for "bookmarks"
sending listkeys command
sending 19 bytes
using auth.nng.* for authentication
received listkey for "bookmarks": 52 bytes
sending branchmap command
using auth.nng.* for authentication
preparing listkeys for "bookmarks"
sending listkeys command
sending 19 bytes
using auth.nng.* for authentication
received listkey for "bookmarks": 52 bytes
3 changesets found
list of changesets:
2baeb4adf51ec11500f4105df8feffc10ed066c9
a82a90e8cf0567a15a3099396a09d43a344f0223
1ede133466ab73ad98ecb8c199533e0399e19ad9
bundle2-output-bundle: "HG20", 4 parts total
bundle2-output-part: "replycaps" 205 bytes payload
bundle2-output-part: "check:heads" streamed payload
bundle2-output-part: "changegroup" (params: 1 mandatory) streamed payload
bundle2-output-part: "pushkey" (params: 4 mandatory) empty payload
sending unbundle command
sending 6206 bytes
using auth.nng.* for authentication
keyring: looking for password (user <user>, url <url>)
keyring: Password found in keyring
using auth.nng.* for authentication
<url> certificate matched fingerprint sha256:<fingerprint>
And after this line nothing happens.
More details about versions:
We are using to scm-manager versions on two different servers. One is used for review purposes the other is the real scm manager.
Review: scm-manager v1.44
Host: scm-manager v1.60
When I update hg to 4.9 , I can push commits to review server but can't to source code manager.
Thank you if anyone can help.
Peter
________________________________
This message, including its attachments, is confidential and the email address belongs to NNG Kft. By replying to this message, you expressly acknowledge and consent that in addition to the addressee of the message, NNG Kft's other employees and professionals may have access to the correspondence and its content. Additional terms of NNG's email policy can be found here:
https://www.nng.com/email-policy/
By responding to this email you accept the email policy.
Ez az üzenet - a mellékleteit is ideértve - bizalmas és szakmai jellegu, és az e-mail-cím az NNG Kft.-hez tartozik. Amennyiben válaszol az üzenetre, kifejezett hozzájárulását adja ahhoz, hogy a levelezéshez és annak tartalmához a címzetten kívül az NNG Kft. bármely más alkalmazottja is hozzáférjen. Az NNG e-mail-szabályzatával kapcsolatos egyéb rendelkezéseket itt találja:
https://www.nng.com/email-policy/
Az e-mailre történo válaszadással Ön elfogadja az e-mail-szabályzatot.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20230516/b438da1b/attachment-0001.html>
More information about the Mercurial
mailing list