Bug#934960: closed by Ondřej Nový (Bug#934960: fixed in pytest-mock 1.10.4-1)

2019-08-24 Thread Paul Gevers
Hi Ondřej, On 24-08-2019 19:27, Debian Bug Tracking System wrote: > pytest-mock (1.10.4-1) unstable; urgency=medium > . >* Team upload. >* New upstream release (Closes: #904304). Was this bug only an issue in the autopkgtest, or was it causing an issue in pytest-mock? In the former

Bug#935677: ganeti-2.16: Depends on to be removed packages (python2/python-ipaddr specifically)

2019-08-24 Thread Scott Kitterman
Package: ganeti-2.16 Version: 2.16.0-5 Severity: serious Justification: Policy 2.5 As you may have heard, the plan is to remove python2 for the bullseye release. As part of that effort, the python teams are working on removing as much of the python2 stack as early as we can. As part of that

Bug#935676: ganeti-2.15: Depends on to be removed packages (python2/python-ipaddr specifically)

2019-08-24 Thread Scott Kitterman
Source: ganeti-2.15 Version: 2.15.2-15 Severity: serious Justification: Policy 2.5 As you may have heard, the plan is to remove python2 for the bullseye release. As part of that effort, the python teams are working on removing as much of the python2 stack as early as we can. As part of that

Processed: severity of 927131 is serious

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 927131 serious Bug #927131 [src:grr] src:grr: Please port to python3 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 927131:

Processed: severity of 927132 is serious

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 927132 serious Bug #927132 [src:hash-slinger] src:hash-slinger: Please port to python3 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 927132:

Bug#927135: src:rekall: Please update to python3 version

2019-08-24 Thread Scott Kitterman
On Mon, 15 Apr 2019 08:52:16 -0400 Scott Kitterman wrote: > Package: src:rekall > Version: 1.6.0+dfsg-2 > Severity: important > > Python2.7 will go out of upstream security support during the Bullseye > development cycle. It is not safe to assume it will be included in the > next release, so

Processed: severity of 927135 is serious

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 927135 serious Bug #927135 [src:rekall] src:rekall: Please update to python3 version Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 927135:

Processed: severity of 927136 is serious

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 927136 serious Bug #927136 [src:zabbix-cli] src:zabbix-cli: Please update to python3 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 927136:

Bug#935674: librust-blake2-rfc+clippy-dev/amd64 unsatisfiable Depends: librust-clippy-0.0.41+default-dev

2019-08-24 Thread Steve Langasek
Source: rust-blake2-rfc Version: 0.2.18-2 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan The rust-blake2-rfc package generates a binary package that appears to depend on rust-clippy, but there is no rust-clippy package in the archive (or in the new queue).

Bug#935673: rust-ring depends on out-of-date rust-untrusted

2019-08-24 Thread Steve Langasek
Source: rust-ring Version: 0.14.6-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan The rust-ring package is uninstallable, because it depends on a version of rust-untrusted that is older than what's in unstable: librust-ring-dev : Depends:

Bug#935672: librust-backtrace+addr2line-dev/amd64 unsatisfiable Depends: librust-addr2line-0.9+std-dev

2019-08-24 Thread Steve Langasek
Source: rust-backtrace Version: 0.3.34-1 Severity: serious Affects: src:rust-addr2line User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan The rust-backtrace package depends on a newer rust-addr2line than is available in the Debian archive. librust-backtrace+addr2line-dev/amd64

Bug#935671: librust-rle-decode-fast+bench-dev/amd64 unsatisfiable Depends: librust-criterion-0.2+default-dev

2019-08-24 Thread Steve Langasek
Source: rust-rle-decode-fast Version: 1.0.1-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan The rust-rle-decode-fast package generates two binary packages that appear to depend on rust-criterion, but there is no rust-criterion package in the archive (or in the

Bug#935568: sphinx-issuetracker: should this package be removed?

2019-08-24 Thread Sandro Tosi
On Sat, Aug 24, 2019 at 12:59 PM Dmitry Shachnev wrote: > > Hi Sandro! > > On Fri, Aug 23, 2019 at 10:46:30PM -0400, Sandro Tosi wrote: > > Hello, > > sphinx-issuetracker is currently incompatible with python3.7: > > [...] > > > > It has no reverse-dependencies and it's currently one of the few

Bug#935669: assaultcube-data: Outdated version makes assaultcube uninstallable

2019-08-24 Thread Guillem Jover
Package: assaultcube-data Version: 1.1.0.4+repack1-2.1 Severity: serious Hi! The assaultcube package got updated to version 1.2.0.2.1-1, but the matching assaultcube-data package has not been uploaded which makes the former to be currently uninstallable in unstable. Thanks, Guillem

Bug#875149: [qtcurve] Future Qt4 removal from Buster

2019-08-24 Thread Scott Kitterman
On Sat, 9 Sep 2017 23:07:54 +0200 Lisandro =?iso-8859-1?Q? Dami=E1n_Nicanor_P=E9rez?= Meyer wrote: > Source: qtcurve > Version: 1.8.18+git20160320-3d8622c-5 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are

Bug#925644: marked as done (bladerf: ftbfs with GCC-9)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sun, 25 Aug 2019 01:19:43 + with message-id and subject line Bug#925644: fixed in bladerf 0.2019.07-1 has caused the Debian Bug report #925644, regarding bladerf: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#875215: marked as done ([syncevolution] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sun, 25 Aug 2019 00:50:57 + with message-id and subject line Bug#935239: Removed package(s) from unstable has caused the Debian Bug report #875215, regarding [syncevolution] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#935660: tortoisehg: Obsolete libs (python2) - depends python-pyqt5.qsci

2019-08-24 Thread Scott Kitterman
Source: tortoisehg Version: 4.8.1-0.1 Severity: serious Justification: Policy 2.5 We are in the process of removing python2 from Debian during the bullseye release cycle. This package is the last remaining dependency of python-pyqt5.qsci. Please update to python3 (I have not checked if your

Bug#875494: connectomeviewer: Qt4 removal form Buster

2019-08-24 Thread Scott Kitterman
On Mon, 11 Sep 2017 16:33:30 -0300 =?utf-8?q? Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= wrote: > Source: connectomeviewer > Version: 2.1.0-1.1 > Severity: minor > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > Note: this bug is being filled because your package recommends

Bug#871302: marked as done (libmysql++3v5: requires rebuild against GCC 7 and symbols/shlibs bump)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:49:24 + with message-id and subject line Bug#871302: fixed in mysql++ 3.2.5-1 has caused the Debian Bug report #871302, regarding libmysql++3v5: requires rebuild against GCC 7 and symbols/shlibs bump to be marked as done. This means that you claim that

Bug#874825: marked as done ([appmenu-qt] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:49:23 + with message-id and subject line Bug#935652: Removed package(s) from unstable has caused the Debian Bug report #874825, regarding [appmenu-qt] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#919377: marked as done (mysql++: FTBFS with mariadb-10.3: dbdriver.cpp:260:10: error: 'CLIENT_LONG_PASSWORD' was not declared in this scope)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:49:24 + with message-id and subject line Bug#919377: fixed in mysql++ 3.2.5-1 has caused the Debian Bug report #919377, regarding mysql++: FTBFS with mariadb-10.3: dbdriver.cpp:260:10: error: 'CLIENT_LONG_PASSWORD' was not declared in this scope to be

Bug#875208: marked as done ([tora] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:48:59 + with message-id and subject line Bug#935649: Removed package(s) from unstable has caused the Debian Bug report #875208, regarding [tora] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#934817: marked as done (libmysql++3v5: built with libmariadbclient18, which doesn't exist any longer)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:49:24 + with message-id and subject line Bug#934817: fixed in mysql++ 3.2.5-1 has caused the Debian Bug report #934817, regarding libmysql++3v5: built with libmariadbclient18, which doesn't exist any longer to be marked as done. This means that you

Bug#934815: marked as done (mosquitto-auth-plugin: built with libmariadbclient18, which doesn't exist any longer)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:48:18 + with message-id and subject line Bug#935634: Removed package(s) from unstable has caused the Debian Bug report #934815, regarding mosquitto-auth-plugin: built with libmariadbclient18, which doesn't exist any longer to be marked as done. This

Bug#875164: marked as done ([qwbfsmanager] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:49:50 + with message-id and subject line Bug#935656: Removed package(s) from unstable has caused the Debian Bug report #875164, regarding [qwbfsmanager] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#915346: marked as done (mosquitto-auth-plugin FTBFS with mosquitto 1.5.4-1)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:48:18 + with message-id and subject line Bug#935634: Removed package(s) from unstable has caused the Debian Bug report #915346, regarding mosquitto-auth-plugin FTBFS with mosquitto 1.5.4-1 to be marked as done. This means that you claim that the problem

Bug#875199: marked as done ([synergy] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:47:47 + with message-id and subject line Bug#935457: Removed package(s) from unstable has caused the Debian Bug report #875199, regarding [synergy] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#898549: marked as done (synergy FTBFS: No SOURCES given to target: gmock)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:47:47 + with message-id and subject line Bug#935457: Removed package(s) from unstable has caused the Debian Bug report #898549, regarding synergy FTBFS: No SOURCES given to target: gmock to be marked as done. This means that you claim that the problem

Bug#907528: marked as done (synergy: low grade TLS certificate generation, now unusable in unstable)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:47:47 + with message-id and subject line Bug#935457: Removed package(s) from unstable has caused the Debian Bug report #907528, regarding synergy: low grade TLS certificate generation, now unusable in unstable to be marked as done. This means that you

Bug#874964: marked as done ([knutclient] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:45:31 + with message-id and subject line Bug#935229: Removed package(s) from unstable has caused the Debian Bug report #874964, regarding [knutclient] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#935486: marked as done (quicksynergy: Depends on synergy which is due to be removed (Obsolete libs))

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:46:49 + with message-id and subject line Bug#935631: Removed package(s) from unstable has caused the Debian Bug report #935486, regarding quicksynergy: Depends on synergy which is due to be removed (Obsolete libs) to be marked as done. This means that

Bug#874968: marked as done ([kover] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:46:08 + with message-id and subject line Bug#935230: Removed package(s) from unstable has caused the Debian Bug report #874968, regarding [kover] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Processed: tagging 935086, tagging 935621, found 934815 in 0.1.2-1, found 934817 in 3.2.2+pristine-2 ...

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 935086 + experimental Bug #935086 [src:insighttoolkit4] insighttoolkit4: FTBFS with GCC-9: use of undeclared identifier '__builtin_is_constant_evaluated' Added tag(s) experimental. > tags 935621 + experimental Bug #935621

Bug#875074: marked as done ([openpref] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 23:34:53 + with message-id and subject line Bug#875074: fixed in openpref 0.1.3-3 has caused the Debian Bug report #875074, regarding [openpref] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt

Bug#934816: tcl8.6-tdbc-mysql: built with libmariadbclient18, which doesn't exist any longer

2019-08-24 Thread Andreas Beckmann
Control: severity -1 normal On Sat, 24 Aug 2019 17:11:10 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= wrote: > Increasing severity to 'serious' since this is one of the 5 packages > what still depend on libmariadbclient18, which will soon be removed > from unstable and then render this package

Processed: Re: tcl8.6-tdbc-mysql: built with libmariadbclient18, which doesn't exist any longer

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #934816 [tcl8.6-tdbc-mysql] tcl8.6-tdbc-mysql: built with libmariadbclient18, which doesn't exist any longer Severity set to 'normal' from 'serious' -- 934816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934816 Debian Bug Tracking

Bug#910902: Please test again: my_print_defaults and Akonadi for a freash installation

2019-08-24 Thread Andreas Beckmann
On Sun, 4 Aug 2019 18:45:28 +0100 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= wrote: > For some strange reason page https://tracker.debian.org/pkg/mariadb-10.3 > still says "Updating mariadb-10.3 introduces new bugs: #910902". > > Do you Sandro have any ideas why that is? I think that was because the

Processed: tagging 910902, reassign 910902 to mariadb-server-core-10.3, fixed 910902 in 1:10.3.13-2

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # unblock the migration to testing > tags 910902 - buster Bug #910902 {Done: Otto Kekäläinen } [mariadb-server] resolveip is missing for a fresh installation of Akonadi Removed tag(s) buster. > reassign 910902 mariadb-server-core-10.3

Processed: tagging 910902

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # try to unblock the migration despite of cruft libmariadbclient18 in sid > tags 910902 + buster Bug #910902 {Done: Otto Kekäläinen } [mariadb-server] resolveip is missing for a fresh installation of Akonadi Added tag(s) buster. > thanks

Processed: notfixed 935094 in 5.2.7-1, fixed 935094 in 5.2.9-2 ..., fixed 935453 in 2.018-2 ..., affects 935453

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 935094 5.2.7-1 Bug #935094 {Done: Jörg-Volker Peetz } [src:linux] linux-image-5.2.0-2-amd64: USB 3 storage device not detected No longer marked as fixed in versions src:linux/5.2.7-1. > fixed 935094 5.2.9-2 Bug #935094 {Done:

Bug#875208: [tora] Future Qt4 removal from Buster

2019-08-24 Thread Moritz Mühlenhoff
On Sat, Aug 24, 2019 at 10:12:34PM +0200, Michael Meskes wrote: > > > It's now the last one, so if I don't hear back soon that someone > > > intends to > > > upgrade this to Qt5, I'll file for the rm. > > > > Adding the primary uploader to CC. > > I'm not using the tool anymore, nor do I have

Bug#935657: Please port and switch this package to Python 3 or remove it from Debian

2019-08-24 Thread Thomas Goirand
Package: calendarserver Version: 9.2+dfsg-1 Severity: serious Hi, We're trying to remove Python 2 from Bullseye. And I came across your package, which is still py2 only. Please switch it to Python 3. If that's not possible, then it's probably the time for your package to get removed from

Bug#935621: openstack-dashboard: incompatible with django 2.2

2019-08-24 Thread Thomas Goirand
Hi, I'm very much aware of this issue, but can't find a way to fix it myself. openstack_auth/views.py is using a login() function instead of the now required LoginView class. I'm not skilled enough in Django to do this myself, and upstream unfortunately doesn't feel it's urgent. Until this is

Bug#925664: marked as done (cura-engine: ftbfs with GCC-9)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 21:35:12 + with message-id and subject line Bug#925664: fixed in cura-engine 1:3.3.0-3 has caused the Debian Bug report #925664, regarding cura-engine: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#874825: [Pkg-kde-extras] Bug#874825: [appmenu-qt] Future Qt4 removal from Buster

2019-08-24 Thread Scott Kitterman
On Saturday, August 24, 2019 1:12:04 PM EDT Reiner Herrmann wrote: > There is a Qt5 port available at: https://launchpad.net/appmenu-qt5 I checked and it's dead. Not even in Ubuntu. Scott K

Bug#935277: marked as done (hostname: FTBFS when binNMUed)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 20:59:39 + with message-id and subject line Bug#935277: fixed in hostname 3.22 has caused the Debian Bug report #935277, regarding hostname: FTBFS when binNMUed to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#875208: [Pkg-kde-extras] Bug#875208: [tora] Future Qt4 removal from Buster

2019-08-24 Thread Scott Kitterman
On Saturday, August 24, 2019 4:12:34 PM EDT Michael Meskes wrote: > > > It's now the last one, so if I don't hear back soon that someone > > > intends to > > > upgrade this to Qt5, I'll file for the rm. > > > > Adding the primary uploader to CC. > > I'm not using the tool anymore, nor do I have

Bug#875208: [tora] Future Qt4 removal from Buster

2019-08-24 Thread Michael Meskes
> > It's now the last one, so if I don't hear back soon that someone > > intends to > > upgrade this to Qt5, I'll file for the rm. > > Adding the primary uploader to CC. I'm not using the tool anymore, nor do I have time to take care of it. The only reason why I didn't orphan it, is that

Bug#935639: Abandoned upstream

2019-08-24 Thread David Prévot
Package: phpunit-dbunit Version: 4.0.0-2 Severity: serious [ Filled as an RC-bug by the maintainer to see the package auto-removed from testing. ] Since this PHPUnit extension is abandoned upstream and nothing depends on it in Debian, there is a priori little point to keep this package in the

Bug#935628: marked as done (vim-gtk: symbol lookup error: gtk_icon_factory_add)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 14:55:37 -0400 with message-id <20190824185537.edlb4cqaa3sf5gdr@localhost> and subject line Re: Bug#935628: vim-gtk: symbol lookup error: gtk_icon_factory_add has caused the Debian Bug report #935628, regarding vim-gtk: symbol lookup error: gtk_icon_factory_add

Bug#874855: [codequery] Future Qt4 removal from Buster

2019-08-24 Thread Reiner Herrmann
Control: tags -1 + patch Dear maintainer, Qt5 is already supported and can be easily enabled with the attached patch (which also fixes #886193). Kind regards, Reiner diff -Nru codequery-0.21.1+dfsg1/debian/control codequery-0.21.1+dfsg1/debian/control --- codequery-0.21.1+dfsg1/debian/control

Bug#935616: marked as done (apcupsd: FTBFS on amd64)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 18:49:09 + with message-id and subject line Bug#935616: fixed in apcupsd 3.14.14-3 has caused the Debian Bug report #935616, regarding apcupsd: FTBFS on amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Re: [codequery] Future Qt4 removal from Buster

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #874855 [src:codequery] [codequery] Future Qt4 removal from Buster Added tag(s) patch. -- 874855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#935314: marked as done (trafficserver: CVE-2019-9518)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 18:23:33 + with message-id and subject line Bug#935314: fixed in trafficserver 8.0.5+ds-1 has caused the Debian Bug report #935314, regarding trafficserver: CVE-2019-9518 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#934887: marked as done (CVE-2019-9512 CVE-2019-9514 CVE-2019-9515)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 18:23:33 + with message-id and subject line Bug#934887: fixed in trafficserver 8.0.5+ds-1 has caused the Debian Bug report #934887, regarding CVE-2019-9512 CVE-2019-9514 CVE-2019-9515 to be marked as done. This means that you claim that the problem has

Bug#874844: [choreonoid] Future Qt4 removal from Buster

2019-08-24 Thread Reiner Herrmann
Control: tags -1 + fixed-upstream Qt5 is supported upstream since 1.5.0. signature.asc Description: PGP signature

Processed: Re: [choreonoid] Future Qt4 removal from Buster

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + fixed-upstream Bug #874844 [src:choreonoid] [choreonoid] Future Qt4 removal from Buster Added tag(s) fixed-upstream. -- 874844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874844 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: found 935585 in node-d3/4.13.0-3

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 935585 node-d3/4.13.0-3 Bug #935585 {Done: Pirate Praveen } [src:node-d3] node-d3-scale breaks node-d3 autopkgtest: SyntaxError: Unexpected token export Marked as found in versions node-d3/4.13.0-3. > thanks Stopping processing here.

Processed: found 935585 in node-d3/4.13.0-4

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 935585 node-d3/4.13.0-4 Bug #935585 {Done: Pirate Praveen } [src:node-d3] node-d3-scale breaks node-d3 autopkgtest: SyntaxError: Unexpected token export Marked as found in versions node-d3/4.13.0-4. > thanks Stopping processing here.

Processed: fixed 935585 in node-d3/4.13.0-5

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 935585 node-d3/4.13.0-5 Bug #935585 {Done: Pirate Praveen } [src:node-d3] node-d3-scale breaks node-d3 autopkgtest: SyntaxError: Unexpected token export The source node-d3 and version 4.13.0-5 do not appear to match any binary packages

Processed: reassign 935585 to src:node-d3

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 935585 src:node-d3 Bug #935585 {Done: Pirate Praveen } [src:node-d3-scale, src:node-d3] node-d3-scale breaks node-d3 autopkgtest: SyntaxError: Unexpected token export Bug reassigned from package 'src:node-d3-scale, src:node-d3' to

Bug#935453: marked as done (libconfig-model-tkui-perl breaks libconfig-model-itself-perl autopkgtest)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 17:35:57 + with message-id and subject line Bug#935453: fixed in libconfig-model-itself-perl 2.018-2 has caused the Debian Bug report #935453, regarding libconfig-model-tkui-perl breaks libconfig-model-itself-perl autopkgtest to be marked as done. This

Bug#934960: marked as done (python-mock breaks pytest-mock autopkgtest)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 17:23:17 + with message-id and subject line Bug#934960: fixed in pytest-mock 1.10.4-1 has caused the Debian Bug report #934960, regarding python-mock breaks pytest-mock autopkgtest to be marked as done. This means that you claim that the problem has been

Bug#935585: marked as done (node-d3-scale breaks node-d3 autopkgtest: SyntaxError: Unexpected token export)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 17:21:08 + with message-id and subject line Bug#935585: fixed in node-d3 4.13.0-5 has caused the Debian Bug report #935585, regarding node-d3-scale breaks node-d3 autopkgtest: SyntaxError: Unexpected token export to be marked as done. This means that you

Bug#874825: [appmenu-qt] Future Qt4 removal from Buster

2019-08-24 Thread Reiner Herrmann
There is a Qt5 port available at: https://launchpad.net/appmenu-qt5 signature.asc Description: PGP signature

Bug#935568: sphinx-issuetracker: should this package be removed?

2019-08-24 Thread Dmitry Shachnev
Hi Sandro! On Fri, Aug 23, 2019 at 10:46:30PM -0400, Sandro Tosi wrote: > Hello, > sphinx-issuetracker is currently incompatible with python3.7: > [...] > > It has no reverse-dependencies and it's currently one of the few r-deps of > python-debianbts. > > Should we just remove this package from

Bug#935453: libconfig-model-tkui-perl breaks libconfig-model-itself-perl autopkgtest

2019-08-24 Thread Dominique Dumont
On vendredi 23 août 2019 21:37:34 CEST you wrote: > - ./Build realclean; perl Build.PL > - prove fails Do'h.. I'm so used to type "perl -Ilib t/*.t" that I forgot to remove the '- Ilib'. Now I can reproduce this issue. Turns out that the issue can be fixed in t/load_write_itself.t. I'm going

Processed: Bug#934960 marked as pending in pytest-mock

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #934960 [src:python-mock, src:pytest-mock] python-mock breaks pytest-mock autopkgtest Added tag(s) pending. -- 934960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934960 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#934960: marked as pending in pytest-mock

2019-08-24 Thread Ondřej Nový
Control: tag -1 pending Hello, Bug #934960 in pytest-mock 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 (with 2 errors): your mail

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 934959 src:sunpy 0.9.6-2 Bug #934959 [src:python-mock, src:sunpy] python-mock breaks sunpy autopkgtest Bug reassigned from package 'src:python-mock, src:sunpy' to 'src:sunpy'. No longer marked as found in versions sunpy/0.9.6-2 and

Bug#934959:

2019-08-24 Thread Ondrej Novy
reassign 934959 src:sunpy 0.9.6-2 thx This is bug in sunpy, using StopIteration in newer Python 3. Thanks. -- Best regards Ondřej Nový

Bug#935628: vim-gtk: symbol lookup error: gtk_icon_factory_add

2019-08-24 Thread Rob Evans
Package: vim-gtk Version: 2:7.4.488-7+deb8u4 Severity: serious Justification: Policy 3.5 Dear Maintainer, * What led up to the situation? New install of Raspian including this package. Error occurs when I try to edit a file with vim: $ vim .hpodder/hpodder.conf vim:

Bug#819641: Fwd: urgent

2019-08-24 Thread Rep
I'm a legal adviser, I seek your consent for a claim of sum $5.5 million belonging to my late client who was an investor. if you are interested i will present you as foreign partner,all legal documents is in my jurisdiction to ensure the fund is transfer to your name and favor, I wait to discuss

Processed: Re: Bug#935620: thrift: FTBFS on amd64

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +confirmed Bug #935620 [src:thrift] thrift: FTBFS on amd64 Added tag(s) confirmed. -- 935620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#935620: thrift: FTBFS on amd64

2019-08-24 Thread GCS
Control: tags -1 +confirmed On Sat, Aug 24, 2019 at 4:06 PM Ivo De Decker wrote: > A binnmu of thrift in unstable fails on amd64: Indeed and I've a fix for this. However I would like to add a Python 3 package and don't know if it's accepted automatically or have to go through the NEW queue.

Bug#933591: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 15:49:02 + with message-id and subject line Bug#933591: fixed in yade 2019.01a-3 has caused the Debian Bug report #933591, regarding BD on texlive-generic-extra which isn't build anymore and isn't in bullseye to be marked as done. This means that you

Bug#935584: marked as done (octave-octclip FTBFS in bullseye, "fgeneral.c:270:8: error: 'nDatos' is predetermined 'shared' for 'shared'")

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 15:45:08 + with message-id and subject line Bug#935584: fixed in octave-octclip 1.0.8-7 has caused the Debian Bug report #935584, regarding octave-octclip FTBFS in bullseye, "fgeneral.c:270:8: error: 'nDatos' is predetermined 'shared' for 'shared'" to be

Bug#875068: marked as done ([openambit] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 15:44:05 + with message-id and subject line Bug#935610: Removed package(s) from unstable has caused the Debian Bug report #875068, regarding [openambit] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#875321: marked as done (QJson removal form Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 15:44:05 + with message-id and subject line Bug#935610: Removed package(s) from unstable has caused the Debian Bug report #875321, regarding QJson removal form Buster to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#875327: marked as done (QJson removal in Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 15:44:05 + with message-id and subject line Bug#935610: Removed package(s) from unstable has caused the Debian Bug report #875321, regarding QJson removal in Buster to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#875222: marked as done ([valkyrie] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 15:43:08 + with message-id and subject line Bug#935600: Removed package(s) from unstable has caused the Debian Bug report #875222, regarding [valkyrie] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#874892: marked as done ([gnudoq] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 15:43:40 + with message-id and subject line Bug#935603: Removed package(s) from unstable has caused the Debian Bug report #874892, regarding [gnudoq] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#875134: marked as done ([qemuctl] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 15:41:14 + with message-id and subject line Bug#935597: Removed package(s) from unstable has caused the Debian Bug report #875134, regarding [qemuctl] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#900771: marked as done (yubikey-ksm: depends on php-mcrypt which is no longer available in php7.2)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 15:40:00 + with message-id and subject line Bug#935594: Removed package(s) from unstable has caused the Debian Bug report #900771, regarding yubikey-ksm: depends on php-mcrypt which is no longer available in php7.2 to be marked as done. This means that

Bug#875136: marked as done ([qmpdclient] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 15:34:16 + with message-id and subject line Bug#935558: Removed package(s) from unstable has caused the Debian Bug report #875136, regarding [qmpdclient] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Processed: tcl8.6-tdbc-mysql: built with libmariadbclient18, which doesn't exist any longer

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #934816 [tcl8.6-tdbc-mysql] tcl8.6-tdbc-mysql: built with libmariadbclient18, which doesn't exist any longer Severity set to 'serious' from 'normal' -- 934816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934816 Debian Bug Tracking

Processed: libdballe7: built with libmariadbclient18, which doesn't exist any longer

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #934814 [libdballe7] libdballe7: built with libmariadbclient18, which doesn't exist any longer Severity set to 'serious' from 'normal' -- 934814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934814 Debian Bug Tracking System Contact

Processed: libmysql++3v5: built with libmariadbclient18, which doesn't exist any longer

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #934817 [libmysql++3v5] libmysql++3v5: built with libmariadbclient18, which doesn't exist any longer Severity set to 'serious' from 'normal' -- 934817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934817 Debian Bug Tracking System

Processed: libquickfix16: built with libmariadbclient18, which doesn't exist any longer

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #934818 [libquickfix16] libquickfix16: built with libmariadbclient18, which doesn't exist any longer Severity set to 'serious' from 'normal' -- 934818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934818 Debian Bug Tracking System

Processed: user debian...@lists.debian.org, affects 876686, affects 934021, affects 934643

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > affects 876686 + check-mk-server Bug #876686 [check-mk-config-icinga] check-mk-config-icinga: file conflict with check-mk-common:

Processed: mosquitto-auth-plugin: built with libmariadbclient18, which doesn't exist any longer

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #934815 [mosquitto-auth-plugin] mosquitto-auth-plugin: built with libmariadbclient18, which doesn't exist any longer Severity set to 'serious' from 'normal' -- 934815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934815 Debian Bug

Processed: stardict-tools: built with libmariadbclient18, which doesn't exist any longer

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #934819 [stardict-tools] stardict-tools: built with libmariadbclient18, which doesn't exist any longer Severity set to 'serious' from 'normal' -- 934819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934819 Debian Bug Tracking System

Processed: Re: node-d3-scale breaks node-d3 autopkgtest: SyntaxError: Unexpected token export

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 930920 Bug #935585 [src:node-d3-scale, src:node-d3] node-d3-scale breaks node-d3 autopkgtest: SyntaxError: Unexpected token export 935585 was not blocked by any bugs. 935585 was not blocking any bugs. Added blocking bug(s) of 935585: 930920 -- 935585:

Bug#935585: node-d3-scale breaks node-d3 autopkgtest: SyntaxError: Unexpected token export

2019-08-24 Thread Pirate Praveen
Control: block -1 by 930920 On Sat, 24 Aug 2019 11:29:57 +0200 Paul Gevers wrote: > autopkgtest [18:11:04]: test require: [--- > /usr/lib/nodejs/d3/node_modules/d3-scale/index.js:1 > (function (exports, require, module, __filename, __dirname) { export { >

Bug#934643: marked as done (libparlatype2: missing Breaks+Replaces: libparlatype1)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 14:57:10 + with message-id and subject line Bug#934643: fixed in parlatype 1.6.1-2 has caused the Debian Bug report #934643, regarding libparlatype2: missing Breaks+Replaces: libparlatype1 to be marked as done. This means that you claim that the problem

Bug#935584: marked as pending in octave-octclip

2019-08-24 Thread Rafael Laboissiere
Control: tag -1 pending Hello, Bug #935584 in octave-octclip 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#935584 marked as pending in octave-octclip

2019-08-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #935584 [octave-octclip] octave-octclip FTBFS in bullseye, "fgeneral.c:270:8: error: 'nDatos' is predetermined 'shared' for 'shared'" Added tag(s) pending. -- 935584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935584 Debian Bug Tracking

Processed: severity of 935577 is serious

2019-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935577 serious Bug #935577 [src:debhelper] debhelper: dh_makeshlibs confused by --add-udeb (broken in 12.5.3) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#874823: marked as done ([ams] Future Qt4 removal from Buster)

2019-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2019 14:42:41 + with message-id and subject line Bug#874823: fixed in ams 2.1.2-1 has caused the Debian Bug report #874823, regarding [ams] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with. If

  1   2   >