WHATSNEW: Add some information on migrating printers.samba-3.6.14

Thanks to Andreas for providing the text and making sure that it ends up in the
release notes!

Karolin
(cherry picked from commit 5aba70a99dd8d3e7e12a4837c00194eaba5f271c)

1 files changed, 33 insertions, 0 deletions

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index d3ad3bd360f..be09c558148 100644
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -43,6 +43,39 @@ o   Andreas Schneider <asn@samba.org>
     * BUG 9766: Cache name_to_sid/sid_to_name correctly.
 
 
+Note about upgrading from older versions:
+-----------------------------------------
+
+It is still the case that there are printing tdbs (ntprinting.tdb, ntforms.tdb,
+ntdrivers.tdb) which are in latin1 or other encodings. When updating from
+Samba 3.5 or earlier to Samba 3.6 or 4.0 these tdbs need to be migrated to our
+new registry based printing management.  This means during the migration we
+also need to do charset conversion. This can only been done manually cause we don't
+know in which encoding the tdb is. You have to specify the correct code page
+for the conversion, see iconv -l and Wikipedia [1] for the available codepages.
+The mostly used one is Windows Latin1 which is CP1252.
+
+We've extended the 'net printing dump' and 'net printing migrate' commands to
+define the encoding of the tdb. So you can correctly view the tdb with:
+
+  net printing dump encoding=CP1252 /path/to/ntprinters.tdb
+
+or migrate it with e.g.:
+
+  net printing migrate encoding=CP1252 /path/to/ntprinters.tdb
+
+If you migrate printers we suggest you do it in the following order.
+
+ntforms.tdb
+ntdrivers.tdb
+ntprinting.tdb
+
+Don't forget to rename, move or delete these files in /var/lib/samba after the
+migration.
+
+[1] https://en.wikipedia.org/wiki/Code_page
+
+
 ######################################################################
 Reporting bugs & Development Discussion
 #######################################