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 1rvoDJ-00EdRM-V2 for pgsql-pkg-debian@arkaria.postgresql.org; Sun, 14 Apr 2024 00:59: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 1rvoDH-0061fl-Vg for pgsql-pkg-debian@arkaria.postgresql.org; Sun, 14 Apr 2024 00:59:19 +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 1rvoDH-0061fd-PY for pgsql-pkg-debian@lists.postgresql.org; Sun, 14 Apr 2024 00:59:19 +0000 Received: from mail-lj1-x22c.google.com ([2a00:1450:4864:20::22c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rvoD9-000oVZ-Pf for pgsql-pkg-debian@lists.postgresql.org; Sun, 14 Apr 2024 00:59:18 +0000 Received: by mail-lj1-x22c.google.com with SMTP id 38308e7fff4ca-2da08b07157so22583641fa.1 for ; Sat, 13 Apr 2024 17:59:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713056349; x=1713661149; 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=u38b2mTLQ/uu0RxXc0L9mNA4maOlGuVJXVwdIl26+YM=; b=Kw6HEULTkrvvBBnmwumeyv69aXBH9OSncWmuBMgQGXLer9WtSZ51WaMtyjEmjZP71w Nk4rRIb9ZUo+F3JbykB7n8dgZkFA7HCOXK4VmDjaoNcyoo7pReC6/dWpEO+eIra21OKw SuFCWQUCL0KQNrwRHGOnS48P5mGc9fszGfF8UdYpzRY4724CJGtbBcbSMh2v+o8caxVp qWdJX/pcsPooKf4VWyYTyW+cdxIbqcXMiZaUUBxbH4NQTcsXQD7kk8/FEhBUP/1GdkPJ Nh0V6beKI5XmE8aDnkGQEyhJ5YuyWZzywyeyArI8YWglMXY6pbQY/VASNLQ7j78dCjDl V6VQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713056349; x=1713661149; 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=u38b2mTLQ/uu0RxXc0L9mNA4maOlGuVJXVwdIl26+YM=; b=Wo9B9tZl6U27tHXZ6ie5t8vTa341+PNbsQ24aYr8MU9Weensjp4sTLPuPYdCEhsrCF RpJ2bY8tHsEkvT18I+Hwky9u9XRq8i3X5nflSbKVMyy50uBjlBktwuBmepFuNK8Osqxg EPw2z6iH/o71TQ8Qa0BkSMUsfx7g4wAByHAhD594ekIK7EutIf2kfZN7YKiMPoQnwA6N YmoerEjzZDwmzABT281SMlPOJpfT5LwlhO2gstcVbTZuWYQkDKru789c9YhMTFvP8SZm bYwtgjKIEhSSv5wXRWHPnxU0RYJ69zMiOoxKkrJwQfiM6a3y280g09IhrgPEDQzHUQvl AH6A== X-Forwarded-Encrypted: i=1; AJvYcCUO6GlCGPiV7XR7Pz1HGi3RPrOJesU8CZXKspbjvfYL3gBjAtVB/ENT1qwO9G8bmNcgTlzi8M5Kb0l5ylkxnqAwQ1OlJR94ztgAat3VB9jX9cfHGPEF X-Gm-Message-State: AOJu0Yy7VRl+aigxAkLXRkh/ntPVs6pDbCmMB0M6RKIkDmMPsPLZw9JP ogOwQqxAQfVpJS7HRBaxDZLPHtoD5ZE/JXpGgmWHrBvJi4jx2l4ilKaUYXRAVfoZYuPmM/mDf8k nnqGcHSgS2px6Q/eP4V7mLGDBQvs= X-Google-Smtp-Source: AGHT+IFjoMuqTT0a6RNbCGtpp7rnvOBgd4bdIzoPgUs//iVnXoIDO1x0/WD4LloXdhXKyRu5cQjwpD9k0cOFlIr+YzA= X-Received: by 2002:a2e:2205:0:b0:2d8:7266:ae74 with SMTP id i5-20020a2e2205000000b002d87266ae74mr4135488lji.26.1713056349205; Sat, 13 Apr 2024 17:59:09 -0700 (PDT) MIME-Version: 1.0 References: <4c8a11b6-8828-47db-b2d0-cd67e9b7224d@ulb.be> In-Reply-To: <4c8a11b6-8828-47db-b2d0-cd67e9b7224d@ulb.be> From: Bradford Boyle Date: Sat, 13 Apr 2024 17:58:57 -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 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/consoleText