geoip tests: move download URL to S3, update region code mapping stuff
geoip tests: use softlinks instead of copies
Fix segfault/assertfail due to bad GeoIP database (Issue #28)
Make regression testsuite more tolerant of timing issues

(Should also be faster on average in the slow cases)
Fix GeoIP database magic marker/type parsing

The GeoIP database has a magic marker of 0xFFFFFF, followed by one byte
indicating the database type (country/city, IPv4/IPv6). This sequence
can appear at the end or nearly at the end, followed by some other
garbage.

The code is supposed to start at the end, then move up one byte at a
time until it finds the magic, then move forward three bytes (magic
length) to read the type.

The current code moved backwards 4 bytes at a time, which isn't not
according to the de facto spec (libGeoIP). Presumably, this happened
because of an oversight while inspecting MaxMind's code: libGeoIP does
"lseek(fno, -3, SEEK_END);" followed by a "read(fno, delim, 3);"
eventually followed by a "lseek(fno, -4l, SEEK_CUR);". My guess is that
the reverse engineering missed the fact that read() actually seeks
forward, and hence reading 3 bytes and seeking -4 actually seeks -1 from
the original position.

Note that the databases as shipped by MaxMind contain exactly 3 bytes
after the database type, which just happened to make the current buggy
code work(!). Debian actually recreates the binary databases from the
"source" (CSV) with a home-made converter program which places the
magic/type being at the end of the file, something which is valid and
accepted by libGeoIP.

This addresses issue #28.
Merge pull request #28 from paravoid/issues/28

Segfault while reading GeoIPv6.dat
silence ln warnings on libgdmaps test re-execution
Fix test output stuff under automake 1.13+

Basically, switched from using the automake testrunner back to
  using a check-local rule.  This is due to compatibility issues
  between the new parallel-tests default in automake 1.13 and
  Debian's automake 1.11.6 not having the newer "serial-tests"
  option.

http://lists.gnu.org/archive/html/automake/2013-01/msg00051.html
copyright fixups
update to AUTHORS file (probably still incomplete)
speling fixs
Fix up identifiers that start with _[A-Z]

The C Standard reserves ^__.* and ^_[A-Z].* for the implementation
remove now-invalid nonnull constraint
Fix GeoIP database magic marker/type parsing

The GeoIP database has a magic marker of 0xFFFFFF, followed by one byte
indicating the database type (country/city, IPv4/IPv6). This sequence
can appear at the end or nearly at the end, followed by some other
garbage.

The code is supposed to start at the end, then move up one byte at a
time until it finds the magic, then move forward three bytes (magic
length) to read the type.

The current code moved backwards 4 bytes at a time, which isn't not
according to the de facto spec (libGeoIP). Presumably, this happened
because of an oversight while inspecting MaxMind's code: libGeoIP does
"lseek(fno, -3, SEEK_END);" followed by a "read(fno, delim, 3);"
eventually followed by a "lseek(fno, -4l, SEEK_CUR);". My guess is that
the reverse engineering missed the fact that read() actually seeks
forward, and hence reading 3 bytes and seeking -4 actually seeks -1 from
the original position.

Note that the databases as shipped by MaxMind contain exactly 3 bytes
after the database type, which just happened to make the current buggy
code work(!). Debian actually recreates the binary databases from the
"source" (CSV) with a home-made converter program which places the
magic/type being at the end of the file, something which is valid and
accepted by libGeoIP.

This addresses issue #28.

Conflicts:
	plugins/meta/libgdmaps/gdgeoip.c
Merge branch 'master' into dev

(This is the no-op merge of master->dev after cherry-picking
 Faidon's GeoIP fix from dev->master, which gets everything clean
 again for future dev<->master merges, I believe).
bring NEWS up to date for the next release...
Fix "make check-download", was broken by b0b6f82e
libgdmaps tests: check other databases for basic load (Issue #28)

Added new basic check for loading arbitrary GeoIP database
  pathnames, listed in the env var GDMAPS_GEOIP_TEST_LOAD.
  The files are simply loaded and queried while ignoring results,
  in hopes of catching stupid crashes against newer/different
  data than the fixed test set, when the tester has such data
  available.  If left unspecified, the test script will attempt
  defaulting to /usr/share/GeoIP/Geo*.dat if any such pathnames
  exist on the test host.

Example:
  GDMAPS_GEOIP_TEST_LOAD="/somedir/GeoIPTestDatav[46].dat" make check
minor README.md updates, mostly autogen.sh
1.7.6 version-bump stuff