summaryrefslogtreecommitdiff
path: root/databases/pgbarman/files/patch-setup.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* databases/pgbarman: Update to 2.17Matthew Seaman2021-12-171-22/+15
| | | | | | | | | | | | | | | | | | | | | Following upstream changes, switch master site to GitHub, including for hte pre-build PDF manual. Drop support for python-3.6 -- the software claims to support this version, but setup.py fails with an obscure error, and considering that python-3.6 is going out of support at the end of this month, I could not justify the time to develop a compatibility fix. Drop the USE_PYTHON 'optsuffix' flag in favour of an explicit PKGNAMESUFFIX As reported in PR 260340, appending the python version to the barman ${ETCDIR} doesn't make sense. Fix this by dropping the USE_PYTHON 'concurrent' flag, which doesn't really make sense for end-user software rather than library modules. (1) PR: 260340 (1) Reported by: bsd at abinet.ru
* Update to 2.11Matthew Seaman2020-07-181-2/+8
| | | | ChangeLog: https://sourceforge.net/projects/pgbarman/files/2.11/
* Update to 2.10Matthew Seaman2019-12-071-2/+6
| | | | | | | Regenerate patches with 'make makepatch' after changes to files/patch-setup.py ChangeLog: https://sourceforge.net/projects/pgbarman/files/2.10/
* Update to 2.8Matthew Seaman2019-05-161-8/+12
| | | | | | Regenerate patches ChangeLog: https://sourceforge.net/projects/pgbarman/files/2.8/
* Update to 2.0Matthew Seaman2016-09-301-2/+2
| | | | | | - Account for different username between postgresql 9.5 (postgres) or earlier versions (pgsql) - Regenerate patches by 'make makepatch'
* - Install man pages to a location where man(1) can find themMatthew Seaman2014-12-031-0/+13
- While here update man pages and speciment barman.conf file to use FreeBSD-ish locations for various things, particularly that our idea of the PostgreSQL default user is 'pgsql' although the database to connect to is 'postgres'