Bug#934026: python-django: CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 CVE-2019-14235

2019-09-02 Thread Moritz Mühlenhoff
On Mon, Sep 02, 2019 at 10:36:58PM +0200, Salvatore Bonaccorso wrote: > Hi Chris, > > On Mon, Sep 02, 2019 at 02:07:55PM +0100, Chris Lamb wrote: > > Chris Lamb wrote: > > > > > > > +python-django (1:1.11.23-1~deb10u1) buster-security; urgency=high > > > > > > > > Thanks, these both look good; p

Bug#938970: mpi4py: FTBFS when built with dpkg-buildpackage -A

2019-09-02 Thread Graham Inggs
Hi I believe this failure was actually caused by a bug in debhelper 12.5.3, and fixed in 12.5.4. See #935780. Regards Graham

Bug#939303: matplotlib2: FTBFS unsatisfied b-d on python-pyshp

2019-09-02 Thread Johannes 'josch' Schauer
Source: matplotlib2 Version: 2.2.3-6 Severity: serious Justification: fails to build from source Hi, src:matplotlib2 currently FTBFS because its build dependencies cannot be satisfied in Debian unstable. It follows some evidence: $ dose-builddebcheck --explain --failures --deb-native-arch am

Bug#784181: marked as done (razorqt: Razor-Qt dead upstream, superseded by LXQt)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:38:42 + with message-id and subject line Bug#939296: Removed package(s) from unstable has caused the Debian Bug report #784181, regarding razorqt: Razor-Qt dead upstream, superseded by LXQt to be marked as done. This means that you claim that the problem

Bug#875169: marked as done ([razorqt] Future Qt4 removal from Buster)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:38:42 + with message-id and subject line Bug#939296: Removed package(s) from unstable has caused the Debian Bug report #875169, regarding [razorqt] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been d

Bug#875200: marked as done ([tagainijisho] Future Qt4 removal from Buster)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:37:45 + with message-id and subject line Bug#939281: Removed package(s) from unstable has caused the Debian Bug report #875200, regarding [tagainijisho] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has b

Bug#851244: marked as done (percona-xtrabackup: CVE-2016-6225)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:37:18 + with message-id and subject line Bug#939279: Removed package(s) from unstable has caused the Debian Bug report #851244, regarding percona-xtrabackup: CVE-2016-6225 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#903043: marked as done (percona-xtrabackup 2.2.3-2.1 Unsupported server version: 10.1.26-MariaDB-0+deb9u1)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:37:18 + with message-id and subject line Bug#939279: Removed package(s) from unstable has caused the Debian Bug report #903043, regarding percona-xtrabackup 2.2.3-2.1 Unsupported server version: 10.1.26-MariaDB-0+deb9u1 to be marked as done. This means

Bug#848447: marked as done (percona-xtrabackup-test: Should Depends/Recommends the metapackage default-mysql-*)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:37:18 + with message-id and subject line Bug#939279: Removed package(s) from unstable has caused the Debian Bug report #848447, regarding percona-xtrabackup-test: Should Depends/Recommends the metapackage default-mysql-* to be marked as done. This means

Bug#811896: marked as done (percona-xtrabackup: FTBFS with GCC 6: inconsistent user-defined literal suffixes)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:37:18 + with message-id and subject line Bug#939279: Removed package(s) from unstable has caused the Debian Bug report #811896, regarding percona-xtrabackup: FTBFS with GCC 6: inconsistent user-defined literal suffixes to be marked as done. This means t

Bug#882059: marked as done (rewrite ibus-tegaki with GObject introspection (GI))

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:36:22 + with message-id and subject line Bug#939275: Removed package(s) from unstable has caused the Debian Bug report #882059, regarding rewrite ibus-tegaki with GObject introspection (GI) to be marked as done. This means that you claim that the problem

Bug#875221: marked as done ([v4l2ucp] Future Qt4 removal from Buster)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:35:57 + with message-id and subject line Bug#939274: Removed package(s) from unstable has caused the Debian Bug report #875221, regarding [v4l2ucp] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been d

Bug#896709: marked as done (innobackupex: Error: Unsupported server version: '5.7.21-1-log')

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:37:18 + with message-id and subject line Bug#939279: Removed package(s) from unstable has caused the Debian Bug report #896709, regarding innobackupex: Error: Unsupported server version: '5.7.21-1-log' to be marked as done. This means that you claim that

Bug#915755: marked as done (zope2.13 FTBFS with python-pip 18.1)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:36:49 + with message-id and subject line Bug#939278: Removed package(s) from unstable has caused the Debian Bug report #915755, regarding zope2.13 FTBFS with python-pip 18.1 to be marked as done. This means that you claim that the problem has been dealt

Bug#806127: marked as done (zope2.13: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:36:49 + with message-id and subject line Bug#939278: Removed package(s) from unstable has caused the Debian Bug report #806127, regarding zope2.13: FTBFS when built with dpkg-buildpackage -A (No such file or directory) to be marked as done. This means t

Bug#933883: marked as done (Should zope2.13 be removed?)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:36:49 + with message-id and subject line Bug#939278: Removed package(s) from unstable has caused the Debian Bug report #933883, regarding Should zope2.13 be removed? to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#933882: marked as done (Should percona-xtrabackup be removed?)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:37:18 + with message-id and subject line Bug#939279: Removed package(s) from unstable has caused the Debian Bug report #933882, regarding Should percona-xtrabackup be removed? to be marked as done. This means that you claim that the problem has been deal

Bug#875130: marked as done ([qimageblitz] Future Qt4 removal from Buster)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 05:35:29 + with message-id and subject line Bug#939273: Removed package(s) from unstable has caused the Debian Bug report #875130, regarding [qimageblitz] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has be

Processed: Re: Bug#939044: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

2019-09-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unmerge 939044 Bug #939044 [src:ocrmypdf] ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest Bug #935749 [src:ocrmypdf] ocrmypdf: autopkgtest regression: This test may fail if Tesseract language packs are missing Di

Bug#939044: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

2019-09-02 Thread Sean Whitton
unmerge 939044 severity 935749 normal tag 935749 - sid bullseye notfound 935749 8.0.1+dfsg-1 affects 939044 src:pikepdf affects 939044 src:ghostscript affects 939044 src:pytest notfound 939044 9.0.1+dfsg-1 thanks Hello, On Mon 02 Sep 2019 at 08:58PM +02, Paul Gevers wrote: > The difference here

Bug#939299: virtualenvwrapper incorrectly dropped virtualenv dependency

2019-09-02 Thread James Tocknell
Package: virtualenvwrapper Version: 4.8.4-3 Severity: grave Justification: renders package unusable It appears the new virtualenvwrapper update dropped the virtualenv requirement, but it appears that virtualenv (the script) is still required, and depending on the python module is insufficient. Cou

Processed: forcibly merging 935015 936367

2019-09-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 935015 936367 Bug #935015 {Done: Sandro Tosi } [src:datalad] datalad: please drop python-datalad (python 2 removal effort) Bug #936367 [src:datalad] datalad: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' 93785

Bug#935782: marked as done (at-spi2-atk: bump B-D: libatk1.0-dev (>= 2.33.3+really2.33.3))

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 23:19:00 + with message-id and subject line Bug#935782: fixed in at-spi2-atk 2.33.92-1 has caused the Debian Bug report #935782, regarding at-spi2-atk: bump B-D: libatk1.0-dev (>= 2.33.3+really2.33.3) to be marked as done. This means that you claim that the

Bug#935015: marked as done (datalad: please drop python-datalad (python 2 removal effort))

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 23:19:11 + with message-id and subject line Bug#935015: fixed in datalad 0.11.6-1.1 has caused the Debian Bug report #935015, regarding datalad: please drop python-datalad (python 2 removal effort) to be marked as done. This means that you claim that the pr

Bug#925777: marked as done (mkl-dnn: ftbfs with GCC-9)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 21:00:12 + with message-id and subject line Bug#925777: fixed in mkl-dnn 1.0.1-1 has caused the Debian Bug report #925777, regarding mkl-dnn: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#874862: cppreference-doc: diff for NMU version 20170409-1.1

2019-09-02 Thread Moritz Muehlenhoff
On Mon, Sep 02, 2019 at 11:14:38PM +0300, Povilas Kanapickas wrote: > Thanks a lot! > > I was waiting for my usual sponsors to sponsor a new version of > cppreference-doc [1] that contains this fix too, but they haven't > replied yet. Ah, sorry. I wasn't aware of the package on mentors.debian.net

Bug#934026: python-django: CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 CVE-2019-14235

2019-09-02 Thread Salvatore Bonaccorso
Hi Chris, On Mon, Sep 02, 2019 at 02:07:55PM +0100, Chris Lamb wrote: > Chris Lamb wrote: > > > > > +python-django (1:1.11.23-1~deb10u1) buster-security; urgency=high > > > > > > Thanks, these both look good; please upload to security-master. > > > > Both uploaded to security-master. > > There

Bug#874862: cppreference-doc: diff for NMU version 20170409-1.1

2019-09-02 Thread Povilas Kanapickas
Thanks a lot! I was waiting for my usual sponsors to sponsor a new version of cppreference-doc [1] that contains this fix too, but they haven't replied yet. Cheers, Povilas [1] - https://mentors.debian.net/debian/pool/main/c/cppreference-doc/cppreference-doc_20170409-2.dsc On 9/2/19 9:40 PM, Mo

Bug#780620: marked as done (control file not policy compliant and build failures almost everywhere)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 2 Sep 2019 21:21:23 +0100 with message-id <20190902200704.GA20056@sokka.flat11.house> and subject line Re: Bug#780620: control file not policy compliant and build failures almost everywhere has caused the Debian Bug report #780620, regarding control file not policy complian

Bug#896344: marked as done (python-raven: raven fails to import)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 19:46:08 + with message-id and subject line Bug#939074: Removed package(s) from unstable has caused the Debian Bug report #896344, regarding python-raven: raven fails to import to be marked as done. This means that you claim that the problem has been dealt

Bug#935447: marked as done (Please drop the Python 2 subpackage)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 19:46:08 + with message-id and subject line Bug#939074: Removed package(s) from unstable has caused the Debian Bug report #935447, regarding Please drop the Python 2 subpackage to be marked as done. This means that you claim that the problem has been dealt

Bug#939072: marked as done (src:python-raven: Should this package be removed)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 19:46:08 + with message-id and subject line Bug#939074: Removed package(s) from unstable has caused the Debian Bug report #939072, regarding src:python-raven: Should this package be removed to be marked as done. This means that you claim that the problem ha

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

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 19:46:08 + with message-id and subject line Bug#939074: Removed package(s) from unstable has caused the Debian Bug report #935447, regarding python-raven: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

Bug#892625: marked as done (python-raven FTBFS: TypeError: _log() got an unexpected keyword argument 'blah')

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 19:46:08 + with message-id and subject line Bug#939074: Removed package(s) from unstable has caused the Debian Bug report #892625, regarding python-raven FTBFS: TypeError: _log() got an unexpected keyword argument 'blah' to be marked as done. This means th

Processed: [bts-link] source package src:rust-memoffset

2019-09-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:rust-memoffset > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.

Bug#939288: python-os-vif: CVE-2019-15753

2019-09-02 Thread Salvatore Bonaccorso
Source: python-os-vif Version: 1.15.1-2 Severity: grave Tags: security upstream Forwarded: https://launchpad.net/bugs/1837252 Hi, The following vulnerability was published for python-os-vif. CVE-2019-15753[0]: | In OpenStack os-vif 1.15.x before 1.15.2, and 1.16.0, a hard-coded MAC | aging time

Processed: retitle 937632 to RM: pythoncard -- RoQA; orphaned; Python 2 only; dead upstream; low popcon ...

2019-09-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 937632 RM: pythoncard -- RoQA; orphaned; Python 2 only; dead > upstream; low popcon Bug #937632 [src:pythoncard] pythoncard: Python2 removal in sid/bullseye Changed Bug title to 'RM: pythoncard -- RoQA; orphaned; Python 2 only; dead upst

Processed: [bts-link] source package src:ceph

2019-09-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ceph > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Settin

Bug#874862: marked as done ([cppreference-doc] Future Qt4 removal from Buster)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 19:20:08 + with message-id and subject line Bug#874862: fixed in cppreference-doc 20170409-1.1 has caused the Debian Bug report #874862, regarding [cppreference-doc] Future Qt4 removal from Buster to be marked as done. This means that you claim that the pro

Bug#874809: [alsoft-conf] Future Qt4 removal from Buster

2019-09-02 Thread Markus Koschany
Hi, Am 02.09.19 um 20:56 schrieb Moritz Mühlenhoff: [...] > alsoft-conf is dead upstream, does anyone in the Debian Games Team intend to > port it themselves? Otherwise I'll file a removal bug. I'm fine with removing alsoft-conf from Debian. There was only one initial upload by the actual uploade

Bug#939044: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

2019-09-02 Thread Paul Gevers
Hi Sean, On 02-09-2019 01:03, Sean Whitton wrote: > control: forcemerge 935749 -1 Not fully agreeing, but whatever, as long as the situation for your (test) dependencies gets fixed. > On Sat 31 Aug 2019 at 03:25PM +02, Paul Gevers wrote: > >> With a recent upload of pikepdf and with a recent up

Bug#874809: [alsoft-conf] Future Qt4 removal from Buster

2019-09-02 Thread Moritz Mühlenhoff
On Sat, Sep 09, 2017 at 08:57:00PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: alsoft-conf > Version: 1.4.3-2 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as [annou

Bug#784181: [razorqt] Future Qt4 removal from Buster

2019-09-02 Thread Moritz Mühlenhoff
On Tue, Sep 12, 2017 at 12:25:16AM +0200, Manuel A. Fernandez Montecelo wrote: > 2017-09-09 23:09 Lisandro Damián Nicanor Pérez Meyer: > > > > In order to make this move, all packages directly or indirectly depending on > > the Qt4 libraries have to either get ported to Qt5 or eventually get > > r

Bug#874862: cppreference-doc: diff for NMU version 20170409-1.1

2019-09-02 Thread Moritz Mühlenhoff
Dear maintainer, I've uploaded an NMU for cppreference-doc (versioned as 20170409-1.1). Cheers, Moritz diff -Nru cppreference-doc-20170409/debian/changelog cppreference-doc-20170409/debian/changelog --- cppreference-doc-20170409/debian/changelog 2017-04-09 02:00:00.0 +0200 +++ cp

Processed: severity of 927165 is important

2019-09-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Was not RC after all > severity 927165 important Bug #927165 [debian-installer] debian-installer: improve support for LUKS Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -

Bug#933715: jh_linkjars: dpkg -L "debhelper-compat" returned exit code 1

2019-09-02 Thread Niels Thykier
Control: severity -1 important On Fri, 02 Aug 2019 14:05:25 +0200 Markus Koschany wrote: > Package: javahelper > Version: 0.72.9 > Severity: serious > > > jh_linkjars apparently chokes on the new debhelper-compat package. > Since it is not a real package dpkg -L does not work. I presume the > w

Processed: Re: jh_linkjars: dpkg -L "debhelper-compat" returned exit code 1

2019-09-02 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #933715 [javahelper] jh_linkjars: dpkg -L "debhelper-compat" returned exit code 1 Severity set to 'important' from 'serious' -- 933715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933715 Debian Bug Tracking System Contact ow...@bugs

Bug#933883: Should zope2.13 be removed?

2019-09-02 Thread Moritz Mühlenhoff
On Sun, Aug 04, 2019 at 10:22:54PM +0200, Moritz Muehlenhoff wrote: > Source: zope2.13 > Severity: serious > > Should zope2.13 be removed? > > - Unmaintained (last upload in 2014) > - FTBFS for a long time, missed two stable releases No objections for a month, filed a removal bug. Cheers,

Bug#875140: [qliss3d] Future Qt4 removal from Buster

2019-09-02 Thread Moritz Mühlenhoff
On Sat, Sep 09, 2017 at 11:06:23PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: qliss3d > Version: 1.4-2 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as [announced]

Bug#925794: marked as done (open-vm-tools: ftbfs with GCC-9)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 18:07:31 + with message-id and subject line Bug#925794: fixed in open-vm-tools 2:11.0.0~0-1 has caused the Debian Bug report #925794, regarding open-vm-tools: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt w

Bug#939022: marked as done (pyresample: autopkgtest failure with PROJ 6 (epsg data file removed))

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 16:51:12 + with message-id and subject line Bug#939022: fixed in pyresample 1.12.3-6 has caused the Debian Bug report #939022, regarding pyresample: autopkgtest failure with PROJ 6 (epsg data file removed) to be marked as done. This means that you claim tha

Bug#939267: clangd: missing Breaks+Replaces: clang-tools (<< 1:8)

2019-09-02 Thread Andreas Beckmann
Package: clangd Version: 1:8.0-48 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packa

Processed: Not present in sid, removing tag

2019-09-02 Thread Debian Bug Tracking System
Processing control commands: > tags -1 - sid Bug #939101 [elogind] elogind: elogind 239 in bullseye FTBFS with gcc-9 Removed tag(s) sid. -- 939101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#939101: Not present in sid, removing tag

2019-09-02 Thread Mark Hindley
Control: tags -1 - sid Andreas, On Mon, Sep 02, 2019 at 05:21:13PM +0200, Andreas Beckmann wrote: > tags 939101 + sid bullseye Actually, this isn't present in sid AFAICS. Thanks Mark

Processed: fixed 920578 in 1.16.0-1

2019-09-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 920578 1.16.0-1 Bug #920578 {Done: Sebastian Dröge } [src:gstreamer-vaapi] gstreamer-vaapi: FTBFS on 32-bit architectures Marked as fixed in versions gstreamer-vaapi/1.16.0-1. > thanks Stopping processing here. Please contact me if you nee

Processed: fixed 891233 in 3.2.4-1, tagging 891233, tagging 936076, tagging 938963, tagging 922978 ...

2019-09-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 891233 3.2.4-1 Bug #891233 [kamoso] kamoso: segmentation fault in kamoso in Debian 9 stable. Application crashes while starting. Marked as fixed in versions kamoso/3.2.4-1. > tags 891233 - stretch Bug #891233 [kamoso] kamoso: segmentation f

Bug#939022: [#939022] Re: pyresample: autopkgtest failure with PROJ 6 (epsg data file removed)

2019-09-02 Thread Sebastiaan Couwenberg
proj (6.2.0-1) & python-pyproj (2.3.1+ds-1) are now in unstable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1

Bug#919036: marked as done (libopenexr24 botched upload issue also affects libopenexr23 and libilmbase23)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 15:05:00 + with message-id and subject line Bug#919036: fixed in openexr 2.3.0-6 has caused the Debian Bug report #919036, regarding libopenexr24 botched upload issue also affects libopenexr23 and libilmbase23 to be marked as done. This means that you clai

Bug#935671: marked as done (librust-rle-decode-fast+bench-dev/amd64 unsatisfiable Depends: librust-criterion-0.2+default-dev)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 14:49:20 + with message-id and subject line Bug#935671: fixed in rust-rle-decode-fast 1.0.1-3 has caused the Debian Bug report #935671, regarding librust-rle-decode-fast+bench-dev/amd64 unsatisfiable Depends: librust-criterion-0.2+default-dev to be marked a

Bug#933918: src:lava: Unsafe use of yaml.load()

2019-09-02 Thread Steve McIntyre
On Mon, Aug 05, 2019 at 01:28:40AM -0400, Scott Kitterman wrote: >Package: src:lava >Version: 2019.01-5 >Severity: grave >Tags: security >Justification: user security hole > >The new version of pyyaml no longer allows use of yaml.load() without a >loader being specifed. This raises a deprecation w

Bug#933919: src:lavacli: Unsafe use of yaml.load()

2019-09-02 Thread Steve McIntyre
On Mon, Aug 05, 2019 at 01:31:12AM -0400, Scott Kitterman wrote: >Package: src:lavacli >Version: 0.9.7-1 >Severity: grave >Tags: security >Justification: user security hole > >The new version of pyyaml no longer allows use of yaml.load() without a >loader being specifed. This raises a deprecation

Bug#934026: python-django: CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 CVE-2019-14235

2019-09-02 Thread Chris Lamb
Chris Lamb wrote: > > > +python-django (1:1.11.23-1~deb10u1) buster-security; urgency=high > > > > Thanks, these both look good; please upload to security-master. > > Both uploaded to security-master. There is now a 1.11.24 (ie. 1:1.11.24-1~deb10u1) upstream: https://docs.djangoproject.com/e

Bug#938984: marked as done (librust-pangocairo-sys-dev : Depends: librust-cairo-sys-rs-0.7+default-dev but it is not installable)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 12:51:06 + with message-id and subject line Bug#938984: fixed in rust-pangocairo-sys 0.10.0-1 has caused the Debian Bug report #938984, regarding librust-pangocairo-sys-dev : Depends: librust-cairo-sys-rs-0.7+default-dev but it is not installable to be mark

Bug#933854: marked as done (solr-jetty: Jetty refuses to start SOLR due to a probably depreceated Call )

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 12:50:05 + with message-id and subject line Bug#933854: fixed in lucene-solr 3.6.2+dfsg-21 has caused the Debian Bug report #933854, regarding solr-jetty: Jetty refuses to start SOLR due to a probably depreceated Call to be marked as done. This means that

Processed: tagging 938984

2019-09-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 938984 + pending Bug #938984 [src:rust-pangocairo-sys] librust-pangocairo-sys-dev : Depends: librust-cairo-sys-rs-0.7+default-dev but it is not installable Added tag(s) pending. > thanks Stopping processing here. Please contact me if you ne

Bug#933854: marked as pending in lucene-solr

2019-09-02 Thread Markus Koschany
Control: tag -1 pending Hello, Bug #933854 in lucene-solr 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/java-team/lucene-solr/commit/f58985f500c3ef0c7e874c011

Processed: Bug#933854 marked as pending in lucene-solr

2019-09-02 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #933854 [solr-jetty] solr-jetty: Jetty refuses to start SOLR due to a probably depreceated Call Ignoring request to alter tags of bug #933854 to the same tags previously set -- 933854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933854 De

Processed: Re: solr-jetty: Jetty lacks necessary write permissions to /var/lib/solr/data/index/

2019-09-02 Thread Debian Bug Tracking System
Processing control commands: > tags 933857 pending Bug #933857 [solr-jetty] solr-jetty: Jetty lacks necessary write permissions to /var/lib/solr/data/index/ Added tag(s) pending. > tags 933854 pending Bug #933854 [solr-jetty] solr-jetty: Jetty refuses to start SOLR due to a probably depreceated

Processed: Re: solr-jetty: Jetty lacks necessary write permissions to /var/lib/solr/data/index/

2019-09-02 Thread Debian Bug Tracking System
Processing control commands: > tags 933857 pending Bug #933857 [solr-jetty] solr-jetty: Jetty lacks necessary write permissions to /var/lib/solr/data/index/ Ignoring request to alter tags of bug #933857 to the same tags previously set > tags 933854 pending Bug #933854 [solr-jetty] solr-jetty: Jet

Bug#933854: solr-jetty: Jetty lacks necessary write permissions to /var/lib/solr/data/index/

2019-09-02 Thread Markus Koschany
Control: tags 933857 pending Control: tags 933854 pending On Sun, 1 Sep 2019 19:47:48 -0700 "J.P. Larocque" wrote: > stephan, thanks for tracking this down. I almost figured it out, and > then I found that you already reported this bug. Your other bug > report was also super helpful for me to g

Bug#875089: marked as done ([pianobooster] Future Qt4 removal from Buster)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 12:04:44 + with message-id and subject line Bug#875089: fixed in pianobooster 0.6.8+git20190826.56b485f-1 has caused the Debian Bug report #875089, regarding [pianobooster] Future Qt4 removal from Buster to be marked as done. This means that you claim that

Bug#939160: grub-efi-amd64-signed: not installable, broken dependencies

2019-09-02 Thread Matteo F. Vescovi
Hi Colin! On Mon, Sep 2, 2019 at 12:31 PM Colin Watson wrote: > You're using unstable, which isn't guaranteed to stay > dependency-consistent. The way that the signed GRUB packages work means > that there'll always be a short window after a grub2 upload to unstable > when the corresponding signe

Bug#939160: marked as done (grub-efi-amd64-signed: not installable, broken dependencies)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 2 Sep 2019 11:31:28 +0100 with message-id <20190902103128.go3...@riva.ucam.org> and subject line Re: Bug#939160: grub-efi-amd64-signed: not installable, broken dependencies has caused the Debian Bug report #939160, regarding grub-efi-amd64-signed: not installable, broken de

Bug#939045: marked as done (mypy: autopkgtest needs update for new version of lxml)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 09:04:26 + with message-id and subject line Bug#939045: fixed in mypy 0.720-3 has caused the Debian Bug report #939045, regarding mypy: autopkgtest needs update for new version of lxml to be marked as done. This means that you claim that the problem has bee

Bug#934687: Bug#938974: Removed package(s) from unstable

2019-09-02 Thread Yaroslav Halchenko
On Mon, 02 Sep 2019, Debian FTP Masters wrote: > Version: 0.5.3-1+rm oh well -- I have missed all the reports (misconfigured debian.net MX for a few months, heh). So only saw the effect of RM. Just want to clarify heudiconv is maintained python3 support was added upstream as of 0.3 I believ

Bug#933527: snakemake: fails to install: SyntaxError: duplicate argument 'stay_on_remote' in function definition

2019-09-02 Thread Andreas Tille
Hi, On Wed, Jul 31, 2019 at 10:37:22AM +0200, Andreas Beckmann wrote: > Version: 5.5.3-1 > Severity: serious > > during a test with piuparts I noticed your package failed to install. As > per definition of the release team this makes the package too buggy for > a release, thus the severity. > >

Bug#920578: marked as done (gstreamer-vaapi: FTBFS on 32-bit architectures)

2019-09-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Sep 2019 10:38:17 +0300 with message-id <1775b7b6623b8f51cee674e392fd502756fd35a4.ca...@coaxion.net> and subject line Re: gstreamer-vaapi: FTBFS on 32-bit architectures has caused the Debian Bug report #920578, regarding gstreamer-vaapi: FTBFS on 32-bit architectures to b

Bug#931566: Don't complain about suite changes (Acquire::AllowReleaseInfoChange::Suite should be "true")

2019-09-02 Thread Christoph Berg
Re: Paul Wise 2019-09-02 <68737fa6fe19d3c2a71beadefbe69c661dd4d271.ca...@debian.org> > I recently had a similar issue with the backports repos: > > E: Repository 'https://incoming.debian.org/debian-buildd > buildd-stretch-backports-sloppy InRelease' changed its default priority for > apt_prefer