From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Asaf Kahlon <asafka7@gmail.com>,
Fiona Klute via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2 3/4] package/fail2ban: bump version to 1.1.0
Date: Tue, 9 Jul 2024 13:55:38 +0200 [thread overview]
Message-ID: <20240709135538.4594978e@windsurf> (raw)
In-Reply-To: <1e0c66a5-b6d3-4117-aafb-68b4d00a5565@gmx.de>
Hello Fiona,
On Tue, 9 Jul 2024 12:19:49 +0200
Fiona Klute <fiona.klute@gmx.de> wrote:
> >> -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?
>
> I saw a build failure because host Python hadn't been built before
> without it. I now suspect that was the result of adding a runtime-only
> dependency to build-time dependencies (see below), I guess it broke some
> implicit dependency handling? After completely removing that line the
> build passes, too.
Adding a runtime dependency to build-time dependencies cannot break
dependency handling. It just enforces a "strong" dependency that
doesn't exist, but it clearly cannot be responsible for a build
failure. So it looks like we haven't figured out why the build was at
some point failing for you.
A good practice when testing a package:
$ make clean
$ ./utils/docker-run make fail2ban
This will only build fail2ban and its build dependencies, and nothing
else. This will therefore make sure that you properly captured all
dependencies. And it does so in a minimal docker container, to ensure
no tools from your host machine are used.
> > 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.
>
> That's indeed a runtime dependency.
>
> Thanks for the review! I've just sent an updated version of the series
> with the runtime comment added and the build time dependency removed. If
> it's good to merge now, please keep in mind that it's only going to fix
> the fail2ban build if merged after Angelo's fixes to the config file
> handling (linked in the cover letter).
ACK, 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-09 11:55 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
2024-07-09 10:19 ` Fiona Klute via buildroot
2024-07-09 11:55 ` Thomas Petazzoni via buildroot [this message]
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=20240709135538.4594978e@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