From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] Prepare for python3
Date: Fri, 10 Mar 2017 15:32:18 +0100 [thread overview]
Message-ID: <1489156338.1865.0@mail01.ipfire.org> (raw)
In-Reply-To: <1489156222-29550-2-git-send-email-jonatan.schlag@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
Sorry this path is already in next, he can safely ignored.
Am Fr, 10. Mär, 2017 um 3:30 schrieb Jonatan Schlag
<jonatan.schlag(a)ipfire.org>:
> The build of ipaadr fails with python3 because two possibilities of
> /usr/lib/python* are availible. This patch set the path to
> /usr/lib/python2* to make the path clear.
>
> Signed-off-by: Jonatan Schlag <jonatan.schlag(a)ipfire.org>
> ---
> lfs/ipaddr | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lfs/ipaddr b/lfs/ipaddr
> index 4b74e02..186141c 100644
> --- a/lfs/ipaddr
> +++ b/lfs/ipaddr
> @@ -70,7 +70,7 @@ $(subst %,%_MD5,$(objects)) :
> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> @$(PREBUILD)
> @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
> - cd $(DIR_APP) && install -m 0644 ipaddr.py /usr/lib/python*
> + cd $(DIR_APP) && install -m 0644 ipaddr.py /usr/lib/python2*
> /usr/bin/python -c "import ipaddr"
> @rm -rf $(DIR_APP)
> @$(POSTBUILD)
> --
> 2.1.4
>
next prev parent reply other threads:[~2017-03-10 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 14:30 [PATCH 1/2] Fix rootfile of keepalived after initscript changes Jonatan Schlag
2017-03-10 14:30 ` [PATCH 1/2] Prepare for python3 Jonatan Schlag
2017-03-10 14:32 ` Jonatan Schlag [this message]
2017-03-10 16:40 ` Michael Tremer
-- strict thread matches above, loose matches on Subject: below --
2017-01-23 15:17 Python3 Jonatan Schlag
2017-01-23 15:17 ` [PATCH 1/2] Prepare for python3 Jonatan Schlag
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=1489156338.1865.0@mail01.ipfire.org \
--to=jonatan.schlag@ipfire.org \
--cc=development@lists.ipfire.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