the latest version of unison ignores the perms=0 option. I see this when I try to sync a local dir with an smb share, where I cannot set any unix permṡ.
This is the kind of messages I see
d% 00:00 ETAFailed [[filename]]: Error in setting permissions:
Operation not supported [chmod([filename])]
UNISON 2.32.52 finished propagating changes at 11:36:27 on 22 Mar 2010
previous versions worked fine
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages unison depends on:
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
Versions of packages unison recommends:
ii openssh-client [ssh-client] 1:5.3p1-3 secure shell (SSH) client, for sec
unison suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
The preference "perms=0" means that permissions should not be
propagated. But Unison still sets the permissions of an updated file
based on the permissions of the previous version of the file, in order
to preserve file permissions.
(See https://bugs.launchpad.net/ubuntu/+source/unison/+bug/304453 )
You now need to add "dontchmod=true" to your profile as well, if you
don't want Unison to use chmod at all.
-- Jerome
Am 22.03.2010 15:02, schrieb Jerome Vouillon:
> On Mon, Mar 22, 2010 at 11:37:59AM +0100, Johannes Rohr wrote:
>> the latest version of unison ignores the perms=0 option. I see this
>> when I try to sync a local dir with an smb share, where I cannot set
>> any unix permṡ.
>
> The preference "perms=0" means that permissions should not be
> propagated. But Unison still sets the permissions of an updated file
> based on the permissions of the previous version of the file, in order
> to preserve file permissions.
> (See https://bugs.launchpad.net/ubuntu/+source/unison/+bug/304453 )
>
> You now need to add "dontchmod=true" to your profile as well, if you
> don't want Unison to use chmod at all.
But has unison's behaviour changed? I have in the meantime downgraded
to unison2.27.57, and here it works without that option.
- --
Johannes Rohr
Russia Coordinator / Координатор по России
International Work Group for Indigenous Affairs /
Международная рабочая группа по делам коренных народов (IWGIA)
Classensgade 11E, DK-2100 Copenhagen
http://www.iwgia.org <http://www.iwgia.org/>
Tel.: +45 35 27 05 01, Fax: +45 35 27 05 07
Mobile: +45-22 88 76 53 (Denmark);
+7-909-907 88 84 (Russia), +49-1570-3322883 (Germany)
Skype: johannesrohr,
/Please visit IWGIA's webshop at/
shop.iwgia.org <http://shop.iwgia.org/>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFLp4K+P0U1iBhill4RAo19AJ9cFrfsnJuDMl4GcNQ+OCaAIjLixgCdGder
hwC9Nb/9NozRvKmwETmJYSw=
=W5rX
-----END PGP SIGNATURE-----
Unison's behavior was changed in 2.27 to provide a workaround to the
chmod failure issue. It has been reverted back in 2.32 and the
"dontchmod" preference has been added as a better workaround.
-- Jerome