Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"

[Dirk Eddelbuettel]

On 9 July 2024 at 04:10, Adrian Bunk wrote:
| Control: tags -1 patch
| 
| On Mon, Jul 08, 2024 at 03:30:17PM -0500, Dirk Eddelbuettel wrote:
| > 
| > On 8 July 2024 at 22:09, Sebastian Ramacher wrote:
| > | Source: rmpi
| > | Version: 0.7-2-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=rmpi=armel=0.7-2-1%2Bb2=1720427935=0
| > | 
| > | checking if pkg-config knows about OpenMPI... no
| > | checking for stdio.h... yes
| > | checking for stdlib.h... yes
| > | checking for string.h... yes
| > | checking for inttypes.h... yes
| > | checking for stdint.h... yes
| > | checking for strings.h... yes
| > | checking for sys/stat.h... yes
| > | checking for sys/types.h... yes
| > | checking for unistd.h... yes
| > | checking for mpi.h... no
| > | configure: error: "Cannot find mpi.h header file"
| > | ERROR: configuration failed for package ‘Rmpi’
| > | * removing 
‘/<>/debian/r-cran-rmpi/usr/lib/R/site-library/Rmpi’
| > | dh_auto_install: error: R CMD INSTALL -l 
/<>/debian/r-cran-rmpi/usr/lib/R/site-library --clean 
--no-test-load . "--built-timestamp='Mon, 08 Jul 2024 08:38:43 +'" returned 
exit code 1
| > | make: *** [debian/rules:7: binary-arch] Error 25
| > 
| > :-/
| > 
| > R no linger supports i386 (and other 32 bt arches) upstream.
| 
| Neither does Open MPI, and the current transition to MPICH on 32bit is 
| the relevant change that broke it.

Nice catch, Adrian!
 
| The good news is that rmpi does support MPICH, it only uses a very 
| manual way when trying to find it - and that fails.
| 
| The attached patch adds a pkg-config search to configure.ac
| (similar to what was already added for Open MPI above).

Yes that is all old code from the mid/late 2000s and I may have helped
upstream.  Thanks for the patch, will fold it in once I get home.

Dirk

| 
| > Dirk
| 
| cu
| Adrian
| [DELETED ATTACHMENT mpich-pkg-config.patch, text/x-diff]

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1075760: hplip-gui breaks with python 3.12

[Tianyu Chen]

Control: severity -1 serious
Control: tag -1 patch

On Thu, 4 Jul 2024 10:13:27 -0300 Adilson dos Santos Dantas 
 wrote> Traceback (most recent call last):

 File "/usr/bin/hp-toolbox", line 38, in 
   from base.g import *
 File "/usr/share/hplip/base/g.py", line 239, in 
   sys_conf = SysConfig()
  ^^^
 File "/usr/share/hplip/base/g.py", line 184, in __init__
   ConfigBase.__init__(self, '/etc/hp/hplip.conf')
 File "/usr/share/hplip/base/g.py", line 89, in __init__
   self.read()
 File "/usr/share/hplip/base/g.py", line 130, in read
   self.conf.readfp(fp)
   
AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you
mean: '
read'?


readfp seems removed from python 3.12. I've prepared a patch for this.

Best regards,
Tianyu Chen @ deepindiff --git a/base/g.py b/base/g.py
index f73e23f..38d9a1d 100644
--- a/base/g.py
+++ b/base/g.py
@@ -128,7 +128,7 @@ class ConfigBase(object):
 try:
 fp = open(self.filename, "r")
 try:
-self.conf.readfp(fp)
+self.conf.read_file(fp)
 except configparser.MissingSectionHeaderError:
 print("")
 log.error("Found No Section in %s. Please set the http proxy for root and try again." % self.filename)
diff --git a/ui/devmgr4.py b/ui/devmgr4.py
index cc2552f..0d4bf5d 100644
--- a/ui/devmgr4.py
+++ b/ui/devmgr4.py
@@ -1227,7 +1227,7 @@ class DevMgr4(DevMgr4_base):
 
 hplip_conf = ConfigParser.ConfigParser()
 fp = open("/etc/hp/hplip.conf", "r")
-hplip_conf.readfp(fp)
+hplip_conf.read_file(fp)
 fp.close()
 
 try:
diff --git a/ui4/devmgr5.py b/ui4/devmgr5.py
index 652e297..4beac44 100644
--- a/ui4/devmgr5.py
+++ b/ui4/devmgr5.py
@@ -1024,7 +1024,7 @@ class DevMgr5(QMainWindow,  Ui_MainWindow):
 
 hplip_conf = configparser.ConfigParser()
 fp = open("/etc/hp/hplip.conf", "r")
-hplip_conf.readfp(fp)
+hplip_conf.read_file(fp)
 fp.close()
 
 try:
diff --git a/ui5/devmgr5.py b/ui5/devmgr5.py
index 7957446..50e9736 100644
--- a/ui5/devmgr5.py
+++ b/ui5/devmgr5.py
@@ -1074,7 +1074,7 @@ class DevMgr5(Ui_MainWindow_Derived, Ui_MainWindow, QMainWindow):
 
 hplip_conf = configparser.ConfigParser()
 fp = open("/etc/hp/hplip.conf", "r")
-hplip_conf.readfp(fp)
+hplip_conf.read_file(fp)
 fp.close()
 
 try:

Processed: Re: hplip-gui breaks with python 3.12

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1075760 [hplip-gui] hplip-gui breaks with python 3.12
Severity set to 'serious' from 'grave'
> tag -1 patch
Bug #1075760 [hplip-gui] hplip-gui breaks with python 3.12
Added tag(s) patch.

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

Processed: Re: hplip-gui breaks with python 3.12

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1075760 [hplip-gui] hplip-gui breaks with python 3.12
Severity set to 'grave' from 'normal'

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

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

[Debian Bug Tracking System]

Your message dated Tue, 9 Jul 2024 04:17:59 +
with message-id 

and subject line 
has caused the Debian Bug report #1054759,
regarding spaghetti: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p 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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:310: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_spaghetti 
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/spaghetti
> copying spaghetti/__init__.py -> build/lib/spaghetti
> copying spaghetti/analysis.py -> build/lib/spaghetti
> copying spaghetti/util.py -> build/lib/spaghetti
> copying spaghetti/network.py -> build/lib/spaghetti
> creating build/lib/spaghetti/tests
> copying spaghetti/tests/test_network.py -> build/lib/spaghetti/tests
> copying spaghetti/tests/__init__.py -> build/lib/spaghetti/tests
> running egg_info
> creating spaghetti.egg-info
> writing spaghetti.egg-info/PKG-INFO
> writing dependency_links to spaghetti.egg-info/dependency_links.txt
> writing requirements to spaghetti.egg-info/requires.txt
> writing top-level names to spaghetti.egg-info/top_level.txt
> writing manifest file 'spaghetti.egg-info/SOURCES.txt'
> reading manifest file 'spaghetti.egg-info/SOURCES.txt'
> adding license file 'LICENSE.txt'
> writing manifest file 'spaghetti.egg-info/SOURCES.txt'
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/spaghetti
> copying build/lib/spaghetti/__init__.py -> 
> build/bdist.linux-x86_64/wheel/spaghetti
> creating build/bdist.linux-x86_64/wheel/spaghetti/tests
> copying build/lib/spaghetti/tests/test_network.py -> 
> build/bdist.linux-x86_64/wheel/spaghetti/tests
> copying build/lib/spaghetti/tests/__init__.py -> 
> build/bdist.linux-x86_64/wheel/spaghetti/tests
> copying build/lib/spaghetti/analysis.py -> 
> build/bdist.linux-x86_64/wheel/spaghetti
> copying build/lib/spaghetti/util.py -> 
> build/bdist.linux-x86_64/wheel/spaghetti
> copying build/lib/spaghetti/network.py -> 
> build/bdist.linux-x86_64/wheel/spaghetti
> running install_egg_info
> Copying spaghetti.egg-info to 
> build/bdist.linux-x86_64/wheel/spaghetti-0.0.0.egg-info
> running install_scripts
> creating build/bdist.linux-x86_64/wheel/spaghetti-0.0.0.dist-info/WHEEL
> creating 
> '/<>/.pybuild/cpython3_3.11_spaghetti/.tmp-tc66ejt4/spaghetti-0.0.0-py3-none-any.whl'
>  and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'spaghetti/__init__.py'
> adding 'spaghetti/analysis.py'
> adding 'spaghetti/network.py'
> adding 'spaghetti/util.py'
> adding 'spaghetti/tests/__init__.py'
> adding 'spaghetti/tests/test_network.py'
> adding 'spaghetti-0.0.0.dist-info/LICENSE.txt'
> adding 'spaghetti-0.0.0.dist-info/METADATA'
> adding 'spaghetti-0.0.0.dist-info/WHEEL'
> adding 'spaghetti-0.0.0.dist-info/top_level.txt'
> adding 'spaghetti-0.0.0.dist-info/RECORD'
> removing build/bdist.linux-x86_64/wheel
> Successfully built spaghetti-0.0.0-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with 
> "installer" module
> PYTHONPATH=. https_proxy='https://127.0.0.1:9/' no_proxy=localhost python3 -m 
> sphinx -N -bhtml docs/ debian/html
> Running Sphinx v5.3.0
> /<>/spaghetti/network.py:40: FutureWarning: The next major 
> release of pysal/spaghetti (2.0.0) will drop support for all ``libpysal.cg`` 
> geometries. This change is a first step in refactoring ``spaghetti`` that is 
> expected to result in dramatically reduced runtimes for network instantiation 
> and operations. Users currently requiring network and point pattern input as 
> ``libpysal.cg`` geometries should prepare for this simply by converting to 
> ``shapely`` geometries.
>   warnings.warn(dep_msg, FutureWarning, stacklevel=1)
> making output directory... done
> checking 

Bug#1073309: [RFS] Re: Bug#1073309: cegui-mk2: FTBFS: XMLParser.cpp:102:40: error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlError*

[Bo YU]

Hi,
On Sun, Jun 16, 2024 at 02:51:33PM +0200, Lucas Nussbaum wrote:

Source: cegui-mk2
Version: 0.8.7+git20220615-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie
on amd64.


Relevant part (hopefully):

cd /<>/obj-x86_64-linux-gnu/cegui/src/RendererModules/OpenGL && /usr/bin/c++ -DCEGUIOPENGLRENDERER_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/cegui/include -I/<>/cegui/include 
-I/<>/cegui/include/RendererModules/OpenGL -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11  -fsigned-char -Wall -Wextra -Wundef 
-std=c++11 -fPIC -MD -MT cegui/src/RendererModules/OpenGL/CMakeFiles/CEGUIOpenGLRenderer-0.dir/GL3FBOTextureTarget.cpp.o -MF 
CMakeFiles/CEGUIOpenGLRenderer-0.dir/GL3FBOTextureTarget.cpp.o.d -o CMakeFiles/CEGUIOpenGLRenderer-0.dir/GL3FBOTextureTarget.cpp.o -c 
/<>/cegui/src/RendererModules/OpenGL/GL3FBOTextureTarget.cpp
/<>/cegui/src/XMLParserModules/Libxml2/XMLParser.cpp: In member function 
‘virtual void CEGUI::LibxmlParser::parseXML(CEGUI::XMLHandler&, const CEGUI::RawDataContainer&, 
const CEGUI::String&)’:
/<>/cegui/src/XMLParserModules/Libxml2/XMLParser.cpp:102:40: 
error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlError*’ 
{aka ‘_xmlError*’} [-fpermissive]
  102 | xmlError* err = xmlGetLastError();
  | ~~~^~
  ||
  |const xmlError* {aka const 
_xmlError*}


I have pushed some commits which one of was tried to fix the issue also.

piupart should be okay once the new binary was got to be upload.

reprotest should be not a regreesion from my view.

Please review it at your free time.

https://salsa.debian.org/games-team/cegui-mk2

BR,
Bo


signature.asc
Description: PGP signature

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1069511 src:openmpi
Bug #1069511 [src:mpgrafic] mpgrafic: FTBFS on armhf: tests fail
Bug reassigned from package 'src:mpgrafic' to 'src:openmpi'.
No longer marked as found in versions mpgrafic/0.3.19-1.
Ignoring request to alter fixed versions of bug #1069511 to the same values 
previously set
> forcemerge 1069433 1069511
Bug #1069433 {Done: Samuel Thibault } [src:openmpi] 
gtg-trace: FTBFS on armhf: tests fail
Bug #1069418 {Done: Samuel Thibault } [src:openmpi] 
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed: 
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069439 {Done: Samuel Thibault } [src:openmpi] 
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Removed indication that 1069512 affects src:python-escript, src:gtg-trace, 
src:arpack, and src:ruby-mpi
Added indication that 1069512 affects 
src:python-escript,src:ruby-mpi,src:arpack,src:gtg-trace
Removed indication that 1069418 affects src:ruby-mpi, src:arpack, 
src:gtg-trace, and src:python-escript
Added indication that 1069418 affects 
src:python-escript,src:ruby-mpi,src:arpack,src:gtg-trace
Removed indication that 1069433 affects src:python-escript, src:gtg-trace, 
src:ruby-mpi, and src:arpack
Added indication that 1069433 affects 
src:python-escript,src:ruby-mpi,src:arpack,src:gtg-trace
Removed indication that 1069439 affects src:python-escript, src:gtg-trace, 
src:ruby-mpi, and src:arpack
Added indication that 1069439 affects 
src:python-escript,src:ruby-mpi,src:arpack,src:gtg-trace
Bug #1069511 [src:openmpi] mpgrafic: FTBFS on armhf: tests fail
Marked Bug as done
Added indication that 1069511 affects 
src:python-escript,src:ruby-mpi,src:arpack,src:gtg-trace
Marked as fixed in versions openmpi/4.1.6-13.
Marked as found in versions openmpi/4.1.6-3 and openmpi/4.1.6-12.
Bug #1069418 {Done: Samuel Thibault } [src:openmpi] 
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed: 
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069439 {Done: Samuel Thibault } [src:openmpi] 
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Merged 1069418 1069433 1069439 1069511 1069512
> affects 1069433 src:mpgrafic
Bug #1069433 {Done: Samuel Thibault } [src:openmpi] 
gtg-trace: FTBFS on armhf: tests fail
Bug #1069418 {Done: Samuel Thibault } [src:openmpi] 
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed: 
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069439 {Done: Samuel Thibault } [src:openmpi] 
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Bug #1069511 {Done: Samuel Thibault } [src:openmpi] 
mpgrafic: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Added indication that 1069433 affects src:mpgrafic
Added indication that 1069418 affects src:mpgrafic
Added indication that 1069439 affects src:mpgrafic
Added indication that 1069511 affects src:mpgrafic
Added indication that 1069512 affects src:mpgrafic
> thanks
Stopping processing here.

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

Processed: retitle 1071331 to netcdf-parallel FTBFS with glibc 2.38

[Debian Bug Tracking System]

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

> retitle 1071331 netcdf-parallel FTBFS with glibc 2.38
Bug #1071331 [src:netcdf-parallel] netcdf-parallel: FTBFS: dpkg-gensymbols: 
error: some symbols or patterns disappeared in the symbols file
Changed Bug title to 'netcdf-parallel FTBFS with glibc 2.38' from 
'netcdf-parallel: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file'.
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1069439 src:openmpi
Bug #1069439 [src:arpack] arpack: FTBFS on armhf: make[6]: *** [Makefile:831: 
test-suite.log] Error 1
Bug reassigned from package 'src:arpack' to 'src:openmpi'.
No longer marked as found in versions arpack/3.9.1-1.1 and arpack/3.9.1-1.
Ignoring request to alter fixed versions of bug #1069439 to the same values 
previously set
> reassign 1069418 src:openmpi
Bug #1069418 [src:ruby-mpi] ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" 
failed: /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug reassigned from package 'src:ruby-mpi' to 'src:openmpi'.
No longer marked as found in versions ruby-mpi/0.3.2-4.
Ignoring request to alter fixed versions of bug #1069418 to the same values 
previously set
> forcemerge 1069433 1069439 1069418
Bug #1069433 {Done: Samuel Thibault } [src:openmpi] 
gtg-trace: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Bug #1069439 [src:openmpi] arpack: FTBFS on armhf: make[6]: *** [Makefile:831: 
test-suite.log] Error 1
Marked Bug as done
Added indication that 1069439 affects src:python-escript,src:gtg-trace
Marked as fixed in versions openmpi/4.1.6-13.
Marked as found in versions openmpi/4.1.6-3 and openmpi/4.1.6-12.
Bug #1069418 [src:openmpi] ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" 
failed: /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Marked Bug as done
Added indication that 1069418 affects src:python-escript,src:gtg-trace
Marked as fixed in versions openmpi/4.1.6-13.
Marked as found in versions openmpi/4.1.6-12 and openmpi/4.1.6-3.
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Merged 1069418 1069433 1069439 1069512
> affects 1069433 src:arpack src:ruby-mpi
Bug #1069433 {Done: Samuel Thibault } [src:openmpi] 
gtg-trace: FTBFS on armhf: tests fail
Bug #1069418 {Done: Samuel Thibault } [src:openmpi] 
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed: 
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069439 {Done: Samuel Thibault } [src:openmpi] 
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Added indication that 1069433 affects src:arpack and src:ruby-mpi
Added indication that 1069418 affects src:arpack and src:ruby-mpi
Added indication that 1069439 affects src:arpack and src:ruby-mpi
Added indication that 1069512 affects src:arpack and src:ruby-mpi
> thanks
Stopping processing here.

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

Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"

[Adrian Bunk]

Control: tags -1 patch

On Mon, Jul 08, 2024 at 03:30:17PM -0500, Dirk Eddelbuettel wrote:
> 
> On 8 July 2024 at 22:09, Sebastian Ramacher wrote:
> | Source: rmpi
> | Version: 0.7-2-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=rmpi=armel=0.7-2-1%2Bb2=1720427935=0
> | 
> | checking if pkg-config knows about OpenMPI... no
> | checking for stdio.h... yes
> | checking for stdlib.h... yes
> | checking for string.h... yes
> | checking for inttypes.h... yes
> | checking for stdint.h... yes
> | checking for strings.h... yes
> | checking for sys/stat.h... yes
> | checking for sys/types.h... yes
> | checking for unistd.h... yes
> | checking for mpi.h... no
> | configure: error: "Cannot find mpi.h header file"
> | ERROR: configuration failed for package ‘Rmpi’
> | * removing ‘/<>/debian/r-cran-rmpi/usr/lib/R/site-library/Rmpi’
> | dh_auto_install: error: R CMD INSTALL -l 
> /<>/debian/r-cran-rmpi/usr/lib/R/site-library --clean 
> --no-test-load . "--built-timestamp='Mon, 08 Jul 2024 08:38:43 +'" 
> returned exit code 1
> | make: *** [debian/rules:7: binary-arch] Error 25
> 
> :-/
> 
> R no linger supports i386 (and other 32 bt arches) upstream.

Neither does Open MPI, and the current transition to MPICH on 32bit is 
the relevant change that broke it.

The good news is that rmpi does support MPICH, it only uses a very 
manual way when trying to find it - and that fails.

The attached patch adds a pkg-config search to configure.ac
(similar to what was already added for Open MPI above).

> Dirk

cu
Adrian
Description: Try to find mpich with pkg-config if pkg-config did not find openmpi
Author: Adrian Bunk 

--- rmpi-0.7-2.orig/configure.ac
+++ rmpi-0.7-2/configure.ac
@@ -96,6 +96,11 @@ if test -z "$MPI_ROOT" ; then
 fi
 
 if test -z "$MPI_ROOT" ; then
+	#Use pkg-config to find mpich
+	PKG_CHECK_MODULES([MPICH],[mpich],[MPITYPE="MPICH" MPI_ROOT="NONEED"],[:])
+fi
+
+if test -z "$MPI_ROOT" ; then
   for d in /opt/lib /usr/lib /usr /usr/lib/x86_64-linux-gnu/openmpi \
   /usr/local/lib /usr/local /usr/lib64/mpi/gcc/openmpi; do
 if test -f $d/include/mpi.h && test -d $d/lib/openmpi; then
@@ -303,7 +308,12 @@ case "$MPITYPE" in
 PKG_LIBS="-L${MPI_LIBPATH} -lmpi -llam ${MPI_LIBS}"
 ;;
   MPICH)
-PKG_LIBS="-L${MPI_LIBPATH} -lmpich -lmpl -lopa ${MPI_LIBS}"
+if test "$MPI_ROOT" = "NONEED"; then
+		PKG_CPPFLAGS="${MPICH_CFLAGS}"
+		PKG_LIBS="${MPICH_LIBS}"
+else
+		PKG_LIBS="-L${MPI_LIBPATH} -lmpich -lmpl -lopa ${MPI_LIBS}"
+fi
 ;;
   MPICH2)
 PKG_LIBS="-L${MPI_LIBPATH} -lmpich -lmpl -lopa ${MPI_LIBS}"

Processed: Re: Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1075978 [src:rmpi] rmpi: FTBFS on 32 bit architectures: configure: error: 
"Cannot find mpi.h header file"
Added tag(s) patch.

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

Bug#1075985: libfftw3-mpi3 might be misbuilt with MPICH as default

[Adrian Bunk]

Package: libfftw3-mpi3
Version: 3.3.10-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Alastair McKinstry 

https://buildd.debian.org/status/fetch.php?pkg=fftw3=i386=3.3.10-1%2Bb3=1720426229=0

...
./configure --enable-single  --build i686-linux-gnu F77="gfortran -ff2c" 
--prefix=/usr --enable-shared --enable-threads --enable-openmp --enable-mpi 
--libdir=\${prefix}/lib/i386-linux-gnu MPILIBS="" --enable-sse --enable-avx
...
   dh_shlibdeps -a
dpkg-shlibdeps: warning: symbol MPI_Comm_split used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_dup used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Bcast used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_size used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Alltoall used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_free used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Allreduce used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Abort used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_rank used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Alltoallv used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3l_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: 4 other similar warnings have been skipped (use -v to 
see them all)
dpkg-shlibdeps: warning: symbol MPI_Sendrecv used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Alltoallv used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_rank used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Abort used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_f2c used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Send used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Recv used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Bcast used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_size used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_dup used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3f_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: 4 other similar warnings have been skipped (use -v to 
see them all)
dpkg-shlibdeps: warning: symbol MPI_Alltoallv used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Abort used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_rank used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_f2c used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Send used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Sendrecv used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Recv used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_split used by 
debian/libfftw3-mpi3/usr/lib/i386-linux-gnu/libfftw3_mpi.so.3.6.10 found in 
none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_dup used by 

Processed: severity of 1074370 is important

[Debian Bug Tracking System]

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

> # temporarily disabled asm support on armel and armhf
> severity 1074370 important
Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1075920: marked as done (pycallgraph: pycallgraph fails to run)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 22:00:14 +
with message-id 
and subject line Bug#1075920: fixed in pycallgraph 1.1.3-3
has caused the Debian Bug report #1075920,
regarding pycallgraph: pycallgraph fails to run
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.)


-- 
1075920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycallgraph
Version: 1.1.3-2
Severity: important

Dear Maintainer,

pycallgraph fails to run.

$ pycallgraph 
Traceback (most recent call last):
  File "/usr/bin/pycallgraph", line 11, in 
import pycallgraph as __pycallgraph
  File "/usr/lib/python3/dist-packages/pycallgraph/__init__.py", line 11, in 

from .pycallgraph import PyCallGraph
  File "/usr/lib/python3/dist-packages/pycallgraph/pycallgraph.py", line 3, in 

from .output import Output
  File "/usr/lib/python3/dist-packages/pycallgraph/output/__init__.py", line 3, 
in 
from .output import Output
  File "/usr/lib/python3/dist-packages/pycallgraph/output/output.py", line 3, 
in 
from distutils.spawn import find_executable
ModuleNotFoundError: No module named 'distutils.spawn'


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

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

-- 
Regards
Sudip
--- End Message ---
--- Begin Message ---
Source: pycallgraph
Source-Version: 1.1.3-3
Done: Sudip Mukherjee 

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated pycallgraph 
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, 08 Jul 2024 22:07:42 +0100
Source: pycallgraph
Architecture: source
Version: 1.1.3-3
Distribution: unstable
Urgency: medium
Maintainer: Carl Chenet 
Changed-By: Sudip Mukherjee 
Closes: 1075920
Changes:
 pycallgraph (1.1.3-3) unstable; urgency=medium
 .
   * Team upload.
   * Remove distutils usage. (Closes: #1075920)
   * Update Standards-Version to 4.6.2.
   * Update debhelper-compat to 13.
Checksums-Sha1:
 80b5fbac7a945bba6199eb89244d6a10557476d1 2029 pycallgraph_1.1.3-3.dsc
 68176529bc4be562cc3325550b149a68df28f9de 4484 pycallgraph_1.1.3-3.debian.tar.xz
 049a3ef5283805fdcd6012943be39260f5a50978 8422 
pycallgraph_1.1.3-3_amd64.buildinfo
Checksums-Sha256:
 dc29c92dd91a836c0af26cc6435d90f421dc25381411e07a51d5faa2ae15310b 2029 
pycallgraph_1.1.3-3.dsc
 e71df09cc89d3ccca59311ebe50e4e23c83951f11c04e6c0842cb1af02b48e88 4484 
pycallgraph_1.1.3-3.debian.tar.xz
 5ce9447423b4c04f9304da72b345050c9a63804acccbfff53576a0c77cfa05ee 8422 
pycallgraph_1.1.3-3_amd64.buildinfo
Files:
 8af51b12308d11d73a493bf1720c9545 2029 python optional pycallgraph_1.1.3-3.dsc
 4d30c2da7b6599cb1d4ee1b848255c82 4484 python optional 
pycallgraph_1.1.3-3.debian.tar.xz
 eb25038e34d75faadac5700a28b1a7e1 8422 python optional 
pycallgraph_1.1.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAmaMV28ACgkQR5mjUUbR
KzWcXw/8DcxJtRNHfLgfN/AzpTF8qr7ADp0hLo291uQVe7pjTFaa66Tl0Etr/tsg
DU9dn/3IJPxyAUmU7Qu4tuBLvocQuo6TIUpY2oybylFjilZ/dLr8G2wDz3SSjVjH
GZLaPFjFJARZ5rk27LyudXLIMos48pdLAqv2l/fSWK/dk71LK+avpIQgCiARaxE1
LByL02V5gu4xSGBSZMnVW3EQrh2EdaADipIhYyqk5aKNx9V9eq4UKahbHI4XH9UY
lhyb59hTZ+N86clcQS9hTM22XLWU8Oyilu/fjhK2Cwxj28ZEwRty/8Vpi+w2O4NJ
ce6RG/sPFTfizWcAcDhXaOnd2tjobYp54ZoSJLeQIco0sphfljSDN5tizQPn/QQg
Nsud9WDQjMjOROEcxLUtHIs1fm4k33VGnHX13Vb7pE4yTgBA08l/nSFs9u8iNKTD
QDJ4pFUW1N470BsaFqRvMXzljTe9N5OlT5LiDZ1/aSQJ9jDHpuniW9WiCR6KM1f4
GPI4k/it2GsaCtvZMVspvRsTBzkEDEiDRVvacO8Uv0y7ZKMEZbNVXPXyH3DTVuTv
YmJBYgasV0rCUPxFrB/P5DHAieVT5oeE5m+wA+i+JUQOHBusV6Q3jREU4sGz45Lz
em0IpMNdmZAcbgUVXHSoH0TFAyxn1cuShD/fLYqGPh9CgeoxMv8=
=etAT
-END PGP SIGNATURE-



pgpBxLbafIg8f.pgp
Description: 

Processed: reassign 1075900 to exim4, tagging 1075979, tagging 1040102, found 1040102 in 0.9.6-2 ...

[Debian Bug Tracking System]

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

> reassign 1075900 exim4 4.96-15+deb12u4
Bug #1075900 [exim4/stable,stable-security] Exim4 in Debian can't deliver to 
DANE secured Mailservers
Warning: Unknown package 'exim4/stable'
Warning: Unknown package 'stable-security'
Bug reassigned from package 'exim4/stable,stable-security' to 'exim4'.
Ignoring request to alter found versions of bug #1075900 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1075900 to the same values 
previously set
Bug #1075900 [exim4] Exim4 in Debian can't deliver to DANE secured Mailservers
Marked as found in versions exim4/4.96-15+deb12u4.
> tags 1075979 + sid trixie
Bug #1075979 [src:molds] molds: FTBFS with mpich as default MPI provider: 
/usr/bin/ld: cannot find -lmpi_cxx: No such file or directory
Added tag(s) sid and trixie.
> tags 1040102 + sid trixie
Bug #1040102 {Done: Bastian Germann } [src:pyinotify] 
pyinotify: deprecation of Python libraries asyncore and asynchat
Added tag(s) trixie and sid.
> found 1040102 0.9.6-2
Bug #1040102 {Done: Bastian Germann } [src:pyinotify] 
pyinotify: deprecation of Python libraries asyncore and asynchat
Marked as found in versions pyinotify/0.9.6-2.
> notfound 1075961 5.6.3-2
Bug #1075961 [src:kamailio] FTBFS: hep.c:985:41: error: implicit declaration of 
function ‘inet_ntop’
No longer marked as found in versions kamailio/5.6.3-2.
> found 1075961 5.8.2-2
Bug #1075961 [src:kamailio] FTBFS: hep.c:985:41: error: implicit declaration of 
function ‘inet_ntop’
Marked as found in versions kamailio/5.8.2-2.
> tags 1075811 + sid trixie
Bug #1075811 {Done: Bastian Germann } [python3-pyinotify] 
autokey-qt can be installed but will nor run
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Bug#1075857: marked as done (Crashes with squeekboard when launching apps or showing system modal dialogs)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 21:32:23 +
with message-id 
and subject line Bug#1075857: fixed in phoc 0.40.0+ds-2
has caused the Debian Bug report #1075857,
regarding Crashes with squeekboard when launching apps or showing system modal 
dialogs
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.)


-- 
1075857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phoc
Version: 0.40.0+ds-1
Severity: normal

Dear Maintainer,

   after upgrade to 0.40.0+ds-1 phoc started to crash frequently in
   different cases on original PinePhone. If phoc is downgraded to
   0.39.0+ds-2, then phoc doesn't crash anymore

   phoc crashes constantly when I search for 'keypassx' in phosh and
   try to launch it. Another case it crashed a lot, when I unlocked
   ssh key in phosh, when I've tried to connect to remote machine in
   terminal.

   Here is coredump information for one of the crashes.
  
```
   $ coredumpctl info phoc
   PID: 1534 (phoc)
   UID: 1000 (mobian)
   GID: 1000 (mobian)
Signal: 6 (ABRT)
 Timestamp: Sat 2024-07-06 16:25:14 MSK (3h 1min ago)
  Command Line: /usr/bin/phoc -S -C /etc/phosh/phoc.ini -E $'bash -lc \'exec 
gnome-session --disable-acceleration-check --session=phosh\''
Executable: /usr/bin/phoc
 Control Group: /user.slice/user-1000.slice/session-3.scope
  Unit: session-3.scope
 Slice: user-1000.slice
   Session: 3
 Owner UID: 1000 (mobian)
   Boot ID: 93ec88a428004ed680d5d597d116aea9
Machine ID: 72d23d3703de45bbb0c5e12a67e9a407
  Hostname: mobian-dev
   Storage: 
/var/lib/systemd/coredump/core.phoc.1000.93ec88a428004ed680d5d597d116aea9.1534.172027231400.zst
 (present)
  Size on Disk: 6.3M
   Message: Process 1534 (phoc) of user 1000 dumped core.

Module libzstd.so.1 from deb libzstd-1.5.6+dfsg-1.arm64
Module libblkid.so.1 from deb util-linux-2.40.1-9.arm64
Module libsystemd.so.0 from deb systemd-256.1-2.arm64
Module libmount.so.1 from deb util-linux-2.40.1-9.arm64
Module libudev.so.1 from deb systemd-256.1-2.arm64
Stack trace of thread 1534:
#0  0xb53de6a8 __pthread_kill_implementation (libc.so.6 
+ 0x7e6a8)
#1  0xb5394d6c __GI_raise (libc.so.6 + 0x34d6c)
#2  0xb5380980 __GI_abort (libc.so.6 + 0x20980)
#3  0xb5b9eae0 g_assertion_message (libglib-2.0.so.0 + 
0x8eae0)
#4  0xb5b9eb44 g_assertion_message_expr 
(libglib-2.0.so.0 + 0x8eb44)
#5  0xade19cd4 n/a (phoc + 0x49cd4)
#6  0xaddf9e14 n/a (phoc + 0x29e14)
#7  0xaddfadf8 n/a (phoc + 0x2adf8)
#8  0xaddf6bcc n/a (phoc + 0x26bcc)
#9  0xb5719564 wl_signal_emit_mutable 
(libwayland-server.so.0 + 0x9564)
#10 0xb5629350 n/a (libwlroots.so.12 + 0x59350)
#11 0xb408f040 drmHandleEvent (libdrm.so.2 + 0xf040)
#12 0xb562aa6c n/a (libwlroots.so.12 + 0x5aa6c)
#13 0xb571b918 wl_event_loop_dispatch 
(libwayland-server.so.0 + 0xb918)
#14 0xadde5adc n/a (phoc + 0x15adc)
#15 0xb5b6e500 n/a (libglib-2.0.so.0 + 0x5e500)
#16 0xb5b708bc n/a (libglib-2.0.so.0 + 0x608bc)
#17 0xb5b71354 g_main_loop_run (libglib-2.0.so.0 + 
0x61354)
#18 0xadde5338 n/a (phoc + 0x15338)
#19 0xb5381044 __libc_start_call_main (libc.so.6 + 
0x21044)
#20 0xb5381118 __libc_start_main_impl (libc.so.6 + 
0x21118)
#21 0xadde5470 n/a (phoc + 0x15470)

Stack trace of thread 1573:
#0  0xb543d61c __GI___poll (libc.so.6 + 0xdd61c)
#1  0xb5b707f0 n/a (libglib-2.0.so.0 + 0x607f0)
#2  0xb5b71068 g_main_context_iteration 
(libglib-2.0.so.0 + 0x61068)
#3  0xb5b710c4 n/a (libglib-2.0.so.0 + 0x610c4)
#4  0xb5ba0768 n/a (libglib-2.0.so.0 + 0x90768)
#5  0xb53dca9c start_thread (libc.so.6 + 0x7ca9c)
#6  0xb544808c thread_start (libc.so.6 + 0xe808c)

Stack trace of thread 1575:

Bug#1075857: marked as pending in phoc

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1075857 in phoc 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/DebianOnMobile-team/phoc/-/commit/4eb37a810e82a751bbcd1458d381016e862173c2


layer-shell: Mark layer cache dirty when OSK changes layers

Closes: #1075857
Thanks: Andrey Skvortsov for the report and testing the fix


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1075857

Processed: Bug#1075857 marked as pending in phoc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1075857 [phoc] Crashes with squeekboard when launching apps or showing 
system modal dialogs
Ignoring request to alter tags of bug #1075857 to the same tags previously set

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

Bug#1075857: marked as pending in phoc

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1075857 in phoc 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/DebianOnMobile-team/phoc/-/commit/4eb37a810e82a751bbcd1458d381016e862173c2


layer-shell: Mark layer cache dirty when OSK changes layers

Closes: #1075857
Thanks: Andrey Skvortsov for the report and testing the fix


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1075857

Processed: Bug#1075857 marked as pending in phoc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1075857 [phoc] Crashes with squeekboard when launching apps or showing 
system modal dialogs
Added tag(s) pending.

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

Bug#1075980: mpi4py: FTBFS with mpich as default MPI provider on 32 bit systems: testPackUnpackExternal (test_pack.TestPackExternal.testPackUnpackExternal) ... Conversion of types whose size is not th

[Sebastian Ramacher]

Source: mpi4py
Version: 3.1.6-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=mpi4py=armel=3.1.6-1%2Bb1=1720427513=0

testMessageNoProc (test_p2p_obj_matched.TestMessage.testMessageNoProc) ... ok
testMessageNull (test_p2p_obj_matched.TestMessage.testMessageNull) ... ok
testIMProbe (test_p2p_obj_matched.TestP2PMatchedSelf.testIMProbe) ... ok
testProbeRecv (test_p2p_obj_matched.TestP2PMatchedSelf.testProbeRecv) ... ok
testIMProbe (test_p2p_obj_matched.TestP2PMatchedSelfDup.testIMProbe) ... ok
testProbeRecv (test_p2p_obj_matched.TestP2PMatchedSelfDup.testProbeRecv) ... ok
testIMProbe (test_p2p_obj_matched.TestP2PMatchedWorld.testIMProbe) ... ok
testProbeRecv (test_p2p_obj_matched.TestP2PMatchedWorld.testProbeRecv) ... ok
testIMProbe (test_p2p_obj_matched.TestP2PMatchedWorldDup.testIMProbe) ... ok
testProbeRecv (test_p2p_obj_matched.TestP2PMatchedWorldDup.testProbeRecv) ... ok
testPackSize (test_pack.TestPackExternal.testPackSize) ... ok
testPackUnpackExternal (test_pack.TestPackExternal.testPackUnpackExternal) ... 
Conversion of types whose size is not the same as the size in external32 is not 
supported
Aborting with internal error
[unset]: PMIU_write error; fd=-1 buf=:cmd=abort exitcode=1 message=Aborting 
with internal error
:
system msg for write_line failure : Bad file descriptor
make[1]: *** [debian/rules:91: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:52: binary-arch] Error 2

Cheers
-- 
Sebastian Ramacher

Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"

[Dirk Eddelbuettel]

On 8 July 2024 at 22:09, Sebastian Ramacher wrote:
| Source: rmpi
| Version: 0.7-2-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=rmpi=armel=0.7-2-1%2Bb2=1720427935=0
| 
| checking if pkg-config knows about OpenMPI... no
| checking for stdio.h... yes
| checking for stdlib.h... yes
| checking for string.h... yes
| checking for inttypes.h... yes
| checking for stdint.h... yes
| checking for strings.h... yes
| checking for sys/stat.h... yes
| checking for sys/types.h... yes
| checking for unistd.h... yes
| checking for mpi.h... no
| configure: error: "Cannot find mpi.h header file"
| ERROR: configuration failed for package ‘Rmpi’
| * removing ‘/<>/debian/r-cran-rmpi/usr/lib/R/site-library/Rmpi’
| dh_auto_install: error: R CMD INSTALL -l 
/<>/debian/r-cran-rmpi/usr/lib/R/site-library --clean 
--no-test-load . "--built-timestamp='Mon, 08 Jul 2024 08:38:43 +'" returned 
exit code 1
| make: *** [debian/rules:7: binary-arch] Error 25

:-/

R no linger supports i386 (and other 32 bt arches) upstream.

Dirk
 
| Cheers
| -- 
| Sebastian Ramacher

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1075979: molds: FTBFS with mpich as default MPI provider: /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory

[Sebastian Ramacher]

Source: molds
Version: 0.3.1-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=molds=armhf=0.3.1-1%2Bb12=1720428636=0

mpicxx -I/usr/include/mpi -I/usr/lib/openblas-base//include/ -o obj/Main.o 
Main.cpp -g -Wall -fopenmp -O2 -fopenmp -c
mpicxx -o molds -Wl,-rpath=/usr//lib/ -Wl,-rpath=/usr/lib/openblas-base 
obj/Enums.o  obj/PrintController.oobj/MolDSException.o  
  obj/MallocerFreer.o
obj/MpiProcess.o   obj/AsyncCommunicator.oobj/Blas.o
obj/Lapack.oobj/Utilities.oobj/MathUtilities.oobj/EularAngle.o
obj/Parameters.oobj/Atom.oobj/Hatom.o  obj/Liatom.o 
 obj/Catom.o  obj/Natom.o  obj/Oatom.o  
obj/Satom.o obj/EnvironmentalPointCharge.o  
obj/AtomFactory.oobj/Molecule.oobj/InputParser.o
obj/GTOExpansionSTO.oobj/RealSphericalHarmonicsIndex.o
obj/MOLogger.oobj/DensityLogger.o
obj/HoleDensityLogger.oobj/ParticleDensityLogger.o  
 obj/Cndo2.o   obj/Indo.o 
obj/ZindoS.oobj/Mndo.o   obj/Am1.o   obj/Am1D.o   obj/Pm3.o   obj/Pm3D.o   
obj/Pm3Pddg.o  obj/ElectronicStructureFactory.o  obj/MD.o  obj/MC.o 
   obj/RPMD.o obj/NASCO.oobj/Optimizer.o
obj/ConjugateGradient.oobj/SteepestDescent.oobj/BFGS.o  
  obj/GEDIIS.o  obj/OptimizerFactory.o obj/MolDS.o   
obj/Main.o -L/usr//lib/ -L/usr/lib/openblas-base -lstdc++ -lm -lpthread -lgomp 
-L/usr/lib/lapack/ -llapacke -lmpi -lmpi_cxx -lboost_serialization -lboost_mpi 
-lboost_thread -lboost_system -lopenblas
/usr/bin/ld: cannot find -lmpi_cxx: No such file or directory
collect2: error: ld returned 1 exit status

Cheers
-- 
Sebastian Ramacher

Bug#1075851: mayavi2: FTBFS on ppc64el and riscv64

[Aurelien Jarno]

On 2024-07-06 12:09, Graham Inggs wrote:
> Source: mayavi2
> Version: 4.8.1-5
> Severity: serious
> Tags: ftbfs
> X-Debbugs-Cc: debian-ri...@lists.debian.org, debian-powe...@lists.debian.org
> 
> Hi Maintainer
> 
> mayavi2 FTBFS on ppc64el [1] and riscv64 [2], where it built
> previously.   I've copied what I hope
> is the relevant part of the log below.

From a quick look, the problems appears when testing for the support of
-march=native. ppc64el and riscv64 have in common that they don't
support this GCC option.

Normally this fails the following way:

| $ gcc -march=native
| gcc: error: '-march=native': ISA string must begin with rv32 or rv64
| gcc: fatal error: no input files
| compilation terminated.

However something sets LC_CTYPE to C.UTF-8, and pybuild also sets LC_ALL
to C.UTF-8. This causes GCC to output a slightly different error message:

| $ LC_CTYPE=C.UTF-8 gcc -march=native
| gcc: error: ‘-march=native’: ISA string must begin with rv32 or rv64
| gcc: fatal error: no input files
| compilation terminated.

Note how the quotes are different and use non-ASCII characters. This is
what chokes numpy distutils code. Now I am not sure why the problem
suddenly happens. It might be related or not to a Python 3.12 change.

Regards
Aurelien

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

Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"

[Sebastian Ramacher]

Source: rmpi
Version: 0.7-2-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=rmpi=armel=0.7-2-1%2Bb2=1720427935=0

checking if pkg-config knows about OpenMPI... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for mpi.h... no
configure: error: "Cannot find mpi.h header file"
ERROR: configuration failed for package ‘Rmpi’
* removing ‘/<>/debian/r-cran-rmpi/usr/lib/R/site-library/Rmpi’
dh_auto_install: error: R CMD INSTALL -l 
/<>/debian/r-cran-rmpi/usr/lib/R/site-library --clean 
--no-test-load . "--built-timestamp='Mon, 08 Jul 2024 08:38:43 +'" returned 
exit code 1
make: *** [debian/rules:7: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher

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

[Salvatore Bonaccorso]

Hi Paul,

On Thu, May 30, 2024 at 12:58:45PM +0100, Ben Hutchings wrote:
> On Thu, 2024-05-16 at 08:09 +0200, Paul Gevers wrote:
> > Hi Ben (and all the rest),
> > 
> > On 15-05-2024 9:56 p.m., Ben Hutchings wrote:
> > > Apologies for leaving this bug for so long.
> > 
> > NP, part of live I guess.
> > 
> > > Is this bug still occurring?
> > 
> > I don't know. The problem was severe enough for us to abandon the idea 
> > of running the backport kernels on our arm64 hosts, so we went back to 
> > the stable kernel there.
> > 
> > > I had a look for possibly related fixes,
> > > and found:
> > > 
> > > commit 22e111ed6c83dcde3037fc81176012721bc34c0b
> > 
> > [...]
> > 
> > > The fix went into
> > > 6.8-rc1 and was backported to 6.6.15, so Debian versions 6.6.15-1
> > > onward should have it.
> > 
> > > commit a8b0026847b8c43445c921ad2c85521c92eb175f
> > 
> > [...]
> > 
> > > which went into 6.8 but was *not* backported.
> > 
> > If you think it worth enough knowing if either is the case, I can 
> > install the backports kernel again on the arm64 hosts, but obviously 
> > that will be annoying for us. Please let me know if I should pursue this 
> > (I would be expecting a bit quicker turn around on this bug if you say 
> > yes now ;) ).
> 
> If you can test with the unstable kernel that would be great.  If you
> are limited to only stable and backports, then you should probably wait
> until 6.8 is in backports rather than testing the current 6.7 backport
> that has only one of the fixes.

In the last weekly kernel team meeting we discussed about some of the
open issues, and we wondered if you were able to test again with
either a unstable kernel, or if that's not possible with the current
versions available trough backports?

Unfortunately for the 6.8.y series though the package is not yet out
of backports-new. 

Regards,
Salvatore

Processed: [bts-link] source package src:nova

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:nova
> # 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 #1074762 (http://bugs.debian.org/1074762)
> # Bug title: CVE-2024-32498: Arbitrary file access through custom QCOW2 
> external data
> #  * https://bugs.launchpad.net/bugs/2059809
> #  * remote status changed: (?) -> Fix-Released
> #  * closed upstream
> tags 1074762 + fixed-upstream
Bug #1074762 [src:nova] CVE-2024-32498: Arbitrary file access through custom 
QCOW2 external data
Added tag(s) fixed-upstream.
> usertags 1074762 + status-Fix-Released
There were no usertags set.
Usertags are now: status-Fix-Released.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:cinder

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:cinder
> # 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 #1074763 (http://bugs.debian.org/1074763)
> # Bug title: CVE-2024-32498: Arbitrary file access through custom QCOW2 
> external data
> #  * https://bugs.launchpad.net/bugs/2059809
> #  * remote status changed: (?) -> Fix-Released
> #  * closed upstream
> tags 1074763 + fixed-upstream
Bug #1074763 [src:cinder] CVE-2024-32498: Arbitrary file access through custom 
QCOW2 external data
Added tag(s) fixed-upstream.
> usertags 1074763 + status-Fix-Released
There were no usertags set.
Usertags are now: status-Fix-Released.
> thanks
Stopping processing here.

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

Processed: (No Subject)

[Debian Bug Tracking System]

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

> forwarded 1071954 https://github.com/irontec/sngrep/issues/492
Bug #1071954 [src:sngrep] sngrep: FTBFS against libgcrypt 1.11
Set Bug forwarded-to-address to 'https://github.com/irontec/sngrep/issues/492'.
> --
Stopping processing here.

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

Processed: src:gcc-13-cross-mipsen: fails to migrate to testing for too long: stuck behind gcc-14-cross-mipsen

[Debian Bug Tracking System]

Processing control commands:

> close -1 3+c1
Bug #1075974 [src:gcc-13-cross-mipsen] src:gcc-13-cross-mipsen: fails to 
migrate to testing for too long: stuck behind gcc-14-cross-mipsen
Marked as fixed in versions gcc-13-cross-mipsen/3+c1.
Bug #1075974 [src:gcc-13-cross-mipsen] src:gcc-13-cross-mipsen: fails to 
migrate to testing for too long: stuck behind gcc-14-cross-mipsen
Marked Bug as done

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

Bug#1075974: src:gcc-13-cross-mipsen: fails to migrate to testing for too long: stuck behind gcc-14-cross-mipsen

[Paul Gevers]

Source: gcc-13-cross-mipsen
Version: 2+c1
Severity: serious
Control: close -1 3+c1
Tags: sid trixie
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:gcc-13-cross-mipsen has been trying to 
migrate for 32 days [2]. Hence, I am filing this bug. The version in 
unstable has a relation with gcc-14-cross-mipsen but that new package 
isn't ready to migrate yet.


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=gcc-13-cross-mipsen



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1071332: marked as done (ola: FTBFS: plugins/osc/OSCNode.cpp:153:28: error: cannot convert ‘lo_arg*’ to ‘lo_blob’)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 19:09:31 +
with message-id 
and subject line Bug#1071332: fixed in ola 0.10.9.nojsmin-5
has caused the Debian Bug report #1071332,
regarding ola: FTBFS: plugins/osc/OSCNode.cpp:153:28: error: cannot convert 
‘lo_arg*’ to ‘lo_blob’
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.)


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

Package: src:ola
Version: 0.10.9.nojsmin-4.1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
dh build --parallel --with bash_completion,python3
   dh_update_autotools_config
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
   dh_autoreconf
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'config'.
libtoolize: copying file 'config/libtool.m4'
libtoolize: copying file 'config/ltoptions.m4'
libtoolize: copying file 'config/ltsugar.m4'
libtoolize: copying file 'config/ltversion.m4'
libtoolize: copying file 'config/lt~obsolete.m4'

[... snipped ...]

/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |^~~~
In file included from ./olad/OlaServer.h:36:
./include/ola/rdm/PidStore.h:172:8: warning: ‘template class 
std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead 
[-Wdeprecated-declarations]
  172 |   std::auto_ptr m_esta_store;
  |^~~~
/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |^~~~
./olad/OlaServer.h:181:8: warning: ‘template class std::auto_ptr’ is 
deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations]
  181 |   std::auto_ptr m_our_export_map;
  |^~~~
/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |^~~~
./olad/OlaServer.h:185:8: warning: ‘template class std::auto_ptr’ is 
deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations]
  185 |   std::auto_ptr m_device_manager;
  |^~~~
/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |^~~~
./olad/OlaServer.h:186:8: warning: ‘template class std::auto_ptr’ is 
deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations]
  186 |   std::auto_ptr m_plugin_manager;
  |^~~~
/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |^~~~
./olad/OlaServer.h:187:8: warning: ‘template class std::auto_ptr’ is 
deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations]
  187 |   std::auto_ptr m_plugin_adaptor;
  |^~~~
/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |^~~~
./olad/OlaServer.h:188:8: warning: ‘template class std::auto_ptr’ is 
deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations]
  188 |   std::auto_ptr m_universe_store;
  |^~~~
/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |^~~~
./olad/OlaServer.h:189:8: warning: ‘template class std::auto_ptr’ is 
deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations]
  189 |   std::auto_ptr m_port_manager;
  |^~~~
/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |^~~~
./olad/OlaServer.h:190:8: warning: ‘template class std::auto_ptr’ is 
deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations]
  190 |   std::auto_ptr m_service_impl;
  |^~~~
/usr/include/c++/13/bits/unique_ptr.h:65:28: note: declared here
   65 |   template class auto_ptr;
  |^~~~
./olad/OlaServer.h:191:8: warning: ‘template class std::auto_ptr’ is 
deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations]
  191 

Bug#1074583: marked as done (getmail6: fails at startup with "TypeError: IMAP4_SSL.__init__()" after change to python3.12 )

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 19:04:09 +
with message-id 
and subject line Bug#1074583: fixed in getmail6 6.19.02-1
has caused the Debian Bug report #1074583,
regarding getmail6: fails at startup with "TypeError: IMAP4_SSL.__init__()" 
after change to python3.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.)


-- 
1074583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: getmail6
Version: 6.19.01-1
Severity: grave

getmail6 now crashes at startup with the error shown below in the
transcript.  It works fine with Python 3.11:

  $ python3.11 /usr/bin/getmail --rcfile=rc-inbox
  getmail version 6.19.01
  Copyright (C) 1998-2024 Charles Cazabon and others. Licensed under GNU GPL 
version 2.
  SimpleIMAPSSLRetriever:san...@mit.edu@outlook.office365.com:993:
0 messages (0 bytes) retrieved, 0 skipped

My system (mostly running 'unstable') just changed to Python 3.12 a day
or so ago, and getmail6 has failed since then (but not before).  Thus, I
suspect something is now incompatible between the getmail code and
Python 3.12's expectations.

Here is promised failure transcript with Python 3.12:

  $ /usr/bin/getmail --rcfile=rc-inbox
  getmail version 6.19.01
  Copyright (C) 1998-2024 Charles Cazabon and others. Licensed under GNU GPL 
version 2.
  SimpleIMAPSSLRetriever:san...@mit.edu@outlook.office365.com:993:

  Exception: please read docs/BUGS and include the following information in any 
bug report:

getmail version 6.19.01
Python version 3.12.4 (main, Jun 12 2024, 19:06:53) [GCC 13.2.0]

  Unhandled exception follows:
  File "/usr/bin/getmail", line 1077, in main
  success = go(configs, options.idle, options.only_account)
^^^
  File "/usr/bin/getmail", line 188, in go
  retriever.initialize(options)
  File "/usr/lib/python3/dist-packages/getmailcore/_retrieverbases.py", 
line 1807, in initialize
  self._connect()
  File "/usr/lib/python3/dist-packages/getmailcore/_retrieverbases.py", 
line 714, in _connect
  self.conn = imaplib.IMAP4_SSL(
  ^^
TypeError: IMAP4_SSL.__init__() takes from 1 to 3 positional arguments but 
5 were given

  Please also include configuration information from running getmail
  with your normal options plus "--dump".


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

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

Versions of packages getmail6 depends on:
ii  python3  3.12.2-1

getmail6 recommends no packages.

getmail6 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: getmail6
Source-Version: 6.19.02-1
Done: Sudip Mukherjee 

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated getmail6 
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, 08 Jul 2024 19:32:10 +0100
Source: getmail6
Architecture: source
Version: 6.19.02-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sudip Mukherjee 
Closes: 1074583
Changes:
 getmail6 (6.19.02-1) unstable; urgency=medium
 .
   * New upstream version 6.19.02
   * Add upstream patch to fix error with python3.12. (Closes: #1074583)
Checksums-Sha1:
 6599612a9f17f2dda4cc1655c23b5d4d95d94624 2042 getmail6_6.19.02-1.dsc
 1f2a7237df17adb377f6c362ae885fa4e779f39e 215162 getmail6_6.19.02.orig.tar.gz
 c4b73b90d59eecf740063ff7b69084145513ddf7 3884 

Bug#1071007: Update available upstream

[Paul Pfeister]

Hey all

Upstream has been bumped to 0.15.0, and with this, the importable
module has been renamed from `sherlock` to `sherlock_project`.

Repackaging should allow both Serious bugs to be closed.

As indicated in the prior...

With this, upstream has also moved to adopt properly tagged releases,
so long git ref version numbers should no longer be needed. Proper
version numbers such as 0.15.0-1 are now possible.

Packager can also get rid of the only-run-one-test solution for unit
testing, as there is built in support for offline-only unit tests via
either `tox -e offline` (preferred for consistency) or `pytest -m "not
online"` and their respective macros.

Feel free to reach out with any questions or help with implementation.

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

[Matthias Geiger]

On 08.07.24 18:45, Jonas Smedegaard wrote:

Quoting Matthias Geiger (2024-07-07 11:21:07)

On 07.07.24 10:10, Jonas Smedegaard wrote:
[...]

[...]

isahc requires sluice only for some pipe functionality in two files.
Since patching sluice proves to be hard I'd

opt to patch isahc to use something like stdio::piped() rather than
sluice::pipe. Then I can file a RM request for sluice since it's not
used elsewhere and we can finish this transition.

Makes great sense.


I attached my wip for using os_pipe instead of sluice. Still has four 
errors atm; I'd appreciate some knowledgable people looking into it 
(CC'd ncts). I do not have any more time atm to sink into this; will 
pick it up later unless someone beats me to it.


best,

werdahias
diff --git a/Cargo.toml b/Cargo.toml
index e1ab8ef..351fbc1 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -35,6 +35,7 @@ unstable-interceptors = []
 async-channel = "1.4.2"
 castaway = "0.1.1"
 crossbeam-utils = ">=0.7.0, <0.9.0"
+os_pipe = "*"
 curl = "0.4.36"
 curl-sys = "0.4.55"
 event-listener = "2.3.3"
@@ -44,7 +45,6 @@ log = "0.4"
 once_cell = "1"
 polling = "2"
 slab = "0.4"
-sluice = "0.5.4"
 url = "2.1"
 waker-fn = "1"
 
diff --git a/src/body/sync.rs b/src/body/sync.rs
index e035dee..fe6d380 100644
--- a/src/body/sync.rs
+++ b/src/body/sync.rs
@@ -1,11 +1,11 @@
 use super::AsyncBody;
 use futures_lite::{future::yield_now, io::AsyncWriteExt};
-use sluice::pipe::{pipe, PipeWriter};
+use os_pipe::{PipeWriter, pipe};
 use std::{
 borrow::Cow,
 fmt,
 fs::File,
-io::{Cursor, ErrorKind, Read, Result},
+io::{Cursor, ErrorKind, Read, Result, Write},
 };
 
 /// Contains the body of a synchronous HTTP request or response.
@@ -158,7 +158,8 @@ impl Body {
 Inner::Empty => (AsyncBody::empty(), None),
 Inner::Buffer(cursor) => (AsyncBody::from_bytes_static(cursor.into_inner()), None),
 Inner::Reader(reader, len) => {
-let (pipe_reader, writer) = pipe();
+
+let Ok((pipe_reader, writer)) = pipe();
 
 (
 if let Some(len) = len {
@@ -275,7 +276,7 @@ impl Writer {
 Err(e) => return Err(e),
 };
 
-self.writer.write_all([..len]).await?;
+self.writer.write_all([..len]);
 }
 }
 }
diff --git a/src/handler.rs b/src/handler.rs
index 92445f6..05c9fc9 100644
--- a/src/handler.rs
+++ b/src/handler.rs
@@ -14,7 +14,7 @@ use curl_sys::CURL;
 use futures_lite::io::{AsyncRead, AsyncWrite};
 use http::Response;
 use once_cell::sync::OnceCell;
-use sluice::pipe;
+use os_pipe::{pipe, PipeReader};
 use std::{
 ascii,
 ffi::CStr,
@@ -79,7 +79,7 @@ pub(crate) struct RequestHandler {
 response_headers: http::HeaderMap,
 
 /// Writing end of the pipe where the response body is written.
-response_body_writer: pipe::PipeWriter,
+response_body_writer: os_pipe::PipeWriter,
 
 /// A waker used with writing the response body asynchronously. Populated by
 /// an agent when the request is initialized.
@@ -126,7 +126,7 @@ impl RequestHandler {
 ) {
 let (sender, receiver) = async_channel::bounded(1);
 let shared = Arc::new(Shared::default());
-let (response_body_reader, response_body_writer) = pipe::pipe();
+let Ok((response_body_reader, response_body_writer)) = os_pipe::pipe() else { todo!() };
 
 let handler = Self {
 span: tracing::debug_span!("handler", id = tracing::field::Empty),
@@ -672,7 +672,8 @@ impl fmt::Debug for RequestHandler {
 /// Wrapper around a pipe reader that returns an error that tracks transfer
 /// cancellation.
 pub(crate) struct ResponseBodyReader {
-inner: pipe::PipeReader,
+inner: os_pipe::PipeReader,
+
 shared: Arc,
 }
 

Bug#1074519: graph-tool: autopkgtest failure with Python 3.12

[Graham Inggs]

Control: reopen -1

Hi Jerome

The test still seems to be failing with graph-tool/2.71+ds-1.

Regards
Graham

Processed: graph-tool: autopkgtest failure with Python 3.12

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1074519 {Done: Jerome BENOIT } [src:graph-tool] 
graph-tool: autopkgtest failure with Python 3.12
Bug reopened
Ignoring request to alter fixed versions of bug #1074519 to the same values 
previously set

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

Processed: fixed 1072480 in condor/23.6.2+dfsg-1

[Debian Bug Tracking System]

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

> fixed 1072480 condor/23.6.2+dfsg-1
Bug #1072480 {Done: Tim Theisen } [src:condor] condor: 
hard-coded dependencies on pre-t64 libraries
Marked as fixed in versions condor/23.6.2+dfsg-1.
> thanks
Stopping processing here.

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

Processed: tagging 1065848

[Debian Bug Tracking System]

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

> tags 1065848 + pending
Bug #1065848 [src:docker-compose] docker-compose: Please drop dependencies on 
python3-distutils
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1065848: docker-compose: Please drop dependencies on python3-distutils

[Emmanuel Arias]

Dear maintainer,

I am planning a NMU for docker-compose package to remove
python3-distutils package from dependency. I tested the patch and it
work for me and is attached to this bug report. I'm going to upload to
DELAYED/3-days, to give you time to review it and provide feedback if it
needed.

If you have any objections or would you like to make the changes
yourself please let me know.

-- 
cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
 
 ⠈⠳⣄
diff -Nru docker-compose-1.29.2/debian/changelog docker-compose-1.29.2/debian/changelog
--- docker-compose-1.29.2/debian/changelog	2023-08-11 12:05:52.0 -0300
+++ docker-compose-1.29.2/debian/changelog	2024-07-08 12:49:42.0 -0300
@@ -1,3 +1,13 @@
+docker-compose (1.29.2-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/patches/remove_distutils.patch: Add patch to remove the use of
+python3-distutils.
+  * d/control: Remove python3-distutils from binary packages Dependency.
+Replaced by python3-packaging (Closes: #1065848).
+
+ -- Emmanuel Arias   Mon, 08 Jul 2024 12:49:42 -0300
+
 docker-compose (1.29.2-6) unstable; urgency=medium
 
   * Source-only rebuild.
diff -Nru docker-compose-1.29.2/debian/control docker-compose-1.29.2/debian/control
--- docker-compose-1.29.2/debian/control	2023-08-11 12:05:52.0 -0300
+++ docker-compose-1.29.2/debian/control	2024-07-08 12:49:12.0 -0300
@@ -33,8 +33,8 @@
 Depends:
  ${misc:Depends},
  ${python3:Depends},
- python3-distutils,
  python3-compose (= ${binary:Version}),
+ python3-packaging,
 Recommends: docker.io (>= 1.9.0)
 Description: define and run multi-container Docker applications with YAML
  docker-compose is a service management software built on top of docker. Define
@@ -48,7 +48,7 @@
 Depends:
  ${misc:Depends},
  ${python3:Depends},
- python3-distutils,
+ python3-packaging,
 Replaces: docker-compose (<< 1.29.2-4~)
 Breaks: docker-compose (<< 1.29.2-4~)
 Description: Python implementation of docker-compose file specification
diff -Nru docker-compose-1.29.2/debian/patches/remove_distutils.patch docker-compose-1.29.2/debian/patches/remove_distutils.patch
--- docker-compose-1.29.2/debian/patches/remove_distutils.patch	1969-12-31 21:00:00.0 -0300
+++ docker-compose-1.29.2/debian/patches/remove_distutils.patch	2024-07-08 12:49:42.0 -0300
@@ -0,0 +1,87 @@
+Description: Remove use of distutils
+ distutils is deprecated. This patch remove the references to distutils. In the project
+ was used by the find_executable call that was replaced by shutil.which. In the other
+ hand, LooseVersion was replaced by packaging.version.Version.
+Author: Emmanuel Arias 
+Bug-Debian: https://bugs.debian.org/1065848
+Forwarded: no
+Last-Update: 2024-07-08
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/compose/cli/errors.py
 b/compose/cli/errors.py
+@@ -1,7 +1,7 @@
+ import contextlib
+ import logging
+ import socket
+-from distutils.spawn import find_executable
++from shutil import which
+ from textwrap import dedent
+ 
+ from docker.errors import APIError
+@@ -114,11 +114,11 @@
+ 
+ def get_conn_error_message(url):
+ try:
+-if find_executable('docker') is None:
++if which('docker') is None:
+ return docker_not_found_msg("Couldn't connect to Docker daemon.")
+ if is_docker_for_mac_installed():
+ return conn_error_docker_for_mac
+-if find_executable('docker-machine') is not None:
++if which('docker-machine') is not None:
+ return conn_error_docker_machine
+ except UnicodeDecodeError:
+ # https://github.com/docker/compose/issues/5442
+--- a/compose/cli/main.py
 b/compose/cli/main.py
+@@ -6,7 +6,7 @@
+ import re
+ import subprocess
+ import sys
+-from distutils.spawn import find_executable
++from shutil import which
+ from inspect import getdoc
+ from operator import attrgetter
+ 
+@@ -1547,7 +1547,7 @@
+ 
+ 
+ def call_docker(args, dockeropts, environment):
+-executable_path = find_executable('docker')
++executable_path = which('docker')
+ if not executable_path:
+ raise UserError(errors.docker_not_found_msg("Couldn't find `docker` binary."))
+ 
+--- a/compose/version.py
 b/compose/version.py
+@@ -1,7 +1,7 @@
+-from distutils.version import LooseVersion
++from packaging.version import Version
+ 
+ 
+-class ComposeVersion(LooseVersion):
++class ComposeVersion(Version):
+ """ A hashable version object """
+ def __hash__(self):
+ return hash(self.vstring)
+--- a/tests/integration/service_test.py
 b/tests/integration/service_test.py
+@@ -2,7 +2,7 @@
+ import re
+ import shutil
+ import tempfile
+-from distutils.spawn import find_executable
++from shutil import which
+ from io import StringIO
+ from os import path
+ 
+@@ -171,7 +171,7 @@
+ @pytest.mark.xfail(True, reason='Option has been removed in 

Bug#1072480: marked as done (condor: hard-coded dependencies on pre-t64 libraries)

[Debian Bug Tracking System]

Your message dated Mon, 8 Jul 2024 11:25:39 -0500
with message-id <67afaab7-b7b0-4222-befc-8de32476c...@cs.wisc.edu>
and subject line Re: condor: hard-coded dependencies on pre-t64 libraries
has caused the Debian Bug report #1072480,
regarding condor: hard-coded dependencies on pre-t64 libraries
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.)


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

condor has a bunch of hard-coded dependencies. At least one of them
(libssl3) got renamed as part of the t64 transition. Please take a look
at the changes in Ubuntu on how to compute these dependencies.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
condor 23.6.2 has been accepted into unstable. Closing this bug as it is 
a duplicate of #106766, since that bug was fixed.


...Tim

--
Tim Theisen (he, him, his)
Release Manager
HTCondor & Open Science Grid
Center for High Throughput Computing
Department of Computer Sciences
University of Wisconsin - Madison
4261 Computer Sciences and Statistics
1210 W Dayton St
Madison, WI 53706-1685
+1 608 265 5736--- End Message ---

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

[Jonas Smedegaard]

Quoting Matthias Geiger (2024-07-07 11:21:07)
> On 07.07.24 10:10, Jonas Smedegaard wrote:
> [...]
> >> Patching sluice seems not trivial. Given that it's sole rdep is isahc,
> >> would you be ok with me filing a RM request for it if I patch isahc to
> >> use standard rust pipes ? imo this is the easiest option going forward.
> >> The code changes look more doable than patching sluice.
> >   
> > I would ertainly be happy getting help with isahc, but I don't quite
> > understand what you are proposing concretely - how will patching isahc
> > also require an RM request?!?
> isahc requires sluice only for some pipe functionality in two files. 
> Since patching sluice proves to be hard I'd
> 
> opt to patch isahc to use something like stdio::piped() rather than 
> sluice::pipe. Then I can file a RM request for sluice since it's not 
> used elsewhere and we can finish this transition.

Makes great sense.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1075969: python3-fitz: error when launching pymupdf

[Eric Valette]

Package: python3-fitz
Version: 1.24.2+ds1-2
Severity: grave
Justification: renders package unusable

/usr/bin/pymupdf
Traceback (most recent call last):
  File "/usr/bin/pymupdf", line 5, in 
from fitz.__main__ import main
ModuleNotFoundError: No module named 'fitz'

 dpkg -L python3-fitz 
/.
/usr
/usr/bin
/usr/bin/pymupdf
/usr/lib
/usr/lib/python3
/usr/lib/python3/dist-packages
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/INSTALLER
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/METADATA
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/README.md
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/WHEEL
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/entry_points.txt
/usr/lib/python3/dist-packages/fitz_old
/usr/lib/python3/dist-packages/fitz_old/__init__.py
/usr/lib/python3/dist-packages/fitz_old/__main__.py
/usr/lib/python3/dist-packages/fitz_old/_fitz_old.cpython-311-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/fitz_old/_fitz_old.cpython-312-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/fitz_old/fitz_old.py
/usr/lib/python3/dist-packages/fitz_old/table.py
/usr/lib/python3/dist-packages/fitz_old/utils.py



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

Kernel: Linux 6.6.37 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-fitz depends on:
ii  libc62.39-3.1
ii  libfreetype6 2.13.2+dfsg-1+b4
ii  libgumbo20.12.0+dfsg-2+b1
ii  libharfbuzz0b8.3.0-2+b1
ii  libjbig2dec0 0.20-1+b2
ii  libjpeg62-turbo  1:2.1.5-3
ii  libmujs3 1.3.3-3+b2
ii  libopenjp2-7 2.5.0-2+b3
ii  python3  3.12.2-1

python3-fitz recommends no packages.

python3-fitz suggests no packages.

-- no debconf information

Processed: Re: Bug#1075793: plastimatch FTBFS with DCMTK 3.6.8

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 
> https://gitlab.com/plastimatch/plastimatch/-/commit/a1a6f4da5681735544db1239ddd3d01066ce10d8
Bug #1075793 [src:plastimatch] plastimatch FTBFS with DCMTK 3.6.8
Set Bug forwarded-to-address to 
'https://gitlab.com/plastimatch/plastimatch/-/commit/a1a6f4da5681735544db1239ddd3d01066ce10d8'.
> tags -1 patch
Bug #1075793 [src:plastimatch] plastimatch FTBFS with DCMTK 3.6.8
Added tag(s) patch.

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

Bug#1075793: plastimatch FTBFS with DCMTK 3.6.8

[Adrian Bunk]

Control: forwarded -1 
https://gitlab.com/plastimatch/plastimatch/-/commit/a1a6f4da5681735544db1239ddd3d01066ce10d8
Control: tags -1 patch

On Fri, Jul 05, 2024 at 11:19:57AM +0200, Mathieu Malaterre wrote:
> Source: plastimatch
> Version: 1.9.4+dfsg.1-2
> Severity: serious
> Tags: ftbfs
> 
> /<>/src/plastimatch/base/dcmtk_rtss.cxx: In member
> function ‘void Dcmtk_rt_study::rtss_save(const char*)’:
> /<>/src/plastimatch/base/dcmtk_rtss.cxx:475:46: error:
> ‘DCM_ROIObservationLabel’ was not declared in this scope; did you mean
> ‘DCM_ObservationNumber’?
>   475 | rtroio_item->putAndInsertString (DCM_ROIObservationLabel,
>   |  ^~~
>   |  DCM_ObservationNumber
> 
> https://people.debian.org/~emollier/transitions/dcmtk/plastimatch_dcmtk.build.xz
> 
> It has been retired:
> 
> % cat dcmdata/include/dcmtk/dcmdata/dcdeftag.h | grep 3006 | grep 85
> #define DCM_RETIRED_ROIObservationLabel  DcmTagKey(0x3006, 0x0085)

The commit above (applied to src/plastimatch/base/dcmtk_rtss.cxx) firxes 
the build.

cu
Adrian

Bug#1075916: marked as done (libdcmtk-dev: Removed dependencies are required for a CMake target)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 15:56:09 +
with message-id 
and subject line Bug#1075916: fixed in orthanc 1.12.4+dfsg-3
has caused the Debian Bug report #1075916,
regarding libdcmtk-dev: Removed dependencies are required for a CMake target
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.)


-- 
1075916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdcmtk-dev
Version: 3.6.8-5
Severity: serious
Tags: ftbfs
Control: affects -1 src:orthanc-neuro

https://buildd.debian.org/status/logs.php?pkg=orthanc-neuro=1.1%2Bdfsg-1%2Bb1

...
[ 90%] Linking CXX shared library libOrthancNeuro.so
/usr/bin/cmake -E cmake_link_script CMakeFiles/OrthancNeuro.dir/link.txt 
--verbose=1
/usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wno-long-long -Wno-variadic-macros -Wl,-z,relro 
-Wl,-z,now -Wl,--no-undefined -Wl,--as-needed 
-Wl,--version-script=/<>/Resources/Orthanc/Plugins/VersionScriptPlugins.map
 -shared -Wl,-soname,libOrthancNeuro.so.1.1 -o libOrthancNeuro.so.1.1 
CMakeFiles/OrthancNeuro.dir/Sources/Plugin/Plugin.cpp.o 
CMakeFiles/OrthancNeuro.dir/Sources/Plugin/PluginFrameDecoder.cpp.o 
CMakeFiles/OrthancNeuro.dir/Sources/Framework/BufferReader.cpp.o 
CMakeFiles/OrthancNeuro.dir/Sources/Framework/CSAHeader.cpp.o 
CMakeFiles/OrthancNeuro.dir/Sources/Framework/CSATag.cpp.o 
CMakeFiles/OrthancNeuro.dir/Sources/Framework/DicomInstancesCollection.cpp.o 
CMakeFiles/OrthancNeuro.dir/Sources/Framework/IDicomFrameDecoder.cpp.o 
CMakeFiles/OrthancNeuro.dir/Sources/Framework/InputDicomInstance.cpp.o 
CMakeFiles/OrthancNeuro.dir/Sources/Framework/NeuroToolbox.cpp.o 
CMakeFiles/OrthancNeuro.dir/Sources/Framework/NiftiWriter.cpp.o 
CMakeFiles/OrthancNeuro.dir/Sources/Framework/Slice.cpp.o 
CMakeFiles/OrthancNeuro.dir/AUTOGENERATED/EmbeddedResources.cpp.o 
CMakeFiles/OrthancNeuro.dir/Resources/Orthanc/Plugins/OrthancPluginCppWrapper.cpp.o
  -lpthread -lrt -ldl -Wl,-Bstatic -lOrthancFramework -Wl,-Bdynamic -ldcmdata 
-ldcmjpls -ldcmimage -ldcmjpeg -lofstd -lboost_filesystem -lboost_iostreams 
-lboost_locale -lboost_regex -lboost_thread -lpugixml -luuid -ljsoncpp -lpng 
-ljpeg -lz -lniftiio -lznz -lrt -ldl -Wl,-Bstatic -lOrthancFramework 
-Wl,-Bdynamic -ldcmdata -ldcmjpls -ldcmimage -ldcmjpeg -lofstd 
-lboost_filesystem -lboost_iostreams -lboost_locale -lboost_regex 
-lboost_thread -lpugixml -luuid -ljsoncpp -lpng -ljpeg -lz -lniftiio -lznz
/usr/bin/ld: cannot find -lpng: No such file or directory
/usr/bin/ld: cannot find -ljpeg: No such file or directory
/usr/bin/ld: cannot find -lpng: No such file or directory
/usr/bin/ld: cannot find -ljpeg: No such file or directory
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/OrthancNeuro.dir/build.make:300: 
libOrthancNeuro.so.1.1] Error 1



dcmtk (3.6.8-4) experimental; urgency=medium
...
  * d/control: Reduce number of dependencies for -dev package


That's problematic when the CMake files require them for some target:
  /usr/lib/x86_64-linux-gnu/cmake/dcmtk/DCMTKTargets.cmake:  
INTERFACE_LINK_LIBRARIES 
"DCMTK::oflog;DCMTK::dcmdata;DCMTK::dcmimgle;/usr/lib/x86_64-linux-gnu/libtiff.so;/usr/lib/x86_64-linux-gnu/libjpeg.so;/usr/lib/x86_64-linux-gnu/libpng.so"
--- End Message ---
--- Begin Message ---
Source: orthanc
Source-Version: 1.12.4+dfsg-3
Done: Sebastien Jodogne 

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

Debian distribution maintenance software
pp.
Sebastien Jodogne  (supplier of updated orthanc 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, 08 Jul 2024 17:02:24 +0200
Source: orthanc
Architecture: source
Version: 1.12.4+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sebastien Jodogne 
Closes: 1075916
Changes:
 orthanc (1.12.4+dfsg-3) unstable; urgency=medium
 .
   * Added dependency 

Bug#1075965: marked as done (libmpich-dev: libucx-dev dependency must not be unconditional)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 15:25:03 +
with message-id 
and subject line Bug#1075965: fixed in mpich 4.2.0-8
has caused the Debian Bug report #1075965,
regarding libmpich-dev: libucx-dev dependency must not be unconditional
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.)


-- 
1075965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmpich-dev
Version: 4.2.0-7
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Alastair McKinstry 

hpcc build-depends on:
- mpi-default-dev:armhf
mpi-default-dev depends on:
- libmpich-dev:armhf
libmpich-dev depends on missing:
- libucx-dev:armhf


Before it was dropped by accident, the libucx-dev followed
the build dependency:
  libucx-dev [amd64  ppc64el arm64]


BTW:
Unrelated (perhaps for experimental):
Should libucx-dev also be used on riscv64, where it is now available?
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 4.2.0-8
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated mpich 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, 08 Jul 2024 15:16:50 +0100
Source: mpich
Architecture: source
Version: 4.2.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 1075965
Changes:
 mpich (4.2.0-8) unstable; urgency=medium
 .
   * libucx-dev deps needs to be conditional. Drop ppc64el for now, add riscv64
 Closes: #1075965
Checksums-Sha1:
 cfb24452b803a04bdbee5f1cf9b055becfaf5b36 2763 mpich_4.2.0-8.dsc
 0ae88fdf27b7044a938ed99f113be9674dc373ce 350496 mpich_4.2.0-8.debian.tar.xz
Checksums-Sha256:
 544b44601e1a7d06501e02ffede9a0d40aeafc499daa43c1cbe42baeeaf000e4 2763 
mpich_4.2.0-8.dsc
 3972d781a7bdd080136111afc00348e1a0d1f1b5e376e260716382b67ee024dd 350496 
mpich_4.2.0-8.debian.tar.xz
Files:
 37fd371decc9a634456a1730dcb453fa 2763 devel optional mpich_4.2.0-8.dsc
 e31428f6d384dbcaec904b39cc8cfca6 350496 devel optional 
mpich_4.2.0-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmaL/8sACgkQy+a7Tl2a
06XSOQ//Xxrc+fqc1DXhK5IDug63iHknQaIkzyS4VKPqfpLFhYoulKztPeW0iWlt
7ng59V81goqbDuvTVJB3XFTqPfeLgDkssH8cDoQyOMBM7+TvyjGlrrHdtX+vaYM/
JtpCTWayqzfwv+pzzW9LarstkwALulZTIhx0Qf2b4YiOGtXN7hXW5dr6GsXrf/B/
4xRUz/mQiHeOOEp412XCbAkV/aEbJApvS7py9NK7k3RjmRQkEFeuPuNy+0BTgcUo
WdBPExJX65F1YzuulShkKYGzpBYrLnCsqMtVBI0L8r/E26E/eyQw3oNaXaqZsce+
l2JyC1YTIKar67C8krXwnoKUxyJCljCS03RzTLCT3epp6cmPOlVLaiWj+sQhVVS8
L00I1lmOKWzRfNQvdC/TSZLteGasvF2gK0vYJPdzxnA5+oZ45fWx+BEnI4di3HKS
AwRtR7Adzs+zlISRPqjq0kqsAObOVhKA238Xc8r4bz1gL945OnvHXoiLcasqVpOD
kSxMC3I00OhuFIFyMUqx+3/rC0cP2eixzddyz+GyErGmpbae9Z6VpyjCH/Lwsbft
2S7BlMnzgJ+VhscWmONLl8QsZraZtE/rm2O23F9wl6UtJrFWz3Sw9r0T4uZKofG3
v7tXkUouTBlZSmxJsMzKPqW/0liUwOiPw3wtpgIXmiz+joixEXE=
=/RMA
-END PGP SIGNATURE-



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

Bug#1065310: deborphan should take "Provides:" into account

[jim_p]

Package: deborphan
Version: 1.7.35
Followup-For: Bug #1065310
X-Debbugs-Cc: pitsior...@outlook.com

Thank you for the clarification. As it seems, there is no viable alternative to
deborphan right now :(


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

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

Versions of packages deborphan depends on:
ii  libc6  2.38-13

Versions of packages deborphan recommends:
ii  apt   2.9.6
ii  gettext-base  0.22.5-1

deborphan suggests no packages.

-- no debconf information

Bug#1075729: marked as done (znc: CVE-2024-39844)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 14:55:10 +
with message-id 
and subject line Bug#1075729: fixed in znc 1.9.1-1
has caused the Debian Bug report #1075729,
regarding znc: CVE-2024-39844
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.)


-- 
1075729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: znc
Version: 1.9.0-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.8.2-2
Control: found -1 1.8.2-3.1
Control: fixed -1 1.8.2-2+deb11u1
Control: fixed -1 1.8.2-3.1+deb12u1

Hi,

The following vulnerability was published for znc.

CVE-2024-39844[0]:
| In ZNC before 1.9.1, remote code execution can occur in modtcl via a
| KICK.

The version with above fixed versions were uploaded to security-master
and will be released in the upcoming DSA for znc.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-39844
https://www.cve.org/CVERecord?id=CVE-2024-39844
[1] https://wiki.znc.in/ChangeLog/1.9.1
[2] https://github.com/znc/znc/commit/8cbf8d628174ddf23da680f3f117dc54da0eb06e

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: znc
Source-Version: 1.9.1-1
Done: Patrick Matthäi 

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated znc 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, 08 Jul 2024 14:56:14 +0200
Source: znc
Architecture: source
Version: 1.9.1-1
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Closes: 1075729
Changes:
 znc (1.9.1-1) unstable; urgency=high
 .
   * New upstream release.
 - Fix RCE vulnerability in modtcl as described in CVE-2024-39844.
   Closes: #1075729
   * Bump Standards-Version to 4.7.0.
   * Add 1.8.2-3.1+deb12u1 changelog entry.
Checksums-Sha1:
 ebf721fa4729224776164efe6f4429f220149984 2437 znc_1.9.1-1.dsc
 fbaf45d698151b647316007430b690d58705d6ef 2236498 znc_1.9.1.orig.tar.gz
 d7f22af6b63b1dd1362836e53c92067dbe3a5b59 833 znc_1.9.1.orig.tar.gz.asc
 724106cc15f71a4c40b152900716eaf441e7f6e3 511980 znc_1.9.1-1.debian.tar.xz
 e34a469788b0e62b6a825de9dbda7ce4299fa69c 7991 znc_1.9.1-1_source.buildinfo
Checksums-Sha256:
 d706aa5eacf358daeed0b7ce9dc8915d9f9b10e933109ec6333781f5e0cc2e99 2437 
znc_1.9.1-1.dsc
 e8a7cf80e19aad510b4e282eaf61b56bc30df88ea2e0f64fadcdd303c4894f3c 2236498 
znc_1.9.1.orig.tar.gz
 99ba195266a6a1b0fcff3c4c005a11a2c417e0a34d4fd54bd5af37eef4be4e48 833 
znc_1.9.1.orig.tar.gz.asc
 6abc06549ec7c9b9599140d98891ffbcf42118894ce4a5eb5fa7643c6b14811c 511980 
znc_1.9.1-1.debian.tar.xz
 89e7b344747ab81ebce0fb87496a6cb24b40ce5903309064481ffbea39b73aac 7991 
znc_1.9.1-1_source.buildinfo
Files:
 5abd22e51d4be76a6409dbb18f81bd29 2437 net optional znc_1.9.1-1.dsc
 85ec4aec1c5d072c63c4b58f442e9710 2236498 net optional znc_1.9.1.orig.tar.gz
 cf1a4f3e05e33e83b5ee48c3a229f085 833 net optional znc_1.9.1.orig.tar.gz.asc
 dd4e002759df45c3a0d1fbb70d8e64b8 511980 net optional znc_1.9.1-1.debian.tar.xz
 cfa5de7f6a2e9c7aae2930aaa1056ed3 7991 net optional znc_1.9.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWKA9xYJCWk3IuQ4TEtmwSpDL2OQFAmaL7u8ACgkQEtmwSpDL
2ORWGA//UhDZsuaH0BV22VoKNkEWoazcy9W6Ado10//I0UlPxtTB4TRs2hlNjy60
IXCsDBdm3G/iBNCDMfJDj8r3mbOMewC4lhM2J8QsM+r6eAcesrkDB20rRdXTYmdI
k/unIYi3XEgN3fPPd0s5i3BbzqDYus0KwPHGET8JosAucsoWsYEjz7qz0Z3x+Nsl
HcLOFnVqXCrqtxKNAaiwbSUJPLOMjIvKMyN0yUSAn/7dyJBYFrucV0fHKaq4wiAv
8A2pf0GX0LhpXzz0Nn6f5yh4A8v2l1olm9/SYbTjSVfGi5QgC/8SYv4Nhvs+ReX+
/ectfRKnTIHMNGeu5nn3Xzxdd9LWmd6JxzD4Swm/tF+8SPdj2mt4+i6AyzyNe5dP
2/DG5aewOOxFWYp8zhUc8M2GQYiEeK32dRihI54z3zc9EEVPxj8Risu7vS/QiV3t
GRPudp2aAdxo/rffCA0s5f4x88ty2LeQhmOpyg+zsD/LtzH02WvRXegACY/FGO09

Bug#1074647: marked as done (jackd2: FTBFS: ModuleNotFoundError: No module named 'imp')

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 13:34:08 +
with message-id 
and subject line Bug#1074647: fixed in jackd2 1.9.22~dfsg-1
has caused the Debian Bug report #1074647,
regarding jackd2: FTBFS: ModuleNotFoundError: No module named 'imp'
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.)


-- 
1074647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jackd2
Version: 1.9.21~dfsg-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 ./waf configure \
>   --prefix=/usr --classic --example-tools \
>   --libdir=/usr/lib/x86_64-linux-gnu \
>   --alsa --dbus --firewire \
>   CC='x86_64-linux-gnu-gcc' CXX='x86_64-linux-gnu-g++' 
> PKGCONFIG='x86_64-linux-gnu-pkgconf'
> /<>/waflib/Utils.py:733: SyntaxWarning: invalid escape sequence 
> '\d'
>   return re.split('\d+$', s)[0]
> /<>/waflib/ConfigSet.py:14: SyntaxWarning: invalid escape 
> sequence '\ '
>   re_imp = re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$', re.M)
> /<>/waflib/ansiterm.py:267: SyntaxWarning: invalid escape 
> sequence '\['
>   ansi_tokens = re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
> /<>/waflib/Context.py:610: SyntaxWarning: invalid escape 
> sequence '\_'
>   """
> Traceback (most recent call last):
>   File "/<>/./waf", line 166, in 
> from waflib import Scripting
>   File "/<>/waflib/Scripting.py", line 10, in 
> from waflib import Utils, Configure, Logs, Options, ConfigSet, Context, 
> Errors, Build, Node
>   File "/<>/waflib/Configure.py", line 16, in 
> from waflib import ConfigSet, Utils, Options, Logs, Context, Build, Errors
>   File "/<>/waflib/Options.py", line 14, in 
> from waflib import Logs, Utils, Context, Errors
>   File "/<>/waflib/Context.py", line 9, in 
> import os, re, imp, sys
> ModuleNotFoundError: No module named 'imp'
> make[1]: *** [debian/rules:22: override_dh_auto_configure] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/jackd2_1.9.21~dfsg-3_unstable.log

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated jackd2 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, 08 Jul 2024 15:25:39 +0200
Source: jackd2
Architecture: source
Version: 1.9.22~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 1074647
Changes:
 jackd2 (1.9.22~dfsg-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Nicholas D Steeves ]
   * Mark reproducibility patches as forwarded, and set URL
 .
   [ Sebastian Ramacher ]
   * New upstream version 1.9.22~dfsg
   * debian/patches:
 - Remove patches included upstream
 - Refresh patches
 - Fix build with Python 3.12 (Closes: #1074647)
   * debian/control:
 - Bump Standards-Version
 - Drop unnecessary pkg-config dependency from -dev packages
   * debian/: No 

Processed: Bug#1074647 marked as pending in jackd2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1074647 [src:jackd2] jackd2: FTBFS: ModuleNotFoundError: No module named 
'imp'
Added tag(s) pending.

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

Bug#1074647: marked as pending in jackd2

[Sebastian Ramacher]

Control: tag -1 pending

Hello,

Bug #1074647 in jackd2 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/multimedia-team/jackd2/-/commit/bf264de8ee7a07e83eb9e5a76cba22a33b8ceca6


Fix build with Python 3.12

Closes: #1074647


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1074647

Bug#1069405: marked as done (x11-apps: FTBFS with libxcb 1.17: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met)

[Debian Bug Tracking System]

Your message dated Mon, 8 Jul 2024 15:28:19 +0200
with message-id 

and subject line Re: x11-apps: FTBFS on arm64: configure: error: Package 
requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met
has caused the Debian Bug report #1069405,
regarding x11-apps: FTBFS with libxcb 1.17: Package requirements (x11-xcb 
xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met
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.)


-- 
1069405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: x11-apps
Version: 7.7+11
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
> checking if gcc supports -Werror=attributes... yes
> checking whether make supports nested variables... (cached) yes
> checking for xi >= 1.7 x11 xt xext xmu xproto >= 7.0.17... yes
> checking for xrender >= 0.4... yes
> checking for x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage... no
> configure: error: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes 
> xcb-damage) were not met
> 
> Package 'xcb-dri3', required by 'xcb-present', not found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables PRESENT_CFLAGS
> and PRESENT_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>   cd xeyes-build && tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/x11-apps_7.7+11_unstable-arm64.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 ---
This problem is not present in unstable anymore, so I presume
#1069408 fixed it.

Chris--- End Message ---

Bug#1066678: marked as done (lacheck: FTBFS: ./lacheck.lex:1328:32: error: implicit declaration of function ‘isatty’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Mon, 8 Jul 2024 16:16:57 +0300
with message-id 
and subject line Fixed in 1.26-17.1
has caused the Debian Bug report #1066678,
regarding lacheck: FTBFS: ./lacheck.lex:1328:32: error: implicit declaration of 
function ‘isatty’ [-Werror=implicit-function-declaration]
to be marked as done.

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

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


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

Hi,

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

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

Relevant part (hopefully):
> cc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2  -c -o lacheck.o lacheck.c
> ./lacheck.lex: In function ‘yy_init_buffer’:
> ./lacheck.lex:1328:32: error: implicit declaration of function ‘isatty’ 
> [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
> make[2]: *** [: lacheck.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/lacheck_1.26-17_unstable.log

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

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

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

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

lacheck (1.26-17.1) unstable; urgency=medium
...
  * Fix building with -Werror=implicit-function-declaration.
...
 -- Andreas Beckmann   Fri, 28 Jun 2024 09:06:10 +0200--- End Message ---

Bug#1075965: libmpich-dev: libucx-dev dependency must not be unconditional

[Adrian Bunk]

Package: libmpich-dev
Version: 4.2.0-7
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Alastair McKinstry 

hpcc build-depends on:
- mpi-default-dev:armhf
mpi-default-dev depends on:
- libmpich-dev:armhf
libmpich-dev depends on missing:
- libucx-dev:armhf


Before it was dropped by accident, the libucx-dev followed
the build dependency:
  libucx-dev [amd64  ppc64el arm64]


BTW:
Unrelated (perhaps for experimental):
Should libucx-dev also be used on riscv64, where it is now available?

Bug#1075916: libdcmtk-dev: Removed dependencies are required for a CMake target

[Sébastien Jodogne]

Hello Adrian,

> orthanc-neuro builds and links with the shared library when I remove the
> -DORTHANC_FRAMEWORK_USE_SHARED:BOOL=OFF, is there any reason why this
> would not work?

This would not work, because the libOrthancFramework.so shared library
is designed to share code between the Orthanc core and its plugin, and
has not a stable C++ ABI across versions of Orthanc. Static linking is
definitely needed here.

I think that the fix simply consists in adding "libpng-dev" and
"libjpeg-dev" to the "Depends" of "liborthancframwork-dev". These
dependencies were formerly part of "libdcmtk-dev", but have been
removed by the following changeset in the "debian/experimental"
branch, which breaks the packages that build-depend on
"liborthancframework-dev" since its reintegration into master:
https://salsa.debian.org/med-team/dcmtk/-/commit/f032735429e36f188aeac6e9002255ef00f743ab

Kind Regards,
Sébastien-

Bug#1074660: marked as done (python-mapnik: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'mapnik-config')

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 13:06:30 +
with message-id 
and subject line Bug#1069130: fixed in python-mapnik 1:0.0~20240222-5ab32f020-1
has caused the Debian Bug report #1069130,
regarding python-mapnik: FTBFS: FileNotFoundError: [Errno 2] No such file or 
directory: 'mapnik-config'
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.)


-- 
1069130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mapnik
Version: 1:0.0~20200224-7da019cf9-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 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:311: python3.11 setup.py config 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 99, in 
> lib_path = os.path.join(check_output([mapnik_config, '--prefix']),'lib')
> ^
>   File "/<>/setup.py", line 19, in check_output
> output = subprocess.check_output(args)
>  ^
>   File "/usr/lib/python3.11/subprocess.py", line 466, in check_output
> return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
>^
>   File "/usr/lib/python3.11/subprocess.py", line 548, in run
> with Popen(*popenargs, **kwargs) as process:
>  ^^^
>   File "/usr/lib/python3.11/subprocess.py", line 1026, in __init__
> self._execute_child(args, executable, preexec_fn, close_fds,
>   File "/usr/lib/python3.11/subprocess.py", line 1955, in _execute_child
> raise child_exception_type(errno_num, err_msg, err_filename)
> FileNotFoundError: [Errno 2] No such file or directory: 'mapnik-config'
> E: pybuild pybuild:389: configure: plugin distutils failed with: exit code=1: 
> python3.11 setup.py config 
> dh_auto_configure: error: pybuild --configure -i python{version} -p "3.11 
> 3.12" returned exit code 13
> make: *** [debian/rules:22: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/python-mapnik_0.0~20200224-7da019cf9-5_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-mapnik
Source-Version: 1:0.0~20240222-5ab32f020-1
Done: Bas Couwenberg 

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

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

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated python-mapnik 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, 08 Jul 2024 14:13:46 +0200
Source: python-mapnik
Architecture: source
Version: 1:0.0~20240222-5ab32f020-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1069130
Changes:
 python-mapnik (1:0.0~20240222-5ab32f020-1) unstable; urgency=medium
 .
   * Require at least libmapnik-dev 4.0.0.
   * Add patch by Gianfranco Costamagna to fix FTBFS with Mapnik 4.0.0.
 (closes: #1069130)
   * Move 

Processed: xorg: diff for NMU version 1:7.7+23.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1070350 + patch
Bug #1070350 [xorg-dev] xorg-dev: drop dependency on libdmx-dev
Added tag(s) patch.
> tags 1070350 + pending
Bug #1070350 [xorg-dev] xorg-dev: drop dependency on libdmx-dev
Added tag(s) pending.

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

Bug#1070350: xorg: diff for NMU version 1:7.7+23.1

[Chris Hofstaedtler]

Control: tags 1070350 + patch
Control: tags 1070350 + pending


I've checked the archive and apparently nothing (build-)depends on
xorg-dev. Thus it seems safe to remove libdmx-dev from this
metapackage.

I've uploaded an NMU as 1:7.7+23.1 to DELAYED/10.

Feel free to reschedule / supersede / cancel.

Best,
Chris

diff -Nru xorg-7.7+23/debian/changelog xorg-7.7+23.1/debian/changelog
--- xorg-7.7+23/debian/changelog	2021-08-18 13:00:51.0 +0200
+++ xorg-7.7+23.1/debian/changelog	2024-07-08 14:45:55.0 +0200
@@ -1,3 +1,10 @@
+xorg (1:7.7+23.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop libdmx-dev from xorg-dev meta-package. (Closes: #1070350)
+
+ -- Chris Hofstaedtler   Mon, 08 Jul 2024 14:45:55 +0200
+
 xorg (1:7.7+23) unstable; urgency=medium
 
   [ Timo Aaltonen ]
diff -Nru xorg-7.7+23/debian/control xorg-7.7+23.1/debian/control
--- xorg-7.7+23/debian/control	2021-08-18 09:24:40.0 +0200
+++ xorg-7.7+23.1/debian/control	2024-07-08 14:45:44.0 +0200
@@ -125,7 +125,6 @@
 Package: xorg-dev
 Architecture: all
 Depends:
- libdmx-dev,
  libfontenc-dev,
  libfs-dev,
  libice-dev,

Bug#1075916: libdcmtk-dev: Removed dependencies are required for a CMake target

[Adrian Bunk]

On Mon, Jul 08, 2024 at 08:23:57AM +0200, Mathieu Malaterre wrote:
> Control: reassign -1 liborthancframework-dev
> 
> On Sun, Jul 7, 2024 at 9:48 PM Adrian Bunk  wrote:
> >
> > Package: libdcmtk-dev
> > Version: 3.6.8-5
> > Severity: serious
> > Tags: ftbfs
> > Control: affects -1 src:orthanc-neuro
> >
> > https://buildd.debian.org/status/logs.php?pkg=orthanc-neuro=1.1%2Bdfsg-1%2Bb1
> >
> > ...
> > [ 90%] Linking CXX shared library libOrthancNeuro.so
> > /usr/bin/cmake -E cmake_link_script CMakeFiles/OrthancNeuro.dir/link.txt 
> > --verbose=1
> > /usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. 
> > -fstack-protector-strong -fstack-clash-protection -Wformat 
> > -Werror=format-security -fcf-protection -DNDEBUG -Wdate-time 
> > -D_FORTIFY_SOURCE=2 -Wall -Wno-long-long -Wno-variadic-macros -Wl,-z,relro 
> > -Wl,-z,now -Wl,--no-undefined -Wl,--as-needed 
> > -Wl,--version-script=/<>/Resources/Orthanc/Plugins/VersionScriptPlugins.map
> >  -shared -Wl,-soname,libOrthancNeuro.so.1.1 -o libOrthancNeuro.so.1.1 
> > CMakeFiles/OrthancNeuro.dir/Sources/Plugin/Plugin.cpp.o 
> > CMakeFiles/OrthancNeuro.dir/Sources/Plugin/PluginFrameDecoder.cpp.o 
> > CMakeFiles/OrthancNeuro.dir/Sources/Framework/BufferReader.cpp.o 
> > CMakeFiles/OrthancNeuro.dir/Sources/Framework/CSAHeader.cpp.o 
> > CMakeFiles/OrthancNeuro.dir/Sources/Framework/CSATag.cpp.o 
> > CMakeFiles/OrthancNeuro.dir/Sources/Framework/DicomInstancesCollection.cpp.o
> >  CMakeFiles/OrthancNeuro.dir/Sources/Framework/IDicomFrameDecoder.cpp.o 
> > CMakeFiles/OrthancNeuro.dir/Sources/Framework/InputDicomInstance.cpp.o 
> > CMakeFiles/OrthancNeuro.dir/Sources/Framework/NeuroToolbox.cpp.o 
> > CMakeFiles/OrthancNeuro.dir/Sources/Framework/NiftiWriter.cpp.o 
> > CMakeFiles/OrthancNeuro.dir/Sources/Framework/Slice.cpp.o 
> > CMakeFiles/OrthancNeuro.dir/AUTOGENERATED/EmbeddedResources.cpp.o 
> > CMakeFiles/OrthancNeuro.dir/Resources/Orthanc/Plugins/OrthancPluginCppWrapper.cpp.o
> >   -lpthread -lrt -ldl -Wl,-Bstatic -lOrthancFramework -Wl,-Bdynamic 
> > -ldcmdata -ldcmjpls -ldcmimage -ldcmjpeg -lofstd -lboost_filesystem 
> > -lboost_iostreams -lboost_locale -lboost_regex -lboost_thread -lpugixml 
> > -luuid -ljsoncpp -lpng -ljpeg -lz -lniftiio -lznz -lrt -ldl -Wl,-Bstatic 
> > -lOrthancFramework -Wl,-Bdynamic -ldcmdata -ldcmjpls -ldcmimage -ldcmjpeg 
> > -lofstd -lboost_filesystem -lboost_iostreams -lboost_locale -lboost_regex 
> > -lboost_thread -lpugixml -luuid -ljsoncpp -lpng -ljpeg -lz -lniftiio -lznz
> > /usr/bin/ld: cannot find -lpng: No such file or directory
> > /usr/bin/ld: cannot find -ljpeg: No such file or directory
> > /usr/bin/ld: cannot find -lpng: No such file or directory
> > /usr/bin/ld: cannot find -ljpeg: No such file or directory
> > collect2: error: ld returned 1 exit status
> > make[3]: *** [CMakeFiles/OrthancNeuro.dir/build.make:300: 
> > libOrthancNeuro.so.1.1] Error 1
> >
> >
> >
> > dcmtk (3.6.8-4) experimental; urgency=medium
> > ...
> >   * d/control: Reduce number of dependencies for -dev package
> >
> >
> > That's problematic when the CMake files require them for some target:
> >   /usr/lib/x86_64-linux-gnu/cmake/dcmtk/DCMTKTargets.cmake:  
> > INTERFACE_LINK_LIBRARIES 
> > "DCMTK::oflog;DCMTK::dcmdata;DCMTK::dcmimgle;/usr/lib/x86_64-linux-gnu/libtiff.so;/usr/lib/x86_64-linux-gnu/libjpeg.so;/usr/lib/x86_64-linux-gnu/libpng.so"
> >
> 
> Here is what I have no my side:
> 
> % grep tiff  /usr/lib/x86_64-linux-gnu/cmake/dcmtk/DCMTKTargets.cmake
> -> nothing
> 
> since I manually simplified it to:
> 
> [...]
>   INTERFACE_LINK_LIBRARIES "DCMTK::oflog;DCMTK::dcmdata;DCMTK::dcmimgle"
> [...]

I see your point that orthanc-neuro is the bigger problem here,
I am less sure how many of the 3 packages involved are considered buggy.

> Rebuilding orthanc-neuro with this new cmake file *still* triggers the
> exact same symptoms. I suspect it is dues to orthanc-neuro d/rules:
> 
> [...]
> "-DORTHANC_FRAMEWORK_ADDITIONAL_LIBRARIES=dcmdata [...] png jpeg
> [...]
> 
> Fundamentally I believe the real linking error should occur with the
> static libs:
> 
> % nm  /usr/lib/gcc/x86_64-linux-gnu/13/../../../../lib/libOrthancFramework.a
>...

Dependencies for static linking are a mess, we do not usually have them 
in place since static linking is not recommended in most cases.

orthanc-neuro builds and links with the shared library when I remove the 
-DORTHANC_FRAMEWORK_USE_SHARED:BOOL=OFF, is there any reason why this 
would not work?

> Thanks,

cu
Adrian

Bug#1070699: marked as done (gdb can not be started on testing)

[Debian Bug Tracking System]

Your message dated Mon, 8 Jul 2024 14:30:28 +0200
with message-id 
and subject line gdb: symbols fixed
has caused the Debian Bug report #1070699,
regarding gdb can not be started on testing
to be marked as done.

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

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


-- 
1070699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdb
Version: 13.2-1+b1
Severity: grave
Justification: renders package unusable

mmediately stops with the error:

gdb: symbol lookup error: /lib/x86_64-linux-gnu/libpython3.11.so.1.0: undefined 
symbol: XML_SetReparseDeferralEnabled

libpython3.11.so.1.0 is part of libpython3.11t64


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

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

Versions of packages gdb depends on:
ii  libbabeltrace1   1.5.11-3+b6
ii  libc62.38-7
ii  libdebuginfod1t640.191-1+b1
ii  libexpat12.6.2-1
ii  libgcc-s114-20240330-1
ii  libgmp10 2:6.3.0+dfsg-2+b1
ii  libipt2  2.0.6-1
ii  liblzma5 5.6.1+really5.4.5-1
ii  libmpfr6 4.2.1-1+b1
ii  libncursesw6 6.4+20240414-1
ii  libpython3.11t64 3.11.9-1
ii  libreadline8t64  8.2-4
ii  libsource-highlight4t64  3.1.9-4.3
ii  libstdc++6   14-20240330-1
ii  libtinfo66.4+20240414-1
ii  libxxhash0   0.8.2-2+b1
ii  libzstd1 1.5.5+dfsg2-2
ii  zlib1g   1:1.3.dfsg-3.1

Versions of packages gdb recommends:
ii  libc6-dbg [libc-dbg]  2.38-7

Versions of packages gdb suggests:
pn  gdb-doc
pn  gdbserver  

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 gdb/13.2-1+b2

In the meantime gdb was rebuilt for python3.12, and the problem
apparently has vanished.--- End Message ---

Bug#1075961: FTBFS: hep.c:985:41: error: implicit declaration of function ‘inet_ntop’

[Chris Hofstaedtler]

Source: kamailio
Version: 5.6.3-2
Severity: serious
Tags: ftbfs

kamailio currently FTBFS on s390x, but built there before.
The same problem can be observed on ppc64:

https://buildd.debian.org/status/fetch.php?pkg=kamailio=s390x=5.8.2-2=1720212227=0

hep.c: In function ‘hepv3_get_chunk’:
hep.c:985:41: error: implicit declaration of function ‘inet_ntop’ 
[-Werror=implicit-function-declaration]
  985 | inet_ntop(AF_INET, 
&(hg->hep_src_ip4->data), ipstr,
  | ^
gcc -fPIC -DPIC -pthread -DKSR_PTHREAD_MUTEX_SHARED -Wall -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DVERSION_NODATE   -DNAME='"kamailio"' 
-DVERSION='"5.8.2"' -DARCH='"s390x"' -DOS='linux_' -DOS_QUOTED='"linux"' 
-DCOMPILER='"gcc 13.3.0"' -D__CPU_s390x -D__OS_linux -DVERSIONVAL=5008002 
-DCFG_DIR='"/etc/kamailio/"' -DSHARE_DIR='"/usr/share/kamailio/"' 
-DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MMAP -DDNS_IP_HACK 
-DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE 
-DUSE_DNS_FAILOVER -DUSE_DST_BLOCKLIST -DUSE_NAPTR -DMEM_JOIN_FREE -DF_MALLOC 
-DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS 
-DSTATISTICS -DMALLOC_STATS -DUSE_SCTP -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN 
-DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL 
-DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_IP_MREQN 
-DUSE_RAW_SOCKS -DUSE_PTHREAD_MUTEX -DHAVE_EPOLL -DHAVE_SIGIO_RT 
-DSIGINFO64_WORKAROUND -DUSE_FUTEX -DHAVE_SELECT  -DMOD_NAME='"sipcapture"' 
-DMOD_NAMEID='sipcapture' -c sipcapture.c -o sipcapture.o -MMD -MP
In file included from ../../core/atomic_ops.h:180,
 from ../../core/locking.h:72,
 from ../../core/rpc.h:34,
 from ../../core/sr_module.h:36,
 from sipcapture.c:54:
...
make[4]: *** [../../Makefile.rules:100: hep.o] Error 1
...

Bug#1075917: marked as done (dcmtk: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 11:49:17 +
with message-id 
and subject line Bug#1075917: fixed in dcmtk 3.6.8-6
has caused the Debian Bug report #1075917,
regarding dcmtk: autopkgtest regression
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.)


-- 
1075917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dcmtk
Version: 3.6.8-5
Severity: serious
Tags: ftbfs

Issues preventing migration:
∙ ∙ autopkgtest for dcmtk/3.6.8-5: amd64: Regression or new test ♻ (reference 
♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new 
test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: 
Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ 
(reference ♻), riscv64: Failed (not a regression), s390x: Regression or new 
test ♻ (reference ♻)
...


...
 29s autopkgtest [03:11:53]: test run-unit-test: [---
 30s cp: cannot stat '/usr/share/libdcmtk17/dicom.dic': No such file or 
directory
 30s autopkgtest [03:11:54]: test run-unit-test: ---]
 30s autopkgtest [03:11:54]: test run-unit-test:  - - - - - - - - - - results - 
- - - - - - - - -
 30s run-unit-testFAIL non-zero exit status 1
...
--- End Message ---
--- Begin Message ---
Source: dcmtk
Source-Version: 3.6.8-6
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated dcmtk 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, 08 Jul 2024 13:31:04 +0200
Source: dcmtk
Architecture: source
Version: 3.6.8-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Mathieu Malaterre 
Closes: 1074483 1075917
Changes:
 dcmtk (3.6.8-6) unstable; urgency=medium
 .
   * d/t/run-unit-test: Fix unit-test for new release. Closes: #1075917
   * d/patches: Fixed possible overflows when allocating memory. Closes: 
#1074483
Checksums-Sha1:
 c6414c45739e82603f38bec31a4e6b4295189137 2410 dcmtk_3.6.8-6.dsc
 cb24d221b83165ff0a7a396d791bc45558e3fd63 56852 dcmtk_3.6.8-6.debian.tar.xz
 93a29df61cb84084514eef7dd1b5444ff8a59898 9040 dcmtk_3.6.8-6_source.buildinfo
Checksums-Sha256:
 76a67b74abcc6fffd0727e24a68a8a0def6a093de46567e384ae8d834b7d7a82 2410 
dcmtk_3.6.8-6.dsc
 b965dc6dc37e85bef66b03473f6ccac504f7c417370217ec8412ad636b3bfef1 56852 
dcmtk_3.6.8-6.debian.tar.xz
 220a00452e14836125f617cfe3bf2b5ff7b1a18e3ea4b763a3c49cc5a98750ad 9040 
dcmtk_3.6.8-6_source.buildinfo
Files:
 f6def198d0fb6f9ae6c422fd630bfdaa 2410 science optional dcmtk_3.6.8-6.dsc
 df03a54ddab175e7b5f7aeca8342b072 56852 science optional 
dcmtk_3.6.8-6.debian.tar.xz
 3796d0e1aca9d9b73b4bb280420effe9 9040 science optional 
dcmtk_3.6.8-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmaLzjwRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0VszA//cBIC39JDAQjDyzp3sK+0MxI2Fg29bUre
B0yhYDD90H3PdOzMhv9l/Pd4FfIHmd1xefdz7scgzhr5QC9uJDk0OIvT2Ndmb14d
nY+g3vVA1Nu+GGQef6d8JazG66cTHGxsxrzloo3x1mKaBI6CsbbkY/5eO+EHB7rq
FFwrdH9v/GDfSN1hRZSg8KQTpZRXGBEs/6xIShivbcSMMhJjVbEmjn6s65m9fGqr
uiRHmZ0X6AEsd3cF5ryHhXlUFXJUghBF9ctXLJkju15JZ1J4dVyI0diW7jSNfkZ9
IJf6byjiIJjcaIoJw/mj/dvVMKbOXd0SyH95lRdBZ7w481jl1JhkdpJDXWSc9ymZ
QrQ7NOSyGSuVuXlOfm0zZ7k/GXtVOPoOAIkHHO6Rh/c+r+lM5oguiVKc5N+3d/Aj
CFoEv/QnlcYlb270YLWL4yYZzCTYMcH0aXm1kIGG0n+cCLnxQBOnGL4j883+C33v
zC/b2zgrIJ2eRqc6qFHZsW/qSHxHuTHwnaAGoBBKz9J1D9BnP9DJFk/4CUCWPoGD
hYWT43vYJ2bs8ky1irLjAbBqiDTaQ4vY1UuFbr7kQiuAg9NVh7elUnVp5bZxLBYn
Pe+mpXI/UhtapyNcW5K5Zyi7oi/iWheLk+yQvsl1OyMCc9YjklvBVb2yircIhnEn
dvCRfBrb2ow=
=HDFv
-END PGP SIGNATURE-



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

Bug#1074483: marked as done (dcmtk: CVE-2024-27628)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 11:49:17 +
with message-id 
and subject line Bug#1074483: fixed in dcmtk 3.6.8-6
has caused the Debian Bug report #1074483,
regarding dcmtk: CVE-2024-27628
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.)


-- 
1074483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dcmtk
Version: 3.6.7-15
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://support.dcmtk.org/redmine/issues/1108
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 3.6.7-9~deb12u1

Hi,

The following vulnerability was published for dcmtk.

CVE-2024-27628[0]:
| Buffer Overflow vulnerability in DCMTK v.3.6.8 allows an attacker to
| execute arbitrary code via the EctEnhancedCT method component.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-27628
https://www.cve.org/CVERecord?id=CVE-2024-27628
[1] https://support.dcmtk.org/redmine/issues/1108
[2] 
https://github.com/DCMTK/dcmtk/commit/ec52e99e1e33fc39810560421c0833b02da567b3

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: dcmtk
Source-Version: 3.6.8-6
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated dcmtk 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, 08 Jul 2024 13:31:04 +0200
Source: dcmtk
Architecture: source
Version: 3.6.8-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Mathieu Malaterre 
Closes: 1074483 1075917
Changes:
 dcmtk (3.6.8-6) unstable; urgency=medium
 .
   * d/t/run-unit-test: Fix unit-test for new release. Closes: #1075917
   * d/patches: Fixed possible overflows when allocating memory. Closes: 
#1074483
Checksums-Sha1:
 c6414c45739e82603f38bec31a4e6b4295189137 2410 dcmtk_3.6.8-6.dsc
 cb24d221b83165ff0a7a396d791bc45558e3fd63 56852 dcmtk_3.6.8-6.debian.tar.xz
 93a29df61cb84084514eef7dd1b5444ff8a59898 9040 dcmtk_3.6.8-6_source.buildinfo
Checksums-Sha256:
 76a67b74abcc6fffd0727e24a68a8a0def6a093de46567e384ae8d834b7d7a82 2410 
dcmtk_3.6.8-6.dsc
 b965dc6dc37e85bef66b03473f6ccac504f7c417370217ec8412ad636b3bfef1 56852 
dcmtk_3.6.8-6.debian.tar.xz
 220a00452e14836125f617cfe3bf2b5ff7b1a18e3ea4b763a3c49cc5a98750ad 9040 
dcmtk_3.6.8-6_source.buildinfo
Files:
 f6def198d0fb6f9ae6c422fd630bfdaa 2410 science optional dcmtk_3.6.8-6.dsc
 df03a54ddab175e7b5f7aeca8342b072 56852 science optional 
dcmtk_3.6.8-6.debian.tar.xz
 3796d0e1aca9d9b73b4bb280420effe9 9040 science optional 
dcmtk_3.6.8-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmaLzjwRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0VszA//cBIC39JDAQjDyzp3sK+0MxI2Fg29bUre
B0yhYDD90H3PdOzMhv9l/Pd4FfIHmd1xefdz7scgzhr5QC9uJDk0OIvT2Ndmb14d
nY+g3vVA1Nu+GGQef6d8JazG66cTHGxsxrzloo3x1mKaBI6CsbbkY/5eO+EHB7rq
FFwrdH9v/GDfSN1hRZSg8KQTpZRXGBEs/6xIShivbcSMMhJjVbEmjn6s65m9fGqr
uiRHmZ0X6AEsd3cF5ryHhXlUFXJUghBF9ctXLJkju15JZ1J4dVyI0diW7jSNfkZ9
IJf6byjiIJjcaIoJw/mj/dvVMKbOXd0SyH95lRdBZ7w481jl1JhkdpJDXWSc9ymZ
QrQ7NOSyGSuVuXlOfm0zZ7k/GXtVOPoOAIkHHO6Rh/c+r+lM5oguiVKc5N+3d/Aj
CFoEv/QnlcYlb270YLWL4yYZzCTYMcH0aXm1kIGG0n+cCLnxQBOnGL4j883+C33v
zC/b2zgrIJ2eRqc6qFHZsW/qSHxHuTHwnaAGoBBKz9J1D9BnP9DJFk/4CUCWPoGD
hYWT43vYJ2bs8ky1irLjAbBqiDTaQ4vY1UuFbr7kQiuAg9NVh7elUnVp5bZxLBYn
Pe+mpXI/UhtapyNcW5K5Zyi7oi/iWheLk+yQvsl1OyMCc9YjklvBVb2yircIhnEn
dvCRfBrb2ow=
=HDFv
-END PGP SIGNATURE-



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

Bug#1075939: marked as done (python3-pyinotify missing runtime dependency)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 11:37:39 +
with message-id 
and subject line Bug#1075939: fixed in pyinotify 0.9.6-3
has caused the Debian Bug report #1075939,
regarding python3-pyinotify missing runtime dependency
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.)


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

Package: python3-pyinotify
Version: 0.9.6-2

After the python 3.12 upgrade on trixie, python3-pyinotify became unusable due to a missing asyncore module. libpython3.12-stdlib 
moved it to /usr/lib/python3.12/test/support/asyncore.py, while the actual module is shipped via python3-pyasyncore.


>>> import pyinotify
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pyinotify.py", line 71, in 
import asyncore
ModuleNotFoundError: No module named 'asyncore'
--- End Message ---
--- Begin Message ---
Source: pyinotify
Source-Version: 0.9.6-3
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated pyinotify 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, 08 Jul 2024 12:58:39 +0200
Source: pyinotify
Architecture: source
Version: 0.9.6-3
Distribution: unstable
Urgency: medium
Maintainer: Mikhail Gusarov 
Changed-By: Bastian Germann 
Closes: 1040102 1075811 1075939
Changes:
 pyinotify (0.9.6-3) unstable; urgency=medium
 .
   * Team upload.
   * Trim trailing whitespace.
   * Bump debhelper from old 12 to 13.
   * Add pyasyncore to Depends for support in Python >= 3.12.
 (Closes: #1075811, #1040102, #1075939)
Checksums-Sha1:
 d4fcbb946416adcdd5b99bc63a215aed8bb84099 1887 pyinotify_0.9.6-3.dsc
 340b82db45fc9a2ca07bfd1ad418fa72070b3713 5608 pyinotify_0.9.6-3.debian.tar.xz
 bd1727603045976e21be20dd16170dbfc5dacd57 6378 
pyinotify_0.9.6-3_source.buildinfo
Checksums-Sha256:
 bde7d75221179c06741810fbc2854ea1c6f9c85319fd767d142e6e27a601c818 1887 
pyinotify_0.9.6-3.dsc
 640685e0fe64b48d27d9f12e40a52fea0c2211141b4ac8870ca8ce6d36cb6056 5608 
pyinotify_0.9.6-3.debian.tar.xz
 201a7c198aea3b76bd1d00a70b905d8755c0cff1fdd111caada4b730b19c972f 6378 
pyinotify_0.9.6-3_source.buildinfo
Files:
 bbf27b864f6a80dcac496108a3b057b4 1887 python optional pyinotify_0.9.6-3.dsc
 4cb3184066a31576d9108dd2e4e4f71c 5608 python optional 
pyinotify_0.9.6-3.debian.tar.xz
 4aba84e617af3e81c66e499828416a4d 6378 python optional 
pyinotify_0.9.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmaLx6cQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFOMKC/4y85q2hAEtCKMMJ9ZU39aQz6Nv8oDgo3WQ
SkGyvD5JFeiJv2CLvN4+ToHDHPoyXI4CPsZX9asGw7h+yM4q0qeu4kUjfD+YWGDU
UYcLAqIMtBWfx7leFhIBcI+oUhPJ777+fyIqEpgGb5IsZsHxgvkarU7482XhSekx
QZx0mQ2mJBo5zkPNohRAdFSiIItDiMf1KM+HwG3R7X1rroYrTZLZ/Ca+8uIfSawj
PWy39OX3OrIKQVqsdUxh/M93Viq/eamleqwzXnC+uEaRU8RrD3TWevM/80cdWf2i
hkXmEfTczQsEipnuiYNsr4nVi7eLkx6F+eqpKmhcBMCnAw/u7ASRSdFh9DpK4K2w
6+atdHSRZoFiv+Mw0I1smk05KH2qCDJDAFDbXYHOO2PFAyDVAJ5K2PGkznng5K15
NVUu+P34TbPZ0JR8EPv1bfO5j7y4+HE1TfNHhZrU1GKSLPLxjjSB5P2bTn2LWt4u
S3xBbYwkmKQF0bfPDB5cBd1M4XDZy4k=
=5jE8
-END PGP SIGNATURE-



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

Bug#1075811: marked as done (autokey-qt can be installed but will nor run)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 11:37:39 +
with message-id 
and subject line Bug#1075811: fixed in pyinotify 0.9.6-3
has caused the Debian Bug report #1075811,
regarding autokey-qt can be installed but will nor run
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.)


-- 
1075811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: autokey-qt
Version: 0.95.10-2.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Autokey is loaded on login, but not always used. Today I found it did
not function, and had not been loaded. I believe it has been used
within the last three weeks.

Installing autokey-qt after purging autokey-qt and autokey-common
appears to work normally, no errors are shown.
Running it from the GUI menu does nothing, running from the terminal
produces these python errors:

joe@jrenewsid:~$ autokey-qt
Traceback (most recent call last):
  File "/usr/bin/autokey-qt", line 33, in 
sys.exit(load_entry_point('autokey==0.95.10', 'console_scripts',
'autokey- qt')())
^
  File "/usr/bin/autokey-qt", line 25, in importlib_load_entry_point
return next(matches).load()
   
  File "/usr/lib/python3.12/importlib/metadata/__init__.py", line 205,
in load module = import_module(match.group('module'))
 
  File "/usr/lib/python3.12/importlib/__init__.py", line 90, in
import_module return _bootstrap._gcd_import(name[level:], package,
level) 
  File "", line 1387, in _gcd_import
  File "", line 1360, in _find_and_load
  File "", line 1331, in
_find_and_load_unlocked File "", line 935,
in _load_unlocked File "", line
995, in exec_module File "", line 488, in
_call_with_frames_removed File
"/usr/lib/python3/dist-packages/autokey/qtui/__main__.py", line 23, in
 from autokey.qtapp import Application
  File "/usr/lib/python3/dist-packages/autokey/qtapp.py", line 37, in
 from autokey import service, monitor
  File "/usr/lib/python3/dist-packages/autokey/monitor.py", line 24, in

from pyinotify import WatchManager, Notifier, EventsCodes,
ProcessEvent File "/usr/lib/python3/dist-packages/pyinotify.py", line
71, in  import asyncore
ModuleNotFoundError: No module named 'asyncore'



It appears the asyncore module has been deprecated and removed from
python. I have tried autokey-gtk but it also uses asyncore.
I can find no Debian bug reports for autokey-qt, possibly there are not
many users.

Is there a workaround?


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

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

Versions of packages autokey-qt depends on:
ii  autokey-common   0.95.10-2.1
ii  python3  3.12.2-1
ii  python3-pyqt55.15.10+dfsg-1+b3
ii  python3-pyqt5.qsci   2.14.1+dfsg-1+b3
ii  python3-pyqt5.qtsvg  5.15.10+dfsg-1+b3

autokey-qt recommends no packages.

Versions of packages autokey-qt suggests:
pn  gnome-shell-extension-appindicator  

-- no debconf information

Best regards,
Joe
--- End Message ---
--- Begin Message ---
Source: pyinotify
Source-Version: 0.9.6-3
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated pyinotify 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, 08 Jul 2024 12:58:39 +0200
Source: pyinotify
Architecture: source
Version: 0.9.6-3
Distribution: unstable
Urgency: medium
Maintainer: Mikhail Gusarov 
Changed-By: Bastian Germann 
Closes: 1040102 1075811 

Bug#1074577: marked as done (gnat ftbfs with glibc from experimental)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 11:34:48 +
with message-id 
and subject line Bug#1074577: fixed in gcc-13 13.3.0-2
has caused the Debian Bug report #1074577,
regarding gnat ftbfs with glibc from experimental
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.)


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

Package: gnat-13
Version: 13.3.0-1
Severity: serious
Tags: sid trixie

gnat ftbfs with glibc 2.39 from experimental, failing to link.

this patch set doesn't work anymore with the glibc 2.39 branch on 64bit 
architectures.  Linking fails with


/<>/build/gcc/ada/rts/s-tpopmo.adb:62:(.text+0xcd): 
undefined reference to `__clock_gettime64'

and other __*64 functions.
Complete build logs at
https://launchpad.net/ubuntu/+source/gcc-14/14.1.0-3ubuntu2

the glibc change causing this is
https://sourceware.org/git/?p=glibc.git;a=commit;h=dd535f4f19ef2b5c367a362af445ecadcf45401e


Not applying the 0009-Ada-*.diff patch on the 64bit archs works around 
the issue.  However dropping the 0009-Ada-* patches also changes the 
gnat-14-XXX provides, forcing just another gnat transition.


Also please forward the Ada patches upstream, carrying these locally 
isn't very robust.



see also
https://bugs.launchpad.net/ubuntu/+source/gcc-13/+bug/2071605
--- End Message ---
--- Begin Message ---
Source: gcc-13
Source-Version: 13.3.0-2
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-13 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, 08 Jul 2024 12:53:33 +0200
Source: gcc-13
Architecture: source
Version: 13.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 1055711 1074577
Changes:
 gcc-13 (13.3.0-2) unstable; urgency=medium
 .
   * Update to git 20240707 from the gcc-13 branch.
 - Fix PR target/106069 (PPC), PR target/115355 (PPC),
   PR target/103100 (AArch64), PR target/115618 (AArch64),
   PR target/114846 (PPC), PR driver/115440, PR fortran/83865,
   PR libstdc++/115668, PR libstdc++/115454, PR libstdc++/115575,
   PR target/87376 (AVR), PR target/115475 (AArch64),
   PR target/115457 (AArch64), PR target/115691 (PARISC),
   PR target/98762 (AVR), PR target/106069 (PPC), PR target/115355 (PPC),
  PR target/88236 (AVR), PR target/115726 (AVR).
   * Disable running the tests on the Ubuntu arm64 buildds (times out).
   * Starting with Ubuntu 24.10, stop building s390x multilibs.
   * d/p/0006-Ada-select-64-bits-time-functions-from-GNU-libc-when-.diff
 Adjust for the new glibc behaviour of defining __USE_TIME_BITS64 also
 on native 64-bits platforms (Simon Chopin). Closes: #1074577. LP: #2071605.
   * Pass --package-metadata on distros with supporting linkers (starting
 with Debian trixie and Ubuntu noble).
 The package metadata is constructed from the environment variables
 DEB_BUILD_OS_RELEASE_ID, DEB_SOURCE, DEB_VERSION and DEB_HOST_ARCH.
 Setting NO_PKG_METADATA=1 disables the generation of the package metadata.
   * Build target libraries with -mbranch-protection=standard to enable PAC/BTI
 support on arm64 (Emanuele Rocca). Closes: #1055711.
   * Build target libraries with -fno-omit-frame-pointer, when enabled in
 dpkg-buildflags.
Checksums-Sha1:
 d594a7aae4e90120711f8800a87aa1cedd2d8b3b 39089 gcc-13_13.3.0-2.dsc
 ca64967f426f9516150de10bcb9e01f5d9230271 617836 gcc-13_13.3.0-2.debian.tar.xz
 5a30235538bc9dda118e67553c9274622db0cd21 8385 gcc-13_13.3.0-2_source.buildinfo
Checksums-Sha256:
 9b57c87d825cf0164220565dbfe6a13a4eff906aa6524a14c57e88c05cc816d7 39089 
gcc-13_13.3.0-2.dsc
 7c297608df8bc0b077ebdb3d493490cbcb317327a346dedd3ee547ccc3874b97 617836 
gcc-13_13.3.0-2.debian.tar.xz
 d51e07851230d43133d0dd3ba02d61ed48cf61c11db60595803aef4da5c73791 8385 
gcc-13_13.3.0-2_source.buildinfo
Files:
 

Bug#1040102: marked as done (pyinotify: deprecation of Python libraries asyncore and asynchat)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 11:37:39 +
with message-id 
and subject line Bug#1040102: fixed in pyinotify 0.9.6-3
has caused the Debian Bug report #1040102,
regarding pyinotify: deprecation of Python libraries asyncore and asynchat
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.)


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

Source: pyinotify
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: asyncore-asynchat-deprecation

Dear maintainer(s),

In Python 3.6, asyncore and asynchat have been formally marked as 
deprecated. Code that imports these libraries will no longer work from 
Python 3.12, which is currently in Trixie.


Since pyinotify uses either of these Python libraries, please prepare 
for this removal and migrate away from them.


See this link for more details: 
https://peps.python.org/pep-0594/#deprecated-modules


Cheers,

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pyinotify
Source-Version: 0.9.6-3
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated pyinotify 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, 08 Jul 2024 12:58:39 +0200
Source: pyinotify
Architecture: source
Version: 0.9.6-3
Distribution: unstable
Urgency: medium
Maintainer: Mikhail Gusarov 
Changed-By: Bastian Germann 
Closes: 1040102 1075811 1075939
Changes:
 pyinotify (0.9.6-3) unstable; urgency=medium
 .
   * Team upload.
   * Trim trailing whitespace.
   * Bump debhelper from old 12 to 13.
   * Add pyasyncore to Depends for support in Python >= 3.12.
 (Closes: #1075811, #1040102, #1075939)
Checksums-Sha1:
 d4fcbb946416adcdd5b99bc63a215aed8bb84099 1887 pyinotify_0.9.6-3.dsc
 340b82db45fc9a2ca07bfd1ad418fa72070b3713 5608 pyinotify_0.9.6-3.debian.tar.xz
 bd1727603045976e21be20dd16170dbfc5dacd57 6378 
pyinotify_0.9.6-3_source.buildinfo
Checksums-Sha256:
 bde7d75221179c06741810fbc2854ea1c6f9c85319fd767d142e6e27a601c818 1887 
pyinotify_0.9.6-3.dsc
 640685e0fe64b48d27d9f12e40a52fea0c2211141b4ac8870ca8ce6d36cb6056 5608 
pyinotify_0.9.6-3.debian.tar.xz
 201a7c198aea3b76bd1d00a70b905d8755c0cff1fdd111caada4b730b19c972f 6378 
pyinotify_0.9.6-3_source.buildinfo
Files:
 bbf27b864f6a80dcac496108a3b057b4 1887 python optional pyinotify_0.9.6-3.dsc
 4cb3184066a31576d9108dd2e4e4f71c 5608 python optional 
pyinotify_0.9.6-3.debian.tar.xz
 4aba84e617af3e81c66e499828416a4d 6378 python optional 
pyinotify_0.9.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmaLx6cQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFOMKC/4y85q2hAEtCKMMJ9ZU39aQz6Nv8oDgo3WQ
SkGyvD5JFeiJv2CLvN4+ToHDHPoyXI4CPsZX9asGw7h+yM4q0qeu4kUjfD+YWGDU
UYcLAqIMtBWfx7leFhIBcI+oUhPJ777+fyIqEpgGb5IsZsHxgvkarU7482XhSekx
QZx0mQ2mJBo5zkPNohRAdFSiIItDiMf1KM+HwG3R7X1rroYrTZLZ/Ca+8uIfSawj
PWy39OX3OrIKQVqsdUxh/M93Viq/eamleqwzXnC+uEaRU8RrD3TWevM/80cdWf2i
hkXmEfTczQsEipnuiYNsr4nVi7eLkx6F+eqpKmhcBMCnAw/u7ASRSdFh9DpK4K2w
6+atdHSRZoFiv+Mw0I1smk05KH2qCDJDAFDbXYHOO2PFAyDVAJ5K2PGkznng5K15
NVUu+P34TbPZ0JR8EPv1bfO5j7y4+HE1TfNHhZrU1GKSLPLxjjSB5P2bTn2LWt4u
S3xBbYwkmKQF0bfPDB5cBd1M4XDZy4k=
=5jE8
-END PGP SIGNATURE-



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

Bug#1028172: marked as done (libmpich-dev lacks dependencies required by its pkgconfig file)

[Debian Bug Tracking System]

Your message dated Mon, 08 Jul 2024 11:36:17 +
with message-id 
and subject line Bug#1028172: fixed in mpich 4.2.0-7
has caused the Debian Bug report #1028172,
regarding libmpich-dev lacks dependencies required by its pkgconfig file
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.)


-- 
1028172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiledarray
Version: 1.0.0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar

Hi Michael,

tiledarray's build-dependencies are now satisfied in unstable (bug
#1014548), but it fails to build from source :)

[...]
CMake Error at /usr/share/cmake-3.25/Modules/CMakeTestCXXCompiler.cmake:63 
(message):
  The C++ compiler

"/usr/bin/c++"

  is not able to compile a simple test program.

  It fails with the following output:

Change Dir: 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98

Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_d2ec9/fast && 
gmake[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
/usr/bin/gmake  -f CMakeFiles/cmTC_d2ec9.dir/build.make 
CMakeFiles/cmTC_d2ec9.dir/build
gmake[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
Building CXX object CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o
/usr/bin/c++   -I/usr/include/x86_64-linux-gnu/mpich  -o 
CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o -c 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98/testCXXCompiler.cxx
Linking CXX executable cmTC_d2ec9
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_d2ec9.dir/link.txt 
--verbose=1
/usr/bin/c++ -I/usr/include/x86_64-linux-gnu/mpich  -lmpich -lpthread 
-lhwloc -lucp -lucs -lrt  CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o -o 
cmTC_d2ec9 
/usr/bin/ld: cannot find -lhwloc: No such file or directory
/usr/bin/ld: cannot find -lucp: No such file or directory
/usr/bin/ld: cannot find -lucs: No such file or directory
collect2: error: ld returned 1 exit status
gmake[3]: *** [CMakeFiles/cmTC_d2ec9.dir/build.make:99: cmTC_d2ec9] Error 1
gmake[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
gmake[2]: *** [Makefile:127: cmTC_d2ec9/fast] Error 2
gmake[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
[...]

  
(https://buildd.debian.org/status/fetch.php?pkg=tiledarray=amd64=1.0.0-1=1673126398=0)


Possibly an issue in a build-dependency, I see that these library options
come from the output of `pkg-config --libs-only-l mpi` but libmpich-dev
apparently doesn't depend on the packages providing the libs in its output.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 4.2.0-7
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated mpich 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, 08 Jul 2024 11:43:54 +0100
Source: mpich
Architecture: source
Version: 4.2.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 1028172
Changes:
 mpich (4.2.0-7) unstable; urgency=medium
 .
   * Add patch that was accidentally dropped:
  Add Deps to libmpich-dev needed for pkg-config. Closes: #1028172
Checksums-Sha1:
 7e04561fc9099848e4a224def6185e93e835fa52 2763 mpich_4.2.0-7.dsc
 6e97d5a85ee9fc8bd624d341730be2659ab5577c 350328 mpich_4.2.0-7.debian.tar.xz

Bug#1075917: marked as pending in dcmtk

[Mathieu Malaterre]

Control: tag -1 pending

Hello,

Bug #1075917 in dcmtk 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/dcmtk/-/commit/df880c7da1ec0b8f52e3e5e89236e55a0654c099


d/t/run-unit-test: Fix unit-test for new release. Closes: #1075917


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1075917

Processed: Bug#1075917 marked as pending in dcmtk

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1075917 [src:dcmtk] dcmtk: autopkgtest regression
Added tag(s) pending.

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

Processed: Bug#1074483 marked as pending in dcmtk

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1074483 [src:dcmtk] dcmtk: CVE-2024-27628
Added tag(s) pending.

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

Bug#1074483: marked as pending in dcmtk

[Mathieu Malaterre]

Control: tag -1 pending

Hello,

Bug #1074483 in dcmtk 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/dcmtk/-/commit/71a4fcfd112d8be5d0b61e9c1509d255c3ac8e24


d/patches: Fixed possible overflows when allocating memory. Closes: #1074483


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1074483

Processed: Bug#1073449 marked as pending in python-keystoneauth1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073449 [src:python-keystoneauth1] python-keystoneauth1: FTBFS: 
keystoneauth1.exceptions.connection.UnknownConnectionError: Unexpected 
exception for http://keystoneauth-betamax.test/v2.0/tokens: ('Connection 
broken: IncompleteRead(780 bytes read, 1904 more expected)', IncompleteRead(780 
bytes read, 1904 more expected))
Added tag(s) pending.

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

Bug#1075959: websockify: build-depends on python3-all-dev but doesn't build extensions

[Graham Inggs]

Source: websockify
Version: 0.10.0+dfsg1-6
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

websockify build-depends on python3-all-dev but doesn't build
extensions for all supported Python versions.  This caused it to
appear on the python3.12-default tracker [1] and be binNMU'd for the
transition.

Being rebuilt for this phase of the transition to Python 3.12 just
means websockify will not need another rebuild for the next phase
(python3.12-only), however this binNMU resulted in a FTBFS on riscv64
(#1075849) and websockify's subsequent removal from testing.

Regards
Graham


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

Bug#1073449: marked as pending in python-keystoneauth1

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/libs/python-keystoneauth1/-/commit/bae8258152b315494f30148e561679d61ea92638


Blacklist test_keystoneauth_betamax_fixture() (Closes: #1073449).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073449

Bug#1071884: marked as done (r-bioc-rcwl: FTBFS: unsatisfiable build-dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 8 Jul 2024 12:06:19 +0200
with message-id <9d58ff64-9f8f-47a6-a627-9e5240208...@debian.org>
and subject line Re: r-bioc-rcwl: FTBFS: unsatisfiable build-dependencies
has caused the Debian Bug report #1071884,
regarding r-bioc-rcwl: FTBFS: unsatisfiable build-dependencies
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.)


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

Package: src:r-bioc-rcwl
Version: 1.18.0+ds-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
Install main build dependencies (apt-based resolver)


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sbuild-build-depends-main-dummy : Depends: r-cran-diagrammer but it is not 
installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed
Not removing build depends: cloned chroot in use



The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

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

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

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---

Version: 1.18.0+ds-2

r-cran-diagrammer is in the archive now



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: closing 1073326

[Debian Bug Tracking System]

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

> close 1073326 0.16.4-1
Bug #1073326 [src:obconf-qt] obconf-qt: FTBFS: obconf-qt.cpp:233:36: error: 
invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to 
‘xmlErrorPtr’ {aka ‘_xmlError*’} [-fpermissive]
Marked as fixed in versions obconf-qt/0.16.4-1.
Bug #1073326 [src:obconf-qt] obconf-qt: FTBFS: obconf-qt.cpp:233:36: error: 
invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to 
‘xmlErrorPtr’ {aka ‘_xmlError*’} [-fpermissive]
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1074483: dcmtk: CVE-2024-27628

[Adrian Bunk]

Control: tags -1 patch

On Sat, Jun 29, 2024 at 04:44:43PM +0200, Salvatore Bonaccorso wrote:
>...
> The following vulnerability was published for dcmtk.
> 
> CVE-2024-27628[0]:
> | Buffer Overflow vulnerability in DCMTK v.3.6.8 allows an attacker to
> | execute arbitrary code via the EctEnhancedCT method component.
> 
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2024-27628
> https://www.cve.org/CVERecord?id=CVE-2024-27628
> [1] https://support.dcmtk.org/redmine/issues/1108
> [2] 
> https://github.com/DCMTK/dcmtk/commit/ec52e99e1e33fc39810560421c0833b02da567b3
>...

Attached is this patch for 3.6.8 (no conflicts during rebasing).

The new test fails without the fix and passes with the fix,
no regressions during the build test.

The actual code fix is pretty small (and not ABI breaking),
most of the patch is test code.

cu
Adrian
>From 855ee5eacad12b4ef39d36a78c9c24d038c4a231 Mon Sep 17 00:00:00 2001
From: Michael Onken 
Date: Tue, 20 Feb 2024 10:50:28 +0100
Subject: Fixed possible overflows when allocating memory.

Thanks to GitHub user "bananabr" (Daniel Berredo) for the report and
suggested patch.
---
 dcmect/libsrc/enhanced_ct.cc |  14 +-
 dcmect/tests/CMakeLists.txt  |   1 +
 dcmect/tests/Makefile.dep| 151 +++
 dcmect/tests/Makefile.in |   4 +-
 dcmect/tests/t_overflow.cc   | 362 +++
 dcmect/tests/tests.cc|   3 +-
 6 files changed, 531 insertions(+), 4 deletions(-)
 create mode 100644 dcmect/tests/t_overflow.cc

diff --git a/dcmect/libsrc/enhanced_ct.cc b/dcmect/libsrc/enhanced_ct.cc
index 619374290..47d6335f0 100644
--- a/dcmect/libsrc/enhanced_ct.cc
+++ b/dcmect/libsrc/enhanced_ct.cc
@@ -24,6 +24,7 @@
 #include "dcmtk/dcmect/types.h"
 #include "dcmtk/dcmfg/concatenationcreator.h"
 #include "dcmtk/dcmfg/concatenationloader.h"
+#include "dcmtk/dcmfg/fgtypes.h"
 #include "dcmtk/dcmiod/iodutil.h"
 #include "dcmtk/dcmiod/modimagepixel.h"
 
@@ -100,8 +101,19 @@ struct EctEnhancedCT::WriteVisitor
 m_CT.getRows(rows);
 m_CT.getColumns(cols);
 const size_t numFrames  = m_CT.m_Frames.size();
+if (numFrames > 2147483647)
+{
+DCMECT_ERROR("More than 2147483647 frames provided");
+return FG_EC_PixelDataTooLarge;
+}
+const size_t numPixelsFrame = OFstatic_cast(size_t, rows) * OFstatic_cast(size_t, cols);
 const size_t numBytesFrame  = m_CT.m_Frames[0]->length;
-const size_t numPixelsFrame = rows * cols;
+if (numBytesFrame != numPixelsFrame * 2)
+{
+DCMECT_ERROR("Invalid number of bytes per frame: Expected " << numPixelsFrame * 2 << " but got "
+  << numBytesFrame << " frame pixel data");
+return ECT_InvalidPixelInfo;
+}
 // Creates the correct pixel data element, based on the image pixel module used.
 DcmPixelData* pixData = new DcmPixelData(DCM_PixelData);
 OFCondition result;
diff --git a/dcmect/tests/CMakeLists.txt b/dcmect/tests/CMakeLists.txt
index 5d66b1145..032553414 100644
--- a/dcmect/tests/CMakeLists.txt
+++ b/dcmect/tests/CMakeLists.txt
@@ -2,6 +2,7 @@
 DCMTK_ADD_EXECUTABLE(dcmect_tests
   tests.cc
   t_huge_concat.cc
+  t_overflow.cc
   t_roundtrip.cc
 )
 
diff --git a/dcmect/tests/Makefile.dep b/dcmect/tests/Makefile.dep
index 9d26f581c..dfb50b812 100644
--- a/dcmect/tests/Makefile.dep
+++ b/dcmect/tests/Makefile.dep
@@ -192,6 +192,157 @@ t_huge_concat.o: t_huge_concat.cc \
  ../../dcmfg/include/dcmtk/dcmfg/fgrealworldvaluemapping.h \
  ../../dcmiod/include/dcmtk/dcmiod/iodcontentitemmacro.h \
  ../../dcmfg/include/dcmtk/dcmfg/fgtemporalposition.h
+t_overflow.o: t_overflow.cc ../../config/include/dcmtk/config/osconfig.h \
+ ../include/dcmtk/dcmect/enhanced_ct.h ../include/dcmtk/dcmect/def.h \
+ ../../ofstd/include/dcmtk/ofstd/ofexport.h \
+ ../include/dcmtk/dcmect/types.h ../../oflog/include/dcmtk/oflog/oflog.h \
+ ../../oflog/include/dcmtk/oflog/logger.h \
+ ../../oflog/include/dcmtk/oflog/config.h \
+ ../../ofstd/include/dcmtk/ofstd/ofdefine.h \
+ ../../ofstd/include/dcmtk/ofstd/ofcast.h \
+ ../../ofstd/include/dcmtk/ofstd/ofstdinc.h \
+ ../../oflog/include/dcmtk/oflog/config/defines.h \
+ ../../oflog/include/dcmtk/oflog/helpers/threadcf.h \
+ ../../oflog/include/dcmtk/oflog/loglevel.h \
+ ../../ofstd/include/dcmtk/ofstd/ofvector.h \
+ ../../ofstd/include/dcmtk/ofstd/oftypes.h \
+ ../../ofstd/include/dcmtk/ofstd/ofstream.h \
+ ../../oflog/include/dcmtk/oflog/tstring.h \
+ ../../ofstd/include/dcmtk/ofstd/ofstring.h \
+ ../../oflog/include/dcmtk/oflog/tchar.h \
+ ../../oflog/include/dcmtk/oflog/spi/apndatch.h \
+ ../../oflog/include/dcmtk/oflog/appender.h \
+ ../../ofstd/include/dcmtk/ofstd/ofmem.h \
+ ../../ofstd/include/dcmtk/ofstd/ofutil.h \
+ 

Processed: Re: Bug#1074483: dcmtk: CVE-2024-27628

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1074483 [src:dcmtk] dcmtk: CVE-2024-27628
Added tag(s) patch.

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

Processed: libmpich-dev lost dependencies needed for pkg-config

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.2.0-6
Bug #1028172 {Done: Bastian Germann } [libmpich-dev] 
libmpich-dev lacks dependencies required by its pkgconfig file
Marked as found in versions mpich/4.2.0-6 and reopened.
> affects -1 src:hpcc
Bug #1028172 [libmpich-dev] libmpich-dev lacks dependencies required by its 
pkgconfig file
Added indication that 1028172 affects src:hpcc

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

Bug#1028172: libmpich-dev lost dependencies needed for pkg-config

[Adrian Bunk]

Control: found -1 4.2.0-6
Control: affects -1 src:hpcc

On Tue, Jan 10, 2023 at 12:39:07PM +, Debian Bug Tracking System wrote:
>...
> Maintainer: Debian Science Maintainers 
> 
> Changed-By: Alastair McKinstry 
> Closes: 1028172
> Changes:
>  mpich (4.0.2-3) unstable; urgency=medium
>  .
>* Standards-Version: 4.6.1
>* Add Deps to libmpich-dev needed for pkg-config. Closes: #1028172
>...

This change was apparently lost at some point:

Package: libmpich-dev
Version: 4.2.0-6
Depends: gfortran | fortran-compiler, g++, libmpich12 (= 4.2.0-6), gfortran-13 
| gfortran-mod-15, mpich (= 4.2.0-6)


cu
Adrian

Processed: staticsite: depends on python3-pyinotify which seems dead upstream

[Debian Bug Tracking System]

Processing control commands:

> block 1004387 by -1
Bug #1004387 [python3-pyinotify] Upstream seems abandoned
1004387 was blocked by: 1075953 1075951 1075952 1075957 1075947 1075950 1075954 
1075949 1075948 1075955 1075956
1004387 was not blocking any bugs.
Added blocking bug(s) of 1004387: 1075958
> affects 1075939 + staticsite
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Added indication that 1075939 affects staticsite

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

Processed: python-oslo.log: depends on python3-pyinotify which seems dead upstream

[Debian Bug Tracking System]

Processing control commands:

> block 1004387 by -1
Bug #1004387 [python3-pyinotify] Upstream seems abandoned
1004387 was blocked by: 1075948 1075952 1075953 1075950 1075951 1075956 1075954 
1075955 1075947 1075949
1004387 was not blocking any bugs.
Added blocking bug(s) of 1004387: 1075957
> affects 1075939 + python3-oslo.log
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Added indication that 1075939 affects python3-oslo.log

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

Processed: poezio: depends on python3-pyinotify which seems dead upstream

[Debian Bug Tracking System]

Processing control commands:

> block 1004387 by -1
Bug #1004387 [python3-pyinotify] Upstream seems abandoned
1004387 was blocked by: 1075952 1075948 1075955 1075949 1075953 1075951 1075947 
1075954 1075950
1004387 was not blocking any bugs.
Added blocking bug(s) of 1004387: 1075956
> affects 1075939 + poezio
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Added indication that 1075939 affects poezio

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

Processed: python3-opensnitch-ui: depends on python3-pyinotify which seems dead upstream

[Debian Bug Tracking System]

Processing control commands:

> block 1004387 by -1
Bug #1004387 [python3-pyinotify] Upstream seems abandoned
1004387 was blocked by: 1075950 1075947 1075949 1075948 1075952 1075953 1075954 
1075951
1004387 was not blocking any bugs.
Added blocking bug(s) of 1004387: 1075955
> affects 1075939 + python3-opensnitch-ui
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Added indication that 1075939 affects python3-opensnitch-ui

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

Processed: mate-hud: depends on python3-pyinotify which seems dead upstream

[Debian Bug Tracking System]

Processing control commands:

> block 1004387 by -1
Bug #1004387 [python3-pyinotify] Upstream seems abandoned
1004387 was blocked by: 1075952 1075953 1075948 1075951 1075949 1075947 1075950
1004387 was not blocking any bugs.
Added blocking bug(s) of 1004387: 1075954
> affects 1075939 + mate-hud
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Added indication that 1075939 affects mate-hud

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

Processed: lintian-brush: depends on python3-pyinotify which seems dead upstream

[Debian Bug Tracking System]

Processing control commands:

> block 1004387 by -1
Bug #1004387 [python3-pyinotify] Upstream seems abandoned
1004387 was blocked by: 1075949 1075950 1075951 1075947 1075952 1075948
1004387 was not blocking any bugs.
Added blocking bug(s) of 1004387: 1075953
> affects 1075939 + lintian-brush
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Added indication that 1075939 affects lintian-brush

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

Processed: ganeti: depends on python3-pyinotify which seems dead upstream

[Debian Bug Tracking System]

Processing control commands:

> block 1004387 by -1
Bug #1004387 [python3-pyinotify] Upstream seems abandoned
1004387 was blocked by: 1075951 1075950 1075949 1075948 1075947
1004387 was not blocking any bugs.
Added blocking bug(s) of 1004387: 1075952
> affects 1075939 + ganeti
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Added indication that 1075939 affects ganeti

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

Processed: fail2ban: depends on python3-pyinotify which seems dead upstream

[Debian Bug Tracking System]

Processing control commands:

> block 1004387 by -1
Bug #1004387 [python3-pyinotify] Upstream seems abandoned
1004387 was blocked by: 1075947 1075948 1075950 1075949
1004387 was not blocking any bugs.
Added blocking bug(s) of 1004387: 1075951
> affects 1075939 + fail2ban
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Added indication that 1075939 affects fail2ban

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

Processed: affects 1075939

[Debian Bug Tracking System]

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

> affects 1075939 + cinnamon
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Added indication that 1075939 affects cinnamon
> thanks
Stopping processing here.

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

Processed: unarchiving 1028172

[Debian Bug Tracking System]

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

> unarchive 1028172
Bug #1028172 {Done: Bastian Germann } [libmpich-dev] 
libmpich-dev lacks dependencies required by its pkgconfig file
Unarchived Bug 1028172
> thanks
Stopping processing here.

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

Processed: retitle 1073484 to cinnamon: FTBFS: could not load ../xml/cinnamon-recorder.xml, and no fallback was found

[Debian Bug Tracking System]

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

> retitle 1073484 cinnamon: FTBFS: could not load ../xml/cinnamon-recorder.xml, 
> and no fallback was found
Bug #1073484 [src:cinnamon] cinnamon: FTBFS: make: *** [debian/rules:25: 
binary] Error 25
Changed Bug title to 'cinnamon: FTBFS: could not load 
../xml/cinnamon-recorder.xml, and no fallback was found' from 'cinnamon: FTBFS: 
make: *** [debian/rules:25: binary] Error 25'.
> thanks
Stopping processing here.

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

Processed: doit: depends on python3-pyinotify which seems dead upstream

[Debian Bug Tracking System]

Processing control commands:

> block 1004387 by -1
Bug #1004387 [python3-pyinotify] Upstream seems abandoned
1004387 was blocked by: 1075947 1075949 1075948
1004387 was not blocking any bugs.
Added blocking bug(s) of 1004387: 1075950
> affects 1075939 + doit
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Added indication that 1075939 affects doit

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

Processed: circuits: depends on python3-pyinotify which seems dead upstream

[Debian Bug Tracking System]

Processing control commands:

> block 1004387 by -1
Bug #1004387 [python3-pyinotify] Upstream seems abandoned
1004387 was blocked by: 1075948 1075947
1004387 was not blocking any bugs.
Added blocking bug(s) of 1004387: 1075949
> affects 1075939 + circuits
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Added indication that 1075939 affects circuits

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

Bug#1074583: upstream has provided a one-line patch to fix it

[Sanjoy Mahajan]

Upstream has a one-line patch to fix this issue, which I've tested with
success.  The commit id is given in the github issue:


-Sanjoy

Processed: Re: Bug#1075811: autokey-qt can be installed but will nor run

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-pyinotify 0.9.6-2
Bug #1075811 [autokey-qt] autokey-qt can be installed but will nor run
Bug reassigned from package 'autokey-qt' to 'python3-pyinotify'.
No longer marked as found in versions autokey/0.95.10-2.1.
Ignoring request to alter fixed versions of bug #1075811 to the same values 
previously set
Bug #1075811 [python3-pyinotify] autokey-qt can be installed but will nor run
Marked as found in versions pyinotify/0.9.6-2.
> affects -1 + autokey-common
Bug #1075811 [python3-pyinotify] autokey-qt can be installed but will nor run
Added indication that 1075811 affects autokey-common

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

Bug#1075811: autokey-qt can be installed but will nor run

[Simon McVittie]

Control: reassign -1 python3-pyinotify 0.9.6-2
Control: affects -1 + autokey-common

On Fri, 05 Jul 2024 at 16:25:30 +0100, Joe wrote:
> joe@jrenewsid:~$ autokey-qt
> Traceback (most recent call last):
...
> File "/usr/lib/python3/dist-packages/pyinotify.py", line
> 71, in 
> import asyncore
> ModuleNotFoundError: No module named 'asyncore'

This is a bug in pyinotify rather than in autokey-qt (a duplicate of
#1075939, see also #1040102).

> Is there a workaround?

According to #1040102, `apt install python3-pyasyncore` should work
around this.

smcv

Processed: severity of 1040102 is serious

[Debian Bug Tracking System]

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

> severity 1040102 serious
Bug #1040102 [src:pyinotify] pyinotify: deprecation of Python libraries 
asyncore and asynchat
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1075939 is serious, user debian-pyt...@lists.debian.org, usertagging 1075939

[Debian Bug Tracking System]

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

> severity 1075939 serious
Bug #1075939 [python3-pyinotify] python3-pyinotify missing runtime dependency
Severity set to 'serious' from 'normal'
> user debian-pyt...@lists.debian.org
Setting user to debian-pyt...@lists.debian.org (was s...@debian.org).
> usertags 1075939 + python3.12
There were no usertags set.
Usertags are now: python3.12.
> thanks
Stopping processing here.

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