<?xml version="1.0" encoding="UTF-8"?>
<otherdata xmlns="http://linux.duke.edu/metadata/other" packages="26">
<package pkgid="b0f5828c88eebe9846b781b0371be1f2c001388f69490362f4cc4d282fd9b5d4" name="ck" arch="src">
  <version epoch="0" ver="0.7.2" rel="150600.23.2"/>
  <changelog author="mrueckert@suse.de" date="1453723200">- initial package</changelog>
  <changelog author="mrueckert@suse.de" date="1453896000">- include license file
- explain why we don't use the configure macro</changelog>
  <changelog author="mpluskal@suse.com" date="1493208000">- Update to version 0.6.0</changelog>
  <changelog author="mpluskal@suse.com" date="1493208001">- Disable s390 building as it is not supported architecture</changelog>
  <changelog author="mpluskal@suse.com" date="1495022400">- Add _constraints to avoid test failures</changelog>
  <changelog author="mpluskal@suse.com" date="1524052800">- Small packaging changes</changelog>
  <changelog author="bwiedemann@suse.com" date="1560859200">- Add ck-fix-j1.patch to fix build with -j1</changelog>
  <changelog author="mpluskal@suse.com" date="1570622400">- Disable tests as they fail with gcc9</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1572350400">- Fix symbol name clash between glibc 2.30 and ck, add
  ck-fix-gettid-glibc-clash.patch
- Reenable tests again</changelog>
  <changelog author="rpm@fthiessen.de" date="1625400000">- Update to version 0.7.1
  * Add s390x support
  * ck_hs: add convenience hash function wrapper ck_hs_hash
  * ck_backoff: avoid dead store to ceiling
  * ck_ring: add two new utility functions for persistent rings
  * ck_sequence: reduce thread count to account for writer
  * ck_queue: fix logic inversion in CK_STAILQ_CONCAT
  * ck_epoch: allow record sharing and reentrancy for write-side operations
- Drop upstream merged patches: ck-fix-gettid-glibc-clash.patch,
  ck-fix-j1.patch</changelog>
  <changelog author="mpluskal@suse.com" date="1722340800">- Update to version 0.7.2:
  * This release adds support for riscv, as provided by Mitchell Horne, as well a miscellaneous bug fixes and improvments
- Enable building for all architectures</changelog>
  <changelog author="bwiedemann@suse.com" date="1747828800">- avoid using %jobs (boo#1237231)</changelog>
</package>
<package pkgid="126542b34718ceb14419c53cc4b44f7d662663745c9031b934f767a1f93294bd" name="ck-devel" arch="aarch64">
  <version epoch="0" ver="0.7.2" rel="150600.23.2"/>
  <changelog author="mrueckert@suse.de" date="1453723200">- initial package</changelog>
  <changelog author="mrueckert@suse.de" date="1453896000">- include license file
- explain why we don't use the configure macro</changelog>
  <changelog author="mpluskal@suse.com" date="1493208000">- Update to version 0.6.0</changelog>
  <changelog author="mpluskal@suse.com" date="1493208001">- Disable s390 building as it is not supported architecture</changelog>
  <changelog author="mpluskal@suse.com" date="1495022400">- Add _constraints to avoid test failures</changelog>
  <changelog author="mpluskal@suse.com" date="1524052800">- Small packaging changes</changelog>
  <changelog author="bwiedemann@suse.com" date="1560859200">- Add ck-fix-j1.patch to fix build with -j1</changelog>
  <changelog author="mpluskal@suse.com" date="1570622400">- Disable tests as they fail with gcc9</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1572350400">- Fix symbol name clash between glibc 2.30 and ck, add
  ck-fix-gettid-glibc-clash.patch
- Reenable tests again</changelog>
  <changelog author="rpm@fthiessen.de" date="1625400000">- Update to version 0.7.1
  * Add s390x support
  * ck_hs: add convenience hash function wrapper ck_hs_hash
  * ck_backoff: avoid dead store to ceiling
  * ck_ring: add two new utility functions for persistent rings
  * ck_sequence: reduce thread count to account for writer
  * ck_queue: fix logic inversion in CK_STAILQ_CONCAT
  * ck_epoch: allow record sharing and reentrancy for write-side operations
- Drop upstream merged patches: ck-fix-gettid-glibc-clash.patch,
  ck-fix-j1.patch</changelog>
  <changelog author="mpluskal@suse.com" date="1722340800">- Update to version 0.7.2:
  * This release adds support for riscv, as provided by Mitchell Horne, as well a miscellaneous bug fixes and improvments
- Enable building for all architectures</changelog>
  <changelog author="bwiedemann@suse.com" date="1747828800">- avoid using %jobs (boo#1237231)</changelog>
</package>
<package pkgid="82c496542f796964b3d775edf25f3112bb83a5cf961b5413adbfefb3ac0f44e5" name="ck-devel" arch="x86_64">
  <version epoch="0" ver="0.7.2" rel="150600.23.2"/>
  <changelog author="mrueckert@suse.de" date="1453723200">- initial package</changelog>
  <changelog author="mrueckert@suse.de" date="1453896000">- include license file
- explain why we don't use the configure macro</changelog>
  <changelog author="mpluskal@suse.com" date="1493208000">- Update to version 0.6.0</changelog>
  <changelog author="mpluskal@suse.com" date="1493208001">- Disable s390 building as it is not supported architecture</changelog>
  <changelog author="mpluskal@suse.com" date="1495022400">- Add _constraints to avoid test failures</changelog>
  <changelog author="mpluskal@suse.com" date="1524052800">- Small packaging changes</changelog>
  <changelog author="bwiedemann@suse.com" date="1560859200">- Add ck-fix-j1.patch to fix build with -j1</changelog>
  <changelog author="mpluskal@suse.com" date="1570622400">- Disable tests as they fail with gcc9</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1572350400">- Fix symbol name clash between glibc 2.30 and ck, add
  ck-fix-gettid-glibc-clash.patch
- Reenable tests again</changelog>
  <changelog author="rpm@fthiessen.de" date="1625400000">- Update to version 0.7.1
  * Add s390x support
  * ck_hs: add convenience hash function wrapper ck_hs_hash
  * ck_backoff: avoid dead store to ceiling
  * ck_ring: add two new utility functions for persistent rings
  * ck_sequence: reduce thread count to account for writer
  * ck_queue: fix logic inversion in CK_STAILQ_CONCAT
  * ck_epoch: allow record sharing and reentrancy for write-side operations
- Drop upstream merged patches: ck-fix-gettid-glibc-clash.patch,
  ck-fix-j1.patch</changelog>
  <changelog author="mpluskal@suse.com" date="1722340800">- Update to version 0.7.2:
  * This release adds support for riscv, as provided by Mitchell Horne, as well a miscellaneous bug fixes and improvments
- Enable building for all architectures</changelog>
  <changelog author="bwiedemann@suse.com" date="1747828800">- avoid using %jobs (boo#1237231)</changelog>
</package>
<package pkgid="33f50ae50255615da3324d9cc6132e8fc4fae35ee98aaa1aff31e7c80775a3ee" name="libck0" arch="aarch64">
  <version epoch="0" ver="0.7.2" rel="150600.23.2"/>
  <changelog author="mrueckert@suse.de" date="1453723200">- initial package</changelog>
  <changelog author="mrueckert@suse.de" date="1453896000">- include license file
- explain why we don't use the configure macro</changelog>
  <changelog author="mpluskal@suse.com" date="1493208000">- Update to version 0.6.0</changelog>
  <changelog author="mpluskal@suse.com" date="1493208001">- Disable s390 building as it is not supported architecture</changelog>
  <changelog author="mpluskal@suse.com" date="1495022400">- Add _constraints to avoid test failures</changelog>
  <changelog author="mpluskal@suse.com" date="1524052800">- Small packaging changes</changelog>
  <changelog author="bwiedemann@suse.com" date="1560859200">- Add ck-fix-j1.patch to fix build with -j1</changelog>
  <changelog author="mpluskal@suse.com" date="1570622400">- Disable tests as they fail with gcc9</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1572350400">- Fix symbol name clash between glibc 2.30 and ck, add
  ck-fix-gettid-glibc-clash.patch
- Reenable tests again</changelog>
  <changelog author="rpm@fthiessen.de" date="1625400000">- Update to version 0.7.1
  * Add s390x support
  * ck_hs: add convenience hash function wrapper ck_hs_hash
  * ck_backoff: avoid dead store to ceiling
  * ck_ring: add two new utility functions for persistent rings
  * ck_sequence: reduce thread count to account for writer
  * ck_queue: fix logic inversion in CK_STAILQ_CONCAT
  * ck_epoch: allow record sharing and reentrancy for write-side operations
- Drop upstream merged patches: ck-fix-gettid-glibc-clash.patch,
  ck-fix-j1.patch</changelog>
  <changelog author="mpluskal@suse.com" date="1722340800">- Update to version 0.7.2:
  * This release adds support for riscv, as provided by Mitchell Horne, as well a miscellaneous bug fixes and improvments
- Enable building for all architectures</changelog>
  <changelog author="bwiedemann@suse.com" date="1747828800">- avoid using %jobs (boo#1237231)</changelog>
</package>
<package pkgid="a255c4bd0cbf5468e53a87a24424882e319235fdfbc461d08ad807a7d46543b5" name="libck0" arch="x86_64">
  <version epoch="0" ver="0.7.2" rel="150600.23.2"/>
  <changelog author="mrueckert@suse.de" date="1453723200">- initial package</changelog>
  <changelog author="mrueckert@suse.de" date="1453896000">- include license file
- explain why we don't use the configure macro</changelog>
  <changelog author="mpluskal@suse.com" date="1493208000">- Update to version 0.6.0</changelog>
  <changelog author="mpluskal@suse.com" date="1493208001">- Disable s390 building as it is not supported architecture</changelog>
  <changelog author="mpluskal@suse.com" date="1495022400">- Add _constraints to avoid test failures</changelog>
  <changelog author="mpluskal@suse.com" date="1524052800">- Small packaging changes</changelog>
  <changelog author="bwiedemann@suse.com" date="1560859200">- Add ck-fix-j1.patch to fix build with -j1</changelog>
  <changelog author="mpluskal@suse.com" date="1570622400">- Disable tests as they fail with gcc9</changelog>
  <changelog author="stefan.bruens@rwth-aachen.de" date="1572350400">- Fix symbol name clash between glibc 2.30 and ck, add
  ck-fix-gettid-glibc-clash.patch
- Reenable tests again</changelog>
  <changelog author="rpm@fthiessen.de" date="1625400000">- Update to version 0.7.1
  * Add s390x support
  * ck_hs: add convenience hash function wrapper ck_hs_hash
  * ck_backoff: avoid dead store to ceiling
  * ck_ring: add two new utility functions for persistent rings
  * ck_sequence: reduce thread count to account for writer
  * ck_queue: fix logic inversion in CK_STAILQ_CONCAT
  * ck_epoch: allow record sharing and reentrancy for write-side operations
- Drop upstream merged patches: ck-fix-gettid-glibc-clash.patch,
  ck-fix-j1.patch</changelog>
  <changelog author="mpluskal@suse.com" date="1722340800">- Update to version 0.7.2:
  * This release adds support for riscv, as provided by Mitchell Horne, as well a miscellaneous bug fixes and improvments
- Enable building for all architectures</changelog>
  <changelog author="bwiedemann@suse.com" date="1747828800">- avoid using %jobs (boo#1237231)</changelog>
</package>
<package pkgid="f3b60cac96121a6b4225c9d364ef70172978d502c8c51f20779001571f10a8b4" name="liblz4-1" arch="aarch64">
  <version epoch="0" ver="1.10.0" rel="150600.54.3"/>
  <changelog author="jengelh@inai.de" date="1417176000">- Update to version 1.4+svn124
  * LZ4F_compressBound() may be called with NULL preferencesPtr
  * LZ4_loadDict now returns the dictionary size instead of 1
  on success
- Add lz4-soversion.diff to address ABI changes</changelog>
  <changelog author="jengelh@inai.de" date="1459598400">- Update to new upstream release 131 (library 1.7) (boo#973735)
  * slightly improved decoding speed
  * lz4frame API is included in liblz4
  * new -m command line option to compress multiple files
  * new lz4 and lz4hc compression API (old one retained)</changelog>
  <changelog author="dimstar@opensuse.org" date="1484568000">- Add baselibs.conf: provide liblz4-1_7 as -32bit compatibility
  package, required by systemd-32bit.</changelog>
  <changelog author="jengelh@inai.de" date="1499256000">- Update to new upstrema release 1.7.5 (2017-01-03)
  * back to the old version scheme
  * lz4hc: new compression levels 10-12
- Remove lz4-soversion.diff (not needed),
  lz4-killdate.diff (no longer needed)</changelog>
  <changelog author="ddiss@suse.com" date="1502798400">- Use official upstream repository; (boo#1053910)</changelog>
  <changelog author="jengelh@inai.de" date="1503662400">- Update to new upstream release 1.8.0
  * cli: fix: do not modify /dev/null's permissions.
  * cli: added POSIX separator "--" for specifying that all
    following arguments are non-options.
  * cli: restored -BX command enabling block checksum.
  * API: added LZ4_compress_HC_destSize() and
    LZ4F_resetDecompressionContext().
  * API: lz4frame: negative compression levels trigger fast
    acceleration.
  * API: lz4frame: ability to control block checksum and
    dictionary ID.
  * API: fix: expose obsolete decoding functions
  * API: experimental: lz4frame_static.h:
    new dictionary compression API
  * doc: Updated LZ4 Frame format to v1.6.0, restoring
    Dictionary ID field in header.
- Add lz-export.diff</changelog>
  <changelog author="avindra@opensuse.org" date="1518004800">- Update to new upstream release 1.8.1.2
  * Most visible new feature is support for dictionary compression
  * Support is now more formally added on the API side within
    lib/lz4frame_static.h. It's early days, and this new API is
    tagged "experimental" for the time being.
  * Support is also added in the command line utility lz4, using
    the new command -D. The behavior of this command is identical
    to zstd, should you be already familiar.
  * lz4 doesn't specify how to build a dictionary. All it says is
    that it can be any file up to 64 KB.
  * This approach is compatible with zstd dictionary builder, which
    can be instructed to create a 64 KB dictionary.
  * Improved performance at ultra settings (levels 10+).
  * These levels receive a new code, called optimal parser,
    available in lib/lz4_opt.h.
  * New parser uses less memory (from 384KB to 256KB), performs
    faster, compresses a little bit better (not much, as it was
    already close to theoretical limit), and resists pathological
    patterns which could destroy performance.
  * New parser is directly compatible with lower compression levels,
    which brings additional benefits:
    + Compatibility with LZ4_*_destSize() variant, which reverses
    the logic by trying to fit as much data as possible into a
    predefined limited size buffer.
    + Compatibility with Dictionary compression, as it uses the
    same tables as regular HC mode
  * In the future, this compatibility will also allow dynamic change
    of compression level.
  * Small set of bug fixes and improvements:
    + perf : faster and stronger ultra modes (levels 10+)
    + perf : slightly faster compression and decompression speed
    + perf : fix bad degenerative case
    + fix : decompression failed when using a combination of
    extDict + low memory address
    + cli : support for dictionary compression (-D)
    + cli : fix : lz4 -d --rm preserves timestamp
    + cli : fix : do not modify /dev/null permission as root
    + api : _destSize() variant supported for all compression
    levels
- partial cleanup with spec-cleaner
- drop lz4-use-shlib.diff, breaks build
- misc spec cleanups
  - remove Makefile fix
  - build and install separately
  - New URL</changelog>
  <changelog author="astieger@suse.com" date="1530187200">- lz4 1.8.2:
  * speed inprovemtns for compression and decompression
  * fix compression compatible with low memory addresses
  * fix decompression segfault when provided with NULL input
  * cli: new command --favor-decSpeed
  * cli: benchmark mode more accurate for small inputs</changelog>
  <changelog author="astieger@suse.com" date="1539345600">- lz4 1.8.3:
  * minor decompression speed improvement (~+2%) with gcc
  * fix corruption in v1.8.2 at level 9 for files &gt; 64KB under
    rare conditions
  * Add new command --fast
  * api: LZ4_decompress_safe_partial() now decodes exactly the
    number of bytes requested</changelog>
  <changelog author="jengelh@inai.de" date="1559822400">- Update to new upstream release 1.9.1
  * Decompression speed was improved by about 12% (x86/x64).
  * New option `lz4 --list` to inspect the block type, checksum
    information, compressed and decompressed sizes (if present). The
    command is limited to single-frame files for the time being.</changelog>
  <changelog author="pgajdos@suse.com" date="1571140800">- version update to 1.9.2
  * decompression functions were reading a few bytes beyond input size
  * api: lz4frame initializers compatibility with c++, reported by @degski
  * cli : added command --list, based on a patch by @gabrielstedman
  * fixes CVE-2019-17543 [bsc#1153936]</changelog>
  <changelog author="pgajdos@suse.com" date="1571227200">- enable testsuite
- verbose build</changelog>
  <changelog author="jengelh@inai.de" date="1605528000">- Update to release 1.9.3
  * api: LZ4_decompress_safe_partial() now supports unknown
    compressed size
  * api: improved LZ4F_compressBound() with automatic flushing
  * cli: multiple files are compressed now using the legacy format</changelog>
  <changelog author="pgajdos@suse.com" date="1633348800">- version 1.9.3 fixes also CVE-2021-3520 [bsc#1185438]</changelog>
  <changelog author="jengelh@inai.de" date="1660651200">- Update to release 1.9.4
  * Decompression speed on high-end ARM64 platform is improved,
    by ~+20%.
  * For the specific scenario of data compressed with -BD4
    setting (small blocks, &lt;= 64 KB, linked) decompressed
    block-by-block into a flush buffer (like lz4 CLI does),
    decompression speed is improved ~+70%.
  * For compressed data employing the lz4frame format (native
    format of lz4 CLI), it's possible to ignore checksum
    validation during decompression, resulting in speed
    improvements of ~+40% . This capability is exposed at both
    CLI (see --no-crc) and library levels.</changelog>
  <changelog author="mpluskal@suse.com" date="1678276800">- Build AVX2 enabled hwcaps library for x86_64-v3</changelog>
  <changelog author="jengelh@inai.de" date="1721649600">- Update to release 1.10.0
  * Support for multithreading
  * Full support for dictionary compression
  * New compression level 2</changelog>
  <changelog author="code@bnavigator.de" date="1723636800">- Switch to cmake build system: Creates extra cmake modules for
  consuming projects</changelog>
</package>
<package pkgid="d9e3598b75085c956deefc93b7e72c1a5d252a7c356d60377b212c8dc2dcef00" name="liblz4-1" arch="x86_64">
  <version epoch="0" ver="1.10.0" rel="150600.54.3"/>
  <changelog author="jengelh@inai.de" date="1417176000">- Update to version 1.4+svn124
  * LZ4F_compressBound() may be called with NULL preferencesPtr
  * LZ4_loadDict now returns the dictionary size instead of 1
  on success
- Add lz4-soversion.diff to address ABI changes</changelog>
  <changelog author="jengelh@inai.de" date="1459598400">- Update to new upstream release 131 (library 1.7) (boo#973735)
  * slightly improved decoding speed
  * lz4frame API is included in liblz4
  * new -m command line option to compress multiple files
  * new lz4 and lz4hc compression API (old one retained)</changelog>
  <changelog author="dimstar@opensuse.org" date="1484568000">- Add baselibs.conf: provide liblz4-1_7 as -32bit compatibility
  package, required by systemd-32bit.</changelog>
  <changelog author="jengelh@inai.de" date="1499256000">- Update to new upstrema release 1.7.5 (2017-01-03)
  * back to the old version scheme
  * lz4hc: new compression levels 10-12
- Remove lz4-soversion.diff (not needed),
  lz4-killdate.diff (no longer needed)</changelog>
  <changelog author="ddiss@suse.com" date="1502798400">- Use official upstream repository; (boo#1053910)</changelog>
  <changelog author="jengelh@inai.de" date="1503662400">- Update to new upstream release 1.8.0
  * cli: fix: do not modify /dev/null's permissions.
  * cli: added POSIX separator "--" for specifying that all
    following arguments are non-options.
  * cli: restored -BX command enabling block checksum.
  * API: added LZ4_compress_HC_destSize() and
    LZ4F_resetDecompressionContext().
  * API: lz4frame: negative compression levels trigger fast
    acceleration.
  * API: lz4frame: ability to control block checksum and
    dictionary ID.
  * API: fix: expose obsolete decoding functions
  * API: experimental: lz4frame_static.h:
    new dictionary compression API
  * doc: Updated LZ4 Frame format to v1.6.0, restoring
    Dictionary ID field in header.
- Add lz-export.diff</changelog>
  <changelog author="avindra@opensuse.org" date="1518004800">- Update to new upstream release 1.8.1.2
  * Most visible new feature is support for dictionary compression
  * Support is now more formally added on the API side within
    lib/lz4frame_static.h. It's early days, and this new API is
    tagged "experimental" for the time being.
  * Support is also added in the command line utility lz4, using
    the new command -D. The behavior of this command is identical
    to zstd, should you be already familiar.
  * lz4 doesn't specify how to build a dictionary. All it says is
    that it can be any file up to 64 KB.
  * This approach is compatible with zstd dictionary builder, which
    can be instructed to create a 64 KB dictionary.
  * Improved performance at ultra settings (levels 10+).
  * These levels receive a new code, called optimal parser,
    available in lib/lz4_opt.h.
  * New parser uses less memory (from 384KB to 256KB), performs
    faster, compresses a little bit better (not much, as it was
    already close to theoretical limit), and resists pathological
    patterns which could destroy performance.
  * New parser is directly compatible with lower compression levels,
    which brings additional benefits:
    + Compatibility with LZ4_*_destSize() variant, which reverses
    the logic by trying to fit as much data as possible into a
    predefined limited size buffer.
    + Compatibility with Dictionary compression, as it uses the
    same tables as regular HC mode
  * In the future, this compatibility will also allow dynamic change
    of compression level.
  * Small set of bug fixes and improvements:
    + perf : faster and stronger ultra modes (levels 10+)
    + perf : slightly faster compression and decompression speed
    + perf : fix bad degenerative case
    + fix : decompression failed when using a combination of
    extDict + low memory address
    + cli : support for dictionary compression (-D)
    + cli : fix : lz4 -d --rm preserves timestamp
    + cli : fix : do not modify /dev/null permission as root
    + api : _destSize() variant supported for all compression
    levels
- partial cleanup with spec-cleaner
- drop lz4-use-shlib.diff, breaks build
- misc spec cleanups
  - remove Makefile fix
  - build and install separately
  - New URL</changelog>
  <changelog author="astieger@suse.com" date="1530187200">- lz4 1.8.2:
  * speed inprovemtns for compression and decompression
  * fix compression compatible with low memory addresses
  * fix decompression segfault when provided with NULL input
  * cli: new command --favor-decSpeed
  * cli: benchmark mode more accurate for small inputs</changelog>
  <changelog author="astieger@suse.com" date="1539345600">- lz4 1.8.3:
  * minor decompression speed improvement (~+2%) with gcc
  * fix corruption in v1.8.2 at level 9 for files &gt; 64KB under
    rare conditions
  * Add new command --fast
  * api: LZ4_decompress_safe_partial() now decodes exactly the
    number of bytes requested</changelog>
  <changelog author="jengelh@inai.de" date="1559822400">- Update to new upstream release 1.9.1
  * Decompression speed was improved by about 12% (x86/x64).
  * New option `lz4 --list` to inspect the block type, checksum
    information, compressed and decompressed sizes (if present). The
    command is limited to single-frame files for the time being.</changelog>
  <changelog author="pgajdos@suse.com" date="1571140800">- version update to 1.9.2
  * decompression functions were reading a few bytes beyond input size
  * api: lz4frame initializers compatibility with c++, reported by @degski
  * cli : added command --list, based on a patch by @gabrielstedman
  * fixes CVE-2019-17543 [bsc#1153936]</changelog>
  <changelog author="pgajdos@suse.com" date="1571227200">- enable testsuite
- verbose build</changelog>
  <changelog author="jengelh@inai.de" date="1605528000">- Update to release 1.9.3
  * api: LZ4_decompress_safe_partial() now supports unknown
    compressed size
  * api: improved LZ4F_compressBound() with automatic flushing
  * cli: multiple files are compressed now using the legacy format</changelog>
  <changelog author="pgajdos@suse.com" date="1633348800">- version 1.9.3 fixes also CVE-2021-3520 [bsc#1185438]</changelog>
  <changelog author="jengelh@inai.de" date="1660651200">- Update to release 1.9.4
  * Decompression speed on high-end ARM64 platform is improved,
    by ~+20%.
  * For the specific scenario of data compressed with -BD4
    setting (small blocks, &lt;= 64 KB, linked) decompressed
    block-by-block into a flush buffer (like lz4 CLI does),
    decompression speed is improved ~+70%.
  * For compressed data employing the lz4frame format (native
    format of lz4 CLI), it's possible to ignore checksum
    validation during decompression, resulting in speed
    improvements of ~+40% . This capability is exposed at both
    CLI (see --no-crc) and library levels.</changelog>
  <changelog author="mpluskal@suse.com" date="1678276800">- Build AVX2 enabled hwcaps library for x86_64-v3</changelog>
  <changelog author="jengelh@inai.de" date="1721649600">- Update to release 1.10.0
  * Support for multithreading
  * Full support for dictionary compression
  * New compression level 2</changelog>
  <changelog author="code@bnavigator.de" date="1723636800">- Switch to cmake build system: Creates extra cmake modules for
  consuming projects</changelog>
</package>
<package pkgid="7d43c0abed92af217655a583dc3a642006bbf2def620c93113d83099da79477a" name="liblz4-1-64bit" arch="aarch64_ilp32">
  <version epoch="0" ver="1.10.0" rel="150600.54.3"/>
  <changelog author="jengelh@inai.de" date="1417176000">- Update to version 1.4+svn124
  * LZ4F_compressBound() may be called with NULL preferencesPtr
  * LZ4_loadDict now returns the dictionary size instead of 1
  on success
- Add lz4-soversion.diff to address ABI changes</changelog>
  <changelog author="jengelh@inai.de" date="1459598400">- Update to new upstream release 131 (library 1.7) (boo#973735)
  * slightly improved decoding speed
  * lz4frame API is included in liblz4
  * new -m command line option to compress multiple files
  * new lz4 and lz4hc compression API (old one retained)</changelog>
  <changelog author="dimstar@opensuse.org" date="1484568000">- Add baselibs.conf: provide liblz4-1_7 as -32bit compatibility
  package, required by systemd-32bit.</changelog>
  <changelog author="jengelh@inai.de" date="1499256000">- Update to new upstrema release 1.7.5 (2017-01-03)
  * back to the old version scheme
  * lz4hc: new compression levels 10-12
- Remove lz4-soversion.diff (not needed),
  lz4-killdate.diff (no longer needed)</changelog>
  <changelog author="ddiss@suse.com" date="1502798400">- Use official upstream repository; (boo#1053910)</changelog>
  <changelog author="jengelh@inai.de" date="1503662400">- Update to new upstream release 1.8.0
  * cli: fix: do not modify /dev/null's permissions.
  * cli: added POSIX separator "--" for specifying that all
    following arguments are non-options.
  * cli: restored -BX command enabling block checksum.
  * API: added LZ4_compress_HC_destSize() and
    LZ4F_resetDecompressionContext().
  * API: lz4frame: negative compression levels trigger fast
    acceleration.
  * API: lz4frame: ability to control block checksum and
    dictionary ID.
  * API: fix: expose obsolete decoding functions
  * API: experimental: lz4frame_static.h:
    new dictionary compression API
  * doc: Updated LZ4 Frame format to v1.6.0, restoring
    Dictionary ID field in header.
- Add lz-export.diff</changelog>
  <changelog author="avindra@opensuse.org" date="1518004800">- Update to new upstream release 1.8.1.2
  * Most visible new feature is support for dictionary compression
  * Support is now more formally added on the API side within
    lib/lz4frame_static.h. It's early days, and this new API is
    tagged "experimental" for the time being.
  * Support is also added in the command line utility lz4, using
    the new command -D. The behavior of this command is identical
    to zstd, should you be already familiar.
  * lz4 doesn't specify how to build a dictionary. All it says is
    that it can be any file up to 64 KB.
  * This approach is compatible with zstd dictionary builder, which
    can be instructed to create a 64 KB dictionary.
  * Improved performance at ultra settings (levels 10+).
  * These levels receive a new code, called optimal parser,
    available in lib/lz4_opt.h.
  * New parser uses less memory (from 384KB to 256KB), performs
    faster, compresses a little bit better (not much, as it was
    already close to theoretical limit), and resists pathological
    patterns which could destroy performance.
  * New parser is directly compatible with lower compression levels,
    which brings additional benefits:
    + Compatibility with LZ4_*_destSize() variant, which reverses
    the logic by trying to fit as much data as possible into a
    predefined limited size buffer.
    + Compatibility with Dictionary compression, as it uses the
    same tables as regular HC mode
  * In the future, this compatibility will also allow dynamic change
    of compression level.
  * Small set of bug fixes and improvements:
    + perf : faster and stronger ultra modes (levels 10+)
    + perf : slightly faster compression and decompression speed
    + perf : fix bad degenerative case
    + fix : decompression failed when using a combination of
    extDict + low memory address
    + cli : support for dictionary compression (-D)
    + cli : fix : lz4 -d --rm preserves timestamp
    + cli : fix : do not modify /dev/null permission as root
    + api : _destSize() variant supported for all compression
    levels
- partial cleanup with spec-cleaner
- drop lz4-use-shlib.diff, breaks build
- misc spec cleanups
  - remove Makefile fix
  - build and install separately
  - New URL</changelog>
  <changelog author="astieger@suse.com" date="1530187200">- lz4 1.8.2:
  * speed inprovemtns for compression and decompression
  * fix compression compatible with low memory addresses
  * fix decompression segfault when provided with NULL input
  * cli: new command --favor-decSpeed
  * cli: benchmark mode more accurate for small inputs</changelog>
  <changelog author="astieger@suse.com" date="1539345600">- lz4 1.8.3:
  * minor decompression speed improvement (~+2%) with gcc
  * fix corruption in v1.8.2 at level 9 for files &gt; 64KB under
    rare conditions
  * Add new command --fast
  * api: LZ4_decompress_safe_partial() now decodes exactly the
    number of bytes requested</changelog>
  <changelog author="jengelh@inai.de" date="1559822400">- Update to new upstream release 1.9.1
  * Decompression speed was improved by about 12% (x86/x64).
  * New option `lz4 --list` to inspect the block type, checksum
    information, compressed and decompressed sizes (if present). The
    command is limited to single-frame files for the time being.</changelog>
  <changelog author="pgajdos@suse.com" date="1571140800">- version update to 1.9.2
  * decompression functions were reading a few bytes beyond input size
  * api: lz4frame initializers compatibility with c++, reported by @degski
  * cli : added command --list, based on a patch by @gabrielstedman
  * fixes CVE-2019-17543 [bsc#1153936]</changelog>
  <changelog author="pgajdos@suse.com" date="1571227200">- enable testsuite
- verbose build</changelog>
  <changelog author="jengelh@inai.de" date="1605528000">- Update to release 1.9.3
  * api: LZ4_decompress_safe_partial() now supports unknown
    compressed size
  * api: improved LZ4F_compressBound() with automatic flushing
  * cli: multiple files are compressed now using the legacy format</changelog>
  <changelog author="pgajdos@suse.com" date="1633348800">- version 1.9.3 fixes also CVE-2021-3520 [bsc#1185438]</changelog>
  <changelog author="jengelh@inai.de" date="1660651200">- Update to release 1.9.4
  * Decompression speed on high-end ARM64 platform is improved,
    by ~+20%.
  * For the specific scenario of data compressed with -BD4
    setting (small blocks, &lt;= 64 KB, linked) decompressed
    block-by-block into a flush buffer (like lz4 CLI does),
    decompression speed is improved ~+70%.
  * For compressed data employing the lz4frame format (native
    format of lz4 CLI), it's possible to ignore checksum
    validation during decompression, resulting in speed
    improvements of ~+40% . This capability is exposed at both
    CLI (see --no-crc) and library levels.</changelog>
  <changelog author="mpluskal@suse.com" date="1678276800">- Build AVX2 enabled hwcaps library for x86_64-v3</changelog>
  <changelog author="jengelh@inai.de" date="1721649600">- Update to release 1.10.0
  * Support for multithreading
  * Full support for dictionary compression
  * New compression level 2</changelog>
  <changelog author="code@bnavigator.de" date="1723636800">- Switch to cmake build system: Creates extra cmake modules for
  consuming projects</changelog>
</package>
<package pkgid="3ef8517a2c4948742a0c34b50741235ba99fa7c3394593e1c3b5cd85a8679fb8" name="liblz4-devel" arch="aarch64">
  <version epoch="0" ver="1.10.0" rel="150600.54.3"/>
  <changelog author="jengelh@inai.de" date="1417176000">- Update to version 1.4+svn124
  * LZ4F_compressBound() may be called with NULL preferencesPtr
  * LZ4_loadDict now returns the dictionary size instead of 1
  on success
- Add lz4-soversion.diff to address ABI changes</changelog>
  <changelog author="jengelh@inai.de" date="1459598400">- Update to new upstream release 131 (library 1.7) (boo#973735)
  * slightly improved decoding speed
  * lz4frame API is included in liblz4
  * new -m command line option to compress multiple files
  * new lz4 and lz4hc compression API (old one retained)</changelog>
  <changelog author="dimstar@opensuse.org" date="1484568000">- Add baselibs.conf: provide liblz4-1_7 as -32bit compatibility
  package, required by systemd-32bit.</changelog>
  <changelog author="jengelh@inai.de" date="1499256000">- Update to new upstrema release 1.7.5 (2017-01-03)
  * back to the old version scheme
  * lz4hc: new compression levels 10-12
- Remove lz4-soversion.diff (not needed),
  lz4-killdate.diff (no longer needed)</changelog>
  <changelog author="ddiss@suse.com" date="1502798400">- Use official upstream repository; (boo#1053910)</changelog>
  <changelog author="jengelh@inai.de" date="1503662400">- Update to new upstream release 1.8.0
  * cli: fix: do not modify /dev/null's permissions.
  * cli: added POSIX separator "--" for specifying that all
    following arguments are non-options.
  * cli: restored -BX command enabling block checksum.
  * API: added LZ4_compress_HC_destSize() and
    LZ4F_resetDecompressionContext().
  * API: lz4frame: negative compression levels trigger fast
    acceleration.
  * API: lz4frame: ability to control block checksum and
    dictionary ID.
  * API: fix: expose obsolete decoding functions
  * API: experimental: lz4frame_static.h:
    new dictionary compression API
  * doc: Updated LZ4 Frame format to v1.6.0, restoring
    Dictionary ID field in header.
- Add lz-export.diff</changelog>
  <changelog author="avindra@opensuse.org" date="1518004800">- Update to new upstream release 1.8.1.2
  * Most visible new feature is support for dictionary compression
  * Support is now more formally added on the API side within
    lib/lz4frame_static.h. It's early days, and this new API is
    tagged "experimental" for the time being.
  * Support is also added in the command line utility lz4, using
    the new command -D. The behavior of this command is identical
    to zstd, should you be already familiar.
  * lz4 doesn't specify how to build a dictionary. All it says is
    that it can be any file up to 64 KB.
  * This approach is compatible with zstd dictionary builder, which
    can be instructed to create a 64 KB dictionary.
  * Improved performance at ultra settings (levels 10+).
  * These levels receive a new code, called optimal parser,
    available in lib/lz4_opt.h.
  * New parser uses less memory (from 384KB to 256KB), performs
    faster, compresses a little bit better (not much, as it was
    already close to theoretical limit), and resists pathological
    patterns which could destroy performance.
  * New parser is directly compatible with lower compression levels,
    which brings additional benefits:
    + Compatibility with LZ4_*_destSize() variant, which reverses
    the logic by trying to fit as much data as possible into a
    predefined limited size buffer.
    + Compatibility with Dictionary compression, as it uses the
    same tables as regular HC mode
  * In the future, this compatibility will also allow dynamic change
    of compression level.
  * Small set of bug fixes and improvements:
    + perf : faster and stronger ultra modes (levels 10+)
    + perf : slightly faster compression and decompression speed
    + perf : fix bad degenerative case
    + fix : decompression failed when using a combination of
    extDict + low memory address
    + cli : support for dictionary compression (-D)
    + cli : fix : lz4 -d --rm preserves timestamp
    + cli : fix : do not modify /dev/null permission as root
    + api : _destSize() variant supported for all compression
    levels
- partial cleanup with spec-cleaner
- drop lz4-use-shlib.diff, breaks build
- misc spec cleanups
  - remove Makefile fix
  - build and install separately
  - New URL</changelog>
  <changelog author="astieger@suse.com" date="1530187200">- lz4 1.8.2:
  * speed inprovemtns for compression and decompression
  * fix compression compatible with low memory addresses
  * fix decompression segfault when provided with NULL input
  * cli: new command --favor-decSpeed
  * cli: benchmark mode more accurate for small inputs</changelog>
  <changelog author="astieger@suse.com" date="1539345600">- lz4 1.8.3:
  * minor decompression speed improvement (~+2%) with gcc
  * fix corruption in v1.8.2 at level 9 for files &gt; 64KB under
    rare conditions
  * Add new command --fast
  * api: LZ4_decompress_safe_partial() now decodes exactly the
    number of bytes requested</changelog>
  <changelog author="jengelh@inai.de" date="1559822400">- Update to new upstream release 1.9.1
  * Decompression speed was improved by about 12% (x86/x64).
  * New option `lz4 --list` to inspect the block type, checksum
    information, compressed and decompressed sizes (if present). The
    command is limited to single-frame files for the time being.</changelog>
  <changelog author="pgajdos@suse.com" date="1571140800">- version update to 1.9.2
  * decompression functions were reading a few bytes beyond input size
  * api: lz4frame initializers compatibility with c++, reported by @degski
  * cli : added command --list, based on a patch by @gabrielstedman
  * fixes CVE-2019-17543 [bsc#1153936]</changelog>
  <changelog author="pgajdos@suse.com" date="1571227200">- enable testsuite
- verbose build</changelog>
  <changelog author="jengelh@inai.de" date="1605528000">- Update to release 1.9.3
  * api: LZ4_decompress_safe_partial() now supports unknown
    compressed size
  * api: improved LZ4F_compressBound() with automatic flushing
  * cli: multiple files are compressed now using the legacy format</changelog>
  <changelog author="pgajdos@suse.com" date="1633348800">- version 1.9.3 fixes also CVE-2021-3520 [bsc#1185438]</changelog>
  <changelog author="jengelh@inai.de" date="1660651200">- Update to release 1.9.4
  * Decompression speed on high-end ARM64 platform is improved,
    by ~+20%.
  * For the specific scenario of data compressed with -BD4
    setting (small blocks, &lt;= 64 KB, linked) decompressed
    block-by-block into a flush buffer (like lz4 CLI does),
    decompression speed is improved ~+70%.
  * For compressed data employing the lz4frame format (native
    format of lz4 CLI), it's possible to ignore checksum
    validation during decompression, resulting in speed
    improvements of ~+40% . This capability is exposed at both
    CLI (see --no-crc) and library levels.</changelog>
  <changelog author="mpluskal@suse.com" date="1678276800">- Build AVX2 enabled hwcaps library for x86_64-v3</changelog>
  <changelog author="jengelh@inai.de" date="1721649600">- Update to release 1.10.0
  * Support for multithreading
  * Full support for dictionary compression
  * New compression level 2</changelog>
  <changelog author="code@bnavigator.de" date="1723636800">- Switch to cmake build system: Creates extra cmake modules for
  consuming projects</changelog>
</package>
<package pkgid="8041f79b55bd9be29d0ebe1999a43ca97e0cded1f38d1729bf56244b74ea3539" name="liblz4-devel" arch="x86_64">
  <version epoch="0" ver="1.10.0" rel="150600.54.3"/>
  <changelog author="jengelh@inai.de" date="1417176000">- Update to version 1.4+svn124
  * LZ4F_compressBound() may be called with NULL preferencesPtr
  * LZ4_loadDict now returns the dictionary size instead of 1
  on success
- Add lz4-soversion.diff to address ABI changes</changelog>
  <changelog author="jengelh@inai.de" date="1459598400">- Update to new upstream release 131 (library 1.7) (boo#973735)
  * slightly improved decoding speed
  * lz4frame API is included in liblz4
  * new -m command line option to compress multiple files
  * new lz4 and lz4hc compression API (old one retained)</changelog>
  <changelog author="dimstar@opensuse.org" date="1484568000">- Add baselibs.conf: provide liblz4-1_7 as -32bit compatibility
  package, required by systemd-32bit.</changelog>
  <changelog author="jengelh@inai.de" date="1499256000">- Update to new upstrema release 1.7.5 (2017-01-03)
  * back to the old version scheme
  * lz4hc: new compression levels 10-12
- Remove lz4-soversion.diff (not needed),
  lz4-killdate.diff (no longer needed)</changelog>
  <changelog author="ddiss@suse.com" date="1502798400">- Use official upstream repository; (boo#1053910)</changelog>
  <changelog author="jengelh@inai.de" date="1503662400">- Update to new upstream release 1.8.0
  * cli: fix: do not modify /dev/null's permissions.
  * cli: added POSIX separator "--" for specifying that all
    following arguments are non-options.
  * cli: restored -BX command enabling block checksum.
  * API: added LZ4_compress_HC_destSize() and
    LZ4F_resetDecompressionContext().
  * API: lz4frame: negative compression levels trigger fast
    acceleration.
  * API: lz4frame: ability to control block checksum and
    dictionary ID.
  * API: fix: expose obsolete decoding functions
  * API: experimental: lz4frame_static.h:
    new dictionary compression API
  * doc: Updated LZ4 Frame format to v1.6.0, restoring
    Dictionary ID field in header.
- Add lz-export.diff</changelog>
  <changelog author="avindra@opensuse.org" date="1518004800">- Update to new upstream release 1.8.1.2
  * Most visible new feature is support for dictionary compression
  * Support is now more formally added on the API side within
    lib/lz4frame_static.h. It's early days, and this new API is
    tagged "experimental" for the time being.
  * Support is also added in the command line utility lz4, using
    the new command -D. The behavior of this command is identical
    to zstd, should you be already familiar.
  * lz4 doesn't specify how to build a dictionary. All it says is
    that it can be any file up to 64 KB.
  * This approach is compatible with zstd dictionary builder, which
    can be instructed to create a 64 KB dictionary.
  * Improved performance at ultra settings (levels 10+).
  * These levels receive a new code, called optimal parser,
    available in lib/lz4_opt.h.
  * New parser uses less memory (from 384KB to 256KB), performs
    faster, compresses a little bit better (not much, as it was
    already close to theoretical limit), and resists pathological
    patterns which could destroy performance.
  * New parser is directly compatible with lower compression levels,
    which brings additional benefits:
    + Compatibility with LZ4_*_destSize() variant, which reverses
    the logic by trying to fit as much data as possible into a
    predefined limited size buffer.
    + Compatibility with Dictionary compression, as it uses the
    same tables as regular HC mode
  * In the future, this compatibility will also allow dynamic change
    of compression level.
  * Small set of bug fixes and improvements:
    + perf : faster and stronger ultra modes (levels 10+)
    + perf : slightly faster compression and decompression speed
    + perf : fix bad degenerative case
    + fix : decompression failed when using a combination of
    extDict + low memory address
    + cli : support for dictionary compression (-D)
    + cli : fix : lz4 -d --rm preserves timestamp
    + cli : fix : do not modify /dev/null permission as root
    + api : _destSize() variant supported for all compression
    levels
- partial cleanup with spec-cleaner
- drop lz4-use-shlib.diff, breaks build
- misc spec cleanups
  - remove Makefile fix
  - build and install separately
  - New URL</changelog>
  <changelog author="astieger@suse.com" date="1530187200">- lz4 1.8.2:
  * speed inprovemtns for compression and decompression
  * fix compression compatible with low memory addresses
  * fix decompression segfault when provided with NULL input
  * cli: new command --favor-decSpeed
  * cli: benchmark mode more accurate for small inputs</changelog>
  <changelog author="astieger@suse.com" date="1539345600">- lz4 1.8.3:
  * minor decompression speed improvement (~+2%) with gcc
  * fix corruption in v1.8.2 at level 9 for files &gt; 64KB under
    rare conditions
  * Add new command --fast
  * api: LZ4_decompress_safe_partial() now decodes exactly the
    number of bytes requested</changelog>
  <changelog author="jengelh@inai.de" date="1559822400">- Update to new upstream release 1.9.1
  * Decompression speed was improved by about 12% (x86/x64).
  * New option `lz4 --list` to inspect the block type, checksum
    information, compressed and decompressed sizes (if present). The
    command is limited to single-frame files for the time being.</changelog>
  <changelog author="pgajdos@suse.com" date="1571140800">- version update to 1.9.2
  * decompression functions were reading a few bytes beyond input size
  * api: lz4frame initializers compatibility with c++, reported by @degski
  * cli : added command --list, based on a patch by @gabrielstedman
  * fixes CVE-2019-17543 [bsc#1153936]</changelog>
  <changelog author="pgajdos@suse.com" date="1571227200">- enable testsuite
- verbose build</changelog>
  <changelog author="jengelh@inai.de" date="1605528000">- Update to release 1.9.3
  * api: LZ4_decompress_safe_partial() now supports unknown
    compressed size
  * api: improved LZ4F_compressBound() with automatic flushing
  * cli: multiple files are compressed now using the legacy format</changelog>
  <changelog author="pgajdos@suse.com" date="1633348800">- version 1.9.3 fixes also CVE-2021-3520 [bsc#1185438]</changelog>
  <changelog author="jengelh@inai.de" date="1660651200">- Update to release 1.9.4
  * Decompression speed on high-end ARM64 platform is improved,
    by ~+20%.
  * For the specific scenario of data compressed with -BD4
    setting (small blocks, &lt;= 64 KB, linked) decompressed
    block-by-block into a flush buffer (like lz4 CLI does),
    decompression speed is improved ~+70%.
  * For compressed data employing the lz4frame format (native
    format of lz4 CLI), it's possible to ignore checksum
    validation during decompression, resulting in speed
    improvements of ~+40% . This capability is exposed at both
    CLI (see --no-crc) and library levels.</changelog>
  <changelog author="mpluskal@suse.com" date="1678276800">- Build AVX2 enabled hwcaps library for x86_64-v3</changelog>
  <changelog author="jengelh@inai.de" date="1721649600">- Update to release 1.10.0
  * Support for multithreading
  * Full support for dictionary compression
  * New compression level 2</changelog>
  <changelog author="code@bnavigator.de" date="1723636800">- Switch to cmake build system: Creates extra cmake modules for
  consuming projects</changelog>
</package>
<package pkgid="e9f8c8d0a3d1fa1a8596077b037cc5dceac37fbddbec25be6a6dc5f24993af18" name="libmaxminddb" arch="src">
  <version epoch="0" ver="1.13.3" rel="150600.30.1"/>
  <changelog author="p.drouand@gmail.com" date="1419163200">- Initial release (version 1.0.3)</changelog>
  <changelog author="p.drouand@gmail.com" date="1421841600">- Update to version 1.0.4
  * 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. GitHub #69.
  * A test failure in t/compile_c++_t.pl on new installs was fixed.</changelog>
  <changelog author="p.drouand@gmail.com" date="1437912000">- Update to version 1.1.1
  * Added `maxminddb-compat-util.h` as a source file to dist.
- Changes from version 1.1.0
  * 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 &amp; #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.</changelog>
  <changelog author="p.drouand@gmail.com" date="1447848000">- Update to version 1.1.2
  * 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.
  * Several segmentation faults found with afl-fuzz were fixed. These
    were caused by missing bounds checking and missing verification
    of data type.
    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.
- Add a build dependency to pkg-config</changelog>
  <changelog author="p.drouand@gmail.com" date="1460462400">- Update to version 1.2.0
  * 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 (https://github.com/maxmind/libmaxminddb/issues/110)
- Changes from version 1.1.5
  * 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.
- Changes from version 1.1.4
  * Packaging fixes. The 1.1.3 tarball release contained a lot of extra
    junk in the t/ directory.
- Changes from version 1.1.3
  * Added several additional checks to make sure that we don't attempt to read
    past the end of the databases's data section. GitHub #103
    (https://github.com/maxmind/libmaxminddb/pull/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. GitHub #102 (https://github.com/maxmind/libmaxminddb/pull/102)
  * Don't attempt to mmap a file that is too large to be mmapped on the system.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).
  * Added a missing out of memory check when reading a file's metadata.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/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.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1526558400">- Run tests
- Packaged LICENSE
- Update to version 1.3.2
  * 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.
    gh#maxmind/libmaxminddb#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_*).
- Update to version 1.3.1
  * Fix build problems related to rpl_malloc(). Pull request by Rainer
    Gerhards. gh#maxmind/libmaxminddb
  * Fix a race to set and read data in a field on the MMDB_s struct
    (ipv4_start_node). gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#153.
- Update to version 1.3.0
  * Perform fewer memory allocations in MMDB_get_entry_data_list(). This
    significantly improves its performance. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#143.
- Update to version 1.2.1
  * 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. gh#maxmind/libmaxminddb#120.
  * Several compiler warnings on Visual C++ were fixed. Pull request by Marcel
    Raad. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#140.
  * Add --disable-tests option to configure. Pull request by Fabrice
    Fontaine. gh#maxmind/libmaxminddb#136.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1572782400">- update to 1.4.2:
  * negative array index for MMDB_*get_value specifies the last element
  * Fix a memory leak when using custom databases without languages
    defined in the metadata
  * mmdblookup now displays the prefix length for the record when
    using the verbose flag</changelog>
  <changelog author="dimstar@opensuse.org" date="1574251200">- Add baselibs.conf: build libmaxminddb0-32bit, which is required
  by libdns1310-32bit (new dependency gained).</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1596801600">- update to 1.4.3:
  * Use of uninitialized memory in dump_entry_data_list() could have
    cause a heap buffer flow in mmdblookup [bsc#1175006]</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1610020800">- libmaxminddb 1.5.0:
  * build system changes for other platforms only</changelog>
  <changelog author="dmueller@suse.com" date="1614686400">- update to 1.5.2:
  * With `libmaxminddb` on Windows and `mmdblookup` generally, there were
    instances where the return value of `calloc` was not checked, which could
    lead to issues in low memory situations or when resource limits had been
    set.
  * The formatting of the manpages has been improved and the script that
    generates them now supports `lowdown` in addition to `pandoc`.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1619784000">- libmaxminddb 1.6.0:
  * CMake build system fixes, not in use in this package</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1664625600">- libmaxminddb 1.7.1:
  * FD_CLOEXEC is now set on platforms that do not support O_CLOEXEC
  * File size check now correctly compares the size to SSIZE_MAX
  * developer visible changes</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1699358400">- libmaxminddb 1.8.0:
  * PACKAGE_VERSION is now a private compile definition when
    building with CMake.
  * The feature test macro _POSIX_C_SOURCE is no longer set by
    maxminddb.h
  * assert() is no longer used outside test code</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1704888000">- libmaxminddb 1.9.1:
  * On very large databases, the calculation to determine the search
    tree size could overflow. This was fixed and several additional
    guards against overflows were added
  * build system tweaks</changelog>
  <changelog author="dmueller@suse.com" date="1721304000">- update to 1.10.0:
  * The reader can now lookup records on a database with a search
    tree that is greater than 4 gigabytes without sometimes
    returning erroneous results due to an integer overflow.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1739275200">- update to 1.12.2:
  * fix memory leaks
  * MMDB_get_entry_data_list() now always sets the passed
    entry_data_list parameter to either NULL or valid memory. This
    makes it safe for callers to use MMDB_free_entry_data_list() on
    it even in case of error.
  * more build system tweaks</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1774785600">- update to 1.13.3:
  * Fix validation of empty maps and arrays at the end of the
    metadata section
  * MMDB_open would incorrectly reject databases where a 0-element
    map or array was the last field in metadata
- includes changes from 1.13.2:
  * fixes for other platforms
- includes changes from 1.13.1:
  * No code changes
- includes changes from 1.13.0:
  * improved data validation
  * Fixes for integer overflow, undefined behavior, buffer overflow
    and other code correctness issues what could be triggered by
    large or malicously crafted database
  * Prevent stack overflow via unbounded recursion</changelog>
</package>
<package pkgid="b1675eb1e421afa6cf95571453310d91e23b6125119ea7a674fe7cbafd2d7639" name="libmaxminddb-devel" arch="aarch64">
  <version epoch="0" ver="1.13.3" rel="150600.30.1"/>
  <changelog author="p.drouand@gmail.com" date="1419163200">- Initial release (version 1.0.3)</changelog>
  <changelog author="p.drouand@gmail.com" date="1421841600">- Update to version 1.0.4
  * 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. GitHub #69.
  * A test failure in t/compile_c++_t.pl on new installs was fixed.</changelog>
  <changelog author="p.drouand@gmail.com" date="1437912000">- Update to version 1.1.1
  * Added `maxminddb-compat-util.h` as a source file to dist.
- Changes from version 1.1.0
  * 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 &amp; #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.</changelog>
  <changelog author="p.drouand@gmail.com" date="1447848000">- Update to version 1.1.2
  * 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.
  * Several segmentation faults found with afl-fuzz were fixed. These
    were caused by missing bounds checking and missing verification
    of data type.
    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.
- Add a build dependency to pkg-config</changelog>
  <changelog author="p.drouand@gmail.com" date="1460462400">- Update to version 1.2.0
  * 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 (https://github.com/maxmind/libmaxminddb/issues/110)
- Changes from version 1.1.5
  * 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.
- Changes from version 1.1.4
  * Packaging fixes. The 1.1.3 tarball release contained a lot of extra
    junk in the t/ directory.
- Changes from version 1.1.3
  * Added several additional checks to make sure that we don't attempt to read
    past the end of the databases's data section. GitHub #103
    (https://github.com/maxmind/libmaxminddb/pull/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. GitHub #102 (https://github.com/maxmind/libmaxminddb/pull/102)
  * Don't attempt to mmap a file that is too large to be mmapped on the system.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).
  * Added a missing out of memory check when reading a file's metadata.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/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.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1526558400">- Run tests
- Packaged LICENSE
- Update to version 1.3.2
  * 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.
    gh#maxmind/libmaxminddb#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_*).
- Update to version 1.3.1
  * Fix build problems related to rpl_malloc(). Pull request by Rainer
    Gerhards. gh#maxmind/libmaxminddb
  * Fix a race to set and read data in a field on the MMDB_s struct
    (ipv4_start_node). gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#153.
- Update to version 1.3.0
  * Perform fewer memory allocations in MMDB_get_entry_data_list(). This
    significantly improves its performance. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#143.
- Update to version 1.2.1
  * 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. gh#maxmind/libmaxminddb#120.
  * Several compiler warnings on Visual C++ were fixed. Pull request by Marcel
    Raad. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#140.
  * Add --disable-tests option to configure. Pull request by Fabrice
    Fontaine. gh#maxmind/libmaxminddb#136.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1572782400">- update to 1.4.2:
  * negative array index for MMDB_*get_value specifies the last element
  * Fix a memory leak when using custom databases without languages
    defined in the metadata
  * mmdblookup now displays the prefix length for the record when
    using the verbose flag</changelog>
  <changelog author="dimstar@opensuse.org" date="1574251200">- Add baselibs.conf: build libmaxminddb0-32bit, which is required
  by libdns1310-32bit (new dependency gained).</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1596801600">- update to 1.4.3:
  * Use of uninitialized memory in dump_entry_data_list() could have
    cause a heap buffer flow in mmdblookup [bsc#1175006]</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1610020800">- libmaxminddb 1.5.0:
  * build system changes for other platforms only</changelog>
  <changelog author="dmueller@suse.com" date="1614686400">- update to 1.5.2:
  * With `libmaxminddb` on Windows and `mmdblookup` generally, there were
    instances where the return value of `calloc` was not checked, which could
    lead to issues in low memory situations or when resource limits had been
    set.
  * The formatting of the manpages has been improved and the script that
    generates them now supports `lowdown` in addition to `pandoc`.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1619784000">- libmaxminddb 1.6.0:
  * CMake build system fixes, not in use in this package</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1664625600">- libmaxminddb 1.7.1:
  * FD_CLOEXEC is now set on platforms that do not support O_CLOEXEC
  * File size check now correctly compares the size to SSIZE_MAX
  * developer visible changes</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1699358400">- libmaxminddb 1.8.0:
  * PACKAGE_VERSION is now a private compile definition when
    building with CMake.
  * The feature test macro _POSIX_C_SOURCE is no longer set by
    maxminddb.h
  * assert() is no longer used outside test code</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1704888000">- libmaxminddb 1.9.1:
  * On very large databases, the calculation to determine the search
    tree size could overflow. This was fixed and several additional
    guards against overflows were added
  * build system tweaks</changelog>
  <changelog author="dmueller@suse.com" date="1721304000">- update to 1.10.0:
  * The reader can now lookup records on a database with a search
    tree that is greater than 4 gigabytes without sometimes
    returning erroneous results due to an integer overflow.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1739275200">- update to 1.12.2:
  * fix memory leaks
  * MMDB_get_entry_data_list() now always sets the passed
    entry_data_list parameter to either NULL or valid memory. This
    makes it safe for callers to use MMDB_free_entry_data_list() on
    it even in case of error.
  * more build system tweaks</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1774785600">- update to 1.13.3:
  * Fix validation of empty maps and arrays at the end of the
    metadata section
  * MMDB_open would incorrectly reject databases where a 0-element
    map or array was the last field in metadata
- includes changes from 1.13.2:
  * fixes for other platforms
- includes changes from 1.13.1:
  * No code changes
- includes changes from 1.13.0:
  * improved data validation
  * Fixes for integer overflow, undefined behavior, buffer overflow
    and other code correctness issues what could be triggered by
    large or malicously crafted database
  * Prevent stack overflow via unbounded recursion</changelog>
</package>
<package pkgid="c290a6fd1659761ace8d6b9b88832bfc11f523a9efa21d588a485fe32bb56dde" name="libmaxminddb-devel" arch="x86_64">
  <version epoch="0" ver="1.13.3" rel="150600.30.1"/>
  <changelog author="p.drouand@gmail.com" date="1419163200">- Initial release (version 1.0.3)</changelog>
  <changelog author="p.drouand@gmail.com" date="1421841600">- Update to version 1.0.4
  * 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. GitHub #69.
  * A test failure in t/compile_c++_t.pl on new installs was fixed.</changelog>
  <changelog author="p.drouand@gmail.com" date="1437912000">- Update to version 1.1.1
  * Added `maxminddb-compat-util.h` as a source file to dist.
- Changes from version 1.1.0
  * 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 &amp; #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.</changelog>
  <changelog author="p.drouand@gmail.com" date="1447848000">- Update to version 1.1.2
  * 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.
  * Several segmentation faults found with afl-fuzz were fixed. These
    were caused by missing bounds checking and missing verification
    of data type.
    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.
- Add a build dependency to pkg-config</changelog>
  <changelog author="p.drouand@gmail.com" date="1460462400">- Update to version 1.2.0
  * 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 (https://github.com/maxmind/libmaxminddb/issues/110)
- Changes from version 1.1.5
  * 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.
- Changes from version 1.1.4
  * Packaging fixes. The 1.1.3 tarball release contained a lot of extra
    junk in the t/ directory.
- Changes from version 1.1.3
  * Added several additional checks to make sure that we don't attempt to read
    past the end of the databases's data section. GitHub #103
    (https://github.com/maxmind/libmaxminddb/pull/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. GitHub #102 (https://github.com/maxmind/libmaxminddb/pull/102)
  * Don't attempt to mmap a file that is too large to be mmapped on the system.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).
  * Added a missing out of memory check when reading a file's metadata.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/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.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1526558400">- Run tests
- Packaged LICENSE
- Update to version 1.3.2
  * 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.
    gh#maxmind/libmaxminddb#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_*).
- Update to version 1.3.1
  * Fix build problems related to rpl_malloc(). Pull request by Rainer
    Gerhards. gh#maxmind/libmaxminddb
  * Fix a race to set and read data in a field on the MMDB_s struct
    (ipv4_start_node). gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#153.
- Update to version 1.3.0
  * Perform fewer memory allocations in MMDB_get_entry_data_list(). This
    significantly improves its performance. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#143.
- Update to version 1.2.1
  * 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. gh#maxmind/libmaxminddb#120.
  * Several compiler warnings on Visual C++ were fixed. Pull request by Marcel
    Raad. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#140.
  * Add --disable-tests option to configure. Pull request by Fabrice
    Fontaine. gh#maxmind/libmaxminddb#136.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1572782400">- update to 1.4.2:
  * negative array index for MMDB_*get_value specifies the last element
  * Fix a memory leak when using custom databases without languages
    defined in the metadata
  * mmdblookup now displays the prefix length for the record when
    using the verbose flag</changelog>
  <changelog author="dimstar@opensuse.org" date="1574251200">- Add baselibs.conf: build libmaxminddb0-32bit, which is required
  by libdns1310-32bit (new dependency gained).</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1596801600">- update to 1.4.3:
  * Use of uninitialized memory in dump_entry_data_list() could have
    cause a heap buffer flow in mmdblookup [bsc#1175006]</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1610020800">- libmaxminddb 1.5.0:
  * build system changes for other platforms only</changelog>
  <changelog author="dmueller@suse.com" date="1614686400">- update to 1.5.2:
  * With `libmaxminddb` on Windows and `mmdblookup` generally, there were
    instances where the return value of `calloc` was not checked, which could
    lead to issues in low memory situations or when resource limits had been
    set.
  * The formatting of the manpages has been improved and the script that
    generates them now supports `lowdown` in addition to `pandoc`.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1619784000">- libmaxminddb 1.6.0:
  * CMake build system fixes, not in use in this package</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1664625600">- libmaxminddb 1.7.1:
  * FD_CLOEXEC is now set on platforms that do not support O_CLOEXEC
  * File size check now correctly compares the size to SSIZE_MAX
  * developer visible changes</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1699358400">- libmaxminddb 1.8.0:
  * PACKAGE_VERSION is now a private compile definition when
    building with CMake.
  * The feature test macro _POSIX_C_SOURCE is no longer set by
    maxminddb.h
  * assert() is no longer used outside test code</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1704888000">- libmaxminddb 1.9.1:
  * On very large databases, the calculation to determine the search
    tree size could overflow. This was fixed and several additional
    guards against overflows were added
  * build system tweaks</changelog>
  <changelog author="dmueller@suse.com" date="1721304000">- update to 1.10.0:
  * The reader can now lookup records on a database with a search
    tree that is greater than 4 gigabytes without sometimes
    returning erroneous results due to an integer overflow.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1739275200">- update to 1.12.2:
  * fix memory leaks
  * MMDB_get_entry_data_list() now always sets the passed
    entry_data_list parameter to either NULL or valid memory. This
    makes it safe for callers to use MMDB_free_entry_data_list() on
    it even in case of error.
  * more build system tweaks</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1774785600">- update to 1.13.3:
  * Fix validation of empty maps and arrays at the end of the
    metadata section
  * MMDB_open would incorrectly reject databases where a 0-element
    map or array was the last field in metadata
- includes changes from 1.13.2:
  * fixes for other platforms
- includes changes from 1.13.1:
  * No code changes
- includes changes from 1.13.0:
  * improved data validation
  * Fixes for integer overflow, undefined behavior, buffer overflow
    and other code correctness issues what could be triggered by
    large or malicously crafted database
  * Prevent stack overflow via unbounded recursion</changelog>
</package>
<package pkgid="24483fa768c4a7dfa475f60a1c043828f4053ff6caf3a50491a352be61e32c13" name="libmaxminddb0" arch="aarch64">
  <version epoch="0" ver="1.13.3" rel="150600.30.1"/>
  <changelog author="p.drouand@gmail.com" date="1419163200">- Initial release (version 1.0.3)</changelog>
  <changelog author="p.drouand@gmail.com" date="1421841600">- Update to version 1.0.4
  * 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. GitHub #69.
  * A test failure in t/compile_c++_t.pl on new installs was fixed.</changelog>
  <changelog author="p.drouand@gmail.com" date="1437912000">- Update to version 1.1.1
  * Added `maxminddb-compat-util.h` as a source file to dist.
- Changes from version 1.1.0
  * 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 &amp; #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.</changelog>
  <changelog author="p.drouand@gmail.com" date="1447848000">- Update to version 1.1.2
  * 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.
  * Several segmentation faults found with afl-fuzz were fixed. These
    were caused by missing bounds checking and missing verification
    of data type.
    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.
- Add a build dependency to pkg-config</changelog>
  <changelog author="p.drouand@gmail.com" date="1460462400">- Update to version 1.2.0
  * 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 (https://github.com/maxmind/libmaxminddb/issues/110)
- Changes from version 1.1.5
  * 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.
- Changes from version 1.1.4
  * Packaging fixes. The 1.1.3 tarball release contained a lot of extra
    junk in the t/ directory.
- Changes from version 1.1.3
  * Added several additional checks to make sure that we don't attempt to read
    past the end of the databases's data section. GitHub #103
    (https://github.com/maxmind/libmaxminddb/pull/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. GitHub #102 (https://github.com/maxmind/libmaxminddb/pull/102)
  * Don't attempt to mmap a file that is too large to be mmapped on the system.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).
  * Added a missing out of memory check when reading a file's metadata.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/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.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1526558400">- Run tests
- Packaged LICENSE
- Update to version 1.3.2
  * 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.
    gh#maxmind/libmaxminddb#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_*).
- Update to version 1.3.1
  * Fix build problems related to rpl_malloc(). Pull request by Rainer
    Gerhards. gh#maxmind/libmaxminddb
  * Fix a race to set and read data in a field on the MMDB_s struct
    (ipv4_start_node). gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#153.
- Update to version 1.3.0
  * Perform fewer memory allocations in MMDB_get_entry_data_list(). This
    significantly improves its performance. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#143.
- Update to version 1.2.1
  * 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. gh#maxmind/libmaxminddb#120.
  * Several compiler warnings on Visual C++ were fixed. Pull request by Marcel
    Raad. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#140.
  * Add --disable-tests option to configure. Pull request by Fabrice
    Fontaine. gh#maxmind/libmaxminddb#136.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1572782400">- update to 1.4.2:
  * negative array index for MMDB_*get_value specifies the last element
  * Fix a memory leak when using custom databases without languages
    defined in the metadata
  * mmdblookup now displays the prefix length for the record when
    using the verbose flag</changelog>
  <changelog author="dimstar@opensuse.org" date="1574251200">- Add baselibs.conf: build libmaxminddb0-32bit, which is required
  by libdns1310-32bit (new dependency gained).</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1596801600">- update to 1.4.3:
  * Use of uninitialized memory in dump_entry_data_list() could have
    cause a heap buffer flow in mmdblookup [bsc#1175006]</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1610020800">- libmaxminddb 1.5.0:
  * build system changes for other platforms only</changelog>
  <changelog author="dmueller@suse.com" date="1614686400">- update to 1.5.2:
  * With `libmaxminddb` on Windows and `mmdblookup` generally, there were
    instances where the return value of `calloc` was not checked, which could
    lead to issues in low memory situations or when resource limits had been
    set.
  * The formatting of the manpages has been improved and the script that
    generates them now supports `lowdown` in addition to `pandoc`.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1619784000">- libmaxminddb 1.6.0:
  * CMake build system fixes, not in use in this package</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1664625600">- libmaxminddb 1.7.1:
  * FD_CLOEXEC is now set on platforms that do not support O_CLOEXEC
  * File size check now correctly compares the size to SSIZE_MAX
  * developer visible changes</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1699358400">- libmaxminddb 1.8.0:
  * PACKAGE_VERSION is now a private compile definition when
    building with CMake.
  * The feature test macro _POSIX_C_SOURCE is no longer set by
    maxminddb.h
  * assert() is no longer used outside test code</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1704888000">- libmaxminddb 1.9.1:
  * On very large databases, the calculation to determine the search
    tree size could overflow. This was fixed and several additional
    guards against overflows were added
  * build system tweaks</changelog>
  <changelog author="dmueller@suse.com" date="1721304000">- update to 1.10.0:
  * The reader can now lookup records on a database with a search
    tree that is greater than 4 gigabytes without sometimes
    returning erroneous results due to an integer overflow.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1739275200">- update to 1.12.2:
  * fix memory leaks
  * MMDB_get_entry_data_list() now always sets the passed
    entry_data_list parameter to either NULL or valid memory. This
    makes it safe for callers to use MMDB_free_entry_data_list() on
    it even in case of error.
  * more build system tweaks</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1774785600">- update to 1.13.3:
  * Fix validation of empty maps and arrays at the end of the
    metadata section
  * MMDB_open would incorrectly reject databases where a 0-element
    map or array was the last field in metadata
- includes changes from 1.13.2:
  * fixes for other platforms
- includes changes from 1.13.1:
  * No code changes
- includes changes from 1.13.0:
  * improved data validation
  * Fixes for integer overflow, undefined behavior, buffer overflow
    and other code correctness issues what could be triggered by
    large or malicously crafted database
  * Prevent stack overflow via unbounded recursion</changelog>
</package>
<package pkgid="10e52d13de03ff9f937de3a07fea62f55ec749fb21ab14c252a77d10bcff38c7" name="libmaxminddb0" arch="x86_64">
  <version epoch="0" ver="1.13.3" rel="150600.30.1"/>
  <changelog author="p.drouand@gmail.com" date="1419163200">- Initial release (version 1.0.3)</changelog>
  <changelog author="p.drouand@gmail.com" date="1421841600">- Update to version 1.0.4
  * 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. GitHub #69.
  * A test failure in t/compile_c++_t.pl on new installs was fixed.</changelog>
  <changelog author="p.drouand@gmail.com" date="1437912000">- Update to version 1.1.1
  * Added `maxminddb-compat-util.h` as a source file to dist.
- Changes from version 1.1.0
  * 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 &amp; #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.</changelog>
  <changelog author="p.drouand@gmail.com" date="1447848000">- Update to version 1.1.2
  * 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.
  * Several segmentation faults found with afl-fuzz were fixed. These
    were caused by missing bounds checking and missing verification
    of data type.
    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.
- Add a build dependency to pkg-config</changelog>
  <changelog author="p.drouand@gmail.com" date="1460462400">- Update to version 1.2.0
  * 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 (https://github.com/maxmind/libmaxminddb/issues/110)
- Changes from version 1.1.5
  * 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.
- Changes from version 1.1.4
  * Packaging fixes. The 1.1.3 tarball release contained a lot of extra
    junk in the t/ directory.
- Changes from version 1.1.3
  * Added several additional checks to make sure that we don't attempt to read
    past the end of the databases's data section. GitHub #103
    (https://github.com/maxmind/libmaxminddb/pull/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. GitHub #102 (https://github.com/maxmind/libmaxminddb/pull/102)
  * Don't attempt to mmap a file that is too large to be mmapped on the system.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).
  * Added a missing out of memory check when reading a file's metadata.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/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.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1526558400">- Run tests
- Packaged LICENSE
- Update to version 1.3.2
  * 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.
    gh#maxmind/libmaxminddb#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_*).
- Update to version 1.3.1
  * Fix build problems related to rpl_malloc(). Pull request by Rainer
    Gerhards. gh#maxmind/libmaxminddb
  * Fix a race to set and read data in a field on the MMDB_s struct
    (ipv4_start_node). gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#153.
- Update to version 1.3.0
  * Perform fewer memory allocations in MMDB_get_entry_data_list(). This
    significantly improves its performance. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#143.
- Update to version 1.2.1
  * 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. gh#maxmind/libmaxminddb#120.
  * Several compiler warnings on Visual C++ were fixed. Pull request by Marcel
    Raad. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#140.
  * Add --disable-tests option to configure. Pull request by Fabrice
    Fontaine. gh#maxmind/libmaxminddb#136.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1572782400">- update to 1.4.2:
  * negative array index for MMDB_*get_value specifies the last element
  * Fix a memory leak when using custom databases without languages
    defined in the metadata
  * mmdblookup now displays the prefix length for the record when
    using the verbose flag</changelog>
  <changelog author="dimstar@opensuse.org" date="1574251200">- Add baselibs.conf: build libmaxminddb0-32bit, which is required
  by libdns1310-32bit (new dependency gained).</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1596801600">- update to 1.4.3:
  * Use of uninitialized memory in dump_entry_data_list() could have
    cause a heap buffer flow in mmdblookup [bsc#1175006]</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1610020800">- libmaxminddb 1.5.0:
  * build system changes for other platforms only</changelog>
  <changelog author="dmueller@suse.com" date="1614686400">- update to 1.5.2:
  * With `libmaxminddb` on Windows and `mmdblookup` generally, there were
    instances where the return value of `calloc` was not checked, which could
    lead to issues in low memory situations or when resource limits had been
    set.
  * The formatting of the manpages has been improved and the script that
    generates them now supports `lowdown` in addition to `pandoc`.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1619784000">- libmaxminddb 1.6.0:
  * CMake build system fixes, not in use in this package</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1664625600">- libmaxminddb 1.7.1:
  * FD_CLOEXEC is now set on platforms that do not support O_CLOEXEC
  * File size check now correctly compares the size to SSIZE_MAX
  * developer visible changes</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1699358400">- libmaxminddb 1.8.0:
  * PACKAGE_VERSION is now a private compile definition when
    building with CMake.
  * The feature test macro _POSIX_C_SOURCE is no longer set by
    maxminddb.h
  * assert() is no longer used outside test code</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1704888000">- libmaxminddb 1.9.1:
  * On very large databases, the calculation to determine the search
    tree size could overflow. This was fixed and several additional
    guards against overflows were added
  * build system tweaks</changelog>
  <changelog author="dmueller@suse.com" date="1721304000">- update to 1.10.0:
  * The reader can now lookup records on a database with a search
    tree that is greater than 4 gigabytes without sometimes
    returning erroneous results due to an integer overflow.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1739275200">- update to 1.12.2:
  * fix memory leaks
  * MMDB_get_entry_data_list() now always sets the passed
    entry_data_list parameter to either NULL or valid memory. This
    makes it safe for callers to use MMDB_free_entry_data_list() on
    it even in case of error.
  * more build system tweaks</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1774785600">- update to 1.13.3:
  * Fix validation of empty maps and arrays at the end of the
    metadata section
  * MMDB_open would incorrectly reject databases where a 0-element
    map or array was the last field in metadata
- includes changes from 1.13.2:
  * fixes for other platforms
- includes changes from 1.13.1:
  * No code changes
- includes changes from 1.13.0:
  * improved data validation
  * Fixes for integer overflow, undefined behavior, buffer overflow
    and other code correctness issues what could be triggered by
    large or malicously crafted database
  * Prevent stack overflow via unbounded recursion</changelog>
</package>
<package pkgid="780b99f08805a3a7aaedec3cab7946306c18a449f584b786f003a2acc2d6d69c" name="libmaxminddb0-64bit" arch="aarch64_ilp32">
  <version epoch="0" ver="1.13.3" rel="150600.30.1"/>
  <changelog author="p.drouand@gmail.com" date="1419163200">- Initial release (version 1.0.3)</changelog>
  <changelog author="p.drouand@gmail.com" date="1421841600">- Update to version 1.0.4
  * 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. GitHub #69.
  * A test failure in t/compile_c++_t.pl on new installs was fixed.</changelog>
  <changelog author="p.drouand@gmail.com" date="1437912000">- Update to version 1.1.1
  * Added `maxminddb-compat-util.h` as a source file to dist.
- Changes from version 1.1.0
  * 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 &amp; #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.</changelog>
  <changelog author="p.drouand@gmail.com" date="1447848000">- Update to version 1.1.2
  * 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.
  * Several segmentation faults found with afl-fuzz were fixed. These
    were caused by missing bounds checking and missing verification
    of data type.
    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.
- Add a build dependency to pkg-config</changelog>
  <changelog author="p.drouand@gmail.com" date="1460462400">- Update to version 1.2.0
  * 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 (https://github.com/maxmind/libmaxminddb/issues/110)
- Changes from version 1.1.5
  * 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.
- Changes from version 1.1.4
  * Packaging fixes. The 1.1.3 tarball release contained a lot of extra
    junk in the t/ directory.
- Changes from version 1.1.3
  * Added several additional checks to make sure that we don't attempt to read
    past the end of the databases's data section. GitHub #103
    (https://github.com/maxmind/libmaxminddb/pull/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. GitHub #102 (https://github.com/maxmind/libmaxminddb/pull/102)
  * Don't attempt to mmap a file that is too large to be mmapped on the system.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).
  * Added a missing out of memory check when reading a file's metadata.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/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.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1526558400">- Run tests
- Packaged LICENSE
- Update to version 1.3.2
  * 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.
    gh#maxmind/libmaxminddb#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_*).
- Update to version 1.3.1
  * Fix build problems related to rpl_malloc(). Pull request by Rainer
    Gerhards. gh#maxmind/libmaxminddb
  * Fix a race to set and read data in a field on the MMDB_s struct
    (ipv4_start_node). gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#153.
- Update to version 1.3.0
  * Perform fewer memory allocations in MMDB_get_entry_data_list(). This
    significantly improves its performance. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#143.
- Update to version 1.2.1
  * 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. gh#maxmind/libmaxminddb#120.
  * Several compiler warnings on Visual C++ were fixed. Pull request by Marcel
    Raad. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#140.
  * Add --disable-tests option to configure. Pull request by Fabrice
    Fontaine. gh#maxmind/libmaxminddb#136.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1572782400">- update to 1.4.2:
  * negative array index for MMDB_*get_value specifies the last element
  * Fix a memory leak when using custom databases without languages
    defined in the metadata
  * mmdblookup now displays the prefix length for the record when
    using the verbose flag</changelog>
  <changelog author="dimstar@opensuse.org" date="1574251200">- Add baselibs.conf: build libmaxminddb0-32bit, which is required
  by libdns1310-32bit (new dependency gained).</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1596801600">- update to 1.4.3:
  * Use of uninitialized memory in dump_entry_data_list() could have
    cause a heap buffer flow in mmdblookup [bsc#1175006]</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1610020800">- libmaxminddb 1.5.0:
  * build system changes for other platforms only</changelog>
  <changelog author="dmueller@suse.com" date="1614686400">- update to 1.5.2:
  * With `libmaxminddb` on Windows and `mmdblookup` generally, there were
    instances where the return value of `calloc` was not checked, which could
    lead to issues in low memory situations or when resource limits had been
    set.
  * The formatting of the manpages has been improved and the script that
    generates them now supports `lowdown` in addition to `pandoc`.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1619784000">- libmaxminddb 1.6.0:
  * CMake build system fixes, not in use in this package</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1664625600">- libmaxminddb 1.7.1:
  * FD_CLOEXEC is now set on platforms that do not support O_CLOEXEC
  * File size check now correctly compares the size to SSIZE_MAX
  * developer visible changes</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1699358400">- libmaxminddb 1.8.0:
  * PACKAGE_VERSION is now a private compile definition when
    building with CMake.
  * The feature test macro _POSIX_C_SOURCE is no longer set by
    maxminddb.h
  * assert() is no longer used outside test code</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1704888000">- libmaxminddb 1.9.1:
  * On very large databases, the calculation to determine the search
    tree size could overflow. This was fixed and several additional
    guards against overflows were added
  * build system tweaks</changelog>
  <changelog author="dmueller@suse.com" date="1721304000">- update to 1.10.0:
  * The reader can now lookup records on a database with a search
    tree that is greater than 4 gigabytes without sometimes
    returning erroneous results due to an integer overflow.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1739275200">- update to 1.12.2:
  * fix memory leaks
  * MMDB_get_entry_data_list() now always sets the passed
    entry_data_list parameter to either NULL or valid memory. This
    makes it safe for callers to use MMDB_free_entry_data_list() on
    it even in case of error.
  * more build system tweaks</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1774785600">- update to 1.13.3:
  * Fix validation of empty maps and arrays at the end of the
    metadata section
  * MMDB_open would incorrectly reject databases where a 0-element
    map or array was the last field in metadata
- includes changes from 1.13.2:
  * fixes for other platforms
- includes changes from 1.13.1:
  * No code changes
- includes changes from 1.13.0:
  * improved data validation
  * Fixes for integer overflow, undefined behavior, buffer overflow
    and other code correctness issues what could be triggered by
    large or malicously crafted database
  * Prevent stack overflow via unbounded recursion</changelog>
</package>
<package pkgid="62764b418b499535e1fbba21840804e654ea17f78de9493c8db1a7e27b0c1c54" name="lz4" arch="aarch64">
  <version epoch="0" ver="1.10.0" rel="150600.54.3"/>
  <changelog author="jengelh@inai.de" date="1417176000">- Update to version 1.4+svn124
  * LZ4F_compressBound() may be called with NULL preferencesPtr
  * LZ4_loadDict now returns the dictionary size instead of 1
  on success
- Add lz4-soversion.diff to address ABI changes</changelog>
  <changelog author="jengelh@inai.de" date="1459598400">- Update to new upstream release 131 (library 1.7) (boo#973735)
  * slightly improved decoding speed
  * lz4frame API is included in liblz4
  * new -m command line option to compress multiple files
  * new lz4 and lz4hc compression API (old one retained)</changelog>
  <changelog author="dimstar@opensuse.org" date="1484568000">- Add baselibs.conf: provide liblz4-1_7 as -32bit compatibility
  package, required by systemd-32bit.</changelog>
  <changelog author="jengelh@inai.de" date="1499256000">- Update to new upstrema release 1.7.5 (2017-01-03)
  * back to the old version scheme
  * lz4hc: new compression levels 10-12
- Remove lz4-soversion.diff (not needed),
  lz4-killdate.diff (no longer needed)</changelog>
  <changelog author="ddiss@suse.com" date="1502798400">- Use official upstream repository; (boo#1053910)</changelog>
  <changelog author="jengelh@inai.de" date="1503662400">- Update to new upstream release 1.8.0
  * cli: fix: do not modify /dev/null's permissions.
  * cli: added POSIX separator "--" for specifying that all
    following arguments are non-options.
  * cli: restored -BX command enabling block checksum.
  * API: added LZ4_compress_HC_destSize() and
    LZ4F_resetDecompressionContext().
  * API: lz4frame: negative compression levels trigger fast
    acceleration.
  * API: lz4frame: ability to control block checksum and
    dictionary ID.
  * API: fix: expose obsolete decoding functions
  * API: experimental: lz4frame_static.h:
    new dictionary compression API
  * doc: Updated LZ4 Frame format to v1.6.0, restoring
    Dictionary ID field in header.
- Add lz-export.diff</changelog>
  <changelog author="avindra@opensuse.org" date="1518004800">- Update to new upstream release 1.8.1.2
  * Most visible new feature is support for dictionary compression
  * Support is now more formally added on the API side within
    lib/lz4frame_static.h. It's early days, and this new API is
    tagged "experimental" for the time being.
  * Support is also added in the command line utility lz4, using
    the new command -D. The behavior of this command is identical
    to zstd, should you be already familiar.
  * lz4 doesn't specify how to build a dictionary. All it says is
    that it can be any file up to 64 KB.
  * This approach is compatible with zstd dictionary builder, which
    can be instructed to create a 64 KB dictionary.
  * Improved performance at ultra settings (levels 10+).
  * These levels receive a new code, called optimal parser,
    available in lib/lz4_opt.h.
  * New parser uses less memory (from 384KB to 256KB), performs
    faster, compresses a little bit better (not much, as it was
    already close to theoretical limit), and resists pathological
    patterns which could destroy performance.
  * New parser is directly compatible with lower compression levels,
    which brings additional benefits:
    + Compatibility with LZ4_*_destSize() variant, which reverses
    the logic by trying to fit as much data as possible into a
    predefined limited size buffer.
    + Compatibility with Dictionary compression, as it uses the
    same tables as regular HC mode
  * In the future, this compatibility will also allow dynamic change
    of compression level.
  * Small set of bug fixes and improvements:
    + perf : faster and stronger ultra modes (levels 10+)
    + perf : slightly faster compression and decompression speed
    + perf : fix bad degenerative case
    + fix : decompression failed when using a combination of
    extDict + low memory address
    + cli : support for dictionary compression (-D)
    + cli : fix : lz4 -d --rm preserves timestamp
    + cli : fix : do not modify /dev/null permission as root
    + api : _destSize() variant supported for all compression
    levels
- partial cleanup with spec-cleaner
- drop lz4-use-shlib.diff, breaks build
- misc spec cleanups
  - remove Makefile fix
  - build and install separately
  - New URL</changelog>
  <changelog author="astieger@suse.com" date="1530187200">- lz4 1.8.2:
  * speed inprovemtns for compression and decompression
  * fix compression compatible with low memory addresses
  * fix decompression segfault when provided with NULL input
  * cli: new command --favor-decSpeed
  * cli: benchmark mode more accurate for small inputs</changelog>
  <changelog author="astieger@suse.com" date="1539345600">- lz4 1.8.3:
  * minor decompression speed improvement (~+2%) with gcc
  * fix corruption in v1.8.2 at level 9 for files &gt; 64KB under
    rare conditions
  * Add new command --fast
  * api: LZ4_decompress_safe_partial() now decodes exactly the
    number of bytes requested</changelog>
  <changelog author="jengelh@inai.de" date="1559822400">- Update to new upstream release 1.9.1
  * Decompression speed was improved by about 12% (x86/x64).
  * New option `lz4 --list` to inspect the block type, checksum
    information, compressed and decompressed sizes (if present). The
    command is limited to single-frame files for the time being.</changelog>
  <changelog author="pgajdos@suse.com" date="1571140800">- version update to 1.9.2
  * decompression functions were reading a few bytes beyond input size
  * api: lz4frame initializers compatibility with c++, reported by @degski
  * cli : added command --list, based on a patch by @gabrielstedman
  * fixes CVE-2019-17543 [bsc#1153936]</changelog>
  <changelog author="pgajdos@suse.com" date="1571227200">- enable testsuite
- verbose build</changelog>
  <changelog author="jengelh@inai.de" date="1605528000">- Update to release 1.9.3
  * api: LZ4_decompress_safe_partial() now supports unknown
    compressed size
  * api: improved LZ4F_compressBound() with automatic flushing
  * cli: multiple files are compressed now using the legacy format</changelog>
  <changelog author="pgajdos@suse.com" date="1633348800">- version 1.9.3 fixes also CVE-2021-3520 [bsc#1185438]</changelog>
  <changelog author="jengelh@inai.de" date="1660651200">- Update to release 1.9.4
  * Decompression speed on high-end ARM64 platform is improved,
    by ~+20%.
  * For the specific scenario of data compressed with -BD4
    setting (small blocks, &lt;= 64 KB, linked) decompressed
    block-by-block into a flush buffer (like lz4 CLI does),
    decompression speed is improved ~+70%.
  * For compressed data employing the lz4frame format (native
    format of lz4 CLI), it's possible to ignore checksum
    validation during decompression, resulting in speed
    improvements of ~+40% . This capability is exposed at both
    CLI (see --no-crc) and library levels.</changelog>
  <changelog author="mpluskal@suse.com" date="1678276800">- Build AVX2 enabled hwcaps library for x86_64-v3</changelog>
  <changelog author="jengelh@inai.de" date="1721649600">- Update to release 1.10.0
  * Support for multithreading
  * Full support for dictionary compression
  * New compression level 2</changelog>
  <changelog author="code@bnavigator.de" date="1723636800">- Switch to cmake build system: Creates extra cmake modules for
  consuming projects</changelog>
</package>
<package pkgid="ea089f471a0ad1b79e1a78ec8f0bf64e2dc3a086457de679bd39ea879fffb7aa" name="lz4" arch="src">
  <version epoch="0" ver="1.10.0" rel="150600.54.3"/>
  <changelog author="jengelh@inai.de" date="1405512000">- Update to svn revision 119, set version to 1.2.0 (based upon
  Makefile contents; it's still odd to see the 1.4 Windows release)
  * Provide LZ4 as a shared library
- Remove lz4-automake.diff (no longer deemed necessary)
- Add lz4-use-shlib.diff</changelog>
  <changelog author="jengelh@inai.de" date="1412164800">- Update to version 1.3.1+svn123
  * Added a pkgconfig file
  * Fix a LZ4HC streaming bug
  * Updated the framing specificaiton to 1.4.1</changelog>
  <changelog author="jengelh@inai.de" date="1417176000">- Update to version 1.4+svn124
  * LZ4F_compressBound() may be called with NULL preferencesPtr
  * LZ4_loadDict now returns the dictionary size instead of 1
  on success
- Add lz4-soversion.diff to address ABI changes</changelog>
  <changelog author="jengelh@inai.de" date="1459598400">- Update to new upstream release 131 (library 1.7) (boo#973735)
  * slightly improved decoding speed
  * lz4frame API is included in liblz4
  * new -m command line option to compress multiple files
  * new lz4 and lz4hc compression API (old one retained)</changelog>
  <changelog author="dimstar@opensuse.org" date="1484568000">- Add baselibs.conf: provide liblz4-1_7 as -32bit compatibility
  package, required by systemd-32bit.</changelog>
  <changelog author="jengelh@inai.de" date="1499256000">- Update to new upstrema release 1.7.5 (2017-01-03)
  * back to the old version scheme
  * lz4hc: new compression levels 10-12
- Remove lz4-soversion.diff (not needed),
  lz4-killdate.diff (no longer needed)</changelog>
  <changelog author="ddiss@suse.com" date="1502798400">- Use official upstream repository; (boo#1053910)</changelog>
  <changelog author="jengelh@inai.de" date="1503662400">- Update to new upstream release 1.8.0
  * cli: fix: do not modify /dev/null's permissions.
  * cli: added POSIX separator "--" for specifying that all
    following arguments are non-options.
  * cli: restored -BX command enabling block checksum.
  * API: added LZ4_compress_HC_destSize() and
    LZ4F_resetDecompressionContext().
  * API: lz4frame: negative compression levels trigger fast
    acceleration.
  * API: lz4frame: ability to control block checksum and
    dictionary ID.
  * API: fix: expose obsolete decoding functions
  * API: experimental: lz4frame_static.h:
    new dictionary compression API
  * doc: Updated LZ4 Frame format to v1.6.0, restoring
    Dictionary ID field in header.
- Add lz-export.diff</changelog>
  <changelog author="avindra@opensuse.org" date="1518004800">- Update to new upstream release 1.8.1.2
  * Most visible new feature is support for dictionary compression
  * Support is now more formally added on the API side within
    lib/lz4frame_static.h. It's early days, and this new API is
    tagged "experimental" for the time being.
  * Support is also added in the command line utility lz4, using
    the new command -D. The behavior of this command is identical
    to zstd, should you be already familiar.
  * lz4 doesn't specify how to build a dictionary. All it says is
    that it can be any file up to 64 KB.
  * This approach is compatible with zstd dictionary builder, which
    can be instructed to create a 64 KB dictionary.
  * Improved performance at ultra settings (levels 10+).
  * These levels receive a new code, called optimal parser,
    available in lib/lz4_opt.h.
  * New parser uses less memory (from 384KB to 256KB), performs
    faster, compresses a little bit better (not much, as it was
    already close to theoretical limit), and resists pathological
    patterns which could destroy performance.
  * New parser is directly compatible with lower compression levels,
    which brings additional benefits:
    + Compatibility with LZ4_*_destSize() variant, which reverses
    the logic by trying to fit as much data as possible into a
    predefined limited size buffer.
    + Compatibility with Dictionary compression, as it uses the
    same tables as regular HC mode
  * In the future, this compatibility will also allow dynamic change
    of compression level.
  * Small set of bug fixes and improvements:
    + perf : faster and stronger ultra modes (levels 10+)
    + perf : slightly faster compression and decompression speed
    + perf : fix bad degenerative case
    + fix : decompression failed when using a combination of
    extDict + low memory address
    + cli : support for dictionary compression (-D)
    + cli : fix : lz4 -d --rm preserves timestamp
    + cli : fix : do not modify /dev/null permission as root
    + api : _destSize() variant supported for all compression
    levels
- partial cleanup with spec-cleaner
- drop lz4-use-shlib.diff, breaks build
- misc spec cleanups
  - remove Makefile fix
  - build and install separately
  - New URL</changelog>
  <changelog author="astieger@suse.com" date="1530187200">- lz4 1.8.2:
  * speed inprovemtns for compression and decompression
  * fix compression compatible with low memory addresses
  * fix decompression segfault when provided with NULL input
  * cli: new command --favor-decSpeed
  * cli: benchmark mode more accurate for small inputs</changelog>
  <changelog author="astieger@suse.com" date="1539345600">- lz4 1.8.3:
  * minor decompression speed improvement (~+2%) with gcc
  * fix corruption in v1.8.2 at level 9 for files &gt; 64KB under
    rare conditions
  * Add new command --fast
  * api: LZ4_decompress_safe_partial() now decodes exactly the
    number of bytes requested</changelog>
  <changelog author="jengelh@inai.de" date="1559822400">- Update to new upstream release 1.9.1
  * Decompression speed was improved by about 12% (x86/x64).
  * New option `lz4 --list` to inspect the block type, checksum
    information, compressed and decompressed sizes (if present). The
    command is limited to single-frame files for the time being.</changelog>
  <changelog author="pgajdos@suse.com" date="1571140800">- version update to 1.9.2
  * decompression functions were reading a few bytes beyond input size
  * api: lz4frame initializers compatibility with c++, reported by @degski
  * cli : added command --list, based on a patch by @gabrielstedman
  * fixes CVE-2019-17543 [bsc#1153936]</changelog>
  <changelog author="pgajdos@suse.com" date="1571227200">- enable testsuite
- verbose build</changelog>
  <changelog author="jengelh@inai.de" date="1605528000">- Update to release 1.9.3
  * api: LZ4_decompress_safe_partial() now supports unknown
    compressed size
  * api: improved LZ4F_compressBound() with automatic flushing
  * cli: multiple files are compressed now using the legacy format</changelog>
  <changelog author="pgajdos@suse.com" date="1633348800">- version 1.9.3 fixes also CVE-2021-3520 [bsc#1185438]</changelog>
  <changelog author="jengelh@inai.de" date="1660651200">- Update to release 1.9.4
  * Decompression speed on high-end ARM64 platform is improved,
    by ~+20%.
  * For the specific scenario of data compressed with -BD4
    setting (small blocks, &lt;= 64 KB, linked) decompressed
    block-by-block into a flush buffer (like lz4 CLI does),
    decompression speed is improved ~+70%.
  * For compressed data employing the lz4frame format (native
    format of lz4 CLI), it's possible to ignore checksum
    validation during decompression, resulting in speed
    improvements of ~+40% . This capability is exposed at both
    CLI (see --no-crc) and library levels.</changelog>
  <changelog author="mpluskal@suse.com" date="1678276800">- Build AVX2 enabled hwcaps library for x86_64-v3</changelog>
  <changelog author="jengelh@inai.de" date="1721649600">- Update to release 1.10.0
  * Support for multithreading
  * Full support for dictionary compression
  * New compression level 2</changelog>
  <changelog author="code@bnavigator.de" date="1723636800">- Switch to cmake build system: Creates extra cmake modules for
  consuming projects</changelog>
</package>
<package pkgid="092d33875096c3954ad5f197d58bc36edf46c7b6cbd742f581907839b174c33b" name="lz4" arch="x86_64">
  <version epoch="0" ver="1.10.0" rel="150600.54.3"/>
  <changelog author="jengelh@inai.de" date="1417176000">- Update to version 1.4+svn124
  * LZ4F_compressBound() may be called with NULL preferencesPtr
  * LZ4_loadDict now returns the dictionary size instead of 1
  on success
- Add lz4-soversion.diff to address ABI changes</changelog>
  <changelog author="jengelh@inai.de" date="1459598400">- Update to new upstream release 131 (library 1.7) (boo#973735)
  * slightly improved decoding speed
  * lz4frame API is included in liblz4
  * new -m command line option to compress multiple files
  * new lz4 and lz4hc compression API (old one retained)</changelog>
  <changelog author="dimstar@opensuse.org" date="1484568000">- Add baselibs.conf: provide liblz4-1_7 as -32bit compatibility
  package, required by systemd-32bit.</changelog>
  <changelog author="jengelh@inai.de" date="1499256000">- Update to new upstrema release 1.7.5 (2017-01-03)
  * back to the old version scheme
  * lz4hc: new compression levels 10-12
- Remove lz4-soversion.diff (not needed),
  lz4-killdate.diff (no longer needed)</changelog>
  <changelog author="ddiss@suse.com" date="1502798400">- Use official upstream repository; (boo#1053910)</changelog>
  <changelog author="jengelh@inai.de" date="1503662400">- Update to new upstream release 1.8.0
  * cli: fix: do not modify /dev/null's permissions.
  * cli: added POSIX separator "--" for specifying that all
    following arguments are non-options.
  * cli: restored -BX command enabling block checksum.
  * API: added LZ4_compress_HC_destSize() and
    LZ4F_resetDecompressionContext().
  * API: lz4frame: negative compression levels trigger fast
    acceleration.
  * API: lz4frame: ability to control block checksum and
    dictionary ID.
  * API: fix: expose obsolete decoding functions
  * API: experimental: lz4frame_static.h:
    new dictionary compression API
  * doc: Updated LZ4 Frame format to v1.6.0, restoring
    Dictionary ID field in header.
- Add lz-export.diff</changelog>
  <changelog author="avindra@opensuse.org" date="1518004800">- Update to new upstream release 1.8.1.2
  * Most visible new feature is support for dictionary compression
  * Support is now more formally added on the API side within
    lib/lz4frame_static.h. It's early days, and this new API is
    tagged "experimental" for the time being.
  * Support is also added in the command line utility lz4, using
    the new command -D. The behavior of this command is identical
    to zstd, should you be already familiar.
  * lz4 doesn't specify how to build a dictionary. All it says is
    that it can be any file up to 64 KB.
  * This approach is compatible with zstd dictionary builder, which
    can be instructed to create a 64 KB dictionary.
  * Improved performance at ultra settings (levels 10+).
  * These levels receive a new code, called optimal parser,
    available in lib/lz4_opt.h.
  * New parser uses less memory (from 384KB to 256KB), performs
    faster, compresses a little bit better (not much, as it was
    already close to theoretical limit), and resists pathological
    patterns which could destroy performance.
  * New parser is directly compatible with lower compression levels,
    which brings additional benefits:
    + Compatibility with LZ4_*_destSize() variant, which reverses
    the logic by trying to fit as much data as possible into a
    predefined limited size buffer.
    + Compatibility with Dictionary compression, as it uses the
    same tables as regular HC mode
  * In the future, this compatibility will also allow dynamic change
    of compression level.
  * Small set of bug fixes and improvements:
    + perf : faster and stronger ultra modes (levels 10+)
    + perf : slightly faster compression and decompression speed
    + perf : fix bad degenerative case
    + fix : decompression failed when using a combination of
    extDict + low memory address
    + cli : support for dictionary compression (-D)
    + cli : fix : lz4 -d --rm preserves timestamp
    + cli : fix : do not modify /dev/null permission as root
    + api : _destSize() variant supported for all compression
    levels
- partial cleanup with spec-cleaner
- drop lz4-use-shlib.diff, breaks build
- misc spec cleanups
  - remove Makefile fix
  - build and install separately
  - New URL</changelog>
  <changelog author="astieger@suse.com" date="1530187200">- lz4 1.8.2:
  * speed inprovemtns for compression and decompression
  * fix compression compatible with low memory addresses
  * fix decompression segfault when provided with NULL input
  * cli: new command --favor-decSpeed
  * cli: benchmark mode more accurate for small inputs</changelog>
  <changelog author="astieger@suse.com" date="1539345600">- lz4 1.8.3:
  * minor decompression speed improvement (~+2%) with gcc
  * fix corruption in v1.8.2 at level 9 for files &gt; 64KB under
    rare conditions
  * Add new command --fast
  * api: LZ4_decompress_safe_partial() now decodes exactly the
    number of bytes requested</changelog>
  <changelog author="jengelh@inai.de" date="1559822400">- Update to new upstream release 1.9.1
  * Decompression speed was improved by about 12% (x86/x64).
  * New option `lz4 --list` to inspect the block type, checksum
    information, compressed and decompressed sizes (if present). The
    command is limited to single-frame files for the time being.</changelog>
  <changelog author="pgajdos@suse.com" date="1571140800">- version update to 1.9.2
  * decompression functions were reading a few bytes beyond input size
  * api: lz4frame initializers compatibility with c++, reported by @degski
  * cli : added command --list, based on a patch by @gabrielstedman
  * fixes CVE-2019-17543 [bsc#1153936]</changelog>
  <changelog author="pgajdos@suse.com" date="1571227200">- enable testsuite
- verbose build</changelog>
  <changelog author="jengelh@inai.de" date="1605528000">- Update to release 1.9.3
  * api: LZ4_decompress_safe_partial() now supports unknown
    compressed size
  * api: improved LZ4F_compressBound() with automatic flushing
  * cli: multiple files are compressed now using the legacy format</changelog>
  <changelog author="pgajdos@suse.com" date="1633348800">- version 1.9.3 fixes also CVE-2021-3520 [bsc#1185438]</changelog>
  <changelog author="jengelh@inai.de" date="1660651200">- Update to release 1.9.4
  * Decompression speed on high-end ARM64 platform is improved,
    by ~+20%.
  * For the specific scenario of data compressed with -BD4
    setting (small blocks, &lt;= 64 KB, linked) decompressed
    block-by-block into a flush buffer (like lz4 CLI does),
    decompression speed is improved ~+70%.
  * For compressed data employing the lz4frame format (native
    format of lz4 CLI), it's possible to ignore checksum
    validation during decompression, resulting in speed
    improvements of ~+40% . This capability is exposed at both
    CLI (see --no-crc) and library levels.</changelog>
  <changelog author="mpluskal@suse.com" date="1678276800">- Build AVX2 enabled hwcaps library for x86_64-v3</changelog>
  <changelog author="jengelh@inai.de" date="1721649600">- Update to release 1.10.0
  * Support for multithreading
  * Full support for dictionary compression
  * New compression level 2</changelog>
  <changelog author="code@bnavigator.de" date="1723636800">- Switch to cmake build system: Creates extra cmake modules for
  consuming projects</changelog>
</package>
<package pkgid="2f93068e1e3aab81ab553c4852f2f0d1d04c338a763f250ce0fa72dacc00b1ec" name="mmdblookup" arch="aarch64">
  <version epoch="0" ver="1.13.3" rel="150600.30.1"/>
  <changelog author="p.drouand@gmail.com" date="1419163200">- Initial release (version 1.0.3)</changelog>
  <changelog author="p.drouand@gmail.com" date="1421841600">- Update to version 1.0.4
  * 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. GitHub #69.
  * A test failure in t/compile_c++_t.pl on new installs was fixed.</changelog>
  <changelog author="p.drouand@gmail.com" date="1437912000">- Update to version 1.1.1
  * Added `maxminddb-compat-util.h` as a source file to dist.
- Changes from version 1.1.0
  * 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 &amp; #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.</changelog>
  <changelog author="p.drouand@gmail.com" date="1447848000">- Update to version 1.1.2
  * 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.
  * Several segmentation faults found with afl-fuzz were fixed. These
    were caused by missing bounds checking and missing verification
    of data type.
    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.
- Add a build dependency to pkg-config</changelog>
  <changelog author="p.drouand@gmail.com" date="1460462400">- Update to version 1.2.0
  * 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 (https://github.com/maxmind/libmaxminddb/issues/110)
- Changes from version 1.1.5
  * 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.
- Changes from version 1.1.4
  * Packaging fixes. The 1.1.3 tarball release contained a lot of extra
    junk in the t/ directory.
- Changes from version 1.1.3
  * Added several additional checks to make sure that we don't attempt to read
    past the end of the databases's data section. GitHub #103
    (https://github.com/maxmind/libmaxminddb/pull/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. GitHub #102 (https://github.com/maxmind/libmaxminddb/pull/102)
  * Don't attempt to mmap a file that is too large to be mmapped on the system.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).
  * Added a missing out of memory check when reading a file's metadata.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/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.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1526558400">- Run tests
- Packaged LICENSE
- Update to version 1.3.2
  * 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.
    gh#maxmind/libmaxminddb#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_*).
- Update to version 1.3.1
  * Fix build problems related to rpl_malloc(). Pull request by Rainer
    Gerhards. gh#maxmind/libmaxminddb
  * Fix a race to set and read data in a field on the MMDB_s struct
    (ipv4_start_node). gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#153.
- Update to version 1.3.0
  * Perform fewer memory allocations in MMDB_get_entry_data_list(). This
    significantly improves its performance. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#143.
- Update to version 1.2.1
  * 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. gh#maxmind/libmaxminddb#120.
  * Several compiler warnings on Visual C++ were fixed. Pull request by Marcel
    Raad. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#140.
  * Add --disable-tests option to configure. Pull request by Fabrice
    Fontaine. gh#maxmind/libmaxminddb#136.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1572782400">- update to 1.4.2:
  * negative array index for MMDB_*get_value specifies the last element
  * Fix a memory leak when using custom databases without languages
    defined in the metadata
  * mmdblookup now displays the prefix length for the record when
    using the verbose flag</changelog>
  <changelog author="dimstar@opensuse.org" date="1574251200">- Add baselibs.conf: build libmaxminddb0-32bit, which is required
  by libdns1310-32bit (new dependency gained).</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1596801600">- update to 1.4.3:
  * Use of uninitialized memory in dump_entry_data_list() could have
    cause a heap buffer flow in mmdblookup [bsc#1175006]</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1610020800">- libmaxminddb 1.5.0:
  * build system changes for other platforms only</changelog>
  <changelog author="dmueller@suse.com" date="1614686400">- update to 1.5.2:
  * With `libmaxminddb` on Windows and `mmdblookup` generally, there were
    instances where the return value of `calloc` was not checked, which could
    lead to issues in low memory situations or when resource limits had been
    set.
  * The formatting of the manpages has been improved and the script that
    generates them now supports `lowdown` in addition to `pandoc`.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1619784000">- libmaxminddb 1.6.0:
  * CMake build system fixes, not in use in this package</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1664625600">- libmaxminddb 1.7.1:
  * FD_CLOEXEC is now set on platforms that do not support O_CLOEXEC
  * File size check now correctly compares the size to SSIZE_MAX
  * developer visible changes</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1699358400">- libmaxminddb 1.8.0:
  * PACKAGE_VERSION is now a private compile definition when
    building with CMake.
  * The feature test macro _POSIX_C_SOURCE is no longer set by
    maxminddb.h
  * assert() is no longer used outside test code</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1704888000">- libmaxminddb 1.9.1:
  * On very large databases, the calculation to determine the search
    tree size could overflow. This was fixed and several additional
    guards against overflows were added
  * build system tweaks</changelog>
  <changelog author="dmueller@suse.com" date="1721304000">- update to 1.10.0:
  * The reader can now lookup records on a database with a search
    tree that is greater than 4 gigabytes without sometimes
    returning erroneous results due to an integer overflow.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1739275200">- update to 1.12.2:
  * fix memory leaks
  * MMDB_get_entry_data_list() now always sets the passed
    entry_data_list parameter to either NULL or valid memory. This
    makes it safe for callers to use MMDB_free_entry_data_list() on
    it even in case of error.
  * more build system tweaks</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1774785600">- update to 1.13.3:
  * Fix validation of empty maps and arrays at the end of the
    metadata section
  * MMDB_open would incorrectly reject databases where a 0-element
    map or array was the last field in metadata
- includes changes from 1.13.2:
  * fixes for other platforms
- includes changes from 1.13.1:
  * No code changes
- includes changes from 1.13.0:
  * improved data validation
  * Fixes for integer overflow, undefined behavior, buffer overflow
    and other code correctness issues what could be triggered by
    large or malicously crafted database
  * Prevent stack overflow via unbounded recursion</changelog>
</package>
<package pkgid="a74fd046e7b9149abe90e77fb4be19f105e9052f064346e96901130e1cb724e1" name="mmdblookup" arch="x86_64">
  <version epoch="0" ver="1.13.3" rel="150600.30.1"/>
  <changelog author="p.drouand@gmail.com" date="1419163200">- Initial release (version 1.0.3)</changelog>
  <changelog author="p.drouand@gmail.com" date="1421841600">- Update to version 1.0.4
  * 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. GitHub #69.
  * A test failure in t/compile_c++_t.pl on new installs was fixed.</changelog>
  <changelog author="p.drouand@gmail.com" date="1437912000">- Update to version 1.1.1
  * Added `maxminddb-compat-util.h` as a source file to dist.
- Changes from version 1.1.0
  * 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 &amp; #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.</changelog>
  <changelog author="p.drouand@gmail.com" date="1447848000">- Update to version 1.1.2
  * 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.
  * Several segmentation faults found with afl-fuzz were fixed. These
    were caused by missing bounds checking and missing verification
    of data type.
    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.
- Add a build dependency to pkg-config</changelog>
  <changelog author="p.drouand@gmail.com" date="1460462400">- Update to version 1.2.0
  * 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 (https://github.com/maxmind/libmaxminddb/issues/110)
- Changes from version 1.1.5
  * 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.
- Changes from version 1.1.4
  * Packaging fixes. The 1.1.3 tarball release contained a lot of extra
    junk in the t/ directory.
- Changes from version 1.1.3
  * Added several additional checks to make sure that we don't attempt to read
    past the end of the databases's data section. GitHub #103
    (https://github.com/maxmind/libmaxminddb/pull/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. GitHub #102 (https://github.com/maxmind/libmaxminddb/pull/102)
  * Don't attempt to mmap a file that is too large to be mmapped on the system.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).
  * Added a missing out of memory check when reading a file's metadata.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/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.
    GitHub #101 (https://github.com/maxmind/libmaxminddb/pull/101).</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1526558400">- Run tests
- Packaged LICENSE
- Update to version 1.3.2
  * 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.
    gh#maxmind/libmaxminddb#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_*).
- Update to version 1.3.1
  * Fix build problems related to rpl_malloc(). Pull request by Rainer
    Gerhards. gh#maxmind/libmaxminddb
  * Fix a race to set and read data in a field on the MMDB_s struct
    (ipv4_start_node). gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#153.
- Update to version 1.3.0
  * Perform fewer memory allocations in MMDB_get_entry_data_list(). This
    significantly improves its performance. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#143.
- Update to version 1.2.1
  * 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. gh#maxmind/libmaxminddb#120.
  * Several compiler warnings on Visual C++ were fixed. Pull request by Marcel
    Raad. gh#maxmind/libmaxminddb#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. gh#maxmind/libmaxminddb#140.
  * Add --disable-tests option to configure. Pull request by Fabrice
    Fontaine. gh#maxmind/libmaxminddb#136.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1572782400">- update to 1.4.2:
  * negative array index for MMDB_*get_value specifies the last element
  * Fix a memory leak when using custom databases without languages
    defined in the metadata
  * mmdblookup now displays the prefix length for the record when
    using the verbose flag</changelog>
  <changelog author="dimstar@opensuse.org" date="1574251200">- Add baselibs.conf: build libmaxminddb0-32bit, which is required
  by libdns1310-32bit (new dependency gained).</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1596801600">- update to 1.4.3:
  * Use of uninitialized memory in dump_entry_data_list() could have
    cause a heap buffer flow in mmdblookup [bsc#1175006]</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1610020800">- libmaxminddb 1.5.0:
  * build system changes for other platforms only</changelog>
  <changelog author="dmueller@suse.com" date="1614686400">- update to 1.5.2:
  * With `libmaxminddb` on Windows and `mmdblookup` generally, there were
    instances where the return value of `calloc` was not checked, which could
    lead to issues in low memory situations or when resource limits had been
    set.
  * The formatting of the manpages has been improved and the script that
    generates them now supports `lowdown` in addition to `pandoc`.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1619784000">- libmaxminddb 1.6.0:
  * CMake build system fixes, not in use in this package</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1664625600">- libmaxminddb 1.7.1:
  * FD_CLOEXEC is now set on platforms that do not support O_CLOEXEC
  * File size check now correctly compares the size to SSIZE_MAX
  * developer visible changes</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1699358400">- libmaxminddb 1.8.0:
  * PACKAGE_VERSION is now a private compile definition when
    building with CMake.
  * The feature test macro _POSIX_C_SOURCE is no longer set by
    maxminddb.h
  * assert() is no longer used outside test code</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1704888000">- libmaxminddb 1.9.1:
  * On very large databases, the calculation to determine the search
    tree size could overflow. This was fixed and several additional
    guards against overflows were added
  * build system tweaks</changelog>
  <changelog author="dmueller@suse.com" date="1721304000">- update to 1.10.0:
  * The reader can now lookup records on a database with a search
    tree that is greater than 4 gigabytes without sometimes
    returning erroneous results due to an integer overflow.</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1739275200">- update to 1.12.2:
  * fix memory leaks
  * MMDB_get_entry_data_list() now always sets the passed
    entry_data_list parameter to either NULL or valid memory. This
    makes it safe for callers to use MMDB_free_entry_data_list() on
    it even in case of error.
  * more build system tweaks</changelog>
  <changelog author="andreas.stieger@gmx.de" date="1774785600">- update to 1.13.3:
  * Fix validation of empty maps and arrays at the end of the
    metadata section
  * MMDB_open would incorrectly reject databases where a 0-element
    map or array was the last field in metadata
- includes changes from 1.13.2:
  * fixes for other platforms
- includes changes from 1.13.1:
  * No code changes
- includes changes from 1.13.0:
  * improved data validation
  * Fixes for integer overflow, undefined behavior, buffer overflow
    and other code correctness issues what could be triggered by
    large or malicously crafted database
  * Prevent stack overflow via unbounded recursion</changelog>
</package>
<package pkgid="f2174cfb1b0044318ef8815e875773f0955b72b31968ccbd971af7a6399ebe54" name="perl-Test-Command-Simple" arch="noarch">
  <version epoch="0" ver="0.05" rel="150600.2.1"/>
</package>
<package pkgid="a67fdb7d122b3961deecb51bd35c54b34a0f9cf69506dea565ac6ef52499c42e" name="perl-Test-Command-Simple" arch="src">
  <version epoch="0" ver="0.05" rel="150600.2.1"/>
</package>
<package pkgid="b43a9673cb0b3e097b3382cb70d682bd92d1f60f51cddc71139760077f57a110" name="python-maxminddb" arch="src">
  <version epoch="0" ver="3.0.0" rel="150600.2.1"/>
  <changelog author="sebix+novell.com@sebix.at" date="1495713600">- initial package</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1527422400">- update to version 1.4.0:
  * IMPORTANT: Previously, the pure Python reader would allow
  `ipaddress.IPv4Address` and `ipaddress.IPv6Address` objects when calling
  `.get()`. This would fail with the C extension. The fact that these objects
  worked at all was an implementation detail and has varied with different
  releases. This release makes the pure Python implementation consistent
  with the extension. A `TypeError` will now be thrown if you attempt to
  use these types with either the pure Python implementation or the
  extension. The IP address passed to `.get()` should be a string type.
  * Fix issue where incorrect size was used when unpacking some types with the
  pure Python reader. Reported by Lee Symes. GitHub #30.
  * You may now pass in the database via a file descriptor rather than a file
  name when creating a new ``maxminddb.Reader`` object using ``MODE_FD``.
  This will read the database from the file descriptor into memory. Pull
  request by nkinkade. GitHub #33.</changelog>
  <changelog author="tchvatal@suse.com" date="1535544000">- Update to 1.4.1:
  * Fixes for python 3.7</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1570363200">- update to version 1.5.1:
  - Fix a possible segfault due to not correctly incrementing the reference
    on a returned object.
- update to version 1.5.0:
  - Python 3.3 and 3.4 are no longer supported.
  - The extension source directory was moved to prevent an ``ImportWarning``
    when importing the module on Python 2 with ``-Wdefault`` set. Reported by
    David Szotten and Craig de Stigter. GitHub #31.
  - The ``get`` method now accepts ``ipaddress.IPv4Address`` and
    ``ipaddress.IPv6Address`` objects in addition to strings.  This works with
    both the pure Python implementation as well as the extension. Based on a
    pull request #48 by Eric Pruitt. GitHub #50.
  - A new method, ``get_with_prefix_len``, was added. This method returns a
    tuple containing the record and the prefix length.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1577880000">- update to version 1.5.2:
  - Minor performance improvements in the pure Python reader.</changelog>
  <changelog author="tchvatal@suse.com" date="1584187200">- Fix build without python2</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1588852800">- update to version 1.5.4:
  - 1.5.3 was missing a test database. This release adds the test file.
  There are no other changes. Reported by Lumír 'Frenzy' Balhar. GitHub #60.
- update to version 1.5.3:
  - Fix a segfault when decoding a database with a corrupt data section.
  Reported by Robert Scott. GitHub #58.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1595505600">- update to version 2.0.1:
  - Fix minimum required python version in ``setup.py``. Pull request by
  Boros Gábor. GitHub #69 &amp; #70.
- update to version 2.0.0:
  - IMPORTANT: Python 3.6 or greater is required. If you are using an older
  version, please use a 1.x.x release.
  - Type hints have been added.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1595937600">- update to version 2.0.2:
  - Added ``py.typed`` file per PEP 561. Reported by Árni Már Jónsson.</changelog>
  <changelog author="jayvdb@gmail.com" date="1597579200">- Replace nose with pytest</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1604232000">- update to version 2.0.3:
  - The 2.0.0 release unintentionally required Python to be compiled with
    ``mmap`` support for the module to work. ``mmap`` is now optional
    again. Reported by john-heasman-cg. GitHub #76.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1622894400">- disable python 2, fixes Leap builds. Python 2 is no longer supported.
  fixes boo#1186841</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1631966400">- update to version 2.1.0:
  - The C extension now correctly supports objects that implement the
  ``os.PathLike`` interface.
  - When opening a database fails due to an access issue, the correct
  ``OSError`` subclass will now be thrown.
  - The ``Metadata`` class object is now available from the C extension
  module as ``maxminddb.extension.Metadata`` rather than
  ``maxminddb.extension.extension``.
  - Type stubs have been added for ``maxminddb.extension``.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1632484800">- update to version 2.2.0:
  - The return type for ``maxminddb.open_database()`` has been simplified
  to be just the ``Reader`` class as opposed to a union of that with
  the extension class. This is done by casting the extension to
  ``Reader``. The extension class has the same public API as the
  pure Python implementation. This simplifies type checking for users of
  this library. The ``Reader`` class is exposed as ``maxminddb.Reader``.
  Pull request by wouter bolsterlee. GitHub #88.
  - ``maxminddb.__all__`` is now set to define a public API. Pull request
  by wouter bolsterlee. GitHub #88.
  - Fix minor regression in ``repr`` output of ``maxminddb.reader.Metadata``
  in 2.1.0.</changelog>
  <changelog author="pgajdos@suse.com" date="1648468800">- python-mock is not required for build</changelog>
  <changelog author="dmueller@suse.com" date="1682078400">- add sle15_python_module_pythons (jsc#PED-68)</changelog>
  <changelog author="mmachova@suse.com" date="1697544000">- Update to 2.4.0
  * IMPORTANT: Python 3.7 or greater is required.
  * distutils is no longer used for building the C extension.
  * Missing Py_INCREF was added for the C extension.
  * The C extension now decrements the reference count on an object
    containing the database filename after its use in an error message
    rather than before.</changelog>
  <changelog author="sebix@sebix.at" date="1746014400">- update to version 2.6.3:
  - The vendored ``libmaxminddb`` has been updated to 1.12.0. This fixes a
  memory leak when opening a database fails.
  - Binary wheels are now built for Python 3.13.
- update to version 2.6.2:
  - The vendored ``libmaxminddb`` has been updated to 1.10.0. This fixes a
  bug that would cause incorrect results on databases that had search
  trees greater than 4 GB.
- update to version 2.6.1:
  - This release includes no source code changes. The only changes are to
  the release workflow.
  - Binary wheels are now built on Linux for aarch64. Pull request by Kevin
  Park. GitHub #160.
  - Binary wheels are now built on macOS for Apple silicon. Requested by
  Kevin Park. GitHub #152.
- update to version 2.6.0:
  - Added type annotations for instance variables on ``Metadata``
  - Updated type stubs for ``maxminddb.extension``.
  - ``setuptools`` is no longer listed as a runtime dependency. Pull request
  by Lewis Collard. GitHub #155.
- update to version 2.5.2:
  - The vendored ``libmaxminddb`` version was updated to 1.9.0. This fixes
  an issue when reading databases with a search tree exceeding 2 GB.
  Reported by Sami Salonen. GitHub #146.
- update to version 2.5.1:
  - This is a re-release of 2.5.0 to address missing files from the sdist.
  Reported by Lumír 'Frenzy' Balhar. GitHub #132.
- update to version 2.5.0:
  - IMPORTANT: Python 3.8 or greater is required. If you are using an older
  version, please use an earlier release.
  - Windows is now supported by the C extension.
  - The ``Reader`` class now implements the ``__iter__`` method. This will
  return an iterator that iterates over all records in the database,
  excluding repeated aliased of the IPv4 network. Requested by
  Jean-Baptiste Braun and others. GitHub #23.
  - The multiprocessing test now explicitly uses ``fork``. This allows it
  to run successfully on macOS. Pull request by Theodore Ni. GitHub #116.
  - A vendored copy of ``libmaxminddb`` will now be used by default when
  building the extension. If you wish to continue using the system shared
  library, you may set the ``MAXMINDDB_USE_SYSTEM_LIBMAXMINDDB`` environment
  variable to a true value when building the extension.
  - The C extension now builds on Python 3.13.
  - The C extension will now be built for PyPy.</changelog>
  <changelog author="steven.kowalik@suse.com" date="1750161600">- Use pyproject macros to build and install.</changelog>
  <changelog author="georg.pfuetzenreuter@suse.com" date="1769688000">- Update to version 3.0.0:
  * jump multiple versions, reference upstream changelog
- Clean up spec file, add workaround to keep compatibility with Leap 15.6
  (new version would otherwise require newer setuptools)</changelog>
</package>
<package pkgid="71351a21dd8f105f568768d7e26c57e3245634b9e99c60c173201c2f4937c665" name="python311-maxminddb" arch="aarch64">
  <version epoch="0" ver="3.0.0" rel="150600.2.1"/>
  <changelog author="sebix+novell.com@sebix.at" date="1495713600">- initial package</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1527422400">- update to version 1.4.0:
  * IMPORTANT: Previously, the pure Python reader would allow
  `ipaddress.IPv4Address` and `ipaddress.IPv6Address` objects when calling
  `.get()`. This would fail with the C extension. The fact that these objects
  worked at all was an implementation detail and has varied with different
  releases. This release makes the pure Python implementation consistent
  with the extension. A `TypeError` will now be thrown if you attempt to
  use these types with either the pure Python implementation or the
  extension. The IP address passed to `.get()` should be a string type.
  * Fix issue where incorrect size was used when unpacking some types with the
  pure Python reader. Reported by Lee Symes. GitHub #30.
  * You may now pass in the database via a file descriptor rather than a file
  name when creating a new ``maxminddb.Reader`` object using ``MODE_FD``.
  This will read the database from the file descriptor into memory. Pull
  request by nkinkade. GitHub #33.</changelog>
  <changelog author="tchvatal@suse.com" date="1535544000">- Update to 1.4.1:
  * Fixes for python 3.7</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1570363200">- update to version 1.5.1:
  - Fix a possible segfault due to not correctly incrementing the reference
    on a returned object.
- update to version 1.5.0:
  - Python 3.3 and 3.4 are no longer supported.
  - The extension source directory was moved to prevent an ``ImportWarning``
    when importing the module on Python 2 with ``-Wdefault`` set. Reported by
    David Szotten and Craig de Stigter. GitHub #31.
  - The ``get`` method now accepts ``ipaddress.IPv4Address`` and
    ``ipaddress.IPv6Address`` objects in addition to strings.  This works with
    both the pure Python implementation as well as the extension. Based on a
    pull request #48 by Eric Pruitt. GitHub #50.
  - A new method, ``get_with_prefix_len``, was added. This method returns a
    tuple containing the record and the prefix length.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1577880000">- update to version 1.5.2:
  - Minor performance improvements in the pure Python reader.</changelog>
  <changelog author="tchvatal@suse.com" date="1584187200">- Fix build without python2</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1588852800">- update to version 1.5.4:
  - 1.5.3 was missing a test database. This release adds the test file.
  There are no other changes. Reported by Lumír 'Frenzy' Balhar. GitHub #60.
- update to version 1.5.3:
  - Fix a segfault when decoding a database with a corrupt data section.
  Reported by Robert Scott. GitHub #58.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1595505600">- update to version 2.0.1:
  - Fix minimum required python version in ``setup.py``. Pull request by
  Boros Gábor. GitHub #69 &amp; #70.
- update to version 2.0.0:
  - IMPORTANT: Python 3.6 or greater is required. If you are using an older
  version, please use a 1.x.x release.
  - Type hints have been added.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1595937600">- update to version 2.0.2:
  - Added ``py.typed`` file per PEP 561. Reported by Árni Már Jónsson.</changelog>
  <changelog author="jayvdb@gmail.com" date="1597579200">- Replace nose with pytest</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1604232000">- update to version 2.0.3:
  - The 2.0.0 release unintentionally required Python to be compiled with
    ``mmap`` support for the module to work. ``mmap`` is now optional
    again. Reported by john-heasman-cg. GitHub #76.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1622894400">- disable python 2, fixes Leap builds. Python 2 is no longer supported.
  fixes boo#1186841</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1631966400">- update to version 2.1.0:
  - The C extension now correctly supports objects that implement the
  ``os.PathLike`` interface.
  - When opening a database fails due to an access issue, the correct
  ``OSError`` subclass will now be thrown.
  - The ``Metadata`` class object is now available from the C extension
  module as ``maxminddb.extension.Metadata`` rather than
  ``maxminddb.extension.extension``.
  - Type stubs have been added for ``maxminddb.extension``.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1632484800">- update to version 2.2.0:
  - The return type for ``maxminddb.open_database()`` has been simplified
  to be just the ``Reader`` class as opposed to a union of that with
  the extension class. This is done by casting the extension to
  ``Reader``. The extension class has the same public API as the
  pure Python implementation. This simplifies type checking for users of
  this library. The ``Reader`` class is exposed as ``maxminddb.Reader``.
  Pull request by wouter bolsterlee. GitHub #88.
  - ``maxminddb.__all__`` is now set to define a public API. Pull request
  by wouter bolsterlee. GitHub #88.
  - Fix minor regression in ``repr`` output of ``maxminddb.reader.Metadata``
  in 2.1.0.</changelog>
  <changelog author="pgajdos@suse.com" date="1648468800">- python-mock is not required for build</changelog>
  <changelog author="dmueller@suse.com" date="1682078400">- add sle15_python_module_pythons (jsc#PED-68)</changelog>
  <changelog author="mmachova@suse.com" date="1697544000">- Update to 2.4.0
  * IMPORTANT: Python 3.7 or greater is required.
  * distutils is no longer used for building the C extension.
  * Missing Py_INCREF was added for the C extension.
  * The C extension now decrements the reference count on an object
    containing the database filename after its use in an error message
    rather than before.</changelog>
  <changelog author="sebix@sebix.at" date="1746014400">- update to version 2.6.3:
  - The vendored ``libmaxminddb`` has been updated to 1.12.0. This fixes a
  memory leak when opening a database fails.
  - Binary wheels are now built for Python 3.13.
- update to version 2.6.2:
  - The vendored ``libmaxminddb`` has been updated to 1.10.0. This fixes a
  bug that would cause incorrect results on databases that had search
  trees greater than 4 GB.
- update to version 2.6.1:
  - This release includes no source code changes. The only changes are to
  the release workflow.
  - Binary wheels are now built on Linux for aarch64. Pull request by Kevin
  Park. GitHub #160.
  - Binary wheels are now built on macOS for Apple silicon. Requested by
  Kevin Park. GitHub #152.
- update to version 2.6.0:
  - Added type annotations for instance variables on ``Metadata``
  - Updated type stubs for ``maxminddb.extension``.
  - ``setuptools`` is no longer listed as a runtime dependency. Pull request
  by Lewis Collard. GitHub #155.
- update to version 2.5.2:
  - The vendored ``libmaxminddb`` version was updated to 1.9.0. This fixes
  an issue when reading databases with a search tree exceeding 2 GB.
  Reported by Sami Salonen. GitHub #146.
- update to version 2.5.1:
  - This is a re-release of 2.5.0 to address missing files from the sdist.
  Reported by Lumír 'Frenzy' Balhar. GitHub #132.
- update to version 2.5.0:
  - IMPORTANT: Python 3.8 or greater is required. If you are using an older
  version, please use an earlier release.
  - Windows is now supported by the C extension.
  - The ``Reader`` class now implements the ``__iter__`` method. This will
  return an iterator that iterates over all records in the database,
  excluding repeated aliased of the IPv4 network. Requested by
  Jean-Baptiste Braun and others. GitHub #23.
  - The multiprocessing test now explicitly uses ``fork``. This allows it
  to run successfully on macOS. Pull request by Theodore Ni. GitHub #116.
  - A vendored copy of ``libmaxminddb`` will now be used by default when
  building the extension. If you wish to continue using the system shared
  library, you may set the ``MAXMINDDB_USE_SYSTEM_LIBMAXMINDDB`` environment
  variable to a true value when building the extension.
  - The C extension now builds on Python 3.13.
  - The C extension will now be built for PyPy.</changelog>
  <changelog author="steven.kowalik@suse.com" date="1750161600">- Use pyproject macros to build and install.</changelog>
  <changelog author="georg.pfuetzenreuter@suse.com" date="1769688000">- Update to version 3.0.0:
  * jump multiple versions, reference upstream changelog
- Clean up spec file, add workaround to keep compatibility with Leap 15.6
  (new version would otherwise require newer setuptools)</changelog>
</package>
<package pkgid="4552a59085f8116e5ed46be1d29a39e701a79813229f341e8357358d070fd069" name="python311-maxminddb" arch="x86_64">
  <version epoch="0" ver="3.0.0" rel="150600.2.1"/>
  <changelog author="sebix+novell.com@sebix.at" date="1495713600">- initial package</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1527422400">- update to version 1.4.0:
  * IMPORTANT: Previously, the pure Python reader would allow
  `ipaddress.IPv4Address` and `ipaddress.IPv6Address` objects when calling
  `.get()`. This would fail with the C extension. The fact that these objects
  worked at all was an implementation detail and has varied with different
  releases. This release makes the pure Python implementation consistent
  with the extension. A `TypeError` will now be thrown if you attempt to
  use these types with either the pure Python implementation or the
  extension. The IP address passed to `.get()` should be a string type.
  * Fix issue where incorrect size was used when unpacking some types with the
  pure Python reader. Reported by Lee Symes. GitHub #30.
  * You may now pass in the database via a file descriptor rather than a file
  name when creating a new ``maxminddb.Reader`` object using ``MODE_FD``.
  This will read the database from the file descriptor into memory. Pull
  request by nkinkade. GitHub #33.</changelog>
  <changelog author="tchvatal@suse.com" date="1535544000">- Update to 1.4.1:
  * Fixes for python 3.7</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1570363200">- update to version 1.5.1:
  - Fix a possible segfault due to not correctly incrementing the reference
    on a returned object.
- update to version 1.5.0:
  - Python 3.3 and 3.4 are no longer supported.
  - The extension source directory was moved to prevent an ``ImportWarning``
    when importing the module on Python 2 with ``-Wdefault`` set. Reported by
    David Szotten and Craig de Stigter. GitHub #31.
  - The ``get`` method now accepts ``ipaddress.IPv4Address`` and
    ``ipaddress.IPv6Address`` objects in addition to strings.  This works with
    both the pure Python implementation as well as the extension. Based on a
    pull request #48 by Eric Pruitt. GitHub #50.
  - A new method, ``get_with_prefix_len``, was added. This method returns a
    tuple containing the record and the prefix length.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1577880000">- update to version 1.5.2:
  - Minor performance improvements in the pure Python reader.</changelog>
  <changelog author="tchvatal@suse.com" date="1584187200">- Fix build without python2</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1588852800">- update to version 1.5.4:
  - 1.5.3 was missing a test database. This release adds the test file.
  There are no other changes. Reported by Lumír 'Frenzy' Balhar. GitHub #60.
- update to version 1.5.3:
  - Fix a segfault when decoding a database with a corrupt data section.
  Reported by Robert Scott. GitHub #58.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1595505600">- update to version 2.0.1:
  - Fix minimum required python version in ``setup.py``. Pull request by
  Boros Gábor. GitHub #69 &amp; #70.
- update to version 2.0.0:
  - IMPORTANT: Python 3.6 or greater is required. If you are using an older
  version, please use a 1.x.x release.
  - Type hints have been added.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1595937600">- update to version 2.0.2:
  - Added ``py.typed`` file per PEP 561. Reported by Árni Már Jónsson.</changelog>
  <changelog author="jayvdb@gmail.com" date="1597579200">- Replace nose with pytest</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1604232000">- update to version 2.0.3:
  - The 2.0.0 release unintentionally required Python to be compiled with
    ``mmap`` support for the module to work. ``mmap`` is now optional
    again. Reported by john-heasman-cg. GitHub #76.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1622894400">- disable python 2, fixes Leap builds. Python 2 is no longer supported.
  fixes boo#1186841</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1631966400">- update to version 2.1.0:
  - The C extension now correctly supports objects that implement the
  ``os.PathLike`` interface.
  - When opening a database fails due to an access issue, the correct
  ``OSError`` subclass will now be thrown.
  - The ``Metadata`` class object is now available from the C extension
  module as ``maxminddb.extension.Metadata`` rather than
  ``maxminddb.extension.extension``.
  - Type stubs have been added for ``maxminddb.extension``.</changelog>
  <changelog author="sebix+novell.com@sebix.at" date="1632484800">- update to version 2.2.0:
  - The return type for ``maxminddb.open_database()`` has been simplified
  to be just the ``Reader`` class as opposed to a union of that with
  the extension class. This is done by casting the extension to
  ``Reader``. The extension class has the same public API as the
  pure Python implementation. This simplifies type checking for users of
  this library. The ``Reader`` class is exposed as ``maxminddb.Reader``.
  Pull request by wouter bolsterlee. GitHub #88.
  - ``maxminddb.__all__`` is now set to define a public API. Pull request
  by wouter bolsterlee. GitHub #88.
  - Fix minor regression in ``repr`` output of ``maxminddb.reader.Metadata``
  in 2.1.0.</changelog>
  <changelog author="pgajdos@suse.com" date="1648468800">- python-mock is not required for build</changelog>
  <changelog author="dmueller@suse.com" date="1682078400">- add sle15_python_module_pythons (jsc#PED-68)</changelog>
  <changelog author="mmachova@suse.com" date="1697544000">- Update to 2.4.0
  * IMPORTANT: Python 3.7 or greater is required.
  * distutils is no longer used for building the C extension.
  * Missing Py_INCREF was added for the C extension.
  * The C extension now decrements the reference count on an object
    containing the database filename after its use in an error message
    rather than before.</changelog>
  <changelog author="sebix@sebix.at" date="1746014400">- update to version 2.6.3:
  - The vendored ``libmaxminddb`` has been updated to 1.12.0. This fixes a
  memory leak when opening a database fails.
  - Binary wheels are now built for Python 3.13.
- update to version 2.6.2:
  - The vendored ``libmaxminddb`` has been updated to 1.10.0. This fixes a
  bug that would cause incorrect results on databases that had search
  trees greater than 4 GB.
- update to version 2.6.1:
  - This release includes no source code changes. The only changes are to
  the release workflow.
  - Binary wheels are now built on Linux for aarch64. Pull request by Kevin
  Park. GitHub #160.
  - Binary wheels are now built on macOS for Apple silicon. Requested by
  Kevin Park. GitHub #152.
- update to version 2.6.0:
  - Added type annotations for instance variables on ``Metadata``
  - Updated type stubs for ``maxminddb.extension``.
  - ``setuptools`` is no longer listed as a runtime dependency. Pull request
  by Lewis Collard. GitHub #155.
- update to version 2.5.2:
  - The vendored ``libmaxminddb`` version was updated to 1.9.0. This fixes
  an issue when reading databases with a search tree exceeding 2 GB.
  Reported by Sami Salonen. GitHub #146.
- update to version 2.5.1:
  - This is a re-release of 2.5.0 to address missing files from the sdist.
  Reported by Lumír 'Frenzy' Balhar. GitHub #132.
- update to version 2.5.0:
  - IMPORTANT: Python 3.8 or greater is required. If you are using an older
  version, please use an earlier release.
  - Windows is now supported by the C extension.
  - The ``Reader`` class now implements the ``__iter__`` method. This will
  return an iterator that iterates over all records in the database,
  excluding repeated aliased of the IPv4 network. Requested by
  Jean-Baptiste Braun and others. GitHub #23.
  - The multiprocessing test now explicitly uses ``fork``. This allows it
  to run successfully on macOS. Pull request by Theodore Ni. GitHub #116.
  - A vendored copy of ``libmaxminddb`` will now be used by default when
  building the extension. If you wish to continue using the system shared
  library, you may set the ``MAXMINDDB_USE_SYSTEM_LIBMAXMINDDB`` environment
  variable to a true value when building the extension.
  - The C extension now builds on Python 3.13.
  - The C extension will now be built for PyPy.</changelog>
  <changelog author="steven.kowalik@suse.com" date="1750161600">- Use pyproject macros to build and install.</changelog>
  <changelog author="georg.pfuetzenreuter@suse.com" date="1769688000">- Update to version 3.0.0:
  * jump multiple versions, reference upstream changelog
- Clean up spec file, add workaround to keep compatibility with Leap 15.6
  (new version would otherwise require newer setuptools)</changelog>
</package>
</otherdata>