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

Bug#424067: marked as done (ITP: python-sasync -- asynchronous access for SQLAlchemy)

Your message dated Sun, 19 Aug 2007 13:21:30 +0000
with message-id <E1IMkig-00046p-Vp@ries.debian.org>
and subject line Bug#424067: fixed in python-sasync 0.6-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)
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Eric Evans <eevans@debian.org>


* Package name    : python-sasync
  Version         : 0.4
  Upstream Author : Edwin A. Suominen <ed@eepatents.com>
* URL             : http://foss.eepatents.com/sAsync
* License         : GPL
  Programming Lang: Python
  Description     : asynchronous access for SQLAlchemy

An enhancement to the SQLAlchemy package that provides asynchronous
deferred-result access via the Twisted framework and an access broker
for conveniently managing database access, table setup, and 
transactions. Included are modules for implementing persistent
dictionaries, three-dimensional arrays, and graph objects.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (700, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
Eric Evans
eevans@sym-link.com

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Source: python-sasync
Source-Version: 0.6-1

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

python-sasync_0.6-1.diff.gz
  to pool/main/p/python-sasync/python-sasync_0.6-1.diff.gz
python-sasync_0.6-1.dsc
  to pool/main/p/python-sasync/python-sasync_0.6-1.dsc
python-sasync_0.6-1_all.deb
  to pool/main/p/python-sasync/python-sasync_0.6-1_all.deb
python-sasync_0.6.orig.tar.gz
  to pool/main/p/python-sasync/python-sasync_0.6.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 424067@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Eric Evans <eevans@debian.org> (supplier of updated python-sasync 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: Sun, 05 Aug 2007 13:31:37 -0500
Source: python-sasync
Binary: python-sasync
Architecture: source all
Version: 0.6-1
Distribution: unstable
Urgency: low
Maintainer: Eric Evans <eevans@debian.org>
Changed-By: Eric Evans <eevans@debian.org>
Description: 
 python-sasync - asynchronous database access for python using SQLAlchemy
Closes: 424067
Changes: 
 python-sasync (0.6-1) unstable; urgency=low
 .
   * Initial release. (Closes: #424067)
Files: 
 b5455c26a73fe902c53bb5d52545866f 646 python optional python-sasync_0.6-1.dsc
 f1ecc32bd0e234fbf6c575af43aac9e7 41740 python optional python-sasync_0.6.orig.tar.gz
 c2e991218d7bdf8debbb5bc8348a4330 1899 python optional python-sasync_0.6-1.diff.gz
 f304a3a19bf6924c3cede4d5d95cd694 23202 python optional python-sasync_0.6-1_all.deb

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

iD8DBQFGtibU+DWPovKDPJMRAhITAJ9dzvmM3tY5K4trkU4YXZ8XEgB10wCgoj6d
1SrlAGqjHtAq8aCZzu5mfyI=
=mHCU
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: