Source: librem5-flash-image
Version: 0.0.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

librem5-flash-image recently started to FTBFS in sid:

debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure
debian/rules override_dh_auto_build
make[1]: Entering directory '/build/librem5-flash-image-0.0.4'
PREFIX=/usr dh_auto_build
make -j3 "INSTALL=install --strip-program=true"
make[2]: Entering directory '/build/librem5-flash-image-0.0.4'
make -C scripts/
make[3]: Entering directory '/build/librem5-flash-image-0.0.4/scripts'
flake8 librem5-devkit-flash-image
python3 -m doctest librem5_flash_image.py
make[3]: Leaving directory '/build/librem5-flash-image-0.0.4/scripts'
make -C data/
make[3]: Entering directory '/build/librem5-flash-image-0.0.4/data' appstreamcli validate sm.puri.librem5-flash-image.metainfo.xml
W: sm.puri.librem5-flash-image:~: url-homepage-missing
I: sm.puri.librem5-flash-image:~: content-rating-missing
I: sm.puri.librem5-flash-image:~: developer-info-missing

? Validation failed: warnings: 1, infos: 2, pedantic: 1
make[3]: *** [Makefile:7: check] Error 3
make[3]: Leaving directory '/build/librem5-flash-image-0.0.4/data'
make[2]: *** [Makefile:9: check] Error 2
make[2]: Leaving directory '/build/librem5-flash-image-0.0.4'
dh_auto_build: error: make -j3 "INSTALL=install --strip-program=true" returned exit code 2
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
make[1]: Leaving directory '/build/librem5-flash-image-0.0.4'
make: *** [debian/rules:6: binary] Error 2


Andreas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Wed, 17 Apr 2024 06:49:45 +0000
with message-id <E1rwz73-00CuEI-4P@fasolo.debian.org>
and subject line Bug#1067089: fixed in librem5-flash-image 0.0.4-2
has caused the Debian Bug report #1067089,
regarding librem5-flash-image: FTBFS: Validation failed: warnings: 1, infos: 2, pedantic: 1
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 owner@bugs.debian.org
immediately.)


--
1067089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067089
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 18 Mar 2024 09:31:52 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-6.0 required=4.0 tests=BAYES_00,FROMDEVELOPER,
SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham
autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 23; hammy, 118; neutral, 22; spammy,
0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--H*F:U*anbe,
0.000-+--H*rp:U*anbe, 0.000-+--Hx-spam-relays-external:anbe@debian.org,
0.000-+--H*RU:anbe@debian.org
Return-path: <anbe@debian.org>
Received: from lambdaproxy.unixos.de ([87.106.170.14]:53176)
by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
(Exim 4.94.2)
(envelope-from <anbe@