bzr and ntfsmount (fuse) issues?

[John Arbash Meinel]

Martin Pool wrote:
> On  7 Aug 2006, John Arbash Meinel <john at arbash-meinel.com> wrote:
>> Aaron Bentley wrote:
>>> John Arbash Meinel wrote:
>> How would you detect it?  On win32 we do call 'os.chmod()'. It just
>> doesn't *do* anything. It seems to complicate things a lot to have to
>> start doing mount-point detection.
>>
>> It is Fuse which is setting EPERM when we try to call os.chmod(). Since
>> it doesn't permit chmod() on an ntfs mount.
> 
> Well it's actually ENOTSUPP according to this report.
> 
> We can reasonably expect to do chmod on unix, but not on all
> filesystems.  Since we can cope without it, we should issue a
> user-visible warning (showing the filename) and continue.
> 

Well, my concern is that we are going to get *lots* of errors. (One per
file we create).

I don't know that scrolling errors is really helpful.


The traceback he submitted actually showed EPERM

76, in commit
    os.chmod(self.tmpfilename, self._new_mode)
OSError: [Errno 1] Operation not
permitted:
'/mnt/winxp/<snip>/Macros/.bzr/checkout/stat-cache.8074.transmuter.tmp'

return code 3

1 == EPERM (as does 'Operation not permitted')

John
=:->


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060807/67319c89/attachment.pgp