From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/nfs-utils: fix nfs-utils_env.sh path
Date: Fri, 4 Oct 2019 14:55:00 +0200 [thread overview]
Message-ID: <20191004145500.6d87de51@windsurf> (raw)
In-Reply-To: <CADvTj4qg4CffhdG8bd-tLxU7vp-K5713UF+uVO0wku92WOfFjQ@mail.gmail.com>
On Fri, 4 Oct 2019 14:43:18 +0200
James Hilliard <james.hilliard1@gmail.com> wrote:
> > If I get it correctly looking at upstream commit
> > bf12e1fa9f48e8ee91a2869e69484c70595b5160, this script is only used from
> > nfs-config.service, and we are not installing nfs-config.service. So
> > what is the impact ?
> The package itself handles nfs-config.service installation so we do use it.
> See:
> http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=blob;f=systemd/Makefile.am;h=03f96e93dccf814f7c8aee5cc9a78083231fefb3;hb=188354e57dd8476e66ce30d647180a106da29b88#l8
OK.
> > Also, could you indicate if this issue is applicable to 2019.02.x,
> > 2019.05.x and 2019.08.x ? I guess it depends on which version of
> > nfs-utils is currently shipped in those branches, and whether they have
> > bf12e1fa9f48e8ee91a2869e69484c70595b5160 or not.
> It was broken by buildroot commit 06445ee36dee49555599bc9c963201bce237ab64
> so anything before that should be fine.
OK, so 2019.08.x is affected, but not 2019.05.x and 2019.02.x.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-04 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 14:04 [Buildroot] [PATCH 1/1] package/nfs-utils: fix nfs-utils_env.sh path James Hilliard
2019-10-03 18:14 ` Carlos Santos
2019-10-04 8:16 ` Thomas Petazzoni
2019-10-04 12:43 ` James Hilliard
2019-10-04 12:55 ` Thomas Petazzoni [this message]
2019-10-05 21:35 ` Thomas Petazzoni
2019-10-28 9:39 ` 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=20191004145500.6d87de51@windsurf \
--to=thomas.petazzoni@bootlin.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