geoip2_c 0.3.4 → 0.4.1

data/ext/geoip2/libmaxminddb/Changes.md

@@ -1,277 +0,0 @@
-## 1.3.2 - 2018-01-17
-
-* Allocate memory for `MMDB_entry_data_list_s` structs in separate chunks
-  rather than one large chunk. This simplifies accessing memory in
-  `MMDB_get_entry_data_list()` and increases performance. It builds on the
-  changes in 1.3.0 and 1.3.1.
-* We no longer export `data_pool_*` symbols. These are internal functions
-  but we were previously exporting them. Pull request by Faidon Liambotis.
-  GitHub #162.
-* Build with POSIX.1-2008 by default if the system supports it. This allows
-  use of `open()` with `O_CLOEXEC`. We retain support for systems that
-  provide only POSIX.1-2001.
-* Open the database with the `O_CLOEXEC` flag if the system provides it.
-  This avoids cases where we could leak fds when called in multi-threaded
-  programs that `fork()` and `exec()`. Original report and PR by Brandon L
-  Black.
-* Added a test to ensure we export only intended symbols (e.g. MMDB_*).
-
-
-## 1.3.1 - 2017-11-24
-
-* Fix build problems related to `rpl_malloc()`. Pull request by Rainer
-  Gerhards. GitHub #152.
-* Fix a race to set and read data in a field on the `MMDB_s` struct
-  (`ipv4_start_node`). GitHub #153.
-* Fix cases of invalid memory access when using
-  `MMDB_get_entry_data_list()`. This was introduced in 1.3.0 and occurred
-  when performing large lookups. GitHub #153.
-
-
-## 1.3.0 - 2017-11-10
-
-* Perform fewer memory allocations in `MMDB_get_entry_data_list()`. This
-  significantly improves its performance. GitHub #147.
-* Fix `mmdblookup`'s build epoch reporting on some systems. Big endian
-  systems with a 32-bit `time_t` no longer show a database build date of
-  1970-01-01 00:00:00. Pull request by Rainer Jung. GitHub #143.
-
-
-## 1.2.1 - 2017-05-15
-
-* Use autoconf to check the system's endianness rather than trying to do this
-  with compiler-defined macros like `__BYTE_ORDER__`. Apparently this didn't
-  work properly on a Sparc system. GitHub #120.
-* Several compiler warnings on Visual C++ were fixed. Pull request by Marcel
-  Raad. GitHub #130.
-* Fix segmentation faults found in `MMDB_open()` using afl-fuzz. This
-  occurred on corrupt databases that had a data pointer large enough to
-  cause an integer overflow when doing bound checking. Reported by Ryan
-  Whitworth. GitHub #140.
-* Add --disable-tests option to `configure`. Pull request by Fabrice
-  Fontaine. GitHub #136.
-
-
-## 1.2.0 - 2016-03-23
-
-* Four additional fields were added to the end of the `MMDB_search_node_s`
-  struct returned by `MMDB_read_node`. These fields allow the user to iterate
-  through the search tree without making undocumented assumptions about how
-  this library works internally and without knowing the specific details of
-  the database format. GitHub #110.
-
-
-## 1.1.5 - 2016-03-20
-
-* Previously, reading a database with a pointer in the metadata would cause an
-  `MMDB_INVALID_METADATA_ERROR` to be returned. This was due to an invalid
-  offset being used when calculating the pointer. The `data_section` and
-  `metadata_section` fields now both point to the beginning of the data
-  section. Previously, `data_section` pointed to the beginning of the data
-  separator. This will not affect anyone using only documented fields from
-  `MMDB_s`.
-* `MMDB_lookup_sockaddr` will set `mmdb_error` to
-  `MMDB_IPV6_LOOKUP_IN_IPV4_DATABASE_ERROR` if an IPv6 `sockaddr` is looked up
-  in an IPv4-only database. Previously only `MMDB_lookup_string` would set
-  this error code.
-* When resolving an address, this library now relies on `getaddrinfo` to
-  determine the address family rather than trying to guess it itself.
-
-
-## 1.1.4 - 2016-01-06
-
-* Packaging fixes. The 1.1.3 tarball release contained a lot of extra junk in
-  the t/ directory.
-
-
-## 1.1.3 - 2016-01-05
-
-* Added several additional checks to make sure that we don't attempt to read
-  past the end of the databases's data section. Implemented by Tobias
-  Stoeckmann. GitHub #103.
-* When searching for the database metadata, there was a bug that caused the
-  code to think it had found valid metadata when none existed. In addition,
-  this could lead to an attempt to read past the end of the database
-  entirely. Finally, if there are multiple metadata markers in the database,
-  we treat the final one as the start of the metdata, instead of the first.
-  Implemented by Tobias Stoeckmann. GitHub #102.
-* Don't attempt to mmap a file that is too large to be mmapped on the
-  system. Implemented by Tobias Stoeckmann. GitHub #101.
-* Added a missing out of memory check when reading a file's
-  metadata. Implemented by Tobias Stoeckmann. GitHub #101.
-* Added several additional checks to make sure that we never attempt to
-  `malloc` more than `SIZE_MAX` memory, which would lead to integer
-  overflow. This could only happen with pathological databases. Implemented by
-  Tobias Stoeckmann. GitHub #101.
-
-
-## 1.1.2 - 2015-11-16
-
-* IMPORTANT: This release includes a number of important security fixes. Among
-  these fixes is improved validation of the database metadata. Unfortunately,
-  MaxMind GeoIP2 and GeoLite2 databases created earlier than January 28, 2014
-  had an invalid data type for the `record_size` in the metadata. Previously
-  these databases worked on little endian machines with libmaxminddb but did
-  not work on big endian machines. Due to increased safety checks when reading
-  the file, these databases will no longer work on any platform. If you are
-  using one of these databases, we recommend that you upgrade to the latest
-  GeoLite2 or GeoIP2 database
-* Added pkg-config support. If your system supports it, then running `make
-  install` now installs a `libmaxminddb.pc` file for pkgconfig. Implemented by
-  Jan Vcelak.
-* Several segmentation faults found with afl-fuzz were fixed. These were
-  caused by missing bounds checking and missing data type verification checks.
-* `MMDB_get_entry_data_list` will now fail on data structures with a depth
-  greater than 512 and data structures that are cyclic. This should not
-  affect any known MaxMind DB in production. All databases produced by
-  MaxMind have a depth of less than five.
-
-
-## 1.1.1 - 2015-07-22
-
-* Added `maxminddb-compat-util.h` as a source file to dist.
-
-
-## 1.1.0 - 2015-07-21
-
-* Previously, when there was an error in `MMDB_open()`, `errno` would
-  generally be overwritten during cleanup, preventing a useful value from
-  being returned to the caller. This was changed so that the `errno` value
-  from the function call that caused the error is restored before returning to
-  the caller. In particular, this is important for `MMDB_IO_ERROR` errors as
-  checking `errno` is often the only way to determine what actually failed.
-* If `mmap()` fails due to running out of memory space, an
-  `MMDB_OUT_OF_MEMORY_ERROR` is now returned from `MMDB_open` rather than an
-  `MMDB_IO_ERROR`.
-* On Windows, the `CreateFileMappingA()` handle was not properly closed if
-  opening the database succeeded. Fixed by Bly Hostetler. GitHub #75 & #76.
-* On Windows, we were not checking the return value of `CreateFileMappingA()`
-  properly for errors. Fixed by Bly Hotetler. GitHub #78.
-* Several warnings from Clang's scan-build were fixed. GitHub #86.
-* All headers are now installed in `$(includedir)`. GitHub #89.
-* We no longer install `maxminddb-compat-util.h`. This header was intended for
-  internal use only.
-
-
-## 1.0.4 - 2015-01-02
-
-* If you used a non-integer string as an array index when doing a lookup with
-  `MMDB_get_value()`, `MMDB_vget_value()`, or `MMDB_aget_value()`, the first
-  element of the array would be returned rather than an error. A
-  `MMDB_LOOKUP_PATH_DOES_NOT_MATCH_DATA_ERROR` error will now be returned.
-  GitHub #61.
-* If a number larger than `LONG_MAX` was used in the same functions,
-  `LONG_MAX` would have been used in the lookup. Now a
-  `MMDB_INVALID_LOOKUP_PATH_ERROR` error will be returned.
-* Visual Studio build files were added for unit tests and some compatibility
-  issues with the tests were fixed.
-* Visual Studio project was updated to use property pages. Patch by Andre.
-  GitHub #69.
-* A test failure in `t/compile_c++_t.pl` on new installs was fixed.
-
-
-## 1.0.3 - 2014-12-02
-
-* A memory and file handle leak on Win32 was fixed when getting the database
-  size fails. Patch by Federico G. Schwindt. GitHub PR #49.
-* Documentation fix. Federico G. Schwindt. GitHub PR #50.
-* Added Visual Studio build files and fixed incorrect CreateFileMappingA
-  usage. Patch by Andre. GitHub #52.
-* The includes for the Windows header files were made lowercase in order to
-  match the actual file names on case-sensitive file systems. GitHub PR #57.
-* Removed `realloc()` calls that caused warnings on Windows and generally
-  cleaned up memory allocation in `MMDB_vget_value()`. See relevant discussion
-  in GitHub #52.
-* Added an `extern "C" { ... }` wrapper to maxminddb.h when compiling with a
-  C++ compiler. GitHub #55.
-
-
-## 1.0.2 - 2014-09-22
-
-* Fixed a number of small issues found by Coverity.
-* When freeing the MMDB struct in `MMDB_close()` we make sure to set the
-  pointers to NULL after freeing the memory they point to. This makes it safe
-  to call `MMDB_close` more than once on the same `MMDB_s` struct
-  pointer. Before this change, calling this function twice on the same pointer
-  could cause the code to free memory that belonged to something else in the
-  process. Patch by Shuxin Yang. GitHub PR #41.
-
-
-## 1.0.1 - 2014-09-03
-
-* Added missing LICENSE and NOTICE files to distribution. No code changes.
-
-
-## 1.0.0 - 2014-09-02
-
-* Bumped version to 1.0.0. No code changes.
-
-
-## 0.5.6 - 2014-07-21
-
-* There was a leak in the `MMDB_open()` sub when it was called against a file
-  which did not contain any MMDB metadata. Reported by Federico
-  G. Schwindt. GitHub issue #36.
-* Fixed an error that occurred when passing AI_V4MAPPED to `getaddrinfo()` on
-  FreeBSD. Apparently this macro is defined but doesn't work the way we
-  expected it to on that platform.
-* Made sure to call `freeaddrinfo()` when a call to `getaddrinfo()` fails but
-  still allocated memory.
-* Fixed a segfault in the tests that occurred on FreeBSD if we passed a NULL
-  value to `freeaddrinfo()`.
-* Added a missing step to the README.md file for installing from our GitHub
-  repository. Patch by Yasith Fernando.
-* Added instructions for installing via Homebrew. Patch by Yasith Fernando.
-
-
-## 0.5.5 - 2014-03-11
-
-* The previous tarball failed to compile because it was missing the
-  src/maxminddb-compat-util.h file. Reported by Günter Grodotzki. GitHub issue
-  #18.
-
-
-## 0.5.4 - 2014-03-03
-
-* Added support for compiling in the MinGW environment. Patch by Michael
-  Eisendle.
-* Added const declarations to many spots in the public API. None of these
-  should require changes to existing code.
-* Various documentation improvements.
-* Changed the license to the Apache 2.0 license.
-
-
-## 0.5.3 - 2013-12-23
-
-* The internal value_for_key_as_uint16 method was returning a uint32_t instead
-  of a uint16_t. Reported by Robert Wells. GitHub issue #11.
-* The ip_version member of the MMDB_metadata_s struct was a uint8_t, even
-  though the docs and spec said it should be a uint16_t. Reported by Robert
-  Wells. GitHub issue #11.
-* The mmdblookup_t.pl test now reports that it needs IPC::Run3 to run (which
-  it always did, but it didn't tell you this). Patch by Elan Ruusamäe. GitHub
-  issue #10.
-
-
-## 0.5.2 - 2013-11-20
-
-* Running `make` from the tarball failed. This is now fixed.
-
-
-## 0.5.1 - 2013-11-20
-
-* Renamed MMDB_LOOKUP_PATH_DOES_NOT_MATCH_DATA define to
-  MMDB_LOOKUP_PATH_DOES_NOT_MATCH_DATA_ERROR for consistency. Fixes github
-  issue #5. Reported by Albert Strasheim.
-* Updated README.md to show git clone with --recursive flag so you get the
-  needed submodules. Fixes github issue #4. Reported by Ryan Peck.
-* Fixed some bugs with the MMDB_get_*value functions when navigating a data
-  structure that included pointers. Fixes github issue #3. Reported by
-  bagadon.
-* Fixed compilation problems on OSX and OpenBSD. We have tested this on OSX
-  and OpenBSD 5.4. Fixes github issue #6.
-* Removed some unneeded memory allocations and added const to many variable
-  declarations. Based on patches by Timo Teräs. Github issue #8.
-* Added a test that uses threads to check for thread safety issue in the
-  library.
-* Distro tarball now includes man pages, tests, and test data

data/ext/geoip2/libmaxminddb/LICENSE

@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

data/ext/geoip2/libmaxminddb/Makefile.am

@@ -1,41 +0,0 @@
-
-include_HEADERS = include/maxminddb.h
-
-nodist_include_HEADERS = include/maxminddb_config.h
-
-SUBDIRS = \
-  src     \
-  bin
-
-if TESTS
-SUBDIRS += \
-  t
-endif
-
-EXTRA_DIST = doc t Changes.md LICENSE NOTICE README.md projects/VS12 projects/VS12-tests
-dist-hook:
-	dev-bin/make-man-pages.pl $(distdir)
-	find $(distdir) -name '.git*' | xargs rm -fr
-
-safedist: clean dist
-	tmpdir="$${TMPDIR-/tmp}/safedist-$$$$" \
-	  && mkdir "$$tmpdir" \
-	  && tar -xvf $(distdir).tar.gz --directory "$$tmpdir" \
-	  && $(am__cd) "$$tmpdir/$(distdir)" \
-	  && ./configure \
-	  && make -j 4 check
-
-man1_MANS = man/man1/*.1
-
-man3_MANS = man/man3/*.3
-
-man/man1/*.1:
-	if [ ! -f man/man1/mmdblookup.1 ]; then mkdir -p man/man1 && touch man/man1/mmdblookup.1; fi
-
-man/man3/*.3:
-	if [ ! -f man/man3/libmaxminddb.3 ]; then mkdir -p man/man3 && touch man/man3/libmaxminddb.3; fi
-
-release:
-	dev-bin/make-release.sh
-
-.PHONY: man/man1/*.1 man/man3/*.3 release

data/ext/geoip2/libmaxminddb/NOTICE

@@ -1,13 +0,0 @@
-Copyright 2013-2014 MaxMind, Inc.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.

data/ext/geoip2/libmaxminddb/README.dev.md

@@ -1,69 +0,0 @@
-# Releasing this library
-
-We release by uploading the tarball to GitHub, uploading Ubuntu PPAs, and by
-updating the Homebrew recipe for this library.
-
-## Creating the release tarball
-You may want to refer to the section about prerequisites.
-
-* Check whether there are any open issues to fix while you're doing this.
-* Update `Changes.md` to include specify the new version, today's date, and
-  list relevant changes. Commit this.
-* Run `./dev-bin/release.sh` to update various files in the distro, our
-  GitHub pages, and creates a GitHub release with the tarball.
-* Check the release looks good on both GitHub and launchpad.net.
-
-## PPA
-
-In order to upload a PPA, you have to create a launchpad.net account and
-register a GPG key with that account. You also need to be added to the MaxMind
-team. Ask in the dev channel for someone to add you. See
-https://help.launchpad.net/Packaging/PPA for more details.
-
-The PPA release script is at `dev-bin/ppa-release.sh`. Running it should
-guide you though the release, although it may require some changes to run on
-configurations different than Greg's machine.
-
-Check whether any new Ubuntu versions need to be listed in this script
-before running it.
-
-You should run it from `master`.
-
-## Homebrew
-
-* Go to https://github.com/Homebrew/homebrew-core/edit/master/Formula/libmaxminddb.rb
-* Edit the file to update the url and sha256. You can get the sha256 for the
-  tarball with the `sha256sum` command line utility.
-* Make a commit with the summary `libmaxminddb <VERSION>`
-* Submit a PR with the changes you just made.
-
-# Prerequisites for releasing
-
-* Required packages (Ubuntu Artful): vim git-core dput build-essential
-  autoconf automake libtool git-buildpackage libfile-slurp-perl pandoc
-  dirmngr libfile-slurp-tiny-perl libdatetime-perl debhelper dh-autoreconf
-  libipc-run3-perl libtest-output-perl devscripts
-* Install [hub](https://github.com/github/hub/releases). (Using `./install`
-  from the tarball is fine)
-* GitHub ssh key (e.g. in `~/.ssh/id_rsa`)
-* Git config (e.g. `~/.gitconfig`)
-* Import your GPG secret key (or create one if you don't have a suitable
-  one)
-  * `gpg --import /path/to/key`
-  * `gpg --edit-key KEYID` and trust it ultimately
-  * Ensure it shows with `gpg --list-secret-keys`
-* You need to be invited to the launchpad.net MaxMind organization on your
-  launchpad.net account.
-* You need your GPG key listed on your launchpad.net account
-  * You can add it in the web interface. It wants the output of
-    `gpg --fingerprint`.
-  * Part of the instructions involve having your key published on the
-    Ubuntu keyserver:
-    `gpg --keyserver keyserver.ubuntu.com --send-keys KEYID`
-  * You'll get an email with an encrypted payload that you need to decrypt
-    and follow the link to confirm it.
-* Ensure `dch` knows your name and email. Refer to its man page for how to
-  tell it this. One way is to set the `DEBFULLNAME` and `DEBEMAIL`
-  environment variables. These should match your GPG key's name and email
-  exactly. This is what gets used in the Debian changelog as well as
-  defines what GPG key to use.