Processed (with 2 errors): Re: Bug#943401: libreoffice: Autopkgtests are failing since 2019-10-21

Processing commands for cont...@bugs.debian.org: > retitle 943401 C++ Unit tests failing (Failure instantiating protector Bug #943401 [src:libreoffice] libreoffice: Autopkgtests are failing since 2019-10-21 Changed Bug title to 'C++ Unit tests failing (Failure instantiating protector' from

Bug#943438: marked as done (src:icinga2: Please update/remove libwxgtk3.0-dev build-dependency)

Your message dated Fri, 25 Oct 2019 05:34:00 + with message-id and subject line Bug#943438: fixed in icinga2 2.11.1-2 has caused the Debian Bug report #943438, regarding src:icinga2: Please update/remove libwxgtk3.0-dev build-dependency to be marked as done. This means that you claim that

Bug#943440: marked as done (src:grass: Please update/remove libwxgtk3.0-dev build-dependency)

Your message dated Fri, 25 Oct 2019 05:19:13 + with message-id and subject line Bug#943440: fixed in grass 7.8.0-2 has caused the Debian Bug report #943440, regarding src:grass: Please update/remove libwxgtk3.0-dev build-dependency to be marked as done. This means that you claim that the

Processed: Re: [Pkg-nagios-devel] Bug#943438: src:icinga2: Please update/remove libwxgtk3.0-dev build-dependency

Processing control commands: > tags -1 pending Bug #943438 [src:icinga2] src:icinga2: Please update/remove libwxgtk3.0-dev build-dependency Added tag(s) pending. -- 943438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943438 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#943438: [Pkg-nagios-devel] Bug#943438: src:icinga2: Please update/remove libwxgtk3.0-dev build-dependency

Control: tags -1 pending On 10/24/19 9:36 PM, Olly Betts wrote: > However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that > your package has a build-dependency on libwxgtk3.0-dev which doesn't > result in any shlib dependencies in the built packages. If this package > is not

Bug#943440: src:grass: Please update/remove libwxgtk3.0-dev build-dependency

Control: tags -1 pending On 10/24/19 9:24 PM, Olly Betts wrote: > However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that > your package has a build-dependency on libwxgtk3.0-dev which doesn't > result in any shlib dependencies in the built packages. If this package > is not

Processed: Re: Bug#943440: src:grass: Please update/remove libwxgtk3.0-dev build-dependency

Processing control commands: > tags -1 pending Bug #943440 [src:grass] src:grass: Please update/remove libwxgtk3.0-dev build-dependency Added tag(s) pending. -- 943440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943440 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#927747: [Pkg-samba-maint] Bug#927747: bind9_dlz backend is entirely broken in Debian

I would like to add my observations on this bug after upgrading from stretch to 10.1. The apparmor fixes seem OK so far. My samba system was originally created by moving a samba-3 system from CentOS 6 to Debian 9 and then using the samba tools to migrate to an ad-dc system. I mention this,

Bug#943462: [polkit-kde-agent-1] Fails to start with elogind

Package: polkit-kde-agent-1 Version: 4:5.14.5-1 Severity: serious --- Please enter the report below this line. --- I'm using elogind 239.3+20190131-1+debian1 and the agent fails to start at the kde launch with the following diagnostics: === New PolkitAgentListener 0xbfaf9ca0 Adding new

Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

On Thu, Oct 24, 2019 at 10:12:08PM +0100, Olly Betts wrote: > On Fri, Oct 25, 2019 at 12:02:11AM +0300, Jussi Pakkanen wrote: > > https://mentors.debian.net/package/meson > > > > Feel free to upload it to the archive. > > Thanks for the quick response. Building now. It seems this package

Bug#942674: marked as done (git: FTBFS on big-endian targets - testsuite failure)

Your message dated Fri, 25 Oct 2019 00:49:17 + with message-id and subject line Bug#942674: fixed in git 1:2.24.0~rc1-1 has caused the Debian Bug report #942674, regarding git: FTBFS on big-endian targets - testsuite failure to be marked as done. This means that you claim that the problem

Bug#943439: marked as done (src:asc: Please update/remove libwxgtk3.0-dev build-dependency)

Your message dated Thu, 24 Oct 2019 22:04:21 + with message-id and subject line Bug#943439: fixed in asc 2.6.1.0-6 has caused the Debian Bug report #943439, regarding src:asc: Please update/remove libwxgtk3.0-dev build-dependency to be marked as done. This means that you claim that the

Bug#942768: marked as done (lcl-units-2.0: file conflict with lazarus-src-2.0 (versin 2.0.2+dfsg-5))

Your message dated Thu, 24 Oct 2019 22:05:40 + with message-id and subject line Bug#942768: fixed in lazarus 2.0.2+dfsg-7 has caused the Debian Bug report #942768, regarding lcl-units-2.0: file conflict with lazarus-src-2.0 (versin 2.0.2+dfsg-5) to be marked as done. This means that you

Bug#943439: src:asc: Please update/remove libwxgtk3.0-dev build-dependency

Hi Olly, Am 24.10.19 um 21:31 schrieb Olly Betts: > Package: src:asc > Version: 2.6.1.0-5 > Severity: serious > Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition [...] Thanks for reporting. I have uploaded a new revision of asc that uses libwxgtk3.0-gtk3-dev instead of

Bug#943439: marked as pending in asc

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

Processing control commands: > tag -1 pending Bug #943439 [src:asc] src:asc: Please update/remove libwxgtk3.0-dev build-dependency Added tag(s) pending. -- 943439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

Control: tags -1 +pending On Fri, Oct 25, 2019 at 12:02:11AM +0300, Jussi Pakkanen wrote: > On Thu, Oct 24, 2019 at 11:03 PM Olly Betts wrote: > > > However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that > > your package has a build-dependency on libwxgtk3.0-dev which doesn't >

Processed: Re: Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

Processing control commands: > tags -1 +pending Bug #943437 [src:meson] src:meson: Please update/remove libwxgtk3.0-dev build-dependency Added tag(s) pending. -- 943437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943437 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

On Thu, Oct 24, 2019 at 11:03 PM Olly Betts wrote: > However, checking "dak rm -Rn -b libwxgtk3.0-dev" on coccia I see that > your package has a build-dependency on libwxgtk3.0-dev which doesn't > result in any shlib dependencies in the built packages. If this package > is not actually used

Bug#943447: the autopkg test calls python instead of python2

Package: src:gexiv Version: 0.10.9-1 Severity: serious Tags: sid bullseye patch the autopkg test calls python instead of python2. This will make the package fail the next binNMU when adding python3.8 support. http://launchpadlibrarian.net/448276453/gexiv2_0.10.9-1_0.10.9-1ubuntu1.diff.gz

Bug#943446: the autopkg test calls python instead of python2

Package: src:last-align Version: 983-1 Severity: serious Tags: sid bullseye patch the autopkg test calls python instead of python2. This will make the package fail the next binNMU when adding python3.8 support. http://launchpadlibrarian.net/448278213/last-align_983-1_983-1ubuntu1.diff.gz

Bug#943445: the autopkg test calls python instead of python2

Package: src:python-fann2 Version: 1:1.1.2+ds-1 Severity: serious Tags: sid bullseye patch the autopkg test calls python instead of python2. This will make the package fail the next binNMU when adding python3.8 support.

Bug#943444: the autopkg test calls python instead of python2

Package: src:tlsh Version: 3.4.4+20151206-1.1 Severity: serious Tags: sid bullseye patch the autopkg test calls python instead of python2. This will make the package fail the next binNMU when adding python3.8 support.

Bug#941537: Merge request

control: tag -1 pending Am 24.10.19 um 20:35 schrieb Adrian Heine: > I opened a merge request: > https://salsa.debian.org/debian/lilypond/merge_requests/1 Merged, thanks. Regards, Tobias signature.asc Description: OpenPGP digital signature

Processed: Re: Merge request

Processing control commands: > tag -1 pending Bug #941537 [lilypond] lilypond: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended Added tag(s) pending. -- 941537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941537 Debian Bug Tracking System Contact

Processed: block 894663 with 943437 943438 943439 943440

Processing commands for cont...@bugs.debian.org: > block 894663 with 943437 943438 943439 943440 Bug #894663 [release.debian.org] transition: wxwidgets3.0-gtk3 894663 was blocked by: 934099 933415 933454 933430 933447 933452 933463 933423 933434 933436 933432 933426 933455 933469 933445 895134

Bug#943439: src:asc: Please update/remove libwxgtk3.0-dev build-dependency

Package: src:asc Version: 2.6.1.0-5 Severity: serious Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition According to the transition tracker, the wxwidgets3.0-gtk3 transition is 96% and the only remaining blockers are a missing mips64el build of codelite (currently building)

Bug#943440: src:grass: Please update/remove libwxgtk3.0-dev build-dependency

Package: src:grass Version: 7.8.0-1 Severity: serious Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition According to the transition tracker, the wxwidgets3.0-gtk3 transition is 96% and the only remaining blockers are a missing mips64el build of codelite (currently building)

Bug#943438: src:icinga2: Please update/remove libwxgtk3.0-dev build-dependency

Package: src:icinga2 Version: 2.11.1-2~exp1 Severity: serious Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition According to the transition tracker, the wxwidgets3.0-gtk3 transition is 96% and the only remaining blockers are a missing mips64el build of codelite (currently

Bug#943437: src:meson: Please update/remove libwxgtk3.0-dev build-dependency

Package: src:meson Version: 0.52.0-1 Severity: serious Justification: blocks the almost-complete wxwidgets3.0-gtk3 transition According to the transition tracker, the wxwidgets3.0-gtk3 transition is 96% and the only remaining blockers are a missing mips64el build of codelite (currently building)

Bug#943396: FTBFS on armhf: testsuite segfault

On Thu, 24 Oct 2019 13:13:43 +0100 Iain Lane wrote: > Package: src:fftw3 > Version: 3.3.8-2 > We found this in an Ubuntu test rebuild, but I just confirmed on > harris.d.o: Is this reproducible in buster, too, or limited to sid/bullseye? Andreas

Processed: tagging 943372, tagging 943410, tagging 943394

Processing commands for cont...@bugs.debian.org: > tags 943372 + sid bullseye Bug #943372 [scim] Can not active scim after Debian testing upgrade on 10 Oct 2019 Added tag(s) bullseye and sid. > tags 943410 + experimental Bug #943410 [src:xapian-bindings] autopkg test calls python instead of

Processed: [bts-link] source package ibus

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

Bug#942533: marked as done (sardana: needs a source-only upload.)

Your message dated Thu, 24 Oct 2019 18:41:22 + with message-id and subject line has caused the Debian Bug report #942533, regarding sardana: needs a source-only upload. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#941537: Merge request

I opened a merge request: https://salsa.debian.org/debian/lilypond/merge_requests/1 signature.asc Description: OpenPGP digital signature

Processed: py2removal blocks updates - 2019-10-24 18:36:20.581302+00:00

Processing commands for cont...@bugs.debian.org: > # Part of the effort for the removal of python from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # ldtp > block 933025 by 936833 Bug #933025 [src:ldtp] ldtp: Porting to

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

[ sent again with ASCII-only headers to please Debian mail servers ] Quoting Jérémy Lal (2019-10-24 19:47:48) > Le jeu. 24 oct. 2019 à 19:33, Jonas Smedegaard a écrit : > > > Quoting Pirate Praveen (2019-10-24 19:12:22) > > > > > > > > > On Thu, Oct 24, 2019 at 19:05, Jonas Smedegaard wrote: >

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

Le jeu. 24 oct. 2019 à 19:33, Jonas Smedegaard a écrit : > Quoting Pirate Praveen (2019-10-24 19:12:22) > > > > > > On Thu, Oct 24, 2019 at 19:05, Jonas Smedegaard wrote: > > > Quoting Pirate Praveen (2019-10-24 18:42:17) > > >> On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard > >>

Bug#943389: [Pkg-javascript-devel] Bug#943389: Bug#943389: node-lodash: source package does not contain upstream source

Le 24 octobre 2019 19:12:22 GMT+02:00, Pirate Praveen a écrit : > > >On Thu, Oct 24, 2019 at 19:05, Jonas Smedegaard wrote: >> Quoting Pirate Praveen (2019-10-24 18:42:17) >>> On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard >> > wrote: >>> > Quoting Pirate Praveen

Bug#934599: Pricing needed

Good day, Can you please provide me with quote for the below. 7 HP 651A Magenta Original LaserJet Toner Cartridge, CE343A Original Microsoft Surface Book 2 MFR #: HN6-1 x 9 Thank you Jerry Wilson Director of Purchasing Contemporary Plan 2741 W 21st St, Erie, PA 16506 814 208 9313

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

Quoting Pirate Praveen (2019-10-24 19:12:22) > > > On Thu, Oct 24, 2019 at 19:05, Jonas Smedegaard wrote: > > Quoting Pirate Praveen (2019-10-24 18:42:17) > >> On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard >> > wrote: > >> > Quoting Pirate Praveen (2019-10-24

Bug#943428: autopkg test calls python instead of python2

Package: src:pygobject Version: 3.34.0-1 Severity: serious Tags: sid bullseye patch the autopkg test calls python instead of python2. This will make the package fail the next binNMU when adding python3.8 support. And it's probably too early to remove the python package.

Bug#943427: autopkg test calls python instead of python2

Package: src:fast5 Version: 0.6.5-2 Severity: serious Tags: sid bullseye patch the autopkg test calls python instead of python2. This will make the package fail the next binNMU when adding python3.8 support. And it's probably too early to remove the python package.

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

On Thu, Oct 24, 2019 at 19:05, Jonas Smedegaard wrote: Quoting Pirate Praveen (2019-10-24 18:42:17) On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard > wrote: > Quoting Pirate Praveen (2019-10-24 15:34:15) >> All files derived from source have their corresponding

Bug#943424: Plymouth prevents clean shutdown in some cases, which may result in data loss

Package: plymouth Version: 0.9.4-1.1 Severity: grave Justification: may result in data loss Hi, I've noticed that when using offline-updates[1], remounting the root filesystem read-only at shutdown fails with 'Device or resource busy' (see the attached screenshot). As the result, the filesystem

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

Quoting Pirate Praveen (2019-10-24 18:42:17) > On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard wrote: > > Quoting Pirate Praveen (2019-10-24 15:34:15) > >> All files derived from source have their corresponding source code > >> and it is regenerated during build. > > > > It may very well be

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard wrote: Quoting Pirate Praveen (2019-10-24 15:34:15) On Thu, Oct 24, 2019 at 11:40, Jonas Smedegaard > wrote: > The source package src:node-lodash states in its debian/copyright > file that its upstream source is

Processed: py2removal blocks updates - 2019-10-24 16:36:29.947841+00:00

Processing commands for cont...@bugs.debian.org: > # Part of the effort for the removal of python from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # ldtp > block 933025 by 936833 Bug #933025 [src:ldtp] ldtp: Porting to

Processed: Re: [Tts-project] Bug#943402: festival: calling festival --tts or text2wave aborts

Processing control commands: > reassign -1 festlex-ifd Bug #943402 [festival] festival: calling festival --tts or text2wave aborts Bug reassigned from package 'festival' to 'festlex-ifd'. No longer marked as found in versions festival/1:2.5.0-4. Ignoring request to alter fixed versions of bug

Processed: block 938718 with 943409, block 943409 with 941722

Processing commands for cont...@bugs.debian.org: > block 938718 with 943409 Bug #938718 [src:translate-toolkit] translate-toolkit: Python2 removal in sid/bullseye 938718 was blocked by: 938781 938718 was blocking: 936196 936289 936973 937410 937422 937558 937598 937695 937700 937834 937875

Bug#943412: the autopkg test calls python instead of python2

Package: src:pysvn Version: 1.9.9-1 Severity: serious Tags: sid bullseye patch the autopkg test calls python instead of python2. This will make the package fail the next binNMU when adding python3.8 support. And it's probably too early to remove the python package. patch at

Bug#943357: marked as done (mypy, python3-mypy: Both ship /usr/bin/dmypy)

Your message dated Thu, 24 Oct 2019 15:22:09 + with message-id and subject line Bug#943357: fixed in mypy 0.740-2 has caused the Debian Bug report #943357, regarding mypy, python3-mypy: Both ship /usr/bin/dmypy to be marked as done. This means that you claim that the problem has been dealt

Bug#943409: python3-cheroot: Missing dependency on python3-jaraco.functools

Package: python3-cheroot Version: 8.2.1+ds-1 Severity: serious Justification: Policy 3.5 Packages must specify their dependencies Dear Maintainer, python3-cheroot appears to have grown a dependency on jaraco.functools; python3-jaraco.functools versio 2.0-1 is in the NEW queue. $ python3 -c

Bug#943410: autopkg test calls python instead of python2

Package: src:xapian-bindings Version: 1.4.11-2 Severity: serious Tags: sid bullseye patch the autopkg test calls python instead of python2. This will make the package fail the next binNMU when adding python3.8 support. And it's probably too early to remove the python package.

Bug#935300: marked as done (rsyslog: FTBFS on s390x)

Your message dated Thu, 24 Oct 2019 14:57:50 + with message-id and subject line Bug#935300: fixed in rsyslog 8.1910.0-2 has caused the Debian Bug report #935300, regarding rsyslog: FTBFS on s390x to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#927481: marked as done (.help fails with "Sorry! Something went wrong.")

Your message dated Thu, 24 Oct 2019 14:58:14 + with message-id and subject line Bug#927481: fixed in sopel 6.6.9-1 has caused the Debian Bug report #927481, regarding .help fails with "Sorry! Something went wrong." to be marked as done. This means that you claim that the problem has been

Processed: py2removal blocks updates - 2019-10-24 14:36:17.169303+00:00

Processing commands for cont...@bugs.debian.org: > # Part of the effort for the removal of python from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # ldtp > block 933025 by 936833 Bug #933025 [src:ldtp] ldtp: Porting to

Processed: upstream bug reference

Processing commands for cont...@bugs.debian.org: > forwarded 943396 https://github.com/FFTW/fftw3/issues/182 Bug #943396 [src:fftw3] FTBFS on armhf: testsuite segfault Set Bug forwarded-to-address to 'https://github.com/FFTW/fftw3/issues/182'. > thanks Stopping processing here. Please contact me

Bug#935300: marked as pending in rsyslog

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

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

Bug#943396: FTBFS on armhf: testsuite segfault

The bug also has been reported upstream on https://github.com/FFTW/fftw3/issues/182 which includes a valgrind log. Getting a backtrace is a bit tricky since the test hangs under gdb... Cheers,

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

Quoting Pirate Praveen (2019-10-24 15:34:15) > On Thu, Oct 24, 2019 at 11:40, Jonas Smedegaard wrote: > > The source package src:node-lodash states in its debian/copyright > > file that its upstream source is > > > > I don't thik that is how DFSG is

Processed: severity of 943402 is important

Processing commands for cont...@bugs.debian.org: > severity 943402 important Bug #943402 [festival] festival: calling festival --tts or text2wave aborts Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 943402:

Bug#943402: [Tts-project] Bug#943402: festival: calling festival --tts or text2wave aborts

Control: severity important Control: tags -1 unreproducible moreinfo Hello, fulvio ciriaco, le jeu. 24 oct. 2019 15:38:11 +0200, a ecrit: > calling festival --tts > or > festival > (SayText "test") > only gives an error: > SIOD ERROR: wrong type of argument to get_c_utt > the same happens if

Processed (with 1 error): Re: [Tts-project] Bug#943402: festival: calling festival --tts or text2wave aborts

Processing control commands: > severity important Unknown command or malformed arguments to command. > tags -1 unreproducible moreinfo Bug #943402 [festival] festival: calling festival --tts or text2wave aborts Added tag(s) unreproducible and moreinfo. -- 943402:

Bug#943405: unsuitable for release: no upstream patch releases

Package: sopel Version: 6.6.2-1 Severity: serious Tags: upstream In bug #927481, I was bit by a bug that wasn't solved upstream in a simple patch release. It would force me to maintain a fork of the project for every supported debian release to fix any bug, because upstream doesn't follow the

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

On Thu, Oct 24, 2019 at 11:40, Jonas Smedegaard wrote: Package: node-lodash Version: 4.17.15+dfsg-1 Severity: serious Justification: Policy 2.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The source package src:node-lodash states in its debian/copyright file that its upstream source is

Bug#943402: festival: calling festival --tts or text2wave aborts

Package: festival Version: 1:2.5.0-4 Severity: grave Justification: renders package unusable calling festival --tts or festival (SayText "test") only gives an error: SIOD ERROR: wrong type of argument to get_c_utt the same happens if one calls text2wave. Thanks Fulvio -- System Information:

Bug#943389: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

On Thu, Oct 24, 2019 at 11:40, Jonas Smedegaard wrote: Package: node-lodash Version: 4.17.15+dfsg-1 Severity: serious Justification: Policy 2.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The source package src:node-lodash states in its debian/copyright file that its upstream source is

Bug#943396: FTBFS on armhf: testsuite segfault

Package: src:fftw3 Version: 3.3.8-2 Severity: serious Tags: patch Hiya, We found this in an Ubuntu test rebuild, but I just confirmed on harris.d.o: > perl -w ./check.pl -r --estimate -c=5 -v `pwd`/bench > Executing "/home/laney/fftw3-3.3.8/tests/bench -o estimate --verbose=1 > --verify

Bug#940540: marked as done (codelite: Uninstallable due to conflicting dependencies)

Your message dated Thu, 24 Oct 2019 11:49:18 + with message-id and subject line Bug#940540: fixed in codelite 13.0+dfsg-1 has caused the Debian Bug report #940540, regarding codelite: Uninstallable due to conflicting dependencies to be marked as done. This means that you claim that the

Bug#934096: marked as done (codelite: Please rebuild against wxWidgets GTK 3 package)

Your message dated Thu, 24 Oct 2019 11:49:18 + with message-id and subject line Bug#934096: fixed in codelite 13.0+dfsg-1 has caused the Debian Bug report #934096, regarding codelite: Please rebuild against wxWidgets GTK 3 package to be marked as done. This means that you claim that the

Bug#943394: libkeduvocdocument FTBFS: symbol errors

Source: libkeduvocdocument Version: 4:17.08.3-1 Severity: serious Tags: ftbfs libkeduvocdocument fails to build from source in unstable when using sbuild natively on amd64. A log ends with: | dh_makeshlibs '-Xusr/lib/libkdeinit5_*' | dpkg-gensymbols: error: some symbols or patterns disappeared

Bug#943389: node-lodash: source package does not contain upstream source

Package: node-lodash Version: 4.17.15+dfsg-1 Severity: serious Justification: Policy 2.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The source package src:node-lodash states in its debian/copyright file that its upstream source is https://github.com/lodash/lodash $ apt source node-lodash $

Bug#935730: marked as done (kamcli: port to python 3 (or remove from Debian?))

Your message dated Thu, 24 Oct 2019 09:07:32 + with message-id and subject line Bug#935730: fixed in kamcli 2.0.0-1 has caused the Debian Bug report #935730, regarding kamcli: port to python 3 (or remove from Debian?) to be marked as done. This means that you claim that the problem has been

Bug#935845: [Pkg-javascript-devel] Bug#940708: Bug#935845: Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

Quoting Pirate Praveen (2019-10-24 10:46:20) > > > On Thu, Oct 24, 2019 at 10:05, Jonas Smedegaard wrote: > > What I criticise is *zero* indication of bundling for the package > > lodash: > > > > src:lodash 4.17.15+dfsg-1 > > > > I would strongly prefer using current bundling scheme for

Bug#942851: perl-modules-5.30: CPAN.pm is insecure by default, no warnings

On 2019-10-23 22:20:04 +0300, Niko Tyni wrote: > So as I understand this, verifying CHECKSUMS would be the thing to do, > and setting 'check_sigs' wouldn't really help (only deployed partially > and no web of trust to the module authors). Indeed, and even if check_sigs is set, it is ignored if

Bug#942851: perl-modules-5.30: CPAN.pm is insecure by default, no warnings

On 2019-10-23 22:20:04 +0300, Niko Tyni wrote: > FWIW this has been the case since forever. Yes, but almost no-one knows about this security issue. Using the CPAN client is generally recommended on the web, but I have never seen any mention of this security issue, not even on the cpan website:

Bug#935845: [Pkg-javascript-devel] Bug#940708: Bug#935845: Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

On Thu, Oct 24, 2019 at 10:05, Jonas Smedegaard wrote: What I criticise is *zero* indication of bundling for the package lodash: src:lodash 4.17.15+dfsg-1 I would strongly prefer using current bundling scheme for that: src:lodash 4.17.15+dfsg+~4.17.5-1 If lodash had had such a

Bug#936219: marked as done (blockdiag: Python2 removal in sid/bullseye)

Your message dated Thu, 24 Oct 2019 08:42:45 + with message-id and subject line Bug#936219: fixed in blockdiag 1.5.3+dfsg-5.3 has caused the Debian Bug report #936219, regarding blockdiag: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#935845: [Pkg-javascript-devel] Bug#935845: Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

Quoting Xavier (2019-10-24 09:18:38) > > > Le 23 octobre 2019 22:07:55 GMT+02:00, Jonas Smedegaard a > écrit : > >Quoting Paolo Greppi (2019-10-23 21:18:37) > >> First, I tripped on this one while testing yarnpkg 1.19.1 from > >experimental. > >> For the record, this is how I found that

Bug#936219: diff of the NMU for this bug

Hi, Since you haven't replied to the previous mail, I've uploaded this without delay, fixing the RC bug on blockdiag. Cheers, Thomas Goirand (zigo) diff -Nru blockdiag-1.5.3+dfsg/debian/changelog blockdiag-1.5.3+dfsg/debian/changelog --- blockdiag-1.5.3+dfsg/debian/changelog 2018-07-16

Bug#935845: [Pkg-javascript-devel] Bug#935845: Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

Le 23 octobre 2019 22:07:55 GMT+02:00, Jonas Smedegaard a écrit : >Quoting Paolo Greppi (2019-10-23 21:18:37) >> First, I tripped on this one while testing yarnpkg 1.19.1 from >experimental. >> For the record, this is how I found that node-lodash was the culprit: >> >> node

Bug#937926: Lowered severity

Hi, I've re-introduced python-pbr, so the severity of this bug can be lowered back to just 'important'. We'll revisit Py2 removal from this package once these are fixed: http://sandrotosi.me/debian/py2removal/python-mock_1.svg Cheers, Thomas Goirand (zigo)

Processed: Lower python-mock severity

Processing commands for cont...@bugs.debian.org: > severity 937926 important Bug #937926 [src:python-mock] python-mock: Python2 removal in sid/bullseye Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 937926:

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 936046 5.12.3+dfsg-3 Bug #936046 [python3-pyqt5] python3-pyqt5: does not depends on matching qtbase-abi Marked as fixed in versions pyqt5/5.12.3+dfsg-3. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#936046: python3-pyqt5: does not depends on matching qtbase-abi

Looks like the dependency chain is fixed, python3-pyqt5 is installable again. Thanks.

Bug#936046: marked as done (python3-pyqt5: does not depends on matching qtbase-abi)

Your message dated Thu, 24 Oct 2019 09:07:46 +0200 with message-id <07d8e1c7-0da2-da3a-feaa-57faf0c88...@gmail.com> and subject line has caused the Debian Bug report #936046, regarding python3-pyqt5: does not depends on matching qtbase-abi to be marked as done. This means that you claim that the