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

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 | > |

Bug#1075760: hplip-gui breaks with python 3.12

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 =

Processed: Re: hplip-gui breaks with python 3.12

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:

Processed: Re: hplip-gui breaks with python 3.12

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)

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

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

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

Processed: Merge duplicates

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

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

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

Processed: Merge duplicates

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

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

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

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

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

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

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

Processed: severity of 1074370 is important

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

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

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

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

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

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

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

Bug#1075857: marked as pending in phoc

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:

Processed: Bug#1075857 marked as pending in phoc

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

Bug#1075857: marked as pending in phoc

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:

Processed: Bug#1075857 marked as pending in phoc

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

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

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

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

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 | |

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

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

Bug#1075851: mayavi2: FTBFS on ppc64el and riscv64

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

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

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

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

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

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

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

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

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

Processed: (No Subject)

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

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

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]

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

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

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

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

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

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.

Bug#1071007: Update available upstream

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,

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

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

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

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

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:

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

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

Processed: tagging 1065848

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:

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

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.

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

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

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

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

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

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 /.

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

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

Bug#1075793: plastimatch FTBFS with DCMTK 3.6.8

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 > >

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

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

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

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

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

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,

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

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

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

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

Processed: Bug#1074647 marked as pending in jackd2

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

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:

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)

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

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

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

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

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

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

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

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

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

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

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:

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

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 /

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

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

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

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

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

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’:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Bug#1075917: marked as pending in dcmtk

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:

Processed: Bug#1075917 marked as pending in dcmtk

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

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

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:

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

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

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

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

Bug#1073449: marked as pending in python-keystoneauth1

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:

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

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

Processed: closing 1073326

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

Bug#1074483: dcmtk: CVE-2024-27628

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

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

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

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

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

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 > . >

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

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:

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

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 >

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

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

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

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 +

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

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

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

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

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

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

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

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

Processed: affects 1075939

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:

Processed: unarchiving 1028172

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. --

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

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

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

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]

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

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]

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

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

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

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

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 >

Processed: severity of 1040102 is serious

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. --

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

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

  1   2   >