unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Gary Johnson <lambdatronic@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: PostGIS does not work with Postgresql installation
Date: Wed, 27 Feb 2019 16:00:09 -0500	[thread overview]
Message-ID: <87y361ueue.fsf@gmail.com> (raw)
In-Reply-To: <CAE4v=piZXEbb0_JMDp-y6KD8U-SgXsjVySzW+xXbiykUFbm_tw@mail.gmail.com>

Thanks for the pointer to Julien's Postgresql extensions patch.
(http://issues.guix.info/issue/32297) I have a couple of follow-up
questions:

1. Is there any timeline for when this change will be merged into
   master? It seems generally useful to the community since currently
   you can't use any custom Postgresql extensions with the database
   server, and Julien's patch looked pretty complete.

2. How do I go about cherry-picking commits from different guix branches
   into the guix branch that I am building from? How will this interact
   with future calls to guix pull? Do I need to maintain a separate
   branch that merges guix master and guix staging (or commits I
   cherry-pick therefrom)?

Thanks for your help. I really need to get PostGIS operational ASAP.

~Gary

Gábor Boskovits <boskovits@gmail.com> writes:

> Hello,
>
> Gary Johnson <lambdatronic@gmail.com> ezt írta (időpont: 2019. febr.
> 5., K, 19:22):
>>
>> Hi Guix,
>>
>>   I need to install the PostGIS spatial extensions into my local
>> PostgreSQL database. However, due to our unique packaging setup,
>> PostgreSQL cannot find the PostGIS extension directory.
>>
>
> The fix for this is currently on staging, see:
> http://issues.guix.info/issue/32297.
> If needed you can cherry-pick it from there, but this may trigger lot
> of rebuilds.
>
>> Here is the error I'm getting from within a psql session:
>>
>> -------------------------------------------------------------
>> postgres=# CREATE EXTENSION postgis;
>>
>> ERROR: could not open extension control file
>> "/gnu/store/1ybw54pgin4b59czcppybzlk6jkqnxik-postgresql-10.6/share/extension/postgis.control":
>> No such file or directory
>> -------------------------------------------------------------
>>
>> This file is actually installed here:
>>
>> /gnu/store/nx9lyaia3z8ilxm1z80f7rhg1j3ka1j8-postgis-2.4.4/share/extension/postgis.control
>>
>> So...the issue is, of course, that Guix is installing PostGIS into its
>> own directory under /gnu/store rather then into the PostgreSQL install
>> directory, which is how other package managers do it.
>>
>> Unfortunately, I can't find any environment variables that I can set to
>> tell PostgreSQL where to look from the postgis.control file. Instead, it
>> looks like the *postgis* package under gnu/packages/geo.scm needs to be
>> rewritten to correctly write out symlinks into the postgresql install
>> directory.
>>
>> I don't currently have the Guix programming chops to make this happen.
>> Perhaps someone else on this mailing list can help?
>>
>> Thanks,
>>   Gary
>>
>
> Thank you for your report.
>
> Best regards,
> g_bor

  reply	other threads:[~2019-02-27 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 17:59 PostGIS does not work with Postgresql installation Gary Johnson
2019-02-05 23:45 ` Gábor Boskovits
2019-02-27 21:00   ` Gary Johnson [this message]
2019-02-27 21:16   ` Gary Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y361ueue.fsf@gmail.com \
    --to=lambdatronic@gmail.com \
    --cc=boskovits@gmail.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).