Bug#127063: marked as done (ITP: mird1 - Mird database library)
Your message dated Wed, 09 Jan 2002 15:05:04 -0500
with message-id <E16OOy8-0000tH-00@auric.debian.org>
and subject line Bug#127063: fixed in mird 1.0.7-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 30 Dec 2001 17:58:34 +0000
>From eloy@transilvania.eu.org Sun Dec 30 11:58:34 2001
Return-path: <eloy@transilvania.eu.org>
Received: from fargo.cgs.poznan.pl (fargo.cgs.pl) [212.126.5.98] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16KkED-0001Cg-00; Sun, 30 Dec 2001 11:58:33 -0600
Received: by fargo.cgs.pl (Postfix, from userid 1000)
id 339C11439F; Sun, 30 Dec 2001 18:57:51 +0100 (CET)
Date: Sun, 30 Dec 2001 18:57:51 +0100
From: Krzysztof Krzyzaniak <eloy@transilvania.eu.org>
To: submit@bugs.debian.org
Subject: ITP: mird1 - Mird database library
Message-ID: <20011230175751.GA9697@transilvania.eu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.3.24i
X-Debbugs-CC: debian-devel@lists.debian.org
X-Operating-System: Linux fargo 2.2.20pre8
X-Uptime: 18:36:19 up 22 days, 6:28, 3 users, load average: 0.17, 0.17, 0.08
X-Fingerprint: AC3A 464A DF87 6468 F63D CCB2 F8D3 1F49 DEB0 EC31
Delivered-To: submit@bugs.debian.org
Package: wnpp
Severity: wishlist
Package: mird-dev
Description: Mird database library (developer files)
Package: mird1
Description: Mird database library (runtime files)
URL: http://www.mirar.org/mird/
Licence:
The Mird database library may be freely distributed and used with these
limits:
* The database library may be distributed with or without source.
* There is no promise that this software works. (But if you find any
bugs, please let me know!)
* You can use this software for whatever you want. You don't have to
pay me.
* You may not pretend that you wrote this software. If you use it in
a program, you must acknowledge it somewhere in your documentation.
>From tutorial.txt:
Mird is a database library, for operating on simple disk-based
databases with the following features:
* The database is key-value oriented, primarily - this is useful for
most database operations, from inserting and removing lines in
tables, and for object-oriented data, provided it's fast enough.
(It should be.) The key can be either a 32-bit integer or a byte
string of any size. (A integer-key table using 32 bit hash keys is
used to store the string-key entries.)
* The database consists of several tables or key-value mappings.
On this level, the table is identified by a 32-bit integer. It is
easy enough to implement a table name lookup table, when the need
arises.
* Changes to the database is made in the shell of transactions,
where each transaction encapsulates any change to the database
atomically.
* More then one transaction could be in progress at any given
moment, with resulting conflicts at the closing of the last
transactions, if they operate on the same data.
* Conflicts are either based on changes to a key:value pair, but a
whole table could be locked to mark dependency conflicts.
* The syncing against disk is normally done first when the database
is closed or forced to sync; this is when any unused block is
reused. This gives very high speed.
(The database could of course be in a state where every
transaction completion is synced to the disk.)
* To make this non-syncing secure, the database uses a journal file.
When something fatal happened to the process using the database
(power loss, kill -9, whatever), this file is read back and the
database is restored to the latest state possible.
* The transaction order is guaranteed; any transaction following any
failed (ie, broken, not cancelled) transaction will never be seen
as valid.
* The database is fast; it is normally no problem to write or read
several thousand entries per second, if the I/O wait is slow
enough.
* The database is unfortunately low-level, there is no high-level
replicating, memory-only or distributing schemes included. It was
never inteded to solve these problems, only the speed and
security.
* The library is heavily tested by a testsuite, including tests
simulating power loss and write failures (as in writing the wrong
data to the database).
Debianized source version you can find on ftp://ftp.cgs.pl/pub/debian/mird/
eloy
--
--Krzysztof-eloy-Krzy¿aniak-----------------------eloy-@-transilvania-eu-org--
Moje oczy s± oczami wariata
Kiedy spotykaj± siê z twoimi oczami
---------------------------------------
Received: (at 127063-close) by bugs.debian.org; 9 Jan 2002 20:08:55 +0000
>From troup@auric.debian.org Wed Jan 09 14:08:55 2002
Return-path: <troup@auric.debian.org>
Received: from auric.debian.org [206.246.226.45] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16OP1r-00069V-00; Wed, 09 Jan 2002 14:08:55 -0600
Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian))
id 16OOy8-0000tH-00; Wed, 09 Jan 2002 15:05:04 -0500
From: Krzysztof Krzyzaniak (eloy) <eloy@debian.org>
To: 127063-close@bugs.debian.org
X-Katie: $Revision: 1.66 $
Subject: Bug#127063: fixed in mird 1.0.7-2
Message-Id: <E16OOy8-0000tH-00@auric.debian.org>
Sender: James Troup <troup@auric.debian.org>
Date: Wed, 09 Jan 2002 15:05:04 -0500
Delivered-To: 127063-close@bugs.debian.org
We believe that the bug you reported is fixed in the latest version of
mird, which has been installed in the Debian FTP archive:
mird-dev_1.0.7-2_i386.deb
to pool/main/m/mird/mird-dev_1.0.7-2_i386.deb
mird1_1.0.7-2_i386.deb
to pool/main/m/mird/mird1_1.0.7-2_i386.deb
mird_1.0.7-2.diff.gz
to pool/main/m/mird/mird_1.0.7-2.diff.gz
mird_1.0.7-2.dsc
to pool/main/m/mird/mird_1.0.7-2.dsc
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 127063@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Krzysztof Krzyzaniak (eloy) <eloy@debian.org> (supplier of updated mird package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 9 Jan 2002 12:20:09 +0100
Source: mird
Binary: mird-dev mird1
Architecture: source i386
Version: 1.0.7-2
Distribution: unstable
Urgency: low
Maintainer: Krzysztof Krzyzaniak (eloy) <eloy@debian.org>
Changed-By: Krzysztof Krzyzaniak (eloy) <eloy@debian.org>
Description:
mird-dev - Mird database library (developer files)
mird1 - Mird database library (runtime files)
Closes: 127063
Changes:
mird (1.0.7-2) unstable; urgency=low
.
* control file is fixed (Section: libs changed to Section: devel)
* Preparating process is done (closes: #127063)
Files:
8d5e07012b2108c75779b81cfde2d4ee 637 devel optional mird_1.0.7-2.dsc
5c0e3399426fcedcad34ea5c7c4db2c1 3008 devel optional mird_1.0.7-2.diff.gz
8a48fe7b287fb41ead921f7fd234249d 83276 devel optional mird-dev_1.0.7-2_i386.deb
73847994a0a39d784d3aaf8dd58544a5 31452 devel optional mird1_1.0.7-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Dalsze informacje znajduj± siê na http://www.gnupg.org/
iD8DBQE8PClE+NMfSd6w7DERAlbiAJ9EccW8u5ZYDVUQvZK9W5zEf4PjlQCcCIdZ
jt+D2L2wSJcwWKEDM1mo2vs=
=T+ys
-----END PGP SIGNATURE-----
Reply to: