Re: Packaging request MobilityDB

Quick update on the status of packaging MobilityDB:

* Simplified the package's autopkgtest to use the upstream's test
queries and expected output [1]
- pg_regress uses a different set of psql options and directory
structure (sql & expected vs queries & expected)
* Debian 12 (bookworm/stable) amd64
- builds successfully
- piuparts passes
- autopkgtest passes
* Debian 12 (bookworm/stable) arm64
- builds successfully
- piuparts passes
- autopkgtest fails (failing test cases below)
* 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

Once the test failure for bookworm arm64 is fixed, I think MobilityDB
could go ahead and tag the 1.1 release. This will allow for a typical
packaging pattern of pulling upstream source archives from a tag/release
page on GitHub. I don't know if the test failure on trixie needs to be a
blocker at the moment since bookworm was just released; as a data point,
the latest Ubuntu distro (lunar/23.04) is using libproj 9.1.1 (same as
bookworm). I just checked and it looks like the next Ubuntu release
(mantic/23.10) will include libproj 9.2.1.

[1]: https://salsa.debian.org/postgresql/mobilitydb/-/commit/1402c0a837f733d43fe4abdd03b815b41bf80ce0

Regards,

--Bradford

Here is the regression diff for test failure on bookworm arm64

2 tests failed ...
--- /tmp/autopkgtest.KVtGQg/autopkgtest_tmp/055_geography_funcs.out
2023-06-30 04:40:00.150375986 +0000
+++ /tmp/autopkgtest.KVtGQg/build.nb7/src/mobilitydb/test/point/expected/055_geography_funcs.test.out
2023-06-14 12:48:54.000000000 +0000
@@ -35,9 +35,9 @@
(1 row)

SELECT ST_LineLocatePoint(geography 'Linestring(1 1,2 2)', 'Point(1 1)', false);
- st_linelocatepoint
------------------------
- 2.398573818138993e-17
+ st_linelocatepoint
+--------------------
+ 0
(1 row)

SELECT ST_LineInterpolatePoint(geography 'Linestring empty', 0.1);
--- /tmp/autopkgtest.KVtGQg/autopkgtest_tmp/082_npointset_tbl.out
2023-06-30 04:41:48.855089230 +0000
+++ /tmp/autopkgtest.KVtGQg/build.nb7/src/mobilitydb/test/npoint/expected/082_npointset_tbl.test.out
2023-06-14 12:48:54.000000000 +0000
@@ -28,9 +28,9 @@
(1 row)

SELECT npointset '{"Npoint(1,0.5)", "Npoint(2,0.5)", "Npoint(3,0.5)"}'::stbox;
- stbox
--------------------------------------------------------------------------------------------------
- SRID=5676;STBOX
X((24.98171384036678,25.103669244214274),(71.25850933871267,80.96965130918636))
+ stbox
+------------------------------------------------------------------------------------------------
+ SRID=5676;STBOX
X((24.98171384036678,25.10366924421426),(71.25850933871268,80.96965130918636))
(1 row)

SELECT COUNT(*) FROM tbl_npoint WHERE np::npointset IS NOT NULL;

Here is the regression diff for the test failure on trixie amd64

1 tests failed ...
--- /tmp/autopkgtest.eBycLQ/autopkgtest_tmp/056_tpoint_spatialfuncs.out
2023-06-30 04:55:01.810972446 +0000
+++ /tmp/autopkgtest.eBycLQ/build.OTW/src/mobilitydb/test/point/expected/056_tpoint_spatialfuncs.test.out
2023-06-18 14:44:23.000000000 +0000
@@ -113,9 +113,17 @@
(1 row)

SELECT ROUND(MIN(xmin(transform(transform(setSRID(b,3812), 5676),
3812)))::numeric, 1) FROM tbl_stbox;
-ERROR: transform: File not found or invalid (1029)
+ round
+-------
+ 0.5
+(1 row)
+
SELECT MIN(xmin(round(transform(transform(setSRID(b, 3812), 5676),
3812), 1))) FROM tbl_stbox;
-ERROR: transform: File not found or invalid (1029)
+ min
+-----
+ 0.5
+(1 row)
+
SELECT SRID(tgeompoint 'Point(1 1)@2000-01-01');
srid
------