On 10/11/25 11:54 AM, Paul Gevers wrote:
On 10/11/25 11:37, Paul Gevers wrote:
If I read the log from mobilitydb correctly, this is a test only problem,
right? Otherwise a versioned Breaks somewhere (I didn't check where yet) should
help britney2 to do the right thing.
Seems like there's something isn't working as expected in the postgresql-common
"transition"? I guess that "PostgreSQLÂ 17" shouldn't be there in the
mobilitydb logs [1] given that source only ships a postgresql-18-mobilitydb binary.
Some annotated recent jobs:
* https://ci.debian.net/packages/m/mobilitydb/testing/amd64/65059749/
1.3.0~alpha-2
src:mobilitydb from unstable
src:h3-pg from unstable
src:postgis from unstable
Pulls in both postgresql-17-postgis-3 & postgresql-18-postgis-3 because it
hardcoded the postgresql-17 version debian/tests/control.
This was fixed in 1.3.0~alpha-3.
* https://ci.debian.net/packages/m/mobilitydb/testing/amd64/65079693/
1.2.0-2
src:postgresql-common from unstable
Fails because it needs the postgresql-common-dev test dependency from
1.3.0~alpha-2.
* https://ci.debian.net/packages/m/mobilitydb/testing/amd64/65081605/
1.3.0~alpha-3
src:mobilitydb from unstable
src:h3-pg from unstable
src:postgis from unstable
Fails because it tries to use packages built for postgresql-18 with
postgresql-17 because it didn't get postgresql-common from unstable too.
* https://ci.debian.net/packages/m/mobilitydb/testing/amd64/65089581/
src:mobilitydb from unstable
src:postgresql-common from unstable
src:postgis from unstable
I scheduled this with the required combination of packages from unstable,
but the job installed none of them from unstable.
This is the combination that britney needs to test for a successful
autopkgtest with postgresql-18.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
