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

Auto Upgrades when not on Stable branch break #898

Closed
calebcall opened this issue Jan 6, 2017 · 1 comment
Closed

Auto Upgrades when not on Stable branch break #898

calebcall opened this issue Jan 6, 2017 · 1 comment

Comments

@calebcall
Copy link

Ombi Version:

V 2.0.1186

Update Branch:

Early Access Preview or dev

Operating System:

OS X Sierra

Mono Version (only if your not on windows)

$ mono -V
Mono JIT compiler version 4.6.2 (mono-4.6.0-branch/08fd525 Thu Nov 10 20:28:28 EST 2016)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: normal
SIGSEGV: altstack
Notification: kqueue
Architecture: x86
Disabled: none
Misc: softdebug
LLVM: yes(3.6.0svn-mono-master/8b1520c)
GC: sgen

Applicable Logs (from /logs/ directory or the Admin page):


(Logs go here. Don't remove the ``` tags for showing your logs correctly. Please make sure you remove any personal information from the logs)

Problem Description:

Now I may be running this incorrectly. If I launch plexrequests.exe, I always get the 1.X version. However, if I launch Ombi.exe, I get the 2.X version. So when I do an auto update, it relaunches plexrequests.exe. Should I not be running Ombi.exe? If I try to run the Early Access Preview branch with plexrequests.exe, it appears to always be the current stable version that launches. Or, is auto update not actually available if you're not on the Stable branch?

Reproduction Steps:

Please include any steps to reproduce the issue, this the request that is causing the problem etc.

@Ombi-robot
Copy link

Hi!
Thanks for the issue report. Before a real human comes by, please make sure you used our bug report format.
Before posting make sure you also read our FAQ and known issues.
Make the title describe your issue. Having "not working" or "I get this bug" for 100 issues, isn't really helpful.
If we need more information or there is some progress we tag the issue or update the tag and keep you updated.
Cheers!
Ombi Support Team

tidusjar pushed a commit that referenced this issue Jan 9, 2017
@tidusjar tidusjar closed this as completed Jan 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants