Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
drknstrmyknight opened this issue Aug 30, 2015 · 8 comments
Closed

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

drknstrmyknight opened this issue Aug 30, 2015 · 8 comments
Labels

Comments

@drknstrmyknight
Copy link

No description provided.

@ccrisan
Copy link
Collaborator

ccrisan commented 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.

@drknstrmyknight
Copy link
Author

Well, that was a wasted morning...
From: Calin Crisan [email protected]
To: ccrisan/motioneye [email protected]
Cc: drknstrmyknight [email protected]
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.

@ccrisan
Copy link
Collaborator

ccrisan commented Aug 30, 2015

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

@drknstrmyknight
Copy link
Author

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 [email protected]
To: ccrisan/motioneye [email protected]
Cc: drknstrmyknight [email protected]
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.

@ccrisan
Copy link
Collaborator

ccrisan commented 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.

@drknstrmyknight
Copy link
Author

Had to change my source to squeeze to get ffmpeg installed on debian jessie - all is good now.
From: Calin Crisan [email protected]
To: ccrisan/motioneye [email protected]
Cc: drknstrmyknight [email protected]
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.

@ccrisan
Copy link
Collaborator

ccrisan commented 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?

@drknstrmyknight
Copy link
Author

To: ccrisan/motioneye [email protected]
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 <[email protected]>

To: ccrisan/motioneye [email protected]
Cc: drknstrmyknight [email protected]
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.

ccrisan pushed a commit that referenced this issue Oct 3, 2016
Minor change in Motion Notifications section
ccrisan pushed a commit that referenced this issue Jun 13, 2019
jmichault added a commit that referenced this issue Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants