All Enclosed are the minutes of this weeks call regards Andrew ---------------
Minutes of the 17th October 2024 Teleconference Austin-1431 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 19th October 2024 Attendees: Andrew Josey, The Open Group Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE SA OR Geoff Clare, The Open Group Eric Ackermann, CISPA Eric Blake, Red Hat, The Open Group OR Tom Thompson, IEEE The ISO status remains unchanged-- we are still awaiting a formal reply from the ISO editors. We mentioned to Tom that the IEEE PSDO path is still an option. Andrew took an action to pass the candidate errata items to Tom so we can get a readout from the IEEE editors on whether the two items could qualify as errata (1854 and 1860). * Carried forward Bug 1851: FD_CLOFORK should not be preserved across exec https://www.austingroupbugs.net/bug_view_page.php?bug_id=1851 This item still open. AI: Andrew to try to contact Solaris, other BSD, AIX, and macOS for comments. Andrew has partially completed this, sending notes to contacts for Solaris and macOS. A response has been received for Solaris. It does not appear as if we will get further responses on this one. Bug 1854: dd iflags=fullblock should be iflag=fullblock OPEN https://www.austingroupbugs.net/bug_view_page.php?bug_id=1854 This item still open On this issue, which appears to be a typo in the standard. We are looking for advice from IEEE on whether this can be handled as an errata item (iflags should have been iflag). (See above) * Current Business Bug 1857: Several problems with the new "lazy" regex quantifier. Accepted as Marked https://www.austingroupbugs.net/bug_view_page.php?bug_id=1857 An interpretation is required. This item is tagged for TC1-2024. Interpretation response: The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: The standard does not state the precedence between greedy and non-greedy repetitions when nested. Notes to the Editor (not part of this interpretation): Make the changes in bugnote:6881. Bug 1861: xargs -L broken by 0000243 resolution Accepted as Marked. https://www.austingroupbugs.net/bug_view_page.php?bug_id=1861 An interpretation is required. This item is tagged for TC1-2024. Interpretation response: The standard states that xargs -L number utility invokes utility for for each set of number arguments from standard input, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: When the -0 option was added, there was no intention to change the behavior of -L when -0 is not specified, but an attempt to reword the description of -L in a way that covered both cases resulted in such a change. Notes to the Editor (not part of this interpretation): On page 3601 line 123207 section xargs (-L), change: Invoke utility for each set of number arguments from standard input. The last invocation of utility shall be with fewer arguments if fewer than number remain. If the -0 option is not specified, each line in the standard input shall be treated as containing one argument except that empty lines shall be ignored and a line ending with a trailing unescaped <blank> shall signal continuation to the next non-empty line, inclusive; such continuation shall result in removal of all trailing unescaped <blank> characters and all <newline> characters that immediately follow them from the argument. to: If the -0 option is specified, -L number shall be equivalent to -n number. If the -0 option is not specified, the utility shall be invoked for each non-empty number logical lines of arguments from standard input. The last invocation of utility shall be with fewer logical lines of arguments if fewer than number remain. Each line in the standard input shall be treated as one logical line except that empty lines shall be ignored and a line ending with a trailing unescaped <blank> shall signal continuation of the logical line to the next non-empty line, inclusive; such continuation shall result in removal of all trailing unescaped <blank> characters and all <newline> characters that immediately follow them from the logical line. On page 3601 line 123218 section xargs (-n), change: (or {LINE_MAX} if there is no -s option) to: (or the default command line length if there is no -s option) Next Steps ---------- The next calls are on Thu 2024-10-24 (WEBEX meeting - general bugs) Thu 2024-10-31 (WEBEX meeting - general bugs) The calls are for 90 minutes Apologies in advance: 2024-10-24 Eric Blake Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Bugs are at: https://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/20xx-mm-dd (For write access this uses The Open Group single sign on, for those individuals with gitlab.opengroup.org accounts. Please contact Andrew if you need to be setup) -------- Andrew Josey The Open Group Austin Group Chair Email: [email protected] Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub&listid=2481
