On Wed, Sep 25, 2024 at 03:09:35PM +0200, Santiago Vila wrote: > Hello. > > As the subject says, many postgresql-related packages FTBFS in this way: > (I'm taking postgresql-unit as an example) > > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_clean > pg_buildext checkcontrol > --- debian/control 2024-09-15 11:58:15.000000000 +0000 > +++ debian/control.VFAeRh 2024-09-19 05:00:18.737341291 +0000 > @@ -14,7 +14,7 @@ > Vcs-Browser: https://github.com/df7cb/postgresql-unit > Homepage: https://github.com/df7cb/postgresql-unit > -Package: postgresql-17-unit > +Package: postgresql-16-unit > Architecture: any > Depends: ${misc:Depends}, ${shlibs:Depends}, ${postgresql:Depends} > Description: SI Units for PostgreSQL > Error: debian/control needs updating from debian/control.in. Run 'pg_buildext > updatecontrol'. > If you are seeing this message in a buildd log, a sourceful upload is > required. > make: *** [debian/rules:10: clean] Error 1 shuffle=2080555641 > dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2 > > > Is this really normal/expected, or is there a bug somewhere? (like, for > example, > a missing build-dependency which propagated to testing prematurely).
This is expected for PostgreSQL transitions. > I'm concerned about this because even if this is the kind of bug which > end up being fixed over time, if we were to release trixie as stable today, > we would ship many FTBFS bugs like those, so this is apparently something > that we should avoid to happen. This is tracked as an ongoing transition, which is already mostly finished in unstable: https://release.debian.org/transitions/html/postgresql-17.html E.g. for postgresql-unit in your example the renamed package for 17 has already migrated - but postgresql-common which changes the default not yet. > Thanks. cu Adrian
