Comment 136 for bug 57875

Hi Shawn,

Just an update, I have fixed the said annoyance by disabling the SWT check in the source. I cleaned out my Azureus tree and only got an update for azupdater, which applied successfully. Subsequent startups did not have nagging updates or errors.

The change is currently in bzr on Launchpad; along with another one that enforces the usage of a Icedtea or Sun Java 5/6 stack. (Turns out GCJ is EXTREMELY slow hash-checking to the point that it's unacceptable). I will not be rolling out a testing deb until I get some more feedback on the changes, to avoid spamming with a huge storm of updated debs and bloated version numbers.