Adding upstream version 4.22.0.upstream/4.22.0

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

1 files changed, 192 insertions, 0 deletions

diff --git a/upstream/debian-bookworm/man1/perl5281delta.1 b/upstream/debian-bookworm/man1/perl5281delta.1
new file mode 100644
index 00000000..c937fd01
--- /dev/null
+++ b/upstream/debian-bookworm/man1/perl5281delta.1
@@ -0,0 +1,192 @@
+.\" Automatically generated by Pod::Man 4.14 (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
+..
+.\" Set up some character translations and predefined strings.  \*(-- will
+.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
+.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
+.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
+.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
+.\" nothing in troff, for use with C<>.
+.tr \(*W-
+.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
+.ie n \{\
+.    ds -- \(*W-
+.    ds PI pi
+.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
+.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
+.    ds L" ""
+.    ds R" ""
+.    ds C` ""
+.    ds C' ""
+'br\}
+.el\{\
+.    ds -- \|\(em\|
+.    ds PI \(*p
+.    ds L" ``
+.    ds R" ''
+.    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 "PERL5281DELTA 1"
+.TH PERL5281DELTA 1 "2023-11-25" "perl v5.36.0" "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"
+perl5281delta \- what is new for perl v5.28.1
+.SH "DESCRIPTION"
+.IX Header "DESCRIPTION"
+This document describes differences between the 5.28.0 release and the 5.28.1
+release.
+.PP
+If you are upgrading from an earlier release such as 5.26.0, first read
+perl5280delta, which describes differences between 5.26.0 and 5.28.0.
+.SH "Security"
+.IX Header "Security"
+.SS "[\s-1CVE\-2018\-18311\s0] Integer overflow leading to buffer overflow and segmentation fault"
+.IX Subsection "[CVE-2018-18311] Integer overflow leading to buffer overflow and segmentation fault"
+Integer arithmetic in \f(CW\*(C`Perl_my_setenv()\*(C'\fR could wrap when the combined length
+of the environment variable name and value exceeded around 0x7fffffff.  This
+could lead to writing beyond the end of an allocated buffer with attacker
+supplied data.
+.PP
+[\s-1GH\s0 #16560] <https://github.com/Perl/perl5/issues/16560>
+.SS "[\s-1CVE\-2018\-18312\s0] Heap-buffer-overflow write in S_regatom (regcomp.c)"
+.IX Subsection "[CVE-2018-18312] Heap-buffer-overflow write in S_regatom (regcomp.c)"
+A crafted regular expression could cause heap-buffer-overflow write during
+compilation, potentially allowing arbitrary code execution.
+.PP
+[\s-1GH\s0 #16649] <https://github.com/Perl/perl5/issues/16649>
+.SH "Incompatible Changes"
+.IX Header "Incompatible Changes"
+There are no changes intentionally incompatible with 5.28.0.  If any exist,
+they are bugs, and we request that you submit a report.  See
+\&\*(L"Reporting Bugs\*(R" below.
+.SH "Modules and Pragmata"
+.IX Header "Modules and Pragmata"
+.SS "Updated Modules and Pragmata"
+.IX Subsection "Updated Modules and Pragmata"
+.IP "\(bu" 4
+Module::CoreList has been upgraded from version 5.20180622 to 5.20181129_28.
+.SH "Selected Bug Fixes"
+.IX Header "Selected Bug Fixes"
+.IP "\(bu" 4
+Perl 5.28 introduced an \f(CW\*(C`index()\*(C'\fR optimization when comparing to \-1 (or
+indirectly, e.g. >= 0).  When this optimization was triggered inside a \f(CW\*(C`when\*(C'\fR
+clause it caused a warning (\*(L"Argument \f(CW%s\fR isn't numeric in smart match\*(R").  This
+has now been fixed.
+[\s-1GH\s0 #16626] <https://github.com/Perl/perl5/issues/16626>
+.IP "\(bu" 4
+Matching of decimal digits in script runs, introduced in Perl 5.28, had a bug
+that led to \f(CW"1\eN{THAI DIGIT FIVE}"\fR matching \f(CW\*(C`/^(*sr:\ed+)$/\*(C'\fR when it should
+not.  This has now been fixed.
+.IP "\(bu" 4
+The new in-place editing code no longer leaks directory handles.
+[\s-1GH\s0 #16602] <https://github.com/Perl/perl5/issues/16602>
+.SH "Acknowledgements"
+.IX Header "Acknowledgements"
+Perl 5.28.1 represents approximately 5 months of development since Perl 5.28.0
+and contains approximately 6,100 lines of changes across 44 files from 12
+authors.
+.PP
+Excluding auto-generated files, documentation and release tools, there were
+approximately 700 lines of changes to 12 .pm, .t, .c and .h files.
+.PP
+Perl continues to flourish into its fourth decade thanks to a vibrant community
+of users and developers.  The following people are known to have contributed
+the improvements that became Perl 5.28.1:
+.PP
+Aaron Crane, Abigail, Chris 'BinGOs' Williams, Dagfinn Ilmari Mannsåker, David
+Mitchell, James E Keenan, John \s-1SJ\s0 Anderson, Karen Etheridge, Karl Williamson,
+Sawyer X, 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 \s-1CPAN\s0 modules
+included in Perl's core.  We're grateful to the entire \s-1CPAN\s0 community for
+helping Perl to flourish.
+.PP
+For a more complete list of all of Perl's historical contributors, please see
+the \fI\s-1AUTHORS\s0\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 perl bug database
+at <https://rt.perl.org/> .  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 perlbug 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 see
+\&\*(L"\s-1SECURITY VULNERABILITY CONTACT INFORMATION\*(R"\s0 in perlsec
+for details of how to report the issue.
+.SH "Give Thanks"
+.IX Header "Give Thanks"
+If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
+you can do so by running the \f(CW\*(C`perlthanks\*(C'\fR program:
+.PP
+.Vb 1
+\&    perlthanks
+.Ve
+.PP
+This will send an email to the Perl 5 Porters list with your show of thanks.
+.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 \fI\s-1INSTALL\s0\fR file for how to build Perl.
+.PP
+The \fI\s-1README\s0\fR file for general stuff.
+.PP
+The \fIArtistic\fR and \fICopying\fR files for copyright information.