Log message:
*: reset MAINTAINER for fhajny on his request

Log message:
all: migrate homepages from http to https

pkglint -r --network --only "migrate"

As a side-effect of migrating the homepages, pkglint also fixed a few
indentations in unrelated lines. These and the new homepages have been
checked manually.

Log message:
py-barman: updated to 2.5

Version 2.5:

- Add support for PostgreSQL 11

- Add check-backup command to verify that WAL files required for
   consistency of a base backup are present in the archive. Barman now
   adds a new state (WAITING_FOR_WALS) after completing a base backup,
   and sets it to DONE once it has verified that all WAL files from
   start to the end of the backup exist. This command is included in
   the regular cron maintenance job. Barman now notifies users
   attempting to recover a backup that is in WAITING_FOR_WALS state.

- Allow switch-xlog --archive to work on a standby (just for the
   archive part)

- Bug fixes:
  - Fix decoding errors reading external commands output
  - Fix documentation regarding WAL streaming and backup from
        standby

Log message:
*: update email for fhajny

Log message:
py-barman: updated to 2.4

Version 2.4:
-   Add standard and retry hook scripts for backup deletion (pre/post)
-   Add standard and retry hook scripts for recovery (pre/post)
-   Add standard and retry hook scripts for WAL deletion (pre/post)
-   Add --standby-mode option to barman recover to add standby_mode = on
    in pre-generated recovery.conf
-   Add --target-action option to barman recover, allowing users to add
    shutdown, pause or promote to the pre-generated recovery.conf file
-   Improve usability of point-in-time recovery with consistency checks
    (e.g. recovery time is after end time of backup)
-   Minor documentation improvements
-   Drop support for Python 3.3

Relevant bug fixes:
-   Fix remote get_file_content method, preventing
    incremental recovery from happening
-   Unicode issues with command
-   Add --wal-method=none when pg_basebackup >= 10

Minor bug fixes:
-   Stop process manager module from ovewriting lock files content
-   Relax the rules for rsync output parsing
-   Ignore vanished files in streaming directory
-   Case insensitive slot names
-   Make DataTransferFailure.from_command_error() more resilient
-   Rename command() to barman_command()
-   Initialise synchronous standby names list if not set
-   Correct placeholders ordering
-   Force datestyle to iso for replication connections
-   Returns error if delete command does not remove the backup
-   Fix exception when calling is_power_of_two(None)
-   Downgraded sync standby names messages to debug

Version 2.3:
-   Add support to PostgreSQL 10
-   Follow naming changes in PostgreSQL 10:
    -   The switch-xlog command has been renamed to switch-wal.
    -   In commands output, the xlog word has been changed to WAL and
        location has been changed to LSN when appropriate.
-   Add the --network-compression/--no-network-compression options to
    barman recover to enable or disable network compression at run-time
-   Add --target-immediate option to recover command, in order to exit
    recovery when a consistent state is reached (end of the backup,
    available from PostgreSQL 9.4)
-   Show cluster state (master or standby) with barman status command
-   Documentation improvements
-   Bug fixes:
    -   Fix high memory usage with parallel_jobs > 1
    -   Better handling of errors using parallel copy
    -   Make barman diagnose more robust with system exceptions
    -   Let archive-wal ignore files with .tmp extension

Version 2.2:
-   Implement parallel copy for backup/recovery through the
    parallel_jobs global/server option to be overridden by the --jobs or
    -j runtime option for the backup and recover command. Parallel
    backup is available only for the rsync copy method. By default, it
    is set to 1 (for behaviour compatibility with previous versions).
-   Support custom WAL size for PostgreSQL 8.4 and newer. At backup
    time, Barman retrieves from PostgreSQL wal_segment_size and
    wal_block_size values and computes the necessary calculations.
-   Improve check command to ensure that incoming directory is empty
    when archiver=off, and streaming directory is empty when
    streaming_archiver=off
-   Add external_configuration to backup_options so that users can
    instruct Barman to ignore backup of configuration files when they
    are not inside PGDATA (default for Debian/Ubuntu installations). In
    this case, Barman does not display a warning anymore.
-   Add --get-wal and --no-get-wal options to barman recover
-   Add max_incoming_wals_queue global/server option for the check
    command so that a non blocking error is returned in case incoming
    WAL directories for both archiver and the streaming_archiver contain
    more files than the specified value.
-   Documentation improvements
-   File format changes:
    -   The format of backup.info file has changed. For this reason a
        backup taken with Barman 2.2 cannot be read by a previous
        version of Barman. But, backups taken by previous versions can
        be read by Barman 2.2.
-   Minor bug fixes:
    -   Allow replication-status to work against a standby
    -   Close any PostgreSQL connection before starting pg_basebackup
    -   Safely handle paths containing special characters
    -   Archive .partial files after promotion of streaming source
    -   Recursively create directories during recovery
    -   Improve xlog.db locking
    -   Remove tablespace_map file during recover
    -   Reconnect to PostgreSQL if connection drops

Version 2.1:
-   Add --archive and --archive-timeout options to switch-xlog command
-   Preliminary support for PostgreSQL 10
-   Minor additions:
    -   Add last archived WAL info to diagnose output
    -   Add start time and execution time to the output of delete
        command
-   Minor bug fixes:
    -   Return failure for get-wal command on inactive server
    -   Make streaming_archiver_names and streaming_backup_name options
        global
    -   Fix rsync failures due to files truncated during transfer
    -   Correctly handle compressed history files
    -   Avoid de-referencing symlinks in pg_tblspc when preparing
        recovery
    -   Fix comparison of last archiving failure
    -   Avoid failing recovery if postgresql.conf is not writable
    -   Fix output of replication-status command
    -   Exclude files from backups like pg_basebackup
    -   Exclude directories from other Postgres versions while copying
        tablespaces
    -   Make retry hook script options global

Version 2.0 - 27 Sep 2016

-   Support for pg_basebackup and base backups over the PostgreSQL
    streaming replication protocol with backup_method=postgres
    (PostgreSQL 9.1 or higher required)

-   Support for physical replication slots through the slot_name
    configuration option as well as the --create-slot and --drop-slot
    options for the receive-wal command (PostgreSQL 9.4 or higher
    required). When slot_name is specified and streaming_archiver is
    enabled, receive-wal transparently integrates with pg_receivexlog,
    and check makes sure that slots exist and are actively used

-   Support for the new backup API introduced in PostgreSQL 9.6, which
    transparently enables concurrent backups and backups from standby
    servers using the standard rsync method of backup. Concurrent backup
    was only possible for PostgreSQL 9.2 to 9.5 versions through the
    pgespresso extension. The new backup API will make pgespresso
    redundant in the future

-   If properly configured, Barman can function as a synchronous standby
    in terms of WAL streaming. By properly setting the
    streaming_archiver_name in the synchronous_standby_names priority
    list on the master, and enabling replication slot support, the
    receive-wal command can now be part of a PostgreSQL synchronous
    replication cluster, bringing RPO=0 (PostgreSQL 9.5.5 or
    higher required)

-   Introduce barman-wal-restore, a standard and robust script written
    in Python that can be used as restore_command in recovery.conf files
    of any standby server of a cluster. It supports remote parallel
    fetching of WAL files by efficiently invoking get-wal through SSH.
    Currently available as a separate project called barman-cli. The
    barman-cli package is required for remote recovery when get-wal is
    listed in recovery_options

-   Control the maximum execution time of the check command through the
    check_timeout global/server configuration option (30 seconds
    by default)

-   Limit the number of WAL segments that are processed by an
    archive-wal run, through the archiver_batch_size and
    streaming_archiver_batch_size global/server options which control
    archiving of WAL segments coming from, respectively, the standard
    archiver and receive-wal

-   Removed locking of the XLOG database during check operations

-   The show-backup command is now aware of timelines and properly
    displays which timelines can be used as recovery targets for a given
    base backup. Internally, Barman is now capable of parsing .history
    files

-   Improved the logic behind the retry mechanism when copy operations
    experience problems. This involves backup (rsync and postgres) as
    well as remote recovery (rsync)

-   Code refactoring involving remote command and physical copy
    interfaces

-   Bug fixes:
    -   Correctly handle .history files from streaming
    -   Fix replication-status on PostgreSQL 9.1
    -   Fix replication-status when sent and write locations are not
        available
    -   Fix misleading message on pg_receivexlog termination

Log message:
Switch py-dateutils to plain DEPENDS.

It supports both python 2 and 3 nowadays.

Log message:
Update databases/py-barman to 1.6.1.

- Add --peek option to get-wal command to discover existing WAL
  files from the Barman's archive
- Add replication-status command for monitoring the status of any
  streaming replication clients connected to the PostgreSQL
  server. The --target option allows users to limit the request to
  only hot standby servers or WAL streaming clients
- Add the switch-xlog command to request a switch of a WAL file to
  the PostgreSQL server. Through the '--force' it issues a
  CHECKPOINT beforehand
- Add streaming_archiver_name option, which sets a proper
  application_name to pg_receivexlog when streaming_archiver is
  enabled (only for PostgreSQL 9.3 and above)
- Check for _superuser_ privileges with PostgreSQL's standard
  connections (#30)
- Check the WAL archive is never empty
- Check for 'backup_label' on the master when server is down
- Improve barman-wal-restore contrib script
- Treat the "failed backups" check as non-fatal
- Rename '-x' option for get-wal as '-z'
- Add archive_mode=always support for PostgreSQL 9.5 (#32)
- Properly close PostgreSQL connections when necessary
- Fix receive-wal for pg_receive_xlog version 9.2

Log message:
Update databases/py-barman to 1.6.0.

Version 1.6.0 - 29 Feb 2016

-   Support for streaming replication connection through the
    streaming_conninfo server option
-   Support for the streaming_archiver option that allows Barman to
    receive WAL files through PostgreSQL's native streaming protocol.
    When set to 'on', it relies on pg_receivexlog to receive WAL data,
    reducing Recovery Point Objective. Currently, WAL streaming is an
    additional feature (standard log archiving is still required)
-   Implement the receive-wal command that, when streaming_archiver is
    on, wraps pg_receivexlog for WAL streaming. Add --stop option to
    stop receiving WAL files via streaming protocol. Add --reset option
    to reset the streaming status and restart from the current xlog
    in Postgres.
-   Automatic management (startup and stop) of receive-wal command via
    cron command
-   Support for the path_prefix configuration option
-   Introduction of the archiver option (currently fixed to on) which
    enables continuous WAL archiving for a specific server, through log
    shipping via PostgreSQL's archive_command
-   Support for streaming_wals_directory and errors_directory options
-   Management of WAL duplicates in archive-wal command and integration
    with check command
-   Verify if pg_receivexlog is running in check command when
    streaming_archiver is enabled
-   Verify if failed backups are present in check command
-   Accept compressed WAL files in incoming directory
-   Add support for the pigz compressor (thanks to Stefano Zacchiroli
    zack@upsilon.cc)
-   Implement pygzip and pybzip2 compressors (based on an initial idea
    of Christoph Moench-Tegeder christoph@2ndquadrant.de)
-   Creation of an implicit restore point at the end of a backup
-   Current size of the PostgreSQL data files in barman status
-   Permit archive_mode=always for PostgreSQL 9.5 servers (thanks to
    Christoph Moench-Tegeder christoph@2ndquadrant.de)
-   Complete refactoring of the code responsible for connecting to
    PostgreSQL
-   Improve messaging of cron command regarding sub-processes
-   Native support for Python >= 3.3
-   Changes of behaviour:
    -   Stop trashing WAL files during archive-wal (commit:e3a1d16)
-   Bug fixes:
    -   Atomic WAL file archiving (#9 and #12)
    -   Propagate "-c" option to any Barman subprocess (#19)
    -   Fix management of backup ID during backup deletion (#22)
    -   Improve archive-wal robustness and log messages (#24)
    -   Improve error handling in case of missing parameters

Version 1.5.1 - 16 Nov 2015

-   Add support for the 'archive-wal' command which performs WAL
    maintenance operations on a given server
-   Add support for "per-server" concurrency of the 'cron' command
-   Improved management of xlog.db errors
-   Add support for mixed compression types in WAL files (SF.net#61)
-   Bug fixes:
    -   Avoid retention policy checks during the recovery
    -   Avoid 'wal_level' check on PostgreSQL version < 9.0 (#3)
    -   Fix backup size calculation (#5)

Log message:
Remove duplicate SHA512 digests that crept in.

Log message:
Add SHA512 digests for distfiles for databases category

Problems found with existing distfiles:
	distfiles/D6.data.ros.gz
	distfiles/cstore0.2.tar.gz
	distfiles/data4.tar.gz
	distfiles/sphinx-2.2.7-release.tar.gz
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.