Bug 201962
| Summary: | databases/postgresql-repmgr: update to 2.0.3 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Jimmy Olgeni <olgeni> | ||||||||
| Component: | Individual Port(s) | Assignee: | Muhammad Moinur Rahman <bofh> | ||||||||
| Status: | Closed FIXED | ||||||||||
| Severity: | Affects Only Me | CC: | ard_1 | ||||||||
| Priority: | --- | Flags: | bofh:
maintainer-feedback+
|
||||||||
| Version: | Latest | ||||||||||
| Hardware: | Any | ||||||||||
| OS: | Any | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 159357 [details]
poudriere test run
I have checked it. The problem is we have to limit postgresql version number. If you go through the postgresql version requirement you can check it out. We need to modify the Uses/pgsql. Am working on it. (In reply to Muhammad Moinur Rahman from comment #2) Can 2.0.3 be committed? Created attachment 169262 [details]
Patch to limit PostgreSQL version
Since repmgr 2.x has limited support for PostgreSQL versions up to 9.4.x in upstream, we should also have this limitation in port.
A commit references this bug: Author: bofh Date: Thu Jun 9 19:50:41 UTC 2016 New revision: 416623 URL: https://svnweb.freebsd.org/changeset/ports/416623 Log: [NEW] databases/postgresql-repmgr2: 2.X version of postgresql-repmgr - postgresql-repmgr will be updated to 3.X branch PR: 201962 Submitted by: olgeni Changes: head/UPDATING head/databases/Makefile head/databases/postgresql-repmgr2/ head/databases/postgresql-repmgr2/Makefile head/databases/postgresql-repmgr2/distinfo Committed. As 2.X has limited capacity with 9.4 I have limited it with 9.3. |
Created attachment 159356 [details] Upgrade patch Update to version 2.0.3. Is 3.x planned?