motioneye.py dated 8/30/2015 is 0 bytes

deekerman commented

2026-02-28 00:01:53 -05:00

Owner

Originally created by @drknstrmyknight on GitHub (Aug 30, 2015).

deekerman

2026-02-28 00:01:53 -05:00

closed this issue
added the
invalid
label

deekerman commented

2026-02-28 00:02:01 -05:00

Author

Owner

@ccrisan commented on GitHub (Aug 30, 2015):

Yes, the file is no longer used and will be removed. The migration to setuptools and github is not yet complete. I'm working on some wiki pages that will help users install, configure and run motionEye on their systems. Until then, please stick with the bitbucket 0.26 version.

@ccrisan commented on GitHub (Aug 30, 2015): Yes, the file is no longer used and will be removed. The migration to setuptools and github is not yet complete. I'm working on some wiki pages that will help users install, configure and run motionEye on their systems. Until then, please stick with the bitbucket 0.26 version.

deekerman commented

2026-02-28 00:02:02 -05:00

Author

Owner

@drknstrmyknight commented on GitHub (Aug 30, 2015):

Well, that was a wasted morning...
From: Calin Crisan notifications@github.com
To: ccrisan/motioneye motioneye@noreply.github.com
Cc: drknstrmyknight frank@boffey.com
Sent: Sunday, August 30, 2015 12:58 PM
Subject: Re: [motioneye] motioneye.py dated 8/30/2015 is 0 bytes (#1)

Yes, the file is no longer used and will be removed. The migration to setuptools and github is not yet complete. I'm working on some wiki pages that will help users install, configure and run motionEye on their systems. Until then, please stick with the bitbucket 0.26 version.—
Reply to this email directly or view it on GitHub.

@drknstrmyknight commented on GitHub (Aug 30, 2015): Well, that was a wasted morning... From: Calin Crisan notifications@github.com To: ccrisan/motioneye motioneye@noreply.github.com Cc: drknstrmyknight frank@boffey.com Sent: Sunday, August 30, 2015 12:58 PM Subject: Re: [motioneye] motioneye.py dated 8/30/2015 is 0 bytes (#1) Yes, the file is no longer used and will be removed. The migration to setuptools and github is not yet complete. I'm working on some wiki pages that will help users install, configure and run motionEye on their systems. Until then, please stick with the bitbucket 0.26 version.— Reply to this email directly or view it on GitHub.

deekerman commented

2026-02-28 00:02:02 -05:00

Author

Owner

@ccrisan commented on GitHub (Aug 30, 2015):

I'm sorry, what exactly was a wasted morning? For whom? I'm not sure I understand the issue here.

@ccrisan commented on GitHub (Aug 30, 2015): I'm sorry, what exactly was a wasted morning? For whom? I'm not sure I understand the issue here.

deekerman commented

2026-02-28 00:02:02 -05:00

Author

Owner

@drknstrmyknight commented on GitHub (Aug 30, 2015):

going through the motions of installing 27.1Don't get me wrong, you're going great work, I just got caught in the flux
From: Calin Crisan notifications@github.com
To: ccrisan/motioneye motioneye@noreply.github.com
Cc: drknstrmyknight frank@boffey.com
Sent: Sunday, August 30, 2015 5:17 PM
Subject: Re: [motioneye] motioneye.py dated 8/30/2015 is 0 bytes (#1)

I'm sorry, what exactly was a wasted morning? For whom? I'm not sure I understand the issue here.—
Reply to this email directly or view it on GitHub.

@drknstrmyknight commented on GitHub (Aug 30, 2015): going through the motions of installing 27.1Don't get me wrong, you're going great work, I just got caught in the flux From: Calin Crisan notifications@github.com To: ccrisan/motioneye motioneye@noreply.github.com Cc: drknstrmyknight frank@boffey.com Sent: Sunday, August 30, 2015 5:17 PM Subject: Re: [motioneye] motioneye.py dated 8/30/2015 is 0 bytes (#1) I'm sorry, what exactly was a wasted morning? For whom? I'm not sure I understand the issue here.— Reply to this email directly or view it on GitHub.

deekerman commented

2026-02-28 00:02:02 -05:00

Author

Owner

@ccrisan commented on GitHub (Aug 30, 2015):

This migration to github, to PyPI and everything is long overdue. I knew it wouldn't be easy but it had to be done. As soon as I manage to put together new install docs, things will become a lot clearer for everyone.

@ccrisan commented on GitHub (Aug 30, 2015): This migration to github, to PyPI and everything is long overdue. I knew it wouldn't be easy but it had to be done. As soon as I manage to put together new install docs, things will become a lot clearer for everyone.

deekerman commented

2026-02-28 00:02:02 -05:00

Author

Owner

@drknstrmyknight commented on GitHub (Sep 1, 2015):

Had to change my source to squeeze to get ffmpeg installed on debian jessie - all is good now.
From: Calin Crisan notifications@github.com
To: ccrisan/motioneye motioneye@noreply.github.com
Cc: drknstrmyknight frank@boffey.com
Sent: Sunday, August 30, 2015 5:34 PM
Subject: Re: [motioneye] motioneye.py dated 8/30/2015 is 0 bytes (#1)

This migration to github, to PyPI and everything is long overdue. I knew it wouldn't be easy but it had to be done. As soon as I manage to put together new install docs, things will become a lot clearer for everyone.—
Reply to this email directly or view it on GitHub.

@drknstrmyknight commented on GitHub (Sep 1, 2015): Had to change my source to squeeze to get ffmpeg installed on debian jessie - all is good now. From: Calin Crisan notifications@github.com To: ccrisan/motioneye motioneye@noreply.github.com Cc: drknstrmyknight frank@boffey.com Sent: Sunday, August 30, 2015 5:34 PM Subject: Re: [motioneye] motioneye.py dated 8/30/2015 is 0 bytes (#1) This migration to github, to PyPI and everything is long overdue. I knew it wouldn't be easy but it had to be done. As soon as I manage to put together new install docs, things will become a lot clearer for everyone.— Reply to this email directly or view it on GitHub.

deekerman commented

2026-02-28 00:02:02 -05:00

Author

Owner

@ccrisan commented on GitHub (Sep 1, 2015):

That's odd. I tried it with debian 8 and it went alright with "jessie". What was the problem, so I can update the docs?

@ccrisan commented on GitHub (Sep 1, 2015): That's odd. I tried it with debian 8 and it went alright with "jessie". What was the problem, so I can update the docs?

deekerman commented

2026-02-28 00:02:02 -05:00

Author

Owner

@drknstrmyknight commented on GitHub (Sep 18, 2015):

 From: "frank@boffey.com" <frank@boffey.com>

To: ccrisan/motioneye reply@reply.github.com
Sent: Tuesday, September 1, 2015 7:07 AM
Subject: Re: [motioneye] motioneye.py dated 8/30/2015 is 0 bytes (#1)

Had to change my source to squeeze to get ffmpeg installed on debian jessie - all is good now.

 From: Calin Crisan <notifications@github.com>

To: ccrisan/motioneye motioneye@noreply.github.com
Cc: drknstrmyknight frank@boffey.com
Sent: Sunday, August 30, 2015 5:34 PM
Subject: Re: [motioneye] motioneye.py dated 8/30/2015 is 0 bytes (#1)

This migration to github, to PyPI and everything is long overdue. I knew it wouldn't be easy but it had to be done. As soon as I manage to put together new install docs, things will become a lot clearer for everyone.—
Reply to this email directly or view it on GitHub.

@drknstrmyknight commented on GitHub (Sep 18, 2015): ``` From: "frank@boffey.com" <frank@boffey.com> ``` To: ccrisan/motioneye reply@reply.github.com Sent: Tuesday, September 1, 2015 7:07 AM Subject: Re: [motioneye] motioneye.py dated 8/30/2015 is 0 bytes (#1) Had to change my source to squeeze to get ffmpeg installed on debian jessie - all is good now. ``` From: Calin Crisan <notifications@github.com> ``` To: ccrisan/motioneye motioneye@noreply.github.com Cc: drknstrmyknight frank@boffey.com Sent: Sunday, August 30, 2015 5:34 PM Subject: Re: [motioneye] motioneye.py dated 8/30/2015 is 0 bytes (#1) This migration to github, to PyPI and everything is long overdue. I knew it wouldn't be easy but it had to be done. As soon as I manage to put together new install docs, things will become a lot clearer for everyone.— Reply to this email directly or view it on GitHub.

deekerman referenced this issue

2026-02-28 01:00:00 -05:00

emulate motion not working correctly #1974

deekerman referenced this issue

2026-02-28 01:04:16 -05:00

Problem installing on Debian Bullseye #2112

Rows
Columns

motioneye.py dated 8/30/2015 is 0 bytes #3