Avoid truncating image files

Thanks to inejge for the bug report and patch.

Now with striped LV support

Thanks for sjbrunner for the patch.

Support for parsing striped LVs from vgcfgbackup

sjbronner discovered that the vgcfgbackup parser in lvmsync didn't
handle striped LVs, and instead crashed. Note that I don't know whether
lvmsync will actually work when syncing off a striped LV, but at least
the parser doesn't crash now.

Also incorporates some documentation fixes from nickjwebb.

Now with debugging!

In case you're having real problems, you can now run with --debug to get
as much detail as we can give you about what's going on. To compensate,
--verbose has been turned down a little.

New options: --data-source, --quiet, and --rsh

Quite the flurry of new features today, although they're somewhat niche.

For anyone who wants to do consistent "rolling" snapshots, the
--data-source will be useful, by letting you specify any other block
device as the one to read data blocks from. Specifying completely the wrong
block device will end in tears, so don't make a mistake...

If knowing how much time you've saved annoys you, the --quiet option will
cause lvmsync to only display fatal error messages.

Finally, if you want to run something other than just ssh as your network
transport, the --rsh option will suit you perfectly.

Ignore some errors when reading the remote's error output

Just a little bugfix to help out with tracking down problems.

Ruby 1.8 compatibility fixes

May as well maintain support while we can.

Dependency fixes, and more useful output

Just one little bug fixed here: due to recent changes, lvmsync now needs a
newer version of git-version-bump, but we didn't declare that dependency.
So, anyone who upgraded from an earlier version of lvmsync as a gem wouldn't
have upgraded git-version-bump, and all hell broke loose.

In an attempt to hunt down another bug, I've also improved the reporting of
problems issuing from the lvmsync "receiver" process. This means that if
the receiver reports any problems, they'll be displayed (prefixed by
"remote:"), rather than being lost for all eternity (or irritatingly
interspersed with local output).

Fix outrageous offsets (and add --version option)

With help from several people who provided input, but especially
@UnwashedMeme, who did the legwork to identify the root cause, this
showstopped bug is now finally fixed. Apologies to everyone for the time it
took to get this fixed.

The Womble & Womble "no more tears" release

I've jumped the version number significantly here, to bring it in line with
the current protocol version; that'll be the benchmark for a major version
release from now on (since that's the epitomy of non-backwards-compatible).
Things fixed in this release include:

• lvmsync now works again, for everyone;
• It should now work under Ruby 1.8 or later, for those poor sods still
  running RHEL 5;
• Snapback files have their header back, so they look like snapback files
  again;
• Arbitrary LV and VG names should now be recognised and properly escaped;
• htonq works the right way around now;
• The test suite has been fixed so it always invokes the lvmsync under test,
  rather than the system-wide one.

The vast majority of the work involved in this release wasn't done by me,
and I'd like to thank everyone who submitted patches and bug reports for
this release:

• Steven McDonald
• Ryan Egesdahl
• Piotr Dobrowolski
• Roberto Rodriguez Alcala
• Nathan O'Sullivan
• dpeddi
• WMP
• dipohl
• irvintim
• Marcus (localguru)