Bug#963546: marked as done (meson: autopkgtest failures)

Your message dated Tue, 14 Jul 2020 05:18:33 + with message-id and subject line Bug#963546: fixed in meson 0.55.0-1 has caused the Debian Bug report #963546, regarding meson: autopkgtest failures to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does

On Wed, May 20, 2020 at 12:48:18PM -0700, Ross Vandegrift wrote: > On Thu, May 07, 2020 at 07:52:31PM +0200, Julien Cristau wrote: > > On Thu, May 07, 2020 at 09:48:34PM +1000, Dmitry Smirnov wrote: > > > On Thursday, 7 May 2020 7:04:17 PM AEST Julien Cristau wrote: > > > > This use of Provides is

Bug#885195: [Pkg-electronics-devel] Bug#885195: Bug#885195: geda-gaf: please migrate to guile-2.2

Bdale Garbee writes: > So... while I'm sure gEDA could be "saved" in Debian with enough effort, > I just don't see the point, and won't put any time or attention on it > myself. I'd suggest we should do something "soonish". This is the last package holding guile-2.0 in testing, and I'd

Processed: clone 959845

Processing commands for cont...@bugs.debian.org: > clone 959845 -1 -2 Bug #959845 [src:librsvg] librsvg: FTBFS on Loongson-3A: assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1)) Bug 959845 cloned as bugs 964988-964989 > reassign -1 src:llvm-toolchain-9 Bug #964988 [src:librsvg] librsvg:

Bug#961606: marked as done (sklearn-pandas: FTBFS: doctest error)

Your message dated Mon, 13 Jul 2020 23:39:08 + with message-id and subject line Bug#961606: fixed in python-hug 2.6.0-2 has caused the Debian Bug report #961606, regarding sklearn-pandas: FTBFS: doctest error to be marked as done. This means that you claim that the problem has been dealt

Bug#916022: marked as done (python-hug binary-any FTBFS)

Your message dated Mon, 13 Jul 2020 23:39:08 + with message-id and subject line Bug#916022: fixed in python-hug 2.6.0-2 has caused the Debian Bug report #916022, regarding python-hug binary-any FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#953258: marked as done (python3-hug-doc: missing Breaks+Replaces: python3-hug (<< 2.4.1))

Your message dated Mon, 13 Jul 2020 23:39:08 + with message-id and subject line Bug#953258: fixed in python-hug 2.6.0-2 has caused the Debian Bug report #953258, regarding python3-hug-doc: missing Breaks+Replaces: python3-hug (<< 2.4.1) to be marked as done. This means that you claim that

Bug#964822: marked as done (pandoc: BD-Uninstallable)

Your message dated Mon, 13 Jul 2020 22:34:15 + with message-id and subject line Bug#964822: fixed in pandoc 2.8.1-1 has caused the Debian Bug report #964822, regarding pandoc: BD-Uninstallable to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Bug#964220: vdr: FTBFS with glibc 2.31 (uses removed stime function)

Processing control commands: > severity -1 serious Bug #964220 [src:vdr] vdr: FTBFS with glibc 2.31 (uses removed stime function) Severity set to 'serious' from 'important' -- 964220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964220 Debian Bug Tracking System Contact

Processed: Bug#964223: linuxtv-dvb-apps: FTBFS with glibc 2.31 (uses removed stime function)

Processing control commands: > severity -1 serious Bug #964223 [src:linuxtv-dvb-apps] linuxtv-dvb-apps: FTBFS with glibc 2.31 (uses removed stime function) Severity set to 'serious' from 'important' -- 964223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964223 Debian Bug Tracking System

Processed: Bug#964231: faketime: FTBFS with glibc 2.31 due to ftime deprecation

Processing control commands: > severity -1 serious Bug #964231 [faketime] faketime: FTBFS with glibc 2.31 due to ftime deprecation Severity set to 'serious' from 'important' -- 964231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964231 Debian Bug Tracking System Contact

Processed: Bug#964227: datefudge: FTBFS with glibc 2.31 (conflicting gettimeofday prototype)

Processing control commands: > severity -1 serious Bug #964227 [datefudge] datefudge: FTBFS with glibc 2.31 (conflicting gettimeofday prototype) Severity set to 'serious' from 'important' -- 964227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964227 Debian Bug Tracking System Contact

Bug#964687: marked as done (quassel: FTBFS: qmetatype.h:818:16: error: ambiguous overload for ‘operator<<’ (operand types are ‘QDataStream’ and ‘const DccConfig::IpDetectionMode’))

Your message dated Mon, 13 Jul 2020 21:21:20 + with message-id and subject line Bug#964687: fixed in quassel 1:0.13.1-4 has caused the Debian Bug report #964687, regarding quassel: FTBFS: qmetatype.h:818:16: error: ambiguous overload for ‘operator<<’ (operand types are ‘QDataStream’ and

Bug#964334:

After running "sudo apt update && sudo apt upgrade && sudo apt dist-upgrade" There was an update to chromium and the issue seems to be resolved.

Bug#963808: ruby-sanitize: CVE-2020-4054: HTML sanitization bypass in Sanitize

Hi Antonio, On Mon, Jul 13, 2020 at 11:19:38AM -0300, terce...@debian.org wrote: > On Sun, Jul 12, 2020 at 03:11:30PM +0200, Salvatore Bonaccorso wrote: > > On Sat, Jun 27, 2020 at 09:10:01PM +0200, Salvatore Bonaccorso wrote: > > > Source: ruby-sanitize > > > Version: 4.6.6-2 > > > Severity:

Bug#963808: ruby-sanitize: diff for NMU version 4.6.6-2.1

Control: tags 963808 + patch Control: tags 963808 + pending Dear maintainer, I've prepared an NMU for ruby-sanitize (versioned as 4.6.6-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Salvatore diff -Nru ruby-sanitize-4.6.6/debian/changelog

Processed: ruby-sanitize: diff for NMU version 4.6.6-2.1

Processing control commands: > tags 963808 + patch Bug #963808 [src:ruby-sanitize] ruby-sanitize: CVE-2020-4054: HTML sanitization bypass in Sanitize Added tag(s) patch. > tags 963808 + pending Bug #963808 [src:ruby-sanitize] ruby-sanitize: CVE-2020-4054: HTML sanitization bypass in Sanitize

Bug#964821: New Upstream Version

There's a new upstream version available, and I cannot update the github-backup package until libghc-github-dev (>= 0.23) is available. So I hope to see the new version packaged. Cheers, --Barak.

Processed: found 964950 in 1.14.2-2+deb10u1, found 964950 in 1.10.3-1+deb9u3, found 964950 in 1.10.3-1

Processing commands for cont...@bugs.debian.org: > found 964950 1.14.2-2+deb10u1 Bug #964950 [nginx] nginx: CVE-2020-11724 Marked as found in versions nginx/1.14.2-2+deb10u1. > found 964950 1.10.3-1+deb9u3 Bug #964950 [nginx] nginx: CVE-2020-11724 Marked as found in versions

Bug#964979: src:neutron-vpnaas: fails to migrate to testing for too long: piuparts regression

Source: neutron-vpnaas Version: 2:15.0.0-2 Severity: serious Control: close -1 2:16.0.0-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

Bug#964981: src:neutron-dynamic-routing: fails to migrate to testing for too long: piuparts regression

Source: neutron-dynamic-routing Version: 2:15.0.0-3 Severity: serious Control: close -1 2:16.0.0-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

Processed: src:neutron-vpnaas: fails to migrate to testing for too long: piuparts regression

Processing control commands: > close -1 2:16.0.0-1 Bug #964979 [src:neutron-vpnaas] src:neutron-vpnaas: fails to migrate to testing for too long: piuparts regression Marked as fixed in versions neutron-vpnaas/2:16.0.0-1. Bug #964979 [src:neutron-vpnaas] src:neutron-vpnaas: fails to migrate to

Processed: src:biojava4-live: fails to migrate to testing for too long: maintainer built arch:all binary

Processing control commands: > close -1 4.2.12+dfsg-3 Bug #964982 [src:biojava4-live] src:biojava4-live: fails to migrate to testing for too long: maintainer built arch:all binary Marked as fixed in versions biojava4-live/4.2.12+dfsg-3. Bug #964982 [src:biojava4-live] src:biojava4-live: fails to

Processed: src:neutron-dynamic-routing: fails to migrate to testing for too long: piuparts regression

Processing control commands: > close -1 2:16.0.0-1 Bug #964981 [src:neutron-dynamic-routing] src:neutron-dynamic-routing: fails to migrate to testing for too long: piuparts regression Marked as fixed in versions neutron-dynamic-routing/2:16.0.0-1. Bug #964981 [src:neutron-dynamic-routing]

Bug#964982: src:biojava4-live: fails to migrate to testing for too long: maintainer built arch:all binary

Source: biojava4-live Version: 4.2.12+dfsg-2 Severity: serious Control: close -1 4.2.12+dfsg-3 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

Processed: found 964950 in 1.18.0-4

Processing commands for cont...@bugs.debian.org: > found 964950 1.18.0-4 Bug #964950 [nginx] nginx: CVE-2020-11724 Marked as found in versions nginx/1.18.0-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 964950:

Processed: src:ruby-pgplot: fails to migrate to testing for too long: B-D on non-free package

Processing control commands: > close -1 0.2.0-1 Bug #964978 [src:ruby-pgplot] src:ruby-pgplot: fails to migrate to testing for too long: B-D on non-free package The source 'ruby-pgplot' and version '0.2.0-1' do not appear to match any binary packages Marked as fixed in versions

Bug#964978: src:ruby-pgplot: fails to migrate to testing for too long: B-D on non-free package

Source: ruby-pgplot Version: 0.1.9-3 Severity: serious Control: close -1 0.2.0-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

Bug#964044: mrpt: FTBFS: test failure

On 2020-06-30 22:37:57 +0200, Sebastian Ramacher wrote: > Source: mrpt > Version: 1:2.0.4-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > binNMUs of mrpt failed to build: > | [--] 1 test from RawlogGrabberApp > | [

Processed: found 964136 in 2.3.1-2

Processing commands for cont...@bugs.debian.org: > found 964136 2.3.1-2 Bug #964136 {Done: Nicolas Mora } [glewlwyd] glewlwyd build-depedencies unsatisfiable on armel Marked as found in versions glewlwyd/2.3.1-2. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#960073: Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT)

Hi, sorry for the late reply too. On Mon, Jul 06, 2020 at 02:56:04PM +0800, pengzon...@uniontech.com wrote: > Hi! > > Sorry for my late reply. I preload libGLX_mesa.so.0 , and then run the code > on the arm machine is ok. > I tried to debug it, and then I found something different. The parameter

Bug#964318: gosa login broken with PHP 7.4

Control: forwarded -1 https://github.com/gosa-project/gosa-core/pull/33 Hi, On Do 09 Jul 2020 21:54:34 CEST, Wolfgang Schweer wrote: On Mon, Jul 06, 2020 at 12:05:44PM +0200, Wolfgang Schweer wrote: In both encrypt and decrypt cases, the chosen cipher method seems to return 0. This is the

Processed: bug 963305 is forwarded to https://github.com/epam/Indigo/commit/7986373c9cc7664635df031a42f420a439ddc861

Processing commands for cont...@bugs.debian.org: > forwarded 963305 > https://github.com/epam/Indigo/commit/7986373c9cc7664635df031a42f420a439ddc861 Bug #963305 [src:indigo] indigo: FTBFS: ./api/java/src/main/java/com/epam/indigo/Indigo.java:95: error: incompatible types: boolean cannot be

Bug#964950: nginx: CVE-2020-11724

In case this helps, here's some documentation to test the issue with the new upstream test cases: https://wiki.debian.org/LTS/TestSuites/nginx and my planned stretch package: https://www.beuc.net/tmp/debian-lts/nginx/ Cheers! Sylvain Beucler Debian LTS Team diff -Nru

Bug#954517: marked as done (python-junit-xml: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13)

Your message dated Mon, 13 Jul 2020 14:42:19 + with message-id and subject line Bug#954517: fixed in python-junit-xml 1.9-1 has caused the Debian Bug report #954517, regarding python-junit-xml: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13 to be

Bug#963808: ruby-sanitize: CVE-2020-4054: HTML sanitization bypass in Sanitize

On Sun, Jul 12, 2020 at 03:11:30PM +0200, Salvatore Bonaccorso wrote: > On Sat, Jun 27, 2020 at 09:10:01PM +0200, Salvatore Bonaccorso wrote: > > Source: ruby-sanitize > > Version: 4.6.6-2 > > Severity: grave > > Tags: security upstream > > Justification: user security hole > > > > Hi, > > > >

Bug#964210: marked as done (octave-nan: FTBFS without internet access)

Your message dated Mon, 13 Jul 2020 13:48:40 + with message-id and subject line Bug#964210: fixed in octave-nan 3.4.5-3 has caused the Debian Bug report #964210, regarding octave-nan: FTBFS without internet access to be marked as done. This means that you claim that the problem has been

Bug#964210: marked as pending in octave-nan

Control: tag -1 pending Hello, Bug #964210 in octave-nan 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#964210 marked as pending in octave-nan

Processing control commands: > tag -1 pending Bug #964210 [src:octave-nan] octave-nan: FTBFS without internet access Added tag(s) pending. -- 964210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#964606: marked as done (ukui-control-center: FTBFS: qmetatype.h:812:20: error: use of deleted function ‘_KeyEntry::_KeyEntry(const _KeyEntry&)’)

Your message dated Mon, 13 Jul 2020 13:33:34 + with message-id and subject line Bug#964606: fixed in ukui-control-center 2.0.5-1 has caused the Debian Bug report #964606, regarding ukui-control-center: FTBFS: qmetatype.h:812:20: error: use of deleted function ‘_KeyEntry::_KeyEntry(const

Bug#959624: ruby-faraday: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `split' for nil:NilClass

Control: fixed -1 0.17.3-1 Hi, It seems that ruby-faraday 0.15.4-3 was updated, and the new version 0.17.3-1 doesn't have FTBFS issue. Regards,

Processed: Re: ruby-faraday: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `split' for nil:NilClass

Processing control commands: > fixed -1 0.17.3-1 Bug #959624 [src:ruby-faraday] ruby-faraday: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `split' for nil:NilClass Marked as fixed in versions ruby-faraday/0.17.3-1. -- 959624:

Bug#951981: marked as done (xfce4-sntray-plugin: FTBFS: libxfce4panel-2.0.vapi:104.9-104.47: error: overriding method `Xfce.PanelPlugin.remote_event' is incompatible with base method `bool Xfce.PanelP

Your message dated Mon, 13 Jul 2020 12:24:33 + with message-id and subject line Bug#951981: fixed in xfce4-sntray-plugin 0.4.13-1 has caused the Debian Bug report #951981, regarding xfce4-sntray-plugin: FTBFS: libxfce4panel-2.0.vapi:104.9-104.47: error: overriding method

Bug#962876: marked as done (kytos-sphinx-theme-common: should depend on fonts-glyphicons-halflings (not fonts-glewlwyd))

Your message dated Mon, 13 Jul 2020 12:07:56 + with message-id and subject line Bug#962876: fixed in kytos-sphinx-theme 0.0.1+dfsg-2 has caused the Debian Bug report #962876, regarding kytos-sphinx-theme-common: should depend on fonts-glyphicons-halflings (not fonts-glewlwyd) to be marked as

Bug#964318: marked as done (password encryption/decryption broken with PHP 7.4)

Your message dated Mon, 13 Jul 2020 11:54:20 + with message-id and subject line Bug#964318: fixed in gosa 2.7.4+reloaded3-12 has caused the Debian Bug report #964318, regarding password encryption/decryption broken with PHP 7.4 to be marked as done. This means that you claim that the problem

Bug#952044: ruby-browser: FTBFS: ERROR: Test "ruby2.7" failed: Invalid gemspec in [browser.gemspec]: No such file or directory - git

On Sun, 23 Feb 2020 08:43:58 +0100 Lucas Nussbaum wrote: > Source: ruby-browser > Version: 2.5.3-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: buster sid > Usertags: ftbfs-20200222 ftbfs-buster > > Hi, > > During a rebuild of all packages in sid, your package failed to build >

Processed: Re: Bug#964318: gosa login broken with PHP 7.4

Processing control commands: > forwarded -1 https://github.com/gosa-project/gosa-core/pull/33 Bug #964318 [gosa] password encryption/decryption broken with PHP 7.4 Set Bug forwarded-to-address to 'https://github.com/gosa-project/gosa-core/pull/33'. -- 964318:

Bug#964957: ugrep: Baseline violation on several architectures

Source: ugrep Version: 2.1.1+dfsg-1 Severity: serious After looking at the build log and sources, there are several baseline violations due to the package being built for what is supported on the buildd instead of the architecture baseline: - -march=native is always wrong in a distribution build

Bug#964318: marked as pending in gosa

Control: tag -1 pending Hello, Bug #964318 in gosa 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#964318 marked as pending in gosa

Processing control commands: > tag -1 pending Bug #964318 [gosa] password encryption/decryption broken with PHP 7.4 Added tag(s) pending. -- 964318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#964212: marked as done (net-cpp: FTBFS without internet access)

Your message dated Mon, 13 Jul 2020 11:05:50 + with message-id and subject line Bug#964212: fixed in net-cpp 2.2.1+dfsg1-5 has caused the Debian Bug report #964212, regarding net-cpp: FTBFS without internet access to be marked as done. This means that you claim that the problem has been

Processed: Bug#964670 marked as pending in gsettings-qt

Processing control commands: > tag -1 pending Bug #964670 [src:gsettings-qt] gsettings-qt: FTBFS: QQmlComponent: Component is not ready Added tag(s) pending. -- 964670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964670 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#964670: marked as pending in gsettings-qt

Control: tag -1 pending Hello, Bug #964670 in gsettings-qt 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#964212 marked as pending in net-cpp

Processing control commands: > tag -1 pending Bug #964212 [src:net-cpp] net-cpp: FTBFS without internet access Added tag(s) pending. -- 964212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#964212: marked as pending in net-cpp

Control: tag -1 pending Hello, Bug #964212 in net-cpp 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#894705: marked as done (pytest-instafail's autopkg tests fail with pytest 3.3)

Your message dated Mon, 13 Jul 2020 10:34:14 + with message-id and subject line Bug#894705: fixed in pytest-instafail 0.4.2-1 has caused the Debian Bug report #894705, regarding pytest-instafail's autopkg tests fail with pytest 3.3 to be marked as done. This means that you claim that the

Processed: Re: Bug#953489: fixed in php-horde-text-filter-jsmin 1.0.2-8

Processing control commands: > close -1 Bug #953489 [src:php-horde-text-filter-jsmin] php-horde-text-filter-jsmin: binaries for non-free not auto-built Marked Bug as done -- 953489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953489 Debian Bug Tracking System Contact

Bug#953489: fixed in php-horde-text-filter-jsmin 1.0.2-8

Control: close -1 Hi Ivo, On Fr 10 Jul 2020 21:46:28 CEST, Ivo De Decker wrote: On 7/10/20 8:57 PM, Mike Gabriel wrote: Hi Ivo, Hi Mike, I have asked for white-listing some days back. I have pinged Philipp Kern explicitly once more (he white-listed php-horde-javascriptminify-jsmin

Bug#963200: marked as done (flightgear: FTBFS on i386: 6 - FlightplanUnitTests (Failed))

Your message dated Mon, 13 Jul 2020 10:03:26 + with message-id and subject line Bug#963200: fixed in flightgear 1:2020.1.3+dfsg-1 has caused the Debian Bug report #963200, regarding flightgear: FTBFS on i386: 6 - FlightplanUnitTests (Failed) to be marked as done. This means that you claim

Processed: Bug#964211 marked as pending in octave-instrument-control

Processing control commands: > tag -1 pending Bug #964211 {Done: =?utf-8?q?Rafael_Laboissi=C3=A8re?= } [src:octave-instrument-control] octave-instrument-control: FTBFS without internet access Added tag(s) pending. -- 964211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964211 Debian Bug

Bug#963795: marked as done (r-cran-httr: autopkgtest regression)

Your message dated Mon, 13 Jul 2020 10:03:36 + with message-id and subject line Bug#963795: fixed in r-cran-httr 1.4.1-3 has caused the Debian Bug report #963795, regarding r-cran-httr: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt

Processed: severity of 962881 is serious

Processing commands for cont...@bugs.debian.org: > severity 962881 serious Bug #962881 [python3-django-postorius] python3-django-postorius: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) Severity set to 'serious' from 'important' > thanks Stopping

Bug#964211: marked as pending in octave-instrument-control

Control: tag -1 pending Hello, Bug #964211 in octave-instrument-control 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#964211: marked as done (octave-instrument-control: FTBFS without internet access)

Your message dated Mon, 13 Jul 2020 10:03:31 + with message-id and subject line Bug#964211: fixed in octave-instrument-control 0.5.0-2 has caused the Debian Bug report #964211, regarding octave-instrument-control: FTBFS without internet access to be marked as done. This means that you claim

Bug#964240: marked as done (samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency)

Your message dated Mon, 13 Jul 2020 09:10:05 + with message-id and subject line Bug#964240: fixed in sssd 2.3.0-1 has caused the Debian Bug report #964240, regarding samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency to be marked as done. This means that you

Bug#964701: marked as done (sssd: FTBFS: ../src/providers/ad/ad_gpo_ndr.c:108:13: error: implicit declaration of function ‘ndr_pull_get_switch_value’; did you mean ‘ndr_pull_set_switch_value’? [-Werro

Your message dated Mon, 13 Jul 2020 09:10:05 + with message-id and subject line Bug#964701: fixed in sssd 2.3.0-1 has caused the Debian Bug report #964701, regarding sssd: FTBFS: ../src/providers/ad/ad_gpo_ndr.c:108:13: error: implicit declaration of function ‘ndr_pull_get_switch_value’; did

Bug#964950: nginx: CVE-2020-11724

Package: nginx X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security upstream Hi, The following vulnerability was published for ngx_lua. CVE-2020-11724[0]: | ngx_http_lua_subrequest.c allows HTTP request smuggling, as | demonstrated by the ngx.location.capture API. If you fix

Bug#963111: marked as done (r-bioc-biocparallel: autopkgtest regression on ppc64el)

Your message dated Mon, 13 Jul 2020 08:41:20 + with message-id and subject line Bug#963111: fixed in r-bioc-biocparallel 1.22.0-2 has caused the Debian Bug report #963111, regarding r-bioc-biocparallel: autopkgtest regression on ppc64el to be marked as done. This means that you claim that

Processed: bug 962938 is forwarded to https://github.com/Lasagne/Lasagne/issues/923

Processing commands for cont...@bugs.debian.org: > forwarded 962938 https://github.com/Lasagne/Lasagne/issues/923 Bug #962938 [src:lasagne] lasagne: autopkgtest fails with newer python-mock Set Bug forwarded-to-address to 'https://github.com/Lasagne/Lasagne/issues/923'. > thanks Stopping

Processed: Added tags

Processing commands for cont...@bugs.debian.org: > tags 964946 + security squeeze wheezy jessie stretch buster bullseye sid Bug #964946 [rhythmbox] rhythmbox.org domain doesn't belong to GNOME/Rhythmbox Added tag(s) security, buster, squeeze, wheezy, sid, bullseye, jessie, and stretch. > End of

Processed: Bug#955107: python3-sphinxcontrib.spelling: Uses obsolete API ‘Sphinx.info’

Processing control commands: > reassign -1 python3-sphinxcontrib.spelling Bug #955107 [src:python-coverage] python-coverage: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info' Bug reassigned from package 'src:python-coverage' to 'python3-sphinxcontrib.spelling'. No

Bug#955107: python3-sphinxcontrib.spelling: Uses obsolete API ‘Sphinx.info’

Control: reassign -1 python3-sphinxcontrib.spelling Control: retitle -1 python3-sphinxcontrib.spelling: Uses obsolete API ‘Sphinx.info’ Control: found -1 python3-sphinxcontrol.spelling/4.2.0-2 Control: fixed -1 python3-sphinxcontrol.spelling/4.3.0-1 On 27-Mar-2020, Lucas Nussbaum wrote: > > […]

Processed: Update severity

Processing commands for cont...@bugs.debian.org: > severity 964946 critical Bug #964946 [rhythmbox] rhythmbox.org domain doesn't belong to GNOME/Rhythmbox Severity set to 'critical' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 964946:

Processed: tagging 962825

Processing commands for cont...@bugs.debian.org: > tags 962825 + fixed Bug #962825 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } [node-opencv] node-opencv: FTBFS against nodejs 12.18 - fixed in upstream version 7.0.0 Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need

Processed: tagging 937442

Processing commands for cont...@bugs.debian.org: > tags 937442 + fixed-in-experimental Bug #937442 {Done: Markus Koschany } [src:pygame-sdl2] pygame-sdl2: Python2 removal in sid/bullseye Added tag(s) fixed-in-experimental. > thanks Stopping processing here. Please contact me if you need

Processed: notfound 962085 in bcalm/2.2.2-1.1

Processing commands for cont...@bugs.debian.org: > notfound 962085 bcalm/2.2.2-1.1 Bug #962085 {Done: David Parsons } [bcalm,kissplice] bcalm,kissplice: both ship /usr/bin/bcalm No longer marked as found in versions bcalm/2.2.2-1.1. > thanks Stopping processing here. Please contact me if you

Bug#964705: marked as done (zoneminder: FTBFS: build-dependency not installable: fonts-glewlwyd)

Your message dated Mon, 13 Jul 2020 06:48:49 + with message-id and subject line Bug#962886: fixed in zoneminder 1.34.16-2 has caused the Debian Bug report #962886, regarding zoneminder: FTBFS: build-dependency not installable: fonts-glewlwyd to be marked as done. This means that you claim

Bug#962886: marked as done (zoneminder: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd))

Your message dated Mon, 13 Jul 2020 06:48:49 + with message-id and subject line Bug#962886: fixed in zoneminder 1.34.16-2 has caused the Debian Bug report #962886, regarding zoneminder: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) to be marked as

Processed: Bug#962886 marked as pending in zoneminder

Processing control commands: > tag -1 pending Bug #962886 [src:zoneminder] zoneminder: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) Bug #964705 [src:zoneminder] zoneminder: FTBFS: build-dependency not installable: fonts-glewlwyd Added tag(s)

Bug#962886: marked as pending in zoneminder

Control: tag -1 pending Hello, Bug #962886 in zoneminder 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: