Processed: Merge duplicates

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 980429 src:mkvtoolnix Bug #980429 [src:gcc-10] g++-10: spurious c++17 mode segmentation fault in append_to_statement_list_1 (tree-iterator.c:65) Bug #980629 [src:gcc-10] nheko: FTBFS: internal compiler error Added indication that 980429 a

Bug#980630: libvigraimpex: FTBFS: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb3 in position 138922: invalid start byte

2021-01-30 Thread Andreas Metzler
On 2021-01-20 Lucas Nussbaum wrote: > Source: libvigraimpex > Version: 1.11.1+dfsg-7 > Severity: serious > Justification: FTBFS on amd64 [...] > > File "/usr/lib/python3.9/codecs.py", line 322, in decode > > (result, consumed) = self._buffer_decode(data, self.errors, final) > > UnicodeDecode

Processed: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #980809 {Done: Dirk Eddelbuettel } [src:rmatrix, src:r-cran-glmmtmb] rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x Bug reopened Ignoring request to alter fixed versions of bug #980809 to the same values previously set -- 980809: https://bug

Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x

2021-01-30 Thread Graham Inggs
Control: reopen -1 Hi Dirk Paul's test results showed that the run-unit-test autopkgtest still fails with the same errors ( Error: gradient function must return a numeric vector of length...) as in my original report. The "Package version inconsistency detected" warning is now gone (due to #9809

Processed: fixed 955772 in 2021.01.0+ds.1-1

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # I skipped the test in the build and am hoping it will work with more > network access in the autopkgtests > fixed 955772 2021.01.0+ds.1-1 Bug #955772 [src:dask.distributed] dask.distributed: flaky autopkgtest: timeout reached in test_robust_to

Processed: fixed 954507 in 2021.01.0+ds.1-1

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 954507 2021.01.0+ds.1-1 Bug #954507 [src:dask.distributed] dask.distributed: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.7 3.8" returned exit code 13 The source 'dask.distributed' and version '2021.01.

Processed: tagging 954507

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 954507 + pending Bug #954507 [src:dask.distributed] dask.distributed: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.7 3.8" returned exit code 13 Added tag(s) pending. > thanks Stopping processing here. P

Bug#956427: marked as done (python3-httplib2: please add breaks on python3-wsgi-intercept << 1.9.0)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sun, 31 Jan 2021 04:49:19 + with message-id and subject line Bug#956427: fixed in python-httplib2 0.18.1-2 has caused the Debian Bug report #956427, regarding python3-httplib2: please add breaks on python3-wsgi-intercept << 1.9.0 to be marked as done. This means that you cl

Bug#956427: marked as pending in python-httplib2

2021-01-30 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #956427 in python-httplib2 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/python-team/packages/python-httplib2/-/commit/f600

Processed: Bug#956427 marked as pending in python-httplib2

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #956427 [python3-httplib2] python3-httplib2: please add breaks on python3-wsgi-intercept << 1.9.0 Added tag(s) pending. -- 956427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956427 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#975535: elpy's autopkg tests fail with Python 3.9

2021-01-30 Thread Nicholas D Steeves
Hi Adrian, Thank you for checking in with this bug! Please let me know ASAP if another autoremoval exception will be provided, because if necessary I can do the shady thing of disabling tests to buy time...but I'd really prefer not to! My primary upstream contacts appear to be on holiday and/or

Bug#981428: python3-fido2: Version 0.9 breaks yubikey-manager

2021-01-30 Thread nicoo
Package: python3-fido2 Version: 0.9.0-1 Severity: serious Justification: breaks other packages -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 python-fido2 had minor API-breaking changes, which breaks (at least) yubikey-manager. Let's hold it back from transitionning to testing until upstream cu

Processed: block 950598 with 896460

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 950598 with 896460 Bug #950598 [python3-jupyter-sphinx] python3-jupyter-sphinx: package relies on unavailable `ipywidgets.embed` module 950598 was not blocked by any bugs. 950598 was not blocking any bugs. Added blocking bug(s) of 950598: 8

Bug#971368: marked as done (libfcgi-perl: missing source for FCGI_COMMON_CHECKS)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sun, 31 Jan 2021 00:49:07 + with message-id and subject line Bug#971368: fixed in libfcgi-perl 0.79+ds-2 has caused the Debian Bug report #971368, regarding libfcgi-perl: missing source for FCGI_COMMON_CHECKS to be marked as done. This means that you claim that the problem

Bug#980776: marked as done (namazu2: contents of namazu2-index-tools different when built separately from arch specific binaries)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sun, 31 Jan 2021 00:34:32 + with message-id and subject line Bug#980776: fixed in namazu2 2.0.21-22.2 has caused the Debian Bug report #980776, regarding namazu2: contents of namazu2-index-tools different when built separately from arch specific binaries to be marked as don

Bug#979301: marked as done (namazu2-index-tools: contains namazu.1 manpage after separate arch-indep build)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sun, 31 Jan 2021 00:34:32 + with message-id and subject line Bug#979301: fixed in namazu2 2.0.21-22.2 has caused the Debian Bug report #979301, regarding namazu2-index-tools: contains namazu.1 manpage after separate arch-indep build to be marked as done. This means that yo

Bug#973128: celery-batches: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

2021-01-30 Thread s3v
Dear Maintainer, celery-batches supports Celery 5.0 now [1]. FWIW, packaging new upstream version fixes this issue. Kind Regards [1] https://github.com/clokep/celery-batches/commit/5e3b9d

Processed: Re: paraview: segfaults at startup via libvtkCommonCore-pv5.9.so

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #981378 [meshio-tools] paraview: segfaults at startup via libvtkCommonCore-pv5.9.so Severity set to 'important' from 'grave' > forwarded -1 https://gitlab.kitware.com/paraview/paraview/-/issues/20412 Bug #981378 [meshio-tools] paraview: seg

Bug#981378: paraview: segfaults at startup via libvtkCommonCore-pv5.9.so

2021-01-30 Thread Drew Parsons
Package: meshio-tools Followup-For: Bug #981378 Control: severity -1 important Control: forwarded -1 https://gitlab.kitware.com/paraview/paraview/-/issues/20412 Probably severity grave is overegging it. paraview and meshio-tools won't necessarily be installed at the same time. paraview will work

Processed: missing /dev/stdin etc.

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 975017 > https://github.com/systemd/systemd/commit/6b2229c6c60d0486#commitcomment-42637841 Bug #975017 {Done: =?utf-8?q?Rapha=C3=ABl_Hertzog?= } [udev] udev: missing /dev/stdin etc. Set Bug forwarded-to-address to 'https://github.com/

Processed: Re: paraview: segfaults at startup via libvtkCommonCore-pv5.9.so

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > reassign 981378 meshio-tools 4.3.5-2 Bug #981378 [paraview] paraview: segfaults at startup via libvtkCommonCore-pv5.9.so Bug reassigned from package 'paraview' to 'meshio-tools'. No longer marked as found in versions paraview/5.9.0-1. Ignoring request to alter fixed

Bug#981378: paraview: segfaults at startup via libvtkCommonCore-pv5.9.so

2021-01-30 Thread Drew Parsons
Package: paraview Followup-For: Bug #981378 Control: reassign 981378 meshio-tools 4.3.5-2 Aha, the segfault disappears if meshio-tools is not installed. It must be related to the meshio plugin. I'll transfer this bug report to python-meshio.

Bug#979672: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE-2021-1056)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 22:47:09 + with message-id and subject line Bug#979672: fixed in nvidia-graphics-drivers-legacy-390xx 390.141-2~deb10u1 has caused the Debian Bug report #979672, regarding nvidia-graphics-drivers-legacy-390xx: CVE-2021-1056 to be marked as done. This means

Bug#979670: marked as done (nvidia-graphics-drivers: CVE-2021-1052, CVE-2021-1053, CVE-2021-1056)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 22:47:08 + with message-id and subject line Bug#979670: fixed in nvidia-graphics-drivers 418.181.07-1 has caused the Debian Bug report #979670, regarding nvidia-graphics-drivers: CVE-2021-1052, CVE-2021-1053, CVE-2021-1056 to be marked as done. This means t

Bug#979689: marked as done (pepperflashplugin-nonfree: Installation script fails to download flash from adobe's servers)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 22:02:09 + with message-id and subject line Bug#979689: fixed in pepperflashplugin-nonfree 1.8.8~deb10u1 has caused the Debian Bug report #979689, regarding pepperflashplugin-nonfree: Installation script fails to download flash from adobe's servers to be ma

Bug#980606: marked as done (supertuxkart: FTBFS: gamepad_config.cpp:35:45: error: static assertion failed: non continous name)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 21:51:37 + with message-id and subject line Bug#980606: fixed in supertuxkart 1.2+ds-2 has caused the Debian Bug report #980606, regarding supertuxkart: FTBFS: gamepad_config.cpp:35:45: error: static assertion failed: non continous name to be marked as done

Bug#980240: marked as done (Cyrus-common: /etc/cron.daily/cyrus-imapd is not working)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 21:47:08 + with message-id and subject line Bug#980240: fixed in cyrus-imapd 3.0.8-6+deb10u5 has caused the Debian Bug report #980240, regarding Cyrus-common: /etc/cron.daily/cyrus-imapd is not working to be marked as done. This means that you claim that th

Bug#970066: marked as done (atftp: CVE-2020-6097)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 21:47:07 + with message-id and subject line Bug#970066: fixed in atftp 0.7.git20120829-3.2~deb10u1 has caused the Debian Bug report #970066, regarding atftp: CVE-2020-6097 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#981422: xdg-utils: autopkgtest failure: make: dh: No such file or directory

2021-01-30 Thread Nicholas Guriev
Hello! On Sat, 2021-01-30 at 21:54 +0100, Paul Gevers wrote: > You recently added an autopkgtest to your package xdg-utils, great. > However, it fails. Currently this failure is blocking the migration to > testing [1]. Can you please investigate the situation and fix it? There are several ways to

Bug#960786: phpize7.4 also hardcodes incorrect absolute path to sed if built on /usr-merged system

2021-01-30 Thread Paul Gevers
Hi, On Sat, 16 May 2020 16:36:18 + (UTC) Thorsten Glaser wrote: > Setting ac_cv_path_SED=/bin/sed in the environment > of the configure call might even be easier and less invasive. Can we please have a fix for this bug? It was discussed during the IRC meeting of the Release Team and we want

Bug#981422: xdg-utils: autopkgtest failure: make: dh: No such file or directory

2021-01-30 Thread Paul Gevers
Source: xdg-utils Version: 1.1.3-4 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package xdg-utils, great. However, it fails. Currently this failure is blocking the m

Bug#934843: parsedatetime: FTBFS in stretch

2021-01-30 Thread Bernd Zeimetz
Hi, On 1/30/21 12:54 AM, Santiago Vila wrote: > > I have not tested myself, but if this were my package I would try to > built it in 2019-08 (using "libfaketime" or something similar), as the > failure in the test suite seems to depend on the date on which it's > built. just done that with seve

Processed: Re: Bug#980637: git-buildpackage: FTBFS: AttributeError: 'str' object has no attribute 'decode'

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #980637 [src:git-buildpackage] git-buildpackage: FTBFS: AttributeError: 'str' object has no attribute 'decode' Added tag(s) patch. -- 980637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980637 Debian Bug Tracking System Contact ow...@bugs

Bug#980637: git-buildpackage: FTBFS: AttributeError: 'str' object has no attribute 'decode'

2021-01-30 Thread Jochen Sprickerhof
Control: tags -1 + patch Hi Guido, * Guido Günther [2021-01-27 12:08]: Hi, On Wed, Jan 20, 2021 at 09:37:56PM +0100, Lucas Nussbaum wrote: Source: git-buildpackage Version: 0.9.21 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye

Bug#718272: why was bitcoin package removed from testing?

2021-01-30 Thread Jonas Smedegaard
Quoting Paul Gevers (2021-01-30 19:49:31) > On 30-01-2021 11:50, Jonas Smedegaard wrote: > > If the release team consider bitcoin unacceptable for Debian stable, > > then please elaborate why. > > We consider it unacceptable for Debian bullseye because the security > team doesn't want to support

Bug#979983: marked as done (qcelemental downloads from the internet during the build)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 19:49:43 + with message-id and subject line Bug#979983: fixed in qcelemental 0.17.0+dfsg-3 has caused the Debian Bug report #979983, regarding qcelemental downloads from the internet during the build to be marked as done. This means that you claim that the

Processed: Re: Bug#981394: sane-airscan: Dependency missing?

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 981394 Dependency missing? Bug #981394 [sane-airscan] sane-airscan: zzz Changed Bug title to 'Dependency missing?' from 'sane-airscan: zzz'. > thanks Stopping processing here. Please contact me if you need assistance. -- 981394: https://

Processed: Bug#980703 marked as pending in $i

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #980703 [src:qcelemental] qcelemental: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 Added tag(s) pending. -- 980703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980703 Debian Bug

Processed: Bug#979983 marked as pending in $i

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #979983 [src:qcelemental] qcelemental downloads from the internet during the build Added tag(s) pending. -- 979983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#980703: marked as pending in $i

2021-01-30 Thread Michael Banck
Control: tag -1 pending Hello, Bug #980703 in $i 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/debichem-team/qcelemental/-/commit/fd056b87e9b09317d068e1b39954

Bug#979983: marked as pending in $i

2021-01-30 Thread Michael Banck
Control: tag -1 pending Hello, Bug #979983 in $i 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/debichem-team/qcelemental/-/commit/fd056b87e9b09317d068e1b39954

Bug#718272: why was bitcoin package removed from testing?

2021-01-30 Thread Paul Gevers
Hi Jonas, On 30-01-2021 11:50, Jonas Smedegaard wrote: > If the release team consider bitcoin unacceptable for Debian stable, > then please elaborate why. We consider it unacceptable for Debian bullseye because the security team doesn't want to support it. Paul OpenPGP_signature Description:

Bug#977779: geary FTBFS on mipsel: test suite failure

2021-01-30 Thread Alberto Garcia
On Fri, Jan 29, 2021 at 02:11:00PM +0200, Adrian Bunk wrote: > > But this a bug in the CPU, right? Do I understand correctly that the > > package can fail depending on what CPU it is run on regardless of how > > it was built? > > > > I'm trying to understand what we can do in WebKit in order to fi

Bug#981404: compressed file is world readable, while zstd is running

2021-01-30 Thread Harald Dunkel
Package: zstd Version: 1.3.8+dfsg-3 Severity: critical Compressing a large file with restricted access permissions a new, world readable file is created, revealing the contents of the uncompressed file. Sample: # whoami root # zstd -q -13 -T8 sample.dmp &> zstd.log & : : # ls -al total 385983012

Bug#975530: marked as done (pymol's autopkg tests fail with Python 3.9)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 17:34:21 +0100 with message-id <60158a8e.1c69fb81.cc8c5.8...@mx.google.com> and subject line Re: [Debichem-devel] Bug#975530: pymol's autopkg tests fail with Python 3.9 has caused the Debian Bug report #975530, regarding pymol's autopkg tests fail with Python 3.

Bug#975530: pymol's autopkg tests fail with Python 3.9

2021-01-30 Thread s3v
Dear Maintainer, this issue was fixed upstream, please see https://github.com/schrodinger/pymol-open-source/commit/deabfe Kind Regards

Processed: Bug#980606 marked as pending in supertuxkart

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #980606 [src:supertuxkart] supertuxkart: FTBFS: gamepad_config.cpp:35:45: error: static assertion failed: non continous name Added tag(s) pending. -- 980606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980606 Debian Bug Tracking System Con

Bug#980606: marked as pending in supertuxkart

2021-01-30 Thread Reiner Herrmann
Control: tag -1 pending Hello, Bug #980606 in supertuxkart 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/games-team/supertuxkart/-/commit/bcea0a1cd9820c5f2aa4

Bug#981398: sa-exim: not installable with bullseye's exim4

2021-01-30 Thread Adam Borowski
Package: sa-exim Version: 4.2.1-19 Severity: grave Justification: renders package uninstallable Hi! Current version of sa-exim depends on exim4-localscanapi-3.1, and indeed it was compiled against that version. This makes it non-coinstallable with fully-featured (-heavy) build with exim; it is cu

Bug#951770: marked as done (libpam-radius-auth: do not release in bullseye without active maintainer)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 15:33:36 + with message-id and subject line Bug#951770: fixed in libpam-radius-auth 1.4.0-4 has caused the Debian Bug report #951770, regarding libpam-radius-auth: do not release in bullseye without active maintainer to be marked as done. This means that y

Bug#980809: marked as done (rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 08:57:52 -0600 with message-id <24597.29680.445478.248...@rob.eddelbuettel.com> and subject line Re: Bug#980809: log on s390x has caused the Debian Bug report #980809, regarding rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x to be marked as done. This me

Bug#981393: ltsp: Unable to generate image

2021-01-30 Thread Alkis Georgopoulos
Hello, if at all possible, please use the following bug trackers for LTSP, for any distribution or version: For bugs: https://github.com/ltsp/ltsp/issues For discussions: https://github.com/ltsp/ltsp/discussions For example, I assume that the problem in this case is that you manually edited

Bug#981394: sane-airscan: zzz

2021-01-30 Thread Brian Potkin
Package: sane-airscan Version: 0.99.23-1 Severity: grave Tags: patch On a system without a SANE frontend or libsane1, sane-airscan is effectively useless. I reckon there should be a Depends: on at least sane-utils. I hope the severity level is not over the top. Regards, Brian.

Bug#981393: ltsp: Unable to generate image

2021-01-30 Thread peto
Package: ltsp Version: 21.01-1 Severity: grave Justification: renders package unusable Dear Maintainer, I have a problem with LTSP 21 that renders it unusable with Bullseye. I have been successfully using old LTSP5 with Buster before. * What led up to the situation? Installing packages acco

Processed: paraview affects python3-meshio

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 981378 python3-meshio Bug #981378 [paraview] paraview: segfaults at startup via libvtkCommonCore-pv5.9.so Added indication that 981378 affects python3-meshio > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: Unlinking bug with MR

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > notforwarded -1 Bug #971946 {Done: Steve McIntyre <93...@debian.org>} [libdebian-installer] libdebian-installer: READSIZE size insufficient for cdebootstrap to build sid/unstable from buster/stable environment Unset Bug forwarded-to-address -- 971946: https://bug

Bug#971946: Unlinking bug with MR

2021-01-30 Thread Diederik de Haas
Control: notforwarded -1

Processed: severity of 981390 is serious

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 981390 serious Bug #981390 [kylin-video] kylin-video: drop (build-)dependency on crystalhd, which will not be in bullseye Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance

Processed: found 981390 in 2.1.1.1-1

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 981390 2.1.1.1-1 Bug #981390 [kylin-video] kylin-video: drop (build-)dependency on crystalhd, which will not be in bullseye Marked as found in versions kylin-video/2.1.1.1-1. > thanks Stopping processing here. Please contact me if you need

Processed: kylin-video: drop (build-)dependency on crystalhd, which will not be in bullseye

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #934242 [src:crystalhd] crystalhd: unusable without (available and properly working) firmware Bug 934242 cloned as bug 981390 > reassign -2 kylin-video Bug #981390 [src:crystalhd] crystalhd: unusable without (available and properly working) firmware

Bug#934242: kylin-video: drop (build-)dependency on crystalhd, which will not be in bullseye

2021-01-30 Thread Ivo De Decker
Control: clone -1 -2 Control: reassign -2 kylin-video Control: retitle -2 kylin-video: drop (build-)dependency on crystalhd, which will not be in bullseye Hi, On Tue, Dec 22, 2020 at 09:29:03PM +0100, Paul Gevers wrote: > On 21-12-2020 23:32, Jonas Smedegaard wrote: > > Yes, there are still pack

Bug#971681: r-cran-openmx regression on arm, will not migrate to testing due to failing autopkgtests

2021-01-30 Thread Joshua N Pritikin
On Sat, Jan 30, 2021 at 06:32:48PM +0530, Nilesh Patra wrote: > Many thanks for fixes, > > The freeze has started and soft freeze time is near as well.(2 weeks > from now) OpenMx has removals of a bunch of packages from testing. > > Hence, please consider doing a new upstream release if it looks

Bug#981370: marked as done (libgcrypt20: CVE-2021-3345: Exploitable heap-based buffer overflow (Only relevant for Debian/experimental))

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 13:34:07 + with message-id and subject line Bug#981336: fixed in libgcrypt20 1.9.1-1 has caused the Debian Bug report #981336, regarding libgcrypt20: CVE-2021-3345: Exploitable heap-based buffer overflow (Only relevant for Debian/experimental) to be marked

Bug#981336: marked as done (libgcrypt20: CVE-2021-3345: Exploitable heap-based buffer overflow (Only relevant for Debian/experimental))

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 13:34:07 + with message-id and subject line Bug#981336: fixed in libgcrypt20 1.9.1-1 has caused the Debian Bug report #981336, regarding libgcrypt20: CVE-2021-3345: Exploitable heap-based buffer overflow (Only relevant for Debian/experimental) to be marked

Bug#971681: r-cran-openmx regression on arm, will not migrate to testing due to failing autopkgtests

2021-01-30 Thread Nilesh Patra
Hi Joshua, Many thanks for fixes, The freeze has started and soft freeze time is near as well.(2 weeks from now) OpenMx has removals of a bunch of packages from testing. Hence, please consider doing a new upstream release if it looks okay to you. Thanks and regards, Nilesh signature.asc Des

Bug#981286: marked as done (node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv')

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 12:03:43 + with message-id and subject line Bug#981286: fixed in node-jest 26.6.3+repack+~cs64.44.39-2 has caused the Debian Bug report #981286, regarding node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv' to be marked as done

Processed: Bug#981286 marked as pending in node-jest

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #981286 [jest] node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv' Added tag(s) pending. -- 981286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981286 Debian Bug Tracking System Contact ow...@bugs.debian.org w

Bug#981286: marked as pending in node-jest

2021-01-30 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #981286 in node-jest 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/js-team/node-jest/-/commit/7296ac45a6aa1cdbc8067219f42d7

Processed: affects 981286

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 981286 node-mimic-response Bug #981286 [jest] node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv' Added indication that 981286 affects node-mimic-response > thanks Stopping processing here. Please contact me

Processed: Re: [Pkg-javascript-devel] Bug#981286: Bug#981286: node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv'

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #981286 {Done: Xavier Guimard } [src:node-mimic-response] node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv' 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, an

Bug#981286: [Pkg-javascript-devel] Bug#981286: Bug#981286: node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv'

2021-01-30 Thread Xavier
Control: reopen -1 Control: reassign -1 jest Le 30/01/2021 à 10:30, Xavier a écrit : > Le 30/01/2021 à 10:06, Xavier a écrit : >> Le 30/01/2021 à 10:02, Xavier a écrit : >>> Control: tags -1 + moreinfo >>> >>> Hi, >>> >>> debci autopkgtest still reports "Cannot find module 'iconv'" with arm64, >>>

Bug#718272: why was bitcoin package removed from testing?

2021-01-30 Thread Jonas Smedegaard
The bitcoin package was removed from testing some hours ago - https://tracker.debian.org/news/1225530/bitcoin-removed-from-testing/ references bug#718272 but that bug is closed. If the removal accidental (e.g. cause by bug closure flip-flop, then please consider correcting that by fast-trackign

Bug#981378: paraview: segfaults at startup via libvtkCommonCore-pv5.9.so

2021-01-30 Thread Drew Parsons
Package: paraview Version: 5.9.0-1 Severity: grave Justification: renders package unusable Thanks for packaging the new paraview release. The latest version of python-meshio should be able to run with it. paraview is segfaulting (SIGBABRT) at start up though, $ paraview Warning: Ignoring XDG_SE

Processed: bug 981370 is forwarded to https://dev.gnupg.org/T5275, tagging 981370

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 981370 https://dev.gnupg.org/T5275 Bug #981370 [libgcrypt20] libgcrypt20: CVE-2021-3345: Exploitable heap-based buffer overflow (Only relevant for Debian/experimental) Bug #981336 [libgcrypt20] libgcrypt20: CVE-2021-3345: Exploitable he

Processed: Re: Bug#981370: CVE - critical security bug - Exploitable overflow in Libgcrypt 1.9.0

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 981336 981370 Bug #981336 [libgcrypt20] libgcrypt20: Version 1.9.0 (Debian experimental) know to be broken Bug #981370 [libgcrypt20] libgcrypt20: CVE-2021-3345: Exploitable heap-based buffer overflow Unset Bug forwarded-to-address Severity set to 'seriou

Bug#981286: marked as done (node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv')

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 09:48:50 + with message-id and subject line Bug#981286: fixed in node-mimic-response 3.1.0-4 has caused the Debian Bug report #981286, regarding node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv' to be marked as done. This me

Bug#981286: [Pkg-javascript-devel] Bug#981286: node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv'

2021-01-30 Thread Xavier
Le 30/01/2021 à 10:06, Xavier a écrit : > Le 30/01/2021 à 10:02, Xavier a écrit : >> Control: tags -1 + moreinfo >> >> Hi, >> >> debci autopkgtest still reports "Cannot find module 'iconv'" with arm64, >> armhf i386 and ppc64el but I'm unable to reproduce this in a porterbox >> (and node-iconv is l

Processed: Bug#981286 marked as pending in node-mimic-response

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #981286 [src:node-mimic-response] node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv' Added tag(s) pending. -- 981286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981286 Debian Bug Tracking System Contact ow..

Bug#981286: marked as pending in node-mimic-response

2021-01-30 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #981286 in node-mimic-response 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/js-team/node-mimic-response/-/commit/e593e77cc

Bug#972598: marked as done (pgcli: Broken dependencies render package unusable)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 09:33:28 + with message-id and subject line Bug#972598: fixed in pgcli 3.1.0-0.1 has caused the Debian Bug report #972598, regarding pgcli: Broken dependencies render package unusable to be marked as done. This means that you claim that the problem has been

Bug#981286: node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv'

2021-01-30 Thread Xavier
Le 30/01/2021 à 10:02, Xavier a écrit : > Control: tags -1 + moreinfo > > Hi, > > debci autopkgtest still reports "Cannot find module 'iconv'" with arm64, > armhf i386 and ppc64el but I'm unable to reproduce this in a porterbox > (and node-iconv is listed in test dependencies). Could someone take

Processed: Re: node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv'

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #981286 [src:node-mimic-response] node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv' Added tag(s) moreinfo. -- 981286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981286 Debian Bug Tracking System Contact

Bug#981286: node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv'

2021-01-30 Thread Xavier
Control: tags -1 + moreinfo Hi, debci autopkgtest still reports "Cannot find module 'iconv'" with arm64, armhf i386 and ppc64el but I'm unable to reproduce this in a porterbox (and node-iconv is listed in test dependencies). Could someone take a look ?

Processed: reopening 981286

2021-01-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 981286 Bug #981286 {Done: Xavier Guimard } [src:node-mimic-response] node-mimic-response: autopkgtest regression on !amd64: Cannot find module 'iconv' 'reopen' may be inappropriate when a bug has been closed with a version; all fixed vers

Bug#933928: marked as pending in macsyfinder

2021-01-30 Thread Michael R. Crusoe
Control: tag -1 pending Hello, Bug #933928 in macsyfinder 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/med-team/macsyfinder/-/commit/421623a15e365930a72f4c87

Processed: Bug#933928 marked as pending in macsyfinder

2021-01-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #933928 [src:macsyfinder] macsyfinder: Port to Python3 needed Added tag(s) pending. -- 933928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#970501: marked as done (dojo FTBFS: Cannot set property "dojo" of null)

2021-01-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jan 2021 08:17:41 + with message-id and subject line Bug#970501: fixed in dojo 1.15.4+dfsg1-1 has caused the Debian Bug report #970501, regarding dojo FTBFS: Cannot set property "dojo" of null to be marked as done. This means that you claim that the problem has been

Bug#980202: FTBFS: gscan2pdf tests fail

2021-01-30 Thread Jeff
On 23/01/2021 17:53, Cristy wrote: Thanks for the problem report. We can reproduce it and will have a patch to fix it in the GIT main branch @ https://github.com/ImageMagick/ImageMagick6 later today. The patch will be available in the beta releases of ImageMagick @ https://imagemagick.org/down