Yes, that's the pain of having libraries in non public directory. Either
solution is fine, I would like to avoid editing the /etc/ld.so.conf
What about adding --with-postgres-libraries to the psycopg2 configure line?
Best regards,
Adis
___
On Mon, 2013-09-30 at 15:29:28 +0200, Adis Nezirovic wrote:
Yes, that's the pain of having libraries in non public directory. Either
solution is fine, I would like to avoid editing the /etc/ld.so.conf
What about adding --with-postgres-libraries to the psycopg2 configure line?
In my last
On Sun, Sep 29, 2013 at 04:13:02PM +0300, Audrius Kažukauskas wrote:
On Thu, 2013-09-19 at 12:58:54 +0200, Adis Nezirovic wrote:
Great, I've restored the line for explicit permissions of DATADIR and added
a few tips for upgrade in README.SBo
See attached archive.
I have successfully
On Sun, 29 Sep 2013, Audrius Kažukauskas wrote:
I have successfully upgraded from 9.2.4 to 9.3.0 and then encountered the
problem: while psycopg2 (Python DB adapter for Postgres) builds fine,
trying to use it results in the following error:
ImportError: libpq.so.5: cannot open shared
Great, I've restored the line for explicit permissions of DATADIR and added
a few tips for upgrade in README.SBo
See attached archive.
Best regards,
Adis
postgresql.tgz
Description: GNU Zip compressed data
___
SlackBuilds-users mailing list
On Wed, Sep 18, 2013 at 12:24 AM, Thomas Morper tho...@beingboiled.infowrote:
Minor problem: doinst.sh generates broken symlinks to usr/lib... instead
of /usr/lib... - was easily fixed.
3.4) Make sure new rc.postgresql script is active
Minor problem: Could not find 'postgres' binary.
On Wed, 18 Sep 2013, Adis Nezirovic wrote:
The problem with symlinks is we must not use absolute paths (installpkg
can be called with --root parameter). Anyway, I've simplified logic for
symlinks in doinst.sh, should be more robust now.
I've also removed PRGNAM from all scripts except
On Wed, 11 Sep 2013, Adis Nezirovic wrote:
3) You have PostgreSQL installed (let's say 9.x series, or at least 8.3)
You want to do in-place testing (two running PostgreSQL instances) and
upgrade using pg_upgrade
I've got a small 15 GB Postgres 9.2 DB on a modest Atom server. The
Hello guys,
I have test slackbuild (see attachment). The scenario for using package
produced by this
slackbuild would be the following:
1) You don't have PostgreSQL installed. Install package, business as usual
2) You have PostgreSQL installed, don't care for in-place upgrades:
Create
On Sep 3, 2013 10:03 PM, Benjamin Trigona-Harany bo...@alumni.sfu.ca
wrote:
On September 3, 2013 17:04:15 Adis Nezirovic wrote:
Guys, I have a question for all PostgreSQL users and SBo admins.
Would it be OK for the next PostgreSQL package (upcoming 9.3) to be
version
specific and
10 matches
Mail list logo