Package: pumpa Version: 0.9-1 Severity: normal If I have a note I'm trying to post, and the current wifi network is a typical horrible gatewayed public wifi network, the post may fail a couple of times. I'll then go do something else. In the meantime, pumpa will try to refresh the timeline. Then pumpa will complain that it got a bad ssl cert. Then it will exit. This causes the words I was trying to post to get lost.
I suggest pumpa not exit in this situation, but instead just fail whatever network operation is being blocked by the MITM. (Not filing at grave bug severity because meh, it's just words. How important can words be? ...) -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pumpa depends on: ii libaspell15 0.60.7~20110707-3 ii libc6 2.19-17 ii libgcc1 1:4.9.2-10 ii libqjson0 0.8.1-3 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libstdc++6 4.9.2-10 ii libtidy-0.99-0 20091223cvs-1.4 pumpa recommends no packages. pumpa suggests no packages. -- no debconf information -- see shy jo
signature.asc
Description: Digital signature
