Adding upstream version 4.22.0.upstream/4.22.0

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

1 files changed, 266 insertions, 0 deletions

diff --git a/upstream/fedora-rawhide/man1/perl5125delta.1 b/upstream/fedora-rawhide/man1/perl5125delta.1
new file mode 100644
index 00000000..f552250d
--- /dev/null
+++ b/upstream/fedora-rawhide/man1/perl5125delta.1
@@ -0,0 +1,266 @@
+.\" -*- mode: troff; coding: utf-8 -*-
+.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)
+.\"
+.\" Standard preamble:
+.\" ========================================================================
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Vb \" Begin verbatim text
+.ft CW
+.nf
+.ne \\$1
+..
+.de Ve \" End verbatim text
+.ft R
+.fi
+..
+.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
+.ie n \{\
+.    ds C` ""
+.    ds C' ""
+'br\}
+.el\{\
+.    ds C`
+.    ds C'
+'br\}
+.\"
+.\" Escape single quotes in literal strings from groff's Unicode transform.
+.ie \n(.g .ds Aq \(aq
+.el       .ds Aq '
+.\"
+.\" If the F register is >0, we'll generate index entries on stderr for
+.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" entries marked with X<> in POD.  Of course, you'll have to process the
+.\" output yourself in some meaningful fashion.
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
+..
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{\
+.    if \nF \{\
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
+..
+.        if !\nF==2 \{\
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
+.\}
+.rr rF
+.\" ========================================================================
+.\"
+.IX Title "PERL5125DELTA 1"
+.TH PERL5125DELTA 1 2024-01-25 "perl v5.38.2" "Perl Programmers Reference Guide"
+.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
+.\" way too many mistakes in technical documents.
+.if n .ad l
+.nh
+.SH NAME
+perl5125delta \- what is new for perl v5.12.5
+.SH DESCRIPTION
+.IX Header "DESCRIPTION"
+This document describes differences between the 5.12.4 release and
+the 5.12.5 release.
+.PP
+If you are upgrading from an earlier release such as 5.12.3, first read
+perl5124delta, which describes differences between 5.12.3 and
+5.12.4.
+.SH Security
+.IX Header "Security"
+.ie n .SS """Encode"" decode_xs n\-byte heap-overflow (CVE\-2011\-2939)"
+.el .SS "\f(CWEncode\fP decode_xs n\-byte heap-overflow (CVE\-2011\-2939)"
+.IX Subsection "Encode decode_xs n-byte heap-overflow (CVE-2011-2939)"
+A bug in \f(CW\*(C`Encode\*(C'\fR could, on certain inputs, cause the heap to overflow.
+This problem has been corrected.  Bug reported by Robert Zacek.
+.ie n .SS "File::Glob::bsd_glob() memory error with GLOB_ALTDIRFUNC (CVE\-2011\-2728)."
+.el .SS "\f(CWFile::Glob::bsd_glob()\fP memory error with GLOB_ALTDIRFUNC (CVE\-2011\-2728)."
+.IX Subsection "File::Glob::bsd_glob() memory error with GLOB_ALTDIRFUNC (CVE-2011-2728)."
+Calling \f(CW\*(C`File::Glob::bsd_glob\*(C'\fR with the unsupported flag GLOB_ALTDIRFUNC would 
+cause an access violation / segfault.  A Perl program that accepts a flags value from
+an external source could expose itself to denial of service or arbitrary code
+execution attacks.  There are no known exploits in the wild.  The problem has been
+corrected by explicitly disabling all unsupported flags and setting unused function
+pointers to null.  Bug reported by Clément Lecigne.
+.SS "Heap buffer overrun in 'x' string repeat operator (CVE\-2012\-5195)"
+.IX Subsection "Heap buffer overrun in 'x' string repeat operator (CVE-2012-5195)"
+Poorly written perl code that allows an attacker to specify the count to
+perl's 'x' string repeat operator can already cause a memory exhaustion
+denial-of-service attack. A flaw in versions of perl before 5.15.5 can
+escalate that into a heap buffer overrun; coupled with versions of glibc
+before 2.16, it possibly allows the execution of arbitrary code.
+.PP
+This problem has been fixed.
+.SH "Incompatible Changes"
+.IX Header "Incompatible Changes"
+There are no changes intentionally incompatible with 5.12.4. If any
+exist, they are bugs and reports are welcome.
+.SH "Modules and Pragmata"
+.IX Header "Modules and Pragmata"
+.SS "Updated Modules"
+.IX Subsection "Updated Modules"
+\fIB::Concise\fR
+.IX Subsection "B::Concise"
+.PP
+B::Concise no longer produces mangled output with the \fB\-tree\fR option
+[perl #80632].
+.PP
+\fIcharnames\fR
+.IX Subsection "charnames"
+.PP
+A regression introduced in Perl 5.8.8 has been fixed, that caused
+\&\f(CWcharnames::viacode(0)\fR to return \f(CW\*(C`undef\*(C'\fR instead of the string "NULL"
+[perl #72624].
+.PP
+\fIEncode has been upgraded from version 2.39 to version 2.39_01.\fR
+.IX Subsection "Encode has been upgraded from version 2.39 to version 2.39_01."
+.PP
+See "Security".
+.PP
+\fIFile::Glob has been upgraded from version 1.07 to version 1.07_01.\fR
+.IX Subsection "File::Glob has been upgraded from version 1.07 to version 1.07_01."
+.PP
+See "Security".
+.PP
+\fIUnicode::UCD\fR
+.IX Subsection "Unicode::UCD"
+.PP
+The documentation for the \f(CW\*(C`upper\*(C'\fR function now actually says "upper", not
+"lower".
+.PP
+\fIModule::CoreList\fR
+.IX Subsection "Module::CoreList"
+.PP
+Module::CoreList has been updated to version 2.50_02 to add data for
+this release.
+.SH "Changes to Existing Documentation"
+.IX Header "Changes to Existing Documentation"
+.SS perlebcdic
+.IX Subsection "perlebcdic"
+The perlebcdic document contains a helpful table to use in \f(CW\*(C`tr///\*(C'\fR to
+convert between EBCDIC and Latin1/ASCII.  Unfortunately, the table was the
+inverse of the one it describes.  This has been corrected.
+.SS perlunicode
+.IX Subsection "perlunicode"
+The section on
+User-Defined Case Mappings had
+some bad markup and unclear sentences, making parts of it unreadable.  This
+has been rectified.
+.SS perluniprops
+.IX Subsection "perluniprops"
+This document has been corrected to take non-ASCII platforms into account.
+.SH "Installation and Configuration Improvements"
+.IX Header "Installation and Configuration Improvements"
+.SS "Platform Specific Changes"
+.IX Subsection "Platform Specific Changes"
+.IP "Mac OS X" 4
+.IX Item "Mac OS X"
+There have been configuration and test fixes to make Perl build cleanly on
+Lion and Mountain Lion.
+.IP NetBSD 4
+.IX Item "NetBSD"
+The NetBSD hints file was corrected to be compatible with NetBSD 6.*
+.SH "Selected Bug Fixes"
+.IX Header "Selected Bug Fixes"
+.IP \(bu 4
+\&\f(CW\*(C`chop\*(C'\fR now correctly handles characters above "\ex{7fffffff}"
+[perl #73246].
+.IP \(bu 4
+\&\f(CW\*(C`($<,$>) = (...)\*(C'\fR stopped working properly in 5.12.0.  It is supposed
+to make a single \f(CWsetreuid()\fR call, rather than calling \f(CWsetruid()\fR and
+\&\f(CWseteuid()\fR separately.  Consequently it did not work properly.  This has
+been fixed [perl #75212].
+.IP \(bu 4
+Fixed a regression of \fBkill()\fR when a match variable is used for the
+process ID to kill [perl #75812].
+.IP \(bu 4
+\&\f(CW\*(C`UNIVERSAL::VERSION\*(C'\fR no longer leaks memory.  It started leaking in Perl
+5.10.0.
+.IP \(bu 4
+The C\-level \f(CW\*(C`my_strftime\*(C'\fR functions no longer leaks memory.  This fixes a
+memory leak in \f(CW\*(C`POSIX::strftime\*(C'\fR [perl #73520].
+.IP \(bu 4
+\&\f(CW\*(C`caller\*(C'\fR no longer leaks memory when called from the DB package if
+\&\f(CW@DB::args\fR was assigned to after the first call to \f(CW\*(C`caller\*(C'\fR.  Carp
+was triggering this bug [perl #97010].
+.IP \(bu 4
+Passing to \f(CW\*(C`index\*(C'\fR an offset beyond the end of the string when the string
+is encoded internally in UTF8 no longer causes panics [perl #75898].
+.IP \(bu 4
+Syntax errors in \f(CW\*(C`(?{...})\*(C'\fR blocks in regular expressions no longer
+cause panic messages [perl #2353].
+.IP \(bu 4
+Perl 5.10.0 introduced some faulty logic that made "U*" in the middle of
+a pack template equivalent to "U0" if the input string was empty.  This has
+been fixed [perl #90160].
+.SH Errata
+.IX Header "Errata"
+.ie n .SS "\fBsplit()\fP and @_"
+.el .SS "\fBsplit()\fP and \f(CW@_\fP"
+.IX Subsection "split() and @_"
+\&\fBsplit()\fR no longer modifies \f(CW@_\fR when called in scalar or void context.
+In void context it now produces a "Useless use of split" warning.
+This is actually a change introduced in perl 5.12.0, but it was missed from
+that release's perl5120delta.
+.SH Acknowledgements
+.IX Header "Acknowledgements"
+Perl 5.12.5 represents approximately 17 months of development since Perl 5.12.4
+and contains approximately 1,900 lines of changes across 64 files from 18
+authors.
+.PP
+Perl continues to flourish into its third decade thanks to a vibrant community
+of users and developers. The following people are known to have contributed the
+improvements that became Perl 5.12.5:
+.PP
+Andy Dougherty, Chris 'BinGOs' Williams, Craig A. Berry, David Mitchell,
+Dominic Hargreaves, Father Chrysostomos, Florian Ragwitz, George Greer, Goro
+Fuji, Jesse Vincent, Karl Williamson, Leon Brocard, Nicholas Clark, Rafael
+Garcia-Suarez, Reini Urban, Ricardo Signes, Steve Hay, Tony Cook.
+.PP
+The list above is almost certainly incomplete as it is automatically generated
+from version control history. In particular, it does not include the names of
+the (very much appreciated) contributors who reported issues to the Perl bug
+tracker.
+.PP
+Many of the changes included in this version originated in the CPAN modules
+included in Perl's core. We're grateful to the entire CPAN community for
+helping Perl to flourish.
+.PP
+For a more complete list of all of Perl's historical contributors, please see
+the \fIAUTHORS\fR file in the Perl source distribution.
+.SH "Reporting Bugs"
+.IX Header "Reporting Bugs"
+If you find what you think is a bug, you might check the articles
+recently posted to the comp.lang.perl.misc newsgroup and the perl
+bug database at http://rt.perl.org/perlbug/ .  There may also be
+information at http://www.perl.org/ , the Perl Home Page.
+.PP
+If you believe you have an unreported bug, please run the \fBperlbug\fR
+program included with your release.  Be sure to trim your bug down
+to a tiny but sufficient test case.  Your bug report, along with the
+output of \f(CW\*(C`perl \-V\*(C'\fR, will be sent off to perlbug@perl.org to be
+analysed by the Perl porting team.
+.PP
+If the bug you are reporting has security implications, which make it
+inappropriate to send to a publicly archived mailing list, then please send
+it to perl5\-security\-report@perl.org. This points to a closed subscription
+unarchived mailing list, which includes all the core committers, who be able
+to help assess the impact of issues, figure out a resolution, and help
+co-ordinate the release of patches to mitigate or fix the problem across all
+platforms on which Perl is supported. Please only use this address for
+security issues in the Perl core, not for modules independently
+distributed on CPAN.
+.SH "SEE ALSO"
+.IX Header "SEE ALSO"
+The \fIChanges\fR file for an explanation of how to view exhaustive details
+on what changed.
+.PP
+The \fIINSTALL\fR file for how to build Perl.
+.PP
+The \fIREADME\fR file for general stuff.
+.PP
+The \fIArtistic\fR and \fICopying\fR files for copyright information.