Package: python2.3-maxdb
Version: 7.5.00.24-3
Severity: important
Tags: patch
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686-smp
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages python2.3-maxdb depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii python2.3 2.3.5-3 An interactive high-level object-o
-- no debconf information
The module 'sdb.dbapi' imports from the non-existing module 'sapdb' (which
should be 'sdb' instead). This is the reason why no DBSIG2 is available for
MaxDB atm. The following patch will solve the problem:
--- dbapi.py 2005-06-01 16:28:29.186348207 +0200
+++ dbapi-org.py 2005-06-01 16:28:17.479136193 +0200
@@ -45,7 +45,7 @@
_connectionLock = _PseudoLock ()
-import sdb.sql
+import sapdb.sql
apilevel = '2.0'
@@ -58,9 +58,9 @@
# print call, args
result = apply (call, args)
# print '==>', result
- except sdb.sql.SQLError, err:
+ except sapdb.sql.SQLError, err:
raise ProgrammingError (err)
- except sdb.sql.CommunicationError, err:
+ except sapdb.sql.CommunicationError, err:
raise OperationalError (err)
return result
@@ -107,7 +107,7 @@
configString = string.join (['genericResults=true'] + configList, '&')
try:
_connectionLock.acquire ()
- self.__connection = wrapCall (sdb.sql.connect, user, password,
+ self.__connection = wrapCall (sapdb.sql.connect, user, password,
database, host, configString)
finally:
_connectionLock.release ()
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
