Bug#587154: Sympa upgrade overwrites current .conf files
I found some solution: in /etc/dbconfig-common/sympa.conf, I add dbc_hostname='x.x.x.x' (it should be dbc_dbserver, but in postinst script there is a wrong parameter) Now sympa is trying to connect the server (still having errors - but this is a big step forward ;D -- Tomasz Brzezina -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587154: Sympa upgrade overwrites current .conf files
I have been also bitten by this with sympa-6.1.1~dfsg. I opted for expert (not using dbconfig) mode when installing sympa and the result was: Installation script was saying that there is unknown database type (empty) as of course there was nothing configured in /etc/dbconfig-common/sympa.conf. I had to set database type there even if I don't want to use it. And rerun installation. Then it overwrote my database settings in sympa.conf (comment old out values and set empty/wrong values). And so it again failed installing it. I just could not make values stick. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587154: [Pkg-sympa-devel] Bug#587154: Sympa upgrade overwrites current .conf files
On Mon, Jan 24, 2011 at 09:32:59AM +0100, Mitar wrote: I have been also bitten by this with sympa-6.1.1~dfsg. I opted for expert (not using dbconfig) mode when installing sympa and the result was: Installation script was saying that there is unknown database type (empty) as of course there was nothing configured in /etc/dbconfig-common/sympa.conf. I had to set database type there even if I don't want to use it. And rerun installation. With rerun installation you mean dpkg-reconfigure sympa or...? Then it overwrote my database settings in sympa.conf (comment old out values and set empty/wrong values). And so it again failed installing it. I just could not make values stick. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#587154: [Pkg-sympa-devel] Bug#587154: Sympa upgrade overwrites current .conf files
On Mon, Jan 24, 2011 at 12:54 PM, Jonas Smedegaard d...@jones.dk wrote: With rerun installation you mean dpkg-reconfigure sympa or...? Installation of Sympa fails in configuration phase because of this problems. Rerunning means simply retrying to install Sympa again (which reruns configuration phase again). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587154: [Pkg-sympa-devel] Bug#587154: Bug#587154: Sympa upgrade overwrites current .conf files
On Mon, Jan 24, 2011 at 05:07:03PM +0100, Mitar wrote: On Mon, Jan 24, 2011 at 12:54 PM, Jonas Smedegaard d...@jones.dk wrote: With rerun installation you mean dpkg-reconfigure sympa or...? Installation of Sympa fails in configuration phase because of this problems. Rerunning means simply retrying to install Sympa again (which reruns configuration phase again). Ok. Thanks for clarifying. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#587154: Sympa upgrade overwrites current .conf files
I experience this bug too on every upgrade in the 6.0.x series (most
recently, 6.0.1+dfsg-3), and in my situation it renders the package
uninstallable. I have the database for sympa located on a different
server and no sympa database on the local server. It appears that even
if /etc/dbconfig-common/sympa.conf has the right settings, the
configuration file installed has the corresponding, auto-generated line
commented out -- forcing the localhost default.
My old workaround was to run mysql on the local server just long enough
to make the installation succeed then manually restore sympa.conf and
wwsympa.conf from backups, but this is kludgy. My new workaround is to
run a loop script that restores these files while the upgrade is in
progress so sympa starts from the original config file instead of the
backup and installation succeeds. There seem to be two issues:
#1 The host line in the auto-generated file is commented out, so
dbconfig-common customization of the host line is impossible.
#2 sympa.conf and wwsympa.conf are both replaced by the installer
scripts or scripts invoked by those scripts
The output from a botched installation is below.
a...@kvm03:~$ sudo aptitude install -f
The following partially installed packages will be configured:
sympa
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up sympa (6.0.1+dfsg-3) ...
dbconfig-common: writing config to /etc/dbconfig-common/sympa.conf
apache2: installation seems OK ...
apache2: installation seems OK ...
Reloading web server config: apache2.
DBI connect('sympa:localhost','sympa',...) failed: Can't connect to
local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
at /usr/share/sympa/lib/SQLSource.pm line 176
SQLSource::connect() Can't connect to Database DBI:mysql:sympa:localhost
as sympa
List::check_db_connect() Failed to connect to database
DBI connect('dbname=mysql;host=localhost','root',...) failed: Can't
connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2) at /usr/share/sympa/lib/SQLSource.pm
line 293
SQLSource::create_db() Cannot connect as root to database
Database sympa defined in sympa.conf has not the right structure or is
unreachable. verify db_xxx parameters in sympa.conf
dpkg: error processing sympa (--configure):
subprocess installed post-installation script returned error exit
status 1
configured to not write apport reports
Errors were encountered while
processing:
sympa
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up sympa (6.0.1+dfsg-3) ...
dbconfig-common: writing config to /etc/dbconfig-common/sympa.conf
apache2: installation seems OK ...
apache2: installation seems OK ...
Reloading web server config: apache2.
DBI connect('sympa:localhost','sympa',...) failed: Can't connect to
local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
at /usr/share/sympa/lib/SQLSource.pm line 176
SQLSource::connect() Can't connect to Database DBI:mysql:sympa:localhost
as sympa
List::check_db_connect() Failed to connect to database
DBI connect('dbname=mysql;host=localhost','root',...) failed: Can't
connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2) at /usr/share/sympa/lib/SQLSource.pm
line 293
SQLSource::create_db() Cannot connect as root to database
Database sympa defined in sympa.conf has not the right structure or is
unreachable. verify db_xxx parameters in sympa.conf
dpkg: error processing sympa (--configure):
subprocess installed post-installation script returned error exit
status 1
Errors were encountered while processing:
sympa
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587154: Sympa upgrade overwrites current .conf files
Package: sympa Version: 6.0.1+dfsg-2 Severity: important Hello again, I've found yet another bug in your Sympa 6.0.1+dfsg-2 package from Debian testing. It seems that package upgrade overwrites current Sympa configuration on a server. Fortunately I have a server backup and I didn't lost a content of my /etc/sympa/sympa.conf and /etc/sympa/wwsympa.conf files... Could you please add debian/conffiles file to your source package or use another Debian way to protect Sympa configuration? Have a nice weekend, Pawel Tecza -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587154: Sympa upgrade overwrites current .conf files
On 06/25/2010 04:02 PM, Paweł Tęcza wrote: Package: sympa Version: 6.0.1+dfsg-2 Severity: important Hello again, I've found yet another bug in your Sympa 6.0.1+dfsg-2 package from Debian testing. It seems that package upgrade overwrites current Sympa configuration on a server. Fortunately I have a server backup and I didn't lost a content of my /etc/sympa/sympa.conf and /etc/sympa/wwsympa.conf files... These files are not conffiles and are rewritten on upgrades. Current settings should be honoured unless they affect path settings etc. So please give a detailed report what went wrong. Regards Racke -- LinuXia Systems = http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP = http://www.icdevgroup.org/ Interchange Development Team -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587154: Sympa upgrade overwrites current .conf files
On Fri, 25 Jun 2010 16:14:21 +0200 Stefan Hornburg (Racke) ra...@linuxia.de wrote: On 06/25/2010 04:02 PM, Paweł Tęcza wrote: Package: sympa Version: 6.0.1+dfsg-2 Severity: important Hello again, I've found yet another bug in your Sympa 6.0.1+dfsg-2 package from Debian testing. It seems that package upgrade overwrites current Sympa configuration on a server. Fortunately I have a server backup and I didn't lost a content of my /etc/sympa/sympa.conf and /etc/sympa/wwsympa.conf files... These files are not conffiles and are rewritten on upgrades. Current settings should be honoured unless they affect path settings etc. So please give a detailed report what went wrong. Hi Stefan, At first, thanks a lot for your fast reply! :) Below is diff between my sympa.conf for old and stable Sympa 5.3.4-6.1 and new and testing Sympa 6.0.1+dfsg-2: --- 5.3.4-6.1/sympa.conf2010-06-24 16:54:55.0 +0200 +++ 6.0.1+dfsg-2/sympa.conf 2010-06-25 15:32:57.0 +0200 @@ -160,7 +160,7 @@ ### Web interface ### ## Sympa's main page URL -wwsympa_urlhttp://lista.uw.edu.pl/sympa +wwsympa_url http://lista.uw.edu.pl/wws ## SOAP service URL soap_url http://lista.uw.edu.pl/sympasoap @@ -170,4 +170,6 @@ db_passwd sympa db_user sympa -db_host localhost +# db_host localhost +bounce_warn_rate 30 +bounce_halt_rate 50 As you can see above the changes are rather minor... But here is diff between my sympa.conf for testing Sympa 6.0.1+dfsg-2 and rebuilt Sympa 6.0.1+dfsg-2 with added by me missing .mo files (see my previous bug report #587096): --- 6.0.1+dfsg-2/sympa.conf 2010-06-25 15:25:19.0 +0200 +++ 6.0.1+dfsg-2~ptecza1/sympa.conf 2010-06-25 15:32:51.0 +0200 @@ -49,7 +49,7 @@ ### General definition ### ## Main robot hostname -domain lista.uw.edu.pl +domain lists.gpa.net.icm.edu.pl ## Listmasters email list comma separated ## Sympa will associate listmaster privileges to these email addresses (mail and web interfaces). Some error reports may also be sent to these addresses. @@ -60,7 +60,7 @@ email sympa ## Default lang (cs | de | el | en_US | fr | hu | it | ja_JP | nl | oc | pt_BR | tr) -lang pl +lang en_US ## Who is able to create lists ## This parameter is a scenario, check sympa documentation about scenarios if you want to define one Here the changes are bigger. Package upgrade broke my locale settings. Also it changed my domain. lists.gpa.net.icm.edu.pl is my old and unused domain. Now I use only lista.uw.edu.pl domain. Cheers, Pawel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
