Re: gettext - acl tests - cygwin specific code path

2018-08-21 Thread cyg Simple
On 8/21/2018 4:13 PM, Andrey Repin wrote: > Greetings, cyg Simple! > >> During the testing at least one of the tests does `setfacl -m group:0:1 >> tmpfile0`. Obviously this gets a 'permission denied' error as group 0 >> doesn't exist. What do you suggest for reasonable replacement for 0? > > No

Re: gettext - acl tests - cygwin specific code path

2018-08-21 Thread Andrey Repin
Greetings, cyg Simple! > During the testing at least one of the tests does `setfacl -m group:0:1 > tmpfile0`. Obviously this gets a 'permission denied' error as group 0 > doesn't exist. What do you suggest for reasonable replacement for 0? Nothing. Not all systems have a concept of "group 0". J

Re: gettext - acl tests - cygwin specific code path

2018-08-21 Thread Marco Atzeri
Am 21.08.2018 um 20:58 schrieb cyg Simple: On 8/21/2018 11:52 AM, cyg Simple wrote: I've been reviewing the testing of gettext and I have a failure for all of the acl tests. I've found that a file without acl will obtain acl if the mode is changed to 605. STC below. During the testing at

Re: gettext - acl tests - cygwin specific code path

2018-08-21 Thread cyg Simple
On 8/21/2018 11:52 AM, cyg Simple wrote: > I've been reviewing the testing of gettext and I have a failure for all > of the acl tests. I've found that a file without acl will obtain acl if > the mode is changed to 605. STC below. > > > $ touch /tmp/tmpfile0 > $ ls -l /tmp/tmpfile0 > -rw-r--r-- 1

gettext - acl tests - cygwin specific code path

2018-08-21 Thread cyg Simple
I've been reviewing the testing of gettext and I have a failure for all of the acl tests. I've found that a file without acl will obtain acl if the mode is changed to 605. STC below. $ touch /tmp/tmpfile0 $ ls -l /tmp/tmpfile0 -rw-r--r-- 1 myUser myGroup 0 Aug 21 11:35 /tmp/tmpfile0 $ getfacl /t

Re: memory reported in /proc/pid/status is wrongly scaled

2018-08-21 Thread Corinna Vinschen
On Aug 21 16:53, Livio Bertacco wrote: > Thanks Corinna, I tried the developer snapshot and the VmSize line from > "status" file looks good now. > > What do you think about adding the VmPeak line too? (I can create the patch > myself). > > > On second thought there's more wrong than just that. >

Re: memory reported in /proc/pid/status is wrongly scaled

2018-08-21 Thread Livio Bertacco
Thanks Corinna, I tried the developer snapshot and the VmSize line from "status" file looks good now. What do you think about adding the VmPeak line too? (I can create the patch myself). > On second thought there's more wrong than just that. > Just dividing by page_size or allocation_granularity

[ANNOUNCEMENT] Updated: libunistring 0.9.10-1

2018-08-21 Thread waterlan
libunistring (source package) libunistring2 (runtime library) libunistring-devel (development library and include files) libunistring-doc (documentation) CHANGES: New in 0.9.10: * The functions u8_casing_prefix_context, u8_casing_prefixes_context, u8_casing_suffix_context, u8_