./databases/p5-App-Sqitch, Sane database change management

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 0.9998, Package name: p5-App-Sqitch-0.9998, Maintainer: schmonz

Sqitch is a VCS-aware SQL change management application. What makes
it different from your typical migration-style approaches? A few

* No opinions
* Native scripting
* VCS integration
* Dependency resolution
* No numbering
* Bundling
* Reduced duplication

Required to run:
[textproc/p5-String-ShellQuote] [www/p5-URI] [misc/p5-Locale-libintl] [databases/p5-DBI] [lang/perl5] [security/p5-Digest-SHA] [time/p5-DateTime] [devel/p5-IO-Pager] [devel/p5-Scalar-List-Utils] [devel/p5-File-HomeDir] [devel/p5-List-MoreUtils] [devel/p5-Path-Class] [devel/p5-Devel-StackTrace] [devel/p5-Clone] [devel/p5-Sub-Exporter] [devel/p5-IPC-Run3] [devel/p5-Hash-Merge] [devel/p5-SUPER] [devel/p5-Term-ANSIColor] [devel/p5-namespace-autoclean] [devel/p5-IPC-System-Simple] [devel/p5-Try-Tiny] [devel/p5-Config-GitLike] [textproc/p5-Template-Tiny] [devel/p5-Throwable] [textproc/p5-Encode-Locale] [devel/p5-Moo] [textproc/p5-String-Formatter] [www/p5-URI-db] [devel/p5-PerlIO-utf8_strict] [devel/p5-Type-Tiny] [devel/p5-Type-Tiny-XS]

Required to build:
[textproc/p5-Text-Diff] [databases/p5-DBD-SQLite] [devel/p5-Test-Exception] [devel/p5-Test-NoWarnings] [devel/p5-Module-Build] [devel/p5-Test-Deep] [devel/p5-Test-File-Contents] [devel/p5-Test-MockModule] [devel/p5-Capture-Tiny] [devel/p5-Module-Runtime] [devel/p5-Test-Dir] [devel/p5-Test-File] [pkgtools/cwrappers]

Master sites: (Expand)

SHA1: 12659220aff24f2866808e9227b1a0d5f379c8fa
RMD160: f147fe5a87735fd7ec8d43d7071d7e7f3f97b2e3
Filesize: 554.13 KB

Version history: (Expand)

CVS history: (Expand)

   2018-10-05 12:37:39 by Amitai Schleier | Files touched by this commit (3) | Package updated
Log message:
Update to 0.9998. From the changelog:

- Fixed an issue where Sqitch would sometimes truncate the registry
  version number fetched from MySQL, most likely because the Perl runtime
  was using 32-bit integers. Fixed by casting the version to CHAR in the
  query, before Perl ever see it. Thanks to Allen Godfrey David for the
- Added the Snowflake engine.
- Now require URI::db v0.19 for Snowflake URI support.
- The Vertica and Exasol engines now require DBD::ODBC 1.59, which fixes
  a Unicode issue. Thanks to Martin J. Evans for the quick fix
- Added the `bundle` command to `./Build`. This command installs only the
  runtime dependencies into the `--install_base` directory. This should
  simplify building distribution packages, binary installs, Docker images,
  and the like.
- Added the `--with` option to `./Build`, to require that Sqitch be build
  with the specified engine. Pass once for each engine. See the README
  for the list of supported engines.
- Added a check for Hash::Merge 0.298 during installation, since that
  release has a fatal bug that breaks Sqitch. If it's installed, the
  installer will issue a warning and added v0.299 to its list of
  dependencies. Thanks to Slaven Rezić for the suggestion (#377).
- Fixed the PostgreSQL engine so it properly checks the `psql` client
  version to determine whether or not the `:registry` variable is
  supported. Previously it relied on the server version, which would fail
  if the server version was greater than 8.4 but the `psql` client was
  not. Thanks to multiple folks reporting issues with registry names and
  search paths (#314).
- The plan parser will now complain if a change specifies a duplicate
  dependency. This should be less confusing than a database unique
  violation. Thanks to Eric Bréchemier for the suggestion (#344).
- Moved the project to its own GitHub organization:
- Fixed likely cause of Oracle buffer allocation bug when selecting
  timestamp strings. Thanks to @johannwilfling for the bug report and to
  @nmaqsudov for the analysis and solution (#316).
- Changed the way the conninfo string is passed to `psql` to eliminate
  argument ordering problems on Windows. Thanks to @highlowhighlow for
  the report (#384).
- Added `$SQITCH_USERNAME` environment variable to complement
  `$SQITCH_PASSWORD`. It can be used to override the username set in
  for a target.
- Added the `$SQITCH_FULLNAME` and `$SQITCH_EMAIL` environment
  variables, which take precedence over the values of the `user.name` and
  `user.email` config variables.
  `$SQITCH_ORIG_EMAIL` environment variables. For those situations when
  Sqitch attempts to read OS data for user information, These new
  environment variables override these system-derived values. The
  intention is to allow an originating host to set these values on
  another host where Sqitch will actually execute.
- Fixed an error triggered by whitespace trailing an engine name in the
  configuration. Thanks to Jeremy Simkins for the report (#400).
- Refactored the engine-specific username and password attributes to
  support a consistent search for values. Sqitch searches first for one
  of its own environment variables (`$SQITCH_USERNAME` and
  `$SQITCH_PASSSWORD`), then the target URI, and finally any engine-
  specific values, which might include additional environment variables,
  configuration files, the system user, or none at all.
- Database engines that implicitly relied on username and/or password
  environment variables or on the system username now explicitly rely on
  them. These include the Firebird, MySQL, Postgres, and Vertical
  engines. This change should exhibit no change in the behavior of these
- Added support for the `$MYSQL_HOST` and `$MYSQL_TCP_PORT` environment
  variables to the MySQL engine.
- Documented all supported engine-specific environment variables in the
  sqitch-environment guide.
- Renamed the sqitch-passwords guide to sqitch-authentication and added a
  section on username specification.
- Updated all URLs to use the https scheme. Only exceptions are tt2.org,
  which doesn't support TLS, and conferences.embarcadero.com, which
  appears to be down.

pkgsrc changes:

- Add options: mysql odbc oracle pgsql sqlite
   2018-08-22 11:48:07 by Thomas Klausner | Files touched by this commit (3558)
Log message:
Recursive bump for perl5-5.28.0
   2018-03-18 09:31:13 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
p5-App-Sqitch: update to 0.9997.

Add some missing dependencies.

0.9997 2018-03-15T21:13:52Z
     - Fixed the Firebird engine to properly detect multiple instances of a
       change specified to `revert` and `verify`, matching the behavior of
       displaying tag-qualified alternates added to the other engines in
     - Fixed test failure on Windows.
     - Updated the MySQL and PostgreSQL tests to use process-specific database
       names, to try to avoid conflicts when tests are being run by multiple
       processes on the same box, as happens with CPAN smoke testing boxes.
     - Fixed an issue where Sqitch would sometimes truncate the registry
       version number fetched from Postgres, most likely because the Perl
       runtime was using 32-bit integers. Fixed by casting the version to text
       in the query, before Perl ever see it. Thanks to Malte Legenhausen for
       the report (#343).
     - The MySQL engine will now read the username from MySQL configuration
       files. Thanks to Eliot Alter for the bug report (#353).
     - Added Italian translation, with thanks to Luca Ferrari and @BeaData!
     - Improved multi-value config examples in the `sqitch-config`
       documentation to be a bit less confusing. Thanks to Emil for reporting
       where he got confused!
     - Added the Exasol engine. Thanks to Johan Wärlander for the PR (#362)!
     - Fixed an issue where URI::db needed to be explicitly loaded. Thanks to
       Hugh Esco for the report (#370)!
     - Changed the exit value for `rebase` and `revert` from 1 to 0 when there
       is no work to do. This is to match the expectation of non-zero exit
       statuses only when a command is unsuccessful, as well as the behavior
       of `deploy` as of v0.995. Nothing to do is considered successful.
       Thanks to Paul Williams for the PR (#374)!
     - Update `psql` options to use a conninfo string to honor connection
       parameter key words for PostgreSQL targets. It can now take advantage
       of the connection service file using `db:pg:///?service=$PGSERVICE` as
       well as other connection parameters. Thanks to Paul Williams for the PR
   2017-07-23 02:28:37 by Amitai Schleier | Files touched by this commit (2) | Package updated
Log message:
Update to 0.9996. From the changelog:

- Fixed an error where Oracle sometimes truncated timestamp formats so
  that date parsing failed. Thanks to Johann Wilfling for the report and
  @nmaqsudov for the solution (#316).
- Added pager configuration, prioritizing the new `core.pager`
  configuration variable over the `$PAGER` environment variable. The new
  `$SQITCH_PAGER` environment variable trumps all. Thanks to Yati Sagade
  for the pull request (#329).
- Documented the `core.editor` configuration variable.
- Updated PostgreSQL registry detection to avoid errors when not running
  Sqitch as a superuser and the registry schema already exists. Done by
  looking for the `changes` table in the `pg_tables` view instead of
  looking for the registry schema in the `pg_namespace` catalog table,
  and by using `CREATE SCHEMA IF NOT EXISTS` on PostgreSQL 9.3 and
  higher. Thanks to @djk447 for the pull request (#307).
- Updated PostgreSQL registry detection to avoid errors when the `psql`
  client is newer than the server version. Sqitch now fetches the version
  from the server instead of parsing it from the client.
- Specifying a change before a target name on the command-line no longer
  ignores the target (#281).
- The `--db-*` options are now more consistently applied to a target,
  including when the target is specified as a URI (#293).
- `HEAD` and `ROOT` are now properly recognized as aliases for `@HEAD`
  and `@ROOT`, when querying the database. This was supposedly done in
  v0.991, but due to a bug, it wasn't really. Sorry about that.
- The `revert` and `verify` commands will now fail if a change is
  specified and matches multiple changes. This happens when referencing a
  reworked change only by its name. In this case, Sqitch will emit an
  error listing properly tag-qualified changes to use. Suggested by Jay
  Hannah (#312).
- Sqitch no longer returns an error when a target name is passed to a
  command and the default target's plan file does not exist (#324).
- Added missing options to the `rework` usage statement. Thanks to Jay
  Hannah for the PR (#342).
- Passing an engine name or plan file as the `<database>` parameter to
  the `log`, `status`, and `upgrade` commands now works correctly,
  matching what the documention has said for some time (#324).
- Added the `--target` option to the `plan` and `show` commands.
- Added the `<database>` parameter to the `plan` command.
- Sqitch now loads targets from all config files, not just the local
  file, when trying to determine if a `<database>` parameter is a plan
  file name.
- Improved the error message when a change is found more than once in a
  plan, typically a reworked changed referenced only by name. The error
  will no longer be "Key at multiple indexes", but "Change is \ 
  Please specify a tag-qualified change:", followed by a list of
  tag-qualified variants of the change.
- Fixed a bug where the verify command would return a database error when
  it finds no registory. Now it reports that the registry wasn't found in
  the database.
   2017-06-05 16:25:36 by Ryo ONODERA | Files touched by this commit (2298)
Log message:
Recursive revbump from lang/perl5 5.26.0
   2016-07-28 14:40:58 by Wen Heping | Files touched by this commit (2) | Package updated
Log message:
Update to 0.9995

Upstream changes:
0.9995 2016-07-27T09:23:55Z
     - Taught the `add` command not to ignore the `--change` option.
     - The `add` command now emits a usage statement when no change name is
       passed to it.
     - The `add` command now helpfully suggests using the --change option when
       attempting to add a change with the same name as a target. Thanks to
       Ivan Nunes for the report!
     - The `tag` command now helpfully suggests using the --tag option when
       attempting to add a tag with the same name as a target.
     - Added `--global` as an alias for `--user` to the `config` command. This
       alias benefits the muscle memory of Git users.
     - Added a note for Git users to the `sqitch-revert` documentation, to
       head off potential confusion with `git revert`. Thanks to Eric
       Br矇chemier for the "time travel" analogy and wording.
     - Fixed an "uninitialized value" error when creating a registry \ 
       on Windows. Thanks to Steven C. Buttgereit for the report (Issue #289).
     - Fixed editor selection to prioritize the `core.editor` configuration
       variable over the `$EDITOR` environment variable. The `$SQITCH_EDITOR`
       environment variable still trumps all. Thanks to Jim Nasby for the pull
       request (#296).
     - Added detection of the `$VISUAL` environment variable to Editor
       selection, prioritzed after the `core.editor` configuration variable
       and before the `$EDITOR` environment variable. Thanks to Jim Nasby for
       the pull request (#296).
     - Updated the DateTime code to set the locale via `set_locale()` instead
       of `set()`, as the latter may actually change the local time
       unintentionally, and has been deprecated since DateTime v1.04. Thanks
       to Dave Rolsky for the pull request (#304).

0.9994 2016-01-08T19:46:43Z
     - Reduced minimum required MySQL engine from 5.1.0 to 5.0.0. Thanks to
       @dgc-wh for testing it (Issue #251).
     - Fixed floating-point rounding issue with SQLite registry versions on
       Perls with 16-byte doubles. Thanks to H. Merijn Brand for the report
       and testing.
     - Fixed an error when adding an engine with the `engine` command. Thanks
       to Victor Mours for the report and fix!
     - Updated the Oracle engine to support Oracle Wallet connection strings,
       where no username or host is in the connection URI. Thanks to Timothy
       Procter for the patch!
     - Improved the installer's selection of the prefix in which to install
       `etc` files to better match the `--installdirs` option, which defaults
       to the "site" directories. Thanks to @carragom for the pull request
     - Added missing dash to `-engine` in sample calls to `sqitch init` in the
       tutorials. Thanks to Andrew Dunstan for the spot (Issue #268).
     - Fixed broken Vertica documentation links.
     - Attempting to revert a database with no associated registry no longer
       reports the registry as version 0, but correctly reports that no
       registry can be found. Thanks to Arnaldo Piccinelli for the spot (Issue
     - Fixed the search for change IDs in engines to match the search for
       changes. Specifically, change ID seaerch now properly handles the
       offset characters `~` and `^`. This bug mainly affected the `verify`
       command, but it's good to address the inconsistency, done mainly by
       adding the `find_change_id` and `change_id_offset_from_id` methods to
       complement the `find_change` and `change_offset_from_id` methods.
       Thanks to Andrew Dunstan for the spot (Issue #272).
     - Fixed the `flips` table example in the MySQL tutorial. It was
       inappropriately copied from the PostgreSQL tutorial at some point.
       Thanks to Jeff Carpenter for the spot (Issue #254)!

0.9993  2015-08-17T17:55:26Z
     [Bug Fixes]
     - Eliminated test failures due to warnings from DateTime::Locale when
       `LC_TIME` is set to C.UTF-8. Thanks to Shantanu Bhadoria for the report
       and Dave Rolsky for the workaround.
     - Fixed an error checking the registry version when the local uses a
       comma for decimal values. Thanks to Steffen Mç¾¹ller for the report
       (Issue #234).
     - Worked around an error setting the MySQL storage engine using versions
       of DBI prior to 1.631. Thanks to melon-babak for the report!
     - Fixed an error from the Oracle engine when deploying more than 1000
       changes. Thanks to Timothy Procter and Minh Hoang for the report and
       testing the fix.
     - Fixed a bunch of typos in error messages, comments, and documentation.
       Thanks to Dmitriy for the pull request!
     - Fixed test failures due to new warnings from File::Path on Perl
     - On Firebird, Looking up a change and tag in the database (via the
       `--onto` option to `rebase` or the `--to` option to `revert`, among
       others) would sometimes return the incorrect change if the change has
       been reworked two or more times. Was fixed for the other engines in
     - Fixed the `--all` option used to apply a command to all known targets
       so that it loads only targets specified by the local configuration.
       Otherwise, user and system configuration can get in the way when they
       specify engines and targets not used by the current project.
     - Added support for the `--set` option when deploying to MySQL. Thanks to
       Chris Bandy for figuring out how to do it!
     - Added support for a "reworked directory". By default, reworked \ 
       scripts live in the deploy, revert, and verify directories along with
       all the other change scripts. But if that starts to get too messy, or
       you simply don't want to see them, add a `reworked_dir` setting to the
       core, engine, or target config and reworked scripts will be stored
       there, instead. Also supported are `reworked_deploy_dir`,
       `reworked_revert_dir`, and `reworked_verify_dir`.
     - Added the `--dir` option to the `init`, `engine`, and `target`
     - Copied the core configuration options (`--engine`, `--target`,
       `--plan-file`, `--registry`, etc.) to the `init`, `engine`, and
       `target` commands. This means that they can be specified after the
       command, which is a bit more natural. It also means that the
       `--registry` and `--client` options of the `target` are no longer
     - The `init` command on longer writes out commented values for the
       `deploy_dir`, `revert_dir`, or `verify_dir` settings. I think these
       settings are not commonly used, and it would start to get crowded if we
       also added their "reworked" variants, which will be used still less.
     - Added the `alter` action to the `engine` and `target` commands to set
       engine and target properties.
     - Added support for setting reworked directories to the `engine` and
       `target` commands.
     - Reformatted the output of the `engine` and `target` command `show`
       actions to include reworked directories, and to bit a bit less flat.
     - Attempting to add or alter an engine with a target URI that connects to
       a different engine now triggers an error. For example, you can't set
       the target for engine `pg` to `db:sqlite:`.
     - The `add` and `alter` actions of the `engine` and `target` commands
       now create script directories if they don't already exist.
     - The `add` action of the `engine` and `target` commands now creates a
       plan file if one does not exist in the specified location for the
       engine or target.
     - Added the `deploy_dir`, `revert_dir`, and `verify_dir` methods to
       App::Sqitch::Plan::Change. Each points to the proper directory for the
       target depending on whether or not the change has been reworked.
     - In the MySQL engine, the following URI query params will be converted
       to options passed to the command-line client, if they're present:
       * mysql_compression=1   => --compress
       * mysql_ssl=1           => --ssl
       * mysql_connect_timeout => --connect_timeout
       * mysql_init_command    => --init-command
       * mysql_socket          => --socket
       * mysql_ssl_client_key  => --ssl-key
       * mysql_ssl_client_cert => --ssl-cert
       * mysql_ssl_ca_file     => --ssl-ca
       * mysql_ssl_ca_path     => --ssl-capath
       * mysql_ssl_cipher      => --ssl-cipher
     - Added the "Overworked" section to sqitch-configuration guide with an
       example of how to move reworked change scripts into a `reworked_dir`.
     - Deprecated the `set-*` actions in the `engine` and `target` commands in
       favor of the new `alter` action.
     - The core `--deployed-dir`, `--revert-dir`, and `--verify-dir` options
       are deprecated in favor of the `--dir` option on the `init`, `engine`,
       and `target` command.

0.9992 2015-05-20T23:51:41Z
     - On PostgreSQL, Sqitch now sets the `client_encoding` parameter to
       `UTF8` for its own connection to the database. This ensures that data
       sent to and from the databse should always be properly encoded and
       decoded. Users should still set the proper encodings for change scripts
       as appropriate.
     - Fixed test failures due to path differences on Windows.
     - DateTime::TimeZone is now explicitly required in an attempt to head off
       "Cannot determine local time zone" errors.
     - Corrected some typos and thinkos in `sqitchtutorial-oracle`, thanks to
       George Hartzell.
     - Improved the script to upgrade an Oracle registry to v1.0 to support
       versions prior to Oracle 12, thanks to Timothy Procter.
     - Added missing closing parenthesis to the "Nothing to deploy" \ 
       Thanks to George Hartzell for the pull request (Issue #226).
     - Replaced the unique constraint on the `script_hash` column in the
       `changes` registry table with a unique constraint on `project` and
       `script_hash`. This is to allow a deploy script to be used in more than
       one project in a single database. This change increments the registry
       version to v1.1. Thanks to Timothy Procter for the report.
     - Updated the registry check constraints to have consistent names on the
       engines that support them. This will make it easier to modify the
       constraints in the future.
     - Fixed precision issues with the registry version on MySQL and Firebird.
     - Added comment to sqitch-passwords guide that MySQL::Config is required
       to read passwords from the MySQL configuration files. Thanks to
       Sterling Hanenkamp for the patch!

0.9991 2015-04-03T23:14:39Z
     - Reduced minimum required MySQL engine from 5.6.4 to 5.1.0. Versions
       prior to 5.6.4 lose the following features:
       * Versions earlier than 5.6.4 is fractional second precision on
         registry `DATETIME` columns. Since the ordering of those timestamps
         is so important to the functioning of Sqitch, it will sleep in 100 ms
         increments between logging changes to the registry until the time has
         ticked over to the next second. Naturally, reverts and deploys will
         be a little slower on versions of MySQL before 5.6.4, but accurate.
       * Versions earlier than 5.5.0 lose the `checkit()` functions, which
         would otherwise be used to emulate CHECK constraints in the registry,
         as well as in user-created verify scripts, as recommended in the
         MySQL tutorial, `sqitchtutorial-mysql`.
     - Added a script to update the `DATETIME` columns in a MySQL Sqitch
       registry that was upgraded to MySQL 5.6.4 or higher. It will be
       installed as `tools/upgrade-registry-to-mysql-5.6.4.sql` in the
       directory returned by `sqitch --etc`.
     - Added a script to add the `checkit()` function and registry triggers to
       emulate CHECK constraints to a MySQL Sqitch registry that was upgraded
       to MySQL 5.5.0 or higher. It will be installed as
       `tools/upgrade-registry-to-mysql-5.5.0.sql` in the directory returned
       by `sqitch --etc`.
     - The `init` command now throws an error when the plan file already
       exists and is invalid or defined for a different project. Thanks to
       Gabriel Potk獺ny for the suggestion (Issue #214).
     - All commands that take target arguments can now specify them as engine
       names or plan file paths as well as target names and URIs.
     - Added the `--all` option and the `$command.all` configuration variable
       to the `add`, `rework`, `tag`, and `bundle` commands. This option tells
       the commands to do their thing for all plans known from the
       configuration, not just the default plan.
     - Pass engine, target, or plan file names to the `add`, `rework`, `tag`,
       and `bundle` commands` commands to specify specify one or more targets,
       engines, and plans to act on.
     - Added the `--change` option to the `add`, `rework`, and `tag` commands
       to distinguish the change to be added, reworked, or tagged from
       plan-specifying arguments, if necessary.
     - Added the `--tag` option to the `tag` command to distinguish the tag to
       be added from plan-specifying arguments, if necessary.
     - Changed the short variant of the `--conflicts` option to the `add` and
       `rework` commands from `-c` to `-x`. The `-c` option is now used as the
       short variant for `--change` (and `--conflicts` has almost certainly
       never been used, anyway).
     - Added the `engine` and `project` variables to the execution of script
       templates by the `add` command. The default templates now use it to
       make their first lines one of:
       * -- Deploy [% project %]:[% change %] to [% engine]
       * -- Revert [% project %]:[% change %] from [% engine]
       * -- Verify [% project %]:[% change %] on [% engine]
     [Bug Fixes]
     - DateTime::TimeZone::Local::Win32 is now required on Windows.
     - The MySQL engine no longer passes `--skip-pager` on Windows, since
       it is not supported there. Thanks to Gabriel Potk獺ny for the report
       (Issue #213).
     - Fixed "no such table: changes" error when upgrading the SQLite
     - Fixed upgrade failure on PostgreSQL 8.4. Thanks to Phillip Smith for
       the report!
     - Fixed an error when the `status` command `show_changes` and `show_tags`
       configuration variables were set. Thanks to Adrian Klaver for the
       report (Issue #219).
     - Fixed `log` and `plan` usage statements to properly spell `--abbrev`.
       Thanks to Adrian Klaver for the report (Issue #220).
     - Fixed the formatting of change notes so that a space precedes the `#`
       character whether the note was added by the `--note` option or via an
     - Fixed a bug when parsing plan files with DOS/Windows line endings.
       Thanks to Timothy Procter for the report (Issue #212).
     - Looking up a change and tag in the database (via the `--onto` option to
       `rebase` or the `--to` option to `revert`, among others) would
       sometimes return the incorrect change if the change has been reworked
       two or more times. Thanks to BryLo for the report!
     - Updated docs to be consistent in referring to the location of the system
       configuration and template location as `$(prefix)/etc/sqitch`. Also
       added notes pointing to the `--etc-dir` to find out exactly what that
       resolves to. Suggested by Joseph Anthony Pasquale Holsten (Issue #167).
     - Reverted deprecation of the database connection options. Target URIs
       are still generally preferred, but sometimes you want to use a target
       but just change the user name or database name. Retaining the options
       is the easiest way to do this. Plus, a fair number of people have
       scripts that use these options, and it seems petty to break them. Sorry
       for the double-take here! The list of un-deprecated options is:
       * `--db-client`
       * `--db-host`
       * `--db-port`
       * `--db-username`
       * `--db-password`
       * `--db-name`

0.999  2015-02-12T19:43:45Z
     - Improved MySQL missing table error detection by relying on error codes
       instead of matching a (possibly localized) error string.
     - Made the registry upgrade more transparent when deploying. Sqitch is
       now is a little more vigilent in checking for things being out-of-date
       and updating them.
     - Fixed an issue where the `status` command would return an error when
       run against a an older version of the registry.
     - Fixed a Postgres test failure when DBD::Pg is installed but psql is not
       in the path.
     - Now require Config::GitLike 1.15 to build on Windows in order to avoid
       test failures when Cwd::abs_path dies on non-existant paths.
     - Clarified the behavior of each `deploy` reversion mode with regard to
       deploy script vs. verify script failures, and with the expectation that
       deploy scripts are atomic.
     - Target passwords can now be set via a single environment variable,
       `$SQITCH_PASSWORD`. Its value will override URI-specified password.
     - Added the sqitch-passwords and sqitch-environment guides.

0.998  2015-01-15T22:17:44Z
     - Fixed a bug in `sqitch engine update-config` where it would add data to
       config files that did not previously have them, or report that data was
       present in nonexistent config files.
     - Added the `releases` table to the databases. This table will keep track
       of releases of the Sqitch registry schema.
     - The Oracle `registry` variable is now always `DEFINE`d when Oracle
       scripts run.
     - Added the `upgrade` command, which upgrades the schema for the Sqitch
       registry for a target database.
     - Added the `script_hash` column to the `changes` registry table. This
       column contains a SHA-1 hash of the deploy script for the change at the
       time it was deployed. For existing registries, the upgrade script sets
       its value to be the same as the change ID. This value is update the
       next time a project is deployed to the database.
     - The error message when `deploy` cannot find the currently-deployed
       change ID in the plan now includes more contextual information,
       including the change name, associated tags, and the plan file name.
       Suggested by Curtis Poe (Issue #205).
     - Comments on Firebird registry objects are now created with the
       `COMMENT` command, rather than INSERTs into catalog tables.
     - Added support for "merge" events, though none are logged, yet.
   2016-06-08 21:25:20 by Thomas Klausner | Files touched by this commit (2236) | Package updated
Log message:
Bump PKGREVISION for perl-5.24.
   2015-11-03 02:56:36 by Alistair G. Crooks | Files touched by this commit (368)
Log message:
Add SHA512 digests for distfiles for databases category

Problems found with existing distfiles:
No changes made to the cstore or mariadb55-client distinfo files.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.