t/50-checksum: /possibly/ fix a stuck test

This possible fix could also be hiding another bug, but the
original test ordering was suspect...
Checking in changes prior to tagging of version 2.61.

Changelog diff is:

diff --git a/CHANGES b/CHANGES
index 5b59d7f..de3ba9b 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,33 @@
+2012-05-18: Release version 2.61
+
+   * fix issue #57 by Pyry and Eric (dormando <dormando@rydia.net>)
+     (mogadm host status sometimes allowed typos)
+
+   * avoid unnecessary devcount update in create_close (Eric Wong <normalperson@yhbt.net>)
+
+   * sqlite: implement locking via tables (Eric Wong <normalperson@yhbt.net>)
+
+   * worker/query: Add optional callid parameter (Gernot Vormayr <notti@bgcc.at>)
+     (allows command pipelining)
+
+   * delete: prevent orphan files from replicator race (Eric Wong <normalperson@yhbt.net>)
+
+   * fsck: prevent running over 100% completion (Eric Wong <normalperson@yhbt.net>)
+
+   * fsck: cleanup and reduce unnecessary devcount updates (Eric Wong <normalperson@yhbt.net>)
+
+   * fsck: update devcount, forget devs on unfixable FIDs (Eric Wong <normalperson@yhbt.net>)
+
+   * fsck: log bad count correctly instead of policy violation (Eric Wong <normalperson@yhbt.net>)
+
+   * tests: add test for fsck functionality (Eric Wong <normalperson@yhbt.net>)
+
+   * monitor: only broadcast reject_bad_md5 on change (Eric Wong <normalperson@yhbt.net>)
+
+   * worker: delete_domain returns has_classes error (Eric Wong <normalperson@yhbt.net>)
+
+   * log: enable autoflush for stdout logging (Eric Wong <normalperson@yhbt.net>)
+
 2012-03-30: Release version 2.60

    * Fix fsck status when running for the first time (dormando <dormando@rydia.net>)
dangling reference to MogileFS::Sys removed
Postgres: Fix v15 schema upgrade.

Schema upgrade needs to use Pg-specific column types for the v15 upgrade
adding class.hashtype. Only CREATE TABLE is auto-converted where
possible, not ALTER TABLE.

Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
fix CHANGES for 2.60 :P
Checking in changes prior to tagging of version 2.62.

Changelog diff is:

diff --git a/CHANGES b/CHANGES
index b526b6a..6333f9f 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,9 @@
+2012-05-19: Release version 2.62
+
+   * Critical bugfix for a compilation error (dormando, reported by Robin)
+
+   * Fix for upgrading a Postgres install for checksums (Robin * H. Johnson <robbat2@gentoo.org>)
+
 2012-05-18: Release version 2.61

    * fix issue #57 by Pyry and Eric (dormando <dormando@rydia.net>)
postgres: fix replace_into_file regression in 2.61

commit f54e6fd1076e0c71e5ab9b9dfa1bf01a7960e0e8 botched
the ordering of parameters when updating the file table.
Checking in changes prior to tagging of version 2.63.

Changelog diff is:

diff --git a/CHANGES b/CHANGES
index 6333f9f..07790f3 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,8 @@
+2012-05-29: Release version 2.63
+
+   * Critical bugfix for Postgres users introduced by 2.61. New file uploads
+     would fail. (noticed by robin H. Johnson, fixed by Eric Wong)
+
 2012-05-19: Release version 2.62

    * Critical bugfix for a compilation error (dormando, reported by Robin)
monitor skips hosts marked dead or down

Host don't define readability/writability themselves, so the
Host::should_get_new_files sub is renamed to "alive" and
Device->can_read_from respects host status.

Also, queryworker now skips down/dead hosts in cmd_get_paths.

ref: http://code.google.com/p/mogilefs/issues/detail?id=46
Device->observed_* all respects observed host state

The observed unreachable state of the host should always supercede the
observed state of the device.  This is already the case with
observed_writeable, but not with observed_readable nor
observed_unreachable.

The monitor worker does not (and should not, to save bandwidth) update
states of all devices when a host goes down.
Device->should_read_from respects all host/device states

should_read_from() should replace all uses of can_read_from() in
non-Monitor workers.  This avoids the overhead of needlessly
rechecking devices either the monitor or user marked down.

This simplifies queryworker logic a bit.
DevFID size/checksum respects Device->should_read_from

Avoid needlessly attempting connections for checking files on
host/devices the monitor (or user) marked as unreadable.

This also makes the Fsck->size_on_disk function redundant.