[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#468175: marked as done (ITP: pymssql -- python database access for MS SQL server and Sybase)

Your message dated Thu, 06 Mar 2008 22:37:04 +0000
with message-id <E1JXOi0-0003O2-NN@ries.debian.org>
and subject line Bug#468175: fixed in pymssql 0.8.0+dfsg-1
has caused the Debian Bug report #468175,
regarding ITP: pymssql -- python database access for MS SQL server and Sybase
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
468175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468175
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Josselin Mouette <joss@debian.org>

* Package name    : pymssql
  Version         : 0.8.0
  Upstream Author : Park joon-cheol <jooncheol@gmail.com>
                    Andrzej Kukula <akukula@gmail.com>
* URL             : http://pymssql.sourceforge.net/
* License         : LGPL
  Programming Lang: C, Python
  Description     : python database access for MS SQL server and Sybase

 This package contains a python module allowing direct access to 
 Microsoft SQL server and Sybase databases. It is designed for 
 simplicity and performance, and conforms to Python DB-API 2.0.

--- End Message ---
--- Begin Message --- 
Source: pymssql
Source-Version: 0.8.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
pymssql, which is due to be installed in the Debian FTP archive:

pymssql_0.8.0+dfsg-1.diff.gz
  to pool/main/p/pymssql/pymssql_0.8.0+dfsg-1.diff.gz
pymssql_0.8.0+dfsg-1.dsc
  to pool/main/p/pymssql/pymssql_0.8.0+dfsg-1.dsc
pymssql_0.8.0+dfsg.orig.tar.gz
  to pool/main/p/pymssql/pymssql_0.8.0+dfsg.orig.tar.gz
python-pymssql_0.8.0+dfsg-1_amd64.deb
  to pool/main/p/pymssql/python-pymssql_0.8.0+dfsg-1_amd64.deb



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 468175@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Josselin Mouette <joss@debian.org> (supplier of updated pymssql 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: Thu, 06 Mar 2008 12:49:56 +0100
Source: pymssql
Binary: python-pymssql
Architecture: source amd64
Version: 0.8.0+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Josselin Mouette <joss@debian.org>
Changed-By: Josselin Mouette <joss@debian.org>
Description: 
 python-pymssql - Python database access for MS SQL server and Sybase
Closes: 468175
Changes: 
 pymssql (0.8.0+dfsg-1) unstable; urgency=low
 .
   * Remove ntwdblib.dll from the upstream sources, because this file
     doesn’t have any associated source. Thanks Joerg Jaspert for
     noticing.
 .
 pymssql (0.8.0-1) unstable; urgency=low
 .
   * Initial release. Closes: #468175.
Files: 
 05c2f2e4e3edafbe1e6c8bd9298ccb19 672 python optional pymssql_0.8.0+dfsg-1.dsc
 27653292d8618cb215e33c4c3a18b692 26532 python optional pymssql_0.8.0+dfsg.orig.tar.gz
 8b61af8d4a311e02b05cdbd2b0fb5f17 1528 python optional pymssql_0.8.0+dfsg-1.diff.gz
 c6ea5a704d2ecc9a798fdeeee992af0e 29932 python optional python-pymssql_0.8.0+dfsg-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHz9wKrSla4ddfhTMRAozuAKCsUnWMjSBYZVfeF8rWfuLj/0xmggCcCHOx
9pLTyWGxdg3kwj+5rHRN1gs=
=udcP
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: