Bug#972974: [Pkg-clamav-devel] Bug#972974: clamav-freshclam start faild.

I have checked the apparmor profile for clamav-daemon at /usr/sbin/clamd and | capability dac_override, exists. I had to install apparmor-utils to aa-disable the usr.sbin.clamd profile in order to get the process to load.

Bug#943060: marked as done (ifupdown-multi: Python2 removal in sid/bullseye)

Your message dated Thu, 29 Oct 2020 02:48:53 + with message-id and subject line Bug#943060: fixed in ifupdown-multi 1.0.0 has caused the Debian Bug report #943060, regarding ifupdown-multi: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#966747: marked as done (ifupdown-multi: Unversioned Python removal in sid/bullseye)

Your message dated Thu, 29 Oct 2020 02:48:53 + with message-id and subject line Bug#943060: fixed in ifupdown-multi 1.0.0 has caused the Debian Bug report #943060, regarding ifupdown-multi: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

On Wed, Oct 28, 2020 at 07:02:06PM -0300, Lucas Kanashiro wrote: > Thanks to David Rodriguez (our dear bundler upstream maintainer :) I was > able to workaround the bug locally and understand a bit better what is going > on. > > The source of this problem is this commit: > >

Bug#973286: marked as done (fonts-noto: file conflict between fonts-noto-core and fonts-noto-mono)

Your message dated Thu, 29 Oct 2020 01:18:49 + with message-id and subject line Bug#973286: fixed in fonts-noto 20201027-3 has caused the Debian Bug report #973286, regarding fonts-noto: file conflict between fonts-noto-core and fonts-noto-mono to be marked as done. This means that you claim

Bug#973303: marked as done (fonts-noto: file conflict between fonts-noto-unhinted and fonts-noto-mono)

Your message dated Thu, 29 Oct 2020 01:18:49 + with message-id and subject line Bug#973286: fixed in fonts-noto 20201027-3 has caused the Debian Bug report #973286, regarding fonts-noto: file conflict between fonts-noto-unhinted and fonts-noto-mono to be marked as done. This means that you

Bug#973286: marked as pending in fonts-noto

Control: tag -1 pending Hello, Bug #973286 in fonts-noto reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#973286 marked as pending in fonts-noto

Processing control commands: > tag -1 pending Bug #973286 {Done: Jonas Smedegaard } [src:fonts-noto] fonts-noto: file conflict between fonts-noto-core and fonts-noto-mono Bug #973297 {Done: Jonas Smedegaard } [src:fonts-noto] Conflicting file with fonts-noto-mono Bug #973303 {Done: Jonas

Bug#973297: marked as done (Conflicting file with fonts-noto-mono)

Your message dated Thu, 29 Oct 2020 01:18:49 + with message-id and subject line Bug#973286: fixed in fonts-noto 20201027-3 has caused the Debian Bug report #973286, regarding Conflicting file with fonts-noto-mono to be marked as done. This means that you claim that the problem has been dealt

Bug#973149: marked as pending in kwin

Control: tag -1 pending Hello, Bug #973149 in kwin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#973149 marked as pending in kwin

Processing control commands: > tag -1 pending Bug #973149 [src:kwin] kwin: FTBFS: egl_dmabuf.cpp:97:9: error: ‘EGL_TEXTURE_Y_XUXV_WL’ was not declared in this scope Added tag(s) pending. -- 973149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973149 Debian Bug Tracking System Contact

Processed: severity 973322 normal

Processing commands for cont...@bugs.debian.org: > severity 973322 normal Bug #973322 [thunderbird] thunderbird: caldav calendar missing some events and shows "!" with Assert failed: unexpected endBatch in error console Severity set to 'normal' from 'serious' > End of message, stopping

Bug#973322: Acknowledgement (thunderbird: caldav calendar missing some events and shows "!" with Assert failed: unexpected endBatch in error console)

On Wed, Oct 28, 2020 at 02:46:52PM -0500, Ryan Nowakowski wrote: > With the previous version of thunderbird(68.12.0), I did not see this > issue. I have the older version (68.12.0) still running on a different Debian 10 machine(along with lightning 68.12.0 since it used to be a separate

Bug#972974: [Pkg-clamav-devel] Bug#972974: clamav-freshclam start faild.

On 2020-10-27 07:22:22 [+], Michael Borgelt wrote: > I have tried different permissions for the file and the directory without > success. The obove permissions are after a clean reinstall off clamav > package. The problem appears to be the apparmor or freshclam's profile for it. So disabling

Bug#973144: marked as done (restic: FTBFS: src/github.com/restic/restic/internal/fuse/blobcache.go:9:2: cannot find package "github.com/hashicorp/golang-lru/simplelru")

Your message dated Wed, 28 Oct 2020 23:03:31 + with message-id and subject line Bug#973144: fixed in restic 0.10.0-2 has caused the Debian Bug report #973144, regarding restic: FTBFS: src/github.com/restic/restic/internal/fuse/blobcache.go:9:2: cannot find package

Bug#963321: marked as done (python-pyaudio: FTBFS: dh_linktree: error: link destination debian/python-pyaudio-doc/usr/share/doc/python-pyaudio-doc/docs/_static is a directory)

Your message dated Wed, 28 Oct 2020 22:49:42 + with message-id and subject line Bug#961798: fixed in python-pyaudio 0.2.11-1.2 has caused the Debian Bug report #961798, regarding python-pyaudio: FTBFS: dh_linktree: error: link destination

Bug#961798: marked as done (python-pyaudio: FTBFS for doc package)

Your message dated Wed, 28 Oct 2020 22:49:42 + with message-id and subject line Bug#961798: fixed in python-pyaudio 0.2.11-1.2 has caused the Debian Bug report #961798, regarding python-pyaudio: FTBFS for doc package to be marked as done. This means that you claim that the problem has been

Bug#957270: marked as done (getdp: ftbfs with GCC-10)

Your message dated Wed, 28 Oct 2020 22:18:35 + with message-id and subject line Bug#957270: fixed in getdp 3.2.0+dfsg1-1.1 has caused the Debian Bug report #957270, regarding getdp: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

Thanks to David Rodriguez (our dear bundler upstream maintainer :) I was able to workaround the bug locally and understand a bit better what is going on. The source of this problem is this commit: https://github.com/rubygems/rubygems/commit/226ec115fe503bcc93bffdf5cd3e8a668890b4d8 Quoting

Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.syst

Hi Andreas, I can confirm that this bug is in commons-io 2.8.0 while commons-io 2.6 workes fine. The bug is in PathUtils.deleteFile(), line 360 and 361: """ final boolean exists = Files.exists(file, LinkOption.NOFOLLOW_LINKS); final long size = exists ? Files.size(file) : 0;

Bug#957132: dibbler: diff for NMU version 1.0.1-1.1

Control: tags 957132 + patch Control: tags 957132 + pending -- Dear maintainer, I've prepared an NMU for dibbler (versioned as 1.0.1-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru dibbler-1.0.1/debian/changelog

Processed: dibbler: diff for NMU version 1.0.1-1.1

Processing control commands: > tags 957132 + patch Bug #957132 [src:dibbler] dibbler: ftbfs with GCC-10 Added tag(s) patch. > tags 957132 + pending Bug #957132 [src:dibbler] dibbler: ftbfs with GCC-10 Added tag(s) pending. -- 957132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957132

Bug#973012: marked as done (pybind11's autopkg tests are failing, blocking python3-defaults)

Your message dated Wed, 28 Oct 2020 20:36:32 + with message-id and subject line Bug#973012: fixed in pybind11 2.6.0-1 has caused the Debian Bug report #973012, regarding pybind11's autopkg tests are failing, blocking python3-defaults to be marked as done. This means that you claim that the

Bug#973295: marked as done (command4 autopkg test fails with 3.8 and 3.9 as supported)

Your message dated Wed, 28 Oct 2020 20:36:32 + with message-id and subject line Bug#973295: fixed in pybind11 2.6.0-1 has caused the Debian Bug report #973295, regarding command4 autopkg test fails with 3.8 and 3.9 as supported to be marked as done. This means that you claim that the problem

Bug#957788: marked as done (seyon: ftbfs with GCC-10)

Your message dated Wed, 28 Oct 2020 20:37:32 + with message-id and subject line Bug#957788: fixed in seyon 2.20c-33 has caused the Debian Bug report #957788, regarding seyon: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#973322: thunderbird: caldav calendar missing some events and shows "!" with Assert failed: unexpected endBatch in error console

Package: thunderbird Version: 1:78.4.0-1~deb10u1 Severity: serious Justification: 4 Dear Maintainer, After upgrading to this release one of my caldav calendars(served from davmail), some calendar events are missing. Thunderbird consistently shows an "!" next to it in the sidebar. After

Bug#973112: marked as done (libcxx-serial: FTBFS: make[5]: *** No rule to make target 'tests/gmock/libgmock.a', needed by 'devel/lib/cxx-serial/cxx-serial-test'. Stop.)

Your message dated Wed, 28 Oct 2020 19:48:31 + with message-id and subject line Bug#973112: fixed in libcxx-serial 1.2.1-4 has caused the Debian Bug report #973112, regarding libcxx-serial: FTBFS: make[5]: *** No rule to make target 'tests/gmock/libgmock.a', needed by

Bug#957769: marked as done (rotter: ftbfs with GCC-10)

Your message dated Wed, 28 Oct 2020 19:48:49 + with message-id and subject line Bug#957769: fixed in rotter 0.9-3.1 has caused the Debian Bug report #957769, regarding rotter: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: found 973286 in 20201027-2

Processing commands for cont...@bugs.debian.org: > found 973286 20201027-2 Bug #973286 {Done: Jonas Smedegaard } [src:fonts-noto] fonts-noto: file conflict between fonts-noto-core and fonts-noto-mono Bug #973297 {Done: Jonas Smedegaard } [src:fonts-noto] Conflicting file with fonts-noto-mono

Bug#957686: pinfo: diff for NMU version 0.6.13-1.1

Thanks, very much appreciated!  nfortunately I don't have much  time to spend on this package, so all help is welcome :) Greetings, bas. On 28-10-2020 20:13, Sudip Mukherjee wrote: > Control: tags 957686 + patch > Control: tags 957686 + pending > -- > > Dear maintainer, > > I've prepared an NMU

Bug#973070: marked as done (libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unable to del

Your message dated Wed, 28 Oct 2020 19:35:09 + with message-id and subject line Bug#973070: fixed in libsis-base-java 18.09~pre1+git20180928.45fbd31+dfsg-1 has caused the Debian Bug report #973070, regarding libsis-base-java: FTBFS: Could not delete the directory

Processed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.syst

Processing control commands: > forwarded -1 Bernd Rinn Bug #973070 [src:libsis-base-java] libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unable to delete file:

Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.syst

Control: forwarded -1 Bernd Rinn Hi, I'd recommend reading the bug report log from here to get some hints about recommended changes in the code: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973070#17 For the moment I've excluded the affected tests. Kind regards Andreas.

Processed: pinfo: diff for NMU version 0.6.13-1.1

Processing control commands: > tags 957686 + patch Bug #957686 [src:pinfo] pinfo: ftbfs with GCC-10 Added tag(s) patch. > tags 957686 + pending Bug #957686 [src:pinfo] pinfo: ftbfs with GCC-10 Added tag(s) pending. -- 957686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957686 Debian Bug

Bug#957686: pinfo: diff for NMU version 0.6.13-1.1

Control: tags 957686 + patch Control: tags 957686 + pending -- Dear maintainer, I've prepared an NMU for pinfo (versioned as 0.6.13-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru pinfo-0.6.13/debian/changelog

Bug#943060: ifupdown-multi: Python2 removal in sid/bullseye

On Wed, Oct 28, 2020 at 02:38:14PM -0400, Robert Edmonds wrote: > Moritz Mühlenhoff wrote: > > On Wed, Oct 23, 2019 at 02:33:26AM +, mo...@debian.org wrote: > > > Source: ifupdown-multi > > > Version: 0.1.1 > > > Severity: normal > > > Tags: sid bullseye > > > User:

Bug#938150: python-ruamel.ordereddict: Python2 removal in sid/bullseye

On Fri, Aug 30, 2019 at 07:46:25AM +, Matthias Klose wrote: > Package: src:python-ruamel.ordereddict > Version: 0.4.14-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove >

Bug#956285: Problems identified in debian/copyright

On Mon, Jul 06, 2020 at 10:14:48PM +0200, Petter Reinholdtsen wrote: > [Michael Lustfield] > > I noticed that this package appears to have some issues with > > debian/copyright. > > Hi. Any hope to have a fix for this in time for the next stable release? JFTR, this is fixed in 1.2.9 Cheers,

Processed: severity of 947299 is serious

Processing commands for cont...@bugs.debian.org: > severity 947299 serious Bug #947299 [src:hgsubversion] hgsubversion: Python2 removal in sid/bullseye Bug #936700 [src:hgsubversion] hgsubversion: Python2 removal in sid/bullseye Bug #948847 [src:hgsubversion] hgsubversion: Python2 removal in

Processed: severity of 938492 is normal

Processing commands for cont...@bugs.debian.org: > severity 938492 normal Bug #938492 [src:six] six: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 938492:

Bug#943060: ifupdown-multi: Python2 removal in sid/bullseye

Moritz Mühlenhoff wrote: > On Wed, Oct 23, 2019 at 02:33:26AM +, mo...@debian.org wrote: > > Source: ifupdown-multi > > Version: 0.1.1 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal > > > > Python2 becomes end-of-live upstream,

Processed: severity of 973298 is serious

Processing commands for cont...@bugs.debian.org: > severity 973298 serious Bug #973298 [src:rust-failure] rust-failure: Should rust-failure be removed from unstable? Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 973298:

Bug#973070: [Debian-med-packaging] Bug#973070: Help needed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exc

Am 28.10.20 um 16:01 schrieb olivier sallou: [...] > *dumb* patch would be to simply remove those tests from code... Either this or you can keep the override for dh_auto_test-arch empty. The test creates a broken symlink but then FileUtils.deleteDirectory fails to delete the file, obviously

Processed: Re: lilo: ftbfs with GCC-10

Processing commands for cont...@bugs.debian.org: > tags 957490 + patch Bug #957490 [src:lilo] lilo: ftbfs with GCC-10 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 957490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957490 Debian Bug

Bug#957490: lilo: ftbfs with GCC-10

tags 957490 + patch thanks Please see attached debdiff for a NMU ftbfs fix. Sponsorship is requested, thank you. diff -Nru lilo-24.2/debian/changelog lilo-24.2/debian/changelog --- lilo-24.2/debian/changelog 2019-12-10 14:41:00.0 -0800 +++ lilo-24.2/debian/changelog 2020-10-28

Bug#943060: ifupdown-multi: Python2 removal in sid/bullseye

On Wed, Oct 23, 2019 at 02:33:26AM +, mo...@debian.org wrote: > Source: ifupdown-multi > Version: 0.1.1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the

Bug#973286: [Pkg-fonts-devel] Bug#973286: fonts-noto: file conflict between fonts-noto-core and fonts-noto-mono

Quoting Witold Baryluk (2020-10-28 19:06:06) > I think the issue is not fully resolved: > > > Preparing to unpack .../fonts-noto-unhinted_20201027-2_all.deb ... > Unpacking fonts-noto-unhinted (20201027-2) over (20200323-1) ... > dpkg: error processing archive >

Bug#972118: nmu: tpm2-abrmd_2.3.3-1 tpm2-tools_4.3.0-1

Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: normal Hello, libtpm2-tss bump the soname of its lib. Make the package tpm2-abrmd needs to build against the latest libtpm2-tss. Please see #972118 We have split the tpm2-tss already so that the

Bug#973206: marked as done (libldac: FTBFS: dh_auto_configure: error: mini-soong -o soong.mk returned exit code 1)

Your message dated Wed, 28 Oct 2020 18:20:15 + with message-id and subject line Bug#973206: fixed in mini-soong 0.20201028 has caused the Debian Bug report #973206, regarding libldac: FTBFS: dh_auto_configure: error: mini-soong -o soong.mk returned exit code 1 to be marked as done. This

Bug#973100: prometheus-postfix-exporter: FTBFS: src/github.com/alecthomas/kingpin/i18n_init.go:13:2: cannot find package "github.com/nicksnyder/go-i18n/i18n" in any of:

Hi! On 28/10/2020 15:06, Shengjing Zhu wrote: >> This bug is actually on the golang-github-nicksnyder-go-i18n-dev >> package. It seems the last upload brought a new API version, which >> changes import paths, and probably other API breaks. This should have >> been a new binary package and not an

Processed: found 973206 in 0.20201018

Processing commands for cont...@bugs.debian.org: > found 973206 0.20201018 Bug #973206 [src:mini-soong] libldac: FTBFS: dh_auto_configure: error: mini-soong -o soong.mk returned exit code 1 Marked as found in versions mini-soong/0.20201018. > thanks Stopping processing here. Please contact me

Bug#973286: fonts-noto: file conflict between fonts-noto-core and fonts-noto-mono

Package: fonts-noto Version: 20201027-2 Followup-For: Bug #973286 X-Debbugs-Cc: witold.bary...@gmail.com I think the issue is not fully resolved: Preparing to unpack .../fonts-noto-unhinted_20201027-2_all.deb ... Unpacking fonts-noto-unhinted (20201027-2) over (20200323-1) ... dpkg: error

Processed: reassign 973206 to src:mini-soong

Processing commands for cont...@bugs.debian.org: > reassign 973206 src:mini-soong Bug #973206 [src:libldac] libldac: FTBFS: dh_auto_configure: error: mini-soong -o soong.mk returned exit code 1 Bug reassigned from package 'src:libldac' to 'src:mini-soong'. No longer marked as found in versions

Bug#957640: marked as done (openntpd: ftbfs with GCC-10)

Your message dated Wed, 28 Oct 2020 17:49:50 + with message-id and subject line Bug#957640: fixed in openntpd 1:6.2p3-4.1 has caused the Debian Bug report #957640, regarding openntpd: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#972721: marked as done (python-httpretty: ftbfs with python3.9 as supported version)

Your message dated Wed, 28 Oct 2020 17:50:10 + with message-id and subject line Bug#972721: fixed in python-httpretty 0.9.5-7 has caused the Debian Bug report #972721, regarding python-httpretty: ftbfs with python3.9 as supported version to be marked as done. This means that you claim that

Bug#973019: marked as done (python-boto's autopkg tests are failing with python3.9)

Your message dated Wed, 28 Oct 2020 18:37:38 +0100 with message-id and subject line No bug has caused the Debian Bug report #973019, regarding python-boto's autopkg tests are failing with python3.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

Running the same command with verbose enabled tells us that bundler ignores the ffi gem because it's missing extensions: root@rubygems-test:~/test# bundle --local --verbose Running `bundle install --local --verbose` with bundler 2.2.0.rc.1 Don't run Bundler as root. Bundler can ask for sudo if

Bug#973062: Confirming

Hi, I confirm that the s/isAlive/is_alive/ issue was in httpretty, though after fixing that one, cloud-init still suffered from broken tests under Python 3.9 with OpenNebula. I've blacklisted the tests for that data source, because I don't think anyone cares much about OpenNebula in 2020. If I'm

Bug#972721: marked as pending in python-httpretty

Control: tag -1 pending Hello, Bug #972721 in python-httpretty reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#972721 marked as pending in python-httpretty

Processing control commands: > tag -1 pending Bug #972721 [src:python-httpretty] python-httpretty: ftbfs with python3.9 as supported version Added tag(s) pending. -- 972721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972721 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: reassign 973303 to src:fonts-noto, forcibly merging 973286 973303

Processing commands for cont...@bugs.debian.org: > reassign 973303 src:fonts-noto Bug #973303 [fonts-noto-unhinted] fonts-noto: file conflict between fonts-noto-unhinted and fonts-noto-mono Bug reassigned from package 'fonts-noto-unhinted' to 'src:fonts-noto'. No longer marked as found in

Bug#971155: marked as done (gitlab-workhorse: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 gitlab.com/gitlab-org/gitlab-workhorse gitlab.com/gitlab-org/gitlab-workhorse/cmd/gitlab

Your message dated Wed, 28 Oct 2020 15:18:46 + with message-id and subject line Bug#971155: fixed in gitlab-workhorse 8.39.0+debian-1 has caused the Debian Bug report #971155, regarding gitlab-workhorse: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4

Bug#973100: prometheus-postfix-exporter: FTBFS: src/github.com/alecthomas/kingpin/i18n_init.go:13:2: cannot find package "github.com/nicksnyder/go-i18n/i18n" in any of:

On Wed, Oct 28, 2020 at 8:48 PM Martina Ferrari wrote: > > reassign 973100 golang-github-nicksnyder-go-i18n-dev > retitle 973100 Breaks API without package name change > thanks > > This bug is actually on the golang-github-nicksnyder-go-i18n-dev > package. It seems the last upload brought a new

Bug#973070: [Debian-med-packaging] Bug#973070: Help needed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exc

On Wed, 2020-10-28 at 09:05 +0100, Andreas Tille wrote: > Hi, > > On Tue, Oct 27, 2020 at 10:55:43PM +0100, Markus Koschany wrote: > > This appears to be caused by the recent upgrade of Apache commons- > > io to > > version 2.8.0 (we had 2.6), see also #973135. In version 2.7 they > > removed a

Bug#973238: marked as done (typedload: FTBFS: typedload/datadumper.py:159: error: NotImplemented? not callable)

Your message dated Wed, 28 Oct 2020 15:03:53 + with message-id and subject line Bug#973238: fixed in typedload 2.3-1 has caused the Debian Bug report #973238, regarding typedload: FTBFS: typedload/datadumper.py:159: error: NotImplemented? not callable to be marked as done. This means that

Bug#972971: marked as done (atlas-ecmwf FTBFS on 32bit)

Your message dated Wed, 28 Oct 2020 15:03:28 + with message-id and subject line Bug#972971: fixed in atlas-ecmwf 0.22.0-5 has caused the Debian Bug report #972971, regarding atlas-ecmwf FTBFS on 32bit to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#973218: marked as done (localslackirc: FTBFS: rocket.py:213: error: NotImplemented? not callable)

Your message dated Wed, 28 Oct 2020 15:49:18 +0100 with message-id and subject line Closing has caused the Debian Bug report #973218, regarding localslackirc: FTBFS: rocket.py:213: error: NotImplemented? not callable to be marked as done. This means that you claim that the problem has been

Processed: reassign 973297 to src:fonts-noto, forcibly merging 973286 973297

Processing commands for cont...@bugs.debian.org: > reassign 973297 src:fonts-noto Bug #973297 [fonts-noto-core] Conflicting file with fonts-noto-mono Bug reassigned from package 'fonts-noto-core' to 'src:fonts-noto'. No longer marked as found in versions fonts-noto/20201027-1. Ignoring request to

Bug#933091: marked as done (node-rollup-plugin-typescript seems incompatible with rollup/typescript)

Your message dated Wed, 28 Oct 2020 11:22:05 +0100 with message-id <30a3f306-ac8d-9b05-0c83-8a32859d6...@debian.org> and subject line Already Fixed has caused the Debian Bug report #933091, regarding node-rollup-plugin-typescript seems incompatible with rollup/typescript to be marked as done.

Bug#967965: marked as done (astropy: FTBFS with scipy 1.5: [doctest] astropy.stats.funcs.binom_conf_interval failed)

Your message dated Wed, 28 Oct 2020 12:10:20 +0100 with message-id <38b54f2e-574a-2199-91ec-074e061d8...@debian.org> and subject line Re: astropy test fails has caused the Debian Bug report #967965, regarding astropy: FTBFS with scipy 1.5: [doctest] astropy.stats.funcs.binom_conf_interval failed

Processed (with 1 error): forcibly merging 973286 973297

Processing commands for cont...@bugs.debian.org: > forcemerge 973286 973297 Bug #973286 {Done: Jonas Smedegaard } [src:fonts-noto] fonts-noto: file conflict between fonts-noto-core and fonts-noto-mono Unable to merge bugs because: package of #973297 is 'fonts-noto-core' not 'src:fonts-noto'

Bug#973297: Conflicting file with fonts-noto-mono

Package: fonts-noto-core Version: 20201027-1 Severity: serious Hi, just today: root@gnu:~# LC_ALL=C apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded:   fonts-noto-core 1

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

On 2020/10/12 15:54, Paul Wise wrote: > On Mon, 2020-10-12 at 15:35 +0200, Kyle Robbertze wrote: > >> I'm going to consider requesting the removal of this package from >> unstable in the next while unless there is any other opinions. > > That seems reasonable. > > Personally I wanted an

Bug#973100: prometheus-postfix-exporter: FTBFS: src/github.com/alecthomas/kingpin/i18n_init.go:13:2: cannot find package "github.com/nicksnyder/go-i18n/i18n" in any of:

reassign 973100 golang-github-nicksnyder-go-i18n-dev retitle 973100 Breaks API without package name change thanks This bug is actually on the golang-github-nicksnyder-go-i18n-dev package. It seems the last upload brought a new API version, which changes import paths, and probably other API

Processed: Bug#972758 in package liburing marked as pending

Processing control commands: > tag 972758 pending Bug #972758 {Done: Guillem Jover } [liburing1] ABI breakage without soname bump Added tag(s) pending. -- 972758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#973100: prometheus-postfix-exporter: FTBFS: src/github.com/alecthomas/kingpin/i18n_init.go:13:2: cannot find package "github.com/nicksnyder/go-i18n/i18n" in any of:

Processing commands for cont...@bugs.debian.org: > reassign 973100 golang-github-nicksnyder-go-i18n-dev Bug #973100 [src:prometheus-postfix-exporter] prometheus-postfix-exporter: FTBFS: src/github.com/alecthomas/kingpin/i18n_init.go:13:2: cannot find package "github.com/nicksnyder/go-i18n/i18n"

Bug#972758: in package liburing marked as pending

Control: tag 972758 pending Hi! Bug #972758 in package liburing reported by you has been fixed in the debian/pkgs/liburing.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.hadrons.org/cgit/debian/pkgs/liburing.git/diff/?id=941e718

Bug#973135: plexus-io: FTBFS

I can't reproduce the build failure in SymlinkUtilsTest.java. On my system all tests succeed. This is strange because upstream pushed a commit a few months ago that seems to address a symlink test failure. https://github.com/codehaus-plexus/plexus-io/pull/24 It is related to the maven resource

Bug#973295: command4 autopkg test fails with 3.8 and 3.9 as supported

Package: src:pybind11 Version: 2.5.0-5 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 command4 autopkg test fails with 3.8 and 3.9 as supported the build picks up 3.9, but the test then runs with 3.8: the test dependency for that test should be

Bug#972758: marked as done (ABI breakage without soname bump)

Your message dated Wed, 28 Oct 2020 12:03:31 + with message-id and subject line Bug#972758: fixed in liburing 0.7-2 has caused the Debian Bug report #972758, regarding ABI breakage without soname bump to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#973081: marked as done (pdf.js: FTBFS: [12:18:32] TypeError: Cannot read property 'then' of undefined)

Your message dated Wed, 28 Oct 2020 11:31:05 +0100 with message-id and subject line Fixed has caused the Debian Bug report #973081, regarding pdf.js: FTBFS: [12:18:32] TypeError: Cannot read property 'then' of undefined to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#972789: qemu: FTBFS on arm{el,hf}: /<>/linux-user/m68k/signal.c:44:1: error: ‘TYPE_CANONICAL’ is not compatible

Processing control commands: > reassign -1 gcc-10 10.2.0-15 Bug #972789 [src:qemu] qemu: FTBFS on arm{el,hf}: /<>/linux-user/m68k/signal.c:44:1: error: ‘TYPE_CANONICAL’ is not compatible Bug reassigned from package 'src:qemu' to 'gcc-10'. No longer marked as found in versions qemu/1:5.1+dfsg-4.

Bug#972789: qemu: FTBFS on arm{el,hf}: /<>/linux-user/m68k/signal.c:44:1: error: ‘TYPE_CANONICAL’ is not compatible

Control: reassign -1 gcc-10 10.2.0-15 Control: tags -1 upstream Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97323 Control: affects -1 src:qemu On 2020-10-24 07:38:39 +0300, Michael Tokarev wrote: > 23.10.2020 19:50, Sebastian Ramacher wrote: > > Source: qemu > > Version:

Bug#973286: marked as done (fonts-noto: file conflict between fonts-noto-core and fonts-noto-mono)

Your message dated Wed, 28 Oct 2020 11:19:11 + with message-id and subject line Bug#973286: fixed in fonts-noto 20201027-2 has caused the Debian Bug report #973286, regarding fonts-noto: file conflict between fonts-noto-core and fonts-noto-mono to be marked as done. This means that you claim

Processed: Bug#973286 marked as pending in fonts-noto

Processing control commands: > tag -1 pending Bug #973286 {Done: Jonas Smedegaard } [src:fonts-noto] fonts-noto: file conflict between fonts-noto-core and fonts-noto-mono Added tag(s) pending. -- 973286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973286 Debian Bug Tracking System

Bug#973286: marked as pending in fonts-noto

Control: tag -1 pending Hello, Bug #973286 in fonts-noto reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#973103: marked as done (node-lunr: FTBFS: tests failed)

Your message dated Wed, 28 Oct 2020 10:35:08 + with message-id and subject line Bug#973103: fixed in node-lunr 2.3.8~dfsg-2 has caused the Debian Bug report #973103, regarding node-lunr: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with.

Processed: fixed 973081 in 2.6.347+dfsg-2

Processing commands for cont...@bugs.debian.org: > fixed 973081 2.6.347+dfsg-2 Bug #973081 [src:pdf.js] pdf.js: FTBFS: [12:18:32] TypeError: Cannot read property 'then' of undefined Marked as fixed in versions pdf.js/2.6.347+dfsg-2. > thanks Stopping processing here. Please contact me if you

Bug#973170: node-fetch has no default export

Control: retitle -1 node-fetch has no default export Le 27/10/2020 à 21:47, Xavier a écrit : > Control: reassign -1 node-fetch > Control: affects -1 node-formidable > > Le 27/10/2020 à 18:07, Lucas Nussbaum a écrit : >> Source: node-formidable >> Version: 1.2.1+20200129git8231ea6-1 >> Severity:

Processed: Re: [Pkg-javascript-devel] Bug#973081: Bug#973081: pdf.js: FTBFS: [12:18:32] TypeError: Cannot read property 'then' of undefined

Processing control commands: > reassign -1 src:pdf.js Bug #973081 {Done: Xavier Guimard } [webpack] pdf.js: FTBFS: [12:18:32] TypeError: Cannot read property 'then' of undefined Bug reassigned from package 'webpack' to 'src:pdf.js'. Ignoring request to alter found versions of bug #973081 to the

Bug#973081: [Pkg-javascript-devel] Bug#973081: Bug#973081: pdf.js: FTBFS: [12:18:32] TypeError: Cannot read property 'then' of undefined

Control: reassign -1 src:pdf.js Control: found -1 2.6.347+dfsg-1 Le 27/10/2020 à 23:29, Xavier a écrit : > Control: reassign -1 webpack > Control: affects -1 src:pdf.js > > Le 27/10/2020 à 18:09, Lucas Nussbaum a écrit : >> Source: pdf.js >> Version: 2.6.347+dfsg-1 >> Severity: serious >>

Bug#973147: pg-wait-sampling: FTBFS: diff in generated debian/control

Hello, A fix has been submitted: https://github.com/postgrespro/pg_wait_sampling/pull/28 We also must wait for a new release from the project. Regards, -- Adrien NAYRAT

Processed: Re: Bug#973170: node-fetch has no default export

Processing control commands: > retitle -1 node-fetch has no default export Bug #973170 [node-fetch] node-formidable: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Changed Bug title to 'node-fetch has no default export' from 'node-formidable: FTBFS:

Bug#973103: marked as pending in node-lunr

Control: tag -1 pending Hello, Bug #973103 in node-lunr reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: sphinxcontrib-bibtex FTBFS was actually a bug in python-latexcodec (fixed now)

Processing commands for cont...@bugs.debian.org: > reassign 973037 src:python-latexcodec 1.0.7-1 Bug #973037 [src:sphinxcontrib-bibtex] sphinxcontrib-bibtex's autopkg tests are failing with python3.9 Bug reassigned from package 'src:sphinxcontrib-bibtex' to 'src:python-latexcodec'. No longer

Processed: Bug#973103 marked as pending in node-lunr

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

Processed: tagging 957881

Processing commands for cont...@bugs.debian.org: > tags 957881 + ftbfs Bug #957881 [src:tpm2-initramfs-tool] tpm2-initramfs-tool: ftbfs with GCC-10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 957881:

Bug#972175: closed by Debian FTP Masters (reply to Thomas Pierson ) (Bug#972175: fixed in clementine 1.4.0~rc1+git346-g4e3e9c8d1+dfsg-1)

On Tue, Oct 27, 2020 at 12:47:00PM +0100, Thomas Pierson wrote: > Hi Dmitry, > > I just uploaded a new version of clementine disabling projectm for now > because I have also others issues related to its integration. I need a bit > of time to work on this. > > So for now the new version of

Bug#973292: blender ftbfs with python3.9

Package: src:blender Version: 2.83.5+dfsg-3 Severity: serious Tags: sid bullseye ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.9 to reproduce, you can use the repositories found at: deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./ deb [trusted=yes]

Bug#973290: ros-ros ftbfs in unstable with python3.9

Package: src:ros-ros Version: 1.15.7-1 Severity: serious Tags: sid bullseye ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.9 to reproduce, you can use the repositories found at: deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./ deb [trusted=yes]

  1   2   >