Source: atlas-ecmwf
Version: 0.36.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cd /<<PKGBUILDDIR>>/debian/build/atlas_io/tests && /usr/bin/c++  
> -I/<<PKGBUILDDIR>>/atlas_io/src -I/<<PKGBUILDDIR>>/debian/build/atlas_io/src 
> -I/usr/include/x86_64-linux-gnu/eckit -g -O2 
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -O3 -DNDEBUG -std=gnu++17 -fPIE -MD -MT 
> atlas_io/tests/CMakeFiles/atlas_io_test_record.dir/test_io_record.cc.o -MF 
> CMakeFiles/atlas_io_test_record.dir/test_io_record.cc.o.d -o 
> CMakeFiles/atlas_io_test_record.dir/test_io_record.cc.o -c 
> /<<PKGBUILDDIR>>/atlas_io/tests/test_io_record.cc
> /<<PKGBUILDDIR>>/src/atlas/library/Library.cc:63:10: fatal error: 
> ectrans/transi.h: No such file or directory
>    63 | #include "ectrans/transi.h"
>       |          ^~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[3]: *** [src/atlas/CMakeFiles/atlas_ecmwf.dir/build.make:93: 
> src/atlas/CMakeFiles/atlas_ecmwf.dir/library/Library.cc.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/atlas-ecmwf_0.36.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;[email protected]
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&[email protected]&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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 mark 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