Bug#1145527: rsyslog: FTBFS on reproduce.d.n

[Jochen Sprickerhof]

* Michael Biebl <bi...@debian.org> [2026-08-25 23:04]:

Am 25.08.26 um 20:12 schrieb Michael Biebl:

Am 25.08.26 um 20:09 schrieb Michael Biebl:

Hi Jochen,

is there a way to find this build failure from the tracker.d.o dashboard?

It is listed right there:

Reproducibility regression on amd64: rsyslog, rsyslog-clickhouse, rsyslog-czmq, rsyslog-docker, rsyslog-elasticsearch, rsyslog-gnutls, rsyslog-gssapi, rsyslog-hiredis, rsyslog-http, rsyslog-kafka, rsyslog-kubernetes, rsyslog-mongodb, rsyslog-mysql, rsyslog-openssl, rsyslog-pgsql, rsyslog-relp, rsyslog-snmp

Can the package be given back / retried?

It was retried multiple times already and failed every time.

Problem is, the test suite passes really reliably here on my local system, i.e. I can reproduce the problem or create an environment where

I can *not* reproduce the problem...

I tried building it using

debrebuild --builder=sbuild+unshare and
debrebuild --builder=sbuild

TMPDIR=/var/tmp sbuild --chroot-mode=unshare --dist=unstable rsyslog

But only on some computers..

For completeness, reproduce.debian.net uses --builder=sbuild+unshare but that is actually unrelated as I can get the same result with:

You said you ran your own tests, what were your findings so far?

Cheers Jochen

I only found that it happens when compiling on ext4 (via setting TMPDIR as above). Do you need anything specific from a failed run to debug this?

signature.asc
Description: PGP signature