Bug 72967
| Summary: | update databases/slony1 to latest | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Vick Khera <vivek> | ||||
| Component: | Individual Port(s) | Assignee: | Volker Stolz <vs> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Here is a revised patch that updates slony1 to 1.0.5, which came out a few hours after 1.0.4 was found to contain an error. --- slony1.old/Makefile Thu Oct 14 09:56:22 2004 +++ slony1/Makefile Thu Nov 4 14:28:11 2004 @@ -6,11 +6,11 @@ # PORTNAME= slony1 -PORTVERSION= 1.0.2 +PORTVERSION= 1.0.5 CATEGORIES= databases MASTER_SITES= http://developer.postgresql.org/~wieck/slony1/download/ -MAINTAINER= ports@FreeBSD.org +MAINTAINER= vivek@khera.org COMMENT= PostgreSQL master to multiple slaves replication system PGSQL_PORT= ${PORTSDIR}/databases/postgresql7 diff -Pru slony1.old/distinfo slony1/distinfo --- slony1.old/distinfo Thu Aug 26 15:46:16 2004 +++ slony1/distinfo Thu Nov 4 14:28:31 2004 @@ -1,2 +1,2 @@ -MD5 (slony1-1.0.2.tar.gz) = 0ca6a4af061793a6d0a998a514ea50f7 -SIZE (slony1-1.0.2.tar.gz) = 322353 +MD5 (slony1-1.0.5.tar.gz) = 66fcc0f53028101e4e0f969e5f47fe43 +SIZE (slony1-1.0.5.tar.gz) = 374903 State Changed From-To: open->feedback Are you sure the note in UPDATING is necessary? Database-admins tend to think before typing anyway...I don't want to spam UPDATING with too many instructions which boil down to "Take care" and are not relevant to 99.9% of users. Responsible Changed From-To: freebsd-ports-bugs->vs I'll handle this. State Changed From-To: feedback->closed Committed, thanks! |
I am willing to take ownership of this port, as reflected in the patch below. Update databases/slony1 replication software for Postgres to latest version, 1.0.4. notes for ports/UPDATING file: The proper upgrade procedure is: 1. Stop the slon replication engine on all nodes. 2. Install the new Slony version on all nodes. 3. Execute a slonik script containing the command update functions (id = <nodeId>); for every node in the cluster. 4. Start all slon replication engines.