Bug#946850: LAST build fails on non-amd64 platforms.

2019-12-17 Thread Charles Plessy
[CCed to Debians' bug tracking system] Hi Martin, LAST fails to build on non-amd64 platforms, where it does not find the immintrin.h header file. We can either try to fix that (most likely relying on you to do it), or restrict the builds to the amd64 platform (missing opportunities to find porta

Bug#946566: marked as done (r-cran-xml2: broken symlink: /usr/lib/R/site-library/xml2/extdata/html5shiv.min.js -> ../../../../nodejs/html5shiv/dist/html5shiv.min.js)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 07:34:14 + with message-id and subject line Bug#946566: fixed in r-cran-xml2 1.2.2-2 has caused the Debian Bug report #946566, regarding r-cran-xml2: broken symlink: /usr/lib/R/site-library/xml2/extdata/html5shiv.min.js -> ../../../../nodejs/html5shiv/dist

Bug#945920: Chrome bug

2019-12-17 Thread PPHome2
On Tue, 17 Dec 2019 11:00:44 -0800 Csaba Toth < > Are the other reporters here also have AMD CPU or GPU?> It doesn't depend on hardware I think.In the office I use Intel CPU + Intel GPU, at home I use Intel CPU + AMD GPU.The bug also exists under GNOME Xorg and Wayland.I think it could be caused b

Processed: bug 938766 is forwarded to https://github.com/unbit/uwsgi/pull/2062

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 938766 https://github.com/unbit/uwsgi/pull/2062 Bug #938766 [src:uwsgi] uwsgi: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'https://github.com/unbit/uwsgi/pull/2062'. > thanks Stopping processing here. Please contact

Bug#935449: marked as done (Build-Depends on removed python-celery)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 06:02:54 + with message-id and subject line Bug#946925: Removed package(s) from unstable has caused the Debian Bug report #935449, regarding Build-Depends on removed python-celery to be marked as done. This means that you claim that the problem has been dea

Bug#938663: marked as done (thumbor: Python2 removal in sid/bullseye)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 06:02:54 + with message-id and subject line Bug#946925: Removed package(s) from unstable has caused the Debian Bug report #935450, regarding thumbor: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#943243: marked as done (uligo: Python2 removal in sid/bullseye)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 06:04:14 + with message-id and subject line Bug#946928: Removed package(s) from unstable has caused the Debian Bug report #943243, regarding uligo: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dea

Bug#943213: marked as done (shogun: Python2 removal in sid/bullseye)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 06:03:40 + with message-id and subject line Bug#946927: Removed package(s) from unstable has caused the Debian Bug report #943213, regarding shogun: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been de

Bug#925827: marked as done (shogun: ftbfs with GCC-9)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 06:03:40 + with message-id and subject line Bug#946927: Removed package(s) from unstable has caused the Debian Bug report #925827, regarding shogun: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#935812: marked as done (FTBFS: FAIL: test_can_get_304_with_last_modified (tests.handlers.test_base_handler.ImageOperationsWithLastModifiedTestCase))

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 06:02:54 + with message-id and subject line Bug#946925: Removed package(s) from unstable has caused the Debian Bug report #935812, regarding FTBFS: FAIL: test_can_get_304_with_last_modified (tests.handlers.test_base_handler.ImageOperationsWithLastModifiedTe

Bug#935450: marked as done (Please port to Python 3 or remove)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 06:02:54 + with message-id and subject line Bug#946925: Removed package(s) from unstable has caused the Debian Bug report #935450, regarding Please port to Python 3 or remove to be marked as done. This means that you claim that the problem has been dealt wi

Bug#943276: marked as done (wmii: Python2 removal in sid/bullseye)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 06:04:47 + with message-id and subject line Bug#946929: Removed package(s) from unstable has caused the Debian Bug report #943276, regarding wmii: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Bug#938766: uwsgi: Python2 removal in sid/bullseye

2019-12-17 Thread Xavier
Hi, uwsgi is going to be removed from testing. Can someone fix this issue ? Cheers, Xaavier

Processed: Re: ipykernel: failing tests with python3.8

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #943901 [ipykernel] ipykernel: failing tests with python3.8 Severity set to 'serious' from 'important' > tags -1 -patch Bug #943901 [ipykernel] ipykernel: failing tests with python3.8 Removed tag(s) patch. -- 943901: https://bugs.debian.org/

Bug#913015: Bug#936372: dcmstack: diff for version 0.7-2

2019-12-17 Thread Sandro Tosi
On Tue, Dec 17, 2019 at 11:41 PM Yaroslav Halchenko wrote: > > > On Tue, 17 Dec 2019, Sandro Tosi wrote: > > > Control: tags 913015 + patch > > Control: tags 936372 + patch > > Control: tags 942992 + patch > > > > Dear maintainer, > > > I've prepared an upload for dcmstack (versioned as 0.7-2). Th

Bug#913015: Bug#936372: dcmstack: diff for version 0.7-2

2019-12-17 Thread Yaroslav Halchenko
On Tue, 17 Dec 2019, Sandro Tosi wrote: > Control: tags 913015 + patch > Control: tags 936372 + patch > Control: tags 942992 + patch > Dear maintainer, > I've prepared an upload for dcmstack (versioned as 0.7-2). The diff > is attached to this message. > i dont have access to the GH repos, so

Bug#946858: marked as done (ruby-grib: Should this package be removed?)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 04:04:09 + with message-id and subject line Bug#946858: fixed in ruby-grib 0.4.0-4 has caused the Debian Bug report #946858, regarding ruby-grib: Should this package be removed? to be marked as done. This means that you claim that the problem has been dealt

Processed: Bug#946858 marked as pending in ruby-grib

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #946858 [src:ruby-grib] ruby-grib: Should this package be removed? Added tag(s) pending. -- 946858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#946858: marked as pending in ruby-grib

2019-12-17 Thread Youhei SASAKI
Control: tag -1 pending Hello, Bug #946858 in ruby-grib 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/ruby-team/ruby-grib/commit/67263421aa3aa79ea308a2758e290

Bug#942992: marked as done (dcmstack: Python2 removal in sid/bullseye)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 03:19:22 + with message-id and subject line Bug#942992: fixed in dcmstack 0.7-2 has caused the Debian Bug report #942992, regarding dcmstack: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt wit

Bug#913015: marked as done (python{,3}-dcmstack: both ship /usr/bin/dcmstack, /usr/bin/nitool)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 03:19:21 + with message-id and subject line Bug#913015: fixed in dcmstack 0.7-2 has caused the Debian Bug report #913015, regarding python{,3}-dcmstack: both ship /usr/bin/dcmstack, /usr/bin/nitool to be marked as done. This means that you claim that the pr

Bug#946858: [DRE-maint] Bug#946858: not fixed with ruby-grib 0.4.0-3

2019-12-17 Thread Youhei SASAKI
Hi, On Wed, 18 Dec 2019 03:45:08 +0900, Boyuan Yang wrote: > > On Tue, 17 Dec 2019 03:04:39 + Youhei SASAKI > wrote: > > ruby-grib (0.4.0-3) unstable; urgency=medium > > . > >[ Youhei SASAKI ] > >* Use eccodes instead of grib_api (Closes: #946858) > > Unfortunately ruby-grib stil

Bug#913015: dcmstack: diff for version 0.7-2

2019-12-17 Thread Sandro Tosi
Control: tags 913015 + patch Control: tags 936372 + patch Control: tags 942992 + patch Dear maintainer, I've prepared an upload for dcmstack (versioned as 0.7-2). The diff is attached to this message. i dont have access to the GH repos, so i post the changes here Regards. diff -Nru dcmstack-0

Processed: dcmstack: diff for version 0.7-2

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > tags 913015 + patch Bug #913015 [python-dcmstack,python3-dcmstack] python{,3}-dcmstack: both ship /usr/bin/dcmstack, /usr/bin/nitool Ignoring request to alter tags of bug #913015 to the same tags previously set > tags 936372 + patch Bug #936372 [src:dcmstack] dcmsta

Processed: dcmstack: diff for version 0.7-2

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > tags 913015 + patch Bug #913015 [python-dcmstack,python3-dcmstack] python{,3}-dcmstack: both ship /usr/bin/dcmstack, /usr/bin/nitool Added tag(s) patch. > tags 936372 + patch Bug #936372 [src:dcmstack] dcmstack: Python2 removal in sid/bullseye Added tag(s) patch. >

Processed: dcmstack: diff for version 0.7-2

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > tags 913015 + patch Bug #913015 [python-dcmstack,python3-dcmstack] python{,3}-dcmstack: both ship /usr/bin/dcmstack, /usr/bin/nitool Ignoring request to alter tags of bug #913015 to the same tags previously set > tags 936372 + patch Bug #936372 [src:dcmstack] dcmsta

Processed: skales: Python2 removal in sid/bullseye

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > affects 943273 u-boot Bug #943273 [src:skales] skales: Python2 removal in sid/bullseye Added indication that 943273 affects u-boot -- 943273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943273 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#943273: skales: Python2 removal in sid/bullseye

2019-12-17 Thread Vagrant Cascadian
Control: affects 943273 u-boot Since u-boot build-depends on skales, this indirectly affects u-boot as well. live well, vagrant signature.asc Description: PGP signature

Bug#943090: marked as done (ganv: Python2 removal in sid/bullseye)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 01:49:16 + with message-id and subject line Bug#943090: fixed in ganv 1.4.2~dfsg0-3 has caused the Debian Bug report #943090, regarding ganv: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt wit

Bug#941231: marked as done (u-boot-imx: mx6cuboxi fails to boot)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 01:35:22 + with message-id and subject line Bug#941231: fixed in u-boot 2020.01~rc5+dfsg-1 has caused the Debian Bug report #941231, regarding u-boot-imx: mx6cuboxi fails to boot to be marked as done. This means that you claim that the problem has been deal

Processed: cloning 943276, severity of -1 is normal, retitle -1 to RM: RoM: RoQA: wmii, python2, orphaned, buggy ...

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 943276 -1 Bug #943276 [src:wmii] wmii: Python2 removal in sid/bullseye Bug 943276 cloned as bug 946929 937695 was blocked by: 943125 937867 936444 936921 937211 937557 937273 943180 938782 937326 936242 943203 936288 936261 938748 938050 93

Processed: cloning 943243, severity of -1 is normal ..., found -1 in , reassign -1 to ftp.debian.org

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 943243 -1 Bug #943243 [src:uligo] uligo: Python2 removal in sid/bullseye Bug 943243 cloned as bug 946928 937695 was blocked by: 936480 936745 938846 938157 936123 936528 938271 936658 938329 936672 938362 938568 936149 936923 937904 945736

Bug#946422: silx: autopkgtest regression: pocl error

2019-12-17 Thread Andreas Beckmann
I've minimized it to =8<= import unittest def suite(): from silx.io import test as test_io from silx.opencl import test as test_ocl test_suite = unittest.TestSuite() test_suite.addTest(test_ocl.suite()) return test_suite if __name__ == '__main__': runner = unitte

Processed: cloning 943213, severity of -1 is normal ..., found -1 in , reassign -1 to ftp.debian.org

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 943213 -1 Bug #943213 [src:shogun] shogun: Python2 removal in sid/bullseye Bug 943213 cloned as bug 946927 937695 was blocked by: 937094 937251 938065 937377 936420 937749 936840 936463 936217 938388 938204 936251 936377 939478 937420 93805

Bug#946926: pysparse: should this package be removed?

2019-12-17 Thread Sandro Tosi
Source: pysparse Severity: serious Hello, it looks like pysparse is no longer fit to remain in debian: * python2 only * no upstream release in 8+ years * python3-sparse exists, as a possible alternative? If i dont hear back within a week with a good reason to keep this package, i will file for i

Bug#938486: marked as done (simulavr: Python2 removal in sid/bullseye)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 01:19:36 + with message-id and subject line Bug#938486: fixed in simulavr 1.0.0+git20160221.e53413b-2 has caused the Debian Bug report #938486, regarding simulavr: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the prob

Processed (with 5 errors): cloning 936358, severity of -1 is normal ..., found -1 in , reassign -1 to ftp.debian.org

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 936358 -1 Bug #936358 [src:cwiid] cwiid: Python2 removal in sid/bullseye Bug #942981 [src:cwiid] cwiid: Python2 removal in sid/bullseye Failed to clone 936358: Bug is marked as being merged with others. Use an existing clone. > severity -1

Bug#937214: openturns: Python2 removal in sid/bullseye

2019-12-17 Thread Sandro Tosi
tests are failing when building the updated package in git, https://github.com/openturns/openturns/issues/1346

Processed: cloning 935449, severity of -1 is normal ..., found -1 in , reassign -1 to ftp.debian.org

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 935449 -1 Bug #935449 [src:thumbor] Build-Depends on removed python-celery Bug 935449 cloned as bug 946925 > severity -1 normal Bug #946925 [src:thumbor] Build-Depends on removed python-celery Severity set to 'normal' from 'serious' > retitl

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

2019-12-17 Thread Debian Bug Tracking System
Your message dated Wed, 18 Dec 2019 00:49:41 + with message-id and subject line Bug#937811: fixed in python-hkdf 0.0.3-4 has caused the Debian Bug report #937811, regarding python-hkdf: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Processed (with 5 errors): cloning 938663, severity of -1 is normal ..., found -1 in , reassign -1 to ftp.debian.org

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 938663 -1 Bug #938663 [src:thumbor] thumbor: Python2 removal in sid/bullseye Bug #935450 [src:thumbor] Please port to Python 3 or remove Failed to clone 938663: Bug is marked as being merged with others. Use an existing clone. > severity -

Processed (with 5 errors): cloning 935450, severity of -1 is normal ..., found -1 in , reassign -1 to ftp.debian.org

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 935450 -1 Bug #935450 [src:thumbor] Please port to Python 3 or remove Bug #938663 [src:thumbor] thumbor: Python2 removal in sid/bullseye Failed to clone 935450: Bug is marked as being merged with others. Use an existing clone. > severity -

Processed: Re: Bug#946920: vlc FTBFS after libfluidsynth update

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libvncserver-dev 0.9.12+dfsg-4 Bug #946920 [src:vlc] vlc FTBFS after libfluidsynth update Bug reassigned from package 'src:vlc' to 'libvncserver-dev'. No longer marked as found in versions vlc/3.0.8-3. Ignoring request to alter fixed versions of bug #9469

Bug#946920: vlc FTBFS after libfluidsynth update

2019-12-17 Thread Sebastian Ramacher
Control: reassign -1 libvncserver-dev 0.9.12+dfsg-4 Control: forcemerge 946865 -1 Control: affects 946865 src:vlc On 2019-12-17 22:28:04, Paul Gevers wrote: > Source: vlc > Version: 3.0.8-3 > Severity: serious > Tags: ftbfs sid bullseye > Justification: ftbfs > > -BEGIN PGP SIGNED MESSAGE

Bug#936247: marked as done (btest: Python2 removal in sid/bullseye)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Dec 2019 18:18:41 -0500 with message-id and subject line Re: btest: Python2 removal in sid/bullseye has caused the Debian Bug report #936247, regarding btest: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Bug#940678: Please import pools by stable device label

2019-12-17 Thread Alberto Berti
> "Petter" == Petter Reinholdtsen writes: Petter> So, should this problem be considered a documentation issue, a local Petter> configuration error, a bug in the startup scripts or something else? Petter> In other words, should it be kept over or closed as fixed? Petter> It i

Processed: tagging 946861, tagging 946863, tagging 946862, tagging 946881, tagging 946858

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 946861 + sid bullseye Bug #946861 [src:buzztrax] buzztrax FTBFS after libfluidsynth update Added tag(s) bullseye and sid. > tags 946863 + sid bullseye Bug #946863 [src:freewheeling] freewheeling FTBFS after libfluidsynth update Added tag(s) s

Bug#946921: Project abandoned

2019-12-17 Thread Moritz Muehlenhoff
Source: rust-spin Severity: serious https://rustsec.org/advisories/RUSTSEC-2019-0031.html was issued to flag that rust-spin development stop. I suppose that means it should not enter bullseye / get removed. Cheers, Moritz

Bug#940678: marked as done (zfsutils-linux: zfs-import-cache fails w. "one or more devices is currently unavailable" on Buster after upgrade from Stretch)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Dec 2019 23:18:58 +0100 with message-id <8736dir3xp@metapensiero.it> and subject line Fixed has caused the Debian Bug report #940678, regarding zfsutils-linux: zfs-import-cache fails w. "one or more devices is currently unavailable" on Buster after upgrade from Stret

Processed: music: diff for NMU version 1.1.16-1.1

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > tags 946541 + patch Bug #946541 [music] music: FTBFS: wrongly use DEB_TARGET_GNU_TYPE in debian/rules Added tag(s) patch. > tags 946541 + pending Bug #946541 [music] music: FTBFS: wrongly use DEB_TARGET_GNU_TYPE in debian/rules Added tag(s) pending. -- 946541: ht

Bug#946541: music: diff for NMU version 1.1.16-1.1

2019-12-17 Thread Boyuan Yang
Control: tags 946541 + patch Control: tags 946541 + pending Dear maintainer, I've prepared an NMU for music (versioned as 1.1.16-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru music-1.1.16/debian/changelog music-1.1.16/debian/chang

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

2019-12-17 Thread Sandro Knauß
Control: severity -1 important Control: reassign -1 libqt5webenginewidgets5 5.12.5+dfsg-3+b1 Control: affects -1 nextcloud-desktop As this is looks like that it is only nvidia specific, I reassign to important. It is properly a bug inside Qt stack so reassign to Qt package. hefee -- On Monta

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

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #946405 [nextcloud-desktop] nextcloud-desktop: Nextcloud desktop client crash when trying to enter login/password Severity set to 'important' from 'grave' > reassign -1 libqt5webenginewidgets5 5.12.5+dfsg-3+b1 Bug #946405 [nextcloud-desktop

Bug#940678: Please import pools by stable device label

2019-12-17 Thread Petter Reinholdtsen
So, should this problem be considered a documentation issue, a local configuration error, a bug in the startup scripts or something else? In other words, should it be kept over or closed as fixed? It is the only open RC issue with zfs on linux. -- Happy hacking Petter Reinholdtsen

Bug#936558: Ping

2019-12-17 Thread Bernhard Schmidt
Pinging this bug to delay testing removal, the fix is in unstable but migration is currently blocked by several RC bugs in libxcrypt.

Bug#936630: gnumed-client: upstream has (unreleased) py3 support

2019-12-17 Thread Moritz Mühlenhoff
On Fri, Aug 30, 2019 at 12:18:16PM +0200, Karsten Hilbert wrote: > Package: gnumed-client > Version: 1.7.6+dfsg-1 > Followup-For: Bug #936630 > > Has been ported to py3 upstream but not released yet because: > > Would like to be able to get bugfix-only 1.7.x py2 packages > into the deb package po

Bug#946920: vlc FTBFS after libfluidsynth update

2019-12-17 Thread Paul Gevers
Source: vlc Version: 3.0.8-3 Severity: serious Tags: ftbfs sid bullseye Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainers, Your package is part of the libfluidsynth2 transition, so I scheduled binNMU's. However, your package FTBFS on all architectures. Please

Processed: tagging 946888, severity of 946888 is serious

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 946888 + ftbfs sid bullseye Bug #946888 {Done: Dmitry Smirnov } [scummvm] scummvm fails to build with the new libfluidsynth Added tag(s) bullseye, sid, and ftbfs. > severity 946888 serious Bug #946888 {Done: Dmitry Smirnov } [scummvm] scummv

Bug#946919: swami FTBFS after libfluidsynth update

2019-12-17 Thread Paul Gevers
Source: swami Version: 2.0.0+svn389-5 Severity: serious Tags: ftbfs sid bullseye Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainers, Your package is part of the libfluidsynth2 transition, so I scheduled binNMU's. However, your package FTBFS on all architectures

Bug#946916: libtritonus-java FTBFS after libfluidsynth update

2019-12-17 Thread Paul Gevers
Source: libtritonus-java Version: 20070428-14+b1 Severity: serious Tags: ftbfs Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainers, Your package is part of the libfluidsynth2 transition, so I scheduled binNMU's. However, your package FTBFS on all architectures.

Bug#946917: muse FTBFS after libfluidsynth update

2019-12-17 Thread Paul Gevers
Source: muse Version: 3.0.2+ds1-1 Severity: serious Tags: ftbfs sid bullseye Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainers, Your package is part of the libfluidsynth2 transition, so I scheduled binNMU's. However, your package FTBFS on all architectures. P

Bug#943943: getfem++ ftbfs on s390x where it built before

2019-12-17 Thread Paul Gevers
On Fri, 1 Nov 2019 12:00:12 +0100 Matthias Klose wrote: > getfem++ ftbfs on s390x where it built before, test failures. > > https://buildd.debian.org/status/package.php?p=getfem%2B%2B > shows that all other 64bit big endian targets also fail. Your package is part of the "scalapack mumps petsc sl

Bug#946915: espresso FTBFS on archs where it build in the past

2019-12-17 Thread Paul Gevers
Source: espresso Version: 6.4.1-1 Severity: serious Tags: ftbfs Justification: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainers, Your package is part of the "scalapack mumps petsc slepc" transition and I want to schedule binNMU's. However, your last upload of the package FT

Bug#907489: Fixing sambamba 0.8.6

2019-12-17 Thread Andreas Tille
On Mon, Dec 16, 2019 at 03:30:43AM +0100, Matthias Klumpp wrote: > > Sambamba is only failing on missing cram_to_bam, so once that's fixed, > it should be good to go as well. So how can this actually be fixed? I noticed that you uploaded 0.7.1-1 which does not build from source. Did you got it

Bug#946906: marked as done (autoremoval looking at Recommends field)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Dec 2019 20:59:49 +0100 with message-id <4a4965b4-bc2b-68e9-f261-fd4ab4cb5...@debian.org> and subject line Re: Bug#946906: autoremoval looking at Recommends field has caused the Debian Bug report #946906, regarding autoremoval looking at Recommends field to be marked as d

Bug#946894: marked as done (runsnake cannot open python3 profiling information)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Dec 2019 19:04:58 + with message-id and subject line Bug#946894: fixed in runsnakerun 2.0.5-1 has caused the Debian Bug report #946894, regarding runsnake cannot open python3 profiling information to be marked as done. This means that you claim that the problem has

Bug#938420: marked as done (runsnakerun: Python2 removal in sid/bullseye)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Dec 2019 19:04:58 + with message-id and subject line Bug#938420: fixed in runsnakerun 2.0.5-1 has caused the Debian Bug report #938420, regarding runsnakerun: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#945920: Chrome bug

2019-12-17 Thread Csaba Toth
References=<915a12b07a1c5c2178dfa530ce16caf89dd17fb8.ca...@gmail.com> On Mon, 16 Dec 2019 17:38:21 +0100 PPHome2 wrote: > "Override software rendering list" > > It helped my machine but didn't really solve the problem, chrome worked > for 1-2 hours with this setup. Resetting it to default has been

Bug#946858: not fixed with ruby-grib 0.4.0-3

2019-12-17 Thread Boyuan Yang
reopen 946858 notfixed 946858 0.4.0-3 thanks On Tue, 17 Dec 2019 03:04:39 + Youhei SASAKI wrote: > ruby-grib (0.4.0-3) unstable; urgency=medium > . >[ Youhei SASAKI ] >* Use eccodes instead of grib_api (Closes: #946858) Unfortunately ruby-grib still depends on libgrib-api-tools, wh

Processed: Re: Bug#946858: not fixed with ruby-grib 0.4.0-3

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 946858 Bug #946858 {Done: Youhei SASAKI } [src:ruby-grib] ruby-grib: Should this package be removed? 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add th

Processed: notfound 941991 in 3.34.2-1

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # sorry, wrong bug > notfound 941991 3.34.2-1 Bug #941991 [gnome-shell] gnome-shell: crashes on startup (Wayland only) with "JS ERROR: TypeError: actor.get_meta_window(...) is null" No longer marked as found in versions gnome-shell/3.34.2-1. > th

Bug#946718: marked as done (gbrowse: autopkgtest regression: Can't call method "features" on an undefined value)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Dec 2019 17:19:18 + with message-id and subject line Bug#946718: fixed in gbrowse 2.56+dfsg-7 has caused the Debian Bug report #946718, regarding gbrowse: autopkgtest regression: Can't call method "features" on an undefined value to be marked as done. This means th

Processed: found 941991 in 3.34.2-1

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 941991 3.34.2-1 Bug #941991 [gnome-shell] gnome-shell: crashes on startup (Wayland only) with "JS ERROR: TypeError: actor.get_meta_window(...) is null" Marked as found in versions gnome-shell/3.34.2-1. > thanks Stopping processing here. Pl

Bug#945413: marked as done (fast-histogram fails it's tests during the build)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Dec 2019 16:34:27 + with message-id and subject line Bug#945413: fixed in fast-histogram 0.7-2 has caused the Debian Bug report #945413, regarding fast-histogram fails it's tests during the build to be marked as done. This means that you claim that the problem has b

Bug#946718: gbrowse: autopkgtest regression: Can't call method "features" on an undefined value

2019-12-17 Thread gregor herrmann
On Tue, 17 Dec 2019 13:49:24 +0100, gregor herrmann wrote: I had a chance to look at the actual package now, which is more helpful than hand-waving advice, and here are my results: > It looks like t/05.deferredrendering.t wants conf/ (in addition to t/ > and sample_data/) in debian/tests/pkg-perl

Bug#946906: autoremoval looking at Recommends field

2019-12-17 Thread Joao Eriberto Mota Filho
Package: release.debian.org Severity: serious >From https://udd.debian.org/cgi-bin/autoremovals.cgi: forensics-all: buggy deps aircrack-ng, flagged for removal in 18 days >From https://tracker.debian.org/pkg/forensics-all: Version 3.12 of forensics-all is marked for autoremoval from testi

Bug#945605: python-neovim: autopkgtest needs update for new version of neovim: Invalid option name: 'listchars'

2019-12-17 Thread Sebastien Bacher
tags 945605 patch user ubuntu-de...@lists.ubuntu.com usertags 945605 origin-ubuntu focal ubuntu-patch thank you The attached patch fixes the issue by backporting 2 commits from upstream diff -Nru python-neovim-0.3.0/debian/changelog python-neovim-0.3.0/debian/changelog --- python-neovim-0.3.0/de

Processed: python-neovim: autopkgtest needs update for new version of neovim: Invalid option name: 'listchars'

2019-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 945605 patch Bug #945605 [src:python-neovim] python-neovim: autopkgtest needs update for new version of neovim: Invalid option name: 'listchars' Added tag(s) patch. > user ubuntu-de...@lists.ubuntu.com Setting user to ubuntu-de...@lists.ubun

Bug#937249: marked as done (patool: Python2 removal in sid/bullseye)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Dec 2019 15:19:24 + with message-id and subject line Bug#937249: fixed in patool 1.12-4 has caused the Debian Bug report #937249, regarding patool: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#945920: Chromium randomly crashes in the latest version.

2019-12-17 Thread Jaap Joris Vens
Dear maintainer, I experience the same random crashes with chromium 79.0.3945.79-1. This is the console output from the moment of crashing: Received signal 11 SEGV_MAPERR #0 0x55d293b7ca99 #1 0x55d293ac60a6 #2 0x55d293b7b293 #3 0x55d293b7ca16 #4 0x7f3ca2883510 #5 0x55d294ee8ee7

Bug#946886: rustc: FTBFS on mips/mipsel with test failures in sync::atomic::Atomic*

2019-12-17 Thread YunQiang Su
Raphaël Hertzog 于2019年12月17日周二 下午5:39写道: > > Source: rustc > Version: 1.39.0+dfsg1-3 > Severity: serious > Justification: FTBFS > > rustc is not migrating to testing (and thus holding up migration of the > latest thunderbird) because it fails to build on mipsel and mips64el with > too many test fa

Processed: julia: FTBFS on arm64 and armhf

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #928131 [src:julia] julia: FTBFS on arm64 and armhf Severity set to 'important' from 'serious' -- 928131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#928131: julia: FTBFS on arm64 and armhf

2019-12-17 Thread Graham Inggs
Control: severity -1 important Downgrading severity since julia was removed on these architectures. (see #946814)

Bug#936992: Upstream here: Please close this bug

2019-12-17 Thread Sam Trenholme
I have gone to the bother of converting bind2csv2.py to be a python2 and python3 polyglot. Keep in mind that this script does not work with a good number of real-world BIND zonefiles: But it will now run in python3 the same way it runs in python2 (converting a strict subset of BIND zone files). Th

Bug#946219: marked as done (python3-nftables non-functional without libnftables-dev)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Dec 2019 13:20:42 + with message-id and subject line Bug#946219: fixed in nftables 0.9.3-2 has caused the Debian Bug report #946219, regarding python3-nftables non-functional without libnftables-dev to be marked as done. This means that you claim that the problem ha

Bug#946718: gbrowse: autopkgtest regression: Can't call method "features" on an undefined value

2019-12-17 Thread gregor herrmann
On Tue, 17 Dec 2019 13:10:54 +0100, Andreas Tille wrote: > Well, now it is > > > https://ci.debian.net/data/autopkgtest/unstable/amd64/g/gbrowse/3667492/log.gz > > It looks pretty the same after implementing your hint So I'm reopening. In my view it looks different. Previously t/01.yeast.t

Bug#946894: Upstream has a python3 version

2019-12-17 Thread Enrico Zini
Hello, I checked and upstream has migrated to python3, both for runsnakerun and for squaremap. Enrico -- GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini signature.asc Description: PGP signature

Bug#946850: last-align ftbfs on non-x86 architectures

2019-12-17 Thread Matthias Klose
did somebody even look at the code? The AVX2 code is never used. Looks like an unguarded include.

Processed: Re: Bug#946718: gbrowse: autopkgtest regression: Can't call method "features" on an undefined value

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #946718 {Done: Andreas Tille } [src:gbrowse] gbrowse: autopkgtest regression: Can't call method "features" on an undefined value 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may ne

Bug#946718: gbrowse: autopkgtest regression: Can't call method "features" on an undefined value

2019-12-17 Thread Andreas Tille
Control: reopen -1 On Tue, Dec 17, 2019 at 08:50:27AM +0100, gregor herrmann wrote: > On Tue, 17 Dec 2019 08:35:40 +0100, Andreas Tille wrote: > > > > https://ci.debian.net/data/autopkgtest/testing/amd64/g/gbrowse/3555081/log.gz > > > > > > t/01.yeast.t .. > > > 1..7 > > > not ok 1 >

Bug#946894: runsnake cannot open python3 profiling information

2019-12-17 Thread Enrico Zini
Package: runsnakerun Version: 2.0.4-2 Severity: grave Hello, runsnake as packaged in Debian cannot read profiling information for python3 programs: $ cat hello.py print("hello") $ python3 -m cProfile -o hello.out ./hello.py hello $ runsnake hello.out The window is all emp

Bug#938554: Bug#877783: spyne_2.13.11a0-0.1_source.changes REJECTED

2019-12-17 Thread Russell Stuart
On Tue, 2019-12-17 at 09:52 +0100, Bastian Germann wrote: > The "unlikely scenario" is reality NOW. Maybe you did not check but > spyne is already gone in testing. > That is what I wanted to draw your attention at. Ahh OK. I didn't realise you considered it being dropped from testing as important.

Processed: Re: [Pkg-rust-maintainers] Bug#946886: rustc: FTBFS on mips/mipsel with test failures in sync::atomic::Atomic*

2019-12-17 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 946874 Bug #946886 [src:rustc] rustc: FTBFS on mips/mipsel with test failures in sync::atomic::Atomic* 946886 was not blocked by any bugs. 946886 was not blocking any bugs. Added blocking bug(s) of 946886: 946874 -- 946886: https://bugs.debian.org/cgi-

Bug#946886: [Pkg-rust-maintainers] Bug#946886: rustc: FTBFS on mips/mipsel with test failures in sync::atomic::Atomic*

2019-12-17 Thread Ximin Luo
Control: block -1 by 946874 see also https://github.com/rust-lang/rust/issues/67167 Raphaël Hertzog: > Source: rustc > Version: 1.39.0+dfsg1-3 > Severity: serious > Justification: FTBFS > > rustc is not migrating to testing (and thus holding up migration of the > latest thunderbird) because it f

Bug#946889: flashplugin-nonfree: Update build-depends and depends on libpango1.0-0

2019-12-17 Thread Simon McVittie
Package: flashplugin-nonfree Version: 1:3.7 Severity: grave Justification: will soon render package unusable This package Depends on the transitional package libpango1.0-0, which has been requested to be removed (#940744). Please replace this dependency with a dependency on the core Pango library

Bug#946887: python3-qtile: Update build-depends and depends on libpango1.0-0

2019-12-17 Thread Simon McVittie
Package: python3-qtile Version: 0.10.7-2 Severity: grave Justification: will soon render package unusable This package Depends and Build-Depends on the transitional package libpango1.0-0, which has been requested to be removed (#940744). Please replace these dependencies with a dependency on the

Bug#946886: rustc: FTBFS on mips/mipsel with test failures in sync::atomic::Atomic*

2019-12-17 Thread Raphaël Hertzog
Source: rustc Version: 1.39.0+dfsg1-3 Severity: serious Justification: FTBFS rustc is not migrating to testing (and thus holding up migration of the latest thunderbird) because it fails to build on mipsel and mips64el with too many test failures: https://buildd.debian.org/status/fetch.php?pkg=rus

Bug#946718: marked as done (gbrowse: autopkgtest regression: Can't call method "features" on an undefined value)

2019-12-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Dec 2019 09:34:21 + with message-id and subject line Bug#946718: fixed in gbrowse 2.56+dfsg-6 has caused the Debian Bug report #946718, regarding gbrowse: autopkgtest regression: Can't call method "features" on an undefined value to be marked as done. This means th

Bug#946856: Breaks d-i at runtime due to dependency loop with libc6-udeb

2019-12-17 Thread Marco d'Itri
The fixed package is currently in NEW. -- ciao, Marco signature.asc Description: PGP signature

Bug#938510: soapysdr: Python2 removal in sid/bullseye

2019-12-17 Thread Christoph Berg
Hi Andreas, I pushed some changes to git. Could you review these? Christoph

  1   2   >