Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qQVgY-0008V9-Hd for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 31 Jul 2023 16:23:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qQVfX-000toL-Gk for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 31 Jul 2023 16:22:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qQVfX-000toD-Ax for pgsql-pkg-debian@lists.postgresql.org; Mon, 31 Jul 2023 16:22:52 +0000 Received: from mail-lf1-x12c.google.com ([2a00:1450:4864:20::12c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qQVfV-0001QA-J2 for pgsql-pkg-debian@lists.postgresql.org; Mon, 31 Jul 2023 16:22:51 +0000 Received: by mail-lf1-x12c.google.com with SMTP id 2adb3069b0e04-4f95bf5c493so7587640e87.3 for ; Mon, 31 Jul 2023 09:22:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690820568; x=1691425368; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=blQZe0J82FIJrEvQ55D+xHPBIlwV2kNpUYrkOUyYF+w=; b=KjhZAQxDdaN99kTAXnQ4Yvl1BGeePc08lBwbuwot+ko0oMhRt/A86wFKAZpvsyNhsf 2f2K3HwkoSMsKFgRpF7R8MZiz1Kt2uCiDQZFzWVKjA1eyyP4eI0sL8IOXYo52QItZBOL dRaP4+h8966ltABUATpep2hhyoCHnnzbZoTIGPTzjTHwbOfTu0yGCce5PseNspZpp7um xtNwGq9TcuEYF1g9ClxPBseg9B4KyoMgLPpLqglL+A43D0moFm6dDl7I1N9pAjOBfCgD T9sguLyggNVeI01Bmoy4/6wZ4jnE7M12hgVfKM0zHipYADYAKKl2atZOcwG5g/rXxTfJ PFsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690820568; x=1691425368; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=blQZe0J82FIJrEvQ55D+xHPBIlwV2kNpUYrkOUyYF+w=; b=KB0xOqGew7BVqVfZChRz6Zwk1rgiR2qkILqrGDcTRcl/WaoNe7EPFV7bS9Z/8fgjj3 nrIqF9bqeLfEiYQKIRSh6Pwfq8QWclLDDCJEV1LjPtepIC7jIGlrDsWfp1T4fJty7Yqo 1avVnoKZyfxMQx9unFDET31fiArkYXZWLeU1EcsXqns55OL6CkWxfA4kNNc8J08ahFI+ jgdvLaEVlr9m9HJ3JFcxxvNNatzNKQTO9Hv3roDZ62t235Ql4AEEKnq4h6C0PUsHqWE7 NzR2Gari07KYP+PR9Y/n4daRslWE87cLE20PkzRcvQC8RTX2VqOu4aeO8g+3x2ZEaqoU uBug== X-Gm-Message-State: ABy/qLYWXVoXmGPcwULzwltbrvZi/kxaCVSWGvrVGq53v6DNCQsL6WRS tPF7GFDJcoLq6GzokHoO4A/SsPAFkX2tGlGHAs0= X-Google-Smtp-Source: APBJJlHjVPrTKQiGVu4tk7eiq5EZ9/jdJVvjkpxcozw+5+K5lB3pQZIZQlPwZvA+E80Sy3AZ6M36ocbZD0MTYdvSheg= X-Received: by 2002:a05:6512:747:b0:4fd:bec3:776a with SMTP id c7-20020a056512074700b004fdbec3776amr165135lfs.61.1690820567375; Mon, 31 Jul 2023 09:22:47 -0700 (PDT) MIME-Version: 1.0 References: <75679669-4482-3f16-bd4d-6ec1f9950941@abcsql.com> In-Reply-To: From: Esteban Zimanyi Date: Mon, 31 Jul 2023 18:22:11 +0200 Message-ID: Subject: Re: Packaging request MobilityDB To: Christoph Berg Cc: Bradford Boyle , =?UTF-8?Q?C=C3=A9dric_Villemain?= , pgsql-pkg-debian@lists.postgresql.org, SCHOEMANS Maxime Content-Type: multipart/alternative; boundary="0000000000004c22d10601cad7b8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004c22d10601cad7b8 Content-Type: text/plain; charset="UTF-8" > Yes I was building off that tag. Great! Regarding the question of PostGIS versions, in our CI workflows we are testing with PG versions 12-15 (and tested already with PG 16 beta but waiting for the official release to add PG 16) with the latest available PostGIS version for that PG version (MobilityDB is not compatible with PostGIS 2.5 for various technical reasons). For example, in the last run https://github.com/MobilityDB/MobilityDB/actions/runs/5714733863/job/15482641928 we can find postgresql-12-postgis-3 postgresql-13-postgis-3 postgresql-14-postgis-3 postgresql-15-postgis-3 I don't know whether this answers your question .... --0000000000004c22d10601cad7b8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> Yes I was building off that tag.
Great!

Re= garding the question of PostGIS versions, in our CI workflows we are testin= g with PG versions 12-15 (and tested already with PG 16 beta but waiting fo= r the official release to add PG 16) with the latest available PostGIS vers= ion for that PG version (MobilityDB is not compatible with PostGIS 2.5 for = various technical reasons).

For example, in the last run=
we can find

postgresql-12-postgis-3
postgresql-13-postgis-3postgresql-14-postgis-3
postgresql-15-postgis-3

I don't know whether this answers your question ....

--0000000000004c22d10601cad7b8--