Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gpsd: do not interact with systemd on install
Date: Mon, 15 May 2017 14:07:50 +0200	[thread overview]
Message-ID: <87fug6iaqx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170513082736.22734-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Sat, 13 May 2017 10:27:36 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > When building on a systemd-based host for a systemd-based target, gpsd's
 > buildsystem will try to tell systemd to reload the its configuration and
 > recreate the entire dependency tree of services.

 > Of course, this can not work when run as a user:
 >>>> gpsd 3.16 Installing to target
 >     ==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
 >     Authentication is required to reload the systemd state.
 >     Authenticating as: root
 >     Password:

 > In fact, this does not even mean anything in cross-compilation.

 > Fortunately, upstream has already fixed their sin, so we backport it
 > (tweaked to apply onto 3.16).

 > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
 > Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>

 > ---
 > Note: this was never observed in any of the autobuilders, even those
 > running on a systemd-based distro, because in this case stdin is
 > redirected and systemctl simply fails, but the construct is just to
 > ignore the failure, so the build proceeds; the issue only occurs when
 > there is an actual terminal to provide user input... :-/

Committed to 2017.02.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2017-05-15 12:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13  8:27 [Buildroot] [PATCH] package/gpsd: do not interact with systemd on install Yann E. MORIN
2017-05-13 12:58 ` Thomas Petazzoni
2017-05-15 12:07 ` Peter Korsgaard [this message]

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=87fug6iaqx.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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