Bug#1064374: marked as done (rust-gtk-layer-shell-sys: Depends on obsolete rust-gtk)

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 04:31:10 +
with message-id 
and subject line Bug#1069111: Removed package(s) from unstable
has caused the Debian Bug report #1064374,
regarding rust-gtk-layer-shell-sys: Depends on obsolete rust-gtk
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.)


-- 
1064374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-gtk-layer-shell-sys
Version: 0.7.0-1
Severity: serious
X-Debbugs-CC: maytha8the...@gmail.com, sylves...@debian.org

rust-gtk-layer-shell-sys (and rust-gtk-layer-shell) depends on
rust-gtk which is the old GTK3 library that is no longer maintained.
rust-gtk is only in Debian because of squeekboard.

Please instead package https://crates.io/crates/gtk4-layer-shell and
encourage apps using the old rust-gtk-layer-shell to switch to the
gtk4 version.

Please let me know if there is a reason we should not file a removal
bug for rust-gtk-layer-shell-sys (which only appeared in Debian this
month).

On behalf of the Debian Rust Maintainers,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Version: 0.7.0-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#1062773: marked as done (python-watchgod: autopkgtest needs update for new version of python-anyio)

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 04:30:42 +
with message-id 
and subject line Bug#1061967: Removed package(s) from unstable
has caused the Debian Bug report #1062773,
regarding python-watchgod: autopkgtest needs update for new version of 
python-anyio
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.)


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

Source: python-watchgod
Version: 0.8.2-2
Severity: serious
X-Debbugs-CC: python-an...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-anyio

Dear maintainer(s),

[I note that python-watchgod has been requested for removal, but it has 
a big chain of reverse dependencies, so this bug is mostly to warn them, 
as it will trigger autoremoval from testing of python-watchgod and these 
reverse dependencies.]


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


   passfail
python-anyio   from testing4.2.0-1
python-watchgodfrom testing0.8.2-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of python-anyio to 
testing [1]. Of course, python-anyio shouldn't just break your 
autopkgtest (or even worse, your package), but it seems to me that the 
change in python-anyio was intended and your package needs to update to 
the new situation.


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-watchgod/42699299/log.gz

=== FAILURES 
===
 57s _ test_async_alive_terminates[asyncio+uvloop] 
__
 57s  57s pyfuncitem = test_async_alive_terminates[asyncio+uvloop]>

 57s  57s @pytest.hookimpl(tryfirst=True)
 57s def pytest_pyfunc_call(pyfuncitem: Any) -> bool | None:
 57s def run_with_hypothesis(**kwargs: Any) -> None:
 57s with get_runner(backend_name, backend_options) as runner:
 57s runner.run_test(original_func, kwargs)
 57s  57s backend = pyfuncitem.funcargs.get("anyio_backend")
 57s if backend:
 57s backend_name, backend_options = 
extract_backend_and_options(backend)

 57s  57s if hasattr(pyfuncitem.obj, "hypothesis"):
 57s # Wrap the inner test function unless it's already 
wrapped

 57s original_func = pyfuncitem.obj.hypothesis.inner_test
 57s if original_func.__qualname__ != 
run_with_hypothesis.__qualname__:

 57s if iscoroutinefunction(original_func):
 57s pyfuncitem.obj.hypothesis.inner_test = 
run_with_hypothesis

 57s  57s return None
 57s  57s if iscoroutinefunction(pyfuncitem.obj):
 57s funcargs = pyfuncitem.funcargs
 57s testargs = {arg: funcargs[arg] for arg in 
pyfuncitem._fixtureinfo.argnames}
 57s >   with get_runner(backend_name, backend_options) as 
runner:
 57s  57s /usr/lib/python3/dist-packages/anyio/pytest_plugin.py:123: 
57s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _  57s /usr/lib/python3.11/contextlib.py:137: in __enter__

 57s return next(self.gen)
 57s /usr/lib/python3/dist-packages/anyio/pytest_plugin.py:45: in 
get_runner

 57s asynclib.create_test_runner(backend_options)
 57s /usr/lib/python3/dist-packages/anyio/_backends/_asyncio.py:2465: 
in create_test_runner

 57s return TestRunner(**options)
 57s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _  57s  57s self = object at 0x9513e590>

Bug#1061026: marked as done (python-watchgod: FTBFS: FAILED tests/test_watch.py::test_watch_log[trio] - RuntimeError: Already runn...)

[Debian Bug Tracking System]

Your message dated Sat, 20 Apr 2024 04:30:42 +
with message-id 
and subject line Bug#1061967: Removed package(s) from unstable
has caused the Debian Bug report #1061026,
regarding python-watchgod: FTBFS: FAILED 
tests/test_watch.py::test_watch_log[trio] - RuntimeError: Already runn...
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config 
> running config
> I: pybuild base:305: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/version.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/main.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/watcher.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/__main__.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/cli.py -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> copying watchgod/py.typed -> 
> /<>/.pybuild/cpython3_3.12_watchgod/build/watchgod
> I: pybuild base:305: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/version.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/main.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/watcher.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/__main__.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/cli.py -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
> copying watchgod/py.typed -> 
> /<>/.pybuild/cpython3_3.11_watchgod/build/watchgod
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_watchgod/build; python3.12 -m pytest 
> -W ignore::trio.TrioDeprecationWarning
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> configfile: setup.cfg
> plugins: anyio-4.1.0, asyncio-0.20.3, toolbox-0.4, sugar-0.9.7, mock-3.12.0
> asyncio: mode=Mode.STRICT
> collected 162 items
> 
> tests/test_cli.py .. [ 
> 33%]
> ...  [ 
> 42%]
> tests/test_run_process.py F..[ 
> 51%]
> tests/test_watch.py  [ 
> 83%]
> ....F..F..   
> [100%]
> 
> === FAILURES 
> ===
> _ test_async_alive_terminates[asyncio+uvloop] 
> __
> 
> pyfuncitem = 
> 
> @pytest.hookimpl(tryfirst=True)
> def pytest_pyfunc_call(pyfuncitem: Any) -> bool | None:
> def run_with_hypothesis(**kwargs: Any) -> None:
> with get_runner(backend_name, backend_options) as runner:
> runner.run_test(original_func, kwargs)
> 
> backend = pyfuncitem.funcargs.get("anyio_backend")
> if backend:
> backend_name, backend_options = 
> extract_backend_and_options(backend)
> 
> if hasattr(pyfuncitem.obj, "hypothesis"):
> # Wrap the inner test function unless it's already wrapped
> original_func = pyfuncitem.obj.hypothesis.inner_test
> if original_func.__qualname__ != 
> run_with_hypothesis.__qualname__:
> if 

Bug#1037699: intel-mediasdk: ftbfs with GCC-13

[Zixing Liu]

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

Dear Maintainer,

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

  * debian/patches/fix-missing-includes.patch: Add missing header
includes. (LP: #2062948).


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-28-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru intel-mediasdk-22.5.4/debian/patches/fix-missing-includes.patch 
intel-mediasdk-22.5.4/debian/patches/fix-missing-includes.patch
--- intel-mediasdk-22.5.4/debian/patches/fix-missing-includes.patch 
1969-12-31 17:00:00.0 -0700
+++ intel-mediasdk-22.5.4/debian/patches/fix-missing-includes.patch 
2024-04-19 21:28:34.0 -0600
@@ -0,0 +1,18 @@
+Description: Add missing header includes
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037699
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/2062948
+Forwarded: no
+Last-Update: 2024-04-19
+---
+--- intel-mediasdk-22.5.4.orig/api/mfx_dispatch/linux/mfxparser.cpp
 intel-mediasdk-22.5.4/api/mfx_dispatch/linux/mfxparser.cpp
+@@ -22,7 +22,7 @@
+ #include 
+ #include 
+ #include 
+-
++#include 
+ #include 
+ 
+ #include "mfxloader.h"
diff -Nru intel-mediasdk-22.5.4/debian/patches/series 
intel-mediasdk-22.5.4/debian/patches/series
--- intel-mediasdk-22.5.4/debian/patches/series 2022-10-18 05:16:05.0 
-0600
+++ intel-mediasdk-22.5.4/debian/patches/series 2024-04-19 21:13:23.0 
-0600
@@ -1 +1,2 @@
 #placeholder
+fix-missing-includes.patch

Processed: Re: intel-mediasdk: ftbfs with GCC-13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1037699 [src:intel-mediasdk] intel-mediasdk: ftbfs with GCC-13
Ignoring request to alter tags of bug #1037699 to the same tags previously set

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

Bug#1069309: marked as done (xfractint FTBFS: error: implicit declaration of function)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 23:50:55 +
with message-id 
and subject line Bug#1069309: fixed in xfractint 20.4.10-5
has caused the Debian Bug report #1069309,
regarding xfractint FTBFS: error: implicit declaration of function
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.)


-- 
1069309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfractint
Version: 20.4.10-4
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Petter Reinholdtsen 

https://buildd.debian.org/status/logs.php?pkg=xfractint=20.4.10-4

...
/usr/bin/gcc -I../headers -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-mbranch-protection=standard -I./headers -DXFRACT  -DNOBSTRING   -g 
-DBIG_ANSI_C -DLINUX -fno-builtin -fcommon -O2 -Wdate-time -D_FORTIFY_SOURCE=2  
-c -o 3d.o 3d.c
3d.c: In function ‘longvmultpersp’:
3d.c:290:20: error: implicit declaration of function ‘multiply’ 
[-Werror=implicit-function-declaration]
  290 |  tmp[j] += multiply(s[i],m[i][j],bitshift);
  |^~~~
3d.c:318:20: error: implicit declaration of function ‘divide’ 
[-Werror=implicit-function-declaration]
  318 |   tmpview[0] = divide(lview[0],denom,bitshift);
  |^~
cc1: some warnings being treated as errors
make[3]: *** [: 3d.o] Error 1
--- End Message ---
--- Begin Message ---
Source: xfractint
Source-Version: 20.4.10-5
Done: Petter Reinholdtsen 

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

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

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated xfractint 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: Sat, 20 Apr 2024 01:16:21 +0200
Source: xfractint
Architecture: source
Version: 20.4.10-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Petter Reinholdtsen 
Closes: 1069309
Changes:
 xfractint (20.4.10-5) unstable; urgency=medium
 .
   * QA upload.
 .
   * Added 1030-no-implicit-declaration.patch to fix build problem
 (Closes: #1069309).
Checksums-Sha1:
 9ea5d0559462e62f70d74e6ef19ab086543b5f65 1901 xfractint_20.4.10-5.dsc
 d1c642a50b7b7384b4610d00f4a4d97ef56b38e2 8312 xfractint_20.4.10-5.debian.tar.xz
 83089127b415877ac18b822465765092bd8d0605 6861 
xfractint_20.4.10-5_source.buildinfo
Checksums-Sha256:
 01a4ea7dae2b788f6b9efdd6d23cae744734dd0ae3da7591275feb626e363f5e 1901 
xfractint_20.4.10-5.dsc
 856f398da106ba975b849e6053f7e08a5b123144ad680554f71630553e761530 8312 
xfractint_20.4.10-5.debian.tar.xz
 6a0ef1208d1fe4a49553635953e3e36145e7f1548974acc5cd0f234bdc98ed8d 6861 
xfractint_20.4.10-5_source.buildinfo
Files:
 a33e1344877e50e5f56b2344914f26e4 1901 non-free/graphics optional 
xfractint_20.4.10-5.dsc
 7572ab1b79b7849d95efa0bdd70006c5 8312 non-free/graphics optional 
xfractint_20.4.10-5.debian.tar.xz
 736e5e708eabd41452203a0f0e40a256 6861 non-free/graphics optional 
xfractint_20.4.10-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmYi/AoACgkQgSgKoIe6
+w4LcA/+JVzulbP6dWP5uDBcatN1GeK4eZC2qllpY8CacloFfMMHiKq+jVCPGZzr
Ez+BHuIpMEhxK/NRqU7KrNcoO8DqvIvsADn8L+EItbrkcMaThoErMksabmf14lX5
L8t4fLu6kXsmAHbSRlx0RhJ+meI+xW9j5gwAjVjg1Rzz6vlUmDINoq+mhwZOZAwz
S6wWP6jhFPo5UZ0Fb4Mdf+V8OqT+nIMeVLEn6nU/knbNXr4xZ9/nGXM/bc+lPTCa
BaEe7qJAnqAqSv/plAIhbmarCm/BXXIFVud+DwKWuleeq2AOwX3N22W7+l8EQS7I
e/uRdBq52UK9iuWdb5rxuY3BbvQg1x0T4Rzd0RJpeo8CrLrXnUqLYCPZYWcvLa2C
18W29Hw0u1bNqqNGkhKd7CZxlESclZ8d6d1/8qcaxQ9FlILnjKgznb8Bs31YeQQl
Oc6ToftiNRQ3qnL3WAx+1eN5Qicnx4JA0RFHrkS99MvpDZrlXhEaFA63fPxMjNwK
0QjJrMPwTN9X0bmmx0jZT/LJB/H2mkLd9vNnXRDal5QSdezipeZ0FajmwAh1ULuM
JN8CH2cahB2zcXTYPW3UdAHuygDMy6PBjYRFwsYubOBHTmGsHZAJPYlIXcXHJLdh
x4+6v+WQvAnu8P7+qBX1g++hubqlxHBCnFW4y5cf/YHOGg4MG5Y=
=0j4s
-END PGP SIGNATURE-



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

Bug#1068580: marked as done (collected: FTBFS on arm{el,hf}: configure: error: "Some plugins are missing dependencies - see the summary above for details")

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 23:04:34 +
with message-id 
and subject line Bug#1068580: fixed in collectd 5.12.0-18
has caused the Debian Bug report #1068580,
regarding collected: FTBFS on arm{el,hf}: configure: error: "Some plugins are 
missing dependencies - see the summary above for details"
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.)


-- 
1068580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: collectd
Version: 5.12.0-17.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=collectd=armhf=5.12.0-17.1=1712493429=0


Configuration:
  Build:
Platform  . . . . . . Linux
Compiler vendor . . . gnu
CC  . . . . . . . . . arm-linux-gnueabihf-gcc
CFLAGS  . . . . . . . -Wall -Werror -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -Wno-error=deprecated-declarations 
-Wno-error=address-of-packed-member -Wno-stringop-truncation -Wno-cpp 
-Wno-error=format-truncation
CXXFLAGS  . . . . . . -Wall -Werror -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -Wall 
-Wno-error=deprecated-declarations
CPP . . . . . . . . . arm-linux-gnueabihf-gcc -E
CPPFLAGS  . . . . . . -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
-I/<>/debian/include -UCONFIGFILE 
-DCONFIGFILE='"/etc/collectd/collectd.conf"'
GRPC_CPP_PLUGIN . . . /usr/bin/grpc_cpp_plugin
LD  . . . . . . . . . /usr/bin/ld
LDFLAGS . . . . . . . -Wl,-z,relro -Wl,-z,now
PROTOC  . . . . . . . /usr/bin/protoc
YACC  . . . . . . . . bison -y
YFLAGS  . . . . . . . 

  Libraries:
intel mic . . . . . . no (MicAccessApi not found)
libaquaero5 . . . . . no (libaquaero5.h not found)
libatasmart . . . . . yes
libcurl . . . . . . . yes
libdbi  . . . . . . . yes
libdpdk . . . . . . . no (rte_config.h not found)
libesmtp  . . . . . . yes
libganglia  . . . . . no (gm_protocol.h not found)
libgcrypt . . . . . . yes
libgps  . . . . . . . yes
libgrpc++ . . . . . . no ( not found)
libhiredis  . . . . . yes
libi2c-dev  . . . . . yes
libiokit  . . . . . . no
libiptc . . . . . . . yes
libjansson  . . . . . yes
libjevents  . . . . . no (jevents.h not found)
libjvm  . . . . . . . yes
libkstat  . . . . . . no (Solaris only)
libkvm  . . . . . . . no
libldap . . . . . . . yes
liblua  . . . . . . . yes
libmemcached  . . . . yes
libmicrohttpd . . . . yes
libmnl  . . . . . . . yes
libmodbus . . . . . . yes
libmongoc . . . . . . yes
libmosquitto  . . . . yes
libmysql  . . . . . . yes
libnetapp . . . . . . no (netapp_api.h not found)
libnetsnmp  . . . . . yes
libnetsnmpagent . . . yes
libnotify . . . . . . yes
libnvidia-ml  . . . . no
libopenipmi . . . . . yes
liboping  . . . . . . yes
libowcapi . . . . . . yes
libpcap . . . . . . . yes
libperfstat . . . . . no (AIX only)
libperl . . . . . . . yes (version 5.38.2)
libpmwapi . . . . . . no (pmw_api.h not found)
libpq . . . . . . . . yes
libpqos . . . . . . . no (pqos.h not found)
libprotobuf . . . . . yes
libprotobuf-c . . . . yes
libpython . . . . . . yes
libqpid-proton .  . . yes
librabbitmq . . . . . yes
libriemann-client . . yes
librdkafka  . . . . . yes
librouteros . . . . . no (routeros_api.h not found)
librrd  . . . . . . . yes
libsensors  . . . . . yes
libsigrok   . . . . . no (pkg-config could not find libsigrok)
libssl  . . . . . . . yes
libslurm .  . . . . . no (pkg-config doesn't know libslurm)
libstatgrab . . . . . no
libtokyotyrant  . . . no (tcrdb.h not found)
libudev . . . . . . . yes
libupsclient  . . . . yes
libvarnish  . . . . . no (pkg-config doesn't know varnishapi)
libvirt . . . . . . . yes
libxenctrl  . . . . . yes
libxml2 . . . . . . . yes
libxmms . . . . . . . no
libyajl . . . . . . . yes
oracle  . . . . . . . no (ORACLE_HOME is not set)
protobuf-c  . . . . . yes
protoc 3  . . . . . . yes

  Features:
daemon mode . . . . . yes
debug . . . . . . . . no

  Bindings:
perl  . . . . . . . . yes (INSTALLDIRS=vendor INSTALL_BASE=)

  Modules:

Bug#1068538: ruby-ffi-libarchive: arch:all package depends on pre-t64 library

[Bastian Germann]

This can be fixed with a binNMU.

Bug#1059673: trololio: autopkgtest failure with Python 3.12

[me]

Hi,

I'm the author of Trololio.
I've never posted to Debian mailing lists, so apologies if I don't
follow proper etiquette. I did take a quick look at the relevant Wiki
page and CoC.

Trololio was written to make Python 3 async easily back-compatible
with Python 2.
The context is Trollius was a back-port of Python 3's asyncio module
to Python 2, and Trololio provides a compatibility layer to support
both with a single codebase.
Similar to what the six module does for general 2/3 compatibility.

Nowadays, Python 2 compatibility is not a priority for most anymore,
and Trollius has been deprecated since at least 2018 [1].
And as per the discussion on GitHub, pagure-ev-server seems to be the
only reverse dependency. Its author removed the dependency in a commit
yesterday [2].

With that in mind, I think it's best to retire the package.
If you do need to keep it working for stable, then I can try and update
it to use importlib. Though I would rather not spend time on a Python 2
related project these days :)

Thanks,
ThinkChaos (they/them)

[1] 
https://github.com/jamadden/trollius/commit/479788fb7b568c0c685599e55e0e98cab9fe474c
[2] 
https://pagure.io/pagure/c/59edf699016d1049fdaecd1ff728ad8eeb355b64?branch=master

Bug#1069017: marked as done (rtags: FTBFS due to time64_t changes)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 22:36:59 +
with message-id 
and subject line Bug#1069017: fixed in rtags 2.38-10
has caused the Debian Bug report #1069017,
regarding rtags: FTBFS due to time64_t changes
to be marked as done.

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

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


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

Package: rtags
Version: 2.38-9
Severity: serious
Tags: patch

Hello maintainer, I fixed a FTBFS on armhf due to time64_t. The regex was causing 
"=64" to be stripped from _FILE_OFFSET_BITS, causing cmake to fail to build 
test code.

With this regex the example test code of clang fails in cmake, causing an error.
this is due to -I/usr/lib/llvm-18/include -std=c++17 -fno-exceptions 
-funwind-tables -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS 
-D__STDC_LIMIT_MACROS
becoming:
-I/usr/lib/llvm-18/include;-D_GNU_SOURCE;-D_FILE_OFFSET_BITS;-D_LARGEFILE_SOURCE;-D_FILE_OFFSET_BITS;-D__STDC_CONSTANT_MACROS;-D__STDC_FORMAT_MACROS;-D__STDC_LIMIT_MACROS

If you undefine _FILE_OFFSET_BITS and you enable _TIME_BITS=64 you get a FTBFS

/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only 
with _FILE_OFFSET_BITS=64"
26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"


  * Fix regex on find clang without stripping defines content.


Thanks for considering the patch.
diff -Nru rtags-2.38/debian/patches/fix-regex.patch 
rtags-2.38/debian/patches/fix-regex.patch
--- rtags-2.38/debian/patches/fix-regex.patch   1970-01-01 01:00:00.0 
+0100
+++ rtags-2.38/debian/patches/fix-regex.patch   2024-04-15 08:50:11.0 
+0200
@@ -0,0 +1,18 @@
+Description:
+   * Add -D_FILE_OFFSET_BITS=64 to fix FTBFS on armhf
+ (bad regex on find clang making build fail)
+Author: Gianfranco Costamagna 
+Forwarded: https://github.com/Andersbakken/rtags/pull/1439
+Last-Update: 2024-04-15
+
+--- rtags-2.38.orig/cmake/FindLibClang.cmake
 rtags-2.38/cmake/FindLibClang.cmake
+@@ -88,7 +88,7 @@ if (NOT LIBCLANG_CXXFLAGS)
+ endif ()
+ set(LIBCLANG_CXXFLAGS "-I${LIBCLANG_CXXFLAGS}")
+ endif ()
+-string(REGEX MATCHALL "-(D__?[a-zA-Z_]*|I([^\" ]+|\"[^\"]+\"))" LIBCLANG_CXXFLAGS 
"${LIBCLANG_CXXFLAGS}")
++string(REGEX MATCHALL "-(D__?[a-zA-Z_=0-9]*|I([^\" ]+|\"[^\"]+\"))" 
LIBCLANG_CXXFLAGS "${LIBCLANG_CXXFLAGS}")
+ string(REGEX REPLACE ";" " " LIBCLANG_CXXFLAGS "${LIBCLANG_CXXFLAGS}")
+ set(LIBCLANG_CXXFLAGS ${LIBCLANG_CXXFLAGS} CACHE STRING "The LLVM C++ compiler 
flags needed to compile LLVM based applications.")
+ unset(LIBCLANG_CXXFLAGS_HACK_CMAKECACHE_DOT_TEXT_BULLSHIT CACHE)
diff -Nru rtags-2.38/debian/patches/series rtags-2.38/debian/patches/series
--- rtags-2.38/debian/patches/series2023-08-29 19:36:08.0 +0200
+++ rtags-2.38/debian/patches/series2024-04-15 08:49:15.0 +0200
@@ -15,3 +15,4 @@
 0015-expand-range-of-llvm-versions.patch
 0016-always-finish-the-connection.patch
 0017-Add-when-argument-to-define-obsolete-function-alias.patch
+fix-regex.patch


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: rtags
Source-Version: 2.38-10
Done: Denis Danilov 

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

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

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

Debian distribution maintenance software
pp.
Denis Danilov  (supplier of updated rtags 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, 19 Apr 2024 23:52:58 +0200
Source: rtags
Architecture: source
Version: 2.38-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Denis Danilov 
Closes: 1069017
Changes:
 rtags (2.38-10) unstable; urgency=medium
 .
   * add patch by Gianfranco Costamagna to fix build failure (Closes: #1069017)
   * fix lintian warning
   * update Standards Version to 4.7.0
Checksums-Sha1:
 7969e4241730b1b025d99ec67e70c05ba5ce4b26 2435 rtags_2.38-10.dsc
 

Bug#1067209: marked as done (jruby: please update libfixposix4 runtime depency)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 22:35:55 +
with message-id 
and subject line Bug#1067209: fixed in jruby 9.4.6.0+ds-1.1
has caused the Debian Bug report #1067209,
regarding jruby: please update libfixposix4 runtime depency
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.)


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

Package: jruby
Version: 9.4.6.0+ds-1
Severity: serious
Tags: patch

Hello, libfixposix4 was renamed in libfixposix4t64, please drop or update the 
runtime dependency accordingly


Thanks for considering the patch.

diff -Nru jruby-9.4.6.0+ds/debian/control jruby-9.4.6.0+ds/debian/control
--- jruby-9.4.6.0+ds/debian/control 2024-03-08 08:55:39.0 +0100
+++ jruby-9.4.6.0+ds/debian/control 2024-03-20 07:56:30.0 +0100
@@ -63,7 +62,7 @@
  libasm-java (>= 9.5),
  libbackport9-java (>= 1.10),
  libdirgra-java,
- libfixposix4,
+ libfixposix4t64,
  libheadius-options-java (>= 1.4),
  libinvokebinder-java (>= 1.13),
  libjansi1-java,


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: jruby
Source-Version: 9.4.6.0+ds-1.1
Done: Bastian Germann 

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

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

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated jruby 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, 19 Apr 2024 22:06:26 +
Source: jruby
Architecture: source
Version: 9.4.6.0+ds-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Bastian Germann 
Closes: 1067209
Changes:
 jruby (9.4.6.0+ds-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Gianfranco Costamagna ]
   * d/control: update libfixposix4 runtime depency (Closes: #1067209)
Checksums-Sha1:
 0851c4c86b106db437db7f9423b69ee1a5909443 3342 jruby_9.4.6.0+ds-1.1.dsc
 725dc4d63e020554083268efac5c280b919e2aab 3 
jruby_9.4.6.0+ds-1.1.debian.tar.xz
 52d1898b4440f3750aab4c437888c53294621e85 14837 
jruby_9.4.6.0+ds-1.1_source.buildinfo
Checksums-Sha256:
 9e7a53a2cd26d9d9713cd08bf49efc6beaad1458c2f4b1dad926c4e3cc4bc0b3 3342 
jruby_9.4.6.0+ds-1.1.dsc
 0bb73e9a579aa9cd37a847f48e53cfb7bb0a04122615ca340affce4f920f126d 3 
jruby_9.4.6.0+ds-1.1.debian.tar.xz
 ec16a5077ebb39f0a5c1e1306b109f96ce8b5e150b7ee7b11e980dd3840ba224 14837 
jruby_9.4.6.0+ds-1.1_source.buildinfo
Files:
 633bc300048fec4b5ad8afa25fb53cf6 3342 ruby optional jruby_9.4.6.0+ds-1.1.dsc
 ff70a6762925531c0a7d124634f9f1dd 3 ruby optional 
jruby_9.4.6.0+ds-1.1.debian.tar.xz
 47ba88aaf02234214416e5ee2c77ed19 14837 ruby optional 
jruby_9.4.6.0+ds-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYi7hYQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFOvjC/9NWZIpvgy2QyuB/0vS71Un+qW4oHWGdxp5
xe6lh7Tz/EiUD8G5vlZYfqg3BoNVxhoH2nYbV9WqwBGOghp/1xCV1yT5ZiIX11D4
PGp73B85kE1GtVBfyb4iGeQEAnNlRyHVm7BaRNSRV0fZ/KySrYovcnxlhOijx/tg
N8RfrjnZO1UFlwxDIPKQLrvF8sz0OYU/LYocp09RvXAuf2odCkmC/kLgfzmQvOrl
C7elT061ZS8i+t/VcBF3VBMYPEhXjVJXq9AppEiUjVq/csZ9S54j9GXLSxvqZmGh
Ex0G2hZfFtmYucMyYfKR+pKaj8Y36228Emaf7JRxWTsD2f2TVarPNCCHtrLgUww1
BJ9GPjgNqen3hmiuqwoym4By6pW3krU7FqLBJfUEasfDjC7S5lWvGziQloOsYsKg
yUEJfG5LN9Mo3z3REVTf/aAUR02GIte61LmG60smZI403ulGTFb1qvaMDc52uTsS
umL9N4XdKmKJGsi7jF2sCKmxaJqJVoo=
=UMSM
-END PGP SIGNATURE-



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

Bug#1067209: jruby: please update libfixposix4 runtime depency

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru jruby-9.4.6.0+ds/debian/changelog jruby-9.4.6.0+ds/debian/changelog
--- jruby-9.4.6.0+ds/debian/changelog   2024-02-29 00:39:52.0 +
+++ jruby-9.4.6.0+ds/debian/changelog   2024-04-19 22:06:26.0 +
@@ -1,3 +1,12 @@
+jruby (9.4.6.0+ds-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Gianfranco Costamagna ]
+  * d/control: update libfixposix4 runtime depency (Closes: #1067209)
+
+ -- Bastian Germann   Fri, 19 Apr 2024 22:06:26 +
+
 jruby (9.4.6.0+ds-1) unstable; urgency=medium
 
   * New upstream version 9.4.6.0+ds
diff -Nru jruby-9.4.6.0+ds/debian/control jruby-9.4.6.0+ds/debian/control
--- jruby-9.4.6.0+ds/debian/control 2024-02-29 00:39:52.0 +
+++ jruby-9.4.6.0+ds/debian/control 2024-04-19 22:05:30.0 +
@@ -62,7 +62,7 @@
  libasm-java (>= 9.5),
  libbackport9-java (>= 1.10),
  libdirgra-java,
- libfixposix4,
+ libfixposix4t64,
  libheadius-options-java (>= 1.4),
  libinvokebinder-java (>= 1.13),
  libjansi1-java,

Bug#1066938: Fwd: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined

[Santiago Vila]

El 25/3/24 a las 20:12, Chris Lamb escribió:

Alberto Bertogli wrote:


If you know of a functional official image that I can use to try to
reproduce the problem, or recently-tested steps I can follow to get
a working qemu install, please let me know.


Alas, I can't actually be helpful here. There are no official images
as far as I know… and somewhat annoyingly I (ie. a Debian Developer)
actually have access to some machines set aside for this purpose. I
call this "annoying" because I naturally can't then give you direct
SSH access transitively — but I can proxy ideas, of course.


Hi.

I can't offer ssh access either (for now), but I've checked and
this error may be reproduced easily on an arm64 machine using an
armel chroot.

Several cloud vendors (like GCP, AWS or Hetzner) offer arm64 machines,
billed hourly and relatively cheap.

Also (but only if your stomach allows it :-), Oracle Cloud has arm64 machines in
their Free Tier. In this case I think they only have Ubuntu and not Debian,
but this would be not matter if you are using a Debian chroot.

Thanks.

Bug#1066483: scrollz: FTBFS: configure: error: Fatal: You must get working getaddrinfo() function.

[Mike Markley]

I've updated this package to a newer upstream release and it seems to
build fine on my own amd64 system.

However, I haven't had a key in the Debian key ring for quite some time
and I'm not able to upload.

I'm starting here in the hopes that someone who's also interested in this
package will see it; I'll seek a sponsor to upload it on my behalf soon if
this bug doesn't catch anyone's eye.

-- 
Mike Markley 

Bug#1069017: rtags: FTBFS due to time64_t changes

[Denis Danilov]

Hi Gianfranco,

thanks for the patch with the fix. I will upload new version with our patch 
included.

Best regards,
Denis


On Mon, Apr 15, 2024 at 09:00:06AM +0200, Gianfranco Costamagna wrote:
> Package: rtags
> Version: 2.38-9
> Severity: serious
> Tags: patch
> 
> Hello maintainer, I fixed a FTBFS on armhf due to time64_t. The regex was 
> causing "=64" to be stripped from _FILE_OFFSET_BITS, causing cmake to fail to 
> build test code.
> 
> With this regex the example test code of clang fails in cmake, causing an 
> error.
> this is due to -I/usr/lib/llvm-18/include -std=c++17 -fno-exceptions 
> -funwind-tables -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS 
> -D__STDC_LIMIT_MACROS
> becoming:
> -I/usr/lib/llvm-18/include;-D_GNU_SOURCE;-D_FILE_OFFSET_BITS;-D_LARGEFILE_SOURCE;-D_FILE_OFFSET_BITS;-D__STDC_CONSTANT_MACROS;-D__STDC_FORMAT_MACROS;-D__STDC_LIMIT_MACROS
> 
> If you undefine _FILE_OFFSET_BITS and you enable _TIME_BITS=64 you get a FTBFS
> 
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
> only with _FILE_OFFSET_BITS=64"
> 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
> 
> 
>   * Fix regex on find clang without stripping defines content.
> 
> 
> Thanks for considering the patch.
> diff -Nru rtags-2.38/debian/patches/fix-regex.patch 
> rtags-2.38/debian/patches/fix-regex.patch
> --- rtags-2.38/debian/patches/fix-regex.patch 1970-01-01 01:00:00.0 
> +0100
> +++ rtags-2.38/debian/patches/fix-regex.patch 2024-04-15 08:50:11.0 
> +0200
> @@ -0,0 +1,18 @@
> +Description:
> +   * Add -D_FILE_OFFSET_BITS=64 to fix FTBFS on armhf
> + (bad regex on find clang making build fail)
> +Author: Gianfranco Costamagna 
> +Forwarded: https://github.com/Andersbakken/rtags/pull/1439
> +Last-Update: 2024-04-15
> +
> +--- rtags-2.38.orig/cmake/FindLibClang.cmake
>  rtags-2.38/cmake/FindLibClang.cmake
> +@@ -88,7 +88,7 @@ if (NOT LIBCLANG_CXXFLAGS)
> + endif ()
> + set(LIBCLANG_CXXFLAGS "-I${LIBCLANG_CXXFLAGS}")
> + endif ()
> +-string(REGEX MATCHALL "-(D__?[a-zA-Z_]*|I([^\" ]+|\"[^\"]+\"))" 
> LIBCLANG_CXXFLAGS "${LIBCLANG_CXXFLAGS}")
> ++string(REGEX MATCHALL "-(D__?[a-zA-Z_=0-9]*|I([^\" ]+|\"[^\"]+\"))" 
> LIBCLANG_CXXFLAGS "${LIBCLANG_CXXFLAGS}")
> + string(REGEX REPLACE ";" " " LIBCLANG_CXXFLAGS "${LIBCLANG_CXXFLAGS}")
> + set(LIBCLANG_CXXFLAGS ${LIBCLANG_CXXFLAGS} CACHE STRING "The LLVM C++ 
> compiler flags needed to compile LLVM based applications.")
> + unset(LIBCLANG_CXXFLAGS_HACK_CMAKECACHE_DOT_TEXT_BULLSHIT CACHE)
> diff -Nru rtags-2.38/debian/patches/series rtags-2.38/debian/patches/series
> --- rtags-2.38/debian/patches/series  2023-08-29 19:36:08.0 +0200
> +++ rtags-2.38/debian/patches/series  2024-04-15 08:49:15.0 +0200
> @@ -15,3 +15,4 @@
>  0015-expand-range-of-llvm-versions.patch
>  0016-always-finish-the-connection.patch
>  0017-Add-when-argument-to-define-obsolete-function-alias.patch
> +fix-regex.patch

Processed: Re: Bug#1061546: srcpd: installs file into aliased location

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1061546 [src:srcpd] srcpd: installs file into aliased location
Added tag(s) pending.

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

Bug#1061546: srcpd: installs file into aliased location

[Preuße]

Control: tags -1 + pending

On 26.01.2024 23:01, Preuße...@buxtehude.debian.org, Hilmar wrote:

On 26.01.2024 09:35, Chris Hofstaedtler wrote:


Hi,


Please move /lib/udev/rules.d/10-liusb.rules into /usr/lib before
srcpd reaches testing.



hille42@hz:~/devel/srcpd$ dpkg-deb -c srcpd_2.1.6-2_amd64.deb|grep usb
-rw-r--r-- root/root   151 2024-01-26 21:45 
./usr/lib/udev/rules.d/10-liusb.rules


I guess this looks OK, not sure when I'll upload.


Tag bug pending, time for upload still not determined.

H.
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1058200: marked as done (python-pyepics: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 21:10:16 +
with message-id 
and subject line Bug#1058200: fixed in python-pyepics 3.5.2+ds-1
has caused the Debian Bug report #1058200,
regarding python-pyepics: FTBFS: AttributeError: module 'configparser' has no 
attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?
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.)


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

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean 
> /<>/versioneer.py:421: SyntaxWarning: invalid escape sequence 
> '\s'
>   LONG_VERSION_PY['git'] = '''
> Traceback (most recent call last):
>   File "/<>/setup.py", line 47, in 
> version = versioneer.get_version(),
>   
>   File "/<>/versioneer.py", line 1480, in get_version
> return get_versions()["version"]
>^^
>   File "/<>/versioneer.py", line 1412, in get_versions
> cfg = get_config_from_root(root)
>   ^^
>   File "/<>/versioneer.py", line 342, in get_config_from_root
> parser = configparser.SafeConfigParser()
>  ^
> AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. 
> Did you mean: 'RawConfigParser'?
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: 
> python3.12 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11" 
> returned exit code 13
> make: *** [debian/rules:7: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/python-pyepics_3.5.1+ds-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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-pyepics
Source-Version: 3.5.2+ds-1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated python-pyepics 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, 19 Apr 2024 18:53:28 +
Source: python-pyepics
Architecture: source
Version: 3.5.2+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PaN Maintainers 

Changed-By: Bastian Germann 
Closes: 1058200
Changes:
 python-pyepics (3.5.2+ds-1) unstable; urgency=medium
 .
   * Team upload
   * d/watch: Import from GitHub
   * New upstream version 3.5.2+ds (Closes: #1058200)
   * Add build deps for new version
   * Rebase patches
   * d/copyright: Drop removed licenses
 .
   [ Sébastien Delafond ]
   * d/control: remove myself from uploaders
Checksums-Sha1:
 d3f9c98866724b11d7ab66330f9d6fb62fd0bb37 2302 python-pyepics_3.5.2+ds-1.dsc
 c71ccc6972635908f6f76f32c8163804fc74a065 858592 
python-pyepics_3.5.2+ds.orig.tar.xz
 934511929cfba557d0983ef2d7ec08b1887d5f2b 6188 
python-pyepics_3.5.2+ds-1.debian.tar.xz
 

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

[Salvatore Bonaccorso]

FWIW, I will try to work on the new available upstream version in the
next days and see if the two RC bugs on lnav can be addressed along.

it does not make sense to investigate the testsuite failure right now
without rebasing to the new version.

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #1067616 [src:clanlib] FTBFS: error: ‘struct input_event’ has no member 
named ‘time’
Added tag(s) patch.

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

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

[Andreas Beckmann]

Followup-For: Bug #1067616
Control: tag -1 patch

I'm attaching a patch fixing input_event.time usage.

Andreas
>From 8435c93a70ae65035002d0039a9a511a5974df90 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Fri, 19 Apr 2024 17:12:42 +0200
Subject: [PATCH 1/2] fix --link-doc package

---
 debian/changelog | 6 ++
 debian/rules | 2 +-
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index a124d88..05ea064 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+clanlib (1.0~svn3827-12) UNRELEASED; urgency=medium
+
+  * Fix --link-doc package.
+
+ -- Andreas Beckmann   Fri, 19 Apr 2024 17:10:30 +0200
+
 clanlib (1.0~svn3827-11.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --git a/debian/rules b/debian/rules
index ccb1097..0bd042f 100755
--- a/debian/rules
+++ b/debian/rules
@@ -46,7 +46,7 @@ override_dh_auto_clean:
rm -f Documentation/Tutorial/Kavanek/*.html
 
 override_dh_installdocs-arch:
-   dh_installdocs --link-doc=libclanapp-1.0v5
+   dh_installdocs --link-doc=libclanapp-1.0t64
 
 override_dh_installexamples-indep:
dh_installexamples -pclanlib-doc Examples/*
-- 
2.20.1

>From 822447ffd6362ea37f48441f630275a98c0b2d34 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Fri, 19 Apr 2024 18:22:23 +0200
Subject: [PATCH 2/2] work around struct input_event.time kernel api change

---
 debian/changelog  |  1 +
 debian/patches/input_event.time.patch | 30 +++
 debian/patches/series |  1 +
 3 files changed, 32 insertions(+)
 create mode 100644 debian/patches/input_event.time.patch

diff --git a/debian/changelog b/debian/changelog
index 05ea064..4c916e2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 clanlib (1.0~svn3827-12) UNRELEASED; urgency=medium
 
   * Fix --link-doc package.
+  * Work around struct input_event.time kernel api change.  (Closes: #1067616)
 
  -- Andreas Beckmann   Fri, 19 Apr 2024 17:10:30 +0200
 
diff --git a/debian/patches/input_event.time.patch 
b/debian/patches/input_event.time.patch
new file mode 100644
index 000..e52873d
--- /dev/null
+++ b/debian/patches/input_event.time.patch
@@ -0,0 +1,30 @@
+Author: Andreas Beckmann 
+Description: work around struct input_event.time kernel api change
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=152194fe9c3f
+
+--- a/Sources/GL/GLX/input_device_linuxevent.cpp
 b/Sources/GL/GLX/input_device_linuxevent.cpp
+@@ -266,12 +266,12 @@ CL_InputDevice_LinuxEvent::keep_alive()
+   if (ev[i].type == EV_SYN) 
+   {
+   printf("Event: time %ld.%06ld, 
-- %s \n",
+-   
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].code ? "Config Sync" : "Report 
Sync" );
++   
ev[i].input_event_sec, ev[i].input_event_usec, ev[i].code ? "Config Sync" : 
"Report Sync" );
+   }
+   else if (ev[i].type == EV_MSC && 
(ev[i].code == MSC_RAW || ev[i].code == MSC_SCAN)) 
+   {
+   printf("Event: time %ld.%06ld, 
type %d (%s), code %d (%s), value %02x\n",
+-   
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type,
++   
ev[i].input_event_sec, ev[i].input_event_usec, ev[i].type,
+
events[ev[i].type] ? events[ev[i].type] : "?",
+ev[i].code,
+
names[ev[i].type] ? (names[ev[i].type][ev[i].code] ? 
names[ev[i].type][ev[i].code] : "?") : "?",
+@@ -280,7 +280,7 @@ CL_InputDevice_LinuxEvent::keep_alive()
+   else 
+   {
+   printf("Event: time %ld.%06ld, 
type %d (%s), code %d (%s), value %d\n",
+-   
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type,
++   
ev[i].input_event_sec, ev[i].input_event_usec, ev[i].type,
+
events[ev[i].type] ? events[ev[i].type] : "?",
+ev[i].code,
+
names[ev[i].type] ? (names[ev[i].type][ev[i].code] ? 
names[ev[i].type][ev[i].code] : "?") : "?",
diff --git a/debian/patches/series b/debian/patches/series

Bug#1069321: FTBFS: [Makefile:163: check] Error 1

[Andrey Rakhmatullin]

Source: hypre
Version: 2.28.0-8
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=hypre=armhf=2.28.0-8%2Bb2=1713420980=0

I couldn't find the actual failing command.


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

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

Bug#1069320: FTBFS on mips64el: cannot find -lasan: No such file or directory

[Andrey Rakhmatullin]

Source: datatype99
Version: 1.6.4-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=datatype99=mips64el=1.6.4-1=1713121986=0

make[4]: Entering directory '/<>/testsbuild'
[ 10%] Building C object CMakeFiles/tests.dir/tests.c.o
[ 20%] Linking C executable tests
/usr/bin/ld: cannot find libasan_preinit.o: No such file or directory
/usr/bin/ld: cannot find -lasan: No such file or directory
collect2: error: ld returned 1 exit status


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

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

Bug#1069319: FTBFS on armel: undefined reference to `__atomic_store_8'

[Andrey Rakhmatullin]

Source: datatype99
Version: 1.6.4-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=datatype99=armel=1.6.4-1=1713120793=0

make[4]: Entering directory '/<>/testsbuild'
[ 10%] Building C object CMakeFiles/tests.dir/tests.c.o
[ 20%] Linking C executable tests
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/13/libasan.so: undefined reference
to `__atomic_store_8'
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/13/libasan.so: undefined reference
to `__atomic_load_8'
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/13/libasan.so: undefined reference
to `__atomic_compare_exchange_8'
collect2: error: ld returned 1 exit status


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

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

Processed: tagging 1067697

[Debian Bug Tracking System]

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

> tags 1067697 + ftbfs
Bug #1067697 [src:xca] Update Build-Depends for the time64 library renames
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1069318: FTBFS: error: unknown type name ‘StdVideoH264LevelIdc’

[Andrey Rakhmatullin]

Source: wine-development
Version: 8.21~repack-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=wine-
development=amd64=8.21%7Erepack-1%2Bb5=1712016271=0


In file included from dlls/d3d12/d3d12_main.c:27:
include/wine/vulkan.h:11804:5: error: unknown type name ‘StdVideoH264LevelIdc’
11804 | StdVideoH264LevelIdc maxLevelIdc;
  | ^~~~
include/wine/vulkan.h:11822:11: error: unknown type name
‘StdVideoEncodeH264ReferenceInfo’
11822 | const StdVideoEncodeH264ReferenceInfo *pStdReferenceInfo;
  |   ^~~
include/wine/vulkan.h:11847:11: error: unknown type name
‘StdVideoEncodeH264SliceHeader’
11847 | const StdVideoEncodeH264SliceHeader *pStdSliceHeader;
  |   ^
include/wine/vulkan.h:11856:11: error: unknown type name
‘StdVideoEncodeH264PictureInfo’
11856 | const StdVideoEncodeH264PictureInfo *pStdPictureInfo;
  |   ^
include/wine/vulkan.h:11864:5: error: unknown type name
‘StdVideoH264ProfileIdc’
11864 | StdVideoH264ProfileIdc stdProfileIdc;
  | ^~
include/wine/vulkan.h:11917:5: error: unknown type name ‘StdVideoH264LevelIdc’
11917 | StdVideoH264LevelIdc maxLevelIdc;
  | ^~~~
include/wine/vulkan.h:11925:11: error: unknown type name
‘StdVideoH264SequenceParameterSet’
11925 | const StdVideoH264SequenceParameterSet *pStdSPSs;
  |   ^~~~
include/wine/vulkan.h:11927:11: error: unknown type name
‘StdVideoH264PictureParameterSet’
11927 | const StdVideoH264PictureParameterSet *pStdPPSs;
  |   ^~~
include/wine/vulkan.h:11962:5: error: unknown type name ‘StdVideoH265LevelIdc’
11962 | StdVideoH265LevelIdc maxLevelIdc;
  | ^~~~
include/wine/vulkan.h:11983:11: error: unknown type name
‘StdVideoEncodeH265ReferenceInfo’
11983 | const StdVideoEncodeH265ReferenceInfo *pStdReferenceInfo;
  |   ^~~
include/wine/vulkan.h:12008:11: error: unknown type name
‘StdVideoEncodeH265SliceSegmentHeader’
12008 | const StdVideoEncodeH265SliceSegmentHeader *pStdSliceSegmentHeader;
  |   ^~~~
include/wine/vulkan.h:12017:11: error: unknown type name
‘StdVideoEncodeH265PictureInfo’
12017 | const StdVideoEncodeH265PictureInfo *pStdPictureInfo;
  |   ^
include/wine/vulkan.h:12024:5: error: unknown type name
‘StdVideoH265ProfileIdc’
12024 | StdVideoH265ProfileIdc stdProfileIdc;
  | ^~
include/wine/vulkan.h:12076:5: error: unknown type name ‘StdVideoH265LevelIdc’
12076 | StdVideoH265LevelIdc maxLevelIdc;
  | ^~~~
include/wine/vulkan.h:12084:11: error: unknown type name
‘StdVideoH265VideoParameterSet’
12084 | const StdVideoH265VideoParameterSet *pStdVPSs;
  |   ^
include/wine/vulkan.h:12086:11: error: unknown type name
‘StdVideoH265SequenceParameterSet’
12086 | const StdVideoH265SequenceParameterSet *pStdSPSs;
  |   ^~~~
include/wine/vulkan.h:12088:11: error: unknown type name
‘StdVideoH265PictureParameterSet’
12088 | const StdVideoH265PictureParameterSet *pStdPPSs;
  |   ^~~


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

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

Processed: Re: Bug#1069310: FTBFS: tests failed

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 golang-github-hanwen-go-fuse-dev
Bug #1069310 [src:gocryptfs] FTBFS: tests failed
Bug reassigned from package 'src:gocryptfs' to 
'golang-github-hanwen-go-fuse-dev'.
No longer marked as found in versions gocryptfs/2.4.0-1.
Ignoring request to alter fixed versions of bug #1069310 to the same values 
previously set
> affects -1 src:gocryptfs
Bug #1069310 [golang-github-hanwen-go-fuse-dev] FTBFS: tests failed
Added indication that 1069310 affects src:gocryptfs

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

Bug#1069310: FTBFS: tests failed

[Shengjing Zhu]

Control: reassign -1 golang-github-hanwen-go-fuse-dev
Control: affects -1 src:gocryptfs

On Sat, Apr 20, 2024 at 2:54 AM Andrey Rakhmatullin  wrote:
>
> Source: gocryptfs
> Version: 2.4.0-1
> Severity: serious
> Tags: ftbfs
>
> https://buildd.debian.org/status/fetch.php?pkg=gocryptfs=mips64el=2.4.0-1%2Bb6=1713405841=0
>
> panic: DIRECT (8000) overlaps with LARGEFILE (8000)
>
> goroutine 1 [running]:
> github.com/hanwen/go-fuse/fuse.(*flagNames).set(0xc000126708, 0x8000,
> {0x1201d640e, 0x6})
> 
> /<>/_build/src/github.com/hanwen/go-fuse/fuse/print.go:126
> +0x234
> github.com/hanwen/go-fuse/fuse.init.1()
> /<>/_build/src/github.com/hanwen/go-
> fuse/fuse/print_linux.go:13 +0x68
> FAILgithub.com/rfjakob/gocryptfs/internal/syscallcompat 0.007s
>

This is similar to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061659 and
https://github.com/hanwen/go-fuse/issues/502 which is only fixed on
i386.

-- 
Shengjing Zhu

Bug#1069317: FTBFS: tests failed

[Andrey Rakhmatullin]

Source: sonic-visualiser
Version: 4.5.2-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=sonic-
visualiser=armel=4.5.2-2%2Bb3=1713251413=0

FAIL!  : TestVampRealTime::fromTimeval() Compared values are not the same
   Loc: [test-svcore-base.p/../../svcore/base/test/TestVampRealTime.h(144)]



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

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

Processed: tagging 1069017

[Debian Bug Tracking System]

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

> tags 1069017 + ftbfs
Bug #1069017 [rtags] rtags: FTBFS due to time64_t changes
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

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

[Andrey Rakhmatullin]

Source: openjdk-20
Version: 20.0.2+9-1
Severity: serious
Tags: ftbfs

The package explicitly Build-Depends: libgtk2.0-0 | libgtk-3-0,
these need to be changed to lib*t64 if these deps are needed at all.


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

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

Bug#1069313: FTBFS: implicit declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’?

[Andrey Rakhmatullin]

Source: jskeus
Version: 1.2.4+dfsg-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=jskeus=armhf=1.2.4%2Bdfsg-3%2Bb2=1710976387=0

gcc -g -c -o /<>/irteus/LinuxARM/obj/irtmath.o -DARM -DLinux
-Wimplicit -falign-functions=4 -DGCC3  -DGCC -fsigned-char  -DTHREADED
-DPTHREAD -fpic  -I/usr/share/euslisp/include -O2 -g -O2 -Werror=implicit-
function-declaration -ffile-prefix-map=/<>=. -fstack-protector-
strong -fstack-clash-protection -Wformat -Werror=format-security
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time
-D_FORTIFY_SOURCE=2 -DLinux -D_REENTRANT -DGCC -I/usr/share/euslisp/include
-DTHREADED -DPTHREAD -DSVNVERSION=\"\" -fPIC -falign-functions=8 ./irtmath.c;
ld -shared -build-id -o /<>/irteus/LinuxARM/obj/irtmath.so
/<>/irteus/LinuxARM/obj/irtmath.ojpegmemcd.c: In function
‘JPEG_compress’:
jpegmemcd.c:29:3: error: implicit declaration of function ‘jpeg_memio_dest’;
did you mean ‘jpeg_mem_dest’? [-Werror=implicit-function-declaration]
   29 |   jpeg_memio_dest(, jpeg_image_buffer, _count);
  |   ^~~
  |   jpeg_mem_dest
jpegmemcd.c: In function ‘JPEG_header’:
jpegmemcd.c:92:3: error: implicit declaration of function ‘jpeg_memio_src’; did
you mean ‘jpeg_mem_src’? [-Werror=implicit-function-declaration]
   92 |   jpeg_memio_src(, jpeg_image, jpeg_size);
  |   ^~
  |   jpeg_mem_src


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

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

Bug#1069312: FTBFS: debian/hlibrary.setup build --builddir=dist-ghc returned exit code 1

[Andrey Rakhmatullin]

Source: haskell-gi-gtk
Version: 3.0.41-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=haskell-gi-
gtk=armel=3.0.41-1%2Bb6=1713045220=0

[707 of 708] Compiling GI.Gtk.Structs   ( GI/Gtk/Structs.hs, dist-
ghc/build/GI/Gtk/Structs.o, dist-ghc/build/GI/Gtk/Structs.dyn_o )
-e: error: debian/hlibrary.setup build --builddir=dist-ghc returned exit code 1
 at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 875.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup build
--builddir=dist-ghc returned exit"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 614
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup build
--builddir=dist-ghc") called at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 477
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "build", "--
builddir=dist-ghc") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 656
Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25


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

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

Bug#1067296: marked as done (gap-hapcryst: FTBFS: Can't load '/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so' for module Polymake::Ext: libflint.so.18: cannot op

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 18:51:43 +
with message-id 
and subject line Bug#1067296: fixed in gap-hapcryst 0.1.15-4
has caused the Debian Bug report #1067296,
regarding gap-hapcryst: FTBFS: Can't load 
'/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so'
 for module Polymake::Ext: libflint.so.18: cannot open shared object file: No 
such file or directory at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm 
line 201.
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p debian/gaproot/pkg
> ln -s ../../.. debian/gaproot/pkg/HAPcryst
> # This is a HACK. GAPDoc2HTML identifies the MainRootPath by checking for 
> # init.g. Since AutoDoc and GAPDoc are unable to handle multiple books
> # the HAPprog book is considered an external link. Therefore it is necessary
> # to replace debian/gaproot with double dots. We fake it as a MainRootPath
> # to achieve this. 
> ln -s /usr/share/gap/lib debian/gaproot/lib
> # This prevents an absolute path to polymaking as a result of the above.
> ln -s /usr/share/gap/pkg/polymaking debian/gaproot/pkg/polymaking
> gap -q -l "/<>/debian/gaproot;/usr/share/gap" < tst/testall.g | 
> tee debian/gap.tst
> #I  HAP warning: Set NEATO_PATH manually if needed.
> #I  HAP warning: Set DOT_PATH manually if needed.
> #I  HAP warning: Set DISPLAY_PATH manually if needed.
> #I  HAP warning: Set BROWSER_PATH manually if needed.
> #I  HAP warning: Set ASY_PATH manually if needed.
> true
> Architecture: x86_64-pc-linux-gnu-default64-kv8
> 
> testing: /<>/debian/gaproot/pkg/HAP\
> cryst/tst/HAPcryst.tst
> Can't load 
> '/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so'
>  for module Polymake::Ext: libflint.so.18: cannot open shared object file: No 
> such file or directory at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm 
> line 201.
>  at /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> BEGIN failed--compilation aborted at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at /usr/share/polymake/perllib/Polymake.pm line 
> 29.
> BEGIN failed--compilation aborted at /usr/share/polymake/perllib/Polymake.pm 
> line 29.
> Compilation failed in require at /usr/bin/polymake line 156.
> BEGIN failed--compilation aborted at /usr/bin/polymake line 156.
> Can't load 
> '/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so'
>  for module Polymake::Ext: libflint.so.18: cannot open shared object file: No 
> such file or directory at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm 
> line 201.
>  at /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> BEGIN failed--compilation aborted at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at /usr/share/polymake/perllib/Polymake.pm line 
> 29.
> BEGIN failed--compilation aborted at /usr/share/polymake/perllib/Polymake.pm 
> line 29.
> Compilation failed in require at /usr/bin/polymake line 156.
> BEGIN failed--compilation aborted at /usr/bin/polymake line 156.
> Can't load 
> '/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so'
>  for module Polymake::Ext: libflint.so.18: cannot open shared object file: No 
> such file or directory at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm 
> line 201.
>  at /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> BEGIN failed--compilation aborted at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at /usr/share/polymake/perllib/Polymake.pm line 
> 29.
> BEGIN failed--compilation aborted at /usr/share/polymake/perllib/Polymake.pm 
> line 29.
> Compilation failed in require at /usr/bin/polymake line 156.
> BEGIN failed--compilation aborted at /usr/bin/polymake line 156.

Bug#1069310: FTBFS: tests failed

[Andrey Rakhmatullin]

Source: gocryptfs
Version: 2.4.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=gocryptfs=mips64el=2.4.0-1%2Bb6=1713405841=0

panic: DIRECT (8000) overlaps with LARGEFILE (8000)

goroutine 1 [running]:
github.com/hanwen/go-fuse/fuse.(*flagNames).set(0xc000126708, 0x8000,
{0x1201d640e, 0x6})
/<>/_build/src/github.com/hanwen/go-fuse/fuse/print.go:126
+0x234
github.com/hanwen/go-fuse/fuse.init.1()
/<>/_build/src/github.com/hanwen/go-
fuse/fuse/print_linux.go:13 +0x68
FAILgithub.com/rfjakob/gocryptfs/internal/syscallcompat 0.007s


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

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

Bug#1069309: xfractint FTBFS: error: implicit declaration of function

[Adrian Bunk]

Source: xfractint
Version: 20.4.10-4
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Petter Reinholdtsen 

https://buildd.debian.org/status/logs.php?pkg=xfractint=20.4.10-4

...
/usr/bin/gcc -I../headers -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-mbranch-protection=standard -I./headers -DXFRACT  -DNOBSTRING   -g 
-DBIG_ANSI_C -DLINUX -fno-builtin -fcommon -O2 -Wdate-time -D_FORTIFY_SOURCE=2  
-c -o 3d.o 3d.c
3d.c: In function ‘longvmultpersp’:
3d.c:290:20: error: implicit declaration of function ‘multiply’ 
[-Werror=implicit-function-declaration]
  290 |  tmp[j] += multiply(s[i],m[i][j],bitshift);
  |^~~~
3d.c:318:20: error: implicit declaration of function ‘divide’ 
[-Werror=implicit-function-declaration]
  318 |   tmpview[0] = divide(lview[0],denom,bitshift);
  |^~
cc1: some warnings being treated as errors
make[3]: *** [: 3d.o] Error 1

Bug#1066938: Fwd: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined

[Alberto Bertogli]

On Mon, Mar 25, 2024 at 07:12:24PM +, Chris Lamb wrote:

Alberto Bertogli wrote:


If you know of a functional official image that I can use to try to
reproduce the problem, or recently-tested steps I can follow to get
a working qemu install, please let me know.


Alas, I can't actually be helpful here. There are no official images
as far as I know… and somewhat annoyingly I (ie. a Debian Developer)
actually have access to some machines set aside for this purpose. I
call this "annoying" because I naturally can't then give you direct
SSH access transitively — but I can proxy ideas, of course.


I totally understand the access part, that's very reasonable on Debian's 
part.


But unfortunately, if I can't even run a local VM to try to reproduce 
the problem, it's too limiting for me. Especially considering the kind 
of issues libfiu often runs into, which tend to be a bit on the esoteric 
side :)




Hm, googling the actual error message a little, I think this might be
a bigger issue... or perhaps more accurately, at least one that has
potentially been also solved elsewhere:

 * Same think in lightdm: 

 * Some kind of "_FILE_OFFSET_BITS"-related patch for v4l-utils
   


Thank you for looking at this!

I think they could be similar; in particular the second one.

Maybe there's something like `#define pread pread64` in the 
architecture's headers that is triggering these errors?




Does this spark anything worth trying? :-)


Maybe seeing the preprocessor output and the actual (temporary) file 
getting the complaints could be useful in figuring out what's going on.


That said, even if we find what the problem is, we may keep finding 
other issues in the future. If I'm not able to have a VM for this
platform where I can try to reproduce problems, I'm not sure it's viable 
to support the package on it :(


Thanks!
Alberto

Bug#1069308: FTBFS: tests failed

[Andrey Rakhmatullin]

Source: gnome-subtitles
Version: 1.8-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=gnome-
subtitles=amd64=1.8-1%2Bb3=1712013676=0

@@ -747,7 +747,7 @@

 "GstDiscovererClass.starting": "144"
 "GstDiscovererClass.discovered": "152"
 "GstDiscovererClass.source_setup": "160"
-"GstDiscovererClass._reserved": "176"
+"GstDiscovererClass._reserved": "168"
 "sizeof(GstDiscoverer)": "64"
 "GstDiscoverer.priv": "24"
 "GstDiscoverer._reserved": "32"


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

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

Bug#1069307: FTBFS: configure: error: must specify --with-locking-method option

[Andrey Rakhmatullin]

Source: courier
Version: 1.0.16-3.2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=courier=armel=1.0.16-3.2%2Bb4=1712019536=0

checking for locking method... configure: error: must specify --with-locking-
method option
configure: error: ./configure failed for libs/liblock


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

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

Bug#1062558: marked as done (libosmo-netif: NMU diff for 64-bit time_t transition)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 17:38:05 + (UTC)
with message-id 

and subject line no longer packages on 32bit architectures
has caused the Debian Bug report #1062558,
regarding libosmo-netif: NMU diff for 64-bit time_t transition
to be marked as done.

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

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


-- 
1062558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libosmo-netif
Version: 1.2.0-2
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

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

Dear maintainer,

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

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

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

Please find the patch for this NMU attached.

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



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libosmo-netif-1.2.0/debian/changelog 
libosmo-netif-1.2.0/debian/changelog
--- libosmo-netif-1.2.0/debian/changelog2022-10-13 17:02:35.0 
+
+++ libosmo-netif-1.2.0/debian/changelog2024-02-01 22:59:33.0 
+
@@ -1,3 +1,10 @@
+libosmo-netif (1.2.0-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Thu, 01 Feb 2024 22:59:33 +
+
 libosmo-netif (1.2.0-2) unstable; urgency=medium
 
   * upload to unstable
diff -Nru libosmo-netif-1.2.0/debian/control libosmo-netif-1.2.0/debian/control
--- libosmo-netif-1.2.0/debian/control  2022-10-13 17:02:35.0 +
+++ libosmo-netif-1.2.0/debian/control  2024-02-01 22:59:33.0 +
@@ -15,7 +15,10 @@
 Vcs-Git: https://salsa.debian.org/debian-mobcom-team/libosmo-netif.git
 Homepage: http://git.osmocom.org/libosmo-netif/
 
-Package: libosmonetif8
+Package: libosmonetif8t64
+Provides: ${t64:Provides}
+Replaces: libosmonetif8
+Breaks: libosmonetif8 (<< ${source:Version})
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Multi-Arch: same
@@ -30,7 +33,7 @@
 Depends: ${shlibs:Depends},
  ${misc:Depends},
  libosmocore-dev,
- libosmonetif8 (= ${binary:Version})
+ libosmonetif8t64 (= ${binary:Version})
 Multi-Arch: same
 Description: Development headers for Osmocom network interface
  The libosmo-netif library is one of the libraries needed by the
diff -Nru libosmo-netif-1.2.0/debian/libosmonetif8.install 
libosmo-netif-1.2.0/debian/libosmonetif8.install
--- libosmo-netif-1.2.0/debian/libosmonetif8.install2022-10-13 
17:02:35.0 +
+++ libosmo-netif-1.2.0/debian/libosmonetif8.install1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libosmonetif*.so.*
diff -Nru libosmo-netif-1.2.0/debian/libosmonetif8.symbols 
libosmo-netif-1.2.0/debian/libosmonetif8.symbols
--- libosmo-netif-1.2.0/debian/libosmonetif8.symbols2022-10-13 

Bug#1066005: marked as done (epic4: FTBFS on arm{el,hf}: gailib.c:95:17: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 18:02:56 +
with message-id 
and subject line Bug#1066005: fixed in epic4 1:2.10.10-1.1
has caused the Debian Bug report #1066005,
regarding epic4: FTBFS on arm{el,hf}: gailib.c:95:17: error: implicit 
declaration of function ‘strlcpy’; did you mean ‘strncpy’? 
[-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.)


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

https://buildd.debian.org/status/fetch.php?pkg=epic4=armhf=1%3A2.10.10-1%2Bb5=1709806588=0

gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  
-I./../include -I../include -c gailib.c
gailib.c: In function ‘get_name’:
gailib.c:95:17: error: implicit declaration of function ‘strlcpy’; did you mean 
‘strncpy’? [-Werror=implicit-function-declaration]
   95 | strlcpy((ai)->ai_canonname, (str), strlen(str) + 1);\
  | ^~~
gailib.c:426:17: note: in expansion of macro ‘GET_CANONNAME’
  426 | GET_CANONNAME(cur, hp->h_name);
  | ^
cc1: some warnings being treated as errors
make[2]: *** [Makefile:31: gailib.o] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: epic4
Source-Version: 1:2.10.10-1.1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
epic4, 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 epic4 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, 19 Apr 2024 18:46:14 +0200
Source: epic4
Architecture: source
Version: 1:2.10.10-1.1
Distribution: unstable
Urgency: medium
Maintainer: Kurt Roeckx 
Changed-By: Bastian Germann 
Closes: 1066005
Changes:
 epic4 (1:2.10.10-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix implicit function declarations. (Closes: #1066005)
Checksums-Sha1:
 633d799c5558322f158bd31b1bbd6640fc924481 1581 epic4_2.10.10-1.1.dsc
 3cd9e2d20facc3efc1e7a4e27e450708c3bb1f3b 16916 epic4_2.10.10-1.1.debian.tar.xz
 77fd295b6c9794683e830330640d73039aaa2a97 5553 
epic4_2.10.10-1.1_source.buildinfo
Checksums-Sha256:
 3425a3bf75cd3466281d49fb0d9a001028e9c4e6cf82e253f8f36a09cc7018f0 1581 
epic4_2.10.10-1.1.dsc
 391b0e6afe386f05f6b0f05063fff2ef71fab5f45d565f559a4ccd806df83e28 16916 
epic4_2.10.10-1.1.debian.tar.xz
 9e631a755a7e7eea2c05615934a7c5e9f123285e0453966ebbb8ebaef4cda8e3 5553 
epic4_2.10.10-1.1_source.buildinfo
Files:
 5ecef19a6b0f9f5970479d5557a42dd3 1581 net optional epic4_2.10.10-1.1.dsc
 6f05c79acf0ab6e8a712cbdae46f613f 16916 net optional 
epic4_2.10.10-1.1.debian.tar.xz
 6c26c9442905c2456480d17bea4e18ac 5553 net optional 
epic4_2.10.10-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYioIIQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFDKgC/9KxUQyDzbIjIJxTMJHug+6qeFpYdK3+/fF
7W5WW4Q2/4d/YLa8zRkGaOHeIxee6EkEqJeAQ3X77XYrFCX8B170kYegGJlHMTRM
9DEKE7r/IjvnktWOnfJyfTf5KX4tXtIx7WVxIvdEC5ne87KT02oM8lzN2Xt3068E
HyKq8bcDgVEmOeN4PqqBGlBKN8JQ6qm6pvi8MQMFOxDLXENIltNESKiD9MlPlUF/
sYlhtvP6lKVVW8waDHlief87V/grCO2HUhjRb+quztLCmc0FZ938r5q9WT2rU3hF
+2ApnndTWepkKlZoaJoG09ltaaeP6oKjqR3ZzEeqPqFMAq3yoStlTGFjxobErgNT
MkkZJfpYBMy6Qh/8huZHf9QObqmrH80ULvjPW2W0ptYQHg+ltw16wlXu5+59Wmxj
SbdiXqDmFk7duyt/0ggLdHxosMee3U+3DBHbyjPLm4Z9vhoCGPHyBICSI6OTqaHJ
CQmj7VymBxTquPIjc+Fnk/JUHwDX9XQ=
=A66a
-END PGP SIGNATURE-



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

Bug#1066005: NMU: error: implicit declaration of function ‘strlcpy’

[Bastian Germann]

I am uploading a NMU to fix this.
Please find the debdiff attached.

epic4_2.10.10-1.1.debdiff
Description: Binary data

Processed: Report #1059673 upstream

[Debian Bug Tracking System]

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

> forwarded 1059673 https://github.com/ThinkChaos/Trololio/issues/2
Bug #1059673 [src:trololio] trololio: autopkgtest failure with Python 3.12
Set Bug forwarded-to-address to 
'https://github.com/ThinkChaos/Trololio/issues/2'.
>
End of message, stopping processing here.

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

Bug#1068696: marked as done (haskell-hourglass FTBFS on armel and armhf)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 16:19:33 +
with message-id 
and subject line Bug#1068696: fixed in haskell-hourglass 0.2.12-6
has caused the Debian Bug report #1068696,
regarding haskell-hourglass FTBFS on armel and armhf
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.)


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

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

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


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





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





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

4 out of 21 tests failed (0.03s)



I strongly suspect this is related to the time64 transition.
--- End Message ---
--- Begin Message ---
Source: haskell-hourglass
Source-Version: 0.2.12-6
Done: Ilias Tsitsimpis 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 18:45:44 +0300
Source: haskell-hourglass
Architecture: source
Version: 0.2.12-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Closes: 1001686 1068696
Changes:
 haskell-hourglass (0.2.12-6) unstable; urgency=medium
 .
   * Fix issues with 64-bit time_t 

Bug#1063418: marked as done (mdp ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 16:04:47 +
with message-id 
and subject line Bug#1063418: fixed in mdp 3.6-7
has caused the Debian Bug report #1063418,
regarding mdp ftbfs in unstable
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.)


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

Package: src:mdp
Version: 3.6-6
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
tests fail with both Python 3.11 and 3.12.

Also with 3.12:
mdp/test/test_reload.py:4
  /<>/mdp/test/test_reload.py:4: DeprecationWarning: the 
imp module is deprecated in favour of importlib and slated for removal 
in Python 3.12; see the module's documentation for alternative uses

from imp import reload


[...]
=== short test summary info 

FAILED mdp/test/test_hinet_generic.py::test_dtype_consistency[FlowNode] 
- Typ...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[SFA2Node] 
- Typ...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[FDANode] - 
Type...
FAILED 
mdp/test/test_nodes_generic.py::test_dtype_consistency[GaussianClassifier]
FAILED 
mdp/test/test_nodes_generic.py::test_dtype_consistency[LinearRegressionNode]
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[JADENode] 
- Typ...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[XSFANode] 
- Typ...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[iGSFANode] 
- Ty...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[LLENode] - 
Type...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[HLLENode] 
- Typ...
FAILED 
mdp/test/test_nodes_generic.py::test_dtype_consistency[CuBICANode] - T...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[FANode] - 
TypeE...
FAILED 
mdp/test/test_nodes_generic.py::test_dtype_consistency[FastICANode] - ...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[GSFANode] 
- Typ...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[ISFANode] 
- Typ...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[PCANode] - 
Type...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[SFANode] - 
Type...
FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[TDSEPNode] 
- Ty...
FAILED 
mdp/test/test_nodes_generic.py::test_dtype_consistency[VartimeSFANode]

FAILED mdp/test/test_nodes_generic.py::test_dtype_consistency[WhiteningNode]
== 20 failed, 823 passed, 16 skipped, 3 warnings in 158.17s 
(0:02:38) ==
E: pybuild pybuild:391: test: plugin custom failed with: exit code=1: 
python3.11 -m pytest --seed=725021957 mdp && python3.11 -m pytest 
--seed=725021957 bimdp
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 
"3.12 3.11" returned exit code 13
--- End Message ---
--- Begin Message ---
Source: mdp
Source-Version: 3.6-7
Done: Bastian Germann 

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

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

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated mdp 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, 19 Apr 2024 17:48:15 +0200
Source: mdp
Architecture: source
Version: 3.6-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Bastian Germann 
Closes: 1063418
Changes:
 mdp (3.6-7) unstable; urgency=medium
 .
   * Team upload
   * Patch: Migrate from inspect.getfullargspec to inspect.signature
   * Patch: compatibility with 32bit arches (Closes: #1063418)
   * Patch: Deprecation of numpy.typeDict
Checksums-Sha1:
 5685b8aeb9ec5beb7e4406e2430c4f0415638a89 2025 mdp_3.6-7.dsc
 faab8001ccf06bda2ca75c07c9d10dc976975a66 9956 mdp_3.6-7.debian.tar.xz
 8656ed4129e5f522385d2b92f48847354d0f49e1 6738 mdp_3.6-7_source.buildinfo
Checksums-Sha256:
 7e0d8c3aea8ecdace49a5461cb6d3b029e625dddcd64292f45aae86f0b6c2da5 2025 
mdp_3.6-7.dsc
 

Bug#1023035: marked as done (gauche: Includes non-free software)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 17:26:11 +0200
with message-id <87o7a5pe5o@karme.de>
and subject line upstream resolved this in 0.9.13
has caused the Debian Bug report #1023035,
regarding gauche: Includes non-free software
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.)


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

Source: gauche
Severity: serious
Version: 0.9.10-3

debian/ext/srfi/srfi-19.scm has a license that reads "However, this document itself 
may not be modified in any way"
and is documented in d/copyright for lib/srfi-11.scm, which does not have that license (anymore). This clause makes the 
license non-free. Please remove files that are non-free or move the package to the non-free archive section.
--- End Message ---
--- Begin Message ---
Package: gauche
Version: 0.9.13-1--- End Message ---

Processed: Bug#1064293 marked as pending in less

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1064293 [src:less] less: CVE-2022-48624
Ignoring request to alter tags of bug #1064293 to the same tags previously set

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

Processed: less: diff for NMU version 590-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1064293 + patch
Bug #1064293 [src:less] less: CVE-2022-48624
Added tag(s) patch.
> tags 1064293 + pending
Bug #1064293 [src:less] less: CVE-2022-48624
Added tag(s) pending.
> tags 1068938 + patch
Bug #1068938 [src:less] less: CVE-2024-32487: with LESSOPEN mishandles \n in 
paths
Added tag(s) patch.
> tags 1068938 + pending
Bug #1068938 [src:less] less: CVE-2024-32487: with LESSOPEN mishandles \n in 
paths
Added tag(s) pending.

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

Processed: Bug#1068938 marked as pending in less

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068938 [src:less] less: CVE-2024-32487: with LESSOPEN mishandles \n in 
paths
Ignoring request to alter tags of bug #1068938 to the same tags previously set

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

Processed: less: diff for NMU version 590-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1064293 + patch
Bug #1064293 [src:less] less: CVE-2022-48624
Ignoring request to alter tags of bug #1064293 to the same tags previously set
> tags 1064293 + pending
Bug #1064293 [src:less] less: CVE-2022-48624
Ignoring request to alter tags of bug #1064293 to the same tags previously set
> tags 1068938 + patch
Bug #1068938 [src:less] less: CVE-2024-32487: with LESSOPEN mishandles \n in 
paths
Ignoring request to alter tags of bug #1068938 to the same tags previously set
> tags 1068938 + pending
Bug #1068938 [src:less] less: CVE-2024-32487: with LESSOPEN mishandles \n in 
paths
Ignoring request to alter tags of bug #1068938 to the same tags previously set

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

Bug#1068938: marked as pending in less

[Salvatore Bonaccorso]

Control: tag -1 pending

Hello,

Bug #1068938 in less 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/less/-/commit/e353d9a5cf7f29570e0ae4e0431b5254feaebbda


Fix bug when viewing a file whose name contains a newline (CVE-2024-32487)

Closes: #1068938


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068938

Bug#1064293: marked as pending in less

[Salvatore Bonaccorso]

Control: tag -1 pending

Hello,

Bug #1064293 in less 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/less/-/commit/e61c8283fbf69a8262d3cec653090fab6e83042d


Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624)

Closes: #1064293


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064293

Bug#1064293: less: diff for NMU version 590-2.1

[Salvatore Bonaccorso]

Control: tags 1064293 + patch
Control: tags 1064293 + pending
Control: tags 1068938 + patch
Control: tags 1068938 + pending


Dear maintainer,

I've prepared an NMU for less (versioned as 590-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

As well pushed in a separte branch on salsa, which can be merged if
accepted to unstable:

https://salsa.debian.org/debian/less/-/tree/sid-2024-security-fixes?ref_type=heads

Regards.
Salvatore
diff -Nru less-590/debian/changelog less-590/debian/changelog
--- less-590/debian/changelog	2023-03-12 17:18:18.0 +0100
+++ less-590/debian/changelog	2024-04-19 15:09:49.0 +0200
@@ -1,3 +1,13 @@
+less (590-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624)
+(Closes: #1064293)
+  * Fix bug when viewing a file whose name contains a newline (CVE-2024-32487)
+(Closes: #1068938)
+
+ -- Salvatore Bonaccorso   Fri, 19 Apr 2024 15:09:49 +0200
+
 less (590-2) sid; urgency=medium
 
   * d/control: set standards version to 4.6.2
diff -Nru less-590/debian/patches/Fix-bug-when-viewing-a-file-whose-name-contains-a-ne.patch less-590/debian/patches/Fix-bug-when-viewing-a-file-whose-name-contains-a-ne.patch
--- less-590/debian/patches/Fix-bug-when-viewing-a-file-whose-name-contains-a-ne.patch	1970-01-01 01:00:00.0 +0100
+++ less-590/debian/patches/Fix-bug-when-viewing-a-file-whose-name-contains-a-ne.patch	2024-04-19 15:09:49.0 +0200
@@ -0,0 +1,67 @@
+From: Mark Nudelman 
+Date: Thu, 11 Apr 2024 17:49:48 -0700
+Subject: Fix bug when viewing a file whose name contains a newline.
+Origin: https://github.com/gwsw/less/commit/007521ac3c95bc76e3d59c6dbfe75d06c8075c33
+Bug-Debian: https://bugs.debian.org/1068938
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2024-32487
+
+---
+ filename.c | 31 +--
+ 1 file changed, 25 insertions(+), 6 deletions(-)
+
+--- a/filename.c
 b/filename.c
+@@ -136,6 +136,15 @@ metachar(c)
+ }
+ 
+ /*
++ * Must use quotes rather than escape char for this metachar?
++ */
++static int must_quote(char c)
++{
++	/* {{ Maybe the set of must_quote chars should be configurable? }} */
++	return (c == '\n'); 
++}
++
++/*
+  * Insert a backslash before each metacharacter in a string.
+  */
+ 	public char *
+@@ -168,6 +177,9 @@ shell_quote(s)
+  * doesn't support escape chars.  Use quotes.
+  */
+ use_quotes = 1;
++			} else if (must_quote(*p))
++			{
++len += 3; /* open quote + char + close quote */
+ 			} else
+ 			{
+ /*
+@@ -197,15 +209,22 @@ shell_quote(s)
+ 	{
+ 		while (*s != '\0')
+ 		{
+-			if (metachar(*s))
++			if (!metachar(*s))
+ 			{
+-/*
+- * Add the escape char.
+- */
++*p++ = *s++;
++			} else if (must_quote(*s))
++			{
++/* Surround the char with quotes. */
++*p++ = openquote;
++*p++ = *s++;
++*p++ = closequote;
++			} else
++			{
++/* Insert an escape char before the char. */
+ strcpy(p, esc);
+ p += esclen;
++*p++ = *s++;
+ 			}
+-			*p++ = *s++;
+ 		}
+ 		*p = '\0';
+ 	}
diff -Nru less-590/debian/patches/Shell-quote-filenames-when-invoking-LESSCLOSE.patch less-590/debian/patches/Shell-quote-filenames-when-invoking-LESSCLOSE.patch
--- less-590/debian/patches/Shell-quote-filenames-when-invoking-LESSCLOSE.patch	1970-01-01 01:00:00.0 +0100
+++ less-590/debian/patches/Shell-quote-filenames-when-invoking-LESSCLOSE.patch	2024-04-19 15:09:49.0 +0200
@@ -0,0 +1,43 @@
+From: Mark Nudelman 
+Date: Sat, 25 Jun 2022 11:54:43 -0700
+Subject: Shell-quote filenames when invoking LESSCLOSE.
+Origin: https://github.com/gwsw/less/commit/c6ac6de49698be84d264a0c4c0c40bb870b10144
+Bug-Debian: https://bugs.debian.org/1064293
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2022-48624
+
+---
+ filename.c | 10 --
+ 1 file changed, 8 insertions(+), 2 deletions(-)
+
+diff --git a/filename.c b/filename.c
+index 5824e385dce4..dff20c08d81c 100644
+--- a/filename.c
 b/filename.c
+@@ -972,6 +972,8 @@ close_altfile(altfilename, filename)
+ {
+ #if HAVE_POPEN
+ 	char *lessclose;
++	char *qfilename;
++	char *qaltfilename;
+ 	FILE *fd;
+ 	char *cmd;
+ 	int len;
+@@ -986,9 +988,13 @@ close_altfile(altfilename, filename)
+ 		error("LESSCLOSE ignored; must contain no more than 2 %%s", NULL_PARG);
+ 		return;
+ 	}
+-	len = (int) (strlen(lessclose) + strlen(filename) + strlen(altfilename) + 2);
++	qfilename = shell_quote(filename);
++	qaltfilename = shell_quote(altfilename);
++	len = (int) (strlen(lessclose) + strlen(qfilename) + strlen(qaltfilename) + 2);
+ 	cmd = (char *) ecalloc(len, sizeof(char));
+-	SNPRINTF2(cmd, len, lessclose, filename, altfilename);
++	SNPRINTF2(cmd, len, lessclose, qfilename, qaltfilename);
++	free(qaltfilename);
++	free(qfilename);
+ 	fd = shellcmd(cmd);
+ 	free(cmd);
+ 	if (fd != NULL)
+-- 
+2.43.0
+
diff -Nru less-590/debian/patches/series 

Bug#1069299: kodi-visualization-waveform FTBFS on arm*: does not agree on gl vs gles

[Helmut Grohne]

Source: kodi-visualization-waveform
Version: 20.2.1+ds1-1
Severity: serious
Tags: ftbfs

kodi-visualization-waveform fails to build from source on arm
architectures. A build fails like this:

| CMake Error at 
/usr/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
|   Could NOT find OpenGLES (missing: OPENGLES_gl_LIBRARY OPENGLES_INCLUDE_DIR)
| Call Stack (most recent call first):
|   /usr/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:600 
(_FPHSA_FAILURE_MESSAGE)
|   FindOpenGLES.cmake:37 (find_package_handle_standard_args)
|   CMakeLists.txt:41 (find_package)

Looking into CMakeLists.txt, one can see that it takes the
APP_RENDER_SYSTEM=gles path. I guess this is rooted in kodi recently
having changed this for all arm architectures via #1056563. Now
kodi-visualization-waveform does not have any dependency on gles
libraries but happens to pull gl libraries transitively. As a result the
build now fails.

I'm not sure whether this is to be fixed in kodi-visualization-waveform
or kodi. The end result is that this very package FTBFS. Hence filing
here initially, but reassigning may still make sense.

Helmut

Bug#1067561: marked as done (FTBFS: Error: symbol `open64' is already defined)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 14:35:05 +
with message-id 
and subject line Bug#1067561: fixed in lightdm 1.32.0-5
has caused the Debian Bug report #1067561,
regarding FTBFS: Error: symbol `open64' is already defined
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=lightdm=armel=1.32.0-4%2Bb3=1711185127=0

/bin/bash ../../libtool  --tag=CC   --mode=link gcc -Wall
-Wstrict-prototypes  -Wnested-externs
-Werror=missing-prototypes  -Werror=implicit-function-
declaration  -Werror=pointer-arith
-Werror=init-self  -Werror=format-security
-Werror=format=2  -Werror=missing-include-dirs
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include -pthread
-I/usr/include/libmount -I/usr/include/blkid  -I/usr/include/gio-unix-2.0
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include -pthread
-I/usr/include/libmount -I/usr/include/blkid  -g -O2 -Werror=implicit-function-
declaration -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -O0  -Wl,-z,relro
-Wl,-z,now -Wl,-O1 -o Xvnc Xvnc-Xvnc.o Xvnc-x-authority.o Xvnc-x-common.o Xvnc-
x-server.o Xvnc-status.o -lgobject-2.0 -lglib-2.0  -lglib-2.0  -lgio-2.0
-lgobject-2.0 -lglib-2.0  -lgio-2.0 -lgobject-2.0 -lglib-2.0
/tmp/ccCHYR2t.s: Assembler messages:
/tmp/ccCHYR2t.s:2779: Error: symbol `open64' is already defined
/tmp/ccCHYR2t.s:3181: Error: symbol `creat64' is already defined
/tmp/ccCHYR2t.s:3508: Error: symbol `__stat64_time64' is already defined


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

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

We believe that the bug you reported is fixed in the latest version of
lightdm, 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.
Yves-Alexis Perez  (supplier of updated lightdm 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, 19 Apr 2024 15:34:32 +0200
Source: lightdm
Architecture: source
Version: 1.32.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 1067561
Changes:
 lightdm (1.32.0-5) unstable; urgency=medium
 .
   * d/patch: add upstream patch for 64b time_t build failure (Closes: #1067561)
   * d/control: replace pkg-config build-dep by pkgconf
   * d/gir1.2-lightdm-1.install: move typelib to multi-arch dir
   * Upload to unstable
Checksums-Sha1:
 8dcd27ce65dde196c89b62eba48f4ddec656a462 2493 lightdm_1.32.0-5.dsc
 c033f272898779060ebaf6deb616ba74cd239e41 39744 lightdm_1.32.0-5.debian.tar.xz
 0635df7ab89a139794fcf1e63d667b77391706c4 20924 lightdm_1.32.0-5_amd64.buildinfo
Checksums-Sha256:
 ee37960474840f5fa4e31838fb4eaf9ca4154ccbfc5922119af65658f2ea481f 2493 
lightdm_1.32.0-5.dsc
 453248d03826e6af8fcedcfd2039d48927a961cd46d8d9ea6c2c32a3ac1e5a72 39744 
lightdm_1.32.0-5.debian.tar.xz
 110c2ad1de1f97f26c14dc21f614026a707d101d6b70c944d4f30b4a6ecb5f61 20924 
lightdm_1.32.0-5_amd64.buildinfo
Files:
 f8b5cad61493d84b8fe998cc54124f53 2493 x11 optional lightdm_1.32.0-5.dsc
 

Bug#1052855: marked as done (firmware-microbit-micropython: FTBFS: unsatisfiable build-dependencies: libstdc++-arm-none-eabi-dev (= 15:12.2.rel1-1+23), gcc-arm-none-eabi (= 15:12.2.rel1-1))

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 14:30:04 +0100
with message-id <2ed1514f-5951-4963-a261-31534b095...@morrott.co.uk>
and subject line Re: Build deps are now satisfied
has caused the Debian Bug report #1052855,
regarding firmware-microbit-micropython: FTBFS: unsatisfiable 
build-dependencies: libstdc++-arm-none-eabi-dev (= 15:12.2.rel1-1+23), 
gcc-arm-none-eabi (= 15:12.2.rel1-1)
to be marked as done.

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

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


-- 
1052855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firmware-microbit-micropython
Version: 1.0.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cmake, debhelper-compat (= 13), dh-python, 
> gcc-arm-none-eabi, libnewlib-arm-none-eabi, libssl-dev, 
> libstdc++-arm-none-eabi-newlib, ninja-build, python3-setuptools, 
> python3-sphinx, python3-sphinx-rtd-theme, srecord, yotta, build-essential, 
> fakeroot
> Filtered Build-Depends: cmake, debhelper-compat (= 13), dh-python, 
> gcc-arm-none-eabi, libnewlib-arm-none-eabi, libssl-dev, 
> libstdc++-arm-none-eabi-newlib, ninja-build, python3-setuptools, 
> python3-sphinx, python3-sphinx-rtd-theme, srecord, yotta, build-essential, 
> fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [814 B]
> Get:5 copy:/<>/apt_archive ./ Packages [846 B]
> Fetched 2269 B in 0s (79.7 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libstdc++-arm-none-eabi-newlib : Depends: libstdc++-arm-none-eabi-dev (= 
> 15:12.2.rel1-1+23) but it is not going to be installed
>   Depends: gcc-arm-none-eabi (= 
> 15:12.2.rel1-1) but 15:12.3.rel1-1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/firmware-microbit-micropython_1.0.1-4_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Recent updates to the ARM GCC bits in unstable have resolved this issue without 
any work required in the firmware-microbit-micropython package itself.


These updates have, however, resulted in new compilation failures, which I will 
look at next along with packaging the latest 1.1.1 version, now that the build 
dependency situation has resolved.--- End Message ---

Bug#1064293: less: CVE-2022-48624

[Salvatore Bonaccorso]

Hi,

FWIW, I'm actually preparing a security update for the two CVEs and
for bookworm I was first planning to do a 590-2.1 reaching unstable,
and so then 590-2.1~deb12u1 for bookworm.

But if you want to override it with a NMU and proposing to salvage the
package this is equally fine.

Regards,
Salvatore

Processed: bookworm-pu: package python-asdf/2.14.3-1+deb12u1

[Debian Bug Tracking System]

Processing control commands:

> block 1054581 with -1
Bug #1054581 {Done: Ole Streicher } [python3-asdf] asdf: 
Missing dependency on asdf-unit-schemas (breaks pkg_resources)
1054581 was not blocked by any bugs.
1054581 was not blocking any bugs.
Added blocking bug(s) of 1054581: 1069295
> affects -1 + src:python-asdf
Bug #1069295 [release.debian.org] bookworm-pu: package 
python-asdf/2.14.3-1+deb12u1
Added indication that 1069295 affects src:python-asdf

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

Bug#1068537: marked as pending in ruby-ethon

[Antonio Terceiro]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-ethon/-/commit/c66b1a1db60d982a2648f44977ed104a42d93293


Don't hardcode a dependency on libcurl4

Closes: #1068537


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068537

Processed: Bug#1068537 marked as pending in ruby-ethon

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068537 [src:ruby-ethon] ruby-ethon: arch:all package depends on pre-t64 
library
Added tag(s) pending.

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

Processed: block 1068537 with 1069292

[Debian Bug Tracking System]

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

> block 1068537 with 1069292
Bug #1068537 [src:ruby-ethon] ruby-ethon: arch:all package depends on pre-t64 
library
1068537 was not blocked by any bugs.
1068537 was not blocking any bugs.
Added blocking bug(s) of 1068537: 1069292
> thanks
Stopping processing here.

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

Bug#1066315: marked as done (kraptor: FTBFS: src/main.c:57:5: error: implicit declaration of function ‘mkdir’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 13:20:20 +
with message-id 
and subject line Bug#1066315: fixed in kraptor 0.0.20040403+ds-4
has caused the Debian Bug report #1066315,
regarding kraptor: FTBFS: src/main.c:57:5: error: implicit declaration of 
function ‘mkdir’ [-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.)


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

Hi,

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

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

Relevant part (hopefully):
> cc -Iinclude -Wall -O2 `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get 
> CPPFLAGS` -c src/pmask.c -o obj/linux/pmask.o
> src/main.c: In function ‘main’:
> src/main.c:57:5: error: implicit declaration of function ‘mkdir’ 
> [-Werror=implicit-function-declaration]
>57 | mkdir(str, 0755);
>   | ^
> src/main.c:159:1: warning: ‘textout’ is deprecated [-Wdeprecated-declarations]
>   159 | textout(screen, font,"Wait... loading...",0,SCREEN_H - 
> text_height(font)*2, makecol(255,255,255));
>   | ^~~
> In file included from /usr/include/allegro/base.h:41,
>  from /usr/include/allegro.h:25,
>  from src/main.c:23:
> /usr/include/allegro/alcompat.h:139:1: note: declared here
>   139 | AL_INLINE_DEPRECATED(void, textout, (struct BITMAP *bmp, AL_CONST 
> FONT *f, AL_CONST char *str, int x, int y, int color),
>   | ^~~~
> cc -Iinclude -Wall -O2 `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get 
> CPPFLAGS` -c src/premio.c -o obj/linux/premio.o
> cc1: some warnings being treated as errors
> make[2]: *** [makefile.all:17: obj/linux/main.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/kraptor_0.0.20040403+ds-3_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: kraptor
Source-Version: 0.0.20040403+ds-4
Done: Andreas Rönnquist 

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

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

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

Debian distribution maintenance software
pp.
Andreas Rönnquist  (supplier of updated kraptor 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: Fri, 19 Apr 2024 14:51:04 +0200
Source: kraptor
Architecture: source
Version: 0.0.20040403+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Andreas Rönnquist 
Closes: 1066315
Changes:
 kraptor (0.0.20040403+ds-4) unstable; urgency=medium
 .
   [ Andreas Rönnquist ]
   * Team upload.
 .
   [ Alexandre Detiste ]
   * debhelper 14/15 compat
   * remove fixup preinst script from 2013
   * Trim trailing whitespace.
   * Use secure URI in Homepage field.
   * Update Miriam email address
 .
   [ Steve Langasek ]
   * Add missing include (Closes: #1066315)
Checksums-Sha1:
 bd64fc702749353c20bc3c53ef9f9ddded190ad5 2135 kraptor_0.0.20040403+ds-4.dsc
 

Processed (with 1 error): bookworm-pu: package comitup/1.38-2~deb12u1

[Debian Bug Tracking System]

Processing control commands:

> block 1041447 with -1
Bug #1041447 {Done: David Steele } [comitup] comitup: fails 
to install, remove, distupgrade, and install again
1041447 was not blocked by any bugs.
1041447 was not blocking any bugs.
Added blocking bug(s) of 1041447: 1069291
> tag -1 + src:comitup
Unknown tag/s: src:comitup.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky 
forky-ignore.

Bug #1069291 [release.debian.org] bookworm-pu: package comitup/1.38-2~deb12u1
Requested to add no tags; doing nothing.

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

Bug#1067923: marked as done (alsa-ucm-conf: should depend on libasound2t64 instead of libasound2)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 12:34:24 +
with message-id 
and subject line Bug#1067923: fixed in alsa-ucm-conf 1.2.11-1.1
has caused the Debian Bug report #1067923,
regarding alsa-ucm-conf: should depend on libasound2t64 instead of libasound2
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.)


-- 
1067923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alsa-ucm-conf
Version: 1.2.11-1
Severity: serious
Justification: depends on missing package after time_t transition

Dear maintainer,

After the time_t transition, the libasound2 was renamed to libasound2t64, so
the dependencies should be updated.

Regards,


-- 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/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages alsa-ucm-conf depends on:
ii  libasound2t64 [libasound2]  1.2.11-1+b1

alsa-ucm-conf recommends no packages.

alsa-ucm-conf suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: alsa-ucm-conf
Source-Version: 1.2.11-1.1
Done: Bastian Germann 

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

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

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated alsa-ucm-conf 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, 19 Apr 2024 13:07:33 +0200
Source: alsa-ucm-conf
Architecture: source
Version: 1.2.11-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian ALSA Maintainers 
Changed-By: Bastian Germann 
Closes: 1067923
Changes:
 alsa-ucm-conf (1.2.11-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Move to Depends: libasound2t64 (closes: #1067923).
Checksums-Sha1:
 a644175f8165a89559290ee54e95a63a45328b89 2161 alsa-ucm-conf_1.2.11-1.1.dsc
 5a0424126a2796710b420cf16e1dddb46839fdf8 6844 
alsa-ucm-conf_1.2.11-1.1.debian.tar.xz
 3d34590e68e09cc02919efd3fbac0a876555a5f6 5419 
alsa-ucm-conf_1.2.11-1.1_source.buildinfo
Checksums-Sha256:
 1e75fed5ad858dd38d63af5bd1293fa8614d5849686c96c8ed8603490c57c253 2161 
alsa-ucm-conf_1.2.11-1.1.dsc
 2902542086acee873cf5246f197399bd8de472bec425fc0bbe1c20ddf0670665 6844 
alsa-ucm-conf_1.2.11-1.1.debian.tar.xz
 39e4b435f73a1d00821c2421d7c3bd1a2286407ba51fbe6c08ecad788d1f6314 5419 
alsa-ucm-conf_1.2.11-1.1_source.buildinfo
Files:
 ede5fc5665dc2aaa86e37ea77be0ae93 2161 libs optional 
alsa-ucm-conf_1.2.11-1.1.dsc
 60a525ad7886abcd217e8cffbfabb913 6844 libs optional 
alsa-ucm-conf_1.2.11-1.1.debian.tar.xz
 ed0b87cc5fee87b92829e5ec568c0efa 5419 libs optional 
alsa-ucm-conf_1.2.11-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYiXvgQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFBxwDACnEGVIzKp61VVFYYGMBNYHWAcCFFE2bl/k
1vncshz79clRix6jdwS6HLg+99344K0cpOUSjDqPcixsVlln0qHck0XDvkXC/hnz
xrIWNIcYADUlHeYlLcGQ2nJ4tOGYSC9xXzi81TlH2Kt4iykUnswbZ5U8onbclQ0D
yj1Bi/45dJx3Q5nS04TGuOuguQSqIouopApaxG0DqO2o7vYQ+MmnmS4vCfH6Dzqc
J8kLyiZ0V2sFdK6AXhnyOIIm1D6CTXiD+icDkET71n2RsNz98yJXBUD3Ob9KMICM
exIOGAIXhvOij1+MY2WbQ4sPMG6l5LK1dTdsnnPqQau0brblN++g+O5q621+ry0u
3jDvzLkfDQeqt+XVVpwBNaeUxcSH1qk1GLV7a4+aoKMvTXHTTUN+1K7/mL0AjOZd
dSwLySC817iDkQiZwYp2r7dngacRtQ/Ee1M4H43g/Ih7kppv//oAI/hYbqdO/97C
iZMMtuRvDT72G8lYCBGkGJKkV15umak=
=70oW
-END PGP SIGNATURE-



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

Bug#1067923: alsa-ucm-conf: should depend on libasound2t64 instead of libasound2

[Bastian Germann]

I am uploading a NMU to fix this.
The debdiff is attached.

alsa-ucm-conf_1.2.11-1.1.debdiff
Description: Binary data

Bug#1069163: closed by Debian FTP Masters (reply to Patrick Franz ) (Bug#1069163: fixed in libkf5ksieve 4:22.12.3-2)

[Jonas Schäfer]

Hi there,

With a test build provided by Patrick, I was able to confirm that this 
fixes the issue on my system.

Thank you for the swift response!

kind regards,
-- 
Jonas Schäfer
Team Lead Cloud Infrastructure Development

Cloud Technologies GmbH
Königsbrücker Straße 96 | 01099 Dresden
+49 351 479 367 37
jonas.schae...@cloudandheat.com | www.cloudandheat.com

Green, Open, Efficient.
Your Cloud Service and Cloud Technology Provider from Dresden.
https://www.cloudandheat.com/

Commercial Register: District Court Dresden
Register Number: HRB 30549
VAT ID No.: DE281093504
Managing Director: Nicolas Röhrs
Authorized signatory: Dr. Marius Feldmann


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

Processed: Re: python3-h5sparse incomplete Depends: python3-h5py-serial

[Debian Bug Tracking System]

Processing control commands:

> tag -1 sid trixie
Bug #1053266 {Done: Nilesh Patra } [python3-h5sparse] 
python3-h5sparse incomplete Depends: python3-h5py-serial
Added tag(s) trixie and sid.

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

Bug#1053266: python3-h5sparse incomplete Depends: python3-h5py-serial

[Andreas Beckmann]

Control: tag -1 sid trixie

On Sat, 30 Sep 2023 12:34:07 +0200 Drew Parsons  wrote:

Package: python3-h5sparse
Version: 0.1.0-6


doing 'import h5sparse' with this package version installed in bookworm
works fine without python3-h5py while it fails in sid without python3-h5py:


import h5sparse

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/h5sparse/__init__.py", line 2, in 

from .h5sparse import Group, File, Dataset  # noqa: F401
^^
  File "/usr/lib/python3/dist-packages/h5sparse/h5sparse.py", line 29, in 

class Group(h5py.Group):
^^
AttributeError: module 'h5py' has no attribute 'Group'


Andreas

Bug#1067561: FTBFS: Error: symbol `open64' is already defined

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, 2024-04-19 at 00:01 +0100, Peter Green wrote:
> Thanks, upstream has now accepted a patch that takes a slightly different
> approach to fixing the issue.
> 
> https://github.com/canonical/lightdm/issues/352

Yes I saw. That's why I think this should have been reported and talked
directly with upstream, before the NMU, but eh...
> 
> Could we get this uploaded to sid, so that the lightweight desktops
> are installable on armel/armhf again?

Yes I'll look into it.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYiRuIACgkQ3rYcyPpX
RFsQkQgA1h8bIbWp0Sj6VqgcdG/dkwKEQ6Xrcuh6gpL7Gy2BiT2d1tY4HFN94bhG
FJVz9E9QOqlZt2Mo7JQ6EBYyvcTspO0T09ZU/22VjA2NdP0eSRHTiyiFXq4hyoYf
OBnPpKTxq0Wp9L7Tefta7uNPIBX+lsVlw9cdwv6PIEy6jlF3xjX+B8FoK/K/fIeY
FuQh5qOw/k/nnPAM4pHxYGAfRw+BNBEnI3ADFCCWDvpQSgZ9uJ9UB3wnEo50aXub
dsNsXAZx3UIX2CfDBs1jXsPc/B37csOr9sJIqDn1xJKaT/Q6Yk1A/LV8uTa38wGh
MykmdfDqWLT0nK4atbVH5fxjkTNdDg==
=Fysh
-END PGP SIGNATURE-

Processed: Re: pagetools: FTBFS with netpbm11

[Debian Bug Tracking System]

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

> tags 1012690 + patch
Bug #1012690 [src:pagetools] pagetools: FTBFS with netpbm11
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1012690: pagetools: FTBFS with netpbm11

[Santiago Vila]

tags 1012690 + patch
thanks

Hello Víctor.

I believe the attached patch will be enough to fix the build failure
(but you might want to update other things as well).

I would gladly be your sponsor if you still need it.

Thanks.diff --git a/debian/control b/debian/control
index 0e9a667..9b33160 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: graphics
 Priority: optional
 Maintainer: Víctor Cuadrado Juan 
 Standards-Version: 4.1.3
-Build-Depends: debhelper (>= 11), libnetpbm10-dev, libtiff5-dev
+Build-Depends: debhelper (>= 11), libnetpbm11-dev, libtiff5-dev
 Homepage: https://sourceforge.net/projects/pagetools/
 Vcs-Git: https://salsa.debian.org/viccuad-guest/pagetools.git
 Vcs-Browser: https://salsa.debian.org/viccuad-guest/pagetools
diff --git a/formats/pbmfact.cpp b/formats/pbmfact.cpp
index c65fef5..2374ba5 100644
--- a/formats/pbmfact.cpp
+++ b/formats/pbmfact.cpp
@@ -19,7 +19,7 @@
 #include 
 
 extern "C"{
-#include 
+#include 
 }
 
 namespace pagetools{

Bug#1064293: less: CVE-2022-48624

[P. J. McDermott]

On 2024-04-12 at 16:10, Christoph Anton Mitterer wrote:
> Hey.
> 
> There seems to be a somewhat similar issue reported by Jakub Wilk on
> oss-security:
> https://www.openwall.com/lists/oss-security/2024/04/12/5
> 
> where quoting causes troubles (though I couldn't replay the demo).

That was since assigned CVE-2024-32487 and Debian bug #1068938.

> Any chance to get both fixed in Debian unstable?

While the maintainer appears to be somewhat active elsewhere in Debian,
this package hasn't seen an upload in over a year and the packaged
version is getting close to three years old.  (Although I found that
updating to the latest upstream release version introduces new test
suite and lintian issues requiring some upstream patches backported and
reverted/fixed.)

In my Salsa fork[1] I have updated the package (fixing CVE-2022-48624)
and backported (with necessary code changes) the CVE-2024-32487 fix.
I would like to adopt, co-maintain, or if necessary salvage src:less
(see bug #1069280).  But the procedure[2] for that requires 28 days of
waiting for the maintainer to respond.  Perhaps in the meantime a new
upstream version NMU is warranted, or should the procedure be sped up
somehow?

[1]: https://salsa.debian.org/pehjota/less
[2]: 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#how-to-salvage-a-package
-- 
Patrick "P. J." McDermott:  http://www.pehjota.net/
Lead Developer, ProteanOS:  http://www.proteanos.com/
Founder and CEO, Libiquity: http://www.libiquity.com/

Bug#1064531: marked as done (src:amberol: unsatisfied build dependency in testing: librust-lofty-0.17-dev)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 10:04:27 +
with message-id 
and subject line Bug#1064531: fixed in amberol 0.10.3-3
has caused the Debian Bug report #1064531,
regarding src:amberol: unsatisfied build dependency in testing: 
librust-lofty-0.17-dev
to be marked as done.

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

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


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

Source: amberol
Version: 0.10.3-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

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

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

Paul

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

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



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: amberol
Source-Version: 0.10.3-3
Done: Arnaud Ferraris 

We believe that the bug you reported is fixed in the latest version of
amberol, 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.
Arnaud Ferraris  (supplier of updated amberol 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: Fri, 19 Apr 2024 11:36:42 +0200
Source: amberol
Architecture: source
Version: 0.10.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Arnaud Ferraris 
Closes: 1064531
Changes:
 amberol (0.10.3-3) unstable; urgency=medium
 .
   * debian: update build dependencies.
 Some Rust crates such as `lofty` and `mpris-server` are being updated in
 Debian, so let's reflect that in both our patches and `d/control`.
 (Closes: #1064531)
   * d/gbp.conf: change default `dch` commit message
Checksums-Sha1:
 98e5efc6f822c1b7d1e5f5e418c88fbfe7a3a9a7 2712 amberol_0.10.3-3.dsc
 223e1bdb343bdc97ca7d855cd19dbeb9b4492470 28408 amberol_0.10.3-3.debian.tar.xz
 ec3dc5c50b55eb6e4851d456f8c8e773a052e5e7 41508 
amberol_0.10.3-3_source.buildinfo
Checksums-Sha256:
 50f4311c022b598139d3e10b7433456b1b4b59a1bcc0bcac85e706e3ee190489 2712 
amberol_0.10.3-3.dsc
 0608dd244039b282526854e0280faea8294a537d8b523765b75cdb47c962d98f 28408 
amberol_0.10.3-3.debian.tar.xz
 e7fe71b85c55dd27678a81bb1cd8a8a0fea0aca356febd5f0de5175851f38014 41508 
amberol_0.10.3-3_source.buildinfo
Files:
 ce136e844561964e89105b31e435aaf1 2712 gnome optional amberol_0.10.3-3.dsc
 e7248233e56adcc1b9042a4f540d0f97 28408 gnome optional 
amberol_0.10.3-3.debian.tar.xz
 1831ded35a72b44f79dab647dc42a35b 41508 gnome optional 
amberol_0.10.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEeW2zk9w/9AIituoi0+u1lmu5kZYFAmYiPWkACgkQ0+u1lmu5
kZaSyg//cOLUciUPzOqhvI3KiSgCXhA4cKp9Y7w0XfGtLik94HqI/2oseKq88A0g
P9wLt68dzDYM9nfA5Ot9s2ozQW2NH2dhys87YBN4ptm6C0thry6kCI/8bT8CQQvP
+wCgYlujWVEFh8XY1zb4Q9uwE5TFrVNDkxmTnMwnZM3UALN4c1BqisA3WI7LTiy/
F2Pp7Dop1cjQXHqrkGLxv4JyQY1PGCpwiG54eexbPw4A+XLazcJoiHA9lXmoAYif
Cto3CPYRLCD+m9U6kL6Xeq3/1oy19X4r2dv7W+qea73Z7OvHU1w8El2UjykX5Du3
KaYVcV04Fck3NWyleXQT1+RJmR2VS0pYJVKGVOAhkCZhLRqo0a/WBY47lmUXjnna
RKJ8jfzPZqzytg37ippFGhIRSKj+E8mfXVu2YkBw/UX6gsM3FSvewFscGHHiEV4+
bAtbDWxULo46bkxGjN3JtPU6ow23tPctv9RfljT4cnmuTeLNtWAnt7PWIS7TYW0z

Processed: bookworm-pu: package libmail-dkim-perl/1.20230212-2~deb12u1

[Debian Bug Tracking System]

Processing control commands:

> block 1040438 with -1
Bug #1040438 {Done: gregor herrmann } [libmail-dkim-perl] 
libmail-dkim-perl: missing dependency on libgetopt-long-descriptive-perl
1040438 was not blocked by any bugs.
1040438 was not blocking any bugs.
Added blocking bug(s) of 1040438: 1069284
> affects -1 + src:libmail-dkim-perl
Bug #1069284 [release.debian.org] bookworm-pu: package 
libmail-dkim-perl/1.20230212-2~deb12u1
Added indication that 1069284 affects src:libmail-dkim-perl

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

Bug#1066224:

[Miriam Espana Acebal]

Hi,

In ubuntu we applied the upstream's fix at
https://github.com/radvd-project/radvd/pull/196. I adapted it to a pair of
patches that I attach here for fixing this FTBFS.

I am sending this for your consideration, and I hope it helps.

Best,

Miriam

-- 
[image: Canonical-20th-anniversary]

Miriam España Acebal

Software Engineer II - Ubuntu Public Cloud/Server

Email:

miriam.esp...@canonical.com

Location:

Spain  (GMT+2)

canonical.com

ubuntu.com
Origin: upstream, https://github.com/radvd-project/radvd/commit/e0f5bcd9091a5f7abd423fce9f372c8079849a64
From: Sam James 
Date: Thu, 17 Nov 2022 22:03:25 +
Subject: [PATCH] gram.y: Fix -Wimplicit-function-declaration

Clang 16 makes -Wimplicit-function-declaration an error by default.

For more information, see LWN.net [0] or LLVM's Discourse [1], the Gentoo wiki [2],
or the (new) c-std-porting mailing list [3].

[0] https://lwn.net/Articles/913505/
[1] https://discourse.llvm.org/t/configure-script-breakage-with-the-new-werror-implicit-function-declaration/65213
[2] https://wiki.gentoo.org/wiki/Modern_C_porting
[3] hosted at lists.linux.dev.

Bug-Gentoo: https://bugs.gentoo.org/880823
Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/radvd/+bug/2061370
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066224
Forwarded: yes
Signed-off-by: Sam James 
---
 gram.y | 4 
 1 file changed, 4 insertions(+)

--- a/gram.y
+++ b/gram.y
@@ -20,6 +20,10 @@
 
 #define YYERROR_VERBOSE 1
 
+int yylex (void);
+void yyset_in (FILE * _in_str);
+int yylex_destroy (void);
+
 #if 0 /* no longer necessary? */
 #ifndef HAVE_IN6_ADDR_S6_ADDR
 # ifdef __FreeBSD__
Origin: upstream, https://github.com/radvd-project/radvd/commit/ff7ab0cf445236f30e58531175ba912614fed952
From: Sam James 
Date: Thu, 17 Nov 2022 22:03:25 +
Subject: [PATCH] Makefile.am: drop -Wno-implicit-function-declaration

1. Clang 16 makes -Wimplicit-function-declaration error by default
   (and it's planned that GCC 14 will do the same) so we need to fix
   the real problem. This is papering over it.

2. It's not true that there's nothing we can do about it. Fix in a follow-up
   commit.

Bug-Gentoo: https://bugs.gentoo.org/880823
Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/radvd/+bug/2061370
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066224
Forwarded: yes
Signed-off-by: Sam James 
---
 Makefile.am | 3 ---
 1 file changed, 3 deletions(-)

--- a/Makefile.am
+++ b/Makefile.am
@@ -66,9 +66,6 @@
 scanner.c: gram.h
 gram.h: gram.c
 
-libradvd_parser_a_CFLAGS = \
-	-Wno-implicit-function-declaration
-
 libradvd_parser_a_SOURCES = \
 	gram.h \
 	gram.y \

Processed: bookworm-pu: package what-is-python/13+deb12u1

[Debian Bug Tracking System]

Processing control commands:

> block 1034995 with -1
Bug #1034995 {Done: Matthias Klose } [python-is-python3] 
python-is-python3: missing Breaks+Replaces for python-dev-is-python2 when 
upgrading from bullseye
1034995 was not blocked by any bugs.
1034995 was not blocking any bugs.
Added blocking bug(s) of 1034995: 1069281
> affects -1 + src:what-is-python
Bug #1069281 [release.debian.org] bookworm-pu: package what-is-python/13+deb12u1
Added indication that 1069281 affects src:what-is-python

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

Bug#1012893: Status of the t64 transition

[Andreas Tille]

Hi Sebastian,

thank you for your work on t64 transition.

Am Thu, Apr 18, 2024 at 09:22:02PM +0200 schrieb Sebastian Ramacher:

I've spotted these Debian Med packages.

> gentle
> jellyfish
> quorum
> sbmltoolbox

No idea how we can help here.  Please let us know if we can do
something.

> anfo

We like to fix gcc-12 issues (#1012893) in anfo but so far nobody
managed to do so since it seems to be quite complex.  If we are
blocking progress with this package its probably a sign that it
should be removed from Debian.

> blasr

We try to work on #1067374.

> freebayes

Upstream is working on bug #1067271.

> vg

This package is in a bad state in any case and we are aware of this.
However, could you explain in how far is this affecting t64 transition
since 32bit architectures are excluded?

> If you maintain any of the packages above, please check their status and
> help get them fixed. Any help in filing bugs, fixing packages,
> requesting removals, etc. is appreciated so that we can look into
> unblocking the whole stack and migrate it to testing.

I fixed two packages of Debian Python Team and pinged about some
packages in Debian Science Team.

Kind regards
Andreas. 

-- 
https://fam-tille.de

Bug#1064702: marked as done (libxcb: FTBFS: KeyError: 'xcb_report_level_t')

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 09:05:50 +
with message-id 
and subject line Bug#1064702: fixed in libxcb 1.17.0-1
has caused the Debian Bug report #1064702,
regarding libxcb: FTBFS: KeyError: 'xcb_report_level_t'
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/build/src'
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/xproto.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/bigreq.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/xc_misc.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/composite.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/damage.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/dpms.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/dri2.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/dri3.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/present.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/glx.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/randr.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/record.xml
> python3 ../../src/c_client.py -c "libxcb 1.15" -l "X Version 11" \
>   -s "3" -p //usr/lib/python3.11/site-packages \
>\
>   //usr/share/xcb/render.xml
> Traceback (most recent call last):
>   File "/<>/build/src/../../src/c_client.py", line 3394, in 
> 
> module.generate()
>   File "/usr/lib/python3/dist-packages/xcbgen/state.py", line 131, in generate
> item.out(name)
>   File "/<>/build/src/../../src/c_client.py", line 3198, in 
> c_request
> _c_request_helper(self, name, void=True, regular=False)
>   File "/<>/build/src/../../src/c_client.py", line 2273, in 
> _c_request_helper
> if namecount[tname] > 1:
>~^^^
> KeyError: 'xcb_report_level_t'
> make[2]: *** [Makefile:1408: damage.c] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/libxcb_1.15-1_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: libxcb
Source-Version: 1.17.0-1
Done: Timo Aaltonen 

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

A summary of the changes between 

Bug#1063631: marked as done (hkl FTBFS with libcglm-dev 0.9.2-1)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 09:05:37 +
with message-id 
and subject line Bug#1063631: fixed in hkl 5.0.0.3434-1
has caused the Debian Bug report #1063631,
regarding hkl FTBFS with libcglm-dev 0.9.2-1
to be marked as done.

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

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


-- 
1063631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hkl
Version: 5.0.0.3381-1
Severity: serious
Tags: ftbfs patch
Forwarded: 
https://repo.or.cz/hkl.git/commit/c3badf0779a70f1666ccf8241d144ebb01897a0e

https://buildd.debian.org/status/logs.php?pkg=hkl=5.0.0.3381-1%2Bb1

...
hkl-binoculars-geometry.c: In function 
‘hkl_binoculars_parameter_transformation_get’:
hkl-binoculars-geometry.c:45:45: error: incompatible type for argument 1 of 
‘glms_rotate_atm’
   45 | r = glms_rotate_atm(m, pivot, angle, axis);
  | ^
  | |
  | mat4s
...
--- End Message ---
--- Begin Message ---
Source: hkl
Source-Version: 5.0.0.3434-1
Done: Picca Frédéric-Emmanuel 

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

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

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated hkl 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, 19 Apr 2024 10:26:26 +0200
Source: hkl
Architecture: source
Version: 5.0.0.3434-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PaN Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Closes: 1013821 1046274 1063631
Changes:
 hkl (5.0.0.3434-1) unstable; urgency=medium
 .
   [ Picca Frédéric-Emmanuel ]
   * Add missing build dependency on gobject-introspection-bin for addon gir.
   * New upstream version 5.0.0.3434
   * Bug fix: "hkl FTBFS with libcglm-dev 0.9.2-1", thanks to Adrian Bunk
 (Closes: #1063631).
   * d/control: Added B-D libinih-dev
   * d/libhkl5.symbols: Updated
   * d/rules: use the right syntax for dh_autoreconf
 .
   [ Roland Mas ]
   * d/control: Added Myself as Uploaders.
   * d/control: B-D added libdatatype99-dev.
   * Bug fix: "Please remove dependency on install-info", thanks to
 hill...@web.de; (Closes: #1013821).
   * Bug fix: "Fails to build source after successful build", thanks to
 Lucas Nussbaum (Closes: #1046274).
Checksums-Sha1:
 2f298f8e96996f6c05d0e1adf7ec44dbe040e2bf 3733 hkl_5.0.0.3434-1.dsc
 1c1c968310e5282d5c8f008b4129eeeaf235ae90 11768260 hkl_5.0.0.3434.orig.tar.xz
 dc7a8b6575f23f74520881d57adde4ca1d3284cf 11788 hkl_5.0.0.3434-1.debian.tar.xz
Checksums-Sha256:
 37d4f711fcba4cf88b3a812d1447fce55ed42cf877500243adc990ab91bc8315 3733 
hkl_5.0.0.3434-1.dsc
 e3cbab502b98cd6eeb4101824fdf8d46b00ea9bd6e67dbacf91cef12a3e91eb4 11768260 
hkl_5.0.0.3434.orig.tar.xz
 21e5f751969a511063061c87a8e23f97179858542d52cece9347add0e4c8f7bf 11788 
hkl_5.0.0.3434-1.debian.tar.xz
Files:
 53caecc0d10554abdbe200e510e29daf 3733 science optional hkl_5.0.0.3434-1.dsc
 6dca73eb6beb12ab477cf351a278f326 11768260 science optional 
hkl_5.0.0.3434.orig.tar.xz
 ad11ea6b9d1297256140085ff35471d3 11788 science optional 
hkl_5.0.0.3434-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmYiKycRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALux4w//c91+9/eRjJRHZjt/C/0wAwjgyb6Vd7/c
WZMT9ZUHXw+MbS6MMaUsmKPPs5qOaaS1lhOWUn8YaQdSg3NHaZWDvs/YmJglLqrJ
KeYKtUg3oHyQ2tU2CRq4w+46gdCWKLgdo6t9sy5EFbdfKE5z9jmm1OlsvQJk9xzi
r7o4iq7LnOh3v36tBgDqcyAYIliUKQChM5SuZk/umQFJHpRuBu6tAFghZRIb0cda
STp2JTi+vwpUL8aHs3IT6OI8MbCcRcL1Cz0eQpYlZi75rSjhE6Ga7mFfQG1Le1/O
Kpyj7F2a7+/jo3IVRSAuTtAkFVPHxiNfAPGfoLDpLfLeTFlH5kr5qrBhn1yEkpGE
aDlb+aPDqMj2VymDEc364MwygH0no5xbuqnQKPUTmCyNltm/wKyVQqJxMKGBvVhn
KJopnuzxrzrNywd6sWnyQ0CZRgUprFOPdd0FghdXKc62EGgapTdBsyPTBwOeadoQ
CoLtndLlgvLtvdmV1gMh4vmpts9uoQCbYwFNJiShfj+MVGKm+2uLzlhzvj6ObBAQ
JwPhRBfl4tvDETvr9bzomqBmduIK0vpqWvY/uUkWFpcJIzOFgisyEH3NCGWuYXsb
JjTKTO4MqV4Vv0VknfJ4fEDKMoKh5VTVnyaRj8HNpDmb6KRDNwERzGz/F4C0gFNp
H9tWHQi8i6k=
=gIRs

Bug#1068963: marked as done (python-falcon: FTBFS: testsuite failure: 3084 passed, 313 skipped, 170 warnings, 35 errors)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 08:40:25 +
with message-id 
and subject line Bug#1068963: fixed in python-falcon 3.1.1-3
has caused the Debian Bug report #1068963,
regarding python-falcon: FTBFS: testsuite failure: 3084 passed, 313 skipped, 
170 warnings, 35 errors
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.)


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

Dear maintainer,

python-falcon fails to build from source due to errors in the testsuite.
>From my build log on amd64:

| === short test summary info 

| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_get[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_put[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_head_405[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_post_multipart_form[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_post_multiple[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_post_invalid_content_length[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_post_read_bounded_stream[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_post_read_bounded_stream_large[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_post_read_bounded_stream_no_body[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_sse[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_sse_client_disconnects_early[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestASGIServer::test_stream_chunked_request[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_hello[_uvicorn_factory-None-True]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_hello[_uvicorn_factory-None-False]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_hello[_uvicorn_factory-4321-True]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_hello[_uvicorn_factory-4321-False]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_rejected[_uvicorn_factory-None-True]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_rejected[_uvicorn_factory-None-False]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_rejected[_uvicorn_factory-4040-True]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_rejected[_uvicorn_factory-4040-False]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_missing_responder[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_select_subprotocol_known[_uvicorn_factory-*-amqp]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_select_subprotocol_known[_uvicorn_factory-wamp-wamp]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_select_subprotocol_unknown[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_disconnecting_client_early[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_send_before_accept[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_recv_before_accept[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_invalid_close_code[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_close_code_on_unhandled_error[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_close_code_on_unhandled_http_error[_uvicorn_factory]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_type_mismatch[_uvicorn_factory-text-send]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_type_mismatch[_uvicorn_factory-text-recv]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_type_mismatch[_uvicorn_factory-data-send]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_type_mismatch[_uvicorn_factory-data-recv]
| ERROR 
tests/asgi/test_asgi_servers.py::TestWebSocket::test_passing_path_params[_uvicorn_factory]
| = 3084 passed, 313 skipped, 170 warnings, 35 errors in 36.58s 
==

A full build log on riscv64 is available here:

Processed: Re: ruby-aws-partitions: Package missing partitions.json

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.653.0-2
Bug #1042415 {Done: Cédric Boutillier } 
[ruby-aws-partitions] ruby-aws-partitions: Package missing partitions.json
Marked as found in versions ruby-aws-partitions/1.653.0-2; no longer marked as 
fixed in versions ruby-aws-partitions/1.653.0-2 and reopened.

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

Bug#1042415: ruby-aws-partitions: Package missing partitions.json

[Andreas Beckmann]

Followup-For: Bug #1042415
Control: found -1 1.653.0-2

I was looking into backporting the trivial fix to stable, but upon
verification I ran into another missing file (partitions-metadata.json),
which is also reproducible on sid:

# irb
irb(main):001:0> require 'aws-partitions'
irb(main):002:1* Aws::Partitions.each do |partition|
irb(main):003:1*   puts partition.name
irb(main):004:0> end
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:235:in
 `read': No such file or directory @ rb_sysopen - 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/partitions-metadata.json
 (Errno::ENOENT)
from 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:235:in
 `default_metadata'
from 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:215:in
 `default_partition_list'
from 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:137:in
 `each'
from (irb):2:in `'
from /usr/lib/ruby/gems/3.1.0/gems/irb-1.4.1/exe/irb:11:in `'
from /usr/bin/irb:25:in `load'
from /usr/bin/irb:25:in `'
irb(main):005:0>

Please add a (superficial) autopkgtest to at least catch these kind of
unusability.
And backport the fixes to bookworm.


Andreas

Bug#1068963: marked as pending in python-falcon

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1068963 in python-falcon 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/openstack-team/python/python-falcon/-/commit/608aa7872ff45cf501f546a7cb696116d9219e6d


* Exclude tests/asgi/test_asgi_servers.py when running tests, as teardown
appears broken. Note that I tried running uvicorn manually, and it seems
working as expected (Closes: #1068963).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068963

Processed: Bug#1068963 marked as pending in python-falcon

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068963 [src:python-falcon] python-falcon: FTBFS: testsuite failure: 3084 
passed, 313 skipped, 170 warnings, 35 errors
Added tag(s) pending.

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

Processed: Bug#1068963 marked as pending in python-falcon

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068963 [src:python-falcon] python-falcon: FTBFS: testsuite failure: 3084 
passed, 313 skipped, 170 warnings, 35 errors
Ignoring request to alter tags of bug #1068963 to the same tags previously set

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

Bug#1068963: marked as pending in python-falcon

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1068963 in python-falcon 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/openstack-team/python/python-falcon/-/commit/608aa7872ff45cf501f546a7cb696116d9219e6d


* Exclude tests/asgi/test_asgi_servers.py when running tests, as teardown
appears broken. Note that I tried running uvicorn manually, and it seems
working as expected (Closes: #1068963).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068963

Bug#1068116: marked as done (python-pylibdmtx: depends on pre-t64 packages)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 07:34:34 +
with message-id 
and subject line Bug#1068116: fixed in python-pylibdmtx 0.1.10-2
has caused the Debian Bug report #1068116,
regarding python-pylibdmtx: depends on pre-t64 packages
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.)


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

python3-pylibdtmtx depends on a package that was renamed for the time_t
64 transition. The dependency needs to be updated to the new package
name.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: python-pylibdmtx
Source-Version: 0.1.10-2
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-pylibdmtx 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, 19 Apr 2024 09:16:07 +0200
Source: python-pylibdmtx
Architecture: source
Version: 0.1.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1068116
Changes:
 python-pylibdmtx (0.1.10-2) unstable; urgency=medium
 .
   * Team upload.
   * Depends: s/libdmtx0b/libdmtx0t64/
 Closes: #1068116
   * Standards-Version: 4.7.0 (routine-update)
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
Checksums-Sha1:
 a20c31f031bec64114e95f970aa0dcffb3c8750d 2274 python-pylibdmtx_0.1.10-2.dsc
 6b111e1df653cfc1dfad1012cc8c7a45b716cb6a 5032 
python-pylibdmtx_0.1.10-2.debian.tar.xz
 5b3a12058d56b721cbfa83574fc16f5ee9ffa604 7891 
python-pylibdmtx_0.1.10-2_amd64.buildinfo
Checksums-Sha256:
 e7c7736d066138c400115e16095557e54f05d77a52e012bf5fd9645efb7bf9bc 2274 
python-pylibdmtx_0.1.10-2.dsc
 9bad2a91fb31bf7a60721e04ebaca84dfc14ed131e515140d1e343470502beb9 5032 
python-pylibdmtx_0.1.10-2.debian.tar.xz
 652065b49210867e830518bde114f949f1fb312d04caf5924cd36b76d8c592ea 7891 
python-pylibdmtx_0.1.10-2_amd64.buildinfo
Files:
 b30fc497eed2d1b325d65a741c48a036 2274 python optional 
python-pylibdmtx_0.1.10-2.dsc
 1a7432f42c2c65e279dc3190ed58f0eb 5032 python optional 
python-pylibdmtx_0.1.10-2.debian.tar.xz
 0783f1774822ae03df01aa5112d03148 7891 python optional 
python-pylibdmtx_0.1.10-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmYiGuERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHliQ//eitztRRl7GYPKU9GkIXBMd5HkDG7h4h/
JyeWmaHc1qZt3+PEyGVD9rz+VKwkMwc1407QbTsAfRLU+Dj14USD+FgA8luSDKy+
vSOFV52H6TYB8jcxUvzYv3YCehs0+TOTVhUMXJJRmtlBE9cNybyJ/ud/WZdgBddW
ss8lUCZusVg8rTtG3C8uMMfRyE34GoPWcmDrrO/B4LzlI++KWeouRv0tFfnD2S01
MYHVkGK9AY05BwIdk6YDi4hpyvtkPDn0FnUV85vhiUUUOqVRHvBXf/evYF1f4gMy
+78iOBgitni2+8Yiwo+oSeTYwP9fzw8U+MxnvdvZMFKGVTcj+g0BNdvixPztfCyP
ACuJhZIPFuLKeJ8mjs5OsdIt12l1/WGsUE5F1IyITCato3X0BO6cUVE/00o8hLcP
YWm/gWtAz3lFm894719jd+9hrraNAHgCAc123cl0HEGoe7BegLLRjsRUUlipvAp3
1XgvxMAX5bJVmhkgjKh1Saw2Rg5GhL0tx6+ooTKZez1kHVEvVamLJHsdVaMBc0IF
uFWJ5bOtnU2rlpC/onXxXlVbu9qKY02Zz7h9OZ4E08xcpPDh5M4Jf31k2MaSP4yK
ZddPYpV9fhZF/8kDugZlNPe1HST4ixMsjc+4LwTlL9i/hqALSwFHgmIG8AVMTq+a
9QIY+FRf2V8=
=Wvr1
-END PGP SIGNATURE-



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

Processed: bookworm-pu: package pdudaemon/0.0.8.58.g597052b-1+deb12u1

[Debian Bug Tracking System]

Processing control commands:

> block 1060768 with -1
Bug #1060768 {Done: Sjoerd Simons } [pdudaemon] pdudaemon: 
Missing dependency on python3-aiohttp
1060768 was not blocked by any bugs.
1060768 was not blocking any bugs.
Added blocking bug(s) of 1060768: 1069274
> affects -1 + src:pdudaemon
Bug #1069274 [release.debian.org] bookworm-pu: package 
pdudaemon/0.0.8.58.g597052b-1+deb12u1
Added indication that 1069274 affects src:pdudaemon

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

Bug#1069202: marked as done (gpg-sq: gpg-from-sq diverts /usr/bin/gpg but doesn't place a symlink pointing to gpg-sq)

[Debian Bug Tracking System]

Your message dated Fri, 19 Apr 2024 07:05:06 +
with message-id 
and subject line Bug#1069202: fixed in rust-sequoia-chameleon-gnupg 0.8.0-4
has caused the Debian Bug report #1069202,
regarding gpg-sq: gpg-from-sq diverts /usr/bin/gpg but doesn't place a symlink 
pointing to gpg-sq
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.)


-- 
1069202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpg-from-sq
Version: 0.8.0-1
Severity: grave
X-Debbugs-Cc: Daniel Kahn Gillmor 

I did:

 apt install gpg-from-sq

and i expected to run `gpg --version` and see the resultant info from
the chameleon.

Instead, i see:

bash: gpg: command not found

I'm seeing the same issue with gpg-from-sq version 0.8.0-1

--dkg

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

Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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)

Versions of packages gpg-sq depends on:
ii  libbz2-1.0  1.0.8-5.1
ii  libc6   2.37-15
ii  libgcc-s1   14-20240201-3
ii  libgmp102:6.3.0+dfsg-2+b1
ii  libhogweed6t64  3.9.1-2.2
ii  libnettle8t64   3.9.1-2.2
ii  libsqlite3-03.45.1-1
ii  libssl3t64  3.2.1-3

Versions of packages gpg-sq recommends:
ii  sq  0.33.0-3

gpg-sq suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: rust-sequoia-chameleon-gnupg
Source-Version: 0.8.0-4
Done: Holger Levsen 

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

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

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated 
rust-sequoia-chameleon-gnupg 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, 19 Apr 2024 08:46:04 +0200
Source: rust-sequoia-chameleon-gnupg
Architecture: source
Version: 0.8.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Holger Levsen 
Closes: 1069202
Changes:
 rust-sequoia-chameleon-gnupg (0.8.0-4) unstable; urgency=medium
 .
   * Fix ordering in gpg(v).links. Closes: #1069202.
   * Drop gpg(v)-from-sq.lintian-overrides.
Checksums-Sha1:
 d3c667b9355ccdd134e62b3193f8032bfe458d48 4116 
rust-sequoia-chameleon-gnupg_0.8.0-4.dsc
 ae1d5e317d4bf0a386b31db2bdab257f202bfae1 18332 
rust-sequoia-chameleon-gnupg_0.8.0-4.debian.tar.xz
 ddcb551bc49d3ff3d1b6a1357ae92fe74fe5384e 7658 
rust-sequoia-chameleon-gnupg_0.8.0-4_source.buildinfo
Checksums-Sha256:
 f640cf69a92ef03a2e946c915d0042b72722aa56f1114423ee64397873f5c797 4116 
rust-sequoia-chameleon-gnupg_0.8.0-4.dsc
 9c2cac444971f4eab61e3f704c5551190bfb6f0bd7c45796b80a0a62a6386ffc 18332 
rust-sequoia-chameleon-gnupg_0.8.0-4.debian.tar.xz
 06e6e3ff8eccb2adcae5eaf11379f70e3b15c54550f920309ecb51d8fad7ebbe 7658 
rust-sequoia-chameleon-gnupg_0.8.0-4_source.buildinfo
Files:
 9713e604f1dd93aa51f680bd6cb1ef20 4116 utils optional 
rust-sequoia-chameleon-gnupg_0.8.0-4.dsc
 504045e009073f9f598dea2a11bc543f 18332 utils optional 
rust-sequoia-chameleon-gnupg_0.8.0-4.debian.tar.xz
 10ca06a67c3eb761c504b11d6759645a 7658 utils optional 
rust-sequoia-chameleon-gnupg_0.8.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAmYiEzgSHGhvbGdlckBk
ZWJpYW4ub3JnAAoJEAkauFYGmqocPGcP/2vYb45cXUx+BImjDvWRWXR1/0weS31i
GbVXRDrE8bcum9GEUnOZYyJveq8leiHAz8MceisBJyad0ovE6oTKYgd2izYU8ZTl
ACttu8YEWv++eyA7ShYOu+kx5vJrl5HsEetjrMWYZ5GFLIHInxIc7UnsP/8lyLWj
45iGAMROY28C3BRK2i5FyoSksviLIh0iDpJXIqhbLGXh4kuQbqF6/rgqxeTWwgXF
YQVqNWYEfQikTKy3PRIQcWRvmTKSH7JSR/PnCp9ejkb1eD3nVi1mXWtx/LE4KrYR