Source: sqlalchemy-i18n
Version: 1.0.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>     conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
> psycopg2.OperationalError: connection to server at "localhost" (::1), port 
> 54469 failed: Connection refused
>       Is the server running on that host and accepting TCP/IP connections?
> connection to server at "localhost" (127.0.0.1), port 54469 failed: 
> Connection refused
>       Is the server running on that host and accepting TCP/IP connections?
> 
> 2021-10-23 07:44:56.935 UTC [28085] LOG:  starting PostgreSQL 14.0 (Debian 
> 14.0-1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.3.0-11) 10.3.0, 
> 64-bit
> 2021-10-23 07:44:56.935 UTC [28085] LOG:  listening on IPv4 address 
> "127.0.0.1", port 54469
> 2021-10-23 07:44:56.935 UTC [28085] LOG:  listening on Unix socket 
> "/tmp/tmpwfn7fr11/tmp/.s.PGSQL.54469"
> 2021-10-23 07:44:56.937 UTC [28086] LOG:  database system was shut down at 
> 2021-10-23 07:44:56 UTC
> 2021-10-23 07:44:56.940 UTC [28085] LOG:  database system is ready to accept 
> connections
> make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> make: *** [debian/rules:5: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/sqlalchemy-i18n_1.0.3-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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Reply via email to