public inbox for [email protected]  

help / color / mirror / Atom feed

From: Christoph Berg <[email protected]>
To: Bradford Boyle <[email protected]>
Cc: [email protected]
Subject: Re: Updated packaging for MobilityDB 1.1.0~beta1
Date: Sun, 5 Nov 2023 15:04:08 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAOMoQbTOZ0ZLUnsu2Z8NJkS3JrjKDpbYgfWWn0KD_jGBJHnj6g@mail.gmail.com>
References: <CAOMoQbTOZ0ZLUnsu2Z8NJkS3JrjKDpbYgfWWn0KD_jGBJHnj6g@mail.gmail.com>

Re: Bradford Boyle
> Hello,
> 
> I have just pushed an update to the Debian packaging of MobilityDB to
> salsa.debian.org [1] that addresses the feedback [2] from the first
> attempt at packaging this extension.

Thanks!

> * I've updated d/control.in so that PGVERSION is no longer used --
>   declaring a dependency on postgresql-postgis is sufficient

In postgresql-XX-mobility, we need the XX version of
postgresql-XX-postgis-3, not just any version, so this change isn't
correct.

The usage of "postgresql-postgis" in the Build-Depends is also fishy,
but the "update debian/control from control.in" machinery doesn't
support using PGVERSION in the Source section yet. I tried
implementing that the other week, but didn't get to finish it yet,
hopefully that will happen over the next days.

I haven't investigated the cause yet, but the pgdg build is failing:

https://pgdgbuild.dus.dg-i.net/job/mobilitydb-binaries/2/architecture=amd64,distribution=sid/console

14:56:48 dh_missing: warning: usr/lib/postgresql/16/lib/libMobilityDB-1.1.so exists in debian/tmp but is not installed to anywhere
14:56:48 dh_missing: warning: usr/share/postgresql/16/extension/mobilitydb--1.1.0.sql exists in debian/tmp but is not installed to anywhere
14:56:48 dh_missing: warning: usr/share/postgresql/16/extension/mobilitydb.control exists in debian/tmp but is not installed to anywhere
14:56:48 dh_missing: error: missing files, aborting

Christoph

view thread (18+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Updated packaging for MobilityDB 1.1.0~beta1
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox