Bug#1056443: marked as done (pysph ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Tue, 26 Dec 2023 08:38:43 +0200
with message-id 

and subject line pysph ftbfs with Python 3.12
has caused the Debian Bug report #1056443,
regarding pysph ftbfs with Python 3.12
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.)


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

Package: src:pysph
Version: 1.0~b1-6
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

pysph ftbfs with Python 3.12:

[...]
I: pybuild base:310: cd '/<>/.pybuild/cpython3_3.12/build'; 
python3.12 -m pytest -k "not test_sph_evaluator and not TestInterpolator 
and not test_get_points_from_mgrid and not test_get_surface_points_uniform"
= test session starts 
==

platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
rootdir: /<>
configfile: tox.ini
collected 224 items / 29 errors / 91 deselected / 133 selected

 ERRORS 

_ ERROR collecting 
.pybuild/cpython3_3.12/build/pysph/base/tests/test_device_helper.py _
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.12/build/pysph/base/tests/test_device_helper.py'.

Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.12/importlib/__init__.py:90: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
pysph/base/tests/test_device_helper.py:4: in 
from pysph.base.utils import get_particle_array  # noqa: E402
pysph/base/utils.py:7: in 
from .particle_array import ParticleArray, \
pysph/base/particle_array.pyx:25: in init pysph.base.particle_array
from compyle.array import Array, get_backend, to_device
/usr/lib/python3/dist-packages/compyle/array.py:11: in 
from .sort import radix_sort
/usr/lib/python3/dist-packages/compyle/sort.py:5: in 
from .transpiler import Transpiler, convert_to_float_if_needed
/usr/lib/python3/dist-packages/compyle/transpiler.py:12: in 
from .ext_module import ExtModule
/usr/lib/python3/dist-packages/compyle/ext_module.py:14: in 
from pyximport import pyxbuild
/usr/lib/python3/dist-packages/pyximport/__init__.py:1: in 
from .pyximport import *
/usr/lib/python3/dist-packages/pyximport/pyximport.py:51: in 
import imp
E   ModuleNotFoundError: No module named 'imp'
_ ERROR collecting 
.pybuild/cpython3_3.12/build/pysph/base/tests/test_domain_manager.py _
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.12/build/pysph/base/tests/test_domain_manager.py'.

Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.12/importlib/__init__.py:90: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
pysph/base/tests/test_domain_manager.py:8: in 
from pysph.base.nnps import DomainManager, BoxSortNNPS, LinkedListNNPS
pysph/base/nnps.py:1: in 
from pysph.base.nnps_base import get_number_of_threads, py_flatten, \
pysph/base/nnps_base.pyx:1: in init pysph.base.nnps_base
# cython: language_level=3, embedsignature=True
pysph/base/particle_array.pyx:25: in init pysph.base.particle_array
from compyle.array import Array, get_backend, to_device
/usr/lib/python3/dist-packages/compyle/array.py:11: in 
from .sort import radix_sort
/usr/lib/python3/dist-packages/compyle/sort.py:5: in 
from .transpiler import Transpiler, convert_to_float_if_needed
/usr/lib/python3/dist-packages/compyle/transpiler.py:12: in 
from .ext_module import ExtModule
/usr/lib/python3/dist-packages/compyle/ext_module.py:14: in 
from pyximport import pyxbuild
/usr/lib/python3/dist-packages/pyximport/__init__.py:1: in 
from .pyximport import *
/usr/lib/python3/dist-packages/pyximport/pyximport.py:51: in 
import imp
E   ModuleNotFoundError: No module named 'imp'
--- End Message ---
--- Begin Message ---
Version: 0.29.36-4

pysph 1.0~b1-7 built successfully with cython3 0.29.36-4.--- End Message ---

Processed: pysph ftbfs with Python 3.12

[Debian Bug Tracking System]

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

> notfound 1056443 cython3/0.29.36-2
Bug #1056443 [src:cython] pysph ftbfs with Python 3.12
The source cython3 and version 0.29.36-2 do not appear to match any binary 
packages
No longer marked as found in versions cython3/0.29.36-2.
> notfixed 1056443 cython3/3.0.5-1
Bug #1056443 [src:cython] pysph ftbfs with Python 3.12
The source cython3 and version 3.0.5-1 do not appear to match any binary 
packages
No longer marked as fixed in versions cython3/3.0.5-1.
> found 1056443 cython/0.29.36-2
Bug #1056443 [src:cython] pysph ftbfs with Python 3.12
Marked as found in versions cython/0.29.36-2.
> fixed 1056443 cython/3.0.5-1
Bug #1056443 [src:cython] pysph ftbfs with Python 3.12
Marked as fixed in versions cython/3.0.5-1.
> thanks
Stopping processing here.

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

Bug#1057840: marked as done (macs ftbfs with Python 3.12)

[Debian Bug Tracking System]

Your message dated Tue, 26 Dec 2023 08:22:46 +0200
with message-id 

and subject line macs ftbfs with Python 3.12
has caused the Debian Bug report #1057840,
regarding macs ftbfs with Python 3.12
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.)


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

Package: src:macs
Version:
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

macs ftbfs with Python 3.12 (note that also cython 3.0.5 was used)

[...]
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:310: python3.12 setup.py config

Error compiling Cython file:

...
crick_right = right_sum(crick, search_start, window_size)

wtd_list = np.zeros( search_end - search_start + 1, dtype="float32")
i = 0
for j in range(search_start, search_end+1):
wtd_list[i] = max((2 * (watson_left * crick_right)**0.5 - 
watson_right - crick_left),0) # minimum score is 0


 ^


MACS2/IO/CallPeakUnit.pyx:200:93: complex types are unordered
Compiling MACS2/Prob.pyx because it changed.
Compiling MACS2/IO/Parser.pyx because it changed.
Compiling MACS2/Pileup.pyx because it changed.
Compiling MACS2/PeakModel.pyx because it changed.
Compiling MACS2/PeakDetect.pyx because it changed.
Compiling MACS2/Signal.pyx because it changed.
Compiling MACS2/IO/PeakIO.pyx because it changed.
Compiling MACS2/IO/BedGraphIO.pyx because it changed.
Compiling MACS2/IO/FixWidthTrack.pyx because it changed.
Compiling MACS2/IO/PairedEndTrack.pyx because it changed.
Compiling MACS2/IO/BedGraph.pyx because it changed.
Compiling MACS2/IO/ScoreTrack.pyx because it changed.
Compiling MACS2/IO/CallPeakUnit.pyx because it changed.
[ 1/13] Cythonizing MACS2/IO/BedGraph.pyx
[ 2/13] Cythonizing MACS2/IO/BedGraphIO.pyx
[ 3/13] Cythonizing MACS2/IO/CallPeakUnit.pyx
Traceback (most recent call last):
  File "/<>/setup.py", line 102, in 
main()
  File "/<>/setup.py", line 98, in main
ext_modules = cythonize( ext_modules ),
  
  File "/usr/lib/python3/dist-packages/Cython/Build/Dependencies.py", 
line 1154, in cythonize

cythonize_one(*args)
  File "/usr/lib/python3/dist-packages/Cython/Build/Dependencies.py", 
line 1321, in cythonize_one

raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: MACS2/IO/CallPeakUnit.pyx
E: pybuild pybuild:395: configure: plugin distutils failed with: exit 
code=1: python3.12 setup.py config
dh_auto_configure: error: pybuild --configure -i python{version} -p 
"3.12 3.11" returned exit code 13

make: *** [debian/rules:14: binary] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.29.36-3.1

macs 2.2.9.1-1+b1 built successfully with cython3 0.29.36-3.1.
The build failure with cython 3.0.x is #1056813.--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Tue, 26 Dec 2023 08:20:39 +0200
with message-id 

and subject line compyle: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
has caused the Debian Bug report #1058379,
regarding compyle: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/utils.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/cuda.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/ext_module.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/parallel.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/capture_stream.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/translator.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/low_level.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/opencl.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/ast_utils.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/types.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/profile.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/api.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/template.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/config.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/sort.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/jit.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/extern.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/transpiler.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/cython_generator.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> copying compyle/array.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle
> creating /<>/.pybuild/cpython3_3.12_compyle/build/compyle/thrust
> copying compyle/thrust/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/thrust
> creating /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/test_parallel.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/test_cython_generator.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/test_capture_stream.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/test_gpu_struct.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/test_types.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/test_cuda.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/test_profile.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/test_transpiler.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/test_translator.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/test_low_level.py -> 
> /<>/.pybuild/cpython3_3.12_compyle/build/compyle/tests
> copying compyle/tests/test_utils.py -> 
> 

Bug#1056017: rlvm: FTBFS: boost1.83 transition

[Bo YU]

Hi！

On Tue, Dec 26, 2023 at 1:24 AM Ying-Chun Liu (PaulLiu)
 wrote:
>
> Hi Bo YU,
>
> Please NMU it and I'll sponsor it.

Thanks. please to see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059441

```

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/rlvm/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/r/rlvm/rlvm_0.14-5.2.dsc

Changes since the last upload:

 rlvm (0.14-5.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix ftbfs on boost1.83. (Closes: #1056017)
   * Use libboost-timer-dev instead of libboost-date-time-dev.

```

BR,
Bo
>
> Yours,
> Paul
>
>
> On 2023/12/25 19:52, Bo YU wrote:
> > Source: rlvm
> > Version: 0.14-5.1
> > Followup-For: Bug #1056017
> > Tags: patch
> >
> > Dear Maintainer,
> >
> > I cost some time to fix the issue and patch attached. Please review it.
> >
> > In order to fix the RC bug ASAP, I may do a NMU to mentor and find a
> > sponsor to upload it. Please feel free to break the process if there is
> > any issue.
> >
> >

Bug#958682: marked as done (node-jsonld: Remove dependency to node-request)

[Debian Bug Tracking System]

Your message dated Tue, 26 Dec 2023 01:04:15 +
with message-id 
and subject line Bug#958682: fixed in node-jsonld 8.3.2-1
has caused the Debian Bug report #958682,
regarding node-jsonld: Remove dependency to node-request
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.)


-- 
958682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-jsonld
Severity: important
Control: block 956423 by -1

Upstream has deprecated node-request:
https://github.com/request/request/issues/3142

It can be replaced by node-got 
--- End Message ---
--- Begin Message ---
Source: node-jsonld
Source-Version: 8.3.2-1
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated node-jsonld 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, 25 Dec 2023 19:19:51 +0100
Source: node-jsonld
Architecture: source
Version: 8.3.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 958682 1003502
Changes:
 node-jsonld (8.3.2-1) experimental; urgency=medium
 .
   * declare compliance with Debian Policy 4.6.2
   * update copyright info: update coverage
   * drop all patches, obsoleted by upstream changes
   * update build rules;
 build-depend on node-rollup-plugin-commonjs
 node-rollup-plugin-json node-rollup-plugin-node-resolve rollup
 (not node-babel7 node-babel-loader node-webpack-merge webpack);
 closes: bug#958682, #1003502, thanks to yadd and Caleb Adepitan
Checksums-Sha1:
 d933cd19a8ecfc2b98cf43d078f5c01ab99b888a 2282 node-jsonld_8.3.2-1.dsc
 dae3dfa6849ee174662205033ba8c16b927e9e94 163223 node-jsonld_8.3.2.orig.tar.gz
 49d88e4a0eb4e4738705260676356d1d58976a59 6160 node-jsonld_8.3.2-1.debian.tar.xz
 96d62b461b6c26fa0c2dd94a3b901a4e150e9371 8000 
node-jsonld_8.3.2-1_amd64.buildinfo
Checksums-Sha256:
 554262a389b76d1973390a7a95245654cb6cf9a36c7070fece9506290658e28c 2282 
node-jsonld_8.3.2-1.dsc
 a9eb43784fe850fa159fc6b7c8e6bb1904160b0840c860a2a7651d72c9102b0b 163223 
node-jsonld_8.3.2.orig.tar.gz
 f3f40b02260408df61141cab8214f68282d4ec2e6951ba88494d58718db9b649 6160 
node-jsonld_8.3.2-1.debian.tar.xz
 75a2a62562532e15ba05ae8d25b403432525d25d504ee809c6502580cb97fb91 8000 
node-jsonld_8.3.2-1_amd64.buildinfo
Files:
 b5a5a14945b2a4d7a41b29033085ef36 2282 javascript optional 
node-jsonld_8.3.2-1.dsc
 19e1dc69f017cca0184b64ff78f59e8d 163223 javascript optional 
node-jsonld_8.3.2.orig.tar.gz
 5162e4e1ec3217319755d31f6a99e4e7 6160 javascript optional 
node-jsonld_8.3.2-1.debian.tar.xz
 0eb0896ccad208588c664a83406ccdd5 8000 javascript optional 
node-jsonld_8.3.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmWKIcQACgkQLHwxRsGg
ASFhdw/+OYFUm+D2a3EydOSFYFj5AlWALtjxhTUUZWH7R9ekK0WV33AxOtzOPZOh
BZndkUXK89pLWgV9uoA3nfh0JI+AYPmbS/CfUSkW058xUvsEoehW2/d4EDR/vtvH
L1uowHUbRU3+hYkPs92ii2BCZZhQDMNEGSH6nVlyPLyi2bFxVEnaMhZX/pQzPRZo
MqEWP0MnP/iFlOCPoArh5zO62o0kocmNyYNg+eSBn8kGQ2OWcyzCMsVnkDoeFHmy
/ELuJnH50nG+BwMQ6Jh6jWYne+qVhvtQZTe0Y1ukb5R1wbRMkD6jttK/N/6dbQWt
bLcc60Ewx86HHy6M4jvUilU7mCehNAzgBmOfhRI/MwqUvLeA5k+hIUKbu+HZEXtj
b6BFGfaySpCbPRvo2KfqOOn4HC1+sSamzMJfKxtsOM08PoLgnBGwFt9kVEw1CVME
+pR6QV+BWdVokk9UqkR+ww75MXcOWTA6HcuBxt7nzZc+tNXCu516lpp3+q/R3N0E
X/x/y8QZrvVcPH00HmlSXjKBRznBjqmoK/+88iWS5Bg7l2tXF8a+j+KB1iXkt7sV
RivwIgrAPYUz/oziypb4kV/pMv7nn3E/IrfBSd827zb4mwM3DDbAv3/PPxjHJjtS
2JzgbfCI3BSFmSFAbqVpe4gMzTAW2CPohLhIYMqj0M8vCL9JL8Y=
=pXAd
-END PGP SIGNATURE End Message ---

Processed: severity of 1057445 is serious, severity of 1057452 is serious, severity of 1057449 is serious ...

[Debian Bug Tracking System]

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

> # Linux 6.6 has been uploaded to sid
> severity 1057445 serious
Bug #1057445 [jool-dkms] jool-dkms: module build fails for Linux 6.6: 
nl_common.c:17:20: error: 'struct genl_info' has no member named 'userhdr'
Severity set to 'serious' from 'important'
> severity 1057452 serious
Bug #1057452 {Done: Andreas Beckmann } [zfs-dkms] zfs-dkms: 
module build fails for Linux 6.6: zfs_ctldir.c:523:13: error: 'struct inode' 
has no member named 'i_ctime'
Severity set to 'serious' from 'important'
> severity 1057449 serious
Bug #1057449 [falcosecurity-scap-dkms] falcosecurity-scap-dkms: module build 
fails for Linux 6.6: ppm_fillers.c:1438:63: error: 'struct inode' has no member 
named 'i_ctime'
Severity set to 'serious' from 'important'
> severity 1057447 serious
Bug #1057447 [broadcom-sta-dkms] broadcom-sta-dkms: module build fails for 
Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 
'wireless_handlers'
Severity set to 'serious' from 'important'
> severity 1057446 serious
Bug #1057446 [evdi-dkms] evdi-dkms: module build fails for Linux 6.6: 
evdi_fb.c:421:23: error: 'FBINFO_DEFAULT' undeclared
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1059040: libxml2: ABI change? (undefined references)

[Rene Engelhard]

Hi,

Am 25.12.23 um 22:57 schrieb Rene Engelhard:
I didn't file it for the plain build issue. Nevertheless, if it broke so 
many projects you probably should do a full-fledged rebuild and send 


Well, mitigated by 2.12.3, but still.

But again, this is completely off-topic to what I filed in this bug 
which is the ABI break.


Which *maybe* could be ignored. Maybe one can do Breaks: after a rebuild 
(then you might get a problem inbetween only when in this case 
libreoffice is to be rebuilt. But here libreoffice fails its tests even).


But not until one knows what is affected.

*You* need to do a test as the library maintainer/the one who wants to 
update it, not me.


Regards,

Rene

Bug#1059040: libxml2: ABI change? (undefined references)

[Thorsten Glaser]

On Mon, 25 Dec 2023, Rene Engelhard wrote:

> In any case, *this* bug is about the ABI change: removed symbols/versions 
> other
> stuff relies on.
>
> Long story short: libxml2 2.12 has still a long road to go with much work on
> your side until you can upload it to unstable.

Sounds like it needs a solib major version and package name change
for coïnstallability, upgrades, etc. *or* a fix that restores the
prior ABI.

Perhaps first ask upstream whether the removal was desired (and in
which case they would do the version bump).

bye,
//mirabilos
-- 
15:41⎜ Somebody write a testsuite for helloworld :-)

Bug#1058129: python-scruffy: FTBFS: ModuleNotFoundError: No module named 'imp'

[Dale Richards]

I've opened a merge request in Salsa that fixes this bug and updates the 
package to upstream version 0.3.8.2:
https://salsa.debian.org/python-team/packages/python-scruffy/-/merge_requests/2

Could a DPT member please review and merge/upload as required?

I've also submitted a fix upstream:
https://github.com/snare/scruffy/pull/31


Best regards,
Dale Richards

Bug#1059040: libxml2: ABI change? (undefined references)

[Rene Engelhard]

Hi,

Am 25.12.23 um 22:33 schrieb Rene Engelhard:

The tests are still failing and there is no patch anywhere yet, see


Sorry, link got lost: 
https://bugs.documentfoundation.org/show_bug.cgi?id=158423


and c) you ignore the actual issue here at hand and that is that the new 
libxml2 breaks the ABI, causing at least libxmlsec to be needed to be 
rebuilt.


I didn't file it for the plain build issue. Nevertheless, if it broke so 
many projects you probably should do a full-fledged rebuild and send 
patches before uploading to unstable and putting this on all maintainers 
(or by making them get a FTBFS bug by Lucas once a rebuild happens at 
which time people won't remember the libxml2 update)


In any case, *this* bug is about the ABI change: removed 
symbols/versions other stuff relies on.


Long story short: libxml2 2.12 has still a long road to go with much 
work on your side until you can upload it to unstable.


Regards,

Rene

Bug#1059335: marked as done (librandombytes-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/librandombytes.a)

[Debian Bug Tracking System]

Your message dated Mon, 25 Dec 2023 21:50:29 +
with message-id 
and subject line Bug#1059335: fixed in librandombytes 0~20230919-4
has caused the Debian Bug report #1059335,
regarding librandombytes-dev has an undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/librandombytes.a
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.)


-- 
1059335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librandombytes-dev
Version: 0~20230919-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libnacl-dev

librandombytes-dev has an undeclared file conflict. This may result in
an unpack error from dpkg.

The file /usr/lib/x86_64-linux-gnu/librandombytes.a is contained in the
packages
 * libnacl-dev/20110221-12 as present in bookworm
 * librandombytes-dev/0~20230919-3 as present in unstable

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

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: librandombytes
Source-Version: 0~20230919-4
Done: Jan Mojžíš 

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

Debian distribution maintenance software
pp.
Jan Mojžíš  (supplier of updated librandombytes 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, 25 Dec 2023 22:00:59 +0100
Source: librandombytes
Architecture: source
Version: 0~20230919-4
Distribution: unstable
Urgency: medium
Maintainer: Jan Mojžíš 
Changed-By: Jan Mojžíš 
Closes: 1059335
Changes:
 librandombytes (0~20230919-4) unstable; urgency=medium
 .
   * d/rules: add also 'Replaces: libnacl-dev' (Closes: #1059335)
Checksums-Sha1:
 bdb3cc36dcda29121299609e06661ccb48585b0e 2214 librandombytes_0~20230919-4.dsc
 723f23de1af2cf13ab53fed87bbd7c0c32801f31 5004 
librandombytes_0~20230919-4.debian.tar.xz
 4707cf1483e9bd9b65c30e0bf58c3fdf302f1ddf 6541 
librandombytes_0~20230919-4_source.buildinfo
Checksums-Sha256:
 1762997662cb646b0dd50d968647efbe6509dbbd3cfa61faabe5a2a0b8ef2e09 2214 
librandombytes_0~20230919-4.dsc
 f7b54dacdb9f7f9a4bc9637145edbba060b245179bf3bb3c192262935e88190c 5004 
librandombytes_0~20230919-4.debian.tar.xz
 50ac20f81941f3ca5cae22d1c8a8393346da336c72249f68ae568c2d3a4ebfca 6541 
librandombytes_0~20230919-4_source.buildinfo
Files:
 df6034396536ce13bc6c18c97766d419 2214 libs optional 
librandombytes_0~20230919-4.dsc
 000e502826950af3c49f7a3970fd187b 5004 libs optional 
librandombytes_0~20230919-4.debian.tar.xz
 1fd424f4f5140276af25cdc7a36df639 6541 libs optional 
librandombytes_0~20230919-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEE0Aiwwj2EeeRrn8uQRdpRdJaTn/kFAmWJ7roVHGphbi5tb2p6
aXNAZ21haWwuY29tAAoJEEXaUXSWk5/5HkoP/jJ7P9GeOwcNfBjnN2ynAbos7Bk0
pl+32YDkGxtBat/PI5gacv9sxSaNYgvGlmSogbob3TmuIJkORpkxE8J4fawgy1lK
TaCjtm0tlqSKa8ikykPo9Jp+WKCfB/uyudiw6eXiDpQD+fDLLJUMnnfdZhAAH1sN
L8C3fpZ/L5/5Bjn8b6qWmcSlQFXiWlbwldfeNYt+bFB9XqdFMVNWSFqyO4KxtySh
xJ5KhNCSMjtf0GizS+nzGq2ZZUc9r9s5dqpnu6BGel0d9pSjt4NQM5IpcG+6zQ5k
AmvYDeGBRNowXWI+vjAzO4ZJfGk49NdLeAMuj740hLk1ReFEF/z1OTBB0Bj+8kdu
pSDJ4F+WW170o2ejg1AScwfK76nPNgHoqKf1gDVFCi3599qJ2oqrPX1/lTxUFZO7
WeSgouAvV7LzZxzTW5oWyy3TFfqoXG0lZCiIjQA5oWsJfHMgSGmi9AD1EKNiNj+V
xal6fNLOatQfvI75eeA5EeiAi1wLPfoUH3p2yI4+YfL6ut7xl8dGqmRDLfOUkhTF
CXUH0T09jTQOuZMPJD3f41MbJG4J9v71DMg4IYPUHnxecy24mqNg3Ss9OPZNGy//
Gz0ENq8McfMVQk9QYHk5SzDTUzk2EPjHYpfZ3Xj8mWUSXyTWlPPCP7vmyo7wh+Sb
NwsCmyHilEqbkmih
=92OI
-END PGP SIGNATURE End Message ---

Bug#1058795: installing docker.io makes all qemu guests lose internet connection

[Michael Tokarev]

On Sat, 16 Dec 2023 14:54:32 +0100 Wolfgang Rohdewald  
wrote:

Package: docker.io
Version: 20.10.24+dfsg1-1+b3
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

   * What led up to the situation?

installed docker.io with existing qemu guests in bridge mode, did not do
anything else.


This seems to be because docker includes some firewall rules which does not
play nice with existing firewall rules.  For example, in my case I use
nftables, and after docker.io is installed, I had to

 rmmod xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo 
xt_addrtype nft_compat br_netfilter

in order to make my bridge working again.  It isn't only qemu guests which
are broken, it's everything connected to the host bridge besides the host
itself, - eg nspawn containers.

/mjt

Processed: Re: Bug#1058029: qemu-guest-agent: QEMU-GA WON'T START

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo unreproducible
Bug #1058029 [qemu-guest-agent] qemu-guest-agent: QEMU-GA WON'T START
Added tag(s) unreproducible and moreinfo.

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

Bug#1058029: qemu-guest-agent: QEMU-GA WON'T START

[Michael Tokarev]

Control: tag -1 + moreinfo unreproducible

11.12.2023 14:51, Y :

Package: qemu-guest-agent
Version: 1:8.1.2+ds-1~bpo12+1
Severity: serious
Justification: 6

Dear Maintainer,

The problem arose after upgrading from bullseye to bookworm.


What did you upgrade, host or guest system?


All was OK on bullseye, but on bookworm qemu-ga refuse to start with
following messages :

1702295113.963828: debug: disabling command: guest-get-devices
1702295113.963868: critical: error opening channel 
'/dev/virtio-ports/org.qemu.guest_agent.0': No such file or directory
1702295113.963873: critical: failed to create guest agent channel
1702295113.963875: critical: failed to initialize guest agent channel

The systemd command looks like :
[Unit]
Description=QEMU Guest Agent
BindsTo=dev-virtio\x2dports-org.qemu.guest_agent.0.device
After=dev-virtio\x2dports-org.qemu.guest_agent.0.device


This is the standard qga systemd unit file.
This unit file tells systemd to start qemu-ga *only* if
/dev/virtio-ports/org.qemu.guest_agent.0 device is present.

So it is either present and qga will start okay, or it is
not present, and systemd wont start it.  But not both.

I can't reproduce this issue, everything looks and works
like it is supposed to look and work.

Also, there are *lots* of bullseye VMs and hosts has been
upgraded to bookworm, and qemu-ga continues to work just
fine.

I've no idea what to get out of all this.

/mjt

Bug#1059040: libxml2: ABI change? (undefined references)

[Rene Engelhard]

Hi,

Am 25.12.23 um 16:31 schrieb Aron Xu:

Hi Rene,

On Wed, Dec 20, 2023 at 3:39 AM Rene Engelhard  wrote:

Am Tue, Dec 19, 2023 at 08:03:56PM +0100 schrieb Rene Engelhard:

LibreOffice builds (patch available), but doesn't yet build with 2.12.

"... but doesn't yet succeed the tests with 2.12"


That didn't change, see below.

[...]


Do we have removed symbols/removed versions here? (libxmlsec.so.1 was
not rebuilt)

After a rebuild of libxmlsec1 this link succeeds...


I see that you've committed this patch[1] to libreoffice, does this


Which is the above patch I mentioned to fix the *BUILD* with libxml2. 
After that applied I ran into the issue which resulted in thig bug 
report (see below in c))


The tests are still failing and there is no patch anywhere yet, see


It would actually be helpful to read because that one is said a) here 
and b) in the commit ("|Only the build, not the tests (yet)!")|



mean I can proceed to upload this version of libxml2 to unstable
without further action? Or is there anything else I should coordinate
with you to prevent breakage?


and c) you ignore the actual issue here at hand and that is that the new 
libxml2 breaks the ABI, causing at least libxmlsec to be needed to be 
rebuilt.



Regards,


Rene

Processed: severity of 1056787 is serious, severity of 1056789 is serious, severity of 1056791 is serious ...

[Debian Bug Tracking System]

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

> # cython 3 uploaded to unstable
> severity 1056787 serious
Bug #1056787 [src:astra-toolbox] astra-toolbox: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056789 serious
Bug #1056789 [src:basemap] basemap: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056791 serious
Bug #1056791 [src:azure-uamqp-python] azure-uamqp-python: ftbfs with cython 
3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056792 serious
Bug #1056792 [src:bitshuffle] bitshuffle: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056793 serious
Bug #1056793 [src:ceph] ceph: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056794 serious
Bug #1056794 [src:chemps2] chemps2: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056797 serious
Bug #1056797 [src:cypari2] cypari2: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056798 serious
Bug #1056798 [src:dioptas] dioptas: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056800 serious
Bug #1056800 [src:fpylll] fpylll: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056801 serious
Bug #1056801 [src:freeart] freeart: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056802 serious
Bug #1056802 [src:gensim] gensim: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056803 serious
Bug #1056803 [src:grpc] grpc: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056805 serious
Bug #1056805 [src:healpy] healpy: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056806 serious
Bug #1056806 [src:guiqwt] guiqwt: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056807 serious
Bug #1056807 [src:h5py] h5py: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056811 serious
Bug #1056811 [src:libgpuarray] libgpuarray: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056813 serious
Bug #1056813 [src:macs] macs: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056814 serious
Bug #1056814 [src:logbook] logbook: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056815 serious
Bug #1056815 [src:mdtraj] mdtraj: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056816 serious
Bug #1056816 [src:mayavi2] mayavi2: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056829 serious
Bug #1056829 [src:peewee] peewee: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056819 serious
Bug #1056819 [src:mlpy] mlpy: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056820 serious
Bug #1056820 [src:mpi4py] mpi4py: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056821 serious
Bug #1056821 [src:music] music: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056822 serious
Bug #1056822 [src:mpi4py-fft] mpi4py-fft: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056823 serious
Bug #1056823 [src:nipy] nipy: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056825 serious
Bug #1056825 [src:numpy] numpy: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056826 serious
Bug #1056826 [src:openems] openems: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056832 serious
Bug #1056832 [src:pplpy] pplpy: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable
> severity 1056827 serious
Bug #1056827 [src:opentsne] opentsne: ftbfs with cython 3.0.x
Severity set to 'serious' from 'important'
> # cython 3 uploaded to unstable

Bug#1059254: marked as done (cacti: CVE-2023-49084 CVE-2023-49086)

[Debian Bug Tracking System]

Your message dated Mon, 25 Dec 2023 20:49:36 +
with message-id 
and subject line Bug#1059254: fixed in cacti 1.2.26+ds1-1
has caused the Debian Bug report #1059254,
regarding cacti: CVE-2023-49084 CVE-2023-49086
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.)


-- 
1059254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cacti
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for cacti.

CVE-2023-49084[0]:
| Cacti is a robust performance and fault management framework and a
| frontend to RRDTool - a Time Series Database (TSDB). While using the
| detected SQL Injection and insufficient processing of the include
| file path, it is possible to execute arbitrary code on the server.
| Exploitation of the vulnerability is possible for an authorized
| user. The vulnerable component is the `link.php`. Impact of the
| vulnerability execution of arbitrary code on the server.

https://github.com/Cacti/cacti/commit/58a980f335980ab57659420053d89d4e721ae3fc

CVE-2023-49086[1]:
| Cacti is a robust performance and fault management framework and a
| frontend to RRDTool - a Time Series Database (TSDB). Bypassing an
| earlier fix (CVE-2023-39360) that leads to a DOM XSS attack.
| Exploitation of the vulnerability is possible for an authorized
| user. The vulnerable component is the `graphs_new.php`. Impact of
| the vulnerability - execution of arbitrary javascript code in the
| attacked user's browser. This issue has been patched in version
| 1.2.26.

https://github.com/Cacti/cacti/security/advisories/GHSA-wc73-r2vw-59pr

I think 
https://github.com/Cacti/cacti/commit/58a980f335980ab57659420053d89d4e721ae3fc
should address both, but please doublecheck.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-49084
https://www.cve.org/CVERecord?id=CVE-2023-49084
[1] https://security-tracker.debian.org/tracker/CVE-2023-49086
https://www.cve.org/CVERecord?id=CVE-2023-49086

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: cacti
Source-Version: 1.2.26+ds1-1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated cacti 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: Sun, 24 Dec 2023 21:46:33 +0100
Source: cacti
Architecture: source
Version: 1.2.26+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Cacti Maintainer 
Changed-By: Paul Gevers 
Closes: 1059254 1059286
Changes:
 cacti (1.2.26+ds1-1) unstable; urgency=medium
 .
   * postinst/postrm: ensure DEBHELPER content is always run
   * New upstream version 1.2.26+ds1
 Fixes the following vulnerabilities: CVE-2023-49084, CVE-2023-49085,
 CVE-2023-49086, CVE-2023-49088 CVE-2023-46490, CVE-2023-51448 and
 CVE-2023-50250 (Closes: #1059254, #1059286)
   * font-awesom-path.patch: refresh
   * Depends on node-dompurify and link purify.js instead of using upstream
 vendored version
Checksums-Sha1:
 da4aed01ee4a13d52cbfcd0f12348e4b74bce0d3 2231 cacti_1.2.26+ds1-1.dsc
 f5d11a7a734889eb41660d2717f1165b8f2e8d7f 24214045 
cacti_1.2.26+ds1.orig-docs-source.tar.gz
 64e1d3bf34784c1500f3181d5caab45ef289a35c 10834472 cacti_1.2.26+ds1.orig.tar.gz
 7f880149edd7e5668489a5638784b7873bdd38d4 57492 cacti_1.2.26+ds1-1.debian.tar.xz
Checksums-Sha256:
 e97c500888ceb1d076734a8e94d7ca37d6ccf6dde6990dff560fb35715d0e38f 2231 
cacti_1.2.26+ds1-1.dsc
 6913e0dbeb8f63c133e310d86b02351170cebcfb5350b341c5e5b90fda9257dd 24214045 
cacti_1.2.26+ds1.orig-docs-source.tar.gz
 0e96f66dbb77e8a43896be7627746353400a2cfcca185b89231d821cfb92fb65 10834472 
cacti_1.2.26+ds1.orig.tar.gz
 0491878922a2bfff4598bcfcf10577d35d0e2da62582c3d468eec7d7bb81bfe5 

Processed: src:lz4-java: fails to migrate to testing for too long: FTBFS on i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.8.0-4
Bug #1059447 [src:lz4-java] src:lz4-java: fails to migrate to testing for too 
long: FTBFS on i386
Marked as fixed in versions lz4-java/1.8.0-4.
Bug #1059447 [src:lz4-java] src:lz4-java: fails to migrate to testing for too 
long: FTBFS on i386
Marked Bug as done

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

Bug#1059447: src:lz4-java: fails to migrate to testing for too long: FTBFS on i386

[Paul Gevers]

Source: lz4-java
Version: 1.8.0-3
Severity: serious
Control: close -1 1.8.0-4
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:lz4-java has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable failed to 
build on i386.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=lz4-java



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1058245: libportal: FTBFS: dh_auto_test regression with python3-dbusmock (>= 0.30.0-2)

[Simon McVittie]

Control: retitle -1 libportal: FTBFS: dh_auto_test regression with 
python3-dbusmock (>= 0.30.0-2)

On Tue, 12 Dec 2023 at 09:11:51 +0100, Lucas Nussbaum wrote:
> >  TestRemoteDesktop.test_connect_to_eis 
> > _
> > 
> > self =  > testMethod=test_connect_to_eis>
> > 
> > def test_connect_to_eis(self):
> > >   setup = self.create_session(start_session=True)
> > 
> > pyportaltest/test_remotedesktop.py:428: 
> > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> > _ _ 
> > pyportaltest/test_remotedesktop.py:62: in create_session
> > self.setup_daemon(params=params, extra_templates=extra_templates)
> > pyportaltest/__init__.py:99: in setup_daemon
> > self.start_session_bus()
> > /usr/lib/python3/dist-packages/dbusmock/testcase.py:296: in 
> > start_session_bus
> > cls.__start_bus('session')
> > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> > _ _ 
> > 
> > cls = 
> > bus_type = 'session'
> > 
> > @classmethod
> > def __start_bus(cls, bus_type) -> None:
> > bustype = BusType(bus_type)
> > old_pid = getattr(DBusTestCase, f"{bustype.value}_bus_pid")
> > >   assert old_pid is None, f"PID {old_pid} still alive?"
> > E   AssertionError: PID 3954437 still alive?
> > 
> > /usr/lib/python3/dist-packages/dbusmock/testcase.py:284: AssertionError

(and many similar assertion errors)

These tests passed with python3-dbusmock 0.29.1-2, but fail starting
from version 0.30.0-2. I don't know whether this is a bug in libportal
or in python3-dbusmock, and I haven't bisected python3-dbusmock to an
exact commit.

smcv

Processed: Re: Bug#1058245: libportal: FTBFS: dh_auto_test regression with python3-dbusmock (>= 0.30.0-2)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libportal: FTBFS: dh_auto_test regression with python3-dbusmock 
> (>= 0.30.0-2)
Bug #1058245 [src:libportal] libportal: FTBFS with test failure: 
AssertionError: dbus-daemon PID still alive
Changed Bug title to 'libportal: FTBFS: dh_auto_test regression with 
python3-dbusmock (>= 0.30.0-2)' from 'libportal: FTBFS with test failure: 
AssertionError: dbus-daemon PID still alive'.

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

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

[Debian Bug Tracking System]

Your message dated Mon, 25 Dec 2023 19:34:17 +
with message-id 
and subject line Bug#1058320: fixed in drms 0.7.0-2
has caused the Debian Bug report #1058320,
regarding drms: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> /usr/lib/python3/dist-packages/setuptools/installer.py:134: UserWarning: 
> Unbuilt egg for drms [unknown version] (/<>)
>   pkg_resources.get_distribution('wheel')
> WARNING: The wheel package is not available.
> running config
> I: pybuild base:310: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> /usr/lib/python3/dist-packages/setuptools/installer.py:134: UserWarning: 
> Unbuilt egg for drms [unknown version] (/<>)
>   pkg_resources.get_distribution('wheel')
> WARNING: The wheel package is not available.
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> /usr/lib/python3/dist-packages/setuptools/installer.py:134: UserWarning: 
> Unbuilt egg for drms [unknown version] (/<>)
>   pkg_resources.get_distribution('wheel')
> WARNING: The wheel package is not available.
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_drms/build/drms
> copying drms/utils.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms
> copying drms/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms
> copying drms/version.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms
> copying drms/exceptions.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms
> copying drms/main.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms
> copying drms/_version.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms
> copying drms/client.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms
> copying drms/json.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms
> copying drms/config.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms
> creating /<>/.pybuild/cpython3_3.12_drms/build/drms/tests
> copying drms/tests/test_kis_basic.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms/tests
> copying drms/tests/test_series_info.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms/tests
> copying drms/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_drms/build/drms/tests
> copying drms/tests/test_jsoc_query.py -> 

Processed: [bts-link] source package src:python-werkzeug

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:python-werkzeug
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1058318 (http://bugs.debian.org/1058318)
> # Bug title: flask-login: FTBFS: dh_auto_test: error: pybuild --test 
> --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
> #  * https://github.com/pallets/werkzeug/issues/2704
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1058318 + fixed-upstream
Bug #1058318 [src:python-werkzeug] flask-login: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
Added tag(s) fixed-upstream.
> usertags 1058318 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: openmpi fortran

[Debian Bug Tracking System]

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

> block 1059377 by 1058876
Bug #1059377 [src:sundials] sundials: FTBFS: Imported target "MPI::MPI_Fortran" 
includes non-existent path
1059377 was not blocked by any bugs.
1059377 was not blocking any bugs.
Added blocking bug(s) of 1059377: 1058876
> thanks
Stopping processing here.

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

Bug#1056017: rlvm: FTBFS: boost1.83 transition

[Ying-Chun Liu (PaulLiu)]

Hi Bo YU,

Please NMU it and I'll sponsor it.

Yours,
Paul


On 2023/12/25 19:52, Bo YU wrote:

Source: rlvm
Version: 0.14-5.1
Followup-For: Bug #1056017
Tags: patch

Dear Maintainer,

I cost some time to fix the issue and patch attached. Please review it.

In order to fix the RC bug ASAP, I may do a NMU to mentor and find a
sponsor to upload it. Please feel free to break the process if there is
any issue.




OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1058558: marked as done (seqkit: FTBFS: make: *** [debian/rules:8: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 25 Dec 2023 17:20:50 +
with message-id 
and subject line Bug#1058558: fixed in seqkit 2.3.1+ds-2
has caused the Debian Bug report #1058558,
regarding seqkit: FTBFS: make: *** [debian/rules:8: binary] 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=golang --with=golang --builddirectory=build # 
> --sourcedirectory=seqkit
>dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=build
>dh_autoreconf -O--buildsystem=golang -O--builddirectory=build
>dh_auto_configure -O--buildsystem=golang -O--builddirectory=build
>dh_auto_build -O--buildsystem=golang -O--builddirectory=build
>   cd build && go install -trimpath -v -p 8 
> github.com/shenwei356/seqkit/benchmark github.com/shenwei356/seqkit/seqkit 
> github.com/shenwei356/seqkit/seqkit/cmd
> src/github.com/shenwei356/seqkit/seqkit/cmd/pair.go:32:2: cannot find package 
> "github.com/pkg/errors" in any of:
>   /usr/lib/go-1.21/src/github.com/pkg/errors (from $GOROOT)
>   /<>/build/src/github.com/pkg/errors (from $GOPATH)
> dh_auto_build: error: cd build && go install -trimpath -v -p 8 
> github.com/shenwei356/seqkit/benchmark github.com/shenwei356/seqkit/seqkit 
> github.com/shenwei356/seqkit/seqkit/cmd returned exit code 1
> make: *** [debian/rules:8: binary] Error 25


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

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: seqkit
Source-Version: 2.3.1+ds-2
Done: Nilesh Patra 

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

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated seqkit 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, 25 Dec 2023 22:26:02 +0530
Source: seqkit
Architecture: source
Version: 2.3.1+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 1046668 1058558
Changes:
 seqkit (2.3.1+ds-2) unstable; urgency=medium
 .
   * Update Build-Depends, fix with cme (Closes: #1058558)
   * Add d/clean to cleanup generate artifacts (Closes: #1046668)
Checksums-Sha1:
 16266bc24931359dfd7de371db6d6a4a2741fedd 2502 seqkit_2.3.1+ds-2.dsc
 6f9b3a2eeb7907f68a32229de13006cd6c6768da 10774768 
seqkit_2.3.1+ds-2.debian.tar.xz
 5583fb9dea764e18f68a96619c4694b080d8d2b0 10880 
seqkit_2.3.1+ds-2_source.buildinfo
Checksums-Sha256:
 143e83f111c3c047b52646824f8051d6263dadb455f884af2f8a0a8ac2f7dca1 2502 
seqkit_2.3.1+ds-2.dsc
 475b89d025f4cbaeb818f57bf4b3de3643bfd1cc3e03c6e8367a8fa39f87f9c4 10774768 
seqkit_2.3.1+ds-2.debian.tar.xz
 6b11a074bb2faede0174317813331d4a7f22c8fd217e22b2a8ebc444829dfe29 10880 
seqkit_2.3.1+ds-2_source.buildinfo
Files:
 2fbacb07368760bf2670f7103c4e992c 2502 science optional seqkit_2.3.1+ds-2.dsc
 25ffc95461c2f491b5a82f8c9f8e68ec 10774768 science optional 

Bug#1056093: marked as done (casparcg-server: FTBFS: boost1.83 transition)

[Debian Bug Tracking System]

Your message dated Mon, 25 Dec 2023 17:19:03 +
with message-id 
and subject line Bug#1056093: fixed in casparcg-server 2.3.3+dfsg-3.2
has caused the Debian Bug report #1056093,
regarding casparcg-server: FTBFS: boost1.83 transition
to be marked as done.

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

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


-- 
1056093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: casparcg-server
Version: 2.3.3+dfsg-3.1
Severity: normal
User: gl...@debian.org
Usertags: boost183 ftbfs-boost183-transition

Hi,

we are preparing the transition of all libs on the new boost 1.83. During the
rebuild of packages against this library it was identified that probably your
package fails to build.

Relevant part (hopefully):

-

[ 14%] Precompiling StdAfx.h for core (C++)
cd 
/mnt/mod01/build_results/casparcg-server/casparcg-server/obj-x86_64-linux-gnu/core
 && /usr/bin/c++ 
@/mnt/mod01/build_results/casparcg-server/casparcg-server/obj-x86_64-linux-gnu/core/core_pch/compile_flags.rsp
 -x c++-header -o 
/mnt/mod01/build_results/casparcg-server/casparcg-server/obj-x86_64-linux-gnu/core/core_pch/StdAfx.h.gch/.c++
 
/mnt/mod01/build_results/casparcg-server/casparcg-server/obj-x86_64-linux-gnu/core/core_pch/StdAfx.h
In file included from 
/mnt/mod01/build_results/casparcg-server/casparcg-server/obj-x86_64-linux-gnu/core/core_pch/StdAfx.h:39:
/usr/include/boost/timer.hpp:21:3: error: #error This header is deprecated and 
will be removed. (You can define BOOST_TIMER_ENABLE_DEPRECATED to suppress this 
error.)
   21 | # error This header is deprecated and will be removed. (You can define 
BOOST_TIMER_ENABLE_DEPRECATED to suppress this error.)


-

To reproduce this behavior, you can install  -dev Boost packages from the
experimental repository, as shown in the following command:

  apt install libboost-dev -t experimental


The full build log is available from:
https://people.debian.org/~gladk/boost183/casparcg-server.log

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

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 are unable to reproduce this, please provide a build log and diff it
so that we can identify any relevant changes that may have occurred in the 
meantime.
--- End Message ---
--- Begin Message ---
Source: casparcg-server
Source-Version: 2.3.3+dfsg-3.2
Done: Anton Gladky 

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated casparcg-server 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, 25 Dec 2023 18:09:38 +0100
Source: casparcg-server
Architecture: source
Version: 2.3.3+dfsg-3.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Anton Gladky 
Closes: 1056093
Changes:
 casparcg-server (2.3.3+dfsg-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS against boost1.83. (Closes: #1056093)
Checksums-Sha1:
 3bd6912d0e20d65768616bb2a8ee5a355a6d19b2 2627 
casparcg-server_2.3.3+dfsg-3.2.dsc
 03ec76dadced1c2425bc4b4487c6b7fb2cc42bb9 12024 
casparcg-server_2.3.3+dfsg-3.2.debian.tar.xz
 cbff79116ab37193f74498f06ba34f30f77487a3 14025 
casparcg-server_2.3.3+dfsg-3.2_source.buildinfo
Checksums-Sha256:
 019796d90e9dfc093e5488219501b9b732cda6a6cef230c25614bc826f5b2f8d 2627 
casparcg-server_2.3.3+dfsg-3.2.dsc
 21d81f7c22196ab9e207f4b814a98ac1d96f3ac40acc02c197d5f3e5dfc698be 12024 
casparcg-server_2.3.3+dfsg-3.2.debian.tar.xz
 ab286cfa0a79b4acf1cd12e3aff46464416746d02bcedfc5cf918a42a28b8d4e 14025 
casparcg-server_2.3.3+dfsg-3.2_source.buildinfo
Files:
 55cbe1ffe74b461e61cecbab055c9883 2627 contrib/video optional 

Bug#1058506: marked as done (golang-github-shenwei356-util: FTBFS: make: *** [debian/rules:4: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 25 Dec 2023 17:03:59 +
with message-id 
and subject line Bug#1058506: fixed in golang-github-shenwei356-util 0.5.0-2
has caused the Debian Bug report #1058506,
regarding golang-github-shenwei356-util: FTBFS: make: *** [debian/rules:4: 
binary] 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.)


-- 
1058506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-shenwei356-util
Version: 0.5.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 8 
> github.com/shenwei356/util/bytesize github.com/shenwei356/util/byteutil 
> github.com/shenwei356/util/cliutil github.com/shenwei356/util/exec 
> github.com/shenwei356/util/math github.com/shenwei356/util/numbers 
> github.com/shenwei356/util/pathutil github.com/shenwei356/util/randutil 
> github.com/shenwei356/util/stats github.com/shenwei356/util/stringutil 
> github.com/shenwei356/util/struct/sa github.com/shenwei356/util/struct/stack
> src/github.com/shenwei356/util/cliutil/others.go:9:2: cannot find package 
> "github.com/pkg/errors" in any of:
>   /usr/lib/go-1.21/src/github.com/pkg/errors (from $GOROOT)
>   /<>/_build/src/github.com/pkg/errors (from $GOPATH)
> dh_auto_build: error: cd _build && go install -trimpath -v -p 8 
> github.com/shenwei356/util/bytesize github.com/shenwei356/util/byteutil 
> github.com/shenwei356/util/cliutil github.com/shenwei356/util/exec 
> github.com/shenwei356/util/math github.com/shenwei356/util/numbers 
> github.com/shenwei356/util/pathutil github.com/shenwei356/util/randutil 
> github.com/shenwei356/util/stats github.com/shenwei356/util/stringutil 
> github.com/shenwei356/util/struct/sa github.com/shenwei356/util/struct/stack 
> returned exit code 1
> make: *** [debian/rules:4: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/golang-github-shenwei356-util_0.5.0-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: golang-github-shenwei356-util
Source-Version: 0.5.0-2
Done: Nilesh Patra 

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

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-shenwei356-util 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, 25 Dec 2023 22:17:45 +0530
Source: golang-github-shenwei356-util
Architecture: source
Version: 0.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Nilesh Patra 
Closes: 1058506
Changes:
 golang-github-shenwei356-util (0.5.0-2) unstable; urgency=medium
 .
   * Update B-D and Depends according to go.mod 

Processed: Bug#1058558 marked as pending in seqkit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058558 [src:seqkit] seqkit: FTBFS: make: *** [debian/rules:8: binary] 
Error 25
Added tag(s) pending.

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

Bug#1058558: marked as pending in seqkit

[Nilesh Patra]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/seqkit/-/commit/21e6afbbd44d78695e03765e912121dc82bc8966


Update Build-Depends, fix with cme (Closes: #1058558)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058558

Processed: Bug#1058506 marked as pending in golang-github-shenwei356-util

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058506 [src:golang-github-shenwei356-util] golang-github-shenwei356-util: 
FTBFS: make: *** [debian/rules:4: binary] Error 25
Added tag(s) pending.

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

Bug#1058506: marked as pending in golang-github-shenwei356-util

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #1058506 in golang-github-shenwei356-util reported by you has been fixed in 
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-github-shenwei356-util/-/commit/be7324447985d49092b125bac93cc9f8d08930f1


Update B-D and Depends according to go.mod (Closes: #1058506)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058506

Bug#1056088: marked as done (bagel: FTBFS: boost1.83 transition)

[Debian Bug Tracking System]

Your message dated Mon, 25 Dec 2023 16:19:11 +
with message-id 
and subject line Bug#1056088: fixed in bagel 1.2.2-7
has caused the Debian Bug report #1056088,
regarding bagel: FTBFS: boost1.83 transition
to be marked as done.

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

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


-- 
1056088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bagel
Version: 1.2.2-6
Severity: normal
User: gl...@debian.org
Usertags: boost183 ftbfs-boost183-transition

Hi,

we are preparing the transition of all libs on the new boost 1.83. During the
rebuild of packages against this library it was identified that probably your
package fails to build.

Relevant part (hopefully):

-

/usr/include/boost/property_tree/ptree_serialization.hpp:66:24: error: 
‘library_version_type’ in namespace ‘bsa’ does not name a type
   66 | const bsa::library_version_type library_version(
  |^~~~
/usr/include/boost/property_tree/ptree_serialization.hpp:69:21: error: 
‘library_version_type’ is not a member of ‘bsa’; did you mean 
‘boost::serialization::library_version_type’?
   69 | if(bsa::library_version_type(3) < library_version){
  | ^~~~


-

To reproduce this behavior, you can install  -dev Boost packages from the
experimental repository, as shown in the following command:

  apt install libboost-dev -t experimental


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/bagel_1.2.2-6_unstable_boost181.log

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

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 are unable to reproduce this, please provide a build log and diff it
so that we can identify any relevant changes that may have occurred in the 
meantime.
--- End Message ---
--- Begin Message ---
Source: bagel
Source-Version: 1.2.2-7
Done: Anton Gladky 

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated bagel 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, 25 Dec 2023 17:08:13 +0100
Source: bagel
Architecture: source
Version: 1.2.2-7
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Anton Gladky 
Closes: 1056088
Changes:
 bagel (1.2.2-7) unstable; urgency=medium
 .
   * Team upload.
   * Fix FTBFS against boost 1.83. (Closes: #1056088)
Checksums-Sha1:
 6ad21da34b39acdd1ae17b3e5a8f82a10e3c0127 2219 bagel_1.2.2-7.dsc
 05188c4959a826f854ffb6633716d8ba85473557 8876 bagel_1.2.2-7.debian.tar.xz
 7941a2ff28ff9e139e3269f66408523a0fdc6a97 7094 bagel_1.2.2-7_source.buildinfo
Checksums-Sha256:
 634b7c5c3d93368bfecc79db19ad4a80ebc81c85177101888d48cd91a7e45aa9 2219 
bagel_1.2.2-7.dsc
 749485cfab45d692050c5f47a9d4a04a69022149cc53ef1edd0b8edc2d044623 8876 
bagel_1.2.2-7.debian.tar.xz
 267ba2a79be7542bea422f5a2acf20ecd23ce3b676014352f139a7ae335b27cf 7094 
bagel_1.2.2-7_source.buildinfo
Files:
 22d0b58937224c1e60bc5e94a9c32b13 2219 science optional bagel_1.2.2-7.dsc
 b948d4af307812943635a1e4d8485d3d 8876 science optional 
bagel_1.2.2-7.debian.tar.xz
 da658e66cc05fee634e11359f53cadd1 7094 science optional 
bagel_1.2.2-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmWJqZ8ACgkQ0+Fzg8+n
/waT0w//QjfXhLT5W3zfgju1RS0S6q7QK3vC1WtUmrPsRWN6MSbQJuLrnsZ/qzLD
vfyRnZqhelH8IFN4y1mlg5t4bJ/UChd2qlhhY5rYI/Jc2wwH3r/xC7r6WUnWz4ZG
1xiNOO7ROkOoj6QYMTZgdOA8MR337kmGTBAH4uNpVbwSZgEwwH3s0SAb2FtIeCiY
PIPxfLq1Do+ORQALGMv9mPxLZQff28aVFSujWc2AO55m3BFAZ+jUdGM7WotntkfE

Processed: Bug#1056088 marked as pending in bagel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1056088 [src:bagel] bagel: FTBFS: boost1.83 transition
Added tag(s) pending.

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

Bug#1056088: marked as pending in bagel

[Anton Gladky]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debichem-team/bagel/-/commit/2dc6e7c37ac418531088df93d512dfe6fc9aa501


Fix FTBFS against boost 1.83. (Closes: #1056088)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056088

Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices

[Cyril Brulebois]

Julian Andres Klode  (2023-12-25):
> We picked the previous XFS patch for extent parsing but did not pick
> this one because it had not been merged at that point yet, the fix
> only got merged two weeks or so ago, and we didn't want to take chances
> and pick it ahead of time as it's security critical code (filesystem
> parsing is where all the security bugs live!).
> 
> The release was supposed to be out 2 weeks ago but got pushed back
> another week to last week's release, sadly.

Thanks for all the details, and sorry if it appeared I was chasing you
down; I just stumbled upon this again while re-testing various things,
and was merely wondering whether things were.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices

[Julian Andres Klode]

On Mon, Dec 25, 2023 at 04:33:36PM +0100, Cyril Brulebois wrote:
> Julian Andres Klode  (2023-12-25):
> > The final grub 2.12 that includes the fix should hit unstable in the
> > middle of January. As you might be aware many are busy with family
> > stuff and holiday celebrations right now.
> 
> Sure. I wasn't aware an upstream release was in the pipes, only that
> patches have existed and been confirmed OK for close to 2 months.

We picked the previous XFS patch for extent parsing but did not pick
this one because it had not been merged at that point yet, the fix
only got merged two weeks or so ago, and we didn't want to take chances
and pick it ahead of time as it's security critical code (filesystem
parsing is where all the security bugs live!).

The release was supposed to be out 2 weeks ago but got pushed back
another week to last week's release, sadly.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices

[Cyril Brulebois]

Julian Andres Klode  (2023-12-25):
> The final grub 2.12 that includes the fix should hit unstable in the
> middle of January. As you might be aware many are busy with family
> stuff and holiday celebrations right now.

Sure. I wasn't aware an upstream release was in the pipes, only that
patches have existed and been confirmed OK for close to 2 months.

> As always though it stands to reason that this is a change that should
> (have been) reverted in xfsprogs first until a grub that understands
> it has been released in a stable point release such that you can use a
> stable grub to inspect an XFS filesystem created by a trixie xfsprogs.

The more we tick boxes in the compatibility matrix, the happier, yes.

> It seems the bug has been wrongly reassigned instead of being cloned
> and reassigned, so I'm cloning it back to xfsprogs.

Right, this would have been easier to track if debian-boot@ had been put
(and kept) in the loop all along.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1059040: libxml2: ABI change? (undefined references)

[Aron Xu]

Hi Rene,

On Wed, Dec 20, 2023 at 3:39 AM Rene Engelhard  wrote:
>
> Am Tue, Dec 19, 2023 at 08:03:56PM +0100 schrieb Rene Engelhard:
> > LibreOffice builds (patch available), but doesn't yet build with 2.12.
>
> "... but doesn't yet succeed the tests with 2.12"
>
> > S=/home/rene/LibreOffice/git/libreoffice-24-2 && I=$S/instdir && 
> > W=$S/workdir &&  /usr/bin/ccache x86_64-linux-gnu-g++ -pthread  
> > -flto=jobserver -fuse-linker-plugin -O2  -Wl,-z,origin 
> > '-Wl,-rpath,$ORIGIN/../Library' -Wl,-rpath-link,$I/program  -Wl,-z,defs 
> > -Wl,-rpath-link,/lib:/usr/lib -Wl,-z,combreloc  -Wl,--hash-style=gnu  
> > -Wl,-Bsymbolic-functions -L$W/LinkTarget/StaticLibrary -L$I/sdk/lib  
> > -L$I/program  -L$I/program  -L$W/LinkTarget/Library -ffat-lto-objects 
> > -Wl,-z,relro$W/CxxObject/xmlsecurity/workben/pdfverify.o   
> > -Wl,--start-group-Wl,--end-group -Wl,--no-as-needed -luno_cppu 
> > -luno_cppuhelpergcc3 -luno_sal -lxmlsecurity -lmergedlo  -o 
> > $W/LinkTarget/Executable/pdfverify
> > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
> > `xmlIOFTPMatch@LIBXML2_2.4.30'
> > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
> > `xmlNanoFTPCleanup@LIBXML2_2.4.30'
> > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
> > `xmlIOFTPOpen@LIBXML2_2.4.30'
> > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
> > `xmlIOFTPClose@LIBXML2_2.4.30'
> > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
> > `xmlIOFTPRead@LIBXML2_2.4.30'
> > /usr/bin/ld: /lib/x86_64-linux-gnu/libxmlsec1.so.1: undefined reference to 
> > `xmlNanoFTPInit@LIBXML2_2.4.30'
> > collect2: error: ld returned 1 exit status
> > make[3]: *** 
> > [/home/rene/LibreOffice/git/libreoffice-24-2/solenv/gbuild/LinkTarget.mk:853:
> >  
> > /home/rene/LibreOffice/git/libreoffice-24-2/workdir/LinkTarget/Executable/pdfverify]
> >  Error 1
> >
> > Do we have removed symbols/removed versions here? (libxmlsec.so.1 was
> > not rebuilt)
>
> After a rebuild of libxmlsec1 this link succeeds...
>

I see that you've committed this patch[1] to libreoffice, does this
mean I can proceed to upload this version of libxml2 to unstable
without further action? Or is there anything else I should coordinate
with you to prevent breakage?


Regards,
Aron Xu

[1]https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/-/commit/56d340483b0285c079c7ac08ddf441457d40b955

Bug#1033516: marked as done (twisted: autopkgtest fails: failures=21, errors=35)

[Debian Bug Tracking System]

Your message dated Mon, 25 Dec 2023 15:05:51 +
with message-id 
and subject line Bug#1033516: fixed in twisted 23.10.0-1
has caused the Debian Bug report #1033516,
regarding twisted: autopkgtest fails: failures=21, errors=35
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.)


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

Source: twisted
Version: 22.4.0-4
Severity: serious
Tags: bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Control: found -1 18.9.0-3

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. Can you 
please investigate the situation and fix it? I copied some of the output 
at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/t/twisted/32195474/log.gz

twisted.test.test_application.LoadingTests.test_simpleStoreAndLoad
===
[ERROR]
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/twisted/test/test_tcp.py", line 
1232, in clientDisconnected

hamcrest.assert_that(
  File "/usr/lib/python3/dist-packages/hamcrest/core/assert_that.py", 
line 58, in assert_that

_assert_match(actual=actual, matcher=matcher, reason=reason)
  File "/usr/lib/python3/dist-packages/hamcrest/core/assert_that.py", 
line 73, in _assert_match

raise AssertionError(description)
builtins.AssertionError:
Expected: a sequence containing [a sequence containing ['SSL routines', 
('SSL_write' or 'ssl_write_internal'), 'protocol is shutdown']]

 but: item 0: item 1: was ''


twisted.test.test_ssl.StolenTCPTests.test_properlyCloseFiles
---
Ran 11861 tests in 1260.901s

FAILED (skips=1673, failures=21, errors=35, successes=10149)


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 23.10.0-1
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated twisted 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, 25 Dec 2023 10:49:12 -0400
Source: twisted
Architecture: source
Version: 23.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 1033516 1034499 1054913
Changes:
 twisted (23.10.0-1) unstable; urgency=medium
 .
   [ Matthias Klose ]
   * Remove myself as uploader.
 .
   [ Stefano Rivera ]
   * Add myself as an uploader.
   * New upstream release.
 - Resolves CVE-2023-46137: Disordered HTTP pipeline response in
   twisted.web. (Closes: #1054913)
   * Refresh patches.
   * Drop patches, superseded upstream:
 - debian-hacks/Sphinx-Set-html_theme-to-twisteddefault.patch
 - documentation/pydoctor-22.7.patch
 - Implement-twisted.python.failure._Code.co_positions.patch
 - Deprecate-twisted.web.resource.ErrorPage-and-spawn.patch
 - Implement-twisted.web.pages.patch
 - Update-imports-to-avoid-warnings.patch
 - Update-the-docs.patch
 - Address-DummyRequest-MyPy-issue.patch
 - Address-IRenderable-MyPy-issue.patch
 - Failing-test.patch
 - Fix-NameVirtualHost-HTML-injection-vulnerability.patch
 - Fix-references-to-twisted.pages.patch
 - Call-the-superclass-constructor-via-private-alias.patch
 - twisted.web.pages.-ErrorPage-errorPage.patch
 - tests/Tests-remove-spurious-test-for-illegal-whitespace-in-xmlns.patch
 - Add-CVE-to-newsfragment.patch
 - 

Bug#1058890: more tests

[Dr . André Desgualdo Pereira]

If I use "echo mem > /sys/power/state" instead of systemctl to suspend, the 
result is the same, ie, the notebook doesn't seem to fully wake up, when trying 
to wake up from suspend, the screen stays black.
The CAPS LOCK led doesn't change when pressing the CAPS LOCK button, but the 
computer can shutdown with "Alt + SysRq + B". 

-- 
André Desgualdo Pereira

Processed: [pymatgen] Bug #1058040: forward to upstream fix

[Debian Bug Tracking System]

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

> forwarded 1058040 
> https://github.com/materialsproject/pymatgen/pull/3454/commits/a8199919b4630828da
Bug #1058040 [src:pymatgen] pymatgen: FTBFS with Python 3.12
Set Bug forwarded-to-address to 
'https://github.com/materialsproject/pymatgen/pull/3454/commits/a8199919b4630828da'.
> thanks
Stopping processing here.

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

Bug#1056017: rlvm: FTBFS: boost1.83 transition

[Bo YU]

Source: rlvm
Version: 0.14-5.1
Followup-For: Bug #1056017
Tags: patch

Dear Maintainer,

I cost some time to fix the issue and patch attached. Please review it.

In order to fix the RC bug ASAP, I may do a NMU to mentor and find a
sponsor to upload it. Please feel free to break the process if there is
any issue.


-- 
Regards,
--
  Bo YU

diff -Nru rlvm-0.14/debian/changelog rlvm-0.14/debian/changelog
--- rlvm-0.14/debian/changelog  2021-10-04 03:16:33.0 +0800
+++ rlvm-0.14/debian/changelog  2023-12-25 15:40:26.0 +0800
@@ -1,3 +1,11 @@
+rlvm (0.14-5.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs on boost1.83. (Closes: #1056017)
+  * Use libboost-timer-dev instead of libboost-date-time-dev.
+
+ -- Bo YU   Mon, 25 Dec 2023 15:40:26 +0800
+
 rlvm (0.14-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru rlvm-0.14/debian/control rlvm-0.14/debian/control
--- rlvm-0.14/debian/control2021-10-04 03:16:13.0 +0800
+++ rlvm-0.14/debian/control2023-12-25 15:40:26.0 +0800
@@ -4,7 +4,6 @@
 Maintainer: Ying-Chun Liu (PaulLiu) 
 Build-Depends: debhelper (>= 10),
google-mock,
-   libboost-date-time-dev,
libboost-dev,
libboost-filesystem-dev,
libboost-iostreams-dev,
@@ -12,6 +11,7 @@
libboost-python-dev,
libboost-serialization-dev,
libboost-thread-dev,
+   libboost-timer-dev,
libfreetype6-dev,
libgl1-mesa-dev,
libglew-dev,
diff -Nru rlvm-0.14/debian/patches/005_fix_boost_ftbfs.patch 
rlvm-0.14/debian/patches/005_fix_boost_ftbfs.patch
--- rlvm-0.14/debian/patches/005_fix_boost_ftbfs.patch  1970-01-01 
07:30:00.0 +0730
+++ rlvm-0.14/debian/patches/005_fix_boost_ftbfs.patch  2023-12-25 
15:40:26.0 +0800
@@ -0,0 +1,65 @@
+Description: fix ftbfs on boost1.83 
+Author: Bo YU  
+Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056017 
+Last-Update: 2023-12-25
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/vendor/wxInclude.cpp
 b/vendor/wxInclude.cpp
+@@ -18,7 +18,7 @@
+ #include 
+ #include 
+ #include 
+-#include 
++#include 
+ 
+ namespace po = boost::program_options;
+ namespace fs = boost::filesystem;
+@@ -207,7 +207,7 @@
+ if ( opt.count( "input-file" ) || opt.count( "input-type" ) ) {
+   if ( opt.count( "output-file" ) ) { 
+   /* Create timer */
+-  boost::timer timer;
++  boost::timer::cpu_timer timer;
+ 
+   /* Create output file */
+   std::string headername( opt[ "output-file" 
].as() );
+@@ -361,7 +361,7 @@
+ 
+   /* Show status */
+ if (!silent)
+-  std::cout << "Build  : " << timer.elapsed() << "s needed 
for conversion of " << list.size() << " files." << std::endl;
++  std::cout << "Build  : " << timer.elapsed().user<< "s 
needed for conversion of " << list.size() << " files." << std::endl;
+   } else {
+   throw std::invalid_argument( "No output 
defined!" );
+   }
+--- a/SConstruct
 b/SConstruct
+@@ -81,6 +81,7 @@
+   "boost_iostreams",
+   "boost_filesystem",
+   "boost_date_time",
++  "boost_timer",
+   "boost_thread",
+   "boost_system"])
+ 
+--- a/src/systems/base/system.h
 b/src/systems/base/system.h
+@@ -33,6 +33,7 @@
+ #include 
+ 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
+--- a/src/utilities/file.h
 b/src/utilities/file.h
+@@ -31,6 +31,7 @@
+ #include 
+ 
+ #include 
++#include 
+ #include 
+ #include 
+ 
diff -Nru rlvm-0.14/debian/patches/series rlvm-0.14/debian/patches/series
--- rlvm-0.14/debian/patches/series 2020-02-01 10:20:05.0 +0800
+++ rlvm-0.14/debian/patches/series 2023-12-25 15:37:58.0 +0800
@@ -2,3 +2,4 @@
 002_include-iostream.patch
 003_use_pkg-config_for_freetype2.patch
 004_port_to_python3.patch
+005_fix_boost_ftbfs.patch


signature.asc
Description: PGP signature

Bug#1059436: lxappearance segmentation fault

[Karine Crèvecœur]

Package: lxappearance
Version: 0.6.3-5
Severity: grave

Hi,

Wen I start lxappearance that leads to the following messages:

(lxappearance:10707): Gtk-WARNING **: 12:14:33.248: Theme parsing error: 
:1:17: Expected a string.
segmentation fault

I tried to not use theme at all, I moved the ~/.config/gtk-* to another
place (under ~/dot.config/ to be precise). The messages are the same.

With gdb I saw the issue came in cairo_surface_get_content () from
/lib/x86_64-linux-gnu/libcairo.so.2

I tried to run the application with:
  $ LANG=C lxpappearance
It was the same issue.

system information:
debian/sid
architecture amd64

kernel: linux 6.6.8 (uname -r)
Locale: LANG=fr_FR.utf8
shell: /bin/bash
init: systemd

apt-cache depends lxappearance:
  Dépend: libc6
  Dépend: libdbus-1-3
  Dépend: libgdk-pixbuf-2.0-0
  Dépend: libglib2.0-0
  Dépend: libgtk-3-0
  Dépend: libx11-6
  Recommande: lxde-settings-daemon
lxsession

Cheers.
--
Karine Crévecœur

Bug#1059431: linux: FTBFS on mips64el: make[3]: *** [/<>/Makefile:246: __sub-make] Error 2

[Bastian Blank]

On Mon, Dec 25, 2023 at 11:38:17AM +0100, Sebastian Ramacher wrote:
> (sorry, I wasn't able to find an error, so this is the end of the build
> log.)

The error is:

| Relocations overflow available space!
| Please adjust CONFIG_RELOCATION_TABLE_SIZE to at least 0x001d3000
| make[6]: *** [/<>/arch/mips/Makefile.postlink:28: vmlinux] Error 
1
| make[6]: *** Deleting file 'vmlinux'
| make[5]: *** [/<>/scripts/Makefile.vmlinux:37: vmlinux] Error 2
| make[4]: *** [/<>/Makefile:1176: vmlinux] Error 2
| make[4]: *** Waiting for unfinished jobs

Bastian

-- 
The sight of death frightens them [Earthers].
-- Kras the Klingon, "Friday's Child", stardate 3497.2

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

[Rafael Laboissière]

* Rafael Laboissière  [2023-12-22 04:36]:


* Sébastien Villemot  [2023-12-21 15:23]:


Le jeudi 21 décembre 2023 à 08:49 +0100, Rafael Laboissière a écrit :

* Santiago Vila  [2023-12-20 22:03]:


El 20/12/23 a las 21:08, Rafael Laboissière escribió:

HOME := $(shell mktemp -d)

so that the same directory is never used twice between consecutive builds.


Yes, this is a much better solution. Thanks for the 
suggestion. I am just wondering: is there a simple way to 
delete the temporary directory after he build is finished ?


I don't know, but most people build packages in 
temporary/disposable chroots, so if the package just writes a 
few files which are also small, it's not something for which I 
would worry too much.


Yes, it not really a worrisome issue. However, I have just noticed 
that the solution that you proposed with mktemp is a little bit 
intrusive. Indeed, a new temporary directory is created at each 
invocation of debain/rules, such that I end up with five 
/tmp/tmp.* directories after package building, with only the last 
one being actually used. I will try another approach, probably by 
changing the dh_octave_check script, which is the one that 
eventually needs a writable $HOME directory.


Note that within the context of a shell script, the following 
ensures that the directory is automatically deleted upon exit:


tmpdir=$(mktemp -d) 
cleanup () 
{ 
   rm -rf "${tmpdir}" 
} 
trap cleanup EXIT


Thanks, Sébastien.

I think that it is possible to do something similar in Perl (the 
language in which dh_octave_check is written) by using the %SIG hash. 
I will take a look at it.


I got confused, sorry. Actually, dh_octave_check is written in Shell.

I have uploaded version 1.6.0 of dh-octave with the needed changes.

Best,

Rafael

Bug#1059431: linux: FTBFS on mips64el: make[3]: *** [/<>/Makefile:246: __sub-make] Error 2

[Sebastian Ramacher]

Source: linux
Version: 6.6.8-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=linux=mips64el=6.6.8-1=1703469825=0

  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/nfc/nci/nci.ko net/nfc/nci/nci.o 
net/nfc/nci/nci.mod.o;  /usr/bin/make -f 
/<>/arch/mips/Makefile.postlink net/nfc/nci/nci.ko
# LD [M]  net/nfc/nfc_digital.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/nfc/nfc_digital.ko net/nfc/nfc_digital.o 
net/nfc/nfc_digital.mod.o;  /usr/bin/make -f 
/<>/arch/mips/Makefile.postlink net/nfc/nfc_digital.ko
# LD [M]  net/psample/psample.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/psample/psample.ko net/psample/psample.o 
net/psample/psample.mod.o;  /usr/bin/make -f 
/<>/arch/mips/Makefile.postlink net/psample/psample.ko
# LD [M]  net/ife/ife.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/ife/ife.ko net/ife/ife.o net/ife/ife.mod.o;  
/usr/bin/make -f /<>/arch/mips/Makefile.postlink net/ife/ife.ko
# LD [M]  net/openvswitch/openvswitch.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/openvswitch/openvswitch.ko 
net/openvswitch/openvswitch.o net/openvswitch/openvswitch.mod.o;  /usr/bin/make 
-f /<>/arch/mips/Makefile.postlink net/openvswitch/openvswitch.ko
# LD [M]  net/openvswitch/vport-vxlan.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/openvswitch/vport-vxlan.ko 
net/openvswitch/vport-vxlan.o net/openvswitch/vport-vxlan.mod.o;  /usr/bin/make 
-f /<>/arch/mips/Makefile.postlink net/openvswitch/vport-vxlan.ko
# LD [M]  net/openvswitch/vport-geneve.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/openvswitch/vport-geneve.ko 
net/openvswitch/vport-geneve.o net/openvswitch/vport-geneve.mod.o;  
/usr/bin/make -f /<>/arch/mips/Makefile.postlink 
net/openvswitch/vport-geneve.ko
# LD [M]  net/openvswitch/vport-gre.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/openvswitch/vport-gre.ko 
net/openvswitch/vport-gre.o net/openvswitch/vport-gre.mod.o;  /usr/bin/make -f 
/<>/arch/mips/Makefile.postlink net/openvswitch/vport-gre.ko
# LD [M]  net/vmw_vsock/vsock.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/vmw_vsock/vsock.ko net/vmw_vsock/vsock.o 
net/vmw_vsock/vsock.mod.o;  /usr/bin/make -f 
/<>/arch/mips/Makefile.postlink net/vmw_vsock/vsock.ko
# LD [M]  net/vmw_vsock/vsock_diag.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/vmw_vsock/vsock_diag.ko net/vmw_vsock/vsock_diag.o 
net/vmw_vsock/vsock_diag.mod.o;  /usr/bin/make -f 
/<>/arch/mips/Makefile.postlink net/vmw_vsock/vsock_diag.ko
# LD [M]  net/vmw_vsock/vmw_vsock_virtio_transport.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/vmw_vsock/vmw_vsock_virtio_transport.ko 
net/vmw_vsock/vmw_vsock_virtio_transport.o 
net/vmw_vsock/vmw_vsock_virtio_transport.mod.o;  /usr/bin/make -f 
/<>/arch/mips/Makefile.postlink 
net/vmw_vsock/vmw_vsock_virtio_transport.ko
# LD [M]  net/vmw_vsock/vmw_vsock_virtio_transport_common.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/vmw_vsock/vmw_vsock_virtio_transport_common.ko 
net/vmw_vsock/vmw_vsock_virtio_transport_common.o 
net/vmw_vsock/vmw_vsock_virtio_transport_common.mod.o;  /usr/bin/make -f 
/<>/arch/mips/Makefile.postlink 
net/vmw_vsock/vmw_vsock_virtio_transport_common.ko
# LD [M]  net/vmw_vsock/vsock_loopback.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/vmw_vsock/vsock_loopback.ko 
net/vmw_vsock/vsock_loopback.o net/vmw_vsock/vsock_loopback.mod.o;  
/usr/bin/make -f /<>/arch/mips/Makefile.postlink 
net/vmw_vsock/vsock_loopback.ko
# LD [M]  net/nsh/nsh.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/nsh/nsh.ko net/nsh/nsh.o net/nsh/nsh.mod.o;  
/usr/bin/make -f /<>/arch/mips/Makefile.postlink net/nsh/nsh.ko
# LD [M]  net/hsr/hsr.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/hsr/hsr.ko net/hsr/hsr.o net/hsr/hsr.mod.o;  
/usr/bin/make -f /<>/arch/mips/Makefile.postlink net/hsr/hsr.ko
# LD [M]  net/qrtr/qrtr.ko
  ld -r -m elf64ltsmip -z noexecstack --no-warn-rwx-segments --build-id=sha1  
-T scripts/module.lds -o net/qrtr/qrtr.ko net/qrtr/qrtr.o 

Bug#1058553: node-js-sdsl: FTBFS: TypeError: Cannot set property constructor of [object Object] which has only a getter

[Ying-Chun Liu (PaulLiu)]

Hi Yadd,

I think this FTBFS is caused by TTSC introduced by commit 
a3371fa529c30a579f52f507b6e5fcd902d30505.

Can I revert this change? Or we need to upgrade TTSC?

Yours,
Paul


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1059424: Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices

[Julian Andres Klode]

Control: tag 1059424 patch

(switching to the cloned xfsprogs bug)

On Mon, Dec 25, 2023 at 09:15:59AM +0100, Julian Andres Klode wrote:
> Control: clone -1 -2
> Control: reassign -2 xfsprogs
> 
> On Sat, Dec 23, 2023 at 11:11:53PM +0100, Cyril Brulebois wrote:
> > Hi,
> > 
> > Anthony Iliopoulos  (2023-10-30):
> > > On Mon, Oct 30, 2023 at 04:19:32PM +0100, Philip Hands wrote:
> > > > Anthony Iliopoulos  writes:
> > > > 
> > > > > On Sun, Oct 29, 2023 at 09:02:01PM +0100, Philip Hands wrote:
> > > > ...
> > > > >>   error: invalid XFS directory entry.
> > > > ...
> > > > > This issue exists independently of the large extent counter, and it is
> > > > > related to grub commit ef7850c75 ("fs/xfs: Fix issues found while
> > > > > fuzzing the XFS filesystem"). That's actually the issue described in
> > > > > #1051543.
> > > > 
> > > > Ah, yes -- good point.
> > > > 
> > > > > There's a proposed fix at [1], and it works as expected with that 
> > > > > patch
> > > > > applied.
> > > > ...
> > > > > [1] 
> > > > > https://lore.kernel.org/grub-devel/20231018030347.36174-1-n...@vault24.org/
> > > > 
> > > > I can confirm that having applied both patches:
> > > > 
> > > >   https://salsa.debian.org/philh/grub2/-/pipelines/596346
> > > > 
> > > > it now succeeds at both installing grub, and then booting the system:
> > > > 
> > > >   https://openqa.debian.net/tests/200503#details
> > > 
> > > Thanks for confirming, perhaps then you can add your tested-by in the
> > > respective patches upstream.
> > > 
> > > BTW, another handy way to test if this works is via grub-mount.
> > 
> > Any chance we could have an updated grub2 package to fix this?
> 
> The final grub 2.12 that includes the fix should hit unstable in the
> middle of January. As you might be aware many are busy with family
> stuff and holiday celebrations right now.
> 
> As always though it stands to reason that this is a change that should
> (have been) reverted in xfsprogs first until a grub that understands it
> has been released in a stable point release such that you can use a
> stable grub to inspect an XFS filesystem created by a trixie xfsprogs.
> 
> It seems the bug has been wrongly reassigned instead of being cloned
> and reassigned, so I'm cloning it back to xfsprogs.

Ah I see I fixed this in Ubuntu's xfsprogs back in November, so patch
attached, I seem to have forgotten to forward this?

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en


xfsprogs_6.5.0-1_6.5.0-1ubuntu1.diff.gz
Description: application/gzip

Processed: Re: Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices

[Debian Bug Tracking System]

Processing control commands:

> tag 1059424 patch
Bug #1059424 [xfsprogs] xfsprogs-udeb: causes D-I to fail, reporting errors 
about missing partition devices
Added tag(s) patch.

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

Bug#1058299: marked as done (influxdb-python: FTBFS: AssertionError: 2 != 1 : .WarnBulkSizeNoEffect'> call should h

[Debian Bug Tracking System]

Your message dated Mon, 25 Dec 2023 08:23:31 +
with message-id 
and subject line Bug#1058299: fixed in influxdb-python 5.3.1-5
has caused the Debian Bug report #1058299,
regarding influxdb-python: FTBFS: AssertionError: 2 != 1 : .WarnBulkSizeNoEffect'>
 call should have generated one warning.
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb
> copying influxdb/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb
> copying influxdb/resultset.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb
> copying influxdb/_dataframe_client.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb
> copying influxdb/exceptions.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb
> copying influxdb/client.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb
> copying influxdb/dataframe_client.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb
> copying influxdb/chunked_json.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb
> copying influxdb/helper.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb
> copying influxdb/line_protocol.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb
> creating /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests
> copying influxdb/tests/helper_test.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests
> copying influxdb/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests
> copying influxdb/tests/dataframe_client_test.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests
> copying influxdb/tests/test_line_protocol.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests
> copying influxdb/tests/chunked_json_test.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests
> copying influxdb/tests/misc.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests
> copying influxdb/tests/client_test.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests
> copying influxdb/tests/resultset_test.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests
> creating 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/influxdb08
> copying influxdb/influxdb08/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/influxdb08
> copying influxdb/influxdb08/client.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/influxdb08
> copying influxdb/influxdb08/dataframe_client.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/influxdb08
> copying influxdb/influxdb08/chunked_json.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/influxdb08
> copying influxdb/influxdb08/helper.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/influxdb08
> creating 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests/server_tests
> copying influxdb/tests/server_tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests/server_tests
> copying influxdb/tests/server_tests/client_test_with_server.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests/server_tests
> copying influxdb/tests/server_tests/base.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests/server_tests
> copying influxdb/tests/server_tests/influxdb_instance.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests/server_tests
> creating 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests/influxdb08
> copying influxdb/tests/influxdb08/helper_test.py -> 
> /<>/.pybuild/cpython3_3.12_influxdb/build/influxdb/tests/influxdb08
> copying influxdb/tests/influxdb08/__init__.py -> 
> 

Processed: Re: Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1054644 [grub2] xfsprogs-udeb: causes D-I to fail, reporting errors about 
missing partition devices
Bug 1054644 cloned as bug 1059424
> reassign -2 xfsprogs
Bug #1059424 [grub2] xfsprogs-udeb: causes D-I to fail, reporting errors about 
missing partition devices
Bug reassigned from package 'grub2' to 'xfsprogs'.
Ignoring request to alter found versions of bug #1059424 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1059424 to the same values 
previously set

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

Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices

[Julian Andres Klode]

Control: clone -1 -2
Control: reassign -2 xfsprogs

On Sat, Dec 23, 2023 at 11:11:53PM +0100, Cyril Brulebois wrote:
> Hi,
> 
> Anthony Iliopoulos  (2023-10-30):
> > On Mon, Oct 30, 2023 at 04:19:32PM +0100, Philip Hands wrote:
> > > Anthony Iliopoulos  writes:
> > > 
> > > > On Sun, Oct 29, 2023 at 09:02:01PM +0100, Philip Hands wrote:
> > > ...
> > > >>   error: invalid XFS directory entry.
> > > ...
> > > > This issue exists independently of the large extent counter, and it is
> > > > related to grub commit ef7850c75 ("fs/xfs: Fix issues found while
> > > > fuzzing the XFS filesystem"). That's actually the issue described in
> > > > #1051543.
> > > 
> > > Ah, yes -- good point.
> > > 
> > > > There's a proposed fix at [1], and it works as expected with that patch
> > > > applied.
> > > ...
> > > > [1] 
> > > > https://lore.kernel.org/grub-devel/20231018030347.36174-1-n...@vault24.org/
> > > 
> > > I can confirm that having applied both patches:
> > > 
> > >   https://salsa.debian.org/philh/grub2/-/pipelines/596346
> > > 
> > > it now succeeds at both installing grub, and then booting the system:
> > > 
> > >   https://openqa.debian.net/tests/200503#details
> > 
> > Thanks for confirming, perhaps then you can add your tested-by in the
> > respective patches upstream.
> > 
> > BTW, another handy way to test if this works is via grub-mount.
> 
> Any chance we could have an updated grub2 package to fix this?

The final grub 2.12 that includes the fix should hit unstable in the
middle of January. As you might be aware many are busy with family
stuff and holiday celebrations right now.

As always though it stands to reason that this is a change that should
(have been) reverted in xfsprogs first until a grub that understands it
has been released in a stable point release such that you can use a
stable grub to inspect an XFS filesystem created by a trixie xfsprogs.

It seems the bug has been wrongly reassigned instead of being cloned
and reassigned, so I'm cloning it back to xfsprogs.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1059422: sdbus-cpp: pkgconfig fails to resolve systemd dependency

[Amin Bandali]

Source: sdbus-cpp
Version: 1.4.0-1
Severity: serious
Justification: causes dependent packages to fail to build from source
Tags: patch upstream

Dear maintainer,

The upstream sdbus-cpp 1.4.0 release shipped with a problematic
sdbus-c++.pc pkgconfig file that causes dependent packages that
use it to fail to build from source.  For example:

https://buildd.debian.org/status/fetch.php?pkg=ring=amd64=20230922.0%7Eds2-1%2Bb1=1701601320=0

The issue was reported[1] and fixed[2] upstream already, but
there hasn't been a new release as of yet.  Given the severity
of the issue, please consider doing an upload with the attached
patch for the time being, until upstream releases a new version
with the fix included.

I'd look to do an NMU with the patch in the next week or two if you
may be unavailable/busy, so as to unbreak dependent packages' build.

Thanks,
-a

[1] https://github.com/Kistler-Group/sdbus-cpp/issues/377
[2] https://github.com/Kistler-Group/sdbus-cpp/pull/378

diff --git a/CMakeLists.txt b/CMakeLists.txt
index 2803722..7d29973 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -12,7 +12,8 @@ include(GNUInstallDirs) # Installation directories for `install` command and pkg
 # PERFORMING CHECKS & PREPARING THE DEPENDENCIES
 #---
 
-set(LIBSYSTEMD "systemd")
+set(LIBSYSTEMD_IMPL "systemd")
+set(LIBSYSTEMD_LIB "libsystemd")
 
 option(BUILD_LIBSYSTEMD "Build libsystemd static library and incorporate it into libsdbus-c++" OFF)
 
@@ -23,13 +24,15 @@ if(NOT BUILD_LIBSYSTEMD)
 message(WARNING "libsystemd not found, checking for libelogind instead")
 pkg_check_modules(Systemd IMPORTED_TARGET GLOBAL libelogind>=236)
 if(TARGET PkgConfig::Systemd)
-set(LIBSYSTEMD "elogind")
+set(LIBSYSTEMD_IMPL "elogind")
+set(LIBSYSTEMD_LIB "libelogind")
 string(REPLACE "." ";" VERSION_LIST ${Systemd_VERSION})
 list(GET VERSION_LIST 0 Systemd_VERSION)
 	else()
 message(WARNING "libelogind not found, checking for basu instead")
 pkg_check_modules(Systemd IMPORTED_TARGET GLOBAL basu)
-set(LIBSYSTEMD "basu")
+set(LIBSYSTEMD_IMPL "basu")
+set(LIBSYSTEMD_LIB "basu")
 # https://git.sr.ht/~emersion/basu/commit/d4d185d29a26
 set(Systemd_VERSION "240")
 endif()
@@ -125,8 +128,8 @@ add_library(sdbus-c++-objlib OBJECT ${SDBUSCPP_SRCS})
 target_compile_definitions(sdbus-c++-objlib PRIVATE
 BUILD_LIB=1
 LIBSYSTEMD_VERSION=${LIBSYSTEMD_VERSION}
-SDBUS_${LIBSYSTEMD}
-SDBUS_HEADER=<${LIBSYSTEMD}/sd-bus.h>)
+SDBUS_${LIBSYSTEMD_IMPL}
+SDBUS_HEADER=<${LIBSYSTEMD_IMPL}/sd-bus.h>)
 target_include_directories(sdbus-c++-objlib PUBLIC $
$)
 if(BUILD_SHARED_LIBS)
@@ -236,6 +239,7 @@ if(BUILD_SHARED_LIBS AND (BUILD_LIBSYSTEMD OR Systemd_LINK_LIBRARIES MATCHES "/l
 else()
 set(PKGCONFIG_REQS "")
 endif()
+set(PKGCONFIG_DEPS ${LIBSYSTEMD_LIB})
 configure_file(pkgconfig/sdbus-c++.pc.in pkgconfig/sdbus-c++.pc @ONLY)
 install(FILES ${CMAKE_CURRENT_BINARY_DIR}/pkgconfig/sdbus-c++.pc
 DESTINATION ${CMAKE_INSTALL_LIBDIR}/pkgconfig COMPONENT dev)
diff --git a/pkgconfig/sdbus-c++.pc.in b/pkgconfig/sdbus-c++.pc.in
index 07034769..1e17f33d 100644
--- a/pkgconfig/sdbus-c++.pc.in
+++ b/pkgconfig/sdbus-c++.pc.in
@@ -5,7 +5,7 @@ includedir=@CMAKE_INSTALL_FULL_INCLUDEDIR@
 
 Name: @PROJECT_NAME@
 Description: C++ library on top of sd-bus, a systemd D-Bus library
-Requires@PKGCONFIG_REQS@: @LIBSYSTEMD@
+Requires@PKGCONFIG_REQS@: @PKGCONFIG_DEPS@
 Version: @SDBUSCPP_VERSION@
 Libs: -L${libdir} -l@PROJECT_NAME@
 Cflags: -I${includedir}
diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
index 56c48528..85abf97e 100644
--- a/tests/CMakeLists.txt
+++ b/tests/CMakeLists.txt
@@ -106,7 +106,7 @@ include_directories(${CMAKE_CURRENT_SOURCE_DIR})
 add_executable(sdbus-c++-unit-tests ${UNITTESTS_SRCS})
 target_compile_definitions(sdbus-c++-unit-tests PRIVATE
 LIBSYSTEMD_VERSION=${LIBSYSTEMD_VERSION}
-SDBUS_HEADER=<${LIBSYSTEMD}/sd-bus.h>)
+SDBUS_HEADER=<${LIBSYSTEMD_IMPL}/sd-bus.h>)
 target_link_libraries(sdbus-c++-unit-tests sdbus-c++-objlib GTest::gmock)
 
 add_executable(sdbus-c++-integration-tests ${INTEGRATIONTESTS_SRCS})