Your message dated Fri, 1 Jan 2021 15:26:06 +0000
with message-id <20210101152606.gb...@tack.einval.com>
and subject line Re: Bug#976482: strace: FTBFS: ../io_uring.c:30:1: error: 
static assertion failed: "struct io_cqring_offsets.resv is missing, please 
update the decoder"
has caused the Debian Bug report #976482,
regarding strace: FTBFS: ../io_uring.c:30:1: error: static assertion failed: 
"struct io_cqring_offsets.resv is missing, please update the decoder"
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.)


-- 
976482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strace
Version: 5.5-3
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H   -I./linux/aarch64 -I../linux/aarch64 -I./linux 
> -I../linux -I. -I..     -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wempty-body 
> -Wformat-security -Wignored-qualifiers -Wimplicit-fallthrough=5 -Winit-self 
> -Wlogical-op -Wmissing-parameter-type -Wnested-externs 
> -Wold-style-declaration -Wold-style-definition -Woverride-init -Wsign-compare 
> -Wtype-limits -Wwrite-strings   -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -O2 -MT 
> strace-io_uring.o -MD -MP -MF .deps/strace-io_uring.Tpo -c -o 
> strace-io_uring.o `test -f 'io_uring.c' || echo '../'`io_uring.c
> In file included from ../static_assert.h:11,
>                  from ../xlat/uring_setup_features.h:4,
>                  from ../io_uring.c:14:
> ../io_uring.c:30:1: error: static assertion failed: "struct 
> io_cqring_offsets.resv is missing, please update the decoder"
>    30 | static_assert(0, "struct io_cqring_offsets.resv is missing"
>       | ^~~~~~~~~~~~~
> make[3]: *** [Makefile:5165: strace-io_uring.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/strace_5.5-3_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 me
so that we can identify if something relevant changed in the meantime.

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.

--- End Message ---
--- Begin Message ---
Control: fixed -1 5.10-1

Just uploaded version 5.10-1 with some tests disabled. Looks good on
amd64, arm64 and s390x so I think this is fixed.

Cheers,

Steve

On Sat, Dec 05, 2020 at 09:11:23PM +0100, Lucas Nussbaum wrote:
>On 05/12/20 at 13:31 +0100, Lucas Nussbaum wrote:
>> Source: strace
>> Version: 5.5-3
>> Severity: serious
>> Justification: FTBFS on arm64
>> Tags: bullseye sid ftbfs
>> Usertags: ftbfs-20201205 ftbfs-bullseye
>> 
>> Hi,
>> 
>> During a rebuild of all packages in sid, your package failed to build
>> on arm64 (I don't know if it also fails on amd64).
>
>It also fails on amd64. You can find a build log in
>http://qa-logs.debian.net/2020/12/05/amd64/
>
>Lucas
>
-- 
Steve McIntyre, Cambridge, UK.                                st...@einval.com
Google-bait:       https://www.debian.org/CD/free-linux-cd
  Debian does NOT ship free CDs. Please do NOT contact the mailing
  lists asking us to send them to you.

--- End Message ---

Reply via email to