On Tue, Jan 23, 2018 at 12:33 PM, Kris Keller <[email protected]> wrote:
> My team currently runs a custom version of the guacamole server based off > of version 0.9.9. We recently merged in commits from GUACAMOLE-40< > https://issues.apache.org/jira/browse/GUACAMOLE-40> to get support RDS. > We specifically cherry picked from these commits made on Apr 10 2017: > https://github.com/glyptodon/guacamole-server/commit/ > af8ef9f526546acc6682cb8ea591f7dad7f849d8 > https://github.com/glyptodon/guacamole-server/commit/ > da8636ef546add9f71db6ffcc0d873e085d5e13f > https://github.com/glyptodon/guacamole-server/commit/ > 09099050cb2448a6b40ac3b17eab59f47c57d6a2 > > Beware that this is not the upstream git repository for guacamole-server; it is the repository used by the project prior to the move to the ASF. The correct repository for guacamole-server is: https://github.com/apache/guacamole-server We only took the changes specifically for the load-balance-info switch and > didn’t not take the gateway or C MACRO changes. > A forked, modified version of 0.9.9 with some upstream commits backported / cherry-picked is simply not an Apache Guacamole release. Before moving forward with this, can you please try to reproduce what you're seeing against the latest upstream code (either 0.9.14 or git master)? The conversation and investigation for this really needs to be relevant to Apache Guacamole and its community, rather than to your internal fork. If this is determined to be a bug, the issue is fixed upstream, and you ultimately backport that fix to your internal fork, that's absolutely fine, but the baseline for everything here needs to be current, unmodified, Apache Guacamole. - Mike
