[Bug 4287] New: "hg push" fails when trying to chmod files on CIFS share mounted via gvfs

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Mon Jun 23 03:43:52 CDT 2014


http://bz.selenic.com/show_bug.cgi?id=4287

          Priority: normal
            Bug ID: 4287
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: "hg push" fails when trying to chmod files on CIFS
                    share mounted via gvfs
          Severity: bug
    Classification: Unclassified
                OS: Linux
          Reporter: nihil84 at gmail.com
          Hardware: PC
            Status: UNCONFIRMED
           Version: earlier
         Component: Mercurial
           Product: Mercurial

What I want is to use as "server" a remote repository on a Windows shared
folder in a corporate domain: using gvfs instead of autofs or fstab allow a
more secure management of the windows domain passwords 

But using gvfs (v1.20) will fail on push operations because of the CIFS
implementation returns EOPNOTSUPP when trying to chmod remote files: the
exception remains uncaught then the script crashes.

More in detail (mercurial 2.8.2, python 2.7):
'hg push' crashes on line 61 of transaction.py

To get at least a push working I 'fixed' the script with:
    try:
        os.chmod(dst, st_mode)
    except OSError, e:
        if e.errno != errno.EOPNOTSUPP:
            raise

Then it crashes on posix.py:122
With the same code above also in posix.py, the push worked but it continue to
fail if performed through thg (why?).

PS: I am not a python developer, and I don't know why it is trying to make a
chmod of the remote files: I know that my code actually do not fix anything and
may also break some interlocking protocol. That code is there only to show
where and why I think that the script is not working.

I hope this will get fixed someday, hopefully before our data center
administrators will ever know that we are storing our account passwords in a
bunch of clear-text files.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list