Fix fail2ban
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | package/fail2ban: fix data_files installation pathpackage/ | +73 | 0 replies | |
| 2/2 | package/pkg-python: fix pep517 data files installationpackage/ | +2 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [PATCH 0/2] Fix fail2ban
From: Angelo Compagnucci <[email protected]>
This series fixes fail2ban not installing configuration files in /etc anymore. While fixing the problem, I discovered a bug in the way we invoke the pyinstaller.py in pep517 compatibility.
Basically, pyinstaller.py will install data_files defined in setup.py and tarballed in the wheel inside the directory pointed by the --data parameter, which is nowadays pointing to /usr of TARGET/STAGING directory.
I consider this wrong, because the data folder shall point to the TARGET_DIR/STAGING_DIR to be correct and we shall trust the destination path expressed in the setup.py.
In the case of fail2ban, configuration files end up being installed in /usr/etc/fail2ban instead of /etc/fail2ban.
Angelo Compagnucci (2):
package/fail2ban: fix data_files installation path package/pkg-python: fix pep517 data files installation
...001-setup.py-fix-data-relative-paths.patch | 73 +++++++++++++++++++ package/pkg-python.mk | 4 +- 2 files changed, 75 insertions(+), 2 deletions(-) create mode 100644 package/fail2ban/0001-setup.py-fix-data-relative-paths.patch
Signature · 6 lines
2.34.1 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot