| Summary: | security/wazuh-manager 4.6.0 fails port build | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Joel Rodriguez <joel> |
| Component: | Individual Port(s) | Assignee: | Jose Alonso Cardenas Marquez <acm> |
| Status: | Closed Overcome By Events | ||
| Severity: | Affects Some People | CC: | acm |
| Priority: | --- | Flags: | linimon:
maintainer-feedback?
(acm) |
| Version: | Latest | ||
| Hardware: | amd64 | ||
| OS: | Any | ||
|
Description
Joel Rodriguez
2023-12-13 00:53:59 UTC
Hi Joel, it seems like some things are broken in your system. wazuh-manager 4.6.0 build without problems on 12, 13, 14 and 15. Take a look at https://www.freshports.org/security/wazuh-manager I have updated wazuh to 4.7.0. You could try it in a fresh installation of FreeBSD. Remember 12 will not have support soon For the life of me I do not understand how you can claim there is a problem on my install without a shred of proof. There are over 1700 ports successfully built and installed on my system.
root@tahoestores:~/bin # pkg delete wazuh-manager-4.4.3
Updating database digests format: 100%
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):
Installed packages to be REMOVED:
wazuh-manager: 4.4.3
Number of packages to be removed: 1
The operation will free 438 MiB.
Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling wazuh-manager-4.4.3...
[1/1] Deleting files for wazuh-manager-4.4.3: 100%
==> You should manually remove the "wazuh" user.
==> You should manually remove the "wazuh" group
Problem solved.
and as a final reminder, the shared object libpython3.9.so is something your make has bundled in. The error is: ld: error: ./libpython3.9.so: undefined reference to SSL_get1_peer_certificate [--no-allow-shlib-undefined] root@tahoestores:/usr/ports/security/wazuh-manager # find . -name libpython3\.9\.so -print ./work/wazuh-4.7.0/src/external/cpython/libpython3.9.so If you compile all ports in your system the best is build your own packages using a clean environment. poudriere can be useful in your case. Thanks for your PR poudriere is a nice option if and only if I have multiple systems to maintain. I have but one PRODUCTION server and I have augmented building ports with a number of scripts. I have no need to build pkg(s), I use ports. I am also fully aware of the EOL for FreeBSD 12 and the reason I am pursuing the rather limited port failures I have is to prepare for the upgrade during the last week of the year. I will dump anything that doesn't work prior to the upgrade and it appears that this particular port is not making the cut. In the future it would be best if you addressed the cause of the linking error and refrain from giving your adhoc advise to others. This notion of a "clean" environment is absurd as python alone has at least 4 different versions and it is clear that many of the ports cannot and do not keep pace with this level of complexity. In the case of this port it is clear that the recent openssl-3 updates haven't been fully addressed as is evidenced by the linking error that only cropped up after openssl-3 was updated. There were over 900 ports impacted by the openssl-3 update and I am sorry to say, only two or three ports choked on the update. Obviously, this port was one of them. So thanks for nothing and the broken english. |