Processed: Re: clblas: FTBFS on arm{el,hf}: /<>/src/library/blas/gens/symv.c:955:29: error: implicit declaration of function ‘abs’; did you mean ‘fabs’? [-Werror=implicit-function-declara

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1065777 [src:clblas] clblas: FTBFS on arm{el,hf}: 
/<>/src/library/blas/gens/symv.c:955:29: error: implicit 
declaration of function ‘abs’; did you mean ‘fabs’? 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1065777: clblas: FTBFS on arm{el,hf}: /<>/src/library/blas/gens/symv.c:955:29: error: implicit declaration of function ‘abs’; did you mean ‘fabs’? [-Werror=implicit-function-declarati

[Steve Langasek]

Package: clblas
Followup-For: Bug #1065777
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue.  This patch has been uploaded
to Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru clblas-2.12/debian/patches/no-implicit-declarations.patch 
clblas-2.12/debian/patches/no-implicit-declarations.patch
--- clblas-2.12/debian/patches/no-implicit-declarations.patch   1969-12-31 
16:00:00.0 -0800
+++ clblas-2.12/debian/patches/no-implicit-declarations.patch   2024-04-09 
14:41:58.0 -0700
@@ -0,0 +1,18 @@
+Description: Add missing stdlib.h include
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1065777
+Last-Update: 2024-04-09
+Forwarded: no
+
+Index: clblas-2.12/src/library/blas/gens/gemv.c
+===
+--- clblas-2.12.orig/src/library/blas/gens/gemv.c
 clblas-2.12/src/library/blas/gens/gemv.c
+@@ -21,6 +21,7 @@
+ 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru clblas-2.12/debian/patches/series clblas-2.12/debian/patches/series
--- clblas-2.12/debian/patches/series   2023-09-28 16:21:54.0 -0700
+++ clblas-2.12/debian/patches/series   2024-04-09 14:40:35.0 -0700
@@ -9,3 +9,4 @@
 Fix-double-literals.patch
 Fix-null-pointer-crash.patch
 Fix-local-variables-not-declared-in-outermost-scope.patch
+no-implicit-declarations.patch

Bug#1068251: marked as done (glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 22:35:39 +
with message-id 
and subject line Bug#1068251: fixed in glibc 2.37-16
has caused the Debian Bug report #1068251,
regarding glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit 
time_t
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.)


-- 
1068251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.37-15.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-...@lists.debian.org

Starting with gcc-12 version 12.3.0-15, -D_TIME_BITS=64 together with
-D_FILE_OFFSET_BITS=64 are passed by default on 32-bit architectures
except i386.

This has been partially fixed in the 2.37-15.1 NMU by adding
-U_TIME_BITS to CFLAGS, however it causes failures in the testsuite:

| +-+
| | Encountered regressions that don't match expected failures. |
| +-+
| FAIL: conform/ISO/stdio.h/linknamespace
| FAIL: conform/ISO11/stdio.h/linknamespace
| FAIL: conform/ISO99/stdio.h/linknamespace
| FAIL: conform/POSIX/aio.h/linknamespace
| FAIL: conform/POSIX/dirent.h/linknamespace
| FAIL: conform/POSIX/fcntl.h/conform
| FAIL: conform/POSIX/fcntl.h/linknamespace
| FAIL: conform/POSIX/glob.h/conform
| FAIL: conform/POSIX/mqueue.h/conform
| FAIL: conform/POSIX/mqueue.h/linknamespace
| FAIL: conform/POSIX/stdio.h/linknamespace
| FAIL: conform/POSIX/sys/mman.h/linknamespace
| FAIL: conform/POSIX/sys/stat.h/conform
| FAIL: conform/POSIX/unistd.h/conform
| FAIL: conform/POSIX/unistd.h/linknamespace
| FAIL: conform/POSIX/utime.h/conform
| FAIL: conform/POSIX2008/aio.h/linknamespace
| FAIL: conform/POSIX2008/dirent.h/linknamespace
| FAIL: conform/POSIX2008/fcntl.h/conform
| FAIL: conform/POSIX2008/fcntl.h/linknamespace
| FAIL: conform/POSIX2008/glob.h/conform
| FAIL: conform/POSIX2008/mqueue.h/conform
| FAIL: conform/POSIX2008/mqueue.h/linknamespace
| FAIL: conform/POSIX2008/signal.h/conform
| FAIL: conform/POSIX2008/stdio.h/linknamespace
| FAIL: conform/POSIX2008/stdlib.h/linknamespace
| FAIL: conform/POSIX2008/sys/mman.h/linknamespace
| FAIL: conform/POSIX2008/sys/select.h/conform
| FAIL: conform/POSIX2008/sys/stat.h/conform
| FAIL: conform/POSIX2008/sys/statvfs.h/linknamespace
| FAIL: conform/POSIX2008/unistd.h/linknamespace
| FAIL: conform/UNIX98/aio.h/linknamespace
| FAIL: conform/UNIX98/dirent.h/linknamespace
| FAIL: conform/UNIX98/fcntl.h/conform
| FAIL: conform/UNIX98/fcntl.h/linknamespace
| FAIL: conform/UNIX98/glob.h/conform
| FAIL: conform/UNIX98/mqueue.h/conform
| FAIL: conform/UNIX98/mqueue.h/linknamespace
| FAIL: conform/UNIX98/stdio.h/linknamespace
| FAIL: conform/UNIX98/stdlib.h/linknamespace
| FAIL: conform/UNIX98/sys/mman.h/linknamespace
| FAIL: conform/UNIX98/sys/resource.h/linknamespace
| FAIL: conform/UNIX98/sys/statvfs.h/linknamespace
| FAIL: conform/UNIX98/sys/time.h/conform
| FAIL: conform/UNIX98/unistd.h/linknamespace
| FAIL: conform/UNIX98/utmpx.h/conform
| FAIL: conform/XOPEN2K/aio.h/linknamespace
| FAIL: conform/XOPEN2K/dirent.h/linknamespace
| FAIL: conform/XOPEN2K/fcntl.h/conform
| FAIL: conform/XOPEN2K/fcntl.h/linknamespace
| FAIL: conform/XOPEN2K/glob.h/conform
| FAIL: conform/XOPEN2K/mqueue.h/conform
| FAIL: conform/XOPEN2K/mqueue.h/linknamespace
| FAIL: conform/XOPEN2K/stdio.h/linknamespace
| FAIL: conform/XOPEN2K/stdlib.h/linknamespace
| FAIL: conform/XOPEN2K/sys/mman.h/linknamespace
| FAIL: conform/XOPEN2K/sys/resource.h/linknamespace
| FAIL: conform/XOPEN2K/sys/select.h/conform
| FAIL: conform/XOPEN2K/sys/statvfs.h/linknamespace
| FAIL: conform/XOPEN2K/sys/time.h/conform
| FAIL: conform/XOPEN2K/unistd.h/linknamespace
| FAIL: conform/XOPEN2K/utmpx.h/conform
| FAIL: conform/XOPEN2K8/aio.h/linknamespace
| FAIL: conform/XOPEN2K8/dirent.h/linknamespace
| FAIL: conform/XOPEN2K8/fcntl.h/conform
| FAIL: conform/XOPEN2K8/fcntl.h/linknamespace
| FAIL: conform/XOPEN2K8/ftw.h/conform
| FAIL: conform/XOPEN2K8/glob.h/conform
| FAIL: conform/XOPEN2K8/mqueue.h/conform
| FAIL: conform/XOPEN2K8/mqueue.h/linknamespace
| FAIL: conform/XOPEN2K8/signal.h/conform
| FAIL: conform/XOPEN2K8/stdio.h/linknamespace
| FAIL: conform/XOPEN2K8/stdlib.h/linknamespace
| FAIL: conform/XOPEN2K8/sys/mman.h/linknamespace
| FAIL: conform/XOPEN2K8/sys/resource.h/linknamespace
| FAIL: conform/XOPEN2K8/sys/select.h/conform
| FAIL: conform/XOPEN2K8/sys/stat.h/conform
| FAIL: 

Bug#1067911: FTBFS: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror]

[Chris Knadle]

Hello Audrey.

Apparently this new bug got introduced with the time_t 64bit transition:

"abi=time64 turns on -Werror=implicit-function-declaration in 
dpkg-buildflags, which causes unrelated build failures."


See: https://wiki.debian.org/BrainDumpT64

https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=4993fe783

What I don't know is what has to be done now to get zeroc-ice fixed. 
Does this require an upload to disable the implict-function-declaration 
flag, or does this simply require a binNMU?


I need to fix this to allow zeroc-ice to transition to Testing, in order 
to allow mumble to transition to Testing.


   -- Chris

--
Chris Knadle
chris.kna...@coredump.us


Source: zeroc-ice
Version: 3.7.10-2.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=zeroc-
ice=armhf=3.7.10-2.1=1711639887=0

arm-linux-gnueabihf-g++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-
protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -MT

modules/IcePy/build/arm-linux-gnueabihf/shared/pic/Grammar.o -MMD -MP -MF
modules/IcePy/build/arm-linux-gnueabihf/shared/pic/Grammar.Td -Wall 
-Wextra

-Wshadow -Wdeprecated -Werror -pthread -DNDEBUG -Imodules/IcePy
-I../cpp/include -I../cpp/include/generated -I../cpp/src
-I/usr/include/python3.11 -I/usr/include/python3.11 -Wsign-compare -g
-Werror=implicit-function-declaration -fstack-protector-strong 
-fstack-clash-
protection -Wformat -Werror=format-security -DNDEBUG -g -fwrapv -O2 
-Wall -Wno-

missing-field-initializers -Wno-psabi -fPIC -fvisibility=hidden
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time
-D_FORTIFY_SOURCE=2 -c ../cpp/src/Slice/Grammar.cpp -o 
modules/IcePy/build/arm-

linux-gnueabihf/shared/pic/Grammar.o
cc1plus: error: ‘-Werror=’ argument 
‘-Werror=implicit-function-declaration’ is

not valid for C++ [-Werror]
cc1plus: error: ‘-Werror=’ argument 
‘-Werror=implicit-function-declaration’ is

not valid for C++ [-Werror]
cc1plus: error: ‘-Werror=’ argument 
‘-Werror=implicit-function-declaration’ is

not valid for C++ [-Werror]
cc1plus: error: ‘-Werror=’ argument 
‘-Werror=implicit-function-declaration’ is

not valid for C++ [-Werror]

Bug#1068730: Fails to build from source since removal of liblz4-tool

[Christoph Biedl]

Source: systemd
Severity: serious
Tags: patch
X-Debbugs-Cc: debian.a...@manchmal.in-ulm.de

Greetings,

systemd build-depends on liblz4-tool but that package is no longer build
from src:lz4 (since 1.9.4-2, uploaded about a week ago). Just replacing
the dependency with lz4 seems to fix this problem (build passes, didn't
check further).

Cheers,

Christoph

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.23 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)



signature.asc
Description: PGP signature

Bug#1066286: das-watchdog: FTBFS: test_rt.c:32:33: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration]

[Steve Langasek]

Package: das-watchdog
Followup-For: Bug #1066286
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue, which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru das-watchdog-0.9.0/debian/patches/no-implicit-declarations.patch 
das-watchdog-0.9.0/debian/patches/no-implicit-declarations.patch
--- das-watchdog-0.9.0/debian/patches/no-implicit-declarations.patch
1969-12-31 16:00:00.0 -0800
+++ das-watchdog-0.9.0/debian/patches/no-implicit-declarations.patch
2024-04-09 16:13:22.0 -0700
@@ -0,0 +1,18 @@
+Description: add missing unistd.h include
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066286
+Last-Update: 2024-04-09
+Forwarded: no
+
+Index: das-watchdog-0.9.0/test_rt.c
+===
+--- das-watchdog-0.9.0.orig/test_rt.c
 das-watchdog-0.9.0/test_rt.c
+@@ -4,6 +4,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ int main() {
+   struct sched_param params;
diff -Nru das-watchdog-0.9.0/debian/patches/series 
das-watchdog-0.9.0/debian/patches/series
--- das-watchdog-0.9.0/debian/patches/series2023-09-19 01:59:37.0 
-0700
+++ das-watchdog-0.9.0/debian/patches/series2024-04-09 16:11:24.0 
-0700
@@ -6,3 +6,4 @@
 0001-Remove-duplicate-check-for-temp-i-0.patch
 0003-The-result-of-fgetc-is-an-int-not-a-char.patch
 fix-memory-leak-on-realloc.patch
+no-implicit-declarations.patch

Processed: Re: das-watchdog: FTBFS: test_rt.c:32:33: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066286 [src:das-watchdog] das-watchdog: FTBFS: test_rt.c:32:33: error: 
implicit declaration of function ‘getpid’ 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Processed: also in bullseye

[Debian Bug Tracking System]

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

> retitle 1053334 galera-4: FTBFS in bullseye and bookworm because of expired 
> SSL certificates
Bug #1053334 {Done: Otto Kekäläinen } [galera-4] galera-4: 
FTBFS in bookworm because of expired SSL certificates
Changed Bug title to 'galera-4: FTBFS in bullseye and bookworm because of 
expired SSL certificates' from 'galera-4: FTBFS in bookworm because of expired 
SSL certificates'.
> found 1053334 26.4.11-0+deb11u1
Bug #1053334 {Done: Otto Kekäläinen } [galera-4] galera-4: 
FTBFS in bullseye and bookworm because of expired SSL certificates
Marked as found in versions galera-4/26.4.11-0+deb11u1.
> tags 1053334 + bullseye
Bug #1053334 {Done: Otto Kekäläinen } [galera-4] galera-4: 
FTBFS in bullseye and bookworm because of expired SSL certificates
Added tag(s) bullseye.
> thanks
Stopping processing here.

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

Processed: Re: gnome-paint: FTBFS: cv_resize.c:368:9: error: implicit declaration of function ‘undo_add_resize’ [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066463 [src:gnome-paint] gnome-paint: FTBFS: cv_resize.c:368:9: error: 
implicit declaration of function ‘undo_add_resize’ 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1066463: gnome-paint: FTBFS: cv_resize.c:368:9: error: implicit declaration of function ‘undo_add_resize’ [-Werror=implicit-function-declaration]

[Steve Langasek]

Package: gnome-paint
Followup-For: Bug #1066463
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gnome-paint-0.4.0/debian/patches/no-implicit-declarations.patch 
gnome-paint-0.4.0/debian/patches/no-implicit-declarations.patch
--- gnome-paint-0.4.0/debian/patches/no-implicit-declarations.patch 
1969-12-31 16:00:00.0 -0800
+++ gnome-paint-0.4.0/debian/patches/no-implicit-declarations.patch 
2024-04-09 22:03:59.0 -0700
@@ -0,0 +1,192 @@
+Description: Add missing includes, don't set GTK_DISABLE_DEPRECATED
+ deprecated APIs are in use.
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066463
+Last-Update: 2024-04-09
+Forwarded: no
+
+Index: gnome-paint-0.4.0/src/Makefile.am
+===
+--- gnome-paint-0.4.0.orig/src/Makefile.am
 gnome-paint-0.4.0/src/Makefile.am
+@@ -78,7 +78,6 @@
+ gnome_paint_CFLAGS = \
+   -DG_DISABLE_DEPRECATED\
+   -DG_DISABLE_SINGLE_INCLUDES\
+-  -DGTK_DISABLE_DEPRECATED\
+   -DGDK_DISABLE_SINGLE_INCLUDES\
+   -DGTK_DISABLE_SINGLE_INCLUDES
+ 
+Index: gnome-paint-0.4.0/src/color.c
+===
+--- gnome-paint-0.4.0.orig/src/color.c
 gnome-paint-0.4.0/src/color.c
+@@ -20,6 +20,8 @@
+ #include "common.h"
+ #include "color.h"
+ #include "cv_drawing.h"
++#include "cv_eraser_tool.h"
++#include "cv_paintbrush_tool.h"
+ #include "pixbuf_util.h"
+ 
+ #include 
+Index: gnome-paint-0.4.0/src/undo.c
+===
+--- gnome-paint-0.4.0.orig/src/undo.c
 gnome-paint-0.4.0/src/undo.c
+@@ -28,7 +28,7 @@
+ #include "gp-image.h"
+ #include "gp_point_array.h"
+ #include "file.h"
+-
++#include "selection.h"
+ 
+ 
+ typedef enum
+Index: gnome-paint-0.4.0/src/cv_rectangle_tool.c
+===
+--- gnome-paint-0.4.0.orig/src/cv_rectangle_tool.c
 gnome-paint-0.4.0/src/cv_rectangle_tool.c
+@@ -25,6 +25,7 @@
+ #include 
+ 
+ #include "cv_rectangle_tool.h"
++#include "cv_drawing.h"
+ #include "file.h"
+ #include "undo.h"
+ #include "gp_point_array.h"
+Index: gnome-paint-0.4.0/src/cv_pencil_tool.c
+===
+--- gnome-paint-0.4.0.orig/src/cv_pencil_tool.c
 gnome-paint-0.4.0/src/cv_pencil_tool.c
+@@ -23,6 +23,7 @@
+  
+  #include 
+ 
++#include "cv_drawing.h"
+ #include "cv_pencil_tool.h"
+ #include "gp_point_array.h"
+ #include "undo.h"
+Index: gnome-paint-0.4.0/src/cv_resize.c
+===
+--- gnome-paint-0.4.0.orig/src/cv_resize.c
 gnome-paint-0.4.0/src/cv_resize.c
+@@ -28,6 +28,7 @@
+ #include "cv_resize.h"
+ #include "cv_drawing.h"
+ #include "file.h"
++#include "undo.h"
+ 
+ 
+ #define BOX_EDGE_SIZE 4
+Index: gnome-paint-0.4.0/src/cv_ellipse_tool.c
+===
+--- gnome-paint-0.4.0.orig/src/cv_ellipse_tool.c
 gnome-paint-0.4.0/src/cv_ellipse_tool.c
+@@ -24,6 +24,7 @@
+  
+  #include 
+ 
++#include "cv_drawing.h"
+ #include "cv_ellipse_tool.h"
+ #include "file.h"
+ #include "undo.h"
+Index: gnome-paint-0.4.0/src/cv_polygon_tool.c
+===
+--- gnome-paint-0.4.0.orig/src/cv_polygon_tool.c
 gnome-paint-0.4.0/src/cv_polygon_tool.c
+@@ -24,6 +24,7 @@
+  
+  #include 
+ 
++#include "cv_drawing.h"
+ #include "cv_polygon_tool.h"
+ #include "gp_point_array.h"
+ #include "undo.h"
+Index: gnome-paint-0.4.0/src/image_menu.c
+===
+--- gnome-paint-0.4.0.orig/src/image_menu.c
 gnome-paint-0.4.0/src/image_menu.c
+@@ -28,6 +28,7 @@
+ #include "selection.h"
+ #include "image_menu.h"
+ #include "gp-image.h"
++#include "undo.h"
+ 
+ typedef enum{
+   GP_FILP_VERT = 0,
+Index: gnome-paint-0.4.0/src/selection.h
+===
+--- gnome-paint-0.4.0.orig/src/selection.h
 gnome-paint-0.4.0/src/selection.h
+@@ -38,6 +38,10 @@
+ gbooleangp_selection_start_action   ( GdkPoint *p );
+ voidgp_selection_do_action  ( GdkPoint *p );
+ voidgp_selection_draw   ( GdkDrawable *gdkd );
++voidgp_selection_invert ( void );
++voidgp_selection_rotate ( GdkPixbufRotation 
angle );
++void

Bug#1066608: dvbstreamer: FTBFS: standard/dvb/sdtprocessor.c:299:14: error: implicit declaration of function ‘UTF8_nextchar’ [-Werror=implicit-function-declaration]

[Steve Langasek]

Package: dvbstreamer
Followup-For: Bug #1066608
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue which has been uploaded to
Ubuntu.  In addition to the missing declaration of UTF8_nextchar(), this
fixes a typo which would cause one of the plugins to build, but have
unresolvable symbol references.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru dvbstreamer-2.1.0/debian/patches/no-implicit-declarations.patch 
dvbstreamer-2.1.0/debian/patches/no-implicit-declarations.patch
--- dvbstreamer-2.1.0/debian/patches/no-implicit-declarations.patch 
1969-12-31 16:00:00.0 -0800
+++ dvbstreamer-2.1.0/debian/patches/no-implicit-declarations.patch 
2024-04-09 17:01:35.0 -0700
@@ -0,0 +1,38 @@
+Description: fix missing declaration of UTF8_nextchar() and typo
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066608
+Last-Update: 2024-04-09
+Forwarded: no
+
+Index: dvbstreamer-2.1.0/src/standard/dvb/sdtprocessor.c
+===
+--- dvbstreamer-2.1.0.orig/src/standard/dvb/sdtprocessor.c
 dvbstreamer-2.1.0/src/standard/dvb/sdtprocessor.c
+@@ -46,6 +46,7 @@
+ #include "sdtprocessor.h"
+ #include "dvbtext.h"
+ #include "standard/dvb.h"
++#include "utf8.h"
+ 
+ 
/***
+ * Defines 
 *
+Index: dvbstreamer-2.1.0/src/plugins/cam.c
+===
+--- dvbstreamer-2.1.0.orig/src/plugins/cam.c
 dvbstreamer-2.1.0/src/plugins/cam.c
+@@ -97,7 +97,7 @@
+ 
+ if (pmt->i_program_number == service->id)
+ {
+-needs_decrypting = PMTDoesNeedDecypting(pmt);
++needs_decrypting = PMTDoesNeedDecrypting(pmt);
+ 
+ if (currentPMT)
+ {
+@@ -197,4 +197,4 @@
+ }
+ 
+ return false;
+-}
+\ No newline at end of file
++}
diff -Nru dvbstreamer-2.1.0/debian/patches/series 
dvbstreamer-2.1.0/debian/patches/series
--- dvbstreamer-2.1.0/debian/patches/series 2021-10-16 01:37:38.0 
-0700
+++ dvbstreamer-2.1.0/debian/patches/series 2024-04-09 17:00:23.0 
-0700
@@ -16,3 +16,4 @@
 
 ## does not apply, needs some care
 #svn_819.diff
+no-implicit-declarations.patch

Processed: Re: dvbstreamer: FTBFS: standard/dvb/sdtprocessor.c:299:14: error: implicit declaration of function ‘UTF8_nextchar’ [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066608 [src:dvbstreamer] dvbstreamer: FTBFS: 
standard/dvb/sdtprocessor.c:299:14: error: implicit declaration of function 
‘UTF8_nextchar’ [-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1067629: FTBFS: Build killed with signal TERM after 150 minutes of inactivity

[Torrance, Douglas]

Control: reassign -1 gprbuild
Control: found -1 2024.1.20231009-4
Control: affects -1 src:phcpack

On Mon, 25 Mar 2024 00:49:45 +0500 Andrey Rakhmatullin  wrote:

Source: phcpack
Version: 2.4.90+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=phcpack=armhf=2.4.90%2Bdfsg-1=1711030010=0

   debian/rules execute_after_dh_auto_clean
make[1]: Entering directory '/<>'
gprclean src/Ada/Main/main.gpr || true
E: Build killed with signal TERM after 150 minutes of inactivity


This seems to be a bug with gprclean, as we're hanging at the initial dh_clean
step when building phcpack.  I was able to reproduce this on an armhf
porterbox.  Sending an interrupt while it's hanging with gdb gives the
following.  Perhaps it's related to the t64 transition?

   Starting program: /usr/bin/gprclean -v src/Ada/Main/main.gpr
   [Thread debugging using libthread_db enabled]
   Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
   GPRCLEAN Pro 18.0w (19940713) (arm-linux-gnueabihf)
   Copyright (C) 2006-2016, AdaCore
   
   Parsing Project File "src/Ada/Main/main.gpr".
   
150 lines: No errors

   TMPDIR = "/tmp/GPR.22180"
   /usr/bin/gprconfig --batch -o /tmp/GPR.22180/GNAT-TEMP-01.TMP 
--target=armhf-linux --fallback-targets --config=c --config=ada 
--config=c++
   [Detaching after fork from child process 22185]
   Checking configuration /tmp/GPR.22180/GNAT-TEMP-01.TMP
   Setting the default project search directories
  Adding directory "/usr/armhf-linux/share/gpr"
  Adding directory "/usr/armhf-linux/lib/gnat"
  Adding directory "/usr/share/gpr"
  Adding directory "/usr/lib/gnat"
   /usr/bin/gprconfig --batch -o /tmp/GPR.22180/GNAT-TEMP-02.TMP 
--target=armhf-linux --fallback-targets --config=c --config=ada 
--config=c++
   [Detaching after fork from child process 22203]
   Checking configuration /tmp/GPR.22180/GNAT-TEMP-02.TMP
   Setting the default project search directories
  Adding directory "/usr/armhf-linux/share/gpr"
  Adding directory "/usr/armhf-linux/lib/gnat"
  Adding directory "/usr/share/gpr"
  Adding directory "/usr/lib/gnat"
150 lines: No errors
   
   Parsing of Project File "src/Ada/Main/main.gpr" is finished.
   
   Cleaning project "main"
   
   
   No file has been deleted

   ^C
   Program received signal SIGINT, Interrupt.
   0xb5f7948a in __pthread_cond_timedwait64 ()
  from /lib/arm-linux-gnueabihf/libc.so.6
   (gdb) bt
   #0  0xb5f7948a in __pthread_cond_timedwait64 ()
  from /lib/arm-linux-gnueabihf/libc.so.6
   #1  0xb5f79636 in pthread_cond_timedwait ()
  from /lib/arm-linux-gnueabihf/libc.so.6
   #2  0xb63258c6 in system.task_primitives.operations.monotonic.timed_sleep ()
  from /lib/arm-linux-gnueabihf/libgnarl-13.so
   #3  0xb6325c7a in system.task_primitives.operations.timed_sleep ()
  from /lib/arm-linux-gnueabihf/libgnarl-13.so
   #4  0xb632b820 in system.tasking.stages.finalize_global_tasks ()
  from /lib/arm-linux-gnueabihf/libgnarl-13.so
   #5  0x00553930 in ?? ()
   #6  0xb5f3b7da in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
   #7  0xb5f3b87e in __libc_start_main () from 
/lib/arm-linux-gnueabihf/libc.so.6
   #8  0x005539ac in ?? ()
   Backtrace stopped: previous frame identical to this frame (corrupt stack?)


signature.asc
Description: PGP signature

Processed: Re: FTBFS: Build killed with signal TERM after 150 minutes of inactivity

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 gprbuild
Bug #1067629 [src:phcpack] FTBFS: Build killed with signal TERM after 150 
minutes of inactivity
Bug reassigned from package 'src:phcpack' to 'gprbuild'.
No longer marked as found in versions phcpack/2.4.90+dfsg-1.
Ignoring request to alter fixed versions of bug #1067629 to the same values 
previously set
> found -1 2024.1.20231009-4
Bug #1067629 [gprbuild] FTBFS: Build killed with signal TERM after 150 minutes 
of inactivity
Marked as found in versions gprbuild/2024.1.20231009-4.
> affects -1 src:phcpack
Bug #1067629 [gprbuild] FTBFS: Build killed with signal TERM after 150 minutes 
of inactivity
Added indication that 1067629 affects src:phcpack

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

Bug#1066677: marked as done (xpenguins: FTBFS: toon_signal.c:38:3: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Wed, 10 Apr 2024 03:34:10 +
with message-id 
and subject line Bug#1066677: fixed in xpenguins 3.2.1-2
has caused the Debian Bug report #1066677,
regarding xpenguins: FTBFS: toon_signal.c:38:3: error: implicit declaration of 
function ‘exit’ [-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.)


-- 
1066677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xpenguins
Version: 2.2-11
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 -DHAVE_CONFIG_H -I. -I..   -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 
> -DPKGDATADIR=\""/usr/share/xpenguins"\" -c -o toon_signal.o toon_signal.c
> toon_signal.c: In function ‘__ToonExitGracefully’:
> toon_signal.c:38:3: error: implicit declaration of function ‘exit’ 
> [-Werror=implicit-function-declaration]
>38 |   exit(0);
>   |   ^~~~
> toon_signal.c:20:1: note: include ‘’ or provide a declaration of 
> ‘exit’
>19 | #include "toon.h"
>   +++ |+#include 
>20 | 
> toon_signal.c:38:3: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>38 |   exit(0);
>   |   ^~~~
> toon_signal.c:38:3: note: include ‘’ or provide a declaration of 
> ‘exit’
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:389: toon_signal.o] Error 1


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

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: xpenguins
Source-Version: 3.2.1-2
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
xpenguins, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated xpenguins 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: Tue, 09 Apr 2024 23:11:24 -0400
Source: xpenguins
Architecture: source
Version: 3.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Boyuan Yang 
Closes: 1066677
Changes:
 xpenguins (3.2.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Upload to unstable. (Closes: #1066677)
   * debian/: Apply wrap-and-sort -abst.
   * Bump Standards-Version to 4.7.0.
   * debian/README.source: Dropped, useless.
Checksums-Sha1:
 a4e6d9ab00df31c2246114dc1cd92c0520823605 2026 xpenguins_3.2.1-2.dsc
 3601f3a0c44e5fafca29fb8bced46d6f9310e9f3 405876 xpenguins_3.2.1.orig.tar.gz
 eca2debda4041c00bac9d2647ac767dad502bf91 5264 xpenguins_3.2.1-2.debian.tar.xz
 81b1344ff323e66b2a001310bb3efb55cea14dc9 14827 
xpenguins_3.2.1-2_amd64.buildinfo
Checksums-Sha256:
 48c98a040a139849b6c01482d79a9838ef793451b2cf9e3fb1d0dd4e688e8ca4 2026 
xpenguins_3.2.1-2.dsc
 

Bug#1068731: falcosecurity-libs: FTBFS on riscv64 and ppc64el

[Bo YU]

Source: falcosecurity-libs
Version: 0.15.1-1
Severity: serious
Tags: ftbfs, patch

Dear Maintainer,

It seems new upstream release ftbfs on riscv64 and ppc64el due to:

```
/<>/userspace/chisel/chisel.cpp: In static member function ‘static 
bool sinsp_chisel::init_lua_chisel(chisel_desc&, const std::string&)’:
/<>/userspace/chisel/chisel.cpp:978:9: error: ‘luaL_setfuncs’ was 
not declared in this scope; did you mean ‘lua_setfenv’?
  978 | luaL_setfuncs(ls, ll_tool, 0);
  | ^
  | lua_setfenv
/<>/userspace/chisel/chisel.cpp: In member function ‘void 
sinsp_chisel::load(std::string, bool)’:
/<>/userspace/chisel/chisel.cpp:1189:9: error: ‘luaL_setfuncs’ was 
not declared in this scope; did you mean ‘lua_setfenv’?
 1189 | luaL_setfuncs(m_ls, ll_tool, 0);
  | ^
  | lua_setfenv
[ 53%] Building CXX object 
test/drivers/CMakeFiles/drivers_test.dir/test_suites/syscall_exit_suite/vfork_x.cpp.o
```

See 
https://buildd.debian.org/status/fetch.php?pkg=falcosecurity-libs=riscv64=0.15.1-1=1712602717=0
 
and 
https://buildd.debian.org/status/fetch.php?pkg=falcosecurity-libs=riscv64=0.15.1-1=1712602717=0

And there is no still luajit support for riscv64(or ppc64el?), so this[0] is 
right. but maybe we need upgrade to >liblua5.3[1].

BTW, it was build failed again with the patch on ppc64el but I tested it
on qemu-user and I ddi not have look more this.

Apart from these two architectures, FTBFS on other architectures due to
test failed[2]. But I think this is another story.

[0]: 
https://salsa.debian.org/debian/falcosecurity-libs/-/blob/master/debian/control?ref_type=heads#L24
[1]: 
https://github.com/owasp-modsecurity/ModSecurity/issues/1622#issuecomment-345841731
[2]: https://buildd.debian.org/status/package.php?p=falcosecurity-libs

-- 
Regards,
--
  Bo YU

diff -Nru falcosecurity-libs-0.15.1/debian/changelog 
falcosecurity-libs-0.15.1/debian/changelog
--- falcosecurity-libs-0.15.1/debian/changelog  2024-04-07 02:54:51.0 
+0800
+++ falcosecurity-libs-0.15.1/debian/changelog  2024-04-09 22:22:39.0 
+0800
@@ -1,3 +1,11 @@
+falcosecurity-libs (0.15.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use liblua5.3-dev instead of liblua5.1-dev to fix ftbfs 
+on riscv64 and ppc64el. (Closes: #-1)
+
+ -- Bo YU   Tue, 09 Apr 2024 22:22:39 +0800
+
 falcosecurity-libs (0.15.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru falcosecurity-libs-0.15.1/debian/control 
falcosecurity-libs-0.15.1/debian/control
--- falcosecurity-libs-0.15.1/debian/control2024-02-03 14:44:31.0 
+0800
+++ falcosecurity-libs-0.15.1/debian/control2024-04-09 22:22:04.0 
+0800
@@ -21,7 +21,7 @@
protobuf-compiler,
protobuf-compiler-grpc,
libprotobuf-dev,
-   libluajit-5.1-dev [amd64 arm64 armel armhf i386 mips64el s390x] 
| liblua5.1-0-dev,
+   libluajit-5.1-dev [amd64 arm64 armel armhf i386 mips64el s390x] 
| liblua5.3-dev,
libelf-dev,
libre2-dev,
libcap-dev,


signature.asc
Description: PGP signature

Processed: Re: gnome-breakout: FTBFS: anim.c:58:17: error: implicit declaration of function ‘gb_error’; did you mean ‘g_error’? [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066584 [src:gnome-breakout] gnome-breakout: FTBFS: anim.c:58:17: error: 
implicit declaration of function ‘gb_error’; did you mean ‘g_error’? 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1066584: gnome-breakout: FTBFS: anim.c:58:17: error: implicit declaration of function ‘gb_error’; did you mean ‘g_error’? [-Werror=implicit-function-declaration]

[Steve Langasek]

Package: gnome-breakout
Followup-For: Bug #1066584
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue, which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gnome-breakout-0.5.3/debian/patches/no-implicit-declarations.patch 
gnome-breakout-0.5.3/debian/patches/no-implicit-declarations.patch
--- gnome-breakout-0.5.3/debian/patches/no-implicit-declarations.patch  
1969-12-31 16:00:00.0 -0800
+++ gnome-breakout-0.5.3/debian/patches/no-implicit-declarations.patch  
2024-04-09 21:55:20.0 -0700
@@ -0,0 +1,30 @@
+Description: fix missing gb_error() prototype
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066584
+Last-Update: 2024-04-09
+Forwarded: no
+
+Index: gnome-breakout-0.5.3/src/anim.c
+===
+--- gnome-breakout-0.5.3.orig/src/anim.c
 gnome-breakout-0.5.3/src/anim.c
+@@ -11,6 +11,7 @@
+ #include"gui.h"
+ #include"animloc.h"
+ #include"anim.h"
++#include "util.h"
+ 
+ /* Database of all the animations */
+ static Animation *animations;
+Index: gnome-breakout-0.5.3/src/gui.c
+===
+--- gnome-breakout-0.5.3.orig/src/gui.c
 gnome-breakout-0.5.3/src/gui.c
+@@ -14,6 +14,7 @@
+ #include "gui-callbacks.h"
+ #include "game.h"
+ #include "anim.h"
++#include "util.h"
+ 
+ /* See gui.h for more info */
+ static GuiInfo *gui = NULL;
diff -Nru gnome-breakout-0.5.3/debian/patches/series 
gnome-breakout-0.5.3/debian/patches/series
--- gnome-breakout-0.5.3/debian/patches/series  2018-09-13 05:13:26.0 
-0700
+++ gnome-breakout-0.5.3/debian/patches/series  2024-04-09 21:52:53.0 
-0700
@@ -7,3 +7,4 @@
 07_fix_wformat_warnings.patch
 08_link_mathlib.patch
 09_goocanvas_port.patch
+no-implicit-declarations.patch

Processed: also in bullseye

[Debian Bug Tracking System]

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

> found 1064676 30.0.3-4
Bug #1064676 [src:android-platform-tools-apksig] android-platform-tools-apksig: 
FTBFS: dh_auto_test: error: gradle --info --console plain --offline 
--stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle 
-Duser.home=. -Duser.name=debian -Ddebian.package=android-platform-tools-apksig 
-Dfile.encoding=UTF-8 --parallel --max-workers=8 test returned exit code 1
Marked as found in versions android-platform-tools-apksig/30.0.3-4.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 1068457 https://github.com/Azure/azure-uamqp-python/issues/387
Bug #1068457 [src:azure-uamqp-python] azure-uamqp-python: CVE-2024-29195
Set Bug forwarded-to-address to 
'https://github.com/Azure/azure-uamqp-python/issues/387'.
>
End of message, stopping processing here.

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

Bug#1066222: gtk-chtheme: FTBFS: theme_sel.c:113:5: error: implicit declaration of function ‘gtk_timeout_add’; did you mean ‘g_timeout_add’? [-Werror=implicit-function-declaration]

[Steve Langasek]

Package: gtk-chtheme
Followup-For: Bug #1066222
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gtk-chtheme-0.3.1/debian/patches/no-implicit-declarations.patch 
gtk-chtheme-0.3.1/debian/patches/no-implicit-declarations.patch
--- gtk-chtheme-0.3.1/debian/patches/no-implicit-declarations.patch 
1969-12-31 16:00:00.0 -0800
+++ gtk-chtheme-0.3.1/debian/patches/no-implicit-declarations.patch 
2024-04-09 22:44:20.0 -0700
@@ -0,0 +1,19 @@
+Description: don't set GTK_DISABLE_DEPRECATED, deprecated APIs in use.
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066222
+Last-Update: 2024-04-09
+Forwarded: no
+
+Index: gtk-chtheme-0.3.1/Makefile
+===
+--- gtk-chtheme-0.3.1.orig/Makefile
 gtk-chtheme-0.3.1/Makefile
+@@ -5,7 +5,7 @@
+ 
+ LDFLAGS = $(shell $(PKG_CONFIG) --libs gtk+-2.0)
+ CFLAGS += -Wall
+-CFLAGS += $(shell $(PKG_CONFIG) --cflags gtk+-2.0) -DGTK_DISABLE_BROKEN 
-DGTK_DISABLE_DEPRECATED
++CFLAGS += $(shell $(PKG_CONFIG) --cflags gtk+-2.0) -DGTK_DISABLE_BROKEN
+ CFLAGS += -DPROJNAME='"$(PROJNAME)"' -DVERSION='"$(VERSION)"'
+ CPPFLAGS =
+ CXXFLAGS =
diff -Nru gtk-chtheme-0.3.1/debian/patches/series 
gtk-chtheme-0.3.1/debian/patches/series
--- gtk-chtheme-0.3.1/debian/patches/series 2020-03-28 16:34:21.0 
-0700
+++ gtk-chtheme-0.3.1/debian/patches/series 2024-04-09 22:43:09.0 
-0700
@@ -2,3 +2,4 @@
 deprecated-on-gtk3+.patch
 cross.patch
 fix_ftbfs.patch
+no-implicit-declarations.patch

Processed: Re: gtk-chtheme: FTBFS: theme_sel.c:113:5: error: implicit declaration of function ‘gtk_timeout_add’; did you mean ‘g_timeout_add’? [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066222 [src:gtk-chtheme] gtk-chtheme: FTBFS: theme_sel.c:113:5: error: 
implicit declaration of function ‘gtk_timeout_add’; did you mean 
‘g_timeout_add’? [-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1068251: marked as pending in glibc

[Aurelien Jarno]

Control: tag -1 pending

Hello,

Bug #1068251 in glibc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/glibc-team/glibc/-/commit/2aeb43031cb6bbcd1978c5329ffee010155c044f


debian/rules.d/build.mk: present glibc with a compiler that does not default to 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64, as upstream doesn't support this 
configuration. This has the consequence of hiding real issues found by the 
testsuite, but there is a consensus that this is the way to go for now. Thanks 
to Helmut Grohne for the hint and starting the discussion.  Closes: #1068251.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068251

Processed: Bug#1068251 marked as pending in glibc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068251 [src:glibc] glibc: FTBFS on 32-bit architectures due to GCC 
defaulting to 64-bit time_t
Added tag(s) pending.

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

Bug#1066645: gtkterm: FTBFS: ../src/interface.c:738:9: error: implicit declaration of function ‘g_sprintf’; did you mean ‘g_snprintf’? [-Werror=implicit-function-declaration]

[Steve Langasek]

Package: gtkterm
Followup-For: Bug #1066645
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gtkterm-1.2.1/debian/patches/no-implicit-declarations.patch 
gtkterm-1.2.1/debian/patches/no-implicit-declarations.patch
--- gtkterm-1.2.1/debian/patches/no-implicit-declarations.patch 1969-12-31 
16:00:00.0 -0800
+++ gtkterm-1.2.1/debian/patches/no-implicit-declarations.patch 2024-04-09 
22:49:04.0 -0700
@@ -0,0 +1,28 @@
+Description: add missing includes
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066645
+Last-Update: 2024-04-09
+Forwarded: no
+
+Index: gtkterm-1.2.1/src/interface.c
+===
+--- gtkterm-1.2.1.orig/src/interface.c
 gtkterm-1.2.1/src/interface.c
+@@ -79,6 +79,7 @@
+ #include "logging.h"
+ 
+ #include 
++#include 
+ #include 
+ 
+ guint id;
+Index: gtkterm-1.2.1/src/user_signals.c
+===
+--- gtkterm-1.2.1.orig/src/user_signals.c
 gtkterm-1.2.1/src/user_signals.c
+@@ -1,3 +1,5 @@
++#include 
++#include 
+ #include 
+ #include "interface.h"
+ 
diff -Nru gtkterm-1.2.1/debian/patches/series 
gtkterm-1.2.1/debian/patches/series
--- gtkterm-1.2.1/debian/patches/series 1969-12-31 16:00:00.0 -0800
+++ gtkterm-1.2.1/debian/patches/series 2024-04-09 22:48:12.0 -0700
@@ -0,0 +1 @@
+no-implicit-declarations.patch

Processed: Re: gtkterm: FTBFS: ../src/interface.c:738:9: error: implicit declaration of function ‘g_sprintf’; did you mean ‘g_snprintf’? [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066645 [src:gtkterm] gtkterm: FTBFS: ../src/interface.c:738:9: error: 
implicit declaration of function ‘g_sprintf’; did you mean ‘g_snprintf’? 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1066305: 3dchess: FTBFS: init.c:140:21: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration]

[Steve Langasek]

Package: 3dchess
Version: 0.8.1-21
Followup-For: Bug #1066305
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached the fix for this bug, which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru 3dchess-0.8.1/debian/patches/no-implicit-declarations.patch 
3dchess-0.8.1/debian/patches/no-implicit-declarations.patch
--- 3dchess-0.8.1/debian/patches/no-implicit-declarations.patch 1969-12-31 
16:00:00.0 -0800
+++ 3dchess-0.8.1/debian/patches/no-implicit-declarations.patch 2024-04-09 
13:23:33.0 -0700
@@ -0,0 +1,18 @@
+Description: fix missing declaration of time()
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066305
+Last-Update: 2024-04-09
+Forwarded: no
+
+Index: 3dchess-0.8.1/src/init.c
+===
+--- 3dchess-0.8.1.orig/src/init.c
 3dchess-0.8.1/src/init.c
+@@ -29,6 +29,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include "../include/machine.h"
+ #include "../include/3Dc.h"
+ 
diff -Nru 3dchess-0.8.1/debian/patches/series 
3dchess-0.8.1/debian/patches/series
--- 3dchess-0.8.1/debian/patches/series 2022-03-26 18:33:58.0 -0700
+++ 3dchess-0.8.1/debian/patches/series 2024-04-09 13:22:34.0 -0700
@@ -4,3 +4,4 @@
 13_machine.h.patch
 hardening.patch
 wasteful-CPU-consumption.patch
+no-implicit-declarations.patch

Processed: Re: 3dchess: FTBFS: init.c:140:21: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066305 [src:3dchess] 3dchess: FTBFS: init.c:140:21: error: implicit 
declaration of function ‘time’ [-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Processed: Re: aa3d: FTBFS: aa3d.c:37:30: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066274 [src:aa3d] aa3d: FTBFS: aa3d.c:37:30: error: implicit declaration 
of function ‘strcmp’ [-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1066274: aa3d: FTBFS: aa3d.c:37:30: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration]

[Steve Langasek]

Package: aa3d
Version: 1.0-8.2
Followup-For: Bug #1066274
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a fix for this bug.

This fix has been uploaded to Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru aa3d-1.0/debian/patches/no-implicit-declarations.patch 
aa3d-1.0/debian/patches/no-implicit-declarations.patch
--- aa3d-1.0/debian/patches/no-implicit-declarations.patch  1969-12-31 
16:00:00.0 -0800
+++ aa3d-1.0/debian/patches/no-implicit-declarations.patch  2024-04-09 
13:42:30.0 -0700
@@ -0,0 +1,18 @@
+Description: add missing string.h include
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066274
+Last-Update: 2024-04-09
+Forwarded: no
+
+Index: aa3d-1.0/aa3d.c
+===
+--- aa3d-1.0.orig/aa3d.c
 aa3d-1.0/aa3d.c
+@@ -22,6 +22,7 @@
+  */
+ #include 
+ #include 
++#include 
+ static char data[65536 / 2];
+ int main(int argc, char **argv)
+ {
diff -Nru aa3d-1.0/debian/patches/series aa3d-1.0/debian/patches/series
--- aa3d-1.0/debian/patches/series  1969-12-31 16:00:00.0 -0800
+++ aa3d-1.0/debian/patches/series  2024-04-09 13:41:03.0 -0700
@@ -0,0 +1 @@
+no-implicit-declarations.patch

Bug#1067108: alien-arena: FTBFS with -Werror=implicit-function-declaration

[Steve Langasek]

Package: alien-arena
Followup-For: Bug #1067108
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a fix for this bug, which has been uploaded to Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru alien-arena-7.71.3+dfsg/debian/patches/no-implicit-declarations.patch 
alien-arena-7.71.3+dfsg/debian/patches/no-implicit-declarations.patch
--- alien-arena-7.71.3+dfsg/debian/patches/no-implicit-declarations.patch   
1969-12-31 16:00:00.0 -0800
+++ alien-arena-7.71.3+dfsg/debian/patches/no-implicit-declarations.patch   
2024-04-09 13:53:07.0 -0700
@@ -0,0 +1,18 @@
+Description: add missing include
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1067108
+Last-Update: 2024-04-09
+Forwarded: no
+
+Index: alien-arena-7.71.3+dfsg/source/game/g_unlagged.c
+===
+--- alien-arena-7.71.3+dfsg.orig/source/game/g_unlagged.c
 alien-arena-7.71.3+dfsg/source/game/g_unlagged.c
+@@ -21,6 +21,7 @@
+ #include "config.h"
+ #endif
+ 
++#include "qcommon/qcommon.h"
+ #include "g_local.h"
+ 
+ /*
diff -Nru alien-arena-7.71.3+dfsg/debian/patches/series 
alien-arena-7.71.3+dfsg/debian/patches/series
--- alien-arena-7.71.3+dfsg/debian/patches/series   2023-02-12 
08:19:19.0 -0800
+++ alien-arena-7.71.3+dfsg/debian/patches/series   2024-04-09 
13:51:57.0 -0700
@@ -6,3 +6,4 @@
 odeconfig.patch
 irc.patch
 http11.patch
+no-implicit-declarations.patch

Processed: Re: alien-arena: FTBFS with -Werror=implicit-function-declaration

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1067108 [src:alien-arena] alien-arena: FTBFS with 
-Werror=implicit-function-declaration
Added tag(s) patch.

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

Bug#1068030: FTBFS on armel: undefined reference to `__atomic_load_8'

[Jeremy Sowden]

On 2024-04-09, at 15:24:28 +0100, Jeremy Sowden wrote:
> On 2024-03-30, at 02:03:57 +0500, Andrey Rakhmatullin wrote:
> > Source: maildir-utils
> > Version: 1.10.8-2
> > Severity: serious
> > Tags: ftbfs
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=maildir-utils=armel=1.10.8-2%2Bb2=1711722478=0
> > 
> > /usr/bin/ld: lib/index/libmu-index.a.p/mu-indexer.cc.o: in function
> > `std::__atomic_base::store(long long, std::memory_order)':
> > /usr/include/c++/13/bits/atomic_base.h:481:(.text+0xb14): undefined 
> > reference
> > to `__atomic_store_8'
> > /usr/bin/ld: lib/index/libmu-index.a.p/mu-indexer.cc.o: in function
> > `std::__atomic_base::load(std::memory_order) const':
> > /usr/include/c++/13/bits/atomic_base.h:505:(.text+0x1384): undefined 
> > reference
> > to `__atomic_load_8'
> 
> This is a 64-bit time_t bug.  Will investigate.

gcc includes a library, libatomic.so, which supplies implementations of
atomic operations which cannot be implemented by native instructions.
On armel, this is required for 64 bit types:

$ cat test.cc 
#include 
#include 

using namespace std;

int
main(void)
{
atomic_llong x(0);
long long y = 123;

x.store(y);

cout << x << endl;
}
$ g++ test.cc -o test 
/usr/bin/ld: /tmp/ccVWAQDN.o: in function `main':
test.cc:(.text+0xe0): undefined reference to `__atomic_store_8'
/usr/bin/ld: /tmp/ccVWAQDN.o: in function `std::__atomic_base::operator long long() const':

test.cc:(.text._ZNKSt13__atomic_baseIxEcvxEv[_ZNKSt13__atomic_baseIxEcvxEv]+0x98):
 undefined reference to `__atomic_load_8'
collect2: error: ld returned 1 exit status
$ g++ test.cc -o test -latomic
$ ./test 
123

Thus it is now required for 64-bit `time_t`.

This doesn't appear to be documented anywhere apart from other bug
reports.  May be worth broaching with upstream.

J.


signature.asc
Description: PGP signature

Processed: bullseye-pu: package json-smart/2.2-2+deb11u1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:json-smart
Bug #1068694 [release.debian.org] bullseye-pu: package json-smart/2.2-2+deb11u1
Added indication that 1068694 affects src:json-smart
> block 1039985 with -1
Bug #1039985 [libjson-smart-java] libjson-smart-java: buster-lts has a newer 
version than bullseye/bookworm/sid
1039985 was not blocked by any bugs.
1039985 was not blocking any bugs.
Added blocking bug(s) of 1039985: 1068694
> block 1033474 with -1
Bug #1033474 [src:json-smart] json-smart: CVE-2023-1370
1033474 was not blocked by any bugs.
1033474 was not blocking any bugs.
Added blocking bug(s) of 1033474: 1068694

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

Bug#1066209: Pending upload

[Patrick Winnertz]

Control: tags 1066209 + pending

I've updated the VCS, a upload is pending.

With best regards
Patrick

Processed: Pending upload

[Debian Bug Tracking System]

Processing control commands:

> tags 1066209 + pending
Bug #1066209 [src:aprsdigi] aprsdigi: FTBFS: libax25ext.c:101:7: error: 
implicit declaration of function ‘ax25_aton_entry’ 
[-Werror=implicit-function-declaration]
Ignoring request to alter tags of bug #1066209 to the same tags previously set

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

Bug#1054795: system-config-printer: FTBFS: dh_install: error: missing files, aborting

[Peter Green]

Ubuntu has made a couple of changes that look like they may relate to this 
issue.

Changelog for version 1.5.18-1ubuntu6 says

"Fix installation of cupshelpers module with Python 3.12."

Changelog for version 1.5.18-1ubuntu7 says

"Drop build dependency on python3-distutils."

Diffs are available at

http://launchpadlibrarian.net/720405816/system-config-printer_1.5.18-1ubuntu5_1.5.18-1ubuntu6.diff.gz

http://launchpadlibrarian.net/720655573/system-config-printer_1.5.18-1ubuntu6_1.5.18-1ubuntu7.diff.gz

Can someone review whether these changes are appropriate and fix the issue?
system-config-printer is a blocker for the time_t transition.

Bug#1039985: libjson-smart-java: buster-lts has a newer version than bullseye/bookworm/sid

[Andreas Beckmann]

Followup-For: Bug #1039985
Control: tag -1 pending
Control: tag 1033474 pending
Control: fixed 1033474 2.2-2+deb10u1

In order to get the version skew between buster-lts and bullseye+ fixed,
I've prepared a NMU for sid (versioned 2.2-2.1) that simply rebuilds the
package from buster-lts and uploaded it to DELAYED/10.

Furthermore I've opened PU requests for bullseye and bookworm:
#1068694, #1068695

My changes can be found https://salsa.debian.org/anbe/json-smart
Signed tags will be added there once the packages have been accepted in
the archive.


Andreas

Processed: Re: libjson-smart-java: buster-lts has a newer version than bullseye/bookworm/sid

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1039985 [libjson-smart-java] libjson-smart-java: buster-lts has a newer 
version than bullseye/bookworm/sid
Added tag(s) pending.
> tag 1033474 pending
Bug #1033474 [src:json-smart] json-smart: CVE-2023-1370
Added tag(s) pending.
> fixed 1033474 2.2-2+deb10u1
Bug #1033474 [src:json-smart] json-smart: CVE-2023-1370
The source 'json-smart' and version '2.2-2+deb10u1' do not appear to match any 
binary packages
Marked as fixed in versions json-smart/2.2-2+deb10u1.

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

Bug#1068251: glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t

[Helmut Grohne]

Hi Aurelien,

On Mon, Apr 08, 2024 at 11:24:40PM +0200, Aurelien Jarno wrote:
> Thanks for you analysis and your patch. In short your proposal is to
> extend the initial patch from Steve to fully hide the fact that the
> compiler default to -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64.
> 
> This indeed works and fixes the FTBFS. However it seems that, at least
> for some of the issues, it just hides them. For instance the wrong type
> for timeval.tv_usec, reported by Simon upstream [1], was detected by the
> conformance tests. Quoting utmpx.h/conform.out:

I think this needs a more nuanced look. From the comments in the
conformance test suite, it is evident that it expects to be run without
_FILE_OFFSET_BITS and _TIME_BITS. Many of the symbols it requires to
exist only exist when these macros are unset. The conformance test suite
has a comment saying that it should be testing the case where
_FILE_OFFSET_BITS is defined, but it currently does not provide
expectations for that case.

Before we can reasonably run the conformance test suite with these
macros set (and really, the test suite should be in control of these
macros), we cannot reasonably use it with them set. Let us now imagine a
future where the conformance test suite has been extended to provide
expectations (which in lots of cases means that *64 symbols disappear
when -D_FILE_OFFSET_BITS=64). Then what still remains is Simon's issue:

> | /tmp/tmp98wzaavx/test.c:4:35: error: conflicting types for ‘b2_10’; have 
> ‘__suseconds64_t’ {aka ‘long long int’}
> | 4 | extern __typeof__ (a2_10.tv_usec) b2_10;
> |   |   ^
> | /tmp/tmp98wzaavx/test.c:3:20: note: previous declaration of ‘b2_10’ with 
> type ‘suseconds_t’ {aka ‘long int’}
> | 3 | extern suseconds_t b2_10;
> |   |^
> | FAIL: Type of member tv_usec

Indeed, this is not something that can easily be fixed and where
upstream is still debating on what the correct solution should be. It
also is an issue that existed for a long time. If you head over to a
bookworm glibc and enable -D_TIME_BITS=64 there, you'll also notice that
tv_usec and suseconds_t have different sizes. So yes, this is a bug, but
it is not one that is directly related to Debian changing the default.
We merely increased the visibility of this problem that existed earlier
already.

Given that
 * the issue is already present in bookworm,
 * there are two mutually exclusive solutions and
 * upstream is still discussing the best solution
I recommend deferring this aspect.

> And we know it is the reason for the FTBFS of libflorist [2], so should
> we just ignore that issue anyway?

The libflorist issue likely is a consequence. It arises from
gnat_to_gnu_field where GNAT verifies that the value (of type
suseconds_t) to be assigned to a field (tv_usec) has the matching size.
This is directly based on the POSIX expectation and will be fixed with
the glibc issue.

How about filing a separate bug with glibc that tracks this POSIX
divergence and mark the libflorist bug as being blocked by this other
glibc bug? It can be RC or not, but since it affects bookworm, it won't
block testing migration.

Helmut

Bug#1066209: marked as done (aprsdigi: FTBFS: libax25ext.c:101:7: error: implicit declaration of function ‘ax25_aton_entry’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 10:49:05 +
with message-id 
and subject line Bug#1066209: fixed in aprsdigi 3.10.0-6
has caused the Debian Bug report #1066209,
regarding aprsdigi: FTBFS: libax25ext.c:101:7: error: implicit declaration of 
function ‘ax25_aton_entry’ [-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.)


-- 
1066209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aprsdigi
Version: 3.10.0-5
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 -DPACKAGE_NAME=\"aprsdigi\" -DPACKAGE_TARNAME=\"aprsdigi\" 
> -DPACKAGE_VERSION=\"3.10.0\" -DPACKAGE_STRING=\"aprsdigi\ 3.10.0\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"aprsdigi\" 
> -DVERSION=\"3.10.0\" -DHAVE_LIBAX25=1 -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 
> -DHAVE_SYS_WAIT_H=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_IOCTL_H=1 
> -DHAVE_SYS_TIME_H=1 -DHAVE_UNISTD_H=1 -DIPV6=1 -DRETSIGTYPE=void 
> -DHAVE_WAIT3=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_STRDUP=1 
> -DHAVE_STRTOL=1 -DHAVE_UNAME=1 -DHAVE_SHMCTL=1 -DUSE_SHM=1 -I.   -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 -c 
> -o aprsmon.o aprsmon.c
> libax25ext.c: In function ‘parse_cooked_ax25’:
> libax25ext.c:101:7: error: implicit declaration of function ‘ax25_aton_entry’ 
> [-Werror=implicit-function-declaration]
>   101 |   ax25_aton_entry(*frame,calls->ax_from_call.ax25_call);
>   |   ^~~
> fiforead.c:23:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>23 | main(int argc, char **argv)
>   | ^~~~
> gcc -DPACKAGE_NAME=\"aprsdigi\" -DPACKAGE_TARNAME=\"aprsdigi\" 
> -DPACKAGE_VERSION=\"3.10.0\" -DPACKAGE_STRING=\"aprsdigi\ 3.10.0\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"aprsdigi\" 
> -DVERSION=\"3.10.0\" -DHAVE_LIBAX25=1 -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 
> -DHAVE_SYS_WAIT_H=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_IOCTL_H=1 
> -DHAVE_SYS_TIME_H=1 -DHAVE_UNISTD_H=1 -DIPV6=1 -DRETSIGTYPE=void 
> -DHAVE_WAIT3=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_STRDUP=1 
> -DHAVE_STRTOL=1 -DHAVE_UNAME=1 -DHAVE_SHMCTL=1 -DUSE_SHM=1 -I.   -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 -c 
> -o aprsshm.o aprsshm.c
> testparse.c:28:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>28 | main()
>   | ^~~~
> testparse.c: In function ‘main’:
> testparse.c:52:33: warning: format ‘%x’ expects argument of type ‘unsigned 
> int’, but argument 3 has type ‘unsigned char *’ [-Wformat=]
>52 |   fprintf(stderr,"data @0x%0x (len %d): %s\n",bp,buflen,bp);
>   |   ~~^ ~~
>   | | |
>   | unsigned int  unsigned char *
>   |   %0hhn
> testparse.c:57:34: warning: format ‘%x’ expects argument of type ‘unsigned 
> int’, but argument 3 has type ‘unsigned char *’ [-Wformat=]
>57 |   fprintf(stderr,"cooked@0x%0x (len %d): %s\n",obuf,olen,obuf);/* 
> ?? */
>   |~~^ 
>   |  | |
>   |  unsigned int  unsigned char *
>   |%0hhn
> testparse.c:58:33: warning: format ‘%x’ expects argument of type ‘unsigned 
> int’, but argument 3 has type ‘unsigned char *’ [-Wformat=]
>58 |   

Bug#1068698: hdf-eos5 2:2.0-2 silently reverts the 64-bit time_t transition

[Julian Andres Klode]

Source: hdf-eos5
Severity: serious
X-Debbugs-Cc: j...@debian.org

hdf-eos5 2:2.0-2 ignores the hdf-eos5 2:2.0-1.1 NMU that introduced the
time_t renames (that was Bug##1063118), causing misbuilt libhe5-hdfeos0
with the new ABI, potentially breaking applications built against it.

-- System Information:
Debian Release: trixie/sid
  APT prefers noble-updates
  APT policy: (500, 'noble-updates'), (500, 'noble'), (500, 'mantic-security'), 
(100, 'noble-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.8.0-20-generic (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1054449: pesign: Missing Pre-Depends on passwd

[Andreas Beckmann]

Followup-For: Bug #1054449
Control: tag -1 sid trixie

This is only an issue from trixie onwards where apt has dropped the
dependency on adduser, breaking the dependency chain
  apt (Priority: required) -> adduser -> passwd


Andreas

Processed: Re: pesign: Missing Pre-Depends on passwd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 sid trixie
Bug #1054449 {Done: Steve McIntyre <93...@debian.org>} [pesign] pesign: Missing 
Pre-Depends on passwd
Added tag(s) sid and trixie.

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

Bug#1063077: syslog-ng: identified for time_t transition but no ABI in shlibs

[Shengjing Zhu]

On Mon, Apr 8, 2024 at 9:15 PM Attila Szalay  wrote:
>
> Ok. I re-checked the patch and realized that I checked the only wrong
> module (the only one which is arch all and not any).
>
> So my apologies for the fuzz and will apply the patch with the
> appropriate changes.
>
> But here my original reply too:
>
> I admit that I joined late to this conversation. But my complain is not
> about the time_t change.
>
> My complain is the contradiction between two thing:
> 1. https://wiki.debian.org/binNMU says that I should declar[e]
> dependency between an arch: all to an arch: any package: Depends: foo
> (>= ${source:Version}), foo (<< ${source:Version}.1~)
>

This is for arch: all -> arch: any. However I see most syslog-ng-mod-*
packages are arch: any. So it should just use strict equal on
syslog-ng-core.
What I'm confused about is some syslog-ng-mod-* packages are arch:
all, which don't have .so in it. Then why do they need to depend on
syslog-ng-core?

> 2. The bug report ask to depend on 'syslog-ng-core (=
> $${binary:Version})'
>
> This two is contradict and because syslog-ng complies with the binNMU
> request, I really reluctant to change that. Especially because in that
> case another ticket will be created in no-time to revert it.
>
> This is from the proposed changelog:
> +  * Adjust shlibs for syslog-ng-core to use a strict versioned depends;
> +previously, modules used >=, << dependencies which did not account for
> +the possibility of ABI skew in a binNMU, which is exactly what happens
> +with the 64-bit time_t transition.
>
> And my question is again, is the rules really changed or we bend the
> rules just because of one transition?

-- 
Shengjing Zhu

Bug#1067784: marked as done (Doesn't contain libpmix.so.2)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 09:35:17 +
with message-id 
and subject line Bug#1067784: fixed in openmpi 4.1.6-9
has caused the Debian Bug report #1067784,
regarding Doesn't contain libpmix.so.2
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.)


-- 
1067784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpmix2t64
Version: 5.0.2-1
Severity: grave

After installing the package there is no /usr/lib/x86_64-linux-
gnu/libpmix.so.2.

Looking at the contents of .deb, there are:

./usr/lib/x86_64-linux-gnu/pmix2/lib/libpmix.so.2.13.2
./usr/lib/x86_64-linux-gnu/libpmix.so.2 -> pmix2/lib/libpmix.so.2.13.1
./usr/lib/x86_64-linux-gnu/libpmix.so.2.13.1 -> pmix2/lib/libpmix.so.2.13.1
./usr/lib/x86_64-linux-gnu/pmix2/lib/libpmix.so.2 -> libpmix.so.2.13.2

So the symlinks in the public path are broken, and after installing the package
they don't even exist at all (I assume ldconfig removes them?).


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

Versions of packages libpmix2t64 depends on:
ii  libc6   2.37-15.1
ii  libevent-core-2.1-7t64  2.1.12-stable-8.1+b1
ii  libevent-pthreads-2.1-7t64  2.1.12-stable-8.1+b1
ii  libhwloc-plugins2.10.0-1+b1
ii  libhwloc15  2.10.0-1+b1
ii  libmunge2   0.5.15-4
ii  zlib1g  1:1.3.dfsg-3.1

libpmix2t64 recommends no packages.

libpmix2t64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openmpi
Source-Version: 4.1.6-9
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
openmpi, 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.
Alastair McKinstry  (supplier of updated openmpi 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: SHA256

Format: 1.8
Date: Tue, 09 Apr 2024 09:17:18 +0100
Source: openmpi
Architecture: source
Version: 4.1.6-9
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 1067784 1068612
Changes:
 openmpi (4.1.6-9) unstable; urgency=medium
 .
   * Ship pmix on 32-bit systems; ensure we break/depend on libpmix on 32-bit
 systems. Closes: #1067784, #1068612
Checksums-Sha1:
 8dfd2f31432f079f115d44dee8a6b230c72de269 2828 openmpi_4.1.6-9.dsc
 ab88c965b1840254109c46ed6bb77eb93d49e651 69592 openmpi_4.1.6-9.debian.tar.xz
Checksums-Sha256:
 200bda997df9520e80d2c3de3cacaa540a64ecf93404f8a105134844187c175f 2828 
openmpi_4.1.6-9.dsc
 ce3ba13400dd5deaabf20a3869dc6b10d15a72f9609c4a21ddaaa1ad71c806ab 69592 
openmpi_4.1.6-9.debian.tar.xz
Files:
 666d07aad2a765a5edfd61df88e102d7 2828 net optional openmpi_4.1.6-9.dsc
 b3a1445cff1cf0265542320f5eac8cef 69592 net optional 
openmpi_4.1.6-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmYVB1AACgkQy+a7Tl2a
06Wzyg/9GEeq2YKMa/A+qLzqiyOB85ZPuAgm0tlKdiFNm4NdltM7P+GgCZYfXLix
m8YEcHh5qSHgNr9QzuhgunOhZs4o9kOdkWDqBoPgGj1EA7SrVlwYhIDSkfJzvG52
zXdEo0j4LGCJ/CRZW8FWcG6dMvbww/ryaochC5efGAhdp6JQI/JkMZOeL+e8aIdj
c6BfDeEckRuzHrpmgINxZoZGtGbvfp9gX5dxMrpl/2th0vngKc5d3HIIA7eqMnOZ
6WyUF/djyO++pvXxVrv+ivRtaGg2RXkt1WQ/6QLmQMZHuqHRFoeSOixnmSkP570H
uQ8bPi2e4lC3SIgSF0sF9LVlN9RV1WuzCZLXTco4e9miysqElmjN9rtx5+dGO0ab
kovrFSvomfvIAfiPqj8RfdJ5dWOkAnz053ab//W0Ck/hCuZSU0c9KNF++WDQYaEU
ymsmJtyfYuZLdlp3pvD5sBrDmiMj4nWo/L+/U+DNw2/hrOtauvhEl+WQIAQTG4Ze
zPvh4SIIOd4smuyZcK2U0BxFB4E86xwtv84tDwdXSEuu1/w2gl0JMDxqbjHHHQ2O

Bug#1068612: marked as done (libopenmpi3t64: mca_pmix_pmix3x.so: undefined symbol: pmix_value_load on 32bit)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 09:35:17 +
with message-id 
and subject line Bug#1068612: fixed in openmpi 4.1.6-9
has caused the Debian Bug report #1068612,
regarding libopenmpi3t64: mca_pmix_pmix3x.so: undefined symbol: pmix_value_load 
on 32bit
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.)


-- 
1068612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenmpi3t64
Version: 4.1.6-8
Severity: serious
Tags: ftbfs
Control: affects -1 src:hypre src:h5py src:fenics-dolfinx src:dune-uggrid 
src:dolfinx-mpc src:dolfin src:liggghts

https://buildd.debian.org/status/fetch.php?pkg=dune-uggrid=i386=2.9.0-2%2Bb3=1712511034=0

...
orted: symbol lookup error: 
/usr/lib/i386-linux-gnu/openmpi/lib/openmpi3/mca_pmix_pmix3x.so: undefined 
symbol: pmix_value_load
...
--- End Message ---
--- Begin Message ---
Source: openmpi
Source-Version: 4.1.6-9
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
openmpi, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated openmpi 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: SHA256

Format: 1.8
Date: Tue, 09 Apr 2024 09:17:18 +0100
Source: openmpi
Architecture: source
Version: 4.1.6-9
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 1067784 1068612
Changes:
 openmpi (4.1.6-9) unstable; urgency=medium
 .
   * Ship pmix on 32-bit systems; ensure we break/depend on libpmix on 32-bit
 systems. Closes: #1067784, #1068612
Checksums-Sha1:
 8dfd2f31432f079f115d44dee8a6b230c72de269 2828 openmpi_4.1.6-9.dsc
 ab88c965b1840254109c46ed6bb77eb93d49e651 69592 openmpi_4.1.6-9.debian.tar.xz
Checksums-Sha256:
 200bda997df9520e80d2c3de3cacaa540a64ecf93404f8a105134844187c175f 2828 
openmpi_4.1.6-9.dsc
 ce3ba13400dd5deaabf20a3869dc6b10d15a72f9609c4a21ddaaa1ad71c806ab 69592 
openmpi_4.1.6-9.debian.tar.xz
Files:
 666d07aad2a765a5edfd61df88e102d7 2828 net optional openmpi_4.1.6-9.dsc
 b3a1445cff1cf0265542320f5eac8cef 69592 net optional 
openmpi_4.1.6-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmYVB1AACgkQy+a7Tl2a
06Wzyg/9GEeq2YKMa/A+qLzqiyOB85ZPuAgm0tlKdiFNm4NdltM7P+GgCZYfXLix
m8YEcHh5qSHgNr9QzuhgunOhZs4o9kOdkWDqBoPgGj1EA7SrVlwYhIDSkfJzvG52
zXdEo0j4LGCJ/CRZW8FWcG6dMvbww/ryaochC5efGAhdp6JQI/JkMZOeL+e8aIdj
c6BfDeEckRuzHrpmgINxZoZGtGbvfp9gX5dxMrpl/2th0vngKc5d3HIIA7eqMnOZ
6WyUF/djyO++pvXxVrv+ivRtaGg2RXkt1WQ/6QLmQMZHuqHRFoeSOixnmSkP570H
uQ8bPi2e4lC3SIgSF0sF9LVlN9RV1WuzCZLXTco4e9miysqElmjN9rtx5+dGO0ab
kovrFSvomfvIAfiPqj8RfdJ5dWOkAnz053ab//W0Ck/hCuZSU0c9KNF++WDQYaEU
ymsmJtyfYuZLdlp3pvD5sBrDmiMj4nWo/L+/U+DNw2/hrOtauvhEl+WQIAQTG4Ze
zPvh4SIIOd4smuyZcK2U0BxFB4E86xwtv84tDwdXSEuu1/w2gl0JMDxqbjHHHQ2O
bKZsAaSh/LO5rVog++q2HC4t+4WO/+H3rU5TJV8B3CLMRKLExhM2j7ie9rmYnXr0
HGczYgxW8H9niQma81t4K2IicZs7fhM6cz/LZ25tGgVnSH68vFo=
=Jwp1
-END PGP SIGNATURE-



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

Bug#1068656: marked as pending in pgsql-http

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #1068656 in pgsql-http reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/postgresql/pgsql-http/-/commit/f92a339d44e621a56ee174ccaacb9466d819cbb5


Disable build-time tests. (Closes: #1068656)

Skip autopkgtest when networking is unavailable.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068656

Processed: Bug#1068656 marked as pending in pgsql-http

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068656 [src:pgsql-http] pgsql-http accesses the internet during the build
Added tag(s) pending.

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

Bug#1065951: patch applied as MR!6

[Philip Hands]

Hi,

Just in case it helps, I've applied Michael's patch, and opened an MR on salsa:

  https://salsa.debian.org/virtualsquare-team/vde2/-/merge_requests/6

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil

Bug#1068038: marked as done (FTBFS: error: ‘struct input_event’ has no member named ‘time’)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 10:04:28 +
with message-id 
and subject line Bug#1068038: fixed in flightgear 1:2020.3.18+dfsg-1.1
has caused the Debian Bug report #1068038,
regarding FTBFS: error: ‘struct input_event’ has no member named ‘time’
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.)


-- 
1068038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flightgear
Version: 1:2020.3.18+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=flightgear=armhf=1%3A2020.3.18%2Bdfsg-1%2Bb2=1711729288=0

/<>/src/Input/FGLinuxEventInput.cxx: In member function ‘virtual
void FGLinuxInputDevice::Send(const char*, double)’:
/<>/src/Input/FGLinuxEventInput.cxx:418:7: error: ‘struct
input_event’ has no member named ‘time’
  418 |   evt.time.tv_sec = 0;
  |   ^~~~
/<>/src/Input/FGLinuxEventInput.cxx:419:7: error: ‘struct
input_event’ has no member named ‘time’
  419 |   evt.time.tv_usec = 0;
  |   ^~~~


-- 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: flightgear
Source-Version: 1:2020.3.18+dfsg-1.1
Done: Dmitry Shachnev 

We believe that the bug you reported is fixed in the latest version of
flightgear, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated flightgear 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: Sun, 07 Apr 2024 12:30:07 +0300
Source: flightgear
Architecture: source
Version: 1:2020.3.18+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian FlightGear Crew 
Changed-By: Dmitry Shachnev 
Closes: 1068038
Changes:
 flightgear (1:2020.3.18+dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add a patch to fix build with 64-bit time_t on 32-bit architectures.
 Closes: #1068038.
   * Bump libsimgear-dev build-dependency to a version that is built with
 the new time_t ABI.
Checksums-Sha1:
 9ae388214a264c74f1e49545d2903f0f3d7346ae 2741 flightgear_2020.3.18+dfsg-1.1.dsc
 847cec0da373ce71af64952dd5326c1e26e63121 27624 
flightgear_2020.3.18+dfsg-1.1.debian.tar.xz
 5ff7a2a091377625a1751af8792721196675243a 14560 
flightgear_2020.3.18+dfsg-1.1_source.buildinfo
Checksums-Sha256:
 1a6cc9951a182a7fd1f1b05334696c3a4936341a20c28a37c1f7120c0b79d9d7 2741 
flightgear_2020.3.18+dfsg-1.1.dsc
 680aeffcd1553f0e15c6f9afaa691a68453f34d6a887cc2539d915154ee411b6 27624 
flightgear_2020.3.18+dfsg-1.1.debian.tar.xz
 8e3c17a389958b5c71ce3ec086b165679c2a8e913629567e7b4e83f1af9efaaf 14560 
flightgear_2020.3.18+dfsg-1.1_source.buildinfo
Files:
 083791ac5a7368da27a0d8e4133af558 2741 games optional 
flightgear_2020.3.18+dfsg-1.1.dsc
 9603637c59f9dd1e7a1de2cfd149ab4e 27624 games optional 
flightgear_2020.3.18+dfsg-1.1.debian.tar.xz
 a7cf2cfbf7b03a3771be8f1f8006e927 14560 games optional 
flightgear_2020.3.18+dfsg-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEq2sdvrA0LydXHe1qsmYUtFL0RrYFAmYSaLcTHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRCyZhS0UvRGtrO+EAC1oZOlsUfS7X4mxVVIViYUKlYpCY7b
31YN9vtewKxeNhDp5KRcGC5vb+Nf9mt9eh4jRylQfl+TxsFGvMiTbfztxQy3NuMz
Xq7/JnOY6Hy6ZRymB7F57yvvNVwXyvGLrm+vkEcQgyC/2jBMlgbjMxShOYCwH92z
tL9KoectBrNrqUeFHTkEs0dwDig0ONeUsH7xCgbLaLBdRSN+eVfQ/9EVwikUrKDS
uRMAit4i1yxtOvKtWinwsQ9GVnhdM4tFUjEU/qLbI/pKyfxuHH7gmemxQKwgJPfy
oXNZFEGuzhAGLvgg2FJKmYie5aRdymsmmbhzkOUBc2XXzhkXydEPR6gVDAYZEu87
tSxjLMTtZdWVjuELylEm4NilWcSieYCjaOV1WWQeJjD1Lx5mZrqZYGruQxAefROi

Processed: Bug#1066209 marked as pending in aprsdigi

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066209 [src:aprsdigi] aprsdigi: FTBFS: libax25ext.c:101:7: error: 
implicit declaration of function ‘ax25_aton_entry’ 
[-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1066209: marked as pending in aprsdigi

[Patrick Winnertz]

Control: tag -1 pending

Hello,

Bug #1066209 in aprsdigi reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian-hamradio-team/aprsdigi/-/commit/42fb7fdf1e008696134863116f7748fc6b1d93ad


Include missing headers so that the library builds again. (Closes: #1066209)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066209

Processed: bookworm-pu: package json-smart/2.2-2+deb12u1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:json-smart
Bug #1068695 [release.debian.org] bookworm-pu: package json-smart/2.2-2+deb12u1
Added indication that 1068695 affects src:json-smart
> block 1039985 with -1
Bug #1039985 [libjson-smart-java] libjson-smart-java: buster-lts has a newer 
version than bullseye/bookworm/sid
1039985 was blocked by: 1068694
1039985 was not blocking any bugs.
Added blocking bug(s) of 1039985: 1068695
> block 1033474 with -1
Bug #1033474 [src:json-smart] json-smart: CVE-2023-1370
1033474 was blocked by: 1068694
1033474 was not blocking any bugs.
Added blocking bug(s) of 1033474: 1068695

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

Bug#1068696: haskell-hourglass FTBFS on armel and armhf

[Peter Green]

Package: haskell-hourglass
Version: 0.2.15-5
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t

The recent binnmus of haskell-hourglass on armel and armhf
failed to build with test failures.


calendar: FAIL
  *** Failed! (after 44 tests):
  Exception:
expected: -10088515868s got: -1498581276s
CallStack (from HasCallStack):
  error, called at tests/Tests.hs:120:25 in main:Main
  -10088515868s
  Use --quickcheck-replay=164206 to reproduce.
  Use -p '/calendar/' to rerun this test only.





iso8601 date: FAIL
  *** Failed! (after 42 tests):
  Exception:
expected: "2085-11-16" got: "1949-10-11"
CallStack (from HasCallStack):
  error, called at tests/Tests.hs:120:25 in main:Main
  3656792852s
  Use --quickcheck-replay=277582 to reproduce.
  Use -p '/formating.iso8601 date/' to rerun this test only.





custom-1: FAIL
  *** Failed! (after 2 tests):
  Exception:
expected: DateTime {dtDate = Date {dateYear = 2081, dateMonth = 
December, dateDay = 8}, dtTime = TimeOfDay {todHour = 13h, todMin = 59m, todSec 
= 21s, todNSec = 24752790ns}} got: DateTime {dtDate = Date {dateYear = 1945, 
dateMonth = November, dateDay = 2}, dtTime = TimeOfDay {todHour = 7h, todMin = 
31m, todSec = 5s, todNSec = 24752790ns}}
CallStack (from HasCallStack):
  error, called at tests/Tests.hs:120:25 in main:Main
  DateTime {dtDate = Date {dateYear = 2081, dateMonth = December, dateDay = 
8}, dtTime = TimeOfDay {todHour = 13h, todMin = 59m, todSec = 21s, todNSec = 
24752790ns}}
  Use --quickcheck-replay=893847 to reproduce.
  Use -p '/custom-1/' to rerun this test only.
custom-2: FAIL
  *** Failed! (after 1 test):
  Exception:
expected: DateTime {dtDate = Date {dateYear = 2132, dateMonth = August, 
dateDay = 11}, dtTime = TimeOfDay {todHour = 16h, todMin = 38m, todSec = 47s, 
todNSec = 5036393ns}} got: DateTime {dtDate = Date {dateYear = 1996, dateMonth 
= July, dateDay = 5}, dtTime = TimeOfDay {todHour = 10h, todMin = 10m, todSec = 
31s, todNSec = 5036393ns}}
CallStack (from HasCallStack):
  error, called at tests/Tests.hs:120:25 in main:Main
  DateTime {dtDate = Date {dateYear = 2132, dateMonth = August, dateDay = 
11}, dtTime = TimeOfDay {todHour = 16h, todMin = 38m, todSec = 47s, todNSec = 
5036393ns}}
  Use --quickcheck-replay=738259 to reproduce.
  Use -p '/custom-2/' to rerun this test only.
  Regression Tests
Real instance of ElapsedP (#33):  OK
Real instance of ElapsedP (#33) (2):  OK

4 out of 21 tests failed (0.03s)



I strongly suspect this is related to the time64 transition.

Bug#1068572: tgt: diff for NMU version 1:1.0.85-1.2

[Chris Hofstaedtler]

Control: tags 1068572 + patch
Control: tags 1068572 + pending

Dear maintainer,

I've prepared an NMU for tgt (versioned as 1:1.0.85-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Chris

diff -Nru tgt-1.0.85/debian/changelog tgt-1.0.85/debian/changelog
--- tgt-1.0.85/debian/changelog	2023-11-17 22:35:38.0 +0100
+++ tgt-1.0.85/debian/changelog	2024-04-09 09:28:44.0 +0200
@@ -1,3 +1,11 @@
+tgt (1:1.0.85-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Stop building tgt-rbd on 32bit archs (Closes: #1068572)
+  * Replace Build-Depends: pkg-config (deprecated) with pkgconf
+
+ -- Chris Hofstaedtler   Tue, 09 Apr 2024 09:28:44 +0200
+
 tgt (1:1.0.85-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru tgt-1.0.85/debian/control tgt-1.0.85/debian/control
--- tgt-1.0.85/debian/control	2023-11-17 22:35:38.0 +0100
+++ tgt-1.0.85/debian/control	2024-04-09 09:28:44.0 +0200
@@ -3,8 +3,10 @@
 Priority: optional
 Maintainer: Apollon Oikonomopoulos 
 Build-Depends: debhelper-compat (= 13), libibverbs-dev, librdmacm-dev (>= 1.0.16),
-	   xsltproc, docbook-xsl, librbd-dev, libglusterfs-dev [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64], uuid-dev,
-   bash-completion, libsystemd-dev, libaio-dev, pkg-config
+   xsltproc, docbook-xsl,
+   librbd-dev [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64],
+   libglusterfs-dev [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64],
+   uuid-dev, bash-completion, libsystemd-dev, libaio-dev, pkgconf
 Vcs-Git: https://salsa.debian.org/debian/tgt.git
 Vcs-Browser: https://salsa.debian.org/debian/tgt
 Standards-Version: 4.6.1
@@ -35,7 +37,7 @@
  This package includes the daemon and user-space tools.
 
 Package: tgt-rbd
-Architecture: linux-any
+Architecture: amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64
 Depends: tgt (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
 Description: Linux SCSI target user-space daemon and tools - RBD support
  The Linux target framework (tgt) allows a Linux system to provide SCSI
diff -Nru tgt-1.0.85/debian/rules tgt-1.0.85/debian/rules
--- tgt-1.0.85/debian/rules	2023-11-17 22:35:38.0 +0100
+++ tgt-1.0.85/debian/rules	2024-04-09 09:28:44.0 +0200
@@ -1,12 +1,16 @@
 #!/usr/bin/make -f
 #export DH_VERBOSE=1
 
-FEATURES = ISCSI_RDMA=1 CEPH_RBD=1 SD_NOTIFY=1
+FEATURES = ISCSI_RDMA=1 SD_NOTIFY=1
 
 glfs_libs = $(shell pkg-config --libs glusterfs-api 2>/dev/null)
 ifneq ($(glfs_libs),)
 FEATURES += GLFS_BD=1
 endif
+rbd_lib = $(shell ls /usr/lib/${DEB_HOST_MULTIARCH}/librbd.so 2>/dev/null)
+ifneq ($(rbd_lib),)
+FEATURES += CEPH_RBD=1
+endif
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 

Processed: tgt: diff for NMU version 1:1.0.85-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1068572 + patch
Bug #1068572 [src:tgt] tgt: ceph no longer supports 32 bit architectures
Ignoring request to alter tags of bug #1068572 to the same tags previously set
> tags 1068572 + pending
Bug #1068572 [src:tgt] tgt: ceph no longer supports 32 bit architectures
Added tag(s) pending.

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

Bug#1054445: softhsm2-common: Missing Depends on passwd

[Andreas Beckmann]

Followup-For: Bug #1054445
Control: tag -1 sid trixie

This is only an issue from trixie onwards where apt has dropped the
dependency on adduser, breaking the dependency chain
  apt (Priority: required) -> adduser -> passwd


Andreas

Processed: Re: softhsm2-common: Missing Depends on passwd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 sid trixie
Bug #1054445 {Done: Bastian Germann } [softhsm2-common] 
softhsm2-common: Missing Depends on passwd
Added tag(s) sid and trixie.

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

Bug#1060926: marked as done (simgear: FTBFS: Compositor.hxx:137:34: error: field ‘_uniforms’ has incomplete type ‘simgear::compositor::Compositor::BuiltinUniforms’ {aka ‘std::array

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 09:49:25 +
with message-id 
and subject line Bug#1060926: fixed in simgear 1:2020.3.18+dfsg-2.1
has caused the Debian Bug report #1060926,
regarding simgear: FTBFS: Compositor.hxx:137:34: error: field ‘_uniforms’ has 
incomplete type ‘simgear::compositor::Compositor::BuiltinUniforms’ {aka 
‘std::array, 14>’}
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.)


-- 
1060926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simgear
Version: 1:2020.3.18+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cd /<>/build/simgear && /usr/bin/c++ -DHAVE_CONFIG_H 
> -DHAVE_INTTYPES_H -I/<> -I/<>/build/simgear 
> -I/<>/build -I/usr/include/AL 
> -I/<>/simgear/canvas/ShivaVG/include 
> -I/<>/3rdparty/utf8/source -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -msse2 -mfpmath=sse -ftree-vectorize 
> -ftree-slp-vectorize  -Wall -fPIC -Wno-unused-local-typedefs  
> -DBOOST_BIMAP_DISABLE_SERIALIZATION -DBOOST_NO_STDLIB_CONFIG -O3 -g -DNDEBUG 
> -msse2 -mfpmath=sse -ftree-vectorize -ftree-slp-vectorize -std=gnu++11 -MD 
> -MT simgear/CMakeFiles/SimGearScene.dir/sound/xmlsound.cxx.o -MF 
> CMakeFiles/SimGearScene.dir/sound/xmlsound.cxx.o.d -o 
> CMakeFiles/SimGearScene.dir/sound/xmlsound.cxx.o -c 
> /<>/simgear/sound/xmlsound.cxx
> In file included from /<>/simgear/scene/viewer/Compositor.cxx:17:
> /<>/simgear/scene/viewer/Compositor.hxx:137:34: error: field 
> ‘_uniforms’ has incomplete type 
> ‘simgear::compositor::Compositor::BuiltinUniforms’ {aka 
> ‘std::array, 14>’}
>   137 | BuiltinUniforms  _uniforms;
>   |  ^
> In file included from /usr/include/c++/13/bits/hashtable_policy.h:34,
>  from /usr/include/c++/13/bits/hashtable.h:35,
>  from /usr/include/c++/13/bits/unordered_map.h:33,
>  from /usr/include/c++/13/unordered_map:41,
>  from /<>/simgear/scene/viewer/Compositor.hxx:20:
> /usr/include/c++/13/tuple:2005:45: note: declaration of 
> ‘simgear::compositor::Compositor::BuiltinUniforms’ {aka ‘struct 
> std::array, 14>’}
>  2005 |   template struct array;
>   | ^
> [ 74%] Building CXX object 
> simgear/CMakeFiles/SimGearScene.dir/sound/filters.cxx.o
> cd /<>/build/simgear && /usr/bin/c++ -DHAVE_CONFIG_H 
> -DHAVE_INTTYPES_H -I/<> -I/<>/build/simgear 
> -I/<>/build -I/usr/include/AL 
> -I/<>/simgear/canvas/ShivaVG/include 
> -I/<>/3rdparty/utf8/source -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -msse2 -mfpmath=sse -ftree-vectorize 
> -ftree-slp-vectorize  -Wall -fPIC -Wno-unused-local-typedefs  
> -DBOOST_BIMAP_DISABLE_SERIALIZATION -DBOOST_NO_STDLIB_CONFIG -O3 -g -DNDEBUG 
> -msse2 -mfpmath=sse -ftree-vectorize -ftree-slp-vectorize -std=gnu++11 -MD 
> -MT simgear/CMakeFiles/SimGearScene.dir/sound/filters.cxx.o -MF 
> CMakeFiles/SimGearScene.dir/sound/filters.cxx.o.d -o 
> CMakeFiles/SimGearScene.dir/sound/filters.cxx.o -c 
> /<>/simgear/sound/filters.cxx
> [ 74%] Building CXX object 
> simgear/CMakeFiles/SimGearScene.dir/sound/soundmgr_openal.cxx.o
> cd /<>/build/simgear && /usr/bin/c++ -DHAVE_CONFIG_H 
> -DHAVE_INTTYPES_H -I/<> -I/<>/build/simgear 
> -I/<>/build -I/usr/include/AL 
> -I/<>/simgear/canvas/ShivaVG/include 
> -I/<>/3rdparty/utf8/source -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -msse2 -mfpmath=sse -ftree-vectorize 
> -ftree-slp-vectorize  -Wall -fPIC -Wno-unused-local-typedefs  
> -DBOOST_BIMAP_DISABLE_SERIALIZATION -DBOOST_NO_STDLIB_CONFIG -O3 -g -DNDEBUG 
> -msse2 -mfpmath=sse -ftree-vectorize -ftree-slp-vectorize -std=gnu++11 -MD 
> -MT simgear/CMakeFiles/SimGearScene.dir/sound/soundmgr_openal.cxx.o -MF 
> CMakeFiles/SimGearScene.dir/sound/soundmgr_openal.cxx.o.d -o 
> CMakeFiles/SimGearScene.dir/sound/soundmgr_openal.cxx.o -c 
> /<>/simgear/sound/soundmgr_openal.cxx
> [ 74%] Building CXX object 
> 

Bug#1068586: ghc: Broken on arm{el,hf} because of time_t transition

[Adrian Bunk]

On Sun, Apr 07, 2024 at 05:18:06PM +0300, Ilias Tsitsimpis wrote:
> Package: ghc
> Version: 9.4.7-3
> Severity: grave
> Justification: renders package unusable
> 
> I recently uploaded a new version of GHC to unstable, in order to fix
> #1068179. As a result, GHC got rebuilt taking into account the new size
> for time_t on arm{el,hf}. This is evident from the build logs, where
> we now see:
> 
>   
> https://buildd.debian.org/status/fetch.php?pkg=ghc=armel=9.4.7-4=1712410679=0
> 
>   checking Haskell type for time_t... Int64
> 
> whereas previously we had:
> 
>   
> https://buildd.debian.org/status/fetch.php?pkg=ghc=armel=9.4.7-3=1708366014=0
> 
>   checking Haskell type for time_t... Int32
> 
> 
> After this change, a number of Haskell packages have started to FTBFS:
> 
> * 
> https://buildd.debian.org/status/fetch.php?pkg=haskell-filestore=armel=0.6.5-3%2Bb2=1712457355=0
> * 
> https://buildd.debian.org/status/fetch.php?pkg=haskell-fold-debounce=armel=0.2.0.11-1%2Bb2=1712466208=0
> * 
> https://buildd.debian.org/status/fetch.php?pkg=haskell-hourglass=armel=0.2.12-5%2Bb2=1712462130=0

FTR, in haskell-hourglass this is #1001686 which already failed on x32 
for this reason.

> Looking into this, I see that (at least) the getPOSIXTime method is
> broken on arm{el,hf}.
>...

https://buildd.debian.org/status/fetch.php?pkg=haskell-lambdahack=armhf=0.11.0.0-4%2Bb1=1712562043=0
https://buildd.debian.org/status/fetch.php?pkg=haskell-hledger-lib=armhf=1.30-1%2Bb1=1712566894=0

  Exception: user error (localtime_r failed)

My reading of the code is that this happens when 
libraries/time/lib/cbits/HsTime.c returns 0x8000 due to 
localtime_r() called in this function returning an error.

The "localtime_r failed" is from
libraries/time/lib/Data/Time/LocalTime/Internal/TimeZone.hs

> Ilias

cu
Adrian

Bug#1068251: glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t

[Aurelien Jarno]

Hi,

On 2024-04-09 07:56, Helmut Grohne wrote:
> Hi Aurelien,
> 
> On Mon, Apr 08, 2024 at 11:24:40PM +0200, Aurelien Jarno wrote:
> > Thanks for you analysis and your patch. In short your proposal is to
> > extend the initial patch from Steve to fully hide the fact that the
> > compiler default to -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64.
> > 
> > This indeed works and fixes the FTBFS. However it seems that, at least
> > for some of the issues, it just hides them. For instance the wrong type
> > for timeval.tv_usec, reported by Simon upstream [1], was detected by the
> > conformance tests. Quoting utmpx.h/conform.out:
> 
> I think this needs a more nuanced look. From the comments in the
> conformance test suite, it is evident that it expects to be run without
> _FILE_OFFSET_BITS and _TIME_BITS. Many of the symbols it requires to
> exist only exist when these macros are unset. The conformance test suite
> has a comment saying that it should be testing the case where
> _FILE_OFFSET_BITS is defined, but it currently does not provide
> expectations for that case.
> 
> Before we can reasonably run the conformance test suite with these
> macros set (and really, the test suite should be in control of these
> macros), we cannot reasonably use it with them set. Let us now imagine a
> future where the conformance test suite has been extended to provide
> expectations (which in lots of cases means that *64 symbols disappear
> when -D_FILE_OFFSET_BITS=64). Then what still remains is Simon's issue:
> 
> > | /tmp/tmp98wzaavx/test.c:4:35: error: conflicting types for ‘b2_10’; have 
> > ‘__suseconds64_t’ {aka ‘long long int’}
> > | 4 | extern __typeof__ (a2_10.tv_usec) b2_10;
> > |   |   ^
> > | /tmp/tmp98wzaavx/test.c:3:20: note: previous declaration of ‘b2_10’ with 
> > type ‘suseconds_t’ {aka ‘long int’}
> > | 3 | extern suseconds_t b2_10;
> > |   |^
> > | FAIL: Type of member tv_usec
> 
> Indeed, this is not something that can easily be fixed and where
> upstream is still debating on what the correct solution should be. It
> also is an issue that existed for a long time. If you head over to a
> bookworm glibc and enable -D_TIME_BITS=64 there, you'll also notice that
> tv_usec and suseconds_t have different sizes. So yes, this is a bug, but
> it is not one that is directly related to Debian changing the default.
> We merely increased the visibility of this problem that existed earlier
> already.

I agree that this is an existing issue. My point there was mostly that
your solution is just hiding a real issue that is found by the
testsuite, and basically the testsuite runs in a different configuration
than the one used on the system. We might just miss new issues for new
upstream versions, which is not something very comfortable for a base
library.

> Given that
>  * the issue is already present in bookworm,
>  * there are two mutually exclusive solutions and
>  * upstream is still discussing the best solution
> I recommend deferring this aspect.

While the issue is already present in bookworm, it is not visible
because the toolchain has different defaults.

> > And we know it is the reason for the FTBFS of libflorist [2], so should
> > we just ignore that issue anyway?
> 
> The libflorist issue likely is a consequence. It arises from
> gnat_to_gnu_field where GNAT verifies that the value (of type
> suseconds_t) to be assigned to a field (tv_usec) has the matching size.
> This is directly based on the POSIX expectation and will be fixed with
> the glibc issue.
> 
> How about filing a separate bug with glibc that tracks this POSIX
> divergence and mark the libflorist bug as being blocked by this other
> glibc bug? It can be RC or not, but since it affects bookworm, it won't
> block testing migration.

Yes we can do that. That said I am not sure we can claim the issue
affects bookworm, as again the toolchain does not have the same defaults
and therefore libflorist does not FTBFS in bookworm.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net


signature.asc
Description: PGP signature

Bug#1050288: marked as done (nsis 3.08-3 (bookworm) generates bogus relocation information (regression))

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 08:11:14 +0200
with message-id <14045375.RDIVbhacDa@turnagra>
and subject line Re: Bug#1050288: nsis 3.08-3 (bookworm) generates bogus 
relocation information (regression)
has caused the Debian Bug report #1050288,
regarding nsis 3.08-3 (bookworm) generates bogus relocation information 
(regression)
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.)


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

Package: nsis
Version: 3.08-3
Severity: important

makensis 3.08-3 on bookworm creates installers with a non-empty 
relocation section which contains garbage.


The installers work, but trigger false positive warnings from security 
scanners, likely due to exe file corruption.


Testcase:

$ dpkg --list nsis nsis-common
...
ii  nsis   3.08-3   amd64    ...
ii  nsis-common    3.08-3   all  ...

$ cat test.nsi
Section "Empty"
SectionEnd

$ makensis test.nsi
...

$ objdump -p test.exe >/dev/null
objdump: error: test.exe(.reloc) is too large (0x8e4 bytes)

$ objdump -p test.exe 2>/dev/null
...
Entry 5 00047000 08e4 Base Relocation Directory [.reloc]
...

$ objdump -p /usr/share/nsis/Stubs/zlib-x86-unicode
...
Entry 5 00047000 08e4 Base Relocation Directory [.reloc]
...
PE File Base Relocations (interpreted .reloc section contents)

Virtual Address: 1000 Chunk size 196 (0xc4) Number of fixups 94
    reloc    0 offset   2b [102b] HIGHLOW
    reloc    1 offset   40 [1040] HIGHLOW
...
Virtual Address: c000 Chunk size 216 (0xd8) Number of fixups 104
    reloc    1 offset    8 [c008] HIGHLOW
    reloc    2 offset    c [c00c] HIGHLOW
...
    reloc  102 offset  8f8 [c8f8] HIGHLOW
    reloc  103 offset  8fc [c8fc] HIGHLOW


All the stubs apparently have a non-empty relocation section with 
garbage. This is not the case for the stubs from nsis-common-3.06.1-1 
(bullseye) and nsis-common-3.09-1 (sid).


This is also not the case with the upstream 3.08 and 3.09 builds for 
windows which are available at

https://sourceforge.net/projects/nsis/files/NSIS%203/

Related: https://sourceforge.net/p/nsis/bugs/1299/

--
Regards
Christian Franke
smartmontools.org
--- End Message ---
--- Begin Message ---
Version: 3.09-1

Le samedi, 26 août 2023, 14.23:38 h CEST Thomas Gaugler a écrit :
> Thank you for your detailed bug report.
> 
> I built the nsis_3.09-1 and nsis-common_3.09-1 packages on Debian
> Bookworm, installed the resulting packages and can confirm with the two
> Nullsoft Installer (.nsi) scripts provided by you that the resulting
> installer executables no longer show the "(.reloc) is too large" error
> with objdump.

In other words, you are claiming that you have verified that this is fixed in 
the 3.09-1 version.

I'm hereby marking this bug as fixed in that version (via a -done email, with 
a "Version:" pseudo-header).

This will mark it as solved in testing and sid (as the 3.09-1 is older than 
the versions in both these releases. It will open the possibility for a fix in 
stable.

Best,
OdyX

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

Bug#1068683: zmat: FTBFS: ar: blosc2/blosc/*.o: No such file or directory

[Sébastien Villemot]

Le mardi 09 avril 2024 à 10:14 +0800, Bo YU a écrit :
> The package has ftbfs issue but on amd64 and i386, the common issue is
> follows:
> 
> ```
> CC obj/conf_91c451f6ae5e059804729dd256611361/static/cover.o
> CC obj/conf_91c451f6ae5e059804729dd256611361/static/divsufsort.o
> CC obj/conf_91c451f6ae5e059804729dd256611361/static/fastcover.o
> CC obj/conf_91c451f6ae5e059804729dd256611361/static/zdict.o
> compiling single-threaded static library 1.5.5
> make[4]: Leaving directory 
> '/<>/src/blosc2/internal-complibs/zstd'
> make[3]: Leaving directory '/<>/src/blosc2'
> Building ../lib/libzmat.a
> ar cr -o ../lib/libzmat.a zmatlib.o miniz/miniz.o easylzma/compress.o 
> easylzma/decompress.o easylzma/lzma_header.o easylzma/lzip_header.o 
> easylzma/common_internal.o easylzma/pavlov/LzmaEnc.o 
> easylzma/pavlov/LzmaDec.o easylzma/pavlov/LzmaLib.o easylzma/pavlov/LzFind.o 
> easylzma/pavlov/Bra.o easylzma/pavlov/BraIA64.o easylzma/pavlov/Alloc.o 
> easylzma/pavlov/7zCrc.o blosc2/blosc/*.o 
> blosc2/internal-complibs/zstd/obj/*/static/*.o 
> ar: blosc2/blosc/*.o: No such file or directory

The problem is actually that zmat tries to compile a file with -msse2,
which of course is only available on amd64 and i386.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Bug#1067957: [EXTERNAL] Re: [[maude-bugs]] Maude fails to build on armhf

[Sebastian Ramacher]

Hi Steven

On 2024-04-08 15:38:50 -0700, Steven Eker wrote:
> Hi Nilish,
> 
> I don't have a 32-bit machine to test on, but my understanding is that Linux
> has moved to a 64-bit signed integer for time_t and this is a long long on
> 32-bit machines which is explicitly not supported by GMP's C++ API.

This sounds like it needs to fixed in GMP then.

> 
> https://en.wikipedia.org/wiki/Year_2038_problem
> https://gmplib.org/manual/C_002b_002b-Interface-Integers
> 
> I'm not happy converting a signed value to an unsigned value for all
> architectures. But
> 
>   mpz_class nanoSeconds(static_cast(timeValue.tv_sec));
> 
> should fix the problem, at least until 2038. Can you check that this works?
> If so I'll put it in the next public alpha.

And this does not sound like a fix which we want.

Best
Sebastian
-- 
Sebastian Ramacher

Processed: tagging 1068512, tagging 1064034, tagging 1068473

[Debian Bug Tracking System]

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

> tags 1068512 + sid trixie
Bug #1068512 {Done: tony mancill } [src:welle.io] 
welle.io: FTBFS on arm{el,hf}: manually disables mpg123's LFS API
Added tag(s) trixie and sid.
> tags 1064034 + sid trixie
Bug #1064034 {Done: Chris Hofstaedtler } [src:ruby3.1] FTBFS: 
Expired test certificate
Added tag(s) trixie and sid.
> tags 1068473 + sid trixie
Bug #1068473 [src:icinga2] icinga2: crashes on startup on ppc64el
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Bug#1066291: marked as done (gimp-plugin-registry: FTBFS: separate-gui.c:603:7: error: implicit declaration of function ‘icc_button_set_enable_empty’; did you mean ‘icc_button_get_enable_empty’? [-Wer

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 12:36:20 +
with message-id 
and subject line Bug#1066291: fixed in gimp-plugin-registry 9.20240404
has caused the Debian Bug report #1066291,
regarding gimp-plugin-registry: FTBFS: separate-gui.c:603:7: error: implicit 
declaration of function ‘icc_button_set_enable_empty’; did you mean 
‘icc_button_get_enable_empty’? [-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.)


-- 
1066291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gimp-plugin-registry
Version: 9.20200928
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 -g -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -DUSE_LCMS2 `pkg-config gimp-2.0 --cflags` `pkg-config gimpui-2.0 --cflags` 
> `pkg-config gtk+-2.0 --cflags` `pkg-config lcms2 --cflags` 
> -DENABLE_COLOR_MANAGEMENT -DENABLE_NLS 
> -DGETTEXT_PACKAGE="\"gimp20-separate\"" -DUSE_ICC_BUTTON -c separate-gui.c
> In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
>  from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
>  from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
>  from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
>  from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:33,
>  from separate-gui.c:22:
> /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is 
> deprecated [-Wdeprecated-declarations]
>   236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
>   | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
>  from /usr/include/glib-2.0/gobject/gbinding.h:31,
>  from /usr/include/glib-2.0/glib-object.h:24,
>  from /usr/include/glib-2.0/gio/gioenums.h:30,
>  from /usr/include/glib-2.0/gio/giotypes.h:30,
>  from /usr/include/glib-2.0/gio/gio.h:28,
>  from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
>  from /usr/include/gtk-2.0/gdk/gdk.h:32,
>  from /usr/include/gtk-2.0/gtk/gtk.h:32:
> /usr/include/glib-2.0/gobject/gtype.h:723:1: note: declared here
>   723 | {
>   | ^
> In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
>  from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
>  from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
>  from /usr/include/gtk-2.0/gtk/gtk.h:126:
> /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is 
> deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations]
>73 |   GTimeVal last_popdown;
>   |   ^~~~
> In file included from /usr/include/glib-2.0/glib/galloca.h:34,
>  from /usr/include/glib-2.0/glib.h:32,
>  from /usr/include/glib-2.0/gobject/gbinding.h:30:
> /usr/include/glib-2.0/glib/gtypes.h:580:8: note: declared here
>   580 | struct _GTimeVal
>   |^
> separate-gui.c: In function ‘run’:
> separate-gui.c:299:3: warning: ‘gimp_drawable_get’ is deprecated: Use 
> 'gimp_drawable_get_buffer' instead [-Wdeprecated-declarations]
>   299 |   drawable = gimp_drawable_get (param[index].data.d_drawable);
>   |   ^~~~
> In file included from /usr/include/gimp-2.0/libgimp/gimp.h:41,
>  from separate-gui.c:24:
> /usr/include/gimp-2.0/libgimp/gimpdrawable.h:52:16: note: declared here
>52 | GimpDrawable * gimp_drawable_get(gint32 
> drawable_ID);
>   |^
> separate-gui.c:300:3: warning: 

Bug#1060134: kmod-udeb vs busybox-udeb: agree on who ships depmod

[Marco d'Itri]

On Jan 06, Michael Tokarev  wrote:

> Yes, some utils in busybox aren't as good as regular implementations. For
Yes. Nowadays kmod has many more features related to compressed modules 
and verification of signatures.
Can we agree that kmod should provide these programs for d-i?
Or can the d-i maintainers just tell us what they want?

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1064997: marked as done (tdfsb: fails to trap errors from ./compile.sh)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 13:10:02 +
with message-id 
and subject line Bug#1064997: fixed in tdfsb 0.0.10-4
has caused the Debian Bug report #1064997,
regarding tdfsb: fails to trap errors from ./compile.sh
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.)


-- 
1064997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tdfsb
Version: 0.0.10-3
Severity: serious
Justification: policy 4.6

tdfsb's compile.sh fails to terminate with an error when one of the
invoked build commands fails. This violates Debian policy section 4.6. A
relatively simple counter measure would be adding "set -e" to the
script.

Helmut
--- End Message ---
--- Begin Message ---
Source: tdfsb
Source-Version: 0.0.10-4
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
tdfsb, 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 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated tdfsb 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: SHA256

Format: 1.8
Date: Tue, 09 Apr 2024 14:25:27 +0200
Source: tdfsb
Architecture: source
Version: 0.0.10-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 745645 1011486 1064997
Changes:
 tdfsb (0.0.10-4) unstable; urgency=medium
 .
   * QA upload.
   * Import package history into GIT.
   * Add a minimal Makefile instead of fixing up compile.sh. (Closes: #1064997)
   * Respect all flags from dpkg-buildflags.  (Closes: #1011486)
   * Fix building with -Werror=format-security.
   * Fix building with clang instead of gcc, thanks to Nicolas
 Sévelin-Radiguet.  (Closes: #745645)
   * Declare Rules-Requires-Root: no.
Checksums-Sha1:
 cdaf130d3163a8722afc7bd8be00c9a29b7182af 1923 tdfsb_0.0.10-4.dsc
 ad473a477e33cb93002f1a03515f8a99eb796c2d 5436 tdfsb_0.0.10-4.debian.tar.xz
 f873c99cafcb6fd3ee244d7d15876e3b2070d73b 11531 tdfsb_0.0.10-4_source.buildinfo
Checksums-Sha256:
 5b9b1faa72608e34757d5457dd994d280f15318fde24354f5578b8513e24ebd4 1923 
tdfsb_0.0.10-4.dsc
 9c480ca93ce393ce4d69992849183394f82b483095a314f1f73145b2ec5dbfa5 5436 
tdfsb_0.0.10-4.debian.tar.xz
 adbb2a491da051f7891367b0ca30458091e0aabc8c50be761175da6f705b8c14 11531 
tdfsb_0.0.10-4_source.buildinfo
Files:
 91db8bdb7fd39df41e63ebec145fbdf1 1923 games optional tdfsb_0.0.10-4.dsc
 942468c89cec71c82e7ce80200df8f50 5436 games optional 
tdfsb_0.0.10-4.debian.tar.xz
 9157e8dbe4ec440168a1738b6f6c5eeb 11531 games optional 
tdfsb_0.0.10-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYVNVIQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCDWIEACDOfOb0xUSulut/6I0SPgGBc4fRM0HRbVR
D9yflNY2aIu025Eh/IxBzctVDqvQLJOmYl8i0Exdxf6hShh6ekGr+rQ95AyUjoQu
VoUcvHybRKsiWuN64LQAS24BYHgTwR7CXmFvBlFXDXZG1RiHAkjFnVWN2fDaNJru
2zUSLmvpsYl50IoCE3+TjLuR0benF8KKY2Do60qBFU0lhWc3qs+dmtXxI7cQMpFM
iUWJPv5cXu82rRHL6NxsnTeeqskijx47y/vLfUBp3o99NaRjqbP4ITTlehKeAEiP
dS1W8FKB7Pu9QHctvTcZaa71dF5uJlkRwi02xPSWlA00pubKIyi53DbI70UQyHA/
KoLECwaBUr5FI2l1op/MclpGg01uH1YIS/mBU9/ebgumD8OchQxy1wb1aRgFLXSC
X3RUrb1N9M+xYMvaaWFIDPSIUuHX+nn7p718xug5DMnMFG5deQHre1K/J4uL5QYK
Eo0YSU814JFdRGayjxlqR/48Mkg5Xo7ri0A6lIsyo9OiaYk5F1Tq1YniBe8kv90g
3i31xjA6nc22JBkJtrRwnZzbSc7cJ1P5r8f5Nq0A/anD/Wr441vkooGArFH0tgVj
MLmToccFLvJgl8TtC/6pZgvW8KcQudLqzvrxqv1UmvXF0t1Q//oI/frGU8Psjt2Y
EB7DA0/IvQ==
=6NCX
-END PGP SIGNATURE-



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

Bug#1068600: marked as done (swi-prolog, uninstallable on 32-bit non-i386 architectures.)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 13:09:55 +
with message-id 
and subject line Bug#1068600: fixed in swi-prolog 9.0.4+dfsg-4
has caused the Debian Bug report #1068600,
regarding swi-prolog, uninstallable on 32-bit non-i386 architectures.
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.)


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

Package: swi-prolog
Version: 9.0.4+dfsg-3.1
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t

It looks like the adjustments for the time64 transition in the 
9.0.4+dfsg-3.1

NMU were incomplete. Resulting in unsatisfiable dependencies on armel
and armhf at least (and probablly some debian-ports architectures too).

swi-prolog (9.0.4+dfsg-3.1) [PTS 
] [ctrl 
]

   ↓ swi-prolog-doc (>= 9.0.4+dfsg-3.1)
swi-prolog-doc 
 
(9.0.4+dfsg-3.1) [PTS ] [ctrl 
]

   ↓ swi-prolog-core (>= 9.0.4+dfsg-3.1)
swi-prolog-core 
 
(9.0.4+dfsg-3.1) [PTS ] [ctrl 
]

   ↓ libswipl9
MISSING

Ubuntu seem to have fixed this.

http://launchpadlibrarian.net/721003900/swi-prolog_9.0.4+dfsg-3.1ubuntu2_9.0.4+dfsg-3.1ubuntu3.diff.gz
--- End Message ---
--- Begin Message ---
Source: swi-prolog
Source-Version: 9.0.4+dfsg-4
Done: Lev Lamberov 

We believe that the bug you reported is fixed in the latest version of
swi-prolog, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lev Lamberov  (supplier of updated swi-prolog 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: Tue, 09 Apr 2024 17:16:03 +0500
Source: swi-prolog
Architecture: source
Version: 9.0.4+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Lev Lamberov 
Changed-By: Lev Lamberov 
Closes: 1068600
Changes:
 swi-prolog (9.0.4+dfsg-4) unstable; urgency=medium
 .
   * Import Ubuntu fix for 64-bit time_t (Closes: #1068600)
Checksums-Sha1:
 4d6273bdbef6f3d3a96b2e36890764614ae61890 3500 swi-prolog_9.0.4+dfsg-4.dsc
 17e560391189a95ef3f534cd75ee0882c34f5c4f 35596 
swi-prolog_9.0.4+dfsg-4.debian.tar.xz
 18fb212e23042963d7fff738ccb41dffd010cc8a 18603 
swi-prolog_9.0.4+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 0e672327c2fbb41cd17c6e5560f251f9a897ce0d4aa0aeff9226f85d7d4906a3 3500 
swi-prolog_9.0.4+dfsg-4.dsc
 4f391e5f10d3a7c59d6b00b7f5d1038c19127e50f27e4df1b99ec199c91a8ce4 35596 
swi-prolog_9.0.4+dfsg-4.debian.tar.xz
 aa0614ed9954ac40cbfec051432d82606d7ece1a5fdc7a2c84621a8ab051f764 18603 
swi-prolog_9.0.4+dfsg-4_amd64.buildinfo
Files:
 7514f0dae7e6c842d506f8a6d64bb45b 3500 interpreters optional 
swi-prolog_9.0.4+dfsg-4.dsc
 0e2722a00f8cccd6f8ff8c929d471a0a 35596 interpreters optional 
swi-prolog_9.0.4+dfsg-4.debian.tar.xz
 4f3c9f250bcfb073ca9ccef0ffc47eb5 18603 interpreters optional 
swi-prolog_9.0.4+dfsg-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE3mumcdV9mwCc9oZQXudu4gIW0qUFAmYVNbYACgkQXudu4gIW
0qXkrRAAiSH6Dz9dp6VBmG01jqKbfS1csg7mu+S9pXCzSwP9nJpXXfRyf29rsqfv
2Dlnx0BaarVhjZ0m2ntQyMw8f4kdU67BxzCaVwLXkQM1tw59ZZk54zCOOldehPMN
RKyeOJueRlZBOcAN9CoMN00yj9+e9W14MGQCSSEAL3Keqg8XPuBqW9RX9kyTEPYw
SMN1JYzbryB+hLsnsnjdjR1L0vGayTJK70l34Y6ydiXZ0TTDhkNgy4udw+T4fUrh
ySFKyd8iZrQjAjFThWulE2xZD6EiHXcnYPVDgHslB6tfPAtexCiNEEDmUmrg/7L5
aBNQh52uqI0mQ4K282JE72ARdC/VZEhgUcsMUDJmmc+VJx3FB6s1Kvif9G4z+ijz
SMLTDhJ0S44G2eNV5ofqgBpVOErnH/9qZJKLumbvfJ/XKv9vFxMYi7p9TdBKwAZV
WP8iAoxB01lR19+DxMu4Nd3jKquFIzlKun8rtL7vHDQCHz/tTlZ7ojmov9ervjRy
QZ5jevd3eKEOXN1yYZIeP8xdO0h7zID7RnpRcGg1SEB46UdEjtrYdLh1coTbtqVa
dyTaR0sETn8EEH5i7PguctpSFMryCRgW6vp2oiqeN4RYPfvVdoNqijvWakI11KWN

Bug#1060134: kmod-udeb vs busybox-udeb: agree on who ships depmod

[Cyril Brulebois]

Hi,

Marco d'Itri  (2024-04-09):
> Yes. Nowadays kmod has many more features related to compressed modules 
> and verification of signatures.
> Can we agree that kmod should provide these programs for d-i?
> Or can the d-i maintainers just tell us what they want?

I meant to come back to this after experimenting, then things happened…

I picked kmod at the time because it worked, and because busybox didn't
work, which I summed up in:
  
https://salsa.debian.org/installer-team/debian-installer/-/commit/450daf0bd24ee94d4f466ab65908c079ef795145

(plus follow-up commit, woopsie
  
https://salsa.debian.org/installer-team/debian-installer/-/commit/69777be465c5d0210d16159a456ab88535513a07
)

I'm fine with sticking to kmod regarding module support in d-i. I'm not
sure we should keep support in two different modules, so dropping it
from busybox would work for me. Others might have different views on
this, though.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1067354: marked as done (ibus-client-clutter: FTBFS: dpkg-deb: error: parsing file 'debian/ibus-clutter/DEBIAN/control' near line 7 package 'ibus-clutter':)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 13:49:29 +
with message-id 
and subject line Bug#1067354: fixed in ibus-client-clutter 
0.0+git20090728.a936bacf-8
has caused the Debian Bug report #1067354,
regarding ibus-client-clutter: FTBFS: dpkg-deb: error: parsing file 
'debian/ibus-clutter/DEBIAN/control' near line 7 package 'ibus-clutter':
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.)


-- 
1067354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ibus-client-clutter
Version: 0.0+git20090728.a936bacf-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> make[3]: Nothing to be done for 'install-exec-am'.
> make[3]: Nothing to be done for 'install-data-am'.
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
> touch debian/stamp-makefile-install
> Adding cdbs dependencies to debian/ibus-clutter.substvars
> dh_installdirs -pibus-clutter \
>   
> dh_installdocs -pibus-clutter ./README ./NEWS ./AUTHORS
> dh_installexamples -pibus-clutter 
> dh_installman -pibus-clutter 
> dh_installinfo -pibus-clutter 
> dh_installmenu -pibus-clutter 
> dh_installcron -pibus-clutter 
> dh_systemd_enable -pibus-clutter 
> dh_installinit -pibus-clutter 
> dh_installdebconf -pibus-clutter 
> dh_installemacsen -pibus-clutter 
> dh_installcatalogs -pibus-clutter 
> dh_installpam -pibus-clutter 
> dh_installlogrotate -pibus-clutter 
> dh_installlogcheck -pibus-clutter 
> dh_installchangelogs -pibus-clutter ./ChangeLog
> dh_installudev -pibus-clutter 
> dh_lintian -pibus-clutter 
> dh_bugfiles -pibus-clutter 
> dh_install -pibus-clutter 
> dh_systemd_start -pibus-clutter 
> dh_link -pibus-clutter 
> dh_installmime -pibus-clutter 
> dh_installgsettings -pibus-clutter 
> rm -f 
> debian/ibus-clutter/usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/*.la
> rm -f 
> debian/ibus-clutter/usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules/*.a
> dh_strip -pibus-clutter  
> dh_strip_nondeterminism -pibus-clutter 
> dh_compress -pibus-clutter 
> dh_fixperms -pibus-clutter 
> dh_makeshlibs -pibus-clutter  -Xim-ibus
> dh_installdeb -pibus-clutter 
> dh_perl -pibus-clutter 
> dh_shlibdeps -pibus-clutter 
> dh_gencontrol -pibus-clutter  -- -V'glib:Depends=libglib2.0-0 (>= )'
> dpkg-gencontrol: warning: relation > is deprecated: use >> or >=
> dpkg-gencontrol: warning: relation > is deprecated: use >> or >=
> # only call dh_scour for packages in main
> if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null; then 
> dh_scour -pibus-clutter ; fi
> dh_md5sums -pibus-clutter 
> dh_builddeb -pibus-clutter 
> dpkg-deb: error: parsing file 'debian/ibus-clutter/DEBIAN/control' near line 
> 7 package 'ibus-clutter':
>  'Depends' field, reference to 'libglib2.0-0': version '=': version number 
> does not start with digit
> dh_builddeb: error: dpkg-deb --build debian/ibus-clutter .. returned exit 
> code 2
> dpkg-deb: building package 'ibus-clutter-dbgsym' in 
> '../ibus-clutter-dbgsym_0.0+git20090728.a936bacf-7_amd64.deb'.
> dh_builddeb: error: Aborting due to earlier error
> make: *** [/usr/share/cdbs/1/rules/debhelper.mk:353: 
> binary-makedeb-IMPL/ibus-clutter] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/ibus-client-clutter_0.0+git20090728.a936bacf-7_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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: ibus-client-clutter
Source-Version: 0.0+git20090728.a936bacf-8
Done: Ying-Chun Liu (PaulLiu) 

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

Processed: found 1060134 in 28-1, found 1060134 in 1:1.30.1-6, found 1068698 in 2:2.0-2 ..., tagging 1056608 ...

[Debian Bug Tracking System]

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

> found 1060134 28-1
Bug #1060134 [kmod-udeb,busybox-udeb] kmod-udeb vs busybox-udeb: agree on who 
ships depmod
There is no source info for the package 'busybox-udeb' at version '28-1' with 
architecture ''
Marked as found in versions kmod/28-1.
> found 1060134 1:1.30.1-6
Bug #1060134 [kmod-udeb,busybox-udeb] kmod-udeb vs busybox-udeb: agree on who 
ships depmod
There is no source info for the package 'kmod-udeb' at version '1:1.30.1-6' 
with architecture ''
Marked as found in versions busybox/1:1.30.1-6.
> found 1068698 2:2.0-2
Bug #1068698 [src:hdf-eos5] hdf-eos5 2:2.0-2 silently reverts the 64-bit time_t 
transition
Marked as found in versions hdf-eos5/2:2.0-2.
> notfound 1068696 0.2.15-5
Bug #1068696 [haskell-hourglass] haskell-hourglass FTBFS on armel and armhf
There is no source info for the package 'haskell-hourglass' at version 
'0.2.15-5' with architecture ''
Unable to make a source version for version '0.2.15-5'
No longer marked as found in versions 0.2.15-5.
> found 1068696 0.2.12-5
Bug #1068696 [haskell-hourglass] haskell-hourglass FTBFS on armel and armhf
There is no source info for the package 'haskell-hourglass' at version 
'0.2.12-5' with architecture ''
Unable to make a source version for version '0.2.12-5'
Marked as found in versions 0.2.12-5.
> retitle 1060939 python-workalendar: FTBFS: CalendarError: Need configure 2024 
> for China.
Bug #1060939 [src:python-workalendar] python-workalendar: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned 
exit code 13
Changed Bug title to 'python-workalendar: FTBFS: CalendarError: Need configure 
2024 for China.' from 'python-workalendar: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13'.
> tags 1056608 - bookworm
Bug #1056608 [timeshift] timeshift: Timeshift cant restore RSYNC snapshots if 
your system installed on BTRFS with wrong subvolume
Removed tag(s) bookworm.
> fixed 1056608 23.07.1-1
Bug #1056608 [timeshift] timeshift: Timeshift cant restore RSYNC snapshots if 
your system installed on BTRFS with wrong subvolume
Marked as fixed in versions timeshift/23.07.1-1.
> found 1052230 4.1.9-1
Bug #1052230 {Done: Stéphane Glondu } [src:ocamlnet] 
"Missing build-dependency on pkg-config"
Marked as found in versions ocamlnet/4.1.9-1.
> tags 1052230 + sid trixie
Bug #1052230 {Done: Stéphane Glondu } [src:ocamlnet] 
"Missing build-dependency on pkg-config"
Added tag(s) sid and trixie.
> tags 1050175 + sid trixie
Bug #1050175 {Done: Mo Zhou } [python3-torch] Missing symbol 
when importing torch
Added tag(s) sid and trixie.
> found 1050516 1.4.3-1
Bug #1050516 {Done: Bastian Germann } [src:checkit-tiff] 
checkit-tiff: FTBFS on big-endian platforms
The source 'checkit-tiff' and version '1.4.3-1' do not appear to match any 
binary packages
Marked as found in versions checkit-tiff/1.4.3-1.
> tags 1042960 + sid trixie
Bug #1042960 {Done: Dmitry Baryshkov } [gcc-doc-base] 
FTBFS: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 3 package 
'gcc-doc'
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1042960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042960
1050175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050175
1050516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050516
1052230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052230
1056608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056608
1060134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060134
1060939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060939
1068696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068696
1068698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068711: oar-web-status: the Monika CGI page does not work - missing dependency.

[Pierre Neyron]

Package: oar-web-status
Version: 2.5.9-1
Severity: serious
Tags: 
Justification: Monika requires libcgi-fast-perl
X-Debbugs-Cc: pierre.ney...@free.fr

Hello,

When installing the oar-web-status package only, without the oar-restful-api 
alongside (not dependency between then), the Monika CGI page does not work.

The problem does not arise when oar-restful-api is installed alongside as well, 
because it bring the required dependency: libcgi-fast-perl.

oar-web-status should require libcgi-fast-perl, like oar-restful-api.

Problem still occures in Debian testing with oar-web-status 2.5.10-1. 

-- System Information:
Debian Release: 12.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 oar-web-status depends on:
ii  apache2 [httpd-cgi]   2.4.57-2
ii  libappconfig-perl 1.71-2.2
ii  libdbd-pg-perl3.16.0-2
ii  libdbi-perl   1.643-4
ii  libsort-naturally-perl1.03-4
ii  libtie-ixhash-perl1.23-4
ii  perl  5.36.0-7+deb12u1
ii  php   2:8.2+93
ii  php-pgsql 2:8.2+93
ii  php8.2 [php]  8.2.7-1~deb12u1
ii  php8.2-pgsql [php-pgsql]  8.2.7-1~deb12u1

oar-web-status recommends no packages.

Versions of packages oar-web-status suggests:
pn  oar-doc  

-- no debconf information

Bug#1066239: marked as done (gnome-system-tools: FTBFS: shares-tool.c:113:17: error: implicit declaration of function ‘table_add_share’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 14:34:43 +
with message-id 
and subject line Bug#1066239: fixed in gnome-system-tools 3.0.0-10
has caused the Debian Bug report #1066239,
regarding gnome-system-tools: FTBFS: shares-tool.c:113:17: error: implicit 
declaration of function ‘table_add_share’ 
[-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.)


-- 
1066239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-system-tools
Version: 3.0.0-9.1
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 -DHAVE_CONFIG_H -I. -I../.. 
> -DPIXMAPS_DIR=\""/usr/share/gnome-system-tools/pixmaps"\" 
> -DINTERFACES_DIR=\""/usr/share/gnome-system-tools/ui"\" -DFRONTEND_DIR=\"""\" 
> -DDESKTOP_DATA_DIR=\"""\" -DCONF_DIR=\""/etc/gnome-system-tools"\" 
> -I../../src/common -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread 
> -I/usr/include/liboobs-1.0  -I/usr/include/polkit-1 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/gio-unix-2.0 -pthread-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 
> -Wall -Wchar-subscripts -Wmissing-declarations -Wnested-externs 
> -Wpointer-arith -Wcast-align -Wsign-compare -Wformat-security -c -o 
> shares-tool.o shares-tool.c
> In file included from /usr/include/liboobs-1.0/oobs/oobs.h:28,
>  from ../../src/common/gst-tool.h:30,
>  from shares-tool.h:27,
>  from shares-tool.c:22:
> /usr/include/liboobs-1.0/oobs/oobs-session.h:79:13: warning: Deprecated 
> pre-processor symbol: replace with "const"
>79 | G_CONST_RETURN gchar * oobs_session_get_authentication_action 
> (OobsSession *session);
>   | ^
> In file included from /usr/include/liboobs-1.0/oobs/oobs-user.h:40,
>  from /usr/include/liboobs-1.0/oobs/oobs-selfconfig.h:28,
>  from /usr/include/liboobs-1.0/oobs/oobs.h:31:
> /usr/include/liboobs-1.0/oobs/oobs-group.h:58:13: warning: Deprecated 
> pre-processor symbol: replace with "const"
>58 | G_CONST_RETURN gchar* oobs_group_get_name (OobsGroup *group);
>   | ^
> /usr/include/liboobs-1.0/oobs/oobs-user.h:84:13: warning: Deprecated 
> pre-processor symbol: replace with "const"
>84 | G_CONST_RETURN gchar* oobs_user_get_login_name (OobsUser *user);
>   | ^~~~ 
> /usr/include/liboobs-1.0/oobs/oobs-user.h:94:13: warning: Deprecated 
> pre-processor symbol: replace with "const"
>94 | G_CONST_RETURN gchar* oobs_user_get_home_directory (OobsUser *user);
>   | ^~~~ 
> /usr/include/liboobs-1.0/oobs/oobs-user.h:97:13: warning: Deprecated 
> pre-processor symbol: replace with "const"
>97 | G_CONST_RETURN gchar* oobs_user_get_shell (OobsUser *user);
>   | ^~~  
> /usr/include/liboobs-1.0/oobs/oobs-user.h:100:13: warning: Deprecated 
> pre-processor symbol: replace with "const"
>   100 | G_CONST_RETURN gchar* oobs_user_get_full_name (OobsUser *user);
>   | 

Bug#1066408: marked as done (ncl: FTBFS: ld: cannot find -lncarg_c: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 15:06:59 +
with message-id 
and subject line Bug#1066408: fixed in ncl 6.6.2.dfsg.1-6
has caused the Debian Bug report #1066408,
regarding ncl: FTBFS: ld: cannot find -lncarg_c: No such file or directory
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.)


-- 
1066408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncl
Version: 6.6.2.dfsg.1-4.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/common/src/graphcap'
> f77 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection  -fallow-invalid-boz 
> -fallow-argument-mismatch  -fno-second-underscore -fno-range-check -c 
> capchg.f
> capchg.f:710:72:
> 
>   710 |   10  DFLNAM(II:II) = ' '
>   |   
>  1
> Warning: Fortran 2018 deleted feature: DO termination statement which is not 
> END DO or CONTINUE with label 10 at (1)
> capchg.f:773:72:
> 
>   773 |  60   DFLNAM(II:II) = ' '
>   |   
>  1
> Warning: Fortran 2018 deleted feature: DO termination statement which is not 
> END DO or CONTINUE with label 60 at (1)
> f77 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection  -fallow-invalid-boz 
> -fallow-argument-mismatch  -fno-second-underscore -fno-range-check  -c -o 
> binput.o binput.f
> binput.f:316:15:
> 
>   315 |   DO  II = 1,DUMSIZ
>   |   
>  2
>   316 | DUMSPC(II) = 0
>   |   1
> Warning: Array reference at (1) out of bounds (327 > 326) in loop beginning 
> at (2)
> binput.f:246:32:
> 
>   226 |   CALL BINWRI(UNIT, LENDEV, DGISTR, IOS, STATUS)
>   |2
> ..
>   246 |   CALL BINWRI(UNIT, LENLIN, PLAVBL, IOS, STATUS)
>   |1
> Warning: Type mismatch between actual argument at (1) and actual argument at 
> (2) (LOGICAL(4)/INTEGER(4)).
> binput.f:298:32:
> 
>   226 |   CALL BINWRI(UNIT, LENDEV, DGISTR, IOS, STATUS)
>   |2
> ..
>   298 |   CALL BINWRI(UNIT, LENBND, PLBTEC, IOS, STATUS)
>   |1
> Warning: Rank mismatch between actual argument at (1) and actual argument at 
> (2) (rank-1 and scalar)
> binput.f:316:72:
> 
>   316 | DUMSPC(II) = 0
>   |   
>  ^
> Warning: iteration 326 invokes undefined behavior 
> [-Waggressive-loop-optimizations]
> binput.f:315:18:
> 
>   315 |   DO  II = 1,DUMSIZ
>   |  ^
> note: within this loop
> f77 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection  -fallow-invalid-boz 
> -fallow-argument-mismatch  -fno-second-underscore -fno-range-check  -c -o 
> bndcls.o bndcls.f
> f77 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection  -fallow-invalid-boz 
> -fallow-argument-mismatch  -fno-second-underscore -fno-range-check -c 
> capast.f
> capast.f:96:16:
> 
>96 |  4 'Z','[','\\',']','^','_','`','a','b','c','d','e','f','g','h',
>   |1
> Warning: Initialization string at (1) was truncated to fit the variable (1/2)
> f77 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection  -fallow-invalid-boz 
> -fallow-argument-mismatch  -fno-second-underscore -fno-range-check  -c -o 
> capdat.o capdat.f
> f77 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection  -fallow-invalid-boz 
> -fallow-argument-mismatch  -fno-second-underscore -fno-range-check  -c -o 
> cappar.o cappar.f
> f77 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection  -fallow-invalid-boz 
> -fallow-argument-mismatch  -fno-second-underscore -fno-range-check  -c -o 
> dascls.o dascls.f
> f77 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection  -fallow-invalid-boz 
> -fallow-argument-mismatch  

Bug#1068713: oar-common: Submitting jobs does not work on a fresh installation of OAR

[Pierre Neyron]

Package: oar-common
Version: 2.5.9-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: pierre.ney...@imag.fr

Hello

After a fresh install of OAR on Debian stable (bookworm), starting jobs does 
not work.

Indeed the ssh connection to nodes is forbidden because the oar user is locked, 
instead of just not accepting password connections.

It is due to a change in the way the adduser ( >= 3.130 ) `--disabled-password` 
option works (it now set `!` instead of `*` in the password hash field).
`usermod -p '*' oar` fixes the issue.

This bug is fixed in Debian testing / oar-common 2.5.10-1.

-- System Information:
Debian Release: 12.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 oar-common depends on:
ii  adduser  3.134
ii  libc62.36-9+deb12u4
ii  liboar-perl  2.5.9-1
ii  perl 5.36.0-7+deb12u1
ii  ucf  3.0043+nmu1

oar-common recommends no packages.

Versions of packages oar-common suggests:
pn  oar-doc 
pn  oar-node
pn  oar-server  
ii  oar-user2.5.9-1

-- no debconf information

Bug#1068030: FTBFS on armel: undefined reference to `__atomic_load_8'

[Jeremy Sowden]

On 2024-03-30, at 02:03:57 +0500, Andrey Rakhmatullin wrote:
> Source: maildir-utils
> Version: 1.10.8-2
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/fetch.php?pkg=maildir-utils=armel=1.10.8-2%2Bb2=1711722478=0
> 
> /usr/bin/ld: lib/index/libmu-index.a.p/mu-indexer.cc.o: in function
> `std::__atomic_base::store(long long, std::memory_order)':
> /usr/include/c++/13/bits/atomic_base.h:481:(.text+0xb14): undefined reference
> to `__atomic_store_8'
> /usr/bin/ld: lib/index/libmu-index.a.p/mu-indexer.cc.o: in function
> `std::__atomic_base::load(std::memory_order) const':
> /usr/include/c++/13/bits/atomic_base.h:505:(.text+0x1384): undefined reference
> to `__atomic_load_8'

This is a 64-bit time_t bug.  Will investigate.

J.

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


signature.asc
Description: PGP signature

Bug#1068210: marked as done (fricas: FTBFS on arm{el,hf}: /<>/src/lisp/fricas-lisp.c:1750:10: error: implicit declaration of function ‘sock_get_string_buf’; did you mean ‘sock_send_string

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 15:36:19 +
with message-id 
and subject line Bug#1068210: fixed in fricas 1.3.10-2
has caused the Debian Bug report #1068210,
regarding fricas: FTBFS on arm{el,hf}: 
/<>/src/lisp/fricas-lisp.c:1750:10: error: implicit declaration of 
function ‘sock_get_string_buf’; did you mean ‘sock_send_string_len’? 
[-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.)


-- 
1068210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fricas
Version: 1.3.10-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=fricas=armhf=1.3.10-1%2Bb2=1711729211=0

/<>/src/lisp/fricas-lisp.c: In function 
‘sock_get_string_buf_wrapper’:
/<>/src/lisp/fricas-lisp.c:1750:10: error: implicit declaration of 
function ‘sock_get_string_buf’; did you mean ‘sock_send_string_len’? 
[-Werror=implicit-function-declaration]
 1750 |   return sock_get_string_buf(i, x->st.st_self, j); }
  |  ^~~
  |  sock_send_string_len
cc1: some warnings being treated as errors

Correctable error: 
Fast links are on: do (si::use-fast-links nil) for debugging
Signalled by COMPILE-FILE.
If continued: Continues anyway.SIMPLE-ERROR: (SYSTEM "/usr/bin/gcc  -c -g 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/<>/gcl-2.6.14=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fsigned-char -pipe 
-fcommon -fno-builtin-malloc -fno-builtin-free -fno-PIE -fno-pie -fno-PIC 
-fno-pic -Wall -Wno-empty-body -Wno-unused-but-set-variable 
-fdollars-in-identifiers -g -I/usr/include/tirpc -D_TIME_BITS=64 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  
-I/usr/lib/gcl-2.6.14/unixport/../h  -O2  -c 
/<>/src/lisp/fricas-lisp.c -o 
/<>/src/lisp/fricas-lisp.o ") returned a non-zero value 1 0.

Broken at COMPILE-FILE.  Type :H for Help.
1 (continue) Continues anyway. 
2  Return to top level. 
BOOTTRAN>>
The compiler was called recursively.
Cannot compile primitives.lisp.
NIL
NIL
NIL
BOOTTRAN>>make[3]: *** [Makefile:249: do_it.gcl] Error 255

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: fricas
Source-Version: 1.3.10-2
Done: Camm Maguire 

We believe that the bug you reported is fixed in the latest version of
fricas, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Camm Maguire  (supplier of updated fricas 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: SHA256

Format: 1.8
Date: Tue, 09 Apr 2024 11:02:50 -0400
Source: fricas
Architecture: source
Version: 1.3.10-2
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Closes: 1068210
Changes:
 fricas (1.3.10-2) unstable; urgency=medium
 .
   * Bug fix: "FTBFS on arm{el,hf}:
 /PKGBUILDDIR/src/lisp/fricas-lisp.c:1750:10: error:
 implicit declaration of function ‘sock_get_string_buf’; did you mean
 ‘sock_send_string_len’? [-Werror=implicit-function-declaration]",
 thanks to Sebastian Ramacher (Closes: #1068210).
Checksums-Sha1:
 5ab2323cb8768f327589371da33e0b3350deb354 2363 fricas_1.3.10-2.dsc
 068d4ef93873eaf4cc58981325cf3ece7a4cad88 246392 fricas_1.3.10-2.debian.tar.xz
 70c2a18bf08f15e50770550429fa0e276f67298e 9823 fricas_1.3.10-2_source.buildinfo
Checksums-Sha256:
 7c979d5c444b033ee8770b63fcb5f0991e02632475a5926e58e29a6f28f37686 2363 
fricas_1.3.10-2.dsc
 b84c911370271124e4c3f05293355b622eaffd7268a07ac5b6e66627d1c83ef6 246392 
fricas_1.3.10-2.debian.tar.xz
 5eb6ab2b5dd825a8d630a6bf763901304b94a4c7c47bf8d10064cd5686df323b 9823 
fricas_1.3.10-2_source.buildinfo
Files:
 16a883f7766c1172c66b7919e8764b9f 2363 math optional fricas_1.3.10-2.dsc
 60607bb32e6ba66d0431738f0f71edf6 246392 math optional 
fricas_1.3.10-2.debian.tar.xz
 ca30b01c1978fffc670f724a61c6aa0a 9823 math optional 

Bug#1068714: packages.debian.org: Please make links to deb.debian.org use HTTPS instead of HTTP

[Pierre-Elliott Bécue]

Package: www.debian.org
Severity: serious
Tags: security
X-Debbugs-Cc: Debian Security Team 

Hello,

In packages.debian.org, links pointing to the different source files
useful for a package are pointing to deb.debian.org via HTTP (not HTTPS)
links.

See https://packages.debian.org/bookworm/python3-pep517, which points
for [pep517_0.13.0-2.debian.tar.xz] to
http://deb.debian.org/debian/pool/main/p/pep517/pep517_0.13.0-2.debian.tar.xz

In these times of supply chain attack reveals etc, I think we would be
best to give HTTPS links.

Regards,
-- 
PEB

Bug#1065963: marked as done (foxeye: FTBFS on arm{el,hf}: configure: error: you have no encryption library but need it for password save.)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 15:49:06 +
with message-id 
and subject line Bug#1065963: fixed in foxeye 0.12.1-5
has caused the Debian Bug report #1065963,
regarding foxeye: FTBFS on arm{el,hf}: configure: error: you have no encryption 
library but need it for password save.
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.)


-- 
1065963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: foxeye
Version: 0.12.1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=foxeye=armhf=0.12.1-4%2Bb1=1709989052=0

yes
checking for strncasecmp... rm: cannot remove 'core': Is a directory
yes
checking for towlower... rm: cannot remove 'core': Is a directory
yes
checking whether you need libcrypt... rm: cannot remove 'core': Is a directory
rm: cannot remove 'core': Is a directory
no
configure: error: you have no encryption library but need it for password save.
rm: cannot remove 'core': Is a directory

...

configure:9575: gcc -o conftest -pthread -O2 -g -pipe -Wall -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fpic -fno-strict-aliasing -Wextra 
-Wno-unused-parameter -Wno-pointer-sign -Wno-long-long -Wno-trigraphs 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,defs -Wl,-O1 -rdynamic -Wl,-z,relro -Wl,-z,now 
conftest.c -lcrypt  >&5
conftest.c: In function 'main':
conftest.c:70:1: error: implicit declaration of function 'crypt' 
[-Werror=implicit-function-declaration]
   70 | crypt ("","");
  | ^
cc1: some warnings being treated as errors


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: foxeye
Source-Version: 0.12.1-5
Done: Andriy Grytsenko 

We believe that the bug you reported is fixed in the latest version of
foxeye, 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 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andriy Grytsenko  (supplier of updated foxeye 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: Tue, 09 Apr 2024 18:15:11 +0300
Source: foxeye
Architecture: source
Version: 0.12.1-5
Distribution: unstable
Urgency: medium
Maintainer: Andriy Grytsenko 
Changed-By: Andriy Grytsenko 
Closes: 1065963
Changes:
 foxeye (0.12.1-5) unstable; urgency=medium
 .
   * Add fix-crypt.patch to fix FTBFS on arm* platforms (Closes: #1065963).
   * Add override on Lintian error library-not-linked-against-libc
Checksums-Sha1:
 42b46f5302e82a7bd5b44acc975b5933de691fe3 2004 foxeye_0.12.1-5.dsc
 15578b0562d6703ca9230bc7a4b58a8f1025cf51 5716 foxeye_0.12.1-5.debian.tar.xz
 723b26c3c35caf027c48defe11e8226dc5413428 6276 foxeye_0.12.1-5_amd64.buildinfo
Checksums-Sha256:
 af982a5b4351adf7fd8cccfd2d8a77bbb142246cab57b374893ed4767de869fc 2004 
foxeye_0.12.1-5.dsc
 c9c5ff9a50639565e5aa8a03cdcf5dbf53a61151991b9697bf5adfbdd75382f8 5716 
foxeye_0.12.1-5.debian.tar.xz
 907cb4a8618bb71d2db1cc730ee8106ecf5fef17a036302ad81c12552a3e6cde 6276 
foxeye_0.12.1-5_amd64.buildinfo
Files:
 afdddcd496bdffc966ca32c80b1ad021 2004 net optional foxeye_0.12.1-5.dsc
 4f55a4d66089bbd4c0e8663f8ce3c594 5716 net optional 
foxeye_0.12.1-5.debian.tar.xz
 33a8656fa5c99eda2f5ea73b610e5186 6276 net optional 
foxeye_0.12.1-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJmFVzZAAoJEAV2MC/hidTSHL4QALAYlNjwUha1epFvBp3HNBRx
t3WuoH4B9axqrJViFPU09hQt2uaa/UHpb6eQ8WuEuNmPLBwYaCGZTRQHlBTithsE
2hklJkXgu2z4+ykMm2+jdcY2tiAH/d8c9IdSDSKfOGucjhkZV/7S5A4cimyHlwR5
pMX9kMIkKOFcGmtmiBCwvgQxZNbEuWW4FqLWuc5hPyMRIZY4NMzjVbYdWtpDDIP9
eaPjUoFNonU1OHuAr92fmu7MoMzeQs+CPUaccFcA9GuVc1sPhwuU6G7NXbmot1hl
6MHrqww6XPZIAmJVIIBJRwG+ia3umWISMH7p9n+gDVWSx1HaylbcClVhjSSDOKf4
MNEhj4WH4qZNj2h16h7zhjKv9x2vhioMl+aeDSIQXVdQ2PAAzBuUFec5jqMt0suB
VfW2vAZ4TK2kxxXiIsLhYBmhxb557/3f0PSm3K5F8gsiC4YbeARVRmAX64Y1hYOG

Bug#1066346: sc: FTBFS: sc.c:1301:46: error: implicit declaration of function ‘list_frames’; did you mean ‘list_ranges’? [-Werror=implicit-function-declaration]

[Adam Majer]

On 2024-04-07 05:23, Ying-Chun Liu (PaulLiu) wrote:

I've fixed the bug. And I'll do NMU if no one object in 10 days.
I'll upload it to the delay/10 queue.

Attachment is the debdiff. Please review it.


Thanks, looks good

- Adam

Bug#1066239: gnome-system-tools: FTBFS: shares-tool.c:113:17: error: implicit declaration of function ‘table_add_share’ [-Werror=implicit-function-declaration]

[Andriy Grytsenko]

Thank you very much for the patch.
Applied it, it looks fine.

Bug#1066396: lftp: FTBFS: ./config.h:2540:11: fatal error: trio.h: No such file or directory

[Benjamin Drung]

On Wed, 13 Mar 2024 13:03:20 +0100 Lucas Nussbaum 
wrote:
> Source: lftp
> Version: 4.9.2-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240313 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > /bin/bash ../libtool --silent  --tag=CC   --mode=compile gcc -
DHAVE_CONFIG_H -I.   -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 -g -Wall -Wall -MT
argmatch.lo -MD -MP -MF $depbase.Tpo -c -o argmatch.lo argmatch.c &&\
> > mv -f $depbase.Tpo $depbase.Plo
> > In file included from argmatch.c:22:
> > ./config.h:2540:11: fatal error: trio.h: No such file or directory
> >  2540 | # include "trio.h"
> >   |   ^~~~
> > compilation terminated.
> > make[5]: *** [Makefile:2321: argmatch.lo] Error 1
> 
> 
> The full build log is available from:
> http://qa-logs.debian.net/2024/03/13/lftp_4.9.2-2_unstable.log
> 
> All bugs filed during this archive rebuild are listed at:
>
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
> or:
>
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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.

We applied following changes in Ubuntu to fix the build failure (patch
attached):

  * Fix C99 compatibility issue (patch taken from upstream)
  * configure.ac: Bump gettext version to 0.21
  * d/rules: Switch to dh to regenerate the configure script
  * Replace obsolete pkg-config build dependency by pkgconf
  * Drop obsolete debian/menu (would be installed by dh)

-- 
Benjamin Drung
Debian & Ubuntu Developer
diff --git a/debian/control b/debian/control
index cea175a..0346640 100644
--- a/debian/control
+++ b/debian/control
@@ -4,7 +4,7 @@ Priority: optional
 Maintainer: Ubuntu Developers 
 XSBC-Original-Maintainer: Noël Köthe 
 Standards-Version: 4.6.1
-Build-Depends: debhelper-compat (= 13), debhelper (>> 13.0.0), libncurses-dev, libreadline-dev, gettext, gawk, bison, libgnutls28-dev, pkg-config, libidn2-dev, zlib1g-dev
+Build-Depends: debhelper-compat (= 13), debhelper (>> 13.0.0), libncurses-dev, libreadline-dev, gettext, gawk, bison, libgnutls28-dev, pkgconf, libidn2-dev, zlib1g-dev
 Homepage: https://lftp.yar.ru
 Rules-Requires-Root: no
 
diff --git a/debian/menu b/debian/menu
deleted file mode 100644
index b0fee43..000
--- a/debian/menu
+++ /dev/null
@@ -1,4 +0,0 @@
-?package(lftp):needs="text" section="Apps/Net" \
-title="Lftp" command="/usr/bin/lftp" \
-hints="FTP" \
-description="Reliable, easy and powerful ftp command-line client"
diff --git a/debian/patches/Fix-C99-compatibility-issue.patch b/debian/patches/Fix-C99-compatibility-issue.patch
new file mode 100644
index 000..745a448
--- /dev/null
+++ b/debian/patches/Fix-C99-compatibility-issue.patch
@@ -0,0 +1,27 @@
+From: DJ Delorie 
+Date: Wed, 8 Feb 2023 23:37:37 -0500
+Subject: Fix C99 compatibility issue
+
+Related to:
+
+  
+  
+
+Closes: #1066396
+Origin: upstream, https://github.com/lavv17/lftp/commit/8af97cc255c3d2488adb107515bd1047dbedadfe
+---
+ m4/needtrio.m4 | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/m4/needtrio.m4 b/m4/needtrio.m4
+index 45478f9..8b350a8 100644
+--- a/m4/needtrio.m4
 b/m4/needtrio.m4
+@@ -9,6 +9,7 @@ AC_DEFUN([LFTP_NEED_TRIO],[
+   else
+ 
+   AC_RUN_IFELSE([AC_LANG_SOURCE([[
++	 #include 
+ 	 int main()
+ 	 {
+ 	unsigned long long x=0,x1;
diff --git a/debian/patches/configure.ac-Bump-gettext-version-to-0.21.patch b/debian/patches/configure.ac-Bump-gettext-version-to-0.21.patch
new file mode 100644
index 000..406de03
--- /dev/null
+++ b/debian/patches/configure.ac-Bump-gettext-version-to-0.21.patch
@@ -0,0 +1,44 @@
+From: Benjamin Drung 
+Date: Tue, 9 Apr 2024 15:08:22 +0200
+Subject: configure.ac: Bump gettext version to 0.21
+
+After running autoreconf and configure on Ubuntu 24.04 (noble), the
+generated `po/Makefile` will fail to run `make install`:
+
+```
+$ make install DESTDIR=debian/lftp
+[...]
+Making install in po
+make[4]: Entering directory 'po'
+debian/lftp/usr/share
+make[4]: debian/lftp/usr/share: Permission denied
+```
+
+This failure is caused by `mkdir_p` pointing to `MKDIR_P` but `MKDIR_P`
+not being defined in 

Bug#1068586: ghc: Broken on arm{el,hf} because of time_t transition

[Ilias Tsitsimpis]

Hi Adrian,

On Tue, Apr 09, 2024 at 12:56PM, Adrian Bunk wrote:
> FTR, in haskell-hourglass this is #1001686 which already failed on x32 
> for this reason.

I believe it's not. haskell-hourglass used to work on arm{el,hf} just
before the time64 transition.

> My reading of the code is that this happens when 
> libraries/time/lib/cbits/HsTime.c returns 0x8000 due to 
> localtime_r() called in this function returning an error.
> 
> The "localtime_r failed" is from
> libraries/time/lib/Data/Time/LocalTime/Internal/TimeZone.hs

The problem is that GHC uses the ccall calling convention in order to
call clock_gettime() [1]. GHC assumes time_t to be 64-bits, but ends up
calling the old 32-bits variant of clock_gettime(), and not the new one
__clock_gettime64().

Here is more information about GHC's FFI calling conventions[2].
Here is also an upstream issue about this[3].

[1] 
https://gitlab.haskell.org/ghc/packages/time/-/blob/baab563ee2ce547f7b7f7e7069ed09db2d406941/lib/Data/Time/Clock/Internal/CTimespec.hsc#L30
[2] https://www.haskell.org/ghc/blog/20210709-capi-usage.html
[3] https://github.com/haskell/directory/pull/145

The fix here is to backport (at least) the following patches which
change these calls to use the capi calling convention:

  * 
https://gitlab.haskell.org/ghc/packages/time/-/commit/d52314edb138b6ecd7e888c588f83917b0ee2c29
  * 
https://gitlab.haskell.org/ghc/packages/directory/-/commit/f6b288bd96fba5a955d1f73663eb52c1859ee765

Other Haskell libraries may have the same bug as GHC if they are calling
directly the C functions using the ccall calling convention. An example
is haskell-hourglass, which needs to be patched as well:

  * 
https://github.com/vincenthz/hs-hourglass/blob/36bd2e6d5d0eb316532f13285d1c533d6da297ef/Data/Hourglass/Internal/Unix.hs#L82

We need a way to identify every package that is broken.

-- 
Ilias

Bug#1068473: marked as done (icinga2: crashes on startup on ppc64el)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 16:47:10 +
with message-id 
and subject line Bug#1068473: fixed in icinga2 2.13.6-2+deb12u1
has caused the Debian Bug report #1068473,
regarding icinga2: crashes on startup on ppc64el
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.)


-- 
1068473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icinga2
Version: 2.13.6-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: d...@debian.org
Control: fixed -1 icinga2/2.14.2-1

Dear maintainer,

DSA has issues running icinga2 on ppc64el on Bookworm, it fails with a
segmentation fault just after startup:

| × icinga2.service - Icinga host/service/network monitoring system
|  Loaded: loaded (/lib/systemd/system/icinga2.service; enabled; preset: 
enabled)
|  Active: failed (Result: exit-code) since Thu 2024-04-04 20:55:13 UTC; 
3min 57s ago
|Duration: 1.209s
|Docs: https://icinga.com/docs/icinga2/latest/
| Process: 356368 ExecStartPre=/usr/lib/icinga2/prepare-dirs 
/usr/lib/icinga2/icinga2 (code=exited, status=0/SUCCESS)
| Process: 356373 ExecStart=/usr/sbin/icinga2 daemon --close-stdio -e 
${ICINGA2_ERROR_LOG} (code=exited, status=139)
|Main PID: 356373 (code=exited, status=139)
|  Status: "Startup finished."
| CPU: 473ms
| 
| Apr 04 20:55:12 platti icinga2[356415]: [2024-04-04 20:55:12 +] 
information/ConfigItem: Instantiated 1 IcingaApplication.
| Apr 04 20:55:12 platti icinga2[356415]: [2024-04-04 20:55:12 +] 
information/ConfigItem: Instantiated 2 Endpoints.
| Apr 04 20:55:12 platti icinga2[356415]: [2024-04-04 20:55:12 +] 
information/ConfigItem: Instantiated 1 FileLogger.
| Apr 04 20:55:12 platti icinga2[356415]: [2024-04-04 20:55:12 +] 
information/ConfigItem: Instantiated 249 CheckCommands.
| Apr 04 20:55:12 platti icinga2[356415]: [2024-04-04 20:55:12 +] 
information/ConfigItem: Instantiated 1 ApiListener.
| Apr 04 20:55:12 platti icinga2[356415]: [2024-04-04 20:55:12 +] 
information/ScriptGlobal: Dumping variables to file 
'/var/cache/icinga2/icinga2.vars'
| Apr 04 20:55:12 platti systemd[1]: Started icinga2.service - Icinga 
host/service/network monitoring system.
| Apr 04 20:55:12 platti icinga2[356373]: [2024-04-04 20:55:12 +] 
information/cli: Closing console log.
| Apr 04 20:55:13 platti systemd[1]: icinga2.service: Main process exited, 
code=exited, status=139/n/a
| Apr 04 20:55:13 platti systemd[1]: icinga2.service: Failed with result 
'exit-code'.

I have been able to obtain a backtrace:

| (gdb) bt full
| #0  0x000127d44850 in icinga::JsonRpcConnection::CheckLiveness 
(this=this@entry=0x0, yc=...) at ./lib/remote/jsonrpcconnection.cpp:344
| ec = {val_ = 0, failed_ = false, cat_ = 0x0}
| #1  0x000127d44f04 in operator() (__closure=0x7fff7c002620, yc=...) at 
./lib/remote/jsonrpcconnection.cpp:58
| keepAlive = {px = 0x0}
| this = 0x0
| keepAlive = 
| this = 
| #2  operator() (__closure=__closure@entry=0x7fff7c002620, yc=...) at 
./lib/base/io-engine.hpp:106
| f = {__this = 0x0, __keepAlive = {px = 0x0}}
| #3  0x000127d521bc in 
boost::asio::detail::coro_entry_point, 
icinga::IoEngine::SpawnCoroutine 
>(boost::asio::io_context::strand&, 
icinga::JsonRpcConnection::Start()::)::
 >::operator() (
| ca=..., this=) at 
/usr/include/boost/asio/impl/spawn.hpp:355
| data = 
| yield = {coro_ = 
std::weak_ptr> (use count 1, weak count 
5) = {get() = 0x7fff7c0c3640}, ca_ = @0x7fff7c103488,
|   handler_ = {> = {}, 
> = {}, > = {}, > = {executor_ = {service_ = 
@0x7fff94003150,
| impl_ = 0x7fff7c002040}, target_ = 0x127d70760 
}, }, ec_ = 0x0}
| data = 
| yield = 
| #4  
boost::coroutines::detail::push_coroutine_object,
 void, boost::asio::detail::coro_entry_point, 
icinga::IoEngine::SpawnCoroutine 
>(boost::asio::io_context::strand&, 
icinga::JsonRpcConnection::Start()::)::
 >&, 
boost::coroutines::basic_standard_stack_allocator
 >::run (this=0x7fff7c1035c0)
| at /usr/include/boost/coroutine/detail/push_coroutine_object.hpp:302
| b = {> = 
{ = { = {}, },
| _vptr.pull_coroutine_impl = 0x12884b938 +16>, flags_ = 0, 
except_ = {ptr_ = {px = 0x0, pn = {pi_ = 0x0}}}, caller_ = 0x7fff7c103618,
| callee_ = 0x7fff7c1035f0}, }
| push_coro = {impl_ = 0x7fff7c103490}
| to = {do_unwind = 64, coro = 0x7fff7c103670}
| __PRETTY_FUNCTION__ = 
| b = 
| push_coro = 
| to 

Bug#1068653: marked as done (evolution: Can't use google accounts)

[Debian Bug Tracking System]

Your message dated Mon, 08 Apr 2024 14:29:42 -0400
with message-id 
and subject line close
has caused the Debian Bug report #1068653,
regarding evolution: Can't use google accounts
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.)


-- 
1068653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: evolution
Version: 3.50.3-1+b1
Severity: grave

I have two accounts (personal and work) and both of them are returning
“Timeout was reached”.  I have tried removing the accounts and re-adding
them without success.

personal account is @gmail.com

work account is @EMPLOYER'S-DOMAIN

-- System Information
Debian Release: 12.5
Kernel Version: Linux gabriel 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.1.76-1 (2024-02-01) x86_64 GNU/Linux

-- 
http://hexmode.com/

Don't ask me who's influenced me. A lion is made up of the
lambs he's digested, and I've been reading all my life.
-- Giorgos Seferis
--- End Message ---
--- Begin Message ---
Rebooting laptop allowed it to work after upgrading to unstable.--- End Message ---

Bug#1068698: marked as done (hdf-eos5 2:2.0-2 silently reverts the 64-bit time_t transition)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 18:00:11 +
with message-id 
and subject line Bug#1068698: fixed in hdf-eos5 2:2.0-3
has caused the Debian Bug report #1068698,
regarding hdf-eos5 2:2.0-2 silently reverts the 64-bit time_t transition
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.)


-- 
1068698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hdf-eos5
Severity: serious
X-Debbugs-Cc: j...@debian.org

hdf-eos5 2:2.0-2 ignores the hdf-eos5 2:2.0-1.1 NMU that introduced the
time_t renames (that was Bug##1063118), causing misbuilt libhe5-hdfeos0
with the new ABI, potentially breaking applications built against it.

-- System Information:
Debian Release: trixie/sid
  APT prefers noble-updates
  APT policy: (500, 'noble-updates'), (500, 'noble'), (500, 'mantic-security'), 
(100, 'noble-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.8.0-20-generic (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
--- End Message ---
--- Begin Message ---
Source: hdf-eos5
Source-Version: 2:2.0-3
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
hdf-eos5, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated hdf-eos5 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: SHA256

Format: 1.8
Date: Tue, 09 Apr 2024 10:53:23 +0100
Source: hdf-eos5
Binary: libhe5-hdfeos-dev libhe5-hdfeos0t64 libhe5-hdfeos0t64-dbgsym
Architecture: source arm64
Version: 2:2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libhe5-hdfeos-dev - Development files for the HDF-EOS5 library
 libhe5-hdfeos0t64 - Earth Observation System extensions to HDF5
Closes: 1063118 1068698
Changes:
 hdf-eos5 (2:2.0-3) unstable; urgency=medium
 .
   * Redo patch for t64 transition that was accidentally dropped.
 Closes: #1063118, #1068698
Checksums-Sha1:
 07307a5a5f3e15c4ffa0035c873d9735458be447 2053 hdf-eos5_2.0-3.dsc
 996ee813be7a27f2fe5e8959679e87505dd9cb86 10752 hdf-eos5_2.0-3.debian.tar.xz
 7c232b8bb42590e0de57fa7d0f8577820d85eb59 9931 hdf-eos5_2.0-3_arm64.buildinfo
 f7926347f9b8bab3a7a187e457177aeb3db63959 422136 
libhe5-hdfeos-dev_2.0-3_arm64.deb
 5a0034002271c510af70408742bb96e6367d8e6e 1235600 
libhe5-hdfeos0t64-dbgsym_2.0-3_arm64.deb
 92cebb2d901fde482f248b3709028c90b3e116af 300284 
libhe5-hdfeos0t64_2.0-3_arm64.deb
Checksums-Sha256:
 ecfb9709155cf3a71e4500e1b6f501f16ade0fbe39e981391de06ba38d206017 2053 
hdf-eos5_2.0-3.dsc
 6a9160c0e306081d6846b495ab5ea0f9eecb966ffdd25b2400d62b009f96d0b6 10752 
hdf-eos5_2.0-3.debian.tar.xz
 ff8f1aa51a3398e82e448b7db3b97d4b26cc49e7fd2cb65361dd50d703ac0adc 9931 
hdf-eos5_2.0-3_arm64.buildinfo
 c88a8dd2a2eb1de2d367fcad024c92e50978167517464a558d4b37d81f1ea11f 422136 
libhe5-hdfeos-dev_2.0-3_arm64.deb
 cea562d70b17c0413c4502c1c4fc766d7a59b23f6b1c434ecf7af744d677979c 1235600 
libhe5-hdfeos0t64-dbgsym_2.0-3_arm64.deb
 3a6591bfc384b566bd95ef9c208751d8f717a697384e251df282cf2a5567263a 300284 
libhe5-hdfeos0t64_2.0-3_arm64.deb
Files:
 f5906843b1fb8193580dea6fba7aba37 2053 libs optional hdf-eos5_2.0-3.dsc
 2e8eef19956bb9a48f3270eff7e972c5 10752 libs optional 
hdf-eos5_2.0-3.debian.tar.xz
 7930c47abc171b1ce7ad8ccab1168090 9931 libs optional 
hdf-eos5_2.0-3_arm64.buildinfo
 e7e8be0b227ffa6c857564ba8c1eaee8 422136 libdevel optional 
libhe5-hdfeos-dev_2.0-3_arm64.deb
 06b644d3c1e76f16656fa3fb9cc8b047 1235600 debug optional 
libhe5-hdfeos0t64-dbgsym_2.0-3_arm64.deb
 7d2604ec93f75f24fce0bb8610eff8d5 300284 libs optional 
libhe5-hdfeos0t64_2.0-3_arm64.deb

-BEGIN PGP SIGNATURE-

Bug#1068653: close

[Mark A. Hershberger]

close #1068653

Restarting laptop after upgrading to unstable (from stable) worked.

Bug#1066522: marked as done (netpipe: FTBFS: ./src/mpi2.c:110:7: error: implicit declaration of function ‘sched_yield’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 16:22:34 +
with message-id 
and subject line Bug#1066522: fixed in netpipe 3.7.2-9
has caused the Debian Bug report #1066522,
regarding netpipe: FTBFS: ./src/mpi2.c:110:7: error: implicit declaration of 
function ‘sched_yield’ [-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.)


-- 
1066522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netpipe
Version: 3.7.2-8.1
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):
> make[1]: Entering directory '/<>'
> mpicc.lam -Wl,-z,relro -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 -DMPI -DMPI2 ./src/netpipe.c \
>./src/mpi2.c -o NPmpi2 -I./ 
> ./src/mpi2.c: In function ‘RecvData’:
> ./src/mpi2.c:110:7: error: implicit declaration of function ‘sched_yield’ 
> [-Werror=implicit-function-declaration]
>   110 |   sched_yield(); /* Since we made r_ptr volatile, we don't 
> necessarily
>   |   ^~~
> cc1: some warnings being treated as errors
> mpicc.lam: No such file or directory
> make[1]: *** [makefile:255: mpi2] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/netpipe_3.7.2-8.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: netpipe
Source-Version: 3.7.2-9
Done: Camm Maguire 

We believe that the bug you reported is fixed in the latest version of
netpipe, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Camm Maguire  (supplier of updated netpipe 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: SHA256

Format: 1.8
Date: Tue, 09 Apr 2024 11:49:01 -0400
Source: netpipe
Architecture: source
Version: 3.7.2-9
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Closes: 1066522
Changes:
 netpipe (3.7.2-9) unstable; urgency=medium
 .
   * Bug fix: "FTBFS: ./src/mpi2.c:110:7: error: implicit declaration of
 function ‘sched_yield’ [-Werror=implicit-function-declaration]",
 thanks to Lucas Nussbaum (Closes: #1066522).
Checksums-Sha1:
 8c9bc41af7c34c5b655c07388e9786b9b81c0ce0 2005 netpipe_3.7.2-9.dsc
 3b63fadcb318ddb0ca75879ae8044e4d3a94abf6 12136 netpipe_3.7.2-9.debian.tar.xz
 bda16312edbddf548f8135f145d3b4b5b9605fb2 8119 netpipe_3.7.2-9_source.buildinfo
Checksums-Sha256:
 bfc5151627e372de4468828d1bdf3c96be018710dfeaa5710bee14f60f484cf4 2005 
netpipe_3.7.2-9.dsc
 2ad32cb59fd7f5bd7629675220216ac26911cca10c6945482fa053f4133ecf41 12136 
netpipe_3.7.2-9.debian.tar.xz
 0e0f7a3f08256a410e757375ab90419892c1ca3b82453f4171b5148ad39aa5d6 8119 
netpipe_3.7.2-9_source.buildinfo
Files:
 d3bfc39013632dbf224a36f0fa117b26 2005 net optional netpipe_3.7.2-9.dsc
 ba1f50a17e406d3186b3d3a2bf2fd5a7 12136 net optional 

Bug#1068586: ghc: Broken on arm{el,hf} because of time_t transition

[Adrian Bunk]

On Tue, Apr 09, 2024 at 07:23:29PM +0300, Ilias Tsitsimpis wrote:
> Hi Adrian,

Hi Ilias,

> On Tue, Apr 09, 2024 at 12:56PM, Adrian Bunk wrote:
> > FTR, in haskell-hourglass this is #1001686 which already failed on x32 
> > for this reason.
> 
> I believe it's not. haskell-hourglass used to work on arm{el,hf} just
> before the time64 transition.

before this transition x32 was the only 32bit architecture with 64bit time_t.

> > My reading of the code is that this happens when 
> > libraries/time/lib/cbits/HsTime.c returns 0x8000 due to 
> > localtime_r() called in this function returning an error.
> > 
> > The "localtime_r failed" is from
> > libraries/time/lib/Data/Time/LocalTime/Internal/TimeZone.hs
>...
> The fix here is to backport (at least) the following patches which
> change these calls to use the capi calling convention:
> 
>   * 
> https://gitlab.haskell.org/ghc/packages/time/-/commit/d52314edb138b6ecd7e888c588f83917b0ee2c29
>   * 
> https://gitlab.haskell.org/ghc/packages/directory/-/commit/f6b288bd96fba5a955d1f73663eb52c1859ee765

This localtime_r issue I mentioned is not covered in the above commit in 
time.

>...
> We need a way to identify every package that is broken.

$ nm -D /usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHStime-1.12.2-ghc9.4.7.so | 
grep gettimeofday
 U gettimeofday@GLIBC_2.4
...

$ nm -D /usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHSdirectory-1.3.7.1-ghc9.4.7.so 
| grep utimensat 
...
 U utimensat@GLIBC_2.6

$ nm -D /usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHStime-1.12.2-ghc9.4.7.so | 
grep localtime
 U __localtime64_r@GLIBC_2.34


But the last one is the broken localtime_r one, is anything going wrong 
with the ccall from TimeZone.hs to cbits there?

get_current_timezone_seconds() returning long is wrong,
and might contribute to that bug:

  foreign import ccall unsafe "HsTime.h get_current_timezone_seconds"
get_current_timezone_seconds ::
CTime -> Ptr CInt -> Ptr CString -> IO CLong
...
  getTimeZoneCTime ctime =
...
secs <- get_current_timezone_seconds ctime pdst pcname

I don't know Haskell, but is this declaring ctime as CLong,
and then passing it instead of a CTime?


> Ilias

cu
Adrian

Bug#1067957: [[maude-bugs]] [EXTERNAL] Re: Maude fails to build on armhf

[Steven Eker]

Hi Sebastian,

The lack of long long support in GMP has been the subject of some 
discussions:


https://gmplib.org/list-archives/gmp-bugs/2020-June/thread.html#4771
https://gmplib.org/list-archives/gmp-discuss/2021-January/thread.html#6625

I don't see it happening soon - it took years for the x18 issue on Apple 
silicon to be fixed.

In my development version I've modified the code to:

  Index seconds = timeValue.tv_sec;  // this is 32-bit on 32-bit 
machines so mpz_class constuctor is defined

  mpz_class nanoSeconds(seconds);
  nanoSeconds *= BILLION;
  nanoSeconds += timeValue.tv_nsec;

This is harmless on 64-bit architectures since Index will be a signed 
64-bit integer and if it works on 32-bit architectures, it's a work 
around until GMP is fixed (hopefully before 2038).


Steven

On 4/9/24 00:01, Sebastian Ramacher wrote:

Hi Steven

On 2024-04-08 15:38:50 -0700, Steven Eker wrote:

Hi Nilish,

I don't have a 32-bit machine to test on, but my understanding is that Linux
has moved to a 64-bit signed integer for time_t and this is a long long on
32-bit machines which is explicitly not supported by GMP's C++ API.

This sounds like it needs to fixed in GMP then.


https://urldefense.com/v3/__https://en.wikipedia.org/wiki/Year_2038_problem__;!!DZ3fjg!--tzUBTnQHRKfnkc8PqaPE5gHxPm2QWswg2_MWTbLaWxFFDXu6jiPCjltocalTdckv2oG8G8tDajml0HNO6JIFyo$
https://urldefense.com/v3/__https://gmplib.org/manual/C_002b_002b-Interface-Integers__;!!DZ3fjg!--tzUBTnQHRKfnkc8PqaPE5gHxPm2QWswg2_MWTbLaWxFFDXu6jiPCjltocalTdckv2oG8G8tDajml0HNHAQQdRg$

I'm not happy converting a signed value to an unsigned value for all
architectures. But

   mpz_class nanoSeconds(static_cast(timeValue.tv_sec));

should fix the problem, at least until 2038. Can you check that this works?
If so I'll put it in the next public alpha.

And this does not sound like a fix which we want.

Best
Sebastian

Bug#1068721: Depends on nonexistant librust-parking-2+std-dev

[Matthias Geiger]

Package: librust-event-listener-dev
Severity: serious
X-Debbugs-Cc: werdah...@riseup.net

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Jonas,

thanks for updating event-listener.
However, the package is unistallable for me:

sudo apt install librust-event-listener-dev -t experimental  -s
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
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:
 librust-event-listener-dev : Depends: librust-parking-2+std-dev but it is not 
installable
E: Unable to correct problems, you have held broken packages.

parking does not have a +std feature enabled:

[...]

Provides:
  librust-parking+default-dev
  librust-parking-2+default-dev
  librust-parking-2-dev
  librust-parking-2.0+default-dev
  librust-parking-2.0-dev
  librust-parking-2.0.0+default-dev
  librust-parking-2.0.0-dev
Replaces: librust-parking-dev
[...]

best,

werdahias

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

Kernel: Linux 6.5.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled

Versions of packages librust-event-listener-dev depends on:
pn  librust-concurrent-queue-2+std-dev
pn  librust-parking-2+std-dev 
pn  librust-pin-project-lite-0.2+default-dev  

librust-event-listener-dev recommends no packages.

librust-event-listener-dev suggests no packages.

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmYVhPkVHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR11vMQAMBgRGPBHxDTy7893h2ovmTguPBs
1hqSiZFgZVaySLtMd0RY2MT3YlaCfUQGVMmyHMBVjHc0FLj0YZxSrSI7760bBNL7
O7binQZEl0VIGUb1TKSHNTiapo9l8xKwuwt3nG5ObttQV3cFk0vxIHgUjjpHffYE
sZOD2cLZYx5zLU29TGSDP/WIqMCaBhUwDHNqQGihpuVniRzKO9b0YTBvsNSrKy9+
+vh8CiK2sQzNcpcFgPH3nlhIDUj+XEfo4rEWBIuO7MDbuFCPehmoBGQnM7nnmB9e
3XGamSigg8+ZUJhKa5AbTppZbugLCfXW2htqaX6bVuseFmfKtGxfnXK01Xvsgi+x
7tucQpUcVEpXGh7pA2VmKNOVSvFUWH+m/QI5XN2gtnaVICe1pHpPPaIGHIdSQhyA
Ua0tSSM0MDsjJ0KUU3y+ZPW7zAfdTenSwkqCWbEyGQ0+A9xLXWhsm7zEbTyfSK+g
3SwueCajbKNFFCG71Hot/VgMyfTPQwbJcy6bQmDVWTipDGymEmwpce83tO9Ec3IW
t52ShOPUjWiKWtIeI2ScSIsesS/2XZmqAEx2LJTB5oObpJe4XIfTeG5Sm9mZrhpN
ODowu6du/WJ6vz1sM+OhawysJbM3jZFFBKEfzD+LwglN70mAfZ7f7gZfkcByc+BD
gBpcQKl3ZqfaDoPn
=ppql
-END PGP SIGNATURE-

Bug#1068586: ghc: Broken on arm{el,hf} because of time_t transition

[Ilias Tsitsimpis]

On Tue, Apr 09, 2024 at 08:53PM, Adrian Bunk wrote:
> On Tue, Apr 09, 2024 at 07:23:29PM +0300, Ilias Tsitsimpis wrote:
> > I believe it's not. haskell-hourglass used to work on arm{el,hf} just
> > before the time64 transition.
> 
> before this transition x32 was the only 32bit architecture with 64bit time_t.

Aha! Didn't know that, thanks for flagging this. I am surprised that we
hadn't noticed this earlier (as we see now, GHC is completely broken).

> > The fix here is to backport (at least) the following patches which
> > change these calls to use the capi calling convention:
> > 
> >   * 
> > https://gitlab.haskell.org/ghc/packages/time/-/commit/d52314edb138b6ecd7e888c588f83917b0ee2c29
> >   * 
> > https://gitlab.haskell.org/ghc/packages/directory/-/commit/f6b288bd96fba5a955d1f73663eb52c1859ee765
> 
> This localtime_r issue I mentioned is not covered in the above commit in 
> time.

Hmm true. My guess here is that GHC gets a completely bogus CTime value
back from clock_gettime() (we proved that the way we call
clock_gettime() is currently broken) and when it passes this CTime value
to localtime_r() it fails. I haven't verified any of this, just a guess.

> > We need a way to identify every package that is broken.
> 
> $ nm -D /usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHStime-1.12.2-ghc9.4.7.so | 
> grep gettimeofday
>  U gettimeofday@GLIBC_2.4
> ...
> 
> $ nm -D 
> /usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHSdirectory-1.3.7.1-ghc9.4.7.so | 
> grep utimensat 
> ...
>  U utimensat@GLIBC_2.6
> 
> $ nm -D /usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHStime-1.12.2-ghc9.4.7.so | 
> grep localtime
>  U __localtime64_r@GLIBC_2.34

Thank you! Can we maybe run this against all Haskell libraries and
identify the ones that are currently broken? Maybe we have such a script
already for the time64 transition.

> But the last one is the broken localtime_r one, is anything going wrong 
> with the ccall from TimeZone.hs to cbits there?
> 
> get_current_timezone_seconds() returning long is wrong,
> and might contribute to that bug:
> 
>   foreign import ccall unsafe "HsTime.h get_current_timezone_seconds"
> get_current_timezone_seconds ::
> CTime -> Ptr CInt -> Ptr CString -> IO CLong
> ...
>   getTimeZoneCTime ctime =
> ...
> secs <- get_current_timezone_seconds ctime pdst pcname
> 
> I don't know Haskell, but is this declaring ctime as CLong,
> and then passing it instead of a CTime?

I believe it returns the timezone in seconds (i.e., 3600 for +1 hour
timezone), so CLong should be large enough to hold this value. My guess
right now is that it fails due to the bogus CTime value that we pass, we
need to test this.

-- 
Ilias

Bug#1068721: Depends on nonexistant librust-parking-2+std-dev

[Jonas Smedegaard]

Quoting Matthias Geiger (2024-04-09 20:12:13)
 
> parking does not have a +std feature enabled:

Whoops, sorry about that - a silly typo.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1068721: marked as done (Depends on nonexistant librust-parking-2+std-dev)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 19:05:29 +
with message-id 
and subject line Bug#1068721: fixed in rust-event-listener 5.3.0-2
has caused the Debian Bug report #1068721,
regarding Depends on nonexistant librust-parking-2+std-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.)


-- 
1068721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-event-listener-dev
Severity: serious
X-Debbugs-Cc: werdah...@riseup.net

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Jonas,

thanks for updating event-listener.
However, the package is unistallable for me:

sudo apt install librust-event-listener-dev -t experimental  -s
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
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:
 librust-event-listener-dev : Depends: librust-parking-2+std-dev but it is not 
installable
E: Unable to correct problems, you have held broken packages.

parking does not have a +std feature enabled:

[...]

Provides:
  librust-parking+default-dev
  librust-parking-2+default-dev
  librust-parking-2-dev
  librust-parking-2.0+default-dev
  librust-parking-2.0-dev
  librust-parking-2.0.0+default-dev
  librust-parking-2.0.0-dev
Replaces: librust-parking-dev
[...]

best,

werdahias

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

Kernel: Linux 6.5.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled

Versions of packages librust-event-listener-dev depends on:
pn  librust-concurrent-queue-2+std-dev
pn  librust-parking-2+std-dev 
pn  librust-pin-project-lite-0.2+default-dev  

librust-event-listener-dev recommends no packages.

librust-event-listener-dev suggests no packages.

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmYVhPkVHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR11vMQAMBgRGPBHxDTy7893h2ovmTguPBs
1hqSiZFgZVaySLtMd0RY2MT3YlaCfUQGVMmyHMBVjHc0FLj0YZxSrSI7760bBNL7
O7binQZEl0VIGUb1TKSHNTiapo9l8xKwuwt3nG5ObttQV3cFk0vxIHgUjjpHffYE
sZOD2cLZYx5zLU29TGSDP/WIqMCaBhUwDHNqQGihpuVniRzKO9b0YTBvsNSrKy9+
+vh8CiK2sQzNcpcFgPH3nlhIDUj+XEfo4rEWBIuO7MDbuFCPehmoBGQnM7nnmB9e
3XGamSigg8+ZUJhKa5AbTppZbugLCfXW2htqaX6bVuseFmfKtGxfnXK01Xvsgi+x
7tucQpUcVEpXGh7pA2VmKNOVSvFUWH+m/QI5XN2gtnaVICe1pHpPPaIGHIdSQhyA
Ua0tSSM0MDsjJ0KUU3y+ZPW7zAfdTenSwkqCWbEyGQ0+A9xLXWhsm7zEbTyfSK+g
3SwueCajbKNFFCG71Hot/VgMyfTPQwbJcy6bQmDVWTipDGymEmwpce83tO9Ec3IW
t52ShOPUjWiKWtIeI2ScSIsesS/2XZmqAEx2LJTB5oObpJe4XIfTeG5Sm9mZrhpN
ODowu6du/WJ6vz1sM+OhawysJbM3jZFFBKEfzD+LwglN70mAfZ7f7gZfkcByc+BD
gBpcQKl3ZqfaDoPn
=ppql
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-event-listener
Source-Version: 5.3.0-2
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
rust-event-listener, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-event-listener 
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: Tue, 09 Apr 2024 20:52:07 +0200
Source: rust-event-listener
Architecture: source
Version: 5.3.0-2
Distribution: experimental
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1068721
Changes:
 rust-event-listener (5.3.0-2) experimental; urgency=medium
 .
   * fix dependency for crate parking; closes: bug#1068721, thanks to Matthias 
Geiger
Checksums-Sha1:
 c6c0983ccc50099bd9d42366c85cab41f26b83b8 2519 

Bug#1068586: ghc: Broken on arm{el,hf} because of time_t transition

[Adrian Bunk]

[ Steve added, for the symbol list question ]

On Tue, Apr 09, 2024 at 09:44:43PM +0300, Ilias Tsitsimpis wrote:
> On Tue, Apr 09, 2024 at 08:53PM, Adrian Bunk wrote:
> > On Tue, Apr 09, 2024 at 07:23:29PM +0300, Ilias Tsitsimpis wrote:
> > > I believe it's not. haskell-hourglass used to work on arm{el,hf} just
> > > before the time64 transition.
> > 
> > before this transition x32 was the only 32bit architecture with 64bit 
> > time_t.
> 
> Aha! Didn't know that, thanks for flagging this. I am surprised that we
> hadn't noticed this earlier (as we see now, GHC is completely broken).

I wouldn't call it "completely broken".

I'm too lazy to get exact numbers, but the arm{el,hf} situation is more 
like 1000 packages built (a large part with tests) and 10 failed.

>...
> > > We need a way to identify every package that is broken.
> > 
> > $ nm -D /usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHStime-1.12.2-ghc9.4.7.so | 
> > grep gettimeofday
> >  U gettimeofday@GLIBC_2.4
> > ...
> > 
> > $ nm -D 
> > /usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHSdirectory-1.3.7.1-ghc9.4.7.so | 
> > grep utimensat 
> > ...
> >  U utimensat@GLIBC_2.6
> > 
> > $ nm -D /usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHStime-1.12.2-ghc9.4.7.so | 
> > grep localtime
> >  U __localtime64_r@GLIBC_2.34
> 
> Thank you! Can we maybe run this against all Haskell libraries and
> identify the ones that are currently broken? Maybe we have such a script
> already for the time64 transition.

Steve, do you have a list of all bad symbols for the time_t transition?

With this list it should be possible to just install all currently 
installable Haskell packages on a porterbox and do something like

$ for s in gettimeofday utimensat localtime localtime_r; do for f in 
/usr/lib/ghc/lib/arm-linux-ghc-9.4.7/*.so 
/usr/lib/haskell-packages/ghc/lib/arm-linux-ghc-9.4.7/*.so; do nm -D $f | grep 
$s@ && echo $f; done; done
 U gettimeofday@GLIBC_2.4
/usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHStime-1.12.2-ghc9.4.7.so
 U utimensat@GLIBC_2.6
/usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHSdirectory-1.3.7.1-ghc9.4.7.so
 U utimensat@GLIBC_2.6
/usr/lib/ghc/lib/arm-linux-ghc-9.4.7/libHSunix-2.7.3-ghc9.4.7.so
$

That last one is likely
libraries/unix/System/Posix/Files/Common.hsc:foreign import ccall unsafe 
"utimensat"

> > But the last one is the broken localtime_r one, is anything going wrong 
> > with the ccall from TimeZone.hs to cbits there?
> > 
> > get_current_timezone_seconds() returning long is wrong,
> > and might contribute to that bug:
> > 
> >   foreign import ccall unsafe "HsTime.h get_current_timezone_seconds"
> > get_current_timezone_seconds ::
> > CTime -> Ptr CInt -> Ptr CString -> IO CLong
> > ...
> >   getTimeZoneCTime ctime =
> > ...
> > secs <- get_current_timezone_seconds ctime pdst pcname
> > 
> > I don't know Haskell, but is this declaring ctime as CLong,
> > and then passing it instead of a CTime?
> 
> I believe it returns the timezone in seconds (i.e., 3600 for +1 hour
> timezone), so CLong should be large enough to hold this value. My guess
> right now is that it fails due to the bogus CTime value that we pass, we
> need to test this.

Yes, I suspect that this function with
  CTime -> Ptr CInt -> Ptr CString -> IO CLong
gets called as
  CLong -> Ptr CInt -> Ptr CString -> IO CLong
but I'm surprised if Haskell does not catch something like that at 
compile time.

> Ilias

cu
Adrian

Bug#1068723: quickflux: binary-any FTBFS

[Adrian Bunk]

Source: quickflux
Version: 1.1.3+git20201110.2a37acf-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Debian UBports Team 

https://buildd.debian.org/status/logs.php?pkg=quickflux=1.1.3%2Bgit20201110.2a37acf-1

...
   debian/rules override_dh_installexamples
make[1]: Entering directory '/<>'
dh_installexamples
rm 
debian/quickflux-doc/usr/share/doc/quickflux-doc/examples/middleware/.gitignore
rm: cannot remove 
'debian/quickflux-doc/usr/share/doc/quickflux-doc/examples/middleware/.gitignore':
 No such file or directory
make[1]: *** [debian/rules:33: override_dh_installexamples] Error 1

Bug#1068384: marked as done (python-hdf4: FTBFS with HDF 4.3.0.)

[Debian Bug Tracking System]

Your message dated Tue, 09 Apr 2024 19:19:33 +
with message-id 
and subject line Bug#1068384: fixed in python-hdf4 0.11.4-2
has caused the Debian Bug report #1068384,
regarding python-hdf4: FTBFS with HDF 4.3.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.)


-- 
1068384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-hdf4
Version: 0.11.4-1
Severity: serious
Tags: upstream ftbfs
Justification: makes the package in question unusable or mostly so
User: debian-...@lists.debian.org
Usertags: hdf-4.3

Dear Maintainer,

Your package FTBFS while performing test rebuilds with HDF 4.3.20.

 pyhdf/hdfext_wrap.c:3845:10: fatal error: hdfi.h: No such file or directory
  3845 | #include "hdfi.h" /* declares int32, float32, etc */
   |  ^~~~

The hdfi.h private header was removed. See:

 https://github.com/HDFGroup/hdf4/blob/hdf4.3.0/doc/HDF-4.2-to-4.3-migration.md

Kind Regards,

Bas
dpkg-checkbuilddeps: error: Unmet build dependencies: pybuild-plugin-pyproject
W: Unmet build-dependency in source
dh clean --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building python-hdf4 using existing 
./python-hdf4_0.11.4.orig.tar.gz
dpkg-source: info: building python-hdf4 in python-hdf4_0.11.4-1.1.debian.tar.xz
dpkg-source: info: building python-hdf4 in python-hdf4_0.11.4-1.1.dsc
I: Generated dsc will be overwritten by build result; not generating 
changes file
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.460859
I: forking: cp -al /var/cache/pbuilder/base-sid+rebuild.cow 
/var/cache/pbuilder/build/cow.460859
I: removed stale ilistfile /var/cache/pbuilder/build/cow.460859/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.460859 cowdancer-ilistcreate 
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts  --debbuildopts  --buildplace 
/var/cache/pbuilder/build/cow.460859 --buildresult .. --mirror 
http://ftp.nl.debian.org/debian/ --distribution sid --no-targz 
--internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.460859 cow-shell' 
/home/bas/tmp/debian/python-hdf4_0.11.4-1.1.dsc
I: Running in no-targz mode
I: pbuilder: network access will be disabled during build
I: Current time: Thu Apr  4 12:47:57 CEST 2024
I: pbuilder-time-stamp: 1712227677
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage 
for details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [/home/bas/tmp/debian/python-hdf4_0.11.4-1.1.dsc]
I: copying [/home/bas/tmp/debian/python-hdf4_0.11.4.orig.tar.gz]
I: copying [/home/bas/tmp/debian/python-hdf4_0.11.4-1.1.debian.tar.xz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package 
(python-hdf4_0.11.4-1.1.dsc)
dpkg-source: info: extracting python-hdf4 in python-hdf4-0.11.4
dpkg-source: info: unpacking python-hdf4_0.11.4.orig.tar.gz
dpkg-source: info: unpacking python-hdf4_0.11.4-1.1.debian.tar.xz
I: Not using root during the build.
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper-compat (= 13), dh-python, dh-sequence-numpy3, 
dh-sequence-python3, libhdf4-alt-dev, libjpeg-dev, pybuild-plugin-pyproject, 
python3-all-dev, python3-pytest, python3-numpy, python3-setuptools, zlib1g-dev
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.