Bug#1067796: mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment

[Sean Whitton]

Thanks, but can you sign this off?  Ty!
-- 
Sean Whitton

Bug#1066942: xmrig: FTBFS on armhf: cc: error: unrecognized command-line option ‘-maes’

[Ben Westover]

Hello,

Since my last message, I have tried to reproduce this in several ways, 
e.g. an sbuild chroot in both qemu-user-static and on actual hardware 
(Raspberry Pi 2), and also a direct build on an armhf VM. It always 
builds successfully. Since then, there has been a new upstream release 
of xmrig, so I figured I would just upload and see if it still fails 
buildd. On the buildd log, it indeed fails with the same maes error.


This means xmrig thinks it's building on x86 and adds those flags, but 
this doesn't happen on arm64; only on armhf, only after the t64 
transition. It also doesn't happen on any of my systems but does on 
buildd and apparently your system. I guess I'll request guest access to 
an armhf porterbox and hope FTBFS happens there so I can debug this.


--
Ben Westover


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1068290: python3-fastkml: ImportError since python3-pygeoif 1.4.0

[Tomas Janousek]

Hi,

On Wed, Apr 03, 2024 at 12:29:36AM +0100, Tomas Janousek wrote:

I believe this is because both shapely and pygeoif deprecated
asShape/as_shape respectively. The function is now called just "shape"
in both.
[…]
I think it might be okay to just patch fastkml/geometry.py to

   from shapely.geometry import shape as asShape
   …
   from pygeoif.geometry import shape as asShape

but it needs to be tested more thoroughly.


Yep, almost that. The following seems to work well (makes my CI pass):
https://github.com/liskin/liscopridge/commit/c44c3e6054af5a12bdf24d5687b6478d39480194#diff-e8ae9ced1dd6c13b4566c8a4a669116272e05115ce64aa743658523f4455ad5fR11

--
Tomáš "liskin" ("Pivník") Janoušek, https://lisk.in/

Bug#1068205: marked as done (gauche: FTBFS on arm{el,hf}: "list.c", line 827 (Scm__GetExtendedPairDescriptor): Assertion failed: (z->hiddenTag&0x7) == 0x7)

[Debian Bug Tracking System]

Your message dated Wed, 03 Apr 2024 00:19:22 +
with message-id 
and subject line Bug#1068205: fixed in gauche 0.9.14-3
has caused the Debian Bug report #1068205,
regarding gauche: FTBFS on arm{el,hf}: "list.c", line 827 
(Scm__GetExtendedPairDescriptor): Assertion failed: (z->hiddenTag&0x7) == 0x7
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=gauche=armhf=0.9.14-2=1711974534=0

gcc -DHAVE_CONFIG_H -I. -I. -I./../gc/include -I../gc/include 
`./get-atomic-ops-flags.sh .. .. --cflags`  -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -Wextra -Wno-unused-label -fPIC 
-fomit-frame-pointer  -c test-extra.c
gcc -DHAVE_CONFIG_H -I. -I. -I./../gc/include -I../gc/include 
`./get-atomic-ops-flags.sh .. .. --cflags`  -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -Wextra -Wno-unused-label -fPIC 
-fomit-frame-pointer  -c libextra.c
TARGETLIB="`pwd`"  gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -Wall -Wextra 
-Wno-unused-label -fPIC -Wl,--rpath="`pwd`" -L. -Wl,-z,relro  -rdynamic -o 
test-extra test-extra.o libextra.o -lgauche-0.98 -lmbedtls -lcrypt -lrt -lm  
-lpthread
make[3]: Leaving directory '/<>/src'
make[3]: Entering directory '/<>/lib'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/lib'
make[3]: Entering directory '/<>/ext'
(cd util; make default)
make[4]: Entering directory '/<>/ext/util'
"../../src/gosh" -ftest "../../lib/tools/precomp" -e -P -o util--match 
../../libsrc/util/match.scm
"list.c", line 827 (Scm__GetExtendedPairDescriptor): Assertion failed: 
(z->hiddenTag&0x7) == 0x7
make[4]: *** [Makefile:26: util--match.c] Error 1
make[4]: Leaving directory '/<>/ext/util'
make[3]: *** [Makefile:38: util] Error 2
make[3]: Leaving directory '/<>/ext'
make[2]: *** [Makefile:47: all] Error 1
make[2]: Leaving directory '/<>'
dh_auto_build: error: make -j1 returned exit code 2
make[1]: *** [debian/rules:23: override_dh_auto_build] Error 255

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gauche
Source-Version: 0.9.14-3
Done: NIIBE Yutaka 

We believe that the bug you reported is fixed in the latest version of
gauche, 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.
NIIBE Yutaka  (supplier of updated gauche 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, 02 Apr 2024 15:02:58 +0900
Source: gauche
Architecture: source
Version: 0.9.14-3
Distribution: unstable
Urgency: medium
Maintainer: NIIBE Yutaka 
Changed-By: NIIBE Yutaka 
Closes: 1068205
Changes:
 gauche (0.9.14-3) unstable; urgency=medium
 .
   * debian/patches/50_extended_pair_alignment.patch: New
   (Closes: #1068205).
   * debian/patches/series: Update.
   * debian/control (Build-Depends): Require newer dpkg-dev.
Checksums-Sha1:
 1b0c7e4c76630517cdece12af3870aa5a387e504 1690 gauche_0.9.14-3.dsc
 cb50e5ee8102e6ce1149742070e59446aaec4a87 36988 gauche_0.9.14-3.debian.tar.xz
 e344c918d8b167432c551fd6c77845ec536e8760 8768 gauche_0.9.14-3_amd64.buildinfo
Checksums-Sha256:
 8911a42732f8d7bec417c602031e1ea6058433faf422175b2fc113fe8f0059fb 1690 
gauche_0.9.14-3.dsc
 d29f5ce1b8e15e7cfbbf55fd183cce003b8f483c091f6fd23cca915d7446e936 36988 
gauche_0.9.14-3.debian.tar.xz
 

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1067360 src:flint
Bug #1067360 [src:macaulay2] macaulay2: FTBFS: make[3]: *** 
[../Makefile.library:235: 
/<>/M2/BUILD/tarfiles/normaliz-3.9.2.tar.gz] Error 1
Bug reassigned from package 'src:macaulay2' to 'src:flint'.
No longer marked as found in versions macaulay2/1.22+ds-6.
Ignoring request to alter fixed versions of bug #1067360 to the same values 
previously set
> forcemerge 1067226 1067360
Bug #1067226 {Done: Doug Torrance } [src:flint] flint: 
libflint needs soversion bump to 19
Bug #1067262 {Done: Jerome Benoit } [src:flint] e-antic: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libeantic3/usr/lib/x86_64-linux-gnu/libeantic.so.3.0.2)
Bug #1067274 {Done: Jerome Benoit } [src:flint] normaliz: 
FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
undefined reference to `_fmpq_canonicalise'
Bug #1067286 {Done: Sebastian Ramacher } [src:flint] 
msolve: FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by debian/msolve/usr/bin/msolve)
Bug #1067363 {Done: Doug Torrance } [src:flint] polymake: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Bug #1068140 {Done: Doug Torrance } [src:flint] polymake: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Bug #1067363 {Done: Doug Torrance } [src:flint] polymake: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
1067360 was blocked by: 1067363 1068140 1067274 1067262 1067226 1067286
1067360 was not blocking any bugs.
Removed blocking bug(s) of 1067360: 1068140, 1067286, 1067226, 1067262, 
1067363, and 1067274
Removed indication that 1067363 affects src:e-antic, src:msolve, src:polymake, 
libflint18t64, and src:normaliz
Added indication that 1067363 affects 
src:polymake,libflint18t64,src:msolve,src:e-antic,src:normaliz
Removed indication that 1067226 affects src:msolve, src:normaliz, 
libflint18t64, src:polymake, and src:e-antic
Added indication that 1067226 affects 
src:polymake,libflint18t64,src:msolve,src:e-antic,src:normaliz
Removed indication that 1067262 affects src:msolve, src:normaliz, src:polymake, 
libflint18t64, and src:e-antic
Added indication that 1067262 affects 
src:polymake,libflint18t64,src:msolve,src:e-antic,src:normaliz
Removed indication that 1067274 affects src:msolve, libflint18t64, 
src:normaliz, src:polymake, and src:e-antic
Added indication that 1067274 affects 
src:polymake,libflint18t64,src:msolve,src:e-antic,src:normaliz
Removed indication that 1067286 affects src:e-antic, src:msolve, src:polymake, 
libflint18t64, and src:normaliz
Added indication that 1067286 affects 
src:polymake,libflint18t64,src:msolve,src:e-antic,src:normaliz
Removed indication that 1068140 affects src:msolve, libflint18t64, 
src:normaliz, src:polymake, and src:e-antic
Added indication that 1068140 affects 
src:polymake,libflint18t64,src:msolve,src:e-antic,src:normaliz
Bug #1067360 [src:flint] macaulay2: FTBFS: make[3]: *** 
[../Makefile.library:235: 
/<>/M2/BUILD/tarfiles/normaliz-3.9.2.tar.gz] Error 1
Severity set to 'grave' from 'serious'
1067300 was blocked by: 1068140 1067274 1067363 1067286 1067262 1067226
1067300 was not blocking any bugs.
Added blocking bug(s) of 1067300: 1067360
1067293 was blocked by: 1067262 1067226 1067286 1067363 1068140 1067274
1067293 was not blocking any bugs.
Added blocking bug(s) of 1067293: 1067360
Marked Bug as done
Added indication that 1067360 affects 
src:polymake,libflint18t64,src:msolve,src:e-antic,src:normaliz
Marked as fixed in versions flint/3.1.2-1~exp1.
Marked as found in versions flint/3.1.1-1.
Added tag(s) sid and trixie.
Bug #1067262 {Done: Jerome Benoit } [src:flint] e-antic: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libeantic3/usr/lib/x86_64-linux-gnu/libeantic.so.3.0.2)
Bug #1067274 {Done: Jerome Benoit } [src:flint] normaliz: 
FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
undefined reference to `_fmpq_canonicalise'
Bug #1067286 {Done: Sebastian Ramacher } [src:flint] 
msolve: FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by debian/msolve/usr/bin/msolve)
Bug #1068140 {Done: Doug Torrance } [src:flint] polymake: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Merged 1067226 1067262 1067274 1067286 1067360 1067363 1068140
> affects 1067226 

Bug#1068290: python3-fastkml: ImportError since python3-pygeoif 1.4.0

[Tomas Janousek]

Package: python3-fastkml
Version: 0.12-3
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: t...@nomi.cz

Dear Maintainer,

Since python3-pygeoif 1.4.0-1 appeared in Debian testing, fastkml cannot 
be imported at all:

In [1]: import fastkml
---
ImportError   Traceback (most recent call last)
File /usr/lib/python3/dist-packages/fastkml/geometry.py:39
 38 from shapely.geometry import Polygon
---> 39 from shapely.geometry import asShape
 40 from shapely.geometry.polygon import LinearRing

ImportError: cannot import name 'asShape' from 'shapely.geometry' 
(/usr/lib/python3/dist-packages/shapely/geometry/__init__.py)

During handling of the above exception, another exception occurred:

ImportError   Traceback (most recent call last)
Cell In[1], line 1
> 1 import fastkml

File /usr/lib/python3/dist-packages/fastkml/__init__.py:34
 32 from .atom import Contributor
 33 from .atom import Link
---> 34 from .kml import KML
 35 from .kml import Data
 36 from .kml import Document

File /usr/lib/python3/dist-packages/fastkml/kml.py:46
 44 import fastkml.atom as atom
 45 import fastkml.config as config
---> 46 import fastkml.gx as gx
 48 from .base import _BaseObject
 49 from .base import _XMLObject

File /usr/lib/python3/dist-packages/fastkml/gx.py:92
 89 from pygeoif.geometry import GeometryCollection
 91 from .config import GXNS as NS
---> 92 from .geometry import Geometry
 94 logger = logging.getLogger(__name__)
 97 class GxGeometry(Geometry):

File /usr/lib/python3/dist-packages/fastkml/geometry.py:46
 44 from pygeoif.geometry import MultiPoint, MultiLineString, 
MultiPolygon
 45 from pygeoif.geometry import LinearRing
---> 46 from pygeoif.geometry import as_shape as asShape
 48 import logging
 50 from pygeoif.geometry import GeometryCollection

ImportError: cannot import name 'as_shape' from 'pygeoif.geometry' 
(/usr/lib/python3/dist-packages/pygeoif/geometry.py)

I believe this is because both shapely and pygeoif deprecated 
asShape/as_shape respectively. The function is now called just "shape" 
in both.

Unfortunately, fastkml doesn't have a newer release compatible with 
recent pygeoif (or shapely) versions. There's only been a steady stream 
of 1.0.alphas, most of which are broken in various ways (I have a 
project that depends on fastkml so its CI has been notifying me of ways 
my project breaks with those alphas and I tried to work around these for 
a while but recently gave up and just pinned fastkml to 0.12).

I think it might be okay to just patch fastkml/geometry.py to

from shapely.geometry import shape as asShape
…
from pygeoif.geometry import shape as asShape

but it needs to be tested more thoroughly.

Also, fastkml 0.12 explicitly depends on pygeoif < 1.0, for good reason 
apparently, so it's a bit unfortunate that this dependency is relaxed in 
the Debian package. :-(

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

Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_USER
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages python3-fastkml depends on:
ii  python33.11.6-1
ii  python3-dateutil   2.9.0-2
ii  python3-pkg-resources  68.1.2-2
ii  python3-pygeoif1.4.0-1

python3-fastkml recommends no packages.

python3-fastkml suggests no packages.

-- no debconf information

-- 
Tomáš "liskin" ("Pivník") Janoušek, https://lisk.in/

Bug#1068288: openjdk-21: bootstrap builds required on armel and armhf

[Wookey]

On 2024-04-03 00:20 +0200, Sebastian Ramacher wrote:
> building openjdk-21 is currently still stuck on openjdk-21
> build-depending on itself:
> 
> https://buildd.debian.org/status/package.php?p=openjdk-21
> 
> 
> Somebody did the work to provide boostrap builds of openjdk-17 on armel
> and armhf. We need the same for openjdk-21.

Yes. I had a look at this. I was hoping to use the openjdk-17 to allow
building of openjdk-21. But it doesn't 'just work', because:

checking for version string... 21.0.3-ea+7-Debian-1
configure: Found potential Boot JDK using configure arguments
configure: Potential Boot JDK found at /usr/lib/jvm/java-17-openjdk-armhf is 
incorrect JDK version (openjdk version "17.0.11-ea" 2024-04-16 OpenJDK Runtime 
Environment (build 17.0.11-ea+7-Debian-1) OpenJDK Server VM (build 
17.0.11-ea+7-Debian-1, mixed mode, sharing)); ignoring
configure: (Your Boot JDK version must be one of: 20 21)
configure: error: The path given by --with-boot-jdk does not contain a valid 
Boot JDK

Now what I'm not sure is whether openjdk-21 _actually_ needs openjdk
20 (or 21), or if it just needs 'java', and has been set to '20 or 21'
for reasons of being able to drop -17 in due course.

Nor where these things are configured.

If it _does_ need -20, then can I build -20 with -17 or -19 with -17 and so on?

The advantage of going straight to -21 is that it's not in the archive already 
and 'just' needs a binary build.
and also -21 has had its build-deps modified for t64 dependencies. -20 and -19 
haven't been

-20 needs -19 (and jtreg7 but one can use -Pnocheck)
-19 needs -18 (and jtreg6 but one can use -Pnocheck)

So right now I'm not sure what the easiest path is.

Can I actually just build -21 with -17 if I can persuade the build system, or 
will something important break with that much version-skew?

can I build -19 with -17 (and appropriate t64 dep updates) (-18 is no longer in 
the archive so I really hope we don't need to go 18,19,20,21

Clues welcome on the best approach.

Wookey
-- 
Principal hats:  Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Bug#1066289: marked as done (clipit: FTBFS: main.c:1080:9: error: implicit declaration of function ‘umask’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 22:49:05 +
with message-id 
and subject line Bug#1066289: fixed in clipit 1.4.5+git20210313-2
has caused the Debian Bug report #1066289,
regarding clipit: FTBFS: main.c:1080:9: error: implicit declaration of function 
‘umask’ [-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.)


-- 
1066289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clipit
Version: 1.4.5+git20210313-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..  -I.. -I/usr/include/gtk-3.0 
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread  
> -I/usr/include/libayatana-appindicator3-0.1 
> -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/gtk-3.0 
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 
> -pthread  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g 
> -DCLIPITLOCALEDIR=\""/usr/share/locale"\" -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wall -pedantic -c -o 
> eggaccelerators.o eggaccelerators.c
> preferences.c: In function ‘read_actions’:
> preferences.c:324:12: warning: variable ‘fread_return’ set but not used 
> [-Wunused-but-set-variable]
>   324 | size_t fread_return;
>   |^~~~
> preferences.c: In function ‘read_excludes’:
> preferences.c:596:12: warning: variable ‘fread_return’ set but not used 
> [-Wunused-but-set-variable]
>   596 | size_t fread_return;
>   |^~~~
> preferences.c: In function ‘show_preferences’:
> preferences.c:732:53: warning: ‘GtkStock’ is deprecated 
> [-Wdeprecated-declarations]
>   732 | GTK_STOCK_CANCEL, 
>   GTK_RESPONSE_REJECT,
>   | ^~~~
> preferences.c:733:53: warning: ‘GtkStock’ is deprecated 
> [-Wdeprecated-declarations]
>   733 | GTK_STOCK_OK, 
>   GTK_RESPONSE_ACCEPT, NULL);
>   | ^~~~
> preferences.c:735:3: warning: ‘gtk_widget_render_icon_pixbuf’ is deprecated: 
> Use 'gtk_icon_theme_load_icon' instead [-Wdeprecated-declarations]
>   735 |   gtk_window_set_icon((GtkWindow*)dialog, 
> gtk_widget_render_icon_pixbuf(dialog, GTK_STOCK_PREFERENCES, 
> GTK_ICON_SIZE_MENU));
>   |   ^~~
> In file included from /usr/include/gtk-3.0/gtk/gtkapplication.h:27,
>  from /usr/include/gtk-3.0/gtk/gtkwindow.h:33,
>  from /usr/include/gtk-3.0/gtk/gtkdialog.h:32,
>  from /usr/include/gtk-3.0/gtk/gtkaboutdialog.h:30,
>  from /usr/include/gtk-3.0/gtk/gtk.h:31,
>  from preferences.c:24:
> /usr/include/gtk-3.0/gtk/gtkwidget.h:1182:15: 

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1067262 src:flint
Bug #1067262 {Done: Jerome Benoit } [src:e-antic] 
e-antic: FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libeantic3/usr/lib/x86_64-linux-gnu/libeantic.so.3.0.2)
Bug reassigned from package 'src:e-antic' to 'src:flint'.
No longer marked as found in versions e-antic/2.0.2+ds-1.
No longer marked as fixed in versions e-antic/2.0.2+ds-2~exp1.
> reassign 1067286 src:flint
Bug #1067286 {Done: Sebastian Ramacher } [src:msolve] 
msolve: FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by debian/msolve/usr/bin/msolve)
Bug reassigned from package 'src:msolve' to 'src:flint'.
No longer marked as found in versions msolve/0.6.5-1.
Ignoring request to alter fixed versions of bug #1067286 to the same values 
previously set
> reassign 1067274 src:flint
Bug #1067274 {Done: Jerome Benoit } [src:normaliz] 
normaliz: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
undefined reference to `_fmpq_canonicalise'
Bug reassigned from package 'src:normaliz' to 'src:flint'.
No longer marked as found in versions normaliz/3.10.2+ds-1.
No longer marked as fixed in versions normaliz/3.10.2+ds-2~exp1.
> forcemerge 1067226 1067262 1067286 1067274
Bug #1067226 {Done: Doug Torrance } [src:flint] flint: 
libflint needs soversion bump to 19
Bug #1067363 {Done: Doug Torrance } [src:flint] polymake: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Bug #1068140 {Done: Doug Torrance } [src:flint] polymake: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Bug #1067363 {Done: Doug Torrance } [src:flint] polymake: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
1067262 was blocked by: 1068140 1067363 1067226
1067262 was not blocking any bugs.
Removed blocking bug(s) of 1067262: 1067363, 1068140, and 1067226
1067274 was blocked by: 1068140 1067226 1067363
1067274 was not blocking any bugs.
Removed blocking bug(s) of 1067274: 1067226, 1067363, and 1068140
1067286 was blocked by: 1068140 1067226 1067363
1067286 was not blocking any bugs.
Removed blocking bug(s) of 1067286: 1067226, 1068140, and 1067363
Added tag(s) sid and trixie.
Added tag(s) sid and trixie.
Added tag(s) trixie and sid.
Bug #1067274 {Done: Jerome Benoit } [src:flint] normaliz: 
FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libeantic.so: 
undefined reference to `_fmpq_canonicalise'
Severity set to 'grave' from 'serious'
1067300 was blocked by: 1067226 1067363 1068140
1067300 was not blocking any bugs.
Added blocking bug(s) of 1067300: 1067274
1067293 was blocked by: 1067226 1067363 1068140
1067293 was not blocking any bugs.
Added blocking bug(s) of 1067293: 1067274
1067360 was blocked by: 1067363 1067226 1068140
1067360 was not blocking any bugs.
Added blocking bug(s) of 1067360: 1067274
Added indication that 1067274 affects src:polymake
Marked as fixed in versions flint/3.1.2-1~exp1.
Marked as found in versions flint/3.1.1-1.
Added tag(s) sid and trixie.
Bug #1067262 {Done: Jerome Benoit } [src:flint] e-antic: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libeantic3/usr/lib/x86_64-linux-gnu/libeantic.so.3.0.2)
Severity set to 'grave' from 'serious'
1067360 was blocked by: 1067363 1068140 1067274 1067226
1067360 was not blocking any bugs.
Added blocking bug(s) of 1067360: 1067262
1067300 was blocked by: 1067226 1067363 1068140 1067274
1067300 was not blocking any bugs.
Added blocking bug(s) of 1067300: 1067262
1067293 was blocked by: 1067226 1067363 1068140 1067274
1067293 was not blocking any bugs.
Added blocking bug(s) of 1067293: 1067262
Added indication that 1067262 affects src:polymake
Marked as fixed in versions flint/3.1.2-1~exp1.
Marked as found in versions flint/3.1.1-1.
Added tag(s) sid and trixie.
Bug #1067286 {Done: Sebastian Ramacher } [src:flint] 
msolve: FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by debian/msolve/usr/bin/msolve)
Severity set to 'grave' from 'serious'
1067360 was blocked by: 1067262 1067226 1068140 1067274 1067363
1067360 was not blocking any bugs.
Added blocking bug(s) of 1067360: 1067286
1067300 was blocked by: 1067226 1067262 1067274 1068140 1067363
1067300 was not blocking any bugs.
Added blocking bug(s) of 1067300: 1067286
1067293 was blocked by: 1067226 1067262 1067363 1067274 1068140
1067293 was not blocking any bugs.
Added blocking bug(s) of 1067293: 1067286
Added indication that 1067286 

Bug#1056893: marked as done (uvloop: ftbfs with cython 3.0.x)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 22:22:27 +
with message-id 
and subject line Bug#1056893: fixed in uvloop 0.19.0+ds1-2.1
has caused the Debian Bug report #1056893,
regarding uvloop: ftbfs with cython 3.0.x
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.)


-- 
1056893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:uvloop
Version: 0.19.0+ds1-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: cython3

[This bug is targeted to the upcoming trixie release]

The package fails to build in a test rebuild on at least arm64 with
cython 3.0.5, but succeeds to build with cython 0.29.36.  Please
update the package to build with cython 3.0.5 (available in experimental).

If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable).  There is no replacement for cython3-dbg.

Build logs building with cython 3.0.5 can be found at
https://people.debian.org/~stefanor/cython3/cython-3.0.5/

See also https://lists.debian.org/debian-python/2023/11/msg00034.html
--- End Message ---
--- Begin Message ---
Source: uvloop
Source-Version: 0.19.0+ds1-2.1
Done: Sebastian Ramacher 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 31 Mar 2024 23:47:16 +0200
Source: uvloop
Architecture: source
Version: 0.19.0+ds1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Sebastian Ramacher 
Closes: 1056893
Changes:
 uvloop (0.19.0+ds1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Graham Inggs ]
   * Include proposed patch for compatibility with Cython 3 (Closes: #1056893)
 (LP: #2051150)
   * Skip tests failing with libuv 1.48.0
Checksums-Sha1:
 fe8dbc58253f988138c2214f8a3706cae8b0ad26 1660 uvloop_0.19.0+ds1-2.1.dsc
 5fab2244d8c07a11efdac845262e24151a992d53 15556 
uvloop_0.19.0+ds1-2.1.debian.tar.xz
 40d3fec31425cc41411a1484a3b482b0685c2d48 8247 
uvloop_0.19.0+ds1-2.1_source.buildinfo
Checksums-Sha256:
 d51f8859d220ee6abb42366f2a7f94bef12f9c7929c312ca30f5cb0992ba9791 1660 
uvloop_0.19.0+ds1-2.1.dsc
 1fb62f5dfbdb6af16415dc9c9f12e4680cd595ac8e4c77c54ecd748ac534a659 15556 
uvloop_0.19.0+ds1-2.1.debian.tar.xz
 f8e68e55caf1f64d15795721c6d97aa2a41cecd5e8cf28fa94d1252a6fabac72 8247 
uvloop_0.19.0+ds1-2.1_source.buildinfo
Files:
 db672dc39a884c77e4f2f212d02b5cfb 1660 python optional uvloop_0.19.0+ds1-2.1.dsc
 6124fa6ddf0d30701b9a20c4aca7480f 15556 python optional 
uvloop_0.19.0+ds1-2.1.debian.tar.xz
 74cc4a742a7caeb34edb3964f67de277 8247 python optional 
uvloop_0.19.0+ds1-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZgnbLAAKCRAhk2s2YA/N
iYM1AQDmiu9vZrlRklsbUUkQ/K1TEHMC9JuSG31miNNyDzxVOgEAs+7UvyVbTN+a
kGWpCuEaR7n+No2OeNRh3fvmynuSFAM=
=gEZK
-END PGP SIGNATURE-



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

Processed: closing 1067286

[Debian Bug Tracking System]

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

> # was a bug in flint
> close 1067286
Bug #1067286 [src:msolve] msolve: FTBFS: dpkg-shlibdeps: error: no dependency 
information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/msolve/usr/bin/msolve)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1068288: openjdk-21: bootstrap builds required on armel and armhf

[Sebastian Ramacher]

Source: openjdk-21
Version: 21.0.3~7ea-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org, debian-...@lists.debian.org

Hi Matthias, hi arm* porters

building openjdk-21 is currently still stuck on openjdk-21
build-depending on itself:

https://buildd.debian.org/status/package.php?p=openjdk-21

Dependency installability problem for openjdk-21 on armel:

openjdk-21 build-depends on:
- libcups2-dev:armel
libcups2-dev depends on:
- libcups2t64:armel (= 2.4.7-1.2)
openjdk-21 build-depends on:
- openjdk-21-jdk-headless:armel
openjdk-21-jdk-headless depends on:
- openjdk-21-jre-headless:armel (= 21.0.2+13-2)
openjdk-21-jre-headless depends on:
- libcups2:armel
libcups2t64 conflicts with:
- libcups2:armel (< 2.4.7-1.2)

Dependency installability problem for openjdk-21 on armhf:

openjdk-21 build-depends on:
- libcups2-dev:armhf
libcups2-dev depends on:
- libcups2t64:armhf (= 2.4.7-1.2)
openjdk-21 build-depends on:
- openjdk-21-jdk-headless:armhf
openjdk-21-jdk-headless depends on:
- openjdk-21-jre-headless:armhf (= 21.0.2+13-2)
openjdk-21-jre-headless depends on:
- libcups2:armhf
libcups2t64 conflicts with:
- libcups2:armhf (< 2.4.7-1.2)

Somebody did the work to provide boostrap builds of openjdk-17 on armel
and armhf. We need the same for openjdk-21.

Cheers
-- 
Sebastian Ramacher

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 1063596 3.1.1-1
Bug #1063596 {Done: "Torrance, Douglas" } [src:flint] 
flint: FTBFS on amd64: test segfault
Marked as fixed in versions flint/3.1.1-1.
> thanks
Stopping processing here.

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

Bug#1067796: mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment

[Daniel Kahn Gillmor]

Control: tags 1067796 + patch

On Thu 2024-03-28 13:09:48 +0800, Sean Whitton wrote:
> Please take a look into this test suite failure for your script.

The attached patch should clean things up now that argcomplete is
annotated.  in my local tests, the script runs and exits cleanly.

This patch is worth applying generally, but given the flux around mypy
typing, i would also be fine with just recording the output of mypy
--strict instead of failing hard on it.

 --dkg

From b522c1cc6201f75ab6103954016bbb719d4dd2fa Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor 
Date: Tue, 30 Jan 2024 15:40:58 -0500
Subject: [PATCH] email-print-mime-structure: clean up typechecking
 (argcomplete types are known)

(and, update copyright years)
---
 email-print-mime-structure | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/email-print-mime-structure b/email-print-mime-structure
index b7646e0..7635f53 100755
--- a/email-print-mime-structure
+++ b/email-print-mime-structure
@@ -2,7 +2,7 @@
 # PYTHON_ARGCOMPLETE_OK
 # -*- coding: utf-8 -*-
 
-# Copyright (C) 2019 Daniel Kahn Gillmor
+# Copyright (C) 2019-2024 Daniel Kahn Gillmor
 #
 # This program is free software: you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -39,6 +39,7 @@ import subprocess
 
 from argparse import ArgumentParser, Namespace
 from typing import Optional, Union, List, Tuple, Any
+from types import ModuleType
 from email.charset import Charset
 from email.message import Message
 
@@ -47,8 +48,9 @@ try:
 except ImportError:
 pgpy = None
 
+argcomplete:Optional[ModuleType]
 try:
-import argcomplete #type: ignore
+import argcomplete
 except ImportError:
 argcomplete = None
 
-- 
2.43.0



signature.asc
Description: PGP signature

Processed: Re: Bug#1067796: mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment

[Debian Bug Tracking System]

Processing control commands:

> tags 1067796 + patch
Bug #1067796 [src:mailscripts] mailscripts: FTBFS: 
email-print-mime-structure:51: error: Unused "type: ignore" comment
Added tag(s) patch.

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

Bug#1064728: marked as done (davfs2: FTBFS: configure: error: could not find neon)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 21:19:21 +
with message-id 
and subject line Bug#1064728: fixed in davfs2 1.7.0-1
has caused the Debian Bug report #1064728,
regarding davfs2: FTBFS: configure: error: could not find neon
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.)


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

Hi,

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


Relevant part (hopefully):
> checking whether to use NLS... yes
> checking where the gettext function comes from... libc
> checking for neon-config... /usr/bin/neon-config
> checking linking against neon... yes
> configure: incompatible neon library version 0.33.0: wanted 0.27 28 29 30 31 
> 32
> configure: error: could not find neon
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/davfs2_1.6.1-3_unstable.log

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

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

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated davfs2 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, 02 Apr 2024 23:03:15 +0200
Source: davfs2
Architecture: source
Version: 1.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Sebastian Ramacher 
Closes: 1064728
Changes:
 davfs2 (1.7.0-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream version 1.7.0
   * Fix build with neon 0.33 (Closes: #1064728)
Checksums-Sha1:
 80dd8146cfb9cff2c0f07b767e5031b24376cae6 1241 davfs2_1.7.0-1.dsc
 5f42d89933ad24f13dd6c5b0895dda37a1e72909 295476 davfs2_1.7.0.orig.tar.xz
 d85391ea28f37d8ec1ea43f412922b018da2e7cc 26596 davfs2_1.7.0-1.debian.tar.xz
 bb1e737d6f3465d4b88b98e1a615b701b5d101fe 6586 davfs2_1.7.0-1_amd64.buildinfo
Checksums-Sha256:
 edc8a02c6783554f9f9b0872f9da29fbaa362a8d20b6a40854f160a1f48ff044 1241 
davfs2_1.7.0-1.dsc
 1db801dff696187467326544bff6509dc17ae7df28e04932714bfcc8b479e618 295476 
davfs2_1.7.0.orig.tar.xz
 e8dd1eea87583f0ff6c1e559456dff7de72b3794630a5c668fe8607cd9dbb835 26596 
davfs2_1.7.0-1.debian.tar.xz
 30984855cec840a6144a8d4da0b9fdc23b3a61c362d2b5170a3d60839c680a7c 6586 
davfs2_1.7.0-1_amd64.buildinfo
Files:
 fe317d15b198625fd82719fbcf3ff097 1241 utils optional davfs2_1.7.0-1.dsc
 ae04e128aa6c2582c5f092dd21c45b98 295476 utils optional davfs2_1.7.0.orig.tar.xz
 9cee180d4a608ec753b1bd12e9ca9910 26596 utils optional 
davfs2_1.7.0-1.debian.tar.xz
 11dc73ccd753fed8c3d86e956cf5541d 6586 utils optional 
davfs2_1.7.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZgxy6wAKCRAhk2s2YA/N
iYahAQD7IosEyUYhefVFsCukfm4N6hwWvqwVqyEddH8NXpbi7QD/UWGH/Ma1g7B1
TGjTc9C/yw/5wIBWIOXdO0BXC2bG0gY=
=tCwv
-END PGP SIGNATURE-



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

Bug#1066439: marked as done (squidguard: FTBFS: ././conftest.c:17:(.text.startup+0xb): undefined reference to `yywrap')

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 21:11:09 +
with message-id 
and subject line Bug#1066439: fixed in squidguard 1.6.0-5
has caused the Debian Bug report #1066439,
regarding squidguard: FTBFS: ././conftest.c:17:(.text.startup+0xb): undefined 
reference to `yywrap'
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.)


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

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: /tmp/ccG4JRNN.o: in function `main':
> ././conftest.c:17:(.text.startup+0xb): undefined reference to `yywrap'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/squidguard_1.6.0-4_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: squidguard
Source-Version: 1.6.0-5
Done: Joachim Wiedorn 

We believe that the bug you reported is fixed in the latest version of
squidguard, 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.
Joachim Wiedorn  (supplier of updated squidguard 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, 02 Apr 2024 22:28:07 +0200
Source: squidguard
Architecture: source
Version: 1.6.0-5
Distribution: unstable
Urgency: medium
Maintainer: Joachim Wiedorn 
Changed-By: Joachim Wiedorn 
Closes: 994187 1066439
Changes:
 squidguard (1.6.0-5) unstable; urgency=medium
 .
   * debian/control:
 - Add libfl-dev as build dependency. Closes: #1066439
 - Bump to Standards-Version 4.6.2 (no changes).
 - Move to debhelper-compat 13.
   * debian/update-squidguard:
 - Optimize script using DATADIR as symlink. Closes: #994187
Checksums-Sha1:
 f17a8409e9a93d4b195c7bff82cc21949f470665 1850 squidguard_1.6.0-5.dsc
 e271b5bf2c7608be81f3fab5086d307105aadf1e 1902233 squidguard_1.6.0.orig.tar.gz
 ea0ab90914412eecfbcdf0dcc93fd8fe9b41882c 25724 squidguard_1.6.0-5.debian.tar.xz
 10abcd649df0c2e58da6b8d1d4fdfd4c636d2db8 6337 
squidguard_1.6.0-5_source.buildinfo
Checksums-Sha256:
 47407740c09c2a6149edbf604576696aef761ce951d3260536fc0dd0af4a6953 1850 
squidguard_1.6.0-5.dsc
 3de0d64b7f1b4b69de16d3168a438c8df28419041e0fdaf9446e7a4599e612b5 1902233 
squidguard_1.6.0.orig.tar.gz
 c35d149d68696302ccc3d66740381e872181de229bf1221f14b085c909a4db0c 25724 
squidguard_1.6.0-5.debian.tar.xz
 b804b93f7c75999410b5053eebe0ae7d3e0ff44a42d5facf01937488a8c333ea 6337 
squidguard_1.6.0-5_source.buildinfo
Files:
 6c464d194a91136920afdbfad9aa7b92 1850 web optional squidguard_1.6.0-5.dsc
 ebf207accc6da4ad07de2db6e71ce8dc 1902233 web optional 
squidguard_1.6.0.orig.tar.gz
 e07a38bd072ff8869425fc94fa3c176a 25724 web optional 
squidguard_1.6.0-5.debian.tar.xz
 25ab4c5771979d6169f54685caf075a5 6337 web optional 
squidguard_1.6.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHIBAEBCgAyFiEEuiB7VTCOYLwzX77x8VbpZqUQ5LwFAmYMayIUHGpvb2RlYmlh
bkBqb29uZXQuZGUACgkQ8VbpZqUQ5LyICQwAhf6Zw1Ijl8k4GzoCZVDUwZxUPUDw
ik06cAmFAU8xvjvoR1k3Pd3GdDc7ysKRicmyQOPB8nvfAx0T4WWe9CJuLhBlqlBH
foLBPQkvUIVrZQfhv8utYiUv1VbGlnd0CiP8jgWwlrZAAqWNk4w15ZQoUZOI23CD

Bug#1068264: avfs: FTBFS on armel: ./src/xzread.c:185:(.text+0x1b0): undefined reference to `__atomic_fetch_add_8'

[Sebastian Ramacher]

Source: avfs
Version: 1.1.5-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=avfs=armel=1.1.5-1=1691158944=0

/bin/bash ../libtool  --tag=CC   --mode=link arm-linux-gnueabi-gcc -I../include 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -D_GNU_SOURCE 
-I/usr/include/neon -D_LARGEFILE64_SOURCE -DNE_LFS  -I/usr/include/fuse 
-D_FILE_OFFSET_BITS=64-g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z,relro 
-Wl,-z,now -lpthread -ldl  -lneon-gnutls  -llzma  -lzstd  -Wl,-z,relro 
-Wl,-z,now -o runtest runtest.o ../lib/libavfs_static.la -lpthread -ldl  
-lneon-gnutls  -llzma  -lzstd 
libtool: link: arm-linux-gnueabi-gcc -I../include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -D_GNU_SOURCE 
-I/usr/include/neon -D_LARGEFILE64_SOURCE -DNE_LFS -I/usr/include/fuse 
-D_FILE_OFFSET_BITS=64 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z 
-Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,relro -Wl,-z -Wl,now -o 
gzip_multimember_test gzip_multimember_test.o  ../lib/.libs/libavfs_static.a 
-lz -lbz2 -lpthread -ldl -lneon-gnutls -llzma -lzstd
libtool: link: arm-linux-gnueabi-gcc -I../include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -D_GNU_SOURCE 
-I/usr/include/neon -D_LARGEFILE64_SOURCE -DNE_LFS -I/usr/include/fuse 
-D_FILE_OFFSET_BITS=64 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z 
-Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,relro -Wl,-z -Wl,now -o testread testread.o 
 ../lib/.libs/libavfs_static.a -lz -lbz2 -lpthread -ldl -lneon-gnutls -llzma 
-lzstd
/usr/bin/ld: ../lib/.libs/libavfs_static.a(xzread.o): in function 
`xzfile_decompress':
./src/xzread.c:185:(.text+0x1b0): undefined reference to `__atomic_fetch_add_8'
libtool: link: arm-linux-gnueabi-gcc -I../include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -D_GNU_SOURCE 
-I/usr/include/neon -D_LARGEFILE64_SOURCE -DNE_LFS -I/usr/include/fuse 
-D_FILE_OFFSET_BITS=64 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z 
-Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,relro -Wl,-z -Wl,now -o runtest runtest.o  
../lib/.libs/libavfs_static.a -lz -lbz2 -lpthread -ldl -lneon-gnutls -llzma 
-lzstd
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:401: gzip_multimember_test] Error 1
make[2]: *** Waiting for unfinished jobs
/usr/bin/ld: ../lib/.libs/libavfs_static.a(xzread.o): in function 
`xzfile_decompress':
./src/xzread.c:185:(.text+0x1b0): undefined reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:409: testread] Error 1
/usr/bin/ld: ../lib/.libs/libavfs_static.a(xzread.o): in function 
`xzfile_decompress':
./src/xzread.c:185:(.text+0x1b0): undefined reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:405: runtest] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1063596: marked as done (flint: FTBFS on amd64: test segfault)

[Debian Bug Tracking System]

Your message dated Tue, 2 Apr 2024 21:00:12 +
with message-id <87jzlfqy3t@piedmont.edu>
and subject line Re: flint: FTBFS on amd64: test segfault
has caused the Debian Bug report #1063596,
regarding flint: FTBFS on amd64: test segfault
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.)


-- 
1063596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flint
Version: 3.0.1-3
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=flint=amd64=3.0.1-3=1707499549=0

powmod_x_fmpz_preinv...PASS
randtest_irreduciblePASS
scalar_addmul_fq... PASS
scalar_div_fq... PASS
scalar_mul_fq... PASS
scalar_submul_fq... PASS
set_fmpz_poly... PASS
set_nmod_poly... PASS
set_trunc... PASS
PASS
sqr... shift_left/right... PASS
sqr_KS... PASS
sqr_classical... PASS
sqrt... PASS
sqrt_seriesPASS
sub... PASS
sub_series... PASS
xgcdPASS
xgcd_euclidean_fPASS
ctx_init_modulusPASS
ctx_init_modulus_nmodPASS
PASS
make[2]: *** [Makefile:663: 
build/fq_default/test/t-ctx_init_modulus_nmod_TEST_RUN] Segmentation fault
make[2]: *** Waiting for unfinished jobs
PASS
ctx_modulusPASS

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---

Control: fixed -1 3.1.1-1

On Fri, 9 Feb 2024 20:54:31 +0100 Sebastian Ramacher  
wrote:

ctx_init_modulusPASS
ctx_init_modulus_nmodPASS
PASS
make[2]: *** [Makefile:663: 
build/fq_default/test/t-ctx_init_modulus_nmod_TEST_RUN] Segmentation fault
make[2]: *** Waiting for unfinished jobs
PASS
ctx_modulusPASS


There were some updates to this test in [1], which was included in flint 3.1.0.
There haven't been any build failures since the first post-3.1.0 Debian package
was uploaded (3.1.1-1), so this appears to have been fixed.

[1] https://github.com/flintlib/flint/pull/1765


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

Bug#1067849: marked as done (util-linux: CVE-2024-28085: wall: escape sequence injection)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 20:33:09 +
with message-id 
and subject line Bug#1067849: fixed in util-linux 2.36.1-8+deb11u2
has caused the Debian Bug report #1067849,
regarding util-linux: CVE-2024-28085: wall: escape sequence injection
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.)


-- 
1067849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: util-linux
Version: 2.39.3-11
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2.38.1-5 
Control: found -1 2.36.1-8+deb11u1
Control: found -1 2.36.1-8
Control: found -1 2.33.1-0.1

Hi,

The following vulnerability was published for util-linux.

CVE-2024-28085[0]:
| escape sequence injection in wall


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-28085
https://www.cve.org/CVERecord?id=CVE-2024-28085
[1] https://www.openwall.com/lists/oss-security/2024/03/27/5
[2] https://people.rit.edu/sjf5462/6831711781/wall_2_27_2024.txt
[3] https://github.com/skyler-ferrante/CVE-2024-28085

Regards,
Salvatore

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

Kernel: Linux 6.1.0-18-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.36.1-8+deb11u2
Done: Chris Hofstaedtler 

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

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

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated util-linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Mar 2024 11:09:40 +0100
Source: util-linux
Architecture: source
Version: 2.36.1-8+deb11u2
Distribution: bullseye-security
Urgency: high
Maintainer: util-linux packagers 
Changed-By: Chris Hofstaedtler 
Closes: 1067849
Changes:
 util-linux (2.36.1-8+deb11u2) bullseye-security; urgency=high
 .
   * d/gbp.conf: update for stable release
   * Add upstream patches to fix CVE-2024-28085 (Closes: #1067849)
   * No longer install wall, write setgid tty to address CVE-2024-28085
Checksums-Sha1:
 f810388ed84976999fabbf49173bbec13f151e66 4306 util-linux_2.36.1-8+deb11u2.dsc
 472c45dcb65e1ddc4687e808e3ebe5a308f8fbae 106524 
util-linux_2.36.1-8+deb11u2.debian.tar.xz
 5fe5251010b33fa2b9216461a891ef47f7779e2f 18966 
util-linux_2.36.1-8+deb11u2_arm64.buildinfo
Checksums-Sha256:
 16cfb1bc4d0a52f5edf2c78b5e022bb1fc180f03b93a5094b5c420a0d8d4431a 4306 
util-linux_2.36.1-8+deb11u2.dsc
 0b07fbb79e1dab3be2568295664af950a7c3e589ce7821febf2ab0a3ccbe4862 106524 
util-linux_2.36.1-8+deb11u2.debian.tar.xz
 4f03b0edcb15aec39bca17f9fdd9a668af59bbf3b51d0a61d6f8f3b896c0de57 18966 
util-linux_2.36.1-8+deb11u2_arm64.buildinfo
Files:
 1e70bcd412d9ad7ff8bb1f2458782fec 4306 base required 
util-linux_2.36.1-8+deb11u2.dsc
 b88fa53fa6422a3a64743166a23384e5 106524 base required 
util-linux_2.36.1-8+deb11u2.debian.tar.xz
 47b9a361c456edbf3d95a6f5e395e5ed 18966 base required 
util-linux_2.36.1-8+deb11u2_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmYFQ5YACgkQXBPW25MF
LgPaPA//TpX7f7WxWEGgyvWlBDt8KTuBM6uzvkOJ+od+1/tiAMSHM8f9kNmK8uA1
KLkmh1owP9j24wdfu9BMXwMF1jwQkbBh9WPaADRGvG6biIWR0O3VdMTlJZFNgzYI
0RwPvLw9D9L9urbqqoK2/kOarApjKb93+GhQiMfX/ejBcvQV9BObik+OvX2ONFkS
STW9bomWRq8UOsK97mdR/sdplgc6lSUzakd7WWhixjlMAG/uuX+5m/JAeDyNt28B
F2byGErcP+0BlqO9xD7NyOQmhcx7Alak8wMTsDTw4aBu2PSAdPZ/d4cJpQ7U80RN
zrEH1Lm2JDm3relIJxCQutY3cf+o94w73dE1JR9C2y2h9VMLF8v/gSG7hzIlyI46
oqhSrxCcQadn4wk+etYV1ho4fopPKcMZUuf7e5AENpAaCxYiVQvw4UIFrlm6d4WB

Bug#1067115: marked as done (gross: CVE-2023-52159)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 20:32:32 +
with message-id 
and subject line Bug#1067115: fixed in gross 1.0.2-4.1~deb11u1
has caused the Debian Bug report #1067115,
regarding gross: CVE-2023-52159
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.)


-- 
1067115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gross
Version: 1.0.2-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for gross.

CVE-2023-52159[0]:
| A stack-based buffer overflow vulnerability in gross 0.9.3 through
| 1.x before 1.0.4 allows remote attackers to trigger a denial of
| service (grossd daemon crash) or potentially execute arbitrary code
| in grossd via crafted SMTP transaction parameters that cause an
| incorrect strncat for a log entry.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-52159
https://www.cve.org/CVERecord?id=CVE-2023-52159
[1] 
https://codeberg.org/bizdelnick/gross/wiki/Known-vulnerabilities#cve-2023-52159

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gross
Source-Version: 1.0.2-4.1~deb11u1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
gross, 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.
Adrian Bunk  (supplier of updated gross 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, 29 Mar 2024 23:02:44 +0200
Source: gross
Architecture: source
Version: 1.0.2-4.1~deb11u1
Distribution: bullseye
Urgency: high
Maintainer: Antonio Radici 
Changed-By: Adrian Bunk 
Closes: 1067115
Changes:
 gross (1.0.2-4.1~deb11u1) bullseye; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for bullseye.
 .
 gross (1.0.2-4.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * CVE-2023-52159: Stack-based buffer overflow (Closes: #1067115)
Checksums-Sha1:
 87933f0fd7c19768ef9a378e0b288cd25ef121b0 1869 gross_1.0.2-4.1~deb11u1.dsc
 00961feb7b9c8330bb6db2a33b8d5c378c1eaee2 317461 gross_1.0.2.orig.tar.gz
 4098437e9f84970f1c43c3df2699f78eebe68915 7024 
gross_1.0.2-4.1~deb11u1.debian.tar.xz
Checksums-Sha256:
 1ce55dfb6b85c0710c374db83ec40a5300dc3488b4a6f43a7f5e267a92f71c3c 1869 
gross_1.0.2-4.1~deb11u1.dsc
 8443b9ba46537ed6470bda60109df68d40d3dd11b9f5a07c9180cb01af7147f9 317461 
gross_1.0.2.orig.tar.gz
 d9eec296a55d140deb5b525ed9e93d9bf767239b23e8828fe961b5d07f37a948 7024 
gross_1.0.2-4.1~deb11u1.debian.tar.xz
Files:
 9ce1eaa1da132e4eb44634cc16e9a69a 1869 mail extra gross_1.0.2-4.1~deb11u1.dsc
 cb88d88553161c01e9bed7a74c3e9263 317461 mail extra gross_1.0.2.orig.tar.gz
 8c360f13264f1d8098dc51c01a4d779c 7024 mail extra 
gross_1.0.2-4.1~deb11u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmYHLWAACgkQiNJCh6LY
mLGTexAAjVy3+rghJcTR26UweRS+P1/NuUIwTHqLfAAoSYmZQMLHnVQdodxabwzW
No7F+tmVkUvr1oNCkjmXUnSSKG2BPki2w5lb4oBoDrZxZ0wwOLw8Xg6r5HEVpTev
4UxjOeKZFrJiHPtmBfSDEADlC3CqcuEnE19E6P0LFdiOgvvVflqpWaDb6Yyik0X7
jST6OnbxuTNuQJhSS8pXfqOuqE5KapUjIzkeMK3ljoe+zNblY32QCQL6+IMAyJBN
fGEqV6wYrcfr6SeF2XMCia2se7eyRyQCrigyVrMUSPjMg+4PowvTL/Etb2J9edR5
J5J/qSMf3WxSuW6a9O15+paM7Hfe259Z/BfzYxwi8bU9FW9BPijiXLAfSB3uMDWM
cX78hla2UDll/B1yhUkN1gUR2CLcQUGGBKXirExGYROfPbWlQwSgcJuIgKrvi+az
lGbYJEX2orrOVgPBXYDN8goDLRey9tCi+ZX5IpqNiUFjiF2oQBykVMdyRmdKpLA6
twujVx6uC7uiodXsUJHghLq+N5RV3CeopB+7S7GEvfvNRG0ZM9qeitnLK9CJtVDs
WS1tAzUR+JqwOULK0savfzVbDpsOKyfbmYH9PfOVbh2NxNn96aP/KspmGnMFFxxJ
fdsCcRIqE+cdbdD7dmIW6BVV+KUTLezUoC2IOKmd4p6lfNJRxoo=
=Lcwv
-END PGP SIGNATURE-



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

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

[Sebastian Ramacher]

On 2024-04-02 07:13:38 +0100, Alastair McKinstry wrote:
> 
> On 01/04/2024 23:25, Sebastian Ramacher wrote:
> > > There is a transition to openmpi-5 / mpi-defaults which is stalled by the
> > > t64 transition.
> > > 
> > > It drops 32-bit support from OpenMPI.
> > > 
> > > Because of this, I don't think the solution is to  port 32-bit atomics for
> > > armel/armhf, as it will be removed in a few weeks/months.
> > > 
> > > While we didn't want the transitions to be done simultaneously, it might 
> > > be
> > > the best answer.
> > > 
> > > 
> > > What does the release team think?
> > Adding another transition on top will just delay the time_t transition
> > even more. So if we can avoid that, I'd prefer to not do this transition
> > now. Unfortunately, uploads such as the one of pmix that no dropped
> > support for 32 bit architectures (#1068211) are not really helpful.
> > 
> > Also, #1064810 has no information on test builds with the new
> > mpi-defaults on a 32 bit architecture. So has this transition been
> > tested?
> > 
> > Cheers
> 
> OpenMPI 5 drops 32-bit support, but otherwise does not change the API/ABI.
> So it is technically not a transition, but breaks 32-bit builds.

Doesn't make it better. This is not the time to do that without tests
builds and bugs filed.

> The solution is changing mpi-defaults to MPICH for 32-bit archs. MPICH
> builds on all archs, but testing all dependencies of the change has not been
> tested, and I don't know how you would do that - setting up eg ratt to
> rebuild all on 32-bit archs (as everything on 64-bit will not have changed.)

Beside the easy part of chaning mpi-defaults, I count 30 something
packages that have explicit build dependencies on libopenmpi-dev. None
of those packages has bugs filed to change to mpich on 32 bit
architectures.

To be honest, I don't see these two changes (changing mpi-defaults to
mpich on 32 bit; breaking 32 bit build of openmpi) to be ready. It'd be
preferable to reinstate a 32-bit compatible pmix and fix openmpi on 32
bit until the time_t transition is done.

Cheers
-- 
Sebastian Ramacher

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

[Michael Ivanov]

Package: dnf
Version: 4.14.0-4.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I have just tried to start up dnf and it aborts with a following error:

Traceback (most recent call last):
File "/usr/bin/dnf", line 61, in 
from dnf.cli import main
File "/usr/lib/python3/dist-packages/dnf/__init__.py", line 30, in 
import dnf.base
File "/usr/lib/python3/dist-packages/dnf/base.py", line 29, in 
import libdnf.transaction
File "/usr/lib/python3/dist-packages/libdnf/__init__.py", line 13, in

from . import module
File "/usr/lib/python3/dist-packages/libdnf/module.py", line 10, in 
from . import _module
ImportError: cannot import name '_module' from partially initialized module
'libdnf' (most likely due to a circular import) (/usr/lib/python3/dist-
packages/libdnf/__init__.py)

Python version is 3.11.8 (python package version is 3.11.8-3+b2)


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

Kernel: Linux 6.7.9-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dnf depends on:
ii dnf-data 4.14.0-4.1
ii libmodulemd2 2.14.0-3+b1
ii python3 3.11.8-1
ii python3-dbus 1.3.2-5+b2
ii python3-dnf 4.14.0-4.1
ii sqlite3 3.45.2-1

dnf recommends no packages.

dnf suggests no packages.

-- no debconf information

Bug#1068216: marked as done (aqemu, dependencies unsatisfiable on 32-bit non-i386 architectures.)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 19:49:13 +
with message-id 
and subject line Bug#1068216: fixed in aqemu 0.9.2-4
has caused the Debian Bug report #1068216,
regarding aqemu, dependencies unsatisfiable on 32-bit non-i386 architectures.
to be marked as done.

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

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


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

Package: aqemu
Version: 0.9.2-3
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, aqemu still
depends on libqt5dbus5. As a result it is uninstallable on
architectures that are undergoing the time64 transition
(armel, armhf and some debian-ports archictures).
--- End Message ---
--- Begin Message ---
Source: aqemu
Source-Version: 0.9.2-4
Done: Sebastian Ramacher 

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

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated aqemu 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, 02 Apr 2024 21:28:15 +0200
Source: aqemu
Architecture: source
Version: 0.9.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Sebastian Ramacher 
Closes: 1068216
Changes:
 aqemu (0.9.2-4) unstable; urgency=medium
 .
   * QA upload
   * debian/control:
 - Bump Standards-Version
 - Drop hard-coded dependency (Closes: #1068216)
Checksums-Sha1:
 7362509a9d5a8c2ed812609bda0c432b736269bc 1539 aqemu_0.9.2-4.dsc
 769057809db1f50279a5cf41a1664f45730b8bd1 19680 aqemu_0.9.2-4.debian.tar.xz
 2d71b2ae57f0ae3cf97f6e17250174f0108b4d40 11595 aqemu_0.9.2-4_amd64.buildinfo
Checksums-Sha256:
 3a9e5dcc0429c208c1a374a38b97c1bec8d166883d83b4fd2cc6dee1d3b939e0 1539 
aqemu_0.9.2-4.dsc
 0b26bfe63b0ed8861210a388278338521e0cfcc27fd3cdb7a40ad3276c957011 19680 
aqemu_0.9.2-4.debian.tar.xz
 beb075b301d56ebe4145174bacf33c9002c4c555ada4736fa7994ae3397ea2a3 11595 
aqemu_0.9.2-4_amd64.buildinfo
Files:
 a0e8605f606d11163ac5cb6f12af13a6 1539 x11 optional aqemu_0.9.2-4.dsc
 60f3ec63210c376858420f354cbae879 19680 x11 optional aqemu_0.9.2-4.debian.tar.xz
 2397a77dee56dec4f9e0497d06ce4325 11595 x11 optional 
aqemu_0.9.2-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZgxdMgAKCRAhk2s2YA/N
iRuZAP4xEOwJpOvOAmrj91E50oZlyP0bWedPWZ3OA+fv6UnQZwEAgqWjz/7zYzR+
+UJq8vZcIa/KGpT1IoPj91hXcO95vgk=
=S0Zq
-END PGP SIGNATURE-



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

Bug#1067326: mkdocstrings: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Dmitry Shachnev]

Hi Carsten!

On Wed, Mar 20, 2024 at 10:00:48PM +0100, Lucas Nussbaum wrote:
> Source: mkdocstrings
> Version: 0.24.1-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240319 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> [...]
>
> The full build log is available from:
> http://qa-logs.debian.net/2024/03/19/mkdocstrings_0.24.1-1_unstable.log

Upstream released 0.24.2 today, which should fix this failure [1].

[1]: https://github.com/mkdocstrings/mkdocstrings/commit/c0d009000678a2cc

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1065305: marked as done (brewtarget: switch to boost 1.83)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 19:19:14 +
with message-id 
and subject line Bug#1065305: fixed in brewtarget 3.0.11-1
has caused the Debian Bug report #1065305,
regarding brewtarget: switch to boost 1.83
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.)


-- 
1065305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: brewtarget
Version: 3.0.6-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

We'd like to release trixie without boost1.74 (see #1060102). Please
switch to the unversioned build dependencies or to boost1.83.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: brewtarget
Source-Version: 3.0.11-1
Done: Dr. Tobias Quathamer 

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

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

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated brewtarget 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, 02 Apr 2024 20:35:45 +0200
Source: brewtarget
Architecture: source
Version: 3.0.11-1
Distribution: unstable
Urgency: medium
Maintainer: Dr. Tobias Quathamer 
Changed-By: Dr. Tobias Quathamer 
Closes: 1065305
Changes:
 brewtarget (3.0.11-1) unstable; urgency=medium
 .
   * New upstream version 3.0.11
 - Refresh patch
   * Switch to unversioned libboost-dev for Build-Depends. (Closes: #1065305)
   * Add missing Build-Depends on libboost-stacktrace-dev
   * Update d/copyright
   * Update to Standards-Version 4.6.2, no changes needed
   * Update location of brewtarget.desktop in d/install
   * Use wrap-and-sort -at
Checksums-Sha1:
 61fbb009193d94349f43d91dbff38db92a4a320b 2044 brewtarget_3.0.11-1.dsc
 69d725bf2712c67caed0162611268eeb15fc2a05 13556382 brewtarget_3.0.11.orig.tar.gz
 321506816e06c5a0707b247a42f463603ff1980b 11232 
brewtarget_3.0.11-1.debian.tar.xz
 548a40301b20b9b518dfbe1dbcba7f476d5b3dab 14114 
brewtarget_3.0.11-1_amd64.buildinfo
Checksums-Sha256:
 098b5de2f55dcc071de3609fef217bed6bcd5c8e6c22a7a3ea2f1521b213a352 2044 
brewtarget_3.0.11-1.dsc
 fe797392fbe832b2ee8ee84e154877611a34891f9126e5ca69ea30ebc56b3b46 13556382 
brewtarget_3.0.11.orig.tar.gz
 9768f0031ae2809d1c69a19a4f185e0a3557a4416f4a7a2d7a3d8a9cbf8a1d01 11232 
brewtarget_3.0.11-1.debian.tar.xz
 55658b145540961f7e37376dd37796f70752e45a74cd5e7e8343eccd119d49bb 14114 
brewtarget_3.0.11-1_amd64.buildinfo
Files:
 f85b4e2e8f880458c2512bc9bd0498ab 2044 misc optional brewtarget_3.0.11-1.dsc
 343bbc9ea7c6101f57349c59aa08b0f0 13556382 misc optional 
brewtarget_3.0.11.orig.tar.gz
 c138956757ad37a839d69874292f0e35 11232 misc optional 
brewtarget_3.0.11-1.debian.tar.xz
 b03b7b6e9253a8fd42833ea46276d832 14114 misc optional 
brewtarget_3.0.11-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAmYMVAQACgkQEwLx8Dbr
6xnHJA//XftsLw/4UYnsFsgM3fUOSELavx4PmTibEQGD/7PP7K7rhQNS2SgzhonV
gxg9LNUeHf2lKNUw65i8lCq4MWoECRW0u/VIJ3RX7CMgdxXEaW79HhauT2gF7SWq
OKVV+ZuiQKwi3zFPgyDEoPUUp6L0aiMi96el54vIfEs/Mss2rsQNEcXTQyCUgpUG
tYG4ob8m0cmvULtP+h/7GEOUo0CcjMEvKc0LgzyjXB0zgy0qKyUSyJrZ5SLXPAiP
Zn2rOKeziqr7CYGO7ypFHI2S0CT/H0sEmV4iBzYB7vI4Dlps3rC2wizFCmqA9d7b
f1qrp3ooVOxTd1DiQuGjaimMtXk9tYWiE4ioFv/+GPVFtduS4guCDg4Qbv9HK8hx
VlGmPnS2foT2ht8G+jxAUKj11CbHsdwSrB1gJw4GrqIBAtlWpHU40oiarohxmqJt
qrmP9W/x2PryoR5gCjQOFONt5zWi+zpJcAY5PmKqRQ+3CZcp8sGq3rmCBp8AzJT/
4Zz0ti+TGtIxoBFHvt/z7ifl7meD10bF25IvF6Yyr0Yudtw5iNY0yHErr3NS27Tm
oDN5VcO5VOcdSFBlWFfcudIxygR1aDVBpzhaOKE/NoQ9LmluSxZR/ArbFiT0jOZh
wa9YR3yRxungrZi0dL0H2d3N/KUfahYHJNreoY/wlY7Lx8ucc0M=
=XzZ+
-END PGP SIGNATURE-



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

Processed: Re: Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

[Debian Bug Tracking System]

Processing control commands:

> found -1 glibc/2.37-15.1
Bug #1068188 [glibc-doc] pthread_cond_init.3.gz: conflict with manpages-dev 
6.7-1
Marked as found in versions glibc/2.37-15.1.

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

Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

[Aurelien Jarno]

control: found -1 glibc/2.37-15.1

Hi,

On 2024-04-01 16:23, Alejandro Colomar wrote:
> Package: glibc-doc
> Version: 2.38-6
> Severity: serious
> Justification: Policy 7.4
> X-Debbugs-Cc: a...@kernel.org, mar...@debian.org
> 
> Dear Maintainer,
> 
> The Linux man-pages project has recently added the pthread_*(3) manual
> pages that were provided by glibc-doc.  The first upstream version of
> the Linux man-pages that includes these pages is man-pages-6.06.  Here's
> what was added:

Thanks, that sounds great that we can finally get rid out of those in
the debian package.

>   $ git diff --stat b06cd070f..128a3ae35
>man3/pthread_cond_init.3| 264 
>man3/pthread_condattr_init.3|  48 
>man3/pthread_key_create.3   | 178 +
>man3/pthread_mutex_init.3   | 241 ++
>man3/pthread_mutexattr_setkind_np.3 |  52 
>man3/pthread_once.3 |  44 
>6 files changed, 827 insertions(+)
> 
> Debian's manpages-dev_6.7-1_all.deb has been the first package since
> that happened, and I've noticed that dpkg(1) (via apt-get(8)) refuses to
> upgrade manpages-dev due to a conflict with glibc-doc.
> 
>   $ sudo apt-get upgrade -V;
>   [...]
>   Do you want to continue? [Y/n] y
>   Reading changelogs... Done
>   (Reading database ... 404853 files and directories currently installed.)
>   Preparing to unpack .../manpages-dev_6.7-1_all.deb ...
>   Unpacking manpages-dev (6.7-1) over (6.05.01-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/manpages-dev_6.7-1_all.deb (--unpack):
>trying to overwrite '/usr/share/man/man3/pthread_cond_init.3.gz', 
> which is also in package glibc-doc 2.38-6
>   Errors were encountered while processing:
>/var/cache/apt/archives/manpages-dev_6.7-1_all.deb
>   needrestart is being skipped since dpkg has failed
>   E: Sub-process /usr/bin/dpkg returned an error code (1)

I think this is actually not specific to the experimental version, those
manpages are also in the unstable version.

> Please, remove from glibc-doc those manual pages that conflict with
> manpages-dev.

Noted. However following the time_t transition, the glibc package does
not build anymore on 32-bit architectures (i have just opened #1059937
to make people aware of that), so uploading a new glibc now is probably
not the best idea.

Regards
Aurelien

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

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

[Aurelien Jarno]

Source: glibc
Version: 2.37-15.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-...@lists.debian.org

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

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

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

Bug#1068213: marked as done (gnome-remote-desktop: hard-coded dependency on pre-t64 library)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 18:04:25 +
with message-id 
and subject line Bug#1068213: fixed in gnome-remote-desktop 44.2-8
has caused the Debian Bug report #1068213,
regarding gnome-remote-desktop: hard-coded dependency on pre-t64 library
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.)


-- 
1068213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-remote-desktop
Version: 44.2-7
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

gnome-remote-desktop builds a binary pckage with a hard-coded dependy on
libmutter-12-0. This library was renamed as part of the time_t 64
transition. Please update the dependencies accordingly.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gnome-remote-desktop
Source-Version: 44.2-8
Done: Jeremy Bícha 

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gnome-remote-desktop 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 02 Apr 2024 13:56:27 -0400
Source: gnome-remote-desktop
Built-For-Profiles: noudeb
Architecture: source
Version: 44.2-8
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1068213
Changes:
 gnome-remote-desktop (44.2-8) unstable; urgency=medium
 .
   * Update Depends: libmutter-12-0 to libmutter-12-0t64 (Closes: #1068213)
Checksums-Sha1:
 1598bc585390d2eab281c9f06aeb1ee137866c1c 2692 gnome-remote-desktop_44.2-8.dsc
 e8ec57a750a66ce8337fd80b2c5226d749f6becd 6816 
gnome-remote-desktop_44.2-8.debian.tar.xz
 5a6d951f27b349185e7d4c27df86665a9e0665f2 18325 
gnome-remote-desktop_44.2-8_source.buildinfo
Checksums-Sha256:
 5b184bd749e79216127cf436fffd1a6c43e94b61ed8cf2f78879cb41387de667 2692 
gnome-remote-desktop_44.2-8.dsc
 0b21454ce8360d5f2557144551f656009c46898c4a02a0a30f087f4a853631b9 6816 
gnome-remote-desktop_44.2-8.debian.tar.xz
 0ff82817da1b83d1230de2104d5313d5788546b48c0c7ab0184509304f765a7c 18325 
gnome-remote-desktop_44.2-8_source.buildinfo
Files:
 7d555d8fa3618924195ee60b20ae8913 2692 gnome optional 
gnome-remote-desktop_44.2-8.dsc
 e2ad86fe748acabc7be041e5b44a908e 6816 gnome optional 
gnome-remote-desktop_44.2-8.debian.tar.xz
 2a3b79614e05e7f76f40297267dbfbfd 18325 gnome optional 
gnome-remote-desktop_44.2-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmYMRuYACgkQ5mx3Wuv+
bH1O6A//a0gKbPGV4G5CAvnvDA4attvubR2p5vxRniBpsWiLLci7GvUSLGQKjjWu
/T46EvNjIyk9qHA8voW7ZxRWkfONyg6r9szFJoXKJXwYn2RSEET0n6Qz7mc6dn0x
6LWAgFKk7YNFR+2kUz/HhM3RYk2O+vIsxtr+B7TMDLvhyxVeRweMVskBKiIPEOya
O9kBiDZnl/k9qMtc9E04akLrdvp1QMIjT5Bhuf/+BrqZDsaO4Jvboeecp5wKV8zZ
bIt/aPj70WnFt9Yp/My4LyCBs6BRR3AW8b2PpkozgjcClj6FWj104eJgDpLFEFfJ
BGwJKQrYHIyD0khlgD71IZpcsXkzSAew/+1QZD2kfyohtvLVGiiztycaEGkyftgm
YezyW86JhVC9mH8I9wljt5nkCTuxFlETiYD4Izy4xnYV4kAUztSqbvMQSwsL5K24
ci7jqcBFBYJ+vpuTtkZcMr+u8F/PI4Sh3+SsH+GMtIQZSrN2VuBrvvpyaLLfNGVB
SBwji8BsbXPYZttvNrceVC3SEclzG5G4Po5m92KrvSfiAM3s509Ty6QF90PW/SEZ
F3gEWl+70NXPfyvpF6RZh5pXmFgaJRFj0ZBH2vibGIBb3TwtYscKSFY1+75wzO0k
m0ordglEQyKotuhwFFFD5zPBVViuwurJ3uYjxj5oWQq3hTy6W7c=
=oHbm
-END PGP SIGNATURE-



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

Processed: Re: Bug#1068016: bookworm-pu: package node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - confirmed + moreinfo
Bug #1068016 [release.debian.org] bookworm-pu: package 
node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2
Removed tag(s) confirmed.
Bug #1068016 [release.debian.org] bookworm-pu: package 
node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2
Added tag(s) moreinfo.
> block -1 with 1063530
Bug #1068016 [release.debian.org] bookworm-pu: package 
node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2
1068016 was not blocked by any bugs.
1068016 was blocking: 1037234
Added blocking bug(s) of 1068016: 1063530

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

Bug#1068166: marked as done (manpages-dev: Fails to upgrade due to file conflict)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 16:50:01 +
with message-id 
and subject line Bug#1068166: fixed in manpages 6.7-2
has caused the Debian Bug report #1068166,
regarding manpages-dev: Fails to upgrade due to file conflict
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.)


-- 
1068166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: manpages
Version: 6.05.01-1
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

manpages-dev failed to upgrade due to a conflict with glibc-doc:

 Unpacking manpages-dev (6.7-1) over (6.05.01-1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/manpages-dev_6.7-1_all.deb (--unpack):
  trying to overwrite '/usr/share/man/man3/pthread_cond_init.3.gz', which is 
also in package glibc-doc 2.37-15.1
 Errors were encountered while processing:
  /var/cache/apt/archives/manpages-dev_6.7-1_all.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)

Breaks/Replaces will need to be added if the file was moved, but it seems that 
only one of these packages should include this manpage.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: manpages
Source-Version: 6.7-2
Done: Marcos Fouces 

We believe that the bug you reported is fixed in the latest version of
manpages, 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.
Marcos Fouces  (supplier of updated manpages 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, 02 Apr 2024 18:20:34 +0200
Source: manpages
Architecture: source
Version: 6.7-2
Distribution: unstable
Urgency: medium
Maintainer: Dr. Tobias Quathamer 
Changed-By: Marcos Fouces 
Closes: 1068166
Changes:
 manpages (6.7-2) unstable; urgency=medium
 .
   [ Marcos Fouces ]
   * Add breaks/replace in manpage-dev (Thanks to Andreas Beckman).
 .
   [ Sven Joachim ]
   * d/check-conflicts: avoid large temporary file
   * d/check-conflicts: also check for manpages in arch:all packages
   * Update d/rules with check-conflicts script (Closes: #1068166)
Checksums-Sha1:
 054ba81fbb4e5880356bb23e4bf1a57f0ffdecc9 2098 manpages_6.7-2.dsc
 968c513229bce22dbcb56e1c251c0511c13b2707 60216 manpages_6.7-2.debian.tar.xz
 c93924e7fc36555370974f63035db3ca8cb8dd70 9448 manpages_6.7-2_source.buildinfo
Checksums-Sha256:
 1e8e0b48c1eb18b0cc999fd99e09e46f711377fe1ee9bd077950820fe45a88c9 2098 
manpages_6.7-2.dsc
 0aba1407d1faa2601178e71a67395b688748c4976c102ae43e9a3b4c70507a93 60216 
manpages_6.7-2.debian.tar.xz
 68bc1415bcbd2de3c738672961dd7b9c2148bfd8ffe5b1c1779d707509584da6 9448 
manpages_6.7-2_source.buildinfo
Files:
 d561409c06dbaed5a56b68e163ba1a5b 2098 doc standard manpages_6.7-2.dsc
 5da3d779634e32dda9a5e8e70e019a9c 60216 doc standard 
manpages_6.7-2.debian.tar.xz
 ad54d43128593ee1b84890df4c381e71 9448 doc standard 
manpages_6.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfLiv/VYDL+NaNH0uasy9D6O3RHwFAmYMMRoACgkQasy9D6O3
RHwc2w//fjpEG9u+BXzb9IXYR3Ts+MZmIaKeZzPHZr+TO2lKRiEDBCrVjTcIaR9I
Ryxp9pOJJQFvpZwFaxaO/v71Huy3K1N6rh6AqhCc2YhuvCqrZCM4l3fEX5Uy86oI
2Epxrl/ePXghv2fMhiu536IXRmfBZ6w55XPqfik7A7AMYJLerkHHBRvLOYI0Dlir
rKJOEVq5d9RJQi/ASQS3n2vIHR1B+6FdemFFf8gWUoemutuZwQcuBU+3E5uq7V49
ggnrbS/8BLGP3myOp/fSTbfjSpUOj82grkGZI1UjmxDo66aOwx0ehhWEzHpwCRXZ
dPI6mCD8WtIGLKfGyMiMD9UloVgb4SeePWvDLRe6XDGJnwqKbgOlfJCWicyWvsZC
krx9nH7ls4QxATMi+U7ED8drjPrrgWImSpsb9x9QWN7SvPPQGpiQSsshj8hsIMQb
VTuu8O3kXDcWMJl2Px4ZvZ7ZlWvg0xzEMoYS5NU9uY2HNMrZlV5hico8uqesf4w9
tVei2KPT2Wk7JblPumKaBlqUPtxKTbPlM/87upiAspTxdt3zGN2Q0Ct4Sb5VDQqU
IegHzMVS4m9gJrMcoGnUkjnLluHPZV5GU6AAeD5bLQE+PH4XKrS9Bn+rgyKtaLYw
6W3ZTxez7OdRw4fjCjr3plp2c1BdOLdceroxaxeDXniT3yY7SkA=
=VfFT
-END PGP SIGNATURE-



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

Bug#1068167: marked as done (manpages-dev: Update to 6.7-1 fails)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 16:50:01 +
with message-id 
and subject line Bug#1068166: fixed in manpages 6.7-2
has caused the Debian Bug report #1068166,
regarding manpages-dev: Update to 6.7-1 fails
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.)


-- 
1068166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: manpages-dev
Version: 6.05.01-1
Severity: important
X-Debbugs-Cc: sidto...@gmail.com

Dear Maintainer,

System update failed due to this.

Preparing to unpack .../03-manpages_6.7-1_all.deb ...
Unpacking manpages (6.7-1) over (6.05.01-1) ...
Preparing to unpack .../04-manpages-dev_6.7-1_all.deb ...
Unpacking manpages-dev (6.7-1) over (6.05.01-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-oRcZxm/04-manpages-
dev_6.7-1_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man3/pthread_cond_init.3.gz', which is
also in package glibc-doc 2.37-15.1


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

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

Versions of packages manpages-dev depends on:
iu  manpages  6.7-1

manpages-dev recommends no packages.

Versions of packages manpages-dev suggests:
it  man-db [man-browser]  2.12.0-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: manpages
Source-Version: 6.7-2
Done: Marcos Fouces 

We believe that the bug you reported is fixed in the latest version of
manpages, 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.
Marcos Fouces  (supplier of updated manpages 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, 02 Apr 2024 18:20:34 +0200
Source: manpages
Architecture: source
Version: 6.7-2
Distribution: unstable
Urgency: medium
Maintainer: Dr. Tobias Quathamer 
Changed-By: Marcos Fouces 
Closes: 1068166
Changes:
 manpages (6.7-2) unstable; urgency=medium
 .
   [ Marcos Fouces ]
   * Add breaks/replace in manpage-dev (Thanks to Andreas Beckman).
 .
   [ Sven Joachim ]
   * d/check-conflicts: avoid large temporary file
   * d/check-conflicts: also check for manpages in arch:all packages
   * Update d/rules with check-conflicts script (Closes: #1068166)
Checksums-Sha1:
 054ba81fbb4e5880356bb23e4bf1a57f0ffdecc9 2098 manpages_6.7-2.dsc
 968c513229bce22dbcb56e1c251c0511c13b2707 60216 manpages_6.7-2.debian.tar.xz
 c93924e7fc36555370974f63035db3ca8cb8dd70 9448 manpages_6.7-2_source.buildinfo
Checksums-Sha256:
 1e8e0b48c1eb18b0cc999fd99e09e46f711377fe1ee9bd077950820fe45a88c9 2098 
manpages_6.7-2.dsc
 0aba1407d1faa2601178e71a67395b688748c4976c102ae43e9a3b4c70507a93 60216 
manpages_6.7-2.debian.tar.xz
 68bc1415bcbd2de3c738672961dd7b9c2148bfd8ffe5b1c1779d707509584da6 9448 
manpages_6.7-2_source.buildinfo
Files:
 d561409c06dbaed5a56b68e163ba1a5b 2098 doc standard manpages_6.7-2.dsc
 5da3d779634e32dda9a5e8e70e019a9c 60216 doc standard 
manpages_6.7-2.debian.tar.xz
 ad54d43128593ee1b84890df4c381e71 9448 doc standard 
manpages_6.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfLiv/VYDL+NaNH0uasy9D6O3RHwFAmYMMRoACgkQasy9D6O3
RHwc2w//fjpEG9u+BXzb9IXYR3Ts+MZmIaKeZzPHZr+TO2lKRiEDBCrVjTcIaR9I
Ryxp9pOJJQFvpZwFaxaO/v71Huy3K1N6rh6AqhCc2YhuvCqrZCM4l3fEX5Uy86oI
2Epxrl/ePXghv2fMhiu536IXRmfBZ6w55XPqfik7A7AMYJLerkHHBRvLOYI0Dlir
rKJOEVq5d9RJQi/ASQS3n2vIHR1B+6FdemFFf8gWUoemutuZwQcuBU+3E5uq7V49
ggnrbS/8BLGP3myOp/fSTbfjSpUOj82grkGZI1UjmxDo66aOwx0ehhWEzHpwCRXZ
dPI6mCD8WtIGLKfGyMiMD9UloVgb4SeePWvDLRe6XDGJnwqKbgOlfJCWicyWvsZC
krx9nH7ls4QxATMi+U7ED8drjPrrgWImSpsb9x9QWN7SvPPQGpiQSsshj8hsIMQb
VTuu8O3kXDcWMJl2Px4ZvZ7ZlWvg0xzEMoYS5NU9uY2HNMrZlV5hico8uqesf4w9

Bug#1066194: marked as done (nstreams: FTBFS: parse_tcpdump.c:262:50: error: implicit declaration of function ‘int2proto’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 16:34:58 +
with message-id 
and subject line Bug#1066194: fixed in nstreams 1.0.4-1.1
has caused the Debian Bug report #1066194,
regarding nstreams: FTBFS: parse_tcpdump.c:262:50: error: implicit declaration 
of function ‘int2proto’ [-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.)


-- 
1066194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nstreams
Version: 1.0.4-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 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -I/usr/include/pcap  -I/usr/include -I/<>/includes -c 
> parse_tcpdump.c
> parse_tcpdump.c: In function ‘parse_tcpdump_line’:
> parse_tcpdump.c:262:50: error: implicit declaration of function ‘int2proto’ 
> [-Werror=implicit-function-declaration]
>   262 |  ret->src = ascaddr2intaddr(src, >ports[0], 
> int2proto(ret->proto));
>   |  ^
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:17: parse_tcpdump.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/nstreams_1.0.4-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: nstreams
Source-Version: 1.0.4-1.1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
nstreams, 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.
Bastian Germann  (supplier of updated nstreams 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, 23 Mar 2024 14:59:32 +
Source: nstreams
Architecture: source
Version: 1.0.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Joerg Jaspert 
Changed-By: Bastian Germann 
Closes: 939158 1007384 1066194
Changes:
 nstreams (1.0.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Convert to source format 3.0 (Closes: #1007384)
   * Declare missing function prototype (Closes: #1066194)
 .
   [ Helmut Grohne ]
   * FTCBFS: Let dpkg's buildtools.mk supply a CC to configure (Closes: #939158)
Checksums-Sha1:
 9b244705e4b27c48cc046989a546602791a65dbf 1542 nstreams_1.0.4-1.1.dsc
 ee43ae6f6cadf0ee9549490b8f9e642ea63e7542 3592 nstreams_1.0.4-1.1.debian.tar.xz
 cbe6dec0a1ca90f3c27099620b98d94806876c4d 6360 
nstreams_1.0.4-1.1_source.buildinfo
Checksums-Sha256:
 911789a5ab01fc455a1af78109758479c399b41e3a0fbfe0cf23d39faf62b98a 1542 
nstreams_1.0.4-1.1.dsc
 ac4c1eb098aea86e451a5ddbcf85faaed77b79630ca7633c5fd8a4f301db8324 3592 
nstreams_1.0.4-1.1.debian.tar.xz
 dabf7c8cb3b549220aedb73bee5cccba40d21b2d017c7e77782cd9c7d36aec13 6360 
nstreams_1.0.4-1.1_source.buildinfo
Files:
 b38143acd27ce15e6648e6df3bfdd2c7 1542 net optional nstreams_1.0.4-1.1.dsc
 

Bug#1064170: mediastreamer2: NMU diff for 64-bit time_t transition

[Dennis Filder]

X-Debbugs-CC: Steve Langasek , Sebastian Ramacher 


Can I get confirmation that this will get uploaded before the
autoremoval from testing on April 15th?  Message #17 has the fixed NMU
patch.

Regards.

Processed: retitle 1059088 to whizzytex 1.3.7 is incompatible with texlive >= 2021, fixed 1059088 in 1.4.0-1 ...

[Debian Bug Tracking System]

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

> retitle 1059088 whizzytex 1.3.7 is incompatible with texlive >= 2021
Bug #1059088 [whizzytex] whizzytex: deb file error
Changed Bug title to 'whizzytex 1.3.7 is incompatible with texlive >= 2021' 
from 'whizzytex: deb file error'.
> fixed 1059088 1.4.0-1
Bug #1059088 [whizzytex] whizzytex 1.3.7 is incompatible with texlive >= 2021
Marked as fixed in versions whizzytex/1.4.0-1.
> tags 1059088 + bookworm sid trixie experimental
Bug #1059088 [whizzytex] whizzytex 1.3.7 is incompatible with texlive >= 2021
Added tag(s) bookworm, experimental, sid, and trixie.
> tags 1058828 + sid trixie
Bug #1058828 {Done: Chris Hofstaedtler } 
[src:thunderbolt-tools] thunderbolt-tools: installs tbtacl-write twice when 
udev.pc changes
Added tag(s) sid and trixie.
> tags 813866 + sid trixie
Bug #813866 [php-fdomdocument] Useless in Debian
Added tag(s) trixie and sid.
> tags 813865 + sid trixie
Bug #813865 [php-fxsl] Useless in Debian
Added tag(s) trixie and sid.
> tags 813861 + sid trixie
Bug #813861 [phpdox] Useless in Debian
Added tag(s) sid and trixie.
> tags 1059175 + sid trixie
Bug #1059175 {Done: Picca Frédéric-Emmanuel } [src:dials] 
dials: FTBFS: Imported target "DXTBX::DXTBX" includes non-existent path
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Processed: Re: python-meshplex: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-args=--ignore-glob=\*test_io\* returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 ftbfs
Bug #1067308 [src:python-meshplex] python-meshplex: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" 
--test-args=--ignore-glob=\*test_io\* returned exit code 13
Ignoring request to alter tags of bug #1067308 to the same tags previously set

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

Bug#1067308: python-meshplex: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-args=--ignore-glob=\*test_io\* returned exit code 13

[Drew Parsons]

Source: python-meshplex
Followup-For: Bug #1067308
Control: tags -1 ftbfs

I can't reproduce this error now.  It must have been resolved by a
separate library transition, or possibly a numpy update.

If 0.17.1-3 passes tests successfully then we can close this bug.

Bug#1068243: marked as done (bsdgames: fails to configure)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 16:19:37 +
with message-id 
and subject line Bug#1068243: fixed in bsdgames 2.17-32
has caused the Debian Bug report #1068243,
regarding bsdgames: fails to configure
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.)


-- 
1068243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bsdgames
Version: 2.17-31
Severity: serious

Your package fails to configure in a fresh installation (but not when
upgrading from a previous version).  This is what happens in a throwaway
chroot (unrelated lines stripped from apt/dpkg output):

,
| # apt install bsdgames
| Selecting previously unselected package bsdgames.
| Preparing to unpack .../bsdgames_2.17-31_amd64.deb ...
| Unpacking bsdgames (2.17-31) ...
| Setting up bsdgames (2.17-31) ...
| cp: cannot stat '/usr/share/games/bsdgames/phantasia/void': No such file or 
directory
| dpkg: error processing package bsdgames (--configure):
|  installed bsdgames package post-installation script subprocess returned 
error exit status 1
| Errors were encountered while processing:
|  bsdgames
| E: Sub-process /usr/bin/dpkg returned an error code (1)
`

See also the Salsa CI job at [1].


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


1. https://salsa.debian.org/games-team/bsdgames/-/jobs/5528281
--- End Message ---
--- Begin Message ---
Source: bsdgames
Source-Version: 2.17-32
Done: Dr. Tobias Quathamer 

We believe that the bug you reported is fixed in the latest version of
bsdgames, 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.
Dr. Tobias Quathamer  (supplier of updated bsdgames 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, 02 Apr 2024 17:53:12 +0200
Source: bsdgames
Architecture: source
Version: 2.17-32
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Dr. Tobias Quathamer 
Closes: 1068243
Changes:
 bsdgames (2.17-32) unstable; urgency=medium
 .
   * Remove phantasia files from pre- and postinst. Closes: #1068243
Checksums-Sha1:
 ea21de84581728cb65681e29847737c8e7cbb6a2 1933 bsdgames_2.17-32.dsc
 e575c925276e54ea8df8dd6aa03096c767327c12 67744 bsdgames_2.17-32.debian.tar.xz
 30173e1bd5b0ef7b05559669f4e68abae5f388d9 7004 bsdgames_2.17-32_amd64.buildinfo
Checksums-Sha256:
 b3b082c697acbc40d8206a3a1de8e13ce7cb442a58d672f6624519a65f10d46e 1933 
bsdgames_2.17-32.dsc
 5c33b61b8585edeafc24cee73aa4296c9230ef390bf659812d0d93c70ded4e52 67744 
bsdgames_2.17-32.debian.tar.xz
 ecca2c8bfe4ca8f277b29c96bae20c8369510401a2dabebe137248f9fa0356c4 7004 
bsdgames_2.17-32_amd64.buildinfo
Files:
 903fc8d3faaba233cf7f21b1eacf2dc4 1933 games optional bsdgames_2.17-32.dsc
 f8b3b5ce964988a727eb938d19a88d98 67744 games optional 
bsdgames_2.17-32.debian.tar.xz
 2452d0851d9c41ddc31b725670ecd24d 7004 games optional 
bsdgames_2.17-32_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAmYMLRkACgkQEwLx8Dbr
6xmeEg//V8tCEZu8mfGiCwvQ+CXKkinUmQGhfu8OyjdfXBb4iz165j48ElllnecN
frqdCkLsSH9MhzxPveDmbJn6KkObrjyDEwli8Sxwl6yYjW+NAjsA+VCVH1V/3dIZ
L2Q5nmASMjYVVdXVjmcLfBCDq8OilwvFxobTjTxJIibSQS3hH1Y87NDVp9GR5jjI
yZBrIkbZBvlhQRvWaAnLiG2dVylPx6j7FZKHlL2CAsDfkJ91+h88pYyKCoHRM1cx
VDcqgURA9O/+UztXzXF137kCuqL66n48Np3ZXi24pQrWk5SU73FWFMdWk8vc3Xhl
yDj8lMRXPDrtbkwsfZ2ARHyNiFLdqKUIJOs7UqJ0jryH9qNJ44nnlesPYWY0w25t
FQiTr2a7sFQkBPJTd207/CVGg3JVhV41votudLEQFotDgmnKEHu8WF3cxnJDEjQt
E/qK+SIdisDE2yLitCKuuFDOICRL0gNT6m9gm4NaI7Y1qIbmC6c7IBLax34hDtr9
VCAKq4umXNSMBvJkj8nvWa2VrHSduCyj4ce6GjGsD3bltLDOCFYkvpM2oMti0Cg1
DhTXzjGn4exfrBZxZgtkZYByzRUF+JDtSwkTO4Fckw+3sRwN39fN+faXnkcuDaG2
+OK9R2P52ApSqVawEIYVKpJo9qvSnRLH16iM1g2+DUB0PEoX47c=
=Qa2t
-END PGP SIGNATURE-



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

Bug#1067378: marked as done (python-docs-theme: FTBFS: make: *** [debian/rules:4: build] Error 25)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 16:07:18 +
with message-id 
and subject line Bug#1067378: fixed in python-docs-theme 2024.3-1
has caused the Debian Bug report #1067378,
regarding python-docs-theme: FTBFS: make: *** [debian/rules:4: build] 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.)


-- 
1067378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-docs-theme
Version: 2024.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=pybuild --with python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> E: pybuild pybuild:389: configure: plugin pyproject failed with: PEP517 
> plugin dependencies are not available. Please Build-Depend on 
> pybuild-plugin-pyproject.
> dh_auto_configure: error: pybuild --configure -i python{version} -p 3.11 
> returned exit code 13
> make: *** [debian/rules:4: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/python-docs-theme_2024.2-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-docs-theme
Source-Version: 2024.3-1
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
python-docs-theme, 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.
Matthias Klose  (supplier of updated python-docs-theme 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, 02 Apr 2024 17:43:53 +0200
Source: python-docs-theme
Built-For-Profiles: noudeb
Architecture: source
Version: 2024.3-1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 1067378
Changes:
 python-docs-theme (2024.3-1) unstable; urgency=medium
 .
   * New upstream version.
   * Build-depend on pybuild-plugin-pyproject. Closes: #1067378.
Checksums-Sha1:
 cca3d905051a7604f9873c6217f53007c4946a0b 1920 python-docs-theme_2024.3-1.dsc
 6f7b7752558e452972bdaf7ba7ca49bc03a247e6 20561 
python-docs-theme_2024.3.orig.tar.gz
 fa1471d3f757c752755e55689b50058c4c60a296 14208 
python-docs-theme_2024.3-1.debian.tar.xz
 c493d59dc7669aa918220c69ce1f45679d41af3e 8949 
python-docs-theme_2024.3-1_source.buildinfo
Checksums-Sha256:
 05eeaa0785a7a5a4d74ea9ae674821f2368fbba65a7e0fd297dfd9b3e790e60f 1920 
python-docs-theme_2024.3-1.dsc
 9728c4591da7fff8377214acd0d3c6bde826214f8a2dc7052c594d663d7e1cc2 20561 
python-docs-theme_2024.3.orig.tar.gz
 f54e9fda517d5c37f992302279479113a0ff6f12aadb43d23f530afa4eec32be 14208 
python-docs-theme_2024.3-1.debian.tar.xz
 252c4fd9c2594d28ef93a1139de8308de5ab00ce9f9fc4ecfdacd4219888ef11 8949 
python-docs-theme_2024.3-1_source.buildinfo
Files:
 c27683bd991218231e6528292146e190 1920 python optional 
python-docs-theme_2024.3-1.dsc
 fa4fbc12b4b937ae2ac6240795cfd1ee 20561 python optional 
python-docs-theme_2024.3.orig.tar.gz
 d0154744d8f62054bc000677e239a70e 14208 python optional 
python-docs-theme_2024.3-1.debian.tar.xz
 d6d16e034ea6c7fde6cceceefbe35369 8949 python optional 
python-docs-theme_2024.3-1_source.buildinfo

Bug#1068243: bsdgames: fails to configure

[Dr. Tobias Quathamer]

Am 02.04.24 um 17:19 schrieb Sven Joachim:

Package: bsdgames
Version: 2.17-31
Severity: serious

Your package fails to configure in a fresh installation (but not when
upgrading from a previous version).  This is what happens in a throwaway
chroot (unrelated lines stripped from apt/dpkg output):


Hi Sven,

thanks for the report, I've just discovered that issue at the time time 
as your bug report came in. :-)


It's fixed already, the upload is on its way.

Regards,
Tobias



OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 15:53:44 +
with message-id 
and subject line Bug#1067076: fixed in x11vnc 0.9.16-10
has caused the Debian Bug report #1067076,
regarding x11vnc: FTBFS on arm{el,hf}: uinput.c:723:25: error: ‘struct 
input_event’ has no member named ‘time’
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=x11vnc=armhf=0.9.16-9%2Bb1=1710639780=0

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

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: x11vnc
Source-Version: 0.9.16-10
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
x11vnc, 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.
Mike Gabriel  (supplier of updated x11vnc 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, 02 Apr 2024 17:32:02 +0200
Source: x11vnc
Architecture: source
Version: 0.9.16-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Closes: 1067076
Changes:
 x11vnc (0.9.16-10) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Michael Hudson-Doyle ]
   * debian/patches:
 + Add 0007-use-clock_gettime-to-replace-gettimeofday.patch. Fix FTBFS
   related to time_64t transition. (Closes: #1067076).
 .
   [ Mike Gabriel ]
   * debian/control:
 + Bump Standards-Version: to 4.6.2. No changes needed.
Checksums-Sha1:
 3556e9fba7a25158af969a8e7e6aa25495d6d934 2212 x11vnc_0.9.16-10.dsc
 7789ea269e5456883379a00916e1897412226ea7 23736 x11vnc_0.9.16-10.debian.tar.xz
 c2b8c341c496ca371d9267131f3a00848354d4d5 7575 x11vnc_0.9.16-10_source.buildinfo
Checksums-Sha256:
 11b6e968d1d6e89302d5b3ba7d10cf1558212a17beff713479ba5bac0251347f 2212 
x11vnc_0.9.16-10.dsc
 602731fcb3873ed5133b037b15b1debfd8ce1a4182795759ca5e1bee20b9d485 23736 
x11vnc_0.9.16-10.debian.tar.xz
 00226b659a72c8cc6e4359420e02fe14df68afb61a66c616ab4fa8ea8a280a4d 7575 
x11vnc_0.9.16-10_source.buildinfo
Files:
 6ef8b5f8913b960109b168322a743f3f 2212 x11 optional x11vnc_0.9.16-10.dsc
 4a0a01321086c335074bb760b3331634 23736 x11 optional 
x11vnc_0.9.16-10.debian.tar.xz
 606d7e119efc0a6a802153badd84a035 7575 x11 optional 
x11vnc_0.9.16-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmYMJYkVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxtV0P/3utrHP4q7E+rRfm+cdQPn0GQqFy
ZtDa0SDjSfGbmi1KBPLx5IoJacCSA3luBVs8Y+c75+NTQtMNR+za+c0C7wb1UgUy
SOp5gmTXIzmgkVDHBXHl1W6OCbVc/VZmLMFq34GxXNBVYCgdAUIs1joyJ9C31sqR
erviMBZz50ejaoyEjxgTpogsRAkgIeRNUWmTjxLymjbMFuA/QmiirS+IB/2iHwQL
3TIkDYoYxZw3p3RmxPCAdSujmbtOUFQGW02JC+ocB+EZ5Ym9qfUECoT3lJJQWLja

Processed: Bug#1067076 marked as pending in x11vnc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067076 [src:x11vnc] x11vnc: FTBFS on arm{el,hf}: uinput.c:723:25: error: 
‘struct input_event’ has no member named ‘time’
Added tag(s) pending.

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

Bug#1067076: marked as pending in x11vnc

[Mike Gabriel]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-remote-team/x11vnc/-/commit/8bc94652676a6e4d700ab2c5b6850876dab2796f


debian/patches: Add 0007-use-clock_gettime-to-replace-gettimeofday.patch. Fix 
FTBFS related to time_64t transition. (Closes: #1067076).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067076

Bug#1067391: marked as done (bitlbee-facebook: redundant dependency on libglib2.0-0)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 15:34:22 +
with message-id 
and subject line Bug#1067391: fixed in bitlbee-facebook 1.2.2-3
has caused the Debian Bug report #1067391,
regarding bitlbee-facebook: redundant dependency on libglib2.0-0
to be marked as done.

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

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


-- 
1067391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bitlbee-facebook
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com

Dear Maintainer,

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


  * Remove explicit depedency on libglib2.0-0.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru bitlbee-facebook-1.2.2/debian/control 
bitlbee-facebook-1.2.2/debian/control
--- bitlbee-facebook-1.2.2/debian/control   2024-03-08 16:56:22.0 
+1300
+++ bitlbee-facebook-1.2.2/debian/control   2024-03-21 10:47:15.0 
+1300
@@ -17,7 +16,6 @@
 Architecture: any
 Depends:
  bitlbee (>= 3.4) | bitlbee-libpurple (>= 3.4),
- libglib2.0-0 (>= 2.28),
  libjson-glib-1.0-0 (>= 0.14),
  ${misc:Depends},
  ${shlibs:Depends},
--- End Message ---
--- Begin Message ---
Source: bitlbee-facebook
Source-Version: 1.2.2-3
Done: Boyuan Yang 

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated bitlbee-facebook 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, 02 Apr 2024 11:15:33 -0400
Source: bitlbee-facebook
Architecture: source
Version: 1.2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 1067391
Changes:
 bitlbee-facebook (1.2.2-3) unstable; urgency=medium
 .
   * QA upload.
   * debian/control: Drop explicit dependency on libjson-glib-1.0-0
 and libglib2.0-0. (Closes: #1067391)
   * debian/control: Update Vcs-* fields.
   * Bump debhelper compat to v13.
Checksums-Sha1:
 e400a2fc876ceb5a52455c9289c0fcccfea9feb8 2011 bitlbee-facebook_1.2.2-3.dsc
 9f6ac49b150a41c1391e271bc0e892698c0fee83 58836 
bitlbee-facebook_1.2.2.orig.tar.xz
 a38a3ff08fb41c1d192aecf750936d121028c3c9 2596 
bitlbee-facebook_1.2.2-3.debian.tar.xz
 a664c87c391a45e4520e16dc5c34d99135fc3b40 8049 
bitlbee-facebook_1.2.2-3_amd64.buildinfo
Checksums-Sha256:
 66bd0874253359114557558ba74089027165425d30cc33f54fdc35dc2763157a 2011 
bitlbee-facebook_1.2.2-3.dsc
 f547e1a24e1d8abe8e0695c39e366024db942475dc8a30d9b6307af755dc82e1 58836 
bitlbee-facebook_1.2.2.orig.tar.xz
 8bd222f7ad241eb0ec78b075535b7ba0ad5416f07f5238e6f488dd5b3c7594ce 2596 
bitlbee-facebook_1.2.2-3.debian.tar.xz
 d4835f0d77304531844f503937c1f732448477a34e260c9c2635cd7fbd41771c 8049 
bitlbee-facebook_1.2.2-3_amd64.buildinfo
Files:
 c21a288b05c70749c6753096051c970e 2011 net optional bitlbee-facebook_1.2.2-3.dsc
 7e0432d2fe6b8fc8b2d1c9b7add659f2 58836 net optional 
bitlbee-facebook_1.2.2.orig.tar.xz
 1a259b2518c722795fc6d0abb5f0bf1e 2596 net optional 
bitlbee-facebook_1.2.2-3.debian.tar.xz
 1bb880c71b64b48f1119ae45168db19e 8049 net optional 
bitlbee-facebook_1.2.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmYMIgUACgkQwpPntGGC
Ws5wpA//csbCbOKV2nC7Alw78nn1cfEHrzeMDeOaA8VjGKjQ0uwVgasAB9S9vVUP
JVC86L3GQReuaToL21gUapyUEYT11dw337ut+NHjN6bQVIvpzN55dZYY71oFkusB

Bug#1068222: marked as done (libappmenu-gtk3-parser0, dependencies unsatisfiable on 32-bit non-i386 architectures.)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 15:34:12 +
with message-id 
and subject line Bug#1068222: fixed in appmenu-gtk-module 0.7.6-3
has caused the Debian Bug report #1068222,
regarding libappmenu-gtk3-parser0, dependencies unsatisfiable on 32-bit 
non-i386 architectures.
to be marked as done.

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

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


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

Package: libappmenu-gtk3-parser0
Version: 0.7.6-2.1
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, libappmenu-gtk3-parser0
depends on both libgtk3-0 and libgtk3-0t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).

Ubuntu already seem to have prepared a fix for this.
--- End Message ---
--- Begin Message ---
Source: appmenu-gtk-module
Source-Version: 0.7.6-3
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
appmenu-gtk-module, 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 appmenu-gtk-module 
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, 02 Apr 2024 17:23:46 +0200
Source: appmenu-gtk-module
Architecture: source
Version: 0.7.6-3
Distribution: unstable
Urgency: medium
Maintainer: Ayatana Packagers 
Changed-By: Mike Gabriel 
Closes: 1068222
Changes:
 appmenu-gtk-module (0.7.6-3) unstable; urgency=medium
 .
   [ Logan Rosen ]
   * debian/control:
 + Fix Vcs-Browser URL
 .
   [ Mike Gabriel ]
   * debian/control:
 + Drop exlicit/versioned D on libgtk-dev from bin:pkg libappmenu-gtk3-
   parser0. (Closes: #1068222).
   * debian/copyright:
 + Fix duplicate entries.
 + Update copyright attribution for debian/.
   * debian/control:
 + Bump Standards-Version: to 4.6.2. No changes needed.
   * debian/watch:
 + Switch to format version 4.
Checksums-Sha1:
 15556fb8571704106eeb4cdff0e384264c87fdca 2953 appmenu-gtk-module_0.7.6-3.dsc
 2394683f5a8f3d4e74f41780d5ac1278753c085c 4800 
appmenu-gtk-module_0.7.6-3.debian.tar.xz
 d7ed50aa7f11ebefaacdc9ff56ded7cbad31bb0a 15958 
appmenu-gtk-module_0.7.6-3_source.buildinfo
Checksums-Sha256:
 040a1cb9e150b4b9b87f14664f6b26af13189e69c33bdbf386424acddb89144c 2953 
appmenu-gtk-module_0.7.6-3.dsc
 9cd315981f8cc7c1916dc21ea3c3063b0322897acd3a11c6dbedcbddc26d427a 4800 
appmenu-gtk-module_0.7.6-3.debian.tar.xz
 b11240d76d96c55f5c0e43f877a8ca747310da3918d2e64e9329b4a7124d9a6f 15958 
appmenu-gtk-module_0.7.6-3_source.buildinfo
Files:
 ccbce481e09d2a29f03f7ace591a5994 2953 libs optional 
appmenu-gtk-module_0.7.6-3.dsc
 ac6f464d4dfcf61a04248f470e0de398 4800 libs optional 
appmenu-gtk-module_0.7.6-3.debian.tar.xz
 b8070efbbc3d6f21c2dece177b63b7ca 15958 libs optional 
appmenu-gtk-module_0.7.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmYMIykVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx9HYP/R9mjmlFoGzedQSxIeA0gziTP0nY
yAeC/HiP0iI7P73dspzzQ/3vcGbXqG6sJ8rnouIY5o+Y5yf0hqvniND1/vmEzRcW
SVpSjPEey85RTEq+x9yisz+8/WQNM0GEi0sGuV172/Su+I+W1vUue/u9aaEy6oC3
PEZKgnZKUKkCsmitHA9+PH65+yC1UNAuDcvqkRDpJi/qo9JnWo6uj/ffTui9oaLL
8M0D7P7eQpBj39G0SOUWq1AYflbxfDjSnlmz2ulLW0vKCtEet/1toSMVzdvJkgLP
BUH31Uxseq/jp0l/FS+4gs3S8MDQXmiMvGG23ko1mKyQ8+WaOac3r3zptlEGDVJa
7XhW9CX3etoo8dmITuy99ZEjQtSr95i0vFdqdtNGMChfB/3BoDSwIsxvSbDKLWeL
Yt8T6mus1igU00qZAhifrSUCT63KFynE1O1s4RpnKj1arIDhhJ0010Zg9oyLzLND
waNceIRxipgvI2U2TodFjz6W3USdHgYNgWmdL6OCcrKMUoahjx7iiMKL/4p82Tpi
r76ZwNPxJIhB5dECe41+wgCEKS0xWE5HDuppSKeZglBzOM+J6xpHei7gDuF56ioF
L0kbtYMRNdCR6TljGpfKf1duMOYnnYIPLMvrXcqCoCH+vuvLLPuYJRdNaELwwXxi
lhnHWZvb6SU9lMIN
=OuTs
-END PGP SIGNATURE-



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

Bug#1068158: python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:

[Bo YU]

On Tue, Apr 2, 2024 at 11:19 PM Sebastian Ramacher  wrote:
>
> Hi
>
> On 2024-04-02 23:16:16 +0800, Bo YU wrote:
> > Tags: patch
> >
> > Hi,
> > >  File "/<>/site_scons/extractdebbuild.py", line 61:
> > >raise RuntimeError("We do not current support different different 
> > > dpkg-buildflags for C vs C++")
> > > make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2
> >
> > I have looked into this a bit.
> > As the error hint here, the default cflags in here when build is:
> >
> > ```
> > -g -O2 -Werror=implicit-function-declaration 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-
> > clash-protection -Wformat -Werror=format-security -fcf-protection 
> > -Wno-uninitialized
> > ```
> >
> > But cxxflags without[0] `-Werror=implicit-function-declaration` here. Is it
> > expected?
>
> It is expected. -Werror=implicit-function-declaration makes no sense in
> C++ since C++ simply does not support implicit function declarations.

Thanks for clarification.

Once cleared my local build, I will push this update again.

BR,
Bo
>
> Cheers
>

Bug#1068222: marked as pending in appmenu-gtk-module

[Mike Gabriel]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-ayatana-team/appmenu-gtk-module/-/commit/367cb5e9daddc66d315b4b1cf40b6b1c1e571e61


debian/control: Drop exlicit/versioned D on libgtk-dev from bin:pkg 
libappmenu-gtk3-parser0. (Closes: #1068222).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068222

Processed: Bug#1068222 marked as pending in appmenu-gtk-module

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068222 [libappmenu-gtk3-parser0] libappmenu-gtk3-parser0, dependencies 
unsatisfiable on 32-bit non-i386 architectures.
Added tag(s) pending.

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

Bug#1068158: python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:

[Sebastian Ramacher]

Hi

On 2024-04-02 23:16:16 +0800, Bo YU wrote:
> Tags: patch
> 
> Hi,
> >  File "/<>/site_scons/extractdebbuild.py", line 61:
> >raise RuntimeError("We do not current support different different 
> > dpkg-buildflags for C vs C++")
> > make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2
> 
> I have looked into this a bit.
> As the error hint here, the default cflags in here when build is:
> 
> ```
> -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-
> clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wno-uninitialized
> ```
> 
> But cxxflags without[0] `-Werror=implicit-function-declaration` here. Is it
> expected?

It is expected. -Werror=implicit-function-declaration makes no sense in
C++ since C++ simply does not support implicit function declarations.

Cheers

> 
> 
> 
> Once we added the build flags for cxx[1] and sorted these config with
> compared, the built is okay.
> 
> [0]: 
> https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=ef90821fe45b99fa8c8c4279b9a74c30f59f491d
> [1]: 
> https://salsa.debian.org/science-team/python-escript/-/blob/debian/latest/debian/rules?ref_type=heads#L16
> 
> -- 
> Regards,
> --
>   Bo YU
> 

> diff -Nru python-escript-5.6/debian/changelog 
> python-escript-5.6/debian/changelog
> --- python-escript-5.6/debian/changelog   2023-12-10 18:53:54.0 
> +0800
> +++ python-escript-5.6/debian/changelog   2024-04-02 20:27:27.0 
> +0800
> @@ -1,3 +1,12 @@
> +python-escript (5.6-7) unstable; urgency=medium
> +
> +  * Team upload.
> +  * Add fix-dpkg-buildflags-on-c-c++.patch to fix ftbfs issue.
> +(Closes: #1068158)
> +  * No build dependencies issue again. (Closes: #1067385)
> +
> + -- Bo YU   Tue, 02 Apr 2024 20:27:27 +0800
> +
>  python-escript (5.6-6) unstable; urgency=medium
>  
>* Update patch for new buildflags. Closes: #1057593
> diff -Nru 
> python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch 
> python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch
> --- python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch  
> 1970-01-01 08:00:00.0 +0800
> +++ python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch  
> 2024-04-02 20:26:55.0 +0800
> @@ -0,0 +1,32 @@
> +Description: false postive for different build flags
> +  Do not support different different dpkg-buildflags for C vs C++
> +  In fact, cflags and cxxflags was the same with following config:
> +  cxxflags: -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=form
> +at-security -fcf-protection -Wno-uninitialized 
> -Werror=implicit-function-declaration
> +
> +  cflags:   -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-
> +clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wno-uninitialized
> + so sorted them can fix the issue.
> +
> +Author: Bo YU 
> +Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068158
> +Last-Update: 2024-04-02
> +---
> +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
> +--- a/site_scons/extractdebbuild.py
>  b/site_scons/extractdebbuild.py
> +@@ -57,8 +57,12 @@
> + mycflags=val
> + if key=="CXXFLAGS":
> + mycxxflags=val
> +-if mycflags is not None and mycxxflags is not None and 
> mycflags!=mycxxflags:
> +-raise RuntimeError("We do not current support different different 
> dpkg-buildflags for C vs C++")
> ++if mycflags is not None and mycxxflags is not None: 
> ++print(mycxxflags)
> ++print(mycflags)
> ++
> ++if sorted(mycflags.split()) != sorted(mycxxflags.split()):
> ++raise RuntimeError("We do not current support different 
> different dpkg-buildflags for C vs C++")
> + if usedflags[key] is None:
> + continue
> + res.append([usedflags[key],val])
> diff -Nru python-escript-5.6/debian/patches/py3.patch 
> python-escript-5.6/debian/patches/py3.patch
> --- python-escript-5.6/debian/patches/py3.patch   2023-12-10 
> 16:25:14.0 +0800
> +++ python-escript-5.6/debian/patches/py3.patch   2024-04-02 
> 17:40:23.0 +0800
> @@ -4,11 +4,9 @@
>  Last-Updated: 2020-03-09
>   Updated for python3.8
>  
> -Index: python-escript-5.6/site_scons/extractdebbuild.py
> -===
>  python-escript-5.6.orig/site_scons/extractdebbuild.py
> -+++ python-escript-5.6/site_scons/extractdebbuild.py
> -@@ -35,7 +35,7 @@ def getdebbuildflags():
> +--- a/site_scons/extractdebbuild.py
>  b/site_scons/extractdebbuild.py
> +@@ -35,7 +35,7 @@
> mycflags=None
> mycxxflags=None
> try:
> @@ -17,11 +15,9 @@
> except OSError:
>   return []
> res=[]
> -Index: python-escript-5.6/site_scons/dependencies.py
> -===
>  

Bug#1068243: bsdgames: fails to configure

[Sven Joachim]

Package: bsdgames
Version: 2.17-31
Severity: serious

Your package fails to configure in a fresh installation (but not when
upgrading from a previous version).  This is what happens in a throwaway
chroot (unrelated lines stripped from apt/dpkg output):

,
| # apt install bsdgames
| Selecting previously unselected package bsdgames.
| Preparing to unpack .../bsdgames_2.17-31_amd64.deb ...
| Unpacking bsdgames (2.17-31) ...
| Setting up bsdgames (2.17-31) ...
| cp: cannot stat '/usr/share/games/bsdgames/phantasia/void': No such file or 
directory
| dpkg: error processing package bsdgames (--configure):
|  installed bsdgames package post-installation script subprocess returned 
error exit status 1
| Errors were encountered while processing:
|  bsdgames
| E: Sub-process /usr/bin/dpkg returned an error code (1)
`

See also the Salsa CI job at [1].


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


1. https://salsa.debian.org/games-team/bsdgames/-/jobs/5528281

Bug#1068158: python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:

[Bo YU]

Tags: patch

Hi,

 File "/<>/site_scons/extractdebbuild.py", line 61:
   raise RuntimeError("We do not current support different different dpkg-buildflags 
for C vs C++")
make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2


I have looked into this a bit.
As the error hint here, the default cflags in here when build is:

```
-g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-
clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wno-uninitialized
```

But cxxflags without[0] `-Werror=implicit-function-declaration` here. Is it
expected?



Once we added the build flags for cxx[1] and sorted these config with
compared, the built is okay.

[0]: 
https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=ef90821fe45b99fa8c8c4279b9a74c30f59f491d
[1]: 
https://salsa.debian.org/science-team/python-escript/-/blob/debian/latest/debian/rules?ref_type=heads#L16

--
Regards,
--
  Bo YU

diff -Nru python-escript-5.6/debian/changelog 
python-escript-5.6/debian/changelog
--- python-escript-5.6/debian/changelog 2023-12-10 18:53:54.0 +0800
+++ python-escript-5.6/debian/changelog 2024-04-02 20:27:27.0 +0800
@@ -1,3 +1,12 @@
+python-escript (5.6-7) unstable; urgency=medium
+
+  * Team upload.
+  * Add fix-dpkg-buildflags-on-c-c++.patch to fix ftbfs issue.
+(Closes: #1068158)
+  * No build dependencies issue again. (Closes: #1067385)
+
+ -- Bo YU   Tue, 02 Apr 2024 20:27:27 +0800
+
 python-escript (5.6-6) unstable; urgency=medium
 
   * Update patch for new buildflags. Closes: #1057593
diff -Nru python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch 
python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch
--- python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch
1970-01-01 08:00:00.0 +0800
+++ python-escript-5.6/debian/patches/fix-dpkg-buildflags-on-c-c++.patch
2024-04-02 20:26:55.0 +0800
@@ -0,0 +1,32 @@
+Description: false postive for different build flags
+  Do not support different different dpkg-buildflags for C vs C++
+  In fact, cflags and cxxflags was the same with following config:
+  cxxflags: -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=form
+at-security -fcf-protection -Wno-uninitialized 
-Werror=implicit-function-declaration
+
+  cflags:   -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-
+clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wno-uninitialized
+ so sorted them can fix the issue.
+
+Author: Bo YU 
+Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068158
+Last-Update: 2024-04-02
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/site_scons/extractdebbuild.py
 b/site_scons/extractdebbuild.py
+@@ -57,8 +57,12 @@
+ mycflags=val
+ if key=="CXXFLAGS":
+ mycxxflags=val
+-if mycflags is not None and mycxxflags is not None and 
mycflags!=mycxxflags:
+-raise RuntimeError("We do not current support different different 
dpkg-buildflags for C vs C++")
++if mycflags is not None and mycxxflags is not None: 
++print(mycxxflags)
++print(mycflags)
++
++if sorted(mycflags.split()) != sorted(mycxxflags.split()):
++raise RuntimeError("We do not current support different different 
dpkg-buildflags for C vs C++")
+ if usedflags[key] is None:
+ continue
+ res.append([usedflags[key],val])
diff -Nru python-escript-5.6/debian/patches/py3.patch 
python-escript-5.6/debian/patches/py3.patch
--- python-escript-5.6/debian/patches/py3.patch 2023-12-10 16:25:14.0 
+0800
+++ python-escript-5.6/debian/patches/py3.patch 2024-04-02 17:40:23.0 
+0800
@@ -4,11 +4,9 @@
 Last-Updated: 2020-03-09
  Updated for python3.8
 
-Index: python-escript-5.6/site_scons/extractdebbuild.py
-===
 python-escript-5.6.orig/site_scons/extractdebbuild.py
-+++ python-escript-5.6/site_scons/extractdebbuild.py
-@@ -35,7 +35,7 @@ def getdebbuildflags():
+--- a/site_scons/extractdebbuild.py
 b/site_scons/extractdebbuild.py
+@@ -35,7 +35,7 @@
mycflags=None
mycxxflags=None
try:
@@ -17,11 +15,9 @@
except OSError:
  return []
res=[]
-Index: python-escript-5.6/site_scons/dependencies.py
-===
 python-escript-5.6.orig/site_scons/dependencies.py
-+++ python-escript-5.6/site_scons/dependencies.py
-@@ -122,7 +122,7 @@ def call_python_config(bin=None):
+--- a/site_scons/dependencies.py
 b/site_scons/dependencies.py
+@@ -122,7 +122,7 @@
  cmd+='  
sp=subprocess.Popen([pythonroot+"python"+pyversion+"-config","--ldflags"], 
stdout=subprocess.PIPE)\n'
  cmd+='d=sp.stdout.readline().split()\n'
  cmd+="libdirs=[z[2:] for z in d if z.startswith(b'-L')]\n"
@@ -30,7 +26,7 @@
  

Bug#1066248: [Pkg-electronics-devel] Bug#1066248: librnd: FTBFS: ../src/librnd/plugins/hid_lesstif/main.c:261:25: error: implicit declaration of function ‘lesstif_attr_sub_update_hidlib’ [-Werror=impl

[Bdale Garbee]

Peter Michael Green  writes:

> The functions in question are defined in 
> src/librnd/plugins/hid_lesstif/dialogs.c
> and used in src/librnd/plugins/hid_lesstif/main.c

Correct.  Upstream has fixed this and will have a new release on 10
April that I'm waiting for rather than patching the current Debian
sources.

> while working on this issue I discovered that the clean target was not
> cleaning up properly, so I fixed that too.

Thank you!  That's been on my to-do list, will talk to upstream about
the lingering files since his build structure should be cleaning up
after itself better, I think.

Bdale


signature.asc
Description: PGP signature

Bug#1068240: marked as done (nauty: autopkgtest regression in testing)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 15:05:06 +
with message-id 
and subject line Bug#1068240: fixed in nauty 2.8.8+ds-3
has caused the Debian Bug report #1068240,
regarding nauty: autopkgtest regression in testing
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.)


-- 
1068240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nauty
Version: 2.8.8+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Sometime around 2024-01-23, nauty's autopkgtest regressed in testing
[1].  I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/n/nauty/testing/amd64/


60s The following packages have unmet dependencies:
60s autopkgtest-satdep : Depends: libnauty2-dev but it is not installable
60s E: Unable to correct problems, you have held broken packages.
60s autopkgtest: WARNING: Test dependencies are unsatisfiable -
calling apt install on test deps directly for further data about
failing dependencies in test logs
60s Reading package lists...
60s Building dependency tree...
60s Reading state information...
60s Package libnauty2-dev is not available, but is referred to by
another package.
60s This may mean that the package is missing, has been obsoleted, or
60s is only available from another source
60s
60s E: Package 'libnauty2-dev' has no installation candidate
60s build-examples FAIL badpkg
60s blame: nauty
60s badpkg: Test dependencies are unsatisfiable. A common reason is
that your testbed is out of date with respect to the archive, and you
need to use a current testbed or run apt-get update or use -U.
--- End Message ---
--- Begin Message ---
Source: nauty
Source-Version: 2.8.8+ds-3
Done: Andrius Merkys 

We believe that the bug you reported is fixed in the latest version of
nauty, 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.
Andrius Merkys  (supplier of updated nauty 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, 02 Apr 2024 10:38:14 -0400
Source: nauty
Architecture: source
Version: 2.8.8+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andrius Merkys 
Closes: 1068240
Changes:
 nauty (2.8.8+ds-3) unstable; urgency=medium
 .
   * Team upload.
   * Replace libnauty2-dev with libnauty-dev in debian/tests/control
 (Closes: #1068240).
   * Replace in Build-Depends: pkg-config => pkgconf.
Checksums-Sha1:
 798345b7a613a9290e9061bc00656ff0d5fd9b08 2305 nauty_2.8.8+ds-3.dsc
 66c1ab0b744553dfa388ba2c69f60c4c52e40094 65636 nauty_2.8.8+ds-3.debian.tar.xz
 7bd1db3350ac3750910444577cf06f331d0b892e 6840 nauty_2.8.8+ds-3_source.buildinfo
Checksums-Sha256:
 037d4128dab2b9578f92123b5664bd3b8d1e37b48d30aa37f44ac67a234fb867 2305 
nauty_2.8.8+ds-3.dsc
 1f55d71fa7e68f0ba6ee7a510022dd74b42a1c4c16fa5af1bb0492500f367a3e 65636 
nauty_2.8.8+ds-3.debian.tar.xz
 54899e856b9f4bd5b3d6a57fbd92ed5e111fdaef3b9d7f51f18a64802a26da34 6840 
nauty_2.8.8+ds-3_source.buildinfo
Files:
 ac4e22c764a0bc5cd3711d2b86a1ed48 2305 math optional nauty_2.8.8+ds-3.dsc
 ee24d72755f19fa94a830ed7ab1d9278 65636 math optional 
nauty_2.8.8+ds-3.debian.tar.xz
 485a4431cc33a14845ef1e2bbbe79b80 6840 math optional 
nauty_2.8.8+ds-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmYMGIYSHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKH2TgP/3J2eGynpKAHsyV3dvurtPvOJQ2zzSl1
sMPemAoLbUPtW0s4EuQVfnnWp8EGTjYiNuax7za4UBv8v72tchpgMAtUpTK93rXz
KZv5egv92iNWPNaZpY4aGzOklN/SVUqBOD82gU+KeFb58y8tvw0WXX2+YNBCATH9
sNVPcJy6anPjvahp+6btdBv6QJOq0bZC946KmafSzzvefMZQarKA5Djxz5fxc/PR
yMSOYcXeyACqbVMUYW1+Ej5piCApAp2urbmBT+v2saN5wFJAckJlJgqcUczs5IJy
dODUYclN3Um7OcaaNSD2Bo2PULIvR4tVaKgg5fB4wZqS2f4DMVqnLwia5MUZsRxu
OwycH8o/FfEfil/AuqGW1WHu3GnhSRZfCQkr2JfcDGhUV+ZFTzaOSdDXF92SOEnK
p6WkDkwhgggH0bETri+4dEHN6MsRrE2Ufj/xliNe3wiBXJKTk/vHYcgQmehw+iN6
AesHq887FOfWvQb3GqdtfuRKaMXwx+qHky7g7EvCqIksIu9uOrQrkI8jfcEEJAOD
f4r8/2sXc2Gw1NfhZbZWLLr+4tqQYUK4cA23uDiavLHT1IgXTsRUkpoY5PPItSaQ

Processed: severity of 1056156 is important

[Debian Bug Tracking System]

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

> severity 1056156 important
Bug #1056156 [src:varnish] varnish: CVE-2023-44487: VSV00013 Varnish HTTP/2 
Rapid Reset Attack
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#1060407: gtkwave update for {bookworm,bullseye,buster}-security

[Adrian Bunk]

On Sun, Mar 31, 2024 at 01:52:40PM +0200, Moritz Mühlenhoff wrote:
> Hi Adrian,

Hi Moritz,

>...
> > debdiffs contain only changes to debian/
> 
> The bookworm/bullseye debdiffs looks good, please upload to security-master, 
> thanks!

both are now uploaded.

> Note that both need -sa, but dak needs some special attention when
> uploading to security-master. You'll need to wait for the ACCEPTED mail
> before you can upload the next one.

Done, but I am not sure this was necessary in this case since these are 
different upstream tarballs gtkwave_3.3.118.orig.tar.gz and 
gtkwave_3.3.104+really3.3.118.orig.tar.gz

(The contents also differs since as mentioned one is the GTK 2+3 
 upstream tarball and the other one is the GTK 1+2 upstream tarball.)

> Cheers,
> Moritz

cu
Adrian

Processed: affects 1068242, block 1039583 with 1068242, block 1039612 with 1068242

[Debian Bug Tracking System]

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

> affects 1068242 + src:libtool
Bug #1068242 [release.debian.org] bookworm-pu: package libtool/2.4.7-7~deb12u1
Added indication that 1068242 affects src:libtool
> block 1039583 with 1068242
Bug #1039583 {Done: Alastair McKinstry } [libltdl-dev] 
libltdl-dev: missing Breaks+Replaces: libltdl3-dev
1039583 was not blocked by any bugs.
1039583 was not blocking any bugs.
Added blocking bug(s) of 1039583: 1068242
> block 1039612 with 1068242
Bug #1039612 {Done: Alastair McKinstry } [libtool] 
libtool: Incorrect check for += operator causes func_append to fail
1039612 was not blocked by any bugs.
1039612 was not blocking any bugs.
Added blocking bug(s) of 1039612: 1068242
> thanks
Stopping processing here.

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

Bug#1068240: nauty: autopkgtest regression in testing

[Graham Inggs]

Source: nauty
Version: 2.8.8+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Sometime around 2024-01-23, nauty's autopkgtest regressed in testing
[1].  I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/n/nauty/testing/amd64/


60s The following packages have unmet dependencies:
60s autopkgtest-satdep : Depends: libnauty2-dev but it is not installable
60s E: Unable to correct problems, you have held broken packages.
60s autopkgtest: WARNING: Test dependencies are unsatisfiable -
calling apt install on test deps directly for further data about
failing dependencies in test logs
60s Reading package lists...
60s Building dependency tree...
60s Reading state information...
60s Package libnauty2-dev is not available, but is referred to by
another package.
60s This may mean that the package is missing, has been obsoleted, or
60s is only available from another source
60s
60s E: Package 'libnauty2-dev' has no installation candidate
60s build-examples FAIL badpkg
60s blame: nauty
60s badpkg: Test dependencies are unsatisfiable. A common reason is
that your testbed is out of date with respect to the archive, and you
need to use a current testbed or run apt-get update or use -U.

Processed: your mail

[Debian Bug Tracking System]

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

> affects 1067226 src:polymake
Bug #1067226 {Done: Doug Torrance } [src:flint] flint: 
libflint needs soversion bump to 19
Bug #1067363 {Done: Doug Torrance } [src:flint] polymake: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Bug #1068140 {Done: Doug Torrance } [src:flint] polymake: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Added indication that 1067226 affects src:polymake
Added indication that 1067363 affects src:polymake
Added indication that 1068140 affects src:polymake
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 1067226 1068140
Bug #1067226 {Done: Doug Torrance } [src:flint] flint: 
libflint needs soversion bump to 19
Bug #1067363 {Done: Doug Torrance } [src:flint] polymake: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Bug #1068140 [src:flint] polymake: FTBFS: dpkg-shlibdeps: error: no dependency 
information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Severity set to 'grave' from 'serious'
1067293 was blocked by: 1067363 1067226
1067293 was not blocking any bugs.
Added blocking bug(s) of 1067293: 1068140
1067274 was blocked by: 1067363 1067226
1067274 was not blocking any bugs.
Added blocking bug(s) of 1067274: 1068140
1067360 was blocked by: 1067363 1067226
1067360 was not blocking any bugs.
Added blocking bug(s) of 1067360: 1068140
1067262 was blocked by: 1067226 1067363
1067262 was not blocking any bugs.
Added blocking bug(s) of 1067262: 1068140
1067286 was blocked by: 1067363 1067226
1067286 was not blocking any bugs.
Added blocking bug(s) of 1067286: 1068140
1067300 was blocked by: 1067226 1067363
1067300 was not blocking any bugs.
Added blocking bug(s) of 1067300: 1068140
Marked Bug as done
Removed indication that 1068140 affects src:polymake
Marked as fixed in versions flint/3.1.2-1~exp1.
Bug #1067363 {Done: Doug Torrance } [src:flint] polymake: 
FTBFS: dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Merged 1067226 1067363 1068140
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1067226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067226
1067262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067262
1067274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067274
1067286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067286
1067293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067293
1067300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067300
1067360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067360
1067363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067363
1068140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 1067339

[Debian Bug Tracking System]

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

> close 1067339
Bug #1067339 [src:deal.ii] deal.ii: FTBFS: unsatisfiable build-dependencies
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

[Guido Günther]

Hi,
On Tue, Apr 02, 2024 at 02:32:16PM +0530, Pirate Praveen wrote:
> Package: gnome-settings-daemon,phosh
> severity: serious
> 
> Recently automatic suspend stopped working. I think this was after gnome
> settings daemon 46 was available. Some background
> 

Suspends fine here with phosh 0.37.1 (although notching changed in that
area for a while) and g-s-d 46

Cheers,
 -- Guido

> 
> Not sure if phosh needs some adjustments with recent changes in gnome
> settings daemon. For now assigned to both.
> 
> On kde plasma mobile, automatic suspend still works, so this appears to be
> gnome specific regression.
> 

Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

[Jeremy Bícha]

On Tue, Apr 2, 2024 at 8:03 AM Jeremy Bícha  wrote:
>
> On Tue, Apr 2, 2024 at 5:31 AM Pirate Praveen  
> wrote:
> > Recently automatic suspend stopped working. I think this was after gnome 
> > settings daemon 46 was available. Some background
> > https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7
> >
> > Not sure if phosh needs some adjustments with recent changes in gnome 
> > settings daemon. For now assigned to both.
>
> Do you have phosh 0.37 or higher installed yet?

Correction: Do you have phosh 0.37.0-2 or 3.7.1-1 installed?

Thank you,
Jeremy Bícha

Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

[Jeremy Bícha]

On Tue, Apr 2, 2024 at 5:31 AM Pirate Praveen  wrote:
> Recently automatic suspend stopped working. I think this was after gnome 
> settings daemon 46 was available. Some background
> https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7
>
> Not sure if phosh needs some adjustments with recent changes in gnome 
> settings daemon. For now assigned to both.

Do you have phosh 0.37 or higher installed yet?

Thank you,
Jeremy Bícha

Bug#1066638: marked as done (ukui-screensaver: FTBFS: kylin-network-interface.c:199:5: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declarati

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 11:55:00 +
with message-id 
and subject line Bug#1066638: fixed in ukui-screensaver 3.0.3.3-1
has caused the Debian Bug report #1066638,
regarding ukui-screensaver: FTBFS: kylin-network-interface.c:199:5: error: 
implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? 
[-Werror=implicit-function-declaration]
to be marked as done.

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

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


-- 
1066638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ukui-screensaver
Version: 3.0.3.2-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):
> cd /<>/obj-x86_64-linux-gnu/KylinNM && /usr/bin/cc -DQT_CORE_LIB 
> -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB 
> -I/<>/obj-x86_64-linux-gnu/KylinNM -I/<>/KylinNM 
> -I/<>/obj-x86_64-linux-gnu/KylinNM/Kylin-nm_autogen/include 
> -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/KF5/KWindowSystem -isystem /usr/include/KF5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fPIC -MD -MT KylinNM/CMakeFiles/Kylin-nm.dir/src/kylin-network-interface.c.o 
> -MF CMakeFiles/Kylin-nm.dir/src/kylin-network-interface.c.o.d -o 
> CMakeFiles/Kylin-nm.dir/src/kylin-network-interface.c.o -c 
> /<>/KylinNM/src/kylin-network-interface.c
> /<>/KylinNM/src/kylin-network-interface.c: In function 
> ‘kylin_network_get_activecon_info’:
> /<>/KylinNM/src/kylin-network-interface.c:199:5: error: implicit 
> declaration of function ‘asprintf’; did you mean ‘vsprintf’? 
> [-Werror=implicit-function-declaration]
>   199 | asprintf(, "%s%s%s", chr, tmpPrefix, name);
>   | ^~~~
>   | vsprintf
> /<>/KylinNM/src/kylin-network-interface.c: In function 
> ‘kylin_network_get_conlist_info’:
> /<>/KylinNM/src/kylin-network-interface.c:99:5: warning: 
> ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ 
> [-Wunused-result]
>99 | fgets(ConStrLine,1024,confp);
>   | ^~~~
> /<>/KylinNM/src/kylin-network-interface.c:102:9: warning: 
> ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ 
> [-Wunused-result]
>   102 | fgets(ConStrLine,1024,confp);
>   | ^~~~
> /<>/KylinNM/src/kylin-network-interface.c:117:5: warning: 
> ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ 
> [-Wunused-result]
>   117 | fgets(StrLine,1024,fp);
>   | ^~
> /<>/KylinNM/src/kylin-network-interface.c:122:9: warning: 
> ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ 
> [-Wunused-result]
>   122 | fgets(StrLine,1024,fp);
>   | ^~
> /<>/KylinNM/src/kylin-network-interface.c: In function 
> ‘kylin_network_get_activecon_info’:
> /<>/KylinNM/src/kylin-network-interface.c:217:5: warning: 
> ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ 
> [-Wunused-result]
>   217 | fgets(activeStrLine,1024,activefp);
>   | ^~
> /<>/KylinNM/src/kylin-network-interface.c:220:9: warning: 
> ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ 
> [-Wunused-result]
>   220 | fgets(activeStrLine,1024,activefp);
>   | ^~
> /<>/KylinNM/src/kylin-network-interface.c:237:5: warning: 
> ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ 
> [-Wunused-result]
>   237 | fgets(StrLine,1024,fp);
>   | ^~
> 

Processed: bug 1067712 is forwarded to https://github.com/rust-lang/stacker/issues/85

[Debian Bug Tracking System]

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

> forwarded 1067712 https://github.com/rust-lang/stacker/issues/85
Bug #1067712 [src:rust-stacker] rust-stacker: FTBFS on mips64el: process didn't 
exit successfully: 
`/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/smoke-983e0e8761f2ceb1`
 (signal: 11, SIGSEGV: invalid memory reference)
Set Bug forwarded-to-address to 
'https://github.com/rust-lang/stacker/issues/85'.
> thanks
Stopping processing here.

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

Processed: tagging 1068224, tagging 1068222, found 1067391 in 1.2.2-2, tagging 1067391, tagging 1068216 ...

[Debian Bug Tracking System]

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

> tags 1068224 + sid trixie
Bug #1068224 [deepin-movie] deepin-movie, dependencies unsatisfiable on 32-bit 
non-i386 architectures.
Added tag(s) trixie and sid.
> tags 1068222 + sid trixie
Bug #1068222 [libappmenu-gtk3-parser0] libappmenu-gtk3-parser0, dependencies 
unsatisfiable on 32-bit non-i386 architectures.
Added tag(s) trixie and sid.
> found 1067391 1.2.2-2
Bug #1067391 [bitlbee-facebook] bitlbee-facebook: redundant dependency on 
libglib2.0-0
There is no source info for the package 'bitlbee-facebook' at version '1.2.2-2' 
with architecture ''
Unable to make a source version for version '1.2.2-2'
Marked as found in versions 1.2.2-2.
> tags 1067391 + sid trixie
Bug #1067391 [bitlbee-facebook] bitlbee-facebook: redundant dependency on 
libglib2.0-0
Added tag(s) trixie and sid.
> tags 1068216 + sid trixie
Bug #1068216 [aqemu] aqemu, dependencies unsatisfiable on 32-bit non-i386 
architectures.
Added tag(s) sid and trixie.
> tags 1068149 + sid trixie
Bug #1068149 [src:porg] FTBFS: Error: symbol `open64' is already defined
Added tag(s) sid and trixie.
> forwarded 1041803 https://github.com/hyperspy/hyperspy/issues/3217
Bug #1041803 [hyperspy] hyperspy: FTBFS test_image fails
Set Bug forwarded-to-address to 
'https://github.com/hyperspy/hyperspy/issues/3217'.
> tags 1041803 + sid trixie
Bug #1041803 [hyperspy] hyperspy: FTBFS test_image fails
Added tag(s) trixie and sid.
> tags 1068040 + sid trixie
Bug #1068040 [src:deepin-deb-installer] Update Build-Depends for the time64 
library renames
Added tag(s) sid and trixie.
> tags 1068202 + sid trixie
Bug #1068202 [src:bazel-bootstrap] bazel-bootstrap: FTBFS: 
/usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less 
than C++14 are not supported."
Added tag(s) sid and trixie.
> found 1068230 0.36.0-1
Bug #1068230 [gnome-settings-daemon,phosh] automatic suspend regression with 
gnome-settings-daemon 46
There is no source info for the package 'gnome-settings-daemon' at version 
'0.36.0-1' with architecture ''
Marked as found in versions phosh/0.36.0-1.
> found 1068230 46~beta-1
Bug #1068230 [gnome-settings-daemon,phosh] automatic suspend regression with 
gnome-settings-daemon 46
There is no source info for the package 'phosh' at version '46~beta-1' with 
architecture ''
Marked as found in versions gnome-settings-daemon/46~beta-1.
> tags 1068180 + sid trixie
Bug #1068180 {Done: Sebastian Ramacher } [src:libgav1] 
FTBFS: C++ versions less than C++14 are not supported.
Added tag(s) trixie and sid.
> tags 1068194 + sid trixie
Bug #1068194 [src:pcsx2] pcsx2: FTBFS: 
/<>/plugins/cdvdGigaherz/src/CDVD.cpp:143:19: error: 
‘system_error’ in namespace ‘std’ does not name a type
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1041803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041803
1067391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067391
1068040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068040
1068149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068149
1068180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068180
1068194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068194
1068202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068202
1068216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068216
1068222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068222
1068224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068224
1068230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 sid trixie
Bug #1068155 [src:lmms] lmms: FTBFS on i386: dh_install: warning: Cannot find 
(any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp)
Added tag(s) trixie and sid.

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

Bug#1068155: lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp)

[Andreas Beckmann]

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

Comparing bookworm and sid buildlogs shows the following relevant
differences during cmake:

-Setting up libwine-dev:i386 (8.0~repack-4) ...^M
+Setting up libwine-dev:i386 (9.0~repack-4+b1) ...^M

--- Found Wine: /usr/lib/i386-linux-gnu/wine/libwine.so
+CMake Warning (dev) at cmake/modules/FindWine.cmake:20 (EXEC_PROGRAM):
+  Policy CMP0153 is not set: The exec_program command should not be called.
+  Run "cmake --help-policy CMP0153" for policy details.  Use the cmake_policy
+  command to set the policy and suppress this warning.
+
+  Use execute_process() instead.
+Call Stack (most recent call first):
+  CMakeLists.txt:462 (FIND_PACKAGE)
+This warning is for project developers.  Use -Wno-dev to suppress it.
+
+-- Could NOT find Wine (missing: WINE_LIBRARIES)

-* VST-instrument hoster   : OK, with workaround linking 
/usr/lib/i386-linux-gnu/wine/i386-unix/libwinecrt0.a/
-* VST-effect hoster   : OK, with workaround linking 
/usr/lib/i386-linux-gnu/wine/i386-unix/libwinecrt0.a/
+* VST-instrument hoster   : not found, please install (lib)wine-dev (or 
similar) - 64 bit systems additionally need gcc-multilib and g++-multilib
+* VST-effect hoster   : not found, please install (lib)wine-dev (or 
similar) - 64 bit systems additionally need gcc-multilib and g++-multilib

 CMake Warning:
   Manually-specified variables were not used by the project:

 CMAKE_EXPORT_NO_PACKAGE_REGISTRY
 CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
 FETCHCONTENT_FULLY_DISCONNECTED
+WINE_CXX_FLAGS


Andreas

Processed: Re: fpzip: FTBFS on armel, armhf, i386 (1 - compress-decompress-validate (Failed))

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1068067 [src:fpzip] fpzip: FTBFS on armel, armhf, i386 (1 - 
compress-decompress-validate (Failed))
Severity set to 'normal' from 'serious'
> found -1 1.3.0-2
Bug #1068067 [src:fpzip] fpzip: FTBFS on armel, armhf, i386 (1 - 
compress-decompress-validate (Failed))
Marked as found in versions fpzip/1.3.0-2.

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

Bug#1068067: fpzip: FTBFS on armel, armhf, i386 (1 - compress-decompress-validate (Failed))

[Andreas Beckmann]

Followup-For: Bug #1068067
Control: severity -1 normal
Control: found -1 1.3.0-2

This is not a regression. Maybe a
  B-D: architecture-is-64-bit
should be added.


Andreas

Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

[Pirate Praveen]

Package: gnome-settings-daemon,phosh
severity: serious

Recently automatic suspend stopped working. I think this was after 
gnome settings daemon 46 was available. Some background



Not sure if phosh needs some adjustments with recent changes in gnome 
settings daemon. For now assigned to both.


On kde plasma mobile, automatic suspend still works, so this appears to 
be gnome specific regression.

Bug#1066594: octave-iso2mesh: FTBFS: nl_single_file.c:2505:26: error: implicit declaration of function ‘lsame_’ [-Werror=implicit-function-declaration]

[Rafael Laboissière]

* Qianqian Fang  [2024-03-29 10:52]:


On 3/29/24 01:24, Rafael Laboissière wrote:

It seems so. If we fix Bug#1066594, then both octave-iso2mesh and
octave-brain2mesh will be able to migrate into testing.



thanks Rafael, replying to #1066594

it looks like someone from Fedora had submitted a patch last year 
fixing the same problem - see


https://github.com/fangq/meshfix/pull/1

can you help me update this folder and try rebuilding the package?

https://salsa.debian.org/pkg-octave-team/octave-iso2mesh/-/tree/debian/latest/meshfix?ref_type=heads


Thanks for the link. The package is fixed and version 1.9.6+ds-10 of the 
package has been uploaded to unstable.



I no longer have access to octave-iso2mesh on salsa.


You are still a member of the octave-iso2mesh project at Salsa.d.o, with 
login fangq.


Best,

Rafael Laboissière

Bug#1067486: more information

[Andreas Beckmann]

On Mon, 1 Apr 2024 10:39:05 +0200 Bastian Blank  wrote:


binNMU are known to not work on the signing side of the archive.


Shouldn't the affected packages fail early during the build (and with an 
informative error message) if a binNMU is attempted? S.t. these "broken" 
binNMUs don't show up in the archive?



Andreas

Processed: opensearch: FTBFS with lucene9/9.10.0+dfsg

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 opensearch: FTBFS with lucene9/9.10.0+dfsg
Bug #1066450 [src:opensearch] opensearch: FTBFS: 
server/src/main/java/org/opensearch/index/codec/CodecService.java:37: error: 
cannot find symbol
Changed Bug title to 'opensearch: FTBFS with lucene9/9.10.0+dfsg' from 
'opensearch: FTBFS: 
server/src/main/java/org/opensearch/index/codec/CodecService.java:37: error: 
cannot find symbol'.

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

Bug#1066450: opensearch: FTBFS with lucene9/9.10.0+dfsg

[Andrius Merkys]

control: retitle -1 opensearch: FTBFS with lucene9/9.10.0+dfsg

I have recently updated lucene9. Current FTBFS is caused by missing 
lucene9 classes. Thus it seems that lucene9 API has changed breaking 
backwards compatibility.


Andrius

Processed: Re: Bug#1064708: pygame: FTBFS: AssertionError: "No video mode" does not match "Parameter 'surface' is invalid"

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1064708 [src:pygame] pygame: FTBFS: AssertionError: "No video mode" does 
not match "Parameter 'surface' is invalid"
Severity set to 'serious' from 'important'

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

Bug#1054486: marked as done (sogo: installs sogo.service twice once dh_installsystemd installs to /usr)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 10:20:52 +0200
with message-id 
and subject line Fixed in 5.9.1-1
has caused the Debian Bug report #1054486,
regarding sogo: installs sogo.service twice once dh_installsystemd installs to 
/usr
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.)


-- 
1054486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sogo
Version: 5.8.4-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to modify dh_installsystemd such that it install units below
/usr in order to finalize the /usr-merge transition via DEP17. When
doing so, sogo.service ends up being installed to both /lib (via
dh_install) and /usr/lib (via dh_installsystemd). Doing so is a policy
violation and therefore this bug will become release-critical once I
upload debhelper. I'm attching a patch for your convenience.

Helmut
diff -Nru sogo-5.8.4/debian/changelog sogo-5.8.4/debian/changelog
--- sogo-5.8.4/debian/changelog 2023-06-26 00:11:31.0 +0200
+++ sogo-5.8.4/debian/changelog 2023-10-24 11:59:57.0 +0200
@@ -1,3 +1,10 @@
+sogo (5.8.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd unit only once. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 24 Oct 2023 11:59:57 +0200
+
 sogo (5.8.4-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru sogo-5.8.4/debian/sogo.install sogo-5.8.4/debian/sogo.install
--- sogo-5.8.4/debian/sogo.install  2021-12-17 13:26:58.0 +0100
+++ sogo-5.8.4/debian/sogo.install  2023-10-24 11:59:50.0 +0200
@@ -2,7 +2,6 @@
 etc/default/sogo
 etc/logrotate.d/sogo
 debian/sogo.conf etc/sogo
-debian/sogo.service lib/systemd/system
 usr/include/GNUstep/*
 usr/lib/GNUstep/Frameworks/*
 usr/lib/GNUstep/OCSTypeModels/*
--- End Message ---
--- Begin Message ---
This bug was closed two months ago with the following changes file,
which was missing the corresponding closes: command.

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Feb 2024 16:39:36 +0100
Source: sogo
Architecture: source
Version: 5.9.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian SOGo Maintainers

Changed-By: Jordi Mallach 
Changes:
 sogo (5.9.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Revert all unvendoring changes as they completely break SOGo.
   * Rely on dh_installinit to install the systemd service file.
   * Refresh Remove-build-date.patch.
   * Update number of expected test failures to 1.
   * Release to unstable.
Checksums-Sha1:
 a0de7bcc140f48cbee4b3a1c65a4875e0fa1fd17 2264 sogo_5.9.1-1.dsc
 4674851c65672b7070023dbdae2eef9b8ddf0280 34831391
sogo_5.9.1.orig.tar.gz
 580e185dca322a62032869a1f3b8bce688d07112 18276 sogo_5.9.1-
1.debian.tar.xz
 36366d5cec0c489b7d637764f4128fb441a7b4fa 11322 sogo_5.9.1-
1_amd64.buildinfo
Checksums-Sha256:
 c1372ed8ede354b7ef534ec94ad0b28097c937d6120406fd74c2cfbb707b4832 2264
sogo_5.9.1-1.dsc
 df6ac305a99196ee66d60fda395af81d8da044e7f5c1b1603a51dc4a8edf8ac4
34831391 sogo_5.9.1.orig.tar.gz
 8f211e9ebbd87ee81f4869c940d96d4a749b0d21fa564174e3ca7148c7ce33e8 18276
sogo_5.9.1-1.debian.tar.xz
 bc7bd540fe6520504bc15af43607b45ec58dedb244c1976646fce982d3782f56 11322
sogo_5.9.1-1_amd64.buildinfo
Files:
 10df580323cea3434bdca93dfcbe5c39 2264 mail optional sogo_5.9.1-1.dsc
 a260fe92c447f0b185dbd6ebeb411907 34831391 mail optional
sogo_5.9.1.orig.tar.gz
 36387abcff529a9720a676365085dd5f 18276 mail optional sogo_5.9.1-
1.debian.tar.xz
 f48324600482875ab6b6b90067035549 11322 mail optional sogo_5.9.1-
1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAmXGas4ACgkQJVAvb8vj
ywQuMxAAm6BBOyqtWJ2panPGkdREkfOW+uvM480CVL2uEkzb5lSkedmyHQ1WU2P5
lDsXYj0cZbA9Qkjyf1jZqjOCRWW472FPBYkrG19oeS4Qnc3t8HN17Urv13lSrWm1
A0rCqDBGaI+uPSRI33DfkEbuc2BvZnb9l6gbeSgEyONRKbQ1IsuseQyS6Kuc/plu
vqvCWC2/Bi3YTjvxSYfKwqDJggd/6LtNPok0rL2++Iu6gD9i9NHZY/nLe2hyqzqQ
sMcejzJB0Gc3ZtDeQVD7kr9IMZnLUQUra5wby8XrbQx6YSzw7fJ/fhemczqicJ67
CfTCtRs0TzDQlzA5UxsXKGEcGVsIKDfD59Cbhfdv6EnEDCcnsAUf4wC+GStjtI8n
8tN4rU6WOdS3suW2ZdxTco7ujpxyimcxHe/Z2ruO44XWuaOK6XN2EqweULfUc5cR
3qkPpGftHbZUQh12at4enjL85EpMOXf832jMiamaNnwwgQE9rtisCfphOUOz8rLX
xWEjCqPkJ8JQPQeCTghJK0rWonZfLMgi6ooLOco9BOZWMtuEF/BmaVsfTOR0zafq
YoGMot69JzIQbVcbpbBhNHSwa6IXW1nzzm3V40cajM4p3lubb7YOesXLyGeZTPO3
gdQ2w7CSsPLMUAZMJMG+/K3qy1epbdAANRnVPCWyR8fjR9KvPnQ=
=j//V
-END PGP SIGNATURE-


-- 
Jordi Mallach 
Debian Project--- End Message ---

Bug#1059228: This is fixed in the next release 0.11.1

[Gianfranco Costamagna]

Hello,

On Fri, 15 Mar 2024 13:53:18 +0100 =?UTF-8?Q?Sebastian_Sp=C3=A4th?= 
 wrote:
This is fixed in the next release 0.11.1. However, I fail to build a 
package (due to my unexperience I guess).


When I try to build a package from
https://salsa.debian.org/DebianOnMobile-team/s2geometry

I get the error:

CMake Error at CMakeLists.txt:204 (target_link_libraries):
   Target "s2" links to:
 absl::check
   but the target was not found.  Possible reasons include:
 * There is a typo in the target name.
 * A find_package call is missing for an IMPORTED target.
 * An ALIAS target is missing.

So something seems to be missing in the abseil library that it depends 
on. I am a bit at a loss about how to fix this. With a working package I 
could upload a new version...


http://debomatic-amd64.debian.net/distribution#unstable/s2geometry/0.11.1-1/buildlog

Looks like now that newer abseil is in sid, this issue is gone (maybe the cmake 
was fixed in abseil side)

(however, one test looks failing)
78: [ RUN  ] S2PolygonTestBase.Area
111: .WARNING: All log messages before absl::InitializeLog() is called 
are written to STDERR
111: F 00:00:1712046075.956008 1262963 s2edge_distances.cc:405] Check failed: 
tolerance.radians() > 0 (0 vs. 0)
111: *** Check failure stack trace: ***
110/111 Test #111: s2geometry_test Subprocess 
aborted***Exception:   1.52 sec
...Index 
terms/doc: 13.00, Query terms/doc: 0.00


G.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1068226: libtrantor1, hardcoded dependency on libssl3

[Peter Michael Green]

Package: libtrantor1
Version: 1.5.12+ds-1
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

libtrantor1 was recently binnmu'd for the time_t transition,
however, despite the binnmu, it still depends on the old libssl3
because said dependency is hardcoded in the source package.

Ubuntu removed the dependency with the following changelog
entry.

trantor (1.5.12+ds-1ubuntu1) noble; urgency=medium

  * Drop spurious Depends on libssl3 as package is currently built with no TLS
provider.

 -- Michael Hudson-Doyle   Thu, 21 Mar 2024 15:06:24 
+1300

Please review the situation, and either drop the dependency or
change it to libssl3t64 as you deem appropriate.

Bug#1067312: spirv-tools: FTBFS: operand.kinds-unified1.inc:566:97: error: ‘SPV_OPERAND_TYPE_NAMED_MAXIMUM_NUMBER_OF_REGISTERS’ was not declared in this scope

[Giovanni Mascellani]

Hi,

On Wed, 20 Mar 2024 21:58:27 +0100 Lucas Nussbaum  
wrote:> During a rebuild of all packages in sid, your package failed to 
build

on amd64.


I'm having the same problem. As a data point, builds succeeds as soon as 
I revert spirv-headers to 1.6.1+1.3.275.0-1.


HTH, Gio.

Bug#1068224: deepin-movie, dependencies unsatisfiable on 32-bit non-i386 architectures.

[Peter Michael Green]

Package: deepin-movie
Version: 5.10.8-2
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, deepin-movie
still depends on libqt5concurrent5. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).

Ubuntu seem to have fixed this by manually changing the
dependency.

Bug#1066555: marked as done (kylin-nm: FTBFS: src/kylin-network-interface.c:197:5: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2024 07:34:12 +
with message-id 
and subject line Bug#1066555: fixed in kylin-nm 3.0.3.1-1
has caused the Debian Bug report #1066555,
regarding kylin-nm: FTBFS: src/kylin-network-interface.c:197:5: error: implicit 
declaration of function ‘asprintf’; did you mean ‘vsprintf’? 
[-Werror=implicit-function-declaration]
to be marked as done.

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

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


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

Hi,

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

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

Relevant part (hopefully):
> gcc -c -pipe -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -D_REENTRANT -fPIC 
> -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_X11EXTRAS_LIB -DQT_SVG_LIB 
> -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_CONCURRENT_LIB 
> -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -Isrc/singleapplication 
> -I/usr/include/x86_64-linux-gnu/qt5 
> -I/usr/include/x86_64-linux-gnu/qt5/QtX11Extras 
> -I/usr/include/KF5/KWindowSystem -I/usr/include/x86_64-linux-gnu/qt5/QtSvg 
> -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui 
> -I/usr/include/x86_64-linux-gnu/qt5/QtDBus 
> -I/usr/include/x86_64-linux-gnu/qt5/QtConcurrent 
> -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
> .obj/kylin-network-interface.o src/kylin-network-interface.c
> src/kylin-network-interface.c: In function ‘kylin_network_get_ifacename’:
> src/kylin-network-interface.c:44:20: warning: pointer targets in assignment 
> from ‘unsigned char *’ to ‘char *’ differ in signedness [-Wpointer-sign]
>44 | ifconf.ifc_buf = buf;
>   |^
> src/kylin-network-interface.c: In function ‘kylin_network_get_conlist_info’:
> src/kylin-network-interface.c:127:9: warning: statement with no effect 
> [-Wunused-value]
>   127 | for(index;*index!='\n';index++)
>   | ^~~
> src/kylin-network-interface.c:146:9: warning: statement with no effect 
> [-Wunused-value]
>   146 | for(index;*index!='\n';index++)
>   | ^~~
> src/kylin-network-interface.c:150:20: warning: suggest parentheses around 
> assignment used as truth value [-Wparentheses]
>   150 | if(*(index+1)=' ')
>   |^
> src/kylin-network-interface.c:157:9: warning: statement with no effect 
> [-Wunused-value]
>   157 | for(index1;*index1!='\n';index1++)
>   | ^~~
> src/kylin-network-interface.c:167:9: warning: statement with no effect 
> [-Wunused-value]
>   167 | for(index2;*index2!='\n';index2++)
>   | ^~~
> src/kylin-network-interface.c: In function ‘kylin_network_get_activecon_info’:
> src/kylin-network-interface.c:197:5: error: implicit declaration of function 
> ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]
>   197 | asprintf(, "%s%s%s", chr, tmpPrefix, name);
>   | ^~~~
>   | vsprintf
> src/kylin-network-interface.c:246:9: warning: statement with no effect 
> [-Wunused-value]
>   246 | for(index;*index!='\n';index++)
>   | ^~~
> src/kylin-network-interface.c:265:9: warning: statement with no effect 
> [-Wunused-value]
>   265 | for(index;*index!='\n';index++)
>   | ^~~
> src/kylin-network-interface.c:269:20: warning: suggest parentheses around 
> assignment used as truth value [-Wparentheses]
>   269 | if(*(index+1)=' ')
>   |^
> src/kylin-network-interface.c:276:9: warning: statement with no effect 
> [-Wunused-value]
>   276 | for(index1;*index1!='\n';index1++)
>   | ^~~
> 

Bug#1066630: Patch to address Debian Bug report #1066630

[Bill MacAllister]

The following patch results in a clean build.  I will work to get the 
patch

uploaded.  (I am not a Debian Developer)

Index: libnet-ldapapi-perl/Makefile.PL
===
--- libnet-ldapapi-perl.orig/Makefile.PL	2024-03-29 07:00:25.037139644 
+

+++ libnet-ldapapi-perl/Makefile.PL 2024-04-02 07:07:21.401195313 +
@@ -124,7 +124,7 @@
'DEFINE'=>  '-DMOZILLA_LDAP',
) : (
'LIBS'  =>  ["-L$lib_ldap $ldap_lib"],
-   'DEFINE'=>  '-DOPENLDAP',
+   'DEFINE'=>  '-DOPENLDAP -DLDAP_DEPRECATED=1',
)),
'depend'=>  { 'LDAPapi.c' => 'constant.h' },
'clean' =>  { 'FILES' => 'constant.h' },

The patch is from Quanah Gibson-Mount .  Thanks.

Bill

Bug#1068223: cyrus-imapd - FTBFS on 32-bit non-i386 architectures

[Peter Michael Green]

Package: cyrus-imapd
Version: 3.8.2-1
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t

cyrus-imapd is failing to build on the architectures affected by the
time_t transition (armel, armhf, several debian-ports architectures)
with the following error.


unit: fatal(Internal error: assertion failed: cunit/timeofday.c: 113: 
tv.tv_usec != 0x)

A quick look at the code, suggests that the testsuite is trying to
intercept gettimeofday, and this interception is broken by the
time64 changes.

The specific error appears to be cause by calling
the non-time64 gettimeofday function from glibc with the time64
definition of struct timeval, but I suspect there are other issues
with the interception code that will rear their ugly head if that one
is fixed.

Bug#1068222: libappmenu-gtk3-parser0, dependencies unsatisfiable on 32-bit non-i386 architectures.

[Peter Michael Green]

Package: libappmenu-gtk3-parser0
Version: 0.7.6-2.1
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, libappmenu-gtk3-parser0
depends on both libgtk3-0 and libgtk3-0t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).

Ubuntu already seem to have prepared a fix for this.

Bug#1068221: comet-ms, dependencies unsatisfiable on 32-bit non-i386 architectures.

[Peter Michael Green]

Package: comet-ms
Version: 2019015+cleaned1-4
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, comet-ms depends
on both libmstoolkit82 and libmstoolkit82t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).

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

[Alastair McKinstry]

On 01/04/2024 23:25, Sebastian Ramacher wrote:

There is a transition to openmpi-5 / mpi-defaults which is stalled by the
t64 transition.

It drops 32-bit support from OpenMPI.

Because of this, I don't think the solution is to  port 32-bit atomics for
armel/armhf, as it will be removed in a few weeks/months.

While we didn't want the transitions to be done simultaneously, it might be
the best answer.


What does the release team think?

Adding another transition on top will just delay the time_t transition
even more. So if we can avoid that, I'd prefer to not do this transition
now. Unfortunately, uploads such as the one of pmix that no dropped
support for 32 bit architectures (#1068211) are not really helpful.

Also, #1064810 has no information on test builds with the new
mpi-defaults on a 32 bit architecture. So has this transition been
tested?

Cheers


OpenMPI 5 drops 32-bit support, but otherwise does not change the 
API/ABI. So it is technically not a transition, but breaks 32-bit builds.


The solution is changing mpi-defaults to MPICH for 32-bit archs. MPICH 
builds on all archs, but testing all dependencies of the change has not 
been tested, and I don't know how you would do that - setting up eg ratt 
to rebuild all on 32-bit archs (as everything on 64-bit will not have 
changed.)


I'm sorry I missed the dropped 32-bit support for pmix; I tested on 
64-bit platforms only.


Regards

Alastair


--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e:alast...@mckinstry.ie, im: @alastair:mckinstry.ie

Bug#1063922: libnfft3-long4 has an undeclared file conflict

[Daniel Vacek]

Package: libnfft3-long4
Version: 3.5.3-3
Followup-For: Bug #1063922
X-Debbugs-Cc: neel...@gmail.com

There is a typo in the soname change patch. It should Breaks+Replaces
libnfft3-long2 but in fact it does B+R libnfft3-single2.

https://salsa.debian.org/science-
team/nfft/-/blob/debian/master/debian/control?ref_type=heads#L101
https://salsa.debian.org/science-
team/nfft/-/commit/7eb43a5fac433bae2cd24b74d4b7d32fb1515c57#58ef006ab62b83b4bec5d81fe5b32c3b4c2d1cc2_135_101

I'd also consider adding Provides: libnfft3-long2 (and vice versa for the other
precisions) otherwise dependents need to be rebuilt which is not needed in this
case, IIUC. This applies to current version of `python3-pynfft` which is not
satisfied and needs to be removed at the moment.

--nX


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

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

Versions of packages libnfft3-long4 depends on:
ii  libc6   2.37-15
ii  libfftw3-long3  3.3.10-1+b1
ii  libgomp114-20240201-3

libnfft3-long4 recommends no packages.

libnfft3-long4 suggests no packages.