Bug#946537: marked as done (chimeraslayer: depends on removed transitional package blast2)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 Dec 2019 07:49:12 + with message-id and subject line Bug#946537: fixed in microbiomeutil 20101212+dfsg1-3 has caused the Debian Bug report #946537, regarding chimeraslayer: depends on removed transitional package blast2 to be marked as done. This means that you

Processed: your mail

2019-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 945911 - moreinfo Bug #945911 {Done: Julian Andres Klode } [apt] only send credentials over https by default Removed tag(s) moreinfo. > severity 945911 critical Bug #945911 {Done: Julian Andres Klode } [apt] only send credentials over

Bug#911207: Fwd: stardict | close: #911207 (!1)

2019-12-11 Thread 肖盛文 Faris xiao
I create a merge request on salsa to fix this bug. Please see: https://salsa.debian.org/debian/stardict/merge_requests/1/diffs 转发的消息 主题: stardict | close: #911207 (!1) 日期: Thu, 12 Dec 2019 04:34:23 + 发件人:faris xiao 回复地址: Debian / stardict 收件人:

Bug#938909: zope.interface: Python2 removal in sid/bullseye

2019-12-11 Thread peter green
severity 938909 normal thanks Version 4.6.0-2 eliminates the unsatisfiable build-dependency and has migrated to testing. Returning this bug to normal severity.

Processed: re: zope.interface: Python2 removal in sid/bullseye

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

Bug#937562: marked as done (pytest-localserver: Python2 removal in sid/bullseye)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 Dec 2019 03:51:16 + with message-id and subject line Bug#937562: fixed in pytest-localserver 0.5.0-2 has caused the Debian Bug report #937562, regarding pytest-localserver: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#813383: marked as done (herwig++: FTBFS on i386: Floating point exception in check-LHC-Powheg target)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 Dec 2019 03:39:56 + with message-id and subject line Bug#946586: Removed package(s) from unstable has caused the Debian Bug report #813383, regarding herwig++: FTBFS on i386: Floating point exception in check-LHC-Powheg target to be marked as done. This means that

Bug#925840: marked as done (thepeg: ftbfs with GCC-9)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 Dec 2019 03:40:26 + with message-id and subject line Bug#946587: Removed package(s) from unstable has caused the Debian Bug report #925840, regarding thepeg: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug#937562 marked as pending in pytest-localserver

2019-12-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #937562 [src:pytest-localserver] pytest-localserver: Python2 removal in sid/bullseye Added tag(s) pending. -- 937562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937562 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#937562: marked as pending in pytest-localserver

2019-12-11 Thread Dimitri Ledkov
Control: tag -1 pending Hello, Bug #937562 in pytest-localserver 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:

Bug#944017: libsoxr: autopkgtest regression: segmentation fault

2019-12-11 Thread Bernhard Übelacker
Hello Adrian, hello Paul, I could reproduce the issue in a minimal revertable Unstable qemu VM with this command: /usr/bin/autopkgtest libsoxr -- null As far as I see the test is called this way: src/debian/tests/inst-check src/inst-check src/inst-check-soxr

Bug#934850: marked as done (bat: missing Breaks+Replaces: bareos-bat)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 Dec 2019 01:20:30 + with message-id and subject line Bug#934850: fixed in rust-bat 0.12.1-1 has caused the Debian Bug report #934850, regarding bat: missing Breaks+Replaces: bareos-bat to be marked as done. This means that you claim that the problem has been dealt

Bug#935578: marked as done (bat: bacula-console-qt already ships /usr/sbin/bat (and /usr/share/man/man1/bat.1.gz))

2019-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 Dec 2019 01:20:30 + with message-id and subject line Bug#934850: fixed in rust-bat 0.12.1-1 has caused the Debian Bug report #934850, regarding bat: bacula-console-qt already ships /usr/sbin/bat (and /usr/share/man/man1/bat.1.gz) to be marked as done. This means

Bug#935578: marked as done (bat: bacula-console-qt already ships /usr/sbin/bat (and /usr/share/man/man1/bat.1.gz))

2019-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 Dec 2019 01:20:30 + with message-id and subject line Bug#935578: fixed in rust-bat 0.12.1-1 has caused the Debian Bug report #935578, regarding bat: bacula-console-qt already ships /usr/sbin/bat (and /usr/share/man/man1/bat.1.gz) to be marked as done. This means

Bug#934850: marked as done (bat: missing Breaks+Replaces: bareos-bat)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 Dec 2019 01:20:30 + with message-id and subject line Bug#935578: fixed in rust-bat 0.12.1-1 has caused the Debian Bug report #935578, regarding bat: missing Breaks+Replaces: bareos-bat to be marked as done. This means that you claim that the problem has been dealt

Bug#946599: libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system

2019-12-11 Thread Thorsten Glaser
Aurelien Jarno dixit: >I am not sure we can use a Pre-Depends given we have a dependency loop, Ah, dependency loops cause unpredictable behaviour… >I thing that's the issue. Multi-Arch forces some order for all the >versions of libc6, and also all the versions of libcrypt1. … plus that. bye,

Bug#946599: libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system

2019-12-11 Thread Aurelien Jarno
On 2019-12-11 17:54, Marco d'Itri wrote: > On Dec 11, Thorsten Glaser wrote: > > > Thankfully, I had a root session in a chroot open and used > > the program, statically linked, from http://koltsoff.com/pub/getroot/ > > to recover access outside the chroot, by using dpkg -i --force-all > > first

Bug#946198: Since upgrading to 1.25.13 no remote printer is made available anymore

2019-12-11 Thread Simon John
I've not seen either of my remote printers disappear, but am now getting "The PPD file for this printer is damaged" whenever I double-click on the printer in the print settings gui. I downgraded cups-browsed to cups-browsed_1.25.12-1_amd64.deb but also get the error, so suspect its the filter

Bug#946614: keystone: CVE-2019-19687

2019-12-11 Thread Salvatore Bonaccorso
Source: keystone Version: 2:16.0.0-4 Severity: grave Tags: security upstream Forwarded: https://bugs.launchpad.net/keystone/+bug/1855080 Hi, The following vulnerability was published for keystone. CVE-2019-19687[0]: | OpenStack Keystone 15.0.0 and 16.0.0 is affected by Data Leakage in | the

Bug#925716: marked as done (iem-plugin-suite: ftbfs with GCC-9)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 21:19:16 + with message-id and subject line Bug#925716: fixed in iem-plugin-suite 1.11.0-1 has caused the Debian Bug report #925716, regarding iem-plugin-suite: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been

Bug#940917: marked as done (pylint: removal of pylint makes files disappear from pylint3)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 20:49:28 + with message-id and subject line Bug#940917: fixed in pylint 2.4.4-2 has caused the Debian Bug report #940917, regarding pylint: removal of pylint makes files disappear from pylint3 to be marked as done. This means that you claim that the

Bug#940012: marked as done (pylint: renaming broke reverse-dependencies)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 20:49:28 + with message-id and subject line Bug#940012: fixed in pylint 2.4.4-2 has caused the Debian Bug report #940012, regarding pylint: renaming broke reverse-dependencies to be marked as done. This means that you claim that the problem has been dealt

Bug#946198: Since upgrading to 1.25.13 no remote printer is made available anymore

2019-12-11 Thread Till Kamppeter
I have done several fixes on cups-filters upstream now, please try a current GIT snapshot of cups-filters. Till

Processed: Bug#940917 marked as pending in pylint

2019-12-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #940917 [pylint] pylint: removal of pylint makes files disappear from pylint3 Added tag(s) pending. -- 940917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#940012 marked as pending in pylint

2019-12-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #940012 [src:pylint] pylint: renaming broke reverse-dependencies Added tag(s) pending. -- 940012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#940917: marked as pending in pylint

2019-12-11 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #940917 in pylint 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:

Bug#940012: marked as pending in pylint

2019-12-11 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #940012 in pylint 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:

Bug#946561: Bug #946561

2019-12-11 Thread Stefano Fabri
Try to apt-get install hplip when you have in the system python >=3.8 (https://packages.debian.org/experimental/python3). In this status hplip is not installable.

Processed: your mail

2019-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 946561 Bug #946561 {Done: Brian Potkin } [hplip] hplip: Not installable with python3 >= 3.8 Bug reopened Ignoring request to alter fixed versions of bug #946561 to the same values previously set > End of message, stopping processing

Bug#946198: Since upgrading to 1.25.13 no remote printer is made available anymore

2019-12-11 Thread Brian Potkin
On Fri 06 Dec 2019 at 15:31:59 +, Brian Potkin wrote: > tags 946198 upstream > thanks > > > On Fri 06 Dec 2019 at 11:08:19 +0100, Michael Meskes wrote: > > > > Which printers list? An application dialog? > > > > Oops, sorry, I was referring to the printers tab on localhost:631. In > > the

Bug#946561: marked as done (hplip: Not installable with python3 >= 3.8)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 19:32:26 + with message-id <11122019192628.c9b08fd64...@desktop.copernicus.org.uk> and subject line Re: Bug#946561: hplip: Not installable with python3 >= 3.8 has caused the Debian Bug report #946561, regarding hplip: Not installable with python3 >= 3.8 to

Bug#945263: marked as done (f2py3.8 fails with "Entry point not found" exception)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 18:49:21 + with message-id and subject line Bug#945263: fixed in numpy 1:1.17.4-4 has caused the Debian Bug report #945263, regarding f2py3.8 fails with "Entry point not found" exception to be marked as done. This means that you claim that the problem has

Bug#937084: marked as done (mountpy: Python2 removal in sid/bullseye)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 18:34:18 + with message-id and subject line Bug#937084: fixed in mountpy 0.9 has caused the Debian Bug report #937084, regarding mountpy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#946599: libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system

2019-12-11 Thread Thorsten Glaser
Marco d'Itri dixit: >Theory A: maybe after all we really need some Pre-Depends in libc6? Pre-Depends + Replaces, maybe? (Though Replaces is already there.) >Theory B: did we miss something related to x32? Unsure if it’s about x32 or about Multi-Arch or the missing Pre-Depends. >Is this an x32

Bug#946538: marked as done (metastudent: depends on removed transitional package blast2)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 17:36:07 + with message-id and subject line Bug#946538: fixed in metastudent 2.0.1-8 has caused the Debian Bug report #946538, regarding metastudent: depends on removed transitional package blast2 to be marked as done. This means that you claim that the

Bug#939950: marked as done (hkl: fails to build with gtk-doc 1.32)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 17:35:57 + with message-id and subject line Bug#939950: fixed in hkl 5.0.0.2569-1 has caused the Debian Bug report #939950, regarding hkl: fails to build with gtk-doc 1.32 to be marked as done. This means that you claim that the problem has been dealt

Bug#946599: libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system

2019-12-11 Thread Thorsten Glaser
On Wed, 11 Dec 2019, Thorsten Glaser wrote: > Justification: breaks the whole system > > I’ve did a “sudo apt-get --purge dist-upgrade” and ended with, Given it worked in the amd64-only chroot and on another machine, this most likely only fails if one has more than one architecture enabled in

Bug#946599: libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system

2019-12-11 Thread Marco d'Itri
On Dec 11, Thorsten Glaser wrote: > Thankfully, I had a root session in a chroot open and used > the program, statically linked, from http://koltsoff.com/pub/getroot/ > to recover access outside the chroot, by using dpkg -i --force-all > first on libc6_*.deb, then libcrypt1_*.deb. Afterwards,

Bug#946599: libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system

2019-12-11 Thread Thorsten Glaser
Package: libcrypt1 Version: 1:4.4.10-5 Severity: critical Justification: breaks the whole system I’ve did a “sudo apt-get --purge dist-upgrade” and ended with, see screenshot below. Thankfully, I had a root session in a chroot open and used the program, statically linked, from

Bug#943612: marked as done (python3-ownet: Python2-only code shipped in Python3 module)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 16:35:01 + with message-id and subject line Bug#943612: fixed in owfs 3.2p3+dfsg1-5 has caused the Debian Bug report #943612, regarding python3-ownet: Python2-only code shipped in Python3 module to be marked as done. This means that you claim that the

Bug#937225: marked as done (owfs: Python2 removal in sid/bullseye)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 16:35:01 + with message-id and subject line Bug#937225: fixed in owfs 3.2p3+dfsg1-5 has caused the Debian Bug report #937225, regarding owfs: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#946597: python-apt: security regression in 1.9.1

2019-12-11 Thread Julian Andres Klode
Package: python-apt Version: 1.9.1 Severity: critical Tags: security experimental I made python-apt use all available hashes instead of defaulting to md5 in 1.9.1 (and 1.9.0 was just broken); but now, if there are no hashes, that'd verify correctly as well, so I gotta fix that, but might not make

Bug#944091: marked as done (deprecation warnings with 3.8 in the autopkg tests)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 15:54:22 + with message-id and subject line Bug#944091: fixed in python-apt 1.9.1 has caused the Debian Bug report #944091, regarding deprecation warnings with 3.8 in the autopkg tests to be marked as done. This means that you claim that the problem has

Bug#944696: marked as done (python-apt: relies on MD5 internally to download packages)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 15:54:22 + with message-id and subject line Bug#944696: fixed in python-apt 1.9.1 has caused the Debian Bug report #944696, regarding python-apt: relies on MD5 internally to download packages to be marked as done. This means that you claim that the problem

Processed: py2removal blocks updates - 2019-12-11 15:37:41.887537+00:00

2019-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Part of the effort for the removal of python from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # mercurial > block 937009 by 937011 937012 Bug #937009 [src:mercurial]

Processed: severity of 937697 is serious

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

Bug#944696: marked as pending in python-apt

2019-12-11 Thread Julian Andres Klode
Control: tag -1 pending Hello, Bug #944696 in python-apt 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#944696 marked as pending in python-apt

2019-12-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #944696 [python-apt] python-apt: relies on MD5 internally to download packages Added tag(s) pending. -- 944696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#934140: marked as done (brightd does not fade)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 13:49:10 + with message-id and subject line Bug#934140: fixed in brightd 0.4.1-3 has caused the Debian Bug report #934140, regarding brightd does not fade to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: user debian...@lists.debian.org, usertagging 942472, severity of 942472 is serious ...

2019-12-11 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). > usertags 942472 piuparts There were no usertags set. Usertags are now: piuparts. > severity 942472 serious Bug #942472 [r-cran-shiny]

Bug#945932: logrotate: did not preserve the user's configuration file, logs lost

2019-12-11 Thread Vincent Lefevre
On 2019-12-10 14:51:10 +0100, Christian Göttsche wrote: > Control: tags -1 moreinfo > > > there wasn't even a warning about that > > Where did you place the configuration for /var/log/wtmp ? /etc/logrotate.conf before, /etc/logrotate.d/wtmp after the upgrade. > II. dpkg should also ask If you

Processed: block 937012 with 937011, unblock 937011 with 937012

2019-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 937012 with 937011 Bug #937012 [src:mercurial-keyring] mercurial-keyring: Python2 removal in sid/bullseye 937012 was blocked by: 937009 937012 was blocking: 937011 937695 937870 938168 Added blocking bug(s) of 937012: 937011 > unblock

Processed: block 937012 with 937009, block 937011 with 937009, unblock 937009 with 937012 ...

2019-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 937012 with 937009 Bug #937012 [src:mercurial-keyring] mercurial-keyring: Python2 removal in sid/bullseye 937012 was not blocked by any bugs. 937012 was blocking: 937009 937011 937695 937870 938168 Added blocking bug(s) of 937012: 937009 >

Bug#946591: mkesmtpdcert does not make file where it said

2019-12-11 Thread PICCORO McKAY Lenz
Package: courier-mta Version: 1.0.6-1 Severity: critical Justification: causes serious data loss the mkesmtpdcert pgrogram in debian was altered, BUT are not in sync around documentations.. that may cause confusion and data loss due admins does not find resulting cert file and daemons does not

Bug#925826: shim: FTBFS w/ GCC 9 fix

2019-12-11 Thread Steve McIntyre
On Tue, Dec 10, 2019 at 11:06:49PM -0500, John Scott wrote: >Control: tags -1 patch > >Merge request with fix at https://github.com/rhboot/shim/pull/170 Thanks for the heads-up! -- Steve McIntyre, Cambridge, UK.st...@einval.com There's no sensation to compare

Bug#885505: bumping severity of pygtk bugs

2019-12-11 Thread Moritz Muehlenhoff
On Wed, Dec 11, 2019 at 09:52:15AM +0100, Thibaut Paumard wrote: > Le 10/12/2019 à 19:59, Moritz Mühlenhoff a écrit : > > On Mon, Oct 07, 2019 at 04:51:09PM +0200, Thibaut Paumard wrote: > >> Dear Jeremy, > >> > >> Thanks, I have warned upstream that spydr will be removed if not updated > >> to

Bug#937811: python-hkdf: Python2 removal in sid/bullseye

2019-12-11 Thread Sascha Steinbiss
> It looks like all reverse deps are currently exclusively using the Python3 > version: Or maybe not, looks like not all rdeps are displayed. Looks like things like python-omemo and friends still depend on this. So no removal upload for me then. S.

Bug#946568: marked as done (libbio-cluster-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3))

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 10:19:16 + with message-id and subject line Bug#946568: fixed in libbio-cluster-perl 1.7.3-2 has caused the Debian Bug report #946568, regarding libbio-cluster-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3) to be marked as done. This means

Processed: your mail

2019-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 946582 946583 Bug #946582 [pocl] silx: autopkgtest regression: pocl error Bug #946583 [pocl] silx: autopkgtest regression: pocl error Merged 946582 946583 > stop Stopping processing here. Please contact me if you need assistance. --

Processed: your mail

2019-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 946422 -1 Bug #946422 [src:silx] silx: autopkgtest regression: pocl error Bug 946422 cloned as bug 946583 > reassign -1 pocl Bug #946583 [src:silx] silx: autopkgtest regression: pocl error Bug reassigned from package 'src:silx' to 'pocl'.

Processed: your mail

2019-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 946422 -1 Bug #946422 [src:silx] silx: autopkgtest regression: pocl error Bug 946422 cloned as bug 946582 > reassign -1 pocl Bug #946582 [src:silx] silx: autopkgtest regression: pocl error Bug reassigned from package 'src:silx' to 'pocl'.

Bug#885505: bumping severity of pygtk bugs

2019-12-11 Thread Thibaut Paumard
Le 10/12/2019 à 19:59, Moritz Mühlenhoff a écrit : > On Mon, Oct 07, 2019 at 04:51:09PM +0200, Thibaut Paumard wrote: >> Dear Jeremy, >> >> Thanks, I have warned upstream that spydr will be removed if not updated >> to Python 3 and Gtk 3. > > Was there any reaction? Otherwise let's go ahead with

Bug#946571: marked as done (silx, build-depends on obsolete package ipython3-qtconsole)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 08:45:06 + with message-id and subject line Bug#946571: fixed in silx 0.11.0+dfsg-3 has caused the Debian Bug report #946571, regarding silx, build-depends on obsolete package ipython3-qtconsole to be marked as done. This means that you claim that the

Bug#946435: marked as done (texlive-latex-recommended: Missing Breaks+Replaces texlive-latex-extra 2019.20191112-1)

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 17:17:29 +0900 with message-id <20191211081729.d37rkmmyz5h4x...@burischnitzel.preining.info> and subject line Re: Bug#946430: texlive-latex-recommended: missing Breaks+Replaces: texlive-latex-base (<< 2019.20191208) has caused the Debian Bug report #946430,

Bug#946430: marked as done (texlive-latex-recommended: missing Breaks+Replaces: texlive-latex-base (<< 2019.20191208))

2019-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2019 17:17:29 +0900 with message-id <20191211081729.d37rkmmyz5h4x...@burischnitzel.preining.info> and subject line Re: Bug#946430: texlive-latex-recommended: missing Breaks+Replaces: texlive-latex-base (<< 2019.20191208) has caused the Debian Bug report #946430,

Processed: severity of 943234 is normal

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

Processed: block 945679 with 937218, owner 945679

2019-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 945679 with 937218 Bug #945679 [src:osc-plugins-dput] osc-plugins-dput: Python2 removal in sid/bullseye 945679 was not blocked by any bugs. 945679 was blocking: 937218 937691 Added blocking bug(s) of 945679: 937218 > owner 945679 ! Bug

Processed: block 936700 with 937009

2019-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 936700 with 937009 Bug #936700 [src:hgsubversion] hgsubversion: Python2 removal in sid/bullseye 936700 was not blocked by any bugs. 936700 was blocking: 937009 937695 938578 938579 Added blocking bug(s) of 936700: 937009 > thanks Stopping