On 10/11/25 11:37 AM, Paul Gevers wrote:
On 10/11/25 10:08, Bas Couwenberg wrote:
Testing migration of postgis is blocked by the autopkgtest failure of
mobilitydb.
That autopkgtest is buggy and had changes in 1.3.0~alpha-2 & 1.3.0~alpha-3 to
address them.
This means that britney needs to schedule the autopkgtest for mobilitydb with
mobilitydb from unstable, but also postgresql-common & postgis from unstable
for the postgresql-18 changes.
If I read the log from mobilitydb correctly, this is a test only problem, right?
Yes, the Build-Depends are in order.
Otherwise a versioned Breaks somewhere (I didn't check where yet) should help
britney2 to do the right thing.
We really shouldn't need to upload a new package revision when the tooling can
find newer versions of the affected packages in unstable.
As long a britney is not smart enough to test packages involved in a transition
together, people with access to its debci credentials will need to schedule
those combinations for it.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
