From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: yegorslists--- via buildroot <buildroot@buildroot.org>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH] python-configobj: new package
Date: Tue, 6 Aug 2024 22:35:42 +0200 [thread overview]
Message-ID: <20240806223542.31af8fee@windsurf> (raw)
In-Reply-To: <20231011072701.1014328-1-yegorslists@googlemail.com>
On Wed, 11 Oct 2023 09:27:01 +0200
yegorslists--- via buildroot <buildroot@buildroot.org> wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> python-configobj package was removed in
> 8d264a96172cfa1c1f515d1160b921c013fa3bd7 because of the missing support
> for Python 3.x.
>
> Meanwhile, this problem was fixed, hence readd the package.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> Config.in.legacy | 6 ------
> package/Config.in | 1 +
> package/python-configobj/Config.in | 7 +++++++
> package/python-configobj/python-configobj.hash | 5 +++++
> package/python-configobj/python-configobj.mk | 14 ++++++++++++++
> 5 files changed, 27 insertions(+), 6 deletions(-)
> create mode 100644 package/python-configobj/Config.in
> create mode 100644 package/python-configobj/python-configobj.hash
> create mode 100644 package/python-configobj/python-configobj.mk
Sorry for the huge delay, but... patch applied!
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-06 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 7:27 [Buildroot] [PATCH] python-configobj: new package yegorslists--- via buildroot
2024-01-28 21:35 ` Yegor Yefremov via buildroot
2024-08-06 20:35 ` Thomas Petazzoni via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-11 9:13 Zoltan Gyarmati
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=20240806223542.31af8fee@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--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