Source: pg-rage-terminator Version: 0.1.4-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160930 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > pg_buildext checkcontrol > --- debian/control 2016-01-22 12:40:59.000000000 +0000 > +++ debian/control.WO1M11 2016-10-01 00:38:29.316000000 +0000 > @@ -10,12 +10,12 @@ > Vcs-Git: https://github.com/disco-stu/pg-rage-terminator-pkg.git > Vcs-Browser: https://github.com/disco-stu/pg-rage-terminator-pkg > > -Package: pg-rage-terminator-9.5 > +Package: pg-rage-terminator-9.6 > Architecture: any > Depends: > ${shlibs:Depends}, > ${misc:Depends}, > - postgresql-9.5 > + postgresql-9.6 > Description: PostgreSQL background worker that kill random sessions. > pg-rage-terminator is a custom background worker which is able to kill > random > PostgreSQL backends. > 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. > /usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target > 'debian/control' failed > make: *** [debian/control] Error 1 If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 The full build log is available from: http://aws-logs.debian.net/2016/09/30/pg-rage-terminator_0.1.4-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
