Your message dated Mon, 21 Nov 2022 15:08:21 +0000
with message-id <c500aae7ef76cfbd0f92139822426...@tecnico.ulisboa.pt>
and subject line Fixed in 0.20.0-2
has caused the Debian Bug report #1013827,
regarding FTBFS, post-build tests fail on architectures armel and armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1013827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: varnish-modules
Version: 0.20.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the
past)
Dear Maintainer,
This version fails to build on Ubuntu Kinetic with varnish 7.1.0-6 only on
armhf. The builds for all other architectures succeed.
Build log:
https://launchpadlibrarian.net/609387386/buildlog_ubuntu-kinetic-armhf.varnish-modules_0.20.0-1_BUILDING.txt.gz
Failing tests:
FAIL: tests/bodyaccess/test01.vtc
FAIL: tests/bodyaccess/test03.vtc
FAIL: tests/bodyaccess/test05.vtc
FAIL: tests/header/append.vtc
FAIL: tests/header/copy.vtc
FAIL: tests/header/get.vtc
FAIL: tests/header/import.vtc
FAIL: tests/header/keep-others.vtc
FAIL: tests/header/remove.vtc
FAIL: tests/header/some-data.vtc
FAIL: tests/header/regsub.vtc
FAIL: tests/saintmode/test04.vtc
FAIL: tests/saintmode/test05.vtc
FAIL: tests/str/test01.vtc
FAIL: tests/str/test02.vtc
FAIL: tests/str/test03.vtc
FAIL: tests/str/test04.vtc
FAIL: tests/str/test05.vtc
FAIL: tests/str/test06.vtc
FAIL: tests/str/test08.vtc
FAIL: tests/tcp/01-dumpinfo.vtc
FAIL: tests/tcp/02-congestion.vtc
FAIL: tests/tcp/03-read-tcpinfo.vtc
FAIL: tests/tcp/04-pacing.vtc
FAIL: tests/var/test01.vtc
FAIL: tests/var/test02.vtc
FAIL: tests/var/test03.vtc
FAIL: tests/var/test04.vtc
FAIL: tests/var/test05.vtc
FAIL: tests/var/test06.vtc
FAIL: tests/vsthrottle/test01.vtc
FAIL: tests/vsthrottle/test02.vtc
FAIL: tests/vsthrottle/test04.vtc
FAIL: tests/xkey/test01.vtc
FAIL: tests/xkey/test02.vtc
FAIL: tests/xkey/test03.vtc
FAIL: tests/xkey/test04.vtc
FAIL: tests/xkey/test05.vtc
FAIL: tests/xkey/test06.vtc
FAIL: tests/xkey/test07.vtc
FAIL: tests/xkey/test08.vtc
FAIL: tests/xkey/test09.vtc
FAIL: tests/xkey/test10.vtc
FAIL: tests/xkey/test11.vtc
FAIL: tests/xkey/test13.vtc
--- End Message ---
--- Begin Message ---
To whom it may concern,
The maintainer provided a workaround in version 0.20.0-2, that disables
the build on architectures where
tests fail.
Kind regards,
Luís Infante da Câmara
--- End Message ---
