From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14321] Error: Could not install package {PACKAGE}: 'name'
Date: Thu, 04 Nov 2021 15:38:19 +0000 [thread overview]
Message-ID: <bug-14321-163-IvTlKTGvCm@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14321-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14321
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
scanpypi is not there to install a Python package, it is a script to help
create a new Buildroot package for a Python module.
First of all, you should not use Buildroot as root, nor scanpypi itself.
Secondly, I'm not sure how pyinstaller can be useful in the context of
Buildroot. According to its description, "PyInstaller bundles a Python
application and all its dependencies into a single package. The user can run
the packaged app without installing a Python interpreter or any modules.". I
don't see how having pyinstaller available on the target system is going to be
of any use.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-04 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 14:33 [Buildroot] [Bug 14321] New: Error: Could not install package {PACKAGE}: 'name' bugzilla
2021-11-04 15:38 ` bugzilla [this message]
2021-11-04 15:38 ` [Buildroot] [Bug 14321] scanpypi doesn't work with the pyinstaller module bugzilla
2021-11-04 17:09 ` bugzilla
2021-11-04 17:36 ` bugzilla
2021-11-05 15:19 ` bugzilla
2021-11-05 23:24 ` bugzilla
2021-11-06 11:04 ` bugzilla
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-14321-163-IvTlKTGvCm@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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