Arch Linux User Repository

(EDIT: Updated to a newer commit that fixes the submodule repo address.)

Yeah, upstream literally just switched that git submodule to a new repo but they haven't yet released a new ZoneMinder version, so building is currently broken for anyone trying to build from source.

I would like to keep this PKGBUILD clean and not change the way it works just for a temporary fix (I'd need to convert it to a zoneminder-git type of package), so for the time being and until a new upstream version is released, please replace

source=("${pkgname}-git::git+https://github.com/ZoneMinder/zoneminder.git#tag=${pkgver}"
        ...

with

source=("${pkgname}-git::git+https://github.com/ZoneMinder/zoneminder.git#commit=bbc2c2a607c49f70847b5d1611d297013d5f8e30"
        ...

which will allow you to build ZoneMinder with the new submodule repo included.

It fails with:

fatal: repository 'https://github.com/ZoneMinder/crud.git/' not found

/home/xyz/.cache/yay/zoneminder/src/zoneminder/src/jwt-cpp/include/jwt-cpp/picojson.h:372:12: note: in definition of macro ‘GET’
  372 |     return var;                                                                                                                    \
      |            ^~~
[ 57%] Linking CXX static library libzm.a
[ 57%] Built target zm
make: *** [Makefile:171: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
error making: zoneminder

@rageltman perl-sys-mmap is already a dependency, so it's probably something else on your end that breaks the build (e.g a misconfigured PATH).

This needs the perl-sys-mmap aur package added to its dependency list, otherwise builds break with:

[2020-10-04T06:31:42.105Z] -- Checking for perl module Sys::Mmap
[2020-10-04T06:31:42.108Z] -- Checking for perl module Sys::Mmap - failed
[2020-10-04T06:31:42.110Z] -- Could NOT find PerlModules (missing: PERLMODULES_SYS_MMAP_MODULE) 
[2020-10-04T06:31:42.112Z] CMake Error at CMakeLists.txt:785 (message):
[2020-10-04T06:31:42.114Z]   Not all required perl modules were found on your system
[2020-10-04T06:31:42.117Z] 
[2020-10-04T06:31:42.117Z] 
[2020-10-04T06:31:42.117Z] -- Configuring incomplete, errors occurred!
[2020-10-04T06:31:42.119Z] See also "/build/zoneminder/src/zoneminder/CMakeFiles/CMakeOutput.log".
[2020-10-04T06:31:42.122Z] See also "/build/zoneminder/src/zoneminder/CMakeFiles/CMakeError.log".
[2020-10-04T06:31:42.124Z] ==> ERROR: A failure occurred in build().
[2020-10-04T06:31:42.127Z]     Aborting...

@zlqrn, php-fpm is a dependency of this package because the web interface runs on PHP, so yeah, it makes sense that it wouldn't work for you if you somehow managed to install it without php-fpm, or more probably failed to start php-fpm's service before running ZoneMinder. Now that I think about it, it'd be a good idea to modify the note printed after install and list the services that should be run before ZoneMinder for it to work properly.

Regarding the personalized username & password, ZoneMinder's upstream code unfortunately contains (or used to contain) some hardcoded stuff that really shouldn't be hardcoded (e.g. paths), so it wouldn't surprise me if the username/password for the database were hardcoded as well. But as far as I know, those can be configured by creating a conf file in /etc/zoneminder/conf.d/ (or by editing /etc/zoneminder/zm.conf directly, but it's discouraged) and assigning the variables ZM_DB_USER and ZM_DB_PASS. Unless you mean that you've already tried that and ZoneMinder failed to pick up the changes?

web interface just code? for those bigger noobs than me on a clean install web interface didnt work until i installed php-fpm some reason personalized username and passwd for zm and mariadb didnt work had to revert to defaults zmuser etc. also refer to mariadb guide for update folder structure for conf files. perhaps for mysql the official arch zonminder guide works, but not for mariadb (my.conf and my.conf.d) so far install seems great. web interface is working

Wait, you mean that without pod2man the build fails for you even when not using Docker? Alright, that's a weird one. In my case everything builds properly each and every time I test the package before uploading a new release, and I guess this holds true for the majority of the people using this package (otherwise the comments here would've been flooded with complaints). Even the upstream documentation mentions pod2man as a dependency only in the context of Docker, not as a hard dependency for a generic, non-Docker build.

It doesn't cost me anything to add it as a dependency, of course, but I'd like to understand this issue a bit better first. What's the exact error you've been getting? Is it the same as @superpupervlad's?

at least for me and superpupervlad the build fails without pod2man installed, that's why I think it should be a mandatory dependency. :)

@hillbicks it's already an optional dependency.