From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Bradford Boyle <bradford(dot)d(dot)boyle(at)gmail(dot)com> |
Cc: | pgsql-pkg-debian(at)lists(dot)postgresql(dot)org |
Subject: | Re: Updated packaging for MobilityDB 1.1.0~beta1 |
Date: | 2023-11-06 16:25:42 |
Message-ID: | ZUkThiWJt6rE5Uiv@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-debian |
Re: To Bradford Boyle
> In postgresql-XX-mobility, we need the XX version of
> postgresql-XX-postgis-3, not just any version, so this change isn't
> correct.
>
> The usage of "postgresql-postgis" in the Build-Depends is also fishy,
> but the "update debian/control from control.in" machinery doesn't
> support using PGVERSION in the Source section yet. I tried
> implementing that the other week, but didn't get to finish it yet,
> hopefully that will happen over the next days.
Hi Bradford,
I've done that now, it will be available in postgresql-common 256.
I pushed a change that uses it and also loops over the versions that
should be targeted for cmake.
Ideally, testing the extension could also use this from
debian/tests/installcheck:
pg_buildext run_installed /usr/bin/cmake -Btest-%v
pg_buildext run_installed make -C test-% test
... but that starts by recompiling the package instead of just running
the tests.
Perhaps you have an idea how to make it work? The existing
debian/tests/regress.sh file looks very complex and might break with
every little upstream change. (Of course if there's no easier way to
get the upstream testsuite to run, we have to go the complex route.)
Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Bradford Boyle | 2023-11-08 07:19:06 | Re: Updated packaging for MobilityDB 1.1.0~beta1 |
Previous Message | Devrim Gündüz | 2023-11-05 22:42:21 | Re: Include h3-pg extension |