You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
x I am running the most recent version of the script.
x I have followed the setup instructions correctly.
x I have set the appropriate file permissions and modes.
x I am running the script as the correct user.
Update Script Version
1.1.02
Ombi Version:
3.0.3022
Operating System:
Ubuntu Server 17.10 (Linux 4.13.0-36-generic x64)
Custom Configuration: (update_ombi.conf)
N/A
Update Script Applicable Logs: (/var/log/ombiupdater.log by default)
N/A
Problem Description:
As of posting the script is broken, but assuming it is resolved by #20 this will only allow updating to beta versions of Ombi and only builds that come from the develop branch. It would be nice if we could have the script handle updates only to stable releases, or for that matter to other branches. In the case of #20 as you can see by the commit history the DotNetCore branch was renamed to develop after the initial PR was made, which furthers my opinion that the need for handling multiple branches should be considered.
Initial Troubleshooting:
N/A
Reproduction Steps:
N/A
Additional Detail:
N/A
The text was updated successfully, but these errors were encountered:
First Checks:
x I am running the most recent version of the script.
x I have followed the setup instructions correctly.
x I have set the appropriate file permissions and modes.
x I am running the script as the correct user.
Update Script Version
1.1.02
Ombi Version:
3.0.3022
Operating System:
Ubuntu Server 17.10 (Linux 4.13.0-36-generic x64)
Custom Configuration: (
update_ombi.conf
)N/A
Update Script Applicable Logs: (
/var/log/ombiupdater.log
by default)N/A
Problem Description:
As of posting the script is broken, but assuming it is resolved by #20 this will only allow updating to beta versions of Ombi and only builds that come from the
develop
branch. It would be nice if we could have the script handle updates only to stable releases, or for that matter to other branches. In the case of #20 as you can see by the commit history theDotNetCore
branch was renamed todevelop
after the initial PR was made, which furthers my opinion that the need for handling multiple branches should be considered.Initial Troubleshooting:
N/A
Reproduction Steps:
N/A
Additional Detail:
N/A
The text was updated successfully, but these errors were encountered: