Bug#977824: php-imagick: diff for NMU version 3.4.4-4.2

2020-12-28 Thread David Prévot
Control: tags 977824 + pending Dear maintainer, I've prepared an NMU for php-imagick (versioned as 3.4.4-4.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. The patch is also available as a pull request on salsa:

Processed: php-imagick: diff for NMU version 3.4.4-4.2

2020-12-28 Thread Debian Bug Tracking System
Processing control commands: > tags 977824 + pending Bug #977824 [php-imagick] CI fails with PHPUnit 9 Ignoring request to alter tags of bug #977824 to the same tags previously set -- 977824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977824 Debian Bug Tracking System Contact

Bug#946265: marked as done (New version available fixing build with python 3.8)

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 13:34:59 + with message-id and subject line Bug#946265: fixed in pympler 0.9+dfsg1-1 has caused the Debian Bug report #946265, regarding New version available fixing build with python 3.8 to be marked as done. This means that you claim that the problem has

Bug#968589: PPP name resolver service not restarted upon upgrade

2020-12-28 Thread Chris Boot
Control: severity -1 normal On 10/09/2020 15:39, 積丹尼 Dan Jacobson wrote: > Bug still affecting several of my machines. Forwarding to > https://github.com/systemd/systemd/issues/17004 . I don't know why you think this bug is 'grave'. This does not make your system unusable (and you've found a

Processed: Re: Bug#968589: PPP name resolver service not restarted upon upgrade

2020-12-28 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #968589 [ppp] ppp needs to be updated to work with systemd-resolved Bug #970076 [ppp] ppp needs to be updated to work with systemd-resolved Severity set to 'normal' from 'grave' Severity set to 'normal' from 'grave' -- 968589:

Bug#978282: marked as done (bidict: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 13:33:26 + with message-id and subject line Bug#978282: fixed in bidict 0.21.2-2 has caused the Debian Bug report #978282, regarding bidict: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as done. This

Processed: limit source to php-imagick, tagging 977824

2020-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source php-imagick Limiting to bugs with field 'source' containing at least one of 'php-imagick' Limit currently set to 'source':'php-imagick' > tags 977824 + pending Bug #977824 [php-imagick] CI fails with PHPUnit 9 Added tag(s) pending.

Bug#973796: marked as done (zeek: FTBFS error: 'IntrusivePtr','EnumType' in namespace 'zeek' does not name a template type)

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 14:23:25 +0100 with message-id <8735zqqd2q@msgid.hilluzination.de> and subject line Fixed in 3.2.3+ds1-1 has caused the Debian Bug report #973796, regarding zeek: FTBFS error: 'IntrusivePtr','EnumType' in namespace 'zeek' does not name a template type to be

Bug#978509: marked as done (clasp: non-standard gcc/g++ used for build (gcc-9))

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 13:04:30 + with message-id and subject line Bug#978509: fixed in clasp 3.3.5-4 has caused the Debian Bug report #978509, regarding clasp: non-standard gcc/g++ used for build (gcc-9) to be marked as done. This means that you claim that the problem has been

Bug#957949: marked as done (wmnut: ftbfs with GCC-10)

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 13:05:24 + with message-id and subject line Bug#957949: fixed in wmnut 0.66-2 has caused the Debian Bug report #957949, regarding wmnut: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: Re: python-typing-extensions included in CPython, should not ship

2020-12-28 Thread Debian Bug Tracking System
Processing control commands: > severity -1 wishlist Bug #978536 [src:python-typing-extensions] python-typing-extensions included in CPython, should not ship Severity set to 'wishlist' from 'serious' -- 978536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978536 Debian Bug Tracking System

Bug#978536: python-typing-extensions included in CPython, should not ship

2020-12-28 Thread Michael R. Crusoe
control: severity -1 wishlist On Mon, 28 Dec 2020 13:02:31 +0100 Matthias Klose wrote: > python-typing-extensions is included in CPython since 3.5, it should not ship > with bullseye, but the typing module be used instead. CPython does not provide a module name "typing_extensions" and many

Processed: your mail

2020-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 978427 978419 Bug #978427 [ppp] ppp: Updates create a copy of /lib/systemd/system/pppd-dns.service and dangling symlink Bug #978419 [ppp] enablement symlinks are not cleaned up on upgrades Severity set to 'serious' from 'normal'

Bug#978536: python-typing-extensions included in CPython, should not ship

2020-12-28 Thread Matthias Klose
Package: src:python-typing-extensions Version: 3.7.4.3-1 Severity: serious Tags: sid bullseye python-typing-extensions is included in CPython since 3.5, it should not ship with bullseye, but the typing module be used instead.

Bug#973848: security update of chromium in Debian stable?

2020-12-28 Thread Jan Luca Naumann
Hey, I have got a successful buster build half an hour ago :) As soon as [1] is fixed or at least worked around (so we do not release a version with a regression), I think we could do the update. I will contact the security team now to discuss the update. Best, Jan [1]

Bug#978258: marked as done (taskw: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 11:52:40 + with message-id and subject line Bug#978258: fixed in taskw 1.3.0-1 has caused the Debian Bug report #978258, regarding taskw: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13 to be marked as done. This

Bug#978253: marked as done (bugwarrior: FTBFS: ValueError: badly formed hexadecimal UUID string)

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 11:52:40 + with message-id and subject line Bug#978258: fixed in taskw 1.3.0-1 has caused the Debian Bug report #978258, regarding bugwarrior: FTBFS: ValueError: badly formed hexadecimal UUID string to be marked as done. This means that you claim that the

Bug#978258: marked as done (taskw: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 11:52:40 + with message-id and subject line Bug#978253: fixed in taskw 1.3.0-1 has caused the Debian Bug report #978253, regarding taskw: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13 to be marked as done. This

Bug#978253: marked as done (bugwarrior: FTBFS: ValueError: badly formed hexadecimal UUID string)

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 11:52:40 + with message-id and subject line Bug#978253: fixed in taskw 1.3.0-1 has caused the Debian Bug report #978253, regarding bugwarrior: FTBFS: ValueError: badly formed hexadecimal UUID string to be marked as done. This means that you claim that the

Bug#973848: security update of chromium in Debian stable?

2020-12-28 Thread Tomas Pospisek
Hi Jan Luca, are you working on or respectively are you planing to do the stable build? (I am not sure if I would be able to get access to a powerful enough machine to do the build and get up to speed within reasonable time on how to build chromium and on how to do it efficiently so that I do

Bug#978100: marked as done (libreoffice-parlatype: missing Breaks+Replaces: parlatype-libreoffice-helpers (<< 2))

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 11:19:23 + with message-id and subject line Bug#978100: fixed in parlatype-libreoffice-extension 2.1-2 has caused the Debian Bug report #978100, regarding libreoffice-parlatype: missing Breaks+Replaces: parlatype-libreoffice-helpers (<< 2) to be marked as

Processed: update pending

2020-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 844770 + pending Bug #844770 [xz-utils] xzcmp: SIGPIPE is raised because CMP does exit while the XZ commands are still writing to the pipe Added tag(s) pending. > tags 894454 + pending Bug #894454 [xz-utils] xz.1: Some tidying of the manual

Bug#977657: marked as done (swi-prolog: FTBFS with OpenSSL 1.1.1i)

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 10:49:43 + with message-id and subject line Bug#977657: fixed in swi-prolog 8.2.3+dfsg-3 has caused the Debian Bug report #977657, regarding swi-prolog: FTBFS with OpenSSL 1.1.1i to be marked as done. This means that you claim that the problem has been

Bug#978489: QML QtQuick dependencies

2020-12-28 Thread Bernhard Schmidt
Hi, I've recently packaged a QML based application (linphone-desktop) and I have been hit with a couple of missing qml-module-* dependencies in the resulting binary package which caused RC bugs. The latest one (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978489) I cannot even reproduce

Bug#978209: mrpt: FTBFS: mainwindow.h:218:2: error: reference to ‘Tracker’ is ambiguous

2020-12-28 Thread José Luis Blanco-Claraco
Thanks Lucas for reporting. This seems to be an issue detected with gcc 10.2.1, since I tried with the exact opencv version 4.5.1 and both gcc 7.5 and 10.2.0 and it didn't complain about that ambiguity. I'll try to install gcc 10.2.1 to verify this. Best, JL

Processed: raise severity, trying to remove GCC 9 from bullseye

2020-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 978509 serious Bug #978509 [clasp] clasp: non-standard gcc/g++ used for build (gcc-9) Severity set to 'serious' from 'important' > severity 978510 serious Bug #978510 [eso-midas] eso-midas: non-standard gcc/g++ used for build (gcc-9)

Bug#978489: missing dependency on qml-module-qtquick-controls

2020-12-28 Thread Bernhard Schmidt
Control: tags -1 + pending Hi Marco, Am 28.12.20 um 01:00 schrieb Marco d'Itri: > Package: linphone-desktop > Version: 4.2.5-2 > Severity: grave > > Or else linphone will crash with: > > [00:50:46:566][0x5618e548aed0][Info]app/App.cpp:784: "Open Linphone app." >

Processed: Re: Bug#978489: missing dependency on qml-module-qtquick-controls

2020-12-28 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #978489 [linphone-desktop] missing dependency on qml-module-qtquick-controls Added tag(s) pending. -- 978489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#978522: ospd-openvas' autopkg tests fail

2020-12-28 Thread Matthias Klose
Package: src:ospd-openvas Version: 20.8.0-1 Severity: serious Tags: sid bullseye ospd-openvas' autopkg tests fail, blocking migration of setuptools. == ERROR: test_get_openvas_timestamp_scan_host_end

Processed: tagging 973096

2020-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 973096 + patch Bug #973096 [src:python-bleach] python-bleach: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13 Added tag(s) patch. > thanks Stopping processing here. Please

Bug#977900: marked as done (node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path')

2020-12-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Dec 2020 09:03:22 + with message-id and subject line Bug#977900: fixed in node-autoprefixer 10.1.0.0+dfsg1+~cs14.1.12-2 has caused the Debian Bug report #977900, regarding node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path' to be marked as

Bug#911587: infnoise: busy-waits, using too much CPU

2020-12-28 Thread Axel Beckert
Hi Stephen, Stephen Kitt wrote: > Dear Maintainer, You're writing to yourself as "Dear Maintainer"? :-) > Version 0.3 of infnoise busy-waits; 0.2.6 didn’t, so this is a > regression. Any news on this? I just dist-upgraded a box which has a Infinite Noise TRNG connected from Buster to Bullseye

<    1   2