Merge branch 'release/1.0.7' into develop
abort in extract_identifier if an identifier cannot be found

- previously due to a logic bug this would just return the
  original line (value[0:-1])
categorize --flush-privileges section

- If --flush-privileges is used in a mysqldump there will be
  a section immediately after the "mysql" system database
  creation that issues a FLUSH PRIVILEGES.  This is noted
  by a comment block that starts with "-- Flush Grant Tables",
  which categorize_section() now detects properly
tweak parse_section() terminate condition

- previously parse_section terminated when it saw any line
  that started with a sql comment ("--"); now it terminates
  only on a blank comment indicating the start of a comment
  block (line == "--").  This fixes the problem of parsing
  --master-data=2 where the change master line is a comment
  and also has the effect of folding the "Dump completed"
  line into the footer which is currently ignored by default
  anyway.
output skipped lines to debug output
update CHANGES for issue#33

- Resolves issue #33
Merge branch 'feature/issue#33' into develop
bump version to 1.0.8-dev
fix bug with mysql 4.1 MYSQL_TYPE_VAR_STRING default values

- previously var_string types were treated identically to modern
  MYSQL_TYPE_VARCHAR, but this is not the case.  Instead this
  type's default value buffer should be interpretted as a fixed
  width string with trailing whitespace padding.  This whitespace
  is stripped from the end on output.
  Resolves issue #36
handle io errors when reading mysql bootstrap files

- previously io errors resulted in uncaught exceptions if the
  expected .sql bootstrap files could not be opened.  This
  causes dbsake to fail somewhat more gracefully with a clearer
  error message.
  Resolves issue #37
add debug logging when .frm parsing fails

- previously the interesting traceback was supresssed in all
  cases.  Now if --debug is enabled a traceback is output to
  help debugging for cases where frm-to-schema is doing something
  incorrectly.
add more consistency to formatting of .frm files

- remove use of __str__() for implicit string conversions.
  This becomes a big headache for python3 compatibility and
  leads to inconsistent behavior.  Instead the pattern of
  definiting a format() method on each class is used to
  always return unicode strings
- consistently use unicode_literals pragma through frm code
  to help ensure we're generating unicode strings and help
  with future python3 compatibility
- always decode metadata using utf-8 and be more consistent
  about converting these values.  Resolves issue #38
Merge branch 'feature/issue#38' into develop
update CHANGES to document recent bugfixes
include charset / collation when formatting TEXT blob types

- this has been done for all the other string types, but blob
  types with a defined character set were only formatted with
  the bare type name, even if the column charset differed from
  the table charset. This should make dbsake output somewhat
  more in-line with what SHOW CREATE TABLE produces and more
  correct in cases where a TEXT type's charset or collation
  differs from the table default.
  Resolves issue #40
search for bootstrap files in /usr/share/percona-server

- Recent versions of Percona-Server move the share / language files
  to /usr/share/percona-server rather than /usr/share/mysql. This
  change causes dbsake to conditionally search /usr/share/percona-server
  before /usr/share/mysql if it looks like the target is percona server
  Resolves issue #41
cleanup logging

- only log the uncompressed vs. extracted tarball size in debug
  mode.  This was causing confusion with some users and in general
  I suppose its not useful information.
- demote some bootstrapping messages to debug level
- demote many distribution_from_system log messages to debug level
- demote many distribution_from_download log messages to debug level
update CHANGES
bump release data in CHANGES
bump version in contrib/dbsake.spec