From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@buildroot.org
Cc: Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Angelo Compagnucci <angelo@amarulasolutions.com>
Subject: [Buildroot] [PATCH 1/2] package/fail2ban: fix data_files installation path
Date: Fri, 19 Apr 2024 23:18:32 +0200 [thread overview]
Message-ID: <20240419211833.498273-2-angelo.compagnucci@gmail.com> (raw)
In-Reply-To: <20240419211833.498273-1-angelo.compagnucci@gmail.com>
From: Angelo Compagnucci <angelo@amarulasolutions.com>
When packaging data_files in a wheel, those files shall have the destination
path expressed as relative to the wheel installation.
The reason for that is the wheel installation shall be contained inside a
specific folder and/or in site-packages.
When building the wheel file by the bdist_wheel command, python will package
files with absolute pats as python files ending up installing them in
site-packages.
Fixes:
http://autobuild.buildroot.net/results/36ac5278d19195a21c3d02d087965e08f49228ef
Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
---
...001-setup.py-fix-data-relative-paths.patch | 73 +++++++++++++++++++
1 file changed, 73 insertions(+)
create mode 100644 package/fail2ban/0001-setup.py-fix-data-relative-paths.patch
diff --git a/package/fail2ban/0001-setup.py-fix-data-relative-paths.patch b/package/fail2ban/0001-setup.py-fix-data-relative-paths.patch
new file mode 100644
index 0000000000..e1b5bc490b
--- /dev/null
+++ b/package/fail2ban/0001-setup.py-fix-data-relative-paths.patch
@@ -0,0 +1,73 @@
+From 7b7fa3c02d4575c09362336bc310835c37859f1a Mon Sep 17 00:00:00 2001
+From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
+Date: Fri, 19 Apr 2024 22:47:20 +0200
+Subject: [PATCH] setup.py: fix data relative paths
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+As per distutils documentation:
+
+The directory should be a relative path. It is interpreted relative to the
+installation prefix (Python’s sys.prefix for system installations;
+site.USER_BASE for user installations). Distutils allows directory to be an
+absolute installation path, but this is discouraged since it is incompatible
+with the wheel packaging format [1].
+
+When packaging to a bdist_wheel indeed, the files in the "data_files" dictionary
+are not picked at all as data files if they have an absolute path,
+but they are instead added to the wheel as python files.
+This has the effect of installing them as part of python files in the
+site-packages folder when the wheel is installed.
+
+This patch cannot be sent upstream because it breaks the legacy way of
+installing the package with *python setup.py install* and it is needed only to
+comply with the pep517 buildroot compatibility layer.
+
+[1] https://docs.python.org/3.10/distutils/setupscript.html#installing-additional-files
+Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
+---
+ setup.py | 14 +++++++-------
+ 1 file changed, 7 insertions(+), 7 deletions(-)
+
+diff --git a/setup.py b/setup.py
+index 91f71cf2..99ba2e32 100755
+--- a/setup.py
++++ b/setup.py
+@@ -238,26 +238,26 @@ setup(
+ for f in w[2]]
+ } if with_tests else {},
+ data_files = [
+- ('/etc/fail2ban',
++ ('etc/fail2ban',
+ glob("config/*.conf")
+ ),
+- ('/etc/fail2ban/filter.d',
++ ('etc/fail2ban/filter.d',
+ glob("config/filter.d/*.conf")
+ ),
+- ('/etc/fail2ban/filter.d/ignorecommands',
++ ('etc/fail2ban/filter.d/ignorecommands',
+ [p for p in glob("config/filter.d/ignorecommands/*") if isfile(p)]
+ ),
+- ('/etc/fail2ban/action.d',
++ ('etc/fail2ban/action.d',
+ glob("config/action.d/*.conf") +
+ glob("config/action.d/*.py")
+ ),
+- ('/etc/fail2ban/fail2ban.d',
++ ('etc/fail2ban/fail2ban.d',
+ ''
+ ),
+- ('/etc/fail2ban/jail.d',
++ ('etc/fail2ban/jail.d',
+ ''
+ ),
+- ('/var/lib/fail2ban',
++ ('var/lib/fail2ban',
+ ''
+ ),
+ ] + data_files_extra,
+--
+2.34.1
+
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-19 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 21:18 [Buildroot] [PATCH 0/2] Fix fail2ban Angelo Compagnucci
2024-04-19 21:18 ` Angelo Compagnucci [this message]
2024-04-19 21:18 ` [Buildroot] [PATCH 2/2] package/pkg-python: fix pep517 data files installation Angelo Compagnucci
-- strict thread matches above, loose matches on Subject: below --
2024-04-19 21:27 [Buildroot] [PATCH 0/2] Fix fail2ban Angelo Compagnucci
2024-04-19 21:27 ` [Buildroot] [PATCH 1/2] package/fail2ban: fix data_files installation path Angelo Compagnucci
2024-04-19 21:32 [Buildroot] [PATCH 0/2] Fix fail2ban Angelo Compagnucci
2024-04-19 21:32 ` [Buildroot] [PATCH 1/2] package/fail2ban: fix data_files installation path Angelo Compagnucci
2024-06-11 14:14 ` Fiona Klute via buildroot
2024-07-09 20:28 ` Thomas Petazzoni via buildroot
2024-07-09 20:54 ` 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=20240419211833.498273-2-angelo.compagnucci@gmail.com \
--to=angelo.compagnucci@gmail.com \
--cc=angelo@amarulasolutions.com \
--cc=buildroot@buildroot.org \
--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