Debian Bug report logs -
#180379
libdb3: errno useless with 1.85 compatibility interface
Reported by: Colin Watson <cjwatson@debian.org>
Date: Sun, 9 Feb 2003 18:18:01 UTC
Severity: normal
Found in version 3.2.9-17
Fixed in version 3.2.9+dfsg-1+rm
Done: Marco Rodrigues <gothicx@sapo.pt>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded to
debian-bugs-dist@lists.debian.org, Matthew Wilcox <willy@debian.org>, db3@packages.qa.debian.org:
Bug#180379; Package
libdb3.
Full text and
rfc822 format available.
Acknowledgement sent to
Colin Watson <cjwatson@debian.org>:
New Bug report received and forwarded. Copy sent to
Matthew Wilcox <willy@debian.org>, db3@packages.qa.debian.org.
Full text and
rfc822 format available.
Message #5 received at submit@bugs.debian.org (full text, mbox):
Package: libdb3
Version: 3.2.9-17
Severity: normal
In db 1.85 (and I believe using libdb2's 1.85 interface as well), an
application used to be able to get a useful value out of errno. When
using db3's 1.85 interface, this is no longer true. For example, when
ENOSPC occurs while writing a log entry, get() returns DB_RUNRECOVERY in
errno - but that's part of the new API, not the old one, and strerror()
doesn't do anything sensible with it. To get an error string from this,
one must call db_strerror(), which wasn't available before db3 and
therefore isn't in db_185.h. To find the true underlying errno so that
something more useful than "Fatal error, run database recovery" can be
printed, one must use DBENV->set_paniccall(), which isn't available in
the old API either.
In short, the compatibility API isn't compatible as far as error returns
are concerned. I'd like the 1.85 compatibility layer to use
DBENV->set_paniccall() to retrieve the underlying errno when
DB_RUNRECOVERY is returned and fill it back into errno, so that
applications can print proper error messages again. As far as I can
tell, no changes to the new API should be required to achieve this.
(I'm running into this in a big way with man-db, which has problems when
encountering ENOSPC. I've had a request to move to the new API anyway,
and I probably will as soon as I can write the extra database layer for
it, but it seems a shame that this is required urgently when db3's 1.85
interface is almost good enough and the new API is really much more
heavyweight than I need.)
Thanks,
--
Colin Watson [cjwatson@flatline.org.uk]
Information forwarded to
debian-bugs-dist@lists.debian.org, Matthew Wilcox <willy@debian.org>, db3@packages.qa.debian.org:
Bug#180379; Package
libdb3.
Full text and
rfc822 format available.
Acknowledgement sent to
Keith Bostic <bostic@abyssinian.sleepycat.com>:
Extra info received and forwarded to list. Copy sent to
Matthew Wilcox <willy@debian.org>, db3@packages.qa.debian.org.
Full text and
rfc822 format available.
Message #10 received at 180379@bugs.debian.org (full text, mbox):
> In short, the compatibility API isn't compatible as far as
> error returns are concerned.
This problem was fixed in revision 11.25 of db185/db185.c,
about a year ago, and fixed in any Berkeley DB 4.1 release.
Regards,
--keith
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Keith Bostic bostic@sleepycat.com
Sleepycat Software Inc. keithbosticim (ymsgid)
118 Tower Rd. +1-781-259-3139
Lincoln, MA 01773 http://www.sleepycat.com
Information forwarded to
debian-bugs-dist@lists.debian.org, Matthew Wilcox <willy@debian.org>, db3@packages.qa.debian.org:
Bug#180379; Package
libdb3.
Full text and
rfc822 format available.
Acknowledgement sent to
Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to
Matthew Wilcox <willy@debian.org>, db3@packages.qa.debian.org.
Full text and
rfc822 format available.
Message #18 received at 180379@bugs.debian.org (full text, mbox):
On Fri, Feb 14, 2003 at 11:14:09AM -0500, Keith Bostic wrote:
> > In short, the compatibility API isn't compatible as far as
> > error returns are concerned.
>
> This problem was fixed in revision 11.25 of db185/db185.c,
> about a year ago, and fixed in any Berkeley DB 4.1 release.
Fantastic, thanks! That may be a strong incentive for me to switch
man-db to using that then.
--
Colin Watson [cjwatson@flatline.org.uk]
Reply sent
to
Marco Rodrigues <gothicx@sapo.pt>:
You have taken responsibility.
(Sat, 21 Mar 2009 11:12:07 GMT)
Full text and
rfc822 format available.
Notification sent
to
Colin Watson <cjwatson@debian.org>:
Bug acknowledged by developer.
(Sat, 21 Mar 2009 11:12:07 GMT)
Full text and
rfc822 format available.
Message #23 received at 180379-done@bugs.debian.org (full text, mbox):
Version: 3.2.9+dfsg-1+rm
The libdb3 package has been removed from Debian so we are closing
the bugs that were still opened against it.
For more information about this package's removal, read
http://bugs.debian.org/434704 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
Kind regards,
--
Marco Rodrigues
Bug archived.
Request was from
Debbugs Internal Request <owner@bugs.debian.org>
to
internal_control@bugs.debian.org.
(Sun, 19 Apr 2009 07:36:28 GMT)
Full text and
rfc822 format available.
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Tue Feb 9 19:23:04 2010;
Machine Name:
busoni.debian.org
Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.