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

Your message dated Sun, 06 Sep 2020 06:03:21 + with message-id and subject line Bug#937665: fixed in python-coverage 5.1+dfsg.1-2 has caused the Debian Bug report #937665, regarding python-coverage: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the probl

Bug#969622: gnome-shell-extension-log-out-button: fails to load: TypeError: System._createActionButton is not a function

Package: gnome-shell-extension-log-out-button Version: 1.0.8-1 Severity: serious The "Log Out Button" GNOME shell extension fails to load with GNOME 3.36. When I click the "Show Errors" link in the GNOME shell Looking Glass (type lg into the run dialog, click on Extensions) I see this: TypeError:

Bug#969623: gnome-shell-extension-show-ip: load fails: ReferenceError: None is not defined

Package: gnome-shell-extension-show-ip Version: 8-6 Severity: serious I noticed that this extension now fails to load with this error: ReferenceError: None is not defined -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, '

Processed (with 1 error): Re: gnome-shell-extension-weather: fails to load: TypeError: this.actor.reparent is not a function

Processing control commands: > retitle -1 gnome-shell-extension-weather: fails to load: TypeError: > this.actor.reparent is not a function Bug #969273 [gnome-shell-extension-weather] gnome-shell-extension-weather: Error loading the extension. Changed Bug title to 'gnome-shell-extension-weather:

Bug#969621: propellor: Propellor fails to find location of built propellor binary

Package: propellor Version: 5.10.2-2 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, While trying to test propellor on a Debian Testing system, I discovered my changes were not taking effect. Eventually I discovered that the haskell build system was writing

Processed: bug 943032 is forwarded to https://github.com/mnauw/git-remote-hg/issues/34

Processing commands for cont...@bugs.debian.org: > forwarded 943032 https://github.com/mnauw/git-remote-hg/issues/34 Bug #943032 [src:git-remote-hg] git-remote-hg: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'https://github.com/mnauw/git-remote-hg/issues/34'. > thanks Stopping

Bug#969608: ncbi-blast+: regressions on armhf

Steve Langasek writes: > I have reproduced the ncbi-blast+ autopkgtest failure on abel.debian.org, > confirming this is not a problem specific to the Debian build. Thanks for the report. I have a solid idea for a patch that should help here (and on 32-bit architectures in general), and will tes

Bug#969559: Info received (Bug#969559: curl segmentation fauls on any https URL)

I have checked my pkcs11 device and it is functioning properly, but curl still crashes. Fortunately I can just use 'wget' until this is fixed. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its

Bug#969616: rust-tui builds 5 uninstallable packages

Source: rust-tui Version: 0.8.0-2 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy The rust-tui source package builds 5 different binary packages all of which has unsatisfiable dependencies, as reported by britney: librust-tui+crossterm-dev/amd64 has unsatisfiabl

Bug#969103: [Pkg-emacsen-addons] Bug#969103: seq.el: requesting an update to the version in GNU ELPA

Hello, On Fri 04 Sep 2020 at 11:57AM GMT, Stefan Kangas wrote: > Lev Lamberov writes: > >> I've applied your patch to seq from the ELPA git repository and tested >> it both in GNU Emacs 24 and GNU Emacs 25 from the Debian archive >> (stretch release). Here is the output: > > Thanks for testing!

Processed: Re: Bug#937665: Waiting for Python 2-depending reverse dependencies

Processing control commands: > unblock -1 by 933750 Bug #937665 [src:python-coverage] python-coverage: Python2 removal in sid/bullseye 937665 was blocked by: 938009 938407 936340 937609 937159 938300 938011 937989 936335 937157 936745 938244 943014 936296 938278 936473 937516 938676 937580 9376

Bug#937665: Waiting for Python 2-depending reverse dependencies

Control: unblock -1 by 933750 Control: tags -1 + pending Control: outlook -1 0 We will ignore the remaining reverse-dependencies. This release will break those reverse-dependencies, but they have already lost other Python dependencies which drop Python 2 support. On 17-Aug-2020, Jann Haber wrote:

Bug#969615: rust-unicode-script has unsatisfiable dependency on non-existent rust-harfbuzz-sys

Source: rust-unicode-script Version: 0.3.0-2 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy The librust-unicode-script+harfbuzz-dev package is uninstallable because it depends on librust-harfbuzz-sy-0.3+default-dev, which does not exist anywhere in Debian, inclu

Bug#969103: [Pkg-emacsen-addons] Bug#969103: elpa-flycheck: causes leak in GNU Emacs 27.1

Hello Lev, Thanks for the report and testing. New version uploaded. -- Sean Whitton signature.asc Description: PGP signature

Processed: closing 966835

Processing commands for cont...@bugs.debian.org: > close 966835 0.19.1-1 Bug #966835 [src:haskell-shake] haskell-shake needs source upload for new haddock interface The source 'haskell-shake' and version '0.19.1-1' do not appear to match any binary packages Marked as fixed in versions haskell-sh

Bug#969609: rust-zstd: unbuildable, uninstallable, depends on non-existent rust-zstd-safe

Source: rust-zstd Version: 0.5.1-1 Severity: grave The rust-zstd package has both a dependency and a build-dependency on librust-zstd-safe-2.0.3+experimental-dev, which does not exist anywhere in Debian. Presumably it would be built by a rust-zstd-safe package, but no such package exists, includi

Bug#957685: marked as done (pipewire: ftbfs with GCC-10)

Your message dated Sat, 05 Sep 2020 22:00:13 + with message-id and subject line Bug#957685: fixed in pipewire 0.3.10-1 has caused the Debian Bug report #957685, regarding pipewire: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#969608: ncbi-blast+: regressions on armhf

Source: ncbi-blast+ Version: 2.10.0-1 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy Dear maintainers, It appears that ncbi-blast+ 2.10 has regressed on armhf, and is significantly broken. In Ubuntu, all of the autopkgtests triggered by ncbi-blast+ have regres

Processed: fixed 959555 in 5.1.0-1

Processing commands for cont...@bugs.debian.org: > fixed 959555 5.1.0-1 Bug #959555 [src:zope.interface] zope.interface: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py) Marked as fixed in versions zope.interface/5.1.0-1.

Processed: closing 959555

Processing commands for cont...@bugs.debian.org: > close 959555 Bug #959555 [src:zope.interface] zope.interface: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py) Marked Bug as done > thanks Stopping processing here. Pleas

Bug#961584: lxc-stop fails with exit code 1

Le mercredi 03 juin 2020 à 10:57:13+0200, Inaki Malerba a écrit : > El 2/6/20 a las 20:07, Pierre-Elliott Bécue escribió: > > Could you remove the --quiet bit to see if lxc-stop gives us a bit more > > intel? > > > > If possible, have your testbed call lxc-stop --kill --logpriority trace > > --log

Bug#964973: mesa-opencl-icd: Applications using OpenCL crash with : CommandLine Error: Option 'polly' registered more than once!

Package: libreoffice Version: 1:7.0.1-1 Followup-For: Bug #964973 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello! I just got a hit by this bugs while trying to start LibreOffice: #954849 does not start: LLVM ERROR: inconsistency in registered CommandLine options #964973 mesa-opencl-ic

Processed: src:minimap2: fails to migrate to testing for too long: FTBFS on multiple arches

Processing control commands: > close -1 2.17+dfsg-11 Bug #969596 [src:minimap2] src:minimap2: fails to migrate to testing for too long: FTBFS on multiple arches Marked as fixed in versions minimap2/2.17+dfsg-11. Bug #969596 [src:minimap2] src:minimap2: fails to migrate to testing for too long: F

Bug#969596: src:minimap2: fails to migrate to testing for too long: FTBFS on multiple arches

Source: minimap2 Version: 2.17+dfsg-9 Severity: serious Control: close -1 2.17+dfsg-11 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing

Bug#969534: marked as done (ffc autopkg test failure)

Your message dated Sat, 05 Sep 2020 16:50:51 + with message-id and subject line Bug#969534: fixed in ffc 2019.2.0~git20200123.6b621eb-3 has caused the Debian Bug report #969534, regarding ffc autopkg test failure to be marked as done. This means that you claim that the problem has been dealt

Bug#969548: marked as done (setuptools breaks ffc autopkgtest: No module named 'ffc_factory')

Your message dated Sat, 05 Sep 2020 16:50:51 + with message-id and subject line Bug#969534: fixed in ffc 2019.2.0~git20200123.6b621eb-3 has caused the Debian Bug report #969534, regarding setuptools breaks ffc autopkgtest: No module named 'ffc_factory' to be marked as done. This means that yo

Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25

Source: sane-backends Version: 1.0.27-3.2 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) sane-backends FTBFS on armel and armhf: | @@ -7204,7 +7151,7 @@ | sanei_pp_outb_addr@Base 1.0.25 | sanei_pp_outb_ctrl@Base 1.0.25

Bug#966353: FTBFS: guile segfaults when run to collect docs

On Mon, Jul 27, 2020 at 09:09:45PM +1000, Stuart Prescott wrote: >... > guile segfaults as soon as it is started (with or without docs on stdin). > The backtrace is as follows in case the problem jumps out. > > /build/lilypond-jv5Dao/lilypond-2.20.0/guile18/libguile/.libs$ > LD_LIBRARY_PATH=. gdb

Bug#969570: marked as done (ulfius: FTBFS on s390x)

Your message dated Sat, 5 Sep 2020 17:54:00 +0200 with message-id <0abc14f9-6e93-17c6-cce0-17f0656d4...@debian.org> and subject line Re: Bug#969570: ulfius: FTBFS on s390x has caused the Debian Bug report #969570, regarding ulfius: FTBFS on s390x to be marked as done. This means that you claim tha

Bug#969559: curl segmentation fauls on any https URL

On Sat, Sep 5, 2020 at 03:50:20PM +0200, Bernhard Übelacker wrote: > Dear Maintainer, > I tried to reproduce this fault, but did not get a segfault. > > However, I think the backtrace points to these lines: > > (gdb) bt > #0 0x7769dbce in int_ctx_new () at ../crypto/evp/pmeth_li

Bug#969260: openfjx: FTBFS (gstreamer)

Hi Chris! On Sat, Sep 05, 2020 at 05:43:17AM +, Chris Knadle wrote: > Chris Knadle: > > For what it's worth, I used a clean cowbuilder sid chroot that was fully > > upgraded to build openjfx 11.0.7+0-4 and the package built fine. The build > > log > > is about 808kB -- I'll send it to the bug

Bug#957813: marked as pending in slimevolley

Control: tag -1 pending Hello, Bug #957813 in slimevolley 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/slimevolley/-/commit/b01d76ea37e5a14a59bb41

Processed: Bug#957813 marked as pending in slimevolley

Processing control commands: > tag -1 pending Bug #957813 [src:slimevolley] slimevolley: ftbfs with GCC-10 Added tag(s) pending. -- 957813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#969534: ffc autopkg test failure

Source: ffc Followup-For: Bug #969534 Control: forwarded -1 https://github.com/pypa/setuptools/issues/2295 Looks like setuptools is now deprecated upstream. "python3 setup.py install --prefix " no longer installs an importable module (site.py is no longer installed) setuptools upstream recommend

Processed: Re: ffc autopkg test failure

Processing control commands: > forwarded -1 https://github.com/pypa/setuptools/issues/2295 Bug #969534 [src:ffc] ffc autopkg test failure Bug #969548 [src:ffc] setuptools breaks ffc autopkgtest: No module named 'ffc_factory' Set Bug forwarded-to-address to 'https://github.com/pypa/setuptools/iss

Bug#967198: marked as done (pecomato: Unversioned Python removal in sid/bullseye)

Your message dated Sat, 05 Sep 2020 15:21:39 + with message-id and subject line Bug#967198: fixed in pecomato 0.0.15-11 has caused the Debian Bug report #967198, regarding pecomato: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#969569: marked as done (Gnome-builder: build-depends on package that is not in testing.)

Your message dated Sat, 05 Sep 2020 15:19:13 + with message-id and subject line Bug#969569: fixed in gnome-builder 3.36.1-1 has caused the Debian Bug report #969569, regarding Gnome-builder: build-depends on package that is not in testing. to be marked as done. This means that you claim that

Bug#957271: gfpoken: ftbfs with GCC-10

Hi, the GCC 10 build error is easily fixed with the attached patch. But the build also fails while generating artwork via a Gimp script (art/mktiles): > Starting extension: 'extension-script-fu' > No batch interpreter specified, using the default 'plug-in-script-fu-eval'. > Welcome to TinyScheme

Bug#969579: marked as done (ruby-oj: ftbfs on armel, armhf and mipsel - Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "1

Your message dated Sat, 05 Sep 2020 14:53:20 + with message-id and subject line Bug#969579: fixed in ruby-oj 3.10.13-2 has caused the Debian Bug report #969579, regarding ruby-oj: ftbfs on armel, armhf and mipsel - Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Exp

Processed: Re: [Pkg-sass-devel] Bug#953415: Processed: gitlab upstream forwarded this to libsass upstream

Processing control commands: > retitle -1 libsass: performance regression from v3.5.2 to v3.6.4 Bug #953415 [libsass] regression in libsass Bug #956205 [libsass] regression in libsass Changed Bug title to 'libsass: performance regression from v3.5.2 to v3.6.4' from 'regression in libsass'. Change

Bug#953415: [Pkg-sass-devel] Bug#953415: Processed: gitlab upstream forwarded this to libsass upstream

Control: retitle -1 libsass: performance regression from v3.5.2 to v3.6.4 Control: severity -1 important Quoting Pirate Praveen (2020-09-05 10:13:38) > Control: forwarded -1 https://github.com/sass/libsass/issues/3125 > Control: retitle -1 regression in libsass > Control: severity -1 serious >

Processed: Bug#969569 marked as pending in gnome-builder

Processing control commands: > tag -1 pending Bug #969569 [gnome-builder] Gnome-builder: build-depends on package that is not in testing. Added tag(s) pending. -- 969569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969569 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Bug#969559: curl segmentation fauls on any https URL

Dear Maintainer, I tried to reproduce this fault, but did not get a segfault. However, I think the backtrace points to these lines: (gdb) bt #0 0x7769dbce in int_ctx_new () at ../crypto/evp/pmeth_lib.c:160 #1 0x7769dcfa in EVP_PKEY_CTX_new () at ../crypto/evp/pmeth_

Bug#969569: marked as pending in gnome-builder

Control: tag -1 pending Hello, Bug #969569 in gnome-builder 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/gnome-team/gnome-builder/-/commit/55ae5219639a74edaf

Bug#969315: marked as done (pytsk FTBFS with sleuthkit 4.9.0)

Your message dated Sat, 05 Sep 2020 13:18:34 + with message-id and subject line Bug#969315: fixed in pytsk 20200117-2 has caused the Debian Bug report #969315, regarding pytsk FTBFS with sleuthkit 4.9.0 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#969315: marked as pending in pytsk

Control: tag -1 pending Hello, Bug #969315 in pytsk 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/pkg-security-team/pytsk/-/commit/08f5882bdc9fd5c130d71b6b925

Processed: Bug#969315 marked as pending in pytsk

Processing control commands: > tag -1 pending Bug #969315 [src:pytsk] pytsk FTBFS with sleuthkit 4.9.0 Added tag(s) pending. -- 969315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#969570: ulfius: FTBFS on s390x

Hello, Le 20-09-05 à 03 h 42, Gianfranco Costamagna a écrit :> > Hello, your package FTBFS on s390x. Please have a look if possible > [...] > Start 3: framework > 3/4 Test #3: framework ***Failed0.65 sec > Running suite(s): Ulfius framework function tests > 86%: Ch

Bug#969537: marked as done (elpa-pdf-tools-server: broken when compiled against libpoppler102)

Your message dated Sat, 05 Sep 2020 12:18:27 + with message-id and subject line Bug#969537: fixed in emacs-pdf-tools 1.0~20200512-1 has caused the Debian Bug report #969537, regarding elpa-pdf-tools-server: broken when compiled against libpoppler102 to be marked as done. This means that you c

Processed: tagging 958622

Processing commands for cont...@bugs.debian.org: > tags 958622 + pending Bug #958622 [src:tor] tor: Build-Depends on deprecated dh-systemd which is going away Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 958622: https://bugs.debian.org/cg

Bug#952085: marked as done (ruby-invisible-captcha: FTBFS: ERROR: Test "ruby2.5" failed: LoadError:)

Your message dated Sat, 05 Sep 2020 11:50:24 + with message-id and subject line Bug#952085: fixed in ruby-invisible-captcha 0.12.2-3 has caused the Debian Bug report #952085, regarding ruby-invisible-captcha: FTBFS: ERROR: Test "ruby2.5" failed: LoadError: to be marked as done. This means th

Processed: ruby-oj: ftbfs on armel, armhf and mipsel - Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "12.12345678901234"

Processing control commands: > forwarded -1 https://github.com/ohler55/oj/issues/610 Bug #969579 [ruby-oj] ruby-oj: ftbfs on armel, armhf and mipsel - Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "12.12345678901234" Set Bug forw

Bug#969578: rakudo 2020.08.2-1 breaks perl6-* modules

Package: rakudo Version: 2020.08.2-1 Severity: serious Justification: breaks other packages -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Today's update of rakudo+nqp+moarvm left a big mess, after trying several things and purging everything perl6 related an reinstalling it looks like: rakudo+

Bug#969579: ruby-oj: ftbfs on armel, armhf and mipsel - Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "12.12345678901234

Package: ruby-oj Version: 3.10.13-1 Severity: serious Control: forwarded -1 https://github.com/ohler55/oj/issues/610 Failed to build on official buildd with error 1) Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "12.12345678901

Bug#969577: caml-crush: FTBFS with GCC 10: multiple definition of `my_arch'

Source: caml-crush Version: 1.0.9-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) caml-crush fails to build with GCC 10: | gcc -Wl,-z,relro,-z,now -shared -Wl,-soname,libp11clienttcpssl.so -fPIC -o libp11client"".so pkcs

Bug#967186: marked as done (ogmrip: Unversioned Python removal in sid/bullseye)

Your message dated Sat, 5 Sep 2020 11:52:36 +0200 with message-id <20200905095236.ga663...@ramacher.at> and subject line Re: Bug#967186: ogmrip: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967186, regarding ogmrip: Unversioned Python removal in sid/bullseye to be m

Bug#967211: marked as done (swami: Unversioned Python removal in sid/bullseye)

Your message dated Sat, 5 Sep 2020 11:53:15 +0200 with message-id <20200905095315.gb663...@ramacher.at> and subject line Re: Bug#967211: swami: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967211, regarding swami: Unversioned Python removal in sid/bullseye to be mar

Bug#966020: marked as done (jekyll: ftbfs with ruby-kramdown 2.x in experimental)

Your message dated Sat, 05 Sep 2020 09:33:29 + with message-id and subject line Bug#966020: fixed in jekyll 3.9.0+dfsg-1 has caused the Debian Bug report #966020, regarding jekyll: ftbfs with ruby-kramdown 2.x in experimental to be marked as done. This means that you claim that the problem ha

Processed: Re: [Pkg-sass-devel] Processed: gitlab upstream forwarded this to libsass upstream

Processing control commands: > forwarded -1 https://github.com/sass/libsass/issues/3125 Bug #953415 [libsass] gitlab: Top-level selectors may not contain the parent selector "&" Bug #956205 [libsass] gitlab: Problem installing 12.8.8-6 Changed Bug forwarded-to-address to 'https://github.com/sass

Bug#959571: marked as pending in audacity

Control: tag -1 pending Hello, Bug #959571 in audacity 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/multimedia-team/audacity/-/commit/ec4ff31207413cd59935cf1

Processed: Bug#959571 marked as pending in audacity

Processing control commands: > tag -1 pending Bug #959571 [src:ruby-psych] ruby-psych: FTBFS: LoadError: no such file to load -- psych Added tag(s) pending. -- 959571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#969570: ulfius: FTBFS on s390x

Source: ulfius Version: 2.6.9-1 Severity: serious Hello, your package FTBFS on s390x. Please have a look if possible gmake[4]: Leaving directory '/<>/build' gmake[3]: Leaving directory '/<>/build' Start 1: core 1/4 Test #1: core . Passed0.08 sec Start 2: