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 1rsM13-006Wjq-L0 for pgsql-pkg-debian@arkaria.postgresql.org; Thu, 04 Apr 2024 12:16:26 +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 1rsM12-004FUJ-Oi for pgsql-pkg-debian@arkaria.postgresql.org; Thu, 04 Apr 2024 12:16:24 +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 1rsM12-004FS5-IP for pgsql-pkg-debian@lists.postgresql.org; Thu, 04 Apr 2024 12:16:24 +0000 Received: from mail-ej1-x633.google.com ([2a00:1450:4864:20::633]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rsM0z-000Wo8-6u for pgsql-pkg-debian@lists.postgresql.org; Thu, 04 Apr 2024 12:16:23 +0000 Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-a517d773844so126055666b.1 for ; Thu, 04 Apr 2024 05:16:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712232979; x=1712837779; 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=PJV5+RY0b2DsqdM8EUiO7g1xA1M0ylpoR9rIwAn57yk=; b=K0qNEog6wT1Jyr6CpVWKoMlC+3VhjDrSv5LGDVtZzVN+1QkD/Uc8sPP6g3JOuO+98Q HKJFNpATv1uz814GtR48QzgwXg1cm0fAcBB3EGy2ZQI35igUFAlmalsQ/2HLAn2pB3SH iYqVU04954gwzCEIkID+vpM4/0NjH2M0MH1tdD7ZJv6GMKnBKZFVeZzw+d/7dMYJpdzh tkI57eXJLc2xohkEcLp/PJ7lFzV9BQU3dEGUmygHH53ox+sCU0CTJf+QqfpStMwLp83g IVayQBarz3peDrwX4u+Cjd5mTFqpJcUJAFQDbybRfW6sGmdw4StV1W383y14lX8s84q0 f4XA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712232979; x=1712837779; 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=PJV5+RY0b2DsqdM8EUiO7g1xA1M0ylpoR9rIwAn57yk=; b=qlvPlBA2UgJcf3r6jJng9bURB8+AsS6ODlMn3/Q02CizabYnev5nAUZ3q97PSArlyt n/qjNalik6fiV1B/XNAi6AWriYHH+SFm3XFkQ5o7IxhTbYmGeF1GpFa/POK6qCVkbju5 4AzLc6pTYz0mR69nZnp6MmaaYTJEyAbOqz4pwbgLlmUwQExsxj2F2UhHD3NZQSHc4zUw eAnZo+KAPT29hDENDKCuzOjZ7C5l3dMbzh806gi/VBYj6uTWAHfJ1xZ61ZSdPV7mAxIy s3SMic+XMID6JpYphLflBGK3rx8RsO9Tzy1k54yUf7z84xeHJMJmySc+vhHwkRBSSY80 JjHA== X-Forwarded-Encrypted: i=1; AJvYcCUPDtQ6EvHt4Mg0Zd7qg6GeUpgTfCzHyhZ6+VkfJyOfOkurLSWlIimUlI+eIf+h6HoPx2pcKdLQAZ6FxuatbXISmbSqWJE2l3JoMNX0I7TQ8cRKBDZH X-Gm-Message-State: AOJu0Yx6KAAFExvxZH2uoEFdT9eOWrUa6gIgc5xDpgyyw9xGpwDVfUrL DPmCL6oTjMS6FhLOiz1MT0Czts5+vMR4EbPqgbBrniY8XDPvJq5AIychDQkJLxrvxmsPXpHlNM8 lKPp2qY2k+kphXfGww8YmI1yHMBs= X-Google-Smtp-Source: AGHT+IHmWSGEPggOBL/3Xh3iw2eZku+TuVgzbus7OwyOyjM5xK4QHMCfdPCm5GuO5xpIC/ZaAmWj4MnfAbNRLu4nIwg= X-Received: by 2002:a17:906:2c56:b0:a4e:8b32:c259 with SMTP id f22-20020a1709062c5600b00a4e8b32c259mr1531982ejh.46.1712232979342; Thu, 04 Apr 2024 05:16:19 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Esteban Zimanyi Date: Thu, 4 Apr 2024 14:24:12 +0200 Message-ID: Subject: Re: Updated packaging for MobilityDB 1.1.0 To: Christoph Berg Cc: Bradford Boyle , pgsql-pkg-debian@lists.postgresql.org, SCHOEMANS Maxime , =?UTF-8?B?VsOtY3RvciBEaXbDrQ==?= , Regina Obe Content-Type: multipart/alternative; boundary="00000000000081b1580615444eb7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000081b1580615444eb7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear all (cc MobilityDB Team and Regina Obe) The MobilityDB 1.1 version was released two weeks ago. See: https://github.com/MobilityDB/MobilityDB/releases/tag/v1.1.0 However, as this release was not running on ARM, we were waiting to produce a v1.1.1 release with small bug fixes that allows MobilityDB to run on the ARM architecture. This is now almost complete and we are thus planning to release and announce MobilityDB 1.1.1 either at the end of this week or next week. Regards Esteban ------------------------------------------------------------ Prof. Esteban Zimanyi Department of Computer & Decision Engineering (CoDE) CP 165/15 Universite Libre de Bruxelles Avenue F. D. Roosevelt 50 B-1050 Brussels, Belgium fax: + 32.2.650.47.13 tel: + 32.2.650.31.85 e-mail: esteban.zimanyi@ulb.be Internet: http://cs.ulb.ac.be/members/esteban/ ------------------------------------------------------------ On Thu, Apr 4, 2024 at 2:12=E2=80=AFPM Christoph Berg wro= te: > Hi Bradford, > > where are we with MobilityDB? Are the remaining test failures a > problem in the source, or just artifacts of the way we try to run the > tests? > > Christoph > > > --00000000000081b1580615444eb7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all (cc MobilityDB Team and Regina Obe)

The MobilityDB 1.1 version was released two weeks ago.
See: https:= //github.com/MobilityDB/MobilityDB/releases/tag/v1.1.0

However, = as this release was not running on ARM, we were waiting to produce a v1.1.1= release with small bug fixes that allows MobilityDB to run on the ARM arch= itecture. This is now almost complete and we are thus planning to release a= nd announce MobilityDB 1.1.1 either at the end of this week or next week.
Regards

Esteban
---------------------------------------------------------= ---
Prof. Esteban Zimanyi
Department of Computer & Decision Engin= eering=C2=A0 (CoDE) CP 165/15=C2=A0 =C2=A0
Universite Libre de Bruxelle= s=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
Avenue F. D. Roosevelt 50=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
B-1050 Brussels, B= elgium=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0
fax= : + 32.2.650.47.13
tel: + 32.2.650.31.85
e-mail: esteban.zimanyi@ulb.be
Inter= net:=C2=A0http://cs.ulb.ac.be/members/esteban/
-----------------------------= -------------------------------


On T= hu, Apr 4, 2024 at 2:12=E2=80=AFPM Christoph Berg <myon@debian.org> wrote:
Hi Bradford,

where are we with MobilityDB? Are the remaining test failures a
problem in the source, or just artifacts of the way we try to run the
tests?

Christoph


--00000000000081b1580615444eb7--