zabbix-server: add version 7#18345
Conversation
|
It is also the Postgres timescaldb extension necessary. |
|
I assume the build uses the generic (mediated) library at /usr/lib/amd64/libpq.so.5 and so it adds all PostgreSQL versions that could possibly satisfy that (so basically all) to You should make sure that one specific PostgreSQL version is used using macros from the |
|
Your are right. The problem is this library path list |
cgrzemba
force-pushed
the
zabbix-7
branch
4 times, most recently
from
904ab73 to
b2f530f
Compare
|
I have run gmake sample-manifest here: You'll need to manually add the build dependency on |
cgrzemba
force-pushed
the
zabbix-7
branch
2 times, most recently
from
f332680 to
c9f2bb6
Compare
|
This change added the @cgrzemba, could you please fix this issue? Thank you. PS: The issue was detected by oi-pkg-checker. |
|
Am 14.08.24 um 08:06 schrieb Marcel Telka:
This change added the |application/management/zabbix-agent| package,
but the same package is already provided by the network/zabbix-agent
<https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/network/zabbix-agent>
component. This is obviously wrong because we cannot deliver single
package from two components.
@cgrzemba <https://github.com/cgrzemba>, could you please fix this issue?
Thank you.
PS: The issue was detected by oi-pkg-checker
<https://github.com/aueam/oi-pkg-checker>.
Have you considered to create a package for oi-pkg-checker?
|
Yes. This is my long term plan, once the project is a bit more polished. |
|
Am 14.08.24 um 08:06 schrieb Marcel Telka:
This change added the |application/management/zabbix-agent| package,
but the same package is already provided by the network/zabbix-agent
<https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/network/zabbix-agent>
component. This is obviously wrong because we cannot deliver single
package from two components.
@cgrzemba <https://github.com/cgrzemba>, could you please fix this issue?
Thank you.
PS: The issue was detected by oi-pkg-checker
<https://github.com/aueam/oi-pkg-checker>.
—
Reply to this email directly, view it on GitHub
<#18345 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADET4N7G3KKMPGSDQDXMAYLZRLXXXAVCNFSM6AAAAABL2SLQI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBXHEZDOMBZGA>.
You are receiving this because you modified the open/close
state.Message ID:
***@***.***>
I think we should split this single zabbix folder into at least two (and
maybe three) separate folders because zabbix-server has a lot more
dependencies (eg. postgressql) than zabbix-agent.
I am not sure about the dependencies of zabbix-proxy, though. It may
share its dependencies with one of the others and could be put together
with that then.
If we don't split the packages an installation that only needs
zabbix-agent will also have to install the heavy dependencies of
zabbix-server which is most probably not wanted.
|
The component's build dependencies and the runtime package dependencies are very loosely related. The amount of build dependencies is not a problem in a case when the actual packages are designed properly. This seems to be the case here, maybe with one exception: I noticed that Anyway, back to the main topic: Since both Also some minor tweaks in the vs.
Packages are already split: The |
|
Am 15.08.24 um 12:35 schrieb Marcel Telka:
I think we should split this single zabbix folder into at least
two (and maybe three) separate folders because zabbix-server has a
lot more dependencies (eg. postgressql) than zabbix-agent.
The component's /build/ dependencies and the /runtime/ package
dependencies are very loosely related. The amount of /build/
dependencies is not a problem in a case when the actual packages are
designed properly. This seems to be the case here, maybe with one
exception:
I noticed that |zabbix_get| got moved from the ***@***.***|
package to the ***@***.***| package. I'm not sure where it
really belongs (I know nothing about Zabbix), but from the
|zabbix_get(1)| man page I'd say it should stay in |zabbix-agent|.
Anyway, back to the main topic:
Since both |network/zabbix| and |network/zabbix-agent| components are
compiled from the same source tarball -
|zabbix-$(COMPONENT_VERSION).tar.gz| - the proper solution in this
case seems to be simple |git rm -r components/network/zabbix-agent|.
Also some minor tweaks in the |components/network/zabbix| directory
are needed, so it does not say the |zabbix-agent| is the server
(please note *Summary*):
|$ pkg info
***@***.***:20240813T203127Z
Name: application/management/zabbix-agent Summary: Zabbix server
Category: Applications/System Utilities State: Installed Publisher:
openindiana.org Version: 7.0.1 Branch: 2024.0.0.0 Packaging Date:
August 13, 2024 at 08:31:27 PM Last Install Time: February 20, 2024 at
01:15:28 AM Last Update Time: August 13, 2024 at 11:54:47 PM Size:
1.33 MB FMRI:
***@***.***:20240813T203127Z
Project URL: http://www.zabbix.com/ Source URL:
https://cdn.zabbix.com/zabbix/sources/stable/7.0/zabbix-7.0.1.tar.gz $ |
vs.
|$ pkg info -r
***@***.***:20230227T190250Z
Name: application/management/zabbix-agent Summary: Zabbix agent
Category: Applications/System Utilities State: Not installed
Publisher: openindiana.org Version: 6.2.7 Branch: 2023.0.0.0 Packaging
Date: February 27, 2023 at 07:02:50 PM Size: 1.25 MB FMRI:
***@***.***:20230227T190250Z
Project URL: http://www.zabbix.com/ Source URL:
https://cdn.zabbix.com/zabbix/sources/stable/6.2/zabbix-6.2.7.tar.gz $ |
I am not sure about the dependencies of zabbix-proxy, though. It
may share its dependencies with one of the others and could be put
together with that then. If we don't split the packages an
installation that only needs zabbix-agent will also have to
install the heavy dependencies of zabbix-server which is most
probably not wanted.
Packages are already split:
|$ jq -r '.fmris' components/network/zabbix/pkg5 [
"application/management/zabbix-agent",
"application/management/zabbix-proxy",
"application/management/zabbix-server" ] $ |
The
***@***.***:20240813T203127Z|
package does not require the |application/management/zabbix-server|
package and so you can easily install |zabbix-agent| without
|zabbix-server|.
—
Reply to this email directly, view it on GitHub
<#18345 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADET4NZ3FY5YTZG7PMU5FWLZRR76DAVCNFSM6AAAAABL2SLQI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJRGA2DINZSHE>.
You are receiving this because you modified the open/close
state.Message ID:
***@***.***>
Ok, I was wrong regarding the zabbix-agent dependencies. The package
doesn't inherit the same dependencies that are stated in pkg5.
I misattributed the dependencies metadata in the pkg5 file. In fact it
describes the build dependencies only, not the runtime dependencies.
I don't know if anybody is using this data, though. We also lack
documentation for it as far as I can see.
|
Yes, exactly. The AFAIK, nobody is currently actively using neither BTW, the issue with ICU mentioned here is already solved. I believe that the need for the mass rebuild of components (because of some other component changed) is wrong by design. Especially for rolling releases like OI Hipster. But I'm afraid I went too off topic here, so I should stop :-). |
3 participants
This PR provides the Zabbix server,proxy and agent component in version 7. It provides the support for Postgresql only.
There is an issue with the Postresql library dependency. If I let the buildsystem do all automatically it adds all Postresql versions to the REQUIRED_PACKAGES.
If I add
<transform file path=usr/sbin/zabbix_server -> add pkg.depend.bypass-generate (.)lib(.)/libpq.so.*>
then 'gmake REQUIRED_PACKAGES' removes the Postgresql library dependency at all.
What is the correct way here?