@acodega commented on GitHub:
Would you like to open a PR? We have a guide at https://github.com/Installomator/Installomator/wiki/GitHub-howto-create-PRs
@rs1278 commented on GitHub:
yes, but I believe i need write access to the installomator repo
@duderin0 commented on GitHub:
Since its been 2 weeks, I've submitted my own (#1128 ) and have used XPath instead of the curl options, since I couldn't get the above to work.
@scriptingosx commented on GitHub:
you can add a loading with Swift Dialog. example scripts are here https://github.com/Installomator/Installomator/blob/main/MDM/swiftdialog_example.sh and here…
@KUSU2 commented on GitHub:
Fixed with https://github.com/Installomator/Installomator/pull/1097
@duderin0 commented on GitHub:
They only added a suffix of "-x86_64" to the name of the download file, so an easy change. Submitted #1084 for this, since both this version (7.3) and last (7.2)…
@acodega commented on GitHub:
The proper fix would be to change the downloadURL so not use downloadURLFromGit, since that will get the "latest" and not the pre-release. Tunnelblick is unusual in…
@duderin0 commented on GitHub:
The label is set to download only what is released under the Latest tag, but the appNewVersion only…
@scriptingosx commented on GitHub:
can confirm, though the latest version of the script provides a more helpful 404 error. The download URL must have changed
@duderin0 commented on GitHub:
Yeah that was what I was thinking, and had done for another label (bitwarden #1067). I spent some time trying to figure out a way to consistently get the beta, but…
@bbrendon commented on GitHub:
It used to download 4.0beta consistently. And according to some docs in Tunnelblick it is recommended for compatibility.( I know it’s strange. ). If it’s…
@bbrendon commented on GitHub:
I think I have a fix. Could someone merge it if it satisfies the maintainers?
version_plus_build=$(curl -sf https://github.com/Tunnelblick/Tunnelblick/relea…
@huexley commented on GitHub:
I've opened a case on their support forum… Well thanks anyway !
@scriptingosx commented on GitHub:
Why should it not consider 3.3.2 and 3.3.2.0 the same?
@bbrendon commented on GitHub:
@scriptingosx can we use the fix I posted?