Bug#938013: marked as done (python-peak.rules: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:18:43 + with message-id and subject line Bug#948162: Removed package(s) from unstable has caused the Debian Bug report #938013, regarding python-peak.rules: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#938727: marked as done (turbojson: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:17:38 + with message-id and subject line Bug#948162: Removed package(s) from unstable has caused the Debian Bug report #938727, regarding turbojson: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#948162: marked as done (RM: python-peak.util -- RoQA; python2-only; combination of modules most of which deprecated, no py3k available)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:17:35 + with message-id and subject line Bug#948162: Removed package(s) from unstable has caused the Debian Bug report #948162, regarding RM: python-peak.util -- RoQA; python2-only; combination of modules most of which deprecated, no py3k available to be

Bug#938712: marked as done (trac-wikiprint: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:06:43 + with message-id and subject line Bug#948068: Removed package(s) from unstable has caused the Debian Bug report #938712, regarding trac-wikiprint: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#938713: marked as done (trac-wikitablemacro: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:07:09 + with message-id and subject line Bug#948069: Removed package(s) from unstable has caused the Debian Bug report #938713, regarding trac-wikitablemacro: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the proble

Bug#938714: marked as done (trac-wysiwyg: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:07:44 + with message-id and subject line Bug#948070: Removed package(s) from unstable has caused the Debian Bug report #938714, regarding trac-wysiwyg: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

Bug#938701: marked as done (trac-odtexport: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:03:56 + with message-id and subject line Bug#948062: Removed package(s) from unstable has caused the Debian Bug report #938701, regarding trac-odtexport: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#866487: marked as done (trac-odtexport: depends on obsolete python-imaging (replace with python3-pil or python-pil))

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:03:56 + with message-id and subject line Bug#948062: Removed package(s) from unstable has caused the Debian Bug report #866487, regarding trac-odtexport: depends on obsolete python-imaging (replace with python3-pil or python-pil) to be marked as done. T

Bug#938711: marked as done (trac-virtualticketpermissions: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:06:20 + with message-id and subject line Bug#948067: Removed package(s) from unstable has caused the Debian Bug report #938711, regarding trac-virtualticketpermissions: Python2 removal in sid/bullseye to be marked as done. This means that you claim that

Bug#938707: marked as done (trac-subcomponents: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:05:20 + with message-id and subject line Bug#948065: Removed package(s) from unstable has caused the Debian Bug report #938707, regarding trac-subcomponents: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#938705: marked as done (trac-sensitivetickets: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:04:46 + with message-id and subject line Bug#948064: Removed package(s) from unstable has caused the Debian Bug report #938705, regarding trac-sensitivetickets: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the prob

Bug#938710: marked as done (trac-translatedpages: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:05:48 + with message-id and subject line Bug#948066: Removed package(s) from unstable has caused the Debian Bug report #938710, regarding trac-translatedpages: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the probl

Bug#889277: marked as done (trac-privatetickets is empty)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:04:21 + with message-id and subject line Bug#948063: Removed package(s) from unstable has caused the Debian Bug report #889277, regarding trac-privatetickets is empty to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#938698: marked as done (trac-mastertickets: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:03:31 + with message-id and subject line Bug#948061: Removed package(s) from unstable has caused the Debian Bug report #938698, regarding trac-mastertickets: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#938715: marked as done (trac-xmlrpc: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:00:52 + with message-id and subject line Bug#948055: Removed package(s) from unstable has caused the Debian Bug report #938715, regarding trac-xmlrpc: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has be

Bug#938709: marked as done (trac-tags: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:00:06 + with message-id and subject line Bug#948053: Removed package(s) from unstable has caused the Debian Bug report #938709, regarding trac-tags: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#938708: marked as done (trac-subtickets: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:00:31 + with message-id and subject line Bug#948054: Removed package(s) from unstable has caused the Debian Bug report #938708, regarding trac-subtickets: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem ha

Bug#938703: marked as done (trac-privatewiki: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:01:38 + with message-id and subject line Bug#948057: Removed package(s) from unstable has caused the Debian Bug report #938703, regarding trac-privatewiki: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem h

Bug#938704: marked as done (trac-roadmap: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:01:16 + with message-id and subject line Bug#948056: Removed package(s) from unstable has caused the Debian Bug report #938704, regarding trac-roadmap: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

Bug#938697: marked as done (trac-jsgantt: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:03:00 + with message-id and subject line Bug#948060: Removed package(s) from unstable has caused the Debian Bug report #938697, regarding trac-jsgantt: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

Bug#938700: marked as done (trac-navadd: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:01:59 + with message-id and subject line Bug#948058: Removed package(s) from unstable has caused the Debian Bug report #938700, regarding trac-navadd: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has be

Bug#938699: marked as done (trac-mercurial: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:02:30 + with message-id and subject line Bug#948059: Removed package(s) from unstable has caused the Debian Bug report #938699, regarding trac-mercurial: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#787722: marked as done (trac-mercurial: Upstream Defect #11696 applies to Jessie, too)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 06:02:30 + with message-id and subject line Bug#948059: Removed package(s) from unstable has caused the Debian Bug report #787722, regarding trac-mercurial: Upstream Defect #11696 applies to Jessie, too to be marked as done. This means that you claim that t

Bug#938695: marked as done (trac-icalview: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:57:51 + with message-id and subject line Bug#948046: Removed package(s) from unstable has caused the Debian Bug report #938695, regarding trac-icalview: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#938694: marked as done (trac-httpauth: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:57:09 + with message-id and subject line Bug#948044: Removed package(s) from unstable has caused the Debian Bug report #938694, regarding trac-httpauth: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#938688: marked as done (trac-customfieldadmin: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:58:55 + with message-id and subject line Bug#948049: Removed package(s) from unstable has caused the Debian Bug report #938688, regarding trac-customfieldadmin: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the prob

Bug#938690: marked as done (trac-diavisview: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:58:34 + with message-id and subject line Bug#948048: Removed package(s) from unstable has caused the Debian Bug report #938690, regarding trac-diavisview: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem ha

Bug#938689: marked as done (trac-datefield: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:58:13 + with message-id and subject line Bug#948047: Removed package(s) from unstable has caused the Debian Bug report #938689, regarding trac-datefield: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#938683: marked as done (trac-accountmanager: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:59:43 + with message-id and subject line Bug#948051: Removed package(s) from unstable has caused the Debian Bug report #938683, regarding trac-accountmanager: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the proble

Bug#938696: marked as done (trac-includemacro: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:57:30 + with message-id and subject line Bug#948045: Removed package(s) from unstable has caused the Debian Bug report #938696, regarding trac-includemacro: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#938684: marked as done (trac-announcer: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:59:16 + with message-id and subject line Bug#948050: Removed package(s) from unstable has caused the Debian Bug report #938684, regarding trac-announcer: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#938685: marked as done (trac-authopenid: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:56:17 + with message-id and subject line Bug#948042: Removed package(s) from unstable has caused the Debian Bug report #938685, regarding trac-authopenid: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem ha

Bug#938693: marked as done (trac-graphviz: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:56:40 + with message-id and subject line Bug#948043: Removed package(s) from unstable has caused the Debian Bug report #938693, regarding trac-graphviz: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#895282: marked as done (trac-authopenid: fails to work with trac 1.2 (get_db_cnx does not work))

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:56:17 + with message-id and subject line Bug#948042: Removed package(s) from unstable has caused the Debian Bug report #895282, regarding trac-authopenid: fails to work with trac 1.2 (get_db_cnx does not work) to be marked as done. This means that you c

Bug#936543: marked as done (fontypython: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:52:57 + with message-id and subject line Bug#943872: Removed package(s) from unstable has caused the Debian Bug report #936543, regarding fontypython: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has be

Bug#855494: marked as done (mgltools-pmv: runPmv script does not work: ImportError: No module named oldnumeric)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:51:40 + with message-id and subject line Bug#855701: Removed package(s) from unstable has caused the Debian Bug report #855494, regarding mgltools-pmv: runPmv script does not work: ImportError: No module named oldnumeric to be marked as done. This means

Bug#855485: marked as done (mgltools-pmv: runPmv script does not work: TclError: cannot use geometry manager grid)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:51:40 + with message-id and subject line Bug#855701: Removed package(s) from unstable has caused the Debian Bug report #855485, regarding mgltools-pmv: runPmv script does not work: TclError: cannot use geometry manager grid to be marked as done. This me

Bug#798738: marked as done (fontypython: Fonty Python doesn't start, throws wx._core.PyAssertionError)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:52:57 + with message-id and subject line Bug#943872: Removed package(s) from unstable has caused the Debian Bug report #798738, regarding fontypython: Fonty Python doesn't start, throws wx._core.PyAssertionError to be marked as done. This means that you

Bug#914884: marked as done (Crashes with wx._core.PyAssertionError: C++ assertion "isOpaque" failed..)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:52:57 + with message-id and subject line Bug#943872: Removed package(s) from unstable has caused the Debian Bug report #798738, regarding Crashes with wx._core.PyAssertionError: C++ assertion "isOpaque" failed.. to be marked as done. This means that you

Bug#938827: marked as done (RM: winpdb -- RoQA; semi-dead upstream; unmaintained; low popcon; blocking py2 removal)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:52:08 + with message-id and subject line Bug#938827: Removed package(s) from unstable has caused the Debian Bug report #938827, regarding RM: winpdb -- RoQA; semi-dead upstream; unmaintained; low popcon; blocking py2 removal to be marked as done. This m

Bug#948452: closing 948452

2020-01-08 Thread Salvatore Bonaccorso
close 948452 72.0.1-1 thanks

Processed: closing 948452

2020-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 948452 72.0.1-1 Bug #948452 {Done: Mike Hommey } [firefox] firefox: Please update to 72.0.1 (and firefox-esr to 68.4.1) because of CVE-2019-17026 Marked as fixed in versions firefox/72.0.1-1; no longer marked as fixed in versions 72.0.1-1.

Bug#937944: marked as done (python-networkx: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 05:49:48 + with message-id and subject line Bug#948431: Removed package(s) from unstable has caused the Debian Bug report #937944, regarding python-networkx: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem ha

Processed: Re: Bug#948473: cain: should this package be removed?

2020-01-08 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 keep cain out of testing Bug #948473 [src:cain] cain: should this package be removed? Changed Bug title to 'keep cain out of testing' from 'cain: should this package be removed?'. -- 948473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948473 Debia

Bug#948473: cain: should this package be removed?

2020-01-08 Thread Sandro Tosi
control: retitle -1 keep cain out of testing On Thu, Jan 9, 2020 at 12:12 AM Andreas Tille wrote: > > Hi Sandro, > > On Wed, Jan 08, 2020 at 09:28:16PM -0500, Sandro Tosi wrote: > > > > * python2-only > > * no upstream release since July 2012 (not even advertized on their HP) > > * low popcon (bu

Bug#948473: cain: should this package be removed?

2020-01-08 Thread Andreas Tille
Hi Sandro, On Wed, Jan 08, 2020 at 09:28:16PM -0500, Sandro Tosi wrote: > > * python2-only > * no upstream release since July 2012 (not even advertized on their HP) > * low popcon (but it's also probably part of a niche package) I once gave it a try with 2to3 but failed. I intend to give it ano

Bug#948404: glances crashes on startup

2020-01-08 Thread Daniel Echeverry
tags 948404 + moreinfo unreproducible thanks Hi! Thanks for your report! Unfortunately I can't reproduce this bug, I install glances via ap-get install and works fine, However, I think that bug is related with this other bug[1], One Question, Do you have network interfaces? Regards. [1]: http

Processed: Re: Bug#948404: glances crashes on startup

2020-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 948404 + moreinfo unreproducible Bug #948404 [glances] glances crashes on startup Added tag(s) unreproducible and moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 948404: https://bugs.debian.org/cgi-

Bug#943052: marked as done (distro-info: Python2 removal in sid/bullseye)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 09 Jan 2020 04:19:16 + with message-id and subject line Bug#943052: fixed in distro-info 0.23 has caused the Debian Bug report #943052, regarding distro-info: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Bug#943052: marked as pending in distro-info

2020-01-08 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #943052 in distro-info 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: https://salsa.debian.org/debian/distro-info/commit/723f1a6ca4f386c371dea4e15f6d

Processed: Bug#943052 marked as pending in distro-info

2020-01-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #943052 [src:distro-info] distro-info: Python2 removal in sid/bullseye Added tag(s) pending. -- 943052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: py2removal bugs severity updates - 2020-01-09 03:36:13.627321+00:00

2020-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-an

Bug#948473: cain: should this package be removed?

2020-01-08 Thread Sandro Tosi
Source: cain Severity: serious Hello, it seems to me there are several issues with this package: * python2-only * no upstream release since July 2012 (not even advertized on their HP) * low popcon (but it's also probably part of a niche package) * one of the only 2 reverse-dependency for python-s

Processed: Re: /usr/bin/tifffile doesn't work

2020-01-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #939511 {Done: Andreas Tille } [tifffile] /usr/bin/tifffile doesn't work Added tag(s) pending. -- 939511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#939511: /usr/bin/tifffile doesn't work

2020-01-08 Thread Andreas Beckmann
Followup-For: Bug #939511 Control: tag -1 pending buster-pu request: https://bugs.debian.org/948472 Andreas

Bug#948452: marked as done (firefox: Please update to 72.0.1 (and firefox-esr to 68.4.1) because of CVE-2019-17026)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 9 Jan 2020 09:26:57 +0900 with message-id <20200109002657.nglycrd6zctvo...@glandium.org> and subject line Re: Bug#948452: firefox: Please update to 72.0.1 (and firefox-esr to 68.4.1) because of CVE-2019-17026 has caused the Debian Bug report #948452, regarding firefox: Plea

Bug#947865: marked as done (pyopencl: FTBFS in sid)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Thu, 9 Jan 2020 00:38:32 +0100 with message-id and subject line Re: [Pkg-opencl-devel] Bug#947865: pyopencl: FTBFS in sid has caused the Debian Bug report #947865, regarding pyopencl: FTBFS in sid to be marked as done. This means that you claim that the problem has been dealt w

Bug#947712: autopkgtest regressions in python-dbusmock with newer network-manager 1.22.2-1

2020-01-08 Thread Martin Pitt
Hello Michael and Thomas, Michael Biebl [2020-01-08 19:42 +0100]: > > The latest update of network-manager causes an autopkgtest regression in > > python-dbusmock. > > > > https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/3793816/log.gz > > > > ==

Processed: Re: pykaraoke: Pykaraoke doesn't work because it needs packages "ttf-dejavu ttf-dejavu-extra"

2020-01-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #948385 [src:pykaraoke] pykaraoke: Pykaraoke doesn't work because it needs packages "ttf-dejavu ttf-dejavu-extra" Added tag(s) pending. > found -1 0.7.5-1.2 Bug #948385 [src:pykaraoke] pykaraoke: Pykaraoke doesn't work because it needs packages "

Bug#948385: pykaraoke: Pykaraoke doesn't work because it needs packages "ttf-dejavu ttf-dejavu-extra"

2020-01-08 Thread Andreas Beckmann
Followup-For: Bug #948385 Control: tag -1 pending Control: found -1 0.7.5-1.2 No need for the transitional ttf-* packages, just fix the symlinks: s/ttf-//. buster-pu: https://bugs.debian.org/948464 stretch-pu: https://bugs.debian.org/948465 Andreas

Bug#947613: [Pkg-utopia-maintainers] Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1

2020-01-08 Thread Eugen Dedu
On 08/01/2020 16:07, Michael Biebl wrote: Anyone willing to check the proposed fix https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/848b869c6ede3a796872a0b5cd8b2398804c3697 Hi, I tested the proposed patch on top of debian's 1.22.2-1 version. This patch does NOT fix the iss

Bug#948417: marked as done (python-astor ftbfs with Python 3.8)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Jan 2020 22:08:53 + with message-id and subject line Bug#948417: fixed in python-astor 0.8.1-1 has caused the Debian Bug report #948417, regarding python-astor ftbfs with Python 3.8 to be marked as done. This means that you claim that the problem has been dealt with

Bug#948460: xserver-xorg-video-nvidia-legacy-340xx: Xorg won't start with xserver-xorg-video-nvidia-legacy-340xx on testing/Bullseye

2020-01-08 Thread Andreas Beckmann
On 08/01/2020 21.53, Alexis wrote: > So I installed packages to use the nvidia proprietary drivers (xserver-xorg- > video-nvidia-legacy-340xx and related packages). You didn't install the metapackage nvidia-legacy-340xx-driver, did you? > pn nvidia-legacy-340xx-driver

Bug#930764: marked as done (Fails to configure package due to "unknown type of DB: BACKUP" on upgrade-db)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Jan 2020 21:47:08 + with message-id and subject line Bug#930764: fixed in cyrus-imapd 3.0.8-6+deb10u4 has caused the Debian Bug report #930764, regarding Fails to configure package due to "unknown type of DB: BACKUP" on upgrade-db to be marked as done. This means t

Bug#946937: marked as done (python-django: CVE-2019-19844: Potential account hijack via password reset form)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Jan 2020 21:47:38 + with message-id and subject line Bug#946937: fixed in python-django 1:1.10.7-2+deb9u7 has caused the Debian Bug report #946937, regarding python-django: CVE-2019-19844: Potential account hijack via password reset form to be marked as done. This

Bug#946937: marked as done (python-django: CVE-2019-19844: Potential account hijack via password reset form)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Jan 2020 21:47:11 + with message-id and subject line Bug#946937: fixed in python-django 1:1.11.27-1~deb10u1 has caused the Debian Bug report #946937, regarding python-django: CVE-2019-19844: Potential account hijack via password reset form to be marked as done. Thi

Bug#941266: marked as done (netty: CVE-2019-16869)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Jan 2020 21:47:37 + with message-id and subject line Bug#941266: fixed in netty 1:4.1.7-2+deb9u1 has caused the Debian Bug report #941266, regarding netty: CVE-2019-16869 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#930774: marked as done (guile-2.2: FTBFS when built with dpkg-buildpackage -A)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Jan 2020 21:47:09 + with message-id and subject line Bug#930774: fixed in guile-2.2 2.2.4+1-2+deb10u1 has caused the Debian Bug report #930774, regarding guile-2.2: FTBFS when built with dpkg-buildpackage -A to be marked as done. This means that you claim that the p

Bug#944820: marked as done (SimpleSAMLphp fails when consuming assertion)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Jan 2020 21:47:13 + with message-id and subject line Bug#944820: fixed in simplesamlphp 1.16.3-1+deb10u2 has caused the Debian Bug report #944820, regarding SimpleSAMLphp fails when consuming assertion to be marked as done. This means that you claim that the problem

Bug#945864: marked as done (unhide[208429]: segfault at 7ffd06cfec58 ip 000055c15aa077d3 sp 00007ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000])

2020-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Jan 2020 21:47:14 + with message-id and subject line Bug#945864: fixed in unhide 20130526-3+deb10u1 has caused the Debian Bug report #945864, regarding unhide[208429]: segfault at 7ffd06cfec58 ip 55c15aa077d3 sp 7ffd06cfec60 error 6 in unhide-linux[55c15aa07

Processed: your mail

2020-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 948426 + pending Bug #948426 [src:python-whoosh] python-whoosh ftbfs in unstable Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 948426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Processed: Bug#948417 marked as pending in python-astor

2020-01-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #948417 [src:python-astor] python-astor ftbfs with Python 3.8 Added tag(s) pending. -- 948417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#948417: marked as pending in python-astor

2020-01-08 Thread Tianon Gravi
Control: tag -1 pending Hello, Bug #948417 in python-astor 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: https://salsa.debian.org/python-team/modules/python-astor/commit/77a011ab0cdb6

Bug#947679: qsynth: FTBFS on s390x: lrelease error: Parse error ... qsynth_sr.ts:734:29: Premature end of document.

2020-01-08 Thread Lisandro Damián Nicanor Pérez Meyer
Hi! El mié., 8 ene. 2020 18:08, Sebastian Ramacher escribió: > Control: tags -1 + help moreinfo > > On 2019-12-28 22:12:34, Lisandro Damián Nicanor Pérez Meyer wrote: > > Source: qsynth > > Version: 0.6.0-1 > > Severity: serious > > Justification: FTBFS on s390x > > > > Hi! Your package failed t

Processed: Re: Bug#947679: qsynth: FTBFS on s390x: lrelease error: Parse error ... qsynth_sr.ts:734:29: Premature end of document.

2020-01-08 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + help moreinfo Bug #947679 [src:qsynth] qsynth: FTBFS on s390x: lrelease error: Parse error ... qsynth_sr.ts:734:29: Premature end of document. Added tag(s) moreinfo and help. -- 947679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947679 Debian Bug

Bug#947679: qsynth: FTBFS on s390x: lrelease error: Parse error ... qsynth_sr.ts:734:29: Premature end of document.

2020-01-08 Thread Sebastian Ramacher
Control: tags -1 + help moreinfo On 2019-12-28 22:12:34, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: qsynth > Version: 0.6.0-1 > Severity: serious > Justification: FTBFS on s390x > > Hi! Your package failed to build from source on s390x with the following > error: > > lrelease error: P

Bug#948460: xserver-xorg-video-nvidia-legacy-340xx: Xorg won't start with xserver-xorg-video-nvidia-legacy-340xx on testing/Bullseye

2020-01-08 Thread Alexis
Package: xserver-xorg-video-nvidia-legacy-340xx Version: 340.108-2 Severity: grave Justification: renders package unusable Dear Maintainer, first things first, happy new year to all ! I've been using Debian since Potato and I've always found it stable so far. On 5th january I did a fresh install

Bug#948459: sympy breaks yt autopkgtest: FAIL: Create units with strings and check attributes.

2020-01-08 Thread Paul Gevers
Source: sympy, yt Control: found -1 sympy/1.5-1 Control: found -1 yt/3.5.1-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of sympy the autopkgtest of yt fails in

Processed: sympy breaks yt autopkgtest: FAIL: Create units with strings and check attributes.

2020-01-08 Thread Debian Bug Tracking System
Processing control commands: > found -1 sympy/1.5-1 Bug #948459 [src:sympy, src:yt] sympy breaks yt autopkgtest: FAIL: Create units with strings and check attributes. Marked as found in versions sympy/1.5-1. > found -1 yt/3.5.1-2 Bug #948459 [src:sympy, src:yt] sympy breaks yt autopkgtest: FAIL:

Processed: sympy breaks octave-symbolic autopkgtest: unsupported operand type(s) for +: 'Singleton' and 'FiniteSet'

2020-01-08 Thread Debian Bug Tracking System
Processing control commands: > found -1 sympy/1.5-1 Bug #948458 [src:sympy, src:octave-symbolic] sympy breaks octave-symbolic autopkgtest: unsupported operand type(s) for +: 'Singleton' and 'FiniteSet' Marked as found in versions sympy/1.5-1. > found -1 octave-symbolic/2.8.0-1 Bug #948458 [src:sy

Bug#948458: sympy breaks octave-symbolic autopkgtest: unsupported operand type(s) for +: 'Singleton' and 'FiniteSet'

2020-01-08 Thread Paul Gevers
Source: sympy, octave-symbolic Control: found -1 sympy/1.5-1 Control: found -1 octave-symbolic/2.8.0-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of sympy the a

Bug#944742: fixed in assimp 5.0.0~ds2-4

2020-01-08 Thread Debian/GNU
(resending as a signed-mail, and with the TS included) On 05.01.20 10:27, Jochen Sprickerhof wrote: > I would propose to add the workaround for s390x and wait for new test > results for armhf resp. ignore them for ppc64el, as they where not > reproducible. If no one disagrees I will do a NMU and c

Processed: Re: python3-ownet: Python2-only code shipped in Python3 module

2020-01-08 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:owfs 3.2p3+dfsg1-2 Bug #943612 {Done: Vincent Danjean } [python3-ownet] python3-ownet: Python2-only code shipped in Python3 module Bug reassigned from package 'python3-ownet' to 'src:owfs'. No longer marked as found in versions owfs/3.2p3+dfsg1-2. No

Bug#947463: bio-tradis: autopkgtest regression: Use of uninitialized value $total_uis (and lots of mv: cannot stat '/tmp/aut.....)

2020-01-08 Thread Paul Gevers
Hi Micheal, On Fri, 3 Jan 2020 09:31:43 +0100 Michael Crusoe wrote: > > With a recent upload of bio-tradis the autopkgtest of bio-tradis fails > > in testing when that autopkgtest is run with the binary packages of > > bio-tradis from unstable. It passes when run with only packages from > > testi

Processed: tagging 948452, severity of 948452 is grave

2020-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 948452 + security Bug #948452 [firefox] firefox: Please update to 72.0.1 (and firefox-esr to 68.4.1) because of CVE-2019-17026 Added tag(s) security. > severity 948452 grave Bug #948452 [firefox] firefox: Please update to 72.0.1 (and firefox

Bug#943612: python3-ownet: Python2-only code shipped in Python3 module

2020-01-08 Thread Andreas Beckmann
Followup-For: Bug #943612 Control: reassign -1 src:owfs 3.2p3+dfsg1-2 Control: fixed -1 3.2p3+dfsg1-5 Control: tag -1 pending (Reassigning to the source package since the BTS does not understand that a removed python3-ownet is a fixed python3-ownet.) I've prepared a buster-pu request to drop the

Processed: Re: xserver-xorg-video-radeon 19.1 (ppc64) crash at startup: undefined symbol: exaGetPixmapDriverPrivate

2020-01-08 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #943664 [xserver-xorg-video-radeon] xserver-xorg-video-radeon 19.1 (ppc64) crash at startup: undefined symbol: exaGetPixmapDriverPrivate Severity set to 'important' from 'grave' -- 943664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Bug#942895: Fix buster vulnerability

2020-01-08 Thread Bharath Muraleedharan
Please fix this vulnerability in buster. https://security-tracker.debian.org/tracker/CVE-2019-18224 Thanks and Regards, Bharath The information contained in this e-mail message and any attachments is confidential. If the reader of this message is not the intende

Bug#943664: xserver-xorg-video-radeon 19.1 (ppc64) crash at startup: undefined symbol: exaGetPixmapDriverPrivate

2020-01-08 Thread Andreas Beckmann
Control: severity -1 important On Sun, 27 Oct 2019 16:59:23 +0100 "Ralf P." wrote: > Package: xserver-xorg-video-radeon > Version: 1:19.0.1-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > >on the ppc64 architecture the package Downgrading the severity

Bug#948455: ruby-byebug breaks ruby-pry-byebug autopkgtest: missing versioned Breaks

2020-01-08 Thread Paul Gevers
Source: ruby-byebug Version: 11.0.1-4 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks Dear maintainers, With a recent upload of ruby-byebug the autopkgtest of ruby-pry-byebug fails in testing when that autopkgtest is

Bug#948454: python-numpy: autopkgtest regression: tests/capi: 89: Syntax error: word unexpected (expecting ")")

2020-01-08 Thread Paul Gevers
Source: python-numpy Version: 1:1.16.5-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a (not so) recent upload of python-numpy the autopkgtest of python-numpy fails in testing when that autopkgtest is run w

Bug#948453: python-dmsh: autopkgtest regression: No module named 'perfplot'

2020-01-08 Thread Paul Gevers
Source: python-dmsh Version: 0.1.6-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of python-dmsh the autopkgtest of python-dmsh fails in testing when that autopkgtest is run with the binary

Bug#846695: kadu-mime-tex: FTBFS: mime_tex_plugin.h:12: Error: Undefined interface

2020-01-08 Thread Paul Gevers
Hi Patryk, On Sat, 3 Dec 2016 08:20:22 +0100 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. This bug hasn't seen any activity since it was filed and your package hasn't been part of testing for 3 years now. I intent to ask for its remova

Bug#945820: sysvinit: diff for NMU version 2.96-2.1

2020-01-08 Thread Boyuan Yang
Control: tags 945820 + patch Control: tags 945820 + pending Dear maintainer, I've prepared an NMU for sysvinit (versioned as 2.96-2.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. diff -Nru sysvinit-2.96/debian/changelog sysvinit-2.96/debian/ch

Processed: sysvinit: diff for NMU version 2.96-2.1

2020-01-08 Thread Debian Bug Tracking System
Processing control commands: > tags 945820 + patch Bug #945820 [src:sysvinit] sysvinit_2.96-2_amd64.changes REJECTED Added tag(s) patch. > tags 945820 + pending Bug #945820 [src:sysvinit] sysvinit_2.96-2_amd64.changes REJECTED Added tag(s) pending. -- 945820: https://bugs.debian.org/cgi-bin/bugr

Bug#948078: marked as done (autoconf-archive: please apply patch to fix boost_python library link)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Jan 2020 19:19:09 + with message-id and subject line Bug#948078: fixed in autoconf-archive 20190106-2.1 has caused the Debian Bug report #948078, regarding autoconf-archive: please apply patch to fix boost_python library link to be marked as done. This means that yo

Bug#948450: djview-plugin might be useless now

2020-01-08 Thread Adrian Bunk
Package: djview-plugin Version: 4.11-2 Severity: serious This package provides an NPAPI plugin. All major browsers have dropped support for NPAPI.

Bug#948449: garmin-plugin might be useless now

2020-01-08 Thread Adrian Bunk
Package: garmin-plugin Version: 0.3.23-5 Severity: serious This package provides an NPAPI plugin. All major browsers have dropped support for NPAPI.

Bug#947712: autopkgtest regressions in python-dbusmock with newer network-manager 1.22.2-1

2020-01-08 Thread Michael Biebl
On Sun, 29 Dec 2019 13:35:35 +0100 Michael Biebl wrote: > Package: network-manager, python-dbusmock > Version: 1.22.2-1 > Severity: serious > > The latest update of network-manager causes an autopkgtest regression in > python-dbusmock. > > https://ci.debian.net/data/autopkgtest/testing/amd64/p/p

Bug#771615: marked as done (python-lamson: non-functioning email address for Maintainer)

2020-01-08 Thread Debian Bug Tracking System
Your message dated Wed, 8 Jan 2020 19:16:33 +0100 with message-id <42ecf1b7-b69d-6e6b-bf3a-72aed3755...@debian.org> and subject line Re: python-lamson: non-functioning email address for Maintainer has caused the Debian Bug report #771615, regarding python-lamson: non-functioning email address for M

  1   2   >