Bug#942229: Issue confirmed on Buster i386

2019-10-26 Thread Jérémy Viès
Hello, I haven't find any solution for the llvm build on buster i386. By the way, the -3 release from sid makes the backport further more complicated as now it draws z3, that needs a newer version of ocaml... For now, I abandonned the idea to quickly backport mesa from sid to buster. Best

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

2019-10-26 Thread Olly Betts
On Fri, Oct 25, 2019 at 01:52:31AM +0100, Olly Betts wrote: > I'll try to sort out my chroots over the weekend, but meanwhile if you > can get somebody else to sponsor please go for it. I've rebuilt my build chroots in a larger partition. However, then the build fails for me running tests using

Bug#943545: Similar behaviour for me

2019-10-26 Thread Paul Bryan
Similar behaviour for me on Lenovo T480, though: 1. I have no audio at all through built-in speakers or headphones. 2. Initially, there are no output devices enumerated. 3. After a minute or so, HDMI and built-in headphones devices appear. 4. Built-in speakers still do not appear in device list.

Bug#885375: marked as done (pygtkspellcheck: Depends on unmaintained pygtk)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Oct 2019 02:39:20 + with message-id and subject line Bug#885375: fixed in pygtkspellcheck 4.0.5-2 has caused the Debian Bug report #885375, regarding pygtkspellcheck: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has

Bug#942235: dask: autopkgtest needs update for new version of pytest

2019-10-26 Thread Drew Parsons
Source: dask Followup-For: Bug #942235 Fixed upstream, latest version is pushed to the experimental branch. Needs sphinx-click, which is in the NEW queue. Drew -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental')

Bug#940092: marked as done (flowblade doesn't start)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Oct 2019 00:34:06 + with message-id and subject line Bug#940092: fixed in flowblade 2.2+py3-1 has caused the Debian Bug report #940092, regarding flowblade doesn't start to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#937593: marked as done (python-aws-xray-sdk: Python2 removal in sid/bullseye)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 23:49:49 + with message-id and subject line Bug#937593: fixed in python-aws-xray-sdk 0.95-2 has caused the Debian Bug report #937593, regarding python-aws-xray-sdk: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#922586: FTBFS against opencv 4.0.1 (exp)

2019-10-26 Thread Olly Betts
On Sat, Oct 26, 2019 at 10:39:47PM +0200, José Luis Blanco-Claraco wrote: > However, I want to point out that we don't need to wait for > mrpt-2.0.0, since the current version in unstable (1.5.8) already > fixes this wxwidgets3.0-gtk3 bug. > As you said, the problem now is the build issue in

Bug#943584: xul-ext-dispmua: AddOn does not work with Thunderbird 68.x

2019-10-26 Thread Carsten Schoenert
Package: xul-ext-dispmua Version: 1.8.2-1 Severity: grave Dear Maintainer, the extension does not work with TB 68 anymore. The AddOn is not detected by the curent new TB ESR version. Regards Carsten -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500,

Processed: tagging 922599, severity of 922599 is serious

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 922599 + ftbfs Bug #922599 [src:uprightdiff] FTBFS against opencv 4.0.1 (exp) Added tag(s) ftbfs. > severity 922599 serious Bug #922599 [src:uprightdiff] FTBFS against opencv 4.0.1 (exp) Severity set to 'serious' from 'important' > thanks

Bug#943569: virtualbox-dkms:ERROR: missing module or filename. rc=-1908 linux-headers-5.3.0-1-amd64

2019-10-26 Thread Gustavo Castro
The latest update of the dkms package corrected the failure package: dkms Versión: 2.7.1-5 Thank you

Processed: tagging 943479, tagging 943474

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 943479 + sid bullseye Bug #943479 [src:haskell-werewolf] FTBFS with ghc-8.6.5 Added tag(s) sid and bullseye. > tags 943474 + sid bullseye Bug #943474 [src:django-modeltranslation] Doesn't build with Django 2.2 Added tag(s) bullseye and sid.

Bug#922586: FTBFS against opencv 4.0.1 (exp)

2019-10-26 Thread José Luis Blanco-Claraco
Ok, sorry, forgot my last message, you already mentioned the new problem: > But now that missing mipsel build can't be addressed without > also updating mrpt for auto-opencv because it currently FTBFS in > unstable. It's a shame, but I think that perhaps I'll just leave mrpt to be removed from

Bug#922586: FTBFS against opencv 4.0.1 (exp)

2019-10-26 Thread José Luis Blanco-Claraco
Hi Olly, > It was waiting for mrpt 2.0.0 for wxwidgets3.0-gtk3 that got us into the > current mess of having two entangled transitions on the go for mrpt. If > we'd just updated the B-Ds of the existing package we'd have got that > out the way weeks (possibly months) ago. Instead mrpt is now

Bug#943578: fluxbox: FTBFS due to undefined references

2019-10-26 Thread Andreas Beckmann
Source: fluxbox Version: 1.3.7-1~exp1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, fluxbox/experimental FTBFS in a current sid/experimental pbuilder environment: g++ -g -O2 -fdebug-prefix-map=/build/fluxbox-1.3.7=.

Processed: your mail

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 943566 https://github.com/KIT-Telematics/pktanon/issues/2 Bug #943566 [src:pktanon] FTBFS with nettle 3.5.1 Set Bug forwarded-to-address to 'https://github.com/KIT-Telematics/pktanon/issues/2'. > tags 943566 help Bug #943566

Processed: severity of 941686 is grave

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 941686 grave Bug #941686 [backintime-qt] backintime-qt: Version 1.2.1-1 has wrong dependency on qt4 python3-dbus.mainloop Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need

Bug#885375: marked as pending in pygtkspellcheck

2019-10-26 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #885375 in pygtkspellcheck 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#885375 marked as pending in pygtkspellcheck

2019-10-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #885375 [src:pygtkspellcheck] pygtkspellcheck: Depends on unmaintained pygtk Added tag(s) pending. -- 885375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#922586: FTBFS against opencv 4.0.1 (exp)

2019-10-26 Thread Olly Betts
On Thu, Oct 24, 2019 at 12:48:08AM +0200, Gianfranco Costamagna wrote: > the package is going to get kicked out from testing because of this > bug soon... It's actually #933469 which will get it auto-removed from testing in next few days - the AUTORM for this bug wouldn't kick in for a couple of

Bug#943573: debian-edu-config: Don't depend on python-notify

2019-10-26 Thread Holger Levsen
Hi Jeremy, thanks for your bug report and all the work on GNOME! On Sat, Oct 26, 2019 at 02:40:52PM -0400, Jeremy Bicha wrote: > As part of the Python2 removal, the Debian GNOME team is working to > remove pygtk from Debian. One of the blockers is python-notify. > > Please drop

Bug#941779: marked as done (aiscm: FTBFS on amd64)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 19:34:04 + with message-id and subject line Bug#941779: fixed in aiscm 0.19.2-1 has caused the Debian Bug report #941779, regarding aiscm: FTBFS on amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#943574: pyhoca-gui: Please don't depend on python-notify

2019-10-26 Thread Jeremy Bicha
Source: pyhoca-gui Version: 0.5.0.8-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid bullseye As part of the Python2 removal, the Debian GNOME team is working to remove pygtk from Debian. One of the blockers is python-notify. Please drop

Bug#943573: debian-edu-config: Don't depend on python-notify

2019-10-26 Thread Jeremy Bicha
Source: debian-edu-config Version: 2.11.5 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid bullseye As part of the Python2 removal, the Debian GNOME team is working to remove pygtk from Debian. One of the blockers is python-notify. Please

Processed: Re: Bug#885261: bleachbit: Depends on unmaintained pygtk

2019-10-26 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #885261 [src:bleachbit] bleachbit: Depends on unmaintained pygtk Severity set to 'serious' from 'important' > tags -1 -buster Bug #885261 [src:bleachbit] bleachbit: Depends on unmaintained pygtk Removed tag(s) buster. -- 885261:

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

2019-10-26 Thread Chris Lamb
Hi László, > But you mean plural packages? I knew only python-django. I meant > sure, it's a FTBFS in experimental where […] I see what you mean now, thanks. I assumed it affected more packages and was more severe than just python-django from the description, but I admittedly had done no

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

2019-10-26 Thread Andreas Beckmann
On 26/10/2019 17.13, László Böszörményi (GCS) wrote: > In short, I don't get the importance of filing a FTBFS bug for a beta > release in experimental. I'm filing bugs for artefacts discovered by QA. I don't know if it is a beta, RC, or whatever release. I only noticed "something is not working".

Bug#942229: Issue confirmed on Buster i386

2019-10-26 Thread Sylvestre Ledru
Hello I just experienced it too and the cmake logs are useless. Have you been able to find a fix for that? It is pretty confusing :/ Thanks Sylvestre Le 17/10/2019 à 19:29, Jérémy Viès a écrit : Hello, I'm following this bug as I try to do the same backport. I can confirm the issue in a

Bug#939819: Fwd: mariadb-10.3_10.3.18-0+deb10u1_source.changes ACCEPTED into proposed-updates->stable-new

2019-10-26 Thread Otto Kekäläinen
Hello! Just a status update. This was approved for a stable update in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940521 and uploaded for 1,5 months ago. However there is no schedule for the next Buster point release yet at https://release.debian.org/ ("stable (10.2) Not yet planned").

Bug#943569: virtualbox-dkms:ERROR: missing module or filename. rc=-1908 linux-headers-5.3.0-1-amd64

2019-10-26 Thread Gustavo Castro
Package: virtualbox-dkms Version: 6.0.14-dfsg-1 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, The VirtualBox Linux kernel driver is either not loaded or not set up correctly. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT

Bug#943561: marked as done (unoconv: CVE-2019-17400)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 15:52:46 + with message-id and subject line Bug#943561: fixed in unoconv 0.7-2 has caused the Debian Bug report #943561, regarding unoconv: CVE-2019-17400 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#939382: marked as done (fswatch: bad symbols file on !amd64)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 15:18:59 + with message-id and subject line Bug#939382: fixed in fswatch 1.14.0+repack-13 has caused the Debian Bug report #939382, regarding fswatch: bad symbols file on !amd64 to be marked as done. This means that you claim that the problem has been

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

2019-10-26 Thread GCS
Hi Chris, On Sat, Oct 26, 2019 at 2:48 PM Chris Lamb wrote: > Not quite sure what you mean by bad. It's "bad" in that it's causing > an FTBFS in other packages, but I don't think that's quite what you > meant here. :) > Yeah, you are British. :) But you mean plural packages? I knew only

Processed: your mail

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 942105 important Bug #942105 [fcitx] Can not active fcitx after Debian testing upgraded today Severity set to 'important' from 'grave' > severity 943372 important Bug #943372 [scim] Can not active scim after Debian testing upgrade on 10

Bug#943566: FTBFS with nettle 3.5.1

2019-10-26 Thread Paul Gevers
Source: pktanon Version: 2~git20160407.0.2bde4f2+dfsg-5 Severity: serious Tags: ftbfs Justification: ftbfs Control: block 941150 by -1 Dear maintainer, Currently the nettle 3.5.1 transition is going on. I tried to binNMU your package but it fails to build from source on all architectures. Paul

Processed: FTBFS with nettle 3.5.1

2019-10-26 Thread Debian Bug Tracking System
Processing control commands: > block 941150 by -1 Bug #941150 [release.debian.org] transition: nettle 941150 was blocked by: 941101 940985 941041 941150 was not blocking any bugs. Added blocking bug(s) of 941150: 943566 -- 941150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941150 943566:

Bug#943561: unoconv: CVE-2019-17400

2019-10-26 Thread Salvatore Bonaccorso
Source: unoconv Version: 0.7-1.1 Severity: grave Tags: security upstream Forwarded: https://github.com/unoconv/unoconv/pull/510 Hi, The following vulnerability was published for unoconv. CVE-2019-17400[0]: | The unoconv package before 0.9 mishandles untrusted pathnames, leading | to SSRF and

Bug#942105: Can not active fcitx after Debian testing upgraded

2019-10-26 Thread 王钢林
There is not any echo about this bug for three weeks. Who can resolve this problem? It makes debian lost function of input Chinese.

Bug#943372: Can not active scim after Debian testing upgrade on 10 Oct 2019

2019-10-26 Thread 王钢林
There is not any echo about this bug for three weeks. Who can resolve this problem? It makes debian lost function of input Chinese.

Processed: found 942895 in 2.0.5-1, tagging 942895

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 942895 2.0.5-1 Bug #942895 {Done: Salvatore Bonaccorso } [src:libidn2] CVE-2019-18224 Marked as found in versions libidn2/2.0.5-1. > tags 942895 + upstream fixed-upstream Bug #942895 {Done: Salvatore Bonaccorso } [src:libidn2]

Processed: closing 942895

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 942895 2.2.0-1 Bug #942895 [src:libidn2] CVE-2019-18224 Marked as fixed in versions libidn2/2.2.0-1. Bug #942895 [src:libidn2] CVE-2019-18224 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance.

Bug#942895: closing 942895

2019-10-26 Thread Salvatore Bonaccorso
close 942895 2.2.0-1 thanks

Processed: re: stressant: Python2 removal in sid/bullseye

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 938573 serious Bug #938573 [src:stressant] stressant: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 938573:

Processed: re: python-easydev: Python2 removal in sid/bullseye

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 937720 serious Bug #937720 [src:python-easydev] python-easydev: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 937720:

Processed: tagging 942831, bug 942831 is forwarded to https://github.com/proftpd/proftpd/issues/846 ...

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 942831 + upstream Bug #942831 {Done: Hilmar Preusse } [src:proftpd-dfsg] CVE-2019-18217 Added tag(s) upstream. > forwarded 942831 https://github.com/proftpd/proftpd/issues/846 Bug #942831 {Done: Hilmar Preusse } [src:proftpd-dfsg]

Processed: found 942830 in 1:5.35-5, tagging 942830, found 942830 in 1:5.35-4, found 942830 in 1:5.30-1 ...

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # add a bit of bts metadata > found 942830 1:5.35-5 Bug #942830 {Done: Christoph Biedl } [file] CVE-2019-18218 There is no source info for the package 'file' at version '1:5.35-5' with architecture '' Unable to make a source version for version

Bug#943555: wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3

2019-10-26 Thread Chris.
Package: wireguard-dkms Version: 0.0.20191012-1 Severity: grave Justification: renders package unusable Dear Maintainer, on Raspberry Pi3 kernel module stops building since updating to kernel 5.3.0.1. Output of /var/lib/dkms/wireguard/0.0.20191012/build/make.log DKMS make.log for

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

2019-10-26 Thread Chris Lamb
Hi László, > > https://code.djangoproject.com/ticket/30879 > > > > It appears to be an issue in sqlite 3.30.1. > > Indeed, the bug is in SQLite3 but the mentioned fix and its successor > don't fix this issue. The current HEAD yes, but that may introduce > other problems. I'm interested how

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

2019-10-26 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #942851 [src:perl] perl: CPAN.pm is insecure by default, no warnings Severity set to 'important' from 'grave' -- 942851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942851 Debian Bug Tracking System Contact ow...@bugs.debian.org

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

2019-10-26 Thread Niko Tyni
Control: severity -1 important On Wed, Oct 23, 2019 at 11:22:47PM +0200, Moritz Muehlenhoff wrote: > On Wed, Oct 23, 2019 at 10:20:04PM +0300, Niko Tyni wrote: > > Control: reassign -1 src:perl > > Control: found -1 5.20.2-3 > > > > On Tue, Oct 22, 2019 at 12:36:14PM +0200, Vincent Lefevre

Bug#941041: marked as done (unbound: FTBFS with nettle 3.5.1, accesses ECC curves directly)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 12:36:11 + with message-id and subject line Bug#941041: fixed in unbound 1.9.4-2 has caused the Debian Bug report #941041, regarding unbound: FTBFS with nettle 3.5.1, accesses ECC curves directly to be marked as done. This means that you claim that the

Bug#943554: engrampa FTBFS: python segfault while running itstool

2019-10-26 Thread Helmut Grohne
Source: engrampa Version: 1.22.2-1 Severity: serious Tags: ftbfs engrampa fails to build from source in unstable using sbuild on amd64. A build ends with: | if test -f "${mo}"; then mo="../${mo}"; else mo="/<>/help/${mo}"; fi; \ | (cd "as/" && itstool -m "${mo}" ${d}/C/index.docbook

Bug#936418: marked as done (django-picklefield: Py2 rm in sid/bullseye + django 2.2)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 11:34:08 + with message-id and subject line Bug#936418: fixed in django-picklefield 2.0-1 has caused the Debian Bug report #936418, regarding django-picklefield: Py2 rm in sid/bullseye + django 2.2 to be marked as done. This means that you claim that the

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

2019-10-26 Thread GCS
On Sat, Oct 26, 2019 at 11:33 AM Chris Lamb wrote: > > python-django/experimental FTBFS: > > Indeed. I noticed this after uploading and reported it upstream here: > > https://code.djangoproject.com/ticket/30879 > > It appears to be an issue in sqlite 3.30.1. > Indeed, the bug is in SQLite3

Processed: block 941150 with 941101 940985 941041, tagging 940985

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 941150 with 941101 940985 941041 Bug #941150 [release.debian.org] transition: nettle 941150 was not blocked by any bugs. 941150 was not blocking any bugs. Added blocking bug(s) of 941150: 941041, 941101, and 940985 > tags 940985 + ftbfs Bug

Bug#943523: marked as done (xpdf: FTBFS: build/PDFCore.cc:311:37: error: no matching function for call to 'PDFDoc::findPage(Ref&)')

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 10:51:34 + with message-id and subject line Bug#943523: fixed in xpdf 3.04-13exp3 has caused the Debian Bug report #943523, regarding xpdf: FTBFS: build/PDFCore.cc:311:37: error: no matching function for call to 'PDFDoc::findPage(Ref&)' to be marked as

Processed: tagging 941101, severity of 941101 is serious

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 941101 + ftbfs Bug #941101 [rdup] rdup: Uses functions deprecated in Nettle 3.5 Added tag(s) ftbfs. > severity 941101 serious Bug #941101 [rdup] rdup: Uses functions deprecated in Nettle 3.5 Severity set to 'serious' from 'normal' > thanks

Processed: django-reversion is fixed

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 943476 3.0.4-2 Bug #943476 [src:django-reversion] django-reversion: Django 2.2 support The source 'django-reversion' and version '3.0.4-2' do not appear to match any binary packages Marked as fixed in versions django-reversion/3.0.4-2. >

Bug#943476: Package was fixed, but uploaded with binaries

2019-10-26 Thread Thomas Goirand
Hi, It appears it was fixed indeed, but uploaded with binaries, and therefore didn't migrate to testing. I'm re-uploading to fix that. Cheers, Thomas Goirand (zigo)

Processed: fixed

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 926946 2.2.99.0-1 Bug #926946 {Done: Iain Lane } [src:tracker] tracker-miner-fs SIGSEGV in process_func_start() Marked as fixed in versions tracker/2.2.99.0-1. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

2019-10-26 Thread Chris Lamb
reassign 943509 sqlite3 3.30.1-1 affects 943509 python-django thanks Hi Andreas, > python-django/experimental FTBFS: Indeed. I noticed this after uploading and reported it upstream here: https://code.djangoproject.com/ticket/30879 It appears to be an issue in sqlite 3.30.1. Regards, --

Processed: Re: Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 943509 sqlite3 3.30.1-1 Bug #943509 [src:python-django] python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4 Bug reassigned from package 'src:python-django' to 'sqlite3'. No longer marked as found in

Bug#943549: dymo-cups-drivers FTBFS: ../common/CupsPrintEnvironment.cpp:139:23: error: ‘cupsBackChannelRead’ was not declared in this scope

2019-10-26 Thread Helmut Grohne
Source: dymo-cups-drivers Version: 1.4.0-8 Severity: serious Tags: ftbfs dymo-cups-drivers fails to build from source in unstable using sbuild on amd64. The compiler error is quite hidden in the amount of warnings: | ../common/CupsPrintEnvironment.cpp: In member function 'virtual void

Bug#943523: marked as done (xpdf: FTBFS: build/PDFCore.cc:311:37: error: no matching function for call to 'PDFDoc::findPage(Ref&)')

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 11:08:34 +0200 with message-id and subject line Re: xpdf: FTBFS: build/PDFCore.cc:311:37: error: no matching function for call to 'PDFDoc::findPage(Ref&)' has caused the Debian Bug report #943523, regarding xpdf: FTBFS: build/PDFCore.cc:311:37: error: no

Bug#942236: marked as done (doit: autopkgtest needs update for new version of pytest)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 09:06:52 + with message-id and subject line Bug#942236: fixed in doit 0.31.1-3 has caused the Debian Bug report #942236, regarding doit: autopkgtest needs update for new version of pytest to be marked as done. This means that you claim that the problem has

Bug#943331: qgis: FTBFS with Qt 5.12.5

2019-10-26 Thread Dmitry Shachnev
On Sat, Oct 26, 2019 at 10:35:37AM +0200, Sebastiaan Couwenberg wrote: > On 10/26/19 10:19 AM, Dmitry Shachnev wrote: > > Thanks for fixing this! Unfortunately it still FTBFS on mipsel. Do you know > > what could cause this? > > My gut says it just inherent to the arch, mips* tends to be

Bug#941933: marked as done (polymake: FTBFS: no more rules available to compute 'HILBERT_BASIS_GENERATORS')

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 08:44:52 + with message-id and subject line Bug#941933: fixed in normaliz 3.8.1+ds-1 has caused the Debian Bug report #941933, regarding polymake: FTBFS: no more rules available to compute 'HILBERT_BASIS_GENERATORS' to be marked as done. This means that

Bug#885271: marked as done (dia-common: Depends on unmaintained pygtk)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 08:39:54 + with message-id and subject line Bug#885271: fixed in dia 0.97.3+git20160930-8.2 has caused the Debian Bug report #885271, regarding dia-common: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has

Bug#939382: fswatch: bad symbols file on !amd64

2019-10-26 Thread Gianfranco Costamagna
control: reopen -1 control: notfixed -1 1.14.0+repack-12 Hello, On Sat, 5 Oct 2019 19:46:00 +0200 Alf Gaida wrote: > On Wed, 4 Sep 2019 11:42:01 +0200 Gianfranco Costamagna > wrote: > > I don't think exporting such c++ symbols is a good idea, specially > because they change between

Bug#943331: qgis: FTBFS with Qt 5.12.5

2019-10-26 Thread Sebastiaan Couwenberg
On 10/26/19 10:19 AM, Dmitry Shachnev wrote: > Thanks for fixing this! Unfortunately it still FTBFS on mipsel. Do you know > what could cause this? My gut says it just inherent to the arch, mips* tends to be problematic. I don't know how to fix the "Error: branch out of range" issues, so I'll

Processed: Re: fswatch: bad symbols file on !amd64

2019-10-26 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #939382 {Done: Alf Gaida } [src:fswatch] fswatch: bad symbols file on !amd64 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as

Bug#943331: qgis: FTBFS with Qt 5.12.5

2019-10-26 Thread Dmitry Shachnev
Hi Sebastiaan, On Wed, Oct 23, 2019 at 04:52:47PM +0200, Sebastiaan Couwenberg wrote: > The log implies the problem is with OpenCL, it may be the same as > #942015 which is already fixed in git. > > The next upstream release will be on Friday, since this issue will also > break their builds, a

Processed: tagging 941041

2019-10-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 941041 + ftbfs Bug #941041 [unbound] unbound: FTBFS with nettle 3.5.1, accesses ECC curves directly Ignoring request to alter tags of bug #941041 to the same tags previously set > thanks Stopping processing here. Please contact me if you

Processed: Re: fixed 941041 in 1.9.4-1

2019-10-26 Thread Debian Bug Tracking System
Processing control commands: > notfixed -1 1.9.4-1 Bug #941041 [unbound] unbound: FTBFS with nettle 3.5.1, accesses ECC curves directly No longer marked as fixed in versions unbound/1.9.4-1. > tags -1 + ftbfs Bug #941041 [unbound] unbound: FTBFS with nettle 3.5.1, accesses ECC curves directly

Bug#941041: fixed 941041 in 1.9.4-1

2019-10-26 Thread Helmut Grohne
Control: notfixed -1 1.9.4-1 Control: tags -1 + ftbfs On Sat, Oct 05, 2019 at 08:18:03PM -0400, Robert Edmonds wrote: > fixed 941041 1.9.4-1 The nettle transition has started now. I tried building 1.9.4-1 in unstable and I get this: | ./libtool --tag=CC --mode=compile gcc -I. -Wdate-time

Bug#943545: pulseaudio: audio completely broken

2019-10-26 Thread Mario Alegre
Package: pulseaudio Version: 13.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, I recently ran apt upgrade (on 2019-10-23). The last update before that was about two weeks before. The sound was working fine before I ran the update. After the update, sound will no

Bug#936189: marked as done (bcfg2: Python2 removal in sid/bullseye)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 07:09:15 + with message-id and subject line Bug#943378: Removed package(s) from unstable has caused the Debian Bug report #936189, regarding bcfg2: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#899802: marked as done (libpam-sshauth: Invalid maintainer address pkg-ltsp-de...@lists.alioth.debian.org)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 07:06:08 + with message-id and subject line Bug#942806: Removed package(s) from unstable has caused the Debian Bug report #899802, regarding libpam-sshauth: Invalid maintainer address pkg-ltsp-de...@lists.alioth.debian.org to be marked as done. This means

Bug#899601: marked as done (ltsp-docs: Invalid maintainer address pkg-ltsp-de...@lists.alioth.debian.org)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 07:05:44 + with message-id and subject line Bug#942805: Removed package(s) from unstable has caused the Debian Bug report #899601, regarding ltsp-docs: Invalid maintainer address pkg-ltsp-de...@lists.alioth.debian.org to be marked as done. This means that

Bug#924660: marked as done (tails-installer: Should not be part of Buster)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 07:04:12 + with message-id and subject line Bug#942790: Removed package(s) from unstable has caused the Debian Bug report #924660, regarding tails-installer: Should not be part of Buster to be marked as done. This means that you claim that the problem has

Bug#942403: marked as done (golang-github-hashicorp-raft breaks golang-github-canonicalltd-raft-membership autopkgtest)

2019-10-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Oct 2019 07:02:55 + with message-id and subject line Bug#942745: Removed package(s) from unstable has caused the Debian Bug report #942403, regarding golang-github-hashicorp-raft breaks golang-github-canonicalltd-raft-membership autopkgtest to be marked as done.