Bug#1064718: marked as done (pyfltk: FTBFS: ./fltk/fltk_wrap.cpp:5033:21: error: ‘SWIG_Python_str_AsChar’ was not declared in this scope; did you mean ‘SWIG_Python_str_FromChar’?)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2024 03:51:46 +
with message-id 
and subject line Bug#1064718: fixed in pyfltk 1.3.9+repack-2
has caused the Debian Bug report #1064718,
regarding pyfltk: FTBFS: ./fltk/fltk_wrap.cpp:5033:21: error: 
‘SWIG_Python_str_AsChar’ was not declared in this scope; did you mean 
‘SWIG_Python_str_FromChar’?
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.)


-- 
1064718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyfltk
Version: 1.3.9+repack-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 setup.py swig
> /usr/include/FL/x.H:118: Warning 503: Can't wrap 'operator XFontStruct*' 
> unless renamed to a valid identifier.
> Building for Linux
> ['./src', './contrib', '/usr/include']
> Checking FLTK configuration ... 
> Checking fltk-config using FLTK_HOME
> Checking fltk-config using default installation
> Using FLTK:  ['1.3.8\n']
> fltk-config includes:  ['/usr/include/cairo', '/usr/include/libpng16', 
> '/usr/include/freetype2', '/usr/include/pixman-1', '/usr/include/freetype2', 
> '/usr/include/libpng16', '/usr/include/cairo', '/usr/include/libpng16', 
> '/usr/include/freetype2', '/usr/include/pixman-1']
> fltk-config link paths:  []
> fltk-config link libraries:  ['fltk_images', 'fltk_gl', 'fltk_forms', 'fltk', 
> 'X11']
> FLTK was configured without multi-threading support!
> FLTK was configured with OpenGL support!
> FLTK was configured with Forms support!
> done
> Using default location for FLTK!
> dh_auto_build
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> ./fltk/fltk_wrap.cpp: In function ‘int 
> Fl_File_Browser_load_new(Fl_File_Browser*, PyObject*, PyObject*)’:
> ./fltk/fltk_wrap.cpp:5033:21: error: ‘SWIG_Python_str_AsChar’ was not 
> declared in this scope; did you mean ‘SWIG_Python_str_FromChar’?
>  5033 | char *directory=SWIG_Python_str_AsChar(dObj);
>   | ^~
>   | SWIG_Python_str_FromChar
> ./fltk/fltk_wrap.cpp: In function ‘int Fl_Menu__add__SWIG_2(Fl_Menu_*, 
> PyObject*, PyObject*, PyObject*, PyObject*, PyObject*)’:
> ./fltk/fltk_wrap.cpp:6094:33: error: ‘SWIG_Python_str_AsChar’ was not 
> declared in this scope; did you mean ‘SWIG_Python_str_FromChar’?
>  6094 | char* pyLabel = SWIG_Python_str_AsChar(lObj);
>   | ^~
>   | SWIG_Python_str_FromChar
> ./fltk/fltk_wrap.cpp: In function ‘void Fl_Window_show(Fl_Window*, PyObject*, 
> PyObject*)’:
> ./fltk/fltk_wrap.cpp:6246:20: error: ‘SWIG_Python_str_AsChar’ was not 
> declared in this scope; did you mean ‘SWIG_Python_str_FromChar’?
>  6246 |   tmp[i] = SWIG_Python_str_AsChar(PyList_GetItem(count,i));
>   |^~
>   |SWIG_Python_str_FromChar
> ./fltk/fltk_wrap.cpp:6271:20: error: ‘SWIG_Python_str_AsChar’ was not 
> declared in this scope; did you mean ‘SWIG_Python_str_FromChar’?
>  6271 |   tmp[i] = SWIG_Python_str_AsChar(PyList_GetItem(data,i));
>   |^~
>   |SWIG_Python_str_FromChar
> ./fltk/fltk_wrap.cpp: In function ‘void 
> Fl_Double_Window_show(Fl_Double_Window*, PyObject*, PyObject*)’:
> ./fltk/fltk_wrap.cpp:6314:20: error: ‘SWIG_Python_str_AsChar’ was not 
> declared in this scope; did you mean ‘SWIG_Python_str_FromChar’?
>  6314 |   tmp[i] = SWIG_Python_str_AsChar(PyList_GetItem(count,i));
>   |^~
>   |SWIG_Python_str_FromChar
> ./fltk/fltk_wrap.cpp:6339:20: error: ‘SWIG_Python_str_AsChar’ was not 
> declared in this scope; did you mean ‘SWIG_Python_str_FromChar’?
>  6339 |   tmp[i] = SWIG_Python_str_AsChar(PyList_GetItem(data,i));
>   |^~
>   |SWIG_Python_str_FromChar
> ./fltk/fltk_wrap.cpp: In function ‘void Fl_Gl_Window_show(Fl_Gl_Window*, 
> PyObject*, PyObject*)’:
> ./fltk/fltk_wrap.cpp:6473:20: error: ‘SWIG_Python_str_AsChar’ was not 
> declared in this scope; did you mean ‘SWIG_Python_str_FromChar’?
>  6473 |   tmp[i] = SWIG_Python_str_AsChar(PyList_GetItem(count,i));
>   |

Bug#1066118: marked as done (telegram-desktop: does not start under Debian sid)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2024 01:31:08 +
with message-id 
and subject line Re: Bug#1066118: telegram-desktop: does not start under Debian 
sid
has caused the Debian Bug report #1066118,
regarding telegram-desktop: does not start under Debian sid
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.)


-- 
1066118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: telegram-desktop
Version: 4.14.9+ds-1+b1
Severity: grave
Justification: renders package unusable

It depends on a symbol not present in the current libqt5quick5 
(automatically rebuilt as part of the time_t migration).

$ telegram-desktop
telegram-desktop: symbol lookup error: /lib/x86_64-linux-gnu/libQt5Quick.so.5: 
undefined symbol: 
_ZN18QTextureGlyphCache8populateEP11QFontEngineiPKjPK11QFixedPoint, version 
Qt_5_PRIVATE_API

-- Package-specific info:

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

Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages telegram-desktop depends on:
ii  libabsl20220623t64   20220623.1-3.1
ii  libavcodec60 7:6.1.1-2
ii  libavfilter9 7:6.1.1-2
ii  libavformat607:6.1.1-2
ii  libavutil58  7:6.1.1-2
ii  libc62.37-15.1
ii  libgcc-s114-20240303-1
ii  libglib2.0-0t64  2.78.4-4
ii  libglibmm-2.68-1t64  2.78.1-2.2
ii  libhunspell-1.7-01.7.2+really1.7.2-10+b1
ii  libjpeg62-turbo  1:2.1.5-2+b2
ii  libkf5coreaddons55.107.0-1+b1
ii  liblz4-1 1.9.4-1+b2
ii  libminizip1t64   1:1.3.dfsg-3.1
ii  libopenal1   1:1.23.1-4+b1
ii  libopus0 1.4-1+b1
ii  libqrcodegencpp1 1.8.0-1.2+b1
ii  libqt5core5t64 [qtbase-abi-5-15-10]  5.15.10+dfsg-7.2+b1
ii  libqt5gui5t645.15.10+dfsg-7.2+b1
ii  libqt5network5t645.15.10+dfsg-7.2+b1
ii  libqt5qml5   5.15.10+dfsg-2+b1
ii  libqt5quick5 5.15.10+dfsg-2+b1
ii  libqt5quickwidgets5  5.15.10+dfsg-2+b1
ii  libqt5svg5   5.15.10-2+b1
ii  libqt5waylandcompositor5 5.15.10-2+b2
ii  libqt5widgets5t645.15.10+dfsg-7.2+b1
ii  librlottie0-10.1+dfsg-4+b2
ii  libsigc++-3.0-0  3.6.0-1
ii  libsrtp2-1   2.5.0-3
ii  libssl3t64   3.1.5-1.1
ii  libstdc++6   14-20240303-1
ii  libswresample4   7:6.1.1-2
ii  libswscale7  7:6.1.1-2
ii  libvpx8  1.13.1-2
ii  libx11-6 2:1.8.7-1
ii  libxcb-keysyms1  0.4.0-1+b2
ii  libxcb-record0   1.15-1
ii  libxcb-screensaver0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  libxxhash0   0.8.2-2+b1
ii  libyuv0  0.0~git202401110.af6ac82-1
ii  qt5-image-formats-plugins5.15.10-2+b1
ii  zlib1g   1:1.3.dfsg-3.1

Versions of packages telegram-desktop recommends:
ii  fonts-open-sans   1.11-2
ii  libwebkit2gtk-4.0-37  2.42.5-1+b2
ii  libwebkit2gtk-4.1-0   2.42.5-1+b2

telegram-desktop suggests no packages.

Versions of packages telegram-desktop is related to:
ii  xdg-desktop-portal   1.18.2-1
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]  1.15.1-1

-- no debconf information
[2024.03.08 13:09:47] Launched version: 4015001, 

Bug#1067054: Debian 12 - Copy files on USB 3

[pham...@bluewin.ch]

For complement of information :
The SSD used is a Samsung 850 Pro 256 GB and the case is a Satechi ST-TCDEM. 
Write rates were high at the start of the copy (450 MB/sec then dropped before 
the crash to +/- 30 Mb/sec).
 
 
 Restoring the disk image with this same SSD but integrated in a Delock USB 3 
Type A case to a USB A socket on my computer works correctly with a transfer 
rate of 60 to 90 MB/s.
 
 
The same SSD still plugged into the Delock USB 3 Type A box but connected to my 
machine on a USB C port completes the restoration of the image with a constant 
transfer rate of +/- 41MB/sec.
Regards.
 
 
 

Bug#1052805: marked as done (hyperkitty: FTBFS: unsatisfiable build-dependencies: python3-django (< 3:4.2), python3-django-mailman3 (>= 1.3.8))

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2024 00:35:10 +
with message-id 
and subject line Bug#1052805: fixed in hyperkitty 1.3.9-1
has caused the Debian Bug report #1052805,
regarding hyperkitty: FTBFS: unsatisfiable build-dependencies: python3-django 
(< 3:4.2), python3-django-mailman3 (>= 1.3.8)
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.)


-- 
1052805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hyperkitty
Version: 1.3.7-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-python, python3-all, 
> python3-bs4, python3-django (>= 2:3.2), python3-django (<< 3:4.2), 
> python3-django-compressor, python3-django-extensions, 
> python3-django-gravatar2, python3-django-haystack, python3-django-mailman3 
> (>= 1.3.8), python3-django-q, python3-djangorestframework, 
> python3-elasticsearch, python3-flufl.lock, python3-isort, python3-lxml, 
> python3-mailmanclient, python3-mistune (>= 2.0.0), python3-mock, 
> python3-networkx, python3-robot-detection, python3-setuptools, python3-tz, 
> python3-whoosh, python3-sphinx, sassc, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-python, python3-all, 
> python3-bs4, python3-django (>= 2:3.2), python3-django (<< 3:4.2), 
> python3-django-compressor, python3-django-extensions, 
> python3-django-gravatar2, python3-django-haystack, python3-django-mailman3 
> (>= 1.3.8), python3-django-q, python3-djangorestframework, 
> python3-elasticsearch, python3-flufl.lock, python3-isort, python3-lxml, 
> python3-mailmanclient, python3-mistune (>= 2.0.0), python3-mock, 
> python3-networkx, python3-robot-detection, python3-setuptools, python3-tz, 
> python3-whoosh, python3-sphinx, sassc, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1147 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1180 B]
> Fetched 2942 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: python3-django (< 3:4.2) but 
> 3:4.2.5-2 is to be installed
>Depends: python3-django-mailman3 (>= 
> 1.3.8) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/hyperkitty_1.3.7-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=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: hyperkitty
Source-Version: 1.3.9-1
Done: Pierre-Elliott Bécue 

We believe that the bug you reported is 

Processed: Bug#1052805 marked as pending in hyperkitty

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1052805 [src:hyperkitty] hyperkitty: FTBFS: unsatisfiable 
build-dependencies: python3-django (< 3:4.2), python3-django-mailman3 (>= 1.3.8)
Added tag(s) pending.

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

Bug#1052805: marked as pending in hyperkitty

[Pierre-Elliott Bécue]

Control: tag -1 pending

Hello,

Bug #1052805 in hyperkitty 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/mailman-team/hyperkitty/-/commit/79ee1ebdd7c3a0465fbda5c45082b29df28765f4


New upstream release 1.3.9

Update (Build-)Dependencies
Closes: #1052805


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052805

Processed: retitle 1060953 to ibus-anthy: FTBFS: can't resolve libraries to shared libraries: anthy

[Debian Bug Tracking System]

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

> retitle 1060953 ibus-anthy: FTBFS: can't resolve libraries to shared 
> libraries: anthy
Bug #1060953 [src:ibus-anthy] ibus-anthy: FTBFS: make[3]: *** 
[/usr/share/gobject-introspection-1.0/Makefile.introspection:156: 
Anthy-9000.gir] Error 1
Changed Bug title to 'ibus-anthy: FTBFS: can't resolve libraries to shared 
libraries: anthy' from 'ibus-anthy: FTBFS: make[3]: *** 
[/usr/share/gobject-introspection-1.0/Makefile.introspection:156: 
Anthy-9000.gir] Error 1'.
> thanks
Stopping processing here.

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

Bug#1067077: frr: FTBFS on armel: /usr/bin/ld: ./build/../bgpd/bgp_io.c:476:(.text+0x51c): undefined reference to `__atomic_store_8'

[Sebastian Ramacher]

Source: frr
Version: 9.1-0.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=frr=armel=9.1-0.1=1710631814=0

libtool: link: gcc -fms-extensions -fno-omit-frame-pointer -funwind-tables 
-Wall -Wextra -Wformat-nonliteral -Wformat-security -Wswitch-enum 
-Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith 
-Wbad-function-cast -Wwrite-strings -Wundef -Wno-unused-result 
-Wno-unused-parameter -Wno-missing-field-initializers -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -g -o bgpd/.libs/bgpd 
bgpd/bgp_main.o yang/frr-bgp-types.yang.o yang/frr-bgp.yang.o 
yang/frr-bgp-common-structure.yang.o yang/frr-bgp-common.yang.o 
yang/frr-bgp-common-multiprotocol.yang.o yang/frr-bgp-neighbor.yang.o 
yang/frr-bgp-peer-group.yang.o yang/frr-bgp-bmp.yang.o yang/frr-bgp-rpki.yang.o 
yang/frr-deviations-bgp-datacenter.yang.o yang/frr-bgp-filter.yang.o 
yang/frr-bgp-route-map.yang.o -Wl,--export-dynamic  bgpd/libbgp.a 
bgpd/rfp-example/librfp/librfp.a lib/.libs/libfrr.so -lyang -lcap -lm -ljson-c 
-lrt -Wl,-rpath -Wl,/usr/lib/arm-linux-gnueabi/frr
/usr/bin/ld: /usr/bin/ld: bgpd/libbgp.a(bgp_vty.o): in function `bgp_show_peer':
./build/../bgpd/bgp_vty.c:13678:(.text+0x1d934): undefined reference to 
`__atomic_load_8'
/usr/bin/ld: ./build/../bgpd/bgp_vty.c:13686:(.text+0x1d9bc): undefined 
reference to `__atomic_load_8'
/usr/bin/ld: ./build/../bgpd/bgp_vty.c:13778:(.text+0x1ed90): undefined 
reference to `__atomic_load_8'
bgpd/libbgp.a(bgp_vty.o): in function `bgp_show_peer':
./build/../bgpd/bgp_vty.c:13678:(.text+0x1d934): undefined reference to 
`__atomic_load_8'
/usr/bin/ld: ./build/../bgpd/bgp_vty.c:13686:(.text+0x1d9bc): undefined 
reference to `__atomic_load_8'
/usr/bin/ld: ./build/../bgpd/bgp_vty.c:13778:(.text+0x1ed90): undefined 
reference to `__atomic_load_8'
/usr/bin/ld: bgpd/libbgp.a(bgp_packet.o): in function `bgp_update_receive':
./build/../bgpd/bgp_packet.c:2328:(.text+0x5fac): undefined reference to 
`__atomic_store_8'
/usr/bin/ld: bgpd/libbgp.a(bgp_fsm.o): in function `bgp_stop':
./build/../bgpd/bgp_fsm.c:1549:(.text+0x7dc): undefined reference to 
`__atomic_store_8'
/usr/bin/ld: bgpd/libbgp.a(bgp_fsm.o): in function `bgp_adjust_routeadv':
./build/../bgpd/bgp_fsm.c:984:(.text+0x3700): undefined reference to 
`__atomic_load_8'
/usr/bin/ld: bgpd/libbgp.a(bgp_io.o): in function `bgp_write':
./build/../bgpd/bgp_io.c:471:(.text+0x3e8): undefined reference to 
`__atomic_store_8'
/usr/bin/ld: ./build/../bgpd/bgp_io.c:471:(.text+0x4f4): undefined reference to 
`__atomic_store_8'
/usr/bin/ld: ./build/../bgpd/bgp_io.c:476:(.text+0x51c): undefined reference to 
`__atomic_store_8'
/usr/bin/ld: bgpd/libbgp.a(bgp_packet.o): in function `bgp_update_receive':
./build/../bgpd/bgp_packet.c:2328:(.text+0x5fac): undefined reference to 
`__atomic_store_8'
/usr/bin/ld: bgpd/libbgp.a(bgp_fsm.o): in function `bgp_stop':
./build/../bgpd/bgp_fsm.c:1549:(.text+0x7dc): undefined reference to 
`__atomic_store_8'
/usr/bin/ld: bgpd/libbgp.a(bgp_fsm.o): in function `bgp_adjust_routeadv':
./build/../bgpd/bgp_fsm.c:984:(.text+0x3700): undefined reference to 
`__atomic_load_8'
/usr/bin/ld: bgpd/libbgp.a(bgp_io.o): in function `bgp_write':
./build/../bgpd/bgp_io.c:471:(.text+0x3e8): undefined reference to 
`__atomic_store_8'
/usr/bin/ld: ./build/../bgpd/bgp_io.c:471:(.text+0x4f4): undefined reference to 
`__atomic_store_8'
/usr/bin/ld: ./build/../bgpd/bgp_io.c:476:(.text+0x51c): undefined reference to 
`__atomic_store_8'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:8013: bgpd/bgp_btoa] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1067076: x11vnc: FTBFS on arm{el,hf}: uinput.c:723:25: error: ‘struct input_event’ has no member named ‘time’

[Sebastian Ramacher]

Source: x11vnc
Version: 0.9.16-9
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=x11vnc=armhf=0.9.16-9%2Bb1=1710639780=0

gcc -DHAVE_CONFIG_H -I. -I..   -D_REENTRANT  -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -c -o x11vnc-user.o `test -f 'user.c' || echo 
'./'`user.c
uinput.c: In function ‘ptr_move’:
uinput.c:723:25: error: ‘struct input_event’ has no member named ‘time’
  723 | gettimeofday(, NULL);
  | ^
uinput.c: In function ‘ptr_abs’:
uinput.c:776:25: error: ‘struct input_event’ has no member named ‘time’
  776 | gettimeofday(, NULL);
  | ^
uinput.c: In function ‘button_click’:
uinput.c:962:25: error: ‘struct input_event’ has no member named ‘time’
  962 | gettimeofday(, NULL);
  | ^
uinput.c: In function ‘uinput_key_command’:
uinput.c:1256:25: error: ‘struct input_event’ has no member named ‘time’
 1256 | gettimeofday(, NULL);
  | ^

Cheers
-- 
Sebastian Ramacher

Bug#1067075: openvas-scanner: FTBFS on arm{el,hf}: /<>/src/attack.c:1617:16: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘__time64_t’ {aka ‘long long

[Sebastian Ramacher]

Source: openvas-scanner
Version: 22.7.9-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=openvas-scanner=armhf=22.7.9-1%2Bb1=1710667919=0

[ 89%] Building C object src/CMakeFiles/openvas.dir/pluginload.c.o
cd /<>/obj-arm-linux-gnueabihf/src && /usr/bin/cc 
-DNVT_TIMEOUT=320 -DOPENVAS_CONF=\"/etc/openvas/openvas.conf\" 
-DOPENVAS_DATA_DIR=\"/usr/share/openvas\" 
-DOPENVAS_FEED_LOCK_PATH=\"/var/lib/openvas/feed-update.lock\" 
-DOPENVAS_NVT_DIR=\"/var/lib/openvas/plugins\" -DOPENVAS_RUN_DIR=\"/run/ospd\" 
-DOPENVAS_STATE_DIR=\"/var/lib/openvas\" -DOPENVAS_SYSCONF_DIR=\"/etc/openvas\" 
-DOPENVAS_VERSION=\"22.7.9\" -DPREFIX=\"/usr\" -DSCANNER_NVT_TIMEOUT=36000 
-DSYSCONFDIR=\"/etc\" -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/gvm -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 
-DLARGEFILE_SOURCE=1 -std=c11   
  -Wall -Wextra 
-Werror -Wpedantic  
   -Wmissing-prototypes -Wshadow
 -Wsequence-point 
-D_BSD_SOURCE -D_ISOC11_SOURCE  
   -D_SVID_SOURCE -D_DEFAULT_SOURCE 
-O3 -DNDEBUG -Wformat -Wformat-security -D_FORTIFY_SOURCE=2 -fstack-protector 
-MD -MT src/CMakeFiles/openvas.dir/pluginload.c.o -MF 
CMakeFiles/openvas.dir/pluginload.c.o.d -o 
CMakeFiles/openvas.dir/pluginload.c.o -c /<>/src/pluginload.c
In file included from /usr/include/glib-2.0/glib.h:64,
 from /<>/src/../misc/scanneraux.h:14,
 from /<>/src/attack.h:16,
 from /<>/src/attack.c:13:
/<>/src/attack.c: In function ‘attack_network’:
/<>/src/attack.c:1617:16: error: format ‘%ld’ expects argument of 
type ‘long int’, but argument 5 has type ‘__time64_t’ {aka ‘long long int’} 
[-Werror=format=]
 1617 | g_message ("Vulnerability scan %s finished in %ld seconds: "
  |^
 1618 |"%d alive hosts of %d",
 1619 |globals->scan_id, now.tv_sec - then.tv_sec,
  |  
  | |
  | __time64_t {aka long long 
int}
/usr/include/glib-2.0/glib/gmessages.h:350:32: note: in definition of macro 
‘g_message’
  350 |__VA_ARGS__)
  |^~~
/<>/src/attack.c:1617:53: note: format string is defined here
 1617 | g_message ("Vulnerability scan %s finished in %ld seconds: "
  |   ~~^
  | |
  | long int
  |   %lld
/<>/src/attack.c:1622:16: error: format ‘%ld’ expects argument of 
type ‘long int’, but argument 5 has type ‘__time64_t’ {aka ‘long long int’} 
[-Werror=format=]
 1622 | g_message ("Vulnerability scan %s finished in %ld seconds: %d 
hosts",
  |^
 1623 |globals->scan_id, now.tv_sec - then.tv_sec,
  |  
  | |
  | __time64_t {aka long long 
int}
/usr/include/glib-2.0/glib/gmessages.h:350:32: note: in definition of macro 
‘g_message’
  350 |__VA_ARGS__)
  |^~~
/<>/src/attack.c:1622:53: note: format string is defined here
 1622 | g_message ("Vulnerability scan %s finished in %ld seconds: %d 
hosts",
  |   ~~^
  | |
  | long int
  |   %lld

Cheers
-- 
Sebastian Ramacher

Bug#1067074: liblog4ada: FTBFS on arm{el,hf}: gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed

[Sebastian Ramacher]

Source: liblog4ada
Version: 1.3.1.b6dafb49-13
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=liblog4ada=armhf=1.3.1.b6dafb49-13=1710696951=0

/usr/bin/gcc-13 -c -x ada -gnatA -gnat12 -gnati1 -gnatf -gnatyM122 -gnatwa 
-gnatwe -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -gno-record-gcc-switches -fPIC 
-gnatec=/tmp/GPR.1869/GNAT-TEMP-03.TMP 
-gnatem=/tmp/GPR.1869/GNAT-TEMP-04.TMP 
/<>/client/src/log4ada.ads
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed

make[1]: *** [debian/rules:35: override_dh_auto_build-arch] Error 7

Cheers
-- 
Sebastian Ramacher

Bug#1067073: libncursesada: FTBFS on arm{el,hf}: gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed

[Sebastian Ramacher]

Source: libncursesada
Version: 6.3.20211021-11
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=libncursesada=armel=6.3.20211021-11=1710701629=0

/usr/bin/gcc-13 -c -x ada -gnatA -gnataEfnoQq -gnatVa -gnatwa.eH.Y -Wall 
-Wextra -gnatyyM80 -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -gno-record-gcc-switches 
-gnatec=/tmp/GPR.16132/GNAT-TEMP-03.TMP 
-gnatem=/tmp/GPR.16132/GNAT-TEMP-04.TMP 
/<>/src/terminal_interface-curses-trace.adb
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
terminal_interface-curses.ads:460:30: warning: memory layout out of order 
[-gnatw_r]
terminal_interface-curses.ads:490:10: warning: component clause out of order 
with respect to declaration [-gnatw_r]
terminal_interface-curses.ads:499:16: warning: component clause out of order 
with respect to declaration [-gnatw_r]
gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed

Cheers
-- 
Sebastian Ramacher

Bug#1067072: libflorist: FTBFS on arm{el,hf}: posix-c.ads:876:07: error: size for "suseconds_t" too small, minimum allowed is 64

[Sebastian Ramacher]

Source: libflorist
Version: 2022.0.1~20220616-5
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=libflorist=armhf=2022.0.1%7E20220616-5=1710701527=0

gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
/usr/bin/gcc-13 -c -x ada -gnatA -O2 -gnatp -gnat95 -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -gno-record-gcc-switches 
-gnatVa -gnatafno -fPIC -gnatec=/tmp/GPR.1718/GNAT-TEMP-03.TMP 
-gnatem=/tmp/GPR.1718/GNAT-TEMP-05.TMP 
/<>/libsrc/threads/posix-message_queues.adb
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
posix-c.ads:876:07: error: size for "suseconds_t" too small, minimum allowed is 
64
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
posix-c.ads:876:07: error: size for "suseconds_t" too small, minimum allowed is 
64
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
posix-c.ads:876:07: error: size for "suseconds_t" too small, minimum allowed is 
64
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
posix-c.ads:876:07: error: size for "suseconds_t" too small, minimum allowed is 
64

   compilation of posix-message_queues.adb failed
   compilation of posix-condition_variables.adb failed
   compilation of posix-asynchronous_io.adb failed
   compilation of posix-timers-extensions.adb failed

gprbuild: *** compilation phase failed

Cheers
-- 
Sebastian Ramacher

Bug#1067071: lubaunit: FTBFS on arm{el,hf}: gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed

[Sebastian Ramacher]

Source: libaunit
Version: 24.0.0-2
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=libaunit=armel=24.0.0-2=1710701210=0

/usr/bin/gcc-13 -c -x ada -gnatA -O2 -gnatp -gnatn -gnatwa.X -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -gno-record-gcc-switches 
-gnatfno -gnatwa -gnatVa -fno-strict-aliasing -fPIC 
-gnatec=/tmp/GPR.3085/GNAT-TEMP-03.TMP 
-gnatem=/tmp/GPR.3085/GNAT-TEMP-06.TMP 
/<>/include/aunit/framework/aunit.adb
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed

Cheers
-- 
Sebastian Ramacher

Bug#1067070: adacgi: FTBFS on arm{el,hf}: gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed

[Sebastian Ramacher]

Source: adacgi
Version: 1.6-34
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=adacgi=armel=1.6-34=1710700906=0

/usr/bin/gcc-13 -c -x ada -gnatA -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -gno-record-gcc-switches 
-gnatec=/tmp/GPR.27197/GNAT-TEMP-03.TMP 
-gnatem=/tmp/GPR.27197/GNAT-TEMP-05.TMP /<>/cgi.adb
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gnat1: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
not valid for Ada
gprbuild: raised CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed

make[1]: *** [debian/rules:28: override_dh_auto_build] Error 7

Cheers
-- 
Sebastian Ramacher

Processed: severity of 1055352 is serious, cloning 1055352, retitle -1 to ruby3.2: bootstrapping issue ...

[Debian Bug Tracking System]

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

> # blocker for time_t transition
> severity 1055352 serious
Bug #1055352 [ruby3.1] ruby3.1: circular dependency between libruby3.1 and 
ruby-sdbm
Severity set to 'serious' from 'important'
> clone 1055352 -1
Bug #1055352 [ruby3.1] ruby3.1: circular dependency between libruby3.1 and 
ruby-sdbm
Bug 1055352 cloned as bug 1067069
1036884 was blocked by: 1066049 1055352 1065787 1065816
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1067069
> retitle -1 ruby3.2: bootstrapping issue
Bug #1067069 [ruby3.1] ruby3.1: circular dependency between libruby3.1 and 
ruby-sdbm
Changed Bug title to 'ruby3.2: bootstrapping issue' from 'ruby3.1: circular 
dependency between libruby3.1 and ruby-sdbm'.
> reassign -1 src:ruby3.2 3.2.3-1
Bug #1067069 [ruby3.1] ruby3.2: bootstrapping issue
Bug reassigned from package 'ruby3.1' to 'src:ruby3.2'.
No longer marked as found in versions ruby3.1/3.1.2-7.
Ignoring request to alter fixed versions of bug #1067069 to the same values 
previously set
Bug #1067069 [src:ruby3.2] ruby3.2: bootstrapping issue
Marked as found in versions ruby3.2/3.2.3-1.
> thanks
Stopping processing here.

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

Bug#1052901: closing 1052901

[Sebastian Ramacher]

close 1052901 3.1.2-8.3
thanks

Processed: closing 1052901

[Debian Bug Tracking System]

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

> close 1052901 3.1.2-8.3
Bug #1052901 [src:ruby3.1] ruby3.1: FTBFS: Errno::EADDRINUSE: Address already 
in use - listen(2)
Marked as fixed in versions ruby3.1/3.1.2-8.3.
Bug #1052901 [src:ruby3.1] ruby3.1: FTBFS: Errno::EADDRINUSE: Address already 
in use - listen(2)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1066350: marked as done (gcc-mingw-w64: FTBFS: enable-execute-stack.c:36:5: error: implicit declaration of function ‘abort’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 22:35:02 +
with message-id 
and subject line Bug#1066350: fixed in gcc-mingw-w64 26.2
has caused the Debian Bug report #1066350,
regarding gcc-mingw-w64: FTBFS: enable-execute-stack.c:36:5: error: implicit 
declaration of function ‘abort’ [-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.)


-- 
1066350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-mingw-w64
Version: 26.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):
> /<>/build/i686-w64-mingw32-posix/./gcc/xgcc 
> -B/<>/build/i686-w64-mingw32-posix/./gcc/ 
> -L/usr/i686-w64-mingw32/lib -L/usr/mingw/lib -isystem 
> /usr/i686-w64-mingw32/include -isystem /usr/mingw/include 
> -B/usr/i686-w64-mingw32/bin/ -B/usr/i686-w64-mingw32/lib/ -isystem 
> /usr/i686-w64-mingw32/include -isystem /usr/i686-w64-mingw32/sys-include 
> -isystem /<>/build/i686-w64-mingw32-posix/sys-include-g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -Wall -O2 
> -I../../../../src/libgcc/../winsup/w32api/include -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -Wall -DIN_GCC  
> -DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wno-narrowing -Wwrite-strings 
> -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  
> -isystem ./include   -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector   
> -I. -I. -I../.././gcc -I../../../../src/libgcc -I../../../../src/libgcc/. 
> -I../../../../src/libgcc/../gcc -I../../../../src/libgcc/../include 
> -I../../../../src/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT 
> -DHAVE_CC_TLS -DUSE_EMUTLS  -o _gcov_ior_profiler.o -MT _gcov_ior_profiler.o 
> -MD -MP -MF _gcov_ior_profiler.dep -DL_gcov_ior_profiler -c 
> ../../../../src/libgcc/libgcov-profiler.c
> enable-execute-stack.c: In function ‘__enable_execute_stack’:
> enable-execute-stack.c:36:5: error: implicit declaration of function ‘abort’ 
> [-Werror=implicit-function-declaration]
>36 | abort ();
>   | ^
> enable-execute-stack.c:27:1: note: include ‘’ or provide a 
> declaration of ‘abort’
>26 | #include 
>   +++ |+#include 
>27 | 
> enable-execute-stack.c:36:5: warning: incompatible implicit declaration of 
> built-in function ‘abort’ [-Wbuiltin-declaration-mismatch]
>36 | abort ();
>   | ^
> enable-execute-stack.c:36:5: note: include ‘’ or provide a 
> declaration of ‘abort’
> cc1: some warnings being treated as errors
> make[3]: *** [../../../../src/libgcc/shared-object.mk:14: 
> enable-execute-stack.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/gcc-mingw-w64_26.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: gcc-mingw-w64
Source-Version: 26.2
Done: Stephen Kitt 

We believe that the bug you reported is fixed in the latest version of
gcc-mingw-w64, 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.
Stephen Kitt  (supplier of updated 

Processed: tagging 1032485, severity of 1032485 is serious

[Debian Bug Tracking System]

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

> # 
> https://buildd.debian.org/status/fetch.php?pkg=ruby-fcgi=amd64=0.9.2.1-3%2Bb3=1710696058=0
> tags 1032485 + ftbfs sid trixie
Bug #1032485 [ruby-fcgi] ruby-fcgi: Incompatible version with ruby >3.0
Added tag(s) ftbfs, sid, and trixie.
> severity 1032485 serious
Bug #1032485 [ruby-fcgi] ruby-fcgi: Incompatible version with ruby >3.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1067067: ruby-rdiscount: FTBFS: rdiscount.c:50:17: error: implicit declaration of function ‘rb_rdiscount__get_flags’ [-Werror=implicit-function-declaration]

[Sebastian Ramacher]

Source: ruby-rdiscount
Version: 2.1.8-2
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=ruby-rdiscount=amd64=2.1.8-2%2Bb3=1710698993=0

gcc -fdebug-prefix-map=/<>=. -I. 
-I/usr/include/x86_64-linux-gnu/ruby-3.1.0 
-I/usr/include/ruby-3.1.0/ruby/backward -I/usr/include/ruby-3.1.0 -I. 
-DHAVE_RANDOM -DHAVE_SRANDOM -DHAVE_RAND -DHAVE_SRAND -DSIZEOF_UNSIGNED_LONG=8 
-DSIZEOF_UNSIGNED_INT=4 -DSIZEOF_UNSIGNED_INT=4 -DVERSION=\"2.1.8\" -Wdate-time 
-D_FORTIFY_SOURCE=2   -fPIC -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=BUILDDIR=. -fstack-protector-strong -fstack-clash-protection 
-Wformat -Werror=format-security -fcf-protection -fPIC  -o rdiscount.o -c 
rdiscount.c
rdiscount.c: In function ‘rb_rdiscount_to_html’:
rdiscount.c:50:17: error: implicit declaration of function 
‘rb_rdiscount__get_flags’ [-Werror=implicit-function-declaration]
   50 | int flags = rb_rdiscount__get_flags(self);
  | ^~~
cc1: some warnings being treated as errors
make[1]: *** [Makefile:246: rdiscount.o] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1067066: ruby-fusefs: fusefs_fuse.c:31:10: error: implicit declaration of function ‘fuse_chan_fd’ [-Werror=implicit-function-declaration]

[Sebastian Ramacher]

Source: ruby-fusefs
Version: 0.7.0-5
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=ruby-fusefs=amd64=0.7.0-5%2Bb3=1710696156=0

make[1]: Entering directory '/<>/ext'
gcc -fdebug-prefix-map=/<>=. -I. 
-I/usr/include/x86_64-linux-gnu/ruby-3.1.0 
-I/usr/include/ruby-3.1.0/ruby/backward -I/usr/include/ruby-3.1.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=BUILDDIR=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -fPIC  -o fusefs_fuse.o -c fusefs_fuse.c
fusefs_fuse.c: In function ‘fusefs_fd’:
fusefs_fuse.c:31:10: error: implicit declaration of function ‘fuse_chan_fd’ 
[-Werror=implicit-function-declaration]
   31 |   return fuse_chan_fd(fusech);
  |  ^~~~
fusefs_fuse.c: In function ‘fusefs_unmount’:
fusefs_fuse.c:41:5: warning: ignoring return value of ‘system’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
   41 | system(buf);
  | ^~~
cc1: some warnings being treated as errors
make[1]: *** [Makefile:246: fusefs_fuse.o] Error 1
make[1]: Leaving directory '/<>/ext'

Cheers
-- 
Sebastian Ramacher

Bug#1066237: marked as done (nas: FTBFS: main.c:125:9: error: implicit declaration of function ‘yyparse’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 22:09:41 +
with message-id 
and subject line Bug#1066237: fixed in nas 1.9.4-8
has caused the Debian Bug report #1066237,
regarding nas: FTBFS: main.c:125:9: error: implicit declaration of function 
‘yyparse’ [-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.)


-- 
1066237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nas
Version: 1.9.4-7
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 -c -g -O2 -fno-strict-aliasing -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
> -fcommon   -I. -I../include -I../../include -I../../lib/audio -I../../include 
>-Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L  
>   -D_POSIX_SOURCE -D_XOPEN_SOURCE 
> -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO   
> -DNASCONFSEARCHPATH=\"/etc/nas/\"   main.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from main.c:54:
> /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> main.c: In function ‘main’:
> main.c:125:9: error: implicit declaration of function ‘yyparse’ 
> [-Werror=implicit-function-declaration]
>   125 | yyparse();
>   | ^~~
> main.c:143:9: error: implicit declaration of function ‘osLogMsg’ 
> [-Werror=implicit-function-declaration]
>   143 | osLogMsg("%s\n", release);
>   | ^~~~
> main.c:147:9: error: implicit declaration of function ‘osBecomeOrphan’ 
> [-Werror=implicit-function-declaration]
>   147 | osBecomeOrphan();
>   | ^~
> main.c:148:9: error: implicit declaration of function ‘osBecomeDaemon’ 
> [-Werror=implicit-function-declaration]
>   148 | osBecomeDaemon();
>   | ^~
> main.c:156:5: error: implicit declaration of function ‘chdir’ 
> [-Werror=implicit-function-declaration]
>   156 | chdir("/");
>   | ^
> cc1: some warnings being treated as errors
> make[4]: *** [Makefile:1077: main.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/nas_1.9.4-7_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: nas
Source-Version: 1.9.4-8
Done: Steve McIntyre <93...@debian.org>

We believe that the bug you reported is fixed in the latest version of
nas, 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.
Steve McIntyre <93...@debian.org> (supplier of updated nas package)

(This message was 

Bug#1067063: Fix in experimental

[Thomas Goirand]

Hi,

OpenStack Carcal is about to be released, and the fix must be in the 
package in Experimental already.


Cheers,

Thomas Goirand (zigo)

Processed: Reducing severity to important

[Debian Bug Tracking System]

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

> severity 1062128 important
Bug #1062128 {Done: Steve Langasek } [src:gridsite] 
gridsite: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062887 important
Bug #1062887 {Done: Benjamin Drung } [src:scitokens-cpp] 
scitokens-cpp: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1062922 important
Bug #1062922 {Done: Benjamin Drung } [src:srm-ifce] 
srm-ifce: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1063054 important
Bug #1063054 {Done: Steve Langasek } [src:voms] voms: NMU 
diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1063156 important
Bug #1063156 {Done: Benjamin Drung } [src:myproxy] myproxy: 
NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1063204 important
Bug #1063204 {Done: Benjamin Drung } [src:nordugrid-arc] 
nordugrid-arc: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1063298 important
Bug #1063298 {Done: Steve Langasek } [src:xrootd] xrootd: 
NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1064079 important
Bug #1064079 {Done: Steve Langasek } [src:gsoap] gsoap: NMU 
diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> severity 1065771 important
Bug #1065771 {Done: Mattias Ellert } [src:dcap] 
dcap: FTBFS on arm{el,hf}: dcap.h:56:21: error: conflicting types for 
‘dc_readdir64’; have ‘struct dirent *(DIR *)’
Severity set to 'important' from 'serious'
> severity 1067015 important
Bug #1067015 {Done: Mattias Ellert } [src:xrootd] 
xrootd: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error 
"_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1062128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062128
1062887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062887
1062922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062922
1063054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063054
1063156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063156
1063204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063204
1063298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063298
1064079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064079
1065771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065771
1067015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1029451: marked as done (gnome-remote-desktop FTBFS with nocheck profile: missing gudev-1.0.pc)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 21:15:40 +
with message-id 
and subject line Bug#1029451: fixed in gnome-remote-desktop 45.1-3
has caused the Debian Bug report #1029451,
regarding gnome-remote-desktop FTBFS with nocheck profile: missing gudev-1.0.pc
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.)


-- 
1029451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-remote-desktop
Version: 43.3-1
Tags: ftbfs
Severity: important
Justification: will be rc after bookworm

gnome-remote-desktop fails to build from source in unstable when built
with the nocheck build profile, because it misses a dependency for
gudev-1.0.pc as shipped by libgudev-1.0-dev, which is erroneously tagged
. Please remove the annotation and ensure that building with
the nocheck build profile actually works.

Helmut
--- End Message ---
--- Begin Message ---
Source: gnome-remote-desktop
Source-Version: 45.1-3
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gnome-remote-desktop 
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: Sun, 17 Mar 2024 19:53:25 +
Source: gnome-remote-desktop
Architecture: source
Version: 45.1-3
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1029451
Changes:
 gnome-remote-desktop (45.1-3) experimental; urgency=medium
 .
   * Team upload
   * Merge packaging from unstable
 - Stop marking libgudev-1.0-dev as .
   It is needed at build-time, even when not intending to run the
   test suite. (Closes: #1029451)
Checksums-Sha1:
 4f29d4edc5b9f4a8a8c8a51547f72bbf304b3fa1 2852 gnome-remote-desktop_45.1-3.dsc
 84a94172c53386a8eea7da65460a6845caf81d7e 6980 
gnome-remote-desktop_45.1-3.debian.tar.xz
 851aa43b54fef85cdd6570faf74a57a7caf99f55 18739 
gnome-remote-desktop_45.1-3_source.buildinfo
Checksums-Sha256:
 c0c08db32200caacf346f1e44da55e1fb1d61f44d69ea895cac5ef062180 2852 
gnome-remote-desktop_45.1-3.dsc
 1b1626c3e6a00afa5effdcf88693eabf5c7c9ae196bb827a14ca74fc017d6e53 6980 
gnome-remote-desktop_45.1-3.debian.tar.xz
 cb8d680440a4bc4790fa46a8367d12339e3f6e812f8625235b1abcd85c3da28e 18739 
gnome-remote-desktop_45.1-3_source.buildinfo
Files:
 50ab8b919b05a8e25faf387dd41716d0 2852 gnome optional 
gnome-remote-desktop_45.1-3.dsc
 ba163168ad895bb8e013fabde1c7bc45 6980 gnome optional 
gnome-remote-desktop_45.1-3.debian.tar.xz
 31f7014524481addb68808195d8a0ef7 18739 gnome optional 
gnome-remote-desktop_45.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmX3UFkACgkQ4FrhR4+B
TE8srA//VgXCTeu7l11nHoZg/xC2eQTo/MLo88DXNK1//otr2YUCcdRiR/g4t0Wq
VUMHgmMcYVANdnBUIGEgfL6d5WNI/h58B2xUCyBZgV+GD+xz4o2+Q2isBOa+qHlQ
aqV1q+IzJ5MQ462WhSmQ/fHnNt1zMpgujKyHDQBWAla+pSKrEYutU/o4funPiJ+2
qxTTLTZbUI6TMIhy7R0bTV7zLdZEqJiwgAvY1IQh8aUWHLxvFwrywdRbwWqVV84A
ew6ZEwLZN/NQBN7IPCKVznH1HNBETCPI2PAmh+NzYcazMsf4ohAwof/5OkhmSvzG
OhRqBF45lt6wgmORqPxWu2qEFw18pI1GvBKlaB1gahjX9z9s45DEj8DVNgPSVvSk
hYAC/KNlvkkxzFmzYNkOfEk4okVLZ+M2ujEupr4kb0PGiYwrmIxLNiEtkjtpT66a
V+8/bXPWUYDw+scr2oIv3ImkokiExgkLV9A8yTzYrNchBTAidG86caq7nUVm1XLT
iVV3M9A5U9jLML/Tn2RR3UH9Bbb9RsTYR+0RQuerm2LxRQee5Zy7vQrOKk2AM9Om
17/woO1zXDST/Y4ggsAM6QkbrnToBdHopnZCCc6xtI39h5Yj+KDoVG13mypiVigw
NPoVF7nrl/UoxLyARI2N4Y9YS/Y3IkzutmPxmAaDkidJJzwfihs=
=jaj+
-END PGP SIGNATURE-



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

Bug#1029451: marked as done (gnome-remote-desktop FTBFS with nocheck profile: missing gudev-1.0.pc)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 21:15:29 +
with message-id 
and subject line Bug#1029451: fixed in gnome-remote-desktop 44.2-7
has caused the Debian Bug report #1029451,
regarding gnome-remote-desktop FTBFS with nocheck profile: missing gudev-1.0.pc
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.)


-- 
1029451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-remote-desktop
Version: 43.3-1
Tags: ftbfs
Severity: important
Justification: will be rc after bookworm

gnome-remote-desktop fails to build from source in unstable when built
with the nocheck build profile, because it misses a dependency for
gudev-1.0.pc as shipped by libgudev-1.0-dev, which is erroneously tagged
. Please remove the annotation and ensure that building with
the nocheck build profile actually works.

Helmut
--- End Message ---
--- Begin Message ---
Source: gnome-remote-desktop
Source-Version: 44.2-7
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gnome-remote-desktop 
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: Sun, 17 Mar 2024 17:53:17 +
Source: gnome-remote-desktop
Architecture: source
Version: 44.2-7
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1029451
Changes:
 gnome-remote-desktop (44.2-7) unstable; urgency=medium
 .
   * Team upload
   * d/gbp.conf: Use debian/trixie, upstream/44.x branches
   * Stop using debian/control.in and dh_gnome_clean
   * Stop marking libgudev-1.0-dev as .
 It is needed at build-time, even when not intending to run the
 test suite. (Closes: #1029451)
Checksums-Sha1:
 379d1ac4d042b7f750c3416862a759eb3a764877 2817 gnome-remote-desktop_44.2-7.dsc
 6309b0e974b74638d1628eb25bd8c832dba77d7c 6760 
gnome-remote-desktop_44.2-7.debian.tar.xz
 59ae70804e92fccca81ba598208a61516c88953a 18920 
gnome-remote-desktop_44.2-7_source.buildinfo
Checksums-Sha256:
 597b1ceaeb7092bff8cb937cddaba36186670f64dc759dad5ead25ed53e35130 2817 
gnome-remote-desktop_44.2-7.dsc
 574c3777841a8b7660197e417f39d5560857063ae81533b496338202f48dad4f 6760 
gnome-remote-desktop_44.2-7.debian.tar.xz
 44a8c4e127114a13628751525897676c336e370677816f093de44ba28799ccbe 18920 
gnome-remote-desktop_44.2-7_source.buildinfo
Files:
 797208d5efcdf463e3a7d182a9f7e62b 2817 gnome optional 
gnome-remote-desktop_44.2-7.dsc
 15b1b100f823ac7bd8cd8f0b272d77e1 6760 gnome optional 
gnome-remote-desktop_44.2-7.debian.tar.xz
 5ba300f90374fb4ce8193ac0b4606234 18920 gnome optional 
gnome-remote-desktop_44.2-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmX3Sa0ACgkQ4FrhR4+B
TE9ivg//eBBLM1bN4mRPDWiOCNGdc8gaLAa39yl+vENcrbYDr0D93ZI0DKe3BMlv
Q8c/V3tfe/jhpNynYfloYaQv5W8falI6liUJSmtdVGcoj8+Xw7aH8hVAWlQydYol
Tz2fZLfTUjSE51Y+wHQv0fq6qjBccydUSu6dZ8b+TjSRX1vwP1tlyS+gDe6iCpnw
XBcL+o/Sphpexrl0coVykvOKUCyWE7LWAz8DRmP96UsWKAfU0AE1AXQytG8cNeGI
BPx1/emQiVj2HXt5yntM2AKy4OzsimkDHjZNAJ5p/w5YoCwMllNYL5P5oTvPp8Hj
vWmvDfdASkJvcj2bMB5i3AgmDWL1sN0P384AGv/CxoYgG6ShPe5ojLMy1m67MLiZ
9VIKcWj5UAQH2CoEdF/7RjYwoRQul9BvCTn9xu1l/RyRd3UlPYm9dCAFAz+dlrFu
dZ8f6EkNbGijMKgWy1KWu2ZpRA83CWA17WkhQ6qzdtIftHfmUAdPUE1dK0whWLKh
mkwwy0fXLUR6Qdg2lbpfeeWZ9kEz16E2gR/6q/r32xZew7O9easR+F9XK4EWe4lw
HqKU5QaAB3qssL7Z4qeZIho6Xta/1StLdAKvYaEevHfMBKM6AhY3X8jOqxL56C55
IuuFPEWDbZmobtu0e5zP1brt/iRH+AHmG70ksUY+ksE1RGBtXMk=
=D/8k
-END PGP SIGNATURE-



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

Bug#1066726: marked as done (openlp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 21:58:09 +0100
with message-id <1ae0bd13-2df3-412b-b65d-e75ec1b95...@debian.org>
and subject line Re: openlp: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.11 returned exit code 13
has caused the Debian Bug report #1066726,
regarding openlp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.11 returned exit code 13
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.)


-- 
1066726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openlp
Version: 3.1.0~rc4-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[1]: Entering directory '/<>'
> QT_QPA_PLATFORM=offscreen dh_auto_test
> I: pybuild base:305: cd 
> '/<>/.pybuild/cpython3_3.11_openlp/build'; python3.11 -m pytest 
> -k 'not test_load_settings_position_invalid and not 
> test_get_directory_for_language_dir_from_source and not 
> test_get_ip_address_default'
> = test session starts 
> ==
> platform linux -- Python 3.11.8, pytest-8.0.2, pluggy-1.4.0
> PyQt5 5.15.10 -- Qt runtime 5.15.10 -- Qt compiled 5.15.10
> rootdir: /<>
> configfile: setup.cfg
> plugins: qt-4.3.1
> collected 2482 items / 3 deselected / 1 skipped / 2479 selected
> 
> tests/openlp_core/api/endpoint/test_controller.py    [  
> 0%]
> tests/openlp_core/api/http_server/test_http.py ..[  
> 0%]
> tests/openlp_core/api/http_server/test_init.py ...   [  
> 0%]
> tests/openlp_core/api/test_deploy.py ... [  
> 0%]
> tests/openlp_core/api/test_http.py ...   [  
> 1%]
> tests/openlp_core/api/test_main.py . [  
> 1%]
> tests/openlp_core/api/test_tab.py .  [  
> 1%]
> tests/openlp_core/api/test_websockets.py ... [  
> 2%]
> tests/openlp_core/api/v2/test_controller.py  [  
> 3%]
>  [  
> 4%]
> tests/openlp_core/api/v2/test_core.py .. [  
> 4%]
> tests/openlp_core/api/v2/test_plugins.py .   [  
> 5%]
> tests/openlp_core/api/v2/test_service.py [  
> 5%]
> tests/openlp_core/common/test_actions.py ..  [  
> 5%]
> tests/openlp_core/common/test_applocation.py [  
> 6%]
> tests/openlp_core/common/test_handlers.py .  [  
> 6%]
> tests/openlp_core/common/test_httputils.py ..[  
> 7%]
> tests/openlp_core/common/test_i18n.py    [  
> 7%]
> tests/openlp_core/common/test_init.py .. [  
> 8%]
> ..   [  
> 9%]
> tests/openlp_core/common/test_json.py .. [ 
> 10%]
> tests/openlp_core/common/test_mixins.py  [ 
> 10%]
> tests/openlp_core/common/test_network_interfaces.py ..   [ 
> 10%]
> tests/openlp_core/common/test_path.py .. [ 
> 11%]
> tests/openlp_core/common/test_platform.py .  [ 
> 11%]
> tests/openlp_core/common/test_registry.py .  [ 
> 12%]
> tests/openlp_core/common/test_settings.py ...[ 
> 13%]
> tests/openlp_core/common/test_utils.py ...   [ 
> 13%]
> tests/openlp_core/db/test_helpers.py [ 
> 13%]
> tests/openlp_core/db/test_manager.py ..  [ 
> 13%]
> tests/openlp_core/db/test_upgrades.py .. [ 
> 13%]
> tests/openlp_core/display/test_render.py ..  [ 
> 14%]
> tests/openlp_core/display/test_screens.py    [ 
> 15%]
> tests/openlp_core/display/test_window.py FFF [ 
> 16%]
> .[ 
> 16%]
> tests/openlp_core/lib/test_exceptions.py .   [ 
> 

Bug#1064726: 0ad: FTBFS: ImportError: cannot import name 'dist' from 'distutils' (/usr/lib/python3.11/distutils/__init__.py)

[David W. Kennedy]

Hi,

I found that adding Build-Depends: python3-distutils solves this 
problem.


The natural question is why did build of 0ad work in the past, but not 
now. I found that python3-distutils was being pulled in only as a side 
effect of one of the dependencies, libsdl2-dev. The build failure is 
caused by the fact that the Debian package of glib2.0 stopped depending 
on python3-distutils as of 23 Jan 2024.


Specifically, libsdl2-dev depends on libibus-1.0-dev, which depends on 
libglib2.0-dev, which depends on libglib2.0-dev-bin, which used to 
depend on python3-distutils, but now depends on python3-packaging. This 
change was made to libglib2.0-dev-bin in version 2.78.3-2 on 23 Jan 
2024.


I've committed the Build-Depends change to Debian Salsa.

Thanks.
--
David W. Kennedy

Bug#1066314: regina-rexx: FTBFS: ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did you mean ‘popcallstack’? [-Werror=implicit-function-declaration]

[Agustin Martin]

El vie, 15 mar 2024 a las 18:57, Agustin Martin
() escribió:
>
> Hi, Lucas and Alen.
>
> While it is easy to fix this particular error (see attached patch,
> from upstream repo), other similar error happens afterwards in my
> tests. The problem is that this package is way behind upstream and I
> think priority is to upgrade to a recent upstream version and then fix
> whatever is left.

Hi, Alen,

Some time ago I played a bit with upgrading regina-rexx to a recent
upstream version. I think I can find that stuff and try again with
last upstream version. In case of success, I would like to push
changes to regina-rexx salsa repo for further inspection. Let me know
your POV.

Regards,

-- 
Agustin

Processed: Bug#1064726 marked as pending in 0ad

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1064726 [src:0ad] 0ad: FTBFS: ImportError: cannot import name 'dist' from 
'distutils' (/usr/lib/python3.11/distutils/__init__.py)
Ignoring request to alter tags of bug #1064726 to the same tags previously set

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

Processed: Bug#1064726 marked as pending in 0ad

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1064726 [src:0ad] 0ad: FTBFS: ImportError: cannot import name 'dist' from 
'distutils' (/usr/lib/python3.11/distutils/__init__.py)
Added tag(s) pending.

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

Bug#1064726: marked as pending in 0ad

[David W. Kennedy]

Control: tag -1 pending

Hello,

Bug #1064726 in 0ad 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/games-team/0ad/-/commit/439aeb868f5ea45edc72954699faea61b0b6acff


Fix build failure due to missing distutils (Closes: #1064726)

Fix build failure of embedded mozjs library that displays message
"cannot import name 'dist' from 'distutils'." Cause: dependency
libsdl2-dev stopped indirectly depending on python3-distutils as of 23
Jan 2024. Therefore, add Build-Depends on python3-distutils.
Closes: #1064726


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064726

Bug#1064726: marked as pending in 0ad

[David W. Kennedy]

Control: tag -1 pending

Hello,

Bug #1064726 in 0ad 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/games-team/0ad/-/commit/439aeb868f5ea45edc72954699faea61b0b6acff


Fix build failure due to missing distutils (Closes: #1064726)

Fix build failure of embedded mozjs library that displays message
"cannot import name 'dist' from 'distutils'." Cause: dependency
libsdl2-dev stopped indirectly depending on python3-distutils as of 23
Jan 2024. Therefore, add Build-Depends on python3-distutils.
Closes: #1064726


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064726

Bug#1064671: marked as done (yuzu: FTBFS: vulkan_wrapper.cpp:285:12: error: enumeration value ‘VK_ERROR_INVALID_VIDEO_STD_PARAMETERS_KHR’ not handled in switch [-Werror=switch])

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 20:09:06 +
with message-id 
and subject line Bug#1064671: fixed in yuzu 0-1335+ds-1.4
has caused the Debian Bug report #1064671,
regarding yuzu: FTBFS: vulkan_wrapper.cpp:285:12: error: enumeration value 
‘VK_ERROR_INVALID_VIDEO_STD_PARAMETERS_KHR’ not handled in switch 
[-Werror=switch]
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.)


-- 
1064671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yuzu
Version: 0-1335+ds-1.3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src/video_core && /usr/bin/c++ 
> -DARCHITECTURE_x86_64=1 -DBOOST_ASIO_DISABLE_CONCEPTS 
> -DBOOST_CONTEXT_DYN_LINK -DBOOST_CONTEXT_NO_LIB -DBOOST_DATE_TIME_NO_LIB 
> -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_REGEX_NO_LIB -DBOOST_SYSTEM_NO_LIB 
> -DFMT_SHARED -DNDEBUG -DYUZU_UNIX=1 -D_FILE_OFFSET_BITS=64 
> -I/<>/src/. 
> -I/<>/obj-x86_64-linux-gnu/src/video_core/host_shaders/include 
> -I/<>/externals/./microprofile 
> -I/<>/externals/glad/include 
> -I/<>/externals/sirit/src/../include -g -Werror=clobbered 
> -Werror=volatile-register-var 
> -D__DEB_CANARY_CXXFLAGS_05a70454516ecd9194c293b0e415777f__ 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -march=x86-64-v2 -D__DEB_CANARY_CPPFLAGS_05a70454516ecd9194c293b0e415777f__ 
> -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -std=gnu++20 -flto=auto 
> -fno-fat-lto-objects -Werror=all -Werror=extra -Werror=missing-declarations 
> -Werror=shadow -Werror=unused -Wno-attributes -Wno-invalid-offsetof 
> -Wno-unused-parameter -mcx16 -fwrapv -Wno-array-bounds -Wno-stringop-overread 
> -Wno-stringop-overflow -Werror=conversion -Wno-sign-conversion -Winvalid-pch 
> -include 
> /<>/obj-x86_64-linux-gnu/src/video_core/CMakeFiles/video_core.dir/cmake_pch.hxx
>  -MD -MT 
> src/video_core/CMakeFiles/video_core.dir/vulkan_common/vulkan_wrapper.cpp.o 
> -MF CMakeFiles/video_core.dir/vulkan_common/vulkan_wrapper.cpp.o.d -o 
> CMakeFiles/video_core.dir/vulkan_common/vulkan_wrapper.cpp.o -c 
> /<>/src/video_core/vulkan_common/vulkan_wrapper.cpp
> /<>/src/video_core/vulkan_common/vulkan_wrapper.cpp: In function 
> ‘const char* Vulkan::vk::ToString(VkResult)’:
> /<>/src/video_core/vulkan_common/vulkan_wrapper.cpp:285:12: 
> error: enumeration value ‘VK_ERROR_INVALID_VIDEO_STD_PARAMETERS_KHR’ not 
> handled in switch [-Werror=switch]
>   285 | switch (result) {
>   |^
> [ 41%] Building CXX object 
> src/video_core/CMakeFiles/video_core.dir/vulkan_common/nsight_aftermath_tracker.cpp.o
> cd /<>/obj-x86_64-linux-gnu/src/video_core && /usr/bin/c++ 
> -DARCHITECTURE_x86_64=1 -DBOOST_ASIO_DISABLE_CONCEPTS 
> -DBOOST_CONTEXT_DYN_LINK -DBOOST_CONTEXT_NO_LIB -DBOOST_DATE_TIME_NO_LIB 
> -DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_REGEX_NO_LIB -DBOOST_SYSTEM_NO_LIB 
> -DFMT_SHARED -DNDEBUG -DYUZU_UNIX=1 -D_FILE_OFFSET_BITS=64 
> -I/<>/src/. 
> -I/<>/obj-x86_64-linux-gnu/src/video_core/host_shaders/include 
> -I/<>/externals/./microprofile 
> -I/<>/externals/glad/include 
> -I/<>/externals/sirit/src/../include -g -Werror=clobbered 
> -Werror=volatile-register-var 
> -D__DEB_CANARY_CXXFLAGS_05a70454516ecd9194c293b0e415777f__ 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -march=x86-64-v2 -D__DEB_CANARY_CPPFLAGS_05a70454516ecd9194c293b0e415777f__ 
> -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -std=gnu++20 -flto=auto 
> -fno-fat-lto-objects -Werror=all -Werror=extra -Werror=missing-declarations 
> -Werror=shadow -Werror=unused -Wno-attributes -Wno-invalid-offsetof 
> -Wno-unused-parameter -mcx16 -fwrapv -Wno-array-bounds -Wno-stringop-overread 
> -Wno-stringop-overflow -Werror=conversion -Wno-sign-conversion -Winvalid-pch 
> -include 
> /<>/obj-x86_64-linux-gnu/src/video_core/CMakeFiles/video_core.dir/cmake_pch.hxx
>  -MD -MT 
> src/video_core/CMakeFiles/video_core.dir/vulkan_common/nsight_aftermath_tracker.cpp.o
>  -MF CMakeFiles/video_core.dir/vulkan_common/nsight_aftermath_tracker.cpp.o.d 
> -o CMakeFiles/video_core.dir/vulkan_common/nsight_aftermath_tracker.cpp.o -c 
> /<>/src/video_core/vulkan_common/nsight_aftermath_tracker.cpp
> [ 41%] Building CXX object 
> 

Bug#1067063: OpenSSL.crypto.PKCS12 is removed in pyOpenSSL 24.1.0

[Andrey Rakhmatullin]

Package: octavia-tempest-plugin
Version: 2.4.1-1
Severity: serious
Tags: upstream fixed-upstream

octavia_tempest_plugin/common/cert_utils.py uses OpenSSL.crypto.PKCS12() which
was deprecated since pyOpenSSL 23.3.0 and is removed in 24.1.0 which will soon
be uploaded to Debian.  The issue is fixed upstream at
https://github.com/openstack/octavia-tempest-
plugin/commit/25872b36de18a857b1ef36450980f52c8e08e97d , included in 2.5.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

Versions of packages octavia-tempest-plugin depends on:
ii  python3 3.11.8-1
pn  python3-barbicanclient  
ii  python3-cryptography41.0.7-5
ii  python3-dateutil2.8.2-3
pn  python3-httpx   
pn  python3-keystoneauth1   
ii  python3-openssl 24.0.0-3
pn  python3-oslo.config 
pn  python3-oslo.log
pn  python3-oslo.serialization  
pn  python3-oslo.utils  
pn  python3-oslotest
ii  python3-pbr 6.0.0-1
ii  python3-requests2.31.0+dfsg-1
pn  python3-tempest 
pn  python3-tenacity
pn  python3-testtools   
pn  tempest 

octavia-tempest-plugin recommends no packages.

octavia-tempest-plugin suggests no packages.

Bug#1067062: OpenSSL.crypto.PKCS12 is removed in pyOpenSSL 24.1.0

[Andrey Rakhmatullin]

Package: salt-common
Version: 3004.1+dfsg-2.2
Severity: serious
Tags: upstream

salt/modules/tls.py uses OpenSSL.crypto.PKCS12 which was deprecated since
pyOpenSSL 23.3.0 and is removed in 24.1.0 which will soon be uploaded to
Debian. The issue is not fixed (or reported) upstream as far as I can see. The
pyOpenSSL changelog suggests "OpenSSL.crypto.PKCS12 may be replaced by the
PKCS#12 APIs in the cryptography package."


-- 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 salt-common depends on:
ii  iproute2   6.8.0-1
ii  python33.11.8-1
ii  python3-apt2.7.6+b1
ii  python3-dateutil   2.8.2-3
ii  python3-distro 1.9.0-1
ii  python3-jinja2 3.1.3-1
ii  python3-markupsafe 2.1.5-1
ii  python3-msgpack1.0.3-3+b1
ii  python3-pkg-resources  68.1.2-2
ii  python3-psutil 5.9.8-2
ii  python3-pycryptodome   3.20.0+dfsg-1
ii  python3-requests   2.31.0+dfsg-1
ii  python3-yaml   6.0.1-2
pn  python3-zmq

Versions of packages salt-common recommends:
ii  lsb-release   12.0-2
pn  python3-croniter  

Versions of packages salt-common suggests:
ii  python3-mako  1.3.2-1
pn  salt-doc  

Bug#1059042: marked as done (munge: FTBFS if libsystemd-dev is installed)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 19:54:56 +
with message-id 
and subject line Bug#1059042: fixed in munge 0.5.15-4
has caused the Debian Bug report #1059042,
regarding munge: FTBFS if libsystemd-dev is installed
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.)


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

Package: munge
Version: 0.5.15-3
Severity: serious
Tags: patch

Hello, if libsystemd-dev is installed (or something similar, didn't dig too 
much into this), the package FTBFS due to service file not being installed from 
debian/tmp

checking for systemdunitdir... ${prefix}/lib/systemd/system
[...]
dh_missing: warning: usr/lib/systemd/system/munge.service exists in debian/tmp 
but is not installed to anywhere
dh_missing: error: missing files, aborting

This happens e.g. in Ubuntu builders.

Adding the file in not-installed works, but maybe we can just drop that 
debian/rules override_dh_install hack?

G.


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: munge
Source-Version: 0.5.15-4
Done: Gennaro Oliva 

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

Debian distribution maintenance software
pp.
Gennaro Oliva  (supplier of updated munge 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, 17 Mar 2024 17:51:28 +0100
Source: munge
Architecture: source
Version: 0.5.15-4
Distribution: unstable
Urgency: medium
Maintainer: Gennaro Oliva 
Changed-By: Gennaro Oliva 
Closes: 1053827 1058798 1059042
Changes:
 munge (0.5.15-4) unstable; urgency=medium
 .
   * Remove /run/munge on removal only (Closes: #1053827)
   * Move munge.service under /usr (Closes: #1058798)
   * Handle munge.service with munge.install (Closes: #1059042)
Checksums-Sha1:
 d6bfbef95978da3793b17c5569e103fb4c63554a 1994 munge_0.5.15-4.dsc
 88e4f0fa439d78c213e8a3aff7826756115075ce 283185 munge_0.5.15.orig.tar.gz
 4d2f3ff0f98753e089fd054136c7171527f6271f 10484 munge_0.5.15-4.debian.tar.xz
 aa5c43125fa8fb5fba22c4cbd254fa3ff1f43805 7347 munge_0.5.15-4_amd64.buildinfo
Checksums-Sha256:
 9a23e5a22d8e9b45de5edf9cf2f9faad86b65ef67fe01a7aed323a86b0333ac9 1994 
munge_0.5.15-4.dsc
 51b2c81d1a7ec2ab5d486fa51b50c7e79eb1810ca6687b6ed65f3601abc55614 283185 
munge_0.5.15.orig.tar.gz
 dd25bbd1773eeaab750fe1c21797bb4297aa06cc6e869b59e7a93dd7635c252f 10484 
munge_0.5.15-4.debian.tar.xz
 2dad3554c7d45d27a078ff7232247e1160ebea712258d511ab29fd82fe0013ec 7347 
munge_0.5.15-4_amd64.buildinfo
Files:
 2775147a87a483dc35809a4a8584cc08 1994 admin optional munge_0.5.15-4.dsc
 0def5e24a4c1566526472ccafa2fa9aa 283185 admin optional munge_0.5.15.orig.tar.gz
 ef8fbda8f827679f6e9f2abf5b82151c 10484 admin optional 
munge_0.5.15-4.debian.tar.xz
 cac3ec41fba2a100f2a29ef4cbc5f45c 7347 admin optional 
munge_0.5.15-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE6zNF9WRBuLgad5h2ffpBrZYZhdcFAmX3QZcRHG9saXZhQGRl
Ymlhbi5vcmcACgkQffpBrZYZhdfIgQ//XX0FREIFqVU5kHQ+DJ6gJxwLi1tnWK5A
HH/fdeVPesVTKuT9Yrvk1THeRSzzhEsqG2QmmR5c5662lgS8Ybpqv5mLpSwOZhd+
YMUbKAVfjO7a9X8K7U0kKF7uvAZxN5EgbAHwqO/ULn4xvx0OJNc0+u40ck1b0rAc
43AYYSLjv9MR5gZK7wtK2HwWzkChaD97ggZtke1GFqFnaJ+BxMn/MeDqhnQv/cwE
OXczFoKBBzIV7EuBtNNwZoPrgmGgPZjxoJ0KNh81EkSMwNnEmuZRjbAX7vycdpnz
rlDNeVX00ElZu51BatdkPXLFKis3cyZZnWPIDirOg/Sx8NGN8pG8tBQMhB5jIMVW
CPsdatl2Erd3IFmqax1bvck7vXaGLBdjZBoJQXj0acTFCzlg545TcfIiSVne19mB
PWf/4e+mVxK+dOoTsqNHDLk0ljpeW0OaiJNqbjJ7oIRjaVQ2pSD44t/moi+F1F+d
CdzV6ZBfEs3BrtmGLfhpSrztUuCS5/jlEZf4TrXuX3c1M2jKJPk6IuPbCwLboa3u
5wEn5hwOKNn8yHCjQZpxIwb4DGnPda+a7ov84FjOtu54Qt/FUoDKMPJN2GiBklTA
N7OzY0Ska69VlRqs/0/hWARQU7hLVkJGcGvD6vDSfmEJNHaIbdPJAyQPhPnpnmoe
7/fFBVasj2Q=
=399D
-END PGP SIGNATURE-



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

Bug#1067059: ruby-hdfeos5: FTBFS with gcc-14 (-Werror=implicit-function-declaration)

[Bas Couwenberg]

Source: ruby-hdfeos5
Version: 1.2-11
Severity: serious
Tags: ftbfs upstream
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

Your package FTBFS in unstable:

 hdfeos5pt_wrap.c: In function ‘sort_data_byte’:
 hdfeos5pt_wrap.c:329:14: error: implicit declaration of function 
‘HE5_PTreadlevelF’; did you mean ‘HE5_PTreadlevel’? 
[-Werror=implicit-function-declaration]
   329 | status = HE5_PTreadlevelF(i_ptid, i_level, o_linkfield, 
H5T_NATIVE_CHAR, o_data_parent);
   |  ^~~~
   |  HE5_PTreadlevel

 
https://buildd.debian.org/status/fetch.php?pkg=ruby-hdfeos5=amd64=1.2-11%2Bb4=1710703222=log

See also: 
https://gcc.gnu.org/gcc-14/porting_to.html#implicit-function-declaration

Kind Regards,

Bas

Bug#1067058: gnuradio b-d's on a shared library which doesn't exist anymore

[Matthias Klose]

Package: src:gnuradio
Version: 3.10.9.2-1.1
Severity: serious
Tags: sid trixie ftbfs patch

gnuradio b-d's on a shared library which doesn't exist anymore. Just 
drop it, depend on the -dev packages instead.


patch at
http://launchpadlibrarian.net/719912937/gnuradio_3.10.9.2-1.1build1_3.10.9.2-1.1ubuntu1.diff.gz

Bug#1064671: yuzu: FTBFS: vulkan_wrapper.cpp:285:12: error: enumeration value ‘VK_ERROR_INVALID_VIDEO_STD_PARAMETERS_KHR’ not handled in switch [-Werror=switch]

[Bastian Germann]

I am uploading a NMU to fix this.
Please find the debdiff attached.diff -Nru yuzu-0-1335+ds/debian/changelog yuzu-0-1335+ds/debian/changelog
--- yuzu-0-1335+ds/debian/changelog 2023-11-01 22:22:28.0 +
+++ yuzu-0-1335+ds/debian/changelog 2024-03-17 18:37:24.0 +
@@ -1,3 +1,10 @@
+yuzu (0-1335+ds-1.4) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Fix build with current vulkan-headers (Closes: #1064671)
+
+ -- Bastian Germann   Sun, 17 Mar 2024 18:37:24 +
+
 yuzu (0-1335+ds-1.3) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru yuzu-0-1335+ds/debian/patches/series 
yuzu-0-1335+ds/debian/patches/series
--- yuzu-0-1335+ds/debian/patches/series2023-11-01 22:22:28.0 
+
+++ yuzu-0-1335+ds/debian/patches/series2024-03-17 18:35:09.0 
+
@@ -1,6 +1,7 @@
 update-savecontext-loadcontext.patch
 update-vulkan-headers.patch
 fixes-for-gcc-13.patch
+vulkan-headers.patch
 # Upstreamable patches
 cmake-mbedtls.patch
 #cmake-microprofile.patch
diff -Nru yuzu-0-1335+ds/debian/patches/vulkan-headers.patch 
yuzu-0-1335+ds/debian/patches/vulkan-headers.patch
--- yuzu-0-1335+ds/debian/patches/vulkan-headers.patch  1970-01-01 
00:00:00.0 +
+++ yuzu-0-1335+ds/debian/patches/vulkan-headers.patch  2024-03-17 
18:34:23.0 +
@@ -0,0 +1,25 @@
+Origin: 
https://gitlab.com/suyu-emu/suyu/-/commit/310834aea2fa3293ec30bad9f5f37ac7b5681b26
+From: Jan Beich 
+Date: Wed, 20 Dec 2023 01:07:26 +0100
+Subject: vulkan_common: unbreak build with Vulkan-Headers 1.3.274
+
+src/video_core/vulkan_common/vulkan_wrapper.cpp:293:13: error: enumeration 
value 'VK_ERROR_INVALID_VIDEO_STD_PARAMETERS_KHR' not handled in switch 
[-Werror,-Wswitch]
+switch (result) {
+^~
+---
+ src/video_core/vulkan_common/vulkan_wrapper.cpp | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/src/video_core/vulkan_common/vulkan_wrapper.cpp 
b/src/video_core/vulkan_common/vulkan_wrapper.cpp
+index 70cf14afa9..2f78b8af08 100644
+--- a/src/video_core/vulkan_common/vulkan_wrapper.cpp
 b/src/video_core/vulkan_common/vulkan_wrapper.cpp
+@@ -377,6 +377,8 @@ const char* ToString(VkResult result) noexcept {
+ return "VK_OPERATION_DEFERRED_KHR";
+ case VkResult::VK_OPERATION_NOT_DEFERRED_KHR:
+ return "VK_OPERATION_NOT_DEFERRED_KHR";
++case VkResult::VK_ERROR_INVALID_VIDEO_STD_PARAMETERS_KHR:
++return "VK_ERROR_INVALID_VIDEO_STD_PARAMETERS_KHR";
+ case VkResult::VK_PIPELINE_COMPILE_REQUIRED_EXT:
+ return "VK_PIPELINE_COMPILE_REQUIRED_EXT";
+ case VkResult::VK_RESULT_MAX_ENUM:

Bug#1066663: marked as done (dazzdb: FTBFS: ONElib.c:1793:29: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 19:20:38 +
with message-id 
and subject line Bug#103: fixed in dazzdb 1.0+git20230919.414ad05-2
has caused the Debian Bug report #103,
regarding dazzdb: FTBFS: ONElib.c:1793:29: error: implicit declaration of 
function ‘vasprintf’; did you mean ‘vsprintf’? 
[-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.)


-- 
103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dazzdb
Version: 1.0+git20230919.414ad05-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):
> cc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O3 
> -Wall -Wextra -Wno-unused-result -fno-strict-aliasing -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now  DB2ONE.c DB.c DB.h QV.c QV.h 
> ONElib.c ONElib.h  -lm -lz -o DB2ONE
> ONElib.c: In function ‘oneAddProvenance’:
> ONElib.c:1793:29: error: implicit declaration of function ‘vasprintf’; did 
> you mean ‘vsprintf’? [-Werror=implicit-function-declaration]
>  1793 |   va_start (args, format) ; vasprintf (, format, args) ; 
> va_end (args) ;
>   | ^
>   | vsprintf
> ONElib.c: In function ‘intGet’:
> ONElib.c:3487:7: warning: this statement may fall through 
> [-Wimplicit-fallthrough=]
>  3487 |   switch (u[0] & 0x07)
>   |   ^~
> ONElib.c:3498:5: note: here
>  3498 | case 4:
>   | ^~~~
> In function ‘intGet’,
> inlined from ‘ltfRead’ at ONElib.c:3547:7:
> ONElib.c:3502:25: warning: ‘u’ may be used uninitialized 
> [-Wmaybe-uninitialized]
>  3502 | case 1: *pval = *(I64*)(u+1) | 0x ; return 3 ;
>   | ^~~~
> ONElib.c: In function ‘ltfRead’:
> ONElib.c:3542:17: note: ‘u’ declared here
>  3542 |   unsigned char u[16] ;
>   | ^
> In function ‘intGet’,
> inlined from ‘ltfRead’ at ONElib.c:3547:7:
> ONElib.c:3503:25: warning: ‘u’ may be used uninitialized 
> [-Wmaybe-uninitialized]
>  3503 | case 2: *pval = *(I64*)(u+1) | 0xff00 ; return 4 ;
>   | ^~~~
> ONElib.c: In function ‘ltfRead’:
> ONElib.c:3542:17: note: ‘u’ declared here
>  3542 |   unsigned char u[16] ;
>   | ^
> In function ‘intGet’,
> inlined from ‘ltfRead’ at ONElib.c:3547:7:
> ONElib.c:3504:25: warning: ‘u’ may be used uninitialized 
> [-Wmaybe-uninitialized]
>  3504 | case 3: *pval = *(I64*)(u+1) | 0x ; return 5 ;
>   | ^~~~
> ONElib.c: In function ‘ltfRead’:
> ONElib.c:3542:17: note: ‘u’ declared here
>  3542 |   unsigned char u[16] ;
>   | ^
> In function ‘intGet’,
> inlined from ‘ltfRead’ at ONElib.c:3547:7:
> ONElib.c:3505:25: warning: ‘u’ may be used uninitialized 
> [-Wmaybe-uninitialized]
>  3505 | case 4: *pval = *(I64*)(u+1) | 0xff00 ; return 6 ;
>   | ^~~~
> ONElib.c: In function ‘ltfRead’:
> ONElib.c:3542:17: note: ‘u’ declared here
>  3542 |   unsigned char u[16] ;
>   | ^
> In function ‘intGet’,
> inlined from ‘ltfRead’ at ONElib.c:3547:7:
> ONElib.c:3506:25: warning: ‘u’ may be used uninitialized 
> [-Wmaybe-uninitialized]
>  3506 | case 5: *pval = *(I64*)(u+1) | 0x ; return 7 ;
>   | ^~~~
> ONElib.c: In function ‘ltfRead’:
> ONElib.c:3542:17: note: ‘u’ declared here
>  3542 |   unsigned char u[16] ;
>   | ^
> In function ‘intGet’,
> inlined from ‘ltfRead’ at ONElib.c:3547:7:
> ONElib.c:3507:25: warning: ‘u’ may be used uninitialized 
> [-Wmaybe-uninitialized]
>  3507 | case 6: *pval = *(I64*)(u+1) | 0xff00 ; return 8 ;
>   | ^~~~
> ONElib.c: In function ‘ltfRead’:
> ONElib.c:3542:17: note: ‘u’ declared here
>  3542 |   unsigned char u[16] 

Bug#1066485: marked as done (volpack: FTBFS: scalevolume.c:63:9: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 19:04:36 +
with message-id 
and subject line Bug#1066485: fixed in volpack 1.0b3-9.1
has caused the Debian Bug report #1066485,
regarding volpack: FTBFS: scalevolume.c:63:9: 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.)


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

Hi,

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

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -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 -c -o denfile.o denfile.c
> scalevolume.c:42:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>42 | main(argc, argv)
>   | ^~~~
> scalevolume.c: In function ‘main’:
> scalevolume.c:63:9: error: implicit declaration of function ‘exit’ 
> [-Werror=implicit-function-declaration]
>63 | exit(1);
>   | ^~~~
> scalevolume.c:41:1: note: include ‘’ or provide a declaration of 
> ‘exit’
>40 | #include 
>   +++ |+#include 
>41 | 
> scalevolume.c:63:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>63 | exit(1);
>   | ^~~~
> scalevolume.c:63:9: note: include ‘’ or provide a declaration of 
> ‘exit’
> scalevolume.c:72:14: error: implicit declaration of function ‘strcmp’ 
> [-Werror=implicit-function-declaration]
>72 | if (!strcmp(argv[6], "-b")) {
>   |  ^~
> scalevolume.c:41:1: note: include ‘’ or provide a declaration of 
> ‘strcmp’
>40 | #include 
>   +++ |+#include 
>41 | 
> scalevolume.c:84:13: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>84 | exit(1);
>   | ^~~~
> scalevolume.c:84:13: note: include ‘’ or provide a declaration of 
> ‘exit’
> scalevolume.c:91:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>91 | exit(1);
>   | ^~~~
> scalevolume.c:91:9: note: include ‘’ or provide a declaration of 
> ‘exit’
> scalevolume.c:101:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>   101 | exit(1);
>   | ^~~~
> scalevolume.c:101:9: note: include ‘’ or provide a declaration of 
> ‘exit’
> scalevolume.c:109:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>   109 | exit(1);
>   | ^~~~
> scalevolume.c:109:9: note: include ‘’ or provide a declaration of 
> ‘exit’
> scalevolume.c:113:10: error: implicit declaration of function ‘write_den’ 
> [-Werror=implicit-function-declaration]
>   113 | if (!write_den(dst_file, dst_volume, dst_xlen, dst_ylen, 
> dst_zlen))
>   |  ^
> scalevolume.c:114:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>   114 | exit(1);
>   | ^~~~
> scalevolume.c:114:9: note: include ‘’ or provide a declaration of 
> ‘exit’
> scalevolume.c:116:5: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>   116 | exit(0);
>   | ^~~~
> scalevolume.c:116:5: note: include ‘’ or provide a declaration of 
> ‘exit’
> denfile.c: In function ‘read_den’:
> denfile.c:51:15: error: implicit declaration of function ‘open’; did you mean 
> ‘popen’? [-Werror=implicit-function-declaration]
>51 | if ((fd = open(filename, 0)) < 0) {
>   |   ^~~~
>   |   popen
> denfile.c:57:10: error: implicit declaration of function ‘read_shorts’ 
> [-Werror=implicit-function-declaration]
>57 | if (!read_shorts(fd, _version, 1, 0)) {
>   |  ^~~
> denfile.c:81:10: error: 

Bug#1064612: marked as done (rust-ahash: Failing autopkgtests)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 19:03:40 +
with message-id 
and subject line Bug#1064612: fixed in rust-ahash 0.8.11-1
has caused the Debian Bug report #1064612,
regarding rust-ahash: Failing autopkgtests
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.)


-- 
1064612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-ahash
Version: 0.8.8-2
Severity: serious

rust-ahash is unable to migrate to Testing because its autopkgtests are failing:

https://qa.debian.org/excuses.php?package=rust-ahash

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: rust-ahash
Source-Version: 0.8.11-1
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
rust-ahash, 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.
Jonas Smedegaard  (supplier of updated rust-ahash 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, 17 Mar 2024 18:14:24 +0100
Source: rust-ahash
Architecture: source
Version: 0.8.11-1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1064612
Changes:
 rust-ahash (0.8.11-1) unstable; urgency=medium
 .
   [ upstream ]
   * new release(s)
 .
   [ Jonas Smedegaard ]
   * update and unfuzz patches; update DEP-3 headers
   * extend patch 1002;
 closes: bug#1064612, thanks (again) to Peter Michael Green
   * bump project versions in virtual packages and autopkgtests
   * add patch 2001_pcg-mwc
 to avoid test-only not-in-Debian crate pcg-mwc
   * add patch 2001_smallvec
 to accept older releases of crate smallvec
   * add patch 1003 to fix upstream version;
 temporarily tolerate failing build target dh_auto_clean
   * build- and autopkgtest-depend on package for crate smallvec
Checksums-Sha1:
 639b4ef0bf10d76c3eb1836f7312c64c52c02502 3445 rust-ahash_0.8.11-1.dsc
 8f1a37ebe2566de5f086c60fe04b26e09e61c619 559442 rust-ahash_0.8.11.orig.tar.gz
 e021911c5e94ebc8b357561ca9c0f3f4f7982285 18504 
rust-ahash_0.8.11-1.debian.tar.xz
 4f5be555ae33351bcc2fc4dd6ad9652321d3 19763 
rust-ahash_0.8.11-1_amd64.buildinfo
Checksums-Sha256:
 ff806659d35b12fc2ba82ee79442ef52806be1cea664ce26ab9cf6a2235d344d 3445 
rust-ahash_0.8.11-1.dsc
 374feba319eb17defdf1363a4ef2da11e39ebe277aca6ca0ebc7a871de88c6ca 559442 
rust-ahash_0.8.11.orig.tar.gz
 3f06e16fb4a883fec9bd32b0c4019348228e1d9e0fe264e583258b6e962ca8c7 18504 
rust-ahash_0.8.11-1.debian.tar.xz
 1d88c0910bfab51393f5d7e2849e50ba214e97f06b1e6af4d20f44d5c7dfe754 19763 
rust-ahash_0.8.11-1_amd64.buildinfo
Files:
 756c34d941daa2325a0112300d587185 3445 rust optional rust-ahash_0.8.11-1.dsc
 5419861cf1bae416017be3d9484d70c6 559442 rust optional 
rust-ahash_0.8.11.orig.tar.gz
 5975cc29e370e38bd486107c24fa74ae 18504 rust optional 
rust-ahash_0.8.11-1.debian.tar.xz
 45f26ddab674f6d1d00d88e1e3950501 19763 rust optional 
rust-ahash_0.8.11-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmX3L5sACgkQLHwxRsGg
ASFQTg//aL+NiuVlpQry03RAkS4S8DVt5leIihaMyg2MLw5B/LAqjRRi//lKCgBN
RBTBVISY8lMAVaV6UnwwKiQZaFTf3NxaO0ShePau1/eZ6ox0ccqj3XwYA7qnZI0N
wJgq4hIBpG/aMTUfq3P6TNRlrTHKvcA9p7LtsO/7i97GZQQD1o3vCIllqMLSDxxK
Z2ptI4L8FcdiO3n9fvkaXo5BnySQBwdEPbmaIZbmRtxdEzyzq/YYtonvfnf0yUHA
l5kP+Mu336GVpScUsw1Wdb08OG8jf23uVVxKdmwtwpRfypCGgV+alc01OOK3VXqB
XsxORu3Zw0Ag1aisjFRlAhfPKTNfhmIzeboQ20yuFAsx0Jrwi82WMuOsYGS24uDe
zWrTKjISeZB2AcfmuYUmZBuKifcaLRQmAhI+BPigPiIv20cbor75GbNu9Don+TNN
Uw5d984TS76b02AJGoztDOXWmvCvUKWy91qxX5P+K0CXlnAAP1qpSqSxNeCbsfMJ
6mBw0f9m4XokbJfBckVcgH9+FdBMzixmoABbdpRAZ+hY+6LbJ5Q6XUy9bTL3suad
4C7QkIMfMMlvo8icrCVbK3Ape6p23Cs5RpXMDAp2tZ5q3thHESxssSGi3dHNlRpU
VYRVjPFVa0i3HSx0bCooNH7zxS2X5cJpNE0Y/AUBF7ewGvYmWPs=
=voWW
-END PGP SIGNATURE-



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

Bug#1064745: marked as done (libgnatcoll-db: FTBFS: make[1]: *** [debian/rules:81: override_dh_auto_build-arch] Error 4)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 18:47:05 +
with message-id 
and subject line Bug#1064745: fixed in libgnatcoll-db 23.0.0-6
has caused the Debian Bug report #1064745,
regarding libgnatcoll-db: FTBFS: make[1]: *** [debian/rules:81: 
override_dh_auto_build-arch] Error 4
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.)


-- 
1064745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgnatcoll-db
Version: 23.0.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> gprconfig --batch --config=Ada --config=Cgcc-12
> rm -f xref/generated/*
> gprbuild -p -R -v -j8  -XGNATCOLL_SQLITE=external -aPsql -aPsqlite 
> -aPpostgres -aPxref -XGNATCOLL_SQL_VERSION=3 -XGNATCOLL_SQLITE_VERSION=20 
> -XGNATCOLL_POSTGRES_VERSION=1 -XGNATCOLL_XREF_VERSION=20  
> gnatcoll_db2ada/gnatcoll_all2ada.gpr -XLIBRARY_TYPE=relocatable
> object directory "/<>/sql/obj/relocatable" created for project 
> GnatColl_SQL
> library directory "/<>/sql/lib/relocatable" created for project 
> GnatColl_SQL
> object directory "/<>/sqlite/obj/relocatable" created for 
> project GnatColl_Sqlite
> library directory "/<>/sqlite/lib/relocatable" created for 
> project GnatColl_Sqlite
> object directory "/<>/postgres/obj/relocatable" created for 
> project GnatColl_Postgres
> library directory "/<>/postgres/lib/relocatable" created for 
> project GnatColl_Postgres
> object directory "/<>/gnatcoll_db2ada/obj" created for project 
> gnatcoll_all2ada
> Changing to object directory of "gnatcoll_all2ada": 
> "/<>/gnatcoll_db2ada/obj/"
> /usr/bin/x86_64-linux-gnu-gcc-12 -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection -gno-record-gcc-switches 
> -gnatec=/tmp/GNAT-TEMP-01.TMP -gnatem=/tmp/GNAT-TEMP-02.TMP 
> /<>/gnatcoll_db2ada/gnatcoll_all2ada.adb
> Changing to object directory of "GnatColl_Postgres": 
> "/<>/postgres/obj/relocatable/"
> /usr/bin/gcc-12 -c -x c -O2 -Wunreachable-code -DHAS_PQPREPARE -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MMD -MF postgres_support.d 
> -specs=/tmp/GNAT-TEMP-04.TMP /<>/postgres/postgres_support.c
> /usr/bin/x86_64-linux-gnu-gcc-12 -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection -gno-record-gcc-switches -fPIC 
> -gnatec=/tmp/GNAT-TEMP-05.TMP -gnatem=/tmp/GNAT-TEMP-06.TMP 
> /<>/postgres/gnatcoll-sql-ranges.adb
> /usr/bin/x86_64-linux-gnu-gcc-12 -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection -gno-record-gcc-switches -fPIC 
> -gnatec=/tmp/GNAT-TEMP-05.TMP -gnatem=/tmp/GNAT-TEMP-07.TMP 
> /<>/postgres/gnatcoll-sql-postgres.adb
> Changing to object directory of "GnatColl_Sqlite": 
> "/<>/sqlite/obj/relocatable/"
> /usr/bin/x86_64-linux-gnu-gcc-12 -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection -gno-record-gcc-switches -fPIC 
> -gnatec=/tmp/GNAT-TEMP-08.TMP -gnatem=/tmp/GNAT-TEMP-09.TMP 
> /<>/sqlite/gnatcoll-sql-sqlite-builder.adb
> /usr/bin/x86_64-linux-gnu-gcc-12 -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection -gno-record-gcc-switches -fPIC 
> -gnatec=/tmp/GNAT-TEMP-08.TMP -gnatem=/tmp/GNAT-TEMP-10.TMP 
> /<>/sqlite/gnatcoll-sql-sqlite.adb
> /usr/bin/x86_64-linux-gnu-gcc-12 -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection -gno-record-gcc-switches -fPIC 
> -gnatec=/tmp/GNAT-TEMP-08.TMP -gnatem=/tmp/GNAT-TEMP-11.TMP 
> /<>/sqlite/gnatcoll-sql-sqlite-gnade.adb
> Changing to object directory of "GnatColl_SQL": 
> "/<>/sql/obj/relocatable/"
> /usr/bin/x86_64-linux-gnu-gcc-12 -c -x ada -gnatA -O2 -gnatn -gnatwaCJ -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection -gno-record-gcc-switches -fPIC 
> -gnatec=/tmp/GNAT-TEMP-12.TMP 

Bug#1066791: marked as done (pyiosxr: FTBFS: ModuleNotFoundError: No module named 'netmiko.ssh_exception')

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 18:46:40 +
with message-id 
and subject line Bug#1065370: Removed package(s) from unstable
has caused the Debian Bug report #1066791,
regarding pyiosxr: FTBFS: ModuleNotFoundError: No module named 
'netmiko.ssh_exception'
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.)


-- 
1066791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyiosxr
Version: 0.53-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):
>  debian/rules build
> dh build --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:744: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'description-file' will not be supported in 
> future
> versions. Please use the underscore name 'description_file' instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> running config
> I: pybuild base:305: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:744: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'description-file' will not be supported in 
> future
> versions. Please use the underscore name 'description_file' instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:744: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'description-file' will not be supported in 
> future
> versions. Please use the underscore name 'description_file' instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> running build
> running build_py
> file pyIOSXR.py (for module pyIOSXR) not found
> creating /<>/.pybuild/cpython3_3.12_pyIOSXR/build/pyIOSXR
> copying pyIOSXR/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_pyIOSXR/build/pyIOSXR
> copying pyIOSXR/exceptions.py -> 
> /<>/.pybuild/cpython3_3.12_pyIOSXR/build/pyIOSXR
> copying pyIOSXR/iosxr.py -> 
> /<>/.pybuild/cpython3_3.12_pyIOSXR/build/pyIOSXR
> running egg_info
> creating pyIOSXR.egg-info
> writing pyIOSXR.egg-info/PKG-INFO
> writing dependency_links to pyIOSXR.egg-info/dependency_links.txt
> writing requirements to pyIOSXR.egg-info/requires.txt
> writing top-level names to pyIOSXR.egg-info/top_level.txt
> writing manifest file 'pyIOSXR.egg-info/SOURCES.txt'
> file pyIOSXR.py (for module pyIOSXR) not found
> reading manifest file 'pyIOSXR.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'pyIOSXR.egg-info/SOURCES.txt'
> file pyIOSXR.py (for module pyIOSXR) not found
> I: pybuild base:305: /usr/bin/python3 setup.py build 
> 

Processed: Bug#1064671 marked as pending in yuzu

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1064671 [src:yuzu] yuzu: FTBFS: vulkan_wrapper.cpp:285:12: error: 
enumeration value ‘VK_ERROR_INVALID_VIDEO_STD_PARAMETERS_KHR’ not handled in 
switch [-Werror=switch]
Added tag(s) pending.

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

Bug#1064671: marked as pending in yuzu

[Bastian Germann]

Control: tag -1 pending

Hello,

Bug #1064671 in yuzu 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/yuzu/-/commit/442331b9da1bc900b144a796a46b96aed68d9a3d


Fix build with current vulkan-headers (Closes: #1064671)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064671

Bug#1061703: marked as done (gnome-characters nocheck FTBFS: ../meson.build:47:14: ERROR: Program '/usr/bin/gjs-console' not found or not executable)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 18:36:51 +
with message-id 
and subject line Bug#1061703: fixed in gnome-characters 45.0-3
has caused the Debian Bug report #1061703,
regarding gnome-characters nocheck FTBFS: ../meson.build:47:14: ERROR: Program 
'/usr/bin/gjs-console' not found or not executable
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.)


-- 
1061703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-characters
Version: 45.0-2
Severity: serious
Tags: ftbfs

Hi,

gnome-characters fails to build from source when built with the nocheck
build profile. A build ends with:

| Run-time dependency gjs-1.0 found: YES 1.78.1
| env[PKG_CONFIG_PATH]:
| env[PKG_CONFIG]: /usr/bin/mips64el-linux-gnuabi64-pkg-config
| ---
| Called: `/usr/bin/mips64el-linux-gnuabi64-pkg-config --variable=gjs_console 
gjs-1.0` -> 0
| stdout:
| /usr/bin/gjs-console
| ---
| Got pkg-config variable gjs_console : /usr/bin/gjs-console
| Program /usr/bin/gjs-console found: NO
| 
| ../meson.build:47:14: ERROR: Program '/usr/bin/gjs-console' not found or not 
executable
| dh_auto_configure: error: cd obj-mips64el-linux-gnuabi64 && 
DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/mips64el-linux-gnuabi64 
-Dpython.bytecompile=-1 --cross-file 
/<>/debian/.debhelper/generated/_source/meson-cross-file.conf 
returned exit code 1
| make: *** [debian/rules:7: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

Since trixie, a FTBFS with the nocheck build profile is considered
release-critical. The  annotation on the gjs build dependency
should be dropped or some change to the upstream build system should
enable building without gjs-console.

Helmut
--- End Message ---
--- Begin Message ---
Source: gnome-characters
Source-Version: 45.0-3
Done: Simon McVittie 

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gnome-characters 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: Sun, 17 Mar 2024 17:35:16 +
Source: gnome-characters
Architecture: source
Version: 45.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1061703
Changes:
 gnome-characters (45.0-3) unstable; urgency=medium
 .
   * Team upload
   * d/control: gjs is needed at build-time even if not running tests.
 This source package only has one binary package, and it requires gjs,
 so there would be no benefit to adjusting the upstream build system
 to be able to build without gjs present. (Closes: #1061703)
   * d/control: Build-depend on pkgconf instead of superseded pkg-config
   * d/lintian-overrides: Remove unused override
Checksums-Sha1:
 d297b34babd27a906607d298112df8f31623a848 2536 gnome-characters_45.0-3.dsc
 6cd715a837d4b1c0ba87371e014287bafe04c178 21712 
gnome-characters_45.0-3.debian.tar.xz
 251d5c9b2203795d112c6ee15e75ff4f649d0f1f 15832 
gnome-characters_45.0-3_source.buildinfo
Checksums-Sha256:
 0f1413380bd521f86fbe9dc9f89b4dd42e86117072792328fc604febdbcfea42 2536 
gnome-characters_45.0-3.dsc
 66f1582091c5df4322505b0cbd30c9300ec844b93d929218476bd589b022beff 21712 
gnome-characters_45.0-3.debian.tar.xz
 f24e863c0cfcb3ebd70bcc2ce1e3aba0b3885cb7d6bb11adec76b22151d23c4a 15832 
gnome-characters_45.0-3_source.buildinfo
Files:
 b7ee049aad3bf020420d5816b7d748c0 2536 gnome optional 
gnome-characters_45.0-3.dsc
 e447d05f81c22fed399d02d79671efa6 21712 gnome optional 
gnome-characters_45.0-3.debian.tar.xz
 0344aa4df18706afd9c1db4f57d23b52 15832 gnome optional 
gnome-characters_45.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmX3LUgACgkQ4FrhR4+B
TE960w//cg82mp6s3KyK69n7ndIvsVbytTF4udKo0aikeRnPHNvMIYVzfEmnCo8Q

Processed: Re: libdbi-drivers: FTBFS: src/unit.c:229:5: error: implicit declaration of function ‘wait’; did you mean ‘want’? [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066281 [src:libdbi-drivers] libdbi-drivers: FTBFS: src/unit.c:229:5: 
error: implicit declaration of function ‘wait’; did you mean ‘want’? 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1066281: libdbi-drivers: FTBFS: src/unit.c:229:5: error: implicit declaration of function ‘wait’; did you mean ‘want’? [-Werror=implicit-function-declaration]

[Steve Langasek]

Package: libdbi-drivers
Version: 0.9.0-11
Followup-For: Bug #1066281
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a (trivial) patch for this issue.

-- 
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 libdbi-drivers-0.9.0/debian/control 
libdbi-drivers-0.9.0/debian/control
--- libdbi-drivers-0.9.0/debian/control 2023-01-18 07:10:49.0 -0800
+++ libdbi-drivers-0.9.0/debian/control 2024-03-17 11:28:49.0 -0700
@@ -1,8 +1,7 @@
 Source: libdbi-drivers
 Section: libs
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Laszlo Boszormenyi (GCS) 
+Maintainer: Laszlo Boszormenyi (GCS) 
 Uploaders: Prach Pongpanich 
 Build-Depends: automake,
debhelper-compat (= 12),
diff -Nru libdbi-drivers-0.9.0/debian/patches/no-implicit-declarations.patch 
libdbi-drivers-0.9.0/debian/patches/no-implicit-declarations.patch
--- libdbi-drivers-0.9.0/debian/patches/no-implicit-declarations.patch  
1969-12-31 16:00:00.0 -0800
+++ libdbi-drivers-0.9.0/debian/patches/no-implicit-declarations.patch  
2024-03-17 11:28:43.0 -0700
@@ -0,0 +1,20 @@
+Description: fix implicit declaration error for wait()
+ 64-bit time_t requires us to be stricter about function declarations.
+ include the missing system header that defines wait().
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066281
+Forwarded: no
+Last-Update: 2024-03-17
+
+Index: libdbi-drivers-0.9.0/tests/cgreen/src/unit.c
+===
+--- libdbi-drivers-0.9.0.orig/tests/cgreen/src/unit.c
 libdbi-drivers-0.9.0/tests/cgreen/src/unit.c
+@@ -9,6 +9,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ enum {test_function, test_suite};
+ 
diff -Nru libdbi-drivers-0.9.0/debian/patches/series 
libdbi-drivers-0.9.0/debian/patches/series
--- libdbi-drivers-0.9.0/debian/patches/series  2023-01-18 07:10:47.0 
-0800
+++ libdbi-drivers-0.9.0/debian/patches/series  2024-03-17 11:26:21.0 
-0700
@@ -10,3 +10,4 @@
 test_mysql_date_tz.patch
 mysql-8.0.patch
 no_mariadb_timezone.patch
+no-implicit-declarations.patch

Bug#1067055: openmpi: error: implicit declaration of function 'OPAL_THREAD_ADD_FETCH64'

[Thorsten Glaser]

Source: openmpi
Version: 4.1.6-7
Severity: serious
Justification: ftbfs
Tags: ftbfs
Tag: ftbfs
X-Debbugs-Cc: t...@mirbsd.de

[…]
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../../../opal/mca/btl/ofi 
-I../../../../opal/include -I../../../../ompi/include 
-I../../../../oshmem/include 
-I../../../../opal/mca/hwloc/hwloc201/hwloc/include/private/autogen 
-I../../../../opal/mca/hwloc/hwloc201/hwloc/include/hwloc/autogen 
-I../../../../ompi/mpiext/cuda/c -I../../../../../.. -I../../../.. 
-I../../../../../../opal/include -I../../../../../../orte/include 
-I../../../../orte/include -I../../../../../../ompi/include 
-I../../../../../../oshmem/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include 
-I/usr/local/include -DNDEBUG -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/tmp/buildd/openmpi-4.1.6=. -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -finline-functions -fno-strict-aliasing -c 
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c  -fPIC -DPIC -o 
.libs/btl_ofi_rdma.o
In file included from ../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c:14:
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c: In function 
'mca_btl_ofi_get':
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.h:33:13: error: implicit 
declaration of function 'OPAL_THREAD_ADD_FETCH64'; did you mean 
'OPAL_THREAD_ADD_FETCH32'? [-Werror=implicit-function-declaration]
   33 | OPAL_THREAD_ADD_FETCH64(&(module)->outstanding_rdma, 1);
\
  | ^~~
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c:70:5: note: in expansion of 
macro 'MCA_BTL_OFI_NUM_RDMA_INC'
   70 | MCA_BTL_OFI_NUM_RDMA_INC(ofi_btl);
  | ^~~~
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c:82:40: warning: cast from 
pointer to integer of different size [-Wpointer-to-int-cast]
   82 | remote_address = (remote_address - (uint64_t) 
remote_handle->base_addr);
  |^
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c: In function 
'mca_btl_ofi_put':
../../../../../../opal/mca/btl/ofi/btl_ofi_rdma.c:132:40: warning: cast from 
pointer to integer of different size [-Wpointer-to-int-cast]
  132 | remote_address = (remote_address - (uint64_t) 
remote_handle->base_addr);
  |^
cc1: some warnings being treated as errors
make[4]: *** [Makefile:1946: btl_ofi_rdma.lo] Error 1
make[4]: Leaving directory 
'/tmp/buildd/openmpi-4.1.6/debian/build-gfortran/opal/mca/btl/ofi'

Bug#1066326: marked as done (codonw: FTBFS: codonW.h:38:74: error: implicit declaration of function ‘gets’; did you mean ‘fgets’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 18:34:53 +
with message-id 
and subject line Bug#1066326: fixed in codonw 1.4.4-8
has caused the Debian Bug report #1066326,
regarding codonw: FTBFS: codonW.h:38:74: error: implicit declaration of 
function ‘gets’; did you mean ‘fgets’? [-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.)


-- 
1066326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: codonw
Version: 1.4.4-7
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):
> cc -c -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -DLINUX -Wdate-time -D_FORTIFY_SOURCE=2 coresp.c
> In file included from menu.c:31:
> menu.c: In function ‘main_menu’:
> codonW.h:38:74: error: implicit declaration of function ‘gets’; did you mean 
> ‘fgets’? [-Werror=implicit-function-declaration]
>38 | #define pause {fprintf(stderr,"\nPress return or enter to continue -> 
> ");gets(pm->junk);}
>   |   
>^~~~
> menu.c:69:9: note: in expansion of macro ‘pause’
>69 | pause;
>   | ^
> codons.c: In function ‘main’:
> codons.c:190:55: warning: format ‘%i’ expects argument of type ‘int’, but 
> argument 3 has type ‘long int’ [-Wformat=]
>   190 | fprintf(pm->my_err,"\n\n\t\tNumber of sequences: %i\n",
>   |  ~^
>   |   |
>   |   int
>   |  %li
>   191 | num_sequence);
>   |    
>   | |
>   | long int
> codons.c:196:32: warning: format ‘%i’ expects argument of type ‘int’, but 
> argument 3 has type ‘long int’ [-Wformat=]
>   196 |fprintf(pm->my_err, "\tWARNING\t At least one sequence in 
> your"
>   |
> ^~~
>   197 | " input file has\ninternal stop codons (found %i"
>   198 | " internal stops) \tWARNING\n",num_seq_int_stop);
>   |
>   ||
>   |long int
> codons.c:197:68: note: format string is defined here
>   197 | " input file has\ninternal stop codons (found %i"
>   |   ~^
>   ||
>   |int
>   |   %li
> codons.c:200:46: warning: format ‘%i’ expects argument of type ‘int’, but 
> argument 3 has type ‘long int’ [-Wformat=]
>   200 |fprintf(pm->my_err, "\tWARNING\t %i sequences had internal 
> "
>   | ~^
>   |  |
>   |  int
>   | %li
>   201 |"stop codons 
> \tWARNING\n",num_seq_int_stop);
>   |  
>   |  |
>   |  long int
> In file included from codons.c:90:
> codonW.h:38:74: error: implicit declaration of function ‘gets’; did you mean 
> ‘fgets’? [-Werror=implicit-function-declaration]
>38 | #define pause {fprintf(stderr,"\nPress return or enter to continue -> 
> ");gets(pm->junk);}
>   | 

Bug#1066351: marked as done (aalib: FTBFS: aainfo.c:12:9: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 18:34:30 +
with message-id 
and subject line Bug#1066351: fixed in aalib 1.4p5-51.1
has caused the Debian Bug report #1066351,
regarding aalib: FTBFS: aainfo.c:12:9: 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.)


-- 
1066351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aalib
Version: 1.4p5-51
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.   -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  -I/usr/include  
> -I/usr/include/ncurses  -c -o aainfo.o aainfo.c
> aainfo.c: In function ‘main’:
> aainfo.c:12:9: error: implicit declaration of function ‘exit’ 
> [-Werror=implicit-function-declaration]
>12 | exit(1);
>   | ^~~~
> aainfo.c:4:1: note: include ‘’ or provide a declaration of ‘exit’
> 3 | #include "aaint.h"
>   +++ |+#include 
> 4 | int main(int argc, char **argv)
> aainfo.c:12:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>12 | exit(1);
>   | ^~~~
> aainfo.c:12:9: note: include ‘’ or provide a declaration of ‘exit’
> aainfo.c:17:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>17 | exit(1);
>   | ^~~~
> aainfo.c:17:9: note: include ‘’ or provide a declaration of ‘exit’
> cc1: some warnings being treated as errors
> make[4]: *** [Makefile:712: aainfo.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/aalib_1.4p5-51_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: aalib
Source-Version: 1.4p5-51.1
Done: Andrey Rakhmatullin 

We believe that the bug you reported is fixed in the latest version of
aalib, 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.
Andrey Rakhmatullin  (supplier of updated aalib 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: Wed, 13 Mar 2024 22:25:58 +0500
Source: aalib
Architecture: source
Version: 1.4p5-51.1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter 
Changed-By: Andrey Rakhmatullin 
Closes: 1066351
Changes:
 aalib (1.4p5-51.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066351).
Checksums-Sha1:
 8b6ef25c5a7bebe7118c0f8e14fce3d12261b28c 2020 aalib_1.4p5-51.1.dsc
 f2d6fb57554187a5c61086ed50212df5988cf807 17368 aalib_1.4p5-51.1.debian.tar.xz
 5d4bcd31f4026989bd559fc9a01ffbff311c3cdb 8086 aalib_1.4p5-51.1_amd64.buildinfo
Checksums-Sha256:
 

Bug#1067054: Debian 12 - Copy files on USB 3

[pham...@bluewin.ch]

Package: kernel
Version: 6.1.76-1 (2024-02-01)
Severity: critical

Bug Description:
Good morning,
I noticed a problem with Debian 12 and USB 3.
When I copy a large volume of data +/- 150 Gb onto a 2.5 inch SSD integrated 
into an external enclosure (Satechi) which has a USB 3 type C socket and this 
enclosure is plugged into a USB 3 A socket on my PC, the copy cuts out after a 
while (+/- 20%), there is a crash. If I use a USB 3 C socket on my PC it seems 
to make the problem worse.
Same thing if I restore a 250 GB disk image, it also crashes.
If I do the same restoration job but on a 2 A USB socket, everything works 
perfectly, except that it takes a lot of time...
If I use an M.2 2280 drive also integrated into an external enclosure with a 
USB 3 type C socket, everything works fine.
If I use an SD card connected to an SD card reader connected via USB 3 to my 
machine it also works perfectly.
Debian and its kernel do not seem to appreciate 2.5 inch SSDs integrated into 
external enclosures with a USB 3 type C socket...
Please try to fix this...
Best regards.

Processed: Bug#1066663 marked as pending in dazzdb

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #103 [src:dazzdb] dazzdb: FTBFS: ONElib.c:1793:29: error: implicit 
declaration of function ‘vasprintf’; did you mean ‘vsprintf’? 
[-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1066663: marked as pending in dazzdb

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #103 in dazzdb 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/med-team/dazzdb/-/commit/6fe639ca615c146de96937acc2c5122addd74a15


fix-declaration.patch: new: fix build failure.

The patch appends the missing declarations for vasprintf(3).

Closes: #103


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/103

Bug#1066772: marked as done (seqmagick: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 18:16:02 +
with message-id 
and subject line Bug#1066772: fixed in seqmagick 0.8.6-2
has caused the Debian Bug report #1066772,
regarding seqmagick: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.12 3.11" returned exit code 13
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.)


-- 
1066772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seqmagick
Version: 0.8.6-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):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/dist.py:509: 
> SetuptoolsDeprecationWarning: Invalid version: ''.
> !!
> 
> 
> 
> The version specified is not a valid version according to PEP 440.
> This may not work as expected with newer versions of
> setuptools, pip, and PyPI.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See https://peps.python.org/pep-0440/ for details.
> 
> 
> 
> !!
>   self._validate_version(self.metadata.version)
> running config
> I: pybuild base:305: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/dist.py:509: 
> SetuptoolsDeprecationWarning: Invalid version: ''.
> !!
> 
> 
> 
> The version specified is not a valid version according to PEP 440.
> This may not work as expected with newer versions of
> setuptools, pip, and PyPI.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See https://peps.python.org/pep-0440/ for details.
> 
> 
> 
> !!
>   self._validate_version(self.metadata.version)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/dist.py:509: 
> SetuptoolsDeprecationWarning: Invalid version: ''.
> !!
> 

Processed: bug 1063962 is forwarded to https://github.com/pytest-dev/pytest-order/issues/110

[Debian Bug Tracking System]

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

> forwarded 1063962 https://github.com/pytest-dev/pytest-order/issues/110
Bug #1063962 [pytest-order] pytest-order: autopkgtest regression with pytest 8
Set Bug forwarded-to-address to 
'https://github.com/pytest-dev/pytest-order/issues/110'.
> thanks
Stopping processing here.

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

Bug#1061703: marked as pending in gnome-characters

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #1061703 in gnome-characters 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/gnome-team/gnome-characters/-/commit/04fb8b2309a41d79d6fa586870b53e70c54965bf


d/control: gjs is needed at build-time even if not running tests

This source package only has one binary package, and it requires gjs,
so there would be no benefit to adjusting the upstream build system to
be able to build without gjs present.

Closes: #1061703


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1061703

Processed: Bug#1061703 marked as pending in gnome-characters

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1061703 [src:gnome-characters] gnome-characters nocheck FTBFS: 
../meson.build:47:14: ERROR: Program '/usr/bin/gjs-console' not found or not 
executable
Added tag(s) pending.

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

Bug#1066193: marked as done (adasockets: FTBFS: gnat1: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for Ada [-Werror])

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 17:49:40 +
with message-id 
and subject line Bug#1066193: fixed in adasockets 1.14-1
has caused the Debian Bug report #1066193,
regarding adasockets: FTBFS: gnat1: error: ‘-Werror=’ argument 
‘-Werror=implicit-function-declaration’ is not valid for Ada [-Werror]
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.)


-- 
1066193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adasockets
Version: 1.12-8
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):
>   /bin/bash ../libtool --tag=CC --mode=compile \
>   ../support/adacompiler gnatmake -v -j8 -R -eS  -cargs -g -O2 -Wall -Werror 
> -gnatag -gnatwa -gnatwe -gnatg -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection  -gno-record-gcc-switches -I. -I. 
> -largs -Wl,-z,relro -Wl,-z,now -Wl,--no-allow-shlib-undefined 
> -Wl,--no-copy-dt-needed-entries -Wl,--no-undefined -margs sockets-thin.ads; \
> fi
> gcc-12 -I. -o constants_nodef ./constants.c -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wl,-z,relro -Wl,-z,now -Wl,--no-allow-shlib-undefined 
> -Wl,--no-copy-dt-needed-entries -Wl,--no-undefined
> 
> GNATMAKE 12.3.0
> Copyright (C) 1992-2022, Free Software Foundation, Inc.
>   "split.ali" being checked ...
>   -> "split.ali" missing.
> x86_64-linux-gnu-gcc-12 -c -I./ -g -O2 -Wall -Werror -gnatag -gnatwa -gnatwe 
> -gnatg -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection -gno-record-gcc-switches -I. -I. -I- 
> ./split.adb
> gnat1: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is 
> not valid for Ada [-Werror]
> libtool: compile:  ../support/adacompiler gnatmake -v -j8 -R -eS -cargs -g 
> -O2 -Wall -Werror -gnatag -gnatwa -gnatwe -gnatg -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -fcf-protection 
> -gno-record-gcc-switches -I. -I. -largs -Wl,-z,relro -Wl,-z,now 
> -Wl,--no-allow-shlib-undefined -Wl,--no-copy-dt-needed-entries 
> -Wl,--no-undefined -margs sockets-utils.adb  -fPIC -DPIC -o 
> .libs/sockets-utils.o
> libtool: compile:  ../support/adacompiler gnatmake -v -j8 -R -eS -cargs -g 
> -O2 -Wall -Werror -gnatag -gnatwa -gnatwe -gnatg -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -fcf-protection 
> -gno-record-gcc-switches -I. -I. -largs -Wl,-z,relro -Wl,-z,now 
> -Wl,--no-allow-shlib-undefined -Wl,--no-copy-dt-needed-entries 
> -Wl,--no-undefined -margs sockets-stream_io.adb  -fPIC -DPIC -o 
> .libs/sockets-stream_io.o
> libtool: compile:  ../support/adacompiler gnatmake -v -j8 -R -eS -cargs -g 
> -O2 -Wall -Werror -gnatag -gnatwa -gnatwe -gnatg -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -fcf-protection 
> -gno-record-gcc-switches -I. -I. -largs -Wl,-z,relro -Wl,-z,now 
> -Wl,--no-allow-shlib-undefined -Wl,--no-copy-dt-needed-entries 
> -Wl,--no-undefined -margs sockets-link.ads  -fPIC -DPIC -o 
> .libs/sockets-link.o
> libtool: compile:  ../support/adacompiler gnatmake -v -j8 -R -eS -cargs -g 
> -O2 -Wall -Werror -gnatag -gnatwa -gnatwe -gnatg -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -fcf-protection 
> -gno-record-gcc-switches -I. -I. -largs -Wl,-z,relro -Wl,-z,now 
> -Wl,--no-allow-shlib-undefined -Wl,--no-copy-dt-needed-entries 
> -Wl,--no-undefined -margs sockets-types.ads  -fPIC -DPIC -o 
> .libs/sockets-types.o
> libtool: compile:  ../support/adacompiler gnatmake -v -j8 -R -eS -cargs -g 
> -O2 -Wall -Werror -gnatag -gnatwa -gnatwe -gnatg -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> 

Bug#1066485: [Debian-med-packaging] Bug#1066485: volpack: diff for NMU version 1.0b3-9.1

[Étienne Mollier]

Hi Andrey,

Andrey Rakhmatullin, on 2024-03-17:
> I've prepared an NMU for volpack (versioned as 1.0b3-9.1) and
> uploaded it to DELAYED/4. Please feel free to tell me if I
> should delay it longer.

Thank you for helping out with tackling these bugs, I reviewed
through your changes, with which I agree, and inlined them in
the VCS, so they will be preserved on further uploads.  Please
feel even free to reduce the delay to 0, if you like.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/4, please excuse my verbosity
   `-on air: Jean-Luc Ponty - Upon The Wings Of Music


signature.asc
Description: PGP signature

Processed: Bug#1066485 marked as pending in volpack

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066485 [src:volpack] volpack: FTBFS: scalevolume.c:63:9: error: implicit 
declaration of function ‘exit’ [-Werror=implicit-function-declaration]
Ignoring request to alter tags of bug #1066485 to the same tags previously set

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

Bug#1066485: marked as pending in volpack

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1066485 in volpack 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/med-team/volpack/-/commit/d85b54d6fb0c06207759da3510e70c218b8c7fa8


Fix FTBFS with -Werror=implicit-function-declaration

Closes: #1066485
Signed-off-by: Étienne Mollier 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066485

Processed: Bug#1066326 marked as pending in codonw

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066326 [src:codonw] codonw: FTBFS: codonW.h:38:74: error: implicit 
declaration of function ‘gets’; did you mean ‘fgets’? 
[-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1066326: marked as pending in codonw

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1066326 in codonw 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/med-team/codonw/-/commit/5fbba98d10658ec9d77cff7bb0743b1e38d5d3c6


remove-gets.patch: new: replace gets by fgets.

Closes: #1066326


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066326

Bug#1066581: marked as done (zh-autoconvert: FTBFS: judge.c:72:24: error: implicit declaration of function ‘j_code3’; did you mean ‘j_code’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 17:25:01 +
with message-id 
and subject line Bug#1066581: fixed in zh-autoconvert 0.3.16-10
has caused the Debian Bug report #1066581,
regarding zh-autoconvert: FTBFS: judge.c:72:24: error: implicit declaration of 
function ‘j_code3’; did you mean ‘j_code’? 
[-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.)


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

Hi,

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

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

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -fPIC -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -O2 
> -g -Wall -Iinclude -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> judge.c
> judge.c: In function ‘j_code’:
> judge.c:47:16: warning: pointer targets in assignment from ‘char *’ to 
> ‘unsigned char *’ differ in signedness [-Wpointer-sign]
>47 | for(phz=buff;phz<(buff+count);phz++){
>   |^
> judge.c:47:25: warning: comparison of distinct pointer types lacks a cast
>47 | for(phz=buff;phz<(buff+count);phz++){
>   | ^
> judge.c:72:24: error: implicit declaration of function ‘j_code3’; did you 
> mean ‘j_code’? [-Werror=implicit-function-declaration]
>72 | return j_code3(buff,count);
>   |^~~
>   |j_code
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:11: judge.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/zh-autoconvert_0.3.16-9_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: zh-autoconvert
Source-Version: 0.3.16-10
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
zh-autoconvert, 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 zh-autoconvert 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, 17 Mar 2024 12:32:32 -0400
Source: zh-autoconvert
Architecture: source
Version: 0.3.16-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Chinese Team 
Changed-By: Boyuan Yang 
Closes: 1066581
Changes:
 zh-autoconvert (0.3.16-10) unstable; urgency=medium
 .
   * Team upload.
   * debian/patches/0017-Make-function-definition-explicit.patch:
 Add patch to make function declarations explicit to avoid
 FTBFS. (Closes: #1066581)
Checksums-Sha1:
 129f633406f3bb4ff88efead29e73f0e9f05fcf5 2125 zh-autoconvert_0.3.16-10.dsc
 20d0b972f407dcac6522ded2cca69efbd2fbedf8 275360 
zh-autoconvert_0.3.16.orig.tar.gz
 a35e37448c7605dabc5bd44683af3f66eba50d25 20300 
zh-autoconvert_0.3.16-10.debian.tar.xz
 b493cb385bddc8ae8f7637e6d0bef9f4c0168184 7155 

Bug#1063492: marked as done (openvswitch: CVE-2023-3966: Invalid memory access in Geneve with HW offload)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 17:02:44 +
with message-id 
and subject line Bug#1063492: fixed in openvswitch 3.1.0-2+deb12u1
has caused the Debian Bug report #1063492,
regarding openvswitch: CVE-2023-3966: Invalid memory access in Geneve with HW 
offload
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.)


-- 
1063492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openvswitch
Version: 3.3.0~git20240118.e802fe7-3
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 3.1.0-2

Hi,

The following vulnerability was published for openvswitch.

CVE-2023-3966[0]:
| Invalid memory access in Geneve with HW offload


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-3966
https://www.cve.org/CVERecord?id=CVE-2023-3966
[1] https://www.openwall.com/lists/oss-security/2024/02/08/3
[2] https://mail.openvswitch.org/pipermail/ovs-dev/2024-February/411702.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: openvswitch
Source-Version: 3.1.0-2+deb12u1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated openvswitch 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: Sun, 18 Feb 2024 16:46:26 +0100
Source: openvswitch
Architecture: source
Version: 3.1.0-2+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1063492
Changes:
 openvswitch (3.1.0-2+deb12u1) bookworm-security; urgency=medium
 .
   * CVE-2023-5366: A flaw was found in Open vSwitch that allows ICMPv6 Neighbor
 Advertisement packets between virtual machines to bypass OpenFlow rules.
 This issue may allow a local attacker to create specially crafted packets
 with a modified or spoofed target IP address field that can redirect ICMPv6
 traffic to arbitrary IP addresses. Added upstream patch: "Fix missing masks
 on a final stage with ports trie".
   * CVE-2023-3966: Invalid memory access in Geneve with HW offload. Added
 upstream patch: netdev-offload-tc: Check geneve metadata length
 (Closes: #1063492).
Checksums-Sha1:
 6fddff647c4124aa3e34552fb523ee4632c95a42 3559 openvswitch_3.1.0-2+deb12u1.dsc
 f1fd1f728cbf71894c752b546cd3c27d57ebaebe 4847692 openvswitch_3.1.0.orig.tar.xz
 6e6cbffad704d727e6b3e4b05dd83a1be765f62d 74096 
openvswitch_3.1.0-2+deb12u1.debian.tar.xz
 8b24eaa8734c78d1bc87330092ecaa365a95334e 25342 
openvswitch_3.1.0-2+deb12u1_amd64.buildinfo
Checksums-Sha256:
 22ca1b4ea0ac2e00c6d017aeb3fc16a2d1e381338414960011543ee2a16a9b4a 3559 
openvswitch_3.1.0-2+deb12u1.dsc
 c56c34e37058ce4dd131733b0b24c9b557b0d0ee092a9786739b51f5e906a297 4847692 
openvswitch_3.1.0.orig.tar.xz
 a73be9099e7014117cc7625711efeed1e0b90c2cef3a3341f146cfb7ce37df8d 74096 
openvswitch_3.1.0-2+deb12u1.debian.tar.xz
 301974eaed1bee652b6b4a53c48be3638e8ac72b3b4c495e2cad5ea06bfce1fd 25342 
openvswitch_3.1.0-2+deb12u1_amd64.buildinfo
Files:
 8fcf6e716a9c556bfbebc93bdfd86f4b 3559 net optional 
openvswitch_3.1.0-2+deb12u1.dsc
 45a3b182b9cbf6d9c98c76c0026a65d6 4847692 net optional 
openvswitch_3.1.0.orig.tar.xz
 5cbf3df575d6aaa567c28c3c4b67c47e 74096 net optional 
openvswitch_3.1.0-2+deb12u1.debian.tar.xz
 b88ccade8d141cc34354dac8bec9c9f2 25342 net optional 
openvswitch_3.1.0-2+deb12u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmXxu3YACgkQ1BatFaxr
Q/6hSg//QPjYGfVAu1TvYCU2jFEJV5M3jvGj2J16OM5jmciYxmgkQNoritawmWaC
EYMixP/rEcuX2tA5PUxTnoa6/qd999rZOOamffwocEt/jTcuoyac1jpVeRwb3+Dr
OjU/gXTCPxyfJFeDVSez2Pb42Ff17xaq/aFfWdyO+aeE2SBTpFB0fimouqmNjvd0

Bug#1063484: marked as done (libuv1: CVE-2024-24806)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 17:02:40 +
with message-id 
and subject line Bug#1063484: fixed in libuv1 1.44.2-1+deb12u1
has caused the Debian Bug report #1063484,
regarding libuv1: CVE-2024-24806
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.)


-- 
1063484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libuv1
Version: 1.46.0-3
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libuv1.

CVE-2024-24806[0]:
| libuv is a multi-platform support library with a focus on
| asynchronous I/O. The `uv_getaddrinfo` function in
| `src/unix/getaddrinfo.c` (and its windows counterpart
| `src/win/getaddrinfo.c`), truncates hostnames to 256 characters
| before calling `getaddrinfo`. This behavior can be exploited to
| create addresses like `0x7f01`, which are considered valid
| by `getaddrinfo` and could allow an attacker to craft payloads that
| resolve to unintended IP addresses, bypassing developer checks. The
| vulnerability arises due to how the `hostname_ascii` variable (with
| a length of 256 bytes) is handled in `uv_getaddrinfo` and
| subsequently in `uv__idna_toascii`. When the hostname exceeds 256
| characters, it gets truncated without a terminating null byte. As a
| result attackers may be able to access internal APIs or for websites
| (similar to MySpace) that allows users to have
| `username.example.com` pages. Internal services that crawl or cache
| these user pages can be exposed to SSRF attacks if a malicious user
| chooses a long vulnerable username. This issue has been addressed in
| release version 1.48.0. Users are advised to upgrade. There are no
| known workarounds for this vulnerability.

Note, that the advisory at [1] mentions that affected versions are
only > 1.45.x. Looking at the git changes, is it not introduced after
6dd44caa35b4 ("unix,win: support IDNA 2008 in uv_getaddrinfo()") in
v1.24.0?

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-24806
https://www.cve.org/CVERecord?id=CVE-2024-24806
[1] https://github.com/libuv/libuv/security/advisories/GHSA-f74f-cvh7-c6q6

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libuv1
Source-Version: 1.44.2-1+deb12u1
Done: Dominique Dumont 

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

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated libuv1 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, 20 Feb 2024 18:28:54 +0100
Source: libuv1
Architecture: source
Version: 1.44.2-1+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: Dominique Dumont 
Changed-By: Dominique Dumont 
Closes: 1063484
Changes:
 libuv1 (1.44.2-1+deb12u1) bookworm-security; urgency=medium
 .
   * add patch to fix CVE-2024-24806 (Closes: 1063484)
Checksums-Sha1:
 9588ae6ca442e22acaec2475194ec189901f9d4f 2029 libuv1_1.44.2-1+deb12u1.dsc
 ced06e69586ea4b3be56c2cc67caa5dc1718a70c 1308776 libuv1_1.44.2.orig.tar.gz
 5061d77c2055b183b1bc3640f3f53eb9c24c53dd 21460 
libuv1_1.44.2-1+deb12u1.debian.tar.xz
 3d8acd17328c4b9935cca168e7bec194226fc46e 8840 
libuv1_1.44.2-1+deb12u1_source.buildinfo
Checksums-Sha256:
 798be0a2bcbcd40bb85302f6ccbf02b240e1958d4ad9cf153b8101c3a82f21b9 2029 
libuv1_1.44.2-1+deb12u1.dsc
 d79b4b06ef04be85fb890bf39d55942cc64c2e15fd14eaa32dae5dce94485484 1308776 
libuv1_1.44.2.orig.tar.gz
 14fc605e7d1520137416fd8c097b58a191be9b07bdbb406f7b39c7894b7d66a5 21460 
libuv1_1.44.2-1+deb12u1.debian.tar.xz
 6729f56c1a50bcf954f70ab4016e1c44047af50707e283e83d9d79b8651e70ac 8840 
libuv1_1.44.2-1+deb12u1_source.buildinfo
Files:
 24577671198dca02c1a0da01b977dd35 2029 libs optional libuv1_1.44.2-1+deb12u1.dsc
 

Bug#1064139: ogre-1.12: FTBFS: error: ‘BuildFontAtlas’ is not a member of ‘ImGuiFreeType’

[Flavien Bridault]

Mmm this is weird, I got it built completely with the latest unstable 
docker image, thus with swig 4.2... What could be the difference?


I'll try with cowbuilder now...


*Dr. Flavien BRIDAULT*
Director of Software Development
IRCAD France & IRCAD Africa

flavien.brida...@ircad.fr 
Tél. : +33 (0)3 88 119 201
IRCAD France
http://www.ircad.fr/
http://www.ircad.africa/ 

Suivez l'IRCAD sur Facebook 



*IRCAD France*
Hôpitaux Universitaires - 1, place de l'Hôpital - 67091 Strasbourg Cedex 
- FRANCE


Le 17/03/2024 à 16:05, Matthias Klose a écrit :

On 17.03.24 14:59, Matthias Klose wrote:

with both patches, I get until:

/home/packages/tmp/x/ogre-1.12-1.12.10+dfsg2/obj-x86_64-linux-gnu/Components/Python/CMakeFiles/_ 

Overlay.dir/OgreOverlayPYTHON_wrap.cxx:6527:56: error: expected 
template-name before '<' token
  6527 | struct SwigPyMapIterator_T : 
SwigPyIteratorClosed_T
 >
   | ^
/home/packages/tmp/x/ogre-1.12-1.12.10+dfsg2/obj-x86_64-linux-gnu/Components/Python/CMakeFiles/_ 

Overlay.dir/OgreOverlayPYTHON_wrap.cxx:6527:56: error: expected '{' 
before '<' token


[...]

/home/packages/tmp/x/ogre-1.12-1.12.10+dfsg2/obj-x86_64-linux-gnu/Components/Python/CMakeFiles/_Overlay.dir/OgreOverlayPYTHON_wrap.cxx:6547:12: 
error: 'SwigPyIterator' does not name a type; did you mean 
'SwigPyMapIterator_T'?

  6547 | inline SwigPyIterator*
   |    ^~
   |    SwigPyMapIterator_T
/home/packages/tmp/x/ogre-1.12-1.12.10+dfsg2/obj-x86_64-linux-gnu/Components/Python/CMakeFiles/_Overlay.dir/OgreOverlayPYTHON_wrap.cxx:6565:12: 
error: 'SwigPyIterator' does not name a type; did you mean 
'SwigPyMapIterator_T'?

  6565 | inline SwigPyIterator*
   |    ^~
   |    SwigPyMapIterator_T



this is introduced by swig 4.2.x, builds with wig 4.1.x



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066485: volpack: diff for NMU version 1.0b3-9.1

[Andrey Rakhmatullin]

Control: tags 1066485 + patch
Control: tags 1066485 + pending

Dear maintainer,

I've prepared an NMU for volpack (versioned as 1.0b3-9.1) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
WBR, wRAR
diff -Nru volpack-1.0b3/debian/changelog volpack-1.0b3/debian/changelog
--- volpack-1.0b3/debian/changelog	2020-08-28 09:42:35.0 +0500
+++ volpack-1.0b3/debian/changelog	2024-03-17 21:32:58.0 +0500
@@ -1,3 +1,10 @@
+volpack (1.0b3-9.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066485).
+
+ -- Andrey Rakhmatullin   Sun, 17 Mar 2024 21:32:58 +0500
+
 volpack (1.0b3-9) unstable; urgency=medium
 
   * Test-Depends: build-essential
diff -Nru volpack-1.0b3/debian/patches/fix-implicit-function-declaration.patch volpack-1.0b3/debian/patches/fix-implicit-function-declaration.patch
--- volpack-1.0b3/debian/patches/fix-implicit-function-declaration.patch	1970-01-01 05:00:00.0 +0500
+++ volpack-1.0b3/debian/patches/fix-implicit-function-declaration.patch	2024-03-17 21:32:58.0 +0500
@@ -0,0 +1,104 @@
+Description: Add missing header includes and prototypes.
+Author: Andrey Rakhmatullin 
+Bug-Debian: https://bugs.debian.org/1066485
+Last-Update: 2024-03-17
+
+Index: volpack-1.0b3/examples/scalevolume.c
+===
+--- volpack-1.0b3.orig/examples/scalevolume.c
 volpack-1.0b3/examples/scalevolume.c
+@@ -38,6 +38,10 @@
+ #include 
+ #include 
+ #include 
++#include 
++#include 
++
++int write_den(char* filename, unsigned char* data, int xlen, int ylen, int zlen);
+ 
+ main(argc, argv)
+ int argc;
+Index: volpack-1.0b3/examples/rendervolume.c
+===
+--- volpack-1.0b3.orig/examples/rendervolume.c
 volpack-1.0b3/examples/rendervolume.c
+@@ -29,8 +29,13 @@
+  */
+ 
+ #include 
++#include 
++#include 
++#include 
+ #include "volume.h"
+ 
++int StorePGM(char* image, int width, int height, char* filename);
++
+ main(argc, argv)
+ int argc;
+ char **argv;
+Index: volpack-1.0b3/examples/denfile.c
+===
+--- volpack-1.0b3.orig/examples/denfile.c
 volpack-1.0b3/examples/denfile.c
+@@ -6,6 +6,9 @@
+  */
+ 
+ #include 
++#include 
++#include 
++#include 
+ 
+ #ifndef MIN
+ #define MIN(a, b) ((a) > (b) ? (b) : (a))
+@@ -17,6 +20,11 @@
+ 
+ #define MAX_READ_SIZE	8192	/* maximum # of bytes per read(2) call */
+ 
++int read_shorts(int fd, short* sbuf, int shortcount, int swap);
++int read_words(int fd, int* wbuf, int wordcount, int swap);
++int read_bytes(int fd, char* buf, int bytecount);
++int write_bytes(int fd, char* buf, int bytecount);
++
+ /*
+  * read_den
+  *
+Index: volpack-1.0b3/examples/classifyvolume.c
+===
+--- volpack-1.0b3.orig/examples/classifyvolume.c
 volpack-1.0b3/examples/classifyvolume.c
+@@ -29,6 +29,9 @@
+  */
+ 
+ #include 
++#include 
++#include 
++#include 
+ #include "volume.h"
+ 
+ main(argc, argv)
+Index: volpack-1.0b3/examples/makeoctree.c
+===
+--- volpack-1.0b3.orig/examples/makeoctree.c
 volpack-1.0b3/examples/makeoctree.c
+@@ -29,6 +29,8 @@
+  */
+ 
+ #include 
++#include 
++#include 
+ #include "volume.h"
+ 
+ main()
+Index: volpack-1.0b3/examples/makevolume.c
+===
+--- volpack-1.0b3.orig/examples/makevolume.c
 volpack-1.0b3/examples/makevolume.c
+@@ -29,6 +29,8 @@
+  */
+ 
+ #include 
++#include 
++#include 
+ #include "volume.h"
+ 
+ main()
diff -Nru volpack-1.0b3/debian/patches/series volpack-1.0b3/debian/patches/series
--- volpack-1.0b3/debian/patches/series	2020-08-28 09:42:35.0 +0500
+++ volpack-1.0b3/debian/patches/series	2024-03-17 21:32:58.0 +0500
@@ -1,3 +1,4 @@
 10_examples.patch
 10_vp_global_h.patch
 fixmanpages.patch
+fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Processed: volpack: diff for NMU version 1.0b3-9.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1066485 + patch
Bug #1066485 [src:volpack] volpack: FTBFS: scalevolume.c:63:9: error: implicit 
declaration of function ‘exit’ [-Werror=implicit-function-declaration]
Added tag(s) patch.
> tags 1066485 + pending
Bug #1066485 [src:volpack] volpack: FTBFS: scalevolume.c:63:9: error: implicit 
declaration of function ‘exit’ [-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1067018: lnav: FTBFS on arm{el,hf}: test failures

[Salvatore Bonaccorso]

Hi Sebastian,

On Sat, Mar 16, 2024 at 11:34:23PM +0100, Sebastian Ramacher wrote:
> Source: lnav
> Version: 0.11.2-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=lnav=armhf=0.11.2-1%2Bb1=1710618595=0
> 
> 
> 2024-03-16T19:49:36+00:00 
> ␛[0;35m=␛[0m
> ␛[0;35mCommand␛[0m: test: env TEST_COMMENT=parse_url1 ./drive_sql
> ␛[0;32mBEGIN␛[0m 
> test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.out
> ␛[0;32mEND␛[0m   
> test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.out
> OUT: test: env TEST_COMMENT=parse_url1 ./drive_sql
> --- 
> /<>/test/expected/test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.out
>   2023-07-03 04:16:02.0 +
> +++ test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.out 
> 2024-03-16 19:49:36.550940820 +
> @@ -1,2 +0,0 @@
> -Row 0:
> -  Column parse_url('https://example.com'): 
> {"scheme":"https","user":null,"password":null,"host":"example.com","port":null,"path":"/","query":null,"parameters":null,"fragment":null}
> FAIL! EXPECTED OUT DIFF
> ␛[0;31mBEGIN␛[0m 
> test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.err
> error: sqlite3_exec failed -- misuse of sqlite3_result_subtype() by 
> parse_url()
> ␛[0;31mEND␛[0m   
> test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.err
> ERR: test: env TEST_COMMENT=parse_url1 ./drive_sql
> --- 
> /<>/test/expected/test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.err
>   2023-07-03 04:16:02.0 +
> +++ test_sql_str_func.sh_b088735cf46f23ca3d5fb3da41f07a6a3b1cba35.err 
> 2024-03-16 19:49:36.558940841 +
> @@ -0,0 +1 @@
> +error: sqlite3_exec failed -- misuse of sqlite3_result_subtype() by 
> parse_url()
> FAIL! EXPECTED ERR DIFF
> 
> 2024-03-16T19:49:36+00:00 
> ␛[0;35m=␛[0m
> ␛[0;35mCommand␛[0m: test: env TEST_COMMENT=parse_url2 ./drive_sql
> ␛[0;32mBEGIN␛[0m 
> test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.out
> ␛[0;32mEND␛[0m   
> test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.out
> OUT: test: env TEST_COMMENT=parse_url2 ./drive_sql
> --- 
> /<>/test/expected/test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.out
>   2023-07-03 04:16:02.0 +
> +++ test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.out 
> 2024-03-16 19:49:36.662941118 +
> @@ -1,2 +0,0 @@
> -Row 0:
> -  Column parse_url('https://example.com/'): 
> {"scheme":"https","user":null,"password":null,"host":"example.com","port":null,"path":"/","query":null,"parameters":null,"fragment":null}
> FAIL! EXPECTED OUT DIFF
> ␛[0;31mBEGIN␛[0m 
> test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.err
> error: sqlite3_exec failed -- misuse of sqlite3_result_subtype() by 
> parse_url()
> ␛[0;31mEND␛[0m   
> test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.err
> ERR: test: env TEST_COMMENT=parse_url2 ./drive_sql
> --- 
> /<>/test/expected/test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.err
>   2023-07-03 04:16:02.0 +
> +++ test_sql_str_func.sh_0947bfe7ec626eaa0409a45b10fcbb634fb12eb7.err 
> 2024-03-16 19:49:36.674941150 +
> @@ -0,0 +1 @@
> +error: sqlite3_exec failed -- misuse of sqlite3_result_subtype() by 
> parse_url()
> FAIL! EXPECTED ERR DIFF
> 
> 2024-03-16T19:49:36+00:00 
> ␛[0;35m=␛[0m
> ␛[0;35mCommand␛[0m: test: env TEST_COMMENT=parse_url3 ./drive_sql
> ␛[0;32mBEGIN␛[0m 
> test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.out
> ␛[0;32mEND␛[0m   
> test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.out
> OUT: test: env TEST_COMMENT=parse_url3 ./drive_sql
> --- 
> /<>/test/expected/test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.out
>   2023-07-03 04:16:02.0 +
> +++ test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.out 
> 2024-03-16 19:49:36.778941428 +
> @@ -1,2 +0,0 @@
> -Row 0:
> -  Column parse_url('https://example.com/search?flag'): 
> {"scheme":"https","user":null,"password":null,"host":"example.com","port":null,"path":"/search","query":"flag","parameters":{"flag":null},"fragment":null}
> FAIL! EXPECTED OUT DIFF
> ␛[0;31mBEGIN␛[0m 
> test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.err
> error: sqlite3_exec failed -- misuse of sqlite3_result_subtype() by 
> parse_url()
> ␛[0;31mEND␛[0m   
> test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.err
> ERR: test: env TEST_COMMENT=parse_url3 ./drive_sql
> --- 
> /<>/test/expected/test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.err
>   2023-07-03 04:16:02.0 +
> +++ test_sql_str_func.sh_bac7f6531a2adf70cd1871fb13eab26dff133b7c.err 
> 2024-03-16 19:49:36.790941460 +
> @@ 

Bug#1067045: marked as done (libsendmail-pmilter-perl: Includes non-free document)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 16:50:01 +
with message-id 
and subject line Bug#1067045: fixed in libsendmail-pmilter-perl 1.00-1.3
has caused the Debian Bug report #1067045,
regarding libsendmail-pmilter-perl: Includes non-free document
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.)


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

Source: libsendmail-pmilter-perl
Version: 1.00-1
Severity: serious

The source package includes the non-free milter-protocol.txt that is claimed to 
be excluded in README.Debian.
--- End Message ---
--- Begin Message ---
Source: libsendmail-pmilter-perl
Source-Version: 1.00-1.3
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
libsendmail-pmilter-perl, 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.
Bastian Germann  (supplier of updated libsendmail-pmilter-perl 
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, 17 Mar 2024 15:27:27 +
Source: libsendmail-pmilter-perl
Architecture: source
Version: 1.00-1.3
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Bastian Germann 
Closes: 1007675 1067045
Changes:
 libsendmail-pmilter-perl (1.00-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Convert source to format 3.0.
 (Closes: #1007675)
   * d/copyright: Convert to machine-readable format.
   * Exclude non-free document according to README.Debian.
 (Closes: #1067045)
Checksums-Sha1:
 32f70e01ec110401294b4eac232965925518e507 1691 
libsendmail-pmilter-perl_1.00-1.3.dsc
 9128106ca4991308bac518f891a4c53267e438f0 21924 
libsendmail-pmilter-perl_1.00.orig.tar.xz
 e17cae867aa9034e94c7bdd57da932c10829eda8 4640 
libsendmail-pmilter-perl_1.00-1.3.debian.tar.xz
 fa94d0cafaed673778a88b6a3caf571459853d1d 6140 
libsendmail-pmilter-perl_1.00-1.3_source.buildinfo
Checksums-Sha256:
 f2e6f0b126d86ce35d594f76c0172a6137cf1a37754e070e92124b63a1445bb1 1691 
libsendmail-pmilter-perl_1.00-1.3.dsc
 b2f5d8c81294df3114e7b2b69f4b1646c47a44e7af7cbf6b446a591bdce5e5ea 21924 
libsendmail-pmilter-perl_1.00.orig.tar.xz
 c057703b0fd595211e55243a2c687cca393008d2ad7410f53d2d694d58e841b3 4640 
libsendmail-pmilter-perl_1.00-1.3.debian.tar.xz
 67f8068e8bafbed1b7a0290ea460a1023551a5b66d225f35441609160c0515e2 6140 
libsendmail-pmilter-perl_1.00-1.3_source.buildinfo
Files:
 5e63650fcb6a722b63e1bf6eda5f8185 1691 perl optional 
libsendmail-pmilter-perl_1.00-1.3.dsc
 fd857a9ab6d9d0644a2fb0f797993821 21924 perl optional 
libsendmail-pmilter-perl_1.00.orig.tar.xz
 e1fad6c35973ef360e5716faa20a2a05 4640 perl optional 
libsendmail-pmilter-perl_1.00-1.3.debian.tar.xz
 67b41cbb13c46e0c7d5d98833c9b5cce 6140 perl optional 
libsendmail-pmilter-perl_1.00-1.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmX3GScQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFCL3DACht04V+vJsRoVjupOhSwAjc47tNevPzxPM
M3CWIxY4wX/gSg8SuE1N3sP2pPpM/lvPX84S7wMiJUpbPLtCnC2fK/EJpBK4AZkd
VZ6rvKSUdMOSYCrNoV1bdhuzSCavPr5F/aesUDNkx12c8OqJ+8a2mxDhSyv54vdK
9hCs8zPcY/qXLi1oT47dhG8DfMgY/S8hH5oWN1L6FCId3gufb2ceVSnWZjrhE0qp
iubAn5lVjEPEVHCKYlsed+uPEC4Xmbu4GhsehzX0Z5BzSFTaibL7qVQRYXhjlpnR
3PDJoGtLWHWQVaxDY2uAEDKKOIwhLvjYpUU7J6axYVD/yCMjnbtKu68eNfozplxy
4SUBxQ53m66k57B4dR7rcRNEs6TOzbRTDMBRvl7x52lKchIAektX32kBbYqAcVgh
Jok06mS0HeWqn74xV+uvGtr8aI+9U+IU40HsuAtvX0c17cXEB2t4l7+vJlvFYUap
gJSOjXmdvdKaIxtp94M6tjQ1wavjqSQ=
=8VK9
-END PGP SIGNATURE-



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

Bug#1065000: marked as done (pgpool2: the package fails to build on armhf due to gcc-13 13.2.0-16.1 changes)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 17:35:21 +0100
with message-id 
and subject line Re: Bug#1065000: pgpool2: the package fails to build on armhf 
due to gcc-13 13.2.0-16.1 changes
has caused the Debian Bug report #1065000,
regarding pgpool2: the package fails to build on armhf due to gcc-13 
13.2.0-16.1 changes
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.)


-- 
1065000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgpool2
Version: 4.3.7-1
Severity: serious

Dear Maintainer,

armhf has -Werror=implicit-function-declaration enabled in default gcc flags of
gcc-13 13.2.0-16.1.

pgpool2 has a number of implicit function declarations causing the build
failure[1]

[1] https://launchpadlibrarian.net/716403848/buildlog_ubuntu-noble-
armhf.pgpool2_4.3.7-1ubuntu1_BUILDING.txt.gz


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

Kernel: Linux 6.5.0-21-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 4.3.7-2

Re: To Vladimir Petko
> Re: Vladimir Petko
> > armhf has -Werror=implicit-function-declaration enabled in default gcc 
> > flags of
> > gcc-13 13.2.0-16.1.
> 
> Huh, why only on armhf? That makes debugging this a bit hard.
> 
> >   Would it be possible to consider a merge request[1] that addresses this 
> > issue?
> 
> I'm looking now.

This was fixed in the last upload, but didn't make it into the
changelog.

Thanks,
Christoph--- End Message ---

Processed: Bug#1065000 marked as pending in pgpool2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1065000 [src:pgpool2] pgpool2: the package fails to build on armhf due to 
gcc-13 13.2.0-16.1 changes
Added tag(s) pending.

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

Bug#1067047: Buildng the package removes debian/.gitlab-ci.yml

[Andrey Rahmatullin]

Source: gnucash
Version: 1:5.5-1.1
Severity: serious

Simply build the package from source produces a source package that doesn't
contain debian/.gitlab-ci.yml in debian.tar, one needs to rebuild the source
package separately, skipping the clean target. The reason for that is that the
file is listed debian/clean for some reason (alternatively, if it shouldn't be
in the package, please remove it from the package).


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

Bug#1065000: marked as pending in pgpool2

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #1065000 in pgpool2 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/pgpool2/-/commit/0d80c3f9759b682f88740570efce1a59636a8b61


fix -Werror=implicit-function-declaration errors. (Closes: #1065000)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065000

Processed: severity of 1062567 is important

[Debian Bug Tracking System]

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

> severity 1062567 important
Bug #1062567 [src:libpg-query] libpg-query: NMU diff for 64-bit time_t 
transition
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1066245: gnucash: diff for NMU version 1:5.5-1.2

[Andrey Rakhmatullin]

Control: tags 1066245 + patch
Control: tags 1066245 + pending

Dear maintainer,

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

Regards.


-- 
WBR, wRAR
diff -Nru gnucash-5.5/debian/changelog gnucash-5.5/debian/changelog
--- gnucash-5.5/debian/changelog	2024-02-23 22:55:23.0 +0500
+++ gnucash-5.5/debian/changelog	2024-03-17 20:39:48.0 +0500
@@ -1,3 +1,10 @@
+gnucash (1:5.5-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066245).
+
+ -- Andrey Rakhmatullin   Sun, 17 Mar 2024 20:39:48 +0500
+
 gnucash (1:5.5-1.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru gnucash-5.5/debian/patches/fix-implicit-function-declaration.patch gnucash-5.5/debian/patches/fix-implicit-function-declaration.patch
--- gnucash-5.5/debian/patches/fix-implicit-function-declaration.patch	1970-01-01 05:00:00.0 +0500
+++ gnucash-5.5/debian/patches/fix-implicit-function-declaration.patch	2024-03-17 20:39:48.0 +0500
@@ -0,0 +1,18 @@
+Description: Add missing header includes.
+Author: Andrey Rakhmatullin 
+Bug-Debian: https://bugs.debian.org/1066245
+Last-Update: 2024-03-17
+
+Index: gnucash-5.5/bindings/python/sqlite3test.c
+===
+--- gnucash-5.5.orig/bindings/python/sqlite3test.c
 gnucash-5.5/bindings/python/sqlite3test.c
+@@ -20,6 +20,8 @@
+ 
+ #include 
+ #include "qofsession.h"
++#include "qoflog.h"
++#include "gnc-engine.h"
+ #define TESTFILE "/tmp/blah.gnucash"
+ int main()
+ {
diff -Nru gnucash-5.5/debian/patches/series gnucash-5.5/debian/patches/series
--- gnucash-5.5/debian/patches/series	2024-02-23 22:55:23.0 +0500
+++ gnucash-5.5/debian/patches/series	2024-03-17 20:39:48.0 +0500
@@ -1,3 +1,4 @@
 build-flags.patch
 
 #t-skip--python-bindings.patch
+fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Processed: gnucash: diff for NMU version 1:5.5-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1066245 + patch
Bug #1066245 [src:gnucash] gnucash: FTBFS: sqlite3test.c:30:5: error: implicit 
declaration of function ‘qof_log_init’ [-Werror=implicit-function-declaration]
Added tag(s) patch.
> tags 1066245 + pending
Bug #1066245 [src:gnucash] gnucash: FTBFS: sqlite3test.c:30:5: error: implicit 
declaration of function ‘qof_log_init’ [-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Processed: bug 1066275 is forwarded to https://github.com/rlancaste/stellarsolver/issues/125

[Debian Bug Tracking System]

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

> forwarded 1066275 https://github.com/rlancaste/stellarsolver/issues/125
Bug #1066275 [src:stellarsolver] stellarsolver: FTBFS: os-features.h:123:17: 
error: implicit declaration of function ‘qsort_r’; did you mean ‘qsort’? 
[-Werror=implicit-function-declaration]
Set Bug forwarded-to-address to 
'https://github.com/rlancaste/stellarsolver/issues/125'.
> thanks
Stopping processing here.

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

Bug#1066636: marked as done (surf-alggeo: FTBFS: polyyacc.c:1703:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 16:08:13 +
with message-id 
and subject line Bug#1066636: fixed in surf-alggeo 1.0.6+ds-7
has caused the Debian Bug report #1066636,
regarding surf-alggeo: FTBFS: polyyacc.c:1703:16: error: implicit declaration 
of function ‘yylex’ [-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.)


-- 
1066636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: surf-alggeo
Version: 1.0.6+ds-6
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=\"surf\" -DPACKAGE_TARNAME=\"surf\" 
> -DPACKAGE_VERSION=\"1.0.6\" -DPACKAGE_STRING=\"surf\ 1.0.6\" 
> -DPACKAGE_BUGREPORT=\"endr...@mathematik.uni-mainz.de\" -DPACKAGE_URL=\"\" 
> -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 -DHAVE_WCHAR_H=1 -DSTDC_HEADERS=1 -D_ALL_SOURCE=1 
> -D_DARWIN_C_SOURCE=1 -D_GNU_SOURCE=1 -D_HPUX_ALT_XOPEN_SOCKET_API=1 
> -D_NETBSD_SOURCE=1 -D_OPENBSD_SOURCE=1 -D_POSIX_PTHREAD_SEMANTICS=1 
> -D__STDC_WANT_IEC_60559_ATTRIBS_EXT__=1 -D__STDC_WANT_IEC_60559_BFP_EXT__=1 
> -D__STDC_WANT_IEC_60559_DFP_EXT__=1 -D__STDC_WANT_IEC_60559_FUNCS_EXT__=1 
> -D__STDC_WANT_IEC_60559_TYPES_EXT__=1 -D__STDC_WANT_LIB_EXT2__=1 
> -D__STDC_WANT_MATH_SPEC_FUNCS__=1 -D_TANDEM_SOURCE=1 -D__EXTENSIONS__=1 
> -DPACKAGE=\"surf\" -DVERSION=\"1.0.6\" -DYYTEXT_POINTER=1 -DHAVE_DLFCN_H=1 
> -DLT_OBJDIR=\".libs/\" -DHAVE_INSTANTIATIONS=/\*\*/ 
> -DHAVE_FUNCTION_NONTYPE_PARAMETERS=/\*\*/ -DHAVE_PTHREAD_PRIO_INHERIT=1 
> -D_REENTRANT=1 -DNO_GUI=1 -DHAVE_PROGRAM_INVOCATION_SHORT_NAME=1 -I. 
> -I../../../yaccsrc  -I../../../src -I../../../curve -I../../../drawfunc 
> -I../../../draw -I../../../dither -I../../../image-formats -I../../../yaccsrc 
> -I../../../mt -I../../../misc -I../../../debug -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 -O3 
> -Wall -W -Wwrite-strings -Wpointer-arith -Wconversion -Wno-unused 
> -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations 
> -Wnested-externs -c -o libsurf_parser_a-polyyacc.o `test -f 'polyyacc.c' || 
> echo '../../../yaccsrc/'`polyyacc.c
> polyyacc.c: In function ‘yyparse’:
> polyyacc.c:1703:16: error: implicit declaration of function ‘yylex’ 
> [-Werror=implicit-function-declaration]
>  1703 |   yychar = yylex ();
>   |^
> polyyacc.c:1703:16: warning: nested extern declaration of ‘yylex’ 
> [-Wnested-externs]
> ../../../yaccsrc/polyyacc.y:474:57: warning: conversion from ‘size_t’ {aka 
> ‘long unsigned int’} to ‘int’ may change value [-Wconversion]
>   474 | $$ = new_char( len + 1 );
>   | ~   ^  
> ../../../yaccsrc/polyyacc.y:495:60: warning: conversion from ‘size_t’ {aka 
> ‘long unsigned int’} to ‘int’ may change value [-Wconversion]
>   495 | $$ = new_char( length + 1 );
>   |    ^  
> ../../../yaccsrc/polyyacc.y:506:60: warning: conversion from ‘size_t’ {aka 
> ‘long unsigned int’} to ‘int’ may change value [-Wconversion]
>   506 | $$ = new_char( length + 1 );
>   |    ^  
> ../../../yaccsrc/polyyacc.y:518:75: warning: comparison of integer 
> expressions of different signedness: ‘int’ and ‘size_t’ {aka ‘long unsigned 
> int’} [-Wsign-compare]
>   518 | if( $3 > 50 || $3 < length )
>   |   
> ^
> ../../../yaccsrc/polyyacc.y:525:59: warning: conversion to ‘size_t’ {aka 
> ‘long unsigned int’} from ‘int’ may change the sign of the result 
> [-Wsign-conversion]
>   525 | zeroes = $3 - length;
>   | 

Bug#1065815: marked as done (racket-doc: missing Breaks+Replaces: racket-common (<< 8.12))

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 16:07:49 +
with message-id 
and subject line Bug#1065815: fixed in racket 8.12+dfsg1-5
has caused the Debian Bug report #1065815,
regarding racket-doc: missing Breaks+Replaces: racket-common (<< 8.12)
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.)


-- 
1065815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: racket-doc
Version: 8.12+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid' installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../racket-doc_8.12+dfsg1-1_all.deb ...
  Unpacking racket-doc (8.12+dfsg1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/racket-doc_8.12+dfsg1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/racket/release/Draw_and_GUI_5_1.txt.gz', 
which is also in package racket-common 8.10+dfsg1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/racket-doc_8.12+dfsg1-1_all.deb

The conflictig files are:

usr/share/doc/racket/release/Draw_and_GUI_5_1.txt.gz
usr/share/doc/racket/release/HISTORY.txt.gz
usr/share/doc/racket/release/HISTORY_10.txt.gz
usr/share/doc/racket/release/HISTORY_11.txt.gz
usr/share/doc/racket/release/HISTORY_2.txt.gz
usr/share/doc/racket/release/HISTORY_3.txt.gz
usr/share/doc/racket/release/HISTORY_4.txt.gz
usr/share/doc/racket/release/HISTORY_5.txt
usr/share/doc/racket/release/HISTORY_6.txt.gz
usr/share/doc/racket/release/HISTORY_7.txt
usr/share/doc/racket/release/HISTORY_8.txt
usr/share/doc/racket/release/HISTORY_9.txt.gz
usr/share/doc/racket/release/MrEd_100.txt.gz
usr/share/doc/racket/release/MrEd_100_Framework.txt.gz
usr/share/doc/racket/release/MzScheme_200.txt.gz
usr/share/doc/racket/release/MzScheme_300.txt.gz
usr/share/doc/racket/release/MzScheme_4.txt.gz
usr/share/doc/racket/release/Racket_5.txt
usr/share/doc/racket/release/blueboxes.rktd
usr/share/doc/racket/release/index.html
usr/share/doc/racket/release/out0.sxref
usr/share/doc/racket/release/out1.sxref
usr/share/doc/racket/release/stamp.sxref


cheers,

Andreas


racket-common=8.10+dfsg1-2_racket-doc=8.12+dfsg1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: racket
Source-Version: 8.12+dfsg1-5
Done: David Bremner 

We believe that the bug you reported is fixed in the latest version of
racket, 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.
David Bremner  (supplier of updated racket 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: Sun, 17 Mar 2024 11:51:37 -0300
Source: racket
Architecture: source
Version: 8.12+dfsg1-5
Distribution: unstable
Urgency: medium
Maintainer: David Bremner 
Changed-By: David Bremner 
Closes: 1065815
Changes:
 racket (8.12+dfsg1-5) unstable; urgency=medium
 .
   * Upload to unstable
 .
 racket (8.12+dfsg1-4) experimental; urgency=medium
 .
   * Cherry pick 40a530935c and 5a6921d from upstream in an attempt to resolve
 big-endian build problems.
   * Switch mips64el to BC backend, as PB backend seems buggy
 (https://github.com/racket/racket/issues/4952)
 .
 racket (8.12+dfsg1-3) experimental; urgency=medium
 .
   * Move release notes back to racket-common (Closes: #1065815).
   * Cherry-pick 9d988ca1 from upstream to support PB mode on s390x
   * Enable PB mode on s390x
 .
 racket (8.12+dfsg1-2) experimental; urgency=medium
 .
   * Enable portable bytecode (PB) backend to fix some builds (notably ppc64el,
 mips64el) 

Bug#1067045: libsendmail-pmilter-perl: Includes non-free document

[Bastian Germann]

I am uploading a NMU in order to fix this.
The debdiff is attached.diff -Nru libsendmail-pmilter-perl-1.00/Makefile.PL 
libsendmail-pmilter-perl-1.00/Makefile.PL
--- libsendmail-pmilter-perl-1.00/Makefile.PL   2024-03-17 15:56:40.0 
+
+++ libsendmail-pmilter-perl-1.00/Makefile.PL   2011-04-16 13:05:03.0 
+
@@ -1,4 +1,4 @@
-# $Id: Makefile.PL,v 1.3 2004-08-14 18:09:38 bengen Exp $
+# $Id: Makefile.PL,v 1.11 2004/08/10 21:10:36 tvierling Exp $
 
 use 5.006;
 use ExtUtils::MakeMaker;
diff -Nru libsendmail-pmilter-perl-1.00/debian/changelog 
libsendmail-pmilter-perl-1.00/debian/changelog
--- libsendmail-pmilter-perl-1.00/debian/changelog  2024-03-17 
15:56:40.0 +
+++ libsendmail-pmilter-perl-1.00/debian/changelog  2024-03-17 
15:27:27.0 +
@@ -1,3 +1,14 @@
+libsendmail-pmilter-perl (1.00-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert source to format 3.0.
+(Closes: #1007675)
+  * d/copyright: Convert to machine-readable format.
+  * Exclude non-free document according to README.Debian.
+(Closes: #1067045)
+
+ -- Bastian Germann   Sun, 17 Mar 2024 15:27:27 +
+
 libsendmail-pmilter-perl (1.00-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libsendmail-pmilter-perl-1.00/debian/copyright 
libsendmail-pmilter-perl-1.00/debian/copyright
--- libsendmail-pmilter-perl-1.00/debian/copyright  2024-03-17 
15:56:40.0 +
+++ libsendmail-pmilter-perl-1.00/debian/copyright  2024-03-17 
15:27:27.0 +
@@ -1,31 +1,32 @@
-This is the debian package for the PMilter module.
-It was created by Hilko Bengen  using
-dh-make-perl.
-
-Upstream author:
-
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: PMilter
+Comment:
+This is the debian package for the PMilter module.
+It was created by Hilko Bengen  using
+dh-make-perl.
+Files-Excluded: doc/milter-protocol.txt
+Upstream-Contact:
 Todd Vierling  
 
+Files:
+*
 Copyright:
-
 Copyright (c) 2002-2004 Todd Vierling
-
-License: BSD
-
+License: BSD-3-clause
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are met:
-
+.
 1. Redistributions of source code must retain the above copyright notice,
 this list of conditions and the following disclaimer.
-
+.
 2. Redistributions in binary form must reproduce the above copyright
 notice, this list of conditions and the following disclaimer in the
 documentation and/or other materials provided with the distribution.
-
+.
 3. Neither the name of the author nor the names of contributors may be used
 to endorse or promote products derived from this software without specific
 prior written permission.
-
+.
 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
 AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
diff -Nru libsendmail-pmilter-perl-1.00/debian/patches/debian.patch 
libsendmail-pmilter-perl-1.00/debian/patches/debian.patch
--- libsendmail-pmilter-perl-1.00/debian/patches/debian.patch   1970-01-01 
00:00:00.0 +
+++ libsendmail-pmilter-perl-1.00/debian/patches/debian.patch   2024-03-17 
15:27:27.0 +
@@ -0,0 +1,92 @@
+Description: Correct headings
+--- libsendmail-pmilter-perl-1.00.orig/lib/Sendmail/Milter.pm
 libsendmail-pmilter-perl-1.00/lib/Sendmail/Milter.pm
+@@ -145,6 +145,10 @@ __END__
+ 
+ =pod
+ 
++=head1 NAME
++
++Sendmail::Milter - compatibility interface for Sendmail::PMilter
++
+ =head1 SYNOPSIS
+  
+ use Sendmail::Milter;
+--- libsendmail-pmilter-perl-1.00.orig/lib/Sendmail/PMilter.pm
 libsendmail-pmilter-perl-1.00/lib/Sendmail/PMilter.pm
+@@ -80,8 +80,6 @@ to be called Mail::Milter.
+ 
+ =head1 METHODS
+ 
+-=over 4
+-
+ =cut
+ 
+ # Symbols exported to the caller
+@@ -124,6 +122,8 @@ sub new ($) {
+ 
+ =pod
+ 
++=over 4
++
+ =item get_max_interpreters()
+ 
+ Returns the maximum number of interpreters passed to C.  This is
+@@ -470,10 +470,6 @@ these methods would not be useful with t
+ 
+ =over 4
+ 
+-=cut
+-
+-=pod
+-
+ =item auto_getconn(NAME[, CONFIG])
+ 
+ Returns the connection descriptor for milter NAME in Sendmail configuration
+@@ -950,6 +946,8 @@ Note that, because the default socket ba
+ wise to increase this backlog by calling C before entering
+ C if using this dispatcher.
+ 
++=back
++
+ =cut
+ 
+ sub sequential_dispatcher () {
+@@ -1042,8 +1040,6 @@ when called:
+ 
+ =back
+ 
+-=back
+-
+ =head1 SECURITY CONSIDERATIONS
+ 
+ =over 4
+--- libsendmail-pmilter-perl-1.00.orig/lib/Sendmail/PMilter/Context.pm
 libsendmail-pmilter-perl-1.00/lib/Sendmail/PMilter/Context.pm
+@@ -48,7 +48,7 @@ our $VERSION = '0.94';
+ 
+ =pod
+ 
+-=head1 SYNOPSIS
++=head1 NAME
+ 
+ 

Bug#1066475: libpsortb: FTBFS: debug_funcs.c:320:38: error: implicit declaration of function ‘get_mtx_index’ [-Werror=implicit-function-declaration]

[Andrey Rakhmatullin]

On Wed, Mar 13, 2024 at 12:52:40PM +0100, Lucas Nussbaum wrote:
> > debug_funcs.c:320:38: error: implicit declaration of function 
> > ‘get_mtx_index’ [-Werror=implicit-function-declaration]
An obvious solution would be including funcs.h into debug_funcs.c but this
dead code is so bad that the prototypes in funcs.h for the functions
defined in debug_funcs.c itself are different from the function
definitions so this isn't possible. Probably nobody actually calls those
functions so nothing breaks at the run time but to be able to actually
compile them the prototypes in funcs.h should probably be fixed.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1066340: t4kcommon: FTBFS: linebreak.c:163:19: error: implicit declaration of function ‘u8_mbtouc_unsafe’ [-Werror=implicit-function-declaration]

[Andrey Rakhmatullin]

On Wed, Mar 13, 2024 at 12:45:32PM +0100, Lucas Nussbaum wrote:
> > linebreak.c:163:19: error: implicit declaration of function 
> > ‘u8_mbtouc_unsafe’ [-Werror=implicit-function-declaration]
> >   163 |   int count = u8_mbtouc_unsafe (, s, s_end - s);
The prototype, in src/linebreak/unistr.h, is under 
#ifdef GNULIB_UNISTR_U8_MBTOUC_UNSAFE, but nothing sets that.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1067045: libsendmail-pmilter-perl: Includes non-free document

[Bastian Germann]

Source: libsendmail-pmilter-perl
Version: 1.00-1
Severity: serious

The source package includes the non-free milter-protocol.txt that is claimed to 
be excluded in README.Debian.

Processed: Re: Bug#1061019: xdg-desktop-portal: FTBFS: test_inputcapture: Timed out waiting for response from SetPointerBarriers

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo help
Bug #1061019 [src:xdg-desktop-portal] xdg-desktop-portal: FTBFS: 
test_inputcapture: Timed out waiting for response from SetPointerBarriers
Added tag(s) help and moreinfo.
> severity -1 important
Bug #1061019 [src:xdg-desktop-portal] xdg-desktop-portal: FTBFS: 
test_inputcapture: Timed out waiting for response from SetPointerBarriers
Severity set to 'important' from 'serious'

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

Bug#1061019: xdg-desktop-portal: FTBFS: test_inputcapture: Timed out waiting for response from SetPointerBarriers

[Simon McVittie]

Control: tags -1 + moreinfo help
Control: severity -1 important

On Sun, 21 Jan 2024 at 13:17:45 +, Simon McVittie wrote:
> On Tue, 16 Jan 2024 at 20:37:49 +0100, Lucas Nussbaum wrote:
> > > 26/28 xdg-desktop-portal:pytest / pytest test_inputcaptureFAIL
> > > 11.21s   exit status 1
> > > >>> MALLOC_PERTURB_=39 
> > > >>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
> > > >>> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> > > >>>  /usr/bin/pytest-3 --verbose --log-level=DEBUG -k test_inputcapture
> 
> I tried rebuilding the package locally (in sbuild in an amd64 bookworm
> VM) and this test passed.

I still cannot reproduce this, and it doesn't seem to affect the buildds
or reproducible-builds infrastructure, so I don't consider this to be RC.
I attach an example of a successful build log.

It's probably a race condition in the upstream test suite, possibly
triggered by Lucas' test-build happening on a machine with 8 cores and 32G
of RAM. If someone else can reproduce this, patches gratefully received.

Thanks,
smcv


xdg-desktop-portal_1.18.2-1_amd64_20240317t150806.build.gz
Description: application/gzip

Bug#1067043: marked as done (libruby: needs updating for libruby3.1t64)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 15:23:18 +
with message-id 
and subject line Bug#1067043: fixed in ruby-defaults 1:3.1+nmu1
has caused the Debian Bug report #1067043,
regarding libruby: needs updating for libruby3.1t64
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.)


-- 
1067043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libruby
Version: 1:3.1
Severity: serious
Justification: blocker for 64-bit time_t transition
X-Debbugs-Cc: z...@debian.org, debian-...@lists.debian.org
Control: affects -1 + src:graphviz src:vala

Now that libruby3.1t64 has reached unstable, libruby is uninstallable on
the architectures affected by the 64-bit time_t transition, blocking the
rebuild of packages such as graphviz and vala via this dependency chain:

... -> vala -> graphviz -> ruby -> libruby -> libruby3.1

The impact of this is visible in for example
.

I suspect the only change needed here is to update the libruby metapackage
so that it depends on libruby3.1t64 instead of libruby3.1. Please could
someone who knows Ruby check this?

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: ruby-defaults
Source-Version: 1:3.1+nmu1
Done: Chris Hofstaedtler 

We believe that the bug you reported is fixed in the latest version of
ruby-defaults, 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.
Chris Hofstaedtler  (supplier of updated ruby-defaults 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: Sun, 17 Mar 2024 16:08:39 +0100
Source: ruby-defaults
Architecture: source
Version: 1:3.1+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Chris Hofstaedtler 
Closes: 1067043
Changes:
 ruby-defaults (1:3.1+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * libruby: follow libruby3.1 -> libruby3.1t64 rename (Closes: #1067043)
Checksums-Sha1:
 ed25b34408bc84222ecc1e03946e93b99a82f409 2004 ruby-defaults_3.1+nmu1.dsc
 6fc6a81c4dad1562f405e6d8d02e74137bd25336 13280 ruby-defaults_3.1+nmu1.tar.xz
 ef31c9044d8499620c3289d64274e4e1e9140a24 7311 
ruby-defaults_3.1+nmu1_arm64.buildinfo
Checksums-Sha256:
 ec07c7fdd15b00cdbff7710f350eddc8b9fa3e21c470201214588307362f0a16 2004 
ruby-defaults_3.1+nmu1.dsc
 516dce3f6a360ca2db28fa587f90dacd1f4c53a7b8594c2fc90c971b8aa0494e 13280 
ruby-defaults_3.1+nmu1.tar.xz
 1814adaf836600f1364eb7dd92a5ee0cb4cefd3a931dcb6c4dd2edf947f89925 7311 
ruby-defaults_3.1+nmu1_arm64.buildinfo
Files:
 01e7a2d026a9b6fd70554a1a102f5002 2004 ruby optional ruby-defaults_3.1+nmu1.dsc
 4b041b3f8271c88f8912a4acab39bb1c 13280 ruby optional 
ruby-defaults_3.1+nmu1.tar.xz
 8936beed1003caf9df143cd9e5bf8de2 7311 ruby optional 
ruby-defaults_3.1+nmu1_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmX3CD8ACgkQXBPW25MF
LgPJKQ//VDcTYahkjVw0ym1M6iiVwfg6mJtGhMtSld6erYVESB4X+/7Y5p6DQfiX
hmGEE1WeouWLtyrwF8ve1kSKyIct+QE4BI3MJOeCIhdkQptoBmr0ETjAmH1nbIF6
zTVcwbhGFx3mNODfxXNHtbXnxAIuPh7Xejk55qKeP38nSl7RBDoRFfBRh6G5HPCy
kqBDbBGfcNrGShCeQf1nxiCB1g1PIEJ63nZHSD2wrEwytUxZzBg9cOZAtZKKDRXv
fAowpwJillcCDzDQ51ng6qZmanSyiSQ1MLIr/Ir1ey5OmYgYmeKBGJ+PUS0lGv/9
GfcJBaVI2RWBhUJoDRirUkmZdSni0BNGBWk464kdX5iOpygpIZQSICwgKBFhIl+5
3CfJ2xb1ZD2hF6mphnTrShLXqGjH0ebN69vh4yRQhqmAIv8GyHFAkCphZJ/JeU2/
IHXM8C7I1p8nyTQ9RC6hzsCK+eH5ZvE9n9LtJZ9O9u7y3pmtwLk82r+LRoM+mOQd
tvmGoWwUkcZE4M9c9rmzeMEPX0W64/bvzUjOaSRz0jo1JeVwN/rOGtoVT6NF/Umx
2s2BP9RRVBXf28ujHYtB1jZljXnpikoQNTNLpM7EBs5GlAG+hvTNgZeozsdv8cF7
7w1neN9Qcny9vTnYrrqU3IU8Gr91lmPU/ehAVpS/qFjEHqpUODc=
=grLy
-END PGP SIGNATURE-



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

Bug#1067043: libruby: needs updating for libruby3.1t64

[Chris Hofstaedtler]

Control: tags -1 + pending

* Simon McVittie  [240317 15:57]:
> Package: libruby
> Version: 1:3.1
[..]

> Now that libruby3.1t64 has reached unstable, libruby is uninstallable on
> the architectures affected by the 64-bit time_t transition, 
[..]

> I suspect the only change needed here is to update the libruby metapackage
> so that it depends on libruby3.1t64 instead of libruby3.1. Please could
> someone who knows Ruby check this?

Indeed. I've uploaded ruby-defaults 1:3.1+nmu1 and pushed to salsa.

Chris

PS: @ruby-team: if you disagree / want to take over, please let me know.

Processed: Re: Bug#1067043: libruby: needs updating for libruby3.1t64

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1067043 [libruby] libruby: needs updating for libruby3.1t64
Ignoring request to alter tags of bug #1067043 to the same tags previously set

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

Processed: Bug#1067043 marked as pending in ruby-defaults

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067043 [libruby] libruby: needs updating for libruby3.1t64
Added tag(s) pending.

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

Bug#1067043: marked as pending in ruby-defaults

[Chris Hofstaedtler]

Control: tag -1 pending

Hello,

Bug #1067043 in ruby-defaults 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/ruby-team/ruby-defaults/-/commit/0f0bd9f3bc8dde8192350491c14a02cbe058ae3e


libruby: follow libruby3.1 -> libruby3.1t64 rename

Closes: #1067043


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067043

Bug#1061633: marked as done (libtemplates-parser: autopkgtest needs update for new version of gcc-12)

[Debian Bug Tracking System]

Your message dated Sun, 17 Mar 2024 15:06:01 +
with message-id 
and subject line Bug#1061633: fixed in libtemplates-parser 24.0.0-2
has caused the Debian Bug report #1061633,
regarding libtemplates-parser: autopkgtest needs update for new version of 
gcc-12
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.)


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

Source: libtemplates-parser
Version: 23.0.0-3
Severity: serious
X-Debbugs-CC: gcc...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gcc-12

Dear maintainer(s),

With a recent upload of gcc-12 the autopkgtest of libtemplates-parser 
fails in testing when that autopkgtest is run with the binary packages 
of gcc-12 from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
gcc-12 from testing12.3.0-14
libtemplates-parserfrom testing23.0.0-3
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of gcc-12 to testing 
[1]. Of course, gcc-12 shouldn't just break your autopkgtest (or even 
worse, your package), so please investigate.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from gcc-12 should really add 
a versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=gcc-12

https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtemplates-parser/42388674/log.gz

 30s Changing to object directory of "P": 
"/tmp/autopkgtest-lxc.xtf31hge/downtmp/autopkgtest_tmp/"
 30s /usr/bin/gcc-12 -c -x ada -gnatA -gnatec=/tmp/GNAT-TEMP-03.TMP 
-gnatem=/tmp/GNAT-TEMP-04.TMP 
/tmp/autopkgtest-lxc.xtf31hge/downtmp/build.69k/src/docs/src/demo.adb

 30s /usr/libexec/gprbuild/gprbind demo.bexch
 30s /usr/bin/gnatbind -shared -o b__demo.adb 
/tmp/autopkgtest-lxc.xtf31hge/downtmp/autopkgtest_tmp/demo.ali -x 
-F=/tmp/GNAT-TEMP-05.TMP -O=/tmp/GNAT-TEMP-07.TMP
 30s error: "templates_parser_tasking__standard_tasking.adb" must be 
compiled
 30s error: 
("/usr/lib/x86_64-linux-gnu/ada/adalib/templates_parser/templates_parser_tasking__standard_tasking.ali" 
is obsolete and read-only)

 30s gprbind: invocation of gnatbind failed
 30s gprbuild: unable to bind demo.adb
 30s autopkgtest [11:05:41]: test link-with-shared



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libtemplates-parser
Source-Version: 24.0.0-2
Done: Nicolas Boulenguez 

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

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

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

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated 
libtemplates-parser 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, 17 Mar 2024 15:34:24 +0100
Source: libtemplates-parser
Architecture: source
Version: 24.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Brenta 
Changed-By: Nicolas Boulenguez 
Closes: 1061633
Changes:
 libtemplates-parser (24.0.0-2) unstable; urgency=medium
 .
   * Reupload to unstable for the gnat-13/time_t64 transition.
 Closes: #1061633.
Checksums-Sha1:
 81a443fd6b48bfeaf2e868be2d7e744b77b86dec 2739 libtemplates-parser_24.0.0-2.dsc
 1756c2882c28cd3a347c139ddf88f97bb62788c5 13144 
libtemplates-parser_24.0.0-2.debian.tar.xz
 0eb9f3264a79fedb91764998882b91a0c37c57c3 6135 
libtemplates-parser_24.0.0-2_source.buildinfo
Checksums-Sha256:
 

Bug#1064139: ogre-1.12: FTBFS: error: ‘BuildFontAtlas’ is not a member of ‘ImGuiFreeType’

[Matthias Klose]

On 17.03.24 14:59, Matthias Klose wrote:

with both patches, I get until:

/home/packages/tmp/x/ogre-1.12-1.12.10+dfsg2/obj-x86_64-linux-gnu/Components/Python/CMakeFiles/_
Overlay.dir/OgreOverlayPYTHON_wrap.cxx:6527:56: error: expected 
template-name before '<' token
  6527 | struct SwigPyMapIterator_T : 
SwigPyIteratorClosed_T
 >
   |    ^
/home/packages/tmp/x/ogre-1.12-1.12.10+dfsg2/obj-x86_64-linux-gnu/Components/Python/CMakeFiles/_
Overlay.dir/OgreOverlayPYTHON_wrap.cxx:6527:56: error: expected '{' 
before '<' token


[...]

/home/packages/tmp/x/ogre-1.12-1.12.10+dfsg2/obj-x86_64-linux-gnu/Components/Python/CMakeFiles/_Overlay.dir/OgreOverlayPYTHON_wrap.cxx:6547:12:
 error: 'SwigPyIterator' does not name a type; did you mean 
'SwigPyMapIterator_T'?
  6547 | inline SwigPyIterator*
   |    ^~
   |    SwigPyMapIterator_T
/home/packages/tmp/x/ogre-1.12-1.12.10+dfsg2/obj-x86_64-linux-gnu/Components/Python/CMakeFiles/_Overlay.dir/OgreOverlayPYTHON_wrap.cxx:6565:12:
 error: 'SwigPyIterator' does not name a type; did you mean 
'SwigPyMapIterator_T'?
  6565 | inline SwigPyIterator*
   |    ^~
   |    SwigPyMapIterator_T



this is introduced by swig 4.2.x, builds with wig 4.1.x

Processed: Re: sbd: FTBFS due to hardcoded libaio SONAME used in dlopen()

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1065486 [src:sbd] sbd: FTBFS due to hardcoded libaio SONAME used in 
dlopen()
Added tag(s) pending.

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

Bug#1065486: sbd: FTBFS due to hardcoded libaio SONAME used in dlopen()

[Ferenc Wágner]

Control: tags -1 + pending

On Tue, 5 Mar 2024 12:29:36 +0100 Guillem Jover  wrote:

> the package is already explicitly linking against -laio (which I guess
> also means there's a missing Build-Depends here)

Hi Guillem,

libaio-dev is already in Build-Depends, so I think we're fine here.

> it might also be worth investigating in the future whether the dlopen
> is really necessary at all (the test case is already being linked also
> against -laio).

I can't see the point of dlopen() here.  I pushed a change eliminating
it to Salsa and I'll upload it soon unless Valentin objects.
-- 
Thanks,
Feri.