ZoneMinder Forums

Sorry it took so long but the 1.22.2 rpm is up and ready for testing.

http://www.computerntelecom.com/pub/lin ... testing/3/

You will need ffmpeg-0.4.9-0.3 packages (minus the devel unless you want it) also in the same directory as above.

To upgrade use rpm -Uvh zm-1.22.2-0.0.fc.root.i386.rpm

You don't even have to stop the service

Regards,
Corey

[edit] corrected URL
Please report any problems you encounter with this package here in this thread.

Hey cordel, check the IP that isn't working

You are doing a grat job, thanks you a lot!

http://computerntelecom.com/pub/linux/z ... testing/3/
Looks like corery put the locasl address, bet it works fine for him, lol Anyway try the above

My bad, was in a cut and paste kinda mood

If there are no major issues, I'll add it to the yum repo after about a week. Same for the ffmpeg packages.

Regards,
Corey

awesome work man your rpm has made my life very easy these past couple of days with the problems i was having compiling.
I tried to install your latest rpm but I get some failed deps

rpm -Uhv ffmpeg-libpostproc-0.4.9-0.3.20051207.2.fc3.CTU.i386.rpm
error: Failed dependencies:
pkgconfig is needed by ffmpeg-libpostproc-0.4.9-0.3.20051207.2.fc3.CTU.i386


rpm -Uhv ffmpeg-0.4.9-0.3.20051207.2.fc3.CTU.i386.rpm
error: Failed dependencies:
libfaac.so.0 is needed by ffmpeg-0.4.9-0.3.20051207.2.fc3.CTU.i386
libpostproc.so.0.0.1 is needed by ffmpeg-0.4.9-0.3.20051207.2.fc3.CTU.i386
libtheora.so.0 is needed by ffmpeg-0.4.9-0.3.20051207.2.fc3.CTU.i386
libxvidcore.so.4 is needed by ffmpeg-0.4.9-0.3.20051207.2.fc3.CTU.i386

[root@dvr ~]# rpm -Uhv zm-1.22.2-0.0.fc.root.i386.rpm
error: Failed dependencies:
ffmpeg >= 0.4.9 is needed by zm-1.22.2-0.0.fc.root.i386
libavutil.so is needed by zm-1.22.2-0.0.fc.root.i386
perl(X10::ActiveHome) is needed by zm-1.22.2-0.0.fc.root.i386


is it possible to add the testing folder as a yum repo?

i think if you look in the contribs part for coreys entry on the distro there is a step by step guide to get funning on fc3 including adding his servers as repo's

I tried modifying one of the repos using the testing folder although I'm pretty sure you're gonna laugh when you see what I did, needless to say it didn't work. I searched the forum but only the update server and the base server repo config are listed.

[ctu-testing]
name=CTU Core $releasever - $basearch - testing
#baseurl=ftp://download.computerntelecom.com/pub ... /$basearch
gpgkey=ftp://download.computerntelecom.com/pub/RPM-GPG-KEY-CTU
enabled=1
gpgcheck=1

what did I miss?

#baseurl=ftp://download.computerntelecom.com/pub ... /$basearch

You have this commented out id remove the # and try again. This wont install 1.22.2 but you will be able to install the previous versions that Corey put up this way. Out of interest if this is a dedicated machine can you not just download the ct install cd, as this and the live cd make things quite easy!

I had some time constraints and I was in panic mode (management riding me too hard) but now that things are up and running for me I take more time to explore those options.

I was able to get the 1.21.4 rpm properly i'll wait till the 1.22 rpm gets placed in released i guess no rush now this is more like icing on the cake

yum will not work in the testing directory as I don't have the xml files created for it. I make people work for those packages in hopes that it will cause them enough concern to backup their files and database
I was always affraid that if I made it to easy, some one might put that directory as enabled in yum and accidenly update from testing so I didn't set that one up.

By the way, any problems found should be reported in this thread.

Regards,
Corey

The 64 bit version is now up for testing

Cheers,
Corey

good stuff Corey

I did the 1.22.2 upgrade & it went without a problem, but the version # at the top still shows 1.22.0 I know it did install, there is a new feature where it shows a line of info above the playback of an event. Did I miss something ?
I don't have to run zmupdatepkg.pl anymore right ?

zmupdate should run when the service restarts which should happen after the package finishes updating. If 1.22.0 is still displayed then the /etc/zm.conf file might have not updated properly. Try restarting the service and see if the zm.conf file updates, else I will have to try to find why this didn't work on your system.
In /etc/init.d/zm is the script responsible for updating the config file and the database.

Regards,
Corey

happened here to
updated ok
but still shows 1.22.0