Index: modules/update/update.authorize.inc
===================================================================
RCS file: /cvs/drupal/drupal/modules/update/update.authorize.inc,v
retrieving revision 1.3
diff -u -r1.3 update.authorize.inc
--- modules/update/update.authorize.inc	1 Nov 2009 23:02:13 -0000	1.3
+++ modules/update/update.authorize.inc	1 Apr 2010 23:32:52 -0000
@@ -154,7 +154,9 @@
   }
 
   _update_batch_create_message($context['results']['log'][$project], t('Installed %project_name successfully', array('%project_name' => $project)));
-  $context['results']['tasks'] += $tasks;
+  if (!empty($tasks)) {
+    $context['results']['tasks'] += $tasks;
+  }
 
   // This particular operation is now complete, even though the batch might
   // have other operations to perform.
@@ -206,7 +208,11 @@
       'type' => 'error',
     );
   }
-
+  // Since we're doing an update of existing code, always add a task for
+  // running update.php.
+  $results['tasks'][] = t('Your modules have been downloaded and updated.');
+  $results['tasks'][] = t('<a href="@update">Run database updates</a>', array('@update' => base_path() . 'update.php'));
+
   // Set all these values into the SESSION so authorize.php can display them.
   $_SESSION['authorize_results']['success'] = $success;
   $_SESSION['authorize_results']['page_message'] = $page_message;
Index: modules/system/system.updater.inc
===================================================================
RCS file: /cvs/drupal/drupal/modules/system/system.updater.inc,v
retrieving revision 1.6
diff -u -r1.6 system.updater.inc
--- modules/system/system.updater.inc	31 Mar 2010 19:10:39 -0000	1.6
+++ modules/system/system.updater.inc	1 Apr 2010 23:32:52 -0000
@@ -81,10 +81,8 @@
   }
 
   public function postUpdateTasks() {
-    // @todo: If there are schema updates.
-    return array(
-      l(t('Run database updates for !project', array('!project' => $this->title)), 'update.php'),
-    );
+    // We don't want to check for DB updates here, we do that once for all
+    // updated modules on the landing page.
   }
 
 }