[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#169748: marked as done (unison: Unison shows wrong permission flag (sgid))



Your message dated Wed, 09 May 2012 07:40:01 +0200
with message-id <E1SRzd3-0005BV-No@wallace.tews.net>
and subject line Re: Bug#169748: unison: Unison shows wrong permission flag (sgid)
has caused the Debian Bug report #169748,
regarding unison: Unison shows wrong permission flag (sgid)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
169748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=169748
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: unison
Version: 2.9.1-1
Severity: minor

If I have a directory with following permissions  rwxr-x--- and change
it too rwxr-s--- the gtk-gui (I only checked this one) shows a wrong
diff.

It just shows

	local     : dir props changed  [...] size 0         rwxr-x---
	remote : unchanged dir         [...] size 0         rwxr-x---

(right, it doesn't show the s flag).

This is only a problem in the userinterface because unison
handles this correctly.

Adam

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux local 2.4.19 #5 Mon Oct 14 23:20:54 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages unison depends on:
ii  libc6                         2.2.5-14.3 GNU C Library



--- End Message ---
--- Begin Message ---
Hi,

the behavior of unison wrt setgid flags has probably been changed
long ago. Now unison does not report or propagate differences
in setgid flags. The manual says

     * For security reasons, the Unix setuid and setgid bits are not
       propagated.

I am therefore closing this bug.

Bye,

Hendrik


--- End Message ---

Reply to: