unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: 32712@debbugs.gnu.org
Subject: bug#32712: Error running "create extension postgis"
Date: Wed, 12 Sep 2018 09:11:44 +0200	[thread overview]
Message-ID: <D7679F77-8D35-4CFF-9801-F0B775A35484@lepiller.eu> (raw)
In-Reply-To: <8736uf9zx2.fsf@sturm.com.au>

Hi, this is a known issue. I have sent a patch for that but it wasn't reviewed yet. Ideally I could also patch the postgresql service to allow specifying extensions. I will try to do something about it.

Le 12 septembre 2018 05:07:21 GMT+02:00, Ben Sturmfels <ben@stumbles.id.au> a écrit :
>Hi Folks,
>
>When I attempt to create a database with PostGIS extensions, I get an
>error "could not open extension control file":
>
>  $ createdb -O ben testdb
>  $ psql testdb --command="create extension postgis"
>ERROR:  could not open extension control file
>"/gnu/store/6238qjlc6cl7wld3gykcfj83ajlsrmjd-postgresql-10.5/share/extension/postgis.control":
>No such file or directory
>
>My GuixSD system configuration includes the PostgreSQL service and the
>PostGIS package, something like this:
>
>  (packages (cons*
>            ...
>            postgis
>            %base-packages))
>
>  (services (cons*
>            ...
>            (postgresql-service)
>            %desktop-services))
>
>If I look in the store, I see "postgis.control" in a number of places,
>but definitely not in the "postgresql-10.5" directory:
>
>  $ find /gnu/store -name postgis.control
>/gnu/store/a9bnyqpxbhskf4vz6p84k4m42li4zqc8-postgis-2.4.4/share/extension/postgis.control
>/gnu/store/8jimyykpydhppbdbp72zr4z7l0z2fblr-profile/share/extension/postgis.control
>
>Regards,
>Ben

  reply	other threads:[~2018-09-12  7:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12  3:07 bug#32712: Error running "create extension postgis" Ben Sturmfels
2018-09-12  7:11 ` Julien Lepiller [this message]
2018-09-12  7:40   ` Gábor Boskovits
2019-04-24  1:59     ` Ben Sturmfels

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=D7679F77-8D35-4CFF-9801-F0B775A35484@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=32712@debbugs.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).