GNU bug report logs - #78066
[PATCH 0/2] Fix fail2ban build

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#78066: closed ([PATCH 0/2] Fix fail2ban build)
Date: Tue, 06 May 2025 10:32:04 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 06 May 2025 12:29:08 +0200
with message-id <87a57qvxqj.fsf <at> gnu.org>
and subject line Re: [bug#78066] [PATCH v3 0/6] Fix fail2ban build
has caused the debbugs.gnu.org bug report #78066,
regarding [PATCH 0/2] Fix fail2ban build
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
78066: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78066
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Rodion Goritskov <rodion <at> goritskov.com>
To: guix-patches <at> gnu.org
Cc: Rodion Goritskov <rodion <at> goritskov.com>
Subject: [PATCH 0/2] Fix fail2ban build
Date: Fri, 25 Apr 2025 22:12:30 +0200

Hi!

Currently fail2ban is not building [1] because its test suite is not compatible with Python 3.11.
Quick fix is to use Python 3.10 there.

Probably I will find some time to update fail2ban package in the nearest future
(because it is quite old now, four years passed already).

However, I think it is good to have the current version building for now.

[1] - https://issues.guix.gnu.org/77996

Rodion Goritskov (2):
  gnu: python: Export wrap-python3.
  gnu: fail2ban: Build with Python 3.10.

 gnu/packages/admin.scm  | 3 ++-
 gnu/packages/python.scm | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

-- 
2.49.0

[Message part 3 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: Nicolas Graves <ngraves <at> ngraves.fr>
Cc: 78066-done <at> debbugs.gnu.org
Subject: Re: [bug#78066] [PATCH v3 0/6] Fix fail2ban build
Date: Tue, 06 May 2025 12:29:08 +0200

Nicolas Graves <ngraves <at> ngraves.fr> writes:

> I think the fail2ban tests were broken before the Python <at> 3.10 update.
> The -basic test runs properly, but the other tests do not.
>
> I focussed on fixing the -basic test because I don't understand why
> the other tests fail (socket is not found, but when I try it in real
> conditions, it is).
>
> The main issue was that the paths-debian.conf in jail.conf was
> substituted after the wheel was built, so the change didn't make it in
> the output.  Probably related to the migration to the
> pyproject-build-system.
>
> So now the -basic test passes, but the -simple and -extension tests
> don't, but I guess it's because tests rather than the package are
> broken.  Ready to be merged IMHO.
>
> Nicolas Graves (6):
>   gnu: fail2ban: Move file deletion to source snippet.
>   gnu: fail2ban: Move setup and test patches to phases.
>   gnu: fail2ban: Update to 1.1.0.
>   gnu: fail2ban: Improve style.
>   gnu: fail2ban: Improve style.
>   gnu: fail2ban: Improve snippet.

Applied, thanks!

Ludo'.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.