On Sat, Nov 14, 2009 at 06:49:34AM +0100, Olivier Berger wrote:
> Hi.
> 
> Upon installation of fusionforge 4.8.1 on testing, one is prompted (every 
> time ?) with UCF about conflicting changes on 
> /etc/postgresql/8.3/main/pg_hba.conf :
> "A new version of configuration file /etc/postgresql/8.3/main/pg_hba.conf is 
> available, but the version installed currently has been locally modified."
> 
> This is really not intuitive and would need to be non-ambiguous.
> 
> In the installation test I'm doing, the postgres installation is made as a 
> dependency of it, so no prior configuration was made by the user. Then, 
> pg_hba.conf is what it should be right after postgres-8.3 has installed it. 
> So there has been no user configuration.
> 
> The default option prompted by UCF is to keep the installed version, however, 
> by looking at the diffs, it seems that the best thing to do might be to 
> install the new version with additions made by gforge-db-postgresql's 
> postinst.
> 
> Is UCF used the right way ? Ain't it another way to deal with such cases when 
> no one made any modifications and the postinst's version can be applied 
> safely ?
> 
> Thanks in advance.
> 

Btw, if choosing the wrong option, the error message is like :
DBI connect('dbname=gforge;port=5432','gforge',...) failed: FATAL:  
authentification Ident ?chou?e pour l'utilisateur << gforge >> at 
/usr/share/gforge/lib/include.pl line 25
Uncaught exception from user code:
        Error while connecting to database:  at 
/usr/share/gforge/lib/include.pl line 27.
 at /usr/share/gforge/lib/include.pl line 27
        main::db_connect called at /usr/share/gforge/bin/db-upgrade.pl line 33
dpkg : erreur de traitement de gforge-db-postgresql (--configure) :
 le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 255
Des erreurs ont été rencontrées pendant l'exécution :
 gforge-db-postgresql

Hope this helps finding the bug by search engines.

Best regards,



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

Reply via email to