kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/gdbm/distinfo

13 lines
829 B
Text
Raw Normal View History

Add SHA512 digests for distfiles for databases category Problems found with existing distfiles: distfiles/D6.data.ros.gz distfiles/cstore0.2.tar.gz distfiles/data4.tar.gz distfiles/sphinx-2.2.7-release.tar.gz No changes made to the cstore or mariadb55-client distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2015-11-03 02:56:09 +01:00
$NetBSD: distinfo,v 1.10 2015/11/03 01:56:11 agc Exp $
+ move the distfile digest/checksum value from files/md5 to distinfo + move the patch digest/checksum values from files/patch-sum to distinfo + include distfile filesizes in distinfo
2001-04-17 11:56:50 +02:00
Update gdbm packages to 1.11, after martin@ diagnosed the compilation problem. Thanks, martin! Changes: Version 1.11, 2013-12-25 * Improved dump format. A new dump format is implemented, which encodes all data in base64 and stores not only key/data pairs, but also the original database file metadata, such as file name, mode and ownership. Files in this format can be sent without additional encapsulation over transmission channels that normally allow only ASCII data. Dumps in this format allow for restoring an exact copy of the database, including file ownership and privileges. * New function: gdbm_count int gdbm_count (GDBM_FILE *file, gdbm_count *count); Counts records in `file' and stores the result in the memory location pointed to by `count'. * New utilities: gdbm_dump and gdbm_load. Gdbm_dump creates a plain-text dump of the GDBM database. This dump can be used to create an exact copy of the database afterward. The gdbm_load performs the reverse: given the dump file, it creates a GDBM database. Apart from native GDBM dump formats, it also understands the format generated by Berkeley DB db_dump utility. Thus, an easy way to convert a Berkeley DB database to GDBM is: db_dump input.db | gdbm_load output.db * gdbmtool The gdbmtool utility allows you to examine, modify or create GDBM databases. It provides an easy-to-use interactive shell and can be used for scripting. One of the unique features of gdbmtool is that it allows to define datum structures for key and content parts, similarly to the C "struct" declarations, and to input and display such structured data.
2014-05-23 22:49:15 +02:00
SHA1 (gdbm-1.11.tar.gz) = ce433d0f192c21d41089458ca5c8294efe9806b4
RMD160 (gdbm-1.11.tar.gz) = f3d38a31ed509fdbfe52674e55585c2e570938c5
Add SHA512 digests for distfiles for databases category Problems found with existing distfiles: distfiles/D6.data.ros.gz distfiles/cstore0.2.tar.gz distfiles/data4.tar.gz distfiles/sphinx-2.2.7-release.tar.gz No changes made to the cstore or mariadb55-client distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2015-11-03 02:56:09 +01:00
SHA512 (gdbm-1.11.tar.gz) = 272fb65ab9ca0a21e9f0dcfb2c638457e87cbb938c65ee850123474d11f2858496f84d3fa9edca27cd91c7220160cfdb59f90bd46ddc45395514addc9fd4151c
Update gdbm packages to 1.11, after martin@ diagnosed the compilation problem. Thanks, martin! Changes: Version 1.11, 2013-12-25 * Improved dump format. A new dump format is implemented, which encodes all data in base64 and stores not only key/data pairs, but also the original database file metadata, such as file name, mode and ownership. Files in this format can be sent without additional encapsulation over transmission channels that normally allow only ASCII data. Dumps in this format allow for restoring an exact copy of the database, including file ownership and privileges. * New function: gdbm_count int gdbm_count (GDBM_FILE *file, gdbm_count *count); Counts records in `file' and stores the result in the memory location pointed to by `count'. * New utilities: gdbm_dump and gdbm_load. Gdbm_dump creates a plain-text dump of the GDBM database. This dump can be used to create an exact copy of the database afterward. The gdbm_load performs the reverse: given the dump file, it creates a GDBM database. Apart from native GDBM dump formats, it also understands the format generated by Berkeley DB db_dump utility. Thus, an easy way to convert a Berkeley DB database to GDBM is: db_dump input.db | gdbm_load output.db * gdbmtool The gdbmtool utility allows you to examine, modify or create GDBM databases. It provides an easy-to-use interactive shell and can be used for scripting. One of the unique features of gdbmtool is that it allows to define datum structures for key and content parts, similarly to the C "struct" declarations, and to input and display such structured data.
2014-05-23 22:49:15 +02:00
Size (gdbm-1.11.tar.gz) = 811662 bytes
SHA1 (patch-src_gdbmtool.c) = 3f96f09d42dc4942b55da698d4853a3f175e6a44
SHA1 (patch-src_gdbmtool.h) = 0301c08bbf66a3c4249bf32666f04a355803247b
SHA1 (patch-tests_create00.at) = 2ce3d6ebac588b25699a6f38b298d4fb63965714
SHA1 (patch-tests_dbmcreate00.at) = 5d5030b9ff6b9f5a4141abec82a066afba5c557f
SHA1 (patch-tests_dbmdel00.at) = 3a472a1b0b45e315823dc5a505ddd656f2d8c469
SHA1 (patch-tests_delete00.at) = 6ba7832eaf118d9b7380b0459ddcf786d497f431
Reference in a new issue Copy permalink