Bug#1017711: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

Hello, On Mon 22 Aug 2022 at 02:55AM +02, Vincent Lefevre wrote: > Control: found -1 1:28.1+1-2 > Control: severity -1 serious > > On 2022-08-19 12:10:31 +0200, Vincent Lefevre wrote: >> I have noticed that Emacs left a 137 MB coredump. > > This has occurred again (this time a 54 MB coredump). >

Bug#1017845: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el

Hello, On Sun 21 Aug 2022 at 02:46PM +02, Axel Beckert wrote: > Package: emacs-common > Version: 1:28.1+1-2 > Severity: serious > X-Debbugs-Cc: a...@debian.org > Control: affects -1 elpa-folding elpa-org elpa-git-timemachine > elpa-password-store > > Hi, > > upgrading emacs respectively

Processed (with 1 error): forcibly merging 1017698 1018253

Processing commands for cont...@bugs.debian.org: > forcemerge 1017698 1018253 Bug #1017698 [emacs-common] emacs-gtk: core dump with unsorted double linked list corrupted Bug #1017779 [emacs-common] emacs-common dies in postinst with "corrupted double-linked list" Bug #1017798 [emacs-common]

Processed: your mail

Processing commands for cont...@bugs.debian.org: > block 1020193 by 1021731 Bug #1020193 [src:pcre2el] pcre2el: FTBFS: make: *** [debian/rules:4: binary] Error 25 1020193 was not blocked by any bugs. 1020193 was not blocking any bugs. Added blocking bug(s) of 1020193: 1021731 > thanks Stopping

Bug#1020193: (no subject)

This bug is fixed in the upstream repository, but the fix requires a.el, which is in NEW at the moment. I'll upload fix for pcre2el when a-el gets accepted. Regards, Lev

Bug#1021755: racon: build-dependencies unsatisfiable on 32-bit.

Package: racon Version: 1.5.0-2 Severity: serious racon build-depends on libthread-pool-dev which is no longer available on 32-bit architectures, this means that the package can no longer be built on those architectures but the binaries are still in testing/unstable. In general there are three

Bug#1021754: rust-zoxide: build-dependencies unsatisfiable.

Package: rust-zoxide Version: 0.4.3-4 Severity: serious The rust-zoxide package depends on version 0.2 of the float-ord crate, but testing/unstable now has version 0.3 Unfortunately when I try to prepare an update with debcargo I get. REALVER=0.4.3 SOURCEONLY=1 DEBFULLNAME="Peter Michael

Bug#984205: marked as done (libpsm2: ftbfs with GCC-11)

Your message dated Fri, 14 Oct 2022 03:34:14 + with message-id and subject line Bug#984205: fixed in libpsm2 11.2.185-2 has caused the Debian Bug report #984205, regarding libpsm2: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#984297: marked as done (presage: ftbfs with GCC-11)

Your message dated Fri, 14 Oct 2022 03:34:39 + with message-id and subject line Bug#984297: fixed in presage 0.9.1-2.3 has caused the Debian Bug report #984297, regarding presage: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1020019: spring: FTBFS

I have been working on packaging a new upstream release which should address this problem. I still need to resolve some issues with the build system and the patches. The current results can be found in Git. signature.asc Description: This is a digitally signed message part

Bug#1016272: marked as done (ruby-kramdown: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError: invalid byte sequence in UTF-8)

Your message dated Fri, 14 Oct 2022 00:03:54 +0200 with message-id <956cde89-e8c0-a143-5a1f-f49f647c9...@web.de> and subject line Re: Bug#1016272: transient bug in latex has caused the Debian Bug report #1016272, regarding ruby-kramdown: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError: invalid

Processed: Bug#1021699 marked as pending in gimp

Processing control commands: > tag -1 pending Bug #1021699 [src:gimp] gimp: FTBFS: error: conflicting types for 'heif_init' Ignoring request to alter tags of bug #1021699 to the same tags previously set -- 1021699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021699 Debian Bug Tracking

Bug#1021699: marked as pending in gimp

Control: tag -1 pending Hello, Bug #1021699 in gimp 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#908056: marked as done (golang-github-vbatts-tar-split: CVE-2017-14992)

Your message dated Thu, 13 Oct 2022 23:39:52 +0200 with message-id <76004cd6-2ed4-3a1b-6d3a-9f50e926b...@debian.org> and subject line Re: golang-github-vbatts-tar-split: CVE-2017-14992 has caused the Debian Bug report #908056, regarding golang-github-vbatts-tar-split: CVE-2017-14992 to be marked

Processed: notfound 1016272 in texlive-base/2022.20220923-1

Processing commands for cont...@bugs.debian.org: > notfound 1016272 texlive-base/2022.20220923-1 Bug #1016272 [texlive-latex-base] ruby-kramdown: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError: invalid byte sequence in UTF-8 Ignoring request to alter found versions of bug #1016272 to the

Bug#1020566: closing 1020566

close 1020566 0.9.29 thanks Patches are listed in the changelog and CI seems to be fixed: https://ci.debian.net/packages/g/git-buildpackage/

Processed: closing 1020566

Processing commands for cont...@bugs.debian.org: > close 1020566 0.9.29 Bug #1020566 [src:git-buildpackage] git-buildpackage's autopkg tests fail with setuptools 65 Marked as fixed in versions git-buildpackage/0.9.29. Bug #1020566 [src:git-buildpackage] git-buildpackage's autopkg tests fail with

Processed: tagging 1021739

Processing commands for cont...@bugs.debian.org: > tags 1021739 + upstream Bug #1021739 [src:nekohtml] nekohtml: CVE-2022-24839 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1021739:

Bug#1020028: marked as done (cimg: FTBFS: ImfHeader.h:22:10: fatal error: ImathVec.h: No such file or directory)

Your message dated Thu, 13 Oct 2022 20:51:59 + with message-id and subject line Bug#1020028: fixed in cimg 3.1.6+dfsg-1 has caused the Debian Bug report #1020028, regarding cimg: FTBFS: ImfHeader.h:22:10: fatal error: ImathVec.h: No such file or directory to be marked as done. This means

Processed: tagging 1021737

Processing commands for cont...@bugs.debian.org: > tags 1021737 + upstream Bug #1021737 [src:lava] lava: CVE-2022-42902 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1021737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021737

Processed: severity of 958692 is serious, severity of 958682 is serious, severity of 980316 is serious

Processing commands for cont...@bugs.debian.org: > # raising severity as they block removal of node-request > severity 958692 serious Bug #958692 [node-matrix-js-sdk] node-matrix-js-sdk: Remove dependency to node-request Severity set to 'serious' from 'important' > severity 958682 serious Bug

Bug#1016085: marked as done (libqt5network5: depends on libssl3 but loads (wrong) file provided by libssl-dev instead)

Your message dated Thu, 13 Oct 2022 22:07:25 +0200 with message-id and subject line Re: Bug#1016085: libqt5network5: depends on libssl3 but loads (wrong) file provided by libssl-dev instead has caused the Debian Bug report #1016085, regarding libqt5network5: depends on libssl3 but loads (wrong)

Bug#1021732: libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ...

The QuickTime ColorRepresentation is decoded into separate tags as of ExifTool 12.45. - Phil > On Oct 13, 2022, at 1:52 PM, Paul Gevers wrote: > > Source: libimage-exiftool-perl, mat2 > Control: found -1 libimage-exiftool-perl/12.47+dfsg-1 > Control: found -1 mat2/0.13.0-1 > Severity:

Bug#1021394: marked as done (src:libcereal: FTBFS on arm, ppc64le, s390x)

Your message dated Thu, 13 Oct 2022 19:35:36 + with message-id and subject line Bug#1021394: fixed in libcereal 1.3.2+dfsg-4 has caused the Debian Bug report #1021394, regarding src:libcereal: FTBFS on arm, ppc64le, s390x to be marked as done. This means that you claim that the problem has

Bug#1017143: marked as done (android-platform-art: FTBFS: runtime/thread_linux.cc:36:22: error: constexpr variable 'kHostAltSigStackSize' must be initialized by a constant expression)

Your message dated Thu, 13 Oct 2022 19:34:43 + with message-id and subject line Bug#1017143: fixed in android-platform-art 11.0.0+r48-4 has caused the Debian Bug report #1017143, regarding android-platform-art: FTBFS: runtime/thread_linux.cc:36:22: error: constexpr variable

Bug#1017321: marked as done (android-platform-art: FTBFS: runtime/thread_linux.cc:36:22: error: constexpr variable 'kHostAltSigStackSize' must be initialized by a constant expression)

Your message dated Thu, 13 Oct 2022 19:34:43 + with message-id and subject line Bug#1017143: fixed in android-platform-art 11.0.0+r48-4 has caused the Debian Bug report #1017143, regarding android-platform-art: FTBFS: runtime/thread_linux.cc:36:22: error: constexpr variable

Bug#1015860: libxalan2-java: CVE-2022-34169

Hi, I just had a go at this issue and I discovered that libxalan2-java in Debian is not affected but rather bcel. https://tracker.debian.org/pkg/bcel The fixing commit in OpenJDK addresses the same code which is nowhere to be found in libxalan2-java but is present in bcel. The bcel upstream

Bug#1021739: nekohtml: CVE-2022-24839

Source: nekohtml X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for nekohtml. CVE-2022-24839[0]: | org.cyberneko.html is an html parser written in Java. The fork of | `org.cyberneko.html` used by Nokogiri (Rubygem) raises a |

Bug#1021394: src:libcereal: FTBFS on arm, ppc64le, s390x

Hi Scott, Am Thu, Oct 13, 2022 at 01:49:17PM -0400 schrieb Scott Talbert: > Merge request sent with patch: > https://salsa.debian.org/med-team/libcereal/-/merge_requests/1 Thanks a lot, uploaded by sponsoring the package as you to reward you for closing the bug. Kind regards Andreas. --

Bug#1021737: lava: CVE-2022-42902

Source: lava X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for lava. CVE-2022-42902[0]: | In Linaro Automated Validation Architecture (LAVA) before 2022.10, | there is dynamic code execution in lava_server/lavatable.py. Due

Processed: Bug#1017143 marked as pending in android-platform-art

Processing control commands: > tag -1 pending Bug #1017143 [src:android-platform-art] android-platform-art: FTBFS: runtime/thread_linux.cc:36:22: error: constexpr variable 'kHostAltSigStackSize' must be initialized by a constant expression Bug #1017321 [src:android-platform-art]

Bug#1017143: marked as pending in android-platform-art

Control: tag -1 pending Hello, Bug #1017143 in android-platform-art 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: tagging 1021699

Processing commands for cont...@bugs.debian.org: > tags 1021699 + pending Bug #1021699 [src:gimp] gimp: FTBFS: error: conflicting types for 'heif_init' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1021699:

Processed: Bug#1021394 marked as pending in libcereal

Processing control commands: > tag -1 pending Bug #1021394 [src:libcereal] src:libcereal: FTBFS on arm, ppc64le, s390x Added tag(s) pending. -- 1021394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1021394: marked as pending in libcereal

Control: tag -1 pending Hello, Bug #1021394 in libcereal 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: merging 1017143 1017321

Processing commands for cont...@bugs.debian.org: > merge 1017143 1017321 Bug #1017143 [src:android-platform-art] android-platform-art: FTBFS: runtime/thread_linux.cc:36:22: error: constexpr variable 'kHostAltSigStackSize' must be initialized by a constant expression Bug #1017143

Processed: popt uploaded to unstable

Processing control commands: > severity -1 serious Bug #1020446 [src:gdisk] gdisk: FTBFS with popt 1.19+dfsg-1~exp1 Severity set to 'serious' from 'important' -- 1020446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020446 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1021736: rake-compiler: autopkgtest regression: cannot load such file -- rspec/core/rake_task

Source: rake-compiler Version: 1.2.0-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of rake-compiler the autopkgtest of rake-compiler fails in testing when that autopkgtest is run with the binary packages of rake-compiler

Bug#1021735: libffi breaks python3.10 autopkgtest on arm64 (and 5 other packages)

Source: libffi Control: found -1 libffi/3.4.3-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks Dear maintainer(s), With a recent upload of libffi the autopkgtest of python3.10 fails in testing when that autopkgtest is run with the binary packages of

Processed: libffi breaks python3.10 autopkgtest on arm64 (and 5 other packages)

Processing control commands: > found -1 libffi/3.4.3-2 Bug #1021735 [src:libffi] libffi breaks python3.10 autopkgtest on arm64 (and 5 other packages) Marked as found in versions libffi/3.4.3-2. -- 1021735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021735 Debian Bug Tracking System

Processed: Re: please update sage for pari 2.15.0 and gap 4.12.0

Processing control commands: > severity -1 serious Bug #1020576 [src:sagemath] please update sage for pari 2.15.0 and gap 4.12.0 Severity set to 'serious' from 'normal' -- 1020576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020576 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1021734: prometheus-alertmanager: autopkgtest regression: address already in use

Source: prometheus-alertmanager Version: 0.24.0-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of prometheus-alertmanager the autopkgtest of prometheus-alertmanager fails in testing when that autopkgtest is run with the

Processed: src:sbcl: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 2:2.2.9-1 Bug #1021733 [src:sbcl] src:sbcl: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions sbcl/2:2.2.9-1. Bug #1021733 [src:sbcl] src:sbcl: fails to migrate to testing for too long: autopkgtest regression

Bug#1021733: src:sbcl: fails to migrate to testing for too long: autopkgtest regression

Source: sbcl Version: 2:2.2.3-2 Severity: serious Control: close -1 2:2.2.9-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1016750 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Bug#1021732: libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ...

Source: libimage-exiftool-perl, mat2 Control: found -1 libimage-exiftool-perl/12.47+dfsg-1 Control: found -1 mat2/0.13.0-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libimage-exiftool-perl the

Processed: libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ...

Processing control commands: > found -1 libimage-exiftool-perl/12.47+dfsg-1 Bug #1021732 [src:libimage-exiftool-perl, src:mat2] libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ... Marked as found in versions libimage-exiftool-perl/12.47+dfsg-1. > found -1

Processed: Re: Bug#1021394: src:libcereal: FTBFS on arm, ppc64le, s390x

Processing control commands: > tags -1 patch Bug #1021394 [src:libcereal] src:libcereal: FTBFS on arm, ppc64le, s390x Added tag(s) patch. -- 1021394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1021394: src:libcereal: FTBFS on arm, ppc64le, s390x

Control: tags -1 patch On Fri, 7 Oct 2022, Scott Talbert wrote: Control: tags -1 help Control: tags -1 upstream Control: tags -1 forwarded https://github.com/USCiLab/cereal/issues/744 Merge request sent with patch: https://salsa.debian.org/med-team/libcereal/-/merge_requests/1 Regards,

Processed: your mail

Processing commands for cont...@bugs.debian.org: > affects 1021566 + src:slic3r-prusa Bug #1021566 [occt-misc] occt-misc contains architecture dependent CMake files Added indication that 1021566 affects src:slic3r-prusa > thanks Stopping processing here. Please contact me if you need assistance.

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 975490 u-boot/2022.10+dfsg-1 Bug #975490 [u-boot-sunxi] u-boot-sunxi: A64-Olinuxino-eMMC boot stuck at "Starting kernel ..." Marked as fixed in versions u-boot/2022.10+dfsg-1. > thanks Stopping processing here. Please contact me if you

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

Your message dated Thu, 13 Oct 2022 16:39:47 + with message-id and subject line Bug#1020107: fixed in khal 1:0.10.4~ds-4 has caused the Debian Bug report #1020107, regarding khal: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13 to be

Processed: Bug#1020107 marked as pending in khal

Processing control commands: > tag -1 pending Bug #1020107 [src:khal] khal: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13 Added tag(s) pending. -- 1020107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020107 Debian Bug Tracking

Bug#1020107: marked as pending in khal

Control: tag -1 pending Hello, Bug #1020107 in khal 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#1021537: marked as done (poetry-core: FTBFS with test failures)

Your message dated Thu, 13 Oct 2022 16:12:02 + with message-id and subject line Bug#1021537: fixed in poetry-core 1.1.0~b3-2 has caused the Debian Bug report #1021537, regarding poetry-core: FTBFS with test failures to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#1021676: r-cran-leidenbase: autopkgtest failure on several architectures

Processing control commands: > tags -1 upstream Bug #1021676 [src:r-cran-leidenbase] r-cran-leidenbase: autopkgtest failure on several architectures Added tag(s) upstream. > forwarded -1 https://github.com/cole-trapnell-lab/leidenbase/issues/36 Bug #1021676 [src:r-cran-leidenbase]

Bug#1021676: r-cran-leidenbase: autopkgtest failure on several architectures

Control: tags -1 upstream Control: forwarded -1 https://github.com/cole-trapnell-lab/leidenbase/issues/36 Hi Adrian, thanks a lot for this bug report Am Wed, Oct 12, 2022 at 09:59:05PM +0300 schrieb Adrian Bunk: > Source: r-cran-leidenbase > Version: 0.1.12-1 > Severity: serious > Control:

Processed: Re: telegram-cli: Outdated app that is no longer supported

Processing control commands: > severity -1 grave Bug #1018754 [telegram-cli] telegram-cli: Outdated app that is no longer supported Severity set to 'grave' from 'important' -- 1018754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018754 Debian Bug Tracking System Contact

Bug#1021537: marked as pending in poetry-core

Control: tag -1 pending Hello, Bug #1021537 in poetry-core 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#1021537 marked as pending in poetry-core

Processing control commands: > tag -1 pending Bug #1021537 [src:poetry-core] poetry-core: FTBFS with test failures Added tag(s) pending. -- 1021537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1020046: slimit: FTBFS: ModuleNotFoundError: No module named 'minifier'

This needs to be converted to a relative import. Upstream did this in commit https://github.com/rspivak/slimit/commit/40956e7fc6e954b3e6d7b629faeb3303f5efb7ea

Bug#1021389: marked as done (tcl-ttkthemes: When this is installed, tclsh 'package require Tk' fails with circular dependency error)

Your message dated Thu, 13 Oct 2022 15:11:47 + with message-id and subject line Bug#1021389: fixed in ttkthemes 3.2.2+git20220101+07e6509cc6bf-2 has caused the Debian Bug report #1021389, regarding tcl-ttkthemes: When this is installed, tclsh 'package require Tk' fails with circular

Bug#1020056:

The reason for the build breakage can be found in https://tracker.debian.org/media/packages/z/zeromq3/changelog-4.3.4-3 which has zeromq3 (4.3.4-3) unstable; urgency=medium * Remove zmq{,_addon}.hpp as these provided by cppzmq-dev from now on (closes: #972785). -- Laszlo Boszormenyi

Bug#1021660: gcc-12-offload-nvptx: offloading to nvidia via nvptx fails with cuda version 11 (default in sid)

On Thu, 13 Oct 2022, Thomas Schwinge wrote: It does work, but only for the code that GCC/nvptx generates in that 'gcc-12' invocation, but not for the support libraries that it linkes in, which are built for sm_30. Does this mean then that the support libraries of gcc-11-offload-nvptx include

Bug#1020046: marked as pending in slimit

Control: tag -1 pending Hello, Bug #1020046 in slimit 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#1020046 marked as pending in slimit

Processing control commands: > tag -1 pending Bug #1020046 [src:slimit] slimit: FTBFS: ModuleNotFoundError: No module named 'minifier' Added tag(s) pending. -- 1020046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020046 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1017941: greenbone-security-assistant downloads source from the network

Hello, Le 12/10/2022 à 01:37, Andreas Beckmann a écrit : A similar case is src:nvda2speechd (#1021390) and the solution there was to move the package to non-free. Yes I think it's the only solution here. I will move the package to non-free. There is a new upstream release. I'm working on the

Bug#1020043: pillow: FTBFS: ModuleNotFoundError: No module named 'PIL'

Control: tags -1 patch Hi, Please consider applying the patch pasted inline if deemed appropriate. I confirm that it fixes the build locally for me. Thanks! diff --git a/debian/rules b/debian/rules index 68e9a8c..96cc5ca 100755 --- a/debian/rules +++ b/debian/rules @@ -23,7 +23,7 @@

Processed: Re: pillow: FTBFS: ModuleNotFoundError: No module named 'PIL'

Processing control commands: > tags -1 patch Bug #1020043 [src:pillow] pillow: FTBFS: ModuleNotFoundError: No module named 'PIL' Added tag(s) patch. -- 1020043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1021235: marked as done (python-pymeasure: please switch to QtWidgets.QTreeWidgetItem)

Your message dated Thu, 13 Oct 2022 11:50:28 + with message-id and subject line Bug#1021235: fixed in python-pymeasure 0.9.0-2 has caused the Debian Bug report #1021235, regarding python-pymeasure: please switch to QtWidgets.QTreeWidgetItem to be marked as done. This means that you claim

Bug#1017252: marked as done (xcffib: FTBFS: make[2]: *** [Makefile:16: xcffib] Error 1)

Your message dated Thu, 13 Oct 2022 11:08:29 + with message-id and subject line Bug#1017252: fixed in xcffib 0.11.1-3 has caused the Debian Bug report #1017252, regarding xcffib: FTBFS: make[2]: *** [Makefile:16: xcffib] Error 1 to be marked as done. This means that you claim that the

Bug#1021660: gcc-12-offload-nvptx: offloading to nvidia via nvptx fails with cuda version 11 (default in sid)

Hi! (Tom added in CC; for your information, this is about .) On 2022-10-13T12:38:17+0200, Giacomo Mulas wrote: > On Thu, 13 Oct 2022, Thomas Schwinge wrote: > >> Aha, that's a legit question to wonder about: the reason is that GCC 11 >> defaulted to sm_35 code

Processed: Bug#1017252 marked as pending in xcffib

Processing control commands: > tag -1 pending Bug #1017252 [src:xcffib] xcffib: FTBFS: make[2]: *** [Makefile:16: xcffib] Error 1 Added tag(s) pending. -- 1017252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1017252: marked as pending in xcffib

Control: tag -1 pending Hello, Bug #1017252 in xcffib 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#1021660: gcc-12-offload-nvptx: offloading to nvidia via nvptx fails with cuda version 11 (default in sid)

On Thu, 13 Oct 2022, Thomas Schwinge wrote: Aha, that's a legit question to wonder about: the reason is that GCC 11 defaulted to sm_35 code generation (which CUDA 11 still does support): , just then GCC 12 again reverted to sm_30:

Bug#1021707: xrstools: build dependency missing in testing: python3-tango

Source: xrstools Version: 0.15.0+git20210910+c147919d-3 Severity: serious User: debian...@lists.debian.org Usertag: edos-uninstallable Dear maintainer(s), Dose [1] is reporting issues with your packages. Normally your build dependencies shouldn't be removed from testing without removal all

Bug#1021660: gcc-12-offload-nvptx: offloading to nvidia via nvptx fails with cuda version 11 (default in sid)

Hi Giacomo! On 2022-10-13T12:20:19+0200, Giacomo Mulas wrote: > On Thu, 13 Oct 2022, Thomas Schwinge wrote: > >> Debian need to update nvptx-tools to a version that includes >> >> "as: Deal with CUDA 11.0, "Support for Kepler 'sm_30' and

Bug#1021706: tt-rss: build dependency missing in testing: libjs-prototype (= 1.7.1-3.1)

Source: tt-rss Version: 21~git20210204.b4cbc79+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertag: edos-uninstallable Dear maintainer(s), Dose [1] is reporting issues with your packages. Normally your build dependencies shouldn't be removed from testing without removal all

Bug#1021705: metakernel: build dependency missing in testing: python3-pypandoc

Source: metakernel Version: 0.27.5-4 Severity: serious User: debian...@lists.debian.org Usertag: edos-uninstallable Dear maintainer(s), Dose [1] is reporting issues with your packages. Normally your build dependencies shouldn't be removed from testing without removal all reverse build

Bug#1021704: amanda: build dependency missing in testing xfsdump

Source: amanda Version: 1:3.5.1-9 Severity: serious User: debian...@lists.debian.org Usertag: edos-uninstallable Dear maintainer(s), Dose [1] is reporting issues with your packages. Normally your build dependencies shouldn't be removed from testing without removal all reverse build

Bug#1020022: marked as done (python-argon2: FTBFS: cc1: fatal error: extras/libargon2/src/argon2.c: No such file or directory)

Your message dated Thu, 13 Oct 2022 10:19:20 + with message-id and subject line Bug#1020022: fixed in python-argon2 21.1.0-2 has caused the Debian Bug report #1020022, regarding python-argon2: FTBFS: cc1: fatal error: extras/libargon2/src/argon2.c: No such file or directory to be marked as

Processed: affects multiple packages that somehow survived removal

Processing commands for cont...@bugs.debian.org: > affects 1012482 src:ardour src:python-biopython src:zeitgeist Bug #1012482 [src:rdflib] rdflib: URLInputSource can be abused to retrieve arbitrary documents if used naïvely Added indication that 1012482 affects src:ardour, src:python-biopython,

Processed: affects multiple packages that somehow survived removal

Processing commands for cont...@bugs.debian.org: > affects 1012482 src:kallisto Bug #1012482 [src:rdflib] rdflib: URLInputSource can be abused to retrieve arbitrary documents if used naïvely Added indication that 1012482 affects src:kallisto > thanks Stopping processing here. Please contact me

Bug#1021660: gcc-12-offload-nvptx: offloading to nvidia via nvptx fails with cuda version 11 (default in sid)

On Thu, 13 Oct 2022, Thomas Schwinge wrote: Debian need to update nvptx-tools to a version that includes "as: Deal with CUDA 11.0, "Support for Kepler 'sm_30' and 'sm_32' architecture based products is dropped" ok, but I am puzzled by

Processed: Bug#1020022 marked as pending in python-argon2

Processing control commands: > tag -1 pending Bug #1020022 [src:python-argon2] python-argon2: FTBFS: cc1: fatal error: extras/libargon2/src/argon2.c: No such file or directory Added tag(s) pending. -- 1020022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020022 Debian Bug Tracking System

Bug#1021701: pytest-testinfra: build dependency missing in testing: salt-common

Source: pytest-testinfra Version: 6.8.0-1 Severity: serious User: debian...@lists.debian.org Usertag: edos-uninstallable Dear maintainer(s), Dose [1] is reporting issues with your packages. Normally your build dependencies shouldn't be removed from testing without removal all reverse build

Bug#1020022: marked as pending in python-argon2

Control: tag -1 pending Hello, Bug #1020022 in python-argon2 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#1021660: gcc-12-offload-nvptx: offloading to nvidia via nvptx fails with cuda version 11 (default in sid)

reassign 1021660 nvptx-tools stop Hi! On 2022-10-12T17:19:02+0200, Giacomo Mulas wrote: > the nvptx plugin for gcc-12 currently available for sid mandates a > cuda level sm_30, which is no longer available in cuda 11 (the one > now in sid). This means that even a trivial example code like

Processed: Re: Bug#1021660: gcc-12-offload-nvptx: offloading to nvidia via nvptx fails with cuda version 11 (default in sid)

Processing commands for cont...@bugs.debian.org: > reassign 1021660 nvptx-tools Bug #1021660 [gcc-12-offload-nvptx] gcc-12-offload-nvptx: offloading to nvidia via nvptx fails with cuda version 11 (default in sid) Bug reassigned from package 'gcc-12-offload-nvptx' to 'nvptx-tools'. No longer

Processed: tagging 1020087, found 1020087 in 0.15.1-1

Processing commands for cont...@bugs.debian.org: > tags 1020087 - bookworm sid Bug #1020087 [src:guile-ssh] guile-ssh: FTBFS: dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2 Removed tag(s) bookworm and sid. > found

Processed: NMU bug 965878: xbitmaps: Removal of obsolete debhelper compat 5 and 6 in bookworm

Processing control commands: > tag -1 pending Bug #965878 [src:xbitmaps] xbitmaps: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965878 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#965878: NMU bug 965878: xbitmaps: Removal of obsolete debhelper compat 5 and 6 in bookworm

Control: tag -1 pending Hi, On Mon, 20 Jul 2020 19:35:37 + Niels Thykier wrote: The package xbitmaps uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! *

Bug#1020054: h5py: FTBFS: ld: final link failed: bad value

Source: h5py Followup-For: Bug #1020054 The problem is partially related to the -L/usr/lib/x86_64-linux-gnu -lhdf5 in the failing compilation line. Since debian provides serial and mpi builds of hdf5, there is no /usr/lib/x86_64-linux-gnu/libhdf5.so (there is libhdf5_serial.so and

Processed: maybe a non-existing version doesn't work...

Processing commands for cont...@bugs.debian.org: > notfixed 1010152 1:27.2~ Bug #1010152 [emacs-gtk] emacs-gtk: tries to read a config file from another user's home dir There is no source info for the package 'emacs-gtk' at version '1:27.2~' with architecture '' Unable to make a source version

Bug#1020054: h5py: FTBFS: ld: final link failed: bad value

Source: h5py Version: 3.7.0-2 Followup-For: Bug #1020054 Reproducible, e.g. https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/h5py_3.7.0-2.rbuild.log.gz I suspect the bug is not in h5py but rather in libhdf5-openmpi-dev, possibly in the flags used by h5pcc. The last hdf5