Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Wed, 22 Aug 2001 20:13:30 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: perl, second shot (was: Re: first shot perl) Message-ID: <20010822201330.E5940@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <3B8380FA DOT 11581 DOT 1261A491 AT localhost>; <20010822130915 DOT J17561 AT cygbert DOT vinschen DOT de> <3B843093 DOT 20004 DOT 150F933D AT localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3B843093.20004.150F933D@localhost>; from cygwin-apps@cygwin.com on Wed, Aug 22, 2001 at 10:22:11PM +0200 On Wed, Aug 22, 2001 at 10:22:11PM +0200, Gerrit P. Haase wrote: >Corinna Vinschen schrieb am 2001-08-22, 13:09: > >>On Wed, Aug 22, 2001 at 09:52:58AM +0200, Gerrit P. Haase wrote: >>> Corinna Vinschen schrieb am 2001-08-22, 8:30: >>> >I just tested groups.t. It first failed since one of my groups >>> >has a space in the name and the groups.t test is sensitive for >>> >that, unfortunately. I changed the group name to not contain >>> >spaces and then the test was ok running under both, a privileged >>> >and a non-privileged user account. >>> > >>> >This is with the current developers version of Cygwin, ntsec on. >[...] >>> >>> Hmmm, i thought i patched the test according to the 'space'-issue. >>> >>> I got this with cygwin-1.3.2: >>> ============================= >>> $ groups.t >>> # groups=0(Jeder),544(Administratoren),545(Benutzer),11041(services) >>> # g0 = 0(Jeder) 544(Administratoren) 545(Benutzer) 11041(services) >>> # g1 = Jeder Administratoren Benutzer services >>> 1..2 >>> #gr1 is >>> #gr2 is >>> not ok 1 >>> ok 2 >> >>Did you try it with a developer snapshot? >> >>Corinna >> > >Not yet, is there a release date scheduled? We seem to have a couple of strange problems with the DLL now. Jason Tishler has reported two and Kazuhiro has reported one. I'm going to be looking at the bash exiting bug tonight since I suspect that it is somehow my fault. I don't know about the other two. cgf