From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Asaf Kahlon <asafka7@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 2/3] package/python-crossbar: drop package
Date: Tue, 6 Feb 2024 23:31:22 +0100 [thread overview]
Message-ID: <20240206233122.30f9be84@windsurf> (raw)
In-Reply-To: <20231218220457.1705749-2-adam.duskett@amarulasolutions.com>
On Mon, 18 Dec 2023 15:04:55 -0700
Adam Duskett <adam.duskett@amarulasolutions.com> wrote:
> The current package has not recieved an update since Sat Oct 9 2021
> 33ece2446e25e20929d1c7eefa9f3244a3b79a92 and is not python 3.12 compatible.
>
> Furthermore, the current version requires at least 42 new packages worth of
> depedencies of which several require patches to be python 3.12 compatible.
> As nobody has stepped up to maintain the package and its ever-growing list of
> dependencies, along with the other problems, it is time to drop the package.
>
> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
> ---
> Config.in.legacy | 16 ++++
> DEVELOPERS | 1 -
> package/Config.in | 1 -
> .../0001-Avoid-intentional-syntax-error.patch | 29 --------
> ...s-min.txt-drop-indirect-dependencies.patch | 74 -------------------
> ...ice-wap-use-markupsafe-instead-of-we.patch | 53 -------------
> package/python-crossbar/Config.in | 72 ------------------
> package/python-crossbar/python-crossbar.hash | 5 --
> package/python-crossbar/python-crossbar.mk | 14 ----
> 9 files changed, 16 insertions(+), 249 deletions(-)
> delete mode 100644 package/python-crossbar/0001-Avoid-intentional-syntax-error.patch
> delete mode 100644 package/python-crossbar/0002-requirements-min.txt-drop-indirect-dependencies.patch
> delete mode 100644 package/python-crossbar/0003-crossbar-webservice-wap-use-markupsafe-instead-of-we.patch
> delete mode 100644 package/python-crossbar/Config.in
> delete mode 100644 package/python-crossbar/python-crossbar.hash
> delete mode 100644 package/python-crossbar/python-crossbar.mk
Applied to master, 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-02-06 22:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 22:04 [Buildroot] [PATCH v4 1/3] package/python-pygame: drop package Adam Duskett
2023-12-18 22:04 ` [Buildroot] [PATCH v4 2/3] package/python-crossbar: " Adam Duskett
2024-02-06 22:31 ` Thomas Petazzoni via buildroot [this message]
2023-12-18 22:04 ` [Buildroot] [PATCH v4 3/3] package/python3: bump version to 3.12.1 Adam Duskett
2023-12-24 22:12 ` Adam Duskett
2024-02-06 22:33 ` Thomas Petazzoni via buildroot
2024-02-07 2:32 ` James Hilliard
2024-02-24 13:58 ` Peter Korsgaard
[not found] ` <87wmqut14w.fsf__36507.8827760712$1708783134$gmane$org@48ers.dk>
2024-02-24 19:01 ` Bernd Kuhls
2024-02-25 11:21 ` Yann E. MORIN
2024-02-26 14:02 ` Arnout Vandecappelle via buildroot
2024-02-06 22:31 ` [Buildroot] [PATCH v4 1/3] package/python-pygame: drop package Thomas Petazzoni via buildroot
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=20240206233122.30f9be84@windsurf \
--to=buildroot@buildroot.org \
--cc=adam.duskett@amarulasolutions.com \
--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