Package: tinyerp-server
Version: 4.0.3-2
Severity: important

hi,

thank you for providing tinyerp.

upstream sqlalchemy does support either psycopg or psycopg2, 
but would use the second if both installed. since the support 
of psycopg1 to some sa actions is limited, sa maintainer has 
decided to conflict sa with psycopg1, thus with tinyerp-server too.

sa is a very important package, and turbogears (which provides 
tinyerp web access) depends on it.

i'm sure you know about this conflict, but here is a solution:
if package psycopg1 would depend on psycopg2, each program will 
have the choice of which psycopg to import, so sa (and mezogis, 
which i'm maintaining) would use psycopg2, and will allow other 
programs to use psycopg1.


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

Kernel: Linux 2.6.21-2-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages tinyerp-server depends on:
ii  adduser                    3.105         add and remove users and groups
ii  python                     2.4.4-6       An interactive high-level object-o
ii  python-libxml2             2.6.30.dfsg-2 Python bindings for the GNOME XML 
ii  python-libxslt1            1.1.22-1      Python bindings for libxslt1
ii  python-psycopg2            2.0.6-1       Python module for PostgreSQL
ii  python-reportlab           2.0dfsg-1     ReportLab library to create PDF do
ii  python-support             0.7.3         automated rebuilding support for p
ii  python-xml                 0.8.4-8       XML tools for Python

Versions of packages tinyerp-server recommends:
pn  graphviz                      <none>     (no description available)
ii  postgresql-8.1                8.1.10-1   object-relational SQL database, ve
pn  postgresql-client             <none>     (no description available)
ii  python-imaging                1.1.6-1    Python Imaging Library
pn  python-pyparsing              <none>     (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to