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 1ruRgz-005TDh-DC for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 10 Apr 2024 06:44:21 +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 1ruRgy-00GP3Z-4T for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 10 Apr 2024 06:44:20 +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 1ruRgx-00GP3R-Uc for pgsql-pkg-debian@lists.postgresql.org; Wed, 10 Apr 2024 06:44:19 +0000 Received: from mail-lj1-x232.google.com ([2a00:1450:4864:20::232]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ruRgv-0028i2-Ba for pgsql-pkg-debian@lists.postgresql.org; Wed, 10 Apr 2024 06:44:18 +0000 Received: by mail-lj1-x232.google.com with SMTP id 38308e7fff4ca-2d476d7972aso81968811fa.1 for ; Tue, 09 Apr 2024 23:44:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712731456; x=1713336256; 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=K3YAfgJt2uCOdYpyqRnNKHp82Z+6gPzpDET9x6/sap4=; b=SLYDE1MpP2dA/5qHcdh5jpGohB0wEcdtCFse92mcSIy4uSJidoL06EBBT7fS0cpTaz 5j8I6/NmAt0FmlMrW/4mzxA0zJuQQFeNce30EiewGl24BjHYrvMi/W4qtDzzBiPtn0e5 xXlqJ7BHYa0kT2IO+P2N+tVmIuOey2LDdxV7aVVzywx14wapxts8rgcpwC5fDm4aRFFz 3goxDnWZVnVbFUcacveG1anUSoloWzWZBw1NrVQb58YcfL5P59SvCNe0Gs4/68vSNysq 2KPmPmEykkGwcFqZSwloK7yIyg3o0BM4u5dH/GiX/fX9z35gCosIZdH/E+0W1aO88cre xNbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712731456; x=1713336256; 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=K3YAfgJt2uCOdYpyqRnNKHp82Z+6gPzpDET9x6/sap4=; b=TWl1/h1Z4q11gCWqR8jYkDsWx0eUL9rv6/541WK766pdtlDSqaGQL5SMy5+6tDIXmw 3QZtJx+LzvCcV6l9iXa4BPvSY7wjmqS2xvtiEO5ytb9ODLd+fIhLKpvhYLt2wx3oR2KW 3lbrt0MlcOQH28SxMcU12mXQ111e29NowsdI5c3zMRc6re233iRvxL9f5OYEALi1nsAF FjQEHKJ5qPePr9e2mEYUb9+4CMrTKSPzSmNMW0aMyTxW1JafCpvZ/k2A1gGW6sjbKiff 4zPKc4ChOMSfp5bGShcJMHMbPKSjbJsTdy2b6sLDtx6r9ZE0E4ZzHCvXwPGl1sexdya5 z2lA== X-Forwarded-Encrypted: i=1; AJvYcCWyDlJHL4dVEOVIcDd2A+pID0KXp5yBonPUNDEm5/CKofItAIa4NI/NZq/g2RzSEOHD6aQkwVhUcB26Bm9TDGbr9O24cLuUu2PAS4jTTmzWad1oEPuj X-Gm-Message-State: AOJu0YyVCj/xS+G3aoGpnCBcGQdXWliYZpC7m/PYPDojRMyDcJmhOaJ1 +K0KRz8lSBmlV55lpAqPlgx3LRR+Us+QsvRIqYelHXvl3NiUtMf8wBvW7066yNvW9yWskrNYXCy /xc//Do8h+PH51VKukjT8d+N0r5U= X-Google-Smtp-Source: AGHT+IGh4mVx1+2D29iNHbbVCNGuSTuaAVPD8H8lqIEAt1z1EfVE488jiqdzYubsNuIJq01vdfuRkGEYgE1mN/6vcS8= X-Received: by 2002:a2e:a7d4:0:b0:2d8:3d0d:aa03 with SMTP id x20-20020a2ea7d4000000b002d83d0daa03mr1987777ljp.29.1712731455374; Tue, 09 Apr 2024 23:44:15 -0700 (PDT) MIME-Version: 1.0 References: <4c8a11b6-8828-47db-b2d0-cd67e9b7224d@ulb.be> In-Reply-To: From: Bradford Boyle Date: Tue, 9 Apr 2024 23:44:03 -0700 Message-ID: Subject: Re: Updated packaging for MobilityDB 1.1.0 To: SCHOEMANS Maxime Cc: Christoph Berg , "pgsql-pkg-debian@lists.postgresql.org" , Esteban Zimanyi Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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