Arch Linux User Repository

Thank you @Nocifer. I got it installed on blendOS.

Needed:
system disk > 40GB.
RAM: 8GB (or 4GB + >1GB swapfile) (the swapfile shouldn't be needed but I had 3 instances where RAM got exhausted and my system effectively froze but I could not reproduce this behavior).

My system.yaml ended up being surprisingly simple:

arch-repo: https://geo.mirror.pkgbuild.com
impl: https://github.com/blend-os/tracks/raw/main
repo: https://pkg-repo.blendos.co

track: default-gnome

packages:
- 'fcgiwrap'
- 'spawn-fcgi'
- 'nginx'
- 'mariadb' # required for zoneminder

aur-packages:
- 'multiwatch' # https://aur.archlinux.org/packages/multiwatch
- 'zmeventnotification' # https://aur.archlinux.org/packages/zmeventnotification
- 'zoneminder' #success https://aur.archlinux.org/packages/zoneminder

services:
- 'fcgiwrap-multiwatch.service'

Now it's all installed... Now what do I do? :) I'll repost any answers I found.

@boogschutter It's not that the files are missing, it's just that they've been updated by their creator and their hashes have changed, which means the PKGBUILD also needs to be updated with the new hashes.

The way their creator pushes new updates for the files (AFAIK they simply overwrite the old ones with the new ones) means that I can't easily/automatically synchronize the PKGBUILD with those changes, so occasionally things break. But it's not a major issue really, next time simply report the package as out-of-date and I'll get right on it.

I'm trying to install zoneminder on blendOS Immutable Arch Linux through the /system.yaml file.

I think Deimos666 is right when he says yolov3 is missing. Quote:
==> Validating source files with sha256sums...
a306ad2dbe87c5ace3d0ba89d9d4235fd489424b.zip ... Passed
coco.names ... Passed
yolov3.cfg ... Passed
yolov3.weights ... FAILED
yolov3-tiny.cfg ... Passed
yolov3-tiny.weights ... FAILED
yolov4.cfg ... Passed
yolov4.weights ... Passed
yolov4-tiny.cfg ... Passed
yolov4-tiny.weights ... Passed
coco_labels.txt ... Passed
ssd_mobilenet_v2_coco_quant_postprocess_edgetpu.tflite ... Passed
ssd_mobilenet_v2_face_quant_postprocess_edgetpu.tflite ... Passed
ssdlite_mobiledet_coco_qat_postprocess_edgetpu.tflite ... Passed
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'zmeventnotification-6.1.29.ga306ad2-3':

Now what do we do? The links given by Deimos666 in August last year do work again and the files can be downloaded. But how to tell my system.yaml this...? I'll have to start asking around I suppose? :)

The sources file: https://pjreddie.com/media/files/yolov3-tiny.weights https://pjreddie.com/media/files/yolov3.weights

Are not anymore avalaible

If possible, please remove the dependency on python-furure/ make the package working without python-future:

WARNING: python-future package is not compatible with Python 3.13

The python-future project was created in 2013 to attempt to save Python from the schism of version incompatibility that was threatening to tear apart the language (as Perl 6 contributed to the death of Perl).

That time is now past. Thanks to a huge porting effort across the Python community, Python 3 eventually thrived. Python 2 reached its end of life in 2020 and the python-future package should no longer be necessary. Use it to help with porting legacy code to Python 3 but don’t depend on it for new code.

If you use packages that depend on it, please contact maintainers and/or upstream of these packages and try to work out whether this dependency is really needed.

Regards and thanks for this package!

In order to implement with a Coral Edge TPU and the default (after enabling EdgeTPU) objectdetect.ini, I also needed the following weights files:

        'https://github.com/google-coral/edgetpu/raw/master/test_data/ssd_mobilenet_v2_face_quant_postprocess_edgetpu.tflite'
        'https://github.com/google-coral/test_data/raw/master/ssdlite_mobiledet_coco_qat_postprocess_edgetpu.tflite'

@happyrogue

Regarding [2], most of these sound weird to me as well, but they have been previously reported as needed by two separate commenters (see below), so unless someone tests and confirms they're not needed I'll have to keep them in. The exceptions are face_recognition and scikit-learn (which could be remnants of a pre-6.0.0 version) but again, I'd need someone who actively uses zmeventnotification (I don't anymore) to test for this and verify they are OK to remove.

Regarding [3], since it's listed in setup.py, that's also something for upstream to correct if needed.

Regarding [4], it's not listed because as you said it's already being pulled in by shapely, so there's no need to list it here as well.

The dependencies seem a bit outdated, so I went through them.

Perl dependencies:

TODO (by someone else)

Python dependencies:

opencv
Imported by hook/{zm_detect.py,zmes_hook_helpers/image_manip.py}

python-future[1]
Imported by hook/zmes_hook_helpers/utils.py

[1]: Should probably be dropped, but that's something for upstream.

python-gifsicle
Imported by hook/zmes_hook_helpers/image_manip.py

python-imageio
Imported by hook/zmes_hook_helpers/image_manip.py

python-imutils
Imported by hook/zm_detect.py

python-pyzm-git
Imported by hook/{train_faces.py,zm_detect.py,zm_train_faces.py,zmes_hook_helpers/apigw.py,zmes_hook_helpers/log.py} pushapi_plugins/pushapi_pushover.py

python-requests
Imported by hook/{zm_detect.py,zmes_hook_helpers/image_manip.py} pushapi_plugins/pushapi_pushover.py

python-shapely
Imported by hook/zmes_hook_helpers/image_manip.py

python-face_recognition[2]
python-imageio-ffmpeg[3]
python-mysql-connector[2]
python-psutil[2]
python-scikit-learn[2]
python-sqlalchemy[2]
qt5-base[2]

[2]: No references found.
[3]: Not referenced outside of hook/setup.py?

python-numpy[4]
Imported by hook/{zm_detect.py,zmes_hook_helpers/image_manip.py}

[4]: Listed as a dependency of python-shapely but not this package directly. Could someone clarify for me if it should be added?

Of note, the "no references" packages may still be required by pyzm. But that's an issue for a different package maintainer.

@lainpants @ultimategrandson Actually both of you correct; the two files were indeed updated and thus needed to have their sha256 sums updated (which was done in the 6.1.6 release) but you also may have to clear your cache (or at least find and delete those two yolov4 specific files) in order for e.g. yay to redownload them instead of trying to use the out-of-date existing files and failing. That's the case for most all packages that use unversioned binary files as their sources.

@lainpants

I got the same issue but after clearing the package cache (in my case yay -Scc), it worked fine.