Comment # 9 on bug 4393 from
(In reply to Damian Wrobel from comment #8)
> Please find a few additional comments from an attempt to run version:
> 1.30.1-1 on a new F25:
> 
> 1) /usr/lib/systemd/system/zoneminder.service:14] Not an absolute path,
> ignoring: "/var/run/zoneminder/zm.pid"
> 
> The following change helped:
> 
> -PIDFile="/var/run/zoneminder/zm.pid"
> +PIDFile=/var/run/zoneminder/zm.pid
> 

Thank you. Change has been committed upstream:
https://github.com/ZoneMinder/ZoneMinder/commit/c594ad8be7943f2dac3b331116d827e82252ac9b

> 
> 2) Missing directory for pid file:
> Creating /var/run/zoneminer directory accessible for httpd daemon solved it.
> 

ZoneMinder uses tmpfiles.d to create the runtime folder. It should have
happened automatically during package installation. Perhaps the command to
force tmpfiles.d to update immediately w/o reboot went missing from %post. I
can look.

https://github.com/ZoneMinder/ZoneMinder/blob/master/distros/redhat/systemd/zoneminder.tmpfiles.in


> 
> 3) ERR ['zmtelemetry.pl' exited abnormally, exit status 9]
> 
> I had to install the following missing packages mentioned here[1] to make it
> working:
> perl-IO-Socket-SSL
> perl-Sys-CPU
> perl-Sys-MemInfo
> 
> [1] https://forums.zoneminder.com/viewtopic.php?t=24389#p93112

That forum thread was from an Ubuntu user so missing packages can be expected
when building against master, since the deb packaging process does not have the
auto-requires ability rpm does.

Is your entire build output available for viewing anywhere?
Can you try this on F24?

I can manually add these to Requires if I have to, but I think there is
something else going on here.

These Requires should be picked up automatically during the build process and
should look like this:
https://gist.github.com/knnniggett/4811c111a692f585d6b40a4e5f29e564

However, I've noticed that only on F25, my builds both locally and on copr are
not getting their requires & provides set properly. Don't know what the problem
is yet, but it does not seem to be isolated to zoneminder. Perhaps there is
some change in F25 that I am not yet aware of.


You are receiving this mail because: