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

SickRage install fails not finding autoProcessTV/autoProcessTV.cfg.sample #29

Closed
htpcBeginner opened this issue Nov 19, 2015 · 9 comments

Comments

@htpcBeginner
Copy link
Owner

http://www.htpcbeginner.com/atomic-toolkit/#comment-5004

@ZaLiTHkA
Copy link
Contributor

I believe this might be a duplicate of #25.. I saw the post a few days back, but I haven't had a chance to check it myself yet.

@Phobix
Copy link

Phobix commented Nov 23, 2015

also having this issue

@Phobix
Copy link

Phobix commented Nov 23, 2015

I found the issue. The sickrage git no longer has the AutoProcessTV folder. I was able to edit the sickrage install script to use an alternative file location that contained the .cfg.example it was looking for. Just go into the sickrage install script and look for the correct line and edit accordingly.

@htpcBeginner
Copy link
Owner Author

@Phobix where did you find the autoProcessTV.cfg.example file?

@Phobix
Copy link

Phobix commented Nov 25, 2015

github, just search for the file. I can also upload here if needed.

@htpcBeginner
Copy link
Owner Author

@Phobix there is no autoProcessTV.cfg.sample file in SickRage. I couldn't find it. That is why I asked for the specific path.

@htpcBeginner
Copy link
Owner Author

Fixed in development branch. The script now looks for autoProcessTV.cfg.sample file. If not found, it moves on with installation without erroring out.

@Phobix
Copy link

Phobix commented Nov 27, 2015

Are you just having it auto create its own? Its only like 5 lines, can just have the script create the needed file.

@htpcBeginner
Copy link
Owner Author

@Phobix Yes, but the question is is autoProcessTV.cfg file need anymore? There should be a reason why it was removed from SickRage.

Right now (with the fix) the script just ignores if it is not found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants