From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 38146 invoked by alias); 4 Sep 2018 20:08:55 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 38137 invoked by uid 89); 4 Sep 2018 20:08:55 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=BAYES_00,CYGWIN_OWNER_BODY,GIT_PATCH_2 autolearn=ham version=3.3.2 spammy=ps, p.s, sk:corinna, corinnacygwincygwincom X-HELO: Ishtar.sc.tlinx.org Received: from ishtar.tlinx.org (HELO Ishtar.sc.tlinx.org) (173.164.175.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 04 Sep 2018 20:08:53 +0000 Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id w84K8one047526 for ; Tue, 4 Sep 2018 13:08:52 -0700 Message-ID: <5B8EE652.1090804@tlinx.org> Date: Tue, 04 Sep 2018 20:08:00 -0000 From: L A Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: handling invalid user/groups (was incompat in cygwin choice of using '+' as domain and user separator.) References: <5B7DE56E.6060109@tlinx.org> <20180823081135.GN3348@calimero.vinschen.de> <5B8370CA.5080209@tlinx.org> <20180827090909.GA4733@calimero.vinschen.de> <20180827104152.GC4733@calimero.vinschen.de> <20180827105031.GF4733@calimero.vinschen.de> <20180827172629.GB6350@calimero.vinschen.de> In-Reply-To: <20180827172629.GB6350@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-09/txt/msg00077.txt.bz2 On 8/27/2018 10:26 AM, Corinna Vinschen wrote: On 8/27/2018 3:50 AM, Corinna Vinschen wrote: > The only sane way to handle unknown SIDs in file ACLs is to ignore them > entirely. The result will be that you never see them in getfacl, nor > will they be stored by tar or rsync. They are just not there from the > Cygwin perspective. --- Sounds fine to me... > I created a patch, uploaded developer snapshots to > https://cygwin.com/snapshots/ and released a new Cygwin test > release 2.11.0-0.4 with this change. Please giver any of > them a try. does the latest cygwin also have this patch as I wasn't able to duplicate the error case with the newer cygwin (nor the patch you posted earlier). I.e. was trying to make sure I got the error w/o patch, then goes away w/patch, but in this case, either I didn't dup the error or it was in latest version. Hoping it is the latter. Cheers, Linda p.s. -- some "FYI" stuff about your email: when i respond to one of your emails, I get two (2) "To:" entries -- both to cygwin@cygwin.com. I think it might be because the emails from you contain two 'Mail-Followup-To:' lines -- see below**. Also, I don't get your message included in a response (because it is in a separate attachment. Is that intentional? **-(elided header stuff): Received: (qmail 2620 invoked by alias); 27 Aug 2018 17:26:36 -0000 Mailing-List: contact cygwin-help-cygwin.com; run by ezmlm Precedence: bulk ... Sender: cygwin-owner-cygwin.com Mail-Followup-To: cygwin-cygwin.com <<<---- Delivered-To: mailing list cygwin-cygwin.com Received: (qmail 2605 invoked by uid 89); 27 Aug 2018 17:26:35 -0000 Authentication-Results: sourceware.org; auth=none ... From: Corinna Vinschen ... Reply-To: cygwin-cygwin.com Mail-Followup-To: cygwin-cygwin.com <<<--- ---- Looks like 1 is added by the list, the other is maybe added by your email client? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple