Processed: tk-brief: diff for NMU version 5.10-0.1

Processing control commands: > tags 223915 + patch Bug #223915 [src:tk-brief] tk-brief: Please don't package it as a native package Bug #733433 [src:tk-brief] tk-brief: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision Added

Bug#223915: tk-brief: diff for NMU version 5.10-0.1

Control: tags 223915 + patch Control: tags 223915 + pending Control: tags 249196 + pending Dear maintainer, find attached the debdiff (limited to debian/ for an NMU for tk-brief (versioned as 5.10-0.1), upload to DELAYED/0[*) will follow in a few hours. Please feel free to tell me if I should

Processed: tk-brief: diff for NMU version 5.10-0.1

Processing control commands: > tags 223915 + patch Bug #223915 [src:tk-brief] tk-brief: Please don't package it as a native package Bug #733433 [src:tk-brief] tk-brief: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

On Wed, Jan 18, 2017 at 4:49 AM, Fabian Greffrath wrote: > Please note that the "preferred form for modification" is a term > exclusive to the GPL, it does not necessarily apply to fonts licensed > under any other license. Also, I am not sure if this is really exactly > what is meant by the

Bug#848214: marked as done (nfsdcltrack installed to wrong location)

Your message dated Wed, 18 Jan 2017 07:37:40 +0100 with message-id and subject line fixed in unstable / stretch has caused the Debian Bug report #848214, regarding nfsdcltrack installed to wrong location to be marked as done. This means that you

Bug#851634: Extensions do not load.

Also if this option "--enable-remote-extensions" is not specified, no extensions load.

Processed: Re: Bug#851710: zoneminder: CVE-2016-10140

Processing control commands: > severity -1 grave Bug #851710 [src:zoneminder] zoneminder: CVE-2016-10140 Severity set to 'grave' from 'important' -- 851710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#851375: marked as done (s3ql FTBFS: test_retrieve fails on several architectures)

Your message dated Wed, 18 Jan 2017 04:49:49 + with message-id and subject line Bug#851375: fixed in s3ql 2.21+dfsg-3 has caused the Debian Bug report #851375, regarding s3ql FTBFS: test_retrieve fails on several architectures to be marked as done. This

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

On Tue, Jan 17, 2017 at 10:29 PM, Fabian Greffrath wrote: > But the OTF format itself is just as suitable a source format for fonts as > any other format. Why is it so important what upstream has chosen? It is > not that font composition is a human-readable-to-binary-one-way-road like >

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

That would have been my guess too, but Bio:: Graphics 2.40 is the right version. When running build test on a virgin Mint 18.2 system with Bio::Perl 1.7.1 and Bio::Graphics 2.40 I'm getting 100% test success. This is very puzzling. I'll take a closer look tonight. Lincoln On Tue, Jan 17, 2017

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

On January 17, 2017 3:49:46 PM EST, Fabian Greffrath wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA256 > >Am Mittwoch, den 18.01.2017, 03:24 +1100 schrieb Ben Finney: >> Debian recipients should have equal access to make modifications to >> the work, build the work

Bug#850077: python-paramiko doesn't work with python-crypto 2.6-4

Version: 2.6-4+deb7u7 Hi, > python-paramiko doesn't work with python-crypto 2.6-4 I believe this was fixed in 2.6-4+deb7u7 (or earlier). :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#850077: marked as done (python-paramiko doesn't work with python-crypto 2.6-4)

Your message dated Wed, 18 Jan 2017 01:03:55 + with message-id <1484701435.2699191.851084080.0efc4...@webmail.messagingengine.com> and subject line Re: python-paramiko doesn't work with python-crypto 2.6-4 has caused the Debian Bug report #850077, regarding python-paramiko doesn't work with

Bug#851726: liggghts: FTBFS on single-CPU machines (not enough slots available)

Package: src:liggghts Version: 3.5.0+repack1-8 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh build-indep

Bug#753179: marked as done (festvox-czech-machac: FTBFS: Error reading ESPS file ./lpc/machac0004.lpc)

Your message dated Wed, 18 Jan 2017 00:04:32 + with message-id and subject line Bug#753179: fixed in festvox-czech-machac 1.0.0-3 has caused the Debian Bug report #753179, regarding festvox-czech-machac: FTBFS: Error reading ESPS file ./lpc/machac0004.lpc

Bug#753189: marked as done (festvox-czech-krb: FTBFS: Error reading ESPS file ./lpc/krb0012.lpc)

Your message dated Wed, 18 Jan 2017 00:04:12 + with message-id and subject line Bug#753189: fixed in festvox-czech-krb 1.0.0-3 has caused the Debian Bug report #753189, regarding festvox-czech-krb: FTBFS: Error reading ESPS file ./lpc/krb0012.lpc to be

Bug#750344: marked as done (festvox-czech-dita: FTBFS: US DB: failed to read coefs file from ./lpc/dita0001.lpc)

Your message dated Wed, 18 Jan 2017 00:03:50 + with message-id and subject line Bug#750344: fixed in festvox-czech-dita 1.0.0-3 has caused the Debian Bug report #750344, regarding festvox-czech-dita: FTBFS: US DB: failed to read coefs file from

Bug#851724: python-llfuse: FTBFS (failing tests)

Package: src:python-llfuse Version: 1.1.1+dfsg-5 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh build-indep

Bug#844796:

Adding /usr/lib/x86_64-linux-gnu/mutter to /etc/ld.so.conf.d/x86_64-linux-gnu.conf and running ldconfig fixed it for me. ldconfig doesn't process directories recursively and the mutter directory was missing. Here's what the conf looked like before the edit. # Multiarch support

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

On Tue, 17 Jan 2017 18:06:02 -0500, Lincoln Stein wrote: > Not good! But I believe that Gregor found that all these were caused by the > testing suite not finding the proper data files due to an assumption about > the current working directory. When he fixed this, there were just a > handful of

Bug#851634: sh -n checks

I would add a sh -n test to the build scripts to avoid such errors getting sent out.

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

Not good! But I believe that Gregor found that all these were caused by the testing suite not finding the proper data files due to an assumption about the current working directory. When he fixed this, there were just a handful of tests still failing. Gregor, is there a patch file that I can apply

Processed: tagging 838671

Processing commands for cont...@bugs.debian.org: > tags 838671 + jessie Bug #838671 [openchangeproxy] openchangeproxy: uninstallable in jessie, broken by samba Added tag(s) jessie. > thanks Stopping processing here. Please contact me if you need assistance. -- 838671:

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

Control: tags -1 patch One way to reproduce this bug: # apt-get install pocl-opencl-icd blender $ gdb blender open User Preferences -> System This promptly crashes; beignet-opencl-icd 1.2.1-1 (LLVM 3.8, like pocl) also triggers it, but beignet-opencl-icd 1.2.1-2 and mesa-opencl-icd (LLVM 3.9,

Processed: Re: Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

Processing control commands: > tags -1 patch Bug #848368 [src:llvm-toolchain-3.9] llvm-toolchain-3.9: Please add ELF symbols versions to the libraries Added tag(s) patch. -- 848368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848368 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#851714: gitlab: Cannot push to gitlab repositories with git >= 2.11.0

Package: gitlab Version: 8.13.6+dfsg2-2 Severity: grave Dear Maintainer, Gitlab repositories will no longer accept remote pushes to protected branches (which is the default!) with git 2.11.0 installed on the gitlab system, failing with: remote: GitLab: You are not allowed to force push code to

Bug#851518: cinnamon won't start

Hi, I updated today and cinnamon is working again. Thanks, Carsten

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Oh, I just remembered I once had a short conversation with RMS about the distribution of the ghostscript fonts in binary Type1 format albeit being licensed under the terms of the GPL: Date: Sun, 13 Feb 2011 14:02:32 -0500 From: Richard Stallman

Bug#851235: [debian-mysql] Bug#851235: Security fixes from the January 2017 CPU

I've built and tested the updates, and will pass debdiffs on to the security team once the CVE list is available. -- Lars - norvald.ry...@oracle.com wrote: > Source: mysql-5.7 > Version: 5.7.16-2 > Severity: grave > Tags: security upstream fixed-upstream > > The Oracle Critical Patch

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Mittwoch, den 18.01.2017, 03:24 +1100 schrieb Ben Finney: > Debian recipients should have equal access to make modifications to > the work, build the work from modified source, and install the > result. All these modifications could be made to

Bug#851233: [debian-mysql] Bug#851233: Security fixes from the January 2017 CPU

I've built and tested the updates, and will pass debdiffs on to the security team once the CVE list is available. -- Lars - norvald.ry...@oracle.com wrote: > Source: mysql-5.5 > Version: 5.5.53-0+deb8u1 > Severity: grave > Tags: security upstream fixed-upstream > > The Oracle Critical

Bug#851234: [debian-mysql] Bug#851234: Security fixes from the January 2017 CPU

I've built and tested the update, and will pass debdiffs on to the security team once the CVE list is available. -- Lars - norvald.ry...@oracle.com wrote: > Source: mysql-5.6 > Version: 5.6.34-1 > Severity: grave > Tags: security upstream fixed-upstream > > The Oracle Critical Patch Update

Bug#850970: pvpgn: switch to build depend on the metapackage default-libmysqlclient-dev

On Tuesday, 17 January 2017 12:54:44 AM AEDT Andreas Beckmann wrote: > I just uploaded a NMU to DELAYED/2, fixing these issues. Please let me > know if I should delay it longer. > > pvpgn (1.8.5-2.1) unstable; urgency=medium > . >* Non-maintainer upload. >* Switch Build-Depends to

Processed: severity of 794331 is normal

Processing commands for cont...@bugs.debian.org: > severity 794331 normal Bug #794331 {Done: Holger Levsen } [piuparts] daptup: insane amounts of output on upgrades from testing or jessie to sid Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please

Processed: unblock 851071 with 851041, unblock 851041 with 851071, forcibly merging 851071 851041

Processing commands for cont...@bugs.debian.org: > unblock 851071 with 851041 Bug #851071 [debhelper] debhelper: dh_auto_test now run twice, once under fakeroot 851071 was not blocked by any bugs. 851071 was blocking: 851041 Removed blocking bug(s) of 851071: 851041 > unblock 851041 with 851071

Processed: limit source to debhelper, tagging 851071

Processing commands for cont...@bugs.debian.org: > limit source debhelper Limiting to bugs with field 'source' containing at least one of 'debhelper' Limit currently set to 'source':'debhelper' > tags 851071 + pending Bug #851071 [debhelper] debhelper: dh_auto_test now run twice, once under

Processed (with 1 error): reassign 851041 to debhelper, forcibly merging 851071 851041

Processing commands for cont...@bugs.debian.org: > # This is a bug in debhelper - not f-el (affects already set) > reassign 851041 debhelper Bug #851041 [src:f-el] f-el: FTBFS: test failures Bug reassigned from package 'src:f-el' to 'debhelper'. No longer marked as found in versions

Bug#851702: marked as done (linux-image-amd64: Important (and unacceptable) delay for providing updates for users of signed linux kernels)

Your message dated Tue, 17 Jan 2017 19:54:49 + with message-id <1484682889.2998.61.ca...@decadent.org.uk> and subject line Re: Bug#851702: linux-image-amd64: Important (and unacceptable) delay for providing updates for users of signed linux kernels has caused the Debian Bug report #851702,

Processed: Re: Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Processing control commands: > clone -1 -2 Bug #850708 [pinentry-gtk2] pinentry-gtk-2 frequently fails to grab the pointer under fvwm Bug 850708 cloned as bug 851707 > retitle -2 pinentry-gtk-2 frequently fails to grab the keyboard under awesome Bug #851707 [pinentry-gtk2] pinentry-gtk-2

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Control: clone -1 -2 Control: retitle -2 pinentry-gtk-2 frequently fails to grab the keyboard under awesome <#secure method=pgpmime mode=sign> ❦ 17 janvier 2017 20:34 +0100, Vincent Lefevre  : >> ** (pinentry-gtk-2:21583): CRITICAL **: could not grab keyboard: not >>

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

On 2017-01-17 20:21:05 +0100, Vincent Bernat wrote: > Here is the output I get: > > OK Pleased to meet you > > ** (pinentry-gtk-2:21583): CRITICAL **: could not grab keyboard: not viewable > (3) > > ** (pinentry-gtk-2:21583): WARNING **: it took 4097 tries to grab the keyboard > > **

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

❦ 17 janvier 2017 12:13 +0100, Vincent Lefevre  : >> I have the same behaviour with awesome. My setup didn't change since >> quite some time but this behaviour is recent while neither awesome nor >> pinentry-gtk2 has been updated. I got the behavior immediately after >>

Bug#851702: linux-image-amd64: Important (and unacceptable) delay for providing updates for users of signed linux kernels

Package: linux-image-amd64 Version: 4.8+77~bpo8+1 Severity: critical Tags: security Justification: root security hole Hi, As of now two flavours of Linux kernels are released. The default ones are signed ones while other unsigned kernels are available. The problem is that there's a significant

Bug#850266: marked as done (Missing headers in -dev package)

Your message dated Tue, 17 Jan 2017 19:04:21 + with message-id and subject line Bug#850266: fixed in libsrtp2 2.0.0+20161214-1 has caused the Debian Bug report #850266, regarding Missing headers in -dev package to be marked as done. This means that you

Bug#851579: lcdproc: fails to install: post-installation script returned error exit status 10

On Monday, 16 January 2017 15:54:36 CET you wrote: > during a test with piuparts I noticed your package failed to install. The root cause is now fixed in dh_cme_upgrade with [1]. I will upload a new lcdproc package once cme is updated. All the best [1]

Bug#851552: marked as done (cowsay-off: Replaces and Breaks must be updated to 3.03+dfsg2-1 was 3.03+dfsg1-13)

Your message dated Tue, 17 Jan 2017 18:18:54 + with message-id and subject line Bug#851552: fixed in cowsay 3.03+dfsg2-3 has caused the Debian Bug report #851552, regarding cowsay-off: Replaces and Breaks must be updated to 3.03+dfsg2-1 was 3.03+dfsg1-13

Bug#844785: "not authorised" doing various desktoppy things [and 1 more messages] [and 1 more messages]

On Tue, 17 Jan 2017 13:35:14 + Ian Jackson wrote: > [1] AIUI this is when your laptop suspends to RAM, but after a timeout > or when the battery is low, wakes up so that it can suspend to disk. Linux implements hybrid sleep by going ahead and writing the

Bug#774164: libocrad-dev: libocrad.a contains non-reallocatable code

Control: severity -1 normal On Thu, Dec 15, 2016 at 09:42:08PM +0100, Petter Reinholdtsen wrote: > Control: severity -1 grave >... > If I understand the test results from > https://ci.debian.net/packages/o/ocrad/unstable/amd64/ > correct, the > library is no longer usable. >... That's mostly

Processed: Re: Bug#774164: libocrad-dev: libocrad.a contains non-reallocatable code

Processing control commands: > severity -1 normal Bug #774164 [libocrad-dev] libocrad-dev: libocrad.a contains non-reallocatable code Severity set to 'normal' from 'grave' -- 774164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774164 Debian Bug Tracking System Contact

Bug#845729: libtspi-dev must not force OpenSSL 1.1 on packages that are not ready

Control: reopen -1 Control: block 811576 by -1 On Tue, Jan 03, 2017 at 01:24:09PM +, Dimitri John Ledkov wrote: > On Wed, 30 Nov 2016 00:11:01 +0100 Sebastian Andrzej Siewior > wrote: > > On 2016-11-26 11:31:49 [+0200], Adrian Bunk wrote: > > > Package: libtspi-dev >

Processed: Re: Bug#845729: libtspi-dev must not force OpenSSL 1.1 on packages that are not ready

Processing control commands: > reopen -1 Bug #845729 {Done: Dimitri John Ledkov } [libtspi-dev] libtspi-dev must not force OpenSSL 1.1 on packages that are not ready 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

On 17-Jan-2017, Fabian Greffrath wrote: > Paul Wise wrote: > > […] The issue is that there is no Free Software in Debian main > > that can build the OTF from source. […] > > But the OTF format itself is just as suitable a source format for > fonts as any other format. Why is it so important what

Processed: Bug does not seem to be limited to latest packages

Processing commands for cont...@bugs.debian.org: > reassign 840931 src:libimobiledevice Bug #840931 [libimobiledevice6] libimobiledevice4 GnuTLS settings broken with iOS 10 Bug #847977 [libimobiledevice6] libimobiledevice6: GnuTLS error: Error in the pull function (iOS 10.1.1) Bug reassigned

Bug#846422: marked as done (fauhdlc: add libfl-dev to Build-Depends)

Your message dated Tue, 17 Jan 2017 16:04:42 + with message-id and subject line Bug#846422: fixed in fauhdlc 20130704-1.1 has caused the Debian Bug report #846422, regarding fauhdlc: add libfl-dev to Build-Depends to be marked as done. This means that you

Bug#835106: marked as done (fauhdlc: FTBFS: expected ')' before 'istream')

Your message dated Tue, 17 Jan 2017 16:04:42 + with message-id and subject line Bug#835106: fixed in fauhdlc 20130704-1.1 has caused the Debian Bug report #835106, regarding fauhdlc: FTBFS: expected ')' before 'istream' to be marked as done. This means

Bug#847580: util-vserver testing migration is delayed by #850765

The util-vserver testing migration is delayed by #850765 cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S.

Bug#828524: qterm testing migration is delayed by #851412

The qterm testing migration is delayed by #851412 cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck -

Processed: #851412 affects qterm package

Processing commands for cont...@bugs.debian.org: > affects 851412 + qterm Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV Bug #851505 [src:systemd] Xvfb segfaults on mips64el Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el Bug #851642

Bug#850244: marked as done (reconserver: FTBFS: reConServer.cxx:941:164: error: no matching function for call to 'resip::HEPSipMessageLoggingHandler::HEPSipMessageLoggingHandler(resip::Data&, int&, in

Your message dated Tue, 17 Jan 2017 15:54:38 + with message-id and subject line Bug#850244: fixed in reconserver 0.13.3-1 has caused the Debian Bug report #850244, regarding reconserver: FTBFS: reConServer.cxx:941:164: error: no matching function for call

Processed: #851412 affects dbus (SIGSEGV), thus affects qevercloud build on mips64el

Processing commands for cont...@bugs.debian.org: > affects 851412 + qevercloud Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV Bug #851505 [src:systemd] Xvfb segfaults on mips64el Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el Bug #851642

Processed: Re: Bug#753927: usbredir: Broken patch disallows dpkg-source unpack

Processing commands for cont...@bugs.debian.org: > # already marked as fixed in 0.7-1, in stable and sid > close 753927 Bug #753927 [src:usbredir] usbredir: Broken patch disallows dpkg-source unpack Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance.

Processed: Re: Bug#846771: python-traits: FTBFS randomly

Processing commands for cont...@bugs.debian.org: > severity 846771 important Bug #846771 [src:python-traits] python-traits: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13 Severity set to 'important' from 'serious' > retitle 846771 python-traits: FTBFS

Bug#850948: marked as done (needrestart,piuparts: needrestart hangs -> piupart fails -> debian-design blocked)

Your message dated Tue, 17 Jan 2017 15:33:40 + with message-id and subject line Bug#850948: fixed in needrestart 2.11-1 has caused the Debian Bug report #850948, regarding needrestart,piuparts: needrestart hangs -> piupart fails -> debian-design blocked

Bug#850765: marked as done (util-vserver: fails to remove: postrm called with unknown argument `remove')

Your message dated Tue, 17 Jan 2017 15:08:10 + with message-id and subject line Bug#850765: fixed in util-vserver 0.30.216-pre3120-1.4 has caused the Debian Bug report #850765, regarding util-vserver: fails to remove: postrm called with unknown argument

Bug#851063: marked as done (bind9: CVE-2016-9147: An error handling a query response containing inconsistent DNSSEC information could cause an assertion failure)

Your message dated Tue, 17 Jan 2017 15:00:15 + with message-id and subject line Bug#851063: fixed in bind9 1:9.10.4-P5-1 has caused the Debian Bug report #851063, regarding bind9: CVE-2016-9147: An error handling a query response containing inconsistent

Bug#851062: marked as done (bind9: CVE-2016-9444: An unusually-formed DS record response could cause an assertion failure)

Your message dated Tue, 17 Jan 2017 15:00:15 + with message-id and subject line Bug#851062: fixed in bind9 1:9.10.4-P5-1 has caused the Debian Bug report #851062, regarding bind9: CVE-2016-9444: An unusually-formed DS record response could cause an

Bug#851065: marked as done (bind9: CVE-2016-9131: A malformed response to an ANY query can cause an assertion failure during recursion)

Your message dated Tue, 17 Jan 2017 15:00:16 + with message-id and subject line Bug#851065: fixed in bind9 1:9.10.4-P5-1 has caused the Debian Bug report #851065, regarding bind9: CVE-2016-9131: A malformed response to an ANY query can cause an assertion

Bug#839010: marked as done (bind9: CVE-2016-2776: Assertion failure in query processing)

Your message dated Tue, 17 Jan 2017 15:00:15 + with message-id and subject line Bug#839010: fixed in bind9 1:9.10.4-P5-1 has caused the Debian Bug report #839010, regarding bind9: CVE-2016-2776: Assertion failure in query processing to be marked as done.

Bug#842858: marked as done (bind9: CVE-2016-8864: A problem handling responses containing a DNAME answer can lead to an assertion failure)

Your message dated Tue, 17 Jan 2017 15:00:15 + with message-id and subject line Bug#842858: fixed in bind9 1:9.10.4-P5-1 has caused the Debian Bug report #842858, regarding bind9: CVE-2016-8864: A problem handling responses containing a DNAME answer can

Bug#828082: marked as done (bind9: FTBFS with openssl 1.1)

Your message dated Tue, 17 Jan 2017 15:00:15 + with message-id and subject line Bug#828082: fixed in bind9 1:9.10.4-P5-1 has caused the Debian Bug report #828082, regarding bind9: FTBFS with openssl 1.1 to be marked as done. This means that you claim that

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

Paul Wise wrote: > The issue isn't that they currently use proprietary software to > convert to OTF format. The issue is that there is no Free Software in > Debian main that can build the OTF from source. This is a clear > violation of Debian policy and that indicates the package needs to be > in

Bug#851412: #851412: libsystemd segfaults on mips64el

Control: affects -1 src:iodine On Sun, 15 Jan 2017 14:12:06 +0100, Christian Hofstaedtler wrote: > Control: affects -1 + pdns pdns-recursor > > pdns and pdns-recursor link against libsystemd, and this bug causes > both of them to just segfault on startup on mips64el. I'm pretty sure that the

Processed: Re: Bug#851412: #851412: libsystemd segfaults on mips64el

Processing control commands: > affects -1 src:iodine Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV Bug #851505 [src:systemd] Xvfb segfaults on mips64el Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el Bug #851642 [src:systemd] perl: FTBFS on

Bug#851649: (no subject)

I have no objections, but I don't have time right now to do it. Piotr did the 1.7.0-1 upload so please verify with him.

Processed: Re: Bug#851642: perl: FTBFS on mips64el: dist/threads/t/join.t failure

Processing control commands: > reassign -1 src:systemd Bug #851642 [perl] perl: FTBFS on mips64el: dist/threads/t/join.t failure Bug reassigned from package 'perl' to 'src:systemd'. No longer marked as found in versions perl/5.24.1-1. Ignoring request to alter fixed versions of bug #851642 to the

Bug#851642: perl: FTBFS on mips64el: dist/threads/t/join.t failure

Control: reassign -1 src:systemd Control: forcemerge 851412 -1 Control: affects 851412 perl procps Hi, On 17/01/17 07:37, Niko Tyni wrote: > Package: perl > Version: 5.24.1-1 > Severity: serious > X-Debbugs-Cc: debian-m...@lists.debian.org > > This package failed to build on mips64el: > >

Bug#838671: openchangeproxy: uninstallable in jessie, broken by samba

Followup-For: Bug #838671 openchange also FTBFS in stable: Compiling mapiproxy/dcesrv_mapiproxy.c with -fPIC mapiproxy/dcesrv_mapiproxy.c: In function 'mapiproxy_op_connect': mapiproxy/dcesrv_mapiproxy.c:135:5: error: dereferencing pointer to incomplete type b->assoc_group_id =

Bug#821530: marked as done (libsparkline-php: PHP 7.0 Transition)

Your message dated Tue, 17 Jan 2017 13:49:15 + with message-id and subject line Bug#821530: fixed in sparkline-php 0.2-6 has caused the Debian Bug report #821530, regarding libsparkline-php: PHP 7.0 Transition to be marked as done. This means that you

Bug#848289: marked as done (ruby-riddle: (build-)depends on mysql-{client,server})

Your message dated Tue, 17 Jan 2017 13:49:10 + with message-id and subject line Bug#848289: fixed in ruby-riddle 1.5.12-4 has caused the Debian Bug report #848289, regarding ruby-riddle: (build-)depends on mysql-{client,server} to be marked as done. This

Bug#841601: marked as done (ruby-riddle: FTBFS: ERROR: Test "ruby2.3" failed.)

Your message dated Tue, 17 Jan 2017 13:49:10 + with message-id and subject line Bug#841601: fixed in ruby-riddle 1.5.12-4 has caused the Debian Bug report #841601, regarding ruby-riddle: FTBFS: ERROR: Test "ruby2.3" failed. to be marked as done. This

Bug#851564: nslcd fails to start: postinst sets tls_cacertdir wrong

Control: found -1 nss-pam-ldapd/0.9.4-2 Control: tags -1 + pending On Mon, 2017-01-16 at 12:55 +0100, Thomas Wallrafen wrote: > See the attached ncslcd.conf file (the version before the > upgrade). Thanks for providing the info. I tracked the bug down to a problem in the parsing of the

Processed: Re: Bug#851564: nslcd fails to start: postinst sets tls_cacertdir wrong

Processing control commands: > found -1 nss-pam-ldapd/0.9.4-2 Bug #851564 [nslcd] nslcd fails to start: postinst sets tls_cacertdir wrong Marked as found in versions nss-pam-ldapd/0.9.4-2. > tags -1 + pending Bug #851564 [nslcd] nslcd fails to start: postinst sets tls_cacertdir wrong Added tag(s)

Bug#844785: "not authorised" doing various desktoppy things [and 1 more messages] [and 1 more messages]

Martín Ferrari writes ("Re: "not authorised" doing various desktoppy things [and 1 more messages]"): > This seems to solve the problem for me, thank you very much! (And I hope > you can get this in for stretch!) Thanks to everyone for their reports. This is very helpful. Currently experimental

Bug#851598: tex-common: fails to upgrade jessie->stretch (recommends enabled) with cadabra installed

Hi Andreas, big thanks for testing! > /etc/texmf/owned by: texlive-math-extra, texlive-base, tex-common Sounds reasonable. > /etc/texmf/hyphen.d/ not owned > > not sure who created /etc/texmf/hyphen.d/ (and which file might have > been in there) > if that's still in active use, some

Processed: Fwd:

Processing commands for cont...@bugs.debian.org: > severity 851003 normal Bug #851003 [src:python-django-pyscss] python-django-pyscss: FTBFS: Test failures Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 851003:

Processed (with 2 errors): your mail

Processing commands for cont...@bugs.debian.org: > tags 851003 moreinfo unreproducible ! Unknown tag/s: !. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental

Bug#761568: Your printing quotes

Good Morning, I own a medium sized print company based in the UK and I am looking to see if we can help you with your ongoing print requirements. Your business is really important to us!! Please let us quote on your next print job!! You can request a free sample pack here

Bug#845827: marked as done (captagent: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Tue, 17 Jan 2017 13:18:27 + with message-id and subject line Bug#845827: fixed in captagent 6.1.0.20-3 has caused the Debian Bug report #845827, regarding captagent: switch to build depend on the metapackage default-libmysqlclient-dev

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

Hi Yann, On 17 January 2017 at 06:54, Yann Richard wrote: > > Hi, > > We have made a package from fcoe-utils source version 1.0.31 which fix init > bug : > > https://github.com/DSI-Universite-Rennes2/fcoe-utils > > Tested on HP 465c G8 on Ethernet controller:

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

On Tue, Jan 17, 2017 at 7:32 PM, Fabian Greffrath wrote: > thank you very much for your bug report. However, I believe you are wrong > with applying RC severity to this issue and I have added FTP-Masters to CC > in the hope for clarification. I agree with Ben on this issue.

Bug#851667: openjdk-8-jre-headless needs Breaks: ca-certificates-java (<< 20160321~)

Package: openjdk-8-jre-headless Severity: serious Tags: security patch < Viiru> Hmm. So apparently ca-certificates-java has a hard-coded list of JRE versions. < Viiru> Thus if one installs JRE 8 from backports to a jessie machine (and removes JRE 7) the trust store will never

Bug#851598: tex-common: fails to upgrade jessie->stretch (recommends enabled) with cadabra installed

On 2017-01-17 05:37, Norbert Preining wrote: >> That worked. > > Thanks for testing. > >> I'll now check the other failures with this new package, but that will >> take more time - some larger metapackages like med-bio are involved here. > > Do you have a time frame when it will be ready? If it

Bug#851666: php-sabre-event: PHP 7.0 transition

Package: php-sabre-event Version: 3.0.0-1 Severity: serious Hi, php-sabre-event in experimental still depends on php5. Andreas

Bug#851665: php-hamcrest: php 7.0 transition

Package: php-hamcrest Version: 2.0.0-1 Severity: serious php-hamcrest in experimental still depends on php5 ... Andreas

Bug#846771: Unable to reproduce

On Tue, Jan 17, 2017 at 11:20:55AM +0100, Andreas Tille wrote: > I intentionally ssh-ed into a machine without enabling X and have > build there in pbuilder. The build runs fine. My build history for this package: Status: successful python-traits_4.5.0-1_amd64-20161126T172508Z Status: failed

Bug#851339: [Pkg-fonts-devel] Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

Dear Ben, thank you very much for your bug report. However, I believe you are wrong with applying RC severity to this issue and I have added FTP-Masters to CC in the hope for clarification. Ben Finney wrote: > I see now that this refers to a proprietary program named Glyphs, as a > program used

Bug#846268: cython: Upstream resolution

Hi Yaroslav, looks like upstream included the fix in cython 0.25.2, so if you don't wait too long this bug can still be fixed by just uploading the new version. Best, Tobias On Fri, 2 Dec 2016 08:14:24 -0500 Antonio Russo wrote: > tags -1 + patch > > Upstream has

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

On 2017-01-17 10:19:50 +0100, Vincent Bernat wrote: > I have the same behaviour with awesome. My setup didn't change since > quite some time but this behaviour is recent while neither awesome nor > pinentry-gtk2 has been updated. I got the behavior immediately after > rebooting. Applying the patch

Processed: retitle 848764

Processing commands for cont...@bugs.debian.org: > retitle 848764 theano: test failures with Numpy 1.12 Bug #848764 [src:theano] test failures with Numpy 1.12 Changed Bug title to 'theano: test failures with Numpy 1.12' from 'test failures with Numpy 1.12'. > thanks Stopping processing here.

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

> Ehm, yes. :) so I just tested an upgrade from jessie to sid of tango-db and it works :))) Now I have only one concern about the dump. Since we had a failure with the dump when it ran as user, we discovered that our procedures where wrong and necessitate the dbadmin grants in order to works.

  1   2   >