search

chrisss404 / check-mk-arm

Checkmk for Raspberry Pi.
182 stars 23 forks source link

Dependency resolution issue with 2.2.0p11 #62

Closed chrisss404 closed 7 months ago

chrisss404 commented 10 months ago

Hi all,

recently I am running into dependency resolution issues when trying to build checkmk 2.2.0p11:

Locking Failed!
  Locking...
ERROR:pip.subprocessor:[present-rich] Getting requirements to build wheel exited with 1
[ResolutionFailure]:   File "/usr/local/lib/python3.11/site-packages/pipenv/resolver.py", line 811, in _main
[ResolutionFailure]:       resolve_packages(
...
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved.

See full build log: build.log

I have no idea what is causing this, any hint is welcome.

Thx in advance & BR

martux69 commented 8 months ago

We are now at 2.2.0p16 , I think, this issue can be closed. If the problem still exists in the new version, feel free to create a new ticket :-)

chrisss404 commented 8 months ago

If the problem still exists in the new version, feel free to create a new ticket :-)

Unfortunately, it does. It seems like it's no longer possible to build 32bit arm packages of recent checkmk versions.

martux69 commented 8 months ago

That's a pity :-( If I understand it aright from the build log, the failure is caused by compiling openssl-1.1.1u with bazel. Perhaps it could be a solution to use the openssl from the repos of the raspi os? Perhaps also the bazel version could be a problem (it is very old)?

chrisss404 commented 7 months ago

Thx, for taking a look.

Perhaps it could be a solution to use the openssl from the repos of the raspi os?

I am not sure how to do that.

Perhaps also the bazel version could be a problem (it is very old)?

Yes, the bazel version is very old because bazel also has no official 32bit arm support, see subsequent project: https://github.com/koenvervloesem/bazel-on-arm

Maybe it's time to move to 64-bit and leave 32-bit behind.