| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
ChangeLog: https://sourceforge.net/projects/pgbarman/files/2.11/
|
| |
|
|
|
|
|
| |
Regenerate patches with 'make makepatch' after changes to
files/patch-setup.py
ChangeLog: https://sourceforge.net/projects/pgbarman/files/2.10/
|
| |
|
|
|
|
| |
Regenerate patches
ChangeLog: https://sourceforge.net/projects/pgbarman/files/2.8/
|
| |
|
|
|
|
| |
- Account for different username between postgresql 9.5 (postgres)
or earlier versions (pgsql)
- Regenerate patches by 'make makepatch'
|
|
|
- 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'
|