Bug#596869: Possible unblock for fusionforge/5.0.2-1
retitle 596869 unblock: fusionforge/5.0.2-1
thanks
On Tue, Sep 14, 2010 at 18:49:55 +0200, Roland Mas wrote:
>> I'd like to ask for permission for an upload of FusionForge 5.0.2, which
[...]
Julien Cristau, 2010-09-15 23:41:35 +0200 :
> Based on your summary, this sounds fine.
Thanks. It's being uploaded right now, with an extra one-line patch
fixing #596931:
=== modified file 'gforge/deb-specific/install-db.sh'
--- gforge/deb-specific/install-db.sh 2010-08-30 11:32:12 +0000
+++ gforge/deb-specific/install-db.sh 2010-09-16 08:14:05 +0000
@@ -190,7 +190,7 @@
if su -s /bin/sh postgres -c "/usr/bin/psql template1" 1> $tmp1 2> $tmp2 <<EOF \
&& [ "$(tail -n +2 $tmp1 | head -1)" = 'CREATE DATABASE' ] ;
SET LC_MESSAGES = 'C' ;
-CREATE DATABASE $db_name WITH ENCODING 'UNICODE';
+CREATE DATABASE $db_name WITH TEMPLATE template0 ENCODING 'UNICODE';
EOF
then
# Creation OK
This creates the database using the “template0” template rather than the
“template1” one; both can be declared as using any encodings (and when
PostgreSQL has been installed in the C locale, for instance, they're
using SQL_ASCII), but template0 is guaranteed to be empty, so PostgreSQL
special-cases it and allows creating new databases from it even if the
encoding differs. Which allows us to create the “gforge” database with
the UNICODE encoding in those cases.
Roland.
--
Roland Mas
If you're ever confused as to which mode you're in, keep entering the
<escape> key until vi beeps at you. -- nvi manual page.
Reply to: