From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 27282@debbugs.gnu.org
Subject: bug#27282: Perl 5.26.0 "dotless @INC" [was Re: bug#27227: [PATCH] gnu: perl: Update to 5.26.0.]
Date: Wed, 14 Jun 2017 09:38:12 +0200 [thread overview]
Message-ID: <87a85bt3x7.fsf@gnu.org> (raw)
In-Reply-To: <20170613194727.GA29641@jasmine.lan> (Leo Famulari's message of "Tue, 13 Jun 2017 15:47:27 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Sun, Jun 11, 2017 at 10:48:02PM -0400, Leo Famulari wrote:
>> I filed a bug report:
>>
>> https://github.com/swig/swig/issues/997
>>
>> In the meantime, setting PERL_USE_UNSAFE_INC will give us what we had
>> before, which is a SWIG that looks for modules in the current working
>> directory.
>
> The upstream fix has basically the same effect:
>
> https://github.com/swig/swig/commit/8855ef2b482c09da9255079b0fac92d08c8308fb
>
> To avoid adding another patch, I'll push the change to set
> PERL_USE_UNSAFE_INC to core-updates soon unless there is an objection.
Sounds good to me. Thanks for taking care of it!
Ludo’.
next prev parent reply other threads:[~2017-06-14 7:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 8:40 bug#27227: [PATCH] gnu: perl: Update to 5.26.0 Leo Famulari
2017-06-04 13:45 ` Marius Bakke
2017-06-04 16:37 ` Leo Famulari
2017-06-04 18:35 ` Marius Bakke
2017-06-04 19:19 ` Leo Famulari
2017-06-07 22:37 ` bug#27282: Perl 5.26.0 "dotless @INC" [was Re: bug#27227: [PATCH] gnu: perl: Update to 5.26.0.] Leo Famulari
2017-06-08 0:25 ` bug#27282: Perl 5.26.0 "dotless @INC" Leo Famulari
2017-06-08 12:28 ` bug#27282: Perl 5.26.0 "dotless @INC" [was Re: bug#27227: [PATCH] gnu: perl: Update to 5.26.0.] Ludovic Courtès
2017-06-08 15:29 ` Leo Famulari
2017-06-12 2:48 ` Leo Famulari
2017-06-13 19:47 ` Leo Famulari
2017-06-14 7:38 ` Ludovic Courtès [this message]
2017-06-14 14:30 ` Leo Famulari
2017-08-02 22:10 ` Ludovic Courtès
2017-08-02 22:41 ` Leo Famulari
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=87a85bt3x7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27282@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.