Search Criteria
Package Details: zoneminder 1.36.33-2
Package Actions
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: | 72 |
Popularity: | 1.48 |
First Submitted: | 2008-03-21 00:09 (UTC) |
Last Updated: | 2024-02-12 12:50 (UTC) |
Dependencies (46)
- ffmpeg (ffmpeg-intel-full-gitAUR, ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-cudaAUR, ffmpeg-ffplayoutAUR, ffmpeg-decklinkAUR, ffmpeg-fullAUR, ffmpeg-gitAUR, ffmpeg-amd-fullAUR, ffmpeg-obsAUR, ffmpeg-libfdk_aacAUR, ffmpeg-headlessAUR, ffmpeg-amd-full-gitAUR, ffmpeg-full-gitAUR)
- libjwtAUR
- perl-archive-zip
- perl-crypt-eksblowfishAUR
- perl-data-dump
- perl-data-entropyAUR
- perl-data-uuid
- perl-date-manip
- perl-datetime
- perl-dbd-mysql
- perl-device-serialport
- perl-file-slurp
- perl-image-info
- perl-io-interfaceAUR
- perl-io-socket-multicastAUR
- perl-json-maybexs
- perl-libwww
- perl-lwp-protocol-https
- perl-mime-lite
- perl-mime-tools
- Show 26 more dependencies...
Required by (1)
Sources (8)
- fcgiwrap-multiwatch.service
- https://github.com/FriendsOfCake/crud/archive/refs/tags/v3.2.0.tar.gz
- https://github.com/ZoneMinder/CakePHP-Enum-Behavior/archive/refs/tags/1.0-zm.tar.gz
- https://github.com/ZoneMinder/RtspServer/archive/055d81fe1293429e496b19104a9ed3360755a440.zip
- https://github.com/ZoneMinder/zoneminder/archive/refs/tags/1.36.33.tar.gz
- zoneminder-httpd.conf
- zoneminder-nginx.conf
- zoneminder-php.ini
Latest Comments
« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 62 Next › Last »
Mike616 commented on 2021-03-26 06:40 (UTC) (edited on 2021-03-26 06:52 (UTC) by Mike616)
Okay it looks like zoneminder doesn't yet support the latest release of
libx264
. Downgradingffmpeg
,libx265
, andlibx264
to the previous versions solved the problem for me.Here's how I did this:
Find the previous versions of all three packages:
If you haven't cleared your pacman cache, you can install the previous cached versions. You'll have to do all three packages at the same time since they are dependent on each other:
You can tell pacman to ignore updates for these packages for the time being by adding the following to the
options
section of/etc/pacman.conf
:After doing this, all my cameras came back to life. Yay because I'm going on vacation tomorrow.
Mike616 commented on 2021-03-26 06:17 (UTC) (edited on 2021-03-26 06:17 (UTC) by Mike616)
@alanking I just ran
pacman -Suy
and rebooted and now I'm having the same problem. All cameras are red. I can open the web console but cannot stream anything.Trying to run
zmc
orzma
directly produces:alanking commented on 2021-03-25 13:40 (UTC)
did this break for anyone else a couple of days ago. all my cameras are red and no longer working. Console still works fine.
ubone commented on 2021-03-16 15:09 (UTC)
http://ix.io/2T3U
error
wuestengecko commented on 2021-03-05 11:23 (UTC)
Yes, that's what I was trying to say. It does fail when simply using
makechrootpkg
as well, unless you add--no-commit
to the mentioned line. When you're building directly on your development host, where you're using git to push to the AUR, then git will find your user config during the build and use that.Yes, please do that.
Nocifer commented on 2021-03-05 11:17 (UTC)
@wuestengecko Ah, that's a new one for me. So then, since this could potentially affect anyone trying to build the package without having set up a git identity (Docker or no Docker), I should probably add '--no-commit' to that cherry-pick line by default, yeah?
raqua commented on 2021-03-05 11:13 (UTC) (edited on 2021-03-05 11:15 (UTC) by raqua)
@wuestengecko I understand, but .gitconfig is not created on installation of git package. I just tried it in virtual machine. EDIT- I also checked my other machines, it is not there. Git was installed and no user configuration is done. Therefore I believe this will also fail regardless of Docker. Maybe the "--no-commit" clause should be there.
wuestengecko commented on 2021-03-05 11:05 (UTC)
@raqua The issue isn't that your build environment is too dirty, it's precisely the opposite: your environment is too clean. The issue is this line in the PKGBUILD:
Without
--no-commit
, git wants to record the cherry-pick in the commit history, and it wants to do so with you as the committer. If you're building in a chroot (or Docker container - same effect), it doesn't know who you are, because why would you set up git in an ephemeral environment.raqua commented on 2021-03-05 10:51 (UTC)
@Nocifer I am not doing anything dirty. At least I am not aware of it. All I do is
I am doing it inside Docker container so it is by principle fresh install. I was using the same Dockerfile for months now, there is no change and it was building before. After I added my git contact info it builds.
Nocifer commented on 2021-03-05 10:25 (UTC)
@raqua You shouldn't really, if git is asking you for an email it means you're trying to access a non-public or non-existent repo. If I had to guess, I'd say you're trying to do a "dirty" update of ZM and so the cherry-picked fix is not being applied. You should instead try to do a clean update, i.e. delete your previous sources and let makepkg download them all over again.
A proper install will look like this at the point where yours failed (this is from a build I did just now):
« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 62 Next › Last »