Your message dated Wed, 25 Jan 2006 23:47:12 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349778: fixed in cl-pg 20061225-1
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; 25 Jan 2006 08:02:15 +0000
>From [EMAIL PROTECTED] Wed Jan 25 00:02:15 2006
Return-path: <[EMAIL PROTECTED]>
Received: from gourmet.spamgourmet.com ([216.218.230.146])
by spohr.debian.org with esmtp (Exim 4.50)
id 1F1fbb-00087Q-9Y
for [EMAIL PROTECTED]; Wed, 25 Jan 2006 00:02:15 -0800
Received: from gourmet.spamgourmet.com (localhost [127.0.0.1])
by gourmet.spamgourmet.com (8.12.11/8.12.11) with ESMTP id
k0P84DJ4020722
for <[EMAIL PROTECTED]>; Wed, 25 Jan 2006 00:04:13 -0800
Received: (from [EMAIL PROTECTED])
by gourmet.spamgourmet.com (8.12.11/8.12.11/Submit) id k0P84C8n020705
for [EMAIL PROTECTED]; Wed, 25 Jan 2006 00:04:12 -0800
Received: from smtp1-cv.offis.uni-oldenburg.de (smtp1-cv.OFFIS.Uni-Oldenburg.DE
[134.106.50.227])
by gourmet.spamgourmet.com (8.12.11/8.12.11) with ESMTP id
k0P84BDV020648
for <>; Wed, 25 Jan 2006 00:04:11 -0800
Received: by smtp1-cv.offis.uni-oldenburg.de (Postfix, from userid 1003)
id 37E1011AB943; Wed, 25 Jan 2006 09:01:52 +0100 (CET)
Received: from smtp2.fauna (smtp2.fauna [192.168.100.9])
by smtp1-cv.offis.uni-oldenburg.de (Postfix) with ESMTP id 2FC446AEF
for <>; Wed, 25 Jan 2006 09:01:49 +0100 (CET)
Received: from [192.168.100.110] (luchs.fauna [192.168.100.110])
by smtp2.fauna (Postfix) with ESMTP id 0469B2C88017
for <>; Wed, 25 Jan 2006 09:01:46 +0100 (CET)
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 25 Jan 2006 09:01:46 +0100
From: [EMAIL PROTECTED]
User-Agent: Mozilla Thunderbird 1.0 (X11/20041207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: Documentation for pg-close-portal wrong
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-hits: 0.0
X-Spam-score: 0.0 ()
X-Spamgourmet:
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.4 required=4.0 tests=BAYES_00,HAS_PACKAGE,
NO_REAL_NAME autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: cl-pg
Version: 20050717-1
These two functions have identical documentation. If they implement
identical functionality, then one should be deleted; if they implement
different functionality, the documentation should explain the difference:
(defgeneric pg-close-statement (connection statement-name)
(:documentation
"Closes a prepared statement"))
(defgeneric pg-close-portal (connection portal)
(:documentation
"Closes a prepared statement"))
So yes, I know that one closes a statement, while the other closes a
portal. But I don't know what a portal is, I don't know what "close"
means ("delete"? "forget about"? "prevent updates of"? "wrap inside a
closure"?) and pg-close-statement isn't doing what I expect it to do (I
get errors saying that the statement already exists when I try to
re-create it afterwards). I don't have enough information to verify
that the functions are doing what they're supposed to do. They should
certainly include references to whichever function "opens" the things
that they are closing.
Also, the start of the file recommends seeing the README:
;; See the README for API documentation.
...but no README is included. I've chased up the README from CVS, and
in fact it provides no help here. But it should probably be included
anyway, with a disclaimer saying that it's out of date.
Even better, it would be nice if there was some actual real
documentation provided, including examples of how each of the functions
is supposed to be used. Right now, I'm just having to guess how to use
prepared statements, and after a couple of days of bashing my head
against the problem I still can't get it to work.
---------------------------------------
Received: (at 349778-close) by bugs.debian.org; 26 Jan 2006 07:52:34 +0000
>From [EMAIL PROTECTED] Wed Jan 25 23:52:34 2006
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1F21qa-0006KP-4J; Wed, 25 Jan 2006 23:47:12 -0800
From: Peter Van Eynde <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.65 $
Subject: Bug#349778: fixed in cl-pg 20061225-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 25 Jan 2006 23:47:12 -0800
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Source: cl-pg
Source-Version: 20061225-1
We believe that the bug you reported is fixed in the latest version of
cl-pg, which is due to be installed in the Debian FTP archive:
cl-pg_20061225-1.diff.gz
to pool/main/c/cl-pg/cl-pg_20061225-1.diff.gz
cl-pg_20061225-1.dsc
to pool/main/c/cl-pg/cl-pg_20061225-1.dsc
cl-pg_20061225-1_all.deb
to pool/main/c/cl-pg/cl-pg_20061225-1_all.deb
cl-pg_20061225.orig.tar.gz
to pool/main/c/cl-pg/cl-pg_20061225.orig.tar.gz
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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Van Eynde <[EMAIL PROTECTED]> (supplier of updated cl-pg 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 [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 25 Jan 2006 20:32:49 +0100
Source: cl-pg
Binary: cl-pg
Architecture: source all
Version: 20061225-1
Distribution: unstable
Urgency: low
Maintainer: Peter Van Eynde <[EMAIL PROTECTED]>
Changed-By: Peter Van Eynde <[EMAIL PROTECTED]>
Description:
cl-pg - Common Lisp library that provides a socket level postgresql inter
Closes: 349778
Changes:
cl-pg (20061225-1) unstable; urgency=low
.
* New upstream
* Better sbcl unicode support
* Improved asdf compatibility
* Documentation for pg-close-portal fixed in upstream
(Closes: #349778)
Files:
d551749861df07eddea2fab0bb5b371e 573 devel optional cl-pg_20061225-1.dsc
d4f90f7ef781099a7e67d46292ff3090 47938 devel optional
cl-pg_20061225.orig.tar.gz
63b19de1869d2ba7fde68d3c492d914f 1575 devel optional cl-pg_20061225-1.diff.gz
c6b8e92f1dd4123b0bf1a2b0acd05107 39620 devel optional cl-pg_20061225-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD1/E/11ldN0tyliURAt7GAJ9OOL/UKjODVPapfY+6hTNUYSKG/QCfUsXe
bsSnbQUO6c7tXT39eimIVIc=
=Wt4g
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
