Bug#944824: marked as done (pylint-celery (build-)depends on cruft package.)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Dec 2019 07:49:24 + with message-id and subject line Bug#944824: fixed in pylint-celery 0.3-5 has caused the Debian Bug report #944824, regarding pylint-celery (build-)depends on cruft package. to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#940906: make autopkgtest working

2019-12-09 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #940906 [src:glm] glm: autopkgtest regression: CMake Error at CMakeLists.txt:6 (find_package): Severity set to 'serious' from 'important' -- 940906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940906 Debian Bug Tracking System

Bug#938520: marked as done (sozi: Python2 removal in sid/bullseye)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Dec 2019 05:09:38 + with message-id and subject line Bug#946489: Removed package(s) from unstable has caused the Debian Bug report #938520, regarding sozi: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#885482: marked as done (sozi: Depends on unmaintained pygtk)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Dec 2019 05:09:38 + with message-id and subject line Bug#946489: Removed package(s) from unstable has caused the Debian Bug report #885482, regarding sozi: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been dealt

Bug#936978: marked as done (magicor: Python2 removal in sid/bullseye)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Dec 2019 05:09:01 + with message-id and subject line Bug#946488: Removed package(s) from unstable has caused the Debian Bug report #936978, regarding magicor: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#885352: marked as done (magicor: Depends on unmaintained pygtk)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Dec 2019 05:09:01 + with message-id and subject line Bug#946488: Removed package(s) from unstable has caused the Debian Bug report #885352, regarding magicor: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been

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

2019-12-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Dec 2019 02:43:17 + with message-id and subject line Bug#937568: fixed in pytest-xdist 1.30.0-2 has caused the Debian Bug report #937568, regarding pytest-xdist: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#946497: zfs-dkms: fails to build module for 5.3.0-3-amd64

2019-12-09 Thread Petter Reinholdtsen
[Andreas Beckmann] > during a test with piuparts I noticed your package failed to install. Thank you for the heads up. Looking at the attached log, I see gcc-9 is installed, and thus the error message is very strange: > Building initial module for 5.3.0-3-amd64 > configure: error: in

Processed: severity of 946492 is serious, found 903794 in 3.0-a9+debian.1-3

2019-12-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 946492 serious Bug #946492 [vdjtools] vdjtools: broken symlink: /usr/share/java/vdjtools.jar -> vdjtools-1.2.1+git20190311.jar Severity set to 'serious' from 'normal' > found 903794 3.0-a9+debian.1-3 Bug #903794 [lmbench-doc]

Bug#946497: zfs-dkms: fails to build module for 5.3.0-3-amd64

2019-12-09 Thread Andreas Beckmann
Package: zfs-dkms Version: 0.8.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, 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. >From the

Bug#946494: cpl-plugin-kmos-calib: download location no longer available ?

2019-12-09 Thread Andreas Beckmann
Package: cpl-plugin-kmos-calib Version: 2.1.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, 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

Bug#946396: marked as done (glibc+libxcrypt breaks cross-toolchain-base)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 23:19:57 + with message-id and subject line Bug#946396: fixed in glibc 2.29-6 has caused the Debian Bug report #946396, regarding glibc+libxcrypt breaks cross-toolchain-base to be marked as done. This means that you claim that the problem has been dealt

Processed: Bug#946396 marked as pending in glibc

2019-12-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #946396 [src:glibc] glibc+libxcrypt breaks cross-toolchain-base Ignoring request to alter tags of bug #946396 to the same tags previously set -- 946396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946396 Debian Bug Tracking System Contact

Bug#946396: marked as pending in glibc

2019-12-09 Thread Aurelien Jarno
Control: tag -1 pending Hello, Bug #946396 in glibc 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#946396 marked as pending in glibc

2019-12-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #946396 [src:glibc] glibc+libxcrypt breaks cross-toolchain-base Added tag(s) pending. -- 946396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#946396: marked as pending in glibc

2019-12-09 Thread Aurelien Jarno
Control: tag -1 pending Hello, Bug #946396 in glibc 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#946484: marked as done (internetarchive: DistributionNotFound: The 'backports.csv' distribution was not found)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 23:07:24 + with message-id and subject line Bug#946484: fixed in python-internetarchive 1.9.0-2 has caused the Debian Bug report #946484, regarding internetarchive: DistributionNotFound: The 'backports.csv' distribution was not found to be marked as done.

Bug#946405: nextcloud-desktop: Nextcloud desktop client crash when trying to enter login/password

2019-12-09 Thread Bernhard Übelacker
Hello Ludovic, I tried to collect some more information from your crash dump. With debug symbols this backtrace should look like below. I guess you are running a nvidia graphics card with the nouveau drivers? As a workaround it may work if you start the client from a terminal by following:

Bug#946433: marked as done (python3-jpylyzer: missing Breaks+Replaces: python-jpylyzer (<< 1.18.0-3.1))

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 22:21:48 + with message-id and subject line Bug#946433: fixed in jpylyzer 1.18.0-3.2 has caused the Debian Bug report #946433, regarding python3-jpylyzer: missing Breaks+Replaces: python-jpylyzer (<< 1.18.0-3.1) to be marked as done. This means that you

Bug#946484: internetarchive: DistributionNotFound: The 'backports.csv' distribution was not found

2019-12-09 Thread Antoine Beaupré
On 2019-12-09 22:51:16, Jakub Wilk wrote: > Package: internetarchive > Version: 1.8.5-1 > Severity: grave > > The ia command doesn't work at all: > >$ ia help >Traceback (most recent call last): > File "/usr/bin/ia", line 6, in >from pkg_resources import load_entry_point >

Bug#946484: internetarchive: DistributionNotFound: The 'backports.csv' distribution was not found

2019-12-09 Thread Jakub Wilk
Package: internetarchive Version: 1.8.5-1 Severity: grave The ia command doesn't work at all: $ ia help Traceback (most recent call last): File "/usr/bin/ia", line 6, in from pkg_resources import load_entry_point File

Processed: jpylyzer: diff for NMU version 1.18.0-3.2

2019-12-09 Thread Debian Bug Tracking System
Processing control commands: > tags 946433 + patch Bug #946433 [python3-jpylyzer] python3-jpylyzer: missing Breaks+Replaces: python-jpylyzer (<< 1.18.0-3.1) Added tag(s) patch. -- 946433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946433 Debian Bug Tracking System Contact

Bug#946433: jpylyzer: diff for NMU version 1.18.0-3.2

2019-12-09 Thread Sandro Tosi
Control: tags 946433 + patch Dear maintainer, I've prepared an NMU for jpylyzer (versioned as 1.18.0-3.2). The diff is attached to this message. Regards. diff -Nru jpylyzer-1.18.0/debian/changelog jpylyzer-1.18.0/debian/changelog --- jpylyzer-1.18.0/debian/changelog 2019-11-29

Bug#946347: Thunderbird: After dist-upgrade thunderbird thinks it is too old.

2019-12-09 Thread Carsten Schoenert
Control: severity -1 normal Hello Robert, On Sat, Dec 07, 2019 at 05:25:22PM +0100, Robert Pommrich wrote: > After a dist-upgrade from stretch to buster with thunderbird installed > in version 68.2.2-1~deb9u1 and being upgraded to version > 68.2.2-1~deb10u1 thunderbird shows a message at the

Processed: Re: Bug#946347: Thunderbird: After dist-upgrade thunderbird thinks it is too old.

2019-12-09 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #946347 [thunderbird] Thunderbird: After dist-upgrade thunderbird thinks it is too old. Severity set to 'normal' from 'grave' -- 946347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946347 Debian Bug Tracking System Contact

Bug#944742: marked as done (assimp: testsuite regression)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 20:48:26 + with message-id and subject line Bug#944742: fixed in assimp 5.0.0~ds2-3 has caused the Debian Bug report #944742, regarding assimp: testsuite regression to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#946415: [Pkg-rust-maintainers] Bug#946415: rust-cargo Build-Depends on librust-crates-io-0.25+default-dev which doesn't exist

2019-12-09 Thread Sylvestre Ledru
Paul, I do find this bugs valuable on my side. Thanks for filling them! Sylvestre Le 09/12/2019 à 00:30, Ximin Luo a écrit : Hi, This type of bug is a natural artifact of the way rust crates are structured and updated, and the Rust team is continually aware of these types of bugs. There is

Bug#945453: marked as done (camitk: FTBFS, uninstallable build-deps in unstable)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 20:43:02 +0100 with message-id <6fa2fefa7bfae02457636d4fe8c6f7a10d24f631.ca...@gmail.com> and subject line Re: camitk: FTBFS, uninstallable build-deps in unstable has caused the Debian Bug report #945453, regarding camitk: FTBFS, uninstallable build-deps in

Bug#946470: libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

2019-12-09 Thread Andreas Beckmann
On 09/12/2019 18.37, Rene Engelhard wrote: > Either asap or next week when rc1 will be there (but either way will be NEW > given the previous versions > are still waiting in NEW since mid-November...) No need to hurry ... as long as it is fixed once these packages go to sid. Andreas

Bug#946415: rust-cargo Build-Depends on librust-crates-io-0.25+default-dev which doesn't exist

2019-12-09 Thread Paul Gevers
Hi Ximin, On 09-12-2019 00:30, Ximin Luo wrote: > This type of bug is a natural artifact of the way rust crates are structured and updated, and the Rust team is continually aware of these types of bugs. There is no need to file these types of bugs for packages in unstable as the testing migration

Bug#945322: marked as done (ruby-maxitest: uninstallable in sid: Depends: ruby-minitest (< 5.12.0) but 5.13.0-1 is to be installed)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 19:06:23 + with message-id and subject line Bug#945322: fixed in ruby-maxitest 3.6.0-1 has caused the Debian Bug report #945322, regarding ruby-maxitest: uninstallable in sid: Depends: ruby-minitest (< 5.12.0) but 5.13.0-1 is to be installed to be marked

Bug#945489: closed by Sylvestre Ledru (Bug#945489: fixed in llvm-toolchain-9 1:9.0.1~+rc2-1~exp1)

2019-12-09 Thread Sylvestre Ledru
 Hello, Le 09/12/2019 à 19:04, Lisandro Damián Nicanor Pérez Meyer a écrit : Hy Sylvestre! On 19/12/07 04:15, Debian Bug Tracking System wrote: [snip] Format: 1.8 Date: Tue, 03 Dec 2019 07:56:16 +0100 Source: llvm-toolchain-9 Architecture: source Version: 1:9.0.1~+rc2-1~exp1 Distribution:

Processed: 937727

2019-12-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 937727 src:python-enable Bug #937727 [ftp.debian.org] RM: python-enable -- RoQA; unmaintained; low popcon; blocking py2 removal; no rdeps Bug reassigned from package 'ftp.debian.org' to 'src:python-enable'. Ignoring request to alter

Bug#937727: RM python-enable

2019-12-09 Thread Varun Hiremath
reassign -1 src:python-enable retitle -1 python-enable: convert package to Python 3 thanks Hi Dmitry, Yes, sorry for the delay but I have finally gotten some time to spend on my Debian packages. Thanks to you and Scott for taking care of traits, traitsui and pyface! I plan to work on enable and

Bug#945489: closed by Sylvestre Ledru (Bug#945489: fixed in llvm-toolchain-9 1:9.0.1~+rc2-1~exp1)

2019-12-09 Thread Lisandro Damián Nicanor Pérez Meyer
Hy Sylvestre! On 19/12/07 04:15, Debian Bug Tracking System wrote: [snip] > Format: 1.8 > Date: Tue, 03 Dec 2019 07:56:16 +0100 > Source: llvm-toolchain-9 > Architecture: source > Version: 1:9.0.1~+rc2-1~exp1 > Distribution: experimental > Urgency: medium > Maintainer: LLVM Packaging Team >

Bug#946470: libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

2019-12-09 Thread Rene Engelhard
Hi, On Mon, Dec 09, 2019 at 05:20:49PM +0100, Andreas Beckmann wrote: > This bug is present in several libreoffice-l10n-?? packages > and libreoffice-help-common. Maybe also in more packages > depending on these failing ones since they cannot be tested. Nah, that script was just ran on -help-*

Processed: Bug#946470 marked as pending in libreoffice

2019-12-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #946470 [libreoffice-l10n-de] libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Added tag(s) pending. -- 946470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946470 Debian Bug Tracking System Contact

Bug#946470: marked as pending in libreoffice

2019-12-09 Thread Rene Engelhard
Control: tag -1 pending Hello, Bug #946470 in libreoffice 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#946474: fluidsynth: Incomplete debian/copyright?

2019-12-09 Thread Chris Lamb
Source: fluidsynth Version: 2.0.5-1 Severity: serious Justication: Policy § 12.5 X-Debbugs-CC: Fabian Greffrath , ftpmas...@debian.org Hi, I just ACCEPTed fluidsynth from NEW but noticed it was missing attribution in debian/copyright for at least the Creative Commons documentation... This is

Bug#946473: llvm-9-tools: missing Breaks+Replaces: libclang-common-9-dev (<< 1:9.0.1~+rc2)

2019-12-09 Thread Andreas Beckmann
Package: llvm-9-tools Version: 1:9.0.1~+rc2-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails

Bug#943620: marked as done (gammapy's tests fail with numpy-1.17 and python3.8)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 17:05:32 + with message-id and subject line Bug#943620: fixed in gammapy 0.15-1 has caused the Debian Bug report #943620, regarding gammapy's tests fail with numpy-1.17 and python3.8 to be marked as done. This means that you claim that the problem has been

Processed: affects 942469

2019-12-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 942469 + r-cran-tidyverse Bug #942469 [r-cran-rmarkdown] r-cran-rmarkdown: directory to symlink conversion not correctly handled on upgrade Added indication that 942469 affects r-cran-tidyverse > thanks Stopping processing here. Please

Bug#946223: marked as done ([NMU] FTFBS with CGAL 5.0)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 16:35:31 + with message-id and subject line Bug#946223: fixed in yade 2019.12~git~0~e74819ea-1 has caused the Debian Bug report #946223, regarding [NMU] FTFBS with CGAL 5.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#946470: libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

2019-12-09 Thread Andreas Beckmann
Package: libreoffice-l10n-de Version: 1:6.4.0~beta1-0reprotest1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libreoffice-l10n-ja libreoffice-l10n-he libreoffice-l10n-in libreoffice-l10n-za libreoffice-help-common Hi, an upgrade test with piuparts

Processed: libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

2019-12-09 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + libreoffice-l10n-ja libreoffice-l10n-he libreoffice-l10n-in > libreoffice-l10n-za libreoffice-help-common Bug #946470 [libreoffice-l10n-de] libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Added indication that

Bug#946436: marked as done (libplplot-data: missing Breaks+Replaces: libplplot17 (<< 5.15.0+dfsg-8))

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 15:37:41 + with message-id and subject line Bug#946436: fixed in plplot 5.15.0+dfsg-9 has caused the Debian Bug report #946436, regarding libplplot-data: missing Breaks+Replaces: libplplot17 (<< 5.15.0+dfsg-8) to be marked as done. This means that you

Bug#946465: librust-rand+alloc-dev: does not find upgrade path from buster to bullseye

2019-12-09 Thread Andreas Beckmann
Package: librust-rand+alloc-dev Version: 0.6.4-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails. >From the attached

Processed: notfound 603757 in 5:77, reassign 946412 to src:janus, tagging 946452

2019-12-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 603757 5:77 Bug #603757 {Done: Aurélien COUDERC } [kde-plasma-desktop] plasma: Multiple-monitor issues with panel No longer marked as found in versions meta-kde/5:77. > reassign 946412 src:janus Bug #946412 [janus-gateway]

Processed: Bug#944742 marked as pending in assimp

2019-12-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #944742 [src:assimp] assimp: testsuite regression Added tag(s) pending. -- 944742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#944742: marked as pending in assimp

2019-12-09 Thread IOhannes zmölnig
Control: tag -1 pending Hello, Bug #944742 in assimp 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#946448: marked as done (z3: FTBFS: ../src/util/mpz.cpp:57:30: error: definition of ‘uint32_t __builtin_ctz(uint32_t)’ ambiguates built-in declaration ‘int __builtin_ctz(unsigned int)’)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 13:20:11 + with message-id and subject line Bug#946448: fixed in z3 4.8.7-2 has caused the Debian Bug report #946448, regarding z3: FTBFS: ../src/util/mpz.cpp:57:30: error: definition of ‘uint32_t __builtin_ctz(uint32_t)’ ambiguates built-in declaration

Bug#946455: marked as done (nomad: FTBFS (missing build-dependency on tzdata))

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 12:49:28 + with message-id and subject line Bug#946455: fixed in nomad 0.10.2+dfsg1-2 has caused the Debian Bug report #946455, regarding nomad: FTBFS (missing build-dependency on tzdata) to be marked as done. This means that you claim that the problem has

Bug#946427: marked as done (python3-vcf: missing Breaks+Replaces: python3-pyvcf)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 12:20:14 + with message-id and subject line Bug#946427: fixed in python-pyvcf 0.6.8+git20170215.476169c-5 has caused the Debian Bug report #946427, regarding python3-vcf: missing Breaks+Replaces: python3-pyvcf to be marked as done. This means that you

Processed: Bug#946455 marked as pending in nomad

2019-12-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #946455 [src:nomad] nomad: FTBFS (missing build-dependency on tzdata) Added tag(s) pending. -- 946455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#946455: marked as pending in nomad

2019-12-09 Thread Dmitry Smirnov
Control: tag -1 pending Hello, Bug #946455 in nomad 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: please stop building python-pytest-xdist now

2019-12-09 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #937568 [src:pytest-xdist] pytest-xdist: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' -- 937568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937568 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#945472: python-datrie: FTBFS with recent hypothesis version

2019-12-09 Thread Matthias Klose
On 09.12.19 11:46, Andreas Tille wrote: > Hi, > > I have upgraded python-datrie in Git[1] to latest upstream version > (0.8). It shows the same issue - so I admit I have no better clue than > reporting the issue upstream which I'd rather leave to the official > Uploader of the package. > > BTW,

Bug#945472: python-datrie: FTBFS with recent hypothesis version

2019-12-09 Thread Andreas Tille
Hi, I have upgraded python-datrie in Git[1] to latest upstream version (0.8). It shows the same issue - so I admit I have no better clue than reporting the issue upstream which I'd rather leave to the official Uploader of the package. BTW, we probably should expect build issues with Python

Processed: severity of 937808 is important

2019-12-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # I don't think this warrants serious severity. > severity 937808 important Bug #937808 [src:python-hglib] python-hglib: Python2 removal in sid/bullseye Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact

Bug#937727: RM python-enable

2019-12-09 Thread Dmitry Shachnev
Hi Varun! On Sun, Dec 08, 2019 at 10:35:51PM -0500, Scott Talbert wrote: > Control: reassign -1 ftp.debian.org > Control: retitle -1 RM: python-enable -- RoQA; unmaintained; low popcon; > blocking py2 removal; no rdeps I see you started working on python-enable in Git [1]. If you want to

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

2019-12-09 Thread Emmanuel Bourg
Hi Thorsten, The issue I reported that prevented systemd-sysusers from being used without systemd as the init system has just been fixed (#926316). So in theory we should be able to use it with other init systems. But the fact that elogind conflicts with systemd creates another hurdle. If the

Bug#946455: nomad: FTBFS (missing build-dependency on tzdata)

2019-12-09 Thread Santiago Vila
Package: src:nomad Version: 0.10.2+dfsg1-1 Severity: serious Tags: ftbfs Dear maintainer: This package fails to build in a minimal chroot including only essential and build-essential packages: [...] --- FAIL:

Bug#946425: marked as done (python3-pubsub: missing Breaks+Replaces: python3-pypubsub)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 08:41:34 + with message-id and subject line Bug#946425: fixed in python-pypubsub 4.0.3-4 has caused the Debian Bug report #946425, regarding python3-pubsub: missing Breaks+Replaces: python3-pypubsub to be marked as done. This means that you claim that the

Bug#946426: marked as done (python-pbcore: depends on old pylint3)

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 08:41:28 + with message-id and subject line Bug#946426: fixed in python-pbcore 1.7.1+git20191121.7947eb7+dfsg-3 has caused the Debian Bug report #946426, regarding python-pbcore: depends on old pylint3 to be marked as done. This means that you claim that

Bug#946264: marked as done (openems: FTBFS (affects CGAL transition))

2019-12-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Dec 2019 08:41:20 + with message-id and subject line Bug#946264: fixed in openems 0.0.35+git20190103.6a75e98+dfsg.1-2 has caused the Debian Bug report #946264, regarding openems: FTBFS (affects CGAL transition) to be marked as done. This means that you claim that

Bug#946452: mpqc3: FTBFS in sid

2019-12-09 Thread merkys
Source: mpqc3 Version: 0.0~git20170114-4 Severity: serious Hello, mpqc3 seems to FTBFS in sid with the following: In file included from /<>/src/lib/chemistry/qc/libint2/tbintlibint2.h:33, from /<>/src/lib/chemistry/qc/libint2/tbintlibint2.cc:34: