Bug#987816: marked as pending in dask.distributed

Control: tag -1 pending Hello, Bug #987816 in dask.distributed 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#987816 marked as pending in dask.distributed

Processing control commands: > tag -1 pending Bug #987816 [src:dask.distributed] dask.distributed: FTBFS due to a build-time test failure Added tag(s) pending. -- 987816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987816 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1000732: python3-click-threading: broken monkeypatching

Package: python3-click-threading Version: 0.4.4-2 Severity: serious X-Debbugs-Cc: none, Tollef Fog Heen It seems like the monkeypatching in /usr/lib/python3/dist-packages/click_threading/monkey.py is broken, at least for me. I'm using python3-click-threading by way of vdirsyncer: $ vdirsyncer

Bug#1000187: [Pkg-auth-maintainers] Bug#1000187: yubikey-manager: Exception when trying to add an oath account

Hi Tobias, On Fri, Nov 19, 2021 at 11:51:46AM +, Tobias Bengfort wrote: > Package: yubikey-manager > Version: 4.0.0~a1-4 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > >$ ykman oath accounts add foo bar > > always results in > >AttributeError:

Bug#1000233: php-remctl lost its phpapi-20190902 dependency

Adrian Bunk writes: > Package: php-remctl > Version: 3.17-1 > Severity: serious > Tags: bookworm sid > After the src:remctl rebuild to add Python 3.10 as supported version, > php-remctl lost its phpapi-20190902 dependency: > Package: php-remctl > Source: remctl > Version: 3.17-1 >

Bug#1000680: python3-aiohttp: fails to import, "TypeError: function() argument 'code' must be code, not str"

> root@zion:/# python3.9 -c "import aiohttp" > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python3/dist-packages/aiohttp/__init__.py", line 6, in > > from .client import ( > File "/usr/lib/python3/dist-packages/aiohttp/client.py", line 35, in > >

Processed: tagging 996294

Processing commands for cont...@bugs.debian.org: > tags 996294 - pending Bug #996294 [src:ruby-httpclient] ruby-httpclient: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 996294:

Processed: bug 996294 is forwarded to https://github.com/nahi/httpclient/issues/448

Processing commands for cont...@bugs.debian.org: > forwarded 996294 https://github.com/nahi/httpclient/issues/448 Bug #996294 [src:ruby-httpclient] ruby-httpclient: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Set Bug forwarded-to-address to 'https://github.com/nahi/httpclient/issues/448'.

Bug#996294: Change in webrick 1.7.0 is causing a problem with the tests in Ruby 2.7 (at least)

I did some debugging on the issue reported that the tests fail after adding ruby-webrick 1.7.0 to b-d for Ruby 3.0. The problem is in parse_header() (lib/httpclient/session.rb) in the line 828 line = socket.gets("\n") With webrick 1.7.0 it stalls here. This is caused by this small

Bug#1000204: marked as done (pyfai: FTBFS if built using python3.10 (collections.MutableSets deprecated))

Your message dated Sun, 28 Nov 2021 02:48:31 + with message-id and subject line Bug#1000204: fixed in pyfai 0.20.0+dfsg1-4.1 has caused the Debian Bug report #1000204, regarding pyfai: FTBFS if built using python3.10 (collections.MutableSets deprecated) to be marked as done. This means that

Processed: tagging 999857

Processing commands for cont...@bugs.debian.org: > tags 999857 + pending Bug #999857 [src:mod-wsgi] mod-wsgi FTBFS with python 3.10 as supported version Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 999857:

Bug#997424: marked as done (python-aiohttp-security: FTBFS: Could not import extension aiohttp_doctools (exception: cannot import name 'PyModulelevel' from 'sphinx.domains.python' (/usr/lib/python3/di

Your message dated Sun, 28 Nov 2021 01:19:53 + with message-id and subject line Bug#997424: fixed in python-aiohttp-security 0.4.0-3 has caused the Debian Bug report #997424, regarding python-aiohttp-security: FTBFS: Could not import extension aiohttp_doctools (exception: cannot import name

Processed: severity of 996238 is important, severity of 1000729 is important

Processing commands for cont...@bugs.debian.org: > severity 996238 important Bug #996238 [src:ruby-hamster] ruby-hamster: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Severity set to 'important' from 'serious' > # workarounds are in place, so demote to important > severity

Processed: bug 996238 is forwarded to https://github.com/hamstergem/hamster/issues/251

Processing commands for cont...@bugs.debian.org: > forwarded 996238 https://github.com/hamstergem/hamster/issues/251 Bug #996238 [src:ruby-hamster] ruby-hamster: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Set Bug forwarded-to-address to

Processed: block 996238 with 1000729

Processing commands for cont...@bugs.debian.org: > block 996238 with 1000729 Bug #996238 [src:ruby-hamster] ruby-hamster: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: 996238 was not blocked by any bugs. 996238 was not blocking any bugs. Added blocking bug(s) of 996238: 1000729

Processed: bug 1000729 is forwarded to https://github.com/knu/sorted_set/issues/3

Processing commands for cont...@bugs.debian.org: > forwarded 1000729 https://github.com/knu/sorted_set/issues/3 Bug #1000729 [src:ruby-sorted-set] ruby-hamster FTBFS caused by ruby-rbtree and ruby-sorted-set Set Bug forwarded-to-address to 'https://github.com/knu/sorted_set/issues/3'. > thanks

Bug#996238: ruby-hamster FTBFS caused by ruby-rbtree and ruby-sorted-set

Source: ruby-sorted-set Version: 1.0.3-2 Severity: serious User: debian-r...@lists.debian.org Usertags: ruby3.0 Tags: help After doing some debugging on the ruby-hamster FTBFS, the problem seems to be ruby-btree and ruby-sorted-set breaking the tests. In a pure Ruby 2.7 environment, this is

Bug#998281: marked as done (uhd: FTBFS during binary-indep only build)

Your message dated Sat, 27 Nov 2021 23:38:22 + with message-id and subject line Bug#998281: fixed in uhd 4.1.0.4-2 has caused the Debian Bug report #998281, regarding uhd: FTBFS during binary-indep only build to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: Bug#997208: firmware-microbit-micropython: FTBFS: platform.h:25:10: fatal error: cstddef: No such file or directory

Processing control commands: > severity 998365 serious Bug #998365 [libstdc++-arm-none-eabi-newlib] libstdc++-arm-none-eabi-newlib: Version of libstdc++-arm-none-eabi-newlib and gcc-arm-none-eabi must match or the C++ libraries can't be found Ignoring request to change severity of Bug 998365 to

Processed: Re: Bug#997208: firmware-microbit-micropython: FTBFS: platform.h:25:10: fatal error: cstddef: No such file or directory

Processing control commands: > severity 998365 serious Bug #998365 [libstdc++-arm-none-eabi-newlib] libstdc++-arm-none-eabi-newlib: Version of libstdc++-arm-none-eabi-newlib and gcc-arm-none-eabi must match or the C++ libraries can't be found Severity set to 'serious' from 'important' > close

Bug#997208: firmware-microbit-micropython: FTBFS: platform.h:25:10: fatal error: cstddef: No such file or directory

Control: severity 998365 serious Control: close 997208 On Sun, Oct 24, 2021 at 12:48:33PM +0200, Ondřej Kuzník wrote: > On Sat, Oct 23, 2021 at 09:11:58PM +0200, Lucas Nussbaum wrote: > > Source: firmware-microbit-micropython > > Version: 1.0.1-2 > > Severity: serious > > Justification: FTBFS > >

Bug#1000414: marked as done (textdistance: autopkgtest regression on arm64: AssertionError: assert 3.0 <= 1)

Your message dated Sat, 27 Nov 2021 22:48:43 + with message-id and subject line Bug#1000414: fixed in textdistance 4.2.2-2 has caused the Debian Bug report #1000414, regarding textdistance: autopkgtest regression on arm64: AssertionError: assert 3.0 <= 1 to be marked as done. This means

Bug#1000666: marked as done (git-review: Fatal failure with newer git releases)

Your message dated Sat, 27 Nov 2021 22:48:37 + with message-id and subject line Bug#1000666: fixed in git-review 2.2.0-1 has caused the Debian Bug report #1000666, regarding git-review: Fatal failure with newer git releases to be marked as done. This means that you claim that the problem has

Processed: Bug#1000666 marked as pending in git-review

Processing control commands: > tag -1 pending Bug #1000666 [git-review] git-review: Fatal failure with newer git releases Added tag(s) pending. -- 1000666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1000666: marked as pending in git-review

Control: tag -1 pending Hello, Bug #1000666 in git-review 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: Forwarded gammapy bug

Processing commands for cont...@bugs.debian.org: > forwarded 1000613 https://github.com/gammapy/gammapy/issues/3662 Bug #1000613 [src:gammapy] gammapy FTBFS on !amd64: test failures Set Bug forwarded-to-address to 'https://github.com/gammapy/gammapy/issues/3662'. > thanks Stopping processing

Bug#996350: marked as done (ruby-rabl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)

Your message dated Sat, 27 Nov 2021 21:49:28 + with message-id and subject line Bug#996350: fixed in ruby-rabl 0.13.1-2 has caused the Debian Bug report #996350, regarding ruby-rabl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This means that you claim that the

Bug#1000702: marked as done (src:sonic-visualiser: fails to migrate to testing for too long: FTBFS on armel and mipsel)

Your message dated Sat, 27 Nov 2021 21:50:00 + with message-id and subject line Bug#1000702: fixed in sonic-visualiser 4.4-2 has caused the Debian Bug report #1000702, regarding src:sonic-visualiser: fails to migrate to testing for too long: FTBFS on armel and mipsel to be marked as done.

Processed: Bug#996350 marked as pending in ruby-rabl

Processing control commands: > tag -1 pending Bug #996350 [src:ruby-rabl] ruby-rabl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) pending. -- 996350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996350 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#996350: marked as pending in ruby-rabl

Control: tag -1 pending Hello, Bug #996350 in ruby-rabl 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#997455: marked as done (snapd-glib: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Sat, 27 Nov 2021 21:18:53 + with message-id and subject line Bug#997455: fixed in snapd-glib 1.59-1 has caused the Debian Bug report #997455, regarding snapd-glib: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output

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

I guess so, I have both pipewire and pipewire-pulse in the output of ps Altgough I have no idea what that is for Il lun 22 nov 2021, 11:50 Sebastian Ramacher ha scritto: > Control: tags -1 moreinfo > > On 2021-11-21 00:55:50, Arnaldo Pirrone wrote: > > Package: jackd2 > > Version: 1.9.19~dfsg-2

Bug#1000702: marked as pending in sonic-visualiser

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

Processing control commands: > tag -1 pending Bug #1000702 [src:sonic-visualiser] src:sonic-visualiser: fails to migrate to testing for too long: FTBFS on armel and mipsel Added tag(s) pending. -- 1000702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000702 Debian Bug Tracking System

Bug#1000611: marked as done (libvtk9{,-qt}: soname change without library transition)

Your message dated Sat, 27 Nov 2021 20:49:51 + with message-id and subject line Bug#1000611: fixed in vtk9 9.1.0+really9.0.3+dfsg1-3 has caused the Debian Bug report #1000611, regarding libvtk9{,-qt}: soname change without library transition to be marked as done. This means that you claim

Processed: Re: ponyorm 3.10 additional details

Processing commands for cont...@bugs.debian.org: > retitle 1000716 ponyorm: FTBFS on Python 3.10 Bug #1000716 [src:ponyorm] python3-pony: fails on Python 3.10 with "ModuleNotFoundError: No module named 'parser'" Changed Bug title to 'ponyorm: FTBFS on Python 3.10' from 'python3-pony: fails on

Processed (with 1 error): Re: ponyorm 3.10 additional details

Processing commands for cont...@bugs.debian.org: > reassign 1000716 src:ponyorm Bug #1000716 [python3-pony] python3-pony: fails on Python 3.10 with "ModuleNotFoundError: No module named 'parser'" Bug reassigned from package 'python3-pony' to 'src:ponyorm'. No longer marked as found in versions

Bug#1000716: ponyorm 3.10 additional details

reassign 1000716 src:ponyorm rename 1000716 ponyorm: FTBFS on Python 3.10 thanks Oh well, it seems it does sys.exit(1) when trying to build the package, just not when running the testsuite by itself... I: pybuild base:237: python3.10 setup.py clean Sorry, but pony 0.7.14 requires Python of one

Processed: ponyorm 3.10 additional details

Processing commands for cont...@bugs.debian.org: > forwarded 1000716 https://github.com/ponyorm/pony/issues/598 Bug #1000716 [python3-pony] python3-pony: fails on Python 3.10 with "ModuleNotFoundError: No module named 'parser'" Set Bug forwarded-to-address to

Bug#1000255: marked as done (mpv: autopkgtest failures)

Your message dated Sat, 27 Nov 2021 19:49:03 + with message-id and subject line Bug#1000255: fixed in python-mpv 0.5.2-2 has caused the Debian Bug report #1000255, regarding mpv: autopkgtest failures to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: tagging 984371

Processing commands for cont...@bugs.debian.org: > tags 984371 + fixed Bug #984371 {Done: Adrian Bunk } [src:trafficserver] trafficserver: ftbfs with GCC-11 Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 984371:

Bug#1000717: supysonic: FTBFS on Python 3.10

Source: supysonic Version: 0.6.2+ds-4 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.10 supysonic FTBFS when using Python 3.10. This is caused by python3-pony not supporting Python 3.10 yet. === python3.10 === tests (unittest.loader._FailedTest) ... ERROR

Bug#1000716: python3-pony: fails on Python 3.10 with "ModuleNotFoundError: No module named 'parser'"

Package: python3-pony Version: 0.7.14-1 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.10 Hello, It seems the current version of ponyorm is broken on python3.10. If you look closely at the logs from the latest DebCI run [1], it outputs (without failing): >

Processed: glusterfs: diff for NMU version 10.0-1.3

Processing control commands: > tags 1000215 + patch Bug #1000215 [src:glusterfs] glusterfs: FTBFS on armel, armhf, mipsel Added tag(s) patch. > tags 1000215 + pending Bug #1000215 [src:glusterfs] glusterfs: FTBFS on armel, armhf, mipsel Added tag(s) pending. -- 1000215:

Bug#1000215: glusterfs: diff for NMU version 10.0-1.3

Control: tags 1000215 + patch Control: tags 1000215 + pending Dear maintainer, I've prepared an NMU for glusterfs (versioned as 10.0-1.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru

Bug#1000237: marked as done (pygame: FTBFS with python3.10)

Your message dated Sat, 27 Nov 2021 19:17:32 + with message-id <2ae5befc-4649-5a47-0b23-4edf7b338...@debian.org> and subject line pygame: FTBFS with python3.10 has caused the Debian Bug report #1000237, regarding pygame: FTBFS with python3.10 to be marked as done. This means that you claim

Processed: tagging 996380

Processing commands for cont...@bugs.debian.org: > # https://github.com/paolobrasolin/safe_yaml/compare/master...development > tags 996380 + patch Bug #996380 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) patch. > thanks

Bug#1000255: mpv: autopkgtest failures

On 2021-11-23 15 h 22, Sebastian Ramacher wrote: > Control: reassign -1 src:python-mpv 0.5.2-1 > Control: forwarded -1 https://github.com/jaseg/python-mpv/issues/187 > > On 2021-11-21 23:21:24, Sebastian Ramacher wrote: >> Control: tags -1 help >> >> On 2021-11-20 09:34:37 +0100, Gianfranco

Bug#998682: marked as done (libgetdata: b-d on python3-all-dev, but not built for all supported Python3 versions)

Your message dated Sat, 27 Nov 2021 19:03:31 + with message-id and subject line Bug#998682: fixed in libgetdata 0.11.0-2 has caused the Debian Bug report #998682, regarding libgetdata: b-d on python3-all-dev, but not built for all supported Python3 versions to be marked as done. This means

Processed: bug 996380 is forwarded to https://github.com/dtao/safe_yaml/issues/100

Processing commands for cont...@bugs.debian.org: > forwarded 996380 https://github.com/dtao/safe_yaml/issues/100 Bug #996380 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Set Bug forwarded-to-address to

Bug#997177: marked as done (pacvim: FTBFS: src/game.cpp:237:15: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Sat, 27 Nov 2021 17:03:37 + with message-id and subject line Bug#997177: fixed in pacvim 1.1.1-1.1 has caused the Debian Bug report #997177, regarding pacvim: FTBFS: src/game.cpp:237:15: error: format not a string literal and no format arguments [-Werror=format-security]

Processed: Re: statsmodels FTBFS - tests fail

Processing control commands: > forwarded -1 https://github.com/statsmodels/statsmodels/issues/7911 Bug #997081 [src:statsmodels] statsmodels: FTBFS: tests fail Set Bug forwarded-to-address to 'https://github.com/statsmodels/statsmodels/issues/7911'. -- 997081:

Bug#996878: closed by Debian FTP Masters (reply to Thomas Andrejak ) (Bug#996878: fixed in libprelude 5.2.0-5)

Hi, Thanks for this fix ! I'll test it as soon as the compiled package enters unstable. Cheers, François Le 27/11/2021 à 10:39, Debian Bug Tracking System a écrit : > This is an automatic notification regarding your Bug report > which was filed against the python3-prelude package: > >

Bug#995475: marked as done (bash-static: segfault on startup when running with glibc 2.32)

Your message dated Sat, 27 Nov 2021 17:09:29 +0100 with message-id and subject line fixed has caused the Debian Bug report #995475, regarding bash-static: segfault on startup when running with glibc 2.32 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: tagging 997389

Processing commands for cont...@bugs.debian.org: > tags 997389 + pending Bug #997389 [src:xrdesktop] xrdesktop: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 997389:

Bug#1000701: marked as done (node-mdn-data: Wrong license, package is covered by CC-1.0, not MPL-2.0)

Your message dated Sat, 27 Nov 2021 15:04:39 + with message-id and subject line Bug#1000701: fixed in node-mdn-data 2.0.23-3 has caused the Debian Bug report #1000701, regarding node-mdn-data: Wrong license, package is covered by CC-1.0, not MPL-2.0 to be marked as done. This means that you

Bug#1000701: marked as pending in node-css-tree

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

Processing control commands: > tag -1 pending Bug #1000701 {Done: Yadd } [src:node-mdn-data] node-mdn-data: Wrong license, package is covered by CC-1.0, not MPL-2.0 Added tag(s) pending. -- 1000701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000701 Debian Bug Tracking System Contact

Processed: Bug#1000701 marked as pending in node-mdn-data

Processing control commands: > tag -1 pending Bug #1000701 [src:node-mdn-data] node-mdn-data: Wrong license, package is covered by CC-1.0, not MPL-2.0 Added tag(s) pending. -- 1000701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000701 Debian Bug Tracking System Contact

Bug#1000701: marked as pending in node-mdn-data

Control: tag -1 pending Hello, Bug #1000701 in node-mdn-data 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#1000702: src:sonic-visualiser: fails to migrate to testing for too long: FTBFS on armel and mipsel

Source: sonic-visualiser Version: 4.2-1 Severity: serious Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a

Bug#1000701: node-mdn-data: Wrong license, package is covered by CC-1.0, not MPL-2.0

Source: node-mdn-data Version: 2.0.23-1 Severity: serious Justification: Policy 2.3 debian/copyright is wrong, package is covered by CC-1.0-Universal, not MPL-2.0

Processed: Re: Bug#996154: obexftp: FTBFS: ld: final link failed: bad value

Processing control commands: > reassign -1 libopenobex2-dev 1.7.2-2 Bug #996154 [src:obexftp] obexftp: FTBFS with ruby3.0: ld: final link failed: bad value Bug reassigned from package 'src:obexftp' to 'libopenobex2-dev'. No longer marked as found in versions obexftp/0.24-6. Ignoring request to

Bug#996154: obexftp: FTBFS: ld: final link failed: bad value

Control: reassign -1 libopenobex2-dev 1.7.2-2 Control: retitle -1 libopenobex2-dev: openobex-target-release.cmake forces static linking Control: affects -1 src:obexftp Control: tags -1 patch On Mon, Oct 11, 2021 at 10:33:44AM -0300, Antonio Terceiro wrote: >... > Relevant part (hopefully): > >

Bug#992927: marked as done (mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug)

Your message dated Sat, 27 Nov 2021 12:53:55 + with message-id and subject line Bug#992927: fixed in mutt 2.1.3-1 has caused the Debian Bug report #992927, regarding mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug to be marked as done. This means that you claim that the

Processed: some aiohttp rdeps affected by the failure to import

Processing commands for cont...@bugs.debian.org: > affects 1000680 + python3-matrix-nio weechat-matrix Bug #1000680 [python3-aiohttp] python3-aiohttp: fails to import, "TypeError: function() argument 'code' must be code, not str" Added indication that 1000680 affects python3-matrix-nio and

Processed: your mail

Processing commands for cont...@bugs.debian.org: > notfound 999606 fetchmail/6.4.23-1 Bug #999606 [fetchmail] fetchmail: configuration requires TLS for SSH authentication Ignoring request to alter found versions of bug #999606 to the same values previously set > End of message, stopping

Processed: your mail

Processing commands for cont...@bugs.debian.org: > notfound 999606 fetchmail/6.4.24-1 Bug #999606 [fetchmail] fetchmail: configuration requires TLS for SSH authentication Ignoring request to alter found versions of bug #999606 to the same values previously set > End of message, stopping

Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug

On Tue, Nov 23, 2021 at 12:36:07PM -0800, Kevin J. McCarthy wrote: > On Tue, Nov 23, 2021 at 08:45:47PM +0100, Hannes von Haugwitz wrote: > > Is there any progress with this bug? > > Mutt 2.1.3 included the corrected sort commit referenced in my last email. > So, for unstable/testing it would be

Processed: cloning 1000560, reassign -1 to php-laravel-lumen-framework

Processing commands for cont...@bugs.debian.org: > clone 1000560 -1 Bug #1000560 [php-laravel-framework] Compatibility with Symfony 5 Bug 1000560 cloned as bug 1000696 > reassign -1 php-laravel-lumen-framework 6.3.5-2 Bug #1000696 [php-laravel-framework] Compatibility with Symfony 5 Bug

Bug#1000289: marked as done (mbedtls: enabling CMAC support changes ABI)

Your message dated Sat, 27 Nov 2021 12:33:13 +0100 with message-id <777e2704-004d-4364-ec73-036e729cd...@debian.org> and subject line Re: shadowsocks-libev: autopkgtest failing on Testing after updating mbedtls has caused the Debian Bug report #1000289, regarding mbedtls: enabling CMAC support

Processed: Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

Processing commands for cont...@bugs.debian.org: > tag 1000146 pending Bug #1000146 [cppcheck] cppcheck: incorrect dependencies: libc6 should be >= 2.32 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000146:

Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

The root case of the problem has now been identified (see bug #100421). I'll upload a new version cppcheck with a workaround shortly (and before the autoremoval kicks in) -- just wanting to wait a bit more for a potential new upstream release. Best regards, Joachim

Bug#995843: marked as done (abook: missing licenses in d/copyright)

Your message dated Sat, 27 Nov 2021 10:33:29 + with message-id and subject line Bug#995843: fixed in abook 0.6.1-2 has caused the Debian Bug report #995843, regarding abook: missing licenses in d/copyright to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Bug#999522 marked as pending in brian

Processing control commands: > tag -1 pending Bug #999522 [src:brian] brian: FTBFS with numpy 1.21 (in experimental): TypeError: logical_and() takes from 2 to 3 positional arguments but 1 were given Added tag(s) pending. -- 999522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999522

Bug#999522: marked as pending in brian

Control: tag -1 pending Hello, Bug #999522 in brian 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#996878: marked as done (python3-prelude: python3 import prelude throws an ImportError exception)

Your message dated Sat, 27 Nov 2021 09:34:44 + with message-id and subject line Bug#996878: fixed in libprelude 5.2.0-5 has caused the Debian Bug report #996878, regarding python3-prelude: python3 import prelude throws an ImportError exception to be marked as done. This means that you claim

Processed: severity of 996878 is serious

Processing commands for cont...@bugs.debian.org: > severity 996878 serious Bug #996878 [python3-prelude] python3-prelude: python3 import prelude throws an ImportError exception Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1000611: libvtk9{,-qt}: soname change without library transition

Hi Anton, * Anton Gladky [2021-11-25 22:07]: thanks for the bug report. It was really an accidental upload into unstable instead of experimental. Yes, I will rename the package and upload it ASAP. What about uploading the old 9.0.3+dfsg1-3 as 9.1.0+really9.0.3+dfsg1-3 in the meantime to fix

Processed: python-django-modelcluster: autopkgtest fails with django-taggit >= 2.0.0

Processing control commands: > found -1 python-django-modelcluster/5.2-1 Bug #1000684 [src:python-django-modelcluster] python-django-modelcluster: autopkgtest fails with django-taggit >= 2.0.0 Ignoring request to alter found versions of bug #1000684 to the same values previously set --

Bug#1000684: python-django-modelcluster: autopkgtest fails with django-taggit >= 2.0.0

Source: python-django-modelcluster Version: 5.2-1 Severity: serious Control: found -1 python-django-modelcluster/5.2-1 Dear Maintainer, the autopkgtesting is failing since the upload of python3-django-taggit 2.0.0-1 but was working with versions of python3-django-taggit less than this version.