Bug#918973:

2019-09-03 Thread Mario.Limonciello
With Buster out now, can this effort be resumed?

Processed: comitup bug severity

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935731 normal Bug #935731 [comitup] comitup: port to python 3 Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 935731:

Bug#935731: comitup: port to python 3

2019-09-03 Thread David Steele
Severity: normal thanks There is an erroneous "Suggests" control file listing for the Python 2 package. This has no effect on the usability of the package. The issue doesn't rate autoremoval 18 months before the next stable release. The fix is in git, and will be released in due course.

Bug#939362: grantlee5: FTBFS with Qt 5.12.4 in experimental

2019-09-03 Thread Steve Langasek
Source: grantlee5 Version: 5.1.0-2.1 Severity: serious Tags: experimental User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan Dear maintainers, The grantlee5 package fails to build with the version of Qt in experimental, 5.12.4. This was discovered because Ubuntu also has Qt 5.12.4

Bug#921194: marked as done (amarok: Amarok depends on libmariadbd18, which doesn't exist any longer)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Wed, 04 Sep 2019 00:13:32 + with message-id and subject line Re: [Pkg-kde-extras] Processed: Amarok is still not available has caused the Debian Bug report #921194, regarding amarok: Amarok depends on libmariadbd18, which doesn't exist any longer to be marked as done.

Processed: Amarok is still not available

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 921194 Bug #921194 {Done: Boris Pek } [amarok] amarok: Amarok depends on libmariadbd18, which doesn't exist any longer Bug reopened Ignoring request to alter fixed versions of bug #921194 to the same values previously set > thanks

Processed: found 939333 in varnish/6.1.1-1

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 939333 varnish/6.1.1-1 Bug #939333 {Done: Stig Sandbeck Mathisen } [src:varnish] varnish: CVE-2019-15892: VSV3 DoS attack vector Marked as found in versions varnish/6.1.1-1. > thanks Stopping processing here. Please contact me if you

Bug#932505: marked as done (kombu: (build-)depends on cruft package.)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 3 Sep 2019 19:48:01 -0400 with message-id and subject line kombu dropped python2 support has caused the Debian Bug report #932505, regarding kombu: (build-)depends on cruft package. to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#939333: varnish: VSV00003 DoS attack vector

2019-09-03 Thread Moritz Mühlenhoff
On Tue, Sep 03, 2019 at 10:43:55PM +0200, Steinar H. Gunderson wrote: > tags 939333 + patch > thanks > > On Tue, Sep 03, 2019 at 02:27:33PM +0200, Salvatore Bonaccorso wrote: > > See https://varnish-cache.org/security/VSV3.html . A CVE does not > > seem yet to be assigned (but a request

Processed: ROM; Obsolete libs - Qt4, no Qt5 release

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 921194 by 935022 Bug #921194 {Done: Boris Pek } [amarok] amarok: Amarok depends on libmariadbd18, which doesn't exist any longer 921194 was not blocked by any bugs. 921194 was not blocking any bugs. Added blocking bug(s) of 921194: 935022

Bug#875243: [yagf] Future Qt4 removal from Buster

2019-09-03 Thread Moritz Mühlenhoff
On Sat, Sep 09, 2017 at 11:13:30PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: yagf > Version: 0.9.3.2-1 > 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

Bug#939333: varnish: VSV00003 DoS attack vector

2019-09-03 Thread Steinar H. Gunderson
tags 939333 + patch thanks On Tue, Sep 03, 2019 at 02:27:33PM +0200, Salvatore Bonaccorso wrote: > See https://varnish-cache.org/security/VSV3.html . A CVE does not > seem yet to be assigned (but a request pending now). I made a backport to 6.1.1 for stable. It consists of all changes

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

2019-09-03 Thread Moritz Mühlenhoff
On Mon, Sep 02, 2019 at 09:06:04PM +0200, Markus Koschany wrote: > 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

Processed: retitle 939333 to varnish: CVE-2019-15892: VSV00003 DoS attack vector

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 939333 varnish: CVE-2019-15892: VSV3 DoS attack vector Bug #939333 {Done: Stig Sandbeck Mathisen } [src:varnish] varnish: VSV3 DoS attack vector Changed Bug title to 'varnish: CVE-2019-15892: VSV3 DoS attack vector' from

Processed: severity of 935550 is serious

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935550 serious Bug #935550 [src:yubioath-desktop] yubioath-desktop: Qt4 removal from Bullseye Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 935550:

Processed: severity of 935354 is serious

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935354 serious Bug #935354 [src:vitables] vitables: Qt4 removal from Bullseye Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 935354:

Processed: severity of 935359 is serious

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935359 serious Bug #935359 {Done: Mattia Rizzolo } [src:znc] znc: Missing copyright attributions Ignoring request to change severity of Bug 935359 to the same value. > thanks Stopping processing here. Please contact me if you need

Processed: severity of 935348 is serious

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935348 serious Bug #935348 [src:nfs-ganesha] python-nfs-ganesha: Qt4 removal from Bullseye Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 935348:

Processed: severity of 935353 is serious

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935353 serious Bug #935353 [src:vistrails] vistrails: Qt4 removal from Bullseye Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 935353:

Processed: severity of 935346 is serious

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935346 serious Bug #935346 [src:puddletag] puddletag: Qt4 removal from Bullseye Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 935346:

Processed: severity of 935341 is serious

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935341 serious Bug #935341 [src:backintime] backintime-qt4: Qt4 removal from Bullseye Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 935341:

Processed: severity of 935349 is serious

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935349 serious Bug #935349 [src:python-pyface] python-pyface: Qt4 removal from Bullseye Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 935349:

Processed: severity of 935352 is serious

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935352 serious Bug #935352 [src:trimage] trimage: Qt4 removal from Bullseye Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 935352:

Processed: severity of 935343 is serious

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935343 serious Bug #935343 [src:eficas] eficas: Qt4 removal from Bullseye Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 935343:

Processed: severity of 935345 is serious

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 935345 serious Bug #935345 [src:microbegps] microbegps: Qt4 removal from Bullseye Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 935345:

Bug#939333: marked as done (varnish: VSV00003 DoS attack vector)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 20:44:52 + with message-id and subject line Bug#939333: fixed in varnish 6.2.1-1 has caused the Debian Bug report #939333, regarding varnish: VSV3 DoS attack vector to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: Bug#939333: varnish: VSV00003 DoS attack vector

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 939333 + patch Bug #939333 [src:varnish] varnish: VSV3 DoS attack vector Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 939333:

Bug#939308: gkrellm2-cpufreq_0.6.4-5_mips64el.changes REJECTED

2019-09-03 Thread John Paul Adrian Glaubitz
Hi Ansgar! On 9/3/19 10:11 PM, Ansgar wrote: > That should be "Missing mandatory field 'Section'"; fixed for the future > in dak[1]. > > [1]: > https://salsa.debian.org/ftp-team/dak/commit/e839612cdeac09be62453801945be2380d614c57 Ah, that makes more sense, indeed. Glad my mistake was able to

Bug#939308: gkrellm2-cpufreq_0.6.4-5_mips64el.changes REJECTED

2019-09-03 Thread Ansgar
John Paul Adrian Glaubitz writes: >> On 2019-09-02 23:19, Debian FTP Masters wrote: >>> gkrellm-cpufreq_0.6.4-5_mips64el.deb: Missing mandatory field >>> gkrellm-cpufreq_0.6.4-5_mips64el.deb. That should be "Missing mandatory field 'Section'"; fixed for the future in dak[1]. [1]:

Processed: Re: Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-03 Thread Debian Bug Tracking System
Processing control commands: > severity 934491 serious Bug #934491 [libelogind0] libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing Severity set to 'serious' from 'important' -- 934132:

Processed: bug 917686 is forwarded to https://bugs.documentfoundation.org/show_bug.cgi?id=127315

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 917686 https://bugs.documentfoundation.org/show_bug.cgi?id=127315 Bug #917686 [src:lightproof] lightproof: FTBFS: "zipfile is empty" with python 3.7 ("Key Error") Set Bug forwarded-to-address to

Processed: Re: python-acme: Please port to Python 3 and/or drop Python 2 package

2019-09-03 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #935211 [python-acme] python-acme: Please port to Python 3 and/or drop Python 2 package Severity set to 'serious' from 'normal' -- 935211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935211 Debian Bug Tracking System Contact

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

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 16:56:47 + with message-id and subject line Bug#925794: fixed in open-vm-tools 2:10.3.10-3 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

Bug#794466: Virtualbox backport for Stretch?

2019-09-03 Thread Roger Shimizu
On Fri, Aug 23, 2019 at 5:33 PM Gianfranco Costamagna wrote: > > I'm not sure backports team will be happy with this... > and the lack of upstream cooperation is still an issue. Backports team won't complain if the package is in testing. And I think release team won't complain now since it's not

Bug#939299: marked as done (virtualenvwrapper incorrectly dropped virtualenv dependency)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 16:38:46 + with message-id and subject line Bug#939299: fixed in virtualenvwrapper 4.8.4-4 has caused the Debian Bug report #939299, regarding virtualenvwrapper incorrectly dropped virtualenv dependency to be marked as done. This means that you claim that

Bug#928993: Uploading new release of sdaps onto Debian unstable

2019-09-03 Thread Boyuan Yang
Dear sdaps maintainers, I will proceed to upload the new release of sdaps onto Debian unstable after the previous upload onto experimental. If there's any issue, please feel free to let me know. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part

Bug#939338: /usr/include/gpsim/pic-processor.h references non-existent ../config.h

2019-09-03 Thread Helmut Grohne
Package: gpsim-dev Version: 0.31.0-1 Severity: serious Justification: simulide FTBFS Tags: ftbfs Control: affects -1 + src:simulide File: /usr/include/gpsim/pic-processor.h simulide fails to build from source. A build on amd64 ends with: | g++ -c -pipe -g -fdebug-prefix-map=/<>=.

Processed: /usr/include/gpsim/pic-processor.h references non-existent ../config.h

2019-09-03 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:simulide Bug #939338 [gpsim-dev] /usr/include/gpsim/pic-processor.h references non-existent ../config.h Added indication that 939338 affects src:simulide -- 939338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939338 Debian Bug Tracking

Bug#936079: marked as done (python-ceilometerclient (build-)depends on cruft packages.)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 13:44:40 + with message-id and subject line Bug#936079: fixed in python-ceilometerclient 2.9.0-5 has caused the Debian Bug report #936079, regarding python-ceilometerclient (build-)depends on cruft packages. to be marked as done. This means that you claim

Processed: Re: Bug#938962: user-mode-linux needs update for new linux

2019-09-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 help Bug #938962 [user-mode-linux] user-mode-linux needs update for new linux Added tag(s) help. -- 938962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#938962: user-mode-linux needs update for new linux

2019-09-03 Thread Ritesh Raj Sarraf
Control: tag -1 help Adding libpcap's maintainer. Maybe he has some insight. On Fri, 2019-08-30 at 17:28 +0200, Ivo De Decker wrote: > The version of user-mode-linux in testing and unstable build-depends > on > linux-source-4.19, which is no longer available in testing. THere seems to be a

Bug#939078: bro: unfulfilled (build) dependencies libbroker-dev and libbroker0

2019-09-03 Thread Hilko Bengen
* Matthias Klose: > according to https://tracker.debian.org/pkg/bro, it references a > nn-existing libbroker0, and doesn't build on any other architecture > because of a missing libbroker-dev package. libbroker0 does not exist yet; src:broker is waiting in NEW (re-uploaded after the first

Bug#939333: varnish: VSV00003 DoS attack vector

2019-09-03 Thread Salvatore Bonaccorso
Source: varnish Version: 6.2.0-1 Severity: grave Tags: security upstream Justification: user security hole Hi See https://varnish-cache.org/security/VSV3.html . A CVE does not seem yet to be assigned (but a request pending now). Regards, Salvatore

Bug#934905: marked as done (libaqbanking35: libaqbanking not ready for PSD2, will not work after 14 September 2019)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:19:57 + with message-id and subject line Bug#934905: fixed in libaqbanking 5.8.2-0.1 has caused the Debian Bug report #934905, regarding libaqbanking35: libaqbanking not ready for PSD2, will not work after 14 September 2019 to be marked as done. This

Bug#939323: haskell-serialise: huge build logs

2019-09-03 Thread Julien Cristau
Source: haskell-serialise Version: 0.2.1.0-3 Severity: serious root@arm-arm-01:~# ls -lh /home/buildd/logs/haskell-serialise_0.2.1.0-3_armhf-2019-09-02T09\:05\:13Z -rw-rw-r-- 1 buildd buildd 11G Sep 3 11:11 /home/buildd/logs/haskell-serialise_0.2.1.0-3_armhf-2019-09-02T09:05:13Z Most of it

Bug#915753: marked as done (napalm-junos FTBFS with python-pip 18.1)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:06:01 + with message-id and subject line Bug#939255: Removed package(s) from unstable has caused the Debian Bug report #915753, regarding napalm-junos FTBFS with python-pip 18.1 to be marked as done. This means that you claim that the problem has been

Bug#896229: marked as done (python-napalm-iosxr: napalm_iosxr fails to import)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:02:31 + with message-id and subject line Bug#939254: Removed package(s) from unstable has caused the Debian Bug report #896229, regarding python-napalm-iosxr: napalm_iosxr fails to import to be marked as done. This means that you claim that the problem

Bug#915746: marked as done (napalm-iosxr FTBFS with python-pip 18.1)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:02:31 + with message-id and subject line Bug#939254: Removed package(s) from unstable has caused the Debian Bug report #915746, regarding napalm-iosxr FTBFS with python-pip 18.1 to be marked as done. This means that you claim that the problem has been

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

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 10:59:11 + with message-id and subject line Bug#939319: Removed package(s) from unstable has caused the Debian Bug report #937662, regarding python-contract: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

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

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 10:59:36 + with message-id and subject line Bug#939320: Removed package(s) from unstable has caused the Debian Bug report #938035, regarding python-plwm: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#915752: marked as done (napalm-fortios FTBFS with python-pip 18.1)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:01:33 + with message-id and subject line Bug#939252: Removed package(s) from unstable has caused the Debian Bug report #915752, regarding napalm-fortios FTBFS with python-pip 18.1 to be marked as done. This means that you claim that the problem has been

Bug#921704: marked as done (tortoisehg: uninstallable with mercurial 4.9)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:00:11 + with message-id and subject line Bug#939258: Removed package(s) from unstable has caused the Debian Bug report #921704, regarding tortoisehg: uninstallable with mercurial 4.9 to be marked as done. This means that you claim that the problem has

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

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:00:11 + with message-id and subject line Bug#939258: Removed package(s) from unstable has caused the Debian Bug report #935660, regarding tortoisehg: Obsolete libs (python2) - depends python-pyqt5.qsci to be marked as done. This means that you claim

Bug#896250: marked as done (python-napalm-base: napalm_base fails to import)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:00:41 + with message-id and subject line Bug#939250: Removed package(s) from unstable has caused the Debian Bug report #896250, regarding python-napalm-base: napalm_base fails to import to be marked as done. This means that you claim that the problem

Bug#915750: marked as done (napalm-eos FTBFS with python-pip 18.1)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:01:05 + with message-id and subject line Bug#939251: Removed package(s) from unstable has caused the Debian Bug report #915750, regarding napalm-eos FTBFS with python-pip 18.1 to be marked as done. This means that you claim that the problem has been

Bug#839349: marked as done (spykeutils: FTBFS: Tests failures)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 10:58:46 + with message-id and subject line Bug#939082: Removed package(s) from unstable has caused the Debian Bug report #839349, regarding spykeutils: FTBFS: Tests failures to be marked as done. This means that you claim that the problem has been dealt

Bug#896260: marked as done (python-napalm-ios: napalm_ios fails to import)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:01:59 + with message-id and subject line Bug#939253: Removed package(s) from unstable has caused the Debian Bug report #896260, regarding python-napalm-ios: napalm_ios fails to import to be marked as done. This means that you claim that the problem has

Bug#915748: marked as done (napalm-base FTBFS with python-pip 18.1)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:00:41 + with message-id and subject line Bug#939250: Removed package(s) from unstable has caused the Debian Bug report #915748, regarding napalm-base FTBFS with python-pip 18.1 to be marked as done. This means that you claim that the problem has been

Bug#915747: marked as done (napalm-ios FTBFS with python-pip 18.1)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:01:59 + with message-id and subject line Bug#939253: Removed package(s) from unstable has caused the Debian Bug report #915747, regarding napalm-ios FTBFS with python-pip 18.1 to be marked as done. This means that you claim that the problem has been

Bug#896280: marked as done (python-napalm-fortios: napalm_fortios fails to import)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:01:33 + with message-id and subject line Bug#939252: Removed package(s) from unstable has caused the Debian Bug report #896280, regarding python-napalm-fortios: napalm_fortios fails to import to be marked as done. This means that you claim that the

Bug#896412: marked as done (python-napalm-eos: napalm_eos fails to import)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 11:00:41 + with message-id and subject line Bug#939250: Removed package(s) from unstable has caused the Debian Bug report #896250, regarding python-napalm-eos: napalm_eos fails to import to be marked as done. This means that you claim that the problem has

Bug#844402: marked as done (spykeviewer: FTBFS: ImportError: No module named spyderlib.widgets.variableexplorer.collectionseditor)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 10:58:23 + with message-id and subject line Bug#939081: Removed package(s) from unstable has caused the Debian Bug report #844402, regarding spykeviewer: FTBFS: ImportError: No module named spyderlib.widgets.variableexplorer.collectionseditor to be marked

Bug#937632: pythoncard: Python2 removal in sid/bullseye

2019-09-03 Thread Scott Kitterman
Blocked until libkate it either removed (likely) or ported (unlikely). Scott K

Processed (with 1 error): block 937632 with 93936883

2019-09-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 937632 with 93936883 Bug #937632 [ftp.debian.org] RM: pythoncard -- RoQA; orphaned; Python 2 only; dead upstream; low popcon No valid blocking bug(s) given; not doing anything Failed to set blocking bugs of 937632: Unknown/archived

Bug#938925: xmds2: fails mpi hdf5 tests

2019-09-03 Thread Drew Parsons
Package: xmds2 Version: 3.0.0+dfsg-2 Followup-For: Bug #938925 Control: tags -1 + ftbfs The test failure also means xmds2 FTBFS.

Processed: Re: xmds2: fails mpi hdf5 tests

2019-09-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + ftbfs Bug #938925 [src:xmds2] xmds2: fails mpi hdf5 tests Added tag(s) ftbfs. -- 938925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#939308: gkrellm2-cpufreq_0.6.4-5_mips64el.changes REJECTED

2019-09-03 Thread John Paul Adrian Glaubitz
Dear FTP Masters! > On 2019-09-02 23:19, Debian FTP Masters wrote: >> gkrellm-cpufreq_0.6.4-5_mips64el.deb: Missing mandatory field >> gkrellm-cpufreq_0.6.4-5_mips64el.deb. >> >> >> >> === >> >> Please feel free to respond to this email if you don't understand why >> your files were rejected, or

Bug#939309: marked as done (redmine: Postinstallation script fails)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 3 Sep 2019 09:26:32 + with message-id <20190903092632.GJ1480@debian> and subject line Re: [DRE-maint] Bug#939309: Solved has caused the Debian Bug report #939309, regarding redmine: Postinstallation script fails to be marked as done. This means that you claim that the

Bug#934788: marked as done (gst-plugins-good1.0 non-buildd binaries)

2019-09-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Sep 2019 09:06:22 + with message-id and subject line Bug#934788: fixed in gst-plugins-good1.0 1.16.0-3 has caused the Debian Bug report #934788, regarding gst-plugins-good1.0 non-buildd binaries to be marked as done. This means that you claim that the problem has

Bug#939311: monero: FTBFS on arm64: final link failed: file in wrong format

2019-09-03 Thread Jonathan Wiltshire
Source: monero Version: 0.14.1.2-1 Severity: serious Justification: ftbfs Hi, monero fails to build from source in sid on arm64, tail of the log is: | /usr/bin/ld: can not size stub section: invalid operation | /usr/bin/ld: linker stubs: file class ELFCLASSNONE incompatible with ELFCLASS64 |

Bug#939308: gkrellm2-cpufreq_0.6.4-5_mips64el.changes REJECTED

2019-09-03 Thread Aurelien Jarno
On 2019-09-03 09:25, John Paul Adrian Glaubitz wrote: > Hello Aurelien! > > On 9/3/19 9:19 AM, Aurelien Jarno wrote: > > Package: gkrellm2-cpufreq > > Version: 0.6.4-5 > > Severity: serious > > > > On 2019-09-02 23:19, Debian FTP Masters wrote: > >> gkrellm-cpufreq_0.6.4-5_mips64el.deb: Missing

Bug#939309: Solved

2019-09-03 Thread Alvaro Gamez
Please, close this bug, as I've already found what was the issue. This system had a very old and deprecated version of redmine that was manually installed and it was conflicting with the new package. Sorry for the inconvenience, I was way too fast on reporting this! -- Álvaro Gámez Machado

Bug#939309: redmine: Postinstallation script fails

2019-09-03 Thread Alvaro G. M.
Package: redmine Version: 4.0.4-1 Severity: grave Dear Maintainer, This version seems uninstallable because post script script fails: Setting up redmine (4.0.4-1) ... Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. dbconfig-common: writing config to

Bug#939308: gkrellm2-cpufreq_0.6.4-5_mips64el.changes REJECTED

2019-09-03 Thread John Paul Adrian Glaubitz
Hello Aurelien! On 9/3/19 9:19 AM, Aurelien Jarno wrote: > Package: gkrellm2-cpufreq > Version: 0.6.4-5 > Severity: serious > > On 2019-09-02 23:19, Debian FTP Masters wrote: >> gkrellm-cpufreq_0.6.4-5_mips64el.deb: Missing mandatory field >> gkrellm-cpufreq_0.6.4-5_mips64el.deb. Can you

Bug#939308: gkrellm2-cpufreq_0.6.4-5_mips64el.changes REJECTED

2019-09-03 Thread Aurelien Jarno
Package: gkrellm2-cpufreq Version: 0.6.4-5 Severity: serious On 2019-09-02 23:19, Debian FTP Masters wrote: > gkrellm-cpufreq_0.6.4-5_mips64el.deb: Missing mandatory field > gkrellm-cpufreq_0.6.4-5_mips64el.deb. > > > > === > > Please feel free to respond to this email if you don't

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

2019-09-03 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;

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

2019-09-03 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