推送完成后，xxx似乎不是hg储存库 [英] xxx does not appear to be an hg repository after push finishes

问题描述

就在几天前，当我推送到hg存储库时，在推送完成后会出现类似"xxx似乎不是hg存储库"的信息.输出看起来像这样:

Just several days ago, when I push to a hg repository, something like 'xxx does not appear to be an hg repository' appears after push finishes. The output looks like this:

pushing to http://xxx/scm/hg/jewelry
searching for changes    
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
abort: 'http://xxx/scm/hg/jewelry' does not appear to be an hg repository:
---%<--- (no content-type)

---%<---
!

实际上已经完成了推送，所以这没什么大不了的，除了它确实很烦人. 有人遇到过吗?

The push is actually finished, so this can't be a big deal, except that it's really annoying. So did anyone come across this?

顺便说一句，客户端的hg版本为2.1&服务器是2.3.但这似乎不是版本问题，因为它几天前才从任何地方冒出来.

BTW, the hg version on client side is 2.1 & server is 2.3. But this does not seem to be a version problem because it just came out from nowhere several days ago.

推荐答案

我不确定，但是看起来有人在服务器上安装了一个钩子，可以在推送和钩子断开后运行某些东西?如果将--debug添加到推送中，您是否还看到其他细节?有人最近添加了服务器端changegroup挂钩吗?也许通知"发送电子邮件?

I'm not certain but it looks like someone has installed a hook on the server to run something after the push and their hook is broken? Do you see any extra detail if you add --debug to the push? Any chance someone recently added a server side changegroup hook? Perhaps 'notify' to send out emails?

这篇关于推送完成后，xxx似乎不是hg储存库的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！