Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] supervisor: add runtime dependency on python-setuptools
Date: Wed, 11 Jun 2014 21:17:47 +0200	[thread overview]
Message-ID: <7514f33bf3a507a044a5.1402514267@localhost> (raw)

supervisor has a runtime dependency on python-setuptools which was not
expressed in its Config.in file. When running supervisor without setuptools,
one gets:

Starting supervisord: Traceback (most recent call last):
  File "/usr/bin/supervisord", line 5, in <module>
    from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

Partially fixes bug #7184 (https://bugs.busybox.net/show_bug.cgi?id=7184)

Reported-by: Sebastian Himberger <sebastian@himberger.de>
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>

---
 package/supervisor/Config.in |  1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff -r a3b89cb15e8f -r 7514f33bf3a5 package/supervisor/Config.in
--- a/package/supervisor/Config.in	Mon Jun 09 10:43:55 2014 +0200
+++ b/package/supervisor/Config.in	Wed Jun 11 21:15:11 2014 +0200
@@ -2,6 +2,7 @@
 	bool "supervisor"
 	depends on BR2_PACKAGE_PYTHON
 	select BR2_PACKAGE_PYTHON_MELD3
+	select BR2_PACKAGE_PYTHON_SETUPTOOLS # runtime dependency
 	help
 	  A client/server system that allows its users to control a
 	  number of processes on UNIX-like operating systems.

             reply	other threads:[~2014-06-11 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 19:17 Thomas De Schampheleire [this message]
2014-06-11 20:25 ` [Buildroot] [PATCH] supervisor: add runtime dependency on python-setuptools 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=7514f33bf3a507a044a5.1402514267@localhost \
    --to=patrickdepinguin@gmail.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