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 1qRPuN-001d6P-Vx for pgsql-pkg-debian@arkaria.postgresql.org; Thu, 03 Aug 2023 04:25:56 +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 1qRPuM-009n4q-9I for pgsql-pkg-debian@arkaria.postgresql.org; Thu, 03 Aug 2023 04:25:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qRPuM-009n4h-18 for pgsql-pkg-debian@lists.postgresql.org; Thu, 03 Aug 2023 04:25:54 +0000 Received: from mail-lj1-x236.google.com ([2a00:1450:4864:20::236]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qRPuJ-000GP0-QI for pgsql-pkg-debian@lists.postgresql.org; Thu, 03 Aug 2023 04:25:53 +0000 Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-2b9b5ee9c5aso7521461fa.1 for ; Wed, 02 Aug 2023 21:25:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691036751; x=1691641551; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ULtCPRWfmkOm41ZheGUsBgtr8yrpG6LTQ+AaRj4mI3Y=; b=ZkgEow6NrGWsF5kRPELDo3ZRvmbTKFkl3artV+rV65Az5R/qrcMoGWn7BhOdijm77O a2GuV1QsqQDrzCjIGHXjyMIIrAdR6cW0Yl2sa6uMzP60CI7eOZ8ufGdBzTyz3+u7YQ+d sBnOGkHcOhOSq+sP180wvJh98buYmwSb9ap9Pabw7yBLUCJese0nzoqp98vtiutHsBdy eCgNHqhMAYPpCvi0Bn4htuP1djrE/tlQywZP8YXFNs26GXsHtOy1EigoRsHwlRrT8dq8 ZJPK9uqZk89abu/Jc1kzQOYCKZ+wM0v/0bWRz/4cLUKdWn3Aadm1PzdZUNwHrGQ1vTJf 244w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691036751; x=1691641551; 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=ULtCPRWfmkOm41ZheGUsBgtr8yrpG6LTQ+AaRj4mI3Y=; b=lgwrivW+UM3zKjKPfJCeBeqcpTwgUGjUlwwfZ8C/jvXhCteCugK+ZtGxyzUTJ6+68c uPJskkObni1qicjqdmGEDXM5nyawch32dHRD6t+yDDr2i/j10gftXAMqkYfcXj8B0PZo UsTqia6voikfU4ETP8+LQVvDXSD1hb43YmTAPUUo/YoI1OGrBWJCY58njg0b8y+857zv gpDtMjk8G54uTXWG/hL+esXBsA0RqIu0KYtv0GgdiYwo7V2SoZjV3cVEOR0DcYhouyYO nbUYpO86chjFX3AWf9ZEQD7bW5BZ+qrKFcAwsO5fVCCIGbvvlfW3LrCd9otHlftVa57/ Vnrg== X-Gm-Message-State: ABy/qLZcPcGllZHBGJzS5myyrp3bVeWGRCXExPpqXN2OtuphcKm+SHUC 5WVCsFIseDGkODM2ugI3zIbtxt6+DWEHS30wHUU= X-Google-Smtp-Source: APBJJlEvwV5abco4XoSA2HB4do9Rnew7hPj2Z273m+7noZ7pHy8M3GLEzeHYuXX83lk2RYskn+fqKhA/ICnXil3H6cg= X-Received: by 2002:a2e:870b:0:b0:2b4:5cad:f246 with SMTP id m11-20020a2e870b000000b002b45cadf246mr6477845lji.7.1691036750409; Wed, 02 Aug 2023 21:25:50 -0700 (PDT) MIME-Version: 1.0 References: <75679669-4482-3f16-bd4d-6ec1f9950941@abcsql.com> In-Reply-To: From: Bradford Boyle Date: Wed, 2 Aug 2023 21:25:38 -0700 Message-ID: Subject: Re: Packaging request MobilityDB To: Esteban Zimanyi Cc: Christoph Berg , =?UTF-8?Q?C=C3=A9dric_Villemain?= , pgsql-pkg-debian@lists.postgresql.org, SCHOEMANS Maxime Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, Thank you for the initial round of feedback. > 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: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 ... I've made some changes to how the autopkg tests are run and the tests are running and passing when building with sbuild on arm64 (I don't have an amd64 environment available at the momment). Now that there is a pre-release tag on GitHub, I've enabled the CI/CD in s.d.o to point at d/gitlab-ci.yml > debian/copyright: LICENSE mentions the ULB - haven't checked the rest > of the source yet I still need to update d/copyright -- there are several different copyrights in the source (PGDG, ULB, PostGIS, etc) that I need to add to d/copyright. This is the area of packaging that I am less familiar with, so any high-level suggestions would be appreciated. > debian/tests/installcheck: Why is that .so trickery necessary? If > mobilitydb needs postgis that way, it should link against it. Mobilitydb needs postgis -- without setting shared_preload_libraries, tests fail with the errors similar to this one ERROR: could not load library "/usr/lib/postgresql/15/lib/libMobilityDB-1.1.so": /usr/lib/postgresql/15/lib/libMobilityDB-1.1.so: undefined symbol: ST_Intersects I've spent some time trying to patch the CMake build to link mobilitydb against postgis with no success. If I update CMakeLists.txt to link with -L /usr/lib/postgresql/15/lib -lpostgis-3, the build fails with /usr/bin/ld: cannot find -lpostgis-3.so: No such file or directory I think this is because postgis-3.so doesn't have a SONAME field set. If the build links w/ /usr/lib/postgresql/15/lib/postgis-3.so, then dpkg-shlibdebs fails with cannot find library /usr/lib/postgresql/15/lib/postgis-3.so needed by build/libMobilityDB-1.1.so (ELF format: 'elf64-x86-64' abi: '0201003e00000000'; RPATH: '') > 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.) I've updated d/control to use the postgresql-postgis package. --Bradford