Bug#556188: gforge-db-postgresql: Postgres configuration for pg_hba.conf ambiguous
Hi.
Thinking about this issue, I wonder if it wouldn't be easier to have
FusionForge use its own PostGreSQL cluster instead of the default one ('main')
which is created by postgres upon installation.
Why not use pg_createcluster to create a dedicated cluster for it ?
Maybe this is completely naive suggestion, as I'm not really competent in
PostGres matters.
What's your opinion ?
Best regards,
On Sat, Nov 14, 2009 at 06:49:34AM +0100, Olivier Berger wrote:
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.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556188: gforge-db-postgresql: Postgres configuration for pg_hba.conf ambiguous
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 debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556188: gforge-db-postgresql: Postgres configuration for pg_hba.conf ambiguous
found 556188 fusionforge/5.0.1+svn10155-1 thanks 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. This still happens to me on a system where I have had to configure postgres beforehands. It looks like this ain't solved for squeeze still :-( Maybe this package deserves more love ? Best regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556188: gforge-db-postgresql: Postgres configuration for pg_hba.conf ambiguous
Package: gforge-db-postgresql Version: 4.8.1-2 Severity: normal 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. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
