Processed: chromium

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1069586 https://crbug.com/329678163
Bug #1069586 [chromium] Chromium native Wayland support broken
Set Bug forwarded-to-address to 'https://crbug.com/329678163'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1069586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069586
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): Re: Bug#1069586: Chromium native Wayland support broken

[Debian Bug Tracking System]

Processing control commands:

> tags -1 forwarded https://crbug.com/329678163
Unknown tag/s: forwarded, https://crbug.com/329678163.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky 
forky-ignore.

> severity -1 serious
Bug #1069586 [chromium] Chromium native Wayland support broken
Severity set to 'serious' from 'normal'

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

Bug#1066674: marked as done (gramophone2: FTBFS: GRAMophone.c:94:9: error: implicit declaration of function ‘usageError’; did you mean ‘strerror’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 21 Apr 2024 03:34:03 +
with message-id 
and subject line Bug#1066674: fixed in gramophone2 0.8.13a-3.3
has caused the Debian Bug report #1066674,
regarding gramophone2: FTBFS: GRAMophone.c:94:9: error: implicit declaration of 
function ‘usageError’; did you mean ‘strerror’? 
[-Werror=implicit-function-declaration]
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.)


-- 
1066674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gramophone2
Version: 0.8.13a-3.2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -fcommon -O2 -Wl,-z,relro -o 
> gramophone2 GRAMophone.c\
>   grammyVM.c init.c midicode.c\
>   midifile.c expcode.c debug.c errors.c\
>   hash.c GRAMophone.tab.c -lm
> GRAMophone.c: In function ‘main’:
> GRAMophone.c:94:9: error: implicit declaration of function ‘usageError’; did 
> you mean ‘strerror’? [-Werror=implicit-function-declaration]
>94 | usageError();
>   | ^~
>   | strerror
> GRAMophone.c:98:3: error: implicit declaration of function ‘initGRAMophone’ 
> [-Werror=implicit-function-declaration]
>98 |   initGRAMophone();
>   |   ^~
> GRAMophone.c:99:3: error: implicit declaration of function ‘yyparse’ 
> [-Werror=implicit-function-declaration]
>99 |   yyparse();
>   |   ^~~
> GRAMophone.c:102:59: error: implicit declaration of function ‘grammyvm’ 
> [-Werror=implicit-function-declaration]
>   102 |   checkOption?(printf("the composition source is ok\n")):(grammyvm());
>   |   ^~~~
> cc1: some warnings being treated as errors
> grammyVM.c: In function ‘chomsky_generator’:
> grammyVM.c:711:53: error: implicit declaration of function 
> ‘mf_write_midi_event’ [-Werror=implicit-function-declaration]
>   711 | 
> if(!mf_write_midi_event(prev_duration, note_on, 
> players[playerCount]->local_params[CHN], data, 2)) {
>   | 
> ^~~
> grammyVM.c: In function ‘lindenmayer_prod_generator’:
> grammyVM.c:1114:67: error: implicit declaration of function ‘hash’ 
> [-Werror=implicit-function-declaration]
>  1114 | 
> buffer[counter++]=hash(string_buf, 0);
>   |   ^~~~
> grammyVM.c: In function ‘myputc’:
> grammyVM.c:1477:5: warning: type of ‘c’ defaults to ‘int’ [-Wimplicit-int]
>  1477 | int myputc(c) {
>   | ^~
> grammyVM.c: In function ‘write_player_track’:
> grammyVM.c:1481:5: warning: type of ‘track’ defaults to ‘int’ [-Wimplicit-int]
>  1481 | int write_player_track(track) {
>   | ^~
> grammyVM.c:1487:21: error: implicit declaration of function 
> ‘mf_write_meta_event’ [-Werror=implicit-function-declaration]
>  1487 | if(!mf_write_meta_event(0, copyright_notice, 
> copyright, strlen(copyright))) {
>   | ^~~
> grammyVM.c:1491:17: error: implicit declaration of function ‘mf_write_tempo’ 
> [-Werror=implicit-function-declaration]
>  1491 | mf_write_tempo((long)6000/tempo);
>   | ^~
> grammyVM.c:1514:33: error: implicit declaration of function 
> ‘print_local_params’ [-Werror=implicit-function-declaration]
>  1514 | print_local_params(playerCount);  
>   //debug
>   | ^~
> grammyVM.c: In function ‘grammyvm’:
> grammyVM.c:1548:11: error: implicit declaration of function 
> ‘print_composition_info’ [-Werror=implicit-function-declaration]
>  1548 |   print_composition_info(); //debug
>   |   

Bug#1067316: gnucash-docs: FTBFS: Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so: libharfbuzz.so.0: cannot open shared object file:

[Vincent Lefevre]

[Not reassigning yet to openjdk-17-jre-headless, as the change
was done on purpose, but Cc-ing the OpenJDK Team.]

Hi,

Since no-one looked at this issue in a month and gnucash-docs
has now been removed from testing...

On 2024-03-20 22:03:18 +0100, Lucas Nussbaum wrote:
[...]
> > Exception in thread "main" java.lang.UnsatisfiedLinkError: 
> > /usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so: libharfbuzz.so.0: 
> > cannot open shared object file: No such file or directory
[...]

Indeed, on my machine

qaa:~> ldd /usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so | grep 
libharfbuzz
libharfbuzz.so.0 => /lib/x86_64-linux-gnu/libharfbuzz.so.0 
(0x7fe984534000)

where /usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so
comes from openjdk-17-jre-headless, but the build log shows
that libharfbuzz0b is not installed, while being recommended by
openjdk-17-jre-headless. However, I would say that even though
libharfbuzz.so.0 is used by a particular library, this should
be a "Depends:", not a "Recommends:". In any case, I think
that gnucash-docs is not supposed to know the libfontmanager.so
internals, i.e. this cannot be a bug in gnucash-docs.

But also

qaa:~> ldd /usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so | grep 
freetype
libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 
(0x7f835ed1d000)

while libfreetype6 is also only recommended.

openjdk-17 (17.0.10+7-3) unstable; urgency=medium
[...]
  * Make the dependencies for libfontmanager.so and libjsound.so
recommendations in jre-headless, and dependencies in jre.
[...]
 -- Matthias Klose   Mon, 11 Mar 2024 16:08:33 +0100

which was done in commit

https://salsa.debian.org/openjdk-team/openjdk/-/commit/6f0e4b17a1ff58aaf32da9be9abcf0224c481885

But why?

A warning has been added in

https://salsa.debian.org/openjdk-team/openjdk/-/commit/8010273018af3ada65de8901735ab60bb0dd5c0e

but this is the kind of things that building systems will ignore.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1069535: [debian-mysql] Bug#1069535: galera-3: FTBFS on armel: dh_auto_test: error: cd obj-arm-linux-gnueabi && make -j1 test ARGS\+=--verbose ARGS\+=-j1 ARGS=--output-on-failure returned exit cod

[Otto Kekäläinen]

Galera 25.3.37 was last release from upstream in 3.x series. I suspect
the best resolution here is to wait a bit and then just file removal
request for galera-3 in sid/trixie when we are confident there is no
MariaDB 10.1/2/3 users out there anymore.

Bug#1064293: Bug#1068938: less: diff for NMU version 590-2.1

[Milan Kupcevic]

On 4/19/24 11:31, Salvatore Bonaccorso wrote:

Control: tags 1064293 + patch
Control: tags 1064293 + pending
Control: tags 1068938 + patch
Control: tags 1068938 + pending


Dear maintainer,

I've prepared an NMU for less (versioned as 590-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

As well pushed in a separte branch on salsa, which can be merged if
accepted to unstable:

https://salsa.debian.org/debian/less/-/tree/sid-2024-security-fixes?ref_type=heads

Regards.
Salvatore



ACK.

Thank you Salvatore; much appreciated.

Milan

Bug#1067547: marked as done (FTBFS: "vsnprintf is so broken we can't compensate. Sorry.")

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 21:36:19 +
with message-id 
and subject line Bug#1067547: fixed in wmweather+ 2.19~alpha+ds-1.1
has caused the Debian Bug report #1067547,
regarding FTBFS: "vsnprintf is so broken we can't compensate. Sorry."
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.)


-- 
1067547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wmweather+
Version: 2.19~alpha+ds-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=wmweather%2B=amd64=2.19%7Ealpha%2Bds-1%2Bb1=1710656065=0

gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include
-I/usr/include -I/usr/include  -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-
protection -Wformat -Werror=format-security -fcf-protection -Wall   -c -o
vsnprintf.o vsnprintf.c
vsnprintf.c:93:3: error: #error "vsnprintf is so broken we can't compensate.
Sorry."
   93 | # error "vsnprintf is so broken we can't compensate. Sorry."
  |   ^


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: wmweather+
Source-Version: 2.19~alpha+ds-1.1
Done: Jeremy Sowden 

We believe that the bug you reported is fixed in the latest version of
wmweather+, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Sowden  (supplier of updated wmweather+ package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 18 Apr 2024 21:40:43 +0100
Source: wmweather+
Architecture: source
Version: 2.19~alpha+ds-1.1
Distribution: unstable
Urgency: medium
Maintainer: Martin Stigge 
Changed-By: Jeremy Sowden 
Closes: 1067547
Changes:
 wmweather+ (2.19~alpha+ds-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/patches: add patch to fix FTBFS (Closes: #1067547)
Checksums-Sha1:
 41d143c7f1a238afe966baf491e6105263097d9a 2066 wmweather+_2.19~alpha+ds-1.1.dsc
 edb9cad02ee311eaabc4a18a18c7995f7c882cf2 4980 
wmweather+_2.19~alpha+ds-1.1.debian.tar.xz
 355b4fe5babeb5c799ac61bedfe7821817954652 9634 
wmweather+_2.19~alpha+ds-1.1_amd64.buildinfo
Checksums-Sha256:
 697bd79eba3e0e8f36bcdf06efa20d3d3cd716da558c50d6bde40106dd268ef0 2066 
wmweather+_2.19~alpha+ds-1.1.dsc
 31a049dadc9ee1534d1304a07dc4ead16cc347154f0c93064a4d2ec041449aa2 4980 
wmweather+_2.19~alpha+ds-1.1.debian.tar.xz
 b491ced970a64ee62439780531d3cb0b1ba0eb4477583063e6b7e13aa8072d54 9634 
wmweather+_2.19~alpha+ds-1.1_amd64.buildinfo
Files:
 b9b9dfdf987a4b3e21f2951865a27f84 2066 x11 optional 
wmweather+_2.19~alpha+ds-1.1.dsc
 bfe61c4de46b443521312f1bdf0f0efd 4980 x11 optional 
wmweather+_2.19~alpha+ds-1.1.debian.tar.xz
 88681594e28470fa60cf694860096866 9634 x11 optional 
wmweather+_2.19~alpha+ds-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEbB20U2PvQDe9VtUXKYasCr3xBA0FAmYhiPsSHGF6YXplbEBk
ZWJpYW4ub3JnAAoJECmGrAq98QQNBIwP/Ao59ulsdrRwCjLUBQjg1Yc2NHrAlNMU
KvPjs9CmlRcNdhNTHWh+iiI+bM8p+Nx7GNeGFFbNflgxqL/C/FU4WOru3az+DT09
slCKvANK/66elg/xC4OUGRLU+kFppmslRPp4pyaan09r1okX60wtcli3rXvhApDE
fabDV8SrWvxX/K8nUmCz0/fPjpKL/GtdsRTFSB9OAfNfdz7xXjAnx4E28SglWyPT
YR1ZPiT8a2KZW/r0CcnpuqZK1+dO6aV5qSz0Xvn8fqw3OzhV8eOxNqbwWaCrR9qM
iQiHcXWMMnMWtY3lxToZYo57q0ddlIA/Hj7Pjj3U6IWZhEhfjiEUyvqTKw2d3kdX
3QfVda6aZhzOyNioqBYpdWCK+LPI+W1Yr07+gxm2dqL8JH/0EwIVbjdI/bsJaSIB
Vt4oT6B52eigjVVGqJVcJWyl8fij6PC+641eoTjmk8sKwieXEvY4LPSkJnYmecld
ho1YHcRSsQG5YzSFLtqSzFOPVrCnRdZvDC19KBlZohX4IGZcCsg4jB2SrzFSoJXs

Bug#1061546: marked as done (srcpd: installs file into aliased location)

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 21:35:45 +
with message-id 
and subject line Bug#1061546: fixed in srcpd 2.1.6-2
has caused the Debian Bug report #1061546,
regarding srcpd: installs file into aliased location
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.)


-- 
1061546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: srcpd
Version: 2.1.6-1
User: helm...@debian.org
Usertag: dep17m2
Severity: important

Hello,

your package srcpd started installing a file in /lib, instead of
installing it into /usr/lib. This is contrary to the currently
ongoing UsrMerge[1] effort.

Please move /lib/udev/rules.d/10-liusb.rules into /usr/lib before
srcpd reaches testing.

Thanks,
Chris
--- End Message ---
--- Begin Message ---
Source: srcpd
Source-Version: 2.1.6-2
Done: Hilmar Preusse 

We believe that the bug you reported is fixed in the latest version of
srcpd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilmar Preusse  (supplier of updated srcpd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 20 Apr 2024 23:23:42 +0200
Source: srcpd
Architecture: source
Version: 2.1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Hilmar Preusse 
Changed-By: Hilmar Preusse 
Closes: 1061546
Changes:
 srcpd (2.1.6-2) unstable; urgency=medium
 .
   * Install 10-liusb.rules into /usr/lib instead of /lib
 (Closes: #1061546)
   * Fix build failure on GNU/Hurd.
Checksums-Sha1:
 eaf55ea6cd65175cdfd87e00bef313b088555899 1960 srcpd_2.1.6-2.dsc
 124c9f29fb333c8f40421e3c54ccb12067e6508c 5164 srcpd_2.1.6-2.debian.tar.xz
 af6a651a94d2fad9ba29c34880201ea55534ac54 5930 srcpd_2.1.6-2_source.buildinfo
Checksums-Sha256:
 f8d99f578554d18c54f88c32642ee1bdc80c357fffa4e67030f11ead2dd72d87 1960 
srcpd_2.1.6-2.dsc
 aa06a33ed3480305fc7d3337375d21463c54d0f7682e922e26f26192a68b193b 5164 
srcpd_2.1.6-2.debian.tar.xz
 bfce6fae65d9bbc6887c6f4a7d3ad5ecec38089ca9866b692720d70e4a53de14 5930 
srcpd_2.1.6-2_source.buildinfo
Files:
 7a498e21397a0e7f2a558e16082d50f3 1960 electronics optional srcpd_2.1.6-2.dsc
 d90b98f817207a38e761e8e018c683c0 5164 electronics optional 
srcpd_2.1.6-2.debian.tar.xz
 670795508c2499ffe7db1e05b21bf654 5930 electronics optional 
srcpd_2.1.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmYkMoFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5
NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg
LIv/8g//eaY85C5LO10diyTxPlSrTzUAb9fNfpTtz9iRggLM8RbiH9hdVARgqZnK
eYyVf62L+rrKJha3vCfNW34gIevSaWzdXz8+Lx147ZXzsXP+PXXbZd6WQuGECkcF
4Swx4kBfHFqp8yyiCX7qKss1rQnfO4C+g+kJ2jBnSq3rT7LEL4fwiYaghbFw7I3s
zcoNVow1NAN5yRoYb2RGdtI/hTDBVbey2yWMhAatYct+qPs5f5ykLXEHzfmES5zY
njC93MZex3m7yqZ0KOl9s/q1ZYtMIbg2JOxO12xWS1V5xMFmuW8fMa/jJcFlSBtN
4J75xCkvE+UN+mJYNqwk0HFI7KaufVeRtvQPZTJQd50SUexDOkLqroF1kANlEoB8
pl2TFnKqgw/ID2rPijTp2pWEAPqXbbUSexNGdau0o7ub/VrkHJl+iXReJza7rmgA
oVti2EEI8Ecyz3cKZ9pgZ2GthKgqalWT8dpTUN98J/ybZLxcWsACI9OuZYqlwtSP
3JXufTCbexeSgCwszjYY2Vygr+oIObpVVKs7HJdBr1KezCVPjSG5zlpF2X6SL5aq
0fXtK/keYwaTE1G+nSUM3Z+a2zMY5wGBtvl6D6PhGDjKHstyMGU7O1zi8QfTgN1O
n+HY+hslsVFuWCc5y5Z0UotCFDJUfPaTElfB3Ulty/T9Zna1NCE=
=MzlE
-END PGP SIGNATURE-



pgpjskm1b_WpX.pgp
Description: PGP signature
--- End Message ---

Bug#1069398: marked as done (iraf-st4gem: FTBFS on arm64: tbtopn.c:91:(.text+0x20c): undefined reference to `isvote_')

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 21:13:01 +
with message-id 
and subject line Bug#1069398: fixed in iraf-st4gem 1.0+ds-3
has caused the Debian Bug report #1069398,
regarding iraf-st4gem: FTBFS on arm64: tbtopn.c:91:(.text+0x20c): undefined 
reference to `isvote_'
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.)


-- 
1069398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iraf-st4gem
Version: 1.0+ds-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: /<>/lib/libtbtables_p.a(tbtopn.o): in function 
> `tbtopn_':
> /<>/lib/tbtables/tbtopn.c:91:(.text+0x20c): undefined reference 
> to `isvote_'
> /usr/bin/ld: /<>/lib/tbtables/tbtopn.c:92:(.text+0x228): 
> undefined reference to `vottos_'
> /usr/bin/ld: /<>/lib/tbtables/tbtopn.c:117:(.text+0x478): 
> undefined reference to `isvote_'
> /usr/bin/ld: /<>/lib/tbtables/tbtopn.c:118:(.text+0x494): 
> undefined reference to `vottos_'
> /usr/bin/ld: /<>/lib/tbtables/tbtopn.c:126:(.text+0x510): 
> undefined reference to `isvote_'
> /usr/bin/ld: /<>/lib/tbtables/tbtopn.c:133:(.text+0x5fc): 
> undefined reference to `isvote_'
> /usr/bin/ld: /<>/lib/tbtables/tbtopn.c:134:(.text+0x618): 
> undefined reference to `vottos_'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/iraf-st4gem_1.0+ds-2_unstable-arm64.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.
--- End Message ---
--- Begin Message ---
Source: iraf-st4gem
Source-Version: 1.0+ds-3
Done: Ole Streicher 

We believe that the bug you reported is fixed in the latest version of
iraf-st4gem, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated iraf-st4gem package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 20 Apr 2024 21:47:20 +0200
Source: iraf-st4gem
Architecture: source
Version: 1.0+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 1069398
Changes:
 iraf-st4gem (1.0+ds-3) unstable; urgency=medium
 .
   * Don't build local tbtables (Closes: #1069398)
Checksums-Sha1:
 ee43b29f8aaac22445f90965618253b51a01cfad 1999 iraf-st4gem_1.0+ds-3.dsc
 9b68e4ae3faffcb6f8ead5c702a513e8b3f2a986 4196 
iraf-st4gem_1.0+ds-3.debian.tar.xz
Checksums-Sha256:
 1d2a5c35a9f4514e4a2d034de03db95c958400b07c4da69234f8e9c6279ba554 1999 
iraf-st4gem_1.0+ds-3.dsc
 f4537ad366f9ff94b16b74949df4f9bad0bbe396cabbc98594bb6c460ebc6e8e 4196 
iraf-st4gem_1.0+ds-3.debian.tar.xz
Files:
 88a5159bd66bd830aa003a052526cfd5 1999 science optional iraf-st4gem_1.0+ds-3.dsc
 74f0ca644d595115f276f898bd1a0586 4196 science optional 
iraf-st4gem_1.0+ds-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAmYkHBQACgkQmk9WvbkO
GL3sZA/+I6ckMLUjKa/gdJdpa17AcD6PJ80zcurkJNZe1ZXIAhnnyCLRkLYanWkH
S3q0T3YYulBchT6Ue7lM5i0wgl5nHJK3e8ikKcpjOBcITsOcRehW8nZsNm6Vj4l4
Fi0+gse6PNH5cHGVxQopxcyLeBZuU8/JNfCNO5Mvjx/QQIUaKlUb1NdthtCIYkuy
qZkUyAGUw9E0T/zuvKfX3GU25/cJH5idBPYkgX9pkyH28vmb5PyqBZqqqRki11V9
gZNJx

Processed: Re: Bug#1069433: gtg-trace: FTBFS on armhf: tests fail

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 openmpi
Bug #1069433 [src:gtg-trace] gtg-trace: FTBFS on armhf: tests fail
Bug reassigned from package 'src:gtg-trace' to 'openmpi'.
No longer marked as found in versions gtg-trace/0.2-3-2.
Ignoring request to alter fixed versions of bug #1069433 to the same values 
previously set
> affects -1 gtg-trace
Bug #1069433 [openmpi] gtg-trace: FTBFS on armhf: tests fail
Added indication that 1069433 affects gtg-trace

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

Bug#1069554: [Pkg-pascal-devel] Bug#1069554: winff: FTBFS on armel: build-dependency not installable: libreoffice-draw-nogui

[Paul Gevers]

Hi,

On 20-04-2024 3:22 p.m., Lucas Nussbaum wrote:

The following packages have unmet dependencies:
  sbuild-build-depends-main-dummy : Depends: libreoffice-draw-nogui but it is 
not installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.


I recall rene mentioning that parts of lo are expected to not work on 
armel due to java being broken. Probably the best way forward is to 
request binary removal on armel.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1069433: gtg-trace: FTBFS on armhf: tests fail

[Samuel Thibault]

Control: reassign -1 openmpi
Control: affects -1 gtg-trace

Hello,

Lucas Nussbaum, le sam. 20 avril 2024 14:52:03 +0200, a ecrit:
> > --
> > Sorry!  You were supposed to get help about:
> > pmix_init:startup:internal-failure
> > But I couldn't open the help file:
> > /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  
> > Sorry!
> > --
> > [ip-10-84-234-251:1132190] PMIX ERROR: NOT-FOUND in file 
> > ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c 
> > at line 237
> > running testEvent_parall 1
> > --

This happens on i386 too, but also with the following trivial testcase
on armhf and i386:

$ cat test.c
#include 
#include 
int main(int argc, char *argv[]) {
int size, rank;
MPI_Init(, );
MPI_Comm_size(MPI_COMM_WORLD, );
MPI_Comm_rank(MPI_COMM_WORLD, );
printf("%d/%d\n", rank, size);
MPI_Finalize();
return 0;
}
$ mpicc test.c -o test
$ mpirun -np 2 ./test
--
Sorry!  You were supposed to get help about:
pmix_init:startup:internal-failure
But I couldn't open the help file:
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
--
[abel:25256] PMIX ERROR: NOT-FOUND in file 
../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
line 237

Thus reassigning to openmpi. It seems that even if pmix is not built on
32bit archs any more, openmpi is still enabling pmix support, perhaps
that needs to be disabled?

Samuel

Processed: severity of 1010992 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # failed on buildds: 
> https://buildd.debian.org/status/fetch.php?pkg=sstp-client=amd64=1.0.19-1%2Bb2=1713643682=0
> severity 1010992 serious
Bug #1010992 [src:sstp-client] sstp-client FTBFS on IPV6-only buildds
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1010992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069551: numpy: FTBFS on armel: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13

[Timo Röhling]

Hi Lucas,

* Lucas Nussbaum  [2024-04-20 15:21]:

Relevant part (hopefully):


self = 

@pytest.mark.skipif(IS_WASM, reason="fp errors don't work in wasm")
@pytest.mark.skipif(arm_softfloat,
reason='platform/cpu issue with FPU (gh-413,-15562)')
def test_invalid(self):


This test is supposed to be skipped on armel, as arm_softfloat is 
initialized with


hosttype = sysconfig.get_config_var('HOST_GNU_TYPE')
arm_softfloat = False if hosttype is None else hosttype.endswith('gnueabi')

Can you help me figure out why this did not work with your rebuild? 
Judging from the configuration output,



libdir   : lib/arm-linux-gnueabi


I would have expected that arm_softfloat is True. Maybe 
sysconfig.get_config_var('HOST_GNU_TYPE') returns None?



Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Bug#1069337: marked as done (Update Depends for the time64 library renames)

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 19:53:55 +
with message-id 
and subject line Bug#1069337: fixed in thunderbird 1:115.10.1-1
has caused the Debian Bug report #1069337,
regarding Update Depends for the time64 library renames
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.)


-- 
1069337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:115.9.0-1+b1
Severity: serious

thunderbird explicitly Depends: libotr5. It should be changed to the t64 name
if it's really needed.

Note that the package is still installable because it's not built on 32-bit
time64 arches, but it still needs to be fixed so that libotr5 can be removed.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thunderbird depends on:
ii  debianutils 5.17
ii  fontconfig  2.15.0-1.1
ii  kdialog 4:22.12.3-1+b1
ii  libasound2t64 [libasound2]  1.2.11-1+b1
ii  libatk1.0-0t64 [libatk1.0-0]2.52.0-1
ii  libc6   2.37-18
ii  libcairo-gobject2   1.18.0-3+b1
ii  libcairo2   1.18.0-3+b1
ii  libdbus-1-3 1.14.10-4+b1
pn  libdbus-glib-1-2
ii  libevent-2.1-7t64 [libevent-2.1-7]  2.1.12-stable-8.1+b3
ii  libffi8 3.4.6-1
ii  libfontconfig1  2.15.0-1.1
ii  libfreetype62.13.2+dfsg-1+b4
ii  libgcc-s1   14-20240330-1
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b3
ii  libglib2.0-0t64 [libglib2.0-0]  2.78.4-6
ii  libgtk-3-0t64 [libgtk-3-0]  3.24.41-4
ii  libnspr42:4.35-1.1+b1
ii  libnss3 2:3.99-1
pn  libotr5 
ii  libpango-1.0-0  1.52.1+ds-1
pn  librnp0 
ii  libstdc++6  14-20240330-1
ii  libvpx8 1.13.1-2
ii  libx11-62:1.8.7-1
ii  libx11-xcb1 2:1.8.7-1
ii  libxcb-shm0 1.17.0-1
ii  libxcb1 1.17.0-1
ii  libxext62:1.3.4-1+b1
ii  libxrandr2  2:1.5.4-1
ii  psmisc  23.7-1
ii  x11-utils   7.7+6+b1
ii  zenity  4.0.1-1+b1
ii  zlib1g  1:1.3.dfsg-3.1

Versions of packages thunderbird recommends:
ii  hunspell-ru [hunspell-dictionary]  1:24.2.2-1

Versions of packages thunderbird suggests:
ii  apparmor  3.0.13-2
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.20.1-6+b1
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:115.10.1-1
Done: Carsten Schoenert 

We believe that the bug you reported is fixed in the latest version of
thunderbird, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 20 Apr 2024 19:35:18 +0200
Source: thunderbird
Architecture: source
Version: 1:115.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Closes: 1069337
Changes:
 thunderbird (1:115.10.1-1) unstable; urgency=medium
 .
   [ William Desportes ]

Processed: Re: dnf: dnf aborts with ImportError: cannot import name '_module' from partially initialized module 'libdnf'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 dh-python 6.20240401
Bug #1068255 [dnf] dnf: dnf aborts with ImportError: cannot import name 
'_module' from partially initialized module 'libdnf'
Bug reassigned from package 'dnf' to 'dh-python'.
No longer marked as found in versions dnf/4.14.0-4.1.
Ignoring request to alter fixed versions of bug #1068255 to the same values 
previously set
Bug #1068255 [dh-python] dnf: dnf aborts with ImportError: cannot import name 
'_module' from partially initialized module 'libdnf'
Marked as found in versions dh-python/6.20240401.
> retitle -1 dh-python: dh_python3 loses cpython module name when renaming 
> shared object
Bug #1068255 [dh-python] dnf: dnf aborts with ImportError: cannot import name 
'_module' from partially initialized module 'libdnf'
Changed Bug title to 'dh-python: dh_python3 loses cpython module name when 
renaming shared object' from 'dnf: dnf aborts with ImportError: cannot import 
name '_module' from partially initialized module 'libdnf''.

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

Bug#1068255: dnf: dnf aborts with ImportError: cannot import name '_module' from partially initialized module 'libdnf'

[Luca Boccassi]

Control: reassign -1 dh-python 6.20240401
Control: retitle -1 dh-python: dh_python3 loses cpython module name when 
renaming shared object

On Tue, 2 Apr 2024 22:47:12 +0300 Michael Ivanov 
wrote:
> Package: dnf
> Version: 4.14.0-4.1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> I have just tried to start up dnf and it aborts with a following
error:
> 
> Traceback (most recent call last):
> File "/usr/bin/dnf", line 61, in 
> from dnf.cli import main
> File "/usr/lib/python3/dist-packages/dnf/__init__.py", line 30, in

> import dnf.base
> File "/usr/lib/python3/dist-packages/dnf/base.py", line 29, in

> import libdnf.transaction
> File "/usr/lib/python3/dist-packages/libdnf/__init__.py", line 13, in
> 
> from . import module
> File "/usr/lib/python3/dist-packages/libdnf/module.py", line 10, in

> from . import _module
> ImportError: cannot import name '_module' from partially initialized
module
> 'libdnf' (most likely due to a circular import)
(/usr/lib/python3/dist-
> packages/libdnf/__init__.py)
> 
> Python version is 3.11.8 (python package version is 3.11.8-3+b2)

This is caused by dh_python3. A regression was introduced at some
point, and when renaming the cpython shared object dh_python3 loses the
name, and _module.so is renamed to _.cpython-311-x86_64-linux-gnu.so
when libdnf is built, breaking the import at runtime:

I: dh_python3 fs:418: renaming _module.so to _.cpython-311-x86_64-linux-gnu.so

https://buildd.debian.org/status/fetch.php?pkg=libdnf=amd64=0.73.1-1=1713175615=0

Renaming the shared library manually to the expected filename makes dnf
work again.

Reassigning to dh-python. A binnmu of libdnf (and any other affected
package) will be needed once resolved and uploaded.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Processed: Bug#1063501: building less from source fails the island test

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1063501 wishlist
Bug #1063501 [src:less] building less from source fails the island test
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1063501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056901: marked as done (network-manager-fortisslvpn: 1.4.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 18:22:54 +
with message-id 
and subject line Bug#1056901: fixed in network-manager-fortisslvpn 1.4.0-1.1
has caused the Debian Bug report #1056901,
regarding network-manager-fortisslvpn: 1.4.0-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 ow...@bugs.debian.org
immediately.)


-- 
1056901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: network-manager-fortisslvpn
Version: 1.4.0-1
Severity: important
Tags: upstream patch

Dear Maintainer,

I'm preparing to upload ppp-2.5.0 to unstable, and
network-manager-fortisslvpn fails to build with the updated pppd plugin
API in ppp-2.5.0. I see there is a patch[1] in the GNOME GitLab instance
which may resolve this issue.

Please could you upload a fixed version to unstable soon?

I'll upgrade the bug to RC when I upload ppp-2.5.0 to unstable.

Many thanks,
Chris

1. 
https://gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn/-/commit/084ef529c5fb816927ca54866f66b340265aa9f6
--- End Message ---
--- Begin Message ---
Source: network-manager-fortisslvpn
Source-Version: 1.4.0-1.1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
network-manager-fortisslvpn, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated 
network-manager-fortisslvpn package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 20 Apr 2024 17:44:35 +
Source: network-manager-fortisslvpn
Architecture: source
Version: 1.4.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Lubomir Rintel 
Changed-By: Bastian Germann 
Closes: 1056901
Changes:
 network-manager-fortisslvpn (1.4.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Build with ppp 2.5.0 (Closes: #1056901)
Checksums-Sha1:
 50b18fb9ca75262b732879011ec6014fe97071ad 2235 
network-manager-fortisslvpn_1.4.0-1.1.dsc
 d5ef873a23dcc075cea6674f605784f05074d77b 7180 
network-manager-fortisslvpn_1.4.0-1.1.debian.tar.xz
 42cdd35eb7a8ec6cb2a7381f9db6588cf904c80f 15991 
network-manager-fortisslvpn_1.4.0-1.1_source.buildinfo
Checksums-Sha256:
 b06e5491ae9293896e10a2d2f38642018b8ee9bfad75354525e3cb2234e1d47c 2235 
network-manager-fortisslvpn_1.4.0-1.1.dsc
 6e261eb0a43f1e10c5fc3763dc3ab0aebb20b853b9fd688661d87c064e3d27f8 7180 
network-manager-fortisslvpn_1.4.0-1.1.debian.tar.xz
 206ea2324c799b82de44210d4a46b2d0d6f654dd8d664d3148ce090c7512790a 15991 
network-manager-fortisslvpn_1.4.0-1.1_source.buildinfo
Files:
 60853382809a193ad335af1b4cf95208 2235 net optional 
network-manager-fortisslvpn_1.4.0-1.1.dsc
 ff6c65f503138345942af45dc9d1e660 7180 net optional 
network-manager-fortisslvpn_1.4.0-1.1.debian.tar.xz
 24af56793737a11dbcd112bdb2573e26 15991 net optional 
network-manager-fortisslvpn_1.4.0-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYkAGEQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFNYJDADn8y/SHyGUyGloTwtsxZ4apf/btrxOmGS8
mwVecCi72CzORjzlANucnBl/QbMTILl+RHx3in829tDYkN2OAeCZ0+6d+imW/Ytl
jnFcgODV2/cwEjTOiGePAnUdfPW+gYOllOG0M0NrlPN1xvWcatFrPTWmazlq2R3H
P61Ub+DA76I9NKlv3INpJe1iBErOIhqmY+mzC/zJKMBbokjF59Q86lhFSQYXgFnn
IjL0VKsqCi4P+G0OJ3EJNv3F/F7712sfSCTPsOPlEsjfIU+2a5uUxhSgrs3Auyjl
SO/LXC/3veOFBX8cFZLPNcwpoiUb+8kMZK0jEwlsShBUCAc3BpZrUciTzdSgNx8v
Vac/qegU7Lrl5RicvrYaj7BgxFQWFqq8pLUW0OVkUaAkr1QcNPk2ceIrWpw5QBR7
QUZP3wL4W3mEuR/Q2yTyEa1rFqcl3hDG+9K5uD1brlHVuXm8u2PrfdyKiNts3faw
qZiB4nO+tXVENeTEmoQm909O6VtZQ50=
=HpEk
-END PGP SIGNATURE-



pgp0lB6RtQxj6.pgp
Description: PGP signature
--- End Message ---

Bug#1069247: libconfig-model-dpkg-perl: test failures

[Niko Tyni]

On Sat, Apr 20, 2024 at 11:09:17AM +0200, Dominique Dumont wrote:
> On Thursday, 18 April 2024 19:21:55 CEST you wrote:
> > Source: libconfig-model-dpkg-perl
> > Version: 3.004
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source
> 
> This really looks like a bug with prove:
> 
> $ perl t/reorder.t 
> ok 1 -  test re-ordered list
> 1..1

> I can't see what's wrong with the output of reorder test...

Looks like something is injecting apt progress messages to stdout with
CR characters hiding it on the terminal but obviously not from `prove`.

$ perl t/reorder.t |od -c
000  \r   R   e   a   d   i   n   g   p   a   c   k   a   g   e
020   l   i   s   t   s   .   .   .   0   %  \r  \r   R   e
040   a   d   i   n   g   p   a   c   k   a   g   e   l   i
060   s   t   s   .   .   .   1   0   0   %  \r
100
120  \r  \r   B   u   i   l
140   d   i   n   g   d   e   p   e   n   d   e   n   c   y
160   t   r   e   e   .   .   .   0   %  \r  \r   B   u   i   l
200   d   i   n   g   d   e   p   e   n   d   e   n   c   y
220   t   r   e   e   .   .   .   0   %  \r  \r   B   u   i   l
240   d   i   n   g   d   e   p   e   n   d   e   n   c   y
260   t   r   e   e   .   .   .   5   0   %  \r  \r   B   u   i
300   l   d   i   n   g   d   e   p   e   n   d   e   n   c   y
320   t   r   e   e   .   .   .   5   0   %  \r
340
360  \r  \r   R
400   e   a   d   i   n   g   s   t   a   t   e   i   n   f
420   o   r   m   a   t   i   o   n   .   .   .   0   %  \r  \r
440   R   e   a   d   i   n   g   s   t   a   t   e   i   n
460   f   o   r   m   a   t   i   o   n   .   .   .   0   %  \r
500
*
540  \r   o   k   1   -   t   e   s   t   r   e
560   -   o   r   d   e   r   e   d   l   i   s   t  \n   1   .
600   .   1  \n
603

HTH,
-- 
Niko

Bug#1056901: network-manager-fortisslvpn: 1.4.0-1

[Bastian Germann]

Done. I haev uploaded a NMU with the referenced patch.

Bug#1069480: bochs: FTBFS on armhf: build-dependency not installable: gcc-i686-linux-gnu

[Lucas Nussbaum]

On 20/04/24 at 19:11 +0200, Stephen Kitt wrote:
> gcc-i686-linux-gnu is in Build-Depends-Indep, it’s only used to build Arch:
> all packages. Is there a requirement that these build on armhf? Given that
> armhf doesn’t have gcc-i686-linux-gnu, I’m not sure how I would go about
> fixing this, short of asking for the cross-compiler to be added to armhf
> (which doesn’t seem all that useful).

No, indeed. That could be closed, or downgraded to wishlist + wontfix as
"arch:all packages can only be built on amd64 due to missing
build-depends(-Indep) on other architectures". (I'd prefer a downgrade,
because if that bug had existed, I would have seen it and would not have
filed the bug)

Lucas

Bug#1069480: bochs: FTBFS on armhf: build-dependency not installable: gcc-i686-linux-gnu

[Stephen Kitt]

Hi Lucas,

On Sat, 20 Apr 2024 14:46:39 +0200, Lucas Nussbaum  wrote:

> Source: bochs
> Version: 2.8+dfsg-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on armhf.
> 
> 
> Relevant part (hopefully):
> > +--+
> > | Install package build dependencies
> >  |
> > +--+
> > 
> > 
> > Setup apt archive
> > -
> > 
> > Merged Build-Depends: bison, debhelper-compat (= 13), flex, libaa1-dev,
> > libasound2-dev, libgtk-3-dev, libice-dev, libltdl-dev, libncurses-dev,
> > libreadline-dev, libsdl2-dev, libsm-dev, libtool, libwxgtk3.2-dev,
> > libx11-dev, libxpm-dev, libz-dev, build-essential, fakeroot,
> > acpica-tools, bcc, bin86, docbook-dsssl, gcc-i686-linux-gnu Filtered
> > Build-Depends: bison, debhelper-compat (= 13), flex, libaa1-dev,
> > libasound2-dev, libgtk-3-dev, libice-dev, libltdl-dev, libncurses-dev,
> > libreadline-dev, libsdl2-dev, libsm-dev, libtool, libwxgtk3.2-dev,
> > libx11-dev, libxpm-dev, libz-dev, build-essential, fakeroot,
> > acpica-tools, bcc, bin86, docbook-dsssl, gcc-i686-linux-gnu dpkg-deb:
> > building package 'sbuild-build-depends-main-dummy' in
> > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. Ign:1
> > copy:/<>/apt_archive ./ InRelease Get:2
> > copy:/<>/apt_archive ./ Release [609 B] Ign:3
> > copy:/<>/apt_archive ./ Release.gpg Get:4
> > copy:/<>/apt_archive ./ Sources [915 B] Get:5
> > copy:/<>/apt_archive ./ Packages [908 B] Fetched 2432 B in
> > 0s (0 B/s) Reading package lists... Reading package lists...
> > 
> > Install main build dependencies (apt-based resolver)
> > 
> > 
> > Installing build dependencies
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> > 
> > The following packages have unmet dependencies:
> >  sbuild-build-depends-main-dummy : Depends: gcc-i686-linux-gnu but it is
> > not installable E: Unable to correct problems, you have held broken
> > packages. apt-get failed.  

gcc-i686-linux-gnu is in Build-Depends-Indep, it’s only used to build Arch:
all packages. Is there a requirement that these build on armhf? Given that
armhf doesn’t have gcc-i686-linux-gnu, I’m not sure how I would go about
fixing this, short of asking for the cross-compiler to be added to armhf
(which doesn’t seem all that useful).

Regards,

Stephen


pgpytC3Od5ois.pgp
Description: OpenPGP digital signature

Bug#1069307: FTBFS: configure: error: must specify --with-locking-method option

[Andreas Metzler]

Control: tags -1 patch

On 2024-04-19 Andrey Rakhmatullin  wrote:
> Source: courier
> Version: 1.0.16-3.2
> Severity: serious
> Tags: ftbfs

> https://buildd.debian.org/status/fetch.php?pkg=courier=armel=1.0.16-3.2%2Bb4=1712019536=0

> checking for locking method... configure: error: must specify --with-locking-
> method option
> configure: error: ./configure failed for libs/liblock
[...]

Multiple autoconf tests are thrown by
-Wno-error=implicit-function-declaration.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Description: Fixx FTBFS due to implicit declarations in autoconf tests.
Author: Andreas Metzler 
Bug-Debian: https://bugs.debian.org/1069307
Origin: vendor
Last-Update: 2024-04-20

--- a/libs/ldapaddressbook/configure.ac
+++ b/libs/ldapaddressbook/configure.ac
@@ -52,10 +52,11 @@ then
 	AC_TRY_LINK([
 #include 
 #if HAVE_LBER_H
 #include 
 #endif
+#define LDAP_DEPRECATED 1
 #include 
 ],
 [
 	LDAP *p=NULL;
 
--- a/libs/liblock/locktest.c
+++ b/libs/liblock/locktest.c
@@ -15,10 +15,13 @@
 #endif
 #include	
 #include	
 #include	
 #include	
+#include	
+#include	
+
 
 int main()
 {
 #define FILENAME	"courier-imap.locktest.XX"
 int	fd[2];
--- a/libs/tcpd/configure.ac
+++ b/libs/tcpd/configure.ac
@@ -221,10 +221,11 @@ AC_TRY_RUN(
 
 changequote(<<,>>)
 
 #include	
 #include	
+#include	
 
 int main(int argc, char **argv)
 {
 int	pipefd[2];
 char	c;
--- a/libs/waitlib/confwait.c
+++ b/libs/waitlib/confwait.c
@@ -22,10 +22,12 @@
 #include	
 
 #define	INCLUDED_FROM_CONFIGURE
 #include	"waitlib.c"
 
+#include	
+
 #define	NUMPROCS	10
 
 static int numterminated=0;
 
 

Processed: Re: Bug#1069307: FTBFS: configure: error: must specify --with-locking-method option

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1069307 [src:courier] FTBFS: configure: error: must specify 
--with-locking-method option
Added tag(s) patch.

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

Processed (with 1 error): Re: dolfin: NMU diff for 64-bit time_t transition

[Debian Bug Tracking System]

Processing control commands:

> severity 1062405 testing
Severity level `testing' is not known.
Recognized are: critical, grave, serious, important, normal, minor, wishlist, 
fixed.

> tags 1062405 moreinfo
Bug #1062405 [src:dolfin] dolfin: NMU diff for 64-bit time_t transition
Added tag(s) moreinfo.

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

Bug#1062405: dolfin: NMU diff for 64-bit time_t transition

[Drew Parsons]

Source: dolfin
Followup-For: Bug #1062405
Control: severity 1062405 testing
Control: tags 1062405 moreinfo

This time_t patch was never applied.  Is it not needed after all? 
Can we close this bug now?

Processed: Re: Bug#1069370: shasta: FTBFS: dpkg-shlibdeps: error: cannot continue due to the error above

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # also happens in amd64
> retitle 1069370 shasta: FTBFS: dpkg-shlibdeps: error: cannot continue due to 
> the error above
Bug #1069370 [src:shasta] shasta: FTBFS on arm64: dpkg-shlibdeps: error: cannot 
continue due to the error above
Changed Bug title to 'shasta: FTBFS: dpkg-shlibdeps: error: cannot continue due 
to the error above' from 'shasta: FTBFS on arm64: dpkg-shlibdeps: error: cannot 
continue due to the error above'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1069370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1056901: network-manager-fortisslvpn: 1.4.0-1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1056901 [src:network-manager-fortisslvpn] network-manager-fortisslvpn: 
1.4.0-1
Severity set to 'serious' from 'important'
> tags -1 ftbfs
Bug #1056901 [src:network-manager-fortisslvpn] network-manager-fortisslvpn: 
1.4.0-1
Added tag(s) ftbfs.

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

Processed: Re: Bug#1056898: pptpd: Build failures with ppp-2.5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1056898 [src:pptpd] pptpd: Build failures with ppp-2.5.0
Severity set to 'serious' from 'important'
> tags -1 ftbfs
Bug #1056898 [src:pptpd] pptpd: Build failures with ppp-2.5.0
Added tag(s) ftbfs.

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

Bug#1064293: less: CVE-2022-48624

[P. J. McDermott]

On 2024-04-20 at 16:19, Christoph Anton Mitterer wrote:
> On Sat, 2024-04-20 at 07:54 -0400, P. J. McDermott wrote:
> > Then the salvage procedure can play out for the full 28+ days
> > specified
> > by developers-reference (21 days to allow the maintainer to object
> > followed by a DELAYED/7 adoption upload).  I've already soft-proposed
> > to
> > salvage in bug #1069280 yesterday.  And as mentioned there I'm not
> > yet a
> > DD or DM, so I'd need to find a sponsor (and access to
> > debian/less.git).  
> 
> In the light of the recent XZ backdoor, wouldn't it generally be more
> desirable to get more co-maintainers, rather than replacing an existing
> one?

Sure, that's exactly the plan.  I don't intend to remove or prevent
anyone from co-maintaining src:less.  Note that my proposal to adopt,
co-maintain, or salvage (bug #1069280) said that I would keep the
current maintainer in Uploaders or Maintainer unless he requests
otherwise.  My intent is not to force out the existing maintainer,
but to help where he seems to have been too busy to properly maintain
src:less for at least two years.  (No shame in being busy, but it looks
like the package could use some help keeping up with new upstream
releases, security issues like these, etc.)

And the repository is already in the "debian" Salsa group (formerly
"collab-maint" on Alioth), where any DD can commit to it.  Also, if I
adopt or salvage src:less, I plan to allow low-threshold NMU[1].  Other
than that, I don't know of an appropriate team for it.

[1]: https://wiki.debian.org/LowThresholdNmu
-- 
Patrick "P. J." McDermott:  http://www.pehjota.net/
Lead Developer, ProteanOS:  http://www.proteanos.com/
Founder and CEO, Libiquity: http://www.libiquity.com/

Bug#1069446: marked as done (osmo-iuh: FTBFS on armhf: unsatisfiable build-dependencies: libosmo-netif-dev (>= 1.2.0), libosmo-sigtran-dev (>= 1.6.0))

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 15:51:41 +
with message-id 
and subject line Bug#1069446: fixed in osmo-iuh 1.3.0+dfsg1-7
has caused the Debian Bug report #1069446,
regarding osmo-iuh: FTBFS on armhf: unsatisfiable build-dependencies: 
libosmo-netif-dev (>= 1.2.0), libosmo-sigtran-dev (>= 1.6.0)
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.)


-- 
1069446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osmo-iuh
Version: 1.3.0+dfsg1-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), 
> pkg-config, autoconf, automake, libtool, osmo-libasn1c-dev (>= 0.9.30), 
> libsctp-dev, libosmocore-dev (>= 1.7.0), libosmo-netif-dev (>= 1.2.0), 
> libosmo-sigtran-dev (>= 1.6.0), python3, build-essential, fakeroot
> Filtered Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), 
> pkg-config, autoconf, automake, libtool, osmo-libasn1c-dev (>= 0.9.30), 
> libsctp-dev, libosmocore-dev (>= 1.7.0), libosmo-netif-dev (>= 1.2.0), 
> libosmo-sigtran-dev (>= 1.6.0), python3, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [823 B]
> Get:5 copy:/<>/apt_archive ./ Packages [855 B]
> Fetched 2287 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libosmo-netif-dev (>= 1.2.0) but 
> it is not installable
>Depends: libosmo-sigtran-dev (>= 1.6.0) 
> but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/osmo-iuh_1.3.0+dfsg1-6_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.
--- End Message ---
--- Begin Message ---
Source: osmo-iuh
Source-Version: 1.3.0+dfsg1-7
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
osmo-iuh, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribu

Bug#1069247: libconfig-model-dpkg-perl: test failures

[gregor herrmann]

On Sat, 20 Apr 2024 11:09:17 +0200, Dominique Dumont wrote:

> This really looks like a bug with prove:
> 
> $ perl t/reorder.t 
> ok 1 -  test re-ordered list
> 1..1
> $ prove -l -v -p t/reorder.t 
> t/reorder.t .. 
> ok 1 -  test re-ordered list
> 1..1
> Failed 1/1 subtests 
> 
> Test Summary Report
> ---
> t/reorder.t (Wstat: 0 Tests: 0 Failed: 0)
>   Parse errors: Bad plan.  You planned 1 tests but ran 0.
> Files=1, Tests=0,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.92 cusr  0.07 
> csys =  1.01 CPU)
> Result: FAIL

Good idea to run this directly with `perl'.
 
> I can't see what's wrong with the output of reorder test...

Ack, and same for the failing test in dh-make-perl (#1069246).

But I don't see that `prove' has changed recently … So maybe this is
in fact even somewhere "deeper"?
 
> I'll try to dig this later on..

Thanks!


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1066574: marked as done (xbill: FTBFS: Game.c:258:21: error: implicit declaration of function ‘strncasecmp’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 14:55:25 +
with message-id 
and subject line Bug#1066574: fixed in xbill 2.1-10
has caused the Debian Bug report #1066574,
regarding xbill: FTBFS: Game.c:258:21: error: implicit declaration of function 
‘strncasecmp’ [-Werror=implicit-function-declaration]
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.)


-- 
1066574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xbill
Version: 2.1-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I. -c OS.c -o OS.o
> Game.c: In function ‘parse_args’:
> Game.c:258:21: error: implicit declaration of function ‘strncasecmp’ 
> [-Werror=implicit-function-declaration]
>   258 | if (strncasecmp(argv[i], "-l", 2) == 0) {
>   | ^~~
> Game.c:258:48: warning: ‘strncasecmp’ argument 3 type is ‘int’ where ‘long 
> unsigned int’ is expected in a call to built-in function declared without 
> prototype [-Wbuiltin-declaration-mismatch]
>   258 | if (strncasecmp(argv[i], "-l", 2) == 0) {
>   |^
> : note: built-in ‘strncasecmp’ declared here
> x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I. -DSCOREFILE=\"/var/games/xbill.scores\" 
> -c Scorelist.c -o Scorelist.o
> x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I. -c Spark.c -o Spark.o
> Scorelist.c: In function ‘Scorelist_read’:
> Scorelist.c:26:25: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>26 | fscanf(scorefile, "%20s%d%d\n", 
> scores[i].name,
>   | 
> ^~~
>27 |[i].level, [i].score);
>   |~~~
> x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I. -c UI.c -o UI.o
> x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I. -c util.c -o util.o
> x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I.  -c x11-athena.c -o x11-athena.o
> x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I.  -DIMAGES=\"/usr/share/xbill\" -c x11.c 
> -o x11.o
> Scorelist.c: In function ‘Scorelist_update’:
> Scorelist.c:88:25: warning: ‘%-*s’ directive writing 20 bytes into a region 
> of size between 1 and 500 [-Wformat-overflow=]
>88 | sprintf(str, "%s%-*s %6s %7s\n", str, NAMELEN,
>   | ^~~~
>89 | "Name", "Level", "Score");
>   | ~~   
> In file included from /usr/include/stdio.h:906,
>  from Scorelist.c:1:
> In function ‘sprintf’,
> inlined from ‘Scorelist_update’ at Scorelist.c:88:2:
> 

Processed: bug 1069390 is forwarded to https://gitlab.com/gnutls/guile/-/issues/25

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1069390 https://gitlab.com/gnutls/guile/-/issues/25
Bug #1069390 [src:guile-gnutls] guile-gnutls: FTBFS on arm64: dh_auto_test: 
error: cd b4deb && make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 
returned exit code 2
Set Bug forwarded-to-address to 'https://gitlab.com/gnutls/guile/-/issues/25'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1069390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1069259: haskell-termonad: FTBFS on armhf: callStackDoc, called at compiler/GHC/Utils/Panic.hs:182:37 in ghc:GHC.Utils.Panic

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1069259 [src:haskell-termonad] haskell-termonad: FTBFS on armhf: 
callStackDoc, called at compiler/GHC/Utils/Panic.hs:182:37 in 
ghc:GHC.Utils.Panic
Severity set to 'important' from 'serious'

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

Bug#1069259: haskell-termonad: FTBFS on armhf: callStackDoc, called at compiler/GHC/Utils/Panic.hs:182:37 in ghc:GHC.Utils.Panic

[Ilias Tsitsimpis]

Control: severity -1 important

On Thu, Apr 18, 2024 at 10:48PM, Sebastian Ramacher wrote:
> https://buildd.debian.org/status/fetch.php?pkg=haskell-termonad=armhf=4.5.0.0-1%2Bb4=1713092640=0

This appears to be a GHC bug. I have requested the removal of
haskell-termonad from armhf, for now.

-- 
Ilias

Bug#1069550: marked as done (kvirc: FTBFS on armel: build-dependency not installable: qtwebengine5-dev)

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 19:42:19 +0500
with message-id 
and subject line Re: Bug#1069550: kvirc: FTBFS on armel: build-dependency not 
installable: qtwebengine5-dev
has caused the Debian Bug report #1069550,
regarding kvirc: FTBFS on armel: build-dependency not installable: 
qtwebengine5-dev
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.)


-- 
1069550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kvirc
Version: 4:5.2.2+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cmake (>= 3.16.0), debhelper-compat (= 13), 
> dh-sequence-kf5, extra-cmake-modules, libenchant-2-dev, libkf5coreaddons-dev, 
> libkf5i18n-dev, libkf5kio-dev, libkf5notifications-dev, libkf5parts-dev, 
> libkf5service-dev, libkf5windowsystem-dev, libkf5xmlgui-dev, libperl-dev, 
> libphonon4qt5-dev, libqt5svg5-dev, libqt5x11extras5-dev, libssl-dev, 
> libx11-dev, libxrender-dev, libxss-dev, pkgconf, python3-dev, qtbase5-dev, 
> qtmultimedia5-dev, qtwebengine5-dev, zlib1g-dev, build-essential, fakeroot, 
> doxygen, graphviz
> Filtered Build-Depends: cmake (>= 3.16.0), debhelper-compat (= 13), 
> dh-sequence-kf5, extra-cmake-modules, libenchant-2-dev, libkf5coreaddons-dev, 
> libkf5i18n-dev, libkf5kio-dev, libkf5notifications-dev, libkf5parts-dev, 
> libkf5service-dev, libkf5windowsystem-dev, libkf5xmlgui-dev, libperl-dev, 
> libphonon4qt5-dev, libqt5svg5-dev, libqt5x11extras5-dev, libssl-dev, 
> libx11-dev, libxrender-dev, libxss-dev, pkgconf, python3-dev, qtbase5-dev, 
> qtmultimedia5-dev, qtwebengine5-dev, zlib1g-dev, build-essential, fakeroot, 
> doxygen, graphviz
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [ B]
> Get:5 copy:/<>/apt_archive ./ Packages [1106 B]
> Fetched 2832 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: qtwebengine5-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/kvirc_5.2.2+dfsg-2_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.
--- End Message ---
--- Begin Message ---
On Sat, Apr 20, 2024 at 03:23:37PM +0200, Lucas Nussbaum wrote:
> > The following packages have unmet dependencies:
> >

Bug#1069368: Updating golang-github-golang-protobuf-1-5 to fix FTBFS

[Shengjing Zhu]

On Sat, Apr 20, 2024 at 10:28 PM Mathias Gibbens  wrote:
>
> Hi Anthony,
>
>   A few weeks ago you uploaded a new version of golang-google-protobuf
> to unstable which caused a FTBFS in golang-github-golang-protobuf-1-5
> v1.5.3 [1,2,3]. This has been blocking the transition of various golang
> packages from unstable to testing.
>
>   I've verified that v1.5.4 of golang-github-golang-protobuf-1-5 builds
> fine on my amd64 system. `build-rdeps golang-github-golang-protobuf-1-
> 5-dev` identifies 219 rdeps in main, so I haven't kicked off a `ratt`
> run testing for any build regressions with the newer version yet.
>

This is a known regression in 1.5.3, see
https://github.com/golang/protobuf/issues/1596#issuecomment-1981208282


-- 
Shengjing Zhu

Bug#1069368: Updating golang-github-golang-protobuf-1-5 to fix FTBFS

[Mathias Gibbens]

Hi Anthony,

  A few weeks ago you uploaded a new version of golang-google-protobuf
to unstable which caused a FTBFS in golang-github-golang-protobuf-1-5
v1.5.3 [1,2,3]. This has been blocking the transition of various golang
packages from unstable to testing.

  I've verified that v1.5.4 of golang-github-golang-protobuf-1-5 builds
fine on my amd64 system. `build-rdeps golang-github-golang-protobuf-1-
5-dev` identifies 219 rdeps in main, so I haven't kicked off a `ratt`
run testing for any build regressions with the newer version yet.

  Are you waiting on something specific before updating golang-github-
golang-protobuf-1-5?

Thanks,
Mathias

[1] -- https://qa.debian.org/excuses.php?package=golang-google-protobuf
[2] -- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068136
[3] -- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069368


signature.asc
Description: This is a digitally signed message part

Bug#1067547: wmweather+: diff for NMU version 2.19~alpha+ds-1.1

[Jeremy Sowden]

[Cc'ing t...@debian.org as I probably should have done with the nmudiff.
Apologies]

On 2024-04-18, at 21:37:40 +0100, Jeremy Sowden wrote:
> Control: tags 1067547 + patch
> Control: tags 1067547 + pending
> 
> 
> Dear maintainer,
> 
> I've prepared an NMU for wmweather+ (versioned as 2.19~alpha+ds-1.1) and
> am going to upload it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

I've forked the Salsa repo and pushed the changes to my fork:

  https://salsa.debian.org/azazel/wmweather-plus

I note that 2.17-2 and 2.18-1 were not committed to master, and
2.19~alpha+ds-1 wasn't in the repo at all.  I merged the older releases
to master and then used gbp-import-dsc to import 2.19~alpha+ds-1.  Does
this look all right?  May I push?

J.

> diff -Nru wmweather+-2.19~alpha+ds/debian/changelog 
> wmweather+-2.19~alpha+ds/debian/changelog
> --- wmweather+-2.19~alpha+ds/debian/changelog 2022-09-06 22:02:18.0 
> +0100
> +++ wmweather+-2.19~alpha+ds/debian/changelog 2024-04-18 21:14:57.0 
> +0100
> @@ -1,3 +1,10 @@
> +wmweather+ (2.19~alpha+ds-1.1) UNRELEASED; urgency=medium

I fixed this before uploading.

> +
> +  * Non-maintainer upload.
> +  * d/patches: add patch to fix FTBFS (Closes: #1067547)
> +
> + -- Jeremy Sowden   Thu, 18 Apr 2024 21:14:57 +0100
> +
>  wmweather+ (2.19~alpha+ds-1) unstable; urgency=medium
>  
>* Bump standards version to 4.6.1.
> diff -Nru wmweather+-2.19~alpha+ds/debian/patches/series 
> wmweather+-2.19~alpha+ds/debian/patches/series
> --- wmweather+-2.19~alpha+ds/debian/patches/series1970-01-01 
> 01:00:00.0 +0100
> +++ wmweather+-2.19~alpha+ds/debian/patches/series2024-04-18 
> 21:14:57.0 +0100
> @@ -0,0 +1 @@
> +update-snprintf-and-vsnprintf-checks.patch
> diff -Nru 
> wmweather+-2.19~alpha+ds/debian/patches/update-snprintf-and-vsnprintf-checks.patch
>  
> wmweather+-2.19~alpha+ds/debian/patches/update-snprintf-and-vsnprintf-checks.patch
> --- 
> wmweather+-2.19~alpha+ds/debian/patches/update-snprintf-and-vsnprintf-checks.patch
> 1970-01-01 01:00:00.0 +0100
> +++ 
> wmweather+-2.19~alpha+ds/debian/patches/update-snprintf-and-vsnprintf-checks.patch
> 2024-04-18 21:14:57.0 +0100
> @@ -0,0 +1,80 @@
> +Description: update snprintf and vsnprintf checks for
> + -Werror=implicit-function-declaration
> + .
> + This is the upstream fix.
> +Author: Brad Jorsch 
> +Last-Update: 2024-03-23
> +Forwarded: not-needed
> +Applied-upstream: commit:393394818cf4aa9b34071297a6947409cb19d74b
> +Bug-Debian: https://bugs.debian.org/1067547
> +
> +---
> + m4/snprintf.m4  | 6 +++---
> + m4/vsnprintf.m4 | 6 +++---
> + 2 files changed, 6 insertions(+), 6 deletions(-)
> +
> +diff --git a/m4/snprintf.m4 b/m4/snprintf.m4
> +index 03567bc5931e..1131e93ce206 100644
> +--- a/m4/snprintf.m4
>  b/m4/snprintf.m4
> +@@ -24,7 +24,7 @@ int snprintf(char *str, size_t size, const char *format, 
> ...);
> + #endif
> + ]],
> + [[char foo[]="ABC"; snprintf(foo, 2, "%d", 12);
> +-exit((foo[0]=='1' && foo[1]=='\0' && foo[2]=='C')?0:1);]])],
> ++return ((foo[0]=='1' && foo[1]=='\0' && foo[2]=='C')?0:1);]])],
> + [x_cv_func_snprintf_size=yes],
> + [x_cv_func_snprintf_size=no],
> + [x_cv_func_snprintf_size=no])])
> +@@ -52,7 +52,7 @@ AC_CACHE_CHECK([if snprintf return value is sane], 
> x_cv_func_snprintf_retval,
> + int snprintf(char *str, size_t size, const char *format, ...);
> + #endif
> + ]],
> +-[[char foo[10]; exit((snprintf(foo, 1, "%d", 9876)==4)?0:1);]])],
> ++[[char foo[10]; return ((snprintf(foo, 1, "%d", 9876)==4)?0:1);]])],
> + [x_cv_func_snprintf_retval=yes],
> + [x_cv_func_snprintf_retval=no],
> + [x_cv_func_snprintf_retval=no])])
> +@@ -79,7 +79,7 @@ AC_CACHE_CHECK([if snprintf(NULL, 0, ...) works], 
> x_cv_func_snprintf_null_ok,
> + int snprintf(char *str, size_t size, const char *format, ...);
> + #endif
> + ]],
> +-[int r=snprintf(NULL, 0, "%d", 100); exit((r==3 || r==-1)?0:1);])],
> ++[int r=snprintf(NULL, 0, "%d", 100); return ((r==3 || r==-1)?0:1);])],
> + [x_cv_func_snprintf_null_ok=yes],
> + [x_cv_func_snprintf_null_ok=no],
> + [x_cv_func_snprintf_null_ok=no])])
> +diff --git a/m4/vsnprintf.m4 b/m4/vsnprintf.m4
> +index a5de274cfc00..b580f46d2fcc 100644
> +--- a/m4/vsnprintf.m4
>  b/m4/vsnprintf.m4
> +@@ -37,7 +37,7 @@ int doit(char *str, size_t size, const char *format, ...){
> + }
> + ]],
> + [[char foo[]="ABC"; doit(foo, 2, "%d", 12);
> +-exit((foo[0]=='1' && foo[1]=='\0' && foo[2]=='C')?0:1);]])],
> ++return ((foo[0]=='1' && foo[1]=='\0' && foo[2]=='C')?0:1);]])],
> + [x_cv_func_vsnprintf_size=yes],
> + [x_cv_func_vsnprintf_size=no],
> + [x_cv_func_vsnprintf_size=no])])
> +@@ -74,7 +74,7 @@ int doit(char *str, size_t size, const char *format, ...){
> + return r;
> + }
> + ]],
> +-[[char foo[10]; exit((doit(foo, 1, "%d", 9876)==4)?0:1);]])],
> ++[[char foo[10]; return ((doit(foo, 1, "%d", 9876)==4)?0:1);]])],
> + [x_cv_func_vsnprintf_retval=yes],
> + [x_cv_func_vsnprintf_retval=no],
> + 

Bug#1064293: less: CVE-2022-48624

[Christoph Anton Mitterer]

On Sat, 2024-04-20 at 07:54 -0400, P. J. McDermott wrote:
> Then the salvage procedure can play out for the full 28+ days
> specified
> by developers-reference (21 days to allow the maintainer to object
> followed by a DELAYED/7 adoption upload).  I've already soft-proposed
> to
> salvage in bug #1069280 yesterday.  And as mentioned there I'm not
> yet a
> DD or DM, so I'd need to find a sponsor (and access to
> debian/less.git).

In the light of the recent XZ backdoor, wouldn't it generally be more
desirable to get more co-maintainers, rather than replacing an existing
one?


Cheers,
Chris.

Bug#1067560: marked as done (FTBFS on 32-bit time64 architectures: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’})

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 13:49:50 +
with message-id 
and subject line Bug#1067560: fixed in deepin-log-viewer 5.9.7+ds1-3
has caused the Debian Bug report #1067560,
regarding FTBFS on 32-bit time64 architectures: cannot convert ‘long int*’ to 
‘const time_t*’ {aka ‘const long long int*’}
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.)


-- 
1067560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deepin-log-viewer
Version: 5.9.7+ds1-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=deepin-log-
viewer=armel=5.9.7%2Bds1-2%2Bb2=1711175532=0

/<>/application/wtmpparse.cpp: In function ‘char*
show_end_time(long int)’:
/<>/application/wtmpparse.cpp:183:19: error: cannot convert ‘long
int*’ to ‘const time_t*’ {aka ‘const long long int*’}
  183 | t = localtime();
  |   ^~~~
  |   |
  |   long int*
In file included from /usr/include/features.h:490,
 from /usr/include/fcntl.h:25,
 from /<>/application/wtmpparse.h:25,
 from /<>/application/wtmpparse.cpp:22:
/usr/include/time.h:141:19: note:   initializing argument 1 of ‘tm*
localtime(const time_t*)’
  141 | extern struct tm *__REDIRECT_NTH (localtime, (const time_t *__timer),
  |   ^~


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: deepin-log-viewer
Source-Version: 5.9.7+ds1-3
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
deepin-log-viewer, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated deepin-log-viewer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 20 Apr 2024 09:34:08 -0400
Source: deepin-log-viewer
Architecture: source
Version: 5.9.7+ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Deepin Packaging Team 

Changed-By: Boyuan Yang 
Closes: 1067560
Changes:
 deepin-log-viewer (5.9.7+ds1-3) unstable; urgency=medium
 .
   * Team upload.
   * debian/patches/0003-fix-32-64-time_t.patch: Cherry-pick upstream
 patch to fix build with 64-bit time_t build. (Closes: #1067560)
Checksums-Sha1:
 2189afef5191abe4846a94cadabbf59e5aa8aae1 2423 deepin-log-viewer_5.9.7+ds1-3.dsc
 fc8d0cc5319e3d957d919ef4609ce1ed61180683 9069704 
deepin-log-viewer_5.9.7+ds1.orig.tar.xz
 a9a038adee61cbf4d58a599caa3c5ab13823886e 6048 
deepin-log-viewer_5.9.7+ds1-3.debian.tar.xz
 a0b9c48583357198da97075883656746ff8533e3 15550 
deepin-log-viewer_5.9.7+ds1-3_amd64.buildinfo
Checksums-Sha256:
 8fdf7cdc6284a1f2e32306fbbc5f82ac4dc7f0df050f92ec9f188c99d887bbb6 2423 
deepin-log-viewer_5.9.7+ds1-3.dsc
 b5d6546bf21988c1ae478266b3061350eba033223fadc10b5e1e4bc47a35c199 9069704 
deepin-log-viewer_5.9.7+ds1.orig.tar.xz
 a7685402683e742cfb590cbdf53b3016a18892951d27443a508e7366804436f8 6048 
deepin-log-viewer_5.9.7+ds1-3.debian.tar.xz
 67fc5b66222ee058a8e7860b760709eaa82fb538aa635921bdfccee000bce139 15550 
deepin-log-viewer_5.9.7+ds1-3_amd64.buildinfo
Files:
 6fdc4712339227ed39be2f98adaa1f19 2423 misc optional 
deepin-log-viewer_5.9.7+ds1-3.dsc
 409237bfbd335a8344f0f04a7db7498e 9069704 misc optional 
deepin-log-viewer_5.9.7+ds1.orig.tar.xz
 d3a8fdeee592736587117ce8d131c1db 6048 misc optional 
deepin-log-viewer_5.9.7+ds1-3.debian.tar.xz
 678492b1900ca61465cb6b85285ad227 15550 misc optional 

Bug#1069367: qemu: FTBFS on arm64: build-dependency not installable: gcc-powerpc64-linux-gnu

[Lucas Nussbaum]

On 20/04/24 at 15:39 +0300, Michael Tokarev wrote:
> 20.04.2024 15:33, Lucas Nussbaum wrote:
> [..]
> > This is part of a mass rebuild, first building on arm64 and then on
> > armhf and armel. So I'm not suggesting anything. :-)
> 
> Aha.
> 
> > Is this failing because the build is trying to build arch:all packages,
> > that can only be built on amd64? If so, the bug severity could be
> > lowered, clearly.
> 
> Well.  Yes, this is exactly the case.  qemu uses quite a few cross-compilers 
> to
> build various firmware components.  This is arch-all package qemu-system-data.
> Most of these cross-compilers are available on x86 _only_, including the
> mentioned gcc-powerpc64-linux-gnu.
> 
> I especially made these deps to be in Build-Depends-Indep only, - to be able
> to (re)build qemu on non-x86 by using `apt --arch-only`.
> 
> I can't say this is a bug to begin with, - wrt lowering its severity.  If it
> is a bug, it's a bug in gcc, not qemu (since it is gcc which does not provide
> these cross-compilers on all architectures).  Or in the build environment.

Sure. The only reason for leaving a bug behind is that, if there had
been a "FTBFS everywhere except amd64 when building arch-indep
packages", I would have caught this and not filed this bug. wishlist +
wontfix would be OK.

Lucas

Bug#1066224:

[Geert Stappers]

Tags: +acknowledge

On Fri, Apr 19, 2024 at 12:02:13PM +0200, Miriam Espana Acebal wrote:
> Hi,
> 
> In ubuntu we applied the upstream's fix at
> https://github.com/radvd-project/radvd/pull/196. I adapted it to a pair of
> patches that I attach here for fixing this FTBFS.
> 
> I am sending this for your consideration, and I hope it helps.

We will find out this weekend:-)


 
> --- a/gram.y
> +++ b/gram.y
> @@ -20,6 +20,10 @@
>  
>  #define YYERROR_VERBOSE 1
>  
> +int yylex (void);
> +void yyset_in (FILE * _in_str);
> +int yylex_destroy (void);
> +
>  #if 0 /* no longer necessary? */
>  #ifndef HAVE_IN6_ADDR_S6_ADDR
>  # ifdef __FreeBSD__

> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -66,9 +66,6 @@
>  scanner.c: gram.h
>  gram.h: gram.c
>  
> -libradvd_parser_a_CFLAGS = \
> - -Wno-implicit-function-declaration
> -
>  libradvd_parser_a_SOURCES = \
>   gram.h \
>   gram.y \



Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#1069556: rovclock: FTBFS on armel: rovclock.c:27:10: fatal error: sys/io.h: No such file or directory

[Lucas Nussbaum]

Source: rovclock
Version: 0.6e-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -o rovclock 
> rovclock.c
> rovclock.c:27:10: fatal error: sys/io.h: No such file or directory
>27 | #include 
>   |  ^~
> compilation terminated.
> make[1]: *** [Makefile:16: rovclock] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/rovclock_0.6e-7_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069557: libkdumpfile: FTBFS on armel: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: libkdumpfile
Version: 0.5.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>/src/kdumpfile'
> PASS: test-clone-attr
> PASS: test-blob
> PASS: test-cache
> FAIL: test-fcache
> ==
>libkdumpfile 0.5.4: src/kdumpfile/test-suite.log
> ==
> 
> # TOTAL: 4
> # PASS:  3
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test-fcache
> =
> 
> length at 0:0: 4096 != 16384
> length at 1:0: 4096 != 16384
> length at 0:1: 4095 != 16383
> length at 1:1: 4095 != 16383
> FAIL test-fcache (exit status: 1)
> 
> 
> Testsuite summary for libkdumpfile 0.5.4
> 
> # TOTAL: 4
> # PASS:  3
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See src/kdumpfile/test-suite.log
> Please report to p...@tesarici.cz
> 
> make[5]: *** [Makefile:933: test-suite.log] Error 1
> make[5]: Leaving directory '/<>/src/kdumpfile'
> make[4]: *** [Makefile:1041: check-TESTS] Error 2
> make[4]: Leaving directory '/<>/src/kdumpfile'
> make[3]: *** [Makefile:1135: check-am] Error 2
> make[3]: Leaving directory '/<>/src/kdumpfile'
> make[2]: *** [Makefile:420: check-recursive] Error 1
> make[2]: Leaving directory '/<>/src'
> make[1]: *** [Makefile:531: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libkdumpfile_0.5.4-1_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069553: xsd: FTBFS on armel: dh_auto_test: error: make -j4 test returned exit code 2

[Lucas Nussbaum]

Source: xsd
Version: 4.0.0-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> arm-linux-gnueabi-g++ 
> -I/<>/xsd/tests/cxx/parser/validation/built-in/binary 
> -I/<>/xsd/tests/cxx/parser/validation/built-in/binary 
> -I/<>/xsd/libxsd  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -std=gnu++11  -o 
> /<>/xsd/tests/cxx/parser/validation/built-in/binary/driver.o -c 
> /<>/xsd/tests/cxx/parser/validation/built-in/binary/driver.cxx
> arm-linux-gnueabi-g++ 
> -I/<>/xsd/tests/cxx/parser/validation/built-in/boolean 
> -I/<>/xsd/tests/cxx/parser/validation/built-in/boolean 
> -I/<>/xsd/libxsd  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -std=gnu++11  -o 
> /<>/xsd/tests/cxx/parser/validation/built-in/boolean/driver.o -c 
> /<>/xsd/tests/cxx/parser/validation/built-in/boolean/driver.cxx
> arm-linux-gnueabi-g++ 
> -I/<>/xsd/tests/cxx/parser/validation/built-in/byte 
> -I/<>/xsd/tests/cxx/parser/validation/built-in/byte 
> -I/<>/xsd/libxsd  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -std=gnu++11  -o 
> /<>/xsd/tests/cxx/parser/validation/built-in/byte/driver.o -c 
> /<>/xsd/tests/cxx/parser/validation/built-in/byte/driver.cxx
> arm-linux-gnueabi-g++ 
> -I/<>/xsd/tests/cxx/parser/validation/built-in/date-time 
> -I/<>/xsd/tests/cxx/parser/validation/built-in/date-time 
> -I/<>/xsd/libxsd  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -std=gnu++11  -o 
> /<>/xsd/tests/cxx/parser/validation/built-in/date-time/driver.o 
> -c 
> /<>/xsd/tests/cxx/parser/validation/built-in/date-time/driver.cxx
> In file included from 
> /<>/xsd/libxsd/xsd/cxx/parser/validating/xml-schema-pimpl.hxx:10,
>  from 
> /<>/xsd/tests/cxx/parser/validation/built-in/binary/driver.cxx:10:
> /<>/xsd/libxsd/xsd/cxx/config.hxx:40:29: warning: 
> ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' 
> instead [-Wdeprecated-declarations]
>40 | #  define XSD_AUTO_PTR std::auto_ptr
>   | ^~~~
> /<>/xsd/libxsd/xsd/cxx/parser/validating/xml-schema-pskel.hxx:498:19:
>  note: in expansion of macro ‘XSD_AUTO_PTR’
>   498 |   virtual XSD_AUTO_PTR
>   |   ^~~~
> In file included from /usr/include/c++/13/memory:78,
>  from 
> /<>/xsd/libxsd/xsd/cxx/parser/validating/xml-schema-pskel.hxx:9,
>  from 
> /<>/xsd/libxsd/xsd/cxx/parser/validating/xml-schema-pimpl.hxx:12:
> /usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
>65 |   template class auto_ptr;
>   |^~~~
> /<>/xsd/libxsd/xsd/cxx/config.hxx:40:29: warning: 
> ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' 
> instead [-Wdeprecated-declarations]
>40 | #  define XSD_AUTO_PTR std::auto_ptr
>   | ^~~~
> /<>/xsd/libxsd/xsd/cxx/parser/validating/xml-schema-pskel.hxx:511:19:
>  note: in expansion of macro ‘XSD_AUTO_PTR’
>   511 |   virtual XSD_AUTO_PTR
>   |   ^~~~
> /usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
>65 |   template class auto_ptr;
>   |^~~~
> In file included from 
> /<>/xsd/libxsd/xsd/cxx/parser/validating/xml-schema-pimpl.hxx:10,
>  from 
> /<>/xsd/tests/cxx/parser/validation/built-in/boolean/driver.cxx:10:
> /<>/xsd/libxsd/xsd/cxx/config.hxx:40:29: warning: 
> ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' 
> instead [-Wdeprecated-declarations]
>40 | #  define XSD_AUTO_PTR std::auto_ptr
>   | ^~~~
> /<>/xsd/libx

Bug#1069555: gtk-d: FTBFS on armel: unsatisfiable build-dependencies: dh-dlang (>= 0.6.6), gir-to-d

[Lucas Nussbaum]

Source: gtk-d
Version: 3.10.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-dlang (>= 0.6.6), gir-to-d, 
> gnome-pkg-tools (>= 0.10), libgstreamer-plugins-base1.0-dev, 
> libgstreamer1.0-dev, libgtk-3-dev, libgtksourceview-3.0-dev, libpeas-dev, 
> libvte-2.91-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-dlang (>= 0.6.6), 
> gir-to-d, gnome-pkg-tools (>= 0.10), libgstreamer-plugins-base1.0-dev, 
> libgstreamer1.0-dev, libgtk-3-dev, libgtksourceview-3.0-dev, libpeas-dev, 
> libvte-2.91-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [800 B]
> Get:5 copy:/<>/apt_archive ./ Packages [832 B]
> Fetched 2241 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: dh-dlang (>= 0.6.6) but it is not 
> going to be installed
>Depends: gir-to-d but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/gtk-d_3.10.0-3_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069554: winff: FTBFS on armel: build-dependency not installable: libreoffice-draw-nogui

[Lucas Nussbaum]

Source: winff
Version: 1.6.3+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), fpc, libgtk2.0-dev, lcl, 
> lcl-qt5, build-essential, fakeroot, libreoffice-draw-nogui, libreoffice-writer
> Filtered Build-Depends: debhelper-compat (= 13), fpc, libgtk2.0-dev, lcl, 
> lcl-qt5, build-essential, fakeroot, libreoffice-draw-nogui, libreoffice-writer
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [715 B]
> Get:5 copy:/<>/apt_archive ./ Packages [727 B]
> Fetched 2051 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libreoffice-draw-nogui but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/winff_1.6.3+dfsg-2_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069552: freecontact: FTBFS on armel: make[1]: *** [Makefile:469: all-recursive] Error 1

[Lucas Nussbaum]

Source: freecontact
Version: 1.0.21-13.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/src'
> g++ -DHAVE_CONFIG_H -I. -I../lib  -I../lib -I../src -I/usr/include 
> -I/usr/include/xercesc  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -c -o 
> freecontact-freecontact.o `test -f 'freecontact.cpp' || echo 
> './'`freecontact.cpp
> xsdcxx cxx-tree --location-map 
> http://bioxsd.org/BioXSD-1.1.xsd=BioXSD-1.1.xsd \
>   --namespace-map 
> http://rostlab.org/freecontact/input=freecontact_input_xsd \
>   --namespace-map 
> http://rostlab.org/freecontact/output=freecontact_output_xsd \
>   --namespace-map http://bioxsd.org/BioXSD-1.1=BioXSD \
>   --generate-serialization --generate-doxygen \
>   --generate-polymorphic --polymorphic-type-all \
>   --omit-default-attributes \
>   --root-element-all \
>   --hxx-suffix _xsd.hxx --cxx-suffix _xsd.cxx \
>   BioXSD-1.1.xsd
> sed -e 
> 's|__pkgdatadir__|/usr/share/freecontact|g;s|__examplesdir__|/usr/share/doc/freecontact/examples|g;s|__sysconfdir__|/etc|g;s|__bindir__|/usr/bin|g;s|__PACKAGE_VERSION__|1.0.21|g'
>  "freecontact.cpp" | \
> pod2man --utf8 -c 'User Commands' -r "1.0.21" -name FREECONTACT > 
> "freecontact.1"
> make[2]: *** [Makefile:1405: BioXSD-1.1_xsd.hxx] Illegal instruction
> make[2]: *** Waiting for unfinished jobs
> In file included from freecontact.cpp:25:
> ../lib/freecontact.h:69:54: warning: ignoring attributes on template argument 
> ‘freecontact::__m128i’ {aka ‘__vector(2) long long int’} 
> [-Wignored-attributes]
>69 | class LIBFREEC_API ali_t : public std::vector<__m128i>
>   |  ^
> ../lib/freecontact.h: In constructor ‘freecontact::ali_t::ali_t(uint16_t)’:
> ../lib/freecontact.h:80:79: warning: ignoring attributes on template argument 
> ‘freecontact::__m128i’ {aka ‘__vector(2) long long int’} 
> [-Wignored-attributes]
>80 | ali_t( const uint16_t __alilen = 0 ) : 
> std::vector<__m128i>(), seqcnt(0), alilen(__alilen), alilen16(( alilen-1 )/16 
> + 1), alilenpad( 16 * alilen16 )
>   |   
> ^
> freecontact.cpp: In function ‘int main(int, char**)’:
> freecontact.cpp:165:9: warning: ‘template class std::auto_ptr’ is 
> deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations]
>   165 | auto_ptr ali_ifs_p;
>   | ^~~~
> In file included from /usr/include/c++/13/memory:78,
>  from /usr/include/boost/function/function_base.hpp:33,
>  from /usr/include/boost/function/detail/prologue.hpp:18,
>  from /usr/include/boost/function/function_template.hpp:13,
>  from /usr/include/boost/function/detail/maybe_include.hpp:22,
>  from /usr/include/boost/function/function1.hpp:11,
>  from 
> /usr/include/boost/program_options/value_semantic.hpp:13,
>  from 
> /usr/include/boost/program_options/options_description.hpp:13,
>  from /usr/include/boost/program_options.hpp:15,
>  from freecontact.cpp:17:
> /usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
>65 |   template class auto_ptr;
>   |^~~~
> freecontact.cpp:169:25: warning: ‘template class std::auto_ptr’ is 
> deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations]
>   169 | ali_ifs_p = auto_ptr(new 
> std::ifstream(vm["ali"].as().c_str()));
>   | ^~~~
> /usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
>65 |   template class auto_ptr;
>   |^~~~
> make[2]: Leaving directory '/<>/src'
> make[1]: *** [Makefile:469: all-recursive] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/freecontact_1.0.21-13.1_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available 

Bug#1069549: racket: FTBFS on armel: dh_install: error: missing files, aborting

[Lucas Nussbaum]

Source: racket
Version: 8.12+dfsg1-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>/build'
> bin/zuo . install MAKE="make" DESTDIR="/<>/debian/tmp" 
> PLT_SETUP_OPTIONS=""
> bc/racket3m -O info'@'compiler/cm -l- setup --boot ../src/setup-go.rkt 
> bc/compiled ignored bc/ignored.d ../src/bc/mksystem.rkt bc/system.rktd 3m 
> machine
> compiler/cm:   start-compile: /<>/src/bc/mksystem.rkt
> compiler/cm:   finish-compile: /<>/src/bc/mksystem.rkt
> bc/racket3m -O info'@'compiler/cm -l- setup --boot ../src/setup-go.rkt 
> bc/compiled ignored bc/ignored.d ../src/bc/mkincludes.rkt 
> /<>/debian/tmp/usr/include/racket ../src/bc/ bc
> compiler/cm:   start-compile: /<>/src/bc/mkincludes.rkt
> compiler/cm:   finish-compile: /<>/src/bc/mkincludes.rkt
> Making /<>/debian/tmp/usr/include/racket
> Done.
> cp bc/racket3m /<>/debian/tmp/usr/bin/racketbc
> strip /<>/debian/tmp/usr/bin/racketbc
> bc/racket3m -O info'@'compiler/cm -l- setup --boot ../src/setup-go.rkt 
> bc/compiled ignored bc/ignored.d ../src/start/collects-path.rkt ../src/ 
> /<>/debian/tmp/usr/bin/racketbc /usr/share/racket/collects 
> /etc/racket
> compiler/cm:   start-compile: /<>/src/start/collects-path.rkt
> compiler/cm:   finish-compile: /<>/src/start/collects-path.rkt
> cp bc/gracket3m 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/racket/gracketbc
> strip /<>/debian/tmp/usr/lib/arm-linux-gnueabi/racket/gracketbc
> bc/racket3m -O info'@'compiler/cm -l- setup --boot ../src/setup-go.rkt 
> bc/compiled ignored bc/ignored.d ../src/start/collects-path.rkt ../src/ 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/racket/gracketbc 
> /usr/share/racket/collects /etc/racket
> strip /<>/debian/tmp/usr/lib/arm-linux-gnueabi/racket/starter
> bc/racket3m -O info'@'compiler/cm -l- setup --boot ../src/setup-go.rkt 
> bc/compiled ignored bc/ignored.d ../src/start/collects-path.rkt ../src/ 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/racket/starter 
> /usr/share/racket/collects /etc/racket
> cp bc/libracket3m.a 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/libracket3m.a
> strip -S /<>/debian/tmp/usr/lib/arm-linux-gnueabi/libracket3m.a
> /<>/debian/tmp/usr/bin/racketbc -X ../collects -G ../etc -O 
> info'@'compiler/cm -l- setup --boot ../src/setup-go.rkt bc/compiled ignored 
> bc/ignored.d ../collects/setup/unixstyle-install.rkt make-install-copytree 
> ../ /<>/debian/tmp/usr/bin 
> /<>/debian/tmp/usr/share/racket/collects 
> /<>/debian/tmp/usr/share/racket/pkgs 
> /<>/debian/tmp/usr/share/doc/racket 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi 
> /<>/debian/tmp/usr/include/racket 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/racket 
> /<>/debian/tmp/usr/share/racket 
> /<>/debian/tmp/etc/racket 
> /<>/debian/tmp/usr/share/applications 
> /<>/debian/tmp/usr/share/man no bc/compiled
> Copying collects -> /<>/debian/tmp/usr/share/racket/collects
> Copying share/pkgs -> /<>/debian/tmp/usr/share/racket/pkgs
> Copying share -> /<>/debian/tmp/usr/share/racket
> Copying doc -> /<>/debian/tmp/usr/share/doc/racket
>   missing source path "doc", skipping...
> Copying etc -> /<>/debian/tmp/etc/racket
> Copying with merge collects -> 
> /<>/debian/tmp/usr/share/racket/collects
> Copying with merge share/pkgs -> 
> /<>/debian/tmp/usr/share/racket/pkgs
> Copying with merge doc -> /<>/debian/tmp/usr/share/doc/racket
>   missing source path "doc", skipping...
> Rewriting configuration file at: 
> /<>/debian/tmp/etc/racket/config.rktd...
> /<>/debian/tmp/usr/bin/racketbc -X 
> /<>/debian/tmp/usr/share/racket/collects -G 
> /<>/debian/tmp/etc/racket --no-user-path -N raco -l- setup 
> --no-user --no-docs
> raco setup: version: 8.12
> raco setup: platform: arm-linux [3m]
> raco setup: target machine: racket
> raco setup: installation name: 8.12
> raco setup: variants: 3m
> raco setup: main collects: 
> /<>/debian/tmp/usr/share/racket/collects
> raco setup: collects paths: 
> raco setup:   /<>/debian/tmp/usr/share/racket/collects
> raco setup: main pkgs: /<>/debian/tmp/usr/share/racket/pkgs
> raco setup: pkgs paths: 
> raco setup:   /<>/debian/tmp/usr/share/racket/pkgs
> raco setup:   /sbuild-nonexistent/.local/share/racket/8.12/pkgs
> raco setup: links

Bug#1069550: kvirc: FTBFS on armel: build-dependency not installable: qtwebengine5-dev

[Lucas Nussbaum]

Source: kvirc
Version: 4:5.2.2+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cmake (>= 3.16.0), debhelper-compat (= 13), 
> dh-sequence-kf5, extra-cmake-modules, libenchant-2-dev, libkf5coreaddons-dev, 
> libkf5i18n-dev, libkf5kio-dev, libkf5notifications-dev, libkf5parts-dev, 
> libkf5service-dev, libkf5windowsystem-dev, libkf5xmlgui-dev, libperl-dev, 
> libphonon4qt5-dev, libqt5svg5-dev, libqt5x11extras5-dev, libssl-dev, 
> libx11-dev, libxrender-dev, libxss-dev, pkgconf, python3-dev, qtbase5-dev, 
> qtmultimedia5-dev, qtwebengine5-dev, zlib1g-dev, build-essential, fakeroot, 
> doxygen, graphviz
> Filtered Build-Depends: cmake (>= 3.16.0), debhelper-compat (= 13), 
> dh-sequence-kf5, extra-cmake-modules, libenchant-2-dev, libkf5coreaddons-dev, 
> libkf5i18n-dev, libkf5kio-dev, libkf5notifications-dev, libkf5parts-dev, 
> libkf5service-dev, libkf5windowsystem-dev, libkf5xmlgui-dev, libperl-dev, 
> libphonon4qt5-dev, libqt5svg5-dev, libqt5x11extras5-dev, libssl-dev, 
> libx11-dev, libxrender-dev, libxss-dev, pkgconf, python3-dev, qtbase5-dev, 
> qtmultimedia5-dev, qtwebengine5-dev, zlib1g-dev, build-essential, fakeroot, 
> doxygen, graphviz
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [ B]
> Get:5 copy:/<>/apt_archive ./ Packages [1106 B]
> Fetched 2832 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: qtwebengine5-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/kvirc_5.2.2+dfsg-2_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069548: haskell-yesod-auth-hashdb: FTBFS on armel: unsatisfiable build-dependencies

[Lucas Nussbaum]

Source: haskell-yesod-auth-hashdb
Version: 1.7.1.7-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 9.4), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-aeson-dev, libghc-aeson-prof, 
> libghc-persistent-dev (>= 2.1), libghc-persistent-prof, libghc-yesod-auth-dev 
> (>= 1.4.18), libghc-yesod-auth-dev (<< 1.7), libghc-yesod-auth-prof, 
> libghc-yesod-core-dev (>= 1.4.19), libghc-yesod-core-dev (<< 1.7), 
> libghc-yesod-core-prof, libghc-yesod-form-dev (>= 1.4), libghc-yesod-form-dev 
> (<< 1.8), libghc-yesod-form-prof, libghc-yesod-persistent-dev (>= 1.2), 
> libghc-yesod-persistent-prof, build-essential, fakeroot, ghc-doc, 
> libghc-aeson-doc, libghc-persistent-doc, libghc-yesod-auth-doc, 
> libghc-yesod-core-doc, libghc-yesod-form-doc, libghc-yesod-persistent-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 9.4), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-aeson-dev, libghc-aeson-prof, 
> libghc-persistent-dev (>= 2.1), libghc-persistent-prof, libghc-yesod-auth-dev 
> (>= 1.4.18), libghc-yesod-auth-dev (<< 1.7), libghc-yesod-auth-prof, 
> libghc-yesod-core-dev (>= 1.4.19), libghc-yesod-core-dev (<< 1.7), 
> libghc-yesod-core-prof, libghc-yesod-form-dev (>= 1.4), libghc-yesod-form-dev 
> (<< 1.8), libghc-yesod-form-prof, libghc-yesod-persistent-dev (>= 1.2), 
> libghc-yesod-persistent-prof, build-essential, fakeroot, ghc-doc, 
> libghc-aeson-doc, libghc-persistent-doc, libghc-yesod-auth-doc, 
> libghc-yesod-core-doc, libghc-yesod-form-doc, libghc-yesod-persistent-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1270 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1283 B]
> Fetched 3168 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-yesod-auth-dev : Depends: libghc-aeson-dev-2.1.2.1-758be but it is 
> not installable
>  Depends: libghc-authenticate-dev-1.3.5.2-027bd but 
> it is not installable
>  Depends: libghc-base-dev-4.17.2.0-38dbb but it is 
> not installable
>  Depends: libghc-base16-bytestring-dev-1.0.2.0-9ed39 
> but it is not installable
>  Depends: libghc-base64-bytestring-dev-1.2.1.0-9b712 
> but it is not installable
>  Depends: libghc-binary-dev-0.8.9.1-67631 but it is 
> not installable
>  Depends: libghc-blaze-builder-dev-0.4.2.3-9f520 but 
> it is not installable
>  Depends: libghc-blaze-html-dev-0.9.1.2-b0fe9 but it 
> is not installable
>  Depends: libghc-blaze-markup-dev-0.8.3.0-22399 but 
> it is not installable
>  Depends: libghc-bytestring-dev-0.11.5.2-302b4 but it 
> is not installable
>  Depends: libghc-conduit-dev-1.3.5-d052e but it is 
> not installable
>  Depends: libghc-conduit-extra-dev-1.3.6-c2c52 but it 
> is not installable
>  Depends: libghc-containers-dev-0.6.7-e92e7 but it is 
> not installable
>  Depends: libghc-cryptonite-dev-0.30-aaf1f but it is 
> not installable
>  Depends: libghc-data-default-dev-0.7.1.1-11a36 but 
> it is not install

Bug#1069547: libkolabxml: FTBFS on armel: make[3]: *** [CMakeFiles/generate_bindings.dir/build.make:89: bindings/kolabformat.cxx] Error 132

[Lucas Nussbaum]

Source: libkolabxml
Version: 1.2.1-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/.pybuild/cpython3_3.12/build'
> [  7%] Generating XSD bindings
> [  7%] Compiling Kolab XSD schema
> cd /<> && /usr/bin/xsdcxx cxx-tree --generate-polymorphic 
> --generate-serialization --namespace-map http://kolab.org=KolabXSD 
> --root-element icalendar --root-element vcards --root-element note 
> --root-element configuration --root-element file --output-dir 
> /<>/.pybuild/cpython3_3.12/build/bindings 
> /<>/schemas/ical/kolabformat-xcal.xsd 
> /<>/schemas/ical/iCalendar-params.xsd 
> /<>/schemas/ical/iCalendar-props.xsd 
> /<>/schemas/ical/iCalendar-valtypes.xsd 
> /<>/schemas/kolabformat-xcard.xsd 
> /<>/schemas/xCard.xsd /<>/schemas/kolabformat.xsd
> cd /<> && /<>/.pybuild/cpython3_3.12/build/xsdbin 
> --verbose --array-name iCalendar_schema --output-dir 
> /<>/.pybuild/cpython3_3.12/build 
> /<>/schemas/ical/kolabformat-xcal.xsd 
> /<>/schemas/ical/iCalendar-params.xsd 
> /<>/schemas/ical/iCalendar-props.xsd 
> /<>/schemas/ical/iCalendar-valtypes.xsd 
> /<>/schemas/kolabformat-xcard.xsd 
> /<>/schemas/xCard.xsd /<>/schemas/kolabformat.xsd
> loading /<>/schemas/ical/kolabformat-xcal.xsd
> loading /<>/schemas/ical/iCalendar-params.xsd
> loading /<>/schemas/ical/iCalendar-props.xsd
> loading /<>/schemas/ical/iCalendar-valtypes.xsd
> loading /<>/schemas/kolabformat-xcard.xsd
> loading /<>/schemas/xCard.xsd
> loading /<>/schemas/kolabformat.xsd
> uncomressed data size 229376 bytes
> comressed data size 126131 bytes
> Illegal instruction
> make[3]: *** [CMakeFiles/generate_bindings.dir/build.make:89: 
> bindings/kolabformat.cxx] Error 132


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libkolabxml_1.2.1-5_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069546: ktorrent: FTBFS on armel: dh_install: error: missing files, aborting

[Lucas Nussbaum]

Source: ktorrent
Version: 22.12.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-arm-linux-gnueabi'
> make[2]: Nothing to be done for 'preinstall'.
> make[2]: Leaving directory '/<>/obj-arm-linux-gnueabi'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/libktcore.so.16.0.0
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/libktcore.so.16
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_logviewer.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_logviewer.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_infowidget.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_infowidget.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_upnp.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_upnp.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_scanfolder.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_scanfolder.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_scanforlostfiles.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_scanforlostfiles.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_ipfilter.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_ipfilter.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_stats.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_stats.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_bwscheduler.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_bwscheduler.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/ktorrent/ktorrent_bwschedulerui.rc
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_mediaplayer.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_mediaplayer.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/ktorrent/ktorrent_mediaplayerui.rc
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_downloadorder.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_downloadorder.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/ktorrent/ktorrent_downloadorderui.rc
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_zeroconf.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_zeroconf.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_magnetgenerator.so
> -- Set non-toolchain portion of runtime path of 
> "/<>/debian/tmp/usr/lib/arm-linux-gnueabi/qt5/plugins/ktorrent_plugins/ktorrent_magnetgenerator.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/ktorrent/ktorrent_magnetgeneratorui.rc
> --

Bug#1069544: mame: FTBFS on armel: collect2: error: ld returned 1 exit status

[Lucas Nussbaum]

Source: mame
Version: 0.264+dfsg.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> g++ -o ../../../../../mame obj/Release/src/mame/mame.o 
> obj/Release/generated/mame/mame/drivlist.o obj/Release/generated/version.o
> -fuse-ld=gold -Wl,--no-keep-memory -Wl,-z,relro -Wl,-z,now -Wl,--long-plt 
> -L"../../../../../../../../usr/X11/lib" 
> -L"../../../../../../../../usr/X11R6/lib" 
> -L"../../../../../../../../usr/openwin/lib" -L"." 
> -L"../../../../../scripts/mame_mame" -L"../../../../../scripts/src/mame" 
> -L"../../../../../scripts/src" -L"../../../../../scripts/src/osd/mame_mame" 
> -L"../../../../../scripts/src/osd" -L/usr/lib/arm-linux-gnueabi 
> -Wl,--start-group ../../../../../scripts/mame_mame/libitech.a 
> ../../../../../scripts/mame_mame/libsubsino.a 
> ../../../../../scripts/mame_mame/libmidw8080.a 
> ../../../../../scripts/mame_mame/libericsson.a 
> ../../../../../scripts/mame_mame/libzpa.a 
> ../../../../../scripts/mame_mame/libtecfri.a 
> ../../../../../scripts/mame_mame/libfairchild.a 
> ../../../../../scripts/mame_mame/libcompugraphic.a 
> ../../../../../scripts/mame_mame/libchromatics.a 
> ../../../../../scripts/mame_mame/libwyse.a 
> ../../../../../scripts/mame_mame/libtatsumi.a 
> ../../../../../scripts/mame_mame/libgridcomp.a 
> ../../../../../scripts/mame_mame/libces.a 
> ../../../../../scripts/mame_mame/libupl.a 
> ../../../../../scripts/mame_mame/libadp.a 
> ../../../../../scripts/mame_mame/libfuuki.a 
> ../../../../../scripts/mame_mame/libsnk.a 
> ../../../../../scripts/mame_mame/libbarcrest.a 
> ../../../../../scripts/mame_mame/libzenith.a 
> ../../../../../scripts/mame_mame/libbondwell.a 
> ../../../../../scripts/mame_mame/libfalco.a 
> ../../../../../scripts/mame_mame/libsynertek.a 
> ../../../../../scripts/mame_mame/libsamsung.a 
> ../../../../../scripts/mame_mame/libunicard.a 
> ../../../../../scripts/mame_mame/libmips.a 
> ../../../../../scripts/mame_mame/libdg.a 
> ../../../../../scripts/mame_mame/libhomebrew.a 
> ../../../../../scripts/mame_mame/libcasio.a 
> ../../../../../scripts/mame_mame/libgalaxian.a 
> ../../../../../scripts/mame_mame/libosi.a 
> ../../../../../scripts/mame_mame/libelektron.a 
> ../../../../../scripts/mame_mame/libkyocera.a 
> ../../../../../scripts/mame_mame/libarcadia.a 
> ../../../../../scripts/mame_mame/libibm.a 
> ../../../../../scripts/mame_mame/libnintendo.a 
> ../../../../../scripts/mame_mame/libensoniq.a 
> ../../../../../scripts/mame_mame/libunisonic.a 
> ../../../../../scripts/mame_mame/libepson.a 
> ../../../../../scripts/mame_mame/libunico.a 
> ../../../../../scripts/mame_mame/libbandai.a 
> ../../../../../scripts/mame_mame/libtatung.a 
> ../../../../../scripts/mame_mame/libtiger.a 
> ../../../../../scripts/mame_mame/libmetro.a 
> ../../../../../scripts/mame_mame/libexcellent.a 
> ../../../../../scripts/mame_mame/libpacman.a 
> ../../../../../scripts/mame_mame/libtoshiba.a 
> ../../../../../scripts/mame_mame/libtoaplan.a 
> ../../../../../scripts/mame_mame/libfidelity.a 
> ../../../../../scripts/mame_mame/libxerox.a 
> ../../../../../scripts/mame_mame/libverifone.a 
> ../../../../../scripts/mame_mame/libeaca.a 
> ../../../../../scripts/mame_mame/libheathkit.a 
> ../../../../../scripts/mame_mame/libamiga.a 
> ../../../../../scripts/mame_mame/libphilips.a 
> ../../../../../scripts/mame_mame/libausnz.a 
> ../../../../../scripts/mame_mame/libmatic.a 
> ../../../../../scripts/mame_mame/libwing.a 
> ../../../../../scripts/mame_mame/libnichibutsu.a 
> ../../../../../scripts/mame_mame/libsharp.a 
> ../../../../../scripts/mame_mame/libfunworld.a 
> ../../../../../scripts/mame_mame/libsanritsu.a 
> ../../../../../scripts/mame_mame/libbitcorp.a 
> ../../../../../scripts/mame_mame/libmit.a 
> ../../../../../scripts/mame_mame/libtomy.a 
> ../../../../../scripts/mame_mame/libmicroterm.a 
> ../../../../../scripts/mame_mame/libampro.a 
> ../../../../../scripts/mame_mame/libliberty.a 
> ../../../../../scripts/mame_mame/libbanctec.a 
> ../../../../../scripts/mame_mame/libhusky.a 
> ../../../../../scripts/mame_mame/librobotron.a 
> ../../../../../scripts/mame_mame/libatari.a 
> ../../../../../scripts/mame_mame/libnetronics.a 
> ../../../../../scripts/mame_mame/libacorn.a 
> ../../../../../scripts/mame_mame/libsequential.a 
> ../../../../../scripts/mame_mame/libcybiko.a 
> ../../../../../scripts/mame_mame/libosborne.a 
> ../../../../../scripts/mame_mame/libpalm.a 
> ../../../../../sc

Bug#1069542: octave: FTBFS on armel: make[1]: *** [debian/rules:59: override_dh_auto_build-indep] Error 1

[Lucas Nussbaum]

Source: octave
Version: 8.4.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Enforce generic BLAS (in order to avoid tying the binary to OpenBLAS or 
> ATLAS)
> # Also pass OpenMP flag (#631831)
> # Pass the install directory of fonts-freefont-otf package
> dh_auto_configure -- \
>   --with-blas=blas --enable-openmp \
>   --with-system-freefont=/usr/share/fonts/opentype/freefont \
>   --disable-rpath \
>   --disable-java --with-hdf5-includedir=/usr/include/hdf5/serial 
> --with-hdf5-libdir=/usr/lib/arm-linux-gnueabi/hdf5/serial 
>   ./configure --build=arm-linux-gnueabi --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-option-checking --disable-silent-rules 
> --libdir=\${prefix}/lib/arm-linux-gnueabi --runstatedir=/run 
> --disable-maintainer-mode --disable-dependency-tracking --with-blas=blas 
> --enable-openmp --with-system-freefont=/usr/share/fonts/opentype/freefont 
> --disable-rpath --disable-java 
> --with-hdf5-includedir=/usr/include/hdf5/serial 
> --with-hdf5-libdir=/usr/lib/arm-linux-gnueabi/hdf5/serial
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a race-free mkdir -p... /usr/bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether UID '1001' is supported by ustar format... yes
> checking whether GID '1001' is supported by ustar format... yes
> checking how to create a ustar tar archive... gnutar
> checking whether make supports nested variables... (cached) yes
> checking build system type... arm-unknown-linux-gnueabi
> checking host system type... arm-unknown-linux-gnueabi
> checking whether make supports the include directive... yes (GNU style)
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether the compiler supports GNU C... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to enable C11 features... none needed
> checking whether gcc understands -c and -o together... yes
> checking whether the compiler is clang... no
> checking for compiler option needed when checking for declarations... none
> checking dependency style of gcc... none
> checking for stdio.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for strings.h... yes
> checking for sys/stat.h... yes
> checking for sys/types.h... yes
> checking for unistd.h... yes
> checking for wchar.h... yes
> checking for minix/config.h... no
> checking for sys/param.h... yes
> checking for sys/socket.h... yes
> checking for dirent.h... yes
> checking for fnmatch.h... yes
> checking for netdb.h... yes
> checking for getopt.h... yes
> checking for sys/cdefs.h... yes
> checking for sys/time.h... yes
> checking for glob.h... yes
> checking for threads.h... yes
> checking for iconv.h... yes
> checking for limits.h... yes
> checking for langinfo.h... yes
> checking for xlocale.h... no
> checking for math.h... yes
> checking for sys/mman.h... yes
> checking for sys/select.h... yes
> checking for stdalign.h... yes
> checking for stdbool.h... yes
> checking for stdckdint.h... no
> checking for sys/random.h... yes
> checking for sys/resource.h... yes
> checking for sys/times.h... yes
> checking for sys/uio.h... yes
> checking for sys/utsname.h... yes
> checking for sys/wait.h... yes
> checking for features.h... yes
> checking for crtdefs.h... no
> checking for wctype.h... yes
> checking whether it is safe to define __EXTENSIONS__... yes
> checking whether _XOPEN_SOURCE should be defined... no
> defining octlibdir to be ${libdir}/octave/${version}
> defining archlibdir to be 
> ${libexecdir}/octave/${version}/exec/${canonical_host_type}
> defining localarchlibdir to be 
> ${libexecdir}/octave/site/exec/${canonical_host_type}
> defining localapiarchlibdir to be 
> ${libexecdir}/octave/${api_version}/site/exec/${canonical_host_type}
> defining localverarchlibdir to be 
> ${libexecdir}/octave/${version}/site/exec/${canonical_host_type}
> defining octfile

Bug#1069543: haskell-gi-vte: FTBFS on armel: unsatisfiable build-dependencies

[Lucas Nussbaum]

Source: haskell-gi-vte
Version: 2.91.31-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | 
> haskell-devscripts (>= 0.13), cdbs, ghc, ghc-prof, pkg-config, 
> libvte-2.91-dev, libghc-gi-atk-dev (>= 2.0), libghc-gi-atk-dev (<< 2.1), 
> libghc-gi-atk-prof, libghc-gi-gdk-dev (>= 3.0), libghc-gi-gdk-dev (<< 3.1), 
> libghc-gi-gdk-prof, libghc-gi-gio-dev (>= 2.0), libghc-gi-gio-dev (<< 2.1), 
> libghc-gi-gio-prof, libghc-gi-glib-dev (>= 2.0), libghc-gi-glib-dev (<< 2.1), 
> libghc-gi-glib-prof, libghc-gi-gobject-dev (>= 2.0), libghc-gi-gobject-dev 
> (<< 2.1), libghc-gi-gobject-prof, libghc-gi-gtk-dev (>= 3.0), 
> libghc-gi-gtk-dev (<< 3.1), libghc-gi-gtk-prof, libghc-gi-pango-dev (>= 1.0), 
> libghc-gi-pango-dev (<< 1.1), libghc-gi-pango-prof, libghc-haskell-gi-dev (>= 
> 0.26), libghc-haskell-gi-dev (<< 0.27), libghc-haskell-gi-prof, 
> libghc-haskell-gi-base-dev (>= 0.26), libghc-haskell-gi-base-dev (<< 0.27), 
> libghc-haskell-gi-base-prof, build-essential, fakeroot, ghc-doc, 
> libghc-gi-atk-doc, libghc-gi-gdk-doc, libghc-gi-gio-doc, libghc-gi-glib-doc, 
> libghc-gi-gobject-doc, libghc-gi-gtk-doc, libghc-gi-pango-doc, 
> libghc-haskell-gi-doc, libghc-haskell-gi-base-doc
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, 
> ghc, ghc-prof, pkg-config, libvte-2.91-dev, libghc-gi-atk-dev (>= 2.0), 
> libghc-gi-atk-dev (<< 2.1), libghc-gi-atk-prof, libghc-gi-gdk-dev (>= 3.0), 
> libghc-gi-gdk-dev (<< 3.1), libghc-gi-gdk-prof, libghc-gi-gio-dev (>= 2.0), 
> libghc-gi-gio-dev (<< 2.1), libghc-gi-gio-prof, libghc-gi-glib-dev (>= 2.0), 
> libghc-gi-glib-dev (<< 2.1), libghc-gi-glib-prof, libghc-gi-gobject-dev (>= 
> 2.0), libghc-gi-gobject-dev (<< 2.1), libghc-gi-gobject-prof, 
> libghc-gi-gtk-dev (>= 3.0), libghc-gi-gtk-dev (<< 3.1), libghc-gi-gtk-prof, 
> libghc-gi-pango-dev (>= 1.0), libghc-gi-pango-dev (<< 1.1), 
> libghc-gi-pango-prof, libghc-haskell-gi-dev (>= 0.26), libghc-haskell-gi-dev 
> (<< 0.27), libghc-haskell-gi-prof, libghc-haskell-gi-base-dev (>= 0.26), 
> libghc-haskell-gi-base-dev (<< 0.27), libghc-haskell-gi-base-prof, 
> build-essential, fakeroot, ghc-doc, libghc-gi-atk-doc, libghc-gi-gdk-doc, 
> libghc-gi-gio-doc, libghc-gi-glib-doc, libghc-gi-gobject-doc, 
> libghc-gi-gtk-doc, libghc-gi-pango-doc, libghc-haskell-gi-doc, 
> libghc-haskell-gi-base-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1691 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1670 B]
> Fetched 3976 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-gi-gtk-dev : Depends: libghc-base-dev-4.17.2.0-38dbb but it is not 
> installable
>  Depends: libghc-bytestring-dev-0.11.5.2-302b4 but it is 
> not installable
>  Depends: libghc-containers-dev-0.6.7-e92e7 but it is not 
> installable
>  Depends: libghc-gi-atk-dev-2.0.27-4495d but it is not 
> installable
>  Depends: libghc-gi-cairo-dev-1.0.29-f173d but it is not 
> installable
>  Depends: libghc-gi-gdk-dev-3.0.28-504c3 but it is not 
> installable
>  Depen

Bug#1069541: haskell-gi-dbusmenugtk3: FTBFS on armel: unsatisfiable build-dependencies

[Lucas Nussbaum]

Source: haskell-gi-dbusmenugtk3
Version: 0.4.14-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | 
> haskell-devscripts (>= 0.13), cdbs, ghc, ghc-prof, pkg-config, libgtk-3-dev, 
> libdbusmenu-gtk3-dev, libghc-gi-atk-dev (>= 2.0), libghc-gi-atk-dev (<< 2.1), 
> libghc-gi-atk-prof, libghc-gi-dbusmenu-dev (>= 0.4), libghc-gi-dbusmenu-dev 
> (<< 0.5), libghc-gi-dbusmenu-prof, libghc-gi-gdk-dev (>= 3.0), 
> libghc-gi-gdk-dev (<< 3.1), libghc-gi-gdk-prof, libghc-gi-gdkpixbuf-dev (>= 
> 2.0), libghc-gi-gdkpixbuf-dev (<< 2.1), libghc-gi-gdkpixbuf-prof, 
> libghc-gi-glib-dev (>= 2.0), libghc-gi-glib-dev (<< 2.1), 
> libghc-gi-glib-prof, libghc-gi-gobject-dev (>= 2.0), libghc-gi-gobject-dev 
> (<< 2.1), libghc-gi-gobject-prof, libghc-gi-gtk-dev (>= 3.0), 
> libghc-gi-gtk-dev (<< 3.1), libghc-gi-gtk-prof, libghc-haskell-gi-dev (>= 
> 0.26), libghc-haskell-gi-dev (<< 0.27), libghc-haskell-gi-prof, 
> libghc-haskell-gi-base-dev (>= 0.26), libghc-haskell-gi-base-dev (<< 0.27), 
> libghc-haskell-gi-base-prof, build-essential, fakeroot, ghc-doc, 
> libghc-gi-atk-doc, libghc-gi-dbusmenu-doc, libghc-gi-gdk-doc, 
> libghc-gi-gdkpixbuf-doc, libghc-gi-glib-doc, libghc-gi-gobject-doc, 
> libghc-gi-gtk-doc, libghc-haskell-gi-doc, libghc-haskell-gi-base-doc
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, 
> ghc, ghc-prof, pkg-config, libgtk-3-dev, libdbusmenu-gtk3-dev, 
> libghc-gi-atk-dev (>= 2.0), libghc-gi-atk-dev (<< 2.1), libghc-gi-atk-prof, 
> libghc-gi-dbusmenu-dev (>= 0.4), libghc-gi-dbusmenu-dev (<< 0.5), 
> libghc-gi-dbusmenu-prof, libghc-gi-gdk-dev (>= 3.0), libghc-gi-gdk-dev (<< 
> 3.1), libghc-gi-gdk-prof, libghc-gi-gdkpixbuf-dev (>= 2.0), 
> libghc-gi-gdkpixbuf-dev (<< 2.1), libghc-gi-gdkpixbuf-prof, 
> libghc-gi-glib-dev (>= 2.0), libghc-gi-glib-dev (<< 2.1), 
> libghc-gi-glib-prof, libghc-gi-gobject-dev (>= 2.0), libghc-gi-gobject-dev 
> (<< 2.1), libghc-gi-gobject-prof, libghc-gi-gtk-dev (>= 3.0), 
> libghc-gi-gtk-dev (<< 3.1), libghc-gi-gtk-prof, libghc-haskell-gi-dev (>= 
> 0.26), libghc-haskell-gi-dev (<< 0.27), libghc-haskell-gi-prof, 
> libghc-haskell-gi-base-dev (>= 0.26), libghc-haskell-gi-base-dev (<< 0.27), 
> libghc-haskell-gi-base-prof, build-essential, fakeroot, ghc-doc, 
> libghc-gi-atk-doc, libghc-gi-dbusmenu-doc, libghc-gi-gdk-doc, 
> libghc-gi-gdkpixbuf-doc, libghc-gi-glib-doc, libghc-gi-gobject-doc, 
> libghc-gi-gtk-doc, libghc-haskell-gi-doc, libghc-haskell-gi-base-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1746 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1725 B]
> Fetched 4086 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-gi-gtk-dev : Depends: libghc-base-dev-4.17.2.0-38dbb but it is not 
> installable
>  Depends: libghc-bytestring-dev-0.11.5.2-302b4 but it is 
> not installable
>  Depends: libghc-containers-dev-0.6.7-e92e7 but it is not 
> installable
>  Depends: libghc-gi-atk-dev-2.0.27-4495d but it is not 
> installable
>  Depends: libghc-gi-cairo-dev-1.0.29-f173d but it is not 
> installable

Bug#1069538: zeroc-ice: FTBFS on armel: make[3]: *** [Makefile:29: tests] Error 1

[Lucas Nussbaum]

Source: zeroc-ice
Version: 3.7.10-2.2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/java-compat'
> gradle --gradle-user-home /<>/.gradle --info --console plain 
> --stacktrace --no-daemon --refresh-dependencies -PiceGridGuiUseJavaFX=false 
> -PicegridguiProguard=false -PjarsClassPath=true -PjgoodiesLooksVersion=debian 
> -PjgoodiesFormsVersion=debian -PopenjfxVersion=debian --offline 
> -PiceBuilderVersion=debian -PiceBuilderClassPath=com.zeroc.gradle.ice-builder 
> -PtargetJavaRelease=7 -Pprefix=/usr -PDESTDIR=/<>/debian/tmp 
> :test:assemble
> openjdk version "17.0.11" 2024-04-16
> OpenJDK Runtime Environment (build 17.0.11+9-Debian-1)
> OpenJDK Zero VM (build 17.0.11+9-Debian-1, interpreted mode)
> Initialized native services in: /<>/.gradle/native
> Using 4 worker leases.
> Creating new cache for fileHashes, path 
> /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@41f0c
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
> access org.gradle.cache.internal.DefaultCacheAccess@41f0c
> Creating new cache for fileHashes, path 
> /<>/java-compat/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@5a54b7
> Starting Build
> Settings evaluated using settings file 
> '/<>/java-compat/settings.gradle'.
> Projects loaded. Root project using build file 
> '/<>/java-compat/build.gradle'.
> Included projects: [root project 'java-compat', project ':glacier2-compat', 
> project ':ice-compat', project ':icebox-compat', project ':icebt-compat', 
> project ':icediscovery-compat', project ':icegrid-compat', project 
> ':icelocatordiscovery-compat', project ':icepatch2-compat', project 
> ':icestorm-compat', project ':test', project ':testLambda', project 
> ':testPlugins']
> Parallel execution is an incubating feature.
> Evaluating root project 'java-compat' using build file 
> '/<>/java-compat/build.gradle'.
> Creating new cache for metadata-1.1/results, path 
> /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@12ac7e0
>   Couldn't resolve system dependency:
> java.lang.ClassNotFoundException: org.debian.gradle.plugin.MavenResolverHook
>   at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:445)
>   at 
> org.gradle.internal.classloader.TransformingClassLoader.findClass(TransformingClassLoader.java:53)
>   at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:592)
>   at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
>   at java.base/java.lang.Class.forName0(Native Method)
>   at java.base/java.lang.Class.forName(Class.java:375)
>   at 
> org.gradle.api.internal.artifacts.repositories.resolver.MavenResolver.doResolveComponentMetaData(MavenResolver.java:129)
>   at 
> org.gradle.api.internal.artifacts.repositories.resolver.ExternalResourceResolver$RemoteRepositoryAccess.resolveComponentMetaData(ExternalResourceResolver.java:467)
>   at 
> org.gradle.api.internal.artifacts.ivyservice.ivyresolve.LocalModuleComponentRepository$LocalAccess.resolveComponentMetaData(LocalModuleComponentRepository.java:70)
>   at 
> org.gradle.api.internal.artifacts.ivyservice.ivyresolve.BaseModuleComponentRepositoryAccess.resolveComponentMetaData(BaseModuleComponentRepositoryAccess.java:50)
>   at 
> org.gradle.api.internal.artifacts.ivyservice.ivyresolve.memcache.InMemoryCachedModuleComponentRepository$CachedAccess.resolveComponentMetaData(InMemoryCachedModuleComponentRepository.java:95)
>   at 
> org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ErrorHandlingModuleComponentRepository$ErrorHandlingModuleComponentRepositoryAccess.resolveComponentMetaData(ErrorHandlingModuleComponentRepository.java:126)
>   at 
> org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ComponentMetaDataResolveState.process(ComponentMetaDataResolveState.java:66)
>   at 
> org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ComponentMetaDataResolveState.resolve(ComponentMetaDataResolveState.java:45)
>   at 
> org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainComponentMetaDataResolver.findBestMatch(RepositoryChainComponentMetaDataResolver.java:138)
>   at 
> org.gradle.api.internal.artifacts.ivyservice.ivyresolve

Bug#1069537: haskell-crypton-x509-store: FTBFS on armel: unsatisfiable build-dependencies

[Lucas Nussbaum]

Source: haskell-crypton-x509-store
Version: 1.6.9-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts (>= 0.13), cdbs, 
> ghc (>= 9.4), ghc-prof, libghc-asn1-encoding-dev (>= 0.9), 
> libghc-asn1-encoding-dev (<< 0.10), libghc-asn1-encoding-prof, 
> libghc-asn1-types-dev (>= 0.3), libghc-asn1-types-dev (<< 0.4), 
> libghc-asn1-types-prof, libghc-crypton-dev, libghc-crypton-prof, 
> libghc-crypton-x509-dev (>= 1.7.2), libghc-crypton-x509-prof, libghc-pem-dev 
> (>= 0.1), libghc-pem-dev (<< 0.3), libghc-pem-prof, libghc-tasty-dev, 
> libghc-tasty-prof, libghc-tasty-hunit-dev, libghc-tasty-hunit-prof, 
> build-essential, fakeroot, ghc-doc, libghc-asn1-encoding-doc, 
> libghc-asn1-types-doc, libghc-crypton-doc, libghc-crypton-x509-doc, 
> libghc-pem-doc
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts (>= 0.13), 
> cdbs, ghc (>= 9.4), ghc-prof, libghc-asn1-encoding-dev (>= 0.9), 
> libghc-asn1-encoding-dev (<< 0.10), libghc-asn1-encoding-prof, 
> libghc-asn1-types-dev (>= 0.3), libghc-asn1-types-dev (<< 0.4), 
> libghc-asn1-types-prof, libghc-crypton-dev, libghc-crypton-prof, 
> libghc-crypton-x509-dev (>= 1.7.2), libghc-crypton-x509-prof, libghc-pem-dev 
> (>= 0.1), libghc-pem-dev (<< 0.3), libghc-pem-prof, libghc-tasty-dev, 
> libghc-tasty-prof, libghc-tasty-hunit-dev, libghc-tasty-hunit-prof, 
> build-essential, fakeroot, ghc-doc, libghc-asn1-encoding-doc, 
> libghc-asn1-types-doc, libghc-crypton-doc, libghc-crypton-x509-doc, 
> libghc-pem-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1252 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1265 B]
> Fetched 3132 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-crypton-x509-dev : Depends: libghc-asn1-encoding-dev-0.9.6-77ff6 but 
> it is not installable
>Depends: libghc-asn1-parse-dev-0.9.5-b2c6a but it 
> is not installable
>Depends: libghc-asn1-types-dev-0.3.4-bc8b9 but it 
> is not installable
>Depends: libghc-base-dev-4.17.2.0-38dbb but it is 
> not installable
>Depends: libghc-bytestring-dev-0.11.5.2-302b4 but 
> it is not installable
>Depends: libghc-containers-dev-0.6.7-e92e7 but it 
> is not installable
>Depends: libghc-crypton-dev-0.33-c8903 but it is 
> not installable
>Depends: libghc-hourglass-dev-0.2.12-3e23a but it 
> is not installable
>Depends: libghc-memory-dev-0.18.0-fec46 but it is 
> not installable
>Depends: libghc-pem-dev-0.2.4-d84c7 but it is not 
> installable
>  libghc-crypton-x509-prof : Depends: libghc-asn1-encoding-prof-0.9.6-77ff6 
> but it is not installable
> Depends: libghc-asn1-parse-prof-0.9.5-b2c6a but 
> it is not installable
> Depends: libghc-asn1-types-prof-0.3.4-bc8b9 but 
> it is not installable
> Depends: libghc-base-prof-4.17.2.0-38dbb but it 
> is not installable
> Depends: libghc-bytestring-prof-0.11.5.2-302b4 
> but it is not installable
>

Bug#1069539: softhsm2: FTBFS on armel: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: softhsm2
Version: 2.6.1-2.2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> make[6]: Entering directory '/<>/src/lib/test'
> FAIL: p11test
> 
>SoftHSM 2.6.1: src/lib/test/test-suite.log
> 
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: p11test
> =
> 
> F
> 
> 
> !!!FAILURES!!!
> Test Results:
> Run:  25   Failures: 1   Errors: 0
> 
> 
> 1) test: InfoTests::testGetFunctionList (F) line: 124 TestsNoPINInitBase.cpp
> setUp() failed
> - equality assertion failed
> - Expected: 0
> - Actual  : 48
> 
> 
> ..
> 
> 
> OK (25 tests)
> 
> 
> 
> 
> 
> OK (25 tests)
> 
> 
> ..
> 
> 
> OK (25 tests)
> 
> 
> FAIL p11test (exit status: 1)
> 
> 
> Testsuite summary for SoftHSM 2.6.1
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See src/lib/test/test-suite.log
> 
> make[6]: *** [Makefile:812: test-suite.log] Error 1
> make[6]: Leaving directory '/<>/src/lib/test'
> make[5]: *** [Makefile:920: check-TESTS] Error 2
> make[5]: Leaving directory '/<>/src/lib/test'
> make[4]: *** [Makefile:993: check-am] Error 2
> make[4]: Leaving directory '/<>/src/lib/test'
> make[3]: *** [Makefile:642: check-recursive] Error 1
> make[3]: Leaving directory '/<>/src/lib'
> make[2]: *** [Makefile:404: check-recursive] Error 1
> make[2]: Leaving directory '/<>/src'
> make[1]: *** [Makefile:566: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/softhsm2_2.6.1-2.2_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069536: glib-d: FTBFS on armel: unsatisfiable build-dependencies: dh-dlang (>= 0.6.2), gir-to-d (>= 0.23.2)

[Lucas Nussbaum]

Source: glib-d
Version: 2.4.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-dlang (>= 0.6.2), gir-to-d 
> (>= 0.23.2), gnome-pkg-tools (>= 0.10), libgirepository1.0-dev (>= 1.70), 
> libglib2.0-dev (>= 2.70), meson (>= 0.46), build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-dlang (>= 0.6.2), 
> gir-to-d (>= 0.23.2), gnome-pkg-tools (>= 0.10), libgirepository1.0-dev (>= 
> 1.70), libglib2.0-dev (>= 2.70), meson (>= 0.46), build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [764 B]
> Get:5 copy:/<>/apt_archive ./ Packages [796 B]
> Fetched 2169 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: dh-dlang (>= 0.6.2) but it is not 
> going to be installed
>Depends: gir-to-d (>= 0.23.2) but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/glib-d_2.4.3-2_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069535: galera-3: FTBFS on armel: dh_auto_test: error: cd obj-arm-linux-gnueabi && make -j1 test ARGS\+=--verbose ARGS\+=-j1 ARGS=--output-on-failure returned exit code 2

[Lucas Nussbaum]

Source: galera-3
Version: 25.3.37-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-arm-linux-gnueabi'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --output-on-failure
> Test project /<>/obj-arm-linux-gnueabi
> Start 1: gu_tests
> 1/7 Test #1: gu_tests .   Passed1.91 sec
> Start 2: gu_tests++
> 2/7 Test #2: gu_tests++ ...   Passed1.88 sec
> Start 3: check_gcomm
> 3/7 Test #3: check_gcomm ..   Passed1.23 sec
> Start 4: gcache_tests
> 4/7 Test #4: gcache_tests .   Passed0.04 sec
> Start 5: gcs_tests
> 5/7 Test #5: gcs_tests    Passed0.13 sec
> Start 6: galera_check
> 6/7 Test #6: galera_check .***Failed4.99 sec
> Running suite(s): DataSet
> 100%: Checks: 2, Failures: 0, Errors: 0
> Running suite(s): KeySet
> 100%: Checks: 3, Failures: 0, Errors: 0
> Running suite(s): WriteSet
> 100%: Checks: 5, Failures: 0, Errors: 0
> Running suite(s): write_set
> 100%: Checks: 8, Failures: 0, Errors: 0
> Running suite(s): trx_handle
> 100%: Checks: 2, Failures: 0, Errors: 0
> Running suite(s): service_thd
> 100%: Checks: 3, Failures: 0, Errors: 0
> Running suite(s): ist
> 100%: Checks: 6, Failures: 0, Errors: 0
> Running suite(s): saved_state
> 100%: Checks: 3, Failures: 0, Errors: 0
> Running suite(s): Defaults
> 0%: Checks: 1, Failures: 0, Errors: 1
> ./galera/tests/defaults_check.cpp:283:E:defaults:defaults:0: (after this 
> point) Received signal 4 (Illegal instruction)
> Total tests failed: 1
> 
> Start 7: wsrep_test
> 7/7 Test #7: wsrep_test ...   Passed0.01 sec
> 
> 86% tests passed, 1 tests failed out of 7
> 
> Total Test time (real) =  10.20 sec
> 
> The following tests FAILED:
> 6 - galera_check (Failed)
> Errors while running CTest
> make[2]: *** [Makefile:94: test] Error 8
> make[2]: Leaving directory '/<>/obj-arm-linux-gnueabi'
> dh_auto_test: error: cd obj-arm-linux-gnueabi && make -j1 test 
> ARGS\+=--verbose ARGS\+=-j1 ARGS=--output-on-failure returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/galera-3_25.3.37-1_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069534: pycryptodome: FTBFS on armel: ld: /usr/lib/gcc/arm-linux-gnueabi/13/libasan.so: undefined reference to `__atomic_compare_exchange_8'

[Lucas Nussbaum]

Source: pycryptodome
Version: 3.20.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/src/test'
> [  3%] Building C object CMakeFiles/test_mont.dir/test_mont.c.o
> [  4%] Linking C executable test_mont
> /usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/13/libasan.so: undefined 
> reference to `__atomic_compare_exchange_8'
> /usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/13/libasan.so: undefined 
> reference to `__atomic_load_8'
> /usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/13/libasan.so: undefined 
> reference to `__atomic_store_8'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/pycryptodome_3.20.0+dfsg-1_unstable-armel.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069331: marked as done (Not installable due to hardcoded pre-t64 library deps)

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 13:19:24 +
with message-id 
and subject line Bug#1069331: fixed in cegui-mk2 0.8.7+git20220615-6
has caused the Debian Bug report #1069331,
regarding Not installable due to hardcoded pre-t64 library deps
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.)


-- 
1069331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcegui-mk2-dev
Version: 0.8.7+git20220615-5.1+b5
Severity: grave

Unsatisfied dependencies:
 libcegui-mk2-dev : Depends: libxerces-c3.2 but it is not installable

It should be changed to the t64 name if it's really needed.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libcegui-mk2-dev depends on:
ii  libc6  2.37-18
pn  libcegui-mk2-0.8.7 
pn  libcegui-mk2-0.8.7t64  
pn  libdevil-dev   
pn  libfreeimage-dev   
pn  libfreetype-dev
ii  libgcc-s1  14-20240330-1
pn  libjpeg-dev
pn  liblcms2-dev   
pn  libmng-dev 
pn  libpcre2-dev   
pn  libpng-dev 
ii  libstdc++6 14-20240330-1
pn  libtiff-dev
pn  libxerces-c3.2 
pn  lua-expat-dev  
ii  zlib1g-dev [libz-dev]  1:1.3.dfsg-3.1

libcegui-mk2-dev recommends no packages.

Versions of packages libcegui-mk2-dev suggests:
pn  libcegui-mk2-doc  
--- End Message ---
--- Begin Message ---
Source: cegui-mk2
Source-Version: 0.8.7+git20220615-6
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
cegui-mk2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated cegui-mk2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 20 Apr 2024 11:43:37 +
Source: cegui-mk2
Architecture: source
Version: 0.8.7+git20220615-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Bastian Germann 
Closes: 1069331
Changes:
 cegui-mk2 (0.8.7+git20220615-6) unstable; urgency=medium
 .
   * Team upload
   * Let dev library depend on dev library (Closes: #1069331)
Checksums-Sha1:
 261ec4bbec831db3ffc06227fb2cedf019e39714 3064 cegui-mk2_0.8.7+git20220615-6.dsc
 d7f00b4f7fa008cb58378b17d74dc85b10de1d14 21104 
cegui-mk2_0.8.7+git20220615-6.debian.tar.xz
 fc581f1752c4458e37287135770bdf05aeaa9ada 12532 
cegui-mk2_0.8.7+git20220615-6_source.buildinfo
Checksums-Sha256:
 e0843c92a479f13fbeb34f6bc07536f9f118c674d96081cf8d209017f55103ab 3064 
cegui-mk2_0.8.7+git20220615-6.dsc
 d19cd7ce062fd4238eb2d4a46a5f93e03f245abe4e90129ab70cc6b1f42e8296 21104 
cegui-mk2_0.8.7+git20220615-6.debian.tar.xz
 b93a518730e09fd090fd1706213b474002526e79ad1a9f552e217d7c68ab4748 12532 
cegui-mk2_0.8.7+git20220615-6_source.buildinfo
Files:
 7745ed20c2b1ecf82619c774de4c9ac6 3064 libs optional 
cegui-mk2_0.8.7+git20220615-6.dsc
 966cd864b7fa0357eaf24a4a64e2ee76 21104 libs optional 
cegui-mk2_0.8.7+git20220615-6.debian.tar.xz
 fdc32d728f9cc1a59c5841bc2d9edf92 12532 libs optional 
cegui-mk2_0.8.7+git20220615-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYjvDcQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFDi7C/9+J49EMg8GMxsvaG7yMqXcXltgWgygNPxb
msErAbx4s3DsHsjvNm9XLU2Ov9kif+zMQQY44ssZbXmGR6BB85aI2sxXgIGSl55q
Y6xw4w5lRVEUa2LETBzkY+0Pj6+d2nlB0Odx/fd0PTLrBdcyn5YlXzEEPUs7q4T+
04m7Ro7tLzxYlzrVmBjfSWyHjFvg+19dA1fSPpDp8LKMH0X8C+7wNwGtdAACz+gb
/RQyqnss6N1HzKOzZ0gwNpU7NFRFPJR0bx0Kbju27zvbi07+Nq1GWnU6VoUBPD9O

Bug#1069532: dune-istl: FTBFS on armhf: umfpack.hh:106:27: error: cannot convert ‘long int*’ to ‘const int64_t*’ {aka ‘const long long int*’}

[Lucas Nussbaum]

Source: dune-istl
Version: 2.9.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> cd /<>/build/dune/istl/paamg/test && /usr/bin/c++ -DENABLE_MPI=1 
> -DENABLE_SUITESPARSE=1 -DENABLE_SUPERLU=1 -DHAVE_CONFIG_H 
> -DMYAMG="Dune::Amg::AMG" -I/<>/build 
> -I/<> -isystem /usr/include/suitesparse -isystem 
> /usr/include/superlu -isystem /usr/lib/arm-linux-gnueabihf/openmpi/include 
> -isystem /usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi -std=c++17 -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security  
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIE -MD -MT 
> dune/istl/paamg/test/CMakeFiles/pthreadamgtest.dir/pthreadamgtest.cc.o -MF 
> CMakeFiles/pthreadamgtest.dir/pthreadamgtest.cc.o.d -o 
> CMakeFiles/pthreadamgtest.dir/pthreadamgtest.cc.o -c 
> /<>/dune/istl/paamg/test/pthreadamgtest.cc
> In file included from /<>/dune/istl/paamg/amg.hh:17,
>  from 
> /<>/dune/istl/paamg/test/pthreadamgtest.cc:24:
> /<>/dune/istl/umfpack.hh: In instantiation of ‘static void 
> Dune::UMFPackMethodChooser::symbolic(A ...) [with A = {int, int, long 
> int*, long int*, double*, void**, double*, double*}]’:
> /<>/dune/istl/umfpack.hh:545:23:   required from ‘void 
> Dune::UMFPack::decompose() [with M = 
> Dune::BCRSMatrix >]’
> /<>/dune/istl/umfpack.hh:459:7:   required from ‘void 
> Dune::UMFPack::setMatrix(const Matrix&) [with M = 
> Dune::BCRSMatrix >; Matrix = 
> Dune::BCRSMatrix >]’
> /<>/dune/istl/umfpack.hh:270:7:   required from 
> ‘Dune::UMFPack::UMFPack(const Matrix&, int, bool) [with M = 
> Dune::BCRSMatrix >; Matrix = 
> Dune::BCRSMatrix >]’
> /<>/dune/istl/paamg/amg.hh:658:18:   required from ‘static 
> Dune::Amg::DirectSolverSelector::Solver Dune::Amg::DirectSolverSelector::umfpack>::type* 
> Dune::Amg::DirectSolverSelector::Solver Dune::Amg::DirectSolverSelector::umfpack>::create(const M&, 
> bool, bool) [with M = Dune::BCRSMatrix >; 
> Matrix = Dune::BCRSMatrix >; Vector = 
> Dune::BlockVector >; type = 
> Dune::UMFPack > >]’
> /<>/dune/istl/paamg/amg.hh:683:40:   required from ‘static 
> Dune::Amg::DirectSolverSelector::DirectSolver* 
> Dune::Amg::DirectSolverSelector::create(const Matrix&, bool, 
> bool) [with Matrix = Dune::BCRSMatrix >; 
> Vector = Dune::BlockVector >; DirectSolver = 
> Dune::UMFPack > >]’
> /<>/dune/istl/paamg/amg.hh:745:51:   required from ‘void 
> Dune::Amg::AMG::createHierarchies(C&, const 
> std::shared_ptr&, const PI&) [with C = const 
> Dune::Amg::CoarsenCriterion  1, 1> >, Dune::Amg::FirstDiagonal> >; M = 
> Dune::MatrixAdapter >, 
> Dune::BlockVector >, 
> Dune::BlockVector > >; X = 
> Dune::BlockVector >; S = 
> Dune::SeqSSOR >, 
> Dune::BlockVector >, 
> Dune::BlockVector > >; PI = 
> Dune::Amg::SequentialInformation; A = 
> std::allocator > >]’
> /<>/dune/istl/paamg/amg.hh:448:24:   required from 
> ‘Dune::Amg::AMG::AMG(const Operator&, const C&, const 
> SmootherArgs&, const PI&) [with C = 
> Dune::Amg::CoarsenCriterion  1, 1> >, Dune::Amg::FirstDiagonal> >; M = 
> Dune::MatrixAdapter >, 
> Dune::BlockVector >, 
> Dune::BlockVector > >; X = 
> Dune::BlockVector >; S = 
> Dune::SeqSSOR >, 
> Dune::BlockVector >, 
> Dune::BlockVector > >; PI = 
> Dune::Amg::SequentialInformation; A = 
> std::allocator > >; Operator = 
> Dune::MatrixAdapter >, 
> Dune::BlockVector >, 
> Dune::BlockVector > >; SmootherArgs = 
> Dune::Amg::DefaultSmootherArgs]’
> /<>/dune/istl/paamg/test/pthreadamgtest.cc:176:7:   required 
> from ‘void testAMG(int, int, int) [with int BS = 1; AMG = 
> Dune::Amg::AMG 1, 1> >, Dune::BlockVector >, 
> Dune::BlockVector > >, 
> Dune::BlockVector >, 
> Dune::SeqSSOR >, 
> Dune::BlockVector >, 
> Dune::BlockVector > > >]’
> /<>/dune/istl/paamg/test/pthreadamgtest.cc:232:19:   required 
> from here
> /<>/dune/istl/umfpack.hh:106:27: error: cannot convert ‘long 
> int*’ to ‘const int64_t*’ {aka ‘const long long int*’}
>   106 |   umfpack_dl_symbolic(args...);
>   |   ^~~~
>   |   |
>   |   long int*
> In file included from /&

Processed: found 1069399 in ruby3.1/3.1.2-8

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # i've noticed this problem before, but it is intermittent
> found 1069399 ruby3.1/3.1.2-8
Bug #1069399 [src:ruby3.1] ruby3.1: FTBFS on arm64: Errno::EADDRINUSE: Address 
already in use - listen(2)
Marked as found in versions ruby3.1/3.1.2-8.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1069399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1069531: rcs-blame: FTBFS on armhf: mktime.c:106:52: error: size of array ‘a’ is negative

[Lucas Nussbaum]

Source: rcs-blame
Version: 1.3.1-4.2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I. -I..   -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  -g -O3 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -fcommon -c mktime.c
> mktime.c: In function ‘ydhms_diff’:
> mktime.c:106:52: error: size of array ‘a’ is negative
>   106 | #define verify(name, assertion) struct name { char a[(assertion) ? 1 
> : -1]; }
>   |^
> mktime.c:170:3: note: in expansion of macro ‘verify’
>   170 |   verify (long_int_year_and_yday_are_wide_enough,
>   |   ^~
> make[4]: *** [Makefile:441: mktime.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/rcs-blame_1.3.1-4.2_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069530: mumudvb: FTBFS on armhf: unsatisfiable build-dependency: libzvbi-common (= 0.2.42-1.1) but 0.2.42-2 is to be installed

[Lucas Nussbaum]

Source: mumudvb
Version: 1.7.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 8), dvb-apps, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 8), dvb-apps, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [620 B]
> Get:5 copy:/<>/apt_archive ./ Packages [652 B]
> Fetched 1881 B in 0s (90.1 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libzvbi0 : Depends: libzvbi-common (= 0.2.42-1.1) but 0.2.42-2 is to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/mumudvb_1.7.1-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069529: tua: FTBFS on armhf: tua.c:614:24: error: conflicting types for ‘time’; have ‘time_t(long int *)’ {aka ‘long long int(long int *)’}

[Lucas Nussbaum]

Source: tua
Version: 4.3-14
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> gcc -c -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -DLIBDIR=\"/etc\" 
> -I. -I.. -I../intl -I../intl -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -Wall  tua.c
> In file included from tua.h:81,
>  from tua.c:25:
> tua.c: In function ‘main’:
> tua.c:614:24: error: conflicting types for ‘time’; have ‘time_t(long int *)’ 
> {aka ‘long long int(long int *)’}
>   614 |   extern time_t EXFUN (time, (long *));
>   |^~~~
> ansidecl.h:85:41: note: in definition of macro ‘EXFUN’
>85 | #define EXFUN(name, proto)  name proto
>   | ^~~~
> In file included from /usr/include/features.h:490,
>  from 
> /usr/include/arm-linux-gnueabihf/bits/libc-header-start.h:33,
>  from /usr/include/string.h:26,
>  from tua.h:40:
> /usr/include/time.h:86:15: note: previous declaration of ‘time’ with type 
> ‘time_t(time_t *)’ {aka ‘long long int(long long int *)’}
>86 | extern time_t __REDIRECT_NTH (time, (time_t *__timer), __time64);
>   |   ^~
> make[2]: *** [Makefile:68: tua.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/tua_4.3-14_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069527: libchdr: FTBFS on armhf: libchdr_chd.c:3001:39: error: implicit declaration of function ‘ftello64’; did you mean ‘ftello’? [-Werror=implicit-function-declaration]

[Lucas Nussbaum]

Source: libchdr
Version: 0.0~git20230918.9108f34+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> /usr/bin/cc -Dchdr_EXPORTS -I"/<>/lzma" 
> -I"/<>/obj-arm-linux-gnueabihf/include" 
> -I"/<>/include" -I"/<>/deps/lzma-22.01/include" -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -fvisibility=hidden -MD -MT CMakeFiles/chdr.dir/src/libchdr_chd.c.o -MF 
> CMakeFiles/chdr.dir/src/libchdr_chd.c.o.d -o 
> CMakeFiles/chdr.dir/src/libchdr_chd.c.o -c 
> "/<>/src/libchdr_chd.c"
> /<>/src/libchdr_chd.c: In function ‘core_stdio_fsize’:
> /<>/src/libchdr_chd.c:3001:39: error: implicit declaration of 
> function ‘ftello64’; did you mean ‘ftello’? 
> [-Werror=implicit-function-declaration]
>  3001 | #define core_stdio_ftell_impl ftello64
>   |   ^~~~
> /<>/src/libchdr_chd.c:3013:13: note: in expansion of macro 
> ‘core_stdio_ftell_impl’
>  3013 | p = core_stdio_ftell_impl(fp);
>   | ^
> /<>/src/libchdr_chd.c:3000:39: error: implicit declaration of 
> function ‘fseeko64’; did you mean ‘fseeko’? 
> [-Werror=implicit-function-declaration]
>  3000 | #define core_stdio_fseek_impl fseeko64
>   |   ^~~~
> /<>/src/libchdr_chd.c:3014:9: note: in expansion of macro 
> ‘core_stdio_fseek_impl’
>  3014 | core_stdio_fseek_impl(fp, 0, SEEK_END);
>   | ^
> [ 68%] Building C object CMakeFiles/chdr-static.dir/src/libchdr_cdrom.c.o
> [ 68%] Building C object CMakeFiles/chdr.dir/src/libchdr_flac.c.o
> /usr/bin/cc -Dchdr_EXPORTS -I"/<>/lzma" 
> -I"/<>/obj-arm-linux-gnueabihf/include" 
> -I"/<>/include" -I"/<>/deps/lzma-22.01/include" -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -fvisibility=hidden -MD -MT CMakeFiles/chdr.dir/src/libchdr_flac.c.o -MF 
> CMakeFiles/chdr.dir/src/libchdr_flac.c.o.d -o 
> CMakeFiles/chdr.dir/src/libchdr_flac.c.o -c 
> "/<>/src/libchdr_flac.c"
> /usr/bin/cc  -I"/<>/lzma" 
> -I"/<>/obj-arm-linux-gnueabihf/include" 
> -I"/<>/include" -I"/<>/deps/lzma-22.01/include" -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -MD 
> -MT CMakeFiles/chdr-static.dir/src/libchdr_cdrom.c.o -MF 
> CMakeFiles/chdr-static.dir/src/libchdr_cdrom.c.o.d -o 
> CMakeFiles/chdr-static.dir/src/libchdr_cdrom.c.o -c 
> "/<>/src/libchdr_cdrom.c"
> [ 72%] Building C object CMakeFiles/chdr.dir/src/libchdr_huffman.c.o
> /usr/bin/cc -Dchdr_EXPORTS -I"/<>/lzma" 
> -I"/<>/obj-arm-linux-gnueabihf/include" 
> -I"/<>/include" -I"/<>/deps/lzma-22.01/include" -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -fvisibility=hidden -MD -MT CMakeFiles/chdr.dir/src/libchdr_huffman.c.o -MF 
> CMakeFiles/chdr.dir/src/libchdr_huffman.c.o.d -o 
> CMakeFiles/chdr.dir/src/libchdr_huffman.c.o -c 
> "/<>/src/libchdr_huffman.c"
> [ 76%] Building C object CMakeFiles/chdr-static.dir/src/libchdr_chd.c.o
> /usr/bin/cc  -I"/<>/lzma" 
> -I"/<>/obj-arm-linux-gnueabihf/include" 
> -I"/<>/include" -I"/<>/deps/lzma-22.01/include" -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY

Bug#1069526: libevdevplus: FTBFS on armhf: InputEvent.hpp:23:39: error: ‘struct input_event’ has no member named ‘time’

[Lucas Nussbaum]

Source: libevdevplus
Version: 0.1.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -DevdevPlus_EXPORTS  -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -fPIC -MD -MT 
> CMakeFiles/evdevPlus.dir/Resource.cpp.o -MF 
> CMakeFiles/evdevPlus.dir/Resource.cpp.o.d -o 
> CMakeFiles/evdevPlus.dir/Resource.cpp.o -c /<>/Resource.cpp
> In file included from /<>/evdevPlus.hpp:17,
>  from /<>/evdevPlus.cpp:13:
> /<>/InputEvent.hpp:23:39: error: ‘struct input_event’ has no 
> member named ‘time’
>23 | timeval  = event.time;
>   |   ^~~~
> /<>/InputEvent.hpp: In constructor 
> ‘evdevPlus::InputEvent::InputEvent(uint16_t, uint16_t, uint16_t, timeval*)’:
> /<>/InputEvent.hpp:40:47: error: ‘struct input_event’ has no 
> member named ‘time’
>40 | memcpy(, time, 
> sizeof(timeval));
>   |   ^~~~
> In file included from /<>/evdevPlus.hpp:17,
>  from /<>/Resource.cpp:13:
> /<>/InputEvent.hpp:23:39: error: ‘struct input_event’ has no 
> member named ‘time’
>23 | timeval  = event.time;
>   |   ^~~~
> /<>/InputEvent.hpp: In constructor 
> ‘evdevPlus::InputEvent::InputEvent(uint16_t, uint16_t, uint16_t, timeval*)’:
> /<>/InputEvent.hpp:40:47: error: ‘struct input_event’ has no 
> member named ‘time’
>40 | memcpy(, time, 
> sizeof(timeval));
>   |   ^~~~
> In file included from /<>/evdevPlus.hpp:17,
>  from /<>/evdevPlus.cpp:13:
> /<>/InputEvent.hpp:23:39: error: ‘struct input_event’ has no 
> member named ‘time’
>23 | timeval  = event.time;
>   |   ^~~~
> /<>/InputEvent.hpp: In constructor 
> ‘evdevPlus::InputEvent::InputEvent(uint16_t, uint16_t, uint16_t, timeval*)’:
> /<>/InputEvent.hpp:40:47: error: ‘struct input_event’ has no 
> member named ‘time’
>40 | memcpy(, time, 
> sizeof(timeval));
>   |   ^~~~
> In file included from /<>/evdevPlus.hpp:17,
>  from /<>/Resource.cpp:13:
> /<>/InputEvent.hpp:23:39: error: ‘struct input_event’ has no 
> member named ‘time’
>23 | timeval  = event.time;
>   |   ^~~~
> /<>/InputEvent.hpp: In constructor 
> ‘evdevPlus::InputEvent::InputEvent(uint16_t, uint16_t, uint16_t, timeval*)’:
> /<>/InputEvent.hpp:40:47: error: ‘struct input_event’ has no 
> member named ‘time’
>40 | memcpy(, time, 
> sizeof(timeval));
>   |   ^~~~
> make[3]: *** [CMakeFiles/evdevPlus.dir/build.make:79: 
> CMakeFiles/evdevPlus.dir/evdevPlus.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libevdevplus_0.1.1-2_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069525: libnginx-mod-http-srcache-filter: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25

[Lucas Nussbaum]

Source: libnginx-mod-http-srcache-filter
Version: 0.33-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/usr/share/nginx/src'
> cc -c -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I src/core -I src/event -I 
> src/event/modules -I src/os/unix -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk -I 
> /<>/obj-arm-linux-gnueabihf -I src/http -I src/http/modules -I 
> src/http/v2 -I /usr/share/nginx-ndk/src/src -I /usr/share/nginx-ndk/src/src 
> -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk \
>   -o 
> /<>/obj-arm-linux-gnueabihf/addon/src/ngx_http_srcache_filter_module.o
>  \
>   /<>/./src/ngx_http_srcache_filter_module.c
> cc -c -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I src/core -I src/event -I 
> src/event/modules -I src/os/unix -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk -I 
> /<>/obj-arm-linux-gnueabihf -I src/http -I src/http/modules -I 
> src/http/v2 -I /usr/share/nginx-ndk/src/src -I /usr/share/nginx-ndk/src/src 
> -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk \
>   -o 
> /<>/obj-arm-linux-gnueabihf/addon/src/ngx_http_srcache_util.o \
>   /<>/./src/ngx_http_srcache_util.c
> cc -c -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I src/core -I src/event -I 
> src/event/modules -I src/os/unix -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk -I 
> /<>/obj-arm-linux-gnueabihf -I src/http -I src/http/modules -I 
> src/http/v2 -I /usr/share/nginx-ndk/src/src -I /usr/share/nginx-ndk/src/src 
> -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk \
>   -o 
> /<>/obj-arm-linux-gnueabihf/addon/src/ngx_http_srcache_var.o \
>   /<>/./src/ngx_http_srcache_var.c
> cc -c -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I src/core -I src/event -I 
> src/event/modules -I src/os/unix -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk -I 
> /<>/obj-arm-linux-gnueabihf -I src/http -I src/http/modules -I 
> src/http/v2 -I /usr/share/nginx-ndk/src/src -I /usr/share/nginx-ndk/src/src 
> -I /usr/share/nginx-ndk/src/objs -I 
> /<>/obj-arm-linux-gnueabihf/addon/ndk \
>   -o 
> /<>/obj-arm-linux-gnueabihf/addon/src/ngx_http_srcache_store.o \
>   /<>/./src/ngx_http_srcache_store.c
> cc -c -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I src/core -I src/event -I 
> src/event/modules -I src/os/unix -

Bug#1069520: sbcl: FTBFS on armhf: make[1]: *** [debian/rules:53: override_dh_auto_build] Error 1

[Lucas Nussbaum]

Source: sbcl
Version: 2:2.3.7-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/tools-for-build'
> cc -I../src/runtime -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -marm 
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro  grovel-headers.c  -ldl -Wl,-no-as-needed 
> -lzstd -o grovel-headers
> make[2]: Leaving directory '/<>/tools-for-build'
> 13.75user 0.96system 0:14.73elapsed 99%CPU (0avgtext+0avgdata 
> 54616maxresident)k
> 0inputs+48376outputs (0major+228023minor)pagefaults 0swaps
> make-host-2.sh: 2: set: can't access tty; job control turned off
> //entering make-host-2.sh
> //running cross-compiler to create target object files
> This is SBCL 2.3.7.debian, an implementation of ANSI Common Lisp.
> More information about SBCL is available at <http://www.sbcl.org/>.
> 
> SBCL is free software, provided as is, with absolutely no warranty.
> It is mostly in the public domain; some portions are provided under
> BSD-style licenses.  See the CREDITS and COPYING files in the
> distribution for more information.
> * T
> * ; Installed READ interceptor
> ; Float-ops cache prefill: 4315 entries
> ;; loading #P"/<>/tests/type.before-xc.lisp"
> ;; loading #P"/<>/tests/info.before-xc.lisp"
> ;; loading #P"/<>/tests/vm.before-xc.lisp"
> ctype cache metrics:  Count LF SeekHit maxPSL  Mask
>   FUN :1137  55.5% 57FF
>   List: 737  72.0% 83FF
>   Set : 198  38.7% 51FF
>   UNION   : 177  69.1% 7 FF
>   VALUES  : 175  68.4% 5 FF
>   ARRAY   : 136  53.1% 4 FF
>   NUMERIC : 123  48.0% 3 FF
>   Key-Info:  85  66.4% 4 7F
>   CONSTANT:  53  41.4% 5 7F
>   Key-Info-Set:  38  59.4% 3 3F
>   INTERSECTION:  31  48.4% 2 3F
>   UNKNOWN :  26  40.6% 3 3F
>   MEMBER  :  21  32.8% 2 3F
>   HAIRY   :  13  20.3% 2 3F
>   NEGATION:  12  18.8% 3 3F
>   EQL :   6 NIL  %
>   CHARACTER-SET   :   4   6.3% 1 3F
>   CONS:   2   3.1% 1 3F
>   ALIEN-TYPE  :   1   1.6% 1 3F
>   MEMBER/EQ   :   0   0.0% 0 3F
>   FUN-DESIGNATOR  :   0   0.0% 0 3F
>   Total   :2975
> Alien:
>   POINTER :   1   1.6% 1 3F
>   INTEGER :   0   0.0% 0 3F
>   BOOLEAN :   0   0.0% 0 3F
>   C-STRING:   0   0.0% 0 3F
>   ARRAY   :   0   0.0% 0 3F
>   FUN :   0   0.0% 0 3F
>   VALUES  :   0   0.0% 0 3F
>   ENUM:   0   0.0% 0 3F
>   UNION   :   0   0.0% 0 3F
>   STRUCT  :   0   0.0% 0 3F
>   Total   :   1
> [  1/301] src/code/show(0.028 sec)
> [  2/301] src/compiler/early-constantp (0.016 sec)
> [  3/301] src/compiler/vop-existsp (0.032 sec)
> [  4/301] src/code/defsetfs(0.268 sec)
> [  5/301] src/code/cl-specials (0.028 sec)
> [  6/301] src/code/primordial-extensions   (0.228 sec)
> [  7/301] src/code/cold-init-helper-macros (0.044 sec)
> [  8/301] src/code/backq   (0.16 sec)
> [  9/301] src/code/globals (0.024 sec)
> [ 10/301] src/code/cmacros (0.052 sec)
> [ 11/301] src/code/uncross (0.004 sec)
> [ 12/301] src/code/defbangtype (0.012 sec)
> [ 13/301] src/code/early-constants

Bug#1069524: rl-renderpm: FTBFS on armhf: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

[Lucas Nussbaum]

Source: rl-renderpm
Version: 4.0.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f src/libart_lgpl/art_config.h # this file is generated
> dh_auto_clean
> I: pybuild base:311: python3.12 setup.py clean 
> ===
> Attempting build of _renderPM
> extension from '/<>/src'
> ===
> will use package libart 2.3.12
> installing with freetype version 2.13.2
> FT_LIB_DIR=[] FT_INC_DIR=['/usr/include', '/usr/include/freetype2']
> running clean
> removing '/<>/.pybuild/cpython3_3.12_rl-renderpm/build' (and 
> everything under it)
> 'build/bdist.linux-armv7l' does not exist -- can't clean it
> 'build/scripts-3.12' does not exist -- can't clean it
> I: pybuild base:311: python3.11 setup.py clean 
> ===
> Attempting build of _renderPM
> extension from '/<>/src'
> ===
> will use package libart 2.3.12
> installing with freetype version 2.13.2
> FT_LIB_DIR=[] FT_INC_DIR=['/usr/include', '/usr/include/freetype2']
> running clean
> removing '/<>/.pybuild/cpython3_3.11_rl-renderpm/build' (and 
> everything under it)
> 'build/bdist.linux-armv7l' does not exist -- can't clean it
> 'build/scripts-3.11' does not exist -- can't clean it
> make[1]: Leaving directory '/<>'
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using options from 
> rl-renderpm-4.0.3/debian/source/options: 
> --extend-diff-ignore=^[^/]*[.]egg-info/
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building rl-renderpm using existing 
> ./rl-renderpm_4.0.3.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  rl-renderpm-4.0.3/src/libart_lgpl/art_config.h
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/rl-renderpm_4.0.3-2.diff.sGNO_O
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2024-04-20T02:35:17Z


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/rl-renderpm_4.0.3-2_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069523: libss7: FTBFS on armhf: ss7.c:654:56: error: format ‘%li’ expects argument of type ‘long int’, but argument 3 has type ‘long long int’ [-Werror=format=]

[Lucas Nussbaum]

Source: libss7
Version: 2.0.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -fPIC -O2  -MD -MT 
> ss7.o -MF .ss7.o.d -MP -c -o ss7.o ss7.c
> ss7.c: In function ‘ss7_show_linkset’:
> ss7.c:654:56: error: format ‘%li’ expects argument of type ‘long int’, but 
> argument 3 has type ‘long long int’ [-Werror=format=]
>   654 | sprintf(p, "(%lis)%c", 
> ss7->ss7_sched[ss7->links[i]->mtp3_timer[x]].when.tv_sec - time(NULL),
>   |  ~~^   
> ~
>   ||  
>   |
>   |long int   
>   long long int
>   |  %lli
> isup.c: In function ‘isup_show_calls’:
> isup.c:5250:88: error: format ‘%li’ expects argument of type ‘long int’, but 
> argument 6 has type ‘long long int’ [-Werror=format=]
>  5250 | buf_used = ss7_snprintf(buf, 
> buf_used, buf_size, "%s(%li) ", isup_timer2str(x),  
> ss7->ss7_sched[c->timer[x]].when.tv_sec - time(NULL));
>   |   
>~~^ 
> 
>   |   
>  |
>  |
>   |   
>  long int 
>  long long int
>   |   
>%lli
> cc1: all warnings being treated as errors
> make[1]: *** [Makefile:177: ss7.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libss7_2.0.0-3_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069522: haskell-yesod-bin: FTBFS on armhf: unsatisfiable build-dependencies

[Lucas Nussbaum]

Source: haskell-yesod-bin
Version: 1.6.2.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: haskell-devscripts (>= 0.13), cdbs, debhelper (>= 10), 
> ghc, libghc-aeson-dev, libghc-conduit-dev (>= 1.3), libghc-conduit-extra-dev 
> (>= 1.3), libghc-data-default-class-dev, libghc-file-embed-dev, 
> libghc-fsnotify-dev (>= 0.0), libghc-http-client-dev (>= 0.4.7), 
> libghc-http-client-tls-dev, libghc-http-reverse-proxy-dev (>= 0.4), 
> libghc-http-types-dev (>= 0.7), libghc-network-dev (>= 2.5), 
> libghc-optparse-applicative-dev (>= 0.11), libghc-project-template-dev (>= 
> 0.1.1), libghc-say-dev, libghc-split-dev (>= 0.2), libghc-split-dev (<< 0.3), 
> libghc-streaming-commons-dev, libghc-tar-dev (<< 0.6), libghc-tar-dev (>= 
> 0.4), libghc-transformers-compat-dev, libghc-unliftio-dev, 
> libghc-unordered-containers-dev, libghc-wai-dev (>= 2.0), 
> libghc-wai-extra-dev, libghc-warp-dev (>= 1.3.7.5), libghc-warp-tls-dev (>= 
> 3.0.1), libghc-yaml-dev (>= 0.8), libghc-yaml-dev (<< 0.12), libghc-zlib-dev 
> (>= 0.5), build-essential, fakeroot
> Filtered Build-Depends: haskell-devscripts (>= 0.13), cdbs, debhelper (>= 
> 10), ghc, libghc-aeson-dev, libghc-conduit-dev (>= 1.3), 
> libghc-conduit-extra-dev (>= 1.3), libghc-data-default-class-dev, 
> libghc-file-embed-dev, libghc-fsnotify-dev (>= 0.0), libghc-http-client-dev 
> (>= 0.4.7), libghc-http-client-tls-dev, libghc-http-reverse-proxy-dev (>= 
> 0.4), libghc-http-types-dev (>= 0.7), libghc-network-dev (>= 2.5), 
> libghc-optparse-applicative-dev (>= 0.11), libghc-project-template-dev (>= 
> 0.1.1), libghc-say-dev, libghc-split-dev (>= 0.2), libghc-split-dev (<< 0.3), 
> libghc-streaming-commons-dev, libghc-tar-dev (<< 0.6), libghc-tar-dev (>= 
> 0.4), libghc-transformers-compat-dev, libghc-unliftio-dev, 
> libghc-unordered-containers-dev, libghc-wai-dev (>= 2.0), 
> libghc-wai-extra-dev, libghc-warp-dev (>= 1.3.7.5), libghc-warp-tls-dev (>= 
> 3.0.1), libghc-yaml-dev (>= 0.8), libghc-yaml-dev (<< 0.12), libghc-zlib-dev 
> (>= 0.5), build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1492 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1522 B]
> Fetched 3629 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-http-client-tls-dev : Depends: libghc-base-dev-4.17.2.0-38dbb but it 
> is not installable
>   Depends: libghc-bytestring-dev-0.11.5.2-302b4 
> but it is not installable
>   Depends: 
> libghc-case-insensitive-dev-1.2.1.0-366b1 but it is not installable
>   Depends: libghc-connection-dev-0.3.1-6b46e
>   Depends: libghc-containers-dev-0.6.7-e92e7 but 
> it is not installable
>   Depends: libghc-cryptonite-dev-0.30-d9a59 but 
> it is not installable
>   Depends: 
> libghc-data-default-class-dev-0.1.2.0-65f66 but it is not installable
>   Depends: libghc-http-client-dev-0.7.14-1da8e 
> but it is not installable
>   Depends: libghc-http-types-dev-0.12.3-41c60 but 
> it is not installable
>   Depends: lib

Bug#1069521: patat: FTBFS on armhf: unsatisfiable build-dependencies

[Lucas Nussbaum]

Source: patat
Version: 0.11.0.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), ghc, libghc-aeson-dev (>= 
> 2.0), libghc-aeson-dev (<< 2.3), libghc-ansi-terminal-dev (>= 0.6), 
> libghc-ansi-terminal-dev (<< 1.1), libghc-ansi-wl-pprint-dev (>= 0.6), 
> libghc-ansi-wl-pprint-dev (<< 1.1), libghc-async-dev (>= 2.2), 
> libghc-async-dev (<< 2.3), libghc-base64-bytestring-dev (>= 1.0), 
> libghc-base64-bytestring-dev (<< 1.3), libghc-colour-dev (>= 2.3), 
> libghc-colour-dev (<< 2.4), libghc-mtl-dev (>= 2.2), libghc-mtl-dev (<< 2.4), 
> libghc-optparse-applicative-dev (>= 0.16), libghc-optparse-applicative-dev 
> (<< 0.19), libghc-pandoc-dev (>= 3.0), libghc-pandoc-dev (<< 3.2), 
> libghc-pandoc-types-dev (>= 1.23), libghc-pandoc-types-dev (<< 1.24), 
> libghc-skylighting-dev (>= 0.10), libghc-skylighting-dev (<< 0.15), 
> libghc-terminal-size-dev (>= 0.3), libghc-terminal-size-dev (<< 0.4), 
> libghc-text-dev (>= 1.2), libghc-text-dev (<< 2.2), 
> libghc-unordered-containers-dev (>= 0.2), libghc-unordered-containers-dev (<< 
> 0.3), libghc-yaml-dev (>= 0.8), libghc-yaml-dev (<< 0.12), libghc-wcwidth-dev 
> (>= 0.0), libghc-wcwidth-dev (<< 0.1), libghc-tasty-dev (>= 1.2), 
> libghc-tasty-dev (<< 1.6), libghc-tasty-hunit-dev (>= 0.10), 
> libghc-tasty-hunit-dev (<< 0.11), libghc-tasty-quickcheck-dev (>= 0.10), 
> libghc-tasty-quickcheck-dev (<< 0.11), libghc-quickcheck2-dev (>= 2.8), 
> libghc-quickcheck2-dev (<< 2.15), pandoc-data, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), ghc, libghc-aeson-dev (>= 
> 2.0), libghc-aeson-dev (<< 2.3), libghc-ansi-terminal-dev (>= 0.6), 
> libghc-ansi-terminal-dev (<< 1.1), libghc-ansi-wl-pprint-dev (>= 0.6), 
> libghc-ansi-wl-pprint-dev (<< 1.1), libghc-async-dev (>= 2.2), 
> libghc-async-dev (<< 2.3), libghc-base64-bytestring-dev (>= 1.0), 
> libghc-base64-bytestring-dev (<< 1.3), libghc-colour-dev (>= 2.3), 
> libghc-colour-dev (<< 2.4), libghc-mtl-dev (>= 2.2), libghc-mtl-dev (<< 2.4), 
> libghc-optparse-applicative-dev (>= 0.16), libghc-optparse-applicative-dev 
> (<< 0.19), libghc-pandoc-dev (>= 3.0), libghc-pandoc-dev (<< 3.2), 
> libghc-pandoc-types-dev (>= 1.23), libghc-pandoc-types-dev (<< 1.24), 
> libghc-skylighting-dev (>= 0.10), libghc-skylighting-dev (<< 0.15), 
> libghc-terminal-size-dev (>= 0.3), libghc-terminal-size-dev (<< 0.4), 
> libghc-text-dev (>= 1.2), libghc-text-dev (<< 2.2), 
> libghc-unordered-containers-dev (>= 0.2), libghc-unordered-containers-dev (<< 
> 0.3), libghc-yaml-dev (>= 0.8), libghc-yaml-dev (<< 0.12), libghc-wcwidth-dev 
> (>= 0.0), libghc-wcwidth-dev (<< 0.1), libghc-tasty-dev (>= 1.2), 
> libghc-tasty-dev (<< 1.6), libghc-tasty-hunit-dev (>= 0.10), 
> libghc-tasty-hunit-dev (<< 0.11), libghc-tasty-quickcheck-dev (>= 0.10), 
> libghc-tasty-quickcheck-dev (<< 0.11), libghc-quickcheck2-dev (>= 2.8), 
> libghc-quickcheck2-dev (<< 2.15), pandoc-data, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1936 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1966 B]
> Fetched 4517 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been cr

Bug#1069519: python-udatetime: FTBFS on armhf: ValueError: year 104781 is out of range

[Lucas Nussbaum]

Source: python-udatetime
Version: 0.0.17-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py config 
> running config
> I: pybuild base:311: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:311: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_udatetime/build/udatetime
> copying udatetime/_pure.py -> 
> /<>/.pybuild/cpython3_3.12_udatetime/build/udatetime
> copying udatetime/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_udatetime/build/udatetime
> running egg_info
> creating udatetime.egg-info
> writing udatetime.egg-info/PKG-INFO
> writing dependency_links to udatetime.egg-info/dependency_links.txt
> writing top-level names to udatetime.egg-info/top_level.txt
> writing manifest file 'udatetime.egg-info/SOURCES.txt'
> reading manifest file 'udatetime.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'udatetime.egg-info/SOURCES.txt'
> running build_ext
> building 'udatetime.rfc3339' extension
> creating build
> creating build/temp.linux-armv7l-cpython-312
> creating build/temp.linux-armv7l-cpython-312/src
> arm-linux-gnueabihf-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 
> -Wall -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -D_PYTHON3=1 -I/usr/include/python3.12 -c ./src/rfc3339.c -o 
> build/temp.linux-armv7l-cpython-312/./src/rfc3339.o -Ofast -std=c99
> ./src/rfc3339.c: In function ‘_gettime’:
> ./src/rfc3339.c:104:5: warning: ‘ftime’ is deprecated: Use gettimeofday or 
> clock_gettime instead [-Wdeprecated-declarations]
>   104 | ftime();
>   | ^
> In file included from ./src/rfc3339.c:16:
> /usr/include/arm-linux-gnueabihf/sys/timeb.h:29:12: note: declared here
>29 | extern int ftime (struct timeb *__timebuf)
>   |^
> ./src/rfc3339.c: At top level:
> ./src/rfc3339.c:511:21: warning: ‘CAPI’ initialized and declared ‘extern’
>   511 | extern RFC3999_CAPI CAPI = {
>   | ^~~~
> ./src/rfc3339.c: In function ‘FixedOffset_tzname’:
> ./src/rfc3339.c:585:12: warning: ‘%02d’ directive writing between 2 and 9 
> bytes into a region of size 6 [-Wformat-overflow=]
>   585 | "%c%02d:%02d",
>   |^~~~
> ./src/rfc3339.c:585:9: note: directive argument in the range [-35791394, 
> 35791394]
>   585 | "%c%02d:%02d",
>   | ^
> ./src/rfc3339.c:585:9: note: directive argument in the range [-8, 59]
> In file included from /usr/include/stdio.h:906,
>  from /usr/include/python3.12/Python.h:24,
>  from ./src/rfc3339.c:4:
> In function ‘sprintf’,
> inlined from ‘FixedOffset_tzname’ at ./src/rfc3339.c:583:5:
> /usr/include/arm-linux-gnueabihf/bits/stdio2.h:30:10: note: 
> ‘__builtin___sprintf_chk’ output between 7 and 14 bytes into a destination of 
> size 7
>30 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
>   |  ^~
>31 |   __glibc_objsize (__s), __fmt,
>   |   ~
>32 |   __va_arg_pack ());
>   |   ~
> ./src/rfc3339.c: In function ‘FixedOffset_repr’:
> ./src/rfc3339.c:585:12: warning: ‘%02d’ directive writing between 2 and 9 
> bytes into a region of size 6 [-Wformat-overflow=]
>   585 | "%c%02d:%02d",
>   |^~~~
> In function ‘FixedOffset_tzname’,
> inlined from ‘FixedOffset_repr’ at ./src/rfc3339.c:603:12:
> ./src/rfc3339.c:585:9: note: directive argument in the range [-35791394, 
> 35791394]
>   585 | "%c%02d:%02d",
>   | ^
> ./src/rfc3339.c:585:9: note: directive argument in the range [-8, 59]
> In function ‘sprintf’,
> inlined fr

Bug#1069516: abinit: FTBFS on armhf: tests fail

[Lucas Nussbaum]

Source: abinit
Version: 9.10.4-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> (cd tests; ./runtests.py -t 1800 fast)
> stty: 'standard input': Inappropriate ioctl for device
> /<>/tests/pymods/testsuite.py:400: UserWarning: [t00.abo] 
> Something went wrong with this test:
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/<>/tests/Test_suite/fast_t00/t00.abo'
> 
>   warnings.warn(('[{}] Something went wrong with this test:\n'
> /<>/tests/pymods/testsuite.py:400: UserWarning: [t01.abo] 
> Something went wrong with this test:
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/<>/tests/Test_suite/fast_t01/t01.abo'
> 
>   warnings.warn(('[{}] Something went wrong with this test:\n'
> /<>/tests/pymods/testsuite.py:400: UserWarning: [t02.abo] 
> Something went wrong with this test:
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/<>/tests/Test_suite/fast_t02/t02.abo'
> 
>   warnings.warn(('[{}] Something went wrong with this test:\n'
> Running on ip-10-84-234-172 -- system Linux -- ncpus 4 -- Python 
> 3.11.9 -- runtests.py-0.6.0
> Regenerating database...
> Saving database to /<>/tests/test_suite.cpkl
> Running 26 test(s) with MPI_procs: 1, py_nprocs: 1
> [TIP] runtests.py is using 1 CPUs but your architecture has 4 CPUs 
> (including Hyper-Threading)
> You may want to use python processes to speed up the execution
> Use `runtests -jNUM` to run with NUM processes
> Command   /<>/src/98_main/abinit 
> /<>/tests/Test_suite/fast_t00/t00.abi> 
> /<>/tests/Test_suite/fast_t00/t00.stdout   2> 
> /<>/tests/Test_suite/fast_t00/t00.stderr 
>  returned exit_code: 1
> 
> [fast][t00][np=1][run_etime: 0.04 s]: Internal error:
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/<>/tests/Test_suite/fast_t00/t00.abo' [file=t00.abo]
> [fast][t00][np=1] Test was not expected to fail but subprocesses 
> returned retcode: 1
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-172:3674301] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> [ip-10-84-234-172:3674300] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to 
> start a daemon on the local node in file 
> ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 716
> [ip-10-84-234-172:3674300] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to 
> start a daemon on the local node in file 
> ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172
> --
> It looks like orte_init failed for some reason; your parallel process is
> likely to abort.  There are many reasons that a parallel process can
> fail during orte_init; some of which are due to configuration or
> environment problems.  This failure appears to be an internal failure;
> here's some additional information (which may only be relevant to an
> Open MPI developer):
> 
>   orte_ess_init failed
>   --> Returned value Unable to start a daemon on the local node (-127) 
> instead of ORTE_SUCCESS
> --
> --
> It looks like MPI_INIT failed for some reason; your parallel process is
> likely to abort.  There are many reasons that a parallel process can
> fail during MPI_INIT; some of which are due to configuration or environment
> problems.  This failure appears to be an internal failure; here's some
> additional information (which may only be relevant to an Open MPI
> developer):
> 
>   ompi_mpi_init: ompi_rte_init failed
>   --> Returned "Unable to start a daemon on the local node" (-127) instead of 
> "Success" (0)
> --
> *** An error occurred in MPI_Init
> *** on a NULL communicator
> *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
> ***and potentially your MPI job)
> [ip-10-84-234-

Bug#1069518: projecteur: FTBFS on armhf: deviceinput.cc:697:64: error: narrowing conversion of ‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’ {aka ‘short unsigned int’} [-

[Lucas Nussbaum]

Source: projecteur
Version: 0.10-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -DCXX_COMPILER_ID=GNU -DCXX_COMPILER_VERSION=13.2.0 
> -DHAS_Qt_DBus=1 -DHAS_Qt_X11Extras=1 -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB 
> -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB 
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB 
> -I/<>/obj-arm-linux-gnueabihf/projecteur_autogen/include 
> -I/<>/src 
> -I/<>/obj-arm-linux-gnueabihf/version/projecteur -isystem 
> /usr/include/arm-linux-gnueabihf/qt5 -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtCore -isystem 
> /usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtQuick -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtQmlModels -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtQml -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtX11Extras -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtDBus -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -std=gnu++14 -Wall -Wextra -Werror -fPIC -MD -MT 
> CMakeFiles/projecteur.dir/src/devicescan.cc.o -MF 
> CMakeFiles/projecteur.dir/src/devicescan.cc.o.d -o 
> CMakeFiles/projecteur.dir/src/devicescan.cc.o -c 
> /<>/src/devicescan.cc
> /<>/src/deviceinput.cc: In member function ‘void 
> InputMapper::Impl::emitNativeKeySequence(const NativeKeySequence&)’:
> /<>/src/deviceinput.cc:697:64: error: narrowing conversion of 
> ‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’ 
> {aka ‘short unsigned int’} [-Werror=narrowing]
>   697 |   events.emplace_back(input_event{{}, ie.type, ie.code, 
> ie.value});
>   | ~~~^
> /<>/src/deviceinput.cc:697:69: error: missing initializer for 
> member ‘input_event::value’ [-Werror=missing-field-initializers]
>   697 |   events.emplace_back(input_event{{}, ie.type, ie.code, 
> ie.value});
>   | ^
> /<>/src/deviceinput.cc: In lambda function:
> /<>/src/deviceinput.cc:893:55: error: narrowing conversion of 
> ‘(int32_t)de.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’ 
> {aka ‘short unsigned int’} [-Werror=narrowing]
>   893 | struct input_event ie = {{}, de.type, de.code, de.value};
>   |~~~^
> /<>/src/deviceinput.cc:893:60: error: missing initializer for 
> member ‘input_event::value’ [-Werror=missing-field-initializers]
>   893 | struct input_event ie = {{}, de.type, de.code, de.value};
>   |^
> /<>/src/deviceinput.cc: In member function ‘void 
> InputMapper::addEvents(const KeyEvent&)’:
> /<>/src/deviceinput.cc:906:79: error: missing initializer for 
> member ‘input_event::value’ [-Werror=missing-field-initializers]
>   906 |   if (!hasLastSYN) { events.emplace_back(input_event{{}, EV_SYN, 
> SYN_REPORT, 0}); }
>   |   
> ^
> [ 44%] Building CXX object CMakeFiles/projecteur.dir/src/deviceswidget.cc.o
> /usr/bin/c++ -DCXX_COMPILER_ID=GNU -DCXX_COMPILER_VERSION=13.2.0 
> -DHAS_Qt_DBus=1 -DHAS_Qt_X11Extras=1 -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB 
> -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB 
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB 
> -I/<>/obj-arm-linux-gnueabihf/projecteur_autogen/include 
> -I/<>/src 
> -I/<>/obj-arm-linux-gnueabihf/version/projecteur -isystem 
> /usr/include/arm-linux-gnueabihf/qt5 -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtCore -isystem 
> /usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtQuick -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtQmlModels -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtQml -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem 
> /usr/include/arm-linux-gnueabihf/qt5/QtX11Extras -isyst

Bug#1069517: drogon: FTBFS on armhf: build-dependency not installable: libssl3

[Lucas Nussbaum]

Source: drogon
Version: 1.8.7+ds-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: dpkg-dev (>= 1.22.5), chrpath, cmake, debhelper-compat 
> (= 13), dh-cmake, dh-cmake-compat (= 1), doxygen, libbrotli-dev, 
> libhiredis-dev, libjsoncpp-dev, libmariadb-dev, libpq-dev, libsqlite3-dev, 
> libtrantor-dev, libyaml-cpp-dev, uuid-dev, build-essential, fakeroot
> Filtered Build-Depends: dpkg-dev (>= 1.22.5), chrpath, cmake, 
> debhelper-compat (= 13), dh-cmake, dh-cmake-compat (= 1), doxygen, 
> libbrotli-dev, libhiredis-dev, libjsoncpp-dev, libmariadb-dev, libpq-dev, 
> libsqlite3-dev, libtrantor-dev, libyaml-cpp-dev, uuid-dev, build-essential, 
> fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [830 B]
> Get:5 copy:/<>/apt_archive ./ Packages [862 B]
> Fetched 2301 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libtrantor1 : Depends: libssl3 but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/drogon_1.8.7+ds-1.1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069515: eclib: FTBFS on armhf: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: eclib
Version: 20240408-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/progs'
> Checking conics and cubics programs...
> Checking qcurves programs...
> for prog in solve_conic solve_legendre reduce_cubics list_cubics cubics; do 
> echo -n "Testing ${prog}..."; ./${prog} < ./in/${prog}.in > ${prog}.testout 
> 2>/dev/null && echo "${prog} completed" && diff ${prog}.testout 
> ./out_ntl/${prog}.out || exit $?; done
> Checking qrank programs...
> for prog in point_search indep_test; do echo -n "Testing ${prog}..."; 
> ./${prog} < ./in/${prog}.in > ${prog}.testout 2>/dev/null && echo "${prog} 
> completed" && diff ${prog}.testout ./out_ntl/${prog}.out || exit $?; done
> for prog in mwrank reduce_quartics quartic_points; do echo -n "Testing 
> ${prog}..."; ./${prog} < ./in/${prog}.in > ${prog}.testout 2>/dev/null && 
> echo "${prog} completed" && diff ${prog}.testout ./out_ntl/${prog}.out || 
> exit $?; done
> Checking g0n programs...
> rm -rf nftmp
> Testing solve_conic...Testing point_search...Testing mwrank...rm -rf snftmp
> rm -rf tcurves
> mkdir nftmp
> mkdir snftmp
> mkdir tcurves
> for prog in ecnf nfhpcurve nfhpmcurve h1first h1clist h1bsdcurisog qexp h1bsd 
> h1curve pcurve checkap moreap nfcount aplist; do echo -n "Testing 
> ${prog}..."; ./${prog} < ./in/${prog}.in > ${prog}.testout 2>/dev/null && 
> echo "${prog} completed" && diff ${prog}.testout ./out_ntl/${prog}.out || 
> exit $?; done
> Testing ecnf...solve_conic completed
> Testing solve_legendre...solve_legendre completed
> Testing reduce_cubics...reduce_cubics completed
> Testing list_cubics...list_cubics completed
> Testing cubics...cubics completed
> ecnf completed
> Testing nfhpcurve...mwrank completed
> Testing reduce_quartics...reduce_quartics completed
> Testing quartic_points...quartic_points completed
> rm -f PRIMES 1
> point_search completed
> Testing indep_test...indep_test completed
> nfhpcurve completed
> Testing nfhpmcurve...nfhpmcurve completed
> Testing h1first...h1first completed
> Testing h1clist...h1clist completed
> Testing h1bsdcurisog...h1bsdcurisog completed
> 4c4
> < 37 a   1 [0,0,1,-1,0]   1   1   1   
> 5.9869172924639192596640199589  0.30599977383405230182048368335 
> 0.054082399688402358860997571.0001
> ---
> > 37 a   1 [0,0,1,-1,0]   1   1   1   
> > 5.9869172924639192596640199589  0.30599977383405230182048368337 
> > 0.054082399688402358860997571.0001
> 31c31
> <389 a   1 [0,1,1,-2,0]   2   1   1   
> 4.9804251217101101506427155839  0.75931650028842677023019260781 
> 0.15246017794314375162432475705 0.99989
> ---
> >389 a   1 [0,1,1,-2,0]   2   1   1   
> > 4.9804251217101101506427155839  0.75931650028842677023019260774 
> > 0.15246017794314375162432475705 0.9998
> make[3]: *** [Makefile:1044: check_g0n] Error 1
> make[3]: Leaving directory '/<>/progs'
> make[2]: *** [Makefile:1052: check] Error 2
> make[2]: Leaving directory '/<>/progs'
> make[1]: *** [Makefile:468: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/eclib_20240408-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069514: trophy: FTBFS on armhf: unsatisfiable dependencies

[Lucas Nussbaum]

Source: trophy
Version: 2.0.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), libclanlib-dev (>= 
> 1.0~svn3827-11~), libgl1-mesa-dev, libglu1-mesa-dev, pkg-config, zlib1g-dev, 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), libclanlib-dev (>= 
> 1.0~svn3827-11~), libgl1-mesa-dev, libglu1-mesa-dev, pkg-config, zlib1g-dev, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [713 B]
> Get:5 copy:/<>/apt_archive ./ Packages [745 B]
> Fetched 2067 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libasound2t64 : Breaks: libasound2 (< 1.2.11-1) but 1.2.10-3 is to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/trophy_2.0.4-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069513: isochron: FTBFS on armhf: src/common.c:91:43: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘__time64_t’ {aka ‘long long int’} [-Werror=format=]

[Lucas Nussbaum]

Source: isochron
Version: 0.9~rc4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> cc -DVERSION=\"v0.9-rc4\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_TX_SWHW -Wall -Wextra 
> -Werror -Wno-error=sign-compare -Wno-error=missing-field-initializers 
> -Wno-unused-parameter -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -MMD -c 
> src/isochron.c -o src/isochron.o
> src/common.c: In function ‘ns_sprintf’:
> src/common.c:91:43: error: format ‘%ld’ expects argument of type ‘long int’, 
> but argument 4 has type ‘__time64_t’ {aka ‘long long int’} [-Werror=format=]
>91 | snprintf(buf, TIMESPEC_BUFSIZ, "%ld.%09ld", ts.tv_sec, 
> ts.tv_nsec);
>   | ~~^ ~
>   |   |   |
>   |   long int__time64_t {aka 
> long long int}
>   | %lld
> cc -DVERSION=\"v0.9-rc4\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_TX_SWHW -Wall -Wextra 
> -Werror -Wno-error=sign-compare -Wno-error=missing-field-initializers 
> -Wno-unused-parameter -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -MMD -c src/log.c 
> -o src/log.o
> cc1: all warnings being treated as errors
> make[1]: *** [Makefile:94: src/common.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/isochron_0.9~rc4-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069510: elpa: FTBFS on armhf: make[5]: *** [Makefile:84371: test-suite.log] Error 1

[Lucas Nussbaum]

Source: elpa
Version: 2022.11.001-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>/build'
> FAIL: 
> validate_c_version_complex_double_eigenvalues_1stage_analytic_explicit_default.sh
> FAIL: validate_c_version_complex_double_eigenvalues_1stage_analytic_default.sh
> FAIL: 
> validate_c_version_complex_double_eigenvalues_2stage_default_kernel_analytic_default.sh
> FAIL: 
> validate_c_version_real_double_eigenvalues_1stage_analytic_explicit_default.sh
> FAIL: validate_c_version_real_double_eigenvalues_1stage_analytic_default.sh
> FAIL: 
> validate_c_version_real_double_eigenvalues_2stage_default_kernel_analytic_default.sh
> FAIL: 
> validate_c_version_complex_double_cholesky_1stage_random_explicit_default.sh
> FAIL: validate_c_version_complex_double_cholesky_1stage_random_default.sh
> FAIL: 
> validate_c_version_real_double_cholesky_1stage_random_explicit_default.sh
> FAIL: validate_c_version_real_double_cholesky_1stage_random_default.sh
> FAIL: 
> validate_c_version_complex_double_eigenvectors_1stage_random_explicit_default.sh
> FAIL: validate_c_version_complex_double_eigenvectors_1stage_random_default.sh
> FAIL: 
> validate_c_version_complex_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
> FAIL: 
> validate_c_version_complex_double_eigenvectors_2stage_default_kernel_random_default.sh
> FAIL: 
> validate_c_version_real_double_eigenvectors_1stage_random_explicit_default.sh
> FAIL: validate_c_version_real_double_eigenvectors_1stage_random_default.sh
> FAIL: 
> validate_c_version_real_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
> FAIL: 
> validate_c_version_real_double_eigenvectors_2stage_default_kernel_random_default.sh
> FAIL: validate_c_version_complex_double_generalized_1stage_random_default.sh
> FAIL: validate_c_version_real_double_generalized_1stage_random_default.sh
> FAIL: 
> validate_c_version_complex_double_generalized_decomp_1stage_random_default.sh
> FAIL: 
> validate_c_version_real_double_generalized_decomp_1stage_random_default.sh
> FAIL: 
> validate_c_version_complex_double_hermitian_multiply_1stage_random_explicit_default.sh
> FAIL: 
> validate_c_version_complex_double_hermitian_multiply_1stage_random_default.sh
> FAIL: 
> validate_c_version_real_double_hermitian_multiply_1stage_random_explicit_default.sh
> FAIL: 
> validate_c_version_real_double_hermitian_multiply_1stage_random_default.sh
> FAIL: 
> validate_c_version_real_double_solve_tridiagonal_1stage_toeplitz_default.sh
> FAIL: 
> validate_cpp_version_complex_double_eigenvalues_1stage_analytic_default.sh
> FAIL: 
> validate_cpp_version_complex_double_eigenvalues_2stage_default_kernel_analytic_default.sh
> FAIL: validate_cpp_version_real_double_eigenvalues_1stage_analytic_default.sh
> FAIL: 
> validate_cpp_version_real_double_eigenvalues_2stage_default_kernel_analytic_default.sh
> FAIL: 
> validate_cpp_version_complex_double_cholesky_1stage_random_explicit_default.sh
> FAIL: validate_cpp_version_complex_double_cholesky_1stage_random_default.sh
> FAIL: 
> validate_cpp_version_real_double_cholesky_1stage_random_explicit_default.sh
> FAIL: validate_cpp_version_real_double_cholesky_1stage_random_default.sh
> FAIL: 
> validate_cpp_version_complex_double_eigenvectors_1stage_random_explicit_default.sh
> FAIL: 
> validate_cpp_version_complex_double_eigenvectors_1stage_random_default.sh
> FAIL: 
> validate_cpp_version_complex_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
> FAIL: 
> validate_cpp_version_complex_double_eigenvectors_2stage_default_kernel_random_default.sh
> FAIL: 
> validate_cpp_version_real_double_eigenvectors_1stage_random_explicit_default.sh
> FAIL: validate_cpp_version_real_double_eigenvectors_1stage_random_default.sh
> FAIL: 
> validate_cpp_version_real_double_eigenvectors_2stage_default_kernel_random_explicit_default.sh
> FAIL: 
> validate_cpp_version_real_double_eigenvectors_2stage_default_kernel_random_default.sh
> FAIL: validate_cpp_version_complex_double_generalized_1stage_random_default.sh
> FAIL: validate_cpp_version_real_double_generalized_1stage_random_default.sh
> FAIL: 
> validate_cpp_version_complex_double_generalized_decomp_1stage_random_default.sh
> FAIL: 
> validate_cpp_version_real_double_generalized_decomp_1stage_random_default.sh
> FAIL: 
> validate_cpp_version_complex_double_hermitian_multiply_1stage_random_explicit_default.sh
> FAIL: 
> validate_cpp_version_complex_double_hermitian_multiply_1stage_random_default.sh
> FAIL: 
> va

Bug#1069511: mpgrafic: FTBFS on armhf: tests fail

[Lucas Nussbaum]

Source: mpgrafic
Version: 0.3.19-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>'
> FAIL: regression-test-0.3.7.9.sh
> ===
>mpgrafic 0.3.19: ./test-suite.log
> ===
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: regression-test-0.3.7.9.sh
> 
> 
> Code regression test: does the standard input file generate an
> output file identical to that produced by version 0.3.7.9
> of mpgrafic? IEEE_UNDERFLOW_FLAG and IEEE_DENORMAL exceptions
> are considered acceptable and ignored. Other minor warnings are
> ignored too on some systems/implementations.
> 
> This looks like a debian openmpi system.
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-166:4006035] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> Warning: A 32^3 mpi run of mpgrafic did not match the expected output.
> FAIL regression-test-0.3.7.9.sh (exit status: 1)
> 
> 
> Testsuite summary for mpgrafic 0.3.19
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See ./test-suite.log
> 
> make[5]: *** [Makefile:711: test-suite.log] Error 1
> make[5]: Leaving directory '/<>'
> make[4]: *** [Makefile:819: check-TESTS] Error 2
> make[4]: Leaving directory '/<>'
> make[3]: *** [Makefile:1055: check-am] Error 2
> make[3]: Leaving directory '/<>'
> make[2]: *** [Makefile:596: check-recursive] Error 1
> make[2]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/mpgrafic_0.3.19-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069509: r-cran-metamix: FTBFS on armhf: tests fail

[Lucas Nussbaum]

Source: r-cran-metamix
Version: 0.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>/src'
> make[1]: Leaving directory '/<>/src'
> installing to 
> /<>/debian/r-cran-metamix/usr/lib/R/site-library/00LOCK-r-cran-metamix-0.3/00new/metaMix/libs
> ** R
> ** data
> *** moving datasets to lazyload DB
> ** inst
> ** byte-compile and prepare package for lazy loading
> --
> Sorry!  You were supposed to get help about:
> pmix_init:startup:internal-failure
> But I couldn't open the help file:
> /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  Sorry!
> --
> [ip-10-84-234-19:2164897] PMIX ERROR: NOT-FOUND in file 
> ../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
> line 237
> [ip-10-84-234-19:2164891] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start 
> a daemon on the local node in file 
> ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 716
> [ip-10-84-234-19:2164891] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start 
> a daemon on the local node in file 
> ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172
> --
> It looks like orte_init failed for some reason; your parallel process is
> likely to abort.  There are many reasons that a parallel process can
> fail during orte_init; some of which are due to configuration or
> environment problems.  This failure appears to be an internal failure;
> here's some additional information (which may only be relevant to an
> Open MPI developer):
> 
>   orte_ess_init failed
>   --> Returned value Unable to start a daemon on the local node (-127) 
> instead of ORTE_SUCCESS
> --
> --
> It looks like MPI_INIT failed for some reason; your parallel process is
> likely to abort.  There are many reasons that a parallel process can
> fail during MPI_INIT; some of which are due to configuration or environment
> problems.  This failure appears to be an internal failure; here's some
> additional information (which may only be relevant to an Open MPI
> developer):
> 
>   ompi_mpi_init: ompi_rte_init failed
>   --> Returned "Unable to start a daemon on the local node" (-127) instead of 
> "Success" (0)
> --
> *** An error occurred in MPI_Init
> *** on a NULL communicator
> *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
> ***and potentially your MPI job)
> [ip-10-84-234-19:2164891] Local abort before MPI_INIT completed completed 
> successfully, but am not able to aggregate error messages, and not able to 
> guarantee that all other processes were killed!
> ERROR: lazy loading failed for package ‘metaMix’
> * removing 
> ‘/<>/debian/r-cran-metamix/usr/lib/R/site-library/metaMix’
> dh_auto_install: error: R CMD INSTALL -l 
> /<>/debian/r-cran-metamix/usr/lib/R/site-library --clean . 
> "--built-timestamp='Sat, 21 Mar 2020 14:53:15 +0100'" returned exit code 1
> make: *** [debian/rules:4: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/r-cran-metamix_0.3-2_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069507: dc3dd: FTBFS on armhf: verify.h:132:30: error: negative width in bit-field 'verify_error_if_negative_size__'

[Lucas Nussbaum]

Source: dc3dd
Version: 7.3.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> gcc  -I.   -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
> -Wdate-time -D_FORTIFY_SOURCE=2   -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -c -o localcharset.o localcharset.c
> In file included from getdate.y:40:
> verify.h:132:30: error: negative width in bit-field 
> 'verify_error_if_negative_size__'
>   132 |   (struct { unsigned int verify_error_if_negative_size__: (R) ? 1 
> : -1; }))
>   |  ^~~
> verify.h:138:61: note: in expansion of macro 'verify_true'
>   138 | # define verify(R) extern int (* verify_function__ (void)) 
> [verify_true (R)]
>   | 
> ^~~
> getdate.y:116:1: note: in expansion of macro 'verify'
>   116 | verify (LONG_MIN <= TYPE_MINIMUM (time_t) && TYPE_MAXIMUM (time_t) <= 
> LONG_MAX);
>   | ^~
> make[4]: *** [Makefile:1471: getdate.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/dc3dd_7.3.1-2_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069506: prelude-lml: FTBFS on armhf: unsatisfiable build-dependencies

[Lucas Nussbaum]

Source: prelude-lml
Version: 5.2.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), libev-dev, libprelude-dev (>= 
> 5.2.0), prelude-utils (>= 5.2.0), libpcre2-dev, libicu-dev, pkg-config, 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), libev-dev, libprelude-dev 
> (>= 5.2.0), prelude-utils (>= 5.2.0), libpcre2-dev, libicu-dev, pkg-config, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [719 B]
> Get:5 copy:/<>/apt_archive ./ Packages [751 B]
> Fetched 2079 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  apt : Conflicts: libnettle8 (< 3.9.1-2.2~) but 3.9.1-2+b1 is to be installed
>  libapt-pkg6.0t64 : Conflicts: libnettle8 (< 3.9.1-2.2~) but 3.9.1-2+b1 is to 
> be installed
>  libgnutls30t64 : Breaks: libgnutls30 (< 3.8.5-2) but 3.8.3-1 is to be 
> installed
>  libhogweed6t64 : Breaks: libhogweed6 (< 3.9.1-2.2) but 3.9.1-2+b1 is to be 
> installed
>  libnettle8t64 : Breaks: libnettle8 (< 3.9.1-2.2) but 3.9.1-2+b1 is to be 
> installed
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
> held packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/prelude-lml_5.2.0-3_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069505: tmperamental: FTBFS on armhf: features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

[Lucas Nussbaum]

Source: tmperamental
Version: 1.4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> cc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -fPIC -DPIC -c -o out/tmperamental.o src/tmperamental.c
> sed -e "s,@pkglibdir@,/usr/lib/tmperamental,g"  >out/tmperamental
> chmod +x out/tmperamental
> In file included from /usr/include/features.h:393,
>  from /usr/include/dlfcn.h:22,
>  from src/tmperamental.c:30:
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
> only with _FILE_OFFSET_BITS=64"
>26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
>   | ^
> make[1]: *** [Makefile:34: out/tmperamental.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/tmperamental_1.4_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069503: haskell-gtk-strut: FTBFS on armhf: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:170: build-haddock-stamp] Error 1

[Lucas Nussbaum]

Source: haskell-gtk-strut
Version: 0.1.3.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-gtk-strut-doc.substvars
> dh_installdirs -plibghc-gtk-strut-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe'
> Running find . ! -newer /tmp/XnuZS5Mtno -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-gtk-strut-dev
> libghc-gtk-strut-prof
> libghc-gtk-strut-doc
> Running dh_listpackages
> libghc-gtk-strut-dev
> libghc-gtk-strut-prof
> libghc-gtk-strut-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/gtk-strut-0.1.3.2/ 
> --datasubdir=gtk-strut --htmldir=/usr/share/doc/libghc-gtk-strut-doc/html/ 
> --enable-library-profiling
> Using Parsec parser
> Configuring gtk-strut-0.1.3.2...
> Dependency base >=4.7 && <5: using base-4.17.2.0
> Dependency data-default: using data-default-0.7.1.1
> Dependency gi-gdk >=3.0.25 && <4: using gi-gdk-3.0.28
> Dependency gi-gtk >=3.0.38 && <4: using gi-gtk-3.0.41
> Dependency hslogger: using hslogger-1.3.1.0
> Dependency text: using text-2.0.2
> Dependency transformers: using transformers-0.5.6.2
> Source component graph: component lib
> Configured component graph:
> component gtk-strut-0.1.3.2-rE7vmrEijuZPfVoPMmBo
> include base-4.17.2.0
> include data-default-0.7.1.1-4TeAZDN81Uu1IorgFaPMOc
> include gi-gdk-3.0.28-89CSgrkJIuCFjH4ZKiJGtd
> include gi-gtk-3.0.41-Gc1BXOsaBV9ASBI6GEqeMF
> include hslogger-1.3.1.0-FviSSUEF0qgLcxWW1gLUJE
> include text-2.0.2
> include transformers-0.5.6.2
> Linked component graph:
> unit gtk-strut-0.1.3.2-rE7vmrEijuZPfVoPMmBo
> include base-4.17.2.0
> include data-default-0.7.1.1-4TeAZDN81Uu1IorgFaPMOc
> include gi-gdk-3.0.28-89CSgrkJIuCFjH4ZKiJGtd
> include gi-gtk-3.0.41-Gc1BXOsaBV9ASBI6GEqeMF
> include hslogger-1.3.1.0-FviSSUEF0qgLcxWW1gLUJE
> include text-2.0.2
> include transformers-0.5.6.2
> 
> Graphics.UI.GIGtkStrut=gtk-strut-0.1.3.2-rE7vmrEijuZPfVoPMmBo:Graphics.UI.GIGtkStrut
> Ready component graph:
> definite gtk-strut-0.1.3.2-rE7vmrEijuZPfVoPMmBo
> depends base-4.17.2.0
> depends data-default-0.7.1.1-4TeAZDN81Uu1IorgFaPMOc
> depends gi-gdk-3.0.28-89CSgrkJIuCFjH4ZKiJGtd
> depends gi-gtk-3.0.41-Gc1BXOsaBV9ASBI6GEqeMF
> depends hslogger-1.3.1.0-FviSSUEF0qgLcxWW1gLUJE
> depends text-2.0.2
> depends transformers-0.5.6.2
> Using Cabal-3.8.1.0 compiled by ghc-9.4
> Using compiler: ghc-9.4.7
> Using install prefix: /usr
> Executables installed in: /usr/bin
> Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/arm-linux-ghc-9.4.7/gtk-strut-0.1.3.2-rE7vmrEijuZPfVoPMmBo
> Dynamic Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/arm-linux-ghc-9.4.7
> Private executables installed in:
> /usr/lib/arm-linux-ghc-9.4.7/gtk-strut-0.1.3.2
> Data files installed in: /usr/share/gtk-strut
> Documentation installed in:
> /usr/share/doc/arm-linux-ghc-9.4.7/gtk-strut-0.1.3.2
> Configuration files installed in: /usr/etc
> No alex found
> Using ar found on system at: /usr/bin/arm-linux-gnueabihf-ar
> No c2hs found
> No cpphs found
> No doctest found
> Using gcc version 13 found on system at: /usr/bin/arm-linux-gnueabihf-gcc
> Using ghc version 9.4.7 found on system at: /usr/bin/ghc
> Using ghc-pkg version 9.4.7 found on system at: /usr/bin/ghc-pkg-9.4.7
> No ghcjs found
> No ghcjs-pkg found
> No greencard found
> Using haddock version 2.27.0 found on system at: /usr/bin/haddock-ghc-9.4.7
> No happy foun

Bug#1069504: libosmo-sccp: FTBFS on armhf: build-dependency not installable: libosmo-netif-dev (>= 1.2.0)

[Lucas Nussbaum]

Source: libosmo-sccp
Version: 1.6.0+dfsg1-3.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), 
> pkg-config, libosmocore-dev (>= 1.7.0), autoconf, automake, libtool, doxygen, 
> libdpkg-perl, libosmo-netif-dev (>= 1.2.0), libsctp-dev, build-essential, 
> fakeroot
> Filtered Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), 
> pkg-config, libosmocore-dev (>= 1.7.0), autoconf, automake, libtool, doxygen, 
> libdpkg-perl, libosmo-netif-dev (>= 1.2.0), libsctp-dev, build-essential, 
> fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [774 B]
> Get:5 copy:/<>/apt_archive ./ Packages [806 B]
> Fetched 2189 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libosmo-netif-dev (>= 1.2.0) but 
> it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libosmo-sccp_1.6.0+dfsg1-3.1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069501: haskell-pandoc-server: FTBFS on armhf: unsatisfiable build-dependencies

[Lucas Nussbaum]

Source: haskell-pandoc-server
Version: 0.1.0.2-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts (>= 0.13), cdbs, 
> ghc (>= 9.4), ghc-prof, libghc-aeson-dev (>= 2.0), libghc-aeson-dev (<< 2.3), 
> libghc-aeson-prof, libghc-base64-bytestring-dev (>= 0.1), 
> libghc-base64-bytestring-dev (<< 1.3), libghc-base64-bytestring-prof, 
> libghc-data-default-dev (>= 0.4), libghc-data-default-dev (<< 0.8), 
> libghc-data-default-prof, libghc-doctemplates-dev (>= 0.11), 
> libghc-doctemplates-dev (<< 0.12), libghc-doctemplates-prof, 
> libghc-pandoc-dev (>= 3.0), libghc-pandoc-prof, libghc-pandoc-types-dev (>= 
> 1.22), libghc-pandoc-types-dev (<< 1.24), libghc-pandoc-types-prof, 
> libghc-servant-server-dev (>= 0.19), libghc-servant-server-dev (<< 0.21), 
> libghc-servant-server-prof, libghc-skylighting-dev (>= 0.13), 
> libghc-skylighting-dev (<< 0.14), libghc-skylighting-prof, 
> libghc-unicode-collation-dev (>= 0.1.1), libghc-unicode-collation-dev (<< 
> 0.2), libghc-unicode-collation-prof, libghc-wai-dev (>= 3.2), libghc-wai-dev 
> (<< 3.3), libghc-wai-prof, libghc-wai-cors-dev (>= 0.2.7), 
> libghc-wai-cors-dev (<< 0.3), libghc-wai-cors-prof, build-essential, 
> fakeroot, ghc-doc, libghc-aeson-doc, libghc-base64-bytestring-doc, 
> libghc-data-default-doc, libghc-doctemplates-doc, libghc-pandoc-doc, 
> libghc-pandoc-types-doc, libghc-servant-server-doc, libghc-skylighting-doc, 
> libghc-unicode-collation-doc, libghc-wai-doc, libghc-wai-cors-doc
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts (>= 0.13), 
> cdbs, ghc (>= 9.4), ghc-prof, libghc-aeson-dev (>= 2.0), libghc-aeson-dev (<< 
> 2.3), libghc-aeson-prof, libghc-base64-bytestring-dev (>= 0.1), 
> libghc-base64-bytestring-dev (<< 1.3), libghc-base64-bytestring-prof, 
> libghc-data-default-dev (>= 0.4), libghc-data-default-dev (<< 0.8), 
> libghc-data-default-prof, libghc-doctemplates-dev (>= 0.11), 
> libghc-doctemplates-dev (<< 0.12), libghc-doctemplates-prof, 
> libghc-pandoc-dev (>= 3.0), libghc-pandoc-prof, libghc-pandoc-types-dev (>= 
> 1.22), libghc-pandoc-types-dev (<< 1.24), libghc-pandoc-types-prof, 
> libghc-servant-server-dev (>= 0.19), libghc-servant-server-dev (<< 0.21), 
> libghc-servant-server-prof, libghc-skylighting-dev (>= 0.13), 
> libghc-skylighting-dev (<< 0.14), libghc-skylighting-prof, 
> libghc-unicode-collation-dev (>= 0.1.1), libghc-unicode-collation-dev (<< 
> 0.2), libghc-unicode-collation-prof, libghc-wai-dev (>= 3.2), libghc-wai-dev 
> (<< 3.3), libghc-wai-prof, libghc-wai-cors-dev (>= 0.2.7), 
> libghc-wai-cors-dev (<< 0.3), libghc-wai-cors-prof, build-essential, 
> fakeroot, ghc-doc, libghc-aeson-doc, libghc-base64-bytestring-doc, 
> libghc-data-default-doc, libghc-doctemplates-doc, libghc-pandoc-doc, 
> libghc-pandoc-types-doc, libghc-servant-server-doc, libghc-skylighting-doc, 
> libghc-unicode-collation-doc, libghc-wai-doc, libghc-wai-cors-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1936 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1946 B]
> Fetched 4497 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-pando

Bug#1069502: input-utils: FTBFS on armhf: input.c:146:18: error: ‘struct input_event’ has no member named ‘time’

[Lucas Nussbaum]

Source: input-utils
Version: 1.0-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> checking for libdir name ... lib
> basename: missing operand
> Try 'basename --help' for more information.
> 
> Make.config written, edit if needed
> 
> basename: missing operand
> Try 'basename --help' for more information.
>   CClsinput.o
> sh name.sh EV > EV.h
> sh name.sh REL > REL.h
> sh name.sh ABS > ABS.h
> sh name.sh MSC > MSC.h
> sh name.sh LED > LED.h
> sh name.sh SND > SND.h
> sh name.sh REP > REP.h
> sh name.sh KEY > KEY.h
> sh name.sh BTN > BTN.h
> sh name.sh BUS > BUS.h
> sh name.sh SW > SW.h
>   CCinput.o
> input.c: In function ‘print_event’:
> input.c:146:18: error: ‘struct input_event’ has no member named ‘time’
>   146 | t = event->time.tv_sec;
>   |  ^~
> input.c:148:39: error: ‘struct input_event’ has no member named ‘time’
>   148 | printf("%s.%06ld: %s",ts,event->time.tv_usec,
>   |   ^~
> make[1]: *** [mk/Compile.mk:60: input.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/input-utils_1.0-1.1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069500: haskell-cryptostore: FTBFS on armhf: unsatisfiable build-dependencies

[Lucas Nussbaum]

Source: haskell-cryptostore
Version: 0.3.0.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | 
> haskell-devscripts (>= 0.13), cdbs, ghc, ghc-prof, libghc-asn1-encoding-dev 
> (>= 0.9), libghc-asn1-encoding-dev (<< 0.10), libghc-asn1-encoding-prof, 
> libghc-asn1-types-dev (>= 0.3.1), libghc-asn1-types-dev (<< 0.4), 
> libghc-asn1-types-prof, libghc-basement-dev, libghc-basement-prof, 
> libghc-cryptonite-dev (>= 0.26), libghc-cryptonite-prof, libghc-hourglass-dev 
> (>= 0.2), libghc-hourglass-prof, libghc-memory-dev, libghc-memory-prof, 
> libghc-pem-dev (>= 0.1), libghc-pem-dev (<< 0.3), libghc-pem-prof, 
> libghc-x509-dev (>= 1.7.5), libghc-x509-prof, libghc-x509-validation-dev (>= 
> 1.5), libghc-x509-validation-prof, libghc-tasty-dev, libghc-tasty-prof, 
> libghc-tasty-hunit-dev, libghc-tasty-hunit-prof, libghc-tasty-quickcheck-dev, 
> libghc-tasty-quickcheck-prof, build-essential, fakeroot, ghc-doc, 
> libghc-asn1-encoding-doc, libghc-asn1-types-doc, libghc-basement-doc, 
> libghc-cryptonite-doc, libghc-hourglass-doc, libghc-memory-doc, 
> libghc-pem-doc, libghc-x509-doc, libghc-x509-validation-doc
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, 
> ghc, ghc-prof, libghc-asn1-encoding-dev (>= 0.9), libghc-asn1-encoding-dev 
> (<< 0.10), libghc-asn1-encoding-prof, libghc-asn1-types-dev (>= 0.3.1), 
> libghc-asn1-types-dev (<< 0.4), libghc-asn1-types-prof, libghc-basement-dev, 
> libghc-basement-prof, libghc-cryptonite-dev (>= 0.26), 
> libghc-cryptonite-prof, libghc-hourglass-dev (>= 0.2), libghc-hourglass-prof, 
> libghc-memory-dev, libghc-memory-prof, libghc-pem-dev (>= 0.1), 
> libghc-pem-dev (<< 0.3), libghc-pem-prof, libghc-x509-dev (>= 1.7.5), 
> libghc-x509-prof, libghc-x509-validation-dev (>= 1.5), 
> libghc-x509-validation-prof, libghc-tasty-dev, libghc-tasty-prof, 
> libghc-tasty-hunit-dev, libghc-tasty-hunit-prof, libghc-tasty-quickcheck-dev, 
> libghc-tasty-quickcheck-prof, build-essential, fakeroot, ghc-doc, 
> libghc-asn1-encoding-doc, libghc-asn1-types-doc, libghc-basement-doc, 
> libghc-cryptonite-doc, libghc-hourglass-doc, libghc-memory-doc, 
> libghc-pem-doc, libghc-x509-doc, libghc-x509-validation-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1623 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1602 B]
> Fetched 3840 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-x509-dev : Depends: libghc-asn1-encoding-dev-0.9.6-4f999 but it is 
> not installable
>Depends: libghc-asn1-parse-dev-0.9.5-a5988 but it is not 
> installable
>Depends: libghc-asn1-types-dev-0.3.4-aa235 but it is not 
> installable
>Depends: libghc-base-dev-4.17.2.0-38dbb but it is not 
> installable
>Depends: libghc-bytestring-dev-0.11.5.2-302b4 but it is 
> not installable
>Depends: libghc-containers-dev-0.6.7-e92e7 but it is not 
> installable
>Depends: libghc-cryptonite-dev-0.30-d9a59 but it is not 
> installable
>Depends: libghc-hourglass-dev-0.2.12-35178 but it is not 
> installable
>Depends: libghc-memory-dev-0.18.0-fec46 but it 

Bug#1069499: mtbl: FTBFS on armhf: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: mtbl
Version: 1.3.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> PASS: t/test-block_builder
> PASS: t/test-fileset-partition.sh
> PASS: t/test-crc32c
> PASS: t/test-fixed
> PASS: t/test-varint
> PASS: t/test-vector
> PASS: t/test-metadata
> PASS: t/test-deb716628.sh
> PASS: t/test-iter-seek
> ./build-aux/test-driver: line 112: 712495 Aborted "$@" >> 
> "$log_file" 2>&1
> FAIL: t/test-sorted-merge
> PASS: t/test-foreign-prefix.sh
> PASS: t/test-gh1.sh
> PASS: t/test-verify.sh
> PASS: t/test-compression.sh
> ==
>mtbl 1.3.0: ./test-suite.log
> ==
> 
> # TOTAL: 14
> # PASS:  13
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: t/test-sorted-merge
> =
> 
> test-sorted-merge: t/test-sorted-merge.c:96: quiet_tmpnam: Assertion 
> `not_found == 1' failed.
> FAIL t/test-sorted-merge (exit status: 134)
> 
> 
> Testsuite summary for mtbl 1.3.0
> 
> # TOTAL: 14
> # PASS:  13
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See ./test-suite.log
> Please report to https://github.com/farsightsec/mtbl/issues
> 
> make[3]: *** [Makefile:1416: test-suite.log] Error 1
> make[3]: Leaving directory '/<>'
> make[2]: *** [Makefile:1524: check-TESTS] Error 2
> make[2]: Leaving directory '/<>'
> make[1]: *** [Makefile:1827: check-am] Error 2
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/mtbl_1.3.0-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.

Bug#1069498: libx86emu: FTBFS on armhf: mem.c:581:12: error: implicit declaration of function ‘inb’; did you mean ‘ins’? [-Werror=implicit-function-declaration]

[Lucas Nussbaum]

Source: libx86emu
Version: 3.5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> cc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -g -O2 -fPIC 
> -fvisibility=hidden -fomit-frame-pointer -Wall -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wl,-z,relro -Wl,-z,now -c ops.c
> mem.c: In function ‘vm_i_byte’:
> mem.c:581:12: error: implicit declaration of function ‘inb’; did you mean 
> ‘ins’? [-Werror=implicit-function-declaration]
>   581 | return inb(addr);
>   |^~~
>   |ins
> mem.c: In function ‘vm_i_word’:
> mem.c:619:10: error: implicit declaration of function ‘inw’; did you mean 
> ‘ins’? [-Werror=implicit-function-declaration]
>   619 |   return inw(addr);
>   |  ^~~
>   |  ins
> mem.c: In function ‘vm_i_dword’:
> mem.c:657:10: error: implicit declaration of function ‘inl’; did you mean 
> ‘ins’? [-Werror=implicit-function-declaration]
>   657 |   return inl(addr);
>   |  ^~~
>   |  ins
> mem.c: In function ‘vm_o_byte’:
> mem.c:676:5: error: implicit declaration of function ‘outb’; did you mean 
> ‘outs’? [-Werror=implicit-function-declaration]
>   676 | outb(val, addr);
>   | ^~~~
>   | outs
> mem.c: In function ‘vm_o_word’:
> mem.c:711:3: error: implicit declaration of function ‘outw’; did you mean 
> ‘outs’? [-Werror=implicit-function-declaration]
>   711 |   outw(val, addr);
>   |   ^~~~
>   |   outs
> mem.c: In function ‘vm_o_dword’:
> mem.c:748:3: error: implicit declaration of function ‘outl’; did you mean 
> ‘outs’? [-Werror=implicit-function-declaration]
>   748 |   outl(val, addr);
>   |   ^~~~
>   |   outs
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:22: mem.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libx86emu_3.5-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=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.