Hi, On Sun, 27 Dec 2015 17:59:31 +0100 "W. Martin Borgert" <[email protected]> wrote: > Better solution than mess with /etc/hosts: > > Switch off the config_update in the plugininstaller plugin config > and disable the plugininstaller altogether in ~/.config/gajim/config: > > plugins.plugin_installer.active = False
thanks for the patch! But why does this bug not have RC severity? The fix is simple and non-intrusive. I'm sure you'll get a release exception for it. In fact gajim doesn't just phone home after first startup but it does so 30 seconds [1] after every startup! You can convince yourself by starting gajim like this: $ gajim --loglevel gajim.plugin_system=DEBUG 02/12/2017 08:31:20 (D) gajim.plugin_system Attributes processing started [... 30 seconds pass ...] 02/12/2017 08:31:50 (D) gajim.plugin_system PluginInstallerPlugin.check_update() <entered> 02/12/2017 08:31:50 (D) gajim.plugin_system Fetching https://ftp.gajim.org/plugins_0.16_zip/manifests.zip 02/12/2017 08:31:50 (D) gajim.plugin_system PluginInstallerPlugin.check_update() <left> It is easy for the user to disable this by disabling the plugin_installer plugin but the user probably will only get to doing this *after* gajim already contacted that ftp server and informed the user. If you don't have time for an upload, I'll gladly do an NMU for you! Thanks! cheers, josch [1] http://sources.debian.net/src/gajim/0.16.6-1/plugins/plugin_installer/plugin_installer.py/?hl=92#L92
signature.asc
Description: signature
