Bug#1000220: marked as done (dicomscope: error: cannot bind non-const lvalue reference of type ‘std::__cxx11::list >::const_iterator&’ to an rvalue of type ‘std::__cxx11::list

Your message dated Tue, 23 Nov 2021 07:48:33 + with message-id and subject line Bug#1000220: fixed in dcmtk 3.6.6-3 has caused the Debian Bug report #1000220, regarding dicomscope: error: cannot bind non-const lvalue reference of type ‘std::__cxx11::list >::const_iterator&’ to an rvalue of

Processed: Bug#1000220 marked as pending in dcmtk

Processing control commands: > tag -1 pending Bug #1000220 [src:dcmtk] dicomscope: error: cannot bind non-const lvalue reference of type ‘std::__cxx11::list >::const_iterator&’ to an rvalue of type ‘std::__cxx11::list >::const_iterator’ Ignoring request to alter tags of bug #1000220 to the same

Bug#1000220: marked as pending in dcmtk

Control: tag -1 pending Hello, Bug #1000220 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:

Bug#1000435: Matplotlib crashes on mips64el in lines.py

Source: matplotlib Severity: serious Version: 3.5.0-1 Control: affects -1 yt Control: affects -1 astropy With the new matplotlib version, I now have crashes with a segmentation fault in at least two of my packages on mips64el, which cause a FTBFS: yt and astropy. On both packages, the crash

Processed: Matplotlib crashes on mips64el in lines.py

Processing control commands: > affects -1 yt Bug #1000435 [src:matplotlib] Matplotlib crashes on mips64el in lines.py Added indication that 1000435 affects yt > affects -1 astropy Bug #1000435 [src:matplotlib] Matplotlib crashes on mips64el in lines.py Added indication that 1000435 affects

Bug#999519: xrayutilities: diff for NMU version 1.7.1-2.1

Dear Debian team, I think the patch can be used like this. I'll also release a new upstream version with this patch hopefully today. kind regards Dominik On Tue, Nov 23, 2021 at 2:48 AM Stefano Rivera wrote: > Control: tags 999519 + patch > Control: tags 999519 + pending > > Dear maintainer,

Bug#1000412: marked as done (poetry-core: autopkgtest regression: No such file or directory: 'git')

Your message dated Tue, 23 Nov 2021 06:18:39 + with message-id and subject line Bug#1000412: fixed in poetry-core 1.0.7-2 has caused the Debian Bug report #1000412, regarding poetry-core: autopkgtest regression: No such file or directory: 'git' to be marked as done. This means that you claim

Bug#1000425: marked as done (node-cheerio: FTBFS in sid)

Your message dated Tue, 23 Nov 2021 05:48:28 + with message-id and subject line Bug#1000425: fixed in node-cheerio 1.0.0~rc~10+~cs13.5.2-5 has caused the Debian Bug report #1000425, regarding node-cheerio: FTBFS in sid to be marked as done. This means that you claim that the problem has been

Bug#997364: marked as done (ruby-sprite-factory: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `opacity=' for 320x64 DirectClass 16-bit:Magick::Image)

Your message dated Tue, 23 Nov 2021 05:48:45 + with message-id and subject line Bug#997364: fixed in ruby-sprite-factory 1.7.1-4 has caused the Debian Bug report #997364, regarding ruby-sprite-factory: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `opacity=' for

Processed: tagging 1000412

Processing commands for cont...@bugs.debian.org: > tags 1000412 + pending Bug #1000412 [src:poetry-core] poetry-core: autopkgtest regression: No such file or directory: 'git' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000412:

Bug#997364: marked as pending in ruby-sprite-factory

Control: tag -1 pending Hello, Bug #997364 in ruby-sprite-factory 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#997364 marked as pending in ruby-sprite-factory

Processing control commands: > tag -1 pending Bug #997364 [src:ruby-sprite-factory] ruby-sprite-factory: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `opacity=' for 320x64 DirectClass 16-bit:Magick::Image Added tag(s) pending. -- 997364:

Processed: tagging 997364

Processing commands for cont...@bugs.debian.org: > # > https://github.com/jakesgordon/sprite-factory/pull/55/files#diff-8c5e632b364c4744c063806d71492877069319e4bca52c2723c3423a2095dd9c > tags 997364 + patch Bug #997364 [src:ruby-sprite-factory] ruby-sprite-factory: FTBFS: ERROR: Test "ruby2.7"

Bug#996212: marked as done (ruby-dalli: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 3, expected 2))

Your message dated Tue, 23 Nov 2021 05:03:48 + with message-id and subject line Bug#996212: fixed in ruby-dalli 3.0.3-1 has caused the Debian Bug report #996212, regarding ruby-dalli: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 3,

Bug#996217: marked as done (ruby-dry-logic: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)

Your message dated Tue, 23 Nov 2021 04:33:57 + with message-id and subject line Bug#996217: fixed in ruby-dry-logic 1.2.0-1 has caused the Debian Bug report #996217, regarding ruby-dry-logic: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: to be marked as done. This

Bug#996157: marked as done (ruby-clean-test: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_any_symbol_works(TestAny): ArgumentError: wrong number of arguments (given 2, expected 0..1))

Your message dated Tue, 23 Nov 2021 03:39:56 +0100 with message-id and subject line Fixed in ruby-faker has caused the Debian Bug report #996157, regarding ruby-clean-test: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_any_symbol_works(TestAny): ArgumentError: wrong number of

Bug#1000421: dpkg-shlibdeps: Wrong minimum version requirement on libc6

Hi! On Mon, 2021-11-22 at 22:49:43 +0100, Joachim Reichel wrote: > Package: dpkg-dev > Version: 1.20.9 > Severity: serious > Control: affects -1 cppcheck > dpkg-shlibdeps calculates too low minimum version requirements for cppcheck > on libc6 (see bug 1000146). > > To reproduce, build cppcheck

Bug#1000204: pyfai: diff for NMU version 0.20.0+dfsg1-4.1

Control: tags 1000204 + pending Dear maintainer, I've prepared an NMU for pyfai (versioned as 0.20.0+dfsg1-4.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Also filed as https://salsa.debian.org/science-team/pyfai/-/merge_requests/4 Regards, SR diff

Processed: pyfai: diff for NMU version 0.20.0+dfsg1-4.1

Processing control commands: > tags 1000204 + pending Bug #1000204 [pyfai] pyfai: FTBFS if built using python3.10 (collections.MutableSets deprecated) Added tag(s) pending. -- 1000204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000204 Debian Bug Tracking System Contact

Bug#999519: xrayutilities: diff for NMU version 1.7.1-2.1

Control: tags 999519 + patch Control: tags 999519 + pending Dear maintainer, I've prepared an NMU for xrayutilities (versioned as 1.7.1-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Also filed as:

Processed: xrayutilities: diff for NMU version 1.7.1-2.1

Processing control commands: > tags 999519 + patch Bug #999519 [src:xrayutilities] xrayutilities: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test -i python{version} -p 3.9 -s custom "--test-args={interpreter} {dir}/setup.py egg_info -e {build_dir}; cd

Bug#1000428: gammapy: FTBFS with matplotlib 3.5

Source: gammapy Version: 0.18.2-1 Severity: serious Justification: FTBFS Matplotlib 3.5 seems to have caused some test failures: === short test summary info FAILED gammapy/datasets/tests/test_map.py::test_plot_residual_onoff - ValueEr... FAILED

Bug#1000427: pyregion: FTBFS with setuptools >= 58

Source: pyregion Version: 2.1.1-1 Severity: serious Tags: upstream Justification: FTBFS pyregion fails to build with setuptools >= 58, which dropped use_2to3 support.: /usr/lib/python3/dist-packages/setuptools/dist.py:294: DistDeprecationWarning: use_2to3 is ignored. warnings.warn(f"{attr} is

Processed: block 1000423 with 1000422

Processing commands for cont...@bugs.debian.org: > block 1000423 with 1000422 Bug #1000423 [src:python-biom-format] python-biom-format: FTBFS with Python 3.10 - Test failures 1000423 was not blocked by any bugs. 1000423 was not blocking any bugs. Added blocking bug(s) of 1000423: 1000422 >

Processed (with 1 error): reassign 997882 to src:licensecheck, forcibly merging 994150 997882

Processing commands for cont...@bugs.debian.org: > reassign 997882 src:licensecheck Bug #997882 {Done: Jonas Smedegaard } [src:licensecheck] licensecheck: autopkgtest regression: lots of failures Ignoring request to reassign bug #997882 to the same package > forcemerge 994150 997882 Failed to

Bug#999484: marked as done (freedombox: Missing dependencies for essential modules)

Your message dated Tue, 23 Nov 2021 00:48:35 + with message-id and subject line Bug#999484: fixed in freedombox 21.14 has caused the Debian Bug report #999484, regarding freedombox: Missing dependencies for essential modules to be marked as done. This means that you claim that the problem

Processed: pidgin-sipe: diff for NMU version 1.25.0-2.1

Processing control commands: > tags 997278 + patch Bug #997278 [src:pidgin-sipe] pidgin-sipe: FTBFS: sipe-tls-tester.c:158:17: error: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead [-Werror=deprecated-declarations] Added tag(s) patch. > tags 997278 + pending Bug #997278 [src:pidgin-sipe]

Bug#997278: pidgin-sipe: diff for NMU version 1.25.0-2.1

Control: tags 997278 + patch Control: tags 997278 + pending Dear maintainer, I've prepared an NMU for pidgin-sipe (versioned as 1.25.0-2.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru pidgin-sipe-1.25.0/debian/changelog

Bug#1000414: textdistance: autopkgtest regression on arm64: AssertionError: assert 3.0 <= 1

On Mon, Nov 22, 2021 at 10:14:03PM +0100, Paul Gevers wrote: > Source: textdistance > Version: 4.2.2-1 > X-Debbugs-CC: debian...@lists.debian.org > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > With a recent upload of textdistance the

Bug#1000378: marked as done (telnetd: post-installation error)

Your message dated Mon, 22 Nov 2021 23:21:14 + with message-id and subject line Bug#1000378: fixed in netkit-telnet 0.17-44 has caused the Debian Bug report #1000378, regarding telnetd: post-installation error to be marked as done. This means that you claim that the problem has been dealt

Processed: bug 996406 is forwarded to https://github.com/Pylons/pyramid_chameleon/pull/34

Processing commands for cont...@bugs.debian.org: > forwarded 996406 https://github.com/Pylons/pyramid_chameleon/pull/34 Bug #996406 [src:python-pyramid, src:python-pyramid-chameleon] python-pyramid breaks python-pyramid-chameleon autopkgtest: No module named 'pyramid.compat' Set Bug

Bug#1000425: node-cheerio: FTBFS in sid

control: tags -1 patch Hello, I just discovered that the following patch, extracted from a big upstream refactor fixed the build/test Description: Fix build failure with part of upstream patch Origin: https://github.com/cheeriojs/cheerio/commit/b64cb31bb0d40d9d912a4e3a24a5ad22a5cdfced

Processed: Re: node-cheerio: FTBFS in sid

Processing control commands: > tags -1 patch Bug #1000425 [src:node-cheerio] node-cheerio: FTBFS in sid Added tag(s) patch. -- 1000425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#998507: marked as done (rails: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 3, expected 2))

Your message dated Mon, 22 Nov 2021 22:42:36 + with message-id and subject line Bug#998507: fixed in rails 2:6.1.4.1+dfsg-5 has caused the Debian Bug report #998507, regarding rails: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 3, expected 2) to be

Bug#997883: marked as done (rails: autopkgtest needs update for new version of puma: Could not find gem 'puma (~> 4.1)')

Your message dated Mon, 22 Nov 2021 22:42:36 + with message-id and subject line Bug#997883: fixed in rails 2:6.1.4.1+dfsg-5 has caused the Debian Bug report #997883, regarding rails: autopkgtest needs update for new version of puma: Could not find gem 'puma (~> 4.1)' to be marked as done.

Bug#996377: marked as done (ruby-rspec-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)

Your message dated Mon, 22 Nov 2021 22:42:36 + with message-id and subject line Bug#996377: fixed in rails 2:6.1.4.1+dfsg-5 has caused the Debian Bug report #996377, regarding ruby-rspec-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: to be marked as done. This means

Bug#1000425: node-cheerio: FTBFS in sid

Source: node-cheerio Version: 1.0.0~rc~10+~cs13.5.2-4 Severity: serious Hello, some changes in sid made the package FTBFS debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure --buildsystem=nodejs mkdir node_modules ln -s

Processed: bug 997203 is forwarded to https://svn.linuxsampler.org/cgi-bin/viewvc.cgi/gigedit/trunk/src/gigedit/compat.h?r1=4000=3999=4000

Processing commands for cont...@bugs.debian.org: > forwarded 997203 > https://svn.linuxsampler.org/cgi-bin/viewvc.cgi/gigedit/trunk/src/gigedit/compat.h?r1=4000=3999=4000 Bug #997203 [src:gigedit] gigedit: FTBFS: ../compat.h:194:21: error: ‘const Pango::Alignment Pango::ALIGN_LEFT’ redeclared

Processed: bug 997203 is forwarded to https://svn.linuxsampler.org/cgi-bin/viewvc.cgi/gigedit/trunk/src/gigedit/compat.h?r1=4000

Processing commands for cont...@bugs.debian.org: > forwarded 997203 > https://svn.linuxsampler.org/cgi-bin/viewvc.cgi/gigedit/trunk/src/gigedit/compat.h?r1=4000 Bug #997203 [src:gigedit] gigedit: FTBFS: ../compat.h:194:21: error: ‘const Pango::Alignment Pango::ALIGN_LEFT’ redeclared as

Bug#1000423: python-biom-format: FTBFS with Python 3.10 - Test failures

Source: python-biom-format Version: 2.1.10-2 Severity: serious Tags: upstream Justification: FTBFS Block -1 with 1000422 python-biom-format FTBFS with Python 3.10: === short test summary info ERROR biom/tests/test_err.py ERROR

Bug#1000422: pandas: FTBFS with Python 3.10 - Test failures

Source: pandas Version: 1.1.5+dfsg-2 Severity: serious Justification: FTBFS Pandas fails to build with Python 3.10. See: https://buildd.debian.org/status/fetch.php?pkg=pandas=amd64=1.1.5%2Bdfsg-2%2Bb1=1637461771=0 === FAILURES ===

Processed: dpkg-shlibdeps: Wrong minimum version requirement on libc6

Processing control commands: > affects -1 cppcheck Bug #1000421 [dpkg-dev] dpkg-shlibdeps: Wrong minimum version requirement on libc6 Added indication that 1000421 affects cppcheck -- 1000421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000421 Debian Bug Tracking System Contact

Bug#1000421: dpkg-shlibdeps: Wrong minimum version requirement on libc6

Package: dpkg-dev Version: 1.20.9 Severity: serious Control: affects -1 cppcheck Hi, dpkg-shlibdeps calculates too low minimum version requirements for cppcheck on libc6 (see bug 1000146). To reproduce, build cppcheck 2.6-1 in unstable chroot without cleaning up, e.g., "dpkg-buildpackage

Bug#996380: Explanation

It seems here is an explanation of the problem: https://github.com/paolobrasolin/jekyll-antex/issues/16 I cannot find any patches so far. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 /

Bug#1000419: pymatgen: FTBFS - Test failure: BSPlotterProjectedTest.test_methods

Source: pymatgen Version: 2022.0.14+dfsg1-1 Severity: serious Justification: FTBFS Presumably due to a new matplotlib, but I'm just guessing... .pybuild/test_python3.9/pymatgen/electronic_structure/tests/test_plotter.py . [ 55%] .F === FAILURES

Bug#998532: marked as done (dpdk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: "per_library_versions")

Your message dated Mon, 22 Nov 2021 21:19:37 + with message-id and subject line Bug#998532: fixed in dpdk 20.11.3-2 has caused the Debian Bug report #998532, regarding dpdk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: "per_library_versions" to be marked as done. This means that you

Bug#1000417: devscripts: autopkgtest regression: zstd: not found

Source: devscripts Version: 2.21.5 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of devscripts the autopkgtest of devscripts fails in testing when that autopkgtest is run with the binary

Bug#1000414: textdistance: autopkgtest regression on arm64: AssertionError: assert 3.0 <= 1

Source: textdistance Version: 4.2.2-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of textdistance the autopkgtest of textdistance fails in testing when that autopkgtest is run with the

Bug#1000413: discosnp: autopkgtest regression: Segmentation fault

Source: discosnp Version: 1:2.5.4-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of discosnp the autopkgtest of discosnp fails in testing when that autopkgtest is run with the binary

Bug#997882: marked as done (licensecheck: autopkgtest regression: lots of failures)

Your message dated Mon, 22 Nov 2021 21:04:04 + with message-id and subject line Bug#997882: fixed in licensecheck 3.2.14-1 has caused the Debian Bug report #997882, regarding licensecheck: autopkgtest regression: lots of failures to be marked as done. This means that you claim that the

Bug#997882: marked as pending in licensecheck

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

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

Processing control commands: > tag -1 pending Bug #997882 [src:licensecheck] licensecheck: autopkgtest regression: lots of failures Added tag(s) pending. -- 997882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#997882 marked as pending in licensecheck

Processing control commands: > tag -1 pending Bug #997882 [src:licensecheck] licensecheck: autopkgtest regression: lots of failures Ignoring request to alter tags of bug #997882 to the same tags previously set -- 997882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997882 Debian Bug

Bug#997718: glewlwyd: FTBFS: Module not found: Error: Can't resolve 'cross-fetch' in '/<>/webapp-src/node_modules/i18next-http-backend/cjs'

Hello, The package node-cross-fetch is in the NEW queue [1]. When it will be accepted in unstable, a quick change in the package i18next-http-backend will fix glewlwyd's ftbfs. /Nicolas [1] https://ftp-master.debian.org/new/node-cross-fetch_3.1.4%2Bds.1-1.html

Bug#1000412: poetry-core: autopkgtest regression: No such file or directory: 'git'

Source: poetry-core Version: 1.0.7-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of poetry-core the autopkgtest of poetry-core fails in testing when that autopkgtest is run with the

Bug#998353: src:win32-loader: fails to migrate to testing for too long

Dear Debian-boot, On Tue, 2 Nov 2021 20:55:11 +0100 Paul Gevers wrote: Can somebody please judge if win32-loader should migrate in the current state and take appropriate actions if so: contact ftp to process the package on their side and update bug 982838 (I wouldn't close it, but reuse it

Processed: Bug#998532 marked as pending in dpdk

Processing control commands: > tag -1 pending Bug #998532 [src:dpdk] dpdk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: "per_library_versions" Added tag(s) pending. -- 998532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998532 Debian Bug Tracking System Contact

Bug#998532: marked as pending in dpdk

Control: tag -1 pending Hello, Bug #998532 in dpdk 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#997172: marked as done (sngrep: FTBFS: curses/ui_manager.c:668:5: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Mon, 22 Nov 2021 18:50:32 + with message-id and subject line Bug#997172: fixed in sngrep 1.4.10-1 has caused the Debian Bug report #997172, regarding sngrep: FTBFS: curses/ui_manager.c:668:5: error: format not a string literal and no format arguments

Bug#997248: marked as done (mysql++: FTBFS: ./examples/load_jpeg.cpp:90:50: error: taking address of rvalue [-fpermissive])

Your message dated Mon, 22 Nov 2021 18:33:44 + with message-id and subject line Bug#997248: fixed in mysql++ 3.2.5-2.1 has caused the Debian Bug report #997248, regarding mysql++: FTBFS: ./examples/load_jpeg.cpp:90:50: error: taking address of rvalue [-fpermissive] to be marked as done.

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 1000220 pending patch Bug #1000220 [src:dcmtk] dicomscope: error: cannot bind non-const lvalue reference of type ‘std::__cxx11::list >::const_iterator&’ to an rvalue of type ‘std::__cxx11::list >::const_iterator’ Added tag(s) pending. >

Bug#1000357: marked as done (ddcci-dkms: install and module build failure with Linux 5.15: error: initialization of 'void (*)(struct device *)' from incompatible pointer type 'int (*)(struct device *)

Your message dated Mon, 22 Nov 2021 17:49:40 + with message-id and subject line Bug#1000357: fixed in ddcci-driver-linux 0.4.1-2 has caused the Debian Bug report #1000357, regarding ddcci-dkms: install and module build failure with Linux 5.15: error: initialization of 'void (*)(struct device

Processed: [bts-link] source package src:mod-wsgi

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:mod-wsgi > # 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

Bug#998867: debootstrap: --no-merged-usr became a no-op

On Mon, Nov 15, 2021 at 01:54:36PM +, Dimitri John Ledkov wrote: > > Also, build chroots must still be created without merged-usr for > > sid/bookworm, until something's been done to migrate user systems. > > But Julien, you said that buildds run stable, meaning they are > unaffected by this

Processed: Re: maxima-emacs: fails to install with xemacs21

Processing control commands: > found -1 5.45.1-5 Bug #999626 {Done: Camm Maguire } [maxima-emacs] maxima-emacs: fails to install with xemacs21 Marked as found in versions maxima/5.45.1-5; no longer marked as fixed in versions maxima/5.45.1-5 and reopened. -- 999626:

Bug#999626: maxima-emacs: fails to install with xemacs21

Followup-For: Bug #999626 Control: found -1 5.45.1-5 Hi, the bug is still present, but with a slightly different error message: Setting up maxima-emacs (5.45.1-5) ... Install emacsen-common for xemacs21 emacsen-common: Handling install of emacsen flavor xemacs21 Loading

Bug#984261: marked as done (ocaml-mccs: ftbfs with GCC-11)

Your message dated Mon, 22 Nov 2021 16:48:57 + with message-id and subject line Bug#984261: fixed in ocaml-mccs 1.1+13-1 has caused the Debian Bug report #984261, regarding ocaml-mccs: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1000370: marked as done (FTBFS (static assertion failed))

Your message dated Mon, 22 Nov 2021 16:48:57 + with message-id and subject line Bug#984261: fixed in ocaml-mccs 1.1+13-1 has caused the Debian Bug report #984261, regarding FTBFS (static assertion failed) to be marked as done. This means that you claim that the problem has been dealt with.

Bug#998679: firefox-esr freezes shortly after start

Package: firefox-esr Followup-For: Bug #998679 X-Debbugs-Cc: blasc...@hep.itp.tuwien.ac.at Dear Maintainer, for the past two days I've been testing firefox-esr 91.3.0 downloaded directly from mozilla.org on debian 11 (bullseye) without any problems: no crashes whatsoever.

Bug#998913: [biod/BioD] Fails to build with ldc 1.28.0 (Issue #55)

Hi Pjotr, Am Mon, Nov 22, 2021 at 08:17:26AM -0800 schrieb Pjotr Prins: > Thanks @tillea. I wonder if anyone is using BioD. Sambamba imported a subset > of BioD, but no longer does that. The motivation to package BioD was only to get Sambamba packaged. I have no idea whether there is any

Bug#997248: mysql++: FTBFS: ./examples/load_jpeg.cpp:90:50: error: taking address of rvalue [-fpermissive]

Hi Roberto, thanks for the quick response! > I cannot attend to this at the moment, so I give you my blessing to > proceed with the NMU. Thanks, will do that and upload soon. Cheers Sascha

Bug#993196: Germany Business List

Hi, Interested in Industry contacts professional list.. Please let me know which target criteria you would like to acquire!.. Target Industry: -__? (Any Industry) Target Country: - _? (Denmark , USA , UK, Germany and many more..) Target Job Title: -

Bug#1000182: marked as done (python-jira: network access during the build)

Your message dated Mon, 22 Nov 2021 16:04:27 + with message-id and subject line Bug#1000182: fixed in python-jira 3.1.1-1 has caused the Debian Bug report #1000182, regarding python-jira: network access during the build to be marked as done. This means that you claim that the problem has

Bug#997248: mysql++: FTBFS: ./examples/load_jpeg.cpp:90:50: error: taking address of rvalue [-fpermissive]

On Mon, Nov 22, 2021 at 01:16:06PM +0100, Sascha Steinbiss wrote: > Hi everyone, > > looks like upstream fixed this already [0]. The fix is easily imported > into packaging, see attached debdiff. > > I would be happy to NMU this within a week or so if there is no action > by the maintainer to

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reopen 1000222 Bug #1000222 {Done: Mathieu Malaterre } [src:orthanc] orthanc: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them. 'reopen' may be inappropriate when a bug has been closed

Bug#1000222: marked as done (orthanc: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them.)

Your message dated Mon, 22 Nov 2021 14:39:08 + with message-id and subject line Bug#1000222: fixed in orthanc 1.9.7+dfsg-2 has caused the Debian Bug report #1000222, regarding orthanc: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide

Bug#980016: marked as done (argus FTBFS due to missing link and includes for tirpc library)

Your message dated Mon, 22 Nov 2021 14:36:44 + with message-id and subject line Bug#980016: fixed in argus 2:3.0.8.2-2.1 has caused the Debian Bug report #980016, regarding argus FTBFS due to missing link and includes for tirpc library to be marked as done. This means that you claim that the

Bug#1000222: marked as pending in orthanc

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

Processing control commands: > tag -1 pending Bug #1000222 [src:orthanc] orthanc: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them. Added tag(s) pending. -- 1000222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000222 Debian Bug

Bug#997137: marked as done (ukui-control-center: FTBFS: type_traits:44:3: error: template with C linkage)

Your message dated Mon, 22 Nov 2021 13:34:53 + with message-id and subject line Bug#997137: fixed in ukui-control-center 3.0.4-1 has caused the Debian Bug report #997137, regarding ukui-control-center: FTBFS: type_traits:44:3: error: template with C linkage to be marked as done. This means

Bug#1000380: marked as done (node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/*)

Your message dated Mon, 22 Nov 2021 13:34:11 + with message-id and subject line Bug#1000380: fixed in node-superagent 6.1.0+repack-1 has caused the Debian Bug report #1000380, regarding node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/* to be marked

Bug#1000380: marked as done (node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/*)

Your message dated Mon, 22 Nov 2021 13:34:05 + with message-id and subject line Bug#1000380: fixed in node-fast-safe-stringify 2.1.1-1 has caused the Debian Bug report #1000380, regarding node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/* to be marked

Bug#1000380: marked as pending in node-superagent

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

Processing control commands: > tag -1 pending Bug #1000380 [node-superagent,node-fast-safe-stringify] node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/* Added tag(s) pending. -- 1000380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000380 Debian

Bug#998867: bumping severity

Control: severity -1 critical The current severity, "grave", is a serious understatement. As all buildd chroots that are created with buggy debootstrap are tainted, any packages built recently may assume merged usr, and thus needs to be rebuilt. Do we have a patch? If not, let's revert, today

Processed: bumping severity

Processing control commands: > severity -1 critical Bug #998867 [debootstrap] debootstrap: --no-merged-usr became a no-op Severity set to 'critical' from 'grave' -- 998867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998867 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#999525: [help] New error in test cases of bmtk

Hi, I think I've found a patch[1] to solve the original issue which just seems to be a floating point precision issue. However, meanwhile there is another less simple issue: ERRORS _ ERROR collecting

Bug#997248: mysql++: FTBFS: ./examples/load_jpeg.cpp:90:50: error: taking address of rvalue [-fpermissive]

Hi everyone, looks like upstream fixed this already [0]. The fix is easily imported into packaging, see attached debdiff. I would be happy to NMU this within a week or so if there is no action by the maintainer to avoid mysql++ to be removed from testing. Please let me know if this is not

Bug#1000308: marked as done (pycuda: FTBFS with Python 3.10)

Your message dated Mon, 22 Nov 2021 11:04:03 + with message-id and subject line Bug#1000308: fixed in pycuda 2021.1~dfsg-2 has caused the Debian Bug report #1000308, regarding pycuda: FTBFS with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1000380: node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/*

Package: node-superagent,node-fast-safe-stringify Severity: serious Tags: sid bookworm . User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 6.1.0+~2.1.1-1 Control: found -1 2.0.7-2 Hi, automatic installation tests of packages that share a file and at the same time do not

Processed: node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/*

Processing control commands: > found -1 6.1.0+~2.1.1-1 Bug #1000380 [node-superagent,node-fast-safe-stringify] node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/* There is no source info for the package 'node-fast-safe-stringify' at version

Processed: Re: Bug#1000293: Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1

Processing control commands: > tags -1 moreinfo Bug #1000293 [jackd2] Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1 Added tag(s) moreinfo. -- 1000293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000293 Debian Bug Tracking

Bug#1000293: Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1

Control: tags -1 moreinfo On 2021-11-21 00:55:50, Arnaldo Pirrone wrote: > Package: jackd2 > Version: 1.9.19~dfsg-2 > Severity: grave > X-Debbugs-Cc: it9...@gmail.com > > Apparently there is something wrong with Jack and dbus. > Also reported here: >

Bug#996320: marked as done (ruby-minitest-excludes: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)

Your message dated Mon, 22 Nov 2021 10:49:58 + with message-id and subject line Bug#996320: fixed in ruby-minitest-excludes 2.0.1-2 has caused the Debian Bug report #996320, regarding ruby-minitest-excludes: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This means

Bug#1000222: [Debian-med-packaging] Bug#1000222: orthanc force gnuc++11 reason

Dear Mathieu, I confirm that this is an acceptable patch, except that it could be applied only to "JsonCppConfiguration.cmake" (the "DownloadOrthancFramework.cmake" is part of the skeleton that is copied in each Orthanc official plugin). It was on my plan to do this patch by myself, once I

Bug#1000378: telnetd: post-installation error

Package: telnetd Version: 0.17-43 Severity: grave Justification: renders package unusable Dear Maintainer, package does report error on install: aptitude install telnetd Die folgenden NEUEN Pakete werden zusätzlich installiert: telnetd 0 Pakete aktualisiert, 1 zusätzlich installiert, 0

Processed: Re: orthanc force gnuc++11 reason

Processing control commands: > tags -1 patch Bug #1000222 [src:orthanc] orthanc: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them. Added tag(s) patch. -- 1000222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000222 Debian Bug

Bug#1000222: orthanc force gnuc++11 reason

Control: tags -1 patch Could someone confirm; this is an acceptable patch ? thanks donotforcec++11.patch Description: Binary data

Processed: orthanc force gnuc++11 reason

Processing control commands: > tags -1 upstream confirmed Bug #1000222 [src:orthanc] orthanc: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them. Added tag(s) upstream and confirmed. > affects -1 dcmtk/3.6.6-2 Bug #1000222 [src:orthanc]

  1   2   >