From: Peter Korsgaard <peter@korsgaard.com>
To: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
Cc: Asaf Kahlon <asafka7@gmail.com>,
James Hilliard <james.hilliard1@gmail.com>,
Marcus Hoffmann <buildroot@bubu1.eu>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/python-can: bump to version 4.3.1
Date: Mon, 05 Feb 2024 18:40:41 +0100 [thread overview]
Message-ID: <87ttmmrequ.fsf@48ers.dk> (raw)
In-Reply-To: <db063503-1757-4d25-8abb-20c43d968a9a@bubu1.eu> (Marcus Hoffmann via buildroot's message of "Tue, 9 Jan 2024 18:49:24 +0100")
>>>>> "Marcus" == Marcus Hoffmann via buildroot <buildroot@buildroot.org> writes:
> Hi James,
> On 09.01.24 05:56, James Hilliard wrote:
>> Drop no longer used python-aenum runtime dependency.
>> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
>> ---
>> package/python-can/Config.in | 1 -
>> package/python-can/python-can.hash | 4 ++--
>> package/python-can/python-can.mk | 4 ++--
>> 3 files changed, 4 insertions(+), 5 deletions(-)
>> diff --git a/package/python-can/Config.in
>> b/package/python-can/Config.in
>> index 68a9ffca71..27dc16fa33 100644
>> --- a/package/python-can/Config.in
>> +++ b/package/python-can/Config.in
>> @@ -2,7 +2,6 @@ config BR2_PACKAGE_PYTHON_CAN
>> bool "python-can"
>> select BR2_PACKAGE_PYTHON_SETUPTOOLS # runtime
> setuptools is no longer required as well:
> https://github.com/hardbyte/python-can/commit/1a3f5e3769aa565ada8c27177a94f7db43d019dc
Committed after dropping the setuptools dependency, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-02-05 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 4:56 [Buildroot] [PATCH 1/1] package/python-can: bump to version 4.3.1 James Hilliard
2024-01-09 17:49 ` Marcus Hoffmann via buildroot
2024-02-05 17:40 ` 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=87ttmmrequ.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=angelo.compagnucci@gmail.com \
--cc=asafka7@gmail.com \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.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