Adding upstream version 4.23.0.upstream/4.23.0

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 12 insertions, 13 deletions

diff --git a/upstream/debian-unstable/man3/realpath.3 b/upstream/debian-unstable/man3/realpath.3
index 3f25e60b..0ad4f75a 100644
--- a/upstream/debian-unstable/man3/realpath.3
+++ b/upstream/debian-unstable/man3/realpath.3
@@ -6,7 +6,7 @@
 .\" Rewritten old page, 990824, aeb@cwi.nl
 .\" 2004-12-14, mtk, added discussion of resolved_path == NULL
 .\"
-.TH realpath 3 2023-07-20 "Linux man-pages 6.05.01"
+.TH realpath 3 2024-05-02 "Linux man-pages 6.8"
 .SH NAME
 realpath \- return the canonicalized absolute pathname
 .SH LIBRARY
@@ -16,16 +16,16 @@ Standard C library
 .nf
 .B #include <limits.h>
 .B #include <stdlib.h>
-.PP
+.P
 .BI "char *realpath(const char *restrict " path ,
 .BI "               char *restrict " resolved_path );
 .fi
-.PP
+.P
 .RS -4
 Feature Test Macro Requirements for glibc (see
 .BR feature_test_macros (7)):
 .RE
-.PP
+.P
 .BR realpath ():
 .nf
     _XOPEN_SOURCE >= 500
@@ -53,7 +53,7 @@ The resulting path will have no symbolic link,
 or
 .I "/../"
 components.
-.PP
+.P
 If
 .I resolved_path
 is specified as NULL, then
@@ -74,7 +74,7 @@ If there is no error,
 .BR realpath ()
 returns a pointer to the
 .IR resolved_path .
-.PP
+.P
 Otherwise, it returns NULL, the contents
 of the array
 .I resolved_path
@@ -130,7 +130,6 @@ T{
 .BR realpath ()
 T}	Thread safety	MT-Safe
 .TE
-.sp 1
 .SH VERSIONS
 .SS GNU extensions
 If the call fails with either
@@ -147,12 +146,12 @@ that is not readable or does not exist is returned in
 POSIX.1-2008.
 .SH HISTORY
 4.4BSD, POSIX.1-2001, Solaris.
-.PP
+.P
 POSIX.1-2001 says that the behavior if
 .I resolved_path
 is NULL is implementation-defined.
 POSIX.1-2008 specifies the behavior described in this page.
-.PP
+.P
 In 4.4BSD and Solaris, the limit on the pathname length is
 .B MAXPATHLEN
 (found in \fI<sys/param.h>\fP).
@@ -164,7 +163,7 @@ as found in \fI<limits.h>\fP or provided by the
 .BR pathconf (3)
 function.
 A typical source fragment would be
-.PP
+.P
 .in +4n
 .EX
 #ifdef PATH_MAX
@@ -176,9 +175,9 @@ A typical source fragment would be
 #endif
 .EE
 .in
-.PP
+.P
 (But see the BUGS section.)
-.\".PP
+.\".P
 .\"     2012-05-05, According to Casper Dik, the statement about
 .\"     Solaris was not true at least as far back as 1997, and
 .\"     may never have been true.
@@ -217,7 +216,7 @@ The
 .I "resolved_path\ ==\ NULL"
 feature, not standardized in POSIX.1-2001,
 but standardized in POSIX.1-2008, allows this design problem to be avoided.
-.\" .LP
+.\" .P
 .\" The libc4 and libc5 implementation contained a buffer overflow
 .\" (fixed in libc-5.4.13).
 .\" Thus, set-user-ID programs like