On 10/11/25 3:08 PM, Paul Gevers wrote:
On 10/11/25 12:52, Christoph Berg wrote:
I would propose that we just wait a day until all the extensions that
are currently 1-of-2 days old propagate to forky and then look at the
remaining packages to see if additional fixes are required. At that
point, forcing postgresql-common would likely fix it (or trying
postgresql-common+mobilitydb+postgis together).
Agreed.
As expected that didn't change anything wrt. postgis, that's still blocked by
the mobilitydb autopkgtest failure.
britney once again scheduled a job with src:mobilitydb & src:postgis from
unstable but not postgresql-common which failed:
https://ci.debian.net/packages/m/mobilitydb/testing/amd64/65105666/
Please schedule the job with src:mobilitydb, src:postgresql-common, and src:postgis
from unstable which should let the jobs succeed and let postgis & mobilitydb
migrate to testing.
To unblock testing migration of postgresql-common python-django-postgres-extra
needs to be hinted out of testing or its autopkgtest ignored (#1117647).
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
