Source: postgresql-10
Version: 10.3-1
Severity: wishlist
Tags: patch

Hi,

Thank you so much for caring about users etc. and including NEWS
entries for display by apt-listchanges.

However, I did feel that the most recent entry could be slightly
improved. I have attached a patch with my suggested changes; they
should be self-explanatory. :)


Best wishes,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      la...@debian.org / chris-lamb.co.uk
       `-
diff --git a/debian/postgresql-10.NEWS b/debian/postgresql-10.NEWS
index a7a639b..bf9aa00 100644
--- a/debian/postgresql-10.NEWS
+++ b/debian/postgresql-10.NEWS
@@ -1,14 +1,16 @@
 postgresql-10 (10.3-1) unstable; urgency=medium
 
-  If you run an installation in which not all users are mutually trusting, or
-  if you maintain an application or extension that is intended for use in
-  arbitrary situations, it is strongly recommended that you read the release
-  notes regarding changes around "search_path", and take suitable steps to
-  ensure that your installation or code is secure.
-
-  Also, these changes may cause functions used in index expressions or
-  materialized views to fail during auto-analyze, or when reloading from a
-  dump.  After upgrading, monitor the server logs for such problems, and fix
+  If you run an installation where the users are mutually trusting or if you
+  maintain an application or extension that is intended for use in arbitrary
+  situations, it is highly recommended that you read the release notes
+  regarding changes around "search_path", and take suitable steps to ensure
+  that your installation or code is secure:
+
+    https://www.postgresql.org/docs/10/static/release-10-3.html#id-1.11.6.5.5
+
+  In addition, these changes may cause functions used in index expressions or
+  materialized views to fail during auto-analyze or when reloading from a dump.
+  After upgrading, please monitor the server logs for such problems and fix any
   affected functions.
 
  -- Christoph Berg <christoph.b...@credativ.de>  Tue, 27 Feb 2018 12:57:11 
+0100

Reply via email to