lmdb 0.9.17-3 source package in Ubuntu

Changelog

lmdb (0.9.17-3) unstable; urgency=medium

  * Use `cp -pP` instead of `cp` in upstream Makefile to preserve mode and
    permissions on installed files (Closes: #808785)
  * Update liblmdb0.symbols file

 -- Ondřej Surý <email address hidden>  Mon, 28 Dec 2015 15:53:32 +0100

Upload details

Uploaded by:
Debian Berkeley DB Maintainers
Uploaded to:
Sid
Original maintainer:
Debian Berkeley DB Maintainers
Architectures:
any all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Xenial release universe misc

Downloads

File Size SHA-256 Checksum
lmdb_0.9.17-3.dsc 2.1 KiB 888792d5bcac5d0b5f6bb38ae1d1c939221034dd6cc5f2882dd3d6d85cdc4b25
lmdb_0.9.17.orig.tar.xz 109.6 KiB 8b9e6b5de0c25376e063b4b5ea4979a4f0b00dfe55eb3cdb2b6b2647dde97ca4
lmdb_0.9.17-3.debian.tar.xz 5.3 KiB 2d1e3bef4224f280b73e2bca6de38874873082077f6834e18867bbf54f4e1f69

Available diffs

No changes file available.

Binary packages built by this source

liblmdb-dev: Lightning Memory-Mapped Database development files

 This package contains the development libraries, header files. Install
 lmdb-doc package for man pages.
 .
 Lighting Memory-Mapped Database (LMDB) is an ultra-fast, ultra-compact
 key-value embedded data store developed for the OpenLDAP Project. It uses
 memory-mapped files, so it has the read performance of a pure in-memory
 database while still offering the persistence of standard disk-based
 databases, and is only limited to the size of the virtual address space, (it
 is not limited to the size of physical RAM).

liblmdb-dev-dbgsym: No summary available for liblmdb-dev-dbgsym in ubuntu yakkety.

No description available for liblmdb-dev-dbgsym in ubuntu yakkety.

liblmdb0: No summary available for liblmdb0 in ubuntu yakkety.

No description available for liblmdb0 in ubuntu yakkety.

liblmdb0-dbgsym: debug symbols for package liblmdb0

 This package contains the LMDB shared library.
 .
 Lighting Memory-Mapped Database (LMDB) is an ultra-fast, ultra-compact
 key-value embedded data store developed for the OpenLDAP Project. It uses
 memory-mapped files, so it has the read performance of a pure in-memory
 database while still offering the persistence of standard disk-based
 databases, and is only limited to the size of the virtual address space, (it
 is not limited to the size of physical RAM).

lmdb-dbg: No summary available for lmdb-dbg in ubuntu yakkety.

No description available for lmdb-dbg in ubuntu yakkety.

lmdb-doc: Lightning Memory-Mapped Database doxygen documentation

 This package contains the doxygen generated documentation and the man
 pages for the LMDB library.
 .
 Lighting Memory-Mapped Database (LMDB) is an ultra-fast, ultra-compact
 key-value embedded data store developed for the OpenLDAP Project. It uses
 memory-mapped files, so it has the read performance of a pure in-memory
 database while still offering the persistence of standard disk-based
 databases, and is only limited to the size of the virtual address space, (it
 is not limited to the size of physical RAM).

lmdb-utils: Lightning Memory-Mapped Database Utilities

 This package provides tools for manipulating LMDB databases:
  * mdb_stat - LMDB environment status tool
  * mdb_copy - LMDB environment copy tool
 .
 Lighting Memory-Mapped Database (LMDB) is an ultra-fast, ultra-compact
 key-value embedded data store developed for the OpenLDAP Project. It uses
 memory-mapped files, so it has the read performance of a pure in-memory
 database while still offering the persistence of standard disk-based
 databases, and is only limited to the size of the virtual address space, (it
 is not limited to the size of physical RAM).

lmdb-utils-dbgsym: debug symbols for package lmdb-utils

 This package provides tools for manipulating LMDB databases:
  * mdb_stat - LMDB environment status tool
  * mdb_copy - LMDB environment copy tool
 .
 Lighting Memory-Mapped Database (LMDB) is an ultra-fast, ultra-compact
 key-value embedded data store developed for the OpenLDAP Project. It uses
 memory-mapped files, so it has the read performance of a pure in-memory
 database while still offering the persistence of standard disk-based
 databases, and is only limited to the size of the virtual address space, (it
 is not limited to the size of physical RAM).