Bug#1104365: metview: FTBFS: MeshCache.cc:24:49: error: 'Resource' is not a member of 'eckit'

[Lucas Nussbaum]

Source: metview
Version: 5.25.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20250429 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cd /build/reproducible-path/metview-5.25.0/debian/build/mir/src/mir && /usr/bin/c++ -Dmir_EXPORTS -I/build/reproducible-path/metview-5.25.0/mir/src -I/build/reproducible-path/metview-5.25.0/debian/build/mir/src -I/usr/include/x86_64-linux-gnu/eckit/linalg -I/usr/include/x86_64-linux-gnu/eckit -I/usr/include/x86_64-linux-gnu/eckit/geometry -I/usr/include/x86_64-linux-gnu/eckit/option -g -O2 -ffile-prefix-map=/build/reproducible-path/metview-5.25.0=. -fstack-protector-strong -fstack-clash-protection -fcf-protection -std=gnu++17 -I /usr/include/eigen3 -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -Wall -Wextra -Wno-unused-parameter -Wno-unused-variable -Wno-sign-compare -O3 -DNDEBUG -std=gnu++17 -fPIC -MD -MT mir/src/mir/CMakeFiles/mir.dir/caching/matrix/SharedMemoryLoader.cc.o -MF CMakeFiles/mir.dir/caching/matrix/SharedMemoryLoader.cc.o.d -o CMakeFiles/mir.dir/caching/matrix/SharedMemoryLoader.cc.o -c /build/reproducible-path/metview-5.25.0/mir/src/mir/caching/matrix/SharedMemoryLoader.cc
> /build/reproducible-path/metview-5.25.0/mir/src/mir/caching/MeshCache.cc: In constructor 'mir::caching::MeshCache::MeshCache()':
> /build/reproducible-path/metview-5.25.0/mir/src/mir/caching/MeshCache.cc:24:49: error: 'Resource' is not a member of 'eckit'
>    24 |                                          eckit::Resource<bool>("$MIR_THROW_ON_CACHE_MISS;mirThrowOnCacheMiss", false),
>       |                                                 ^~~~~~~~
> /build/reproducible-path/metview-5.25.0/mir/src/mir/caching/MeshCache.cc:24:58: error: expected primary-expression before 'bool'
>    24 |                                          eckit::Resource<bool>("$MIR_THROW_ON_CACHE_MISS;mirThrowOnCacheMiss", false),
>       |                                                          ^~~~
> /build/reproducible-path/metview-5.25.0/mir/src/mir/caching/MeshCache.cc:25:49: error: 'Resource' is not a member of 'eckit'
>    25 |                                          eckit::Resource<size_t>("$MIR_MESH_CACHE_SIZE", 0)) {}
>       |                                                 ^~~~~~~~
> /build/reproducible-path/metview-5.25.0/mir/src/mir/caching/MeshCache.cc:25:64: error: expected primary-expression before '>' token
>    25 |                                          eckit::Resource<size_t>("$MIR_MESH_CACHE_SIZE", 0)) {}
>       |                                                                ^
> /build/reproducible-path/metview-5.25.0/mir/src/mir/caching/MeshCache.cc:25:66: warning: left operand of comma operator has no effect [-Wunused-value]
>    25 |                                          eckit::Resource<size_t>("$MIR_MESH_CACHE_SIZE", 0)) {}
>       |                                                                  ^~~~~~~~~~~~~~~~~~~~~~
> make[3]: *** [mir/src/mir/CMakeFiles/mir.dir/build.make:992: mir/src/mir/CMakeFiles/mir.dir/caching/MeshCache.cc.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2025/04/29/metview_5.25.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250429;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250429&fusertaguser=lucas@debian.org&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.