Bug#366741: patch

[Robert Millan]

tags 366741 patch
thanks

Ok, this is not what I would send upstream, but I think it's suitable for
Debian.

Normaly, when you modify <platform_name> in client_state.xml, boinc will notice
the architecture is different than the hardcoded platform_name in the program,
and reset the project to avoid incompatible arch mixing.

The attached patch disables this check completely.  Instead of resetting the
project, it sets the <platform_name> in client_state.xml as the valid
platform_name which will be used for scheduler requests.

As for upstream, my plan is to check <platform_name> in client_state.xml against
a list of valid alternatives, but this needs some changes in
m4/boinc_platform.m4 first..

So could you apply this patch for Debian in the meantime?

-- 
Robert Millan

My spam trap is honeypot at aybabtu.com.  Note: this address is only intended for
spam harvesters.  Writing to it will get you added to my black list.
-------------- next part --------------
diff -ur boinc-5.4.10.old/client/client_state.C boinc-5.4.10/client/client_state.C
--- boinc-5.4.10.old/client/client_state.C	2006-05-23 02:03:15.000000000 +0200
+++ boinc-5.4.10/client/client_state.C	2006-08-20 19:51:38.000000000 +0200
@@ -331,14 +331,7 @@
     // This could happen e.g. if user copies files from PPC to Intel Mac
     //
     if (strcmp(platform_name, statefile_platform_name.c_str())) {
-        msg_printf(NULL, MSG_INFO,
-            "Platform changed from %s to %s - resetting projects",
-            statefile_platform_name.c_str(), platform_name
-        );
-        for (i=0; i<projects.size(); i++) {
-            p = projects[i];
-            reset_project(p);
-        }
+        platform_name = strdup (statefile_platform_name.c_str());
     }
 
     return 0;