Package Details: zoneminder 1.36.33-1

Git Clone URL: https://aur.archlinux.org/zoneminder.git (read-only, click to copy)
Package Base: zoneminder
Description: A full-featured, open source, state-of-the-art video surveillance software system
Upstream URL: https://www.zoneminder.com/
Keywords: camera cctv monitor record security surveillance video zoneminder
Licenses: GPL2
Conflicts: zoneminder-git
Submitter: None
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 68
Popularity: 0.006274
First Submitted: 2008-03-21 00:09 (UTC)
Last Updated: 2023-02-24 08:27 (UTC)

Latest Comments

1 2 3 4 5 6 .. 58 Next › Last »

TeslaZap commented on 2023-03-12 10:21 (UTC)

downgrading ffmpeg works for the missing libs error and it is the recommended workaround.

for those who have many packages depending on the new version of ffmpeg and don't want to downgrade them all, they can extract the 4 missing libs from the previous ffmpeg package version, put them in /usr/local/lib and symlink them. it's not recommended and it must be manually cleaned up once zoneminder package is properly updated.

my affected libs were: libavcodec.so.59 libavformat.so.59 libavutil.so.57 libswscale.so.6 they can be found in /var/cache/pacman/pkg/ffmpeg-2:5.1.2-2-x86_64.pkg.tar.zst

tropicalgrating commented on 2023-03-11 20:38 (UTC)

Hello, just for anyone doing a full system update. FFMPEG gets updated to 6.0.3 and will break the zmc video portion. When you update and then try to view your cameras they all come up with nothing and the log files gives a 127 error. When you try to open the cameras in the terminal like zmc -m# it throws an error in relation to libavformat.so.59 does not exist. Searching the system it looks like libavformat gets updated to 60 and zoneminder has no clue how to use this file. I downgraded back to ffmpeg 5.1.2 and this fixed the issue temporarily. Hope this helps

Nocifer commented on 2023-01-13 08:23 (UTC)

@synthead Do you really think that's necessary? It builds and runs fine in non-Docker environments, and pod2man is already an optional dependency for anyone who may need it for Docker, so adding it as a hard dependency would mean that most users would be installing a package they do not need.

synthead commented on 2023-01-13 02:17 (UTC)

@Nocifer, should pod2man be added as a dependency if this package doesn't build without it?

Nocifer commented on 2022-11-02 19:04 (UTC)

If you're talking about the three configuration files that come with the package itself (/etc/zoneminder/zm.conf, /etc/zoneminder/conf.d/01-system-paths.conf, /etc/zoneminder/conf.d/02-multiserver.conf) you're not supposed to edit them directly, you should create new files in conf.d and put whatever settings you may need in there.

rossome commented on 2022-11-02 16:57 (UTC)

any particular reason this package overwrites all the config files in /etc/zoneminder on each update?

Nocifer commented on 2022-09-07 12:39 (UTC)

Your log is full of errors. First of all this one here in the checking step:

FATALERRORNeed pod2man installed to generate man page

Then when the build begins, you have these:

[  0%] Building CXX object dep/RtspServer/CMakeFiles/RtspServer.dir/src/net/Acceptor.cpp.o
[  1%] Generating zmc.8
/bin/sh: linha 1: POD2MAN-NOTFOUND: comando não encontrado
[  2%] Building C object dep/libbcrypt/CMakeFiles/bcrypt.dir/src/bcrypt.c.o
make[2]: *** [src/CMakeFiles/man-zmc.dir/build.make:77: src/zmc.8] Erro 127
make[2]: ** Apagando arquivo 'src/zmc.8'
make[1]: *** [CMakeFiles/Makefile2:594: src/CMakeFiles/man-zmc.dir/all] Erro 2

I'm not entirely familiar with pod2man, but I do know that it is required when building Zoneminder to be deployed as a docker image/container. These errors lead me to believe that BigLinux tries to build Zoneminder in some weird way that resembles a docker-ish environment, and that's why it fails, so a potential solution to your problem would be to install pod2man.

Creto commented on 2022-09-06 12:36 (UTC)

@Nocifer here is complete log of today's installation attempt:

See https://pastebin.com/VyMk4y3V

T+ = See you later

Nocifer commented on 2022-09-06 07:46 (UTC)

No, detect-old-perl-modules.hook is just a system utility that checks for issues with Perl modules, which according to your log there weren't any to find. But this libalpm log (which I assume is Big-Store's output) isn't what I meant anyway; what I meant was the first part of the build log that you posted in your first comment:

==> Making package: zoneminder 1.36.25-1 (Tue 06 Sep 2022 07:36:03 AM UTC)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
-- The C compiler identification is GNU 12.1.1
-- The CXX compiler identification is GNU 12.1.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
...

^This is from my successful attempt at building Zoneminder on Manjaro just now, by the way, so it's almost certain that your issue is an incompatibility on BigLinux's side of things.

(AFAIU = As Far As I Understand = I assume; no worries about the language, that's why we have Google Translate in the first place ;) )

1 2 3 4 5 6 .. 58 Next › Last »