Source: citus
Version: 5.1.1-1
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-07-07 18:43:03.000000000 +0000
> +++ debian/control.dtqrPH     2016-10-01 00:47:49.424000000 +0000
> @@ -8,9 +8,9 @@
>  Homepage: https://github.com/citusdata/citus
>  XS-Testsuite: autopkgtest
>  
> -Package: postgresql-9.5-citus
> +Package: postgresql-9.6-citus
>  Architecture: any
> -Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-9.5
> +Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-9.6
>  Description: sharding and distributed joins for PostgreSQL
>   Citus is a distributed database implemented as a PostgreSQL extension. It
>   provides functions to easily split a PostgreSQL table into shards to be
> 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/citus_5.1.1-1_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.

Reply via email to