Processed (with 1 error): Duplicate bug #1069125

[Debian Bug Tracking System]

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

> forcemerge 1063497 1069125
Bug #1063497 [src:zfs-linux] zfs-dkms: Data loss bug in version in bookworm
Unable to merge bugs because:
package of #1069125 is 'zfs-dkms' not 'src:zfs-linux'
Failed to forcibly merge 1063497: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: found 1067701 in 1:26.2.1+dfsg-1

[Debian Bug Tracking System]

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

> found 1067701 1:26.2.1+dfsg-1
Bug #1067701 {Done: Sergei Golovan } [src:erlang] FTBFS: 
_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64
Marked as found in versions erlang/1:26.2.1+dfsg-1 and reopened.
> thanks
Stopping processing here.

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

Bug#1064559: Forwarded upstream (+ same ftbfs in Ubuntu)

[Bryce Harrington]

Ubuntu is seeing the same failures after its own rebuilds of the package
in Ubuntu noble, also on ppc64el only.  I investigated if it was a known
issue in pdbq or valgrind but did not find convincing matches.  I'm also
not certain if this is a single issue, or multiple.  There are also some
"Invalid opcode" errors from valgrind which I wonder might be a separate
problem.  In Ubuntu I'm going to test if disabling TEST5 is sufficient.

Ubuntu bug:  https://bugs.launchpad.net/ubuntu/+source/pmdk/+bug/2061913

Upstream bug:  https://github.com/pmem/pmdk/issues/5635

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

[pham...@bluewin.ch]

Extra information :
It is stable when you initialize the disk in MBR/MS-DOS format, but only with a 
USB A to USB C cable, if you use a USB c to USB-C cable the problems persist.

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

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 21:50:47 +
with message-id 
and subject line Bug#1067596: fixed in xf86-input-multitouch 1.0~rc3-2.1
has caused the Debian Bug report #1067596,
regarding FTBFS: error: ‘const struct input_event’ has no member named ‘time’
to be marked as done.

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

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


-- 
1067596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xf86-input-multitouch
Version: 1.0~rc3-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=xf86-input-
multitouch=armel=1.0%7Erc3-2%2Bb2=1711272573=0

src/hwstate.c: In function ‘finish_packet’:
src/hwstate.c:43:24: error: ‘const struct input_event’ has no member named
‘time’
   43 | s->evtime = syn->time.tv_usec / ms + syn->time.tv_sec * ms;
  |^~
src/hwstate.c:43:49: error: ‘const struct input_event’ has no member named
‘time’
   43 | s->evtime = syn->time.tv_usec / ms + syn->time.tv_sec * ms;
  | ^~



It also has multiple "warning: implicit declaration of function" which are not
errors because the package ignores compiler flags from dh_auto_build (which is
also a bug, not sure if RC or not).


-- 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: xf86-input-multitouch
Source-Version: 1.0~rc3-2.1
Done: Gianfranco Costamagna 

We believe that the bug you reported is fixed in the latest version of
xf86-input-multitouch, 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.
Gianfranco Costamagna  (supplier of updated 
xf86-input-multitouch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 16 Apr 2024 23:27:03 +0200
Source: xf86-input-multitouch
Built-For-Profiles: noudeb
Architecture: source
Version: 1.0~rc3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Gianfranco Costamagna 
Closes: 1067596
Launchpad-Bugs-Fixed: 2061591
Changes:
 xf86-input-multitouch (1.0~rc3-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   [ Gianfranco Costamagna ]
   * Drop libmtdev1 runtime dependency
 .
   [ Benjamin Drung ]
   * debian/rules: Pass CPPFLAGS and CFLAGS to make call
   * Port usage of struct input_event to input_event_*
 (Closes: #1067596, LP: #2061591)
   * Include headers to fix implicit function declaration
Checksums-Sha1:
 55c6cef99b8212238b83c36d63f9377430219552 2083 
xf86-input-multitouch_1.0~rc3-2.1.dsc
 939e52680d116e4c609a3e3558c2e88100aa2f5a 12628 
xf86-input-multitouch_1.0~rc3-2.1.debian.tar.xz
 5a98eccb0caa4891666cca63f721f9f93759d618 10393 
xf86-input-multitouch_1.0~rc3-2.1_source.buildinfo
Checksums-Sha256:
 6e2f022630563c82ae69d13404ec81a77d659b9af0dc6afa8441eff2d741fb5a 2083 
xf86-input-multitouch_1.0~rc3-2.1.dsc
 5a068c00fe0c322533628f9e84a0b6e00e59001c3c4bdb29310c398e337efc51 12628 
xf86-input-multitouch_1.0~rc3-2.1.debian.tar.xz
 246ae0eff853a922144ef1a3c82e89a008413db4e252a44c8dbf640a9964cc49 10393 
xf86-input-multitouch_1.0~rc3-2.1_source.buildinfo
Files:
 64de169715bef79d1345717be4414e85 2083 x11 optional 
xf86-input-multitouch_1.0~rc3-2.1.dsc
 0adda7c4a1caf3218d52b92051eeb6a7 12628 x11 optional 
xf86-input-multitouch_1.0~rc3-2.1.debian.tar.xz
 a076ca18db766de86451563ac728c2ad 10393 x11 optional 
xf86-input-multitouch_1.0~rc3-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmYe8XwACgkQ808JdE6f

Bug#1066547: marked as done (xf86-input-mtrack: FTBFS: src/gestures.c:763:13: error: implicit declaration of function ‘mtdev_empty’; did you mean ‘mtdev_get’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 21:50:39 +
with message-id 
and subject line Bug#1066547: fixed in xf86-input-mtrack 0.3.1-1.1
has caused the Debian Bug report #1066547,
regarding xf86-input-mtrack: FTBFS: src/gestures.c:763:13: error: implicit 
declaration of function ‘mtdev_empty’; did you mean ‘mtdev_get’? 
[-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.)


-- 
1066547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xf86-input-mtrack
Version: 0.3.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 -DHAVE_CONFIG_H -I.  -I./include/ -I/usr/include/xorg 
> -I/usr/include/pixman-1  -I/usr/include/xorg -fvisibility=hidden 
> -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -D_FORTIFY_SOURCE=2 -c -o 
> src/mtrack_test-gestures.o `test -f 'src/gestures.c' || echo 
> './'`src/gestures.c
> src/gestures.c: In function ‘gestures_sleep’:
> src/gestures.c:763:13: error: implicit declaration of function ‘mtdev_empty’; 
> did you mean ‘mtdev_get’? [-Werror=implicit-function-declaration]
>   763 | if (mtdev_empty(>dev)) {
>   | ^~~
>   | mtdev_get
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:663: src/mtrack_test-gestures.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/xf86-input-mtrack_0.3.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: xf86-input-mtrack
Source-Version: 0.3.1-1.1
Done: Gianfranco Costamagna 

We believe that the bug you reported is fixed in the latest version of
xf86-input-mtrack, 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.
Gianfranco Costamagna  (supplier of updated 
xf86-input-mtrack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 16 Apr 2024 23:32:48 +0200
Source: xf86-input-mtrack
Built-For-Profiles: noudeb
Architecture: source
Version: 0.3.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Gianfranco Costamagna 
Closes: 1066547
Changes:
 xf86-input-mtrack (0.3.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Add patch to fix implicit-function-declaration build failures
 (Closes: #1066547)
Checksums-Sha1:
 b373b79bfe038da6044f369a96edc8917ed039b7 1941 xf86-input-mtrack_0.3.1-1.1.dsc
 379f735c5c00e426a053a84a01bffa3156a85c50 12868 
xf86-input-mtrack_0.3.1-1.1.debian.tar.xz
 f4894e6e383b00e914f7265427ff66d7ee1495c8 10369 
xf86-input-mtrack_0.3.1-1.1_source.buildinfo
Checksums-Sha256:
 d085b85310ff19da8bfdd4f0be28d6a6a98ab460ab7a985ed6fd966fb21bfbb5 1941 
xf86-input-mtrack_0.3.1-1.1.dsc
 

Bug#1067596: FTBFS: error: ‘const struct input_event’ has no member named ‘time’

[Gianfranco Costamagna]

Control: tags 1067596 + patch
Control: tags 1067596 + pending

Dear maintainer,

I've prepared an NMU for xf86-input-multitouch (versioned as 1.0~rc3-2.1) and
uploaded it.

diff -Nru xf86-input-multitouch-1.0~rc3/debian/changelog 
xf86-input-multitouch-1.0~rc3/debian/changelog
--- xf86-input-multitouch-1.0~rc3/debian/changelog  2018-03-12 
06:38:28.0 +0100
+++ xf86-input-multitouch-1.0~rc3/debian/changelog  2024-04-16 
23:27:03.0 +0200
@@ -1,3 +1,17 @@
+xf86-input-multitouch (1.0~rc3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  [ Gianfranco Costamagna ]
+  * Drop libmtdev1 runtime dependency
+
+  [ Benjamin Drung ]
+  * debian/rules: Pass CPPFLAGS and CFLAGS to make call
+  * Port usage of struct input_event to input_event_*
+(Closes: #1067596, LP: #2061591)
+  * Include headers to fix implicit function declaration
+
+ -- Gianfranco Costamagna   Tue, 16 Apr 2024 
23:27:03 +0200
+
 xf86-input-multitouch (1.0~rc3-2) unstable; urgency=medium

   [ Helmut Grohne ]
diff -Nru xf86-input-multitouch-1.0~rc3/debian/control 
xf86-input-multitouch-1.0~rc3/debian/control
--- xf86-input-multitouch-1.0~rc3/debian/control2018-03-12 
06:38:28.0 +0100
+++ xf86-input-multitouch-1.0~rc3/debian/control2024-04-16 
23:27:03.0 +0200
@@ -15,8 +15,7 @@
 Architecture: linux-any
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- ${xinpdriver:Depends},
- libmtdev1
+ ${xinpdriver:Depends}
 Provides: ${xinpdriver:Provides}
 Description: Multitouch X input driver
  This X input driver provides gestures support for multitouch touchpads,
diff -Nru 
xf86-input-multitouch-1.0~rc3/debian/patches/Include-headers-to-fix-implicit-function-declaration.patch
 
xf86-input-multitouch-1.0~rc3/debian/patches/Include-headers-to-fix-implicit-function-declaration.patch
--- 
xf86-input-multitouch-1.0~rc3/debian/patches/Include-headers-to-fix-implicit-function-declaration.patch
 1970-01-01 01:00:00.0 +0100
+++ 
xf86-input-multitouch-1.0~rc3/debian/patches/Include-headers-to-fix-implicit-function-declaration.patch
 2024-04-16 23:27:03.0 +0200
@@ -0,0 +1,46 @@
+From: Benjamin Drung 
+Date: Mon, 15 Apr 2024 20:11:11 +0200
+Subject: Include headers to fix implicit function declaration
+
+---
+ driver/multitouch.c | 1 +
+ src/mtouch.c| 1 +
+ src/test.c  | 1 +
+ 3 files changed, 3 insertions(+)
+
+diff --git a/driver/multitouch.c b/driver/multitouch.c
+index a083adc..0c4615c 100644
+--- a/driver/multitouch.c
 b/driver/multitouch.c
+@@ -22,6 +22,7 @@
+ #include "gestures.h"
+
+ #if GET_ABI_MAJOR(ABI_XINPUT_VERSION) >= 7
++#include 
+ #include 
+ #include 
+ #endif
+diff --git a/src/mtouch.c b/src/mtouch.c
+index a6b96b8..335c61e 100644
+--- a/src/mtouch.c
 b/src/mtouch.c
+@@ -20,6 +20,7 @@
+  **/
+
+ #include "mtouch.h"
++#include 
+
+ static const int use_grab = 0;
+
+diff --git a/src/test.c b/src/test.c
+index 1b67986..77b723e 100644
+--- a/src/test.c
 b/src/test.c
+@@ -22,6 +22,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+
+ static void loop_device(int fd)
+ {
diff -Nru 
xf86-input-multitouch-1.0~rc3/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
 
xf86-input-multitouch-1.0~rc3/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
--- 
xf86-input-multitouch-1.0~rc3/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
 1970-01-01 01:00:00.0 +0100
+++ 
xf86-input-multitouch-1.0~rc3/debian/patches/Port-usage-of-struct-input_event-to-input_event_.patch
 2024-04-16 23:27:03.0 +0200
@@ -0,0 +1,40 @@
+From: Benjamin Drung 
+Date: Mon, 15 Apr 2024 19:56:58 +0200
+Subject: Port usage of struct input_event to input_event_*
+MIME-Version: 1.0
+Content-Type: text/plain; charset="utf-8"
+Content-Transfer-Encoding: 8bit
+
+It fails to build on armhf:
+
+```
+src/hwstate.c: In function ‘finish_packet’:
+src/hwstate.c:43:24: error: ‘const struct input_event’ has no member named
+‘time’
+   43 | s->evtime = syn->time.tv_usec / ms + syn->time.tv_sec * ms;
+  | ^~
+src/hwstate.c:43:49: error: ‘const struct input_event’ has no member named
+‘time’
+   43 | s->evtime = syn->time.tv_usec / ms + syn->time.tv_sec * ms;
+  | ^~
+```
+
+Closes: #1067596
+LP: #2061591
+---
+ src/hwstate.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/hwstate.c b/src/hwstate.c
+index 076efa1..ab2ac48 100644
+--- a/src/hwstate.c
 b/src/hwstate.c
+@@ -40,7 +40,7 @@ static void finish_packet(struct HWState *s, const struct 
Capabilities *caps,
+   if (!caps->has_abs[MTDEV_WIDTH_MINOR])
+   s->data[i].width_minor = s->data[i].width_major;
+   }
+-  s->evtime = syn->time.tv_usec / ms + syn->time.tv_sec * ms;
++  s->evtime = syn->input_event_usec / ms + syn->input_event_sec * ms;
+ }
+
+ static int read_event(struct 

Processed: Re: FTBFS: error: ‘const struct input_event’ has no member named ‘time’

[Debian Bug Tracking System]

Processing control commands:

> tags 1067596 + patch
Bug #1067596 [src:xf86-input-multitouch] FTBFS: error: ‘const struct 
input_event’ has no member named ‘time’
Added tag(s) patch.
> tags 1067596 + pending
Bug #1067596 [src:xf86-input-multitouch] FTBFS: error: ‘const struct 
input_event’ has no member named ‘time’
Added tag(s) pending.

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

Bug#895823: closing 895823

[Noah Meyerhans]

close 895823 
thanks

This was actually fixed with the removal of dovecot-common's postrm script with
version 1:2.2.32-2 way back in 2017.  However, that change never made it to the
Debian 9 (stretch) branch, which I suspect is what led to this issue being
encountered there.

In any case, as we are no longer updating the stretch branch, and haven't been
in some time, there's nothing more we can or should do on this issue, and I am
closing it.

noah

Processed: closing 895823

[Debian Bug Tracking System]

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

> close 895823
Bug #895823 [dovecot-core] cannot purge dovecot-common
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1066547: xf86-input-mtrack: FTBFS: src/gestures.c:763:13: error: implicit declaration of function ‘mtdev_empty’; did you mean ‘mtdev_get’? [-Werror=implicit-function-declaration]

[Gianfranco Costamagna]

updated diff:

debdiff xf86-input-mtrack_0.3.1-1.dsc xf86-input-mtrack_0.3.1-1.1.dsc
diff -Nru xf86-input-mtrack-0.3.1/debian/changelog 
xf86-input-mtrack-0.3.1/debian/changelog
--- xf86-input-mtrack-0.3.1/debian/changelog2015-06-02 07:09:33.0 
+0200
+++ xf86-input-mtrack-0.3.1/debian/changelog2024-04-16 23:32:48.0 
+0200
@@ -1,3 +1,11 @@
+xf86-input-mtrack (0.3.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Add patch to fix implicit-function-declaration build failures
+(Closes: #1066547)
+
+ -- Gianfranco Costamagna   Tue, 16 Apr 2024 
23:32:48 +0200
+
 xf86-input-mtrack (0.3.1-1) unstable; urgency=medium
 
   * Upload to unstable.

diff -Nru 
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
 
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
--- 
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
 1970-01-01 01:00:00.0 +0100
+++ 
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
 2024-04-16 23:32:48.0 +0200
@@ -0,0 +1,24 @@
+Description: Add patch to fix missing includes
+Author: Gianfranco Costamagna 
+Last-Update: 2024-04-16
+
+--- xf86-input-mtrack-0.3.1.orig/include/common.h
 xf86-input-mtrack-0.3.1/include/common.h
+@@ -33,6 +33,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+
+--- xf86-input-mtrack-0.3.1.orig/tools/mtrack-test.c
 xf86-input-mtrack-0.3.1/tools/mtrack-test.c
+@@ -23,6 +23,7 @@
+ #include "mtouch.h"
+ #include 
+ #include 
++#include 
+
+ void xf86Msg(int type, const char *format, ...)
+ {
diff -Nru xf86-input-mtrack-0.3.1/debian/patches/series 
xf86-input-mtrack-0.3.1/debian/patches/series
--- xf86-input-mtrack-0.3.1/debian/patches/series   2012-07-05 
09:57:49.0 +0200
+++ xf86-input-mtrack-0.3.1/debian/patches/series   2024-04-16 
23:32:48.0 +0200
@@ -1,3 +1,4 @@
 #drop-mtrack-test
 #aa
 upsteam-commit
+missing-includes-implicit-function-declaration-fix.patch


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Re: xf86-input-mtrack: FTBFS: src/gestures.c:763:13: error: implicit declaration of function ‘mtdev_empty’; did you mean ‘mtdev_get’? [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #1066547 [src:xf86-input-mtrack] xf86-input-mtrack: FTBFS: 
src/gestures.c:763:13: error: implicit declaration of function ‘mtdev_empty’; 
did you mean ‘mtdev_get’? [-Werror=implicit-function-declaration]
Added tag(s) pending and patch.

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

Bug#1066547: xf86-input-mtrack: FTBFS: src/gestures.c:763:13: error: implicit declaration of function ‘mtdev_empty’; did you mean ‘mtdev_get’? [-Werror=implicit-function-declaration]

[Gianfranco Costamagna]

control: tags -1 patch pending


Dear maintainer,

I've prepared an NMU for xf86-input-mtrack (versioned as 0.3.1-1.1) and
uploaded it.



diff -Nru xf86-input-mtrack-0.3.1/debian/changelog 
xf86-input-mtrack-0.3.1/debian/changelog
--- xf86-input-mtrack-0.3.1/debian/changelog2024-04-01 10:36:37.0 
+0200
+++ xf86-input-mtrack-0.3.1/debian/changelog2024-04-16 23:32:48.0 
+0200
@@ -1,3 +1,10 @@
+xf86-input-mtrack (0.3.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Add patch to fix implicit-function-declaration build failures (Closes: 
#1066547)
+
+ -- Gianfranco Costamagna   Tue, 16 Apr 2024 
23:32:48 +0200
+
 xf86-input-mtrack (0.3.1-1build5) noble; urgency=medium

   * No-change rebuild for CVE-2024-3094
diff -Nru 
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
 
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
--- 
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
 1970-01-01 01:00:00.0 +0100
+++ 
xf86-input-mtrack-0.3.1/debian/patches/missing-includes-implicit-function-declaration-fix.patch
 2024-04-16 23:32:48.0 +0200
@@ -0,0 +1,24 @@
+Description: Add patch to fix missing includes
+Author: Gianfranco Costamagna 
+Last-Update: 2024-04-16
+
+--- xf86-input-mtrack-0.3.1.orig/include/common.h
 xf86-input-mtrack-0.3.1/include/common.h
+@@ -33,6 +33,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+
+--- xf86-input-mtrack-0.3.1.orig/tools/mtrack-test.c
 xf86-input-mtrack-0.3.1/tools/mtrack-test.c
+@@ -23,6 +23,7 @@
+ #include "mtouch.h"
+ #include 
+ #include 
++#include 
+
+ void xf86Msg(int type, const char *format, ...)
+ {
diff -Nru xf86-input-mtrack-0.3.1/debian/patches/series 
xf86-input-mtrack-0.3.1/debian/patches/series
--- xf86-input-mtrack-0.3.1/debian/patches/series   2012-07-05 
09:57:49.0 +0200
+++ xf86-input-mtrack-0.3.1/debian/patches/series   2024-04-16 
23:32:48.0 +0200
@@ -1,3 +1,4 @@
 #drop-mtrack-test
 #aa
 upsteam-commit
+missing-includes-implicit-function-declaration-fix.patch

Bug#1066706: marked as done (tk-html3: FTBFS: ./src/htmltcl.c:503:9: error: implicit declaration of function ‘usleep’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 20:44:45 +
with message-id 
and subject line Bug#1066706: fixed in tk-html3 3.0~fossil20110109-9
has caused the Debian Bug report #1066706,
regarding tk-html3: FTBFS: ./src/htmltcl.c:503:9: error: implicit declaration 
of function ‘usleep’ [-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.)


-- 
1066706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tk-html3
Version: 3.0~fossil20110109-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

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

Relevant part (hopefully):
> gcc -pipe -DPACKAGE_NAME=\"Tkhtml\" -DPACKAGE_TARNAME=\"tkhtml\" 
> -DPACKAGE_VERSION=\"3.0\" -DPACKAGE_STRING=\"Tkhtml\ 3.0\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DHAVE_STDIO_H=1 
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 
> -DSTDC_HEADERS=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_THREAD_ALLOC=1 
> -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 -D_LARGEFILE64_SOURCE=1 
> -DTCL_WIDE_INT_IS_LONG=1 -DUSE_TCL_STUBS=1 -DUSE_TK_STUBS=1  
> -I"/usr/include/tcl8.6" -I"/usr/include/tcl8.6"   -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 -O2 
> -fomit-frame-pointer -Wall -Wno-implicit-int -fPIC -c -I. -I./src `echo 
> ./src/swproc.c` -o swproc.o
> ./src/htmltcl.c: In function ‘runLayoutEngine’:
> ./src/htmltcl.c:446:17: warning: variable ‘pD’ set but not used 
> [-Wunused-but-set-variable]
>   446 | HtmlDamage *pD;
>   | ^~
> ./src/htmltcl.c: In function ‘callbackHandler’:
> ./src/htmltcl.c:503:9: error: implicit declaration of function ‘usleep’ 
> [-Werror=implicit-function-declaration]
>   503 | usleep( 2000 );
>   | ^~
> ./src/htmltcl.c: In function ‘viewCommon’:
> ./src/htmltcl.c:1844:14: warning: variable ‘pScrollCommand’ set but not used 
> [-Wunused-but-set-variable]
>  1844 | Tcl_Obj *pScrollCommand;
>   |  ^~
> ./src/swproc.c:7:19: warning: ‘rcsid’ defined but not used 
> [-Wunused-const-variable=]
> 7 | static const char rcsid[] = "$Id: swproc.c,v 1.6 2006/06/10 12:38:38 
> danielk1977 Exp $";
>   |   ^
> ./src/htmltcl.c: At top level:
> ./src/htmltcl.c:33:19: warning: ‘rcsid’ defined but not used 
> [-Wunused-const-variable=]
>33 | static char const rcsid[] = "@(#) $Id: htmltcl.c,v 1.207 2008/01/16 
> 06:29:27 danielk1977 Exp $";
>   |   ^
> ./src/htmltree.c:39:19: warning: ‘rcsid’ defined but not used 
> [-Wunused-const-variable=]
>39 | static const char rcsid[] = "$Id: htmltree.c,v 1.161 2008/02/14 
> 08:39:14 danielk1977 Exp $";
>   |   ^
> gcc -pipe -DPACKAGE_NAME=\"Tkhtml\" -DPACKAGE_TARNAME=\"tkhtml\" 
> -DPACKAGE_VERSION=\"3.0\" -DPACKAGE_STRING=\"Tkhtml\ 3.0\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DHAVE_STDIO_H=1 
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 
> -DSTDC_HEADERS=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_THREAD_ALLOC=1 
> -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 -D_LARGEFILE64_SOURCE=1 
> -DTCL_WIDE_INT_IS_LONG=1 -DUSE_TCL_STUBS=1 -DUSE_TK_STUBS=1  
> -I"/usr/include/tcl8.6" -I"/usr/include/tcl8.6"   -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 -O2 
> -fomit-frame-pointer -Wall -Wno-implicit-int -fPIC -c -I. -I./src `echo 
> ./src/restrack.c` -o restrack.o
> ./src/restrack.c:64:19: warning: ‘rcsid’ defined but not used 
> [-Wunused-const-variable=]
>64 | static const char rcsid[] = "$Id: restrack.c,v 1.13 2007/12/12 
> 04:50:29 danielk1977 Exp $";
>   |   ^
> gcc -pipe -DPACKAGE_NAME=\"Tkhtml\" 

Bug#1069119: marked as done (gpsshogi: EPL missing from debian/copyright)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 20:37:25 +
with message-id 
and subject line Bug#1069119: fixed in gpsshogi 0.7.0-3.2
has caused the Debian Bug report #1069119,
regarding gpsshogi: EPL missing from debian/copyright
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.)


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

Source: gpsshogi
Version: 0.7.0-3.1
Severity: serious

The EPL-1 that is mentioned in d/copyright is not included in that file with 
the complete text.
A copy is included in debian/epl-v10.txt. Please include it in d/copyright.
--- End Message ---
--- Begin Message ---
Source: gpsshogi
Source-Version: 0.7.0-3.2
Done: Bastian Germann 

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

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

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated gpsshogi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Apr 2024 18:56:27 +
Source: gpsshogi
Architecture: source
Version: 0.7.0-3.2
Distribution: unstable
Urgency: medium
Maintainer: Yann Dirson 
Changed-By: Bastian Germann 
Closes: 1069119
Changes:
 gpsshogi (0.7.0-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/copyright: Convert to standardized format
   * d/copyright: Include EPL text (Closes: #1069119)
Checksums-Sha1:
 dd9a7ac782f8cddf80e4606669231d8c610185f5 2060 gpsshogi_0.7.0-3.2.dsc
 8812f627e7eddb3c5bd0519bfaebd6e72c6080d8 19228 gpsshogi_0.7.0-3.2.debian.tar.xz
 b27ecd2a5cf42e4b11063b9d58c45697ef11ee3a 18186 
gpsshogi_0.7.0-3.2_source.buildinfo
Checksums-Sha256:
 12abd9591a90a7b360637f7a5614518e5465b1cdbb6c75855ec118e18befa29b 2060 
gpsshogi_0.7.0-3.2.dsc
 d12e81e6ace920e990623e68151062ccb0cd15c612f53586a1de8f7c595373f5 19228 
gpsshogi_0.7.0-3.2.debian.tar.xz
 bffefa6fe20475049e10a76fdefb7f7e481e2a368ce7e8112c513b2c76b02521 18186 
gpsshogi_0.7.0-3.2_source.buildinfo
Files:
 02de2e0ad4a7359b52a5f600cdd8cef1 2060 games optional gpsshogi_0.7.0-3.2.dsc
 87a45f00300667f9460df2d62dabec07 19228 games optional 
gpsshogi_0.7.0-3.2.debian.tar.xz
 288360ee43c9a0b38292f30a0c3e48bd 18186 games optional 
gpsshogi_0.7.0-3.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYe1t4QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFOfZDAC3aVeYZKo31lAg0dpj/PZD742GtUJFTlLy
9S7FIkkTMddt7ouDo2Iba+m58Ox7Smrp9Tu21E38MZMwI1EdzNfxysZl6qH1KqRR
pO/+Y/8R2V4LjbfAfg6LgLpY6jw8Se8gfdiydGrgSOsjuk5UYX9VJsqjA3649vLV
+FFaq3GD+ywpKA3rz7GYMKybh8IVFO+KanNlikwpO4tSRC7KJ91wBxmkPzftWCRf
sjTi90G4mqxw+MCO34UnGsW2QkzXD9lb5Lln5DfH29CLrK9BRVrS6AErK83SiWba
RU8fZV4KCltij/TbWyInvfBHGB7AFipSxkz91cONqZqzkFbziI6T2xCAbVvFJFN7
yZEgqtV9meOdvnTB4Q1oB2T9DYEWx10dHPFCzI9DHE0vR6AutuJc7InDtktxv8dg
AQ9kSJZDhXXEzsW88e1Q/sD3+75RXTLNFJomolddG9OgVYdptEUUdb7yVqzmyDgg
WuKNatQpCyP2GJAw7wMYtzArXvEB4mI=
=1Bt8
-END PGP SIGNATURE-



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

Bug#1069119: gpsshogi: EPL missing from debian/copyright

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is included and also pushed to 
git.diff -Nru gpsshogi-0.7.0/debian/changelog gpsshogi-0.7.0/debian/changelog
--- gpsshogi-0.7.0/debian/changelog 2022-09-27 19:03:18.0 +
+++ gpsshogi-0.7.0/debian/changelog 2024-04-16 18:56:27.0 +
@@ -1,3 +1,11 @@
+gpsshogi (0.7.0-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/copyright: Convert to standardized format
+  * d/copyright: Include EPL text (Closes: #1069119)
+
+ -- Bastian Germann   Tue, 16 Apr 2024 18:56:27 +
+
 gpsshogi (0.7.0-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gpsshogi-0.7.0/debian/copyright gpsshogi-0.7.0/debian/copyright
--- gpsshogi-0.7.0/debian/copyright 2022-09-27 18:58:24.0 +
+++ gpsshogi-0.7.0/debian/copyright 2024-04-16 18:56:27.0 +
@@ -1,13 +1,13 @@
-Format-Specification: 
http://wiki.debian.org/Proposals/CopyrightFormat?action=recall=420
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: GPSShogi
-Upstream-Maintainer: 
+Upstream-Contact:
   TANAKA   Tetsurou  
   KANEKO   Tomoyuki  
   MORIWAKI Daigo 
   SOEDAShunsuke  
   HAYASHI  Yoshiki   
   TAKEUCHI Shougo
-Upstream-Source: http://gps.tanaka.ecc.u-tokyo.ac.jp/osl/
+Source: http://gps.tanaka.ecc.u-tokyo.ac.jp/osl/
 
 Files: *
 Copyright: Copyright (C) 2003-2010 Team GPS
@@ -25,7 +25,7 @@
  You should have received a copy of the GNU General Public License
  along with this program; if not, write to the Free Software
  Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
- .
+Comment:
  On Debian systems, the complete text of the GNU General Public License can
  be found in `/usr/share/common-licenses/GPL-2'.
 
@@ -54,17 +54,212 @@
  .
  This file is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE
  WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
- .
+Comment:
  On Debian systems, the complete text of the GNU General Public License can
  be found in `/usr/share/common-licenses/GPL-2'.
 
 Files: sample/cluster_dashboard/src/net/n01se/clojure_jna.clj
 Copyright: Copyright (c) Chris Houser, May 2009. All rights reserved.
-License:  EPL-1
+Comment:
  The use and distribution terms for this software are covered by the
  Eclipse Public License 1.0 (http://opensource.org/licenses/eclipse-1.0.php)
  which can be found in the file epl-v10.html at the root of this distribution.
  By using this software in any fashion, you are agreeing to be bound by
  the terms of this license.
  You must not remove this notice, or any other, from this software.
-
+License: EPL-1
+ Eclipse Public License - v 1.0
+ .
+ THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC
+ LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
+ CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
+ .
+ 1. DEFINITIONS
+ .
+ "Contribution" means:
+ .
+ a) in the case of the initial Contributor, the initial code and documentation
+distributed under this Agreement, and
+ b) in the case of each subsequent Contributor:
+ i) changes to the Program, and
+ ii) additions to the Program;
+ where such changes and/or additions to the Program originate from and are
+ distributed by that particular Contributor. A Contribution 'originates' from
+ a Contributor if it was added to the Program by such Contributor itself or
+ anyone acting on such Contributor's behalf. Contributions do not include
+ additions to the Program which: (i) are separate modules of software
+ distributed in conjunction with the Program under their own license agreement,
+ and (ii) are not derivative works of the Program.
+ "Contributor" means any person or entity that distributes the Program.
+ .
+ "Licensed Patents" mean patent claims licensable by a Contributor which are
+ necessarily infringed by the use or sale of its Contribution alone or when
+ combined with the Program.
+ .
+ "Program" means the Contributions distributed in accordance with this 
Agreement.
+ .
+ "Recipient" means anyone who receives the Program under this Agreement,
+ including all Contributors.
+ .
+ 2. GRANT OF RIGHTS
+ .
+ a) Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide, royalty-free copyright license to
+reproduce, prepare derivative works of, publicly display, publicly perform,
+distribute and sublicense the Contribution of such Contributor, if any, and
+such derivative works, in source code and object code form.
+ b) Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide, royalty-free patent license under
+Licensed Patents to make, use, sell, offer to sell, import and otherwise
+transfer the Contribution of such Contributor, if any, in source code and
+object code form. This patent license shall apply to the combination of the
+   

Processed: tagging 1061212

[Debian Bug Tracking System]

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

> tags 1061212 + upstream fixed-upstream
Bug #1061212 [src:emscripten] Please upgrade to llvm-toolchain-17
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Bug#1066297: marked as done (dvi2dvi: FTBFS: fontcom.c:45:9: error: implicit declaration of function ‘replfont’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 19:04:22 +
with message-id 
and subject line Bug#1066297: fixed in dvi2dvi 2.0alpha-11
has caused the Debian Bug report #1066297,
regarding dvi2dvi: FTBFS: fontcom.c:45:9: error: implicit declaration of 
function ‘replfont’ [-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.)


-- 
1066297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dvi2dvi
Version: 2.0alpha-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):
> gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g 
> -DPOSIX -DANSI -I/usr/include -DKPATHSEA -Wdate-time -D_FORTIFY_SOURCE=2  -c 
> -o dconv.o dconv.c
> fontcom.c: In function ‘get_font_entry’:
> fontcom.c:45:9: error: implicit declaration of function ‘replfont’ 
> [-Werror=implicit-function-declaration]
>45 | if (replfont(n, s, rn, , )) {
>   | ^~~~
> fontcom.c: At top level:
> fontcom.c:100:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   100 | first_markchar(fe, c)
>   | ^~
> fontcom.c:150:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   150 | null_markchar(fe, c)
>   | ^
> fontcom.c:178:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   178 | null_setchar(c)
>   | ^~~~
> dfdcom.c:41:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>41 | dfd_dirkeep()
>   | ^~~
> fontcom.c:185:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   185 | null_setstring(s, len)
>   | ^~
> dfdcom.c: In function ‘dfd_movedown’:
> dfdcom.c:139:5: error: implicit declaration of function ‘dev_move’ 
> [-Werror=implicit-function-declaration]
>   139 | dev_move(a, n, command-n);
>   | ^~~~
> dvi2.c:104:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   104 | main(argc, argv)
>   | ^~~~
> dvi2.c: In function ‘main’:
> dvi2.c:119:21: error: implicit declaration of function ‘getenv’ 
> [-Werror=implicit-function-declaration]
>   119 | if ((dvi2path = getenv(DVI2PATHENV)) == NULL)
>   | ^~
> dvi2.c:8:1: note: ‘getenv’ is defined in header ‘’; did you forget 
> to ‘#include ’?
> 7 | #include
>   +++ |+#include 
> 8 | #endif
> dvi2.c:119:19: warning: assignment to ‘char *’ from ‘int’ makes pointer from 
> integer without a cast [-Wint-conversion]
>   119 | if ((dvi2path = getenv(DVI2PATHENV)) == NULL)
>   |   ^
> dvi2.c:124:18: warning: assignment to ‘char *’ from ‘int’ makes pointer from 
> integer without a cast [-Wint-conversion]
>   124 | if ((dvi2lib = getenv(DVI2LIBENV)) == NULL)
>   |  ^
> dvi2.c:129:23: warning: assignment to ‘char *’ from ‘int’ makes pointer from 
> integer without a cast [-Wint-conversion]
>   129 | if ((fontdescfile = getenv(FONTDESCENV)) == NULL)
>   |   ^
> dfdcom.c: In function ‘dfd_movedown_v’:
> dfdcom.c:149:5: error: implicit declaration of function ‘dev_makemove’ 
> [-Werror=implicit-function-declaration]
>   149 | dev_makemove(-l, RIGHT1-1);
>   | ^~~~
> dfdcom.c: In function ‘dfd_setrule’:
> dfdcom.c:175:5: error: implicit declaration of function ‘dev_setrule’; did 
> you mean ‘dfd_setrule’? [-Werror=implicit-function-declaration]
>   175 | dev_setrule(makeint(a, 4), makeint(b, 4), command);
>   | ^~~
>   | dfd_setrule
> dvi2.c:134:5: error: implicit declaration of function ‘init_default’ 
> [-Werror=implicit-function-declaration]
>   134 | init_default(KPSENAME);
>   | ^~~~
> dfdcom.c: In function ‘d_setrule_v’:
> dfdcom.c:188:13: error: implicit declaration of function ‘dev_push’ 
> [-Werror=implicit-function-declaration]
>   188 | dev_push();
>   | ^~~~
> dconv.c:20:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>20 | setcurdconv(dp)
>   | 

Bug#1065069: marked as done (apt-move rebuilt with the wrong ABI on 32-bit architectures)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 21:02:22 +0200
with message-id 
and subject line Re: apt-move rebuilt with the wrong ABI on 32-bit architectures
has caused the Debian Bug report #1065069,
regarding apt-move rebuilt with the wrong ABI on 32-bit 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.)


-- 
1065069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apt-move
Version: 4.2.27-6+b1
Severity: serious
X-Debbugs-Cc: debian-rele...@lists.debian.org

apt-move has been binNMUed for the time64_t transition. However due to
the lack of extra-depends and the impossibility to recreate chroots on
the buildd, it has been built with pre time64_t version of dpkg and
gcc-13, probably leading to the wrong ABI.

See for instance:
https://buildd.debian.org/status/fetch.php?pkg=apt-move=armel=4.2.27-6%2Bb1=1709156067=0
--- End Message ---
--- Begin Message ---
On Thu, 29 Feb 2024 12:15:53 +0100 Aurelien Jarno  
wrote:

apt-move has been binNMUed for the time64_t transition. However due to
the lack of extra-depends and the impossibility to recreate chroots on
the buildd, it has been built with pre time64_t version of dpkg and
gcc-13, probably leading to the wrong ABI.

See for instance:
https://buildd.debian.org/status/fetch.php?pkg=apt-move=armel=4.2.27-6%2Bb1=1709156067=0


binNMUed again.

Andreas--- End Message ---

Bug#1067959: marked as done (sambamba: FTBFS on armhf (supported compiler issue))

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 18:42:02 +
with message-id 
and subject line Bug#1067959: fixed in sambamba 1.0.1+dfsg-2
has caused the Debian Bug report #1067959,
regarding sambamba: FTBFS on armhf (supported compiler issue)
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.)


-- 
1067959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sambamba
Severity: serious
Tags: ftbfs
Control: found -1 1.0.1+dfsg-1
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

sambamba fails to build on armhf.

FYI:

https://buildd.debian.org/status/fetch.php?pkg=sambamba=armhf=1.0.1%2Bdfsg-1=1699230688=0

Regards,
--- End Message ---
--- Begin Message ---
Source: sambamba
Source-Version: 1.0.1+dfsg-2
Done: Andreas Tille 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Apr 2024 20:18:00 +0200
Source: sambamba
Architecture: source
Version: 1.0.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1067959
Changes:
 sambamba (1.0.1+dfsg-2) unstable; urgency=medium
 .
   * Build-Depends: architecture-is-64-bit, architecture-is-little-endian
 Closes: #1067959
   * Drop unneeded copyright paragraph
   * Drop unused patches
   * Standards-Version: 4.7.0 (routine-update)
   * Set upstream metadata fields: Repository.
   * Build-Depends: s/pkg-config/pkgconf/
Checksums-Sha1:
 7868dac3c6a64a6abf05613a8960e277f35a9b8e 2276 sambamba_1.0.1+dfsg-2.dsc
 316c001f3207c3f74f7223fa9d41fc2390abf4cf 6928 
sambamba_1.0.1+dfsg-2.debian.tar.xz
 37c6d64993d25581cd830f150ca1f6c070bfbd8c 8241 
sambamba_1.0.1+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 242abed88e9635204d5dd414661b090fdd129a673179fb68782fa4771253f795 2276 
sambamba_1.0.1+dfsg-2.dsc
 d3c6c266c79e598fe17753baeea294f2c56e2623fe7758f92c789e5ec6966ca4 6928 
sambamba_1.0.1+dfsg-2.debian.tar.xz
 1281f4a2e0b20765a53499fd33b808843cee854d77952a47f07696a41b693960 8241 
sambamba_1.0.1+dfsg-2_amd64.buildinfo
Files:
 84fb33db02dc334f018c3b80dc93b676 2276 science optional 
sambamba_1.0.1+dfsg-2.dsc
 ddc7a8998e54cedf55b0ad7de4fbf8aa 6928 science optional 
sambamba_1.0.1+dfsg-2.debian.tar.xz
 379ba7e04d638743184c424f630dfc93 8241 science optional 
sambamba_1.0.1+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmYewYQRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEP6w/7Bn73Bijj5hDjFaUdcoxGXZiazHYoFVJt
sZSE/kXduG1v6dk3J8Ua4Yoar5lczTjwMkPaybjnMuJh7k54V5wPnNPWXQOUwi12
2afuW2C7yMl97ba69+vNlovlHwqlFiH3q/3OJ+utGZM79KCdLoshn+iXFOhVBNlD
MH8v79E6+TBTcCUAvPuIs6acqgRc7kAJgtavSrQ+O8BdKv8VybsYv25skkioqz8i
TqY34p3r0Kn2461+zaKBwHA4gLjoayqDLHl6flOud1AAUxCnHLYrZKcnEBdOAg24
dgPuV/3t5HMuPrVRSWYuLEISGIAnU+iXw6MWAnCV7puDztcNrR0GZhL1R6qacFGY
HvDiUcUTl1c9NVA+lSFH3cGqpuvdW9JeJMMUS971rXvPp9MYEgcZ/lgIS2KEKQEA
yDlt9bW31JmXBRv175ebg/c4m1mrt8cOBCzq4AXF7O/eo07iz7rM8D7kWCiigP5c
7ToK0fA4R8+3FkJWgxAsNPAqJNSvr8RgqnN3MlDPTc+9do8SoIEH67kxwkgHAlPZ
VelwFJn5cj44/CSLV19RRTt3x7ZgHUoKd3SaMoR3fiHJGFx7YUNFMwzgPemEUicH
pDUUfjxWVmbA80i3Vn33h+mMEIqeL0ak3QpsAGuuLRR/lE9SeRsaqb3NEn4/TtHx
UUYx/4DhM5Y=
=PKs7
-END PGP SIGNATURE-



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

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

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 18:19:28 +
with message-id 
and subject line Bug#1068074: fixed in koko 23.08.5+ds.1-2
has caused the Debian Bug report #1068074,
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.)


-- 
1068074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: koko
Version: 23.08.5ds.1-1
Severity: serious
Tags: ftbfs

The package explicitly Build-Depends: libqt5gui5, this needs to be changed to
libqt5gui5t64 if it's 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/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: koko
Source-Version: 23.08.5+ds.1-2
Done: Marco Mattiolo 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 23:11:58 +0200
Source: koko
Architecture: source
Version: 23.08.5+ds.1-2
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Marco Mattiolo 
Closes: 1066088 1068074
Changes:
 koko (23.08.5+ds.1-2) unstable; urgency=medium
 .
   [ James Addison ]
   * Fix build reproducibility for timestamps in zip (Closes: #1066088)
 .
   [ Marco Mattiolo ]
   * Update d/control for build-deps after time64 transition (Closes: #1068074)
   * Fix build reproducibility for cmake_rpath_contains_build_path
Checksums-Sha1:
 14b3f4ace10bf80104b29be16292458014fed466 2454 koko_23.08.5+ds.1-2.dsc
 e22a1a3a38ddd259551a010899adfdbc1bea7fc8 26076 
koko_23.08.5+ds.1-2.debian.tar.xz
 75b8b4d525c33b7a95cb0e0a8199ca7d5927f6ff 20918 
koko_23.08.5+ds.1-2_source.buildinfo
Checksums-Sha256:
 00f235a7338b89cafff14f2f64b336fa6712e073b9ce2658f03331f49d8a4ccb 2454 
koko_23.08.5+ds.1-2.dsc
 4e10e82fa676dff7c988a6834741661240b0b3f1f055526d0ed71fbf2a76 26076 
koko_23.08.5+ds.1-2.debian.tar.xz
 ca4f6a01567a3a17b95896013c6fc9c1cb96b6ee80cd579c5ce457a16fa6318d 20918 
koko_23.08.5+ds.1-2_source.buildinfo
Files:
 e68c102d9d1f2d8f6b7eedb1d0dc36b4 2454 kde optional koko_23.08.5+ds.1-2.dsc
 9346fd307fa014adb46c3c48c5567466 26076 kde optional 
koko_23.08.5+ds.1-2.debian.tar.xz
 25f7c0b081d686eb4e62b0cf168aeef9 20918 kde optional 
koko_23.08.5+ds.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEeW2zk9w/9AIituoi0+u1lmu5kZYFAmYevaQACgkQ0+u1lmu5
kZaJoA//RvOPQaVpDifzukMpy2hPxg7p/hbWr/3FkEqsp7mDh/qc1fwobVUT6krc
WHDLueqM0WEgggjPzTBV6CODwfyTDz/FuSvglQagDP6CnkePGLtuHk0UCnFFtGXN
KRe3tGkSH/E+PcMt1Cgu+KWK/gnIYu6pqg4reGvImyvw98pLT6Wp19M0NKIE75Bw
GvL9cOt/YTCUm+2xsy2X+wtPMau6ZVLQn9/pc5x/0SesTaE0Mc/6PAWRy/WdLACt
DmjgBAw7D5epX51L8Xlu9m4yo6fI11PAhEqtkzSixQ/wan6K3Njk75RQPp/RSBo9
XSROIVo48hXAp8rGOgOi3FqMiw0vub/OyyyQ9xHeG/wHZ5/2MI3F0FSXAnAs3CUz
Wp9E9UUfya+BsQ9Mp7U8f9+4Tf+9YJBNX3BGotANfyN8u0is8TQCKV9MkgiiUzDE
7lt8qrOWaQQDdOeqFSz7cTgHyhW66RnIf/Lgp4i02ZZYApp8GG6GyaATalT1VY0R
ZNQv7RD82sCtG8O+vUIx0nw61+jcAtbjaH4klAmzA/LgKyioILXRV1kES8vV5N5O
ipqNTsU5wuisUV/FBmaFcNyabv8vNQQPB07ZgTlSG4JD9C5yPw0W8gvGF6JihOm3
mHOvWhFbWHISX5YPrIHBZ9NH0zbFc5IlS3AEmGAxyVjMNEr6J7M=
=Je8k
-END PGP SIGNATURE-



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

Bug#1069119: gpsshogi: EPL missing from debian/copyright

[Bastian Germann]

Source: gpsshogi
Version: 0.7.0-3.1
Severity: serious

The EPL-1 that is mentioned in d/copyright is not included in that file with 
the complete text.
A copy is included in debian/epl-v10.txt. Please include it in d/copyright.

Bug#999284: marked as done (gdb-msp430: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 17:48:12 +
with message-id 
and subject line Bug#1036349: Removed package(s) from unstable
has caused the Debian Bug report #999284,
regarding gdb-msp430: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdb-msp430
Version: 7.2a~mspgcc-20111205-3.1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 7.2a~mspgcc-20111205-3.1+rm

Dear submitter,

as the package gdb-msp430 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1036349

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#965545: marked as done (gdb-msp430: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 17:48:12 +
with message-id 
and subject line Bug#1036349: Removed package(s) from unstable
has caused the Debian Bug report #965545,
regarding gdb-msp430: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdb-msp430
Version: 7.2a~mspgcc-20111205-3.1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package gdb-msp430 uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 7.2a~mspgcc-20111205-3.1+rm

Dear submitter,

as the package gdb-msp430 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1036349

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1065310: marked as done (deborphan should take "Provides:" into account)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 17:49:34 +
with message-id 
and subject line Bug#1065312: Removed package(s) from unstable
has caused the Debian Bug report #1065310,
regarding deborphan should take "Provides:" into account
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.)


-- 
1065310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: deborphan
Version: 1.7.35
Severity: normal

qaa:~> deborphan
libgnutls-openssl27t64
libzvbi0t64

meaning that I could remove libgnutls-openssl27t64, but actually
this is not possible:

qaa:~> apt remove -s libgnutls-openssl27t64
[...]
The following packages will be REMOVED:
  gkrellm gkrellm-volume gkrellweather libgnutls-openssl27t64

Indeed, gkrellm depends on libgnutls-openssl27, which is provided
by libgnutls-openssl27t64:

Package: libgnutls-openssl27t64
[...]
Version: 3.8.3-1.1
Replaces: libgnutls-openssl27
Provides: libgnutls-openssl27 (= 3.8.3-1.1)
Depends: libgnutls30t64 (= 3.8.3-1.1), libc6 (>= 2.34)
Breaks: libgnutls-openssl27 (<< 3.8.3-1.1)
[...]

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

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

Versions of packages deborphan depends on:
ii  libc6  2.37-15.1

Versions of packages deborphan recommends:
ii  apt   2.7.13+b1
ii  gettext-base  0.21-14+b1

deborphan suggests no packages.

-- no debconf information

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

Dear submitter,

as the package deborphan has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1065312

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1054828: marked as done (propellor: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 17:35:28 +
with message-id 
and subject line Bug#1054828: fixed in propellor 5.17-1
has caused the Debian Bug report #1054828,
regarding propellor: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: 
configure-ghc-stamp] Error 25
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.)


-- 
1054828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: propellor
Version: 5.13-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-propellor-doc.substvars
> dh_installdirs -plibghc-propellor-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe'
> Running find . ! -newer /tmp/0XPnzc0se_ -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-propellor-dev
> libghc-propellor-doc
> libghc-propellor-prof
> propellor
> Running dh_listpackages
> libghc-propellor-dev
> libghc-propellor-doc
> libghc-propellor-prof
> propellor
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/propellor-5.13/ --datasubdir=propellor 
> --htmldir=/usr/share/doc/libghc-propellor-doc/html/ --enable-library-profiling
> Non-zero exit code 1.
> Using Parsec parser
> Configuring propellor-5.13...
> Flags chosen: withtypeerrors=True
> CallStack (from HasCallStack):
>   withMetadata, called at 
> libraries/Cabal/Cabal/src/Distribution/Simple/Utils.hs:370:14 in 
> Cabal-3.8.1.0:Distribution.Simple.Utils
> Error: hlibrary.setup: Duplicate modules in library: Utility.Scheduled
> 
>  at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.
>   
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
>  "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
> "--libexecdir=/usr/lib", ...) called at 
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133
>   
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
>  "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
> "--libexecdir=/usr/lib", ...) called at 
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 637
>   Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe() 
> called at -e line 1
> make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] 
> Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/propellor_5.13-3_unstable.log

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

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

Bug#1054640: marked as done (propellor: FTBFS with ghc 9.4: Not in scope: type constructor or class `UserEntry')

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 17:35:28 +
with message-id 
and subject line Bug#1054640: fixed in propellor 5.17-1
has caused the Debian Bug report #1054640,
regarding propellor: FTBFS with ghc 9.4: Not in scope: type constructor or 
class `UserEntry'
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.)


-- 
1054640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: propellor
Version: 5.13-3
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)

propellor FTBFS with ghc 9.4 (it still builds fine with 9.0 in testing):

https://salsa.debian.org/debian/propellor/-/jobs/4840519

[139 of 180] Compiling Utility.UserInfo ( src/Utility/UserInfo.hs, 
dist-ghc/build/Utility/UserInfo.o, dist-ghc/build/Utility/UserInfo.dyn_o )
src/Utility/UserInfo.hs:57:23: error:
Not in scope: type constructor or class `UserEntry'
   |
57 | myVal :: [String] -> (UserEntry -> String) -> IO (Either String String)
   |   ^
-e: error: debian/hlibrary.setup build --builddir=dist-ghc returned exit code 1
 at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 880.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup build 
--builddir=dist-ghc returned exit"...) called at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 610
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup build 
--builddir=dist-ghc") called at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm 
line 473
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "build", 
"--builddir=dist-ghc") called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 656
Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called 
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Source: propellor
Source-Version: 5.17-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated propellor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 16 Apr 2024 19:17:26 +0200
Source: propellor
Architecture: source
Version: 5.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1045437 1049841 1053981 1054640 1054828
Changes:
 propellor (5.17-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream release.  (Closes: #1054640, #1053981, #1054828)
   * Clean more build artefacts.  (Closes: #1045437, #1049841)
Checksums-Sha1:
 92a0775bcb34c479323628f90a690fde2d970e6c 3094 propellor_5.17-1.dsc
 be0ceea30e7f191116fa6c77b7e32462b07703b4 738024 propellor_5.17.orig.tar.xz
 b4100815057fc23ea29552df6790f43f9f17e76e 31624 propellor_5.17-1.debian.tar.xz
 b64211982b6779f77c8d6bbc2f71af4ad5022557 9447 propellor_5.17-1_source.buildinfo
Checksums-Sha256:
 05a91a2363c5d7b1e4f3da4321df87a7e0b01090a724b72707cdb558382e07b5 3094 
propellor_5.17-1.dsc
 96464166ff001bfaee15d5b61ef8632f1d99d41aefb456235c79b2a1e9750c21 738024 
propellor_5.17.orig.tar.xz
 ea519b43a535f37fd0785ea37343f14fa80d2f38e004f7f14c04a31fb8ce43b8 31624 
propellor_5.17-1.debian.tar.xz
 93a23f9df334eed7b74e7dfeba5fb667d3b8a1d776ae70f864ebc0bfbfbc0e9e 9447 
propellor_5.17-1_source.buildinfo
Files:
 bead5eeada71c5c0cc332fe0019df022 3094 admin optional propellor_5.17-1.dsc
 dfc06b5a7c3b26cc7ea652e4e39aa6fc 738024 admin optional 
propellor_5.17.orig.tar.xz
 9c9fc0b925adca76ee45b112eb0490a8 31624 admin optional 
propellor_5.17-1.debian.tar.xz
 6b70f9989ace95892ec7f98fb0771785 9447 admin optional 
propellor_5.17-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYes1gQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCI3IEACxajhlAJfJSVowmKk9Sys8pGOuX+dZ1Cxv
OvOOkF5wVVEk2GkVE85K64zb9kUIf+71pgMPQSt64K7dgu5CkZtBTkUCNEX/jk7x

Bug#1053981: marked as done (propellor: Needs a sourceful upload to support haddock interface 41)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 17:35:28 +
with message-id 
and subject line Bug#1053981: fixed in propellor 5.17-1
has caused the Debian Bug report #1053981,
regarding propellor: Needs a sourceful upload to support haddock interface 41
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.)


-- 
1053981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: propellor
Version: 5.13-3
Severity: serious

This package needs a sourceful upload to rebuild libghc-propellor-doc
against interface 41.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Source: propellor
Source-Version: 5.17-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated propellor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 16 Apr 2024 19:17:26 +0200
Source: propellor
Architecture: source
Version: 5.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1045437 1049841 1053981 1054640 1054828
Changes:
 propellor (5.17-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream release.  (Closes: #1054640, #1053981, #1054828)
   * Clean more build artefacts.  (Closes: #1045437, #1049841)
Checksums-Sha1:
 92a0775bcb34c479323628f90a690fde2d970e6c 3094 propellor_5.17-1.dsc
 be0ceea30e7f191116fa6c77b7e32462b07703b4 738024 propellor_5.17.orig.tar.xz
 b4100815057fc23ea29552df6790f43f9f17e76e 31624 propellor_5.17-1.debian.tar.xz
 b64211982b6779f77c8d6bbc2f71af4ad5022557 9447 propellor_5.17-1_source.buildinfo
Checksums-Sha256:
 05a91a2363c5d7b1e4f3da4321df87a7e0b01090a724b72707cdb558382e07b5 3094 
propellor_5.17-1.dsc
 96464166ff001bfaee15d5b61ef8632f1d99d41aefb456235c79b2a1e9750c21 738024 
propellor_5.17.orig.tar.xz
 ea519b43a535f37fd0785ea37343f14fa80d2f38e004f7f14c04a31fb8ce43b8 31624 
propellor_5.17-1.debian.tar.xz
 93a23f9df334eed7b74e7dfeba5fb667d3b8a1d776ae70f864ebc0bfbfbc0e9e 9447 
propellor_5.17-1_source.buildinfo
Files:
 bead5eeada71c5c0cc332fe0019df022 3094 admin optional propellor_5.17-1.dsc
 dfc06b5a7c3b26cc7ea652e4e39aa6fc 738024 admin optional 
propellor_5.17.orig.tar.xz
 9c9fc0b925adca76ee45b112eb0490a8 31624 admin optional 
propellor_5.17-1.debian.tar.xz
 6b70f9989ace95892ec7f98fb0771785 9447 admin optional 
propellor_5.17-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYes1gQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCI3IEACxajhlAJfJSVowmKk9Sys8pGOuX+dZ1Cxv
OvOOkF5wVVEk2GkVE85K64zb9kUIf+71pgMPQSt64K7dgu5CkZtBTkUCNEX/jk7x
4ItUmcIdYaTEvlYDx2TB/C2FqsJlizbdhiPZpvJUijhFJwBmi5LNvfHXR1AYNO6X
n2pA47Nc1gsLq2jraN2JUCu4c+9e8AXcZ3cSmMtQO0JwjakOOLSuSqTFQOt5kqmr
gRVFZqsl3KgaIMYA+FJkVXqW1uV5k46dN5WnCnIxn7OuRGqV0KBVoFddoSBZT+XO
zfc1WJUtoTOxhCZbUlnzI0L5Ic1niUiLOWEG2HYK3n08jJv+XJJ18/rNepzjygJn
JzQ//iH56F58Ocoi+Tjj/JkBnbw1wvgCVik2HeXcnYJphwLKVG61nSAGdTSP7Shv
EYxbV4k+JlF3o/FMaO/NuKwCXhx/Tgxtl09Lu4cKYyjUdVr/kubJsNksPFcLUDUL
YWZibk3x3bEj1udHfJmv9Cnr7P6ruaN8LtFr1cWnvE8eLUb5zGJ9AtUD2tHm11gL
tepnDnVVURjjT1npIQx7EHkUH4q7JGspEM0Dzeya1pMjWp/kRSOWJS9lyoQf/MH7
hHtqW99AeJ9PpgSiHb8yHV6+dG15jPTceqR5Y6K2s2Ce8yOw0AGlrKCNdJ1QJarI
TQGSnt+61A==
=VoPC
-END PGP SIGNATURE-



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

Processed: tagging 1061213, tagging 1061215, tagging 1068134, tagging 1068133, tagging 965837, tagging 1065976 ...

[Debian Bug Tracking System]

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

> tags 1061213 + upstream
Bug #1061213 [src:intel-graphics-compiler] Please upgrade to llvm-toolchain-17
Added tag(s) upstream.
> tags 1061215 + upstream
Bug #1061215 [src:oclgrind] Please upgrade to llvm-toolchain-17
Added tag(s) upstream.
> tags 1068134 + sid trixie
Bug #1068134 {Done: Mattias Ellert } 
[src:globus-gram-job-manager-scripts] globus-gram-job-manager-scripts: arch:all 
package depends on pre-t64 library
Added tag(s) trixie and sid.
> tags 1068133 + sid trixie
Bug #1068133 {Done: Mattias Ellert } 
[src:globus-gram-audit] globus-gram-audit: arch:all package depends on pre-t64 
library
Added tag(s) sid and trixie.
> tags 965837 + patch
Bug #965837 [src:tart] tart: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
Added tag(s) patch.
> tags 1065976 + pending
Bug #1065976 [src:python-levenshtein] python-levenshtein: FTBFS on arm{el,hf}: 
Levenshtein/_levenshtein.c:749:15: error: implicit declaration of function 
‘PyUnicode_AS_UNICODE’; did you mean ‘PyUnicode_AsUCS4’? 
[-Werror=implicit-function-declaration]
Added tag(s) pending.
> tags 1061434 + pending
Bug #1061434 [python3-levenshtein] python 3.12 extension not working
Added tag(s) pending.
> reassign 1069004 src:casacore-data-sources 2-4
Bug #1069004 [casacore-data-services] casacore-data-services: Hard coded 
build-depends on decrufted lib libcasa-meas7
Warning: Unknown package 'casacore-data-services'
Bug reassigned from package 'casacore-data-services' to 
'src:casacore-data-sources'.
No longer marked as found in versions 2-4.
Ignoring request to alter fixed versions of bug #1069004 to the same values 
previously set
Bug #1069004 [src:casacore-data-sources] casacore-data-services: Hard coded 
build-depends on decrufted lib libcasa-meas7
Marked as found in versions casacore-data-sources/2-4.
> tags 1069004 + sid trixie
Bug #1069004 [src:casacore-data-sources] casacore-data-services: Hard coded 
build-depends on decrufted lib libcasa-meas7
Added tag(s) trixie and sid.
> tags 1044915 + pending
Bug #1044915 [src:emscripten] emscripten: Fails to build source after 
successful build
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1044915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044915
1061213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061213
1061215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061215
1061434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061434
1065976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065976
1068133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068133
1068134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068134
1069004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069004
965837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Move where it was fixed

[Debian Bug Tracking System]

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

> reassign 1064730 src:rocthrust
Bug #1064730 {Done: Gianfranco Costamagna } 
[src:stdgpu] stdgpu: FTBFS: type_traits.h:736:1: error: expected type-specifier 
before ‘template’
Bug reassigned from package 'src:stdgpu' to 'src:rocthrust'.
No longer marked as found in versions stdgpu/1.3.0+git20220507.32e0517-5.
No longer marked as fixed in versions rocthrust/5.7.1-2.1.
> close 1064730 5.7.1-2.1
Bug #1064730 {Done: Gianfranco Costamagna } 
[src:rocthrust] stdgpu: FTBFS: type_traits.h:736:1: error: expected 
type-specifier before ‘template’
The source 'rocthrust' and version '5.7.1-2.1' do not appear to match any 
binary packages
Marked as fixed in versions rocthrust/5.7.1-2.1.
Bug #1064730 {Done: Gianfranco Costamagna } 
[src:rocthrust] stdgpu: FTBFS: type_traits.h:736:1: error: expected 
type-specifier before ‘template’
Bug 1064730 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#1064730: marked as done (stdgpu: FTBFS: type_traits.h:736:1: error: expected type-specifier before ‘template’)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 17:06:15 +
with message-id 
and subject line Bug#1064730: fixed in rocthrust 5.7.1-2.1
has caused the Debian Bug report #1064730,
regarding stdgpu: FTBFS: type_traits.h:736:1: error: expected type-specifier 
before ‘template’
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.)


-- 
1064730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stdgpu
Version: 1.3.0+git20220507.32e0517-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-openmp/src/stdgpu && /usr/bin/c++ 
> -DTHRUST_DEVICE_SYSTEM=THRUST_DEVICE_SYSTEM_OMP -Dstdgpu_EXPORTS 
> -I/<>/src/stdgpu/.. 
> -I/<>/obj-openmp/src/stdgpu/include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -pedantic -Wextra -Wshadow 
> -Wsign-compare -Wconversion -Wfloat-equal -Wundef -Wdouble-promotion -fopenmp 
> -MD -MT src/stdgpu/CMakeFiles/stdgpu.dir/openmp/impl/device.cpp.o -MF 
> CMakeFiles/stdgpu.dir/openmp/impl/device.cpp.o.d -o 
> CMakeFiles/stdgpu.dir/openmp/impl/device.cpp.o -c 
> /<>/src/stdgpu/openmp/impl/device.cpp
> In file included from /usr/include/thrust/iterator/iterator_facade.h:36,
>  from /usr/include/thrust/iterator/iterator_adaptor.h:36,
>  from /usr/include/thrust/detail/pointer.h:26,
>  from /<>/src/stdgpu/../stdgpu/iterator.h:28,
>  from /<>/src/stdgpu/impl/iterator.cpp:16:
> /usr/include/thrust/detail/type_traits.h:736:1: error: expected 
> type-specifier before ‘template’
>   736 | template 
>   | ^~~~
> In file included from 
> /usr/include/thrust/detail/execute_with_allocator_fwd.h:21,
>  from /usr/include/thrust/detail/execute_with_allocator.h:21,
>  from /usr/include/thrust/execution_policy.h:26,
>  from /<>/src/stdgpu/../stdgpu/execution.h:30,
>  from /<>/src/stdgpu/../stdgpu/memory.h:32,
>  from /<>/src/stdgpu/impl/memory.cpp:16:
> /usr/include/thrust/detail/type_traits.h:736:1: error: expected 
> type-specifier before ‘template’
>   736 | template 
>   | ^~~~
> In file included from 
> /usr/include/thrust/detail/execute_with_allocator_fwd.h:21,
>  from /usr/include/thrust/detail/execute_with_allocator.h:21,
>  from /usr/include/thrust/execution_policy.h:26,
>  from /<>/src/stdgpu/../stdgpu/execution.h:30,
>  from /<>/src/stdgpu/../stdgpu/memory.h:32,
>  from 
> /<>/src/stdgpu/../stdgpu/openmp/memory.h:20,
>  from /<>/src/stdgpu/openmp/impl/memory.cpp:16:
> /usr/include/thrust/detail/type_traits.h:736:1: error: expected 
> type-specifier before ‘template’
>   736 | template 
>   | ^~~~
> In file included from /usr/include/thrust/detail/functional/actor.h:34,
>  from /usr/include/thrust/detail/functional/placeholder.h:20,
>  from /usr/include/thrust/functional.h:26,
>  from /usr/include/thrust/system/detail/generic/copy.inl:21,
>  from /usr/include/thrust/system/detail/generic/copy.h:57,
>  from /usr/include/thrust/detail/copy.inl:22,
>  from /usr/include/thrust/detail/copy.h:90,
>  from 
> /usr/include/thrust/system/detail/sequential/merge.inl:21,
>  from /usr/include/thrust/system/detail/sequential/merge.h:78,
>  from /usr/include/thrust/system/cpp/detail/merge.h:22,
>  from /usr/include/thrust/system/cpp/execution_policy.h:51,
>  from /usr/include/thrust/execution_policy.h:33:
> /usr/include/thrust/detail/type_traits/result_of_adaptable_function.h:41:18: 
> error: ‘invoke_result_t’ does not name a type
>41 | using type = invoke_result_t;
>   |  ^~~
> In file included from /usr/include/thrust/detail/functional/actor.h:34,
>  from /usr/include/thrust/detail/functional/placeholder.h:20,
>  from /usr/include/thrust/functional.h:26,
>  from /usr/include/thrust/system/detail/generic/copy.inl:21,
>  from /usr/include/thrust/system/detail/generic/copy.h:57,
>

Bug#1060787: marked as done (i2pd: FTBFS on armel: Host compiler appears to require libatomic for 64-bit operations, but cannot find it.)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 17:04:30 +
with message-id 
and subject line Bug#1060787: fixed in i2pd 2.51.0-1
has caused the Debian Bug report #1060787,
regarding i2pd: FTBFS on armel: Host compiler appears to require libatomic for 
64-bit operations, but cannot find it.
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=i2pd=armel=2.49.0-1=1704531194=0

dh_auto_configure --buildsystem=cmake --sourcedirectory=build/ -- \
-DWITH_UPNP=ON -DWITH_WEBSOCKETS=ON
cd obj-arm-linux-gnueabi && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/arm-linux-gnueabi 
-DWITH_UPNP=ON -DWITH_WEBSOCKETS=ON ../build
-- The CXX compiler identification is GNU 13.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- The C compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Success
-- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB
-- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB - Failed
-- Looking for __atomic_load_8 in atomic
-- Looking for __atomic_load_8 in atomic - not found
CMake Error at cmake_modules/CheckAtomic.cmake:80 (message):
  Host compiler appears to require libatomic for 64-bit operations, but
  cannot find it.
Call Stack (most recent call first):
  CMakeLists.txt:54 (include)


-- Configuring incomplete, errors occurred!


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: i2pd
Source-Version: 2.51.0-1
Done: Yangfl 

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

Debian distribution maintenance software
pp.
Yangfl  (supplier of updated i2pd 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: Fri, 12 Apr 2024 13:27:08 +0800
Source: i2pd
Architecture: source
Version: 2.51.0-1
Distribution: unstable
Urgency: medium
Maintainer: Yangfl 
Changed-By: Yangfl 
Closes: 1060787 1064793
Changes:
 i2pd (2.51.0-1) unstable; urgency=medium
 .
   * New upstream release
 * Fix FTBFS on armel (Closes: #1060787)
   * Link /usr/sbin/i2pd to /usr/bin/i2pd (Closes: #1064793)
   * Bump Standards-Version to 4.7.0
Checksums-Sha1:
 82afef0694f5bfaa48fc9e28fd59ad5e43455df3 1997 i2pd_2.51.0-1.dsc
 1156e7e6a1eb1014d2160db0a598a9a252111832 670699 i2pd_2.51.0.orig.tar.gz
 477bd56e6e0b5783e7213800773082622b9f1bd0 7348 i2pd_2.51.0-1.debian.tar.xz
 51863511ba9befa652e97c8b6114e03b3aa73f97 8028 i2pd_2.51.0-1_amd64.buildinfo
Checksums-Sha256:
 a11bfff8fe55baec126e75ba7fa9ac5eec3f4f830f644afd69cb794aaff267ce 1997 
i2pd_2.51.0-1.dsc
 d7e4fe2c5c3c00a9115f061b797be3d2fc81bb25beddb20a636ae2b0c912ce31 670699 
i2pd_2.51.0.orig.tar.gz
 c79ffea766fa85b725fed9ebab49ef71ba8ec6caeeeb6e2a78d8ef06feccaeab 7348 
i2pd_2.51.0-1.debian.tar.xz
 fed273ca85919c41461ae4a39b820e7388d47e92a06c3b5c8fe9439b58da7c7d 8028 
i2pd_2.51.0-1_amd64.buildinfo
Files:
 5db359fa781f4665cddd37981f48cd05 1997 net optional i2pd_2.51.0-1.dsc
 

Bug#1064762: Upstream has an incoming fix

[Markus Blatt]

Hi,

seems like upstream already has a proposed fix, see [1]

Best,

Markus

[1] https://gitlab.kitware.com/vtk/vtk/-/issues/19258#note_1510307

Processed (with 1 error): reassign bug 1064762 to vtk9

[Debian Bug Tracking System]

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

> reassign 1064762 vtk9
Bug #1064762 [libexpat1] Parsing of vtk files fails for files that worked 
previously (e.g. in bookworm)
Bug reassigned from package 'libexpat1' to 'vtk9'.
No longer marked as found in versions expat/2.6.2-1.
Ignoring request to alter fixed versions of bug #1064762 to the same values 
previously set
> retitle 1064762 vtk9 fails to parse appendedData in vtk file with expat 
> >=2.6.2
Bug #1064762 [vtk9] Parsing of vtk files fails for files that worked previously 
(e.g. in bookworm)
Changed Bug title to 'vtk9 fails to parse appendedData in vtk file with expat 
>=2.6.2' from 'Parsing of vtk files fails for files that worked previously 
(e.g. in bookworm)'.
> found 1064762 9.1.0+really9.1.0+dfsg2-7.1
Bug #1064762 [vtk9] vtk9 fails to parse appendedData in vtk file with expat 
>=2.6.2
Marked as found in versions vtk9/9.1.0+really9.1.0+dfsg2-7.1.
> found 1064762 9.3.0+dfsg1-1~exp4
Bug #1064762 [vtk9] vtk9 fails to parse appendedData in vtk file with expat 
>=2.6.2
Marked as found in versions vtk9/9.3.0+dfsg1-1~exp4.
> merge 1064762 1065270
Bug #1064762 [vtk9] vtk9 fails to parse appendedData in vtk file with expat 
>=2.6.2
Unable to merge bugs because:
severity of #1065270 is 'important' not 'serious'
blockedby of #1065270 is '1064762' not ''
affects of #1065270 is '' not 'vtk9,dune-grid'
package of #1065270 is 'paraview' not 'vtk9'
blocks of #1064762 is '1065270' not ''
Failed to merge 1064762: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#1062926: marked as done (stdgpu: NMU diff for 64-bit time_t transition)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 16:37:50 +
with message-id 
and subject line Bug#1062926: fixed in stdgpu 1.3.0+git20220507.32e0517-5.2
has caused the Debian Bug report #1062926,
regarding stdgpu: NMU diff for 64-bit time_t transition
to be marked as done.

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

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


-- 
1062926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stdgpu
Version: 1.3.0+git20220507.32e0517-5
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
stdgpu as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for stdgpu
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru stdgpu-1.3.0+git20220507.32e0517/debian/changelog 
stdgpu-1.3.0+git20220507.32e0517/debian/changelog
--- stdgpu-1.3.0+git20220507.32e0517/debian/changelog   2023-07-01 
14:13:20.0 -0700
+++ stdgpu-1.3.0+git20220507.32e0517/debian/changelog   2024-02-03 
16:28:11.0 -0800
@@ -1,3 +1,14 @@
+stdgpu (1.3.0+git20220507.32e0517-5.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+  * Since this is already a custom soname set in debian/rules, adjust the
+soname as well to avoid any need for breaks/replaces.  This breaks
+compatibility on 64-bit archs as well, but with no reverse-dependencies
+in the archive, the impact is negligible.
+
+ -- Steve Langasek   Sun, 04 Feb 2024 00:28:11 +
+
 stdgpu (1.3.0+git20220507.32e0517-5) unstable; urgency=medium
 
   * Fix wrong alignment test to actually provoke wrong alignment
diff -Nru stdgpu-1.3.0+git20220507.32e0517/debian/control 
stdgpu-1.3.0+git20220507.32e0517/debian/control
--- stdgpu-1.3.0+git20220507.32e0517/debian/control 2023-07-01 
14:13:11.0 -0700
+++ stdgpu-1.3.0+git20220507.32e0517/debian/control 2024-02-03 
16:27:36.0 -0800
@@ -21,7 +21,7 @@
  agnostic and native algorithms that look like sequential CPU code but are
  executed in parallel on the GPU.
 
-Package: libstdgpu-openmp0d
+Package: libstdgpu-openmp0t64
 Architecture: any
 Multi-Arch: same
 Depends:
@@ -40,7 +40,7 @@
 Provides: libstdgpu-dev
 Depends:
  ${misc:Depends},
- libstdgpu-openmp0d (= ${binary:Version}),
+ libstdgpu-openmp0t64 (= ${binary:Version}),
  libthrust-dev,
 Description: ${source:Synopsis} (OpenMP development headers)
  ${source:Extended-Description}
diff -Nru stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0d.install 
stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0d.install
--- stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0d.install  
2023-07-01 14:13:11.0 -0700
+++ 

Bug#1064730: stdgpu: FTBFS: type_traits.h:736:1: error: expected type-specifier before ‘template’

[Gianfranco Costamagna]

On Tue, 16 Apr 2024 15:40:12 +0200 Timo =?utf-8?Q?R=C3=B6hling?= 
 wrote:

* Gianfranco Costamagna  [2024-04-16 09:06]:
>I agree with Cory, to me looks also a regression in thrust
>
>I'm trying some hacky patch, lets see
>
>Description: Reintroduce fallback lost in 
https://github.com/ROCm/rocThrust/commit/2b80e29803d60f01701a67bc57ef06dacfe8af8b
>Author: Gianfranco Costamagna 
>Last-Update: 2024-04-16
>
>--- rocthrust-5.7.1.orig/thrust/detail/type_traits.h
>+++ rocthrust-5.7.1/thrust/detail/type_traits.h
>@@ -731,6 +731,8 @@ using invoke_result_t =
> #else // 2017+
>   ::cuda::std::invoke_result_t;
> #endif
>+#else
>+  std::invoke_result_t;
> #endif
>
> template 
>
Thanks for the patch and upstream PR. If that does not pan out, I 
could split stdgpu into two separate (source) packages to have the 
openmp backend built against libthrust-dev. I prefer your solution, 
though.





I would say, we NMU now to unblock the amdgpu transition to time64_t, and then 
we can
split or do whatever you prefer... There is some rush to finish time64_t 
without regressing
the current set of packages...
(whenever possible of course!)

G.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064730: rocthrust: diff for NMU version 5.7.1-2.1

[Gianfranco Costamagna]

Control: tags 1064730 + patch
Control: tags 1064730 + pending

Dear maintainer,

I've prepared an NMU for rocthrust (versioned as 5.7.1-2.1) and
uploaded it.

Regards.

diff -Nru rocthrust-5.7.1/debian/changelog rocthrust-5.7.1/debian/changelog
--- rocthrust-5.7.1/debian/changelog2024-03-26 18:40:24.0 +0100
+++ rocthrust-5.7.1/debian/changelog2024-04-16 18:21:04.0 +0200
@@ -1,3 +1,11 @@
+rocthrust (5.7.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Reintroduce fallback in invoke_result with upstream proposed
+and acked patch (Closes: #1064730)
+
+ -- Gianfranco Costamagna   Tue, 16 Apr 2024 
18:21:04 +0200
+
 rocthrust (5.7.1-2) unstable; urgency=medium

   * Migrate to unstable
diff -Nru rocthrust-5.7.1/debian/patches/invoke_result-std.patch 
rocthrust-5.7.1/debian/patches/invoke_result-std.patch
--- rocthrust-5.7.1/debian/patches/invoke_result-std.patch  1970-01-01 
01:00:00.0 +0100
+++ rocthrust-5.7.1/debian/patches/invoke_result-std.patch  2024-04-16 
09:01:08.0 +0200
@@ -0,0 +1,17 @@
+Description: Reintroduce fallback lost in 
https://github.com/ROCm/rocThrust/commit/2b80e29803d60f01701a67bc57ef06dacfe8af8b
+Author: Gianfranco Costamagna 
+Forwarded: https://github.com/ROCm/rocThrust/pull/402
+Bug-Debian: https://bugs.debian.org/1064730
+Last-Update: 2024-04-16
+
+--- rocthrust-5.7.1.orig/thrust/detail/type_traits.h
 rocthrust-5.7.1/thrust/detail/type_traits.h
+@@ -731,6 +731,8 @@ using invoke_result_t =
+ #else // 2017+
+   ::cuda::std::invoke_result_t;
+ #endif
++#else
++  std::invoke_result_t;
+ #endif
+
+ template 


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066484: marked as done (tcpxtract: FTBFS: confy.c:494:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 16:25:11 +
with message-id 
and subject line Bug#1066484: fixed in tcpxtract 1.0.1-18
has caused the Debian Bug report #1066484,
regarding tcpxtract: FTBFS: confy.c:494:16: error: implicit declaration of 
function ‘yylex’ [-Werror=implicit-function-declaration]
to be marked as done.

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

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


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

Hi,

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

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

Relevant part (hopefully):
> gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"tcpxtract\" -DVERSION=\"1.0.1\" -DYYTEXT_POINTER=1 
> -DHAVE_LIBPCAP=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 -I.   -Wdate-time 
> -D_FORTIFY_SOURCE=2 -D_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection 
> -DDEFAULT_CONFIG_FILE=\"/etc/tcpxtract.conf\" -c -o extract.o extract.c
> confy.c: In function ‘yyparse’:
> confy.c:494:16: error: implicit declaration of function ‘yylex’ 
> [-Werror=implicit-function-declaration]
>   494 | # define YYLEX yylex ()
>   |^
> confy.c:950:16: note: in expansion of macro ‘YYLEX’
>   950 |   yychar = YYLEX;
>   |^
> confy.c:1188:9: error: implicit declaration of function ‘yyerror’; did you 
> mean ‘yyerrok’? [-Werror=implicit-function-declaration]
>  1188 | yyerror ("syntax error");
>   | ^~~
>   | yyerrok
> confy.y: At top level:
> confy.y:58:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>58 | yyerror(char *s)
>   | ^~~
> confl.l: In function ‘yylex’:
> confl.l:28:47: error: implicit declaration of function ‘strdup’ 
> [-Werror=implicit-function-declaration]
>28 | [0-9]+  {yylval.string = 
> strdup(yytext); return NUMBER;}
>   |   ^~
> confl.l:28:47: warning: incompatible implicit declaration of built-in 
> function ‘strdup’ [-Wbuiltin-declaration-mismatch]
> confl.l:29:18: warning: incompatible implicit declaration of built-in 
> function ‘strdup’ [-Wbuiltin-declaration-mismatch]
>29 | [a-zA-Z][a-zA-Z0-9]*{yylval.string = strdup(yytext); return WORD;}
>   |  ^
> confl.l:30:32: warning: incompatible implicit declaration of built-in 
> function ‘strdup’ [-Wbuiltin-declaration-mismatch]
>30 | [a-zA-Z0-9\\\?]+{yylval.string = strdup(yytext); 
> return SPECIFIER;}
>   | ^
> In file included from /usr/include/inttypes.h:25,
>  from /usr/include/pcap/pcap-inttypes.h:98,
>  from /usr/include/pcap/pcap.h:117,
>  from /usr/include/pcap.h:43,
>  from tcpxtract.c:25:
> /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> tcpxtract.c: In function ‘main’:
> tcpxtract.c:312:5: error: implicit declaration of function ‘yyparse’ 
> [-Werror=implicit-function-declaration]
>   312 | yyparse();
>   | ^~~
> tcpxtract.c:320:9: warning: ‘pcap_lookupdev’ is deprecated: use 
> 'pcap_findalldevs' and use the first device [-Wdeprecated-declarations]
>   320 | dev = pcap_lookupdev(errbuf);
>   | ^~~
> /usr/include/pcap/pcap.h:395:18: note: declared here
>   395 | PCAP_API char   *pcap_lookupdev(char *);
>   |  ^~
> tcpxtract.c:355:25: warning: format ‘%s’ expects argument of type ‘char *’, 
> but argument 3 has type ‘struct bpf_program’ [-Wformat=]

Processed: rocthrust: diff for NMU version 5.7.1-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1064730 + patch
Bug #1064730 [src:stdgpu] stdgpu: FTBFS: type_traits.h:736:1: error: expected 
type-specifier before ‘template’
Ignoring request to alter tags of bug #1064730 to the same tags previously set
> tags 1064730 + pending
Bug #1064730 [src:stdgpu] stdgpu: FTBFS: type_traits.h:736:1: error: expected 
type-specifier before ‘template’
Added tag(s) pending.

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

Bug#1068941: marked as done (src:mdevctl: unsatisfied build dependency in testing: librust-env-logger-0.10.0+default-dev)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 15:06:36 +
with message-id 
and subject line Bug#1068941: fixed in mdevctl 1.3.0-2
has caused the Debian Bug report #1068941,
regarding src:mdevctl: unsatisfied build dependency in testing: 
librust-env-logger-0.10.0+default-dev
to be marked as done.

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

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


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

Source: mdevctl
Version: 1.3.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mdevctl
Source-Version: 1.3.0-2
Done: Athos Ribeiro 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Apr 2024 10:59:16 -0300
Source: mdevctl
Built-For-Profiles: noudeb
Architecture: source
Version: 1.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Christian Ehrhardt 
Changed-By: Athos Ribeiro 
Closes: 1068941
Changes:
 mdevctl (1.3.0-2) unstable; urgency=medium
 .
   * d/control:
 - bump env_logger B-D version (Closes: #1068941)
 - bump Standards-Version to 4.7.0
Checksums-Sha1:
 d44020cc8baf564ac1e3d8fbc4ddc9c472e13d35 2291 mdevctl_1.3.0-2.dsc
 f46ec4d6a705a772132d9b7fc1b60f6877619a2b 4948 mdevctl_1.3.0-2.debian.tar.xz
 2ed8b7b5e17a1454c25060e561a17b5058c9846a 9023 mdevctl_1.3.0-2_source.buildinfo
Checksums-Sha256:
 440a7be7b379428fbe507d95b3e354f961f540c6f3b8273ee8ab67a59549c709 2291 
mdevctl_1.3.0-2.dsc
 5a725e22c2ecce8f9a86178bccf4df8769ad6f552a9db3dabe1f4581d16068b0 4948 
mdevctl_1.3.0-2.debian.tar.xz
 4473e1baae25d72442087a5e2bc9398227e0f3ffb27ab07de0c452ad2f045ad4 9023 
mdevctl_1.3.0-2_source.buildinfo
Files:
 543a78e1ac4f16cb02378228de39a2a9 2291 admin optional mdevctl_1.3.0-2.dsc
 5e3f533ad7a8da3bf694694592f125ed 4948 admin optional 
mdevctl_1.3.0-2.debian.tar.xz
 500ea5d2c4a02fb67c548b239897ae07 9023 admin optional 
mdevctl_1.3.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJQBAEBCgA6FiEEQ5iE5oYqQpwpDfY7AzxMonYCSDQFAmYejnIcHGF0aG9zLnJp
YmVpcm9AY2Fub25pY2FsLmNvbQAKCRADPEyidgJINP2BD/9wcpodL3X1vcDpFr6b
SknrGYJ42hLsmGtJCCj3Xfrh5Tgn8prWmKRyweRoZOdDEAWbrc/b56CAyKaaNDlf
uHPU19wuDatud4rVM1UsVTHzGQWeMhXcr2NQnKNg5fAQA0x1WuJNgKb0YWtRNMYB
6HSVkk9Af25HjRr9eVIKR+JYiee0roFOhhaEBUvbGoxQ+QKUGNQfv6Y6K9sPH9TP
g/S5ItV77uWgspN4q/83DqDku0Odd+gxxbHcQPPaheyOXlRIZU0WqIMAbreh9Srs
2kEcuRz6QQFuDiSQ1mJgmPrKAyLeUTgj+xbUMRrGX/lFkfKYEz42DJdy1j7mwPdX
KzhT8+sbX0wThCWlWF5AgvrDMFsvIJv7Y0tE4XQ0smmKPhC6SlrvwiFPSbirAs12
JDY57e79LSQ9FSWDlmcXQ7Uu3Sw1FCHqRPMffuFbqTHTPfLNdCEsQdgfXE6JXAlc
9jg3OHhzG+oZiMR87nSp+cXw2eyNig4ES0rLlMFLSdPAkDtLtBmIyWK6gkFc6acl
hHqPFs48EYGEvJGbYHk3ca7FWICSpwtDwOpjceFC1moCLRBJToPqi7Bz1CKQ9i84

Processed: affects

[Debian Bug Tracking System]

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

> affects 1069097 src:designate-dashboard
Bug #1069097 [openstack-dashboard] openstack-dashboard: postinst error makes 
designate-dashboard to FTBFS randomly
Added indication that 1069097 affects src:designate-dashboard
> thanks
Stopping processing here.

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

Bug#1068655: marked as done (lomiri-telephony-service FTBFS with abseil 20230802.1)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 14:35:11 +
with message-id 
and subject line Bug#1068655: fixed in lomiri-telephony-service 0.5.3-2
has caused the Debian Bug report #1068655,
regarding lomiri-telephony-service FTBFS with abseil 20230802.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.)


-- 
1068655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lomiri-telephony-service
Version: 0.5.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=lomiri-telephony-service=amd64=0.5.3-1%2Bb3=1712518065=0

...
/<>/libtelephonyservice/contactwatcher.cpp: In member function 
‘void ContactWatcher::updateAlias()’:
/<>/libtelephonyservice/contactwatcher.cpp:157:21: error: 
‘dgettext’ is not a member of ‘C’; did you mean ‘dgettext’?
  157 | setAlias(C::dgettext("telephony-service", "Private Number"));
  | ^~~~
In file included from 
/usr/include/x86_64-linux-gnu/c++/13/bits/messages_members.h:36,
 from /usr/include/c++/13/bits/locale_facets_nonio.h:2064,
 from /usr/include/c++/13/locale:43,
 from /usr/include/c++/13/iomanip:45,
 from /usr/include/absl/strings/internal/str_format/arg.h:23,
 from /usr/include/absl/strings/str_format.h:78,
 from /usr/include/absl/crc/crc32c.h:32,
 from /usr/include/absl/crc/internal/crc_cord_state.h:23,
 from /usr/include/absl/strings/cord.h:79,
 from 
/usr/include/absl/container/internal/hash_function_defaults.h:56,
 from /usr/include/absl/container/node_hash_set.h:42,
 from /usr/include/phonenumbers/phonenumberutil.h:33,
 from /<>/libtelephonyservice/phoneutils.h:27,
 from 
/<>/libtelephonyservice/contactwatcher.cpp:25:
/usr/include/libintl.h:44:14: note: ‘dgettext’ declared here
   44 | extern char *dgettext (const char *__domainname, const char *__msgid)
  |  ^~~~
/<>/libtelephonyservice/contactwatcher.cpp:159:21: error: 
‘dgettext’ is not a member of ‘C’; did you mean ‘dgettext’?
  159 | setAlias(C::dgettext("telephony-service", "Unknown Number"));
  | ^~~~
/usr/include/libintl.h:44:14: note: ‘dgettext’ declared here
   44 | extern char *dgettext (const char *__domainname, const char *__msgid)
  |  ^~~~
...
--- End Message ---
--- Begin Message ---
Source: lomiri-telephony-service
Source-Version: 0.5.3-2
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
lomiri-telephony-service, 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.
Mike Gabriel  (supplier of updated 
lomiri-telephony-service package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 16 Apr 2024 15:53:48 +0200
Source: lomiri-telephony-service
Architecture: source
Version: 0.5.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team 
Changed-By: Mike Gabriel 
Closes: 1068655
Changes:
 lomiri-telephony-service (0.5.3-2) unstable; urgency=medium
 .
   * debian/watch:
 + Update file for recent GitLab changes of the tags overview page.
   * debian/patches:
 + Add 1002_CMake-fix-dependency.patch. Fix unhandled dependency on
   generated .h file.
 + Add 1001_gettext-is-not-a-member-of-C.patch. Include libintl.h into
   :: namespace rather than into C::. Resolves conflict with abseil >=
   20230802.1. (Closes: #1068655).
Checksums-Sha1:
 ec2ba2e31a958406279322c8ecde680b81a0d107 2979 
lomiri-telephony-service_0.5.3-2.dsc
 0ea8afb2c9981cf1d44d282f8734ea9d514a5295 19812 
lomiri-telephony-service_0.5.3-2.debian.tar.xz
 b3067b42b7edba68748006718008e63aff5a8b6e 19923 
lomiri-telephony-service_0.5.3-2_source.buildinfo
Checksums-Sha256:
 f58324eb9be29c6a4e74b5d6e21c02803246584827b1aa922a8674f21c0ae764 2979 
lomiri-telephony-service_0.5.3-2.dsc
 

Bug#1068070: marked as done (Hardcoded dependency on liblcmaps0)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 14:34:56 +
with message-id 
and subject line Bug#1068070: fixed in lcmaps-plugins-voms 1.7.1-2
has caused the Debian Bug report #1068070,
regarding Hardcoded dependency on liblcmaps0
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.)


-- 
1068070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
source: lcmaps-plugins-voms
version: 1.7.1-1
severity: serious

During the 64 bit time_t transition the package name liblcmaps0 was
changed to liblcmaps0t64. The old name is still provided by the new
package for architectures where this transition did not cause an ABI
break, but not for architectures like armel and armhf, where these
hardcoded dependency on the old package name are now not satisfiable.

Please change these to use either the new name or to depend on either
the old or the new name (liblcmaps0 | liblcmaps0t64).

Package: lcmaps-plugins-voms
Depends: ${shlibs:Depends}, ${misc:Depends},
 liblcmaps0 (>= 1.5.0)

Mattias



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: lcmaps-plugins-voms
Source-Version: 1.7.1-2
Done: Dennis van Dok 

We believe that the bug you reported is fixed in the latest version of
lcmaps-plugins-voms, 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.
Dennis van Dok  (supplier of updated lcmaps-plugins-voms 
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 16:41:58 +0200
Source: lcmaps-plugins-voms
Architecture: source
Version: 1.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Dennis van Dok 
Changed-By: Dennis van Dok 
Closes: 1068070
Changes:
 lcmaps-plugins-voms (1.7.1-2) unstable; urgency=medium
 .
   * Update dependency on liblcmaps0 to deal with 64 bit time_t
 transition. (Closes: #1068070)
Checksums-Sha1:
 40d0ea4e0732312c83fc69638dc68b96dfa9dc69 2179 lcmaps-plugins-voms_1.7.1-2.dsc
 464f3e208e2d4b0969aa805caf28e16b7c1dfdb1 3264 
lcmaps-plugins-voms_1.7.1-2.debian.tar.xz
 a555a933d52bbf2bb9e1bb9400b1b8850a610e7b 7064 
lcmaps-plugins-voms_1.7.1-2_source.buildinfo
Checksums-Sha256:
 5363d251d42d9ba875b8afdf26a9b65285eed9bda690e9ce5b064188eb34221a 2179 
lcmaps-plugins-voms_1.7.1-2.dsc
 5bfe4f4d6346ada105089d90c9914bdf5a90710d182ad1c95173f5b24d6bb387 3264 
lcmaps-plugins-voms_1.7.1-2.debian.tar.xz
 55c63c03edcfcda69166b19847762ebc2d0b536ae3423a895ee5b8126fab6f6d 7064 
lcmaps-plugins-voms_1.7.1-2_source.buildinfo
Files:
 3291d9fd5c6d4fcd5cf3857b469b 2179 libs optional 
lcmaps-plugins-voms_1.7.1-2.dsc
 c8217d6cedbff3ce5db6b5a725f78f4b 3264 libs optional 
lcmaps-plugins-voms_1.7.1-2.debian.tar.xz
 bfb435fe3fb0624c408e36c8abff3463 7064 libs optional 
lcmaps-plugins-voms_1.7.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWGm4u3eUE64rvBHj3/rYGXYX7xkFAmYeggcACgkQ3/rYGXYX
7xmx0w/8D8fKj91egwsguPefIhs3JoaYbbLt5BnHCkT9i+AGEKZgmAeLB/VQ/L7r
5oOa59bkC8mpzuZJpWzVgoNor95aPUrqrWw3xXZo6Mltu8u95+dXfpLlhsmkYgco
Xo02itkl78A75osP+O1p6f2wr68JFpBSgWx5UMxhxy7aUTMllFzx+yb+Gla7fSWo
TYjXvF+NCO2oz5k/H7iIQ+WkM+kHEzVuGc63lMrtbiIysvRe0H9QF6o+8TZYHcC8
oYa8pheTouz/hSUL1fKOyUXCRFf5I0Hvy/7vOz0Qb1GC9MUQviThBtquqDQIFpMJ
Ncu2EHY6QDpGJYVMNVxfPLXgaARZJtul0yg/Q/6+qqHHFQj4pVuBIFkQgLCK3GLm
t6AMk+vLtd6ynKK66B7E4BvGvJArI4vcwgngxbqUsCHqCdpLZ5srdlMIkYn95liF
Mq6Wb4ORnKgR9azPp9NsfLrSrA8FHyFhv3LxegbO7SCasecL6rgLog+9l/pTy5Se
RxrcDpHV42MfE6zP8qjKnAnLRhKd32wCGJ3R4I0FIDwcgODn+vxNAy70ylfcKzGx
boTUe3CH7Fp/1scJ9Ffnm/gSKw6bTMvvS4s8suUDDRExKa/HcIj7DNAYSIOkJdtI
n6ZY7gw+Ox4GozIQXiylW6XmlDZ8zcneTieC9pTVfg7b6t6gIJI=
=fOHf
-END PGP SIGNATURE-



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

Processed: Bug#1068655 marked as pending in lomiri-telephony-service

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068655 [src:lomiri-telephony-service] lomiri-telephony-service FTBFS with 
abseil 20230802.1
Added tag(s) pending.

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

Bug#1068655: marked as pending in lomiri-telephony-service

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #1068655 in lomiri-telephony-service 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/ubports-team/lomiri-telephony-service/-/commit/c90e6ef8e1558ff5a7ce48cd734628b495f6f9e5


debian/patches: Add 1001_gettext-is-not-a-member-of-C.patch. Include libintl.h 
into :: namespace rather than into C::. Resolves conflict with abseil >= 
20230802.1. (Closes: #1068655).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068655

Bug#1064730: stdgpu: FTBFS: type_traits.h:736:1: error: expected type-specifier before ‘template’

[Timo Röhling]

* Gianfranco Costamagna  [2024-04-16 09:06]:

I agree with Cory, to me looks also a regression in thrust

I'm trying some hacky patch, lets see

Description: Reintroduce fallback lost in 
https://github.com/ROCm/rocThrust/commit/2b80e29803d60f01701a67bc57ef06dacfe8af8b
Author: Gianfranco Costamagna 
Last-Update: 2024-04-16

--- rocthrust-5.7.1.orig/thrust/detail/type_traits.h
+++ rocthrust-5.7.1/thrust/detail/type_traits.h
@@ -731,6 +731,8 @@ using invoke_result_t =
#else // 2017+
  ::cuda::std::invoke_result_t;
#endif
+#else
+  std::invoke_result_t;
#endif

template 

Thanks for the patch and upstream PR. If that does not pan out, I 
could split stdgpu into two separate (source) packages to have the 
openmp backend built against libthrust-dev. I prefer your solution, 
though.



Cheers
Timo



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


signature.asc
Description: PGP signature

Processed: RM: rust-gtk-layer-shell-sys -- ROM; depends on obsolete library

[Debian Bug Tracking System]

Processing control commands:

> block 1064374 by -1
Bug #1064374 [src:rust-gtk-layer-shell-sys] rust-gtk-layer-shell-sys: Depends 
on obsolete rust-gtk
1064374 was not blocked by any bugs.
1064374 was blocking: 1064375
Added blocking bug(s) of 1064374: 1069111

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

Processed: Bug#1060931 marked as pending in python-babel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1060931 [src:python-babel] python-babel: FTBFS: E   
FileNotFoundError: [Errno 2] No such file or directory: 
'/<>/babel/locale-data/sr_ME.dat'
Added tag(s) pending.

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

Bug#1060931: marked as pending in python-babel

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #1060931 in python-babel 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/python-babel/-/commit/774f3ab8251890e820e4387abe6457ad1ceaadbc


Add upstream patch to adjust data/tests in accordance with cldr 44 (Closes: 
#1060931)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1060931

Bug#1064730: stdgpu: FTBFS: type_traits.h:736:1: error: expected type-specifier before ‘template’

[Gianfranco Costamagna]

control: tags -1 patch
control: forwarded -1 https://github.com/ROCm/rocThrust/pull/402

Looks like the build went fine
G.
On Tue, 16 Apr 2024 09:06:27 +0200 Gianfranco Costamagna 
 wrote:

Hello,
On Mon, 15 Apr 2024 16:31:39 -0600 Cordell Bloor  wrote:
> Hi Timo,
> 
> On Sat, 2 Mar 2024 09:21:43 +0100 Timo =?utf-8?Q?R=C3=B6hling?= 
>  wrote:
> 
>  >

>  > On Sun, 25 Feb 2024 20:28:53 +0100 Lucas Nussbaum 
>  > wrote:
>  > > > /usr/include/thrust/detail/type_traits.h:736:1: error: expected
>  > > > type-specifier before ‘template’
>  >
>  > This bug is caused by a #ifdef cascade for different
>  > THRUST_DEVICE_SYSTEM values, which sadly no longer works with
>  > THRUST_DEVICE_SYSTEM_OMP. This makes it effectively impossible to
>  > build the HIP backend and the OpenMP backend from the same source.
> 
> Am I understanding correctly that this was broken in a rocthrust update? 
> Should this be treated as a rocthrust bug? [1]
> 
> Sincerely,

> Cory Bloor
> 



I agree with Cory, to me looks also a regression in thrust

I'm trying some hacky patch, lets see

Description: Reintroduce fallback lost in 
https://github.com/ROCm/rocThrust/commit/2b80e29803d60f01701a67bc57ef06dacfe8af8b
Author: Gianfranco Costamagna 
Last-Update: 2024-04-16

--- rocthrust-5.7.1.orig/thrust/detail/type_traits.h
+++ rocthrust-5.7.1/thrust/detail/type_traits.h
@@ -731,6 +731,8 @@ using invoke_result_t =
  #else // 2017+
::cuda::std::invoke_result_t;
  #endif
+#else
+  std::invoke_result_t;
  #endif

  template 

> [1]: https://bugs.debian.org/1064730
> 
> 
> 


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Re: stdgpu: FTBFS: type_traits.h:736:1: error: expected type-specifier before ‘template’

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1064730 [src:stdgpu] stdgpu: FTBFS: type_traits.h:736:1: error: expected 
type-specifier before ‘template’
Added tag(s) patch.
> forwarded -1 https://github.com/ROCm/rocThrust/pull/402
Bug #1064730 [src:stdgpu] stdgpu: FTBFS: type_traits.h:736:1: error: expected 
type-specifier before ‘template’
Set Bug forwarded-to-address to 'https://github.com/ROCm/rocThrust/pull/402'.

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

Bug#1052111: gnome-shell-extension-weather for GNOME Shell 46/45 fork: https://github.com/penguin-teal/gnome-openweather

[Technologijų tinklas]

There is a gnome-shell-extension-weather fork with GNOME Shell 46/45
support: https://github.com/penguin-teal/gnome-openweather

I think Debian should use this repo
-- 
Prekyba kompiuteriais ir programine įranga - http://tinklas.eu/prekyba
El. paštas: tink...@tinklas.eu
Naudokite laisvą Linux operacinę sistemą savo kompiuteryje - http://baltix.eu
Mantas Kriaučiūnas
Use Baltix GNU/Linux OS ! http://launchpad.net/baltix

Bug#1068073: marked as done (Hardcoded dependency on liblcmaps0)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 12:54:09 +
with message-id 
and subject line Bug#1068073: fixed in lcmaps-plugins-verify-proxy 1.5.10-3
has caused the Debian Bug report #1068073,
regarding Hardcoded dependency on liblcmaps0
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.)


-- 
1068073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
source: lcmaps-plugins-verify-proxy
version: 1.5.10-2
severity: serious

During the 64 bit time_t transition the package name liblcmaps0 was
changed to liblcmaps0t64. The old name is still provided by the new
package for architectures where this transition did not cause an ABI
break, but not for architectures like armel and armhf, where these
hardcoded dependency on the old package name are now not satisfiable.

Please change these to use either the new name or to depend on either
the old or the new name (liblcmaps0 | liblcmaps0t64).

Package: lcmaps-plugins-verify-proxy
Depends: ${shlibs:Depends}, ${misc:Depends}, liblcmaps0

Mattias



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: lcmaps-plugins-verify-proxy
Source-Version: 1.5.10-3
Done: Dennis van Dok 

We believe that the bug you reported is fixed in the latest version of
lcmaps-plugins-verify-proxy, 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.
Dennis van Dok  (supplier of updated 
lcmaps-plugins-verify-proxy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Apr 2024 08:34:19 +0200
Source: lcmaps-plugins-verify-proxy
Architecture: source
Version: 1.5.10-3
Distribution: unstable
Urgency: medium
Maintainer: Dennis van Dok 
Changed-By: Dennis van Dok 
Closes: 1068073
Changes:
 lcmaps-plugins-verify-proxy (1.5.10-3) unstable; urgency=medium
 .
   * Update to address 64 bit time_t transition (Closes: 1068073)
Checksums-Sha1:
 da3ac3a7d7c303ad833369a1ca065ccf4c24ac48 2216 
lcmaps-plugins-verify-proxy_1.5.10-3.dsc
 ac85fb14dc233b6a1d0d7b15f617a5f77cb256ac 4220 
lcmaps-plugins-verify-proxy_1.5.10-3.debian.tar.xz
 1bf3ac098c93a57d6252afedea4c4601d7e37d96 6192 
lcmaps-plugins-verify-proxy_1.5.10-3_source.buildinfo
Checksums-Sha256:
 3ed511eaa903ccc122899d2b71efd5cfed2cb67da4344aa0c815c88168c9ca5c 2216 
lcmaps-plugins-verify-proxy_1.5.10-3.dsc
 4c2c137bd648328012a3d2c0bbaf736af16429d64ae3b4809cef16234f302823 4220 
lcmaps-plugins-verify-proxy_1.5.10-3.debian.tar.xz
 4cb35d9792aa910cb4480d12a472f827287d4c652c8420e57b2f72c12c8e415b 6192 
lcmaps-plugins-verify-proxy_1.5.10-3_source.buildinfo
Files:
 ebe3824bbe0dab7bd428ae7cb3b09964 2216 libs optional 
lcmaps-plugins-verify-proxy_1.5.10-3.dsc
 44f1c05005d739c3219f803a4e5b4c9c 4220 libs optional 
lcmaps-plugins-verify-proxy_1.5.10-3.debian.tar.xz
 9413babed3589a51920a9148dea398c1 6192 libs optional 
lcmaps-plugins-verify-proxy_1.5.10-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWGm4u3eUE64rvBHj3/rYGXYX7xkFAmYeb0UACgkQ3/rYGXYX
7xk3hRAAswYOhGY7qhFHO+70u/tzmtzU4yG4sa8FFe4plKACiLwhWMtUhA9vDp/d
iBwaaGYAN6Ph6s9sBdS4ynUykEByhh9GkfvDj3UY5yAUjUYtPwf7iMtqYNFmI0gm
ZNzJ6e++plUm0Uhgp4SGJYBgMyQmCHmsuEVW+u4ZUxzrCvPA0YmAiQgAt1QsvYn2
XJ9riPgxCQ/tVQiLg/bzJObOSSO8cT/T4GJdLal1S4DJvrJRg2XCPAiL7ONV46z+
Sm0X9+obqEcBdmbm6lnmX2KkY+KVtwrsYqKpJWWHDnph45J6x/B+esrfXqn22w6W
h6LwTw5VHhHO/07FNcxXgMknBEbT6SRlath/ippgM9IKoCMjoD+34uSEVOjeqnBh
ochRIDrplAhJcXL2lBej6AbtC5pm9uhXB+F+XMfUmgOiD+4pLCqTCcGGyWG/dXdy
JZBYGGDAZ4bqLkD4uvo0N5I+oVtjMy7Ddq645/P8ZiKCvYolS2/bvRhTixncxsb0
Tv6DuXWj7+fDwueWutFAaeALHoLR3VhuKzPTTw6wPXB8DcIsnghm0YF/txx4aUVk
6279oqYemlnUVO9YRCgida8viJpRAJ5j5zpiTa2HYeB5ee9mC5M2saWTBxt/mMds
30MwK8BuwrrBJrhLXcNv2mhL0ZCCv9ZQqiQPXKOeB43qjmJoE1w=
=Lr4D
-END PGP SIGNATURE-



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

Bug#1069106: openmpi: 32 bit pmix_init:startup:internal-failure: help-pmix-runtime.txt: No such file

[Drew Parsons]

Source: openmpi
Version: 4.1.6-9
Severity: serious
Justification: ftbfs
Control: affects -1 src:fenics-dolfinx src:petsc

openmpi 4.1.6-9 is failing its own tests on 32-bit systems,
presumeably after they were configuring to use a local copy of pmix
instead of libpmix-dev.

For instance on i386
https://ci.debian.net/data/autopkgtest/unstable/i386/o/openmpi/45463906/log.gz
the error message is

 69s autopkgtest [12:19:13]: test compile_run_mpicc: [---
 69s --
 69s Sorry!  You were supposed to get help about:
 69s pmix_init:startup:internal-failure
 69s But I couldn't open the help file:
 69s /usr/share/pmix/help-pmix-runtime.txt: No such file or directory.  
Sorry!
 69s --
 69s [ci-107-5e0ffbcf:02362] PMIX ERROR: NOT-FOUND in file 
../../../../../../../../opal/mca/pmix/pmix3x/pmix/src/server/pmix_server.c at 
line 237
 

The same error affects builds and debci testing of client packages on
the 32 bit architectures, e.g. petsc, dolfinx

Processed: openmpi: 32 bit pmix_init:startup:internal-failure: help-pmix-runtime.txt: No such file

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:fenics-dolfinx src:petsc
Bug #1069106 [src:openmpi] openmpi: 32 bit pmix_init:startup:internal-failure: 
help-pmix-runtime.txt: No such file
Added indication that 1069106 affects src:fenics-dolfinx and src:petsc

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

Bug#1069101: libdbd-oracle-perl: requires rebuild for time_t transition

[Sebastian Ramacher]

Source: libdbd-oracle-perl
Version: 1.83-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

libdbd-oracle-perl depends on libaio1 which is involved in the time_t
transition and needs to be rebuilt. Please upload builds against the new
package.

Cheers
-- 
Sebastian Ramacher

Processed: block 1068942 by 1069098

[Debian Bug Tracking System]

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

> block 1068942 by 1069098
Bug #1068942 [src:oscar4] src:oscar4: unsatisfied build dependency in testing: 
emboss-data
1068942 was not blocked by any bugs.
1068942 was not blocking any bugs.
Added blocking bug(s) of 1068942: 1069098
> thanks
Stopping processing here.

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

Bug#1069097: openstack-dashboard: postinst error makes designate-dashboard to FTBFS randomly

[Santiago Vila]

Package: openstack-dashboard
Version: 3:24.0.0-2
Affects: src:designate-dashboard
Severity: serious
Justification: Breaks other packages

Dear maintainer:

During an incremental rebuild of all packages in trixie, package 
"designate-dashboard"
failed to build due to a postinst error in openstack-dashboard:


[...]
2717 static files copied to '/var/lib/openstack-dashboard/static'.
/usr/lib/python3/dist-packages/django/conf/__init__.py:267: 
RemovedInDjango50Warning: The USE_L10N setting is deprecat
ed. Starting with Django 5.0, localized formatting of data will always be 
enabled. For example Django will display num
bers and dates using the format of the current locale.
  warnings.warn(USE_L10N_DEPRECATED_MSG, RemovedInDjango50Warning)
/usr/lib/python3/dist-packages/debreach/__init__.py:6: DeprecationWarning: 
distutils Version classes are deprecated. U
se packaging.version instead.
  version_info = version.StrictVersion(__version__).version
CommandError: An error occurred during rendering serial_console.html: Syntax 
error: Found 'inline-blo' but expected one of ADD, ALPHA_FUNCTION, 
BANG_IMPORTANT, BAREWORD, COLOR, DOUBLE_QUOTE, FNCT, IF_FUNCTION, INTERP_START, 
LITERAL_FUNCTION, LPAR, NOT, NUM, SIGN, SINGLE_QUOTE, URL_FUNCTION, VAR
Compressing... dpkg: error processing package openstack-dashboard (--configure):
 installed openstack-dashboard package post-installation script subprocess 
returned error exit status 1
dpkg: dependency problems prevent configuration of 
sbuild-build-depends-main-dummy:
 sbuild-build-depends-main-dummy depends on openstack-dashboard; however:
  Package openstack-dashboard is not configured yet.

dpkg: error processing package sbuild-build-depends-main-dummy (--configure):
 dependency problems - leaving unconfigured
Processing triggers for ca-certificates (20240203) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Errors were encountered while processing:
 openstack-dashboard
 sbuild-build-depends-main-dummy
E: Sub-process /usr/bin/dpkg returned an error code (1)
apt-get failed.


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log (for designate-dashboard) is available here:

https://people.debian.org/~sanvila/build-logs/202404/

Note also how there is a gazillion of error messages like this:


Found another file with the destination path 
'horizon/lib/angular_schema_form/i18n/angular-locale_az-cyrl-az.js'. It will be 
ignored since only the first encountered file is collected. If this is not what 
you want, make sure every static file has a unique path.


That's apparently a django-related issue:

https://stackoverflow.com/questions/35571256/found-another-file-with-the-destination-path-where-is-that-other-file

which I would hope can be fixed as well (maybe it's part of the problem, maybe 
not,
I don't know).


About the archive rebuild: The build was made on virtual machines
of type m6a.large from AWS, using sbuild and a reduced chroot
with only build-essential packages.

I can't provide a "recipe" to reproduce the bug because it happens randomly,
but I expect the above error messages and the full build log will help to
determine the cause.

If required, I could provide ssh access to a virtual machine where
this random build failure happens, but I strongly suggest that
the build log is analyzed first to determine how it could happen.

Thanks.

Bug#1066228: xjdic: FTBFS: implicit declaration of functions

[Ludovic Drolez]

On Wed, Mar 27, 2024 at 11:12:09AM +0100, Bastian Germann wrote:
> Please find a patch included.

Thanks ! Will upload this soon.

Ludo

--
https://drolez.com/blog/   - Music and Tech Blog
https://palmopensource.com - Raspberry, retro and solar tinkering

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

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2024 08:51:09 +
with message-id 
and subject line Bug#1066732: fixed in metpy 1.6.2+ds-1
has caused the Debian Bug report #1066732,
regarding metpy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:305: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_metpy 
>  
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/metpy
> copying src/metpy/__init__.py -> build/lib/metpy
> copying src/metpy/pandas.py -> build/lib/metpy
> copying src/metpy/future.py -> build/lib/metpy
> copying src/metpy/package_tools.py -> build/lib/metpy
> copying src/metpy/deprecation.py -> build/lib/metpy
> copying src/metpy/_version.py -> build/lib/metpy
> copying src/metpy/testing.py -> build/lib/metpy
> copying src/metpy/_warnings.py -> build/lib/metpy
> copying src/metpy/units.py -> build/lib/metpy
> copying src/metpy/xarray.py -> build/lib/metpy
> copying src/metpy/cbook.py -> build/lib/metpy
> creating build/lib/metpy/constants
> copying src/metpy/constants/__init__.py -> build/lib/metpy/constants
> copying src/metpy/constants/nounit.py -> build/lib/metpy/constants
> copying src/metpy/constants/default.py -> build/lib/metpy/constants
> creating build/lib/metpy/plots
> copying src/metpy/plots/__init__.py -> build/lib/metpy/plots
> copying src/metpy/plots/_util.py -> build/lib/metpy/plots
> copying src/metpy/plots/cartopy_utils.py -> build/lib/metpy/plots
> copying src/metpy/plots/patheffects.py -> build/lib/metpy/plots
> copying src/metpy/plots/wx_symbols.py -> build/lib/metpy/plots
> copying src/metpy/plots/declarative.py -> build/lib/metpy/plots
> copying src/metpy/plots/mapping.py -> build/lib/metpy/plots
> copying src/metpy/plots/plot_areas.py -> build/lib/metpy/plots
> copying src/metpy/plots/skewt.py -> build/lib/metpy/plots
> copying src/metpy/plots/ctables.py -> build/lib/metpy/plots
> copying src/metpy/plots/_mpl.py -> build/lib/metpy/plots
> copying src/metpy/plots/station_plot.py -> build/lib/metpy/plots
> creating build/lib/metpy/io
> copying src/metpy/io/__init__.py -> build/lib/metpy/io
> copying src/metpy/io/_tools.py -> build/lib/metpy/io
> copying src/metpy/io/gempak.py -> build/lib/metpy/io
> copying src/metpy/io/text.py -> build/lib/metpy/io
> copying src/metpy/io/station_data.py -> build/lib/metpy/io
> copying src/metpy/io/metar.py -> build/lib/metpy/io
> copying src/metpy/io/gini.py -> build/lib/metpy/io
> copying src/metpy/io/nexrad.py -> build/lib/metpy/io
> creating build/lib/metpy/interpolate
> copying src/metpy/interpolate/__init__.py -> build/lib/metpy/interpolate
> copying src/metpy/interpolate/tools.py -> build/lib/metpy/interpolate
> copying src/metpy/interpolate/slices.py -> build/lib/metpy/interpolate
> copying src/metpy/interpolate/grid.py -> build/lib/metpy/interpolate
> copying src/metpy/interpolate/points.py -> build/lib/metpy/interpolate
> copying src/metpy/interpolate/geometry.py -> build/lib/metpy/interpolate
> copying src/metpy/interpolate/one_dimension.py -> build/lib/metpy/interpolate
> creating build/lib/metpy/calc
> copying src/metpy/calc/basic.py -> build/lib/metpy/calc
> copying src/metpy/calc/__init__.py -> build/lib/metpy/calc
> copying src/metpy/calc/tools.py -> build/lib/metpy/calc
> copying src/metpy/calc/cross_sections.py -> build/lib/metpy/calc
> copying src/metpy/calc/kinematics.py -> build/lib/metpy/calc
> copying src/metpy/calc/exceptions.py -> build/lib/metpy/calc
> copying src/metpy/calc/indices.py -> build/lib/metpy/calc
> copying src/metpy/calc/turbulence.py -> build/lib/metpy/calc
> copying src/metpy/calc/thermo.py -> build/lib/metpy/calc
> 

Bug#1069088: libvdeplug-slirp - dependencies unsatisfiable on 32-bit non-i386 architectures.

[Peter Green]

Package: libvdeplug-slirp
Version: 0.1.0-2
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, libvdeplug-slirp
still depends on the pre-time64 libraries libvdeplug2 and
libvdeslirp0. It also depends on libvdeplug2t64. As a result
it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
architectures).

Ubuntu has already fixed this issue by removing the hardcoded
dependencies and adding code to debian/rules to calculate
a correct libvdeplug dependency.

http://launchpadlibrarian.net/721384619/vdeplug-slirp_0.1.0-2build1_0.1.0-2ubuntu1.diff.gz

Bug#1069059: cockpit update from DSA-5655-1 without binary builds (build failures)

[Salvatore Bonaccorso]

Hi Martin,

On Tue, Apr 16, 2024 at 09:26:02AM +0200, Martin Pitt wrote:
> Control: tag -1 upstream fixed-upstream patch
> Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/19790
> 
> Hello Salvatore and Santiago,
> 
> Salvatore Bonaccorso [2024-04-15 19:28 +0200]:
> > The update for cockpit in DSA 5655-1 had problems with the
> > test-sshbridge test, causing FTBFS:
> >
> > >From the tail of the test failure:
> >
> > # cockpit-protocol-DEBUG: test-ssh: output queue empty
> >
> > (cockpit-ssh:3731): cockpit-ssh-WARNING **: 20:51:17.702: 
> > (src/ssh/cockpitsshrelay.c:1423):cockpit_ssh_connect: runtime check failed: 
> > (ssh_options_set (data->session, SSH_OPTIONS_HOST, host) == 0)
> >
> > (cockpit-ssh:3731): cockpit-ssh-WARNING **: 20:51:17.702: 
> > (src/ssh/cockpitsshrelay.c:1424):cockpit_ssh_connect: runtime check failed: 
> > (ssh_options_parse_config (data->session, NULL) == 0)
> > # cockpit-protocol-DEBUG: test-ssh: reading input 1
> > # cockpit-protocol-DEBUG: test-ssh: received a 82 byte payload
> > # cockpit-protocol-DEBUG: test-ssh: want more data
> > **
> > cockpit-ssh:ERROR:src/ssh/test-sshbridge.c:560:wait_until_transport_init: 
> > assertion failed (json_object_get_string_member (init, "command") == 
> > "init"): ("authorize" == "init")
> > Bail out! 
> > cockpit-ssh:ERROR:src/ssh/test-sshbridge.c:560:wait_until_transport_init: 
> > assertion failed (json_object_get_string_member (init, "command") == 
> > "init"): ("authorize" == "init")
> > cockpit-ssh-Message: 20:51:17.704: cockpit-ssh some_host: -1 couldn't 
> > connect: Hostname required 'some_host' '22'
> > cockpit-ssh-Message: 20:51:17.704: couldn't write control message: Broken 
> > pipe
> > cockpit-ssh-Message: 20:51:17.704: couldn't write authorize message: 
> > Inappropriate ioctl for device
> > FAIL test-sshbridge (exit status: 134)
> 
> Argh, I can reproduce. The test passes with the previous
> http://snapshot.debian.org/package/libssh/0.10.5-3/ but fails with current 
> 0.10.6-0+deb12u1.
> 
> The reason is annoyingly mundane, and already got fixed upstream half a year 
> ago:
> https://github.com/cockpit-project/cockpit/commit/518d36c3492020525
> 
> I prepared a package update with that fix cherry-picked. See attached debdiff.
> It builds fine in a clean bookworm container now.
> But I don't know how exactly to target and upload this: to bookworm-security 
> or
> -updates? It's a follow-up for a previous security update to make that 
> actually
> work, but not a security update in itself.

Technically speaking, as the issue is present already before the DSA
release, you are right and the proposed update way would have been the
way to go. *But* we have a released security-update wich de-facto does
not reach the users right now, so I propose to release the regression
fix trough a security and make it a DSA regression announce.

Can you please upload to security-master?

Regards,
Salvatore

Bug#1069064: util-linux-extra: insufficient Replaces for util-linux due to /usr-move

[Chris Hofstaedtler]

Hi Helmut,

On Mon, Apr 15, 2024 at 08:58:42PM +0200, Helmut Grohne wrote:
> I think I mentioned this on IRC already and you intended to revert, but
> nothing happened, so lets turn this into a bug for tracking purposes at
> least.

Indeed, I forgot to follow up afterwards. Thanks for keeping track!

> util-linux-extra gained the utils ctrlaltdel, [..] In
> util-linux-extra, these now reside below /usr/sbin [..]

> I think we have three ways to address this:

>  1. Revert the move and retry after trixie. I think you favoured this?
>  2. Upgrade Breaks to Conflicts and issue a temporary protective
> diversion from u-l-e.preinst to u-l-e.postinst. In theory, apt can
> first unpack u-l, then unpack u-l-e and then configure both, so
> there is a safe solution. However, there is a risk that apt could
> decide to temporarily remove u-l and that would be really bad.
>  3. Keep Breaks and issue temporary diversions to be removed in forky's
> u-l-e.postinst.
>
> Please let me know your choice and I can do a patch.

I think half of 2) exists now, but Conflicts: util-linux will
probably end badly as you note. I'd welcome a patch implementing 3).

Initially I favored 1), but then u-l will never make progress on
moving the non-essential files.

Thanks!

Chris

Processed: Re: Bug#1069059: cockpit update from DSA-5655-1 without binary builds (build failures)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 upstream fixed-upstream patch
Bug #1069059 [src:cockpit] cockpit update from DSA-5655-1 without binary builds 
(build failures)
Added tag(s) upstream, fixed-upstream, and patch.
> forwarded -1 https://github.com/cockpit-project/cockpit/pull/19790
Bug #1069059 [src:cockpit] cockpit update from DSA-5655-1 without binary builds 
(build failures)
Set Bug forwarded-to-address to 
'https://github.com/cockpit-project/cockpit/pull/19790'.

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

Bug#1069059: cockpit update from DSA-5655-1 without binary builds (build failures)

[Martin Pitt]

Control: tag -1 upstream fixed-upstream patch
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/19790

Hello Salvatore and Santiago,

Salvatore Bonaccorso [2024-04-15 19:28 +0200]:
> The update for cockpit in DSA 5655-1 had problems with the
> test-sshbridge test, causing FTBFS:
>
> >From the tail of the test failure:
>
> # cockpit-protocol-DEBUG: test-ssh: output queue empty
>
> (cockpit-ssh:3731): cockpit-ssh-WARNING **: 20:51:17.702: 
> (src/ssh/cockpitsshrelay.c:1423):cockpit_ssh_connect: runtime check failed: 
> (ssh_options_set (data->session, SSH_OPTIONS_HOST, host) == 0)
>
> (cockpit-ssh:3731): cockpit-ssh-WARNING **: 20:51:17.702: 
> (src/ssh/cockpitsshrelay.c:1424):cockpit_ssh_connect: runtime check failed: 
> (ssh_options_parse_config (data->session, NULL) == 0)
> # cockpit-protocol-DEBUG: test-ssh: reading input 1
> # cockpit-protocol-DEBUG: test-ssh: received a 82 byte payload
> # cockpit-protocol-DEBUG: test-ssh: want more data
> **
> cockpit-ssh:ERROR:src/ssh/test-sshbridge.c:560:wait_until_transport_init: 
> assertion failed (json_object_get_string_member (init, "command") == "init"): 
> ("authorize" == "init")
> Bail out! 
> cockpit-ssh:ERROR:src/ssh/test-sshbridge.c:560:wait_until_transport_init: 
> assertion failed (json_object_get_string_member (init, "command") == "init"): 
> ("authorize" == "init")
> cockpit-ssh-Message: 20:51:17.704: cockpit-ssh some_host: -1 couldn't 
> connect: Hostname required 'some_host' '22'
> cockpit-ssh-Message: 20:51:17.704: couldn't write control message: Broken pipe
> cockpit-ssh-Message: 20:51:17.704: couldn't write authorize message: 
> Inappropriate ioctl for device
> FAIL test-sshbridge (exit status: 134)

Argh, I can reproduce. The test passes with the previous
http://snapshot.debian.org/package/libssh/0.10.5-3/ but fails with current 
0.10.6-0+deb12u1.

The reason is annoyingly mundane, and already got fixed upstream half a year 
ago:
https://github.com/cockpit-project/cockpit/commit/518d36c3492020525

I prepared a package update with that fix cherry-picked. See attached debdiff.
It builds fine in a clean bookworm container now.
But I don't know how exactly to target and upload this: to bookworm-security or
-updates? It's a follow-up for a previous security update to make that actually
work, but not a security update in itself.

Santiago Vila [2024-04-15 20:28 +0200]:
> For completeness: this was already happening in bullseye and bookworm
> before the DSA. (Reminder for myself: report all the bugs I found
> last week while rebuilding bullseye and bookworm).

Right, that makes sense. There are no C code changes between 287 and 287.1.

Thanks, and sorry for the trouble,

Martin
diff -Nru cockpit-287.1/debian/changelog cockpit-287.1/debian/changelog
--- cockpit-287.1/debian/changelog  2024-04-02 11:11:19.0 +0200
+++ cockpit-287.1/debian/changelog  2024-04-16 09:20:17.0 +0200
@@ -1,3 +1,11 @@
+cockpit (287.1-0+deb12u2) bookworm-security; urgency=medium
+
+  * Add 0001-ssh-Use-valid-host-name-in-test-sshbridge.patch:
+Use valid host name in test-sshbridge. Fixes FTBFS due to unit test
+failure when building against libssh 0.10.6. (Closes: #1069059)
+
+ -- Martin Pitt   Tue, 16 Apr 2024 09:20:17 +0200
+
 cockpit (287.1-0+deb12u1) bookworm-security; urgency=medium
 
   * New upstream security update:
diff -Nru 
cockpit-287.1/debian/patches/0001-ssh-Use-valid-host-name-in-test-sshbridge.patch
 
cockpit-287.1/debian/patches/0001-ssh-Use-valid-host-name-in-test-sshbridge.patch
--- 
cockpit-287.1/debian/patches/0001-ssh-Use-valid-host-name-in-test-sshbridge.patch
   1970-01-01 01:00:00.0 +0100
+++ 
cockpit-287.1/debian/patches/0001-ssh-Use-valid-host-name-in-test-sshbridge.patch
   2024-04-16 09:19:18.0 +0200
@@ -0,0 +1,36 @@
+From 518d36c349202052578a459872c3657760226648 Mon Sep 17 00:00:00 2001
+From: Martin Pitt 
+Date: Fri, 29 Dec 2023 07:12:11 +0100
+Subject: [PATCH] ssh: Use valid host name in test-sshbridge
+
+libssh 0.10.6 made host name parsing stricter. `some_host` is not a
+valid general host name, and is rejected with the latest version.
+---
+ src/ssh/test-sshbridge.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/ssh/test-sshbridge.c b/src/ssh/test-sshbridge.c
+index e0ff9a7a9..9c561e29a 100644
+--- a/src/ssh/test-sshbridge.c
 b/src/ssh/test-sshbridge.c
+@@ -323,7 +323,7 @@ setup (TestCase *tc,
+   if (!fixture->knownhosts_home)
+   g_assert_cmpint (mkdir (tc->home_ssh_dir, 0700), ==, 0);
+ 
+-  g_string_append (content, "Host some_host\n");
++  g_string_append (content, "Host somehost\n");
+   g_string_append_printf (content, "\tHostname %s\n", hostname);
+ 
+   if (fixture->ssh_config_port == PORT_VALID)
+@@ -346,7 +346,7 @@ setup (TestCase *tc,
+   if (fixture->ssh_config_user == USER_INVALID_HOST_PRIORITY)
+ g_string_append_printf (new_host, "%s@", g_get_user_name ());
+   /* Host in the ssh 

Bug#1064730: stdgpu: FTBFS: type_traits.h:736:1: error: expected type-specifier before ‘template’

[Gianfranco Costamagna]

Hello,
On Mon, 15 Apr 2024 16:31:39 -0600 Cordell Bloor  wrote:

Hi Timo,

On Sat, 2 Mar 2024 09:21:43 +0100 Timo =?utf-8?Q?R=C3=B6hling?= 
 wrote:


 >
 > On Sun, 25 Feb 2024 20:28:53 +0100 Lucas Nussbaum 
 > wrote:
 > > > /usr/include/thrust/detail/type_traits.h:736:1: error: expected
 > > > type-specifier before ‘template’
 >
 > This bug is caused by a #ifdef cascade for different
 > THRUST_DEVICE_SYSTEM values, which sadly no longer works with
 > THRUST_DEVICE_SYSTEM_OMP. This makes it effectively impossible to
 > build the HIP backend and the OpenMP backend from the same source.

Am I understanding correctly that this was broken in a rocthrust update? 
Should this be treated as a rocthrust bug? [1]


Sincerely,
Cory Bloor




I agree with Cory, to me looks also a regression in thrust

I'm trying some hacky patch, lets see

Description: Reintroduce fallback lost in 
https://github.com/ROCm/rocThrust/commit/2b80e29803d60f01701a67bc57ef06dacfe8af8b
Author: Gianfranco Costamagna 
Last-Update: 2024-04-16

--- rocthrust-5.7.1.orig/thrust/detail/type_traits.h
+++ rocthrust-5.7.1/thrust/detail/type_traits.h
@@ -731,6 +731,8 @@ using invoke_result_t =
 #else // 2017+
   ::cuda::std::invoke_result_t;
 #endif
+#else
+  std::invoke_result_t;
 #endif

 template 


[1]: https://bugs.debian.org/1064730





OpenPGP_signature.asc
Description: OpenPGP digital signature