Minutes of the 21st November 2022 Teleconference Austin-1274 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 23rd November 2022 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Andrew Josey, The Open Group Mark Ziegast, SHware Systems Dev. Apologies: Don Cragun, IEEE PASC OR Tom Thompson, IEEE Eric Ackermann, HPI, University of Potsdam * General news This was a call dedicated to general bugs. Andrew noted that the New APIs Part 2 has been approved by The Open Group Governing Board and a version posted to the document register. It will take a few weeks for final publication. * Carried Forward This section trimmed -- see Austin/1264 Bug 1593: specify whether struct sockaddr_un.sun_path can be a flexible array member OPEN https://austingroupbugs.net/view.php?id=1593 Wait for Eric to complete his action on bug 561 Bug 1406: clarification of SEEK_END when current pointer doesn't match buffer size OPEN https://austingroupbugs.net/view.php?id=1406 Actions carried forward: ACTION: Andrew to contact Rich Felker (dalias) and Alan Coopersmith (Solaris) for feedback. Completed ACTION: Eric B to contact glibc folks. Bug 1616: Standardize mktemp utility OPEN https://austingroupbugs.net/view.php?id=1616 We will need a sponsor; it is not suitable for inclusion in Issue 8. ACTION: Eric to ask The Open Group to sponsor adding the mktemp utility (for Issue 9). * Current Business Bug 1122: POSIX should include gettext() and friends Accepted as Marked https://austingroupbugs.net/view.php?id=1122 This item is tagged for Issue 8 Make the changes from "Additional APIs for Issue 8, Part 2" (Austin/1273) and change the NLSPATH description on all existing utility pages to:
[XSI]NLSPATH Determine the location of messages objects and message catalogs.[/XSI]
Bug 1344: Addition of setresuid()/setresgid()/getresuid()/getresgid() Accepted as Marked https://austingroupbugs.net/view.php?id=1344 This item is tagged for Issue 8 Make the changes from "Additional APIs for Issue 8, Part 2" (Austin/1273). Bug 1457: Add readlink(1) utility Accepted as Marked https://austingroupbugs.net/view.php?id=1457 This item is tagged for Issue 8 Make the changes from "Additional APIs for Issue 8, Part 2" (Austin/1273). Bug 1586: timeout - new utility: run a command with a time limit Accepted as Marked https://austingroupbugs.net/view.php?id=1586 This item is tagged for Issue 8 Make the changes from "Additional APIs for Issue 8, Part 2" (Austin/1273). Bug 1291: Add method to obtain pthread attributes OPEN https://austingroupbugs.net/view.php?id=1291 Needs additional details and sponsor for Issue 9 Bug 1616: Standardize mktemp utility OPEN https://austingroupbugs.net/view.php?id=1616 Will need a sponsor; not suitable for inclusion in Issue 8. AI Eric to ask The Open Group to sponsor adding the mktemp utility (for Issue 9). Bug 1619: Add support for TZ=Area/Location Accepted as Marked https://austingroupbugs.net/view.php?id=1619 This item is tagged for Issue 8. On page 161 line 5616 section 8.3, change: The value of TZ has one of the two forms (spaces inserted for clarity): :characters or: std offset dst offset, rule If TZ is of the first format (that is, if the first character is a ), the characters following the are handled in an implementation-defined manner. The expanded format (for all TZs whose value does not have a as the first character) is as follows: to: The application shall ensure that the value of TZ has one of the three forms (spaces inserted for clarity): :characters or: std offset dst offset, rule or: A format specifying a geographical timezone or a special timezone. If TZ is of the first format (that is, if the first character is a ), the characters following the are handled in an implementation-defined manner. The expanded form of the second format (without the inserted spaces) is as follows: After page 163 line 5700 section 8.3, add: If TZ is of the third format (that is, if the first character is not a and the value does not match the syntax for the second format), the value indicates either a geographical timezone or a special timezone from an implementation-defined timezone database. Typically these take the form Area/Location as in the IANA timezone database. Examples of geographical timezones that may be supported include Africa/Cairo, America/Indiana/Indianapolis, America/New_York, Asia/Tokyo, and Europe/London. The data for each geographical timezone shall include: The offset from Coordinated Universal Time of the timezone's standard time. If Daylight Saving Time (DST) is, or has historically been, observed: a method to discover the dates and times of transitions to and from DST and the offset from Coordinated Universal Time during periods when DST was, is, or is predicted to be, in effect. The timezone names for standard time (std) and, if observed, for DST (dst) to be used by tzset(). These shall each contain no more than {TZNAME_MAX} bytes. If there are any historical variations, or known future variations, of the above data for a geographical timezone, these variations shall be included in the database, except that historical variations from before the Epoch need not be included. If the database incorporates an external database such as the one maintained by IANA, the implementation shall provide an implementation-defined method to allow the database to be updated, for example the method specified by RFC 6557. On page 3460 line 118332 section A.8.3, change: Implementations are encouraged to use the time zone database maintained by IANA to determine when Daylight Saving Time changes occur and to handle TZ values that start with a . See RFC 6557. to: Implementations are encouraged to incorporate the IANA timezone database into the timezone database used for TZ values specifying geographical and special timezones, and to provide a method to allow it to be updated in accordance with RFC 6557. The TZ format beginning with was originally introduced as a way for implementations to support geographical timezones in the form :Area/Location as an extension, but implementations started to support them without the leading (as well as with it) and their use without the became the de-facto standard. Consequently when geographical timezones were added to this standard, it was without the . Bug 1618: pax: extend substitution flags Accepted as Marked https://austingroupbugs.net/view.php?id=1618 This item is tagged for Issue 8. On page 3047 line 102689, change: -s /old/new/[gp] to: -s /old/new/[gpsS] On page 3047 line 102693-102698, change: The optional trailing 'p' shall cause successful substitutions to be written to standard error. File or archive member names that substitute to the empty string shall be ignored when reading and writing archives. to: The optional trailing 'p' shall cause successful substitutions to be written to standard error. The optional trailing 's' and 'S' control whether the substitutions are applied to symbolic link contents: 's' shall cause them not to be applied; 'S' shall cause them to be applied. If neither is present, it is unspecified which is the default. If both are present, the behavior is unspecified. File or archive member names that substitute to the empty string shall be ignored when reading and writing archives. Symbolic link contents that substitute to the empty string shall not be treated specially. Bug 0000561: NUL-termination of sun_path in Unix sockets OPEN http://austingroupbugs.net/view.php?id=561 Next Steps ---------- The next calls are on: Thu 2022-11-24 NO CALL for US Thanksgiving Mon 2022-11-28 (general bugs) Thu 2022-12-01 (general bugs) The calls are for 90 minutes 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)