Processed: limit source to gnustep-make, tagging 1057413

[Debian Bug Tracking System]

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

> limit source gnustep-make
Limiting to bugs with field 'source' containing at least one of 'gnustep-make'
Limit currently set to 'source':'gnustep-make'

> tags 1057413 + pending
Bug #1057413 [src:gnustep-make] FTBFS: dh_install: warning: gnustep-make-doc 
missing files: Documentation/gnustep-make.pdf
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1052763: libgnuastro18 has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libgnuastro_make.so

[Andreas Beckmann]

On Tue, 26 Sep 2023 20:54:29 +0200 Mohammad Akhlaghi 
 wrote:
Will this problem be fixed if we separate 'libgnuastro_make' as a 
separate package in 'debian/control'?


Given that this library is actually a plugin for GNU make, it would be 
useful to move it to separate package (e.g. libgnuatro-make-plugin, no 
SOVERSION in the name) since you need the unversioned name 
libgnuastro_make.so in the -plugin and not in the -dev package.


You would then need in the new package (assuming you introduce it in 
version 0.20-2):

  Breaks:   libgnuastro17 (<< 0.20), libgnuastro18 (<< 0.20-2~)
  Replaces: libgnuastro17 (<< 0.20), libgnuastro18 (<< 0.20-2~)

Andreas

Processed: raise severity of issues, filed for Python 3.12

[Debian Bug Tracking System]

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

> severity 1055576 serious
Bug #1055576 [src:meson-python] meson-python needs an update for Python 3.12
Severity set to 'serious' from 'important'
> user debian-pyt...@lists.debian.org
Setting user to debian-pyt...@lists.debian.org (was d...@debian.org).
> usertag 1041381 python3.12
There were no usertags set.
Usertags are now: python3.12.
> thanks
Stopping processing here.

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

Bug#1057443: sqlalchemy ftbfs with Python 3.12

[Matthias Klose]

Package: src:sqlalchemy
Version: 1.4.47+ds1-1
Severity: serious
Tags: sid trixie

sqlalchemy ftbfs with Python 3.12:

[...]
test/orm/test_eager_relations.py::InnerJoinSplicingWSecondaryTest_sqlite+pysqlite_3_44_2::test_joined_across 
Fatal Python error: Segmentation fault


Current thread 0x7f74c1526740 (most recent call first):
  File "/<>/lib/sqlalchemy/engine/default.py", line 736 in 
do_execute
  File "/<>/lib/sqlalchemy/engine/base.py", line 1900 in 
_execute_context
  File "/<>/lib/sqlalchemy/engine/base.py", line 1572 in 
_execute_clauseelement
  File "/<>/lib/sqlalchemy/sql/elements.py", line 334 in 
_execute_on_connection
  File "/<>/lib/sqlalchemy/engine/base.py", line 1705 in 
_execute_20
  File "/<>/lib/sqlalchemy/orm/session.py", line 1714 in 
execute

  File "/<>/lib/sqlalchemy/orm/query.py", line 2916 in _iter
  File "/<>/lib/sqlalchemy/orm/query.py", line 2773 in all
  File "/<>/test/orm/test_eager_relations.py", line 3654 in go
  File "/<>/lib/sqlalchemy/testing/assertions.py", line 
871 in assert_sql_execution
  File "/<>/lib/sqlalchemy/testing/assertions.py", line 
890 in assert_sql_count
  File "/<>/test/orm/test_eager_relations.py", line 3656 
in _assert_result
  File "/<>/test/orm/test_eager_relations.py", line 3678 
in test_joined_across
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 194 in 
pytest_pyfunc_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1792 in 
runtest
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 169 in 
pytest_runtest_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 

  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 341 in 
from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 261 in 
call_runtest_hook
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 222 in 
call_and_report
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 133 in 
runtestprotocol
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 114 in 
pytest_runtest_protocol
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 350 in 
pytest_runtestloop
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in 
__call__

  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 325 in _main
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 271 in 
wrap_session
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 318 in 
pytest_cmdline_main
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", 
line 169 in main
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", 
line 192 in console_main
  File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5 in 


  File "", line 88 in _run_code
  File "", line 198 in _run_module_as_main
Segmentation fault
make[1]: *** [debian/rules:20: override_dh_auto_install] Error 139

Bug#1057442: onboard ftbfs with Python 3.12

[Matthias Klose]

Package: src:onboard
Version: 1.4.1-5
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

onboard ftbfs with Python 3.12:

[...]
creating build
creating build/temp.linux-x86_64-cpython-312
creating build/temp.linux-x86_64-cpython-312/Onboard
creating build/temp.linux-x86_64-cpython-312/Onboard/osk
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 
-Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 
-ffile-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DMAJOR_VERSION=0 
-DMINOR_VERSION=4 -DMICRO_VERSION=0 -I/usr/include/blkid 
-I/usr/include/cairo -I/usr/include/cloudproviders -I/usr/include/dconf 
-I/usr/include/freetype2 -I/usr/include/fribidi 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 
-I/usr/include/glib-2.0 -I/usr/include/gtk-3.0 -I/usr/include/harfbuzz 
-I/usr/include/hunspell -I/usr/include/libmount -I/usr/include/libpng16 
-I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/webp 
-I/usr/include/x86_64-linux-gnu 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/python3.12 
-c Onboard/osk/osk_audio.c -o 
build/temp.linux-x86_64-cpython-312/Onboard/osk/osk_audio.o 
-Wsign-compare -Wdeclaration-after-statement 
-Werror=declaration-after-statement

In file included from /usr/include/python3.12/Python.h:44,
 from Onboard/osk/osk_module.h:25,
 from Onboard/osk/osk_audio.c:21:
/usr/include/python3.12/object.h: In function ‘Py_SIZE’:
/usr/include/python3.12/object.h:233:5: error: ISO C90 forbids mixed 
declarations and code [-Werror=declaration-after-statement]

  233 | PyVarObject *var_ob = _PyVarObject_CAST(ob);
  | ^~~
In file included from /usr/include/python3.12/Python.h:53:
/usr/include/python3.12/cpython/longintrepr.h: In function 
‘_PyLong_CompactValue’:
/usr/include/python3.12/cpython/longintrepr.h:121:5: error: ISO C90 
forbids mixed declarations and code [-Werror=declaration-after-statement]
  121 | Py_ssize_t sign = 1 - (op->long_value.lv_tag & 
_PyLong_SIGN_MASK);

  | ^~
Onboard/osk/osk_audio.c: In function ‘osk_audio_init_canberra’:
Onboard/osk/osk_audio.c:70:5: warning: ‘gdk_screen_get_number’ is 
deprecated [-Wdeprecated-declarations]

   70 | nr = gdk_screen_get_number(screen);
  | ^~
In file included from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31,
 from /usr/include/gtk-3.0/gdk/gdk.h:32,
 from /usr/include/gtk-3.0/gdk/gdkx.h:28,
 from Onboard/osk/osk_audio.c:23:
/usr/include/gtk-3.0/gdk/gdkscreen.h:56:14: note: declared here
   56 | gint gdk_screen_get_number(GdkScreen 
*screen);

  |  ^
Onboard/osk/osk_audio.c: In function ‘osk_audio_play’:
Onboard/osk/osk_audio.c:101:5: warning: ‘gdk_screen_get_width’ is 
deprecated [-Wdeprecated-declarations]

  101 | sw = gdk_screen_get_width(screen);
  | ^~
/usr/include/gtk-3.0/gdk/gdkscreen.h:58:14: note: declared here
   58 | gint gdk_screen_get_width (GdkScreen 
*screen);

  |  ^~~~
Onboard/osk/osk_audio.c:102:5: warning: ‘gdk_screen_get_height’ is 
deprecated [-Wdeprecated-declarations]

  102 | sh = gdk_screen_get_height(screen);
  | ^~
/usr/include/gtk-3.0/gdk/gdkscreen.h:60:14: note: declared here
   60 | gint gdk_screen_get_height(GdkScreen 
*screen);

  |  ^
cc1: some warnings being treated as errors
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:395: build: plugin distutils failed with: exit 
code=1: /usr/bin/python3.12 setup.py build

I: pybuild base:310: /usr/bin/python3 setup.py build

Bug#1052644: marked as done (kmscon FTBFS when systemd.pc changes systemdsystemunitdir)

[Debian Bug Tracking System]

Your message dated Tue, 05 Dec 2023 04:34:07 +
with message-id 
and subject line Bug#1052644: fixed in kmscon 9.0.0-5
has caused the Debian Bug report #1052644,
regarding kmscon FTBFS when systemd.pc changes systemdsystemunitdir
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.)


-- 
1052644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kmscon
Version: 9.0.0-4
Severity: normal
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. kmscon's upstream build system consumes this variable,
but the packaging hard codes the current value. When we change it,
kmscon will FTBFS. Consider applying the attached patch to avoid that
failure.

Helmut
diff -Nru kmscon-9.0.0/debian/changelog kmscon-9.0.0/debian/changelog
--- kmscon-9.0.0/debian/changelog   2023-01-29 20:19:17.0 +0100
+++ kmscon-9.0.0/debian/changelog   2023-09-25 15:59:39.0 +0200
@@ -1,3 +1,10 @@
+kmscon (9.0.0-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 25 Sep 2023 15:59:39 +0200
+
 kmscon (9.0.0-4) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru kmscon-9.0.0/debian/kmscon.install kmscon-9.0.0/debian/kmscon.install
--- kmscon-9.0.0/debian/kmscon.install  2023-01-29 20:07:23.0 +0100
+++ kmscon-9.0.0/debian/kmscon.install  2023-09-25 15:59:36.0 +0200
@@ -1,5 +1,5 @@
 debian/kmscon.conf etc/needrestart/conf.d
-lib/systemd/system/kmsconvt@.service
+${env:systemdsystemunitdir}/kmsconvt@.service
 usr/bin/kmscon
 usr/lib/${DEB_HOST_MULTIARCH}/kmscon/mod-*.so
 usr/libexec/kmscon/kmscon
diff -Nru kmscon-9.0.0/debian/not-installed kmscon-9.0.0/debian/not-installed
--- kmscon-9.0.0/debian/not-installed   2023-01-29 20:07:23.0 +0100
+++ kmscon-9.0.0/debian/not-installed   2023-09-25 15:59:39.0 +0200
@@ -1 +1 @@
-lib/systemd/system/kmscon.service
+${env:systemdsystemunitdir}/kmscon.service
diff -Nru kmscon-9.0.0/debian/rules kmscon-9.0.0/debian/rules
--- kmscon-9.0.0/debian/rules   2023-01-29 20:07:23.0 +0100
+++ kmscon-9.0.0/debian/rules   2023-09-25 15:59:39.0 +0200
@@ -6,7 +6,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS := qa=+bug hardening=+all reproducible=+all
 export DEB_CFLAGS_MAINT_APPEND := -Wno-error=array-bounds
-
+export systemdsystemunitdir = $(shell pkg-config 
--variable=systemdsystemunitdir systemd | sed s,^/,,)
 
 %:
dh $@ --without single-binary
--- End Message ---
--- Begin Message ---
Source: kmscon
Source-Version: 9.0.0-5
Done: Victor Westerhuis 

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

Debian distribution maintenance software
pp.
Victor Westerhuis  (supplier of updated kmscon 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: Mon, 04 Dec 2023 14:55:05 +0100
Source: kmscon
Architecture: source
Version: 9.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Victor Westerhuis 
Changed-By: Victor Westerhuis 
Closes: 1052644
Changes:
 kmscon (9.0.0-5) unstable; urgency=medium
 .
   * Stop using undocumented autoscripts in d/rules.
   * Use dh_builtusing to generate Built-Using dependency on unifont.
   * Fix FTBFS when systemd.pc changes systemdsystemunitdir.
 Thanks to Helmut Grohne. (Closes: 1052644)
Checksums-Sha1:
 58afa1847267274eb49906e8e1f39268f1002d38 2111 kmscon_9.0.0-5.dsc
 6628aee6f09a729ead8727871e2306003784514a 7812 kmscon_9.0.0-5.debian.tar.xz
 f7cfbe388c0c3feb670d29b567767770f837e62d 11285 kmscon_9.0.0-5_arm64.buildinfo
Checksums-Sha256:
 39e0697dfc0af11488bf9ab19c68bf299e497c0851a2b244713b3ea0b08cff4e 2111 
kmscon_9.0.0-5.dsc
 4d843aacfe9dd6bf5143ac3434ebe275c067027e2fdd1b1c18aac396ebabb7e6 7812 
kmscon_9.0.0-5.debian.tar.xz
 dbf476f20fc72404b58bd94c69fc3144dfc2007e39f3cc91d91b424e57b4add1 11285 
kmscon_9.0.0-5_arm64.buildinfo
Files:
 

Bug#1057437: pmix: FTBFS: dh_missing: error: missing files, aborting

[Chris Hofstaedtler]

Source: pmix
Version: 5.0.1-3
Severity: serious
Tags: ftbfs

Dear Maintainer,

your package FTBFS in unstable, in my own test rebuild as well as on 
reproducible-builds.org.

Build log snippet, hopefully relevant:
   dh_missing: warning: usr/lib/x86_64-linux-gnu/pmix2/local/bin/cygdb exists 
in debian/tmp but is not installed to anywhere 
   dh_missing: warning: usr/lib/x86_64-linux-gnu/pmix2/local/bin/cython exists 
in debian/tmp but is not installed to anywhere 
   dh_missing: warning: usr/lib/x86_64-linux-gnu/pmix2/local/bin/cythonize 
exists in debian/tmp but is not installed to anywhere 
   dh_missing: error: missing files, aborting
  The following debhelper tools have reported what they installed (with 
files per package)
  * dh_install: libpmix-bin (9), libpmix-dev (4), libpmix2 (35), 
python3-pmix (1)
  * dh_installdocs: libpmix-bin (0), libpmix-dev (3), libpmix2 (0), 
python3-pmix (0)
  * dh_installexamples: libpmix-bin (0), libpmix-dev (27), libpmix2 (0), 
python3-pmix (0)
  * dh_installman: libpmix-bin (0), libpmix-dev (5), libpmix2 (0), 
python3-pmix (0)
  If the missing files are installed by another tool, please file a bug 
against it.
  When filing the report, if the tool is not part of debhelper itself, 
please reference the
  "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for 
debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.md.gz)
  Be sure to test with dpkg-buildpackage -A/-B as the results may vary when 
only a subset is built
  If the omission is intentional or no other helper can take care of this 
consider adding the
  paths to debian/not-installed.

  Remember to be careful with paths containing "x86_64-linux-gnu", where 
you might need to
  use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in 
debian/not-installed
  to ensure it works on all architectures (see #961104).
   make: *** [debian/rules:36: binary] Error 25
   dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Full build log attached.
rbo build log here:
   
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/pmix_5.0.1-3.rbuild.log.gz

Best,
Chris



pmix_5.0.1-3.gz
Description: application/gzip

Bug#1057436: ovn: FTBFS: tar (child): /usr/src/openvswitch/openvswitch.tar.gz: Cannot open: No such file or directory

[Chris Hofstaedtler]

Source: ovn
Version: 23.09.0-1
Severity: serious
Tags: ftbfs

Dear Maintainer,

your package FTBFS in unstable, in my own test rebuild as well as on 
reproducible-builds.org.

Build log snippet, hopefully relevant:
   cd ovs && tar -xzf /usr/src/openvswitch/openvswitch.tar.gz 
--strip-components=1
   tar (child): /usr/src/openvswitch/openvswitch.tar.gz: Cannot open: No such 
file or directory
   tar (child): Error is not recoverable: exiting now
   tar: Child returned status 2
   tar: Error is not recoverable: exiting now
   make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2
   make[1]: Leaving directory '/<>'
   make: *** [debian/rules:7: binary] Error 2
   dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2

Full build log attached.
rbo build log here:
   
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/ovn_23.09.0-1.rbuild.log.gz

Best,
Chris

sbuild (Debian sbuild) 0.85.0 (04 January 2023) on cl.home.zeha.at

+==+
| ovn 23.09.0-1 (amd64)Mon, 04 Dec 2023 02:42:26 + |
+==+

Package: ovn
Version: 23.09.0-1
Source Version: 23.09.0-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

Unpacking /home/ch/.cache/sbuild/unstable-amd64.tar to 
/srv/scratch/sbuild/tmp.sbuild.u2WtD4AYK6...
I: NOTICE: Log filtering will replace 'sbuild-unshare-dummy-location' with 
'<>'
I: NOTICE: Log filtering will replace 'build/ovn-XaBoeO/resolver-0rgGjP' with 
'<>'

+--+
| Update chroot|
+--+

Get:1 http://172.16.172.24/debian unstable InRelease [198 kB]
Get:2 http://deb.debian.org/debian unstable InRelease [198 kB]
Ign:3 http://172.16.172.24/debian unstable/non-free amd64 Packages
Ign:4 http://172.16.172.24/debian unstable/contrib amd64 Packages
Ign:5 http://172.16.172.24/debian unstable/main amd64 Packages
Ign:6 http://172.16.172.24/debian unstable/non-free-firmware amd64 Packages
Get:3 http://172.16.172.24/debian unstable/non-free amd64 Packages [123 kB]
Get:4 http://172.16.172.24/debian unstable/contrib amd64 Packages [66.0 kB]
Get:5 http://172.16.172.24/debian unstable/main amd64 Packages [9596 kB]
Get:6 http://172.16.172.24/debian unstable/non-free-firmware amd64 Packages 
[6364 B]
Get:7 http://deb.debian.org/debian unstable/contrib Sources [60.8 kB]
Get:8 http://deb.debian.org/debian unstable/non-free-firmware Sources [6548 B]
Get:9 http://deb.debian.org/debian unstable/non-free Sources [85.1 kB]
Get:10 http://deb.debian.org/debian unstable/main Sources [10.3 MB]
Fetched 20.7 MB in 7s (2851 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  binutils binutils-common binutils-x86-64-linux-gnu cpp-13 g++-13 gcc-13
  gcc-13-base libasan8 libatomic1 libbinutils libcc1-0 libctf-nobfd0 libctf0
  libgcc-13-dev libgcc-s1 libgomp1 libgprofng0 libhwasan0 libitm1 liblsan0
  libquadmath0 libsframe1 libstdc++-13-dev libstdc++6 libsystemd0 libtsan2
  libubsan1 libudev1
28 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 61.5 MB of archives.
After this operation, 173 kB of additional disk space will be used.
Get:1 http://172.16.172.24/debian unstable/main amd64 libcc1-0 amd64 13.2.0-8 
[43.0 kB]
Get:2 http://172.16.172.24/debian unstable/main amd64 libgprofng0 amd64 
2.41.50.20231202-1 [769 kB]
Get:3 http://172.16.172.24/debian unstable/main amd64 libctf0 amd64 
2.41.50.20231202-1 [87.1 kB]
Get:4 http://172.16.172.24/debian unstable/main amd64 libctf-nobfd0 amd64 
2.41.50.20231202-1 [151 kB]
Get:5 http://172.16.172.24/debian unstable/main amd64 binutils-x86-64-linux-gnu 
amd64 2.41.50.20231202-1 [2234 kB]
Get:6 http://172.16.172.24/debian unstable/main amd64 libbinutils amd64 
2.41.50.20231202-1 [515 kB]
Get:7 http://172.16.172.24/debian unstable/main amd64 binutils-common amd64 
2.41.50.20231202-1 [2537 kB]
Get:8 http://172.16.172.24/debian unstable/main amd64 binutils amd64 
2.41.50.20231202-1 [80.1 kB]
Get:9 http://172.16.172.24/debian unstable/main amd64 libgomp1 amd64 13.2.0-8 
[131 kB]
Get:10 http://172.16.172.24/debian unstable/main amd64 libitm1 amd64 13.2.0-8 
[26.1 kB]
Get:11 http://172.16.172.24/debian unstable/main amd64 libatomic1 amd64 
13.2.0-8 [9304 B]
Get:12 http://172.16.172.24/debian unstable/main amd64 libasan8 amd64 13.2.0-8 
[2558 kB]
Get:13 http://172.16.172.24/debian unstable/main amd64 liblsan0 amd64 13.2.0-8 
[1102 kB]
Get:14 http://172.16.172.24/debian unstable/main amd64 libtsan2 amd64 13.2.0-8 
[2334 kB]
Get:15 

Bug#1057434: libreoffice-numbertext 1.0.11-3 is broken; 1.0.10-1 works as expected

[Alexandre Bonneau]

Package: libreoffice-numbertext
Version: 1.0.11-3
Severity: grave

When trying to use the =NUMBERTEXT(5) formula in Libreoffice Calc, you get an 
'Err: 504' error in those cells.

When reverting back to libreoffice-numbertext 1.0.10-1, all the functions using 
the NUMBERTEXT function are correctly parsed.

The package libreoffice-numbertext 1.0.11-3 is broken, when using Debian Trixie 
and Libreoffice 4:7.5.9~rc1-1.

Regards,
Alexandre Bonneau

Bug#1051166: FTBFS with doxygen 1.9.8

[Bastian Germann]

Please note that this issue keeps doxygen from migrating to testing, which in 
turn keeps llvm-toolchain-14 in the key packages and from being removed.

Bug#1057428: libseccomp ftbfs on i386

[Felix Geyer]

On 04.12.23 22:03, Matthias Klose wrote:

Package: src:libseccomp
Version: 2.5.4-2
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

libseccomp ftbfs on i386. probably not related to Python 3.12, but blocks the 
addition of Python 3.12


Seems like glibc 2.37-13 broke valgrind on i386:
https://ci.debian.net/packages/v/valgrind/testing/i386/40527816/

Processed: severity of 1055575 is serious

[Debian Bug Tracking System]

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

> severity 1055575 serious
Bug #1055575 [src:gst-python1.0] gst-python1.0 ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1057430: ring: FTBFS: configure: error: sdbus-c++ not found

[Sebastian Ramacher]

Source: ring
Version: 20230922.0~ds2-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=ring=amd64=20230922.0%7Eds2-1%2Bb1=1701601320=0

checking for zlib... yes
checking for libgit2 >= 1.1.0... yes
checking for libpjproject... yes
checking for yaml-cpp >= 0.5.1... yes
checking for yaml-cpp >= 0.5.1... yes
checking for jsoncpp >= 1.6.5... yes
checking for alsa >= 1.0... yes
checking for libpulse >= 0.9.15... yes
checking for jack... no
checking for sdbus-c++... no
configure: error: sdbus-c++ not found
make[1]: *** [debian/rules:31: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'

Cheers
-- 
Sebastian Ramacher

Bug#1057391: cinnamon: FTBFS: dh_girepository: error: Could not find Clutter-0.gir dependency

[Fabio Fantoni]

Il 04/12/2023 22:14, Holger Schröder ha scritto:



The same thing happens when you try to build Cinnamon 6.0.0


https://github.com/linuxmint/cinnamon


/hsp


Is not related to cinnamon itself but to latest gobject-introspection 
changes in sid/testing


I don't know what is the good way to fix it, a possibile workaround I 
suppose is add provide for each gir but it doesn't seem like a good idea 
add 6 provides in a muffin package


I'll try to see if someone recommend something better, otherwise I'll 
try anyway






OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1057338: marked as done (sddm FTBFS: systemd.pc moved the upstream unit to /usr)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 21:36:29 +
with message-id 
and subject line Bug#1057338: fixed in sddm 0.20.0-2
has caused the Debian Bug report #1057338,
regarding sddm FTBFS: systemd.pc moved the upstream unit to /usr
to be marked as done.

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

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


-- 
1057338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sddm
Version: 0.20.0-1
Severity: serious
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

Hi,

I'm sorry for having noticed this late. When we changed the way
systemd.pc places systemd units, we did a partial archive rebuild and
missed out on sddm. On Nov 30th, the changed systemd was uploaded and
ssdm FTBFS since. The upstream unit is now installed to /usr, which
makes debian/rules fail to delete it and this trips up dh_missing. I've
got a patch for you to delete both locations for now. You may delete the
old location once you are sure that you don't want to backport to
bookworm anymore.

Helmut
diff --minimal -Nru sddm-0.20.0/debian/changelog sddm-0.20.0/debian/changelog
--- sddm-0.20.0/debian/changelog2023-06-24 08:38:52.0 +0200
+++ sddm-0.20.0/debian/changelog2023-12-03 07:36:33.0 +0100
@@ -1,3 +1,10 @@
+sddm (0.20.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS: Also ignore /usr-moved upstream systemd unit. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 03 Dec 2023 07:36:33 +0100
+
 sddm (0.20.0-1) unstable; urgency=medium
 
   [ Aurélien COUDERC ]
diff --minimal -Nru sddm-0.20.0/debian/rules sddm-0.20.0/debian/rules
--- sddm-0.20.0/debian/rules2023-02-20 22:44:19.0 +0100
+++ sddm-0.20.0/debian/rules2023-12-03 07:36:31.0 +0100
@@ -30,7 +30,7 @@
 
 execute_after_dh_auto_install:
# not installed, as the Debian version is used instead
-   rm -f $(CURDIR)/debian/tmp/lib/systemd/system/sddm.service
+   rm -f $(CURDIR)/debian/tmp/lib/systemd/system/sddm.service 
$(CURDIR)/debian/tmp/usr/lib/systemd/system/sddm.service
 
 execute_after_dh_fixperms-arch:
# ensure script is marked as executable
--- End Message ---
--- Begin Message ---
Source: sddm
Source-Version: 0.20.0-2
Done: Patrick Franz 

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

Debian distribution maintenance software
pp.
Patrick Franz  (supplier of updated sddm 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: Mon, 04 Dec 2023 22:08:35 +0100
Source: sddm
Architecture: source
Version: 0.20.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Patrick Franz 
Closes: 1057338
Changes:
 sddm (0.20.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Pino Toscano ]
   * Add the xkb-data dependency, needed for the X11 xkb rules.
   * Remove an obsolete maintscript entry.
 .
   [ Patrick Franz ]
   * Fix FTBFS: Also ignore /usr-moved upstream systemd unit, thx to
 Helmut Grohne (Closes: #1057338).
Checksums-Sha1:
 3cf454284a6d55e38b9cc9d079b46424bdaae01b 2653 sddm_0.20.0-2.dsc
 f398bc0a325a6e6f8c75e97acac6f9337cd586db 58560 sddm_0.20.0-2.debian.tar.xz
 aebd56dc56ed174ee21db7fffc1ad3ecd9c2aaa5 13175 sddm_0.20.0-2_source.buildinfo
Checksums-Sha256:
 63c0e800e64d8bab31cf04288a22289e1a78ed355435b6b17e9f33810a962390 2653 
sddm_0.20.0-2.dsc
 e9b32fe2a616a3c910d1dea5d9bed2a190e9725aee85ab3f51279f2c26c95416 58560 
sddm_0.20.0-2.debian.tar.xz
 7be14d7077829e1e64d50e159b0b2c54456c934f05e78b02656da5f31aad9d2f 13175 
sddm_0.20.0-2_source.buildinfo
Files:
 78a985018b8a0c306d5b99ded7a57a55 2653 kde optional sddm_0.20.0-2.dsc
 d1a5221197090ff1f820d59cd75135cc 58560 kde optional sddm_0.20.0-2.debian.tar.xz
 bd2dc502c9a3bcee5ada6473eaabbd77 13175 kde optional 
sddm_0.20.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmVuQBQACgkQnp96YDB3
/lbWIA/8D4DgSghcPaA1BcpM0NGiMieh6+VZfcON5xmEHfh9Sq3p5WGQ1re6rBVC
0ZVvYK3WsktewGzzHWcx/yQZmWjWi912dw57Ph8038o6vB4TzxY5lwR21IOK7FEd

Bug#1057391: cinnamon: FTBFS: dh_girepository: error: Could not find Clutter-0.gir dependency

[Holger Schröder]

The same thing happens when you try to build Cinnamon 6.0.0


https://github.com/linuxmint/cinnamon


/hsp

Bug#1057424: libmodule-build-perl: Multi-Arch: foreign makes other packages FTBFS

[gregor herrmann]

On Mon, 04 Dec 2023 21:59:12 +0200, Niko Tyni wrote:

> The libnet-cidr-set-perl and libparams-validate-perl packages
> fail to build from source in current unstable.

> This is because libmodule-build-perl was recently marked
> Multi-Arch:foreign, but dpkg-checkbuilddeps does not consider that as
> satisfying :native build dependencies, see #1023438.

Oh dear :/
(I added Multi-Arch:foreign because I wanted to cross-build a
package, and I already had the gut feeling that his might be
dangerous …)
 
> My understanding is that M-A:foreign is probably the right thing
> to do here, but we need to remove the :native build dependency
> in other packages first. Fortunately I see only two in the archive,
> libnet-cidr-set-perl and libparams-validate-perl.
> 
>   grep-dctrl -sPackage,Build-Depends,Build-Depends-Indep 
> -FBuild-Depends,Build-Depends-Indep -r 'libmodule-build-perl[^,]*:native' 
> /var/lib/apt/lists/*_main_source_Sources

Thanks for this research!
 
> Filing against libmodule-build-perl for now to prevent it from entering
> trixie before the other two are changed. Feel free to reassign or clone
> or whatever if you like.

Both fixed (by removing the :native) and uploaded.

I guess we could upload libmodule-build-perl with versioned Breaks on
the 2 packages (and close this bug with the upload) to get the
migration/upgrade order right?
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1057428: libseccomp ftbfs on i386

[Matthias Klose]

Package: src:libseccomp
Version: 2.5.4-2
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

libseccomp ftbfs on i386. probably not related to Python 3.12, but 
blocks the addition of Python 3.12


[...]
Test 59-basic-empty_binary_tree%%001-00351 result:   SUCCESS
 test mode:  c
 test type:  bpf-valgrind
./regression: line 271: 1444558 Illegal instruction valgrind 
--tool=memcheck --error-exitcode=1 --leak-check=full --read-var-info=yes 
--track-origins=yes --suppressions=./valgrind_test.supp --quiet 
--log-fd=4 -- ./59-basic-empty_binary_tree -b
Test 59-basic-empty_binary_tree%%002-1 result:   FAILURE 
59-basic-empty_binary_tree rc=132

Regression Test Summary
 tests run: 8570
 tests skipped: 78
 tests passed: 8533
 tests failed: 37
 tests errored: 0

FAIL: regression
==
1 of 1 test failed
==
make[3]: *** [Makefile:1424: check-TESTS] Error 1

Processed: Re: Bug#1052349: bolt FTBFS when systemdsystemunitdir changes in systemd.pc or udevdir changes in udev.pc

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1052349 [src:bolt] bolt FTBFS when systemdsystemunitdir changes in 
systemd.pc or udevdir changes in udev.pc
Severity set to 'serious' from 'important'

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

Processed: raising severity of python3.12 build issue

[Debian Bug Tracking System]

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

> severity 1055498 serious
Bug #1055498 [src:python-greenlet] greenlet needs an update to 3.x to support 
Python 3.12
Ignoring request to change severity of Bug 1055498 to the same value.
> thanks
Stopping processing here.

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

Processed: libmodule-build-perl: Multi-Arch: foreign makes other packages FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 libnet-cidr-set-perl libparams-validate-perl
Bug #1057424 [libmodule-build-perl] libmodule-build-perl: Multi-Arch: foreign 
makes other packages FTBFS
Added indication that 1057424 affects libnet-cidr-set-perl and 
libparams-validate-perl
> block 1055955 with -1
Bug #1055955 [release.debian.org] transition: perl 5.38
1055955 was blocked by: 1050451 1042525 1040396 1042844 1054793 1057318 1042853 
1057270 1042521 1042845 1054776
1055955 was not blocking any bugs.
Added blocking bug(s) of 1055955: 1057424

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

Bug#1057424: libmodule-build-perl: Multi-Arch: foreign makes other packages FTBFS

[Niko Tyni]

Package: libmodule-build-perl
Version: 0.423400-2
Severity: serious
Tags: ftbfs
Control: affects -1 libnet-cidr-set-perl libparams-validate-perl
X-Debbugs-Cc: debian-cr...@lists.debian.org
Control: block 1055955 with -1

The libnet-cidr-set-perl and libparams-validate-perl packages
fail to build from source in current unstable.

>From a full build log at

 
http://perl.debian.net/rebuild-logs/sid/libparams-validate-perl_1.31-1/libparams-validate-perl_1.31-1.buildlog

  Command: dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -Zxz
  dpkg-buildpackage: info: source package libparams-validate-perl
  dpkg-buildpackage: info: source version 1.31-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by gregor herrmann 
   dpkg-source -Zxz --before-build .
  dpkg-buildpackage: info: host architecture amd64
  dpkg-checkbuilddeps: error: Unmet build dependencies: 
libmodule-build-perl:native
  dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
  dpkg-buildpackage: warning: (Use -d flag to override.)
 
This is because libmodule-build-perl was recently marked
Multi-Arch:foreign, but dpkg-checkbuilddeps does not consider that as
satisfying :native build dependencies, see #1023438.

My understanding is that M-A:foreign is probably the right thing
to do here, but we need to remove the :native build dependency
in other packages first. Fortunately I see only two in the archive,
libnet-cidr-set-perl and libparams-validate-perl.

  grep-dctrl -sPackage,Build-Depends,Build-Depends-Indep 
-FBuild-Depends,Build-Depends-Indep -r 'libmodule-build-perl[^,]*:native' 
/var/lib/apt/lists/*_main_source_Sources

Filing against libmodule-build-perl for now to prevent it from entering
trixie before the other two are changed. Feel free to reassign or clone
or whatever if you like.

As libparams-validate-perl is an arch:any XS module, we need to fix it
one way or another before the Perl 5.38 transition. So marking this as
a blocker.

Copying the debian-cross list in case I got something wrong :)
-- 
Niko Tyni   nt...@debian.org

Bug#1057421: sysstat: FTBFS: dh_install: warning: Cannot find (any matches for) "debian/tmp/lib/systemd/" (tried in ., debian/tmp)

[Chris Hofstaedtler]

Source: sysstat
Version: 12.6.1-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

systemd.pc changed systemd_system_unit_dir to point to /usr. As a
consequence, your package now FTBFS in unstable. Due to a human
mistake this problem was not caught before making the change; we'd
like to apologize.

FTBFS log snippet:
>> if [ -n "/usr/lib/systemd/system" -a -n "/usr/lib/systemd/system-sleep" -a 
>> -d "/<>/debian/tmp/usr/lib/systemd/system-sleep" ]; then \
>>  install -m 755 cron/sysstat.sleep 
>> /<>/debian/tmp/usr/lib/systemd/system-sleep; \
>> fi
>> make[2]: Leaving directory '/<>'
>> mv /<>/debian/tmp/usr/bin/sar 
>> /<>/debian/tmp/usr/bin/sar.sysstat
>> mv /<>/debian/tmp/usr/share/man/man1/sar.1 
>> /<>/debian/tmp/usr/share/man/man1/sar.sysstat.1
>> rm -rf /<>/debian/tmp/usr/doc
>> make[1]: Leaving directory '/<>'
>>dh_install
>> dh_install: warning: Cannot find (any matches for) "debian/tmp/lib/systemd/" 
>> (tried in ., debian/tmp)
>> 
>> dh_install: warning: sysstat missing files: debian/tmp/lib/systemd/
>> dh_install: error: missing files, aborting
>> make: *** [debian/rules:23: binary] Error 25
>> dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
>> status 2


It seems likely you'll need to adapt a debhelper .install file for
the /usr path.

Note: if you intend to backport your package to bookworm or earlier,
please revert any changes for moving to /usr.

Best,
Chris



sysstat_12.6.1-1.gz
Description: application/gzip

Bug#1057420: cfengine3: FTBFS: dh_install: warning: cfengine3 missing files: debian/tmp/lib/systemd

[Chris Hofstaedtler]

Source: cfengine3
Version: 3.21.0-3
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

systemd.pc changed systemd_system_unit_dir to point to /usr. As a
consequence, your package now FTBFS in unstable. Due to a human
mistake this problem was not caught before making the change; we'd
like to apologize.

FTBFS log snippet:
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install --exclude=examples --exclude=ChangeLog
dh_install: warning: Cannot find (any matches for)
"debian/tmp/lib/systemd" (tried in ., debian/tmp)

dh_install: warning: cfengine3 missing files: debian/tmp/lib/systemd
dh_install: error: missing files, aborting
make[1]: *** [debian/rules:70: override_dh_install] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:16: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess
returned exit status 2


It seems likely you'll need to adapt a debhelper .install file for
the /usr path.

Note: if you intend to backport your package to bookworm or earlier,
please revert any changes for moving to /usr.

Best,
Chris



cfengine3_3.21.0-3.gz
Description: application/gzip

Processed: severity of 1055498 is serious

[Debian Bug Tracking System]

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

> severity 1055498 serious
Bug #1055498 [src:python-greenlet] greenlet needs an update to 3.x to support 
Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1057205: The fedora 39 builds using the works on ppc64le

[William Cohen]

Hi,

I have noticed a similar problem on riscv64 openSUSE Tumbleweed 
(gcc13-13.2.1+git7813-6.2.riscv64), but everything builds fine on all the 
fedora 39 and rawhide architectures.  These builds include ppc64le.

fedora 39: https://koji.fedoraproject.org/koji/buildinfo?buildID=2321551
fedora rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=2321548

I don't know what the difference are between the ppc64le Debian and Fedora 
environments, but that would be a starting point to to figure out why systemtap 
isn't compiling on Debian.

-Will Cohen

Bug#1054941: marked as done (haskell-repa: FTBFS: unsatisfiable build-dependency: libghc-vector-dev (< 0.13) but 0.13.1.0-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 18:28:53 +
with message-id 
and subject line Bug#1057294: Removed package(s) from unstable
has caused the Debian Bug report #1054941,
regarding haskell-repa: FTBFS: unsatisfiable build-dependency: 
libghc-vector-dev (< 0.13) but 0.13.1.0-1 is to be installed
to be marked as done.

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

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


-- 
1054941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-repa
Version: 3.4.1.5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 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: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-quickcheck2-dev (>= 2.8), 
> libghc-quickcheck2-dev (<< 2.15), libghc-quickcheck2-prof, libghc-vector-dev 
> (<< 0.13), libghc-vector-dev (>= 0.11), libghc-vector-prof, build-essential, 
> fakeroot, ghc-doc, libghc-quickcheck2-doc, libghc-vector-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-quickcheck2-dev (>= 2.8), 
> libghc-quickcheck2-dev (<< 2.15), libghc-quickcheck2-prof, libghc-vector-dev 
> (<< 0.13), libghc-vector-dev (>= 0.11), libghc-vector-prof, build-essential, 
> fakeroot, ghc-doc, libghc-quickcheck2-doc, libghc-vector-doc
> 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 [911 B]
> Get:5 copy:/<>/apt_archive ./ Packages [923 B]
> Fetched 2443 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libghc-vector-dev (< 0.13) but 
> 0.13.1.0-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/10/28/haskell-repa_3.4.1.5-1_unstable.log

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

Dear submitter,

as the package haskell-repa 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/1057294

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

Bug#1054495: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 18:28:53 +
with message-id 
and subject line Bug#1057294: Removed package(s) from unstable
has caused the Debian Bug report #1054495,
regarding Removal notice: obsolete
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.)


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

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 3.4.1.5-1+rm

Dear submitter,

as the package haskell-repa 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/1057294

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 18:27:47 +
with message-id 
and subject line Bug#1057293: Removed package(s) from unstable
has caused the Debian Bug report #1054868,
regarding haskell-syb-with-class: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 25
to be marked as done.

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

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


-- 
1054868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-syb-with-class
Version: 0.6.1.14-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


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


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/haskell-syb-with-class_0.6.1.14-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 0.6.1.14-1+rm

Dear submitter,

as the package haskell-syb-with-class has just been removed 

Bug#1054942: marked as done (haskell-parallel-tree-search: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, haddock-interface-38, libghc-base-prof-4.15.1.0-6a406)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 18:27:22 +
with message-id 
and subject line Bug#1057292: Removed package(s) from unstable
has caused the Debian Bug report #1054942,
regarding haskell-parallel-tree-search: FTBFS: unsatisfiable 
build-dependencies: libghc-base-dev-4.15.1.0-6a406, haddock-interface-38, 
libghc-base-prof-4.15.1.0-6a406
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.)


-- 
1054942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-parallel-tree-search
Version: 0.4.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts (>= 0.8), cdbs, 
> ghc, ghc-prof, libghc-parallel-dev, libghc-parallel-prof, 
> libghc-tree-monad-dev (>= 0.3.1), libghc-tree-monad-prof (>= 0.3.1), 
> build-essential, fakeroot, ghc-doc, libghc-parallel-doc, libghc-tree-monad-doc
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts (>= 0.8), cdbs, 
> ghc, ghc-prof, libghc-parallel-dev, libghc-parallel-prof, 
> libghc-tree-monad-dev (>= 0.3.1), libghc-tree-monad-prof (>= 0.3.1), 
> build-essential, fakeroot, ghc-doc, libghc-parallel-doc, libghc-tree-monad-doc
> 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 [846 B]
> Get:5 copy:/<>/apt_archive ./ Packages [858 B]
> Fetched 2313 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 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:
>  libghc-tree-monad-dev : Depends: libghc-base-dev-4.15.1.0-6a406 but it is 
> not installable
>  libghc-tree-monad-doc : Depends: haddock-interface-38 but it is not 
> installable
>  libghc-tree-monad-prof : Depends: libghc-base-prof-4.15.1.0-6a406 but it is 
> not installable
> 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/10/28/haskell-parallel-tree-search_0.4.2-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231028;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231028=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 ---
Version: 0.4.2-2+rm

Dear submitter,

as the package haskell-parallel-tree-search 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/1057292

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 

Bug#1054826: marked as done (haskell-numtype: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 18:26:51 +
with message-id 
and subject line Bug#1057291: Removed package(s) from unstable
has caused the Debian Bug report #1054826,
regarding haskell-numtype: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-numtype-doc.substvars
> dh_installdirs -plibghc-numtype-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.lhs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.lhs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe'
> Running find . ! -newer /tmp/IaqP7H8z0z -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-numtype-dev
> libghc-numtype-prof
> libghc-numtype-doc
> Running dh_listpackages
> libghc-numtype-dev
> libghc-numtype-prof
> libghc-numtype-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/numtype-1.2/ --datasubdir=numtype 
> --htmldir=/usr/share/doc/libghc-numtype-doc/html/ --enable-library-profiling
> Using Parsec parser
> Configuring numtype-1.2...
> Dependency base <5: using base-4.17.2.0
> Source component graph: component lib
> Configured component graph:
> component numtype-1.2-1TzeWrAXQ9qDnL7XMQvuDI include base-4.17.2.0
> Linked component graph:
> unit numtype-1.2-1TzeWrAXQ9qDnL7XMQvuDI
> include base-4.17.2.0
> Numeric.NumType=numtype-1.2-1TzeWrAXQ9qDnL7XMQvuDI:Numeric.NumType
> Ready component graph:
> definite numtype-1.2-1TzeWrAXQ9qDnL7XMQvuDI depends base-4.17.2.0
> Using Cabal-3.8.1.0 compiled by ghc-9.4
> Using compiler: ghc-9.4.7
> Using install prefix: /usr
> Executables installed in: /usr/bin
> Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-9.4.7/numtype-1.2-1TzeWrAXQ9qDnL7XMQvuDI
> Dynamic Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-9.4.7
> Private executables installed in: /usr/lib/x86_64-linux-ghc-9.4.7/numtype-1.2
> Data files installed in: /usr/share/numtype
> Documentation installed in: /usr/share/doc/x86_64-linux-ghc-9.4.7/numtype-1.2
> Configuration files installed in: /usr/etc
> No alex found
> Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
> No c2hs found
> No cpphs found
> No doctest found
> Using gcc version 13 found on system at: /usr/bin/x86_64-linux-gnu-gcc
> Using ghc version 9.4.7 found on system at: /usr/bin/ghc
> Using ghc-pkg version 9.4.7 found on system at: /usr/bin/ghc-pkg-9.4.7
> No ghcjs found
> No ghcjs-pkg found
> No greencard found
> Using haddock version 2.27.0 found on system at: /usr/bin/haddock-ghc-9.4.7
> No happy found
> Using haskell-suite found on system at: haskell-suite-dummy-location
> Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
> No hmake found
> Using hpc version 0.68 found on system at: /usr/bin/hpc-ghc-9.4.7
> Using hsc2hs version 0.68.8 found on system at: /usr/bin/hsc2hs-ghc-9.4.7
> Using hscolour version 1.24 found on system at: /usr/bin/HsColour
> No jhc found
> Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
> No pkg-config found
> Using runghc version 9.4.7 found on system at: /usr/bin/runghc-9.4.7
> Using strip version 2.41 found on system at: /usr/bin/strip
> Using tar found on system at: /bin/tar
> No uhc found
> touch configure-ghc-stamp
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'build_recipe'
> Running 

Bug#1054317: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 18:26:51 +
with message-id 
and subject line Bug#1057291: Removed package(s) from unstable
has caused the Debian Bug report #1054317,
regarding Removal notice: obsolete
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.)


-- 
1054317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-numtype
Version: 1.2-7
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS with GHC 9.4
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 1.2-7+rm

Dear submitter,

as the package haskell-numtype 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/1057291

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1054355: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 18:27:22 +
with message-id 
and subject line Bug#1057292: Removed package(s) from unstable
has caused the Debian Bug report #1054355,
regarding Removal notice: obsolete
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.)


-- 
1054355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-parallel-tree-search
Version: 0.4.2-2
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 3 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.4.2-2+rm

Dear submitter,

as the package haskell-parallel-tree-search 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/1057292

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1054318: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 18:27:47 +
with message-id 
and subject line Bug#1057293: Removed package(s) from unstable
has caused the Debian Bug report #1054318,
regarding Removal notice: obsolete
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.)


-- 
1054318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-syb-with-class
Version: 0.6.1.14-1
Severity: serious

I intend to remove this package:

  * The current version FTBFS with GHC 9.4
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.6.1.14-1+rm

Dear submitter,

as the package haskell-syb-with-class 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/1057293

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.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1057381: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’

[Sven Joachim]

Control: tags -1 + trixie sid patch

On 2023-12-04 10:38 +0100, Chris Hofstaedtler wrote:

> Source: aalib
> Version: 1.4p5-50
> Severity: serious
> Tags: ftbfs
>
> Rebuilding your package in unstable currently fails:
>
>
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security
> -fcf-protection -I/usr/include -I/usr/include/ncurses -c aacurses.c
> -fPIC -DPIC -o .libs/aacurses.o
> aacurses.c: In function ‘curses_getsize’:
> aacurses.c:80:20: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>80 | *width = stdscr->_maxx + 1;
>   |^~
> aacurses.c:81:21: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>81 | *height = stdscr->_maxy + 1;
>   | ^~
> make[4]: *** [Makefile:726: aacurses.lo] Error 1

This has been caused by a recent change in ncurses which makes the
WINDOW structure opaque.  Accessing its members directly is no longer
possible, you need to use library functions to obtain window dimensions
and positions.  In the current case, this would be getmaxyx(), see the
attached patch.

See the ncurses INSTALL file:

,
| --enable-opaque-curses
| --enable-opaque-form
| --enable-opaque-menu
| --enable-opaque-panel
|   Define symbol in curses.h controlling whether some library structures
|   are opaque, meaning that their members are accessible only via the
|   documented API.  The --enable-opaque-curses option may be overridden
|   by the --enable-reentrant option.
| 
|   Enabling opaque-curses enables opaque for the form, menu, and panel
|   libraries.  Use their corresponding options to disable the feature
|   individually.
| 
|   NOTE: beginning with ncurses 6.5 this option is enabled by default;
|   older versions disable it by default.
`

While ncurses 6.5 has not been released yet, the change has already been
made in the patchlevel Debian is shipping.  From the NEWS file:

,
| 20231021
|   + change defaults for configure opaque and widec options (prompted by
| discussion with Branden Robinson).
`

Cheers,
   Sven (ncurses maintainer in Debian)

From 033d7355157688eb3bc224b973b130f42d5664b1 Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Mon, 4 Dec 2023 17:45:59 +0100
Subject: [PATCH] Use getmaxyx() to obtain width and height

Ncurses patchlevel 20231021 made the WINDOW scructure opaque, so it is
no longer possible to directly access its members, leading to FTBFS.

Closes: #1057381
---
 src/aacurses.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/src/aacurses.c b/src/aacurses.c
index dc3b220..ae7e097 100644
--- a/src/aacurses.c
+++ b/src/aacurses.c
@@ -77,8 +77,7 @@ static void curses_getsize(aa_context * c, int *width, int *height)
 {
 if (__resized_curses)
 	curses_uninit(c), curses_init(>params, NULL,>driverparams, NULL), __resized_curses = 0;
-*width = stdscr->_maxx + 1;
-*height = stdscr->_maxy + 1;
+getmaxyx(stdscr, *width, *height);
 #ifdef GPM_MOUSEDRIVER
 gpm_mx = *width;
 gpm_my = *height;
--
2.43.0

Processed: Re: Bug#1057381: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + trixie sid patch
Bug #1057381 [src:aalib] FTBFS: error: invalid use of incomplete typedef 
‘WINDOW’
Added tag(s) trixie, sid, and patch.

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

Bug#1054789: marked as done (libpreludedb: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 16:49:21 +
with message-id 
and subject line Bug#1054789: fixed in libpreludedb 5.2.0-2.1
has caused the Debian Bug report #1054789,
regarding libpreludedb: FTBFS: dh_install: error: missing files, aborting
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.)


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

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>'
>  /bin/mkdir -p '/<>/debian/tmp/usr/bin'
>  /usr/bin/install -c ./preludedb-admin '/<>/debian/tmp/usr/bin'
> make[4]: Nothing to be done for 'install-data-am'.
> make[4]: Leaving directory '/<>'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> find . -name "__pycache__" -exec rm -rvf {} +
> removed 
> './debian/tmp/usr/local/lib/python3.11/dist-packages/__pycache__/preludedb.cpython-311.pyc'
> removed directory 
> './debian/tmp/usr/local/lib/python3.11/dist-packages/__pycache__'
> find . -name "*.la" -exec sed -i -e 
> "s/^dependency_libs=.*$/dependency_libs=''/g" {} +
> mkdir -p debian/tmp/usr/lib/x86_64-linux-gnu/libpreludedb/bin
> chmod +x debian/tmp/usr/share/libpreludedb/classic/mysql2sqlite.sh 
> debian/tmp/usr/share/libpreludedb/classic/mysql2pgsql.sh
> mkdir -pv /<>/debian/tmp/usr/share/doc/libpreludedb-doc
> mkdir: created directory '/<>/debian/tmp/usr/share/doc'
> mkdir: created directory 
> '/<>/debian/tmp/usr/share/doc/libpreludedb-doc'
> ln -s /usr/share/gtk-doc/html/libpreludedb 
> /<>/debian/tmp/usr/share/doc/libpreludedb-doc/html
> cd bindings/python && python3.11 setup.py install --root 
> /<>/debian/tmp
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html 
> for details.
> 
> 
> 
> !!
>   self.initialize_options()
> dh override_dh_auto_install 
> make[1]: Leaving directory '/<>'
>dh_install
> dh_install: warning: Cannot find (any matches for) 
> "debian/tmp/usr/lib/python3*/*/*" (tried in ., debian/tmp)
> 
> dh_install: warning: python3-preludedb missing files: 
> debian/tmp/usr/lib/python3*/*/*
> dh_install: error: missing files, aborting
> make: *** [debian/rules:46: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/libpreludedb_5.2.0-2_unstable.log

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

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libpreludedb 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: 

Bug#1051392: closed by Debian FTP Masters (reply to Guillem Jover ) (Bug#1051392: fixed in victoriametrics 1.79.14+ds1-1)

[Simon Vetter]

Hi Guillem,

thanks for taking care of this.

The old version is still in stable as of today and is IMHO rendering 
victoria-metrics almost unusable (keeps crashing randomly, up to 10-15 
times a day on my systems). Is there anything that could be done to push 
the fixed package to bookworm, at the very least for armhf ?


Thanks again for your time and help,

-Simon

On 09/09/2023 00:24, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the victoria-metrics package:

#1051392: Crash on unaligned reads on 32-bit arm architectures

It has been closed by Debian FTP Masters  (reply to 
Guillem Jover ).

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Debian FTP Masters 
 (reply to Guillem Jover ) 
by
replying to this email.



--
Simon Vetter

Bug#1057413: FTBFS: dh_install: warning: gnustep-make-doc missing files: Documentation/gnustep-make.pdf

[Chris Hofstaedtler]

Source: gnustep-make
Version: 2.9.1-2
Severity: serious
Tags: ftbfs

Dear Maintainer,

gnustep-make-doc currently FTBFS in unstable, in both my own test build
and on reproducible-builds. Here is a part of the build log:

Installing GNUstep configuration file in 
/build/reproducible-path/gnustep-make-2.9.1/debian/tmp/etc/GNUstep/GNUstep.conf
Installing gnustep-make support software
Installing makefiles
Installing Test Framework scripts
Installing Test Framework support files
Installing (and compressing) manpages
make[1]: Leaving directory 
'/build/reproducible-path/gnustep-make-2.9.1/build-gnustep-make'
   dh_install -O--builddirectory=build-gnustep-make
dh_install: warning: Cannot find (any matches for) 
"Documentation/gnustep-make.pdf" (tried in ., debian/tmp)

dh_install: warning: gnustep-make-doc missing files: 
Documentation/gnustep-make.pdf
dh_install: error: missing files, aborting
make: *** [debian/rules:24: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full log from reproducible-builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gnustep-make_2.9.1-2.rbuild.log.gz

Best,
Chris

Bug#1057307: marked as done (sioyek: FTBFS with mupdf 0.23)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 15:04:07 +
with message-id 
and subject line Bug#1057307: fixed in sioyek 2.0.0+dfsg-4
has caused the Debian Bug report #1057307,
regarding sioyek: FTBFS with mupdf 0.23
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.)


-- 
1057307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sioyek
Version: 2.0.0+dfsg-3+b5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: mu...@packages.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

mupdf 0.23 drops the pdf_parse_link_uri symbol, causing sioyek to fail
to build from source. I am preparing a new upload to fix the issue.

@mupdf maintainers: Could you test if reverse dependencies still build
before pushing a new version in the future?

- --
Groet, Regards,

Victor Westerhuis

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

Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_NL.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US:en:nl_NL:nl
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sioyek depends on:
ii  libc62.37-12
ii  libfreetype6 2.13.2+dfsg-1
ii  libgcc-s113.2.0-7
ii  libgl1   1.7.0-1
ii  libgumbo20.12.0+dfsg-2
ii  libharfbuzz0b8.0.1-1+~optimized
ii  libjbig2dec0 0.19-3
ii  libjpeg62-turbo  1:2.1.5-2
ii  libjs-sphinxdoc  7.2.6-2
ii  libmujs3 1.3.3-3
ii  libopenjp2-7 2.5.0-2
ii  libqt5core5a 5.15.10+dfsg-5
ii  libqt5gui5   5.15.10+dfsg-5
ii  libqt5network5   5.15.10+dfsg-5
ii  libqt5widgets5   5.15.10+dfsg-5
ii  libsqlite3-0 3.44.2-1
ii  libstdc++6   13.2.0-7
ii  libsynctex2  2023.20230311.66589-8
ii  sphinx-rtd-theme-common  2.0.0~rc3+dfsg-2
ii  zlib1-ng [zlib1g]2.0.6-0+~local1+b1
ii  zlib1g   1:1.3.dfsg-3

sioyek recommends no packages.

sioyek suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE6OxII3T+o0Ujs6ECQz2Rq5dHQPsFAmVr4EQTHHZpY3RvckB3
ZXN0ZXJodS5pcwAKCRBDPZGrl0dA+xTaD/9MoSE02oPgj/bc6EWqumd/iTnk7aHe
VIR7IfeJkvjIvnxEXr518se9Fy8E7V8eLS2shOYM0YWT4e/7kKgnB2trCyD7cMnw
jJLrrBsRf0WEIpvg2J6EwbUoZpExBieD7hdXCWbezCPeNsQNDuhTvC1/0rpttt7v
ZPwUtj0T1wfZwpryLbTMkZxX4Avb5ZLgplu6Hkomf9sfrF0/xCEU8bG3X5Blxy6q
j+nDG49ALo8hKepdWwT5J/FAOY9wn9vLovWHv2S8LrHIkFbpvT71fGy/JnPpcoiD
/KaUsWSf7DQGJ/A7V/85OMSVahFiXvK13VEGFA9d6wLPeO4d4VeoGbsvl2d/0yA8
U4Z6zwwZfgQ1eqJPxhr98Znv5cNFzULuinVXcHgRGW/TWX9SBiy3LU54z3VsjTDw
96++mVz79n6dZt5yAe1mzcniVzSi0bZA3opDeOZbCwY0kq+QXntO39Dgko9D9Pwy
c9HMYBcXMZqf4buEUrnMrHsKA89VdW5YhEuaBVqR0PadljHkoHIadu6poADZUeCD
ckeweCZCP96J4ICGUzXunKZ0uOUQcFAcKJKNTZDG9eGMbx2XTJ5sVCIEDEnYOXww
cPgVVjMpW0XIRp76hgFV9FGBxO8GGNE0pLOCq6JZON0Wovo4ayntYSyB/5CfSUun
o356ZnKsr2hzGw==
=wLiO
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: sioyek
Source-Version: 2.0.0+dfsg-4
Done: Victor Westerhuis 

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

Debian distribution maintenance software
pp.
Victor Westerhuis  (supplier of updated sioyek 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: Mon, 04 Dec 2023 14:24:10 +0100
Source: sioyek
Architecture: source
Version: 2.0.0+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Victor Westerhuis 
Changed-By: Victor Westerhuis 
Closes: 1057307
Changes:
 sioyek (2.0.0+dfsg-4) unstable; urgency=medium
 .
   * Use dh_builtusing to generate Built-Using dependency on libmupdf-dev.
   * Fix build with mupdf 0.23 (Closes: 1057307)
Checksums-Sha1:
 92a972587401d4d342d33f50f5cc6ca501d74991 2317 sioyek_2.0.0+dfsg-4.dsc
 

Processed: closing 1042601

[Debian Bug Tracking System]

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

> close 1042601 2.7.0
Bug #1042601 [src:python-apt] python-apt: FTBFS with Sphinx 7.1, docutils 0.20: 
error: invalid command 'build_sphinx'
Marked as fixed in versions python-apt/2.7.0.
Bug #1042601 [src:python-apt] python-apt: FTBFS with Sphinx 7.1, docutils 0.20: 
error: invalid command 'build_sphinx'
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: unblock 1041519 with 1056067

[Debian Bug Tracking System]

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

> unblock 1041519 with 1056067
Bug #1041519 [src:transmission] transmission: contains prebuilt javascript 
without source
1041519 was blocked by: 1056067
1041519 was not blocking any bugs.
Removed blocking bug(s) of 1041519: 1056067
> thanks
Stopping processing here.

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

Bug#1057412: pynormaliz: FTBFS in testing and unstable

[Graham Inggs]

Source: pynormaliz
Version: 2.18+ds-1
Severity: serious
Tags: ftbfs

Hi Maintainer

As can be seen in reproducible builds [1], pynormaliz currently FTBFS
in testing and unstable.  I've copied what I hope is the relevant part
of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/pynormaliz.html


dh execute_after_dh_auto_build --buildsystem=pybuild
make[1]: Leaving directory '/build/reproducible-path/pynormaliz-2.18+ds'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:310: cd
/build/reproducible-path/pynormaliz-2.18+ds/.pybuild/cpython3_3.11/build;
PYTHONPATH=/build/reproducible-path/pynormaliz-2.18+ds/.pybuild/cpython3_3.11/build
python3.11 tests/runtests.py
Error: nauty.c version mismatch
E: pybuild pybuild:395: test: plugin distutils failed with: exit
code=1: cd 
/build/reproducible-path/pynormaliz-2.18+ds/.pybuild/cpython3_3.11/build;
PYTHONPATH={build_dir} {interpreter} tests/runtests.py
dh_auto_test: error: pybuild --test -i python{version} -p 3.11
returned exit code 13
make: *** [debian/rules:9: binary] Error 25

Bug#1057282: linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel upgrade makes systems unresponsive

[Ben Hutchings]

Control: reassign -1 src:linux 6.5.3-1~bpo12+1
Control: tag -1 moreinfo

On Sat, 2023-12-02 at 18:11 +0100, Paul Gevers wrote:
> Package: linux-image-6.5.0-0.deb12.1-arm64
> Version: 6.5.3-1~bpo12+1
> Severity: serious
> Justification: system stops responding
> 
> Dear kernel maintainers,
> 
> Thursday 30 November I upgraded the ci.debian.net workers. We're running 
> the backports kernel there due to issues we discussed earlier, but after 
> upgrading, we lost access to our arm64 hosts one after the other. We're 
> running the 6.4 kernel again now, and I extracted some of the logs. 
> Please let me know if you need more info.

The first error logged in this file has:

> CPU: 6 PID: 15039 Comm: lxc-start Tainted: G  D WL 
> 6.5.0-0.deb12.1-arm64 #1  Debian 6.5.3-1~bpo12+1

The D and W flags mean there were prior BUG and WARN errors logged. 
Please send those as well.

Ben.

-- 
Ben Hutchings
Power corrupts.  Absolute power is kind of neat. - John Lehman



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

Processed: Re: Bug#1057282: linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel upgrade makes systems unresponsive

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 6.5.3-1~bpo12+1
Bug #1057282 [linux-image-6.5.0-0.deb12.1-arm64] 
linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel upgrade makes systems 
unresponsive
Bug reassigned from package 'linux-image-6.5.0-0.deb12.1-arm64' to 'src:linux'.
No longer marked as found in versions linux-signed-arm64/6.5.3+1~bpo12+1.
Ignoring request to alter fixed versions of bug #1057282 to the same values 
previously set
Bug #1057282 [src:linux] linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel 
upgrade makes systems unresponsive
Marked as found in versions linux/6.5.3-1~bpo12+1.
> tag -1 moreinfo
Bug #1057282 [src:linux] linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel 
upgrade makes systems unresponsive
Added tag(s) moreinfo.

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

Bug#1057410: pymupdf: FTBFS in testing and unstable

[Graham Inggs]

Source: pymupdf
Version: 1.22.5+ds1-1
Severity: serious
Tags: ftbfs

Hi Maintainer

As can be seen in reproducible builds [1], pymupdf currently FTBFS in
testing and unstable.  I've copied what I hope is the relevant part of
the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/pymupdf.html


I: pybuild base:310: cd
/build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build;
python3.11 -m unittest discover -v
fitz (unittest.loader._FailedTest.fitz) ... ERROR

==
ERROR: fitz (unittest.loader._FailedTest.fitz)
--
ImportError: Failed to import test module: fitz
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 452, in _find_test_path
package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.11/unittest/loader.py", line 362, in
_get_module_from_name
__import__(name)
  File 
"/build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build/fitz/__init__.py",
line 10, in 
import fitz.fitz as fitz
  File 
"/build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build/fitz/fitz.py",
line 14, in 
from . import _fitz
ImportError: 
/build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build/fitz/_fitz.cpython-311-x86_64-linux-gnu.so:
undefined symbol: pdf_lookup_anchor


--
Ran 1 test in 0.003s

FAILED (errors=1)

Processed: pycairo b-d on python3-all-dev, but only builds for the default python

[Debian Bug Tracking System]

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

> tags 1055488 + ftbfs
Bug #1055488 [src:pycairo] pycairo b-d on python3-all-dev, but only builds for 
the default python
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: mwparserfromhell ftbfs with Python 3.12 (but falls back to Python code)

[Debian Bug Tracking System]

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

> tags 1057401 + ftbfs
Bug #1057401 [src:mwparserfromhell] mwparserfromhell ftbfs with Python 3.12 
(but falls back to Python code)
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1057409: cctools: b-d on python3-all-dev, but not built for all supported Python3 versions

[Graham Inggs]

Source: cctools
Version: 9.9-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev

Hi Maintainer

This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions.  This is seen
on the transition tracker for adding python3.12 support [1] and
creates false positives.

Please either replace the b-d python3-all-dev with python3-dev, or
build for all supported Python3 versions.  With the former solution
yet get later exposure to a new python3 version, with the latter
solution you get early exposure.

Regards
Graham


[1] https://release.debian.org/transitions/html/python3.12-add.html

Bug#1000044: ccze: depends on obsolete pcre3 library

[Yavor Doganov]

Axel Beckert wrote:
> A local test on my /var/log/syslog immediately ran into a segfault,
> though, so I guess, that's one of the plugins you couldn't test.

I tested it but I guess results depend on the contents of the log;
apparently my log didn't trigger this code.

> Culprit is this line, actually the first line in my current
> /var/log/syslog:
> 
>   Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration reload request
>   received, reloading configuration;

Many thanks for the reproducer.  Attached is patch that fixes it for
me.  I suspect there are other issues like these; in fact my pathethic
patch introduces a few memory leaks (I should have told you that in
advance).  The problem is that ccze code manipulates strings obtained
with pcre_get_substring, and assumes it can always use "free" to free
them.  That assumption is fine in the case with the old pcre, because
the definition of pcre_free_substring is just a wrapper around free
(src:pcre3: pcre_get.c:655):

void
pcre_free_substring(const char *pointer)
{
(PUBL(free))((void *)pointer);
}

So ccze code always uses "free".  However, in pcre2, the equivalent
function is different (src:pcre2: src/pcre2_substring.c:240):

void
pcre2_substring_free(PCRE2_UCHAR *string)
{
if (string != NULL)
  {
  pcre2_memctl *memctl = (pcre2_memctl *)((char *)string - 
sizeof(pcre2_memctl));
  memctl->free(memctl, memctl->memory_data);
  }
}

Attempting to use "free" to free a string obtained with
pcre2_subtring_get_by* results in SIGABRT with invalid pointer, while
using pcre2_substring_free on a string obtained with strdup or some
other standard (glibc) string manipulation functions results in
SIGSEGV.  Attached are two equivalent minimalistic programs that
demonstrate this: foo.c uses pcre2 and if you exchange the free
functions at the end for date and dup, you will observe exactly what I
wrote above.  The other program, bar.c, uses the old pcre and it
doesn't make any difference if you swap them or use only "free" as
ccze does.

I guess I need to revisit my patch and find some way to fix this.
It's up to you whether to upload the memleaky patch now or wait for me
to find a solution.  Sorry about this.
diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
index 6b60dc8..2723ff8 100644
--- a/debian/patches/pcre2.patch
+++ b/debian/patches/pcre2.patch
@@ -2455,26 +2455,32 @@ Last-Update: 2023-12-03
  }

if (process)
-@@ -87,12 +87,13 @@
+@@ -60,7 +60,7 @@
+ 
+ pid = strndup ([1], (size_t)(t2 - t - 1));
+ tmp = strndup (process, (size_t)(t - process));
+-free (process);
++pcre2_substring_free (process);
+ process = tmp;
+   }
+ }
+@@ -87,11 +87,11 @@
else
  toret = strdup (send);
  
 -  free (date);
 -  free (host);
 -  free (send);
--  free (process);
--  free (msg);
 +  pcre2_substring_free (date);
 +  pcre2_substring_free (host);
 +  pcre2_substring_free (send);
-+  pcre2_substring_free (process);
 +  pcre2_substring_free (msg);
+   free (process);
+-  free (msg);
free (pid);
-+  free (tmp);
  
return toret;
- }
-@@ -100,33 +101,34 @@
+@@ -100,33 +100,34 @@
  static void
  ccze_syslog_setup (void)
  {
#define PCRE2_CODE_UNIT_WIDTH 8
#include 
#include 
#include 

int
main (void)
{
  pcre2_code *pcre;
  pcre2_match_data *md;
  int error;
  size_t errptr, l;
  char *date = NULL, *dup;
  const char *str = "Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration "
"reload request received, reloading configuration;";

  pcre = pcre2_compile ("^(\\S*\\s{1,2}\\d{1,2}\\s\\d\\d:\\d\\d:\\d\\d)"
"\\s(\\S+)\\s+((\\S+:?)\\s(.*))$",
PCRE2_ZERO_TERMINATED, 0, , , NULL);

  md = pcre2_match_data_create (99, NULL);

  pcre2_match (pcre, str, PCRE2_ZERO_TERMINATED, 0, 0, md, NULL);
  pcre2_substring_get_bynumber (md, 1, (unsigned char **), );

  if (date)
{
  printf ("%s\n", date);
  dup = strdup (date);
}

  pcre2_substring_free (date);
  free (dup);

  return 0;
}
#include 
#include 
#include 

int
main (void)
{
  pcre *pcre;
  int md[99];
  const char *error;
  int errptr, match;
  char *date = NULL, *dup;
  const char *str = "Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration "
"reload request received, reloading configuration;";

  pcre = pcre_compile ("^(\\S*\\s{1,2}\\d{1,2}\\s\\d\\d:\\d\\d:\\d\\d)"
   "\\s(\\S+)\\s+((\\S+:?)\\s(.*))$",
   0, , , NULL);

  match = pcre_exec (pcre, NULL, str, strlen (str), 0, 0, md, 99);
  pcre_get_substring (str, md, match, 1, (const char **));

  if (date)
{
  printf ("%s\n", date);
  dup = strdup (date);
}

  pcre_free_substring (date);
  free (dup);

  return 0;
}

Processed: raise severity of Python 3.12 issues, 3.12 is now a supported Python3 version in unstable

[Debian Bug Tracking System]

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

> severity 1055572 serious
Bug #1055572 [src:cbflib] cbflib ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> severity 1055570 serious
Bug #1055570 [src:lazy-object-proxy] lazy-object-proxy fails tests with Python 
3.12
Ignoring request to change severity of Bug 1055570 to the same value.
> severity 1055568 serious
Bug #1055568 [src:m2crypto] m2crypto ftbfs with Python 3.12
Ignoring request to change severity of Bug 1055568 to the same value.
> severity 1055566 serious
Bug #1055566 [src:mod-wsgi] mod-wsgi ftbfs with Python 3.12
Ignoring request to change severity of Bug 1055566 to the same value.
> severity 1055488 serious
Bug #1055488 [src:pycairo] pycairo b-d on python3-all-dev, but only builds for 
the default python
Severity set to 'serious' from 'important'
> user debian-pyt...@lists.debian.org
Setting user to debian-pyt...@lists.debian.org (was d...@debian.org).
> usertag 1055546 python3.12
There were no usertags set.
Usertags are now: python3.12.
> usertag 1057388 python3.12
There were no usertags set.
Usertags are now: python3.12.
> thanks
Stopping processing here.

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

Bug#1057405: pynormaliz ftbfs with Python 3.12

[Matthias Klose]

Package: src:pynormaliz
Version: 2.18+ds-1
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

pynormaliz ftbfs with Python 3.12:


[...]
dh execute_after_dh_auto_build --buildsystem=pybuild
make[1]: Leaving directory '/<>'
   dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12/build; 
PYTHONPATH=/<>/.pybuild/cpython3_3.12/build python3.12 
tests/runtests.py

Error: nauty.c version mismatch
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: 
cd /<>/.pybuild/cpython3_3.12/build; PYTHONPATH={build_dir} 
{interpreter} tests/runtests.py
I: pybuild base:310: cd /<>/.pybuild/cpython3_3.11/build; 
PYTHONPATH=/<>/.pybuild/cpython3_3.11/build python3.11 
tests/runtests.py

Error: nauty.c version mismatch
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: 
cd /<>/.pybuild/cpython3_3.11/build; PYTHONPATH={build_dir} 
{interpreter} tests/runtests.py
dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" 
returned exit code 13

make: *** [debian/rules:9: binary-arch] Error 25

Bug#1057403: fq: Please upgrade to fq 0.9.0 (resolves FTBFS with latest golang-golang-x-exp-dev)

[Anthony Fok]

Package: fq
Version: 0.3.0-1+b4
Severity: serious
Tags: ftbfs upstream
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: Daniel Milde , Anthony Fok 

Hi Daniel (and other fellow Debian Go Packaging Team members),

First of all, thank you for packaging fq, a very useful tool indeed.

There has been an API change to SortFunc (etc.) in golang.org/x/exp/slices,
(backported from "slices" in go1.21) which breaks fq << 0.8.0; please see:

  * slices: new standard library package based on x/exp/slices
https://github.com/golang/go/issues/57433 

  * x/exp/slices: "backport" slices.SortFunc
https://github.com/golang/go/issues/61374

So, after my recently upload of golang-golang-x-exp-dev, fq 0.3.0-1 now
fails to build from source (FTBFS).

Fortunately, the issue has been fixed upstream.  Please kindly package
fq 0.9.0, specifying these dependencies with explicit versions:

  * golang-github-burntsushi-toml-dev (>= 1.3.2)
  * golang-golang-x-exp-dev (>= 0.0~git20230725.302865e)

Many thanks!
Cheers,

Anthony Fok

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

Kernel: Linux 6.5.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
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

Versions of packages fq depends on:
ii  libc6  2.37-12

fq recommends no packages.

fq suggests no packages.

-- no debconf information

Bug#1057402: pymupdf ftbfs with Python 3.12

[Matthias Klose]

Package: src:pymupdf
Version: 1.22.5+ds1-1
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

pymupdf ftbfs with Python 3.12 in unstable:

I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12/build; 
python3.12 -m unittest discover -v

fitz (unittest.loader._FailedTest.fitz) ... ERROR

==
ERROR: fitz (unittest.loader._FailedTest.fitz)
--
ImportError: Failed to import test module: fitz
Traceback (most recent call last):
  File "/usr/lib/python3.12/unittest/loader.py", line 427, in 
_find_test_path

package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.12/unittest/loader.py", line 337, in 
_get_module_from_name

__import__(name)
  File 
"/<>/.pybuild/cpython3_3.12/build/fitz/__init__.py", line 
10, in 

import fitz.fitz as fitz
  File "/<>/.pybuild/cpython3_3.12/build/fitz/fitz.py", 
line 14, in 

from . import _fitz
ImportError: 
/<>/.pybuild/cpython3_3.12/build/fitz/_fitz.cpython-312-x86_64-linux-gnu.so: 
undefined symbol: pdf_lookup_anchor



--
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: 
cd /<>/.pybuild/cpython3_3.12/build; python3.12 -m unittest 
discover -v
I: pybuild base:310: cd /<>/.pybuild/cpython3_3.11/build; 
python3.11 -m unittest discover -v

fitz (unittest.loader._FailedTest.fitz) ... ERROR

==
ERROR: fitz (unittest.loader._FailedTest.fitz)
--
ImportError: Failed to import test module: fitz
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 452, in 
_find_test_path

package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.11/unittest/loader.py", line 362, in 
_get_module_from_name

__import__(name)
  File 
"/<>/.pybuild/cpython3_3.11/build/fitz/__init__.py", line 
10, in 

import fitz.fitz as fitz
  File "/<>/.pybuild/cpython3_3.11/build/fitz/fitz.py", 
line 14, in 

from . import _fitz
ImportError: 
/<>/.pybuild/cpython3_3.11/build/fitz/_fitz.cpython-311-x86_64-linux-gnu.so: 
undefined symbol: pdf_lookup_anchor



--
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: 
cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m unittest 
discover -v
dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" 
returned exit code 13

Bug#1057401: mwparserfromhell ftbfs with Python 3.12 (but falls back to Python code)

[Matthias Klose]

Package: src:mwparserfromhell
Version: 0.6.5-1
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

mwparserfromhell ftbfs with Python 3.12 (but falls back to Python code).
the packaging probably should check if the extensions are really built.

[...]
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 
-Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python3.12 -c 
src/mwparserfromhell/parser/ctokenizer/tokenizer.c -o 
build/temp.linux-x86_64-cpython-312/src/mwparserfromhell/parser/ctokenizer/tokenizer.o
src/mwparserfromhell/parser/ctokenizer/tokenizer.c: In function 
‘init_tokenizer_text’:
src/mwparserfromhell/parser/ctokenizer/tokenizer.c:91:18: error: 
‘PyUnicode_WCHAR_KIND’ undeclared (first use in this function); did you 
mean ‘PyUnicode_4BYTE_KIND’?

   91 | text->kind = PyUnicode_WCHAR_KIND;
  |  ^~~~
  |  PyUnicode_4BYTE_KIND
src/mwparserfromhell/parser/ctokenizer/tokenizer.c:91:18: note: each 
undeclared identifier is reported only once for each function it appears in

error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
Falling back to pure Python mode.
[...]

Bug#1055916: marked as done (uninstallable in unstable)

[Debian Bug Tracking System]

Your message dated Mon, 4 Dec 2023 08:05:16 -0500
with message-id 

and subject line Re: gedit uninstallable in unstable
has caused the Debian Bug report #1055916,
regarding uninstallable 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.)


-- 
1055916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gedit
Version: 44.2-1
Severity: serious

Hi,

currently, gedit cannot be installed in unstable with this error message
from apt:

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:
 libtepl-common : Breaks: libtepl-6-2 but 6.4.0-7 is to be installed
E: Unable to correct problems, you have held broken packages.

Sebastian Ramacher suggested in #debian-mentors that I file a bug about that
against gedit as tepl is involved in an uncoordinated transition that needs
action from their respective maintainers.

Relevant other bug: https://bugs.debian.org/1055778

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
gedit 46.1-3 migrated to Testing so I'm closing this issue.

Thank you,
Jeremy Bícha--- End Message ---

Bug#1057398: [Debian-med-packaging] Bug#1057398: FTBFS: libITKIOGDCM-5.3.so.1: undefined reference to `gdcm::DirectionCosines::~DirectionCosines()'

[Emmanuel Promayon]

Hi,

This seems due to bug#1056953 [1] as the error message is linked to the 
same missing symbol.


Best regards,
Emmanuel


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

On 04/12/2023 13:36, Chris Hofstaedtler wrote:

Source: elastix
Version: 5.1.0-1
Severity: serious
Tags: ftbfs

Dear Maintainer,

your package FTBFS in a test rebuild in unstable:

...
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libITKIOGDCM-5.3.so.1: undefined 
reference to `gdcm::DirectionCosines::~DirectionCosines()'
collect2: error: ld returned 1 exit status
...
[ 29%] Built target elxCommon
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[1]: *** [Makefile:149: all] Error 2
make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j16 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
make: *** [debian/rules:11: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Please find a full build log attached.

Best,
Chris

___
Debian-med-packaging mailing list
debian-med-packag...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

Bug#1057151: clang-17: ClangTargets.cmake cannot find libclang-17.so.1

[Vincent Lefevre]

Control: reassign -1 libclang1-17 1:17.0.6-1

because the problem is actually there (and this package may be
installed even if clang-17 isn't).

On 2023-11-30 12:13:21 -0700, Cordell Bloor wrote:
> While attempting to update rocm-device-libs, I noticed that searching
> for clang with find_package(Clang) will fail with an error. The
> ClangTargets.cmake file expects libclang to be found at the path
> "/usr/lib/llvm-17/lib/libclang-17.so.1", but the file is actually
> installed to "/usr/lib/x86_64-linux-gnu/libclang-17.so.1".

This seems normal (/usr/lib/x86_64-linux-gnu/libclang-17.so.1 already
exists in libclang1-17 1:17.0.5-1). However, the symbolic link

  /usr/lib/llvm-17/lib/libclang-17.so.1

changed to

  /usr/lib/llvm-17/lib/libclang-17.so.17

in 1:17.0.6-1, and I'm wondering whether this was expected.
I suppose that this is due to one of the following changes:

   * libclang1-17: Only encode the major version in the soname. Closes: 
#1056126.
   * libclang1-17: Provide a symlink for the last soname with the full version.

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

Processed: Re: Bug#1057151: clang-17: ClangTargets.cmake cannot find libclang-17.so.1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libclang1-17 1:17.0.6-1
Bug #1057151 [clang-17] clang-17: ClangTargets.cmake cannot find 
libclang-17.so.1
Bug reassigned from package 'clang-17' to 'libclang1-17'.
No longer marked as found in versions llvm-toolchain-17/1:17.0.6-1.
Ignoring request to alter fixed versions of bug #1057151 to the same values 
previously set
Bug #1057151 [libclang1-17] clang-17: ClangTargets.cmake cannot find 
libclang-17.so.1
Marked as found in versions llvm-toolchain-17/1:17.0.6-1.

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

Bug#1057388: unrardll: needs binary upload to add Python 3.12 as supported

[Graham Inggs]

Source: unrardll
Version: 0.1.7-1
Severity: serious
Tags: ftbfs

Hi Maintainer

The package unrardll requires a binary upload since it is in contrib
and cannot be built on the buildds [1].

Please upload the binary package python3-unrardll_0.1.7-1+b1_amd64.deb to
the archive.  There is no need for another source upload and no need
to bump the version.

However, as suggested in #977170, a source+binary upload may just be easier.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=unrardll

Bug#1054793: marked as done (libprelude: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 11:05:11 +
with message-id 
and subject line Bug#1054793: fixed in libprelude 5.2.0-5.1
has caused the Debian Bug report #1054793,
regarding libprelude: FTBFS: dh_install: error: missing files, aborting
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.)


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

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>'
>  /bin/mkdir -p '/<>/debian/tmp/usr/bin'
>  /usr/bin/install -c ./libprelude-config '/<>/debian/tmp/usr/bin'
> /usr/bin/install -c -d -m 711 /<>/debian/tmp/var/spool/prelude;
> /usr/bin/install -c -d -m 755 /<>/debian/tmp/etc/prelude;
> /usr/bin/install -c -d -m 755 /<>/debian/tmp/etc/prelude/default;
> /usr/bin/install -c -d -m 711 /<>/debian/tmp/etc/prelude/profile;
>  /bin/mkdir -p '/<>/debian/tmp/usr/include/libprelude'
>  /usr/bin/install -c -m 644 prelude-config.h 
> '/<>/debian/tmp/usr/include/libprelude'
> make[5]: Leaving directory '/<>'
> make[4]: Leaving directory '/<>'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> find . -name "__pycache__" -exec rm -rvf {} +
> removed 
> './debian/tmp/usr/local/lib/python3.11/dist-packages/__pycache__/prelude.cpython-311.pyc'
> removed directory 
> './debian/tmp/usr/local/lib/python3.11/dist-packages/__pycache__'
> find . -name "*.la" -exec sed -i -e 
> 's/^dependency_libs=.*$/dependency_libs=/g' {} +
> mkdir -pv /<>/debian/tmp/usr/share/doc/libprelude-doc
> mkdir: created directory '/<>/debian/tmp/usr/share/doc'
> mkdir: created directory 
> '/<>/debian/tmp/usr/share/doc/libprelude-doc'
> ln -s /usr/share/gtk-doc/html/libprelude 
> /<>/debian/tmp/usr/share/doc/libprelude-doc/html
> cd bindings/python && python3.11 setup.py install --root 
> /<>/debian/tmp
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html 
> for details.
> 
> 
> 
> !!
>   self.initialize_options()
> dh override_dh_auto_install --with ruby
> make[1]: Leaving directory '/<>'
>dh_install
> dh_install: warning: Cannot find (any matches for) 
> "debian/tmp/usr/lib/python3*/*/*" (tried in ., debian/tmp)
> 
> dh_install: warning: python3-prelude missing files: 
> debian/tmp/usr/lib/python3*/*/*
> dh_install: error: missing files, aborting
> make: *** [debian/rules:59: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/libprelude_5.2.0-5_unstable.log

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

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libprelude package)

(This message was generated automatically at their 

Bug#1057383: mapclassify: Build-Depends on python3-libpysal which is not in testing

[Graham Inggs]

Source: mapclassify
Version: 2.6.1-2
Severity: serious
Tags: ftbfs

Hi Maintainer

mapclassify has a build-dependency on python3-libpysal which is no
longer in testing.

Please drop this build-dependency or help get python3-libpysal back
into testing.

In addition, if any of mapclassify's build-dependencies are only used
for build-time tests, please annotate them with the  build
profile [1].

Regards
Graham


[1] https://wiki.debian.org/BuildProfileSpec

Bug#1057357: qtremoteobjects-everywhere-src: FTBFS in bullseye and bookworm because of expired SSL certificates, will also FTBFS in trixie/sid eventually

[Dmitry Shachnev]

Hi Santiago!

On Sun, Dec 03, 2023 at 11:23:07PM +0100, Santiago Vila wrote:
> [...]
>
> I'm attaching two patches to fix this.
>
> The first one modifies the script 
> tests/auto/external_IODevice/cert/generate.sh
> so that certificates expire in ten years.
>
> The second patch is merely the result of running the script.

Generally, we try to avoid including patches which have not been applied
upstream. And upstream has solved this problem by simply regenerating the
patches with the old configuration [1].

So I have forwarded your first patch to upstream [2] to give them chance
to review it. If it's approved/merged, I will submit your second patch to
regenerate the certificates again (I hope you don't mind).

If there is no response from upstream, I will go ahead and make uploads
with both patches in a week.

[1]: https://code.qt.io/cgit/qt/qtremoteobjects.git/commit/?id=ac3b93c886c04bc1
[2]: https://codereview.qt-project.org/c/qt/qtremoteobjects/+/522923

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1033531: marked as done (bdebstrap: autopkgtest regression: ubuntu-keyring not available in testing)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 10:49:49 +0100
with message-id <2c10291090b04429cf0b6709f9157942a4002039.ca...@debian.org>
and subject line Re: bdebstrap: autopkgtest regression: ubuntu-keyring not 
available in testing
has caused the Debian Bug report #1033531,
regarding bdebstrap: autopkgtest regression: ubuntu-keyring not available in 
testing
to be marked as done.

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

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


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

Source: bdebstrap
Version: 0.5.0-1
Severity: serious
Tags: bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, one of the tests 
depends on ubuntu-keyring which was removed from testing on 2019-07-24 
and hence your test fails in testing.


[Release Team hat on] Because of the timing of this bug (during the hard 
freeze) and because it doesn't seem to indicate functionality failure of 
this package, I have marked it as bookworm-ignore. However, if done 
reasonably soon, we'll unblock an upload fixing this issue.


Paul


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Sun, 26 Mar 2023 21:57:26 +0200 Paul Gevers 
wrote:
> Source: bdebstrap
> Version: 0.5.0-1
> Severity: serious
> Tags: bookworm-ignore
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Dear maintainer(s),
> 
> Your package has an autopkgtest, great. However, one of the tests 
> depends on ubuntu-keyring which was removed from testing on 2019-07-24
> and hence your test fails in testing.

ubuntu-keyring 2023.11.28.1-0.2 has migrated to testing.

-- 
Benjamin Drung
Debian & Ubuntu Developer--- End Message ---

Bug#1056953: [Debian-med-packaging] Bug#1056953: gdcm: ABI broke in last version 3.0.22-1

[Emmanuel Promayon]

Thanks for the clarification.

To add my 2 cents, the problem appears to be raised by libITKIOGDCM 
shared object (from the insighttoolkit5 package), which is indeed used 
by libitkimage shared object of CamiTK.


Best regards,
Emmanuel

On 27/11/2023 09:43, Gianfranco Costamagna wrote:

Source: gdcm
Version: 3.0.22-1
Severity: serious

Hello, as seen, gdcm is not migrating because of camitk test regression.
Looking at the failure, looks like the fault is not in camitk, but in 
gdcm itself, changing the ABI without a SONAME bump


quoting 
https://ci.debian.net/data/autopkgtest/testing/amd64/c/camitk/40209513/log.gz


159s 2023-11-26 13:11:35.182 [ERROR  ] Extension manager error:
159s Loading component extension failed after 10 tries.
159s
159s Plugin:
159s 
"/usr/lib/x86_64-linux-gnu/camitk-5.1/components/libitkimage.so.5.1.0"

159s
159s Error:
159s Cannot load library : 
(/lib/x86_64-linux-gnu/libITKIOGDCM-5.3.so.1: undefined symbol: 
_ZN4gdcm16DirectionCosinesD1Ev

159s
159s List of library paths:
159s  - /usr/lib/x86_64-linux-gnu/camitk-5.1/viewers
159s  - /usr/lib/x86_64-linux-gnu/camitk-5.1/components
159s  - /usr/lib/x86_64-linux-gnu/camitk-5.1/actions
159s  - /usr/lib/x86_64-linux-gnu/camitk-5.1
159s  - /usr/lib/x86_64-linux-gnu/qt5/plugins
159s  - /usr/bin
159s


$ echo _ZN4gdcm16DirectionCosinesD1Ev |c++filt
gdcm::DirectionCosines::~DirectionCosines()


Checking the changes in header files for new release I see
-DirectionCosines::~DirectionCosines() = default;

and
-  ~DirectionCosines();
+  ~DirectionCosines() = default;


But this object is used in external packages, so it can't change 
signature or be dropped.


G.

___
Debian-med-packaging mailing list
debian-med-packag...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging


--
Emmanuel Promayon
Professeur Univ. Grenoble Alpes - Polytech Grenoble
Laboratoire TIMC - équipe GMCAO

Bug#1057381: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’

[Chris Hofstaedtler]

Source: aalib
Version: 1.4p5-50
Severity: serious
Tags: ftbfs

Rebuilding your package in unstable currently fails:


libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-I/usr/include -I/usr/include/ncurses -c aacurses.c  -fPIC -DPIC -o 
.libs/aacurses.o
aacurses.c: In function ‘curses_getsize’:
aacurses.c:80:20: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
‘struct _win_st’}
   80 | *width = stdscr->_maxx + 1;
  |^~
aacurses.c:81:21: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
‘struct _win_st’}
   81 | *height = stdscr->_maxy + 1;
  | ^~
make[4]: *** [Makefile:726: aacurses.lo] Error 1
make[4]: Leaving directory '/<>/src'
make[3]: *** [Makefile:483: all] Error 2
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:492: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


Best,
Chris