Re: Packaging request MobilityDB

Hi,

I've finally found the time to look at MobilityDB.

Re: Bradford Boyle
> * Debian 13 (trixie/testing)
> - builds successfully
> - piuparts passes
> - autopkgtests fail for trixie (testing)
> * test failure looks to be an issue with the newer libproj (9.2.1)
> included in trixie

When I run the tests on unstable I get this:

$ debian/tests/installcheck
Creating new PostgreSQL cluster 15/regress ...
test 001_set                      ... *** /tmp/pg_virtualenv.ye3HhD/log/postgresql-15-regress.log (last 100 lines) ***
2023-07-31 14:44:57.593 UTC [321171] LOG:  starting PostgreSQL 15.3 (Debian 15.3-0+deb12u1) on x86_64-pc-linux-gnu,
compiledby gcc (Debian 12.2.0-14) 12.2.0, 64-bit
 
2023-07-31 14:44:57.593 UTC [321171] LOG:  listening on IPv4 address "127.0.0.1", port 5433
2023-07-31 14:44:57.594 UTC [321171] LOG:  could not bind IPv4 address "127.0.0.1": Address already in use
2023-07-31 14:44:57.594 UTC [321171] HINT:  Is another postmaster already running on port 5433? If not, wait a few
secondsand retry.
 
2023-07-31 14:44:57.594 UTC [321171] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5433"
2023-07-31 14:44:57.595 UTC [321174] LOG:  database system was shut down at 2023-07-31 14:44:57 UTC
2023-07-31 14:44:57.597 UTC [321171] LOG:  database system is ready to accept connections
2023-07-31 14:45:00.903 UTC [321209] myon@postgres ERROR:  Could not parse the set: Missing open brace at character 29
2023-07-31 14:45:00.903 UTC [321209] myon@postgres STATEMENT:  /* Errors */
    SELECT tstzset '2000-01-01, 2000-01-02';
Dropping cluster 15/regress ...

(After setting : ${AUTOPKGTEST_TMP:=/tmp} )

debian/copyright: LICENSE mentions the ULB - haven't checked the rest
of the source yet

debian/tests/installcheck: Why is that .so trickery necessary? If
mobilitydb needs postgis that way, it should link against it.

debian/control.in: This would be the first package to use PGVERSION in
the Build-Depends list. I'm slightly surprised it works, but
apparently I coded the logic in pg_buildext correctly. ;)

Is the postgis version used at build time relevant? There is a
postgresql-postgis package that could be used instead. (If the version
is relevant, we need a solution that works when more than one version
is targeted.)

Christoph