Bug#969227: marked as done (FTBFS with new runc 1.0.0~rc92 and libcap2 2.43)

Your message dated Fri, 04 Sep 2020 04:33:28 + with message-id and subject line Bug#969227: fixed in docker.io 19.03.12+dfsg1-4 has caused the Debian Bug report #969227, regarding FTBFS with new runc 1.0.0~rc92 and libcap2 2.43 to be marked as done. This means that you claim that the problem

Bug#969360: Qt seccomp failure patch works

Control: tags -1 - fixed-upstream On Wednesday, September 2, 2020 8:02:42 AM EDT Dmitry Shachnev wrote: > My guess is that we need this patch (not applied upstream yet) Thanks for the pointer, that patch applies cleanly and fixes the issue. > But that bug (QTBUG-81313) is already fixed in Qt

Processed: Re: Bug#969360: Qt seccomp failure patch works

Processing control commands: > tags -1 - fixed-upstream Bug #969360 {Done: Dmitry Shachnev } [libqt5webengine5] kmail freezes when selecting a read mail to show Bug #967011 {Done: Dmitry Shachnev } [libqt5webengine5] [i386] **CRASHING**:seccomp-bpf failure in syscall 0403 Removed tag(s)

Bug#966751: libapache2-mod-python: Unversioned Python removal in sid/bullseye

Control: tag -1 pending Hi, A new upstream release 3.5.0 support py3. This new upstream release is available on salsa. Waiting for sponsorship. Cheers, Arias Emmanuel @eamanu yaerobi.com

Processed: libapache2-mod-python: Unversioned Python removal in sid/bullseye

Processing control commands: > tag -1 pending Bug #966751 [src:libapache2-mod-python] libapache2-mod-python: Unversioned Python removal in sid/bullseye Added tag(s) pending. -- 966751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966751 Debian Bug Tracking System Contact

Bug#967173: marked as done (mediaelement: Unversioned Python removal in sid/bullseye)

Your message dated Thu, 03 Sep 2020 21:03:36 + with message-id and subject line Bug#967173: fixed in mediaelement 2.15.1+dfsg-3 has caused the Debian Bug report #967173, regarding mediaelement: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that

Bug#967211: swami: Unversioned Python removal in sid/bullseye

Hi Matthias, it looks for me that this bug is false positive, because swami has no python dependency and py-compile from the root dir is not in use. Best regards, Dennis

Bug#957816: marked as done (slurm-llnl: ftbfs with GCC-10)

Your message dated Thu, 3 Sep 2020 21:46:43 +0100 with message-id <206e5ae7-2b18-1150-8125-98b0393ac...@p10link.net> and subject line re: slurm-llnl: ftbfs with GCC-10 has caused the Debian Bug report #957816, regarding slurm-llnl: ftbfs with GCC-10 to be marked as done. This means that you claim

Processed: Re: Bug#969494: r-cran-mice: autopkgtest regression: there is no package called ‘broom.mixed’

Processing control commands: > tags -1 pending Bug #969494 [src:r-cran-mice] r-cran-mice: autopkgtest regression: there is no package called ‘broom.mixed’ Added tag(s) pending. -- 969494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969494 Debian Bug Tracking System Contact

Bug#938408: marked as done (rows: Python2 removal in sid/bullseye)

Your message dated Thu, 03 Sep 2020 20:10:09 + with message-id and subject line Bug#938408: fixed in rows 0.4.1-1 has caused the Debian Bug report #938408, regarding rows: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#969494: r-cran-mice: autopkgtest regression: there is no package called ‘broom.mixed’

Control: tags -1 pending Hi Paul, I just realised this in the new version of r-cran-mice and just pushed the missing dependency to new: https://ftp-master.debian.org/new/r-cran-broom.mixed_0.2.6-1.html Hope it will be processed soon to fix this bug. Thanks for all your work

Processed: limit source to mediaelement, tagging 937001, tagging 967173

Processing commands for cont...@bugs.debian.org: > limit source mediaelement Limiting to bugs with field 'source' containing at least one of 'mediaelement' Limit currently set to 'source':'mediaelement' > tags 937001 + pending Bug #937001 [src:mediaelement] mediaelement: Python2 removal in

Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2

On Thu, Sep 3, 2020 at 3:02 PM Michael Biebl wrote: > > Hi Dan Hi Michael > > Am 03.09.20 um 20:42 schrieb Dan Streetman: > > On Mon, Aug 17, 2020 at 4:42 AM Michael Biebl wrote: > and over again. > >> > >> Afaics, the simplest solution, is to simply drop > >> > >>

Bug#969498: mame FTBFS on mips64el: error: relocation overflow

Source: mame Version: 0.224+dfsg.1-2 Severity: serious Tags: patch ftbfs https://buildd.debian.org/status/fetch.php?pkg=mame=mips64el=0.224%2Bdfsg.1-2=1598916733=0 ... ../../../../../scripts/mame_mame/libbarcrest.a(mpu4sw.o):mpu4sw.cpp:function mpu4_state::init_m4debug(): error: relocation

Bug#969467: marked as done (miller: CVE-2020-15167)

Your message dated Thu, 03 Sep 2020 19:04:27 + with message-id and subject line Bug#969467: fixed in miller 5.9.1+dfsg-1 has caused the Debian Bug report #969467, regarding miller: CVE-2020-15167 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#969494: r-cran-mice: autopkgtest regression: there is no package called ‘broom.mixed’

Source: r-cran-mice Version: 3.10.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of r-cran-mice the autopkgtest of r-cran-mice fails in testing when that autopkgtest is run with the

Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2

Hi Dan Am 03.09.20 um 20:42 schrieb Dan Streetman: > On Mon, Aug 17, 2020 at 4:42 AM Michael Biebl wrote: and over again. >> >> Afaics, the simplest solution, is to simply drop >> >> PathExists=/run/systemd/resolve/stub-resolv.conf >> >> and instead add a >> >> [Install] >>

Processed: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

Processing control commands: > close -1 1.33+dfsg-2 Bug #969493 [src:nanook] src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries Marked as fixed in versions nanook/1.33+dfsg-2. Bug #969493 [src:nanook] src:nanook: fails to migrate to testing for too long:

Bug#969493: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

Source: nanook Version: 1.33+dfsg-1 Severity: serious Control: close -1 1.33+dfsg-2 Tags: sid bullseye pending 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

Processed: src:xoreos-tools: fails to migrate to testing for too long: unsatisfied Depends

Processing control commands: > close -1 0.0.5-2 Bug #969492 [src:xoreos-tools] src:xoreos-tools: fails to migrate to testing for too long: unsatisfied Depends Marked as fixed in versions xoreos-tools/0.0.5-2. Bug #969492 [src:xoreos-tools] src:xoreos-tools: fails to migrate to testing for too

Bug#969492: src:xoreos-tools: fails to migrate to testing for too long: unsatisfied Depends

Source: xoreos-tools Version: 0.0.5-1 Severity: serious Control: close -1 0.0.5-2 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 and

Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2

On Mon, Aug 17, 2020 at 4:42 AM Michael Biebl wrote: > > Control: severity -1 serious > Control: tags -1 + patch > > Hi everyone, > > I think the effects of this issue are severe enough, that it needs to be > fixed for bullseye. In other words, it should be RC > > On Sat, 08 Aug 2020 13:13:44

Bug#968339: marked as done (kodi: FTBFS in sid (test failures))

Your message dated Thu, 03 Sep 2020 18:03:57 + with message-id and subject line Bug#968339: fixed in kodi 2:18.8+dfsg1-2 has caused the Debian Bug report #968339, regarding kodi: FTBFS in sid (test failures) to be marked as done. This means that you claim that the problem has been dealt

Bug#936391: Bug#905014: Short status message about dhcpy6d in Debian Unstable and the Python 2 to 3 migration

Hi, Axel Beckert wrote: > just a short update on dhcpy6d in Debian Unstable (and the Python 2 to > 3 migration): > > I'm planning to do an upload of the 1.0.1 upstream version to Debian > Unstable soon (next few days) to fix the Python 2 to 3 migration issue > (#936391) and get the package back

Processed: [bts-link] source package gnome-music

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package gnome-music > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:mariadb-10.0

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:mariadb-10.0 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Processed: [bts-link] source package rasdaemon

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package rasdaemon > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#969477: Acknowledgement (zfs-dkms fails to compile with 5.7.0-3 kernel blocking kernel upgrade)

FYI... jordan@jordan-laptop:~$ cat /var/lib/dkms/zfs/0.8.4/build/make.log DKMS make.log for zfs-0.8.4 for kernel 5.7.0-3-amd64 (x86_64) Thu 03 Sep 2020 09:19:11 AM PDT make: *** No targets specified and no makefile found. Stop. Jordan Mendler [image: The Veloz Group] The

Bug#969477: zfs-dkms fails to compile with 5.7.0-3 kernel blocking kernel upgrade

Package: zfs-dkms Version: 0.8.4-2 Severity: critical Justification: breaks unrelated software X-Debbugs-Cc: jordanmend...@gmail.com jordan@jordan-laptop:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done

Bug#969166: marked as done (ruby-has-scope: FTBFS with rails 6 - ArgumentError: unknown keywords: :only_tall, :id)

Your message dated Thu, 03 Sep 2020 15:37:08 + with message-id and subject line Bug#969166: fixed in ruby-has-scope 0.7.2-3 has caused the Debian Bug report #969166, regarding ruby-has-scope: FTBFS with rails 6 - ArgumentError: unknown keywords: :only_tall, :id to be marked as done. This

Bug#969166: marked as pending in ruby-has-scope

Control: tag -1 pending Hello, Bug #969166 in ruby-has-scope 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#969166 marked as pending in ruby-has-scope

Processing control commands: > tag -1 pending Bug #969166 [ruby-has-scope] ruby-has-scope: FTBFS with rails 6 - ArgumentError: unknown keywords: :only_tall, :id Added tag(s) pending. -- 969166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969166 Debian Bug Tracking System Contact

Bug#969467: miller: CVE-2020-15167

Source: miller Version: 5.9.0-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for miller. CVE-2020-15167[0]: | In Miller (command line utility) using the configuration file support | introduced in

Bug#957039: marked as done (biloba: ftbfs with GCC-10)

Your message dated Thu, 03 Sep 2020 14:48:35 + with message-id and subject line Bug#957039: fixed in biloba 0.9.3-10 has caused the Debian Bug report #957039, regarding biloba: 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#942965: marked as done (closure-compiler: Python2 removal in sid/bullseye)

Your message dated Thu, 03 Sep 2020 14:33:48 + with message-id and subject line Bug#942965: fixed in closure-compiler 20130227+dfsg1-10.1 has caused the Debian Bug report #942965, regarding closure-compiler: Python2 removal in sid/bullseye to be marked as done. This means that you claim that

Bug#942965: Patch for closure-compiler rc bugs, possible NMU.

On 03/09/2020 14:45, tony mancill wrote: Hi Peter, If you have fixes for closure-compiler, please feel free to go ahead and NMU. I will pick up the changes and apply them to the packaging repo from the NMU. NMU uploaded. Thank you for helping with this, tony On Thu, Sep 03, 2020 at

Bug#942965: Patch for closure-compiler rc bugs, possible NMU.

Hi Peter, If you have fixes for closure-compiler, please feel free to go ahead and NMU. I will pick up the changes and apply them to the packaging repo from the NMU. Thank you for helping with this, tony On Thu, Sep 03, 2020 at 02:05:03PM +0100, peter green wrote: > tags 942965 +patch > tags

Bug#969222: Workaround

As a workaround I tried setting the "network.http.spdy.enabled.http2" value to false in Thunderbird and it seems to work for now Gabriel Rolland

Bug#969464: src:r-cran-brms: fails to migrate to testing for too long: autopkgtest regression

Source: r-cran-brms Version: 2.12.0-2 Severity: serious Control: close -1 2.13.3-1 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 and

Processed: src:r-cran-brms: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 2.13.3-1 Bug #969464 [src:r-cran-brms] src:r-cran-brms: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions r-cran-brms/2.13.3-1. Bug #969464 [src:r-cran-brms] src:r-cran-brms: fails to migrate to testing for too

Bug#969222: cyrus-caldav: hhtp keep 100% CPU after access with Thunderbird

Is the same problem of bug #961600 Seems to be a problem with http2 support, but apparently it needs to be disabled during compilation, I have not found a way to disable it with the package :-( Gabriel Rolland

Bug#942965: Patch for closure-compiler rc bugs, possible NMU.

tags 942965 +patch tags 961839 +pending The attached debdiff fixes bugs 942965 and 961839, the former by changing the build-dependency from python-docutils to python3-docutils and the latter by adding "ant.build.javac.source=8" and "ant.build.javac.target=8" to debian/ant.properties. If I do

Bug#964674: debian-reference: FTBFS: build-dependency not installable: libopencc2-data

Lucas Nussbaum wrote: > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: libopencc2-data but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. Fixed in git. Tagging this bug as pending This

Bug#969317: marked as done (paryfor: baseline violation on x86 and FTBFS everywhere else)

Your message dated Thu, 03 Sep 2020 11:50:06 + with message-id and subject line Bug#969317: fixed in paryfor 0.1-3 has caused the Debian Bug report #969317, regarding paryfor: baseline violation on x86 and FTBFS everywhere else to be marked as done. This means that you claim that the problem

Bug#964668: marked as done (fakechroot: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2)

Your message dated Thu, 03 Sep 2020 11:48:39 + with message-id and subject line Bug#964668: fixed in fakechroot 2.19-3.3 has caused the Debian Bug report #964668, regarding fakechroot: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2 to be marked as done. This means

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

Hi Simon, Simon McVittie (2020-09-03): > On Sun, 21 Jan 2018 at 21:27:47 +0100, Egmont Koblinger wrote: > > > We don't do c++ in d-i. > > > > Unfortunately this sounds really problematic. As of version 0.42 vte > > has been using (more and more) C++. This is not like Ubuntu's PCRE2 > > hack

Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte

On Sun, 21 Jan 2018 at 21:27:47 +0100, Egmont Koblinger wrote: > > We don't do c++ in d-i. > > Unfortunately this sounds really problematic. As of version 0.42 vte > has been using (more and more) C++. This is not like Ubuntu's PCRE2 > hack which is a matter of a few hours of work reverting and

Bug#964274: marked as done (ruby-websocket-extensions: CVE-2020-7663)

Your message dated Thu, 03 Sep 2020 08:48:32 + with message-id and subject line Bug#964274: fixed in ruby-websocket-extensions 0.1.5-1 has caused the Debian Bug report #964274, regarding ruby-websocket-extensions: CVE-2020-7663 to be marked as done. This means that you claim that the problem

Bug#969448: bind9: dies with assertion and does not restart

Package: bind9 Version: 1:9.16.6-2 Severity: critical X-Debbugs-Cc: none, Francesco Potortì This happened twice in the last days. Here are the logs Cycle 1/2 Aug 31 16:46:29 tucano named[786855]: starting BIND 9.16.6-Debian (Stable Release) Aug 31 16:46:29