From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "pr@gentoo.org" <pr@gentoo.org>
Subject: [gentoo-dev] RFC: News item: Perl 5.26 update
Date: Sat, 07 Oct 2017 17:03:44 +0200 [thread overview]
Message-ID: <2838067.DFkGrR0re6@porto> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1373 bytes --]
See plaintext below and identical attached file.
=======================================
Title: Perl 5.26 update: possible breakage
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Posted: xxxxxxx
Revision: 1
News-Item-Format: 2.0
Display-If-Installed: >=dev-lang/perl-5.26.0
You have just upgraded to Perl 5.26. This release brings several
incompatible changes, also as a consequence of fixing a security
problem [1]. While we have made sure that all resulting build
failures within Gentoo are fixed, this may not be the case for
runtime issues, and certainly can affect third-party code (e.g.,
"hand-installed" server applications).
Typical errors are
"Can't locate inc/... in @INC (you may need to install the inc::...
module)"
"error: ... has no member named ‘op_sibling’"
"Unescaped left brace in regex is illegal in ..."
Please see the pages [2,3] for details and report bugs if you run
into problems during or after the Perl update.
[1] https://rt.perl.org/Ticket/Display.html?id=127834
https://bugs.gentoo.org/show_bug.cgi?id=589680
[2] https://wiki.gentoo.org/wiki/Project:Perl/Dot-In-INC-Removal
[3] https://wiki.gentoo.org/wiki/Project:Perl/5.26_Known_Issues
=======================================
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)
[-- Attachment #1.2: 2017-10-xx-perl-526-update.en.txt --]
[-- Type: text/plain, Size: 1133 bytes --]
Title: Perl 5.26 update: possible breakage
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Posted: xxxxxxx
Revision: 1
News-Item-Format: 2.0
Display-If-Installed: >=dev-lang/perl-5.26.0
You have just upgraded to Perl 5.26. This release brings several
incompatible changes, also as a consequence of fixing a security
problem [1]. While we have made sure that all resulting build
failures within Gentoo are fixed, this may not be the case for
runtime issues, and certainly can affect third-party code (e.g.,
"hand-installed" server applications).
Typical errors are
"Can't locate inc/... in @INC (you may need to install the inc::... module)"
"error: ... has no member named ‘op_sibling’"
"Unescaped left brace in regex is illegal in ..."
Please see the pages [2,3] for details and report bugs if you run
into problems during or after the Perl update.
[1] https://rt.perl.org/Ticket/Display.html?id=127834
https://bugs.gentoo.org/show_bug.cgi?id=589680
[2] https://wiki.gentoo.org/wiki/Project:Perl/Dot-In-INC-Removal
[3] https://wiki.gentoo.org/wiki/Project:Perl/5.26_Known_Issues
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-10-07 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 15:03 Andreas K. Huettel [this message]
2017-10-07 15:21 ` [gentoo-dev] RFC: News item: Perl 5.26 update Kent Fredric
2017-10-07 15:52 ` Andreas K. Huettel
2017-10-07 16:15 ` Aaron W. Swenson
2017-10-07 16:44 ` Kent Fredric
2017-10-08 12:01 ` [gentoo-dev] RFC v2: " Andreas K. Huettel
2017-10-08 12:41 ` Aaron W. Swenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2838067.DFkGrR0re6@porto \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox