John Goerzen wrote:
On Fri, Jun 01, 2007 at 06:35:24PM +0200, Thomas Arendsen Hein wrote:
* John Goerzen <[EMAIL PROTECTED]> [20070601 18:01]:
Package: mercurial
Version: 0.9.3-2
Severity: normal
this leads to the odd situation where:
hg revert --all
hg commit
actually commits changes.
Is the file owned by someone else? Then you should have noticed an
error like "Operation not permitted".
No, owned by me.
Actually, I'm not sure that my permissions diagnosis was correct. hg
status showed modified files, hg log -v after the commit showed modified
files, but hg export --git didn't show any changes. hg status after
commit no longer showed modified files, but after hg rollback, once
again did.
In fact, I found this bug two days ago, too.
I started to use Mercurial to track an upstream project. The mq
extension allows me to keep local modifications.
This project uses a home-made script to download new versions
and then it set all permission files to r--r--r-- (no w, even for
the owner).
Committing the new modifications works, but reverting files
fails. I get "*.orig" files in my repo. And hg is in a strange
state : it has begun to modify files in the working directory
but has not finished and has not recorded what it has already
done.
I recover by doing something as :
chmod -R +w .
find . -iname "*.orig" -exec rm -v {} \;
hg revert .
upstream_home_made_script_update
chmod -R +w .
hg commit -m "new upstream version"
Best regards,
Vincent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
