From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org,
James Hilliard <james.hilliard1@gmail.com>,
Fiona Klute <fiona.klute@gmx.de>
Subject: Re: [Buildroot] [PATCH v2 2/2] package/python-emailproxy: new package
Date: Sun, 29 Dec 2024 22:12:55 +0100 [thread overview]
Message-ID: <20241229221255.2138fc09@windsurf> (raw)
In-Reply-To: <20241211191630.1414970-2-bernd@kuhls.net>
Hello Bernd,
On Wed, 11 Dec 2024 20:16:30 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> +PYTHON_EMAILPROXY_VERSION = 2024.11.11
> +PYTHON_EMAILPROXY_SOURCE = emailproxy-$(PYTHON_EMAILPROXY_VERSION).tar.gz
> +PYTHON_EMAILPROXY_SITE = https://files.pythonhosted.org/packages/2b/49/386e675f2b0706083fdf02ad3666b98d0875a2e1cdcabff8df9fe641d2e3
> +PYTHON_EMAILPROXY_DEPENDENCIES = host-python-cryptography host-python-pyasyncore
I am still not happy with host-python-cryptography
host-python-pyasyncore being dependencies, while they definitely
shouldn't be needed. I know James asked you to use
--skip-dependency-check, and it apparently wasn't working with:
File "/home/bernd/buildroot/output/build/python-emailproxy-2024.9.12/
emailproxy.py", line 52, in <module>
import asyncore
ModuleNotFoundError: No module named 'asyncore'
Do we have an explanation why?
Adding those dependencies really feels like a hack.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-12-29 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 19:16 [Buildroot] [PATCH 1/2] package/python-pyasyncore: enable host package Bernd Kuhls
2024-12-11 19:16 ` [Buildroot] [PATCH v2 2/2] package/python-emailproxy: new package Bernd Kuhls
2024-12-29 21:12 ` Thomas Petazzoni via buildroot [this message]
2025-01-13 18:17 ` Fiona Klute via buildroot
[not found] ` <PH1P110MB1603B3EEB73618CFAF45272D9F1FA@PH1P110MB1603.NAMP110.PROD.OUTLOOK.COM>
[not found] ` <25105903-5086-463e-847b-d4a392f0cbd0@gmx.de>
[not found] ` <PH1P110MB1603F80585C666F0A6C9336A9F1FA@PH1P110MB1603.NAMP110.PROD.OUTLOOK.COM>
2025-01-26 21:52 ` [Buildroot] [External] - " Bernd Kuhls
2025-01-27 1:48 ` James Hilliard
2025-01-27 13:09 ` Vincent Fazio
2025-01-27 19:00 ` Vincent Fazio
2025-01-27 19:49 ` [Buildroot] " James Hilliard
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=20241229221255.2138fc09@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=fiona.klute@gmx.de \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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