Bug#415765: boinc-client left in a broken state after removing boinc-app-seti

[Magnus Holmgren]

Package: boinc-app-seti
Version: 5.13+cvs20060510-1
Severity: normal

It seems that after boinc-app-seti is removed (and purged),
boinc_client doesn't notice that the seti app is gone and goes
berserk, rapidly downloading new workunits only to find that the
processing fails, but not why. You can see the result here:

http://setiathome.berkeley.edu/results.php?hostid=1312855

I haven't figured out how to get things back to normal yet.

Removal of boinc-app-seti should leave the data directory in a state
that causes boinc_client to automatically re-download the SETI at home
app. If that's not possible without detaching from and reattaching to
SETI at home, please reassign this bug to boinc-client.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (10, 'unstable'), (9, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-proffe-1
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)