[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#862901: marked as done (release-notes: further update to perl @INC change)



Your message dated Sat, 3 Jun 2017 17:57:17 +0200
with message-id <20170603175717.042326f9.baptiste@mailoo.org>
and subject line Re: Bug#862901: Stable link
has caused the Debian Bug report #862901,
regarding release-notes: further update to perl @INC change
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
862901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862901
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: normal

Hi,

Further to #859129, please consider this additional patch which refers
to a possible workaround for local issues, and freshly-minted upstream
documentation for developers on the topic.

Index: en/issues.dbk
===================================================================
--- en/issues.dbk   (revision 11492)
+++ en/issues.dbk   (working copy)
@@ -710,6 +710,25 @@
           <literal>require()</literal>, <literal>do()</literal> etc., where the
           arguments are files in the current directory.
         </para>
+        <!-- the link below is temporary; this would ideally point to
+             perldoc.perl.org once 5.26.0 is released since that is more
+             stable -->
+        <para>
+          All perl programs and module shipped by Debian should have been
+          fixed to address any incompatibilities caused by the above; please
+          file bugs if this is not the case. As the change has now been made
+          in perl 5.26.0, third-party software should also start to be fixed.
+          Information about how to fix this issue for developers is provided
+          in the <ulink url="https://perl5.git.perl.org/perl.git/blob_plain/HEAD:/pod/perldelta.pod";>perl 5.26 release notes</ulink> (see the SECURITY section).
+        </para>
+        <para>
+          If needed you can temporarily reinstate <literal>.</literal> in
+          <literal>@INC</literal> globally by commenting out the line in
+          <filename>/etc/perl/sitecustomize.pl</filename> but you should
+          only do this with a understanding of the potential risks. This
+          workaround will be removed in &debian; &nextrelease;. You can
+          also set the <literal>PERL_USE_UNSAFE_INC</literal> environment
+          variable in a specific context which will have the same effect.               </para>
       </listitem>
       <listitem>

--- End Message ---
--- Begin Message ---
Hello, 

Dixit Dominic Hargreaves, le 18/05/2017 :

>Further to #859129, please consider this additional patch which refers
>to a possible workaround for local issues, and freshly-minted upstream
>documentation for developers on the topic.

Dixit Dominic Hargreaves, le 01/06/2017 :

>Please use 
>https://metacpan.org/changes/release/XSAWYERX/perl-5.26.0#Removal-of-the-current-directory-(%22.%22)-from-@INC
>instead of the gitweb link in the previous patch.

Thanks. Commited in r11535.

Baptiste

Attachment: pgpFkYe3r9GlM.pgp
Description: OpenPGP digital signature


--- End Message ---

Reply to: