From: anisse at astier.eu <anisse@astier.eu>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libglib2: Avoid absolute path to python in shebang
Date: Thu, 19 Jul 2018 13:55:06 +0200 [thread overview]
Message-ID: <20180719115506.5lyyqwk2betdivo7@bifrost> (raw)
In-Reply-To: <87va9bcwr9.fsf@dell.be.48ers.dk>
On Thu, Jul 19, 2018 at 01:04:10PM +0200, Peter Korsgaard wrote:
> >>>>> "Anisse" == Anisse Astier <anisse@astier.eu> writes:
>
> > Hi,
> > We just hit this issue with the buildroot-2018.02 branch. Is this is the
> > scope of LTS-backportable patches ?
>
> > Otherwise it's very easy to take the patch in an external, but I'm
> > guessing it might break other builds somewhere.
>
> Yes, I'll backport to 2018.02.x and 2018.05.x. I'm running a bit behind
> though (synched around July 1st), so it will take a few days.
>
> Does the patch apply as is to 2018.02.x? Have you verified that it fixes
> the issue for you on 2018.02.x?
Yes, I have verified that the patch applies cleanly to libglib2 2.54.2
(the version in the 2018.02.x branch), and that it fixes the build of
json-glib, a package that was affected by the issue.
Regards,
Anisse
next prev parent reply other threads:[~2018-07-19 11:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 16:37 [Buildroot] [PATCH 1/1] libglib2: Avoid absolute path to python in shebang David Owens
2018-07-18 15:18 ` Thomas Petazzoni
2018-07-19 7:58 ` Anisse Astier
2018-07-19 8:04 ` Thomas Petazzoni
2018-07-19 11:50 ` anisse at astier.eu
2018-07-19 12:15 ` Thomas Petazzoni
2018-07-19 12:58 ` anisse at astier.eu
2018-07-19 13:24 ` Thomas Petazzoni
2018-07-19 11:04 ` Peter Korsgaard
2018-07-19 11:55 ` anisse at astier.eu [this message]
2018-07-19 21:44 ` Peter Korsgaard
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=20180719115506.5lyyqwk2betdivo7@bifrost \
--to=anisse@astier.eu \
--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 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.