Summary: | MAKE RPM doesn't work (slony 2.0.0) | ||
---|---|---|---|
Product: | Slony-I | Reporter: | Andrew O'Connell <andrewoconnell> |
Component: | rpm | Assignee: | Slony Bugs List <slony1-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | andrewoconnell, devrim |
Priority: | high | ||
Version: | devel | ||
Hardware: | PC | ||
OS: | Windows |
Description
Andrew O'Connell
2008-12-16 07:53:34 UTC
I'm aware of the problem, and comitted a patch to rpm repository to fix the first error. I'll let you know when I fix the issue completely. Let me know if I can help at all... I couldn't see how I changed that. I built RPMs on Fedora 10: http://yum.pgsqlrpms.org/8.3/fedora/fedora-10-i386/repoview/letter_s.group.html Here is the SRPM link: http://yum.pgsqlrpms.org/srpms/8.3/fedora/fedora-10-i386/repoview/slony1.html Please let me know if the SRPM works for you. Hi, Thanks for getting a fix on this so quick. We're running Centos/Redhat 4 & 5 so I needed to re-build the rpms for that. I worked out how to apply the patch to get rid of the below error /usr/bin/sh is needed by slony1-2.0.0-1_PG8.3.0.i386 But can't quite figure out what to do to get rid of the perl error perl(@@PGLIBDIR@@::slon-tools) is needed by slony1-2.0.0-1_PG8.3.0.i386 Can you shed any light? Would it be usefull for be to email anyone the built rpms (against Pg8.3) ? Thanks! Andrew OK, I think I have a list of fixes now, thanks for the pointers Slony.spec.in & Slony.spec Change the line below to read : Source0: @PACKAGE_NAME@-%{version}.tar.bz2 Add to tools/altperl/Makefile : -e "s#@@PGLIBDIR@@#$(perlsharedir)#;" \ (found this on http://archive.netbsd.se/?ml=slony1-bugs&a=2007-07&t=4562793) Change /tools/slony-cluster-analysis-mass.sh & slony1-2.0.0/tools/slony-cluster-analysis.sh from #!/usr/bin/sh to #!/bin/sh then use ./configure --with-perltools and make rpm the result seams to not throwup any errors when doing rpm -ihv --test /usr/src/redhat/RPMS/i386/slony1-2.0.0-1_PG8.3.0.i386.rpm If anyone wants the rpms then shout I'm closing this bug, since the changes will hopefully appear in 2.0.1. |