From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute via buildroot <buildroot@buildroot.org>
Cc: Angelo Compagnucci <angelo.compagnucci@gmail.com>,
James Hilliard <james.hilliard1@gmail.com>,
Fiona Klute <fiona.klute@gmx.de>, Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 3/4] package/fail2ban: bump version to 1.1.0
Date: Mon, 8 Jul 2024 23:56:39 +0200 [thread overview]
Message-ID: <20240708235639.7a9cc07c@windsurf> (raw)
In-Reply-To: <20240704121352.1915154-4-fiona.klute@gmx.de>
Hello Fiona,
On Thu, 4 Jul 2024 14:13:51 +0200
Fiona Klute via buildroot <buildroot@buildroot.org> wrote:
> From: "Fiona Klute (WIWA)" <fiona.klute@gmx.de>
>
> Fail2ban 1.1.0 brings Python 3.12 compatibility, and removes support
> for 2.x. This means 2to3 handling can be dropped.
>
> Unfortunately fail2ban 1.1.0 still relies on asynchat and asyncore,
> which have been removed from the Python standard library in
> 3.12. Depend on the compatibility package python-pyasynchat (which
> pulls in python-pyasyncore) and remove copies bundled in upstream
> code.
Thanks for the detailed commit log. One question below, though.
> -FAIL2BAN_VERSION = 1.0.2
> +FAIL2BAN_VERSION = 1.1.0
> FAIL2BAN_SITE = $(call github,fail2ban,fail2ban,$(FAIL2BAN_VERSION))
> FAIL2BAN_LICENSE = GPL-2.0+
> FAIL2BAN_LICENSE_FILES = COPYING
> FAIL2BAN_CPE_ID_VENDOR = fail2ban
> FAIL2BAN_SELINUX_MODULES = fail2ban
> FAIL2BAN_SETUP_TYPE = setuptools
> +FAIL2BAN_DEPENDENCIES = host-python3 python-pyasynchat
Why are you adding host-python3 in the dependencies here?
Also, are you sure python-pyasynchat is a build time dependency, and
not just a runtime dependency? If that's the case, then you need to
kept the select in the Config.in file (with a comment # runtime), but
not have it as a build-time dependency in fail2ban.mk.
Thanks!
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-07-08 21:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 12:13 [Buildroot] [PATCH v2 0/4] Update fail2ban to 1.1.0, add dependencies Fiona Klute via buildroot
2024-07-04 12:13 ` [Buildroot] [PATCH v2 1/4] package/python-pyasyncore: new package Fiona Klute via buildroot
2024-07-04 12:13 ` [Buildroot] [PATCH v2 2/4] package/python-pyasynchat: " Fiona Klute via buildroot
2024-07-04 12:13 ` [Buildroot] [PATCH v2 3/4] package/fail2ban: bump version to 1.1.0 Fiona Klute via buildroot
2024-07-08 21:56 ` Thomas Petazzoni via buildroot [this message]
2024-07-09 10:19 ` Fiona Klute via buildroot
2024-07-09 11:55 ` Thomas Petazzoni via buildroot
2024-07-09 16:25 ` Fiona Klute via buildroot
2024-07-09 18:35 ` Thomas Petazzoni via buildroot
2024-07-10 11:17 ` Fiona Klute via buildroot
2024-07-10 11:47 ` Thomas Petazzoni via buildroot
2024-07-10 18:41 ` Fiona Klute via buildroot
2024-07-10 19:58 ` Thomas Petazzoni via buildroot
2024-07-04 12:13 ` [Buildroot] [PATCH v2 4/4] package/fail2ban: fix sshd filter with OpenSSH 9.8 Fiona Klute 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=20240708235639.7a9cc07c@windsurf \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=asafka7@gmail.com \
--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