Package Details: zoneminder 1.36.33-2

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: GPL-2.0-only
Conflicts: zoneminder-git
Submitter: None
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 70
Popularity: 0.31
First Submitted: 2008-03-21 00:09 (UTC)
Last Updated: 2024-02-12 12:50 (UTC)

Dependencies (46)

Sources (8)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 60 Next › Last »

void09 commented on 2022-06-22 19:51 (UTC)

Any idea why once in a while I have to 'sudo systemctl restart fcgiwrap-multiwatch' to get steaming to work again in zmninja ? It gets stuck about once a day or so.

sav commented on 2022-06-13 07:34 (UTC)

Reinstalled the packages with AUR, everything worked. I'm sorry to bother you.

sav commented on 2022-06-12 13:59 (UTC)

[andrey@Server ~]$ systemctl status zoneminder.service × zoneminder.service - ZoneMinder CCTV recording and security system Loaded: loaded (/usr/lib/systemd/system/zoneminder.service; enabled; vendo> Active: failed (Result: exit-code) since Sun 2022-06-12 16:55:12 MSK; 11s > Process: 86464 ExecStart=/usr/bin/zmpkg.pl start (code=exited, status=2) CPU: 121ms [andrey@Server ~]$ journalctl -xeu zoneminder.service Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages. Pass -q to turn off this notice.

Nocifer commented on 2022-06-10 18:31 (UTC)

@sav How exactly does it not work? What kind of error does it give you?

sav commented on 2022-06-10 18:08 (UTC)

Unfortunately, version 19.1 doesn't work for me

synthead commented on 2022-05-24 10:08 (UTC)

It looks like all the ffmpeg 5 issues have been closed :)

https://github.com/ZoneMinder/zoneminder/issues?q=is%3Aissue+is%3Aopen+ffmpeg+5

They haven't cut a new release yet, but keep a lookout for this to be fixed soon!

DaMadOne commented on 2022-05-04 05:25 (UTC)

as my ZM runs in its own VM I just used the pacman chache and downgraded ffmpeg and x264 to previous known working versions and ZM compiled and is running just fine. The price we pay living on the edge. It'll probably be fine when I get around to updating this VM again in 6 months.

Nocifer commented on 2022-04-22 07:40 (UTC)

Well, personally I wouldn't really call a single package (that is also very probably already present on a system) "unnecessary build dependencies", just as I wouldn't call removing a single line from the PKGBUILD "making it simpler", but to each their own. Also, git already checksums its stuff more than adequately.

The only valid concern IMHO is the increased network and disk usage, and to that I'd be inclined to reply that downloading an extra ~100MB the first time the package is downloaded is hardly a burden on either network or storage, while on the other hand git allows for cherry-picking commits, which at one time (when ZoneMinder was being developed more actively) was a very useful feature to have, and it could become so again if ZM's devs decide to pick up the pace.

Anyway, I've been thinking about doing some other minor changes to the PKGBUILD sometime Soon™, so when that time comes I'll consider this as a possible change.

synthead commented on 2022-04-14 16:53 (UTC)

As to the second question, what unnecessary build dependencies could be removed if we switched to release tarballs?

Everything related to git. In addition, less network and disk size would be used, the PKGBUILD would be simpler, and we can checksum the downloaded archive.

Nocifer commented on 2022-04-09 09:53 (UTC)

@Synthead It's an incompatibility with Ffmpeg 5 due to the latter having removed some deprecated stuff like the very often used AVPicture, which breaks a large number of apps that rely on it, ZoneMinder among them. I've already reported the issue on Github and the developers are aware about it and acknowledge the incompatibility as something that needs to be fixed on their side. So, we need to wait for that fix.

As to the second question, what unnecessary build dependencies could be removed if we switched to release tarballs?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 60 Next › Last »