setup: reformat glibc collation warning

* bin/postgresql-setup.in (GLIBC_COLLATION_WARN_STRING): Align to 80 characters, and drop the additional WARNING: keyword.
devexp-db · Mar 5, 2019 · f4483e0 · f4483e0
1 parent 2e29d57
commit f4483e0
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 7 deletions.
diff --git a/NEWS b/NEWS
@@ -2,7 +2,7 @@
 
 New in 8.4 version:
 
-*
+* Reformatted glibc collation warning after pg_upgrade.
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

diff --git a/bin/postgresql-setup.in b/bin/postgresql-setup.in
@@ -123,12 +123,12 @@ Environment:
 
 # Warning about possible glibc collation changes BZ#1668301
 GLIBC_COLLATION_WARN_STRING="\
-WARNING: If you've just upgraded your database from a previous major
-version of Fedora or RHEL, please run reindexdb against your databases.
-Core library collation data may have changed and this will invalidate
-database indexes.  For example, in Fedora 28 and RHEL 8 there have been
-extensive changes in glibc collations to support ISO 14651:2016 (Unicode
-9.0.0 data) and your indexes may be affected: https://sourceware.org/ml/libc-announce/2018/msg00002.html"
+If you've just upgraded your database from a previous major version of Fedora or
+RHEL, please run reindexdb against your databases.  Core library collation data
+may have changed and this will invalidate database indexes.  For example, in
+Fedora 28 and RHEL 8 there have been extensive changes in glibc collations to
+support ISO 14651:2016 (Unicode 9.0.0 data) and your indexes may be affected:
+https://sourceware.org/ml/libc-announce/2018/msg00002.html"
 
 print_version()
 {