public inbox for [email protected]
help / color / mirror / Atom feedUpdated packaging for MobilityDB 1.1.0~beta1
18+ messages / 4 participants
[nested] [flat]
* Updated packaging for MobilityDB 1.1.0~beta1
@ 2023-11-04 23:19 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
0 siblings, 1 reply; 18+ messages in thread
From: Bradford Boyle @ 2023-11-04 23:19 UTC (permalink / raw)
To: [email protected]
Hello,
I have just pushed an update to the Debian packaging of MobilityDB to
salsa.debian.org [1] that addresses the feedback [2] from the first
attempt at packaging this extension. The build passes the GitLab CI
pipeline and I have verified that the package builds and autopkgtests
pass on arm64 (via sbuild). Below is a summary of how I have addressed
the comments/questions raised in the previous review. As time permits, I
would appreciate another review.
* I have updated debian/copyright to more accurately reflect the
copyrights found in the source. I bootstrapped this file using cme[3]
and then manually addressed all of the TODOs. I've also ensured that
lintian doesn't raise any errors or warnings related to d/copyright.
* I've updated d/tests/installcheck to avoid the use of
shared_preload_libraries when creating the test cluster
* Tests instead set session_preload_libraries via PGOPTIONS to load
the postgis extension. I don't think it is possible to link
against postgis since it is not a shared library (no SONAME).
* I've updated d/control.in so that PGVERSION is no longer used --
declaring a dependency on postgresql-postgis is sufficient
Thanks,
-- Bradford
[1]: https://salsa.debian.org/postgresql/mobilitydb/-/commit/9dfff5eee4eab17b8d20ecd408ed10b830750244
[2]: https://www.postgresql.org/message-id/ZMfMWcLtZIVxbDYj%40msg.df7cb.de
[3]: https://wiki.debian.org/CopyrightReviewTools#cme
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0~beta1
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
@ 2023-11-05 14:04 ` Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
0 siblings, 1 reply; 18+ messages in thread
From: Christoph Berg @ 2023-11-05 14:04 UTC (permalink / raw)
To: Bradford Boyle <[email protected]>; +Cc: [email protected]
Re: Bradford Boyle
> Hello,
>
> I have just pushed an update to the Debian packaging of MobilityDB to
> salsa.debian.org [1] that addresses the feedback [2] from the first
> attempt at packaging this extension.
Thanks!
> * I've updated d/control.in so that PGVERSION is no longer used --
> declaring a dependency on postgresql-postgis is sufficient
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.
I haven't investigated the cause yet, but the pgdg build is failing:
https://pgdgbuild.dus.dg-i.net/job/mobilitydb-binaries/2/architecture=amd64,distribution=sid/console
14:56:48 dh_missing: warning: usr/lib/postgresql/16/lib/libMobilityDB-1.1.so exists in debian/tmp but is not installed to anywhere
14:56:48 dh_missing: warning: usr/share/postgresql/16/extension/mobilitydb--1.1.0.sql exists in debian/tmp but is not installed to anywhere
14:56:48 dh_missing: warning: usr/share/postgresql/16/extension/mobilitydb.control exists in debian/tmp but is not installed to anywhere
14:56:48 dh_missing: error: missing files, aborting
Christoph
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0~beta1
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
@ 2023-11-06 16:25 ` Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
0 siblings, 1 reply; 18+ messages in thread
From: Christoph Berg @ 2023-11-06 16:25 UTC (permalink / raw)
To: Bradford Boyle <[email protected]>; +Cc: [email protected]
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
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0~beta1
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
@ 2023-11-08 07:19 ` Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
0 siblings, 1 reply; 18+ messages in thread
From: Bradford Boyle @ 2023-11-08 07:19 UTC (permalink / raw)
To: Christoph Berg <[email protected]>; +Cc: [email protected]
Hi Christoph,
> I've done that now, it will be available in postgresql-common 256.
Thank you!
> 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.)
I agree with your assessment of d/tests/regress.sh. The reason I went
that route initially was because running cmake followed by make test was
rebuilding the package. I did see that autopkgtest has the
'build-needed' restriction [1] but its use seems to be discouraged. I
took another look at the upstream testsuite to see if we can (easily)
run its testsuite without require a rebuild and I think I have found a
way.
In short, upstream was defining a test called 'build' that would rebuild
the extension. We can instruct ctest to exclude this test by specifying
a regex. I was able to drop regress.sh altogether and have
d/tests/installcheck run
cmake -Btest-%v
make -C test-%v ARGS='-E build' test
This does require repeating the list of -dev packages in d/tests/control
so that cmake can generate the Makefiles. If this sounds like a good
approach to you, I can push the commit to s.d.o.
--Bradford
[1]: https://people.debian.org/~eriberto/README.package-tests.html
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0~beta1
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
@ 2023-11-08 08:13 ` Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
0 siblings, 1 reply; 18+ messages in thread
From: Christoph Berg @ 2023-11-08 08:13 UTC (permalink / raw)
To: Bradford Boyle <[email protected]>; +Cc: [email protected]
Re: Bradford Boyle
> In short, upstream was defining a test called 'build' that would rebuild
> the extension. We can instruct ctest to exclude this test by specifying
> a regex. I was able to drop regress.sh altogether and have
> d/tests/installcheck run
>
> cmake -Btest-%v
> make -C test-%v ARGS='-E build' test
>
> This does require repeating the list of -dev packages in d/tests/control
> so that cmake can generate the Makefiles. If this sounds like a good
> approach to you, I can push the commit to s.d.o.
Sure, that sounds sane.
Christoph
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
@ 2024-04-04 12:12 ` Christoph Berg <[email protected]>
2024-04-04 12:24 ` Re: Updated packaging for MobilityDB 1.1.0 Esteban Zimanyi <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
0 siblings, 2 replies; 18+ messages in thread
From: Christoph Berg @ 2024-04-04 12:12 UTC (permalink / raw)
To: Bradford Boyle <[email protected]>; +Cc: [email protected]
Hi Bradford,
where are we with MobilityDB? Are the remaining test failures a
problem in the source, or just artifacts of the way we try to run the
tests?
Christoph
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
@ 2024-04-04 12:24 ` Esteban Zimanyi <[email protected]>
1 sibling, 0 replies; 18+ messages in thread
From: Esteban Zimanyi @ 2024-04-04 12:24 UTC (permalink / raw)
To: Christoph Berg <[email protected]>; +Cc: Bradford Boyle <[email protected]>; [email protected]; SCHOEMANS Maxime <[email protected]>; Víctor Diví <[email protected]>; Regina Obe <[email protected]>
Dear all (cc MobilityDB Team and Regina Obe)
The MobilityDB 1.1 version was released two weeks ago.
See: https://github.com/MobilityDB/MobilityDB/releases/tag/v1.1.0
However, as this release was not running on ARM, we were waiting to produce
a v1.1.1 release with small bug fixes that allows MobilityDB to run on the
ARM architecture. This is now almost complete and we are thus planning to
release and announce MobilityDB 1.1.1 either at the end of this week or
next week.
Regards
Esteban
------------------------------------------------------------
Prof. Esteban Zimanyi
Department of Computer & Decision Engineering (CoDE) CP 165/15
Universite Libre de Bruxelles
Avenue F. D. Roosevelt 50
B-1050 Brussels, Belgium
fax: + 32.2.650.47.13
tel: + 32.2.650.31.85
e-mail: [email protected]
Internet: http://cs.ulb.ac.be/members/esteban/
------------------------------------------------------------
On Thu, Apr 4, 2024 at 2:12 PM Christoph Berg <[email protected]> wrote:
> Hi Bradford,
>
> where are we with MobilityDB? Are the remaining test failures a
> problem in the source, or just artifacts of the way we try to run the
> tests?
>
> Christoph
>
>
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
@ 2024-04-05 06:06 ` Bradford Boyle <[email protected]>
2024-04-05 07:38 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
1 sibling, 1 reply; 18+ messages in thread
From: Bradford Boyle @ 2024-04-05 06:06 UTC (permalink / raw)
To: Christoph Berg <[email protected]>; +Cc: [email protected]
Hi Christoph,
> where are we with MobilityDB? Are the remaining test failures a
> problem in the source, or just artifacts of the way we try to run the
> tests?
I pushed a commit to s.d.o this past weekend updating the version from
1.1.0~rc.1 to 1.1.0. Looking at the latest build on pgdgbuild [1], I see
that there is a failure for sid amd64. I've only looked at the build
output briefly but it looks like the failure is building against
postgres 12:
meos/src/general/tsequence.c:3116:19: error: implicit declaration
of function ‘hash_bytes_uint32’;
There have been some recent commits on this file (tsequence.c) between
1.1.0~rc.1 and 1.1.0 but I'll need to investigate more to figure out a
fix.
--Bradford
[1]: https://pgdgbuild.dus.dg-i.net/job/mobilitydb-binaries/8/
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
@ 2024-04-05 07:38 ` Christoph Berg <[email protected]>
2024-04-08 02:25 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
0 siblings, 1 reply; 18+ messages in thread
From: Christoph Berg @ 2024-04-05 07:38 UTC (permalink / raw)
To: Bradford Boyle <[email protected]>; +Cc: [email protected]
Re: Bradford Boyle
> I pushed a commit to s.d.o this past weekend updating the version from
> 1.1.0~rc.1 to 1.1.0. Looking at the latest build on pgdgbuild [1], I see
> that there is a failure for sid amd64. I've only looked at the build
> output briefly but it looks like the failure is building against
> postgres 12:
>
> meos/src/general/tsequence.c:3116:19: error: implicit declaration
> of function ‘hash_bytes_uint32’;
>
> There have been some recent commits on this file (tsequence.c) between
> 1.1.0~rc.1 and 1.1.0 but I'll need to investigate more to figure out a
> fix.
If it's not trivial to fix, there is always the option to exclude the
older PG versions from the build. 12 is going to be EOL soonish
anyway.
Christoph
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-05 07:38 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
@ 2024-04-08 02:25 ` Bradford Boyle <[email protected]>
2024-04-08 15:45 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
0 siblings, 1 reply; 18+ messages in thread
From: Bradford Boyle @ 2024-04-08 02:25 UTC (permalink / raw)
To: Christoph Berg <[email protected]>; +Cc: [email protected]
Hi Chistoph,
I pushed a commit to s.d.o dropping support for Postgres 12 for
MobilityDB. Can you trigger another build on pgdgbuild?
Thanks,
--Bradford
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-05 07:38 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-08 02:25 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
@ 2024-04-08 15:45 ` SCHOEMANS Maxime <[email protected]>
2024-04-09 05:55 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-14 00:58 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
0 siblings, 2 replies; 18+ messages in thread
From: SCHOEMANS Maxime @ 2024-04-08 15:45 UTC (permalink / raw)
To: Bradford Boyle <[email protected]>; Christoph Berg <[email protected]>; +Cc: [email protected] <[email protected]>; Esteban Zimanyi <[email protected]>
Hi Christoph, Bradford,
Re: Christoph Berg
> If it's not trivial to fix, there is always the option to exclude the
> older PG versions from the build. 12 is going to be EOL soonish
> anyway.
Re: Bradford Boyle
> I pushed a commit to s.d.o dropping support for Postgres 12 for
> MobilityDB. Can you trigger another build on pgdgbuild?
In case you still want to keep support for Postgres 12, we just
published a bugfix release of MobilityDB (v1.1.1) which contains the fix
needed to run on pg12.
Let us know if there is any way we can help in this packaging effort.
Best,
Maxime
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-05 07:38 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-08 02:25 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-08 15:45 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
@ 2024-04-09 05:55 ` Bradford Boyle <[email protected]>
2024-04-10 06:44 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
1 sibling, 1 reply; 18+ messages in thread
From: Bradford Boyle @ 2024-04-09 05:55 UTC (permalink / raw)
To: SCHOEMANS Maxime <[email protected]>; +Cc: Christoph Berg <[email protected]>; [email protected] <[email protected]>; Esteban Zimanyi <[email protected]>
I've updated the Debian package to build MobilityDB v1.1.1 and added
back Postgres 12 support.
-- Bradford
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-05 07:38 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-08 02:25 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-08 15:45 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
2024-04-09 05:55 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
@ 2024-04-10 06:44 ` Bradford Boyle <[email protected]>
0 siblings, 0 replies; 18+ messages in thread
From: Bradford Boyle @ 2024-04-10 06:44 UTC (permalink / raw)
To: SCHOEMANS Maxime <[email protected]>; +Cc: Christoph Berg <[email protected]>; [email protected] <[email protected]>; Esteban Zimanyi <[email protected]>
Hi Christop,
I was reviewing the latest builds for MobilityDB on pgdgbuild and it
looks like autopkgtest is still failing. The issue is that the cmake
build assumes the source tree is writable and the source tree is not
checked out in the same directory as AUTOPKGTEST_TMP. Here are two lines
from one of the failed autopkgtest runs:
chmod -R go+rwX /tmp/autopkgtest.R3ZFXt/autopkgtest_tmp
...
CMake Error: Could not open file for write in copy operation
/tmp/autopkgtest.R3ZFXt/tree/postgis/postgis_config.h.tmp
This is why recursively chmod-ing the AUTOPKGTEST_TMP didn't work. I
have a fix in mind but need to find some time to verify it.
--Bradford
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-05 07:38 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-08 02:25 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-08 15:45 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
@ 2024-04-14 00:58 ` Bradford Boyle <[email protected]>
2024-04-18 15:08 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
1 sibling, 1 reply; 18+ messages in thread
From: Bradford Boyle @ 2024-04-14 00:58 UTC (permalink / raw)
To: SCHOEMANS Maxime <[email protected]>; +Cc: Christoph Berg <[email protected]>; [email protected] <[email protected]>; Esteban Zimanyi <[email protected]>
Hello Maxime,
I have a development branch [1] for the Debian packaging for MobilityDB
1.1.1 that contains some fixes for the build that allow running the
autopkgtest suite for MobilityDB on pgdgbuild [2]. I needed to update a
couple of CMakeLists.txt to write generated configuration files to the
build directory instead of back to the source directory.
The linked job builds one Debian package per supported Postgres version
and then runs MobilityDB's tests against the installed package. It looks
like there are four failing tests for Postgres 12, 13, 14, 15, and 16:
* 053_tpoint_inout_tbl (Failed)
- problem in alloc set ExprContext: detected write past chunk end in
block 0x560f423d2de0, chunk 0x560f423d2e08
* 070_tpoint_spatialrels (Failed)
* 091_tnpoint_routeops_gin_tbl (Failed)
- invalid memory alloc request size 2139062143
* 091_tnpoint_routeops_tbl (Failed)
- invalid memory alloc request size 2139062143
You can view the full console output (which includes both building and
running the tests) here [3].
Regards,
-- Bradford
[1]: https://salsa.debian.org/postgresql/mobilitydb/-/tree/dev-pgdg-autopkgtest?ref_type=heads
[2]: https://pgdgbuild.dus.dg-i.net/job/mobilitydb-binaries/
[3]: https://pgdgbuild.dus.dg-i.net/job/mobilitydb-binaries/16/architecture=amd64,distribution=sid/consol...
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-05 07:38 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-08 02:25 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-08 15:45 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
2024-04-14 00:58 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
@ 2024-04-18 15:08 ` SCHOEMANS Maxime <[email protected]>
2024-04-22 04:39 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-05-07 15:13 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
0 siblings, 2 replies; 18+ messages in thread
From: SCHOEMANS Maxime @ 2024-04-18 15:08 UTC (permalink / raw)
To: Bradford Boyle <[email protected]>; +Cc: Christoph Berg <[email protected]>; [email protected] <[email protected]>; Esteban Zimanyi <[email protected]>
Hi Bradford,
We have been wanting to avoid writing the config files in the source
tree for some time now, so the patch with the fixed for the build is
very much appreciated.
You are welcome to send a PR to the develop branch [1]on the mobilitydb
repository with these changes.
Concerning the failing tests, we indeed did not catch these as they only
appear when running postgres with debug enabled.
We will update our tests to avoid missing these in the future.
In the mean time, I have fixed the issues on our develop branch [2], so
we could produce a new bugfix release with these fixes and the build
patch if this is the only remaining blocker.
I am attaching the patch with the fixes so you can test it out before we
produce the release.
Let us know if there are any other issues or if we can assist you in
producing the PR with the build patch.
Best,
Maxime
[1]: https://github.com/MobilityDB/MobilityDB/tree/develop
[2]:
https://github.com/mobilityDB/MobilityDB/compare/942b10c47e7966f3d0b61a1d3a66e0400ee4769d...6e0e6572...
Attachments:
[text/x-patch] fix_memory_bugs.patch (3.3K, 2-fix_memory_bugs.patch)
download | inline diff:
diff --git a/meos/src/general/type_out.c b/meos/src/general/type_out.c
index c3cadb057..350ca30fe 100644
--- a/meos/src/general/type_out.c
+++ b/meos/src/general/type_out.c
@@ -848,7 +848,7 @@ tsequenceset_mfjson_size(const TSequenceSet *ss, bool isgeo, bool hasz,
size += ( isgeo ? sizeof("{'coordinates':[],") : sizeof("{'values':[],") ) * ss->count;
size += sizeof("'datetimes':[],'lower_inc':false,'upper_inc':false},") * ss->count;
if (isgeo)
- size = coordinates_mfjson_size(ss->totalcount, hasz, precision);
+ size += coordinates_mfjson_size(ss->totalcount, hasz, precision);
else
{
for (int i = 0; i < ss->count; i++)
diff --git a/mobilitydb/src/npoint/tnpoint_gin.c b/mobilitydb/src/npoint/tnpoint_gin.c
index d011aa535..de9441447 100644
--- a/mobilitydb/src/npoint/tnpoint_gin.c
+++ b/mobilitydb/src/npoint/tnpoint_gin.c
@@ -75,9 +75,9 @@ Tnpoint_gin_extract_value(PG_FUNCTION_ARGS)
Datum *elems = palloc(sizeof(Datum) * routes->count);
for (int i = 0; i < routes->count; i++)
elems[i] = Int64GetDatum(SET_VAL_N(routes, i));
- pfree(routes);
*nkeys = routes->count;
*nullFlags = NULL;
+ pfree(routes);
PG_FREE_IF_COPY(temp, 0);
PG_RETURN_POINTER(elems);
}
@@ -127,9 +127,9 @@ Tnpoint_gin_extract_query(PG_FUNCTION_ARGS)
elems = palloc(sizeof(Datum) * routes->count);
for (int i = 0; i < routes->count; i++)
elems[i] = Int64GetDatum(SET_VAL_N(routes, i));
- pfree(routes);
*nkeys = routes->count;
*searchMode = GIN_SEARCH_MODE_DEFAULT;
+ pfree(routes);
PG_FREE_IF_COPY(temp, 0);
break;
default:
diff --git a/postgis/liblwgeom/lwhomogenize.c b/postgis/liblwgeom/lwhomogenize.c
index 70c39e9ee..ac20ab7a7 100644
--- a/postgis/liblwgeom/lwhomogenize.c
+++ b/postgis/liblwgeom/lwhomogenize.c
@@ -101,7 +101,7 @@ lwcollection_build_buffer(const LWCOLLECTION *col, HomogenizeBuffer *buffer)
buffer->buf[geom->type] = bufcol;
}
/* Add sub-geom to buffer */
- lwcollection_add_lwgeom(buffer->buf[geom->type], lwgeom_clone(geom));
+ lwcollection_add_lwgeom(buffer->buf[geom->type], lwgeom_clone_deep(geom));
/* Increment count for this singleton type */
buffer->cnt[geom->type]++;
break;
@@ -217,7 +217,7 @@ lwgeom_homogenize(const LWGEOM *geom)
return lwcollection_as_lwgeom(lwcollection_construct_empty(geom->type, geom->srid, lwgeom_has_z(geom), lwgeom_has_m(geom)));
}
- return lwgeom_clone(geom);
+ return lwgeom_clone_deep(geom);
}
switch (geom->type)
@@ -231,7 +231,7 @@ lwgeom_homogenize(const LWGEOM *geom)
case TRIANGLETYPE:
case CURVEPOLYTYPE:
case POLYGONTYPE:
- return lwgeom_clone(geom);
+ return lwgeom_clone_deep(geom);
/* Process homogeneous geometries lightly */
case MULTIPOINTTYPE:
@@ -247,7 +247,6 @@ lwgeom_homogenize(const LWGEOM *geom)
/* Strip single-entry multi-geometries down to singletons */
if ( col->ngeoms == 1 )
{
- // hgeom = lwgeom_clone((LWGEOM*)(col->geoms[0])); // MobilityDB changed
hgeom = lwgeom_clone_deep((LWGEOM*)(col->geoms[0]));
hgeom->srid = geom->srid;
if (geom->bbox)
@@ -256,7 +255,7 @@ lwgeom_homogenize(const LWGEOM *geom)
}
/* Return proper multigeometry untouched */
- return lwgeom_clone(geom);
+ return lwgeom_clone_deep(geom);
}
/* Work on anonymous collections separately */
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-05 07:38 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-08 02:25 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-08 15:45 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
2024-04-14 00:58 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-18 15:08 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
@ 2024-04-22 04:39 ` Bradford Boyle <[email protected]>
1 sibling, 0 replies; 18+ messages in thread
From: Bradford Boyle @ 2024-04-22 04:39 UTC (permalink / raw)
To: [email protected] <[email protected]>; +Cc: Christoph Berg <[email protected]>; Esteban Zimanyi <[email protected]>; SCHOEMANS Maxime <[email protected]>
Hello,
I’ve updated the packaging for MobilityDB 1.1.1 to address the
autopkgtest issues when building on pgdg. MobilityDB does not build on
buster becuase of the old version of libproj; the package also fails to
build on i386. Additionally there are test failures on s390x. Attached
is a patch for pgapt to exclude these (buster, i386, and s390z) from the
build.
--Bradford
Attachments:
[application/octet-stream] 0001-Disable-mobilitydb-on-unsupported-arch-and-dist.patch (797B, 2-0001-Disable-mobilitydb-on-unsupported-arch-and-dist.patch)
download | inline diff:
From 53d1cd9b0e7bb2d8ece54e1c842c37cc8289f31e Mon Sep 17 00:00:00 2001
From: "Bradford D. Boyle" <[email protected]>
Date: Thu, 18 Apr 2024 21:04:24 -0700
Subject: [PATCH] Disable mobilitydb on unsupported arch and dist
---
jenkins/pgapt-jobs.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/jenkins/pgapt-jobs.yaml b/jenkins/pgapt-jobs.yaml
index 4619033..18090c4 100644
--- a/jenkins/pgapt-jobs.yaml
+++ b/jenkins/pgapt-jobs.yaml
@@ -1185,6 +1185,8 @@
git-branch: main
upstream-url: https://github.com/MobilityDB/MobilityDB.git
upstream-branch: develop
+ arch-filter: 'architecture in ["amd64", "arm64", "ppc64el"]'
+ dist-filter: '!(distribution in ["buster"])'
jobs:
- git+upstream-snapshot
--
2.44.0
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-05 07:38 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-08 02:25 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-08 15:45 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
2024-04-14 00:58 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-18 15:08 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
@ 2024-05-07 15:13 ` Christoph Berg <[email protected]>
2024-05-15 15:42 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
1 sibling, 1 reply; 18+ messages in thread
From: Christoph Berg @ 2024-05-07 15:13 UTC (permalink / raw)
To: SCHOEMANS Maxime <[email protected]>; Bradford Boyle <[email protected]>; +Cc: [email protected] <[email protected]>; Esteban Zimanyi <[email protected]>
Re: SCHOEMANS Maxime
> Let us know if there are any other issues or if we can assist you in
> producing the PR with the build patch.
Hi,
one more thing that would be nice: Every time you invoke `psql` during
testing, it should really be `psql -X` so it doesn't read the user's
~/.psqlrc file. In my case, the `\pset linestyle unicode` and
`\timing` in there cause a lot of noise in the test results.
Re: Bradford Boyle
> I’ve updated the packaging for MobilityDB 1.1.1 to address the
> autopkgtest issues when building on pgdg. MobilityDB does not build on
> buster becuase of the old version of libproj; the package also fails to
> build on i386. Additionally there are test failures on s390x. Attached
> is a patch for pgapt to exclude these (buster, i386, and s390z) from the
> build.
I've finally found the time to get back to this; the build is running.
Sorry, sometimes I'm overwhelmed by TODO items and then simply drop
some of them indefinitely.
Cheers,
Christoph
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Updated packaging for MobilityDB 1.1.0
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-06 16:25 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2023-11-08 07:19 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Re: Updated packaging for MobilityDB 1.1.0~beta1 Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-05 07:38 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-08 02:25 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-08 15:45 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
2024-04-14 00:58 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-18 15:08 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
2024-05-07 15:13 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
@ 2024-05-15 15:42 ` SCHOEMANS Maxime <[email protected]>
0 siblings, 0 replies; 18+ messages in thread
From: SCHOEMANS Maxime @ 2024-05-15 15:42 UTC (permalink / raw)
To: Christoph Berg <[email protected]>; +Cc: [email protected] <[email protected]>; Bradford Boyle <[email protected]>; Esteban Zimanyi <[email protected]>
Hi,
Thanks a lot for your work.
> one more thing that would be nice: Every time you invoke `psql` during
> testing, it should really be `psql -X` so it doesn't read the user's
> ~/.psqlrc file. In my case, the `\pset linestyle unicode` and
> `\timing` in there cause a lot of noise in the test results.
Indeed, this is something we did not think of.
I changed this on both master and stable-1.1, so it will be fixed in all
upcoming releases.
Best,
Maxime
On 07/05/2024 17:13, Christoph Berg wrote:
> Re: SCHOEMANS Maxime
>> Let us know if there are any other issues or if we can assist you in
>> producing the PR with the build patch.
> Hi,
>
> one more thing that would be nice: Every time you invoke `psql` during
> testing, it should really be `psql -X` so it doesn't read the user's
> ~/.psqlrc file. In my case, the `\pset linestyle unicode` and
> `\timing` in there cause a lot of noise in the test results.
>
> Re: Bradford Boyle
>> I’ve updated the packaging for MobilityDB 1.1.1 to address the
>> autopkgtest issues when building on pgdg. MobilityDB does not build on
>> buster becuase of the old version of libproj; the package also fails to
>> build on i386. Additionally there are test failures on s390x. Attached
>> is a patch for pgapt to exclude these (buster, i386, and s390z) from the
>> build.
> I've finally found the time to get back to this; the build is running.
>
> Sorry, sometimes I'm overwhelmed by TODO items and then simply drop
> some of them indefinitely.
>
> Cheers,
> Christoph
^ permalink raw reply [nested|flat] 18+ messages in thread
end of thread, other threads:[~2024-05-15 15:42 UTC | newest]
Thread overview: 18+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-11-04 23:19 Updated packaging for MobilityDB 1.1.0~beta1 Bradford Boyle <[email protected]>
2023-11-05 14:04 ` Christoph Berg <[email protected]>
2023-11-06 16:25 ` Christoph Berg <[email protected]>
2023-11-08 07:19 ` Bradford Boyle <[email protected]>
2023-11-08 08:13 ` Christoph Berg <[email protected]>
2024-04-04 12:12 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-04 12:24 ` Re: Updated packaging for MobilityDB 1.1.0 Esteban Zimanyi <[email protected]>
2024-04-05 06:06 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-05 07:38 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-04-08 02:25 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-08 15:45 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
2024-04-09 05:55 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-10 06:44 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-14 00:58 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-04-18 15:08 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
2024-04-22 04:39 ` Re: Updated packaging for MobilityDB 1.1.0 Bradford Boyle <[email protected]>
2024-05-07 15:13 ` Re: Updated packaging for MobilityDB 1.1.0 Christoph Berg <[email protected]>
2024-05-15 15:42 ` Re: Updated packaging for MobilityDB 1.1.0 SCHOEMANS Maxime <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox