mirror of
https://github.com/motioneye-project/motioneye.git
synced 2026-03-02 22:57:06 -05:00
pip command to install latest commit #11
Labels
No labels
Android app
Arch Linux
CI/CD
CSS
FreeBSD
HTML/HTTP
Home Assistant addon
JavaScript
Python
Raspberry Pi
Stale No Activity 60 Days
bug
code format
dependencies
dev branch
docker
documentation
duplicate
enhancement
feature
help wanted
i18n/l10n
invalid
legacy motionEye
meta
motion
motionEyeOS
notourproblem
python update
question
question
security
troubleshooting
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/motioneye#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @latimeria68 on GitHub (Sep 8, 2015).
Hi Calin,
0.27.2 version still giving me lot of errors; is there a pip command to upgrade to the latest commit before a new version is released?
Thanks
@ccrisan commented on GitHub (Sep 8, 2015):
The difference between 0.27.2 is insignificant. First of all, let me see what errors you are talking about so I can identify the source of the problem.
Secondly, to answer your question, there is a possibility to install the latest commit:
pip uninstall motioneye.tar zxvf master.tar.gz.cd [extracted_motioneye_folder] && python setup.py install --prefix=/usr.@latimeria68 commented on GitHub (Sep 8, 2015):
motioneye is not recording any movie when motion is detected; I have compiled Mr Dave's fork and I got the following warnings in motion.log:
[0] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motioneye/motion.conf
[0] [NTC] [ALL] config_thread: Processing config file thread-1.conf
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_output_movies"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_variable_bitrate"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_video_codec"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "movie_filename"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_bps"
[0] [NTC] [ALL] config_thread: Processing config file thread-2.conf
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_output_movies"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_variable_bitrate"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_video_codec"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "movie_filename"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_bps"
[0] [NTC] [ALL] motion_startup: Motion Unofficial-Git-d71cebf Started
[0] [NTC] [ALL] motion_startup: Logging to syslog
[0] [NTC] [ALL] motion_startup: Using default log type (ALL)
[0] [NTC] [ALL] motion_startup: Using log type (ALL) log level (EMG)
now I don't know if it's a motioneye problem about how it reads motion.conf parameters ( found it here http://www.lavrsen.dk/foswiki/bin/view/Motion/SupportQuestion2014x05x06x220454 ).
Then ( and this is quite trivial ) when an email is received after motion detection event, outlook 2007 reports as email recipient " n; a; m; e;.s; u r; n; a; m; e; @; g; m; a; i; l; .; c; o; m "........why all those semicolons?
Thanks
@ccrisan commented on GitHub (Sep 8, 2015):
I think you have upgraded from motionEye 0.26 or earlier. You must remove all your config files and re-add the cameras after installing motionEye 0.27.
@latimeria68 commented on GitHub (Sep 8, 2015):
yes, seemed I forgot to completely purge remove old motion install before compiling from Mr Dave fork.
If you're interested on, you could put a link on motion compiling page for Raspbian users:
https://crcok.wordpress.com/2015/01/22/cant-compile-motion-with-rtsp-on-raspberry-pi/
doing the following before compiling is the way to avoid ffmpeg support to be disabled:
sudo ln -s /usr/lib/arm-linux-gnueabihf/libavcodec.a /usr/lib/libavcodec.a
sudo ln -s /usr/lib/arm-linux-gnueabihf/libavcodec.so /usr/lib/libavcodec.so
sudo ln -s /usr/lib/arm-linux-gnueabihf/libavformat.a /usr/lib/libavformat.a
sudo ln -s /usr/lib/arm-linux-gnueabihf/libavformat.so /usr/lib/libavformat.so
Thanks
@ccrisan commented on GitHub (Sep 9, 2015):
The instructions are here and are applicable to various common distros (including Raspbian). Symlinking doesn't seem to be required.
@latimeria68 commented on GitHub (Sep 9, 2015):
When I compiled Mr Dave motion the first time I exactly faced the error reported in the link I gave ( on the latest version of Raspbian ); creating all above symlinks did the trick for me. Anyway it is just a suggestion for users may face the same problem.
Thanks
@electronicamystica commented on GitHub (Sep 17, 2015):
@sgiannulli : thanks!
I also had to link the files to get ffmpeg support using raspi B with OS:
Linux raspberrypi 4.1.6+ #810 PREEMPT Tue Aug 18 15:19:58 BST 2015 armv6l GNU/Linux
@ccrisan commented on GitHub (Sep 18, 2015):
I have updated both Install On Raspbian and Compiling Motion to help users build motion on Raspbian.
More precisely, instead of creating links to the misplaced libs, the configure script needs to be told to look for them in some other places: