Bug#651942: Upgrade from sympa_5.3.4-6.1 fails (relation conf_table does not exist)

2012-06-03 Thread Emmanuel Bouthenot 
retitle 651942 upgrades fails while using sympa with postgresql
thanks

-- 
Emmanuel Bouthenot
  mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
  xmpp: kol...@im.openics.org  irc: kolter@{freenode,oftc}



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#651942: Upgrade from sympa_5.3.4-6.1 fails (relation conf_table does not exist)

2012-05-14 Thread Emmanuel Bouthenot 
severity 651942 important
thanks

On Tue, Dec 13, 2011 at 02:10:35PM +0100, Giorgio Volpe wrote:
[...]

 Update from sympa sympa_5.3.4-6.1  to 6.1.7 fails.  I get many
 DBD::Pg::st execute failed: ERROR:  relation conf_table does not
 exist at /usr/share/sympa/lib/Conf.pm line 668. errors.  If i
 manually try to run sympa.pl --upgrade i get the same problem
 (conf_table does not exist errors).

I'm lowering the severity to important as the package is buggy with
Postgres but works fine with other DB engines.

Regards,

M.

-- 
Emmanuel Bouthenot
  mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
  xmpp: kol...@im.openics.org  irc: kolter@{freenode,oftc}




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#651942: Upgrade from sympa_5.3.4-6.1 fails (relation conf_table does not exist)

2012-01-06 Thread David Verdin 

Hi,

Sympa is distributed with queries that recreate the database from 
scratch. For Postgres, you can find it here, for example: 
https://www.sympa.org/distribution/current/src/etc/script/create_db.Pg
Please, pretty please : DON'T USE IT DIRECTLY ON YOUR PRODUCTION 
DATABASE. It is full of drop queries that would erase your preexisting 
data.
However, you can copy the part related to the conf table and apply it 
directly. It will create the table with all the fields and the right 
structure.


I know, this upgrade method sucks. But - and this is a message of hope 
to all the Pg, Oracle and Sybase users around the world - your torments 
will end soon. In the 6.2, we completely revamped the database upgrade / 
usage code and any part related to a given database is now enclosed in a 
dedicated module. That means that we will be able to ask specialists of 
these RDBMS to work on these modules which contain roughly only queries 
(query to create a table, to set a key, to define an index, etc.) and 
Sympa will automagically use them. That means automatic database upgrade 
for any supported RDBMS.


Actually, the work is done for Postgres and I'm going to tackle the 
Oracle part - with all the help I'll be able to find. Any Sybase 
specialist is welcome to contribute.


Cheers,

David

Le 05/01/12 20:00, Giorgio Volpe a écrit :

Il 05/01/2012 17:41, David Verdin ha scritto:

Dear all,

The conf table will be automatically added if you are using mysql or 
SQLite. Other RDBMS-driven databases are not automatically upgraded.

What RDBMS are you using?



OK! Is this the problem?. I use postgres!

Is there a way to upgrade with postgres?

Giorgio

--
*MoVI Regionale FVG
*Via Garibaldi 23, 33038-San Daniele del Friuli.
*Tel*. 0432 943002 - *Cell*. 346 8216304
*Email* giorgio.vo...@movi.fvg.it

Bug#651942: Upgrade from sympa_5.3.4-6.1 fails (relation conf_table does not exist)

2012-01-06 Thread Giorgio Volpe 

OK! I succeeded in upgrading! Thanks to David!

I've not only created conf_table but, by hand, upgraded all database structure. 
(diff  between old and new create_db).
On the bottom of this mail the SQL I've used ... if may be useful for somebody.

Than, when upgrading with apt-get install sympa there was till an error.
I ran sympa.pl --upgrade and get:

 Cannot access cafile /usr/share/sympa/ca-bundle.crt

I copied the old file ca-bundle.crt from 5.4 files and than upgrade went ok 
till the end.

The file was deleted while upgrading debian package: is this an error?

(now problems with wwsympa but this is another story!)

Giorgio

--

alter table user_table add column last_login_date_user  int4;
alter table user_table add column last_login_host_user  varchar (60);
alter table user_table add column wrong_login_count_user  int4;
alter table user_table add column data_user   varchar (255);

alter table subscriber_table add column custom_attribute_subscriber varchar 
(500);
alter table subscriber_table add column suspend_subscriber  smallint;
alter table subscriber_table add column suspend_start_date_subscriberint4;
alter table subscriber_table add column suspend_end_date_subscriber  int4;
CREATE INDEX subscriber_idx2 ON subscriber_table (user_subscriber);

alter TABLE admin_table add column visibility_adminvarchar(20);

CREATE TABLE exclusion_table (
list_exclusion  varchar(50),
user_exclusion  varchar(100),
date_exclusion  int4,
CONSTRAINT ind_exclusion PRIMARY KEY (list_exclusion, user_exclusion)
);
CREATE  INDEX exclusion_idx ON exclusion_table(list_exclusion, user_exclusion);

CREATE TABLE session_table (
id_session  int8 NOT NULL,
start_date_session  int4 NOT NULL,
date_sessionint4 NOT NULL,
remote_addr_session varchar(60),
robot_session   varchar(80),
email_session   varchar(100),
hit_session int4,
data_sessionvarchar(255),
CONSTRAINT ind_session PRIMARY KEY (id_session)
);
CREATE  INDEX session_idx ON session_table(id_session);

CREATE TABLE one_time_ticket_table (
ticket_one_time_ticket  varchar(30),
robot_one_time_ticket   varchar(80),
email_one_time_ticket   varchar(100),
date_one_time_ticketbigint,
data_one_time_ticketvarchar(200),
remote_addr_one_time_ticket varchar(60),
status_one_time_ticket  varchar(60),
CONSTRAINT ind_one_time_ticket PRIMARY KEY (ticket_one_time_ticket)
);
CREATE  INDEX one_time_ticket_idx ON 
one_time_ticket_table(ticket_one_time_ticket);

CREATE TABLE bulkmailer_table(
messagekey_bulkmailer   varchar(80),
packetid_bulkmailer varchar(33),
messageid_bulkmailervarchar(100),
receipients_bulkmailer  text,
returnpath_bulkmailer   varchar(100),
robot_bulkmailervarchar(80),
listname_bulkmailer varchar(50),
verp_bulkmailer smallint,
merge_bulkmailersmallint,
priority_message_bulkmailer int4,
priority_packet_bulkmailer  int4,
reception_date_bulkmailer   int4,
delivery_date_bulkmailerint4,
lock_bulkmailer varchar(30),
constraint ind_bulkmailer PRIMARY KEY (messagekey_bulkmailer, 
packetid_bulkmailer)
);
CREATE INDEX  messagekey_bulkmailer_idx ON 
bulkmailer_table(messagekey_bulkmailer);
CREATE INDEX  packetid_bulkmailer_idx ON bulkmailer_table(packetid_bulkmailer);

CREATE TABLE bulkspool_table (
messagekey_bulkspoolvarchar(33),
messageid_bulkspool varchar(100),
message_bulkspool   text,
lock_bulkspool  smallint,
dkim_privatekey_bulkspool  varchar(100),
dkim_selector_bulkspool varchar(50),
dkim_d_bulkspool varchar(50),
dkim_i_bulkspool varchar(50),
dkim_header_list_bulkspool varchar(500),
constraint ind_bulkspool primary key (messagekey_bulkspool)
);
CREATE INDEX messagekey_bulkspool_idx ON bulkspool_table(messagekey_bulkspool);

CREATE TABLE conf_table (
  robot_conf varchar(80),
  label_conf varchar(80),
  value_conf varchar(300),
  constraint ind_conf primary key (robot_conf,label_conf)
);
CREATE INDEX robot_conf_idx ON conf_table(robot_conf,label_conf);

GRANT ALL on exclusion_table,session_table, one_time_ticket_table, 
bulkmailer_table,bulkspool_table, conf_table TO sympa;

Bug#651942: Upgrade from sympa_5.3.4-6.1 fails (relation conf_table does not exist)

2012-01-05 Thread David Verdin 

Dear all,

The conf table will be automatically added if you are using mysql or 
SQLite. Other RDBMS-driven databases are not automatically upgraded.

What RDBMS are you using?

Regards,

David

Le 19/12/11 23:32, Emmanuel Bouthenot a écrit :

On Mon, Dec 19, 2011 at 10:58:38PM +0100, Giorgio Volpe wrote:

Il 19/12/2011 21.30, Emmanuel Bouthenot ha scritto:

That's sound weird, could you try with the following command: $
/usr/lib/sympa/bin/sympa.pl --upgrade M.

Same result! :-(

I get:
# /usr/lib/sympa/bin/sympa.pl --upgrade
info Configuration file read, default log level 0
DBD::Pg::st execute failed: ERROR:  relation conf_table does not exist at 
/usr/share/sympa/lib/Conf.pm line 668.
err Conf::get_db_conf() Unable to execute SQL statement SELECT
value_conf AS value FROM conf_table WHERE (robot_conf ='*' AND
label_conf ='color_2'): ERROR:  relation conf_table does not exist

And so on ...

After i downgrade back with  dpkg --force-depends -i
sympa_5.3.4-6.1_i386.deb list are alive again... but wwsympa doesn't
work! So I need upgrading. Thanks ...

ok, maybe the following could help a bit more:

$ /usr/lib/sympa/bin/sympa.pl --upgrade --from=5.3.4 --to=6.1.7


M.





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#651942: Upgrade from sympa_5.3.4-6.1 fails (relation conf_table does not exist)

2012-01-05 Thread Giorgio Volpe 

Il 05/01/2012 17:41, David Verdin ha scritto:

Dear all,

The conf table will be automatically added if you are using mysql or 
SQLite. Other RDBMS-driven databases are not automatically upgraded.

What RDBMS are you using?



OK! Is this the problem?. I use postgres!

Is there a way to upgrade with postgres?

Giorgio

--
*MoVI Regionale FVG
*Via Garibaldi 23, 33038-San Daniele del Friuli.
*Tel*. 0432 943002 - *Cell*. 346 8216304
*Email* giorgio.vo...@movi.fvg.it

Bug#651942: Upgrade from sympa_5.3.4-6.1 fails (relation conf_table does not exist)

2011-12-19 Thread Emmanuel Bouthenot 
Hi Giorgio,

Sorry for the late reply,

On Wed, Dec 14, 2011 at 10:50:58AM +0100, Giorgio Volpe wrote:
[...]

 1) Dowloded  
 http://ftp.de.debian.org/debian/pool/main/s/sympa/sympa_6.1.7~dfsg-2_i386.deb
 2) Tried to install with: dpkg -i sympa_6.1.7~dfsg-2_i386.deb

 but the result is the same as before. Many relation conf_table
 does not exist.
 Now i get the following result, if I run
 
 # /usr/lib/sympa/bin/sympa.pl
 DBD::Pg::st execute failed: ERROR:  relation conf_table does not
 exist at /usr/share/sympa/lib/Conf.pm line 668.
 DBD::Pg::st execute failed: ERROR:  relation conf_table does not
 exist at /usr/share/sympa/lib/Conf.pm line 668.
 DBD::Pg::st execute failed: ERROR:  relation conf_table does not
 exist at /usr/share/sympa/lib/Conf.pm line 668.
 DBD::Pg::st execute failed: ERROR:  relation conf_table does not
 exist at /usr/share/sympa/lib/Conf.pm line 668.
 DBD::Pg::st execute failed: ERROR:  relation conf_table does not
 exist at /usr/share/sympa/lib/Conf.pm line 668.
That's sound weird, could you try with the following command:
$ /usr/lib/sympa/bin/sympa.pl --upgrade

M.

-- 
Emmanuel Bouthenot
  mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
  xmpp: kol...@im.openics.org  irc: kolter@{freenode,oftc}




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#651942: Upgrade from sympa_5.3.4-6.1 fails (relation conf_table does not exist)

2011-12-19 Thread Giorgio Volpe 

Il 19/12/2011 21.30, Emmanuel Bouthenot ha scritto:
That's sound weird, could you try with the following command: $ /usr/lib/sympa/bin/sympa.pl --upgrade M. 


Same result! :-(

I get:
# /usr/lib/sympa/bin/sympa.pl --upgrade
info Configuration file read, default log level 0
DBD::Pg::st execute failed: ERROR:  relation conf_table does not exist at 
/usr/share/sympa/lib/Conf.pm line 668.
err Conf::get_db_conf() Unable to execute SQL statement SELECT value_conf AS value FROM conf_table WHERE (robot_conf 
='*' AND label_conf ='color_2'): ERROR:  relation conf_table does not exist


And so on ...

After i downgrade back with  dpkg --force-depends -i sympa_5.3.4-6.1_i386.deb list are alive again... but wwsympa 
doesn't work! So I need upgrading. Thanks ...


Giorgio



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#651942: Upgrade from sympa_5.3.4-6.1 fails (relation conf_table does not exist)

2011-12-19 Thread Emmanuel Bouthenot 

On Mon, Dec 19, 2011 at 10:58:38PM +0100, Giorgio Volpe wrote:
 Il 19/12/2011 21.30, Emmanuel Bouthenot ha scritto:
 That's sound weird, could you try with the following command: $
 /usr/lib/sympa/bin/sympa.pl --upgrade M.
 
 Same result! :-(
 
 I get:
 # /usr/lib/sympa/bin/sympa.pl --upgrade
 info Configuration file read, default log level 0
 DBD::Pg::st execute failed: ERROR:  relation conf_table does not exist at 
 /usr/share/sympa/lib/Conf.pm line 668.
 err Conf::get_db_conf() Unable to execute SQL statement SELECT
 value_conf AS value FROM conf_table WHERE (robot_conf ='*' AND
 label_conf ='color_2'): ERROR:  relation conf_table does not exist
 
 And so on ...
 
 After i downgrade back with  dpkg --force-depends -i
 sympa_5.3.4-6.1_i386.deb list are alive again... but wwsympa doesn't
 work! So I need upgrading. Thanks ...
ok, maybe the following could help a bit more:

$ /usr/lib/sympa/bin/sympa.pl --upgrade --from=5.3.4 --to=6.1.7


M.

-- 
Emmanuel Bouthenot
  mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
  xmpp: kol...@im.openics.org  irc: kolter@{freenode,oftc}




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#651942: Upgrade from sympa_5.3.4-6.1 fails (relation conf_table does not exist)

2011-12-13 Thread Giorgio Volpe 
Package: sympa
Version: 6.1.7~dfsg-1
Severity: grave
Justification: renders package unusable


Update from sympa sympa_5.3.4-6.1  to 6.1.7 fails.
I get many DBD::Pg::st execute failed: ERROR:  relation conf_table does not 
exist at /usr/share/sympa/lib/Conf.pm line 668. errors.
If i manually try to run sympa.pl --upgrade i get the same problem 
(conf_table does not exist errors).




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

Kernel: Linux 2.6.30-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 sympa depends on:
ii  adduser3.112 add and remove users and groups
ii  dbconfig-common1.8.46common framework for packaging dat
ii  debconf [debconf-2.0]  1.5.36Debian configuration management sy
ii  exim4-daemon-heavy [ma 4.77-1+b1 Exim MTA (v4) daemon with extended
ii  libarchive-zip-perl1.30-3Perl module for manipulation of ZI
ii  libc6  2.13-21   Embedded GNU C Library: Shared lib
ii  libcgi-fast-perl   5.14.2-5  CGI::Fast Perl module
ii  libcgi-pm-perl 3.58+dfsg-1   module for Common Gateway Interfac
ii  libdbd-mysql-perl  4.020-1+b1Perl5 database interface to the My
ii  libdbd-pg-perl 2.18.1-1+b1   Perl DBI driver for the PostgreSQL
ii  libdbd-sqlite3-perl1.33-1+b1 Perl DBI driver with a self-contai
ii  libdbd-sybase-perl 1.14-1Sybase/MS SQL database driver for 
ii  libdbi-perl1.616-1+b2Perl Database Interface (DBI)
ii  libfcgi-perl   0.74-1+b1 helper module for FastCGI
ii  libfile-copy-recursive 0.38-1Perl extension for recursively cop
ii  libhtml-format-perl2.04-2format HTML syntax trees into text
ii  libhtml-stripscripts-p 1.03-1module to filter scripts out of HT
ii  libhtml-tree-perl  3.23-2Perl module to represent and creat
ii  libintl-perl   1.20-1Uniforum message translations syst
ii  libio-stringy-perl 2.110-4   Perl modules for IO from scalars a
ii  libmailtools-perl  2.06-1Manipulate email in perl programs
ii  libmime-charset-perl   1.008-1   Perl module for MIME character set
ii  libmime-encwords-perl  1.012-1   Perl interface to deal with RFC 20
ii  libmime-lite-html-perl 1.23-1Transform HTML page into MIME emai
ii  libmime-tools-perl 5.428-1   Perl5 modules for MIME-compliant m
ii  libmsgcat-perl 1.03-5+b2 Locale::Msgcat perl module
ii  libnet-ldap-perl   1:0.4001-2client interface to LDAP servers
ii  libnet-netmask-perl1.9015-4  parse, manipulate and lookup IP ne
ii  libregexp-common-perl  2010010201-1  module with common regular express
ii  libtemplate-perl   2.22-0.1+b2   template processing system written
ii  libterm-progressbar-pe 2.09-6Perl module to print a progress ba
ii  libunicode-linebreak-p 0.0.20110501-1+b1 UAX #14 Unicode Line Breaking Algo
ii  libxml-libxml-perl 1.88+dfsg-1+b1Perl interface to the libxml2 libr
ii  lsb-base   3.2-23.1  Linux Standard Base 3.2 init scrip
ii  mhonarc2.6.16-1  Mail to HTML converter
ii  perl   5.14.2-5  Larry Wall's Practical Extraction 
ii  perl-modules [libcgi-p 5.14.2-5  Core Perl modules
ii  sqlite33.7.9-2   Command line interface for SQLite 
ii  sysklogd [system-log-d 1.5-6 System Logging Daemon

Versions of packages sympa recommends:
ii  ca-certificates  20090814+nmu2   Common CA certificates
ii  doc-base 0.10.3  utilities to manage online documen
ii  libapache2-mod-fastcgi   2.4.6-1 Apache 2 FastCGI module for long-r
ii  libcrypt-ciphersaber-per 0.61-4  Perl module implementing CipherSab
ii  libfile-nfslock-perl 1.20-2  perl module to do NFS (or not) loc
ii  libio-socket-ssl-perl1.33-1  Perl module implementing object or
ii  libmail-dkim-perl0.39-1  cryptographically identify the sen
ii  libsoap-lite-perl0.712-1 Perl implementation of a SOAP clie
ii  locales  2.13-21 Embedded GNU C Library: National L
ii  logrotate3.7.8-6 Log rotation utility
ii  mysql-server 5.1.58-1MySQL database server (metapackage
ii  mysql-server-5.1 [mysql- 5.1.49-2MySQL database server binaries and
ii  postgresql   8.4.5-0squeeze1 object-relational SQL database (su

Versions of packages sympa suggests:
ii  apache2   2.2.21-2   Apache HTTP Server metapackage
ii  apache2-mpm-itk [httpd-cgi]   2.2.21-2   multiuser MPM for Apache 2.2
ii  libapache2-mod-fcgid

Bug#651942: Upgrade from sympa_5.3.4-6.1 fails (relation conf_table does not exist)

2011-12-13 Thread Emmanuel Bouthenot 
Hi Giorgio,

On Tue, Dec 13, 2011 at 02:10:35PM +0100, Giorgio Volpe wrote:
 Package: sympa
 Version: 6.1.7~dfsg-1
 Severity: grave
 Justification: renders package unusable
 
 
 Update from sympa sympa_5.3.4-6.1  to 6.1.7 fails.
 I get many DBD::Pg::st execute failed: ERROR:  relation conf_table
 does not exist at /usr/share/sympa/lib/Conf.pm line 668. errors.  If
 i manually try to run sympa.pl --upgrade i get the same problem
 (conf_table does not exist errors).
This error should be fixed with sympa 6.1.7~dfsg-2 which is already in
unstable, could you try to upgrade your system with the latest version ?


M.

-- 
Emmanuel Bouthenot
  mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
  xmpp: kol...@im.openics.org  irc: kolter@{freenode,oftc}




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org