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 1r0crP-006rtA-2H for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 08 Nov 2023 07:20:23 +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 1r0cqP-00HTz8-Lu for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 08 Nov 2023 07:19:21 +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 1r0cqP-00HTvP-Ck for pgsql-pkg-debian@lists.postgresql.org; Wed, 08 Nov 2023 07:19:21 +0000 Received: from mail-lj1-x231.google.com ([2a00:1450:4864:20::231]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1r0cqN-005J4l-DQ for pgsql-pkg-debian@lists.postgresql.org; Wed, 08 Nov 2023 07:19:20 +0000 Received: by mail-lj1-x231.google.com with SMTP id 38308e7fff4ca-2c5210a1515so90045041fa.0 for ; Tue, 07 Nov 2023 23:19:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699427958; x=1700032758; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pVcXS7ygOztpTpnDKjdpiTXtt0sNw07vh5Ryzi3bf+g=; b=ROSnuHW1JIIBeKLU8i+qZdNfkYUkpp+6B9CN973Y2WLudmugwD3HHlMpnd17ScTTf7 TMakpa6THhW0XFZjdaeymfA24phrbVtWuwCrIb+Hz+W7mPQ60DobWhN6HCiLRsJmA3/S /YK3NeMN1rCIyOlvaQiMkRxpHNdkOwPPYgQiYgIirAVNRhOtu2rTyCqK8VhOyIBFcCaA pjf+xZpkvuP7c33KM7gVSRcFxKce11NNWF2HF5K80Acjf1lIxQstzhprzsawS0Wc12kN ilvrBB72PDTKXv09hlXLnIll0O3YJSCfqsYd0kB5wJZlpFdWoBAsZNh2sQ2kjrbGcfm3 1Qtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699427958; x=1700032758; 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=pVcXS7ygOztpTpnDKjdpiTXtt0sNw07vh5Ryzi3bf+g=; b=S02NbTxemi8HCuQxCjQMxRdyOq1/DflSL1dL0nqZUG5TtlwTeUmFfPN3pdCasbIv4k xaxIxx06YT2cHmTSFd0il+HAT5+6eQo6sz7F53iWJoGZtalAxCi1yiTlZdWMaVOtJJq2 +jHZUOACRLI6mEE78mZNFWGfv9Kh40G0p/de1/JtAFGQqq1v57/jufZbtJJNSE04jJo2 PizOrvimh5cx8pC0s1Cr0Wha2rMBJ10TJ042Kljub7PVCuKqF51WLZ3VAkwkYrmSrDqL yYCbKCOm/bWdPsDm1B5zF7b37mzLXhCelFmxrN8Otkpxopk0s7W2i3SAxXBnpUcw4xwV UTkg== X-Gm-Message-State: AOJu0Yy8un4KGxViuRbHAB5gR9J6PeQPP6pA9hncBylxwyhyvnw7LB6l JpFkvEmZ0uPwTymjVmw7uLKw47anDEEXr/KWIdU= X-Google-Smtp-Source: AGHT+IFcKpot5gI691UEtcRQdZQsmd5A7Ro1To1YEVtRR9Gv+wM5oGzVurZ5xsQdWYA68eVl+pwnvV8ZCUDAbdcvqss= X-Received: by 2002:a2e:be1c:0:b0:2c6:f4b8:1d88 with SMTP id z28-20020a2ebe1c000000b002c6f4b81d88mr1383798ljq.20.1699427957908; Tue, 07 Nov 2023 23:19:17 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Bradford Boyle Date: Tue, 7 Nov 2023 23:19:06 -0800 Message-ID: Subject: Re: Updated packaging for MobilityDB 1.1.0~beta1 To: Christoph Berg Cc: pgsql-pkg-debian@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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