All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9921] New: lockfile module within python-daemon not available
Date: Wed, 31 May 2017 16:31:48 +0000	[thread overview]
Message-ID: <bug-9921-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=9921

            Bug ID: 9921
           Summary: lockfile module within python-daemon not available
           Product: buildroot
           Version: 2017.02.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: reto.rayen at outlook.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Hi guys

we found a bug which is encountering when we use the python-daemon to run a
script as a daemon. When we want to start the daemon. It always fails because
the lockfile within the python-daemon is not available. Can you please add this
to the standard buildroot image when the package "python-daemon" gets compiled.
We encounter the issue with python2 and python3. In both versions it's not
included. Below you can find a error trace:

Traceback (most recent call last):
  File "/usr/local/bin/bender-daemon", line 9, in <module>
    from daemon import runner
  File
"/home/deployer/projects/buildroot-2017.02.2/output/target/usr/lib/python3.5/site-packages/daemon/runner.py",
line 33, in <module>
ImportError: No module named 'lockfile'

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-05-31 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31 16:31 bugzilla at busybox.net [this message]
2017-05-31 19:10 ` [Buildroot] [Bug 9921] lockfile module within python-daemon not available bugzilla at busybox.net
2017-05-31 19:39 ` bugzilla at busybox.net
2017-06-09  8:17   ` Yegor Yefremov
2017-06-09  8:30     ` Yegor Yefremov
2018-06-06 19:16 ` bugzilla at busybox.net

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=bug-9921-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.