Package: feed2imap Version: 1.2.3-1 Severity: minor My gateway lost network access (so my machine didn't notice) recently and I got a pile of those messages from cron in my inbox:
/usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:218:in `join': No live threads left. Deadlock? (fatal) from /usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:218:in `block in initialize' from /usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:218:in `each' from /usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:218:in `initialize' from /usr/bin/feed2imap:48:in `new' from /usr/bin/feed2imap:48:in `<main>' Now I don't expect feed2imap to do anything magical when network goes out: failing is fine and expected. But "No live threads left. Deadlock?" is hardly a error message anyone should be expected to understand. I would suggest "unreachable host" or something to that effect. :) Thanks -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages feed2imap depends on: ii ruby 1:2.1.5 ii ruby-feedparser 0.9.3-2 ii ruby-rubymail 1.0.0-2 ii ruby2.1 [ruby-interpreter] 2.1.5-2 feed2imap recommends no packages. Versions of packages feed2imap suggests: ii dovecot-imapd [imap-server] 1:2.2.13-11 ii evolution [imap-client] 3.12.9~git20141130.241663-1+b1 ii mutt [imap-client] 1.5.23-3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
