From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 2/2] python3: do not use hg or svn when available
Date: Sun, 18 Sep 2016 17:13:35 +0200 [thread overview]
Message-ID: <20160918171335.24f4f5aa@free-electrons.com> (raw)
In-Reply-To: <1472675909-20905-2-git-send-email-thomas.petazzoni@free-electrons.com>
Hello,
On Wed, 31 Aug 2016 22:38:29 +0200, Thomas Petazzoni wrote:
> During the execution of its configure script, Python 3 tries to find an
> available "hg" installation, and if available, will try to use it to get
> information from the version control system. To do this, it tries to
> communicate over the network, potentially over ports that are blocked,
> causing the build to halt. This was reported by a user as part of bug
> 7802.
>
> To solve this, we simply make the Python script use /bin/false as the
> "hg" program.
>
> Fixes bug #7802 for the python3 package.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> package/python3/python3.mk | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
Applied after fixing the commit title to not mention svn, since python3
never tried to use svn (contrary to python 2.x).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-18 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 20:38 [Buildroot] [PATCH/next 1/2] python: do not use hg or svn when available Thomas Petazzoni
2016-08-31 20:38 ` [Buildroot] [PATCH/next 2/2] python3: " Thomas Petazzoni
2016-09-18 15:13 ` Thomas Petazzoni [this message]
2016-09-18 15:13 ` [Buildroot] [PATCH/next 1/2] python: " Thomas Petazzoni
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=20160918171335.24f4f5aa@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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