diff options
Diffstat (limited to 'upstream/debian-bookworm/man1/perl5142delta.1')
-rw-r--r-- | upstream/debian-bookworm/man1/perl5142delta.1 | 259 |
1 files changed, 259 insertions, 0 deletions
diff --git a/upstream/debian-bookworm/man1/perl5142delta.1 b/upstream/debian-bookworm/man1/perl5142delta.1 new file mode 100644 index 00000000..cc288a48 --- /dev/null +++ b/upstream/debian-bookworm/man1/perl5142delta.1 @@ -0,0 +1,259 @@ +.\" 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 "PERL5142DELTA 1" +.TH PERL5142DELTA 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" +perl5142delta \- what is new for perl v5.14.2 +.SH "DESCRIPTION" +.IX Header "DESCRIPTION" +This document describes differences between the 5.14.1 release and +the 5.14.2 release. +.PP +If you are upgrading from an earlier release such as 5.14.0, first read +perl5141delta, which describes differences between 5.14.0 and +5.14.1. +.SH "Core Enhancements" +.IX Header "Core Enhancements" +No changes since 5.14.0. +.SH "Security" +.IX Header "Security" +.ie n .SS """File::Glob::bsd_glob()"" memory error with \s-1GLOB_ALTDIRFUNC\s0 (\s-1CVE\-2011\-2728\s0)." +.el .SS "\f(CWFile::Glob::bsd_glob()\fP memory error with \s-1GLOB_ALTDIRFUNC\s0 (\s-1CVE\-2011\-2728\s0)." +.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 \s-1GLOB_ALTDIRFUNC\s0 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. +.ie n .SS """Encode"" decode_xs n\-byte heap-overflow (\s-1CVE\-2011\-2939\s0)" +.el .SS "\f(CWEncode\fP decode_xs n\-byte heap-overflow (\s-1CVE\-2011\-2939\s0)" +.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. +.SH "Incompatible Changes" +.IX Header "Incompatible Changes" +There are no changes intentionally incompatible with 5.14.0. If any +exist, they are bugs and reports are welcome. +.SH "Deprecations" +.IX Header "Deprecations" +There have been no deprecations since 5.14.0. +.SH "Modules and Pragmata" +.IX Header "Modules and Pragmata" +.SS "New Modules and Pragmata" +.IX Subsection "New Modules and Pragmata" +None +.SS "Updated Modules and Pragmata" +.IX Subsection "Updated Modules and Pragmata" +.IP "\(bu" 4 +\&\s-1CPAN\s0 has been upgraded from version 1.9600 to version 1.9600_01. +.Sp +CPAN::Distribution has been upgraded from version 1.9602 to 1.9602_01. +.Sp +Backported bugfixes from \s-1CPAN\s0 version 1.9800. Ensures proper +detection of \f(CW\*(C`configure_requires\*(C'\fR prerequisites from \s-1CPAN\s0 Meta files +in the case where \f(CW\*(C`dynamic_config\*(C'\fR is true. [rt.cpan.org #68835] +.Sp +Also ensures that \f(CW\*(C`configure_requires\*(C'\fR is only checked in \s-1META\s0 files, +not \s-1MYMETA\s0 files, so protect against \s-1MYMETA\s0 generation that drops +\&\f(CW\*(C`configure_requires\*(C'\fR. +.IP "\(bu" 4 +Encode has been upgraded from version 2.42 to 2.42_01. +.Sp +See \*(L"Security\*(R". +.IP "\(bu" 4 +File::Glob has been upgraded from version 1.12 to version 1.13. +.Sp +See \*(L"Security\*(R". +.IP "\(bu" 4 +PerlIO::scalar has been upgraded from version 0.11 to 0.11_01. +.Sp +It fixes a problem with \f(CW\*(C`open my $fh, ">", \e$scalar\*(C'\fR not working if +\&\f(CW$scalar\fR is a copy-on-write scalar. +.SS "Removed Modules and Pragmata" +.IX Subsection "Removed Modules and Pragmata" +None +.SH "Platform Support" +.IX Header "Platform Support" +.SS "New Platforms" +.IX Subsection "New Platforms" +None +.SS "Discontinued Platforms" +.IX Subsection "Discontinued Platforms" +None +.SS "Platform-Specific Notes" +.IX Subsection "Platform-Specific Notes" +.IP "HP-UX \s-1PA\-RISC/64\s0 now supports gcc\-4.x" 4 +.IX Item "HP-UX PA-RISC/64 now supports gcc-4.x" +A fix to correct the socketsize now makes the test suite pass on HP-UX +PA-RISC for 64bitall builds. +.IP "Building on \s-1OS X 10.7\s0 Lion and Xcode 4 works again" 4 +.IX Item "Building on OS X 10.7 Lion and Xcode 4 works again" +The build system has been updated to work with the build tools under Mac \s-1OS X +10.7.\s0 +.SH "Bug Fixes" +.IX Header "Bug Fixes" +.IP "\(bu" 4 +In \f(CW@INC\fR filters (subroutines returned by subroutines in \f(CW@INC\fR), \f(CW$_\fR used to +misbehave: If returned from a subroutine, it would not be copied, but the +variable itself would be returned; and freeing \f(CW$_\fR (e.g., with \f(CW\*(C`undef *_\*(C'\fR) +would cause perl to crash. This has been fixed [perl #91880]. +.IP "\(bu" 4 +Perl 5.10.0 introduced some faulty logic that made \*(L"U*\*(R" in the middle of +a pack template equivalent to \*(L"U0\*(R" if the input string was empty. This has +been fixed [perl #90160]. +.IP "\(bu" 4 +\&\f(CW\*(C`caller\*(C'\fR no longer leaks memory when called from the \s-1DB\s0 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 +\&\f(CW\*(C`utf8::decode\*(C'\fR had a nasty bug that would modify copy-on-write scalars' +string buffers in place (i.e., skipping the copy). This could result in +hashes having two elements with the same key [perl #91834]. +.IP "\(bu" 4 +Localising a tied variable used to make it read-only if it contained a +copy-on-write string. +.IP "\(bu" 4 +Elements of restricted hashes (see the fields pragma) containing +copy-on-write values couldn't be deleted, nor could such hashes be cleared +(\f(CW\*(C`%hash = ()\*(C'\fR). +.IP "\(bu" 4 +Locking a hash element that is a glob copy no longer causes subsequent +assignment to it to corrupt the glob. +.IP "\(bu" 4 +A panic involving the combination of the regular expression modifiers +\&\f(CW\*(C`/aa\*(C'\fR introduced in 5.14.0 and the \f(CW\*(C`\eb\*(C'\fR escape sequence has been +fixed [perl #95964]. +.SH "Known Problems" +.IX Header "Known Problems" +This is a list of some significant unfixed bugs, which are regressions +from 5.12.0. +.IP "\(bu" 4 +\&\f(CW\*(C`PERL_GLOBAL_STRUCT\*(C'\fR is broken. +.Sp +Since perl 5.14.0, building with \f(CW\*(C`\-DPERL_GLOBAL_STRUCT\*(C'\fR hasn't been +possible. This means that perl currently doesn't work on any platforms that +require it to be built this way, including Symbian. +.Sp +While \f(CW\*(C`PERL_GLOBAL_STRUCT\*(C'\fR now works again on recent development versions of +perl, it actually working on Symbian again hasn't been verified. +.Sp +We'd be very interested in hearing from anyone working with Perl on Symbian. +.SH "Acknowledgements" +.IX Header "Acknowledgements" +Perl 5.14.2 represents approximately three months of development since +Perl 5.14.1 and contains approximately 1200 lines of changes +across 61 files from 9 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.14.2: +.PP +Craig A. Berry, David Golden, Father Chrysostomos, Florian Ragwitz, H.Merijn +Brand, Karl Williamson, Nicholas Clark, Pau Amma and Ricardo Signes. +.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 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 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 \s-1CPAN.\s0 +.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. |