id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc,fix_version,see_also 949,edsc explodes on encountering old discussd,jweiss,,"I tried to start edsc and saw the following in the *Messages* buffer: Loading discuss...done Starting discuss.... waiting for discuss... Started edsc process.... version 2.5 (Sat Oct 2 20:31:43 UTC 2010) builder@zulu.mit.edu:/build/builder-debathena-discuss_10.0.13-0debathena1~ubuntu10.04-i386-Fb_PAD/debathena-discuss-10.0.13/edsc) Listing meetings... error in process filter: discuss-read-form: End of file during parsing error in process filter: End of file during parsing some debugging indicated that it's failing to connect to bloom-beacon. In a similar case discuss reports: peter-petrelli:~/Mail$ discuss charon-maint Discuss version 1.7. Type '?' for a list of commands. discuss: RPC server too old while authenticating to discuss server Error going to Charon_Maintainers_Archive: Connection reset by peer I assume beacon is running a k4 only discussd, and while that is a separate problem, edsc should simply declare the relevant meeting unavailable and not fail outright. (I'll send mail to news about beacon's discussd under seperate cover, which may moot this bug, unless there are other ancient discussds out there, but if my .meetings didn't have one, they're pretty rare).",defect,closed,low,The Distant Future,--,fixed,,,,