Noted. Thanks for the followup. *Jeremy Finzel*
*Database Administrator Tech Lead* *M* 630-777-4520 On Sun, Dec 8, 2019 at 6:37 AM Christoph Berg <m...@debian.org> wrote: > Re: Sebastien Bacher 2019-12-06 < > 18cb3ad6-93b1-7044-5edd-023c5ca0a...@debian.org> > > Package: pglogical-ticker > > Version: 1.4.0-1 > > > > The tests are failing since postgresql-common got updated to 208 > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__ci.debian.net_packages_p_pglogical-2Dticker_unstable_amd64_&d=DwIBAg&c=lEzKI_JJakPtcnbAQ6Q5xQ&r=DqdWOTTF4YJBUfeNWvxJoag6GeBeW-A_9xfI4JO4szc&m=Ej7hrqzcFenwocJrfQXfEHdsw741gvKUxIY9xqdJsdo&s=LaUlTIr6CkErrisbvLFHYoQCM2gRcLv5wL1Dj0IFHu4&e= > > > > pg_buildext: error: /usr/lib/postgresql/11/bin/pg_config does not exist > > > It looks like the package also needs to be updated for postgresql 12? > > The test is failing because the Debian PostgreSQL environment has > already moved to 12, but this package is still only available for 11, > so some parts required to test it have already moved to 12. > > I'm working on moving pg_config into the dependency cone of > the postgresql-XX server package so it would be present whenever > something depending on postgresql-XX would be tested. > > The basic issue is that pglogical isn't available for PG12, though. > > Christoph >
