Bug#1052197: marked as done (xrdp: after bullseye-security upgrade, empty turquoise screen after logging in)

[Debian Bug Tracking System]

Your message dated Fri, 12 Apr 2024 07:44:42 +0200
with message-id 
and subject line xrdp: after bullseye-security upgrade, empty turquoise screen 
after logging in
has caused the Debian Bug report #1052197,
regarding xrdp: after bullseye-security upgrade, empty turquoise screen after 
logging in
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.)


-- 
1052197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xrdp
Version: 0.9.21.1-1~deb11u1
Severity: serious
Justification: does not work
X-Debbugs-Cc: t...@mirbsd.de, t...@security.debian.org

I’ve just upgraded the xrdp package. I had made sure to terminate the
old service before the new version is started.

Then, to test it, I logged in, but all I get is a window with a turquoise
background, nothing on it. I *can* however see in ps(1) that my session
(IceWM, kwalletcli) is started; it’s just not transmitted to rdesktop.


-- System Information:
Debian Release: 11.7
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 
'oldstable-proposed-updates'), (500, 'oldoldstable-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-25-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages xrdp depends on:
ii  adduser  3.118+deb11u1
ii  init-system-helpers  1.60
ii  libc62.31-13+deb11u6
ii  libfuse2 2.9.9-5
ii  libjpeg62-turbo  1:2.0.6-4
ii  libopus0 1.3.1-0.1
ii  libpam0g 1.4.0-9+deb11u1
ii  libssl1.11.1.1w-0~deb11u1
ii  libx11-6 2:1.7.2-1+deb11u1
ii  libxfixes3   1:5.0.3-2
ii  libxrandr2   2:1.5.1-1
ii  lsb-base 11.1.0
ii  ssl-cert 1.1.0+nmu1

Versions of packages xrdp recommends:
ii  fuse  2.9.9-5
ii  xorgxrdp  1:0.2.15-1

Versions of packages xrdp suggests:
pn  guacamole  

Versions of packages xorgxrdp depends on:
ii  libc6  2.31-13+deb11u6
ii  libepoxy0  1.5.5-1
pn  xorg-input-abi-24  
ii  xserver-xorg-core [xorg-video-abi-24]  2:1.20.11-1+deb11u6

Versions of packages xorgxrdp recommends:
pn  xorg  

Versions of packages xrdp is related to:
ii  tightvncserver [vnc-server]  1:1.3.10-3
ii  xserver-xorg-legacy  2:1.20.11-1+deb11u6

-- no debconf information
--- End Message ---
--- Begin Message ---

Dear reporter,

This bug has been closed upstream, and upstream packages have been in 
the archive for a while.


I am closing this bug, but please re-open if they still affect you.

Best,
Alex--- End Message ---

Processed: re: openjfx: 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"

[Debian Bug Tracking System]

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

> Tags 1068159 +patch
Bug #1068159 [src:openjfx] openjfx: 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"
Added tag(s) patch.
> Thanks
Stopping processing here.

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

Bug#1068159: openjfx: 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"

[Peter Green]

Tags 1068159 +patch
Thanks

The build failure is caused by the following in
modules/javafx.media/src/main/native/gstreamer/gstreamer-lite/projects/build/linux/common/config.h

> /* Number of bits in a file offset, on hosts where this is settable. */
> #undef _FILE_OFFSET_BITS

Looking at the file, this looks like output from autotools that was
copied to become a static configuration file when code was vendored.

One option would be to remove this line completely, however to minimise
the risk of causing regressions on architectures not involved in the
time64 transition I choose instead to place it behind a #ifndef
guard.

> /* Number of bits in a file offset, on hosts where this is settable. */
> #ifndef _TIME_BITS
> # undef _FILE_OFFSET_BITS
> #endif

With this change, I was able to build the package successfully on
armhf.

Debdiff attached, if I get no response I will probablly NMU this
in a week or so.diff -Nru openjfx-11.0.11+1/debian/changelog openjfx-11.0.11+1/debian/changelog
--- openjfx-11.0.11+1/debian/changelog  2023-07-16 03:30:26.0 +
+++ openjfx-11.0.11+1/debian/changelog  2024-04-11 15:34:39.0 +
@@ -1,3 +1,10 @@
+openjfx (11.0.11+1-3.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't undefine _FILE_OFFSET_BITS if _TIME_BITS is set (Closes: #1068159)
+
+ -- root   Thu, 11 Apr 2024 15:34:39 +
+
 openjfx (11.0.11+1-3.1) unstable; urgency=medium
 
   * Team upload.
diff -Nru 
openjfx-11.0.11+1/debian/patches/40-dont-unset-file-offset-bits-if-time-bits-set.patch
 
openjfx-11.0.11+1/debian/patches/40-dont-unset-file-offset-bits-if-time-bits-set.patch
--- 
openjfx-11.0.11+1/debian/patches/40-dont-unset-file-offset-bits-if-time-bits-set.patch
  1970-01-01 00:00:00.0 +
+++ 
openjfx-11.0.11+1/debian/patches/40-dont-unset-file-offset-bits-if-time-bits-set.patch
  2024-04-11 15:34:39.0 +
@@ -0,0 +1,29 @@
+Description:  Don't undefine _FILE_OFFSET_BITS if _TIME_BITS is set.
+ Having _TIME_BITS set to 64 but _FILE_OFFSET_BITS not set on a 32-bit
+ architectureis not supported by glibc. As a result of this, unsetting
+ _FILE_OFFSET_BITS on a 32-bit architecture with 64-bit time causes a build
+ failure.
+ 
+ I suspect the unsetting of _FILE_OFFSET_BITS is a leftover from an
+ autogenerated file that became a static file rather than a deliberate
+ choice to override system settings.
+
+ I suspect that unsetting _FILE_OFFSET_BITS is unnessacery in general and the
+ line could be completely removed. However to minimise the risk of regressions
+ I instead used an ifndef gaurd
+Author: Peter Michael Green 
+Bug-Debian: https://bugs.debian.org/1068159
+
+--- 
openjfx-11.0.11+1.orig/modules/javafx.media/src/main/native/gstreamer/gstreamer-lite/projects/build/linux/common/config.h
 
openjfx-11.0.11+1/modules/javafx.media/src/main/native/gstreamer/gstreamer-lite/projects/build/linux/common/config.h
+@@ -544,7 +544,9 @@
+ #endif
+ 
+ /* Number of bits in a file offset, on hosts where this is settable. */
+-#undef _FILE_OFFSET_BITS
++#ifndef _TIME_BITS
++# undef _FILE_OFFSET_BITS
++#endif
+ 
+ /* Define to 1 to make fseeko visible on some hosts (e.g. glibc 2.2). */
+ #undef _LARGEFILE_SOURCE
diff -Nru openjfx-11.0.11+1/debian/patches/series 
openjfx-11.0.11+1/debian/patches/series
--- openjfx-11.0.11+1/debian/patches/series 2023-07-16 03:30:26.0 
+
+++ openjfx-11.0.11+1/debian/patches/series 2024-04-11 15:34:39.0 
+
@@ -21,3 +21,4 @@
 disable-ffmpeg.patch
 38-javadoc.patch
 webkit-217079-only-use-jumpislands-with-JIT.patch
+40-dont-unset-file-offset-bits-if-time-bits-set.patch

Bug#1066658: sup: FTBFS: scm.c:316:9: error: implicit declaration of function ‘setproctitle’ [-Werror=implicit-function-declaration]

[Bo YU]

Tags: patch

Hi,

,On Wed, Mar 13, 2024 at 12:57:21PM +0100, Lucas Nussbaum wrote:

scm.c: In function ‘service’:
scm.c:316:9: error: implicit declaration of function ‘setproctitle’ 
[-Werror=implicit-function-declaration]
  316 | setproctitle("Serving %s", remotehost());
  | ^~~~
scm.c: In function ‘request’:
scm.c:448:16: warning: ignoring return value of ‘write’ declared with attribute 
‘warn_unused_result’ [-Wunused-result]
  448 | (void) write(netfile, , sizeof(int));
  |^~~
scmio.c: In function ‘readfile’:


I have uploaded it to mentor to wait for sponsoring[0]. But there is one
debdiff if you can review it.

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068814

Thanks.

--
Regards,
--
  Bo YU

diff -Nru sup-20100519/debian/changelog sup-20100519/debian/changelog
--- sup-20100519/debian/changelog   2020-08-05 19:53:16.0 +0800
+++ sup-20100519/debian/changelog   2024-04-11 16:41:22.0 +0800
@@ -1,3 +1,12 @@
+sup (20100519-4) unstable; urgency=medium
+
+  * QA upload.
+  * set std-ver to 4.7.0.
+  * Add 07_fix-implicit-function-declaration.patch to fix ftbfs issue.
+(Closes: #1066658)
+
+ -- Bo YU   Thu, 11 Apr 2024 16:41:22 +0800
+
 sup (20100519-3) unstable; urgency=medium
 
   * QA upload.
diff -Nru sup-20100519/debian/control sup-20100519/debian/control
--- sup-20100519/debian/control 2020-08-05 19:48:03.0 +0800
+++ sup-20100519/debian/control 2024-04-11 16:03:18.0 +0800
@@ -3,7 +3,7 @@
 Priority: optional
 Build-Depends: debhelper-compat (= 13), libwrap0-dev
 Maintainer: Debian QA Group 
-Standards-Version: 4.5.0
+Standards-Version: 4.7.0
 
 Package: sup
 Architecture: any
diff -Nru 
sup-20100519/debian/patches/07_fix-implicit-function-declaration.patch 
sup-20100519/debian/patches/07_fix-implicit-function-declaration.patch
--- sup-20100519/debian/patches/07_fix-implicit-function-declaration.patch  
1970-01-01 07:30:00.0 +0730
+++ sup-20100519/debian/patches/07_fix-implicit-function-declaration.patch  
2024-04-11 15:59:50.0 +0800
@@ -0,0 +1,17 @@
+Description: fix implicit-function-declaration issue
+Author: Bo YU 
+Bug: https://bugs.debian.org/1066658
+Last-Update: 2024-04-11
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/scm.c
 b/scm.c
+@@ -195,6 +195,8 @@
+ #define   INADDR_LOOPBACK (u_long)0x7f01  /* 127.0.0.1 */
+ #endif
+ 
++void setproctitle(const char *fmt, ...);
++
+ char scmversion[] = "4.3 BSD";
+ extern int silent;
+ 
diff -Nru sup-20100519/debian/patches/series sup-20100519/debian/patches/series
--- sup-20100519/debian/patches/series  2020-08-05 19:43:02.0 +0800
+++ sup-20100519/debian/patches/series  2024-04-11 15:01:34.0 +0800
@@ -4,3 +4,4 @@
 04_fix_man.patch
 05_unconst.patch
 06_fix_ftbfs.patch
+07_fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1065790: marked as done (libosmo-netif: FTBFS on arm{el,hf}: tests fail)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 22:50:34 +
with message-id 
and subject line Bug#1065790: fixed in libosmo-netif 1.2.0-3
has caused the Debian Bug report #1065790,
regarding libosmo-netif: FTBFS on arm{el,hf}: tests fail
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.)


-- 
1065790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libosmo-netif
Version: 1.2.0-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=libosmo-netif=armhf=1.2.0-2.1=1709142489=0

--- expout  2024-02-28 17:47:53.939733157 +
+++ /<>/tests/testsuite.dir/at-groups/3/stdout 2024-02-28 
17:48:03.951783359 +
@@ -1,108 +1,10 @@
 ===test_output_consecutive===
-sys={0.00}, mono={0.00}: clock_override_set
-sys={0.00}, mono={0.00}: dequeue: seq=50 ts=500 M enqueued=5
-sys={0.00}, mono={0.00}: first dequed before first select
-sys={0.02}, mono={0.02}: clock_override_add
-sys={0.02}, mono={0.02}: second select, second dequed
-sys={0.02}, mono={0.02}: dequeue: seq=51 ts=660 enqueued=4
-sys={0.04}, mono={0.04}: clock_override_add
-sys={0.04}, mono={0.04}: third select, third dequed
-sys={0.04}, mono={0.04}: dequeue: seq=52 ts=820 enqueued=3
-sys={0.06}, mono={0.06}: clock_override_add
-sys={0.06}, mono={0.06}: fourth select, fourth dequed
-sys={0.06}, mono={0.06}: dequeue: seq=53 ts=980 enqueued=2
-sys={0.08}, mono={0.08}: clock_override_add
-sys={0.08}, mono={0.08}: fifth select, fifth dequed
-sys={0.08}, mono={0.08}: dequeue: seq=54 ts=1140 enqueued=1
-sys={0.10}, mono={0.10}: clock_override_add
-sys={0.10}, mono={0.10}: sixth select, sixth dequed
-sys={0.10}, mono={0.10}: dequeue: seq=55 ts=1300 enqueued=0
-sys={0.10}, mono={0.10}: send second osmux frame
-sys={0.10}, mono={0.10}: dequeue: seq=56 ts=1460 enqueued=5
-sys={0.10}, mono={0.10}: first dequed before first select
-sys={0.12}, mono={0.12}: clock_override_add
-sys={0.12}, mono={0.12}: second select, second dequed
-sys={0.12}, mono={0.12}: dequeue: seq=57 ts=1620 enqueued=4
-sys={0.20}, mono={0.20}: clock_override_add
-sys={0.20}, mono={0.20}: third select, four packet should be dequeued
-sys={0.20}, mono={0.20}: dequeue: seq=58 ts=1780 enqueued=3
-sys={0.20}, mono={0.20}: dequeue: seq=59 ts=1940 enqueued=2
-sys={0.20}, mono={0.20}: dequeue: seq=60 ts=2100 enqueued=1
-sys={0.20}, mono={0.20}: dequeue: seq=61 ts=2260 enqueued=0
-sys={0.20}, mono={0.20}: calling flush on empty list, should do nothing
-===test_output_interleaved===
-sys={0.00}, mono={0.00}: clock_override_set
-sys={0.00}, mono={0.00}: dequeue: seq=50 ts=500 M enqueued=5
-sys={0.04}, mono={0.04}: clock_override_add
-sys={0.04}, mono={0.04}: select, 3 dequed, 3 still queued
-sys={0.04}, mono={0.04}: dequeue: seq=51 ts=660 enqueued=4
-sys={0.04}, mono={0.04}: dequeue: seq=52 ts=820 enqueued=3
-sys={0.04}, mono={0.04}: next frame arrives, 3 pending rtp packets are 
dequeued and first of new osmux frame too
-sys={0.04}, mono={0.04}: dequeue: seq=53 ts=980 enqueued=8
-sys={0.04}, mono={0.04}: dequeue: seq=54 ts=1140 enqueued=7
-sys={0.04}, mono={0.04}: dequeue: seq=55 ts=1300 enqueued=6
-sys={0.04}, mono={0.04}: dequeue: seq=56 ts=1460 enqueued=5
-sys={0.14}, mono={0.14}: clock_override_add
-sys={0.14}, mono={0.14}: calling select, then all should be out
-sys={0.14}, mono={0.14}: dequeue: seq=57 ts=1620 enqueued=4
-sys={0.14}, mono={0.14}: dequeue: seq=58 ts=1780 enqueued=3
-sys={0.14}, mono={0.14}: dequeue: seq=59 ts=1940 enqueued=2
-sys={0.14}, mono={0.14}: dequeue: seq=60 ts=2100 enqueued=1
-sys={0.14}, mono={0.14}: dequeue: seq=61 ts=2260 enqueued=0
-===test_output_2together===
-sys={0.00}, mono={0.00}: clock_override_set
-sys={0.00}, mono={0.00}: dequeue: seq=50 ts=500 M enqueued=5
-sys={0.00}, mono={0.00}: calling select in between 2 osmux recv
-sys={0.00}, mono={0.00}: calling select after receiving 2nd osmux. 
Dequeue 1st osmux frame and 1st rtp from 2nd osmux frame.
-sys={0.00}, mono={0.00}: dequeue: seq=51 ts=660 enqueued=10
-sys={0.00}, 

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

[Zixing Liu]

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

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/fix-missing-includes.patch: Add missing includes.
Closes LP: #2061037.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-26-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ruby-fusefs-0.7.0/debian/patches/fix-missing-includes.patch 
ruby-fusefs-0.7.0/debian/patches/fix-missing-includes.patch
--- ruby-fusefs-0.7.0/debian/patches/fix-missing-includes.patch 1969-12-31 
17:00:00.0 -0700
+++ ruby-fusefs-0.7.0/debian/patches/fix-missing-includes.patch 2024-04-11 
16:38:56.0 -0600
@@ -0,0 +1,19 @@
+Description: Add missing includes
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067066
+Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/ruby-fusefs/+bug/2061037
+Forwarded: no
+Last-Update: 2024-04-11
+---
+Index: ruby-fusefs/ext/fusefs_fuse.c
+===
+--- ruby-fusefs.orig/ext/fusefs_fuse.c
 ruby-fusefs/ext/fusefs_fuse.c
+@@ -7,6 +7,7 @@
+ #define _FILE_OFFSET_BITS 64
+ 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru ruby-fusefs-0.7.0/debian/patches/series 
ruby-fusefs-0.7.0/debian/patches/series
--- ruby-fusefs-0.7.0/debian/patches/series 2022-06-30 17:15:19.0 
-0600
+++ ruby-fusefs-0.7.0/debian/patches/series 2024-04-11 16:35:51.0 
-0600
@@ -1,2 +1,3 @@
 port-to-newer-ruby.patch
 fix-dynamic-library-load-path.patch
+fix-missing-includes.patch

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1067066 [src:ruby-fusefs] ruby-fusefs: fusefs_fuse.c:31:10: error: 
implicit declaration of function ‘fuse_chan_fd’ 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1068194: marked as done (pcsx2: FTBFS: /<>/plugins/cdvdGigaherz/src/CDVD.cpp:143:19: error: ‘system_error’ in namespace ‘std’ does not name a type)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 22:23:03 +
with message-id 
and subject line Bug#1068194: fixed in pcsx2 1.6.0+dfsg-2.1
has caused the Debian Bug report #1068194,
regarding pcsx2: FTBFS: 
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:143:19: error: 
‘system_error’ in namespace ‘std’ does not name a type
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.)


-- 
1068194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pcsx2
Version: 1.6.0+dfsg-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=pcsx2=i386=1.6.0%2Bdfsg-2%2Bb10=1711729892=0

[  7%] Generating ../tr_TR__pcsx2_Main.gmo
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgmerge --quiet 
--update --backup=none -s /<>/locales/tr_TR/pcsx2_Main.po 
/<>/locales/templates/pcsx2_Main.pot
/<>/plugins/cdvdGigaherz/src/CDVD.cpp: In function ‘bool 
StartKeepAliveThread()’:
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:143:19: error: 
‘system_error’ in namespace ‘std’ does not name a type
  143 | } catch (std::system_error &) {
  |   ^~~~
/<>/plugins/cdvdGigaherz/src/CDVD.cpp: In function ‘s32 
CDVDopen(const char*)’:
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:188:19: error: 
‘runtime_error’ in namespace ‘std’ does not name a type
  188 | } catch (std::runtime_error ) {
  |   ^
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:22:1: note: 
‘std::runtime_error’ is defined in header ‘’; did you forget to 
‘#include ’?
   21 | #include "svnrev.h"
  +++ |+#include 
   22 | 
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgfmt -o 
/<>/obj-i686-linux-gnu/tr_TR__pcsx2_Main.gmo 
/<>/locales/tr_TR/pcsx2_Main.po
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:189:15: error: ‘ex’ was not 
declared in this scope
  189 | fputs(ex.what(), stdout);
  |   ^~
[  8%] Generating ../zh_CN__pcsx2_Main.gmo
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgmerge --quiet 
--update --backup=none -s /<>/locales/zh_CN/pcsx2_Main.po 
/<>/locales/templates/pcsx2_Main.pot
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgfmt -o 
/<>/obj-i686-linux-gnu/zh_CN__pcsx2_Main.gmo 
/<>/locales/zh_CN/pcsx2_Main.po
[  8%] Generating ../zh_TW__pcsx2_Main.gmo
cd /<>/obj-i686-linux-gnu/locales && /usr/bin/msgmerge --quiet 
--update --backup=none -s /<>/locales/zh_TW/pcsx2_Main.po 
/<>/locales/templates/pcsx2_Main.pot
make[3]: *** 
[plugins/cdvdGigaherz/src/CMakeFiles/cdvdGigaherz.dir/build.make:79: 
plugins/cdvdGigaherz/src/CMakeFiles/cdvdGigaherz.dir/CDVD.cpp.o] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: pcsx2
Source-Version: 1.6.0+dfsg-2.1
Done: Sebastian Ramacher 

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

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated pcsx2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 23:36:38 +0200
Source: pcsx2
Architecture: source
Version: 1.6.0+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Sebastian Ramacher 
Closes: 1068194
Changes:
 pcsx2 (1.6.0+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Mate Kukri ]
   * d/p/cpp_error_ftbfs.patch: fix FTBFS by adding missing include for
 std::*_error types. (LP: #2048072) (Closes: #1068194)
Checksums-Sha1:
 06ce5cae38178e3335c368793c426eabe456f372 1556 pcsx2_1.6.0+dfsg-2.1.dsc
 214d3c84d380106ed1cbd613bd209adb40b229ed 11876 
pcsx2_1.6.0+dfsg-2.1.debian.tar.xz
 c5ae915546b479281970abd0f7682f6288b74145 16579 
pcsx2_1.6.0+dfsg-2.1_source.buildinfo
Checksums-Sha256:
 d07149a8267b3788354ee5b0f0f760e3e6e34c5cf688632dc8fcfc4a0de783da 1556 
pcsx2_1.6.0+dfsg-2.1.dsc
 49109212d0ddb42f2b1033acefe40ec961cd9ba93557195a5800d94ad96a0d12 11876 
pcsx2_1.6.0+dfsg-2.1.debian.tar.xz
 e5302ab3f6db3ddeeb79f8a6931ef330d17ebe4bbc32a3aa38f4358efd5e0f5c 16579 

Bug#1068806: marked as done (Update Build-Depends for the time64 library renames)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 22:22:37 +
with message-id 
and subject line Bug#1068806: fixed in osmo-bts 1.5.0+dfsg1-3
has caused the Debian Bug report #1068806,
regarding Update Build-Depends for the time64 library renames
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osmo-bts
Version: 1.5.0dfsg1-2
Severity: serious
Tags: ftbfs

The package explicitly Build-Depends: libosmocoding0, this needs to be changed
to
libosmocoding0t64 if this dep is needed at all.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: osmo-bts
Source-Version: 1.5.0+dfsg1-3
Done: Thorsten Alteholz 

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated osmo-bts package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 22:03:03 +0200
Source: osmo-bts
Architecture: source
Version: 1.5.0+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Mobcom Maintainers 

Changed-By: Thorsten Alteholz 
Closes: 1068806
Changes:
 osmo-bts (1.5.0+dfsg1-3) unstable; urgency=medium
 .
   * debian/control: update dependencies for time_t transition
 (Closes: #1068806)
Checksums-Sha1:
 1e29704c601c25f7f15b1a5b8bb7c626971450dc 2335 osmo-bts_1.5.0+dfsg1-3.dsc
 49e76bfecec6917e1ceaaa4982da95052f8bd735 386932 
osmo-bts_1.5.0+dfsg1.orig.tar.xz
 e362f74ff30d003a159a32ac6d93dca5d8305de6 5484 
osmo-bts_1.5.0+dfsg1-3.debian.tar.xz
 6f12703c8b363fb505e1171357a159d70f87da30 8032 
osmo-bts_1.5.0+dfsg1-3_amd64.buildinfo
Checksums-Sha256:
 24eaa43534a3e4ddfc14fef147db60635f7393ef0ac96564fdbbf827e6224171 2335 
osmo-bts_1.5.0+dfsg1-3.dsc
 cd2094438206ab2d12e2a2afe195806c747435545bdded587a0caa29102c003b 386932 
osmo-bts_1.5.0+dfsg1.orig.tar.xz
 5383ea3b357db29c98b92cafbd219b162830eac2bb9b01c9a9cf3bbe380050bd 5484 
osmo-bts_1.5.0+dfsg1-3.debian.tar.xz
 52cb8b83a89cc23b7d1b8699cf47e4aec8124c06df2a05443c48d21969e29d2d 8032 
osmo-bts_1.5.0+dfsg1-3_amd64.buildinfo
Files:
 6c977c1f86458493336eac200a0dd33b 2335 net optional osmo-bts_1.5.0+dfsg1-3.dsc
 8d48d2ead6a3536b35ff3853d272d68d 386932 net optional 
osmo-bts_1.5.0+dfsg1.orig.tar.xz
 5fc6efa096f22c4209eeb3d312e707c4 5484 net optional 
osmo-bts_1.5.0+dfsg1-3.debian.tar.xz
 b0011d854c6bf5bf5061f671992c32d3 8032 net optional 
osmo-bts_1.5.0+dfsg1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmYYWL9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR7qfEACO5sLNFRgPWWCdm+xT74qROVMNWiDf
ZAXvqPEAG1RDOBFPbry1Tsuah+9MOZE0dxravEXm7vsdCQOhpCq9FZ0OHDzE96Ir
LBcAMCOYeuHupJCpN2I50v5KFRc8Tl2AiL/CsrnYqPIpB6fZoKkSHJ/un5rHsdu1
Jd2MBC5VprWVbvVGXkvutywvMSgY/jXsB0OYTTi/VA2dsaTltk09pppes9Vqlnlr
3SZiXO7XL2Jn0GJmT6j//lqE22MkWcd/gjtaZi7Uyofwo4X16XUhihHY2rS7iYpD
v4sGMhohebVmvPlWLehcBnkmOUKmzdD/QLaLRjO9j+GFsVykw0VmmU4s7NI/el4q
l2bMlLGAblNX3fWwOIBnPpUrbDBHVGFjY7cIsWT9KDvzAaNb+59yfucROoMlukB7
aVwRoe7IDn5/AsPqMPHBvWKBKpmlEwNlkaZ8cka/cxTIQrwahj5+25BSL3zyIOjb
HWe9ByntxoQb9PLmuM6MZDEjpe4L9fOYqDBCfwjvsWpFrr3XjqL1AZSyicuk2Uqm
mru4PQ8YjkZTi2YGCynKGsy6EBBPZf1YC+/vxFa6nVbMZu2tLZlq4LHdV4k74UB+
TyN1y5fmW+gvdnEi+xU8mQcwuiQDal2UAcw7crz4iuCAFHsuTrnElk8fi4oiEhi/

Bug#1067615: marked as done (FTBFS: error: size of array ‘dummyinfo_does_not_fit’ is negative)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 22:22:47 +
with message-id 
and subject line Bug#1067615: fixed in osmo-pcu 1.1.0-4
has caused the Debian Bug report #1067615,
regarding FTBFS: error: size of array ‘dummyinfo_does_not_fit’ is negative
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.)


-- 
1067615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osmo-pcu
Version: 1.1.0-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=osmo-
pcu=armel=1.1.0-3%2Bb2=1711272169=0

/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DPACKAGE_NAME=\"osmo-pcu\"
-DPACKAGE_TARNAME=\"osmo-pcu\" -DPACKAGE_VERSION=\"1.1.0\"
-DPACKAGE_STRING=\"osmo-pcu\ 1.1.0\" -DPACKAGE_BUGREPORT=\"osmocom-net-
g...@lists.osmocom.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"osmo-pcu\"
-DVERSION=\"1.1.0\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1
-DLT_OBJDIR=\".libs/\" -I.  -I../include -Wall -I/usr/include/ -pthread
-I/usr/include/ -pthread  -I/usr/include/ -pthread  -I/usr/include/ -pthread
-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 -std=gnu11 -c -o osmobts_sock.lo
osmobts_sock.c
In file included from /usr/include/osmocom/core/msgb.h:20,
 from llc.c:21:
llc.c: In function ‘llc_queue_enqueue’:
llc.c:145:9: error: size of array ‘dummyinfo_does_not_fit’ is negative
  145 | osmo_static_assert(sizeof(*meta_storage) <=
sizeof(llc_msg->cb), info_does_not_fit);
  | ^~


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: osmo-pcu
Source-Version: 1.1.0-4
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
osmo-pcu, 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.
Thorsten Alteholz  (supplier of updated osmo-pcu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 23:13:53 +0200
Source: osmo-pcu
Architecture: source
Version: 1.1.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Mobcom Maintainers 

Changed-By: Thorsten Alteholz 
Closes: 1067615
Changes:
 osmo-pcu (1.1.0-4) unstable; urgency=medium
 .
   * debian/control: add architecture-is-64-bit to build dependencies
 (Closes: #1067615)
Checksums-Sha1:
 48650919511f1ddf054c96778cb7984cc3b25646 2226 osmo-pcu_1.1.0-4.dsc
 28ff0071eb6571e5a4e500e15f63ad79bdfd2627 374756 osmo-pcu_1.1.0.orig.tar.xz
 73ed5dd5852063940b0e9724f16d088d9300f6d5 7332 osmo-pcu_1.1.0-4.debian.tar.xz
 2e03a402087d9b76e0159c55952430c526c860ba 7430 osmo-pcu_1.1.0-4_amd64.buildinfo
Checksums-Sha256:
 cb982adc023354a11fe432b4b45c1fc80f29f76bd8d33e00addff03d207b418d 2226 
osmo-pcu_1.1.0-4.dsc
 ccf6e664ea8e6a39a2633ce7be97113c0bc35c0d15e141e88fd277f973483940 374756 
osmo-pcu_1.1.0.orig.tar.xz
 290df60de375bd0a696537a7e86d4538b54a0664264543eb1fc16d4e865f55e7 7332 
osmo-pcu_1.1.0-4.debian.tar.xz
 5017c06304ab7d74f12d6bc48f601341e259258fc6ab02c159f86f8e33f522a1 7430 
osmo-pcu_1.1.0-4_amd64.buildinfo
Files:
 d1f8cf447b54ec0f024a081aba7910a1 2226 net optional osmo-pcu_1.1.0-4.dsc
 69055d80f1d5b303a96127d690c4cfe4 374756 net 

Processed: Re: prime-phylo: FTBFS: gb.tab.c:1096:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066653 [src:prime-phylo] prime-phylo: FTBFS: gb.tab.c:1096:16: error: 
implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1066653: prime-phylo: FTBFS: gb.tab.c:1096:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration]

[Zixing Liu]

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

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/fix-ftbfs-with-gcc13.patch: Fix missing headers and
missing prototypes.  Closes LP: #2061032.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-26-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru prime-phylo-1.0.11/debian/patches/fix-ftbfs-with-gcc13.patch 
prime-phylo-1.0.11/debian/patches/fix-ftbfs-with-gcc13.patch
--- prime-phylo-1.0.11/debian/patches/fix-ftbfs-with-gcc13.patch
1969-12-31 17:00:00.0 -0700
+++ prime-phylo-1.0.11/debian/patches/fix-ftbfs-with-gcc13.patch
2024-04-11 16:13:25.0 -0600
@@ -0,0 +1,54 @@
+Description: Fix missing headers and missing prototypes
+Author: Zixing Liu 
+Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/prime-phylo/+bug/2061032
+Forwarded: no
+Last-Update: 2024-04-11
+Index: prime-phylo/src/cxx/libraries/prime/NHXparse.y
+===
+--- prime-phylo.orig/src/cxx/libraries/prime/NHXparse.y
 prime-phylo/src/cxx/libraries/prime/NHXparse.y
+@@ -2,6 +2,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include "NHXnode.h"
+ #include "NHXtree.h"
+ #include "NHXannotation.h"
+@@ -14,7 +15,9 @@
+ /* #define YYERROR_VERBOSE */ 
+ 
+ /* Here comes some C declarations */
+-
++extern int yylex (void);
++extern void read_from_string(char *str);
++extern void close_string_buffer();
+ extern FILE *yytree_in;
+ extern char *yytree_text;
+ extern unsigned int lineno; /* Current line number in input file */
+Index: prime-phylo/src/cxx/libraries/sfile/gb.y
+===
+--- prime-phylo.orig/src/cxx/libraries/sfile/gb.y
 prime-phylo/src/cxx/libraries/sfile/gb.y
+@@ -23,7 +23,8 @@
+ #include "entry.h"
+ #include "sfile.h"
+ 
+-
++extern int yylex (void);
++unsigned linenumber();
+ static int yyerror();
+ 
+ #define YYDEBUG 1
+Index: prime-phylo/src/cxx/libraries/sfile/gbread.c
+===
+--- prime-phylo.orig/src/cxx/libraries/sfile/gbread.c
 prime-phylo/src/cxx/libraries/sfile/gbread.c
+@@ -3,6 +3,7 @@
+ 
+ extern int yydebug;
+ 
++#include 
+ #include "sfile.h"
+ #include "gb.tab.h"
+  
diff -Nru prime-phylo-1.0.11/debian/patches/series 
prime-phylo-1.0.11/debian/patches/series
--- prime-phylo-1.0.11/debian/patches/series2021-05-20 05:51:42.0 
-0600
+++ prime-phylo-1.0.11/debian/patches/series2024-04-11 16:10:29.0 
-0600
@@ -3,3 +3,4 @@
 fix-gcc-8.patch
 0003-Fix-build-with-Boost-1.67.patch
 0004-fix-gcc10-build.patch
+fix-ftbfs-with-gcc13.patch

Processed: pcsx2: diff for NMU version 1.6.0+dfsg-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1068194 + patch
Bug #1068194 [src:pcsx2] pcsx2: FTBFS: 
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:143:19: error: 
‘system_error’ in namespace ‘std’ does not name a type
Added tag(s) patch.

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

Bug#1068194: pcsx2: diff for NMU version 1.6.0+dfsg-2.1

[Sebastian Ramacher]

Control: tags 1068194 + patch


Dear maintainer,

I've prepared an NMU for pcsx2 (versioned as 1.6.0+dfsg-2.1). The diff
is attached to this message.

Regards.


-- 
Sebastian Ramacher
diff -Nru pcsx2-1.6.0+dfsg/debian/changelog pcsx2-1.6.0+dfsg/debian/changelog
--- pcsx2-1.6.0+dfsg/debian/changelog	2022-10-23 17:00:12.0 +0200
+++ pcsx2-1.6.0+dfsg/debian/changelog	2024-04-11 23:36:38.0 +0200
@@ -1,3 +1,13 @@
+pcsx2 (1.6.0+dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Mate Kukri ]
+  * d/p/cpp_error_ftbfs.patch: fix FTBFS by adding missing include for
+std::*_error types. (LP: #2048072) (Closes: #1068194)
+
+ -- Sebastian Ramacher   Thu, 11 Apr 2024 23:36:38 +0200
+
 pcsx2 (1.6.0+dfsg-2) unstable; urgency=medium
 
   * Team upload
diff -Nru pcsx2-1.6.0+dfsg/debian/patches/cpp_error_ftbfs.patch pcsx2-1.6.0+dfsg/debian/patches/cpp_error_ftbfs.patch
--- pcsx2-1.6.0+dfsg/debian/patches/cpp_error_ftbfs.patch	1970-01-01 01:00:00.0 +0100
+++ pcsx2-1.6.0+dfsg/debian/patches/cpp_error_ftbfs.patch	2024-04-11 23:35:30.0 +0200
@@ -0,0 +1,36 @@
+Description: Fix CDVD.cpp FTBFS by adding  include
+Author: Mate Kukri 
+Last-Update: 2024-01-04
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/plugins/cdvdGigaherz/src/CDVD.cpp
 b/plugins/cdvdGigaherz/src/CDVD.cpp
+@@ -18,6 +18,8 @@
+ #include 
+ #include 
+ #include 
++#include 
++#include 
+ #include "svnrev.h"
+ 
+ Settings g_settings;
+--- a/plugins/cdvdGigaherz/src/ReadThread.cpp
 b/plugins/cdvdGigaherz/src/ReadThread.cpp
+@@ -19,6 +19,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ const u32 sectors_per_read = 16;
+ 
+--- a/plugins/cdvdGigaherz/src/Unix/LinuxIOCtlSrc.cpp
 b/plugins/cdvdGigaherz/src/Unix/LinuxIOCtlSrc.cpp
+@@ -23,6 +23,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ IOCtlSrc::IOCtlSrc(decltype(m_filename) filename)
+ : m_filename(filename)
diff -Nru pcsx2-1.6.0+dfsg/debian/patches/series pcsx2-1.6.0+dfsg/debian/patches/series
--- pcsx2-1.6.0+dfsg/debian/patches/series	2022-10-23 13:49:04.0 +0200
+++ pcsx2-1.6.0+dfsg/debian/patches/series	2024-04-11 23:35:30.0 +0200
@@ -1 +1,2 @@
 wxwidgets3.2.patch
+cpp_error_ftbfs.patch

Bug#1067654: marked as done (tpm2-abrmd: Tests fail on 32-bit t64 arches)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 21:51:02 +
with message-id 
and subject line Bug#1067654: fixed in tpm2-abrmd 3.0.0-1.1
has caused the Debian Bug report #1067654,
regarding tpm2-abrmd: Tests fail on 32-bit t64 arches
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.)


-- 
1067654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tpm2-abrmd
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * Disable testsuite on armhf for now (the mocking the test harness
does fails when _FILE_BITS == 64).

This is very similar to 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067418

Thanks for considering the patch.


-- 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-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru tpm2-abrmd-3.0.0/debian/control tpm2-abrmd-3.0.0/debian/control
diff -Nru tpm2-abrmd-3.0.0/debian/rules tpm2-abrmd-3.0.0/debian/rules
--- tpm2-abrmd-3.0.0/debian/rules   2022-12-12 12:42:50.0 +1300
+++ tpm2-abrmd-3.0.0/debian/rules   2024-03-25 20:21:21.0 +1300
@@ -4,9 +4,14 @@
 export DEB_CFLAGS_MAINT_APPEND  = -Wall
 
 # Some variables:
+DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 DEB_HOST_ARCH_OS  ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
 DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU)
 
+ifeq ($(DEB_HOST_ARCH),armhf)
+DEB_BUILD_OPTIONS+=nocheck
+endif
+
 %:
dh $@ --exclude=.la --with autoreconf
 
--- End Message ---
--- Begin Message ---
Source: tpm2-abrmd
Source-Version: 3.0.0-1.1
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
tpm2-abrmd, 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.
Sebastian Ramacher  (supplier of updated tpm2-abrmd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 23:12:31 +0200
Source: tpm2-abrmd
Architecture: source
Version: 3.0.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: SZ Lin (林上智) 
Changed-By: Sebastian Ramacher 
Closes: 1067654
Changes:
 tpm2-abrmd (3.0.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Michael Hudson-Doyle ]
   * Disable testsuite on armhf for now (the mocking the test harness
 does fails when _FILE_BITS == 64) (Closes: #1067654).
Checksums-Sha1:
 46981697975709c9514973626cc09742e5040c52 1680 tpm2-abrmd_3.0.0-1.1.dsc
 ee42c77d4d90a61e54e0ab024f0b70a93b156ca2 5516 
tpm2-abrmd_3.0.0-1.1.debian.tar.xz
 a1c617df4219f608970f14d9b9456dcfa68ac36a 7638 
tpm2-abrmd_3.0.0-1.1_source.buildinfo
Checksums-Sha256:
 fe03440fe31ce30d960c27cd0178565246b9982408a2c4f7c3cd7d77372f5582 1680 
tpm2-abrmd_3.0.0-1.1.dsc
 7e103e934368d07c4c14bed1f53b9654d7d5aa19e8e6fcbd7d8bb08999504bf7 5516 
tpm2-abrmd_3.0.0-1.1.debian.tar.xz
 b009034b74a12e85ed7dcea48fcb2bad4980f4bf96e33dfaf74a685b047f33f9 7638 
tpm2-abrmd_3.0.0-1.1_source.buildinfo
Files:
 4fad73a52a9b4b9698c764651671b6b3 1680 net optional tpm2-abrmd_3.0.0-1.1.dsc
 7cd0be12c9f375b4661d74cb3840dd78 5516 net optional 
tpm2-abrmd_3.0.0-1.1.debian.tar.xz
 e0542738c57cab22235b84ae753fae04 7638 net optional 
tpm2-abrmd_3.0.0-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZhhT1wAKCRAhk2s2YA/N

Bug#1067830: marked as done (gri: FTBFS on arm{el,hf}: gr.cc:426:22: error: cannot convert ‘long int*’ to ‘time_t*’ {aka ‘long long int*’})

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 21:49:33 +
with message-id 
and subject line Bug#1067830: fixed in gri 2.12.27-1.2
has caused the Debian Bug report #1067830,
regarding gri: FTBFS on arm{el,hf}: gr.cc:426:22: error: cannot convert ‘long 
int*’ to ‘time_t*’ {aka ‘long long int*’}
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gri
Version: 2.12.27-1.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=gri=armel=2.12.27-1.1%2Bb2=1711504387=0

g++ -DDEFAULT_GRI_DIR=\"/usr/share/gri/2.12.27/\"  -DPACKAGE_NAME=\"gri\" 
-DPACKAGE_TARNAME=\"gri\" -DPACKAGE_VERSION=\"2.12.27\" -DPACKAGE_STRING=\"gri\ 
2.12.27\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"gri\" 
-DVERSION=\"2.12.27\" -DGRI_IS_BIG_ENDIAN=1 -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 
-DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 
-DHAVE_UNISTD_H=1 -DHAVE_LIBNETCDF=1 -DHAVE_LIBREADLINE=1 -DHAVE_ISNAN=1 
-DHAVE_ISINF=1 -DHAVE_ACOSH=1 -DHAVE_GETCWD=1 -DHAVE_POPEN=1 -DHAVE_MKSTEMP=1 
-DHAVE_TMPNAM=1 -DHAVE_TEMPNAM=1 -DHAVE_GETHOSTNAME=1 -DHAVE_ACCESS=1 
-DHAVE_LSTAT=1 -DHAVE_STAT=1 -DHAVE_STRERROR=1 -DHAVE_GETENV=1 -DHAVE_DRAND48=1 
-I.   -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -DCPLUSPLUSNEW -I/usr/include -O2 -c -o gr.o gr.cc
gr.cc: In function ‘void insert_ps_header(FILE*, bool)’:
gr.cc:426:22: error: cannot convert ‘long int*’ to ‘time_t*’ {aka ‘long long 
int*’}
  426 | time();
  |  ^~~~
  |  |
  |  long int*
In file included from /usr/include/features.h:490,
 from /usr/include/ctype.h:25,
 from gr.cc:31:
/usr/include/time.h:86:15: note:   initializing argument 1 of ‘time_t 
time(time_t*)’
   86 | extern time_t __REDIRECT_NTH (time, (time_t *__timer), __time64);
  |   ^~
gr.cc:427:71: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const 
long long int*’}
  427 | fprintf(fp, "CreationDate: %s", 
asctime(localtime()));
  |   
^~~~
  |   |
  |   
long int*
/usr/include/time.h:141:19: note:   initializing argument 1 of ‘tm* 
localtime(const time_t*)’
  141 | extern struct tm *__REDIRECT_NTH (localtime, (const time_t *__timer),
  |   ^~
make[2]: *** [Makefile:610: gr.o] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gri
Source-Version: 2.12.27-1.2
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
gri, 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.
Sebastian Ramacher  (supplier of updated gri package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 23:23:28 +0200
Source: gri
Architecture: source
Version: 2.12.27-1.2
Distribution: unstable
Urgency: medium
Maintainer: Peter S Galbraith 
Changed-By: Sebastian Ramacher 
Closes: 1067830
Changes:
 gri (2.12.27-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches: Apply upstream patch to fix build with 64 bit time_t on
 armel and armhf. (Closes: #1067830)
Checksums-Sha1:
 222f38776c073420df6291407d4860e851a40d3f 1366 gri_2.12.27-1.2.dsc
 2079459a9852d1478d267579508f80bc53a7df26 19188 gri_2.12.27-1.2.debian.tar.xz
 1fef1015eb6f3b932fc6f69d4896e199aa787045 9767 gri_2.12.27-1.2_source.buildinfo
Checksums-Sha256:
 

Processed: gri: diff for NMU version 2.12.27-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1067830 + patch
Bug #1067830 [src:gri] gri: FTBFS on arm{el,hf}: gr.cc:426:22: error: cannot 
convert ‘long int*’ to ‘time_t*’ {aka ‘long long int*’}
Added tag(s) patch.

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

Bug#1067830: gri: diff for NMU version 2.12.27-1.2

[Sebastian Ramacher]

Control: tags 1067830 + patch

Dear maintainer,

I've prepared an NMU for gri (versioned as 2.12.27-1.2). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru gri-2.12.27/debian/changelog gri-2.12.27/debian/changelog
--- gri-2.12.27/debian/changelog	2022-08-25 18:33:47.0 +0200
+++ gri-2.12.27/debian/changelog	2024-04-11 23:23:28.0 +0200
@@ -1,3 +1,11 @@
+gri (2.12.27-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Apply upstream patch to fix build with 64 bit time_t on
+armel and armhf. (Closes: #1067830)
+
+ -- Sebastian Ramacher   Thu, 11 Apr 2024 23:23:28 +0200
+
 gri (2.12.27-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gri-2.12.27/debian/patches/fix-build-with-t64.patch gri-2.12.27/debian/patches/fix-build-with-t64.patch
--- gri-2.12.27/debian/patches/fix-build-with-t64.patch	1970-01-01 01:00:00.0 +0100
+++ gri-2.12.27/debian/patches/fix-build-with-t64.patch	2024-04-11 23:22:33.0 +0200
@@ -0,0 +1,40 @@
+From 4d93a4e76543b914400d9e425e7c2de5c9dbb58d Mon Sep 17 00:00:00 2001
+From: dankelley 
+Date: Fri, 5 Apr 2024 07:10:17 -0300
+Subject: [PATCH] possibly fix debian error on time_t
+
+I am a bit concerned that this may break gri on other platforms, but not
+really very concerned, since this fiddling with time types is likely
+irrelevant to modern machines.  And I doubt that anybody is building gri
+on some of the platforms for which the code is making special cases.
+
+Please note that I do not have access to a machine that reproduces the
+error message.  I am on macos, and don't want to break my toolchain by
+over-writing my C++ compilers, etc., to try to reproduce the bug.
+
+Lacking access to any type of linux machine, I am not able to test
+whether my change fixes the problem. But the `git diff` is only one line
+long, so hopefully if there is still a problem on debian, someone can
+tell me a preprocesser symbol that I can use (and perhaps a header.h
+file I can specify) to define the `time_t` type.
+
+Sorry for the hassles.
+
+Dan Kelley
+---
+ src/gr.hh | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/gr.hh b/src/gr.hh
+index 6ff2f20..97b1756 100644
+--- a/src/gr.hh
 b/src/gr.hh
+@@ -395,7 +395,7 @@ double lapse_rate(double S, double t, double p);
+ #if defined(__DECCXX)
+ #define SECOND_TYPE int
+ #else
+-#define SECOND_TYPE long
++#define SECOND_TYPE time_t
+ #endif
+ #endif
+ 
diff -Nru gri-2.12.27/debian/patches/series gri-2.12.27/debian/patches/series
--- gri-2.12.27/debian/patches/series	2022-08-25 18:33:47.0 +0200
+++ gri-2.12.27/debian/patches/series	2024-04-11 23:22:47.0 +0200
@@ -1 +1,2 @@
 imagemagick.patch
+fix-build-with-t64.patch

Bug#1067418: marked as done (Tests fail on 32-bit t64 arches)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 21:21:59 +
with message-id 
and subject line Bug#1067418: fixed in tpm2-tss 4.0.1-7.2
has caused the Debian Bug report #1067418,
regarding Tests fail on 32-bit t64 arches
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.)


-- 
1067418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tpm2-tss
Version: 4.0.1-7.1
Severity: serious
Tags: upstream ftbfs

Control: forwarded -1 https://github.com/tpm2-software/tpm2-tss/issues/2786

The package FTBFS on armel/armhf/powerpc, see e.g.
https://buildd.debian.org/status/fetch.php?pkg=tpm2-tss=armhf=4.0.1-7.1=1711016838=0
or the linked upstream bug report.


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: tpm2-tss
Source-Version: 4.0.1-7.2
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
tpm2-tss, 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.
Sebastian Ramacher  (supplier of updated tpm2-tss package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 23:02:54 +0200
Source: tpm2-tss
Architecture: source
Version: 4.0.1-7.2
Distribution: unstable
Urgency: medium
Maintainer: Mathieu Trudel-Lapierre 
Changed-By: Sebastian Ramacher 
Closes: 1067418
Changes:
 tpm2-tss (4.0.1-7.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches: Apply upstream patch to skip tests which fail on 32-bit
 with _FILE_BITS=64 (Closes: #1067418)
Checksums-Sha1:
 eb816f50c5e260f23b5ba77bb4cc4ff19bee0166 2699 tpm2-tss_4.0.1-7.2.dsc
 a2001f50b31238441ef735e7df18cbfa65e82c78 20336 tpm2-tss_4.0.1-7.2.debian.tar.xz
 011af6aaff6dd66ed63b885641d1affce3a083f4 6937 
tpm2-tss_4.0.1-7.2_source.buildinfo
Checksums-Sha256:
 0c39c269c0342d38ac735ca7894300daa3b91a5f44f72169845433b0afd8e653 2699 
tpm2-tss_4.0.1-7.2.dsc
 c594a5d35f482cf93b8e8181b43806e1f1314c492240c150d40c5a4dbe9f9488 20336 
tpm2-tss_4.0.1-7.2.debian.tar.xz
 342148be9e6185a16bb1cfdb83b5bb058cd7e48dc9753c9f9ef7ec230350641e 6937 
tpm2-tss_4.0.1-7.2_source.buildinfo
Files:
 b348623059a75dd7df5e6b486b21320d 2699 libs optional tpm2-tss_4.0.1-7.2.dsc
 bc39b59eabe1e820e11da551504252d4 20336 libs optional 
tpm2-tss_4.0.1-7.2.debian.tar.xz
 c46f77595494656616a8fa36ddfb40eb 6937 libs optional 
tpm2-tss_4.0.1-7.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZhhRWQAKCRAhk2s2YA/N
iT4HAPwJkunCsebYF5FULaQrKaUbJN2m22twqhd5lvS8VjednQEAjVnmNvPxQ91G
favalG8dPmCMMl1ozrj6W7Qug2mXXw4=
=JOf0
-END PGP SIGNATURE-



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

Bug#1067654: tpm2-abrmd: diff for NMU version 3.0.0-1.1

[Sebastian Ramacher]

Dear maintainer,

I've prepared an NMU for tpm2-abrmd (versioned as 3.0.0-1.1). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru tpm2-abrmd-3.0.0/debian/changelog tpm2-abrmd-3.0.0/debian/changelog
--- tpm2-abrmd-3.0.0/debian/changelog	2022-12-12 00:47:34.0 +0100
+++ tpm2-abrmd-3.0.0/debian/changelog	2024-04-11 23:12:31.0 +0200
@@ -1,3 +1,13 @@
+tpm2-abrmd (3.0.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Michael Hudson-Doyle ]
+  * Disable testsuite on armhf for now (the mocking the test harness
+does fails when _FILE_BITS == 64) (Closes: #1067654).
+
+ -- Sebastian Ramacher   Thu, 11 Apr 2024 23:12:31 +0200
+
 tpm2-abrmd (3.0.0-1) unstable; urgency=low
 
   [ Debian Janitor ]
diff -Nru tpm2-abrmd-3.0.0/debian/rules tpm2-abrmd-3.0.0/debian/rules
--- tpm2-abrmd-3.0.0/debian/rules	2022-12-12 00:42:50.0 +0100
+++ tpm2-abrmd-3.0.0/debian/rules	2024-04-11 23:12:31.0 +0200
@@ -4,9 +4,14 @@
 export DEB_CFLAGS_MAINT_APPEND  = -Wall
 
 # Some variables:
+DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 DEB_HOST_ARCH_OS  ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
 DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU)
 
+ifneq (,$(filter armhf armel,$(DEB_HOST_ARCH)))
+DEB_BUILD_OPTIONS+=nocheck
+endif
+
 %:
 	dh $@ --exclude=.la --with autoreconf
 

Processed: Re: pike8.0: FTBFS: zlibmod.c:1235:5: error: implicit declaration of function ‘pop_n_elems’ [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066378 [src:pike8.0] pike8.0: FTBFS: zlibmod.c:1235:5: error: implicit 
declaration of function ‘pop_n_elems’ [-Werror=implicit-function-declaration]
Ignoring request to alter tags of bug #1066378 to the same tags previously set

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

Bug#1066378: pike8.0: FTBFS: zlibmod.c:1235:5: error: implicit declaration of function ‘pop_n_elems’ [-Werror=implicit-function-declaration]

[Zixing Liu]

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

Dear Maintainer,

This is an update to the previous patch that contains further fixes to the
package.

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/gz_test_fix.patch: Fix zlib detection logic.
  * debian/patches/threads_undefined_var_fix.patch: Fix incorrect
variable referencing in threads.c.  Closes LP: #2061023.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-26-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru pike8.0-8.0.1738/debian/patches/gz_test_fix.patch 
pike8.0-8.0.1738/debian/patches/gz_test_fix.patch
--- pike8.0-8.0.1738/debian/patches/gz_test_fix.patch   1969-12-31 
17:00:00.0 -0700
+++ pike8.0-8.0.1738/debian/patches/gz_test_fix.patch   2024-04-11 
14:31:45.0 -0600
@@ -0,0 +1,18 @@
+Description: Fix zlib detection logic
+ Fixes the issue where vendored zlib fails to compile on armhf
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066378
+Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/pike8.0/+bug/2061023
+Forwarded: no
+Last-Update: 2024-04-11
+--- pike8.0-8.0.1738.orig/src/modules/Gz/gz_test.c
 pike8.0-8.0.1738/src/modules/Gz/gz_test.c
+@@ -320,6 +320,8 @@ void test_sync(compr, comprLen, uncompr,
+ err = inflateSync(_stream);   /* but skip the damaged part */
+ CHECK_ERR(err, "inflateSync");
+ 
++inflateEnd(_stream);
++inflateInit(_stream);
+ err = inflate(_stream, Z_FINISH);
+ if (err != Z_DATA_ERROR) {
+ fprintf(stderr, "inflate should report DATA_ERROR\n");
diff -Nru pike8.0-8.0.1738/debian/patches/series 
pike8.0-8.0.1738/debian/patches/series
--- pike8.0-8.0.1738/debian/patches/series  2022-04-18 11:30:23.0 
-0600
+++ pike8.0-8.0.1738/debian/patches/series  2024-04-11 14:33:12.0 
-0600
@@ -13,3 +13,5 @@
 undefined_htons.patch
 bad_size_t_redef.patch
 dont_disable_debug_symbols.patch
+gz_test_fix.patch
+threads_undefined_var_fix.patch
diff -Nru pike8.0-8.0.1738/debian/patches/threads_undefined_var_fix.patch 
pike8.0-8.0.1738/debian/patches/threads_undefined_var_fix.patch
--- pike8.0-8.0.1738/debian/patches/threads_undefined_var_fix.patch 
1969-12-31 17:00:00.0 -0700
+++ pike8.0-8.0.1738/debian/patches/threads_undefined_var_fix.patch 
2024-04-11 14:33:12.0 -0600
@@ -0,0 +1,16 @@
+Description: Fix incorrect variable referencing in threads.c
+Author: Zixing Liu 
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/pike8.0/+bug/2061023
+Forwarded: no
+Last-Update: 2024-04-11
+--- pike8.0-8.0.1738.orig/src/threads.c
 pike8.0-8.0.1738/src/threads.c
+@@ -3422,7 +3422,7 @@ static TH_RETURN_TYPE farm(void *_a)
+ int current = prctl(PR_GET_DUMPABLE);
+ #endif
+ #ifdef HAVE_BROKEN_LINUX_THREAD_EUID
+-if( setegid(arg.egid) != 0 || seteuid(arg.euid) != 0 )
++if( setegid(me->egid) != 0 || seteuid(me->euid) != 0 )
+ {
+   fprintf (stderr, "%s:%d: Unexpected error from setegid(2). errno=%d\n",
+  __FILE__, __LINE__, errno);

Processed: tpm2-tss: diff for NMU version 4.0.1-7.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1067418 + patch
Bug #1067418 [src:tpm2-tss] Tests fail on 32-bit t64 arches
Added tag(s) patch.

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

Bug#1067418: tpm2-tss: diff for NMU version 4.0.1-7.2

[Sebastian Ramacher]

Control: tags 1067418 + patch

Dear maintainer,

I've prepared an NMU for tpm2-tss (versioned as 4.0.1-7.2). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru tpm2-tss-4.0.1/debian/changelog tpm2-tss-4.0.1/debian/changelog
--- tpm2-tss-4.0.1/debian/changelog	2024-02-29 19:28:02.0 +0100
+++ tpm2-tss-4.0.1/debian/changelog	2024-04-11 23:02:54.0 +0200
@@ -1,3 +1,11 @@
+tpm2-tss (4.0.1-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Apply upstream patch to skip tests which fail on 32-bit
+with _FILE_BITS=64 (Closes: #1067418)
+
+ -- Sebastian Ramacher   Thu, 11 Apr 2024 23:02:54 +0200
+
 tpm2-tss (4.0.1-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru tpm2-tss-4.0.1/debian/patches/series tpm2-tss-4.0.1/debian/patches/series
--- tpm2-tss-4.0.1/debian/patches/series	2024-01-25 14:46:19.0 +0100
+++ tpm2-tss-4.0.1/debian/patches/series	2024-04-11 23:02:01.0 +0200
@@ -4,3 +4,4 @@
 0004-tss2-tcti-tcti-libtpms-fix-test-failure-on-big-endia.patch
 fix-tcti-spi-helper-big-endian.patch
 disable-tests-on-big-endian.patch
+skip-tests-which-fail-on-32-bit.patch
diff -Nru tpm2-tss-4.0.1/debian/patches/skip-tests-which-fail-on-32-bit.patch tpm2-tss-4.0.1/debian/patches/skip-tests-which-fail-on-32-bit.patch
--- tpm2-tss-4.0.1/debian/patches/skip-tests-which-fail-on-32-bit.patch	1970-01-01 01:00:00.0 +0100
+++ tpm2-tss-4.0.1/debian/patches/skip-tests-which-fail-on-32-bit.patch	2024-04-11 23:02:09.0 +0200
@@ -0,0 +1,120 @@
+From 932b1e78047ed0ddc09fcb06bff2e7cf96406976 Mon Sep 17 00:00:00 2001
+From: Juergen Repp 
+Date: Sun, 17 Mar 2024 10:43:19 +0100
+Subject: [PATCH] unit tests:  skip tests which fail on 32-bit with
+ _FILE_BITS=64
+
+Tests file the unit tests are compiled with _FILE_BITS is set to 64.
+The tests work without problems if _FILE_BITS is not set.
+Addresses: #2786
+
+Signed-off-by: Juergen Repp 
+---
+ MAINTAINERS.md   |  2 +-
+ test/unit/fapi-io.c  |  7 +++
+ test/unit/tcti-device.c  | 11 +++
+ test/unit/tcti-libtpms.c |  8 
+ test/unit/tcti-pcap.c| 11 +++
+ 5 files changed, 38 insertions(+), 1 deletion(-)
+
+--- a/test/unit/fapi-io.c
 b/test/unit/fapi-io.c
+@@ -28,6 +28,7 @@
+ #define LOGMODULE tests
+ #include "util/log.h"
+ 
++#define EXIT_SKIP 77
+ /*
+  * The unit tests will simulate error codes which can be returned by the
+  * system calls for file system IO.
+@@ -364,6 +365,12 @@
+ int
+ main(int argc, char *argv[])
+ {
++#if _FILE_OFFSET_BITS == 64
++// Would produce cmocka error
++LOG_WARNING("_FILE_OFFSET == 64 would produce cmocka errors.");
++return EXIT_SKIP;
++#endif
++
+ const struct CMUnitTest tests[] = {
+ };
+ return cmocka_run_group_tests(tests, NULL, NULL);
+--- a/test/unit/tcti-device.c
 b/test/unit/tcti-device.c
+@@ -25,6 +25,11 @@
+ #include "tss2-tcti/tcti-common.h"
+ #include "tss2-tcti/tcti-device.h"
+ 
++#define LOGMODULE tests
++#include "util/log.h"
++
++#define EXIT_SKIP 77
++
+ /*
+  * Size of the TPM2 buffer used in these tests. In some cases this will be
+  * the command sent (transmit tests) and in others it's used as the response
+@@ -443,6 +448,12 @@
+ int
+ main(int argc, char* argv[])
+ {
++#if _FILE_OFFSET_BITS == 64
++// Would produce cmocka error
++LOG_WARNING("_FILE_OFFSET == 64 would produce cmocka errors.");
++return EXIT_SKIP;
++#endif
++
+ const struct CMUnitTest tests[] = {
+ cmocka_unit_test (tcti_device_init_all_null_test),
+ cmocka_unit_test(tcti_device_init_size_test),
+--- a/test/unit/tcti-libtpms.c
 b/test/unit/tcti-libtpms.c
+@@ -28,6 +28,8 @@
+ #define LOGMODULE test
+ #include "util/log.h"
+ 
++#define EXIT_SKIP 77
++
+ #define LIBTPMS_DL_HANDLE  0x12345678
+ #define STATEFILE_PATH "statefile.bin"
+ #define STATEFILE_FD   0xAABB
+@@ -1612,6 +1614,12 @@
+ main(int   argc,
+  char *argv[])
+ {
++#if _FILE_OFFSET_BITS == 64
++// Would produce cmocka error
++LOG_WARNING("_FILE_OFFSET == 64 would produce cmocka errors.");
++return EXIT_SKIP;
++#endif
++
+ const struct CMUnitTest tests[] = {
+ cmocka_unit_test(tcti_libtpms_init_all_null_test),
+ cmocka_unit_test(tcti_libtpms_init_dlopen_fail_test),
+--- a/test/unit/tcti-pcap.c
 b/test/unit/tcti-pcap.c
+@@ -27,6 +27,11 @@
+ #include "tss2-tcti/tcti-common.h"
+ #include "tss2-tcti/tcti-pcap.h"
+ 
++#define LOGMODULE tests
++#include "util/log.h"
++
++#define EXIT_SKIP 77
++
+ #if (__BYTE_ORDER__ == __ORDER_BIG_ENDIAN__)
+ #define _LE32TOH(a,b,c,d) d,c,b,a
+ #define _LE16TOH(a,b) b,a
+@@ -726,6 +731,12 @@
+ main (int   argc,
+   char *argv[])
+ {
++#if _FILE_OFFSET_BITS == 64
++// Would produce cmocka error
++LOG_WARNING("_FILE_OFFSET == 64 would produce cmocka errors.");
++return EXIT_SKIP;
++#endif
++
+ const struct CMUnitTest tests[] = {
+ cmocka_unit_test 

Bug#1066378: pike8.0: FTBFS: zlibmod.c:1235:5: error: implicit declaration of function ‘pop_n_elems’ [-Werror=implicit-function-declaration]

[Zixing Liu]

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

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/gz_test_fix.patch: Fix zlib detection logic.  Closes
LP: #2061023.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-26-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru pike8.0-8.0.1738/debian/patches/gz_test_fix.patch 
pike8.0-8.0.1738/debian/patches/gz_test_fix.patch
--- pike8.0-8.0.1738/debian/patches/gz_test_fix.patch   1969-12-31 
17:00:00.0 -0700
+++ pike8.0-8.0.1738/debian/patches/gz_test_fix.patch   2024-04-11 
14:31:45.0 -0600
@@ -0,0 +1,18 @@
+Description: Fix zlib detection logic
+ Fixes the issue where vendored zlib fails to compile on armhf
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066378
+Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/pike8.0/+bug/2061023
+Forwarded: no
+Last-Update: 2024-04-11
+--- pike8.0-8.0.1738.orig/src/modules/Gz/gz_test.c
 pike8.0-8.0.1738/src/modules/Gz/gz_test.c
+@@ -320,6 +320,8 @@ void test_sync(compr, comprLen, uncompr,
+ err = inflateSync(_stream);   /* but skip the damaged part */
+ CHECK_ERR(err, "inflateSync");
+ 
++inflateEnd(_stream);
++inflateInit(_stream);
+ err = inflate(_stream, Z_FINISH);
+ if (err != Z_DATA_ERROR) {
+ fprintf(stderr, "inflate should report DATA_ERROR\n");
diff -Nru pike8.0-8.0.1738/debian/patches/series 
pike8.0-8.0.1738/debian/patches/series
--- pike8.0-8.0.1738/debian/patches/series  2022-04-18 11:30:23.0 
-0600
+++ pike8.0-8.0.1738/debian/patches/series  2024-04-11 14:19:11.0 
-0600
@@ -13,3 +13,4 @@
 undefined_htons.patch
 bad_size_t_redef.patch
 dont_disable_debug_symbols.patch
+gz_test_fix.patch

Processed: Re: pike8.0: FTBFS: zlibmod.c:1235:5: error: implicit declaration of function ‘pop_n_elems’ [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066378 [src:pike8.0] pike8.0: FTBFS: zlibmod.c:1235:5: error: implicit 
declaration of function ‘pop_n_elems’ [-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1066313: fixed upstream

[micah anderson]

These issues are fixed upstream in main, but there is not a release.

The fix is in commit 1171bf2fd4e7a0cab02cf5fca59090b65af9cd29.

Clément would you pull that fix into the package to resolve this FTBFS?

Processed: block 1036884 with 1068078

[Debian Bug Tracking System]

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

> block 1036884 with 1068078
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1065787 1068325 1067288 1065940 1067171 1055352 1067829 
1068160 1067494 1067509 1055530 1066328 1067676 1066794 1066134 1067192 1067916 
1065816 1067170 1068068 1067508 1067272 1065790 1065973 1066049 1065725 1067189 
1067190 1067069 1067458 1067193 1068586 1067677 1068327 1067175 1062847 1067561
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1068078
> thanks
Stopping processing here.

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

Processed: tagging 1066851

[Debian Bug Tracking System]

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

> tags 1066851 + ftbfs
Bug #1066851 [src:raku-readline] don't hard-code the name of the shared library
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: block 1036884 with 1065725

[Debian Bug Tracking System]

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

> block 1036884 with 1065725
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1067677 1067288 1066134 1067272 1055530 1067509 1065816 
1067561 1065787 1068325 1065973 1066328 1067190 1065790 1067494 1062847 1067508 
1067916 1066794 1065940 1067193 1067189 1068327 1068586 1067069 1067175 1068068 
1067676 1068160 1067829 1067458 1055352 1066049 1067170 1067192 1067171
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1065725
> thanks
Stopping processing here.

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

Bug#1068811: marked as done (camv-rnd: hardcoded librnd4 dependency)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 19:49:13 +
with message-id 
and subject line Bug#1068811: fixed in camv-rnd 1.1.4-2
has caused the Debian Bug report #1068811,
regarding camv-rnd: hardcoded librnd4 dependency
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.)


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

Package: camv-rnd
Version: 1.1.4-1
Severity: serious
Tags: patch


Hello, I found that librnd4 is correctly evaluated from shlibs:Depends in the 
core library and then it can be dropped also on core reverse-dependencies.


Please drop it.


Thanks for considering the patch.

diff -Nru camv-rnd-1.1.4/debian/control camv-rnd-1.1.4/debian/control
--- camv-rnd-1.1.4/debian/control   2023-11-30 16:53:21.0 +0100
+++ camv-rnd-1.1.4/debian/control   2024-04-11 15:44:20.0 +0200
@@ -47,7 +47,7 @@
 Architecture: any
 Replaces: camv-rnd (<< 1.1.0-1)
 Breaks: camv-rnd (<< 1.1.0-1)
-Depends: ${misc:Depends}, ${shlibs:Depends}, librnd4, librnd4-lib-gui
+Depends: ${misc:Depends}, ${shlibs:Depends}, librnd4-lib-gui
 Description: camv-rnd executable with the core functionality and boxsym-rnd
  Includes the data model, the most common action commands, the native
  file format. Can be used in headless mode or batch/scripted mode for
@@ -56,7 +56,7 @@
 
 Package: camv-rnd-export-vector

 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, camv-rnd-core (= 
${binary:Version}), librnd4
+Depends: ${misc:Depends}, ${shlibs:Depends}, camv-rnd-core (= 
${binary:Version})
 Description: Export formats: vector graphics
  Common vector graphic export formats: ps, eps, svg.
 


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: camv-rnd
Source-Version: 1.1.4-2
Done: Bdale Garbee 

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

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

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

Debian distribution maintenance software
pp.
Bdale Garbee  (supplier of updated camv-rnd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 13:19:17 -0600
Source: camv-rnd
Architecture: source
Version: 1.1.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Bdale Garbee 
Closes: 1068811
Changes:
 camv-rnd (1.1.4-2) unstable; urgency=medium
 .
   * add Suggests for other Ringdove applications
   * update Vcs entries for new subgroup on salsa
   * remove redundant hard-coded librnd4 dependency, closes: #1068811
Checksums-Sha1:
 94fc383dcf35c6f69b563c4bb9ca1177765dffec 2492 camv-rnd_1.1.4-2.dsc
 0a06ce7925e162ddd3985a15c419a13d7b198b64 4284 camv-rnd_1.1.4-2.debian.tar.xz
 1eac9162555f935e9e701aedb2e6c37c0398fe31 12231 camv-rnd_1.1.4-2_amd64.buildinfo
Checksums-Sha256:
 481fe66249fcc29a8312c305fc7e8ea7798c373299726f709e5aa3d303030851 2492 
camv-rnd_1.1.4-2.dsc
 a29c5b8da5908f08b91acbe8853faf1b4b83e78d47f302507fa099ca50d334ee 4284 
camv-rnd_1.1.4-2.debian.tar.xz
 5fea1cfe45dc9e00db7d13887a7db773d9f45d1c3c55c69c9e09a9190bed 12231 
camv-rnd_1.1.4-2_amd64.buildinfo
Files:
 5dcc59ee242edcc841142dd3e164857a 2492 electronics optional camv-rnd_1.1.4-2.dsc
 e7a90acaffa09f18676ed7e13b5ab263 4284 electronics optional 
camv-rnd_1.1.4-2.debian.tar.xz
 a56e79e867b9967e9e1960e028e512ae 12231 electronics optional 
camv-rnd_1.1.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAmYYO0kACgkQtwRxBYML
n6Er4hAAk/w1CscWv/m70Lc+kY5rkG2jAJIHIV0ybic+deAEduLgW7w6kk+47aZR
v1CMBO5+S0vp3H7ho0BvoEtwPDAoj1vNbBGUmltbRG4uE74oZ8qiT+kpl9GDAoIh
EJ2Zo9uMTdcWMsOPfP7b6O85hJRvDckWQNKwrDtSuknFCEiMZ3IBtprt0xOYCYv2
sy+laS3jzyUYD/sfhAGdPLZtK6UCnsNwoGVJ0FvXNtGOlv6RSfC0Q6pj2bV+xvXh
N8dLlFeEb89Pz+HJbBC4JgpXj4bZx0pH/yPv6y93GCy4nc6Rs/JH9nx6Wq2RaM3Y
RP6tdhu1WUxhXqBIrj7OzeJs8+6p6ze7IQTwuvwbKFToEJjro0ylDgHSuiUAT5uT
nb4+rjNV/V4qp63NV29Svx2kpr/PRw7QX2vReInBFd36BcSUARBSqe4RNauO0xim
qA6Z4FENbOfpWYxnEHjkGt05PfSF4pfitCVXY97vLiitTdtaZo9gYIUsPwYhQ/nF

Processed: Re: [Pkg-electronics-devel] Bug#1068812: pcb-rnd: hardcoded librnd4 dependency

[Debian Bug Tracking System]

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

> severity 1068812 minor
Bug #1068812 [pcb-rnd] pcb-rnd: hardcoded librnd4 dependency
Severity set to 'minor' from 'serious'
> tags 1068812 +pending
Bug #1068812 [pcb-rnd] pcb-rnd: hardcoded librnd4 dependency
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1068840: llvm-toolchain-14: FTBFS on mips64el: /<>/compiler-rt/lib/builtins/clear_cache.c:97:3: error: implicit declaration of function 'syscall' is invalid in C99 [-Werror,-Wimplicit

[Sebastian Ramacher]

Source: llvm-toolchain-14
Version: 1:14.0.6-19
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=llvm-toolchain-14=mips64el=1%3A14.0.6-19=1712480299=0

[122/276] /<>/build-llvm/./bin/clang 
--target=mips64el-linux-gnuabi64 -DVISIBILITY_HIDDEN  
-Werror=implicit-function-declaration -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-unused-command-line-argument -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  -mips32r2 -mabi=32 -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -std=c11 -fPIC -fno-builtin -fvisibility=hidden 
-fomit-frame-pointer -MD -MT 
CMakeFiles/clang_rt.builtins-mipsel.dir/clear_cache.c.o -MF 
CMakeFiles/clang_rt.builtins-mipsel.dir/clear_cache.c.o.d -o 
CMakeFiles/clang_rt.builtins-mipsel.dir/clear_cache.c.o -c 
/<>/compiler-rt/lib/builtins/clear_cache.c
FAILED: CMakeFiles/clang_rt.builtins-mipsel.dir/clear_cache.c.o 
/<>/build-llvm/./bin/clang --target=mips64el-linux-gnuabi64 
-DVISIBILITY_HIDDEN  -Werror=implicit-function-declaration 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  
-mips32r2 -mabi=32 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -std=c11 -fPIC 
-fno-builtin -fvisibility=hidden -fomit-frame-pointer -MD -MT 
CMakeFiles/clang_rt.builtins-mipsel.dir/clear_cache.c.o -MF 
CMakeFiles/clang_rt.builtins-mipsel.dir/clear_cache.c.o.d -o 
CMakeFiles/clang_rt.builtins-mipsel.dir/clear_cache.c.o -c 
/<>/compiler-rt/lib/builtins/clear_cache.c
/<>/compiler-rt/lib/builtins/clear_cache.c:97:3: error: implicit 
declaration of function 'syscall' is invalid in C99 
[-Werror,-Wimplicit-function-declaration]
  syscall(__NR_cacheflush, start, (end_int - start_int), BCACHE);
  ^
1 error generated.
[123/276] /<>/build-llvm/./bin/clang 
--target=mips64el-linux-gnuabi64 -DVISIBILITY_HIDDEN  
-Werror=implicit-function-declaration -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-unused-command-line-argument -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  -mips32r2 -mabi=32 -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -std=c11 -fPIC -fno-builtin -fvisibility=hidden 
-fomit-frame-pointer -MD -MT 
CMakeFiles/clang_rt.builtins-mipsel.dir/gcc_personality_v0.c.o -MF 
CMakeFiles/clang_rt.builtins-mipsel.dir/gcc_personality_v0.c.o.d -o 
CMakeFiles/clang_rt.builtins-mipsel.dir/gcc_personality_v0.c.o -c 
/<>/compiler-rt/lib/builtins/gcc_personality_v0.c
[124/276] /<>/build-llvm/./bin/clang 
--target=mips64el-linux-gnuabi64 -DVISIBILITY_HIDDEN  
-Werror=implicit-function-declaration -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-unused-command-line-argument -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  -mips32r2 -mabi=32 -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -std=c11 -fPIC -fno-builtin -fvisibility=hidden 
-fomit-frame-pointer -MD -MT CMakeFiles/clang_rt.builtins-mipsel.dir/emutls.c.o 
-MF CMakeFiles/clang_rt.builtins-mipsel.dir/emutls.c.o.d -o 
CMakeFiles/clang_rt.builtins-mipsel.dir/emutls.c.o -c 
/<>/compiler-rt/lib/builtins/emutls.c
[125/276] /<>/build-llvm/./bin/clang 
--target=mips64el-linux-gnuabi64 -DVISIBILITY_HIDDEN  
-Werror=implicit-function-declaration -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-unused-command-line-argument -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  -mips64r2 -mabi=64 -std=c11 -fPIC 
-fno-builtin -fvisibility=hidden -fomit-frame-pointer -MD -MT 
CMakeFiles/clang_rt.builtins-mips64el.dir/comparetf2.c.o -MF 
CMakeFiles/clang_rt.builtins-mips64el.dir/comparetf2.c.o.d -o 
CMakeFiles/clang_rt.builtins-mips64el.dir/comparetf2.c.o -c 
/<>/compiler-rt/lib/builtins/comparetf2.c
[126/276] /<>/build-llvm/./bin/clang 
--target=mips64el-linux-gnuabi64 -DVISIBILITY_HIDDEN  
-Werror=implicit-function-declaration -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-unused-command-line-argument -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  -mips64r2 -mabi=64 -std=c11 -fPIC 
-fno-builtin -fvisibility=hidden -fomit-frame-pointer -MD -MT 
CMakeFiles/clang_rt.builtins-mips64el.dir/addtf3.c.o -MF 
CMakeFiles/clang_rt.builtins-mips64el.dir/addtf3.c.o.d -o 
CMakeFiles/clang_rt.builtins-mips64el.dir/addtf3.c.o -c 
/<>/compiler-rt/lib/builtins/addtf3.c
[127/276] /<>/build-llvm/./bin/clang 
--target=mips64el-linux-gnuabi64 -DVISIBILITY_HIDDEN  
-Werror=implicit-function-declaration -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-unused-command-line-argument -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  -mips64r2 -mabi=64 -std=c11 -fPIC 
-fno-builtin -fvisibility=hidden -fomit-frame-pointer -MD -MT 
CMakeFiles/clang_rt.builtins-mips64el.dir/divtc3.c.o -MF 
CMakeFiles/clang_rt.builtins-mips64el.dir/divtc3.c.o.d -o 
CMakeFiles/clang_rt.builtins-mips64el.dir/divtc3.c.o -c 
/<>/compiler-rt/lib/builtins/divtc3.c
ninja: build stopped: subcommand failed.

FAILED: 

Bug#1068810: marked as done (sch-rnd: hardcoded librnd4 dependency)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 13:17:44 -0600
with message-id <87h6g7emjr@gag.com>
and subject line 
has caused the Debian Bug report #1068810,
regarding sch-rnd: hardcoded librnd4 dependency
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.)


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

Package: sch-rnd
Version: 1.0.5-1
Severity: normal
Tags: patch


Hello, I found that librnd4 is correctly evaluated from shlibs:Depends in the 
core library and then it can be dropped also on core reverse-dependencies.


Please drop it.


Thanks for considering the patch.

diff -Nru sch-rnd-1.0.5/debian/control sch-rnd-1.0.5/debian/control
--- sch-rnd-1.0.5/debian/control2024-04-11 06:59:15.0 +0200
+++ sch-rnd-1.0.5/debian/control2024-04-11 15:46:41.0 +0200
@@ -88,7 +88,7 @@
 
 Package: sch-rnd-core

 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, librnd4 (>= 4.1.0)
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: sch-rnd executable with the core functionality and boxsym-rnd
  Includes the data model, the most common action commands, the native
  file format. Can be used in headless mode or batch/scripted mode for
@@ -97,7 +97,7 @@
 
 Package: sch-rnd-export-vector

 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, sch-rnd-core (= ${binary:Version}), 
librnd4 (>= 4.1.0)
+Depends: ${misc:Depends}, ${shlibs:Depends}, sch-rnd-core (= ${binary:Version})
 Description: Export formats: vector graphics
  Common vector graphic export formats: ps, eps, svg.
 


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
The librnd4 runtime dependency is needed to ensure at least a minimum
version of that library is available so required capability is present.
The "hard coded" dependency is not actually a bug, much less a
release-critical bug.

Bdale


signature.asc
Description: PGP signature
--- End Message ---

Bug#1068810: [Pkg-electronics-devel] Bug#1068810: sch-rnd: hardcoded librnd4 dependency

[Bdale Garbee]

Gianfranco Costamagna  writes:

> Hello, I found that librnd4 is correctly evaluated from shlibs:Depends
> in the core library and then it can be dropped also on core
> reverse-dependencies.

The point of the dependency is to require version 4.1.0 or later, since
that's the librnd version that added support for hierarchical design
which is required by this and later releases of sch-rnd.

> Please drop it.

What actual problem are you trying to solve with this bug report?

Bdale


signature.asc
Description: PGP signature

Bug#1066421: marked as done (mpb: FTBFS: ././conftest.c:44:(.text.startup+0xb): undefined reference to `foobar')

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 18:34:46 +
with message-id 
and subject line Bug#1066421: fixed in mpb 1.11.1-5.1
has caused the Debian Bug report #1066421,
regarding mpb: FTBFS: ././conftest.c:44:(.text.startup+0xb): undefined 
reference to `foobar'
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.)


-- 
1066421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpb
Version: 1.11.1-5
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):
> /usr/bin/ld: /tmp/ccEEtlwH.o: in function `main':
> ././conftest.c:44:(.text.startup+0xb): undefined reference to `foobar'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/mpb_1.11.1-5_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: mpb
Source-Version: 1.11.1-5.1
Done: Andrey Rakhmatullin 

We believe that the bug you reported is fixed in the latest version of
mpb, 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 mpb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 23:13:16 +0500
Source: mpb
Architecture: source
Version: 1.11.1-5.1
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Andrey Rakhmatullin 
Closes: 1066421
Changes:
 mpb (1.11.1-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066421).
Checksums-Sha1:
 e9fc35441fb3b6475bfad205dae78e4da6a8757f 2129 mpb_1.11.1-5.1.dsc
 ccdb7c1fa61d7f2c2bb0d42c3e08ba960593ff5a 145640 mpb_1.11.1-5.1.debian.tar.xz
 8228a104bc989598d129750e0234386c93c4b8fb 12079 mpb_1.11.1-5.1_amd64.buildinfo
Checksums-Sha256:
 db75bb8acefa2cf9d5148262720b9594e64b27fc36ccb4f9cca667dfb42a12da 2129 
mpb_1.11.1-5.1.dsc
 b6b0ad008c5b47ceb25033a09974e91a3c7fdee86b89cd1bab7f2006e5b1d659 145640 
mpb_1.11.1-5.1.debian.tar.xz
 43d0671d6bcc7fbf7c9da3d1ebe4022bfdd22ea60484bc112eea8dc093ef4ab3 12079 
mpb_1.11.1-5.1_amd64.buildinfo
Files:
 e9c14d8a705e682c5d420e869c54d64d 2129 science optional mpb_1.11.1-5.1.dsc
 9a989064bee875381f9d71d7693d4b62 145640 science optional 
mpb_1.11.1-5.1.debian.tar.xz
 ec0240f314de4adabdcc1caf219025fb 12079 science optional 
mpb_1.11.1-5.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmYYKT4ACgkQM2L3AxpJ
kuEmTxAAmP7INdDttMQ9oU4+IFqg6FLMV8QYuDWDKbJX7nvG4Z/Om7FipbTtCj5P
GBOBLGh4HCD6RdjL/fphtWMZEbNAMjYyyvCFKgnwMLUUzEeqDeM+lhHStTXYbHly
9YeWYhv86LLlwN+QHM7n33K58OJLIQAnH4hDhXJ2S8Dixq6WR3r1AYYf2zJmN98N
r9OXBYIieXyxXz1hoLzLtMZiiiYJFXIpQtX1FbkQ7q2CtyCe1yrArykkYINV5jKR
Ops/kGZU9vGBJd0OxsabG2dYXaSzJsMjyACb16QdqvYgWq+TGiVopzUXJSGx7C33
jvuJe2+UdUHSRZKv6ZwgasBvMemWE50dnUaAJRMalB39pXJBQB3tLj3hlkJGWiPV
Q7lqV+ZN/wrBWIsRuvf/FoDZbSMSY5ptcOq+JHWSVTKlLM9C+Ha+wV+jGiCs1Tmd
HHQZmFBhop3vDbmi39j+ccpYBiYomhp61wh7Iejg2ygflX3wu9YAhP1KTMuorHGq
6qLAQfVsmfnQKHGr3NLoR+HnJsDO+KMRofImVTuYJFdcJnI2XVBrW7NE1TUUTK76
xpCU2DMi65+Vn1sgnqZCoAGhKNEmVt/eSJsjePlNwQdohxPNZsVZXgMrQAQ/gNLR
T3U+twkjBBfqpVo9I+TtglbRTmdVezYR2CnN0vUvBPVB/tpgy8c=
=EfNe
-END PGP SIGNATURE-

Processed: closing 1060768

[Debian Bug Tracking System]

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

> close 1060768
Bug #1060768 [pdudaemon] pdudaemon: Missing dependency on python3-aiohttp
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1066421: mpb: diff for NMU version 1.11.1-5.1

[Andrey Rakhmatullin]

Control: tags 1066421 + patch
Control: tags 1066421 + pending

Dear maintainer,

I've prepared an NMU for mpb (versioned as 1.11.1-5.1) and
uploaded it to unstable.

Regards.


-- 
WBR, wRAR
diff -Nru mpb-1.11.1/debian/changelog mpb-1.11.1/debian/changelog
--- mpb-1.11.1/debian/changelog	2022-12-15 02:17:01.0 +0500
+++ mpb-1.11.1/debian/changelog	2024-04-11 23:13:16.0 +0500
@@ -1,3 +1,10 @@
+mpb (1.11.1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066421).
+
+ -- Andrey Rakhmatullin   Thu, 11 Apr 2024 23:13:16 +0500
+
 mpb (1.11.1-5) unstable; urgency=medium
 
   * debian/control: bump Standards Version to 4.6.1 (no changes)
diff -Nru mpb-1.11.1/debian/patches/18-fix-implicit-function-declaration.patch mpb-1.11.1/debian/patches/18-fix-implicit-function-declaration.patch
--- mpb-1.11.1/debian/patches/18-fix-implicit-function-declaration.patch	1970-01-01 05:00:00.0 +0500
+++ mpb-1.11.1/debian/patches/18-fix-implicit-function-declaration.patch	2024-04-11 23:11:20.0 +0500
@@ -0,0 +1,53 @@
+Description: Add missing header includes.
+Author: Andrey Rakhmatullin 
+Bug-Debian: https://bugs.debian.org/1066421
+Last-Update: 2024-04-11
+
+Index: mpb-1.11.1/mpb/fields.c
+===
+--- mpb-1.11.1.orig/mpb/fields.c
 mpb-1.11.1/mpb/fields.c
+@@ -20,6 +20,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #include "config.h"
+ #include 
+Index: mpb-1.11.1/mpb/field-smob.c
+===
+--- mpb-1.11.1.orig/mpb/field-smob.c
 mpb-1.11.1/mpb/field-smob.c
+@@ -17,6 +17,7 @@
+ 
+ #include 
+ #include 
++#include 
+ 
+ #include "config.h"
+ 
+Index: mpb-1.11.1/mpb/material_grid.c
+===
+--- mpb-1.11.1.orig/mpb/material_grid.c
 mpb-1.11.1/mpb/material_grid.c
+@@ -18,6 +18,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #include "config.h"
+ #include 
+Index: mpb-1.11.1/mpb/material_grid_opt.c
+===
+--- mpb-1.11.1.orig/mpb/material_grid_opt.c
 mpb-1.11.1/mpb/material_grid_opt.c
+@@ -20,6 +20,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #include "config.h"
+ #include 
diff -Nru mpb-1.11.1/debian/patches/series mpb-1.11.1/debian/patches/series
--- mpb-1.11.1/debian/patches/series	2022-12-15 02:17:01.0 +0500
+++ mpb-1.11.1/debian/patches/series	2024-04-11 23:01:11.0 +0500
@@ -15,5 +15,6 @@
 14-mpb-mpb.1.patch
 15-mpb-mpb-split.1.patch
 16-utils-mpb-data.1.patch
+18-fix-implicit-function-declaration.patch
 
 zzz-blas-problem-on-mipsel.patch


signature.asc
Description: PGP signature

Processed: mpb: diff for NMU version 1.11.1-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1066421 + patch
Bug #1066421 [src:mpb] mpb: FTBFS: ././conftest.c:44:(.text.startup+0xb): 
undefined reference to `foobar'
Added tag(s) patch.
> tags 1066421 + pending
Bug #1066421 [src:mpb] mpb: FTBFS: ././conftest.c:44:(.text.startup+0xb): 
undefined reference to `foobar'
Added tag(s) pending.

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

Bug#1067337: marked as done (golang-github-dchest-uniuri: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/dchest/uniuri returned exit code 1)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 18:04:17 +
with message-id 
and subject line Bug#1067337: fixed in golang-github-dchest-uniuri 
0.0~git20221007.a87ec9d-1
has caused the Debian Bug report #1067337,
regarding golang-github-dchest-uniuri: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/dchest/uniuri 
returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-dchest-uniuri
Version: 0.0~git20200228.7aecb25-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 
> github.com/dchest/uniuri
> internal/unsafeheader
> internal/coverage/rtcov
> internal/godebugs
> internal/goarch
> internal/goexperiment
> internal/cpu
> internal/goos
> runtime/internal/atomic
> runtime/internal/syscall
> internal/race
> internal/abi
> internal/chacha8rand
> runtime/internal/math
> runtime/internal/sys
> sync/atomic
> math/bits
> unicode/utf8
> unicode
> crypto/internal/alias
> crypto/subtle
> internal/itoa
> internal/bytealg
> math
> crypto/internal/boring/sig
> cmp
> slices
> runtime
> internal/reflectlite
> sync
> internal/testlog
> internal/bisect
> internal/godebug
> errors
> sort
> internal/oserror
> internal/safefilepath
> path
> io
> strconv
> math/rand
> syscall
> hash
> crypto/internal/randutil
> bytes
> strings
> reflect
> crypto
> internal/syscall/execenv
> internal/syscall/unix
> time
> io/fs
> internal/poll
> internal/fmtsort
> encoding/binary
> os
> crypto/cipher
> crypto/internal/boring
> fmt
> math/big
> crypto/rand
> github.com/dchest/uniuri
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/dchest/uniuri
> === RUN   TestNew
> --- PASS: TestNew (0.01s)
> === RUN   TestNewLen
> --- PASS: TestNewLen (0.00s)
> === RUN   TestNewLenChars
> --- PASS: TestNewLenChars (0.00s)
> === RUN   TestNewLenCharsMaxLength
> --- PASS: TestNewLenCharsMaxLength (0.00s)
> === RUN   TestBias
> uniuri_test.go:99: Bias on 'w': expected average 3846.153846, got 4048
> --- FAIL: TestBias (0.00s)
> FAIL
> FAIL  github.com/dchest/uniuri0.014s
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/dchest/uniuri returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/golang-github-dchest-uniuri_0.0~git20200228.7aecb25-1_unstable.log

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

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: golang-github-dchest-uniuri
Source-Version: 0.0~git20221007.a87ec9d-1
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
golang-github-dchest-uniuri, 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.
Thorsten Alteholz  (supplier of updated 
golang-github-dchest-uniuri 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 

Bug#1068371: marked as done (indi-apogee dependencies unsatisfiable on 32-bit non-i386 architectures.)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 18:04:26 +
with message-id 
and subject line Bug#1068371: fixed in indi-apogee 1.9+20221223184417-2
has caused the Debian Bug report #1068371,
regarding indi-apogee dependencies unsatisfiable on 32-bit non-i386 
architectures.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: indi-apogee
Version: 0.10.0-5
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, indi-apogee depends
on both libapogee3 and libapogee3t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
architectures).
--- End Message ---
--- Begin Message ---
Source: indi-apogee
Source-Version: 1.9+20221223184417-2
Done: Thorsten Alteholz 

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated indi-apogee 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, 10 Apr 2024 22:45:32 +0200
Source: indi-apogee
Architecture: source
Version: 1.9+20221223184417-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Thorsten Alteholz 
Closes: 1068371
Changes:
 indi-apogee (1.9+20221223184417-2) unstable; urgency=medium
 .
   * debian/control: change dependency of indi-apogee from
 libapogee3 to libapogee3t64
 (Closes: #1068371)
   * debian/control: bump standard to 4.7.0 (no changes)
Checksums-Sha1:
 79abec018589232f0d24363b79a67a63f53b5d3b 2299 
indi-apogee_1.9+20221223184417-2.dsc
 fdef8c8445f985467a6ca90b938badea4f85a4a4 65133 
indi-apogee_1.9+20221223184417.orig.tar.gz
 64b35ec853847f4b436f03d5655681215370af71 1508 
indi-apogee_1.9+20221223184417-2.debian.tar.xz
 29edaab4724740a72b1389b44532c2580c22835e 9021 
indi-apogee_1.9+20221223184417-2_amd64.buildinfo
Checksums-Sha256:
 4b357024b6b698b29070fb6bd1c8fd84371181b0b38b4cef32d76ea08a7f1432 2299 
indi-apogee_1.9+20221223184417-2.dsc
 50819156e313a90346d01c99c888e339ee0fcff71271ca62397d49e79405ee80 65133 
indi-apogee_1.9+20221223184417.orig.tar.gz
 8a5f582504ff278afa464664c7c5c09db3251e76d9736c357d2b8c2a4fa49898 1508 
indi-apogee_1.9+20221223184417-2.debian.tar.xz
 39fb9d6360ee8aecfa3f8632daae6da19a303d94df026bad1a364fbc24f07f42 9021 
indi-apogee_1.9+20221223184417-2_amd64.buildinfo
Files:
 07397e4f54300ac86fd8025e55a2802c 2299 science optional 
indi-apogee_1.9+20221223184417-2.dsc
 55113e427fb1b47f838fe0bf7d8e8ce2 65133 science optional 
indi-apogee_1.9+20221223184417.orig.tar.gz
 0f4ecf5395d7a8b665f2436653603e3b 1508 science optional 
indi-apogee_1.9+20221223184417-2.debian.tar.xz
 72be02b2fa9b44acec597113786b243f 9021 science optional 
indi-apogee_1.9+20221223184417-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmYYIcZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR2/QEACr33JReG8S4p2XboQpxZuI1OKTdN7t
3QCgtdaaLWGw9JB8zY/IvLp4sLEjTJaunKkdpE32KVijCHA5Ks+LAR/yplR5ivpB
2ZSrTqGB4/YglOGYz2jw89bHGCyzrLYs23bqeJDqbrbqylQ4lGd3X7/Zbo67c6Ai
GV//Lr25WsKOL+y+JZhm0zwfp7djKn/D43/H0QXAsdE0NS+3GAeGQhgNWdpsJr6u
K98KccHrFLZN425rvHjsz7sx3w2APO40BbNiBSj/Zpu0+WLDQtIjaXx0xwBZ5aUe
S8VVKP+5D8xTu+LVMVTWsc0q1i5vkWb6k17oMoLWHErCFZcaZdAh4LrQmgkcGbT9
2SrBcbztNCgofPzJfZfnPTLwY8hcjrUCBKhI3Dm+VKamPUlslzWbiKkr27MnHqgv
sBwmvWtQMn0/tTRWN2Cm+65bKohfLndVPbT8QPq3hvu7IeELDsOpbkk8Jqeb97/6
1u6rFxrMsunI7sOqFiuFk4oSb0pkjNrX9djlwoD3hSVvbj2HP/t7ec99kBP9NCnI
j1rt5TZrp3Yzq6LzIyLvU4Pj8KOMvFw6smNQYD7HNlTvw1P1NTn50mLb1pJrd1xa
J1Tdt1H8ykXkTnM5lFlPvgMEfjQMexjf73QtRYW0xtv9rMqMUg8uf5fmgBdNonJS
K4+1roNLXkz04w==
=YuRS
-END PGP SIGNATURE-



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

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

[Holger Levsen]

Dear Chris,

On Thu, Apr 11, 2024 at 05:51:05PM +, Debian Bug Tracking System wrote:
> Date: Thu, 11 Apr 2024 17:50:02 +
> From: Debian FTP Masters 
> To: 1066340-cl...@bugs.debian.org
> Subject: Bug#1066340: fixed in t4kcommon 0.1.1-11.2
> Reply-To: Chris Hofstaedtler 

thanks for that NMU, much appreciated! <3


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Because things are the way they are, things will not stay the way they are.
(Bertolt Brecht)


signature.asc
Description: PGP signature

Bug#1068145: marked as done (FTBFS: chmod: cannot access 'debian/python-mpltoolkits.basemap-data/usr/share/basemap/data/*': No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 17:49:29 +
with message-id 
and subject line Bug#1068145: fixed in basemap 1.2.2+dfsg-5
has caused the Debian Bug report #1068145,
regarding FTBFS: chmod: cannot access 
'debian/python-mpltoolkits.basemap-data/usr/share/basemap/data/*': No such file 
or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

https://buildd.debian.org/status/fetch.php?pkg=basemap=amd64=1.2.2%2Bdfsg-4=1711493603=0

   debian/rules override_dh_python3
make[1]: Entering directory '/<>'
dh_python3
chmod -x debian/python-mpltoolkits.basemap-data/usr/share/basemap/data/*
chmod: cannot access 'debian/python-mpltoolkits.basemap-
data/usr/share/basemap/data/*': No such file or directory


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: basemap
Source-Version: 1.2.2+dfsg-5
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated basemap 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, 27 Mar 2024 07:03:11 +0100
Source: basemap
Architecture: source
Version: 1.2.2+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1068145
Changes:
 basemap (1.2.2+dfsg-5) unstable; urgency=medium
 .
   * Do not fail in separate arch-all builds. Closes: #1068145.
   * Apply patch for d/rules from bug #790235
Checksums-Sha1:
 a16b3489486e34321dfad4deccca286c367e2dd5 2556 basemap_1.2.2+dfsg-5.dsc
 7f13d42bbec5e4f80419792dfd1b31c06dbb8284 28492 
basemap_1.2.2+dfsg-5.debian.tar.xz
 c7dfd7469e0be121b284fe1ae7a1d55a802b1881 12749 
basemap_1.2.2+dfsg-5_amd64.buildinfo
Checksums-Sha256:
 83d03b6ffd4366a8be672256e83c6f768b35478b81ee82b999778248f9a672d6 2556 
basemap_1.2.2+dfsg-5.dsc
 b511820dcc47221435d6c8d6f64c7b64bf4c5c13f3b0f89d07e092fe39cf08a6 28492 
basemap_1.2.2+dfsg-5.debian.tar.xz
 9642b3dee8f149bfa15965f2fce1c6f0b89873e82a90105d95408f198e49590d 12749 
basemap_1.2.2+dfsg-5_amd64.buildinfo
Files:
 807bd17798e0fd8cf946407b1df4bc70 2556 python optional basemap_1.2.2+dfsg-5.dsc
 f8e1a0e32303f126c68aab3fb9a2c5fa 28492 python optional 
basemap_1.2.2+dfsg-5.debian.tar.xz
 11190dd8485614e613339053c57a2378 12749 python optional 
basemap_1.2.2+dfsg-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmYYHcASHGVhbWFudUBk
ZWJpYW4ub3JnAAoJEPqd7F3hHGPxTvsP/21MXtkdKP70gbtnjkbmL/ycx2b3ZA1f
+FZ5/CwPuIh6zDwj+iTz//pDzDRL5d7QOMOy9wfJtqHFzq/w7VDgHOSNBQLpaSV+
dsuqL30M/WWn4GYWyBxhDmuzi9GJWks34HzhI80uuq0JspiW1VhA4Gy6gbIWfV3t
ffN5oBRuy0x6zf0gMuYHkeRT1wZ0m2vo6qGyZqMxfHV0hpD947pC/fDou3PRL8MK
vE4SYCrdzkrSq5q+o2BtLspZTW0NySipuwsscE0oJBIGyB2hvltzazpC6Zft6HSm
4R88RVF8PiZXJnUw7YLmeCi1MRzA+J2HNQGneveMEZ5dKtztBeeNVIJc9BuchNio
YSF+T+C1aOVPovjD9kEYkMC4MostbE4j5p38juhan5LcabyaqVpa2wTC26i7BgAL
25RhU+oI6quKsc3WKkrYpUbHOukyzWiuW+ZpHZhOBK8TrlQ0zhgEghvb2Nwabspz
3XG71avSDS9FXEtcgI8ekdFsaXUxYF5kDcghdIbyZflD7AL47QwitA6pXZgqt/cD
MJNjRu462P+IXZq+o1qlr3xQqFg9sM5Wdwy3OkjCwSlckPJJ6DBLyO5LCMfSWfWP
pKXyyXTzxF08JEGIJm+5vEbaAdIRhCeD73jLz7Ei2LaC/VRzRDOXBvy+YL+XW+GX
rAHBZ9EOu/NZ
=zBlA
-END PGP SIGNATURE-



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

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

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 17:50:02 +
with message-id 
and subject line Bug#1066340: fixed in t4kcommon 0.1.1-11.2
has caused the Debian Bug report #1066340,
regarding t4kcommon: FTBFS: linebreak.c:163:19: error: implicit declaration of 
function ‘u8_mbtouc_unsafe’ [-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.)


-- 
1066340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: t4kcommon
Version: 0.1.1-11.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):
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -I/usr/include/SDL -D_GNU_SOURCE=1 
> -D_REENTRANT   -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT  
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi 
> -I/usr/include/cairo -I/usr/include/pixman-1  -I/usr/include/SDL 
> -D_GNU_SOURCE=1 -D_REENTRANT  -I/usr/include/librsvg-2.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/webp 
> -pthread -I/usr/include/cairo -I/usr/include/freetype2 
> -I/usr/include/pixman-1  -I/usr/include/cairo -I/usr/include/libpng16 
> -I/usr/include/freetype2 -I/usr/include/pixman-1  -I/usr/include/libpng16  
> -I/usr/include/libxml2  -c -o u8-uctomb.lo `test -f 'unistr/u8-uctomb.c' || 
> echo './'`unistr/u8-uctomb.c
> linebreak.c: In function ‘u8_possible_linebreaks’:
> 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);
>   |   ^~~~
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -I/usr/include/SDL -D_GNU_SOURCE=1 
> -D_REENTRANT   -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT  
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi 
> -I/usr/include/cairo -I/usr/include/pixman-1  -I/usr/include/SDL 
> -D_GNU_SOURCE=1 -D_REENTRANT  -I/usr/include/librsvg-2.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/webp 
> -pthread -I/usr/include/cairo -I/usr/include/freetype2 
> -I/usr/include/pixman-1  -I/usr/include/cairo -I/usr/include/libpng16 
> -I/usr/include/freetype2 -I/usr/include/pixman-1  -I/usr/include/libpng16  
> -I/usr/include/libxml2  -c -o width.lo `test -f 'uniwidth/width.c' || echo 
> './'`uniwidth/width.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL 
> -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi 

Processed: retitle 1063143 to filament: FTBFS: fatal error: 'localintermediate.h' file not found

[Debian Bug Tracking System]

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

> retitle 1063143 filament: FTBFS: fatal error: 'localintermediate.h' file not 
> found
Bug #1063143 [src:filament] filament: FTBFS on armel: fatal error: 
'localintermediate.h' file not found
Changed Bug title to 'filament: FTBFS: fatal error: 'localintermediate.h' file 
not found' from 'filament: FTBFS on armel: fatal error: 'localintermediate.h' 
file not found'.
> thanks
Stopping processing here.

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

Bug#1067337: marked as pending in golang-github-dchest-uniuri

[Thorsten Alteholz]

Control: tag -1 pending

Hello,

Bug #1067337 in golang-github-dchest-uniuri 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/go-team/packages/golang-github-dchest-uniuri/-/commit/fbb9504c8f4c5944b584ed412360aabf3a04492e


Import Debian changes 0.0~git20221007.a87ec9d-1

golang-github-dchest-uniuri (0.0~git20221007.a87ec9d-1) unstable; urgency=medium
.
  * New upstream release. (Closes: #1067337)
  * debian/control: bump standard to 4.7.0 (no changes)
  * debian/control: add Rules-Requires-Root: no
  * debian/control: use dh13


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067337

Processed: Bug#1067337 marked as pending in golang-github-dchest-uniuri

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067337 [src:golang-github-dchest-uniuri] golang-github-dchest-uniuri: 
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
github.com/dchest/uniuri returned exit code 1
Added tag(s) pending.

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

Processed: tagging 1067190

[Debian Bug Tracking System]

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

> tags 1067190 + ftbfs
Bug #1067190 [timekpr-next] timekpr-next: hard-coded dependency on libgtk-3-0 
will become uninstallable on armel/armhf
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#952735: gnupg-pkcs11-scd: when used as scdaemon, `gnupg --card-status` reports wrong informations

[Thorsten Alteholz]

Control: severity -1 normal
Control: forwarded -1 https://github.com/alonbl/gnupg-pkcs11-scd/issues/61

I can reproduce this bug with my card reader and I forwarded the bug 
upstream -> https://github.com/alonbl/gnupg-pkcs11-scd/issues/61


As this is just a cosmectic bug, I reduce severity again to normal.

Processed: Re: gnupg-pkcs11-scd: when used as scdaemon, `gnupg --card-status` reports wrong informations

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #952735 [gnupg-pkcs11-scd] gnupg-pkcs11-scd: when used as scdaemon, `gnupg 
--card-status` reports wrong informations
Severity set to 'normal' from 'serious'
> forwarded -1 https://github.com/alonbl/gnupg-pkcs11-scd/issues/61
Bug #952735 [gnupg-pkcs11-scd] gnupg-pkcs11-scd: when used as scdaemon, `gnupg 
--card-status` reports wrong informations
Set Bug forwarded-to-address to 
'https://github.com/alonbl/gnupg-pkcs11-scd/issues/61'.

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

Processed: Re: Bug#1066860: libprelude ftbfs on time_t64 archs

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1066860 {Done: Benjamin Drung } [src:libprelude] 
libprelude ftbfs on time_t64 archs
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libprelude/5.2.0-5.4.

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

Bug#1066860: libprelude ftbfs on time_t64 archs

[Andrey Rakhmatullin]

Control: reopen -1 

On Thu, Mar 14, 2024 at 04:14:25PM +0100, Matthias Klose wrote:
> libprelude ftbfs on time_t64 archs with symbols file mismatches. 
This still happens, it wasn't addressed in the upload that closed this:

https://buildd.debian.org/status/fetch.php?pkg=libprelude=armel=5.2.0-5.4=1712765101=0

> patch at
> http://launchpadlibrarian.net/719321091/libprelude_5.2.0-5.3build2_5.2.0-5.3ubuntu1.diff.gz

This seems to be about different symbols though.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1068827: Changes from the 0.14.1-5.1 NMU were discarded

[Andrey Rakhmatullin]

Source: falcosecurity-libs
Version: 0.15.1-1
Severity: serious

0.15.1-1 doesn't seem to contain changes from 0.14.1-5.1, both the changelog
entry and the actual changes.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_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

Processed: found 1067619 in falcosecurity-libs/0.15.1-1

[Debian Bug Tracking System]

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

> found 1067619 falcosecurity-libs/0.15.1-1
Bug #1067619 [src:falcosecurity-libs] FTBFS: tests segfault
Marked as found in versions falcosecurity-libs/0.15.1-1.
> thanks
Stopping processing here.

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

Processed: Bug#1068145 marked as pending in basemap

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068145 [src:basemap] FTBFS: chmod: cannot access 
'debian/python-mpltoolkits.basemap-data/usr/share/basemap/data/*': No such file 
or directory
Added tag(s) pending.

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

Bug#1068145: marked as pending in basemap

[Emmanuel Arias]

Control: tag -1 pending

Hello,

Bug #1068145 in basemap 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/python-team/packages/basemap/-/commit/ef8a33ac9a105b0f9cd1889f0be7ea7c8298efe2


Do not fail in separate arch-all builds. Closes: #1068145.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068145

Processed: tagging 1068818

[Debian Bug Tracking System]

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

> tags 1068818 + upstream
Bug #1068818 [src:sngrep] sngrep: CVE-2024-3119 CVE-2024-3120
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1068808: marked as done (openmpi-bin has an undeclared file conflict on /usr/bin/pterm)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 16:51:52 +
with message-id 
and subject line Bug#1068808: fixed in openmpi 5.0.3-2
has caused the Debian Bug report #1068808,
regarding openmpi-bin has an undeclared file conflict on /usr/bin/pterm
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.)


-- 
1068808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openmpi-bin
Version: 5.0.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + pterm

openmpi-bin has an undeclared file conflict. This may result in an
unpack error from dpkg.

The file /usr/bin/pterm is contained in the packages
 * openmpi-bin/5.0.3-1 as present in experimental
 * pterm
   * 0.74-1+deb11u1 as present in bullseye|bullseye-security
   * 0.78-2+deb12u1 as present in bookworm|bookworm-security
   * 0.80-1 as present in trixie
   * 0.80-1+b1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: openmpi
Source-Version: 5.0.3-2
Done: Alastair McKinstry 

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated openmpi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 11 Apr 2024 16:16:39 +0100
Source: openmpi
Binary: libopenmpi-dev libopenmpi3 libopenmpi3-dbgsym openmpi-bin 
openmpi-bin-dbgsym openmpi-common openmpi-doc
Architecture: source arm64 all
Version: 5.0.3-2
Distribution: experimental
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libopenmpi-dev - high performance message passing library -- header files
 libopenmpi3 - high performance message passing library -- shared library
 openmpi-bin - high performance message passing library -- binaries
 openmpi-common - high performance message passing library -- common files
 openmpi-doc - high performance message passing library -- man pages
Closes: 1056054 1068808
Changes:
 openmpi (5.0.3-2) experimental; urgency=medium
 .
   * Rename /usr/bin/pterm to pterm.openmpi. Closes: #1056054, #1068808
Checksums-Sha1:
 8fc2231fea5bd26201b553f3c07f7da451c90a20 2748 openmpi_5.0.3-2.dsc
 576392774261b03c4e4443eed31cdc6e32af04c4 67608 openmpi_5.0.3-2.debian.tar.xz
 aa6cde14c46377b2db49b6e2d61efcb149a1979a 1086004 
libopenmpi-dev_5.0.3-2_arm64.deb
 3d883ed2d724822026799d3763d76cd490b71c53 10498724 
libopenmpi3-dbgsym_5.0.3-2_arm64.deb
 4270ac6db677c980c22d7c553a5ffae6959e7750 2044380 libopenmpi3_5.0.3-2_arm64.deb
 c08dad2314c9d191ad16efd347f319a71c3d36fc 685388 
openmpi-bin-dbgsym_5.0.3-2_arm64.deb
 ae0e798cc7eb8f06b34325f5789270f0d2b7420a 158460 openmpi-bin_5.0.3-2_arm64.deb
 6f4d664ee0af836ea6ed5771fdc706e0217ef44e 94152 openmpi-common_5.0.3-2_all.deb
 a82c8d47004e637760fbc79b21501f275cbf601d 8488748 openmpi-doc_5.0.3-2_all.deb
 f57e59f6cf7d71d118f14ba30bccb9679274b281 17818 openmpi_5.0.3-2_arm64.buildinfo
Checksums-Sha256:
 6ad5e5f840a59fa65e8c195c7b40d9e52060b2760074218784f3e6391e91d74e 2748 
openmpi_5.0.3-2.dsc
 3ca2cbc04d6824b82693ce68e74ed16b336caccb206f599f84f786215394f475 67608 
openmpi_5.0.3-2.debian.tar.xz
 d09b4c1514d29c1322e777fa9509f0483f9ffb5f6c558ecfa99a2f1abdb502b7 1086004 
libopenmpi-dev_5.0.3-2_arm64.deb
 a25740ac2e3f0b1159bd5e62fc22799e9922b0e662a77720b09d2667eaf28566 10498724 
libopenmpi3-dbgsym_5.0.3-2_arm64.deb
 a252f5c5e1f25cc8dadb01ee1a5079c340ec9c07238ae1d675b900286a23ebaa 2044380 

Bug#1056054: marked as done (openmpi-doc: /usr/share/man/man1/pterm.1.gz is already shipped by pterm)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 16:51:52 +
with message-id 
and subject line Bug#1056054: fixed in openmpi 5.0.3-2
has caused the Debian Bug report #1056054,
regarding openmpi-doc: /usr/share/man/man1/pterm.1.gz is already shipped by 
pterm
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.)


-- 
1056054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openmpi-doc
Version: 5.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

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.

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

  Unpacking openmpi-doc (5.0.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/openmpi-doc_5.0.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/pterm.1.gz', which is also in 
package pterm 0.79-1
  Errors were encountered while processing:
   /var/cache/apt/archives/openmpi-doc_5.0.0-1_all.deb

cheers,

Andreas


pterm=0.79-1_openmpi-doc=5.0.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: openmpi
Source-Version: 5.0.3-2
Done: Alastair McKinstry 

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated openmpi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 11 Apr 2024 16:16:39 +0100
Source: openmpi
Binary: libopenmpi-dev libopenmpi3 libopenmpi3-dbgsym openmpi-bin 
openmpi-bin-dbgsym openmpi-common openmpi-doc
Architecture: source arm64 all
Version: 5.0.3-2
Distribution: experimental
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libopenmpi-dev - high performance message passing library -- header files
 libopenmpi3 - high performance message passing library -- shared library
 openmpi-bin - high performance message passing library -- binaries
 openmpi-common - high performance message passing library -- common files
 openmpi-doc - high performance message passing library -- man pages
Closes: 1056054 1068808
Changes:
 openmpi (5.0.3-2) experimental; urgency=medium
 .
   * Rename /usr/bin/pterm to pterm.openmpi. Closes: #1056054, #1068808
Checksums-Sha1:
 8fc2231fea5bd26201b553f3c07f7da451c90a20 2748 openmpi_5.0.3-2.dsc
 576392774261b03c4e4443eed31cdc6e32af04c4 67608 openmpi_5.0.3-2.debian.tar.xz
 aa6cde14c46377b2db49b6e2d61efcb149a1979a 1086004 
libopenmpi-dev_5.0.3-2_arm64.deb
 3d883ed2d724822026799d3763d76cd490b71c53 10498724 
libopenmpi3-dbgsym_5.0.3-2_arm64.deb
 4270ac6db677c980c22d7c553a5ffae6959e7750 2044380 libopenmpi3_5.0.3-2_arm64.deb
 c08dad2314c9d191ad16efd347f319a71c3d36fc 685388 
openmpi-bin-dbgsym_5.0.3-2_arm64.deb
 ae0e798cc7eb8f06b34325f5789270f0d2b7420a 158460 openmpi-bin_5.0.3-2_arm64.deb
 6f4d664ee0af836ea6ed5771fdc706e0217ef44e 94152 openmpi-common_5.0.3-2_all.deb
 a82c8d47004e637760fbc79b21501f275cbf601d 8488748 openmpi-doc_5.0.3-2_all.deb
 f57e59f6cf7d71d118f14ba30bccb9679274b281 17818 openmpi_5.0.3-2_arm64.buildinfo
Checksums-Sha256:
 6ad5e5f840a59fa65e8c195c7b40d9e52060b2760074218784f3e6391e91d74e 2748 
openmpi_5.0.3-2.dsc
 3ca2cbc04d6824b82693ce68e74ed16b336caccb206f599f84f786215394f475 67608 
openmpi_5.0.3-2.debian.tar.xz
 d09b4c1514d29c1322e777fa9509f0483f9ffb5f6c558ecfa99a2f1abdb502b7 1086004 
libopenmpi-dev_5.0.3-2_arm64.deb
 a25740ac2e3f0b1159bd5e62fc22799e9922b0e662a77720b09d2667eaf28566 10498724 
libopenmpi3-dbgsym_5.0.3-2_arm64.deb
 a252f5c5e1f25cc8dadb01ee1a5079c340ec9c07238ae1d675b900286a23ebaa 2044380 
libopenmpi3_5.0.3-2_arm64.deb
 45fd789e85bd308bc82e149ccf0c8f7fd158db019d3fd90c406ab2cd24b2e377 685388 
openmpi-bin-dbgsym_5.0.3-2_arm64.deb
 625df67cb1d0c615f27b00fa5de2d7bd23488261f66856769871330a4d592558 158460 
openmpi-bin_5.0.3-2_arm64.deb
 

Processed: re: ppp: FTBFS due -Werror=implicit-function-declaration

[Debian Bug Tracking System]

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

> block 1036884 by 1066134
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1055352 1067676 1067288 1067916 1068327 1068586 1067829 
1067494 1065787 1065790 1068160 1066049 1067190 1055530 1066794 1067677 1068325 
1067170 1068068 1062847 1067193 1067458 1067272 1067189 1065973 1066328 1067171 
1067069 1067509 1067192 1067508 1065816 1067175 1067561
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1066134 and 1065940
> tags 1066134 +patch
Bug #1066134 {Done: Adrian Bunk } [src:ppp] FTBFS due 
-Werror=implicit-function-declaration
Bug #1065940 {Done: Adrian Bunk } [src:ppp] ppp: FTBFS on 
arm{el,hf}: sys-linux.c:357:9: error: implicit declaration of function 
‘sif6down’; did you mean ‘sifdown’? [-Werror=implicit-function-declaration]
Ignoring request to alter tags of bug #1066134 to the same tags previously set
Ignoring request to alter tags of bug #1065940 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#1066134: ppp: FTBFS due -Werror=implicit-function-declaration

[peter green]

block 1036884 by 1066134
tags 1066134 +patch
thanks

Hi.

The build failure of ppp in unstable is a blocker for the time_t
transition, since ppp needs to be rebuilt against the new versions
of libpcap and openssl. The version in experimental seems to build fine.

Can you fix this, either by adding a backported patch (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066134#12 ),
or by uploading the version in experimental to unstable? or would
you prefer that someone prepares a NMU?

Processed (with 1 error): tagging 1068815, tagging 1068816, tagging 1068817, tagging 168818, tagging 1068820, tagging 1068819 ...

[Debian Bug Tracking System]

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

> tags 1068815 + upstream
Bug #1068815 [src:undertow] undertow: CVE-2023-1973
Added tag(s) upstream.
> tags 1068816 + upstream
Bug #1068816 [src:undertow] undertow: CVE-2024-1459
Added tag(s) upstream.
> tags 1068817 + upstream
Bug #1068817 [src:undertow] undertow: CVE-2024-1635
Added tag(s) upstream.
> tags 168818 + upstream
Failed to alter tags of Bug 168818: Not altering archived bugs; see unarchive.

> tags 1068820 + upstream
Bug #1068820 [src:qemu] qemu: CVE-2024-3446
Added tag(s) upstream.
> tags 1068819 + upstream
Bug #1068819 [src:qemu] qemu: CVE-2024-26327 CVE-2024-26328
Added tag(s) upstream.
> tags 1068821 + upstream
Bug #1068821 [src:qemu] qemu: CVE-2024-3447
Added tag(s) upstream.
> tags 1068822 + upstream
Bug #1068822 [src:qemu] qemu: CVE-2024-3567
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1068815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068815
1068816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068816
1068817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068817
1068819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068819
1068820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068820
1068821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068821
1068822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1066688: marked as done (ng: FTBFS: dir.c:127:11: error: implicit declaration of function ‘rchdir’; did you mean ‘vchdir’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 15:50:20 +
with message-id 
and subject line Bug#1066688: fixed in ng 1.5~beta1-11
has caused the Debian Bug report #1066688,
regarding ng: FTBFS: dir.c:127:11: error: implicit declaration of function 
‘rchdir’; did you mean ‘vchdir’? [-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.)


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

Hi,

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

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

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -DHAVE_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2  -c -o dir.o dir.c
> dir.c: In function ‘ensurecwd’:
> dir.c:127:11: error: implicit declaration of function ‘rchdir’; did you mean 
> ‘vchdir’? [-Werror=implicit-function-declaration]
>   127 |   rchdir(curbp->b_cwd); /* ensure we are in the current dir */
>   |   ^~
>   |   vchdir
> dir.c: At top level:
> dir.c:136:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   136 | changedir(f, n)
>   | ^
> dir.c: In function ‘changedir’:
> dir.c:136:1: warning: type of ‘f’ defaults to ‘int’ [-Wimplicit-int]
> dir.c:136:1: warning: type of ‘n’ defaults to ‘int’ [-Wimplicit-int]
> dir.c: At top level:
> dir.c:213:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   213 | showcwdir(f, n)
>   | ^
> dir.c: In function ‘showcwdir’:
> dir.c:213:1: warning: type of ‘f’ defaults to ‘int’ [-Wimplicit-int]
> dir.c:213:1: warning: type of ‘n’ defaults to ‘int’ [-Wimplicit-int]
> cc1: some warnings being treated as errors
> make[2]: *** [: dir.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/ng_1.5~beta1-10_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: ng
Source-Version: 1.5~beta1-11
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
ng, 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.
Andreas Beckmann  (supplier of updated ng 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: Thu, 11 Apr 2024 17:24:49 +0200
Source: ng
Architecture: source
Version: 1.5~beta1-11
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1066688
Changes:
 ng (1.5~beta1-11) unstable; urgency=medium
 .
   * QA upload.
   * Fix building with -Werror=implicit-function-declaration.
 (Closes: #1066688)
Checksums-Sha1:
 542b074346ffb4b8d0dc823d010baa6be1302d19 1984 ng_1.5~beta1-11.dsc
 c707f4a74d6d21a03f5180bab2f74283cd488c92 77132 ng_1.5~beta1-11.debian.tar.xz
 340c7b27c9c22667925e3183ac900fc5143a0f04 5782 ng_1.5~beta1-11_source.buildinfo

Bug#1063874: marked as done (m2crypto: Testsuite fails with OpenSSL 3.2)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 15:50:00 +
with message-id 
and subject line Bug#1063874: fixed in m2crypto 0.40.1-3
has caused the Debian Bug report #1063874,
regarding m2crypto: Testsuite fails with OpenSSL 3.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: m2crypto
Version: 0.40.1-1
Severity: important
Tags: sid patch
control: affects -1 src:openssl
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-3.2

OpenSSL had an optimisation for PKCS7_verify() where it kept the memory
BIO around. This optimisation is gone in OpenSSL 3.2 and so the test for
verify fails because the memory BIO "ended".

The attached patch fixes the issue.

Sebastian
>From 08308043d7ce8bb645996c8cb29655a23ead43a4 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Tue, 13 Feb 2024 17:47:22 +0100
Subject: [PATCH] test/smime: Rewind BIO before repeadetly invoking verify.

OpenSSL had an optimisation for PKCS7_verify() where it kept the memory
BIO around. This optimisation is gone in OpenSSL 3.2 and so the test for
verify fails because the memory BIO "ended".

Rewind the BIO before invoking verify again on the same data.

Signed-off-by: Sebastian Andrzej Siewior 
---
 tests/test_smime.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/tests/test_smime.py b/tests/test_smime.py
index 6014315353824..1fe7e954fcb89 100644
--- a/tests/test_smime.py
+++ b/tests/test_smime.py
@@ -162,10 +162,12 @@ from tests import unittest
 with self.assertRaises(SMIME.PKCS7_Error):
 s.verify(p7, data)
 
+data.seek(0)
 st.set_verify_cb(verify_cb_dummy_function)
 v = s.verify(p7, data)
 self.assertEqual(v, self.cleartext)
 
+data.seek(0)
 st.set_verify_cb()
 v = s.verify(p7, data)
 self.assertEqual(v, self.cleartext)
-- 
2.43.0

--- End Message ---
--- Begin Message ---
Source: m2crypto
Source-Version: 0.40.1-3
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
m2crypto, 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.
Andreas Beckmann  (supplier of updated m2crypto 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: Thu, 11 Apr 2024 17:29:26 +0200
Source: m2crypto
Architecture: source
Version: 0.40.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team ,
Changed-By: Andreas Beckmann 
Closes: 1063874
Changes:
 m2crypto (0.40.1-3) unstable; urgency=medium
 .
   * QA upload.
   * Cherry-pick upstream patch to fix testsuite with OpenSSL 3.2.
 (Closes: #1063874)
   * Declare Rules-Requires-Root: no.
   * Update Lintian overrides.
Checksums-Sha1:
 81c27e4c02d341c96d762cb80de325646f56c9f3 2292 m2crypto_0.40.1-3.dsc
 8afdd16130d47048847aaeb26a00213fdc82 59176 m2crypto_0.40.1-3.debian.tar.xz
 8b968b0e7eac2aab8fb859f7c75ca9a6d2d70bce 7993 
m2crypto_0.40.1-3_source.buildinfo
Checksums-Sha256:
 1437cf2405f0a6a959f4ef1f92758cfb750dcf37b47ebabc633f8893ee70c76e 2292 
m2crypto_0.40.1-3.dsc
 dbff5bf8a74beff89bc635fc94d9d744c0f0fc7d157b208768f4b9c05eaeaa63 59176 
m2crypto_0.40.1-3.debian.tar.xz
 0b9185ad1131c5464fe7a514e4886aa3bee8a449731bd8f34f25b06f05b85745 7993 
m2crypto_0.40.1-3_source.buildinfo
Files:
 8e7fa2d3152ae7ccfa8b253ee4f6a671 2292 python optional m2crypto_0.40.1-3.dsc
 2aabbfd9d18d4918d25dd94a4d29252c 59176 python optional 
m2crypto_0.40.1-3.debian.tar.xz
 79b6857d48a888be5e3fbb6fd7c8d1d4 7993 python optional 
m2crypto_0.40.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYYAlkQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCB4HD/9QER4tC5RTG4UwGp9kKgdwpAnWhs1+d9vy
afGdZrCw9iV3GjQh031liKXiAaq4St+597osrkfGtSVHzBM0mCY6EvXrwreolyUT
4mp944LrZWRLGhbmyCKpxe7hit9x0hp1IcziaKWvjKluUa/C/qB0mgdCsYUHW+Z5
J6Y5L1KKup6ZOgJfIxxOxeyy+Ho7SKTDzl7fYEitAag5dWI+pYXxos3OUL1XscMw
dwVjYR1sMsXSHElMTis3Sk/0fNI8G/qDm7MWir/nz7vDX43ZsoOe/44VWQb0sSIw

Processed: tagging 1067916

[Debian Bug Tracking System]

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

> tags 1067916 + help
Bug #1067916 [src:capnproto] FTBFS: tests failed
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#1068818: sngrep: CVE-2024-3119 CVE-2024-3120

[Moritz Mühlenhoff]

Source: sngrep
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for sngrep.

CVE-2024-3119[0]:
| A buffer overflow vulnerability exists in all versions of sngrep
| since v0.4.2, due to improper handling of 'Call-ID' and 'X-Call-ID'
| SIP headers. The functions sip_get_callid and sip_get_xcallid in
| sip.c use the strncpy function to copy header contents into fixed-
| size buffers without checking the data length. This flaw allows
| remote attackers to execute arbitrary code or cause a denial of
| service (DoS) through specially crafted SIP messages.

https://github.com/irontec/sngrep/commit/dd5fec92730562af6f96891291cd4e102b80bfcc
 (v1.8.1)

CVE-2024-3120[1]:
| A stack-buffer overflow vulnerability exists in all versions of
| sngrep since v1.4.1. The flaw is due to inadequate bounds checking
| when copying 'Content-Length' and 'Warning' headers into fixed-size
| buffers in the sip_validate_packet and sip_parse_extra_headers
| functions within src/sip.c. This vulnerability allows remote
| attackers to execute arbitrary code or cause a denial of service
| (DoS) via crafted SIP messages.

https://github.com/irontec/sngrep/commit/f3f8ed8ef38748e6d61044b39b0dabd7e37c6809
 (v1.8.1)

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-3119
https://www.cve.org/CVERecord?id=CVE-2024-3119
[1] https://security-tracker.debian.org/tracker/CVE-2024-3120
https://www.cve.org/CVERecord?id=CVE-2024-3120

Please adjust the affected versions in the BTS as needed.

Bug#1066512: marked as done (latencytop: FTBFS: fsync.c:330:17: error: implicit declaration of function ‘gettimeofday’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 15:35:31 +
with message-id 
and subject line Bug#1066512: fixed in latencytop 0.5.0-1
has caused the Debian Bug report #1066512,
regarding latencytop: FTBFS: fsync.c:330:17: error: implicit declaration of 
function ‘gettimeofday’ [-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.)


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

Hi,

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

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -DHAS_GTK_GUI 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -I/usr/include/atk-1.0 
> -pthread  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> -o latencytop-gtk_display.o `test -f 'gtk_display.c' || echo 
> './'`gtk_display.c
> fsync.c: In function ‘fsync_display’:
> fsync.c:330:17: error: implicit declaration of function ‘gettimeofday’ 
> [-Werror=implicit-function-declaration]
>   330 | gettimeofday(, NULL);
>   | ^~~~
> fsync.c: In function ‘parse_ftrace’:
> fsync.c:290:17: warning: ignoring return value of ‘fgets’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   290 | fgets(line, PATH_MAX-1, file);
>   | ^
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:525: latencytop-fsync.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/latencytop_0.5.0-0.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: latencytop
Source-Version: 0.5.0-1
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
latencytop, 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 latencytop package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 11:00:10 -0400
Source: latencytop
Architecture: source
Version: 0.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Boyuan Yang 
Changed-By: Boyuan Yang 
Closes: 1066512 1068786
Changes:
 latencytop (0.5.0-1) unstable; urgency=medium
 .
   * Take over package maintenance after consulting with the old
 package maintainer. 

Bug#1068816: undertow: CVE-2024-1459

[Moritz Mühlenhoff]

Source: undertow
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for undertow.

CVE-2024-1459[0]:
| A path traversal vulnerability was found in Undertow. This issue may
| allow a remote attacker to append a specially-crafted sequence to an
| HTTP request for an application deployed to JBoss EAP, which may
| permit access to privileged or restricted files and directories.

The only reference here is at Red Hat:
https://bugzilla.redhat.com/show_bug.cgi?id=2259475

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-1459
https://www.cve.org/CVERecord?id=CVE-2024-1459

Please adjust the affected versions in the BTS as needed.

Processed (with 1 error): nmu for 1065457 will fix this bug too

[Debian Bug Tracking System]

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

> tags 1066321 + pending
Bug #1066321 [src:openzwave] openzwave: FTBFS: cc1plus: error: ‘-Werror=’ 
argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror]
Added tag(s) pending.
> done
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#1068484: marked as done (juce-modules-source: Depends: libwebkit2gtk-4.0-dev but it is no longer built)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 15:05:08 +
with message-id 
and subject line Bug#1068484: fixed in juce 7.0.5+ds-2
has caused the Debian Bug report #1068484,
regarding juce-modules-source: Depends: libwebkit2gtk-4.0-dev but it is no 
longer built
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.)


-- 
1068484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: juce
Version: 7.0.5+ds-1
Severity: serious
Tags: trixie sid
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: webkit-4.0

Debian's webkit2gtk no longer builds the 4.0 API. The 4.1 API is the
same as the 4.0 API except that it uses libsoup3 instead of
libsoup2.4. Since juce does not use libsoup directly, it should be
possible to change all references to webkit2gtk-4.0 to webkit2gtk-4.1
in both the upstream code (with a patch) and in debian/control to fix
this issue.

Please let me know if you intend to fix this bug soon or I will likely
NMU this next week.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: juce
Source-Version: 7.0.5+ds-2
Done: Jeremy Bícha 

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated juce package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 10:47:48 -0400
Source: juce
Built-For-Profiles: noudeb
Architecture: source
Version: 7.0.5+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Jeremy Bícha 
Closes: 1068484
Changes:
 juce (7.0.5+ds-2) unstable; urgency=medium
 .
   * Team upload
   * Add patch to switch from webkit2gtk 4.0 to 4.1
   * Update juce-modules-source dependency (Closes: #1068484)
Checksums-Sha1:
 265d0cea6ca78567add477e295e29c7c7d1abd8b 2533 juce_7.0.5+ds-2.dsc
 c53afd35a906ab7693c5f73d9d722a8963cbaf06 43036 juce_7.0.5+ds-2.debian.tar.xz
 256e93d3e83544c849d22c321d30f62c91e3ed9f 10336 juce_7.0.5+ds-2_source.buildinfo
Checksums-Sha256:
 6f645d79dfe11f898b0cbced53205f9d4c8792d1d73dae5299611ad60227d394 2533 
juce_7.0.5+ds-2.dsc
 187e941dc38932d7e87e07abd88b49aaf533782746dd6e0cb6ec391221ac0daa 43036 
juce_7.0.5+ds-2.debian.tar.xz
 a8d16165baea3788b4c576378cb8e447059fc2c3c2a653d93113ceed8693c3f4 10336 
juce_7.0.5+ds-2_source.buildinfo
Files:
 496334ebaedf2ae1099ddedc85097608 2533 devel optional juce_7.0.5+ds-2.dsc
 c6a7fa6a8d58433fc7e4717b2dcfb733 43036 devel optional 
juce_7.0.5+ds-2.debian.tar.xz
 297371f781840b2a25cb2209db693c51 10336 devel optional 
juce_7.0.5+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmYX+NsACgkQ5mx3Wuv+
bH3BJxAAmRa8hROX2K/W/hg6TlxvzWCS+XBMjfgqGRTHxw13Bmzu2rbRLouIB9tK
vYMhkUlsVbbwki7G3TDRuUUfULDRarXSEqVqtVGw4nT0q+sKWX1ixBHikU2tW+dO
53plaN0bFTM0bhyEQPgzxioz3vQ/mUvn3S/TF90PCbzUvKlyUmDBma8EyJ/fBrQn
zM3GRXIqCIEiFXY6lps3/aK2FnnFEm0CXXM7BYs3ClKyvmrd4D139c5VAm/bXphy
x9dE8YfyVPwkuLjAKAOmYwnWv7HHBYTn4ZpSWlQZurm263WuUZnTzUqmxIgUJmsK
9vX+f+ZuSnFqDFEM6Ddi13HoTQzGkrgtptE2JX5C35KqA5/w4taRkmShLBeh3ten
A0Lt7vQmgYhWFCU+bsiThJrVSqD66l98zIY0SanxTCLqtnDk/AMpitHYRnNIeLcJ
FmhkeKO9QMNK479/hl0ysmytZdmYYhRfxoDV3Ndl79w/O97+idaO63rWdqUkkDts
hxakQ9B0nUhiyYfQb2jVavmTzxZKiZIEuybnNuZXvB19nRoIjqMz8jwcBESg/YCl
VINHSyZq2MSiizoUvOJ+6F5Xze3tyiRjHAC71ISNwigJ0DnUuu8OntNYTeZkiujy
bHJnxW9ZUQ6qt9cn+XVhSwctMOdIC4wT1mrJXqU/5qsQzYWsWJc=
=xLe4
-END PGP SIGNATURE-



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

Bug#1066386: marked as done (examl: FTBFS: quartets.c:393:31: error: implicit declaration of function ‘basename’; did you mean ‘rename’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 14:49:02 +
with message-id 
and subject line Bug#1066386: fixed in examl 3.0.22-5
has caused the Debian Bug report #1066386,
regarding examl: FTBFS: quartets.c:393:31: error: implicit declaration of 
function ‘basename’; did you mean ‘rename’? 
[-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.)


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

Hi,

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

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/examl'
> rm -f *.o examl-avx2
> mpicc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -mavx2 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o axml.o axml.c
> In function ‘initializePartitions’,
> inlined from ‘initializeTree’ at axml.c:2217:3,
> inlined from ‘main’ at axml.c:2631:5:
> axml.c:2121:40: warning: argument 1 range [18446744071562067968, 
> 18446744073709551615] exceeds maximum object size 9223372036854775807 
> [-Walloc-size-larger-than=]
>  2121 |   *modelWeights = (unsigned long*) calloc(tr->NumberOfModels, 
> sizeof(unsigned long));
>   |
> ^
> In file included from axml.c:44:
> /usr/include/stdlib.h: In function ‘main’:
> /usr/include/stdlib.h:556:14: note: in a call to allocation function ‘calloc’ 
> declared here
>   556 | extern void *calloc (size_t __nmemb, size_t __size)
>   |  ^~
> mpicc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -mavx2 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o optimizeModel.o optimizeModel.c
> mpicc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -mavx2 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o trash.o trash.c
> mpicc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -mavx2 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o searchAlgo.o searchAlgo.c
> mpicc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -mavx2 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o topologies.o topologies.c
> mpicc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -mavx2 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o treeIO.o treeIO.c
> mpicc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -mavx2 -D_OPTIMIZED_FUNCTIONS 
> -D_GNU_SOURCE -fomit-frame-pointer -funroll-loops -D_USE_ALLREDUCE  -O1 
> -Wdate-time -D_FORTIFY_SOURCE=2 -c -o models.o models.c
> mpicc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -mavx2 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o evaluatePartialGenericSpecial.o 
> evaluatePartialGenericSpecial.c
> mpicc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fopenmp-simd -O3 

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

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 14:36:13 +
with message-id 
and subject line Bug#1066475: fixed in libpsortb 1.0+dfsg-6
has caused the Debian Bug report #1066475,
regarding libpsortb: FTBFS: debug_funcs.c:320:38: error: implicit declaration 
of function ‘get_mtx_index’ [-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.)


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

Hi,

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

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
>  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o std_funcs.lo std_funcs.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> debug_funcs.c  -fPIC -DPIC -o .libs/debug_funcs.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> readseqs_multialpha.c  -fPIC -DPIC -o .libs/readseqs_multialpha.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> readhmm.c  -fPIC -DPIC -o .libs/readhmm.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> hmmsearch.c  -fPIC -DPIC -o .libs/hmmsearch.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> std_calculation_funcs.c  -fPIC -DPIC -o .libs/std_calculation_funcs.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> readhmm_multialpha.c  -fPIC -DPIC -o .libs/readhmm_multialpha.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> core_algorithms_multialpha.c  -fPIC -DPIC -o 
> .libs/core_algorithms_multialpha.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> std_funcs.c  -fPIC -DPIC -o .libs/std_funcs.o
> debug_funcs.c: In function ‘dump_viterbi_path’:
> debug_funcs.c:320:38: error: implicit declaration of function ‘get_mtx_index’ 
> [-Werror=implicit-function-declaration]
>   320 | dump_viterbi_path(viterbi_mtxp + get_mtx_index(row-1, cur->prev, 
> row_size), hmmp,
>   |  ^
> debug_funcs.c: In function ‘dump_replacement_letters’:
> debug_funcs.c:861:14: warning: format ‘%c’ expects argument of type ‘int’, 
> but argument 2 has type ‘struct letter_s’ [-Wformat=]
>   861 | printf("%c ", (*(replacement_letters->letters + i)));
>   | ~^

Bug#1068484: marked as done (juce-modules-source: Depends: libwebkit2gtk-4.0-dev but it is no longer built)

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 14:36:05 +
with message-id 
and subject line Bug#1068484: fixed in juce 7.0.11+ds-1~exp2
has caused the Debian Bug report #1068484,
regarding juce-modules-source: Depends: libwebkit2gtk-4.0-dev but it is no 
longer built
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.)


-- 
1068484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: juce
Version: 7.0.5+ds-1
Severity: serious
Tags: trixie sid
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: webkit-4.0

Debian's webkit2gtk no longer builds the 4.0 API. The 4.1 API is the
same as the 4.0 API except that it uses libsoup3 instead of
libsoup2.4. Since juce does not use libsoup directly, it should be
possible to change all references to webkit2gtk-4.0 to webkit2gtk-4.1
in both the upstream code (with a patch) and in debian/control to fix
this issue.

Please let me know if you intend to fix this bug soon or I will likely
NMU this next week.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: juce
Source-Version: 7.0.11+ds-1~exp2
Done: Jeremy Bícha 

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated juce package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 10:14:55 -0400
Source: juce
Built-For-Profiles: noudeb
Architecture: source
Version: 7.0.11+ds-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Jeremy Bícha 
Closes: 1068484
Changes:
 juce (7.0.11+ds-1~exp2) experimental; urgency=medium
 .
   * Team upload
   * Add patch to switch from webkit2gtk 4.0 to 4.1
   * Update juce-modules-source dependency (Closes: #1068484)
Checksums-Sha1:
 825039729f40699cacd3f6de88d2fbfb20349c3b 2605 juce_7.0.11+ds-1~exp2.dsc
 dde109e518716dc42433ed714813d0e42af152b9 44264 
juce_7.0.11+ds-1~exp2.debian.tar.xz
 7793579981e5b87a0af366af133fe38d6d965be3 10360 
juce_7.0.11+ds-1~exp2_source.buildinfo
Checksums-Sha256:
 3b8c2885268a7a7aecec2be40735d4fed8bf42a02eee6cd19b737a95d68d63c1 2605 
juce_7.0.11+ds-1~exp2.dsc
 5ff66cdd1a6506d45cd34968f97da0c706004bd1dd5f89f36ae90c23c56d52d1 44264 
juce_7.0.11+ds-1~exp2.debian.tar.xz
 0cd93287335870a34498738d66d990877bd1df8f7caff4b596d5b6bb5771602e 10360 
juce_7.0.11+ds-1~exp2_source.buildinfo
Files:
 e79af0358031f1e30272c37fe619e0a2 2605 devel optional juce_7.0.11+ds-1~exp2.dsc
 6c349e4f6995b140fe143a9e796c031d 44264 devel optional 
juce_7.0.11+ds-1~exp2.debian.tar.xz
 5b851dd6778ffd6c96c4f68a6cfde1f0 10360 devel optional 
juce_7.0.11+ds-1~exp2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmYX8JUACgkQ5mx3Wuv+
bH3APxAAvz8o0zMCnPZhw8NmzDHNr9Zkg5sHivYSdPe3OWLE5SJ9+vsoaAJtM7cI
eqGl9M42DMXDQNk1UnqNxPiuyQlBT6LH9wkze5woWCsB8PvojynrssZy5GorkYFw
WG3M2u6gholyK6PahULktwKbe5Kzc5yblgXWdORraN1emk3wtrmzhci+RHr1pP+v
JxEiCIIVF9PwagsJIvoI9RQwU4NumjN58XlrWYCidxpzzVf8SYj2Vaz7K5BJjK8J
x9qKc9eu2gbaSN5f5i1b47XNUKI47WUMDuuMeO3bzz3NjlF7qLzQUEdkb3gzymiJ
aBIuMPTltQ0JpnefwqvJmoShw9VucteBu4IUvzIHxcGa7d7Vri8erMbkSKaHPua/
TrkaaDtSQZORnd2a6tCiu0u5oeG/ap89IHqAaErDMJq/Fa5MYlQ53cSuXLTVwdaK
+bETNnUR43mOpkmE7aZ99f3gk0DXfuBz6wfNj3Z4q7Qs/0QzafHiFVAcAIKqs/Sx
xnxqvH7vWhPrV/AeBCDL0GY5PixMMgtFQH55wDzJWO0pzij305Utnii+rIS0WKb/
sqfmQGoWOPVBQpugWgYoBHpTxeozqAkIonHib77y8wHnKIabnJomZpxw8YnXl5hm
Q3CP9yft+tFX2S0B2QVu9bP4foXfej0l64e2+7mL8sz/fxfjHFI=
=g7FY
-END PGP SIGNATURE-



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

Processed: Bug#1068484 marked as pending in juce

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068484 [src:juce] juce-modules-source: Depends: libwebkit2gtk-4.0-dev but 
it is no longer built
Added tag(s) pending.

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

Bug#1068484: marked as pending in juce

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1068484 in juce 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/multimedia-team/juce/-/commit/8589e4cb7ab11c92780c062347ca41af13526ff2


Update juce-modules-source dependency

Closes: #1068484


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068484

Bug#1068812: pcb-rnd: hardcoded librnd4 dependency

[Gianfranco Costamagna]

Package: pcb-rnd
Version: 3.1.4-1
Severity: serious
Tags: patch


Hello, I found that librnd4 is correctly evaluated from shlibs:Depends in the 
core library and then it can be dropped also on core reverse-dependencies.


Please drop it.


Thanks for considering the patch.

diff -Nru pcb-rnd-3.1.4/debian/control pcb-rnd-3.1.4/debian/control
--- pcb-rnd-3.1.4/debian/control2024-03-14 00:19:26.0 +0100
+++ pcb-rnd-3.1.4/debian/control2024-04-11 15:53:47.0 +0200
@@ -162,7 +162,7 @@
 
 Package: pcb-rnd-export

 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, pcb-rnd-core (= 
${binary:Version}), librnd4, librnd4-pixmap
+Depends: ${misc:Depends}, ${shlibs:Depends}, pcb-rnd-core (= 
${binary:Version}), librnd4-pixmap
 Description: Common export plugins.
  Export the board in vector graphics (svg, ps, eps), raster graphics
  (png, jpeg, etc.), gerber, 3d model in openscad, xy for pick and
@@ -192,7 +192,6 @@
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends},
pcb-rnd-core (= ${binary:Version}),
-   librnd4
 Replaces: pcb-rnd (<< 2.2.0-2)
 Breaks: pcb-rnd (<< 2.2.0-2)
 Description: Netlist/schematics import plugins.
@@ -203,7 +202,6 @@
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends},
pcb-rnd-core (= ${binary:Version}),
-   librnd4,
pcb-rnd-lib-io (= ${binary:Version}),
pcb-rnd-io-standard (= ${binary:Version})
 Description: Autoroute and autoplace.
@@ -238,7 +236,7 @@
 
 Package: pcb-rnd-core

 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, librnd4
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Replaces: pcb-rnd (<< 2.2.0-2)
 Breaks: pcb-rnd (<< 2.2.0-2)
 Description: pcb-rnd executable with the core functionality
@@ -252,8 +250,7 @@
 Depends: ${misc:Depends}, ${shlibs:Depends},
pcb-rnd-core (= ${binary:Version}),
pcb-rnd-lib-io (= ${binary:Version}),
-   pcb-rnd-extra (= ${binary:Version}),
-   librnd4
+   pcb-rnd-extra (= ${binary:Version})
 Description: File format compatibility with other PCB layout designers.
  Load and/or save boards in file formats supported by other EDA tools,
  such as KiCAD, Eagle, protel/autotrax, etc.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Re: sch-rnd: hardcoded librnd4 dependency

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1068810 [sch-rnd] sch-rnd: hardcoded librnd4 dependency
Severity set to 'serious' from 'normal'

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

Bug#1068811: camv-rnd: hardcoded librnd4 dependency

[Gianfranco Costamagna]

Package: camv-rnd
Version: 1.1.4-1
Severity: serious
Tags: patch


Hello, I found that librnd4 is correctly evaluated from shlibs:Depends in the 
core library and then it can be dropped also on core reverse-dependencies.


Please drop it.


Thanks for considering the patch.

diff -Nru camv-rnd-1.1.4/debian/control camv-rnd-1.1.4/debian/control
--- camv-rnd-1.1.4/debian/control   2023-11-30 16:53:21.0 +0100
+++ camv-rnd-1.1.4/debian/control   2024-04-11 15:44:20.0 +0200
@@ -47,7 +47,7 @@
 Architecture: any
 Replaces: camv-rnd (<< 1.1.0-1)
 Breaks: camv-rnd (<< 1.1.0-1)
-Depends: ${misc:Depends}, ${shlibs:Depends}, librnd4, librnd4-lib-gui
+Depends: ${misc:Depends}, ${shlibs:Depends}, librnd4-lib-gui
 Description: camv-rnd executable with the core functionality and boxsym-rnd
  Includes the data model, the most common action commands, the native
  file format. Can be used in headless mode or batch/scripted mode for
@@ -56,7 +56,7 @@
 
 Package: camv-rnd-export-vector

 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, camv-rnd-core (= 
${binary:Version}), librnd4
+Depends: ${misc:Depends}, ${shlibs:Depends}, camv-rnd-core (= 
${binary:Version})
 Description: Export formats: vector graphics
  Common vector graphic export formats: ps, eps, svg.
 


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065457: openzwave: diff for NMU version 1.6.1914+ds-1.2

[Chris Hofstaedtler]

Control: tags 1065457 + patch
Control: tags 1065457 + pending

Dear maintainer,

I've prepared an NMU for openzwave (versioned as 1.6.1914+ds-1.2) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru openzwave-1.6.1914+ds/debian/changelog openzwave-1.6.1914+ds/debian/changelog
--- openzwave-1.6.1914+ds/debian/changelog	2024-02-29 19:55:23.0 +0100
+++ openzwave-1.6.1914+ds/debian/changelog	2024-04-11 15:37:03.0 +0200
@@ -1,3 +1,15 @@
+openzwave (1.6.1914+ds-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload. (Closes: #1065457)
+  * Bump dpkg-dev versioned Build-Depends for t64 transition.
+  * Patch upstream Makefiles to show compiler invocations.
+  * Patch additional upstream Makefile to remove -Wno-format.
+  * Build-Depends: add pkgconf, necessary to place .pc file.
+  * Reduce CPPFLAGS updating, to avoid unknown ‘-Werror=implicit-function-declaration’
+in cc1plus aborting the build.
+
+ -- Chris Hofstaedtler   Thu, 11 Apr 2024 15:37:03 +0200
+
 openzwave (1.6.1914+ds-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru openzwave-1.6.1914+ds/debian/control openzwave-1.6.1914+ds/debian/control
--- openzwave-1.6.1914+ds/debian/control	2024-02-29 19:55:23.0 +0100
+++ openzwave-1.6.1914+ds/debian/control	2024-04-11 15:37:03.0 +0200
@@ -7,7 +7,8 @@
 	, dh-exec (>=0.2)
 	, libudev-dev
 	, libxml2-utils
-  , dpkg-dev (>= 1.20)
+	, dpkg-dev (>= 1.22.6)
+	, pkgconf
 Standards-Version: 4.6.0
 Homepage: http://www.openzwave.net/
 Vcs-Browser: https://salsa.debian.org/debian-iot-team/openzwave
diff -Nru openzwave-1.6.1914+ds/debian/patches/makefile-no-silent.patch openzwave-1.6.1914+ds/debian/patches/makefile-no-silent.patch
--- openzwave-1.6.1914+ds/debian/patches/makefile-no-silent.patch	1970-01-01 01:00:00.0 +0100
+++ openzwave-1.6.1914+ds/debian/patches/makefile-no-silent.patch	2024-04-11 15:37:03.0 +0200
@@ -0,0 +1,146 @@
+Index: openzwave-1.6.1914+ds/cpp/build/support.mk
+===
+--- openzwave-1.6.1914+ds.orig/cpp/build/support.mk
 openzwave-1.6.1914+ds/cpp/build/support.mk
+@@ -184,24 +184,24 @@ endif
+ 
+ $(OBJDIR)/%.o : %.cpp
+ 	@echo "Building $(<:$(top_builddir)/cpp/%=%)"
+-	@$(CXX) -MM $(CFLAGS) $(CPPFLAGS) $(INCLUDES) $< > $(DEPDIR)/$*.d
++	$(CXX) -MM $(CFLAGS) $(CPPFLAGS) $(INCLUDES) $< > $(DEPDIR)/$*.d
+ 	@mv -f $(DEPDIR)/$*.d $(DEPDIR)/$*.d.tmp
+ 	@$(SED) -e 's|.*:|$(OBJDIR)/$*.o: $(DEPDIR)/$*.d|' < $(DEPDIR)/$*.d.tmp > $(DEPDIR)/$*.d;
+ 	@$(SED) -e 's/.*://' -e 's/\\$$//' < $(DEPDIR)/$*.d.tmp | $(FMTCMD) | \
+ 	  $(SED) -e 's/^ *//' -e 's/$$/:/' >> $(DEPDIR)/.$*.d;
+ 	@rm -f $(DEPDIR)/$*.d.tmp
+-	@$(CXX) $(CFLAGS) $(CPPFLAGS) $(TARCH) $(INCLUDES) -o $@ $<
++	$(CXX) $(CFLAGS) $(CPPFLAGS) $(TARCH) $(INCLUDES) -o $@ $<
+ 
+ 
+ $(OBJDIR)/%.o : %.c
+ 	@echo "Building $(<:$(top_builddir)/cpp/src/%=%)"
+-	@$(CC) -MM $(CFLAGS) $(INCLUDES) $< > $(DEPDIR)/$*.d
++	$(CC) -MM $(CFLAGS) $(INCLUDES) $< > $(DEPDIR)/$*.d
+ 	@mv -f $(DEPDIR)/$*.d $(DEPDIR)/$*.d.tmp
+ 	@$(SED) -e 's|.*:|$(OBJDIR)/$*.o: $(DEPDIR)/$*.d|' < $(DEPDIR)/$*.d.tmp > $(DEPDIR)/$*.d;
+ 	@$(SED) -e 's/.*://' -e 's/\\$$//' < $(DEPDIR)/$*.d.tmp | $(FMTCMD) | \
+ 	  $(SED) -e 's/^ *//' -e 's/$$/:/' >> $(DEPDIR)/.$*.d;
+ 	@rm -f $(DEPDIR)/$*.d.tmp
+-	@$(CC) $(CFLAGS) $(TARCH) $(INCLUDES) -o $@ $<
++	$(CC) $(CFLAGS) $(TARCH) $(INCLUDES) -o $@ $<
+ 
+ 
+ dummy := $(shell test -d $(OBJDIR) || mkdir -p $(OBJDIR))
+Index: openzwave-1.6.1914+ds/cpp/build/Makefile
+===
+--- openzwave-1.6.1914+ds.orig/cpp/build/Makefile
 openzwave-1.6.1914+ds/cpp/build/Makefile
+@@ -206,7 +206,7 @@ $(LIBDIR)/$(SHARED_LIB_NAME):	$(patsubst
+ 			$(patsubst %.cpp,$(OBJDIR)/%.o,$(indep)) \
+ 			$(OBJDIR)/vers.o
+ 	@echo "Linking Shared Library"
+-	@$(LD) $(LDFLAGS) $(TARCH) -o $@ $+ $(LIBS)
++	$(LD) $(LDFLAGS) $(TARCH) -o $@ $+ $(LIBS)
+ 	@ln -sf $(SHARED_LIB_NAME) $(LIBDIR)/$(SHARED_LIB_UNVERSIONED)
+ 
+ $(top_builddir)/libopenzwave.pc: $(top_srcdir)/cpp/build/libopenzwave.pc.in $(PKGCONFIG)
+@@ -256,35 +256,35 @@ endif
+ 
+ install: $(LIBDIR)/$(SHARED_LIB_NAME) doc $(top_builddir)/libopenzwave.pc $(top_builddir)/ozw_config
+ 	@echo "Installing Shared Library"
+-	@install -d $(DESTDIR)/$(instlibdir)/
+-	@cp  $(LIBDIR)/$(SHARED_LIB_NAME) $(DESTDIR)/$(instlibdir)/$(SHARED_LIB_NAME)
+-	@ln -sf $(SHARED_LIB_NAME) $(DESTDIR)/$(instlibdir)/$(SHARED_LIB_UNVERSIONED)
++	install -d $(DESTDIR)/$(instlibdir)/
++	cp  $(LIBDIR)/$(SHARED_LIB_NAME) $(DESTDIR)/$(instlibdir)/$(SHARED_LIB_NAME)
++	ln -sf $(SHARED_LIB_NAME) $(DESTDIR)/$(instlibdir)/$(SHARED_LIB_UNVERSIONED)
+ 	@echo "Installing Headers"
+-	@install -d $(DESTDIR)/$(includedir)
+-	@install -m 0644 $(top_srcdir)/cpp/src/*.h $(DESTDIR)/$(includedir)
+-	@install -d $(DESTDIR)/$(includedir)/command_classes/
+-	@install -m 0644 $(top_srcdir)/cpp/src/command_classes/*.h 

Processed: openzwave: diff for NMU version 1.6.1914+ds-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1065457 + patch
Bug #1065457 [src:openzwave] openzwave: FTBFS: dh_install: error: missing 
files, aborting
Added tag(s) patch.
> tags 1065457 + pending
Bug #1065457 [src:openzwave] openzwave: FTBFS: dh_install: error: missing 
files, aborting
Added tag(s) pending.

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

Processed: openmpi-bin has an undeclared file conflict on /usr/bin/pterm

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + pterm
Bug #1068808 [openmpi-bin] openmpi-bin has an undeclared file conflict on 
/usr/bin/pterm
Added indication that 1068808 affects pterm

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

Bug#1068808: openmpi-bin has an undeclared file conflict on /usr/bin/pterm

[Helmut Grohne]

Package: openmpi-bin
Version: 5.0.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + pterm

openmpi-bin has an undeclared file conflict. This may result in an
unpack error from dpkg.

The file /usr/bin/pterm is contained in the packages
 * openmpi-bin/5.0.3-1 as present in experimental
 * pterm
   * 0.74-1+deb11u1 as present in bullseye|bullseye-security
   * 0.78-2+deb12u1 as present in bookworm|bookworm-security
   * 0.80-1 as present in trixie
   * 0.80-1+b1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Processed: affects 1067311

[Debian Bug Tracking System]

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

> affects 1067311 + src:matplotlib
Bug #1067311 [src:ipywidgets] ipywidgets: FTBFS: unsatisfiable 
build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 
8.1.1-2 is to be installed
Bug #1067315 [src:ipywidgets] matplotlib: FTBFS: unsatisfiable 
build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 
8.1.1-2 is to be installed
Added indication that 1067311 affects src:matplotlib
Added indication that 1067315 affects src:matplotlib
> thanks
Stopping processing here.

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

Bug#1066285: marked as done (nvi: FTBFS: ../dist/../common/options_f.c:324:16: error: implicit declaration of function 'conv_enc' [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 13:19:49 +
with message-id 
and subject line Bug#1066285: fixed in nvi 1.81.6-21
has caused the Debian Bug report #1066285,
regarding nvi: FTBFS: ../dist/../common/options_f.c:324:16: error: implicit 
declaration of function 'conv_enc' [-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.)


-- 
1066285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvi
Version: 1.81.6-20
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 -DHAVE_CONFIG_H -I. -I../dist -D__REGEX_PRIVATE -I. 
> -I../dist/../include -DVI=\"/usr/bin/nvi-ipc\" -I../dist/../regex -Wdate-time 
> -D_FORTIFY_SOURCE=2 -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 ../dist/../common/options_f.c -o 
> options_f.o
> ../dist/../common/options_f.c: In function 'f_encoding':
> ../dist/../common/options_f.c:324:16: error: implicit declaration of function 
> 'conv_enc' [-Werror=implicit-function-declaration]
>   324 | return conv_enc(sp, offset, str);
>   |^~~~
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:902: options_f.lo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/nvi_1.81.6-20_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: nvi
Source-Version: 1.81.6-21
Done: Tobias Heider 

We believe that the bug you reported is fixed in the latest version of
nvi, 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.
Tobias Heider  (supplier of updated nvi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 11:51:27 +0200
Source: nvi
Architecture: source
Version: 1.81.6-21
Distribution: unstable
Urgency: medium
Maintainer: Tobias Heider 
Changed-By: Tobias Heider 
Closes: 769719 771375 1066285
Changes:
 nvi (1.81.6-21) unstable; urgency=medium
 .
   [ Tobias Heider ]
   * Fix shell quoting in recovery mail script. (Closes: #769719).
   * Fix TOCTOU issue with creation and chmod of vi.recovery.  An attacker
 could exploit this to chmod arbitrary files via symlinks by creating
 it at the right time (Closes: #771375).
   * Add function prototypes to fix implicit function declaration errors
 (Closes: #1066285).
 .
   [ Paride Legovini ]
   * CI: add salsa-ci-team pipeline
Checksums-Sha1:
 cfdb42187cb5b447ea2268b8fc3def70cc72e0d0 1850 nvi_1.81.6-21.dsc
 ce3e0d7d476fb3bdcce9d547e170152290db0347 2324452 nvi_1.81.6.orig.tar.gz
 779032d5b78b468964d5e66edd425382e653c3bd 110424 nvi_1.81.6-21.debian.tar.xz
 5df5d18f79eb4bf7f2e7d21805ff4b05f93d378b 5927 nvi_1.81.6-21_source.buildinfo
Checksums-Sha256:
 

Processed: reassign 1067315 to src:ipywidgets, affects 1067315, forcibly merging 1067311 1067315

[Debian Bug Tracking System]

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

> reassign 1067315 src:ipywidgets
Bug #1067315 [src:matplotlib] matplotlib: FTBFS: unsatisfiable 
build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 
8.1.1-2 is to be installed
Bug reassigned from package 'src:matplotlib' to 'src:ipywidgets'.
No longer marked as found in versions matplotlib/3.6.3-1.1.
Ignoring request to alter fixed versions of bug #1067315 to the same values 
previously set
> affects 1067315 src:matplotlib
Bug #1067315 [src:ipywidgets] matplotlib: FTBFS: unsatisfiable 
build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 
8.1.1-2 is to be installed
Added indication that 1067315 affects src:matplotlib
> forcemerge 1067311 1067315
Bug #1067311 [src:ipywidgets] ipywidgets: FTBFS: unsatisfiable 
build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 
8.1.1-2 is to be installed
Bug #1067315 [src:ipywidgets] matplotlib: FTBFS: unsatisfiable 
build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 
8.1.1-2 is to be installed
Removed indication that 1067315 affects src:matplotlib
The source ipywidgets and version 8.1.1-4 do not appear to match any binary 
packages
Marked as found in versions ipywidgets/8.1.1-4.
Merged 1067311 1067315
> thanks
Stopping processing here.

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

Processed (with 1 error): forcibly merging 1067311 1067315

[Debian Bug Tracking System]

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

> forcemerge 1067311 1067315
Bug #1067311 [src:ipywidgets] ipywidgets: FTBFS: unsatisfiable 
build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 
8.1.1-2 is to be installed
Unable to merge bugs because:
package of #1067315 is 'src:matplotlib' not 'src:ipywidgets'
Failed to forcibly merge 1067311: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: Re: Bug#1067367: mathgl: FTBFS: debian/tests/run-tests: 37: python3.12: not found

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1067367 [src:mathgl] mathgl: FTBFS: debian/tests/run-tests: 37: 
python3.12: not found
Added tag(s) patch.

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

Bug#1067367: mathgl: FTBFS: debian/tests/run-tests: 37: python3.12: not found

[Emanuele Rocca]

Control: tags -1 + patch

Hi,

On 2024-03-20 09:46, Lucas Nussbaum wrote:
> > debian/tests/run-tests: 37: python3.12: not found

This is because debian/tests/run-tests iterates over all supported
python versions (py3versions -s), but only python3.11 is installed.

Please consider build-depending on python3-all (see attached patch) to
ensure all supported python runtimes are installed.
diff -Nru mathgl-8.0.1/debian/changelog mathgl-8.0.1/debian/changelog
--- mathgl-8.0.1/debian/changelog	2024-02-15 07:53:06.0 +0100
+++ mathgl-8.0.1/debian/changelog	2024-04-11 15:00:39.0 +0200
@@ -1,3 +1,10 @@
+mathgl (8.0.1-8) unstable; urgency=medium
+
+  * Build-depend on python3-all to ensure all supported python versions are
+installed when running debian/tests/run-tests. (Closes: #1067367)
+
+ -- Emanuele Rocca   Thu, 11 Apr 2024 15:00:39 +0200
+
 mathgl (8.0.1-7) unstable; urgency=medium
 
   * Team upload.
diff -Nru mathgl-8.0.1/debian/control mathgl-8.0.1/debian/control
--- mathgl-8.0.1/debian/control	2024-02-15 07:53:06.0 +0100
+++ mathgl-8.0.1/debian/control	2024-04-11 15:00:13.0 +0200
@@ -38,6 +38,7 @@
  mpi-default-dev,
  python3-dev,
  python3-numpy,
+ python3-all , 
  qtwebengine5-dev [amd64 arm64 armhf i386],
  swig,
  texinfo,

Processed: block 1036884 with 1065790

[Debian Bug Tracking System]

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

> block 1036884 with 1065790
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1065816 1065787 1068068 1067494 1067190 1067829 1068327 
1067561 1067677 1066049 1067189 1067171 1055352 1067676 1067192 1067193 1067069 
1067272 1067509 1067175 1067288 1067170 1068586 1066794 1067916 1067458 1067508 
1066328 1062847 1065973 1068325 1068160 1055530
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1065790
> thanks
Stopping processing here.

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

Bug#1068806: Update Build-Depends for the time64 library renames

[Andrey Rakhmatullin]

Source: osmo-bts
Version: 1.5.0dfsg1-2
Severity: serious
Tags: ftbfs

The package explicitly Build-Depends: libosmocoding0, this needs to be changed
to
libosmocoding0t64 if this dep is needed at all.


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_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#1068805: python3-pywt: distutils not available in Python 3.12

[Ole Streicher]

Package: python3-pywt
Version: 1.1.1-3
Severity: serious

Dear maintainer,

pywt directly depends on distutils, which is no longer available on 
Python 3.12. in pywt/__init__.py:


---8<--
from __future__ import division, print_function, absolute_import
from distutils.version import LooseVersion
---8<--

This makes the current version of pywt unusable on Python 3.12.

Best

Ole

Bug#1067371: marked as done (nncp: FTBFS: Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so: libharfbuzz.so.0: cannot open shared obje

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 06:56:40 -0500
with message-id <87cyqw5cx1@complete.org>
and subject line Fixed by a newer plantuml
has caused the Debian Bug report #1067371,
regarding nncp: FTBFS: Exception in thread "main" 
java.lang.UnsatisfiedLinkError: 
/usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so: libharfbuzz.so.0: 
cannot open shared object file: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nncp
Version: 8.10.0-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> #mkdir -p _build/src/go.cypherpunks.ru/nncp/v7
> #cp -r src/* _build/src/go.cypherpunks.ru/nncp/v7/
> #ln -s src/uilive _build/src/go.cypherpunks.ru/nncp/v7/uilive
> mv -vi _build/src/go.cypherpunks.ru/nncp/v7/src/* 
> _build/src/go.cypherpunks.ru/nncp/v7/
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/area.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/area.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/call.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/call.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/cfg.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/cfg.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/cfgdir.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/cfgdir.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/check.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/check.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/chunked.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/chunked.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/cmd' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/cmd'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/ctx.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/ctx.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/df.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/df.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/df_netbsd.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/df_netbsd.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/df_openbsd.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/df_openbsd.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/dirwatch.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/dirwatch.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/dirwatch_dummy.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/dirwatch_dummy.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/eblob.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/eblob.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/humanizer.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/humanizer.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/jobs.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/jobs.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/lockdir.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/lockdir.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/log.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/log.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/magic.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/magic.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/mcd.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/mcd.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/mth.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/mth.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/mth_test.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/mth_test.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/nice.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/nice.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/nice_test.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/nice_test.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/nncp.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/nncp.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/node.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/node.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/pipe.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/pipe.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/pkt.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/pkt.go'
> renamed '_build/src/go.cypherpunks.ru/nncp/v7/src/pkt_test.go' -> 
> '_build/src/go.cypherpunks.ru/nncp/v7/pkt_test.go'
> renamed 

Bug#1066300: marked as done (ampliconnoise: FTBFS: FCluster.c:230:13: error: implicit declaration of function ‘UpdateMinCacheForRow’; did you mean ‘UpdateMinCacheForMarkedRows’? [-Werror=implicit-func

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 09:19:05 +
with message-id 
and subject line Bug#1066300: fixed in ampliconnoise 1.29-11
has caused the Debian Bug report #1066300,
regarding ampliconnoise: FTBFS: FCluster.c:230:13: error: implicit declaration 
of function ‘UpdateMinCacheForRow’; did you mean ‘UpdateMinCacheForMarkedRows’? 
[-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.)


-- 
1066300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ampliconnoise
Version: 1.29-10
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 
> -c FCluster.c 
> FCluster.c:223:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   223 | UpdateMinCacheForMarkedRows(struct t_Min* asMin,float** 
> aafDistMatrix,int nN)
>   | ^~~
> FCluster.c: In function ‘UpdateMinCacheForMarkedRows’:
> FCluster.c:230:13: error: implicit declaration of function 
> ‘UpdateMinCacheForRow’; did you mean ‘UpdateMinCacheForMarkedRows’? 
> [-Werror=implicit-function-declaration]
>   230 | UpdateMinCacheForRow(asMin,i,aafDistMatrix);
>   | ^~~~
>   | UpdateMinCacheForMarkedRows
> FCluster.c: At top level:
> FCluster.c:237:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   237 | UpdateMinCacheForRow(struct t_Min* asMin,int i,float** aafDistMatrix)
>   | ^~~~
> cc1: some warnings being treated as errors
> make[2]: *** [makefile:13: FCluster.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/ampliconnoise_1.29-10_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: ampliconnoise
Source-Version: 1.29-11
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
ampliconnoise, 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.
Andreas Tille  (supplier of updated ampliconnoise package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Apr 2024 09:56:08 +0200
Source: ampliconnoise
Architecture: source
Version: 1.29-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1066300
Changes:
 ampliconnoise (1.29-11) unstable; urgency=medium
 .
   * Fix the sequence of function definitions to make sure
 UpdateMinCacheForRow() is known before its first usage
 Closes: #1066300
   * Adjust DEP3 headers and add Forwarded: No (orphaned upstream)
   * Add missing header file
   * Standards-Version: 4.7.0 (routine-update)
Checksums-Sha1:
 c84dea8fd60c94d7535dfa13b99059e80fa59902 2156 ampliconnoise_1.29-11.dsc
 1f1f4d9db0993658c7c000285bbd2f82ac1272c3 

Processed: tagging 1066668

[Debian Bug Tracking System]

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

> tags 108 - trixie
Bug #108 {Done: Samuel Thibault } [src:sphinxtrain] 
sphinxtrain: FTBFS: lexicon.c:202:19: error: implicit declaration of function 
‘str2words’ [-Werror=implicit-function-declaration]
Removed tag(s) trixie.
> thanks
Stopping processing here.

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

Processed: re-close

[Debian Bug Tracking System]

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

> close 1066414
Bug #1066414 [libgenht1-dev] pcb-rnd: FTBFS: 
./util/bxl2txt/./util/bxl2txt/txt2bxl.c:43: multiple definition of `main'; 
/usr/lib/libgenht.a(mainsi.o):(.text+0x9d): first defined here
Marked Bug as done
>
End of message, stopping processing here.

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

Processed: fix a mess

[Debian Bug Tracking System]

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

> reassign 1066414 libgenht1-dev
Bug #1066414 {Done: Bdale Garbee } [src:pcb-rnd] pcb-rnd: FTBFS: 
./util/bxl2txt/./util/bxl2txt/txt2bxl.c:43: multiple definition of `main'; 
/usr/lib/libgenht.a(mainsi.o):(.text+0x9d): first defined here
Bug reassigned from package 'src:pcb-rnd' to 'libgenht1-dev'.
No longer marked as found in versions pcb-rnd/3.1.3-1.
No longer marked as fixed in versions genht/1.1.3-1.
> affects 1066414 + src:pcb-rnd
Bug #1066414 {Done: Bdale Garbee } [libgenht1-dev] pcb-rnd: 
FTBFS: ./util/bxl2txt/./util/bxl2txt/txt2bxl.c:43: multiple definition of 
`main'; /usr/lib/libgenht.a(mainsi.o):(.text+0x9d): first defined here
Added indication that 1066414 affects src:pcb-rnd
> found 1066414 1.1.2-2
Bug #1066414 {Done: Bdale Garbee } [libgenht1-dev] pcb-rnd: 
FTBFS: ./util/bxl2txt/./util/bxl2txt/txt2bxl.c:43: multiple definition of 
`main'; /usr/lib/libgenht.a(mainsi.o):(.text+0x9d): first defined here
Marked as found in versions genht/1.1.2-2 and reopened.
> fixed 1066414 1.1.3-1
Bug #1066414 [libgenht1-dev] pcb-rnd: FTBFS: 
./util/bxl2txt/./util/bxl2txt/txt2bxl.c:43: multiple definition of `main'; 
/usr/lib/libgenht.a(mainsi.o):(.text+0x9d): first defined here
Marked as fixed in versions genht/1.1.3-1.
>
End of message, stopping processing here.

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

Bug#1066200: marked as done (libdbd-sybase-perl: FTBFS: Sybase.xs:83:32: error: implicit declaration of function ‘syb_ping’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 07:35:06 +
with message-id 
and subject line Bug#1066200: fixed in libdbd-sybase-perl 1.24-1
has caused the Debian Bug report #1066200,
regarding libdbd-sybase-perl: FTBFS: Sybase.xs:83:32: error: implicit 
declaration of function ‘syb_ping’ [-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.)


-- 
1066200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdbd-sybase-perl
Version: 1.14-1.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):
> x86_64-linux-gnu-gcc -c  -I/usr/include -DSYB_LP64 -DNO_BLK=1 
> -I/usr/lib/x86_64-linux-gnu/perl5/5.38/auto/DBI -D_REENTRANT -D_GNU_SOURCE 
> -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -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   
> -DVERSION=\"1.14\" -DXS_VERSION=\"1.14\" -fPIC 
> "-I/usr/lib/x86_64-linux-gnu/perl/5.38/CORE"   Sybase.c
> In file included from /usr/lib/x86_64-linux-gnu/perl/5.38/CORE/perl.h:6227,
>  from 
> /usr/lib/x86_64-linux-gnu/perl5/5.38/auto/DBI/DBIXS.h:23,
>  from Sybase.h:16,
>  from Sybase.xs:14:
> Sybase.xs: In function ‘XS_DBD__Sybase__db_ping’:
> Sybase.xs:83:32: error: implicit declaration of function ‘syb_ping’ 
> [-Werror=implicit-function-declaration]
>83 | ST(0) = sv_2mortal(newSViv(syb_ping(dbh, imp_dbh)));
>   |^~~~
> /usr/lib/x86_64-linux-gnu/perl/5.38/CORE/embed.h:612:71: note: in definition 
> of macro ‘sv_2mortal’
>   612 | # define sv_2mortal(a)  Perl_sv_2mortal(aTHX_ 
> a)
>   |   
> ^
> Sybase.xs:83:24: note: in expansion of macro ‘newSViv’
>83 | ST(0) = sv_2mortal(newSViv(syb_ping(dbh, imp_dbh)));
>   |^~~
> Sybase.xs: In function ‘XS_DBD__Sybase__st_cancel’:
> Sybase.xs:95:13: error: implicit declaration of function ‘syb_st_cancel’ 
> [-Werror=implicit-function-declaration]
>95 | ST(0) = syb_st_cancel(sth, imp_sth) ? _sv_yes : _sv_no;
>   | ^
> ./Sybase.xsi: In function ‘XS_DBD__Sybase__db_selectrow_arrayref’:
> ./Sybase.xsi:234:9: warning: ‘Perl_dowantarray’ is deprecated 
> [-Wdeprecated-declarations]
>   234 | if (GIMME == G_SCALAR)
>   | ^~
> In file included from /usr/lib/x86_64-linux-gnu/perl/5.38/CORE/perl.h:6188:
> /usr/lib/x86_64-linux-gnu/perl/5.38/CORE/proto.h:1019:1: note: declared here
>  1019 | Perl_dowantarray(pTHX)
>   | ^~~~
> ./Sybase.xsi:240:9: warning: ‘Perl_dowantarray’ is deprecated 
> [-Wdeprecated-declarations]
>   240 | if (GIMME == G_SCALAR)
>   | ^~
> /usr/lib/x86_64-linux-gnu/perl/5.38/CORE/proto.h:1019:1: note: declared here
>  1019 | Perl_dowantarray(pTHX)
>   | ^~~~
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:350: Sybase.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/libdbd-sybase-perl_1.14-1.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: libdbd-sybase-perl
Source-Version: 1.24-1

Bug#1065789: marked as done (libdbd-sybase-perl: FTBFS on arm{el,hf}: Sybase.xs:83:32: error: implicit declaration of function ‘syb_ping’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 07:35:06 +
with message-id 
and subject line Bug#1065789: fixed in libdbd-sybase-perl 1.24-1
has caused the Debian Bug report #1065789,
regarding libdbd-sybase-perl: FTBFS on arm{el,hf}: Sybase.xs:83:32: error: 
implicit declaration of function ‘syb_ping’ 
[-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.)


-- 
1065789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdbd-sybase-perl
Version: 1.14-1.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=libdbd-sybase-perl=armhf=1.14-1.1%2Bb2=1709894119=0

arm-linux-gnueabihf-gcc -c  -I/usr/include -DNO_BLK=1 
-I/usr/lib/arm-linux-gnueabihf/perl5/5.38/auto/DBI -D_REENTRANT -D_GNU_SOURCE 
-DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -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   -DVERSION=\"1.14\" 
-DXS_VERSION=\"1.14\" -fPIC "-I/usr/lib/arm-linux-gnueabihf/perl/5.38/CORE"   
Sybase.c
In file included from /usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/perl.h:6227,
 from 
/usr/lib/arm-linux-gnueabihf/perl5/5.38/auto/DBI/DBIXS.h:23,
 from Sybase.h:16,
 from Sybase.xs:14:
Sybase.xs: In function ‘XS_DBD__Sybase__db_ping’:
Sybase.xs:83:32: error: implicit declaration of function ‘syb_ping’ 
[-Werror=implicit-function-declaration]
   83 | ST(0) = sv_2mortal(newSViv(syb_ping(dbh, imp_dbh)));
  |^~~~
/usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/embed.h:612:71: note: in definition 
of macro ‘sv_2mortal’
  612 | # define sv_2mortal(a)  Perl_sv_2mortal(aTHX_ a)
  |   ^
Sybase.xs:83:24: note: in expansion of macro ‘newSViv’
   83 | ST(0) = sv_2mortal(newSViv(syb_ping(dbh, imp_dbh)));
  |^~~
Sybase.xs: In function ‘XS_DBD__Sybase__st_cancel’:
Sybase.xs:95:13: error: implicit declaration of function ‘syb_st_cancel’ 
[-Werror=implicit-function-declaration]
   95 | ST(0) = syb_st_cancel(sth, imp_sth) ? _sv_yes : _sv_no;
  | ^
./Sybase.xsi: In function ‘XS_DBD__Sybase__db_selectrow_arrayref’:
./Sybase.xsi:234:9: warning: ‘Perl_dowantarray’ is deprecated 
[-Wdeprecated-declarations]
  234 | if (GIMME == G_SCALAR)
  | ^~
In file included from /usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/perl.h:6188:
/usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/proto.h:1019:1: note: declared here
 1019 | Perl_dowantarray(pTHX)
  | ^~~~
./Sybase.xsi:240:9: warning: ‘Perl_dowantarray’ is deprecated 
[-Wdeprecated-declarations]
  240 | if (GIMME == G_SCALAR)
  | ^~
/usr/lib/arm-linux-gnueabihf/perl/5.38/CORE/proto.h:1019:1: note: declared here
 1019 | Perl_dowantarray(pTHX)
  | ^~~~
cc1: some warnings being treated as errors
make[1]: *** [Makefile:350: Sybase.o] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libdbd-sybase-perl
Source-Version: 1.24-1
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
libdbd-sybase-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: SHA256

Format: 1.8
Date: Thu, 11 Apr 2024 08:03:20 +0200
Source: libdbd-sybase-perl
Built-For-Profiles: noudeb
Architecture: source
Version: 1.24-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Gianfranco 

Bug#1067141: kcemu: FTBFS with -Werror=implicit-function-declaration

[John Paul Adrian Glaubitz]

Hello Zixing,

On Wed, 2024-04-10 at 17:34 -0600, Zixing Liu wrote:
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * debian/patches/add-missing-includes.patch: Add missing includes.
> Closes LP: #2060887.

The issue has already been fixed upstream. I am waiting for upstream
to make a new release as this would also fix #970666 [1].

Adrian

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970666

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#1066248: marked as done (librnd: FTBFS: ../src/librnd/plugins/hid_lesstif/main.c:261:25: error: implicit declaration of function ‘lesstif_attr_sub_update_hidlib’ [-Werror=implicit-function-declara

[Debian Bug Tracking System]

Your message dated Thu, 11 Apr 2024 07:04:45 +
with message-id 
and subject line Bug#1066248: fixed in librnd 4.2.0-1
has caused the Debian Bug report #1066248,
regarding librnd: FTBFS: ../src/librnd/plugins/hid_lesstif/main.c:261:25: 
error: implicit declaration of function ‘lesstif_attr_sub_update_hidlib’ 
[-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.)


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

Hi,

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

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

Relevant part (hopefully):
> gcc -c  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -D_LARGE_FILE_SOURCE=1 -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -fPIC -O3 -DNDEBUG -I. -I.. -I../src_3rd -I../src -I../src_3rd/liblihata
> -o ../src/librnd/plugins/hid_lesstif/ltf_stdarg.o 
> ../src/librnd/plugins/hid_lesstif/ltf_stdarg.c
> ../src/librnd/plugins/hid_lesstif/main.c: In function 
> ‘ltf_update_topwin_dock_hidlibs’:
> ../src/librnd/plugins/hid_lesstif/main.c:261:25: error: implicit declaration 
> of function ‘lesstif_attr_sub_update_hidlib’ 
> [-Werror=implicit-function-declaration]
>   261 | 
> lesstif_attr_sub_update_hidlib(docked->hid_ctx, new_dsg);
>   | ^~
> ../src/librnd/plugins/hid_lesstif/main.c: In function ‘ltf_mod_key’:
> ../src/librnd/plugins/hid_lesstif/main.c:469:9: warning: ‘XKeycodeToKeysym’ 
> is deprecated [-Wdeprecated-declarations]
>   469 | switch (XKeycodeToKeysym(display, e->keycode, 0)) {
>   | ^~
> In file included from /usr/include/X11/Intrinsic.h:53,
>  from ../src/librnd/plugins/hid_lesstif/xincludes.h:10,
>  from ../src/librnd/plugins/hid_lesstif/main.c:1:
> /usr/include/X11/Xlib.h:1687:15: note: declared here
>  1687 | extern KeySym XKeycodeToKeysym(
>   |   ^~~~
> ../src/librnd/plugins/hid_lesstif/main.c: In function ‘rnd_ltf_draw_pixmap_’:
> ../src/librnd/plugins/hid_lesstif/main.c:775:78: warning: passing argument 2 
> of ‘XRenderCreatePicture’ makes integer from pointer without a cast 
> [-Wint-conversion]
>   775 | lpm->p_img_scaled = 
> XRenderCreatePicture(display, lpm->img_scaled, 
> XRenderFindVisualFormat(display, DefaultVisual(display, screen)), 0, 0);
>   |   
> ~~~^~~~
>   |   
>|
>   |   
>XImage *
> In file included from ../src/librnd/plugins/hid_lesstif/xincludes.h:39,
>  from ../src/librnd/plugins/hid_lesstif/ltf_stdarg.h:1,
>  from ../src/librnd/plugins/hid_lesstif/main.c:37:
> /usr/include/X11/extensions/Xrender.h:242:57: note: expected ‘Drawable’ {aka 
> ‘long unsigned int’} but argument is of type ‘XImage *’
>   242 |   Drawable  drawable,
>   |   ~~^~~~
> gcc -c  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -D_LARGE_FILE_SOURCE=1 -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -fPIC -O3 -DNDEBUG -I. -I.. -I../src_3rd -I../src -I../src_3rd/liblihata
> -o ../src/librnd/plugins/hid_lesstif/wt_colorbtn.o 
> ../src/librnd/plugins/hid_lesstif/wt_colorbtn.c
> ../src/librnd/plugins/hid_lesstif/main.c: In function ‘lesstif_do_exit’:
> ../src/librnd/plugins/hid_lesstif/main.c:1626:9: error: implicit declaration 
> of function ‘lesstif_attr_dlg_free_all’ 
> [-Werror=implicit-function-declaration]
>  1626 | lesstif_attr_dlg_free_all();
>   | ^
>