All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 3/4] package/fail2ban: bump version to 1.1.0
Date: Tue, 9 Jul 2024 21:45:19 +0200	[thread overview]
Message-ID: <20240709214519.2c8c5968@windsurf> (raw)
In-Reply-To: <20240709101841.1145134-4-fiona.klute@gmx.de>

Hello Fiona,

On Tue,  9 Jul 2024 12:18:40 +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.
> 
> Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
> ---
> Changes v2 -> v3:
> * Add "# runtime" comment for pyasynchat dependency, drop
>   FAIL2BAN_DEPENDENCIES in fail2ban.mk

Unfortunately, this updated package fails to build for me:

/bin/sed -i -e '/^socket/c\socket = /run/fail2ban.sock' /home/thomas/projets/buildroot/output/target/etc/fail2ban/fail2ban.conf
/bin/sed: can't read /home/thomas/projets/buildroot/output/target/etc/fail2ban/fail2ban.conf: No such file or directory
make: *** [package/pkg-generic.mk:378: /home/thomas/projets/buildroot/output/build/fail2ban-1.1.0/.stamp_target_installed] Error 2

The /etc/fail2ban/fail2ban.conf file is apparently no longer installed.
Did you try the fail2ban build from a fully clean build?

Best regards,

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

  reply	other threads:[~2024-07-09 19:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 10:18 [Buildroot] [PATCH v3 0/4] Update fail2ban to 1.1.0, add dependencies Fiona Klute via buildroot
2024-07-09 10:18 ` [Buildroot] [PATCH v3 1/4] package/python-pyasyncore: new package Fiona Klute via buildroot
2024-07-09 19:42   ` Thomas Petazzoni via buildroot
2024-07-09 10:18 ` [Buildroot] [PATCH v3 2/4] package/python-pyasynchat: " Fiona Klute via buildroot
2024-07-09 19:44   ` Thomas Petazzoni via buildroot
2024-07-09 10:18 ` [Buildroot] [PATCH v3 3/4] package/fail2ban: bump version to 1.1.0 Fiona Klute via buildroot
2024-07-09 19:45   ` Thomas Petazzoni via buildroot [this message]
2024-07-09 19:52     ` Angelo Compagnucci
2024-07-09 20:18       ` Thomas Petazzoni via buildroot
2024-07-12 14:08   ` Arnout Vandecappelle via buildroot
2024-07-09 10:18 ` [Buildroot] [PATCH v3 4/4] package/fail2ban: fix sshd filter with OpenSSH 9.8 Fiona Klute via buildroot
2024-07-12 14:01   ` Arnout Vandecappelle 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=20240709214519.2c8c5968@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.