bzr 1.0.0.candidate.3: ERROR: Permission denied: [Errno 13]

Alexander Belchenko bialix at ukr.net
Thu Dec 13 18:33:23 GMT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel пишет:
> Alexander Belchenko wrote:
>> Jari Aalto ?8H5B:
>>> * Thu 2007-12-13 John Arbash Meinel <john at arbash-meinel.com>
>>> * Message-Id: 476141D5.6070503 at arbash-meinel.com
>>>> ^-- All of your directories are being created in readonly mode. Any idea why
>>>> that would be happening?
>>>>
>>>> I believe the code tries to maintain the permissions of .bzr/, so you might try
>>> Here is another one (FAT32/Native Cygwin)
>>>     $ umask
>>>     0022
>>>     $ ls -la | head -4
>>>     total 256
>>>     dr-xr-xr-x 3 root None    0 Dec 12 22:38 .
>>>     dr-xr-xr-x 7 root None    0 Dec 12 22:06 ..
>>>     dr-xr-xr-x 6 root None    0 Dec 13 02:08 .bzr
>>>     $ touch .bzr/new-file.tmp; ls -la .bzr/new-file.tmp
>>>     -rw-r--r-- 1 root None 0 Dec 13 16:46 .bzr/new-file.tmp
>>>     $ rm .bzr/new-file.tmp; echo $?
>>>     0
>>> Could python see the file permission somehow differently?
>> No. You think in the terms of unix filesystem, but actually you're working on windows filesystem. So
>> you should play by windows rules.
> 
> He is actually on Cygwin, which makes it even more confusing. Since it is the
> Unix permissions overlaid on top of Window permissions.
> 
> The weirdest (to me) is that Windows likes to pretend things are read-only when
> they aren't. (I haven't found a way to make a directory such that you cannot
> put new things in it.)

I know it. We have one test for read-only explicitly ignored on win32.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHYXrzzYr338mxwCURAsusAKCPe01e3qRjgMjOpfbrdIlxytSW0QCeOoAS
MYIapXFzFw1ViQpHZgj3FIo=
=xHHe
-----END PGP SIGNATURE-----



More information about the bazaar mailing list